Adding Expired Volume Information or Native Save Information into BRMS

Troubleshooting

Problem

This document describes methods for adding a volume's media information into the BRMS history database.

Resolving The Problem

This document describes methods for adding a volume's media information into the BRMS database (for example, WRKMEDIBRM). The commands that a user can use to accomplish this are EXTMEDIBRM and ADDMEDIBRM.

Notes:
1. Media needs to be added and expired PRIOR to attempting to use either EXTMEDIBRM or ADDMEDIBRM.

2. Object level detail cannot be retrieved using EXTMEDIBRM and ADDMEDIBRM. Because of this, the following commands will not work:
WRKMEDIBRM, Option 9
WRKLNKBRM
RSTOBJBRM
RSTDLOBRM

Extract Media Information (EXTMEDIBRM)

The Extract Media Information (EXTMEDIBRM) command adds information about a volume in the BRMS media file. You specify the identifier of the volume and what is contained on the volume. BRMS will load the volume in a tape drive and record the content information only for media already added to the BRMS media inventory and only for media whose contents are currently shown as expired. If active contents information for the media already exists, or if the media has not been added to the media inventory, no content information is added.

EXTMEDIBRM
Device . . . . . . . . . . . . . TAPxx
Volume identifier . . . . . . . VOLxxx
File origin . . . . . . . . . . *FILE *FILE, *SAV, *SAVCAL, *SAVCFG, *SAVCHG, *SAVCHGCAL, *SAVCHGDLO, *SAVCHGOBJ, *SAVDLO, *SAVLIB, *SAVOBJ, *SAVSECDTA, *SAVSYS
End of tape option . . . . . . . *REWIND *UNLOAD, *LEAVE, *REWIND

Notes:

When running the EXTMEDIBRM command on a full system save, it is recommended that *FILE is used for the file origin parameter (FILE). If you specify one of the other options, all the entries are entered into the BRMS database as that type of save. It's not possible to use BRMS to restore any data when FILE(*FILE) is used. This is intended for reference only. When a WRKMEDIBRM is run for the volume, all entries will specify a Save type of *FILE, irrespective of what was specified in the FILE parameter.

Integrated File System data cannot be restored using the WRKMEDIBRM nor WRKLNKBRM command.

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

When a sequence starts on a volume and then spans the next two volumes, the volume that has only a continued sequence on it will not list anything when the EXTMEDIBRM command is run on it.

If you want to be able to restore a library using BRMS commands, for example from WRKMEDIBRM you should use FILE(*SAVLIB).

Example

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.

When a library spans media, it is not possible to restore that sequence number using BRMS or use DUPMEDBRM on spanned volumes or a spanned sequence number when EXTMEDIBRM is used. This is because the file sequence is continued from a previous volume; however, BRMS does not know what the previous volume was. The sequence will be listed on the first volume, however, it will not be listed on the continuation volume. The ADDMEDIBRM command must be used for data that spans media. File sequences that span volumes cannot be added on the continuing volume(s). BRM1749 will be logged when trying to add continued file sequence numbers.

When a save of the library already exits in BRMS, the data from the EXTMEDIBRM will not be included in the BRMS Recovery Report.

If there is a requirement to use BRMS commands or menus to restore the data from the media, the EXTMEDIBRM command needs to use the correct value in the File Origin Parameter (FILE). Use the DSPTAP command to verify what command was used to save the data. If multiple types of saves were done to the volume *FILE is recommended (See Note 1). Possible values are:

*FILE
*SAV
*SAVCFG
*SAVCHG
*SAVCHGDLO
*SAVCHGOBJ
*SAVDLO
*SAVLIB
*SAVOBJ
*SAVSECDTA
*SAVSYS

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

Value for FILE parameter on EXTMEDIBRM	BRMS entry value	BRMS save command	Native save command
*SAVSYS	*SAVSYS	SAVSYSBRM	SAVSYS
*SAVSECDTA	*SAVSECDTA		SAVSECDTA
*SAVCFG	*SAVCFG		SAVCFG
*SAVOBJ	*OBJ list	SAVOBJBRM or SAVOBJLBRM	SAVOBJ
*FILE	OBJ list of only FILE objects	SAVOBJBRM or SAVOBJLBRM *FILE	*SAVOBJ OBJTYPE(FILE)**
*SAVLIB	IBM or ALLUSR or library	SAVLIBBRM	SAVLIB
*SAVDLO	ALLDLO or FLR list	SAVDLOBRM	SAVDLO
*SAV	LINK or LNK list	SAVBRM	SAV
*SAVCHGOBJ	Incremental (cumulative) of *OBJ list	CUML or INCR of SAVLIBBRM	SAVCHGOBJ
*SAVCHGDLO	Incremental (cumulative) of *FLR list	CUML or INCR of SAVDLOBRM	SAVDLO using REFCHGDATE
*SAVCHG	Incremental (cumulative) of *LNK list	CUML or INCR of SAVBRM	SAV using CHGPERIOD

Examples of EXTMEDIBRM compared to BRMS saves

When running an EXTMEDIBRM on a volume to extract history saved outside of BRMS, if the volume is not expired, users will see the following message:

Message ID . . . . . . . . . : BRM1392
Message file . . . . . . . . : Q1AMSGF
Library . . . . . . . . . : QBRM

Message . . . . : Unable to use volume &1. (C R)
Cause . . . . . : Volume &1 is not available for use as scratch media. Processing of control group &2 type &3 is interrupted.
Recovery . . . : Do one of the following:
-- Type C to cancel the operation.
-- Pick a different volume, then type R to try the operation again.

After running an EXTMEDIBRM FILE(*FILE) on a volume and trying to restore an object from WRKMEDIBRM using 7-Restore and 7=Specify object, it will fail with:
CPD0033 - STRING BEGINNING 'RSTASP ' NOT VALID COMMAND NAME

It fails because FILE(*FILE) was used. You must use FILE(*SAVLIB). As mentioned earlier in this doc It's not possible to use BRMS to restore any data when FILE(*FILE) is used. This is intended for reference only.

Add Media Information (ADDMEDIBRM)

The Add Media Information to BRM (ADDMEDIBRM) command adds file level detail to the BRMS media inventory content volume information. The files and the volumes that contain them can be from another tape inventory or from some other outside source. The purpose of the command is to allow user applications or another volume management system to insert data (volume file descriptions) into the BRMS media contents information so that the volumes and their contents can be managed. In order for objects to be recoverable through BRMS, ADDMEDIBRM must be used for each sequence on the volume. Multiple volumes write a media information record for each volume; the volume sequence is increased as the records are added.

ADDMEDIBRM
Volume . . . . . . . . . . . . . > VOLXX Character value
Volume sequence . . . . . . . . > 2 1-9999 [This example is for the second volume in the set]
Sequence number . . . . . . . . > 13 1-16777215
File label . . . . . . . . . . . *TYPE
Type . . . . . . . . . . . . . . *LIB *LIB, *ALLDLO, *LINK, *QHST, *SAVSFG, *SAVSECDTA, *SAVSYS
Library . . . . . . . . . . . . > LIBXX Name

Notes:

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. If the WRKMEDIBRM* command is run on the volume, all the entries will have a save type of *FILE.
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.`

[{"Type":"MASTER","Line of Business":{"code":"LOB68","label":"Power HW"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z0000000CKTAA2","label":"Backup Recovery Install Migration-\u003EBRMS"}],"ARM Case Number":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"All Versions"}]

Historical Number

410524987

Was this topic helpful?

Document Information

Modified date:
29 November 2024

UID

nas8N1015029

Tips