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 firstname.lastname@example.org for further assistance. Reference the community FAQ to learn more about the community.
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,
@ 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?
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...
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