Event Notification Facility › Operation › Run CAIENF as a z/OS Subsystem

Run CAIENF as a z/OS Subsystem

Some CA products require initialization before JES and require CAIENF to run as a z/OS subsystem. For these products, you need to define CAIENF as a z/OS subsystem, which will become available at the next IPL.

Note: Running CAIENF as a subsystem reduces diagnostic capability. You should not run CAIENF as a subsystem unless there is a substantial benefit from doing so. As an alternative, you can use auto command. For example, to guarantee that CAIENF initializes before the beginning of batch job activity, you can define JES initiators as drained. Then, in the CAIENF auto commands member, you can use a $SI command to start the desired initiators.

To run CAIENF as a subsystem

1. Ensure that a copy of the CAW0PROC(ENF) member, updated to suit the requirements of your site, is in a system proclib and not in a proclib defined to JES. Pay particular attention to the following DD statements:
   • When running CAIENF as a z/OS subsystem, you cannot direct SYSPRINT to SYSOUT=*. You must specify a SYSPRINT DD DUMMY statement or, if you want the SYSPRINT output, direct SYSPRINT to a permanent data set.
   • If CAICCI is installed, a TRCPRINT DD statement is required. It has the same restrictions as SYSPRINT.

   Note: Subsystem names are restricted to four characters. If you rename the member, you must use a name that is not more than four bytes long.

   ENF is configured as a started task.

2. Ensure that all data sets accessed using the ENF procedure are cataloged in the master catalog.
3. Add the following control statement, starting in Column 1, to the active SYS1.PARMLIB(IEFSSNxx) member. Its position relative to other entries is not critical.

   ENF   CA‑Event Notification Facility
   

   Important! The subsystem name must match the name of the member in Step 1.

4. Use the START command to start ENF before JES at the next IPL.