Global Phased Mode

This chapter includes the following topics:

Overview

Global Phased mode is used when you are reasonably certain that Control-M/Tape is functioning like the other tape management system. As a safety feature, this mode enables both Control-M/Tape and the other tape management system to be fully operational simultaneously.

Previously (in Global Test mode) Control-M/Tape operated in the background (meaning, it had no effect on production). In Global Phased mode, only operations that are allowed by both Control-M/Tape and the other tape management system are performed. Operations not consistent with either Control-M/Tape or the other tape management system are not performed and relevant messages are sent to the console or job log.

Media management features that do not affect compatibility of operations with the other tape management system should be tested in Global Phased mode. Changes that do affect compatibility (for example, Control-M/Tape duplicate volser support) should not be implemented while Control-M/Tape is operating in Global Phased mode.

Most of this chapter deals with preparation for the transfer of Control-M/Tape operations to Global Phased mode. The object of these preparations is to minimize discrepancies between the Control-M/Tape and the other tape management system. Features that do not affect compatibility (for example, alteration of MOUNT and KEEP messages) should be activated with the change to Global Phased mode. Advanced Control-M/Tape features (for example, Dynamic Data Set Stacking) should not be implemented until the transfer to Global Production mode.

Preparation

Installation Parameter Considerations

Most Control-M/Tape installation parameters (in the CTTPARM member) were set prior to activation of Control-M/Tape in Global Test mode. However, values specified for some of these parameters, listed in the following table, should be reconsidered before activation of Control-M/Tape in Global Phased mode.

For a more detailed description of these parameters, see the Control-M/Tape installation chapter in the INCONTROL for z/OS Installation Guide.

Table 7 Control-M/Tape Installation Parameters

Parameter

Description

CNGMSGID

Determines whether to modify IDs of MOUNT and/or KEEP messages. If any software products at your site reference the current message ID, you should update those products (for example, console automation products or automated tape libraries).

Changing a message ID using this parameter can be useful for verifying that Control-M/Tape is active.

DYNWTO

Determines whether to modify the text of MOUNT and/or KEEP messages (for example, to add the scratch pool name to mount messages). The MSGFMT parameter specifies the information that can be added to these messages.

LBLROUTC

Route code to the tape label printer. To test Control-M/Tape’s label printing capability, specify the route code that has been assigned to the console printer at your site.

To view the labels without actually printing them, specify a route code other than the route code of your current label printer. This causes the label information to be sent to the console. Below is a sample label as it would appear on the console:

Copy 
  +----+----1----+----2----+----3----+----4  
  | DSN: MY.DATASET                       |
  |                    EXPDT: 07/06/2001  |
  | VOLSER: 123450     SLNAM: 123450      |
  | BLKSIZE: 03120     LRECL: 00080       |
  | CDATE: 05/05/2000  CTIME: 11:30       |
  | CJOB: PRCOPY04     CUNIT: 0480        |
  +----+----1----+----2----+----3----+----4

Control-M/Tape Exit 9 can be used to customize the format of tape label information. Exit 9 can also be used to direct tape labels to a sysout file that can be printed on any printer. For information about how to use this exit, see the CTTX009 member in the IOA SAMPEXIT library.

MODET

Control-M/Tape operation mode. To indicate that Control-M/Tape should operate in Global Phased mode, set MODET to PHASED.

MSGFMT

Information to be added to MOUNT and/or KEEP messages. Verify that the setting for this parameter suits the needs of your site.

NLASKOP

Specifies whether Control-M/Tape should ask the operator to confirm the volume serial numbers (volsers) of the NL and BLP tapes.

While operating in Global Test mode, Control-M/Tape treats the expression NLASKOP=Y the same way as NLASKOP=N. In Global Phased mode, this parameter can affect tape processing, and therefore should be reconsidered.

RBTTYPE

Automated tape libraries to be used. Only one system (either Control-M/Tape or the other tape management system) should manage the interface to the automated tape library.

  • If Control-M/Tape is to manage the automated tape library interface, specify the automated tape library types.

  • If the other tape management system is to manage the automated tape library interface, set this parameter to NONE.

TESTRULE

Specifies whether Control-M/Tape rules should be checked to see if they should be executed in Test mode when the Global operation mode is PHASED or PROD.

BMC recommends that you set the MODE parameter to PROD in all Control-M/Tape rule definitions. If MODE is set to TEST in a rule definition, the rule does not intervene in the decisions made by the existing tape management system, but it may update the Media Database. Therefore, you should also set TESTRULE to N.

Setting TESTRULE to Y may affect performance time of Control-M/Tape tasks, even if MODE is not set to TEST in any Control-M/Tape rules.

Reestablish Procedures

The Control-M/Tape New Day procedure (CTTDAY) performs various maintenance activities. Some of these activities (for example, statistics collection) may not have been relevant to Control-M/Tape in Global Test mode. If you commented out JCL steps for operation in Global Test mode, it is now necessary to remove the comment indicators (//*) so that these steps become operational in Global Phased mode.

Ensure that the Control-M/Tape New Day procedure is run at exactly the same time as the daily procedure of the other tape management system. Simultaneous generation of the reports by Control-M/Tape and the other tape management system helps guarantee that the information in those reports is consistent (meaning, both sets of reports represent the same media disposition).

Security Implementation

Before Control-M/Tape is started in PHASED mode, security definitions (for example, who is allowed to update Control-M/Tape rules, and who has access to the Online facility) should be specified.

Control-M/Tape security is implemented in two stages:

  1. Customize the Control-M/Tape interface with your security product. Detailed information on this stage is provided in the INCONTROL for z/OS Security Guide.

  2. Modify the Control-M/Tape Security exits so that they are compatible with your site configuration. The following Control-M/Tape security exits are provided:

    Table 8 Control-M/Tape Security Exits

    Exit

    Description

    CTTSE01

    Checks authorization for ordering Control-M/Tape rules. This exit also checks if a user is authorized to activate procedure CTTINIT (used for Control-M/Tape initialization).

    CTTSE03

    Checks authorization for file open requests and JCL parameters BLP and EXPDT=98000.

    CTTSE04

    Checks authorization for dynamic definition of volumes (tapes) and data sets in the Media Database.

    CTTSE06

    Checks authorization to update the Media Database through an online screen or a Control-M/Tape utility.

    CTTSE09

    Checks authorization to print a tape label.

    • For more information on Control-M/Tape security implementation, see the Control-M/Tape chapter in the INCONTROL for z/OS Security Guide.

Automated Tape Library Interfaces

An interface to the automated tape library at your site is typically initialized during Global Phased mode. Only one tape management system should control the automated tape library at any one time. For information about how to implement a Control-M/Tape automated tape library interface, see Automated Tape Library Interface and Virtual Tape Server

Operating in Global Phased Mode

When the steps described above in "Preparation" have been completed, it is time to activate Control-M/Tape in Global Phased mode.

  • If Control-M/Tape is already active and the Media Database is properly synchronized with the database of the other tape management system, you can simply change the value of the MODET parameter in the CTTPARM member and reload it. However, it is highly recommended that you reconvert tape management information from the other tape management system before activating Control-M/Tape in Global Phased mode.

  • If the Control-M/Tape Media Database is not synchronized and rules and parameters have been adjusted, reconvert the Media Database before activating Control-M/Tape in Global Phased mode.

Both tape management systems must be brought down (deactivated) before conversion is performed. For more information on the conversion of tape management, see the Control-M/Tape Conversion Guide.

Monitor Synchronization of Tape Management Databases

Before activating Control-M/Tape in Global Phased mode, the Media Database should already be synchronized with the database of the other tape management system. However, while in Global Phased mode, it is important to continue to monitor the Media Database to check that the information it contains is still consistent with the database of the tape management system being replaced by Control-M/Tape.

Media Database synchronization can be accomplished in a number of different ways.

Reports generated from the tape management system databases are compared (for example, scratch volume, and volume distribution information).

System and job log messages are monitored for messages regarding disagreement between Control-M/Tape and the other tape management system.

Synchronization of tape management database may also be affected by integrity problems in the Media Database. These problems can result from a system crash or a utility abend. The CTTIDB utility is run as part of the Control-M/Tape New Day procedure to verify integrity of the Media Database. For information about Media Database integrity errors, see Verifying Media Database Integrity.