Re: submit job from SYSPUNCH

Subject: Re: submit job from SYSPUNCH Date: Sun, 7 May 2006 15:15:33 + J R [EMAIL PROTECTED] writes Why don't you have SYSPUNCH SYSOUT=(*,INTRDR)? Because it's a good idea to check the assembly completion code to ensure that the generated JCL is good. That way you can avoid

Re: submit job from SYSPUNCH

In [EMAIL PROTECTED], on 05/07/2006 at 10:41 PM, J R [EMAIL PROTECTED] said: 2) It's not clear exactly when PUNCHed data is written to SYSPUNCH and/or SYSLIN. Nor is it relevant. If the macro detects an error, then all it takes is one more line to purge the job. Regardless of when the

Re: submit job from SYSPUNCH

Thanks, Bill, I'd forgotten about /*DEL. Regarding point #2, I think that PUNCH statements are processed as they are encountered. However, one could punch a /*DEL card which should terminate the job which would have been submitted IIRC. Bill

Re: submit job from SYSPUNCH

J R [EMAIL PROTECTED] writes Why don't you have SYSPUNCH SYSOUT=(*,INTRDR)? Because it's a good idea to check the assembly completion code to ensure that the generated JCL is good. That way you can avoid submitting partially and/or incorrectly built jobs to the internal reader.

Re: submit job from SYSPUNCH

To: IBM-MAIN@BAMA.UA.EDU Subject: Re: submit job from SYSPUNCH Date: Sun, 7 May 2006 15:15:33 + J R [EMAIL PROTECTED] writes Why don't you have SYSPUNCH SYSOUT=(*,INTRDR)? Because it's a good idea to check the assembly completion code to ensure that the generated JCL is good. That way