Skip to content

Setting up Global Parameters

Some of the settings in global parameters define the basic configuration for ChangeMan ZMF in your environment. Other parameters govern the action of users.

The application parameters that an administrators will set later can be more restrictive than the global parameters, but they cannot be more permissive. If you set global parameters to allow more options, application administrators can establish tighter control over sensitive applications while allowing other applications more latitude.

Note

The rules you define in global administration are not application specific—they affect all applications.

To set global parameters, execute the following steps to make entries on global parameters panels.

  1. On the Update Global Administration Options menu (CMNGAMN1), select 1 Parms. The Global Parameters Part 1 of 8 panel (CMNGGP01) is displayed.

    CMNGGP01              Global Parameters - Part 1 of 8 
Command ===> ____________________________________________________________ 

Subsystem: 2 

ChangeMan ZMF environment . . . . DP       (A/D/DP/P) 
Job entry system  . . . . . . . . JES2     (JES2 or JES3) 
Site node name  . . . . . . . . . S001      
Logical unit/system name  . . . . BUCKS  
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 . $CMNSUP
Default job scheduler . . . . . . CMN      (CMN, Manual, Other) 
Scheduler interval (CMN). . . . . 001      (Minutes) 

Enter "/" to select option
  / Allow CMN scheduler
  / Allow Manual scheduler  
  _ Allow Other scheduler

    The following table describes the fields of the Global Parameters Part 1 of 8 panel and the valid information that you can enter in the fields.

    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 from 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 Type the site node name you specified in ChangeMan ZMF Environment.
    A - (All) Environment: Type a common name or nickname for this ChangeMan ZMF instance. You cannot use the same name here that you will use for a site name in the Global Site List (=A.G.6).
    D - (Development) Environment: Type a common name or nickname for this ChangeMan ZMF instance. You cannot use the same name here that you will use for a site name in the Global Site List (=A.G.6).
    DP - (Development/Production) Environment: Type the Site Name for this ChangeMan ZMF instance defined in the Global Site List (=A.G.6).
    P - (Production) Environment: Type the Site Name defined in the Global Site List (=A.G.6) of the D or DP ChangeMan ZMF instance that installs to this P instance.
    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 started task will schedule the submission of package installation 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 performs a batch interface to add the package install job information to the external scheduler’s database.
    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 which scheduling systems can be definedwithin application and release administration to control submission of the package installation batch jobs.
    CMN - Allow CMN scheduler
    MANUAL - Allow Manual scheduler
    OTHER - Allow Other scheduler

    ...

  2. When you finish entering information on the Global Parameters Part 1 of 8 panel, press Enter. The Global Parameters Part 2 of 8 panel (CMNGGP02) is displayed.

    CMNGGP02            Global Parameters - Part 2 of 8 
Command ===> ________________________________________________________ 

Transmission vehicle . . . . . . IEBCOPY 
Normal business hours: from  . . 0001      (HHMM) 
                         to  . . 2300      (HHMM) 
Aging - installed packages . . . 180
      - staging datasets . . . . 180
      - component history. . . . 3660
      - staging versions . . . . 365
Allocation retry count . . . . . 5
Allocation retry wait  . . . . . 15 
Number of days in calendar . . . 364 
Store audit report . . . . . . . Y         (Y,N,D) 
Audit report library type  . . . LST 
Started procedures: 
Installation job build . . . . . CMN6ADSP 
Batch component build  . . . . . CMN6ADSP
Promotion JCL build  . . . . . . CMN6ADSP
Default  . . . . . . . . . . . . CMN6ADSP

    The following table describes the fields of the Global Parameters Part 2 of 8 panel and the valid information that you can enter in the fields.

    Field Description
    Transmission vehicle Type IEBCOPY for an A environment or for an initial implementation of a D or DP environment. In a D or DP environment, this field sets the value of ISPF variable TRNSTYP, which is referenced in JOB statement skeletons CMN$$JNM and CMN$$SJN to enable JES job routing statements. Enter the data transmission vehicle that ChangeMan ZMF is to use to transmit messages, change packages, and other data between the development system and the production sites. This variable will be used in file tailoring the install jobs.
    IEBCOPY - Exclude JES routing statements from installation JCL. Use if there are no other sites and DASD is shared between D and P environments.
    OTHER - Include JES routing statements in installation JCL. Other transmission vehicle: XCOM, BDT, etc. will require skeleton file tailoring of the install jobs.
    NOTE: This field no longer sets the transmission vehicle used in building installation job JCL.
    ● An ALL environment uses IEBCOPY by definition.
    ● In a D or DP environment, the transmission vehicle for each site is specified on the Site Information panel (CMNGRST2).
    Normal business hours Type a From and To time in 24-hour clock format (hhmm). Normal business hours determine whether an unplanned package is assigned the Planned Approval List or the Unplanned Approval list when the package is created. If you create an unplanned change package during normal business hours, the Planned Approval List is assigned to your package. If you create an unplanned package outside of normal business hours, the Unplanned Approval List is assigned. To force all unplanned packages to use the Unplanned Approval List, set normal business hours to a one minute range when it is unlikely anyone would create a change package. The settings for normal business hours in Global Administration restrict the entries for these parameters in Application Administration. Normal business hours at the application level must be the same as the global parameters or times that fall within the global time range.
    NOTE: Normal business hours are compared to the time you create your package, not the time that your package is frozen or the time that it is scheduled for install.
    Aging installed packages Type the number of calendar days after a package is installed (status BAS, INS, or TCC) that package records must be retained on the package master. After the specified number of days, package records may be archived or deleted by housekeeping. You may set the value between 0 to 9999. A value of zero (0) days turns off the package aging function, package records are never archived or deleted. The setting for this parameter in global administration restricts the setting in application administration. The application setting cannot be less than the global setting.
    NOTE: The days you specify for Aging - Installed Packages must be equal to greater than the days you specify for Aging - Staging Datasets. Staging data sets cannot be deleted if the package records have been archived or deleted.
    Aging staging datasets Type the number of calendar days after a package is installed (status BAS, INS, or TCC) you want to retain staging libraries. After the specified number of days, staging libraries may be deleted by housekeeping. You may set the value between 0 to 9999. A value of zero (0) days turns off the staging library aging function, and staging libraries are never deleted by housekeeping. The setting for this parameter in global administration restricts the setting in application administration. The application setting cannot be less than the global setting.
    NOTE: The days you specify for Aging - Staging Datasets must be equal to or less than the days you specify for Aging - Installed Packages. Staging data sets cannot be deleted if the package records have been archived or deleted.
    Aging component history Type the number of calendar days after a package is installed (status BAS, INS, or TCC) that component history for that package must be retained on the component master. After the specified number of days, component history records may be archived or deleted by housekeeping. Regardless of the value specified, the most recent history record for a baselined component in a library type in an application is preserved in component history to provide information for future build activity and for audit auto resolve. You may set the value between 0 to 9999.A value of zero (0) days turns off the component history aging function, and component records are never archived or deleted. The setting for this parameter in global administration restricts the setting in application administration. The application setting cannot be less than the global setting.
    NOTE: The value for Aging - Component History must be equal to or greater than the value for Aging - Installed Packages. Even if you specify an aging value for component history that is less than the aging value for installed packages, component history is not deleted or archived until package records are deleted or archived and the associated component history records are flagged with delete/archive status.
    Staging versions Enter the number of days that saved staging versions from a package should remain. The corresponding change package must be in BAS, INS or TCC status for this value to take effect. If the package is in Memo Delete status this value has no effect and the saved staging versions will be deleted regardless. A value of zero (0) for this field means that there will be unlimited staging versions (no aging) regardless of the value specified for package aging.
    CAUTION: specifying a value of zero (no aging) is not recommended due to the resulting potential for unlimited growth in the staging versions master files. Refer to Activity Log Housekeeping for guidance.
    Allocation retry count Enter the number of times to retry failed allocation attempts. The value can be from 0 to 65535. Failed allocation attempts are retried when package installation JCL is generated.
    Allocation retry waits Enter the time in seconds to wait between allocation retry attempts. The value can be from 0 to 65535 seconds.
    Number of days in calendar Enter the number of days you want the calendar to contain. The calendar will be created with the number of days you have specified. The value can be from 364 to 1820.
    Store audit report This value determines if the audit report generated by package audit is to be stored in the package staging library. This sets the default value to be used in application administration. Enter one of the following values.
    Y - Store the audit report.
    N - Do not store the audit report.
    D - Store the audit report only if the package is in DEV status.
    Audit report library type Enter the library type in which to store the audit report generated by package audit. The audit report is stored in compressed listing format. This sets the default value to be used in application administration.
    Started procedure - Installation job build Enter the name of the started procedure used to perform ISPF file tailoring to build the JCL used to install packages. The default name is CMNxADSP, where x is the ZMF subsystem ID.
    Started procedure - Batch component build Enter the name of the started procedure used to perform ISPF file tailoring to build the JCL used to checkout, compile, recompile and relink components. The default name is CMNxADSP, where x is the ZMF subsystem ID.
    Started procedure - Promotion JCL build Enter the name of the started procedure used to perform ISPF file tailoring to build the JCL used to promote and demote components. The default name is CMNxADSP, where x is the ZMF subsystem ID.
    Started procedure - Default Enter the name of the started procedure used to perform ISPF file tailoring to build the JCL used in cases not listed above. The default name is CMNxADSP, where x is the ZMF subsystem ID.

    ...

    Note

    The ChangeMan ZMF installer or global administrator must determine the names to be assigned to the four started procedures and define them to the security system before they can be used. Refer to the ChangeMan ZMF Installation Guide for details on setting up these procedures.

  3. When you finish entering information on the Global Parameters Part 2 of 8 panel, press Enter. The Global Parameters Part 3 of 8 panel (CMNGGP03) is displayed.

    CMNGGP03            Global Parameters - Part 3 of 8 
Command ________________________________________________________ ===> 

Enter "/" to select option   
  Baselines 
  /  Stacked Reverse Delta 
  _  Panvalet   
  _  User defined   
  _  Librarian   
  _  Librarian Access Method (LAM) 
  Notification Vehicles 
  /  Email   
  /  Batch 
  Other options
  /  Use primary Db2 subsystem for I/A: D10L
  _  Require Work request   
  _  Require Department   
  _  Disable installation calendar   
  /  Allow temporary packages   
  _  Process participating packages by install date   
  _  Hierarchical approval process   
  /  Use global notification file   
  /  Allow application update to file   
  _  Force display of global notification file   
Global notification file . . CMNTP.S7.NOTIFY

    The first five fields of the panel specify the storage means for back levels of Baseline libraries. Except for CA Panvalet and CA Librarian, the current level of any baseline library is configured as a PDS. The storage means for the back levels of each particular Baseline library are selected by the Application Administrator (under the Baseline option) based on the means allowed here.

    Note

    The Delta Deck storage means is obsolete for new baseline libraries. However, existing baselines with this storage means are supported.

    The following table describes the fields of the Global Parameter Part 3 of 8 panel and the valid information that you can enter in the fields.

    Field Description
    Stacked Reverse Delta Select to use the Stacked Reverse Delta Deck format. This storage means uses one PDS for the (0) level, and a second PDS for the (-001) thru (-999) levels. Back levels are stored in compressed form.
    Panvalet Select if earlier levels of Baseline are to be kept in PANVALET libraries.
    User defined Select if you will use ROSCOE or any other type of library organization. This will require file tailoring of install skeletons.
    Librarian If you have LIBRARIAN Masters, select this option.
    Librarian Access Method (LAM) Select if you have this method. LAM is only valid for release 3.6 or better.
    Notification vehicle - Email Select if you will use notification via email server. (CMN will send request via SMTP for email notification to user defined email server.)
    Notification vehicle - Batch Select if you will use notification via batch JCL submission. (CMN will build a job from skeleton CMN$$NTF and submit it).
    Use primary Db2 subsystem for I/A The default mechanism for hosting baseline Impact Analysis information uses a dataspace. If you would prefer to use Db2 then select this option (see the Installation Guide for more details).
    If you are licensed for the ZMF Db2 option then you set the default Db2 physical subsystem using the Db2 option admin facility as normal.
    If you are not licensed for the ZMF Db2 option then you can still use Db2 to host the I/A data, you can specify the target Db2 subsystem for the I/A tables on this line.
    Notification vehicle - Note This option is always available (MVS SEND). The notification vehicle(s) selected will determine how approvers receive notification of packages pending approval. Multiple notification options may be selected.
    Require Work Request Select if users will be required to enter a Work Request during package creation. (Work request may be required under the INFO MANAGEMENT CHANGE RULE). Omit if it is to be optional.
    Require Department Select if users will be required to enter Department during package creation. Omit if it is to be optional.
    Disable installation calendar Select to disable the installation calendar; or omit to utilize the full calendar checking function (scheduling install dates, aging of packages, etc). The calendar is defined under the BUILD options, selection 0 (DATES).
    Allow temporary packages Select to allow temporary change package creation. Temporary change packages are placed into production concatenated ahead of production libraries based on the amount of days you have specified. Omit to prevent user from creating temporary change packages.
    NOTE: Temporary packages are never baseline rippled into permanent production libraries; however they are deleted from the production environment after the number of days specified at package creation.
    Process participating packages by install date Select to process and audit participating packages within a Complex or Super package by installation date.Participating packages are processed as groups within a Complex or Super package based on installation dates. Only those participating packages defined to the Complex or Super package which have not been baselined and having installation dates that are equal to or earlier than the participating package containing the component to be compiled or link-edited are included as part of the SYSLIB concatenation. Audit will process participating package groups within a Complex or Super package based on the installation date of participating packages. The Audit process will report only on participating packages defined within a Complex or Super package which have an installation date equal to or less than the installation date of the participating package specified by the user for the execution of the audit job.
    Hierarchical approval process Select this option to send notification of packages pending approval based on the hierarchial approval list you have established. Notification is sent to each approver level as the package is approved. If omitted, all entities will be notified simultaneously.
    Use global notification file Select to activate the global notification file. Messages may be written to this file which serves as a broadcast facility to communicate information from the ChangeMan ZMF administrator to the user. Users are prompted there is an update when they enter a ChangeMan ZMF session and will be able to browse the file.
    Allow application update to file Select to allow Application Administrators to update the global notification file.
    Force display of global notification file Select to automatically display the global notification file if it has been updated since the user last browsed it. If not selected, users are prompted if the global notification file has been updated. The display or notification occurs when the user navigates to the ZMF primary option menu.

    ...

  4. When you finish entering information on the Global Parameters Part 4 of 8 panel, press Enter. The Global Parameters Part 4 of 8 panel (CMNGGP04) is displayed.

    CMNGGP04            Global Parameters - Part 4 of 8 
Command ===> ________________________________________________________ 

Audit level  . . . . . . . . . . . 0 (0,1,2,3,4,5) 
Unplanned package audit option . . 0 (0,1,2)
Checkout enforcement rule  . . . . 1 (1,2,3)
Staging restriction level  . . . . 1 (1,2,3)
Promotion/demotion rule  . . . . . 0 (0,1,2,3,4)
Enter "/" to select option 
  _  Disallow concurrent checkout
  /  Allow checkout to personal lib
  _  Eliminate save to personal lib
  /  Overlay prior staged module
  _  Validate version during staging
  _  Build install JCL at approve
  /  Use like-lod in syslib
  /  Use package syslib service
  _  Restrict deletion of complex/super packages
Validate ISPF libraries
  _  Ispllib
  _  Ispmlib
  _  Ispplib
  _  Ispslib

    This table describes the fields on the Global Parameters Part 4 of 8 panel.

    Field Description
    Audit level Type a one digit code that shows the Audit level that must be passed before a change package can be frozen. If the Audit Level is made more restrictive after a package is frozen, packages with audit return codes that do not comply with the new Audit Level setting must be reverted, corrected and re-frozen, before they can be approved.
    0 - Audit is recommended but not required.
    1 - Audit is required; however any return code (except ABEND) is acceptable.
    2 - Audit is required; the return code must not exceed 12, this implies there are "out-of-synch" conditions within the staging libraries.
    3 - Audit is required; the return code must not exceed 8 which implies there are no "out-of-synch" situations within the staging libraries, but there are "out-of-synch" situations within the Baseline libraries.
    4 - Audit is required; the return code must not exceed 43pauLine, this implies there are no "out-of-synch" situations within the staging libraries or the Baseline libraries, but at least one module of a staging library is a "duplicate" of its Baseline counterpart.
    5 - Audit is required and the return code must not exceed 0 which implies that there are no "out-of-synch" situations with either the staging libraries or the Baseline libraries, and no "duplicates" exist.
    Unplanned package audit option This numeric value dictates the unplanned package Audit option. This option enforces if an unplanned package must be audited.
    0 - Audit is recommended but entirely optional.
    1 - Audit is required; however any return code (except abend) is acceptable.
    2- Audit is required and must pass based on the Audit Level.
    Checkout enforcement rule Select this option to set checkout to staging enforcement rules. The numeric value entered dictates the rule that must be passed before a component may be staged. This setting allows you, as the administrator, to restrict who may stage components which have not been checked out from Baseline.
    NOTE: Checkout enforcement rules are for components that exist in the baseline libraries and are not for new components.
    1 - Users may stage any component, regardless if it has been checked out, to a package. ChangeMan ZMF will not check for the component's existence in the baseline libraries.
    2 - Users attempting to stage a component that exists in baseline but has not been checked out, must pass a security system ENTITY CHECK before the stage can proceed. The entity name is specified in the application parms generation. Staging will not be allowed if the user does not pass the entity check.
    3 - Users will not be allowed to stage a component which exists in the baseline library that has not been checked out to the package requesting the stage.
    Staging restriction level This regulates the Stage Development Driven option:
    1 - Allow all users access to both Development Driven (stage components into a package without checking them out) and Package Driven stage options.
    2 - Users are required to pass an entity check before being allowed to stage any components via the Stage Development Driven option. Only TSO-IDs associated with the ENTITY name are allowed to use both stage options. The entity name, which must be defined to your security system, is specified in Staging Restriction Level in the application parameters.
    3 - Users are required to CHECKOUT all components to a package before staging, effectively disabling the Stage - Development Driven option.
    Promotion/ demotion rule Determines how full and selective promote and demote work for all promotion sites and levels in the application. The setting for this parameter in Global Administration restricts Application Administration settings. An application setting cannot be numerically less than the global setting.
    Rules 1 thru 4 restrict promotion to Frozen (status FRZ) packages only:
    0 - Full and selective promote and demote are allowed without freezing the package first. Full promote can skip promotion levels. Requires the following sequence to change a promoted package component: Selective unfreeze (only if the package is frozen), edit, stage (restage), selective freeze of the component (only if the package is frozen), selective promotion to any level up to the package promotion level.
      NOTE: Because there is no requirement to demote a component before editing it, a component in the package staging library may not be the same as the component in a promotion library. This allows users to freely promote and demote components even if the change package has not been frozen.
    1 - Package must be frozen for promote and demote. Full promote cannot skip promotion levels. Requires the following sequence to change a promoted package component: Selective demote of the component, selective unfreeze, edit, stage, audit package, selective freeze of the component, selective promotion back to the package promotion level.
    2 - Package must be frozen for promote and demote. Full promote cannot skip promotion levels. Requires the following sequence to change a promoted package component: Selective demote of the component, selective unfreeze, edit, stage, audit package, selective freeze of the component, selective promotion through all intermediate levels to the package promotion level.
    3 - Package must be frozen for promote and demote. Full promote cannot skip promotion levels. Requires the following sequence to change a promoted package component:
    Full demote of the package, selective unfreeze of the component, edit, stage, audit package, selective freeze of the component, full promotion through all promotion levels up to the original promotion level.
    4 - Package must be frozen for promote and demote. Full promote cannot skip promotion levels.
    Requires the following sequence to change a promoted package component: Full demote of the package, revert the package to development status, edit, stage, audit package, freeze package, full promotion through all intermediate levels to the package promotion level.
    Disallow concurrent checkout Select to prevent users from checking out components that are part of a planned package.
    NOTE: This rule does not apply to unplanned packages. You can always check out a component into an unplanned package, even if the component is in another package and the Disallow concurrent checkout indicator has not been selected.
    Allow checkout to personal lib Select to allow users to check out to a personal library for editing. A copy of the component is kept in a staging library.
    If users edit components checked out to a personal library outside of ChangeMan ZMF, their changes are never automatically saved to package staging libraries.
    CAUTION! The use of personal libraries is discouraged with change packages, however customers using the ZMF for Eclipse product with RDZ. See field ’Eliminate save to personal lib’ below. If a user edits a package component directly in a personal library, their changes will not be promoted, audited, or installed if they forget to stage the member in the package. For this reason, the use of personal libraries is discouraged with change packages.
    Eliminate save to personal lib Select this option to restrict users from saving edited components to their personal libraries. This option determines how edited components are saved when a personal or development library is involved and the connection between those members. If a component is checked out to a personal lib, or staged from development, edits in staging will be performed on both the package's stage lib and the personal or development lib. After the first edit, changes are saved to both libraries regardless of this rule. Subsequent edits are saved in BOTH places if this rule is omitted.
    NOTE: Selecting this option breaks this connection, and edit changes are saved to the staging library only. If users edit components checked out to a personal library outside of ChangeMan ZMF, their changes are never automatically saved to package staging libraries. If you want users to be able to edit in a personal library, then set Allow Checkout to Personal Lib.
    CAUTION! If a user edits a package component directly in a personal library, their changes will not be promoted, audited, or installed if they forget to stage the member in the package. For this reason, the use of personal libraries with change packages is discouraged.
    Overlay prior staged module Determines whether a user can stage a component from development, and overlay a package component that is identified by another person’s userid. The compare is between the userid of the person attempting the checkout or stage from development and the userid that is stored in the package component record.
    If not selected enforces single ownership of a module in a package and stops other users from overlaying a previously staged module. This option will not be enforced against members that were checked out to the package in batch.
    Validate version during staging Ensures the integrity of baseline library components between checkout and staging. Users must check out components (not stage from development) for validation to be in effect. (See Staging Restriction Level). If the baseline version of a component has been altered after a user has checked it out, staging of that component will be prevented. Select to enforce validation.
    Build install JCL at approve Select this option to delay construction of the Package Installation JCL (often known as the 'x.node JCL') until the last approval takes place. Package Installation JCL is normally built each time the package is frozen.
    Use like-lod in syslib Select this option to include like-lod libraries as part of the in program (Binder) SYSLIB concatenations along with like-OBJ and like-NCL libraries. ChangeMan ZMF will always include Like-OBJ and Like-NCL as part of this concatenation.
    Use package syslib service ChangeMan has a traditional method of generating syslib concatenations for use in builds and referenced by audit. It is a rigid structure of staging, promotion, baseline libraries which must be consistent across builds and audit for accurate results. The package syslib service can be used to generate, and modify via HLL exit, the syslib concatenation. Use this admin option to force audit and build to use this alternative means of generating syslib concatenations. Note that, this added flexibility may cause audit to run more slowly. Also, if you change the syslib structure between the time you build components and when audit runs you will get audit errors.
    Restrict deletion of complex/super packages Select to prevent complex/super packages from being deleted if there are any attached packages. If this is not selected, a complex/super package can be deleted if its participating packages are in DEV, DEL, REJ, or BAK status.
    Validate ISPF libraries Select to activate the ISPF library and concatenation verification. Omit to bypass the ISPF library and concatenation verification. This verification ensures that the User's ISPF libraries and concatenations match those of the ChangeMan started task. This prevents a user from overriding the started task configuration. This function also verifies the ISPF library concatenation used in ChangeMan ZMF cataloged procedure CMNxJOBS. This prevents users from substituting a procedure with unauthorized libraries by using a JCLLIB statement in the JOB STATEMENT INFORMATION on ChangeMan ZMF panels that invoke the batch API.
    Ispllib Select to validate ISPF load library concatenation (data set names and order).
    Ispmlib Select to validate ISPF message library concatenation (data set names and order).
    Ispplib Select to validate ISPF panel library concatenation (data set names and order)
    Ispslib Select to validate ISPF skeleton library concatenation (data set names and order).

    ...

  5. When you finish entering information on the Global Parameters Part 4 of 8 panel, press Enter. The Global Parameters Part 5 of 8 panel (CMNGGP05) is displayed.

    CMNGGP05                Global Parameters - Part 5 of 8          
Command ===> ____________________________________________________

Audit package lock  . . . . OPTIONAL (Always/Never/Optional)                     

Enter "/" to select option                                      
  _  Job name increment override                                
  _  Use zprefix in batch jobs                                  
  _  Suppress msgs in dis/ins/bas jobs                          
  _  Create component work records                              
  _  Memo delete empty packages only                            
  /  Enable package user variables                              
  /  Enable component user variables                           
  _  Add user variables to package list table                     
  _  Allow component in multiple applications
  _  Allow component name in multiple applications
  _  Avoid audit reset when configuring participating packages               
  _  Auto scratch load member with source                       
  _  Run health checks                                          
Approval Restrictions                                         
  _  Package creator cannot approve                             
  _  Package worker cannot approve                              
  _  Only 1 approval per user
  _  Apply approval restrictions to unplanned packages

    This table describes the fields on the Global Parameters Part 5 of 8 panel.

    Field Description
    Audit package lock This value dictates whether a package is locked to prevent the contents being updated while the package is being audited. A setting of ALWAYS or NEVER for this parameter in global administration restricts application administration to the same value. Enter one of the following values:
    Always - Packages must be locked during audit.
    Never - Packages must not be locked during audit.
    Optional - Select if the application administrator for each application will determine whether or not packages are locked during audit.
    Job name increment override Select this option to prevent ChangeMan from incrementing the jobname suffix when submitting batch jobs. Under normal circumstances, ChangeMan will increment a jobname if it consists of the user id and a 1-character alpha suffix, A-Z. This ensures that multiple submissions get a different jobname for each job submitted. If jobs must single-thread, and a similar jobname is required for each submission, then this option should be used. Jobname suffixes 0-9, @, # and $ are not incremented.

    The jobname is incremented for the following types of jobs:
    • Package driven batch stage and build ('SB' and 'ST').
    • Component build ('S1').
    • Batch stage from development ('S1').
    • Stage from development component build ('S1').
    • Recompile ('RC').
    • Package promote ('PR' and 'PM').
    • Package demote ('DM').

    This option does not affect jobname suffix incrementing for mass build jobs initiated from Stage: Mass Build (panel CMNSTG05). The mass build panel provides an option to control jobname suffix incrementing.
    Use zprefix in Batch Jobs Select this setting to ensure ChangeMan ZMF will create a TSO profile using 'Profile prefix(&ZPREFIX) rather than 'Profile prefix(&ZUSER)' when it attaches a batch TSO session (during API functions such as checkout, freeze, stage).
    Setting this parameter in Global Administration restricts Application Administration settings.
    Refer to the IBM ISPF Dialog Developer's Guide and Reference for more information.
    Suppress msgs in dis/ins/bas jobs ChangeMan ZMF jobs that perform distribution, installation, baseline ripple, and back-out functions issue TSO SEND messages to inform you of success or failure. If you are distributing, installing, baselining, or backing out a large number of packages concurrently, the large number of TSO SEND messages can degrade system performance.
    This option enables you to suppress these TSO SEND messages only if a job is successful. If a job fails, you will always receive the TSO notification. Select this option to suppress the ChangeMan ZMF status notification messages issued by the distribution, install, and baseline jobs.This will suppress the messages that are normally sent to the broadcast log at completion of the individual job.
    Create component work records Select to enable the Component Work Record facility, which keeps a record of each userid that acted on a component in a change package. Actions which are recorded include checkout, stage, edit in stage, recompile, relink, and delete.
    Component work records can be accessed through the package list function. See also 'package worker cannot approve'.
    Memo delete empty packages only Determines whether change packages that contain components or utility requests (scratch or rename) can be memo deleted. There are two disadvantages to memo deleting packages that contain components:
    ● If the package is mistakenly memo deleted, work on the components is lost.
    ● Component history makes no distinction between components that were in packages that were installed and aged/deleted, and components that were in packages that were memo deleted and never installed.
    Select to prohibit memo delete if a package contains components or utility requests, requiring users to delete all components from a package before it is memo-deleted.
    Enable package user variables Select this option to allow users access to the package user variables during package lifecycle. This allows users to associate user data with a specific package and is used in conjunction with certain user exits, via a client interface or XML services.
    Enable component user variables Select this option to allow users access to the component user variables during the component lifecycle.
    This allows users to associate user data with a specific component and is used in conjunction with certain user exits, via a client interface or XML services.
    Add user variable to package list table Select this option to add package user data to the package list table. These variables are not used to build the displays in CMNLIST3 and CMNLIST4, but users do have the option to add them in place of existing fields.
    IMPORTANT NOTE: Adding these variables to the table will considerably increase the time to build the package list table, and is not recommended when large package lists are being built and displayed.
    Allow component in multiple applications Select this option to allow adding a component to packages across multiple applications.
    Allow component name in multiple applications Select this option to allow a component name and library type combination to be added to packages across multiple applications.
    Avoid audit reset when configuring participating packages Adding or removing participating packages to or from a complex group invalidates any audit which has been performed on non-baselined members of that group. Default behavior is to reset the audit return code on all relevant participating packages which are in DEV status.

    This option is available to allow administrators to retain compatibility with legacy behavior (not recommended).
    Auto scratch load member with source Select this option to automatically scratch associated load members when you scratch a source member. Additionally you will automatically scratch a source member when an associated load member is scratched. If this option is not selected, the user must manually scratch any associated load or source members.
    Run health checks Select this option to indicate whether supplied Health Check routines are eligible to be run against this ZMF subsystem.
    Approval restrictions The next three fields on this panel limit approval authority for planned packages, even though a user may be otherwise authorized to approve a package.
    Approval restrictions can be used to limit a user's approval authority within planned packages - even though they may otherwise be permitted to apply an approval to that package. Approval restrictions do not apply to unplanned approval lists.
    Package creator cannot approve Select to prevent the user who created the package from being part of the approval process.
    This parameter does not apply to unplanned packages.
    Package worker cannot approve Determines whether someone who has worked on a component in a planned package can approve that package, if they are otherwise authorized.
    Select to prevent a user, whose ID is associated with any of the package components, from taking part in the approval process. A user id is attached by each function (checkout, edit, stage etc.). This option will work in conjunction with the 'Create component work records option. With the option turned on, a history is maintained of each user's access to any component in the package. With the option turned off, only the last user id is stored.
    This parameter does not apply to unplanned packages.
    Only 1 approval per user Determines whether an approver can enter more than one approval for a planned package, even if they are otherwise authorized. Select to prohibit an approver from entering more than one approval for a planned package. If not selected, an approver is allowed to enter more than one approval. This parameter does not apply to unplanned packages.
    Apply approval restrictions to unplanned packages Apply the above three approval restrictions to unplanned packages.

    ...

  6. When you finish entering information on the Global Parameters Part 6 of 8 panel, press Enter. The Global Parameters Part 6 of 8 panel (CMNGGP06) is displayed.

    CMNGGP06          Global Parameters - Part 6 of 8
Command ===> ___________________________________________
Enter "/" to select option
    Enable display order
    _ Library types
    _ Languages
    _ Build procedures
    _ Reason codes
    _ Sites
    _ Db2 physical subsystems
    _ Db2 logical subsystems
    _ Online forms
    _ IMS control regions
    _ IMS DBD overrides
    _ IMS PSB overrides
    _ XML reports
    _ Applications
    _ 3D skeletons

    This table describes the fields on the Global Parameters Part 6 of 8 panel.

    Field Description
    Enable display order Select to activate the default display order defined in global administration. The default display order is defined by a display order number defined for items in global administration. If activated, this is used as the default order in which lists are displayed. Users can use the SORT command to sort lists by various columns. Users can use the 'SORT DEFAULT' command to sort lists by the administration defined default display order, if activated. If not activated, 'SORT DEFAULT' sorts by predefined columns. Some options may be unavailable due to unlicensed options.
    Library types
    Languages
    Build procedures
    Reason codes
    Sites
    Db2 physical subsystems
    Db2 logical subsystems
    Online forms
    IMS control regions
    IMS DBD overrides
    IMS PSB overrides
    XML reports
    Applications
    3D skeletons

    ...

  7. When you finish entering information on the Global Parameters Part 7 of 8 panel, press Enter. The Global Parameters Part 7 of 8 panel (CMNGGP07) is displayed.

    CMNGGP07                Global Parameters - Part 7 of 8                  
Command ===> _________________________________________________________________ 

Staging library model dataset names 
 Dev model dsname . . . CMNTP.S7.STGE.????.####### 
 Dev model zFS name . . /cmntp/c001/sert7/????/stge/#######            +   

   "????" is placeholder for application name.   
   "#######" is placeholder for package number (.#000123). 

 zFS temp folder  . . . /u/sert/Q001/tmp/s7                            +     

 Package master . . . . CMNTP.S7.CMNPMAST   
 Cpnt mstr (short) . . . CMNTP.S7.CMNCMPNT   
 Cpnt mstr (long) . . . CMNTP.S7.CMNCMPNL   
 Delay file . . . . . . CMNTP.S7.CMNDELAY 
 Ser#parm . . . . . . .   
 Impact analysis  . . . CMNTP.S7.IADSP   

 Email server . . . . . mail.mysite.com                                + 
       port . . . . . . 00025

    The table below describes the fields on the Global Parameters Part 7 of 8 panel.

    STAGING LIBRARY MODEL DATASET NAME Staging library data set names and zFS path names are created from a model by:

    • Replacing ???? with the application mnemonic
    • Replacing the last six # of ####### with the change package number

    • Appending a three-character library type to the end as a data set name node or a zFS subdirectory

      Notes

      • You must include the ???? and ####### nodes/directories in the model.
      • You may use the # character in other nodes/directories of the model.
      • Build your models so that they generate staging library names/paths that comply with your local standards.
      • Include the subsystem ID in the models if you will have multiple ChangeMan ZMF instances.
      • If you do not intend to manage Java components in ChangeMan ZMF, leave the zFS model names blank.
    Field Description
    Dev model dsname Enter the model dataset name for staging libraries in the development environment. Four question marks (????) in the dataset name will be replaced with the appropriate application mnemonic. Seven pound signs (#######) will be replaced with the change package number.
    Dev model zFS name Enter the model zFS directory for staging libraries in the development zFS environment. Four question marks (????) in the file name will be replaced with the appropriate application mnemonic. Seven pound signs (#######) will be replaced with the change package number.
    zFS temp folder The directory prefix where any zFS temporary files will be created by ChangeMan. These files are created when editing a file prior to staging back into the package, for example, and are cleaned up automatically.

    The SERNET started tasks running ChangeMan ZMF, File Tailoring started procedures initiated by ChangeMan ZMF, and users who access ChangeMan ZMF must have rights to create files in this folder.
    VSAM master file The Dataset name of the Package, Component, Delay, SER#PARM and Impact analysis files with which ChangeMan was started. (Display Only).
    Package master Displays the data set name of the package master for this ZMF instance.
    Cpnt mstr (short Displays the (short) data set name of the component master VSAM KSDS file for this ZMF instance. This file contains components with names of 8 characters or less (including zFS components).
    Cpnt mstr (long) Displays the (long) data set name of the component master VSAM KSDS file for this ZMF instance. This file contains components with names longer than 8 characters
    Delay file Displays the data set name of the delay file for this ZMF instance.
    Ser#parm Displays the reference table of application TCP/IP addresses and port numbers for this ZMF instance.
    Impact analysis Displays the data set name of the impact analysis LDS file for this ZMF instance (if using Db2 this is NULLFILE).
    Email server Enter the SMTP email server name (or IP address) for the EMAIL approval vehicle, if used. This is the email server name ChangeMan will use to find the email server used at your site. The port number is optional. If omitted, ChangeMan will use port number 25, which is the default for most email servers. NOTE: the email server name is used to determine the domain name for email addresses associated with the internal email system used at your site. The default domain name is considered to be the email server name minus the first 'node'. For instance, if the email server name is 'mail.mysite.com', then the default domain name would be 'mysite.com'. This domain name will be appended to any user names define with an EMAIL notification vehicle in the application approval definition which do not contain a fully qualified email address (i.e. the user name are not appended with '@xxxxx.xxx') Refer to the approval notification setup instructions in application administration. If you specify an IP address here rather than a server name, you cannot use default domain names in your approval lists.
    For the SERNET notification vehicle, you must specify an IP address and port number. The default domain name for approval email addresses is defined in the ECP configuration.
    EMAIL SERVER: mail.mysite.com
    PORT NUMBER: 00025
    (default domain name = mysite.com)
    Port Type the port number of the SMTP email server. If omitted, the port defaults to 00025.

    ...

  8. When you finish entering information on the Global Parameters Part 8 of 8 panel, press Enter. The Global Parameters Part 8 of 8 panel (CMNGGP08) is displayed.

    CMNGGP08              Global Parameters - Part 8 of 8 
Command ===> _________________________________________________________

Mobile app
 Http address . . . . . Q001.microfocus.com:8080 
 Https address  . . . . Q001.microfocus.com:8080                     + 
 Web context  . . . . . zmobile 
 ZMF server . . . . . . SERT7820

Job statement information: 
   //CMNSTART JOB , 'ACCOUNT INFO' 
   //             CLASS=A,MSGCLASS=X 
   //* JOBCARD from Global Parameters - Part 8 of 8
   //* 

   The job statements will be used when package installation jobs 
   are built at freeze time. The job name will change to reflect 
   package and install transaction numbers. Job statements can be 
   overridden at the Application Administration "PARMS" option and
   the Global Administration Db2 option.

    This table describes the fields on the Global Parameters Part 8 of 8 panel. Global parameters are generated after you press Enter.

    Field Description
    Http address Enter the address of the mobile app for the http protocol. This is the server where your web application manager (Tomcat or similar) is running, and the port it uses.
    Https address Enter the address of the mobile app for the https protocol. This is the server where your web application manager (Tomcat or similar) is running, and the port it uses.
    Web context Enter the context of the mobile app
    ZMF Server Enter the name of this ZMF server, as defined to the mobile app.
    Job statement information Enter standard JOB card information which will serve as a model when you create an application. Enter up to 4 lines of standard JOB card information. ChangeMan will overlay the JOB name you specify with the JOB name it submits for batch jobs.

    ...