Skip to content

Setting Up Remote Sites Globally

The Global Administrator is responsible for creating, deleting, and updating remote site information for ChangeMan ZMF. This functionality is accessed from the Update Global Administration Options panel option 1 Parms.

  1. Set up multiple ChangeMan ZMF subsystems by designating one subsystem for your development site, and one for each remote site.

  2. Bring up the Remote Site ChangeMan ZMF instance.

  3. Set global parameters.

    CMNGGP01                  Global Parameters - Part 1 of 8 
    Command ===> _____________________________________________________________ 
    
    Subsystem: 7 
    ChangeMan ZMF environment . . . . DP     (A/D/DP/P) 
    Job entry system  . . . . . . . . JES2   (JES2 or JES3)  
    Site node name  . . . . . . . . . C001 
    Logical unit/system name  . . . . SYSA  
    Management class  . . . . . . . . ______ (Blank for default management class) 
    Storage class . . . . . . . . . . ______ (blank for default storage class) 
    Default unit name . . . . . . . . SYSDA 
    Default volume serial . . . . . . ______
    Default non-vio keyword=name  . . UNIT = SYSDA 
    ChangeMan ZMF security resource . $CMNDEV 
    Default job scheduler . . . . . . MANUAL (CMN, Manual, Other) 
    Scheduler interval (CMN)  . . . . 010    (Minutes)  
    
    Enter "/" to select option   
     / Allow CMN scheduler   
     / Allow Manual scheduler   
     / Allow Other scheduler
    

    ...

    The following table describes the fields on the Global Parameters Part 1 of 8 panel (CMNGGP01).

    Field Description
    Subsystem Displays the subsystem ID that you are currently logged on to.
    ChangeMan ZMF environment Type a one- or two-character code to determine the kind of ChangeMan ZMF instance you are configuring. CAUTION The environment type is set when you run program INITIAL2 to initialize the package master VSAM file for this ChangeMan ZMF instance. (See the ChangeMan ZMF Installation Guide.) Consult with Customer Support before you change the environment on this panel.
    A ALL - A single ChangeMan ZMF instance that manages development, maintains baseline libraries, and maintains production libraries that are on shared DASD and shared catalogs.
    D DEVELOPMENT - A ChangeMan ZMF instance that manages development and maintains baseline libraries, but does not maintain production libraries. A D environment sends package information to a separate P environment for installation into production libraries.
    DP DEVELOPMENT AND PRODUCTION - A ChangeMan ZMF instance that manages development, maintains baseline libraries, manages production libraries on shared DASD and shared catalogs, and can send package information to a separate P environment for installation into production libraries that are not on shared DASD with shared catalogs.
    P PRODUCTION - A stripped-down ChangeMan ZMF instance that receives change package information form a D or DP environment and installs package components into production libraries. No development is performed in a P environment. A P environment is required where production libraries reside on an MVS image that is separated from development and does not share DASD and catalogs with development. A P environment is also required if Db2 binds or IMS gens must be performed for install on an MVS image that is separate from development. **NOTE: If you define a new P site you must also define a calendar for that site.
    Job entry system Type the name of the job entry system (JES2 or JES3) used at your site.
    Site node name Define a unique Site Note Name for this Remote Site.
    Logical unit/system name Type the data transmission vehicle you will use in installation and promotion jobs for remote sites.
    ● Target name for your transmission vehicle (like SNODE for Connect:Direct®).
    ● For IEBCOPY enter the system name (e.g. 'SYSA').
    Management class Enter the management class for SMS managed dataset allocation. Leave blank for default class.
    Storage class Enter the storage class for SMS managed dataset allocation. Leave blank for default class.
    Default unit name Type the generic unit name for DASD to be used for dynamic allocations for this ChangeMan ZMF instance. This field may be left blank if DEFAULT VOLUME SERIAL is used. The Default Unit Name in Global Administration sets the Default Unit Name used when you create an application, but it can be changed at the application level.
    Default volume serial Type the DASD volume serial number to be used for dynamic allocations for this ChangeMan ZMF instance. This field may be left blank if DEFAULT UNIT NAME is used. The Default Volume Serial in Global Administration sets the Default Volume Serial used when you create an application, but it can be changed at the application level.
    Default non-VIO keyword=name For non-SMS managed devices: Enter 'UNIT' = and the generic unit name for disk packs that dynamic allocations requiring non-VIO DASD will utilize unless otherwise specified (e.g. 'SYSDA').
    For SMS managed devices:
    Enter 'STORCLAS' = and the generic SMS storage class name.
    NOTE: UNIT and STORCLAS are mutually exclusive.
    ChangeMan ZMF security resources Type the resource class defined in your security system for ChangeMan ZMF. The literal ’CMN’ is strongly recommended. See the ChangeMan ZMF Installation Guide.
    Default job scheduler Type the default scheduling system you will define to control submission of the package installation batch jobs within application and release administration.
    CMN The ChangeMan ZMF instance schedules the submission of package installation batch jobs.
    MANUAL The installation process begins as soon as the package is approved. This option allows you to install a package before its scheduled install date.
    OTHER ChangeMan ZMF invokes a batch interface to add the package install job information to the database for an external scheduler.
    Scheduler interval (CMN) Type the number of minutes (mmm) between checks by the internal ChangeMan ZMF scheduler for packages that have CMN scheduler type and are ready to be installed. The valid range is 1 to 255.
    Install job scheduler options Specify the scheduling systems you will define and allow within application and release administration to control submission of the package installation batch jobs.
    Allow CMN scheduler
    Allow Manual scheduler
    Allow Other scheduler

    ...

  4. Customize distribution and installation skeletons.

    Several skeletons are involved in the distribution and installation of packages to defined remote sites. Customize these skeletons in accordance with the data set names and transmission vehicles you are using at your site.