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.

.....9 Corporate Background.................Panel...................................................... 21 Change Man Library Environment (DEVPROD Site ................................. 63 UTILITY: RENAME / SCRATCH OPTIONS – Panel ..........Panel........................................................................................................................................................................................Panel ...Panel .......................... 36 BUILD OPTIONS – Panel ...............................................................57 Update Overview......................................................................................................................................................................................................................................................................................................................................................................................... 16 Introduction............................... 24 Accessing Change Man ....................................................................... 57 UPDATE: PACKAGE INFORMATION – Panel..................................................................................Panel........................................................................ 33 NOTIFY – Panel ....................................Panel ................ 33 PRIMARY OPTION MENU – Panel................... 19 Change Man Library Environment (ALLSITE ............................................... 59 UPDATE: AFFECTED APPLICATIONS ............................................................. 28 Primary Option Menu + Build Options.......................................................................Panel............................................................................ 59 UPDATE: SCHEDULING DEPENDENCIES ............................................. 56 Update ... 34 CHANGE MAN TUTORIAL – Panel.............................................................................................. 38 Create ........................................................ 37 PLANNED INSTALLATION CALENDAR .......................................................................................................Data Flow Diagram) ............................................. 63 Table of Contents .....................................................................................User Training Guide Table of Contents Preface.................................. 57 UPDATE: CONTROL INFORMATION – Panel.................Panel....................................... 47 CREATE: ON SITE INFORMATION .............................................................................................................. 60 UPDATE: SITE INFORMATION – Panel ........................................................................................................................ 57 UPDATE: PACKAGE DESCRIPTION ................................................ 13 Change Man® for New Users.....Panel ........................................ 41 CREATE: PACKAGE DESCRIPTION ...........................................Panel............... 53 Commonly Asked Questions..............................................................................................................39 Create Overview .................................. 60 UPDATE: COMPLEX/SUPER INFORMATION .................................................... 45 CREATE: INSTALLATION INSTRUCTIONS .............Panel .....................................................................................17 What Is Change Man ............. 22 Change Man Terminology ........................................................................ 15 Change Man® for Experienced Users ... 26 Change Man Panel and Menu Navigation ......................................................................................................... 9 User Training Guide Content................................................................................. 58 UPDATE: INSTALLATION INSTRUCTIONS ......................................................................................................................................... 39 CREATE: CREATE A NEW PACKAGE .................................................................................................................................................................................................................. 61 Utility.......................................................................................Data Flow Diagram) .......................... 51 CREATE: COMPLEX / SUPER INFORMATION .................................................................................................................. 17 The Change Man ALLSITE ‘Change Package Life Cycle’ .........Panel ...................................... 49 CREATE: AFFECTED APPLICATIONS ................................................................................................................................................................................ 55 Exercises for Create ............ 12 Change Man Course Offerings ...............................................................................63 Utility Overview .......................................................................................................................................................33 Primary Option Menu + Build Options Overview..........

................................................................................................................................................................................ 74 Commonly Asked Questions.......................................Panel.................................................................................................................................................................................................................................69 Checkout Overview ...............Panel...................................Panel ............................................................... 81 STAGE: PACKAGE COMPONENTS -Panel .................................................................................................... 88 COMPONENT LIST PARAMETERS – Panel...................................... 131 PACKAGE INFORMATION CATEGORIES ........................... 127 Exercises for Promote/Demote ...................................................................................... 133 Table of Contents ......................103 Audit Overview .................. 125 DEMOTE OPTIONS – Panel...................................................................Panel ....................................... 97 BROWSE COMPRESSED LISTINGS ................... 103 AUDIT CHANGE PACKAGE . 92 Commonly Asked Questions..........................................................................................................................................Panel................................ 129 APPROVE PACKAGE PARAMETERS ..........................................................................................................................................................................123 Promote/Demote Overview . 123 PROMOTE OPTIONS -Panel ..................................... 95 Listing .................................................................................................................................................................................................. 120 Exercises for Freeze........................................................................................................................... 105 Out-of-synch Conditions..........Panel ....................................................................... 77 Stage ...................................................117 Freeze Overview...... 95 Exercises For Staging ......................................................................................... 129 APPROVE/REJECT OPTIONS ................................................................................... 115 Freeze ......................................... 84 STAGE: COMPILE AND LINK ......................................................................................................................................................................................................................................................................................... 132 APPROVAL LIST – Panel.............................................................. 121 Promote ..................................................................97 Listing Overview ................... 77 Exercises for Checkout ................................................................................................................................ 80 STAGE: FROM DEVELOPMENT – Panel................................................................................................................................................................................... 97 Audit............................................ 66 Exercises for Utility ............................................ 70 CHECKOUT: PACKAGE COMPONENTS – Panel................................................................. 64 Commonly Asked Questions............................................................................................................................................................User Training Guide UTILITY: BASELINE SELECTIONS .................................................................... 123 PROMOTE CHANGE PACKAGE – Panel .......................................................................................................................................................................................... 67 Checkout ............................ 70 CHECKOUT .............................................................................................................................................79 Stage Overview... 69 CHECKOUT OPTIONS – Panel........................................................................ 114 Exercises for Audit ............................................ 128 Approve..................................................... 117 FREEZE OPTIONS – Panel...................................................................................................Panel .. 117 UNFREEZE / REFREEZE Package – Panel ..................................................................................................Panel................................................................................................................................................ 111 Commonly Asked Questions...........................129 Approve Overview ..Panel............................................................................................................................................................................................. 79 STAGE OPTIONS .......... 126 COMMON COMPONENTS –Panel .............................................................................................................................................................................................................................................................................................................................................................................................................................................................................

........User Training Guide REJECT REASONS ................................................................................................................................................................................................................................ 142 Exercises for List ................................................. 169 RELINK LOAD MODULES – Panel........................... 173 QUERY OPTIONS – Panel.................................................................................................173 Query Overview..............................................159 Browse Overview ................................................................................................................................................................................................................................................................................................................................................................................163 Recompile Overview .......................................................................................................................................................... 140 PACKAGE LIST OPTIONS ............................................................................................................................................... 151 REVERT CHANGE PACKAGE ........................................................................................................................................................................155 Backout Overview ...................................... 152 Backout ..... 178 Exercises for Query...................................................................................................................................................................................................................................151 Revert Overview....................................................................................................................................... 159 Recompile............................................................. 146 RESTORE MEMO DELETED PACKAGES – Panel ..... 143 Delete........................................................ 165 Exercises for Recompile .. 173 QUERY PACKAGE PARAMETERS ..... 155 Browse.................................. 174 PACKAGE INFORMATION CATEGORIES – Panel .............................................................................................................................. 180 Compare.................................................... 155 BACKOUT CHANGE PACKAGE – Panel.............................................................................................Panel ..... 145 MEMO DELETE CHANGE PACKAGE – Panel.......................................Panel ....................................................................................................................................................................................................Panel................... 176 QUERY COMPONENT PARAMETERS – Panel............................................................................. 181 Table of Contents ......... 167 Relink ..................................................................................................................................................Panel..............................Panel ...........................................................Panel.............................................................................................................137 List Overview .................................................................................................... 138 CHANGE PACKAGE LIST ........................ 181 COMPARE – Panel................................................................................................... 136 List......................................................................................................................................................Panel ........................... 134 Exercises for Approval .......................................................................................................................................................................................................................................................................................... 176 IMPACT ANALYSIS OF COMPONENTS – Panel................................... 163 ONLINE RECOMPILE JOB INFORMATION .................................................................................................................... 159 BASELINE BROWSE/PRINT FACILITY ................. 137 PACKAGE LIST PARAMETERS ....................................................................145 Delete Overview ....... 155 BACKOUT REASONS -Panel................................... 148 Revert ...169 Relink Overview....... 171 Query...................Panel.................................................................................................................................................................................................................... 163 RECOMPILE SOURCE – Panel ....... 151 REVERT REASONS.........................................................................................................................................................181 Compare Overview................................................................................................................Panel ....................................................................... 145 DELETE OPTIONS – Panel ................................................................................................................................................................................................. 169 Exercises for Relink.........

....................................................................185 Scan Overview.....................191 Log Overview .................................................................................................................................................................................................... 188 Compress ................................................... 189 COMPRESS STAGING LIBRARIES – Panel................................................................................................................................................................................................................................... 190 Log........................................................................ 183 Scan ..................................................................................................................................................................................................................................................................................................................................... 193 Glossary ..................... 191 BROWSE ACTIVITY LOG – Panel........................................................................................................................................................................... 185 Exercises for Scan................ 185 LIBRARY SCAN UTILITY – Panel...................................................................................................................................................................................................................User Training Guide Exercises for Compare................................................................ 189 Exercises for Compress....................................................................189 Compress Overview....... 191 Exercises for Log ................................194 Table of Contents .........................

9 Preface .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. project-based application development and source code reconciliation. load module and text comparison utility that automates the complex tasks of file comparison and systems testing.User Training Guide Preface Corporate Background SERENA Software . 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. COMPAREX plays a vital role in the testing and validation phase of year 2000 conversion projects.400 data centers worldwide. SERENA offers a comprehensive range of services to its customers including support. COMPAREX can identify differences between any two films. software quality assurance. with an office in the U. implementation services and frequent software enhancements. SOFTWARE PRODUCTS COMPAREX ® COMPAREX is a multi-function database. reconciliation of production source and load libraries. The company's focus is increasing software development productivity while reducing the cost of computing for mainframe-based applications. test and implement date-sensitive applications in year 2000 situations. SERENA's Solutions/2000 makes it easy to identify. SERENA is headquartered in Burlingame.The Change Specialists . COMPAREX is an essential tool for application testing.K. modify. Along with innovative software.400 corporate licenses worldwide and is the leading comparison tool for Fortune 1000 organizations. education. SERENA's products are used today in more than 2. California. COMPAREX has more than 1. By performing line-by-line byte-level comparisons.

STARTOOL ® STARTOOL provides an on-line environment for application and system programmers in an IBM OS/390 or MVS environment. identify compile and execution time options (COBOL). direct access and VSAM files. reconcile load modules to source code. including the capability to find and change date-sensitive code. users have access to powerful and versatile tools critical for year 2000 conversions. Change Man ® Change Man is a comprehensive system designed to provide both reliable and streamlined implementation of software changes from development into production. significantly reduces implementation time and improves quality of new releases. 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. the eight-version reconciliation tool. PDSE. To guide you through the reconciliation process. Preface 10 . Change Man improves the availability of your software by ensuring that changes are successful when they get to production. including editing and managing PDS. It also cuts maintenance costs and provides the most thorough treatment of concurrent development available. and their contents. Optima Software markets Change Man in the US and selected markets internationally. locate and replace data in groups of members and data sets. CDF's Version Editor displays all the differences in multiple colors.User Training Guide TM Concurrent Development Facility Concurrent Development Facility (CDFTm). sequential. CDF quickly compares and merges ongoing development and third party software with year 2000 remediation into one consolidated file. It can perform complex file and data management tasks. With STARTOOL. It is the fastest implementing software change management system for MVS environments. The CDF Version Impact Analysis facility helps you to efficiently plan and manage your application upgrade projects.

com.serena. It speeds development and problem resolution with the ability to automatically detect. StarWarp addresses business rules assuring that certain activities can only occur on certain days. or via Email at info@serena.com. decrementing or specifying default values for day. such as the last day of the month or the first Monday of the quarter. and enables programmers to create test data for year 2000 conversion projects by automating the process of incrementing. visit SERENA on the World Wide Web at www. It offers a unique bidirectional high-speed file transfer that improves development by eliminating TSO bottlenecks. or aging the dates in existing files. and recover from changes across local and remote environments. CA). StarWarp minimizes the need to write batch programs for each file-aging situation. SyncTrac was jointly developed with High Power Software (Sacramento. For More Information. SyncTrac@ SyncTrac is an MVS software environment synchronization and data set change tracking product. and century fields. 11 Preface . It ensures synchronization of multiple environments to guarantee system integrity and recoverability in the event of a disaster. 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. month.User Training Guide TM StarWarp StarWarp addresses the issue of Data Aging by providing a method of shifting. StarWarp helps by providing basic date aging capabilities. For more information on any of these products. SyncTrac provides a standardized approach for maintenance and distribution of software thereby reducing redundant tasks performed by programmers. report. thus providing the ability to perform necessary testing without the need to write one-time specialized programs for each test scenario. year. TM X:Change X:Change delivers a single GUI interface to MVS data that provides consistency and ease of use.

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

User Training Guide Change Man Course Offerings SERENA Software International offers the following Change Man training courses. These courses are typically taught at the client’s location: q Change Man® for New Users Change Man® for Experienced Users 1 day 1 day q 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 .

Audit (brief overview). Approve (baseline). Browse (basics).User Training Guide Change Man® for New Users Course Duration .e. 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. Listing Students will perform many hands-on exercises to develop confidence with core product functionality and panel navigation.1 day Intended audience: • • • First time users of Change Man. Create. Freeze. Team Leaders. Promote. Delete. 15 Preface . Checkout. application development staff Individuals who will periodically use Change Man to review development work or approve Packages. Stage (basic functions). Query Build Options: Dates. Update. List (basic functions). Utility.e. i. i. Project Leaders. Tutorial. Build. 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.

Revert Topics covered: • • • • • • • Primary Options: Build. Promote (Demote). List (detailed overview). 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. Audit (detailed overview). Recompile. terminology. Compress. Relink. architecture. Browse (all functions) CMNWRITE step in the compile process Introduction to Change Man CDF and DB2 options Introduction to OFM (Custom) Review of installation. Log Build Options: Stage (all functions). concepts and facilities Change Man internals such as CMNWRITE. Compare.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. Relink. Install jobs. Backout. Preface 16 . Scan. Revert. 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. Recompile. 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. Freeze (Unfreeze).User Training Guide Change Man® for Experienced Users Course Duration .

17 Introduction . 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 . or PL/I CICS programs written in Assembler. COBOL II. COBOL III.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. and utility control cards Copy code used in the compile process Batch programs written in Assembler. It is a system that manages and automates the process of migrating software changes. COBOL. from a development environment to any test environment and then to the production environment. such as: • • • • • • • • • • • • • • JCL. any other component that can be stored in a PDS or PDS-Like structure like 'Librarian' or 'Panvalet'. Change Man can manage the installation of a variety of components. COBOL. A comprehensive TSO/ISPF interface guides the user through various change management processes. COBOL III. PROCs. COBOL II.. or applications..

PDS/e) Full suite of on-line and batch query and reporting capabilities Maintains all historical information in a single repository Introduction 18 . Panvalet.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. or PDS.

through the testing environments. It is a step-by-step description of the most common processes required to migrate a change from production to development. Processes within brackets are potentially optional. 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 . and then back to the production libraries. The Package status is also indicated in the lower right-hand corner of the process box.User Training Guide The Change Man ALLSITE ‘Change Package Life Cycle’ An overview of the Change Man Lifecycle is given below.

For source components. the Change Package may then be Promoted. the information that Change Man needs in order to track and control the package is entered. and is identified by a unique package ID automatically generated by Change Man. whether it is a temporary or permanent change. ZEKE. After successfully passing the audit. staging will ordinarily run the appropriate translation procedure to create associated load modules. ESP. the next step is to Freeze the Change Package. etc. When a Change Package is created.User Training Guide 1. 4. If the CMN method (Change Man's internal scheduler) was selected. 6. Once the package has been installed. After successfully staging all components in the Change Package. promote from system testing to acceptance testing).g. A Change Package contains all of the elements to be edited and installed into production. 8. the package is ready to be installed. etc. Promotion is an optional step. The audit process ensures that no unexpected problems will occur. i. Change Man will automatically install the package on the date and time specified at package creation. JOBTRAC. 3. This locks the package (prohibiting further changes). and the new baseline 0 version is installed. 5. Change Man alerts you to the problem by creating an out-of-synch condition for the package. Change Man will perform the Baseline Ripple. the Change Package must pass an Audit before Freeze. Baseline Ripple is the process that Change Man executes to version all package components. etc.). if they aren't there already. the package will be installed immediately after the final approver has approved it. Change Man will convey the install information to that scheduler so that it can install the Change Package. if a component in the production library has been changed since it was checked out. The first step of the Change Package Life Cycle is the Create process. Components such as documentation or copy members are simply copied into the staging libraries. Depending on the installation. the installation date and time. Promotion allows a Change Package to be moved through various levels of testing (e. 2. Package components are now ready to be Staged. Introduction 20 . and makes the package available for the promotion and approval processes.g. This includes the implementation instructions. For example. 7. Once all of the necessary Approvals have been gathered by Change Man. With checkout. If the Manual installation method was selected when the package was created. -1 becomes -2.: 0 becomes -1.e. CA7. The typical next step is to Checkout components from baseline. -2 becomes -3. If an external scheduler is used (e. 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. In the stage process the user can make all the changes or modifications required to all components.

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 (ALLSITE .

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 it’s 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

load modules use ‘LOD’. Library Type A three character identifier which represents the various component types in an application. The component could be a source module. Consisting of the Application ID and a sequential number (e. a member of a library that has been brought into Change Man for the purpose of being modified. etc. Source components have library type of ‘SRC’. It also makes a package eligible for approval.g. load module. Freeze The act of locking Change Packages so that modifications are prohibited. link/edits. there is a second Staging step that compiles. Usually. 25 Introduction .User Training Guide Component A single member of a Change Package. PROC. etc. copybook components use ‘CPY’. it is the act of copying a component from staging to a promotion environment or level. the component into an executable load module. PAYR000001). Promotion A pseudo-production environment that allows for a variety of testing. copybook. If the component is source (SRC). Package ID Each Change Package is automatically assigned a unique package ID. The contents of the staging libraries are copied to the baseline libraries during the installation process. Stage This function is used to copy components from development or personal libraries into Change Man Staging libraries. datalib member etc. Also. binds. DDL. Stage is also the function that you use to make changes or modifications to the components. JCL. 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.

6 PRIMARY OPTION MENU ---------. with your host security system.1. During the signon initiation you will be presented with a temporary Change Man Title panel. Check with your Global or Local Admin group for CLIST name or access procedures. Change Man dynamically builds this panel after verifying. components and relationships Revert a package to DEV status Display information about Change Man Exit Change Man Press ENTER to process.1.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. Introduction 26 . the Primary Option Menu panel will then appear: ========= == == ======= == == ===== ====== =========== == == ========= == == == ======= ======= == == == == == == == == == == == ======== ========= == == == == ==== ======= == ======== ========= == == == == ==== ======= == == == == == == == == == == == ========== == == == == == ==== ========= ======== ========= == == == == == === ======= ========= ==== ==== ======= == == ============ ========= == == == == == == == == == == == == == == ========= == == == == == == ========= == == == == == == == == == == == == == == == == == ==== == == == == == === Date : Time : Version : 1998/12/11 12:14 4. The options displayed on the Primary Option Menu are built based upon the authorization of your User ID. Once the initiation is complete.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. Interfacing directly to your security system for access. 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. Accessing Change Man is usually accomplished by entering a CLIST in option 6 of TSO. Change Man provides the optimum amount of control without sacrificing performance. The started task architecture provides a single point of control and secure access to your production and development libraries. enter END command to exit.CHANGE MAN 4.6 The Software Change Manager SERENA Software International CMN@PRIM--------.

See the below for all descriptions and details 27 Introduction .) Change Man Users who are developers or approvers will most likely not have any of the additional options listed above. 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. Most of the functions that they will use will be accessed from the Build Option menu.User Training Guide what Change Man functions you have access to. From the Primary Option Menu. 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. option 1 from on the Primary Option Menu.

To return to a previous menu or panel.1 OPTION => =1. the Build Options menu will be displayed.User Training Guide Change Man Panel and Menu Navigation Using Panel by Panel Navigation In the Option line. will usually switch to the Package List option.6. if you typed a ‘1’ (for Build) in the Option line on the Primary Option Menu and then pressed Enter. then press Enter. if you typed: COMMAND => +1. However. type the number or letter that designates the function you want to perform. will switch to the direct access method for navigation or the Package List option. Use the panel by panel navigation method to learn what and where all the functions are in Change Man. usually PF3.6.2 OPTION => =1. most users after they become more familiar with the product. To return to a previous menu or panel.1 COMMAND => =1. Using Direct Access Navigation In the Option or Command field.) between each command. type a sequence of numbers or letters with a plus sign (+) or an equal sign (=) preceding the string and place a period (. Change Man will display the panel of the last character in the direct access stacked commands. For example. See the Package List section in this manual for all descriptions and details. Introduction 28 .2 COMMAND => =1. type ‘END’ in the Option or Command field on any panel or press the appropriate PF key command.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. type END in the option or command field on any panel or press the appropriate PF key command. For example. 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). This method of panel navigation is very fast as the user can do all their work from the Package List panel. Press Enter and Change Man will execute the request. Once the users become more familiar with the product. usually PF3.1 Or COMMAND => +1.

and it must be requested by pressing PF1. Using Selection Lists Change Man has many types of panels. CMNCCMSL FROM JCL/LVL(0) . 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 ---------------. The message appears on the third line of the panel.ZERO. the tutorial option will appear for the function or panel you are on.WSER200. You often access a selection list from a main panel field to help you identify available items. that usually advises the user how to resolve the error. the long message is much more helpful because it provides additional information. To exit and return to previous panel press PF3. one of which is a selection list.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.BASE.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 . A selection list is a panel that has a list from which you can select one or more items.User Training Guide Change Man Online Error Messages Change Man and ISPF handle online error messages similarly.CICS Maps _ PKG DB2 Bind Control Statements . such as a list of all possible library types. Information. the long error message does not display by default. See Tutorial section in this manual for all descriptions and details. left justified. Remember. Ordinarily. If you press PF1 a second time. To display the long (or secondary) error message. press PF1. A short error message is displayed by default in the upper right-hand corner of each panel.JCL ---------- ROW 1 TO 15 OF 15 29 Introduction .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 .

Press ENTER to execute the command.01 01.00 01. type the command letter and a component or package name in the panel.01 01. To use them. Type the following commands on the Command line and press ENTER: • • • • ‘REFRESH’ to Update the list.00 01. Packages and Components There are lists in Change Man that let you view contents of libraries.01 01.00 01.00 01.00 01. ‘H’ to display History for an item. For example. L xxxxxxxxx where xxxxxxxx is the component name. ‘CANCEL’ to Cancel the request. and press ENTER: • • • ‘B’ to Browse an item.01 01. Following are a set of standard commands used to work with these types of lists. a message normally appears in the status column to indicate your action (such as BROWSE for a browsed list item).00 05.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 INIT ===> ID PAGE 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. ‘S’ to Select an item for action. Type the following commands in the cursor field next to the component.00 01. Introduction 30 . packages and components.User Training Guide COMMAND NAME ===>STATUS _ $$$INDEX _ #ACF2 _ #NDM _ A _ ACKLA S AFRICAD _ AFRICAU _ ALLOCBAS _ AMBLIST _ ARCHIVE1 _ ASMDB2SQ _ ASSEMBLE _ A2VECFG _ BACKUP _ BAYD VV. ‘SORT’ to Sort the list. After executing one of these commands. To exit and return to previous panel press PF3.00 01. (Only valid for member and procedure/language displays) ‘L’ to Locate an item in the list.MM 01. Working with Lists of Libraries.00 01.01 06.

If it is a read-only field the label is followed by a colon. If you type an incorrect command or character in a panel. Using Patterns The system often encourages you to input a pattern to get a range of values in a list from Change Man. the arrow symbol still appears. For example. Closing Panels 31 Introduction . Use the UP and DOWN keys (normally PF7 and PF8 keys. To move forward or backward a specific number of lines. Using the combination of a command character and a PF key. Alternatively. A ‘?’ can replace any single character in a string. However. you can also immediately move the maximum number of lines to the top or bottom of a panel or dataset/member. 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. and BROWSE ONLY appears in the upper right hand corner of your screen. There are also visual symbols that follow the field label. If the field is followed by " = = > " the screen expects you to provide data in that field. By typing ‘m’ on the Command line and using the PF7 key. If you have a monochrome screen the intensity of the read only fields differs from the intensity of the data entry fields. For example: LIB TYPE ==>_ indicates a data entry field. the color/hue of the field is the read only color. or the PF8 key to go backward that number of lines. but you are currently prohibited from updating them. lists that you build or access through Change Man are too long to view on the screen. PACKAGE STATUS: DEV is a read only field. Change Man displays the correct available commands from that panel.User Training Guide Not all commands are available from all lists. 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. Scrolling through Lists Often. If the fields are normally data entry fields. If you have color monitors the fields have different colors. respectively) on your keyboard to scroll up and down through the lists. you move backward (toward the top of the data). you can use ‘m’ + PF8 for moving forward (toward the bottom of the data). type a number and use the PF7 key to go forward that number of lines.

you close panels by pressing Enter to process your changes.User Training Guide In general. and then typing ‘End’ and pressing Enter (normally. the panel you are viewing always tells you how to abandon your changes. In general. Other panels require you to type ‘CANCEL’ in the Command line and press Enter. 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. the PF3 key). Introduction 32 .

components and relationships Revert a package to DEV status Display information about Change Man Exit Change Man Press ENTER to process. 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--------. 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. enter END command to exit. 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.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. you will exit the Change Man subsystem and be returned to TSO 33 Primary Option Menu + Build Options .S PRIMARY OPTION MENU --------. The Primary Options Menu is the first panel the user sees when they sign onto the system. Promote and Approve.1.CHANGE MAN 4.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. Their primary function enables the user to access all the Change Man functions. 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. 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.

Discontinue the use of "paper" form SEC00010. will be displayed in the upper right-hand corner of the Primary Option Menu whenever this file is updated. Department number is now required when creating a new change package. New library types have been added to perform automatic JOBSCANs. 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. The following panel with JOB card will be displayed: CMNNOT00 ----------.OUTLIST . 2. Enter your Cost Center number in this field.GLOBAL NOTIFICATION REPORT DISPOSITION ------------------ Primary Option Menu + Build Options 34 .WSER24. APPLICATION GENL 07/05/1998 1. 2.T1447172. Audit level has been changed to 4. you will have the option of printing the Global Notification File. unless you view the Notification File. "NOTIFICATION UPDATED". Any other informational messages. APPLICATION ADMINISTRATION MESSAGE APPLICATION PAYR 07/05/1998 1. This notification message will reappear every time you sign onto Change Man. If the Global Notification File is updated. Change Man will notify you.WSER24. A message. To view this file you use the Notify panel. All baseline libraries will be compressed on Sunday.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. To access this Panel: • Select option ‘N’ from the Primary Option Menu for Notify and press ENTER -BROWSE -.LINE 00000000 COL 001 080 COMMAND ===> SCROLL ===> PAGE ********************************* TOP OF DATA ******************************** GLOBAL ADMINISTRATION MESSAGE 07/01/1998 1. Security request forms have been added to Online Forms. Solutions to common problems.CMN94152.

REGION=4M. ===> // TIME=2.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.T1551260.User Training Guide OPTION ===> OUTLIST DATASET : WSER92.WSER92.999).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 Primary Option Menu + Build Options .MSGCLASS=3.CMN98351.CLASS=E.WSER92.

Many user questions can be answered by viewing the tutorial information. Primary Option Menu + Build Options 36 .TUTORIAL COMMAND ===> More: + ----------------------------------| CHANGE MAN TUTORIAL | ----------------------------------This tutorial provides on-line information about Change Man features and operations. 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.Change Man Tutorial -------------------. 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. The table of contents contains a list of major topics.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. You may view the tutorial items by selecting an option and pressing ENTER. 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 ------------------.

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. 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 Primary Option Menu + Build Options . It will be displayed with the Change Package ID in the upper right-hand corner after a successful creation of a Change Package. edit. Enter END command to exit. To access this Panel: • Select option ‘1’ from the Primary Option Menu for Build and press ENTER CMNBUILD ----------------------. approve or review custom forms Rename and Scratch information Check out components from baseline or promotion Stage. update.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. The Build Options panel can also be displayed at the completion of the package create process. 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.

To set a particular day of the week. To prevent the scheduling of any planned changes for a given day. and decremented when change packages are deleted. enter SET(day) xxx (example: SETMON 123). Dates may also be set individually. leave the maximum at zero for that day.PLANNED INSTALLATION CALENDAR ------COMMAND ===> Press ENTER to update calendar or END command to exit. enter SETALL xxx on the Command line. rescheduled or installed. 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 Primary Option Menu + Build Options 38 . The maximums are initially set to zero for all dates. The calendar will be automatically incremented when change packages are created. To reset all to another number.Panel Use this panel to enter and update the maximum number of planned changes that can be scheduled for any given date.User Training Guide PLANNED INSTALLATION CALENDAR . To access this Panel: • Select option ‘1’ from the Primary Option Menu for Build. Information can be entered or updated for up to 52 weeks from the current date. 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 ----------.

Basically. you provide information about the change package to Change Man through a series of panels. Combined. there may be up to 8 different panels that you might see. This is where you create an entry in the Package Master with a change package ID number and some general housekeeping information. The panels you encounter during the Create process may vary.User Training Guide Create Create Overview The first process in the Change Man Life cycle is the create process. 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. Creating a change package involves describing the "outer structure" of a package. depending on the options you choose along the way. 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 .

Production (this is a remote site. or Development/Production Create 40 . you cannot install them into Production Libraries).User Training Guide No matter what options you plan to use for the new change package. participating. Development (change packages are distributed to remote sites. The panels which you encounter as you Create a change-package are governed by these factors: The package level: simple. no development is performed on this machine). or super/complex Your site configuration: All (you have no remote sites). you will always start the Create process with the ‘Create a New Package’ panel.

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)

Press ENTER to process; Enter END command to exit.

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

Enter the number of days you want the components within the Temporary Package to remain in the temporary library.User Training Guide Field TEMPORARY CHANGE Description This field is mandatory if the Change Package you are DURATION creating is a Temporary package. Change Man does the delete process at the same time to day as the install. Create 44 .m. then the delete will occur also at 02:00 p.m. Change Man will delete the components after the duration period has ended. Example if the install was at 2:00 p.

sometimes rely on this section to get a good picture of the change. It should be as complete and descriptive as possible. 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---------------.User Training Guide CREATE: PACKAGE DESCRIPTION . and other reviewers. This is because approvers. 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.CREATE: PACKAGE DESCRIPTION ----COMMAND ===> Press ENTER or END to continue or type CANCEL to exit. '''' '''' '''' '''' '''' '''' '''' '''' '''' '''' '''' '''' (minimum one line. the Create Change Package process is abandoned and Change Man returns you to the ‘Create a New package’ panel 45 Create .Panel This panel allows you to enter a description of the Change Package. press ENTER or PF3 key to continue to the next panel in the package create Enter ‘CANCEL’ in the Command line and press ENTER.

Repeat an existing line D .User Training Guide Field Description LCMD (first column) I . Keep in mind that some of the people that will be approving your package may not know too many details about it’s content. Create 46 .Delete a line Free form text area Description .Insert a new line R .you may use this area to enter any additional information about this change. This description panel can be used to inform these approvers of the specific package details.

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. Manual or Other) SCHEDULER '''' '''' '''' '''' '''' '''' '''' '''' '''' '''' '''' ===> CMN (minimum one line.User Training Guide CREATE: INSTALLATION 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) ROW 1 TO 12 OF 12 SCROLL ===> PAGE CMNCRT03------------. CONTINGENCY ===> 3 1-Hold production and contact analyst 2-Backout change. Individuals overseeing the installation can use these instructions.CREATE: INSTALLATION INSTRUCTIONS -COMMAND ===> Press ENTER or END to continue or type CANCEL to exit.Panel Use this panel to record instructions for the Installation of the change package. 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 . continue production 3-Other ===> Call Bob the Programmer (CMN. As well it will indicate an option for problem contingency instructions in case a production problem arises after the package has been installed.

Manual . continue production . Create 48 . ‘2’ . but are not limited to. ‘3’ .Insert a new line ‘R’ . CMN . SCHEDULER LCMD (first column) ‘I’ .Discontinue running the production jobs for your application until a supporting analyst can be reached for instructions.Back out of the change package and continue running your application's production jobs as normally scheduled.Specify scheduling instructions for change packages that use a job scheduler other than CMN and Manual. Other .Repeat an existing line ‘D’ .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’ .Use if 1 and 2 above do not apply.Change Man holds the installation until the date and time you specify on one of the Site Configuration panels.Hold production and contact analyst .Back out change.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. production job dependencies and change package Installation dependencies. Describe in this field some other action to be taken if there are problems in installing this change package.Other . This field has a maximum length of 44 characters.Change Man installs the change package as soon as the final approval is given.

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.User Training Guide CREATE: ON SITE INFORMATION . If your site is configured as a ‘D’ or ‘DP’ site. the create change package process is abandoned and Change Man returns you to the ‘Create a New package’ panel 49 Create . This panel is only displayed when your Change Man configuration is an ALL Site. 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. then the ‘Remote Site Information’ panel will be presented (see next section). press ENTER to complete the Package Create process Press PF3 or enter ‘CANCEL’ in the Command line and press ENTER.Panel Use this panel to inform Change Man of the change package installation date and time.

PRIMARY/BACKUP After you have filled in all the information on the panel and pressed ENTER. enter the date and time that the package is to be installed. return you to the BUILD OPTION panel. Create 50 .User Training Guide Field INSTALL DATE/TIME Description In this field. Finally Change Man updates the Planned Installation Calendar. Change Man will then create your change package. Specify the primary and backup contacts' phone numbers or extensions. and display the Change Package ID in the upper right hand corner of the panel. These people are notified if a problem arises during package implementation.

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) ROW 1 TO 12 OF 12 SCROLL ===> PAGE CMNCRT05 --------------. then you can use this panel to identify which applications they are.Panel This panel is only used in conjunction with participating packages.CREATE: AFFECTED APPLICATIONS ---COMMAND ===> Press ENTER to continue or type CANCEL to exit. then just press ENTER Press PF3 or enter ‘CANCEL’ in the Command line and press ENTER. If the participating package you are creating affects other applications.User Training Guide CREATE: AFFECTED APPLICATIONS . Change Man will then add to the approval list any approvers that differ from your regular application approver list. You only use this panel if indeed the participating package you are creating does affect other applications. Note: This panel does not have any required fields. the create change package process is abandoned and Change Man returns you to the ‘Create a New package’ panel 51 Create . If there are no relationships then just press ENTER to continue. 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.

Repeat an existing line ‘D’ .Delete a line Create 52 . 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. If you enter a value in this field. LCMD (first column) ‘I’ .Insert a new line ‘R’ .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.

then just press ENTER. '''' '''' '''' '''' '''' '''' '''' '''' '''' '''' '''' '''' 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.Panel This panel is used to record the participating packages that are associated to this complex / super package. just press ENTER to continue. Change Man will return you to the Create A New Package panel and display the package ID in the upper right-hand corner. CMNCRT08-----------. 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. if there are no participating packages. Once you create the participating packages then you can use the Update Package Information panel to update this list. the create change package process is abandoned and Change Man returns you to the ‘Create a New package’ panel Description Field 53 Create . • Press PF3 or enter ‘CANCEL’ in the Command line and press ENTER. Note: This panel does not have any required fields.User Training Guide CREATE: COMPLEX / SUPER INFORMATION . You can create the complex / super package with no participating packages.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.

LCMD (first column) ‘I’ .Repeat an existing line ‘D’ .Insert a new line ‘R’ .Delete a line Create 54 . Note: The order that the participating packages are entered represents the order references will be resolved during the compile and link processes.User Training Guide PACKAGE ID Enter the participating packages associated to this complex / super package.

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

Create 56 . and keep the change for three days.User Training Guide Exercises for Create Exercise #1: Create a simple planned permanent Change Package to update payroll. Exercise #2: Create a simple unplanned temporary Change Package that is to contain an emergency change to a payroll source component. Exercise #3: Create two (2) participating planned permanent Change Package with a complex parent linking the two new participating packages. It is to be installed one week from today's date. after payroll CICS is brought down. Install it immediately after final approval.

User Training Guide Update Update Overview After creating a change package you may wish to update some of the information associated with it. UPDATE: PACKAGE INFORMATION – Panel To access this panel: • Select option ‘1’ from the Primary Option Menu for Build. Enter END command to exit. you can update option 7. If you have selectively unfrozen the general category. if you have selectively Unfrozen the onsite category.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 Press ENTER to process. so check that the package ID displayed is the Change Package you want to work with. UPDATE: CONTROL INFORMATION – Panel 57 Update . press the ENTER key press PF3 or enter ‘END’ in the Command line and press ENTER. You can browse the information if the package is in Frozen (FRZ) status. you can update options I through 6. then Select option ‘2’ on the Build Options Menu for Update CMNPGNL0 ---------------. 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. To exit this panel you can: • • Enter the update option you want to perform ‘1 – 9’. Change Man returns you to the panel you came from Note: The PACKAGE ID is updateable. Also.

4-Participating) PLANNED PERM (* for list) (In days) STATUS: DEV STATUS: INSTALL DATE: 19981230 Press ENTER to process. enter END command to exit.User Training Guide This panel displays the change package control information. 2-Complex.UPDATE: PACKAGE DESCRIPTION ------.Panel This panel displays the package description information. You can update the description area. CMNPGNL1 ---------------. UPDATE: PACKAGE DESCRIPTION .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.ROW 1 TO 1 OF 1 COMMAND ===> SCROLL ===> PAGE Press ENTER to process. You can update any of the highlighted fields. PACKAGE ID: TEST000066 STATUS: DEV INSTALL DATE: 19981230 (minimum one line. CMNPGNL2 ---------------. which was entered when the package was created. which was entered when the package was created. 3-Super. maximum 46 lines) '''' Payroll month end install________________________________________________ '''' Add in a very detailed description of the change package_________________ ******************************* Bottom of data ******************************* Update 58 . enter END command to exit.

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

Panel Use this panel to display and update the list of individual application change packages that make up this complex or super change package.UPDATE: AFFECTED APPLICATIONS ---COMMAND ===> Press ENTER to process.User Training Guide UPDATE: AFFECTED APPLICATIONS . 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 .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.Panel Use this panel to select the application mnemonics that may be affected by the installation of this change package. Use the 'REFRESH' command to re-display blank lines for entering package ID's. CMNPGNL5---------------. CMNCRT08-----------. PACKAGE ID '''' '''' '''' '''' '''' '''' '''' '''' '''' TEST000012 TEST000045 TEST000077 __________ __________ __________ __________ __________ __________ ******************************* Bottom of data ***************************** Update 60 .

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 . enter END command to exit. CMNONSTE-----------------.UPDATE: SITE INFORMATION -------------------------COMMAND ===> Press ENTER to process.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.

User Training Guide THIS PAGE LEFT BLANK Update 62 .

Process scratch or rename requests in package Press ENTER to process. These requests can be the only items in a change package or can be part of a change package with Staged components. then Select option ‘4’ on the Build Options Menu for Utility CMNUTL00-------------. UTILITY: RENAME / SCRATCH OPTIONS – Panel Use this panel to direct Change Man to where you would like to rename or scratch the components. Change Man will return you to the previous panel Field Description 63 Utility . Enter END command to exit. 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.User Training Guide Utility Utility Overview The Utility Request facility is designed to Rename or Scratch (delete) components in production and/or Baseline Libraries. Change Man processes these requests after installing and rippling staged component versions. To access this Panel: • Select option ‘1’ from the Primary Option Menu for Build.Select baseline components to scratch or rename .UTILITY: RENAME/SCRATCH OPTIONS ----------------------OPTION ===> _ PACKAGE ID ===> TEST000057 1 2 Baseline Package . either a Baseline library or a change package. Change Man during Package production Installation and Baseline Ripple will process these utility requests.

To access this Panel: • Select option ‘1’ from the Utility: Rename / Scratch Options panel CMNUTL01----------------.User Training Guide OPTION ‘1’ .Panel Use this panel to set up utility requests for the members of your application's baseline libraries.Scratch a component blank . Enter END command to exit. Change Man will return you to the previous panel Utility 64 .Short History Press ENTER to process. Enter the Change Package ID.Component History I . ‘2’ .Locate component R .Browse component H . PACKAGE ID UTILITY: BASELINE SELECTIONS .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 . or double check the package ID displayed is still the package you want to work with.Rename component S .UTILITY: BASELINE SELECTIONS ----------------------OPTION ===> _ R .To select from components residing in the baseline libraries. (which mirrors the contents of your application's production libraries).To display utility requests in the change package.Scratch component B .Rename a component S . 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.

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 THIS PAGE LEFT BLANK Utility 68 .

If you checkout to a valid change package ID. rules. and Options The flexibility of Change Man enables your global and application administrators to configure the checkout function with various restrictions. Rules.User Training Guide Checkout Checkout Overview After you have created a change package.mm) is incremented. • • • • 69 Checkout . If Checkout is associated with a change package. and Options are as follows. to Change Man staging libraries or to the user's personal PDS. • Checkout can be restricted or denied for components that are already contained in a change package. depending on the needs of your site. Thus an existing package number must be entered during the Checkout process to ensure that all components checked out are accounted for. Change Man will sent concurrent development notification messages to all parties concerned. the component name is added to the package's component list. Checkout can include components that reside in promotion libraries (if any exist for a given application). until the component is either Staged or deleted from the package component list. disallowing Checkout of a component that is part of a package in motion unless it is an unplanned change. Some of these Restrictions. Restrictions. then each component may be checked out to that package one time only. If another user checks out the same component into a different change package(s). Check with your administrator for the settings at your site. Checkout is restricted to those components associated with a change package. You can check out components by selecting them from a list of Baseline or Promotion Library components. When you checkout a component. the statistics are carried forward and the version number (the vv portion of vv. and options. you use Checkout to copy components from secured libraries. that is. Change Man will add the checkout information to the statistics that make up the component's history. Rules. such as baseline or promotion.

PACKAGE ID CHECKOUT . Enter the Change Package ID. Enter END command to exit. To access this Panel: • Select option ‘1’ from the Primary Option Menu for Build.Checkout from baseline or promotion libraries Package .Panel Checkout 70 . 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. or double check the package ID displayed is still the package you want to work with.To select from components residing in the baseline or promotion libraries ‘2’ . Change Man will return you to the previous panel Field OPTION Description 1’ . then Select option ‘5’ on the Build Options Menu for Checkout CMNMCKOT----------------------.To display components that are already defined to your Change Package through the copied forward package option.Checkout package components Press ENTER to process.CHECKOUT OPTIONS ----------------------------OPTION ===> _ PACKAGE ID ===> TEST000063 1 2 Base/Prom .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.

2-Batch) (Y/N) CHECK OUT TO ===> S PERSONAL LIBRARY ===> LIBRARY DSORG ===> CONFIRM REQUEST CHECKOUT MODE LOCK COMPONENT ===> YES ===> 1 ===> NO Press ENTER to process. * for all members) (Blank for list) (Applies to source code.CHECKOUT --------------------------------OPTION ===> _ L . Enter END command to exit. Change Man will return you to the previous panel Field Description 71 Checkout . * for list) (Baseline 0 to -n.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. LIB) (Y/N) (1-Online. Promotion +1 to +n) (S-Staging library. PDSE. 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. To access this Panel: • Select option ‘1’ from the Checkout Options panel CMNCKOT1--------------------------. P-Personal library) (Personal library: PDS.User Training Guide CHECKOUT is used to copy components from the Baseline or Promotion libraries into a staging library or personal library. SEQ. PAN.

To checkout the components to a personal development library. To checkout components from a promotion library. Enter the name of the language in which the source is written. The name of the component to be checked out. To checkout all the components enter ‘*’ (be careful). Enter the Change Package ID. PACKAGE ID COMPONENT NAME LIBRARY TYPE LANGUAGE SOURCE LIBRARY CHECK OUT TO PERSONAL LIBRARY Field Checkout Description 72 . -2).g. Enter the Library type of the library you want to perform the checkout operation to. To checkout the component to a Change Man staging library. enter an S. enter the version number (e. If you selected P and you leave this field blank. The old versions are baseline -1. -3. enter 0. CMN* or CMN?0000). -2. enter the level number (+1 . If you selected option P on the CHECK OUT TO field. which can be overridden. To checkout components from the most current (production) version. You must enter the Component Name. place the personal dataset name in this field. This means that Change Man keeps several backup versions of the component. If the component has been compiled by Change Man before.User Training Guide OPTION Enter ‘L’ to display a list of the promotion and baseline libraries where a component can be found.g. you may use wild cards in this field (e. Leave this field blank to select from available language names for a component that Change Man has no history for. Enter ‘?’ to specify the language of the designated procedure.+99). it will assume the last compiled language. or double check the package ID displayed is still the package you want to work with. Use the OPTION line to produce a list of libraries where the component exists. enter P. In order to mask the selection list. To checkout components from a previous version. When Change Man installs a change into baseline. If you leave this field blank. Library Type and leave the Source Library field blank. Change Man builds a sequential dataset as default. etc. This field is required for source (SRC) or like-source components. Change Man will display a list of possible library types to select from. it RIPPLES the baseline libraries. Note: If you access this panel through the List option the Package ID field is not updateable.

also since this field is stored in your ISPF profile. enter the library's dataset organization ‘PDS’ or ‘SEQ’. No other user can stage the component within this package. This means that only the userid that checked out the component can stage it (edit or update it).Will place a lock on the component within the package.User Training Guide LIBRARY DSORG If you selected option P on the CHECK OUT TO field. Rule. Specify whether to checkout online ‘1’ or in a batch job ’2’. you will continue to checkout with NO until you change it back to YES (be careful).6. CHECKOUT MODE LOCK COMPONENT NOTE: Batch checkout will not update the member's ISPF statistics. If a component is locked by another user you must go to the stage package driven list (1.2) to UNLOCK (UC) the component prior to checkout. NO . Batch checkout will also bypass the OVERLAY PRIOR STAGED MODULE Admin. 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. YES .Will bypass locking of the component. 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). 73 Checkout .

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. LCMD (first column) ‘S’ . CANCEL.Browse a component ‘D’ . or list the history of a component to be checked out. or LONG. Change Man will return you to the previous panel Field COMMAND SHORT. browse.Delete a component from the package ‘SL’ . LOCATE.Display Source to Load relationship (Source components only) Note: Enter 'LONG' at the Command line to display additional member information. SORT. Checkout 74 .User Training Guide CHECKOUT: PACKAGE COMPONENTS – Panel This function is used to checkout. and 'SHORT' to return to the original member list.Display component history ‘B’ . Typically this option is used for a change package that was created with the ‘Package To Copy Forward’ option. Description Valid commands are REFRESH.Select a component for checkout ‘H’ .

It still remains the responsibility of the individual developers to communicate amongst themselves regarding the resolutions of the various versions of the component.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.CBL. 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. Several different warning and confirmation panels will be displayed throughout the lifecycle of the package. PF3 still performs the checkout. and depending on the circumstances at the time a checkout is attempted.MM LAST ACTION 01. The panel also allows you to CANCEL the checkout operation. To CANCEL the checkout enter ‘CANCEL’ in the Command line and press ENTER. To continue the checkout just press ENTER. CMNCMPSW ------------------------. which you are checking out.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. In this way. An example of the MVSSEND messages is: CMN2445I-Checkout conflict.CMNEX001.00 2000/01/01 08:20 01.95/01/20@16:15-WSER18 Overlay Warning: This panel appears when you are about to overlay a component that is 75 Checkout . one or several of the following panels may be displayed: Confirm Checkout Request: This panel informs you that the component(s). exist in other packages.00 1997/11/10 10:32 02. This component is included in the following packages: PACKAGE ID TEST000018 TEST000017 TEST000002 STA DEV DEV DEV PROMOTION VV.Row 1 to 3 of 3 COMMAND ===> SCROLL ===> PAGE Press ENTER or END to process or enter CANCEL command to exit. During the checkout process.SRC ------------.FOR TEST000010. Change Man is constantly alerting the developers of what concurrent development is in the application.CMNEX001.

Checkout 76 . The panel shows the TSO ID of the person who last changed the component you are about to overlay. * * * ****************************************************************************** Confirm Delete Request: Any delete requests while in checkout option ‘2’ (Checkout package components).CHANGE MAN CHECKOUT WARNING -----------------------COMMAND ===> ****************************************************************************** * Checking out component CMNEX001 will overlay WSER18'S version. CMNSTG13 -----------------. CMNCKWTP ---------------.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.User Training Guide already in your package and does not match the version you are about to checkout. Press ENTER to complete the delete request. Enter END command to cancel request. Press PF3 or enter ‘CANCEL or ‘END’ in the Command line then press ENTER to cancel the delete request. * * * * INSTRUCTIONS: * * * * Press ENTER to check out this component * * Enter END command to cancel request. Change Man will present the Confirm Delete Request panel. This panel gives you the option of verifying the component name and reconsider your request.

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. from the ‘-1’ version of baseline and lock the component. then the next time you go to edit the component you will get a ‘COMPONENT OUT-OF-SYNCH’ message. Exercises for Checkout Exercise #1: Check out a JCL component to a Change Package. If you have no changes to make then Audit will catch the out-of-synch condition. If the first package installs to baseline. If however the component does change in the package you checked it out from. then there can be an OUT-OF-SYNCH situation. Answer. from ‘0’ current version of baseline. check it out to the staging library. 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. Exercise #4: Create a new Change Package with the ‘copy forward’ option. 77 Checkout . Exercise #2: Check out a source component to a Change Package. in online mode. I change the component and install to baseline. Exercise #3: Check out all the source component to a Change Package that start with ‘A*’. Then check out all the components from the copied forward package to this new package. check it out to the staging library. from the ‘0’ current version of baseline. Your changes will not be saved and you must checkout the component from baseline. You can use the package from exercise #1 as the copy forward package.User Training Guide Commonly Asked Questions Question.

User Training Guide THIS PAGE LEFT BLANK Checkout 78 .

they can only Checkout and Stage components that are associated with a change package. 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. Change Man will copy the component into a Change Man staging library. Stage Rule 2 . 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).Allows only users who have been defined (by the local administrator) to a special entity by their TSO ID can Stage new components. Stage or staging a component is where you will edit a component. Also in Stage you can introduce new components into your application. This effectively disables Development Driven Staging. Based on this language name. a language name was specified or assumed. only ones that already exist in your Baseline Library. If the component(s) were checked out to a personal library. 79 Stage . Otherwise. Stage Rule 3 .User Training Guide Stage Stage Overview Stage is where developers will spend most of their time in the Change Man lifecycle. Change Man submits the job to compile the component(s). if any source or like-source components were checked out. They will have chosen 1 of the following parameters: Stage Rule 1 .Does not allow you to Checkout and Stage new components.All users can Stage new components. compile and link edit a program. Your Change Man administrator can effect how the Stage process will work. During the checkout process. or change the status of other components like JCL.

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

2-Batch) (Y/N. the user would use the Stage from Development option. To access this Panel: • Select option ‘1’ from the Stage Options panel. Use this panel to specify the dataset name of where the new components are so that Change Man can perform the copy process. If not then the user can simply cancel it. Press PF3 or enter ‘END’ in the Option line and press ENTER. SEQ. Enter END command to exit. that in most cases do not exist in the baseline libraries. * for all members) OTHER PARTITIONED OR SEQUENTIAL DATASET: DATASET NAME ===> ‘dataset name(member)’ ORGANIZATION ===> (PDS. when Change Man will display the compile and link panel and the user can issue the compile and link if desired. PAN.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). the user has checked out a component without package association and decides to include the modification in an existing change package. OTH) LIBRARY TYPE LANGUAGE STAGE NAME CONFIRM REQUEST STAGE MODE SUPPRESS MESSAGES ===> ===> ===> ===> YES ===> 1 ===> YES (Blank for list) (Blank for list. In these two cases. To exit this panel you can: • • Enter the required fields and press ENTER to proceed to next panel.STAGE: FROM DEVELOPMENT -------------------------COMMAND ===> PACKAGE ID: TEST000074 ISPF LIBRARY: PROJECT ===> GROUP ===> TYPE ===> MEMBER ===> STATUS: DEV INSTALL DATE: 19981230 (Blank or pattern for list. or if the application's users are not required to Checkout to an existing package. applies to batch stage) Press ENTER to process. LIB. CMNSTG02 -----------------. or leave some of the fields blank and select from the resultant lists and press ENTER. Description Field 81 Stage . applies to source code) (Optional if organization not SEQ) (Y/N) (1-Foreground. If the component being staged is a source library type. Change Man will return you to the previous panel. The Stage from Development option enables the user to copy components into the change package.

Enter YES if you do not wish to receive any messages during batch staging. COBOL2).g. etc. For a PDS.). This field is most commonly used for datasets which have other than three qualifiers. Enter ‘1’ to stage online. This field is required for sequential datasets. Use this field to enter the dataset name that contains the components to be staged. Enter a name for the component in this field. Also specify YES if you want to be notified of any concurrent development prior to staging the component. Enter YES to be notified if the staged components are going to overlay existing copies of the same component(s) in the staging library.g. If you are copying all the components. If the component is SRC or like-source. the component name is the member name but you may change the component name by specifying a new name in this field. When a component is to be staged from a sequential dataset. JCL.User Training Guide ISPF LIBRARY Specify the dataset name the same way as it would be on the ISPF EDIT panel. SRC. A component in a sequential dataset has no component name. Enter the type of component to be staged (e. Leave the member name field blank for a list of the members within the dataset. it must be given a component name. Enter ‘2’ to stage in batch mode. or enter the exact component name. OTHER PARTITIONED or SEQUENTIAL LIBRARY TYPE LANGUAGE STAGE NAME CONFIRM REQUEST STAGE MODE SUPPRESS MESSAGES Stage 82 . append * to the dataset name. you must specify the language in which it was developed (e. only a dataset name.

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

The edit process on any component will create a Change Man temporary file. successfully compiled/linked (source). etc. The last request that was performed for the component. CHANGED PROCNAME The date and time that the component was last changed.: STAGE. ID REQUEST Additional Processing Depending on the processing you select on the component. other additional panels will be initiated. Change Man will also notify you of any concurrent development or if other packages contain the same component (see below). Once complete press PF3 to return and save the changes back to your change package. Change Man will then display a Comparison Report Distribution panel (see below) which enables you to print the comparison report. or copied successfully from a development library into the change package (development driven staging). EDIT. The most common process is an edit. Component stage requests also display a Confirm Stage Request panel (see below). This is a Change Man skeleton procedure. 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. i. The procedure that was used to compile/link the program.e. The TSO ID of the last user to modify the component. Stage 86 .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. then Change Man will automatically give you the option of doing a compile and link (see below). This temporary file is where you can make all your changes or enhancements. If the component you have changed is a source (SRC) type component. which you can edit. 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). ACTIVE The component has been edited (if it is non-source). During any processing on any component in the package.

----4----. ----------------------.++++6++++.----5----. 87 Stage .CMN97316.WSER18.----6----.U416ALL.----3----.++++1++++.CMN.++++2++++.TEST.++++7 * * Question: Can the requested package be updated by this user? * * Answer in R15(IXP$RC): 0=no change to current status. The second panel gives you the opportunity to print a hardcopy report of the edit changes. ++++++++|+++.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 (@).CMN973 *********************************************************************** * CHANGE MAN APPLICATION . The first panel shows what changes you have made in the current edit session.++++6++++.OUTLIST Line 00000000 Col 001 080 Command ===> Scroll ===> PAGE ********************************* Top of Data ********************************** S E R C M P A R (MVS-3. <=== CHANGE ACCORDINGLY_____ ===> // MSGCLASS=R <=== CHANGE ACCORDINGLY_____ Press ENTER or END to process Enter CANCEL command to exit without saving changes. --------|---.----1----.++++3++++.SRC(CMNEX001).1.++++2++++. <=== CHANGE ACCORDINGLY_____ ===> // NOTIFY=WSER18.----I * this exit controls who can update the package info.'CHANGE MAN'. SER71I .----2----.++++7 D * the exit controls who can update the package info.END OF TEXT ON FILE SYSUT2 This panel will be displayed automatically to prompt you for the disposition of the Comparison report.#000001.EXIT MODULE 001 * * Purpose: This exit is invoked when updating package information. Menu Utilities Compilers Help ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss BROWSE WSER18.++++1++++.T2147244.++++5++++.1997/213) SERSTAR6 WEDNESDAY NOV SYSUT1=WSER99.COMPARISON REPORT DISPOSITION -----------------------OPTION ===> REPORT DATASET NAME: REPORT DISPOSITION 'WSER18.++++5++++. * 4=set input to yes for update.1 .User Training Guide Comparison Report + Report Distribution The next two panels appear when you have edited your component in Stage.++++3++++.++++4++++.CMN97316.WSER18.T2147244.END OF TEXT ON FILE SYSUT1 SER72I .++++4++++. ++++++++|+++. <=== CHANGE ACCORDINGLY_____ ===> // CLASS=O.WSER18.SYSUT2=WSER18.

333). ? for designated procedure) (Y/N) (Y/N to display other options) JOB STATEMENT INFORMATION: ===> //WSER92I JOB (XXXX. The current Change Man status of the Change Package.REGION=4M. LIBRARY TYPE LANGUAGE DATASET NAME Stage 88 . the staged name is the "new name" of the component.#000074. The language name that was assigned to the component.Source Code ASM WSER200.NOTIFY=WSER92________________________________ ===> //*JOBPARM SYSAFF=ESA1__________________________________________________ ===> //*_____________________________________________________________________ Press ENTER to process.MSGCLASS=3.SRC ===> CMNASM ===> ===> ===> NO ===> YES (Blank for list. CMNSTG04 ---------------.User Training Guide STAGE: COMPILE AND LINK . The component that is being staged. This will either be a Change Man package staging library or a development library. If you are staging a component from a development library into Change Man and you are renaming the component.TRAIN.USER. The date that the Change Package is to be installed. The name of the dataset that contains the component that you are staging.CLASS=E. The type of component that you are staging. Enter END command to exit.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 .____________________ ===> // TIME=2.CMN. Field PACKAGE ID STATUS INSTALL DATE STAGED NAME Description The ID of the Change Package that you are working with.WSER92.Panel Use this panel to indicate how a source code module is to be compiled or compiled and link edited.

Enter "NO" if this program is not a DB2 program. This panel gets customized a great deal in most shops. etc. the link edit parms found in component history will be displayed.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. You may type in link edit parms for the program. 89 Stage . Press ENTER to continue. Enter END command to exit. If this program was previously compiled within Change Man. Specifying 'Y' will cause the user option to be expanded within the procedure. The User Option function is used to incorporate up to twenty additional user options within a Change Man compiling procedure. You may type in compile parms for the program. this field will be in "browse only" mode. 'N' or BLANK will cause the user option to be suppressed. COMPILE PARMS LINKAGE EDIT PARMS DB2 PRE-COMPILE Enter "YES" if this program is a DB2 program. OTHER OPTIONS Enter "YES" if you need to display additional user options such as CICS pre-compile. the compile parms found in component history will be displayed. If only one procedure is available for this language. CMNUSR01 ------------------.User Training Guide Field COMPILING PROCEDURE Description The Change Man compiling procedure that will be used to compile/link the program. If this program was previously linked within Change Man. Your Global Change Man Administrator will define available options for you. The variables are passed to the file tailored skeleton. EZTRIEVE.

When using LCT processing you must specify a name card in each member. ENTRY statements.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 Press ENTER to process. CONFIRM DELETE REQUEST This panel allows for the confirmation of the action chosen for this component (i. Enter END command to cancel request. This listing may be viewed on-line or printed. This IDR record also contains the program ID and the Change Package ID that this module was updated in. etc. Change Man dynamically constructs the linkage edit name card to be the same name as the source. If LCT processing is not required.e.) CMNSTG13 -----------------. Valid responses are. Change Man uses SET SSI (an IBM time stamp) to update the IDR record and link the source and load to ensure integrity.User Training Guide Additional Compile and Link Processing Once the compile has completed. During the link process Change Man inserts information into the Load module created. specifically the IDR record. Stage 90 . Change Man can automatically populate a “compressed listing” library (LST) to contain the output from the compilation. This name card will control the name of the resultant load module. Change Man's LCT processing provides the developer with the ability to specify linkage edit control parameters such as INCLUDEs for specific subroutines. and a name card. press the ENTER key to confirm the request. delete. or enter PF3 or enter ‘CANCEL’ in the Command field to cancel the request. restage an ACTIVE component.

User Training Guide CONFIRM STAGE REQUEST This panel allows for the confirmation of the action chosen for this component (i. CMNCMPSW -----------------------.00 1998/12/04 09:31 WSER92 USER000074 DEV 02. Enter END command to cancel request.) CMNSTG13 -----------------.MM LAST ACTION SIZE PROCNAME ID USER000075 DEV 02.00 1998/12/03 17:08 24 WSER200 ****************************** Bottom of data ******************************* ROW 1 TO 3 OF 3 SCROLL ===> PAGE 91 Stage . This is to notify you that there may be concurrent development within the application.CLOOB.00 1998/12/04 08:30 24 WSER92 USER000063 DEV 02. This component is included in the following packages: PACKAGE ID STA PROMOTION VV. Concurrent Development panel This panel will appear every time you make a change to a component that exists in another package.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 Press ENTER to process. etc. restage an ACTIVE component.e.SRC ---------------COMMAND ===> Press ENTER or END to process or enter CANCEL command to exit. delete.

Press PF3 or enter ‘END’ or ‘CANCEL’ in the Command line and press ENTER. 3-Checkout. Enter END command to exit. 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. changed from date. Stage 92 . Change Man will return you to the previous panel. L-Long) (Y/N) (Y/N.User Training Guide COMPONENT LIST PARAMETERS – Panel This panel is used to filter the stage package driven list that is displayed to the user. To access this Panel: • Select option ‘3’ from the Stage Options panel and press ENTER. To exit this panel you can: • • Enter a Component line command and press ENTER to proceed to next panel. 4-Inactive) (YYYYMMDD) (YYYYMMDD) S YES YES YES (S-Short. applies to edit in stage) Press ENTER to process. component status. applies to batch stage) (Y/N. component type language. CMNSTG12 ----------------. The list can be filtered down by component name.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. compile procedure and TSO-ID. 2-Incomplete. The date that the Change Package is to be installed. changed to date.

User Training Guide Field STAGED NAME Description The component that is being staged. Enter a range of dates to view a list of all components that have been changed within a specified period. enter Yes or No. enter the name of the component to be listed. Enter YES if you do not wish to receive any messages during batch staging. enter COBOL2 to view a list of all components written in COBOL2. Enter the type of the components to be displayed. To display all components that belong to a specific userid. For example. To be notified if the staging will overlay an existing component. If you are staging a component from a development library into Change Man and you are renaming the component. For example. the staged name is the "new name" of the component. The display will be immediately followed by a screen offering print options. Enter the language for components to be displayed. enter the userid in this field. enter JCL to list all JCL components. Indicate whether you want to display the comparison report. If known. The long method displays the name of the dataset from which the component was checked in or checked out to. Enter the status of components to be displayed. This field also controls whether a compare listing is produced when performing an edit during staging. Select from the short or long method. Enter the compiling procedure for the components to be displayed. 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 .

Stage 94 . The Stage Confirm Request option can be set on either of the following panels: Stage: From Development (CMNSTG02) . even for the Stage: (package) Components panel where there is no opportunity to set the Confirm Request option. it is easy to make a keying error and enter ‘D’ instead of ‘S’ beside a component in a component list. The Confirm Request option will be set to NO for all stage operations and panels no matter where it was entered. However. If the Stage Confirm Request Option is set to NO to suppress these panels. Option 1. Developers are sometimes impatient with the edit compare display and the Comparison Report Distribution 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. other important warnings may be missed. If Stage Confirm Request is set to NO. it has a broader effect than might be expected. depending on circumstances at the time a stage or some other action is attempted from a stage panel.6. Option 1. For example. one or several of the following panels may be displayed.3 If the Stage Confirm Request is set to YES. 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.6. you will immediately delete the component instead of opening it for edit.1 Component List Parameters (CMNSTG12).User Training Guide Stage CONFIRM REQUEST Field The Confirm Request option on stage panels appears to offer some processing efficiencies.

Note: Observe how the status of the component changes. Exercise #2: Checkout a source program from baseline into the package from exercise #1. Again watch how the component’s status changes. Then Stage the component using Stage Option ‘Package’. Use the Stage Option ‘Dev’ to stage the new component into your change package. you can set the Comparison Report filed to ‘NO’. 95 Stage . Then Stage the source using Stage Option ‘Package’.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). Edit the component and reply to the displayed panels. Edit the source component and issue the compile and link. Exercises For Staging Exercise #1: Create a new change package and checkout a JCL component into the package from baseline. 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. Answer.

User Training Guide THIS PAGE LEFT BLANK Stage 96 .

Change Man will return you to the previous panel. The Browse Compressed Listing facility is used to decompress these listing into a temporary file for viewing and or printing. Change Man has a facility which allows you to store the output from the compile/link edit procedures within the library type ‘LST’. Non-blank: staging/baseline listings. Change Man stored these listings in a compressed format. As the typical compile/link edit listing is very large.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. A listing can be narrowed down by application. This eliminates the need to keep printed copies of the listings. The disposition of the decompressed listing is specified by the user. package ID and/or date. Blank: staging listings only) (Blank or pattern for list) (Blank for list) (YYYYMMDD) (YYYYMMDD) (Y/N) PROMPT FOR LISTING DISPOSITION ===> NO Press ENTER to process.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. To exit this panel you can: • • Enter the required fields and press ENTER to proceed to next panel. then Select option ‘L’ on the Build Options Menu for Listing. Enter END command to exit.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. Press PF3 or enter ‘END’ in the Option line and press ENTER. BROWSE COMPRESSED LISTINGS . 97 Listing . CMNBLST0 ----------------.

Note: If the Application Field is entered than the Package ID field is ignored. 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. Specify the application if you also wish to display the baseline versions of the compressed listings.00 1995/11/28 1995/11/28 15:31 355 355 SERSTAR S PROGC BASE-00 01. which satisfy the fields entered on the previous panel.BROWSE COMPRESSED LISTINGS ------.02 1996/07/29 1996/07/29 15:11 482 1133 SERSTAR _ PROGA BASE-01 01.ROW 1 TO 7 OF 7 COMMAND ===> SCROLL ===> PAGE Press END command to exit.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. CMNBLST1-----------------. The components.00 1996/01/31 1996/01/31 14:14 16 16 SERSTAR _ PROGCKL BASE-00 01. will be displayed on the following panel.MM CREATED CHANGED SIZE INIT ID _ PROGA STAGING 01. Enter a date in YYYYMMDD format to limit the selection list to only include listings generated prior to that date.02 1995/01/11 1995/01/11 14:43 335 335 SERSTAR _ PROGD BASE-00 01.02 1997/07/29 1997/07/29 15:11 500 1133 SERSTAR _ PROGA BASE-00 01. PACKAGE ID: TEST000074 STATUS: DEV INSTALL DATE: 19981230 NAME LEVEL VV. Enter a date in YYYYMMDD format to limit the selection list to only include listings generated from that date through the current date. 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. Enter YES.02 1995/01/11 1995/01/11 14:47 407 407 SERSTAR _ PROGC2 BASE-00 01. The default is NO.00 1995/10/12 1995/10/12 13:45 338 338 SERSTAR _ PROGC1 BASE-00 01.00 1995/11/29 1995/11/29 12:47 418 418 SERSTAR ****************************** Bottom of data ******************************** To exit this panel you can: Listing 98 . The default is LST.

STAGING contains the copy that resides in your change package. VV. BASE-00 contains current production. Field NAME LEVEL Description The name of the component that was compiled/link edited. The library that contains the compressed listing. This is the information gathered from PDS stats. Press PF3 or enter ‘END’ or ‘CANCEL’ in the Command line and press ENTER.MM CREATED/CHANGED/ SIZE/INIT ID This is the Change Man Started Task ID 99 Listing . etc.User Training Guide • • Enter ‘S’ beside the program you would like Change Man to display the decompressed compile/link edit listing. This is a Change Man tracking version number. then press ENTER to display next panel. BASE-01 contains the prior version. Change Man will return you to the previous panel.

CMN1400I . Therefore the listing will be displayed and explained in sections.SYSPRINT * ****************************************************************************** CMNWRITE (MVS-4. detects and optionally expands COPY members and variations of INCLUDES.BASE0.COPYLIB SYSIN: TYP=SCP/WSER99.1.COPYLIB SYSIN: TYP=CPY/WSER23.COPYLIB SYSIN: CMP=CMNEX001.LINE 00000000 COL 001 080 COMMAND ===> SCROLL ===> PAGE ******************************** TOP OF DATA ********************************* ****************************************************************************** * DDNAME: WRITE. Section 1 Prior to any pre-compiler or compiler step.CMNO. CMNWRITE scans your source code.T1438303. This dataset is shown at the top of the panel. Change Man executes program CMNWRITE. Due to the size of the compressed listing (131 bytes wide).Attempting to initiate dialog with started task. 1997 14:24:21 PARM='SUBSYS=0' PARM interpretation: Change Man subsystem '0' Expansion of uncovered COPY/Include variations SYSIN: TYP:CPY/WSER23.PROMO1.WSER24.SRC SYSIN: LNG=ASM SYSIN: PKG=TEST000237 CMN7500I . Change Man retrieves the component and expands the listing into a temporary ISPF dataset. Nesting of COPYBOOKs and INCLUDEs is supported up to 99 levels.CMNO. The libraries and the order are based on the configuration that has been built by your Change Man Administrator. -BROWSE .COPYLIB SYSIN: TYP=MPC/WSER23. Listing 100 .User Training Guide Compile/Link Edit Listing When you select a compressed listing for Browse. Change Man parses your source code for COPY/INCLUDE statements and will search the library concatenation for those members.CMNO. we are unable to display the entire listing on one panel.Session established with Change Man started task.OUTLIST -.6) 03/29/94 09 WEDNESDAY JUNE 1.CMN94152.BASE0.WSER24.SER410. The first section of the listing shows the search order that Change Man has built for your SYSLIB concatenation.

101 Listing . were found by Change Man.BASE0.WSER24M.01 92/02/29 1994/02/08 07:31 489 488 WSER34 WSER23.T142411.VV. The LV field shows the level of the included members.CMNO.CMNO 02 CPY$ACPM 01.CMN94152.CMNO.Component CPYEXITS is a called copybook.CMNO.WSER24.MM -CREATE.Component CPY$ACPM is a nested copybook which is a copybook that is called by another copybook.COPYLIB (SCP) PDS/WSER23.LINE 00000000 COL 001 080 COMMAND ===> SCROLL ===> PAGE Library search order: PDS/SYS94152.BASE0.User Training Guide -BROWSE .COPYLIB (CPY) PDS/WSER23.RA000.PROMO1.COPYLIB (MPC) LV -MEMBER--.SER410. Level 02 .NULLPDS PDS/WSER23.Component CPYUCADS is a called copybook. that built the object module.01 92/01/10 1994/02/08 07:31 21 21 WSER34 WSER23.L I B R A R C O M P O N E N T D 00 CMNEX001 15. Section 2 (columns 1 .CMNO CMN1410I .01 92/01/10 1994/02/08 07:32 133 133 WSER34 WSER23.SIZE INIT -USERID.COPYLIB (CPY) PDS/WSER23.OUTLIST -.01 92/03/04 1994/06/01 14:22 64 68 WSER24 WSER99.-LAST CHANGED.WSER24. This section also shows the developer where all of the components. Level 01 .CMNO 01 CPYEXITS 03.Component CMNEX001 is the calling source component in the change package.TECH 01 CPYUCADS 01.Session terminated with Change Man started task. Level 01 . In the above example these levels are as follows: Level 00 .80) The second section of the listing displays the libraries that Change Man searched to find the COPY/INCLUDE members.T1438303.

WSER24. Section 2 (columns 53 .User Training Guide -BROWSE .---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.SERENA.CMNO.BASE0. compiler and link edit output from your compile.CMN94152.TECH.CMNO.COPYLIB 3655E2F4-00006C3C 133 WSER34 WSER23.BASE0. This section also shows the internal Change Man generated fingerprint for each component.COPYLIB 34B40005-00000474 d task.WSER24.CMNO.SRC CC1F2D61-00000E04 488 WSER34 WSER23.#000001.L I B R A R Y N A M E---------------------. The remainder of the listing contains the precompiler.T1438303.COPYLIB 79135A46-00001DC6 21 WSER34 WSER23. Listing 102 .LINE 00000000 COL 001 080 COMMAND ===> SCROLL ===> PAGE (CPY) (CPY) (SCP) (MPC) INIT -USERID.132) Columns 53 .BASE0. This fingerprint is written into the Change Man package master file and is verified during the Audit process.OUTLIST -.132 of the listing display the libraries where Change Man found the included members.

This Audit rule can be set between 0 – 5. If any of the components are SRC or CPY type components. Meaning the version in your package is no longer the most current. Its function is to inspect the contents of the Package Staging libraries of an evolving Change Package with respect to Baseline libraries. 103 Audit . If you modify a component in your package. Example. then Audit must be run prior to the Freeze process. then the out-of-synch conditions. the more severe out-of-synch conditions that were found. The higher the return code. which is set by the Administrator. Audit rules 1 – 5 indicate which Audit return code is acceptable in order to pass Audit. then it can not be frozen. and you must run another Audit. A return code of 4 means that some out-of-synch conditions were found. The report also provides current and historical information on each component in your package. This return code indicates of what type of out-of-synch condition was found in your package. which lists all the occurrences of out-of-synch conditions. Small Change Packages probably only need 1 or 2 audits. which caused the return code of 8. Return codes of 8. If the return code was 8. meaning you are not required to run Audit. Note: If your package does not pass Audit. or 20 usually means the user must correct the out-of-synch conditions before the package can be frozen. Audit has an Audit rule. must be corrected in order to pass Audit. Audit jobs also end with a return code. or a package containing a LOD component that does not match its SRC component. The audit job is typically run after all the components have been checked out and ALL modifications have been completed. then their related compiles and links should also be done. It produces an Audit Report. but they are usually only informational. These situations are called out-of-synch conditions. 12. then the Audit return code must be 4 or less to pass the Audit process. then Audit is totally optional. If the Audit Rule has been set to 0.User Training Guide Audit Audit Overview The Audit function or process plays a very important part in the life cycle of a Change Package. then the last Audit return code is no longer valid. if the Audit rule is set to 4. 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. See ‘The Audit Job’ for more detailed information on the Audit return code. The Audit process runs as a batch job on the MVS system. or parameter. Audit may be run at anytime during the package life cycle. This information can be used to resolve out-of-synch conditions easily. while larger Change Packages may run audits daily. Audit provides Change Man the ability to help you detect code that is inconsistent with your development procedures. If the Audit rule has been set between 1 – 5.

Running a Full Audit on this type of package may take a considerable amount of run time. they are. run the Staging Libraries Only Audit to report on any out-of-synch conditions within your package Audit 104 . Therefore. When you run a Full Audit on a participating package in a complex/super package. A Full Audit also updates the audit return code in your package. the number of baseline libraries in your application. before you run a Full Audit. Audit will notify you of out-of-synch conditions across the entire complex/super package. near the end of the package’s development life cycle. This Impact Analysis table is typically a DB2 table and it holds all component relationships. and if the package is associated with a complex/super package. Therefore it might be best to run a Full Audit. • Staging Libraries Only (Audit Lite) Audit Lite ONLY checks for relationships within the package’s own staging libraries. the number of relationships between these two. 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. on this type of package. • • • • • 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. The types of relationships within the Impact Analysis table 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. Depending on how many components you have in your package. This type of Audit is very useful for a package that has many component relationships within it’s own staging libraries and the baseline libraries.User Training Guide The way Audit knows about all component relationships because it reads the Impact Analysis table. a Full Audit may run for a significant amount of time.

you can then run the Full Audit.MSGCLASS=3.CLASS=E.333).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.WSER92. and not for any other participating packages in the complex/super package. Audit catches out-of-synch conditions only for that package. AUDIT CHANGE PACKAGE . then Select option ‘7’ on the Build Options Menu for Audit. CMNAUDIT -------------------.Panel This panel enables you to specify what type of Audit job you want Change Man to submit on your Change Package.REGION=4M. Change Man will return you to the previous panel. Press PF3 or enter ‘END’ in the Command line and press ENTER. SYNCH5!. To exit this panel you can: • • Enter the desired audit fields and press ENTER.____________________ ===> // TIME=2. Change Man will submit the audit job and usually return to the Build Options Menu. Once these conditions have been resolved. and SYNCH10! When you run a Staging Library Only Audit on a participating package. Field Description 105 Audit . To access this Panel: • Select option ‘1’ from the Primary Option Menu for Build. in a complex/super package. namely DUPLIC!.User Training Guide staging libraries first.NOTIFY=WSER92________________________________ ===> //*JOBPARM SYSAFF=ESA1__________________________________________________ ===> //*_____________________________________________________________________ Press ENTER to process. 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. SYNCH8!. Enter END command to exit. Audit Lite does not report on out-of-synch conditions that reference baseline.

If the Audit Rule is set to anything other than 0. It is recommended that you first submit the Audit job with this field set to ‘NO’. Enter ‘YES’ if you want audit to automatically resolve certain out-of-synch conditions by submitting API jobs. SYNCH4!. or enter ‘NO’ to run a Full Audit against the staging and baseline libraries. SYNCH9!. SYNCH8!. or double check the package ID displayed is still the package you want to run the Audit on. AUDIT STAGING LIBRARIES ONLY AUTO RESOLVE OF OUT-OF-SYNCHS CROSS APPLICATION AUDIT Audit 106 . Enter 'YES' to instruct Change Man to perform a cross application Audit for CPY/SRC relationships across "other" applications. a full Audit is required before you can freeze the package. 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’. and SYNCH15! Corrected out-of-synch conditions will be displayed in the audit report. Enter ‘YES’ if you want to check for out-of-synch conditions in just the Staging libraries (Audit Lite). SYNCH5!. This applies to SIMPLE packages only. Change Man automatically resolves the following out-of-synchs: SYNCH2!. SYNCH7!.User Training Guide PACKAGE ID Enter the Change Package ID.

SYNCH10!. These out-of-synch conditions are SYNCH2!.36. No user action is required. User action required prior to freezing the package. 12 . SYNCH4!. SYNCH7!. This return code indicates what type of out-of-synch conditions were found in your package. Typically no user action is required. SYNCH13!. SYNCH11!. relationships between package CPY and LOD components to the baseline libraries.indicates that some out-of-synch conditions were found and that they will need to be reviewed and typically MUST be corrected.indicates that many of the above out-of-synch conditions were found and that they need to be reviewed and typically MUST be corrected. 08 – indicates that some out-of-synch conditions were found and that they will need to be reviewed and possibly corrected. The return codes are. SYNCH12!. • • 107 Audit . SYNCH6!. 04 – indicates that some out-of-synch conditions were found but they are very minor and are usually informational. SYNCH15! and SYNCH16! User action required prior to freezing the package.User Training Guide The Audit Job After Change Man has submitted the audit job. • • • 00 – means there were no out-of-synch conditions found in your package and that everything is clean. SYNCH14!. Typically user action is required prior to freezing the package. 20 . These out-of-synch conditions are SYNCH5! and SYNCH8!. CN(INT ERNAL) 14. SYNCH9!. 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.26 JOB03782 $HASP165 WSER92L ENDED AT HOGNJE CN(INTERNAL) *** This notification message informs you what return code your audit job ended with.

00 1996/01/26 1996/10/28 14:35 0008 0008 USER02 SYNCH12! CMNOFM CMNZDRV 01. Any out-of-synch ‘FLAGS’ are displayed in the center of these side-by-side reports.User Training Guide The Audit Report The Audit job produces an Audit Report. Flasher. The first set contains each component in the Baseline and Staging libraries side-by-side with their corresponding PDF statistics.S t a g i n g ----------------------* ******** ************************************************************* tso-id Name VV. SRC. 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 . The report name in the DDNAME list is called ‘AUDITRPT’. etc. The Audit job processes each library type (CPY.) in the Change Package sorted by library types.80 (4. IOF. DOC.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 .MM Created Changed Size Init Tso-id Name +________ _____ __________ ________________ ____ ____ ________ ________ CMNCCASM 01. JCL.B a s e l i n e ---------------------* *------************************************************************* ******** Name VV. LOD.00 1996/01/26 1996/10/28 14:35 0135 0135 USER01 CMNCCASM CMNOFM 01. 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 ******************************************************************************* *--------------------. you will find a ‘Legend and Summary Report’. After the final 2 sets of reports. It contains a list of all the out-of-synch conditions and shows how many occurrences of these conditions were found in your package. LCT.1997/273) Audit WEDNESDAY DECEMBER 30.MM Created Changed Size Init Tso-id Audit 108 .6 . for the last library type. The second report displays the historical information for the staged like source components for the same library type. The Audit report then displays 2 sets of reports for each library type in your package.1. etc.). This report can be viewed by your shop’s spool display system (SDSF.(SRC) * ******************************************************************************* -------* *---------------------.Example of the 2 sets of Reports by Library Type columns 1 .

Audit is recommended but entirely optional -Out-of-synch messages (hint . CMN7540I . Recommendation Summary Report Listed below are some solutions to resolving out of synch situations that can be flagged within this audit report. They are very similar to ISPF browse or edit headings Audit Report . SYNCH0! (Unknown to Change Man) Cycle component through Change Man.05 02.User Training Guide ________ ________ USER01 CMNCCASM USER02 SYNCH12! CMNOFM USER33 CMNZDRV CMNZFRM _____ 01.08 02.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 .End of job.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.01 01. RC = 12 ******************************** BOTTOM OF DATA ***************************** 109 Audit . Any out-of-synch ‘Flags’ will be listed in the center of these reports (see SYNCH12!). the component has not been included in the change package. Many of the report statistics are the ISPF/PDF statistics in the PDS directory. Check if component resides in another participating package excluded SYNCH12! (Orphan module in staging) Manually delete component from staging. If a component is listed only on the Staging side. the component is new (has never been processed by Change Man).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.PACKAGE TEST000013 PASSED THE AUDIT WITH A RETURN CODE OF 12. 0 .

User Training Guide Audit 110 .

A SYNCH3 will occur.User Training Guide Out-of-synch Conditions The following is a list of out-of-synch conditions that the AUDIT job reports on. Suggested Resolution: Recompile the component using the Designated Procedure.0 Change Man could not find the history (statistics) for the component.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.4 There is no difference between the staging and baseline versions of this component. Suggested Resolution: No action required. This includes components. 111 Audit . which just shows that a relationship exists. SYNCH2! Compile/Designated Proc differ Return Code .0 Shows that there is a copybook within a copybook (an embedded copybook). indicated how severe each out-of-synch condition is.0 This synch will appear on a load module that Change Man cannot parse. It has never been updated by Change Man. SYNCH0! Unknown to Change Man Return Code . This is an informational out-of-synch. Suggested Resolution: Recompile the staging version of the source. Suggested Resolution: Delete the duplicate component from the Change Package. unknown to Change Man. that are copied by another component.12 A source or like-source component was compiled without using the designated compiling procedure. The return code listed. If the IDRDATA records are unparsable. Suggested Resolution: No action required. Suggested Resolution: No action required. !COPY Embedded copybooks Return Code . SYNCH1! PDF statistics not available Return Code . Suggested Resolution: No action required. SYNCH4! CPY problem in staging Return Code . SYNCH3! Unparsable load module Return Code .0 Change Man could not find the PDF statistics for the component. It is also used to generate the return code of the Audit job. DUPLIC! Staging duplicates baseline Return Code .

or when a compile fails. Suggested Resolution: Recompile the baseline version of the source. SYNCH6! Activity file not checked out The activity file does not exist. Suggested Resolution: Stage the source component again. Return Code .12 Suggested Resolution: Checkout the component again or stage in a new activity file if this is a new component.User Training Guide SYNCH5! CPY problem in baseline Return Code . and retrofit changes. Suggested Resolution: Verify the changes to the component and stage again.12 A staging version of the subroutine was linked after the staging version of the calling load module(s).12 The baseline version of this component has a more recent activation date than the staging version.12 Component does not have a matching source and load.12 This synch appears when an unknown component is found in the staging library. SYNCH8! Called subroutine in baseline Return Code . Suggested Resolution: Relink the baseline version of the calling load. SYNCH11! Hashing discrepancy Return Code . SYNCH7! Called subroutine in staging Return Code . Suggested Resolution: Delete the component from the staging library. Audit 112 .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. SYNCH12! Orphan component Return Code .12 The hashing calculation during the Audit of the component differs from the calculation created during staging. Suggested Resolution: Checkout component again. SYNCH10! Version regression problem Return Code . SYNCH9! Source and load discrepancy Return Code . It occurs when a component has been copied into the staging library outside of Change Man. Suggested Resolution: Relink the staging version of the calling load.8 A staging version of a subroutine has a more recent activation date than the baseline version of the calling load.

or restage the component. Suggested Resolution: Stage the component or delete it from the package.12 A baseline.User Training Guide SYNCH13! Baseline/Staging discrepancy Return Code . Suggested Resolution: Recompile the staging version of the source.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. SYNCH15! Source to relationship problem Return Code . a SYNCH14 will occur.8 The baseline version of the recompiled or relinked component has a more recent change package. or other otherwise accessible LCT.12 If any component is not in ACTIVE status when the audit is run. Suggested Resolution: Recompile or relink the module from the Baseline library. SYNCH 16! CPY low-date problem in baseline Return Code . Suggested Resolution: Checkout the component from baseline and retrofit the changes. 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. SYNCH14! Components not in ACTIVE status Return Code . 113 Audit .

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.User Training Guide Commonly Asked Questions Question. but you Stage the component (meaning you run a compile/link) and it’s status changes to ACTIVE. Can I run an audit on a complex/super package? No. If I run a Full Audit on my participating package. A Audit Lite will not review the other participating packages and only check it’s own package staging libraries. will Audit flag this component? YES! Audit will flag the SRC component as a DUPLIC! Answer. Answer. Question. does Audit review the other participating packages associated in the complex/super package? Yes. If you checkout a SRC component and make NO change to the component. Answer. even the SETSSI date will be different. will the audit job raise any flag? NO! The new load module will have a different date and time stamp. Question. Question. a Full Audit will check for any out-of-synch conditions across all the other participating packages within the complex/super package. 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. Audit 114 . Answer. Change Man will issue an error message “Invalid Package Level – Package level must be simple or participating”. Answer.

User Training Guide Exercises for Audit Exercise #1: Run a ‘Staging Libraries Only’ Audit on any Change Package. Review the Audit Report. then go into Stage and modify the copybook. Review the Audit Report and resolve the out-of-synch conditions. The report should show a SYNCH5! 115 Audit . 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 #4: Checkout a copybook used by some SRC program in the baseline library. then run Audit. Exercise #3: Run a ‘Full’ Audit on a Change Package that does not have ALL the components in ACTIVE status.

User Training Guide THIS PAGE LEFT BLANK Audit 116 .

After the freeze process. To access this Panel: • Select option ‘2’ from the Primary Option Menu for Freeze and press ENTER. You can also use the Unfreeze function to ‘unlock’ specific package categories so they can be modified. Change Man will not allow the Change Package to be frozen. you freeze it. Change Man checks for two things: • • That all components in the package are in ACTIVE status. Freeze the package by submitting a batch job. During the freeze process. These options are. and makes it available for approval. locks out further modification. tested.User Training Guide Freeze Freeze Overview Once a Change Package has been built. This process puts the package in frozen ‘FRZ’ status. 117 Freeze . Selectively unfreeze or Refreeze specific package categories and components. FREEZE OPTIONS – Panel Use this panel to select the freeze option you want to execute. the Change Package can still be "unlocked" and moved back to development ‘DEV’ status with the use of the Revert function. • • • • Freeze the package online. and audited. Reset the Freeze in Progress indicator. 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.

When the Freeze job is submitted it sets a flag that indicates the Change Package is frozen. The Global and Application Administrators enable this function.Freeze Package Online. ‘2’ .g. Field OPTION Description Enter the freeze options you want to execute and press ENTER. To exit this panel you can: • • Enter the freeze option you want to execute and press ENTER.Reset. The default is ‘NO’. Change Man will return you to the previous panel.Freeze Package in Batch. ‘3’ . Press PF3 or enter ‘END’ in the Option line and press ENTER. This option allows you to unfreeze/refreeze selective components that require modification without reverting the Change Package back to development.User Training Guide CMNFRZ01-----------------------. ‘4’ . Enter ‘YES’ if you would like Change Man to immediately promote your Change Package upon a successful completion of the freeze process. ‘1’ . If something happens during the freeze job (e. select this option to reset this flag. the freeze job is canceled).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 Press ENTER to process. PACKAGE ID AUTOMATIC PROMOTION AFTER FREEZE Field Freeze Description 118 .Selective. Enter END command to exit. Enter the Change Package ID or double check the package ID displayed is still the package you want to work with.

please wait Date: 1998/12/22 Time: 13:40 ========================================================================== | The Freeze function is performing the following task: | | Constructing the package execution JCL. then it changes the status of ALL package components to FROZEN status. Creates the ‘. Your screen is locked . Notifies the package approvers of the change in status by sending them a message. | | Freezing all the package components. or in batch. If yes. typically an MVSSEND message. Change Man will present the following screen to inform you the progress of the freeze process. Changes the Change Package status from ‘DEV’ to ‘FRZ’. Change Man is doing the following: • • • • Checks to make sure ALL the components in your Change Package are in ACTIVE status. The Freeze Wait Panel When you select freeze option 1 (Freeze Package Online). | | Notifying package approvers | ========================================================================== While this wait panel is displayed.X’ package staging library that contains the installation and backout batch jobs. Enter ‘O’ for online or ‘B’ to submit a batch job. 119 Freeze .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.

Freeze all components within this package category. 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. You can only unfreeze Package categories that are in FROZEN status.ROW 1 TO 6 OF 6 COMMAND ===> SCROLL ===> PAGE LINE CMDS: F-Freeze all. a selection list will be presented and you can selectively unfreeze or refreeze specific components from the list.User Training Guide UNFREEZE / REFREEZE Package – Panel Use this panel to selectively unfreeze or refreeze specific Change Package categories. Press PF3 or enter ‘END’ or ‘CANCEL’ in the Command line and press ENTER. Field Freeze Description 120 . Change Man will return you to the previous panel. After the package category has been unfrozen. Once the modifications are completed.Unfreeze all components within this package category.Where applicable. then you can use the refreeze function to refreeze the package category.UNFREEZE/REFREEZE TEST000074 ----. Meaning you can now made modifications to these components. ‘S’ . so that you can use the Stage process to make the appropriate component changes. Enter ‘F’ to refreeze the component. Field LCMD (first column) Description ‘F’ . CMNUNFRZ-----------------. ‘U’ . then select option ‘3’ from the Freeze Options panel and press ENTER. U-Unfreeze all. but the individual components in that category are marked unfrozen. the Package Status will still remain frozen ‘FRZ’. To access this Panel: • Select option ‘2’ from the Primary Option Menu for Freeze. enter ‘U’ to unfreeze the component.

go back and view the status of each component in your package. The function last selected (*Freeze. 121 Freeze . or *Selective). Once complete. Exercises for Freeze Exercise #1: Freeze a Change Package using the online process. specifically the ‘. *Unfreeze. Review the package staging libraries. Also notice the package status. The package category's current status as of the last REFRESH.X’ file.User Training Guide PACKAGE CATEGORY STATUS FUNCTION The package category for which an action is to be performed.

User Training Guide THIS PAGE LEFT BLANK Freeze 122 .

User Training Guide Promote Promote/Demote Overview Promotion is the process of moving changes through specific environments for various test requirements. and Acceptance testing. such as Unit. which you use to change or confirm the package ID shown is the package you want to promote or demote. CMNPRM00 ------------------. Change Man Administrators determine the promotion/demotion mode (online or batch). Promotion of DB2 or CICS components must be in batch for BINDS and NEWCOPY. If there are matches then Change Man will inform you of the potential overlay. and review the status and historical information for a specific Change Package. Change Man also checks the test environment for components that match the components being promoted. When a component is promoted to a new level. Demotion is the process of deleting components from these environments. You will first be presented with the following panel.PROMOTE CHANGE PACKAGE -------------------------COMMAND ===> PACKAGE ID ===> TEST000074 Press ENTER to process. The testing environments are application specific libraries and/or common libraries shared by multiple applications. and the actual library names. To access this Panel: • Select option ‘3’ from the Primary Option Menu for Promote and press ENTER. Enter END command to exit. PROMOTE CHANGE PACKAGE – Panel Use this panel to display and select the options available within promotion/demotion. usually because errors have been found during testing. System. 123 Promote . the previous level's libraries are cleaned up. The Change Man Administrators define the library types that may be promoted. and the promotion/demotion rule which defines the steps that must be taken within the Change Package Life Cycle.

ACTION REQUESTED Enter the required action you want to perform. MAXIMUM PROMOTION LEVEL Informs you what the last promotion available promotion level is. ‘P’ . Enter ‘B’ if you want the promotion to execute as a batch job. Press PF3 or enter ‘END’ in the Command line and press ENTER.0 MAXIMUM PROMOTION LEVEL: PROMO2 . Change Man will return you to the previous panel.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. 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.Promote package will copy the package component to a promotion level.Demote package will delete the package component from a promotion level.2 ACTION REQUESTED ONLINE OR BATCH LEVEL TO CHECK ===> _ ===> O ===> 1 (P-Promote.ROW 1 TO 2 OF 2 COMMAND ===> SCROLL ===> PAGE PACKAGE ID: TEST000074 CREATOR: WSER92 STATUS: DEV INSTALL DATE: 19981230 CURRENT PROMOTION LEVEL: STAGING . If Change Man needs to perform a BIND for DB2 components or a NEWCOPY for CICS components. ‘D’ .User Training Guide CMNPRM01 ------------------. Field CURRENT PROMOTION LEVEL Description Informs you where the package was fully promoted last. ‘C’ . ONLINE OR BATCH Field Description Promote 124 . Enter ‘O’ if you wish to promote in online mode. you must submit the promotion as a batch job. D-Demote.PROMOTE CHANGE PACKAGE --------. C-Check for overlay) (O-Online.

User Training Guide LEVEL TO CHECK This field is required if the ACTION REQUESTED was specified as C.REGION=4M.2 STATUS: FRZ INSTALL DATE: 19981230 NEXT PROMOTION LEVEL ===> 1 JOB STATEMENT INFORMATION: ===> //WSER92N JOB (XXXX. It dictates the level for which Change Man is to check components This field displays information regarding promotion Historical Information history. Enter END command to exit.Full promotion of the entire package to another promotion level S . CMNPRM02 --------------------. the date and time that the action took place.Selective promotion of components to another promotion level PACKAGE ID: TEST000074 CURRENT PROMOTION LEVEL: MAXIMUM PROMOTION LEVEL: CREATOR: WSER92 STAGING .WSER92. It displays the action taken. or to selectively promote members that have previously been selectively demoted.0 PROMO2 . To exit this panel you can: • • Enter the requested action and press ENTER.PROMOTE OPTIONS ------------------------------OPTION ===> F .MSGCLASS=3. promotion level. and the TSOID of the user who issued the promote/demote request. Change Man will return you to the previous panel. Press PF3 or enter ‘END’ in the Option line and press ENTER. 125 Promote .374).NOTIFY=WSER92________________________________ ===> //*JOBPARM SYSAFF=ESA1__________________________________________________ ===> //*_____________________________________________________________________ Press ENTER to process. nickname.____________________ ===> // TIME=2. PROMOTION/DEMOTION PROMOTE OPTIONS -Panel Use this panel to promote the entire change package.CLASS=E. To access this Panel: • This panel appears automatically after you enter ‘P’ on the ‘Promote Change Package’ panel.

this field is required.Full Promotion.NOTIFY=WSER92________________________________ ===> //*JOBPARM SYSAFF=ESA1__________________________________________________ ===> //*_____________________________________________________________________ Press ENTER to process.User Training Guide Field OPTION Description ‘F’ . select the active components to be promoted. Change Man will display a package component list.CLASS=E. To access this Panel: • This panel appears automatically after you enter ‘D’ on the ‘Promote Change Package’ panel.WSER92. 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.____________________ ===> // TIME=2. From this list. If selective promotion is chosen.DEMOTE OPTIONS ------------------------------OPTION ===> _ F .MSGCLASS=3. Enter the Job card to be used for the promotion batch job.Selective Promotion.Full demotion of the entire package to level 0 (Staging) S .1 MAXIMUM PROMOTION LEVEL: PROMO2 .374). Promote 126 . Enter END command to exit. You will only see the jobcard display if you select option B on the previous panel. ‘S’ . 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. Will promote all the active components of the Change Package to the level indicated in the NEXT PROMOTION LEVEL field.REGION=4M.2 DEMOTE FROM LEVEL ===> 1 JOB STATEMENT INFORMATION: ===> //WSER92Q JOB (X170.Selective demotion of components to level 0 (Staging) PACKAGE ID: TEST000074 CREATOR: WSER92 STATUS: FRZ INSTALL DATE: 19981230 CURRENT PROMOTION LEVEL: PROMO1 . CMNPRM04 ---------------------.

User Training Guide To exit this panel you can: • • Enter the requested action and press ENTER. then you will overlay these common components with the ones in your package. 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. Note: Always check with the owner of the other package if it’s ok to overlay their component. Field OPTION Description ‘F’ .COMMON COMPONENTS -----------. Enter the Job card to be used for the promotion batch job. Change Man will display a package component list. CMNPRM08 --------------------. This indicates that all components of the Change Package are to be demoted from the level indicated in the DEMOTE FROM LEVEL field. Change Man will return you to the previous panel. this field is required. PACKAGE ID: TEST000093 CREATOR: WSER92 STATUS: DEV INSTALL DATE: 19981230 CURRENT PROMOTION LEVEL: STAGING . If selective demotion is chosen. This field allows you to specify to which promotion level you want to promote the change package to. select the components to be demoted.Full Demotion. To cancel the promotion press PF3 or enter ‘END’ or ‘CANCEL’ in the Command line and press ENTER. If you press ENTER. ‘S’ . From this list.OVERLAY WARNING COMMAND ===> SCROLL ===> PAGE Press ENTER to process or enter END to exit.Selective Demotion. If promotion is to take place in batch.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 .0 MAXIMUM PROMOTION LEVEL: PROMO2 . Press PF3 or enter ‘END’ in the Option line and press ENTER. You will only see the jobcard display if you select option B on the previous panel.

Promote 128 . Then do a Full Promote to the first available promotion level. Use the Selective demotion. Now Demote 1 of the programs. Do the promote in online mode. make another change to the program (in Stage) and finally do a Selective promote of the program back to the first promotion level. make a change to both source programs and complete the compile and link process.User Training Guide Exercises for Promote/Demote Exercise #1: Create a Change Package with a SRC program. Exercise #3: Create a Change Package with 2 SRC programs. Then do a Full Promote to the first available promotion level. make a change to the source program and complete the compile and link process. Exercise #2: Use the same package as in exercise #1 to demote the same source program from the first promotion level. Then do another Full Promote to the next promotion level.

APPROVE PACKAGE PARAMETERS . To access this Panel: • Select option ‘4’ from the Primary Option Menu for Approve and press ENTER. Once a Package is frozen. 4-Participating) (Planned or Unplanned) (Permanent or Temporary) (YYYYMMDD) (YYYYMMDD) (YYYYMMDD) (YYYYMMDD) (Y/N) Press ENTER to process.User Training Guide Approve Approve Overview The Approval function is a very important process in the Change Package Life Cycle. This section details what must be done in order to approve or reject a Change Package. the install process will start. Approval is where your package is checked or reviewed for the last time prior to bring installed into production.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. Also the Package status changes from ‘FRZ’ to ‘APR’ (approved). 3-Super. Once the final approver approves your package. There may be several approvers required to review and approve your package. CMNAPPRV ----------------. To exit this panel you can: 129 Approve . blank for list) (Approvals for this security entity) (Packages for which user was notified) (1-Simple. 2-Complex. designated approvers may be notified via TSO (or another notification vehicle) that a Change Package is awaiting approval.Panel This panel is used as selection criteria to display the specific Change Package(s) that you would like to approve or reject. Enter END command to exit.

Press PF3 or enter ‘END’ in the Command line and press ENTER. Enter a remote site to display Change Packages hat affect that remote site. or enter blanks and work with the selection lists. Enter a YES if you wish to limit the display further by specifying component types. Enter Work Request ID to display Packages with that ID. 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 . Description The ID of the Change Package to be approved or rejected. Change Man will return you to the previous panel. Enter a Package Time Span to display Change Packages with that Package Time Span. Leave this field blank to view a list of all Change Packages awaiting your approval. 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.User Training Guide • • Enter the required fields and press ENTER. Enter a Package Type to display Change Packages with that Package Type. Enter a Package Level to display Change Packages with that Package Level. Enter a Department to display Change Packages assigned to that department. 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.

To access this Panel: • This panel will appear automatically after the ‘Approval Package Parameters’ or the ‘Approve Package List’ Panels. 131 Approve . The following panel is an example of this. Enter END command to exit. APPROVE/REJECT OPTIONS . CMNAPPL1 -------------------. CMNAPPOP ------------------.APPROVE PACKAGE LIST ---------. To exit this panel you can: • • Enter the requested action in the Option line and press ENTER. Change Man will return you to the previous panel.User Training Guide The results of the Approve Package Parameters might generate more than 1 Change Package.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. Press PF3 or enter ‘END’ in the Option line and press ENTER.Panel You use this panel to direct Change Man as to which approval process you want to perform.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 Press ENTER to process.

This option displays the Approval List panel that allows you to approve or reject the Change Package.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 . If the Change Package has been rejected by any approver. To access this Panel: • Enter option ‘3’ from the ‘Approve/Reject Options’ panel and press ENTER.QUERY. ROW 1 TO 18 OF 19 SCROLL ===> PAGE CMNQRY03 --------------. 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. ‘4’ . PACKAGE INFORMATION CATEGORIES .User Training Guide Field OPTION Description ‘1’ . This option allows you to reset the progress indicator. ‘3’ .REASONS. This option allows you to review the contents of the Change Package.APPROVE. use this option to display the reasons that it was rejected. ‘2’ .Panel The approvers can use this panel to gather Change Package information prior to approval.RESET.

To access this Panel: • Select option ‘1’ from the ‘Approve/Reject Options’ panel and press ENTER. Field LCMD (first column) Description ‘S’ – Enter S beside package category you want to view. or to indicate that you're in the process of reviewing the Change Package.User Training Guide To exit this panel you can: • • Enter the requested action and press ENTER. Field Description 133 Approve .APPROVAL LIST -------------.ROW 1 TO 2 OF 2 COMMAND ===> SCROLL ===> PAGE Press ENTER to process. but have not yet reached an approve/reject decision. Change Man will return you to the previous panel. Press PF3 or enter ‘END’ or ‘CANCEL’ in the Command line and press ENTER. Change Man will return you to the previous panel. CMNAPPLS ----------------------. Press PF3 or enter ‘END’ or ‘CANCEL’ in the Command line and press ENTER.Project Leader 001 _ Approver #2 . enter END command to exit. 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.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. PACKAGE ID: TEST000074 APPROVER DESCRIPTION _ Approver #1 .

If the Scheduler selected was ‘Manual’ then the Package will be installed right after the last approver has approved the package.USER000095 BASELINE RIPPLED 1999/01/06 @ 10:20:36.APPROVE. Once the final step of the install has occurred Change Man will notify you by sending the following message: CMN405I . CN(INTERNAL) *** Once you see this message the Package has been installed into production and the Baseline Ripple process has completed. The order in which approvals are to be made.g. If the scheduler was ‘CMN’ then the package will be installed at the specified date and time. The Package status has also changed from ‘APR’ to ‘BAS’ (Baselined). Indicates to the person who submitted the package for approval that you are still viewing it. Shows the status of the approval request for each approver. Will approve the Change Package. ‘C’ . REJECT REASONS . APPROVER DESCRIPTION A short description of each level of approval. To access this Panel: • Select option ‘2’ from the ‘Approve/Reject Options’ panel and press ENTER. ‘V’ – VIEWING. reject) Once the last approver approves the Package the Package is ready for the installation process.REJECT. Will reject the Change Package. Approve 134 . (e. approved.Displays a panel on which you can write notes about the package.User Training Guide LCMD (first column) ‘A’ . The date and time the approval or rejection was given.Panel Use this panel to enter the reasons why you rejected the Change Package. ‘R’ . ID DATE/TIME SEQ STATUS The specific TSO userid of the approver.

Field Free form text area Description Enter the reason why the Package is being rejected. Press PF3 or enter ‘END’ in the Command line and press ENTER. 135 Approve . To exit this panel you can: • • Enter the free form text and press ENTER. Change Man will return you to the previous panel.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.

You must enter a reject reason.User Training Guide Exercises for Approval Exercise #1: Use the defined Approval Process to approve a Change Package awaiting your approval. Exercise #2: Use the defined Approval Process to reject a Change Package that is awaiting your approval. Approve 136 . Notice the change in package status. Notice the change in package status.

A major benefit of the List function is that it provides all the Change Man functions to be accessed from one central location. In the List function you can list all the Change Packages in the system.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. From these resultant package lists. they usually switch from the menu driven navigation method to the List function method. like: • • • • • • • • • Updating package information Audit Freeze Approval Revert Checkout Stage Promote / Demote etc. The List function provides an alternative way of navigating throughout the Change Man system or selecting functions to be processed. or you can specify "search" criteria that allows you to list only those Change Packages that meet the search criteria. you can perform almost any Change Man function you want. Once most users become familiar with the Change Man functions and processes. 137 List .

INS. TCC or DEL) (1-Simple. REJ. 4-Participating) (Planned or Unplanned) (Permanent or Temporary) (YYYYMMDD) (YYYYMMDD) (YYYYMMDD) (YYYYMMDD) (Y/N) Press ENTER to process. Change Man will return you to the previous panel. 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. FRZ. CLO. You can enter several search criteria in any of the other fields to further narrow down the resultant package list. Example.User Training Guide PACKAGE LIST PARAMETERS .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. Press PF3 or enter ‘END’ or ‘CANCEL’ in the Command line and press ENTER. or '*' for all packages) (DEV. You will be presented with a list of every package in that application. BAK. OPN.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. You can also use wide cards in most of the input fields. 2-Complex. List 138 . CMNLIST0 ----------------. To exit this panel you can: • • Enter the search criteria and press ENTER. DIS. BAS. To access this Panel: • Select option ‘5’ from the Primary Option Menu for List and press ENTER. The most typical way to use this panel is to only enter the full Package ID in the Package ID field and press enter. blank for list. APR. Enter END command to exit. 3-Super.

enter the inclusive dates in the form of YYYYMMDD. Use this field to mask the list of Change Packages according to the entered package status. To view a list of Change Packages that are to be during a range of dates. Enter the type (planned or unplanned) of the Change Packages to be viewed. or participating) of the Change Packages to be viewed. Enter the department for the Change Packages to be viewed. DEPARTMENT PACKAGE LEVEL PACKAGE TYPE PACKAGE TIME SPAN FROM/TO INSTALL DATE installed FROM/TO CREATION DATE To view a list of Change Packages that were created between a range of dates. Enter ‘Y’ to view the panel with additional selection criteria. or leave this field blank to choose from the list of all applications. WORK REQUEST ID Enter the Work Request ID for the Change Packages to be viewed. Enter the time span (permanent or temporary) of the Change Packages to be viewed. OTHER PARAMETERS 139 List . Enter the TSO ID for the Change Packages to be PACKAGE STATUS CREATOR'S TSO ID viewed. complex. Enter the level (simple.User Training Guide Field PACKAGE ID Description Enter the Package ID or pattern. enter the inclusive dates in the form of YYYYMMDD. super.

This panel also provides informative details on each package being displayed. CMNLIST3 -------------------. Through the menu method you would select 1 for Build. Field List Description 140 . if you wanted to list all the components within a package. For example.Panel This panel displays the Change Packages that meet the selection criteria that were entered on the ‘Package List Parameters’ panel. and finally select 2 for Stage Package. To access this Panel: • Appears automatically after pressing enter from 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. the install date. then select 6 for Stage. 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. Change Man will return you to the previous panel.User Training Guide 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. promotion info and who created the package. Press PF3 or enter ‘END’ or ‘CANCEL’ in the Command line and press ENTER. the type of package. Information like Package Status (STA).CHANGE PACKAGE LIST --------.

place a single question mark ‘?’ or any invalid line command and press enter. complex. there is NO command to CREATE a new package. To display the line command list.User Training Guide Line Commands There are 38 different line commands available for this panel. permanent or temporary). You will be presented with the valid line commands you can use. PACKAGE ID STA INSTALL LEVEL TYPE WORK REQUEST DEPARTMENT PROMOTION AUD CREATOR Note: Of all the 38 possible Package Line commands. 141 List . The Change Package level (simple. The Change Package ID assigned by Change Man. The scheduled date of Change Package installation. The current status of the Change Package. The reason for this is how can you enter the create package command on a package that already exists. or participating). The TSO ID that created the Change Package. The Work Request ID assigned to the Change Package. The current level of promotion (if any). See next section for the list. The type and time span for the Change Package (planned or unplanned. However you still can perform the CREATE new package function by entering ‘CR’ on the Command line of this panel. The department assigned to the Change Package. The return code from the most recent Change Man Audit job for the Change Package. super. Once entered you will go directly to the ‘Create New Package’ panel.

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.PACKAGE LIST OPTIONS ------.Panel This panel displays the available commands that you can enter within Change Package List panel. CMNLIST5 -------------------.User Training Guide 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 .PACKAGE LIST OPTIONS -----. CMNLIST5 -------------------.

checkout a SRC component. 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. create a new package. Exercise #3: Using only the Package List feature. 143 List . display a list of all the Change Packages in an application that are in DEV status and that were created by your Userid. display a list of all the Change Packages in an application. edit/stage the component and run audit on this new package.User Training Guide Exercises for List Exercise #1: Using only the Package List feature. Exercise #2: Using only the Package List feature.

User Training Guide THIS PAGE LEFT BLANK List 144 .

The physical deletion only takes place when the REPORTS task is executed. This is a logical delete. Typically it runs in the middle of the night when Change Man is down. The first step is to mark the Change Package for deletion. DELETE OPTIONS – Panel Use this panel to select which Delete function you want to perform. This option can be used up until the time that the REPORTS job has run. Enter END command to exit. or flag the Package as ‘Memo Deleted’. The second step is the physical deletion of all the datasets associated with the Change Package. A Package to be deleted through this function must be in DEV status. Delete or Undelete. 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. The UNDELETE function is used to remove a change package from a MEMO DELETE status.Memo delete a change package Undelete .User Training Guide Delete Delete Overview The Delete function is used to delete Change Packages that are no longer required. which is accomplished by completing the Delete panel process (see below). and the deletion of all the records within the Change Man Package Master file. Check with your Change Man administrator to determine when package aging occurs against the package master. To access this Panel: • Select option ‘D’ from the Primary Option Menu for Delete and press ENTER CMNDELT0 ----------------------.DELETE OPTIONS -----------------------------OPTION ===> _ 1 2 Delete .Restore memo deleted change packages Press ENTER to process. The Delete function has 2 steps in its’ process. Change Man will return you to the previous panel 145 Delete . The REPORTS task is a Housekeeping job that is usually scheduled to run once a day.

CONFIRM REQUEST Delete 146 . Enter 'NO' if you are certain that the change package is to be deleted. This option informs Change Man you want to Memo Delete a Change Package. 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 ----------------.Delete. This option informs Change Man you want to Undelete a Memo Deleted Change Package(s).Undelete. ‘2’ . 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.User Training Guide Field OPTION Description ‘1’ . 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. Enter END command to exit.MEMO DELETE CHANGE PACKAGE -----------------------COMMAND ===> PACKAGE ID CONFIRM REQUEST ===> TEST000078 ===> YES (Y/N) Press ENTER to process. Enter 'YES' if you want Change Man to display a confirmation of the delete request prior to setting up the Memo Delete.

Enter END command to cancel delete request. This panel informs you that the Memo Delete request has been processed. The Package status also changes from “DEV’ to ‘DEL’.User Training Guide If you enter ‘YES’ for the Confirm Request field. then Change Man will display the following panel: CMNDELT1 ----------------. Enter END command to exit.PACKAGE MEMO DELETED COMMAND ===> PACKAGE ID CONFIRM REQUEST ===> TEST000078 ===> YES (Y/N) Press ENTER to process. which means the Change Package has been marked for deletion.MEMO DELETE CHANGE PACKAGE --.CONFIRM DELETE -----------------------------COMMAND ===> PACKAGE ID: TEST000078 STATUS: DEV INSTALL DATE: 19981230 Press ENTER to confirm delete request. 147 Delete . 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: CMNDELT2 ----------------------.

Delete 148 . 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.RESTORE MEMO DELETED PACKAGES ---------------------COMMAND ===> PACKAGE ID ===> TEST000078 (Blank for list) Press ENTER to process. 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. To access this Panel: • Select option ‘2’ from the Delete Options panel and press ENTER CMNDELT3 --------------. This will result in the following Package List panel: CMNDELT4 ----------------. enter a blank in this field.MEMO DELETED PACKAGE LIST -------. Note: To select from a list of Memo Deleted Change Packages. Enter END command to exit.User Training Guide RESTORE MEMO DELETED PACKAGES – Panel Use this panel to select which Change Package(s) you want to Memo Undelete.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.

RESTORE MEMO DELETED PACKAGES ----. This panel informs you that the Memo Undelete request has been processed. Enter END command to exit. then Change Man will display the following panel: CMNDELT3 --------------. 149 Delete .PACKAGE UNDELETED COMMAND ===> PACKAGE ID ===> TEST000078 (Blank for list) Press ENTER to process. The Change Package status is also changed from ‘DEL’ back to ‘DEV’.User Training Guide If you press ENTER to process the Memo Undelete request.

User Training Guide THIS PAGE LEFT BLANK Delete 150 .

151 Revert . REVERT CHANGE PACKAGE . These revert reasons are available for review using the Change Man Query function. The Revert function is used to accomplish this change. The user is required to enter a revert reason describing why the change package is being reverted. it is no longer available for any changes or modifications.Panel Use this panel to select the Change Package you need to Revert. 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. Once complete the entire Change Package is now available for any modifications. Enter END command to exit. It will change the Change Package status from ‘ BAK’.User Training Guide Revert Revert Overview After a Change Package has been Rejected. FRZ’. If the user needs to go back and make changes to this Package. ‘APR’ or ‘REJ’ to ‘DEV’ status. then the package status must be changed to ‘DEV’.REVERT CHANGE PACKAGE -------------------------COMMAND ===> PACKAGE ID ===> TEST000074 Press ENTER to process. To access this Panel: • Select option ‘R’ from the Primary Option Menu for Revert and press ENTER CMNREV00 ------------------. 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. or Frozen. Backed out.

enter END command to exit. Change Man will return you to the previous panel Field Free form text area Description Enter the revert reason in this area. 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. Revert 152 .Panel Use this panel to enter the reasons why you reverted the Change Package. ===> ===> ===> ===> ===> ===> ===> ===> Press ENTER to process. 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.User Training Guide REVERT REASONS.

REVERT CHANGE PACKAGE ---------.PACKAGE REVERTED COMMAND ===> PACKAGE ID ===> TEST000074 Press ENTER to process. The package status has also been changed from ‘FRZ’. ‘APR’. This panel informs you that the Revert request has been processed. 153 Revert . Enter END command to exit.User Training Guide If you press ENTER to process the Revert request. ‘REJ’ or ‘BAK’ back to ‘DEV’. then Change Man will display the following panel: ---------------------------.

User Training Guide THIS PAGE LEFT BLANK Revert 154 .

LST.BACKOUT CHANGE PACKAGE ------------------------COMMAND ===> PACKAGE ID ===> TEST000074 Press ENTER to process. etc. PRC.: SRC. If you have remote sites. Enter END command to exit. 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. i. You must use the Revert function to get the Change Package back to ‘DEV’ status before you may begin working on it again. To access this Panel: • Select option ‘B’ from the Primary Option Menu for Backout and press ENTER CMNBKOUT ------------------. BACKOUT REASONS -Panel 155 Backout .e. you must initiate the Backout at the remote site(s). Once a Change Package has been backed out. Change Man will back out the entire Change Package during the Backout process. 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. the Package will be in ‘BAK’ status.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. Once the remote sites have been backed out the "reverse ripple" will occur in the development site. LOD. BACKOUT CHANGE PACKAGE – Panel Use this panel to select the Change Package you need to Backout. JCL.

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. 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. Enter END or CANCEL command to exit.User Training Guide Use this panel to enter the reasons why you backed out the Change Package. ===> ===> ===> ===> ===> ===> ===> ===> Press ENTER to process. Need to make additional changes.BACKOUT REASONS -----------------------------COMMAND ===> PACKAGE ID: TEST000052 CREATOR: WSER92 STATUS: BAS INSTALL DATE: 19980313 BACKOUT REASONS: ===> Job abended as a result of poor testing. This panel will appear after the ‘Backout Change Package’ panel.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 .CHANGE PACKAGE LIST -----. CMNBKRSN ---------------------. Change Man will return you to the previous panel Field Free form text area Description Enter the backout reason in this area. ----------------------------. Once you enter the backout reason and press ENTER.

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.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. components and relationships Revert a package to DEV status Display information about Change Man Exit Change Man Press ENTER to process. The Change Package status is also changed from ‘BAS’ back to ‘BAK’. CN(INTERNA L) *** This panel informs you that the Backout request has been processed successfully. CN(INTERNAL) CMN410I . 157 Backout .USER000095 BASELINE REVERSE RIPPLED 1999/01/06 @ 10:34:09.USER000095 BACKED OUT 1999/01/06 @ 10:34:09.CHANGE MAN 4.1. enter END command to exit. Change Man will also notify you the result of the backout jobs by sending you the following MVS Send messages: CMN406I .User Training Guide ---------------.

User Training Guide THIS PAGE LEFT BLANK Backout 158 .

List libraries where component is located B .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. Enter END command to exit. to perform a rename prior to the copy to a user specified dataset.BASELINE BROWSE/PRINT FACILITY ---------------------OPTION ===> L .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 . To exit this panel you can: 159 Browse . Select from components in the baseline libraries.Copy E . This facility provides for member level security checks prior to allowing the user to display or print the member. 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) Press ENTER to process.History S .Print H . 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.Browse in edit mode P .Print expanded (Blank for list) (Blank for list) (Baseline 0 to -n.Panel Use this panel to select the list of components to be viewed. and to fully expand copy and include statements prior to printing. BASELINE BROWSE/PRINT FACILITY . or promotion (+1) libraries. or components in the promotion libraries. To access this Panel: • Select option ‘1’ from the Primary Option Menu for Build.Browse C . then Select option ‘B’ on the Build Options Menu for Browse. Other features of this option include giving the authorized user the ability to copy a component to a user specified dataset. CMNBRWB0 --------------. thus ensuring data integrity.

‘H’ – History. or leave some of the fields blank and select from the resultant lists. Enter L and Change Man will list all the baseline and/or promotion libraries that contain the component that you specify. Enter Y if you wish to build a member list based on additional selection criteria. ‘E’ . Enter V to display the number of levels stored in the SRD (stacked reverse delta) baseline libraries for the component. This allows you to enter standard TSO commands such as EXCLUDE and CHANGE. ‘C’ . Enter X and Change Man will expand all COPY and INCLUDE statements prior to printing the member. ‘X’ .View Stack of SRD.User Training Guide • • Enter the required fields and press ENTER to proceed to next panel. Enter the name of the component that you want to browse of print. Enter the application or leave this field blank to choose from the list of all applications. You will use the following fields for additional selection criteria. Enter ‘0’ to ‘-n’ to select from the baseline library. Enter C to copy a member from a baseline or promotion library to a user specified dataset. ‘P’ – Print.Browse. APPLICATION LIBRARY TYPE LIBRARY LEVEL COMPONENT NAME MEMBER LIST SCAN Field Description Browse 160 . Enter H to display component history. ‘B’ . Enter P to print the member. Enter the library type of leave blank to select from the library type list.List libraries where component is located. Press PF3 or enter ‘END’ on the Option line and press ENTER. ‘S’ . Enter B and Change Man will display the component in browse mode. Enter ‘1’ to ‘+n’ to select from a promotion library.Copy.Print expanded. Field OPTION Description ‘L’ .Browse in edit mode. Enter E and Change Man will display the component in edit mode. Change Man will return you to the previous panel.

Enter the column. for each record. where you want the scan to end. If 0 is entered. the scan will display a list of all members in the baseline library that meet the DATA STRING search criteria. FROM COLUMN TO COLUMN DATA STRING 161 Browse . for each record. Enter the column.User Training Guide RECORDS TO SELECT Enter a numeric value to determine when the scan is to be discontinued. 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. where you want the scan to begin. Enter N if the scan is to be executed without regard to upper and lower case. Enter 0 if you want the scan to begin in column 1. CASE SENSITIVE Enter Y if the DATA STRING should be searched exactly as entered. Enter 0 if you want the scan to end in column 80.

User Training Guide THIS PAGE LEFT BLANK Browse 162 .

To resolve this. 163 Recompile . CMNRCMP0 ---------------------. you would need to recompile those modules that were deemed to be out-of-synch.RECOMPILE SOURCE ---------------------------OPTION ===> L . you would receive an out-of-synch condition (SYNCH5!) when an Audit is performed .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. Enter END command to exit.List libraries where component is found blank . Only the resulting load module is placed into the Change Man Change Package. This function is similar to staging except that the source is not included in the Change Package. To access this Panel: • Select option ‘1’ from the Primary Option Menu for Build. Promotion 1 to nn) (1-Online.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. RECOMPILE SOURCE – Panel Use this panel to select the component(s) to recompile. directly into staging libraries. if you checked out and edited a copy component while other source components (not in the Change Package) also use this copy. The recompile is done from baseline or promotion. then Select option ‘8’ on the Build Options Menu for Recompile. 2-Batch) Press ENTER to process. For example.

Enter the level of the library. NOTE: Batch mode will need to be used for mass recompiles.User Training Guide To exit this panel you can: • • Enter the required fields and press ENTER to proceed to next panel. Enter the language in which the component is written (e. COBOL). Field OPTION Description ‘L’ – List. Use 0 to -999 for baseline versions of a component.Enter 2 to recompile the component in batch mode. Enter the type of component that is to be compiled. or leave some of the fields blank and select from the resultant lists. List all of the levels in which this component may be found. ‘1’ . Press PF3 or enter ‘END’ on the Option line and press ENTER.Display member list. PACKAGE ID COMPONENT NAME SOURCE LIBRARY TYPE LANGUAGE LIBRARY LEVEL RECOMPILE MODE Recompile 164 . Change Man will return you to the previous panel. Enter the ID of the associated Change Package. From this list select the component(s) to be compiled.Enter 1 to recompile the component in foreground ‘2’ . Only a source or like-source component can be used.g. Enter the name of the component to be compiled. or +1 to +99 for promotion versions of a component. A blank in the Option line will display a member list. Blank .

____________________ ===> // TIME=2. The language name that was assigned to the component.Panel This panel is used to compile and optionally link a source component. If you are staging a component from a development library into Change Man and you are renaming the component. LIBRARY TYPE LANGUAGE 165 Recompile .3##).BASE. ? 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.User Training Guide ONLINE RECOMPILE JOB INFORMATION .NOTIFY=WSER92________________________________ ===> //*JOBPARM SYSAFF=ESA1__________________________________________________ ===> //*_____________________________________________________________________ Press ENTER to process. Enter END command to exit. The component that is being staged.REGION=4M.ZERO.MSGCLASS=3. the staged name is the "new name" of the component. Field PACKAGE ID STATUS INSTALL DATE COMPONENT Description The ID of the Change Package that you are working with.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.CLASS=E. The type of component that you are staging.WSER92. The current Change Man status of the Change Package. The date that the Change Package is to be installed.SRC ===> ===> ===> ===> NO ===> YES ===> YES (Blank for list. To access this Panel: • Will automatically appears after the ‘Recompile Source’ panel CMNRCMP1 ------------.

the link edit parms found in component history will be displayed. the compile parms found in component history will be displayed. Enter Yes to suppress component history data processing for the component being recompiled. Enter No to perform the opposite. If this program was previously linked within Change Man. Your Global Change Man Administrator will define available options for you. If only one procedure is available for this language. process component history data for the component being recompiled and bypass the values that were specified on the panel. The Change Man compiling procedure that will be used to compile/link the program. You may type in link edit parms for the program. the data on the panel will be processed instead. Enter "YES" if you need to display additional user options such as CICS pre-compile. this field will be in "browse only" mode.User Training Guide Field DATASET NAME Description The name of the dataset that contains the component that you are staging. COMPILE PROCEDURE COMPILE PARMS LINKAGE EDIT PARMS OTHER OPTIONS SURPRESS HISTORY Recompile 166 . If this program was previously compiled within Change Man. etc. This will either be a Change Man package staging library or a development library. You may type in compile parms for the program. EZTRIEVE.

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. 167 Recompile . Once complete review Package contents to see what the recompile process did.

User Training Guide THIS PAGE LEFT BLANK Recompile 168 .

To access this Panel: • Select option ‘1’ from the Primary Option Menu for Build.Relink single load module blank .REGION=4M.No.RELINK LOAD MODULES ---------------------------OPTION ===> R . Use this function to relink load modules or to delete a relinked or recompiled load module from your Change Package.MSGCLASS=3. relinking is required. A relink target load library to which the member is to be relinked must be specified. To exit this panel you can: 169 Relink .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 . RELINK LOAD MODULES – Panel Use this panel to relink load modules.WSER92. 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. CMNRLNK0 -------------------.CLASS=E. or to delete previously relinked or recompiled modules. Enter END command to exit.____________________ ===> // TIME=2.NOTIFY=WSER92________________________________ ===> //*JOBPARM SYSAFF=ESA1__________________________________________________ ===> //*_____________________________________________________________________ Press ENTER to process. then Select option ‘9’ on the Build Options Menu for Relink. 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.User Training Guide Relink Relink Overview Any time a statically linked subroutine has been modified. 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.333).

It could either be staging or baseline depending on what was entered in the RELINK FROM field. Enter ‘N’ if the LCT library member list is not to be created. the link edit parms found in component history will be displayed. Enter ‘S’ or ‘B’ to relink either from the staging or baseline libraries. EZTRIEVE. Member list that will be created will be from the INPUT LIBRARY TYPE field below. etc. Leave TYPE blank for a member selection list. Blank . TARGET LIBRARY Specify the library type of the load module being relinked. Change Man will return you to the previous panel. or leave some of the fields blank and select from the resultant lists. MEMBER NAME Enter the member name to be processed. Description ‘R’ – Relink single load module. OTHER OPTIONS Relink 170 .User Training Guide • • Enter the required fields and press ENTER to proceed to next panel. Your Global Change Man Administrator will define available options for you. If this program was previously linked within Change Man. This will either be a Change Man package staging library or a development library. If only one procedure is available for this language. Enter "YES" if you need to display additional user options such as CICS pre-compile. this field will be in "browse only" mode. Enter "NO" if this program is not a DB2 program. 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. Field OPTION PACKAGE ID RELINK FROM LCT MEMBER LIST Enter ‘Y’ if the LCT library member list is to be created. You may type in link edit parms for the program. Press PF3 or enter ‘END’ on the Option line and press ENTER. INPUT LIBRARY TYPE Enter the input library type. The ID of the Change Package that you are working with. COMPILE PROCEDURE LINKAGE EDIT PARMS DB2 PRE-COMPILE Enter "YES" if this program is a DB2 program.Display LCT member selection list for multiple processing. DATASET NAME The name of the dataset that contains the component that you are staging.

171 Relink .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.

User Training Guide THIS PAGE LEFT BLANK Relink 172 .

operations personnel.Impact analysis of component relationships Press ENTER to process. Field Description 173 Query . QUERY OPTIONS – Panel Use this panel to selection which Query function you want to execute. Operations personnel monitor package Distribution.QUERY OPTIONS ------------------------------OPTION ===> P C I Package . Managers. Change Man will return you to the previous panel.Query component information Impact .Query package information Component . and depending on the scheduling system used at your site. Installation and Rippling of Baseline. Approvers may often use this function to review the package prior to Approving or Rejecting it. Information for the Query function is being gathered from the Package Master and is a record of all the packages where the component resides. 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. and any concerned parties may wish to sign on to Change Man to query packages and components. 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. application leaders. To access this Panel: • Select option ‘Q’ from the Primary Option Menu for Query and press ENTER CMNQMENU ----------------------. Enter END command to exit. 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.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.

Field Description Query 174 . 2-Complex. TCC or DEL) (1-Simple. BAS. CLO. select all packages) APR.User Training Guide OPTION ‘P’ . OPN.To review and query component information ‘I’ . INS. DIS. FRZ. blank for list. REJ. 4-Participating) (Planned or Unplanned) (Permanent or Temporary) (YYYYMMDD) (YYYYMMDD) (YYYYMMDD) (YYYYMMDD) (Y/N) Press ENTER to process.To view Impact Analysis of component QUERY PACKAGE PARAMETERS .To review and query package information ‘C’ . 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. 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.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. BAK. Enter END command to exit. or pattern. 3-Super.

Enter the department for the Change Packages to be viewed. complex. DEPARTMENT REMOTE SITE AFFECTED PACKAGE LEVEL PACKAGE TYPE PACKAGE TIME SPAN FROM/TO INSTALL DATE installed FROM/TO CREATION DATE To view a list of Change Packages that were created between a range of dates. enter the inclusive dates in the form of YYYYMMDD. super. OTHER PARAMETERS CMNQRY01 -----------------. Enter END command to exit.User Training Guide PACKAGE ID Enter the Package ID or pattern. Enter ID of the remote site. Enter the type (planned or unplanned) of the Change Packages to be viewed. Use this field to mask the list of Change Packages according to the entered package status. The following panel shows these additional fields. enter the inclusive dates in the form of YYYYMMDD. Field Description 175 Query . Enter ‘Y’ to view the panel with additional selection criteria. Enter the time span (permanent or temporary) of the Change Packages to be viewed. or leave this field blank to choose from the list of all applications.EXTENDED SEARCH CRITERIA -----------------------COMMAND ===> NON-SOURCE SOURCE AND LOAD RENAME/SCRATCH INFO CUSTOM COMPONENT ===> ===> ===> ===> (Y/N) (Y/N) (Y/N) (Y/N) Press ENTER to process. or participating) of the Change Packages to be viewed. Enter the TSO ID for the Change Packages to be PACKAGE STATUS CREATOR'S TSO ID viewed. Enter the level (simple. WORK REQUEST ID Enter the Work Request ID for the Change Packages to be viewed. To view a list of Change Packages that are to be during a range of dates.

component scratch or rename requests). CTL.g.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. etc.e.e compiled programs).User Training Guide NON-SOURCE All packages that contain any non-source components (e. QUERY COMPONENT PARAMETERS – Panel Query 176 . All packages that contain any source to load relationships (i. 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. CPY. CMNQRY03 --------------. All packages that contain any utility specifications (i. JCL.). This panel is used to select which Package category you are interested in viewing. PRC.

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 ----------------. 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. Type the 3 or 4 byte application mnemonic for the Change Package you are creating. Enter the type of the components to be displayed. CMN* or CMN?0000). Field COMPONENT NAME Description The name of the component to be checked out. you may use wild cards in this field (e. In order to mask the selection list. COMPONENT TYPE APPLICATION PACKAGE ID PROCEDURE NAME 177 Query . Change Man will return you to the previous panel.g. enter JCL to list all JCL components. Enter the Package ID or pattern. L-Long) (YYYYMMDD) (YYYYMMDD) Press ENTER to process. or leave this field blank to choose from the list of all applications. For example. To checkout all the components enter ‘*’ (be careful).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. Enter the compiling procedure for the component. Enter END command to exit.

Change Man will return you to the previous panel.IMPACT ANALYSIS OF COMPONENTS ----------------------COMMAND ===> SPECIFY SEARCH CRITERIA: COMPONENT NAME ===> COMPONENT TYPE ===> APPLICATION ===> RELATIONSHIP ===> RELATIONSHIP TO ===> Press ENTER to process. Enter the Work Request ID for the Change Packages to be viewed. Enter END command to exit. Enter the from and to dates of the time period you want to search in. Description Field Query 178 . 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. ‘LONG’ .User Training Guide TSOID Enter the TSO ID for the user who last update to the component(s). 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. Enter the option desired for viewing historical nformation for the component. including installed packages ‘SHORT’ . The search will look for relationships for the parameters you have entered.To view only the information of packages in motion . To access this Panel: • Select option ‘I’ from the Query Options panel and press ENTER CMNIMPMP --------------.To view all historical information.

PGM. If you enter a value in this field. LOD. If the Component Name is left blank. leave this field blank and press ENTER. It is required for an 'upstream' search. you may use wild cards in this field (e. Change Man will show the backward link to the Component Name defined above. COMPONENT TYPE APPLICATION RELATIONSHIP RELATIONSHIP TO 179 Query . You must specify a relationship by specifying a library type first in this field. Type the 3 or 4 byte application mnemonic for the Change Package you are creating. 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. This is optional when performing a 'downstream' search. CMN* or CMN?0000). To obtain a list of relationship types.User Training Guide COMPONENT NAME The name of the component to be checked out.g. To checkout all the components enter ‘*’ (be careful). Change Man will show all backward relationships. entering the name of a like-copy member here will furnish a list of all components that 'COPY' this component. For example. enter JCL to list all JCL components. For instance. Enter a relationship to further clarify the request. Enter the type of the components to be displayed. In order to mask the selection list. DSN. Valid types are: CPY.

Query 180 . 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.User Training Guide Exercises for Query Exercise #1: Use the Query function to view all packages that are in FRZ status for any application. You might need to search the baseline JCL library for a valid component name. to see in how many packages it currently exists.

WSER92. blank for list) (Blank for list) (Baseline 0 to -n. The batch portion is executed through the CMN$$CPR skeleton. CMNCOMP1 -------------------------. COMPARE – Panel You can use this panel to enter which component you want to run the compare function on.Compare of one component blank . All the parameters that the program uses are hardcoded within the load module itself. the user may want to review the changes made before resuming the installation process.Display member selection list COMPARE MODE PACKAGE NAME COMPONENT NAME LIBRARY TYPE SOURCE LIBRARY ===> ===> ===> ===> ===> O USER000093 JCL 0 (O-Online.374). Program SERCOMPR controls the compare function that executes the CMNCDCPR program. For example. Promotion +1 to +n) (Y/N) PROMPT FOR REPORT DISPOSITION ===> YES JOB STATEMENT INFORMATION FOR BATCH COMPARE: ===> //WSER92N JOB (X170. then Select option ‘C’ on the Build Options Menu for Compare. Compares can be executed in either online or batch mode. Enter END command to exit.COMPARE --------------------------------COMMAND ===> C . To access this Panel: • Select option ‘1’ from the Primary Option Menu for Build.REGION=4M. B-Batch) (* for all members.NOTIFY=WSER92________________________________ ===> //*JOBPARM SYSAFF=ESA1__________________________________________________ ===> //*_____________________________________________________________________ Press ENTER to process.CLASS=E.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. To exit this panel you can: 181 Compare .MSGCLASS=3. if a change package was created in March and installation was delayed for six months.____________________ ===> // TIME=2. The online portion is executed through the CMNCDCPR program.

This is a required field. This is the level of baseline or promotion from which components are to be compared. Level +1 refers to the first level of Promotion. Press PF3 or enter ‘END’ on the Command line and press ENTER.g. Baseline level 0 refers to the most current version of production. up to +n as subsequent levels. leave it blank to select from a list of all libraries in which a specific component resides. Change Man will return you to the previous panel. you may use wild cards in this field (e.To compare online 'B' . down to -9 as the least current prior version. In order to mask the selection list. Field OPTION Description ‘C’ .T perform the compare via batch Enter the full Package ID The name of the component you want to compare.Display member selection list 'O' . COMPARE MODE PACKAGE NAME COMPONENT NAME LIBRARY TYPE SOURCE LIBRARY PROMPT FOR REPORT DISPOSITION Compare 182 . Indicate how Change Man is to handle disposition of the report output.User Training Guide • • Enter the required fields and press ENTER to proceed to next panel. CMN* or CMN?0000). Enter the library type. To checkout all the components enter ‘*’ (be careful).Compare of one component blank . or leave some of the fields blank and select from the resultant lists.

Exercise #2: 183 Compare .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.

User Training Guide THIS PAGE LEFT BLANK Compare 184 .

With this scan utility. you can specify two (2) data strings. When you request a scan. then Select option ‘S’ on the Build Options Menu for Scan. For a character string search. Be aware that you cannot perform any actions on the items in the list. calls. procedures and various other types of dependencies that are associated with the scanned members. LIBRARY SCAN UTILITY – Panel Use this panel to To access this Panel: • Select option ‘1’ from the Primary Option Menu for Build. Change Man displays a table showing the records found and where they appear. The second data string can be either AND or OR with the first data string. programs executed.User Training Guide Scan Scan Overview The Library Scan facility enables you to perform a quick impact analysis without using the Impact Analysis utility. names. dates. 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 dependency search. 185 Scan . you scan for copybooks. Note: This function does not impact the Baseline Browse scan.

Field APPLICATION Description Type the 3 or 4 byte application mnemonic for the Change Package you are creating. Press PF3 or enter ‘END’ on the Command line and press ENTER. 'O' .To display the member name and the data LIBRARY TYPE SCAN MODE LIST MEMBERS ONLY Scan 186 . Change Man will return you to the previous panel.To display only the member names and no data.To perform the scan via batch ‘YES' .User Training Guide CMNSCN01 -------------------. To exit this panel you can: • • Enter the required fields and press ENTER to proceed to next panel. PGM etc. Enter END command to exit. or leave some of the fields blank and select from the resultant lists. B-Batch) (Y/N. DSN. 'NO' .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. N-Members and Data) (Y/N. * for pattern) ===> ===> ===> 0 ===> 0 ===> ===> ===> ===> OR ===> Press ENTER to process.To scan online 'B' . Scan for copybook. Enter the library type. Y-Members only.) (0 = all) (Y/N) (0 = all) (Max = 80) (Blank for all components.

To include leading or trailing blanks. 'NO' to find all occurrences. Imbedded blanks or non-alphabetic characters will be searched for in place. procedures and other types of dependencies. To include leading or trailing blanks. Enter a character string. Enter a range of components to scan. enclose the string in apostrophes ('). enclose the string in apostrophes ('). Enter starting and ending displacements.To find occurrences of the data string exactly as entered. Enter '0' to search all displacements. even if those members do not actually exist in the dataset. or leave the BEGIN field blank to search all members.For standard data string scan. 'YES' . Scan a single member by entering its name in the BEGIN field. Enter the same number in each field to search that displacement only. both upper and lower case. Enter 'AND' if both the first and second strings are to be found on one line of the member scanned. 'NO' . Specify a number of records to display.To scan for copybook. JCL. programs. PLI and other can be specified in data string 1. or columns. Enter 'OR' if the scan is to contain either the first or second string within the scanned member. RECORDS TO SELECT CASE SENSITIVE? DISPLACEMENT COMPONENTS TO SCAN DATA STRING 1 AND/OR DATA STRING 2 187 Scan . or enter 0 to select all records that exist in the library. dataset names. to begin the search within each record. Enter a pattern (ABC*) in the BEGIN field to limit the scope of the search (the END field will be disregarded). BAL.User Training Guide Field DEPENDENCIES Description 'YES' . Optionally the language type such as COBOL. A range such as MEMBERA to MEMBERZ may be entered to define a range. Enter a second character string. Imbedded blanks or nonalphabetic characters will be searched for in place.

Scan 188 .User Training Guide Exercises for Scan Exercise #1: Use the Scan function to scan for character ‘new’ in the JCL library type. with no case sensitivity and select all the records. Scan in online mode. between columns 5 to 72.

you may have to compress the Staging libraries to reclaim the "dead space". To access this Panel: • Select option ‘1’ from the Primary Option Menu for Build. Change Man will return you to the previous panel. Since partitioned datasets do not reuse space when you make deletions and updates.COMPRESS STAGING LIBRARIES ----------------------COMMAND ===> PACKAGE ID ===> USER000075 JOB STATEMENT INFORMATION: ===> //WSER92N JOB (XXXX.CLASS=E. eventually causing the Staging libraries to become full. then Select option ‘Z’ on the Build Options Menu for Compress. Since PDS's do not reuse space when deletes and updates are made. Press PF3 or enter ‘END’ on the Command line and press ENTER. you populate the libraries with updated components.NOTIFY=WSER92________________________________ ===> //*JOBPARM SYSAFF=ESA1__________________________________________________ ===> //*_____________________________________________________________________ Press ENTER to process. As testing proceeds with the package. Field Description 189 Compress .WSER92. To exit this panel you can: • • Enter the required fields and press ENTER to submit the batch job.REGION=4M. You can use the compress function to compress the partitioned datasets (Staging libraries) associated with change packages. the staging libraries may need to be compressed to reclaim 'dead' space.MSGCLASS=3.User Training Guide Compress Compress Overview When you Create a change package. Enter END command to exit. As the package goes through its life cycle. you often Re-stage many of the components. Use this panel to provide JOB card information for the batch job. the associated Staging libraries are empty.333). 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.____________________ ===> // TIME=2. CMNCPRSS ----------------.

Compress 190 .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.

you should be aware of how often the log is cleared by the system administrator. BROWSE ACTIVITY LOG – Panel Since the Activity Log may contain a great deal of information.BROWSE ACTIVITY LOG ----------------------------COMMAND ===> SCROLL ===> PAGE ONLINE BROWSE ===> YES FROM DATE ===> TO DATE ===> (YES-online. To access this Panel: • Select option ‘L’ from the Primary Option Menu for Log. 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. 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 -------------------. as well as some behind the scene activities that Change Man performs. CMNLOGEX -------------------. NO-batch) (YYYYMMDD. When using the FROM/TO Date fields. you have to access the backup file.User Training Guide Log Log Overview Change Man has a log which records all of the Change Man activities at your site.BROWSE ACTIVITY LOG ----------------------------COMMAND ===> SCROLL ===> PAGE 191 Log . You can also browse the Activity Log for audit return codes on all packages. Nearly all user activities are logged. optional) (YYYYMMDD. If the log has been cleared for the date range you need.

User Training Guide ONLINE BROWSE ===> FROM DATE ===> YES TO DATE ===> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ IND 16 18 20 21 22 30 40 42 44 48 50 80 82 83 84 85 (YES-online. NO-batch) (YYYYMMDD. Change Man will return you to the previous panel.To browse activity log online 'B' .To browse activity log in batch Log 192 . 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. NO-batch) (YYYYMMDD. Press PF3 or enter ‘END’ or ‘CANCEL’ on the Command line and press ENTER. Field ONLINE BROWSE Description 'Y' . optional) (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.

CMNLOGWT -----------------------. LOG DESCRIPTION Change Man will display the following panel while the search is being processed. To display all selected event types from the activity log. leave this field and the next field blank.please wait Date: 1999/01/09 Time: 13:23 The Log function is gathering information from the log file. of the specific period for PACKAGE ID which information is to be displayed. of the specific period from which to display information. 193 Log . leave the FROM DATE and TO DATE fields blank. +-----------+ +-----------+ | | | | | Log | | Log | <----. TO DATE Enter ‘S’ next to each log selection description you wish to view. in YYYYMMDD format.| File | | | | | +-----------+ | | +-----------+ Exercises for Log Exercise #1: Run an online log browse on the Baseline Ripple category on the entire log file. Enter the ending date.User Training Guide FROM DATE Enter the beginning date. Each log selection criteria is described here. in YYYYMMDD format.IN PROGRESS ------------------------------- Your screen is locked . To display all selected event types from the activity log. IND This is an internal indicator to Change Man signifying each type of log selection criteria.

-2. etc. Change Packages may contain one or more components. . and so on. Change Package Within Change Man.Glossary Application ID Application ID is used to identify a “project” within Change Man. in addition to other functions. etc. in addition to a pre-defined number of previous versions (-1. -1 becomes –2. inspects the Staging libraries for any out-of-synch conditions. Baseline Library A Change Man library which stores the most current version (0) of production components. a Change Package is the vehicle in which all changes are moved from a development environment to a production environment. They are used to identify package ownership. This process is called baseline ripple. Applications / Projects are defined groups for which Change Packages are to be created and manipulated. the previous production component becomes the –1 version. Baseline Ripple The process whereby a component becomes the new production component. Usually a four-character code is assigned to a specific Application.). Audit Lite A subset of the Audit utility. it inspects the staging libraries of a Change Package for discrepancies between package components. Approval The process whereby Change Packages are approved by designated individuals prior to installation into baseline / production. The baseline ripple starts with the oldest baseline library and works its way back to the most current library. Audit A Change Man utility that. which are required for a change. source to load integrity.

Usually. (See chapter in this section for complete details). . in which a component resides. Concurrent Development Facility (CDF) A selectable Change Man option which allows you to reconcile multiple versions of a component. The component could be a source module. PROC. datalib member etc. It also makes a package eligible for approval. JCL. DDL. Compile The process of transforming source into object format. Checkout The act of copying components from baseline libraries to staging or development libraries. a member of a library that has been brought into Change Man for the purpose of being modified. Freeze The act of locking Change Packages so that modifications are prohibited. load module. Demotion The process whereby components are removed from promotion libraries. Global Parameters These parameters are defined in the initial Change Man setup to tailor Change Man to your data center environment. other than Change Man or production libraries.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. copybook. Component A single member of a Change Package. Development/Personal Library Any library. They are modifiable at any time by the Global Administrator.

copybook components use ‘CPY’. Package Staging libraries are the living Change Package. It is typically a VSAM file. including package definitions.g. Mass Stage The process of staging a multiple number of components into a Change Package. etc. administration information. They will assist in tailoring each separate application according to their individual needs. Package Staging Libraries Package Staging libraries are created solely for the purpose of holding components of a particular Change Package. load modules use ‘LOD’. Local Parameters These parameters are defined within the initial setup of each Change Man Application (project). The contents of the staging libraries are copied to the baseline libraries during the installation process. Package ID Each Change Package is automatically assigned a unique package ID. PAYR000001). Library Type A three character identifier which represents the various component types in an application. Package Master The repository for all Change Man information. components. and so on. This job will spawn and submit an individual batch job for each stage request.Installation Installation is the final process in the Change Package Life Cycle. Source components have library type of ‘SRC’. This facility moves the processing for a set of staging requests to a batch job. Consisting of the Application ID and a sequential number (e. It is the process that does the final copy from the Package Staging libraries into the baseline/production libraries. . Online Forms Manager A selectable Change Man option which allows you to create and store forms as part of a change package.

Project Synonymous with the term "application". the component into an executable load module. it is the act of copying a component from staging to a promotion environment or level. binds. there is a second Staging step which compiles. 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. Applications are defined groups for which Change Packages are to be created and manipulated. the component is installed. From these libraries. Its Installation is subject to the complete approval list Production Library The library that contains all production versions of each component. . Planned Package A type of Change Package which is created during normal business hours in a non-emergency situation. and can be modified and tested. If the component is source (SRC).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. Promotion A pseudo-production environment that allows for a variety of testing. Separate library types may utilize separate production libraries. link/edits. Stage This function is used to copy components from development or personal libraries into Change Man Staging libraries. etc. Relink The process of transforming object code into an executable load module. Also.

which do not need to go through all the processes in a Package Life Cycle. If created outside of regular 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. then not all Package Life Cycle processes are required and usually there is an abbreviated approval list. . Typically components of a temporary package will be installed into a special library used to hold temporary fixes. Unplanned Package A type of Change Package which is created for an emergency situation. Its installation date is not dependent on the Planned Installation calendar. Often created outside of normal business hours. Temporary Packages are usually created in conjunction with Unplanned Package.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.