Re: TSO ALLOC with/wo unit
In RACF TSO Segment - set default unit type.
On Wed, 20 Mar 2024 08:56:51 +0200, ITschak Mugzach wrote:
>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
Re: TSO ALLOC with/wo unit
There were been some decades to implement DFSMS. With DFSMS you don't have to provide netiher UNIT nor the volser. Not to mention time elapsed since catalogs were introduced. Of course, it is still possible to have unmanaged or even uncataloged datasets, bot NOT FOR REGULAR APPLICATIONS. -- Radoslaw Skorupka Lodz, Poland -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: TSO ALLOC with/wo unit
Hi Leonard,
In the case of an uncataloged Dataset, it would be necessary.
Regards,
David
On 2024-03-20 04:44, Leonard D Woren 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**:
http://www.securiteam.co.il/
**|*
On Wed, Mar 20, 2024 at 9:17 AM Gadi Ben-Avi 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 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
05a7ced721d8-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
Re: TSO ALLOC with/wo unit
HI Mike,
3390 (and SYSALLDA) do not depend upon HCD.
"I/O gen"? -- There has not been one since MVS/ESA V5. (MVS/ESA 4.3 was
the last one to support it.)
Regards,
David
On 2024-03-20 04:52, Mike Schwab wrote:
UNIT is defined in the I/O gen and is customized by each site. 3390,
SYSDA, etc may or may not be present.
On Wed, Mar 20, 2024 at 1:57 AM ITschak Mugzach
<05a7ced721d8-dmarc-requ...@listserv.ua.edu> wrote:
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
Re: TSO ALLOC with/wo unit
I think it is the data in the tso segment.
*| **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 4:06 PM Michael Babcock <
05ad4e2d7232-dmarc-requ...@listserv.ua.edu> wrote:
> SMS versus non-SMS? Esoterics?
>
> On Wed, Mar 20, 2024 at 1:57 AM ITschak Mugzach <
> 05a7ced721d8-dmarc-requ...@listserv.ua.edu> wrote:
>
> > 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
Re: TSO ALLOC with/wo unit
SMS versus non-SMS? Esoterics?
On Wed, Mar 20, 2024 at 1:57 AM ITschak Mugzach <
05a7ced721d8-dmarc-requ...@listserv.ua.edu> wrote:
> 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
Re: TSO ALLOC with/wo unit
For TSO allocations I think it depends what is specified in the UNIT parameter
in your TSO RACF segment. If you have SYSALLDA specified then this will accept
any DASD device. With a specification of SYSDA however, this will depend on the
Eligible Device Table entries at the site.
Lennie Dymoke-Bradshaw
https: //rsclweb.com
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
ITschak Mugzach
Sent: 20 March 2024 06:57
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: TSO ALLOC with/wo unit
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
Re: TSO ALLOC with/wo unit
Tx. I forgot this one!
*| **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 12:11 PM Beate Kawelke
wrote:
> SYSALLDA will also work - see
> https://www.ibm.com/docs/en/zos/2.5.0?topic=up-subparameter-definition-1
>
> -Ursprüngliche Nachricht-
> Von: IBM Mainframe Discussion List Im Auftrag
> von Itschak Mugzach
> Gesendet: Mittwoch, 20. März 2024 09:54
> An: IBM-MAIN@LISTSERV.UA.EDU
> Betreff: Re: [IBM-MAIN] TSO ALLOC with/wo unit
>
> Agree, but it is common to use the devtype 3390.
>
> *| **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**: http://www.securiteam.co.il/ **|*
>
>
>
>
>
> On Wed, Mar 20, 2024 at 10:52 AM Mike Schwab <
> 05962a42dc49-dmarc-requ...@listserv.ua.edu> wrote:
>
> > UNIT is defined in the I/O gen and is customized by each site. 3390,
> > SYSDA, etc may or may not be present.
> >
> > On Wed, Mar 20, 2024 at 1:57 AM ITschak Mugzach
> > <05a7ced721d8-dmarc-requ...@listserv.ua.edu> wrote:
> > >
> > > 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
> >
> >
> >
> > --
> > Mike A Schwab, Springfield IL USA
> > Where do Forest Rangers go to get away from it all?
> >
> > --
> > 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
AW: [IBM-MAIN] TSO ALLOC with/wo unit
SYSALLDA will also work - see
https://www.ibm.com/docs/en/zos/2.5.0?topic=up-subparameter-definition-1
-Ursprüngliche Nachricht-
Von: IBM Mainframe Discussion List Im Auftrag von
Itschak Mugzach
Gesendet: Mittwoch, 20. März 2024 09:54
An: IBM-MAIN@LISTSERV.UA.EDU
Betreff: Re: [IBM-MAIN] TSO ALLOC with/wo unit
Agree, but it is common to use the devtype 3390.
*| **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**: http://www.securiteam.co.il/ **|*
On Wed, Mar 20, 2024 at 10:52 AM Mike Schwab <
05962a42dc49-dmarc-requ...@listserv.ua.edu> wrote:
> UNIT is defined in the I/O gen and is customized by each site. 3390,
> SYSDA, etc may or may not be present.
>
> On Wed, Mar 20, 2024 at 1:57 AM ITschak Mugzach
> <05a7ced721d8-dmarc-requ...@listserv.ua.edu> wrote:
> >
> > 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
>
>
>
> --
> Mike A Schwab, Springfield IL USA
> Where do Forest Rangers go to get away from it all?
>
> --
> 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
Re: TSO ALLOC with/wo unit
Agree, but it is common to use the devtype 3390.
*| **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:52 AM Mike Schwab <
05962a42dc49-dmarc-requ...@listserv.ua.edu> wrote:
> UNIT is defined in the I/O gen and is customized by each site. 3390,
> SYSDA, etc may or may not be present.
>
> On Wed, Mar 20, 2024 at 1:57 AM ITschak Mugzach
> <05a7ced721d8-dmarc-requ...@listserv.ua.edu> wrote:
> >
> > 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
>
>
>
> --
> Mike A Schwab, Springfield IL USA
> Where do Forest Rangers go to get away from it all?
>
> --
> 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
Re: TSO ALLOC with/wo unit
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
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 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 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
> >> 05a7ced721d8-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
Re: TSO ALLOC with/wo unit
UNIT is defined in the I/O gen and is customized by each site. 3390,
SYSDA, etc may or may not be present.
On Wed, Mar 20, 2024 at 1:57 AM ITschak Mugzach
<05a7ced721d8-dmarc-requ...@listserv.ua.edu> wrote:
>
> 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
--
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: TSO ALLOC with/wo unit
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 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 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
05a7ced721d8-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
Re: TSO ALLOC with/wo unit
I'm not sure.
I wouldn't add volume and unit for an allocation for an existing dataset.
Gadi
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Itschak Mugzach
Sent: יום ד 20 מרץ 2024 10:28
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: TSO ALLOC with/wo unit
[You don't often get email from 0305158ad67d-dmarc-requ...@listserv.ua.edu.
Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
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**: http://www.securiteam.co.il/ **|*
On Wed, Mar 20, 2024 at 9:17 AM Gadi Ben-Avi 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 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
> 05a7ced721d8-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
Auto: Re: TSO ALLOC with/wo unit
Je suis absent le 20 mars 2024. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: TSO ALLOC with/wo unit
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 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 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
> 05a7ced721d8-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
Re: TSO ALLOC with/wo unit
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 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
05a7ced721d8-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
TSO ALLOC with/wo unit
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
