Install CA Datacom/AD › Customize CA Datacom/AD for CAIENF

Customize CA Datacom/AD for CAIENF

After installing CA Datacom/AD or deploying CA Datacom/AD on another LPAR image, you can optionally customize CA Datacom/AD for CAIENF.

If you want CAIENF to record events, you must have installed the version of CA Datacom/AD shipped with this version of CA Common Services and you must perform the steps in this procedure.

After completing the CA Datacom/AD installation, there are two CA Datacom/AD load libraries, CAAXLOAD and CUSLIB that are used to customize CA Datacom/AD for CAIENF and must be APF authorized.

CA Datacom/AD MUF Considerations

Important! Before you perform any CA Datacom/AD customization procedures for CAIENF, consider the following:

• A CA Datacom/AD Multi-User Facility (MUF) must be running on the system where the JCL associated with the procedure will execute.
• A CA Datacom/AD MUF can execute in its own address space or under the CAIENF address space.
• To customize CA Datacom/AD for CAIENF or resolve CA Datacom/AD for CAIENF customization issues, the CA Datacom/AD MUF must be running with its own address space and CAIENF must be down or started in a separate address space from the CA Datacom/AD MUF with the control option NODB.
• Save your Datacom/AD MUF startup JCL even if you decide to use an ENF internal MUF (see ENFIMUF below). There will be database maintenance occasions when you need to bring up the MUF while ENF is down.

Customize an Existing CA Datacom/AD for CAIENF

Important! Before starting this procedure read the section titled, CA Datacom/AD MUF Considerations.

To customize an existing CA Datacom/AD for CAIENF

If you already installed the release of CA Datacom/AD being shipped with this version of CA Common Services for z/OS from a prior version of CAIENF, then you will need to import this release's version of the CAIENF plan into your existing CA Datacom/AD environment.

Important! Do not perform the following until you are ready to implement this release's version of CAIENF.

1. Shutdown older version of CAIENF.
2. If not already started, start DATACOM/AD external to CAIENF.
3. IMPORT the New CAIENF plan into DATACOM/AD by editing and submitting CAW0JCL member AW1IMPRT.
4. IPL the system.
5. Start the new release of CAIENF.

Customize a New CA Datacom/AD for CAIENF

To customize a new CA Datacom/AD for CAIENF

1. Modify and submit member, AW1ID001 to install the CAIENF database definitions into CA Datacom/AD and allocate the CAIENF database data sets.
   • Specify CA Datacom/AD data set prefix
   • Specify CAIENF database data set volume
   • Specify the unit type for the volume specified
   • Specify space for the CAIENF database index, IXX700

     Approximate 3390 CYL Index space

     A = ( 30 x #total recorded events) /3036
     B = A + (A x .05)  / 12
     Cyls = (B  / 15) + 1
     

   • Specify space for the CAIENF database data area, ENF700

     Approximate 3390 CYL Area space

     Cyls = #total number of events / 3600
     Approximate 3380 CYL Area space
     Cyls = #total number of events / 3000
     

   Note: If AW1ID001 does not complete successfully, see Resolve CA Datacom/AD for CAIENF Customization Issues.

   If you are upgrading from CA Common Services r11, in order to obtain the total number of events count, your current running CA Common Services for z/OS ENF r11 can be used to help. Run the CAS9DB LIST DETAIL report shortly before your ARCHIVE (BACKUP) time, preferably the day after your three busiest days of the week. The LIST DETAIL report provides the total number of records that are currently recorded for each event type on the ENF r11 database. You can then simply add them up. The following is the CAS9DB LIST DETAIL JCL:

   //CAS9DB   EXEC PGM=CAS9DB,REGION=4M
   //DBOUT    DD SYSOUT=*
   //DBIN     DD *
     LIST DB(*) DETAIL
    /*
   

   Make sure ENF r11 is up and running to use the above JCL as is.

2. Update the CAIENF procedure.

   CAW0PROC contains three CAIENF procedures; ENF, ENFXMUF, and ENFIMUF. Select the procedure that applies to your site's requirements.

   ENF - Use the JCL found in this procedure when you do not wish to record events or install CA Datacom/AD.

   ENFXMUF - Use the JCL found in this procedure when you wish to record events. CA Datacom/AD is installed and the MUF is external (runs in its own address space) to ENF.

   ENFIMUF - Use the JCL found in this procedure when you wish to record events. CA Datacom/AD is installed and the MUF is internal (runs under the ENF address space) to ENF.

   For ENFXMUF and ENFIMUF:

   • Set the parameter values for ADSHLQ and ADHLQ to the CA Datacom/AD CAAXLOAD and CUSLIB data set name prefixes.
   • Update the ENF input parameters referenced by DD ENFPARMS to include control option statements RECORD(YES) and EVENT(event-name,RECORD). There should be an EVENT control option statement for each EVENT to be recorded.

     The Control Options that pertain to the recording of events are:

     NODB 
     RECORD(NO|YES)
     DCM(dcm-name)
     EVENT(event-name,RECORD)|
     EVENT(event-name,NOREC)
     

   • If the CA Datacom/AD MUF is to execute under the ENF address space, update the ENF input parameters referenced by DD ENFPARMS to include control option IMUF

     Note: For more information on these control options, see the Reference Guide and the Administration Guide.

3. Start or Re-start ENF.

   ENF dynamically creates EVENT tables to record events and ENF system tables to record miscellaneous supportive data.

   The EVENT tables are created when ENF initializes with RECORD(YES) specified.

   If RECORD(YES) is specified and the DATACOM/AD MUF is not available, ENF will shutdown.