Page Comparison

...

 
Volume    Library         Volume Sequence          Library Sequence
VOL001                            1
                  LIBA                                                                1
                  LIBB                                                                2
                  LIBC                                                                3
VOL002                            2
                  LIBC                                                                3 (cont)
VOL003                            3
                  LIBC                                                                3 (cont)
                  LIBD                                                                4
                  LIBE                                                                5
 
In the above example, running the EXTMEDIBRM command on VOL002 does not list anything, and the volume remains expired.
 

The table below shows the proper value for the FILE parameter, depending on how the objects were saved.

...

1. Integrated File System data cannot be restored using WRKLNKBRM.
2. It is not possible to use BRMS to restore from parallel saves.  A media definition is required for these, and BRMS cannot create these from data obtained using the ADDMEDIBRM command.
3. The Recovery Report shows only the first volume of the media set.  During the recovery (STRRCYBRM), the following message is issued:  CPA6798 - No volume to mount on device TAPxx (C "cartridge id").  Type the next volume in the set, and press the Enter key.  The restore should continue on that volume.  If you have R540 or later, a special instructions step in the recovery report that lists the volumes in the set can be added. 
4. SAVSYS entries will not appear on the recovery report. BRMS cannot verify the release of the SAVSYS.  If you have R540 or later, a special instructions step in the recovery report that lists the volumes in the set can be added.
5. If a volume is enrolled in BRMS and a native operating system save command is run and that volume is used, the volume expiration date changes, by default,  to *PERM unless SETMEDBRM is used.
6. When running an ADDMEDIBRM on a volume to extract history saved outside of BRMS, if the volume is not expired and sequence 1 is specified, users will see the following error message:

Message ID . . . . . . . . . :   BRM1756 
Message file . . . . . . . . :   Q1AMSGF
  Library  . . . . . . . . . :     QBRM 
 
Message . . . . :   Volume &1 is not expired.
Cause . . . . . :   An attempt to add a contents entry failed because the volume &1 is not expired.
Recovery  . . . :   Retry the request after expiring the media or specifying another volume. Use the WRKMEDBRM to expire the volume.
 
Note:  

• It is not possible to use BRMS to restore from parallel saves.  A media definition is required for these, and BRMS cannot create these from data obtained using the ADDMEDIBRM command.

 
If a volume is enrolled in BRMS and a native operating system save command is run and that volume is used, the volume expiration date changes, by default,  to *PERM unless SETMEDBRM is used.