TIO PRODUCTION DOCUMENTATION INSTRUCTIONS & SAMPLE

Zeke Event Master Record Number:________

* Note: Zeke Event Master Record numbers are assigned by TIO.

1. Application: (FAS, APS, SIS, etc) 2. Job name: * CMSIDxxx

* Note: jobnames are assigned by Production

3. Scheduling criteria: ==> State when the job will run.

eg; every Tuesday when CICS comes down.

4. Dependencies: Previous Job(s): eg; JOB1 Next Job: eg; JOB3

==> If there are any dependencies, fill in the pds member names of

the previous and next jobs.

5. JCL (pds member name): eg; JOB2 6. Library: VS.______PJ.BASEJC

eg; FASCON (refer to TSS standards)

7. Brief Description: ==> State what the job is doing.

eg; JOB2 is a Focus program which runs against the Fas month-end

subsidiary ledger file, printing a financial report for the Institutional

Real Estate department.

8. Editing requirements: ==> State any manual intervention required for

this job to run.

eg; concatenation of input files.

9. TSS security requirements: ==> State any modification needed to the

TSS profile required for this job to run.

eg; read access needed for VS.xxxxxxxx.xxx

10. ZEKE variables: ==> State all parameters that must be set or

maintained within Zeke.

eg; DATE=MM/DD/YY.

11. Files that are updated in this job: Notes:

==> State all files for which a restore may be necessary in the event

of a job failure.

__________________________________________________ ___________________

__________________________________________________ ___________________

12. Output Report Name(s); Medium Distribution/Notes

==> List all output from this job including reports, outside vendor

tapes, etc. Include number of copies, medium (eg; paper, special

forms, tape, etc), and where the output will be sent.

_________________________________ _______________ ___________________

_________________________________ _______________ ___________________

13. Quality Control: Condition Codes/Recovery procedures

==> State the job steps for which a RESTORE is necessary when

there is an abend or a bad return code.

==> State what return codes require a RESTORE.

==> State all non-zero return codes which are acceptable.

==> State rerun considerations when the job has to be resubmitted.

eg; All condition codes must be 0.

If job fails, simply resubmit, no restore is necessary.

14. Problem Referral List:

==> State programmer's name, office, home & beeper numbers and cmsid.

==> State customer's name, office phone number and cmsid.

eg; Programmer: Brian Corr, X4-8516, 212-597-4643 (home) BCCUA

Customer: Nick Goudoras, x4-1003, FASNG