Lizette,

You've quoted only part of the post. If you read the whole thing it is
obvious (to me at least) that it is a CICS program solution that is
required.


On Wed, Aug 6, 2014 at 2:19 PM, Lizette Koehler <[email protected]>
wrote:

> Jim,
>
> You inferred a CICS solution, you did not state it.
>     We now have the need to check to see if the job in question is running
> in any z/OS instance of a SYSPLEX. Any suggestions as to what is the best
> way to accomplish this.
>
>
> So you need a CICS solution.  If you have not done so, you might want to
> join and post on the CICS list
> To join:  https://listserv.uga.edu/cgi-bin/wa?A0=CICS-L
>
>
> Lizette
>
>
> > -----Original Message-----
> > From: IBM Mainframe Discussion List [mailto:[email protected]] On
> > Behalf Of Jim McAlpine
> > Sent: Wednesday, August 06, 2014 5:57 AM
> > To: [email protected]
> > Subject: Re: How to check if a job is running in a SYSPLEX
> >
> > On 6 Aug 2014 12:56, "Elardus Engelbrecht" <
> [email protected]>
> > wrote:
> > >
> > > Vernooij, CP (SPLXM) wrote:
> > >
> > > >Your JES2 MAS will probably cover your Sysplex, so you could ask JES2
> > > >if
> > the job is running (I don't know JES3).
> > >
> > > Good suggestion. With SDSF you can use SYSNAME * and then using ST
> > screen, sorting/filtering according to SAff, Queue, ASYS, etc, (or in DA
> screen you
> > could use SysName) you could see your job(s) when active/running. Above
> can be
> > done in batch too.
> > >
> > >
> >
> > As I said in my original post, I need to be able to do this from a CICS
> program. Is
> > there a JES2 API to accomplish what I want ?
> >
> > Jim Mc
> >
>
> ----------------------------------------------------------------------
> 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

Reply via email to