Duh. This prints the jobname, not the jobid. But you get the idea :-) On Mon, Feb 27, 2012 at 2:15 PM, Kirk Wolf <k...@dovetail.com> wrote:
> This seems to work: > > /* REXX */ > NUMERIC DIGITS 24 ; > CVTPTR=STORAGE(10,4) /*CVT*/ > TCBW=STORAGE(D2X(C2D(CVTPTR)),4) > TCB=STORAGE(D2X(C2D(TCBW)+4),4) > TIOT=STORAGE(D2X(C2D(TCB)+12),4) > JBID=STORAGE(D2X(C2D(TIOT)),8) > JBID=STRIP(JBID) > SAY JBID > > > On Mon, Feb 27, 2012 at 2:04 PM, Kirk Wolf <k...@dovetail.com> wrote: > >> How about a simple REXX unix script that uses STORAGE to grab the jobid >> out of the SSIB? >> >> Kirk Wolf >> Dovetailed Technologies >> http://dovetail.com >> >> On Mon, Feb 27, 2012 at 10:20 AM, McKown, John < >> john.mck...@healthmarkets.com> wrote: >> >>> I was trying to write up a way to do something like that: fetching the >>> sysout from the currently running job into a disk dataset in a later step. >>> But ran into a problem in trying to find an IBM-supplied way to get the >>> running job's JES job number. I know how to write code to get it, but I >>> can't find a TSO or UNIX program to do it for me. I could then use Dovetail >>> Technologies' "Data Set Pipes" to get the sysout into a disk dataset >>> (fromdsn -jes.j????.stepname.procstep.ddname | todsn "//DD:ddname") in a >>> subsequent step. But I got frustrated in trying to find the current JES job >>> number. I would guess that somebody could use the SDSF/REXX interface to do >>> it. But I still don't see how to get the jobname/jobnumber which I need. >>> Using standard IBM programs, that is. >>> >>> -- >>> John McKown >>> Systems Engineer IV >>> IT >>> >>> Administrative Services Group >>> >>> HealthMarkets(r) >>> >>> 9151 Boulevard 26 * N. Richland Hills * TX 76010 >>> (817) 255-3225 phone * >>> john.mck...@healthmarkets.com * www.HealthMarkets.com >>> >>> Confidentiality Notice: This e-mail message may contain confidential or >>> proprietary information. If you are not the intended recipient, please >>> contact the sender by reply e-mail and destroy all copies of the original >>> message. HealthMarkets(r) is the brand name for products underwritten and >>> issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake >>> Life Insurance Company(r), Mid-West National Life Insurance Company of >>> TennesseeSM and The MEGA Life and Health Insurance Company.SM >>> >>> >>> >>> > -----Original Message----- >>> > From: IBM Mainframe Discussion List >>> > [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Paul Gilmartin >>> > Sent: Monday, February 27, 2012 10:15 AM >>> > To: IBM-MAIN@bama.ua.edu >>> > Subject: Re: Duplicating SYSOUT output to another DD/DSN in >>> > realtime ? (JCL) >>> > >>> > On Mon, 27 Feb 2012 08:02:36 -0600, McKown, John wrote: >>> > > >>> > >To the best of my knowledge, z/OS does not come with this >>> > functionality. You basically want the equivalent of the UNIX >>> > "tee" command. >>> > > >>> > With a Rube Goldberg Rexx wrapper you could use "tee", possibly >>> > under a BPXWUNIX task to write to SYSOUT and a data set concurrently. >>> > >>> > It might be more within your skill set to add an intervening step to >>> > use the Rexx SDSF interface to copy the SYSOUT from a previous >>> > step to a data set. In fact, at one point the Rexx SDSF interface >>> > allocates a DDNAME to the spool file -- you might be able to LINKMVS >>> > your postprocessor passing that DDNAME ln the alternate DDNAME >>> > list. >>> > >>> > -- gil >>> > >>> > ---------------------------------------------------------------------- >>> > For IBM-MAIN subscribe / signoff / archive access instructions, >>> > send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN >>> > >>> > >>> >>> ---------------------------------------------------------------------- >>> For IBM-MAIN subscribe / signoff / archive access instructions, >>> send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN >>> >> >> > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
