Historically, the use of a DSN{AME]= value like
*.*.GUBBINS
was not possible for an ordinary application programmer, whose JCL
would have been rejected as in error if it had contained such a DSN=
value. Such practices were once common for member names too. IBM for
long distributed CICS materials as PDS members having formally illicit
names like MCGUFFN¢. The motivation was, of course, to avoid names
that conflicted with those already used by a customer.
The notorious retention date of 99.365 is another, slightly different,
example of the misuse of as coding scheme to encode information it was
not designed to represent.
I should like to think that we were now q
On 9/23/13, Paul Gilmartin <[email protected]> wrote:
> On Mon, 23 Sep 2013 09:08:25 -0400, Gerhard Postpischil wrote:
>>...
>>And I think Mr. Gilmore had too many asterisks. The pattern I recall was
>>to prepend "*." until a unique name resulted (IIRC, giving things like
>>*.*.*.jobname.other). I had a home-grown utility, run daily, that
>>scratched temporary data sets, and *. was one of the patterns it looked
>>for, in addition to the more common SYSnnnnn.
>>
> Nowadays, might a viable practice be to scratch anything
> that's neither catalogued nor allocated?
>
> Has IBM published a warning that such data set names
> are reserved for IBM, and not to be used by application
> programmers, or does IBM rely on "common knowledge"
> of programmers to avoid them?
>
> Is there a similar part of the name space reserved for
> ISVs? I know that in UNIX there is a convention (not
> published as a standard?) that pathnames incorporating
> a registered domain name (rewritten big-endian) are
> reserved for the registrant.
>
> -- gil
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>
--
John Gilmore, Ashland, MA 01721 - USA
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
