In <[EMAIL PROTECTED]>, on 07/17/2008
at 03:54 PM, Matthew Stitt <[EMAIL PROTECTED]> said:
>The confusing issue was begun a very long time ago. If there is apparent
>input data with no specific DD statement to match it up with, there was a
>SYSIN dd statement generated above it. Until recently, that extraneous
>SYSIN dd statement had no effect on the JCL except to prevent either a
>JCL error or an "invalid jcl" error as this SYSIN was ignored since it
>was out of sequence (in most cases) with the specification of SYSIN (if
>there was one) in the procedure.
WTF? There are plenty of cataloged procedures with no SYSIN DD, and the
generated SYSIN DD most definitely has an effect with those. In
particular, the compiler procs typically have no SYSIN DD in the compile
step.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see <http://patriot.net/~shmuel/resume/brief.html>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
