Backup, Recovery, and Media Services (BRMS)

September 2020

Version: PTF 7.4 SI73678, 7.3 SI73677, 7.2 SI73676

Sept. 11, 2020

Enhancements

In version 7.2 and later:

  • BRMS provides SQL services to view, order, and subset BRMS media.
  • The BRMS move policy has been enhanced to support the movement of full volumes to a new location.
  • WRKOBJBRM has been enhanced with a START() parameter to specify which saved objects entries to display first.

Other Fixes

In version 7.3 and later:

  • Fixed issue where DSPASPBRM reports the wrong IASP utilization information while an IASP is being varied off.

In Version 7.2 and later:

  • Fixed issue of BRMS expected logical files missing from QUSRBRM after an upgrade to a new release.
  • A cloud full system recovery incorrectly sets user *PUBLIC with *EXCLUDE authority for the directories in the BRMS shipped QCLDIPL *LNK list was fixed.
  • Cloud and automatic virtual backups to optical that append, may fail with messages MSGOPT2500 and MSGOPT1321 when the backup spans multiple volumes has been fixed.
  • Fixed issue where RSTLIBBRM may restore the wrong library if more than 9,999,999 records exist in the history file.
  • The issue of sync job that will not process any more entries until the Q1ABRMNET subsystem is restarted was fixed.
  • Fixed issue when restoring from a parallel backup, BRMS incorrectly attempts to restore the *CUM before the *FULL backup.
  • BRMS created outfiles with the prefix q1asav in directory '/tmp/brms' are not removed issue has been fixed.
  • STRMNTBRM with parameter PRTRCYRPT(*ALL) or PRTRCYRPT(*SAVEXCP) was enhanced to log message MSGBRM1571 in the BRMS log with severity 0 if zero objects were not saved.

June 2020

Version: PTF 7.4 SI72867, 7.3 SI72866, 7.2 SI72865

Jun 12, 2020

Enhancements

In version 7.2 and later:

  • The PRTRPTBRM command using parameter TYPE(*CLTGRPSTAT) has been enhanced with a new EXPDATE parameter to allow reporting of active control group data.
  • The PRTRPTBRM command using parameter TYPE(*CLTGRPSTAT) output report has been enhanced to show if encryption was used during the backup of any control group entries.
  • BRMS changed the sync job for maintenance with the reorg parameter RGZBRMDB(*YES) to reduce the amount of time there are locks on the networked related files to help prevent locks during maintenance.
  • BRMS has been enhanced to allow the following values for IFS Backup Control Group Entries in the Save While Active attribute: *ALWCKWR, *ALWCKSY, *LNKALL, *LNKALLS.
  • BRMS enhanced the BRMS backup control group processing of an empty *OUTQ.
  • Changes made in the BRMS Recovery Report (QP1ARCY) to streamline the required recovery steps.
Other Fixes

In Version 7.4:

  • Using WRKLNKBRM OUTPUT(*PRINT) with a date range may show additional saves that are out of that date range.

In version 7.2 and later:

  • Issue ENDOPT(*UNLOAD) does not eject media for optical devices fixed.

  • Copying a control group to the same name on the local systems with overwrite *YES incorrectly clears the control group entries issue fixed.

  • Issue with doing a remote multi-library restore from a parallel save may incorrectly skip restoring one of the libraries fixed.

  • Performing a second backup to auto virtual tape after running a parallel backup using auto virtual tape media policy QAVVRTTAP and DUPMEDBRM of those virtual tapes produced a loop in the second backup.

  • Fixed CHGMEDBRM issue that incorrectly allowed a volume marked for duplication to be expired by changing the expiration date.

  • Virtual volume cloud transfers that fail with message MSGICC0004 and MSGCPF9897 incorrectly leave the volume in *TRF status issue fixed.

  • Fixed issue occurring when the CRTLIB command defaults are changed for the ASPDEV parameter, BRMS operations may fail with messages MSGCPF0001, MSGCPF4102 RC6, MSGRNX1211, MSGRNQ1211, and MSGRNQ2002.

  • Cloud backup volumes from image catalog Q1ABRMPOOL are not being cleaned up after being transferred to the cloud.

  • Setting secure DDM using the Node Policy communications in BRMS Enterprise interface does not honor lower case password characters resulting in user profiles being incorrectly disabled.

  • Option 4 ‘Remove’ does not work for WRKPCYBRM *SYS Option 4 ‘Change network group’ when the system is in restricted state.
  • When backing up *SPL lists messages MSGCPC3701 and MSGCPI6705 are not added to the BRMS log.

  • Viewing details for BRMS web GUI failed operations may list message MSGCPF2457 for BRMS messages instead of the correct BRMS message text.
  • RSTLIBBRM and RSTOBJBRM with a SAVASP() parameter value of an IASP name that does not exist on the system incorrectly fails with MSGBRM2112.

  • When the Q1ACHKRSIZ to check the restore size is enabled, spooled file restores may fail with message MSGBRM3D1B.

In Version 7.2:

  • SAVSAVFBRM with ENDOPT(*UNLOAD) did not unload the volume.

March 2020

Version: PTF 7.4 SI71975, 7.3 SI73048, 7.2 SI71973
Enhancements

In version 7.2 and later:

  • BRMS has been enhanced to check for sufficient available storage before running restores.
  • BRMS has been enhanced to include additional job log messages from backup and restore commands in the BRMS log.
  • BRMS will no longer write flight recorder logs or image catalog file in ‘/tmp/brms’. The BRMS flight recorders will be located in ‘/QIBM/UserData/BRMS/logs’. BRMS managed image file will be located in ‘/QIBM/UserData/BRMS/cloud’.
    NOTE: BRMS maintenance needs to be run after applying the PTF to migrate existing BRMS managed image catalogs to their new locations. This initial BRMS maintenance job may run longer than normal depending on the size and number of images that need to be migrated.
Other Fixes

In version 7.2 and later:

  • Disaster recovery from a cloud backup fails to start the QICC/QICCSBS subsystem with message MSGCPF1179 preventing media from being transferred from the cloud.
  • BRMS is only using 1 device for parallel backups when the Minimum resources value is 1 or *AVAIL and Maximum resources value is greater than 1 when using a *USRMLB or multiple tape media libraries.
  • SAVLICPGM LICPGM(5770BR1) and RSTLICPGM LICPGM(5770BR1) job logs contain escape message MSGCPF1653.
  • Virtual backups may produce messages MSGCPF5009, MSGCPF5034, and MSGSQL0803 in the job log.
  • Escape messages are not added to the additional message queue by the BRMS function to send messages to an additional message queue when BRMS adds messages to the BRMS log
  • BRMS cloud backups using a virtual image size of 100Gb or greater leaves the volumes in *TRF state and the cloud transfer job log contains message MSGMCH1212
  • Running STRMNTBRM using *EXPSETMED(*YES) for media classes set to Initialize on expiration *YES may result in message MSGBRM1550 reporting an incorrect count for the number of volumes expired.
  • WRKCTLGBRM option 6 to a Add Job Schedule Entry with a Frequency of *MONTHLY and a Schedule day set to a specific day of the week creates an invalid special value date *UDRDFN.
  • Backups appending to an optical device incorrectly sends message MSGBRM15A3 to load a new volume when the current mounted volume is available to use.
NOTE: BRMS 7.3 PTF SI73048 replaces the 7.3 PTF SI71974. Consult the IBM PTF Cover Letter for more information.

January 2020

Version: PTF 7.4 SI71876, 7.3 SI71875, 7.2 SI71874
Enhancements

In version 7.2 and later:

  • BRMS enhanced the INZBRM OPTION(*FLASHCOPY) STATE(*STRPRC) processing to end the BRMS Enterprise subsystem named Q1ABRMENT.
  • BRMS now provides a Reclaim Media (Q1ARCLMED) API to reclaim a single tape volume.
  • Improved the IFS backup outfile processing performance.
  • To display the cloud retain media retention period the following command can be run:
    CALL PGM(QBRM/Q1AOLD) PARM('CLOUD ' 'RETAINDATA' 'S' 'mmmmmmmmmm' '*DSP')
    where 'mmmmmmmmmm' is the move policy name.
Other Fixes

In version 7.2 and later:

  • RSTBRM may fail with MSGBRM1688.
  • ANZLIBBRM may incorrectly report MSGCD3105 and MSGCPF9899.
  • RSTLICPGM LICPGM(5770BR1) may fail with MSGCPF3D95.
  • STRMNTBRM may fail MSGCPF501B.
  • The GUI Web Enterprise Feature and INZBRM *VFYSYS may incorrectly report connection failures when using secured DDM with mixed case passwords.
  • BRMS restores running longer with the job in MSGW and the call stack ending with Q1AMS and QMHRCVPM.
  • DUPMEDBRM with the parameter TOENDOPT(*UNLOAD) may not unload all of the target volumes.
  • Restoring *SAVSECDTA from a cloud backup using STRRCYBRM or WRKMEDIBRM appears to be in a loop as it repeats the restore 99 times.
  • In 7.2 and later, changes were made in BRMS to address potential security concerns. Existing user profiles used to perform BRMSoperations may require changes to allow proper access by using the SETUSRBRM command with the USAGE(*AUT) parameter. Note: *SECADM authority is required to use the SETUSRBRM command.

In version 7.4:

  • Upgrades with DSLO media may fail with MSGCPD377C causing 5770SS1 option 3 to go into an *ERROR state.

December 2019

Version: PTF 7.4 SI71134, 7.3 SI71133, 7.2 SI71132
Enhancements

In version 7.2 and later:

  • BRMS enhanced the INZBRM OPTION(*FLASHCOPY) STATE(*STRPRC) processing to end the BRMS Enterprise subsystem named Q1ABRMENT.
  • BRMS now provides a Reclaim Media (Q1ARCLMED) API to reclaim a single tape volume.
  • Improved the IFS backup outfile processing performance.
  • To display the cloud retain media retention period the following command can be run:
    CALL PGM(QBRM/Q1AOLD) PARM('CLOUD ' 'RETAINDATA' 'S' 'mmmmmmmmmm' '*DSP')
    where 'mmmmmmmmmm' is the move policy name.
Other Fixes

In version 7.2 and later:

  • RSTBRM may fail with MSGBRM1688.
  • ANZLIBBRM may incorrectly report MSGCD3105 and MSGCPF9899.
  • RSTLICPGM LICPGM(5770BR1) may fail with MSGCPF3D95.
  • STRMNTBRM may fail MSGCPF501B.
  • The GUI Web Enterprise Feature and INZBRM *VFYSYS may incorrectly report connection failures when using secured DDM with mixed case passwords.
  • BRMS restores running longer with the job in MSGW and the call stack ending with Q1AMS and QMHRCVPM.
  • DUPMEDBRM with the parameter TOENDOPT(*UNLOAD) may not unload all of the target volumes.
  • Restoring *SAVSECDTA from a cloud backup using STRRCYBRM or WRKMEDIBRM appears to be in a loop as it repeats the restore 99 times.

In version 7.4:

  • Upgrades with DSLO media may fail with MSGCPD377C causing 5770SS1 option 3 to go into an *ERROR state.

September 2019

Version: PTF 7.4 SI70626, 7.3 SI70625, 7.2 SI70624
Enhancements

In version 7.2 and later:

  • BRMS has enhanced the way it processes job log messages to improve performance.
  • The STRRCYBRM command now orders *IBM and *ALLUSR libraries by ascending tape sequence order.
  • BRMS has been enhanced to provide turnkey virtual support when using media classes named QAVVRTTAP or QAVVRTOPT.
Other Fixes

In version 7.2 and later:

  • Using SAVSAVFBRM for several save file backups up with different media policy retentions may set the wrong volume expiration date.
  • Cloud backups using an IASP for the cloud transfer were not checking for enough space available for the virtual media and MSGBRM1799 did not show the correct IASP name.
  • BRMS restore commands that exceed 1000 characters fail with MSGCPD0013.

  • The BRMS GUI Restore Wizard "Browse" dialog box does not show contents of IASPs.
  • BRMS user media library device support is resolving the incorrect Deallocate device command parameter for the &DEVICE variable.

In version 7.4:

  • The old world call to set the cloud transfer ASP does not change the Cloud transfer ASP setting in the backup policy.

July 2019

Version PTF 7.4 SI70368, 7.3 SI70367, 7.2 SI70366
Enhancements

In version 7.2 and later:

  • The volume selection for concurrent backups tape reservations has been enhanced.
  • Enhanced the backup omit processing to combine BRMS GUI web omits and green screen *BKUPCY omits for libraries
  • The backup control group exit program has been enhanced.
Other Fixes

In version 7.2 and later:

  • The QBRMSYNC job fails with MSGMCH1202 when using User-defined SYSBAS and IASP timestamps.
  • Non-BRMS backups to media not enrolled in BRMS fails with MSGBRM3D1D.
  • The clear missed objects policy setting is not being resolved correctly when the control group Missed Object policy is set to *BKUPCY.
  • The INZBRM OPTION(*VFYNET) or OPTION(*VFYENT) incorrectly reports MSGBRM1177 if more than 50 systems are in the BRMS network.
  • Domino restores using WRKMEDIBRM with the VOL() parameter or WRKMEDBRM options 13 to Display contents shows the wrong Domino package information.
  • Remote restores may not restore all libraries and WRKSPLFBRM remote restores may not restore expected spooled files.
  • Restores of a list of libraries backed up using serial and parallel saves may fail with MSGCPD0071, MSGCPF006, and MSGCPF61FF.
  • *ALLUSR backups using *INCR *INCR may fail with MSGCPF0550.
  • Changing the volume expiration date to an earlier date and changing the owning system for an expired volume in the same operation may cause volume owning system inconsistencies in a BRMS network.
  • An *ALLUSR control group entry using Save While Active *NO and a Save active wait time value of *NOCMTBDY for the control group attribute Pending record changes incorrectly omits Q* and #* libraries.
  • Control group backups containing a folder or spooled file list using a control group exit program may fail with MSGMCH1210.
  • Backups to sequence one may not be reflected in BRMS history if a cloud remote restore preceded the backup in the same job.
NOTE:

The PTFs for IBM i 7.3-SI69390 and IBM i 7.2-SI69389, are superseded by the above PTFs 7.3-SI70367 and 7.2-SI70366.

April 2019

Backup, Recovery, and Media Services (BRMS)

Version 7.4
Enhancements
  • Turn-key cloud control group deployment which allows customers to easily set up custom cloud control groups.
  • Enable the green screen command to change control group attributes which were previously only available in the GUI.
  • Backup for journaled objects changes is now the default setting: the default parameter value for SAVLIBBRM command has been changed to OBJJRN(*YES).
  • New *OBJ list named QALLSPLF to backup all spooled files which improves restore performance.
  • Support for the 3592-60F tape drive with *FMT3592A6 and FMT3592A6E densities.
  • Enhanced log information: uses the system timestamp to preserve message order when messages are logged at the same second are displayed using DSPLOGBRM.

March 2019

Version PTF 7.3 SI68856, 7.2 SI68855
Enhancements

In version 7.2 and later:

  • Improved virtual tape image catalog management for BRMS backups to virtual tape.
  • BRMS enhanced the select user space code to support cumulative/incremental *ALLUSR backups.
  • BRMS added the Change Control Group Attributes (Q1ACHGCGA) API.
Other Fixes

In version 7.3 and later:

  • In 7.3 and later, BRMS GUI web reclaim media fails.

In version 7.2 and later:

  • In 7.2 and later, BRMS backup job loops sending MSGBRM1017.
  • In 7.2 and later, BRMS GUI web incorrectly allows the parallel type to be set for the all IBM data
    control group entry.
  • In 7.2 and later, PRTRPTBRM TYPE(*CTLGRPSTAT) outfile information does not show device names that are less than 10 characters.
  • In 7.2 and later, DSPLOGBRM not reporting some MSGCPC37xx completion messages and some completion messages appear in the wrong order in the job log.
  • In 7.2 and later, volumes with an expiration date in the year 2039 may be changed to *VER xx during maintenance.
  • In 7.2 and later, WRKPCYBRM parameter changes are not saved when paging up or down without hitting enter.
  • In 7.2 and later, DUPMEDBRM batch jobs are not using the BRMS system policy values for Job description and Job queue for the submit job.
  • In 7.2 and later, Object lists QCLDIPL *OBJ, QCLDIPL *LNK, and QCLDOMTUSR *LNK lists are created incorrectly when 5733ICC is not installed.

December 2018

Version PTF 7.3 SI68846, 7.2 SI68845
Enhancements

In version 7.2 and later:

  • The BRM log information has been enhanced to use the system timestamp to preserve message order when messages logged at the same second are displayed using DSPLOGBRM.
  • BRMS has been enhanced to support the new 3592-60F tape drive with new *FMT3592A6 and FMT3592A6E densities.
  • BRMS has enhanced the cloud turnkey solution to allow customers to create their own disaster recovery turnkey control groups.
  • BRMS has enhanced the green screen to change the previously GUI only control group attributes for TCP/IP servers, to unmount user-defined file systems, and run maintenance after backup.
  • BRMS now creates an *OBJ list named QALLSPLF to backup all spooled files.
  • SAVLIBBRM command default for Journaled objects has been changed to OBJJRN(*YES).
Other Updates

In Version 7.2 and later:

  • WRKMEDIBRM with VOL() parameter for a specific volume was not showing any saved items.
  • The BRMS GUI web was not working with EIM/SSO.
  • BRMS GUI Web failed with MSGBRM3C4B after updating the backup policy properties.
  • IFS files greater than 4GB are now able to be archived.
  • BRMS programs that adopt authority now use qualified library programs calls.
  • WRKSPLFBRM fixed to list all the spooled files that were successfully backed up.
  • STRBKUBRM prompt for the control group parameter fixed to return all choices.

September 2018

Version PTF 7.3 SI68073, 7.2 SI68072
Enhancements
  • In 7.3 and later, IFS pattern support using include or omit option *PATINCLUDE and *PATOMIT were added to WRKLBRM *LNK lists.

  • In 7.2 and later, INZBRM OPTION(*VFYSYS) was enhanced to check if the flash copy state allows communication.
Other Fixes
  • In 7.2 and later, the BRMS function to log messages to an additional message queue is not sending the expected messages.
  • In 7.2 and later, STRBKUBRM using the STRSEQ() parameter does not start at the correct library when the starting sequence is a generic library name.
  • In 7.2 and later, backups which select volumes from a WORM media class incorrectly fail with MSGBRM148A when volumes are available.
  • In 7.2 and later, WRKSPLFBRM restores fail with MSGC2M1601.
  • In 7.2 and later, BRMS backups may fail with MSGCPD0084 (for libraries) or MSGCPF3C81, value for key 27 not valid (for IFS) when the Private Authorities parameter is incorrectly changed in a control group.
  • In 7.2 and later, running a native SAVLIB command in the same job previously used for an encrypted BRMS backup incorrectly encrypts the native SAVLIB backup.
    NOTE: Note: This fix will result in a behavior change, BRMS should not be used to encrypt native SAVLIB operations.

June 2018

Version PTF 7.3 SI67946, 7.2 SI67312, 7.1 SI67311
Enhancements
  • In 7.1 and later, BRMS cloud turn key control groups are being enhanced to use any user specified ASP storage for virtual media that is created for cloud transfers.
  • In 7.1 and later, BRMS volume selection has been enhanced to ensure WORM media are only returned if the media class being used is set with the Write once media value set to *YES.
  • In 7.2 and later, the DSPLOGBRM command has been enhanced to support a list of message identifiers on the MSGID() parameter to display or include in the report.
Other Fixes
  • In 7.1 and later, backups are showing excessive file open and close operations to the QA1ANET2 file in QUSRBRM.
  • In 7.1 and later, WRKSPLFBRM does not show correct spooled files when doing a parallel backup of an object list.
  • In 7.2 and later, GUI omits are not being honored if using the BRMS wiki documented interface to control which control groups will not use the select user space code.
  • In 7.3 and later, the BRMS menu selection shows incorrectly translated text on the BRMS Web GUI client.
  • In 7.1 and later, BRMS automatic cloud backups using a user profile with only *SAVSYS authority fails with MSGCPFA09C, MSGCPFBC02, and MSGBRM148A.
  • In 7.1 and later, if there are more than 10,000 media sets in saved history, STRRCYBRM or STRMNTBRM fails with MSGMCH0603.
  • In 7.1 and later, RSTLIBBRM using OUTPUT(*OUTFILE) posts a MSGCPD2861 message and fails to create the outfile .
  • In 7.1 and later, sequence 1 for expired volumes history records may not be removed when the volume is reused.
  • In 7.1 and later, batch parallel restores may fail with MSGSQL7011.
  • In 7.1 and later, BRMS networked systems are incorrectly allowed to send BRMS changes to a remote system while it is in flash copy mode.
  • In 7.1 and later, STRMNTBRM with RGZBRMDB(*YES) may use large amounts of system storage.
  • In 7.1 and later, RSTBRM using SAVLVL(*SAVDATE) parameter may select incorrect volume(s).
  • In 7.1 and later, DUPMEDBRM receives MSGBRM1483 message for volumes that are expired and available to use.

Back to Product Index