On Thu, 4 Jan 2024 12:31:36 -0600, Paul Gorlinsky <[email protected]> wrote:
>On a z/OS 2.5 system using z System Automation V4.3, > >The event needs to issue a 'W L' then locate the SYSLOG output for that >specific LPAR, There are many ways to solve this problem and various considerations. >Where STC08984 is the result of parsing a JES2 $DS'SYSLOG' command > >LPR1 2024002 02:01:00:45 STC08984 $HASP890 JOB(SYSLOG) > > $HASP890 JOB(SYSLOG) > STATUS=(EXECUTING/LPR1),CLASS=STC, > $HASP890 > PRIORITY=15,SYSAFF=(LPR1),HOLD=(NONE) >LPR1 2024002 02:01:00:45 STC09720 $HASP890 JOB(SYSLOG) > > $HASP890 JOB(SYSLOG) > STATUS=(EXECUTING/LPR2),CLASS=STC, > $HASP890 > PRIORITY=15,SYSAFF=(LPR2),HOLD=(NONE) > >I have tried using a PIPE command without success... You never show the PIPE command nor how or why it failed. I can only guess as to why it failed. Possibility 1: Notice the indentation of the $DS output. This shows $DS writes multiple MLWTO's. Does PIPE only return the first MLWTO? Personally, I would issue D A,SYSLOG to get the jobid and forget using $DS. Possibility 2: You issue "W L" before the $DS. Maybe SYSLOG is one of the products that changes it's JOBID to free JES resources. The $DS picks up the wrong JOBID. Solution would be to issue $DS first. Possibility 3: "W L" does not complete before XWTR is started. > start an XWTR with job selection for class and JOBID... > >For example, >'S XWTR.XWTR,END=IEF176I' >'F XWTR.XWTR,CLASS=L,JOBID=STC08984' I suspect that "W L" command issues messages. XWTR should not be started before it completes. Is the JOBID available from those messages? You might consider TRAP & WAIT. Maybe an MPF exit for the messages. Maybe you could use a different class for each system and omit the jobid. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
