Can CA JMR collect joblogs from multiple LPARS using the same JES spool?
search cancel

Can CA JMR collect joblogs from multiple LPARS using the same JES spool?

book

Article ID: 14384

calendar_today

Updated On:

Products

JMR

Issue/Introduction

Utilizing CA JMR to spool output from the JES spool. Getting ready to startup a new LPAR and share all catalogs, dasd, and JES spool between the LPARs. Can CA JMR be setup to collect output from the shared spool from the additional LPAR? 



How does CA JMR spool output from a shared JES spool from multiple LPARS?

Environment

z/OSJES2

Resolution

To setup CA JMR to spool output you setup the CA JMR started tsk (STC) to collect all the correct output class definitions. If you are utilizing a "shared" spool then all the same rules apply regarding collection classes.

EXAMPLE from the startup proc provided in CAIPROC(CAPKJMR):

/CAPKJMR  PROC REG=1024K,                           
/         AUTOSTOP='N',                /*  MODIFY  */
/         CLASS='L',                   /*  MODIFY  */              ----->   You can stack the class designations

EXAMPLE with multiple designations:

//         CLASS='AHOZKSXB',             /*  MODIFY  */              ----> This example shows many output classes being spooled

Since the JES spool is being shared, CA JMR will not be able to determine that the output is coming from a different system. As long as the output class designations are correct in the startup proc all should be good.

In the ISPF panels when you are reviewing the output selected you will see what system the output was spooled from.

EXAMPLE

CMD Jobname   Jobno   Date      Time    System    Error          Highest 
                                                                       Cond Code

 BLAJO02V    6221  17/04/20  12:04:19  DE22   ABEND=S013                        ------> Notice the DE22 under the System label

BLAJO02O    6242  17/04/20  12:44:16  XE76    ABEND=S0C4                        -------> Notice the XE76 under the System label

 

You should remember that the output job class is the key to watch for when you start the CA JMR system within the multi-LPAR environment. 

 

Additional Information

Please read the CA JMR Getting Started Guide especially chapter 4 on Using Multiple CA JMRs