Enhancement to the FCAP0008I output message

IBM does not expect to implement this in the foreseeable future.
The tape mount itself is done asynchronous to the FCAP0008I message. At the point where the message that the capture has started is sent, the tape has not been mounted yet so it is not known what the volser will be.

IBM suggests the following alternatives.
1) Console automation
Each FCAP0008I message which includes the DASD mod and the tape device address will be accompanied by a COTM0310I message that includes the tape device address and the volser. Console automation could be used to extract those messages and construct a table that has the mod and the tape volser.

2) Tape library
Use the tape user exit, CORU, to add code which would place the volumes mounted on the capture drives into a unique capture category. For example, have one category that was exclusively for capture, or use a collection of categories that the exit would rotate through based on the date so that tapes from one day would go into one category while the tapes from the next time that capture was run would go into another. This will not associate a specific volume with a DASD mod, but it will put all the tapes into a common category. At restore time it would then be possible to use ZTPLF FILL to load the tapes from that category to do the restore without knowing ahead of time what those volumes were or what mods they contained. This alternative moves all the capture tape management into the tape library and requires utilization of the CORU user exit. The category support was put in place to support this type of function.