Performance of a JCL PROC

arch_cbit · New User Joined: 18 Jun 2007 Posts: 4 Location: Hyderabad

Hi All,

Can anybody tell me what is the advantage in using a Cataloged PROC instead of the utility with respect to performance of the JCL execution.

enrico-sorichetti · Posted: Mon Sep 22, 2008 4:12 pm

maybe we are facing a language barrier, but Jour question is not clear at all

to what utility are You referring, and how does the question relate to CICS

please clarify if You want to get meaningful answers

dick scherrer · Posted: Mon Sep 22, 2008 8:37 pm

Hello,

Bill Dennis · Posted: Tue Sep 23, 2008 12:14 am

The use of a PROC is purely for your convenience. There is no measurable performance decrease even though the reader task does a little more work locating the proc, etc.

The PROC contains the same EXEC PGM= parameter as your stand alone JCL. Execution CPU time would be no difference.

ridgewalker58 · New User Joined: 26 Sep 2008 Posts: 51 Location: New York

JCL Procs are usally used when the JCL could be used for multiple purposes. If you are creating a job that will eventually be moved into the Production environment, you will want to test ALL elements that will end up in Production. You will be testing the program, but you will also want to test the JCL that will be used to RUN the program. To this end, you will create a JCL PROC that will contain the JCL that will execute the program and also point to the files that will be used by the program.
These files are referred to with the DD CARDS and in these cards you will use SYMBOLIC parameters.
for example: //INFILE1 DD DSN=&QUAL..INFILE1

1. When you run this PROC in your test you will supply a value to
&QUAL ---- QUAL='TESTNAME'

2. When you run this PROC in Production you will supply a value to
&QUAL ----- QAL='PRODNAME'

***** IN THIS WAY most syntax errors or Execution time errors
that could be caused by your JCL will be TESTED.

***** Remember - if you have to RECREATE JCL for production
you could make a typing error