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 co-worker and I are trying to figure out a way to prevent a mainframe job from abending when a certain FOCUS return code is encountered. The objective is for the job to test her access to a variety of datasets. So our question is this: How does one test the return code from the DYNAM command? The &FOCERRNUM and the &RETCODE don’t seem to work. Instead, JES2 does not return the error to FOCUS to be tested, and so the job simply abends with a JCL error. We'd like to capture the error, and continue testing access to the other DSN's. Thanks in advance for any wisdom you can share!This message has been edited. Last edited by: FP Mod Chuck,
I passed this post on to the FOCWIZARD in NY. DYNAM just points FOCUS to a dataset it doesn't actually access it. So in order to test it the user needs to actually try to run a report against the dataset once it is allocated. That said it is not clear what return codes you want to test for and what the JCL error is.
Thank you for using Focal Point!
Chuck Wolff - Focal Point Moderator WebFOCUS 7x and 8x, Windows, Linux All output Formats
Posts: 2127 | Location: Customer Support | Registered: April 12, 2005
I bet it's been 10 years since I actively developed on MVS. But - I have a thought for you to experiment with.
Read up on doing LISTDS from inside your Focexec.
It looks like LISTDS might be able to show you those security attributes if the database exists, and it will tell you if the dataset isn't there.
It's just a thought. If you using the Search option in FocalPoint and type in LISTDS, you'll get a few things. It might help to just experiment with it or google the subject to see if it would be of value to you.