Device Independent JCL Procedures

The purpose of device-independent JCL is to prevent system hardware and software modifications from affecting the production JCL. By having our JCL constructed in this manner, the programming staff is insulated from any system-level changes that have to be made by the Tech Support staff. This facility adds integrity to the computing center in that production jobs will not be terminated because of system changes that were not communicated to the programming staff. This type of job stream will also allow better utilization of our resources, clearer assignment of responsibility among staff members, and better documentation for recovery in the event of a job failure.

1) Tech Support will provide the standard model for device-independent JCL whether using SLI books, VSAM models, or procedures.

2) A standard job stream will be constructed like this model. If there are exceptional circumstances, job streams for a particular application will depart from the model in a mutually agreed-upon manner. These exceptions will be documented and attached to the Job Run Sheet.

3) Each Application Programmer will construct the initial SLI books, VSAM models, or procedures and incorporate these items in the job stream. The jobs that catalog SLI books, VSAM models, or procedures will then be submitted to Operations as production jobs. Once accepted by Operations, Tech Support will update these books as necessary.

4) All changes made by Tech Support to the SLI books, VSAM models, or procedures will be coordinated with the Programming staff before the changes are put into effect.

5) In the event of a job failure, the Operator on duty will follow the documented job failure procedures. If the problem cannot be resolved, the Operator will attempt to determine the nature of the problem and notify Tech Support or the appropriate programmer as necessary.