Advanced Topics › Control and Checkpoint File Considerations › How You Allocate Control and Checkpoint Files › How You Use XES Control Files

How You Use XES Control Files

After you have allocated coupling facility structure control files, you need to update the Coupling Facility Resource Management policy to define the names and attributes of the control file structures.

For detailed information on this process, see the IBM publication Setting Up A Sysplex.

• To determine the actual coupling facility resources available to the system, issue the following command:

  z/OS DISPLAY XCF,CF,CFNAME=ALL
  

• To determine the active CFRM couple data, issue the following command:

   z/OS DISPLAY XCF,COUPLE,TYPE=CFRM
  

• To determine the active CFRM policy, issue the following command:

  z/OS DISPLAY XCF,POLICY,TYPE=CFRM
  

You may need all of the information in the preceding displays to update the sample CFRM policy update job.

When defining structure control files in the CFRM policy, keep the following in mind:

• The primary structure control file should be at least 10 MB.
• The alternate structure control file should be slightly larger than the primary structure control file.
• The primary structure control file should not be allocated in the same coupling facility as the alternate structure control file.
• Structure control file names can be one to sixteen characters long. The first character must be alphabetic and the remaining characters can be alphanumeric or national (@, #, $) characters. CA MIM does not support the underscore ( _ ) character in structure control file names.

To add a policy for the coupling facility structure control files

1. Update the CFRM couple data set by customizing and running the sample JCL in the ALLOCSTR member of the CAI.CBTDJCL data set. Note that the JCL is a sample. You may need to refer to your active CFRM policy to be able to build a complete new CFRM policy that includes the CA MIM structure control files.
2. Define the coupling facility structure control files by place the appropriate ALLOCATE initialization statements in the MIMINIT member of the MIMPARMS data set.

For example, to specify the coupling facility structure control files defined in the preceding example, place the following ALLOCATE statements in the MIMINIT member:

ALLOCATE XESFILEID=00 STRNAME=MIMGR#TABLE00
ALLOCATE XESFILEID=01 STRNAME=MIMGR#TABLE01

If you already have DASD control files specified, and you want to add coupling facility control files in addition to the existing DASD control file, consider the following example placed in the MIMINIT member of the MIMPARMS data set:

ALLOCATE DDNAME=MIMTBL00 DSNAME=MIMGR.TABLE00
ALLOCATE DDNAME=MIMTBL01 DSNAME=MIMGR.TABLE01
ALLOCATE XESFILEID=02 STRNAME=MIMGR#TABLE00
ALLOCATE XESFILEID=03 STRNAME=MIMGR#TABLE01

Note: The MIMTBLnn value and the XESFILEIDnn value cannot be duplicated, because these values are used to identify specific control files in commands and messages during the operation of CA MIM. For this reason, any duplication of the file identifier nn is treated as an error.