120 likes | 262 Vues
This document provides a comprehensive overview of Job Control Language (JCL) standards in our organization. It outlines who uses JCL, how it is created and stored, and the responsibilities for maintaining it. We discuss standard formatting requirements, job naming conventions, and accounting information needed for job submissions. Additionally, we explore the importance of adhering to these standards and consequences of non-compliance. This guide serves as a resource for application and system programmers, schedulers, and operators to ensure consistency and efficiency in JCL processes.
E N D
JCL Standards #1 Company Name
Our organization and JCL • Who uses JCL in our organization? • Where is JCL stored and how is itcreated? • Who is responsible for maintaining JCL?
Who uses JCL in our organization? • Application programmers • System programmers • Schedulers • Operators
Where is JCL stored and how is it created? • What JCL data sets are you allowed to access? • What if I need to run JCL from another location? • Production JCL
Who is responsible for maintaining JCL? • Your own JCL • Production JCL
Job statement • General JCL formatting requirements • Job naming standards • Job accounting information • Keyword parameter standards
JCL formatting requirements • What are our general JCL formatting standards?
Job naming standards • What are our job naming standards? • What will happenif I do not use the standards?
Job accounting information standards • What do I need to code for job accounting information? • How is the accounting information used?
CLASS and MSGCLASS standards • What standards are used for these keyword parameters? • How are these standards enforced?
Other JOB statement parameters • Which other JOB statement parameters are required?
Summary • Importance of JCL standards • JOB statement parameters used by our organization