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] with the message: INFO IBM-MAIN
