13
© Copyright. All rights reserved. Datatask Pty Ltd JCL Standards #4 Company Name

© Copyright. All rights reserved. Datatask Pty Ltd JCL Standards #4 Company Name

Embed Size (px)

Citation preview

Page 1: © Copyright. All rights reserved. Datatask Pty Ltd JCL Standards #4 Company Name

© Copyright. All rights reserved. Datatask Pty Ltd

JCL Standards #4Company Name

Page 2: © Copyright. All rights reserved. Datatask Pty Ltd JCL Standards #4 Company Name

© Copyright. All rights reserved. Datatask Pty Ltd

Using procedures in JCL

• Are in-stream or cataloged procedures used?

• Where are procedures stored and can you create one?

• Procedure standards

Page 3: © Copyright. All rights reserved. Datatask Pty Ltd JCL Standards #4 Company Name

© Copyright. All rights reserved. Datatask Pty Ltd

How are procedures used?

• Why do you need to know about procedures?

• In-stream or cataloged procedures, and why are they used?

• Where are cataloged procedures stored?

Page 4: © Copyright. All rights reserved. Datatask Pty Ltd JCL Standards #4 Company Name

© Copyright. All rights reserved. Datatask Pty Ltd

Creating procedures

• How do you create a cataloged procedure?

• Are there naming standards for procedures?

• How do you reference a procedure from your JCL?

Page 5: © Copyright. All rights reserved. Datatask Pty Ltd JCL Standards #4 Company Name

© Copyright. All rights reserved. Datatask Pty Ltd

Procedure characteristics

• Are there any specific coding requirements for your procedure?

• What symbolic parameters can you use in a procedure?

Page 6: © Copyright. All rights reserved. Datatask Pty Ltd JCL Standards #4 Company Name

© Copyright. All rights reserved. Datatask Pty Ltd

Specialized output parameters

• Do we use a third-party output distribution product?

• How do you code specialized output requirements?

• Are there any statements or parameters that you should not use?

Page 7: © Copyright. All rights reserved. Datatask Pty Ltd JCL Standards #4 Company Name

© Copyright. All rights reserved. Datatask Pty Ltd

Third-party output management products

• Do we use any additional products to manage our output?

• How is the reference to these products coded in your JCL?

• Which JCL parameters are used and what standards govern their use?

Page 8: © Copyright. All rights reserved. Datatask Pty Ltd JCL Standards #4 Company Name

© Copyright. All rights reserved. Datatask Pty Ltd

Coding specialized output parameters

• What statements are used to define output requirements?

• Are there standards associated with the parameters used with these statements?

Page 9: © Copyright. All rights reserved. Datatask Pty Ltd JCL Standards #4 Company Name

© Copyright. All rights reserved. Datatask Pty Ltd

Output parameters that are not used

• Output related statements or parameters you should not use

Page 10: © Copyright. All rights reserved. Datatask Pty Ltd JCL Standards #4 Company Name

© Copyright. All rights reserved. Datatask Pty Ltd

Using JES2 control statements

• Are JES2 control statements used in our JCL?

• What standards govern the use of JES2 control statements?

Page 11: © Copyright. All rights reserved. Datatask Pty Ltd JCL Standards #4 Company Name

© Copyright. All rights reserved. Datatask Pty Ltd

Authorization to use JES2 control statements in JCL

• Are you allowed to code JES2 control statements?

• Which JES2 control statements are you not allowed to use?

Page 12: © Copyright. All rights reserved. Datatask Pty Ltd JCL Standards #4 Company Name

© Copyright. All rights reserved. Datatask Pty Ltd

Standards governing the use of JES2 control statements

• /*ROUTE destination coding requirements

• Is /*OUTPUT used in preference to other statements?

• Other JES2 control statement rules

Page 13: © Copyright. All rights reserved. Datatask Pty Ltd JCL Standards #4 Company Name

© Copyright. All rights reserved. Datatask Pty Ltd

Summary

• Procedures

• Output characteristics

• JES2 control statements