Focal Point Banner


As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.

Join the TIBCO Community
TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.

  • From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
  • Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
  • Request access to the private WebFOCUS User Group (login required) to network with fellow members.

Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [Solved - Finally]&&KILL_RPC not working

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[Solved - Finally]&&KILL_RPC not working
 Login/Join
 
JOE
Platinum Member
posted
I have error notifications set up on my Report Caster reports to alert of any errors. I applied this piece of code I found on the documentation to stop notification emails to be sent when report has 0 records:

 

ENDSTYLE
END
-SET &&KILL_RPC = IF &RECORDS = 0 THEN 'Y' ELSE 'N';
-SET &&KILL_RPC_ERR = 'N';


Usually this report should not have any records but is used for checking dup logids. Records will appear when they occur. Not sure why I am receiving the notification emails when I followed the reference on the documentation? Any help would be appreciated.

Thanks!

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


WebFocus 7.7.02 WinXP
 
Posts: 236 | Registered: May 12, 2006Report This Post
MichaelBalle
Gold member
posted Hide Post
May be its the difference between "printed" and "retrieved":

&RECORDS Is the number of records retrieved in last answer set.
&LINES Is the number of lines printed in last answer set.

TABLE FILE CAR
SUM
DEALER_COST
RETAIL_COST
BY COUNTRY
ON TABLE HOLD AS MYHOLD2
END
-RUN

-TYPE number of records: >&RECORDS<
-TYPE number of lines: >&LINES<


WebFOCUS 7.6, 7.7
Windows, All Output formats
 
Posts: 90 | Location: Stuttgart | Registered: October 20, 2010Report This Post
j.gross
Virtuoso
posted Hide Post
quote:
...
END
-SET &&KILL_RPC = IF &RECORDS = 0 THEN 'Y' ELSE 'N';
...


Make that
...
END
-RUN
-SET &&KILL_RPC = IF &RECORDS EQ 0 THEN 'Y' ELSE 'N';
...
 
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005Report This Post
SWES
Platinum Member
posted Hide Post
JOE,

Please have a look at my previous post on this forum:

Post

Maybe it will help you forward.

SWES


WebFOCUS 8105m
Windows 7, All Outputs

Member of the Benelux Usergroup
 
Posts: 198 | Location: Amsterdam | Registered: August 24, 2011Report This Post
JOE
Platinum Member
posted Hide Post
Thanks for the repies. I tried J Gross's suggestion but still receiving the notification email? Just not sure why this is happening?


WebFocus 7.7.02 WinXP
 
Posts: 236 | Registered: May 12, 2006Report This Post
JRLewis
Gold member
posted Hide Post
I believe you need to use a pre-processing step to set &&KILL_RPC in order for it to work the way you want.

I have included a link to an article that describes &&KILL_RPC in more detail.

Note that a pre-processing step must reside on the reporting server (i.e. not MRE).

https://www.informationbuilder...elopers/reportcaster


WebFOCUS 8
 
Posts: 74 | Location: Gahanna, OH | Registered: September 22, 2009Report This Post
JOE
Platinum Member
posted Hide Post
Thanks JR, but I did what your link stated to do with the ERR = 'N'. Still getting report.


WebFocus 7.7.02 WinXP
 
Posts: 236 | Registered: May 12, 2006Report This Post
susannah
Expert
posted Hide Post
but did you put all this in a pre-processing condition via the reportcaster tool?
only works that way, not in the report fex itself.



In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID
 
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003Report This Post
JOE
Platinum Member
posted Hide Post
Thanks Susannah..Do have instructions on how to do that? Is this something the administrator will have to do?

Thanks,


WebFocus 7.7.02 WinXP
 
Posts: 236 | Registered: May 12, 2006Report This Post
JRLewis
Gold member
posted Hide Post
A pre-processing step is simply a fex. In the pre-processing fex, you run your query and set the &&KILL_RPC and &&KILL_RPC_ERR flags as you have indicated based on the value of &RECORDS. This fex must reside on the reporting server.

In Reportcaster, when setting up your task, you can also identify the above fex as a pre-processing step.

I would recommend checking the documentation on Reportcaster on the IBI Tech Support site.


WebFOCUS 8
 
Posts: 74 | Location: Gahanna, OH | Registered: September 22, 2009Report This Post
JOE
Platinum Member
posted Hide Post
Thanks! I got it to work. For those who are having the same problem, you have to create a simple (separate) fex with those kill variables. While creating your report caster job, you have to go the advanced procedures button and than add your pre-processing fex to kill the job. I was adding the pre processing fex as task 1..A little confusing until I was poking around.


WebFocus 7.7.02 WinXP
 
Posts: 236 | Registered: May 12, 2006Report This Post
susannah
Expert
posted Hide Post
I'm glad you got it to work; i am sorry not to have gotten back to you earlier, but i was locked in BobJ class for the last 3 days [somebody shoot me now, what an awful product!}



In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID
 
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003Report This Post
jgelona
Master
posted Hide Post
Joe, one thing you need to be aware of is that the pre-processing fex is only for the task it is associated with. For example, if you have a Report Caster job with 2 tasks and associate the pre-processing fex with the first task and the first task is killed, the second task will try to run. If you want the remaining tasks killed as well, you have to attach the pre-processing fex to all remaining tasks.

I have a NFR in for a new variable, &&KILL_RPCJOB, that will kill the whole job. At some point I was told it would be in WebFOCUS 8, but as of 8.0.07, it is not there.


In FOCUS since 1985. Prod WF 8.0.08 (z90/Suse Linux) DB (Oracle 11g), Self Serv, Report Caster, WebServer Intel/Linux.
 
Posts: 975 | Location: Oklahoma City | Registered: October 27, 2006Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [Solved - Finally]&&KILL_RPC not working

Copyright © 1996-2020 Information Builders