The dataset is Not Cataloged 2. It does exist on tape and you must reference the dataset with DSN and VOLSER. Alternative is to create the tape with a different DSN so it can be cataloged. If the same VOLSER you overwrote it and any subsequent files on the tape are destroyed. Applies to real or virtual tape. Lookout for automatic deletion due to expiration or not cataloged status.
On Tue, Jan 28, 2020 at 11:30 PM Gadi Ben-Avi <gad...@malam.com> wrote: > > Hi, > User ran a job the uses DFSort to copy a dataset. > The output dataset is on tape. > The output dataset existed on tape before the job run. > Message IGD17101I was issued saying that there already was a dataset with > that name. > The job ended with condition code 0. > > Is this a DFSort behavior? > If yes, can it be changed? > > We are using z/OS v2.2. > > Thanks > > Gadi > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
