Change Control User Manual section
Contents
1. Once the PROC has been changed execute a Job Scan run against the PROC to verify that the PROC is error free with the standards validation Exit Perform a Class A test of the newly alered PROC to validate that it performs its functions correctly When you have successfully completed the Job Scan verification and the Class A test copy the PROC to PLCP GROUP PROCLIB The movement of the PROC to the staging library is performed manually Endevor is not utilized for PROC migrations Notify the Change Control area that the PROC has been migrated to the Quality Assurance library and that verification can begin Change Control Usage Procedures Page 12 10 Standards and Procedures 12 3 4 CARDLIB Whenever new Control Cards are added to a job a PRA form must be completed After creating the new CARDLIB member and placing it in the Endevor Staging library simply submit an E Mail message to the Change Control area stating that the CARDLIB member is ready to be migrated to the production environment The Endevor CARDLIB library for CPU F is PLCPTST ENDVFID ACCEPT CARDLIB The Change Control area will perform the CARDLIB member migration from their terminal via Endevor CARDLIB changes are indicated in the PRA form for new changed PROCs if Cardlib s are being migrated Change Control Usage Procedures Page 12 11 Standards and Procedures 12 3 5 SUPPDATA SUPPDATA documentation is required for2. all new job turnovers and for changes to production jobs Only specific sections of SUPPDATA are required for Changes specifically the Change History area of SUPPDATA but all pertinent areas of SUPPDATA must be completed when altering the job frequency or the predecessor successor relationships of a job SUPPDATA documentation is examined in depth for new jobs but is only reviewed for alterations to existing jobs CARDLIB member changes do not require updates to SUPPDATA but all other changes must be entered into the SUPPDATA Change History section The sections included in SUPPDATA and their usage are Responsibility Action Change History Provides the date and description of previous changes to the job Scheduling Requirements Provides information about when the job is to run how long it takes predecessor and successor information and job contingency priority and data Control Card Shows the record layout and other information pertinent to the control cards Restart Recovery Procedures Documents all non zero condition codes whether or not acceptable providing procedures to follow Microfiche Test has been done and included in packet Out of House Input Provides information about inputs received from location outside the data center Out of House Output Provides information on data center outputs that are shipped Out of House Microfiche Request Form Used to request an off line microfiche report Change Contro
3. 4 7 G FORMS DESIGN REQUEST FORM 00cccccccccseeeeeececeeeeseeaeeueeseeeeeeseeauauseseeeeseeaeanees 25 12 4 8 H VSAM SPACE ALLOCATION FOPM sssessessssesrsssseesnrrrrinrssserrrirrresnrnrrnnrssesunrnnne 26 124 9 NON VSAM SPACE ALLOCATION FORM ooccccccccccnonocnccnncnnnnnnnnncnnnancnnnnonannncccninononos 28 12 4 10 J DISK GDG FOR DATA ENTRY FORM c ocoooccccccccncnnnonnnoccnnnnnonononncnnnnncnnnnonannnnaccnncnnnos 29 12 4 11 K RETENTION PERIODS FOR DATA ON TAPE FORM oococcccccconononcccncnncnnnnonananinnnnnononos 30 Change Control Usage Procedures Page 12 2 Standards and Procedures Section Table of Figures FIGURE 1 OVERVIEW OF CHANGE CONTROL PROCESS ee 4 FIGURE 2 SAMPLE JOB CARD LAYOUT cccoccccconononononononononenonononononononononononononononononononnnonnnnnnnnonanononononanonanananenes 9 FIGURE 3 JOB NAMING STANDARD ccccccccccnnccononononononononononononononononnnnnnnnnnnnnnnnnnnononononononononononononononononononeneneness 9 Change Control Usage Procedures Page 12 3 Standards and Procedures 12 Change Control Usage Procedures 12 1 Overview of Change Control 12 1 1 Introduction Change Control is responsible for the promotion and control of elements being put into production for both the Batch and On Line processing done at the data center This includes the following elements Jobcards Procs Cardlibs Suppdata Runbooks Programs Includes and Copybooks which are moved from the quality assurance staging e
4. Change Control Usage Procedures Release Date March 18 2012 Produced by Thomas Bronack Standards and Procedures Section Table of Contents 12 CHANGE CONTROL USAGE PROCEDURES ccccacccccccocnncnnnnnnononnncnnnonananarononcnnananananonnnnnannaanana 4 12 1 OVERVIEW OF CHANGE CONTROL ss ss ss sss s ss esen ennenen ennn neea 4 124 1 INTRODUCTION A A E E A E A ee aed 4 1 2 1 2 OBJECTIVES OF CHANCE O OAT ROD a a a a in ld att cial 5 A AT 5 12 1 4 PREPARATION MAINTENANCE OF USER GUIDE x e 5 12 2 CREATING AN ON LINE TURNOVER HEOUEST ses se sese esec eee esec eee ee reer ereer 6 12 3 CREATING A BATCH TURNOVER REQUEST sss ss ss evs sss seene ennenen nenen ennenen 8 12 3 1 CHANGE CONTROL TURNAROUND TIMES e e e 8 1232 JOB CARD 1 o a ios dsd 9 1233 PROC A ENS 10 1234 CARD E a a a a nd a dara sia 11 12 3 5 SUPPDAUV A 2 ts L A A EEA Mina 12 12 3 6 SPACE ALLOCATION AND OTHER FORMS cccconocccccccnconononononcnnnnnononennnnnnancn nono nannnnancnnnnonos 13 1253 RROGRAM ES R oc leas 14 12 38 INCLUDES cosa ii as 14 123 96O0PYBOOK Sites ini aa oi alicia diia Dina 15 12 4 APPENDICES eiii IR AR AA 16 12 4 1 A STANDARDS VARIANCE REQUEST EORM 17 T242 B TURNOVER GHEGKINS Ts cional cla atea tilda Load 19 12 4 3 C PROGRAM RELEASE AUTHORIZATION FORM cocononocccccccononononncnncnncnnononanacnnnnnnononos 20 12 4 4 DTAPEREQUEST FOR Mission 22 12 45 E DOCUMENTATION MOpIFICGATION 23 12 4 6 F JOB DELETION AUTHORIZATION 24 12
5. DATE yy mm dd TIME hh mm USERID userid NAME TAPE REQUEST FORM hdhdh hh KE K K K K K K K KK KK JOB NAME FREQUENCY TAPE STATUS DATASET NAME REQUEST TYPE PROGRAM NAME STEP NAME DD NAME DATE NEEDED BY REQUESTED BY PHONE NUMBER APPLICATION NAME VP TO NEXT RUN BACKUP DSN TMSDISP DD OUTCODE CONTINGENCY SITE GENERATION DATA GROUP BUILD REQUEST TEKEK EKE hh hhh EKE EKE EK EK EK E KE E K E E E KE K K K K K K K K K KK KK BUILD COMPLETED BY NAME DATE PHONE TAPE ADDED TO BACKUP LIST BY NAME DATE PHONE Change Control Usage Procedures Page 12 22 Standards and Procedures 12 4 5 E Documentation Modification DATE yy mm dd TIME hh mm USERID userid INFO DOCUMENTATION MODIFICATION hdhdh hhh hdhdh dh hhh K K E K K K K K K KKK K JOB NAME DESCRIPTION OF CHANGE AUTHORIZATION SIGNATURE TEKEK EOK EOE EE E E KE E K E K E K K K KK K K KK KK K MANAGERS APPROVAL DATE REASON FOR REJECTION Change Control Usage Procedures Page 12 23 Standards and Procedures 12 4 6 F Job Deletion Authorization DOCDEL JOB DELETION AUTHORIZATION JOB NAME PROCEDURE NAME PROCLIB PROGRAM NAME INFO NUMBER IMPL DATE CONTROL CARD LIBRARY MEMBER NAME MANAGER S SIGNATURE DATE Change C
6. Job cards are created by the Change Control area for all batch jobs Only the PROC is provided to the Change Control area by the programmer Once a PROC is received for a new batch job the Change Control area generates the appropriate job card The layout of a job card is as follows IIZLCDI10A JOB PROD PROGRAMMER CLASS H MSGCLASS A MSGLEVEL 1 1 NOTIFY LXH648 JOBPARM SYSAFF CPUF Figure 2 Sample Job Card Layout The job naming standard is described below Jobname Standards ZLCDXXXA AAA Always used with exceptions Job sequence number Frequency D W M Q A R Daily Quarterly Lehman Application Abbreviation Weekly Annual Monthly Request Z for Production JOBs Exec JCL P for Production PROCS Figure 3 Job Naming Standard The Change Control area will create a job card for new jobs but job card changes are not required for changed jobs The production job library for CPU F is PRODLCP OPCA JOBLIB Job cards for CPU F will reside in this library Change Control Usage Procedures Page 12 9 Standards and Procedures 12 3 3 PROC A PRA form is required to initiate a PROC Change Control Once completed submit the PRA form to the Change Control area by placing it in the In Basket on the 28th Floor of 101 Hudson Street To change a PROC the programmer will copy the production PROC to their maintenance library The production PROC library for CPU F is PRODLCP PROCLIB
7. LING CHECKED OUT BY WHOM PRODUCTION SERVICES RACF NEEDED NEW CLISTS MODIFIED CLISTS Change Control Usage Procedures Page 12 19 Standards and Procedures 12 4 3 C Program Release Authorization Form hdhdh hhh ae e le E K KE K E K K K ole K K K KKK K RELEASE AUTHORIZATION TEKEK EOK EOK EE E E KE E K E K E K KE K K K K K K K K KKK K JOB NAME APPLIC NAME PROGRAM NAME FREQUENCY PROCEDURE NAME JES JOB NUMBER TEST JOB NAME ENDEVOR SYSTEM TURNOVER TYPE ENDEVOR SUBSYS PROBLEM INFO NO CHANGE TYPE CHANGE INFO NUMBER PTMM NUMBER DASD HAS NOT BEEN REQUESTED ENDEVOR ENDVFID STAGE 1 PROGRAM ELEMENT NAME ENDEVOR TYPE NAME INCLUDE ELEMENT NAME TYPE NAME HAS BEEN CHANGED FROM TYPE PROCEDURE LIBRARY PLCP GROUP PROCLIB CARDLIB ELEMENT NAMES TURNOVER DATE RUN DATE Change Control Usage Procedures Page 12 20 Standards and Procedures Program Release Authorization Form continued AUTHORIZATION SIGNATURES PROGRAM TEST COMPLETED DATE MANAGERS APPROVAL DATE DATABASE DESIGN APPROVAL DATE USER ACCEPTANCE TEST COMPLETED DATE COMPANY CHANGE CONTROL DATE IMPLEMENTATION COMPLETE DATE AUDIT COMPLETED DATE PROGRAM CHANGE DESCRIPTION BACKOUT PROCEDURES REASON FOR REJECTION Change Control Usage Procedures Page 12 21 Standards and Procedures 12 4 4 D Tape Request Form
8. S _ CYLINDERS _ PRIMARY SECONDARY VSAM CATALOG VOLUME DEVICE TYPE SUB ALLOCATION UNIQUE COMPLETED BY DATE Change Control Usage Procedures Page 12 27 Standards and Procedures 12 4 9 I Non VSAM Space Allocation Form DATE yy mm dd TIME hh mm USERID userid NON VSAM SPACE ALLOCATION FORM JOB NAME DATE NEEDED BY DATA SET NAME REQUEST TYPE REQUESTER NAME MANAGERS NAME PHONE NUMBER APPLICATION NAME APPROX REC DSORG LRECL BLKSIZE CONTINGENCY SITE RECFM PRIMARY SECONDARY VOLUME DEVICE TYPE COMPLETED BY DATE Change Control Usage Procedures Page 12 28 Standards and Procedures 12 4 10 J Disk GDG for Data Entry Form DATE yy mm dd TIME hh mm USERID userid DISK GDG FOR DATA ENTRY JOB NAME REQUEST TYPE DATA SET NAME REQUESTER NAME MANAGERS NAME PHONE NUMBER DATE NEEDED BY APPLICATION NAME OF GDG ENTRIES RETENTION PERIOD APPROX OF RECORDS DSORG LRECL BLKSIZE RECFM CONTINGENCY SITE SPACE ALLOCATION TYPE TRACKS ___ CYLINDERS __ PRIMARY SECONDARY VOLUME COMPLETED BY DATE FILE ENTERED INTO PDEDBKP PROC DUMMY CATALOGUE ENTRY FOR DISK FILE Change Control Usage Procedures Page 12 29 Standards and Procedures 12 4 11 K Retention Periods
9. for Data on Tape Form The standard retention time frame for data to be kept on tape is Daily 5 days Weekly 35 days Monthly 155 days Quarterly 180 days Annually 265 days Legal 2 555 days All times are in Business Days Requests to retain data on tape for longer than the standard time must be approved by a Senior Vice President Change Control Usage Procedures Page 12 30
10. includes information about the number of entries record characteristics any contingency site whether storage is in tracks or cylinders and backup volumes Change Control Usage Procedures Page 12 13 Standards and Procedures 12 3 7 PROGRAM A PRA form must be completed to perform a program change Submit the form to the Change Control area by placing the form into the Change Control area s In Basket on the 28th Floor of 101 Hudson Street The change request will be retrieved by one of the Change Control staff and worked on in the order received Program changes are addressed in much the same manner as PROC changes You must perform a Class A test on the program to validate its functions before migration to the production environment will be performed by the Change Control area Update the SUPPDATA associated with the Job s using the program that is being changed Ata minimum the Change History form must be updated to record the change control being performed Once the Class A test has been completed use Endevor to place the program element into the appropriate Stage I library for that program type i e Cobol Assembler etc and notify the Change Control area via E mail that the program is ready for migration The Change Control area will then migrate the program to production through normal Endevor pocedures 12 3 8 INCLUDES As with program changes Includes require the completion of a PRA form to auth
11. l Usage Procedures Page 12 12 Standards and Procedures 12 3 6 Space Allocation and Other Forms A variety of forms available through Docu Text are required for all turnovers if called for by the type of change These forms are particularly necessary for jobs requiring space allocations on DASD and TAPE devices The forms are described below Any form that applies to the type of change you are submitting must be completed All of the forms are provided in the Appendix of this document Responsibility Action Tape Request Form Provides information about the job s tape requirements including backup and contingency needs lt Note gt See Retention Periods for Data on Tape in the appendix for a summary of the standard tape retention timeframe Documentation Modification Describes any changes to the documentation for the job 1 e schedule changes JOB Deletion Authorization Provides information necessary for deleting a job already in production This form is necessary to remove a job from production to an archive library Forms Design Request Describes in detail any forms that must be designed for the Job s output VSAM Space Allocation Form Requests VSAM storage space includes all information needed to allocate the space Non VSAM Space Allocation Form Requests storage space in non VSAM tracks and cylinders also indicates any contingency site Disk GDG for Data Entry Requests Generation Data Group data entries
12. llowing A There are 21 possible fields to use fill in the 3 required fields and any other fields that support your request The 3 required fields are 1 Requester name 2 Delivery name number 3 Description NOTE These fields may be pre filled from information filled in on another screen B Select option 23 Freeform text Change Control Usage Procedures Page 12 6 Standards and Procedures 7 The third panel the FREEFORM TEXT ENTRY PANEL requires the following A There are 7 possible selections fill in the 1 required field and any others that support your request The 1 required field is 1 Element Listing Description Special Instructions amp Backout Plan B Press the ENTER key 8 The fourth and last panel the ON LINE TURNOVER REQUEST SUMMARY PANEL supports the following A There are 13 summary fields populated with previously entered or generated information and 7 selection options B At this point in the process only 3 options apply they are 1 8 9 11 12 Requester data return to the ON LINE TURNOVER REQUEST ENTRY PANEL Freeform text return to the FREEFORM TEXT ENTRY PANEL Save record keep entries but do not submit Request ready for management approval ready to submit for Change Control Cancel request before management approval cancel all inputs and do not submit To complete the process Select option 11 Request ready for management approval Change Co
13. mber of the Change Control staff Change Control Usage Procedures Page 12 15 Standards and Procedures 12 4 Appendices A Standards Variance Request Form B Turnover Checklist C Program Release Authorization Form D Tape Request Form E Documentation Modification F Job Deletion Authorization G Forms Design Request Form H VSAM Space Allocation Form I Non VSAM Space Allocation Form J Disk GDG for Data Entry Form K Retention Periods for Data on Tape Form Change Control Usage Procedures Page 12 16 Standards and Procedures 12 4 1 A Standards Variance Request Form A variance form standards is granted for 5 business days only The job for which this variance is approved must conform to standards within 5 days or the agreed upon date If this job does not conform to standards within the specified period no further variances will be granted to the applications area until this job conforms to standards An application area can have up to 5 variances outstanding at any one time No further variances will be granted to an application area while the area is at the maximum variance level JOBNAME Date of Conformance _ Indicate all standards for which variance is requested Naming Standard Naming Standard Program Name Map and Mapset Name Transient Data destination Name FCT and DD name DSN Transaction Other Name specify VERIFY where implemented Turnover Lead ti
14. me Moratorium CICS documentation Batch documentation Other specify Change Control Usage Procedures Jobname PROC Name DD Name Program Name DSN Other Name specify Block Size Cardlib GDG Allocation Disk Vs Tape Other specify Page 12 17 Standards and Procedures Standards Variance Request Form continued Indicate the reason for variance Regulatory requirements Outside package System unavailable for testing To keep batch and on line in sync Required by Operations Other please specify To access datasets programs Describe the proposed variance also supply reason Requested by Date Location Phone Applications Area Approved by Date Signature Title Variance must be approved at the Systems Facility Manager level Variance Number assigned by Change Management Change Control Usage Procedures Page 12 18 Standards and Procedures 12 4 2 B Turnover Checklist PROJECT NUMBER NEW PROGRAMS MODIFIED PROGRAMS PROGRAMS DOCUMENTED MODIFIED INCLUDES NEW CALL PROGRAMS MODIFIED CALL PROGRAMS NEW PROCEDURE MODIFIED PROCEDURE PROCEDURES DOCUMENTED NEW FILES MODIFIED FILE LENGTHS NEW CARDLIBS MODIFIED CARDLIBS SUPPDATA DOCUMENTED NEW REPORTS REPORT DISTRIBUTION UPDATED APPROXIMATE NUMBER OF PAGES SCHEDU
15. ntrol Usage Procedures Page 12 7 Standards and Procedures 12 3 Creating a Batch Turnover Request The topics described in this section refer to migrating elements of batch jobs into the production environment Each element of a batch job that is subject to change is addressed separately for ease of understanding 12 3 1 Change Control turnaround times When submitting a Change Control complete the appropriate PRA form Program Request Authorization in duplicate and place the form in the In Basket at the Change Control area on the 28th Floor of 101 Hudson Street Change Control personnel will retrieve the form and perform changes in the order that they were received except in the case of a special request Make sure that a Class A test of the change has been performed prior to submitting the change to the Change Control area Should the change fail during testing by the Change Control area it will be returned to the submitter The normal turnaround time for a change is e Normal Changes 2 Business Days e New Jobs 5 Business Days e Same Day Changes ECNS Emergency Change Notification System Any priority changes or additional information related to a change should be provided to the Change Control area as necessary This will inform the Change Control individual of any peculiarities associated with the change Change Control Usage Procedures Page 12 8 Standards and Procedures 12 3 2 JOB CARD
16. nvironment to the production environment The purpose of this document is to explain how to do a Change Control request Change Control Process Development Testing Quality Assurance Production Job Analysis for Flow and Resource Usage Docu Text EDP Security JOBCARD PROC CARDLIB SUPPDATA A Library Management DASD Override management Job JCL Scanning for Library Standards Adherence Disaster Recovery Job Scan Job Library Automated Scheduler INCLUDES COPY BOOKS Scheduler Library AF Operator Restart Recovery Validation e File Allocati ile Allocations Distrbution DB2 Binds Element Sign In s Changes to Input Output JOB and its resources Figure 1 Overview of Change Control Process Change Control Usage Procedures Page 12 4 Standards and Procedures 12 1 2 Objectives of Change Control This User Guide is meant to e convey how the different types of changes are put into the Change Control process e provide a how to which follows established procedure for doing Turnovers to the production environment 121 3 Audience This User Guide is for any employee who wishes to migrate elements from the development to the production environment This manual assumes the reader is familiar with the mainframe environment facilities such as TSO ISPF etc 12 1 4 Preparation Maintenance of User Guide Thi
17. ontrol Usage Procedures Page 12 24 Standards and Procedures 12 4 7 G Forms Design Request Form hdhdh hhh hdhdh hhh hh hh E K K K K K K K K K KK KK N FORMS DESIGN REQUEST k hdhdh hhh hdhdh E K EK E hh E K K K K K K K K K OK oR DESTINATION COLOR REQUIRED REQUESTER INFORMATION NAME PHONE NUMBER LOCATION DEPT NUMBER USER INFORMATION NAME PHONE NUMBER LOCATION LINES PER INCH CHANNELS PAPER SIZE SPECIAL PAPER SIZE FORM LENGTH INCLUDE SAMPLE OF FORM TO BE DESIGNED ALONG WITH REQUEST FORM MANAGER S SIGNATURE DATE Change Control Usage Procedures Page 12 25 Standards and Procedures 12 48 H VSAM Space Allocation Form VSAM Space Allocation Form DATE TIME USERID JOBNAME REQUESTED BY MANAGERS NAME PHONE NUMBER DATASET NAME DATE NEEDED BY REQUEST TYPE DSORG RECORD FORMAT AVERAGE RECORD SIZE MAX RECORD SIZE APPROXIMATE NUMBER OF RECORDS KEY LENGTH RELATIVE TO ZERO START POSITION TYPE OF PROCESSING RATE OF INSERTION DATA CI SIZE INDEX CI SIZE FREE SPACE CE FREE SPACE CA BUFFER SPACE VSAM DATA COMPONENT SPACE TYPE TRACKS ___ CYLINDERS PRIMARY SECONDARY Change Control Usage Procedures Page 12 26 Standards and Procedures VSAM Apace Allocation Form continued VSAM INDEX COMPONENT SPACE TYPE TRACK
18. orize a change Place the completed PRA form into the Change Control In Basket on the 28th Floor of 101 Hudson Street where it will be retrieved and worked on by a member of the Change Control staff Retrieve the production copy of the item to be included alter it as required and place it into the Endevor Stage I library for the type of element it represents after you perform any testing that may be required and update any SUPPDATA forms that apply especially the Change History form Notify the Change Control area via E Mail that the Include is ready to be migrated to production The Change Control staff member will migrate the member to production via normal Endevor procedures Change Control Usage Procedures Page 12 14 Standards and Procedures 12 3 9 COPYBOOKS Complete a PRA form and place it into the Change Control In Basket on the 28th Floor of 101 Hudson Street Add the COPYBOOK statement to your program and perform any testing neeed to validate that the COPYBOOK provides the information your program requires After successful testing update the SUPPDATA as required especially the Change History Place the program that you inserted the COPY BOOK into in the appropriate Endevor Stage I type library for the program i e COBOL Assembler etc Inform the Change Control area via E Mail that the program is ready to be migrated to production under Endevor control The program will be migrated to production by a me
19. s Guide is part of the Standards and Procedures Manual The Manual consists of two parts e PartI Systems Management and Controls Procedure Manuals e Part Il Usage Procedures Manual The creation and maintenance procedures are covered in the Maintaining Usage Procedures Manuals section of Part II Change Control Usage Procedures Page 12 5 Standards and Procedures 12 2 Creating an On line Turnover Request On line Turnover requests can be created updated displayed for review approved and closed Users have the ability to create their own On line requests update requests assigned to their departments and review the closing information in the requests 1 Logon to TSO 2 Select option N INFO MAN from the ISPF PDF Primary Options Menu 3 Select option 0 CHANGE MANAGEMENT AND ON LINE TURNOVER from the INFORMATION MANAGEMENT panel 4 You are now at the ON LINE TURNOVER MENU this is the main menu for On line Turnover activities It consists of an INQUIRIES section and a REQUEST FUNCTION section Select option 12 Enter an On Line request 5 You are now at the first of four panels used to put in an On line Turnover request the ON LINE TURNOVER INITIAL REQUEST PANEL do the following A Fill in the 3 required fields 1 Application name 2 Description 3 Request Impact B Select option 4 On line Application 6 The second panel the ON LINE TURNOVER REQUEST ENTRY PANEL requires the fo
Download Pdf Manuals
Related Search