On Mon, 23 Sep 2013 13:08:01 -0400, Gerhard Postpischil wrote:
>
>Sorry to disagree, but application programmers had wide leeway in
>creating "funny" names. For DOS compatibility, a DSN was allowed to be
>quoted, and could contain a number of special characters that would fail
>in JCL unquoted. With a little more work, any character combination
>could be used in a DSN when allocating with SVC 32.
>
However, a DSN quoted in JCL can not be cataloged, even though it may
contain only characters (and other syntax) considered valid. Go figger.
And I suspect (can't test) that JCL will prohibit such use of data set
names even if the installation has specified MODIFY CATALOG,
DISABLE(DSNCHECK). JCL is a moron. (Yah, I know; reader system<>
converter system<>execution system, etc.)
On Mon, 23 Sep 2013 11:07:09 -0400, 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.
>
Do "ordinary" application programmers use only JCL to create data sets?
(And I'm overlooking the oxymoron in "ordinary ... programmer".)
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
