Category of Work

S No 1 2 3 4 5 6

New JCL 7 8 9 10

11 12 13 14 15 16

Checklist Item Ensure that the jobname starts with the application name. E.g A new JCL in KAC should start than the Jobname is a new one and does not already exist with KAC The jobname is 8 characters at the max If the new job calls a procedure then ensure that there is a proc stepname for easier restarts in case of abend The JCL or PROC should have short description of each step as comments and all the steps in the JCL or PROC should be mentioned at the start with short description All the components in the new Job (Ctllib, datasets) etc should follow the naming standards. All the control lib's should also start with the application name. Datasets should also follow the production naming standards D966.XXXSQ.* for a sequential file D966.XXXVK.* for a VSAM file D966.XXXPO.* for a partitioned dataset D966.FINSQ.* for a sequential dataset name which is updated by users using some mainframe frontend screen D966.FINVK.* for a VSAM dataset name which can be updated by users using some Mainframe frontend screen XXX- Application name Internally created datasets should be deleted first before recreation Tape datasets retention period should be logically chosen The zeke event for the new jobname should be created well in advance having start date in the OCCURS clause The cc codes should be updated in the zeke event and reviewed. The format for updating the zeke cc codes is Stepname Procstepname Returncode Operator Action Make sure that the stepname and Procstepname are appropriately updated and reviewed All the GDG bases used in the new Job should be created Using parameters in the PROC is a good practice for easier restarts Verify if dummydummy generation is created in the job to bases (ifany JCL Errors (If input's generations are created for the new GDG prevent required) required) If there are other zeke events that have a dependency on the new job then have them updated with WEOJ clause instead of EOJ. This will help you manage the schedules better Whenever we test the new job, make sure that you run it twice to catch any JCL Errors

Compliance(Y/N)

Comments

Category of WorkNo S 1

3 4 5 New Program 6 7 8 9 10

Checklist Item Compliance(Y/N) Check the sourcelib's and verify if the new program name already exists. The PLI program source lib is 'D901.CMNPO.FINAN.SOURCE' and the APS program sourcelib is 'D999.CFMPO.PRODAPS.APSPROG' Ensure that the program name is consistent with the Application name .E.g A new program in KAC application should start with KAC instead of choosing a functionality name for the program. Eg. For a program to create a financial report in KAC. The program name should not be FINRPT An APS program name should not be more than 8 characters and a PLI program name should not be more than 7 characters The program should contain a brief description of what it does The program should have a modification log which lists out the ticket no, date, coder name and description of change Program should not have any unnecessary displays, especially no displays in loops. Program should have good exit logic and should display appropriate information like counts etc Empty input file handling should be in place and tested All the logic should not be cluttered at one place, instead code should be logically broken down in paragraphs For APS, the paragraph names should be progressive in nature and a higher paragraph should never call a lower paragraph. Example para 2000 should not call para 1000.

Comments

Category of Work No S 1 2 3 4

5 New PROC

6 7 8 9 10 11 12

Checklist Item Compliance(Y/N) Ensure than the PROC name is a new one and does not already exist Ensure that the procname starts with the application name. E.g A new PROC in KCL should start with KCL The procname is 8 characters at the max The PROC should have short description of each step as comments and all the steps in the PROC should be mentioned at the start with short description All the components in the new PROC (Ctllib, datasets) etc should follow the naming standards. All the control lib's should also start with the application name. Datasets should also follow the production naming standards D966.XXXSQ.* for a sequential file D966.XXXVK.* for a VSAM file D966.XXXPO.* for a partitioned dataset D966.FINSQ.* for a sequential dataset name which is updated by users using some mainframe frontend screen D966.FINVK.* for a VSAM dataset name which can be updated by users using some Mainframe frontend screen XXX- Application name Internally created datasets should be deleted first before recreation Tape datasets retention period should be logically chosen All the GDG bases used in the new Job should be created Using parameters in the PROC is a good practice for easier restarts Verify if dummy generations are created for the new GDG bases (if required) Verify if input's dummy generation is created in the proc to prevent any JCL Errors (If required) Whenever we test the new proc, make sure that you run it twice to catch any JCL Errors

Comments

Category of Work S No 1 2 3 4 5 New Connect Direct 6

Checklist Item Compliance(Y/N) If GDG is used then make sure that always zero generation of the GDG is sent via connect direct and not the +1 that is created in the job Make sure that cc code 4 is added to the zeke cc table for the event Make sure that the LRECL parameter matches the actual record length of the transferred file If the transfer control card is long enough to span acrosss multiple lines, make sure that correct format is used Double check on the transfer filename spelling. E.G If the filename is supposed to be 'ledger.txt', make sure it is spelled correctly and that it is not 'legder.txt' While setting a new connect direct, it is possible that a already existing procedure can be used for the new setup. Ensure that all the functionalities of the existing procedure match the new requirement. It is possible that the existing procedure has a 'run task' step which is not required in the new setup. To create a new procedure the CHGMAN library type is 'PRO' and the production library for the procedure is 'D955.NDM.PROCESS.LIB' and the JCL should be updated accordingly When testing the Connect Direct process, change the filename to a test name to prevent kicking off any process at the destination unless required.

Comments

Category of Work S No

CHGMAN(Temp orary package)

Checklist Item 1 Package Type Should be Unplanned 2 Package Time Span should be Temporary 3 Reason Code = 911 4 Duration = Any days from 1 to 7 5 Contingency = 1(Non-Critical) or not 6 Scheduler = CMN Install Date should be same as the Date of installing the 7 temporary package 8 Freezed the package or not 9 Control lib's cannot be moved in a temporary package work Request Id should have the Ticket no for which the 10 package was created 1 Package Type is Permanent 2 Package Time span is Perm 3 Scheduler = Manual Install Date should be a distant future date for year 2011, it 4 can be 20111231 work Request Id should have the Ticket no 5 for which the package was created Description should be filled with Ticket no 6 for which the package was created

CHGMAN(Perma nent package)

Compliance(Y/N) Comments

S. No

Best Practice While setting up a new Connect Direct process, add 8 as the valid return code for the C:D step. Watch the first process manually and when it completes successfully then get RC=8 removed from the zeke cc table. This will save us from any Connect Direct abends if the process fails the 1 first time due to some typo errors while creating a new program make sure that the following soft rules are applied. 1. If an array is setup then keep the limit of the array atleast 50% more than the currect value and add displays to the program for any warning messages once 80% of the threshold is reached 2. Make sure that the program is coded in such a way that array position 0 is handled. If the array requirements are such that in future it is possible that position zero is going to be accessed then always use position shifting eg. for array size 10 it can be given as array(0:9) and the zero position can be accessed in the program 2 3. If a new event is created for a new job which has to be a dataset triggered and if there is a possibility for the job to kick off during the schedule refresh time in the morning between 6:00 AM to 6:15AM then 3 create the new event as permanent When we install a temporary package for 7 days then by default it does stay put for 7 days from the time of deployment. The calculation is as follows. For example we deployed the package on 01/01/2011 for 7 days at 11:00 am EST with implementation start time as 00:00 hrs and implementation end time as 23:59 (default in most cases). In this case the package would have backed out on 01/07/2011 at 23:59 and not on 01/08/2011 at 11:00 AM as expected. So the best practice is to give the implementation start time as the time when the package is going to be installed (11:00 4 instead of 00:00)

Component Type

JCL

Source program

Zeke

CHGMAN