For example, CA Jobtrac Job Management is running on system LPAR ISZ2. When a file on system LPAR ISZ1 is created (SHARED CATLOG), your job is not triggered on LPAR ISZ2. You have set up the following ADR definition:

-------------------------------------------------------------------------------
DSN: AISHR.TAD.ZC.G*                               CPU: ISZ2        ACT: RUN
TOD                CREATE    CREATE             TRIGGER        TRIGGER
THRESHOLD  EVENT      PROCESS PE     EVENT            PROCESS PE
DAILY             AIZUIMP        DAILY
-------------------------------------------------------------------------------

Release:
Component: JOBTRC

In order for ADR to work in a shared environment, consider the following. In the above case, there was not a monitor CA Jobtrac JM running on LPAR ISZ1 so the CPU definition in the ADR table is incorrect since the LPAR monitored is restricted to IZS2.

1. A monitor CA Jobtrac JM must be running on the system where data sets are to be monitored.
   
   
2. A definition in SYS1.Parmlib member SMFPRMxx for exit IEFU83 and SMF type 15 for non-VSAM and SMF type 64 for VSAM must be defined.