|
The following are data areas that you can use to control various BRMS behaviors:
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/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.
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/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/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)
QUSRBRM/Q1ACRTDOLD
With this data area, the creation date of appended too volumes will change to the date the new data is saved to a volume. Without the data area, the creation date of a volume will only be updated when sequence 1 of the volume is written to.
CRTDTAARA QUSRBRM/Q1ACRTDOLD TYPE(*CHAR) LEN(1)
Note: To use this data area, PTF SI30649 (V6R1M0) or SI30647 (V5R4M0) or SI30646 (V5R3M0) is 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/Q1AIGNRDUP
This data area is used to ignore the USEDUPMED parameter in the STRRCYBRM command. USEDUPMED was introduced in V5R4 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.
CRTDTAARA DTAARA(QUSRBRM/Q1AIGNRDUP) TYPE(*CHAR)
Once this data areas exists, delete /tmp/brms/flightrec when there is no BRMS activity on the system. A new file will be created when BRMS is used again.
QUSRBRM/Q1AMAXFR
This data area is used in V5R3M0 and above to increase the maximum size of the BRMS flight recorders to 500 MB each.
CRTDTAARA DTAARA(QUSRBRM/Q1AMAXFR) TYPE(*CHAR) LEN(1)
Once this data areas exists, delete /tmp/brms/flightrec when there is no BRMS activity on the system. A new file will be created when BRMS is used again.
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:
- It is recommend data area QUSRBRM/Q1AMAXFR is also created to increase the size of the BRMS flight recorders
- When this data area exists, performance of BRMS applications will be affected
QTEMP/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/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.
Data Area: 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/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/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/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/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 DTAARA(QUSRBRM/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.
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/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
QUSRBRM/Q1ACRTDOLD
With this data area, the creation date of appended too volumes will change to the date the new data is saved to a volume. Without the data area, the creation date of a volume will only be updated when sequence 1 of the volume is written to.
CRTDTAARA QUSRBRM/Q1ACRTDOLD TYPE(*CHAR) LEN(1)
Note: To use this data area, PTF SI30649 (V6R1M0) or SI30647 (V5R4M0) or 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/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.
| 
