Jim McAlpine wrote: >We currently have an assembler routine which is called from CICS to check >whether a particular job is running in the same z/OS system as the CICS >system. This routine was written back in the dark ages and accomplishes this >by chasing the ASCB chain and comparing the jobname of each address space. 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.
AFAIK, There is NO easy way to do that across a SYSPLEX. Your 'checker' needs to run on the LPAR to do its check on that specific LPAR. I believe there is something in the CBT ... I just can't find it or used wrong search argument. What about RO *ALL,S <checker> or just /*JOBPARM SYSAFF=<sid> for each of your checking job(s)? Of course, it depends on how you pass on the fact that the job is actually running. Or you can have automation software submit something to all LPARS for checking? CONTROl-O has something like this: IF %%JOBSTAT <job> EQ ACTIVE (Check if active, if true, issue CANCEL) DO COMMAND = C <job> Or, if your job is using a dataset like SYS1.<sid>.blah.blah, you can scan for it using LISTDS (in REXX or CLIST) to check whether the dataset is defined and thus the job is actually running on a specific LPAR. One way I experimented in the past was, I tried out an ENQ ...,RET=TEST on a dataset (or just Alloc and use D GRS,C), I found out who and where is that dataset being kept hostage. Of course your job needs to use DISP=OLD or something like that. So many ways to skin a cat... (or shoot a Kudu or Springbok - in the head, neck or heart) Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
