The z/OS documentation isn't complete and doesn't cover lots of things that users rely on. As with most things, you have to make reasonable judgements. But I do understand that this particular one bothers you :-)
On Mon, Apr 4, 2022, at 1:25 PM, Paul Gilmartin wrote: > On Mon, 4 Apr 2022 12:59:27 -0500, Kirk Wolf wrote: > > > >We certainly have seen that using data sets from z/OS Unix commands that > >don't explicitly document support is your pet peeve. IMO this seems overly > >pedantic, since IBM code that uses fopen (and works) is extremely unlikely > >to stop. > > > The drawbacks are: > o Those utilities that accept DSNs without documentation lack the > fine control of attributes and options provided by such as /bin/cp. > Suppose IBM, to benefit one customer changes, e.g. an > autoconversion behavior that impacts another. > o If it breaks, IBM may not take an APAR. > > As an ISV, do you rely on unsupported behavior in customer-facing > code? (Or is //DSN supporrt documented under special licenses?) > You may have beta test access and be prepared for unexpected > adverse changes. > > -- > gil > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > Kirk Wolf Dovetailed Technologies http://dovetail.com ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
