Starting Your Product › How to Prepare for Deployment › Prepare the System Configuration File (L2OPTS)

Prepare the System Configuration File (L2OPTS)

The information in the System Configuration File, also known as sysfile, establishes the following information:

• Sets the location of the CA WA CA 7 Edition SMF indicator.
• Declares which SMF records are collected.
• States the CA WA CA 7 Edition SVC number and batch security options.
• Indicates other settings.

The HEALTHCHECK keyword controls the interface to the IBM Health Checker.

Note: For more information about the System Configuration File options, see the Systems Programming Guide.

Use the Master Preparation Checklist to complete your values. The CA WA CA 7 Edition Options library CAL2OPTN member AL2INIT creates the default sysfile. If the following default options are acceptable, use this AL2INIT member to initialize the CA WA CA 7 Edition system environment with one CA 7 tracking instance. To change the default settings or to use External Tracking Tables, NCF, or both, change this AL2INIT member. This sysfile information is saved as a sequential file or a PDS member with the DCB attributes of LRECL=80 and RECFM=F or FB. This sysfile information is used in the CAIRIM process (L2OPTS DD) to set up the CA 7 system environment.

Consider the following items for the System File:

• CA WA CA 7 Edition requires one SVC number; the default is 167. If you want to use a different number, identify an available type-3/4 number.
• The last byte of the 8-byte User Identification field in the SMF common exit parameter area is used. Verify that no conflict exists with the usage of this field. If a conflict exists, another byte must be selected. This conflict would occur in the reader time field and identified by the SMFO parameter.
• The RCA, restore common area, allows the record types for which the CA 7 indicator is to be removed from the reader time field. Identify the record types for which to perform this removal.
• Determine the SMF records for which information is passed to CA WA CA 7 Edition. You must have SMF record type 30. The SMF record type 26 is job purge. The data sets have three record types:
  • SMF type 14 is for data set opened for input.
  • SMF type 15 is for data sets that are opened for update or output. Collect this type if you are using data set requirements, triggering, or both.
  • SMF type 64 is for VSAM data sets.
• CA WA CA 7 Edition can use the IBM Health Check exits to monitor CA7ONL and ICOM status. This monitoring permits the issuing of messages when the IBM Health Checker Address space determines something is not right in the CA7ONL and ICOM address spaces. This monitor can be turned off (N), set to defer for later activation (0) or set to a number of minutes to monitor. The default if not coded: HEALTHCHECK(N) and default if coded: HEALTHCHECK(15).
• More options to enforce a security policy are BSUBCHK and SVDSNCHK. BSUBCHK(N) and SVDSNCHK(N) are the defaults for the CA71 ADD statement.
• Determine what CA 7 instances to install in the sysplex. You can define up to eight CA 7 instances, CA71 through CA78. You identify these instances at the CAIRIM initialization so that appropriate system level control blocks are built.

Note: For more information, see the Systems Programming Guide.