In:
z/OS 2.2.0
z/OS MVS
z/OS MVS Program Management: User's Guide and Reference
Starting the binder
Invoking the binder with JCL
DD statements
Binder DD statements
SYSPRINT and SYSLOUT DD statements
I read:
SYSPRINT or SYSLOUT can also be assigned to a z/OS UNIX file. In this case,
FILEDATA=TEXT must also be specified.
(Similar statement about SYSTERM in a different section.) Some readers
will not be surprised that when I read such a rule, I put on my Black Team
cape and investigate what happens when I break it. So:
If SYSPRINT FILEDATA is BINARY or RECORD, Binder writes the file content
as if TEXT had been specified, then leaves the file tagged as the value
specified in the JCL, pretty unusable, and exits with RC=0.
What should I say in my SR? I'm disinclined to accept "You broke the rules;
RTFM; WAD," as an answer. How would Pubs feel about documenting the
behavior, including the RC=0?
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
