Text item: Body.822
For the V2 mvs server, "pending" means that a tape is empty but ADSM is
waiting a certain number of days before reusing it or returning it to the
tape management system scratch pool.  This a new feature which enhances the
database restore process.  If you restore the database back to a level
which thinks there is data on the tape, the data will still be there and
not have been overwritten.  The # of days is set in the storagepool
definition -- "reusedelay" parameter.

Perhaps this feature was added to V1 vm servers via the service stream?
_________________________Reply Header_________________________
Author: ADSM-L AT vm.marist DOT edu
Subject: What is volume status of Pending?
05-24-96 11:34 AM

Date:         Fri, 24 May 1996 11:34:00 EST
From:         Vern Maxson <VM%IUBVM.BITNET AT vm.marist DOT edu>
Subject:      What is volume status of Pending?
To:           Multiple recipients of list ADSM-L <ADSM-L AT vm.marist DOT edu>

I have a tape volume that received an I/O error, so I used the "move data"
command to migrate the data off the tape.  Then I used dsmlabel to create
a new tape with the same volser, and put it into the library in place of
the previous tape.  When I did that, the error state went from Yes to No,
although the number of read and write errors were not reset to zero.
(I suppose that I will have to delete and redefine the volume to fix that.)
Then, I changed the access/mode back to READWRITE.  Now the Volume Status
field for the tape says "Pending", but the only valid Volume Status codes
for a tape are "Empty", "Filling", and "Full".  I don't have any processes
running, and the tape is not mounted in a drive.  What gives?