problem w/ "allocate" cmnd within a REXX

[Bonno, Tuco]

cross-posting to tso-rexx, ibm-main.
environemtn here is z/os 1.9

I am trying to execute an ALLOCATE cmnd from within a rexx, as follows:
the REXX:
pars arg OUTDSN TGTVOL
…..
“ALLOCATE DA(“OUTDSN”) SPACE(…) CYLINDERS <more parm-s> …. VOLUME(“TGTVOL”) “

my calling stmnt:
xyzrexx abc.def.ds DSSUT1

the dataset gets allocated correctly, but not on pack DSSUT1; it gets allocated on an sms-managed pack
I have researched this in the 1.9 _tso_command_reference_ manual, which says as follows:

“Allocating non-SMS-managed data sets With SMS, you can specify DATACLAS to allocate non-SMS-managed data sets. You cannot, however, use the STORCLAS and MGMTCLAS operands. STORCLAS and MGMTCLAS determine whether a data set is managed by SMS.”

--------- but there’s no further info on HOW to use DATACLAS to bypass sms.

so …. does anyone have any know how to do this: how do you bypass SMS when running an ALLOCATE command from within a rexx?

( I don’t have this problem when using ispf 3.2 or batch br14 to allocate datasets …. )

thanks in advance

/s/ tuco bonno
graduate, College of Conflict Management;
University of Southeast Asia;
"I partied on the Ho Chi Minh Trail - tiến lên !! "

[Bob Bridges]

Tuco, this isn't something you can solve in REXX and probably not by looking
in the TSO manual; in my opinion you need to talk with your favorite
storage-management wallah, who can tell you why your choice of VOLSER is
being overridden and what if anything you can do about it. This is almost
certainly due to storage-management policies in place at your installation,
and in my experience every installation is different.

---
Bob Bridges, rhb...@attglobal.net, cell 336 382-7313

/* ....Now some of you are scratching your heads and wondering "How does a
person with an IQ higher than pastry get Super Glue in his ear and not know
it?" But you parents out there are no doubt nodding your heads and saying
"It would not surprise me to learn that this man has a three-year-old son."
-Dave Barry, _Children May Be Hazardous to Your Health_ */

-----Original Message-----
From: Bonno, Tuco
Sent: Tuesday, December 15, 2009 13:47

cross-posting to tso-rexx, ibm-main.
environemtn here is z/os 1.9

I am trying to execute an ALLOCATE cmnd from within a rexx, as follows:
the REXX:
pars arg OUTDSN TGTVOL

...
"ALLOCATE DA("OUTDSN") SPACE(.) CYLINDERS <more parm-s> ..
VOLUME("TGTVOL") "

my calling stmnt:
xyzrexx abc.def.ds DSSUT1

the dataset gets allocated correctly, but not on pack DSSUT1; it gets
allocated on an sms-managed pack
I have researched this in the 1.9 _tso_command_reference_ manual, which
says as follows:

"Allocating non-SMS-managed data sets With SMS, you can specify DATACLAS to
allocate non-SMS-managed data sets. You cannot, however, use the STORCLAS
and MGMTCLAS operands. STORCLAS and MGMTCLAS determine whether a data set is
managed by SMS."

--------- but there's no further info on HOW to use DATACLAS to bypass sms.

so .. does anyone have any know how to do this: how do you bypass SMS when

running an ALLOCATE command from within a rexx?

( I don't have this problem when using ispf 3.2 or batch br14

to allocate datasets .. )

----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,
send email to LIST...@VM.MARIST.EDU with the message: INFO TSO-REXX

[Lizette Koehler]

X-POST to IBMMAIN and TSO/REX

Tuco,

You may need to force the volume to NONSMS if the volume TGTVOL (in your case DSSUT1) is a non sms managed volume. Which means you would need to code STORCLAS and MGMTCLAS appropriately (not necessarily DATACLAS).

If it is a managed volume in SMS, then you may have another issue, like the dataset cannot allocate in that pool.

Check with your storage admin to see what you need to use for this process.

Lizette

>From: "Bonno, Tuco" wrote:

>
>I am trying to execute an ALLOCATE cmnd from within a rexx, as follows:
>the REXX:
>pars arg OUTDSN TGTVOL

> …..
>“ALLOCATE DA(“OUTDSN”) SPACE(…) CYLINDERS <more parm-s> …. VOLUME(“TGTVOL”) “

>
>my calling stmnt:
>xyzrexx abc.def.ds DSSUT1
>
>the dataset gets allocated correctly, but not on pack DSSUT1; it gets allocated on an sms-managed pack
>I have researched this in the 1.9 _tso_command_reference_ manual, which says as follows:
>
>
>“Allocating non-SMS-managed data sets With SMS, you can specify DATACLAS to allocate non-SMS-managed data sets. You cannot, however, use the STORCLAS and MGMTCLAS operands. STORCLAS and MGMTCLAS determine whether a data set is managed by SMS.”
>
>--------- but there’s no further info on HOW to use DATACLAS to bypass sms.
>

----------------------------------------------------------------------

[Styles, Andy , Group IT]

Another possibility is that the ACS routines are selecting the storage pool that the dataset should go into based on its name.

--
Andy Styles

Tuco,

Lizette

>From: "Bonno, Tuco" wrote:

This e-mail is private and confidential and may contain privileged material. If you have received this e-mail in error, please notify the sender and delete it immediately. You must not copy, distribute, disclose or use any of the information in it or any attachments.

Lloyds TSB Bank plc. Registered Office: 25 Gresham Street, London EC2V 7HN. Registered in England and Wales, number 2065. Telephone: 020 7626 1500.

Lloyds TSB Scotland plc. Registered Office: Henry Duncan House, 120 George Street, Edinburgh EH2 4LH. Registered in Scotland, number 95237. Telephone: 0131 225 4555.

Cheltenham & Gloucester plc. Registered Office: Barnett Way, Gloucester GL4 3RL. Registered in England and Wales, number 2299428. Telephone: 01452 372372.

Cheltenham & Gloucester Savings is a division of Lloyds TSB Bank plc.
Lloyds TSB Bank plc, Lloyds TSB Scotland plc and Cheltenham & Gloucester plc are authorised and regulated by the Financial Services Authority.

Lloyds Banking Group plc. Registered Office: The Mound, Edinburgh EH1 1YZ. Registered in Scotland, number 95000. Telephone: 0131 225 4555.

Telephone calls may be monitored or recorded.

[Schwarz, Barry A]

Since the DSN is not enclosed in tic marks, your prefix is being used (unless you have specified no prefix). If that is not your intent, you can fix the allocate statement in the REXX.

Since it is being assigned to an SMS volume, you are guaranteed that someone (probably the SMS Automatic Class Selection routine) is assigning a storage class to your dataset. You will need to check with you storage administrator to determine if this dataset is authorized to be unmanaged and if so what you add to the REXX to inform the system of that fact.

In most of the shops I've seen, the prefix would declare your dataset to be a user dataset (as opposed to production for example) and all user datasets are managed.

-----Original Message-----
From: TSO REXX Discussion List [mailto:TSO-...@VM.MARIST.EDU] On Behalf Of Bonno, Tuco
Sent: Tuesday, December 15, 2009 10:47 AM
To: TSO-...@VM.MARIST.EDU
Subject: problem w/ "allocate" cmnd within a REXX

cross-posting to tso-rexx, ibm-main.
environemtn here is z/os 1.9

I am trying to execute an ALLOCATE cmnd from within a rexx, as follows:
the REXX:
pars arg OUTDSN TGTVOL

.....
"ALLOCATE DA("OUTDSN") SPACE(...) CYLINDERS <more parm-s> .... VOLUME("TGTVOL") "

my calling stmnt:
xyzrexx abc.def.ds DSSUT1

the dataset gets allocated correctly, but not on pack DSSUT1; it gets allocated on an sms-managed pack

----------------------------------------------------------------------

[Bonno, Tuco]

thanks to all who responded to my original post. as was suggested, yes, the solution was to contact our SMS staff and get them to modify their stuff.

thank you to one and all.

/s/ tuco bonno ;
graduate, college of Conflict Management;
University of Southeast Asia;
"I partied on the Ho Chi Minh trail -- tiến lên !!"