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.
We have upgraded our systems which run FOCUS V7.1.1 from z/OS 1.8 to z/OS 1.10. One application cause an issue to uses because of the new logon screen We access FOCUS via an automated script, which at z/OS 1.8 works fine. At z/OS 1.10, however, the script exits its automated mode, and functions have to be executed manually. This is the following code works fine with z/OS 1.8 script: -* LAST ACCESS DATE FOCEXEC SET MESSAGE = OFF SET PAUSE = OFF EX FOCUSE EX LADUPD -RUN -QUIT FOCUS
This is the following scren displayed but this screen should go off automatically without manual intervention.
FOCUS 7.1.1 12/03/2009 07.41.27 1379.05 ***
When we call FOCUS there is a line display, which gives the version of FOCUS being called.
Within the script, under z/OS 1.8, this line display 'ENTER's automatically and the script proceeds. Under z/OS 1.10, a manual 'ENTER' is required to clear the line display, which aborts the automation. I thinks this is called by a different reaction to the 'SET PAUSE = OFF' statement.
Please help me.This message has been edited. Last edited by: Kerry,