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.
I am converting a large FOCUS application running on z/VM to run on z/OS. On VM, we frequently stack commands or calls to FOCEXECs in REXX programs, then call FOCUS. FOCUS reads from the program stack and runs the commands, FOCEXECs, etc. as if they were typed in at the keyboard.
I cannot get this to work on TSO. Jim Marrow posted that I need to allocate SYSIN for FOCUS to pull commands from the program stack. Does anyone have an example to doing this?
Any advice would be greatly appreciated. Thanks!
LarryThis message has been edited. Last edited by: Kerry,
How to test FOCUS after running ISETUP.
Case: 60492515 Product: FOCUS for S/390 Release: 7.6.10 Primary OS: z/OS Date: 10/03/19
Case information refers to the Product, Release, and OS for which this question was asked. The solution may apply to other Products, Releases, and Operating Systems.
Problem:
How to test FOCUS after running ISETUP.
Solution:
If you installed FOCUS correctly, you should be able to run CARTTEST focexec.
Here is sample JCL:
//CARTEST EXEC PGM=FOCUS,REGION=2048K
//STEPLIB DD DSN=prefix.FOCLIB.LOAD,DISP=SHR
//MASTER DD DSN=prefix.MASTER.DATA,DISP=SHR
//FOCEXEC DD DSN=prefix.FOCEXEC.DATA,DISP=SHR
//ERRORS DD DSN=prefix.ERRORS.DATA,DISP=SHR
//CCARS DD DSN=prefix.MASTER.DATA(CCARS),DISP=SHR
//CAR DD DSN=prefix.CAR.FOCUS,DISP=SHR
//SYSPRINT DD SYSOUT=*
//OFFLINE DD SYSOUT=*
//SYSIN DD *
EX CARTEST
FIN
/*
(My first reply to Focal Point so I hope I am doing this correctly....) We have used mainframe Focus for years on MVS - although we are now switching to WebFocus. If I understand your question correctly the example below may be of help. Two items I left in - we use procs in our JCL and the &tpremo and &cyy fields you see are resolved by our scheduling system. The file names of course have been changed.
//STEP1 EXEC FOCUS, // FDSN='FEX LIBRARY', // MDSN='DICTIONARY LIBRARY', // LINES= //OFFLINE DD SYSOUT=* //INFILE DD DSN=INPUT FILE,DISP=OLD //*COMMENT M0=MM, PREVIOUS MONTH, YR= CURRENT YEAR //** EX FEX3 MO=05, YR=05 //** EX FEX4 MO=05, YR=05 //** EX FEX5 MO=05, YR=05 //SYSIN DD * OFFLINE EX FEX1 EX FEX2 EX FEX3 MO=&TPREMO., YR=&CYY. EX FEX4 MO=&TPREMO., YR=&CYY. EX FEX5 MO=&TPREMO., YR=&CYY. FIN /*
Production: WebFocus 8.0.09 Test: WebFocus 8.0.09 Windows, Z-Linux, and ZOS. all output Focus - 7.2.7