COND ParameterNote! COND parameter can be coded at the job level and step level. The COND parameter is used to implement conditional processing within a JCL. It helps to validate the return code to determine whether a job will continue the processing or not. The job processing will continue ...
l 一个instream中不能再定义一个instream procedure(不能嵌套定义instream procedure)。 l Jcl中动态改写 exec 语句的内容。格式: PARAMETER.PROCSTEPNAME=VALUE 000111 //PROC1 PROC 000112 //STEPA1 EXEC PGM=HELLO,TIME=(1,30) 000113 // PEND
<!--[if !supportLists]-->l一个instream中不能再定义一个instream procedure(不能嵌套定义instream procedure)。<!--[endif]--> <!--[if !supportLists]-->l Jcl中动态改写exec语句的内容。格式:PARAMETER.PROCSTEPNAME=VALUE<!--[endif]--> 000111 //PROC1 PROC 000112 //STEPA1 EXEC PGM=HELLO,TI...
When you specify a parameter on the EXEC statement that invokes a proc, and do not specify a stepname, which is what you have above, the parameter applies to all steps (except for the PARM parameter, which doesn't apply here). So for PROC3 the COND parameter is effectively COND=(1,L...
its a vendor supplied PROC. Definitely don't want to mess with it. But it looks like you're saying I can use IF/THEN logic to skip the EP4IN step if the BACKUP1 step fails. So I will do that. As much as I hate COND, at least it "fits" within how JCL otherwise looks, which...