On Thu, 16 Oct 2008 19:19:20 -0500, Mark Zelden wrote:
>>>
>>Is this always the case, or only if the DD statement specifies
>>SYSOUT=*. I believe in our lab configuration if I leave the
>>class empty on my DD SYSOUT statement, and omit the OUTPUT JCL
>>statement, the SYSOUT again goes to bit bucket.
>
>What do you mean if you have a DD SYSOUT statement with the
>class empty? You have to specify something, don't you? At least
>in JCL. ...
>
Actually, you don't have to specify something:
Linkname: 12.63.1 "z/OS V1R10.0 MVS JCL Reference" IBM Library Server
URL:
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2B680/12.63.1
But the syntax is convoluted (They don't even have it right in
the syntax diagram; they needed a verbal addition), or at best
unintuitive. And IIRC they got even that right only in reaction
to my PMR complaining that there was no apparent way in a JCL DD
statement to exploit the DEFAULT= parameter of the JCL OUTPUT
statement; I had tried and failed with such as:
4 //SYSUTX DD SYSOUT=''
STMT NO. MESSAGE
4 IEFC629I INCORRECT USE OF APOSTROPHE IN THE SYSOUT FIELD
and:
4 //SYSUTY DD SYSOUT=()
IEF210I TESTJOB STEP SYSUTY - UNIT FIELD SPECIFIES INCORRECT DEVICE NAME
??? !!! (I thought this used to give "INCORRECT USE OF PARENTHESIS IN
THE SYSOUT FIELD".)
But, hey, if none of the above were true, it would hardly qualify
as JCL, would it?
-- 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
