MVSFORUMS.com

[Ganti]

Hi,

There is a JCL with the following steps
.
.
//STEP1 EXEC PROC1
.
.
//STEP5 EXEC PGM=IEBGENER, COND=(4,LE,STEP1.STEP2)
.
.
The datacenter standard is to have a JCL execute only PROCs and hence we are required to convert the likes of STEP5 into a PROC and hence we will have the following-
JCL
.
.
//STEP5 EXEC PROC2

where PROC2 will be as follows:

//PROC2 PROC
//STEP1 EXEC PGM=IEBGENER, COND=(4,LE,STEP1.STEP2)

I dont think the above conversion is correct, because the condition code check should be at the step executing this PROC in the JCL as follows:

JCL-
//STEP5 EXEC PROC2, COND=(4,LE,STEP1.STEP2)

and
PROC
//PROC2 PROC
//STEP1 EXEC PGM=IEBGENER

When you do a JSCAN or JEM for the PROC with the COND code, it gives an error, whereas in the second case it does not.

Also, both of these execute well.

Would like to know which one of these would be better to implement.

Best regards
Ganti
_________________
Ganti

[kolusu]

Ganti,

I would definitely go with

[Ganti]

Kolusu,

The error I get is that STEP1.STEP2 is not found, when I do a JEM on the PROC alone.
_________________
Ganti

[Mike]

Ganti,
If I understand correctly the reason that JEM/Jobscan gets an error is that it cannot know that the procedure is being invoked by a JOB that has other steps. If I remember correctly, in the abscence of a JOB (e.g. when scanning a procedure on it's own) it generates/assumes a JOB that simply invokes the procedure being scanned, basically circumventing the no JOB statement error. Thus you would expect to get the STEP1.STEP2 not found error. Really you should be scanning the JOB, as the procedure is only used if invoked by a JOB.
_________________
Regards,
Mike.