You can code a WAIT on the ISFSLASH command. Options for slash (/) commands INTERNAL specifies that console ID 0 (INTERNAL) should be used to issue the command WAIT specifies that SDSF should wait the full delay interval before retrieving responses. This option is strongly recommended to ensure the responses are accessible in the ISFULOG special variable. The delay interval is specified with the ISFDELAY variable
-----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Elardus Engelbrecht Sent: Thursday, June 01, 2017 1:37 AM To: [email protected] Subject: Re: SDSF/REXX question Hardee, Chuck wrote: >I am having a random timing issue with a REXX that I am developing using SDSF >calls. >The REXX identifies the job name and number within which it is running and >then attempts to use SDSF to find and process the SYSOUT datasets already >created by previous steps in the job. >The REXX works most of the time, but sometimes when it runs, it fails to find >itself within the returned job list. >What I'm hoping to find out via this post is: >1) Does anyone know why there appears to be a delay in JES entering the >job's output into the queue? >2) Has anyone ever experienced this and, if so, what did you do to get >around this anomaly, if you did get around it? >3) If this is a timing issue, is anyone aware of a means by which I can >cause the REXX to delay a second or two before attempting to read the queue >entries for the job (name) being executed? Please post the parts where you call SDSF and how you're retrieving the data back from JES2 via SDSF. Also post the messages where it 'fails to find itself'. I have other questions to ask: Do you have timing issue when your system is busy and/or when the job is busy or spitting out large SYSOUTs? Priority (in WLM?) of your REXX or job may play a role? That "sleep" call solution others gave you, could help you out in the meantime. Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected]<mailto:[email protected]> with the message: INFO IBM-MAIN ________________________________ This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
