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.
MY suggestion is after any piece of code check &FOCERRNUM and if it is not 0, or one of the warning codes, then process the error. Just make sure you put a -RUN before the test.
In answer to your second question, there is no resume functionality. There is so much functionality that could be completely dependent on what previously may (or may not) have occurred that it ouwld never know whether or not it was safe to continue. For example, a specific piece of code that creates a hold file errors out. If that hold file is subsequently used, it cannot continue because the hold file does not exist.
I can see why this would be desirable , but given the way WF/FOCUS works, I believe there would be more occasion where a resume would not be possible than those where it could continue without further effect. Based on your Dialogue manager code and evaluation of &FOCERRNUM, you could manually overcome this - the key word being MANUALLY.
Regards,
Darin
In FOCUS since 1991 WF Server: 7.7.04 on Linux and Z/OS, ReportCaster, Self-Service, MRE, Java, Flex Data: DB2/UDB, Adabas, SQL Server Output: HTML,PDF,EXL2K/07, PS, AHTML, Flex WF Client: 77 on Linux w/Tomcat
Posts: 2298 | Location: Salt Lake City, Utah | Registered: February 02, 2007
Interesting that I can't INCLUDE a target label in another file.
I had thought INCLUDEd code was simply inserted into the body 'as is'.
I've tried (just for fun) INCLUDE-ing the ON TABLE HOLD part of a TABLE FILE request in a separate file and it worked fine. (Why anyone would want to do this, I don't know, but it worked fine !)
I'd think the label someplace else would not be a problem either, but it apparently is. Kinda puts the kebosh on what I was going to do.
Charlie, We use INCLUDEs here quite alot and one of them is the piece of code that has the ON TABLE HOLD, or in our case the last ON TABLE HOLD. This INCLUDE handles the output format and whether the report is returned to the screen or written somewhere.
As for the Error Checking, we will check the FOCERRNUM after each include/logical section of code for errors, and go to a section of the report that handles the error.