ChangeManUserGuide-Version5 (1) 1

CHANGE MAN
VERSION 5.1
USER GUIDE
JANUARY 2001
COPYRIGHT
This manual, as well as the software described in it, is furnished under license and may be used or copied only in accordance wi the terms th of such license. Except as permitted by such license, no part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording, or otherwise, without the prior written permission of SERENA Software, Inc. The content of this manual is furnished for informational use only, is subject to change without notice, and should not be const rued as a commitment by SERENA Software, Inc. SERENA Software, Inc. assumes no responsibility or liability for any errors or inaccuracies that may appear in this book. Copyright 2000 SERENA Software Inc. All rights reserved.
TRADEMARKS
Change Man, Comparex, StarTool, StarWarp, UltiMIS, ULTIMIZER, and Eye-Spy are registered trademarks of SERENA Software, Inc. Change Transfer, Detect+Resolve, Merge+Reconcile, FULL.CYCLE, SERNET, SERENA, ChangeContent, ChangeXpress, eChange Man, eHealing, eRequestMan, eFull.Cycle, StarProbe, StarSpy, StarTest, StarSuite, and Eye-Spy/390 are trademarks of SERENA Software, Inc. CA-Librarian and CA-Panvalet are registered trademarks of Computer Associates International, Inc. DB2, IMS, and ISPF are trademarks and registered trademarks of the International Business Machines Corporation (IBM). All other products or company names are used for identification purposes only, and may be trademarks of their respective owners. Publication Date: January 2001 Order Number: CMNUG51
CONTENTS
What is Change Man?

Features of Change Man Change Packages The Change Man Life Cycle Inside Change Man Development Create The Checkout Process The Staging Process Auditing Freezing Packages Promoting Packages and Components Approving Packages Installation Backing Up Backing Out Packages or Components Temporary Change Cycle Distribution to Remote Sites Distributing and Installing Components at Remote Sites Change Man Library Environment Checkout Impact Analysis Staging Audit Recompile and Relink Freeze Promotion Approve Production Installation Baseline Libraries and Delta Decks Backout Management Facilities Emergency Changes Storage Name Considerations 1-1 1-1 1-2 1-3 1-3 1-3 1-3 1-5 1-5 1-6 1-7 1-8 1-9 1-10 1-10 1-10 1-11 1-11 1-11 1-12 1-12 1-13 1-14 1-14 1-15 1-15 1-15 1-16 1-16 1-16 1-17
Contents
Accessing Change Man and Navigating Panels

Accessing the Primary Option Menu Accessing the Build Options Menu Navigating Through Change Man Panels Panel By Panel Navigation Using Direct Access Navigation Using Package List Option Working with Lists of Libraries, Packages and Components Using Commands Using Patterns Using Lists Using a Selection List Scrolling Through Lists /Using Basic Edit Line Commands Inserting a Line Repeating a Line Deleting a Line Read-Only Versus Data Entry Fields Accessing the Online Tutorial Exiting Change Man Canceling Changes on a Panel Change Man Online Error Messages Providing Job Card Information 2-1 2-3 2-3 2-3 2-4 2-4 2-4 2-4 2-5 2-5 2-7 2-8 2-9 2-9 2-9 2-9 2-9 2-10 2-10 2-10 2-11 2-11
Creating a Change Package

Creating a New Package Using Short and Long Methods Providing a Package Description Specify Package Installation Instructions Package Scheduling Dependencies Package User Records Scheduling Installation Date and Time An All Site Environment A Remote Site Environment 3-1 3-2 3-5 3-7 3-8 3-9 3-11 3-11 3-12
Updating Change Package Information

Updating a Change Man Package 4-1
ii
Change Man Version 5.1
Contents
Control Information Updating Package Description Package Installation Instructions Package Scheduling Dependencies Affected Applications Complex or Super Package Information Package Installation and Site Information Remote Site Single Site Updating Package Status for Super and Complex Packages
4-2 4-4 4-5 4-6 4-7 4-8 4-8 4-9 4-10 4-12
Checking Out a Component

Checkout Restrictions, Rules, and Options Checking Out Components Selecting Components from Baseline or Promotion Libraries Using the Package List to Select Components 5-1 5-3 5-3 5-7
Staging a Component
Administration Parameters Which Affect Staging Accessing the Stage Options Panel Staging from Development Stage Development Component List Stage Compile and Link Edit Panel User Options Mass Compile and Link Edit Components Staging Other Type Components Panel Staging from Packages Source to Load Relationship Panel User ID Work List Panel Staging Using Package Parameters Component List Parameters 6-1 6-2 6-3 6-7 6-8 6-11 6-12 6-13 6-13 6-15 6-16 6-16 6-17
Auditing Packages
Change Man Audit Function The Role of the Impact Analysis Database Setting Parameters to Determine the Focus of the Audit Application Library Types Order 7-1 7-1 7-2 7-4
User Guide
iii
Contents
Accessing the Audit Change Package Panel 7-4 Fields of the Audit Change Package Panel 7-5 Auditing A PAckage 7-8 Auditing A Simple Package 7-9 Auditing Staging Libraries Only 7-9 Auditing Staging Libraries and Baseline Libraries of the Package Application 7-10 Auditing Staging Libraries of the Package and Baseline Libraries of All Applications 7-11 Auditing A Complex or Super Package 7-12 Auditing Staging Libraries of Participating Packages 7-13 Auditing Staging and Baseline Libraries of Participating Packages 7-13 Auditing a Participating Package as a Simple Package 7-15 Staging Libraries of Participating Packages 7-15 Staging and Baseline Libraries of Participating Packages 7-16 Auditing a Participating Package as a Primary Package 7-18 Staging Libraries Only (with Installation Date Set to No) 7-18 Staging Libraries Only (with Installation Date Set to Yes) 7-19 Staging and Baseline Libraries (with Installation Date Set to No) 7-20 Staging and Baseline Libraries (with Installation Date Set to Yes) 7-22 Auditing a Participating Package by Department Number 7-24 Staging Libraries Only (with Installation Date Set to No) 7-25 Staging Libraries Only (with Installation Date Set to Yes) 7-25 Staging and Baseline Libraries (with Installation Date Set to No) 7-27 Staging and Baseline Libraries (with Installation Date Set to Yes) 7-29 Auditing All or a Group of Participating Packages 7-31 Auditing Staging Libraries of all Participating Packages in a Complex or Super Package (with Installation Date Set to No) 7-32 Auditing Staging Libraries of a Group of Participating Packages in a Complex or Super Package (with Installation Date Set to Yes) 7-32 Auditing Staging and Baseline Libraries of all Participating Packages in a Complex or Super Package (with Installation Date Set to No) 7-33 Auditing Staging and Baseline Libraries of a Group of Participating Packages in the Complex or Super Package (with Installation Date Set to Yes) 7-34 Audit Diagnostic Tracing 7-36 The Audit Report 7-38 Report Header 7-38 Report Body 7-39 Section 1. Staged Components by Library Type 7-39
iv
Contents
Section 2. Component History Area Section 3. Source to Copy Relationships Report Section 4. Load-to-Load Relationships Report Section 5. Legend and Summary Section 6. Recommendation Summary Report Out-of-synch Conditions Return Codes Accessing Submitted Audit Reports Audit Auto-Resolve Resolution Actions Resolving same-named members in multiple (PDS) libraries. About Change Man Assist New Features and Capabilities with Change Man Assist Incremental (partial) Processing Assist How Incremental Processing works Multi-Tasking Support (or Threads) Storage Considerations 4095 Baseline Library limit removed
7-41 7-43 7-44 7-46 7-46 7-47 7-48 7-55 7-56 7-57 7-57 7-58 7-58 7-58 7-58 7-59 7-59 7-59
Freezing a Package
Accessing the Freeze Options Panel Freeze a Package Online Freeze A Package in Batch Unfreeze and Refreeze Components Reset the Freeze in Progress Indicator Resubmit Install JCL Build Request 8-3 8-4 8-5 8-6 8-8 8-9
Promoting to a Local System

Using The Promotion Facility for Intermediate Testing Third Party Testing Unit Testing of Online Systems Promoting and Demoting Changes Promoting a Change Package Promoting Online Promoting in Batch Demoting a Change Package Demoting A Package Online 9-2 9-2 9-2 9-2 9-4 9-4 9-5 9-6 9-7
User Guide
Contents
Demoting in Batch Promoting and Demoting Components Promoting Components Selectively Promote Components Repromote Select Components. Demoting Components from a Package Checking for Common Components
9-7 9-8 9-8 9-8 9-9 9-10 9-11
10
Promoting to a Remote System

How Administrators Can Configure Remote Promotion Promoting Change Packages or Components to a Remote Site Selective Promotion of Components Demoting Change Packages or Components from a Remote Site Checking for Common Components at a Remote Site 10-1 10-2 10-9 10-11 10-15
11
Recompiling and Relinking Components

Recompile Overview Recompiling into Staging Libraries Providing Recompile Job Information Browsing Recompile Source List Relinking Load Components Example Stage User Options Panel 11-1 11-1 11-4 11-5 11-5 11-6 11-8
12
Approving or Rejecting a Package

Approving or Rejecting Packages Approving or Rejecting a Package Approving a Package Rejecting a Package Resubmitting the Batch Approve and Batch Build X Node Data Set JCL Using the Component User ID Work Record Using the Component User ID Work Record during Approval Viewing the Component User ID Work List Deleting the Component User ID Work Record Distribution and Installation of the Change Package Distribution to Remote Sites 12-2 12-5 12-5 12-6 12-6 12-7 12-7 12-7 12-9 12-9 12-9
vi
Contents
13
Reverting a Package
Reverting a change package. 13-2
14
Backing a Package Out of Production

Accessing the Backout Change Package Option Panel Backing Out a Package from a Remote Site 14-1 14-3
15
Using Package List for Change Man Functions

Accessing the Package List Parameters Panel Browsing the Change Package List Acting on Packages 15-1 15-4 15-5
16
Defining and Generating Change Man Reports

Change Man Reports Change Man Programs for Generating Reports Generating SAS Reports REPORTS module CMN$$RPT module Generating non-SAS Reports (CMNBAT10) REPORTS2 module Generating Change Man Reports Generating Change Man Batch Reports Panel Accessing Submitted Change Man Reports 16-1 16-3 16-3 16-3 16-5 16-6 16-6 16-7 16-7 16-9
17
Utility Requests
Compress Staging Libraries Accessing the Compress Staging Libraries Panel Renaming or Deleting Components Accessing the Rename or Scratch Options Panel Creating Utility Requests from Baseline Activating or Deleting Utility Requests from Packages Deleting and Undeleting Packages Deletion Considerations Setting up a Memo Delete Canceling a Deleted Change Package Request 17-1 17-1 17-2 17-2 17-3 17-4 17-5 17-5 17-5 17-6
User Guide
vii
Contents
18
Comparing Staging Libraries

Comparing Staging Libraries to Baseline or Promotion Printing, Deleting or Keeping Comparison Information 18-1 18-3
19
Browsing and Printing Package Information

Using the Activity Log Providing Browse Activity Log Filtering Information Reviewing the Activity Log Produce a Log Activity Report Using the Baseline Browse/Print Facility Browsing Baseline and Promotion Library Components Editing Components in Browse Mode Use ISPF Edit Commands Copy Components to Target Data Sets Printing Copies of Components Print Copies of Components with Expanded Copybooks Browsing a Compressed Listing Browsing Compressed Listings Printing, Deleting or Keeping Compressed Listings Delete, Keep and/or Print the Report Browsing the Global Notification Facility Using the Scan Library Utility Scanning Online Allowing a Library Scan Restricting a Library Scan Search for Dependencies Batch Scan Search for Character String Search for Dependencies Running the Batch Scan 19-1 19-1 19-3 19-3 19-6 19-9 19-11 19-11 19-11 19-13 19-13 19-13 19-13 19-15 19-15 19-15 19-17 19-17 19-20 19-20 19-21 19-22 19-22 19-24 19-25
20
Querying Packages and Components

Accessing the Query Options Panel Querying Change Packages Specifying Filter Criteria Using the Extended Search Criteria Panel Browsing the Query Package List 20-1 20-2 20-2 20-5 20-5
viii
Contents
Querying Components Querying Impact Analysis Data Specify Search Criteria for the Component List Query the Component Selection List
20-9 20-11 20-12 20-15 20-16
Package Category Panels

General Information Non-Source Source Source and Load Relationship Renames and Scratches Approval List Site Activities Date and Time Site and Install Date Information Custom Forms Participating Package Status Start Date and Time Revert Reasons Backout Reason Promotion History Remote Promotion History Promotion Libraries Remote Promotion Libraries Query Development Staging Libraries Query Production Staging Libraries Production Libraries Baseline Libraries A-1 A-2 A-3 A-5 A-5 A-5 A-6 A-6 A-7 A-8 A-8 A-8 A-9 A-9 A-10 A-11 A-12 A-14 A-15 A-15 A-16 G-1 I-1
Glossary Index
User Guide
ix
Contents
WHAT IS CHANGE MAN?
Change Man is a comprehensive system designed to provide reliable and streamlined implementation of software changes on the MVS system. It is a system that manages and automates the process of migrating software changes, or applications, from a development environment to any test environment and to the production environment. A comprehensive TSO/ISPF interface guides you through various change management processes.
FEATURES OF CHANGE MAN

Unique package concept guarantees the coordination of your change Concurrent development is managed Controls version discrepancy and out-of-synch component relationships Maintains listings on-line for immediate access Provides notifications Manage your libraries (CA-Librarian, CA-Panvalet, or PDS, PDS/e) Full suite of on-line and batch query and reporting capabilities Maintain historical information in a single repository.
CHANGE PACKAGES
Within Change Man, a Change Package is the vehicle in which all changes are moved from a development environment to a production environment. A change package may contain one or more components (source, copybook, load, JCL, control cards, compiling procedures, documentation, and other components) which are required to implement a software change.
1-1
1 What is Change Man?
THE CHANGE MAN LIFE CYCLE

This section provides an overview of the Change Man life cycle. It provides a step-bystep description of migrating a change from development to production within Change Man.
Figu re 1:
Create a Change package. A Change package contains the elements to be edited and installed into production, and is identified by an unique package identification generated by Change Man. When you create a package, you provide the information that Change Man needs to track and control the package. Checkout components from baseline. The checkout process allows you copy components from your baseline libraries to a Change Man staging library or to a personal development library where you can make changes. Editing changes. You may edit changes in the Change Man staging or in the development libraries. Staging components. For source components, staging will run the appropriate translation procedures to create associated load modules. Components such as documentation or copy members are copied into the staging libraries, if they are not there already. Audit process. The audit process identifies out-of-synch conditions that may be inconsistent with your development procedures, as well as other code problems. Freeze process. The freeze process locks the package and makes the package available for the promotion and approval processes. Promotion process (optional). Promotion allows a package to be moved through various levels of testing. For example, promote from system testing to acceptance testing. Installation. After all of the approvals have been gathered by Change Man, the package is ready to be installed. If the manual installation method was selected when the package was created, the package will be installed immediately after the final approver has approved the package. If the Change Mans internal scheduler method was selected, Change Man will automatically install the package on the date and time specified at package creation. If an external scheduler is used, Change Man will convey the install information to that scheduler so that it can install the package. Baseline ripple. After installing the package, Change Man will baseline ripple the package. Baseline ripple is the process that Change Man executes to version all package components.
1-2
Inside Change Man Development
INSIDE CHANGE MAN DEVELOPMENT

Behind the displayed Change Man panels, there are jobs being performed that ensure the smooth flow of enhancements to each application maintained by development analysts.
Create
Create is a first step of the Change Man life cycle. After you Create a change package, Change Man allocates Staging Libraries as needed. The dataset names of the Staging Libraries reflect the application mnemonic chosen for your application, the package number assigned by Change Man for this change, and the type of components placed in the library; for example, DEMO . CMNSTAGE .#000023. SRC . The Global Administrator decides on the format of the data set name. The package information is recorded on the Package Master along with the TSOID of the creator. A record of this event (Package Creation) is placed on the Log.
The Checkout Process

Checkout is the process of copying components from the Baseline Library (any level back or from Promotion Libraries) to a staging library or a development area outside of Change Man for modification in a change package. You can Checkout online in the foreground or in background as a batch job. If you Checkout in background mode, Change Man asks you to verify (initially type or update) the jobcard statements needed to perform the batch job. When you Checkout a component, the standard PDF statistics are carried forward and the version number (the vv portion of vv.mm) is incremented. Change Man adds the Checkout information to the statistics that make up a component's history. A record of this event (Checkout component) is placed on the Activity Log. Anyone can browse this log for information not only on Checkout actions, but also other Change Man activities. When you associate the Checkout to a valid change package ID, the component name is added to the package's Staging List. This means that when you select the Stage option from the Build Options Menu and select to Stage from the Package Driven option, the component is already listed with a Checkout status.
The Staging Process

Staging introduces components into Change Man by copying them from development or personal libraries into Change Man Staging Libraries. All Staging Library components must be associated with pre-defined change packages.
User Guide
1-3
Depending on how your administrator configures Staging parameters for your site, you can either Stage any newly created application component into any change package, or only components previously associated with (i.e. checked out to) change packages. For instance, your administrator may want to restrict new development on an application and designate that only existing components be maintained. The administrator can restrict the Staging process so that only components previously associated with change packages can be Staged back into the change cycle. Before staging, verify that your administrator has: Assigned compile procedures for each language type you intend to Stage. Assigned appropriate compilers during installation of Change Man
Staging Libraries contain components of the same type. The following table lists component types that Change Man recognizes and considers when staging.
Type
SRC LOD JCL DOC CPY LCT LIKE SRC LIKE LOD LIKE CPY OTHER
Description
Source modules Load modules JCL Documentation Copybooks Linkage Control Cards Assign this type to SRC, LOD, or CPY components when you want to Stage components of same type into separate Staging Libraries.
Assign this type to components when you want to customize processing of a component. Compiling Procedures
PRC
1-4
You can Stage components either online or Mass Stage them in batch.
Staging Type
Online
Enables User to do the Following:

Use confirmation panels to review relevant parameters and compile procedures prior to Staging a component. Use language assumption, a feature that automatically assigns language types, and designated compile procedures when Staging source components.
Batch
Stage multiple components simultaneously. Stage complete libraries of components. By-pass confirmation panels to Stage components faster. Use the language assumption feature.
Auditing
When you audit a packages Staging Libraries, Change Man analyzes and reports on every module contained in your change package with respect to the baseline versions. The Audit function also validates all copies and program calls, producing a report listing all duplicates and out-of-synch conditions. (Audit also includes copybook promotion libraries when generating the hash token table.)
Freezing Packages
When you are ready to Freeze the package for Promotion (optional) and/or Approval (Approval is required), Change Man checks two things: Are all components in an Active status?
During the Stage process if the component is successfully copied into the appropriate Staging Library and if source components have compiled, link/edited, and their bind has completed successfully then Change Man will change the status of the component to Active. Did the package pass the audit?
The audit level selected by the application's administrator must not be exceeded. When the package is successfully Frozen, the package's status changes from DEV to FRZ, which locks out anyone from Staging into the package's libraries. A record of this event (Freeze package) is placed in the Activity Log.
User Guide
1-5
Promoting Packages and Components

The Promotion facility allows you to set up intermediate environments or Promotion levels where you can perform quality assurance, unit and system tests on packages and components. Promoting involves migrating change packages or components through these intermediate environments. Demoting is the deleting of components logically or physically from these environments. Before using the Promotion facility, your application administrator must first set up:
Promotion levels: Promotion process: Promotion authorization: You can have one or more levels of Promotion, each level having one or more libraries associated with it. You can Promote packages and components either online or in batch. Each Promotion level can be secured. Your administrator can build rules within Change Man and your security system that will designate which users can Promote a package to a specific level.
Generally, you Promote packages from Staging Libraries to specified Promotion levels. The following functional characteristics of the Promotion facility may affect decisions you make about when and how to Promote and Demote packages and components: After components are copied from package Staging Libraries, they will continue to reside in the Staging Libraries. This implies that you should only include executable libraries in your Promotion environment. Source modules do not have to be promoted because they will be retained in the package libraries. Promotion from level to level may be a logical copy or a logical move; that is, the components may remain in the previous environment or they may be deleted from the previous environment upon Promotion. Each time you Promote (or Demote), Change Man updates the statistics constituting the component's history. A record of this event (Promote package) is placed in the Activity Log. Staging skeletons for source components may reference Promotion copybook libraries as part of the copybook concatenation. Therefore, if copybooks are Promoted, they may be made available to source compilation of other packages.
1-6
Change Man does not enforce the use of Promotion, even if it has been set up by an administrator. Moreover, upon completion of the Approval process, the package is Distributed (and Installed) regardless of the level of Promotion reached. This gives you the flexibility to alter the path of migration of each package. However, if you do want to require a Promotion path, you can administratively link your Promotion security to your Approval security. This technique allows a promoter to offer his/her Approval of a package once it has been successfully Promoted and tested.
Approving Packages
When a person accesses the Change Man panels, that persons TSOID is passed along and used to determine which functions are available. Approval may be performed only by those TSOIDs associated to the Entity names that the application's administrator has specified as approvers. The approval process consists of browsing the package information and Staging Libraries for quality control and standards and selecting to Approve (or Reject) the package. A record of this event (Package Approval) is placed in the Activity Log. The package status is changed from FRZ to APR. All Approvals for a package must be gathered before Change Man will Install a package. In fact, the final Approval of a package will actually initiate or schedule the package Installation. A change package must be in Frozen (FRZ) status to be Approved or Rejected. In general, a packages components cannot be modified while in Frozen status. This implies that a packages components cannot be modified while approvals are being gathered. However, components can be selectively unfrozen, modified, and refrozen while the package is still in Frozen status. There can be multiple levels of Approvals. Change Man requires at least one approval but allows administrators to set up more than one level. Multiple levels of Approval may be set up in a hierarchy. This implies that Change Man will enforce an order of Approvals. Change Man will not allow Approvals to be gathered out of order. More than one User ID may be authorized to satisfy a given Approval level. This is set up in your security system. Your application administrator may have set up Approval notifications. Each approval level can be configured with multiple User ID notifications. The User IDs that are notified may or may not coincide with the User IDs that can actually satisfy the Approval.
User Guide
1-7
Different packages may have different Approvals. Change Man allows administrators to set up separate Approval Lists by application and by time of day. Change Man will attach an abbreviated Approval List to unplanned packages Created outside of normal business hours. Change Man will attach a complete Approval List to all other packages. Furthermore, your administrator may have tailored a user exit to customize Approvals Lists further. Change Man provides special processing for packages with an abbreviated Approval List attached. These Approvals must, of course, be gathered before the package can be Installed. However, once Installed, the package continues to be available for Approval or Rejection by approvers on the complete Approval List. This allows for a post-Installation Approval strategy. Packages may be Promoted and Demoted while Approvals are being gathered. This implies that the final Approval of a package will Install it, regardless of the Promotion status. Therefore, the final approver of package should be sensitive to the Promotion activities of packages. If a package is Rejected, it must be Reverted if it is to be updated to conform to the Reject reasons. Package Revert will reset the Rejection and place it in Development status. The package must then be Frozen again to reinitiate Approvals. If a package was Promoted before it was Rejected, then it must be Demoted before it can be Reverted. Package Revert will reset any gathered Approvals. This is true regardless of whether the package is first Rejected.
Installation
Installation depends on whether or not an internal scheduler is set up by the global administrator or if the Install job JCL has been specially modified. There are four variations on Installation: If no scheduling system is specified, the package goes through the Installation process immediately. If the Install job JCL is set up with a TYPRUN=HOLD, the user releases the job when they are ready to Install. If a scheduling system other than Change Man's internal scheduler is specified, then Change Man performs a batch interface to add the Install job to the scheduler's list. The operator, however, must still demand the job for the package to be Installed. If Change Man is the scheduler, it checks the package master every few minutes for any packages which are ready and Installs those that meet the criteria.
1-8
Backing Up
Backup is the first job to be performed when Installation time arrives. This job copies the production libraries (only those components which are about to be overlaid with updates) to a backup set, in case they are needed to back out the incoming enhancement. Next, the contents of the change package Staging Libraries are copied into production libraries. A record of this event (Package Installation) is placed on the Activity Log. This occurs each time the package is Installed at one of the Remote Sites. Once the package is verified as Installed in all requested sites, the following steps are performed: 1 The package status is changed from DIS to INS (or from APR to INS if there are no Remote Sites). A job is sent to the development center to clear out the last level of Promotion reached and ripple the Baseline Libraries for that application. The package status is changed from INS to BAS. A record of this event (Baseline Ripple) is placed on the Log.
3 4
NOTES Only the various versions of changed software components are updated; Change Man ripples the changes through the versions of an application's Baseline Libraries. Assume that the following is true: An application maintains up to three versions of its Baseline Library software: current (0), -1, and -2. You want to update the Baseline Libraries with a change package in which component A is changed, component B is scratched and component C is added. There already is a -1 and -2 version of component A. Thus, the baseline library is updated as follows: The -1 version of component A is copied to overlay the -2 version of component A. The 0 version of component A is copied to overlay the -1 version of component A. The newly Installed version of component A is copied from the production Staging Libraries to overlay the Baseline Library 0 version of A.
User Guide
1-9
Component B is scratched. The newly installed version of component C is copied from Staging Libraries and added to the Baseline 0 Libraries.
Backing Out Packages or Components

If there is a problem with the change package (backout is allowed only for permanent packages) after it has been Installed, the change package is backed out by deleting the updated component in production and then retrieving the previous version of application software from the Backup Library. This option is selected by an authorized user in the production environment, usually an operator or production analyst. Change Man will back out the entire package by copying the components from the Backup Libraries to overlay production. The package status is changed from BAS to BAK. A record of this event (Package Backout) is placed in the Activity Log. A job is submitted in the development area to reverse ripple the Baseline Library. A record of this event (Baseline Reverse Ripple) is placed in the Activity Log.
Temporary Change Cycle

When a temporary change package is Created, the user must type the number of days the change is to remain in the temporary (override) environment (if your global administrator has setup this option). The Installation process is different from other package types because the contents of the temporary change package Staging Libraries are copied into Temporary Libraries, which are concatenated ahead of production libraries. Since the production library components are not touched, Change Man does not perform the Hot Backup. The components are never rippled into the Baseline Library. After the package is Installed, Change Man begins the aging process at each site selected to receive the temporary change. The components in the Temporary Library are deleted when the number of elapsed days is met. If you use a scheduler, the job will automatically be run. If you use a manual scheduling method, the job will be submitted on hold, and will need to be released when the duration of days is met. After the package has been deleted from all sites, its status is changed from INS to TCC, and a record of this event (Temporary Change Cycle Completed) is placed on the Activity Log.
Distribution to Remote Sites

The next step after approval depends on the environment type configured for the site. If there are Remote Sites, then the package Staging Libraries, the Installation JCL, and a copy of the package master records pertaining to this change are:
1-10
Change Man Library Environment
Distributed (copied) to all the sites specified in the Creation/Update package process. A record of this event (Package Distribution) is placed in the Activity Log and a Distribution acknowledgment is sent back to the development center. The package status is changed from APR to DIS. If Remote Sites exist, the package is ready for Installation. For further information, see Installation on page 1-8.
Distributing and Installing Components at Remote Sites

Remote Sites are additional CPUs where Change Man Installs components. An additional CPU can be: A separate computer in another building A separate computer in the same building A logical CPU on the same machine as part of an LPAR (logical partition) without shared DASD
Any of these Remote Site configurations enables you to develop components on one CPU and distribute and Install production level components on a different CPU. Remote Sites act only as a receiver of production level components. The only time developers interact with Remote Sites is when they select which Remote Site to Distribute and Install production level components.
CHANGE MAN LIBRARY ENVIRONMENT

Checkout
Checkout enables you to reintroduce components residing in baseline or promotion libraries to the change cycle. Generally, production level components are checked out for modification. However, you can check out any previous version of a baseline component that exists (-1, -2, -3, etc.). Depending on the way your administrator has configured Change Man, you can check out components: To personal libraries To staging libraries Only if they are associated with change packages
User Guide
1-11
In batch Online Concurrently with other developers
If your site has applications that require parallel development, you can configure Change Man to allow concurrent checkout of components. Change Man has an automated process for managing this concurrent development. As part of this process, Change Man ensures that each owner of a version is aware of the actions of the other owners. After you check out components and make necessary modifications, Change Man records the components and the associated change package for further impact analysis. This ensures that your developers are always working with the proper version of a component.
Impact Analysis
To analyze the impact of changes, many organizations rely on data from a variety of sources, such as batch library scans and cross reference files. This method makes it difficult to maintain all sources of data and ensure that they are current. Change Man provides a comprehensive facility to capture, query, and enforce relationships between components. These relationships include not only the traditional ones, such as a source and executable relationship, but also other relationships based on common references to copybooks, SQL Include components, CA-PANVALET ++INCLUDE components, CA-LIBRARIAN - INC components, called subroutines, and JCL fields such as program name, filename, or data set name.
Staging
Staging is the process of introducing newly developed or previously developed components into the Change Man change cycle for modification or enhancement, and packaging with related change package components. When you stage a component, Change Man recognizes the type of component that you are staging and copies it into a staging library of corresponding type (source, load, JCL, documentation, copybook, etc.). Staged components are also associated with a pre-defined change package, the vehicle Change Man uses to move components through the change cycle and track the history of change management activities for each staged component. In change management systems other than Change Man, staging libraries are merely pre-production holding areas shared by one or more application groups. After components are tested in development libraries, they are copied into staging libraries prior to production implementation.
1-12
Change Man staging libraries, however, are more than pre-production holding libraries. Components can be modified and tested within protected Change Man staging libraries. Moreover, when you stage source components, they are compiled and the resulting load modules are identified, helping you to maintain the integrity of source-to-load relationships. In addition, Change Man maintains up-to-date records of all staging activities for packages and components. For example, when you stage a source component, Change Man records the time that the component was staged, the name of any associated load modules, or copybooks, and the compiling procedures and linkage parameters used during the compile. This information is kept in Change Man's master file, the package master. You can view this component and package information any time by using the query function. Change Man further extends the concept of staging by providing a means of isolating components from other changes in progress. This prevents uncontrolled and unknown copybooks and subroutines from being inadvertently referenced, allowing parallel or concurrent development without the risk of accidental overlays. The stable coexistence of multiple versions of a single component simplifies the blending of changes.
Audit
The Change Man audit process enables you to ensure correct synchronization of components and procedures. Because of the range of features offered by the package master and the impact analysis database, Change Man maintains control of current and past modifications and component versions. Therefore, potential production problems can be identified before they impact production. The audit function inspects the staging library contents of an evolving change package (in the DEV/FRZ status) with respect to baseline library contents. The inspection looks for situations such as a package that shows no change from the baseline library, or a package that contains a LOD component that does not match its SRC component. Recognizing these situations, called out-of-synch components, is part of Change Man's ability to help you detect code that is inconsistent with your development procedure and other code problems. Examples of out-of-synch situations that the Change Man audit addresses include: Copybooks that have been changed after a source program has been compiled Source programs that need to be recompiled due to a copybook change Called subroutines that have been changed after a referencing source program has been compiled and linked
With Change Man you can enforce by application whether you want an audit, and if so, whether you want to correct or leave potential uncovered problems.
User Guide
1-13
Recompile and Relink

You can use audit to analyze the staging library contents of an evolving change package, with respect to baseline contents, for the purpose of finding any out-of-synch situations. The recompile function is used to resolve certain types of out-of-synch conditions found during the audit. The allowable audit return code is determined during global and application parameter generation, and you are not allowed to freeze the change package without passing the audit return value entered for the application. Using the relink option you can relink load components without associating them with source code. The relink process is similar to compile since you select a component from a baseline list. A new load component is produced and copied into the package's staging library. Use the delete function to remove recompiled or relinked components that do not have associated source in the package. You can also delete the resulting LST file and any other non-load components that have been associated with it through the CMNBAT90 service. (See your administrator for details on this service.) A components history is picked up from the history record for that component in the package master. For example, the relink picks up the user options on CMNUSR01 that were there when the program was last relinked. When relinking you can include LCT cards that contain the link control cards from staging or baseline libraries, or you can dynamically generate them if there is no LCT component available. You do this if you: Do not have source code for a component, but make a change to a subroutine Need to perform a composite link where the resulting load component name does not have accompanying source
Freeze
Another unique Change Man feature is the ability to freeze change packages. When the change package is ready for the next phase of the change implementation life cycle, a freeze is performed to prevent further modifications. The freeze also positions the change package for promotion or approval. Traditional methods accomplish this function by moving components from the development libraries to a separate set of libraries or, in some cases, separate environments. With Change Man, however, the CMN instance controls your updates in conjunction with your security system, so component movement is no longer necessary. If further modifications are required, you can unfreeze a change package, and the approval process is reset.
1-14
Promotion
Change Man has the ability to promote change packages through multiple shared, pseudo-production promotion environments. These promotion environments are secured as if they are production, and Change Man controls all updates. Change Man considers shared promotion environments a place where full integrated system testing may be performed. When the time comes for a full system or an integrated system test, authorized approvers promote the acceptable components into the promotion environments. When testing is complete and the change package is approved, Change Man (optionally) removes the components from the promotion environments. All production installation occurs from the change package staging environment. With Change Man, you define your testing methodology and the number of testing levels that are required.
Approve
Approvals for change package installation are performed online, eliminating the requirement for manual approval processes. During the Change Man approval process, authorized approvers can indicate that the change package is acceptable for production implementation, or they have the option to reject or review the change and generate a checklist of questionable or unclear items for the programmer to resolve. Change Man relies on your security system. Change Man does not use internal personnel tables. Approval lists of specific USERIDs or approving entities are defined to your security system so that electronic signatures can be collected. For each application, a variety approvers can be included on the approver list. Separate approval lists can be created for scheduled, planned changes and for unplanned, emergency changes, or you can choose to use an approval hierarchy. With Change Man, you have the flexibility to make these choices.
Production Installation
Change Man is actively involved in the management and control of actual production component installation. Component installation can be automated through Change Man's internal scheduling system or through Change Man's direct interface with a job scheduling system. In addition to component movement, Change Man performs other production installation activities such as DB2 Plan binding. Change Man also has a unique change quantity threshold facility that allows you to control the number of changes that occur within a given time period. For example, you may want to limit the number of change packages that are installed during month-end processing.
User Guide
1-15
BASELINE LIBRARIES AND DELTA DECKS

Change Man recognizes that your software components are vitally important business assets. Change Man gives you the ability to store your production source components in a structure that works for your organization. Components can be stored in PDSs, CA-LIBRARIAN files or CA-PANVALET files. Components can be segregated by application or by categories, such as batch versus online. Equally, applications can share libraries. Change Man automatically stores prior versions of components. These versions can be stored as full copies (inherent for load components), or as delta decks. Change Man uses a unique reverse base/delta technique known as stacked reverse deltas. With this technique, the current version of the component is the base, and delta decks are created to backtrack to previous versions.
BACKOUT MANAGEMENT FACILITIES

Comprehensive backout management requires more than simply backing up the components of a change. Change Man has comprehensive backout management facilities. In addition to source components, the prior functioning executable components are backed up. If a backout becomes necessary, Change Man automatically restores these executable components to production. Change Man also performs all necessary DB2 Plan rebinding automatically. Because Change Man is package driven, it backs out all the components of a change automatically.
EMERGENCY CHANGES
Critical abends occur at inopportune times and require immediate attention. Because Change Man contains the ability to create Unplanned Change Packages, and the ability to maintain a separate list of approvers for unplanned changes, emergency changes are safe, fast and easy to perform. Additionally, because of the facility (optional) to concurrently check out components. Change Man provides notification to any developer affected by the change so that the emergency fix can be incorporated globally into all change packages.
1-16
Storage Name Considerations
Change Man does not impede the emergency change process by requiring that the component be released, reassigned, or renamed by the original owner.
STORAGE NAME CONSIDERATIONS

CA-Panvalet has a ten-character allowance which Change Man does not recognize, because it looks for eight character names. References in this manual assume PDS naming is the convention.
User Guide
1-17
1-18
ACCESSING CHANGE MAN AND NAVIGATING PANELS
Change Man runs as a subtask under SERNET in the MVS subsystem. TSO/ISPF users invoke the Change Man ISPF client, which communicates with the CMN instance using either cross memory services or TCP/IP. The CMN instance architecture provides a single point of control and secure access to your production and development libraries. Interfacing to your security system for access, Change Man provides the optimum amount of control without sacrificing performance. The Primary Options Menu is the first panel the user sees when they sign onto the system. From this panel the user can select whichever function they require. The Primary Option Menu contains some of the Change Package Life Cycle processes like Freeze, Promote and Approve. The remainder of the Life Cycle processes can be found in the Build Options panel. The Build Options panel is accessed from the Primary Option Menu.
ACCESSING THE PRIMARY OPTION MENU

Accessing Change Man is accomplished by selecting Change Man from your initial ISPF menu or executing the designated CLIST. During the sign-on initiation a temporary Change Man title panel appears. Once the sign-on initiation is complete, the Primary Option Menu appears. Note: it is important that you not execute two Change Man sessions through ISPF split screens. Doing so will produce unreliable results. Make sure that you have only one Change Man session running on your terminal at any given time.
2-1
2 Accessing Change Man and Navigating Panels
CMN@PRIM -------- CMN 5.1 OPTION ===> 1 2 3 4 5 6 A B C D L M N O Q R T X Build Freeze Promote Approve List Reports Admin Backout M+R Delete Log Monitor Notify OFMlist Query Revert Tutorial Exit -
Primary Option Menu
SYS(8) -----------------------
Create, update and review package data Freeze or unfreeze a package Promote or demote a package Approve or reject a package Display (to process) package list Generate Change Man batch reports Perform administrative functions Back out a package in production Merge+Reconcile (formerly CDF) Delete or undelete a package Browse the activity log Monitor internal scheduler or packages in limbo Browse the Global Notification File Online Forms package list Query packages, components and relationships Revert a package to DEV status Display information about Change Man Exit Change Man
Press ENTER to process; enter END command to exit.
The Primary Option Menu displays options built upon the authorization of your User ID and your site configuration. After verifying with your host security system which Change Man functions that you can access, Change Man builds the menu. If you are licensed for Online Forms Manager (OFM) or Merge+Reconcile (M+R), those options will appear on the Primary Option menu. The security administrator as well as the global and application administrators can provide information about user and site security configurations. From the Primary Option Menu, you can access Change Man services and functions by using the panel-by-panel access method, the direct access method, or package list method. The Primary Option Menu and the Build Options menu are the main navigational panels in the Change Man system. Their primary function enables the user to access all the Change Man functions.
2-2
Accessing the Build Options Menu
ACCESSING THE BUILD OPTIONS MENU

The Build Options panel allows the user to navigate throughout many of the Change Package Life Cycle processes and many other additional functions. The Build Options panel can also be displayed at the completion of the package create process. It will be displayed with the Change Package ID in the upper right-hand corner after a successful creation of a Change Package.
CMNBUILD ----------------------- BUILD OPTIONS ------------------------------OPTION ===> 0 1 2 3 4 5 6 7 8 9 B C L S Z Dates Create Update Custom Utility Checkout Stage Audit Recompile Relink Browse Compare Listing Scan Compress Display the installation calendar Create a new package Update package information Create, update, approve or review custom forms Rename and Scratch information Check out components from baseline or promotion Stage, edit, browse and delete components Audit a package Recompile source code from baseline or promotion Relink load modules Browse\print\copy baseline or promotion Compare staging to baseline or promotion Browse compressed listings Scan baseline for character strings Compress change package Staging Libraries
Press ENTER to process; Enter END command to exit.
NAVIGATING THROUGH CHANGE MAN PANELS

Panel By Panel Navigation
In the Option field of a menu, type the number or letter that designates a specific function and press Enter. For example, from the Primary Option Menu, you type 1 and press Enter to display the Build Options menu. To return to a previous menu or panel, type End in the Option or Command field on any panel or press the appropriate PF key, usually PF3.
User Guide
2-3
Use panel by panel navigation as you learn Change Man. When you become more familiar with the product, you can use the direct access method for navigation.
Using Direct Access Navigation

In the Option or Command field, type a sequence of numbers or letters with a plus sign or an equal sign preceding the string and place a period between each command. For example, in the Option or Command field, you type:
+1.2
or
=1.2
where 1 and 2 are single character options on successive panels. Change Man displays the panel of the last character in the direct access stacked commands. To return to a previous menu or panel, type END in the Option or Command field on any panel or press the appropriate PF key command.
Using Package List Option

Almost all functions within Change Man are available to every package through the List Option (option 5 in the Primary Option Menu). Once the users become more familiar with the product, will usually switch to the Package List option. This method of panel navigation is very fast as the user can do all their work from the Package List panel.
WORKING WITH LISTS OF LIBRARIES, PACKAGES AND COMPONENTS

There are lists in Change Man that let you view contents of libraries, packages and components.
Using Commands
Following are a set of standard commands used to work with these types of lists. To use them, type the command letter and a component or package name in the panel. Press ENTER to execute the command. Type the following commands in the cursor field next to the component: B to browse
2-4
Working with Lists of Libraries, Packages and Components
S to select an item for action. H to display history for an item.
Type the following commands on the Command line: REFRESH to Update the list. CANCEL to Cancel the request. SORT to Sort the list. (Only valid for member and procedure/language displays) L to locate an item in the list. For example, L xxxxxxxxx where xxxxxxxx is the component name.
After executing one of these commands, a message normally appears in the status column to indicate your action (such as BROWSE for a browsed list item). Not all commands are available from all lists. If you type an incorrect command or character in a panel, Change Man displays the correct available commands for that panel.
Using Patterns
The system often encourages you to input a pattern to get a range of values in a list from Change Man. Pattern rules are: * A * at the end of a character string is a wildcard for any number of characters. It must be used at the end of a string. * A ? can replace any single character in a string.
Using Lists
When using lists within Change Man, there are many options for masking the list you display so that you can work with only a portion of the total list. The following table contains some examples of the masking options and their results.
User Guide
2-5
Masking (or Pattern) * or * * A* A*B *A * 1 ABCD1* ABCD*1 ABCD10* ABCD*10
Description
all packages for all applications all packages for all applications that start with A all packages for all applications that start with A and end with B all packages for all applications ending with A all packages in all applications that begin with 1 all packages whose number starts with 1 in application ABCD (e.g., ABCD100000 to ABCD199999) all packages ending in 1 in application ABCD all packages whose number starts with 10 in application ABCD (e.g., ABCD100000 to ABCD109999) all packages ending with 10 in application ABCD
When masking, the package name must be at least four characters. For example, if the package name is DAM, and you typed D*M, to display all DAM packages for application that begin with D and end with M, you will receive a message indicating a package error. If there is an * in the number part of the package ID, there are no zeroes filled in before the number; e.g., A*10* is resolved to Aaaa10nnnn, not 00010n. However, if an * is not found in the number area, there is zero fill; e.g., A*10 is resolved to Aaaa000010). Also, remember that if the application is only three characters, there will be a blank before the package number. Often when using Change Man, you are asked to complete a list or table of items. There are standard ways to insert, repeat, and delete lines of information from these lists. Each of the following tasks assumes that you have already accessed the required panel to build a list. Refer to the individual panels for information about saving your changes to the list or for functions that are unique to that list.
2-6
Working with Lists of Libraries, Packages and Components
Using a Selection List

A selection list is a panel that displays a list from which you can select one or more items. You often access a selection list from a main panel field to help you identify available items, such as a list of all possible library types. Selection lists are of the following types. Single item selection. You select one item by typing S in the line command field of the item you wish to select and pressing ENTER. If you attempt to select multiple items, only the first is used. After pressing ENTER, processing continues from the panel from which the selection list was accessed. Multiple item selection. You select one or more items by typing S in the line command field of each item you wish to select and pressing ENTER. After pressing ENTER, processing continues from the panel from which the selection list was accessed. Extended multiple item selection. You select one or more items by typing S in the line command field of each item you wish to select and pressing ENTER. If the selection list contains a status column, *SELECT is displayed in the status field for each selected item. You may scroll up or down the list to select more items. You can deselect items by typing D in the line command field of each item you wish to deselect and pressing ENTER. If the selection list contains a status column, *DE-SEL is displayed in the status field for each deselected item. Enter the END command to exit from the selection list and continue processing from the panel from which the selection list was accessed.
Single item selection list:
CMNSTG08 ---------------- LIBRARY TYPE SELECTION LIST -----ROW 1 TO 14 OF 14 COMMAND ===> SCROLL ===> PAGE LIB DESCRIPTION _ CLI CLIST -User Customized CLISTs _ CPY Copybooks _ CP1 Like-CPY (1) _ CTC Control Cards s JCL Job Control Language _ LCI LOADCICS-CICS Load Library _ LCT Linkedit Control Cards _ LDG LOADDLG -ISPF Dialog Load Library _ LD1 Like-LOD (1) _ LOD Load Modules _ OTH OTHER library type _ SKL ISPF Skeletons _ SRC Source Code _ VLD Load Modules ***************************** Bottom of data ******************************
User Guide
2-7
Multiple item selected list:
CMNLNGSL ------------------ LANGUAGE SELECTION LIST ---------- Row 1 to 5 of 5 COMMAND ===> SCROLL ===> CSR LANGUAGE s ASM _ COBOL _ COBOL2 s PLI _ C ******************************* Bottom of data ********************************
Extended multiple item selection list:
CMNRSTSL ----------------- REMOTE SITE SELECTION LIST -------- Row 1 to 5 of 5 COMMAND ===> SCROLL ===> CSR SITE NAME _ U510P *SELECT _ TSITE01 *DE-SEL s TSITE10 s TSITE11 d TSITE12 *SELECT ******************************* Bottom of data ********************************
Scrolling Through Lists

Often, lists that you build or access through Change Man are too long to view on one screen. Use the UP and DOWN keys (normally PF7 and PF8 keys, respectively) on your keyboard to scroll up and down through the lists. To move up or down a specific number of lines, type a number on the command line and use the PF7 key to go up that number of lines, or the PF8 key to go down that number of lines. To move to the top or bottom, enter the command TOP or BOTTOM, respectively, on the command line and press enter.
2-8
/Using Basic Edit Line Commands
/USING BASIC EDIT LINE COMMANDS

Inserting a Line
1 Move the cursor to the first column or the LCMD column of the last row in the list. Type I and press Enter to Insert a new row. Change Man inserts a new row. Provide the information required for each column of that row.
2 3
Repeating a Line
1 Move the cursor to the first column, the LCMD column, of the row that you want to repeat in the list. Type R and press Enter to Repeat a new row.
Change Man copies the row and inserts it after the existing row. 3 4 Move the cursor to the new row. Provide the information required for each column of that row.
See the individual sections of this manual for each panel for a table that describes each column of the list (since these lists differ depending on what information they are to contain).
Deleting a Line
1 Move the cursor to the first column, the LCMD column, of the row that you want to delete in the list. Type D and press Enter to delete the row. The row is deleted.
READ-ONLY VERSUS DATA ENTRY FIELDS

Change Man distinguishes between read-only fields and fields that require you to type data with color/hue and with visual symbols.
User Guide
2-9
If you have a color monitor, the fields display in different colors. If you have a monochrome screen, the intensity of the read-only fields differ from the intensity of the data entry fields. There are also visual symbols that follow the field label. If it is a read-only field the label is followed by a colon. For example, PACKAGE STATUS: DEV is a read only field. If the field is followed by ==> the screen expects you to provide data in that field. For example: LIB TYPE ==>__ indicates a data entry field. If the fields are normally data entry fields, but you are currently prohibited from updating them, the arrow symbol still displays. However, the color/hue of the field is the read-only color, and BROWSE ONLY displays in the upper right hand corner of your screen.
ACCESSING THE ONLINE TUTORIAL

An online tutorial is available to help you understand available options. To view the tutorial, press PF1; you can also type option T from the Primary Options menu.
EXITING CHANGE MAN

You can exit Change Man in the following ways: 1 Type X or END on the command line of the Change Man Primary Option menu and press enter (or press PF3). Type =X on the command line of any Change Man panel and press enter.
CANCELING CHANGES ON A PANEL

You can abandon your changes two ways. Some panels require you to press End without pressing Enter to abandon. Other panels require you to type CANCEL at the command line and press Enter. The panel you are viewing tells you how to abandon your changes.
2-10
Change Man Online Error Messages
CHANGE MAN ONLINE ERROR MESSAGES

Change Man and ISPF handle online error messages similarly. The short (Change Mans term), or primary (ISPFs term), error message displays by default in the upper right-hand corner of your screen. To display the long (or secondary) error message, press PF1. The message appears on the third line of the screen, left justified. Ordinarily, the long message is more helpful because it provides more information. Remember, the long message does not display by default, and must be requested by pressing PF1.
PROVIDING JOB CARD INFORMATION

Change Man often requests that you provide job card information for batch jobs such as install, checkout, stage, and freeze. Each time there are several lines of default information that you input the first time you run a batch job. After you edit the job card information, this information is saved and becomes the default. The following figure shows an example of the Checkout Job Card Information panel.
CMNCKOT2 --------------- CHECKOUT JOB CARD INFORMATION -----------------------COMMAND ===> JOB STATEMENT INFORMATION: ===> //WSER85A JOB ,ACCOUNT INFORMATION______________________________________ ===> //*_____________________________________________________________________ ===> //*_____________________________________________________________________ ===> //*_____________________________________________________________________ Press ENTER to process; Enter END command to exit.
Unless the job card panel contains separate, unique fields, the job card information is simply included into JCL exactly as displayed on the panel.
User Guide
2-11
2-12
CREATING A CHANGE PACKAGE
When you create a change package, you are defining the outer structure of the change package. Creating a change package involves providing information about the change package to Change Man through a series of panels. The panels you encounter during the create process may vary, depending on the options you select.
CREATING A NEW PACKAGE

To create a new change package, take the following steps: 1 From the Primary Option Menu, select option 1 and press Enter. The Build Options Menu appears.
CMNBUILD ----------------------- BUILD OPTIONS -----------------------------OPTION ===> 0 1 2 3 4 5 6 7 8 9 B C L S Z Dates Create Update Custom Utility Checkout Stage Audit Recompile Relink Browse Compare Listing Scan Compress Display the installation calendar Create a new package Update package information Create, update, approve or review custom forms Rename and Scratch information Check out components from baseline or promotion Stage, edit, browse and delete components Audit a package Recompile source code from baseline or promotion Relink load modules Browse\print\copy baseline or promotion Compare staging to baseline or promotion Browse compressed listings Scan baseline for character strings Compress change package Staging Libraries
From the Build Options menu, select option 1 and press Enter. The Create A New Package panel (CMNCRT01) displays:
3-1
3 Creating a Change Package
CMNCRT01 ---------------- CREATE: CREATE A NEW PACKAGE ---------------------OPTION ===> L S Long method - Prompt for package description and special instructions Short method - Use default package description and instructions
PACKAGE TITLE ===> Displaying example for documentation APPLICATION REQUESTERS NAME REQUESTERS PHONE WORK REQUEST ID DEPARTMENT PACKAGE LEVEL PACKAGE TYPE PACKAGE TIME SPAN PACKAGE TO COPY FORWARD UNPLANNED REASON CODE TEMPORARY CHANGE DURATION ===> ===> ===> ===> ===> ===> ===> PLANNED ===> PERM ===> ===> ===> (Blank or pattern for list)
(1-Simple, 2-Complex, 3-Super, 4-Participating) (Planned or Unplanned) (Permanent or Temporary) (Optional package name) (* for list) (In days)
Using Short and Long Methods

You can use a short or long method to create a change package. The short method is quickest and easiest way to create a package. It requires less information than the long method. Default values are used instead of displaying some of the panels that are displayed when using the long method. The long method has more fields and screens, for entering information.
The advantage of the long method is that more historical information is saved for your package. Both are viable methods and each shop may have its own guidelines for which method is preferable and under what circumstances. Fields that are not displayed when you create a package using the short method can still be updated using the Update package information option on the build options menu. At the end of the creation process you are required to provide the scheduled installation date for the change package. When you do this Change Man updates the Planned Installation Calendar, which limits the number of change packages that can be installed on each day for the upcoming year.
3-2
Creating a New Package
The following table describes the fields of the Create A New Package panel (CMNCRT01) and the valid information that you can enter in the fields.
In this field...
PACKAGE TITLE APPLICATION REQUESTER'S NAME REQUESTER'S PHONE WORK REQUEST ID
Type.
Title of the change package that you are creating. An application mnemonic (three or four bytes). The name (up to 25 characters) of the person creating the package.
The phone number (up to 15 characters) of the person creating the package. Up to 11 characters that identifies the work request of the package. (This may be required by the administrator. Depending on the INFO Management rule in effect, this field may be linked to an INFO Change record number.) The department of the person creating the package. (This field entry may be required by the administrator.). 1 (Simple). The change package contains a change that is unrelated to any other change package. This level of change package does not affect any other application, or it does not require them to make any changes to their software or operational procedures. 2 (Complex). The parent for two or more participating change packages that have interdependent change to software or operational procedures. Complex change packages contain only control, general information, and a list of the participating packages. There are no staging libraries associated with super/complex change packages. Remote sites and the installation dates for each site are tracked in the participating change packages. 3 (Super). The parent for two or more participating change packages that contain major changes to several applications. Super change packages contain only control, general information, and a list of the participating packages. There are no staging libraries associated with super/complex change packages. Remote sites and the installation dates for each site are tracked in the participating change packages. 4 (Participating). The change package is related to one or more other participating change packages.
DEPARTMENT
PACKAGE LEVEL
User Guide
3-3
In this field...
PACKAGE TYPE
Type.
Planned (Indicates that the packages are scheduled changes that follow the established application rules.) Unplanned (Indicates that the packages are unscheduled changes, possibly an emergency fix. Emergency packages bypass some of the application rules and have a separate approval list.
PACKAGE TIME SPAN
Permanent (Indicates that the packages are Scheduled changes that update baseline or production libraries. Permanent changes are either planned or unplanned. This is the normal way to install changes. Temporary Changes that run for a predetermined length of time. Once that time has expired, Change Man automatically deletes the change. Temporary changes do not update baseline or production libraries. These changes are installed into a static override library. Temporary changes are either planned or unplanned.
PACKAGE TO COPY FORWARD
The name of the package that contains the information that you wish to copy into the package that you are creating. (If you are creating a package that is similar to an existing package within the application, you can copy the information from that existing package into the package that you are creating.) The code indicating the reason for the package being unplanned., or * to display a list of reason codes. The number of days that the change is to remain in effect.
UNPLANNED REASON CODE TEMPORARY CHANGE DURATION
3-4
Providing a Package Description
After you have completed typing information in the fields of the Create a New Package panel (CMNCRT01), press ENTER to save the information that you entered on the panel. When you press ENTER, the Create Package Description panel (CMNCRT02) appears.
CMNCRT02 ---------------- CREATE: PACKAGE DESCRIPTION ------ Row 1 to 12 of 12 COMMAND ===> SCROLL ===> PAGE Press ENTER or END to continue or type CANCEL to exit. (minimum one line, maximum 46 lines) ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ******************************* Bottom of data ********************************
PROVIDING A PACKAGE DESCRIPTION

The Create Package Description panel (CMNCRT02) allows you to provide a general description of the package that you are creating. To provide a general description of your package, in the general description area (free form text field) of the Create Package Description panel (CMNCRT02), type a description of the change package that you are creating, and press ENTER to save the information and display the next panel. See the section 'Complex or Super Packages' for the remaining panels related to creating Complex or Super packages.
User Guide
3-5
CMNCRT03 ------------- CREATE: INSTALLATION INSTRUCTIONS --- Row 1 to 12 of 12 COMMAND ===> SCROLL ===> PAGE Press ENTER or END to continue or type CANCEL to exit. CONTINGENCY ===> 1 1-Hold production and contact analyst 2-Backout change, continue production 3-Other ===> (CMN, Manual or Other)
SCHEDULER
===> CMN
(minimum one line, maximum 46 lines) ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________
If you selected package level 4 to create a participating package, affected applications panel (CMNCRT05) is displayed.
CMNCRT05 --------------- CREATE: AFFECTED APPLICATIONS ----- Row 1 to 12 of 12 COMMAND ===> SCROLL ===> PAGE Press ENTER to continue or type CANCEL to exit. COMPLEX/SUPER PACKAGE ID ===> __________ APPL '''' ____ '''' ____ '''' ____ '''' ____
In the COMPLEX/SUPER PACKAGE ID field, type the package ID of the complex or super package associated with this participating package. In the APPL column field, type the applications affected by this package. If you enter a value in this field, Change Man adds to the approval list of the package in your current application any approver that differs (interfacing approver) from the planned approval list of the application you enter in this field. You specify interfacing approver when you set up your planned approval list in the Planned Approval panel (CMNCAPLD) during application parameter setup.
3-6
Specify Package Installation Instructions
Press ENTER to save the information entered on the panel. When you press ENTER, to save your information, the Create On Site Information panel (CMNCRT06) or Create Remote Site Information panel (CMNCRT07) is displayed.
SPECIFY PACKAGE INSTALLATION INSTRUCTIONS

The Create Installation Instructions panel (CMNCRT03) allows you to provide instructions for the installation of the change package as well as to indicate an option for problem contingency instructions in case a production problem arises after the package has been Installed. The following table describes the fields of panel (CMNCRT03) and the valid information that you can enter into the fields.
In this field...
CONTINGENCY
Type...
The code that represents the action that you want the operations staff to take if a problem is encountered when installing the change package 1 (Hold production and contact analyst). Discontinue running the production jobs for your application until a supporting analyst can be reached for instructions. 2 (Backout change, continue production). Back out of the change package and continue running your application's production jobs as normally scheduled. 3 (Other). Code Describe in this field some other action to be taken if there are problems in installing this change package. This field has a maximum length of 44 characters.
SCHEDULER
CMN Change Man holds the installation until the date and time you specify on the site installation date and time panel. Manual Change Man installs the change package as soon as the final approval is given. Other Specify scheduling instructions for change packages that use a job scheduler other than CMN and Manual. In order to use this option, the administrator must have set the Installation Job Scheduler field, on the Global Parameters Parameter 1 of 5 panel, to Other, and customized CMN017. If you select this option, the Create Scheduling Dependencies panel (CMNCRT04) appears.
User Guide
3-7
In this field...
INSTALLATION INSTRUCTIONS
Type...
Contains detailed instructions on how your change package should be installed. These can include, but are not limited to, production job dependencies and change package Installation dependencies. Each line has a maximum length of 72 characters and up to 46 lines are saved.
After you have completed typing information in the fields of the Create Installation Instructions panel (CMNCRT03), press ENTER to save the information that you entered on the panel and display the next panel.
Package Scheduling Dependencies

If you typed OTHER in the scheduler field of the Create Installation Instructions panel (CMNCRT03), the Create Scheduling Dependencies panel (CMNCRT04) is displayed. You may wish to specify the successor (run after) and the predecessor (run before) jobs that your scheduling system must be aware of in order to schedule installation of this change package's components.
CMNCRT04 -------------- CREATE: SCHEDULING DEPENDENCIES COMMAND ===> Press ENTER to continue or type CANCEL to exit.
SCROLL ===> PAGE
SUCCESSOR PREDECESSOR JOB3____ JOB1____ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ******************************* Bottom of data ******************************
The Create Scheduling Dependencies panel (CMNCRT04) allows you to specify scheduling instructions for the package. It may not even be required by the job scheduler at your site and is optional. You may leave the panel blank and use the update option on the Build Options menu to modify it at later time.
3-8
Package User Records
The following table describes the fields of the Create Scheduling Dependencies panel (CMNCRT04), and the valid information that you can enter into the fields. You can enter any of the line commands (I, R, or D) in the first column. In this field...
SUCCESSOR
Type...
Successor job name regarding how your change package should be installed. These can include, but are not limited to, production job dependencies and change package installation dependencies (maximum character length = 8). Predecessor job name (maximum character length = 8).
PREDECESSOR
PACKAGE USER RECORDS

If the Package User Records facility has been enabled, you can provide additional information to be associated with the package on panels CMNDPUP1 and CMNDPUP2. These panels are customized to your site's requirements. See your Change Man administrator for more information. The following are samples only. Press ENTER on each panel to continue. Package User Records can be edited via the Update function of the Build menu (option E), or from the Package List using the UE line command.
User Guide
3-9
CMNDPUP1 ------------ CREATE: SAMPLE PACKAGE USER PANEL 1 --------------------COMMAND ===> Enter YES or NO : Field Field Field Field Field Field 1 2 3 4 5 6 ===> ===> ===> ===> ===> ===> NO NO NO NO NO NO
NEXT PANEL ===> N
(Y = yes, N = no)
Press ENTER to continue or CANCEL to exit.
CMNDPUP2 ------------ CREATE: SAMPLE PACKAGE USER PANEL 2 --------------------COMMAND ===> Enter YES or NO to indicate value of variable: TEST TEST TEST TEST VALUE1 VALUE2 VALUE3 VALUE4 ===> ===> ===> ===> NO NO NO NO
Press ENTER to continue or CANCEL to exit.
3-10
Scheduling Installation Date and Time
SCHEDULING INSTALLATION DATE AND TIME

You can provide the date and time when you want your change package to go into production. You provide this information on the Create On Site Information panel (CMNCRT06) or the Create Remote Site Information panel (CMNCRT07). Which panel that you use depends on the option that the global administrator set: All (you have no remote sites) Development (change packages are distributed to remote sites, you cannot install them into production libraries) Production (this is a remote site, no development is performed on this machine) Development/Production (you can distribute change packages to remote sites and install them into production libraries)
An All Site Environment

If your Change Man environment is an All site, the Create On Site Information panel (CMNCRT06) appears when you press ENTER from Create Installation Instructions panel (CMNCRT03). The Create On Site Information panel allows you to schedule the installation date and time of the change package, as well as enter the name and phone number of the people responsible for the change for locations that have only one site.
CMNCRT06 ---------------- CREATE: ON SITE INFORMATION ------------------------COMMAND ===> Press ENTER to create the package or type CANCEL to exit. INSTALL YYYYMMDD 19990628 DATE/TIME FROM TO 0600 0700
PRIMARY/BACKUP CONTACTS Chaka Yebo_______________ D. Read Locks____________
PHONE NUMBERS 323-696-1233___ 323-696-1233___
The following table describes the fields of the Create On Site Information panel (CMNCRT06), and the valid information that you can enter in the fields. In this field...
INSTALL DATE
Type...
Type the date that the package is scheduled to be Installed into production, year first, month, day yyyymmdd.
User Guide
3-11
In this field...
INSTALL TIME FROM INSTALL TIME TO
Type...
Type the time of day in hhmm format in which your change package Installation to begin, military format example 1600=4:00 p.m. Type the required time of day in hhmm format in which you want your change package installation to be completed.
Note:This field may not be applicable, depending on your scheduling interval.

PRIMARY/ BACKUP CONTACTS PHONE NUMBERS Type the names of the primary and back-up personnel, responsible for supporting the installation of this change package at each remote site (maximum character length = 25). Type the phone numbers of the primary and back-up personnel, responsible for supporting the installation of this change package at each site. (maximum character length = 15).
After you have completed typing information in the fields of the Create On Site Information panel (CMNCRT06), press ENTER. Change Man creates your package, displays the Create A New Package panel (CMNCRT01) and your package identification number appears in the upper right corner of the panel.
A Remote Site Environment

If your Change Man environment is a remote site, the Create Remote Site Information panel (CMNCRT07), similar to the following figure, appears when you press ENTER to save information that you entered on the Create Installation Instructions panel (CMNCRT03).
CMNCRT07 -------------- CREATE: REMOTE SITE INFORMATION ------ Row 1 to 2 of 2 COMMAND ===> SCROLL ===> PAGE Press ENTER or END to create the package or type CANCEL to exit. Enter * in line command field for remote site selection list. REMOTE SITE TEST____ INSTALL DATE/TIME YYYYMMDD FROM TO 19990628 0600 0700
PRIMARY/BACKUP CONTACTS PHONE NUMBERS Dave Barnhill____________ 323-742-6222___ Oscar Charleston_________ 323-742-6223___ TEST2___ 19990628 0600 0700 Dave Barnhill____________ 323-742-6222___ Oscar Charleston_________ 323-742-6223___ *******************************Bottom ofdata********************************
If this application has been configured by the administrator to keep the baseline library by site, you must create a separate change package for each remote site.
3-12
Scheduling Installation Date and Time
The Create Remote Site Information panel (CMNCRT07) might look similar to the following figure, which shows the remote sites where you change package will be installed. If it is necessary for you to change the remote site, you can enter the following information in the fields. In the field...
REMOTE SITE INSTALL DATE INSTALL TIME FROM INSTALL TIME TO
Type...
Remote site at which to install the change package. The date (YYMMDD) the package will be installed on the remote site. The time of day (HHMM) the change package installation will begin.
The time of day (HHMM) in which you want your change package installation to be completed.
Note:This field may not be applicable, depending on your scheduling interval.

PRIMARY/ BACKUP CONTACTS PHONE NUMBERS The names of the primary and back-up personnel, responsible for supporting the installation of this change package at each remote site (maximum character length = 25). The phone numbers of the primary and back-up personnel, responsible for supporting the installation of this change package at each remote site (maximum character length = 15).
After you have completed typing information in the fields of the Create Remote Site Information panel (CMNCRT07), press ENTER. Change Man creates your package and displays the Build Option menu (CMNBUILD) with your package identification number appearing in the upper right corner.
User Guide
3-13
3-14
UPDATING CHANGE PACKAGE INFORMATION
After creating a change package, you may wish to update some of the information associated with it. You can update most of the information entered during the creation process as long as the package you update has a Development (DEV) or Open (OPN) status and you have access to the application. You can browse the information if the package is in Frozen (FRZ) status.
UPDATING A CHANGE MAN PACKAGE

To update a Change Man package, take the following steps: 1 From the Primary Option Menu, select option 1 (Build). The Build Options panel (CMNBUILD) appears. From the Build Options panel (CMNBUILD), select option 2 (Update). The Update Package Information panel (CMNPGNL0) appears.
CMNPGNL0 ---------------- UPDATE: PACKAGE INFORMATION ------ INFORMATION SAVED OPTION ===> PACKAGE ID ===> NAVI000006 1 2 3 4 5 6 7 8 9 Control General Instruction Dependencies Affected Apps Complex/Super Install Dates Complex/Super Complex/Super Update Update Update Update Update Update Update Change Change package control information general description installation instructions job scheduling dependencies affected applications cmpx/supr package information install date and site information complex/super package to CLO status complex/super package to OPN status
4-1
4 Updating Change Package Information
If you are using exit CMNEX 001, the installation date of a package in FRZ status can be updated through Option 2 (UPDATE) from the Build Options Menu; otherwise, you can only update the installation date of a package in DEV status. For Option 7, depending on how Change Man was generated, either the on site (CMNONSTE) or remote site (CMNPRSTI) panel is displayed. The scheduling record for a package is created at approve time. This means when a package in FRZ status is being implemented with the Change Man internal scheduler, updates to the install date of a package are captured. Provided you are using this scheduler at Approve time, the scheduling record is built with the latest install date originally entered or updated by the user.
CONTROL INFORMATION
Use the Update Control Information panel to review the control information for a change package. Once packages are frozen or super/complex packages are closed, the panel displays in browse mode. To access the Update Control Information panel, select option 1 on the Update Package Information panel.
CMNPGNL1 ---------------- UPDATE: CONTROL INFORMATION ------------------------COMMAND ===> PACKAGE ID: NAVI000006 COMPLEX/SUPER ID: NAVI000002 STATUS: DEV STATUS: OPN INSTALL DATE: 19971230
PACKAGE TITLE ===> Package to install jcl for test REQUESTERS NAME REQUESTERS PHONE WORK REQUEST ID DEPARTMENT PACKAGE LEVEL PACKAGE TYPE PACKAGE TIME SPAN UNPLANNED REASON CODE TEMPORARY CHANGE DURATION ===> ===> ===> ===> ===> ===> ===> ===> ===> I.Programmer 555-1212 416NAVIG DP 4 (1-Simple, 2-Complex, 3-Super, 4-Participating) PLANNED PERM (* for list) (In days)
4-2
Control Information
The following table describes the fields on the Update Control Information panel. Type in entries in each of the required fields. The only information that you are allowed to change is: the change package title; the requester's name; the requester's phone; the work request number; and the department. Field
PACKAGE TITLE
Description
Type the title for the new change package that you are creating. Choose a title which is easily recognizable since it displays on package lists. Type the 3 or 4 byte application mnemonic for the change package you are creating. Type the requester's name.
APPLICATION
REQUESTER'S NAME REQUESTER'S PHONE WORK REQUEST ID DEPARTMENT PACKAGE LEVEL
Type the requester's phone number.
Type the work request number.
Type the department to which the requester belongs. Simple The change package contains a change that is unrelated to any other change package. Complex and Super A complex or super package is the parent of two or more participating change packages. After you have created all participating change packages, someone is designated to create the complex or super package. It contains a list of the participating packages with the general and control information. It does not contain any of the components to be installed. Participating The change package is related to one or more other packages. All of these packages are considered to be participating with each other.
PACKAGE TYPE
Planned Scheduled changes that are required to follow all established application rules. This is the normal way to install changes. Unplanned Unscheduled changes, possible an emergency fix. Emergency packages bypass some of the application rules and have a separate approval list.
User Guide
4-3
Field
PACKAGE TIME SPAN
Description
Permanent Scheduled changes that update baseline and production libraries. Permanent changes are either planned or unplanned. This is the normal way to install changes. Temporary Changes that run for a predetermined length of time. Once that time has expired, Change Man automatically deletes the change if a scheduler is used. Otherwise, if you use a manual scheduling method, the job will be submitted on hold, and will need to be released when the duration of days is met. Temporary changes do not update baseline/production libraries. These changes are installed into a static override library. Temporary changes are either planned or unplanned.
UPDATING PACKAGE DESCRIPTION

The Package Description panel (CMNPGNL2) allows you to review and update the description of the change package, the request number, name, phone number and department number of the person requesting or responsible for the change. 1 From the Update Package Information (CMNPGNL0), type the package ID of the package and select option 2. The Update Package Description (CMNGNL2) appears.
CMNPGNL2 ---------------- UPDATE: PACKAGE DESCRIPTION ------- ROW 1 TO 1 OF 1 COMMAND ===> SCROLL ===> PAGE Press ENTER to process; enter END command to exit. PACKAGE ID: NAVI000012 STATUS: DEV INSTALL DATE: 19990305
(minimum one line, maximum 46 lines) this is a test changeman package: lifecycle_____________________________ ******************************* Bottom of data ********************************
From this panel, update the description. You can describe your change package using freeform narrative in the General Description area of the panel. Change Man limits you to 46 lines. Use the same commands as you do to edit lists, specifically:
I to insert new (blank) rows. R to repeat existing rows.
4-4
Package Installation Instructions
D to delete existing rows.
Press Enter to save your changes and return to the Update Package Information panel.
PACKAGE INSTALLATION INSTRUCTIONS

The Update Installation Instructions panel allows you to review and update the installation instructions and the problem contingency instructions for a change package. To access the Update Installation Instructions panel, from the Build Option panel, type the package ID and select option.
CMNPGNL3 ------------- UPDATE: INSTALLATION INSTRUCTIONS ---- ROW 1 TO 1 OF 1 COMMAND ===> SCROLL ===> PAGE Press ENTER to process; enter END command to exit. PACKAGE ID: NAVI000005 CONTINGENCY ===> 1 STATUS: DEV INSTALL DATE: 19971230
1-Hold production and contact analyst 2-Backout change, continue production 3-Other ===> (CMN, Manual or Other)
SCHEDULER
===> OTHER
(minimum one line, maximum 46 lines) Install using procedure #1._____________________________________________ ******************************* Bottom of data *****************************
User Guide
4-5
The following table describes the fields on the Update Installation Instructions panel. Field
CONTINGENCY
Description
Code that represents the action you want the operations staff to take if a problem is encountered while installing your change package:
1 - Hold production and contact analyst. Discontinue running the production jobs for your application until a supporting analyst can be reached for instructions. 2 - Back out (reject) change and continue production. Back out of the change package and continue running your application's production jobs as normally scheduled. 3 - Other - Use if 1 and 2 above do not apply. Describe some other action to be taken if you encounter problems when installing this change package. This field has a maximum length of 44 characters.
SCHEDULER
CMN Change Man holds the installation until the date and time you specify on the Remote Site Selection panel. Manual Change Man installs the change package as soon as it passes final approval. Other Specify scheduling instructions for change packages that use a job scheduler other then CMN and Manual.
INSTALLATION INSTRUCTIONS
Freeform instructions on how your change package should be installed. These can include, but are not limited to, production job dependencies and change package installation dependencies. Each line has a maximum length of 72 characters and up to 46 lines are saved.
PACKAGE SCHEDULING DEPENDENCIES

To accees the Update Scheduling Dependencies panel (CMNPGNL4), from the Build Option panel, type the package ID and select option 4 on the Update Package Information panel.
4-6
Affected Applications
CMNPGNL4 -------------- UPDATE: SCHEDULING DEPENDENCIES ----- ROW 1 TO 1 OF 1 COMMAND ===> SCROLL ===> PAGE Press ENTER to process; enter END command to exit. PACKAGE ID: NAVI000005 STATUS: DEV INSTALL DATE: 19971230
SUCCESSOR PREDECESSOR JOB3____ JOB1____ ******************************* Bottom of data *****************************
AFFECTED APPLICATIONS
When you install a participating package, you need to know the other participating packages (affected packages) under the super and complex umbrella. To display these packages, perform the following: 1 2 Select Option 2 on the Build Options menu. Type a participating change package ID and select Option 5 on the Update Package Information panel. Press PF3 or type End after the Update Package Description panel has been displayed. Press PF3 or type End after the Update Installation Instructions panel has been displayed. Press PF3 or type End after the Update Scheduling Dependencies panel has been displayed. The Update Affected Applications panel appears.
User Guide
4-7
CMNPGNL5 --------------- UPDATE: AFFECTED APPLICATIONS ------ ROW 1 TO 1 OF 1 COMMAND ===> SCROLL ===> PAGE Press ENTER to process; enter END command to exit. PACKAGE ID: NAVI000006 COMPLEX/SUPER ID: NAVI000002 STATUS: DEV STATUS: OPN INSTALL DATE: 19971230
APPL BRP_ ******************************* Bottom of data *****************************
COMPLEX OR SUPER PACKAGE INFORMATION

Complete the Complex/Super Information panel. 1 2 Select Option 2 on the Build Options menu. Select Option 6 on the Update Package Information panel. The following panel displays.
ROW 1 TO 14 OF 14 SCROLL ===> PAGE
CMNPGNL6 ------------- UPDATE: COMPLEX/SUPER INFORMATION -COMMAND ===> Press ENTER to process; enter END command to cancel. PACKAGE ID: NAVI000002 PACKAGE ID NAVI000001 NAVI000006 navi000005 __________ STATUS: OPN
PACKAGE INSTALLATION AND SITE INFORMATION

Depending on your site configuration there are two panels which you may encounter when providing site installation information: Remote Site Installation Information for locations which have remote sites
4-8
Package Installation and Site Information
On Site Installation Information for locations which have only one site
Remote Site
You use the Update Remote Site Information panel to choose the remote sites where your change package is to be installed, schedule the installation date and time of the change package and enter the name and phone number of the people responsible for the change. If this application has been configured by the administrator to keep the baseline library by site, a separate change package must be created for each remote site. Complete the Update Remote Site Information panel. 1 2 Select Option 2 on the Build Options menu. Select Option 7 on the Update Package Information panel. The following panel displays.
REMOTE SITE INFORMATION ----------------------------SCROLL ===> PAGE
CMNPRSTI -------------COMMAND ===>
Press ENTER to process; enter END command to exit. Enter * in line command field for remote site selection list. PACKAGE ID: NAVI000005 CREATOR: WSER85 STATUS: DEV
REMOTE INSTALL DATE/TIME SITE YYYYMMDD FROM TO PRIMARY/BACKUP CONTACTS PHONE NUMBERS remote1__ 19971230 0900 1800 Boss_____________________ x275___________ 0900 1600 Asst Boss________________ x276___________ ******************************* BOTTOM OF DATA ********************************
The following table describes the fields on the Remote Site Information panel.
Column
LCMD (first column)
Description
I to insert new (blank) rows R to repeat existing rows D to delete existing rows * to access remote site selection list
REMOTE SITE
Type the remote site at which to install the change package.
User Guide
4-9
Column
INSTALL DATE INSTALL TIME FROM INSTALL TIME TO
Description
Type the date (in yyyymmdd format) the package will be installed on. Type the time of day (in hhmm format) the change package installation will begin. Type the required time of day in hhmm format in which you want your change package installation to be completed. This field is not supported in the current release using the CMN scheduler. Type the names of the primary and back-up personnel, respectively, who are responsible for supporting the installation of this change package for each remote site (maximum character length = 25). Type the phone numbers of the primary and back-up personnel, respectively, who are responsible for supporting the installation of this change package for each remote site (maximum character length = 15).
PRIMARY/ BACKUP CONTACTS PHONE NUMBERS
1 2
Update the rows of the list. Type a * in the LCMD column of a desired row and press Enter to access the Remote Site Selection List. Select a remote site to add to this information panel. Once it is selected it is displayed in the Remote Site column. Press Enter.
Single Site
You use the Update Site Information panel to schedule the installation date and time of the change package and enter the name and phone number of the person(s) responsible for the change. Complete the Update Site Information panel. 1 Select Option 2 on the Build Options Menu.
4-10
Package Installation and Site Information
Select option 7 on the Update Package Information panel. The following panel displays.
CMNONSTE ------------------ UPDATE: SITE INFORMATION ----------------------COMMAND ===> Press ENTER to process; enter END command to exit. PACKAGE ID: NAVI000006 INSTALL YYYYMMDD 19971230 DATE AND TIME: FROM 0700 TO 1600 PRIMARY/BACKUP CONTACTS Boss_____________________ Asst Boss________________ PHONE NUMBERS xt277__________ xt259__________ CREATOR: WSER85 STATUS: DEV
The following table describes the field of the Update Site Information panel. In this field . . .
LCMD (first column) INSTALL DATE
Type . . .
I, D, or R (See/Using Basic Edit Line Commands on page 2-9) The date (in yyyymm format) when the package is scheduled to be Installed. The time of day (in hhmm format) when the change package installation will begin. The required time of day (in hhmm format) when you want your change package installation to complete. Note: This field may not be applicable, depending on your scheduling interval.
INSTALL TIME FROM INSTALL TIME TO
PRIMARY/BACKUP CONTACTS
The names of the primary and back-up personnel, respectively, who are responsible for supporting the installation of this change package for each remote site (maximum character length = 25). The phone numbers of the primary and back-up personnel, respectively, who are responsible for supporting the installation of this change package for each remote site (maximum character length = 15).
PHONE NUMBERS
User Guide
4-11
UPDATING PACKAGE STATUS FOR SUPER AND COMPLEX PACKAGES

The Update Package Information panel provides two options for changing the status of a super or complex package from OPN to CLO, or from CLO to OPN. Select Option 8 to close a super/complex package. A message displays, informing you that the package status has been changed from OPN to CLO. Select Option 9 to reopen a super/complex package. A message displays, informing you that the package status has been changed from CLO to OPN.
4-12
CHECKING OUT A COMPONENT
After creating a package, you must build the inner structure of the package. Checkout is the first step in building the inner structure. It is the process of copying components from secured libraries to your PDS (or sequential file) for either modification in a future change or for checking out to staging where it can be edited. If you associate the checkout to a valid change package ID, the component name is added to the package's component list. If more than one user checks out the same component (associating to different packages), Change Man notifies all parties concerned. When you check out a component, the standard PDF statistics are carried forward and the version number (the vv portion of vv.mm) is incremented. Change Man adds the checkout information to the statistics that make up the component's history.
CHECKOUT RESTRICTIONS, RULES, AND OPTIONS

The flexibility of Change Man enables your global and application administrators to configure the checkout function with various restrictions, rules, and options, depending on the needs of your site. Check with your administrator for the settings at your site. The administrator may have implemented the following restrictions, rules, and options: Checkout can be restricted or denied for components that are already contained in a change package, disallowing checkout of a component that is part of a package in motion unless it is an unplanned change. Change package contents are restricted to components that have been checked out. Change Man does not let the new components be staged. This means that those that do not already exist in Baseline cannot be staged. Checkout is restricted to those components associated with a change package. Thus an existing package number must be entered during the checkout process to ensure that all components checked out are accounted for. (During the stage process, they are checked in.)
5-1
5 Checking Out a Component
If association to a change package is requested or required, Change Man checks for existence of the package and verifies that it is in DEV status and that its install date has not passed. Checkout can include third party vendor load modules, if they have been staged as a unique three character component type, and designated as 'LIKE P'. Checkout can include components that reside in packages that are in promotion (if any exist for a given application). Checkout can be performed in the foreground (online) or background (batch job). DSORG of an external target data set can be SEQ or PDS. If it is SEQ, you can only choose one component. If checkout to a CA-Panvalet or CA-Librarian library has been allowed, checkout must be done in batch mode. You can request Change Man to show you where a component exists [i.e., at what baseline level(s)]. You can check out components by selecting them from a list of baseline libraries or promotion package components. If checkout is associated with a change package, then each component may be checked out to that package one time only; that is, until the component is either staged or deleted from the package component list. Checkout can be restricted to select user IDs or single entity names, letting only authorized users check out secured components. For online and batch mode, when you choose to checkout to a target data set, or personal library, Change Man will check that the user requesting the service has update level security access to the library and that the data set is in the catalog. If Change Man constructs the data set name, SEQ and PDS may perform the checkout online or batch. If CA-Panvalet or CA-Librarian is selected, the checkout must be a batch job. If a data set name is entered, and it does not exist, Change Man will allocate a dottiest name based on the library type attributes. A batch job is required in this case. Activity files are always checked out to staging libraries regardless of the data sets you specify as targets for components you checkout. For batch mode only, when the target data set field for checkout is left blank, Change Man can automatically construct one in the following form:
5-2
Checking Out Components
zprefix.zuser.component_name.component_type
CHECKING OUT COMPONENTS

To checkout components, take the following steps: 1 From the Build Options menu, select option 5 (Check Out). The Checkout Options panel (CMNMCKOT) appears..
CMNMCKOT ---------------------- CHECKOUT OPTIONS ---------------------------OPTION ===> 1 PACKAGE ID ===> NAVI000005 1 2 Base/Prom - Checkout from baseline or promotion libraries Package - Checkout package components
From the Checkout Options panel (CMNMCKOT), you may select components residing in baseline or promotion libraries (option 1), or you may display and check out components that are already defined to your package (option 2).
Selecting Components from Baseline or Promotion Libraries

To check out components from baseline or promotion libraries, from the Checkout Options panel (CMNMCKOT), select option 1. The Checkout panel (CMNCKOT1), similar to the following, appears.
User Guide
5-3
CMNCKOT1 -------------------------- CHECKOUT ------------------------------OPTION ===> L - List libraries where component is located PACKAGE ID COMPONENT NAME LIBRARY TYPE LANGUAGE SOURCE LIBRARY ===> NAVI000005 (Package name) ===> ===> JCL ===> ===> 0000 (Blank or pattern for list; * for all members) (Blank for list) (Applies to source code; * for list) (Baseline 0 to -n; Promotion +1 to +n) (S-Staging library, P-Personal library) (Personal library: PDS, PDSE, SEQ, PAN, LIB) (Y/N) (1-Online, 2-Batch) (Y/N)
CHECK OUT TO ===> S PERSONAL LIBRARY ===> LIBRARY DSORG ===> CONFIRM REQUEST CHECKOUT MODE LOCK COMPONENT ===> YES ===> 1 ===> YES
You can copy components from baseline or promotion libraries to a sequential file or PDS. The copy may be performed online or as a batch job. All components will be checked out to either a staging or personal library. If any component already exists in the target PDS, the Checkout Warning panel is displayed for confirmation. Component historical information may be viewed using two different methods: type YES in the confirm request field or, at the component list, type the appropriate line commands on that panel. If the component is in motion, a warning panel (CMNCMPSW) shows and displays the other packages working on that component.
5-4
If you wish to display a list of libraries where the specified component may be found, type the component name in the Component Name field and L at the command line. you typed a component in the Component Name field and the library type in the Library Type field. In this field...
PACKAGE ID
Type...
The change package ID with which the component will be associated. The package must be in DEV status. If your application does not require association with a change package, you may leave this field blank. If you associate the checkout to a change package, and baseline is kept by site for this application, the Remote Site Selection List is displayed. Change Man will use the remote site selected for the associated change package for the baseline library selection if you opt to checkout from a baseline level back. If you do not associate to a change package, the Remote Site Selection List will be displayed (if baseline is kept by site) regardless of your intended source library.
COMPONENT NAME
The name of the component that you wish to check out. You can use wild cards to mask the selection, for example, CMN* or CMN?0000 . To checkout all components from a specific library: type the library level in the source library field and type * in the component name field; indicate the location in checkout to field.
LIBRARY TYPE
The library type of the component to checkout. To display and select from a list of library types, leave this field blank. The name of the language in which the source is written. This field is required for source (SRC) or like-source components. To select from a list of available languages names for a new component, leave this field blanks. The level of the library that you want to checkout from. To select from baseline enter a level number from 0 to -999, depending on how many levels of baseline have been configured for your application. If baseline is kept by site for this application and you have not specified package association, the Remote Site Selection List will be displayed before selection of the baseline level back. To select from promotion, enter a level number from +1 to +99, depending on how many levels of promotion have been configured for your application. The Promotion Library Selection List will be displayed for selection of the specific promotion library within the level specified. To select from a list of libraries wherein a specific component can be found; leave location blank and enter the component name in the component name field. The Component Library List displays.
LANGUAGE
SOURCE LIBRARY
User Guide
5-5
In this field...
CHECK OUT TO
Type...
S (Checkout the component to a Change Man staging library.) P (Checkout the component to a personal development library.).
PERSONAL LIBRARY
The personal data set name, if you typed P in the Check Out field. If you leave this field blank, Change Man builds a sequential data set as the default. If you are checking out only one component, you are not required to enter a file name. Change Man creates a sequential data set for you in the form specified in exit CMNEXINS . If you specify a non-existing data set name in batch mode, you receive a message indicating that it was not cataloged. However, Change Man lets you continue, imbeds skeleton CMN $$ CKA , and allocates the data set using the library type attributes you specified when you set up the application. This only occurs during batch checkout; online checkout will issue an error message.
LIBRARY DSORG
The librarys data set organization, if you typed P in the checkout to field. You may indicate a specific data set name (SEQ, PDS, PDSE) for a single component checkout. If the target data set is SEQ (and already exists), Change Man displays the Checkout Warning panel that it will overlay the previous SEQ data set. Whether you want to be notified if the checked out components are going to overlay existing copies of the same components in the target library and whether you want to be notified of any concurrent development prior to checking out the component.
CONFIRM REQUEST
CHECKOUT MODE
1 - Online Checkout the component online. 2 - Batch

Checkout the component in batch mode.
5-6
In this field...
LOCK COMPONENT
Type...
YES (Places an immediate lock on the component, thereby requiring an
unlock before checkout or staging the component.)
NO (Bypasses component locking._

UC (Unlocks a component, enabling checkout or staging of the component by another user.) You can also prevent any other user from checking out this component by locking it with the Lock Component function on this panel. Alternatively, you can use unlock to unlock a component which is already locked. The lock component function is specific to one package. It does not cross packages. Batch checkout does not update the members ISPF statistics, but it does bypass the OVERLAY PRIOR STAGED MODULE administrative rule established at application set up. If a component is locked by another user, you must go to the Stage Package Driven List to unlock the component prior to checkout.
Using the Package List to Select Components

If components are already defined to your Change Package, you can select them by taking the following steps: 1 From the Build Options menu, select option 5. The Checkout Options panel (CMNMCKOT) appears. From the Checkout Option panel (CMNMCKOT), select option 2. A Checkout panel (CMNCKOTS) similar to the following appears.
CMNCKOTS ---------------- CHECKOUT: NAVI000015 COMPONENTS ---- Row 1 to 2 of 2 COMMAND ===> SCROLL ===> PAGE NAME TYPE STATUS CHANGED LANGUAGE PROCNAME ID REQUEST __ CPXLOAD JCL CHECKOUT 19990707 123114 WSER83 __ IEBCOPY JCL ACTIVE 19990706 215107 WSER83 ******************************* Bottom of data ********************************
User Guide
5-7
From the Checkout panel (CMNCKOTS), type S (select) in the command line of the component that you wish to forward from another package and press Enter. A Confirm Checkout Request panel, similar to the following, appears.
CMNCMPSW ------------------------- IEBCOPY.JCL --------------- Row 1 to 3 of 3 COMMAND ===> SCROLL ===> PAGE Press ENTER or END to process or enter CANCEL command to exit. This component is included in the following packages: PACKAGE ID STA PROMOTION VV.MM LAST ACTION SIZE PROCNAME ID NAVI000015 DEV 02.01 1999/07/06 21:51 31 WSER83 NAVI000005 DEV 02.02 1997/08/18 15:58 24 WSER85 NAVI000001 DEV 02.00 1997/08/13 13:45 24 WSER85 ******************************* Bottom of data********************************
The Confirm Checkout Request panel displays other active packages that contain the component and gives you a chance to cancel your request to checkout a component.
5-8
STAGING A COMPONENT
After checking out components, you must use the stage function to edit components, compile and link edit a program, or to submit another transformation type of process. You use the staging function to copy components from development or personal libraries into Change Man staging libraries, or to re-stage components already in staging libraries. If the component type is source (SRC), like source (LIKE SRC), or other (OTHER), there is a subsidiary staging step so that you can define parameters for compile and link/edit procedures before generating the associated load component.
ADMINISTRATION PARAMETERS WHICH AFFECT STAGING

Staging is the process of introducing components into change packages. Depending on how your administrator configures your global and application environments you can either copy newly developed components into change packages or be restricted to staging only components that were previously associated with a package. There are other parameters set by your administrator which affect staging. For instance, your administrator can set the following rules (that control how components can be staged and who can stage them. Staging Rule 1 Explanation
All users can stage new components. This means they can stage components that are not yet associated with a package (development driven staging) as well as stage component that are associated with a package (package driven staging). Lets only users who have been defined (by the local administrator) to a special entity by their TSO ID stage new components. Otherwise, they can only checkout and stage components that are associated with a change package. Does not let you checkout and stage new components, only ones that already exist in your baseline library. This effectively disables development driven staging.
6-1
6 Staging a Component
Generally, you checkout components from an application's baseline libraries (with package association) to staging, stage them using the package driven staging option, and make modifications in staging. However, there may come a time when new components are developed for the application (not yet maintained in baseline); or if the application's users are not required to checkout to an existing package, you checked out a component without package association and decide to include the modification in an existing change package. In these two cases, you would stage using the development driven staging option as described below. Your administrator can restrict editing of components to be within staging libraries only. This assists with version control of components.
ACCESSING THE STAGE OPTIONS PANEL

To stage components, from the Build Option menu, select option 6 and press Enter. The Stage Options panel (CMSSTG00) appears.
CMNSTG00 ----------------------- STAGE OPTIONS -------------------------------OPTION ===> PACKAGE ID ===> NAVI000015 1 2 3 Dev Package Parms - Stage components from development libraries - Process package components - Specify component list selection criteria
This panel is seen only if all the following apply:

The application parameters are generated with the stage restriction Level of 1 or 2 You have appropriate security access You are allowed to stage new components (development driven)
6-2
Staging from Development
STAGING FROM DEVELOPMENT

The Stage from Development panel (CMNSTG02) allows you to copy components into a change package, that in most cases do not exist in the baseline libraries. This panel allows to specify the components that you wish to stage from a development library. To access Stage from Development panel, select option 1 from the Stage Option panel and press Enter.
CMNSTG02 ------------------ STAGE: FROM DEVELOPMENT --------------------------COMMAND ===> PACKAGE ID: NAVI000015 ISPF LIBRARY: PROJECT ===> WSER85 GROUP ===> STUFF TYPE ===> JCL MEMBER ===> STATUS: DEV INSTALL DATE: 19990711
(Blank or pattern for list; * for all members)
OTHER PARTITIONED OR SEQUENTIAL DATASET: DATASET NAME ===> ORGANIZATION ===> (PDS, SEQ, PAN, LIB, OTH) LIBRARY TYPE LANGUAGE STAGE NAME CONFIRM REQUEST STAGE MODE SUPPRESS MESSAGES ===> ===> ===> ===> YES ===> 2 ===> YES (Blank for list) (Blank for list; applies to source code) (Optional if organization not SEQ) (Y/N) (1-Foreground, 2-Batch) (Y/N; applies to batch stage)
The following table describes the fields of the Stage from Development panel. Type information in the required fields and press Enter to process to the next panel, or leave some of the fields blank and select from the resultant lists. In this field...
MEMBER
Type...
Name of the member to stage, component name pattern (the Stage Development Component List panel appears), or * (to stage all the components in the development library). If you leave this field blank, a list of all members within the dataset appears.
User Guide
6-3
In this field...
DATASET NAME
Type...
Name of the dataset that contains the components to be staged. Enclose the dataset name in quotes ('dataset name'). If the development library is a PDS, CA-Panvalet library, CA-Librarian master or any other type of library organization, and if you are copying all the components, append * to the data set name. If you are copying just one component, enclose the component name in parentheses and append it to the data set name. If you don't append anything to the data set name, Change Man displays a component list for you to select from.
ORGANIZATION
The type of library organization (PDS, SEQ, PAN, LIB, or OTHer) from which you are staging. The component that you wish to stage. If your development library organization is SEQ, leave the Member field blank. If your development library organization is PDS, PAN, LIB, or any other type, you must specify library type
LIBRARY TYPE
Leave blank to display the Library Type Selection List panel (CMNSTG08), which allows you to select the library type. LANGUAGE Source code language, if the component is SRC or like-SRC, or leave blank to display a language selection list. The name of a components to be staged from a sequential dataset. If you are copying components of a PDS, PAN, LIB or any other type of library organization, Change Man assigns the same names to the copied components in its Staging Library. If you want the component name in the Change Man Staging Library to be different from the name it has in your development library, type the name. CONFIRM REQUEST Yes (To display a list of packages that contain the component that you are requesting to be staged. Also, to activate confirmation panels for component checkout, stage, and delete.) No (To bypass the above functions.) STAGE MODE 1 (To stage online.) 2 (To stage in batch mode). SUPPRESS MESSAGES Yes (To suppress message sent to your screen from the batch stage.) No (To receive messages from the batch stage.).
STAGE NAME
After entering the appropriate information on the Stage from Development panel (CMNSTG02), press Enter.
6-4
If you left the Library Type field blank, then the Library Type Selection List (CMNSTG08) appears. Place an S beside the library type you want to select.
CMNSTG08 ---------------- LIBRARY TYPE SELECTION LIST ------ Row 1 to 20 of 27 COMMAND ===> SCROLL ===> PAGE LIB CLS CPY CP1 CTC DOC GDG DESCRIPTION COMPAREX 8.2.0 CLIST LIBRARY Copybooks Like-CPY (1) Control Cards Documentation GENDLG -Genned ISPF Dialog panels
_ _ _ S _ _
If you left the Member field blank or did not include a member name in the Dataset Name field, then all members within the dataset name appears on the Stage Development Component List panel (CMNSTG03). Place an S beside the component that you want to stage or copy into the package.
CMNSTG03 M - WSER83.TEST.JCL ------------------------------- Row 1 to 21 of 66 COMMAND ===> SCROLL ===> PAGE NAME FUNCTION VV.MM CREATED CHANGED SIZE INIT ID _ #VARLIST 01.00 1997/07/08 1997/07/08 13:37 1511 1511 WSER85 _ @CMN100 01.00 1994/08/24 1995/04/26 16:22 503 503 C41037 _ ALLOC 01.01 1996/08/07 1996/08/07 18:00 70 32 WSER23 _ API 01.14 1995/10/02 1996/07/30 15:49 54 58 WSER56
User Guide
6-5
If you select a SRC type library, then the Stage Compile and Link Edit panel (CMNSTG04) appears.
CMNSTG04 ---------------- STAGE: COMPILE AND LINK EDIT -----------------------COMMAND ===> PACKAGE ID: NAVI000011 STAGED NAME: LIBRARY TYPE: LANGUAGE: DATASET NAME: COMPILE PROCEDURE COMPILE PARMS LINK EDIT PARMS DB2 PRE-COMPILE OTHER OPTIONS STATUS: DEV INSTALL DATE: 19990711
CPXLOAD SRC - Source Code ASM WSER83.TEST.JCL ===> CMNASM ===> ===> ===> NO ===> (Blank for list; ? for designated procedure)
(Y/N) (Y/N to display other options)
JOB STATEMENT INFORMATION: ===> //WSER83W JOB (X170,374),CHANGE MAN, <=== CHANGE ACCORDINGLY______ ===> // MSGCLASS=9,NOTIFY=WSER83,TIME=1 <=== CHANGE ACCORDINGLY______ ===> /*JOBPARM S=ESA5 <=== CHANGE ACCORDINGLY______ ===> //PROCLIB JCLLIB ORDER=(WSER99.CMN416Q.QACUST.SKELS)____________________
6-6
If you typed * in the Member field or appended * to the dataset name, and SRC is the library, then the Stage Mass Compile and Link Edit panel (CMNSTG05) appears.
CMNSTG05 ------------- STAGE: MASS COMPILE AND LINK EDIT ---------------------COMMAND ===> PACKAGE ID: NAVI000011 LIBRARY TYPE: LANGUAGE: DATASET NAME: COMPILE PROCEDURE COMPILE PARMS LINK EDIT PARMS DB2 PRE-COMPILE OTHER OPTIONS SUPPRESS HISTORY STATUS: DEV INSTALL DATE: 19990711
SRC - Source Code ASM WSER83.TEST.JCL ===> ===> ===> ===> ===> ===> CMNASM (Blank for list)
NO YES NO
(Y/N) (Y/N to display other options) (Y/N to use above criteria for all selected components in place of any history data)
Stage Development Component List

From the Stage From Development panel (CMNSTG02), if you left the Member field blank, and pressed Enter. The Stage Development Component List panel (CMNSTG03) appears.
CMNSTG03 M - WSER85.TEST.JCL -------------------------------- ROW 1 TO 4 OF 4 COMMAND ===> SCROLL ===> PAGE NAME FUNCTION VV.MM CREATED LAST MODIFIED SIZE INIT ID _ CPXLOAD 01.01 1996/08/27 1996/08/28 10:35 16 16 WSER23 _ HOUSKEEP 01.00 1997/06/25 1997/06/25 15:11 460 460 WSER85 _ IEBCOPY 01.11 1996/08/13 1996/08/30 12:29 24 15 WSER23 _ REPORTS 01.00 1995/04/26 1995/04/26 16:22 122 122 C41037 ******************************* Bottom of data ******************************
User Guide
6-7
From the Stage Development Component List panel, you can use any of the following line commands: Line Command (type in
any row of the list)
Description
S M
To stage to the staging library. To put selected members into a member list, which is then passed to mass stage processing. mass stage gets the appropriate language and compile procedure from the component history record. Does not let you checkout and stage new components, only ones that already exist in your baseline library. This effectively disables development driven staging. To edit a component in the development library To review the history of the component. If the component has ever been checked out or staged within Change Man, the history panel appears.
B H
The following primary commands can be issued on the Stage Development Component List panel: Stage All the components of the list will be staged. The Stage Mass Compile and Link Edit panel displays. (See Stage Compile and Link Edit Panel on page 6-8). Stage - Only components flagged with an S will be staged. NOTES If the M and S commands are intermixed, all members selected by M or S will be mass staged.
Stage Compile and Link Edit Panel

This Stage Compile and Link Edit panel (CMNSTG04) allows you to indicate how a source code module is to be compiled and link edited. Change Man uses its staging, promotion and application baseline libraries for COPYLIB components and MACROs needed during the compilation or assembly of your component. Make sure that you have already staged any new or changed COPYLIB components and/or MACROs that you want included when your component is compiled or assembled.
6-8
Change Man does not require that you link edit a component to stage it into the staging libraries. But, if any of the source code components in your change package has not been both compiled and link edited, you cannot freeze the change package.
CMNSTG04 ---------------- STAGE: COMPILE AND LINK EDIT -----------------------COMMAND ===> PACKAGE ID: NAVI000011 STAGED NAME: LIBRARY TYPE: LANGUAGE: DATASET NAME: COMPILE PROCEDURE COMPILE PARMS LINK EDIT PARMS DB2 PRE-COMPILE OTHER OPTIONS STATUS: DEV INSTALL DATE: 19990711
CPXLOAD SRC - Source Code ASM WSER83.TEST.JCL ===> CMNASM ===> ===> ===> NO ===> (Blank for list; ? for designated procedure)
(Y/N) (Y/N to display other options)
Type in values in each of the required fields. The table below may help you complete the fields on the panel. Field
STAGED NAME DATASET NAME
Description
Component's name in the Change Man staging library. Displays the name of the data set that contains the component you are staging. Type the Change Man compile procedure to use to compile/link the program. If only one procedure is available for the language, this field is in browse only mode. To use the compile procedure and options designated by your application administrator enter a? . The appropriate procedure and options are displayed in the related fields. The various compile parameters that you want in addition to the ones specified in the compile procedure (for non-designated component procedures).
COMPILE PROCEDURE
COMPILE PARMS
User Guide
6-9
Field
LINK EDIT PARMS
Description
The various linkage edit parameters that you want in addition to the ones specified in the compile and link edit procedure (for non-designated component procedures).
DB2 PRECOMPILE
YES
If you want to process your program source using the DB2 precompiler. (The Stage: DB2 Physical Subsystems panel is then displayed.)
NO
Do not use the DB2 precompiler. OTHER OPTIONS
Yes or No if additional user options are needed. If you type Yes , Change Man displays the Stage User Options panel (CMNUSR 01 ).
Press Enter. If batch stage has been selected, then a job will be submitted (the API job) which will in turn submit a compile and link edit if this is a source component. Should multiple source components be batch staged, then multiple compile and link edit jobs will be submitted with the job name incrementing to the next letter for each job submitted (A then B then C etc.). If you selected another component to be staged, the Stage: Compile and Link Edit panel is displayed again for the next component you selected. Otherwise, Change Man returns you to either Stage from Development panel or Stage Options panel.
6-10
User Options
If you typed Yes, in the Other Options field of the Stage Compile and Link Edit panel (CMNSTG04), the following panel appears when you have finished entering information in the panel and pressed Enter.
CMNUSR01 -------------------- STAGE: USER OPTIONS ----------------------------COMMAND ===> NAME: ALLIO COMPILE ONLY CICS PRE-COMPILE EASYTRIEVE NO NAME USER OPTION 07 USER OPTION 09 USER OPTION 11 USER OPTION 13 USER OPTION 15 USER OPTION 17 USER OPTION 19 TYPE: SRC ===> ===> ===> y ===> n ===> n ===> ===> ===> ===> ===> LANGUAGE: ASM ENTRY DROP USER USER USER USER USER USER USER USER TO DLITCBL ===> INCLUDE STMTS ===> OPTION 06 ===> y OPTION 08 ===> y OPTION 10 ===> n OPTION 12 ===> OPTION 14 ===> OPTION 16 ===> OPTION 18 ===> OPTION 20 ===>
Use Y or N to select or deselect additional processing options; Press ENTER to continue; Enter END command to exit.
The Stage User Options panel (CMNUSR01) allows you to incorporate up to 20 additional user options within a Change Man compiling procedure. The variables are passed when the skeleton is file tailored. Request to expand a user option within the skeleton by typing either a Y or N next to any row of the list.
User Guide
6-11
MASS COMPILE AND LINK EDIT COMPONENTS

If you type an * , in the Member field of the Stage From Development panel (CMNSTG02), finished entering the appropriate information in the other fields of the panel and pressed Enter, the Stage Mass Compile and Link Edit panel (CMNSTG05) appears.
CMNSTG05 ------------- STAGE: MASS COMPILE AND LINK EDIT ---------------------COMMAND ===> PACKAGE ID: NAVI000011 LIBRARY TYPE: LANGUAGE: DATASET NAME: COMPILE PROCEDURE COMPILE PARMS LINK EDIT PARMS DB2 PRE-COMPILE OTHER OPTIONS SUPPRESS HISTORY STATUS: DEV INSTALL DATE: 19990711
SRC - Source Code ASM WSER83.TEST.JCL ===> ===> ===> ===> ===> ===> CMNASM (Blank for list)
NO YES NO
(Y/N) (Y/N to display other options) (Y/N to use above criteria for all selected components in place of any history data)
6-12
Staging from Packages
Staging Other Type Components Panel

This panel is used to enter the job statement information for staging other library types. Other library types refer to the library types within the global and application library type lists that have no value entered under the like field.
CMNSTG09 ----------------- STAGE: OTH COMPONENTS -----------------------------COMMAND ===> PACKAGE ID: NAVI000005 DATASET NAME: WSER85.TEST.JCL LIBRARY TYPE: OTH JOB STATEMENT INFORMATION: ===> //WSER85I JOB (X170,374),CHANGE MAN, ===> // MSGCLASS=9,NOTIFY=WSER85,TIME=1 ===> /*JOBPARM S=ESA5 ===> // JCLLIB ORDER=(WSER85.CHGMAN.PROCLIB) STATUS: DEV INSTALL DATE: 19971230
<=== CHANGE ACCORDINGLY_____ <=== CHANGE ACCORDINGLY_____ <=== CHANGE ACCORDINGLY_____ <=== CHANGE ACCORDINGLY_____
Complete the JOB statement for the batch job that Change Man submits to compile (and link edit) your component. Optionally, you can enter JES3 FORMAT and MAIN statements. Change Man submits the job to execute the appropriate procedure for your component. If you selected another component to be staged, the Stage: Compile and Link Edit panel displays again for the next component you selected. Otherwise, Change Man returns you either to the Stage from Development panel or the Stage Options panel.
STAGING FROM PACKAGES

Option 2 of the Stage Options panel is used for status review and staging or restaging of components already listed in a stage request component list. From the panel, you can: Display the contents of the change package. Check the stage status for each component. Sort by any field in ascending order, using the Sort command with the keywords Name or Member. Then, issue a Locate command to find a component name. For source code components:
User Guide
6-13
Restage (recopy, compile and link edit) updated source code components from development libraries into the Change Man staging libraries. Stage (copy, compile and link edit) source code components that were copied forward from another change package and checked out from baseline. Recompile (compile and link edit) from the staging libraries source code components that were previously staged. (This does not include the copy step as performed in the stage command.) Display source and load relationships for source components. For source code and other components: Stage (copy) components that were copied forward from another change package and checked out from baseline. Restage (recopy) updated components from development libraries into the Change Man staging libraries. Delete components from the staging libraries. Edit staging libraries. Browse components. Provide a history (profile) of the components. For all component types: Edit and stage components in the staging libraries. Delete component from staging libraries. Browse components. Provide a history (profile) of the components. To stage package components, take the following steps:
6-14
Select option 2 on the Stage Options panel. The following panel displays.
CMNSTG01 ---------------- STAGE: NAVI000005 COMPONENTS ------ ROW 1 TO 4 OF 4 COMMAND ===> SCROLL ===> PAGE NAME TYPE STATUS CHANGED PROCNAME ID REQUEST s_ CPXLOAD JCL CHECKOUT 19970818 145338 WSER85 s_ HOUSKEEP JCL CHECKOUT 19970818 145338 WSER85 s_ IEBCOPY JCL CHECKOUT 19970818 145338 WSER85 __ REPORTS JCL CHECKOUT 19970818 145338 WSER85 ******************************* Bottom of data ******************************
Type the component line command and press Enter.
If the selection list parameters (Selection List Parameters panel) has the confirm request field set to YES and if you want to save your source code changes without compiling: first, process all panels (staging comparison report disposition, history panel, and so forth) and then press PF3 or type End at the Stage: Compile and Link Edit panel. Although this results in a *WARNING in the request column and an *INCOMP in the status column, all your changes are saved. For each source code component staged, the Stage: Compile and Link Edit panel displays for each selected component.
Source to Load Relationship Panel

The Source to Load Relationship panel appears when you type SL on a line command of a source component at the Stage Package Components panel. It displays all the load components related to the selected source component.
CMNSR2LD ---------------- SOURCE TO LOAD RELATIONSHIP ------------------------COMMAND ===> SCROLL ===> PAGE Press END command to exit. PACKAGE ID: NAVI000005 SOURCE NAME: ALLIO LIB TYPE: SRC SETSSI: 84561254 RELATED LOAD MODULES: NAME ALLIO TYPE STATUS LOD ACTIVE PROMOTION 1 CHANGED 19970701 ID WSER85 SETSSI 84562236 STATUS: DEV INSTALL DATE: 19971230
This is an information panel for viewing. Once you have browsed the information, press PF3 or type End . You are returned to the Stage Package Components panel.
User Guide
6-15
User ID Work List Panel

This panel displays when you enter UL as a line command for a component on the Stage Package Components panel. It displays all the user IDs that have acted on the selected component.
Staging Using Package Parameters

With staging option 3, you can use the following entities to narrow the package driven list: Component name Component type Component status Changed from and to dates Language name for SRC or LIKE SRC components Procedure name TSO ID List display mode
6-16
Component List Parameters

With option 3 you can filter those components that will be displayed (based on the criteria given on the panel) when the package driven list (option 2 - package) is selected from the Stage Options panel.
CMNSTG12 ----------------- COMPONENT LIST PARAMETERS ----------------------OPTION ===> PACKAGE ID: NAVI000005 STATUS: DEV INSTALL DATE: 19971230
SPECIFY SELECTION CRITERIA: COMPONENT NAME ===> IEBCOPY COMPONENT TYPE ===> JCL LANGUAGE ===> COMPONENT STATUS ===> 1 CHANGED FROM DATE TO DATE COMPILE PROCEDURE TSOID SHORT OR LONG DISPLAY CONFIRM REQUEST SUPPRESS MESSAGES COMPARISON REPORT ===> ===> ===> ===> ===> ===> ===> ===>
(1-Active, 2-Incomplete, 3-Checkout, 4-Inactive) (YYYYMMDD) (YYYYMMDD)
WSER85 L YES YES NO
(S-Short, L-Long) (Y/N) (Y/N; applies to batch stage) (Y/N; applies to edit in stage)
Type in entries in each of the required fields. The table below may help you complete the fields on the panel. Field
COMPONENT STATUS CHANGED FROM/TO DATE COMPILE PROCEDURE TSOID
Description
Type the status of the components to display. Type the range of dates in yyyymmdd to view a list of components that have been changed with in the specified period. Type the compiling procedure for the components to be displayed.
Type the user ID to display all components that belong to the specific user ID.
User Guide
6-17
Field
SHORT OR LONG DISPLAY
Description
Short Type S to display the basic information: name, library type, status, change date and time, language, procedure name, ID, and request. Long Type L to display data set organization, data set name, and target loadlib, in addition to the information displayed by entering S .
CONFIRM REQUEST
YES
Before you stage a component, a panel displays information about the pending stage so that you can confirm your actions. The panel display also includes historical information about the component you are staging, lists of other packages that contain the component you are Staging, confirmation panels for all component deletions, and also controls the display of confirmation messages for staging functions.
NO
Bypasses confirmation panels for all staging activities, but might improve processing time for component staging.
Note:As of version 4.1.6, this field no longer controls the display of the comparison report.
SUPPRESS MESSAGES COMPARISON REPORT Indicate whether you want to receive messages during batch staging. Indicate whether you want to display the comparison report. The display will be immediately followed by a screen offering print options.
6-18
AUDITING PACKAGES
This chapter explains how to use the Change Man audit function in order to ensure synchronization of components in an evolving package. Components that are not or have not been synchronized are considered out-of-synch.
CHANGE MAN AUDIT FUNCTION

The Change Man audit function allows you to ensure synchronization of components in an evolving package with baseline libraries and other participating packages. Based on the package master and the impact analysis database, the audit function inspects the staging libraries of a package for out-of-synch conditions. Out-of-synch conditions could result from: copybooks being modified after compiling the source component that calls them load module being modified after the composite load component that calls them has been link edited a package containing a load component that does not match its source component
Also, audit flags components of a package as out-of-synch for: not being active copied, but not staged a designated compile procedure was not used while staging a source component
The Role of the Impact Analysis Database

The audit function accesses the Impact Analysis database. This database maintains the inherent, pre-existing component relationships. The relationship reported in impact analysis database reflects the existing relationship with the application baseline environment.
7-1
7 Auditing Packages
SETTING PARAMETERS TO DETERMINE THE FOCUS OF THE AUDIT

The parameters that you and your administrator set dictates the focus of your audit. That is, audit determines which package to audit, which out-of-synch condition to flag, and whether to update the packages return code in the package master. The following criteria determines the focus of your audit, which you select on the Audit Change Package panel: The package level (simple, complex, super, or participating) of the package Auditing the participating package as a simple, as a primary package, or by department number Auditing staging libraries only or the corresponding baseline libraries Auditing a staging cross applications
NOTES If auditing staging libraries only, the audit return code is not updated.
The Settings of Your Administrator Effects on Audit

Your Change Man administrator can set specific global and application parameters that affect your audit. These parameters include the audit level, the installation date for processing participating packages, department number, and the order of defining the application library types. Although you may not have access to the administrator options that allow you to set these parameters, this section provides you with the information about their effects on audit. NOTES Speak with your administrator for further information about setting these parameters.
7-2
Setting Parameters to Determine the Focus of the Audit
Audit Level
Your package must pass an audit before you can freeze it for promotion or installation. For your package to pass an audit, the generate audit return code, must not exceed the value specified in the audit level set by your application administrator. If the audit level is...
0
Then...
audit is optional, and you can promote your package before you freeze it. to freeze your package, you must audit it. Any return code, except abend, is acceptable. the return code must not exceed 12. This return code indicates that there are no out-of-synch conditions within the staging libraries of the package. audit is required and the return code must not exceed eight. This return code indicates that there are no out-of-synch conditions to the staging and baseline libraries. the return code must not exceed four. This return code indicates that there are no out-of-sync condition to the staging and baseline libraries, but at least, one component in a staging library is a duplicate of the corresponding baseline component. the return code must not exceed zero. It indicates that there are no out-of-sync conditions to the staging and baseline libraries. Also, there are no duplicate (not modified) components in the staging libraries. Some components unknown to Change Man, components without ISPF statistics, or unparsable load modules are flagged as out-of-sync but allowed to pass the audit.
Process Participating Packages by Installation Date

If your site plans software changes months ahead and installs packages regularly, then your global administrator should set the Process Participating Packages by Install Date parameter, on the Global Parameters panel (CMNGGP02), to Yes. Packages that will be installed earlier or simultaneously with the package that you want to audit will be included in the audit report. Presumably, participating packages with later installation dates are in early development stages. If these participating packages are included, they will generate invalid out-of-sync conditions. Managing Change by installation date results in staging libraries being placed in descending order by installation date in concatenation lists. The compile and link-edit job procedures use these lists. Having staging libraries in descending order ensures the latest copybooks and called load module are included during staging and audit.
User Guide
7-3
7 Auditing Packages
Department Number
Your application administrator can restrict your creation of a new package to be based on department number. This is accomplished when the application administrator sets the Require Department Number parameter, on the Global Parameters panel (CMNGGP02), to Yes. When packages have the same department number, they may include functional subsystems changes of your application and can be audited as a group. Complex or super packages may have participating packages with different department numbers. When the application administrator sets Require Department Number parameter to Yes, audit process can base its process on the department number of the participating package that you want to audit.
Application Library Types Order

The order the library types are defined in your application determines the order autoresolve, recompile, and relink jobs are submitted. See Audit Auto-Resolve on page 7-56.
ACCESSING THE AUDIT CHANGE PACKAGE PANEL

To audit a change package and generate an audit report that provides information about your audit, you must access the Audit Change Package panel (CMNAUDIT). This panel is accessed from Build Options panel.
CMNBUILD ----------------------- BUILD OPTIONS ------------------------------OPTION ===> 0 1 2 3 4 5 6 7 8 9 B C L S Z Dates - Display the installation calendar Create - Create a new package Update - Update package information Custom - Create, update, approve or review custom forms Utility - Rename and Scratch information Checkout - Check out components from baseline or promotion Stage - Stage, edit, browse and delete components Audit - Audit a package Recompile - Recompile source code from baseline or promotion Relink - Relink load modules Browse - Browse\print\copy baseline or promotion Compare - Compare staging to baseline or promotion Listing - Browse compressed listings Scan - Scan baseline for character strings Compress - Compress change package Staging Libraries
To display the Audit Change Package panel (CMNAUDIT):
7-4
Accessing the Audit Change Package Panel
From the Build Options panel, type 7 (Audit) and press ENTER.
CMNAUDIT---------------------- AUDIT CHANGE PACKAGE ---------------------------PACKAGE ID AUDIT STAGING LIBRARIES ONLY AUTO RESOLVE OF OUT-OF-SYNCHS INCLUDE HISTORY RECORDS FORMAT REPORT FOR PRINTING AUDIT PARTICIPATING PACKAGE AS A SIMPLE PACKAGE AS A PRIMARY PACKAGE BY DEPARTMENT NUMBER CROSS APPLICATION AUDIT ===> ===> ===> ===> ===> ===> ===> ===> ===> NAVI000011 NO NO NO NO NO NO NO NO
(Y/N) (Y/N) (Y/N) (Y/N) (Y/N) (Y/N) (Y/N) (Y/N) - (Simple package only)
JOB STATEMENT INFORMATION: ===> //WSER83G JOB (X170,374),CHANGE MAN, ===> // MSGCLASS=9,NOTIFY=WSER83,TIME=1 ===> /*JOBPARM S=ESA5 ===> // JCLLIB ORDER=(WSER83,CHGMAN.PROLIB)
<=== <=== <=== <===
CHANGE CHANGE CHANGE CHANGE
ACCORDINGLY______ ACCORDINGLY______ ACCORDINGLY______ ACCORDINGLY______
Fields of the Audit Change Package Panel

This section describes the fields of the Audit Change Package panel (CMNAUDIT) and the value that you may type in the fields. NOTES No is the default value for the fields that require you to type Yes or No. PACKAGE ID The package ID of the package that you wish to audit (a simple package, a complex or super package, or a participating package). For example, in the CMNAUDIT panel, shown above, the user typed NAV000011 as the package ID. AUDIT STAGING LIBRARIES ONLY This field indicates whether you want to check for out-of-sync conditions in your staging libraries only or in the staging and baseline libraries. If you type...
No Yes
Then audit...
checks for out-of-synch conditions in the staging and baseline libraries. checks for out-of-synch conditions in the staging libraries only.
AUTO RESOLVE OF OUT-OF-SYNCHS
User Guide
7-5
7 Auditing Packages
Audit can identify every source code program that uses a copybooks, which is a component of a package. Since Change Man knows these relationships, this field allows you to indicate if you want audit to automatically resolve out-of-synch conditions in copybooks changes and subroutine modifications. This applies to composite load modules that have statistically link-edited called load modules. If you type...
No Yes
Then audit...
reports out-of-synch conditions only reports out-of-synch conditions and submits recompile and relink jobs, and resolves SYNCH2, SYNCH4, SYNCH5, SYNCH7, SYNCH8, SYNCH9, SYNCH15, and SYNCH16 conditions.
INCLUDE HISTORY RECORDS This field allows you to include or exclude history records in the Audit Report. If you type...
No Yes
Then audit...
will not process history information when generating the Audit Report. extracts component history for each staged component and include it in the Audit Report.
FORMAT REPORT FOR PRINTING This field allows you to customize your Audit Report. If you type...
No
Then audit...
formats the Audit Report for browsing. The text starts in column one and blank lines separate the header and sections of the audit report. formats the Audit Report for printing. This first character is an ASA printer spacing control character that controls the vertical printer motion of your Audit Report.
Yes
AUDIT PARTICIPATING PACKAGE This field allows you to process the participating packages: as a simple package as a primary package
7-6
Accessing the Audit Change Package Panel
by department number
AS A SIMPLE PACKAGE This field allows you to elect whether you wish to audit the specified participating package as a simple package. If you type... No Yes Then audit...
will not process the specified participating package as a simple package. processes the specified participating package as a simple package. Note: You may use this option if the participating package is built as a stand-alone package. Also, select this option if you know the contents of the package and can filter out erroneous outof-synch conditions.
AS A PRIMARY PACKAGE This field allows you to elect whether you wish to audit the specified package as a primary package. If you type...
No Yes
Then audit...
will not process participating packages as a primary package. processes the specified participating package, with regard to other participating packages, as the primary package.
BY DEPARTMENT NUMBER This field allows you to elect whether you wish to audit other participating packages that have the same department number as the specified package. If you type...
No
Then audit...
will not process other participating packages that have the same department number as the specified packages. processes the specified participating packages, with regard to other participating packages, by the department number of the specified package
Yes
CROSS APPLICATION AUDIT
User Guide
7-7
7 Auditing Packages
This field allows you to elect whether you wish to process the components of a simple package with baseline libraries of all applications. This field applies to simple packages only. If you type...
No Yes
Then audit...
will not process the simple package. processes source and copybook components of your simple package with other applications baseline libraries.
The job statement information appears at the bottom of the Audit Change Package panel. Before submitting your audit, verify that the JCL cards have your desired information.
AUDITING A PACKAGE
When auditing components of a package, you should take the following sequence: 1 Audit the staging libraries. The audit job will run faster and the out-of-synch conditions will focused on the relationships between package components. 2 3 Audit staging and baseline libraries. When the out-of-synch condition are resolved through setting the Autoresolve field to Yes or re-staging source components, audit the staging and baseline libraries. Audit highlights the impact of the package on the application. If there are out-ofsynch conditions in the baseline libraries, audit increases the number of like-LOD type components that are recompiled baseline components with changed copybooks and relinked baseline composite load components with statically linkedited changed load modules. NOTES Unless otherwise indicated, the default value (No) is assumed to be the value of the parameters on the Audit Change Package panel.
7-8
Auditing A Simple Package
AUDITING A SIMPLE PACKAGE

The components of a simple package are not dependent on components in other packages. However, a simple package may contain copybooks called-in source components that are not included in the simple package. Also, it may contain load modules that are statically link-edited in composite load modules that are not part of the simple package. Such baseline source and load components may belong to the same or different applications under Change Man control. If the staging and baseline libraries are audited, the package audit return code is updated in the package master. This section describes the parameters that you must set in order to audit a simple package.
Auditing Staging Libraries Only

To audit, check for, and cite out-of-synch conditions between components in the staging libraries of a specified simple package, take the following steps: 1 In the PACKAGE ID field of the Audit Change Package panel, type the name of your simple package (for example, NAVI000005). In the AUDIT STAGING LIBRARIES ONLY field, type YES. Verify that the information in the JOB STATEMENT INFORMATION fields is correct. Your panel should look similar to the following screen.
2 3
CMNAUDIT---------------------- AUDIT CHANGE PACKAGE ---------------------------PACKAGE ID AUDIT STAGING LIBRARIES ONLY AUTO RESOLVE OF OUT-OF-SYNCHS INCLUDE HISTORY RECORDS FORMAT REPORT FOR PRINTING AUDIT PARTICIPATING PACKAGE AS A SIMPLE PACKAGE AS A PRIMARY PACKAGE BY DEPARTMENT NUMBER CROSS APPLICATION AUDIT ===> ===> ===> ===> ===> ===> ===> ===> ===> NAVI000005 YES NO NO NO NO NO NO NO
<=== <=== <=== <===
Press ENTER. A message similar to the following appears:

WSER010X (JOB03581) submitted CN(INTERNAL)
The audit function
User Guide
7-9
7 Auditing Packages
processes the specified simple package and its staging libraries flags out-of-synch conditions amongst the components of the staging libraries Afterwards, a message appears indicating that your audit is complete. 5 At this point, you can retrieve and review your generated audit report for out-ofsynch conditions. (See Accessing Submitted Audit Reports on page 7-55.)
Auditing Staging Libraries and Baseline Libraries of the Package Application

To audit, check for, and cite out-of-synch conditions between components in the staging libraries of a simple package, and components of staging libraries against the components of the baseline libraries of the package application, take the following steps: 1 In the PACKAGE ID field of the Audit Change Package panel, type the name of your package (for example, NAVI000005). Verify that the information in the JOB STATEMENT INFORMATION fields are correct. Your panel should look similar to the following:.
CMNAUDIT---------------------- AUDIT CHANGE PACKAGE ---------------------------PACKAGE ID AUDIT STAGING LIBRARIES ONLY AUTO RESOLVE OF OUT-OF-SYNCHS INCLUDE HISTORY RECORDS FORMAT REPORT FOR PRINTING AUDIT PARTICIPATING PACKAGE AS A SIMPLE PACKAGE AS A PRIMARY PACKAGE BY DEPARTMENT NUMBER CROSS APPLICATION AUDIT ===> ===> ===> ===> ===> ===> ===> ===> ===> NAVI000005 NO NO NO NO NO NO NO NO
<=== <=== <=== <===
Press ENTER. A message similar to the following appears:

The audit function checks for out-of-synch conditions amongst the components of the staging libraries
7-10
Auditing A Simple Package
checks for out-of-synch conditions between the components of the staging libraries and the components of the corresponding baseline libraries of the package application updates the return code of the specified simple package in the package master Afterwards, a message appears indicating that your audit is complete. 4 At this point, you can retrieve and review your generated audit report for out-ofsynch conditions and return codes. (See Accessing Submitted Audit Reports on page 7-55.)
Auditing Staging Libraries of the Package and Baseline Libraries of All Applications
To audit, check for, and cite out-of-synch conditions between components in the staging libraries of a simple package, and components of staging libraries against components of the baseline libraries of all application, take the following steps: 1 In the PACKAGE ID field of the Audit Change Package panel, type the name of your simple package (for example, NAVI000005). In the CROSS APPLICATION AUDIT field, type YES Verify that the information in the JOB STATEMENT INFORMATION fields are correct. Your panel should look similar to the following:
2 3
CMNAUDIT---------------------- AUDIT CHANGE PACKAGE ---------------------------PACKAGE ID ===> AUDIT STAGING LIBRARIES ONLY ===> AUTO RESOLVE OF OUT-OF-SYNCHS ===> INCLUDE HISTORY RECORDS ===> FORMAT REPORT FOR PRINTING ===> AUDIT PARTICIPATING PACKAGE NAVI000005 NO NO NO NO
(Y/N) (Y/N) (Y/N) (Y/N)
AS A SIMPLE PACKAGE ===> NO AS A PRIMARY PACKAGE ===> NO BY DEPARTMENT NUMBER ===> NO CROSS APPLICATION AUDIT ===> YES JOB STATEMENT INFORMATION: ===> //WSER83G JOB (X170,374),CHANGE MAN, ===> // MSGCLASS=9,NOTIFY=WSER83,TIME=1 ===> /*JOBPARM S=ESA5 ===> // JCLLIB ORDER=(WSER83,CHGMAN.PROLIB)
(Y/N) (Y/N) (Y/N) (Y/N) - (Simple package only)
<=== <=== <=== <===
Press ENTER. A message similar to the following appears: WSER010X (JOB03581) submitted CN(INTERNAL) The audit function
User Guide
7-11
7 Auditing Packages
processes the specified simple package checks for out-of-synch conditions amongst the components of the staging libraries checks for out of synch conditions between the components of the staging libraries and components of the corresponding baseline libraries of all applications updates the return code of the specified simple package in the package master Afterwards, a message appears indicating that your audit is complete. 5 At this point, you can retrieve and review your generated audit report for out-ofsynch conditions and return codes. (See Accessing Submitted Audit Reports on page 7-55.)
AUDITING A COMPLEX OR SUPER PACKAGE

Participating packages are connected through a complex or super package. Also, they share related components. When you elect to audit a complex or super package, you are auditing its participating packages, excluding the baselined participating packages. This section describes parameters that you must set in order to audit a complex or super package. When auditing components of a package, you should take the following sequence: 1 Audit the staging libraries. The audit job will run faster and the out-of-synch conditions will focused on the relationships between package components. 2 When the out-of-synch condition are resolved through setting the Autoresolve field to Yes or re-staging source components, audit the staging and baseline libraries. Audit highlights the impact of the package on the application. If there are out-ofsynch conditions in the baseline libraries, audit increases the number of like-LOD type components that are recompiled baseline components with changed copybooks and relinked baseline composite load components with statically linkedited changed load modules.
7-12
Auditing A Complex or Super Package
NOTES No is the default value of the parameters on the Audit Change Package panel.
Auditing Staging Libraries of Participating Packages

This section describes the steps that you must take to audit, check for, and cite out-ofsynch conditions among the components in the staging libraries of all non-baselined participating packages. 1 In the PACKAGE ID field of the Audit Change Package panel, type the name (for example, NAVI000001) of the complex or super package that you wish to audit. In the AUDIT STAGING LIBRARIES ONLY field, type YES. Verify that the information in the JOB STATEMENT INFORMATION fields is correct, and press ENTER. A message similar to the following appears: WSER010X (JOB03581) submitted CN(INTERNAL) In the complex or super package, audit checks for out-of-synch conditions amongst the components of the staging libraries. A message appears indicating that your audit is complete. 4 At this point, you can retrieve and review your generated audit report for out-ofsynch conditions. (See Accessing Submitted Audit Reports on page 7-55.)
2 3
Auditing Staging and Baseline Libraries of Participating Packages

To audit, check for, and cite out-of-synch conditions among the components in the staging libraries and the corresponding baseline libraries of all participating packages of the specified complex or super package, take the following steps: 1 In the PACKAGE ID field of the Audit Change Package panel, type the name of the complex or super package that you wish to audit. Verify that the information in the JOB STATEMENT INFORMATION fields are correct and press ENTER. A message similar to the following appears WSER010X (JOB03581) submitted CN(INTERNAL) and audit processes the packages defined in the complex or super package
User Guide
7-13
7 Auditing Packages
updates the return code in the package master all non-baselined participating packages and for the specified package (complex or super) with the highest of the former return codes Afterwards, a message appears indicating that your audit is complete. 3 At this point, you can retrieve and review your generated audit report for out-ofsynch conditions and return codes. (See Accessing Submitted Audit Reports on page 7-55.)
Example: Auditing Staging and Baseline Libraries of Participating Packages

In the following example, we assume that NAVI000001 is a complex or super package. NAVI000002 through NAVI000008 are its participating packages with the following attributes: Package ID Installation Date Department Number Status
NAVI000002 NAVI000003 NAVI000004 NAVI000005 NAVI000006 NAVI000007 NAVI000008
1998/06/15 1998/07/01 1998/07/15 1998/08/01 1998/09/01 1998/09/15 1998/10/01 2000 5000 2000 2000 4000 5000
Baselined Development Development Development Development Development Development
In this example, we select package NAVI000001 in order to audit it as a complex or super package: 1 2 In the PACKAGE ID field of the Audit Change Package panel, type NAVI000001. Verify that the information in the JOB STATEMENT INFORMATION fields are correct, and press ENTER. The audit function processes NAVI000003 through NAVI000008 package and its staging libraries
7-14
Auditing a Participating Package as a Simple Package
excludes NAVI000002 as it is baselined updates the audit return code in the package master of NAVI000001 and NAVI000003 through NAVI000008 and the log file for their audit activity
AUDITING A PARTICIPATING PACKAGE AS A SIMPLE PACKAGE

Auditing a participating package as a simple package is similar to auditing a simple package. When auditing components of a package, you should take the following sequence: 1 Audit the staging libraries. The audit job will run faster and the out-of-synch conditions will focused on the relationships between package components. 2 When the out-of-synch condition are resolved through setting the Autoresolve field to Yes or re-staging source components, audit the staging and baseline libraries. Audit highlights the impact of the package on the application. If there are out-ofsynch conditions in the baseline libraries, audit increases the number of like-LOD type components that are recompiled baseline components with changed copybooks and relinked baseline composite load components with statically linkedited changed load modules. NOTES Unless otherwise indicated the default value (No) is assumed to be the value of the parameters on the Audit Change Package panel. Also, we assume that we have a complex or super package consisting of participating packages. One of which is specified for auditing.
Staging Libraries of Participating Packages

To audit, check for, and cite out-of-synch conditions between components in the staging libraries of a specified participating package, take the following steps: 1 In the PACKAGE ID field of the Audit Change Package panel, type the name of your participating package that you wish to audit a simple package. The participating package is defined in a complex or super package. In the AUDITING STAGING LIBRARIES ONLY, type YES
User Guide
7-15
7 Auditing Packages
3 4
In the AUDITING PARTICIPATING PACKAGE AS A SIMPLE PACKAGE field, type YES Verify that the information in the JOB STATEMENT INFORMATION fields are correct, and press Enter. A message similar to the following appears: WSER010X (JOB03581) submitted CN(INTERNAL) The audit function processes the specific participating package and its staging libraries excludes all other participating packages defined in the complex or super package Afterwards, a message appears indicating that your audit is complete.
At this point, you can retrieve and review your generated audit report for out-ofsynch conditions and return codes. (See Accessing Submitted Audit Reports on page 7-55.)
Staging and Baseline Libraries of Participating Packages

This section describes the steps that you must take to audit, check for, and cite out-ofsynch conditions components of the staging libraries of the participating package as a simple package and the corresponding baseline libraries. 1 In the PACKAGE ID field of the Audit Change Package panel, type the name of your participating package that you will audit as a simple package. In the AUDITING PARTICIPATING PACKAGE AS A SIMPLE PACKAGE field, type YES Verify that the information in the JOB STATEMENT INFORMATION fields are correct, and press ENTER. A message similar to the following appears: WSER010X (JOB03581) submitted CN(INTERNAL) The audit function processes the specific package and its staging libraries and all corresponding baseline libraries excludes all other participating packages defined in the complex or super package
2 3
7-16
Auditing a Participating Package as a Simple Package
updates the return code in the package master of the specified participating package and the log file for audit activity of the specified participating package Afterwards, a message appears indicating that your audit is complete. 4 At this point, you can retrieve and review your generated audit report for out-ofsynch conditions and return codes. (See Accessing Submitted Audit Reports on page 7-55.)
Example: Auditing a Participating Package as a Simple Package

1998/06/15 1998/07/01 1998/07/15 1998/08/01 1998/09/01 1998/09/15 1998/10/01 2000 5000 2000 2000 4000 5000
We will select and audit a participating package (NAVI000005) as a simple package: 1 2 In the PACKAGE ID field of the Audit Change Package panel, type NAVI000005. In the AUDITING PARTICIPATING PACKAGE AS A SIMPLE PACKAGE field, type YES.
The audit function processes NAVI000005 package and its staging libraries excludes NAVI000002 (a baselined participating package), NAVI000003, NAVI000004, and NAVI000006 through NAVI000008 updates the audit return code in the package master of NAVI000005 and the log file for its audit activity
User Guide
7-17
7 Auditing Packages
AUDITING A PARTICIPATING PACKAGE AS A PRIMARY PACKAGE

When speaking about participating packages, we stress that every participating package has its own installation date, and two participating packages can have different installation dates. Thus, the designation of a primary package makes it possible for it to use the date and time as a delineating factor in filtering associated participating packages. When auditing components of a package, you should take the following sequence: 1 Audit the staging libraries. The audit job will run faster and the out-of-synch conditions will focused on the relationships between package components. 2 When the out-of-synch condition are resolved through setting the Autoresolve field to Yes or re-staging source components, audit the staging and baseline libraries. Audit highlights the impact of the package on the application. If there are out-ofsynch conditions in the baseline libraries, audit increases the number of like-LOD type components that are recompiled baseline components with changed copybooks and relinked baseline composite load components with statically linkedited changed load modules. NOTES You might not have access privilege to the Administration option of the Primary Options Menu. Therefore, you may need to check with your application or global administrator about the user restrictions. Unless otherwise indicated the default value (No) assume to be the value of the parameters on the Audit Change Package panel. Also, we assume that we have a complex package consisting of participating packages, including the primary package.
Staging Libraries Only (with Installation Date Set to No)

This section describes the steps that you must take to audit, check for, and cite out-ofsynch conditions among components in the staging library of a specified participating package that you will audit as a primary package.
7-18
Auditing a Participating Package as a Primary Package
NOTES The global administrator has not changed the default value (No) of the Process Participating Packages by Installation Date parameter. 1 In the PACKAGE ID field of the Audit Change Package panel, type the name of your participating package that you will audit as a primary package (for example, NAVI000005) In the AUDITING STAGING LIBRARIES ONLY, type YES. In the PROCESS PARTICIPATING PACKAGES A PRIMARY PACKAGE field, type YES Verify that the information in the JOB STATEMENT INFORMATION fields are correct, and press ENTER. A message similar to the following appears: WSER010X (JOB03581) submitted CN(INTERNAL) The audit function processes the specified primary package and its staging libraries examines components of other participating packages that are called in components of the primary package flags out-of-synch conditions for the specified package Afterwards, a message appears indicating that your audit is complete. 5 At this point, you can retrieve and review your generated audit report for out-ofsynch conditions and return codes. (See Accessing Submitted Audit Reports on page 7-55.)
2 3 4
Staging Libraries Only (with Installation Date Set to Yes)

This section describes the steps that you must take in order to audit, check for, and cite out-of-synch conditions among components in the staging library of a specified primary package. NOTES The global administrator has set the Process Participating Packages by Installation Date parameter to Yes. 1 In the PACKAGE ID field of the Audit Change Package panel, type the name of your participating package that you will audit as a primary package.
User Guide
7-19
7 Auditing Packages
2 3 4
In the AUDITING STAGING LIBRARIES ONLY, type YES. In the PROCESS PARTICIPATING PACKAGES A PRIMARY PACKAGE field, type YES. Verify that the information in the JOB STATEMENT INFORMATION fields are correct, and press ENTER. A message similar to the following appears: WSER010X (JOB03581) submitted CN(INTERNAL) The audit function processes the specified package and its staging libraries examines called components of only those other participating packages that have the same or earlier installation date than that of the primary package excludes participating packages whose installation dates are greater than that of the specified primary package flags out-of-synch conditions for the specified primary package Afterwards, a message appears indicating that your audit is complete.
Staging and Baseline Libraries (with Installation Date Set to No)

This section describes the steps that you must take in order to audit, check for, and cite out-of-synch conditions among components of the staging libraries of the participating package as a primary package, and the corresponding baseline libraries. NOTES The global administrator has not change the default value (No) of the Process Participating Packages by Installation Date parameter. 1 In the PACKAGE ID field of the Audit Change Package panel, type the name of your participating package that you will audit as a primary package (for example, NAVI000005). In the PROCESS PARTICIPATING PACKAGES A PRIMARY PACKAGE field, type YES Verify that the information in the JOB STATEMENT INFORMATION fields are correct, and press Enter. A message similar to the following appears:
2 3
7-20
WSER010X (JOB03581) submitted CN(INTERNAL) The audit function: processes the specified primary package, its staging libraries, and the corresponding baseline libraries examines components of other participating packages that are called in components of the primary package flags out-of-synch conditions for the specified primary packages updates the audit return code in the package master for the primary participating package and the log file for audit activity. Afterwards, a message appears indicating that your audit is complete. 4 At this point, you can retrieve and review your generated audit report for out-ofsynch conditions and return codes. (See Accessing Submitted Audit Reports on page 7-55.)
Example: Auditing a Participating Package as a Primary Package (with Staging and Baseline Libraries)
1998/06/15 1998/07/01 1998/07/15 1998/08/01 1998/09/01 1998/09/15 1998/10/01 2000 5000 2000 2000 4000 5000
If you elect to audit NAVI000005 (a participating package of a complex or super package) as a primary package, then audit:
User Guide
7-21
7 Auditing Packages
processes NAVI000005 package and include its staging libraries excludes NAVI000002 staging libraries, since it is a baselined participating package processes the staging libraries of NAVI000003 through NAVI000008 for component that are called in components of the primary package NAVI000005 flags out-of-synch conditions for NAVI000005 updates the audit return code in the package master for the primary package (NAVI000005) and the log file for its audit activity
Staging and Baseline Libraries (with Installation Date Set to Yes)

This section describes the steps that you must take in order to audit, check for, and cite out-of-synch conditions amongst components of the staging libraries of the participating package as a primary package and the corresponding baseline libraries. NOTES The global administrator has set the Process Participating Packages by Installation Date parameter to Yes. 1 In the PACKAGE ID field of the Audit Change Package panel, type the name of your participating package that you will audit as a primary package (for example, NAVI000005). In the PROCESS PARTICIPATING PACKAGES A AS PRIMARY PACKAGE field, type YES Verify that the information in the JOB STATEMENT INFORMATION fields are correct, and press Enter. A message similar to the following appears: WSER010X (JOB03581) submitted CN(INTERNAL) The audit: processes the specified package, its staging libraries, and the corresponding baseline libraries examines participating packages whose installation dates are equal to or earlier than the installation date of the specified primary package for called components excludes participating packages whose installation dates are greater than the installation date of the specified primary packages
2 3
7-22
flags out-of-synch conditions for the specified primary packages updates the audit return code in the package master for the primary package and its log file for audit activity Afterwards, a message appears indicating that your audit is complete. 4 At this point, you can retrieve and review your generated audit report for out-ofsynch conditions and return codes. (See Accessing Submitted Audit Reports on page 7-55.)
Example: Auditing a Participating Package as a Primary Package (Installation Date Set to Yes)
1998/06/15 1998/07/01 1998/07/15 1998/08/01 1998/09/01 1998/09/15 1998/10/01 2000 5000 2000 2000 4000 5000
If you elect to audit NAVI000005 (a participating package of a complex or super package) as a primary package, and you know that the global administrator has set the Process Participating Packages by Installation Date parameter to Yes, then audit processes NAVI000005 package, its staging libraries, and corresponding baselined libraries excludes NAVI000002 (a baselined packaged) excludes NAVI000006 through NAVI000008 as their installation dates are later than NAVI000005
User Guide
7-23
7 Auditing Packages
processes NAVI000003 and NAVI000004 for called components in NAVI000005, because their installation dates are equal to or earlier than the installation date of NAVI000005 flags out-of-synch conditions for NAVI000005 updates the audit return code in the package master for the primary package (NAVI000005) and the log file for its audit activity
AUDITING A PARTICIPATING PACKAGE BY DEPARTMENT NUMBER

Auditing a participating package by department number allows you to group related release packages. Also, audit them separately from the other participating packages in a complex or super package. When auditing components of a package, you should take the following sequence: 1 Audit the staging libraries. The audit job will run faster and the out-of-synch conditions will focused on the relationships between package components. 2 When the out-of-synch condition are resolved through setting the Autoresolve field to Yes or re-staging source components, audit the staging and baseline libraries. Audit highlights the impact of the package on the application. If there are out-ofsynch conditions in the baseline libraries, audit increases the number of like-LOD type components that are recompiled baseline components with changed copybooks and relinked baseline composite load components with statically linkedited changed load modules. NOTES You might not have access privilege to the Administration option of the Primary Options Menu. Therefore, you may need to check with your application or global administrator about the user restrictions (See Setting Parameters to Determine the Focus of the Audit on page 7-2). Unless otherwise indicated the default value (No) assume to be the value of the parameters on the Audit Change Package panel. Also, we assume that we have a complex or super package consisting of participating packages. One is specified for auditing.
7-24
Auditing a Participating Package by Department Number
Staging Libraries Only (with Installation Date Set to No)

This section describes the steps that you must take in order to audit, check for, and cite out-of-synch conditions among components in the staging libraries of each participating package having the same department as the specified package. 1 In the PACKAGE ID field of the Audit Change Package panel, type the name of your participating package that you will audit (for example, NAVI000005). In the AUDITING STAGING LIBRARIES ONLY, type YES. In the PROCESS PARTICIPATING PACKAGES BY DEPARTMENT NUMBER field, type
YES
2 3
Verify that the information in the JOB STATEMENT INFORMATION fields are correct, and press ENTER. A message similar to the following appears: WSER010X (JOB03581) submitted CN(INTERNAL) The audit function: processes the specified package and its staging libraries processes the staging libraries of the other participating packages having the same department number as the specified package excludes participating packages having different department number that the specified package flags out-of-synch conditions for the all participating packages having the same department number as the specified package Afterwards, a message appears indicating that your audit is complete.
Staging Libraries Only (with Installation Date Set to Yes)

This section describes the steps that you must take in order to audit, check for, and cite out-of-synch conditions between components in the staging libraries of each participating packages that have the following attributes: the same department number as the specified package, and same or earlier installation date than that of the specified package.
User Guide
7-25
7 Auditing Packages
NOTES The global administrator has set the Process Participating Packages by Installation Date parameter to Yes. 1 In the PACKAGE ID field of the Audit Change Package panel, type the name of your participating package that you will audit as a primary package (for example, NAVI000005) In the AUDITING STAGING LIBRARIES ONLY, type YES. In the PROCESS PARTICIPATING PACKAGES BY DEPARTMENT field, type
YES
2 3 4
Verify that the information in the JOB STATEMENT INFORMATION fields are correct, and press ENTER. A message similar to the following appears: WSER010X (JOB03581) submitted CN(INTERNAL) The audit function: processes the specified package and its staging libraries processes the staging libraries of the other participating packages having the same department number as the specified package and the same or earlier installation dates excludes participating packages having different departments that the specified package excludes participating packages having a greater installation date that the specified package excludes baselined participating packages flags out-of-synch conditions for all participating packages having the same department number as the specified package and same or earlier installation dates. Afterwards, a message appears indicating that your audit is complete.
7-26
Staging and Baseline Libraries (with Installation Date Set to No)

This section describes the steps that you must take to audit, check for, and cite out-ofsynch conditions between components in the staging libraries of each participating package with the same department number as the primary package. NOTES The global administrator has set the Process Participating Packages by Installation Date parameter to No. 1 In the PACKAGE ID field of the Audit Change Package panel, type the name of your participating package that you will audit (for example, NAVI000005). In the PROCESS PARTICIPATING PACKAGES BY DEPARTMENT field, type
YES
2 3
Verify that the information in the JOB STATEMENT INFORMATION fields are correct, and press Enter. A message similar to the following appears: WSER010X (JOB03581) submitted CN(INTERNAL) The audit function: processes the specified package, its staging libraries, and the corresponding baseline libraries processes the staging and baseline libraries of the other participating packages having the same department number as the specified package excludes participating packages with department number different than the specified package excludes baselined participating packages flags out-of-synch conditions for participating packages having the same department number as the specified package updates the audit return code in the package master for all the participating packages with the same department of the specified package updates the log file for audit their activity. Afterwards, a message appears indicating that your audit is complete.
User Guide
7-27
7 Auditing Packages
Example: Auditing a Participating Package by Department Number

1998/06/15 1998/07/01 1998/07/15 1998/08/01 1998/09/01 1998/09/15 1998/10/01 2000 5000 2000 2000 4000 5000
In this example, we will select NAVI000005 (a participating package of a complex or super package) to audit the package by department number of the selected participating package: 1 2 In the PACKAGE ID field of the Audit Change Package panel, type NAVI000005. In the PROCESS PARTICIPATING PACKAGES BY DEPARTMENT field, type The audit function: processes packages (NAVI000003, NAVI000005, and NAVI000006) having the same department (2000), their staging libraries, and corresponding baseline libraries excludes NAVI000002, a baselined participating package excludes NAVI000004, NAVI000007, and NAVI000008, because their department numbers differ from the specified package (NAVI000005) flags out-of-synch conditions for NAVI000003, NAVI000005, and NAVI000006 packages
YES
7-28
Staging and Baseline Libraries (with Installation Date Set to Yes)

This section describes the steps that you must take to audit, check for, and cite out-ofsynch conditions between components in the staging libraries and the corresponding baseline libraries of each participating packages with: the same department number as the specified package same or earlier installation date as the specified package
NOTES The global administrator has set the Process Participating Packages by Installation Date parameter to Yes. 1 In the PACKAGE ID field of the Audit Change Package panel, type the name of your participating package that you will audit (for example, NAVI000005). In the PROCESS PARTICIPATING PACKAGES BY DEPARTMENT field, type
YES
2 3
Verify that the information in the JOB STATEMENT INFORMATION fields are correct, and press Enter. A message similar to the following appears: WSER010X (JOB03581) submitted CN(INTERNAL) The audit function processes the specified package, its staging libraries, and the corresponding baseline libraries processes the staging and baseline libraries of the other participating packages having the same department number and same or earlier installation dates as the specified package excludes participating packages with department numbers different than the specified package excludes participating packages with installation dates greater than the specified package excludes baselined participating package flags out-of-synch conditions for all participating packages having the same department number as the specified package and same or earlier installation dates
User Guide
7-29
7 Auditing Packages
updates the audit return code in the package master for participating packages having the same department number and same or earlier installation dates as the specified package updates the log file for the audit activity of the participating packages Afterwards, a message appears indicating that your audit is complete. 4 At this point, you can retrieve and review your generated audit report for out-ofsynch conditions and return codes. (See Accessing Submitted Audit Reports on page 7-55.)
Example: Auditing a Participating Package by Department Number (Installation Date Set to Yes)
1998/06/15 1998/07/01 1998/07/15 1998/08/01 1998/09/01 1998/09/15 1998/10/01 2000 5000 2000 2000 4000 5000
Also, we assume that the global administrator has set Process Participating Packages by Installation Date parameter to Yes. If you elect to audit NAVI000005 by its department number, audit processes NAVI000003 and NAVI000005 packages, their staging libraries, and the corresponding baseline libraries. These packages have the same department number (2000) and package NAVI000003 has an earlier installation date (1998/07/01) than the specified package. Also, audit excludes NAVI000002, since its a baselined participating package
7-30
Auditing All or a Group of Participating Packages
excludes NAVI00006 because its installation date is later thanNAVI000005 excludes packages (NAVI000004, NAVI000007, and NAVI000008) having department numbers are different than NAVI000005 flags out-of-synch conditions for NAVI000003 and NAVI000005 updates the audit return code in the package master for NAVI000003 and NAVI000005 packages and the log file for their audit activity
AUDITING ALL OR A GROUP OF PARTICIPATING PACKAGES

This section describes how to audit all or a group of participating packages defined in a complex or super package. When auditing components of a package, you should take the following sequence: 1 Audit the staging libraries. The audit job will run faster and the out-of-synch conditions will focused on the relationships between package components. 2 When the out-of-synch condition are resolved through setting the Autoresolve field to Yes or re-staging source components, audit the staging and baseline libraries. Audit highlights the impact of the package on the application. If there are out-ofsynch conditions in the baseline libraries, audit increases the number of like-LOD type components that are recompiled baseline components with changed copybooks and relinked baseline composite load components with statically linkedited changed load modules. NOTES You might not have access privilege to the Administration option of the Primary Options Menu. Therefore, you may need to check with your application or global administrator about the user restrictions (See Setting Parameters to Determine the Focus of the Audit on page 7-2). Unless otherwise indicated the default value (No) assume to be the value of the parameters on the Audit Change Package panel.
User Guide
7-31
7 Auditing Packages
Auditing Staging Libraries of all Participating Packages in a Complex or Super Package (with Installation Date Set to No)
To audit, check for, and cite out-of-synch condition between package components all participating packages in a complex or super package, take the following steps: 1 In the PACKAGE ID field of the Audit Change Package panel, type the name (for example, NAVI000005) of the participating package that you wish to audit. The package is defined in a complex or super package. In the AUDIT STAGING LIBRARIES ONLY field, type YES. Verify that the information in the JOB STATEMENT INFORMATION fields are correct, and press Enter. A message similar to the following appears:
2 3
The audit function: processes the staging libraries of all participating packages, defined in the complex or super package, of the specified package excludes staging libraries of the baselined participating packages flags out-of-synch conditions for all participating packages. 4 At this point, you can retrieve and review your generated audit report for out-ofsynch conditions and return codes. (See Accessing Submitted Audit Reports on page 7-55.)
Auditing Staging Libraries of a Group of Participating Packages in a Complex or Super Package (with Installation Date Set to Yes)
This section describes the steps that you must take in order to audit, check for, and cite out-of-synch conditions amongst components of the participating packages having the same or earlier installation date of the specified package NOTES We assume that the global administrator has set the Process Participating Packages by Installation Date parameter to Yes. 1 In the PACKAGE ID field of the Audit Change Package panel, type the name (for example, NAVI000005) of the participating package that you wish to audit. In the AUDIT STAGING LIBRARIES ONLY field, type YES.
7-32
Verify that the information in the JOB STATEMENT INFORMATION fields are correct, and press ENTER. A message similar to the following appears: WSER010X (JOB03581) submitted CN(INTERNAL) For each participating package that has the same or an earlier installation date than the specified package (for example, NAVI000005), the audit: processes the staging libraries excludes baselined participating packages flags out-of-synch conditions
Auditing Staging and Baseline Libraries of all Participating Packages in a Complex or Super Package (with Installation Date Set to No)
This section describes the steps that you must take in order to audit, check for, and cite out-of-synch conditions among components in the staging libraries and the corresponding baseline libraries of participating packages in a complex or super package. NOTES We assume that the global administrator has set the Process Participating Packages by Installation Date parameter to No. 1 In the PACKAGE ID field of the Audit Change Package panel, type the name (for example, NAVI000005) of a participating package, defined in a complex or super package, that you wish to audit. Verify that the information in the JOB STATEMENT INFORMATION fields are correct, and press ENTER. A message similar to the following appears: WSER010X (JOB03581) submitted CN(INTERNAL) For each participating package in the complex or super package that contains the specified package (for example, NAVI000005), the audit function processes the staging and corresponding baseline libraries excludes the baselined participating packages
User Guide
7-33
7 Auditing Packages
flags out-of-synch conditions updates the audit return code in the package master for that participating packages and the log file for their audit activity 3 At this point, you can retrieve and review your generated audit report for out-ofsynch conditions and return codes. (See Accessing Submitted Audit Reports on page 7-55.)
Auditing Staging and Baseline Libraries of a Group of Participating Packages in the Complex or Super Package (with Installation Date Set to Yes)
This section describes the steps that you must take in order to audit, check for, and cite out-of-synch conditions amongst the components of the participating packages having the same or earlier installation dates as the specified package. NOTES We assume that the global administrator has set the Process Participating Packages by Installation Date parameter to Yes. 1 In the PACKAGE ID field of the Audit Change Package panel, type the name (for example, NAVI000005) of a participating package that you wish to audit. This package is defined in the complex or super package. Verify that the information in the JOB STATEMENT INFORMATION fields are correct, and press ENTER. A message similar to the following appears: Verify that the information in the JOB STATEMENT INFORMATION fields are correct, and press ENTER. A message similar to the following appears: WSER010X (JOB03581) submitted CN(INTERNAL) For each participating package that has the same or an earlier installation date than the specified package (for example, NAVI000005), the audit: processes the staging libraries of all participating packages having same or earlier installation dates as the specified package, and corresponding baseline libraries excludes baselined participating packages flags out-of-synch conditions
7-34
updates the audit return code in the package master for participating packages having same or earlier installation dates as the specified package and the log file for their audit activity 4 At this point, you can retrieve and review your generated audit report for out-ofsynch conditions and return codes. (See Accessing Submitted Audit Reports on page 7-55.)
Example: Auditing All Participating Packages

1998/06/15 1998/07/01 1998/07/15 1998/08/01 1998/09/01 1998/09/15 1998/10/01 2000 5000 2000 2000 4000 5000
NOTES Also, one of the following occurs: The global administrator has set Process Participating Packages by Installation Date parameter to No. You can specify any participating package or, you will specify the participating package with the latest installation date (for example, NAVI000008). All other participating packages will have the same or earlier installation dates and will be included in the auditing process Audit; processes NAVI000003 through NVAI000008 and their staging libraries.
User Guide
7-35
7 Auditing Packages
excludes NAVI000002, a baselined participating package. updates the audit return code in the package master for NAVI000003 through NAVI000008 packages and the log file for their audit activity.
Example: Auditing a Group of Participating Packages (Installation Date Set to Yes)

If you elect to audit a group of the participating packages (for example, in the PACKAGE ID field of the Change Man Audit panel, type NAVI000005) with the global option Process Participating Packages by Installation Date Set to Yes, then audit creates a package group consisting of NAVI000003 to NAVI000005 packages, since their installation dates are equal to or earlier than the installation date of NAVI000005 excludes NAVI000006 through NAVI000008 because their installation dates are later than NAVI000005 excludes NAVI000002, a baselined participating package updates the audit return code in the package master for NAVI000003 through NAVI000005 packages and the log file for their audit activity
AUDIT DIAGNOSTIC TRACING

The audit batch job can produce diagnostic information for debugging. After you report a problem to Change Man Technical Support, Technical Support may request that you submit a trace of the problem, rerun the audit, and send them the diagnostic information. To generate a diagnostic report, you should select the appropriate audit options, type TRACE, FASTRC, or ALLTRC on the command line, press ENTER. If you typed TRACE and pressed ENTER, then the audit job will be submitted.
7-36
Audit Diagnostic Tracing
If you typed FASTRC or ALLTRC and pressed ENTER, you will have to enter up to five trace control cards that will be provided by Technical Support. The Build Audit Trace Control Cards panel (CMNADTRC) appears.
CMNADTRC --------------- BUILD AUDIT TRACE CONTROL CARDS ---------------------COMMAND ===> This panel is used to enter control cards that are input to the Audit Trace Facility. Tracing should only be activated if a problem has been encountered as tacing wil impact audit performance. * SAMPLE TRACE CONTROL CARD INPUT * * * * TRACE PGM,NAME=(CMNAD112) * * TRACE SUB,NAME=(CMNAD100,CMNAD11*) * * TRACE TRP,NAME=(CMNAD143) *
CONTROL CONTROL CONTROL CONTROL CONTROL
CARD1 CARD2 CARD3 CARD4 CARD5
===> ===> ===> ===> ===>
The Audit trace control cards contain: the keyword, TRACE, that activates the audit trace facility the object of tracing a program (PGM), subroutine (SUB), or critical section (TRP) the scope of tracing one or more programs (subroutines, critical sections) entered with parentheses after the NAME keyword
NOTES Wildcard filers like * and? can be used to specify name patterns for the traced programs. Technical Support will provide the exact content of each trace control card. The diagnostic information is added to the TRCPRINT data set in the first job step. After the audit completes, send this data set to Technical Support. If the audit job abends, abend diagnostic information is written to the same TRCPRINT data set that should be sent to Technical Support for investigation.
User Guide
7-37
7 Auditing Packages
THE AUDIT REPORT

The audit report that you generate depends on the parameters and options that you select on the Audit Change Man panel (See Accessing Submitted Audit Reports on page 7-55). For each library type, the audit report provides information about each component in the baseline and staging libraries, their corresponding ISPF statistics, and out-ofsynch conditions. According to your selected parameters and options, your audit report may contain one or all of the following reports (section) each beginning with a report header: Staged component by library type (editable components and load module) Source-to-copy relationship (copybooks members within source code) Load-to-load relationship (statically link-edited called subroutines within composite load modules) Component history
Also, the audit report ends with the following summary reports: Legend and Summary of flagged out-of-synch conditions Recommendation Summary
REPORT HEADER
Each report (section), with the exception of the summary sections, contains a header that provides the version of Change Man at your site. Also, the report contains the generated date and time, the package level, the package ID, the installation date of the package, status of the package, department number of the requested package, and component analysis type or report type. For example, the following illustration is a sample of a report header of a staged components by library type report of a simple package (NAVI000011).
(5.1 - 1999/273 ) Audit TUESDAY NOVEMBER 30, 1999 (1999/334) 17:27:19 Page 1 ************************************************************************************************ *Simple Change Package ===> NAVI000011 Created 1999/11/29 at 10:02:13 by WSER83 * *Package Installation Date ===> 1999/01/ 01 Package Status: DEV Dept No.: 00 * *Component Analysis Type ===> Description of member from directory entry in library - (CPY) * ****************************************************************************************************************************** Change Man
7-38
Report Body
REPORT BODY
The body of the report displays a section for each component library type associated with the package. The components appear with its ISPF statistics in the baseline (on the left side of the body), and the staging libraries for checkup and comparison appear on the right side.
Section 1. Staged Components by Library Type

According to the library type, editable component or load module (load or like-load), the format of the report differs. For example, the following illustration is a Stage Components by Library Type report for editable components (source code, copybooks, or JCL) report..
(5.1 - 1998/273 ) Audit MONDAY NOVEMBER 16, 1998 (1998/320) 17:27:19 Page 1 ************************************************************************************************ *Participating Package ===> NAVI000011 Created 1998/11/05 at 10:02:13 by WSER83 * *Package Installation Date ===> 1999/01/ 01 Package Status: DEV Dept No.: 00 * *Component Analysis Type ===> Description of member from directory entry in library - (CPY) * ************************************************************************************************************************************ *--------------------- B a s e l i n e ---------------------* *---------------------- S t a g i n g ----------------------* ************************************************************* ************************************************************* Name VV.MM Created Changed Size Init Tso-id Name VV.MM Package Changed Size Dept Tso-id ________ _____ __________ ________________ ____ ____ ________ ________ _____ __________ ________________ ____ ____ ________ CMN#PXPL 01.00 1996/10/24 1998/08/19 18:37 0211 0190 C41720 CMN#PXPL 02.01 C417000030 1998/11/08 15:15 0221 00 WSER46 CMN@CCOP 01.00 1996/10/24 1998/07/17 14:34 0359 0306 C41715 CMN@CCOP 02.01 C417000030 1998/11/06 13:33 0455 00 WSER03 CMN@DINF 01.00 1996/10/24 1998/07/17 15:37 0307 0304 C41715 CMN@DINF 02.01 C417000030 1998/11/06 13:39 0337 00 WSER03 CMN@PALU 01.00 1998/06/22 1998/07/21 12:41 0355 0350 C41715 CMN@PALU 02.01 C417000030 1998/11/06 18:12 0359 00 WSER124 CMN@PGDC 01.00 1996/10/24 1998/07/17 15:40 0181 0173 C41715 CMN@PGDC 02.01 C417000030 1998/11/13 16:44 0185 00 WSER03 CMNBLAY5 01.00 1996/01/26 1998/10/27 15:07 0167 9440 C41725 CMNBLAY5 02.02 C417000030 1998/11/11 16:16 0177 00 WSER42 CMNBTSRT 01.00 1996/01/26 1996/10/28 14:42 0064 0064 C41601 CMNBTSRT 02.01 C417000030 1998/11/11 13:52 0064 00 WSER124 CMNRLPCA 01.00 1996/05/01 1998/10/30 13:24 3637 1315 C41725 SYNCH10! CMNRLPCA 02.01 C417000030 1998/11/06 13:40 3641 00 WSER03 CMNRVARC 01.00 1998/07/17 1998/11/02 13:00 0330 0327 C41725 CMNRVARC 02.01 C417000030 1998/11/08 15:17 0337 00 WSER46 Change Man
NOTES Out-of-synch conditions appears between the baseline and staging areas. Also, the following illustration contains information for load modules (LOD and likeLOD library types).
(5.1 - 1998/273) Audit MONDAY NOVEMBER 16, 1998 (1998/320) 17:27:19 Page 7 ************************************************************************************************ *Participating Package ===> C417000030 Created 1998/11/05 at 10:02:13 by WSER73 * *Package Installation Date ===> 1999/01/ 01 Package Status: DEV Dept No.: 00 * *Component Analysis Type ===> Description of member from directory entry in library - (LOD) * ************************************************************************************************************************************ *-------------------- B a s e l i n e --------------------* *----------------------- S t a g i n g -----------------------* *********************************************************** *************************************************************** Name Size Linkdate Alias-of AC Attr Setssi Name Package Dept Size Linkdate Alias-of Setssi ________ ________ __________ ________ __ ____ ________ ________ __________ ____ ________ __________ ________ ________ CMNADMSO 0000E838 1998/11/05 00 C2E2 4911F138 CMNADMSO C417000030 00 0000E848 1998/11/13 491C2B27 CMNAPPRV 000058B0 1998/10/16 00 C2E2 48F72257 CMNAPPRV C417000030 00 000058B0 1998/11/13 491C4F88 CMNAPS20 0000AAC8 1998/10/28 00 C2E2 49071C67 CMNAPS20 C417000030 00 0000AB10 1998/11/10 491806C7 CMNAUD20 0000BC40 1998/10/29 00 C2E2 49083C77 CMNAUD20 C417000030 00 0000BC40 1998/11/10 49187D39 CMNBATCH 0000E1B0 1998/10/27 00 C2E2 4905D959 CMNBATCH C417000030 00 0000E1C0 1998/11/11 4919B2A6 CMNBAT10 00009CA0 1998/09/17 00 C2E2 48D0CC9F CMNBAT10 C417000030 00 00009C28 1998/11/11 49198E58 CMNBAT40 000012F8 1998/09/17 00 C2E2 48D0CE21 CMNBAT40 C417000030 00 00001308 1998/11/11 4919C0E9 CMNBRWLG 00002DE8 1998/10/26 00 C2E2 49047ED3 CMNBRWLG C417000030 00 00002DE8 1998/11/12 491AAD46 Change Man
User Guide
7-39
7 Auditing Packages
The following table describes the fields of the Staged Components by Library Type section of the audit report. Column Name
Name VV.MM
Description
The name of the component. The version and modification number for the component following the IBM standards (mm starts at 01, increments to 99; vv starts at 01, increments to 99, and recycles to 01). The first time the component is processed by Change Man the vv.mm is 01.01. Each successive stage request (within the same change package) increments the mm portion (for example, 01.02, 01.03). The next package using the component causes the vv portion to be incremented (02.01). If an existing library is added to Change Man the vv.mm is not reset.
Created
The date (yyyy/mm/dd) that the component was first included in the Change Man system. The date (yyyy/mm/dd) of the most recent change to the component residing in current production (on the staging side of the report this would be the most recent staged date). The number of lines of text data. The size of the component when first created (version 01.01). The TSO identification of the person responsible for this component's version and modification (vv.mm). Note: For CA-PANVALET library components, this field displays the USER and LANG TYPE because CA-PANVALET does not have a true directory for CMNIFACE to read for the TSO-ID.
Changed
Size Init Tso-id
Package
The name of the participating package where the component resides. The department number field, which is filled in when a new package is created from the Package Create panel. For a load module, this is the link-edit date of the component in the baseline and staging libraries. For a load module, this field indicates that the module is an alias of a specific module. For a load module, the authorization code (usually 00).
Dept
Linkdate
Alias-of
AC
7-40
Report Body
Column Name
Attr Setssi
Description
For a load module, this field displays the attributes. For a load module, a timestamp set by Change Man or extracted from a vendor module.
Section 2. Component History Area

The Component History section provides historical information about the components of the library type. This section has two formats: Source and like-SRC components.
The following figure is an illustration of the Component History section for source components.
Change Man (5.1 - 1998/273) Audit MONDAY NOVEMBER 16, 1998 (1998/320) 17:27:19 ************************************************************************************** *Participating Package ===> C417000030 Created 1998/11/05 at 10:02:13 by WSER73 * *Package Installation Date ===> 1999/01/ 01 Package Status: DEV Dept No.: 00 * *Component Analysis Type ===> History of changes for audited components * **************************************************************************************** *---------------------- C o m p o n e n t H i s t o r y - SRC ----------------------* **************************************************************************************** Name VV.MM Procedure Changed Size Tso-id Package Status Setssi ________ _____ _________ ________________ ____ ________ __________ ______ ________ CMNADMSO 02.12 CMNASM 1996/03/07 16:30 5585 WSER15 C415000004 BAS 440F0658 CMNADMSO 02.03 CMNASM 1996/05/16 19:03 5587 WSER20 C415000005 BAS 446B7355 CMNADMSO 03.08 CMNASM 1996/06/13 11:54 5590 WSER15 C415000007 BAS 448FF8AC CMNADMSO 04.03 CMNASM 1996/08/26 18:42 5597 WSER42 C415000008 BAS 44F1E757 CMNADMSO 02.19 CMNASM 1996/10/30 10:49 0402 WSER03 C416000001 BAS 454729AC CMNADMSO 02.03 CMNASM 1996/11/25 12:01 0405 WSER42 C416000002 BAS 456981FF CMNADMSO 02.04 CMNASM 1996/12/09 14:53 5106 WSER42 C416000003 BAS 457C1F56 CMNADMSO 02.03 CMNHASM 1997/06/09 17:25 5600 WSER33 C415000030 BAS 466C33BD CMNADMSO 02.01 CMNASM 1997/04/23 19:25 5112 WSER117 C416000004 BAS 462E597D CMNADMSO 02.02 CMNHASM 1997/10/06 10:19 5114 WSER52 C416000010 BAS 4708B24F CMNADMSO 02.01 CMNHASM 1997/05/22 19:22 5111 WSER117 C416000005 BAS 46549445 CMNADMSO 02.02 CMNHASM 1998/02/11 17:16 5114 WSER42 C416000030 BAS 47B1D430 CMNADMSO 01.00 *RECOMP* 1998/05/28 12:02 0000 WSER124 C417000010 BAS 483D1F8D CMNADMSO 01.00 CMNASM 1998/08/12 06:51 0000 WSER73 C417000015 BAS 48A071ED CMNADMSO 01.00 1998/09/17 09:01 0000 WSER74 C417000020 BAS 48D0C651
Non-source components.
The following illustration is a sample of the Component History report for non-source components.
Change Man (5.1 - 1998/273) Audit MONDAY NOVEMBER 16, 1998 (1998/320) 17:27:19 ************************************************************************************** *Participating Package ===> NAVI000013 Created 1998/11/05 at 10:02:13 by WSER83 * *Package Installation Date ===> 1999/01/ 01 Package Status: DEV Dept No.: 00 * *Component Analysis Type ===> History of changes for audited components * ************************************************************************************** *------------------ C o m p o n e n t H i s t o r y - CPY -----------------* ******************************************************************************* Name VV.MM Changed Size Tso-id Package Status ________ _____ ________________ ____ ________ __________ ______ CMN#PXPL 01.11 1996/10/28 14:23 0190 WSER03 C416000001 BAS CMN#PXPL 02.03 1997/04/03 09:51 0199 WSER52 C416000003 BAS CMN#PXPL 02.02 1998/07/09 11:40 0208 WSER117 C416000041 BAS CMN#PXPL 02.03 1998/08/13 10:18 0209 WSER03 C417000015 BAS CMN#PXPL 02.03 1998/08/19 18:37 0211 WSER03 C417000020 BAS CMN#PXPL 02.01 1998/11/07 14:06 0218 WSER46 C416000055 DEV CMN#PXPL 02.01 1998/11/08 15:15 0221 WSER46 C417000030 DEV
User Guide
7-41
7 Auditing Packages
The following table describes the fields of the Component History area of an Audit Report. Column Name
Name vv.mm
Description
The name of the component. The version and modification number for the component following the IBM standards (mm starts at 01, increments to 99; vv starts at 01, increments to 99, and recycles to 01). The first time the component is processed by Change Man the vv.mm is 01.01. Each successive stage request (within the same change package) increments the mm portion (for example, 01.02, 01.03). The next package using the component causes the vv portion to be incremented (02.01). If an existing library is added to Change Man the vv.mm is not reset.
Procedure
For a source component, this field describes the procedure used to stage (compile and link-edit) the component. The date in yyyy/mm/dd format of the most recent change to the component residing in current production (on the staging side of the report this would be the most recent staged date). The number of lines of text data. The TSO identification of the person responsible for this component's version and modification (vv.mm). Note For CA-PANVALET library components, this field displays the USER and LANG TYPE because CAPANVALET does not have a true directory for CMNIFACE to read for the TSO-ID.
Changed
Size Tso-id
Package
The name of the participating package where the component resides. The status of the component. For a source component, a timestamp set by Change Man for the corresponding load module created through staging the source code.
Status Setssi
7-42
Report Body
Section 3. Source to Copy Relationships Report

The Source to Copy Relationships report lists the copybooks called in source components. Also, the report provides baseline information (on the left side) and staging information (on the right side) about them. The source component name and flagged out-of-sync conditions appear in the middle of the report. All source components in the audited package and baseline source components that call the changed copybooks appear on the report. If there is no baseline information for a component, then it is a new. If there is no staging information for a component, then it is not staged and resides in the baseline library. The following illustration is a sample of the Source-to-Copy Relationships section of the audit report:
****************************(Dept No. Package Processing)***************************** *Participating Package ===> C510000002 Created 1999/08/30 at 13:38:25 by WSER03 * *Package Installation Date ===> 2000/03/ 08 Package Status: FRZ Dept No.: 00 * *Component Analysis Type ===> Copybook (CPY) members within source (SRC) code * ************************************************************************************************************************************ *--------------------- B a s e l i n e ---------------------* *---------------------- S t a g i n g ----------------------* ************************************************************* ************************************************************* Copybook Source Copybook Name VV.MM Created Changed Size Init Tso-id Name Name VV.MM Package Changed Size Dept Tso-id ________ _____ __________ ________________ ____ ____ ________ ________ ________ _____ __________ ________________ ____ ____ ________ CMN$ AAPR 01.06 C510000002 1999/10/01 18:31 0935 00 WSER03 CMN$GLBL 01.00 1996/01/26 1996/10/28 14:35 0008 0008 C41601 CMN$SETC 01.00 1996/01/26 1998/05/27 17:41 0014 0013 C41710 CMN$SETC 01.03 C510000002 1999/09/23 15:37 0014 00 WSER03 CMNFDTDS 01.01 C510000002 1999/09/23 15:37 0025 00 WSER03 CMNPATCH 01.00 1996/01/26 1996/10/28 16:26 0019 0019 C41601 CMNPMAST 01.00 1996/01/26 1998/09/16 10:14 1708 1322 C41720 SYNCH15! CMNPMAST 02.03 C510000002 1999/10/08 19:31 1724 00 WSER03 CMNSETUP 01.00 1996/01/26 1997/09/12 16:11 0028 0026 C41610 CMNSETUP 02.01 C510000002 1999/09/23 15:37 0027 00 WSER03 CMNVACAD 01.01 C510000002 1999/09/23 15:37 0039 00 WSER03
CMNPMAST was modified on 1999/10/08. When it is compared to CMN$AAPR, a source component, modified on 1999/10/01, audit signals out a out-of-sync condition (SYNCH15!) flags CMNPMAST. The source component needs to be re-staged to get the latest changes to the called copybook. Column Name
Copybook Name VV.MM
Description
The name of the staged or baseline copybook. The version and modification number for the component following the IBM standards (mm starts at 01, increments to 99; vv starts at 01, increments to 99, and recycles to 01). The first time the component is processed by Change Man the vv.mm is 01.01. Each successive stage request (within the same change package) increments the mm portion (for example, 01.02, 01.03). The next package using the component causes the vv portion to be incremented (02.01). If an existing library is added to Change Man the vv.mm is not reset.
Created
The date (yyyy/mm/dd) when the component was created under Change Man. The date and time when the component in the baseline and staging libraries was last modified.
Changed
User Guide
7-43
7 Auditing Packages
Column Name
Size Init Tso-Id
Description
The number of lines of text data. The size of the component when first created (version 01.01). The TSO identification of the person responsible for this component's version and modification (vv.mm). Note For CA-PANVALET library components, this field displays the USER and LANG TYPE because CAPANVALET does not have a true directory for CMNIFACE to read for the TSO-ID.
Source Name Package
The name of the staged or baseline source component. The name of the participating package where the component resides. The date and time when the component in the baseline and staging libraries was last modified. The number of lines of text data. The department number field, which is filled in when a new package is created from the Package Create panel. The TSO identification of the person responsible for this component's version and modification (vv.mm). Note For CA-PANVALET library components, this field displays the USER and LANG TYPE because CAPANVALET does not have a true directory for CMNIFACE to read for the TSO-ID.
Changed
Size Dept
Tso-Id
Section 4. Load-to-Load Relationships Report

The Load-to-Load Relationships report contains the load modules called in composite load modules. Also, it provides baseline information (on the left side) and staging information (on the right side). The calling composite load module name and flagged out-of-synch conditions for the called load modules appear in the middle of the report. This report contains all composite load modules staged in the audited package and those baseline load modules that call load modules changed in the audited package. If there is no baseline information for a load module, then it is a new. If there is no staging information for a load module, then it is not staged and resides in the baseline library.
7-44
Report Body
A sample of the Load/Load Relationships report follows:

Change Man (5.1- 1998/273) Audit SUNAY OCTOBER 10, (1999/283) 17:27:19 Page 102 ************************************************************************************** *Participating Package ===> C510000000 Created 1999/08/05 at 10:02:13 by WSER73 * *Package Installation Date ===> 2000/03/ 008 Package Status: DEV Dept No.: 00 * *Component Analysis Type D===> Statically Link-Edited Called Subroutine (LOD) * ****************************************************************************************************** *--------- B a s e l i n e ---------* *------------------ S t a g i n g ------------------* ************************************* ***************************************************** Called Module Calling Called Module Module Size Linkdate Setssi Module Module Package Dept Size Linkdate Setssi ________ ________ __________ ________ ________ ________ __________ ____ ________ __________ ________ CMNFIXMN C510000000 00 00003E60 1999/10/05 4ACA0254 CMNBIDRB C510000000 00 000008F0 1999/09/13 4ABA7690 CMNCCASM C510000000 00 000006E8 1999/11/13 4ABA8B63 0000E838 1998/11/05 4911F138 CMNOFM CMNCCASM 00000E40 1998/11/06 4911F14F SYNCH8! CMNZDRV 000060DO 1998/11/06 48EC8C1D SYNCH8!
CMNCCASM C510000000 00 CMNZDRV C510000000 00
0000E848 1999/11/13 491C2B27 0000E848 1999/11/13 4ABA9588
The most recent link-edit date for the staged load modules is 1999/11/13. CMNOFM was modified on 1998/11/05. When it is compared to the staged load module, audit flags a out-of-sync condition (SYNCH8!). The CMNOFM module in the baseline library needs to be re-linked to obtain the latest changes to the called load modules in the staging library. The following table describes this section of the report. Column Name
Called Module Module Size
Description
The name of the staged or baseline load module The size (bytes) of the module represented as a hexadecimal value. The link-edit date of the load module in the baseline libraries. A timestamp set by Change Man or extracted from a vendor module. The name of the staged or baseline composite load module. The name of the participating package where the component resides. The department number field, which is filled in when a new package is created from the Package Create panel. The size (bytes) of the module represented as a hexadecimal value. The link-edit date of the load module in the staging libraries. A timestamp set by Change Man.
Linkdate Setssi
Calling Module Package
Dept
Module Size
Linkdate Setssi
User Guide
7-45
7 Auditing Packages
Section 5. Legend and Summary

The Legend and Summary portion of the Audit Report provides the following information: The level of the audit return code The highest encountered return code The number of encountered out-of-synch messages for each out-of-synch conditions A message indicating whether the change package passed or failed its audit
The following illustration is an example of the Legend and Summary section of the Audit Report.
Change Man (5.1 - 1998/273) Audit MONDAY NOVEMBER 16, 1998 (1998/320) 17:27:19 Page Legend and Summary Report The local level of audit chosen at this point ; 0 0 - Audit is recommended but entirely optional Out-of-synch messages (hint - search for "!" marks) DUPLIC! (Staging duplicates baseline) ===> 0 SYNCH0! (Unknown to Change Man) ===> 46 SYNCH1! (ISPF statistics not available) ===> 0 SYNCH2! (Compile/designated proc differ) ===> 0 SYNCH3! ( Unparsable load module) ===> 0 SYNCH4! (CPY problem in staging) ===> 0 SYNCH5! (CPY high-date problem in baseline)===> 111 SYNCH6! (Activity file not checked out) ===> 0 SYNCH7! (Called subroutine in staging) ===> 0 SYNCH8! (Called subroutine in baseline) ===> 0 SYNCH9! (Source and load discrepancy) ===> 0 SYNCH10! (Version regression problem) ===> 3 SYNCH11! (Component hash discrepancy) ===> 0 SYNCH12! (Orphan module in staging) ===> 0 SYNCH13! (Baseline/staging discrepancy) ===> 0 SYNCH14! (Components not in active status) ===> 0 SYNCH15! (Source to relationship problem) ===> 0 SYNCH16! (CPY low-date problem in baseline)===> 0 SYNCH17! (CPY deleted problem in staging) ===> 0 SYNCH18! (LOD deleted problem in staging) ===> 0 Highest return code encountered ===> 12 CMN2666I - PARTICIPATING PACKAGE C417000030 FAILED THE AUDIT WITH A RETURN CODE OF 12.
Section 6. Recommendation Summary Report

The Recommendation Summary Report section of the audit report provides recommendations for resolving out-of-synch conditions detected in the audit package.
7-46
Out-of-synch Conditions
For example, the following illustration of the Recommendation Summary section shows that the audit discovered SYNCH0, SYNCH5, and SYNCH10 as the out-ofsynch conditions.
Listed below are some solutions to resolving out of synch situations that can be flagged within this audit report. SYNCH0! (Unknown to Change Man) Cycle component through Change Man. Check if component resides in another participating package excluded from audit due to install date. SYNCH5! (CPY high-date problem in baseline) Recompile source component from baseline to include copylibs residing in the staging libraries. SYNCH10! (Version regression problem) Copy staging member to development library. Checkout member again from the baseline library. Resolve version regression. Stage member. CMN7540I - End of job; RC = 12
Audit success or failure shows in the 'Audit Pass' line on the last page of the audit report. Generally, If the package does not pass the audit, you cannot be freeze it for promotion or installation. For the package to pass the audit, the audit return code should correspond to the audit level set by your application administrator (See Audit Level on page 7-3). There may be some unknown components to Change Man components. Some components might lack ISPF statistics or be unparsable load modules for which not all the audit checks can be done.
OUT-OF-SYNCH CONDITIONS
Audit detects and reports out-of-synch conditions between the components of an audit package, baseline components, and other components that are called in the primary package components. Each out-of-synch condition sets an appropriate return code based on its impact on the integrity of the audited change package.
User Guide
7-47
7 Auditing Packages
Return Codes
Return Code
0
Description
No out-of-synch conditions were found in your package. No user action is required. Some out-of-synch conditions were found, but the conditions are very minor and are usually informational. Typically, no user action is required. Some out-of-synch conditions were found, and the conditions must be reviewed and possibly corrected. These out-of-synch conditions are SYNCH5, SYNCH8, and SYNCH16. User action is required prior to freezing the package.
12
Some out-of-synch conditions were found, and the conditions must be reviewed and corrected. All out-of-synch conditions are affected, except SYNCH0, SYNCH5, SYNCH8, and SYNCH16. User action is required prior to freezing the package
This section describes the out-of-synch condition messages you can receive during your audit and gives the corresponding return code for each message.
DUPLIC! (Staging duplicates baseline)

Components that, after a line by line compare, show no difference between staging and baseline libraries cause this condition. At baseline ripple, this causes older versions of that component to drop off prematurely. Return Code
4
Resolution
Delete the duplicate component from the change package or change the contents of the staged component.
!COPY! (Embedded copybooks)

Shows that there is a copy within a copy (an embedded copylink). This is an informational code indicating that a relationship exists.
Return Code
0
Resolution
No action required.
SYNCH0! (Component unknown to Change Man)
7-48
If Change Man has no record of this component in the package master, and the component is calling another module and one (or more) of the following situations exist, then SYNCH0! results: The component does not exist in the baseline library The source-to-copy or load-to-load relationship does not exist in the Impact Analysis table The relationship is found but the called or calling component does not exist in the baseline library Return Code
0
Resolution
Ignore if the component resides in another participating package excluded from this audit due to installation date. If the component exists in the baseline library, run the Conversion Assistance to select new relationships.
SYSCH1! (ISPF statistics not available)

A component has no ISPF statistics. Therefore, some audit checks cannot be performed for this component. Return Code
0
Resolution
Create or reset the ISPF statistics for the component.
SYNCH2! (Compile/designated procedure differ)

Source or like-source components in which the final compile was done without using the designated compile procedure (including designated compile options, link options, or user options)
Return Code
12
Resolution
Recompile the component using the designated procedure. Alternatively, set the Auto-Resolve option to YES and re-submit the audit.
SYNCH3! (Unparsable load module)
User Guide
7-49
7 Auditing Packages
A load component whose IDRDATA records cannot be parsed and interpreted correctly. Therefore, some audit checks cannot be performed for the component.
Return Code
0
Resolution
Check the load module, it might be corrupted. Also, stage, relink, or recompile the corresponding source component.
SYNCH4! (CPY problem in staging)

A copybook has been staged after the staging of the source component that calls the copybook. Therefore, the source has been compiled with a previous version of the copybook. An updated staged copybook may be nested in another copybook called in the source copybook.
Return Code
12
Resolution
Stage the source component to include the update copybook staging libraries. Alternatively, set the Auto-Resolve option to YES and resubmit the audit.
SYNCH5! (CPY high date problem in baseline)

When a copybook is staged, source components that are not staged and called the copybook receive outof-synch condition because they are compiled with a previous versions of the copybook. An updated staged copybook may be nested in another copybook called in the baseline source component.
Return Code
8
Resolution
Recompile the source component from the baseline to include copybooks residing in the staging libraries. Alternatively, set the AutoResolve option to YES and re-submit the audit.
SYNCH6! (Activity file not checked out)

The component activity file (CAF) of a component has not been checked out, while the component has been staged.
Return Code
12
Resolution
Check out and stage the associated activity file for the component.
SYNCH7! (Called subroutine in staging)
7-50
After staging the composite load module that calls a specific load module, you have staged that load module. Therefore, an out-of-synch condition is present because a previous version of the called module is link-edited to the calling module.
Return Code
12
Resolution
Relink the calling load module to include the called load module in the staging libraries. Alternatively, set the Auto-Resolve option to YES and re-submit the audit.
SYNCH8! (Called subroutine in baseline)

When you stage a load module, all composite load modules that are not staged and called the staged load module become out-of-synch because a previous version of the subroutine is link-edited with these load modules. An updated staged subroutine may be link-edited in another load module called by the baseline composite load module. Return Code
8
Resolution
Relink the calling load module from baseline to include the called load module in the staging libraries. Alternatively, set the Auto-Resolve option to YES and re-submit the audit.
SYNCH9! (Source and load discrepancy)

A source component and a corresponding load module in the staging libraries do not match. For example, when the load module is link-edited into the staging library, outside of Change Man, it replaces the load module from the staging of the source component and creates a source and load module discrepancy. Return Code
12
Resolution
Stage the source component to create a new load module. Alternatively, set the Auto-Resolve option to YES and re-submit the audit.
SYNCH10! (Version regression problem)

You have checked out a component to more than one change package. At the time of the audit of the other packages, one of the packages has been installed. Therefore, current changes to the component are invalid, because the changes were made to the previous baseline and not to the newly baseline version.
User Guide
7-51
7 Auditing Packages
In order to avoid version regression due to concurrent development, you must merge changes in the new baseline version with the changes in the staged component. Return Code
12
Resolution
Copy the staged component to a development library. Check out component from baseline in order to obtain the latest version. Apply your changes to the latest version and stage the component. Note: You can use the Change Man option, Merge and Reconcile to merge the changes.
SYNCH11! (Component hash discrepancy)

A components was staged, then edited or replaced in the staging library outside of Change Man. Return Code
12
Resolution
Stage the component again.
SYNCH12! (Orphan module in staging)

Outside of Change Man, a component is copied into the staging library. Although the component is in the baseline library and its relationships are recorded in the Impact Analysis table, it is not treated as a component in the staging library. Also, when staging a source component, the compile job abends and no load module is staged. Therefore, the source component is an orphan module. Return Code
12
Resolution
Delete the component from the staging library.
SYNCH13! (Baseline/staging discrepancy)

Based on the ISPF statistics of the baseline and staging libraries, an editable staged component has an earlier last modified date than its corresponding baseline component. Therefore, the staged component is out-of-synch with the baseline library.
7-52
For load modules, the SETSSI of the staged and baseline components are compared and if the staged SETSSI is less than the baseline SETSSI, then the load module is flagged. Return Code
12
Resolution
Check out the most current component from the baseline, apply changes, and stage the component. If a load module in the staging library has been created by recompiling a source component from the baseline, recompile the source component from the baseline again to obtain the most current version.
SYNCH14! (Component not in active status)

A component in the package is not in active status. Return Code
12
Resolution
In order to activate the component, re-stage it.
SYNCH15! (Source to copy relationship problem)

After a source component, which calls the contents of a copybook, was staged, the content of the copybook was changed. These conditions resulted in a out-of-synch condition for the source component with the called copybook. Possible scenarios for this condition follow: The copybook might have been included from the baseline, staging, or promotion libraries based on the SYSLIB search for the source component compile job. The contents of the called copybook (found in either staging, promotion or baseline library) has changed since the Source module was compiled. A new version of the copybook has been added to the SYSLIB search order for that source component.
The Staging LCT member has a more current activation date than the corresponding source member. Return Code
12
Resolution
Re-stage the source component in order to obtain the current COPY or LCT relationship. Alternatively, set the Auto-Resolve option to YES and re-submit the audit.
SYNCH16! (CPY low-date problem in baseline)
User Guide
7-53
7 Auditing Packages
The last modified date of a source component in baseline is after the last recompile date or after a called copybook was last modified in staging library. A copybook was changed in a package, which does not contain the source component that calls it. The source component has been baselined in another package after the copybook has been changed. Therefore, the source-to-copybook relationship will be out-of-synch. Return Code
8
Resolution
Recompile the source component from baseline to include the copybooks residing in the staging libraries. Alternatively, set the AutoResolve option to YES and re-submit the audit.
SYNCH17! (Copybook deleted problem in staging)

A new unknown to Change Man copybook is staged into a package, and a source component that calls the unknown is also staged in the same package or a participating package. When the copybook is deleted, changes are not made to the source component in order to remove any reference to the copybook. A baselined copybook is changed and staged, then deleted from the package but the source that calls it is not re-staged or recompiled. Return Code
12
Resolution
Stage the missing called copybook and re-stage the source component. If the copybook is no longer needed, remove any reference to it from the source component, and re-stage the source component.
If the copybook is no longer needed, and the source was recompiled from baseline, and at least one other copybook has to be included from any staging libraries, recompile the source from baseline to include the baseline version of the deleted copybook. If the copybook is no longer needed, and the source was recompiled from baseline, and there are no other copybooks to be included from any staging libraries, and there are no compile or link-edit attributes changes, delete the recompile source from the package.
SYNCH18! (Load deleted problem in staging)
7-54
Accessing Submitted Audit Reports
A new unknown to Change Man load module is staged into a package, and a composite load module that calls it is also staged in the same package or a participating package. When the load module is deleted, changes are not made to the source and link-edit control cards for the composite load module in order to remove any reference to the load module. Return Code
12
Resolution
Stage the missing called load module in the composite load module, and relink the composite load module. If the called load module is no longer needed, remove any reference from the link-edit control cards, and the source and re-stage the composite load module.
ACCESSING SUBMITTED AUDIT REPORTS

In order to view your submitted audit report, you access your sites output utility. For example, a site might use the Spool Display and Search Facility (SDSF) as its output utility.
HQX1900-----------------COMMAND INPUT ===> LOG DA I O H ST PR INIT MAS LINE NODE SO Display Display Display Display Display Display Display Display Display Display Display Display SDSF PRIMARY OPTION MENU -------------------------SCROLL ===> CSR
the system log active users in the sysplex jobs in the JES2 input queue jobs in the JES2 output queue jobs in the JES2 held output queue status of jobs in the JES2 queues JES2 printers on this system JES2 initiators on this system JES2 members in the MAS JES2 lines on this system JES2 nodes on this system JES2 spool offload for this system
Licensed Materials - Property of IBM 5647-A01 (C) Copyright IBM Corp. 1981, 1997. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
To view your audit report, select the function that allows you to display the batch job that you submitted with your TSO ID as the job name.
User Guide
7-55
7 Auditing Packages
AUDIT AUTO-RESOLVE
When you submit an audit job with the Auto-Resolve option turned on, Audit will generate and submit recompile and relink jobs that will resolve the following out-ofsync conditions: SYNCH2! (Compile/designated Proc differ) SYNCH4! (CPY problem in staging) SYNCH5! (CPY problem in baseline) SYNCH7! (Called subroutine in staging) SYNCH8! (Called subroutine in baseline) SYNCH9! (Source and load discrepancy) SYNCH15! (Source to relationship problem) SYNCH16! (CPY low-date problem in baseline)
After the recompiled and relinked jobs have completed, you can run another audit job to check that all flagged out-of-sync conditions of the type listed above have been in fact resolved. The auto-resolve jobs are submitted in order to allow you to have the recompile and relink jobs of subroutines executed ahead of the jobs for the components calling them. If you single-thread the auto-resolve jobs, one run of Audit will resolve all out-of-sync conditions. Audit submits the auto-resolve jobs based on the library type of the source and load components following the order by which those library type are defined in an application. The application administrator can check and change this order from the Library Types panel selected from the Application Administration Options panel. If you define a source and load library types for subroutines before those of the composite components that call them, the recompile and relink jobs for the subroutines will be submitted ahead of those for the calling modules. Moreover, all recompile jobs will be submitted ahead of the relink jobs.
7-56
Resolution Actions
RESOLUTION ACTIONS
The actions that you can take to resolve out-of-sync conditions are listed in the Outof-sync Conditions table. Also, the last of the audit reports, the Recommendation Summary Report, contains suggestions for resolving those out-of-sync conditions that have been detected and flagged in the current run of Audit.
Resolving same-named members in multiple (PDS) libraries.

When you have a situation that involves same-named members in different libraries, special action may be required. In Assist initialization CMN builds a same-named copybook table from all copylibs in the application. This file is the key to solving the same-named members problem and it contains an entry for every copybook name that exists in more than one physical library in the application. Then when CMN processes a library and finds a copybook, CMN first checks this table. If it is NOT a same-named component CMN knows it is only in one library. So CMN will search all copylibs for this copied member to determine the BUN. If it is a same-named issue, CMN must first go after the history for the source member to locate the last package that member was in. Then CMN will read in the ISIC record, extract the APPL/LIBTYPE for the copy component, and translate that into a BUN number. If the ISIC record does not exist, (either it never existed of has been archived) CMN will issue a query for copies in the source component. If CMN knew the BUN the last time we ran Assist, we extract this information and propagate the BUN number forward. If the BUN number is blank in the query, CMN issues a message saying we cannot determine the BUN for same-named copybook. To solve this you need to open a package and issue a recompile from baseline for every component associated with this message. That will create an ISIC for each component. Then you can re-run Assist and the problem will go away. SERENA specifically did not require that you baseline the entire package, as we wanted to make this issue easy to solve, and auditors might have a problem with baselining the entire package.
User Guide
7-57
7 Auditing Packages
ABOUT CHANGE MAN ASSIST

Change Man Assist processes staging libraries and produces the Impact Analysis file. With Change Man 5.1 it works with Services. Services are implemented as Servers for various Change Man features. The ability to use services allows Change Man Assist to take advantage of multi-tasking and multi-programming for performance improvements.
NEW FEATURES AND CAPABILITIES WITH CHANGE MAN ASSIST

Change Man Conversion Assistance is redesigned and new functionality is added. One noticeable effect of this work is faster throughput for baseline library processing. Another noticeable effect is the larger memory required when taking advantage of this new functionality.
Incremental (partial) Processing Assist

This feature supports updates to the relationships between components. Incremental means that only changed components are processed. A non-incremental (or full) processing updates the entire package without regard to changes since the last full update. Incremental processing determines what libraries have changed since the last Assist and processes only the changes. Incremental processing is usually much faster than full processing.
How Incremental Processing works

A new record was added to the Impact Analysis Flat File. It contains a Date/Time stamp indicating, for each application, when that application was last processed by Assist. Having the date/time of the last Assist for an application eliminates parsing members that have not changed since the last time Assist was run. If this is an Incremental Assist, and the member has not changed since the last time the member was parsed, a Query for the relationships is issued and they are propagated directly to the new output file without parsing. If a shop is using the Flat File and running Assist weekly, only those members that have changed during the week will be parsed. This should be a small percentage of their total baseline members.
7-58
New Features and Capabilities with Change Man Assist
NOTES Do not archive the ISIC records before running a full assist (not incremental). The last changed relationship will be created in the full assist and is needed for incremental processing as well as processing same named members in multiple libraries.
Multi-Tasking Support (or Threads)

The 4.1.6 version of Assist would process one library at a time. A new parameter was added to each Change Man instance that specifies the number of libraries that can be processed simultaneously. Each library is processed as a separate task (or thread). By running as separate (parallel) tasks the library processing is expected to complete much faster than when processed one after another. See Load Balancing. To facilitate the user specified maximum, a new parameter was added to the PARM= field on the EXEC statement: MAXTASKS=xx. This parameter allows for two digits so the effective maximum is 99 subtasks, or libraries that can be processed simultaneously. The default upon installation is to process eight libraries simultaneously, though this should be reviewed with system capacity and processing power in mind.
Storage Considerations
Version 5.1 of Assist requires more storage than previous versions. This is because all directories for all libraries are maintained in storage while processing the application. This is necessary to process multiple copybooks with the same name in different baseline libraries. The rule of thumb for estimating storage requirements is to start with twelve megabytes minimum and then add two to four megabytes per Library Processing Subtask. The number of Library Processing Subtasks is controlled by the job parameter MAXTASKS=xx where xx is an integer representing the max number of simultaneous Library Processing Subtasks.
4095 Baseline Library limit removed

The maximum number of baseline libraries that can now be processed in a single run is increased from 4095 to 46,656.
User Guide
7-59
7 Auditing Packages
7-60
FREEZING A PACKAGE
After building, testing, and auditing your package, you must freeze it. This Freezing your package makes it available for approval and prevents further modification. Before freezing a package, Change Man checks the following things: 1 If the package and its components have the same promotion level. This applies only if the administrator has set the promotion rule to zero and the package has been promoted or demoted. 2 If attached online forms are outstanding This applies only if the Online Forms Manager Option is licensed, and customized forms have been added to the package. If the forms are not approved, then the package will not freeze. 3 Are all components activated? If the component is successfully copied into the appropriate staging library during the stage process, and if the compile, link/edit, bind, etc. procedure is completed for source components, then Change Man will change the status of the component to Active. 4 Did the package pass the audit? (Optional) The audit return code selected by the application's administrator must not be exceeded. If the package is allowed to be frozen, Change Man changes the package's status from DEV to FRZ, which locks out anyone from staging into the package's libraries. A record of this event (freeze package) is placed in the log. If, for any reason, someone decides that your change package needs to be modified before it can be approved, they can selectively unfreeze the component that they want modified. Once modified, the component(s) can be refrozen.
8-1
8 Freezing a Package
If components in a package have been selectively unfrozen, modified, and refrozen, then any approvers who have approved a package will not be notified of the changes. To reset the approvers, you should revert the package. If you are using CMNEX001, the installation date of a package in FRZ status can be updated through Option 2 (Update) from the Build Options menu; otherwise, you can only update the installation date of a package in DEV status. For Option 7, depending on how Change Man was generated, either Option O (Onsite) or Option R (Remote Site) is displayed. At freeze time a separate, asynchronous process is spawned to invoke the CMNPMXJB module which will perform the functions listed below. Control is returned to the user before the job streams are built, and the asynchronous task continues with the JCL build. The package is effectively frozen but the install/baseline ripple job streams will not be available until the asynchronous task (CMNADSP) completes successfully. This also means that Approval of a frozen package cannot take place until the JCL build task has completed. Builds applicable skeleton jobs, by site configuration, as indicated in the following tables: At an ALL site Package Type
PERMANENT TEMPORARY PERMANENT/DB2 TEMPORARY/DB2
Job Name (CMNxx)

20*,30,50,55 20T,31T 20,21,32,30,49.50,56,55 20T,21,49,31T
At a DP site with IEBCOPY (need CMN65 for revert)
Package Type
PERMANENT TEMPORARY PERMANENT/DB2 TEMPORARY/DB2
Job Name (CMNxx)

10,11,15,19,20,25,29,30,50,51,55,59 10,11,15,19,20T,25,29,31T,35,39 10,11,15,19,21,20,25,29,30,32,49,50,51,56,55,59 10,11,15,19,21,20T,25,29,49,31T,35,39
8-2
Accessing the Freeze Options Panel
At a DP site with OTHER (need CMN64-65 for Revert) Package Type

PERMANENT TEMPORARY PERMANENT/DB2
Job Name (CMNxx)

10,11,14,15,18,19,20,24,25,28,29,30,50,51,54,55,58,59 10,11,14,15,18,19,20T,24,25,28,29,31T,34,35,38,39 10,11,14,15,18,19,21,22,20,24,25,28,29,32,30,49,50,51,54,56, 55,58,59 10,11,14,15,18,19,21,20T,24,25,28,29,49,31T,34,35,38,39
TEMPORARY/DB2
The following jobs are created in all configurations, in the situations listed. CMN17 is present if an external scheduler is used. CMN30 and CMN55 are present for all permanent packages. (baseline ripple and backout (reverse ripple), respectively) CMN37 and CMN57 are present for all permanent packages if the DB2 I/A table exists. (baseline ripple and backout, respectively, with CMNDB2TM) Submits, through CMNSCHED, the skeleton jobs at the appropriate time. You may use Exit 28 to split the process of creating the skeleton jobs. Also, you may defer splitting the skeleton jobs until the final approval of the package. When the CMN instance comes up and DB2 (or just Change Mans connection to it DB2 Attach) is down, CMNPMXJB, through CMNBATCH, writes SYSIN cards to the delay file to submit the CMN37 and CMN57 jobs. Otherwise, the JCL for CMN37 and CMN57 is not used.
The scheduling record for a package is created at Approve time. This means that updates to the install date of a package in FRZ status being implemented with the Change Man internal scheduler are captured. At approve time, the scheduling record is built with the latest install date originally entered or updated by the user. Provided your internal scheduler isnt Change Man, you can change the scheduled installation date even after a package is frozen.
ACCESSING THE FREEZE OPTIONS PANEL

You use the Freeze Options panel to do any of the following: Freeze the package online
User Guide
8-3
Submit a batch job to freeze the package Selectively unfreeze packages Reset a Freeze in Progress indicator Resubmit the JCL build process
To access the Freeze Options panel (CMNFRZ01), from the Primary Option Menu, select option 2.
CMNFRZ01 ----------------------- FREEZE OPTIONS --------------------------OPTION ===> 1 PACKAGE ID ===> NAVI000005 1 Online 2 Batch 3 Selective 4 Reset 5 Resubmit Automatic Online or - Freeze package online - Freeze package in batch - Selectively unfreeze/refreeze package components - Reset indicator after unsuccessful batch freeze - Resubmit the JCL build process promotion after freeze ===> NO (Y/N) batch promotion ===> (O-Online, B-Batch)
FREEZE A PACKAGE ONLINE

From the Freeze Options panel (CMNFRZ01), take the following steps to freeze a package in the foreground (online): 1 2 Select option 1. In the Package ID field, type the package ID. To freeze a package, it must meet the following criteria 3 It must be in development (DEV) All components must be active and have the same promotion level Any online forms must be approved.
If you want to promote the package immediately after freezing it, in the Automatic Promotion after Freeze field, type Yes and press Enter.
8-4
Freeze A Package in Batch
NOTES The global and application administrators enable this function. Change Man runs your freeze request. A panel displays asking you to wait while Change Man checks to make sure all of your components are active and notifies package approvers of the status change. When it successfully completes, the package status changes to FRZ (freeze), and the JCL build process is initiated. No changes can now be made to any package components unless they are unfrozen or the whole package reverted. The approval process can begin once the JCL build process has completed. You will be notified of this event. If you requested an automatic promotion after freeze, Change Man automatically fully promotes the package when the freeze has been successfully completed. If your administrator has set up your application to allow for online promotion, then this option is run in the foreground. If it is not allowed the job is submitted to run in the background.
FREEZE A PACKAGE IN BATCH

The Package in Batch panel (CMNFRZ02) allows you to type job card information for the batch freeze process. A batch freeze process requires the use of the CMNAPI or CMNRPC procedures, which is set up by the administrator. To freeze a package in batch, take the following steps: 1 From the Freeze Option panel, select option 2. The Package in Batch panel (CMNFRZ02) displays.
PACKAGE IN BATCH -------------------------------
CMNFRZ02 ----------------OPTION ===> PACKAGE ID: NAVI000005
JOB STATEMENT INFORMATION: ===> //WSER85A JOB ,ACCOUNT INFORMATION______________________________________ ===> //*_____________________________________________________________________ ===> //*_____________________________________________________________________ ===> //*_____________________________________________________________________ Press ENTER to process; Enter END command to exit.
In the Package ID field, type the package ID.
User Guide
8-5
In the Job Statement Information, type the job card information, and press Enter to process.
When the batch freeze process builds JCL for two jobs: to create the batch job, and to freeze the batch. The freeze is executed when this job is selected. If the freeze is successful with a return code 0, the next control card for promotion is acted upon. This runs promotion and the JCL is built to run promotion as a batch job. (If the application parameters specify that promotion should be run in the foreground, a background job is also submitted.). NOTES When you freeze a package in batch mode, the statistics in the X-node dataset seem to disappear. This is an ISPF limitation. When a package is frozen, the TSO ID of the person or the jobname is used for all the install jobs in the X-node dataset. If the TSO ID or the jobname is 8 characters long, ISPF will not display the statistics, but they do exist. You can get the statistics if you dump the directory using IEBGENER or a similar copy utility. A workaround for this ISPF limitation is to keep the jobname 7 characters or less.
UNFREEZE AND REFREEZE COMPONENTS

This feature allows you to selectively unfreeze and refreeze components (not the package) in the event that you want to update particular components without affecting the entire frozen package. If you want to unfreeze an entire package you have to revert it. To access the Unfreeze/Refreeze Component panel (CMNUNFRZ), take the following steps:
8-6
Unfreeze and Refreeze Components
From the Freeze Options panel, select option 3. The following panel displays.
CMNUNFRZ ----------------- UNFREEZE/REFREEZE NAVI000009 ----- ROW 1 TO 6 OF 6 COMMAND ===> SCROLL ===> PAGE LINE CMDS: F-Freeze all, U-Unfreeze all, S-Selective refreeze/unfreeze
PACKAGE CATEGORY STATUS FUNCTION _ General FROZEN _ Non-Source FROZEN _ Source and Load FROZEN _ Utilities FROZEN u Onsite FROZEN _ Custom Forms FROZEN ******************************* Bottom of data ******************************
Complete the fields on the Unfreeze/Refreeze Component panel. Type any of the following line commands: Command
F
Description
Freeze components that were previously unfrozen.,
For each component in which an F was entered, the message, FREEZE, appears at the STATUS column. The status of the change package is still Frozen (FRZ) and the package is now available for approve/reject processing.
S
Selectively refreeze and unfreeze components. By entering an S next to a package component, a panel appears which allows you to selectively unfreeze and refreeze components. Unfreeze components so that they can be restaged (overlaid) by application analysts after modification.
For each component in which a U was entered, the message, UNFREEZE, appears in the STATUS column. The status of the change package is still Frozen (FRZ), but the unfrozen component can be modified. The change package cannot be approved or rejected until all components have been refrozen.
You can only unfreeze components of change packages that are in frozen (FRZ) status. If the change package is in Rejected (REJ) status, the change package must be reverted to Development (DEV) status before any component can be modified.
User Guide
8-7
NOTES For non-source, source and load, and utilities components, you can sort by any field in ascending order, using the Sort command with the keywords NAME or MEMBER. Then, you can issue a Locate command to find a component name. 3 Press Enter to process. If you type a line command next to General, Change Man acts upon your line command, changing the contents of your change package accordingly. If you type a U at the line command, you unfreeze the general information and permit updates (option 2 from the Build Options menu) to that information. If you type a line command next to non-source, Change Man will present you with the Unfreeze/Refreeze Components panel. If you type a line command next to source and load, Change Man will present you with the Unfreeze/Refreeze Components panel. You can enter SL as a line command on the Unfreeze/Refreeze Components panel to display the source and load relationships of a source component. If you type a line command next to utilities, Change Man will present you with the UnFreeze Utility Information panel. You can unfreeze utility requests so they can be restaged (overlaid) after modification. If you type a line command next to remote Sites, or onsite, Change Man acts upon your line command, changing the contents of your change package accordingly. This includes install date information; however, if you have used OTHER as your schedulers and the CMN17 job has already been generated, the change may not be passed to the job unless the skeleton is regenerated. If you type a U at the line command, you unfreeze the remote site or onsite information and permit updates (option 2 from the Build Options menu) to that information. If you type a line command next to custom forms, Change Man will present you with the Freeze/Unfreeze Custom Component panel.
RESET THE FREEZE IN PROGRESS INDICATOR

When a batch freeze is submitted, a freeze in progress indicator is turned on. This will prevent you from submitting another freeze (on-line or batch) or selective unfreeze on the package. If the job never completes (i.e. job is canceled, system crash, etc.), this option lets you reset this indicator and submit another freeze on the package.
8-8
Resubmit Install JCL Build Request
To reset the In Progress indicator, select Option 4 . The message INDICATOR RESET will display in the upper right hand corner of the screen. Then pressing PF1 will display the long message (CMN3036I), indicating that the Freeze in Progress indicator has been reset.
RESUBMIT INSTALL JCL BUILD REQUEST

If, for any reason, the asynchronous build of JCL following the freeze process fails, this option can be used to re-initiate the build for the frozen package.
User Guide
8-9
8-10
PROMOTING TO A LOCAL SYSTEM
This chapter describes how to establish promotion levels for a local system. Promotion is a facility for setting up intermediate environments or promotion levels that can be used for model office, quality assurance, unit and system testing. Promoting is the process of promoting change packages or components from staging libraries into specific promotion levels. Demoting is the process of deleting components logically or physically from these levels. Change Man lets you configure the promotion facility in numerous ways, depending on different change management strategies. Based upon how your administrator has set up the promotion facility: Promoting from one level to another may be a logical copy or a logical move; that is, the components may remain in the previous environment or they may be deleted from the previous environment upon promotion. Demoting a package from a particular promotion level may or may not be a physical demotion; that is, the components may or may not be physically deleted from that promotion level. Promoting and demoting of both packages and components can be performed in one of three ways: Only online Only batch Online or batch, at the users discretion NOTES Some components, notably DB2 components requiring a BIND, must be promoted using the batch method.
9-1
9 Promoting to a Local System
USING THE PROMOTION FACILITY FOR INTERMEDIATE TESTING

By setting up different promotion levels for specific phases of testing, promotion can be linked to the Change Man approval process to ensure that all components are promoted for intermediate testing before packages are approved.
Third Party Testing

Third party testing includes quality assurance testing and systems testing.
Unit Testing of Online Systems

Often developers perform unit testing of package components from staging libraries. However, staging libraries, which are dynamic and built by package, are not an appropriate place to test online systems such as CICS, DB2 or IMS regions. Instead, it is preferable to test online systems from a static library. Therefore, you can choose to set up a level of promotion that is available for unit testing of online systems. If your administrator has chosen promotion rule 0, then you can promote a package prior to freeze. This is particularly useful when using promotion for unit testing of online systems.
PROMOTING AND DEMOTING CHANGES

You initiate all promotion and demotion activity from the Promote Change Package panel. Take the following steps to access and complete the Promote Change Package panel. 1 From the Primary Options menu, select option 3 and press Enter. The Local or Remote Promotion panel (CMNSLRPM) displays.
CMNSLRPM ----------------- LOCAL OR REMOTE PROMOTION -------------------OPTION ===> 1 1 2 Local Remote - Local promotion (standard promotion) - Remote promotion (remote site promotion)
9-2
Promoting and Demoting Changes
On the Local and Remote Promotion panel, type 1 and press Enter . The Promote Change Package panel (CMNRPM00) displays.
CMNPRM00 ------------------- PROMOTE CHANGE PACKAGE --------------------------COMMAND ===> PACKAGE ID ===> NAVI000011 Press ENTER to process; Enter END command to exit.
From the Promote Change Package panel, type the package ID and press Enter. The Promote Change Package panel appears.
CMNPRM01 ------------------- PROMOTE CHANGE PACKAGE ------------------------COMMAND ===> SCROLL ===> CSR PACKAGE ID: NAVI000005 CREATOR: WSER85 - 0 - 2 (P-Promote, D-Demote, C-Check for overlay) (O-Online, B-Batch) (Required for Action C) STATUS: DEV INSTALL DATE: 19971230
CURRENT PROMOTION LEVEL: MAXIMUM PROMOTION LEVEL: ACTION REQUESTED ONLINE OR BATCH LEVEL TO CHECK ===> P ===> O ===>
PROMOTE/DEMOTE HISTORY LVL NICKNAME DATE TIME ID **************************** Bottom of data *****************************
The following table describes the fields of the Promote Change Package panel (CMNPRM01)
Field
CURRENT PROMOTION LEVEL MAXIMUM PROMOTION LEVEL
Description
The packages current promotion level
The maximum number of levels you can promote the package (set at package creation).
User Guide
9-3
Field
ACTION REQUESTED
Description
Type one of the following options:
P - Promote the change package. D - Demote the change package. C - Check for overlay between staging and the specified promotion level.
ONLINE OR BATCH
O - Online promotion. B - Batch promotion.

LEVEL TO CHECK If you typed C in the action requested field, indicate the level to check for overlay.
From this panel, you can: Promote (P - promote) or demote (D - demote) packages or components in batch (B - batch or online (O - online). Check (C -check) a promotion level for components in common with the change package.
NOTES A check is always performed during a promotion. Review promotion/demotion history of the change package, listed in reverse chronological order.
Promoting a Change Package

If you want to immediately promote a package and avoid filling out batch job card information, you can promote packages online. If you want to run the promotion job in the background and avoid locking your screen up during the promotion process, you can promote packages in batch mode.
Promoting Online
To promote a change package online: 1 Type P in the action requested field on the Promote Change Package panel (CMNPRM01).
9-4
Type O in the online or batch field. This displays the Promote Options panel (CMNPRM09) shown below. From this panel you have the option of either promoting a package, or selectively promoting components from a package which has previously been fully promoted.
CMNPRM09 ---------------------- PROMOTE OPTIONS ----------------------------OPTION ===> f F - Full promotion of the entire package to another promotion level S - Selective promotion of components to another promotion level PACKAGE ID: NAVI000005 CREATOR: WSER85 STATUS: DEV INSTALL DATE: 19971230 CURRENT PROMOTION LEVEL: MAXIMUM PROMOTION LEVEL: 0 2 -
NEXT PROMOTION LEVEL ===> 1 BYPASS OVERLAY CHECK ===> NO
(Y-Yes or N-No)
To Promote the change package, type F in the option field. If your administrator has set a promotion rule of 0, you can override the level displayed in the next promotion level field. NOTES Change Man will check for common components before promoting. The Confirm Promotion panel will be displayed if common components are discovered. (See Checking for Common Components on page 9-11.) Warning. If you choose to bypass Overlay Checking, the modules selected may overlay an existing module, and there is no second chance to stop this process. If you use Overlay Checking, you will have a chance to view any modules being overlaid, and you can stop the promotion.
Promoting in Batch
To promote a change package in batch, do the following on the Promote Change Package panel (CMNPRMO1): 1 2 Fill in the required fields and type P in the action requested field Type B in the online or batch field. This displays the Promote Options panel (CMNPRM02) shown below. From this panel you have the option of either promoting a package, or selectively promoting components from a package.
User Guide
9-5
CMNPRM02 ---------------------- PROMOTE OPTIONS -----------------------------OPTION ===> f F - Full promotion of the entire package to another promotion level S - Selective promotion of components to another promotion level PACKAGE ID: NAVI000005 CREATOR: WSER85 CURRENT PROMOTION LEVEL: MAXIMUM PROMOTION LEVEL: 0 2 STATUS: DEV INSTALL DATE: 19971230
NEXT PROMOTION LEVEL ===> 1 BYPASS OVERLAY CHECK ===> NO
(Y-Yes or N-No)
Complete the job card information to submit the promotion job in batch. Promote the change package by typing F in the option field. NOTES If your administrator has set a promotion rule of 0, you can override the level displayed in the next promotion level field. Warning. If you choose to bypass Overlay Checking, the modules selected may overlay an existing module, and there is no second chance to stop this process. If you use Overlay Checking, you will have a chance to view any modules being overlaid, and you can stop the promotion.
Demoting a Change Package

Demotion is the inverse of promotion. Demoting a change package removes the change package components from promotions specified by the person requesting the demotion. If you want to immediately demote a package and avoid filling out batch job card information, you can demote packages online.
9-6
If you want to run the demotion job in the background and avoid locking your screen up during the demotion process, you can demote packages in batch mode.
NOTES Components that have an incomplete (incomp) status, on the Stage panel (CMNSTG01), cannot be demoted.
Demoting A Package Online

To demote a change package: 1 Type D in the action requested field on the Promote Change Package panel (CMNPRM01). Type O in the online or batch field. This displays the Demote Options panel (CMNPRM10) shown below. From this panel you have the option of either demoting a package, or selectively demoting components from the package.
CMNPRM10 ----------------------- DEMOTE OPTIONS ----------------------------OPTION ===> f F - Full demotion of the entire package to level 0 (Staging) S - Selective demotion of components to level 0 (Staging) PACKAGE ID: NAVI000005 CREATOR: WSER85 STATUS: ACTIVE INSTALL DATE: 19971230 CURRENT PROMOTION LEVEL: MAXIMUM PROMOTION LEVEL: DEMOTE FROM LEVEL 3 5
===> 3
Demote the change package by typing F in the option field to perform a full demotion of a change package.
Demoting in Batch
Demote a change package in batch. 1 Type D in the action requested field on the Promote Change Package panel (CMNPRM01).
User Guide
9-7
Type B in the online or batch field. This displays the Demote Options panel (CMNPRM04) shown below. From this panel, you have the option of either demoting a package, or selectively demoting components from the package.
CMNPRM04 ----------------------- DEMOTE OPTIONS ----------------------------OPTION ===> F - Full demotion of the entire package to level 0 (Staging) S - Selective demotion of components to level 0 (Staging) PACKAGE ID: NAVI000005 CREATOR: WSER85 STATUS: DEV INSTALL DATE: 19971230 CURRENT PROMOTION LEVEL: 0 MAXIMUM PROMOTION LEVEL: 2 DEMOTE FROM LEVEL ===> 1
Complete the job card information to submit the demotion job in batch. Demote the Change package by typing F in the option field.
PROMOTING AND DEMOTING COMPONENTS

Promoting Components Selectively Promote Components
To promote components online or in batch, see the section Promoting a Change Package on page 9-4. Note: Full promotion is required before a selective promotion can be attempted. To selectively demote components from the package, see the section Demoting Components from a Package on page 9-10.
9-8
Promoting and Demoting Components
Repromote Select Components.

You selectively repromote components online from the Promote Options panel (CMNPRM09), or in batch from the Promote Options panel (CMNPRM02). In either case: 1 2 Type S in the option field. Press Enter to process the request.
This displays a list of components from which to select the components to promote. The following conditions might apply depending on how your administrator has set up your Change Man subsystem, and whether you are Promoting online or in batch. 3 4 If your administrator has set Promotion Rule 0 , you can override the entry in the next promotion level field. If you are promoting in batch, you must provide valid job card information. If common components are discovered, the Confirm Promotion panel will be displayed. Type the line command S next to the component you want to promote. Type D to deselect components that were selected in error.
CMNPRM05 --------------- : NAVI000005 COMPONENTS ---------------------------COMMAND ===> SCROLL ===> CSR Enter END command to process or CANCEL to exit. CURRENT PACKAGE PROMOTION LEVEL: NEXT COMPONENT PROMOTION LEVEL: NAME TYPE ALIAS-OF ALLIO SRC PROMOTION - 0 - 1 DATE TIME 1997/08/10 09:10 ID STATUS WSER85 ACTIVE
User Guide
9-9
Demoting Components from a Package

When configuring your promotion environment, the administrator will have chosen a rule that controls the ability to demote packages and components. You may or may not be able to demote components of a package. Once a package or components have been demoted, you may or may not have to re-promote though previous levels. If your administrator has selected rules 0, 1, or 2, then you can selectively demote components from a package. To demote components from a package, do the following: 1 2 3 Select Option 3 on the Primary Option menu. Type a change package number on the Promote Change Package panel. Type D for Demotion in Promote Change Package panel. The following panel displays.
CMNPRM04 ----------------------- DEMOTE OPTIONS ----------------------------OPTION ===> F - Full demotion of the entire package to level 0 (Staging) S - Selective demotion of components to level 0 (Staging) PACKAGE ID: NAVI000005 CREATOR: WSER85 STATUS: DEV INSTALL DATE: 19971230 CURRENT PROMOTION LEVEL: 0 MAXIMUM PROMOTION LEVEL: 2 DEMOTE FROM LEVEL ===> 1
Demote Option Panel (CMNPRM04) 4 Demote the change package. Type S to perform a selective demotion of components from a change package.
9-10
Checking for Common Components
If the administrators have determined that promotion shall be done in batch mode, complete the job card information.
Press Enter. Change Man displays a Component List for selecting the components to be demoted.
CHECKING FOR COMMON COMPONENTS

Whenever you promote a package, Change Man invokes a common module check routine. If it detects common modules in your package and in the target promotion data set, it displays a panel that does the following: Warns you of a possible overlay Lists the names and library types of the common modules Lists all change packages that contain a module common to the one you are promoting
The history record, which resides in a package at the promotion level being checked, displays a list of all packages that could contain a module common to the one you are promoting. At that time, you have the option of either continuing the promotion by typing End and pressing Enter, or canceling it, by typing CANCEL and then pressing Enter. To display the components in common between the change package and the next level of promotion: Type C in the Promote Change Package panel. The Common Components panel (CMNPRM08) appears.
CMNPRM08 --------------------- COMMON COMPONENTS ---------------------------COMMAND ===> SCROLL ===> CSR Press ENTER to process or enter END to exit. PACKAGE ID: NAVI000005 CREATOR: WSER85 - 0 - 2 PROMOTION DATE TIME STATUS 1997/06/01 09:00 ACTIVE STATUS: DEV INSTALL DATE: 19971230
CURRENT PROMOTION LEVEL: MAXIMUM PROMOTION LEVEL: NAME TYPE PACKAGE ID STA _ ALLIO SRC NAVI000001
User Guide
9-11
9-12
PROMOTING TO A REMOTE SYSTEM
10
Promotion is a facility for setting up intermediate environments or promotion levels that you can use for model office, quality assurance, unit, and system testing. With this facility, you promote change packages or components from staging libraries into specific promotion levels. The facility for deleting components logically or physically from these levels is called demotion. This chapter describes remote promotion, a feature of Change Man that enables you to establish promotion levels for a remote system. For information on promoting to a local system, see Chapter 15. Promoting to a Local System. With remote promotion, you can promote to local levels and simultaneously promote to multiple remote sites. Similarly, remote demotion enables you to demote a change package or selective components of a change package to promotion level 0 from a remote site.
HOW ADMINISTRATORS CAN CONFIGURE REMOTE PROMOTION

How your administrators have configured the (remote) promotion facility determines which of the following restrictions apply at your site. Remote promotion from one level to another might be a logical copy or a logical move. This means that the components might remain in the previous environment, or be deleted from the previous environment upon promotion. If your administrator has chosen Promotion Rule 0, then you can remotelypromote a package prior to freeze. This might be particularly useful when you use promotion for unit testing of on-line systems. Remote demotion of a package from one level might not be a physical demotion; that is, the components might not be physically deleted from that promotion level. You might not be able to demote components of a package. Once a package (or components of a package) has been remotely-demoted, you might not be required to remotely-repromote through previous levels.
10-1
10 Promoting to a Remote System
If your administrator selected Promotion Rules 0, 1, or 2, you can selectively perform remote promotion or demotion of components in a package.
The following is a list of tasks involving remote promotion, with references to the appropriate pages in this chapter: Promoting Change Packages or Components to a Remote Site on page 10-2. Demoting Change Packages or Components from a Remote Site on page 10-11. Checking for Common Components at a Remote Site on page 10-15. Checking for Common Components at a Remote Site on page 10-15.
PROMOTING CHANGE PACKAGES OR COMPONENTS TO A REMOTE SITE

Promote a change package or selective components of a package to a remote site. 1 From the Primary Option menu, select option 3 and press Enter. The Local or Remote Promotion (CMNSLRPM) panel displays.
CMNSLRPM ----------------- LOCAL OR REMOTE PROMOTION -------------------------OPTION ===> 1 2 Local Remote - Local promotion (standard promotion) - Remote promotion (remote site promotion)
On the Local or Remote Promotion panel, select option 2 (Remote Promotion) and press Enter. The Remote Promote Change Package panel (CMNRPM01) appears.
CMNRPM00 --------------- REMOTE PROMOTE CHANGE PACKAGE --------------------COMMAND ===> PACKAGE ID ===> NAVI000005 Press ENTER to process; Enter END command to exit.
10-2
Promoting Change Packages or Components to a Remote Site
Type the change package ID and press Enter. The Remote Promotion Site List panel (CMNRPM01) appears with lists the available remote sites, the administration-defined force demotion flags, and the prior promotion history of the package at those remote sites.
CMNRPM01 ----------------- REMOTE PROMOTION SITE LIST ----------------------COMMAND ===> SCROLL ===> CSR Press ENTER to process; Enter END command to exit. PACKAGE ID: NAVI000005 CREATOR: WSER85 STATUS: DEV INSTALL DATE: 19971230
FORCED DEMOTION FROM REMOTE PRIOR PROMOTION SITES PRIOR PROMOTION SITE NAME REMOTE LOCAL REMOTE LOCAL _ remote1 x x ***************************** BOTTOM OF DATA*****************************
The following table describes the fields on the Remote Promotion Site List panel. Field
PACKAGE ID CREATOR STATUS INSTALL DATE REMOTE SITE NAME
Description
Displays the package ID Displays the creator of the package. Displays the status of the package. Displays the installation date (yyyymmdd format) of the package. Displays the remote site of the planned promotion.
User Guide
10-3
Field
FORCED DEMOTION FROM PRIOR PROMOTION SITES (REMOTE, LOCAL)
Description
Displays the administratively-defined force demotion flags that apply during remote promotion. The flags are forced (YES ) and not forced (NO ). If force demotion (remote) is YES , then a package from a previously promoted site must be demoted prior to promotion at the selected remote site. Conversely, if a package is promoted to a remote site and the force flag is YES for the promoted site or the selected remote site, then promotion is disallowed. If the force flag is NO for both the promoted site and the selected remote site, then promotion is allowed. If force demotion (local) is YES , then a package from a local site must be demoted prior to promotion at the selected remote site. Conversely, if a package is promoted locally and the force flag is YES for the selected remote site, then promotion is disallowed. If the force flag is NO for the selected remote site, then promotion is allowed.
PRIOR PROMOTION (REMOTE, LOCAL)
Displays prior promotion.
With this information available prior to doing a promotion, you might avoid receiving an error message. 4 On the Remote Promotion Site List panel, type an S next to the remote site name where you want to promote the package or components and press Enter. The Promote/Demote A Change Package (CMNRPM02) panel displays.
10-4
CMNRPM02 -------------- PROMOTE/DEMOTE A CHANGE PACKAGE ---COMMAND ===> Press ENTER to process; Enter END command to exit. PACKAGE ID: NAVI000005 CREATOR: WSER85 STATUS: DEV
ROW 1 TO 8 OF 8 SCROLL ===> CSR
INSTALL DATE: 19971230
REMOTE PROMOTION SITE : remprm1 CURRENT PROMOTION LEVEL: STAGING + 0 MAXIMUM PROMOTION LEVEL: TESTINGA + 2 ACTION REQUESTED LEVEL TO CHECK ===> p ===> (P-Promote, D-Demote, C-Check for overlay) (Required for Action C)
REMOTE HISTORY MOD/CNT PROMOTION DATE TIME ID REMOTE Full Promotion 4 2 TESTINGA 1997/06/19 09:44 WSER85 COMPLETED Full Promotion 4 2 TESTINGA 1997/06/19 09:39 WSER85 FAILED Full Promotion 4 2 TESTINGA 1997/06/18 18:33 WSER85 SUBMITTED Full Promotion 7 1 TESTINGA 1997/06/18 14:58 WSER85 COMPLETED Selective Promotion 3 2 TESTINGA 1997/06/18 14:04 WSER85 COMPLETED First Promotion at 0 2 1 TESTINGA 1997/06/18 14:02 WSER85 SUBMITTED Full Demotion 1 2 TESTINGA 1997/06/18 13:58 WSER85 COMPLETED Full Promotion 7 1 TESTINGA 1997/06/18 13:55 WSER85 SUBMITTED
The Promote/Demote A Change Package panel enables you to promote, demote, or perform common module checking.
Field
REMOTE PROMOTION SITE CURRENT PROMOTION LEVEL MAXIMUM PROMOTION LEVEL ACTION REQUESTED
Description
Displays the site where you want to promote the package.
Displays the packages current promotion level.
Displays the highest level you can promote the package to at the selected remote site.
P Promote the change package D Demote the change package C Check for overlay between the staging and the specified promotion level
LEVEL TO CHECK If you chose C in the action requested field, type the level to check for overlay.
User Guide
10-5
Field
REMOTE HISTORY
Description
Displays a previous action (promotion or demotion) performed on this package. The four different actions are: Full promotion, which means that the package was fully promoted and all components in the package (components currently eligible for promotion) were promoted Full demotion, which means that the package was fully demoted and all components in the package (components currently eligible for demotion) were demoted to staging level 0. Selective promotion, which means that a component or components in the package were selected and promoted. Selective demotion, which means that a component or components in the package (components currently eligible for demotion) were selected and demoted.
First promotion at 0, which means that a component or components in the package were selected and promoted and the package was at level 0. This is the same as selective promotion, except the package was at level 0 and the package level is now at the level selected for the selective promotion.
Note:This is the only selective promotion allowed beyond the package level.
MOD/CNT PROMOTION Displays the number of components that were last promoted or demoted. Displays the administration-defined promotion level and the eight-character nickname for that promotion level (at the remote site) of the last promotion or demotion.
Note:The maximum promotion level value is the upper limit for this field.
DATE TIME ID REMOTE Displays the date (yyyymmdd format) of the last remote promotion or demotion. Displays the time of the last promotion or demotion. Displays the TSOID of the person who performed the last promotion or demotion. Displays the status of the last remote promotion or demotion. The valid values are: SUBMITTED, which means that the remote promotion or demotion job has been submitted for job execution. COMPLETED, which means that processing of the remote promotion or demotion job has completed successfully. FAILED, which means that processing of the remote promotion or demotion job has completed, but it was unsuccessful.
Note:Job completion and failure is determined by a final notification that all processing has
been completed by the remote processor.
The Promote/Demote a Change Package panel enables you to promote, demote or perform common module checking (i.e., Check for Overlay) prior to promotion. The following table describes the fields on the Promote/Demote a Change Package panel.
10-6
NOTES The status of a staged or deleted component is reflected in the query function and the selective Promotion or Demotion list: 5 A restaged component is displayed on both selective promotion or demotion lists and is eligible for both. Until a deleted component is at level 0, it is displayed on the selective Demotion list and is eligible for demotion. On the Promote/Demote A Change Package panel, type P in the action requested field and press Enter. The Promote Options panel displays.
CMNRPM03 ---------------------- PROMOTE OPTIONS ----------------------------OPTION ===> S F - Full promotion of the entire package to another promotion level S - Selective promotion of components to another promotion level PACKAGE ID: NAVI000005 CREATOR: WSER85 STATUS: DEV INSTALL DATE: 19971230 REMOTE PROMOTION SITE : remprm2 CURRENT PROMOTION LEVEL: STAGING + 0 MAXIMUM PROMOTION LEVEL: TESTINGA + 2 NEXT PROMOTION LEVEL BYPASS OVERLAY CHECK ===> 2 ===> NO (blank, * or 0 for a list) (Y-Yes or N-No)
This panel displays many of the fields that show on the previous panel and the current promotion level (0 or staging). Additionally, it lets you specify full or selective promotion, the level to promote to, and the job statement information. Warning. If you choose to bypass Overlay Checking, the modules selected may overlay an existing module, and there is no second chance to stop this process. If you use Overlay Checking, you will have a chance to view any modules being overlaid, and you can stop the promotion. 6 On the Promote Options panel, choose either option F to promote the whole package to another level, or option S to selectively promote components in the package.
User Guide
10-7
Specify the next promotion level. In this scenario, we will specify level 2 .
If you are unsure about the promotion levels that are defined for your application, you can display a list of levels by leaving the next promotion level field blank or entering a 0 or *. The Remote Promotion Level List panel displays listing the available promotion levels (at the remote site) and the nicknames assigned to those levels.
CMNRPM07 ----------COMMAND ===> f
REMOTE PROMOTION LEVEL LIST -----------------SCROLL ===> CSR
Press ENTER to process; Enter END command to exit. PACKAGE ID: NAVI000005 CREATOR: WSER85 STATUS: DEV INSTALL DATE: 19971230 CURRENT PROMOTION LEVEL: NICKNAME remprm1 remote2 test101 testinga LEVEL 00 01 02 03 + 1
_ _ _ _
From the Remote Promotion Level List panel, you can do either of the following: Advance to the next panel in the sequence, by entering an S next to the nickname for the level you want to promote. Return to the Promote Options panel and cancel your selection on this panel, by entering the End command. By default, a 0 is displayed in the next promotion level field on the Primary Options panel.
Because the promotion level has not yet been selected, the current promotion level field retains the value (0 ) from the previous panel. NOTES Provided your administrator has set a Promotion Rule of 0 , you can use the exit CMNEX027 to override the level displayed in the next promotion level field. 8 From the Promote Options panel, complete the Job Statement Information to submit the promotion job and press Enter.
10-8
Selective Promotion of Components

From the Promote Options panel, if you typed S in the command line, the Component List panel (CMNRPM05) appears.
CMNRPM05------------PROMOTE: COMMAND ===> DEMO000045 COMPONENTS ------ROW 1 TO 10 OF 10 SCROLL ===> CSR
Enter END command to process or CANCEL to exit. PACKAGE ID: NAVI000005 CREATOR: WSER85 STATUS: DEV INSTALL DATE: 19971230
REMOTE PROMOTION SITE : TEST CURRENT PACKAGE PROMOTION LEVEL: STAGING + 0 NEXT COMPONENT PROMOTION LEVEL: TEST101 + 1 NAME TYPE ALIAS-OF PROMOTION DATE _ AUDIT CPY 0 STAGING 1997/07/18 S CMN$$BND CPY 0 STAGING 1997/07/17 _ CMNEX009 LOD 0 STAGING 1997/07/18 S CMNEX009 SRC 0 STAGING 1997/07/17 S CMNEX026 LOD 0 STAGING 1997/07/17 S CMNEX026 CPY 0 STAGING 1997/07/18 _ CMNEX027 LOD 0 STAGING 1997/07/17 S CMNEX027 SRC 0 STAGING 1997/07/18 S CMNEX035 LOD 0 STAGING 1997/07/17 _ CMNEX035 SRC 0 STAGING 1997/07/18 ******************************* BOTTOM OF DATA TIME ID REQUEST STATUS 18:33 WSER85 RESTAGED 22:13 WSER85 13:55 WSER85 OVERLAID 22:13 WSER85 OVERLAID 22:13 WSER85 18:33 WSER85 22:13 WSER85 RESTAGED 13:55 WSER85 RESTAGED 22:13 WSER85 13:55 WSER85 *******************************
The following table describes the fields on the Components List panel. Field
REQUEST
Description
Displays the action requested on this component. The actions are: Blank, which means that no action has been requested for this component. SELECTED, which means that the component has been selected for action. DE-SELECTED, which means that the component has been de-selected for action.
STATUS
Displays the status of the component since the last promotion. The statuss are: Blank, which means that no change has occurred RESTAGED, which means that the component was restaged OVERLAID, which means that the component was overlaid by another package
The order of precedence is: OVERLAID, RESTAGED, blank. For implications of this order, see the Notes immediately following this table.
User Guide
10-9
NOTES Only if the component has been restaged or overlaid, can you repromote it back to the same level. For any status value, you can repromote the component to another level. Only promotion rule 0, however, allows the new level to be less than the current level. With all other promotion rules, the new level must be greater than the current level. It indicates the selected remote site, the current package promotion level, and the level you want to promote the component to (level 2, as specified on the previous step). It also displays the components (of the package) that you can selectively promote and the components status since the last promotion. Based on the promotion rule, level input might be disallowed. If you have chosen to selectively promote components and the promotion rule is not 0, the level to promote to (i.e. next component promotion level) is automatically reset based on the current level of the component.
On the Components List panel, type an S next to the components you want to Promote, then type the End command to process. For this scenario, lets select six components from the list. When processing begins, the In Progress panel displays, providing information as to what Change Man is doing.
CMNRPMWT------------IN PROGRESS-----------------------------------------------
Your screen is locked - please wait Date: 07/25/1997 Time: 12:00
=========================================================================== The Remote Promote function is performing the following task: Gathering package components and component information. Checking if there has been any components selected. Checking if all selected components are at the same level. Updating other packages overlaid components. Building prior promotion level cleanup table. Updating package remote promotion history. Updating package component remote promotion history. Constructing remote promotion/demotion JCL. ******************************* BOTTOM OF DATA ********************************
10-10
Demoting Change Packages or Components from a Remote Site
Change Man checks for common components before promoting. If common components are discovered, the Common Components panel displays for confirmation of promotion overlay. (See the section Checking for Common Components at a Remote Site on page 10-15).
DEMOTING CHANGE PACKAGES OR COMPONENTS FROM A REMOTE SITE

Demote a change package or selective components of a package (to level 0) from a remote site. Components that have an incomplete (INCOMP) status, on the Stage panel (CMNSTG01), cannot be demoted. 1 Select Option 3 on the Primary Option menu and press Enter. The Local or Remote Promotion (CMNSLRPM) panel displays.
CMNSLRPM ----------------- LOCAL OR REMOTE PROMOTION -------------------------OPTION ===> 1 2 Local Remote - Local promotion (standard promotion) - Remote promotion (remote site promotion)
On the Local or Remote Promotion panel, type 2 for Remote Promotion and press Enter. The Remote Promote Change Package (CMNRPM00) panel appears. On the Remote Promote Change Package panel, type the change package ID and press Enter. The Remote Promotion Site List (CMNRPM01) panel displays. It lists the available remote sites, the administration-defined force demotion flags, and the prior promotion history of the package at those remote sites. By using such information prior to doing a promotion, you might avoid receiving an error message.
On the Remote Promotion Site List panel, type an S next to the remote site name where you want to demote the package or components. (For this scenario lets select the remote site TEST.) Press Enter. The Promote/Demote A Change Package (CMNRPM02) panel displays.
User Guide
10-11
CMNRPM02 -------------- PROMOTE/DEMOTE A CHANGE PACKAGE ---COMMAND ===> Press ENTER to process; Enter END command to exit. PACKAGE ID: NAVI000005 CREATOR: WSER85 STATUS: DEV
ROW 1 TO 8 OF 8 SCROLL ===> CSR
REMOTE PROMOTION SITE : remprm1 CURRENT PROMOTION LEVEL: STAGING + 0 MAXIMUM PROMOTION LEVEL: TESTINGA + 2 ACTION REQUESTED LEVEL TO CHECK ===> p ===> (P-Promote, D-Demote, C-Check for overlay) (Required for Action C)
REMOTE HISTORY MOD/CNT PROMOTION DATE TIME ID REMOTE Full Promotion 4 2 TESTINGA 1997/06/19 09:44 WSER85 COMPLETED Full Promotion 4 2 TESTINGA 1997/06/19 09:39 WSER85 FAILED Full Promotion 4 2 TESTINGA 1997/06/18 18:33 WSER85 SUBMITTED Full Promotion 7 1 TESTINGA 1997/06/18 14:58 WSER85 COMPLETED Selective Promotion 3 2 TESTINGA 1997/06/18 14:04 WSER85 COMPLETED First Promotion at 0 2 1 TESTINGA 1997/06/18 14:02 WSER85 SUBMITTED Full Demotion 1 2 TESTINGA 1997/06/18 13:58 WSER85 COMPLETED Full Promotion 7 1 TESTINGA 1997/06/18 13:55 WSER85 SUBMITTED
This panel displays the remote site (TEST) and the current package promotion level (2 ). The panel also displays the maximum promotion level ( 2 ) available at TEST for this package and the promotion history for the package at TEST. 5 On the Promote/Demote A Change Package panel, type D in the action requested field and press Enter. The Demote Options panel appears.
10-12
Demoting Change Packages or Components from a Remote Site
CMNRPM04 ----------------------- DEMOTE OPTIONS ----------------------------OPTION ===> f F - Full demotion of the entire package to level 0 (Staging) S - Selective demotion of components to level 0 (Staging) PACKAGE ID: NAVI000005 CREATOR: WSER85 REMOTE PROMOTION SITE : remprm1 CURRENT PROMOTION LEVEL: + MAXIMUM PROMOTION LEVEL: + DEMOTE FROM LEVEL ===> 2 (blank, * or 0 for a list) STATUS: DEV INSTALL DATE: 19971230
On the Demote Options panel, choose either Option F to demote the whole package to level 0, or Option S to selectively demote components of the package to level 0 . Specify the Demote From level. If you are unsure about the demotion levels that are defined for your application, you can display a list of levels by leaving the demote from level field blank or by type a 0 or *. The Remote Promotion Level List panel displays listing the available promotion levels to demote from (at the remote site) and the nicknames assigned to those levels. (Because the demotion from level has yet to be selected, the current promotion level field (on the list panel) retains the value (0) from the previous panel.) From the list panel, you can do either of the following: Advance to the next panel in the sequence, by entering an S next to the nickname for the level you want to demote from. (For this scenario, lets select the nickname TEST101.) Press Enter. (Go to Step 7.) Return to the Demote Options panel and cancel your selection on this panel, by typing the End command + Enter or pressing PF3. By default, a 0 is displayed in the demote from level field.
User Guide
10-13
NOTES If you chose Option F and no components are available for demotion, only the package master is updated. Consequently, the package level will reflect the correct level. 8 Complete the job statement information to submit the demotion job. Press Enter. If you chose option S , the Component List (CMNRPM05) panel appears.
DEMO000045 COMPONENTS ------ROW 1 TO 10 OF 10 SCROLL ===> CSR
CMNRPM05------------PROMOTE: COMMAND ===>
Enter END command to process or CANCEL to exit. PACKAGE ID: NAVI000005 CREATOR: WSER85 STATUS: DEV INSTALL DATE: 19971230
REMOTE PROMOTION SITE : TEST CURRENT PACKAGE PROMOTION LEVEL: STAGING + 0 NEXT COMPONENT PROMOTION LEVEL: TEST101 + 1 NAME TYPE ALIAS-OF PROMOTION DATE _ AUDIT CPY 0 STAGING 1997/07/18 S CMN$$BND CPY 0 STAGING 1997/07/17 _ CMNEX009 LOD 0 STAGING 1997/07/18 S CMNEX009 SRC 0 STAGING 1997/07/17 S CMNEX026 LOD 0 STAGING 1997/07/17 S CMNEX026 CPY 0 STAGING 1997/07/18 _ CMNEX027 LOD 0 STAGING 1997/07/17 S CMNEX027 SRC 0 STAGING 1997/07/18 S CMNEX035 LOD 0 STAGING 1997/07/17 _ CMNEX035 SRC 0 STAGING 1997/07/18 ******************************* BOTTOM OF DATA TIME ID REQUEST STATUS 18:33 WSER85 RESTAGED 22:13 WSER85 13:55 WSER85 OVERLAID 22:13 WSER85 OVERLAID 22:13 WSER85 18:33 WSER85 22:13 WSER85 RESTAGED 13:55 WSER85 RESTAGED 22:13 WSER85 13:55 WSER85 *******************************
The Component List panel (CMNRPM05) indicates the selected remote site, current package promotion level, and the level you want to demote the component to. It also displays the a list of components (of the package) that you can selectively demote, and the components status since the last promotion. For remote demotion, you should interpret the Next Component Promotion level field as the level to Demote from. Consequently, this field inherits the value from the demote from level field on the Demote Options panel. If the value for the next component promotion level field exceeds the promotion level of the component you chose to demote, the next component promotion level is reset to the lower value.
10-14
Checking for Common Components at a Remote Site
The Status field of the Component List panel displays the following status of the component since the last promotion: 9 If the component has been overlaid, only the package master is updated to reflect the correct promotion level (OVERLAID). If the component has been deleted and is demoted to level 0, it will not appear on the component list (DELETED). If the components has been restaged (RESTAGED). Type an S next to the components you want to demote, then enter the END command to process. In this scenario, we will selectively demote three components.
When processing begins, the In Progress panel displays and provides information as to what Change Man is doing.
CHECKING FOR COMMON COMPONENTS AT A REMOTE SITE

Whenever you promote a change package at a remote site, Change Man invokes a common module check routine. This routine detects common modules in your package, the target promotion data set, and the history record (which resides in the package at the promotion level being checked). You also invoke this routine, when you Check for overlay prior to conducting a promotion. Whether you choose to promote or check for overlay, a package list is displayed, listing all the packages that could contain a module common to the one that you are promoting. View the components in common between the change package and the next level of promotion (i.e., check for overlay). 1 Select Option 3 on the Primary Option menu and press Enter. The Local or Remote Promotion (CMNSLRPM) panel displays. On the Local or Remote Promotion panel, type 2 for remote promotion and press Enter. The Remote Promote Change Package (CMNRPM00) panel displays. On the Remote Promote Change Package panel, type the change package ID and press Enter. The Remote Promotion Site List (CMNRPM01) panel displays. It lists the available remote sites, the administration-defined force demotion flags, and the prior promotion history of the packages at those remote sites. By using such information prior to doing a promotion, you might avoid receiving an error message.
User Guide
10-15
On the Remote Promotion Site List panel, type an S next to the remote site name where you want to promote the package or components. (In this scenario, lets select the remote site TEST.) Press Enter. The Promote/Demote A Change Package (CMNRPM02) panel displays, indicating the selected remote site (TEST) and the current package promotion level (0). (The current level is 0 because you have yet to repromote.) The panel also indicates the maximum available promotion level (2) and the promotion history for this package at On the Promote/Demote A Change Package panel, enter a C in the action requested field and press Enter. The Common Components (CMNRPM06) panel displays.
CMNRPM06 --------------------- COMMON COMPONENTS ---------------------------COMMAND ===> f SCROLL ===> CSR Press ENTER to process or enter END to exit. PACKAGE ID: NAVI000005 CREATOR: WSER85 STATUS: DEV INSTALL DATE: 19971230 REMOTE PROMOTION SITE : remprm1 CURRENT PROMOTION LEVEL: STAGING + 0 MAXIMUM PROMOTION LEVEL: TESTINGA + 2 NAME TYPE CMNEX009 SRC CMNEX026 LOD CMNEX026 CPY CMNEX027 SRC CMNEX035 LOD PACKAGE ID DEMO000047 NAVI000074 DEMO000047 *UNKNOWN NAVI000074 STA FRZ DEV FRZ DEV PROMOTION 2 TESTINGA 1 REMPRM1 2 TESTINGA 2 TESTINGA 1 REMPRM1 DATE 1997/07/23 1997/07/23 1997/07/23 1997/05/26 1997/07/21 TIME 13:50 13:44 13:50 14:31 16:57 ID WSER85 WSER85 WSER85 WSER85 STATUS COMMON HISTORY COMMON NOHIST HISTORY
The Common Components panel list the packages that might contain a module common to the one that you are promoting. Specifically, it displays the names and library types of the common modules, the package the component belongs to, the status of that package, the promotion level (and nickname) of the component, the date and time of the promotion, the user ID of the promoter, and the status of the component. If you type a P on the Promote Change Package panel, the Common Components panel displays, with an OVERLAY WARNING message in the upper right hand corner. After viewing the Common Components panel, you can choose to promote by pressing Enter. Alternatively, you can cancel the promotion by typing Cancel or End followed by pressing Enter or PF3.
10-16
RECOMPILING AND RELINKING COMPONENTS
11
RECOMPILE OVERVIEW
Recompiling is primarily used to compile a source component that uses a copybook that has changed. Recompiling from baseline or promotion is similar to staging, meaning you can select from a component list and produce a load component after selecting a compile procedure. The difference is that, when recompiling the source component, only the load component is included. The source component is not copied into the package's staging library during recompile. The reason the source should not be included in the package is that when the package is installed, the components are rippled into baseline and prior versions of the source would be prematurely rolled off (whereas the copy component, having been modified, should be rippled in baseline), Also, recompiling can be used to resolve some of the out-of-sync conditions that can occur from the audit process. The preceding example describes a circumstance in which you need to include the resulting load component with an updated copy component. Problem: Within the application, a programmer checks out a copy, modifies and stages it. Meanwhile, six other source programs within baseline use that copybook (and are not included in the change package). If an audit were to be performed, there would be an out-of-synch condition in the baseline libraries, and any audit level above 3 would restrict you from freezing the package. Solution: Recompile, from baseline, those components that were deemed to be out-ofsynch.
RECOMPILING INTO STAGING LIBRARIES

Take the following steps to recompile from baseline or promotion into staging libraries:
11-1
11 Recompiling and Relinking Components
From the Build Option menu, select option 8. The Recompile Source panel (CMNRCMP0) appears.
CMNRCMP0 ---------------------- RECOMPILE SOURCE ---------------------OPTION ===> L - List libraries where component is found blank - Display member selection list
PACKAGE ID COMPONENT NAME SOURCE LIBRARY TYPE LANGUAGE LIBRARY LEVEL RECOMPILE MODE
===> ===> ===> ===> ===> ===>
RICH000197 (Blank or pattern for list) SRC (Blank for list) COBOL (Blank for list) 0 (Baseline 0, Promotion 1 to nn) 2 (1-Online, 2-Batch)
NOTES If you are recompiling a component and someone else has previously staged it, the user who previously staged the component receives a message informing them that you are recompiling it. The following table describes that valid entries that you can make on the Recompile Source panel (CMNRCMP0).
In this field...
Panel Options
Type...
L(list libraries where components are found) or leave blank to display a member selection list.
Type the package ID of the members to recompile. Type the name of the component to recompile. Leave this field blank or indicate a pattern with an * to display a Component Name list; unless you entered L for the panel options. Type the library type of the component to recompile. Leave this field blank to display a Source Library Type list. Only libraries of type SRC
PACKAGE ID COMPONENT NAME
SOURCE LIBRARY TYPE
(source type) and those libraries designated as Like-Source can be used.

LANGUAGE Type the language name of the component to recompile. Leave this field blank to display a Language Name list.
11-2
Recompiling into Staging Libraries
In this field...
LIBRARY LEVEL
Type...
Type the level of the library to be compiled from. To select from baseline, type 0. To select from promotion, type a level number from 1 to 99, depending on how many levels of promotion have been configured for your application. To select from a list of libraries where a specific component can be found: enter option L , leave this field blank, and type the component name. The Library List panel is displayed. Select the level you wish to perform the recompile.
After entering information on the Recompile Source panel, press Enter. If the component has a history it is displayed before the recompile job is preferred. If you have completed all of the required information, the compile (and link edit) is submitted. All of the components you selected are compiled to the staging load library associated with the package and Online Recompile Job Information panel (CMNRCMP1) similar to the following appears.
CMNRCMP1 ------------- ONLINE RECOMPILE JOB INFORMATION ----------------------COMMAND ===> PACKAGE ID: NAVI000005 COMPONENT: LIBRARY TYPE: LANGUAGE: DATASET NAME: COMPILE PROCEDURE COMPILE PARMS LINK EDIT PARMS DB2 PRE-COMPILE OTHER OPTIONS SUPPRESS HISTORY STATUS: DEV INSTALL DATE: 19971230
ALLIO SRC - Source Code ASM WSER85.TEST.JCL ===> ===> ===> ===> NO ===> ===> NO (Blank for list; ? for designated procedure)
(Y/N) (Y/N to display other options) (Y/N to use above criteria for all selected components in place of any history data) <=== CHANGE ACCORDINGLY_____ <=== CHANGE ACCORDINGLY_____ <=== CHANGE ACCORDINGLY_____ <=== CHANGE ACCORDINGLY_____
JOB STATEMENT INFORMATION: ===> //WSER85C JOB (X170,374),CHANGE MAN, ===> // MSGCLASS=9,NOTIFY=WSER85,TIME=1 ===> /*JOBPARM S=ESA5 ===> // JCLLIB ORDER=(WSER85.CHGMAN.PROCLIB)
User Guide
11-3
PROVIDING RECOMPILE JOB INFORMATION

The Online Recompile Job Information panel (CMNRCMP1) allows you to provide recompile job information in order to complete the recompile. Change package ID, status, install date, dataset name, component name, library type, and language are provided from the previous panel. You can provide the following information to the panel.i
In this field...
COMPILE PROCEDURE
Type...
The compile procedure to recompile the component or leave this field blank to display a Compile Procedures list. If the component has been previously compiled, then the compile procedure that was used will appear. If this component has a designated procedure assigned to it, a ? invokes that procedure and its related parameters. If the designated procedure is in effect under Force Level 2, the procedure and parameters fields show the default values.
COMPILE PARMS
Type additional compile parameters. If you leave this field blank the Compile Procedure Selection list displays. Type additional linkage edit parameters. Indicate whether a DB2 pre-compile is needed. (Y/N ) Indicate whether to display other options. (Y/N ) Enter Yes to suppress component history processing for the component being recompiled, the data on the panel is processed instead. Enter No to perform the opposite, process component history data for the component being recompiled and bypass the values that are specified on the panel.
LINK EDIT PARMS DB2 PRE-COMPILE OTHER OPTIONS SUPPRESS HISTORY
JOB STATEMENT INFORMATION
Complete the job card information for your site.
After entering information on the panel, press Enter to process and submit your recompile batch job.
11-4
Browsing Recompile Source List
BROWSING RECOMPILE SOURCE LIST

If the Component Name field of the Recompile Source panel (CMNRCMP0) is blank or a pattern is entered, a panel similar to the following appears.
CMNRCMP2 FROM - WSER85.STUFF.SRC -------------------COMMAND ===> NAME FUNCTION VV.MM CREATED LAST MODIFIED _ _ _ _ CALLED2 CMNALLIO CMNAPPRV CMNASIST ROW 1 TO 4 OF 4 SCROLL ===> PAGE SIZE INIT ID
02.03 1993/01/21 1996/09/23 13:52 17 16 WSER03 01.00 1994/08/24 1994/08/24 10:20 1151 1151 C410 01.00 1994/10/12 1994/10/12 11:14 4081 4081 C41030 01.00 1994/08/24 1994/08/24 10:20 2958 2958 C410
This panel displays a component list including the standard PDF statistics for each of the baseline or promotion library members which meet the pattern (if any) entered on the Recompile Source panel. Use this panel to select the component names of modules you want to recompile. Use the MASS command to selectively recompile components. When you enter the MASS command, all selected components are recompiled. Use the MASSALL command to recompile all components. When you enter the MASSALL command, all listed components are recompiled. NOTES The MASS and MASSALL commands require the recompile mode to be set to 2 batch on the Recompile Source panel (CMNRCMP0).
RELINKING LOAD COMPONENTS

Using the relink option you can relink load components without associating them with source code. A new load component is produced and copied into the package's Staging library. Language, procedure, link edit, process and user options are obtained from the history record in the package master for the component. Because the options used to relink a component are independent from those used during the compile and link process, relink uses the latest component history from when the component was relinked, not compiled. The latest component history is defined as the first found from the following list.
User Guide
11-5
1 2 3 4 5
Current package. Baselined package with the latest package baselined date/time. Deleted/archived package with the latest component history changed date/time. Package in motion with the latest component history changed date/time. Initial history.
When Relinking you can specify the LCT component in staging or baseline libraries that contains the link control cards. The control cards are dynamically generated if there is no LCT component available. Use an LCT component if you change a subroutine and need to relink the calling program or need to perform a composite link where the resulting load component name does not have accompanying source.
Example
An audit displays a SYNCH8! for a calling LOD and Like-LOD component in baseline, which calls a subroutine being changed in a package. There is no reason to recompile the program because the source has not changed, yet it needs to be relinked to include the current subroutine. The relink function lets you relink the module from baseline without recompiling and remove the synch 8 when you re-run the audit. To relink load components, take the following steps: 1 From the Build Options menu, select option 9 and press Enter. The Relink Load Module panel (CMNRLNK0) displays.
CMNRLNK0 -------------------- RELINK LOAD MODULES ----------------------------OPTION ===> PACKAGE ID RELINK FROM LCT MEMBER LIST INPUT LIBRARY TYPE TARGET LIBRARY TYPE MEMBER NAME ===> NAVI000005 ===> S (S-Staging or B-Baseline) ===> NO (Y - Yes or N - No; member list will be created with input library type) ===> LD1 (Blank for list) ===> LD1 (Blank for list) ===> ALLIO (Blank or pattern for list)
11-6
Relinking Load Components
The following table describes the information that you can enter on the panel. Field
RELINK FROM
Description
The source location of the LCT component or like-LOD component to be relinked.
S (Staging) B (Baseline)
LCT MEMBER LIST INPUT LIBRARY TYPE TARGET LIBRARY TYPE MEMBER NAME
Y to use an LCT member.
The like-LOD library type of the module to be relinked from.
The like-LOD library type of the module to be created.
The name of the like-LOD or LCT member to be relinked. Specify a name pattern or blank to select from a list.
After you complete entering information on the panel, press Enter to process the relink.
NOTES If you are relinking a component and someone is updating the same component, the user updating the component receives a message informing them that you are relinking it.
User Guide
11-7
STAGE USER OPTIONS PANEL

If you typed Yes in the Other Option field of the Recompile Job Information and Relink Load Modules panels, the following panel displays.
CMNUSR01 -------------------- STAGE: USER OPTIONS ----------------------------COMMAND ===> NAME: ALLIO COMPILE ONLY CICS PRE-COMPILE EASYTRIEVE NO NAME USER OPTION 07 USER OPTION 09 USER OPTION 11 USER OPTION 13 USER OPTION 15 USER OPTION 17 USER OPTION 19 TYPE: SRC ===> ===> ===> y ===> n ===> n ===> ===> ===> ===> ===> LANGUAGE: ASM ENTRY DROP USER USER USER USER USER USER USER USER TO DLITCBL ===> INCLUDE STMTS ===> OPTION 06 ===> y OPTION 08 ===> y OPTION 10 ===> n OPTION 12 ===> OPTION 14 ===> OPTION 16 ===> OPTION 18 ===> OPTION 20 ===>
Use Y or N to select or deselect additional processing options; Press ENTER to continue; Enter END command to exit.
11-8
APPROVING OR REJECTING A PACKAGE
12
Frozen change packages can be approved or rejected by the individuals responsible for reviewing and approving change packages. These people are determined by the Change Man administrator during application level generation. (Refer to CMNEX028 for a list of approvers who also work with packages.) During the build process, a change package is created, scheduled, and built to contain the instructions and components that make up a change package. When the building of the change package is complete, the package is frozen the package cannot be modified indicating it is ready to be reviewed and approved. The approval process will not be allowed to begin until the asynchronous JCL build process has been completed successfully (see the chapter on Package Freeze). After a change package has been frozen, it may be promoted and the individuals who are responsible for approving the change package can approve or reject the change package online. (Promotion is optional.) If there are remote sites, an approved change package proceeds to distribution. Otherwise, it proceeds to installation. If a package has been promoted, it may still continue being approved. Care must be taken, however, because when the last person required to approve the package signs on and selects to approve it, the package will immediately be distributed (and/or installed, depending on how the global/application parameters were set up), regardless of the promotion level reached. A rejected change package has to be reverted to development. It can then be modified or deleted. If modified and refrozen, the change package must then go through all subsequent steps as if it had never been processed before. If a package is rejected by an approver, and it has been promoted prior to the rejection, it must be demoted before it can be reverted back to development status for modification. A promoted package may be selectively demoted, such that only the offending component need be affected. Then, of course, the component must be repromoted and the entire package reapproved. If a change package has made it past the build process but requires corrections, and if it has not been rejected, selective components can be unfrozen. The unfrozen components can be modified and refrozen, and the approval process can then proceed.
12-1
12 Approving or Rejecting a Package
Each application will configure two lists of approvers. The Complete Approval List will be the most commonly used for all planned change packages and all unplanned packages created during normal business hours. If you create an unplanned permanent or unplanned temporary change package outside of normal business hours, Change Man will attach the entities associated with this application's Abbreviated Approval List. Unplanned packages (emergencies) must be reapproved by the complete approval list after installation. (The package will remain on the list of packages to be approved, and on the Change Man batch report, Packages Needing Post Approval CMN120.) Certain approvers configured in the application's Complete Approval List will be designated as interfacing approvers. This means that any other application that creates a change package which affects your application must be also approved by your application's interfacing approver. Change Man's approval facility lets authorized users approve or reject packages before they are installed into production. Change Man can capture an electronic signature of the approval or rejection of a package.
APPROVING OR REJECTING PACKAGES

In order to approve or reject packages, you must access the Approve Package Parameters panel (CMNAPPRV). To access this panel, take the following steps:
12-2
Approving or Rejecting Packages
From the Primary Option Menu, select Option 4. The Approve Package Parameters panel (CMNAPPRV) appears.
CMNAPPRV ----------------- APPROVE PACKAGE PARAMETERS ------------------------COMMAND ===> SPECIFY SELECTION CRITERIA: PACKAGE ID ===> NAVI000011 APPROVAL ENTITY NAME ===> NOTIFIED USER ID ===> WORK REQUEST ID ===> DEPARTMENT ===> REMOTE SITE AFFECTED ===> PACKAGE LEVEL ===> PACKAGE TYPE PACKAGE TIME SPAN FROM INSTALL DATE TO INSTALL DATE FROM CREATION DATE TO CREATION DATE OTHER PARAMETERS ===> ===> ===> ===> ===> ===> ===>
(Full name or pattern; blank for list) (Approvals for this security entity) (Packages for which user was notified)
(1-Simple, 2-Complex, 3-Super, 4-Participating) (Planned or Unplanned) (Permanent or Temporary) (YYYYMMDD) (YYYYMMDD) (YYYYMMDD) (YYYYMMDD) (Y/N)
The following table describes the information that you enter in the fields of the Approve Package Parameters panel. In this field...
PACKAGE ID
Type.
The package ID or a pattern to display the list of packages pending approval. If a change package ID was entered, only that change package is displayed for approval or rejection. The Approve/Reject Options panel displays. If a change package ID was not entered, the Approval List displays
APPROVAL ENTITY NAME NOTIFIED USER ID
A security entity name to mask your search and list only those packages pending approval for that entity. The user ID to mask the search criteria and display only those packages, for the specified ID, for which notification has been sent. The work request ID.
WORK REQUEST ID DEPARTMENT
The department.
User Guide
12-3
In this field...
REMOTE SITE AFFECTED PACKAGE LEVEL
Type.
The remote site to display only the packages with approval pending that are to be installed at that site.
1 (Simple) - To view simple change packages only. (Change packages that contain changes not affecting other packages or applications). 2 (Complex) - To view complex change packages only. (The parent of two or more participating change packages that have interdependent changes to software or operational procedures within the same application.) 3 (Super) - To view super packages only. (The parent of two or more participating change packages that have interdependent changes to software or operational procedures within the same application.) 4 (Participating) - To view participating packages only. (A change package that relates to one or more other participating packages, and is a component package of a complex or super package.) Planned - To view packages with scheduled changes that are required to follow all established application rules. Unplanned - To view packages with unscheduled changes. (i.e., possibly an emergency fix) Permanent - To view packages with scheduled changes that update baseline/production libraries. Permanent changes are either planned or unplanned. Temporary - To view packages with changes that run for a predetermined length of time. Once that time has expired, Change Man automatically deletes the change. Temporary changes do not update baseline/production libraries. These changes are Installed into a static override library. Temporary changes are either planned or unplanned.
PACKAGE TYPE
PACKAGE TIME SPAN
FROM/TO INSTALL DATE FROM/TO CREATION DATE OTHER PARAMETERS
Type the installation start and end date (yyyymmdd format) to view packages within this time span. Type the creation start and end date (yyyymmdd format) to view packages within this time span. Indicate whether to further limit the display of packages based on the types of components contained in the packages.
12-4
Approving or Rejecting a Package
After entering the appropriate information on the Approve Package Parameters panel (CMNAPPRV), press Enter. The Approve/Reject Options panel (CMNAPPOP) appears.
CMNAPPOP ------------------- APPROVE/REJECT OPTIONS -------------------------OPTION ===> PACKAGE ID: NAVI000011 1 Approve 2 Reasons 3 Query 4 Reset 5 Resubmit Press ENTER to STATUS: DEV INSTALL DATE: 19990728
- Approve or reject a change package - Display reasons a package was rejected - Query change package - Reset approval in progress indicator - Resubmit the JCL build process process; Enter END command to exit.
APPROVING OR REJECTING A PACKAGE

To approve or reject a package from the Approve/Reject Options panel (CMNAPPOP), select option 1 (Approve) and press Enter. The Approval List panel (CMNAPPLS) appears.
CMNAPPLS ----------------------- APPROVAL LIST --------------- Row 1 to 3 of 3 COMMAND ===> SCROLL ===> PAGE Press ENTER to process; enter END command to exit. PACKAGE ID: NAVI000018 APPROVER DESCRIPTION _ Mgmt. 000 _ Tech. 000 _ QA 000 ******************************* Bottom of data ******************************** STATUS: FRZ INSTALL DATE: 19990722 ID DATE
TIME SEQ STATUS
Approving a Package
In the appropriate line command (approver description list), type A to approve the package and press Enter.
User Guide
12-5
Rejecting a Package
In the appropriate line command (approver description list), type R to reject the package and press Enter. The Reject Reasons panel (CMNREJR1) appears.
CMNREJR1 ----------------------- REJECT REASONS -----------------------------COMMAND ===> PACKAGE ID: NAVI000018 APPROVER: Tech. TSO ID: ===> ===> ===> ===> ===> Press ENTER to process; Enter END command to exit. STATUS: FRZ INSTALL DATE: 19990722
On the Reject Reasons panel (CMNREJR1), type your reason for rejecting the package and press Enter to save you entry.
RESUBMITTING THE BATCH APPROVE AND BATCH BUILD X NODE DATA SET JCL
If CMNEX028 is enabled with: OPT$SPFA set to Y (delay building of X node data set until after final approval) OPT$BAPR set to Y (submit batch job for final approval) To failure in the final approval batch job caused by jobcard or skeleton error can cause problems in working with the package. To resolve the above problem, first fix any problem with the skeletons. To resolve the jobcard issue, resubmit the JCL following the procedure described below: 1 2 3 Reset the approval in progress indicator to access the package. Access the Approve panel for the package. Press ENTER to display the jobcard panel (do not enter A for approve)
12-6
Using the Component User ID Work Record
Correct any jobcard errors and submit the JCL to build the X node data set.
You can always resubmit the JCL for any problems that arise after the package is approved.
USING THE COMPONENT USER ID WORK RECORD

If your administrator has turned on Component User ID Work Record function with Exit CMNEX028, Change Man records all checkout, stage, edit in stage, recompile, relink, and delete actions performed against a package component, for any user ID performing those actions. Change Man records the component name, component type, user ID, last action taken, and last date and time of the action, and then increments the action count by 1. Although only the last action performed against each component name and type appears in the record for each user ID, the number of times that a user ID acted on that component name and type is recorded. Both batch and online actions are recorded.
USING THE COMPONENT USER ID WORK RECORD DURING APPROVAL

The Component User ID Work Record function can be used during the approval process. If the approvers user ID matches any of the user IDs in the Component User ID Work Records, that approver is not allowed to approve the package. Any Component User ID Work Record that is flagged as deleted is bypassed during this process.
VIEWING THE COMPONENT USER ID WORK LIST

You can view the Component User ID Work Record online through Stage Package Driven, Checkout Package Driven, and Query Package. NOTES This function is implemented by the Change Man administrator with the extended administration options exit, CMNEX028. In both Stage Package Driven and Checkout Package Driven, line command UL (User ID List) lets you view all user IDs that have acted on the component.
User Guide
12-7
Although there are two ways to view the information in Query Package, both displays have Sort and Locate commands for all fields: One view displays a complete list of actioned components within a package. When you select the category Component User ID Work List from Package Information Categories, all component user ID work records display, including those flagged as deleted. See , on pag e-8. The complete view displays a table containing the component name, type and status, user ID, last date and time, last action, and number of times that user ID acted on the component. The other view displays information for selected components. To obtain this view, select Non-Source or Source from Package Information Categories and type the UL line command next to the desired component (the same as from a package driven list).
The UL line command displays the component name and type, along with a table of user IDs that acted on the component. The table contains the user ID, last date and time, last action taken, and number of times that the user ID acted on the component.
CMNUCWK1-------------------COMPONENT USERID WORK LIST--------ROW 1 TO 7 OF 7 COMMAND ===> SCROLL ===> CSR Press END command to exit. PACKAGE ID: NAVI000005 STATUS: DEV USER ID WSER48 WSER42 WSER99 WSER48 WSER99 WSER42 WSER99 INSTALL DATE: 19971230 LAST DATE 19970801 19970801 19970823 19970801 19970823 19970801 19970625 LAST TIME 131126 123914 161827 131129 161443 123955 141842 ACTION REQUEST STAGED EDITSTAGED STAGED STAGED STAGED DELETED CHECKOUT ACTIONED COUNT 0001 0001 0002 0001 0001 0001 0011
COMPONENT NAME TYPE $$$BRWBL CPY $$$BRWBL CPY $$$BRWBL CPY $$$PRINT CPY $$$PRINT CPY ABC CPY ABC CPY
STATUS
DELETED DELETED
12-8
Distribution and Installation of the Change Package
CMNUCWK0--------------------USERID WORK LIST-------------ROW 1 TO 5 OF 5 COMMAND ===> SCROLL ===> CSR Press END command to exit. PACKAGE ID: NAVI000005 STATUS: DEV INSTALL DATE: 19971230
COMPONENT NAME: ALLIO COMPONENT TYPE: CPY USER ID WSER48 WSER42 WSER98 WSER97 WSER99 LAST DATE 19970701 19970701 19970726 19970726 19970726 LAST TIME 131134 123946 180142 175147 174747 ACTION REQUEST STAGED STAGED CHECKOUT CHECKOUT CHECKOUT ACTIONED COUNT 0003 0001 0006 0001 0002
**********************************BOTTOM OF DATA***************************
'
Deleting the Component User ID Work Record

When a component is deleted, the Component User ID Work Record is flagged as deleted, but is not deleted. If that component is once again introduced into the package, the delete flag for the Component User ID Work Record is removed, and the prior record is reinstated. Once a user ID is added to the Component User ID Work Record, it cannot be removed.
DISTRIBUTION AND INSTALLATION OF THE CHANGE PACKAGE

After the change package has been approved, it is either installed, or, first distributed and then installed. The specific distribution and installation process depends on the following: The type of scheduler set up by the global administrator Whether or not the Install job has been modified The site type (ALL, DP, etc.)
Distribution to Remote Sites

If the site is D or D, and therefore has remote sites (P), the following occurs:
User Guide
12-9
Specific staging libraries, the installation JCL, and a copy of the package master record pertaining to this change are distributed (copied) to all the remote sites specified in the package control information (it is specified in the creation/update package process). A record of this event (package distribution) is placed in the activity log. A distribution acknowledgment is sent back to the development center. Package status is changed from APR to DIS. The change packages are installed at those sites.
If the site is ALL (no remote sites exist), the change package is ready to install. See the following discussion. If the site is DP or D, the install job CMN20 job runs at the corresponding remote sites), according to the scheduler. Once the change packages are installed to the remote sites, the CMN30 job runs at the DP or D site. If the site is ALL, Change Man executes install jobs CMN20, CMN30, CMN50, and CMN55 directly. The status of the change package changes from APR to BAS.
12-10
REVERTING A PACKAGE
13
Although a package has been rejected, frozen, or backed out, you can return it to development (DEV) status. You are required to complete a text field describing the reasons for reverting the change package. These revert reasons, like reject backout reasons, will be carried along with the package information and are made available for review using the Change Man query function. To revert a package, you must have access to the application and the revert entity. If a package has been frozen and you want to update an individual component, you can selectively unfreeze and refreeze that component instead of executing a revert. A revert takes the entire change package out of the frozen status. Essentially anyone can revert until the package is approved by the first approver. In more detail, however, the rules for reverting packages are: When your package is in an All (no remote production sites) or revelopment (changes not allowed to be installed production libraries) site; the following is true: If the package is rejected, it may be reverted by a user with revert authority. If the package is frozen but the approval process has not started, it may be reverted by any of the application's users. If the package is frozen and the approval process has begun, the package must be rejected (with completed reject reasons) before it can be reverted. If the package has been approved (but not yet installed), the person with authority to revert may do so. If the package has been backed out (by a user with backout authority), it may be reverted by a user with revert authority.
When the package is in the production (remote site) site: If the package is in DIS (distributed) status, it can be reverted by a user with revert authority.
13-1
13 Reverting a Package
If the package has been installed, it must be backed out (with completed backout reasons) by a user with backout authority before it can be reverted by a user with revert authority.
When backing out a change package after it has been distributed to a remote site and installed into production, you must initiate the package backout from the remote site and also revert it at the remote site. Additionally, after a change package has been reverted, the approval process must start over again.
REVERTING A CHANGE PACKAGE.

1 From the Primary Option Menu, select option R. The Revert Change Package appears.
CMNREV00 ------------------- REVERT CHANGE PACKAGE ------------------------COMMAND ===> PACKAGE ID ===> NAVI000005 Press ENTER to process; Enter END command to exit.
Type the change package ID of the package you wish to revert and press Enter. The Revert Reasons panel (CMNREVRS) appears.
REVERT REASONS ------------------------------
CMNREVRS ------------------COMMAND ===> PACKAGE ID: NAVI000005 ===> This package had errors. ===> ===> ===> ===> ===> ===> ===> ===>
STATUS: FRZ
13-2
Reverting a change package.
Type your reason (freeform) for reverting the change package. Each line has a maximum length of 72 characters. You must type at least 1 character for the revert to succeed. When complete, Change Man returns you to the Revert Change Package panel displaying the Package Reverted message.
CMN 5.1 Upgrade Manual
13-3
13 Reverting a Package
13-4
BACKING A PACKAGE OUT OF PRODUCTION
14
After you have installed packages into your production library, you can retrieve the previous version of the application software from the backup library. You can retrieve (backout) a package only if you have backout authority). When you backout a package, Change Man replaces your production library with the contents in your backup library and changes the package status from INS (installed) to BAK (backed out). Once you have backed out all of your production libraries, Change Man backs out its baseline library (also referred to as reverse baseline ripple) and changes the package status from BAS (baseline) to BAK (backed out). Before modifying the package, you must revert it from BAK to DEV (development). There are some restrictions to backing a package from production: If the staging libraries for a package have been deleted or aged, the backout jobs will have vanished. The backout and reverse ripple jobs are built at the same time as the install jobs and stored in other staging library (.X or .X.Remote file). When your package is installed, a backup is generated. If another package has overriden the backup copy of one of the components, you will not be allowed to backout your package. Change Man does not support partial backout. All components are backed out.
ACCESSING THE BACKOUT CHANGE PACKAGE OPTION PANEL

To back out a planned permanent or unplanned permanent change package which has been installed in production, you use the Backout Change Package Option panel. To access the Backout Change Package Option panel, take the following steps:
14-1
14 Backing a Package Out of Production
From the Primary Option Menu, select Option B and press Enter. The Backout Change Package panel (CMNBKOUT) appears.
CMNBKOUT ------------------- BACKOUT CHANGE PACKAGE -----------------------COMMAND ===> PACKAGE ID ===> NAVI000005 Press ENTER to process; Enter END command to exit.
In the Package ID field, type the change package ID and press Enter. The Backout Reasons panel (CMNBKRSN) displays.
CMNBKRSN ---------------------- BACKOUT REASONS ----------------------------COMMAND ===> PACKAGE ID: NAVI000005 CREATOR: WSER85 BACKOUT REASONS: ===> This package was incomplete. ===> ===> ===> ===> ===> ===> ===> ===> Press ENTER to process; Enter END or CANCEL command to exit. STATUS: BAS INSTALL DATE: 19971230
This panel is used to record the reason for the package backout. This information is stored in the package master and may be queried at any time using the query functions. 3 Provide a brief description explaining the reason(s) for this backout action and press Enter to save your description. Press PF3 or type End+Enter, to close the panel and invoke the following events: A job is sent to the development environment to initiate the reverse ripple of baseline but only after all remote sites have backed out the package. The components in production are overlaid with the backup library copies made prior to the package installation.
14-2
Backing Out a Package from a Remote Site
If the jobs run successfully, the following occurs: The status of the change package is changed to backout (BAK). A record is created in production environment with a time and date stamp and it is sent to the package master.
BACKING OUT A PACKAGE FROM A REMOTE SITE

When backing out a change package after it has been distributed to a remote site and installed into production, you must also initiate the package backout from the remote site. However, if you plan on restaging the package components and want to salvage the package itself, then you must revert it at all sites where it was distributed. You can have more than one remote site. When backing out or reverting remote site packages, make sure you backout and/or revert from each remote site.
User Guide
14-3
14 Backing a Package Out of Production
14-4
USING PACKAGE LIST FOR CHANGE MAN FUNCTIONS
15
Package List (option 5 on the Build Option men) provides you with an alternative method to perform the Change Man functions presented in the previous chapters.
ACCESSING THE PACKAGE LIST PARAMETERS PANEL

You access the Package List Parameters panel (CMNLIST0) to enter the appropriate information for filtering the Package List Parameters panel. This panel lets you display a list of packages. Specify filter criteria in the Package List Parameters panel. 1 Select Option 5 on the Primary Option menu. The following panel displays.
CMNLIST0 ------------------ PACKAGE LIST PARAMETERS --------------------------COMMAND ===> SPECIFY SELECTION CRITERIA: PACKAGE ID ===> NAVI000005 PACKAGE STATUS CREATORS TSO-ID WORK REQUEST ID DEPARTMENT PACKAGE LEVEL PACKAGE TYPE PACKAGE TIME SPAN FROM INSTALL DATE TO INSTALL DATE FROM CREATION DATE TO CREATION DATE OTHER PARAMETERS ===> APR ===> ===> ===> ===> WSER85 416NAVIG DP 4
(Full name or pattern; blank for list, or * for all packages) (DEV, FRZ, APR, REJ, DIS, INS, BAS, BAK, OPN, CLO, TCC or DEL)
===> P ===> P ===> ===> ===> ===> ===> Y
15-1
15 Using Package List for Change Man Functions
The following describes the fields of the Package List Parameters. Field
PACKAGE ID
Description
Type the package ID or a pattern to display the list of packages pending Approval.
DEV (development)
PACKAGE STATUS
A change package is in the process of being developed.

FRZ
(frozen) A change package has been build, and awaiting approval.
APR (approve) A change package has been approved, and awaiting distribution (if applicable). REJ (reject)
A change package has been rejected

DIS
(distribution) The package has been distributed to the remote sites where it is to be installed. (install) The package has been installed in the remote sites specified in the change package.
INS
BAS (baseline) - indicates that the package has had its modules rippled through the application's baseline libraries. BAK (backed out) - indicates that all components of the package have been removed from production. OPN (open)
A complex or super change package has been created as an umbrella or reporting tool for inter-related changes. These complex or super packages will remain open until the user updates the status to close it.
CLO (close) A complex or super package will no longer be reported upon, and can not have any participating change packages added under its umbrella. TCC (temporary
change cycle) A change package had been installed and now has been deleted from the temporary production data set.
DEL (delete) The change package has been memo deleted.
CREATORS TSOID WORK REQUEST ID DEPARTMENT
Type the User ID to mask the search criteria and display only those packages, for the specified id. Type the work request ID.
Type the department.
15-2
Accessing the Package List Parameters Panel
Field
REMOTE SITE AFFECTED PACKAGE LEVEL
Description
Type the remote site to display only the packages with approval pending that are to be installed at that site. Simple View a change package that contains a change that is unrelated to any other change package. Complex/Super View a complex or super package that is the parent of two or more participating change packages. After you have created all participating change packages, someone is designated to create the complex or super package. It contains a list of the participating packages with the general and control information. It does not contain any of the components to be Installed. Participating View change packages that are related to one or more other packages. All of these packages are considered to be participating with each other.
PACKAGE TYPE
Planned View packages with scheduled changes that are required to follow all established application rules. Unplanned View packages with unscheduled changes. (i.e., possibly an emergency fix)
PACKAGE TIME SPAN
Permanent View packages with scheduled changes that update baseline/production libraries. Permanent changes are either planned or unplanned. Temporary View packages with changes that run for a predetermined length of time. Once that time has expired, Change Man automatically deletes the change if a scheduler is used. Otherwise, if you use a manual scheduling method, the job will be submitted on hold, and will need to be released when the duration of days is met. Temporary changes do not update baseline/ production libraries. These changes are installed into a static override library. Temporary changes are either planned or unplanned.
Type the installation start and end date (yyyymmdd format) to view packages within this time span. Type the creation start and end date (yyyymmdd format) to view packages within this time span. Indicate whether to further limit the display of packages based on the types of components contained in the packages.
Fill in information in each of the filter criteria fields. This information is used to limit the range of information which is to be displayed in the Change Package List. You can fill in any combination of these fields to limit your search.
User Guide
15-3
To limit the range of packages displayed by specific application(s), leave the package name field blank (or specify a pattern). The Application List displays. Select any or all of the listed applications. All of these fields except the package name field are optional. If you leave any of them blank all information related to the field is displayed. 3 Type YES in the other parameters field to further limit the display of change packages by the kinds of components the change package contains. Press Enter. Change Man creates and displays the Change Package List using your filter criteria, if you specified NO in the other parameters field. If you typed YES for Step 3, then the Extended Search Criteria panel appears before the Change Package List.
CMNQRY01 ------------------ EXTENDED SEARCH CRITERIA ----------------------COMMAND ===> NON-SOURCE SOURCE AND LOAD RENAME/SCRATCH INFO CUSTOM COMPONENT ===> y ===> ===> y ===> (Y/N) (Y/N) (Y/N) (Y/N)
5 6
Complete the Extended Search Criteria. Type YES next to each row of the types of change package components to limit the display of change packages by the kinds of components the change package contains. If you do not want to limit the display of change packages by components contained, type NO (or blank) next to any of the component types. Press Enter. The Change Package List appears.
BROWSING THE CHANGE PACKAGE LIST

When Change Man is done processing your filter criteria, it displays the Change Package List. (For further information about filtering, or masking, displays see Inserting a Line on page -9.)
15-4
Acting on Packages
CMNLIST3 -------------------- CHANGE PACKAGE LIST ---------- ROW 1 TO 4 OF 4 COMMAND ===> SCROLL ===> CSR PACKAGE ID STA INSTALL LVL TYPE DEPT PROMOTION AUD CREATOR __ NAVI000005 BAS 19971230 PART PLN/PRM DP 00 STAGING WSER85 __ NAVI000007 DEV 19971230 SMPL PLN/PRM DP 4 WSER85 __ NAVI000009 CLO 19970901 CMPX PLN/PRM DP WSER85 __ NAVI000011 DEV 19971031 PART PLN/PRM DP 00 STAGING WSER85 ******************************* Bottom of data *******************************
When this view is first shown it is a shortened list which does not display all of the change package information. You can review and act on the shortened list, or you can access the rest of the package details before you act on the package. Access and browse the complete details of the Change Package List (the long list). Choose from the following commands: To include titles in the Package List, type LONG. The Change Package List is displayed. To list all the valid line commands, type OPTIONS . The Package List Options panel is displayed. To list all valid primary commands, type COMMANDS. The Valid Package List Commands is displayed.
ACTING ON PACKAGES
You can use a variety of functions on the listed packages. Change Man provides you with online lists of command line options as well as line commands you can use on the packages. 1 Type OPTIONS at the command line to access a list of command line options. This displays the Package List Options panel that contains the following options: Option
U1 U2 U3
Description
Update control information Update general information Update implementation information
User Guide
15-5
Option
U4 U5 U6 U7 U8 U9 UI OF UA UB UE C1 C2 S1 S2 S3 AP RC RL BB BL CC ZP F1
Description
Update scheduling information Update affected application information Update participating package information Update site (remote) information (new description) Change complex/super package to CLO status Change complex/super package to OPN status Update package IMS system information (replaced UR) Work with online forms Rename and scratch components (from package) Rename and scratch components (baseline) Change Package User Records Checkout components (baseline/promotion) Checkout components (from package) Stage components (from development) Stage components (from package) Stage components (component driven parameters) Audit package Recompile source from baseline/promotion Relink load modules Browse/Print baseline/promotion Browse compressed listing Compare staging against baseline/promotion Compress package staging libraries Freeze a package online
15-6
Acting on Packages
Option
F2 F3 F4 PD PR A1 A2 A4 D1 D2 RV QP B1 SC
Description
Submit batch job to freeze package Selectively freeze/unfreeze components Reset freeze in progress indicator Promote/demote a package Remotely-promote/demote a package Approve/reject a package Display package rejection reasons Reset approval in progress indicator Memo delete a package Undelete a mMemo deleted package Revert a package Query package information Backout a package Scan baseline for character strings
NOTES The PR option is not available (i.e., is not a valid option) if allow remote promotion is set to No during application administration. 2 Type COMMANDS to get a list of all the valid line commands. The following panel displays.
User Guide
15-7
CMNLIST6 ---------------- VALID PACKAGE LIST COMMANDS ----------------------COMMAND ===> SCROLL ===> CSR COMMAND DESCRIPTION ----------------------------------------------------------------------------DATES Display installation calendar OPTIONS Display valid package list options REFRESH Refresh current list - enter after performing a function SORT Sort PACKAGE, STA, INSTALL, LVL, TYPE, WORK, DEPT, PROMO, AUD or CREATOR SHORT Display list in short mode CANCEL Cancel processing and exit from list CREATE Create a new package LOCATE Locate on sorted fields LONG Display list in long mode COMMANDS Display valid commands panel ----------------------------------------------------------------------------Enter END command to exit.
15-8
DEFINING AND GENERATING CHANGE MAN REPORTS
16
Your global administrator or local application administrator specifies which reports are user-designated. That is, the administrator designates which reports that you can generate. This chapter describes the various Change Man reports and how to generate the Change Man batch reports.
CHANGE MAN REPORTS

The following table lists the batch reports that accompany Change Man. NOTES The Change Man global administrator can define these reports as global, application, or user-specific. Local application administrators can change the application reports to user reports and user reports to application reports. Users can only run user-designated reports. Report
CMN010 CMN040 CMN050 CMN060 CMN090 CMN100 CMN110 CMN120
Description
Number of Planned and Unplanned Changes INFO/SYS File and Combined Package Report Installed Change Package History Installed Simple Change Package History Super/Complex Report Application Configuration Report Work Request Number Report Package That Need Post Approval
16-1
16 Defining and Generating Change Man Reports
Report
CMN130 CMN140 CMN150 CMN160 CMN170 CMN180 CMN190 CMN200 CMN210 CMN240 CMN250 CMN260 CMN500 CMN890 CMN900 CMN910 CMN920
Description
Backout Report Rejected Package Report Number of Unplanned Changes by Reason Code Trend Analysis for Planned Changes Trend Analysis for Unplanned Changes by Reason Code Component History Report Trend Analysis for Unplanned Changes Copies, Source/Load Component Report Rename, Scratch Component Report Activity Summary by Application Mnemonic Activity Summary by Department Number Implementation Schedule Package Information Report Skeleton Release ID Report Designated Procedures Report Package in the CMN Scheduler Change Packages and Staging Datasets Targeted for Deletion
Note: This report only marks packages and staging datasets for cleanup.
To delete them, you must run the housekeeping function for reports. CMN930 Implementation Calendar Discrepancy Report
Note: This report only marks the calendar for resynch. To run the resynch,
you must run the housekeeping function for reports. CMN940 CMN950 CMN960 CMN970 Components without Component Level Security Delinquent Package Report Component Level Security Information Packages Pending Approval
16-2
Change Man Programs for Generating Reports
Report
CMN980 CMN990
Description
Implementation Calendar Report Global Administration Configuration Report
CHANGE MAN PROGRAMS FOR GENERATING REPORTS

CMNSAS10 and CMNBAT10 are programs that you can use and modify in order to generate Change Man reports. CMNSAS10 requires that the SAS system to be installed at your site. SAS is the recommended method for generating Change Man reports. If your site does not have SAS, the reports are available in assembler format and you will use CMNBAT10 to generate the Change Man reports.
Generating SAS Reports

We recommend that you use a SAS program to generate Change man reports. CMNSAS10 of somnode.CHGMAN.SAS is a SAS program. CMNSAS10 generates reports from VSAM files package master, VSAM component file, and QSAM backup. Of course, you can generate Change Reports within your Change Man session or outside the Change Man session. REPORTS of somnode.CHGMAN.CNTL and CMN$$RPT of somnode.CHGMAN.SKELS are the modules that use CMNSAS10 in order to generate Change Man reports. You will use and modify REPORTS to generate reports when you are not in a Change Man session, and CMN$$RPT to generate reports when you are in a Change Man session.
REPORTS module
REPORTS of somnode.CHGMAN.CNTL contains the job information that you can modify and use in order to generate reports for Change Man applications. The following is a sample REPORTS.
//jobname JOB (account),CHGMAN/REPORTS, <=== Change Accordingly // CLASS=?,NOTIFY=?, <=== Change Accordingly // MSGCLASS=? <=== Change Accordingly //SAS10 EXEC SAS, *** GENERATE CHANGE MAN SAS REPORTS // REGION=4M, // OPTIONS=MACRO,DQUOTE,YEARCUTOFF=1960, // TIME=10,SORT=20,WORK=20,20 //CMNPMAST DD DISP=SHR,DSN=somnode.CHGMAN.CMNPMAST //CMNCMPNT DD DISP=SHR,DSN=somnode.CHGMAN.CMNCMPNT
User Guide
16-3
//SOURCE DD DISP=SHR,DSN=somnode.CHGMAN.SAS //SYSIN DD DISP=SHR,DSN=somnode.CHGMAN.SAS(CMNSAS10) //DYNACODE DD DISP=(,PASS),DSN=&&DYNACODE, // UNIT=SYSDA,SPACE=(TRK,(5,5)), // DCB=(RECFM=FB,LRECL=80,BLKSIZE=6000) //TRANFILE DD DISP=(,PASS),DSN=&&TRANFILE, // UNIT=SYSDA,SPACE=(TRK,(5,5)), // DCB=(RECFM=FB,LRECL=80,BLKSIZE=6000) //SYNCFILE DD DISP=(,PASS),DSN=&&SYNCFILE, // UNIT=SYSDA,SPACE=(TRK,(5,5)), // DCB=(RECFM=FB,LRECL=80,BLKSIZE=6000) //INFOSYS DD DISP=(,PASS),DSN=&&INFOSYS, // UNIT=SYSDA,SPACE=(TRK,(15,30),RLSE), // DCB=(RECFM=FBA,LRECL=133,BLKSIZE=3990) //CMNSASIN DD * BKUP=N PKGN= FDTE=,TDTE= ****010=Y,****040=Y,****050=Y,****060=Y,****090=Y,****100=Y,****110=Y, ****120=Y,****130=Y,****140=Y,****150=Y,****160=Y,****170=Y,****180=Y, ****190=Y,****200=Y,****210=Y,****240=Y,****250=Y,****260=Y,****500=Y, ****890=Y,****900=Y,****910=Y,****920=Y,****930=Y,****940=Y,****950=Y, ****960=Y,****970=Y,****980=Y,****990=Y //ABNLIGNR DD DUMMY //SYSUDUMP DD SYSOUT=* //BATCH EXEC PGM=CMNBATCH, *** PROCESS REPORT 920/930 TRANSACTIONS // REGION=4M, // PARM=SUBSYS=x <=== Update subsystem ID //SYSPRINT DD SYSOUT=* //CMNDELAY DD DISP=SHR,DSN=somnode.CHGMAN.CMNDELAY //SYSIN DD DISP=(OLD,DELETE),DSN=&&TRANFILE // DD DISP=(OLD,DELETE),DSN=&&SYNCFILE //SYSUDUMP DD SYSOUT=* //ABNLIGNR DD DUMMY
In the above job information, replace somnode.CHGMAN with the names that you use at your site: somnode.CHGMAN.CMNPMAST somnode.CHGMAN.CMNCMPNT somnode.CHGMAN.SAS, which contains the SAS macros somnode.CHGMAN.SAS(CMNSAS10), which points to the main program somnode.CHGMAN.CMNDELAY
16-4
Change Man Programs for Generating Reports
NOTES The CMNPMAST is for the VSAM package master and QSAM backup. The CMNCMPNT is for the VSAM component file and DD DUMMY is for QSAM backup. Also, the BKUP parameter allows you to select whether you wish to use the VSAM package master (Y) or QSAM backup (N).
CMN$$RPT module
CMN$$RPT of somnode.CHGMAN.SKELS contains the job information that you can modify and use in order to generate reports for Change Man application while you are within your Change Man session. The following is a sample of CMN$$RPT.
)IM CMN$$JCD //*)IM CMN$$RPT )CM )CM ROUTINE TO GENERATE CHANGE MAN SAS REPORTS )CM )CM REPLACE ALL somnode LIBRARIES WITH VALID NAMES. )CM REFER TO somnode.CHGMAN.CNTL(REPORTS) FOR MORE INFORMATION. )CM //SAS10 EXEC SAS, *** GENERATE CHANGE MAN SAS REPORTS // REGION=4M, // OPTIONS=MACRO,DQUOTE,YEARCUTOFF=1960, // TIME=10,SORT=20,WORK=20,20 //CMNPMAST DD DISP=SHR,DSN=&PMSTDSN //CMNCMPNT DD DISP=SHR,DSN=&CPNTDSN //SOURCE DD DISP=SHR,DSN=somnode.CHGMAN.SAS //SYSIN DD DISP=SHR,DSN=somnode.CHGMAN.SAS(CMNSAS10) //DYNACODE DD DISP=(,PASS),DSN=&&DYNACODE, // UNIT=SYSDA,SPACE=(TRK,(5,5)), // DCB=(RECFM=FB,LRECL=80,BLKSIZE=6000) //TRANFILE DD DUMMY //SYNCFILE DD DUMMY //ABNLIGNR DD DUMMY //SYSUDUMP DD SYSOUT=* //CMNSASIN DD * BKUP=N PKGN=&RPKGNUM FDTE=&FRMDATE,TDTE=&TODATE )DOT RPTSYITB &RPTSYIN )ENDDOT RPTSYITB
In the above job information, replace with your valid name. you will modify somnode of the following: somnode.CHGMAN.SAS contains the SAS macros somnode.CHGMAN.SAS(CMNSAS10) points to the main program
User Guide
16-5
Generating non-SAS Reports (CMNBAT10)

CMNBAT10 in somnode.CHGMAN.ASSEMBLE allows you to generate Change Man report, if your site does not have an installed SAS system. CMNBAT10 generates reports from QSAM backup of the VSAM package master. NOTES While CMNSAS10 allows you to generate all reports, CMNBAT10 will not generate report 40, 190, 500, 890, 900, 910, 940, 960, 970, 980, and 990. You can generate the reports within your Change Man session or outside the Change Man session. REPORTS2 of somnode.CHGMAN.CNTL and CMN$$RPT of somnode.CHGMAN.SKELS are the modules that use CMNBAT10 in order for you to generate Change Man reports. You will use and modify REPORTS2 module to generate reports when you are not in a Change Man session, and CMN$$RPT to generate reports when you are in a Change Man session.
REPORTS2 module
REPORTS2 of somnode.CHGMAN.CNTL contains the job information that you can modify and use in order to generate reports for Change Man applications. The following is a sample of REPORTS2.
//jobname JOB (account),CHGMAN/REPORTS2, <=== Change Accordingly // CLASS=?,NOTIFY=?, <=== Change Accordingly // MSGCLASS=? <=== Change Accordingly //BAT10 EXEC PGM=CMNBAT10, *** GENERATE CHANGE MAN REPORTS // REGION=4M //CMNQSAM DD DISP=SHR,DSN=somnode.CHGMAN.CMNPMAST.BACKUP //CMNRPORT DD SYSOUT=* //AGETRANS DD DISP=(,PASS),DSN=&&AGETX, // UNIT=SYSDA,SPACE=(TRK,(1,2)), // DCB=(RECFM=FB,LRECL=80,BLKSIZE=6000) //INFOSYS DD DISP=(,PASS),DSN=&&INFOSYS, // UNIT=SYSDA,SPACE=(TRK,(15,30),RLSE), // DCB=(RECFM=FB,LRECL=1000,BLKSIZE=20000) //SORTSTAT DD SYSOUT=* //SYSOUT DD SYSOUT=* //SORTWK01 DD UNIT=SYSDA,SPACE=(CYL,10) //SORTWK02 DD UNIT=SYSDA,SPACE=(CYL,10) //SORTWK03 DD UNIT=SYSDA,SPACE=(CYL,10) //SORTWK04 DD UNIT=SYSDA,SPACE=(CYL,10) //SYSIN DD * ****010=Y,****050=Y,****060=Y,****090=Y,****100=Y,****110=Y,****120=Y ****130=Y,****140=Y,****150=Y,****160=Y,****170=Y,****180=Y,****200=Y ****210=Y,****240=Y,****250=Y,****260=Y,****920=Y,****930=Y,****950=Y //SYSUDUMP DD SYSOUT=* //ABNLIGNR DD DUMMY //BATCH EXEC PGM=CMNBATCH, *** PROCESS REPORT 920/930 TRANSACTIONS // REGION=4M,
16-6
Generating Change Man Reports
// PARM=SUBSYS=x <=== Update subsystem ID ///CMNDELAY DD DISP=SHR,DSN=somnode.CHGMAN.CMNDELAY //SYSIN DD DISP=(OLD,DELETE),DSN=&&AGETX //SYSUDUMP DD SYSOUT=* //ABNLIGNR DD DUMMY
In the above job information, replace somnode.CHGMAN with your valid name. somnode.CHGMAN.CMNPMAST.BACKUP
GENERATING CHANGE MAN REPORTS

During your Change Man session, you can navigate through a series of panels and obtain the Define or Generate Change Man Batch Reports panel (CMNREPT5), which allow you to define and generate batch reports.
Generating Change Man Batch Reports Panel

To access the Generate Change Man Batch Reports panel, take the following steps: 1 From the Change Man Primary Option Menu (CMN@PRIM), type 6 to display the Generate Change Man Batch Reports panel (CMNREPT5).
CMNREPT5 ------------- GENERATE CHANGE MAN BATCH REPORTS ---------------------COMMAND ===> APPLICATION ===> (Full name, pattern or blank for list)
JOB STATEMENT INFORMATION: ===> //WSER83V JOB (X170,374),CHANGE MAN, <=== CHANGE ACCORDINGLY______ ===> // MSGCLASS=9,NOTIFY=WSER83,TIME=1 <=== CHANGE ACCORDINGLY______ ===> /*JOBPARM S=ESA5 <=== CHANGE ACCORDINGLY______ ===> //PROCLIB JCLLIB ORDER=(WSER99.CMN510Q.QACUST.SKELS)____________________
In the APPLICATION field, do one of the following to generate reports: Type the application mnemonic (three to four characters), Type a pattern for an application range (maximum of four characters, use * for mask or pattern), or Type **** to generate reports for all applications.
User Guide
16-7
If you leave this field blank and press enter the Application Selection List panel (CMNRPT9) appears on the screen. The panel displays a list of applications. From this list you can selection the application containing your desired package. 3 Review the job card statement information and make the necessary changes. Once you have verified the information, press ENTER. The Report Selection List panel (CMNREPT6) appears on the screen.
CMNREPT6 ------------------- REPORT SELECTION LIST --------- Row 1 to 12 of 29 Enter END command to process or CANCEL to exit. Package Number Release ID Report Date Range From To ID 010 050 060 090 100 110 ===> ===> ===> ===> (optional, (optional, (YYYYMMDD, (YYYYMMDD, report 500) report 890, blank or mask) optional) optional)
_ _ _ _ _ _
Report Description Summary of Planned and Unplanned Packages Installed Package History Report Installed Simple Package History Report Super/Complex Packages Report Application Configuration Report Work Request Number Report
You can print out SAS or assembler reports. The panel is set to print out SAS reports. However, if you do not have SAS, or want to print out Assembler reports, you can change the default setting for the output file in the CMN$$RPT skeleton to report type ASM and print some of the same reports in functionally stabilized Assembler. 4 On the Report Selection List panel (CMNREPT6), type the range for the dates of the reports in the REPORT DATE RANGE field using the YYYYMMDD format. In the line command, select the reports that you wish to generate and press ENTER. A message appears indicating that the job has been submitted. After several minutes, you will be able to access your Change Man report through your output utility.
16-8
Accessing Submitted Change Man Reports
ACCESSING SUBMITTED CHANGE MAN REPORTS

In order to view your submitted Change Man report, you access your sites output utility. For example, a site might use the Spool Display and Search Facility (SDSF) as its output utility.
HQX1900-----------------COMMAND INPUT ===> LOG DA I O H ST PR INIT MAS LINE NODE SO Display Display Display Display Display Display Display Display Display Display Display Display SDSF PRIMARY OPTION MENU -------------------------SCROLL ===> CSR
the system log active users in the sysplex jobs in the JES2 input queue jobs in the JES2 output queue jobs in the JES2 held output queue status of jobs in the JES2 queues JES2 printers on this system JES2 initiators on this system JES2 members in the MAS JES2 lines on this system JES2 nodes on this system JES2 spool offload for this system
Licensed Materials - Property of IBM 5647-A01 (C) Copyright IBM Corp. 1981, 1997. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
User Guide
16-9
16-10
UTILITY REQUESTS
17
COMPRESS STAGING LIBRARIES

When you create a change package, the associated staging libraries are empty. As the package goes through its life cycle, you populate the libraries with updated components. As testing proceeds with the package, you often restage many of the components, eventually causing the staging libraries to become full. You can use the compress function to compress the partitioned datasets (staging libraries) associated with change packages. Because partitioned datasets do not reuse space when you make deletions and updates, you can compress the staging libraries to reclaim the dead space.
ACCESSING THE COMPRESS STAGING LIBRARIES PANEL

1 To access the Compress Staging Libraries panel, from the Build Options menu, select option Z. The Compress Staging Libraries panel (CMNCPRSS) displays.
CMNCPRSS ----------------- COMPRESS STAGING LIBRARIES ----------------------COMMAND ===> PACKAGE ID ===> navi000005 JOB STATEMENT INFORMATION: ===> //WSER85A JOB ,ACCOUNT INFORMATION______________________________________ ===> //*_____________________________________________________________________ ===> //*_____________________________________________________________________ ===> //*_____________________________________________________________________ Press ENTER to process; Enter END command to exit.
In the Package ID field, type the ID of the package that you wish to compress for the staging libraries.
17-1
17 Utility Requests
Type the job card information. Change Man overlays the job name specified with the
job name it submits for the batch job.
RENAMING OR DELETING COMPONENTS

The utility request facility is designed to rename or delete components in production or baseline libraries. These requests can be the only items in a change package or can be part of a change package with staged components. These utility requests are processed by Change Man during package production installation and baseline ripple. Change Man processes these requests after installing and rippling staged component versions. You use the utility: Rename/Scratch Options panel to access these capabilities.
ACCESSING THE RENAME OR SCRATCH OPTIONS PANEL

Use this panel to choose whether component selection lists are derived from the contents of your baseline library or from the contents of your change package. From the Build Options menu, select option 4 (Utility) from the Build Options menu. The Utility Remane or Scratch Options panel (CMNUTL00) appears.
CMNUTL00 -------------- UTILITY: RENAME/SCRATCH OPTIONS ----------------------OPTION ===> 1 PACKAGE ID ===> NAVI000005 1 2 Baseline Package - Select baseline components to scratch or rename - Process scratch or rename requests in package
With Option 1, you can attach new scratch/rename requests to a package based upon the contents of a baseline library. Change Man presents a list of components derived from the baseline library associated with the requested library type and optional member name pattern. With Option 2, you can review and update an existing list of scratch/rename requests associated with a change package. Requests in this list can be generated in one of two ways. They were completed from the baseline request option above. The status of these requests is active. They can be reviewed or deleted.
17-2
Creating Utility Requests from Baseline
They were carried forward from another package if this package was created with the copy forward option. The status of these requests is inactive. These requests must be changed to active or deleted from this list before this package can be frozen.
Once the components have been selected for renaming or scratching, Change Man keeps track of the information. (It can be modified as long the package is in DEV status.) When the package is frozen, Change Man creates a job to run the requests, but that job is not run until the change package is actually installed.
CREATING UTILITY REQUESTS FROM BASELINE

Complete the following steps to create utility requests from baseline. 1 Select Option 1 on the Utility Rename or Scratch panel (CMNUTL00). The Utility Baseline Selections panel (CMNUTL01) displays.
CMNUTL01 ---------------- UTILITY: BASELINE SELECTIONS -----------------------OPTION ===> r R - Rename a component S - Scratch a component blank - Display component selection list LIBRARY TYPE ===> COMPONENT ===> iebcopy NEW NAME ===> copy1 (Blank for list) (Blank or pattern for list) (Required for option R)
* The following options are available from a component selection list: L - Locate component R - Rename component S - Scratch component B - Browse component H - Component History I - Short History Press ENTER to process; Enter END command to exit.
User Guide
17-3
17 Utility Requests
Column
Panel Options
Description R - Set up a rename request for a component in your baseline or production library. S - Set up a scratch (delete) request for a component in your baseline or
production library.
Blank - Bring up the Utility Baseline Component List panel. From

the panel you can locate, browse, rename, access a long/short history, or scratch it. LIBRARY TYPE COMPONENT Indicate the library type of the component you are renaming or scratching. Type the name of the component you are renaming or scratching. You can enter a pattern to access the Utility: Baseline Component List from which you can set up scratch and rename requests for more than one component. From this list you can use the standard special list commands, or type R or S in the first column of the component rows. If the request is a rename, you type the new name in the RENAME column of the row. NEW NAME If you are renaming a component, type the new name for the component.
When you are done, Change Man processes your input and inserts the request into your change package. Change Man returns you to the Utility: Rename/Scratch Options panel.
If baseline is kept by site for this application, then the remote site affected by the change package displays in the panel header.
ACTIVATING OR DELETING UTILITY REQUESTS FROM PACKAGES

Access and complete the Utility: Change Package Driven List to activate or delete utility requests from a package list. 1 Select option 2 from the Utility Rename or Scratch Options panel. A panel (CMNUTL03) similar to the following appears.
17-4
Deleting and Undeleting Packages
CMNUTL03 ------------------- UTILITY: NAVI000005 LIST ------- ROW 1 TO 1 OF 1 COMMAND ===> SCROLL ===> PAGE REQ NAME RENAME TYPE CHANGED ID STATUS FUNCTION s SCR ALLIO CPY 1997/09/03 12:40 WSER85 ACTIVE ******************************* Bottom of data ******************************
Aside from the special list commands, in the line command of the desired row, type A (to activate an inactive request) or D (to delete a request). Press Enter to reflect the change in the package.
DELETING AND UNDELETING PACKAGES

The delete function is used to delete packages from a Change Man environment. Information about the package is deleted from the package master control file and all related staging libraries are deleted.
Deletion Considerations
A package can only be deleted with this facility if it is in development (DEV) status. Global and application administrators can delete installed packages using the aging facility. See the Administrator Guide for further information. A request to delete a package from these panels is queued for later processing. When your system's housekeeping tasks are run (ordinarily nightly), the package is actually deleted. Before the housekeeping tasks are run, the deletion can be rescinded with undelete. Simple, participating, super, and complex packages can be memo deleted and undeleted with this facility. The following considerations apply when you delete super or complex packages: Be sure that super and complex packages have participating packages that are only in DEL (Delete) or DEV status. When deleting a super or complex package, remove all associations in both the participating packages and the super or complex package.
SETTING UP A MEMO DELETE

To delete a change package.
User Guide
17-5
17 Utility Requests
Select Option D on the Primary Option menu. The following panel displays.
CMNDELT0 ----------------------- DELETE OPTIONS ---------------------------OPTION ===> 1 1 2 Delete - Memo delete a change package Undelete - Restore memo deleted change packages
2 3
Select Option 1 on the Delete Options panel. The following panel displays.
CMNDELT1 ----------------- MEMO DELETE CHANGE PACKAGE ---------------------COMMAND ===> PACKAGE ID CONFIRM REQUEST ===> NAVI000005 ===> YES
(Y/N)
4 5
Type the change package ID. Type YES in the confirm request field if you want to confirm the request to delete before Change Man sets up the delete memo. Press Enter. Confirm the request if you requested confirmation. Otherwise the delete memo is set up without requesting a confirmation.
CANCELING A DELETED CHANGE PACKAGE REQUEST

You can cancel a memo deleted change package (the process is termed undeleting a change package) only prior to completing the housekeeping tasks. To Undelete a change package, do the following.
17-6
Canceling a Deleted Change Package Request
Select Option 2 on the Delete Options panel. The following panel displays.
CMNDELT3 --------------- RESTORE MEMO DELETED PACKAGES --------------------COMMAND ===> PACKAGE ID ===> NAVI000005 (Blank for list)
Type the change package ID. To select from a list of memo deleted change package requests, leave this field blank and press Enter. Change Man displays the Memo Deleted Package List after gathering the information from the package master.
User Guide
17-7
17 Utility Requests
17-8
COMPARING STAGING LIBRARIES
18
The compare function is used to produce a difference report describing the modifications to components within a change package using the application's baseline or promotion libraries as a reference. For example, if a change package was created in March and installation was delayed for six months, the user may want to review the changes made before resuming the installation process. Compares can be run in either online or batch mode.
COMPARING STAGING LIBRARIES TO BASELINE OR PROMOTION

You can compare components of a change package's staging libraries to the application's baseline or promotion libraries. Access and provide filter criteria in the Compare panel. Select option C on the Build Options menu. The following panel displays.
18-1
18 Comparing Staging Libraries
CMNCOMP1 -------------------------- COMPARE --------------------------------COMMAND ===> C - Compare of one component blank - Display member selection list COMPARE MODE PACKAGE NAME COMPONENT NAME LIBRARY TYPE SOURCE LIBRARY ===> ===> ===> ===> ===> O NAVI000005 ALLIO SRC 0000 (O-Online; B-Batch) (* for all members; blank for list) (Blank for list) (Baseline 0 to -n; Promotion +1 to +n) (Y/N)
PROMPT FOR REPORT DISPOSITION ===> YES
JOB STATEMENT INFORMATION FOR BATCH COMPARE: ===> //WSER85C JOB (X170,374),CHANGE MAN, ===> // MSGCLASS=9,NOTIFY=WSER85,TIME=1 ===> /*JOBPARM S=ESA5 ===> // JCLLIB ORDER=(WSER85.CHGMAN.PROCLIB)
The following table describes the fields of the Compare panel.
Field
Panel Options
Description
C
Compare one component.
blank
Display member selection list. COMPARE MODE
O
Compare online.
B
Compare in batch. PACKAGE NAME Type the package name from which the staging libraries are compared to the baseline and promotion libraries.
18-2
Printing, Deleting or Keeping Comparison Information
Field
COMPONENT NAME
Description
Type the component name to compare. Type an * for all members, leave this field blank to select from a list. To compare all components from a specific library, type the library type in the library type field, type * in source library and press Enter. All components are compared to the staging libraries associated to the change package number in the package name field. Type the library type of the component to compare. Leave this field blank to select from a list. Indicate the level of the baseline or promotion library from which to compare components. Baseline 0 is the most current version of production. To select from baseline, enter a level number from 0 to -9, depending on how many levels have been configured for your application. If baseline is kept by site for this application, the Remote Site Selection List is displayed before selection of the baseline level back. Promotion +1 is the first level of promotion. To select from promotion, enter a level number from (+1) to (+99), depending on how many levels of promotion have been configured for your application. The promotion Library Selection List is displayed to select the individual library within the specified level.
LIBRARY TYPE
SOURCE LIBRARY
PROMPT FOR REPORT DISPOSITION
Indicate how Change Man is to handle disposition of the report output:
K - Keep D - Delete PD - Print and Delete PK - Print and Keep
JOB STATEMENT INFORMATION FOR BATCH COMPARE
Complete the job statement information for the batch job Change Man submits to compare components.
PRINTING, DELETING OR KEEPING COMPARISON INFORMATION

You can delete, keep, and print the information after you have browsed it, as specified in panel CMNCDISP. You do this through the Specify Report Disposition panel.
User Guide
18-3
18 Comparing Staging Libraries
Delete, keep and/or print the difference report. Type YES in the prompt for report disposition field of the Compare panel. The following panel displays.
CMNCDISP ----------------- SPECIFY REPORT DISPOSITION ------------------------COMMAND ===> REPORT DATASET NAME: REPORT DISPOSITION WSER85.WSER85.CMN97246.T1336570.OUTLIST D K PD PK Delete - Keep - Print and Delete - Print and Keep
===> D
JOB STATEMENT INFORMATION IF DISPOSITION IS PD OR PK: ===> //WSER85C JOB (X170,374),CHANGE MAN, <=== CHANGE ACCORDINGLY_____ ===> // MSGCLASS=9,NOTIFY=WSER85,TIME=1 <=== CHANGE ACCORDINGLY_____ ===> /*JOBPARM S=ESA5 <=== CHANGE ACCORDINGLY_____ ===> // JCLLIB ORDER=(WSER85.CHGMAN.PROCLIB) <=== CHANGE ACCORDINGLY_____ Press ENTER to process; Enter END command to exit.
The following table describes the fields of the Specify Report Disposition panel.
Field
REPORT DATASET NAME REPORT DISPOSITION
Description
Type the temporary data set name that contains the difference information.
Indicate how Change Man is to handle the disposition of the comparison report after browsing.
D - Delete K - Keep PD - Print and delete PK - Print and keep

JOB STATEMENT INFORMATION IF DISPOSITION IS PD OR PK Complete job card information to process the request.
18-4
BROWSING AND PRINTING PACKAGE INFORMATION
19
Change Man enables you to browse the contents of the activity log, compressed listings of SYSOUT stored online, and attendant basic reporting functionality.
USING THE ACTIVITY LOG

Change Man has a log which records all of the Change Man activities at your site. Nearly all user activities are logged, as well as some behind the scene activities that Change Man performs. You can also browse the activity log for audit return codes on all packages.
PROVIDING BROWSE ACTIVITY LOG FILTERING INFORMATION

Since the activity log can contain a great deal of information, you need to use the Browse Activity Log panel to provide activity log parameters which are used to filter the activity log to display only the information you want to view.
19-1
19 Browsing and Printing Package Information
Select option L on the Primary Option menu. The following panel displays.
CMNLOGEX -------------------- BROWSE ACTIVITY LOG -------------------------COMMAND ===> SCROLL ===> PAGE ONLINE BROWSE ===> YES FROM DATE ===> TO DATE ===> (YES-online; NO-batch) (YYYYMMDD, optional) (YYYYMMDD, optional)
IND LOG DESCRIPTION ********************************* TOP OF DATA ****************************** _ 01 Backout a Package _ 02 Install a Package _ 03 Temporary Change Cycle _ 04 Distribute a Package _ 05 Unauthorized Member Access _ 08 Delete a Package _ 09 Generate Application Information _ 10 Revert a Package _ 11 Generate Global Information _ 12 Activate a Component _ 13 Package Memo Delete _ 14 Undelete a Package _ 15 Baseline Ripple
When using the from/to date fields, you should be aware of how often the log is cleared by the system administrator. If the log containing specific dates was cleared, the backed up log can be viewed to obtain this information. In this case, the log inquiry will must be executed in batch mode. When this panel is displayed, you see all the log selection criteria descriptions available.
Field
ONLINE BROWSE
Description
Indicate whether you want to view the log online ( YES) or submit a batch job (NO ) to create a log report. If you choose NO , Change Man asks you to provide the batch job information. Type the beginning and ending date (yyyymmdd format) to display specific period information.
FROM/TO DATE
To make a selection from the list, type S next to any of the list of selection criteria you desire and press Enter.
19-2
Reviewing the Activity Log
REVIEWING THE ACTIVITY LOG

The following panel is an example of the activity log after you provide the log filtering criteria in the section above.
CMNLOGDS -------------------- ACTIVITY LOG ENTRIES ---------------------------COMMAND ===> SCROLL ===> PAGE BROWSE NEXT PAGE OF LOG ENTRIES ===> YES (Y/N) DATE TIME JOB/ID PACKAGE ID DESCRIPTION ********************************* TOP OF DATA ********************************* 19990723 144335 WSER1323 RICH000265 Activate CMNCOBS1.SRC 19990723 144339 WSER1323 RICH000265 Activate CMNCOBS1.LOD 19990723 155707 WSER46Z DAM2000764 Activate CALLER01.SRC 19990723 155708 WSER46Z DAM2000764 Activate CALLER01.LOD 19990723 160215 WSER22RE SAF 000055 Activate FREMONT.SRC PAGE 0001
When this panel is displayed, you see all the log entries that fit the selection criteria you indicated in the Browse Activity Log panel. If there are many entries displayed on your screen, use any of the following methods to review the information: Type YES in the browse next page of log entries field and press Enter. Change Man displays the next page of log entries. Type P and any page number on the command line and press Enter. Change Man displays that page number. (Example: P4 displays page four of the log entries that match the selection criteria.).
You can type SELECT ALL at the command line to view the entire log (with no selection criteria) Bottom of Data shown after repeated page down commands is not an accurate indicator of the lists end. Use the next page command until the End Of Log message is displayed in the upper right hand corner.
PRODUCE A LOG ACTIVITY REPORT

The following panel displays if you type NO in the online browse field on the Browse Activity Log panel (described in the previous section). It lets you provide batch job information for filtering the activity log using a background job.
User Guide
19-3
You may need to get the name of the log backup copy data set from the Change Man administrator.
CMNLOGE2 -------------------- BROWSE ACTIVITY LOG --------------------------COMMAND ===> BACKUP LOG DATASET NAME: ===> backup.dataset.log JOB STATEMENT INFORMATION: ===> //WSER85C JOB (X170,374),CHANGE MAN, ===> // MSGCLASS=9,NOTIFY=WSER85,TIME=1 ===> /*JOBPARM S=ESA5 ===> // JCLLIB ORDER=(WSER85.CHGMAN.PROCLIB)
<=== <=== <=== <===
ACCORDINGLY_______ ACCORDINGLY_______ ACCORDINGLY_______ ACCORDINGLY_______
In addition to providing the JCL job card statement information, type the QSAM log file name from which the Log Activity Report will be run in the backup log dataset name field. This should be the most current backup copy of the Log. The Log Activity Report (CMN020 an example of which is shown below) is produced in background mode and afterward you are returned to the Browse Activity Log panel.
19-4
Produce a Log Activity Report
1
REPORT ID: CMN020 LOG ACTIVITY REPORT 1997-04-15 through 1997-04-16
2
AS OF 1997-04-15 20:00 PAGE 1
3
PACKAGE ACTIVITY DATE TIME USER-ID NAME DESCRIPTION
______________________________ __________ __________ ________ __________ ____________________________________________
4
BUILD CHECKOUT CHECKOUT STAGE ACTIVATION FREEZE APPROVE REJECT INSTALL BASELINE RIPPLED BACKOUT BASELINE REVERSE RIPPLED REVERT PACKAGE MEMO DELETED DELETE DELETE AGED INSTALLED PACKAGES DELETE AGED STAGING LIBRARIES DELETE COPY FORWARD CALENDAR RESYNCHRONIZATION
7
10:14 12:15 12:17 12:21 12:22 13:14 13:46 14:44 15:36 15:37 15:38 15:38 15:41 15:48 07:44 07:44 07:44 07:44 08:15 08:44 09:38 10:07
8
C911400 C911404 C911404 C911404
9
CGM 000067 Build a package - Create CGM 000012 Checkout CPY - CPY$LOG Checkout CPY - CPY$LOG CGM 000012 Stage SRC - CMN$ACPM
1997-04-15 1997-04-15 1997-04-15 1997-04-15 1997-04-15 1997-04-15 1997-04-15 1997-04-15 1997-04-15 1997-04-15 1997-04-15 1997-04-15 1997-04-15 1997-04-15 1997-04-16 1997-04-16 1997-04-16 1997-04-16 1997-04-16 1997-04-16 1997-04-16 1997-04-16
C911404C CGM 000012 Activate SRC - CMN$ACPM C911401 C911404 C911404 CGM 000071 Freeze a package CGM 000031 Approve a package CGM 000030 Rejected a package
CGM20050 CGM 000050 Install a package CGM30050 CGM 000050 Baseline rippled CGM55050 CGM 000050 Backout a package CGM55050 CGM 000050 Baseline reverse rippled C911404 C911404 CGM 000003 Revert a package CGM 000035 Package has been memo deleted.
C911404R CGM 000035 Package has been deleted C911404R CGM 000035 Staging libraries have been deleted C911404R DEMO000020 Package has been aged C911404R DEMO000020 Package has been deleted C911404R DEMO000020 Staging libraries have been aged C911404R DEMO000020 Staging libraries have been deleted C911403 CGM 000090 Copy forward a package
C911404R CGM 000012 Calendar decremented
The following table describes the fields of the Log Activity Report.
Number
1 2
Description
Change Man report number, in this case, CMN020 . Date in YYYYMMDD format and time in HHMM format. This is the actual date and time the report was produced.
User Guide
19-5
Number
3 4 5 6 7 8
Description
FROM and TO dates as specified in the SYSIN card. The activity that generated a log entry. The date in YYYYMMDD format when the log entry was made. The time in HHMM format when the entry was made. The TSO ID of the user who initiated the activity. Change package mnemonic and number. This unique number identifies this change package from any other package within Change Man. Change package activity description.
USING THE BASELINE BROWSE/PRINT FACILITY

The baseline browse/print facility lets you view the contents of the previous or current version of a baseline or promotion library component without having to checkout that component or enter a valid change package ID for it. You initiate all browsing and printing activities from the Baseline Browse/Print Facility panel. Access the Baseline Browse/Print Facility panel. 1 Type option B from the Build Options menu. This displays the Baseline Browse/ Print Facility panel.
19-6
Using the Baseline Browse/Print Facility
CMNBRWB0 --------------- BASELINE BROWSE/PRINT FACILITY --------------------OPTION ===> H L - List libraries where component is located B - Browse C - Copy E - Browse in edit mode P - Print H - History S - View Stack of SRD APPLICATION LIBRARY TYPE LIBRARY LEVEL COMPONENT NAME MEMBER LIST SCAN RECORDS TO SELECT CASE SENSITIVE FROM COLUMN TO COLUMN DATA STRING ===> ===> ===> ===> NAVI JCL 0 IEBCOPY
X - Print expanded
(Blank for list) (Blank for list) (Baseline 0 to -n; Promotion +1 to +n) (Blank or pattern for list) (Y/N to build member list from scan results) (0 = all) (Y/N) (0 = all) (Max = 80)
===> ===> 0 ===> N ===> ===> ===>
2 3
Identify the component for which you want to run browse/print options. Fill in the component description fields.
User Guide
19-7
Field
Panel Options
Description
L List all baseline or promotion libraries that contain a component you specify. B Browse the full contents of any version of any baseline or promotion library component. C Copy component contents to other files or data set members, including CA-Panvalet and CA-Librarian. E Use any of the ISPF edit commands. X Print baseline or promotion library components with expanded copybooks. P Print baseline or promotion library components. H Display information about previous component activity, including all packages where a component previously resided. S View the stack of individual changes for each previous version of a component, including associated package and user ID information of stacked reverse deltas.
APPLICATION
The name of the application that contains the component. Leaving this field blank will display an application name selection list. The library type associated with the component to be processed. This entry determines which baseline library to process against. The component's version to be processed (0 to -n for baseline; +1 to +n for promotion). For baseline components, A 0 level indicates the most current baseline version which is stored in a fully expanded form. The number of valid -N versions is determined by the application administrator. Type a fully qualified member name against which an option will be processed or apply a masked entry to display a member selection list that matches the masking criteria. Leave this field blank for an entire list of components within the baseline library.
LIBRARY TYPE
LIBRARY LEVEL
COMPONENT NAME
MEMBER LIST SCAN
Type Y to indicate that a member (component) list will be generated based on a scan for a character string. Type N to bypass scan processing altogether.
19-8
Browsing Baseline and Promotion Library Components
Field
RECORDS TO SELECT
Description
Indicates whether to limit the scan to a specific number of matching entries. The scan will terminate when the records selected is equal to the number of matches. Determines whether the scan is to exclude a string based on upper or lower case letters. Type Y if an exact match is required based on the data string entered. Type N if an exact match is not required. Type the start and end columns to initiate and terminate the scan for a record. Specify the data string which is to be searched.
CASE SENSITIVE
FROM/TO COLUMN DATA STRING
BROWSING BASELINE AND PROMOTION LIBRARY COMPONENTS

Browse baseline is the only function that displays only those applications you are authorized to access. For those applications, you can do the following: Browse the contents of baseline and promotion library components View all previous changes to baseline components Browse the history of activity for any component List libraries that contain a component
To display a list of all the promotion and baseline libraries, including library levels, that contain the component, use option L (list) on the (CMNBRBWO) panel. The figure below shows a list of all the libraries that contain a component named $$$PRINT.CPY.
CMNBRWB6 ---------------- IEBCOPY.JCL LIBRARY LIST ---------- ROW 1 TO 2 OF 2 COMMAND ===> SCROLL ===> PAGE LVL DATASET NAME PROMOTION NAME _ 0000 WSER85.TEST.JCL_____________________________ BASELINE _ -001 WSER85.STUFF.JCL____________________________ BASDELTA ******************************* Bottom of data ******************************
User Guide
19-9
For all component types, except LOD, you can enter any of the Browse/Print Facility options as line commands. You can also issue SORT and LOCATE commands from the command line. To browse the full contents of baseline and promotion library components, use option B from panel CMNBRWB0. Copybooks are NOT expanded in browse mode. You can view them in expanded mode by printing the component using the option print expanded. You can also view all previous changes to baseline components with the Baseline Browse facility. When you do this you see: The stack of changes for up to 999 prior versions components stored in Stacked Reverse Delta (SRD) libraries. Characteristics for each version such as date, time stamp, as well as associated package and user ID.
The figure below shows the stack of changes, and version characteristics for component SRCDBRM, on panel CMNBROWS.
CMNBROWS WSER85.WSER85.CMN97230.T1504035.CPXLOAD --- LINE 00000000 COL 001 080 COMMAND ===> SCROLL ===> PAGE ********************************* Top of Data ******************************** //WSER85CX JOB (X170,374),I.PROGRAMMER,REGION=6M, // CLASS=A,TIME=(,30), // MSGCLASS=9, // NOTIFY=WSER85 //* //COMPARE EXEC PGM=COMPAREX //STEPLIB DD DISP=SHR,DSN=WSER99.COMPAREX.LINKLIB //SYSPRINT DD SYSOUT=* //SYSUT1 DD DSN=WSER85.PDS.CMNADMIN(CMNALLIO), // DISP=SHR //SYSUT2 DD DSN=WSER85.APF.LINKLIB(CMNALLIO), // DISP=SHR //SYSIN DD * MAXDIFF=5 CONTINUE /* ******************************** Bottom of Data ******************************
To browse the history of activity for a component, use option H (History) from CMNBRWB0. This displays information about previous component activity, including all packages where a component previously resided.
19-10
Editing Components in Browse Mode
The next figure shows the history of activity for a component SRCDBRM.SRC on panel CMNCMPHI.
CMNCMPHI --------------------- IEBCOPY.JCL HISTORY ---------- ROW 1 TO 2 OF 2 COMMAND ===> SCROLL ===> PAGE Press ENTER to continue. PACKAGE ID STA PROMOTION VV.MM LAST ACTION SIZE PROCNAME ID NAVI000005 DEV 02.02 1997/08/18 15:58 24 WSER85 NAVI000001 DEV 02.00 1997/08/13 13:45 24 WSER85 ******************************* Bottom of data ******************************
EDITING COMPONENTS IN BROWSE MODE

Use ISPF Edit Commands
You can use option E (Browse-in-Edit-Mode) from CMNBRWB0 or you can call the ISPF edit commands to edit baseline or promotion components. Because your edits are not saved when you exit the function, you do not have to worry about corrupting component contents during an edit session.
Copy Components to Target Data Sets

Using option C (Copy) you can copy component contents to other files or data set members, including CA-Panvalet and CA-Librarian files. This provides you more flexibility in renaming components for modeling of new programs within Change Man, enabling you to bypass the sometimes cumbersome task of checking out to a package and using the staged name field to create a copy of a component under a new member name. The figure below shows the panel Change Man displays after you select this option.
User Guide
19-11
CMNBRWB9 ---------- COPY TO DATASET/MEMBER NAME INFORMATION -------------COMMAND ===> FROM DATASET: MEMBER NAME: LIBRARY TYPE: BASELINE LEVEL: WSER85.TEST.JCL IEBCOPY JCL 0000
TO DATASET ===> WSER85.TEST.JCL LIBRARY ORG ===> pds (PDS, PDSE, SEQ, PAN or LIB) AS MEMBER NAME ===> COPY2 Press ENTER to process; Enter END command to exit.
From this panel, you control the destination library and member name the fields described in the table below:
Field
TO DATASET
Description
Indicate the dataset to which the component(s) is to be copied. For each component to be copied a separate target data set can be entered. Indicate the data set organization of the file targeted by the copy option. Type a new member name here if the component is to be renamed as a result of the copy operation. Leave this field blank if the component is not to be renamed.
LIBRARY ORG AS MEMBER NAME
Change Man checks to see if you have update access to the target data set you specify. If you do, Change Man displays the Print/Copy Job Card Information panel.
CMNBRWB2 -------------- PRINT/COPY JOB CARD INFORMATION ----------------------COMMAND ===> JOB STATEMENT INFORMATION: ===> //WSER85C JOB (X170,374),CHANGE MAN, ===> // MSGCLASS=9,NOTIFY=WSER85,TIME=1 ===> /*JOBPARM S=ESA5 ===> // JCLLIB ORDER=(WSER85.CHGMAN.PROCLIB)
Because all copies are done in batch, you must customize the JCL for your copy job.
19-12
Printing Copies of Components
PRINTING COPIES OF COMPONENTS

For applications you are authorized to use, you can: Print the contents of baseline and promotion library components Print copies of components with expanded copybooks
Using option P on panel CMNBRWB0, you can print a component in a baseline library. Change Man displays the Print/Copy Job Card Information panel shown above. Edit the job statements to specify routing information for the print job. This submits a print job for the component you specified.
Print Copies of Components with Expanded Copybooks

Using option X on panel CMNBRBW0, you can expand all copybook components before printing. A job card panel prompts you for submission and print routing information. Edit the job statements and submit the job.
BROWSING A COMPRESSED LISTING

Change Man has a facility which makes it possible to eliminate the paper printing and subsequent storage, access and traceability problems of any application's SYSOUT listings (SYSOUT listings are produced when compiling source components). You can use this facility regardless of whether or not your application uses all of Change Man's capabilities. Essentially, it gathers files originally destined to SYSOUT queues, then concatenates and compresses them into a single component of a PDS. Your administrator sets up the SYSOUT queues for the compression facility. This section describes how to: Browse compressed component listings Print, delete or keep compressed listings
BROWSING COMPRESSED LISTINGS

Complete the following tasks to browse Compressed Listings. 1 Access and provide filter criteria in the Browse Compressed Listing panel (CMNBLST0).
User Guide
19-13
Select option L from the Build Options menu. The following panel displays;
CMNBLST0 ----------------- BROWSE COMPRESSED LISTINGS ------------------------OPTION ===> SPECIFY SELECTION CRITERIA: PACKAGE ID ===> NAVI00005 APPLICATION ===> NAVI
COMPONENT NAME LIBRARY TYPE FROM DATE TO DATE
===> iebcopy ===> LST ===> ===>
(Required if PACKAGE ID not supplied; Non-blank: staging/baseline listings; Blank: staging listings only) (Blank or pattern for list) (Blank for list) (YYYYMMDD) (YYYYMMDD) (Y/N)
PROMPT FOR LISTING DISPOSITION ===> NO
Once you have correctly provided the above information and pressed Enter, a Compressed Listing panel (an example of this panel is shown in the following figure) displays.
ISRBROBF SER05.SER05.CMN91121.T185722.OUTLIST ----- LINE 00000000 COL 001 080 COMMAND ===> SCROLL ===> PAGE ********************************** TOP OF DATA ******************************* ****************************************************************************** * DDNAME: ASM.SYSPRINT * ****************************************************************************** ALLOC SYMBOL EXTERNAL SYMBOL DICTIONARY ID 0001 0002 ADDR 000000 000000 LENGTH 000000 0002FA LD ID FLAGS 00 06
TYPE PC CMNALLOC SD ALLOC LOC
OBJECT CODE
ADDR1
ADDR1 1 2 3 4 5 6 7 8
STMT
SOURCE STATEMENT
**************************************** * CCCCC M M N N AAAA L * C C MM MM NN N A A L * C M M M M N N N A A L * C M M M N N N AAAAAA L * C M M N N N A A L * C C M M N NN A A L * CCCCC M M N N A A LLL
19-14
Printing, Deleting or Keeping Compressed Listings
PRINTING, DELETING OR KEEPING COMPRESSED LISTINGS

Managing your compressed listing involves deleting, keeping and printing the listings after you have browsed them. You manage your compressed listing through the Specify Listing Disposition panel.
Delete, Keep and/or Print the Report

Type YES in the prompt for listing disposition field on the Browse Compressed Listing panel.The Specify Listing Disposition panel (CMNBLST2) appears.
CMNBLST2 ---------------- SPECIFY LISTING DISPOSITION ------------------------OPTION ===> LISTING DATASET NAME: data.set.name.log LISTING DISPOSITION ===> PD D K PD PK Delete Keep Print and Delete Print and Keep
JOB STATEMENT INFORMATION IF DISPOSITION IS PD OR PK: ===> //WSER85A JOB ,ACCOUNT INFORMATION______________________________________ ===> //*_____________________________________________________________________ ===> //*_____________________________________________________________________ ===> //*_____________________________________________________________________ Press ENTER to process; Enter END command to exit.
Indicate (D, K, PD, or PK) how Change Man is to handle disposition of the listing after you browse it. Complete the job card information to process the request.
BROWSING THE GLOBAL NOTIFICATION FACILITY

Global and application administrators use the Global Notification Facility (GNF) to notify the user of: Hints and tips on how to use various functions Changes to the system configuration
User Guide
19-15
Work-around solutions for problems Any other informational messages
During global administration, the administrator activates or deactivates the GNF. This enables the users to browse the GNF to review informational messages. Activation of the GNF causes Change Man to display option (N) on the Primary Option menu. If the global or application administrator updates the GNF, Change Man prompts the administrator with the message Notification Updated when the Primary Option menu is re-accessed. Once the message is displayed initially, Change Man does not redisplay the message unless the administrator updates the GNF with another message. The information the administrator enters in the GNF is immediately available for browsing by the user because the GNF is either a sequential dataset or a member of a partitioned dataset. Consequently, notification of a change or addition to the file appears at the users next logon to Change Man. The users last logon time is compared to the ISPF time stamp (similar to PDF statistics) from the last save of the GNF, and if it is less or earlier (i.e., if the GNF was saved after the user logged on last time), then a notification is sent. Browse the global notification file. 1 Type N on the Primary Option menu. The Global Notification panel appears.
CMNNOT00 ----------- GLOBAL NOTIFICATION REPORT DISPOSITION ------------------OPTION ===> OUTLIST DATASET : WSER83.CMN99214.T1931237.OUTLIST D K PD PK Delete Keep Print and Delete Print and Keep
REPORT DISPOSITION ===> D
JOB STATEMENT INFORMATION IF DISPOSITION IS PD OR PK ===> //WSER83Z JOB (X170,374),CHANGE MAN, <=== CHANGE ACCORDINGLY ===> // MSGCLASS=9,NOTIFY=WSER83,TIME=1 <=== CHANGE ACCORDINGLY ===> /*JOBPARM S=ESA5 <=== CHANGE ACCORDINGLY ===> //PROCLIB JCLLIB ORDER=(WSER99.CMN416Q.QACUST.SKELS) Press ENTER or END to process Enter CANCEL command to exit without saving changes.
19-16
Using the Scan Library Utility
The Global Notification panel displays with the information the administrator has provided. Type End or press PF3 on the command line to save file disposition information. Change Man displays the following panel.
In the outlist dataset field, type the temporary dataset name that contains the listing. Indicate (D, K, PD, or PK) how Change Man is to handle disposition of the report after you browse it. Complete the job card information to process the request.
USING THE SCAN LIBRARY UTILITY

The library scan facility lets you perform a quick impact analysis without using the impact analysis utility. With this scan utility, you can search the baseline level 0 libraries for any of the following: A character string or a dependency on-line or in batch. For a character string search, you can specify two (2) data strings. The second data string can be either AND or OR with the first data string. For a dependency search, you can scan for copybooks, dates names, calls, programs executed, procedures and various other types of dependencies that are associated with the scanned members.
When you request a scan, Change Man displays a table showing the records found and where they appear. Be aware that you cannot perform any actions on the items in the list. This function does not impact the baseline browse scan.
Scanning Online
Select option S on the Build Options menu to display the Library Scan Utility panel. On this panel, specify scan mode=0 (online).
User Guide
19-17
CMNSCN01 -------------------- LIBRARY SCAN UTILITY ------------------------COMMAND ===> APPLICATION LIBRARY TYPE SCAN MODE LIST MEMBERS ONLY DEPENDENCIES RECORDS TO SELECT CASE SENSITIVE? DISPLACEMENT: FROM TO COMPONENTS TO SCAN: BEGIN END DATA STRING 1 AND/OR DATA STRING 2 ===> ===> ===> ===> ===> ===> ===> ===> ===> ===> ===> ===> ===> ===> NAVI JCL O NO NO 0 N 2 72 (Blank for list) (Blank for list) (O-Online, B-Batch) (Y/N, Y-Members only, N-Members and Data) (Y/N, Scan for copybook, DSN, PGM etc.) (0 = all) (Y/N) (0 = all) (Max = 80) (Blank for all components, * for pattern)
CMN* XXXX* CMN AND CHANGE MAN
The following table describes the fields on the Library Scan Utility panel. Field
APPLICATION
Description
Fill in the application. Leave this field blank to access a list of applications. Fill in the library type. Leave this field blank to access a list of library types. Indicate whether the scan is online or batch. Indicate whether to display the member names (and associated data) that meet the criteria, or just the member name. Indicate whether to scan members for copybooks, datasets, procs or types of dependencies (Yes ), or to scan only for data strings (No ).
LIBRARY TYPE
SCAN MODE LIST MEMBERS ONLY DEPENDENCIES
Note:Embedded copybooks are not included in the scan.

RECORDS TO SELECT Type the number of records to display. You may limit your search to a specific number of found records by entering a number. Enter 0 to retrieve all matching records.
19-18
Field
CASE SENSITIVE?
Description
Indicate whether the scan is case sensitive:
YES - To search for a string exactly as you typed it. NO - To find all occurrences of a string, whether in upper, lower or mixed case.
DISPLACEMENT Type the starting and ending displacements to search within each record can be specified. Type 7 for column 7, 36 for column 36, etc. Type 0 in the from field to search all displacements within the record. Type the from and to component range to scan for. To search for all members, leave the begin field blank.
COMPONENTS TO SCAN
To scan for single members, type its name in the begin field. To limit the search scope (Change Man disregards the end field), enter a pattern (such as ABC*) in the begin field.
Note:You can enter a range such as MEMBERA to MEMBERZ even if the members do not exist in the dataset.
AND/OR Indicate whether second data string is AND or OR relative to the first character string. Type the data string to search. Imbedded blanks and non-alphabetic characters are searched for in place, and do not require quotes (around the string). To include leading or trailing blanks, enclose the string in apostrophes.
DATA STRING 1 and 2
Note:If you leave X and Y blank, the default is a dependencies scan.
User Guide
19-19
Allowing a Library Scan

If you do not restrict the scan by specifying list members only, you see a Scan Results panel. On this panel you can see the library component(s) and line(s) that match the search criteria. The bottom of the display shows statistics, such as the number of members scanned, the members that match the selection criteria, the total records that matches the criteria, and the elapsed time for the scan.
----------------------------------- SCAN RESULTS --------- ROW 1 TO 21 OF 4392 COMMAND ===> SCROLL ===> CSR _ BASELINE DATASET: WSER85.NAVI.BASE0.SRC <*** MEMBER AAADB2SQ ***> DB2SQ TITLE CHANGE MAN (&OS$DOS.-&CMNVRM - &RELDATE) * 000018 CMNCSADS DSECT * COMMON SYSTEM AREA 000021 CMNTCADS DSECT * TASK CONTROL AREA 000023 DB2$PLAN DS CL8 PLAN; CMN SUBSYS START 000041 DC C (&OS$DOS.-&CMNVRM) * 000091 USING CMNTCADS,RTCA,RTCA2 TASK CONTROL AREA 000111 USING CMNCSADS,RCSA COMMON SYSTEM AREA ADDRESSABILITY 000115 TM CSA$IND3,CMNIDB2 DB2 LICENSED 000120 ICM R15,B1111,CSAEPHLI CMNIMPFL ALREADY LOADED 000124 * LOAD EP=CMNIMPFL MODULE CMNIMPFL NAME 000126 DB2$0080 BASR R14,R15 CALL CMNIMPFL 000129 TM CSA$IND3,CMNIDB2P DB2 IN TROUBLE 000133 MVC 0(3,R1),=CL3CMN ALWAYS STARTS WITH CMN 000187 TITLE CHANGE MAN (&OS$DOS.-&CMNVRM - &RELDATE) * 000481 MVC DB2STRNG+2(LIMP#DRO1),IMP#DRO1 DROP TABLE CMN 000487 IMP#DRO1 DC CDROP TABLE CMN 000501 MVC DB2STRNG+2(LIMP#CRE1),IMP#CRE1 CREATE TABLE CMN 000508 IMP#CRE1 DC CCREATE TABLE CMN 000524 * QUERY CMNXBASE * 000547
Restricting a Library Scan

You restrict the scan by specifying list members only=Y on the Library Scan Utility panel. Provided the scanned member contains dependencies, you see a panel that lists the members that match the search criteria (No lines displayed). The bottom of the display shows statistics, such as the number of members scanned, the members that match the selection criteria, the total record that matches the criteria, and the elapsed time for the scan.
19-20
Panel CMNSCN01 for scan with member names only ----------------------------------- SCAN RESULTS ---------- ROW 1 TO 21 OF 102 COMMAND ===> SCROLL ===> CSR BASELINE DATASET: WSER85.NAVI.BASE0.SRC *** Member list only *** AAADB2SQ ABC10000 ADTCALD ADTCALL BETTEST1 BETTEST2 BETTEST3 BETTEST4 BLUECROS BLUEX24 BLUEX3 CCCDB2SQ CMN$ACPM CMNADMIN CMNBATCH CMNBOW10 CMNCDISP CMNCOBEB
Searching for Character Strings

On the Library Scan Utility panel, you can request a search for a character string. As displayed, the panel requests a scan for two character strings (DATA STRING 1=CMN and DATA STRING 2=CHANGE MAN ).
Search for Dependencies

When you scan for dependencies rather than character strings, by setting dependencies=Y and list members only=N on the Library Scan Utility panel, the panel SERPANEL displays. The bottom of the display shows statistics, such as the number of members scanned, the members that match the selection criteria, the total record that matches the criteria, and the elapsed time for the scan. Although the DATA STRING 1 field is ignored, you can help the scan utility determine what to scan for by specifying an optional language type, like JCL, COBOL, or PL1. For example, by specifying COBOL, you see only members with COBOL dependencies.
User Guide
19-21
Panel CMNSCN01 for dependencies scan ----------------------------------- SCAN RESULTS ---------- ROW 1 TO 21 OF 523 COMMAND ===> SCROLL ===> CSR BASELINE DATASET: WSER85.NAVI.BASE0.SRC <*** MEMBER AAADB2SQ ***> COPY CPY$GLBL 000016 COPY CPY$SETC 000017 COPY CPYCSADS 000022 COPY CPYTCADS 000024 COPY CPYDB2SQ 000026 COPY CPYIMPSQ 000028 <*** MEMBER ABC10000 ***> COPY CMNCOBC3 <*** MEMBER ADTCALD ***> COPY CMNCOBC3 <*** MEMBER ADTCALL ***> COPY CMNCOBC1 COPY CMNCOBC2 COPY CMNCOBC3 <*** MEMBER BETSRC1 ***>
000013
000014
000039 000040 000041
BATCH SCAN
To perform a batch scan, select option S on the Build Options menu and on the Library Scan Utility panel. scan mode=B (batch). The results of a batch scan are the same as what you see on line. The only difference is that, with a batch scan, you can choose where to route the output. To do the batch scan, you must connect to the CMN instance.
Search for Character String

Through the Library Scan Utility panel, you can conduct a batch scan for a character string. The Scan utility will scan for two character strings (DATA STRING 1=CMN and DATA STRING 2=CHANGE MAN ).
19-22
Batch Scan
When you press Enter, a batch job is submitted. When you review the job output outside of Change Man, you will see the following Batch Sysprint Output.
CMNBSCAN 4.1.6 - 99/08/12 08:52:52 Session established with Change Man Started task. Criteria for this Scan: Application :DAVE Library Type :SRC Records Selected :ALL Starting displacement :1 Ending displacement :80 Starting member :First Member Ending member :Last Member Scan Data 1 :CMN Or Scan Data 2 :ORG Dataset Organization :PDS Dataset Name to Scan :WSER99.CMNQ.BASE0.SRC <*** MEMBER AAADB2SQ ***> DB2SQ TITLE 'CHANGE MAN (&OS$DOS.-&CMNVRM - &RELDATE) CMNCSADS DSECT * COMMON SYSTEM AREA CMNTCADS DSECT * TASK CONTROL AREA ORG TCA$ALIO REDEFINE ALLIO AREA ORG TCA$ALIO REDEFINE ALLIO AREA ORG TCA$ALIO+4096+24 MAXIMUM USED ALLIO AREA <*** MEMBER ABC10000 ***> PROGRAM-ID. CMNCOBS2. COPY CMNCOBC3. .....more data....... ..................... ..................... ..................... *** 148 members scanned *** *** 95 member hits *** *** 4439 record hits *** *** 12.46 seconds elapsed time *** Session terminated with Change Man Started task.
000018 000021 000023 000025 000027 000033
000002 000013
In the output, you can see the library component(s) and line(s) that match the search criteria. The bottom of the display shows statistics, such as the number of members scanned, the members that match the selection criteria, the total record that matches the criteria, and the elapsed time for the scan.
User Guide
19-23
Search for Dependencies

By setting dependencies=Y on the Library Scan Utility panel, you can scan for dependencies rather than character strings. When you press Enter, a batch job is submitted. When you review the job output outside of Change Man, you will see the following Batch Sysprint Output. In the output, you can see the library components and lines that match the search criteria. The bottom of the display shows statistics, such as the number of members scanned, the members that match the selection criteria, the total record that matches the criteria, and the elapsed time for the scan.
CMNBSCAN 4.1.6 - 99/08/12 08:52:52 Session established with Change Man Started task. Criteria for this Scan: Scan for Dependencies Records Selected :ALL Starting displacement :1 Ending displacement :80 Starting member :First Member Ending member :Last Member Dataset Organization :PDS Dataset Name to Scan :WSER42.MISC.CNTL <*** MEMBER $$PRINT ***> PGM IEBGENER DSN WSER42.SUPERC.LIST <*** MEMBER $$REPRO ***> DSN WSER99.CMN410U.LINKLIB DSN WSER99.CMN410.LINKLIB DSN WSER99.SERNET.LINKLIB PGM IDCAMS DSN WSER42.CMN.CMNLOG.BKUP PGM CMNVINIT DSN WSER42.TEST.CMNLOG <*** MEMBER CMNFREZE ***> COPY CPY$GLBL COPY CPY$SETC <*** MEMBER ZAPCMN2 ***> PRC SUPERZAP DSN WSER99.CMN410U.LINKLIB ....more data................... ................................ *** 382 members scanned *** *** 237 member hits *** *** 1923 record hits *** *** 14.19 seconds elapsed time *** Session terminated with Change Man Started task.
000011 000014
000005 000006 000007 000008 000010 000015 000016
000175 000176
000003 000004
19-24
Running the Batch Scan
RUNNING THE BATCH SCAN

You perform a batch scan by specifying one of more of the following keywords for the SYSIN parameter on the module CMNBSCAN. Change Man constructs the job and submits it using the skeleton CMN$$BSN.
Keyword
SCN APL LIB DSN ORG MB1 MB2 LST DPN REC CAS DPS DPE ST1 AOR ST2
Description
Start a new scan (no/yes ); no is the default Application (required if no DSN) Library type (required if DSN is not specified) Data set name (required if APL and LIB are not specified) Library org (PDS/PAN/LIB/SEQ ); PDS is the default Start member name or pattern; first member is the default Ending member name or pattern; last member is the default Member list only (yes/no ); no is the default Dependencies (yes/no ); no is the default Maximum number of hits; all is the default Case sensitive (yes/no ); no is the default Displacement from; beginning of line is the default Displacement to; end of line is the default Scan string 1 And/Or string 1 with string 2; or is the default Scan string 2
The keyword SCN=YES lets you stack in multiple scans on batch run (i.e., lets you run scans against multiple libraries). In other words, SCN=YES tells Change Man to start a scan using the SYSIN prior to SCN=YES. If this keyword is not found, the input keywords are read until no more exist, and only one scan is performed.
User Guide
19-25
The SYSIN for each scan must contain either APL= and LIB=, or just DSN=. When scans are stacked in, all parameters from the prior scan are retained except for APL=, LIB= and DSN=. To change one or more of the scan parameters, do either of the following after the keyword: specify new input, or leave the input blank to reset it to the default.
19-26
QUERYING PACKAGES AND COMPONENTS
20
Change Man provides you with ability to query packages and their components so that you can access general and detailed information. You can use this information in conjunction with the activity log (if you have log security access) to display information on all of the activities of Change Man at your site. Managers, application leaders, operations personnel, and any concerned parties may wish to sign on to Change Man to query packages and components. Approvers may often use this function to review the package prior to approving or rejecting it. Operations personnel monitor package distribution, installation, and rippling of baseline, and depending on the scheduling system used at your site, operators may need to sign on to Change Man to review predecessor/successor job names as well as other information associated to a change package. Information for the query function is being gathered from the package master and is a record of all the packages where the component resides. You use the Query Options panel to access the querying functionality.
ACCESSING THE QUERY OPTIONS PANEL

To access the Query Options menu, select Q from the Primary Option Menu.
CMNQMENU ----------------------- QUERY OPTIONS ----------------------------OPTION ===> i P C I Package - Query package information Component - Query component information Impact - Impact analysis of component relationships
20-1
20 Querying Packages and Components
QUERYING CHANGE PACKAGES

When you query change packages you complete the following tasks: Specify the filter criteria used to filter package information through the Query Package Parameters panel. Browse the filtered Change Package List panel for packages you want to query. Request different types of query information for individual packages using the Package Information List.
Specifying Filter Criteria

Since you may want to query multiple packages for your site, and you may have many change packages, you access the Query Package Parameters panel to specify filter criteria so that Change Man can create a filtered change package list for you to query. 1 Select option P on the Query Options panel. The Query Package Parameters panel appears.
CMNQRY00 ------------------ QUERY PACKAGE PARAMETERS -------------------------COMMAND ===> SPECIFY SELECTION CRITERIA: PACKAGE ID ===> NAVI000005 PACKAGE STATUS CREATORS TSO-ID WORK REQUEST ID DEPARTMENT REMOTE SITE AFFECTED PACKAGE LEVEL PACKAGE TYPE PACKAGE TIME SPAN FROM INSTALL DATE TO INSTALL DATE FROM CREATION DATE TO CREATION DATE OTHER PARAMETERS ===> APR ===> ===> ===> ===> ===> WSER85 416NAVIG DP REMPRM1 4
(Full name or * to (DEV, FRZ, BAS, BAK,
or pattern; blank for list, select all packages) APR, REJ, DIS, INS, OPN, CLO, TCC or DEL)
===> P ===> P ===> ===> ===> ===> ===> Y
20-2
Querying Change Packages
Complete information in the filter criteria fields. This information is used to limit the range of information which is to be displayed in the Query Package List. You can fill in any combination of these fields to limit your search. To limit the range of packages displayed by specific application(s), leave the package ID field blank (or specify a pattern). The following tables describes the fields of the Query Package Parameters panel. All of these fields are optional. If you leave any of them blank all of the change packages in the system are presented. Field
PACKAGE ID
Description
Type the package ID or a pattern to display the list of packages pending approval. The status of the change package. Type the user ID to mask the search criteria and display only those packages, for the specified id. Type the work request ID.
PACKAGE STATUS CREATORS TSOID WORK REQUEST ID DEPARTMENT REMOTE SITE AFFECTED PACKAGE LEVEL
Type the department. Type the remote site to display only the packages with approval pending that are to be installed at that site.
Simple View a change package that contains a change that is unrelated to any other change package. Complex/Super View a complex or super package that is the parent of two or more participating change packages. After you have created all participating change packages, someone is designated to create the complex or super package. It contains a list of the participating packages with the general and control information. It does not contain any of the components to be Installed. Participating View change packages that are related to one or more other packages. All of these packages are considered to be participating with each other.
User Guide
20-3
Field
PACKAGE TYPE
Description
Planned View packages with scheduled changes that are required to follow all established application rules. Unplanned View packages with unscheduled changes. (i.e., possibly an emergency fix) Permanent View packages with scheduled changes that update baseline/ production libraries. Permanent changes are either planned or unplanned. Temporary View packages with changes that run for a predetermined length of time. Once that time has expired, Change Man automatically deletes the change if a scheduler is used. Otherwise, if you use a manual scheduling method, the job will be submitted on hold, and will need to be released when the duration of days is met. Temporary changes do not update baseline/production libraries. These changes are installed into a static override library. Temporary changes are either planned or unplanned.
PACKAGE TIME SPAN
Type the installation start and end date (yyyymmdd format) to view packages within this time span. Type the creation start and end date (yyyymmdd format) to view packages within this time span. Type Y(es) or N(o) to indicate whether to further limit the display of packages based on the types of components contained in the packages. If you type Y, and press Enter, the Extended Search Criteria panel displays. If you type N, and press Enter, the Query Package List panel displays.
20-4
Using the Extended Search Criteria Panel

The Extended Search Criteria panel displays when you type YES in the other parameters field of the Query Package Parameters panel. It lets you further limit the display of change packages by the kinds of components the change package contains.
CMNQRY01 ------------------ EXTENDED SEARCH CRITERIA ----------------------COMMAND ===> NON-SOURCE SOURCE AND LOAD RENAME/SCRATCH INFO CUSTOM COMPONENT ===> y ===> ===> y ===> (Y/N) (Y/N) (Y/N) (Y/N)
Type YES next to each row of the types of change package components to limit the display of change packages by the kinds of components the change package contains. For example, to display only those change packages that have custom components, type YES next to custom component. If you do not want to limit the display of change packages by components contained, type NO (or blank) next to any of the component types. Press Enter. The Query Package List appears. (See Browsing the Query Package List on page 20-5).
Browsing the Query Package List

When Change Man is done processing your filter criteria, it displays the Query Package List.
CMNQRY02 --------------------- QUERY PACKAGE LIST ----------------------------COMMAND ===> SCROLL ===> PAGE PACKAGE ID STA INSTALL LVL TYPE WORK REQUEST DEPT PROMOTION AUD CREATOR _ NAVI000005 FRZ 19971230 PART PLN/PRM 416NAVIG DP 04 WSER85 ******************************* BOTTOM OF DATA *******************************
When the Query Package List panel appears, the panel displays a shortened list change package information. You can: Review and request queries on the shortened list, or you can switch the viewing mode to long to see the package title as well.
User Guide
20-5
Sort on any column heading, and you can use the LOCATE command on those sorted fields.
To switch between the short and long viewing modes in the Query Package List: Type LONG at the command line if you want to expand the shortened list. The long listing shows all listings regardless of status. Type SHORT if you want to condense the long list. The shortened listing shows packages in motion.
To display detailed information about one or more change packages, type S next to the packages you want to display and press Enter. The Package Information Categories panel displays.
CMNQRY03 --------------- PACKAGE INFORMATION CATEGORIES ---------------------COMMAND ===> SCROLL ===> PAGE PACKAGE ID: NAVI000005 CREATOR: WSER85 STATUS: APR AUDIT RC: 04 INSTALL DATE: 19971230
_ General s Non-Source _ Source _ Source and Load Relationship _ Renames and Scratches _ Approval List _ Site/Install Date Information _ Site Activities Date and Time _ Custom Forms _ Participating Package(s) _ Status Start Date and Time _ Revert Reasons _ Backout Reasons _ Promotion History _ Promotion Libraries _ Development Staging Libraries _ Production Staging Libraries _ Production Libraries _ Baseline Libraries ******************************* Bottom of data ******************************
The following tables describes the fields of the Package Information Categories panel (CMNQRY03).
20-6
Field
PACKAGE ID STATUS INSTALL DATE CREATOR AUDIT RC
Description
The ID of the package. The current status of the package. The proposed installation date (yyyymmdd format) of the package. The TSOID of the package creator. The audit return code of the last audit job run, if any.
User Guide
20-7
Field
Package Category
Description
Selecting any of the following categories displays information specific to your package. (See Appendix A. Package Category Panels.) General - Display general package information, such as description; install date and time; requestor name, phone number, and department. Non-Source - Display non-source components in the package: COPYLIB members, cataloged JCL procedures, linkage editor control statements, control cards, and documentation. Source - Display source component staging information. Source and Load Relationship - Display component and their related components. Renames and Scratches - Display package utility requests. Approval List - Display package approval list. Site/Install Date Information - Display remote site information. Site Activities Date and Time - Display starting date and time stamp of activities that were performed at the remote site. Custom Forms - Display custom forms information. Participating Package(s) - Display individual application packages (participating packages) that make up this complex/super package. Status Start Date and Time - Display all possible statuses for the package, as well as the date and time that the package was assigned the status. Revert Reasons - Display the reasons the package was reverted. Backout Reasons - Display the reason the package was backed out Promotion History - Display promotion/demotion history of the package, listed in reverse chronological order. Remote Promotion History - Displays remote promotion or demotion history of the package and component-level remote promotion information, listed in reverse chronological order. Promotion Libraries - Displays the level and data set names of the promotion libraries for the application. Remote Promotion Libraries - Displays the remote site, levels and dataset names of the promotion libraries for the application. Development Staging Libraries - Display the data set name of the development environment staging libraries for the package. Production Staging Libraries - Display the data set name of the production environment staging libraries for the package. Production Libraries - Display the data set name of the production libraries affected by the package. Baseline Libraries - Display the data set name of the baseline libraries affected by the package.
To select a package category, place an S beside the category and press Enter.
20-8
Querying Components
QUERYING COMPONENTS
To search and display component information, take the following steps: 1 From the Primary Option menu, select Option Q . The Query Options panel appears. From the Query Options panel, select Option C. The Query Component Parameters panel (CMNQCMP1) appears
CMNQCMP1 ----------------- QUERY COMPONENT PARAMETERS ---------------------COMMAND ===> SPECIFY SELECTION CRITERIA: COMPONENT NAME ===> IEBCOPY (Full name or pattern) COMPONENT TYPE ===> JCL (Full library type or pattern) APPLICATION ===> NAVI PACKAGE ID ===> NAVI000005 PROCEDURE NAME ===> TSOID ===> WSER85 DISPLAY MODE ===> SHORT (S-Short, L-Long) CHECKOUT/STAGING FROM DATE ===> (YYYYMMDD) TO DATE ===> (YYYYMMDD) Press ENTER to process; Enter END command to exit.
Complete the selection criteria to query components and press Enter. Change Man displays the Query Component List.
User Guide
20-9
CMNQCMP2 ------------------- QUERY: COMPONENT LIST ---------- ROW 1 TO 17 224 COMMAND ===> SCROLL ===> PAGE BROWSE NEXT PAGE OF COMPONENT HISTORY ===> Y LIB SRC SRC SRC SRC SRC SRC SRC SRC SRC SRC SRC SRC SRC SRC SRC SRC SRC NAME CMN$ACPM CMN$STUB CMN$UTIL CMN$XMEM CMNADMIN CMNADMJM CMNADMSO CMNALLIO CMNALLOC CMNAPI CMNAPIS CMNAPIXM CMNAPI2 CMNAPI3 CMNAPPRV CMNAPS10 CMNAPS20 (Y/N)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Review the component list. If there are many components displayed on your screen, use any of the following methods: Type P and any page number on the command line and press Enter. Change Man will display that page number. (Example: P 4 will display page four of the component entries that match the selection criteria.) Use the PF7 and PF8 keys to page up and page down through the list of components. Type N P to display the next block of components that match the selection criteria.
Bottom of Data shown after repeated Page Down commands is not an accurate indication of the end of the component list. Use the Next Page command until End Of Component List message is displayed in upper right-hand corner. 4 To display detailed information about one or more components, type S in the first column next to each component you want displayed, and press Enter. The Component History panel appears.
20-10
Querying Impact Analysis Data
CMNCMPHI --------------------- IEBCOPY.JCL HISTORY ---------- ROW 1 TO 2 OF 2 COMMAND ===> SCROLL ===> PAGE Press ENTER to continue. PACKAGE ID STA PROMOTION VV.MM LAST ACTION SIZE PROCNAME ID NAVI000005 DEV 02.02 1997/08/18 15:58 24 WSER85 NAVI000001 DEV 02.00 1997/08/13 13:45 24 WSER85 ******************************* Bottom of data ******************************
NOTES Components that are not in the package master have a status of D/A (deleted or archived).
QUERYING IMPACT ANALYSIS DATA

Impact analysis is a Change Man facility used to determine relationships and dependencies between the following baseline library components: SRC - CPY (source and copylib) LOD (load and load) PRC/ JCL - DSN PRC/ JCL - PGM PRC/ JCL - PRC
There are two versions of the impact analysis facility: Flat - Sequential file which is not automatically updated by Change Man when relationships change in production. As determined by your administrator, based on your environment and workload, the file can be refreshed periodically by the batch job, CMNASIST, which can be scheduled using an automatic scheduler. DB2 Table - DB2 table containing relationship data which are automatically updated during the baseline ripple function when relationships change in production.
Check with your administrator to determine which version of the impact analysis facility is used at your site and how it is implemented.
User Guide
20-11
By querying impact analysis data for select components you can do the following: Assess the effort involved in completing an intended change. Estimate staffing schedules. Avoid product failures caused when a change is Installed but related components have been omitted.
Specify Search Criteria for the Component List

This panel lets you query the impact of a selected component. Specify search criteria for components to be analyzed. 1 2 Select Option Q on the Primary Option menu. Select Option I on the Query Options panel. The following panel displays.
CMNIMPMP --------------- IMPACT ANALYSIS OF COMPONENTS --------------------COMMAND ===> SPECIFY SEARCH CRITERIA: COMPONENT NAME ===> COMPONENT TYPE ===> APPLICATION ===> RELATIONSHIP ===> RELATIONSHIP TO ===>
ALLIO JCL NAVI ALLIOCPY
Field
COMPONENT NAME COMPONENT TYPE
Description
Type a component name, a full data set name, or a component pattern ending in the wild card character *. For example: CMNIMPL and CMN* . Indicate a library type. The list of library types is dependent on your Global Generation for library types. The sacred list consists of SRC, CPY, LOD, JCL, PRC, DOC, LCT, DBR, and DBB, but there may be many more. The library types in your list should reflect the contents of the libraries. To display a list of library types, leave this field blank and press Enter. The Type Selection List displays .
20-12
Field
APPLICATION
Description
Type an application name to limit your search to a specified application. To obtain a list of applications leave this field blank and Change Man displays the Component Selection List. Type a relationship to further clarify the request. To obtain a list of relationships, leave this field blank and press Enter. You must specify a relationship by specifying a library type first. The list of relationships can look for the following: CPY a component COPY s, INCLUDE s, or EXEC component.
RELATIONSHIP
SQL s another
LOD a load component contains a statically linkage edited called subroutine; external references are captured. PGM a JCL or PRC component invokes a program via EXEC PGM= . DSN a JCL or PRC component references a dataset name temporary dataset names (those starting with ampersand '&') are not taken component names and GDG (take up to the open parenthesis) references are stripped off first. PROC a JCL or PRC component invokes a program via EXEC PROC=. RELATIONSHIP TO If you type a component name in this field it shows the backward relationship to the component name. If you leave it blank, it shows the forward relationship.
After typing the specific information, press Enter. The Application Selection List panel displays.
CMNIMPP3 ----------------- APPLICATION SELECTION LIST ------------ ROW 1 OF 5 COMMAND ===> SCROLL ===> PAGE COMPONENT NAME: ALLIO COMPONENT TYPE: SRC RELATIONSHIP: RELATIONSHIP TO: APPL s NAVI _ C410 _ SERA _ BRP _ CKL1 ****************************** Bottom of data *****************************
User Guide
20-13
From the Application Selection List panel, select the desired application and press Enter. The Type Selection List panel appears.
CMNIMPP2 -------------------- TYPE SELECTION LIST -------------- ROW 16 OF 47 COMMAND ===> SCROLL ===> PAGE COMPONENT NAME: ALLIO APPLICATION: NAVI RELATIONSHIP: RELATIONSHIP TO: TYPE MSG LSO LST DBB DESCRIPTION
_ _ _ _
Type S to select the type SRC, and press Enter. The Component Relationship panel displays.
CMNIMPP4 ------------------ COMPONENT RELATIONSHIPS ------------- ROW 1 OF 24 COMMAND ===> SCROLL ===> PAGE Enter END command to exit. COMPONENT NAME: ALLIO COMPONENT TYPE: SRC APPLICATION: NAVI RELATIONSHIP: RELATIONSHIP TO: REL CPY CPY CPY CPY TO OR FROM ENTITY CMN$GLBL CMN$LOG CMN$SETC CMNCOMRT
20-14
Query the Component Selection List

On the Impact Analysis of Components panel, if you left the application field blank, the Component Selection List panel appears.
CMNIMPP1 ------------------ COMPONENT SELECTION LIST -------------------------COMMAND ===> SCROLL ===> PAGE COMPONENT NAME: ALLIO COMPONENT TYPE: SRC APPLICATION: NAVI RELATIONSHIP: RELATIONSHIP TO: COMPONENT NAME _ CMNBOW10 _ CMNCDCPR s CMNCDCPY
Type an S next to the desired component name and press Enter. The Component Relationships panel appears.
User Guide
20-15
CMNIMPP4 ------------------ COMPONENT RELATIONSHIPS ------------- ROW 1 OF 24 COMMAND ===> SCROLL ===> PAGE Enter END command to exit. COMPONENT NAME: ALLIO COMPONENT TYPE: SRC APPLICATION: NAVI RELATIONSHIP: RELATIONSHIP TO: REL CPY CPY CPY CPY CPY CPY CPY CPY CPY CPY CPY CPY TO OR FROM ENTITY CMN$GLBL CMN$LOG CMN$SETC CMNCOMRT CMNDYNAL CMNFMAIN CMNGMAIN CMNIMPSQ CMNLDCA CMNMBRLS CMNPATCH CMNPDSDR
The Component Relationships panel displays all upstream and downstream relationships for a requested component. A component which calls the requested component has an upstream relationship with the requested component. On the other hand, the component which is called by the requested component has a downstream relationship with the requested component.
20-16
PACKAGE CATEGORY PANELS
This appendix displays the panels that appear when you make a selection on the Package Information Categories panel (CMNQRY03). See Chapter 20 Querying Packages and Components.
GENERAL INFORMATION
Following are the general information panels.
CMNQRY10 ----------------- QUERY: CONTROL INFORMATION -------------------COMMAND ===> PACKAGE ID: NAVI000005 COMPLEX/SUPER ID: NAVI000003 PACKAGE TITLE ===> This is to install test jcl. APPLICATION REQUESTERS NAME REQUESTERS PHONE WORK REQUEST ID DEPARTMENT PACKAGE LEVEL NAVI I.PROGRAMMER 555-1212 416NAVIG DP 4 (1-Simple, 2-Complex, 3-Super, 4-Participating) PACKAGE TYPE ===> P (Planned or Unplanned) PACKAGE TIME SPAN ===> P (Permanent or Temporary) UNPLANNED REASON CODE ===> TEMPORARY CHANGE DURATION ===> (In days) Enter END command to continue. ===> ===> ===> ===> ===> ===> STATUS: APR STATUS: OPN INSTALL DATE: 19971230
A-1
A Package Category Panels
CMNPGNL2 ---------------COMMAND ===>
PACKAGE DESCRIPTION --------------
PACKAGE ID: NAVI000005
STATUS: DEV
(minimum one line, maximum 46 lines) _This is to install test JCL. __________________________________________ ******************************* BOTTOM OF DATA ********************************
CMNPGNL3 ------------- UPDATE: INSTALLATION INSTRUCTIONS ---- ROW 1 TO 1 OF 1 COMMAND ===> SCROLL ===> PAGE Press ENTER to process; enter END command to exit. PACKAGE ID: NAVI000005 CONTINGENCY ===> 1 STATUS: DEV INSTALL DATE: 19971230
1-Hold production and contact analyst 2-Backout change, continue production 3-Other ===> (CMN, Manual or Other)
SCHEDULER
===> OTHER
(minimum one line, maximum 46 lines) Install using procedure #1._____________________________________________ ******************************* Bottom of data *****************************
NON-SOURCE
CMNSTG01 ---------------- STAGE: NAVI000005 COMPONENTS ------ ROW 1 TO 4 OF 4 COMMAND ===> SCROLL ===> PAGE NAME TYPE STATUS CHANGED PROCNAME ID REQUEST s_ CPXLOAD JCL CHECKOUT 19970818 145338 WSER85 s_ HOUSKEEP JCL CHECKOUT 19970818 145338 WSER85 s_ IEBCOPY JCL CHECKOUT 19970818 145338 WSER85 __ REPORTS JCL CHECKOUT 19970818 145338 WSER85 ******************************* Bottom of data ******************************
Type B to display the full contents of the component (the CMNBROWS panel displays) or type H to display component history (the History panel displays.
A-2
Source
You can sort by any field in ascending order, using the Sort command with the keywords NAME or MEMBER. Then, you can issue a Locate command to find a component name.
SOURCE
CMNSTG01 ---------------- QUERY: NAVI000009 COMPONENTS ---- ROW 1 TO 11 OF 11 COMMAND ===> SCROLL ===> CSR NAME TYPE STATUS CHANGED LANGUAGE PROCNAME ID REQUEST __ CMNASIST SRC ACTIVE 19970707 162320 ASM CMNASM WSER03 __ CMNBAT40 SRC ACTIVE 19970630 134444 ASM CMNASM WSER42 __ CMNCDCPR SRC ACTIVE 19970708 130440 ASM CMNASM WSER41 __ CMNCOMPR SRC ACTIVE 19970708 165356 ASM CMNASM WSER41 __ CMNIMSG SRC ACTIVE 19970706 110922 ASM CMNASM WSER42 __ CMNMSGCD SRC ACTIVE 19970705 102536 ASM CMNASM WSER03 __ CMNPARSE SRC ACTIVE 19970630 095819 ASM CMNASM WSER03 __ CMNPOPLP SRC ACTIVE 19970705 115544 ASM CMNASM WSER41 __ CMNPROMO SRC ACTIVE 19970701 152743 ASM CMNASM WSER42 __ CMNQUERY SRC ACTIVE 19970629 161428 ASM CMNASM WSER03 __ CMNSTGER SRC ACTIVE 19970701 151422 ASM CMNASM WSER42 ******************************* BOTTOM OF DATA *******************************
Type B to display the full contents of the component (the CMNBROWS panel displays) or type H to display component history. Type S to display the compile and link edit options. Type SL to display the Source to Load Relationship panel.
2 3
User Guide
A-3
You can sort by any field in ascending order, using the Sort command with the keywords NAME or MEMBER. Then, you can issue a Locate command to find a component name.
CMNQRY22 ------------ QUERY: COMPILE AND LINK EDIT OPTIONS ----------------COMMAND ===> PACKAGE ID: NAVI000005 STATUS: APR INSTALL DATE: 19971230
DATASET NAME: somnode.navi000005.src LIBRARY ORG: pds STAGERS TSO-ID: wser85 COMPONENT STATUS: STAGED NAME: allio SOURCE NAME: allio LIBRARY TYPE: src LANGUAGE: asm COMPILE PROC: asm COMPILE PARMS: LINK EDIT PARMS: DB2 PRE-COMPILE: NO OTHER OPTIONS ===> y (Y/N for additional user options) Press ENTER to continue; Enter END command to exit.
A-4
Source and Load Relationship
SOURCE AND LOAD RELATIONSHIP

CMNQRY21 ---------------- SOURCE TO LOAD RELATIONSHIP -----------------------COMMAND ===> SCROLL ===> PAGE Press END command to exit. PACKAGE ID: NAVI000005 SOURCE NAME TYPE ALLIO SRC LOAD NAME TYPE STATUS ALLIO LOD ACTIVE STATUS: APR INSTALL DATE: 19971230
PROMOTION 1 PROMO1
CHANGED ID 19970701 162320 WSER85
SETSSI 84553124
RENAMES AND SCRATCHES

CMNQRY12 ----------------- QUERY: RENAME/SCRATCH LIST -----------------------COMMAND ===> SCROLL ===> PAGE PACKAGE ID: NAVI000005 REQ SCR NAME RENAME IEBCOPY TYPE JCL STATUS: APR CHANGED 19970707 090520 INSTALL DATE: 19971230 ID STATUS WSER85 ACTIVE
APPROVAL LIST
CMNAPPLS ----------------------- APPROVAL LIST -----------------------------COMMAND ===> SCROLL ===> CSR Press ENTER to process; enter END command to exit. PACKAGE ID: NAVI000005 STATUS: DEV INSTALL DATE: 19971230
APPROVER DESCRIPTION ID DATE TIME SEQ STATUS _ DEVELOPMENT GROUP 001 _ DOCUMENTATION GROUP 002 _ QA GROUP 003 _ MANAGEMENT GROUP 004 ******************************* BOTTOM OF DATA *******************************
User Guide
A-5
SITE ACTIVITIES DATE AND TIME

CMNQRY14 ------------ QUERY: SITE ACTIVITIES DATE AND TIME - ----------------COMMAND ===> SCROLL ===> PAGE Press END command to exit. PACKAGE ID: NAVI000005 REMOTE SITE REMPRM1 REMPRM1 STATUS: APR INSTALL DATE: 19971230
TYPE OF ACTIVITY DATE TIME Distribution Dis-Acknowledgment Installation Temp Change Cycled Full Back-Out Revert Back to DEV *******************************BOTTOMOF DATA*******************************
SITE AND INSTALL DATE INFORMATION

If your administrator has set up your Change Man environment as an All site, Change Man displays the Update Site Information panel.
CMNONSTE ------------------ UPDATE: SITE INFORMATION ----------------------COMMAND ===> Press ENTER to process; enter END command to exit. PACKAGE ID: NAVI000006 INSTALL YYYYMMDD 19971230 CREATOR: WSER85 STATUS: DEV
DATE AND TIME: FROM 0700 TO 1600 PRIMARY/BACKUP CONTACTS Boss_____________________ Asst Boss________________ PHONE NUMBERS xt277__________ xt259__________
Otherwise, Change Man displays the Query Remote Site Information panel.
A-6
Custom Forms
CMNPRSTI -------------COMMAND ===>
REMOTE SITE INFORMATION ----------------------------SCROLL ===> PAGE
Press ENTER to process; enter END command to exit. Enter * in line command field for remote site selection list. PACKAGE ID: NAVI000005 CREATOR: WSER85 STATUS: DEV
REMOTE INSTALL DATE/TIME SITE YYYYMMDD FROM TO PRIMARY/BACKUP CONTACTS PHONE NUMBERS remote1__ 19971230 0900 1800 Boss_____________________ x275___________ 0900 1600 Asst Boss________________ x276___________ ******************************* BOTTOM OF DATA ********************************
CUSTOM FORMS
CMNCUSTM --------------- UPDATE: CUSTOM COMPONENT LIST ---COMMAND ===> PACKAGE ID: NAVI000005 STATUS: DEV
Press ENTER to process; Enter END command to exit. LINE COMMANDS: S - Select, D - De-Select, X - Submit for Approval A - Approve, R - Reject, B - Browse Reject Reasons LEAD DAYS COMPONENT DESCRIPTION TIME LEFT STATUS FUNCTION s Build Generation Data Group Request 0 133 ACTIVE *Select Dasd Request - Data Set Space 0 133 Problem Summary 0 133 Report Distribution Information 0 133 UDPO Standards and Guidelines Revision 0 133 Tape Retention Register 0 133 UDPO Standards Exemption Request 0 133 Security Information 0 133 CA7 Jcl Update 0 133 CA7 Operations Schedule Update 0 133 ******************************* Bottom of data *******************************
User Guide
A-7
PARTICIPATING PACKAGE
CMNQRY11 --------------- QUERY: PARTICIPATING PACKAGES ----------------------COMMAND ===> SCROLL ===> PAGE Press END command to exit. PACKAGE ID: NAVI000005 PACKAGE ID NAVI000006 NAVI000003 NAVI000008 STATUS DEV DEV INS STATUS: APR
INSTALL DATE 19971230 19971230 19970730
STATUS START DATE AND TIME

CMNQRY04 ------------- QUERY: STATUS START DATE AND TIME ------------------COMMAND ===> Press END command to exit. PACKAGE ID: NAVI000005 STATUS DEV REV-DEV FRZ APR REJ STATUS: APR DATE 19970701 19970811 19970819 TIME 0830 1530 1645 INSTALL DATE: 19971230
REVERT REASONS
CMNREVRS ------------------COMMAND ===> PACKAGE ID: NAVI000005 ===> This package had errors. ===> ===> ===> REVERT REASONS ------------------------------
STATUS: FRZ
A-8
Backout Reason
BACKOUT REASON
CMNQRY13 ---------------- QUERY: BACKOUT REASONS LIST -----------------------COMMAND ===> SCROLL ===> PAGE PACKAGE ID: NAVI000005 REMOTE SITE DATE TIME _ REMPRM1 19970823 111500 STATUS: BAK INSTALL DATE: 19971230
PROMOTION HISTORY
CMNQRY23 ----------------- PACKAGE PROMOTION HISTORY ------- ROW 1 TO 15 OF 65 COMMAND ===> SCROLL ===> PAGE Press END command to exit. PACKAGE ID: NAVI000005 PROMOTE/DEMOTE HISTORY LVL Selective Promotion 1 Selective Demotion 1 Selective Promotion 1 STATUS: ACTIVE INSTALL DATE: 19971230 TIME 16:47 16:46 14:25 ID WSER85 WSER85 WSER85
NICKNAME DATE LEVEL1 1997/03/01 LEVEL1 1997/03/01 LEVEL1 1997/03/01
User Guide
A-9
REMOTE PROMOTION HISTORY

CMNQRY26 ------------ REMOTE PROMOTION SELECTION LIST -----------------------COMMAND ===> SCROLL ===> PAGE Press ENTER to process; Enter END command to exit. PACKAGE ID: NAVI000005 REMOTE SITE NAME _ REMPRM1 CREATOR: WSER85 STATUS: DEV INSTALL DATE: 19971230
FORCE DEMOTION (Y/N) REMOTE LOCAL NO NO
Type S next to a remote site to view the (Promotion and Demotion) package list, and press Enter. A panel similar to the following appears.
CMNQRY27 - PACKAGE REMOTE PROMOTION HISTORY FOR NAVI000009 - ROW 49 TO 64 OF 133 COMMAND ===> SCROLL ===> PAGE Press ENTER for component list; Enter END command to exit. PACKAGE ID: NAVI000009 CREATOR: WSER85 STATUS: DEV DATE 1997/07/16 1997/07/16 1997/07/16 1997/07/16 1997/07/15 1997/07/15 1997/07/15 INSTALL DATE: 19971230 ID WSER85 WSER85 WSER85 WSER85 WSER85 WSER85 WSER85 REMOTE Completed Completed Completed Completed Completed Completed Completed
REMOTE HISTORY MOD/CNT PROMOTION Selective Promotion 3 2 TEST102 Selective Demotion 2 2 TEST102 First Promotion at 0 6 2 TEST102 Full Demotion 1 0 STAGING Selective Promotion 2 1 TEST101 Selective Demotion 2 1 TEST101 Full Promotion 7 1 TEST101
TIME 16:14 16:33 16:49 15:47 16:34 16:33 16:32
Press Enter to view the remote promotion status at the component level. The following panel displays.
A-10
Promotion Libraries
CMNQRY28 -COMPONENT REMOTE PROMOTION STATUS FOR NAVI000005-- ROW 1 TO 15 OF 15 COMMAND ===> SCROLL ===> PAGE Press END command to exit. PACKAGE ID: NAVI000005 NAME TYPE $$$BRWBL CPY AL CPY AUDIT CPY CMN$$BND CPY CMNEX009 LOD CMNEX009 SRC CMNEX026 LOD CMNEX026 CPY CMNEX027 LOD CMNEX027 SRC CMNEX028 LOD CMNEX028 SRC CMNEX035 LOD CMNEX035 SRC CMNMOD CPY CREATOR: WSER85 DATE 1995/07/21 1995/06/22 1997/07/26 1997/07/26 1997/07/26 1997/07/26 1997/07/26 1997/07/26 1997/07/26 1997/07/26 1997/07/26 1997/07/26 1997/07/26 1997/07/26 1995/07/16 STATUS: APR TIME 17:54 15:20 20:01 20:01 20:01 20:01 20:01 20:01 20:01 20:01 20:01 20:01 20:01 20:01 18:36 ID WSER85 WSER85 WSER85 WSER85 WSER85 WSER85 WSER85 WSER85 WSER85 WSER85 WSER85 WSER85 WSER85 WSER85 WSER85 INSTALL DATE: 19971230 STATUS DELETED
PROMOTION 0 STAGING 0 STAGING 2 TEST102 2 TEST102 2 TEST102 2 TEST102 2 TEST102 2 TEST102 2 TEST102 1 TEST102 0 STAGING 0 STAGING 1 TEST101 0 STAGING 0 STAGING
OVERLAID
RESTAGED DELETED DELETED DELETED
PROMOTION LIBRARIES
CMNQRY24 --------COMMAND ===>
- PROMOTION LIBRARIES PART 1 OF 2 -----------------------SCROLL ===> PAGE
Press END command to exit. PACKAGE ID: NAVI000006 STATUS: DEV INSTALL DATE: 19971230
NICKNAME ENTITY LEVEL PROCEDURE _ UNIT UNITDEMO 1 _ ACCEPT ACCPDEMO 2 _ QCQC QCQCDEMO 3 ******************************* BOTTOM OF DATA *******************************
User Guide
A-11
CMNQRY25 ------------ PROMOTION LIBRARIES PART 2 OF 2 ------- ROW 1 TO 5 OF 8 COMMAND ===> SCROLL ===> PAGE Press END command to exit. PACKAGE ID: NAVI000006 LIB CPN STATUS: APR INSTALL DATE: 19971230
DATASET NAMES FOR NICKNAME , LEVEL 1 USERID.CMN410U.PANELS
DBB
USERID.CMN410U.CNTL
DBR
USERID.CMN410U.CNTL
HPN
USERID.CMN410U.PANELS
LOD
USERID.CMN410U.LINKLIB
REMOTE PROMOTION LIBRARIES
CMNQRY29 -----COMMAND ===>
- REMOTE PROMOTION LIST PART 1 OF 3 --------
Press ENTER to process; Enter END command to exit. PACKAGE ID: NAVI000005 CREATOR: WSER85 REMOTE SITE NAME TEST TEST10 TEST2 TEST3 TEST4 TEST5 TEST6 TEST7 TEST8 FORCE DEMOTION (Y/N) REMOTE LOCAL Y Y N Y N Y N Y Y N N Y Y N N Y Y N STATUS: APR INSTALL DATE: 19971230 INTERNAL READER CLASS REMOTE LOCAL A A J B A A L D M E N F O G P H Q I
_ _ _ _ _ _ _ _ _
A-12
Remote Promotion Libraries
Type S next to a remote site to view package library information, then press Enter. The following panel displays.
CMNQRY30 ----- / - REMOTE PROMOTION PART 2 OF 3 ------------- ROW 1 TO 2 OF 2 COMMAND ===> SCROLL ===> PAGE Press ENTER to process; Enter END command to exit. PACKAGE ID: NAVI000005 CREATOR: WSER85 STATUS: DEV INSTALL DATE: 19971230
NICKNAME ENTITY LEVEL PROCEDURE _ TEST101 DAVE 1 CMN$$RPM _ TEST102 DAVE 2 CMN$$RPM ****************************** BOTTOM OF DATA ********************************
Type S next to the promotion levels that you want to view, then press Enter.
CMNQRY31 - REMOTE PROMOTION LIBRARIES PART 3 OF 3 ---------------------------COMMAND ===> SCROLL ===> PAGE Press END command to exit. PACKAGE ID: NAVI000005 CREATOR: WSER85 LIB JCL JCL JCL JCL STATUS: APR INSTALL DATE: 19971230
DATASET NAMES FOR NICKNAME , LEVEL SOMNODE.DATA.SET.NAVI000005.SHADOW_______________ Shadow Library SOMNODE.DATA.SET.NAVI000005.PRM1_________________ Promotion Library 1 SOMNODE.DATA.SET.NAVI000005.PRM2_________________ Promotion Library 2 SOMNODE.DATA.SET.NAVI000005.PRM3_________________ Promotion Library 3
User Guide
A-13
QUERY DEVELOPMENT STAGING LIBRARIES

CMNQRY05 ---------- QUERY: DEVELOPMENT STAGING LIBRARIES -- ROW 1 TO 10 OF 10 COMMAND ===> SCROLL ===> PAGE Press END command to exit. PACKAGE ID: NAVI000005 STATUS: APR INSTALL DATE: 19971230
LIB DEVELOPMENT STAGING LIBRARY CLS WSER99.CMN.DEMO.#000025.CLS CPY WSER99.CMN.DEMO.#000025.CPY FIX WSER99.CMN.DEMO.#000025.FIX HPN WSER99.CMN.DEMO.#000025.HPN JCL WSER99.CMN.DEMO.#000025.JCL LOD WSER99.CMN.DEMO.#000025.LOD LST WSER99.CMN.DEMO.#000025.LST MPN WSER99.CMN.DEMO.#000025.MPN SKL WSER99.CMN.DEMO.#000025.SKL SRC WSER99.CMN.DEMO.#000025.SRC ******************************* BOTTOM OF DATA *****************************
A-14
Query Production Staging Libraries
QUERY PRODUCTION STAGING LIBRARIES

CMNQRY06 ---------- QUERY: PRODUCTION STAGING LIBRARIES ---- ROW 1 TO 10 OF 10 COMMAND ===> SCROLL ===> PAGE Press END command to exit. PACKAGE ID: NAVI000005 STATUS: DEV INSTALL DATE: 19971230
LIB PRODUCTION STAGING LIBRARY CLS WSER99.CMN.DEMO.#000025.CLS CPY WSER99.CMN.DEMO.#000025.CPY FIX WSER99.CMN.DEMO.#000025.FIX HPN WSER99.CMN.DEMO.#000025.HPN JCL WSER99.CMN.DEMO.#000025.JCL LOD WSER99.CMN.DEMO.#000025.LOD LST WSER99.CMN.DEMO.#000025.LST MPN WSER99.CMN.DEMO.#000025.MPN SKL WSER99.CMN.DEMO.#000025.SKL SRC WSER99.CMN.DEMO.#000025.SRC ******************************* BOTTOM OF DATA ****************************
PRODUCTION LIBRARIES
If your administrator has set up your Change Man environment as an All site, Change Man displays the Query Production Libraries panel (CMNQRY07).
CMNQRY07 ------------ QUERY: COMMAND ===> Press END command to exit. PACKAGE ID: NAVI000005 TYPE STATUS: DEV INSTALL DATE: 19971230 PRODUCTION LIBRARIES -------ROW 1 TO 1 OF 1 SCROLL ===> PAGE
PRODUCTION DATASET NAME TEMPORARY DATASET NAME BACKUP DATASET NAME LOD WSER99.CMN410.PROD.LINKLIB NULLFILE WSER99.CMN410.PROD.LINKLIB ******************************* BOTTOM OF DATA ****************************
Otherwise, Change Man first displays the Remote Site Selection List in order for you to choose a remote site, and then displays the Query Production Libraries panel.
User Guide
A-15
BASELINE LIBRARIES
CMNQRY08 ------------- QUERY: COMMAND ===> Press END command to exit. PACKAGE ID: NAVI000006 LIB SRC SRO LOD CPY MPN HPN CPN SKL MSG LST JCL DBB DBR CCC HHH BASELINE LIBRARY NAME WSER99.CMN410.ASSEMBLE WSER99.CMN410.ASSEMBLE WSER99.CMN410.LINKLIB WSER99.CMN410.COPYLIB WSER99.CMN410.FMAINPAN WSER99.CMN410.FHELPPAN WSER99.CMN410.FCUSTPAN WSER99.CMN410.SKELS WSER99.CMN410.MSGS WSER99.CMN410.LST WSER99.CMN410.CNTL WSER99.CMN410.DBB WSER99.CMN410.CNTL WSER99.CMN410.ASSEMBLE WSER99.CMN410.HHH STATUS: DEV INSTALL DATE: 19971230 BASELINE LIBRARIES --------ROW 1 TO 15 OF 46 SCROLL ===> PAGE
A-16
GLOSSARY
Change Man Application

An application refers to the project or domain of user software being implemented. It is named and defined by the application administrator, and may be a mnemonic. When the application administrator defines an application domain, they set user restrictions for it. See the administrator for these details. When you encounter an application field you can type in the exact name of the application, or you can usually select from a list of applications by typing a pattern, or masking. Possible References: APPL, PROJECT, LOCAL
Change Package
A package refers to a group of changes to user software. There are three levels of change packages: simple, super/complex, and participating. These will be explained later in this section. Packages can be created by any TSO user authorized to use Change Man. They are made up of members of partitioned detests such as JCL, source code, copybooks, etc., which are called components.
Package ID or Name
Each change package that is built with Change Man is assigned a unique ID which is a combination of the application name and a unique number. You should take note of assigned IDs as they are needed to update or review the change package. When typing the package IDs you need to always key in the application mnemonic, but you can truncate the number to only the relevant part. For example:
CGM 000012 may be rendered as CGM 12 , or CGM 012 , or CGM 00012 , or as shown. XYZV130056 type it, as shown. UHRD004061 may be rendered UHRD4061 , or UHRD04061, or as shown. @13 045300 may be rendered @13 45300, or as shown. $B29000246 may be rendered $B29246 , or $B290246 , or $B2900246 , or as shown.
G-1
Glossary
Sometimes this field is editable and you need to key in the change package name or access a list of change packages. At other times it is provided for your reference. Possible References: PKG NAME, PACKAGE NAME, PKG ID, PACKAGE ID
Package Level
The concept of change package levels in Change Man indicates the complexity, and is designated when you create the package. Different levels have different behavior and creation requirements. Simple
A simple change package is a component of a complex or a super change package. This level of change package does not affect any other application, or it does not require them to make any changes to their 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/ 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 within 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.
G-2
Glossary
Combine the approvers of different applications (Not applicable to participating packages within the same application). Participating change packages must be created prior to their being listed as participating in the parent change package. Your packages 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 a package that is enduring and is only deleted if requested by a user. It can be rippled into the baseline library. A temporary package is a package that 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 of normal business hours. Its implementation is subject to the complete Approval List if it is actually 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.
Use this type of change package...

Planned permanent
In this situation...
Schedule and install permanent updates to production software Set up and run special one-time or short-term processing (i.e., conversion, parallel processing, special reports or extractions) Make emergency fixes to production software which will need to be executed for multiple cycles of processing.
Planned temporary
Unplanned permanent
User Guide
G-3
Glossary
Use this type of change package...

Unplanned temporary
In this situation...
Make short term or one-time-only emergency fixes to production software
Installation Job Scheduler

The scheduling system for a package controls the submission of the packages installation batch jobs. This field may already contain a default value if the administrator set the value when setting up Change Man for your site. NOTES The global administrator sets this parameter in part 1 of the Global Parameters Panels (CMNGGP01). You can change this field by typing in the scheduler of your choice. The options are: CMN - Change Man internal scheduling.
When packages use the CMN scheduler, CMN monitors either hold or install. See the Administrator Guide for details on these capabilities. MANUAL - Manually control the submission of installation jobs.
This causes the installation process to begin as soon as all approvals have been obtained. Package installation can be inhibited by holding the last approval or installed immediately by approving the package before the scheduled installation date and time. If the default scheduler is MANUAL, you cannot change this field. OTHER - An external scheduler such as CA7, ADC2, CA-Scheduler, ControlM, etc.
If the default scheduler is OTHER you can change this field to either CMN, or MANUAL. If CMN is the default, you can change this field value to MANUAL. When you specify OTHER when creating packages, the Scheduling Information panel displays after it. Depending on your scheduler, you may need to provide this optional information.
G-4
Glossary
When you specify OTHER when updating packages you must remember to access the Scheduling Information panel (Option 4 ) from the Update Change Package Information panel to change this information.
Install Date
The date in which you want to install your change package.
Component Concepts
A component is a single member of a change package (a change package is a combination of components which make up a unit of change). Usually, it is a member of a library that has been brought into Change Man for the purpose of being modified. The following concepts relate to components.
Component Name
The name of the component can be selected from a list of components (although you may need to provide some qualifying information for the list, such as a library type or application name), or by typing 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)

Change Man keeps track of the components version and modification number by following 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 Change Man, the vv.mm will be 01.01. Each successive stage request (within the same change package) will increment the mm portion (01.02, 01.03 etc.). The next package using the component will cause the vv portion to be incremented (02.01).
Component Library Type

You can select a library type from a list by leaving the field blank, and pressing Enter. The list of available library types is set by your application administrator, and may a be a combination of reserved, like or custom library types. Reserved are component types which are internally defined to Change Man. Like are components which act similar to Change Man's reserved components. Custom are components which have been designed at your site for its unique needs.
User Guide
G-5
Glossary
Your components which require special processing such as those of type source (SRC) may have compile procedures (described below) designated for them. These procedures are usually associated with the language name associated with the component type. Possible References: COMPONENT TYPE, LIBRARY TYPE, TYPE.
Language Name (Language Assumption)

The language name is the programming language associated with a component which requires special processing such as the source (SRC) component. The language name of a component is important because associated with each language are customized predefined compile procedures. This information is particularly important when performing checkout or stage of components. When you checkout new components Change Man lets you either choose a language (from a list of available ones) or use the one that the administrator has designated for it. To use the component defined procedures designated by the application administrator, type the language in the Checkout panel. If the component is not new and has a checkout history, history records on the component's characteristics were saved. Change Man performs the following steps to determine the language name of a component: 1 2 3 4 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 - the application administrator has designated a language for the component type Last Used Language
For either a single component or multiple components, you are prompted for input. Change Man cannot determine the language for the first component in the list; if multiple components are being checked out or staged, Change Man uses the language of the first item in the list for all subsequent components in the list.
G-6
Glossary
If the procedure has been designated with force level 1, then any user wishing to freeze a change package with the selected component MUST perform the last stage request with the designated procedure. Change Man 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 any user wishing to stage the component MUST use the designated compile procedure at all times. When designating a procedure for the component, the application administrator may have used extra compile and/or link options. NOTES See the Change Man Administrator Guide, Version 5.1 for Designated Procedures and Component Level Security.
Compile Procedure
The compile procedure is used for processing special components like source (SRC). Compile procedures are related to the language name of a component. Usually you can 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.) You can use compile procedures and options designated by your application administrator by typing a ?. The appropriate procedure and options are displayed in the other fields. Possible References: PROCEDURE, COMPILE PROC, PROCEDURE NAME
Mode
Many Change Man functions allow you to process a function on-line or in batch mode. When you choose batch mode you are prompted for batch job card information in an additional panel, but only need to fill it in the first time unless there is a change necessary. Possible References: ONLINE BROWSE.
Confirmation Requests
Confirmation requests let you tell Change Man whether or not major operations shall prompt you before running the function. YES indicates that a confirmation is required when doing such things as overlaying a target file when running checkout. A NO in this field indicates to Change Man that the function should be run without a user confirmation.
User Guide
G-7
Glossary
Most of the time this parameter is an all-or-none parameter. You cannot require confirmation for some packages and components and not for others.
Data Set Organization (DSORG)

This indicates a library's type of organization. Following are the usual options: 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
This is not a required field; if left blank, Change Man can determine the DSORG. Possible References: ORGANIZATION, DSORG
Remote Site
Often when using Change Man you need to indicate what remote sites are affected by a function. If you do not have remote sites you can ignore this field, or more likely, it does not appear. You may be prompted to provide remote site information when you are creating change packages and indicating where the package is to be installed.
ID or TSO ID
TSO USERID that performed a function. Possible References: TSOID
G-8
INDEX
A
accessing online error messages, short and long 2-11 action requested, field description 9-4, 10-5 activity log about 19-1 producing a report 19-3 reviewing 19-3 Activity Log Entries panel (CMNLOGDS) 19-3 affected applications, about 4-7 and/or, field description 19-19 application about G-1 local, about G-1 application, field description 3-3, 4-3, 19-8, 19-18, 20-13 approval entity name, field description 12-3 Approval List panel (CMNAPPLS) 12-5, A-5 Approve Package Parameters panel (CMNAPPRV) 12-2 Approve/Reject Options panel (CMNAPPOP) 12-5 approving frozen packages 1-7 approving or rejecting packages 12-2 as member name, field description 19-12 ASA carriage control 7-6 audit about 1-5, 7-1 full 7-9, 7-11, 7-13, 7-16, 7-20, 7-22, 7-27, 7-29, 7-33 pre- 7-10, 7-13, 7-15, 7-18, 7-19, 7-25, 7-32, 7-34 Audit Change Package panel (CMNAUDIT) 7-4 audit RC, field description 20-7 Audit Report about 7-38 evaluating 7-47
B
backing up 1-9 backout about 1-10 from remote site 14-3 package out of production 14-1 Backout Change Package panel (CMNBKOUT) 14-2 Backout Reasons panel (CMNBKRSN) 14-2 baseline by site 5-5 kept for sites at a DP/P shop 5-5 ripple 7-48 baseline browse/print facility 19-6 Baseline Browse/Print Facility panel (CMNBRWB0) 19-6 batch checkout, unlock components 5-7 mode G-7 stage 6-10 Browse Activity Log panel (CMNLOGE2) 19-4 Browse Activity Log panel (CMNLOGEX) 19-2 Browse Compressed Listing panel (CMNBLST0) 19-13 browsing activity log 19-1 compressed listings 19-1, 19-13 editing components 19-11 global notification facility 19-15
C
case sensitive, field description 19-9 case sensitive?, field description 19-19 Change Man about 1-1 online error messages, short and long 2-11 change package installation instructions 3-7
I-1
Index
Change Package List panel (CMNLIST3) 15-5 change packages, A-E about G-1 approving 12-1 backing out of production 14-1 deleting 17-5 emergency G-3 change packages, creating about 3-1 change packages, demoting from a local system 9-1 from a remote system 10-1 change packages, F-Q freezing 8-1 job scheduler G-4 level G-2 permanent G-3 planned G-3 querying 20-1 change packages, promoting to a local system 9-1 to a remote system 10-1 change packages, R-Z rejecting 12-1 remote promotion 10-2 remote site 3-12 reverting 13-1 scheduling dependencies 3-8 single site 3-11 status G-3 temporary G-3 undeleting 17-5 unplanned G-3 change packages, updating about 4-1 affected applications 4-7 complex 4-8 control information 4-2 description 4-4 installation information 4-8 installation instructions 4-5 remote site 4-9 scheduling dependencies 4-6 single site 4-10 site information 4-8 super 4-8 super/complex package status 4-12 changed from/to date, field description 6-17 changed, column description 7-40, 7-42, 7-43, 7-44 check out to, field description 5-6 checkout about 1-3
baseline by site remote selection list displayed 5-5 options 5-1 restrictions 5-1 rules 5-1 checkout components about 5-1 from baseline 5-3 from promotion 5-3 checkout library dsorg, field description 5-6 checkout library type, field description 5-5 checkout mode, field description 5-6 Checkout Options panel (CMNMCKOT) 5-3 checkout package driven list 5-7 ID list 5-7 ID, field description 5-5 checkout panel field descriptions check out to 5-6 checkout mode 5-6 component name 5-5 confirm request 5-6 language 5-5 library dsorg 5-6 library type 5-5 lock component 5-7 package ID 5-5 personal library 5-6 source library 5-5 CMN30 8-3 CMN37 8-3 CMN55 8-3 CMN57 8-3 CMNASIST 20-11 see also impact analysis CMNBAT10 16-6 CMNPMXJB CMN30 skeleton job 8-3 CMN37 skeleton job 8-3 CMN55 skeleton job 8-3 CMN57 skeleton job 8-3 CMNPMXJB module 8-2 CMNPRM05 9-9 CMNSAS10 16-3 column descriptions install date 3-11, 3-13, 4-10, 4-11 time from 3-12, 3-13, 4-10, 4-11 time to 3-12, 3-13, 4-10, 4-11 LCMD 4-9, 4-11
I-2
Index
phone numbers 3-13, 4-10, 4-11 predecessor 3-9 primary/backup contacts 3-12, 3-13, 4-10, 4-11 remote site 3-13, 4-9 successor 3-9 Common Compoents panel (CMNRPM06) 10-16 common components checking for at a remote site 10-15 Common Components panel (CMNPRM08) 9-11 Common Components panel (CMNRPM06) 10-16 compare mode, field description 18-2 Compare panel (CMNCOMP1) 18-2 comparison report, field description 6-18 compile procedure, about G-7 compile parms, field description 6-9, 11-4 compile procedure, field description 6-9, 6-17, 11-4 complex package about 4-8 complex/super packages about G-2 component history record, mass stage 6-8 Component List panel (CMNRPM05) 10-9 component name G-5 component name, field description 5-5, 11-2, 18-3, 19-8, 20-12 Component Remote Promotion Status for Component panel (CMNQRY28) A-11 component status, field description 6-17 component type, field description 20-12 component types about G-5 components about G-5 checking out 5-1 common, checking for at a remote site 10-15 compile procedure G-7 concepts G-5 language name G-6 library type G-5 locking 5-7 modification number (MM) G-5 querying 20-1 remote promotion 10-2 version (VV) G-5 Components List panel (CMNPRM05) 9-9 Components List Parameters panel (CMNSTG12) 6-17 components to scan, field description 19-19
compress staging libraries 17-1 Compress Staging Libraries (CMNCPRSS) 17-1 Compress Staging Libraries panel 17-1 Compress Staging Libraries panel (CMNCPRSS) 17-1 compressed listings, browsing 19-1, 19-13 configuring remote promotion 10-1 confirm request, field description 5-6, 6-4, 6-18 confirmation requests G-7 contingency, field description 3-7, 4-6 Copy to Dataset/Member Name Information panel 19-12 Copy To Dataset/Member Name Information panel (CMNBRWB9) 19-12 Copy to Dataset/Member Name Information panel (CMNBRWB9) 19-12 CPY (copy) Audit Report section column descriptions changed 7-40, 7-42, 7-43, 7-44 created 7-40, 7-42, 7-45, 7-48 dept 7-40, 7-44, 7-45 init 7-40, 7-44 name 7-40, 7-42, 7-45 package 7-40, 7-42, 7-44, 7-45 size 7-40, 7-42, 7-44 TSO-ID 7-40, 7-42, 7-44, 7-45 VV.MM 7-40, 7-42, 7-45 Create On Site Information (CMNCRT06) 3-11 Create Package Description (CMNCRT02) 3-5 Create Package Description panel (CMNCRT02) 3-5 created, column description 7-40, 7-42, 7-45, 7-48 creator, field description 10-3, 20-7 creators TSO-ID, field description 15-2, 20-3 current promotion level, field description 9-3, 10-5
D
data set organization G-8 data string, field description 19-9, 19-19 dataset name, field description 6-4, 6-9 date, field description 10-6 DB2 pre-compile, field description 6-10, 11-4 Delete Options (CMNDELT0) 17-6 Delete Options panel (CMNDELT0) 17-6 deleting packages about 17-5 canceling requests 17-6
User Guide
I-3
Index
considerations 17-5 setting up memo delete 17-5 Demote Options panel (CMNPRM04) 9-8 Demote Options panel (CMNRPM04) 10-13 Demote Options panels (CMNPRM10) 9-7 demoting components from packages 9-10 from a remote site functional hierarchies 10-11 packages batch 9-7 online 9-7 department number 7-40, 7-44, 7-45 department, field description 3-3, 4-3, 12-3, 15-2, 20-3 dependencies, field description 19-18 dept, column description 7-40, 7-44, 7-45 designated compile procedure G-7 displacement, field description 19-19 Distributed Programming 7-58 distribution to remote sites 1-10 DSORG G-8
E
editing components in browse mode evaluating Audit Reports 7-47 Extended Search Criteria panel (CMNQRY01) 15-4, 20-5 19-11
F
field descriptions package type 12-4 field descriptions, A-B action requested 9-4, 10-5 and/or 19-19 application 3-3, 4-3, 19-8, 19-18, 20-13 approval entity name 12-3 as member name 19-12 audit RC 20-7 field descriptions, C-D case sensitive 19-9 case sensitive? 19-19 changed from/to date 6-17 check out to 5-6 checkout mode 5-6 compare mode 18-2 comparison report 6-18
compile parms 6-9, 11-4 compile procedure 6-9, 6-17, 11-4 component name 5-5, 11-2, 18-3, 19-8, 20-12 component status 6-17 component type 20-12 components to scan 19-19 confirm request 5-6, 6-4, 6-18 contingency 3-7, 4-6 creator 10-3, 20-7 creators TSO-ID 15-2, 20-3 current promotion level 9-3, 10-5 data string 19-9, 19-19 dataset name 6-4, 6-9 date 10-6 DB2 pre-compile 6-10, 11-4 department 3-3, 4-3, 12-3, 15-2, 20-3 dependencies 19-18 displacement 19-19 field descriptions, E-J forced demotion from prior promotion sites (remote, local) 10-4 from/to column 19-9 from/to creation date 12-4, 15-3, 20-4 from/to date 19-2 from/to install date 12-4, 15-3, 20-4 ID 10-6 input library type 11-7 install date 10-3, 20-7 installation instructions 3-8, 4-6 job statement information 11-4 job statement information for batch compare 18-3 job statement information if disposition is PD or PK 18-4 field descriptions, L-M language 5-5, 6-4, 11-2 LCT member list 11-7 level to check 9-4, 10-5 library dsorg 5-6 library level 11-3, 19-8 library org 19-12 library type 5-5, 6-4, 18-3, 19-8, 19-18 link edit parms 6-10, 11-4 list members only 19-18 lock component 5-7 maximum promotion level 9-3, 10-5 member 6-3 member list scan 19-8 member name 11-7 MOD/CNT 10-6 field descriptions, N-O notified user ID 12-3 online browse 19-2 online or batch 9-4 other options 6-10, 11-4
I-4
Index
other parameters 12-4, 15-3, 20-4 field descriptions, P-Q package ID 5-5, 11-2, 12-3, 15-2, 20-3, 20-7 package level 3-3, 4-3, 15-3, 20-3 package name 18-2 package status 15-2, 20-3 package time span 3-4, 4-4, 12-4, 15-3, 20-4 package title 3-3, 4-3 package type 3-4, 4-3, 15-3, 20-4 panel options 11-2, 18-2, 19-8 personal library 5-6 promotion 10-6 prompt for report disposition 18-3 field descriptions, R-S records to select 19-9, 19-18 relationship 20-13 relationship to 20-13 relink from 11-7 remote 10-6 remote history 10-6 remote promotion site 10-5 remote site affected 12-4, 15-3, 20-3 remote site name 10-3 report dataset name 18-4 report disposition 18-4 request 10-9 requesters name 3-3, 4-3 requesters phone 3-3, 4-3 scan mode 19-18 scheduler 3-7, 4-6 short or long display 6-18 source library 5-5, 18-3 source library type 11-2 stage mode 6-4 stage name 6-4 staged name 6-9 status 10-3, 10-9, 20-7 suppress history 11-4 suppress messages 6-4, 6-18 field descriptions, T-Z target library type 11-7 time 10-6 to dataset 19-12 TSOID 6-17 work request ID 3-3, 4-3, 12-3, 15-2, 20-3 forced demotion from prior promotion sites (remote, local), field description 10-4 freeze time CMN30 skeleton job 8-3 CMN37 skeleton job 8-3 CMN55 skeleton job 8-3 CMN57 skeleton job 8-3
CMNPMXJB 8-2 freeze in progress indicator 8-8 Freeze Options panel (CMNFRZ01) 8-4 freezing packages about 1-5, 8-1 batch 8-5 online 8-4 reset indicator 8-8 from/to column, field description 19-9 creation date, field description 12-4, 15-3, 20-4 date, field description 19-2 install date, field description 12-4, 15-3, 20-4 frozen packages, approving 1-7 full audit 7-9, 7-11, 7-13, 7-16, 7-20, 7-22, 7-27, 7-29, 7-33 functional hierarchies, remote demotion 10-11
G
global notification facility, browsing 19-15 Global Notification Report Disposition panel (CMNOT00) 19-16
I
ID, field description 10-6 impact analysis 1-12, 19-17 see also CMNASIST impact analysis data, querying 20-11 Impact Analysis of Components panel (CMNIMPMP) 20-12 informational code 7-48 init, column description 7-40, 7-44 input library type, field description 11-7 install date column description 3-11, 3-13, 4-10, 4-11 field description 10-3, 20-7 time from, column description 3-12, 3-13, 4-10, 4-11 to, column description 3-12, 3-13, 4-10, 4-11 installation about 1-8 instructions about 3-7, 4-5 field description 3-8, 4-6 ISPF
User Guide
I-5
Index
statistics
7-38
J
job statement information field description 11-4 for batch compare, field description 18-3 if disposition is PD or PK, field description
18-4
about 17-5 Memo Delete Change Package (CMNDELT1) menus Query Option (CMNQMENU) 20-1 MOD/CNT, field description 10-6 mode, batch, online G-7 module, member, component G-5
17-6
L
language field description 5-5, 6-4, 11-2 name G-6 LCMD, column description 4-9, 4-11 LCT member list, field description 11-7 level to check, field description 9-4, 10-5 library data set organization 5-6 level, field description 11-3, 19-8 org, field description 19-12 personal 5-6 type about G-5 component type G-5 type, field description 6-4, 18-3, 19-8, 19-18 link edit parms, field description 6-10, 11-4 list members only, field description 19-18 of components, package driven 5-7 Local or Remote Promotion panel (CMNSLRPM) 9-2, 10-11 lock component, field description 5-7
N
name column description 7-40, 7-42, 7-45 notified user ID, field description 12-3
O
online browse, field description 19-2 error messages, short and long, accessing 2-11 mode G-7 or batch, field description 9-4 organization, data set, DSORG G-8 other options, field description 6-10, 11-4 parameters, field description 12-4, 15-3, 20-4 out-of-synch informational code 7-48
P
package column description 7-40, 7-42, 7-44, 7-45 ID G-1 field description 11-2, 12-3, 15-2, 20-3, 20-7 information categories promotion libraries option 20-8 remote promotion history option 20-8 remote promotion libraries option 20-8 level about G-1 field description 3-3, 4-3, 15-3, 20-3 list about 15-1 checkout 5-7 options 15-5 master 7-49 name about G-1 field description 18-2
M
masking package list about 2-5 packages 2-5 mass stage 6-8 component history record 6-8 maximum promotion level, field description 10-5 member component G-5 field description 6-3 list scan, field description 19-8 name, field description 11-7 memo delete
9-3,
I-6
Index
search 2-5 status G-3 field description 15-2, 20-3 time span, field description 3-4, 4-4, 12-4, 15-3, 20-4 title, field description 3-3, 4-3 type G-3 field description 3-4, 4-3, 12-4, 15-3, 20-4 relationships G-3 Package Description panel (CMNPGNL2) A-2 package ID, field description 5-5 Package in Batch panel (CMNFRZ02) 8-5 Package Information Categories panel (CMNQRY03) 20-6 Package List Parameters panel (CMNLIST0) 15-1 Package Promotion History panel (CMNQRY23) A-9 packages change G-1 freezing 1-5 frozen, approving 1-7 querying 20-1 panel 17-1 options, field description 11-2, 18-2, 19-8 Utility Baseline Selections (CMNUTL01) 17-3 panels Activity Log Entries (CMNLOGDS) 19-3 Approval List (CMNAPPLS) 12-5 Approval List panel (CMNAPPLS) A-5 Approve Package Parameters (CMNAPPRV) 12-2 Approve/Reject Options (CMNAPPOP) 12-5 Audit Change Package (CMNAUDIT) 7-4 Backout Change Package (CMNBKOUT) 14-2 Backout Reasons (CMNBKRSN) 14-2 Baseline Browse/Print Facility (CMNBRWB0) 19-6 Browse Activity Log (CMNLOGE2) 19-4 Browse Activity Log (CMNLOGEX) 19-2 Browse Compressed Listing (CMNBLST0) 19-13 Change Package List (CMNLIST3) 15-5 Checkout Options (CMNMCKOT) 5-3 Commnon Components (CMNPRM08) 9-11 Common Components (CMNRPM06) 10-16 Compare (CMNCOMP1) 18-2 Compare panel (CMNCOMP1) 18-2 Component List panel (CMNRPM05) 10-9 Component Remote Promotion Status for Component (CMNQRY28) A-11 Components List (CMNPRM05) 9-9 Components List Parameters (CMNSTG12) 6-17
Compress Staging Libraries (CMNCPRSS) 17-1 Copy To Dataset/Member Name Information (CMNBRWB9) 19-12 Copy to Dataset/Member Name Information (CMNBRWB9) 19-12 Create On Site Information (CMNCRT06) 3-11 Create Package Description (CMNCRT02) 3-5 Delete Options (CMNDELT0) 17-6 Demote Options (CMNPRM04) 9-8 Demote Options (CMNPRM10) 9-7 Demote Options (CMNRPM04) 10-13 Extended Search Criteria (CMNQRY01) 15-4, 20-5 Freeze Options ( CMNFRZ01) 8-4 Global Notification Report Disposition (CMNOT00) 19-16 Impact Analysis of Components (CMNIMPMP) 20-12 Local or Remote Promotion (CMNSLRPM) 9-2, 10-11 Memo Delete Change Package (CMNDELT1) 17-6 Package Description (CMNPGNL2) A-2 Package in Batch (CMNFRZ02) 8-5 Package Information Categories (CMNQRY03) 20-6 Package List Parameters (CMNLIST0) 15-1 Package Promotion History (CMNQRY23) A-9 Print/Copy Job Card Information (CMNBRWB2) 19-12 Promote Change Package (CMNPRM00) 9-3 Promote Change Package panel (CMNPRM01) 9-3 Promote Options (CMNPRM02) 9-6 Promote Options (CMNPRM09) 9-5 Promote Options (CMNRPM03) 10-7 Query Backout Reasons List (CMNQRY13) A-9 Query Baseline Libraries (CMNQRY08) 20-9, A-16 Query Component List (CMNQCMP2) 20-10 Query Component Parameters (CMNQCCMP1) 20-9 Query Control Information (CMNQRY10) A-1 Query Development Staging Libraries (CMNQRY05) A-14 Query Options (CMNQMENU) 20-1 Query Package List (CMNQRY02) 20-5 Query Packages Parameters (CMNQRY00) 20-2 Query Participating Packages (CMNQRY11) A-8 Query Production Libraries (CMNQRY07) A-15 Query Production Staging Libraries (CMNQRY06) A-15 Query Rename/Scratch List (CMNQRY12) A-5 Query Site Activities Date and Time (CMNQRY14) A-6
User Guide
I-7
Index
Query Status Start Date and Time (CMNQRY04) A-8 Recompile Source (CMNRCMP0) 11-2 Remote Promotion Level List 10-8 Remote Promotion List Part 1 or 3 (CMNQRY29) A-12 Remote Promotion Part 2 or 3 (CMNQRY30) A-13 Remote Promotion Selection List (CMNQRY26) A-10 Remote Site Information (CMNPRSTI) 4-9, A-6 Restore Memo Deleted Package (CMNDELT3) 17-7 Restore Memo Deleted Packages (CMNDELT3) 17-7 Revert Change Package (CMNREV00) 13-2 Revert Reasons (CMNREVRS) 13-2, A-9 Revert Reasons panel (CMNREVRS) A-8 Source to Load Relationship (CMNQRY21) A-5 Source to Load Relationship (CMNSR2LD) 6-15 Specify Listing Disposition (CMNBLST2) 19-15 Specify Report Disposition (CMNCDISP) 18-4 Stage Components (CMNSTG01) 6-15, A-2 Stage from Development (CMNSTG02) 6-3 Stage Mass Compile and Link Edit (CMNSTG05) 6-12 Stage Options (CMNSTG00) 6-2 Stage Other Components (CMNSTG09) 6-13 Unfreeze/Refreeze Component (CMNUNFRZ) 8-7 Update Complex/Super Information (CMNPGNL6) 4-8 Update Custom Component List (CMNCUSTM) A-7 Update Custom Component List panel (CMNCUSTM) A-7 Update Installation Instructions (CMNPGNL3) 4-5 Update Package Description (CMNPGNL2) 4-4 Update Scheduling Dependencies (CMNPGNL4) 4-6 Update Site Information (CMNONSTE) 4-11, A-6 Updqate Affected Applications (CMNPGNL5) 4-7 Utility Baseline Selection (CMNTL01) 17-3 Utility Change Package Driven List (CMNUTL03) 17-5 Utility Rename/Scratch Options (CMNUTL00) 17-2 Valid Package List Commands (CMNLIST6) 15-8 participating packages G-2 personal library, field description 5-6 phone numbers, column description 3-13, 4-10, 4-11
pre-audit 7-10, 7-13, 7-15, 7-18, 7-19, 7-25, 7-32, 7-34 predecessor column description 3-9 primary/backup contacts, column description 3-12, 3-13, 4-10, 4-11 Print/Copy Job Card Information panel (CMNBRWB2) 19-12 printer spacing, ASA carriage control 7-6 procedure compile G-7 name G-7 process mode G-7 producing reports about 16-1 project, application, about G-1 Promote Change Package panel (CMNPRM00) 9-3 Promote Change Package panel (CMNPRM01) 9-3 Promote Options panel (CMNPRM02) 9-6 Promote Options panel (CMNPRM09) 9-5 Promote Options panel (CMNRPM03) 10-7 promoting change packages to a remote site 10-2 components 1-6 components to a remote site 10-2 packages about 1-6 batch 9-5 checking for common components 9-11 online 9-4 to a local system 9-1 to a remote site 10-2 to a remote system 10-1 to a remote system 10-1 promotion field description 10-6 libraries package information categories 20-8 prompt for report disposition, field description 18-3
Q
Query Backout Reasons List panel (CMNQRY13) A-9 Query Baseline Libraries panel (CMNQRY08) 20-9, A-16 Query Component List panel (CMNQCMP2) 20-10 Query Component Parameters panel (CMNQCMP1) 20-9
I-8
Index
Query Control Information panel (CMNQRY10) A-1 Query Development Staging Libraries panel (CMNQRY05) A-14 Query Options panel (CMNQMENU) 20-1 Query Package List panel (CMNQRY02) 20-5 Query Packages Parameters panel (CMNQRY00) 20-2 Query Participating Packages panel (CMNQRY11) A-8 Query Production Libraries panel (CMNQRY07) A-15 Query Production Staging Libraries panel (CMNQRY06) A-15 Query Rename/Scratch List panel (CMNQRY12) A-5 Query Site Activities Date and Time panel (CMNQRY14) A-6 Query Status Start Date and Time panel (CMNQRY04) A-8 querying components 20-1 packages 20-1
categories 20-8 packages, checking for common components 10-15 site, field description 10-5 selection list displayed at checkout 5-5 site affected, field description 12-4, 15-3, 20-3 column description 3-13, 4-9 common component checking 10-15 name, field description 10-3 promoting change packages to 10-2 promoting components to 10-2 sites backing out packages 14-3 distribution 1-10 installing packages 3-12, 4-9 new package 3-12 update package 4-9 Remote Promotion Level List panel (CMNRPM07) 10-8 Remote Promotion List Part 1 or 3 panel (CMNQRY29) A-12 Remote Promotion Part 2 or 3 panel (CMNQRY30) A-13 Remote Promotion Selection List panel (CMNQRY26) A-10 Remote Site Information panel (CMNPRSTI) 4-9, A-6 renaming packages 17-2 report dataset name, field description 18-4 disposition, field description 18-4 reports audit, see audit report producing 16-1 recommendation summary 7-46 request, field description 10-9 requesters name, field description 3-3, 4-3 phone, field description 3-3, 4-3 Restore Memo Deleted Package (CMNDELT3) 17-7 Restore Memo Deleted Packages (CMNDELT3) 17-7 Revert Change Package panel (CMNREV00) 13-2 Revert Reasons panel (CMNREVRS) 13-2, A-8, A-9
R
recommendation summary report 7-46 Recompile Source panel (CMNRCMP0) 11-2 records to select, field description 19-9, 19-18 refreezing components 8-7 relationship to, field description 20-13 relationship, field description 20-13 relink from, field description 11-7 relinking load components 11-5 remote demotion change packages 10-11 components of a package 10-11 functional hierarchies 10-11 field description 10-6 history, field description 10-6 promotion change packages 10-2 components of a package 10-2 history, package information categories 20-8 how administrators can configure 10-1 libraries, package information
User Guide
I-9
Index
S
SAS reports 16-3 scan mode, field description 19-18 scanning a library 19-17 scheduler, field description 3-7, 4-6 scheduling dependencies 3-8, 4-6 scratching packages 17-2 searching for packages 2-5 SERPANEL 19-20 short or long display, field description 6-18 simple packages about G-2 single site, installing packages 3-11, 4-10 size, column description 7-40, 7-42, 7-44 source library field description 18-3 type, field description 11-2 source library, field description 5-5 Source to Load Relationship panel (CMNQRY21) A-5 Source to Load Relationship panel (CMNSR2LD) 6-15 Specify Listing Dispositon panel (CMNBLST2) 19-15 Specify Report Disposition panel (CMNCDISP) 18-4 stage mass stage 6-8 mode, field description 6-4 name, field description 6-4 Stage Components panel (CMNSTG01) 6-15, A-2 Stage from Development panel (CMNSTG02) 6-3 Stage Mass Compile and Link Edit panel (CMNSTG05) 6-12 Stage Options panel (CMNSTG00) 6-2 Stage Other Components panel (CMNSTG09) 6-13 staged name, field description 6-9 staging about 1-3 administration parameters 6-1 compile and link-edit 6-8 component list 6-7 components 6-1 from development 6-3 from packages 6-13
LCT member 7-53 libraries compress 17-1 inspection 7-1 libraries, compress 17-1 other type components 6-13 user options 6-11 using package parameters 6-16 statistics, ISPF 7-38 status change packages G-3 field description 10-3, 10-9, 20-7 successor, column description 3-9 summary reports recommendation 7-46 super packages about 4-8 super/complex packages G-2 suppress history, field description 11-4 messages, field description 6-4, 6-18 SYSLIB search order 7-53
T
target library type, field description 11-7 temporary change cycle (TCC) about 1-10 time, field description 10-6 to dataset, field description 19-12 TSO-ID, column description 7-40, 7-42, 7-44, 7-45 TSOID, field description 6-17 type component library G-5
U
undeleting packages 17-5 Unfreeze/Refreeze Component panel (CMNUNFRZ) 8-7 unfreezing components 8-7 unlocking components 5-7 Update Complex/Super Information panel (CMNPGNL6) 4-8 Update Custom Component List (CMNCUSTM) A-7
I-10
Index
Update Custom Component List panel (CMNCUSTM) A-7 Update Installation Instructions panel (CMNPGNL3) 4-5 Update Package Description panel (CMNPGNL2) 4-4 Update Scheduling Dependencies panel (CMNPGNL4) 4-6 Update Site Information panel (CMNONSTE) 4-11, A-6 updating change package information 4-1 Updqate Affected Applications panel (CMNPGNL5) 4-7 utility requests about 17-2 activating from packages 17-4 creating from baseline 17-3 deleting from packages 17-4 Utility Baseline Selection panel (CMNTL01) 17-3 Utility Baseline Selections panel (CMNUTL01) 17-3 Utility Change Package Driven List panel (CMNUTL03) 17-5 Utility Rename/Scratch Options panel (CMNUTL00) 17-2
V
Valid Package List Commands panel (CMNLIST6) 15-8 VV.MM, column description 7-40, 7-42, 7-45
W
work request ID, field description 3-3, 4-3, 12-3, 15-2, 20-3
User Guide
I-11

ChangeManUserGuide-Version5 (1) 1

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

ChangeManUserGuide-Version5 (1) 1

Diunggah oleh

Hak Cipta:

Format Tersedia

CHANGE MAN

What is Change Man?

Accessing Change Man and Navigating Panels

Creating a Change Package

Updating Change Package Information

Change Man Version 5.1

Checking Out a Component

Change Man Version 5.1

Promoting to a Local System

9-7 9-8 9-8 9-8 9-9 9-10 9-11

Promoting to a Remote System

Recompiling and Relinking Components

Approving or Rejecting a Package

Change Man Version 5.1

Backing a Package Out of Production

Using Package List for Change Man Functions

Defining and Generating Change Man Reports

Comparing Staging Libraries

Browsing and Printing Package Information

Querying Packages and Components

Change Man Version 5.1

20-9 20-11 20-12 20-15 20-16

Package Category Panels

Change Man Version 5.1

WHAT IS CHANGE MAN?

FEATURES OF CHANGE MAN

1 What is Change Man?

THE CHANGE MAN LIFE CYCLE

Change Man Version 5.1

Inside Change Man Development

INSIDE CHANGE MAN DEVELOPMENT

The Checkout Process

The Staging Process

1 What is Change Man?

Change Man Version 5.1

Inside Change Man Development

Enables User to do the Following:

1 What is Change Man?

Promoting Packages and Components

Change Man Version 5.1

Inside Change Man Development

1 What is Change Man?

Change Man Version 5.1

Inside Change Man Development

1 What is Change Man?

Backing Out Packages or Components

Temporary Change Cycle

Distribution to Remote Sites

Change Man Version 5.1

Change Man Library Environment

Distributing and Installing Components at Remote Sites

CHANGE MAN LIBRARY ENVIRONMENT

1 What is Change Man?

In batch Online Concurrently with other developers

Change Man Version 5.1

Change Man Library Environment

1 What is Change Man?

Recompile and Relink

Change Man Version 5.1

Change Man Library Environment

1 What is Change Man?

BASELINE LIBRARIES AND DELTA DECKS

Masking (or Pattern) * or * * A* AB A * 1 ABCD1* ABCD1 ABCD10 ABCD*10