Professional Documents
Culture Documents
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.
Table of Contents
Preface.............................................................................................................................9
Corporate Background................................................................................................................. 9
User Training Guide Content....................................................................................................... 12
Change Man Course Offerings .................................................................................................... 13
Change Man for New Users................................................................................................... 15
Change Man for Experienced Users ...................................................................................... 16
Introduction....................................................................................................................17
What Is Change Man ................................................................................................................... 17
The Change Man ALLSITE Change Package Life Cycle ....................................................... 19
Change Man Library Environment (ALLSITE - Data Flow Diagram) ........................................ 21
Change Man Library Environment (DEVPROD Site - Data Flow Diagram) .............................. 22
Change Man Terminology ........................................................................................................... 24
Accessing Change Man ............................................................................................................... 26
Change Man Panel and Menu Navigation ................................................................................... 28
Create ..............................................................................................................................39
Create Overview .......................................................................................................................... 39
CREATE: CREATE A NEW PACKAGE - Panel ...................................................................... 41
CREATE: PACKAGE DESCRIPTION - Panel.......................................................................... 45
CREATE: INSTALLATION INSTRUCTIONS - Panel............................................................. 47
CREATE: ON SITE INFORMATION - Panel ........................................................................... 49
CREATE: AFFECTED APPLICATIONS - Panel ...................................................................... 51
CREATE: COMPLEX / SUPER INFORMATION - Panel ........................................................ 53
Commonly Asked Questions..................................................................................................... 55
Exercises for Create .................................................................................................................. 56
Update .............................................................................................................................57
Update Overview......................................................................................................................... 57
UPDATE: PACKAGE INFORMATION Panel...................................................................... 57
UPDATE: CONTROL INFORMATION Panel..................................................................... 57
UPDATE: PACKAGE DESCRIPTION - Panel......................................................................... 58
UPDATE: INSTALLATION INSTRUCTIONS - Panel........................................................... 59
UPDATE: SCHEDULING DEPENDENCIES - Panel .............................................................. 59
UPDATE: AFFECTED APPLICATIONS - Panel.................................................................... 60
UPDATE: COMPLEX/SUPER INFORMATION - Panel........................................................ 60
UPDATE: SITE INFORMATION Panel ............................................................................... 61
Utility...............................................................................................................................63
Utility Overview .......................................................................................................................... 63
UTILITY: RENAME / SCRATCH OPTIONS Panel ............................................................. 63
Table of Contents
Checkout .........................................................................................................................69
Checkout Overview ..................................................................................................................... 69
CHECKOUT OPTIONS Panel................................................................................................. 70
CHECKOUT - Panel ................................................................................................................... 70
CHECKOUT: PACKAGE COMPONENTS Panel.................................................................. 74
Commonly Asked Questions..................................................................................................... 77
Exercises for Checkout ............................................................................................................. 77
Stage ................................................................................................................................79
Stage Overview............................................................................................................................ 79
STAGE OPTIONS - Panel .......................................................................................................... 80
STAGE: FROM DEVELOPMENT Panel................................................................................ 81
STAGE: PACKAGE COMPONENTS -Panel ............................................................................ 84
STAGE: COMPILE AND LINK - Panel.................................................................................. 88
COMPONENT LIST PARAMETERS Panel........................................................................... 92
Commonly Asked Questions..................................................................................................... 95
Exercises For Staging ............................................................................................................... 95
Listing .............................................................................................................................97
Listing Overview ......................................................................................................................... 97
BROWSE COMPRESSED LISTINGS - Panel........................................................................... 97
Audit................................................................................................................................103
Audit Overview ........................................................................................................................... 103
AUDIT CHANGE PACKAGE - Panel ....................................................................................... 105
Out-of-synch Conditions.............................................................................................................. 111
Commonly Asked Questions................................................................................................... 114
Exercises for Audit ................................................................................................................. 115
Freeze ..............................................................................................................................117
Freeze Overview.......................................................................................................................... 117
FREEZE OPTIONS Panel........................................................................................................ 117
UNFREEZE / REFREEZE Package Panel ............................................................................... 120
Exercises for Freeze................................................................................................................ 121
Promote ...........................................................................................................................123
Promote/Demote Overview ......................................................................................................... 123
PROMOTE CHANGE PACKAGE Panel ................................................................................ 123
PROMOTE OPTIONS -Panel ................................................................................................ 125
DEMOTE OPTIONS Panel...................................................................................................... 126
COMMON COMPONENTS Panel ...................................................................................... 127
Exercises for Promote/Demote ............................................................................................... 128
Approve...........................................................................................................................129
Approve Overview ...................................................................................................................... 129
APPROVE PACKAGE PARAMETERS - Panel........................................................................ 129
APPROVE/REJECT OPTIONS - Panel...................................................................................... 131
PACKAGE INFORMATION CATEGORIES - Panel................................................................ 132
APPROVAL LIST Panel.......................................................................................................... 133
Table of Contents
List...................................................................................................................................137
List Overview .............................................................................................................................. 137
PACKAGE LIST PARAMETERS - Panel.................................................................................. 138
CHANGE PACKAGE LIST - Panel ........................................................................................... 140
PACKAGE LIST OPTIONS - Panel........................................................................................... 142
Exercises for List .................................................................................................................... 143
Delete...............................................................................................................................145
Delete Overview .......................................................................................................................... 145
DELETE OPTIONS Panel ....................................................................................................... 145
MEMO DELETE CHANGE PACKAGE Panel....................................................................... 146
RESTORE MEMO DELETED PACKAGES Panel ................................................................ 148
Revert ..............................................................................................................................151
Revert Overview.......................................................................................................................... 151
REVERT CHANGE PACKAGE - Panel .................................................................................... 151
REVERT REASONS- Panel ....................................................................................................... 152
Backout ...........................................................................................................................155
Backout Overview ....................................................................................................................... 155
BACKOUT CHANGE PACKAGE Panel................................................................................ 155
BACKOUT REASONS -Panel.................................................................................................... 155
Browse.............................................................................................................................159
Browse Overview ........................................................................................................................ 159
BASELINE BROWSE/PRINT FACILITY - Panel .................................................................... 159
Recompile........................................................................................................................163
Recompile Overview ................................................................................................................... 163
RECOMPILE SOURCE Panel ................................................................................................. 163
ONLINE RECOMPILE JOB INFORMATION - Panel.............................................................. 165
Exercises for Recompile ......................................................................................................... 167
Relink ..............................................................................................................................169
Relink Overview.......................................................................................................................... 169
RELINK LOAD MODULES Panel.......................................................................................... 169
Exercises for Relink................................................................................................................ 171
Query...............................................................................................................................173
Query Overview........................................................................................................................... 173
QUERY OPTIONS Panel........................................................................................................ 173
QUERY PACKAGE PARAMETERS - Panel ............................................................................ 174
PACKAGE INFORMATION CATEGORIES Panel .......................................................... 176
QUERY COMPONENT PARAMETERS Panel...................................................................... 176
IMPACT ANALYSIS OF COMPONENTS Panel................................................................... 178
Exercises for Query................................................................................................................. 180
Compare..........................................................................................................................181
Compare Overview...................................................................................................................... 181
COMPARE Panel..................................................................................................................... 181
Table of Contents
Scan .................................................................................................................................185
Scan Overview............................................................................................................................. 185
LIBRARY SCAN UTILITY Panel........................................................................................... 185
Exercises for Scan................................................................................................................... 188
Compress ........................................................................................................................189
Compress Overview..................................................................................................................... 189
COMPRESS STAGING LIBRARIES Panel............................................................................ 189
Exercises for Compress........................................................................................................... 190
Log...................................................................................................................................191
Log Overview .............................................................................................................................. 191
BROWSE ACTIVITY LOG Panel........................................................................................... 191
Exercises for Log .................................................................................................................... 193
Glossary ..........................................................................................................................194
Table of Contents
Preface
Corporate Background
SERENA Software - The Change Specialists - is a privately-owned software company founded in 1980
and is a worldwide provider of software that enables superior development and maintenance of
applications throughout the enterprise. The company's focus is increasing software development
productivity while reducing the cost of computing for mainframe-based applications. SERENA's
products are used today in more than 2,400 data centers worldwide.
The SERENA product line provides complete software life-cycle support for corporations through a
diversified offering that is enhanced by alliances with leading software vendors. Along with innovative
software, SERENA offers a comprehensive range of services to its customers including support,
education, implementation services and frequent software enhancements.
SERENA's Solutions/2000 makes it easy to identify, modify, test and implement date-sensitive
applications in year 2000 situations.
SERENA is headquartered in Burlingame, California, with an office in the U.K.
SOFTWARE PRODUCTS
COMPAREX
COMPAREX is a multi-function database, load module and text comparison utility that automates the
complex tasks of file comparison and systems testing. By performing line-by-line byte-level
comparisons, COMPAREX can identify differences between any two films. COMPAREX plays a vital
role in the testing and validation phase of year 2000 conversion projects. COMPAREX is an essential
tool for application testing, software quality assurance, reconciliation of production source and load
libraries, project-based application development and source code reconciliation. COMPAREX has more
than 1,400 corporate licenses worldwide and is the leading comparison tool for Fortune 1000
organizations.
Preface
TM
Change Man
Change Man is a comprehensive system designed to provide both reliable and streamlined
implementation of software changes from development into production. It is the fastest implementing
software change management system for MVS environments. Change Man improves the availability of
your software by ensuring that changes are successful when they get to production. It also cuts
maintenance costs and provides the most thorough treatment of concurrent development available.
Optima Software markets Change Man in the US and selected markets internationally.
STARTOOL
STARTOOL provides an on-line environment for application and system programmers in an IBM
OS/390 or MVS environment. It can perform complex file and data management tasks, including editing
and managing PDS, PDSE, sequential, direct access and VSAM files, and their contents. With
STARTOOL, users have access to powerful and versatile tools critical for year 2000 conversions,
including the capability to find and change date-sensitive code; reconcile load modules to source code;
identify compile and execution time options (COBOL); locate and replace data in groups of members and
data sets. STARTOOL also provides specialized services such as applying Data Aging techniques to
existing production files to assist in creating year 2000 test files without programming.
Preface
10
TM
StarWarp
StarWarp addresses the issue of Data Aging by providing a method of shifting, or aging the dates in
existing files, thus providing the ability to perform necessary testing without the need to write one-time
specialized programs for each test scenario. StarWarp helps by providing basic date aging capabilities.
StarWarp minimizes the need to write batch programs for each file-aging situation, and enables
programmers to create test data for year 2000 conversion projects by automating the process of
incrementing, decrementing or specifying default values for day, month, year, and century fields.
StarWarp addresses business rules assuring that certain activities can only occur on certain days, such as
the last day of the month or the first Monday of the quarter.
SyncTrac@
SyncTrac is an MVS software environment synchronization and data set change tracking product. It
speeds development and problem resolution with the ability to automatically detect, report, and recover
from changes across local and remote environments. SyncTrac provides a standardized approach for
maintenance and distribution of software thereby reducing redundant tasks performed by programmers.
It ensures synchronization of multiple environments to guarantee system integrity and recoverability in
the event of a disaster. SyncTrac was jointly developed with High Power Software (Sacramento, CA).
TM
X:Change
X:Change delivers a single GUI interface to MVS data that provides consistency and ease of use. It
offers a unique bidirectional high-speed file transfer that improves development by eliminating TSO
bottlenecks. X:Change integrates with leading application development tool vendors and provides a
robust development environment that enables programmers to use their own desktop systems for
development thereby ensuring higher productivity at a lower cost.
11
Preface
Change Man Concurrent Development Facility Option Users Guide and Reference
Change Man Online Forms Manager Option: Users Guide and Reference
These manuals can usually be found with either your Local Administrator or Global Administrator
person(s). If additional copies are required then please contact your Global Administration
Representative and they can contact SERENA Software International.
Since there is a large amount of information contained in the User Training Guide and the other
references guides, our customers have requested that SERENA Software International offer several
courses to best assist them to learn the Change Man system. As a result SERENA offers many courses to
our customers. Please review Change Man Course Offerings section to view the current list of courses
offerings.
Preface
12
1 day
1 day
13
Preface
Preface
Application developers
Business analysts
14
Intended audience:
Prerequisites:
Change Man general concepts and facilities, includes Change Man architecture and
Change Package Lifecycle
Change Man terminology
How to navigate effectively and efficiently within Change Man panels
How to respond to general error conditions or situations using the tutorial function
How Change Man can improve installing changes into baseline environments
productively
Topics covered:
Primary Options: Notify, Tutorial, Build, Freeze, Promote, Approve (baseline), List (basic
functions), Delete, Query
Build Options: Dates, Create, Update, Utility, Checkout, Stage (basic functions), Audit (brief
overview), Browse (basics), Listing
Students will perform many hands-on exercises to develop confidence with core product
functionality and panel navigation.
15
Preface
Intended audience:
Change Man user with any exposure to the Change Package process
Individuals that assist any development staff with Change Man issues,
questions or training
Global or Local Change Man administrators
Prerequisites:
Topics covered:
Primary Options: Build, Freeze (Unfreeze), Promote (Demote), List (detailed overview),
Backout, Revert, Log
Build Options: Stage (all functions), Audit (detailed overview), Recompile, Relink, Compare,
Scan, Compress, Browse (all functions)
CMNWRITE step in the compile process
Introduction to Change Man CDF and DB2 options
Introduction to OFM (Custom)
Review of installation, backout and update Impact Analysis jobs
Remote Promotion + Distribution
Preface
16
Introduction
What Is Change Man
Change Man is a comprehensive system designed to provide both reliable and streamlined
implementation of software changes on the MVS system. It is a system that manages and
automates the process of migrating software changes, or applications, from a development
environment to any test environment and then to the production environment. A comprehensive
TSO/ISPF interface guides the user through various change management processes.
Change Man can manage the installation of a variety of components, such as:
Batch programs written in Assembler, COBOL, COBOL II, COBOL III, or PL/I
CICS programs written in Assembler, COBOL, COBOL II, COBOL III, or PL/I
CICS basic mapping services (BMS) maps and the copy code
... any other component that can be stored in a PDS or PDS-Like structure like
'Librarian' or 'Panvalet'.
17
Introduction
Introduction
18
Create
Stage
Checkout
(DEV)
(Promote)
(Modify
Components)
test
(DEV)
(DEV)
(Audit)
(Unfreeze)
(FRZ)
(Revert)
Impact
Analysis
(DEV)
(Promote)
Freeze
(REJ)
test
(FRZ)
(Backout)
(FRZ)
Approve
(BAK)
(APR)
Baseline Ripple
(BAS)
Optional Processes
19
Introduction
1.
The first step of the Change Package Life Cycle is the Create process. A Change Package contains all of
the elements to be edited and installed into production, and is identified by a unique package ID automatically
generated by Change Man. When a Change Package is created, the information that Change Man needs in order
to track and control the package is entered. This includes the implementation instructions, whether it is a
temporary or permanent change, the installation date and time, etc.
2.
The typical next step is to Checkout components from baseline. With checkout, components from your
baseline libraries are copied to either a Change Man staging library or to a personal development library where
changes can be made.
3.
Package components are now ready to be Staged. In the stage process the user can make all the changes or
modifications required to all components. For source components, staging will ordinarily run the appropriate
translation procedure to create associated load modules. Components such as documentation or copy members
are simply copied into the staging libraries, if they aren't there already.
4.
Depending on the installation, the Change Package must pass an Audit before Freeze. The audit process
ensures that no unexpected problems will occur. For example, if a component in the production library has been
changed since it was checked out, Change Man alerts you to the problem by creating an out-of-synch condition
for the package.
5.
After successfully passing the audit, the next step is to Freeze the Change Package. This locks the package
(prohibiting further changes), and makes the package available for the promotion and approval processes.
6.
Promotion is an optional step. After successfully staging all components in the Change Package, the
Change Package may then be Promoted. Promotion allows a Change Package to be moved through various
levels of testing (e.g. promote from system testing to acceptance testing).
7.
Once all of the necessary Approvals have been gathered by Change Man, the package is ready to be
installed. If the Manual installation method was selected when the package was created, the package will be
installed immediately after the final approver has approved it. If the CMN method (Change Man's internal
scheduler) was selected, Change Man will automatically install the package on the date and time specified at
package creation. If an external scheduler is used (e.g. CA7, ESP, ZEKE, JOBTRAC, etc.), Change Man will
convey the install information to that scheduler so that it can install the Change Package.
8.
Once the package has been installed, Change Man will perform the Baseline Ripple. Baseline Ripple is the
process that Change Man executes to version all package components, i.e.: 0 becomes -1, -1 becomes -2, -2
becomes -3, etc. and the new baseline 0 version is installed.
Introduction
20
New
Component
Development
Test
Environment
(level 10)
Test
Environment
(level 20)
Stage (S1)
Promote
Temporary
Work
File
Test
Environment
(level 30)
Change
Package
Stage (S2)
Edit
STAGING
Audit
Freeze
Approve
Checkout
Baseline
Ripple
Baseline (0)
Baseline (-1)
Backout
Baseline (-2)
21
Introduction
New
Component
Development
Test
Environment
(level 10)
Test
Environment
(level 20)
Stage (S1)
Test
Environment
(level 30)
Promote
Stage (S2)
Edit
Temporary
Work
File
Change
Package
STAGING
Checkout
Remote
Promote
Remote
Test
Environment
Baseline
Ripple
Distribute
Baseline
(0)
Production
Staging
Libraries
Baseline
(-1)
Reverse
Baseline
Ripple
Introduction
Baseline
(-2)
Install
Remote
Production
(0)
Backout
22
Remote
Production
(-1)
Change Man/MVS manages the transition of components from production to development and back to
the production libraries by using Change Package staging libraries. Each Change Package will have its
own set of staging libraries. All the Change Man processes rotate around these staging libraries. These
staging libraries are the actual living breathing Change Package.
Existing production components are copied into the staging libraries via the Checkout process, or new
components from outside development libraries can be copied into the staging libraries via the Stage
(S1) process. Component modification can occur within the Package staging libraries via the Stage (S2)
process. The stage (S2) edit process creates a Temporary Work file where the user does all the
component modifications. Once complete the Temporary Work file is copied back to the Package staging
libraries.
The Promote, Remote Promote and Distribution processes copy the required components from the
Package staging libraries into the test environment files or the production files. .
All components from the Package staging libraries are copied into the baseline libraries during the
Baseline Ripple process.
23
Introduction
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.
Introduction
24
Component
A single member of a Change Package. Usually, a member of a library that has been brought into
Change Man for the purpose of being modified. The component could be a source module, load
module, PROC, JCL, copybook, DDL, datalib member etc.
Freeze
The act of locking Change Packages so that modifications are prohibited. It also makes a
package eligible for approval.
Library Type
A three character identifier which represents the various component types in an application.
Source components have library type of SRC, copybook components use CPY, load modules
use LOD, etc.
Package ID
Each Change Package is automatically assigned a unique package ID. Consisting of the
Application ID and a sequential number (e.g. PAYR000001).
Promotion
A pseudo-production environment that allows for a variety of testing. Also, it is the act of
copying a component from staging to a promotion environment or level.
Stage
This function is used to copy components from development or personal libraries into Change
Man Staging libraries. If the component is source (SRC), there is a second Staging step that
compiles, link/edits, binds, etc. the component into an executable load module. Stage is also the
function that you use to make changes or modifications to the components.
25
Introduction
Date
:
Time
:
Version :
1998/12/11
12:14
4.1.6
CMN@PRIM--------- CHANGE MAN 4.1.6 PRIMARY OPTION MENU ---------- INIT Complete
OPTION ===> _
1
2
3
4
5
A
B
C
D
L
N
O
Q
R
T
X
Build
Freeze
Promote
Approve
List
Admin
Backout
CDF
Delete
Log
Notify
OFMlist
Query
Revert
Tutorial
Exit
The options displayed on the Primary Option Menu are built based upon the authorization of your
User ID. Change Man dynamically builds this panel after verifying, with your host security system,
Introduction
26
what Change Man functions you have access to. The user that had the previous panel displayed has
the following authorizations granted:
Administrator (Option A is displayed)
Revert packages (Option R is displayed)
Back Out packages (Option B is displayed)
Online Forms package list (Option O is displayed as the customer purchased this Change
Man option.)
Change Man Users who are developers or approvers will most likely not have any of the additional
options listed above. Most of the functions that they will use will be accessed from the Build Option
menu, option 1 from on the Primary Option Menu.
From the Primary Option Menu, you can access all the Change Man services and functions by using
the panel by panel access method or the direct access method or the Package List method. See the
below for all descriptions and details
27
Introduction
Or
COMMAND => +1.6.2
COMMAND => =1.6.2
OPTION
=> =1.6.2
Each character of the direct access command is a single character options on successive panels.
Change Man will display the panel of the last character in the direct access stacked commands.
To return to a previous menu or panel, type END in the option or command field on any panel or
press the appropriate PF key command, usually PF3.
28
ROW 1 TO 13 OF 13
SCROLL ===> PAGE
LIB DESCRIPTION
CPY Copybooks
CTC Control Cards
DBB DB2 Bind Control Statements - Plans
DBR DB2 Database Request Modules
DOC Documentation
S JCL Job Control Language
_ LCT Linkedit Control Cards
_ LOD Load Modules
_ LST Compressed Compile Listings
_ MPC Copybooks - CICS Maps
_ PKG DB2 Bind Control Statements - Packages
_ PRC JCL Procedures
_ SRC Source Code
******************************* Bottom of data *******************************
_
_
_
_
_
Type an S beside the selection or member you wish to select and press ENTER.
To exit and return to previous panel press PF3.
29
ROW 1 TO 15 OF 15
Introduction
COMMAND
NAME ===>STATUS
_ $$$INDEX
_ #ACF2
_ #NDM
_ A
_ ACKLA
S AFRICAD
_ AFRICAU
_ ALLOCBAS
_ AMBLIST
_ ARCHIVE1
_ ASMDB2SQ
_ ASSEMBLE
_ A2VECFG
_ BACKUP
_ BAYD
VV.MM
01.00
01.00
01.00
05.01
06.01
01.01
01.01
01.01
01.00
01.00
01.00
01.00
01.00
01.00
01.01
CREATED
1996/01/26
1996/01/26
1996/01/26
1995/06/23
1995/01/06
1996/11/19
1996/11/19
1998/01/29
1996/01/26
1996/01/26
1996/01/26
1996/01/26
1996/01/26
1996/01/26
1996/03/15
LAST MODIFIED
1997/06/21 13:59
1996/06/18 12:20
1996/06/18 12:20
1998/04/20 16:21
1996/09/05 12:39
1997/02/13 16:28
1997/02/13 16:28
1998/04/20 12:37
1996/06/18 12:20
1996/06/18 12:20
1996/06/18 12:20
1996/12/30 17:50
1996/01/26 17:09
1996/06/18 12:20
1997/02/13 16:28
SIZE SCROLL
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.
To exit and return to previous panel press PF3.
B to Browse an item.
Type the following commands on the Command line and press ENTER:
SORT to Sort the list. (Only valid for member and procedure/language displays)
L to Locate an item in the list. For example, L xxxxxxxxx where xxxxxxxx is the
component name.
After executing one of these commands, a message normally appears in the status column to
indicate your action (such as BROWSE for a browsed list item).
Introduction
30
Not all commands are available from all lists. If you type an incorrect command or character in a
panel, Change Man displays the correct available commands from that panel.
Using Patterns
The system often encourages you to input a pattern to get a range of values in a list from Change
Man. Pattern rules are:
Closing Panels
31
Introduction
In general, you close panels by pressing Enter to process your changes, and then typing End
and pressing Enter (normally, the PF3 key).
You can abandon your changes two ways:
Introduction
Some panels require you to enter End in the Option or Command field and press Enter
to abandon.
Other panels require you to type CANCEL in the Command line and press Enter. In
general, the panel you are viewing always tells you how to abandon your changes.
32
Enter the CLIST for the Change Man subsystem you want to sign onto in option 6 of
TSO
CMN@PRIM--------- CHANGE MAN 4.1.S PRIMARY OPTION MENU --------- INIT Complete
OPTION ===> _
1
2
3
4
5
A
B
C
D
L
N
O
Q
R
T
X
Build
Freeze
Promote
Approve
List
Admin
Backout
CDF
Delete
Log
Notify
OFMlist
Query
Revert
Tutorial
Exit
Enter the required selection on the Option line and press ENTER
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:
If the Global Notification File is updated, Change Man will notify you. A message,
"NOTIFICATION UPDATED", will be displayed in the upper right-hand corner of the Primary
Option Menu whenever this file is updated. This notification message will reappear every time
you sign onto Change Man, unless you view the Notification File. To view this file you use the
Notify panel.
To access this Panel:
Select option N from the Primary Option Menu for Notify and press ENTER
-BROWSE -- WSER24.WSER24.CMN94152.T1447172.OUTLIST - LINE 00000000 COL 001 080
COMMAND ===>
SCROLL ===> PAGE
********************************* TOP OF DATA ********************************
GLOBAL ADMINISTRATION MESSAGE 07/01/1998
1. New library types have been added to perform automatic JOBSCANs.
2. Security request forms have been added to Online Forms.
Discontinue the use of "paper" form SEC00010.
APPLICATION ADMINISTRATION MESSAGE
APPLICATION PAYR 07/05/1998
1. All baseline libraries will be compressed on Sunday.
2. Audit level has been changed to 4.
APPLICATION GENL 07/05/1998
1. Department number is now required when creating a new change package.
Enter your Cost Center number in this field.
Upon exiting the notification panel, you will have the option of printing the Global
Notification File. The following panel with JOB card will be displayed:
CMNNOT00 ----------- GLOBAL NOTIFICATION REPORT DISPOSITION ------------------
34
OPTION ===>
OUTLIST DATASET
: WSER92.WSER92.CMN98351.T1551260.OUTLIST
D
K
PD
PK
Delete
Keep
Print and Delete
Print and Keep
Press PF3 or enter END or CANCEL in the Option line to return to the Primary
Option Menu
35
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
GENERAL
BUILD
FREEZE
PROMOTE
APPROVE
DELETE
REVERT
QUERY
LOG
ADMIN
Press PF3 or enter END or CANCEL in the Command field to return to the
previous panel
Note: To scroll down or up in the tutorial panel you use the PF10 (up) and PF11 (down)
function keys.
36
Select option 1 from the Primary Option Menu for Build and press ENTER
Dates
Create
Update
Custom
Utility
Checkout
Stage
Audit
Recompile
Relink
Browse
Compare
Listing
Scan
Compress
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
Select option 1 from the Primary Option Menu for Build, then Select option 0 on
the Build Options Menu for Dates
ROW 1 TO 19 OF 52
SCROLL ===> PAGE
#
SUN
MAX
2 255
0 255
0 255
0 255
0 255
0 255
0 255
0 255
0 255
0 255
0 255
0 255
0 255
0 255
0 255
0 255
0 255
0 255
0 255
TOTALS
#
MAX
5 1785
28 1785
0 1785
1 1785
0 1785
0 1785
0 1785
0 1785
0 1785
0 1785
0 1785
0 1785
0 1785
0 1785
0 1785
0 1785
0 1785
0 1785
0 1785
Enter the required selection in the Command field and press ENTER
Press PF3 or enter END or CANCEL in the Command field to return to the previous
panel
38
Create
Create Overview
The first process in the Change Man Life cycle is the create process. This is where you create an
entry in the Package Master with a change package ID number and some general housekeeping
information. Creating a change package involves describing the "outer structure" of a package.
Basically, you provide information about the change package to Change Man through a series of
panels. The panels you encounter during the Create process may vary, depending on the options
you choose along the way. Combined, these panels provide the following information about the
package to Change Man:
control information
description
site responsibility
job scheduling
installation date
other details
Since the Create process differs depending on the choices you make when you create the Change
Package, there may be up to 8 different panels that you might see, they are:
Panel Name
Panel ID
CMNCRT01
Package Description
CMNCRT02
Installation Instructions
CMNCRT03
Scheduling Dependencies
CMNCRT04
Affected Applications
CMNCRT05
On Site Information
CMNCRT06
CMNCRT07
Complex/Super
CMNCRT08
39
Create
No matter what options you plan to use for the new change package, you will always start the
Create process with the Create a New Package panel. The panels which you encounter as you
Create a change-package are governed by these factors:
The package level: simple, participating, or super/complex
Your site configuration: All (you have no remote sites); Development (change packages are
distributed to remote sites, you cannot install them into Production Libraries); Production (this
is a remote site, no development is performed on this machine); or Development/Production
Create
40
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)
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 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
41
Create
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
Description
OPTION
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.
APPLICATION
Type the 3 or 4 byte application mnemonic for the Change Package you
are creating.
REQUESTER'S
NAME
REQUESTER'S
PHONE
Create
DEPARTMENT
PACKAGE LEVEL
42
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
PACKAGE TIME
SPAN
PACKAGE TO
COPY FORWARD
UNPLANNED
REASON
43
Create
Create
Field
Description
TEMPORARY CHANGE
DURATION
44
You can also access this panel through the Update Package Information (See Update
Package Information section)
ROW 1 TO 12 OF 12
SCROLL ===> PAGE
After you have entered all required fields, press ENTER or PF3 key to continue to the
next panel in the package create
Enter CANCEL in the Command line and press ENTER, the Create Change Package
process is abandoned and Change Man returns you to the Create a New package panel
45
Create
Field
Description
Create
Description - you may use this area to enter any additional information
about this change. Keep in mind that some of the people that will be
approving your package may not know too many details about its
content. This description panel can be used to inform these approvers of
the specific package details.
46
You can also access this panel through the Update Package Information (See Update
Package Information section)
ROW 1 TO 12 OF 12
SCROLL ===> PAGE
SCHEDULER
''''
''''
''''
''''
''''
''''
''''
''''
''''
''''
''''
===> CMN
After you have entered all required fields, press ENTER or PF3 key to continue to the
next panel in the package create process
Enter CANCEL in the Command line and the Create Change Package process is
abandoned and Change Man returns you to the Create a New package panel
47
Create
Field
Description
CONTINGENCY
Code that represents the action you want the operations staff to take if a
problem is encountered while Installing your change package:
1 - Hold production and contact analyst - Discontinue running the
production jobs for your application until a supporting analyst can be
reached for instructions.
2 - Back out change, continue production - Back out of the change
package and continue running your application's production jobs as
normally scheduled.
3 - Other - Use if 1 and 2 above do not apply. Describe in this field
some other action to be taken if there are problems in installing this
change package. This field has a maximum length of 44 characters.
SCHEDULER
CMN - Change Man holds the installation until the date and time you
specify on one of the Site Configuration panels.
Manual - Change Man installs the change package as soon as the final
approval is given.
Other - Specify scheduling instructions for change packages that use a
job scheduler other than CMN and Manual.
Create
Free form text that contains detailed instructions on how your Change
package should be installed. These can include, but are not limited to,
production job dependencies and change package Installation
dependencies.
48
You can also access this panel through the Update Package Information (See Update
Package Information section)
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_
After you have entered all required fields, press ENTER to complete the Package Create
process
Press PF3 or enter CANCEL in the Command line and press ENTER, the create
change package process is abandoned and Change Man returns you to the Create a New
package panel
49
Create
Field
Description
INSTALL DATE/TIME
In this field, enter the date and time that the package is to be
installed.
PRIMARY/BACKUP
After you have filled in all the information on the panel and pressed ENTER, Change Man will
then create your change package, return you to the BUILD OPTION panel, and display the
Change Package ID in the upper right hand corner of the panel. Finally Change Man updates the
Planned Installation Calendar.
Create
50
you can also access this panel through the Update Package Information (See Update
Package Information section)
ROW 1 TO 12 OF 12
SCROLL ===> PAGE
APPL
____
____
____
____
____
____
____
____
____
____
____
Enter any affected applications then press ENTER to continue to the next panel in the
package create process, if there are no affected applications, then just press ENTER
Press PF3 or enter CANCEL in the Command line and press ENTER, the create
change package process is abandoned and Change Man returns you to the Create a New
package panel
51
Create
Field
Description
COMPLEX/SUPER
PACKAGE ID
APPL
Enter the application affected by this package. If you enter a value in this
field, Change Man adds to the approval list of the package in your
current application any approver that differs (interfacing approver) from
the planned approval list of the application you enter in this field.
Create
52
You can also access this panel through the Update Package Information (See Update
Package Information section)
Note: Use the REFRESH command to 'undo' a list that was entered in error.
CMNCRT08------------ CREATE: COMPLEX/SUPER INFORMATION -COMMAND ===>
PACKAGE ID: TEST000064
ROW 1 TO 12 OF 12
SCROLL ===> PAGE
STATUS: OPN
PACKAGE ID
TEST000012
TEST000045
TEST000077
__________
__________
__________
__________
__________
__________
__________
__________
__________
Field
Press PF3 or enter CANCEL in the Command line and press ENTER, the create
change package process is abandoned and Change Man returns you to the Create a
New package panel
Description
53
Create
PACKAGE ID
Create
54
Answer.
Yes you can. Use the Package Update option to change the package level in the
Package Control Information panel.
Question.
If I select Manual for the scheduler, does Change Man use the Install date and
Time?
Answer.
No it does not. The package gets installed as soon as the last approver approves
the package.
Question.
Answer.
No it does not. You will receive an error message Invalid Date Range.
Question.
Answer.
55
Create
Create
Exercise #1:
Exercise #2:
Exercise #3:
Create two (2) participating planned permanent Change Package with a complex
parent linking the two new participating packages.
56
Update
Update Overview
After creating a change package you may wish to update some of the information associated with
it. You can update most of the information entered during the creation process as long as the
package you update has a Development (DEV) or Open (OPN) status and you have access to the
project. You can browse the information if the package is in Frozen (FRZ) status. If you have
selectively unfrozen the general category, you can update options I through 6. Also, if you have
selectively Unfrozen the onsite category, you can update option 7.
Select option 1 from the Primary Option Menu for Build, then Select option 2 on
the Build Options Menu for Update
Control
General
Instruction
Dependencies
Affected Apps
Complex/Super
Install Dates
Complex/Super
Complex/Super
Update
Update
Update
Update
Update
Update
Update
Change
Change
Enter the update option you want to perform 1 9, press the ENTER key
press PF3 or enter END in the Command line and press ENTER, Change Man returns
you to the panel you came from
Note: The PACKAGE ID is updateable, so check that the package ID displayed is the
Change Package you want to work with.
Update
This panel displays the change package control information, which was entered
when the package was created. You can update any of the highlighted fields.
CMNPGNL1 ---------------- UPDATE: CONTROL INFORMATION ---------------------COMMAND ===>
PACKAGE ID: TEST000066
COMPLEX/SUPER ID: N/A
STATUS: DEV
STATUS:
PACKAGE TITLE
===> Payroll month end install
REQUESTER'S NAME
REQUESTER'S PHONE
WORK REQUEST ID
DEPARTMENT
PACKAGE LEVEL
===>
===>
===>
===>
===>
PACKAGE TYPE
PACKAGE TIME SPAN
UNPLANNED REASON CODE
TEMPORARY CHANGE DURATION
===>
===>
===>
===>
WSER92
666 123-3456
PAY234
D1234
1
(1-Simple, 2-Complex,
3-Super, 4-Participating)
PLANNED
PERM
(* for list)
(In days)
STATUS: DEV
Update
58
SCHEDULER
STATUS: DEV
===> MANUAL
ROW 1 TO 12 OF 12
SCROLL ===> PAGE
SUCCESSOR
________
________
________
________
________
________
________
________
________
________
STATUS: DEV
PREDECESSOR
________
________
________
________
________
________
________
________
________
________
59
Update
ROW 1 TO 12 OF 12
SCROLL ===> PAGE
STATUS: DEV
STATUS: OPN
APPL
____
____
____
____
____
____
____
''''
''''
''''
''''
''''
''''
''''
ROW 1 TO 12 OF 12
SCROLL ===> PAGE
STATUS: OPN
TEST000012
TEST000045
TEST000077
__________
__________
__________
__________
__________
__________
Update
60
YYYYMMDD
19980313
FROM
0000
TO
2359
CREATOR: WSER200
STATUS: DEV
PRIMARY/BACKUP CONTACTS
Bob Programmer___________
Susan Analyst____________
61
PHONE NUMBERS
696 6245_______
696 6518_______
Update
Update
62
Utility
Utility Overview
The Utility Request facility is designed to Rename or Scratch (delete) components in production
and/or Baseline Libraries. These requests can be the only items in a change package or can be
part of a change package with Staged components. Change Man during Package production
Installation and Baseline Ripple will process these utility requests. Change Man processes these
requests after installing and rippling staged component versions.
Select option 1 from the Primary Option Menu for Build, then Select option 4 on
the Build Options Menu for Utility
Baseline
Package
Enter 1 or 2 in the Option line then press ENTER to proceed to next panel
Press PF3 or enter END in the Option line and press ENTER, Change Man will return
you to the previous panel
Field
Description
63
Utility
OPTION
PACKAGE ID
Enter the Change Package ID, or double check the package ID displayed
is still the package you want to work with.
Utility
Press PF3 or enter END in the Option line and press ENTER, Change Man will return
you to the previous panel
64
Field
Description
OPTION
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
LIBRARY TYPE
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.
COMPONENT
NEW NAME
For each member selected for Rename, enter the new name.
65
Utility
Use this panel to activate or delete utility requests, Rename or Scratch that exist as part of a
change package.
To access this Panel:
CMNUTL03-------------------COMMAND ===>
REQ
NAME
RENAME TYPE
_ SCR BAYU
JCL
_ REN BDCU
NEWNAME JCL
_ SCR BHFCOPY
CPY
_ SCR CMN$TRC
CPY
ID
WSER92
WSER92
WSER92
WSER92
ROW 1 TO 4 OF 4
SCROLL ===> PAGE
STATUS
FUNCTION
ACTIVE
ACTIVE
ACTIVE
ACTIVE
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
Description
COMMAND
66
Question.
Answer.
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?
Answer.
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.
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
Utility
68
Checkout
Checkout Overview
After you have created a change package, you use Checkout to copy components from secured
libraries, such as baseline or promotion, to Change Man staging libraries or to the user's personal
PDS.
When you checkout a component, the statistics are carried forward and the version number (the
vv portion of vv.mm) is incremented. Change Man will add the checkout information to the
statistics that make up the component's history. If you checkout to a valid change package ID, the
component name is added to the package's component list.
If another user checks out the same component into a different change package(s), Change Man
will sent concurrent development notification messages to all parties concerned.
Checkout can be restricted or denied for components that are already contained in a
change package, disallowing Checkout of a component that is part of a package in
motion unless it is an unplanned change.
Checkout can include components that reside in promotion libraries (if any exist for a
given application).
You can check out components by selecting them from a list of Baseline or Promotion
Library components.
If Checkout is associated with a change package, then each component may be checked
out to that package one time only; that is, until the component is either Staged or deleted
from the package component list.
69
Checkout
Select option 1 from the Primary Option Menu for Build, then Select option 5 on
the Build Options Menu for Checkout
Enter 1 or 2 in the Option line then press ENTER to proceed to next panel
Press PF3 or enter END in the Option line and press ENTER, Change Man will return
you to the previous panel
Field
Description
OPTION
PACKAGE ID
Enter the Change Package ID, or double check the package ID displayed
is still the package you want to work with.
CHECKOUT - Panel
Checkout
70
COMPONENT NAME
LIBRARY TYPE
LANGUAGE
SOURCE LIBRARY
===> ________
===> JCL
===>
===> 0
CHECK OUT TO
===> S
PERSONAL LIBRARY ===>
LIBRARY DSORG
===>
CONFIRM REQUEST
CHECKOUT MODE
LOCK COMPONENT
(Y/N)
(1-Online, 2-Batch)
(Y/N)
===> YES
===> 1
===> NO
Enter the mandatory input field and then select from the displayed lists to complete the
checkout request
Press PF3 or enter END in the Option line and press ENTER, Change Man will return
you to the previous panel
Field
Description
71
Checkout
OPTION
PACKAGE ID
COMPONENT NAME
LIBRARY TYPE
Enter the Library type of the library you want to perform the
checkout operation to. If you leave this field blank, Change Man
will display a list of possible library types to select from.
LANGUAGE
SOURCE LIBRARY
CHECK OUT TO
PERSONAL LIBRARY
Field
Description
Checkout
72
LIBRARY DSORG
CONFIRM REQUEST
CHECKOUT MODE
LOCK COMPONENT
NOTE: Batch checkout will not update the member's ISPF statistics. Batch checkout will also
bypass the OVERLAY PRIOR STAGED MODULE Admin. Rule. If a component is locked by
another user you must go to the stage package driven list (1.6.2) to UNLOCK (UC) the
component prior to checkout.
73
Checkout
ROW 1 TO 6 OF 6
SCROLL ===> PAGE
ID
REQUEST
WSER92
WSER92
WSER92
WSER92
WSER92
WSER92
Press PF3 or enter END or CANCEL in the Option line and press ENTER, Change
Man will return you to the previous panel
Field
Description
COMMAND
SHORT, or LONG.
Checkout
74
STA
DEV
DEV
DEV
PROMOTION
SIZE PROCNAME
ID
CMNHASM WSER124
CMNHASM WSER124
147 CMNHASM WSER124
If you continue with the checkout of the component, Change Man sends a MVSSEND message
to all the other developer(s) informing them that you have checked out a component that exists in
their package. In this way, Change Man is constantly alerting the developers of what concurrent
development is in the application. It still remains the responsibility of the individual developers
to communicate amongst themselves regarding the resolutions of the various versions of the
component.
Overlay Warning: This panel appears when you are about to overlay a component that is
75
Checkout
already in your package and does not match the version you are about to checkout. The panel
shows the TSO ID of the person who last changed the component you are about to overlay.
Confirm Delete Request: Any delete requests while in checkout option 2 (Checkout package
components), Change Man will present the Confirm Delete Request panel. This panel gives you
the option of verifying the component name and reconsider your request. Press ENTER to
complete the delete request. Press PF3 or enter CANCEL or END in the Command line then
press ENTER to cancel the delete request.
CMNSTG13 ------------------ CONFIRM DELETE REQUEST -------------------------COMMAND ===>
PACKAGE ID:
COMPONENT NAME:
COMPONENT TYPE:
LANGUAGE:
STATUS:
CHANGED DATE:
CHANGED TIME:
PROCEDURE NAME:
TSOID:
TEST000001
CMNEX001
SRC
ASM
CHECKOUT
951002
193824
CMNASM
WSER18
Checkout
76
How does checkout from promotion +1 or higher work? What happens if the
component I checked out gets changed in the package I checked it out from? Or,
I change the component and install to baseline, will the other package overlay
my changes when it goes to baseline?
Answer.
If the component does not change in the package you checked it out from, then
there are no out-of-synch problems. If however the component does change in
the package you checked it out from, then there can be an OUT-OF-SYNCH
situation. If the first package installs to baseline, then the next time you go to
edit the component you will get a COMPONENT OUT-OF-SYNCH message.
Your changes will not be saved and you must checkout the component from
baseline.
If you have no changes to make then Audit will catch the out-of-synch condition.
Exercise #1:
Check out a JCL component to a Change Package, check it out to the staging
library, from the 0 current version of baseline, in online mode.
Exercise #2:
Check out a source component to a Change Package, check it out to the staging
library, from the -1 version of baseline and lock the component.
Exercise #3:
Check out all the source component to a Change Package that start with A*,
from 0 current version of baseline.
Exercise #4:
Create a new Change Package with the copy forward option. You can use the
package from exercise #1 as the copy forward package. Then check out all the
components from the copied forward package to this new package.
77
Checkout
Checkout
78
Stage
Stage Overview
Stage is where developers will spend most of their time in the Change Man lifecycle. Stage or
staging a component is where you will edit a component, compile and link edit a program, or
change the status of other components like JCL. Also in Stage you can introduce new
components into your application.
During the checkout process, if any source or like-source components were checked out, a
language name was specified or assumed. Based on this language name, Change Man submits
the job to compile the component(s). If the component(s) are non-source, Change Man may
simply mark the component as ACTIVE, which indicates that it is ready to move on to the next
step. If the component(s) were checked out to a personal library, Change Man will copy the
component into a Change Man staging library.
Your Change Man administrator can effect how the Stage process will work. They will have
chosen 1 of the following parameters:
Stage Rule 1 - All users can Stage new components. This means they can Stage components
that are not yet associated with a package (Development Driven Staging) as well
as Stage component that are associated with a package (Package Driven Staging).
Stage Rule 2 - Allows only users who have been defined (by the local administrator) to a special
entity by their TSO ID can Stage new components. Otherwise, they can only
Checkout and Stage components that are associated with a change package.
Stage Rule 3 - Does not allow you to Checkout and Stage new components, only ones that
already exist in your Baseline Library. This effectively disables Development
Driven Staging.
79
Stage
Select option 1 from the Primary Option Menu for Build, then Select option 6 on
the Build Options Menu for Stage.
Dev
Package
Parms
Stage
Enter 1, 2 or 3 in the Option line then press ENTER to proceed to next panel.
Press PF3 or enter END in the Option line and press ENTER, Change Man will return
you to the previous panel.
Field
Description
OPTION
PACKAGE ID
Enter the Change Package ID, or double check the package ID displayed
is still the package you want to work with.
80
STATUS: DEV
===>
===>
===>
===> YES
===> 1
===> YES
Enter the required fields and press ENTER to proceed to next panel, or leave some of
the fields blank and select from the resultant lists and press ENTER.
Press PF3 or enter END in the Option line and press ENTER, Change Man will return
you to the previous panel.
Field
Description
81
Stage
Stage
ISPF LIBRARY
OTHER PARTITIONED
or
SEQUENTIAL
Use this field to enter the dataset name that contains the
components to be staged. This field is most commonly used for
datasets which have other than three qualifiers. If you are
copying all the components, append * to the dataset name.
LIBRARY TYPE
LANGUAGE
STAGE NAME
CONFIRM REQUEST
STAGE MODE
SUPPRESS MESSAGES
82
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
ROW 1 TO 15 OF 15
SCROLL ===> PAGE
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
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
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
Select option 2 from the Stage Options panel and press ENTER.
Stage
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
Description
COMMAND
84
COMPONENT: A
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
Field
Description
NAME
TYPE
STATUS
85
Stage
Field
Description
INCOMPLETE
A compile and/or link edit has been submitted for the component and it
has not completed execution yet or it has failed.
ACTIVE
The component has been edited (if it is non-source), successfully
compiled/linked (source), or copied successfully from a development
library into the change package (development driven staging).
CHANGED
The date and time that the component was last changed.
PROCNAME
ID
REQUEST
The last request that was performed for the component, i.e.:
STAGE, EDIT, etc.
Additional Processing
Depending on the processing you select on the component, other additional panels will be
initiated. The most common process is an edit. The edit process on any component will create a
Change Man temporary file, which you can edit. This temporary file is where you can make all
your changes or enhancements. Once complete press PF3 to return and save the changes back to
your change package. Change Man will then display a comparison report (see below) which
shows you all the differences between the last staging library version of the component to the
temporary file you just edited. Change Man will then display a Comparison Report Distribution
panel (see below) which enables you to print the comparison report. If the component you have
changed is a source (SRC) type component, then Change Man will automatically give you the
option of doing a compile and link (see below). Other processes will return to the Package List
panel with the status of the component being changed to active. Any component delete request
will display a Confirm Delete Request panel (see below). Component stage requests also display
a Confirm Stage Request panel (see below).
During any processing on any component in the package, Change Man will also notify you of
any concurrent development or if other packages contain the same component (see below).
Stage
86
This panel will be displayed automatically to prompt you for the disposition of the Comparison
report.
----------------------- COMPARISON REPORT DISPOSITION -----------------------OPTION ===>
REPORT DATASET NAME:
REPORT DISPOSITION
'WSER18.WSER18.CMN97316.T2147244.OUTLIST'
===> D
D
K
PD
PK
Delete
Keep
Print and Delete
Print and Keep
87
Stage
STATUS: DEV
STAGED NAME:
LIBRARY TYPE:
LANGUAGE:
DATASET NAME:
ALTER
SRC - Source Code
ASM
WSER200.CMN.TRAIN.USER.#000074.SRC
COMPILE PROCEDURE
COMPILE PARMS
LINK EDIT PARMS
DB2 PRE-COMPILE
OTHER OPTIONS
===> CMNASM
===>
===>
===> NO
===> YES
Stage
Field
Description
PACKAGE ID
STATUS
INSTALL DATE
STAGED NAME
LIBRARY TYPE
LANGUAGE
DATASET NAME
The name of the dataset that contains the component that you are
staging. This will either be a Change Man package staging library or a
development library.
88
Field
Description
COMPILING
PROCEDURE
COMPILE PARMS
You may type in compile parms for the program. If this program was
previously compiled within Change Man, the compile parms found in
component history will be displayed.
LINKAGE EDIT
PARMS
You may type in link edit parms for the program. If this program
was previously linked within Change Man, the link edit parms found in
component history will be displayed.
DB2 PRE-COMPILE Enter "YES" if this program is a DB2 program. Enter "NO" if this
program is not a DB2 program.
OTHER OPTIONS
Enter "YES" if you need to display additional user options such as CICS
pre-compile, EZTRIEVE, etc. Your Global Change Man Administrator
will define available options for you.
The User Option function is used to incorporate up to twenty additional user options within a
Change Man compiling procedure. The variables are passed to the file tailored skeleton.
Specifying 'Y' will cause the user option to be expanded within the procedure, 'N' or BLANK
will cause the user option to be suppressed. This panel gets customized a great deal in most
shops.
CMNUSR01 ------------------- STAGE: USER OPTIONS ---------------------------COMMAND ===>
NAME: ALTER
COMPILE ONLY
CICS PRE-COMPILE
EASYTRIEVE NO NAME
USER OPTION 07
USER OPTION 09
USER OPTION 11
USER OPTION 13
USER OPTION 15
USER OPTION 17
USER OPTION 19
TYPE: SRC
LANGUAGE: ASM
===>
===>
===>
===>
===>
===>
===>
===>
===>
===>
===>
===>
===>
===>
===>
===>
===>
===>
===>
===>
89
Stage
Once the compile has completed, Change Man can automatically populate a compressed listing
library (LST) to contain the output from the compilation. This listing may be viewed on-line or
printed.
During the link process Change Man inserts information into the Load module created,
specifically the IDR record. Change Man uses SET SSI (an IBM time stamp) to update the IDR
record and link the source and load to ensure integrity. This IDR record also contains the
program ID and the Change Package ID that this module was updated in.
Change Man's LCT processing provides the developer with the ability to specify linkage edit
control parameters such as INCLUDEs for specific subroutines, ENTRY statements, and a name
card. When using LCT processing you must specify a name card in each member. This name
card will control the name of the resultant load module. If LCT processing is not required,
Change Man dynamically constructs the linkage edit name card to be the same name as the
source.
TEST000074
ASMBLDV3
SRC
ASM
INACTIVE
19981130
075559
WSER92
Valid responses are, press the ENTER key to confirm the request, or enter PF3 or enter
CANCEL in the Command field to cancel the request.
Stage
90
TEST000074
ALTER
SRC
ASM
INCOMP
19981207
105438
WSER92
ROW 1 TO 3 OF 3
SCROLL ===> PAGE
91
Stage
Select option 3 from the Stage Options panel and press ENTER.
STATUS: DEV
===>
===>
===>
===>
===>
===>
===>
===>
(1-Active,
2-Incomplete,
3-Checkout, 4-Inactive)
(YYYYMMDD)
(YYYYMMDD)
S
YES
YES
YES
(S-Short, L-Long)
(Y/N)
(Y/N; applies to batch stage)
(Y/N; applies to edit in stage)
Stage
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
Description
PACKAGE ID
STATUS
INSTALL DATE
92
Field
Description
STAGED NAME
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
Can you turn off the comparison report from being displayed every time you
exit an edit session?
Answer.
Yes! In the Component List Parameters panel (S3), you can set the
Comparison Report filed to NO.
Create a new change package and checkout a JCL component into the package
from baseline. Then Stage the component using Stage Option Package. Edit the
component and reply to the displayed panels.
Note: Observe how the status of the component changes.
Exercise #2:
Checkout a source program from baseline into the package from exercise #1.
Then Stage the source using Stage Option Package. Edit the source component
and issue the compile and link. Again watch how the components status
changes. Once the compile and link is complete display the source to load
relationship of the source component.
Exercise #3:
Stage a new component into your application. Use the Stage Option Dev to
stage the new component into your change package.
95
Stage
Stage
96
Listing
Listing Overview
The Browse Compressed Listing function allows you to browse a compile/link edit listing of a
source component compiled by Change Man. Change Man has a facility which allows you to
store the output from the compile/link edit procedures within the library type LST. This
eliminates the need to keep printed copies of the listings. As the typical compile/link edit listing
is very large, Change Man stored these listings in a compressed format. The Browse Compressed
Listing facility is used to decompress these listing into a temporary file for viewing and or
printing. The disposition of the decompressed listing is specified by the
user. A listing can be narrowed down by application, package ID and/or date.
Select option 1 from the Primary Option Menu for Build, then Select option L on
the Build Options Menu for Listing.
===>
===> LST
===>
===>
Enter the required fields and press ENTER to proceed to next panel.
Press PF3 or enter END in the Option line and press ENTER, Change Man will return
you to the previous panel.
97
Listing
Field
Description
PACKAGE ID
APPLICATION
COMPONENT
NAME
LIBRARY TYPE
Enter the staging library type for the compressed listings. The
default is LST.
FROM DATE
TO DATE
The components, which satisfy the fields entered on the previous panel, will be displayed on the
following panel.
CMNBLST1------------------ BROWSE COMPRESSED LISTINGS ------- ROW 1 TO 7 OF 7
COMMAND ===>
SCROLL ===> PAGE
Press END command to exit.
PACKAGE ID: TEST000074
STATUS: DEV
NAME
LEVEL
VV.MM CREATED
CHANGED
SIZE INIT
ID
_ PROGA
STAGING 01.02 1997/07/29 1997/07/29 15:11
500 1133 SERSTAR
_ PROGA
BASE-00 01.02 1996/07/29 1996/07/29 15:11
482 1133 SERSTAR
_ PROGA
BASE-01 01.00 1995/11/28 1995/11/28 15:31
355
355 SERSTAR
S PROGC
BASE-00 01.00 1996/01/31 1996/01/31 14:14
16
16 SERSTAR
_ PROGCKL BASE-00 01.00 1995/10/12 1995/10/12 13:45
338
338 SERSTAR
_ PROGC1
BASE-00 01.02 1995/01/11 1995/01/11 14:47
407
407 SERSTAR
_ PROGC2
BASE-00 01.02 1995/01/11 1995/01/11 14:43
335
335 SERSTAR
_ PROGD
BASE-00 01.00 1995/11/29 1995/11/29 12:47
418
418 SERSTAR
****************************** Bottom of data ********************************
Listing
98
Enter S beside the program you would like Change Man to display the decompressed
compile/link edit listing, then press ENTER to display next panel.
Press PF3 or enter END or CANCEL in the Command line and press ENTER,
Change Man will return you to the previous panel.
Field
Description
NAME
LEVEL
VV.MM
CREATED/CHANGED/
SIZE/INIT
ID
99
Listing
Section 1
Prior to any pre-compiler or compiler step, Change Man executes program CMNWRITE.
CMNWRITE scans your source code, detects and optionally expands COPY members and
variations of INCLUDES. Nesting of COPYBOOKs and INCLUDEs is supported up to 99
levels.
The first section of the listing shows the search order that Change Man has built for your
SYSLIB concatenation. The libraries and the order are based on the configuration that has been
built by your Change Man Administrator. Change Man parses your source code for
COPY/INCLUDE statements and will search the library concatenation for those members.
Listing
100
101
Listing
Listing
102
Audit
Audit Overview
The Audit function or process plays a very important part in the life cycle of a Change Package.
Its function is to inspect the contents of the Package Staging libraries of an evolving Change
Package with respect to Baseline libraries. The audit looks for situations such as package
components that have changed in the Baseline libraries since the time you checked them out into
your package. Meaning the version in your package is no longer the most current, or a package
containing a LOD component that does not match its SRC component. These situations are
called out-of-synch conditions. Audit provides Change Man the ability to help you detect code
that is inconsistent with your development procedures.
Audit has an Audit rule, or parameter, which is set by the Administrator. This Audit rule can be
set between 0 5. If the Audit Rule has been set to 0, then Audit is totally optional, meaning you
are not required to run Audit. If the Audit rule has been set between 1 5, then Audit must be
run prior to the Freeze process. The Audit process runs as a batch job on the MVS system. It
produces an Audit Report, which lists all the occurrences of out-of-synch conditions. The report
also provides current and historical information on each component in your package. This
information can be used to resolve out-of-synch conditions easily. Audit jobs also end with a
return code. This return code indicates of what type of out-of-synch condition was found in your
package. A return code of 4 means that some out-of-synch conditions were found, but they are
usually only informational. Return codes of 8, 12, or 20 usually means the user must correct the
out-of-synch conditions before the package can be frozen. See The Audit Job for more detailed
information on the Audit return code. The higher the return code, the more severe out-of-synch
conditions that were found. Audit rules 1 5 indicate which Audit return code is acceptable in
order to pass Audit. Example, if the Audit rule is set to 4, then the Audit return code must be 4 or
less to pass the Audit process. If the return code was 8, then the out-of-synch conditions, which
caused the return code of 8, must be corrected in order to pass Audit.
Note: If your package does not pass Audit, then it can not be frozen.
Audit may be run at anytime during the package life cycle. Small Change Packages probably
only need 1 or 2 audits, while larger Change Packages may run audits daily. The audit job is
typically run after all the components have been checked out and ALL modifications have been
completed. If any of the components are SRC or CPY type components, then their related
compiles and links should also be done. If you modify a component in your package, then the last
Audit return code is no longer valid, and you must run another Audit.
103
Audit
The way Audit knows about all component relationships because it reads the Impact Analysis
table. This Impact Analysis table is typically a DB2 table and it holds all component
relationships. The types of relationships within the Impact Analysis table are;
Audit also queries and reports on nested levels of copybooks for a component within the
Baseline. For example:
Types of Audits
There are two types of Audits you can run, they are;
A Full Audit
A Full Audit will check for relationships for the components in your Change Package with
respect to the baseline libraries in your application. When you run a Full Audit on a
participating package in a complex/super package, Audit will notify you of out-of-synch
conditions across the entire complex/super package. Depending on how many components
you have in your package, the number of baseline libraries in your application, the number of
relationships between these two, and if the package is associated with a complex/super
package, a Full Audit may run for a significant amount of time. Therefore it might be best to
run a Full Audit, on this type of package, near the end of the packages development life
cycle. A Full Audit also updates the audit return code in your package.
Audit
104
staging libraries first. Once these conditions have been resolved, you can then run the Full
Audit. Audit Lite does not report on out-of-synch conditions that reference baseline; namely
DUPLIC!, SYNCH5!, SYNCH8!, and SYNCH10! When you run a Staging Library Only
Audit on a participating package, in a complex/super package, Audit catches out-of-synch
conditions only for that package, and not for any other participating packages in the
complex/super package. Running an Audit Lite DOES NOT update the Audit return code in
your package. This also means Audit Lite does not satisfy the Audit requirement for freezing
a package.
Select option 1 from the Primary Option Menu for Build, then Select option 7 on
the Build Options Menu for Audit.
===>
===>
===>
===>
TEST000089
NO
NO
NO
(Y/N)
(Y/N)
(Y/N)
Enter the desired audit fields and press ENTER. Change Man will submit the audit job
and usually return to the Build Options Menu.
Press PF3 or enter END in the Command line and press ENTER. Change Man will
return you to the previous panel.
Field
Description
105
Audit
Audit
PACKAGE ID
AUTO RESOLVE OF
OUT-OF-SYNCHS
106
This notification message informs you what return code your audit job ended with. This return
code indicates what type of out-of-synch conditions were found in your package.
The return codes are;
00 means there were no out-of-synch conditions found in your package and that
everything is clean. No user action is required.
04 indicates that some out-of-synch conditions were found but they are very minor and
are usually informational. Typically no user action is required.
08 indicates that some out-of-synch conditions were found and that they will need to be
reviewed and possibly corrected. These out-of-synch conditions are SYNCH5! and
SYNCH8!, relationships between package CPY and LOD components to the baseline
libraries. Typically user action is required prior to freezing the package.
12 - indicates that some out-of-synch conditions were found and that they will need to be
reviewed and typically MUST be corrected. These out-of-synch conditions are
SYNCH2!, SYNCH4!, SYNCH6!, SYNCH7!, SYNCH9!, SYNCH10!, SYNCH11!,
SYNCH12!, SYNCH13!, SYNCH14!, SYNCH15! and SYNCH16! User action required
prior to freezing the package.
20 - indicates that many of the above out-of-synch conditions were found and that they
need to be reviewed and typically MUST be corrected. User action required prior to
freezing the package.
107
Audit
columns 55 -134
Y DECEMBER 30, 1998 (1998/364) 11:47:18
Page 1
*************************************************************
T000013 Created 1998/11/19 at 11:49:41 by WSER73
*
9/01/01
Package Status: DEV
*
cription of member from directory entry in library - (SRC) *
*******************************************************************************
-------*
*---------------------- S t a g i n g ----------------------*
********
*************************************************************
tso-id
Name
VV.MM Created
Changed
Size Init Tso-id
Audit
108
________
________
USER01
CMNCCASM
USER02
SYNCH12! CMNOFM
USER33
CMNZDRV
CMNZFRM
_____
01.01
01.05
02.08
02.13
__________
1996/01/26
1996/01/26
1996/01/26
1996/01/26
________________
1998/11/24 12:27
1998/11/24 12:24
1998/11/24 12:23
1998/11/24 12:19
____
0344
0010
1255
1161
____
0343
0010
1241
1148
_______
WSER73
WSER73
WSER73
WSER73
If a component is listed only on the Baseline side, the component has not been included in the
change package. If a component is listed only on the Staging side, the component is new (has
never been processed by Change Man). Any out-of-synch Flags will be listed in the center of
these reports (see SYNCH12!).
Many of the report statistics are the ISPF/PDF statistics in the PDS directory. They are very
similar to ISPF browse or edit headings
Audit Report - Legend and Summary Report
109
Audit
Audit
110
Out-of-synch Conditions
The following is a list of out-of-synch conditions that the AUDIT job reports on. The return code
listed, indicated how severe each out-of-synch condition is. It is also used to generate the return
code of the Audit job.
DUPLIC!
!COPY
Embedded copybooks
Return Code - 0
Shows that there is a copybook within a copybook (an embedded copybook).
This is an informational out-of-synch, which just shows that a relationship exists.
Suggested Resolution: No action required.
SYNCH0!
SYNCH1!
SYNCH2!
SYNCH3!
SYNCH4!
111
Audit
SYNCH5!
SYNCH6!
Return Code - 12
SYNCH8!
SYNCH9!
SYNCH10!
SYNCH11!
Hashing discrepancy
Return Code - 12
The hashing calculation during the Audit of the component differs from the
calculation created during staging.
Suggested Resolution: Verify the changes to the component and stage again.
SYNCH12!
Orphan component
Return Code - 12
This synch appears when an unknown component is found in the staging library.
It occurs when a component has been copied into the staging library outside of
Change Man, or when a compile fails.
Suggested Resolution: Delete the component from the staging library.
Audit
112
SYNCH13!
Baseline/Staging discrepancy
Return Code - 12
This synch appears for staged components that have a baseline version that has
been changed or updated since it was staged into a change package.
Suggested Resolution: Checkout the component from baseline and retrofit the
changes, or restage the component.
SYNCH14!
SYNCH15!
SYNCH 16!
113
Audit
Audit
Question.
If you checkout a SRC component and make NO change to the component, but
you Stage the component (meaning you run a compile/link) and its status
changes to ACTIVE, will Audit flag this component?
Answer.
Question.
Answer.
NO! The new load module will have a different date and time stamp, even the
SETSSI date will be different.
Question.
Do you need to run an audit on a Change Package that only contains Scratch
and Rename requests?
Answer.
Question.
If I run a Full Audit on my participating package, does Audit review the other
participating packages associated in the complex/super package?
Answer.
Yes, a Full Audit will check for any out-of-synch conditions across all the other
participating packages within the complex/super package. A Audit Lite will not
review the other participating packages and only check its own package staging
libraries.
Question.
Answer.
No. Change Man will issue an error message Invalid Package Level
Package level must be simple or participating.
114
Exercise #1:
Exercise #2:
Exercise #3:
Run a Full Audit on a Change Package that does not have ALL the components
in ACTIVE status. Review the Audit Report and resolve the out-of-synch
conditions.
Exercise #4:
Checkout a copybook used by some SRC program in the baseline library, then go
into Stage and modify the copybook, then run Audit. Review the Audit Report.
The report should show a SYNCH5!
115
Audit
Audit
116
Freeze
Freeze Overview
Once a Change Package has been built, tested, and audited, you freeze it. This process puts the
package in frozen FRZ status, locks out further modification, and makes it available for
approval. After the freeze process, the Change Package can still be "unlocked" and moved back
to development DEV status with the use of the Revert function. You can also use the Unfreeze
function to unlock specific package categories so they can be modified.
During the freeze process, Change Man checks for two things:
That all components in the package are in ACTIVE status. This indicates that the
STAGE function completed successfully for all components
If either of these checks fail, Change Man will not allow the Change Package to be frozen.
Select option 2 from the Primary Option Menu for Freeze and press ENTER.
117
Freeze
Online
Batch
Selective
Reset
(Y/N)
(O-Online, B-Batch)
Freeze
Enter the freeze option you want to execute and press ENTER.
Press PF3 or enter END in the Option line and press ENTER. Change Man will return
you to the previous panel.
Field
Description
OPTION
PACKAGE ID
AUTOMATIC PROMOTION
AFTER FREEZE
Field
Description
118
ONLINE OR BATCH
PROMOTION
Time: 13:40
==========================================================================
|
The Freeze function is performing the following task:
|
|
Constructing the package execution JCL.
|
|
Freezing all the package components.
|
|
Notifying package approvers
|
==========================================================================
While this wait panel is displayed, Change Man is doing the following:
Checks to make sure ALL the components in your Change Package are in ACTIVE
status. If yes, then it changes the status of ALL package components to FROZEN status.
Creates the .X package staging library that contains the installation and backout batch
jobs.
Notifies the package approvers of the change in status by sending them a message,
typically an MVSSEND message.
119
Freeze
Select option 2 from the Primary Option Menu for Freeze, then select option 3
from the Freeze Options panel and press ENTER.
PACKAGE CATEGORY
STATUS
FUNCTION
_ General
FROZEN
_ Non-Source
FROZEN
_ Source and Load
FROZEN
_ Utilities
FROZEN
_ Onsite
FROZEN
_ Custom Forms
FROZEN
****************************** Bottom of data ********************************
Enter the unfreeze/refreeze option you want to execute beside the package category and
press ENTER.
Press PF3 or enter END or CANCEL in the Command line and press ENTER.
Change Man will return you to the previous panel.
Field
Description
LCMD (first
column)
Field
Freeze
Description
120
PACKAGE CATEGORY
STATUS
FUNCTION
Freeze a Change Package using the online process. Once complete, go back and
view the status of each component in your package. Also notice the package
status. Review the package staging libraries, specifically the .X file.
121
Freeze
Freeze
122
Promote
Promote/Demote Overview
Promotion is the process of moving changes through specific environments for various test
requirements, such as Unit, System, and Acceptance testing. Demotion is the process of deleting
components from these environments, usually because errors have been found during testing.
The testing environments are application specific libraries and/or common libraries shared by
multiple applications. The Change Man Administrators define the library types that may be
promoted, and the actual library names.
Change Man Administrators determine the promotion/demotion mode (online or batch), and the
promotion/demotion rule which defines the steps that must be taken within the Change Package
Life Cycle.
Change Man also checks the test environment for components that match the components being
promoted. If there are matches then Change Man will inform you of the potential overlay. When
a component is promoted to a new level, the previous level's libraries are cleaned up.
Promotion of DB2 or CICS components must be in batch for BINDS and NEWCOPY.
Select option 3 from the Primary Option Menu for Promote and press ENTER.
You will first be presented with the following panel, which you use to change or confirm the
package ID shown is the package you want to promote or demote.
CMNPRM00 ------------------- PROMOTE CHANGE PACKAGE -------------------------COMMAND ===>
PACKAGE ID ===> TEST000074
Press ENTER to process; Enter END command to exit.
123
Promote
CREATOR: WSER92
STATUS: DEV
===> _
===> O
===> 1
Press PF3 or enter END in the Command line and press ENTER. Change Man will
return you to the previous panel.
Field
Description
MAXIMUM PROMOTION LEVEL Informs you what the last promotion available
promotion level is.
Promote
ACTION REQUESTED
ONLINE OR BATCH
Field
Description
124
LEVEL TO CHECK
PROMOTION/DEMOTION
This panel appears automatically after you enter P on the Promote Change
Package panel.
CREATOR: WSER92
STATUS: FRZ
STAGING - 0
PROMO2 - 2
Press PF3 or enter END in the Option line and press ENTER. Change Man will return
you to the previous panel.
125
Promote
Field
Description
OPTION
JOB STATEMENT
INFORMATION
This panel appears automatically after you enter D on the Promote Change
Package panel.
CREATOR: WSER92
STATUS: FRZ
===> 1
Promote
126
Press PF3 or enter END in the Option line and press ENTER. Change Man will return
you to the previous panel.
Field
Description
OPTION
JOB STATEMENT
INFORMATION
CREATOR: WSER92
STATUS: DEV
127
Promote
Promote
Exercise #1:
Create a Change Package with a SRC program, make a change to the source
program and complete the compile and link process. Then do a Full Promote to
the first available promotion level. Do the promote in online mode.
Exercise #2:
Use the same package as in exercise #1 to demote the same source program
from the first promotion level. Use the Selective demotion.
Exercise #3:
Create a Change Package with 2 SRC programs, make a change to both source
programs and complete the compile and link process. Then do a Full Promote to
the first available promotion level. Then do another Full Promote to the next
promotion level. Now Demote 1 of the programs, make another change to the
program (in Stage) and finally do a Selective promote of the program back to the
first promotion level.
128
Approve
Approve Overview
The Approval function is a very important process in the Change Package Life Cycle. Approval
is where your package is checked or reviewed for the last time prior to bring installed into
production. There may be several approvers required to review and approve your package. Once
the final approver approves your package, the install process will start. Also the Package status
changes from FRZ to APR (approved).
Once a Package is frozen, designated approvers may be notified via TSO (or another notification
vehicle) that a Change Package is awaiting approval. This section details what must be done in
order to approve or reject a Change Package.
Select option 4 from the Primary Option Menu for Approve and press ENTER.
===>
===>
===>
===>
===>
===>
===>
(1-Simple, 2-Complex,
3-Super, 4-Participating)
(Planned or Unplanned)
(Permanent or Temporary)
(YYYYMMDD)
(YYYYMMDD)
(YYYYMMDD)
(YYYYMMDD)
(Y/N)
129
Approve
Approve
Enter the required fields and press ENTER, or enter blanks and work with the selection
lists.
Press PF3 or enter END in the Command line and press ENTER. Change Man will
return you to the previous panel.
Field
Description
PACKAGE ID
NOTIFIED USER ID
WORK REQUEST ID
DEPARTMENT
PACKAGE LEVEL
PACKAGE TYPE
OTHER PARAMETERS
130
The results of the Approve Package Parameters might generate more than 1 Change Package.
The following panel is an example of this;
CMNAPPL1 -------------------- APPROVE PACKAGE LIST ---------- ROW 1 TO 3 OF 3
COMMAND ===>
SCROLL ===> PAGE
PACKAGE ID STA INSTALL
LVL TYPE
DEPT
PROMOTION
AUD CREATOR
_ TEST000067 FRZ 19981230
SMPL PLN/PRM DDDD
WSER92
_ TEST000074 FRZ 19981230
SMPL PLN/PRM DDDD
01 PROMO1
WSER92
_ TEST000093 FRZ 19981230
SMPL PLN/PRM DDDD
WSER92
****************************** Bottom of data ********************************
To select the Change Package you want to work with enter S beside the package ID.
This panel will appear automatically after the Approval Package Parameters or the
Approve Package List Panels.
Approve
Reasons
Query
Reset
STATUS: FRZ
Enter the requested action in the Option line and press ENTER.
Press PF3 or enter END in the Option line and press ENTER. Change Man will return
you to the previous panel.
131
Approve
Field
Description
OPTION
Enter option 3 from the Approve/Reject Options panel and press ENTER.
STATUS: FRZ
AUDIT RC:
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
Approve
132
ROW 1 TO 18 OF 19
SCROLL ===> PAGE
Press PF3 or enter END or CANCEL in the Command line and press ENTER.
Change Man will return you to the previous panel.
Field
Description
Select option 1 from the Approve/Reject Options panel and press ENTER.
STATUS: FRZ
APPROVER DESCRIPTION
Press PF3 or enter END or CANCEL in the Command line and press ENTER.
Change Man will return you to the previous panel.
Field
Description
133
Approve
DATE/TIME
SEQ
STATUS
Once the last approver approves the Package the Package is ready for the installation process. If
the Scheduler selected was Manual then the Package will be installed right after the last
approver has approved the package. If the scheduler was CMN then the package will be
installed at the specified date and time. Once the final step of the install has occurred Change
Man will notify you by sending the following message:
CMN405I - USER000095 BASELINE RIPPLED 1999/01/06 @ 10:20:36. CN(INTERNAL)
***
Once you see this message the Package has been installed into production and the Baseline
Ripple process has completed. The Package status has also changed from APR to BAS
(Baselined).
Approve
Select option 2 from the Approve/Reject Options panel and press ENTER.
134
CMNREJR1--------------------COMMAND ===>
REJECT REASONS
STATUS: FRZ
Press PF3 or enter END in the Command line and press ENTER. Change Man will
return you to the previous panel.
Field
Description
135
Approve
Approve
Exercise #1:
Exercise #2:
136
List
List Overview
Change Man uses menu driven panels to allow the user to navigate throughout the Change Man
system or to select the functions they want to perform. The List function provides an alternative
way of navigating throughout the Change Man system or selecting functions to be processed. A
major benefit of the List function is that it provides all the Change Man functions to be accessed
from one central location. Once most users become familiar with the Change Man functions and
processes, they usually switch from the menu driven navigation method to the List function
method.
In the List function you can list all the Change Packages in the system, or you can specify
"search" criteria that allows you to list only those Change Packages that meet the search criteria.
From these resultant package lists, you can perform almost any Change Man function you want,
like:
137
List
Select option 5 from the Primary Option Menu for List and press ENTER.
===>
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
===>
===>
===>
===>
===>
===>
===>
(1-Simple, 2-Complex,
3-Super, 4-Participating)
(Planned or Unplanned)
(Permanent or Temporary)
(YYYYMMDD)
(YYYYMMDD)
(YYYYMMDD)
(YYYYMMDD)
(Y/N)
List
Press PF3 or enter END or CANCEL in the Command line and press ENTER.
Change Man will return you to the previous panel.
138
Field
Description
PACKAGE ID
PACKAGE STATUS
CREATOR'S TSO ID
viewed.
WORK REQUEST ID
DEPARTMENT
PACKAGE LEVEL
PACKAGE TYPE
OTHER PARAMETERS
139
List
Appears automatically after pressing enter from the Package List Parameters panel.
Enter the package function beside the Package ID and press ENTER.
Press PF3 or enter END or CANCEL in the Command line and press ENTER.
Change Man will return you to the previous panel.
Field
List
Description
140
Line Commands
PACKAGE ID
STA
INSTALL
LEVEL
TYPE
WORK REQUEST
DEPARTMENT
PROMOTION
AUD
The return code from the most recent Change Man Audit
job for the Change Package.
CREATOR
Note: Of all the 38 possible Package Line commands, there is NO command to CREATE a new
package. The reason for this is how can you enter the create package command on a package
that already exists. However you still can perform the CREATE new package function by
entering CR on the Command line of this panel. Once entered you will go directly to the
Create New Package panel.
141
List
List
142
Exercise #1:
Using only the Package List feature, display a list of all the Change Packages in
an application.
Exercise #2:
Using only the Package List feature, display a list of all the Change Packages in
an application that are in DEV status and that were created by your Userid.
Exercise #3:
Using only the Package List feature, create a new package, checkout a SRC
component, edit/stage the component and run audit on this new package.
Exercise #4:
Using only the Package List feature to display all the packages in DEV status
and perform the freeze function on one of these packages.
143
List
List
144
Delete
Delete Overview
The Delete function is used to delete Change Packages that are no longer required. The Delete
function has 2 steps in its process. The first step is to mark the Change Package for deletion, or
flag the Package as Memo Deleted. This is a logical delete, which is accomplished by
completing the Delete panel process (see below). The second step is the physical deletion of all
the datasets associated with the Change Package, and the deletion of all the records within the
Change Man Package Master file. The physical deletion only takes place when the REPORTS
task is executed. The REPORTS task is a Housekeeping job that is usually scheduled to run once
a day. Typically it runs in the middle of the night when Change Man is down. A Package to be
deleted through this function must be in DEV status.
The UNDELETE function is used to remove a change package from a MEMO DELETE
status. This option can be used up until the time that the REPORTS job has run. Check with
your Change Man administrator to determine when package aging occurs against the package
master.
Select option D from the Primary Option Menu for Delete and press ENTER
Delete
- Memo delete a change package
Undelete - Restore memo deleted change packages
Press PF3 or enter END in the Option line and press ENTER. Change Man will return
you to the previous panel
145
Delete
Field
Description
OPTION
Select option 1 from the Delete Options panel and press ENTER
===> TEST000078
===> YES
(Y/N)
Delete
Press PF3 or enter END in the Command line and press ENTER. Change Man will
return you to the previous panel
Field
Description
PACKAGE ID
CONFIRM REQUEST
146
If you enter YES for the Confirm Request field, then Change Man will display the
following panel:
CMNDELT2 ----------------------- CONFIRM DELETE -----------------------------COMMAND ===>
PACKAGE ID:
TEST000078
STATUS:
DEV
INSTALL DATE: 19981230
Press ENTER to confirm delete request.
Enter END command to cancel delete request.
Press PF3 or enter END in the Command line and press ENTER. Change Man will
return you to the previous panel
If you press ENTER to process the Memo Delete request, then Change Man will display the
following panel:
CMNDELT1 ----------------- MEMO DELETE CHANGE PACKAGE --- PACKAGE MEMO DELETED
COMMAND ===>
PACKAGE ID
CONFIRM REQUEST
===> TEST000078
===> YES
(Y/N)
This panel informs you that the Memo Delete request has been processed, which means the
Change Package has been marked for deletion. The Package status also changes from DEV to
DEL.
147
Delete
Select option 2 from the Delete Options panel and press ENTER
Press PF3 or enter END in the Command line and press ENTER. Change Man will
return you to the previous panel.
Field
Description
PACKAGE ID
PACKAGE ID
TEST000078
TEST000088
TEST000089
STATUS
From this list you can enter U beside the Package(s) you want to Memo Undelete.
Delete
148
If you press ENTER to process the Memo Undelete request, then Change Man will display the
following panel:
CMNDELT3 --------------- RESTORE MEMO DELETED PACKAGES ----- PACKAGE UNDELETED
COMMAND ===>
PACKAGE ID ===> TEST000078
This panel informs you that the Memo Undelete request has been processed. The Change
Package status is also changed from DEL back to DEV.
149
Delete
Delete
150
Revert
Revert Overview
After a Change Package has been Rejected, Backed out, or Frozen, it is no longer available for
any changes or modifications. If the user needs to go back and make changes to this Package,
then the package status must be changed to DEV. The Revert function is used to accomplish
this change. It will change the Change Package status from BAK, FRZ, APR or REJ to
DEV status. Once complete the entire Change Package is now available for any modifications.
The user is required to enter a revert reason describing why the change package is being reverted.
These revert reasons are available for review using the Change Man Query function.
Select option R from the Primary Option Menu for Revert and press ENTER
Press PF3 or enter END in the Command line and press ENTER. Change Man will
return you to the previous panel
Field
Description
PACKAGE ID
151
Revert
Revert
Press PF3 or enter END in the Command line and press ENTER. Change Man will
return you to the previous panel
Field
Description
152
If you press ENTER to process the Revert request, then Change Man will display the following
panel:
---------------------------- REVERT CHANGE PACKAGE ---------- PACKAGE REVERTED
COMMAND ===>
PACKAGE ID ===> TEST000074
Press ENTER to process; Enter END command to exit.
This panel informs you that the Revert request has been processed. The package status has also
been changed from FRZ, APR, REJ or BAK back to DEV.
153
Revert
Revert
154
Backout
Backout Overview
The backout function allows you to "de-install" a Change Package after the package has been
installed into the production environment and baseline rippled. Change Man will back out the
entire Change Package during the Backout process, i.e.: SRC, LOD, LST, JCL, PRC, etc.
Once a Change Package has been backed out, the Package will be in BAK status. You must
use the Revert function to get the Change Package back to DEV status before you may begin
working on it again.
If you have remote sites, you must initiate the Backout at the remote site(s). Once the remote
sites have been backed out the "reverse ripple" will occur in the development site.
Select option B from the Primary Option Menu for Backout and press ENTER
Press PF3 or enter END in the Command line and press ENTER. Change Man will
return you to the previous panel
Field
Description
PACKAGE ID
Backout
Use this panel to enter the reasons why you backed out the Change Package.
This panel will appear after the Backout Change Package panel.
CMNBKRSN ---------------------- BACKOUT REASONS -----------------------------COMMAND ===>
PACKAGE ID: TEST000052
CREATOR: WSER92
STATUS: BAS
BACKOUT REASONS:
===> Job abended as a result of poor testing. Need to make additional changes.
===>
===>
===>
===>
===>
===>
===>
===>
Press ENTER to process; Enter END or CANCEL command to exit.
Press PF3 or enter END or CANCEL in the Command line and press ENTER.
Change Man will return you to the previous panel
Field
Description
Once you enter the backout reason and press ENTER, Change Man will immediately submit the
backout jobs. Change Man will advise you it has submitted the job by displaying a Backout Job
Submitted message on the panel you return to.
----------------------------- CHANGE PACKAGE LIST ------ BACKOUT JOB SUBMITTED
COMMAND ===>
SCROLL ===> PAGE
PACKAGE ID STA INSTALL LVL TYPE
WORK REQUEST DEPT PROMOTE AUD CREATOR
__ TEST000095 BAS 19990106 SMPL PLN/PRM AAAAAAAAAAAA DDDD
WSER92
******************************* Bottom of data *******************************
or
Backout
156
Build
Freeze
Promote
Approve
List
Admin
Backout
CDF
Delete
Log
Monitor
Notify
OFMlist
Query
Revert
Tutorial
Exit
Change Man will also notify you the result of the backout jobs by sending you the following
MVS Send messages:
CMN406I - USER000095 BACKED OUT 1999/01/06 @ 10:34:09. CN(INTERNAL)
CMN410I - USER000095 BASELINE REVERSE RIPPLED 1999/01/06 @ 10:34:09. CN(INTERNA
L)
***
This panel informs you that the Backout request has been processed successfully. The Change
Package status is also changed from BAS back to BAK.
157
Backout
Backout
158
Browse
Browse Overview
The Browse\Print\Copy facility allows the Change Man user the option of displaying or printing
any component managed by Change Man, without having to Checkout the component or enter a
valid Change Package. You can view the contents of any component in the current (0) or backup
(-1) baseline libraries, or promotion (+1) libraries. This facility provides for member level
security checks prior to allowing the user to display or print the member, thus ensuring data
integrity.
Other features of this option include giving the authorized user the ability to copy a component to
a user specified dataset, to perform a rename prior to the copy to a user specified dataset, and to
fully expand copy and include statements prior to printing.
Select option 1 from the Primary Option Menu for Build, then Select option B on
the Build Options Menu for Browse.
X - Print expanded
APPLICATION
LIBRARY TYPE
LIBRARY LEVEL
COMPONENT NAME
===> TEST
===> SRC
===> 0
===>
===>
===>
===>
===>
===>
DATA STRING
===>
N
0
N
0
0
Browse
Browse
Enter the required fields and press ENTER to proceed to next panel, or leave some of
the fields blank and select from the resultant lists.
Press PF3 or enter END on the Option line and press ENTER, Change Man will return
you to the previous panel.
Field
Description
OPTION
APPLICATION
LIBRARY TYPE
Enter the library type of leave blank to select from the library
type list.
LIBRARY LEVEL
COMPONENT NAME
Field
Description
160
RECORDS TO SELECT
search criteria.
CASE SENSITIVE
FROM COLUMN
Enter the column, for each record, where you want the scan to
begin. Enter 0 if you want the scan to begin in column 1.
TO COLUMN
Enter the column, for each record, where you want the scan to
end. Enter 0 if you want the scan to end in column 80.
DATA STRING
161
Browse
Browse
162
Recompile
Recompile Overview
The recompile function can be used to resolve some of the out-of-synch conditions that can occur
from the Audit process. For example, if you checked out and edited a copy component while
other source components (not in the Change Package) also use this copy, you would receive an
out-of-synch condition (SYNCH5!) when an Audit is performed . To resolve this, you would
need to recompile those modules that were deemed to be out-of-synch.
This function is similar to staging except that the source is not included in the Change Package.
Only the resulting load module is placed into the Change Man Change Package.
Select option 1 from the Primary Option Menu for Build, then Select option 8 on
the Build Options Menu for Recompile.
===>
===>
===>
===>
===>
===>
TEST000074
SRC
ASM
0
1
163
Recompile
Enter the required fields and press ENTER to proceed to next panel, or leave some of
the fields blank and select from the resultant lists.
Press PF3 or enter END on the Option line and press ENTER, Change Man will return
you to the previous panel.
Field
Description
OPTION
PACKAGE ID
COMPONENT NAME
LANGUAGE
LIBRARY LEVEL
RECOMPILE MODE
Recompile
164
STATUS: FRZ
COMPONENT:
LIBRARY TYPE:
LANGUAGE:
DATASET NAME:
AAADB2SQ
SRC - Source Code
ASM
WSER200.BASE.ZERO.SRC
COMPILE PROCEDURE
COMPILE PARMS
LINK EDIT PARMS
DB2 PRE-COMPILE
OTHER OPTIONS
SUPPRESS HISTORY
===>
===>
===>
===> NO
===> YES
===> YES
Field
Description
PACKAGE ID
STATUS
INSTALL DATE
COMPONENT
LIBRARY TYPE
LANGUAGE
165
Recompile
Field
Description
DATASET NAME
The name of the dataset that contains the component that you are
staging. This will either be a Change Man package staging library or a
development library.
COMPILE
PROCEDURE
COMPILE PARMS
You may type in compile parms for the program. If this program was
previously compiled within Change Man, the compile parms found in
component history will be displayed.
LINKAGE EDIT
PARMS
You may type in link edit parms for the program. If this program
was previously linked within Change Man, the link edit parms found in
component history will be displayed.
OTHER OPTIONS
Enter "YES" if you need to display additional user options such as CICS
pre-compile, EZTRIEVE, etc. Your Global Change Man Administrator
will define available options for you.
SURPRESS
HISTORY
Recompile
166
167
Recompile
Recompile
168
Relink
Relink Overview
Any time a statically linked subroutine has been modified, relinking is required. Use this function
to relink load modules or to delete a relinked or recompiled load module from your Change
Package. The Relink function links a member using LCT images supplied by the user or are
created by Change Man if no LCT cards are supplied. A relink target load library to which the
member is to be relinked must be specified.
Select option 1 from the Primary Option Menu for Build, then Select option 9 on
the Build Options Menu for Relink.
===> TEST000063
===>
(S-Staging or B-Baseline)
===>
(Y - Yes or N - No; member list will
be created with input library type)
INPUT LIBRARY TYPE
===>
(Blank for list)
TARGET LIBRARY TYPE ===>
(Blank for list)
MEMBER NAME
===>
(Blank for list; required for option R)
COMPILE PROCEDURE
===>
(Blank for list)
LINK EDIT PARMS
===>
DB2 PRE-COMPILE
===>
(Y/N)
OTHER OPTIONS
===> YES
(Y/N for additional user options)
JOB STATEMENT INFORMATION:
===> //WSER92N JOB (XXXX,333),WSER92,CLASS=E,MSGCLASS=3,____________________
===> //
TIME=2,REGION=4M,NOTIFY=WSER92________________________________
===> //*JOBPARM SYSAFF=ESA1__________________________________________________
===> //*_____________________________________________________________________
Press ENTER to process; Enter END command to exit.
169
Relink
Enter the required fields and press ENTER to proceed to next panel, or leave some of
the fields blank and select from the resultant lists.
Press PF3 or enter END on the Option line and press ENTER, Change Man will return
you to the previous panel.
Field
Description
OPTION
PACKAGE ID
RELINK FROM
LCT MEMBER LIST Enter Y if the LCT library member list is to be created. Enter N
if the LCT library member list is not to be created. Member list that
will be created will be from the INPUT LIBRARY TYPE field below.
INPUT LIBRARY
TYPE
TARGET LIBRARY Specify the library type of the load module being relinked. Leave
TYPE
blank for a member selection list.
MEMBER NAME
Enter the member name to be processed. Leave this field blank or enter a
pattern to generate a list from which a member may be selected
COMPILE
PROCEDURE
LINKAGE EDIT
PARMS
You may type in link edit parms for the program. If this program
was previously linked within Change Man, the link edit parms found in
component history will be displayed.
DB2 PRE-COMPILE Enter "YES" if this program is a DB2 program. Enter "NO" if this
program is not a DB2 program.
Relink
DATASET NAME
The name of the dataset that contains the component that you are
staging. This will either be a Change Man package staging library or a
development library.
OTHER OPTIONS
Enter "YES" if you need to display additional user options such as CICS
pre-compile, EZTRIEVE, etc. Your Global Change Man Administrator
will define available options for you.
170
Exercise #1:
Exercise #2:
Use the Relink Process to delete the load module that was recompiled from the
recompile exercise.
171
Relink
Relink
172
Query
Query Overview
Change Man provides you with ability to Query packages and their components so that you can
access general and detailed information. You can use this information in conjunction with the
activity log (if you have log security access) to display information on all of the activities of
Change Man at your site.
Managers, application leaders, operations personnel, and any concerned parties may wish to sign
on to Change Man to query packages and components. Approvers may often use this function to
review the package prior to Approving or Rejecting it. Operations personnel monitor package
Distribution, Installation and Rippling of Baseline, and depending on the scheduling system used
at your site, operators may need to sign on to Change Man to review predecessor/successor job
names as well as other information associated to a change package.
Information for the Query function is being gathered from the Package Master and is a record of
all the packages where the component resides.
Select option Q from the Primary Option Menu for Query and press ENTER
Package
- Query package information
Component - Query component information
Impact
- Impact analysis of component relationships
Enter the required request on the Option line and press ENTER to proceed to next panel
Press PF3 or enter END on the Option line and press ENTER, Change Man will return
you to the previous panel.
Field
Description
173
Query
OPTION
Select option P from the Query Options panel and press ENTER
===>
CREATOR'S TSO-ID
WORK REQUEST ID
DEPARTMENT
REMOTE SITE AFFECTED
PACKAGE LEVEL
===>
===>
===>
===>
===>
PACKAGE TYPE
PACKAGE TIME SPAN
FROM INSTALL DATE
TO INSTALL DATE
FROM CREATION DATE
TO CREATION DATE
OTHER PARAMETERS
===>
===>
===>
===>
===>
===>
===>
(Full name
or '*' to
(DEV, FRZ,
BAS, BAK,
(1-Simple, 2-Complex,
3-Super, 4-Participating)
(Planned or Unplanned)
(Permanent or Temporary)
(YYYYMMDD)
(YYYYMMDD)
(YYYYMMDD)
(YYYYMMDD)
(Y/N)
Enter the required fields and press ENTER to proceed to next panel
Press PF3 or enter END on the Command line and press ENTER, Change Man will
return you to the previous panel.
Field
Query
Description
174
PACKAGE ID
PACKAGE STATUS
CREATOR'S TSO ID
viewed.
WORK REQUEST ID
DEPARTMENT
PACKAGE LEVEL
PACKAGE TYPE
OTHER PARAMETERS
===>
===>
===>
===>
(Y/N)
(Y/N)
(Y/N)
(Y/N)
Field
Description
175
Query
NON-SOURCE
RENAME/SCRATCH
INFORMATION
CUSTOM COMPONENT
STATUS: DEV
AUDIT RC:
ROW 1 TO 18 OF 19
SCROLL ===> PAGE
_ 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 ******************************
Query
176
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
(S-Short, L-Long)
(YYYYMMDD)
(YYYYMMDD)
Enter the required fields and press ENTER to proceed to next panel
Press PF3 or enter END on the Command line and press ENTER, Change Man will
return you to the previous panel.
Field
Description
COMPONENT NAME
COMPONENT TYPE
APPLICATION
PACKAGE ID
PROCEDURE NAME
177
Query
TSOID
Enter the TSO ID for the user who last update to the
component(s).
WORK REQUEST ID
DISPLAY MODE
RCHECKOUT / STAGING
FROM DATE
TO DATE
Select option I from the Query Options panel and press ENTER
Enter the required fields and press ENTER to proceed to next panel
Press PF3 or enter END on the Command line and press ENTER, Change Man will
return you to the previous panel.
Field
Query
Description
178
COMPONENT NAME
COMPONENT TYPE
APPLICATION
RELATIONSHIP
RELATIONSHIP TO
179
Query
Query
Exercise #1:
Use the Query function to view all packages that are in FRZ status for any
application. Then select one of the packages from the resultant Package List and
view the Approval List for it.
Exercise #2:
Use the Query function to view a JCL component, to see in how many packages
it currently exists. You might need to search the baseline JCL library for a valid
component name.
180
Compare
Compare Overview
The compare function is used to produce a difference report describing the modifications to
components within a change package using the application's Baseline or Promotion libraries as a
reference. For example, if a change package was created in March and installation was delayed
for six months, the user may want to review the changes made before resuming the installation
process.
Compares can be executed in either online or batch mode. The online portion is executed
through the CMNCDCPR program. All the parameters that the program uses are hardcoded
within the load module itself. Program SERCOMPR controls the compare function that executes
the CMNCDCPR program. The batch portion is executed through the CMN$$CPR skeleton.
COMPARE Panel
You can use this panel to enter which component you want to run the compare function on.
To access this Panel:
Select option 1 from the Primary Option Menu for Build, then Select option C on
the Build Options Menu for Compare.
===>
===>
===>
===>
===>
O
USER000093
JCL
0
(O-Online; B-Batch)
(* for all members; blank for list)
(Blank for list)
(Baseline 0 to -n; Promotion +1 to +n)
(Y/N)
Compare
Enter the required fields and press ENTER to proceed to next panel, or leave some of
the fields blank and select from the resultant lists.
Press PF3 or enter END on the Command line and press ENTER, Change Man will
return you to the previous panel.
Field
Description
OPTION
COMPARE MODE
PACKAGE NAME
COMPONENT NAME
LIBRARY TYPE
SOURCE LIBRARY
Compare
182
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.
Exercise #2:
Run the compare function on the same component, but this time use a promotion
library.
183
Compare
Compare
184
Scan
Scan Overview
The Library Scan facility enables you to perform a quick impact analysis without using the
Impact Analysis utility. With this scan utility, you can search the Baseline level 0 libraries for
any of the following:
For a character string search, you can specify two (2) data strings. The second data
string can be either AND or OR with the first data string.
For a dependency search, you scan for copybooks, dates, names, calls, programs
executed, procedures and various other types of dependencies that are associated
with the scanned members.
When you request a scan, Change Man displays a table showing the records found and where
they appear. Be aware that you cannot perform any actions on the items in the list.
Note: This function does not impact the Baseline Browse scan.
Select option 1 from the Primary Option Menu for Build, then Select option S on
the Build Options Menu for Scan.
185
Scan
===>
===>
===>
===>
===>
RECORDS TO SELECT
CASE SENSITIVE?
DISPLACEMENT: FROM
TO
COMPONENTS TO SCAN:
BEGIN
END
===>
===>
===> 0
===> 0
DATA STRING 1
AND/OR
DATA STRING 2
===>
===> OR
===>
SRC
O
NO
NO
===>
===>
Scan
Enter the required fields and press ENTER to proceed to next panel, or leave some of
the fields blank and select from the resultant lists.
Press PF3 or enter END on the Command line and press ENTER, Change Man will
return you to the previous panel.
Field
Description
APPLICATION
LIBRARY TYPE
SCAN MODE
186
Field
Description
DEPENDENCIES
RECORDS TO SELECT
CASE SENSITIVE?
DISPLACEMENT
COMPONENTS TO SCAN
DATA STRING 1
AND/OR
Enter 'AND' if both the first and second strings are to be found
on one line of the member scanned.
Enter 'OR' if the scan is to contain either the first or second
string within the scanned member.
DATA STRING 2
Enter a second character string. Imbedded blanks or nonalphabetic characters will be searched for in place. To include
leading or trailing blanks, enclose the string in apostrophes (').
187
Scan
Exercise #1:
Scan
Use the Scan function to scan for character new in the JCL library type. Scan
in online mode, between columns 5 to 72, with no case sensitivity and select all
the records.
188
Compress
Compress Overview
When you Create a change package, the associated Staging libraries are empty. As the package
goes through its life cycle, you populate the libraries with updated components. As testing
proceeds with the package, you often Re-stage many of the components, eventually causing the
Staging libraries to become full. You can use the compress function to compress the partitioned
datasets (Staging libraries) associated with change packages. Since partitioned datasets do not
reuse space when you make deletions and updates, you may have to compress the Staging
libraries to reclaim the "dead space".
Select option 1 from the Primary Option Menu for Build, then Select option Z on
the Build Options Menu for Compress.
Enter the required fields and press ENTER to submit the batch job.
Press PF3 or enter END on the Command line and press ENTER, Change Man will
return you to the previous panel.
Field
Description
189
Compress
PACKAGE ID
Exercise #1:
Compress
Run a compress on the last change packages you were working on.
190
Log
Log Overview
Change Man has a log which records all of the Change Man activities at your site. Nearly all
user activities are logged, as well as some behind the scene activities that Change Man performs.
You can also browse the Activity Log for audit return codes on all packages.
(YES-online; NO-batch)
(YYYYMMDD, optional)
(YYYYMMDD, optional)
IND
LOG DESCRIPTION
******************************** TOP OF DATA *********************************
_
01
Backout a Package
_
02
Install a Package
_
03
Temporary Change Cycle
_
04
Distribute a Package
_
05
Unauthorized Member Access
_
06
Invalid Compiling Procedure
_
07
Invalid Designate Remote Sites
_
08
Delete a Package
_
09
Generate Application Information
_
10
Revert a Package
_
11
Generate Global Information
_
12
Activate a Component
_
13
Package Memo Delete
_
14
Undelete a Package
_
15
Baseline Ripple
191
Log
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, 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
(YES-online; NO-batch)
(YYYYMMDD, optional)
(YYYYMMDD, optional)
IND
LOG DESCRIPTION
_
86
Delete Module From Package
_
88
Copy Forward a Package
_
90
Monitor Limbo and internal scheduler
******************************* BOTTOM OF DATA *******************************
Log
Enter the required fields and press ENTER to submit the batch job.
Press PF3 or enter END or CANCEL on the Command line and press ENTER,
Change Man will return you to the previous panel.
Field
Description
ONLINE BROWSE
192
FROM DATE
TO DATE
LOG DESCRIPTION
Change Man will display the following panel while the search is being processed.
CMNLOGWT ------------------------ IN PROGRESS -------------------------------
Exercise #1:
Run an online log browse on the Baseline Ripple category on the entire log file.
193
Log
Glossary
Application ID
Application ID is used to identify a project within Change Man. Applications / Projects are defined groups for which Change
Packages are to be created and manipulated. Usually a four-character code is assigned to a specific Application. They are used to
identify package ownership.
Approval
The process whereby Change Packages are approved by designated individuals prior to installation into baseline / production.
Audit
A Change Man utility that, in addition to other functions, inspects the Staging libraries for any out-of-synch conditions, source to
load integrity, etc.
Audit Lite
A subset of the Audit utility, it inspects the staging libraries of a Change Package for discrepancies between package components.
Baseline Library
A Change Man library which stores the most current version (0) of production components, in addition to a pre-defined number of
previous versions (-1, -2, etc.).
Baseline Ripple
The process whereby a component becomes the new production component, the previous production component becomes the 1
version, -1 becomes 2, and so on.
This process is called baseline ripple. The baseline ripple starts with the oldest baseline library and works its way back to the most
current library.
Change Package
Within Change Man, a Change Package is the vehicle in which all changes are moved from a development environment to a
production environment. Change Packages may contain one or more components, which are required for a change.
Compile
The process of transforming source into object format.
Component
A single member of a Change Package. Usually, a member of a library that has been brought into Change Man for the purpose of
being modified. The component could be a source module, load module, PROC, JCL, copybook, DDL, datalib member etc.
Demotion
The process whereby components are removed from promotion libraries.
Development/Personal Library
Any library, other than Change Man or production libraries, in which a component resides.
Freeze
The act of locking Change Packages so that modifications are prohibited. It also makes a package eligible for approval.
Global Parameters
These parameters are defined in the initial Change Man setup to tailor Change Man to your data center environment. They are
modifiable at any time by the Global Administrator.
Installation
Installation is the final process in the Change Package Life Cycle. It is the process that does the final copy from the Package Staging
libraries into the baseline/production libraries.
Library Type
A three character identifier which represents the various component types in an application. Source components have library type of
SRC, copybook components use CPY, load modules use LOD, etc.
Local Parameters
These parameters are defined within the initial setup of each Change Man Application (project). They will assist in tailoring each
separate application according to their individual needs.
Mass Stage
The process of staging a multiple number of components into a Change Package. This facility moves the processing for a set of
staging requests to a batch job. This job will spawn and submit an individual batch job for each stage request.
Package ID
Each Change Package is automatically assigned a unique package ID. Consisting of the Application ID and a sequential number (e.g.
PAYR000001).
Package Master
The repository for all Change Man information, including package definitions, components, administration information, and so on. It
is typically a VSAM file.
Permanent Package
A type of Change Package that is used to hold components that will be installed into the baseline libraries. Permanent packages
usually go through all the processes in a Package Life Cycle.
Planned Package
A type of Change Package which is created during normal business hours in a non-emergency situation. Its Installation is subject to
the complete approval list
Production Library
The library that contains all production versions of each component. Separate library types may utilize separate production libraries.
Project
Synonymous with the term "application". Applications are defined groups for which Change Packages are to be created and
manipulated.
Promotion
A pseudo-production environment that allows for a variety of testing. Also, it is the act of copying a component from staging to a
promotion environment or level.
Relink
The process of transforming object code into an executable load module.
Stage
This function is used to copy components from development or personal libraries into Change Man Staging libraries. If the
component is source (SRC), there is a second Staging step which compiles, link/edits, binds, etc. the component into an executable
load module. Stage is also the function that you use to make changes or modifications to the components.
Staging Library
Change Man libraries in which components are stored, and can be modified and tested. From these libraries, the component is
installed.
Temporary Package
A type of Change Package that is used for temporary fixes or changes which the user does not want to install into the baseline
libraries. Typically components of a temporary package will be installed into a special library used to hold temporary fixes.
Temporary Packages are usually created in conjunction with Unplanned Package, which do not need to go through all the processes
in a Package Life Cycle.
Unplanned Package
A type of Change Package which is created for an emergency situation. Often created outside of normal business hours. If an
Unplanned Package is created during normal business hours it is treated as a Planned Package and is subject to the complete Package
Life Cycle and Approval list. If created outside of regular business hours, then not all Package Life Cycle processes are required and
usually there is an abbreviated approval list. Its installation date is not dependent on the Planned Installation calendar.