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
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
On 9/23/2013 11:07 AM, John Gilmore wrote:
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.
Sorry to disagree, but application
On 9/23/2013 10:27 AM, Paul Gilmartin wrote:
Nowadays, might a viable practice be to scratch anything
that's neither catalogued nor allocated?
I didn't want to write a monograph, but keep the response brief. The
scratch program in question considers the (installation's)
classification of the
I was not using the word 'ordinary' in a pejorative or even
deprecatory way. I intended only to exclude very savvy people writing
application code in assembly language and their like.
I was at least half-aware of the DOS-compatibility quote-framed DSNAME
value loophole, but if I remember
