In <[EMAIL PROTECTED]>, on 12/31/2007
at 03:11 PM, Paul Gilmartin <[EMAIL PROTECTED]> said:
>I'll retract "grievous".
But see below.
>If the argument of PATH is anything other than '/dev/null'
>(or '//dev/null'), the file is allocated as a UNIX file and can be
>processed as a UNIX file. If it is '/dev/null' it as allocated as
>DUMMY,
If true, I'd have to agree with egregious; neither the C/I not allocation
should have special processing for any path name. Do you have
documentation[1] of that behavior, and have you submitted and ETR?
>Rudimentary JCL sample available on request.
I'd be more interested in the output showing the problem, but it would do
you more good to show it to IBM via formal channels than to show it to me
or the list.
>It's worth a chapter in the JCL RM.
If there actually is such a problem and IBM doesn't correct it, then I'd
say that it should be documented in both the JCL RM and the JCL UG.
>What benefit of this distinct treatment of /dev/null justifies the
>resource spent on its implementation?
I'm not convinced that there is such a treatment, but if you're not
misinterpreting things then it would definitely violate Unix[2] semantics.
Anybody from IBM monitoring this?
[1] I'd include JFCB and TIOT contents as part of the documentation.
[2] You might argue that JCL is outside the scope of Unix, but I doubt
that the Unix community would buy that.
--
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
