CA-ASM2 Support

Control-M/Tape and CA-ASM2 interface through CA-ASM2 Exit $FTEXIT (the Free Tape Exit). CA-ASM2 passes control to this exit before freeing a tape. In the sample for this exit supplied with Control-M/Tape (the AS2FTEXT member in the IOA SAMPLE library), the Control-M/Tape is called to expire the volume being freed (that is, to mark it SCRATCH in the Control-M/Tape Media Database).

Note: Control-M/Tape does not need to communicate with CA-ASM2 Exit $NTEXIT (New Tape). If Control-M/Tape is the only tape management product installed at your site, verify that NONE is specified for the &TAPEMGT parameter of this exit before it is compiled.

Use the following steps to activate the CA-ASM2 interface for Control-M/Tape:

1. Define all CA-ASM2 controlled tapes as belonging to specific tape pools of Control-M/Tape (meaning, Control-M/Tape pools in which all tapes are controlled by CA-ASM2).

   Definition of tape pools is not related to the value of the $TAPPOOL CA-ASM2 installation parameter. Tape pools must be defined for CA-ASM2 tapes regardless of whether CA-ASM2 tape pools are enabled. Pool definitions under Control-M/Tape ensure that only CA-ASM2 SCRATCH tapes are used by CA-ASM2 jobs.

2. If the $TAPPOOL parameter is equal to X'01' (meaning, CA-ASM2 tape pools are enabled), skip to Step 3 (below). Otherwise, define rules that instruct Control-M/Tape to use only tapes from these pools for data sets created by CA-ASM2.

   The data set names in the rules you define must be identical to those that appear in MOUNT messages for the relevant volumes. If you changed the "Dummy" data set name (written as the first file on each CA-ASM2 tape), use the new name in the rules as well.

3. Use the ICE Automatic Exit Installation Tool to compile the $FTEXIT member. For details about this tool, see the exits chapter of the INCONTROL for z/OS Administrator Guide. The $FTEXIT member is called by CA-ASM2 whenever a tape volume no longer contains valid data. The exit marks the volume as scratch in the Media Database and, optionally, interfaces with the automated tape library at the site.

   Figure 39 CA-ASM2 Calling Exit $FTEXIT

   

   If you are currently not using Exit $FTEXIT, continue with Step 4 below.

   If this exit is already in use at your site (that is, by another tape management system), use the following steps to integrate your current $FTEXIT exit with Control-M/Tape’s exit in Global Test and Global Phased modes. You should stop using your other product’s $FTEXIT exit when you first activate Control-M/Tape in Global Production mode.

   1. Rename the load module of the $FTEXIT exit currently in use at your site. You cannot have two different exits with the same name in your CA-ASM2 LOAD library.
   2. Change all occurrences of keyword $TMSEXT$ in the $FTEXIT sample member that is supplied with Control-M/Tape to the exit name you chose in Step A.
   3. "Uncomment" the lines marked *CALLEXIT by replacing the asterisk in the first column with a space.
   4. Run the ASMFTEXT job (described above).

   CA-ASM2 now calls the $FTEXIT exit supplied with Control-M/Tape that in turn calls the old $FTEXIT (that has been renamed).

   Figure 40 CA-ASM2 Calling Exit $FTEXIT Supplied with Control-M/Tape

   

   CA-ASM2 receives a return code from the exit that communicates with the old tape management system. (This exit was originally named $FTEXT.)

4. Verify that the IOA LOAD library is defined as one of the STEPLIB libraries or one of the system’s LINKLIST libraries.
5. Make sure that DO RETENTION=EDM statements are specified in rules for the data sets created by CA-ASM2. This statement indicates that the data sets indicated in the selection criteria of the rule are EDM-controlled. Job names, data set names, program names, or volsers can be used as selection criteria by the rules.