Tx. I think the answer is in the volume operand (I marked it in red). The reason I use volume operand is that the source of the dataset information is APF, where the dataset does not have to be cataloged. If the volume value is not SMS, I allocate it with the volume information. otherwise I ignore the volume information (SMS).
ITschak VOLUME(serial_list)specifies the serial number(s) of an eligible direct access volume(s) on which a new data set is to reside or on which an old data set is located. If you specify VOLUME for an old data set, the data set must be on the specified volume(s) for allocation to take place. If you do not specify VOLUME, new data sets are allocated to any eligible direct access volume. Eligibility is determined by the UNIT information in your procedure entry in the user attribute data set (UADS). You can specify up to 255 volume serial numbers. With SMS, the VOLUME operand is not suggested. The system determines the UNIT and VOLUME from the storage class (STORCLAS operand) associated with the data set. If SMS does not manage the data set and you want to allocate a data set to a *specific* volume, explicitly specify VOLUME. *| **Itschak Mugzach | Director | SecuriTeam Software **|** IronSphere Platform* *|* *Information Security Continuous Monitoring for Z/OS, zLinux and IBM I **| * *|* *Email**: i_mugz...@securiteam.co.il **|* *Mob**: +972 522 986404 **|* *Skype**: ItschakMugzach **|* *Web**: www.Securiteam.co.il **|* On Wed, Mar 20, 2024 at 10:44 AM Leonard D Woren <ibm-main...@ldworen.net> wrote: > Specifying VOLUME more or less always requires specification of UNIT. > Ignoring SMS altering the historic behavior, there is a "default > unitname" associated with each userid. For ALLOC VOL to work without > UNIT, the VOL specified must be within the set of devices covered by > that default unitname. > > I think it doesn't matter that it's an existing data set. > > Why are you specifying VOL for an existing data set??? > > /Leonard > > > Itschak Mugzach wrote on 3/20/2024 1:28 AM: > > GAdi, > > > > Does this rule apply to existing datasets? The allocation request was for > > existing datasets not new. > > > > *| **Itschak Mugzach | Director | SecuriTeam Software **|** IronSphere > > Platform* *|* *Information Security Continuous Monitoring for Z/OS, > zLinux > > and IBM I **| * > > > > *|* *Email**: i_mugz...@securiteam.co.il **|* *Mob**: +972 522 986404 > **|* > > *Skype**: ItschakMugzach **|* *Web**: www.Securiteam.co.il **|* > > > > > > > > > > > > On Wed, Mar 20, 2024 at 9:17 AM Gadi Ben-Avi <gad...@malam.com> wrote: > > > >> As far as I know, If you do not specify a UNIT Type, it will look for > >> volumes that are STORAGE. > >> If there aren't any, the allocation will fail. > >> > >> -----Original Message----- > >> From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On > Behalf > >> Of ITschak Mugzach > >> Sent: יום ד 20 מרץ 2024 08:57 > >> To: IBM-MAIN@LISTSERV.UA.EDU > >> Subject: TSO ALLOC with/wo unit > >> > >> [Some people who received this message don't often get email from > >> 000005a7ced721d8-dmarc-requ...@listserv.ua.edu. Learn why this is > >> important at https://aka.ms/LearnAboutSenderIdentification ] > >> > >> I have a program in Rexx that allocates a dataset using dsname and > volume > >> serial (1) . it works well in my shop but requires a unit type (2) in > >> another shop. Actually the error is msg "IKJ56241I SPECIFIED UNIT IS > >> UNDEFINED". > >> Why does 1 work here and fails in another shop? > >> > >> 1. ALLOC F(XXX) DA('dsname') VOLUME(volser) > >> 2. ALLOC F(XXX) DA('dsname') VOLUME(volser) UNIT(390) > >> > >> ITschak > >> > >> ITschak Mugzach > >> *|** IronSphere Platform* *|* *Information Security Continuous > Monitoring > >> for z/OS, x/Linux & IBM I **| z/VM coming soon * > >> > >> ---------------------------------------------------------------------- > >> For IBM-MAIN subscribe / signoff / archive access instructions, send > email > >> to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > >> > >> ---------------------------------------------------------------------- > >> For IBM-MAIN subscribe / signoff / archive access instructions, > >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > >> > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
