I am not sure if this will help, but there is a JES2 List that might be able to 
provide some guidance.

To join, if you have not done so, go here
http://listserv.vt.edu/cgi-bin/wa?A0=jes2-l

Lizette


> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]] On
> Behalf Of Leonardo Vaz
> Sent: Wednesday, September 02, 2015 8:06 AM
> To: [email protected]
> Subject: Re: JES2 - get system name without JCT addressability.
> 
> I knew I had to be missing something! Thank you very much John! "You're da 
> best!"
> I'll give it a shot!
> 
> Regards,
> Leonardo Vaz
> 
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]] On
> Behalf Of John McKown
> Sent: Wednesday, September 02, 2015 10:51 AM
> To: [email protected]
> Subject: Re: JES2 - get system name without JCT addressability.
> 
> $CBIO doesn't work? It has an input parameter of MTTR with it says is a SPOOL 
> TTR.
> ref: http://publibfp.dhe.ibm.com/epubs/pdf/has2q000.pdf
> <quote>
> MTTR= Specifies the label of, or a register that contains, the spool track 
> address of
> the record to be read or written. If you specify a register, the spool MTTR 
> (module
> track record) must be loaded into the designated register before executing 
> this
> macro instruction. MTTR is required for TYPE=READ or TYPE=WRITE, but is not
> allowed with TYPE=WAIT.
> </quote>
> 
> On Wed, Sep 2, 2015 at 9:29 AM, Leonardo Vaz <[email protected]> wrote:
> 
> > Thanks for the help guys! You understand my problem now, so from the
> > system I'm executing the command from It's not trivial to get the
> > system where the job is running, the easiest field I found is
> > JCTMVSNM, but JCT is probably not resident on the system I'm executing
> > the command from, I think that's why JQE points to the track on the
> > spool where I can find the JCT, but I still couldn't figure out how to read 
> > that track
> on the spool.
> >
> > It doesn't sound something extraordinary, but something rather simple,
> > but I've learned a while ago that assembler is rarely simple.
> >
> > Thanks and regards,
> > Leonardo Vaz
> >
> >
> > -----Original Message-----
> > From: IBM Mainframe Discussion List [mailto:[email protected]]
> > On Behalf Of Charles Mills
> > Sent: Tuesday, September 01, 2015 8:01 PM
> > To: [email protected]
> > Subject: Re: JES2 - get system name without JCT addressability.
> >
> > Ah. It seemed like too simple an answer; that's why I was kind of
> > tentative.
> > At least now I understand the problem.
> >
> > Could one determine "which member of the JES plex" somehow and then
> > have a table that mapped that "which" to the actual system name? Or
> > does this have to be more portable than that (such as for a vendor product)?
> >
> > Charles
> >
> > -----Original Message-----
> > From: IBM Mainframe Discussion List [mailto:[email protected]]
> > On Behalf Of J O Skip Robinson
> > Sent: Tuesday, September 01, 2015 4:49 PM
> > To: [email protected]
> > Subject: Re: JES2 - get system name without JCT addressability.
> >
> > I was going to reply similarly, but I then noticed that OP is talking
> > about a running job, not necessarily the current system. A job can be
> > running on any member of the JES plex. I don't have an easy answer for
> > that question.
> >
> > ----------------------------------------------------------------------
> > 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
> >
> 
> 
> 
> --
> 
> Schrodinger's backup: The condition of any backup is unknown until a restore 
> is
> attempted.
> 
> Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be.
> 
> He's about as useful as a wax frying pan.
> 
> 10 to the 12th power microphones = 1 Megaphone
> 
> Maranatha! <><
> John McKown
> 

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to