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     [CLOSED] FOCERRNUM not capturing FOC198

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[CLOSED] FOCERRNUM not capturing FOC198
 Login/Join
 
Kamesh
Master
posted
Hi,

We are getting FOC198 error due to FOCSORT limitation issue. We are trying to capture that error to show some error message to user to limit their records. But when I add the code
-IF &FOCERRNUM NE 0 THEN GOTO PGM_ERR;

It is not getting passed to the routine. How can I capture the fatal error if FOCERRNUM is not working?

Thanks

This message has been edited. Last edited by: <Kathryn Henning>,


WFConsultant

WF 8105M on Win7/Tomcat
 
Posts: 780 | Location: Florida | Registered: January 09, 2005Report This Post
njsden
Virtuoso
posted Hide Post
It's strange that &FOCERRNUM is not capturing the last FOCERR being triggered. Did you add -RUN right before testing the variable?

In any case, you can also check the &IORETURN variable which has a value <> 0 when the last IO operation failed.

TABLE FILE ..
...
END
-RUN
-TYPE IORETURN  = &IORETURN
-TYPE FOCERRNUM = &FOCERRNUM


You can then control the error condition when either of those variables has a non-zero value.


Prod/Dev: WF Server 8008/Win 2008 - WF Client 8008/Win 2008 - Dev. Studio: 8008/Windows 7 - DBMS: Oracle 11g Rel 2
Test: Dev. Studio 8008 /Windows 7 (Local) Output:HTML, EXL2K.
 
Posts: 1533 | Registered: August 12, 2005Report This Post
Kamesh
Master
posted Hide Post
It is not getting in to that line at all. It breaks input the FOCSORT once it reaches the 2GB limit.


WFConsultant

WF 8105M on Win7/Tomcat
 
Posts: 780 | Location: Florida | Registered: January 09, 2005Report This Post
Ram Prasad E
Master
posted Hide Post
Are you using SQL Pass Thru or Master File retrieval? Looks like you bring large volume of data to WebFOCUS and perform sort operation.

If SQL Pass thru, then after SQLOUT hold file creation, you should get &IORETURN or &LINES.

If you are having this issue with Master File, then check view source to see if the Aggregation Done in the SQL created by WebFOCUS. Try TABLE FILE hold without any BY fields.

Hope this helps.

Thanks,
Ram


WebFOCUS 8.1.05
Windows
http://ibiwebfocus.wordpress.com
https://www.facebook.com/groups/ibi.webfocus/
 
Posts: 542 | Location: Dearborn, MI | Registered: June 03, 2009Report 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     [CLOSED] FOCERRNUM not capturing FOC198

Copyright © 1996-2020 Information Builders