Focal Point Banner
Community Center Education Summit Technical Support User Groups
Let's Get Social!

Facebook Twitter LinkedIn YouTube
Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [CASE-CLOSED] &&KILL_RPC not working in WF8103 ReportCaster
Go
New
Search
Notify
Tools
Reply
  
[CASE-CLOSED] &&KILL_RPC not working in WF8103 ReportCaster
 Login/Join
 
Platinum Member
posted
The reportcaster kill switch is not working. I have the pre-processing fex as

TABLE FILE CAR
PRINT DEALER_COST
WHERE COUNTRY EQ 'CHINA'
END

-TYPE LINES = &LINES

-SET &&KILL_RPC = IF &LINES GT 0 THEN 'N' ELSE 'Y';

-********************
-TYPE &&KILL_RPC
-********************


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 advance

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


WebFOCUS
7703/7705/8105m/8201m/8202m

 
Posts: 100 | Registered: September 10, 2013Reply With QuoteReport This Post
Virtuoso
posted Hide Post
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
 
Posts: 1213 | Location: Seattle, Washington - USA | Registered: October 22, 2007Reply With QuoteReport This Post
Platinum Member
posted Hide Post
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

 
Posts: 100 | Registered: September 10, 2013Reply With QuoteReport This Post
Guru
posted Hide Post
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
 
Posts: 406 | Location: India | Registered: June 13, 2013Reply With QuoteReport This Post
Platinum Member
posted Hide Post
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
 
Posts: 198 | Location: Amsterdam | Registered: August 24, 2011Reply With QuoteReport This Post
Platinum Member
posted Hide Post
@ 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

 
Posts: 100 | Registered: September 10, 2013Reply With QuoteReport This Post
Platinum Member
posted Hide Post
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
 
Posts: 198 | Location: Amsterdam | Registered: August 24, 2011Reply With QuoteReport This Post
Expert
posted Hide Post
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
 
Posts: 10577 | Location: Toronto, Ontario, Canada | Registered: April 27, 2005Reply With QuoteReport This Post
Platinum Member
posted Hide Post
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

 
Posts: 100 | Registered: September 10, 2013Reply With QuoteReport This Post
Platinum Member
posted Hide Post
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.

Thanks for responding to this post.


WebFOCUS
7703/7705/8105m/8201m/8202m

 
Posts: 100 | Registered: September 10, 2013Reply With QuoteReport This Post
  Powered by Social Strata  
 

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [CASE-CLOSED] &&KILL_RPC not working in WF8103 ReportCaster

Copyright © 1996-2018 Information Builders, leaders in enterprise business intelligence.