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 (JOBnnnnn) >>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
