DATACLS



>________________________________
> From: John Gilmore <[email protected]>
>To: [email protected] 
>Sent: Monday, August 13, 2012 7:46 PM
>Subject: Re: Valid DATACLAS names - where documented?
> 
>The language Paul Gilmartin cites is certainly not felicitous.  As I
>have already noted, the OPs problem was, however, a different one.  He
>used dataclass=, a nine-character keyword parameter, in a context in
>which at most eight-character ones are supported.
>
>Now it is fair to note that the choice of the keyword value 'dataclas'
>was an ergonomically poor one: dtaclass=,. which I don't much like,
>would have been better because less error-prone.
>
>A fuss is nevertheless being made about nothing.  The trivial default
>syntax I set out in an earlier post should be familiar, if only
>implicitly, to anyone who writes JCL statements.
>
>--jg
>
>On 8/13/12, Paul Gilmartin <[email protected]> wrote:
>> On Mon, 13 Aug 2012 15:30:01 -0400, Gross, Randall [GCG-PFS] wrote:
>>
>>> Subparameter Definition
>>> -----------------------
>>> data-class-name
>>>     Specifies the name of a data class to be used for allocating the
>>>     data set.
>>>
>>>     The name, one to eight characters, is defined by the storage
>>>     administrator at your installation.
>>>
>> That's not very helpful; actually somewhat circular; if you _are_
>> the storage administrator.  So maybe it's in the ICAG/Tuna?
>>
>> -- gil
>>
>> ----------------------------------------------------------------------
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to [email protected] with the message: INFO IBM-MAIN
>>
>
>----------------------------------------------------------------------
>For IBM-MAIN subscribe / signoff / archive access instructions,
>send email to [email protected] with the message: INFO IBM-MAIN
>
>
>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to