Skip to content


ChangeMan ZMF Application

User software project or domain being implemented. Named and defined by the application administrator; can be a mnemonic. User restrictions are set for it. Type in the exact name of the application in an application, or select from a list of applications by typing a pattern, or use masking.

Possible References: APPL, PROJECT, LOCAL

Change Package

A group of changes to user software. Three levels include simple, super/ complex, and participating. Made up of members of partitioned data sets such as JCL, source code, copybooks, and so on.

Compile Procedure

Used to process special components like source (SRC). Related to the language name of a component. Choose from a list of available procedures for a component by leaving the compile procedure field blank. (If there is only one compile procedure defined for a certain language, this field cannot be modified.)

Use compile procedures and options designated by your application administrator by typing a ?. The appropriate procedure and options are displayed in the other fields.



A single member of a change package; usually a member of a library that was brought into ChangeMan ZMF for modification.

Component Library Type

List of available library types set by the application administrator; can be a combination of reserved, like, or custom library types.

  • Reserved – component types internally defined

  • Like – components that act similar to ChangeMan ZMF reserved components

  • Custom – components designed for unique needs

Compile procedures may be designated for components and are associated with the language name associated with the component type.


Component Name

Name of the component selected from a list of components (you may need to provide some qualifying information for the list, such as a library type or application name), or type a pattern (signified by *, following the relevant portion of the application name) or a blank in the component name field.

Possible References: COMPONENT, MEMBER, MODULE

Component Version (VV.MM)

Component version and modification number using IBM standards (mm starts at 01, increments to 99 and stays there; vv starts at 01, increments to 99 and then recycles to 01). The first time the component is processed by ChangeMan ZMF, the is 01.01. Each successive stage request (in the same change package) increments the mm portion (01.02, 01.03, and so on.). The next package that uses the component causes the vv portion to be incremented (02.01).

Confirmation Requests

Tell ChangeMan ZMF whether or not major operations prompt before running the function.

  • YES – a confirmation is required when overlaying a target file when running checkout.

  • NO – the function should be run without a user confirmation.

An all-or-none parameter. Cannot require confirmation for some packages and components and not for others.

Data Set Organization (DSORG)

A library type of organization:

  • PDS – partitioned data set (Basic Partitioned Access Method {BPAM})

  • SEQ – sequential file (Queued Sequential Access Method {QSAM})

  • PAN – CA Panvalet library

  • LIB – CA Librarian master

  • OTHER – any other type of library organization

Not a required field; if left blank, ChangeMan ZMF determines the DSORG.

Possible References: ORGANIZATION, DSORG


TSO USERID that performed a function.

Possible References: TSOID, USERID

Install Job Scheduler

Controls the submission of the package installation batch jobs. The choice of installation scheduler is controlled by the global administrator. This field may also contain a default value if the administrator set the value when setting up ChangeMan ZMF.

The global administrator sets these parameters in part 1 of the Global Parameters Panels (CMNGGP01).

Change this field by typing in the scheduler of choice, if it has been authorized by global administration:

  • CMN – ChangeMan ZMF internal scheduling.

    The ChangeMan ZMF started task schedules the submission of the package installation jobs. See the ChangeMan ZMF Administrator Guide for details on these capabilities.

  • MANUAL – Manually control the submission of installation jobs.

    The installation process begins as soon as the package is fully approved. Package installation can be inhibited by holding the last approval or installed immediately by approving the package before the scheduled installation date and time.

  • OTHER – An external scheduler such as CA7, ADC2, CA-Scheduler, Control- M, and so on.

    The ChangeMan ZMF started task performs a batch interface to add the package install job information to the external scheduler’s database.

Install Date

Date on which to install your change package.

Language Name (Language Assumption)

Programming language associated with a component that requires special processing such as the source (SRC) component. Language name is associated with each language and is customized predefined compile procedures.

Important when performing checkout or stage of components.

ChangeMan ZMF lets you choose a language (from a list of available ones) or use the one that the administrator designated. Type the language in the Checkout panel.

If component is not new and has a checkout history, history records on the component characteristics were saved. ChangeMan ZMF determines the language name of a component:

  • Designation – initiates Designated Procedures force option level 2

  • Specified – checks if a specified language name is used for the components

  • History – if history exists for the components

  • Designation – designated language for the component type

  • Last Used Language

ChangeMan ZMF uses the language of the first item in the list for all subsequent components in the list.

If procedure has force level 1, a user who wants to freeze a change package with the selected component, must perform the last stage request with the designated procedure. ChangeMan ZMF allows staging with alternate procedures during package development, but the final stage (before attempting to freeze) must be performed with the designated compile procedure for each component. If force level 2 is chosen, then a user who wants to stage the component must use the designated compile procedure. The application administrator may have used extra compile and/or link options.

See the ChangeMan ZMF Administrator Guide for Designated Procedures and Component Level Security.


An on-line function or a batch mode. In batch mode, ChangeMan prompts for batch job card information in an additional panel; only fill it in the first time unless there a change is necessary.

Possible References: ONLINE BROWSE.

Package ID or Name

ChangeMan ZMF assigns a unique ID, which is a combination of the application name and a unique number. Assigned IDs are needed to update or review the change package. When typing the package IDs, key in the application mnemonic, but truncate the number to only the relevant part:

  • CGM 000012 — rendered as CGM 12, or CGM 012, or CGM 00012, or as shown.

  • XYZV130056 — type it, as shown.

  • UHRD004061 — rendered UHRD4061, or UHRD04061, or as shown.

  • @13 045300 — rendered @13 45300, or as shown.

  • $B29000246 — rendered $B29246, or $B290246, or $B2900246, or as shown.

This field may be editable. Key in the change package name or access a list of change packages. At other times it is provided for reference.


Package Level

Change package levels in ChangeMan ZMF indicate the complexity and are designated when the package is created. Different levels have different behavior and creation requirements.

  • Simple – a component of a complex or a super change package.

    Does not affect any other application, or does not require changes to software or operational procedures.

  • Super and Complex – You are creating the “parent” change package for two or more change package applications that have related or interdependent changes, or have major changes to application processing which result in a major impact on the data processing environment.

    Super and complex change packages contain only control, general information, and a list of the participating packages. There are no staging libraries associated with super and complex change packages. Remote site and the installation dates for each site are tracked in the participating change packages.

    Once created, super or complex packages are automatically marked for limbo causing them to immediately display in the Monitor Packages in Limbo option. It is from this monitor function that their status is changed to closed.

    A super change package is functionally equivalent to a complex package. Use super to draw attention to, or segregate, packages.

  • Participating – A participating package is a variation of a simple package that allows an association to one or more additional participating packages. By using participating packages you can:

    • Account for other packages' copybooks or load module staging libraries during compile or link processing.

    • Combine the approvers of different applications (Not applicable to participating packages in the same application).

    • Participating change packages must be created before being listed as participating in the parent change package.

    Your package’s copybook and load module staging libraries are always concatenated before other participating packages in the SYSLIB DDNAME of compile/link steps. The order of the other packages is based upon the order of the packages listed in the complex packages.

Permanent or Temporary

A permanent change package is enduring and is deleted only if requested by a user. It can be rippled into the baseline library. A temporary package is not permanent and is never rippled into the baseline library. It is automatically deleted from production after a specified number of days.

Planned or Unplanned

A planned change package is created during normal business hours (defined in global parameters) in a non-emergency situation. Its implementation is subject to the complete Approval List. Its scheduling for installation is governed by the Planned Installation Calendar.

An unplanned change package is created for an emergency situation, often outside normal business hours. Its implementation is subject to the complete Approval List if it is created during normal business hours. If it is created outside of normal business hours, its approval is based on the abbreviated Approval List. Its installation date is not dependent on the Planned Installation Calendar. Data Set Organization (DSORG).

  • Use a planned permanent change package to schedule and install permanent updates to production software.

  • Use a planned temporary change package to set up and run special one- time or short-term processing (that is, conversion, parallel processing, special reports, or extractions).

  • Use an unplanned permanent change package to make emergency fixes to production software which must be executed for multiple cycles of processing.

  • Use an unplanned temporary change package to make short term or one- time-only emergency fixes to production software.

Remote Site

Use to indicate which remote sites are affected by a function. Provide remote site information when creating change packages and specifying where to install the package.