IBM Mainframe Forum

by **gidonlando** » Wed Jan 11, 2012 2:00 pm

Hello all,
When I run the TSO EDIT command in batch, as so:
//SAOTSO JOB (T1440),'RL',MSGLEVEL=(1,1),REGION=0M,MSGCLASS=X
//TRY EXEC PGM=IKJEFT01
//SYSPRINT DD SYSOUT=*
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
EDIT 'SCTO.DB2V10.SDSNSAMP(DSNTIJIN)' DATA
RENUM 10000 10000

I get the following error:

READY
EDIT 'SCTO.DB2V10.SDSNSAMP(DSNTIJIN)' DATA
EDIT
RENUM 10000 10000
IKJ52304I UTILITY DATA SET NOT ALLOCATED, SYSTEM OR INSTALLATION ERROR+
IKJ52304I DYNAMIC ALLOCATION ERROR CODE 0218
EDIT
END

The same error occurs when running the command ONLINE.

I looked up IKJ52304I in QUICKREF and it pointed to DAIR Return Code 12 that means there was a dynamic allocation error
and that further information is in the DARC table. I couldn't figure out how to get that further information.
I'll mention that the enviroment this command is running on does NOT use SMS when executin Dynamic Allocation.
There is one volume specified in VATLST member in SYS1.PARMLIB that is defined as STORAGE type.

Any help would be apreciated...
Thank you in advance.

by **steve-myers** » Wed Jan 11, 2012 2:30 pm

From z/OS V1R12.0 MVS Authorized Assembler Services Guide

Meaning: Specified volume or an acceptable
volume is not mounted, and user does not have
volume mounting authorization through the
DYNALLOC request. (dsname allocation)(1)

Application Programmer Action: Change volume
specification, or have the required volume
mounted, or change the allocation request to
allow volume mounting. Resubmit the request.

Some possible reasons for this error are:

Â° The dynamic allocation tried to use a
VIO-eligible unit, but the data set name
was not a temporary dsname (DSN=&&dsname).

Â° The dynamic allocation tried to put a data
set with a non-temporary dsname
(DSN=dsname) onto a real DASD volume but

- No volume serial number was supplied,
and

- No volumes on the system were mounted
with a USE attribute of STORAGE.

Corresponding Message: IKJ56221I

I'm not 100% certain what to make of this. Can you access 'SCTO.DB2V10.SDSNSAMP(DSNTIJIN)' through ISPF? TSO EDIT allocates at least one temporary dataset and copies your source dataset to the temporary dataset when it starts, and the message may be coming from its attempt to allocate the temporary dataset. If you can browse your dataset through ISPF, then the problem is almost certainly from allocating the temporary dataset. If this is true, then you need to examine the userid used to run this job. Check the specification of the unit name in the TSO segment for the userid. Since you say the system used to run the job is not using SMS you need to have at least one volume mounted as PUBLIC for the temporary dataset and the volume must be in the units defined for the unit name. That's about all I can d right now. Check this out. Your security team should be able to help you determine the unit name, and the system programmer's can tell you about the definition of the unit names in your system.

by **gidonlando** » Wed Jan 11, 2012 3:17 pm

Thank you for your quick reply!

After you mentioned that EDIT copies the source of the DATASET on to a temporary file, i tried cleanup up the volume specified in VATLST.
I ran the JOB again and it ended succesfully.
So the problem was there wasn't enough space for the temporary file to be allocated.
I'd like to know how you knew that EDIT copies the source to a temporary file? I couldn't fine that in the documentation.

Thank you in advance...

by **steve-myers** » Wed Jan 11, 2012 7:53 pm

gidonlando wrote:... I'd like to know how you knew that EDIT copies the source to a temporary file? I couldn't fine that in the documentation.

I've been using TSO since before ISPF, in fact, before 3270 type terminals were available for TSO. This is one of those things you learn back in thoses pre-historical days!

by **steve-myers** » Thu Jan 12, 2012 9:56 am

Actually, it is documented, but not where you might think is a sensible place. Look at the RECOVER option for the EDIT command in "TSO/E Command Reference." The "EDIT work file" is the temporary dataset used when RECOVER is not an option specified through the PROFILE command.

IBM Mainframe Forum

Dynamic Allocation error when running EDIT

Dynamic Allocation error when running EDIT

Re: Dynamic Allocation error when running EDIT

Re: Dynamic Allocation error when running EDIT

Re: Dynamic Allocation error when running EDIT

Re: Dynamic Allocation error when running EDIT