On Fri, 26 Sep 2008 13:56:34 -0500, Mark Zelden wrote:
>>
>>You would think it would have failed for a JCL error but it did not.
>
>If you had non-blank data in col. 72 it should have been a JCL error.
>
>Open a PMR with IBM. I just tested this on z/OS 1.8 and got a JCL
>error. On z/OS 1.9 I didn't. It does get a JCL error if the first
>library in the concatenation has data in col. 72, but not if other
>libraries do.
>
Ummm. I read:
3.4.1.3 "z/OS V1R9.0 MVS JCL Reference"
___________________________________________________________________
3.4.1.3 Continuing the Comments Field
Include comments by following an interrupted parameter field with at
least one blank. To continue a comment:
1. Interrupt the comment at a convenient place before column 72, up to
and including column 71.
2. Code a nonblank character in column 72.
3. Code // in columns 1 and 2 of the following statement.
4. Code a blank character in column 3 of the following statement.
5. Continue the comments field beginning in any column after column 3.
You can use JCL comment statements as an alternative way to imbed
comments in the JCL stream.
So, for example:
//* 72
//SYSLIB DD DISP=SHR,DSN=SYS1.MACLIB These are comments x
// DD DISP=SHR,DSN=SYS1.MODGEN
So, the "x" in column 72 of the SYS1.MACLIB line causes 4-* of the
following (SYS1.MODGEN) line to be treated as a continuation of the
comment on the prior line. No JCL error. The programmer may be
astonished to learn that macro names he expected to find in MODGEN
are reported as undefined opcodes.
Or do I misread TFM? This does not appear to be changed from
V1R8.0.
What does it mean by "interrupted parameter field"?
-- gil
----------------------------------------------------------------------
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
