Change Man

Change Man / MVS
User Training Guide (Release 4.1.6)
500 Airport Blvd., Suite 200 Burlingame, CA 94010 Telephone 650-696-1800 Fax 650-696-1849
Change Man and Change Man/MVS are registered trademarks of SERENA International.
Copyright 1997, 1998 SERENA Software International, Inc. All Rights Reserved.
This document is protected by the copyright laws of the United States and other countries. No part of this document may be reproduced, in any way, without the express consent of SERENA International. SERENA International reserves the right to revise this document without obligation to notify any licensee of such revision. CA-7 and CA-Librarian are registered trademarks of Computer Associates.
DB2 is a registered trademark of International Business Machines.
User Training Guide
Table of Contents
Preface.............................................................................................................................9
Corporate Background................................................................................................................. 9 User Training Guide Content....................................................................................................... 12 Change Man Course Offerings .................................................................................................... 13 Change Man for New Users................................................................................................... 15 Change Man for Experienced Users ...................................................................................... 16
Introduction....................................................................................................................17
What Is Change Man ................................................................................................................... 17 The Change Man ALLSITE Change Package Life Cycle ....................................................... 19 Change Man Library Environment (ALLSITE - Data Flow Diagram) ........................................ 21 Change Man Library Environment (DEVPROD Site - Data Flow Diagram) .............................. 22 Change Man Terminology ........................................................................................................... 24 Accessing Change Man ............................................................................................................... 26 Change Man Panel and Menu Navigation ................................................................................... 28
Primary Option Menu + Build Options.......................................................................33

Primary Option Menu + Build Options Overview....................................................................... 33 PRIMARY OPTION MENU Panel.......................................................................................... 33 NOTIFY Panel ......................................................................................................................... 34 CHANGE MAN TUTORIAL Panel......................................................................................... 36 BUILD OPTIONS Panel .......................................................................................................... 37 PLANNED INSTALLATION CALENDAR - Panel .................................................................. 38
Create ..............................................................................................................................39
Create Overview .......................................................................................................................... 39 CREATE: CREATE A NEW PACKAGE - Panel ...................................................................... 41 CREATE: PACKAGE DESCRIPTION - Panel.......................................................................... 45 CREATE: INSTALLATION INSTRUCTIONS - Panel............................................................. 47 CREATE: ON SITE INFORMATION - Panel ........................................................................... 49 CREATE: AFFECTED APPLICATIONS - Panel ...................................................................... 51 CREATE: COMPLEX / SUPER INFORMATION - Panel ........................................................ 53 Commonly Asked Questions..................................................................................................... 55 Exercises for Create .................................................................................................................. 56
Update .............................................................................................................................57
Update Overview......................................................................................................................... 57 UPDATE: PACKAGE INFORMATION Panel...................................................................... 57 UPDATE: CONTROL INFORMATION Panel..................................................................... 57 UPDATE: PACKAGE DESCRIPTION - Panel......................................................................... 58 UPDATE: INSTALLATION INSTRUCTIONS - Panel........................................................... 59 UPDATE: SCHEDULING DEPENDENCIES - Panel .............................................................. 59 UPDATE: AFFECTED APPLICATIONS - Panel.................................................................... 60 UPDATE: COMPLEX/SUPER INFORMATION - Panel........................................................ 60 UPDATE: SITE INFORMATION Panel ............................................................................... 61
Utility...............................................................................................................................63
Utility Overview .......................................................................................................................... 63 UTILITY: RENAME / SCRATCH OPTIONS Panel ............................................................. 63 Table of Contents
User Training Guide
UTILITY: BASELINE SELECTIONS - Panel ......................................................................... 64 Commonly Asked Questions..................................................................................................... 66 Exercises for Utility .................................................................................................................. 67
Checkout .........................................................................................................................69
Checkout Overview ..................................................................................................................... 69 CHECKOUT OPTIONS Panel................................................................................................. 70 CHECKOUT - Panel ................................................................................................................... 70 CHECKOUT: PACKAGE COMPONENTS Panel.................................................................. 74 Commonly Asked Questions..................................................................................................... 77 Exercises for Checkout ............................................................................................................. 77
Stage ................................................................................................................................79
Stage Overview............................................................................................................................ 79 STAGE OPTIONS - Panel .......................................................................................................... 80 STAGE: FROM DEVELOPMENT Panel................................................................................ 81 STAGE: PACKAGE COMPONENTS -Panel ............................................................................ 84 STAGE: COMPILE AND LINK - Panel.................................................................................. 88 COMPONENT LIST PARAMETERS Panel........................................................................... 92 Commonly Asked Questions..................................................................................................... 95 Exercises For Staging ............................................................................................................... 95
Listing .............................................................................................................................97
Listing Overview ......................................................................................................................... 97 BROWSE COMPRESSED LISTINGS - Panel........................................................................... 97
Audit................................................................................................................................103
Audit Overview ........................................................................................................................... 103 AUDIT CHANGE PACKAGE - Panel ....................................................................................... 105 Out-of-synch Conditions.............................................................................................................. 111 Commonly Asked Questions................................................................................................... 114 Exercises for Audit ................................................................................................................. 115
Freeze ..............................................................................................................................117
Freeze Overview.......................................................................................................................... 117 FREEZE OPTIONS Panel........................................................................................................ 117 UNFREEZE / REFREEZE Package Panel ............................................................................... 120 Exercises for Freeze................................................................................................................ 121
Promote ...........................................................................................................................123
Promote/Demote Overview ......................................................................................................... 123 PROMOTE CHANGE PACKAGE Panel ................................................................................ 123 PROMOTE OPTIONS -Panel ................................................................................................ 125 DEMOTE OPTIONS Panel...................................................................................................... 126 COMMON COMPONENTS Panel ...................................................................................... 127 Exercises for Promote/Demote ............................................................................................... 128
Approve...........................................................................................................................129
Approve Overview ...................................................................................................................... 129 APPROVE PACKAGE PARAMETERS - Panel........................................................................ 129 APPROVE/REJECT OPTIONS - Panel...................................................................................... 131 PACKAGE INFORMATION CATEGORIES - Panel................................................................ 132 APPROVAL LIST Panel.......................................................................................................... 133
Table of Contents
User Training Guide
REJECT REASONS - Panel....................................................................................................... 134 Exercises for Approval ........................................................................................................... 136
List...................................................................................................................................137
List Overview .............................................................................................................................. 137 PACKAGE LIST PARAMETERS - Panel.................................................................................. 138 CHANGE PACKAGE LIST - Panel ........................................................................................... 140 PACKAGE LIST OPTIONS - Panel........................................................................................... 142 Exercises for List .................................................................................................................... 143
Delete...............................................................................................................................145
Delete Overview .......................................................................................................................... 145 DELETE OPTIONS Panel ....................................................................................................... 145 MEMO DELETE CHANGE PACKAGE Panel....................................................................... 146 RESTORE MEMO DELETED PACKAGES Panel ................................................................ 148
Revert ..............................................................................................................................151
Revert Overview.......................................................................................................................... 151 REVERT CHANGE PACKAGE - Panel .................................................................................... 151 REVERT REASONS- Panel ....................................................................................................... 152
Backout ...........................................................................................................................155
Backout Overview ....................................................................................................................... 155 BACKOUT CHANGE PACKAGE Panel................................................................................ 155 BACKOUT REASONS -Panel.................................................................................................... 155
Browse.............................................................................................................................159
Browse Overview ........................................................................................................................ 159 BASELINE BROWSE/PRINT FACILITY - Panel .................................................................... 159
Recompile........................................................................................................................163
Recompile Overview ................................................................................................................... 163 RECOMPILE SOURCE Panel ................................................................................................. 163 ONLINE RECOMPILE JOB INFORMATION - Panel.............................................................. 165 Exercises for Recompile ......................................................................................................... 167
Relink ..............................................................................................................................169
Relink Overview.......................................................................................................................... 169 RELINK LOAD MODULES Panel.......................................................................................... 169 Exercises for Relink................................................................................................................ 171
Query...............................................................................................................................173
Query Overview........................................................................................................................... 173 QUERY OPTIONS Panel........................................................................................................ 173 QUERY PACKAGE PARAMETERS - Panel ............................................................................ 174 PACKAGE INFORMATION CATEGORIES Panel .......................................................... 176 QUERY COMPONENT PARAMETERS Panel...................................................................... 176 IMPACT ANALYSIS OF COMPONENTS Panel................................................................... 178 Exercises for Query................................................................................................................. 180
Compare..........................................................................................................................181
Compare Overview...................................................................................................................... 181 COMPARE Panel..................................................................................................................... 181 Table of Contents
User Training Guide
Exercises for Compare............................................................................................................ 183
Scan .................................................................................................................................185
Scan Overview............................................................................................................................. 185 LIBRARY SCAN UTILITY Panel........................................................................................... 185 Exercises for Scan................................................................................................................... 188
Compress ........................................................................................................................189
Compress Overview..................................................................................................................... 189 COMPRESS STAGING LIBRARIES Panel............................................................................ 189 Exercises for Compress........................................................................................................... 190
Log...................................................................................................................................191
Log Overview .............................................................................................................................. 191 BROWSE ACTIVITY LOG Panel........................................................................................... 191 Exercises for Log .................................................................................................................... 193
Glossary ..........................................................................................................................194
Table of Contents
User Training Guide
Preface
Corporate Background
SERENA Software - The Change Specialists - is a privately-owned software company founded in 1980 and is a worldwide provider of software that enables superior development and maintenance of applications throughout the enterprise. The company's focus is increasing software development productivity while reducing the cost of computing for mainframe-based applications. SERENA's products are used today in more than 2,400 data centers worldwide. The SERENA product line provides complete software life-cycle support for corporations through a diversified offering that is enhanced by alliances with leading software vendors. Along with innovative software, SERENA offers a comprehensive range of services to its customers including support, education, implementation services and frequent software enhancements. SERENA's Solutions/2000 makes it easy to identify, modify, test and implement date-sensitive applications in year 2000 situations. SERENA is headquartered in Burlingame, California, with an office in the U.K.
SOFTWARE PRODUCTS COMPAREX

COMPAREX is a multi-function database, load module and text comparison utility that automates the complex tasks of file comparison and systems testing. By performing line-by-line byte-level comparisons, COMPAREX can identify differences between any two films. COMPAREX plays a vital role in the testing and validation phase of year 2000 conversion projects. COMPAREX is an essential tool for application testing, software quality assurance, reconciliation of production source and load libraries, project-based application development and source code reconciliation. COMPAREX has more than 1,400 corporate licenses worldwide and is the leading comparison tool for Fortune 1000 organizations.
Preface
User Training Guide
TM
Concurrent Development Facility

Concurrent Development Facility (CDFTm), the eight-version reconciliation tool, significantly reduces implementation time and improves quality of new releases. CDF quickly compares and merges ongoing development and third party software with year 2000 remediation into one consolidated file. The CDF Version Impact Analysis facility helps you to efficiently plan and manage your application upgrade projects. To guide you through the reconciliation process, CDF's Version Editor displays all the differences in multiple colors.
Change Man
Change Man is a comprehensive system designed to provide both reliable and streamlined implementation of software changes from development into production. It is the fastest implementing software change management system for MVS environments. Change Man improves the availability of your software by ensuring that changes are successful when they get to production. It also cuts maintenance costs and provides the most thorough treatment of concurrent development available. Optima Software markets Change Man in the US and selected markets internationally.
STARTOOL
STARTOOL provides an on-line environment for application and system programmers in an IBM OS/390 or MVS environment. It can perform complex file and data management tasks, including editing and managing PDS, PDSE, sequential, direct access and VSAM files, and their contents. With STARTOOL, users have access to powerful and versatile tools critical for year 2000 conversions, including the capability to find and change date-sensitive code; reconcile load modules to source code; identify compile and execution time options (COBOL); locate and replace data in groups of members and data sets. STARTOOL also provides specialized services such as applying Data Aging techniques to existing production files to assist in creating year 2000 test files without programming.
Preface
10
User Training Guide
TM
StarWarp
StarWarp addresses the issue of Data Aging by providing a method of shifting, or aging the dates in existing files, thus providing the ability to perform necessary testing without the need to write one-time specialized programs for each test scenario. StarWarp helps by providing basic date aging capabilities. StarWarp minimizes the need to write batch programs for each file-aging situation, and enables programmers to create test data for year 2000 conversion projects by automating the process of incrementing, decrementing or specifying default values for day, month, year, and century fields. StarWarp addresses business rules assuring that certain activities can only occur on certain days, such as the last day of the month or the first Monday of the quarter.
SyncTrac@
SyncTrac is an MVS software environment synchronization and data set change tracking product. It speeds development and problem resolution with the ability to automatically detect, report, and recover from changes across local and remote environments. SyncTrac provides a standardized approach for maintenance and distribution of software thereby reducing redundant tasks performed by programmers. It ensures synchronization of multiple environments to guarantee system integrity and recoverability in the event of a disaster. SyncTrac was jointly developed with High Power Software (Sacramento, CA).
TM
X:Change
X:Change delivers a single GUI interface to MVS data that provides consistency and ease of use. It offers a unique bidirectional high-speed file transfer that improves development by eliminating TSO bottlenecks. X:Change integrates with leading application development tool vendors and provides a robust development environment that enables programmers to use their own desktop systems for development thereby ensuring higher productivity at a lower cost.
For More Information; For more information on any of these products, visit SERENA on the World Wide Web at www.serena.com, or via Email at info@serena.com.
11
Preface
User Training Guide
User Training Guide Content

The content of the User Training Guide provides the user with most of the information and reference material they will need to become a productive Change Man user. However, due to the vast amount of information the user may potentially require, additional reference manuals are available. These manuals have additional detailed information and technical explanations on all the processes within the Change Man system. These manuals are: Change Man User's Guide Change Man Messages and Codes Change Man Concurrent Development Facility Option Users Guide and Reference Change Man DB2 Option Change Man Online Forms Manager Option: Users Guide and Reference Change Man Information Management (Info/Man) Users Guide Change Man IMS Option
These manuals can usually be found with either your Local Administrator or Global Administrator person(s). If additional copies are required then please contact your Global Administration Representative and they can contact SERENA Software International. Since there is a large amount of information contained in the User Training Guide and the other references guides, our customers have requested that SERENA Software International offer several courses to best assist them to learn the Change Man system. As a result SERENA offers many courses to our customers. Please review Change Man Course Offerings section to view the current list of courses offerings.
Preface
12
User Training Guide
Change Man Course Offerings

SERENA Software International offers the following Change Man training courses. These courses are typically taught at the clients location:
q
Change Man for New Users Change Man for Experienced Users
1 day 1 day
13
Preface
User Training Guide
The intended audience for these courses is:

Application developers Application support staff Application admin staff Application approval staff (project leaders) Data center support staff Business analysts Almost every area of the IS organization that is involved in application change
Preface
14
User Training Guide
Change Man for New Users

Course Duration - 1 day
Intended audience:
First time users of Change Man, i.e. application development staff Individuals who will periodically use Change Man to review development work or approve Packages, i.e. Team Leaders, Project Leaders, or Data Center Support staff Individuals that require a refresher on the Change Package Lifecycle
Prerequisites:
Working knowledge of TSO/MVS Knowledge of the software development and installation procedures
Students will learn:

Change Man general concepts and facilities, includes Change Man architecture and Change Package Lifecycle Change Man terminology How to navigate effectively and efficiently within Change Man panels How to respond to general error conditions or situations using the tutorial function How Change Man can improve installing changes into baseline environments productively
Topics covered:
Primary Options: Notify, Tutorial, Build, Freeze, Promote, Approve (baseline), List (basic functions), Delete, Query Build Options: Dates, Create, Update, Utility, Checkout, Stage (basic functions), Audit (brief overview), Browse (basics), Listing Students will perform many hands-on exercises to develop confidence with core product functionality and panel navigation.
15
Preface
User Training Guide
Change Man for Experienced Users

Course Duration - 1 day
Intended audience:
Change Man user with any exposure to the Change Package process Individuals that assist any development staff with Change Man issues, questions or training Global or Local Change Man administrators
Prerequisites:
Hands on exposure or actual usage of Change Man Completion of Change Man for New Users course or equivalent
Students will learn:

Review of Change Man Lifecycle, architecture, terminology, concepts and facilities Change Man internals such as CMNWRITE, Install jobs, Audit and Compile/Link How to determine and resolve Audit out-of-synch conditions An introduction to the CDF option Advanced features not covered in the New User course such as Unfreeze, Recompile, Relink, Revert
Topics covered:
Primary Options: Build, Freeze (Unfreeze), Promote (Demote), List (detailed overview), Backout, Revert, Log Build Options: Stage (all functions), Audit (detailed overview), Recompile, Relink, Compare, Scan, Compress, Browse (all functions) CMNWRITE step in the compile process Introduction to Change Man CDF and DB2 options Introduction to OFM (Custom) Review of installation, backout and update Impact Analysis jobs Remote Promotion + Distribution
Students will perform many hands-on exercises the topics covered. Note: Students are strongly encouraged to bring real-world questions and situations.
Preface
16
User Training Guide
Introduction
What Is Change Man
Change Man is a comprehensive system designed to provide both 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 then to the production environment. A comprehensive TSO/ISPF interface guides the user through various change management processes. Change Man can manage the installation of a variety of components, such as: JCL, PROCs, and utility control cards Copy code used in the compile process Batch programs written in Assembler, COBOL, COBOL II, COBOL III, or PL/I CICS programs written in Assembler, COBOL, COBOL II, COBOL III, or PL/I Programs written in Easytrieve Programs written in DYL280 Vendor code without source DB2 DCLGEN output DB2 bind control statements DB2 binds for changed DB2 programs CICS basic mapping services (BMS) maps and the copy code CICS maps created by SDF II and the copy code Intertest for COBOL and COBOL II programs ... any other component that can be stored in a PDS or PDS-Like structure like 'Librarian' or 'Panvalet'.
17
Introduction
User Training Guide
Features of Change Man

Unique package concept guarantees the coordination of your entire change Concurrent development are gracefully managed Controls version discrepancy and out-of-synch component relationships Maintains listings on-line for immediate access Provides notifications in a timely manner Can manage your existing libraries (Librarian, Panvalet, or PDS, PDS/e) Full suite of on-line and batch query and reporting capabilities Maintains all historical information in a single repository
Introduction
18
User Training Guide
The Change Man ALLSITE Change Package Life Cycle

An overview of the Change Man Lifecycle is given below. It is a step-by-step description of the most common processes required to migrate a change from production to development, through the testing environments, and then back to the production libraries. Processes within brackets are potentially optional. The Package status is also indicated in the lower right-hand corner of the process box.
Create
Checkout
(DEV)
Stage
(Modify Components)
(DEV)
(Promote)
test
(DEV)
(Audit) (Unfreeze)
(FRZ)
Impact Analysis
(DEV)
(Revert)
(REJ)
Freeze
(FRZ)
(Promote)
test
(FRZ)
(Backout)
(BAK)
Approve
(APR)
Baseline Ripple
(BAS)
Main Process flow
Optional Processes
19
Introduction
User Training Guide
1.
The first step of the Change Package Life Cycle is the Create process. A Change Package contains all of the elements to be edited and installed into production, and is identified by a unique package ID automatically generated by Change Man. When a Change Package is created, the information that Change Man needs in order to track and control the package is entered. This includes the implementation instructions, whether it is a temporary or permanent change, the installation date and time, etc. The typical next step is to Checkout components from baseline. With checkout, components from your baseline libraries are copied to either a Change Man staging library or to a personal development library where changes can be made. Package components are now ready to be Staged. In the stage process the user can make all the changes or modifications required to all components. For source components, staging will ordinarily run the appropriate translation procedure to create associated load modules. Components such as documentation or copy members are simply copied into the staging libraries, if they aren't there already. Depending on the installation, the Change Package must pass an Audit before Freeze. The audit process ensures that no unexpected problems will occur. For example, if a component in the production library has been changed since it was checked out, Change Man alerts you to the problem by creating an out-of-synch condition for the package. After successfully passing the audit, the next step is to Freeze the Change Package. This locks the package (prohibiting further changes), and makes the package available for the promotion and approval processes. Promotion is an optional step. After successfully staging all components in the Change Package, the Change Package may then be Promoted. Promotion allows a Change Package to be moved through various levels of testing (e.g. promote from system testing to acceptance testing). Once all of the necessary 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 it. If the CMN method (Change Man's internal scheduler) was selected, Change Man will automatically install the package on the date and time specified at package creation. If an external scheduler is used (e.g. CA7, ESP, ZEKE, JOBTRAC, etc.), Change Man will convey the install information to that scheduler so that it can install the Change Package. Once the package has been installed, Change Man will perform the Baseline Ripple. Baseline Ripple is the process that Change Man executes to version all package components, i.e.: 0 becomes -1, -1 becomes -2, -2 becomes -3, etc. and the new baseline 0 version is installed.
2.
3.
4.
5.
6.
7.
8.
Introduction
20
User Training Guide
Change Man Library Environment (ALLSITE - Data Flow Diagram)
New Component Development
Test Environment (level 10) Test Environment (level 20)
Stage (S1)
Promote
Test Environment (level 30)
Temporary Work File
Stage (S2) Edit
Change Package STAGING Audit Freeze Approve Checkout
Baseline Ripple
Baseline (0)
Backout
Baseline (-1)
Baseline (-2)
21
Introduction
User Training Guide
Change Man Library Environment (DEVPROD Site - Data Flow Diagram)
New Component Development
Test Environment (level 10) Test Environment (level 20)
Stage (S1)
Promote
Test Environment (level 30)
Temporary Work File
Stage (S2) Edit
Change Package STAGING
Checkout Remote Promote
Baseline Ripple Distribute Baseline (0)
Remote Test Environment
Baseline (-1) Reverse Baseline Ripple Baseline (-2)
Production Staging Libraries
Install
Remote Production (0)
Backout
Remote Production (-1)
Introduction
22
User Training Guide
Change Man/MVS manages the transition of components from production to development and back to the production libraries by using Change Package staging libraries. Each Change Package will have its own set of staging libraries. All the Change Man processes rotate around these staging libraries. These staging libraries are the actual living breathing Change Package. Existing production components are copied into the staging libraries via the Checkout process, or new components from outside development libraries can be copied into the staging libraries via the Stage (S1) process. Component modification can occur within the Package staging libraries via the Stage (S2) process. The stage (S2) edit process creates a Temporary Work file where the user does all the component modifications. Once complete the Temporary Work file is copied back to the Package staging libraries. The Promote, Remote Promote and Distribution processes copy the required components from the Package staging libraries into the test environment files or the production files. . All components from the Package staging libraries are copied into the baseline libraries during the Baseline Ripple process.
23
Introduction
User Training Guide
Change Man Terminology

The following Change Man terms are the main terms new users should learn prior to working with the Change Man system. These are only the basics, and there many additional terms explained in the Glossary section at the end of this manual.
Application ID Application ID is used to identify a project within Change Man. Applications / Projects are defined groups for which Change Packages are to be created and manipulated. Usually a fourcharacter code is assigned to a specific Application. They are used to identify package ownership.
Approval The process whereby Change Packages are approved by designated individuals prior to installation into baseline / production.
Audit A Change Man utility that, in addition to other functions, inspects the Staging libraries for any out-of-synch conditions, source to load integrity, etc.
Baseline Library A Change Man library which stores the most current version (0) of production components, in addition to a pre-defined number of previous versions (-1, -2, etc.).
Baseline Ripple The process whereby a component becomes the new production component, the previous production component becomes the 1 version, -1 becomes 2, and so on. This process is called baseline ripple. The baseline ripple starts with the oldest baseline library and works its way back to the most current library.
Change Package Within Change Man, a Change Package is the vehicle in which all changes are moved from a development environment to a production environment. Change Packages may contain one or more components, which are required for a change.
Change Man Package Life Cycle This is a description of the complete steps or processes a Change Package may have in the Change Man system. (See chapter in this section for complete details).
Introduction
24
User Training Guide
Component A single member of a Change Package. Usually, a member of a library that has been brought into Change Man for the purpose of being modified. The component could be a source module, load module, PROC, JCL, copybook, DDL, datalib member etc.
Freeze The act of locking Change Packages so that modifications are prohibited. It also makes a package eligible for approval.
Library Type A three character identifier which represents the various component types in an application. Source components have library type of SRC, copybook components use CPY, load modules use LOD, etc.
Package ID Each Change Package is automatically assigned a unique package ID. Consisting of the Application ID and a sequential number (e.g. PAYR000001).
Package Staging Libraries Package Staging libraries are created solely for the purpose of holding components of a particular Change Package. Package Staging libraries are the living Change Package. The contents of the staging libraries are copied to the baseline libraries during the installation process.
Promotion A pseudo-production environment that allows for a variety of testing. Also, it is the act of copying a component from staging to a promotion environment or level.
Stage This function is used to copy components from development or personal libraries into Change Man Staging libraries. If the component is source (SRC), there is a second Staging step that compiles, link/edits, binds, etc. the component into an executable load module. Stage is also the function that you use to make changes or modifications to the components.
25
Introduction
User Training Guide
Accessing Change Man

Change Man runs as a started task in the MVS subsystem and utilizes cross-memory services for accessing ISPF. The started task architecture provides a single point of control and secure access to your production and development libraries. Interfacing directly to your security system for access, Change Man provides the optimum amount of control without sacrificing performance. Accessing Change Man is usually accomplished by entering a CLIST in option 6 of TSO. Check with your Global or Local Admin group for CLIST name or access procedures. During the signon initiation you will be presented with a temporary Change Man Title panel. Once the initiation is complete, the Primary Option Menu panel will then appear:
========= == == ======= == == ===== ====== =========== == == ========= == == == ======= ======= == == == == == == == == == == == ======== ========= == == == == ==== ======= == ======== ========= == == == == ==== ======= == == == == == == == == == == == ========== == == == == == ==== ========= ======== ========= == == == == == === ======= ========= ==== ==== ======= == == ============ ========= == == == == == == == == == == == == == == ========= == == == == == == ========= == == == == == == == == == == == == == == == == == ==== == == == == == ===
Date : Time : Version :
1998/12/11 12:14 4.1.6
The Software Change Manager SERENA Software International
CMN@PRIM--------- CHANGE MAN 4.1.6 PRIMARY OPTION MENU ---------- INIT Complete OPTION ===> _ 1 2 3 4 5 A B C D L N O Q R T X Build Freeze Promote Approve List Admin Backout CDF Delete Log Notify OFMlist Query Revert Tutorial Exit 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 Perform administration functions Back out a package in production Concurrent Development Facility Delete or undelete a package Browse the activity log 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 options displayed on the Primary Option Menu are built based upon the authorization of your User ID. Change Man dynamically builds this panel after verifying, with your host security system,
Introduction
26
User Training Guide
what Change Man functions you have access to. The user that had the previous panel displayed has the following authorizations granted: Administrator (Option A is displayed) Revert packages (Option R is displayed) Back Out packages (Option B is displayed) Online Forms package list (Option O is displayed as the customer purchased this Change Man option.) Change Man Users who are developers or approvers will most likely not have any of the additional options listed above. Most of the functions that they will use will be accessed from the Build Option menu, option 1 from on the Primary Option Menu. From the Primary Option Menu, you can access all the Change Man services and functions by using the panel by panel access method or the direct access method or the Package List method. See the below for all descriptions and details
27
Introduction
User Training Guide
Change Man Panel and Menu Navigation

Using Panel by Panel Navigation In the Option line, type the number or letter that designates the function you want to perform. Press Enter and Change Man will execute the request. For example, if you typed a 1 (for Build) in the Option line on the Primary Option Menu and then pressed Enter, the Build Options menu will be displayed. 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, usually PF3. Use the panel by panel navigation method to learn what and where all the functions are in Change Man. However, most users after they become more familiar with the product, will switch to the direct access method for navigation or the Package List option.
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, then press Enter. For example, if you typed: COMMAND => +1.1 COMMAND => =1.1 OPTION => =1.1 Or COMMAND => +1.6.2 COMMAND => =1.6.2 OPTION => =1.6.2
All will bring you to the Create Panel
All will bring you to the Stage Package Panel
Each character of the direct access command is a single character options on successive panels. Change Man will display 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, usually PF3.
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. See the Package List section in this manual for all descriptions and details.
Introduction 28
User Training Guide
Change Man Online Error Messages Change Man and ISPF handle online error messages similarly. A short error message is displayed by default in the upper right-hand corner of each panel. To display the long (or secondary) error message, press PF1. The message appears on the third line of the panel, left justified. Ordinarily, the long message is much more helpful because it provides additional information. Information, that usually advises the user how to resolve the error.
Remember, the long error message does not display by default, and it must be requested by pressing PF1.
If you press PF1 a second time, the tutorial option will appear for the function or panel you are on. See Tutorial section in this manual for all descriptions and details.
Using Selection Lists Change Man has many types of panels, one of which is a selection list. A selection list is a panel that has 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. Usually you type an * in the field or simply leave the field blank and press Enter to access the list. Below are two examples:
CMNCLTSL ---------------- LIBRARY TYPE SELECTION LIST ----COMMAND ===> _ _ _ _ _ ROW 1 TO 13 OF 13 SCROLL ===> PAGE
LIB DESCRIPTION CPY Copybooks CTC Control Cards DBB DB2 Bind Control Statements - Plans DBR DB2 Database Request Modules DOC Documentation S JCL Job Control Language _ LCT Linkedit Control Cards _ LOD Load Modules _ LST Compressed Compile Listings _ MPC Copybooks - CICS Maps _ PKG DB2 Bind Control Statements - Packages _ PRC JCL Procedures _ SRC Source Code ******************************* Bottom of data *******************************
Type an S beside the selection or member you wish to select and press ENTER. To exit and return to previous panel press PF3.
CMNCCMSL FROM JCL/LVL(0) - WSER200.BASE.ZERO.JCL ----------
ROW 1 TO 15 OF 15
29
Introduction
User Training Guide
COMMAND ===>STATUS NAME _ $$$INDEX _ #ACF2 _ #NDM _ A _ ACKLA S AFRICAD _ AFRICAU _ ALLOCBAS _ AMBLIST _ ARCHIVE1 _ ASMDB2SQ _ ASSEMBLE _ A2VECFG _ BACKUP _ BAYD
VV.MM 01.00 01.00 01.00 05.01 06.01 01.01 01.01 01.01 01.00 01.00 01.00 01.00 01.00 01.00 01.01
CREATED 1996/01/26 1996/01/26 1996/01/26 1995/06/23 1995/01/06 1996/11/19 1996/11/19 1998/01/29 1996/01/26 1996/01/26 1996/01/26 1996/01/26 1996/01/26 1996/01/26 1996/03/15
LAST MODIFIED 1997/06/21 13:59 1996/06/18 12:20 1996/06/18 12:20 1998/04/20 16:21 1996/09/05 12:39 1997/02/13 16:28 1997/02/13 16:28 1998/04/20 12:37 1996/06/18 12:20 1996/06/18 12:20 1996/06/18 12:20 1996/12/30 17:50 1996/01/26 17:09 1996/06/18 12:20 1997/02/13 16:28
SIZE SCROLL ===> PAGE INIT ID 56 53 C41610 132 132 C41601 41 41 C41601 32 30 WSER171 42 38 WSER16 39 40 WSER31 34 34 WSER31 180 124 WSER160 11 13 C41601 50 50 C41601 48 48 C41601 37 37 C41601 60 60 C41601 17 17 C41601 56 40 WSER31
Type an S beside the selection or member you wish to select and press ENTER. To exit and return to previous panel press PF3.
Working with Lists of Libraries, Packages and Components There are lists in Change Man that let you view contents of libraries, packages and components. 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, and press ENTER: B to Browse an item. S to Select an item for action. H to display History for an item.
Type the following commands on the Command line and press ENTER: 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).
Introduction
30
User Training Guide
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 from 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.
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. If you have color monitors the fields have different colors. If you have a monochrome screen the intensity of the read only fields differs 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 appears. However, the color/hue of the field is the read only color, and BROWSE ONLY appears in the upper right hand corner of your screen.
Scrolling through Lists Often, lists that you build or access through Change Man are too long to view on the 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 forward or backward a specific number of lines, type a number and use the PF7 key to go forward that number of lines, or the PF8 key to go backward that number of lines. Using the combination of a command character and a PF key, you can also immediately move the maximum number of lines to the top or bottom of a panel or dataset/member. By typing m on the Command line and using the PF7 key, you move backward (toward the top of the data). Alternatively, you can use m + PF8 for moving forward (toward the bottom of the data).
Closing Panels
31 Introduction
User Training Guide
In general, you close panels by pressing Enter to process your changes, and then typing End and pressing Enter (normally, the PF3 key). You can abandon your changes two ways: Some panels require you to enter End in the Option or Command field and press Enter to abandon. Other panels require you to type CANCEL in the Command line and press Enter. In general, the panel you are viewing always tells you how to abandon your changes.
Introduction
32
User Training Guide
Primary Option Menu + Build Options

Primary Option Menu + Build Options Overview
The Primary Option Menu and the Build Options menu are the 2 main navigational panels in the Change Man system. Their primary function enables the user to access all the Change Man functions. 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.
PRIMARY OPTION MENU Panel

To access this Panel: Enter the CLIST for the Change Man subsystem you want to sign onto in option 6 of TSO
CMN@PRIM--------- CHANGE MAN 4.1.S PRIMARY OPTION MENU --------- INIT Complete OPTION ===> _ 1 2 3 4 5 A B C D L N O Q R T X Build Freeze Promote Approve List Admin Backout CDF Delete Log Notify OFMlist Query Revert Tutorial Exit 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 Perform administration functions Back out a package in production Concurrent Development Facility Delete or undelete a package Browse the activity log 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
To exit this panel you can: Enter the required selection on the Option line and press ENTER Use the direct access commands in the Option line Press PF3 or enter END on the Option line and press ENTER, you will exit the Change Man subsystem and be returned to TSO
33 Primary Option Menu + Build Options
User Training Guide
NOTIFY Panel
The Global Notification File is a file that is used by the Change Man Global and Application Administrators to notify Change Man users of: Hints and tips on how to use different functions. Changes to the Change Man configuration. Solutions to common problems. Any other informational messages.
If the Global Notification File is updated, Change Man will notify you. A message, "NOTIFICATION UPDATED", will be displayed in the upper right-hand corner of the Primary Option Menu whenever this file is updated. This notification message will reappear every time you sign onto Change Man, unless you view the Notification File. To view this file you use the Notify panel. To access this Panel: Select option N from the Primary Option Menu for Notify and press ENTER
-BROWSE -- WSER24.WSER24.CMN94152.T1447172.OUTLIST - LINE 00000000 COL 001 080 COMMAND ===> SCROLL ===> PAGE ********************************* TOP OF DATA ******************************** GLOBAL ADMINISTRATION MESSAGE 07/01/1998 1. New library types have been added to perform automatic JOBSCANs. 2. Security request forms have been added to Online Forms. Discontinue the use of "paper" form SEC00010. APPLICATION ADMINISTRATION MESSAGE APPLICATION PAYR 07/05/1998 1. All baseline libraries will be compressed on Sunday. 2. Audit level has been changed to 4. APPLICATION GENL 07/05/1998 1. Department number is now required when creating a new change package. Enter your Cost Center number in this field.
To exit this panel you can: Press PF3 or enter END or CANCEL in the Command field to continue to the next panel in the process
Upon exiting the notification panel, you will have the option of printing the Global Notification File. The following panel with JOB card will be displayed:
CMNNOT00 ----------- GLOBAL NOTIFICATION REPORT DISPOSITION ------------------
34
User Training Guide
OPTION ===> OUTLIST DATASET
: WSER92.WSER92.CMN98351.T1551260.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 ===> //WSER92L JOB (XXXX,999),WSER92,CLASS=E,MSGCLASS=3, ===> // TIME=2,REGION=4M,NOTIFY=WSER92 ===> //*JOBPARM SYSAFF=ESA1 ===> //* Press ENTER or END to process Enter CANCEL command to exit without saving changes.
To exit this panel you can: Press ENTER to instruct Change Man to submit the print job Press PF3 or enter END or CANCEL in the Option line to return to the Primary Option Menu
35
User Training Guide
CHANGE MAN TUTORIAL Panel

Change Man has a very good on-line tutorial feature that enables the user to access information about most Change Man processes and features. Many user questions can be answered by viewing the tutorial information. To access this Panel: Select option T from the Primary Option Menu for Tutorial and press ENTER You can also enter PF1 from any Change Man panel to bring up the tutorial for the specific function you are in
CMN00000 ------------------- Change Man Tutorial -------------------- TUTORIAL COMMAND ===> More: + ----------------------------------| CHANGE MAN TUTORIAL | ----------------------------------This tutorial provides on-line information about Change Man features and operations. The table of contents contains a list of major topics. You may view the tutorial items by selecting an option and pressing ENTER. TABLE OF CONTENTS G 1 2 3 4 D R Q L A GENERAL BUILD FREEZE PROMOTE APPROVE DELETE REVERT QUERY LOG ADMIN General overview of Change Man Create, update and review change package data Freeze or Unfreeze a change package Promote/Demote a change package Approve/Reject a change package Delete a change package Revert a change package to DEVelopment status Query change package information Browse the activity log Perform Administrative functions
To exit this panel you can: Enter the required selection in the Command field and press ENTER Press PF3 or enter END or CANCEL in the Command field to return to the previous panel
Note: To scroll down or up in the tutorial panel you use the PF10 (up) and PF11 (down) function keys.
36
User Training Guide
BUILD OPTIONS Panel

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. To access this Panel: Select option 1 from the Primary Option Menu for Build and press ENTER
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.
To exit this panel you can: Enter the required selection in the Option line and press ENTER Press PF3 or enter END or CANCEL in the Option line to return to the previous panel
37
User Training Guide
PLANNED INSTALLATION CALENDAR - Panel

Use this panel to enter and update the maximum number of planned changes that can be scheduled for any given date. Information can be entered or updated for up to 52 weeks from the current date. The maximums are initially set to zero for all dates. To reset all to another number, enter SETALL xxx on the Command line. To set a particular day of the week, enter SET(day) xxx (example: SETMON 123). Dates may also be set individually. To prevent the scheduling of any planned changes for a given day, leave the maximum at zero for that day. The calendar will be automatically incremented when change packages are created, and decremented when change packages are deleted, rescheduled or installed. To access this Panel: Select option 1 from the Primary Option Menu for Build, then Select option 0 on the Build Options Menu for Dates
ROW 1 TO 19 OF 52 SCROLL ===> PAGE # SUN MAX 2 255 0 255 0 255 0 255 0 255 0 255 0 255 0 255 0 255 0 255 0 255 0 255 0 255 0 255 0 255 0 255 0 255 0 255 0 255 TOTALS # MAX 5 1785 28 1785 0 1785 1 1785 0 1785 0 1785 0 1785 0 1785 0 1785 0 1785 0 1785 0 1785 0 1785 0 1785 0 1785 0 1785 0 1785 0 1785 0 1785
CMNCLNDR ----------- PLANNED INSTALLATION CALENDAR ------COMMAND ===> Press ENTER to update calendar or END command to exit. STARTING MON TUE WED THU FRI SAT DATE # MAX # MAX # MAX # MAX # MAX # MAX 1998/12/21 0 255 0 255 0 255 0 255 0 255 3 255 1998/12/28 0 255 0 255 15 255 13 255 0 255 0 255 1999/01/04 0 255 0 255 0 255 0 255 0 255 0 255 1999/01/11 0 255 0 255 0 255 1 255 0 255 0 255 1999/01/18 0 255 0 255 0 255 0 255 0 255 0 255 1999/01/25 0 255 0 255 0 255 0 255 0 255 0 255 1999/02/01 0 255 0 255 0 255 0 255 0 255 0 255 1999/02/08 0 255 0 255 0 255 0 255 0 255 0 255 1999/02/15 0 255 0 255 0 255 0 255 0 255 0 255 1999/02/22 0 255 0 255 0 255 0 255 0 255 0 255 1999/03/01 0 255 0 255 0 255 0 255 0 255 0 255 1999/03/08 0 255 0 255 0 255 0 255 0 255 0 255 1999/03/15 0 255 0 255 0 255 0 255 0 255 0 255 1999/03/22 0 255 0 255 0 255 0 255 0 255 0 255 1999/03/29 0 255 0 255 0 255 0 255 0 255 0 255 1999/04/05 0 255 0 255 0 255 0 255 0 255 0 255 1999/04/12 0 255 0 255 0 255 0 255 0 255 0 255 1999/04/19 0 255 0 255 0 255 0 255 0 255 0 255 1999/04/26 0 255 0 255 0 255 0 255 0 255 0 255
To exit this panel you can: Enter the required selection in the Command field and press ENTER Press PF3 or enter END or CANCEL in the Command field to return to the previous panel
38
User Training Guide
Create
Create Overview
The first process in the Change Man Life cycle is the create process. This is where you create an entry in the Package Master with a change package ID number and some general housekeeping information. Creating a change package involves describing the "outer structure" of a package. Basically, you provide 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 choose along the way. Combined, these panels provide the following information about the package to Change Man: control information description installation-contingency action / instructions site responsibility job scheduling installation date other details
Since the Create process differs depending on the choices you make when you create the Change Package, there may be up to 8 different panels that you might see, they are: Panel Name Create a New Package Package Description Installation Instructions Scheduling Dependencies Affected Applications On Site Information Remote Site Information Complex/Super Panel ID CMNCRT01 CMNCRT02 CMNCRT03 CMNCRT04 CMNCRT05 CMNCRT06 CMNCRT07 CMNCRT08
39
Create
User Training Guide
No matter what options you plan to use for the new change package, you will always start the Create process with the Create a New Package panel. The panels which you encounter as you Create a change-package are governed by these factors: The package level: simple, participating, or super/complex Your site configuration: 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); or Development/Production
Create
40
User Training Guide
CREATE: CREATE A NEW PACKAGE - Panel

This panel is the start of the Create a new Package in Change Man. It requires that the user supply certain control information. This control information determines which panels you will be presented. To access this Panel: Select option 1 from the Primary Option Menu for Build, then Select option 1 on the Build Options Menu for Create While in the List option from the Primary Options Menu, enter your selection criteria and press ENTER, on the resulting package list panel enter CR in the Command line and it will bring you to the first panel of the Create process You can also access this panel through the Update Package Information (See Update Package Information section)
CMNCRT01 ---------------- CREATE: CREATE A NEW PACKAGE ---------------------OPTION ===> L L S Long method - Prompt for package description and special instructions Short method - Use default package description and instructions
PACKAGE TITLE ===> My first change man package APPLICATION REQUESTER'S NAME REQUESTER'S PHONE WORK REQUEST ID DEPARTMENT PACKAGE LEVEL PACKAGE TYPE PACKAGE TIME SPAN PACKAGE TO COPY FORWARD UNPLANNED REASON CODE TEMPORARY CHANGE DURATION ===> ===> ===> ===> ===> ===> ===> ===> ===> ===> ===> USER (Blank or pattern for list) John Programmer 1234 2345 99 1 (1-Simple, 2-Complex, 3-Super, 4-Participating) PLANNED (Planned or Unplanned) PERM (Permanent or Temporary) (Optional package name) (* for list) (In days)
To exit this panel you can:
Press the ENTER key to continue to the next panel in the process Press PF3 or enter END in the Option line and the Create Change Package process is abandoned and Change Man returns you to the panel you came from Use the direct access commands in the Option line
41
Create
User Training Guide
All of the following fields are required for the first time you create a Change Package. Most of this information is stored in your personal profile, and will reappear with each time you create a package from then on. Changes can be made as necessary. Field OPTION Description L - Create a package the long way. All the required Create package panels will appear, and you will be required to provide all the mandatory information on each panel. S - Create a package the short way. This option only requires you to fill in the Create a New Package and Installation Instructions. All other create panels are not displayed, however they can be filled in later by using the Update option. The short method is generally used to create a package very quickly. Note: The advantage of the long method is that more historical information is saved for your package. They are both viable methods and each shop may have its own guidelines for which method is preferable and under what circumstances. PACKAGE TITLE Type a brief title for the new change package. Choose a title, which is easily recognizable, since it appears 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
Type the requester's phone number.
WORK REQUEST ID Type the work request number. DEPARTMENT PACKAGE LEVEL Type the department to which the Change Package will belong. 1 Simple - The Change Package contains a change that is unrelated to any other change package. 4 Participating - The purpose of a participating package is to have Change packages share components between each other. Only participating packages can share with other participating packages and not simple packages. The participating packages are linked by the use of the Complex/ Super package.
Create
42
User Training Guide
Field
Description 2 Complex / 3 Super - A complex or super package is the parent of two or more participating change packages. You must first create the participating change packages, then someone is designated to create the complex or super package. During the creation of the Complex or Super package you will be asked to enter the package IDs of the participating packages. The order in which the participating packages appear, is the order Change man will use to resolve any references during the compile and link steps. Complex or Super packages never contain any components, therefore they never get installed to baseline.
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, possibly an emergency fix. Unplanned packages bypass some of the application rules and usually have a separate approval list. Permanent - Permanent change packages contain components that are scheduled changes that update Baseline/Production libraries. Permanent packages are either planned or unplanned. This is the normal way to Install changes. Temporary - Temporary change packages contain components that the user does not want to put into the Baseline/Production libraries. These components are installed into a static override library typically STEPLIBed in front of the baseline libraries. Temporary packages can either be planned or unplanned. Temporary packages run for a predetermined length of time. Once that time has expired, Change Man automatically deletes the components for the static temporary library. If you are creating a Change Package that is similar to an existing package within the application, you may want to utilize this option. Change Man will copy all information (package description, installation date/time, etc.) from an existing Change Package to the package which you are creating. This can be a great time-saver. CAUTION: If checkout to personal libraries is allowed, do not copy another developer's Change Package, or you will be checking out to his/her personal library.
PACKAGE TIME SPAN
PACKAGE TO COPY FORWARD
UNPLANNED REASON
This is a required field only if the package type is CODE Unplanned. Enter the code representing the reason that the package is unplanned, or enter an * to display a list of the codes available.
43
Create
User Training Guide
Field TEMPORARY CHANGE
Description This field is mandatory if the Change Package you are
DURATION
creating is a Temporary package. Enter the number of days you want the components within the Temporary Package to remain in the temporary library. Change Man will delete the components after the duration period has ended. Change Man does the delete process at the same time to day as the install. Example if the install was at 2:00 p.m. then the delete will occur also at 02:00 p.m.
Create
44
User Training Guide
CREATE: PACKAGE DESCRIPTION - Panel

This panel allows you to enter a description of the Change Package. It should be as complete and descriptive as possible. This is because approvers, and other reviewers, sometimes rely on this section to get a good picture of the change. Change Man calculates the maximum number of lines based upon your screen size To access this Panel: Automatically displayed after completing the Create A New Package Panel You can also access this panel through the Update Package Information (See Update Package Information section)
ROW 1 TO 12 OF 12 SCROLL ===> PAGE
CMNCRT02---------------- CREATE: PACKAGE DESCRIPTION ----COMMAND ===> Press ENTER or END to continue or type CANCEL to exit. '''' '''' '''' '''' '''' '''' '''' '''' '''' '''' '''' ''''
(minimum one line, maximum 46 lines) You should include a meaningful description of the package______________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________
******************************* Bottom of data ******************************
To exit this panel you can: After you have entered all required fields, press ENTER or PF3 key to continue to the next panel in the package create Enter CANCEL in the Command line and press ENTER, the Create Change Package process is abandoned and Change Man returns you to the Create a New package panel
45
Create
User Training Guide
Field
Description
LCMD (first column) I - Insert a new line R - Repeat an existing line D - Delete a line Free form text area Description - you may use this area to enter any additional information about this change. Keep in mind that some of the people that will be approving your package may not know too many details about its content. This description panel can be used to inform these approvers of the specific package details.
Create
46
User Training Guide
CREATE: INSTALLATION INSTRUCTIONS - Panel

Use this panel to record instructions for the Installation of the change package. As well it will indicate an option for problem contingency instructions in case a production problem arises after the package has been installed. Individuals overseeing the installation can use these instructions. To access this Panel: Automatically displayed after completing the Package Description Panel You can also access this panel through the Update Package Information (See Update Package Information section)
CMNCRT03------------- CREATE: INSTALLATION INSTRUCTIONS -COMMAND ===> Press ENTER or END to continue or type CANCEL to exit. CONTINGENCY ===> 3 1-Hold production and contact analyst 2-Backout change, continue production 3-Other ===> Call Bob the Programmer (CMN, Manual or Other)
SCHEDULER '''' '''' '''' '''' '''' '''' '''' '''' '''' '''' ''''
===> CMN
(minimum one line, maximum 46 lines) You must add some info in this text field_______________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________
To exit this panel you can: After you have entered all required fields, press ENTER or PF3 key to continue to the next panel in the package create process Enter CANCEL in the Command line and the Create Change Package process is abandoned and Change Man returns you to the Create a New package panel
47
Create
User Training Guide
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 change, 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 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. CMN - Change Man holds the installation until the date and time you specify on one of the Site Configuration panels. 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.
SCHEDULER
LCMD (first column) I - Insert a new line R - Repeat an existing line D - Delete a line Free form text area Free form text that 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.
Create
48
User Training Guide
CREATE: ON SITE INFORMATION - Panel Use this panel to inform Change Man of the change package installation date and time. This panel is only displayed when your Change Man configuration is an ALL Site. If your site is configured as a D or DP site, then the Remote Site Information panel will be presented (see next section). To access this Panel: Automatically displayed after completing the Installation Instructions Panel You can also access this panel through the Update Package Information (See Update Package Information section)
CMNCRT06----------------- CREATE: ON SITE INFORMATION ---------------------COMMAND ===> Press ENTER to create the package or type CANCEL to exit. INSTALL YYYYMMDD 19981230 DATE/TIME FROM TO 0700 0730 PRIMARY/BACKUP CONTACTS call Bob Programmer______ call Susan Team Leader PHONE NUMBERS 123-4567 x 789_ 345-6789 x 987_
To exit this panel you can: After you have entered all required fields, press ENTER to complete the Package Create process Press PF3 or enter CANCEL in the Command line and press ENTER, the create change package process is abandoned and Change Man returns you to the Create a New package panel
49
Create
User Training Guide
Field INSTALL DATE/TIME
Description In this field, enter the date and time that the package is to be installed. Specify the primary and backup contacts' phone numbers or extensions. These people are notified if a problem arises during package implementation.
PRIMARY/BACKUP
After you have filled in all the information on the panel and pressed ENTER, Change Man will then create your change package, return you to the BUILD OPTION panel, and display the Change Package ID in the upper right hand corner of the panel. Finally Change Man updates the Planned Installation Calendar.
Create
50
User Training Guide
CREATE: AFFECTED APPLICATIONS - Panel

This panel is only used in conjunction with participating packages. If the participating package you are creating affects other applications, then you can use this panel to identify which applications they are. Change Man will then add to the approval list any approvers that differ from your regular application approver list. Note: This panel does not have any required fields. You only use this panel if indeed the participating package you are creating does affect other applications. If there are no relationships then just press ENTER to continue. To access this Panel: Automatically displayed after completing the Installation Instructions Panel you can also access this panel through the Update Package Information (See Update Package Information section)
CMNCRT05 --------------- CREATE: AFFECTED APPLICATIONS ---COMMAND ===> Press ENTER to continue or type CANCEL to exit. COMPLEX/SUPER PACKAGE ID ===> __________ '''' '''' '''' '''' '''' '''' '''' '''' '''' '''' '''' APPL ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____
******************************* Bottom of data ********************************
To exit this panel you can: Enter any affected applications then press ENTER to continue to the next panel in the package create process, if there are no affected applications, then just press ENTER Press PF3 or enter CANCEL in the Command line and press ENTER, the create change package process is abandoned and Change Man returns you to the Create a New package panel
51
Create
User Training Guide
Field
COMPLEX/SUPER PACKAGE ID APPL
Description
Enter the package ID of the complex/super package associated with this participating package Enter the application 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.
LCMD (first column) I - Insert a new line R - Repeat an existing line D - Delete a line
Create
52
User Training Guide
CREATE: COMPLEX / SUPER INFORMATION - Panel

This panel is used to record the participating packages that are associated to this complex / super package. Note: This panel does not have any required fields. You can create the complex / super package with no participating packages, just press ENTER to continue. Once you create the participating packages then you can use the Update Package Information panel to update this list. To access this Panel: Automatically displayed after completing the Package Description Panel You can also access this panel through the Update Package Information (See Update Package Information section)
Note: Use the REFRESH command to 'undo' a list that was entered in error.
CMNCRT08------------ CREATE: COMPLEX/SUPER INFORMATION -COMMAND ===> PACKAGE ID: TEST000064 STATUS: OPN ROW 1 TO 12 OF 12 SCROLL ===> PAGE
Press ENTER to continue or type CANCEL to exit. '''' '''' '''' '''' '''' '''' '''' '''' '''' '''' '''' '''' PACKAGE ID TEST000012 TEST000045 TEST000077 __________ __________ __________ __________ __________ __________ __________ __________ __________
******************************* Bottom of data *****************************
To exit this panel you can: Enter the participating packages then press ENTER to complete the package create process, if there are no participating packages, then just press ENTER, Change Man will return you to the Create A New Package panel and display the package ID in the upper right-hand corner. Press PF3 or enter CANCEL in the Command line and press ENTER, the create change package process is abandoned and Change Man returns you to the Create a New package panel Description
Field
53
Create
User Training Guide
PACKAGE ID
Enter the participating packages associated to this complex / super package. Note: The order that the participating packages are entered represents the order references will be resolved during the compile and link processes.
LCMD (first column) I - Insert a new line R - Repeat an existing line D - Delete a line
Create
54
User Training Guide
Commonly Asked Questions

Question. When I first created my package I thought it was going to be a Simple package, later I was informed it needed to be a Participating Package, can I change the Package Level? Yes you can. Use the Package Update option to change the package level in the Package Control Information panel.
Answer.
Question.
If I select Manual for the scheduler, does Change Man use the Install date and Time? No it does not. The package gets installed as soon as the last approver approves the package.
Answer.
Question. Answer.
Can the Install date and time span over midnight? No it does not. You will receive an error message Invalid Date Range.
Question. Answer.
Can a Participating package be a Temporary package? No it can not. Participating packages must be permanent.
55
Create
User Training Guide
Exercises for Create

Exercise #1: Create a simple planned permanent Change Package to update payroll. It is to be installed one week from today's date, after payroll CICS is brought down.
Exercise #2:
Create a simple unplanned temporary Change Package that is to contain an emergency change to a payroll source component. Install it immediately after final approval, and keep the change for three days.
Exercise #3:
Create two (2) participating planned permanent Change Package with a complex parent linking the two new participating packages.
Create
56
User Training Guide
Update
Update Overview
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 project. You can browse the information if the package is in Frozen (FRZ) status. If you have selectively unfrozen the general category, you can update options I through 6. Also, if you have selectively Unfrozen the onsite category, you can update option 7.
UPDATE: PACKAGE INFORMATION Panel

To access this panel: Select option 1 from the Primary Option Menu for Build, then Select option 2 on the Build Options Menu for Update
CMNPGNL0 ---------------- UPDATE: PACKAGE INFORMATION --------------------OPTION ===> _ PACKAGE ID ===> TEST000073 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
To exit this panel you can: Enter the update option you want to perform 1 9, press the ENTER key press PF3 or enter END in the Command line and press ENTER, Change Man returns you to the panel you came from
Note: The PACKAGE ID is updateable, so check that the package ID displayed is the Change Package you want to work with.
UPDATE: CONTROL INFORMATION Panel

57 Update
User Training Guide
This panel displays the change package control information, which was entered when the package was created. You can update any of the highlighted fields.
CMNPGNL1 ---------------- UPDATE: CONTROL INFORMATION ---------------------COMMAND ===> PACKAGE ID: TEST000066 COMPLEX/SUPER ID: N/A PACKAGE TITLE ===> Payroll month end install REQUESTER'S NAME REQUESTER'S PHONE WORK REQUEST ID DEPARTMENT PACKAGE LEVEL PACKAGE TYPE PACKAGE TIME SPAN UNPLANNED REASON CODE TEMPORARY CHANGE DURATION ===> ===> ===> ===> ===> ===> ===> ===> ===> WSER92 666 123-3456 PAY234 D1234 1 (1-Simple, 2-Complex, 3-Super, 4-Participating) PLANNED PERM (* for list) (In days) STATUS: DEV STATUS: INSTALL DATE: 19981230
UPDATE: PACKAGE DESCRIPTION - Panel

This panel displays the package description information, which was entered when the package was created. You can update the description area.
CMNPGNL2 ---------------- UPDATE: PACKAGE DESCRIPTION ------- ROW 1 TO 1 OF 1 COMMAND ===> SCROLL ===> PAGE Press ENTER to process; enter END command to exit. PACKAGE ID: TEST000066 STATUS: DEV INSTALL DATE: 19981230
(minimum one line, maximum 46 lines) '''' Payroll month end install________________________________________________ '''' Add in a very detailed description of the change package_________________ ******************************* Bottom of data *******************************
Update
58
User Training Guide
UPDATE: INSTALLATION INSTRUCTIONS - Panel

This panel displays the package description information, which was entered when the package was created. You can update the description area.
CMNPGNL3 ------------- UPDATE: INSTALLATION INSTRUCTIONS ---- ROW 1 TO 1 OF 1 COMMAND ===> SCROLL ===> PAGE Press ENTER to process; enter END command to exit. PACKAGE ID: TEST000066 CONTINGENCY ===> 1 STATUS: DEV INSTALL DATE: 19981230
1-Hold production and contact analyst 2-Backout change, continue production 3-Other ===> (CMN, Manual or Other)
SCHEDULER
===> MANUAL
(minimum one line, maximum 46 lines) '''' PLEASE CALL BOB AT HOME.________________________________________________ ******************************* Bottom of data *******************************
UPDATE: SCHEDULING DEPENDENCIES - Panel

Use this panel to specify the Successor (run after) and the Predecessor (run before) Jobs that your scheduling system must be aware of in order to schedule the installation of this change package's components.
CMNPGNL4 -------------- UPDATE: SCHEDULING DEPENDENCIES --COMMAND ===> Press ENTER to process; enter END command to exit. PACKAGE ID: TEST000066 '''' '''' '''' '''' '''' '''' '''' '''' '''' '''' SUCCESSOR ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ PREDECESSOR ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ STATUS: DEV INSTALL DATE: 19981230 ROW 1 TO 12 OF 12 SCROLL ===> PAGE
****************************** Bottom of data ********************************
59
Update
User Training Guide
UPDATE: AFFECTED APPLICATIONS - Panel

Use this panel to select the application mnemonics that may be affected by the installation of this change package.
CMNPGNL5---------------- UPDATE: AFFECTED APPLICATIONS ---COMMAND ===> Press ENTER to process; enter END command to exit. PACKAGE ID: TEST000057 COMPLEX/SUPER ID: TEST000055 '''' '''' '''' '''' '''' '''' '''' APPL ____ ____ ____ ____ ____ ____ ____ STATUS: DEV STATUS: OPN INSTALL DATE: 19980313 ROW 1 TO 12 OF 12 SCROLL ===> PAGE
****************************** Bottom of data ********************************
UPDATE: COMPLEX/SUPER INFORMATION - Panel

Use this panel to display and update the list of individual application change packages that make up this complex or super change package. Use the 'REFRESH' command to re-display blank lines for entering package ID's.
CMNCRT08------------ UPDATE: COMPLEX/SUPER INFORMATION -COMMAND ===> PACKAGE ID: TEST000064 STATUS: OPN ROW 1 TO 12 OF 12 SCROLL ===> PAGE
Press ENTER to continue or type CANCEL to exit. PACKAGE ID '''' '''' '''' '''' '''' '''' '''' '''' ''''
TEST000012 TEST000045 TEST000077
__________ __________ __________ __________ __________ __________
******************************* Bottom of data *****************************
Update
60
User Training Guide
UPDATE: SITE INFORMATION Panel

Use this panel to update the names and phone numbers of the people who will be responsible for supporting the installation of the change package, as well as entering the installation date information.
CMNONSTE------------------ UPDATE: SITE INFORMATION -------------------------COMMAND ===> Press ENTER to process; enter END command to exit. PACKAGE ID: TEST000057 INSTALL YYYYMMDD 19980313 DATE AND TIME: FROM 0000 TO 2359 PRIMARY/BACKUP CONTACTS Bob Programmer___________ Susan Analyst____________ PHONE NUMBERS 696 6245_______ 696 6518_______ CREATOR: WSER200 STATUS: DEV
61
Update
User Training Guide
THIS PAGE LEFT BLANK
Update
62
User Training Guide
Utility
Utility Overview
The Utility Request facility is designed to Rename or Scratch (delete) components in production and/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. Change Man during Package production Installation and Baseline Ripple will process these utility requests. Change Man processes these requests after installing and rippling staged component versions.
UTILITY: RENAME / SCRATCH OPTIONS Panel

Use this panel to direct Change Man to where you would like to rename or scratch the components, either a Baseline library or a change package. To access this Panel: Select option 1 from the Primary Option Menu for Build, then Select option 4 on the Build Options Menu for Utility
CMNUTL00-------------- UTILITY: RENAME/SCRATCH OPTIONS ----------------------OPTION ===> _ PACKAGE ID ===> TEST000057 1 2 Baseline Package - Select baseline components to scratch or rename - Process scratch or rename requests in package
To exit this panel you can: Enter 1 or 2 in the Option line then press ENTER to proceed to next panel Press PF3 or enter END in the Option line and press ENTER, Change Man will return you to the previous panel
Field
Description
63 Utility
User Training Guide
OPTION
1 - To select from components residing in the baseline libraries. 2 - To display utility requests in the change package. Enter the Change Package ID, or double check the package ID displayed is still the package you want to work with.
PACKAGE ID
UTILITY: BASELINE SELECTIONS - Panel

Use this panel to set up utility requests for the members of your application's baseline libraries, (which mirrors the contents of your application's production libraries). To access this Panel: Select option 1 from the Utility: Rename / Scratch Options panel
CMNUTL01----------------- UTILITY: BASELINE SELECTIONS ----------------------OPTION ===> _ R - Rename a component S - Scratch a component blank - Display component selection list LIBRARY TYPE ===> ___ (Blank for list) COMPONENT ===> ________ (Blank or pattern for list) NEW NAME ===> ________ (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.
To exit this panel you can: Enter the requested fields and press ENTER Press PF3 or enter END in the Option line and press ENTER, Change Man will return you to the previous panel
Utility
64
User Training Guide
Field OPTION
Description This field can only be used if you also enter the Library Type and Component fields. R - To set up a rename request S - To set up a scratch request Enter the Library type of the library you want to perform the scratch or rename operation to. If you leave this field blank, Change Man will display a list of possible library types to select from.
LIBRARY TYPE
COMPONENT
Enter the member name to be scratched or renamed. If you leave this field blank, Change Man will display a list of all the components in the baseline library type. From the displayed component list you can enter the scratch or rename line commands. For each member selected for Rename, enter the new name.
NEW NAME
65
Utility
User Training Guide
UTILITY: PACKAGE LIST
Use this panel to activate or delete utility requests, Rename or Scratch that exist as part of a change package. To access this Panel: Select option 2 from the Utility: Rename / Scratch Options panel
UTILITY: TEST000066 LIST ------CHANGED 1998/12/03 06:13 1998/12/03 06:13 1998/12/03 06:13 1998/12/03 06:13 ID WSER92 WSER92 WSER92 WSER92 ROW 1 TO 4 OF 4 SCROLL ===> PAGE STATUS FUNCTION ACTIVE ACTIVE ACTIVE ACTIVE
CMNUTL03-------------------COMMAND ===> REQ NAME RENAME TYPE _ SCR BAYU JCL _ REN BDCU NEWNAME JCL _ SCR BHFCOPY CPY _ SCR CMN$TRC CPY
******************************* Bottom of data ********************************
To exit this panel you can: Enter the requested fields and press ENTER Press PF3 or enter END in the Option line and press ENTER, Change Man will return you to the previous panel
Utility requests that have already been activated appear on this list with a status of ACTIVE. You can use this panel to delete any of these requests in the change package. If this package was created with the 'copied forward' option, then any utility requests appear on this list with a status of INACTIVE. Use this panel to activate or delete them.
Field COMMAND
Description Valid commands are REFRESH, CANCEL, LOCATE
LCMD (first column) A Activate (activate an inactive request) D - Delete (to delete the utility request) H - History I - Short History L - Locate
Commonly Asked Questions

Utility 66
User Training Guide
Question. Answer.
Can I delete a delete or rename request? Yes you can. Use the Utility Package List option to display and delete any utility requests in a change package.
Question.
When I issue the Scratch request on a component from the baseline library Change Man indicated a scratch, did the component actually get scratched? No the component did not get scratched. The utility requests are only proceeded after the change package has been approved and is done as the last part of the installation process.
Answer.
Exercises for Utility

Exercise #1: Delete any 2 components from the CPY Library Type, also Rename any component in the SRC Library Type, both from baseline.
Exercise #2
Display the utility requests from the package in exercise #1, then Delete 1 of the delete requests.
67
Utility
User Training Guide
Utility
68
User Training Guide
Checkout
Checkout Overview
After you have created a change package, you use Checkout to copy components from secured libraries, such as baseline or promotion, to Change Man staging libraries or to the user's personal PDS. When you checkout a component, the statistics are carried forward and the version number (the vv portion of vv.mm) is incremented. Change Man will add the checkout information to the statistics that make up the component's history. If you checkout to a valid change package ID, the component name is added to the package's component list. If another user checks out the same component into a different change package(s), Change Man will sent concurrent development notification messages to all parties concerned.
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. Some of these Restrictions, Rules, and Options are as follows; 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. 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. Checkout can include components that reside in promotion libraries (if any exist for a given application). You can check out components by selecting them from a list of Baseline or Promotion Library 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.
69
Checkout
User Training Guide
CHECKOUT OPTIONS Panel

This panel allows the user to choose and decide whether component selection lists are derived from the contents of your Baseline/Promotion Library or from your change package. To access this Panel: Select option 1 from the Primary Option Menu for Build, then Select option 5 on the Build Options Menu for Checkout
CMNMCKOT----------------------- CHECKOUT OPTIONS ----------------------------OPTION ===> _ PACKAGE ID ===> TEST000063 1 2 Base/Prom - Checkout from baseline or promotion libraries Package - Checkout package components
To exit this panel you can: Enter 1 or 2 in the Option line then press ENTER to proceed to next panel Press PF3 or enter END in the Option line and press ENTER, Change Man will return you to the previous panel
Field OPTION
Description 1 - To select from components residing in the baseline or promotion libraries 2 - To display components that are already defined to your Change Package through the copied forward package option. Enter the Change Package ID, or double check the package ID displayed is still the package you want to work with.
PACKAGE ID
CHECKOUT - Panel
Checkout
70
User Training Guide
CHECKOUT is used to copy components from the Baseline or Promotion libraries into a staging library or personal library. To access this Panel: Select option 1 from the Checkout Options panel
CMNCKOT1--------------------------- CHECKOUT --------------------------------OPTION ===> _ L - List libraries where component is located PACKAGE ID COMPONENT NAME LIBRARY TYPE LANGUAGE SOURCE LIBRARY ===> TEST000063 (Package name) ===> ________ ===> JCL ===> ===> 0 (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 ===> NO
To exit this panel you can: Enter the requested fields and press ENTER Enter the mandatory input field and then select from the displayed lists to complete the checkout request Press PF3 or enter END in the Option line and press ENTER, Change Man will return you to the previous panel
Field
Description
71
Checkout
User Training Guide
OPTION
Enter L to display a list of the promotion and baseline libraries where a component can be found. You must enter the Component Name, Library Type and leave the Source Library field blank. Enter the Change Package ID, or double check the package ID displayed is still the package you want to work with. Note: If you access this panel through the List option the Package ID field is not updateable. The name of the component to be checked out. In order to mask the selection list, you may use wild cards in this field (e.g. CMN* or CMN?0000). To checkout all the components enter * (be careful). Enter the Library type of the library you want to perform the checkout operation to. If you leave this field blank, Change Man will display a list of possible library types to select from. This field is required for source (SRC) or like-source components. Enter the name of the language in which the source is written. Leave this field blank to select from available language names for a component that Change Man has no history for. If the component has been compiled by Change Man before, it will assume the last compiled language, which can be overridden. Enter ? to specify the language of the designated procedure. When Change Man installs a change into baseline, it RIPPLES the baseline libraries. This means that Change Man keeps several backup versions of the component. The old versions are baseline -1, -2, -3, etc. To checkout components from the most current (production) version, enter 0. To checkout components from a previous version, enter the version number (e.g. -2). To checkout components from a promotion library, enter the level number (+1 - +99). Use the OPTION line to produce a list of libraries where the component exists. To checkout the components to a personal development library, enter P. To checkout the component to a Change Man staging library, enter an S. If you selected option P on the CHECK OUT TO field, place the personal dataset name in this field. If you selected P and you leave this field blank, Change Man builds a sequential dataset as default.
PACKAGE ID
COMPONENT NAME
LIBRARY TYPE
LANGUAGE
SOURCE LIBRARY
CHECK OUT TO
PERSONAL LIBRARY
Field
Checkout
Description
72
User Training Guide
LIBRARY DSORG
If you selected option P on the CHECK OUT TO field, enter the library's dataset organization PDS or SEQ.
CONFIRM REQUEST
Enter YES to be notified if the checked out components are going to overlay existing copies of the same component(s) in the target library (Staging or Personal). Also specify YES if you want to be notified of any concurrent development prior to checking out the component. Note: Entering NO will not inform you of all the above, also since this field is stored in your ISPF profile, you will continue to checkout with NO until you change it back to YES (be careful). Specify whether to checkout online 1 or in a batch job 2. YES - Will place a lock on the component within the package. This means that only the userid that checked out the component can stage it (edit or update it). No other user can stage the component within this package. NO - Will bypass locking of the component.
CHECKOUT MODE LOCK COMPONENT
NOTE: Batch checkout will not update the member's ISPF statistics. Batch checkout will also bypass the OVERLAY PRIOR STAGED MODULE Admin. Rule. If a component is locked by another user you must go to the stage package driven list (1.6.2) to UNLOCK (UC) the component prior to checkout.
73
Checkout
User Training Guide
CHECKOUT: PACKAGE COMPONENTS Panel

This function is used to checkout, browse, or list the history of a component to be checked out. Typically this option is used for a change package that was created with the Package To Copy Forward option. To access this Panel: Select option 2 from the Checkout Options panel
CHECKOUT: TEST000073 COMPONENTS --CHANGED LANGUAGE PROCNAME 19981130 075559 ASM 19981203 142806 ASM 19981130 075559 ASM 19981130 075559 ASM 19981203 150504 COBOL2 19981203 150939 COBOL2 CMNCOB2 ROW 1 TO 6 OF 6 SCROLL ===> PAGE ID REQUEST WSER92 WSER92 WSER92 WSER92 WSER92 WSER92
CMNCKOTS ---------------COMMAND ===> NAME TYPE STATUS __ ABC00015 SRC INACTIVE __ ACKLA SRC INACTIVE __ ASMBLDV3 SRC INACTIVE __ BHFCOB SRC INACTIVE __ CCCDB2SQ SRC INACTIVE __ CKLLOO2 SRC INACTIVE
******************************* Bottom of data *******************************
To exit this panel you can: Enter the requested fields and press ENTER Press PF3 or enter END or CANCEL in the Option line and press ENTER, Change Man will return you to the previous panel
Field COMMAND SHORT, or LONG.
Description Valid commands are REFRESH, CANCEL, SORT, LOCATE,
LCMD (first column) S - Select a component for checkout H - Display component history B - Browse a component D - Delete a component from the package SL - Display Source to Load relationship (Source components only) Note: Enter 'LONG' at the Command line to display additional member information, and 'SHORT' to return to the original member list.
Checkout
74
User Training Guide
Checkout Confirm Request If you entered YES to the Confirm Request Change Man will inform you of any overlay or concurrent development. Several different warning and confirmation panels will be displayed throughout the lifecycle of the package. During the checkout process, and depending on the circumstances at the time a checkout is attempted, one or several of the following panels may be displayed: Confirm Checkout Request: This panel informs you that the component(s), which you are checking out, exist in other packages. The panel also allows you to CANCEL the checkout operation. To continue the checkout just press ENTER. To CANCEL the checkout enter CANCEL in the Command line and press ENTER. PF3 still performs the checkout.
CMNCMPSW ------------------------- CMNEX001.SRC ------------- 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 TEST000018 TEST000017 TEST000002 STA DEV DEV DEV PROMOTION VV.MM LAST ACTION 01.00 2000/01/01 08:20 01.00 1997/11/10 10:32 02.01 1997/09/26 08:17 SIZE PROCNAME ID CMNHASM WSER124 CMNHASM WSER124 147 CMNHASM WSER124
****************************** Bottom of data *******************************
If you continue with the checkout of the component, Change Man sends a MVSSEND message to all the other developer(s) informing them that you have checked out a component that exists in their package. In this way, Change Man is constantly alerting the developers of what concurrent development is in the application. It still remains the responsibility of the individual developers to communicate amongst themselves regarding the resolutions of the various versions of the component.
An example of the MVSSEND messages is:
CMN2445I-Checkout conflict;CMNEX001.CBL;FOR TEST000010;95/01/20@16:15-WSER18
Overlay Warning: This panel appears when you are about to overlay a component that is
75
Checkout
User Training Guide
already in your package and does not match the version you are about to checkout. The panel shows the TSO ID of the person who last changed the component you are about to overlay.
CMNCKWTP ---------------- CHANGE MAN CHECKOUT WARNING -----------------------COMMAND ===> ****************************************************************************** * Checking out component CMNEX001 will overlay WSER18'S version. * * * * INSTRUCTIONS: * * * * Press ENTER to check out this component * * Enter END command to cancel request. * * * ******************************************************************************
Confirm Delete Request: Any delete requests while in checkout option 2 (Checkout package components), Change Man will present the Confirm Delete Request panel. This panel gives you the option of verifying the component name and reconsider your request. Press ENTER to complete the delete request. Press PF3 or enter CANCEL or END in the Command line then press ENTER to cancel the delete request.
CMNSTG13 ------------------ CONFIRM DELETE REQUEST -------------------------COMMAND ===> PACKAGE ID: COMPONENT NAME: COMPONENT TYPE: LANGUAGE: STATUS: CHANGED DATE: CHANGED TIME: PROCEDURE NAME: TSOID: TEST000001 CMNEX001 SRC ASM CHECKOUT 951002 193824 CMNASM WSER18
Press ENTER to process; Enter END command to cancel request.
Checkout
76
User Training Guide
Commonly Asked Questions Question. How does checkout from promotion +1 or higher work? What happens if the component I checked out gets changed in the package I checked it out from? Or, I change the component and install to baseline, will the other package overlay my changes when it goes to baseline? If the component does not change in the package you checked it out from, then there are no out-of-synch problems. If however the component does change in the package you checked it out from, then there can be an OUT-OF-SYNCH situation. If the first package installs to baseline, then the next time you go to edit the component you will get a COMPONENT OUT-OF-SYNCH message. Your changes will not be saved and you must checkout the component from baseline. If you have no changes to make then Audit will catch the out-of-synch condition.
Answer.
Exercises for Checkout
Exercise #1:
Check out a JCL component to a Change Package, check it out to the staging library, from the 0 current version of baseline, in online mode.
Exercise #2:
Check out a source component to a Change Package, check it out to the staging library, from the -1 version of baseline and lock the component.
Exercise #3:
Check out all the source component to a Change Package that start with A*, from 0 current version of baseline.
Exercise #4:
Create a new Change Package with the copy forward option. You can use the package from exercise #1 as the copy forward package. Then check out all the components from the copied forward package to this new package.
77
Checkout
User Training Guide
Checkout
78
User Training Guide
Stage
Stage Overview
Stage is where developers will spend most of their time in the Change Man lifecycle. Stage or staging a component is where you will edit a component, compile and link edit a program, or change the status of other components like JCL. Also in Stage you can introduce new components into your application. During the checkout process, if any source or like-source components were checked out, a language name was specified or assumed. Based on this language name, Change Man submits the job to compile the component(s). If the component(s) are non-source, Change Man may simply mark the component as ACTIVE, which indicates that it is ready to move on to the next step. If the component(s) were checked out to a personal library, Change Man will copy the component into a Change Man staging library. Your Change Man administrator can effect how the Stage process will work. They will have chosen 1 of the following parameters: Stage Rule 1 - 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). Stage Rule 2 - Allows only users who have been defined (by the local administrator) to a special entity by their TSO ID can Stage new components. Otherwise, they can only Checkout and Stage components that are associated with a change package.
Stage Rule 3 - Does not allow you to Checkout and Stage new components, only ones that already exist in your Baseline Library. This effectively disables Development Driven Staging.
79
Stage
User Training Guide
STAGE OPTIONS - Panel

This panel displays which stage options are available and allows the user to select the stage option they want to use with their package. To access this Panel: Select option 1 from the Primary Option Menu for Build, then Select option 6 on the Build Options Menu for Stage.
CMNSTG00 ----------------------- STAGE OPTIONS -----------------------------OPTION ===> _ PACKAGE ID ===> TEST000074 1 2 3 Dev Package Parms - Stage components from development libraries - Process package components - Specify component list selection criteria
To exit this panel you can: Enter 1, 2 or 3 in the Option line then press ENTER to proceed to next panel. Press PF3 or enter END in the Option line and press ENTER, Change Man will return you to the previous panel.
Field OPTION
Description 1 - To stage the package components from the development ibraries, or in other words, from libraries outside of Change Man control. This is the way you introduce new components into Change Man. 2 - To display and work with the components already in your change package. 3 - To display and work with the components already in your change package also, except this option presents a panel which allows you to add in selection criteria to narrow down the resultant component list. Enter the Change Package ID, or double check the package ID displayed is still the package you want to work with.
PACKAGE ID
Stage
80
User Training Guide
STAGE: FROM DEVELOPMENT Panel

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, the user has checked out a component without package association and decides to include the modification in an existing change package. In these two cases, the user would use the Stage from Development option. The Stage from Development option enables the user to copy components into the change package, that in most cases do not exist in the baseline libraries. Use this panel to specify the dataset name of where the new components are so that Change Man can perform the copy process. If the component being staged is a source library type, when Change Man will display the compile and link panel and the user can issue the compile and link if desired. If not then the user can simply cancel it. To access this Panel: Select option 1 from the Stage Options panel.
CMNSTG02 ------------------ STAGE: FROM DEVELOPMENT -------------------------COMMAND ===> PACKAGE ID: TEST000074 ISPF LIBRARY: PROJECT ===> GROUP ===> TYPE ===> MEMBER ===> STATUS: DEV INSTALL DATE: 19981230
(Blank or pattern for list; * for all members)
OTHER PARTITIONED OR SEQUENTIAL DATASET: DATASET NAME ===> dataset name(member) ORGANIZATION ===> (PDS, SEQ, PAN, LIB, OTH) LIBRARY TYPE LANGUAGE STAGE NAME CONFIRM REQUEST STAGE MODE SUPPRESS MESSAGES ===> ===> ===> ===> YES ===> 1 ===> 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)
To exit this panel you can: Enter the required fields and press ENTER to proceed to next panel, or leave some of the fields blank and select from the resultant lists and press ENTER. Press PF3 or enter END in the Option line and press ENTER, Change Man will return you to the previous panel. Description
Field
81
Stage
User Training Guide
ISPF LIBRARY
Specify the dataset name the same way as it would be on the ISPF EDIT panel. Leave the member name field blank for a list of the members within the dataset, or enter the exact component name. Use this field to enter the dataset name that contains the components to be staged. This field is most commonly used for datasets which have other than three qualifiers. If you are copying all the components, append * to the dataset name. Enter the type of component to be staged (e.g. SRC, JCL, etc.). If the component is SRC or like-source, you must specify the language in which it was developed (e.g. COBOL2). When a component is to be staged from a sequential dataset, it must be given a component name. For a PDS, the component name is the member name but you may change the component name by specifying a new name in this field. A component in a sequential dataset has no component name, only a dataset name. Enter a name for the component in this field. This field is required for sequential datasets. Enter YES to be notified if the staged components are going to overlay existing copies of the same component(s) in the staging library. Also specify YES if you want to be notified of any concurrent development prior to staging the component. Enter 1 to stage online. Enter 2 to stage in batch mode. Enter YES if you do not wish to receive any messages during batch staging.
OTHER PARTITIONED or SEQUENTIAL
LIBRARY TYPE LANGUAGE
STAGE NAME
CONFIRM REQUEST
STAGE MODE SUPPRESS MESSAGES
Stage
82
User Training Guide
If you leave the Library Type field blank then Change Man will supply a list of possible library types to select from. Place an S beside the library type you want to work with. In the example below you see the generated Library type panel with the user selecting to stage the JCL library.
CMNSTG08 ---------------- LIBRARY TYPE SELECTION LIST ----COMMAND ===> _ _ _ _ _ S _ _ _ _ _ _ _ _ _ LIB CPY CTC DBB DBR DOC JCL LCT LOD LST MPC OTH PKG PRC SRC VLD DESCRIPTION Copybooks Control Cards DB2 Bind Control Statements - Plans DB2 Database Request Modules Documentation Job Control Language Linkedit Control Cards Load Modules Compressed Compile Listings Copybooks - CICS Maps OTHER library type DB2 Bind Control Statements - Packages JCL Procedures Source Code Load Modules ROW 1 TO 15 OF 15 SCROLL ===> PAGE
******************************* Bottom of data *******************************
If you leave the member field blank or do not include a member name in the dataset name then Change Man will display all the members in the specified dataset name. Place an S beside the component you want to stage or copy into the package. In the example below you can see the dataset member list with the user selecting 1 of the members. Included is the standard PDF statistics for each of the components.
CMNSTG03 M - WSER92.CNTL ------------------------------------ ROW 1 COMMAND ===> SCROLL NAME FUNCTION VV.MM CREATED CHANGED SIZE INIT S ALTER 01.02 1998/01/29 1998/01/30 15:45 28 15 _ TEMP 01.00 1998/10/06 1998/10/06 09:55 26 26 TO 2 OF 2 ===> PAGE ID WSER200 WSER200
******************************* Bottom of data *******************************
If the user selects a SRC type library then Change Man will display the compile and link panel. See Stage option 2 (Package) for example of this panel.
83
Stage
User Training Guide
STAGE: PACKAGE COMPONENTS -Panel

This panel is used to display and process the components in the change package. Process means you can edit, compile, delete, browse, display history information, etc. This is where user will spend most of their time in Change Man making all the changes or enhancements to the individual components. To access this Panel: Select option 2 from the Stage Options panel and press ENTER.
CMNSTG01----------------- STAGE: TEST000074 COMPONENTS ---- ROW 1 TO 11 OF 11 COMMAND ===> SCROLL ===> PAGE NAME TYPE STATUS CHANGED PROCNAME ID REQUEST __ A JCL ACTIVE 19981204 111123 WSER92 __ ABC00015 SRC INACTIVE 19981130 075559 WSER92 __ ABC00017 SRC INACTIVE 19981130 075559 WSER92 __ ACKLA SRC CHECKOUT 19981204 081909 WSER92 __ ALTER SRC INCOMP 19981207 105438 WSER92 __ ASMBLDV3 SRC INACTIVE 19981130 075559 WSER92 __ BHFCOB SRC CHECKOUT 19981204 075920 WSER92 __ CCCDB2SQ SRC INACTIVE 19981203 150504 WSER92 __ CKLA SRC CHECKOUT 19981204 081909 WSER92 __ CKLLOO2 SRC INACTIVE 19981203 150939 CMNCOB2 WSER92 __ CLOOB SRC CHECKOUT 19981204 083040 WSER92 ******************************* Bottom of data *******************************
To exit this panel you can: Enter a Component line command and press ENTER to proceed to next panel. Press PF3 or enter END or CANCEL in the Command line and press ENTER, Change Man will return you to the previous panel.
Field COMMAND
Description Valid commands are REFRESH, CANCEL, SORT, LOCATE, SHORT, or LONG.
Stage
84
User Training Guide
Possible Component Line Commands: To display the list of component line commands enter any invalid line command beside any component listed (i.e. zz) and the following panel will be displayed. You can enter the desired component Command line in the Option line of this panel and Change Man will apply this command to the component you entered the invalid line command on. Or you can PF3 back to the Package Components list and enter it there.
CMNSTG17---------------- VALID STAGING SELECTION CODES ----- INVALID SELECTION OPTION ===> PACKAGE ID: TEST000074 COMPONENT: A LIBRARY TYPE: JCL
Select a valid code. The component will be processed from this panel. B BA BD D E EA ED H R ST SB SL UL UC LC Browse component from personal or staging library Browse component activity file Browse component general description Delete component from staging library Edit and stage component from personal or staging library Edit and stage component activity file Edit component general description Display component history Recompile component from the staging library Stage component into the staging library (S will also work) Stage component in batch mode Display Source to Load relationship Display Component Userid Work List (If turned on by administrator) Unlock Component to allow for Checkout/Stage Lock Component to disallow Checkout/Stage
Press ENTER to process or enter END command to exit.
Field NAME TYPE
Description The member name of the component. The library type of the component. Common component library types are, SRC (source), CPY (copybook, CTL (control cards), DBB (DB2 bind cards). The current status of the component in the change package. Common component statuses are: CHECKOUT The component has been checked out from a baseline or promotion library but has not been modified yet. INACTIVE The component was "copied forward" from another change package but has not been checked out yet.
STATUS
85
Stage
User Training Guide
Field
Description INCOMPLETE A compile and/or link edit has been submitted for the component and it has not completed execution yet or it has failed. ACTIVE The component has been edited (if it is non-source), successfully compiled/linked (source), or copied successfully from a development library into the change package (development driven staging).
CHANGED PROCNAME
The date and time that the component was last changed. The procedure that was used to compile/link the program. This is a Change Man skeleton procedure. The TSO ID of the last user to modify the component. The last request that was performed for the component, i.e.: STAGE, EDIT, etc.
ID REQUEST
Additional Processing Depending on the processing you select on the component, other additional panels will be initiated. The most common process is an edit. The edit process on any component will create a Change Man temporary file, which you can edit. This temporary file is where you can make all your changes or enhancements. Once complete press PF3 to return and save the changes back to your change package. Change Man will then display a comparison report (see below) which shows you all the differences between the last staging library version of the component to the temporary file you just edited. Change Man will then display a Comparison Report Distribution panel (see below) which enables you to print the comparison report. If the component you have changed is a source (SRC) type component, then Change Man will automatically give you the option of doing a compile and link (see below). Other processes will return to the Package List panel with the status of the component being changed to active. Any component delete request will display a Confirm Delete Request panel (see below). Component stage requests also display a Confirm Stage Request panel (see below). During any processing on any component in the package, Change Man will also notify you of any concurrent development or if other packages contain the same component (see below).
Stage
86
User Training Guide
Comparison Report + Report Distribution The next two panels appear when you have edited your component in Stage. The first panel shows what changes you have made in the current edit session. The second panel gives you the opportunity to print a hardcopy report of the edit changes.
Menu Utilities Compilers Help ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss BROWSE WSER18.WSER18.CMN97316.T2147244.OUTLIST Line 00000000 Col 001 080 Command ===> Scroll ===> PAGE ********************************* Top of Data ********************************** S E R C M P A R (MVS-3.1.1 - 1997/213) SERSTAR6 WEDNESDAY NOV SYSUT1=WSER99.CMN.U416ALL.TEST.#000001.SRC(CMNEX001),SYSUT2=WSER18.WSER18.CMN973 *********************************************************************** * CHANGE MAN APPLICATION - EXIT MODULE 001 * * Purpose: This exit is invoked when updating package information, ++++++++|+++.++++1++++.++++2++++.++++3++++.++++4++++.++++5++++.++++6++++.++++7 D * the exit controls who can update the package info. --------|---.----1----.----2----.----3----.----4----.----5----.----6----.----I * this exit controls who can update the package info. ++++++++|+++.++++1++++.++++2++++.++++3++++.++++4++++.++++5++++.++++6++++.++++7 * * Question: Can the requested package be updated by this user? * * Answer in R15(IXP$RC): 0=no change to current status. * 4=set input to yes for update. SER71I - END OF TEXT ON FILE SYSUT1 SER72I - END OF TEXT ON FILE SYSUT2
This panel will be displayed automatically to prompt you for the disposition of the Comparison report.
----------------------- COMPARISON REPORT DISPOSITION -----------------------OPTION ===> REPORT DATASET NAME: REPORT DISPOSITION 'WSER18.WSER18.CMN97316.T2147244.OUTLIST' ===> D D K PD PK Delete Keep Print and Delete Print and Keep
JOB STATEMENT INFORMATION IF DISPOSITION IS PD OR PK: ===> //WSER18 JOB (@),'CHANGE MAN', <=== CHANGE ACCORDINGLY_____ ===> // CLASS=O, <=== CHANGE ACCORDINGLY_____ ===> // NOTIFY=WSER18, <=== CHANGE ACCORDINGLY_____ ===> // MSGCLASS=R <=== CHANGE ACCORDINGLY_____ Press ENTER or END to process Enter CANCEL command to exit without saving changes.
87
Stage
User Training Guide
STAGE: COMPILE AND LINK - Panel Use this panel to indicate how a source code module is to be compiled or compiled and link edited.
CMNSTG04 ---------------- STAGE: COMPILE AND LINK EDIT ----------------------COMMAND ===> PACKAGE ID: TEST000074 STAGED NAME: LIBRARY TYPE: LANGUAGE: DATASET NAME: COMPILE PROCEDURE COMPILE PARMS LINK EDIT PARMS DB2 PRE-COMPILE OTHER OPTIONS STATUS: DEV INSTALL DATE: 19981230
ALTER SRC - Source Code ASM WSER200.CMN.TRAIN.USER.#000074.SRC ===> CMNASM ===> ===> ===> NO ===> YES (Blank for list; ? for designated procedure) (Y/N) (Y/N to display other options)
JOB STATEMENT INFORMATION: ===> //WSER92I JOB (XXXX,333),WSER92,CLASS=E,MSGCLASS=3,____________________ ===> // TIME=2,REGION=4M,NOTIFY=WSER92________________________________ ===> //*JOBPARM SYSAFF=ESA1__________________________________________________ ===> //*_____________________________________________________________________ Press ENTER to process; Enter END command to exit.
Field PACKAGE ID STATUS INSTALL DATE STAGED NAME
Description The ID of the Change Package that you are working with. The current Change Man status of the Change Package. The date that the Change Package is to be installed. The component that is being staged. If you are staging a component from a development library into Change Man and you are renaming the component, the staged name is the "new name" of the component. The type of component that you are staging. The language name that was assigned to the component. The name of the dataset that contains the component that you are staging. This will either be a Change Man package staging library or a development library.
LIBRARY TYPE LANGUAGE DATASET NAME
Stage
88
User Training Guide
Field COMPILING PROCEDURE
Description The Change Man compiling procedure that will be used to compile/link the program. If only one procedure is available for this language, this field will be in "browse only" mode. You may type in compile parms for the program. If this program was previously compiled within Change Man, the compile parms found in component history will be displayed. You may type in link edit parms for the program. If this program was previously linked within Change Man, the link edit parms found in component history will be displayed.
COMPILE PARMS
LINKAGE EDIT PARMS
DB2 PRE-COMPILE Enter "YES" if this program is a DB2 program. Enter "NO" if this program is not a DB2 program. OTHER OPTIONS Enter "YES" if you need to display additional user options such as CICS pre-compile, EZTRIEVE, etc. Your Global Change Man Administrator will define available options for you.
The User Option function is used to incorporate up to twenty additional user options within a Change Man compiling procedure. The variables are passed to the file tailored skeleton. Specifying 'Y' will cause the user option to be expanded within the procedure, 'N' or BLANK will cause the user option to be suppressed. This panel gets customized a great deal in most shops.
CMNUSR01 ------------------- STAGE: USER OPTIONS ---------------------------COMMAND ===> NAME: ALTER 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 ===> ===> ===> ===> ===> ===> ===> ===> ===> ===> LANGUAGE: ASM IMS DLITxxx ENTRY DROP INCLUDE STMTS USER OPTION 06 USER OPTION 08 USER OPTION 10 USER OPTION 12 USER OPTION 14 USER OPTION 16 USER OPTION 18 USER OPTION 20 ===> ===> ===> ===> ===> ===> ===> ===> ===> ===>
Use Y or N to select or deselect additional processing options; Press ENTER to continue; Enter END command to exit.
89
Stage
User Training Guide
Additional Compile and Link Processing
Once the compile has completed, Change Man can automatically populate a compressed listing library (LST) to contain the output from the compilation. This listing may be viewed on-line or printed. During the link process Change Man inserts information into the Load module created, specifically the IDR record. Change Man uses SET SSI (an IBM time stamp) to update the IDR record and link the source and load to ensure integrity. This IDR record also contains the program ID and the Change Package ID that this module was updated in. Change Man's LCT processing provides the developer with the ability to specify linkage edit control parameters such as INCLUDEs for specific subroutines, ENTRY statements, and a name card. When using LCT processing you must specify a name card in each member. This name card will control the name of the resultant load module. If LCT processing is not required, Change Man dynamically constructs the linkage edit name card to be the same name as the source.
CONFIRM DELETE REQUEST This panel allows for the confirmation of the action chosen for this component (i.e. delete, restage an ACTIVE component, etc.)
CMNSTG13 ------------------ CONFIRM DELETE REQUEST ----------------COMMAND ===> PACKAGE ID: COMPONENT NAME: COMPONENT TYPE: LANGUAGE: STATUS: CHANGED DATE: CHANGED TIME: PROCEDURE NAME: TSOID: TEST000074 ASMBLDV3 SRC ASM INACTIVE 19981130 075559 WSER92
Valid responses are, press the ENTER key to confirm the request, or enter PF3 or enter CANCEL in the Command field to cancel the request.
Stage
90
User Training Guide
CONFIRM STAGE REQUEST This panel allows for the confirmation of the action chosen for this component (i.e. delete, restage an ACTIVE component, etc.)
CMNSTG13 ------------------ CONFIRM STAGE REQUEST ---------------------------COMMAND ===> PACKAGE ID: COMPONENT NAME: COMPONENT TYPE: LANGUAGE: STATUS: CHANGED DATE: CHANGED TIME: PROCEDURE NAME: TSOID: TEST000074 ALTER SRC ASM INCOMP 19981207 105438 WSER92
Concurrent Development panel This panel will appear every time you make a change to a component that exists in another package. This is to notify you that there may be concurrent development within the application.
CMNCMPSW ------------------------ CLOOB.SRC ---------------COMMAND ===> 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 USER000075 DEV 02.00 1998/12/04 09:31 WSER92 USER000074 DEV 02.00 1998/12/04 08:30 24 WSER92 USER000063 DEV 02.00 1998/12/03 17:08 24 WSER200 ****************************** Bottom of data ******************************* ROW 1 TO 3 OF 3 SCROLL ===> PAGE
91
Stage
User Training Guide
COMPONENT LIST PARAMETERS Panel

This panel is used to filter the stage package driven list that is displayed to the user. The list can be filtered down by component name, component type language, component status, changed from date, changed to date, compile procedure and TSO-ID. To access this Panel: Select option 3 from the Stage Options panel and press ENTER.
CMNSTG12 ----------------- COMPONENT LIST PARAMETERS -----------------------OPTION ===> PACKAGE ID: TEST000074 SPECIFY SELECTION CRITERIA: COMPONENT NAME ===> COMPONENT TYPE ===> LANGUAGE ===> COMPONENT STATUS ===> CHANGED FROM DATE TO DATE COMPILE PROCEDURE TSOID SHORT OR LONG DISPLAY CONFIRM REQUEST SUPPRESS MESSAGES COMPARISON REPORT ===> ===> ===> ===> ===> ===> ===> ===> STATUS: DEV INSTALL DATE: 19981230
(1-Active, 2-Incomplete, 3-Checkout, 4-Inactive) (YYYYMMDD) (YYYYMMDD) S YES YES YES (S-Short, L-Long) (Y/N) (Y/N; applies to batch stage) (Y/N; applies to edit in stage)
To exit this panel you can: Enter a Component line command and press ENTER to proceed to next panel. Press PF3 or enter END or CANCEL in the Command line and press ENTER, Change Man will return you to the previous panel.
Field PACKAGE ID STATUS INSTALL DATE
Description The ID of the Change Package that you are working with. The current Change Man status of the Change Package. The date that the Change Package is to be installed.
Stage
92
User Training Guide
Field STAGED NAME
Description The component that is being staged. If you are staging a component from a development library into Change Man and you are renaming the component, the staged name is the "new name" of the component. If known, enter the name of the component to be listed. Enter the type of the components to be displayed. For example, enter JCL to list all JCL components. Enter the language for components to be displayed. For example, enter COBOL2 to view a list of all components written in COBOL2. Enter the status of components to be displayed. Enter a range of dates to view a list of all components that have been changed within a specified period. Enter the compiling procedure for the components to be displayed. To display all components that belong to a specific userid, enter the userid in this field. Select from the short or long method. The long method displays the name of the dataset from which the component was checked in or checked out to. To be notified if the staging will overlay an existing component, enter Yes or No. This field also controls whether a compare listing is produced when performing an edit during staging. Enter YES if you do not wish to receive any 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.
COMPONENT NAME COMPONENT TYPE
LANGUAGE NAME
COMPONENT STATUS CHANGED FROM DATE/TO DATE COMPILE PROCEDURE
TSOID
SHORT OR LONG DISPLAY
CONFIRM REQUEST
SUPPRESS MESSAGES
COMPARISON REPORT
93
Stage
User Training Guide
Stage CONFIRM REQUEST Field The Confirm Request option on stage panels appears to offer some processing efficiencies. However, it has a broader effect than might be expected. The Stage Confirm Request option can be set on either of the following panels: Stage: From Development (CMNSTG02) , Option 1.6.1 Component List Parameters (CMNSTG12), Option 1.6.3 If the Stage Confirm Request is set to YES, one or several of the following panels may be displayed, depending on circumstances at the time a stage or some other action is attempted from a stage panel.
Danger in Setting Stage Confirm Request to NO If you set the Stage Confirm Request to NO the following will occur: All of the warning and confirmation panels shown above will be suppressed. The Confirm Request option will be set to NO for all stage operations and panels no matter where it was entered, even for the Stage: (package) Components panel where there is no opportunity to set the Confirm Request option. NO will be stored in your ISPF profile, and the Stage Confirm Request will default to NO until you enter YES in the Stage: From Development panel or the Component List Parameters panel. Developers are sometimes impatient with the edit compare display and the Comparison Report Distribution panel. If the Stage Confirm Request Option is set to NO to suppress these panels, other important warnings may be missed. For example, it is easy to make a keying error and enter D instead of S beside a component in a component list. If Stage Confirm Request is set to NO, you will immediately delete the component instead of opening it for edit.
Stage
94
User Training Guide
Commonly Asked Questions Question. Can you turn off the comparison report from being displayed every time you exit an edit session? Yes! In the Component List Parameters panel (S3), you can set the Comparison Report filed to NO.
Answer.
Exercises For Staging

Exercise #1: Create a new change package and checkout a JCL component into the package from baseline. Then Stage the component using Stage Option Package. Edit the component and reply to the displayed panels. Note: Observe how the status of the component changes.
Exercise #2:
Checkout a source program from baseline into the package from exercise #1. Then Stage the source using Stage Option Package. Edit the source component and issue the compile and link. Again watch how the components status changes. Once the compile and link is complete display the source to load relationship of the source component.
Exercise #3:
Stage a new component into your application. Use the Stage Option Dev to stage the new component into your change package.
95
Stage
User Training Guide
Stage
96
User Training Guide
Listing
Listing Overview
The Browse Compressed Listing function allows you to browse a compile/link edit listing of a source component compiled by Change Man. Change Man has a facility which allows you to store the output from the compile/link edit procedures within the library type LST. This eliminates the need to keep printed copies of the listings. As the typical compile/link edit listing is very large, Change Man stored these listings in a compressed format. The Browse Compressed Listing facility is used to decompress these listing into a temporary file for viewing and or printing. The disposition of the decompressed listing is specified by the user. A listing can be narrowed down by application, package ID and/or date.
BROWSE COMPRESSED LISTINGS - Panel

Use this panel to select the compressed listing you are interested in viewing. To access this Panel: Select option 1 from the Primary Option Menu for Build, then Select option L on the Build Options Menu for Listing.
CMNBLST0 ----------------- BROWSE COMPRESSED LISTINGS -----------------------OPTION ===> SPECIFY SELECTION CRITERIA: PACKAGE ID ===> TEST000076 APPLICATION ===> TEST COMPONENT NAME LIBRARY TYPE FROM DATE TO DATE ===> ===> 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
To exit this panel you can: Enter the required fields and press ENTER to proceed to next panel. Press PF3 or enter END in the Option line and press ENTER, Change Man will return you to the previous panel.
97
Listing
User Training Guide
Field PACKAGE ID
Description Enter the Change Package ID, or double check the package ID displayed is still the package you want to work with. Note: If the Application Field is entered than the Package ID field is ignored. Specify the application if you also wish to display the baseline versions of the compressed listings. If known, enter the name of the component to be listed.
APPLICATION
COMPONENT NAME LIBRARY TYPE
Enter the staging library type for the compressed listings. The default is LST. Enter a date in YYYYMMDD format to limit the selection list to only include listings generated from that date through the current date. Enter a date in YYYYMMDD format to limit the selection list to only include listings generated prior to that date.
FROM DATE
TO DATE
PROMPT FOR LISTING DISPOSITION
If you wish to have the option of printing the uncompressed listing after you have viewed the list, Enter YES. The default is NO.
The components, which satisfy the fields entered on the previous panel, will be displayed on the following panel.
CMNBLST1------------------ BROWSE COMPRESSED LISTINGS ------- ROW 1 TO 7 OF 7 COMMAND ===> SCROLL ===> PAGE Press END command to exit. PACKAGE ID: TEST000074 STATUS: DEV INSTALL DATE: 19981230
NAME LEVEL VV.MM CREATED CHANGED SIZE INIT ID _ PROGA STAGING 01.02 1997/07/29 1997/07/29 15:11 500 1133 SERSTAR _ PROGA BASE-00 01.02 1996/07/29 1996/07/29 15:11 482 1133 SERSTAR _ PROGA BASE-01 01.00 1995/11/28 1995/11/28 15:31 355 355 SERSTAR S PROGC BASE-00 01.00 1996/01/31 1996/01/31 14:14 16 16 SERSTAR _ PROGCKL BASE-00 01.00 1995/10/12 1995/10/12 13:45 338 338 SERSTAR _ PROGC1 BASE-00 01.02 1995/01/11 1995/01/11 14:47 407 407 SERSTAR _ PROGC2 BASE-00 01.02 1995/01/11 1995/01/11 14:43 335 335 SERSTAR _ PROGD BASE-00 01.00 1995/11/29 1995/11/29 12:47 418 418 SERSTAR ****************************** Bottom of data ********************************
Listing
98
User Training Guide
Enter S beside the program you would like Change Man to display the decompressed compile/link edit listing, then press ENTER to display next panel. Press PF3 or enter END or CANCEL in the Command line and press ENTER, Change Man will return you to the previous panel.
Field NAME LEVEL
Description The name of the component that was compiled/link edited. The library that contains the compressed listing. BASE-00 contains current production, BASE-01 contains the prior version, etc. STAGING contains the copy that resides in your change package. This is a Change Man tracking version number. This is the information gathered from PDS stats.
VV.MM CREATED/CHANGED/ SIZE/INIT ID
This is the Change Man Started Task ID
99
Listing
User Training Guide
Compile/Link Edit Listing When you select a compressed listing for Browse, Change Man retrieves the component and expands the listing into a temporary ISPF dataset. This dataset is shown at the top of the panel. Due to the size of the compressed listing (131 bytes wide), we are unable to display the entire listing on one panel. Therefore the listing will be displayed and explained in sections.
-BROWSE - WSER24.WSER24.CMN94152.T1438303.OUTLIST -- LINE 00000000 COL 001 080 COMMAND ===> SCROLL ===> PAGE ******************************** TOP OF DATA ********************************* ****************************************************************************** * DDNAME: WRITE.SYSPRINT * ****************************************************************************** CMNWRITE (MVS-4.1.6) 03/29/94 09 WEDNESDAY JUNE 1, 1997 14:24:21 PARM='SUBSYS=0' PARM interpretation: Change Man subsystem '0' Expansion of uncovered COPY/Include variations SYSIN: TYP:CPY/WSER23.CMNO.PROMO1.COPYLIB SYSIN: TYP=CPY/WSER23.CMNO.BASE0.COPYLIB SYSIN: TYP=SCP/WSER99.SER410.COPYLIB SYSIN: TYP=MPC/WSER23.CMNO.BASE0.COPYLIB SYSIN: CMP=CMNEX001.SRC SYSIN: LNG=ASM SYSIN: PKG=TEST000237 CMN7500I - Attempting to initiate dialog with started task. CMN1400I - Session established with Change Man started task.
Section 1 Prior to any pre-compiler or compiler step, Change Man executes program CMNWRITE. CMNWRITE scans your source code, detects and optionally expands COPY members and variations of INCLUDES. Nesting of COPYBOOKs and INCLUDEs is supported up to 99 levels. The first section of the listing shows the search order that Change Man has built for your SYSLIB concatenation. The libraries and the order are based on the configuration that has been built by your Change Man Administrator. Change Man parses your source code for COPY/INCLUDE statements and will search the library concatenation for those members.
Listing
100
User Training Guide
-BROWSE - WSER24.WSER24.CMN94152.T1438303.OUTLIST -- LINE 00000000 COL 001 080 COMMAND ===> SCROLL ===> PAGE Library search order: PDS/SYS94152.T142411.RA000.WSER24M.NULLPDS PDS/WSER23.CMNO.PROMO1.COPYLIB (CPY) PDS/WSER23.CMNO.BASE0.COPYLIB (CPY) PDS/WSER23.SER410.COPYLIB (SCP) PDS/WSER23.CMNO.BASE0.COPYLIB (MPC) LV -MEMBER--- VV.MM -CREATE- -LAST CHANGED- SIZE INIT -USERID- L I B R A R C O M P O N E N T D 00 CMNEX001 15.01 92/03/04 1994/06/01 14:22 64 68 WSER24 WSER99.TECH 01 CPYUCADS 01.01 92/02/29 1994/02/08 07:31 489 488 WSER34 WSER23.CMNO 02 CPY$ACPM 01.01 92/01/10 1994/02/08 07:32 133 133 WSER34 WSER23.CMNO 01 CPYEXITS 03.01 92/01/10 1994/02/08 07:31 21 21 WSER34 WSER23.CMNO CMN1410I - Session terminated with Change Man started task.
Section 2 (columns 1 - 80) The second section of the listing displays the libraries that Change Man searched to find the COPY/INCLUDE members. This section also shows the developer where all of the components, that built the object module, were found by Change Man. The LV field shows the level of the included members. In the above example these levels are as follows: Level 00 - Component CMNEX001 is the calling source component in the change package. Level 01 - Component CPYUCADS is a called copybook. Level 02 - Component CPY$ACPM is a nested copybook which is a copybook that is called by another copybook. Level 01 - Component CPYEXITS is a called copybook.
101
Listing
User Training Guide
-BROWSE - WSER24.WSER24.CMN94152.T1438303.OUTLIST -- LINE 00000000 COL 001 080 COMMAND ===> SCROLL ===> PAGE (CPY) (CPY) (SCP) (MPC) INIT -USERID- L I B R A R Y N A M E---------------------- ---FINGERPRINT--C O M P O N E N T D E S C R I P T I O N ---(IF ANY)------------------------68 WSER24 WSER99.TECH.SERENA.#000001.SRC CC1F2D61-00000E04 488 WSER34 WSER23.CMNO.BASE0.COPYLIB 3655E2F4-00006C3C 133 WSER34 WSER23.CMNO.BASE0.COPYLIB 79135A46-00001DC6 21 WSER34 WSER23.CMNO.BASE0.COPYLIB 34B40005-00000474 d task.
Section 2 (columns 53 - 132) Columns 53 - 132 of the listing display the libraries where Change Man found the included members. This section also shows the internal Change Man generated fingerprint for each component. This fingerprint is written into the Change Man package master file and is verified during the Audit process. The remainder of the listing contains the precompiler, compiler and link edit output from your compile.
Listing
102
User Training Guide
Audit
Audit Overview
The Audit function or process plays a very important part in the life cycle of a Change Package. Its function is to inspect the contents of the Package Staging libraries of an evolving Change Package with respect to Baseline libraries. The audit looks for situations such as package components that have changed in the Baseline libraries since the time you checked them out into your package. Meaning the version in your package is no longer the most current, or a package containing a LOD component that does not match its SRC component. These situations are called out-of-synch conditions. Audit provides Change Man the ability to help you detect code that is inconsistent with your development procedures. Audit has an Audit rule, or parameter, which is set by the Administrator. This Audit rule can be set between 0 5. If the Audit Rule has been set to 0, then Audit is totally optional, meaning you are not required to run Audit. If the Audit rule has been set between 1 5, then Audit must be run prior to the Freeze process. The Audit process runs as a batch job on the MVS system. It produces an Audit Report, which lists all the occurrences of out-of-synch conditions. The report also provides current and historical information on each component in your package. This information can be used to resolve out-of-synch conditions easily. Audit jobs also end with a return code. This return code indicates of what type of out-of-synch condition was found in your package. A return code of 4 means that some out-of-synch conditions were found, but they are usually only informational. Return codes of 8, 12, or 20 usually means the user must correct the out-of-synch conditions before the package can be frozen. See The Audit Job for more detailed information on the Audit return code. The higher the return code, the more severe out-of-synch conditions that were found. Audit rules 1 5 indicate which Audit return code is acceptable in order to pass Audit. Example, if the Audit rule is set to 4, then the Audit return code must be 4 or less to pass the Audit process. If the return code was 8, then the out-of-synch conditions, which caused the return code of 8, must be corrected in order to pass Audit. Note: If your package does not pass Audit, then it can not be frozen. Audit may be run at anytime during the package life cycle. Small Change Packages probably only need 1 or 2 audits, while larger Change Packages may run audits daily. The audit job is typically run after all the components have been checked out and ALL modifications have been completed. If any of the components are SRC or CPY type components, then their related compiles and links should also be done. If you modify a component in your package, then the last Audit return code is no longer valid, and you must run another Audit.
103
Audit
User Training Guide
The way Audit knows about all component relationships because it reads the Impact Analysis table. This Impact Analysis table is typically a DB2 table and it holds all component relationships. The types of relationships within the Impact Analysis table are; SRC CPY (source and copybook) LOD LOD (Main Load and External Loads) PRC / JCL DSN PRC / JCL PGM PRC / JCL PRC
Audit also queries and reports on nested levels of copybooks for a component within the Baseline. For example: You checkout and change copybook ABC10000 in your package CPY component DEF20000 copies in ABC10000 SRC component GHI30000 copies in DEF20000 Component ABC1000 will receive an out-of-synch condition SYNCH 4! You will need to recompile SRC component GHI30000 to get the latest version of copybook ABC10000 through copybook DEF20000
Types of Audits There are two types of Audits you can run, they are; A Full Audit A Full Audit will check for relationships for the components in your Change Package with respect to the baseline libraries in your application. When you run a Full Audit on a participating package in a complex/super package, Audit will notify you of out-of-synch conditions across the entire complex/super package. Depending on how many components you have in your package, the number of baseline libraries in your application, the number of relationships between these two, and if the package is associated with a complex/super package, a Full Audit may run for a significant amount of time. Therefore it might be best to run a Full Audit, on this type of package, near the end of the packages development life cycle. A Full Audit also updates the audit return code in your package. Staging Libraries Only (Audit Lite) Audit Lite ONLY checks for relationships within the packages own staging libraries. This type of Audit is very useful for a package that has many component relationships within its own staging libraries and the baseline libraries. Running a Full Audit on this type of package may take a considerable amount of run time. Therefore, before you run a Full Audit, run the Staging Libraries Only Audit to report on any out-of-synch conditions within your package
Audit 104
User Training Guide
staging libraries first. Once these conditions have been resolved, you can then run the Full Audit. Audit Lite does not report on out-of-synch conditions that reference baseline; namely DUPLIC!, SYNCH5!, SYNCH8!, and SYNCH10! When you run a Staging Library Only Audit on a participating package, in a complex/super package, Audit catches out-of-synch conditions only for that package, and not for any other participating packages in the complex/super package. Running an Audit Lite DOES NOT update the Audit return code in your package. This also means Audit Lite does not satisfy the Audit requirement for freezing a package.
AUDIT CHANGE PACKAGE - Panel

This panel enables you to specify what type of Audit job you want Change Man to submit on your Change Package. To access this Panel: Select option 1 from the Primary Option Menu for Build, then Select option 7 on the Build Options Menu for Audit.
CMNAUDIT -------------------- AUDIT CHANGE PACKAGE --------------------------COMMAND ===> PACKAGE ID AUDIT STAGING LIBRARIES ONLY AUTO RESOLVE OF OUT-OF-SYNCHS CROSS APPLICATION AUDIT (Simple package only) ===> ===> ===> ===> TEST000089 NO NO NO (Y/N) (Y/N) (Y/N)
JOB STATEMENT INFORMATION: ===> //WSER92L JOB (XXXX,333),WSER92,CLASS=E,MSGCLASS=3,____________________ ===> // TIME=2,REGION=4M,NOTIFY=WSER92________________________________ ===> //*JOBPARM SYSAFF=ESA1__________________________________________________ ===> //*_____________________________________________________________________ Press ENTER to process; Enter END command to exit.
To exit this panel you can: Enter the desired audit fields and press ENTER. Change Man will submit the audit job and usually return to the Build Options Menu. Press PF3 or enter END in the Command line and press ENTER. Change Man will return you to the previous panel.
Field
Description
105 Audit
User Training Guide
PACKAGE ID
Enter the Change Package ID, or double check the package ID displayed is still the package you want to run the Audit on. Enter YES if you want to check for out-of-synch conditions in just the Staging libraries (Audit Lite), or enter NO to run a Full Audit against the staging and baseline libraries. If the Audit Rule is set to anything other than 0, a full Audit is required before you can freeze the package. Enter YES if you want audit to automatically resolve certain out-of-synch conditions by submitting API jobs. Change Man automatically resolves the following out-of-synchs: SYNCH2!, SYNCH4!, SYNCH5!, SYNCH7!, SYNCH8!, SYNCH9!, and SYNCH15! Corrected out-of-synch conditions will be displayed in the audit report. It is recommended that you first submit the Audit job with this field set to NO. After reviewing the output you can then determine if you want Audit to correct these out-of-synch conditions and resubmit the Audit job with this field set to YES. Enter 'YES' to instruct Change Man to perform a cross application Audit for CPY/SRC relationships across "other" applications. This applies to SIMPLE packages only.
AUDIT STAGING LIBRARIES ONLY
AUTO RESOLVE OF OUT-OF-SYNCHS
CROSS APPLICATION AUDIT
Audit
106
User Training Guide
The Audit Job After Change Man has submitted the audit job, Change Man will notify you when the audit job ends by sending you a notification message as follows:
CMN2695I - PACKAGE USER000089 PASSED THE AUDIT WITH A RETURN CODE OF 00. CN(INT ERNAL) 14.36.26 JOB03782 $HASP165 WSER92L ENDED AT HOGNJE CN(INTERNAL) ***
This notification message informs you what return code your audit job ended with. This return code indicates what type of out-of-synch conditions were found in your package. The return codes are; 00 means there were no out-of-synch conditions found in your package and that everything is clean. No user action is required. 04 indicates that some out-of-synch conditions were found but they are very minor and are usually informational. Typically no user action is required. 08 indicates that some out-of-synch conditions were found and that they will need to be reviewed and possibly corrected. These out-of-synch conditions are SYNCH5! and SYNCH8!, relationships between package CPY and LOD components to the baseline libraries. Typically user action is required prior to freezing the package. 12 - indicates that some out-of-synch conditions were found and that they will need to be reviewed and typically MUST be corrected. These out-of-synch conditions are SYNCH2!, SYNCH4!, SYNCH6!, SYNCH7!, SYNCH9!, SYNCH10!, SYNCH11!, SYNCH12!, SYNCH13!, SYNCH14!, SYNCH15! and SYNCH16! User action required prior to freezing the package. 20 - indicates that many of the above out-of-synch conditions were found and that they need to be reviewed and typically MUST be corrected. User action required prior to freezing the package.
107
Audit
User Training Guide
The Audit Report The Audit job produces an Audit Report. This report can be viewed by your shops spool display system (SDSF, IOF, Flasher, etc.). The report name in the DDNAME list is called AUDITRPT. The Audit job processes each library type (CPY, DOC, JCL, LCT, LOD, SRC, etc.) in the Change Package sorted by library types. The Audit report then displays 2 sets of reports for each library type in your package. The first set contains each component in the Baseline and Staging libraries side-by-side with their corresponding PDF statistics. Any out-of-synch FLAGS are displayed in the center of these side-by-side reports. The second report displays the historical information for the staged like source components for the same library type. After the final 2 sets of reports, for the last library type, you will find a Legend and Summary Report. It contains a list of all the out-of-synch conditions and shows how many occurrences of these conditions were found in your package. Following this is a section that describes each outof-synch condition and provides the recommended or suggested resolution for each out-of-sync condition found.
Audit Report - Example of the 2 sets of Reports by Library Type

columns 1 - 80
(4.1.6 - 1997/273) Audit WEDNESDAY DECEMBER 30, 1998 (1998/ ************************************************************* *Simple Change Package ===> TEST000013 Created 1998/11/19 *Package Installation Date ===> 1999/01/01 Package St *Component Analysis Type ===> Description of member from di ******************************************************************************* *--------------------- B a s e l i n e ---------------------* *------************************************************************* ******** Name VV.MM Created Changed Size Init Tso-id Name +________ _____ __________ ________________ ____ ____ ________ ________ CMNCCASM 01.00 1996/01/26 1996/10/28 14:35 0135 0135 USER01 CMNCCASM CMNOFM 01.00 1996/01/26 1996/10/28 14:35 0008 0008 USER02 SYNCH12! CMNOFM CMNZDRV 01.00 1996/01/26 1997/07/30 10:33 0014 0013 USER33 CMNZFRV CMNZFRM Change Man
columns 55 -134
Y DECEMBER 30, 1998 (1998/364) 11:47:18 Page 1 ************************************************************* T000013 Created 1998/11/19 at 11:49:41 by WSER73 * 9/01/01 Package Status: DEV * cription of member from directory entry in library - (SRC) * ******************************************************************************* -------* *---------------------- S t a g i n g ----------------------* ******** ************************************************************* tso-id Name VV.MM Created Changed Size Init Tso-id
Audit
108
User Training Guide
________ ________ USER01 CMNCCASM USER02 SYNCH12! CMNOFM USER33 CMNZDRV CMNZFRM
_____ 01.01 01.05 02.08 02.13
__________ 1996/01/26 1996/01/26 1996/01/26 1996/01/26
________________ 1998/11/24 12:27 1998/11/24 12:24 1998/11/24 12:23 1998/11/24 12:19
____ 0344 0010 1255 1161
____ 0343 0010 1241 1148
_______ WSER73 WSER73 WSER73 WSER73
If a component is listed only on the Baseline side, the component has not been included in the change package. If a component is listed only on the Staging side, the component is new (has never been processed by Change Man). Any out-of-synch Flags will be listed in the center of these reports (see SYNCH12!). Many of the report statistics are the ISPF/PDF statistics in the PDS directory. They are very similar to ISPF browse or edit headings Audit Report - Legend and Summary Report
Legend and Summary Report 0 0 3 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0
The local level of audit chosen at this point; 0 - Audit is recommended but entirely optional -Out-of-synch messages (hint - search for "!" marks) DUPLIC! (Staging duplicates baseline) ===> SYNCH0! (Unknown to Change Man) ===> SYNCH1! (ISPF statistics not available) ===> SYNCH2! (Compile/designated proc differ) ===> SYNCH3! (Unparsable load module) ===> SYNCH4! (CPY problem in staging) ===> SYNCH5! (CPY high-date problem in baseline)===> SYNCH6! (Activity file not checked out) ===> SYNCH7! (Called subroutine in staging) ===> SYNCH8! (Called subroutine in baseline) ===> SYNCH9! (Source and load discrepancy) ===> SYNCH10! (Version regression problem) ===> SYNCH11! (Component hash discrepancy) ===> SYNCH12! (Orphan module in staging) ===> SYNCH13! (Baseline/staging discrepancy) ===> SYNCH14! (Components not in active status) ===> SYNCH15! (Source to relationship problem) ===> SYNCH16! (CPY low-date problem in baseline)===> SYNCH17! (CPY deleted problem in staging) ===> SYNCH18! (LOD deleted problem in staging) ===>
Highest return code encountered ===> 12 CMN2695I - PACKAGE TEST000013 PASSED THE AUDIT WITH A RETURN CODE OF 12.
Recommendation Summary Report 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 SYNCH12! (Orphan module in staging) Manually delete component from staging. CMN7540I - End of job; RC = 12 ******************************** BOTTOM OF DATA *****************************
109
Audit
User Training Guide
Audit
110
User Training Guide
Out-of-synch Conditions
The following is a list of out-of-synch conditions that the AUDIT job reports on. The return code listed, indicated how severe each out-of-synch condition is. It is also used to generate the return code of the Audit job. DUPLIC! Staging duplicates baseline Return Code - 4 There is no difference between the staging and baseline versions of this component. Suggested Resolution: Delete the duplicate component from the Change Package. !COPY Embedded copybooks Return Code - 0 Shows that there is a copybook within a copybook (an embedded copybook). This is an informational out-of-synch, which just shows that a relationship exists. Suggested Resolution: No action required. SYNCH0! Unknown to Change Man Return Code - 0 Change Man could not find the history (statistics) for the component. It has never been updated by Change Man. This includes components, unknown to Change Man, that are copied by another component. Suggested Resolution: No action required. SYNCH1! PDF statistics not available Return Code - 0 Change Man could not find the PDF statistics for the component. Suggested Resolution: No action required. SYNCH2! Compile/Designated Proc differ Return Code - 12 A source or like-source component was compiled without using the designated compiling procedure. Suggested Resolution: Recompile the component using the Designated Procedure. SYNCH3! Unparsable load module Return Code - 0 This synch will appear on a load module that Change Man cannot parse. If the IDRDATA records are unparsable, A SYNCH3 will occur. Suggested Resolution: No action required. SYNCH4! CPY problem in staging Return Code - 12 A staging version of a copy or like-copy component has a more recent activation date than the staging version of the source or like-source component calling it. Suggested Resolution: Recompile the staging version of the source.
111
Audit
User Training Guide
SYNCH5!
CPY problem in baseline Return Code - 8 A staging version of a copy or like-copy component has a more recent activation date than the baseline version of the source or like-source component calling it. Suggested Resolution: Recompile the baseline version of the source.
SYNCH6!
Activity file not checked out The activity file does not exist.
Return Code - 12
Suggested Resolution: Checkout the component again or stage in a new activity file if this is a new component. SYNCH7! Called subroutine in staging Return Code - 12 A staging version of the subroutine was linked after the staging version of the calling load module(s). Suggested Resolution: Relink the staging version of the calling load. SYNCH8! Called subroutine in baseline Return Code - 8 A staging version of a subroutine has a more recent activation date than the baseline version of the calling load. Suggested Resolution: Relink the baseline version of the calling load. SYNCH9! Source and load discrepancy Return Code - 12 Component does not have a matching source and load. Suggested Resolution: Stage the source component again. SYNCH10! Version regression problem Return Code - 12 The baseline version of this component has a more recent activation date than the staging version. Suggested Resolution: Checkout component again, and retrofit changes. SYNCH11! Hashing discrepancy Return Code - 12 The hashing calculation during the Audit of the component differs from the calculation created during staging. Suggested Resolution: Verify the changes to the component and stage again. SYNCH12! Orphan component Return Code - 12 This synch appears when an unknown component is found in the staging library. It occurs when a component has been copied into the staging library outside of Change Man, or when a compile fails. Suggested Resolution: Delete the component from the staging library.
Audit
112
User Training Guide
SYNCH13!
Baseline/Staging discrepancy Return Code - 12 This synch appears for staged components that have a baseline version that has been changed or updated since it was staged into a change package. Suggested Resolution: Checkout the component from baseline and retrofit the changes, or restage the component.
SYNCH14!
Components not in ACTIVE status Return Code - 12 If any component is not in ACTIVE status when the audit is run, a SYNCH14 will occur. Suggested Resolution: Stage the component or delete it from the package.
SYNCH15!
Source to relationship problem Return Code - 12 A baseline, or other otherwise accessible LCT, copy of like-copy module has a later date/time than the (fingerprinted) version of that same LCT, copy or likecopy module which was used/accessed during the activation/compile of the flagged staged like-source component. Suggested Resolution: Recompile the staging version of the source.
SYNCH 16!
CPY low-date problem in baseline Return Code - 8 The baseline version of the recompiled or relinked component has a more recent change package. Suggested Resolution: Recompile or relink the module from the Baseline library.
113
Audit
User Training Guide
Commonly Asked Questions Question. If you checkout a SRC component and make NO change to the component, but you Stage the component (meaning you run a compile/link) and its status changes to ACTIVE, will Audit flag this component? YES! Audit will flag the SRC component as a DUPLIC!
Answer.
Question.
If you do a RC (Recompile) on a SRC component from the baseline library and there are no changes associated with this SRC component, will the audit job raise any flag? NO! The new load module will have a different date and time stamp, even the SETSSI date will be different.
Answer.
Question.
Do you need to run an audit on a Change Package that only contains Scratch and Rename requests? YES! Audit still needs to be run.
Answer.
Question.
If I run a Full Audit on my participating package, does Audit review the other participating packages associated in the complex/super package? Yes, a Full Audit will check for any out-of-synch conditions across all the other participating packages within the complex/super package. A Audit Lite will not review the other participating packages and only check its own package staging libraries.
Answer.
Question. Answer.
Can I run an audit on a complex/super package? No. Change Man will issue an error message Invalid Package Level Package level must be simple or participating.
Audit
114
User Training Guide
Exercises for Audit
Exercise #1:
Run a Staging Libraries Only Audit on any Change Package. Review the Audit Report and determine if there are any out-of-synch conditions.
Exercise #2:
Run a Full Audit on any Change Package. Review the Audit Report and determine if there are any out-of-synch conditions.
Exercise #3:
Run a Full Audit on a Change Package that does not have ALL the components in ACTIVE status. Review the Audit Report and resolve the out-of-synch conditions.
Exercise #4:
Checkout a copybook used by some SRC program in the baseline library, then go into Stage and modify the copybook, then run Audit. Review the Audit Report. The report should show a SYNCH5!
115
Audit
User Training Guide
Audit
116
User Training Guide
Freeze
Freeze Overview
Once a Change Package has been built, tested, and audited, you freeze it. This process puts the package in frozen FRZ status, locks out further modification, and makes it available for approval. After the freeze process, the Change Package can still be "unlocked" and moved back to development DEV status with the use of the Revert function. You can also use the Unfreeze function to unlock specific package categories so they can be modified. During the freeze process, Change Man checks for two things: That all components in the package are in ACTIVE status. This indicates that the STAGE function completed successfully for all components That the package has passed the AUDIT process (optional)
If either of these checks fail, Change Man will not allow the Change Package to be frozen.
FREEZE OPTIONS Panel

Use this panel to select the freeze option you want to execute. These options are; Freeze the package online. Freeze the package by submitting a batch job. Selectively unfreeze or Refreeze specific package categories and components. Reset the Freeze in Progress indicator.
To access this Panel: Select option 2 from the Primary Option Menu for Freeze and press ENTER.
117
Freeze
User Training Guide
CMNFRZ01------------------------ FREEZE OPTIONS -----------------------------OPTION ===> _ PACKAGE ID ===> TEST000074 1 2 3 4 Online Batch Selective Reset Freeze package online Freeze package in batch Selectively unfreeze/refreeze package components Reset indicator after unsuccessful batch freeze (Y/N) (O-Online, B-Batch)
Automatic promotion after freeze ===> NO Online or batch promotion ===> O
To exit this panel you can: Enter the freeze option you want to execute and press ENTER. Press PF3 or enter END in the Option line and press ENTER. Change Man will return you to the previous panel.
Field OPTION
Description Enter the freeze options you want to execute and press ENTER. 1 - Freeze Package Online. 2 - Freeze Package in Batch. 3 - Selective. This option allows you to unfreeze/refreeze selective components that require modification without reverting the Change Package back to development. 4 - Reset. When the Freeze job is submitted it sets a flag that indicates the Change Package is frozen. If something happens during the freeze job (e.g. the freeze job is canceled), select this option to reset this flag. Enter the Change Package ID or double check the package ID displayed is still the package you want to work with. Enter YES if you would like Change Man to immediately promote your Change Package upon a successful completion of the freeze process. The Global and Application Administrators enable this function. The default is NO.
PACKAGE ID
AUTOMATIC PROMOTION AFTER FREEZE
Field
Freeze
Description
118
User Training Guide
ONLINE OR BATCH PROMOTION
If the AUTOMATIC PROMOTION AFTER FREEZE field is set to 'YES', this option indicates whether to perform the promotion online, or in batch. Enter O for online or B to submit a batch job.
The Freeze Wait Panel When you select freeze option 1 (Freeze Package Online), Change Man will present the following screen to inform you the progress of the freeze process.
Your screen is locked - please wait Date: 1998/12/22 Time: 13:40
========================================================================== | The Freeze function is performing the following task: | | Constructing the package execution JCL. | | Freezing all the package components. | | Notifying package approvers | ==========================================================================
While this wait panel is displayed, Change Man is doing the following: Checks to make sure ALL the components in your Change Package are in ACTIVE status. If yes, then it changes the status of ALL package components to FROZEN status. Changes the Change Package status from DEV to FRZ. Creates the .X package staging library that contains the installation and backout batch jobs. Notifies the package approvers of the change in status by sending them a message, typically an MVSSEND message.
119
Freeze
User Training Guide
UNFREEZE / REFREEZE Package Panel

Use this panel to selectively unfreeze or refreeze specific Change Package categories. You can only unfreeze Package categories that are in FROZEN status. After the package category has been unfrozen, the Package Status will still remain frozen FRZ, but the individual components in that category are marked unfrozen. Meaning you can now made modifications to these components. Once the modifications are completed, then you can use the refreeze function to refreeze the package category. To access this Panel: Select option 2 from the Primary Option Menu for Freeze, then select option 3 from the Freeze Options panel and press ENTER.
CMNUNFRZ------------------ UNFREEZE/REFREEZE TEST000074 ----- 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 _ Onsite FROZEN _ Custom Forms FROZEN ****************************** Bottom of data ********************************
To exit this panel you can: Enter the unfreeze/refreeze option you want to execute beside the package category and press ENTER. Press PF3 or enter END or CANCEL in the Command line and press ENTER. Change Man will return you to the previous panel.
Field LCMD (first column)
Description F - Freeze all components within this package category. U - Unfreeze all components within this package category, so that you can use the Stage process to make the appropriate component changes. S - Where applicable, a selection list will be presented and you can selectively unfreeze or refreeze specific components from the list. Enter F to refreeze the component, enter U to unfreeze the component.
Field
Freeze
Description
120
User Training Guide
PACKAGE CATEGORY STATUS FUNCTION
The package category for which an action is to be performed. The package category's current status as of the last REFRESH. The function last selected (*Freeze, *Unfreeze, or *Selective).
Exercises for Freeze Exercise #1: Freeze a Change Package using the online process. Once complete, go back and view the status of each component in your package. Also notice the package status. Review the package staging libraries, specifically the .X file.
121
Freeze
User Training Guide
Freeze
122
User Training Guide
Promote
Promote/Demote Overview
Promotion is the process of moving changes through specific environments for various test requirements, such as Unit, System, and Acceptance testing. Demotion is the process of deleting components from these environments, usually because errors have been found during testing. The testing environments are application specific libraries and/or common libraries shared by multiple applications. The Change Man Administrators define the library types that may be promoted, and the actual library names. Change Man Administrators determine the promotion/demotion mode (online or batch), and the promotion/demotion rule which defines the steps that must be taken within the Change Package Life Cycle. Change Man also checks the test environment for components that match the components being promoted. If there are matches then Change Man will inform you of the potential overlay. When a component is promoted to a new level, the previous level's libraries are cleaned up. Promotion of DB2 or CICS components must be in batch for BINDS and NEWCOPY.
PROMOTE CHANGE PACKAGE Panel

Use this panel to display and select the options available within promotion/demotion, and review the status and historical information for a specific Change Package. To access this Panel: Select option 3 from the Primary Option Menu for Promote and press ENTER.
You will first be presented with the following panel, which you use to change or confirm the package ID shown is the package you want to promote or demote.
CMNPRM00 ------------------- PROMOTE CHANGE PACKAGE -------------------------COMMAND ===> PACKAGE ID ===> TEST000074 Press ENTER to process; Enter END command to exit.
123
Promote
User Training Guide
CMNPRM01 ------------------- PROMOTE CHANGE PACKAGE --------- ROW 1 TO 2 OF 2 COMMAND ===> SCROLL ===> PAGE PACKAGE ID: TEST000074 CREATOR: WSER92 STATUS: DEV INSTALL DATE: 19981230
CURRENT PROMOTION LEVEL: STAGING - 0 MAXIMUM PROMOTION LEVEL: PROMO2 - 2 ACTION REQUESTED ONLINE OR BATCH LEVEL TO CHECK ===> _ ===> O ===> 1 (P-Promote, D-Demote, C-Check for overlay) (O-Online, B-Batch) (Required for Action C)
PROMOTE/DEMOTE HISTORY LVL NICKNAME DATE TIME ID Full Demotion 1 PROMO1 1998/12/23 13:39 WSER92 Full Promotion 1 PROMO1 1998/12/04 10:47 WSER92 ******************************* Bottom of data *******************************
To exit this panel you can: Enter the requested action and press ENTER. Press PF3 or enter END in the Command line and press ENTER. Change Man will return you to the previous panel.
Field CURRENT PROMOTION LEVEL
Description Informs you where the package was fully promoted last.
MAXIMUM PROMOTION LEVEL Informs you what the last promotion available promotion level is. ACTION REQUESTED Enter the required action you want to perform. P - Promote package will copy the package component to a promotion level. D - Demote package will delete the package component from a promotion level. C - Checks a promotion level to determine if any of the change package modules being promoted already exist in the promotion level you want to promote to. Enter O if you wish to promote in online mode. Enter B if you want the promotion to execute as a batch job. If Change Man needs to perform a BIND for DB2 components or a NEWCOPY for CICS components, you must submit the promotion as a batch job.
ONLINE OR BATCH
Field
Description
Promote
124
User Training Guide
LEVEL TO CHECK
This field is required if the ACTION REQUESTED was specified as C. It dictates the level for which Change Man is to check components This field displays information regarding promotion Historical Information history. It displays the action taken, promotion level, nickname, the date and time that the action took place, and the TSOID of the user who issued the promote/demote request.
PROMOTION/DEMOTION
PROMOTE OPTIONS -Panel Use this panel to promote the entire change package, or to selectively promote members that have previously been selectively demoted. To access this Panel: This panel appears automatically after you enter P on the Promote Change Package panel.
CMNPRM02 --------------------- PROMOTE OPTIONS ------------------------------OPTION ===> F - Full promotion of the entire package to another promotion level S - Selective promotion of components to another promotion level PACKAGE ID: TEST000074 CURRENT PROMOTION LEVEL: MAXIMUM PROMOTION LEVEL: CREATOR: WSER92 STAGING - 0 PROMO2 - 2 STATUS: FRZ INSTALL DATE: 19981230
NEXT PROMOTION LEVEL ===> 1 JOB STATEMENT INFORMATION: ===> //WSER92N JOB (XXXX,374),WSER92,CLASS=E,MSGCLASS=3,____________________ ===> // TIME=2,REGION=4M,NOTIFY=WSER92________________________________ ===> //*JOBPARM SYSAFF=ESA1__________________________________________________ ===> //*_____________________________________________________________________ Press ENTER to process; Enter END command to exit.
To exit this panel you can: Enter the requested action and press ENTER. Press PF3 or enter END in the Option line and press ENTER. Change Man will return you to the previous panel.
125
Promote
User Training Guide
Field OPTION
Description F - Full Promotion. Will promote all the active components of the Change Package to the level indicated in the NEXT PROMOTION LEVEL field. S - Selective Promotion. If selective promotion is chosen, Change Man will display a package component list. From this list, select the active components to be promoted. This field allows you to specify to which promotion level you want to promote the change package to. If promotion is to take place in batch, this field is required. Enter the Job card to be used for the promotion batch job. You will only see the jobcard display if you select option B on the previous panel.
NEXT PROMOTION LEVEL
JOB STATEMENT INFORMATION
DEMOTE OPTIONS Panel

Use this panel to demote components of a change package that have been promoted but need modification. To access this Panel: This panel appears automatically after you enter D on the Promote Change Package panel.
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: TEST000074 CREATOR: WSER92 STATUS: FRZ INSTALL DATE: 19981230
CURRENT PROMOTION LEVEL: PROMO1 - 1 MAXIMUM PROMOTION LEVEL: PROMO2 - 2 DEMOTE FROM LEVEL ===> 1
JOB STATEMENT INFORMATION: ===> //WSER92Q JOB (X170,374),WSER92,CLASS=E,MSGCLASS=3,____________________ ===> // TIME=2,REGION=4M,NOTIFY=WSER92________________________________ ===> //*JOBPARM SYSAFF=ESA1__________________________________________________ ===> //*_____________________________________________________________________ Press ENTER to process; Enter END command to exit.
Promote
126
User Training Guide
To exit this panel you can: Enter the requested action and press ENTER. Press PF3 or enter END in the Option line and press ENTER. Change Man will return you to the previous panel.
Field OPTION
Description F - Full Demotion. This indicates that all components of the Change Package are to be demoted from the level indicated in the DEMOTE FROM LEVEL field. S - Selective Demotion. If selective demotion is chosen, Change Man will display a package component list. From this list, select the components to be demoted. This field allows you to specify to which promotion level you want to promote the change package to. If promotion is to take place in batch, this field is required. Enter the Job card to be used for the promotion batch job. You will only see the jobcard display if you select option B on the previous panel.
DEMOTE FROM LEVEL
JOB STATEMENT INFORMATION
COMMON COMPONENTS Panel This panel appears when the components in the Change Package being promoted already exit in the promotion level from some other Change Package. If you press ENTER, then you will overlay these common components with the ones in your package. Note: Always check with the owner of the other package if its ok to overlay their component. To cancel the promotion press PF3 or enter END or CANCEL in the Command line and press ENTER.
CMNPRM08 --------------------- COMMON COMPONENTS ------------ OVERLAY WARNING COMMAND ===> SCROLL ===> PAGE Press ENTER to process or enter END to exit. PACKAGE ID: TEST000093 CREATOR: WSER92 STATUS: DEV INSTALL DATE: 19981230
CURRENT PROMOTION LEVEL: STAGING - 0 MAXIMUM PROMOTION LEVEL: PROMO2 - 2 NAME TYPE PACKAGE ID STA PROMOTION DATE TIME STATUS ABCJCL JCL USER000074 FRZ 1 PROMO1 1998/12/29 13:47 *COMMON ******************************* Bottom of data *******************************
127
Promote
User Training Guide
Exercises for Promote/Demote
Exercise #1:
Create a Change Package with a SRC program, make a change to the source program and complete the compile and link process. Then do a Full Promote to the first available promotion level. Do the promote in online mode.
Exercise #2:
Use the same package as in exercise #1 to demote the same source program from the first promotion level. Use the Selective demotion.
Exercise #3:
Create a Change Package with 2 SRC programs, make a change to both source programs and complete the compile and link process. Then do a Full Promote to the first available promotion level. Then do another Full Promote to the next promotion level. Now Demote 1 of the programs, make another change to the program (in Stage) and finally do a Selective promote of the program back to the first promotion level.
Promote
128
User Training Guide
Approve
Approve Overview
The Approval function is a very important process in the Change Package Life Cycle. Approval is where your package is checked or reviewed for the last time prior to bring installed into production. There may be several approvers required to review and approve your package. Once the final approver approves your package, the install process will start. Also the Package status changes from FRZ to APR (approved). Once a Package is frozen, designated approvers may be notified via TSO (or another notification vehicle) that a Change Package is awaiting approval. This section details what must be done in order to approve or reject a Change Package.
APPROVE PACKAGE PARAMETERS - Panel

This panel is used as selection criteria to display the specific Change Package(s) that you would like to approve or reject. To access this Panel: Select option 4 from the Primary Option Menu for Approve and press ENTER.
CMNAPPRV ----------------- APPROVE PACKAGE PARAMETERS -----------------------COMMAND ===> SPECIFY SELECTION CRITERIA: PACKAGE ID ===> TEST000074 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)
129
Approve
User Training Guide
Enter the required fields and press ENTER, or enter blanks and work with the selection lists. Press PF3 or enter END in the Command line and press ENTER. Change Man will return you to the previous panel. Description The ID of the Change Package to be approved or rejected. Leave this field blank to view a list of all Change Packages awaiting your approval. Enter a security entity name to display Change Packages that are awaiting approval from the entity. Enter a USERID to display Change Packages that have notified the user that approval is required. Enter Work Request ID to display Packages with that ID. Enter a Department to display Change Packages assigned to that department. Enter a remote site to display Change Packages hat affect that remote site. Enter a Package Level to display Change Packages with that Package Level. Enter a Package Type to display Change Packages with that Package Type. Enter a Package Time Span to display Change Packages with that Package Time Span. Enter a TO and FROM date range to display Change Packages scheduled to install between these two dates inclusively. Enter a TO and FROM date range to display Change Packages that were created between these two dates inclusively. Enter a YES if you wish to limit the display further by specifying component types.
Field PACKAGE ID
APPROVAL ENTITY NAME
NOTIFIED USER ID
WORK REQUEST ID
DEPARTMENT
REMOTE SITE AFFECTED
PACKAGE LEVEL
PACKAGE TYPE
PACKAGE TIME SPAN
FROM/TO INSTALL DATE
FROM/TO CREATION DATE
OTHER PARAMETERS
Approve
130
User Training Guide
The results of the Approve Package Parameters might generate more than 1 Change Package. The following panel is an example of this;
CMNAPPL1 -------------------- APPROVE PACKAGE LIST ---------- ROW 1 TO 3 OF 3 COMMAND ===> SCROLL ===> PAGE PACKAGE ID STA INSTALL LVL TYPE DEPT PROMOTION AUD CREATOR _ TEST000067 FRZ 19981230 SMPL PLN/PRM DDDD WSER92 _ TEST000074 FRZ 19981230 SMPL PLN/PRM DDDD 01 PROMO1 WSER92 _ TEST000093 FRZ 19981230 SMPL PLN/PRM DDDD WSER92 ****************************** Bottom of data ********************************
To select the Change Package you want to work with enter S beside the package ID.
APPROVE/REJECT OPTIONS - Panel

You use this panel to direct Change Man as to which approval process you want to perform. To access this Panel: This panel will appear automatically after the Approval Package Parameters or the Approve Package List Panels.
CMNAPPOP ------------------- APPROVE/REJECT OPTIONS ------------------------OPTION ===> _ PACKAGE ID: TEST000074 1 2 3 4 Approve Reasons Query Reset STATUS: FRZ INSTALL DATE: 19981230
Approve or reject a change package Display reasons a package was rejected Query change package Reset approval in progress indicator
To exit this panel you can: Enter the requested action in the Option line and press ENTER. Press PF3 or enter END in the Option line and press ENTER. Change Man will return you to the previous panel.
131
Approve
User Training Guide
Field OPTION
Description 1 - APPROVE. This option displays the Approval List panel that allows you to approve or reject the Change Package. 2 - REASONS. If the Change Package has been rejected by any approver, use this option to display the reasons that it was rejected. 3 - QUERY. This option allows you to review the contents of the Change Package. 4 - RESET. This option allows you to reset the progress indicator.
PACKAGE INFORMATION CATEGORIES - Panel

The approvers can use this panel to gather Change Package information prior to approval. Change Man will display a list of package categories. The approvers can view any of these categories to get all the information they need to determine if they should approve or reject the Package. To access this Panel: Enter option 3 from the Approve/Reject Options panel and press ENTER.
CMNQRY03 --------------- PACKAGE INFORMATION CATEGORIES --COMMAND ===> PACKAGE ID: TEST000074 CREATOR: WSER92 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ General 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 STATUS: FRZ AUDIT RC:
INSTALL DATE: 19981230
Approve
132
User Training Guide
To exit this panel you can: Enter the requested action and press ENTER. Press PF3 or enter END or CANCEL in the Command line and press ENTER. Change Man will return you to the previous panel.
Field LCMD (first column)
Description S Enter S beside package category you want to view.
APPROVAL LIST Panel

Use this panel to indicate your approval or rejection of a Change Package. You can also use this panel to make notes to yourself or others about the Change Package, or to indicate that you're in the process of reviewing the Change Package, but have not yet reached an approve/reject decision. To access this Panel: Select option 1 from the Approve/Reject Options panel and press ENTER.
CMNAPPLS ----------------------- APPROVAL LIST -------------- ROW 1 TO 2 OF 2 COMMAND ===> SCROLL ===> PAGE Press ENTER to process; enter END command to exit. PACKAGE ID: TEST000074 APPROVER DESCRIPTION _ Approver #1 - Project Leader 001 _ Approver #2 - Project Assistant 002 ******************************* Bottom of data ******************************* STATUS: FRZ INSTALL DATE: 19981230 ID DATE TIME SEQ STATUS
To exit this panel you can: Enter the requested action and press ENTER. Press PF3 or enter END or CANCEL in the Command line and press ENTER. Change Man will return you to the previous panel.
Field
Description
133 Approve
User Training Guide
LCMD (first column)
A - APPROVE. Will approve the Change Package. R - REJECT. Will reject the Change Package. V VIEWING. Indicates to the person who submitted the package for approval that you are still viewing it. C - Displays a panel on which you can write notes about the package.
APPROVER DESCRIPTION A short description of each level of approval. ID DATE/TIME SEQ STATUS The specific TSO userid of the approver. The date and time the approval or rejection was given. The order in which approvals are to be made. Shows the status of the approval request for each approver. (e.g. approved, reject)
Once the last approver approves the Package the Package is ready for the installation process. If the Scheduler selected was Manual then the Package will be installed right after the last approver has approved the package. If the scheduler was CMN then the package will be installed at the specified date and time. Once the final step of the install has occurred Change Man will notify you by sending the following message:
CMN405I - USER000095 BASELINE RIPPLED 1999/01/06 @ 10:20:36. CN(INTERNAL) ***
Once you see this message the Package has been installed into production and the Baseline Ripple process has completed. The Package status has also changed from APR to BAS (Baselined).
REJECT REASONS - Panel

Use this panel to enter the reasons why you rejected the Change Package. To access this Panel: Select option 2 from the Approve/Reject Options panel and press ENTER.
Approve
134
User Training Guide
CMNREJR1--------------------COMMAND ===> PACKAGE ID: TEST000237 APPROVER: Operations Manager TSO-ID :
REJECT REASONS STATUS: FRZ
-------------------------SCROLL ===> PAGE INSTALL DATE: 19981125
===> The change is past deadline ===> ===> ===> ===> ===> ===> ===> ===> Press ENTER to process; Enter END command to exit.
To exit this panel you can: Enter the free form text and press ENTER. Press PF3 or enter END in the Command line and press ENTER. Change Man will return you to the previous panel.
Field Free form text area
Description Enter the reason why the Package is being rejected.
135
Approve
User Training Guide
Exercises for Approval
Exercise #1:
Use the defined Approval Process to approve a Change Package awaiting your approval. Notice the change in package status.
Exercise #2:
Use the defined Approval Process to reject a Change Package that is awaiting your approval. You must enter a reject reason. Notice the change in package status.
Approve
136
User Training Guide
List
List Overview
Change Man uses menu driven panels to allow the user to navigate throughout the Change Man system or to select the functions they want to perform. The List function provides an alternative way of navigating throughout the Change Man system or selecting functions to be processed. A major benefit of the List function is that it provides all the Change Man functions to be accessed from one central location. Once most users become familiar with the Change Man functions and processes, they usually switch from the menu driven navigation method to the List function method. In the List function you can list all the Change Packages in the system, or you can specify "search" criteria that allows you to list only those Change Packages that meet the search criteria. From these resultant package lists, you can perform almost any Change Man function you want, like: Updating package information Audit Freeze Approval Revert Checkout Stage Promote / Demote etc.
137
List
User Training Guide
PACKAGE LIST PARAMETERS - Panel

Use this panel to enter the selection criteria to search the Package Master to provide a resultant list of Change Package(s) you want to work with. The most typical way to use this panel is to only enter the full Package ID in the Package ID field and press enter. You can also use wide cards in most of the input fields. Example, if you wanted to get a list of ALL the packages in an application, then enter the 4 character application ID in the package ID field and press enter. You will be presented with a list of every package in that application. You can enter several search criteria in any of the other fields to further narrow down the resultant package list. To access this Panel: Select option 5 from the Primary Option Menu for List and press ENTER.
CMNLIST0 ----------------- PACKAGE LIST PARAMETERS --------------------------COMMAND ===> SPECIFY SELECTION CRITERIA: PACKAGE ID ===> TEST000074 PACKAGE STATUS CREATOR'S 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 ===> ===> ===> ===> ===> ===> ===> ===> ===> ===> ===> ===> (Full name or pattern; blank for list, or '*' for all packages) (DEV, FRZ, APR, REJ, DIS, INS, BAS, BAK, OPN, CLO, TCC or DEL)
To exit this panel you can: Enter the search criteria and press ENTER. Press PF3 or enter END or CANCEL in the Command line and press ENTER. Change Man will return you to the previous panel.
List
138
User Training Guide
Field PACKAGE ID
Description Enter the Package ID or pattern, or leave this field blank to choose from the list of all applications. Use this field to mask the list of Change Packages according to the entered package status. Enter the TSO ID for the Change Packages to be
PACKAGE STATUS
CREATOR'S TSO ID viewed. WORK REQUEST ID
Enter the Work Request ID for the Change Packages to be viewed. Enter the department for the Change Packages to be viewed. Enter the level (simple, complex, super, or participating) of the Change Packages to be viewed. Enter the type (planned or unplanned) of the Change Packages to be viewed. Enter the time span (permanent or temporary) of the Change Packages to be viewed. To view a list of Change Packages that are to be during a range of dates, enter the inclusive dates in the form of YYYYMMDD.
DEPARTMENT
PACKAGE LEVEL
PACKAGE TYPE
PACKAGE TIME SPAN
FROM/TO INSTALL DATE installed
To view a list of Change Packages that were created between a range of dates, enter the inclusive dates in the form of YYYYMMDD. Enter Y to view the panel with additional selection criteria.
OTHER PARAMETERS
139
List
User Training Guide
CHANGE PACKAGE LIST - Panel

This panel displays the Change Packages that meet the selection criteria that were entered on the Package List Parameters panel. From the Change Package List panel you can request almost any Change Package process by issuing line commands beside the Package ID. For example, if you wanted to list all the components within a package, on this panel all you need to do is enter 'S2 beside the package ID you want and Change Man takes you directly to the Stage option 2 panel. Through the menu method you would select 1 for Build, then select 6 for Stage, and finally select 2 for Stage Package. This panel also provides informative details on each package being displayed. Information like Package Status (STA), the install date, the type of package, promotion info and who created the package. To access this Panel: Appears automatically after pressing enter from the Package List Parameters panel.
CMNLIST3 -------------------- CHANGE PACKAGE LIST --------- ROW 1 TO 21 OF 24 COMMAND ===> SCROLL ===> PAGE PACKAGE ID STA INSTALL LVL TYPE WORK REQUEST DEPT PROMOTE AUD CREATOR __ TEST000051 DEV 19990113 SMPL PLN/PRM STALEPACKAGE UTRN WSER200 __ TEST000052 INS 19980313 SMPL PLN/PRM INSTALLABEND UTRN 0 WSER200 __ TEST000053 APR 19980317 SMPL PLN/PRM SCHEDRECORD UTRN STAGING 0 WSER200 __ TEST000054 APR 19980313 SMPL PLN/PRM CONCURRENTDV UTRN PROMO1 WSER200 __ TEST000055 OPN 19980313 CMPX PLN/PRM DEMOCOMPLEX UTRN WSER200 __ TEST000056 DEV 19980313 PART PLN/PRM DEMOPARTPKG UTRN WSER200 __ TEST000057 DEV 19980313 PART PLN/PRM DEMOPARTPKG UTRN WSER200 __ TEST000058 DEV 19980313 SMPL UNP/TMP DEMOPARTPKG UTRN WSER200 __ TEST000063 DEV 19981230 SMPL PLN/PRM AAAAAAAAAAAA DDDD STAGING WSER92 __ TEST000066 DEV 19981230 SMPL PLN/PRM AAAAAAAAAAAA DDDD WSER92 __ TEST000067 DEV 19981230 SMPL PLN/PRM AAAAAAAAAAAA DDDD WSER92 __ TEST000068 DEV 19981230 SMPL PLN/PRM AAAAAAAAAAAA DDDD WSER92 __ TEST000069 DEV 19981230 SMPL PLN/PRM AAAAAAAAAAAA DDDD WSER92 __ TEST000071 OPN 19981201 CMPX PLN/PRM AAAAAAAAAAAA DDDD WSER92 __ TEST000072 OPN 19981201 CMPX PLN/PRM AAAAAAAAAAAA DDDD WSER92 __ TEST000073 DEV 19981230 SMPL PLN/PRM AAAAAAAAAAAA DDDD WSER92 __ TEST000074 FRZ 19981230 SMPL PLN/PRM AAAAAAAAAAAA DDDD STAGING WSER92 __ TEST000075 DEV 19981230 SMPL PLN/PRM AAAAAAAAAAAA DDDD WSER92 __ TEST000076 DEV 19981230 SMPL PLN/PRM AAAAAAAAAAAA DDDD WSER92 __ TEST000078 DEL 19981230 SMPL PLN/TMP AAAAAAAAAAAA DDDD WSER92 __ TEST000088 DEL 19981230 SMPL PLN/PRM AAAAAAAAAAAA DDDD WSER92
To exit this panel you can: Enter the package function beside the Package ID and press ENTER. Press PF3 or enter END or CANCEL in the Command line and press ENTER. Change Man will return you to the previous panel.
Field
List
Description
140
User Training Guide
Line Commands
There are 38 different line commands available for this panel. To display the line command list, place a single question mark ? or any invalid line command and press enter. You will be presented with the valid line commands you can use. See next section for the list. The Change Package ID assigned by Change Man. The current status of the Change Package. The scheduled date of Change Package installation. The Change Package level (simple, complex, super, or participating). The type and time span for the Change Package (planned or unplanned, permanent or temporary). The Work Request ID assigned to the Change Package. The department assigned to the Change Package. The current level of promotion (if any). The return code from the most recent Change Man Audit job for the Change Package. The TSO ID that created the Change Package.
PACKAGE ID STA INSTALL LEVEL
TYPE
WORK REQUEST DEPARTMENT PROMOTION AUD
CREATOR
Note: Of all the 38 possible Package Line commands, there is NO command to CREATE a new package. The reason for this is how can you enter the create package command on a package that already exists. However you still can perform the CREATE new package function by entering CR on the Command line of this panel. Once entered you will go directly to the Create New Package panel.
141
List
User Training Guide
PACKAGE LIST OPTIONS - Panel

This panel displays the available commands that you can enter within Change Package List panel.
CMNLIST5 -------------------- PACKAGE LIST OPTIONS ------ INVALID LINE COMMAND COMMAND ===> SCROLL ===> PAGE OPTION DESCRIPTION -----------------------------------------------------------------------------U1 Update control information U2 Update general information U3 Update implementation information U4 Update scheduling information U5 Update affected application information U6 Update participating package information U7 Update site(remote) information U8 Change complex/super package to CLO status U9 Change complex/super package to OPN status OF Work with Online forms UA Rename and Scratch components (Package driven) UB Rename and Scratch components (Baseline driven) C1 Check out components (Baseline/promotion) C2 Check out components (Package list) S1 Stage components (Dev Lib list) S2 Stage components (Package list) S3 Specify package driven selection parameters AP Audit package RC Recompile source code from baseline/promotion libraries RL Relink load modules.
CMNLIST5 -------------------- PACKAGE LIST OPTIONS ------- ROW 21 TO 38 OF 38 COMMAND ===> SCROLL ===> PAGE OPTION DESCRIPTION -----------------------------------------------------------------------------BB Browse/Print Baseline/Promotion libraries BL Browse compressed listing CC Compare staging changes against baseline/promotion libraries ZP Compress change package staging libraries F1 Freeze the change package online F2 Freeze the change package in batch F3 Selectively unfreeze or refreeze package components F4 Reset Freeze in Progress indicator PD Promote/demote a change package A1 Approve/Reject a change package A2 Display reject reasons A4 Reset Approval in Progress indicator D1 Memo delete a change package D2 Undelete a memo deleted change package RV Revert a change package back to DEVelopment status QP Query change package information B1 Back out a change package SC Scan baseline for character strings ******************************* Bottom of data *******************************
List
142
User Training Guide
Exercises for List
Exercise #1:
Using only the Package List feature, display a list of all the Change Packages in an application.
Exercise #2:
Using only the Package List feature, display a list of all the Change Packages in an application that are in DEV status and that were created by your Userid.
Exercise #3:
Using only the Package List feature, create a new package, checkout a SRC component, edit/stage the component and run audit on this new package.
Exercise #4:
Using only the Package List feature to display all the packages in DEV status and perform the freeze function on one of these packages.
143
List
User Training Guide
List
144
User Training Guide
Delete
Delete Overview
The Delete function is used to delete Change Packages that are no longer required. The Delete function has 2 steps in its process. The first step is to mark the Change Package for deletion, or flag the Package as Memo Deleted. This is a logical delete, which is accomplished by completing the Delete panel process (see below). The second step is the physical deletion of all the datasets associated with the Change Package, and the deletion of all the records within the Change Man Package Master file. The physical deletion only takes place when the REPORTS task is executed. The REPORTS task is a Housekeeping job that is usually scheduled to run once a day. Typically it runs in the middle of the night when Change Man is down. A Package to be deleted through this function must be in DEV status. The UNDELETE function is used to remove a change package from a MEMO DELETE status. This option can be used up until the time that the REPORTS job has run. Check with your Change Man administrator to determine when package aging occurs against the package master.
DELETE OPTIONS Panel

Use this panel to select which Delete function you want to perform, Delete or Undelete. To access this Panel: Select option D from the Primary Option Menu for Delete and press ENTER
CMNDELT0 ----------------------- DELETE OPTIONS -----------------------------OPTION ===> _ 1 2 Delete - Memo delete a change package Undelete - Restore memo deleted change packages
To exit this panel you can: Enter the required option 1 or 2 and press ENTER Press PF3 or enter END in the Option line and press ENTER. Change Man will return you to the previous panel
145
Delete
User Training Guide
Field OPTION
Description 1 - Delete. This option informs Change Man you want to Memo Delete a Change Package. 2 - Undelete. This option informs Change Man you want to Undelete a Memo Deleted Change Package(s).
MEMO DELETE CHANGE PACKAGE Panel

Use this panel to select which Change Package you want to Memo Delete. To access this Panel: Select option 1 from the Delete Options panel and press ENTER
CMNDELT1 ----------------- MEMO DELETE CHANGE PACKAGE -----------------------COMMAND ===> PACKAGE ID CONFIRM REQUEST ===> TEST000078 ===> YES (Y/N)
To exit this panel you can: Enter the required fields and press ENTER Press PF3 or enter END in the Command line and press ENTER. Change Man will return you to the previous panel
Field PACKAGE ID
Description Enter the Change Package ID or double check the package ID displayed is still the package you want to work with. Enter 'YES' if you want Change Man to display a confirmation of the delete request prior to setting up the Memo Delete. Enter 'NO' if you are certain that the change package is to be deleted.
CONFIRM REQUEST
Delete
146
User Training Guide
If you enter YES for the Confirm Request field, then Change Man will display the following panel:
CMNDELT2 ----------------------- CONFIRM DELETE -----------------------------COMMAND ===> PACKAGE ID: TEST000078 STATUS: DEV INSTALL DATE: 19981230 Press ENTER to confirm delete request. Enter END command to cancel delete request.
To exit this panel you can: Press ENTER to process the Memo Delete request Press PF3 or enter END in the Command line and press ENTER. Change Man will return you to the previous panel
If you press ENTER to process the Memo Delete request, then Change Man will display the following panel:
CMNDELT1 ----------------- MEMO DELETE CHANGE PACKAGE --- PACKAGE MEMO DELETED COMMAND ===> PACKAGE ID CONFIRM REQUEST ===> TEST000078 ===> YES (Y/N)
This panel informs you that the Memo Delete request has been processed, which means the Change Package has been marked for deletion. The Package status also changes from DEV to DEL.
147
Delete
User Training Guide
RESTORE MEMO DELETED PACKAGES Panel

Use this panel to select which Change Package(s) you want to Memo Undelete. To access this Panel: Select option 2 from the Delete Options panel and press ENTER
CMNDELT3 --------------- RESTORE MEMO DELETED PACKAGES ---------------------COMMAND ===> PACKAGE ID ===> TEST000078 (Blank for list)
To exit this panel you can: Press ENTER to process the Memo Undelete request Press PF3 or enter END in the Command line and press ENTER. Change Man will return you to the previous panel.
Field PACKAGE ID
Description Enter the Change Package ID or double check the package ID displayed is still the package you want to work with. Note: To select from a list of Memo Deleted Change Packages, enter a blank in this field. This will result in the following Package List panel:
CMNDELT4 ----------------- MEMO DELETED PACKAGE LIST -------- ROW 1 TO 3 OF 3 COMMAND ===> SCROLL ===> PAGE _ _ _ PACKAGE ID TEST000078 TEST000088 TEST000089 STATUS
******************************* Bottom of data *******************************
From this list you can enter U beside the Package(s) you want to Memo Undelete.
Delete
148
User Training Guide
If you press ENTER to process the Memo Undelete request, then Change Man will display the following panel:
CMNDELT3 --------------- RESTORE MEMO DELETED PACKAGES ----- PACKAGE UNDELETED COMMAND ===> PACKAGE ID ===> TEST000078 (Blank for list)
This panel informs you that the Memo Undelete request has been processed. The Change Package status is also changed from DEL back to DEV.
149
Delete
User Training Guide
Delete
150
User Training Guide
Revert
Revert Overview
After a Change Package has been Rejected, Backed out, or Frozen, it is no longer available for any changes or modifications. If the user needs to go back and make changes to this Package, then the package status must be changed to DEV. The Revert function is used to accomplish this change. It will change the Change Package status from BAK, FRZ, APR or REJ to DEV status. Once complete the entire Change Package is now available for any modifications. The user is required to enter a revert reason describing why the change package is being reverted. These revert reasons are available for review using the Change Man Query function.
REVERT CHANGE PACKAGE - Panel

Use this panel to select the Change Package you need to Revert. To access this Panel: Select option R from the Primary Option Menu for Revert and press ENTER
CMNREV00 ------------------- REVERT CHANGE PACKAGE -------------------------COMMAND ===> PACKAGE ID ===> TEST000074 Press ENTER to process; Enter END command to exit.
To exit this panel you can: Enter the required field and press ENTER Press PF3 or enter END in the Command line and press ENTER. Change Man will return you to the previous panel
Field PACKAGE ID
Description Enter the Change Package ID or double check the package ID displayed is still the package you want to work with.
151
Revert
User Training Guide
REVERT REASONS- Panel

Use this panel to enter the reasons why you reverted the Change Package. To access this Panel: Will automatically appears after the Revert Change Package panel
REVERT REASONS --------------------------------STATUS: REJ INSTALL DATE: 19990130
CMNREVRS ------------------COMMAND ===> PACKAGE ID: TEST000067
===> Need to add in some additional components. ===> ===> ===> ===> ===> ===> ===> ===> Press ENTER to process; enter END command to exit.
Description Enter the revert reason in this area.
Revert
152
User Training Guide
If you press ENTER to process the Revert request, then Change Man will display the following panel:
---------------------------- REVERT CHANGE PACKAGE ---------- PACKAGE REVERTED COMMAND ===> PACKAGE ID ===> TEST000074 Press ENTER to process; Enter END command to exit.
This panel informs you that the Revert request has been processed. The package status has also been changed from FRZ, APR, REJ or BAK back to DEV.
153
Revert
User Training Guide
Revert
154
User Training Guide
Backout
Backout Overview
The backout function allows you to "de-install" a Change Package after the package has been installed into the production environment and baseline rippled. Change Man will back out the entire Change Package during the Backout process, i.e.: SRC, LOD, LST, JCL, PRC, etc. Once a Change Package has been backed out, the Package will be in BAK status. You must use the Revert function to get the Change Package back to DEV status before you may begin working on it again. If you have remote sites, you must initiate the Backout at the remote site(s). Once the remote sites have been backed out the "reverse ripple" will occur in the development site.
BACKOUT CHANGE PACKAGE Panel

Use this panel to select the Change Package you need to Backout. To access this Panel: Select option B from the Primary Option Menu for Backout and press ENTER
CMNBKOUT ------------------- BACKOUT CHANGE PACKAGE ------------------------COMMAND ===> PACKAGE ID ===> TEST000074 Press ENTER to process; Enter END command to exit.
Field PACKAGE ID
Description Enter the Change Package ID or double check the package ID displayed is still the package you want to work with.
BACKOUT REASONS -Panel

155 Backout
User Training Guide
Use this panel to enter the reasons why you backed out the Change Package. This panel will appear after the Backout Change Package panel.
CMNBKRSN ---------------------- BACKOUT REASONS -----------------------------COMMAND ===> PACKAGE ID: TEST000052 CREATOR: WSER92 STATUS: BAS INSTALL DATE: 19980313
BACKOUT REASONS: ===> Job abended as a result of poor testing. Need to make additional changes. ===> ===> ===> ===> ===> ===> ===> ===> Press ENTER to process; Enter END or CANCEL command to exit.
To exit this panel you can: Enter the backout reason and press ENTER Press PF3 or enter END or CANCEL in the Command line and press ENTER. Change Man will return you to the previous panel
Description Enter the backout reason in this area.
Once you enter the backout reason and press ENTER, Change Man will immediately submit the backout jobs. Change Man will advise you it has submitted the job by displaying a Backout Job Submitted message on the panel you return to.
----------------------------- CHANGE PACKAGE LIST ------ BACKOUT JOB SUBMITTED COMMAND ===> SCROLL ===> PAGE PACKAGE ID STA INSTALL LVL TYPE WORK REQUEST DEPT PROMOTE AUD CREATOR __ TEST000095 BAS 19990106 SMPL PLN/PRM AAAAAAAAAAAA DDDD WSER92 ******************************* Bottom of data *******************************
or
Backout
156
User Training Guide
---------------- CHANGE MAN 4.1.6S PRIMARY OPTION MEN OPTION ===> 1 2 3 4 5 A B C D L M N O Q R T X Build Freeze Promote Approve List Admin Backout CDF Delete Log Monitor Notify OFMlist Query Revert Tutorial Exit -
BACKOUT JOB SUBMITTED
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 Perform administrative functions Back out a package in production Concurrent Development Facility 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
Change Man will also notify you the result of the backout jobs by sending you the following MVS Send messages:
CMN406I - USER000095 BACKED OUT 1999/01/06 @ 10:34:09. CN(INTERNAL) CMN410I - USER000095 BASELINE REVERSE RIPPLED 1999/01/06 @ 10:34:09. CN(INTERNA L) ***
This panel informs you that the Backout request has been processed successfully. The Change Package status is also changed from BAS back to BAK.
157
Backout
User Training Guide
Backout
158
User Training Guide
Browse
Browse Overview
The Browse\Print\Copy facility allows the Change Man user the option of displaying or printing any component managed by Change Man, without having to Checkout the component or enter a valid Change Package. You can view the contents of any component in the current (0) or backup (-1) baseline libraries, or promotion (+1) libraries. This facility provides for member level security checks prior to allowing the user to display or print the member, thus ensuring data integrity. Other features of this option include giving the authorized user the ability to copy a component to a user specified dataset, to perform a rename prior to the copy to a user specified dataset, and to fully expand copy and include statements prior to printing.
BASELINE BROWSE/PRINT FACILITY - Panel

Use this panel to select the list of components to be viewed. Select from components in the baseline libraries, or components in the promotion libraries. To access this Panel: Select option 1 from the Primary Option Menu for Build, then Select option B on the Build Options Menu for Browse.
CMNBRWB0 --------------- BASELINE BROWSE/PRINT FACILITY ---------------------OPTION ===> 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 ===> TEST ===> SRC ===> 0 ===> ===> ===> ===> ===> ===> ===> N 0 N 0 0 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)

159 Browse
User Training Guide
Enter the required fields and press ENTER to proceed to next panel, or leave some of the fields blank and select from the resultant lists. Press PF3 or enter END on the Option line and press ENTER, Change Man will return you to the previous panel.
Field OPTION
Description L - List libraries where component is located. Enter L and Change Man will list all the baseline and/or promotion libraries that contain the component that you specify. B - Browse. Enter B and Change Man will display the component in browse mode. C - Copy. Enter C to copy a member from a baseline or promotion library to a user specified dataset. E - Browse in edit mode. Enter E and Change Man will display the component in edit mode. This allows you to enter standard TSO commands such as EXCLUDE and CHANGE. X - Print expanded. Enter X and Change Man will expand all COPY and INCLUDE statements prior to printing the member. P Print. Enter P to print the member. H History. Enter H to display component history. S - View Stack of SRD. Enter V to display the number of levels stored in the SRD (stacked reverse delta) baseline libraries for the component. Enter the application or leave this field blank to choose from the list of all applications. Enter the library type of leave blank to select from the library type list. Enter 0 to -n to select from the baseline library. Enter 1 to +n to select from a promotion library. Enter the name of the component that you want to browse of print. Enter Y if you wish to build a member list based on additional selection criteria. You will use the following fields for additional selection criteria.
APPLICATION
LIBRARY TYPE
LIBRARY LEVEL
COMPONENT NAME
MEMBER LIST SCAN
Field
Description
Browse
160
User Training Guide
RECORDS TO SELECT
Enter a numeric value to determine when the scan is to be discontinued. If 0 is entered, the scan will display a list of all members in the baseline library that meet the DATA STRING
search criteria.
CASE SENSITIVE Enter Y if the DATA STRING should be searched exactly as entered. Enter N if the scan is to be executed without regard to upper and lower case. Enter the column, for each record, where you want the scan to begin. Enter 0 if you want the scan to begin in column 1. Enter the column, for each record, where you want the scan to end. Enter 0 if you want the scan to end in column 80. Enter a data string that will be used to build a member selection list. If the MEMBER LIST SCAN field is set to N the data string will be ignored.
FROM COLUMN
TO COLUMN
DATA STRING
161
Browse
User Training Guide
Browse
162
User Training Guide
Recompile
Recompile Overview
The recompile function can be used to resolve some of the out-of-synch conditions that can occur from the Audit process. For example, if you checked out and edited a copy component while other source components (not in the Change Package) also use this copy, you would receive an out-of-synch condition (SYNCH5!) when an Audit is performed . To resolve this, you would need to recompile those modules that were deemed to be out-of-synch. This function is similar to staging except that the source is not included in the Change Package. Only the resulting load module is placed into the Change Man Change Package.
RECOMPILE SOURCE Panel

Use this panel to select the component(s) to recompile. The recompile is done from baseline or promotion, directly into staging libraries. To access this Panel: Select option 1 from the Primary Option Menu for Build, then Select option 8 on the Build Options Menu for Recompile.
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 ===> ===> ===> ===> ===> ===> TEST000074 SRC ASM 0 1 (Blank or pattern for list) (Blank for list) (Blank for list) (Baseline 0, Promotion 1 to nn) (1-Online, 2-Batch)
163
Recompile
User Training Guide
To exit this panel you can: Enter the required fields and press ENTER to proceed to next panel, or leave some of the fields blank and select from the resultant lists. Press PF3 or enter END on the Option line and press ENTER, Change Man will return you to the previous panel.
Field OPTION
Description L List. List all of the levels in which this component may be found. Blank - Display member list. A blank in the Option line will display a member list. From this list select the component(s) to be compiled. Enter the ID of the associated Change Package. Enter the name of the component to be compiled. Enter the type of component that is to be compiled. Only a source or like-source component can be used. Enter the language in which the component is written (e.g. COBOL). Enter the level of the library. Use 0 to -999 for baseline versions of a component, or +1 to +99 for promotion versions of a component. 1 - Enter 1 to recompile the component in foreground 2 - Enter 2 to recompile the component in batch mode. NOTE: Batch mode will need to be used for mass recompiles.
PACKAGE ID COMPONENT NAME SOURCE LIBRARY TYPE
LANGUAGE
LIBRARY LEVEL
RECOMPILE MODE
Recompile
164
User Training Guide
ONLINE RECOMPILE JOB INFORMATION - Panel

This panel is used to compile and optionally link a source component. To access this Panel: Will automatically appears after the Recompile Source panel
CMNRCMP1 ------------- ONLINE RECOMPILE JOB INFORMATION ---------------------COMMAND ===> PACKAGE ID: TEST000074 COMPONENT: LIBRARY TYPE: LANGUAGE: DATASET NAME: COMPILE PROCEDURE COMPILE PARMS LINK EDIT PARMS DB2 PRE-COMPILE OTHER OPTIONS SUPPRESS HISTORY STATUS: FRZ INSTALL DATE: 19981230
AAADB2SQ SRC - Source Code ASM WSER200.BASE.ZERO.SRC ===> ===> ===> ===> NO ===> YES ===> YES (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)
JOB STATEMENT INFORMATION: ===> //WSER92N JOB (XXXX,3##),WSER92,CLASS=E,MSGCLASS=3,____________________ ===> // TIME=2,REGION=4M,NOTIFY=WSER92________________________________ ===> //*JOBPARM SYSAFF=ESA1__________________________________________________ ===> //*_____________________________________________________________________ Press ENTER to process; Enter END command to exit.
Field PACKAGE ID STATUS INSTALL DATE COMPONENT
Description The ID of the Change Package that you are working with. The current Change Man status of the Change Package. The date that the Change Package is to be installed. The component that is being staged. If you are staging a component from a development library into Change Man and you are renaming the component, the staged name is the "new name" of the component. The type of component that you are staging. The language name that was assigned to the component.
LIBRARY TYPE LANGUAGE
165
Recompile
User Training Guide
Field DATASET NAME
Description The name of the dataset that contains the component that you are staging. This will either be a Change Man package staging library or a development library. The Change Man compiling procedure that will be used to compile/link the program. If only one procedure is available for this language, this field will be in "browse only" mode. You may type in compile parms for the program. If this program was previously compiled within Change Man, the compile parms found in component history will be displayed. You may type in link edit parms for the program. If this program was previously linked within Change Man, the link edit parms found in component history will be displayed. Enter "YES" if you need to display additional user options such as CICS pre-compile, EZTRIEVE, etc. Your Global Change Man Administrator will define available options for you. Enter Yes to suppress component history data processing for the component being recompiled, the data on the panel will be processed instead. Enter No to perform the opposite, process component history data for the component being recompiled and bypass the values that were specified on the panel.
COMPILE PROCEDURE
COMPILE PARMS
LINKAGE EDIT PARMS
OTHER OPTIONS
SURPRESS HISTORY
Recompile
166
User Training Guide
Exercises for Recompile Exercise #1: Use the Recompile Process to recompile a source or like-source component from the baseline SRC library. Once complete review Package contents to see what the recompile process did.
167
Recompile
User Training Guide
Recompile
168
User Training Guide
Relink
Relink Overview
Any time a statically linked subroutine has been modified, relinking is required. Use this function to relink load modules or to delete a relinked or recompiled load module from your Change Package. The Relink function links a member using LCT images supplied by the user or are created by Change Man if no LCT cards are supplied. A relink target load library to which the member is to be relinked must be specified.
RELINK LOAD MODULES Panel

Use this panel to relink load modules, or to delete previously relinked or recompiled modules. To access this Panel: Select option 1 from the Primary Option Menu for Build, then Select option 9 on the Build Options Menu for Relink.
CMNRLNK0 -------------------- RELINK LOAD MODULES ---------------------------OPTION ===> R - Relink single load module blank - Display member selection list for multiple member processing PACKAGE ID RELINK FROM LCT MEMBER LIST ===> TEST000063 ===> (S-Staging or B-Baseline) ===> (Y - Yes or N - No; member list will be created with input library type) INPUT LIBRARY TYPE ===> (Blank for list) TARGET LIBRARY TYPE ===> (Blank for list) MEMBER NAME ===> (Blank for list; required for option R) COMPILE PROCEDURE ===> (Blank for list) LINK EDIT PARMS ===> DB2 PRE-COMPILE ===> (Y/N) OTHER OPTIONS ===> YES (Y/N for additional user options) JOB STATEMENT INFORMATION: ===> //WSER92N JOB (XXXX,333),WSER92,CLASS=E,MSGCLASS=3,____________________ ===> // TIME=2,REGION=4M,NOTIFY=WSER92________________________________ ===> //*JOBPARM SYSAFF=ESA1__________________________________________________ ===> //*_____________________________________________________________________ Press ENTER to process; Enter END command to exit.
169
Relink
User Training Guide
Enter the required fields and press ENTER to proceed to next panel, or leave some of the fields blank and select from the resultant lists. Press PF3 or enter END on the Option line and press ENTER, Change Man will return you to the previous panel. Description R Relink single load module. Blank - Display LCT member selection list for multiple processing. The ID of the Change Package that you are working with. Enter S or B to relink either from the staging or baseline libraries.
Field OPTION
PACKAGE ID RELINK FROM
LCT MEMBER LIST Enter Y if the LCT library member list is to be created. Enter N if the LCT library member list is not to be created. Member list that will be created will be from the INPUT LIBRARY TYPE field below. INPUT LIBRARY TYPE Enter the input library type. It could either be staging or baseline depending on what was entered in the RELINK FROM field.
TARGET LIBRARY Specify the library type of the load module being relinked. Leave TYPE blank for a member selection list. MEMBER NAME Enter the member name to be processed. Leave this field blank or enter a pattern to generate a list from which a member may be selected The Change Man compiling procedure that will be used to compile/link the program. If only one procedure is available for this language, this field will be in "browse only" mode. You may type in link edit parms for the program. If this program was previously linked within Change Man, the link edit parms found in component history will be displayed.
COMPILE PROCEDURE
LINKAGE EDIT PARMS
DB2 PRE-COMPILE Enter "YES" if this program is a DB2 program. Enter "NO" if this program is not a DB2 program. DATASET NAME The name of the dataset that contains the component that you are staging. This will either be a Change Man package staging library or a development library. Enter "YES" if you need to display additional user options such as CICS pre-compile, EZTRIEVE, etc. Your Global Change Man Administrator will define available options for you.
OTHER OPTIONS
Relink
170
User Training Guide
Exercises for Relink
Exercise #1:
Use the Relink Process to relink a source or like-source component.
Exercise #2:
Use the Relink Process to delete the load module that was recompiled from the recompile exercise.
171
Relink
User Training Guide
Relink
172
User Training Guide
Query
Query Overview
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.
QUERY OPTIONS Panel

Use this panel to selection which Query function you want to execute. To access this Panel: Select option Q from the Primary Option Menu for Query and press ENTER
CMNQMENU ----------------------- QUERY OPTIONS ------------------------------OPTION ===> P C I Package - Query package information Component - Query component information Impact - Impact analysis of component relationships
To exit this panel you can: Enter the required request on the Option line and press ENTER to proceed to next panel Press PF3 or enter END on the Option line and press ENTER, Change Man will return you to the previous panel.
Field
Description
173 Query
User Training Guide
OPTION
P - To review and query package information C - To review and query component information I - To view Impact Analysis of component
QUERY PACKAGE PARAMETERS - Panel

If you want to query the Change Package information then use the Query Package function to obtain this information. The Query Package Parameters panel is used as selection criteria to search the Package Master for the Packages you want to view. To access this Panel: Select option P from the Query Options panel and press ENTER
CMNQRY00 ------------------ QUERY PACKAGE PARAMETERS ------------------------COMMAND ===> SPECIFY SELECTION CRITERIA: PACKAGE ID ===> USER000052 PACKAGE STATUS CREATOR'S 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 ===> ===> ===> ===> ===> ===> ===> ===> ===> ===> ===> ===> ===> (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)
To exit this panel you can: Enter the required fields and press ENTER to proceed to next panel Press PF3 or enter END on the Command line and press ENTER, Change Man will return you to the previous panel.
Field
Description
Query
174
User Training Guide
PACKAGE ID
Enter the Package ID or pattern, or leave this field blank to choose from the list of all applications. Use this field to mask the list of Change Packages according to the entered package status. Enter the TSO ID for the Change Packages to be
PACKAGE STATUS
CREATOR'S TSO ID viewed. WORK REQUEST ID
Enter the Work Request ID for the Change Packages to be viewed. Enter the department for the Change Packages to be viewed. Enter ID of the remote site. Enter the level (simple, complex, super, or participating) of the Change Packages to be viewed. Enter the type (planned or unplanned) of the Change Packages to be viewed. Enter the time span (permanent or temporary) of the Change Packages to be viewed. To view a list of Change Packages that are to be during a range of dates, enter the inclusive dates in the form of YYYYMMDD.
DEPARTMENT
REMOTE SITE AFFECTED PACKAGE LEVEL
PACKAGE TYPE
PACKAGE TIME SPAN
FROM/TO INSTALL DATE installed
To view a list of Change Packages that were created between a range of dates, enter the inclusive dates in the form of YYYYMMDD. Enter Y to view the panel with additional selection criteria. The following panel shows these additional fields.
OTHER PARAMETERS
CMNQRY01 ------------------ EXTENDED SEARCH CRITERIA -----------------------COMMAND ===> NON-SOURCE SOURCE AND LOAD RENAME/SCRATCH INFO CUSTOM COMPONENT ===> ===> ===> ===> (Y/N) (Y/N) (Y/N) (Y/N)
Field
Description
175
Query
User Training Guide
NON-SOURCE
All packages that contain any non-source components (e.g. JCL, PRC, CTL, CPY, etc.). All packages that contain any source to load relationships (i.e compiled programs). All packages that contain any utility specifications (i.e. component scratch or rename requests). All packages that contain either custom forms or on-line forms (dependent upon whether or not your shop has installed the On-Line Forms selectable option).
SOURCE AND LOAD
RENAME/SCRATCH INFORMATION CUSTOM COMPONENT
PACKAGE INFORMATION CATEGORIES Panel The result of the Query Package Parameters panel will display the following panel. This panel is used to select which Package category you are interested in viewing.
CMNQRY03 --------------- PACKAGE INFORMATION CATEGORIES --COMMAND ===> PACKAGE ID: USER000075 CREATOR: WSER92 STATUS: DEV AUDIT RC: ROW 1 TO 18 OF 19 SCROLL ===> PAGE
INSTALL DATE: 19981230
_ General _ 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 ******************************
Place an S beside the Package category you want to view.
QUERY COMPONENT PARAMETERS Panel
Query
176
User Training Guide
If you want to query a specific component in Change Man, then use this panel to enter the selection criteria to search the Package Master for that specific component. To access this Panel: Select option C from the Query Options panel and press ENTER
CMNQCMP1 ----------------- QUERY COMPONENT PARAMETERS -----------------------COMMAND ===> SPECIFY SELECTION CRITERIA: COMPONENT NAME ===> COMPONENT TYPE ===> APPLICATION ===> PACKAGE ID ===> PROCEDURE NAME ===> TSOID ===> DISPLAY MODE ===> SHORT CHECKOUT/STAGING FROM DATE ===> TO DATE ===> (Full name or pattern) (Full library type or pattern)
(S-Short, L-Long) (YYYYMMDD) (YYYYMMDD)
To exit this panel you can: Enter the required fields and press ENTER to proceed to next panel Press PF3 or enter END on the Command line and press ENTER, Change Man will return you to the previous panel.
Field COMPONENT NAME
Description The name of the component to be checked out. In order to mask the selection list, you may use wild cards in this field (e.g. CMN* or CMN?0000). To checkout all the components enter * (be careful). Enter the type of the components to be displayed. For example, enter JCL to list all JCL components. Type the 3 or 4 byte application mnemonic for the Change Package you are creating. Enter the Package ID or pattern, or leave this field blank to choose from the list of all applications. Enter the compiling procedure for the component.
COMPONENT TYPE
APPLICATION
PACKAGE ID
PROCEDURE NAME
177
Query
User Training Guide
TSOID
Enter the TSO ID for the user who last update to the component(s). Enter the Work Request ID for the Change Packages to be viewed. Enter the option desired for viewing historical nformation for the component. LONG - To view all historical information, including installed packages SHORT - To view only the information of packages in motion . Enter the from and to dates of the time period you want to search in.
WORK REQUEST ID
DISPLAY MODE
RCHECKOUT / STAGING FROM DATE TO DATE
IMPACT ANALYSIS OF COMPONENTS Panel

Use this panel to enter the selection criteria you want to use for searching the Impact Analysis table. The search will look for relationships for the parameters you have entered. To access this Panel: Select option I from the Query Options panel and press ENTER
CMNIMPMP --------------- IMPACT ANALYSIS OF COMPONENTS ----------------------COMMAND ===> SPECIFY SEARCH CRITERIA: COMPONENT NAME ===> COMPONENT TYPE ===> APPLICATION ===> RELATIONSHIP ===> RELATIONSHIP TO ===> Press ENTER to process; Enter END command to exit.
To exit this panel you can: Enter the required fields and press ENTER to proceed to next panel Press PF3 or enter END on the Command line and press ENTER, Change Man will return you to the previous panel. Description
Field
Query
178
User Training Guide
COMPONENT NAME
The name of the component to be checked out. In order to mask the selection list, you may use wild cards in this field (e.g. CMN* or CMN?0000). To checkout all the components enter * (be careful). Enter the type of the components to be displayed. For example, enter JCL to list all JCL components. Type the 3 or 4 byte application mnemonic for the Change Package you are creating. Enter a relationship to further clarify the request. To obtain a list of relationship types, leave this field blank and press ENTER. You must specify a relationship by specifying a library type first in this field. Valid types are: CPY, LOD, PGM, DSN. This is optional when performing a 'downstream' search. It is required for an 'upstream' search. Enter the name or pattern (denoted with an asterisk (*)) of a component with which to search for a 'backward' relationship to the Component Name specified above. If you enter a value in this field, Change Man will show the backward link to the Component Name defined above. If the Component Name is left blank, Change Man will show all backward relationships. For instance, entering the name of a like-copy member here will furnish a list of all components that 'COPY' this component.
COMPONENT TYPE
APPLICATION
RELATIONSHIP
RELATIONSHIP TO
179
Query
User Training Guide
Exercises for Query
Exercise #1:
Use the Query function to view all packages that are in FRZ status for any application. Then select one of the packages from the resultant Package List and view the Approval List for it.
Exercise #2:
Use the Query function to view a JCL component, to see in how many packages it currently exists. You might need to search the baseline JCL library for a valid component name.
Query
180
User Training Guide
Compare
Compare Overview
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 executed in either online or batch mode. The online portion is executed through the CMNCDCPR program. All the parameters that the program uses are hardcoded within the load module itself. Program SERCOMPR controls the compare function that executes the CMNCDCPR program. The batch portion is executed through the CMN$$CPR skeleton.
COMPARE Panel
You can use this panel to enter which component you want to run the compare function on. To access this Panel: Select option 1 from the Primary Option Menu for Build, then Select option C on the Build Options Menu for Compare.
CMNCOMP1 -------------------------- COMPARE --------------------------------COMMAND ===> C - Compare of one component blank - Display member selection list COMPARE MODE PACKAGE NAME COMPONENT NAME LIBRARY TYPE SOURCE LIBRARY ===> ===> ===> ===> ===> O USER000093 JCL 0 (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: ===> //WSER92N JOB (X170,374),WSER92,CLASS=E,MSGCLASS=3,____________________ ===> // TIME=2,REGION=4M,NOTIFY=WSER92________________________________ ===> //*JOBPARM SYSAFF=ESA1__________________________________________________ ===> //*_____________________________________________________________________ Press ENTER to process; Enter END command to exit.

181 Compare
User Training Guide
Enter the required fields and press ENTER to proceed to next panel, or leave some of the fields blank and select from the resultant lists. Press PF3 or enter END on the Command line and press ENTER, Change Man will return you to the previous panel.
Field OPTION
Description C - Compare of one component blank - Display member selection list 'O' - To compare online 'B' - T perform the compare via batch Enter the full Package ID The name of the component you want to compare. In order to mask the selection list, you may use wild cards in this field (e.g. CMN* or CMN?0000). To checkout all the components enter * (be careful). Enter the library type. This is the level of baseline or promotion from which components are to be compared. Baseline level 0 refers to the most current version of production, down to -9 as the least current prior version. Level +1 refers to the first level of Promotion, up to +n as subsequent levels. This is a required field; leave it blank to select from a list of all libraries in which a specific component resides. Indicate how Change Man is to handle disposition of the report output.
COMPARE MODE
PACKAGE NAME COMPONENT NAME
LIBRARY TYPE SOURCE LIBRARY
PROMPT FOR REPORT DISPOSITION
Compare
182
User Training Guide
Exercises for Compare
Exercise #1:
Find a component in a Change Package that has been changed and run the compare function on this component. Compare it to the baseline library component. Run the compare function on the same component, but this time use a promotion library.
Exercise #2:
183
Compare
User Training Guide
Compare
184
User Training Guide
Scan
Scan Overview
The Library Scan facility enables you to 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 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. Note: This function does not impact the Baseline Browse scan.
LIBRARY SCAN UTILITY Panel

Use this panel to To access this Panel: Select option 1 from the Primary Option Menu for Build, then Select option S on the Build Options Menu for Scan.
185
Scan
User Training Guide
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 ===> ===> ===> ===> ===> SRC O NO NO (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)
===> ===> ===> 0 ===> 0 ===> ===> ===> ===> OR ===>
To exit this panel you can: Enter the required fields and press ENTER to proceed to next panel, or leave some of the fields blank and select from the resultant lists. Press PF3 or enter END on the Command line and press ENTER, Change Man will return you to the previous panel.
Field APPLICATION
Description Type the 3 or 4 byte application mnemonic for the Change Package you are creating. Enter the library type. 'O' - To scan online 'B' - To perform the scan via batch YES' - To display only the member names and no data. 'NO' - To display the member name and the data
LIBRARY TYPE SCAN MODE
LIST MEMBERS ONLY
Scan
186
User Training Guide
Field DEPENDENCIES
Description 'YES' - To scan for copybook, dataset names, programs, procedures and other types of dependencies. Optionally the language type such as COBOL, JCL, BAL, PLI and other can be specified in data string 1. 'NO' - For standard data string scan. Specify a number of records to display, or enter 0 to select all records that exist in the library. 'YES' - To find occurrences of the data string exactly as entered. 'NO' to find all occurrences, both upper and lower case. Enter starting and ending displacements, or columns, to begin the search within each record. Enter the same number in each field to search that displacement only. Enter '0' to search all displacements. Enter a range of components to scan, or leave the BEGIN field blank to search all members. Scan a single member by entering its name in the BEGIN field. Enter a pattern (ABC*) in the BEGIN field to limit the scope of the search (the END field will be disregarded). A range such as MEMBERA to MEMBERZ may be entered to define a range, even if those members do not actually exist in the dataset. Enter a character string. Imbedded blanks or non-alphabetic characters will be searched for in place. To include leading or trailing blanks, enclose the string in apostrophes ('). Enter 'AND' if both the first and second strings are to be found on one line of the member scanned. Enter 'OR' if the scan is to contain either the first or second string within the scanned member. Enter a second character string. Imbedded blanks or nonalphabetic characters will be searched for in place. To include leading or trailing blanks, enclose the string in apostrophes (').
RECORDS TO SELECT
CASE SENSITIVE?
DISPLACEMENT
COMPONENTS TO SCAN
DATA STRING 1
AND/OR
DATA STRING 2
187
Scan
User Training Guide
Exercises for Scan
Exercise #1:
Use the Scan function to scan for character new in the JCL library type. Scan in online mode, between columns 5 to 72, with no case sensitivity and select all the records.
Scan
188
User Training Guide
Compress
Compress Overview
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 Re-stage 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. Since partitioned datasets do not reuse space when you make deletions and updates, you may have to compress the Staging libraries to reclaim the "dead space".
COMPRESS STAGING LIBRARIES Panel

This function is used to submit the batch job that will compress the partitioned datasets (staging libraries) associated with a change package. Since PDS's do not reuse space when deletes and updates are made, the staging libraries may need to be compressed to reclaim 'dead' space. Use this panel to provide JOB card information for the batch job. To access this Panel: Select option 1 from the Primary Option Menu for Build, then Select option Z on the Build Options Menu for Compress.
CMNCPRSS ----------------- COMPRESS STAGING LIBRARIES ----------------------COMMAND ===> PACKAGE ID ===> USER000075 JOB STATEMENT INFORMATION: ===> //WSER92N JOB (XXXX,333),WSER92,CLASS=E,MSGCLASS=3,____________________ ===> // TIME=2,REGION=4M,NOTIFY=WSER92________________________________ ===> //*JOBPARM SYSAFF=ESA1__________________________________________________ ===> //*_____________________________________________________________________ Press ENTER to process; Enter END command to exit.
To exit this panel you can: Enter the required fields and press ENTER to submit the batch job. Press PF3 or enter END on the Command line and press ENTER, Change Man will return you to the previous panel.
Field
Description
189 Compress
User Training Guide
PACKAGE ID
Enter the full Package ID
Exercises for Compress
Exercise #1:
Run a compress on the last change packages you were working on.
Compress
190
User Training Guide
Log
Log Overview
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.
BROWSE ACTIVITY LOG Panel

Since the Activity Log may 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. 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 has been cleared for the date range you need, you have to access the backup file. To access this Panel: Select option L from the Primary Option Menu for Log.
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 _ 06 Invalid Compiling Procedure _ 07 Invalid Designate Remote Sites _ 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
CMNLOGEX -------------------- BROWSE ACTIVITY LOG ----------------------------COMMAND ===> SCROLL ===> PAGE
191
Log
User Training Guide
ONLINE BROWSE ===> YES FROM DATE ===> TO DATE ===> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ IND 16 18 20 21 22 30 40 42 44 48 50 80 82 83 84 85
(YES-online; NO-batch) (YYYYMMDD, optional) (YYYYMMDD, optional)
LOG DESCRIPTION Baseline Reverse Ripple Install Package Aged Approve a Package Calendar Re-Synch Staging Libraries Aged Reject a Package Freeze a Package Selectively Unfreeze a Package Demote a Package Promote a Package Audit a Package Create a Package Checkout a Component Potential Checkout Conflict Stage a Component Overlay Previous Module
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 _ 86 Delete Module From Package _ 88 Copy Forward a Package _ 90 Monitor Limbo and internal scheduler ******************************* BOTTOM OF DATA *******************************
To exit this panel you can: Enter the required fields and press ENTER to submit the batch job. Press PF3 or enter END or CANCEL on the Command line and press ENTER, Change Man will return you to the previous panel.
Field ONLINE BROWSE
Description 'Y' - To browse activity log online 'B' - To browse activity log in batch
Log
192
User Training Guide
FROM DATE
Enter the beginning date, in YYYYMMDD format, of the specific period from which to display information. To display all selected event types from the activity log, leave this field and the next field blank. Enter the ending date, in YYYYMMDD format, of the specific period for PACKAGE ID which information is to be displayed. To display all selected event types from the activity log, leave the FROM DATE and TO DATE fields blank.
TO DATE
Enter S next to each log selection description you wish to view. IND This is an internal indicator to Change Man signifying each type of log selection criteria. Each log selection criteria is described here.
LOG DESCRIPTION
Change Man will display the following panel while the search is being processed.
CMNLOGWT ------------------------ IN PROGRESS -------------------------------
Your screen is locked - please wait Date: 1999/01/09 Time: 13:23 The Log function is gathering information from the log file. +-----------+ +-----------+ | | | | | Log | | Log | <----- | File | | | | | +-----------+ | | +-----------+
Exercises for Log
Exercise #1:
Run an online log browse on the Baseline Ripple category on the entire log file.
193
Log
Glossary
Application ID Application ID is used to identify a project within Change Man. Applications / Projects are defined groups for which Change Packages are to be created and manipulated. Usually a four-character code is assigned to a specific Application. They are used to identify package ownership.
Approval The process whereby Change Packages are approved by designated individuals prior to installation into baseline / production.
Audit A Change Man utility that, in addition to other functions, inspects the Staging libraries for any out-of-synch conditions, source to load integrity, etc.
Audit Lite A subset of the Audit utility, it inspects the staging libraries of a Change Package for discrepancies between package components.
Baseline Library A Change Man library which stores the most current version (0) of production components, in addition to a pre-defined number of previous versions (-1, -2, etc.).
Baseline Ripple The process whereby a component becomes the new production component, the previous production component becomes the 1 version, -1 becomes 2, and so on. This process is called baseline ripple. The baseline ripple starts with the oldest baseline library and works its way back to the most current library.
Change Package Within Change Man, a Change Package is the vehicle in which all changes are moved from a development environment to a production environment. Change Packages may contain one or more components, which are required for a change.
Change Man Package Life Cycle This is a description of the complete steps or processes a Change Package may have in the Change Man system. (See chapter in this section for complete details). Checkout The act of copying components from baseline libraries to staging or development libraries.
Compile The process of transforming source into object format.
Component A single member of a Change Package. Usually, a member of a library that has been brought into Change Man for the purpose of being modified. The component could be a source module, load module, PROC, JCL, copybook, DDL, datalib member etc.
Concurrent Development Facility (CDF) A selectable Change Man option which allows you to reconcile multiple versions of a component.
Demotion The process whereby components are removed from promotion libraries.
Development/Personal Library Any library, other than Change Man or production libraries, in which a component resides.
Freeze The act of locking Change Packages so that modifications are prohibited. It also makes a package eligible for approval.
Global Parameters These parameters are defined in the initial Change Man setup to tailor Change Man to your data center environment. They are modifiable at any time by the Global Administrator.
Installation Installation is the final process in the Change Package Life Cycle. It is the process that does the final copy from the Package Staging libraries into the baseline/production libraries. Library Type A three character identifier which represents the various component types in an application. Source components have library type of SRC, copybook components use CPY, load modules use LOD, etc.
Local Parameters These parameters are defined within the initial setup of each Change Man Application (project). They will assist in tailoring each separate application according to their individual needs.
Mass Stage The process of staging a multiple number of components into a Change Package. This facility moves the processing for a set of staging requests to a batch job. This job will spawn and submit an individual batch job for each stage request.
Online Forms Manager A selectable Change Man option which allows you to create and store forms as part of a change package.
Package ID Each Change Package is automatically assigned a unique package ID. Consisting of the Application ID and a sequential number (e.g. PAYR000001).
Package Master The repository for all Change Man information, including package definitions, components, administration information, and so on. It is typically a VSAM file.
Package Staging Libraries Package Staging libraries are created solely for the purpose of holding components of a particular Change Package. Package Staging libraries are the living Change Package. The contents of the staging libraries are copied to the baseline libraries during the installation process.
Permanent Package A type of Change Package that is used to hold components that will be installed into the baseline libraries. Permanent packages usually go through all the processes in a Package Life Cycle.
Planned Package A type of Change Package which is created during normal business hours in a non-emergency situation. Its Installation is subject to the complete approval list
Production Library The library that contains all production versions of each component. Separate library types may utilize separate production libraries. Project Synonymous with the term "application". Applications are defined groups for which Change Packages are to be created and manipulated.
Promotion A pseudo-production environment that allows for a variety of testing. Also, it is the act of copying a component from staging to a promotion environment or level.
Relink The process of transforming object code into an executable load module.
Stage This function is used to copy components from development or personal libraries into Change Man Staging libraries. If the component is source (SRC), there is a second Staging step which compiles, link/edits, binds, etc. the component into an executable load module. Stage is also the function that you use to make changes or modifications to the components.
Staging Library Change Man libraries in which components are stored, and can be modified and tested. From these libraries, the component is installed.
Temporary Package A type of Change Package that is used for temporary fixes or changes which the user does not want to install into the baseline libraries. Typically components of a temporary package will be installed into a special library used to hold temporary fixes. Temporary Packages are usually created in conjunction with Unplanned Package, which do not need to go through all the processes in a Package Life Cycle.
Unplanned Package A type of Change Package which is created for an emergency situation. Often created outside of normal business hours. If an Unplanned Package is created during normal business hours it is treated as a Planned Package and is subject to the complete Package Life Cycle and Approval list. If created outside of regular business hours, then not all Package Life Cycle processes are required and usually there is an abbreviated approval list. Its installation date is not dependent on the Planned Installation calendar.

Change Man

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Change Man

Enviado por

Direitos autorais:

Formatos disponíveis

Change Man / MVS

User Training Guide (Release 4.1.6)

DB2 is a registered trademark of International Business Machines.

User Training Guide

Primary Option Menu + Build Options.......................................................................33

User Training Guide

User Training Guide

REJECT REASONS - Panel....................................................................................................... 134 Exercises for Approval ........................................................................................................... 136

User Training Guide

Exercises for Compare............................................................................................................ 183

User Training Guide

SOFTWARE PRODUCTS COMPAREX

User Training Guide

Concurrent Development Facility

User Training Guide

User Training Guide

User Training Guide Content

User Training Guide

Change Man Course Offerings

User Training Guide

The intended audience for these courses is:

User Training Guide

Change Man for New Users

Students will learn:

User Training Guide

Change Man for Experienced Users

Students will learn:

User Training Guide

User Training Guide

Features of Change Man

User Training Guide

The Change Man ALLSITE Change Package Life Cycle

Main Process flow

User Training Guide

User Training Guide

Change Man Library Environment (ALLSITE - Data Flow Diagram)

New Component Development

Test Environment (level 10) Test Environment (level 20)

Test Environment (level 30)

Temporary Work File

Stage (S2) Edit

Change Package STAGING Audit Freeze Approve Checkout

User Training Guide

Change Man Library Environment (DEVPROD Site - Data Flow Diagram)

New Component Development

Test Environment (level 10) Test Environment (level 20)

Test Environment (level 30)

Temporary Work File

Stage (S2) Edit

Change Package STAGING

Checkout Remote Promote

Baseline Ripple Distribute Baseline (0)

Remote Test Environment

Baseline (-1) Reverse Baseline Ripple Baseline (-2)

Production Staging Libraries

Remote Production (0)

Remote Production (-1)

User Training Guide

User Training Guide

Change Man Terminology

User Training Guide

User Training Guide

Accessing Change Man

Date : Time : Version :

* Bottom of data

* Bottom of data **

*** Bottom of data *