DATE: 11/06/85

SECTION: PRODUCTION ACCEPTANCE REVISED:

SUBJECT: GENERAL INFORMATION

FOR ANY SYSTEM TO BE ACCEPTED INTO OPERATIONS IT MUST BE SUBMITTED TO STANDARDS AND PROCEDURES FOR REVIEW. IT MUST THEN GAIN THE APPROVAL OF OPERATIONS BY SUCESSFULLY COMPLETING SEVERAL PRODUCTION RUNS AS SPECIFIED BY DOCUMENTATION. THE SYSTEM WILL BE CONSIDERED OPERATIONAL ONLY AFTER THESE STEPS ARE COMPLETED.

THE PROGRAMMING LANGUAGES THAT WILL BE ACCEPTABLE FOR PRODUCTION WORK AT THIS INSTALLATION ARE COBOL, FORTRAN, ASSEMBLER, AND DATA ANALYZER.

IN ORDER TO STANDARDIZE, ALL EFFORTS MUST BE MADE TO WRITE YOUR PROGRAMS IN COBOL. ALL PL1 PRODUCTION PROGRAMS MUST HAVE THE WRITTEN APPROVAL OF THE SYSTEM VICE PRESIDENT FOR COMPUTING AFFAIRS.

CHAPTER: OPERATIONS NUMBER: 6.2.02.01

DATE: 11/06/85

SECTION: PRODUCTION ACCEPTANCE REVISED: 06/06/91

SUBJECT: PRODUCTION SUBMISSIONS

¢BOVERVIEW¢P

THIS STANDARD IS INTENDED TO CLARIFY AND IDENTIFY THE STEPS INVOLVED IN TRANSFERRING MEMBERS FROM TEST TO PRODUCTION STATUS. THE GUIDELINES DESCRIBED ARE SUMMARIES OF REQUIREMENTS GIVEN IN THE NOTED CSD STANDARDS MANUAL SECTIONS. THESE SECTIONS SHOULD BE REFERRED TO FOR COMPLETE COVERAGE OF TOPICS.

ALL WORK IS ROUTED THROUGH THE STANDARDS DEPARTMENT IN THE DBA GROUP. ALL WORK IS THEN FORWARDED TO PRODUCTION CONTROL (PC) AFTER REVIEW AND APPROVAL, OR IS SENT BACK TO THE REQUESTING PROGRAMMER/ANALYST WHEN ITEMS ARE FOUND THAT DO NOT MEET CSD REQUIREMENTS. PRODUCTION CONTROL PERSONNEL ALSO REVIEW AND APPROVE THE WORK BEFORE UPDATING PRODUCTION CONTROL AND OPERATIONS FILES AND MANUALS. IF ERRORS ARE FOUND, PRODUCTION CONTROL NOTIFIES THE PROGRAMMER/ANALYST WHO MAKES CORRECTIONS AND RESUBMITS THE WORK THROUGH STANDARDS.

CHAPTER: OPERATIONS NUMBER: 6.2.02.02

DATE: 11/06/85

SECTION: PRODUCTION ACCEPTANCE REVISED: 09/16/97

SUBJECT: PRODUCTION SUBMISSIONS

WHEN SUBMITTING NEW OR MODIFIED WORK TO STANDARDS FOR ACCEPTANCE, AMPLE TIME SHOULD BE ALLOWED FOR BOTH STANDARDS PROCESSING AND PRODUCTION CONTROL PROCESSING. FOR NEW SYSTEMS OR MAJOR MODIFICATIONS TO EXISTING SYSTEMS, FIVE (5) WORKING DAYS SHOULD BE ALLOWED. MINOR MODIFICATIONS GENERALLY REQUIRE ONLY TWO WORKING DAYS. THE PROGRAMMING STAFF SHOULD UNDERSTAND THE TURNOVER PROCESS, EVALUATE THE WORK NEEDED TO TRANSFER THE NEW OR CHANGED MEMBERS, AND PLAN A REASONABLE TIMEFRAME FOR THE TRANSFER TO BE COMPLETED. TURNOVER NEEDS AND TIMETABLES SHOULD BE DISCUSSED WITH STANDARDS TO WORK OUT A SCHEDULE OF ACTIVITIES TO TRANSFER MEMBERS TO PRODUCTION STATUS.

JCL AND JOB DOCUMENTATION CHANGES ARE TRANSFERRED AT NOON EACH DAY, WHILE PROGRAMS ARE SET UP BY 4:00 PM DAILY FOR THE EVENING BATCH RUNS OF THE PROGRAM TRANSFER JOBS. ADEQUATE TIME FOR REVIEW, SPECIALLY FOR JOB TURNOVERS, MUST BE ALLOWED PRIOR TO THESE PROCESSING TIMES.TURNOVER REQUESTS WILL BE HELD UNTIL THE NEXT DAY IF REVIEW AND RESOLUTION OF ANY PROBLEMS HAVE NOT COMPLETED BY STANDARDS STAFF.

BLANK COPIES OF FORMS NEEDED FOR THE TURNOVER PROCESS ARE KEPT IN THE DBA OFFICES AND ARE ALSO AVAILABLE ON JETFORMS. COMPLETED TURNOVER PACKAGES ARE TO BE PLACED IN THE APPROPRIATE MARKED BOXES IN THE DBA OFFICE AREA WHEN READY FOR TRANSFER. WHEN ONLY PROGRAM CHANGES HAVE BEEN MADE, PLACE THE PROGRAMS AND RELATED ITEMS, SUCH AS FORMATS AND PSB AND RUDB REQUESTS IN THE BOX MARKED "PROGRAMS AND SCREEN FORMATS". WHEN THERE ARE BOTH JOB CHANGES AND PROGRAM CHANGES, PUT ALL OF THE FORMS AND LISTINGS TOGETHER AS ONE PACKAGE IN THE BOX MARKED "JOBS AND OTHER DOCUMENTATION".

DECISION ANALYZER FILE DEFINITION AND PROC LOADS TO PRODUCTION LIBRARIES REQUIRE SPECIAL HANDLING AND CAN BE GIVEN TO ANY DBA GROUP MEMBER TO PROCESS.

ALL MEMBERS BEING TURNED OVER TO PRODUCTION STATUS MUST HAVE NUMBERS ASSIGNED USING THE ONLINE STANDARDS SYSTEM ON TSO/ISPF(STDS).

THE NUMBERS MASTER PROGRAM (STDS.1) ALLOWS THE PROGRAMMING STAFF TO INQUIRE AND ASSIGN NUMBERS AS NEEDED.

CHAPTER: OPERATIONS NUMBER: 6.2.02.03

DATE: 11/06/85

SECTION: PRODUCTION ACCEPTANCE REVISED: 09/16/97

SUBJECT: PRODUCTION SUBMISSIONS

¢BPRODUCTION JOB ACCEPTANCE REPORT¢P

THE PRODUCTION JOB ACCEPTANCE REPORT FORM (STANDARD 7.2.14.01) SHOULD ACCOMPANY ALL TRANSFERS OF JCL AND JOB DOCUMENTATION FROM TEST TO PRODUCTION STATUS. THIS FORM IS NOT NEEDED IF ONLY PROGRAM CHANGES ARE BEING TURNED OVER (SEE CHANGE TO PRODUCTION STATUS). THIS FORM SERVES AS A CHECKLIST BY THE PROGRAMMING STAFF, AND BY STANDARDS AND PRODUCTION CONTROL IN IDENTIFYING AND REVIEWING THE ITEMS BEING TURNED OVER TO PRODUCTION STATUS.

A JOB/SCAN (JS) EDIT OF THE JCL MUST BE DONE BY THE PROGRAMMER/ANALYST PRIOR TO TURNOVER. USE SCREEN JS.1 ON TSO/ISPF TO PRODUCE AND PRINT A COPY OF THE EDIT FOR SUBMISSION TO STANDARDS ONCE ALL OF THE ERRORS THAT WILL CAUSE PRODUCTION PROBLEMS HAVE BEEN CORRECTED.

THE PANVALET USER CODE OF THE JCL MEMBER ON CPROD.TEST.PANLIB SHOULD MATCH THE PROGRAMMER'S TSO USER ID ON THE PRODUCTION JOB ACCEPTANCE REPORT FORM TO PREVENT ERRORS IN THE PANVALET TRANSFER JOB.

THE PANVALET LEVEL NUMBER SHOULD BE FURNISHED TO INSURE THAT THAT THE CORRECT VERSION OF THE MEMBER IS TRANSFERRED.

CHANGES TO PRODUCTION JCL SHOULD BE CLEARLY DESCRIBED ON THE PRODUCTION JOB ACCEPTANCE REPORT FORM.

GIVE A SPECIFIC DATE AFTER "WHEN WILL JOB RUN AGAIN". LEAVING THIS FIELD BLANK OR WRITING "AS REQUESTED" OR "USER SUBMITTED" DOES NOT COMMUNICATE ANYTHING TO PRODUCTION CONTROL ABOUT THE TIMEFRAME FOR COMPLETING THE TURNOVER PROCESS. THIS BLANK IS FOR TELLING WHEN, NOT HOW OR BY WHOM, A REVISED JOB IS TO BE RUN. IF NOT FURNISHED, A WEEK FROM THE TIME OF TURNOVER IS ASSUMED.

MASTER COPIES OF JOB DOCUMENTATION ARE MAINTAINED IN SYSTEMS MANUALS BY THE PROGRAMMING STAFF. LEGIBLE COPIES OF CHANGED FORMS ARE NEEDED BY PRODUCTION CONTROL AND SHOULD FIRST BE SENT TO STANDARDS FOR REVIEW AND APPROVAL. COMPUTER RUN SHEETS ARE NO LONGER REQUIRED AS THE DOCU/TEXT PRODUCT ON TSO/ISPF WILL GENERATE FLOWCHARTS ON DEMAND FROM THE JCL. IT IS THE PROGRAMMERS RESPONSIBILTIY TO UPDATE THE SHORT DESCRIPTION FIELDS (DT.5) FOR ALL OUTPUT SO THAT THIS FIELD WILL NOT BE BLANK ON THE DOCU/TEXT FLOWCHART. ORIGINAL FORMS ARE TO BE FILED BY THE PERSONS RESPONSIBLE FOR MAINTAINING THE SYSTEMS MANUALS.

CHAPTER: OPERATIONS NUMBER: 6.2.02.04

DATE: 11/06/85

SECTION: PRODUCTION ACCEPTANCE REVISED: 09/16/97

SUBJECT: PRODUCTION SUBMISSIONS

A MEMBER SHOULD EXIST ON CPROD.TEST.PANLIB UNDER THE PRODUCTION JOB NAME. THE STANDARDS DEPARTMENT WILL SUBMIT ALL JCL AND DOCUMENTATION THAT HAS BEEN APPROVED BY 12 NOON EACH DAY TO PRODUCTION CONTROL. THE JCL IS TRANSFERRED BY A BATCH JOB WHICH COPIES THE APPROVED MEMBERS TO CPROD.STDS.PANLIB. THE USE OF UNASSIGNED JOB, STEP, RDN, AND OTHER MEMBER NUMBERS WILL BE IDENTIFIED AT THIS POINT AND TURNOVER WILL BE DELAYED UNTIL THE PROGRAMMER/ANALYST IS NOTIFIED AND THE ERRORS CORRECTED.

THE DOCUMENTATION IS TAKEN TO PRODUCTION CONTROL AFTER THE OUTPUT OF THE BATCH STANDARD TURNOVER JOB IS CHECKED FOR A SUCCESSFUL TRANSFER RUN. PRODUCTION CONTROL TRANSFERS THE JOBS TO CAI.CA7.PANLIB FOR REVIEW AND TO PREPARE THEM FOR PRODUCTION WORK.

CHAPTER: OPERATIONS NUMBER: 6.2.02.05

DATE: 11/06/85

SECTION: PRODUCTION ACCEPTANCE REVISED: 09/16/97

SUBJECT: PRODUCTION SUBMISSIONS

¢BCHANGE TO PRODUCTION STATUS¢P

THE CHANGE TO PRODUCTION STATUS FORM (STANDARD 7.2.12.01) IS USED TO INDICATE THAT PROGRAMS, SCREENS, OR INCLUDES ARE TO BE TRANSFERRED FROM TEST TO PRODUCTION STATUS. THIS FORM IS NOT NEEDED FOR UTILITIES, SORTS, OR DATA ANALYZER PROGRAMS WHICH ARE TURNED OVER IN JCL.

THE SIGNATURE OF THE PROGRAMMER/ANALYST IS REQUIRED BY STANDARDS AS AUTHORIZATION FOR THE TRANSFER AND PRODUCTION UPDATE. THIS SIGNATURE INDICATES THAT THE PROGRAMMER/ANALYST HAS TESTED THE THE CHANGED MEMBER THOROUGHLY, INCLUDING ERROR HANDLING AND ALL PROGRAM FUNCTIONS. IT IS THE RESPONSIBILITY OF THE PROGRAMMING STAFF TO COMMUNICATE WITH THE APPROPRIATE SYSTEM USER DEPARTMENTS AND TO MAINTAIN WRITTEN DOCUMENTATION OF THE USER'S APPROVAL TO PUT THE REQUESTED CHANGES OR NEW MEMBERS INTO PRODUCTION. APPROVAL BY APPLICATION TEAM LEADERS OR MANAGERS IS NOT REQUIRED UNLESS REQUESTED OF STANDARDS FOR A TEAM OR GROUP.

TO PREVENT ERRORS IN THE PANVALET TRANSFER JOB STEP THE USER CODE ON PANVALET OF THE MEMBER BEING TURNED OVER SHOULD MATCH THE "PROG/ANALYST ID NUMBER" FIELD ON THE CHANGE TO PRODUCTION STATUS FORM. THE LEVEL NUMBER ON PANVALET OF THE MEMBER SHOULD BE THE SAME AS THE "PANVALET LEVEL" FIELD ON THE CHANGE TO PRODUCTION STATUS FORM.

POGRAMS REVIEWS AND APPROVAL BY DBA STAFF ARE NOT REQUIRED FOR TURNOVER TO PRODUCTION STATUS; THEREFORE, COMPILE LISTINGS SHOULD NOT BE SENT TO STANDARDS.

PSB REQUESTS SHOULD BE TURNED OVER WITH THE IMS PROGRAMS AND WILL BE COMPILED THE DAY THE PROGRAM IS TRANSFERRED.

NEW IMS PROGRAMS AND TRANSACTIONS REQUIRE ENTRIES IN THE IMS GEN WHICH IS RUN EVERY TWO WEEKS. THE SCHEDULE DISTRIBUTED BY THE DBA GROUP SHOULD BE CHECKED AND TURNOVERS PLANNED ACCORDINGLY (IE, REQUEST ITEMS FOR THE IMS GEN WITH SUFFICIENT TIME TO BE PROCESSED ON THE REGULARLY SCHEDULED IMS GEN DATES). THE DEADLINE FOR SUBMISSION IS ALWAYS NOON ON THE THURSDAY BEFORE THE IMS GEN JOB RUN.

CHAPTER: OPERATIONS NUMBER: 6.2.02.06

DATE: 11/06/85

SECTION: PRODUCTION ACCEPTANCE REVISED: 09/17/97

SUBJECT: PRODUCTION SUBMISSIONS

PROGRAMS, SCREENS, AND INCLUDES FOR JOBS TRANSFERRED TO PRODUCTION CONTROL AT NOON ARE SET UP BY 4:00 PM EACH DAY FOR THE EVENING TURNOVER RUN BY STANDARDS. THE PROGRAMMER/ANALYST SHOULD CROSS-REFERENCE AND LIST ON THE CHANGE TO PRODUCTION STATUS FORMS THE JOBS AND PROGRAMS BEING TURNED OVER TOGETHER TO INSURE THAT THEY ARE TRANSFERRED ON THE SAME DAY. ALSO TRANSFERRED AT 4:00 PM ARE PROGRAMS, SCREENS, AND INCLUDES TURNED OVER WITHOUT JOB CHANGES WHICH HAVE BEEN BROUGHT TO STANDARDS PRIOR TO THAT TIME. NEW JOBS AND JOBS WITH JCL CHANGES BROUGHT TO STANDARDS AFTER 4:00 PM ARE NOT PROCESSED UNTIL THE NEXT WORKING DAY. ALSO, PROGRAMS TO BE TRANSFERRED CONCURRENTLY WITH JOBS BROUGHT DOWN AFTER NOON ARE NOT SET UP FOR TRANSFER UNTIL THE DAY THE JOBS HAVE BEEN TRANSFERRED TO PRODUCTION CONTROL.

JOB C600814A RUNS FIRST IN THE BATCH EVENING TURNOVER RUN BY PRODUCTION CONTROL AND UPDATES CPROD.PROD.PANLIB BY TRANSFERRING INCLUDES, SAVE AREAS, AND ROUTINES FROM CPROD.TEST.PANLIB, AND THEN SUBMITS COMPILES OF ANY ROUTINES TO THE INTERNAL READER. C600824A IS RUN AFTER C600814A AND ANY COMPILES SUBMITTED ARE COMPLETED. C600824A TRANSFERS PROGRAMS TURNED OVER FROM CPROD.TEST.PANLIB TO CPROD.PROD.PANLIB, THEN SUBMITS COMPILE RUNS FOR EACH PROGRAM THROUGH THE INTERNAL READER. IF RECOMPILES ARE NEEDED OF CPROD.PROD.PANLIB MEMBERS BECAUSE OF A TRANSFERRED INCLUDE OR ROUTINE, THEN JOB C600834A IS SCHEDULED FOR RUNNING AFTER C600824A. NOTE, C600834A DOES NOT TRANSFER MEMBERS FROM TEST PANVALET LIBRARIES,BUT ONLY SUBMITS COMPILE JOBS TO THE INTERNAL READERS FOR MEMBERS ALREADY ON CPROD.PROD.PANLIB.

THE MEMBERS TO BE COMPILED ARE SET UP USING THE ONLINE STDS SYSTEM ON ISPF/TSO. THE STDS SYSTEM CROSS-REFERENCE FEATURE ALONG WITH ANY SPECIAL INSTRUCTIONS INCLUDED ON THE TURNOVER FORMS ARE USED TO DETERMINE WHAT MEMBERS TO RE-COMPILE. THIS ONLINE CROSS-REFERENCE INQUIRY IS AVAILABLE TO THE PROGRAMMING STAFF AND SHOULD BE USED TO ANALYZE THE EFFECTS OF ANY REQUESTED TRANSFERS,INCLUDING ROUTINE HANDLING.

A SPECIAL FILE IS WRITTEN TO IN THE COMPILE RUN IF THE COMPILE FAILS: DBA.CONDCODE.D01. THIS FILE IS BROWSED EACH MORNING BY STANDARDS TO IDENTIFY COMPILE PROBLEMS. AN "EMPTY" FILE INDICATES THAT ALL JOBS HAVE COMPILED SUCCESSFULLY. MEMBERS WITH FAILED COMPILE RUNS ARE WRITTEN TO THIS FILE ALONG WITH THE FAILED STEP AND CONDITION CODE. USUCCESSFUL COMPILES ARE BROUGHT TO THE IMMEDIATE ATTENTION OF THE PROGRAMMER/ ANALYST BY STANDARDS. RECOMPILES MAY BE DONE BY THE STAFF, OR BY THE STANDARDS/DBA GROUP. TO DETERMINE THE SPECIFIC COMPILE ERRORS, A "COMPILE-ONLY" JOB USING THE COBOL PARMS OF 'X,OFF' FOR THE MEMBER ON CPROD.PROD.PANLIB SHOULD BE RUN.

CHAPTER: OPERATIONS NUMBER: 6.2.02.07

DATE: 11/06/85

SECTION: PRODUCTION ACCEPTANCE REVISED: 06/06/91

SUBJECT: PRODUCTION SUBMISSIONS

EVERY EFFORT WILL BE MADE BY STANDARDS AND PRODUCTION CONTROL TO EXPEDITIOUSLY PROCESS NEW AND MODIFIED SYSTEMS THROUGH THE ACCEPTANCE PROCESS. IN CASES OF LARGE NUMBERS OF NEW OR REVISED JOBS AND PROGRAMS OR MAJOR RE-WRITES (ESPECIALLY IMS PROGRAMS POSSIBLY REQUIRING DATA BASE REORGANIZATIONS AND/OR AN IMSGEN UPDATE), THE PROGRAMMER/ANALYST SHOULD DISCUSS AND WORK OUT A TIME SCHEDULE WITH STANDARDS AND DBA PERSONNEL.

THE STANDARDS DEPARTMENT WILL RESPOND TO ANY SPECIAL REQUESTS FOR SITUATIONS WHERE NORMAL PROCESSING IS NOT ADEQUATE. FOR EXAMPLE, A PRODUCTION COMPILE MAY BE NEEDED OF AN ONLINE (TP) PROGRAM DURING FIRST SHIFT TO ALLOW A USER DEPARTMENT TO CONTINUE WORKING. A WRITTEN REQUEST FROM A TEAM OR GROUP MANAGER SHOULD BE MADE TO STANDARDS FOR SPECIAL HANDLING AND/OR PRIORITY TREATMENT. THESE REQUESTS SHOULD BE ON AN EXCEPTION BASIS AND KEPT TO A MINIMUM.

CHAPTER: OPERATIONS NUMBER: 6.2.02.08

DATE: 11/06/85

SECTION: PRODUCTION ACCEPTANCE REVISED: 03/05/92

SUBJECT: PRODUCTION SUBMISSIONS

¢BJCL REQUIREMENTS¢P

SOME OF THE MORE IMPORTANT PRODUCTION JCL REQUIREMENTS AND CHANGES TO BE MADE WHEN CONVERTING FROM TESTING ARE OUTLINED BELOW. REFER TO SECTION V OF THE STANDARDS MANUAL AND TO IBM MANUALS FOR COMPLETE REQUIREMENTS.

-- CHANGE ALL STEPNAMES, PROGRAM NAMES, AND JOB NAMES TO THE NUMBERS ASSIGNED BY STANDARDS. UNASSIGNED NUMBERS ARE NOT ALLOWED IN PRODUCTION JOBS AND WILL BE REJECTED DURING TURNOVER.

 -- REMOVE ANY //SYSDBOUT STATEMENTS FROM THE JCL FOR ANY STEPS EXECUTING PROGRAMS COMPILED UNDER COBOL. THIS IS AN OUTPUT STATEMENT FOR "FLOW,STATE' OPTIONS NOT ALLOWED IN PRODUCTION.

 -- SYSABOUT STATEMENTS ARE ALLOWED AND OPTIONAL FOR STEPS EXECUTING PROGRAMS COMPILED UNDER COBOL. THIS IS AN OPTIONAL STATEMENT THAT WILL ALLOW PRINTING OF ADDITIONAL ABEND INFORMATION

-- SET UP SYSUDUMP STATEMENTS USING CLASS 'G' AND DEST=DUMP AS DESCRIBED IN STANDARD 5.1.04.04.

 -- REMOVE "PASS" AS A DATA SET DISPOSITIONAL PARAMETER AS IT IS NOT ALLOWED IN PRODUCTION JOBS. REFER TO STANDARD 5.1.04.01.

-- CHANGE ALL REFERENCES FROM TEST OBJECT LIBRARIES TO PRODUCTION OBJECT LIBRARIES. FOR EXAMPLE, FOR NON-IMS PROGRAMS PROGRAMS, CHANGE SCUCSD.TESTLIB TO USC.LINKLIB.

 -- SET UP JOB STATEMENTS AS THE JOB WILL BE RUN BY PRODUCTION CONTROL (AS SHOWN IN THE FOLLOWING EXAMPLE). REMOVE TSO USER-ID, NOTIFY, MSGCLASS=C, PROGRAMMER'S NAME, TYPRUN=SCAN, AND OTHER PARAMETERS USED DURING TESTING. BE SURE TO UPDATE THE TIME AND REGION PARAMETERS TO AN ADEQUATE TIME INTERVAL AND REGION SIZE FOR SUCCESSFUL EXECUTION IN PRODUCTION - THESE PARAMETERS ARE NOT UPDATED BY PC. PRODUCTION CONTROL WILL SET UP AN INCLUDE STATEMENT AS THE LAST JOB STATEMENT WHICH WILL CONTAIN THE MSGLEVEL, USER AND PASSWORD PARAMETERS. THIS LAST JOB STATEMENT MAY BE CODED AS SHOWN IN THE EXAMPLE BELOW, AN INCLUDE STATEMENT MAY BE CODED, OR THIS STATEMENT MAY BE LEFT OUT ENTIRELY. IF ADDITIONAL PARAMETERS ARE NEEDED, SUCH AS REGION OR TYPRUN=HOLD, SET UP A SECOND LINE AS SHOWN BELOW. REFER TO STANDARD 5.1.02.01.

CHAPTER: OPERATIONS NUMBER: 6.2.02.09

DATE: 11/06/85

SECTION: PRODUCTION ACCEPTANCE REVISED: 06/06/91

SUBJECT: PRODUCTION SUBMISSIONS

NOTE, THE PRODUCTION ACCOUNT NUMBER MUST BE SPECIFIED BY THE PROGRAMMING STAFF AND SHOULD BE DOUBLE-CHECKED FOR ACCURACY AS THIS IS THE NUMBER THAT WILL BE USED FOR BILLINGS.

//F950004A JOB (F9500018,99),'I/O CONTROL',TIME=5,

// REGION=1024K,TYPRUN=HOLD,

// USER=C0999,PASSWORD=????????,MSGLEVEL=(1,1) OR ++INCLUDE XF95

-- CHANGE ALL HIGH LEVEL QUALIFIERS TO THE APPROPRIATE PRODUCTION HIGH LEVEL QUALIFIER NAMES. FOR EXAMPLE, FROM C0100 TO CPROD.

 -- BE SURE THE PRODUCTION PSB NAME IS USED (NOT THE TEST PSB). THE PSB NUMBER ON THE EXEC STATEMENT MUST MATCH THE PROGRAM STEPNAME WITH THE EXCEPTION OF AN "EXECUTE" PROGRAM NUMBER ('EA'). REFER TO STANDARD 5.1.03.01.

-- USE THE VALID PRODUCTION IMS EXEC STATEMENT, IMSBPROD, NOT IMSBTEST. IMSBPROD AND IMSBTEST REPLACED IMSBATCH WHEN THE INSTALLATION WAS MADE OF THE DUAL (TEST AND PRODUCTION) IMS SYSTEM. IMSBATCH IS STILL FUNCTIONAL BUT ALL PRODUCTION JOBS SHOULD NOW BE SET UP FOR IMSBPROD.

-- TAKE OUT ANY CONTROL "CARDS" USED IN TESTING UNLESS THEY ARE PERMANENT CONTROL STATEMENTS TO BE USED IN PRODUCTION RUNS. SET UP A COMMENT CARD SIMILAR TO THE FOLLOWING FOR PERMANENT CONTROL CARDS AND PLACE PRIOR TO THE ACTUAL CONTROL CARDS.

 //* PERMANENT CONTROL CARD(S) - DO NOT REMOVE FROM JOB DECK

-- "TEMPLATE" CARDS USED TO DOCUMENT CONTROL CARD FORMATS WITHIN THE JCL FOR USE BY PRODUCTION CONTROL MAY BE INCLUDED IN THE JCL. NOTE, THE FORMAT FOR CONTROL CARDS MUST BE FULLY DETAILED ON THE PROGRAM RUN SHEET FOR EACH STEP (REFER TO STANDARD 7.2.05.01).

-- USE THE OUTPUT JCL STATEMENT AS SPECIFIED IN STANDARD 5.1.05.01 FOR PRODUCTION JOB SYSOUT DATA SETS.

CHAPTER: OPERATIONS NUMBER: 6.2.02.10

DATE: 11/06/85

SECTION: PRODUCTION ACCEPTANCE REVISED: 06/06/91

SUBJECT: PRODUCTION SUBMISSIONS

¢BPROGRAM RUN SHEET¢P

THIS DOCUMENTATION IS NEEDED FOR EVERY JOB STEP, INCLUDING SORTS AND UTILITIES (REFER TO STANDARD 7.2.05.01).

-- DESCRIBE "CONTROL CARDS" IN DETAIL. IF PRODUCTION CONTROL IS TO CREATE, INDICATE WHETHER TO FOLLOW THE JOB REQUEST FORM FROM THE USER, TO FOLLOW KEYPUNCH INSTRUCTIONS (REFERENCE BY NUMBER), OR TO FOLLOW THE FORMAT DOCUMENTED ON THE PROGRAM RUN SHEET. ALSO, INDICATE IF A "TEMPLATE" CARD (OR CARDS) IS INCLUDED IN THE JCL.

-- BE SURE TO PROVIDE ADEQUATE RESTART INSTRUCTIONS FOR EACH STEP GIVING DETAILED DESCRIPTIONS OF ACTIONS TO BE TAKEN FOR ABENDS AND OTHER ERROR MESSAGES. IF THE PROGRAM GENERATES SPECIFIC RETURN CODES FOR UNIQUE ERROR CONDITIONS, LIST EACH WITH THE SPECIFIC ACTION FOR OPERATIONS OR PRODUCTION CONTROL TO TAKE.

 ¢BSCHEDULING AND RETENTION¢P

 -- ALL NEW JOBS NEED THIS FORM (STANDARD 7.2.03.01).

-- REFER TO STANDARD 7.2.03.01 FOR COMPLETE INSTRUCTIONS IN COMPLETING THIS FORM. NOTE, THAT THE DATA SET RETENTIONS FURNISHED FOR TAPES AND FOR DISK FILES KEPT AFTER A JOB RUN ARE USED BY PRODUCTION CONTROL TO SET UP TIME OR GENERATIONS. EVALUATE CAREFULLY TO CALCULATE ADEQUATE TIME OR FILE GENERATIONS NEEDED BY AN APPLICATION AND NOT EXCESSIVE LEVELS WHICH WILL NEVER LIKELY BE NEEDED.

 -- IF THE JOB IS TO BE SCHEDULED BY PRODUCTION CONTROL, CLEARLY DESCRIBE WHAT CRITERIA IS TO BE USED. FOR EXAMPLE, SPECIFY IF THE JOB IS TO BE 'TRIGGERED' BY ANOTHER, OR IF IT SHOULD BE RUN ON A CERTAIN DAY.

 -- IF THE JOB IS TO BE SCHEDULED BY A USER DEPARTMENT (IE, USER REQUEST), BE SURE TO TURN OVER A COPY OF THE USER REQUEST SHEET. BE SURE THE JOB NAME AND JOB NUMBER ARE CLEARLY SHOWN ON THE USER REQUEST SHEET, ALONG WITH ANY CONTROL CARD INFORMATION AND SPECIAL INSTRUCTIONS.

 -- IF THE JOB IS ACTUALLY RUN BY A USER DEPARTMENT (FOR EXAMPLE, FROM CMS), INDICATE SO IN THE COMMENT LINES AT THE BOTTOM.

CHAPTER: OPERATIONS NUMBER: 6.2.02.11

DATE: 11/06/85

SECTION: PRODUCTION ACCEPTANCE REVISED: 09/16/92

SUBJECT: PRODUCTION SUBMISSIONS

¢BREPORT DISTRIBUTION¢P

-- A REPORT DISTRIBUTION FORM (STANDARD 7.2.01.01) IS REQUIRED FOR EVERY REPORT PRODUCED BY A PROGRAM.

-- EACH DIFFERENT REPORT SHOULD HAVE A UNIQUE REPORT DISTRIBUTION NUMBER; IE, DO NOT USE AN EXISTING NUMBER OF A DIFFERENT REPORT BECAUSE THE OUTPUT OF BOTH REPORTS IS SENT TO THE SAME OFFICE. REFER TO STANDARD 2.3.14.01. IF A REPORT IS TO BE PRODUCED ON PAPER AND MICROFICHE, ONLY ONE REPORT DISTRIBUTION NUMBER IS NEEDED.

-- THE NUMBER OF COPIES PRODUCED MUST EQUAL THE NUMBER OF COPIES DESIGNATED FOR DISTRIBUTION ON THE FORM.

-- THIS FORM IS USED FOR BOTH MICROFICHE OUTPUT AND PRINTED OUTPUT. IF MICROFICHE AND PAPER OUTPUT SHARE THE SAME REPORT DISTRIBUTION NUMBER, SEPARATE DISTRIBUTION FORMS MUST BE COMPLETED AS TWO DIFFERENT AREAS OF OPERATIONS PROCESS MICROFICHE OUTPUT AND PAPER OUTPUT. NOTE, THE MICROFICHE REPORT DISTRIBUTION NUMBER IS DISPLAYED IN THE VISIBLE HEADER OF EACH FICHE. THE REPORT DISTRIBUTION NUMBER FOR PAPER OUTPUT IS PRINTED BY THE COMPUTER PROGRAM IN THE RIGHT HAND CORNER OF EACH PAGE.

 -- CLEARLY DESCRIBE ANY SPECIAL PROCESSING OR HANDLING FOR THE DISTRIBUTION AREA.

 ¢BCOMPUTER RUN SHEET¢P

 FLOWCHARTS ARE NOT REQUIRED BECAUSE OF THE FEATURE OF DOCU/TEXT THAT ALLOWS THESE TO BE CREATED ON DEMAND FROM THE JCL STATEMENTS.

CHAPTER: OPERATIONS NUMBER: 6.2.03.01

DATE: 11/06/85

SECTION: PRODUCTION ACCEPTANCE REVISED:

SUBJECT: ORIGINAL SUBMISSION - NEW SYSTEM

UPON COMPLETION OF A SYSTEM, THE FOLLOWING ITEMS ARE TO BE SUBMITTED TO THE STANDARDS AND PROCEDURES DEPARTMENT.

1. SYSTEMS MANUAL

2. TEST VERIFICATION CONTAINING:

A. JCL LISTING OF A SUCCESSFUL EXECUTION OF THE JOB STREAM. IF CONDITION CODES ARE USED, A SUCCESSFUL JCL LISTING IS REQUIRED FOR EACH DIFFERENT CONDITION.

B. REQUEST TO CHANGE TO PRODUCTION STATUS.

C. SAMPLE OUTPUT LISTING ALONG WITH AN ALIGNMENT ROUTINE IF APPLICABLE.

3. DATA SET RETENTION AND SCHEDULING FORM INDICATING NEW TAPES CREATED AND EXACT SCHEDULING OF JOB - BY REQUEST, FIXED TIMES, OR AS PART OF A JOB STREAM.

ALL SYSTEMS MANUALS ARE TO BE COMPLETED AS PER STANDARDS (4.2.01.01)

SOURCE WILL BE TAKEN DIRECTLY FROM PANVALET (CPROD.TEST.PANLIB, OBTAINED BY EXECUTING USCPAN).

CHAPTER: OPERATIONS NUMBER: 6.2.04.01

DATE: 11/06/85

SECTION: PRODUCTION ACCEPTANCE REVISED: 09/16/97

SUBJECT: ORIGINAL SUBMISSION - IMS APPLICATION

IMS BATCH AND BATCH MESSAGE PROGRAMS (BMP'S) ARE TO BE SUBMITTED TO THE STANDARDS DEPARTMENT FOR ACCEPTANCE INTO PRODUCTION STATUS AS DESCRIBED IN STANDARD NUMBER 6.2.02.01.

IMS ONLINE SYSTEMS (MESSAGE PROCESSING PROGRAMS (MPP'S) AND SCREEN FORMATS) HAVE DIFFERENT GUIDELINES FOR SUBMISSION TO THE STANDARDS DEPARTMENT FOR ACCEPTANCE INTO PRODUCTION STATUS. JOB NUMBERS ARE NOT REQUIRED FOR ONLINE PROGRAMS, AND THEREFORE NEITHER IS ANY 'JOB-RELATED' DOCUMENTATION. THE ONLY DOCUMENTATION REQUIREMENTS ARE FOR ONLINE PROGRAM USER INSTRUCTIONS AND PROGRAM RUN SHEETS. THESE TWO ITEMS ARE TO BE COMPLETED BY THE PROGRAMMING STAFF AND FILED IN THE APPROPRIATE SYSTEMS MANUAL WITHOUT REVIEW BY STANDARDS. THE PRODUCTION JOB ACCEPTANCE REPORT FORM IS NOT REQUIRED FOR MOVING ONLINE PROGRAMS AND SCREEN FORMATS INTO PRODUCTION. TO TURN OVER ONLINE SCREENS AND PROGRAMS TO PRODUCTION STATUS, SUBMIT THE FOLLOWING ITEMS TO THE STANDARDS DEPARTMENT:

1. PRODUCTION DBD, PSB AND IMSGEN REQUESTS AS NEEDED.

2. 'REQUEST TO CHANGE TO PRODUCTION STATUS' FORMS FOR SCREENS.

3. 'REQUEST TO CHANGE TO PRODUCTION STATUS' FORMS FOR ONLINE PROGRAMS.

THE SOURCE CODE MUST BE STORED ON CPROD.TEST.PANLIB USING THE APPROPRIATE PRODUCTION MEMBER NAME.

CHAPTER: OPERATIONS NUMBER: 6.2.05.01

DATE: 11/06/85

SECTION: PRODUCTION ACCEPTANCE REVISED:

SUBJECT: ORIGINAL SUBMISSION - MESSAGE FORMATS

MESSAGE FORMATS ALONG WITH THEIR INPUT DESCRIPTIONS WILL BE SUBMITTED TO STANDARDS AT THE TIME OF SUBMISSION OF THE ASSOCIATED ONLINE PROGRAM. THE FORMAT WILL THEN BE RECOMPILED AND PLACED ON THE IMS FORMAT LIBRARY AS WELL AS BEING PLACED ON THE PRODUCTION PANVALET LIBRARY.

SOURCE WILL BE TAKEN DIRECTLY FROM PANVALET (CPROD.TEST.PANLIB, OBTAINED BY EXECUTING USCPAN).

CHAPTER: OPERATIONS NUMBER: 6.2.06.01

DATE: 11/06/85

SECTION: PRODUCTION ACCEPTANCE REVISED: 09/16/97

SUBJECT: ORIGINAL SUBMISSION - DATA ANALYZER

RETRIEVALS USING THE DATA ANALYZER ARE ACCEPTABLE FOR PRODUCTION USE. THE JOB SHOULD BE SET UP USING THE CATALOGUE PROCEDURE 'ANALYZ' AND A STEPNAME SHOULD BE OBTAINED FROM STANDARDS SHOWING A PROGRAM TYPE OF "D". THE JOB NAME MUST ALSO BE ASSIGNED BY THE PROGRAMMER USING THE NUMBERS MASTER TSO/ISPF PROGRAM (STDS.1). UPON SUCCESSFUL COMPLETION OF A RETRIEVAL JOB OR ADDITION OF A RETRIEVAL STEP TO AN EXISTING JOB, THE FOLLOWING ITEMS ARE TO BE SUBMITTED TO STANDARDS AND PROCEDURES.

1. SYSTEM MANUAL AS PER STANDARD (4.4.01.01)

2. SAMPLE RUN OF JOB

3. DATA SET RETENTION AND SCHEDULING FORM INDICATING EITHER THE SPECIFIC SCHEDULING OR HAVING ATTACHED TO IT A COPY OF THE REQUEST SHEET.

DATA ANALYZER JOBS MAY INCLUDE TEMPORARY FILE AND DATA DEFINITION (FDD'S). PERMANENT FDD'S AS WELL AS MACROS AND PROCS WILL BE ADDED ONLY BY THE STANDARDS DEPARTMENT IN ORDER TO MAINTAIN FILE INTEGRITY.

CHAPTER: OPERATIONS NUMBER: 6.2.07.01

DATE: 11/06/85

SECTION: PRODUCTION ACCEPTANCE REVISED: 09/16/97

SUBJECT: CHANGES TO PRODUCTION SYSTEMS

ALL CHANGED PROGRAMS ARE TO BE COMPILED FROM CPROD.TEST.PANLIB TO SCUCSD.TESTLIB (OR IMSVS.PGMTEST, FOR ONLINE TELEPROCESSING PROGRAMS) FOR SUBSEQUENT TESTING. ALL CHANGES ARE TO BE TESTED BEFORE TURNING THE WORK BACK IN THROUGH THE STANDARDS DEPARTMENT. SOURCE CODE BEING SUBMITTED TO STANDARDS WILL REQUIRE A "REQUEST TO CHANGE TO PRODUCTION STATUS" FORM (PAGE 7.1.6.1). CHANGED DOCUMENTATION MUST BE REMOVED FROM THE SYSTEMS MANUAL AND SUBMITTED TO STANDARDS TO ENSURE THAT THE APPROPRIATE COPIES ARE MADE AND DISTRIBUTED. NO CHANGES TO A PRODUCTION SYSTEM WILL BE ACCEPTED BY OPERATIONS EXCEPT THROUGH THE STANDARDS AND PROCEDURES DEPARTMENT.

PREVIOUS VERSIONS OF PANVALET MEMBERS MAY BE RETRIEVED FOR THE PROGRAMMING STAFF BY STANDARDS FROM EITHER THE PRODUCTION PANVALET OR TEST PANVALET BACKUP FILES UPON REQUEST.

ALL CHANGES SUBMITTED MUST MEET THE CURRENT STANDARDS ESTABLISHED FOR ORIGINAL SUBMISSION.

CHAPTER: OPERATIONS NUMBER: 6.2.08.01

DATE: 11/06/85

SECTION: PRODUCTION ACCEPTANCE REVISED:

SUBJECT: CHANGES TO PRODUCTION FILES

WHEN A CHANGE TO BE MADE TO A PRODUCTION FILE OR DATA BASE OR ONE IS TO BE DELETED, ADEQUATE CONSIDERATION MUST BE GIVEN TO THE IMPACT ON OTHER SYSTEMS. TO FACILITATE THIS, THE FOLLOWING PROCEDURE HAS BEEN IMPLEMENTED.

WHEN A CHANGE IS TO BE MADE TO A FILE, THE NOTIFICATION OF FILE/DATA BASE CHANGE MUST BE COMPLETED, INCLUDING THE SIGNATURE OF THE MANAGER OVERSEEING IMPLEMENTATION OF THE CHANGE. THE FORM SHOULD THEN BE SUBMITTED TO THE STANDARDS DEPARTMENT WHICH WILL DISTRIBUTE COPIES TO ALL MANAGERS. PARTICULAR NOTE SHOULD BE GIVEN TO JOBS NOW ACCESSING THE FILE OR DATA BASE. MANAGERS WILL THEN HAVE ONE WEEK TO SUBMIT A FORMAL REQUEST TO STANDARDS TO MODIFY OR DELAY THE CHANGE. IF DIFFERENCES EXIST, STANDARDS WILL ATTEMPT TO RECONCILE THEM.

THE ONLINE STANDARDS SYSTEM ON TSO/ISPF SHOULD BE USED BY PROGRAMMERS TO CROSS-REFERENCE THE EFFECTS OF CHANGES TO A MEMBER (STDS.3).

CHAPTER: OPERATIONS NUMBER: 6.2.09.01

DATE: 11/06/85

SECTION: PRODUCTION ACCEPTANCE REVISED:

SUBJECT: PRODUCTION SUBMISSION, OPTICAL SCANNING

JOBS THAT USE TAPES CREATED BY OPTICAL SCANNING DEVICES MUST USE APPROVED OPTICAL SCANNING FORMS (SEE STANDARD 4.4.16.1). IN ADDITION TO THE ITEMS COVERED IN STANDARD 7.1.2.1, THE FOLLOWING ITEMS ARE NECESSARY:

1. A FORMAT CONTROL SCHEET FOR IBM-3881. THE SHEET(S) SHOULD INCLUDE AN EAM NUMBER.

2. THE LATEST OPSCAN JOB SUBMISSION SHEET COMPLETED BY THE OPTICAL SCANNING OPERATOR.

3. THE JCL LISTING SHOWING A SUCCESSFUL RUN OF THE JOB USING THE TAPE CREATED IN STEP 2 ABOVE.

CHAPTER: OPERATIONS NUMBER: 6.2.10.01

DATE: 11/06/85

SECTION: PRODUCTION ACCEPTANCE REVISED:

SUBJECT: PRODUCTION JOB DELETION

OPERATIONS WILL BE NOTIFIED OF ANY PRODUCTION JOBS BEING DELETED OR REPLACED THROUGH THE STANDARDS DEPARTMENT. PROGRAMMERS REQUESTING DELETION WILL SUBMIT A DELETION REPORT FORM (7.2.13.01) TO STANDARDS SPECIFYING JCL, SOURCE, AND ANY ASSOCIATED DOCUMENTATION TO BE REMOVED FROM PRODUCTION CONTROL AND THE STANDARDS DEPARTMENT. IN THE COLUMN MARKED "COMMENTS", THE REQUESTOR MUST INCLUDE THE IDENTIFYING MEMBER NUMBER (IE, PROGRAM, JOB, ETC) FOR EACH ITEM CHECKED OFF ON THE FORM THAT IS APPLICABLE TO THE DELETE REQUEST.

THE SIGNATURE OF THE PROGRAMMER'S SUPERVISOR OR MANAGER IS REQUIRED BEFORE THE FORM WILL BE ACCEPTED. THE PROGRAM OR JOB AND DOCUMENTATION WILL BE RETURNED TO THE REQUESTING PROGRAMMER FOR DISPOSAL.