Skip to main content

Backup Recovery and Media Services

BRMS for IBM i

The following are data areas that you can use to control various BRMS behaviors:

Media

QUSRBRM/Q1ANOVFYM

In V6R1 and above, a change was made which did not allow media volumes that have movement verification pending to be picked as a candidate for save or duplication.
To allow the old behavior, which allows media in movement verification pending to be selected, run the following command:

CRTDTAARA DTAARA(QUSRBRM/Q1ANOVFYM) TYPE(*CHAR).

Notes:

  1. In releases IBM i v6r1m0 and 7.1, the following PTFs or their superseding PTFs are required:
    7.1 SI43868
    V6R1M0 SI43869
  2. Volumes that are expired are not checked for movement verification pending status.



QUSRBRM/Q1ACHGOWNX

In releases V5R4M0 and later, it's possible for BRMS volumes to be owned by a system that is not in the BRMS network. Support has been added to the STRMNTBRM command to change the owner of expired BRMS volumes that are not owned by a system in the BRMS network. The owner will be changed to the system on which the STRMNTBRM is being run. To enable this new function, run the following command: 

CRTDTAARA DTAARA(QUSRBRM/Q1ACHGOWNX) TYPE(*CHAR)

To disable this new function, run the following command:

DLTDTAARA DTAARA(QUSRBRM/Q1ACHGOWNX)

Notes:

  1. It is recommended to only create the data area on one system in a BRMS network. This will help with contention if multiple systems run STRMNTBRM at the same time.
  2. If STRMNTBRM is run in restricted state, this data area will be ignored and no volume ownership changes will occur.

Note: In release IBM i 7.1 or earlier, the following PTFs or their superseding PTFs are required:




QUSRBRM/Q1ANOSYSCK

Will stop checking for same system on picking media even if it can't insure via the network that it can use this media.
 

CRTDTAARA DTAARA(QUSRBRM/Q1ANOSYSCK) TYPE(*CHAR) LEN(1)

See Info APAR II13467 (Data Loss could happen, please read info apar before using!)

Note: This applies only to stand-alone tape drives.




QTEMP/QSRPARFMT

This data area can be used to force saves to be done in true parallel format (object spreading accrss tape drives).

CRTDTAARA DTAARA(QTEMP/QSRPARFMT) TYPE(*CHAR) LEN(1)

This capability does not apply if LIB(*ALLUSR), LIB(*IBM), or LIB(*NONSYS) is specified on the SAVLIB command.




QUSRBRM/Q1APRM

This data are has numerous uses.

1 Movement

The operation of BRMS/400 movement with a media library (MLB) is a complex area, and much thought has to be given to this before deciding on the best solution for you or your user's environment.

Starting with PTF SF17131 (C4242) at V2R3M0 and in the base code in newer releases, there is a byte in a data area that controls whether volumes are ejected from an MLB at media movement (MOVMEDBRM) or verification (VFYMOVBRM) or confirmation (CFMMOVBRM at V2R3M0 and V3R0M5 ). This data area has no effect when volumes are inserted.

The data area name is Q1APRM in library QUSRBRM. If the value at byte 210 is 1, the eject takes place at verification. The value of this data area can be displayed using the following command:

CHGDTAARA DTAARA(QUSRBRM/Q1APRM (210 1)) VALUE('1')

BRMS is shipped with this value set to ' ' (blank).

There are several possible setups depending on the value of this data area and the value of Verify moves in the relevant move policy, that can be viewed by selecting Option 5 (=Display) against the move policy in question from the WRKPCYBRM TYPE(*MOV) command. The possible combinations available are:

 Setup | Q1APRM | Verify
 ------+--------+-------
 1     |  ' '   | *NO
 2     |  ' '   | *YES
 3     |  '1'   | *NO
 4     |  '1'   | *YES

Setup 1

This section describes the sequence of operation when the value of position 210 in data area Q1APRM is ' ' (blank) and verify moves is *NO.
Volumes that are scheduled to leave the MLB will be ejected when movement (MOVMEDBRM) is run. This is achieved by BRMS issuing the Remove Tape Cartridge (RMVTAPCTG) command "under the covers".

Volumes that are scheduled to return to the MLB must be physically placed in the library before the movement is run. Once inserted, these volumes will have a category of *INSERT. When movement (MOVMEDBRM) is run, these volumes are changed to a usable category (for example, *SHARE400 or *NOSHARE) depending on the value of the "Shared media" parameter in the media class associated with the volume. This is achieved by BRMS issuing the Add Tape Cartridge (ADDTAPCTG) command "under the covers".

Setup 2

This section describes the sequence of operation when the value of position 210 in data area Q1APRM is ' ' (blank) and verify moves is *YES.
Volumes that are scheduled to leave the MLB are ejected. Then, movement (MOVMEDBRM) is run. This is achieved by BRMS issuing the Remove Tape Cartridge (RMVTAPCTG) command "under the covers". However, they will not be "moved" in the BRMS database until verify is run.

For volumes that are scheduled to return to the MLB, movement (MOVMEDBRM) is run first which sets the volumes up for verification. The volumes then must be inserted into the MLB prior to verify being run. Once inserted, these volumes have a category of *INSERT. When verify (VFYMOVBRM) is run, these volumes will be changed to a usable category (for example, *SHARE400 or *NOSHARE. This is achieved by BRMS issuing the Add Tape cartridge (ADDTAPCTG) command "under the covers".

Setup 3

When the value of position 210 in data area Q1APRM is 1 and verify moves is *NO, this setup operates the same way as Setup 1.

Setup 4

This section describes the sequence of operation when the value of position 210 in data area Q1APRM is 1 and verify moves is *YES.

For volumes that are scheduled to leave the MLB, movement (MOVMEDBRM) is run first, which sets the volumes up for verification. When verify (VFYMOVBRM) is run, the volumes are ejected and "moved" in the BRMS database. This is achieved by BRMS issuing the Remove Tape Cartridge (RMVTAPCTG) command "under the covers".

For volumes that are scheduled to return to the MLB, movement (MOVMEDBRM) is run first. This sets the volumes up for verification. The volumes then must be inserted into the MLB prior to verify being run. Once inserted, these volumes have a category of *INSERT. When verify (VFYMOVBRM) is run these volumes are changed to a usable category (for example, *SHARE400 or *NOSHARE). Again, this is achieved by BRMS issuing the Add Tape Cartridge (ADDTAPCTG) command "under the covers".

Additional Considerations

When volumes are set for duplication, BRMS does not move nor request that these volumes be ejected from MLBs until the duplication process has completed. BRM1364 will be posted, and volumes will remain at the current location.

2. Number of Days to Retain BRMS Journal Receivers

Journal receivers in BRMS/400 are deleted after 5 days when maintenance is run (STRMNTBRM) and they have been detached. Starting with PTF SF17131 (C4242) at R230 and in the base code of further releases, there is a byte in a data area that controls how many days journal receivers are to be deleted when running maintenance. The data area name is Q1APRM in library QUSRBRM. If the value of byte 201 is changed, the detached journal receivers are deleted after that many days. (This field is 2 characters.) The data area can be displayed using the following command:

DSPDTAARA DTAARA(QUSRBRM/Q1APRM)

The following is shown:

 Display Data Area
 Data area . . . . . . . :  Q1APRM 
 Library . . . . . . . . :  QUSRBRM
 Type . . . . . . . . .  :  *CHAR
 Length . . . . . . . .  :  1000
 Text . . . . . . . . .  :
 Value
 Offset  *...+....1....+....2....+....3....+....4....+....5  
 0  'PRODQBRM      960706102141         4'
 50  '0*LIBL   QSYSOPR       *PRTF       '
 100  'V3R1M0 960706102016                '
 150  '                         '
 200  '05    0  1   QBRM              '
 250  '                         '
 300  '                         '
 350  '                         '
 400  '                         '

The value of this data area can be changed to 'xx' using the following command (where xx is the number of days):

CHGDTAARA DTAARA(QUSRBRM/Q1APRM (201 2)) VALUE('xx')

BRMS is shipped with this value set to '05'.

Note: This affects only the journal receivers associated with journal QUSRBRM/QJ1ACM. Journal receivers associated with the QUSRBRM/QJ1AJRN2 are always deleted immediately a new journal receiver is created.




QUSRBRM/Q1AONLYBRM

BRMS can block initializing and writing to media not enrolled in the BRMS inventory. The purpose of this function is to prevent users from inadvertently overwriting media created by a partition not participating in a BRMS network group.

To enable this feature, create the data area QUSRBRM/Q1AONLYBRM and in the system policy, set the parameter "Auto enroll media" to *NO. Attempts to write or initialize tapes not enrolled in the BRMS inventory will result in message BRM3D1D with reason code 0010.

CRTDTAARA DTAARA(QUSRBRM/Q1AONLYBRM) TYPE(*CHAR) LEN(1)

In order to prevent unauthorized users from enrolling media into BRMS, secure the commands WRKMLMBRM, ADDMEDBRM and WRKMEDBRM, and the data area QUSRBRM/Q1AONLYBRM.

The following BRMS PTF or their supersede is required
V5R3M0 SI30646
V5R4M0 SI30647
V6R1M0 SI30649




QUSRBRM/Q1AREJVOLS

BRMS can be configured to check for 200 volumes rather that 20 volumes before posting a BRM148A message during saves.

CRTDTAARA QUSRBRM/Q1AREJVOLS TYPE(*CHAR) LEN(1)

Note: To use this data area, PTF SI33260 (V5R4M0), or PTF SI33259 (V5R3M0) is required. (V6R1M0 checks for up to a 1000 by default)




QUSRBRM/Q1ADLTVERS

This data area is used in V5R2M0 and above. When using versioning in your media policies, if you delete a library, the tape containing that library will not expire. A new data area, QUSRBRM/Q1ADLTVERS, is provided that will allow you to specify that the tapes containing these deleted libraries should be automatically expired. This data area specifies the number of days that BRMS should retain the saved item information for those libraries after it has detected (via STRMNTBRM) that they have been deleted. Once this time period has been exceeded, the saved item information for those libraries will automatically be expired

In order to specify that you want to expire any saved items whose associated library was deleted in the last xx days, issue the following command:

CRTDTAARA DTAARA(QUSRBRM/Q1ADLTVERS) TYPE(*DEC) LEN(5) VALUE(xx)
 




QUSRBRM/Q1ACTGPMPT

In V6R1 and above, option 6 on the Work with Media Library Media screen for the WRKMLMBRM ommmand can be used to change the category of a media volume. If the volume that you select is a BRMS volume, option 6 will reset the category to be consistent with the media class of the volume without prompting for user input.

To force prompting on each of the volumes when option 6 is specified, create data area QUSRBRM/Q1ACTGPMPT with the following command. This will change the prompting behavior for option 6 in all jobs on the system. CRTDTAARA DTAARA(QUSRBRM/Q1ACTGPMPT) TYPE(*DEC) LEN(1)

To remove prompting when option 6 is specified, delete data area QUSRBRM/Q1ACTGPMPT with the following command. DLTDTAARA DTAARA(QUSRBRM/Q1ACTGPMPT)

Note: The described behavior applies to systems that have the following BRMS PTFs or their superseding PTFs are applied:



QUSRBRM/Q1ANOVFYM

In V5R4M0 and above, volume selection will protect volumes that are in verify move status. After the move media command (MOVMEDBRM) has been ran, volumes that need to have movement verified will not be selected as append candidates.

To enable the old behavior which allows media in verify move status to be selected as an append candidate, run the following command: CRTDTAARA DTAARA(QUSRBRM/Q1ANOVFYM) TYPE(*CHAR).

Note: For releases after IBM i 7.1, no PTF is required. For release IBM i 7.1 and earlier, the following PTFs or their superseding PTFs are required:

Media duplication

QUSRBRM/Q1AIGNRDUP

This data area is used to ignore the USEDUPMED parameter in the STRRCYBRM command. USEDUPMED was introduced in V5R4M0 to indicate that you wanted to include either the original save media or the duplicate save media, but not both. Create this data area if you want to include both the original save media and the duplicate save media in your recovery report Recovery Volume Summary Report (QP1A2RCY) when USEDUPMED(*YES) is specified.

CRTDTAARA DTAARA(QUSRBRM/Q1AIGNRDUP) TYPE(*CHAR)



QUSRBRM/Q1ACRTDOLD

Normally the creation date of a volume will only be updated when data is written to the first sequence on the volume.

1) This data area can be used to update the creation date of a volume when data is written to the first sequence on the volume or when QUSRBRM is saved to the volume.

CRTDTAARA QUSRBRM/Q1ACRTDOLD TYPE(*CHAR) LEN(1)

Note: To use this function, the following PTFs are required:
V5R4M0 : SI30647
V6R1M0 : SI30649

2) This same data area can also be used to update the creation date of a volume every time data is written to the volume, if it contains the value ALL.

CRTDTAARA QUSRBRM/Q1ACRTDOLD TYPE(*CHAR) LEN(10) VALUE('ALL ')

Note: To use this function, the following PTFs are required:
V5R4M0 : SI37269
V6R1M0 : SI37276




QUSRBRM/Q1AALWMFDP

BRMS can be configured to allow multiple parallel volumes to be appended to the save volume when running a DUPMEDBRM TOSEQNBR(*END). The first volume will start on a scratch volume and all other volumes in the parallel set will be appended to that volume until it is full.

CRTDTAARA QUSRBRM/Q1AALWMFDP TYPE(*CHAR) LEN(1)

Notes:

  1. When doing restores from the duplicated single volume, Parallel resources needs to be set to a minimum and maximum of 1 - PRLRSC(1 1)
  2. Ensure that only expired media is available in the media class specified in the MEDPCY parameter on the DUPMEDBRM command. If there are any active volumes in that media class, they will be appended to.
  3. Restores from the duplicate media may take longer.



QTEMP/Q1ADUPCOMP

In V5R4, the COMPACT parameter on the DUPTAP command is being externalized via a data area in BRMS.
This data area(QTEMP/Q1ADUPCOMP) is of length 9.

This would yield current behavior. (or if NO data area):
CRTDTAARA DTAARA(QTEMP/Q1ADUPCOMP) TYPE(*CHAR) LEN(9) VALUE('*FROMFILE')

This would yield a *YES behavior (which is wanted on the TS7650 to physical 3584 tape)
CRTDTAARA DTAARA(QTEMP/Q1ADUPCOMP) TYPE(*CHAR) LEN(9) VALUE('*YES')

This would yield a *NO behavior if needed:
CRTDTAARA DTAARA(QTEMP/Q1ADUPCOMP) TYPE(*CHAR) LEN(9) VALUE('*NO')

This will only apply to the job that the DUPMEDBRM(s) is being run in, if the DUPMEDBRM is done in batch. The creating of the data area must be done in the batch job also.

In V6R1 and above, the COMPACT parameter has been added to the DUPMEDBRM command.

Notes:

  1. The new auto duplication feature in V6R1 and above will not directly support the new parameter on the media policy as not all the parameters are being put on this feature. However, by changing the DUPMEDBRM command default to *DEV for the Compact parameter, the behavior can be acquired.
  2. PTFs SI38733 (V5R4M0) or SI38739 (V6R1M0) or SI38740(V7R1M0) or their superseding PTFs are required.


Maintenance

QUSRBRM/Q1ACHGOWNX

In releases V5R4M0 and later, it's possible for BRMS volumes to be owned by a system that is not in the BRMS network. Support has been added to the STRMNTBRM command to change the owner of expired BRMS volumes that are not owned by a system in the BRMS network. The owner will be changed to the system on which the STRMNTBRM is being run. To enable this new function, run the following command: 

CRTDTAARA DTAARA(QUSRBRM/Q1ACHGOWNX) TYPE(*CHAR)

To disable this new function, run the following command:

DLTDTAARA DTAARA(QUSRBRM/Q1ACHGOWNX)

Notes:

  1. It is recommended to only create the data area on one system in a BRMS network. This will help with contention if multiple systems run STRMNTBRM at the same time.
  2. If STRMNTBRM is run in restricted state, this data area will be ignored and no volume ownership changes will occur.

Note: In release IBM i 7.1 or earlier, the following PTFs or their superseding PTFs are required:




QUSRBRM/Q1AREFREE

To improve performance with RUNCLNUP(*YES) dealing with re-freeing of auto-retrieved objects. If data exists this refreeing is NOT done.

CRTDTAARA DTAARA(QUSRBRM/Q1AREFREE) TYPE(*CHAR) LEN(1)




QUSRBRM/Q1AQRYEST

After loading on the following PTF's, SI24433 for V5R4, SI24427 for V5R3 or SI24426 for V5R2, the BRMS product will default to change the job's query time limit to *NOMAX. This will effect all other work done after BRMS has run and will prevent a problem where the query estimator may cause a CPF427F error. If you do not wish this behavior, you can disable it by running the following commands:

CRTDTAARA DTAARA(QUSRBRM/Q1AQRYEST) TYPE(*CHAR) LEN(1)
CHGOBJOWN OBJ(QUSRBRM/Q1AQRYEST) OBJTYPE(*DTAARA) NEWOWN(QBRMS)




QUSRBRM/Q1AREORG

This data area can be used to indicate that all BRMS files that have more than 0 records will be reorganized.

CRTDTAARA DTAARA(QUSRBRM/Q1AREORG) TYPE(*CHAR) LEN(1)




QUSRBRM/Q1APRM

This data are has numerous uses.

1 Movement

The operation of BRMS/400 movement with a media library (MLB) is a complex area, and much thought has to be given to this before deciding on the best solution for you or your user's environment.

Starting with PTF SF17131 (C4242) at V2R3M0 and in the base code in newer releases, there is a byte in a data area that controls whether volumes are ejected from an MLB at media movement (MOVMEDBRM) or verification (VFYMOVBRM) or confirmation (CFMMOVBRM at V2R3M0 and V3R0M5 ). This data area has no effect when volumes are inserted.

The data area name is Q1APRM in library QUSRBRM. If the value at byte 210 is 1, the eject takes place at verification. The value of this data area can be displayed using the following command:

CHGDTAARA DTAARA(QUSRBRM/Q1APRM (210 1)) VALUE('1')

BRMS is shipped with this value set to ' ' (blank).

There are several possible setups depending on the value of this data area and the value of Verify moves in the relevant move policy, that can be viewed by selecting Option 5 (=Display) against the move policy in question from the WRKPCYBRM TYPE(*MOV) command. The possible combinations available are:

 Setup | Q1APRM | Verify
 ------+--------+-------
 1     |  ' '   | *NO
 2     |  ' '   | *YES
 3     |  '1'   | *NO
 4     |  '1'   | *YES

Setup 1

This section describes the sequence of operation when the value of position 210 in data area Q1APRM is ' ' (blank) and verify moves is *NO.
Volumes that are scheduled to leave the MLB will be ejected when movement (MOVMEDBRM) is run. This is achieved by BRMS issuing the Remove Tape Cartridge (RMVTAPCTG) command "under the covers".

Volumes that are scheduled to return to the MLB must be physically placed in the library before the movement is run. Once inserted, these volumes will have a category of *INSERT. When movement (MOVMEDBRM) is run, these volumes are changed to a usable category (for example, *SHARE400 or *NOSHARE) depending on the value of the "Shared media" parameter in the media class associated with the volume. This is achieved by BRMS issuing the Add Tape Cartridge (ADDTAPCTG) command "under the covers".

Setup 2

This section describes the sequence of operation when the value of position 210 in data area Q1APRM is ' ' (blank) and verify moves is *YES.
Volumes that are scheduled to leave the MLB are ejected. Then, movement (MOVMEDBRM) is run. This is achieved by BRMS issuing the Remove Tape Cartridge (RMVTAPCTG) command "under the covers". However, they will not be "moved" in the BRMS database until verify is run.

For volumes that are scheduled to return to the MLB, movement (MOVMEDBRM) is run first which sets the volumes up for verification. The volumes then must be inserted into the MLB prior to verify being run. Once inserted, these volumes have a category of *INSERT. When verify (VFYMOVBRM) is run, these volumes will be changed to a usable category (for example, *SHARE400 or *NOSHARE. This is achieved by BRMS issuing the Add Tape cartridge (ADDTAPCTG) command "under the covers".

Setup 3

When the value of position 210 in data area Q1APRM is 1 and verify moves is *NO, this setup operates the same way as Setup 1.

Setup 4

This section describes the sequence of operation when the value of position 210 in data area Q1APRM is 1 and verify moves is *YES.

For volumes that are scheduled to leave the MLB, movement (MOVMEDBRM) is run first, which sets the volumes up for verification. When verify (VFYMOVBRM) is run, the volumes are ejected and "moved" in the BRMS database. This is achieved by BRMS issuing the Remove Tape Cartridge (RMVTAPCTG) command "under the covers".

For volumes that are scheduled to return to the MLB, movement (MOVMEDBRM) is run first. This sets the volumes up for verification. The volumes then must be inserted into the MLB prior to verify being run. Once inserted, these volumes have a category of *INSERT. When verify (VFYMOVBRM) is run these volumes are changed to a usable category (for example, *SHARE400 or *NOSHARE). Again, this is achieved by BRMS issuing the Add Tape Cartridge (ADDTAPCTG) command "under the covers".

Additional Considerations

When volumes are set for duplication, BRMS does not move nor request that these volumes be ejected from MLBs until the duplication process has completed. BRM1364 will be posted, and volumes will remain at the current location.

2. Number of Days to Retain BRMS Journal Receivers

Journal receivers in BRMS/400 are deleted after 5 days when maintenance is run (STRMNTBRM) and they have been detached. Starting with PTF SF17131 (C4242) at R230 and in the base code of further releases, there is a byte in a data area that controls how many days journal receivers are to be deleted when running maintenance. The data area name is Q1APRM in library QUSRBRM. If the value of byte 201 is changed, the detached journal receivers are deleted after that many days. (This field is 2 characters.) The data area can be displayed using the following command:

DSPDTAARA DTAARA(QUSRBRM/Q1APRM)

The following is shown:

 Display Data Area
 Data area . . . . . . . :  Q1APRM 
 Library . . . . . . . . :  QUSRBRM
 Type . . . . . . . . .  :  *CHAR
 Length . . . . . . . .  :  1000
 Text . . . . . . . . .  :
 Value
 Offset  *...+....1....+....2....+....3....+....4....+....5  
 0  'PRODQBRM      960706102141         4'
 50  '0*LIBL   QSYSOPR       *PRTF       '
 100  'V3R1M0 960706102016                '
 150  '                         '
 200  '05    0  1   QBRM              '
 250  '                         '
 300  '                         '
 350  '                         '
 400  '                         '

The value of this data area can be changed to 'xx' using the following command (where xx is the number of days):

CHGDTAARA DTAARA(QUSRBRM/Q1APRM (201 2)) VALUE('xx')

BRMS is shipped with this value set to '05'.

Note: This affects only the journal receivers associated with journal QUSRBRM/QJ1ACM. Journal receivers associated with the QUSRBRM/QJ1AJRN2 are always deleted immediately a new journal receiver is created.




QUSRBRM/Q1AMAXFR

The following command can be used to change the flight recorder size:

  CALL PGM(QBRM/Q1AOLD) PARM(FRSIZE ' '*SET ' XXX' )
    - Where XXX is equal to 001 - 999 Note: 0s must be added to the front of the numbers

The following command can be used to change the flight recorder size:

  CALL PGM(QBRM/Q1AOLD) PARM(FRSIZE ' '*DISPLAY' )

Note: The command to change/view the flight recorder size will be available in releases IBM i 7.1 and earlier. In releases following IBM i 7.1, interfaces will be provided on the WRKPCYBRM TYPE(*SYS) work panel. The following PTFs or their superseding PTFs are required:




QUSRBRM/Q1AUTEST

This data area is used in V5R3M0 and above to collect additional information for service support.

CRTDTAARA DTAARA(QUSRBRM/Q1AUTEST) TYPE(*CHAR)

Notes:

  1. It is recommend data area QUSRBRM/Q1AMAXFR is also created to increase the size of the BRMS flight recorders
  2. When this data area exists, performance of BRMS applications will be affected



QUSRBRM/Q1ANODLTAT

Recovery reports generated with the STRRCYBRM ACTION(*REPORT) command can become very large due to the attention block that lists deleted libraries. Libraries are added to the deleted libraries attention block if they were deleted after they were saved. Libraries in the deleted libraries attention block will be excluded from the recovery. The deleted libraries attention block appears in the recovery report as follows:

----- Attention -----------------------------------
The following deleted libraries have been excluded from recovery by using *DELETE on the Libraries to omit (OMITLIB) parameter. These are libraries which have been saved and subsequently removed from the system.
    DLTLIB0001 DLTLIB0002 DLTLIB0003 DLTLIB0004 DLTLIB0005
    DLTLIB0006 DLTLIB0007 DLTLIB0008 DLTLIB0009 DLTLIB0010
    DLTLIB0011 DLTLIB0012
No additional action is necessary if these libraries are not required for system recovery. Otherwise, change the Omit libraries (OMITLIB) parameter so these libraries are not excluded, or use the following command to recover these libraries after all other saved items have been restored.
    STRRCYBRM OPTION(*LIB) ACTION(*RESTORE) LIB(library-name)
----------------------------------------------------

This data area can be used to remove the deleted libraries attention block from the recovery report.

CRTDTAARA DTAARA(QUSRBRM/Q1ANODLTAT) TYPE(*CHAR) LEN(1)

Notes:

  1. To use this data area, PTF SI37269 (V5R4M0) or PTF SI37276 (V6R1M0) is required.
  2. If you wish to include the attention block in the report, simply delete data area QUSRBRM/Q1ANODLTAT.
  3. This data area will not be supported in releases after IBM i 7.1. In releases after IBM i 7.1, an interface will be provided on the Start Recovery using BRM (STRRCYBRM) command to remove the deleted libraries attention block from the recovery report.



QUSRBRM/Q1ANOVFYM

In V5R4M0 and above, volume selection will protect volumes that are in verify move status. After the move media command (MOVMEDBRM) has been ran, volumes that need to have movement verified will not be selected as append candidates.

To enable the old behavior which allows media in verify move status to be selected as an append candidate, run the following command: CRTDTAARA DTAARA(QUSRBRM/Q1ANOVFYM) TYPE(*CHAR).

Note: For releases after IBM i 7.1, no PTF is required. For release IBM i 7.1 and earlier, the following PTFs or their superseding PTFs are required:


Backups

QUSRBRM/Q1AIPLSUB

A control group may try to put the system into restricted state. If an attempt is made to restart the controlling subsystem and the system has not reached restricted state, a CPF1099 may be sent because the control subsystem is still trying to end. The only way to get out of this state is to IPL the system.

In releases V5R4M0 and later, if BRMS receives a CPF1099 when it tries to start the controlling subsystem and data area QUSRBRM/Q1AIPLSUB exists, the system will be IPLed. IPL options from the control group are used. These options may be referencing the BRMS Backup Policy or even the BRMS System Policy. The control group does not need to be set to IPL *YES in order for this IPL to occur.

CRTDTAARA DTAARA(QUSRBRM/Q1AIPLSUB) TYPE(*CHAR) LEN(1)

Note: In release V5R4M0 or later, the following PTFs or their superseding PTFs are required:




QUSRBRM/Q1AENDJOBL

In releases V5R1M0 and V5R2M0, this data area can be used to indicate how many seconds BRMS should wait after issuing the *IMMED before going into restricted state.
 

CRTDTAARA DTAARA(QUSRBRM/Q1AENDJOBL) TYPE(*CHAR) LEN(4) VALUE(xxxx)

where 'xxxx' is in seconds




QUSRBRM/Q1ATSMSIZE

A data area used when saving IFS data to a TSM server and the size specified in the data area will be used instead of finding the size from the L/R file (IFS).

CRTDTAARA DTAARA(QUSRBRM/Q1ATSMSIZE) TYPE(*CHAR) LEN(8)

CHGDTAARA DTAARA(QUSRBRM/Q1ATSMSIZE (1 8)) VALUE('00001024')

Note: The size is in MB




QTEMP/Q1ASAVOUTF

This data area can be used to retain the outfile created by BRMS when IFS objects are saved via *LINK, a link list or SAVBRM.

CRTDTAARA QTEMP/Q1ASAVOUTF TYPE(*CHAR) LEN(1)

The outfile will be stored in tmp/brms/q1asavxxxxxxSave where xxxxxx is the job number of the job that ran the save.

Note: This function is available only in V5R2M0 and above and the file will have to be sent to support for analysis.




QUSRBRM/Q1AOSYSBP

BRMS can be configured to fail rather than bypassing SAVSYS if the partition is unable to reach restricted. To enable this function on a system-wide basis, run the following command:

CRTDTAARA QUSRBRM/Q1ANOSYSBP TYPE(*CHAR) LEN(1)

This feature can also be enabled for a specific job. Create the data area in library QTEMP for the job performing the backup. For example, create the data area in a control group exit prior to running the SAVSYS command.

Note: To use this data area, PTF SI30649 (V6R1M0), PTF SI30647 (V5R4M0), or PTF SI30646 (V5R3M0) is required.




QUSRBRM/Q1AREJVOLS

BRMS can be configured to check for 200 volumes rather that 20 volumes before posting a BRM148A message during saves.

CRTDTAARA QUSRBRM/Q1AREJVOLS TYPE(*CHAR) LEN(1)

Note: To use this data area, PTF SI33260 (V5R4M0), or PTF SI33259 (V5R3M0) is required. (V6R1M0 checks for up to a 1000 by default)




QUSRBRM/Q1APRLNONE

When specifying multiple drives for the Parallel device resources parameter in a control group or SAVxxxBRM command, BRMS will attempt to do a parallel save of the data. BRMS has 2 types of parallel saves, Parallel-Parallel and Multiple-Library Parallel Concurrent Saves. BRMS will attempt to save the data in the most efficient method and when saving *IBM, *ALLUSR, generic libraries or a list of libraries, some data may be saved in the parallel-parallel method while other is saved in the parallel-serial method.

However, some users may prefer not to have data saved in the Parallel-Parallel method.

At V6R1M0, users can force the type of parallel save in the control group entries.

At V5R4M0, users can user the following data area to force parallel-serial saves of *IBM, *ALLUSR, generic libraries or a list of libraries

CRTDTAARA DTAARA(QUSRBRM/Q1APRLNONE) TYPE(*CHAR) LEN(1)

Note: This data area is no longer used in V6R1M0 and above.



Recovery

QUSRBRM/Q1AAPYJRNX

This data area can be used to enable BRMS-integrated forward recovery of your journal receivers with the APYJRNCHGX command.

CRTDTAARA DTAARA(QUSRBRM/Q1AAPYJRNX) TYPE(*CHAR) LEN(1)




QTEMP/Q1ALNKFIL

This data area is used to limit WRKLNKBRM searches to specific links. The data area must contain the path to a streamfile containing a list of the links to search for. When WRKLNKBRM encounters this data area, it will only display directories and saved items that contain the specified links. WRKLNKBRM OUTPUT(*PRINT) will also limit its search and display to the specified links, and the spoolfile will only contain the links specified. If some directories and links are omitted from the display or the spoolfile, message BRM1975 will be issued. This function is available at V5R3 and newer releases.

CRTDTAARA QTEMP/Q1ALNKFIL TYPE(*CHAR) LEN(1) value(' ')




QTEMP/Q1ALNKIGN

This data area is used in conjunction with the data area QTEMP/Q1ALNKFIL. If Q1ALNKIGN exists, WRKLNKBRM will ignore case sensitivity when searching for the specified links.

CRTDTAARA QTEMP/Q1ALNKIGN TYPE(*CHAR) LEN(1)




QTEMP/Q1ANSTRPSN

An enhancement to enable fast media positioning during restores was added for releases IBM i7.1 and above. The new function is enabled within BRMS by default. It may be necessary to disable fast positioning if a restore fails with a CPF5183 message. To disable the function, run the following command:

CRTDTAARA DTAARA(QTEMP/Q1ANSTRPSN) TYPE(*CHAR)




QUSRBRM/Q1APRVSPLF

This data area is used in V5R4M0 to allow WRKMEDIBRM FROMSYS (a system at a release prior to V5R4), Option 9 to "Work with Saved Objects" on *SAVSPLF to show the correct spooled files. PTF SI27664 or its supersede is required.

CRTDTAARA DTAARA(QUSRBRM/Q1APRVSPLF) TYPE(*CHAR) LEN(1)




QUSRBRM/Q1ASAVASP

In V5R4 and above, when restoring an object or library to a specified I-ASP using a RSTOBJBRM or RSTLIBBRM command , and you want to restore the data to a specified iASP, there is no parameter on the commands to specify this.

To specify a iASP, create the following data area in the same job stream and the RSTxxxBRM command

CRTDTAARA DTAARA(QTEMP/Q1ASAVASP) TYPE(*CHAR) LEN(10) VALUE('xxxxxxxxxx').
Where xxxxxxxxxx is replaced by the I-ASP's Name.

This will insure that BRMS restores the correct saved item.

Note: To use this data area, PTF for V5R4m0 is SI33974 or for V6R1M0 is SI33975 is required.




QUSRBRM/Q1ANODLTAT

Recovery reports generated with the STRRCYBRM ACTION(*REPORT) command can become very large due to the attention block that lists deleted libraries. Libraries are added to the deleted libraries attention block if they were deleted after they were saved. Libraries in the deleted libraries attention block will be excluded from the recovery. The deleted libraries attention block appears in the recovery report as follows:

----- Attention -----------------------------------
The following deleted libraries have been excluded from recovery by using *DELETE on the Libraries to omit (OMITLIB) parameter. These are libraries which have been saved and subsequently removed from the system.
    DLTLIB0001 DLTLIB0002 DLTLIB0003 DLTLIB0004 DLTLIB0005
    DLTLIB0006 DLTLIB0007 DLTLIB0008 DLTLIB0009 DLTLIB0010
    DLTLIB0011 DLTLIB0012
No additional action is necessary if these libraries are not required for system recovery. Otherwise, change the Omit libraries (OMITLIB) parameter so these libraries are not excluded, or use the following command to recover these libraries after all other saved items have been restored.
    STRRCYBRM OPTION(*LIB) ACTION(*RESTORE) LIB(library-name)
----------------------------------------------------

This data area can be used to remove the deleted libraries attention block from the recovery report.

CRTDTAARA DTAARA(QUSRBRM/Q1ANODLTAT) TYPE(*CHAR) LEN(1)

Notes:

  1. To use this data area, PTF SI37269 (V5R4M0) or PTF SI37276 (V6R1M0) is required.
  2. If you wish to include the attention block in the report, simply delete data area QUSRBRM/Q1ANODLTAT.



QTEMP/Q1ASPLTMZN

This data area is used to restore spool file data that was saved in a different time zone than time zone of the system doing the restore.

CRTDTAARA QTEMP/Q1ASPLTMZN TYPE(*CHAR) LEN(10) VALUE('xxxxxxxxxx') where 'xxxxxxxxxx' is the time zone value of the system where the original save was done.
For example:
CRTDTAARA QTEMP/Q1ASPLTMZN TYPE(*CHAR) LEN(10) VALUE('Q0000UTC ')

Notes:

1) To use this data area, the following PTFs or their superseding PTFs are required:


2) This data area will not be supported for spool files saved in releases after IBM i 7.1. In releases after IBM i 7.1, the time zone at the time of the save will be stored so that it can be used for any restores, no data area value will be requireded.




General

QTEMP/Q1ACLRSQL

Activation group Q1ABRMS uses SQL CLI with open data sources. The open data sources may cause conflicts with other users of the SQL CLI that change environment variables in the same job. To prohibit these SQL CLI conflicts within a job, run the following commands:

  1. CRTDTAARA DTAARA(QTEMP/Q1ACLRSQL) TYPE(*CHAR)
  2. RCLACTGRP ACTGRP(Q1ABRMS)

Note: In releases IBM i 7.1 or earlier, the following PTFs or their superseding PTFs are required:



Networking

QUSRBRM/Q1ATCPIP

A V5R1 data area to indicate that TCP/IP should be used before SNA. Note that V5R2 and above does not use this data area. Users need to set TCP/IP networking in the system policy (WRKPCYBRM *SYS, Option 4)

CRTDTAARA DTAARA(QUSRBRM/Q1ATCPIP) TYPE(*CHAR) LEN(1)

Go to http://www.ibm.com/systems/i/support/brms/brms/brmstcpip.html to find more information about TCP/IP networking in BRMS.




QUSRBRM/Q1ANOPING

This data area can be used to to prevent BRMS from doing a PING before any BRMS communications activity to ensure that the network is active.
 

CRTDTAARA DTAARA(QUSRBRM/Q1ANOPING) TYPE(*CHAR) LEN(1)




QUSRBRM/Q1ATCPIFC

With PTFs SI36193(V5R4), SI36197(V6R1) or their supeseding PTF applied, the TCP/IP address used is no longer stored in this data area. The TCP/IP address will now be stored in the QUSRBRM/QA1ARI file.

In Release V5R2M0 and V5R3M0, this data area is created when BRMS has been set up to use TCP/IP in a restricted state. For additional information, refer to the following Web site: http://www.ibm.com/systems/i/support/brms/brmstcpip.html#restrict

DSPDTAARA DTAARA(QUSRBRM/Q1ATCPIFC)

If restricted state TCP/IP has been enabled, the TCP/IP address of the system that the command is run from will be in the data area.

 Data area . . . . . . . :  Q1ATCPIFC
 Library . . . . . . . . :  QUSRBRM
 Type . . . . . . . . .  :  *CHAR
 Length . . . . . . . .  :  2000
 Text . . . . . . . . .  :

 Value
 Offset   *...+....1....+....2....+....3....+....4....+....5
  0    '1  9.2.1.155                   '
  50    '                         '
 100    '                         '
 150    '                         '
 200    '                         '
 250    '                         '
 300    '                         '
 350    '                         '
 400    '                         '



QUSRBRM/Q1ASYNTIM

When PTFs SI38733 for V5R4M0 or SI38739 for V6R1M0 or their superseding PTFs are loaded and applied, BRMS will no longer support the option 8 "Set time" on the network panel (WRKPCYBRM TYPE(*SYS) Option 4). Those still wishing to use the function can create the following data area:

CRTDTAARA DTAARA(QUSRBRM/Q1ASYNTIM) TYPE(*CHAR) LEN(1)

Once this data areas exists, WRKPCYBRM TYPE(*SYS) Option 4 Option 8 will sync the time on the target system to the current system's time.



Notes/Domino

QTEMP/Q1APOINT

Used for Lotus Domino Point in Time Recovery on Green Screen.

Recovering just the on-line - full backup (no incremental):

CRTDTAARA DTAARA(QTEMP/Q1APOINT) TYPE(*CHAR) LEN(14) VALUE('*FULL ')

Recovering to a point-in-time (full plus incremental):

CRTDTAARA DTAARA(QTEMP/Q1APOINT) TYPE(*CHAR) LEN(14) VALUE(yyyymmddhhmmss)

where yyyy is the year, mm is the month, dd is the day, hh is the hour, mm is the minutes and ss is the seconds.

Example: VALUE('20010525161212') represents a point-in-time of May 25th, 2001 at 16:12:12 Note that the time is entered in 24-hour clock format.

Please go to http://www.ibm.com/systems/i/support/brms/domIncremental.html in order to find out more information about point in time recovery in BRMS.




QUSRBRM/NOLTSCFG

Will turn off Lotus Configuration during STRMNTBRM , INZBRM *DATA or Slip Install or Upgrade.

CRTDTAARA DTAARA(QUSRBRM/NOLTSCFG) TYPE(*CHAR) LEN(1)

WARNING: Creating this data area will prevent the creation of the QLTS* control groups and the updating of these control groups when INZBRM *DATA or STRMNTBRM is run.




QUSRBRM/Q1ANLSTOMT

Domino expects to be able to access the *.ini and *.id files and the gtrhome and /tmp directories. Saving these files or directories while the Domino server is active may make these files or directories unavailable to Domino and potentially cause some unpredictable results within Domino. We would recommend creating the data area:

CRTDTAARA DTAARA(QUSRBRM/Q1ANLSTOMT) TYPE(*CHAR) LEN(1)

This would omit saving these objects:

*.ini

*.id

gtrhome

/tmp

For the *.ini and *.id files, we would recommend periodically making a copy of those objects and saving the copies.

More information can be found at the following URL: http://www.ibm.com/support/docview.wss?uid=swg21404738




QTEMP/Q1ADAOSSEP

In the BRMS September 2010 PTF (see below for numbers) and with the Domino 8.5.2 release, you can now separate out the domino databases (nsf files) from the directory attach object services(DAOS) objects (nlo files). This allows you to do full and incremental backup in a mixed fashion. Maybe you want a full save of the databases every day, but incremental saves on the weekdays of the DAOS objects, this is now possible.

We have enhanced the weekly activity to support two new backup activities to go with the 2 current ways to back them up. Currently, when you select an ‘F’ for a full, you get both a full save of the domino databases and a full save of the DAOS objects. If you select an ‘I” for incremental save you will get an incremental save of both.

The two new backup activities are:

  1. N’ for a full save of the domino databases but an incremental save of the DAOS objects
  2. ‘D’ for an incremental save of the domino databases but a full save of the DAOS objects.

Note: ‘N’ and ‘D’ are the defaults, but can be customized.

To enable this function, you will need to create a data area:

CRTDTAARA DTAARA(QUSRBRM/Q1ADAOSSEP) TYPE(*DEC) LEN(1)

It may be possible, in a future ptf, to eliminate the need for this data area.

In a futurePTF, BRMS will look to not requiring the data area, but will always run separate.

The recovery report(QP1ARCY) generated by the Start Recovery using BRMS (STRRCYBRM) and Work with Media Information(WRKMEDIBRM) will be enhanced to display 2 new save types:
*DAOSF - A full save of the DAOS objects for that Domino server
*DAOSI - An incremental save of the DAOS objects for that Domino server.

Note: If you use ‘N’ and/or ‘D’, we will run in separated mode , regardless of data area.

Overriding the presentation characters for Domino Databases and DAOS weekly backup activity

Use the following command to override the default presentation characters that are used to represent domino databases and DAOS object saves in weekly activity fields. The default, 'N' is used to represent 'Domino Database full backups and incremental DAOS object backups' and 'D' is used to represent ‘Domino Database incremental backups and full DAOS object backups'.

CALL PGM(QBRM/Q1AOLD) PARM('DAOSCHARS ' '*SET ' ' ' 'N' ‘D')

To show the override values for presentation characters that are used to represent Domino and DAOS, use the following command:

CALL PGM(QBRM/Q1AOLD) PARM('DAOSCHARS ' '*DISPLAY' ' ')

Note: The presentation character overrides for Domino and DAOS will only be available in releases IBM i 7.1 and earlier. In releases following IBM i 7.1, interfaces will be provided on BRMS commands.

Note: The BRMS client will not allow changing of control groups until the releases following IBM i 7.1.

The following PTFs or their superseding PTFs are required:



We're here to help

Easy ways to get the answers you need.


or call us at
1-866-883-8901
Priority code:
101AR13W