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.
Joe
On Tue, Jul 9, 2019 at 2:18 AM Robin Atwood <abend...@gmail.com> wrote:
> We have a customer trying to allocate a data set on some kind of virtual
> tape device and the dynamic allocation is failing
>
> with 0218/0000: "user does not have volume mounting authorization". Using
> the same user id he is able to allocate the same
>
> data set from a TSO session. We suggested he give the user id of the file
> server the same permissions his TSO user id had,
>
> in particular the MOUNT profile in the TSOAUTH class. This made no
> difference. AFAIK, the TSO "authorities" are indicated in
>
> the PSCBATR1 flags in the PSCB but are only present when a TSO environment
> has been created; the file server is running
>
> as a normal started task, no TSO. To make sure I had the customer sends us
> a
> dump of the server and, indeed, there is no
>
> PSCB.
>
>
>
> So what is getting checked and what might we tell the customer to enable so
> the file server can mount the tape?
>
>
>
> Thanks
>
> Robin
>
>
> ----------------------------------------------------------------------
> 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
