Troubleshooting
Problem
There are numerous data areas available in BRMS that can help users change the functionality of BRMS.
Resolving The Problem
There is numerous data areas available in BRMS that can help users change the functionality of BRMS. Following is a list and a brief description of the available data areas:
Data Area: QTEMP/Q1APOINT
Used for IBM Lotus Domino Point in Time Recovery on Green Screen.
Recovering only the online, full backup (no incremental):
Recovering to a point-in-time (full plus incremental):
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.
For example: VALUE('20010525161212') represents a point-in-time of May 25, 2001 at 16:12:12
Data Area: QUSRBRM/NOLTSCFG
Will turn off Lotus Configuration during STRMNTBRM, INZBRM *DATA, or Slip Install or Upgrade.
Data Area: QUSRBRM/Q1ANOSYSCK
Will stop checking for same system on picking media even if it cannot ensure using the network that it can use this media. Requires PTFs SI04977 for V5R1M0 and SI05044 for V5R2M0 or the superseding PTFs.
Note: This data area is ignored if using tape media libraries. This works only if using stand-alone drives.
Data Area: QUSRBRM/Q1AREFREE
This data area improves performance with RUNCLNUP(*YES) dealing with re-freeing of auto-retrieved objects. If data exists, this re-freeing is not done.
Note: This data area is required for R520 and below only. There is an option in R530 and above in STRMNTBRM command, REFREE. Integrated File System objects cannot be auto re-freed in current releases.
Data Area: QUSRBRM/Q1AQRYEST
Data Area: QUSRBRM/Q1ATCPIP
A V5R1, this data area indicates that TCP/IP should be used before SNA. V5R2 and above does not use this data area. Users must set TCP/IP networking in the system policy (run the WRKPCYBRM *SYS command, and select Option 4).
Note: PTF SI01742 or greater is required on the V5R1 system.
For additional information, refer to the following website: TCPIP Networking
Data Area: QUSRBRM/Q1ATSMSIZE
This data area is used when saving Integrated File System data to a Tivoli Storage Manager (TSM) server. The size specified in the data area is used rather than finding the size from the L/R file (Integrated File System).
Note: The size is in MB.
Data Area: QTEMP/QSRPARFMT
This data area can be used to force saves to be done in true parallel format (object spreading across tape drives).
This capability does not apply if LIB(*ALLUSR), LIB(*IBM), or LIB(*NONSYS) is specified on the SAVLIB command.
Note: V5R4M0 is the last release to use the existence of data area QTEMP/QSRPARFMT to indicate that multiple libraries are to be saved in parallel format.
Data Area: 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.
Where xxxx is in seconds.
Data Area: QUSRBRM/Q1ANOPING
In releases V5R1M0 and above, this data area can be used to allow BRMS to DDM without first checking that a network connection is available by running a PING command
Note: Use this data area only if you cannot allow PINGs between systems.
Data Area: QUSRBRM/Q1ATCPIFC
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, for V5R4 and above refer to the following website: How do I setup to use TCPIP in a restricted state
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.
Notes:
Data Area: QUSRBRM/Q1APRM
This data area 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:
The following is shown:
The value of this data area can be changed to 1 using the following command:
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.
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.
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. when movement (MOVMEDBRM) is run. This is achieved by BRMS issuing the Remove Tape Cartridge (RMVTAPCTG) command. 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.
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 before 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".
Movement table
The value of this data area can be changed to 'xx' using the following command (where xx is the number of days):
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.
Data Area: QUSRBRM/Q1AAPYJRNX
This data area is used with SAP
Note: To enable BRMS-integrated forward recovery of your journal receivers using the APYJRNCHGX command, install PTF SI21665 (V5R3) or SI21664 (V5R4).
Refer to Chapter 23. Backup and Recovery at the following website:
http://www.redbooks.ibm.com/redbooks/pdfs/sg247166.pdf
Data Area: QTEMP/Q1ALNKFIL
This data area is used to limit the WRKLNKBRM command searches to specific links. The data area must contain the path to a stream file that contains a list of the links to search for. When the WRKLNKBRM command encounters this data area, it displays only directories and saved items containing the specified links. The WRKLNKBRM OUTPUT(*PRINT) also limits the search and display to the specified links, and the spooled file contains only the links specified. If some directories and links are omitted from the display or the spooled file, BRM1975 is issued. This function is available at V5R3 and newer releases.
The specified stream file must contain data in the CCSID of the job performing the WRKLNKBRM.
Data Area: 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.
Note: To use this data area, PTF SI27222 (V5R4M0) or SI27220 is required.
Data Area: 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.
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.
Data Area: QUSRBRM/Q1AIGNRDUP
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.
Data Area: QUSRBRM/Q1APRVSPLF
This data area is used in V5R4M0 to allow WRKMEDIBRM FROMSYS (a system at a release earlier than V5R4), Option 9 to "Work with Saved Objects" on *SAVSPLF to show the correct spooled files. PTF SI27664 or its supersede is required.
Data Area: QUSRBRM/Q1AMAXFR
This data area is used to specify the size of the BRMS flight recorders in directory '/tmp/brms'
There are 2 options available depending on the BRMS PTF level:
Option 1:
If the following PTFs or their superseding PTFs are applied:
To change the flight recorder size (in megabytes) to 001-999 run this command:
- Where XXX is equal to 001 - 999. Note: 0's must be added to the front of the numbers
To show the current flight recorder size run this command:
Option 2:
If the following PTFs or their superseding PTFs are applied:
or
Notes:
1. If the data area does not exist, the maximum size of the flight recorder will be 10 MB .
2. If the data area exists and the length (LEN) parameter is set to 1 , the maximum size will be 500 MB.
3. If the length (LEN) parameter is set to 9 characters, the size of the data area will be set to the approximate value specified in the VALUE parameter. Example: For a 30 MB (approximate) flight recorder, set the VALUE parameter to '030000000'. This allows the flight recorders to be between 0 and 999999999 bytes. If the value is set to 0, only one entry will be listed in the flight recorder.
4. In V5R4 and above the BRMS flight recorders will default to 50 MB when the following PTF's are applied:
- SI42923 (R540)
- SI42924 (R610)
- SI42925 (7.1)
If you wantto keep it at 10 Meg, please run this command:
Data Area: QUSRBRM/Q1AUTEST
This data area is used in V5R3M0 and above to collect additional information for service support.
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
Data Area: QUSRBRM/Q1ACRTDOLD
Normally the creation date of a volume will only be updated when data is written to the first sequence on the volume.
OPTION 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.
Notes:
1. To use this data area with OPTION 1, PTF SI30649 (V6R1M0) or SI30647 (V5R4M0) or SI30646 (V5R3M0) is required.
2. This only works when SAVMEDIBRM or the BRMS recovery information in a control group is saved.
OPTION 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.
Note: To use this data area with OPTION 2, PTF SI37276 (V6R1M0) or SI37269 (V5R4M0) is required.
Data Area: 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.
Note: To use this data area, PTF SI30649 (V6R1M0), PTF SI30647 (V5R4M0), or PTF SI30646 (V5R3M0) is required.
Data Area: 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:
Note: To use this data area, PTF SI30649 (V6R1M0), PTF SI30647 (V5R4M0), or PTF SI30646 (V5R3M0) is required.
Data Area: QUSRBRM/Q1AREJVOLS
BRMS can be configured to check for 200 volumes rather that 20 volumes before posting a BRM148A message during saves.
Note: To use this data area, PTF SI33260 (V5R4M0), or PTF SI33259 (V5R3M0) is required. (V6R1M0 checks for up to a 1000 by default)
Data Area: QUSRBRM/Q1AALWMFDP
BRMS can be configured to allow multiple parallel volumes to be appended to the same 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.
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.
4. When using the auto duplication function with this data area created, jobs need to be submitted to a single threaded job queue.
5. At V7R1 only the dupmedbrm command has to be changed or a copy made and put in a library ahead of qsys. CHGCMDDFT CMD(DUPMEDBRM) NEWDFT('TOSEQNBR(*END)')
Data Area: 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
Where xxxxxxxxxx is replaced by the I-ASP's Name.
This will ensure that BRMS restores the correct saved item.
Note: To use this data area, PTF SI33974 (V5R4M0) or SI33975 (V6R1M0) is required.
Data Area: 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 (using 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:
Data Area: 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 want 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.
Data Area: 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 does 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 IPL-ed. 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.
Note: In release V5R4M0 or later, the following PTFs or their superseding PTFs are required:
Data Area: QUSRBRM/Q1ANOSNA
At V5R4M0 or earlier releases, this data area will automatically be created when SNA is disabled in a BRMS environment.
More information can be found on disabling the SNA network at the following URL: How do I enable-disable SNA for my BRMS network
Data Area: 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:
To disable this new function, run the following command:
Note: In release IBM i 7.1 or earlier, the following PTFs or their superseding PTFs are required:
Data Area: 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:
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:
Data Area: 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 and earlier, the following PTFs or their superseding PTFs are required:
Data Area: 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:
Data Area: QTEMP/Q1ASPLFDUP
In V5R4 and above, when doing a WRKSPLFBRM, OUTPUT(*), it is not the same as OUTPUT(*PRINT). This PTF will also change the
OUTPUT(*) to not list entries from duplicate volumes. If a data area QTEMP/Q1ASPLFDUP is created, then all original
items and duplication's are displayed.
Note: The following PTFs or their superseding PTFs need to be applied
Data Area: QUSRBRM/Q1ACLSNONE
This data area allows BRMS to pick any media class in a tape media library or any media class that is loaded in a tape drive.
Note: Notes:
1. Once a density is selected, all additional media being selected in the current job will have to have the same density (cartridge type - LTO).
2. No mixed densities (cartridge types - LTO) within a media set
3. If doing parallel saves, all the cartridges will have to have the same density or cartridge type (LTO)
4. The following PTFs or their superseding PTFs are required:
o V7R2M0 SI52668
o V7R1M0 SI51667
o V6R1M0 SI51666
Data Area: QUSRBRM/Q1ARMTEJT
Eject media from an MLB that is not configured on the local system
Data Area: QTEMP/Q1APOINT
Used for IBM Lotus Domino Point in Time Recovery on Green Screen.
Recovering only the online, 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.
For example: VALUE('20010525161212') represents a point-in-time of May 25, 2001 at 16:12:12
Data Area: QUSRBRM/NOLTSCFG
Will turn off Lotus Configuration during STRMNTBRM, INZBRM *DATA, or Slip Install or Upgrade.
CRTDTAARA DTAARA(QUSRBRM/NOLTSCFG) TYPE(*CHAR) LEN(1)
| Caution: Creating this data area prevents the creation of the QLTS* control groups and the updating of these control groups when INZBRM *DATA or STRMNTBRM is run. |
Data Area: QUSRBRM/Q1ANOSYSCK
Will stop checking for same system on picking media even if it cannot ensure using the network that it can use this media. Requires PTFs SI04977 for V5R1M0 and SI05044 for V5R2M0 or the superseding PTFs.
Note: This data area is ignored if using tape media libraries. This works only if using stand-alone drives.
| Caution: Data could be lost. Thoroughly read Information APAR II13467 before running this command. To link to Information APAR II13467 immediately, click here. |
CRTDTAARA DTAARA(QUSRBRM/Q1ANOSYSCK) TYPE(*CHAR) LEN(1)
Data Area: QUSRBRM/Q1AREFREE
This data area improves performance with RUNCLNUP(*YES) dealing with re-freeing of auto-retrieved objects. If data exists, this re-freeing is not done.
CRTDTAARA DTAARA(QUSRBRM/Q1AREFREE) TYPE(*CHAR) LEN(1)
Note: This data area is required for R520 and below only. There is an option in R530 and above in STRMNTBRM command, REFREE. Integrated File System objects cannot be auto re-freed in current releases.
Data Area: QUSRBRM/Q1AQRYEST
The BRMS product, after loading PTF SI24433 for V5R4M0, SI24427 for V5R3M0, or SI24426 for V5R2M0, will default to change the query time limit for the job to *NOMAX. This affects all other work done after BRMS runs and prevents the problem with query estimator causing a CPF427F error. If this behavior is not wanted, after loading on PTFs, it can be disabled by running the following commands:
CRTDTAARA DTAARA(QUSRBRM/Q1AQRYEST) TYPE(*CHAR) LEN(1)
CHGOBJOWN OBJ(QUSRBRM/Q1AQRYEST) OBJTYPE(*DTAARA) NEWOWN(QBRMS)
Data Area: QUSRBRM/Q1ATCPIP
A V5R1, this data area indicates that TCP/IP should be used before SNA. V5R2 and above does not use this data area. Users must set TCP/IP networking in the system policy (run the WRKPCYBRM *SYS command, and select Option 4).
Note: PTF SI01742 or greater is required on the V5R1 system.
CRTDTAARA DTAARA(QUSRBRM/Q1ATCPIP) TYPE(*CHAR) LEN(1)
For additional information, refer to the following website: TCPIP Networking
Data Area: QUSRBRM/Q1ATSMSIZE
This data area is used when saving Integrated File System data to a Tivoli Storage Manager (TSM) server. The size specified in the data area is used rather than finding the size from the L/R file (Integrated File System).
CRTDTAARA DTAARA(QUSRBRM/Q1ATSMSIZE) TYPE(*CHAR) LEN(8)
CHGDTAARA DTAARA(QUSRBRM/Q1ATSMSIZE (1 8)) VALUE('00001024')
Note: The size is in MB.
Data Area: QTEMP/QSRPARFMT
This data area can be used to force saves to be done in true parallel format (object spreading across 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.
Note: V5R4M0 is the last release to use the existence of data area QTEMP/QSRPARFMT to indicate that multiple libraries are to be saved in parallel format.
Data Area: 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(*DEC) LEN(4) VALUE(xxxx)
Where xxxx is in seconds.
Data Area: QUSRBRM/Q1ANOPING
In releases V5R1M0 and above, this data area can be used to allow BRMS to DDM without first checking that a network connection is available by running a PING command
CRTDTAARA DTAARA(QUSRBRM/Q1ANOPING) TYPE(*CHAR) LEN(1)
Note: Use this data area only if you cannot allow PINGs between systems.
Data Area: QUSRBRM/Q1ATCPIFC
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, for V5R4 and above refer to the following website: How do I setup to use TCPIP in a restricted state
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 ' ' Notes:
| 1. | With PTFs SI36193(V5R4), SI36197(V6R1) or their superseding 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. |
| 2. | Starting with PTF SI37269 (V5R4M0) or PTF SI37276 (V6R1M0), you can remove all of the currently defined interfaces by issuing QSYS/CALL QBRM/Q1AOLD PARM('TCPIPIFC' '*REMOVE' '*ALL') and you can display all of the currently defined interfaces by issuing QSYS/CALL QBRM/Q1AOLD PARM('TCPIPIFC' '*DISPLAY' '*ALL'). |
| 3. | MSGCPF1015 - Data area Q1ATCPIFC in QUSRBRM not found, will be logged after PTF SI37269 (V5R4M0) or PTF SI37276 (V6R1M0) or higher is installed. |
Data Area: QUSRBRM/Q1APRM
This data area 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:
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 v <-- where 'v' is the value of byte 210 '
250 ' '
300 ' '
350 ' '
400 ' ' The value of this data area can be changed to 1 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.
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.
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. when movement (MOVMEDBRM) is run. This is achieved by BRMS issuing the Remove Tape Cartridge (RMVTAPCTG) command. 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.
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 before 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".
Movement table
Type |
Direction of Volume Action |
Operation |
Volume status |
Comments |
Q1APRM = ' ' |
leave (mlb) |
MOVMEDBRM |
*Eject |
When we run MOVMEDBRM, BRMS will invoke RMVTAPCTG to eject volume. |
return ( to mlb) |
Insert volume manually |
*Insert |
When customer inserts volume to MLB manually, |
|
MOVMEDBRM |
*available (could be *share/noshare) |
After we run MOVMEDBRM, status of volume will be changed to *SHARE400/*NOSHARE...due to the addtapctg command brms issued. |
||
Q1APRM = ' ' |
leave |
MOVMEDBRM |
*Eject |
Volume is ejected, but at the same time, DB is not updated till we verify it. |
VFYMOVBRM |
*Eject |
DB is updated, volume is "moved" in BRMS db. |
||
return |
Insert volume manually |
*insert |
Location is updated when MOVMEDBRM is run, but ADDTAPCTG is only run once the volume is verified |
|
MOVMEDBRM |
*available (could be *share/noshare) |
ADDTAPCTG is run but DB is not updated that it was moved. |
||
VFYMOVBRM |
*available (could be *share/noshare) |
Only after we verify these movement, is the BRMS DB updated. |
||
Q1APRM = '1' |
same as the first type |
same as the first type |
same as the first type |
same as the first type |
Q1APRM = '1' |
leave |
MOVMEDBRM |
*available (could be *share/noshare) |
DB is setup for verification but media is NOT moved. |
VFYMOVBRM |
*Eject |
Volume is ejected and "moved" in BRMS db and verified. |
||
return |
Insert volume manually |
*Insert |
Customer moves volume back (into I/O slot) |
|
MOVMEDBRM |
*Insert |
DB is setup for verification but media is NOT moved. |
||
VFYMOVBRM |
*available (could be *share/noshare) |
when volume is in MLB and we also verify it. It can be available....we also issue the ADDTAPCTG command on it to make it available. |
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.
Data Area: QUSRBRM/Q1AAPYJRNX
This data area is used with SAP
CRTDTAARA (DTAARA(QUSRBRM/Q1AAPYJRNX) TYPE(*CHAR) LEN(1)
Note: To enable BRMS-integrated forward recovery of your journal receivers using the APYJRNCHGX command, install PTF SI21665 (V5R3) or SI21664 (V5R4).
Refer to Chapter 23. Backup and Recovery at the following website:
http://www.redbooks.ibm.com/redbooks/pdfs/sg247166.pdf
Data Area: QTEMP/Q1ALNKFIL
This data area is used to limit the WRKLNKBRM command searches to specific links. The data area must contain the path to a stream file that contains a list of the links to search for. When the WRKLNKBRM command encounters this data area, it displays only directories and saved items containing the specified links. The WRKLNKBRM OUTPUT(*PRINT) also limits the search and display to the specified links, and the spooled file contains only the links specified. If some directories and links are omitted from the display or the spooled file, BRM1975 is issued. This function is available at V5R3 and newer releases.
CRTDTAARA QTEMP/Q1ALNKFIL TYPE(*CHAR) LEN(<length of path>) value('<path to file'>)
The specified stream file must contain data in the CCSID of the job performing the WRKLNKBRM.
Data Area: 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)
Note: To use this data area, PTF SI27222 (V5R4M0) or SI27220 is required.
Data Area: 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.
Data Area: QUSRBRM/Q1AIGNRDUP
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)
Data Area: QUSRBRM/Q1APRVSPLF
This data area is used in V5R4M0 to allow WRKMEDIBRM FROMSYS (a system at a release earlier than 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)
Data Area: QUSRBRM/Q1AMAXFR
This data area is used to specify the size of the BRMS flight recorders in directory '/tmp/brms'
There are 2 options available depending on the BRMS PTF level:
Option 1:
If the following PTFs or their superseding PTFs are applied:
- V7R1M0 SI44710
- V6R1M0 SI44709
- V5R4M0 SI44708
To change the flight recorder size (in megabytes) to 001-999 run this command:
CALL PGM(QBRM/Q1AOLD) PARM('FRSIZE' '*SET' 'XXX')
- Where XXX is equal to 001 - 999. Note: 0's must be added to the front of the numbers
To show the current flight recorder size run this command:
CALL PGM(QBRM/Q1AOLD) PARM('FRSIZE' '*DISPLAY')
Option 2:
If the following PTFs or their superseding PTFs are applied:
- V7R1M0 Base
- V6R1M0 SI33065
- V5R4M0 SI33064
- V5R3M0 SI33063
CRTDTAARA DTAARA(QUSRBRM/Q1AMAXFR) TYPE(*CHAR) LEN(1)
or
CRTDTAARA DTAARA(QUSRBRM/Q1AMAXFR) TYPE(*CHAR) LEN(9) VALUE('xxxxxxxxx')
Notes:
1. If the data area does not exist, the maximum size of the flight recorder will be 10 MB .
2. If the data area exists and the length (LEN) parameter is set to 1 , the maximum size will be 500 MB.
3. If the length (LEN) parameter is set to 9 characters, the size of the data area will be set to the approximate value specified in the VALUE parameter. Example: For a 30 MB (approximate) flight recorder, set the VALUE parameter to '030000000'. This allows the flight recorders to be between 0 and 999999999 bytes. If the value is set to 0, only one entry will be listed in the flight recorder.
4. In V5R4 and above the BRMS flight recorders will default to 50 MB when the following PTF's are applied:
- SI42923 (R540)
- SI42924 (R610)
- SI42925 (7.1)
If you wantto keep it at 10 Meg, please run this command:
CRTDTAARA DTAARA(QUSRBRM/Q1AMAXFR) TYPE(*CHAR) LEN(9) VALUE('010000000')
Data Area: 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
Data Area: QUSRBRM/Q1ACRTDOLD
Normally the creation date of a volume will only be updated when data is written to the first sequence on the volume.
OPTION 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)
Notes:
1. To use this data area with OPTION 1, PTF SI30649 (V6R1M0) or SI30647 (V5R4M0) or SI30646 (V5R3M0) is required.
2. This only works when SAVMEDIBRM or the BRMS recovery information in a control group is saved.
OPTION 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 data area with OPTION 2, PTF SI37276 (V6R1M0) or SI37269 (V5R4M0) is required.
Data Area: 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. In the system policy, set the parameter "Auto enroll media" to *NO. Attempts to write or initialize tapes not enrolled in the BRMS inventory result in message BRM3D1D with reason code 0010.
CRTDTAARA QUSRBRM/Q1AONLYBRM TYPE(*CHAR) LEN(1)
Note: To use this data area, PTF SI30649 (V6R1M0), PTF SI30647 (V5R4M0), or PTF SI30646 (V5R3M0) is required.
Data Area: 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 before running the SAVSYS command.
Note: To use this data area, PTF SI30649 (V6R1M0), PTF SI30647 (V5R4M0), or PTF SI30646 (V5R3M0) is required.
Data Area: 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)
Data Area: QUSRBRM/Q1AALWMFDP
BRMS can be configured to allow multiple parallel volumes to be appended to the same 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.
4. When using the auto duplication function with this data area created, jobs need to be submitted to a single threaded job queue.
5. At V7R1 only the dupmedbrm command has to be changed or a copy made and put in a library ahead of qsys. CHGCMDDFT CMD(DUPMEDBRM) NEWDFT('TOSEQNBR(*END)')
Data Area: 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 ensure that BRMS restores the correct saved item.
Note: To use this data area, PTF SI33974 (V5R4M0) or SI33975 (V6R1M0) is required.
Data Area: 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 (using 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)
NOTE: This data area is no longer used and has been replaced by "Deleted library retention" in the media policy.
Data Area: 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:
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: Omit additional Lotus Server objects during backups - Q1ANLSTOMT
Data Area: QUSRBRM/Q1ANODLTAT
This data area is used in V5R4M0 and above to remove the attention block for deleted libraries in the BRMS recovery report QP1ARCY
Once this data areas exists, the attention block for deleted libraries will no longer show on the recovery report.
Use of this data area requires PTFs SI37269 for V5R4M0 or SI37276 for V6R1M0 or their superseding PTFs to be applied.
Data Area: 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):
This would yield a *YES behavior (which is wanted on the TS7650 to physical 3584 tape):
This would yield a *NO behavior if needed:
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.
Example CL Program:
PGM
CRTDTAARA DTAARA(QTEMP/Q1ADUPCOMP) TYPE(*CHAR) LEN(9) VALUE('*YES')
DUPMEDBRM
ENDPGM
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.
3. When media is duplicated from non-compacted to compacted media or vice versa, when doing a DSPTAP DATA(*SAVRST) or WRKMEDIBRM Option 5 will always show the value of the original volume. To verify if compaction was done, a DSPTAP DATA(*LABELS) will have to be done.
Data Area: 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
Note: This data area is no longer used at V6R1M0 and above
Data Area: QTEMP/Q1ADAOSSEP
With the BRMS September 2010 PTF (see below for numbers) and the Domino 8.5.2 release, saves of Domino databases (NSF files) can be separated from saves of Directory Attach Object Services (DAOS) objects (nlo files). This allows full and incremental backups to be done in a mixed fashion. For example, a full save of the Domino databases and an incremental save of DAOS objects can be done weekdays.
Currently, when 'F' is selected for a full save, it results in a a full save of the Domino databases and a full save of the DAOS objects. Likewise, if ‘I” is selected for an incremental save, it results in an incremental save of both. The weekly activity support has been enhanced with two new backup activities to go with the existing backup activities. The two new backup activities are as follows:
o ‘N’ for a full save of the domino databases but an incremental save of the DAOS objects
o ‘D’ for an incremental save of the domino databases but a full save of the DAOS objects.
Note: ‘N’ and ‘D’ the default values used to represent the new backup activities but they can be customized,(see section below on Customizing Presentation Characters)
To enable this function, create the following data area:
It may be possible, in a future PTF, to eliminate the need for this data area.
The recovery report (QP1ARCY) generated by the Start Recovery using BRMS (STRRCYBRM) and Work with Media Information (WRKMEDIBRM) will be enhanced to display two 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.
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'.
To show the override values for presentation characters that are used to represent Domino and DAOS, use the following command:
Notes:
1. 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.
2. The BRMS GUI 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:
o V7R1M0 SI40005
o V6R1M0 SI40006
o V5R4M0 SI40001
Data Area: QUSRBRM/Q1ASYNTIM
In V5R4M0 and above, with the listed BRMS PTFS or their superseding PTF, BRMS will no longer support the Option 8 "Set time" on the network panel (WRKPCYBRM *SYS Option 4). If users still want to use the function, for those that depend on it, a data area can be created. However, we strongly advise being careful with this function, and make sure you are only syncing the times between systems within the same network and time zone. To enable the "Set Time" function, create a data area:
This option will be disabled when the following PTF or their supersedes are applied and the data area does not exist:
o SI38733 for V5R4M0
o SI38739 for V6R1M0
o SI38740 for V7R1M0
Data Area: 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.
Notes:
1. To use this data area, the following PTFs or their superseding PTFs are required:
Data Area: 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: Omit additional Lotus Server objects during backups - Q1ANLSTOMT
Data Area: QUSRBRM/Q1ANODLTAT
This data area is used in V5R4M0 and above to remove the attention block for deleted libraries in the BRMS recovery report QP1ARCY
CRTDTAARA DTAARA(QUSRBRM/Q1ANODLTAT) TYPE(*CHAR) LEN(1)
Once this data areas exists, the attention block for deleted libraries will no longer show on the recovery report.
Use of this data area requires PTFs SI37269 for V5R4M0 or SI37276 for V6R1M0 or their superseding PTFs to be applied.
Data Area: 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.
Example CL Program:
PGM
CRTDTAARA DTAARA(QTEMP/Q1ADUPCOMP) TYPE(*CHAR) LEN(9) VALUE('*YES')
DUPMEDBRM
ENDPGM
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.
3. When media is duplicated from non-compacted to compacted media or vice versa, when doing a DSPTAP DATA(*SAVRST) or WRKMEDIBRM Option 5 will always show the value of the original volume. To verify if compaction was done, a DSPTAP DATA(*LABELS) will have to be done.
Data Area: 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 at V6R1M0 and above
Data Area: QTEMP/Q1ADAOSSEP
With the BRMS September 2010 PTF (see below for numbers) and the Domino 8.5.2 release, saves of Domino databases (NSF files) can be separated from saves of Directory Attach Object Services (DAOS) objects (nlo files). This allows full and incremental backups to be done in a mixed fashion. For example, a full save of the Domino databases and an incremental save of DAOS objects can be done weekdays.
Currently, when 'F' is selected for a full save, it results in a a full save of the Domino databases and a full save of the DAOS objects. Likewise, if ‘I” is selected for an incremental save, it results in an incremental save of both. The weekly activity support has been enhanced with two new backup activities to go with the existing backup activities. The two new backup activities are as follows:
o ‘N’ for a full save of the domino databases but an incremental save of the DAOS objects
o ‘D’ for an incremental save of the domino databases but a full save of the DAOS objects.
Note: ‘N’ and ‘D’ the default values used to represent the new backup activities but they can be customized,(see section below on Customizing Presentation Characters)
To enable this function, create the following 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.
The recovery report (QP1ARCY) generated by the Start Recovery using BRMS (STRRCYBRM) and Work with Media Information (WRKMEDIBRM) will be enhanced to display two 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.
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' ' ')
Notes:
1. 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.
2. The BRMS GUI 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:
o V7R1M0 SI40005
o V6R1M0 SI40006
o V5R4M0 SI40001
Data Area: QUSRBRM/Q1ASYNTIM
In V5R4M0 and above, with the listed BRMS PTFS or their superseding PTF, BRMS will no longer support the Option 8 "Set time" on the network panel (WRKPCYBRM *SYS Option 4). If users still want to use the function, for those that depend on it, a data area can be created. However, we strongly advise being careful with this function, and make sure you are only syncing the times between systems within the same network and time zone. To enable the "Set Time" function, create a data area:
CRTDTAARA DTAARA(QUSRBRM/Q1ASYNTIM) TYPE(*CHAR) LEN(1)
This option will be disabled when the following PTF or their supersedes are applied and the data area does not exist:
o SI38733 for V5R4M0
o SI38739 for V6R1M0
o SI38740 for V7R1M0
Data Area: 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:
- V7R1M0 SI40005
- V6R1M0 SI40006
- V5R4M0 SI40001
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 required.
3. Without this data area, users may receive a message CPF3770 when restoring spooled files from a system that has a different time zone specified or the time zone on the system has been changed since the spooled files were saved.
Data Area: QUSRBRM/Q1ACTGPMPT
In V6R1 and above, option 6 on the Work with Media Library Media screen for the WRKMLMBRM command 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.
To remove prompting when option 6 is specified, delete data area QUSRBRM/Q1ACTGPMPT with the following command.
Note: The described behavior applies to systems that have the following BRMS PTFs or their superseding PTFs are applied:
3. Without this data area, users may receive a message CPF3770 when restoring spooled files from a system that has a different time zone specified or the time zone on the system has been changed since the spooled files were saved.
Data Area: QUSRBRM/Q1ACTGPMPT
In V6R1 and above, option 6 on the Work with Media Library Media screen for the WRKMLMBRM command 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:
- V7R1M0 SI40005
- V6R1M0 SI40006
Data Area: 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 want 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.
Data Area: 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 does 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 IPL-ed. 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:
- V7R1M0 SI41206
- V6R1M0 SI41205
- V5R4M0 SI41204
Data Area: QUSRBRM/Q1ANOSNA
At V5R4M0 or earlier releases, this data area will automatically be created when SNA is disabled in a BRMS environment.
More information can be found on disabling the SNA network at the following URL: How do I enable-disable SNA for my BRMS network
Data Area: 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)
Note: In release IBM i 7.1 or earlier, the following PTFs or their superseding PTFs are required:
- V7R1M0 SI42066
- V6R1M0 SI42065
- V5R4M0 SI42064
Data Area: 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:
- V7R1M0 SI42925
- V6R1M0 SI42924
- V5R4M0 SI42923
Data Area: 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 and earlier, the following PTFs or their superseding PTFs are required:
- V7R1M0 SI43868
- V6R1M0 SI43869
- V5R4M0 SI43862
Data Area: 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)
Data Area: QTEMP/Q1ASPLFDUP
In V5R4 and above, when doing a WRKSPLFBRM, OUTPUT(*), it is not the same as OUTPUT(*PRINT). This PTF will also change the
OUTPUT(*) to not list entries from duplicate volumes. If a data area QTEMP/Q1ASPLFDUP is created, then all original
items and duplication's are displayed.
CRTDTAARA DTAARA(QTEMP/Q1ASPLFDUP) TYPE(*CHAR)
Note: The following PTFs or their superseding PTFs need to be applied
- V7R1M0 SI40005
- V6R1M0 SI40006
- V5R4M0 SI40001
Data Area: QUSRBRM/Q1ACLSNONE
This data area allows BRMS to pick any media class in a tape media library or any media class that is loaded in a tape drive.
CRTDTAARA DTAARA(QUSRBRM/Q1ACLSONE) TYPE(*CHAR) LEN(1)
Note: Notes:
1. Once a density is selected, all additional media being selected in the current job will have to have the same density (cartridge type - LTO).
2. No mixed densities (cartridge types - LTO) within a media set
3. If doing parallel saves, all the cartridges will have to have the same density or cartridge type (LTO)
4. The following PTFs or their superseding PTFs are required:
o V7R2M0 SI52668
o V7R1M0 SI51667
o V6R1M0 SI51666
Data Area: QUSRBRM/Q1ARMTEJT
Eject media from an MLB that is not configured on the local system
In releases IBM i 6.1 and later, if media that is being moved is owned by another system and the media is in an MLB that is not configured on the system doing movement, BRMS can be set up to attempt to eject the volume from the MLB on the system that owns the volume. Systems need to be in the same BRMS network
To enable this function, run the following command to create the data area:
CRTDTAARA DTAARA(QUSRBRM/Q1ARMTEJT) TYPE(*CHAR)
[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"7.1.0"}]
Historical Number
322855291
Was this topic helpful?
Document Information
Modified date:
11 October 2022
UID
nas8N1019257