Connecting Control-M for z/OS to Control-M/Enterprise Manager

Note: BMC recommends that, if possible, steps 1 to 4, described below, be performed before installation so that step 5 can be performed as part of the Express installation.

To connect Control-M for z/OS to Control-M/Enterprise Manager do the following:

1. Define all Control-M/EM user IDs as Control-M for z/OS user IDs, with the correct authorizations and files access rights. If a user ID name is longer than 8 characters, or needs a transformation, implement exit CTWX001 either using a table (such as sample CTWX001A) or by modifying the site's own exit.
2. Designate three ports for communication with Control-M. The three port numbers must include a pair of consecutive numbers together with a third additional number. None of these ports can be used by other applications.
3. Decide on a value for the STATACT parameter that is suitable for your organization. If a value of NONE is selected, Control-M/EM will only have display capabilities. If a value of MSG is selected, the Console Operation software will have to be configured to perform the required activities (Up / Down / Parameters / Commands). If a value of CMD is selected, Control-M will perform the actions itself, but it requires the relevant authorizations.
4. Ensure that all 3270 terminal end users who can update job scheduling definitions, can also update the job scheduling definitions through Control-M/EM, and the usage of table/folder is coordinated to avoid the necessity of manually resolving conflicts.
5. Build the IOAGATEC/CTMCAS and IOAGATEM/CTMAS procedures, and tailor the ECAPARMC and ECAPARMM members with the selected numbers, by doing one of the following:
   • In Express installation, specify the installed Control-M/EM and Control-M Configuration Manager and port numbers in the Short Parameters Data Entry screen.
   • If you have already completed the installation phase, then enter the INCONTROL Customization Engine (ICE) on the mainframe and do the following:
     1. Select Customization.
     2. Select the Environment.
     3. Specify Product IOA.
     4. Select Product Customization.
     5. Select major step 14 – ‘Install IOAGATE’.
     6. Select minor step 2 – ‘Configure IOAGATE parameters’.
     7. Select sub-options 0 thru 4, specifying ECAPARMM (for IOAGATEM) in option 0.
     8. Select sub-options 0 thru 4, specifying ECAPARMC (for IOAGATEC) in option 0.
     9. Return to the Install IOAGATE menu, and create IOAGATEM and IOAGATEC procedures as described in minor step 3 ‘Set Up IOAGATE Procedure(s)’.
6. Set STATACT using ICE, if either the CMD or MSG option was selected.

   Enter the INCONTROL Customization Engine (ICE) on the mainframe and do the following:

   1. Select Customization.
   2. Select the Environment.
   3. Change the Product to CTM.
   4. Select Product Customization.
   5. Select major step 3 - 'Specify additional CONTROL-M Parameters'.
   6. Select minor step 2 – 'Customize CONTROL-M/CM App. Server parm.'.
   7. Change the value of STATACT to desired value (CMD or MSG).
7. Set the IOAGATEC/IOAGATEM procedures to be active at all times.
8. Ensure either CMEM or Control-O are active at all times.
9. Using ICE, coordinate the values used for the Control-M/EM History retention with the Control-M for z/OS History Jobs file retention and ensure that the IOALOG size is large enough to hold the required number of days or generations.

   Enter the INCONTROL Customization Engine (ICE) on the mainframe and do the following:

   1. Select Customization.
   2. Select the Environment.
   3. Specify Product IOA.
   4. Select Product Customization.
   5. Select the following options:
      • Major step 2 - 'Customize IOA Dataset Parameters'.
      • Minor step 2 - 'IOA Log File Space Calculation'.
      • Minor step 9 - 'Format IOA LOG File'.
      • Minor step 17 - 'Format the IOALOG index file'.
      • Minor step 18 - 'Reload the IOALOG index file'.
10. Activate the IOALOG Index facility to eliminate delays when accessing the LOG from Control-M/EM.
11. Configure DVIPA if there is a need for an IOAGATE on multiple LPARs to be connected to Control-M/EM, where only one is active.
12. Populate SYNCLIBS, as described below.

    Types of job scheduling definition synchronization

    Synchronization of job definitions, Calendars, and Rule Based Calendars between the Control-M/Enterprise Manager Server and the Control-M/Server(s) occurs automatically, depending on the configuration settings of the data center definition on the Control-M/Enterprise Manager. There are four synchronization modes, as described in the following table:

    Mode	Description
    No Synchronization	No synchronization takes place between Control-M/EM and Control-M/Server. To synchronize manually, you can download the Control-M/Server data to Control-M/EM, upload the Control-M/EM data to Control-M/Servers, or create a regular calendar.
    Update Control-M/Server definition during Check-in	Synchronizes only Control-M/EM Workspace and Calendar changes with Control-M/Server during Check-in. Other Control-M/EM definition changes are not synchronized with Control-M/Server. Control-M/Server changes are not synchronized with Control-M/EM.
    Update Control-M/Server only	Synchronizes Control-M/EM changes with Control-M/Server. Control-M/Server changes are not synchronized with Control-M/EM.
    Update Control-M/Server and Control-M/EM	Synchronizes all Control-M/EM and Control-M/Server changes with each other, for full synchronization. Also known as two-way synchronization.

    Implementation of synchronization

    • For distributed systems components

      From the Control-M Configuration Manager, double click the Control-M Server definition and change the Synchronization mode to ‘Update Control-M/Server and Control-M/EM’.

      For further information, refer to the Control-M Administrator Guide.

    • For mainframe components

      CTMSYNC Userid

      The Control-M/Enterprise Manager uses a special user to request automatic synchronization between mainframe and Control-M/EM. By default, the user ID defined is CTMSYNC. This user must have authorization to access the libraries specified in the SYNCLIBS parameter member (see below). Note that CTMSYNC is the default user name which is customizable within the Control-M/EM system parameters. So if it changed, the new user name must be authorized as described.

      SYNCLIBS parameter member

      The purpose of SYNCLIBS is to define a list of table libraries that are automatically synchronized between Control-M and Control-M/Enterprise Manager. Whenever a table in one of these libraries is updated on the mainframe, Control-M/EM will automatically request downloading that table/folder to the Control-M/EM database so that it is synchronized with Control-M. To support such synchronization of table libraries, two-way synchronization must be enabled.

      In each row in the SYNCLIBS member, specify the name of a library in columns 1-72. Do not include any additional text (such as comments).

      It is recommended that all scheduling libraries be added to this member. This can be performed by doing one of the following:

      • Directly edit the (SYNCLIBS) dataset.
      • Enter the INCONTROL Customization Engine (ICE) on the mainframe and do the following:

           a. Select Customization.

           b. Select the Environment.

           c. Change the Product to CTM.

           d. Select Product Customization.

           e. Select major step 3 - 'Specify additional CONTROL-M Parameters'.

           f. Select minor step 3 – 'Update Member SYNCLIBS'.

           g. Add Scheduling libraries.

           h. Exit ICE.

      Note: If you remove a library from the list in the SYNCLIBS member, the library’s tables are not automatically deleted in Control-M/EM. If you do not want the library’s tables to appear in Control-M/EM, you can delete them manually through the Planning Domain in Control-M/EM. This will delete the tables also from the table library (due to two-way synchronization). If you need the tables to remain in the library, you can back them up before deleting them in Control-M/EM, and restore them in the library after deleting.

13. Define the new Control-M for z/OS in Control-M Configuration Manager. It can be defined as managed (using the Discovery process) or non-managed, where all the details must be supplied during the definition. If the non-managed option is used, there is no need for the IOAGATEC/CTMCAS started tasks, but on the other hand many capabilities for managing Control-M for z/OS from Control-M Configuration Manager will not be available.
14. If the language you are using for Control-M for z/OS is other than English, you must define the EBCDIC code page for the appropriate language by setting the EBCDIC_cp Gateway parameter using Control-M Configuration Manager (CCM).

    The available values are documented in the Control-M Help in the “System parameters for Control-M/EM components” topic in the “Western European language configuration” sub-folder under the “Language and Customization” folder.