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,
- 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.