I get the job name by chasing control blocks, sorry, it works. I am using ADDRESS SDSF
During my testing I, too, retrieved the output that I was writing from within my rexx. It didn't surprise me, but as I worked on the actual task at hand more I was able to get to identify the actual output I needed to look at. At this point, I'm close to solving the issue for which the rexx is being written, with the one exception that sometimes the test job runs and doesn't find itself. I'll try the sleep example you supplied to see it helps any. Thanks! C- Charles (Chuck) Hardee Senior Systems Engineer/Database Administration EAS Information Technology Thermo Fisher Scientific 300 Industry Drive | Pittsburgh, PA 15275 Phone +1 (724) 517-2633 | Mobile +1 (412) 877-2809 | FAX: +1 (412) 490-9230 [email protected] | www.thermofisher.com WORLDWIDE CONFIDENTIALITY NOTE: Dissemination, distribution or copying of this e-mail or the information herein by anyone other than the intended recipient, or an employee or agent of a system responsible for delivering the message to the intended recipient, is prohibited. If you are not the intended recipient, please inform the sender and delete all copies. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Paul Gilmartin Sent: Wednesday, May 31, 2017 10:26 PM To: [email protected] Subject: Re: SDSF/REXX question On Thu, 1 Jun 2017 02:24:43 +0000, 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. > I hope you're using the newer ADDRESS SDSF and not the older batch SDSF. >The REXX works most of the time, but sometimes when it runs, it fails to find >itself within the returned job list. > How do you get the jobname? I used ISPF calls. But that's because I'm loath to trace control blocks. >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? > Is it possible that QSAM buffering intervenes? But SDSF is quite good at chasing buffers to display the most recent output, at least on a terminal. >2) Has anyone ever experienced this and, if so, what did you do to get >around this anomaly, if you did get around it? > No. I've used Rexx SDSF to capture SYSTSPRT for the step in progress, tracing Rexx, and I've seen output right to the command that fetched itself. >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? > ADDRESS SYSCALL 'sleep 2' -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
