Looking again leads me to think that the problem is with 'DATACLASS' itself. It is nine characters in length and should be replaced by 'DATACLAS', which is less perspicuous but is only 8 characters in length.
--jg On 8/13/12, Lizette Koehler <[email protected]> wrote: > Kirk, > > In z/OS V1.12 I have in ISMF > > DGTUC023 > > SUGGESTED ACTION: > Correct and re-enter the construct name. The construct name must be > a fully specified 1 to 30 alphameric for Copy Pool construct and > 1 to 8 alphamerics for constructs other than Copy Pool, starting > with an alphabetic or national ($, @ or #) character. > > Which is different from your message. I would probably open a SR to get > them to fix the DOC. % and * are really valid for searching not for > creating a name. > > > Lizette > > > -----Original Message----- >>From: Kirk Wolf <[email protected]> >>Sent: Aug 13, 2012 12:39 PM >>To: [email protected] >>Subject: Re: Valid DATACLAS names - where documented? >> >>So far, everyone seems to agree - the character set is not defined in the >>manual. >> >>I did find this in the ISMF help when I tried to define a DATACLASS: >> >>=============================== >> MESSAGE NUMBER: DGTUC013 >> >> SHORT MESSAGE: INVALID CONSTRUCT NAME >> >> LONG MESSAGE: Must be 1 to 8 alphamerics starting with >> alphabetic, $, @, *, #, or % >> >> EXPLANATION: >> You entered an invalid construct name. The construct name entered >> does not follow the TSO naming conventions. >> >> >> >> >> SUGGESTED ACTION: >> Correct and re-enter the construct name. The construct name must be >> 1 to 8 alphamerics starting with an alphabetic or national >> ($, @, *, #, or %) character. >> >> >> Use ENTER to continue with ISMF HELP, Use END to return to ISMF. >>================================== >> >>However, you can't use the * or % wildcard characters, so this message is >>not the whole story. >> >> >>On Mon, Aug 13, 2012 at 2:32 PM, Gibney, Dave <[email protected]> wrote: >> >>> Oh, you mean valid values for the name. I would expect standard z/OS JCL >>> (and MVS before) up to 8 characters, uppercase letters, likely the >>> Nationals are allowed. :) >>> >>> I bet it is in the JCL manual.... >>> z/OS >>> >>> MVS JCL Reference >>> >>> Document Number SA22-7597-13 >>> >>> 2.15.2 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. >>> >>> I guess, not really, but in section 4.2 Character Sets >>> >>> >>> Dave Gibney >>> Information Technology Services >>> Washington State University >>> >>> >>> > -----Original Message----- >>> > From: IBM Mainframe Discussion List [mailto:[email protected]] >>> > On Behalf Of Kirk Wolf >>> > Sent: Monday, August 13, 2012 12:26 PM >>> > To: [email protected] >>> > Subject: Re: Valid DATACLAS names - where documented? >>> > >>> > I thought that maybe IBM punted and only documented in the ISMF help >>> > screens, but its not there either. >>> > >>> > On Mon, Aug 13, 2012 at 2:16 PM, Gibney, Dave <[email protected]> wrote: >>> > >>> > > z/OS >>> > > >>> > > DFSMSdfp Storage Administration >>> > > >>> > > Document Number SC26-7402-13 >>> > > >>> > > But, it may not be useful. It is DATACLAS=xxxxxxxx, where xxxxxxxx >>> > > is >>> any >>> > > DATACLAS defined by the user site in ISMF :) >>> > > >>> > > Dave Gibney >>> > > Information Technology Services >>> > > Washington State University >>> > > >>> > > > -----Original Message----- >>> > > > From: IBM Mainframe Discussion List [mailto:IBM- >>> > [email protected]] >>> > > > On Behalf Of Kirk Wolf >>> > > > Sent: Monday, August 13, 2012 12:14 PM >>> > > > To: [email protected] >>> > > > Subject: Valid DATACLAS names - where documented? >>> > > > >>> > > > I'm sorry if I'm dense, but I can't find this in the FM. >>> > > > Does anyone know where the valid syntax of a DATACLAS name is >>> > > > documented? >>> > > > >>> > > > 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 >>> > > >>> > > ---------------------------------------------------------------------- >>> > > 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 >>> >> >>---------------------------------------------------------------------- >>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
