The following sections describe the steps you need to take to successfully define CA Datacom/AD MUF for use with CAIENF:
Determine if you require a CA Datacom/AD MUF:
Follow these steps if your current release of Common Services is earlier than release 12.0:
Run CAS9DB LIST DB(*) DETAIL command on every LPAR that is running Common Services r11. See sample JCL below:
//CAS9DB EXEC PGM=CAS9DB,REGION=4M
//DBOUT DD SYSOUT=*
//DBIN DD *
LIST DB(*) DETAIL
Find the Defined CA-ENF Events within the report output and look for nn Records written.
For example (using a recorded event named JOBINIT:
jobinit - Batch JOB/Started Task/TSO Session Initiations
35 Records written
Options(A,R,P), Retention (1)
If no records have been written, you are likely not recording events
Follow these steps if your current release of Common Services is release 12.0 or greater:
Enter the following ENF modify command on every LPAR that is running CA Common Services:
Look for CAS9280I and CAS9282I messages and for the *RECORD* or *SELECT* entry within the CAS9280I message. See the following examples:
CAS9280I - EVENT(JOBFAIL ) STATUS(*ACTIVE) *RECORD* RP=2
CAS9282I - 00000001 EVENTS HAVE OCCURRED
CAS9280I - EVENT(STEPTERM) STATUS(*ACTIVE) *SELECT* RP=2
CAS9282I - 00000043 EVENTS HAVE OCCURRED
If events are NOT being recorded, you'll see a message similar to the following:
CAS9280I - Event(JOBINIT ) Status(*Active*) Norecord
If you determine that you are NOT recording events, you need not continue with this checklist as CA Datacom/AD is not required for this configuration.
If you ARE recording events, continue to the next section, Determine Size Requirements.
Determine Size Requirements
Before customizing a Datacom/AD database for ENF, you must first determine the size requirements for the ENF database (ENF700) and for the ENF Index (IXX700).
For Common Services releases prior to r12.0, use the reports from the CAS9DB LIST DB(*) DETAIL, as above, to obtain the total number of events being recorded.
For later releases, obtain the total number of events being recorded from the CAS9282I messages as illustrated above.
Total the number of all Records written for all events and follow the formula found in the CA Common Services for z/OS Product documentation listed in the Addtional Information, to determine the size of these datasets. The totals for each CAIENF system can vary, therefore, the size requirements can vary as well.
You will use these totals for executing job AW1ID001 discussed below, in Step 4 Customize CA Datacom/AD for CAIENF, Phase 3.
As an alternative to running the CAS9DB DETAIL Report or the totals from the CAS9282I messages, you may use 500 cylinders for IXX700 and 1500 cylinders for ENF700 datasets as a starting point and monitor usage for a representative work cycle and then run the a DBUTLTY job with the SYSIN:
Review the MAX % Full field to see the high water mark which delineates the space used by the data base and Index (IXX) area during the represented run cycle time. Then you can adjust the size at the next IPL/maintenance opportunity. Please note that this recommended starting point is a high estimate which is a better alternative to experiencing space issues with the ENF data and index areas later on.
Install Datacom/AD MUF for Use with ENF
If you are already running a CA product that requires CA Datacom/AD, verify that you are running Version 14.0 or 15.0. Review your currently running Datacom/AD started task and do a find on message DB00215I, see example below:
DB00215I - CA Datacom/DB r14 at service pack: SP0
If you find that you are running a supported level of Datacom/AD according to the CA Common Services documentation, then you can use the same SMP/E resources that already exist. If you want or need to create a separate SMP/E environment, refer to the appropriate CA Datacom/AD Product documention referenced below in the Addtional Information.
CAIENF requires a unique CA Datacom/AD MUF which is totally independent of the MUF(s) running to support other products such as CA Jobtrac and CA Scheduler.
Run the following CA Datacom/AD jobs to define the Multi-User Facility (MUF) for use with ENF. Refer to the appropriate CA Datacom/AD Product documention referenced below in the Addtional Information.
AXCUS00 - Copies the installation JCL from your existing CA Datacom/AD SMP/E CAAXSAMP members to the INSTJCL members.
AXCUS01 (r14.0) or AXCUSNEW (r15.0) - Performs CA Datacom product custom assemblies and links. This job creates a new CUSLIB, CUSMAC, CUSPROC for use by ENF. Do NOT use the same libraries and PROCs as you have with other environments running CA Datacom/AD.
MUF enflpar ,99,NO
1...........................column.......................................70-- (X continuation column 72)
./ ADD NAME=DBSIDPR
TITLE 'DATACOM/DB - SYSTEM ID BLOCK'
TARGET_MUF_LIST( enflpar ), X
NOTE: The CONNECT_ALLOW_PRIORITY =(LOCAL), specifies only local access, so the TOGROUP=ADXGRP01 is ignored.
AXNEW01 - Adds the JCLLIB members.
Customize CA Datacom/AD for CAIENF
Run ADxxSTRT (where xx = the Datacom release) to bring up the CA Datacom/AD MUF.
Modify and run job AW1ID001 provided for ENF in the CA Common Services CAW0JCL.
Phase 1 - Creates the Datacom/AD Datadictionary definitions for the ENF database, which is defined with DBID 700.
Phase 2 - Catalogs these definitions to the Datacom/AD CXX (Directory).
Phase 3 - Defines the ENF Datacom/AD datasets, initializes them and loads them.
Phase 4 - Imports the ENF PLAN definitions for use with the CA Datacom SQL component.
Run ADxxSTOP (where xx = the Datacom release) to shutdown the customized MUF.
If desired, update the CAIENF ENFPARM member to define an internal MUF or IMUF. As delivered, the CAW0OPTN ENFPARM member defaults to using an external MUF (i.e., XMUF).
Update the appropriate startup procedure found in your CA Common Services CAW0PROC library.
ENFIMUF - Use JCL in this member to run ENF as an internal MUF inside the ENF address space.
ENFXMUF - Use JCL in this member to run ENF as an external MUF which runs in its own address space external to ENF
Start or Restart ENF
If you have defined an IMUF, ENF will initialize the Datacom MUF at startup.
Conversely, an external MUF must be initialized and available prior to starting ENF. Use ADxxSTRT as a model.
NOTE: An IPL is required to start a new release of ENF if the previous release was already active since the last IPL.