After a recent update to V2R2M1 of WebQuery our schedules no longer run with reports that have

-PROMPT for the field selections

Example

-PROMPT &CO.(<Company1,100>,<Company 2,200>).Enter the Company.

The reports run manually just not through Report Caster

The only error given is the 'Task 1' error below. When I remove the -PROMPT and leave the schedule as is they run but then users have issues running the reports manually.

quote:

Executing focexec.


Connection to the Reporting Server EDASERVE closed at 2018-09-11 05:05:03.468-0500 (1,536,660,303,468)


Job ran on the Reporting Server EDASERVE for 1.748 seconds


Task finished.


No report from Task 'Task 1'.


No report to distribute.


Job finished at 2018-09-11 05:05:03.485-0500 (1,536,660,303,485)


Job time on distribution server after the report completed was 0.003 seconds


Total running time was 2.192 seconds


Total elapsed time (including the queue time) was 2.193 seconds

This message has been edited. Last edited by: FP Mod Chuck,

Hi Christa

Welcome to Focal Point. It is a great forum for getting answers to development questions.

Unfortunately there really isn't an error message shown in the log. You might want to put a -SET &ECHO=ALL; at the beginning of the fex and hopefully a more meaningful message will be displayed.

We've been told that due to code tightening that ReportCaster does not handle -PROMPT. If I remember right -PROMPT was originally part of the FOCUS mainframe section and not meant to be part of WebFOCUS was the reasoning.

Can change the -PROMPTs to use -SET or -TYPE and will work. So your example would look like this

-SET &CO=&CO.(<Company1,100>,<Company 2,200>).Enter the Company.;

-TYPE &CO.(<Company1,100>,<Company 2,200>).Enter the Company.

We typically use the -SET but I don't know if there is truly one better than the other.
On a side note with the -TYPE it will show the value in the message viewer so if there is no output could see what the value for the ampersand variable was when it ran. Can change the -TYPE to have the variable name if have several to know which is which like below.

-TYPE CO = &CO.(<Company1,100>,<Company 2,200>).Enter the Company.

Will show CO = 100 or CO = 200 based on which was selected instead of just a line with 100 or 200. If don't want any of the -TYPE information though can use the -SET.

I assume that you are passing in the parms that the -PROMT gets, if so, why don't you check if its a report caster job, and skip the -PROMPT.

I came up with a simple solution to keeping the -Prompts and letting the schedule run without error.

 
-IF &CO NE '' THEN GOTO SKIP_PROMPT;

-PROMPT &CO.(<Company 1,100>,<Company 2,200>).Enter the Company.
-PROMPT……………………………..more prompts
-PROMPT……………………………..more prompts
-PROMPT……………………………..more prompts
-PROMPT……………………………..more prompts

-SKIP_PROMPT;


 

The GOTO works since the schedule sends &CO=100 and a manual run has nothing in it.

I will have to try changing a few reports to -SET or -TYPE and see if that solves the issue to. I'm not a huge fan of 'goto' but it works

This message has been edited. Last edited by: ChristaC,

quote:

Originally posted by Waz:
I assume that you are passing in the parms that the -PROMT gets, if so, why don't you check if its a report caster job, and skip the -PROMPT.

Exactly! I figured it out yesterday afternoon.

quote:

You might want to put a -SET &ECHO=ALL; at the beginning of the fex and hopefully a more meaningful message will be displayed.

It never got far enough through the scheduler to show me anything. I had to guess until I figured out it was the -PROMPT.

Thanks for responding though

Can you update the title of this thread and add [SOLVED] or [CLOSED], so everyone knows there is a solution ?