The following is the task, that runs after the pre-processing step:
TABLE FILE CAR BY CAR END
Somehow, the reportcaster is not killing the job after the pre-processing stage and executing the later task. The following is the output and the source
PAGE 1 CAR ALFA ROMEO AUDI BMW DATSUN JAGUAR JENSEN MASERATI PEUGEOT TOYOTA TRIUMPH
TABLE FILE CAR PRINT DEALER_COST WHERE COUNTRY EQ 'CHINA' END -TYPE LINES = 0 LINES = 0 -SET &&KILL_RPC = IF 0 GT 0 THEN 'N' ELSE 'Y'; -******************** -TYPE Y Y -******************** TABLE FILE CAR BY CAR END
Am i missing any setting?
Thank you in advanceThis message has been edited. Last edited by: WF1326,
WebFOCUS 7703/7705/8105m/8201m/8202m
July 08, 2015, 03:34 PM
Dan Satchell
You must have a -RUN after the END statement of your TABLE FILE query in your pre-processing program. Otherwise &LINES will always be zero.
WebFOCUS 7.7.05
July 08, 2015, 03:44 PM
WF1326
It didn't matter. It supposed to kill the job for zero records, as -SET &&KILL_RPC='Y';
Instead its going to the later tasks
WebFOCUS 7703/7705/8105m/8201m/8202m
July 09, 2015, 02:33 AM
Rifaz
Document states, pre/post processing procedurs must reside on Reporting Server. Do you get any clues from log?
-Rifaz
WebFOCUS 7.7.x and 8.x
July 09, 2015, 04:04 AM
SWES
Hello WF1326,
Did you try to run the procedure without (!) the test in the SET parameter, so you first see if the SET works at all for you using:
-SET &&KILL_RPC = Y or -SET &&KILL_RPC = N;
If this works, then try to do the test separate (!) from the SET parameter:
-SET &OUTPUT = IF &LINES GT 0 THEN 'N' ELSE 'Y';
-SET &&KILL_RPC = &OUTPUT;
Another option is to bypass the SET by using the GOTO command.
-IF &LINES GT 0 THEN GOTO :NEXTSTEP;
-SET &&KILL_RPC = Y;
-:NEXTSTEP
Let me know if this works for you.
Best SWES
WebFOCUS 8105m Windows 7, All Outputs
Member of the Benelux Usergroup
July 09, 2015, 08:50 AM
WF1326
@ Rifaz : The pre-processing fex is on the reporting server. No clues from the log
@SWES: I tried your first two suggestions and it didn't work. Bypassing option could work, but we have to create new fex and use -include to run the next set of tasks based on the result of our condition.
I wonder if its a known issue. Do i have to open a case with ibi?
WebFOCUS 7703/7705/8105m/8201m/8202m
July 09, 2015, 09:31 AM
SWES
I never use(d) KILL_RPC in a pre-processing fex and therefore don't know if this is feasible.
Is there a possibility for you to do the test in the same procedure, or is there a specific reason you would need to?
WebFOCUS 8105m Windows 7, All Outputs
Member of the Benelux Usergroup
July 09, 2015, 09:40 AM
Francis Mariani
quote:
Do i have to open a case with ibi?
Yes you have to. How would they find out there might be a bug? If the code worked in one version and stopped working in another, IBI needs to know. Meanwhile, the best help you can get would be from IBI Tech Support - perhaps your issue is caused by an environment parameter, or it could be a bug...
Francis
Give me code, or give me retirement. In FOCUS since 1991
Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
July 09, 2015, 09:44 AM
WF1326
We could do test in the same fex.
The pre-process and KILL_RPC has been used in many our reportcaster jobs. It worked fine in v7.6.11, and with our migration to v8.1.03 things are not running as expected.
WebFOCUS 7703/7705/8105m/8201m/8202m
August 04, 2015, 10:18 AM
WF1326
IBI got back to me on this issue.
It seems like, this is a known issue in v8.1.03 and they resolved it in v8.1.05.
I need to workaround this issue, since we use 8.1.03.