Joe- Apologies for the confusion, we are trying to read the data set. The customer has not been clear about the hardware involved but the job output they sent us did not have to specify a volser on the DD statement. IIRC, on our own system we used to have catalogued data sets residing on tape which could be allocated without a volser as long as the tape was mounted.
Thanks Robin -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Joe Monk Sent: 09 July 2019 17:44 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: STC gets gets DAIR error 0218/0000 Robin, I took your comments to mean your file server was having problems allocating an output file. Thats why I gave the requirements for an output file for dynamic allocation ... If its a VTL (i.e. disk pool), and the DSN is specified, there are two requirements: a. the VOLSER must be specified and b. the VOLSER must be mounted for STORAGE use. Joe On Tue, Jul 9, 2019 at 3:42 AM Robin Atwood <abend...@gmail.com> wrote: > Joe, thanks for the prompt reply. I think your suggestions don't apply > here because the customer sent us the output of a batch job which analysed > the tape. The interesting part was the allocation messages, the DD > statement was: > > //TAPEIN DD DSN=RC.MD.SQDS.NPDC.PKLHIST.H2000,DISP=OLD > > IEF285I RC.MD.SQDS.NPDC.PKLHIST.H2000 KEPT > IEF285I VOL SER NOS= R02195. > > So I think we can assume the volume info is all in the catalog. Our server > does a dynamic allocation with DSN and DISP specified, so it's basically > the same as the above JCL. > > Thanks > Robin > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Joe Monk > Sent: 09 July 2019 15:03 > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: STC gets gets DAIR error 0218/0000 > > 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 > > ---------------------------------------------------------------------- > 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
