TSO ALLOC In REXX Needs Improvement

muh786 · New User Joined: 14 Jun 2011 Posts: 1 Location: usa

Hello - I would appreciate some input on my dilemma. In Rexx program I am creating (or allocating) a dataset with the following attributes and it works; it creates a dataset:

ADDRESS TSO "ALLOC DA("F4") RECFM(F B) LRECL(80)",
"SPACE(1,1) CYL UNIT(SYSDA) DSORG(PS),BLKSIZE(27920)",
"STORCLAS(STANDARD) MGMTCLAS(BM01YR00)",
"NEW CATALOG"

F4 - has a dataset name. The problem is when I use this dataset in a batch JCL it doesn't get recognized. I get the following error message:

IAT8685 SY56 - REQUIRED RESOURCES NOT AVAILABLE
IAT8685 SY57 - GROUP/CLASS DISABLED

But if I create the same dataset in ISPF 3.4 with same attributes it works. So there must be something missing here that i am not using. Any help will be appreciated. Thanks

enrico-sorichetti · Posted: Sat Nov 16, 2024 3:15 am

explain why
TSO ALLOC In REXX Needs Improvement

the IAT8685 message is a jes3 message,
speak to your support to understand which resource is not available

post the jcl you are using
and the jes log of the job

Pedro · Posted: Sat Nov 16, 2024 8:48 am

I agree with Enrico that you need to show us the JCL. Also, please explain the relationship between the rexx program and the batch job. When is the rexx program running?

My guess is that you are expecting F4 to still be a variable later when the job executes. The rexx and JCl are asynchronous.

Joerg.Findeisen · Posted: Sun Nov 17, 2024 11:37 am

Issue a TSO FREE DA("F4") command after your allocation in REXX and it will work.

It might also good to know for you how to inquire JES3 what resources are not available.

SockFourAgain · Posted: Wed Jan 29, 2025 9:39 pm

The Alloc command in your REXX without single quotes around the dsname will allocate a dataset called userid.F4 (if the variable is unset) or userid.WhateverTheVariableIsSetTo and will therefore very likely succeed. But a batch job trying to allocate "F4" (assuming DSN=F4) will try to create a dataset called F4, it's unlikely there will be a catalog alias or RACF profile setup for this odd high level qualifier, the allocation will fail. Even if the "F4.*" alias does exist - it's also unlikely you will have create (RACF ALTER) access to it.