Subject: SV: REXX IEBCOPY Continuation?
Hi
I havent had a problem with this
/* REXX */
"FREE F(INDD1)"
"FREE F(OUTDD1)"
"FREE F(SYSIN)"
"ALLOC FI(INDD1) DSN('x..aaa') SHR"
"ALLOC FI(OUTDD1) DSN('x..bbb') SHR"
"ALLOC FI(SYSIN) DSN('x..ccc') SHR"
"NEWSTACK"
V1 = " C I=((INDD1,R)),O=OUTDD1"
V2 = " SELECT MEMBER=((MSJT,,R))"
V3 = " SELECT MEMBER=((MSJTST1,,R))"
V4 = " SELECT MEMBER=((MSJTST2,,R))"
V5 = " SELECT MEMBER=((MSJTST7,,R))"
QUEUE V1
QUEUE V2
QUEUE V3
QUEUE V4
QUEUE V5
"EXECIO" QUEUED() "DISKW SYSIN (FINIS"
"TSOEXEC IEBCOPY"
"DELSTACK"
"FREE F(INDD1)"
"FREE F(OUTDD1)"
"FREE F(SYSIN)"
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Auto Reply: IBM-MAIN Digest - 21 Jul 2010 to 22 Jul 2010 (#2010-203)
I'm on vacation, I'll be back Monday the 2nd of August. - Mark -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
How to cancel with just the JES jobid?
>From an authorized assembler program, I've got just a JES jobid (JOBn) and need to cancel it. This needs to work with both JES2 and JES3. There are two possible ways to do this, z/OS cancel or JES cancel. Build a command and issue SVC 34. z/OS Cancel A z/OS cancel (C jobname,A=asid) would be easiest since it works for both JES2 and JES3, but since the jobname is used (not JES jobid), the jobname might not be unique and require the additional A=asid parameter. The jobname can be looked up from the JES jobid using the subsystem interface, but the asid is not available through this interface. I'm not sure how to start with JES jobid (JOBn) and get the asid, although I can get the jobname. Any ideas? I've hit a dead end with this one, without the asid, I can't do a z/OS cancel. JES Cancel JES2 and JES3 have completely different syntax for cancel, so I have to know which type I'm talking to. The CVT points to the JESCT (the main JES controlblock) which has a flag to test for JES2/JES3. That's not too hard. However, the JES2/JES3 commands are normally prefixed with $ (JES2) or * (JES3), but that is really just the subsystem command prefix and could be anything. I can't find the subsystem command character. It isn't in the JESCT or any obvious place. Any notion where that might be kept? Maybe it can be gotten through a subsystem interface call? Without knowing what command character is used for the primary JES, I can just default to $ for JES2 and * for JES3, but if a customer has changed that from the norm, it won't work. Any help on these issues or other approaches for cancelling jobs would be much appreciated. - Mark -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: How to cancel with just the JES jobid?
On Fri, 9 May 2008 13:06:08 -0700, Edward Jaffe <[EMAIL PROTECTED]> wrote: >Mark Jones wrote: >> >From an authorized assembler program, I've got just a JES jobid (JOBn) >> and need to cancel it. This needs to work with both JES2 and JES3. >> >> There are two possible ways to do this, z/OS cancel or JES cancel. Build a >> command and issue SVC 34. >> > >Are you able to use SSI function code 2 (CANCEL)? IEFSSCS has the SSOB >mapping. > Yes I guess, but it isn't documented in the "MVS Using the Subsystem Interface" manual. I could try to figure it out based on similar SSI calls, but would rather use a documented interface. I'll check into the SSOB mapping and see if I can figure it out. Thanks for the idea. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: How to cancel with just the JES jobid?
On Fri, 9 May 2008 23:14:56 -0500, Kenneth E Tomiak <[EMAIL PROTECTED]> wrote: >How is it you came to have a jobid and not know the jobname? Maybe instead >of fighting to find the name you can backtrack to what captured the jobid, it >must have had a jobname at that point too. > No. The assembler program writes JCL (from an MVS dataset or Unix System Services HFS file) to the internal reader, and retrieves the JES jobid from RPLRBAR. This interface does not give you the OS jobname, just JES jobid. But that's not a problem, SSI will return OS jobname for a given JES jobid, so I can get jobname. In the original post, I was trying how to find out the asid given a particular JES jobid (so I could do an OS cancel). An earlier port explained how to do that. Another post suggested using the undocumented SSI CANCEL (2), which is what I'm now leaning toward since it will cancel jobs stuck awaiting execution, where an OS cancel can only cancel a job that's running. >On Fri, 9 May 2008 14:34:39 -0500, Mark Jones <[EMAIL PROTECTED]> >wrote: > >>From an authorized assembler program, I've got just a JES jobid (JOBn) >>and need to cancel it. This needs to work with both JES2 and JES3. >> > >-- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO >Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
