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.
Simple thing ... trying to detect a focerrnum and branch to an error routine. Like a try ... catch.
But the branching is never run. Basically the fex stops completely when it encounters the error.
example below I am passing a bad date "A20140101" and getting the expected error
(FOC36355) INVALID TYPE OF ARGUMENT #1 FOR USER FUNCTION DATECVT
But My test never runs
-IF &FOCERRNUM NE 0 THEN GOTO DATE_ERROR;
So bottom line... how can I tell the fex to keep going when there is an error... I will handle it. I tried SET MESSAGE = OFF.
thx
Jodye
-SET &MYDATE='A20140101';
-SET &X= DATECVT(&MYDATE, 'I8YYMD', 'YYMD');
-IF &FOCERRNUM NE 0 THEN GOTO DATE_ERROR;
-RUN
-GOTO ALL_DONE;
-DATE_ERROR;
-TYPE BAD DATE
-ALL_DONE
-TYPE ALL DONE DATE IS &X
This message has been edited. Last edited by: <Kathryn Henning>,
Thanks guys. Yes that is what I am trying to catch. Nothing should totally stop processing like that. No matter what the error is in a function call, I expect to be able to catch it and continue. I opened a case...
Dialogue Manager does have this habit of stopping processing on an error. However, if this calculation were to be in a DEFINE or COMPUTE, it is expected that an error would be trapped. So how about:
-SET &MYDATE='A20140101';
DEFINE FUNCTION CHECK (INPUT/A10)
CHECK/YYMD = DATECVT(INPUT, 'A8YYMD', 'YYMD');
END
-RUN
-SET &X= CHECK(&MYDATE);
-IF &X EQ 0 THEN GOTO DATE_ERROR;
-GOTO ALL_DONE;
-DATE_ERROR;
-TYPE BAD DATE
-EXIT
-ALL_DONE
-TYPE ALL DONE DATE IS &X
-EXIT
Alan. WF 7.705/8.007
Posts: 1451 | Location: Portugal | Registered: February 07, 2007