Change Man

Change Man

CHANGE MAN

Table of contents 1 What is a Change Man:.............................................................................................................................2 2 What is a Change Package:.......................................................................................................................2 3 Invoking Change Man:.............................................................................................................................2 4 Different Stages in Maintaing Programs in Change Man :.......................................................................2 4.1 Create a Change Man Package :..........................................................................................................................................4 4.1.1 Package General Information Menu.............................................................................................................................4 4.1.2 Package General Description Panel..............................................................................................................................6 4.1.3 Package Installation Instructions..................................................................................................................................6 4.1.4 Scheduling Dependencies.............................................................................................................................................6 4.1.5 Remote Site Information..............................................................................................................................................7 4.1.6 Create Super/Complex Package...................................................................................................................................7 4.1.6.1 Affected Applications panel ..................................................................................................................................7 4.1.6.2 Complex/Super Information panel........................................................................................................................7 4.2 Staging a Component in the Change Package.....................................................................................................................7 4.3 Compile the programs after the changes...........................................................................................................................10 4.4 Audit the package..............................................................................................................................................................11 .............................................................................................................................................................................................12 4.5 Promote the Package.........................................................................................................................................................12 4.6 Freeze the package............................................................................................................................................................12 4.7 Baseline the package.........................................................................................................................................................12

5 Other Stages in Maintaing Components in Change Man :.....................................................................13 5.1 Updating Change Package Information:...........................................................................................................................13 5.2 Checking Out a Component:.............................................................................................................................................13 5.3 Comparing Staging Libraries to Baseline/Promotion Libraries:.......................................................................................13 5.4 Approving or Rejecting a Component:.............................................................................................................................13 5.5 Package Functions:............................................................................................................................................................13 5.5.1 Package Query Functions:..........................................................................................................................................15

6 Change Man Screens :............................................................................................................................16 6.1 Screen 1 : Change Man Primary option menu:.................................................................................................................16 6.2 Screen 2 : Change Man Build Options menu:...................................................................................................................16 6.3 Screen 3 : Package List Parameter...................................................................................................................................17 6.4 Screen 4 : Change Package List.......................................................................................................................................17

Page 1 of 17

Change Man

1 What is a Change Man: Change Man a product of Serena Software International, is a Configuration Management Tool used to manage the process of moving application software from a development environment to a production environment. All the information needed to install a particular change into the production environment is grouped together to form a Change Package. Change Man does its job by managing the movement of change package information among five distinct environments: development, staging, baseline, production and backup. An optional sixth environment could also include a testing, or promotion environment.

2 What is a Change Package: A change package is a logical definition for the collection of items associated with a change request. The associated items include work datasets, activity records, audit records and general information that is stored and managed by Change Man. The following are provided as examples of items that managed by Change Man. The following are provided as examples of items that may be assocatied with a change package: -

Source code(Batch or Online) Load modules Maps JCL ‘s Copybooks Service Requests (i.g. dataset work space, JCL Review) Execution Documentation Package Installation Procedures Vendor Code without source.

3 Invoking Change Man: Change Man executes as a dialog under IBM's ISPF dialog manager facility.You can invoke it by selecting the Change Man option(CM) from a customized version of the ISPF primary option menu,

4 Different Stages in Maintaing Programs in Change Man : The important stages are : • Create a Change Man Package. • Staging a Program in the Change Package. • Compile the programs after the changes. • Audit the package • Promote the Package. • Freeze the package • Baseline the package.

Page 2 of 17

Change Man

CHANGE MAIN LIFE CYCLE Mutiple Site Configuaration Impact Analysis Stage

Modify

(Promote)/test

audit Freeze

Check out

(Promote)/test

Create Baseline Ripple

Un Freeze Backout

Revert

Distribute

Install backout Install

Back up

Page 3 of 17

Approve

Change Man

4.1 Create a Change Man Package : The panels you encounter during the Create process may vary, depending on the options you choose along the way.... some panels were explained below... 4.1.1 Package General Information Menu When you select Build Option 1 (Create), the Create A New Package Menu is presented. You may bypass the Build menu by specifying 1.x from the Primary Option Menu. For example: specify 1.1 to bypass the Build menu and go directly to the Create A New Package Menu. ********************************************************************** ------------------------- CREATE: CREATE A NEW PACKAGE -----------------------OPTION ===> PACKAGE TITLE ===> SR 1135 SOURCE CODE - 00i 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

===> ===> ===> ===> ===>

IACL (Blank or pattern for list) RAMESH KUMAR REDDY 973 276 4080 SR 1135 00I 1 (1-Simple, 2-Complex, 3-Super, 4-Participating) PLANNED (Planned or Unplanned) PERM (Permanent or Temporary) (Optional package name) (* for list) (In days)

Press ENTER to process; Enter END command to exit. **********************************************************************

Now we will see the different options in this menu. PACKAGE TITLE Enter free form text to identify this package. APPLICATION Enter a valid application mnemonic, as established by your Change Man Administrator. Change Man will assign a sequential number as part of the Package ID. REQUESTER'S NAME Enter up to 25 characters for the name of the person creating this package (or requesting the creation of this package).

Page 4 of 17

Change Man REQUESTER'S PHONE Enter up to 15 characters for the phone number (extension) of the person creating this change package (or requesting the creation of this package). WORK REQUEST ID This field may be required by your Administrator. Also, depending upon the INFO MANAGEMENT RULE currently in effect, this number may be tied to an INFO Change Record number. (you can enter some information like SR number or DI number) DEPARTMENT This field may be required by your Change Man Administration. ( you can enter the cycle number in this field) PACKAGE LEVEL Enter 1, 2, 3, or 4 as indicated below. If you 'copy forward' an existing change package to create this one, its 'level' will be copied also. 1

Simple

2

Complex The "parent" for two or more change packages that have interdependent changes to software and/or operational procedures. Complex change packages are comprised only of control, general, and complex/super change package info. This is not meant for installation.

3

Super

Does not require that any other application change its software or its operational procedures.

The "parent" for change packages that contain major changes to several applications. These packages have a high impact on the data processing environment as a whole. They are comprised only of control, general, and complex/super change package information.This is not meant for installation. 4

Participating One of the component change packages of either a Complex or a Super change package. Otherwise, it is much like a Simple package. A participating package is created if other packages will share components between themselves prior to production implementation. Participating packages must have a parent Complex or Super package associated with them in order to share common stage copybook and load libraries.

PACKAGE TYPE PACKAGE TYPE Enter a package type as follows: Planned Indicates that you wish to view PLANNED change packages. These are change packages that have been previously scheduled. Unplanned Indicates that you wish to view UNPLANNED change packages.

Page 5 of 17

Change Man These are packages commonly referred to as "emergencies". are unscheduled changes.

They

PACKAGE TIME SPAN Enter one of the following valid time spans: Permanent Indicates that only change packages that are to remain in production indefinitely are to be viewed. Temporary This option indicates that you wish to view only those change packages that deal with special one-time or short-term processing such as conversion, parallel processing, special reporting, or data extraction. PACKAGE TO COPY FORWARD To use a previous change package as a model for this new one, enter the ID of the previous change package to copy. UNPLANNED REASON CODE Enter the 3 digit change reason code that best represents why you are installing an unplanned change package. These codes were established by your Change Man Administration. Enter '*' for a reason code selection list. TEMPORARY CHANGE DURATION If the change package type selected is TEMPORARY, then Change Man must be instructed as to how many days the package is to remain in the temporary "production" libraries defined in application administration (the package will be automatically removed at the end of this time). Enter the number of days, from 1 to 30. NOTE: The number of days entered in the TEMPORARY CHANGE DURATION field follows a 24-hour time frame. For example, a package installed today at noon, for one day, would be automatically removed tomorrow at noon.

4.1.2 Package General Description Panel You can describe your change package using forever narrative in the General Description area of the panel. Change Man saves upto 46 lines of text. 4.1.3 Package Installation Instructions In this panel you can record instructions for the Installation of the Change package as well as to indicate an option for problem contingency instructions in case a production problem arises after the package has been installed 4.1.4 Scheduling Dependencies Here you can enter the SUCCESSOR and PREDECESSOR job names.

Page 6 of 17

Change Man

4.1.5 Remote Site Information Here you have to enter the remote sites ,where your change package is to be installed, schedule the installation date and time of the change package and enter the name and phone number of the person(s) responsible for the change 4.1.6 Create Super/Complex Package 4.1.6.1 Affected Applications panel

Enter the applications affected by this package. 4.1.6.2 Complex/Super Information panel

Use this panel to record the participating package ID’s associated with the super/complex package.

4.2 Staging a Component in the Change Package. Staging is a process of introducing components into change package. It will copy components from development or personal libraries into Change Man Staging Libraries. The following screen is used to stage a component into a Change Package. When you Use “S1” option next to the Package in the Change Package List the following screen will be presented. Or you can select it by 1.6 option in the Primary menu. ******************************************************************************** --------------------------- STAGE: FROM DEVELOPMENT --------------------------COMMAND ===> PACKAGE ID: IACL000041 ISPF LIBRARY: PROJECT ===> GROUP ===> TYPE ===> MEMBER ===>

STATUS: DEV

INSTALL DATE: 20011205

(Blank or pattern for list; * for all members)

OTHER PARTITIONED OR SEQUENTIAL DATASET: DATASET NAME ===> ORGANIZATION ===> (PDS, SEQ, PAN, LIB, OTH) LIBRARY TYPE LANGUAGE STAGE NAME CONFIRM REQUEST STAGE MODE SUPPRESS MESSAGES

===> ===> ===> ===> YES ===> 1 ===> YES

(Blank for list) (Blank for list; applies to source code) (Optional if organization not SEQ) (Y/N) (1-Foreground, 2-Batch) (Y/N; applies to batch stage)

Page 7 of 17

Change Man

Press ENTER to process; Enter END command to exit. ********************************************************************************

Selecting components in the staging You will get this screen at the time of staging a component when you entered the PDS name but not entered the member name. ******************************************************************************** STAGE FROM - BXIAS1.OPS05.UNIT.C00A05.X097701.SRC ------------ Row 1 to 2 of 2 COMMAND ===> SCROLL ===> CSR NAME FUNCTION VV.MM CREATED CHANGED SIZE INIT ID _ C070115 01.04 1999/10/18 1999/11/08 11:52 2333 2329 X097701 _ C070124 01.05 1999/10/18 1999/11/08 11:55 1958 1956 X097701 ******************************* Bottom of data ********************************

After selecting some componets above by pressing enter ,you will get the following screen

******************************************************************************** ------------------------- STAGE: COMPILE AND LINK EDIT --- PROCEDURE UNDEFINED COMMAND ===> PACKAGE ID: IACL000041

STATUS: DEV

INSTALL DATE: 20011205

STAGED NAME: LIBRARY TYPE: LANGUAGE: DATASET NAME:

C070115 SRO - Source Code - Online COBOL BXIAS1.OPS05.UNIT.C00A05.X097701.SRC

COMPILE PROCEDURE COMPILE PARMS LINK EDIT PARMS DB2 PRE-COMPILE OTHER OPTIONS

===> CMNASM ===> ===> ===> NO ===> YES

(Blank for list; ? for designated procedure) (Y/N) (Y/N to display other options)

JOB STATEMENT INFORMATION: ===> //X097701M JOB (B,X,25CX00),'CHANGE MAN',_______________________________ ===> // MSGCLASS=V,MSGLEVEL=(1,1),TIME=1440,_____________________ ===> // NOTIFY=&SYSUID___________________________________________ ===> //*+JBS BIND CMAN_______________________________________________________ Press ENTER to process; Enter END command to exit. ********************************************************************************

You will get the below screen when staging a component and when you have not entered the type of the component. ******************************************************************************** ------------------------- LIBRARY TYPE SELECTION LIST ------ Row 1 to 11 of 11 COMMAND ===> SCROLL ===> CSR _ _ _ _ _

LIB BMS CPY DCL DOC LCT

DESCRIPTION BMS Map Source Copybooks DCLGEN Copybook Documentation Linkedit Control Cards

Page 8 of 17

Change Man _ MAV CICS Map (Unmodified) _ MPC CICS Map DSECT _ SPL Sample JCL _ SRC Source Code _ SRN Subroutine Source _ SRO Source Code - Online ******************************* Bottom of data ******************************** ********************************************************************************

You will get this screen when staging a component and when you have given “yes” for DB2-Pre compile option in “COMPILE AND LINK EDIT” Screen. ******************************************************************************** --------------------------- DB2 PHYSICAL SUBSYSTEMS --------- Row 1 to 9 of 13 COMMAND ===> SCROLL ===> CSR VERSION ===> ________________________________________________________ Enter S to select a DB2 subsystem and continue. ***

In CSC please select DBB9 for DB2 Version 5.

***

In ERSC please select DBA6 for DB2 Version 5.

*** ***

Enter END command to exit. DB2 REMOTE DB2 SYSTEM SUBSYS SITE LOAD LIBRARY _ DBB4 BXXXB4.DB2.SDSNLOAD _ DBB9 CSC BXXXB9.DB2.SDSNLOAD _ DBB1 CSC BXXXB1.DB2.SDSNLOAD _ DBB3 CSC BXXXB3.DB2.SDSNLOAD _ DBB4 CSC BXXXB4.DB2.SDSNLOAD _ DBB5 CSC BXXXB5.DB2.SDSNLOAD _ DBB6 CSC BXXXB6.DB2.SDSNLOAD _ DBB7 CSC BXXXB7.DB2.SDSNLOAD _ DBA1 CSC AXXXA1.DB2.SDSNLOAD ********************************************************************************

You will get this screen when staging a component and when you have given “yes” for Other Options option in “COMPILE AND LINK EDIT”. ******************************************************************************** ----------------------------- STAGE: USER OPTIONS ----------------------------COMMAND ===> NAME: C070115 TYPE: SRO LANGUAGE: COBOL COMPILE ONLY CICS PRE-COMPILE PARM = SP RELEASE (4=410 3=TS1.3) INCLUDE CICS LIBS BMSMAP OVERRIDE PARMS INCLUDE AOS COPYLIBS BATCH/CICS SHARED MODULE XPEDITER / XLS-Abendaid

===> ===> ===> ===> ===> ===> ===> ===>

BYPASS CYPBK IMBED SAVE SUBROUTINE LOAD(NCAL) TCR (1=APOST, 2=QUOTE) FINALIST VERSION (1=V72 2=V73) INCLUDE MQ SERIES CYCLE (YYCCWW, EX. 97D45)

===>

Page 9 of 17

===> ===> ===> ===> ===> ===> ===>

Change Man DDIO NAME PASSPORT VSAM DICTIONARY

===> ===> ===>

Use Y or N to select or deselect additional processing options; Press ENTER to continue; Enter END command to exit. ***********************************************************************************

By pressing enter this will compile the program. ********************************************************************************

You can also Stage the components from other packages(Re-stage) You can get this screen by selecting 1.6 option in the Primary menu. Or by selecting Option 6 in the Build menu ******************************************************************************** -------------------------------- STAGE OPTIONS -------------------------------OPTION ===> PACKAGE ID ===> IACL000032 1 2 3

Dev Package Parms

- Stage components from development libraries - Process package components - Specify component list selection criteria

Press ENTER to process; Enter END command to exit. ********************************************************************************

4.3 Compile the programs after the changes Components are compiled when staging only.. If we want to do any changes and compile the program then the following procedure to be followed.. Display all the components by typing “S2” next to the package or by typing selective display “S3” When you Use “S3” option next to the Package in the Change Package List the following screen will be presented. ******************************************************************************** -------------------------- COMPONENT LIST PARAMETERS -------------------------OPTION ===> PACKAGE ID: IACL000041

STATUS: DEV

SPECIFY SELECTION CRITERIA: COMPONENT NAME ===>

Page 10 of 17

INSTALL DATE: 20011205

Change Man COMPONENT TYPE LANGUAGE COMPONENT STATUS

===> ===> ===>

CHANGED FROM DATE TO DATE COMPILE PROCEDURE TSOID SHORT OR LONG DISPLAY CONFIRM REQUEST SUPPRESS MESSAGES COMPARISON REPORT COMPARISON TEXT TYPE

===> ===> ===> ===> ===> ===> ===> ===> ===>

(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) (Type of data to be compared)

Press ENTER to process; Enter END command to exit. ********************************************************************************

When you Use “S2” option next to the Package in the Change Package List the following screen will be presented. All the components will be presented. ******************************************************************************** ------------------------- STAGE: IACL000032 COMPONENTS ------- Row 1 to 9 of 9 COMMAND ===> SCROLL ===> CSR NAME TYPE STATUS CHANGED PROCNAME ID REQUEST __ AYPREPRA SRO ACTIVE 20010119 142937 CMNCOB2 X096587 __ AYTGOUT SRO INCOMP 20010321 102541 CMNCOB2 X009838 __ AYTGPGM SRO INCOMP 20010607 171345 CMNCOB2 X009838 __ C33DHIS SLD INCOMP 20001005 103308 *RELINK* X009838 __ C33DHIS SRN INCOMP 20001107 113158 IIGCOB2 X009838 __ C33DHISL LCT ACTIVE 20000918 115814 X096586 __ C33DHISL SLD ACTIVE 20001005 103623 *RELINK* X034275 __ C33DPRJ SRN INCOMP 20001107 112937 IIGCOB2 X009838 __ C33DRDR SRN INCOMP 20001107 113032 IIGCOB2 X009838 ******************************* Bottom of data ******************************** ********************************************************************************

Then Type “E” next to the components to select it for editing.When saving it goes directly to compile and link-edit screens. The following line commands are available from the above panel. B (Browse), D(Delete), E(Edit), H(History), R(Recompile), S(Stage).........etc.,

4.4 Audit the package The audit function compares baseline libraries to staging libraries and identifies out-of-sync situations that could prevent change package components from being successfully installed into production. This might include: 1. Copybooks that have been changed after a source program has been compiled.

Page 11 of 17

Change Man

2. 3.

Source programs that need to be recompiled due to a copybook change. Called subroutines that have been changed after a referencing source program has been complied and linked. The audit function can also analyze regression and warn you if you are moving a component into production that is not the most current version. A change package must pass audit before freeze. Audit can be done by selecting 1.6 option in the Primary menu. Or by selecting Option 7 in the Build menu or by typing “AP” directly next to the package. Audit Report will be generated when auditing . The report displays “FLAGS!” to alert the user to audit problems. For example... SYNCH0!...SYNCH16! ..SYNCH15! means Source to Copy relationship problem..i.e., The contents of the called copybook has changed since the Source module was compiled. You can refer the manual for other return codes, it provides some suggested resolutions to some of the out-of-synch situations.

4.5 Promote the Package Promotion allows a change package to be moved through specific environments for various test requirements, such as unit, system and acceptance testing. For each application, you can determine the number od promotion libraries you require for your testing environment and the types of components that will be tested. However , Library Management minimum promotion level standrads (development and quality assurance) will be enforced. Promote can be done by selecting 3 option in the Primary menu. Or by typing “PD” next to the package to be promoted . Demote also can be done by using the same option.

4.6 Freeze the package This step locks the package prohibiting further changes and makes the package available for the approval process. A change package can be unlocked and moved back to the development environment for additional changes with the use of the revert function. Freeze can be done by selecting 2 option in the Primary menu. Or by typing “F1” next to the package to be freezed.

4.7 Baseline the package Baseline libraries contains both the current version and the prior versions of every component of an application. When a change package is installeld into production, the baseline is rippled. That is, version 0 becomes –1, -1 becomes –2, -2 becomes –3, etc., and the new baseline 0 version is installed.

Page 12 of 17

Change Man

5 Other Stages in Maintaing Components in Change Man : 5.1 Updating Change Package Information: Select Option 2 from the Build Options panel.You will get “Update : Package Information” menu panel from here you can select appropriate options to update control information, Installation instructions, Install dates and site information,Affected applications,Complex/Super package information. You can Update the Package Information by typing “U1” to “U9” next to the package depending on the information needed to be updated.

5.2 Checking Out a Component: This is the process of copying components from secured(or baseline) libraries for modification within development. It serves as a reservation system for controlling who can access components, as well as a function that ensures developers are working with the correct version of a component. Select Option 5 from the Build Options Menu. You will get a “Checkout Options” panal from here you can checkout components from baseline or promotion libraries or you can checkout package components. OR you can directly type “C1” next to the package for checking out components.

5.3 Comparing Staging Libraries to Baseline/Promotion Libraries: 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. Select Option C on the Build Options menu for comparing the components.

5.4 Approving or Rejecting a Component: Frozen change packages can be Approved or Rejected by the individuals responsible for reviewing and Approving change packages. These people are determined by the Change Man Administrator during application level generation. Select Option 4 on the Primary Option Menu OR type “A1” next to the package.

5.5 Package Functions: Package List Options

Page 13 of 17

Change Man

You can use different options in the package list screen . The following screen shoes those options. ******************************************************************************* ----------------------------- PACKAGE LIST OPTIONS ------ INVALID LINE COMMAND COMMAND ===> SCROLL ===> CSR OPTION DESCRIPTION ------------------------------------------------------------------------------U1 Update control information U2 Update general information U3 Update implementation information U4 Update scheduling information U5 Update affected application information U6 Update participating package information U7 Update site(remote) information U8 Change complex/super package to CLO status U9 Change complex/super package to OPN status OF Work with Online forms UA Rename and Scratch components (Package driven) UB Rename and Scratch components (Baseline driven) C1 Check out components (Baseline/promotion) C2 Check out components (Package list) S1 Stage components (Dev Lib list) S2 Stage components (Package list) S3 Specify package driven selection parameters AP Audit package RC Recompile source code from baseline/promotion libraries RL Relink load modules ----------------------------- PACKAGE LIST OPTIONS -------- Row 21 to 38 of 38 COMMAND ===> SCROLL ===> CSR OPTION DESCRIPTION ------------------------------------------------------------------------------BB Browse/Print Baseline/Promotion libraries BL Browse compressed listing CC Compare staging changes against baseline/promotion libraries ZP Compress change package staging libraries F1 Freeze the change package online F2 Freeze the change package in batch F3 Selectively unfreeze or refreeze package components F4 Reset Freeze in Progress indicator PD Promote/demote a change package PR Remote promote/demote a change package A1 Approve/Reject a change package A2 Display reject reasons A4 Reset Approval in Progress indicator D1 Memo delete a change package D2 Undelete a memo deleted change package RV Revert a change package back to DEVelopment status QP Query change package information SC Scan baseline for character strings ******************************* Bottom of data ******************************** ********************************************************************************

Page 14 of 17

Change Man

5.5.1 Package Query Functions: You can view package components, status and installation schedules using the Query Package Function from the Package List panel. ******************************************************************************** ----------------------------- CHANGE PACKAGE LIST ---------- Row 1 to 14 of 14 COMMAND ===> SCROLL ===> CSR PACKAGE ID STA INSTALL LVL TYPE WORK REQUEST DEPT PROMOTE AUD CREATOR __ IACL000003 CLO CMPX PLN/PRM ACL CPLX PKG X074223 __ IACL000028 BAS 20001027 SMPL PLN/PRM R1108- LIB 00I 4 X096586 __ IACL000029 BAS 20001027 SMPL PLN/PRM DI3398 00I 0 X096586 qp IACL000030 DEV 20011231 SMPL PLN/PRM SANDBOX EMER STAGING X097101 __ IACL000031 BAS 20001117 SMPL PLN/PRM R1077 00J 0 X096586 __ IACL000032 DEV 20011231 SMPL PLN/PRM R1126 00J STAGING X096586 ******************************* Bottom of data ******************************** ******************************************************************************** ------------------------ PACKAGE INFORMATION CATEGORIES ---- Row 1 to 18 of 21 COMMAND ===> SCROLL ===> CSR PACKAGE ID: IACL000030 CREATOR: X097101

STATUS: DEV AUDIT RC:

INSTALL DATE: 20011231

_ 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 _ Remote Promotion History _ Promotion Libraries _ Remote Promotion Libraries _ Development Staging Libraries ------------------------ PACKAGE INFORMATION CATEGORIES --- Row 19 to 21 of 21 COMMAND ===> SCROLL ===> CSR PACKAGE ID: IACL000030 CREATOR: X097101

STATUS: DEV AUDIT RC:

INSTALL DATE: 20011231

_ Production Staging Libraries _ Production Libraries _ Baseline Libraries ******************************* Bottom of data ********************************

Page 15 of 17

Change Man ********************************************************************************

6 Change Man Screens : 6.1

Screen 1 : Change Man Primary option menu:

******************************************************************* ---------------- CHANGE MAN 4.1.6X PRIMARY OPTION MEN

OPTION 1 2 3 4 5 C D L N O Q R T X

NOTIFICATION UPDATED

===>

Build Freeze Promote Approve List CDF Delete Log Notify OFMlist Query Revert Tutorial Exit

-

Create, update and review package data Freeze or unfreeze a package Promote or demote a package Approve or reject a package Display (to process) package list Concurrent Development Facility Delete or undelete a package Browse the activity log Browse the Global Notification File Online Forms package list Query packages, components and relationships Revert a package to DEV status Display information about Change Man Exit Change Man

Press ENTER to process; enter END command to exit. **********************************************************************

6.2

Screen 2 : Change Man Build Options menu:

When you select Primary Option 1 (Build), the Build Options Menu is presented. ********************************************************************** -------------------------------- BUILD OPTIONS -------------------------------OPTION ===> 0 1 2 3 4 5 6 7 8 9 B C L S Z

Dates Create Update Custom Utility Checkout Stage Audit Recompile Relink Browse Compare Listing Scan Compress

-

Display the installation calendar Create a new package Update package information Create, update, approve or review custom forms Rename and Scratch information Check out components from baseline or promotion Stage, edit, browse and delete components Audit a package Recompile source code from baseline or promotion Relink load modules Browse\print\copy baseline or promotion Compare staging to baseline or promotion Browse compressed listings Scan baseline for character strings Compress change package Staging Libraries

Page 16 of 17

Change Man

Press ENTER to process; Enter END command to exit. **********************************************************************

6.3 Screen 3 : Package List Parameter When you select Primary Option 5 (List), the List Parameters Menu is presented.

********************************************************************** --------------------------- PACKAGE LIST PARAMETERS --------------------------COMMAND ===> SPECIFY SELECTION CRITERIA: PACKAGE ID ===> IACL PACKAGE STATUS

===>

CREATOR'S TSO-ID WORK REQUEST ID DEPARTMENT PACKAGE LEVEL

===> ===> ===> ===>

PACKAGE TYPE PACKAGE TIME SPAN FROM INSTALL DATE TO INSTALL DATE FROM CREATION DATE TO CREATION DATE OTHER PARAMETERS

===> ===> ===> ===> ===> ===> ===>

(Full name or pattern; blank for list, or '*' for all packages) (DEV, FRZ, APR, REJ, DIS, INS, BAS, BAK, OPN, CLO, TCC or DEL)

(1-Simple, 2-Complex, 3-Super, 4-Participating) (Planned or Unplanned) (Permanent or Temporary) (YYYYMMDD) (YYYYMMDD) (YYYYMMDD) (YYYYMMDD) (Y/N)

Press ENTER to process; Enter END command to exit. **********************************************************************

6.4 Screen 4 : Change Package List When you select Primary Option 5 (List), and then by entering the proper parameters the following package list screen will be presented. ********************************************************************** ----------------------------- CHANGE PACKAGE LIST ---------- Row 1 to 14 of 14 COMMAND ===> SCROLL ===> CSR PACKAGE ID STA INSTALL LVL TYPE WORK REQUEST DEPT PROMOTE AUD CREATOR __ IACL000003 CLO CMPX PLN/PRM ACL CPLX PKG X074223 __ IACL000028 BAS 20001027 SMPL PLN/PRM R1108- LIB 00I 4 X096586 __ IACL000029 BAS 20001027 SMPL PLN/PRM DI3398 00I 0 X096586 __ IACL000030 DEV 20011231 SMPL PLN/PRM SANDBOX EMER STAGING X097101 __ IACL000031 BAS 20001117 SMPL PLN/PRM R1077 00J 0 X096586 __ IACL000032 DEV 20011231 SMPL PLN/PRM R1126 00J STAGING X096586 __ IACL000033 BAS 20001116 SMPL PLN/PRM R1077-IDS US 00J 0 X009838 __ IACL000034 BAS 20001117 SMPL PLN/PRM R1077-IDS CD 00J 0 X009838 __ IACL000035 BAS 20010223 SMPL PLN/PRM DI3417-R4521 01B 0 X009838 __ IACL000036 BAS 20010324 SMPL PLN/PRM R1211 01C 0 X096587 __ IACL000037 BAS 20010406 SMPL PLN/PRM R1246-IDS US 01C+ 0 N000001 __ IACL000038 BAS 20010615 SMPL PLN/PRM REMEDY#2156 01F 0 X072060 __ IACL000039 BAS 20010810 SMPL PLN/PRM DI3435 01H 0 X021546 __ IACL000041 DEV 20011205 SMPL PLN/PRM SANDBOX 3435 UNITH X021546 ******************************* Bottom of data ********************************

********************************************************************************

Page 17 of 17