JCL/PROC Guideline -- Version 1.0
11/05/97

Production Job Definition (JCL)

 1. Introduction
2. Job Statement
3. Symbolic Parameters
4. Setup Records

JCL Procedure Definition (PROC)

 1. Introduction
2. DD Statements
3. Creating Output Files
4. Symbolic Parameters
5. Data Set Naming
6. Printed Output

 JCL/PROC Standard

1. INTRODUCTION

It is suggested, but not required, that a job execute a single PROC.

2. JOB STATEMENT

• Programmer Name Field
• The programmer name field is used to inform operations of output distribution at UMS.
• This field may have a maximum of 20 characters, and should be entered on the job card following the accounting information.
• This field should not be unloaded to the production JCL library. The Customer Coordinator(s) will add this line with distribution information when they add DISPATCH instructions to the JCL.
• Developers should include the programmer name field on batch test jobs formatted as follows:
• Enclosed in single quotes
• location (1 character),
• box number (2 characters)
• comma
• developer name
Example:

        //         ‘U26,STEPHENS’

• If you chose to use the notify command, ‘NOTIFY=logonid’ should be in the 3rd line of the JOB statement.

• In the comment following a tape number symbolic parameter, it would be helpful to mention the actual data set name and description as space allows.


Example:

        //          VOLSER=XXXXXX,
        //*** TAPE NO. FOR  SIS.BRS.EXTRACT.TRANS (SIS ATTRIBUTE TRANS) PRECEDES

• VOLSER parameters in the production JCL which are left blank when using cataloged tapes should include a comment "Leave Blank When Cataloged".


Example:

        //          VOLSER=,                        <======LEAVE BLANK WHEN CATALOGED

• The Customer Coordinator will change a production job to utilize the Dispatch software.

• Setup records in the production JCL library (UMS.PROD.JCL) are examples only.
• Customer Coordinators should check the online documentation (JCLDOC) for valid control card setups.
• The production JCL library will not always be updated when a control card changes, however, customer coordinators must ALWAYS be informed of the changes.
• Control card setups may reside in an input data library and will not be stored in the production JCL library.

JCL PROCEDURE DEFINITION (PROC)

1. INTRODUCTION

Before Making Changes:

• When changing an existing dataset name, check the dataset name cross reference (XREFDSN in Dispatch) for any other jobs using the file. Change all occurrences of the dataset name.
• When changing an existing JCL procedure, check the JCL procedure cross reference (XREFPROC in Dispatch) for any other jobs using the procedure. Change all occurrences of the procedure.
• When changing an existing production data member, check the data member cross reference (XREFDATA in Dispatch) for any other jobs using the member. Change all occurrences of the data member.

• A referback should refer to a data set name.


Example:

        VOL=REF=PP.PARTP.BWMO0490

• DD DUMMY.

Dummy DD statements are allowed in JCL procedures, but are not required if the statement is overridden in the batch job definition (JCL).

• Catalog data sets whenever possible to allow for running jobs in sequence.
• When creating temporary files, always use UNIT=SYSDA and DISP=(NEW,DELETE) or DISP=(NEW,PASS).
• TAPE CREATION.
• All internal tapes should be created using CA-1 (the tape management system).
• If an outside user is furnishing the tape to be created, it should first be created using CA-1 and then copied to the outside users tape.
• Tapes not used after the completion of the job should be in the tape management system with a retention period of zero days.
• If a tape is no longer being created or retained it should be deleted from the tape management system.

• The symbolic parameter &SYSTEM is permissible on input files to facilitate testing.
• The value of the &SYSTEM parameter for developer test files should be ‘UMS.logonid’ or ‘UMSDEV.logonid’. This prevents tapes from showing on the TMS exception list and provides a longer default retention period.


Example:

        DSN=&SYSTEM..PREPAY.TRANS (where SYSTEM=’UMS.D75843’ in test JCL.)

• The last 17 positions of a tape dataset name are written to the tape label. Attempt to limit tape dataset names to 17 characters.
• The system creating the file determines the high order qualifier for the dataset name. If the file is to be used as input into another system, the id of the receiving system should be the second node of the dataset name.
• Use ‘TRANS’ as part of the dataset name for a transaction dataset whenever possible.


Example:

        SIS.BRS.STIPEND.TRANS

• LASER PRINT
• Special print classes have been assigned for printing on the laser printers.
• Two orientations of print are available:

Portrait - printing across the width of the page,
Landscape - printing across the length of the page.
• Duplex (printing on both sides of the page) is available for both orientations.
• The laser print default form will be three-hole paper.
• If you do not want three-hole paper use:

class R, FORM=960S for portrait,
class R, FORM=941S for landscape, or
class R, FORM=541B for duplex landscape.
• For classes P, Q, U, and W, no FORM OR FCB parameter is needed. The class of the output will override any form specified.
• DIRECT WRITER
• When a Direct Writer job goes into production, the customer coordinator will put the start command, the charge account number, and the form number into a message job for the operator. This message job will be executed prior to the running of the direct writer.

Note: JCL for message jobs can be found in the production job definition library (UMS.PROD.JCL) in members CUAA and CUAB.

• The Customer Coordinator will also send an electronic mail message to the stores area the week prior to the execution of the direct writer to insure that there are sufficient forms available for the print.