Backup, Recovery, and Media Services (BRMS)

December 2022

Version: PTF 7.5 SI81688, 7.4 SI81687, 7.3 SI81686

December 15, 2022

Enhancements

In version 7.5:

  • In 7.5, the SETUSRBRM command implementation has been enhanced to provide additional authority for the supplied USER() parameter to allow remote operations from a previous release for the specified USER parameter.

In version 7.3 and later:

  • The SAVBRM command has been enhanced to support the parameter OBJDTL(*YES) or OBJDTL(*NO) to specify whether object detail is kept in the BRMS database for IFS backups. The parameter default value is OBJDTL(*YES).

  • BRMS PTF exit program processing has been enhanced to install the BRMS SQL Services when a BRMS PTF is applied.

  • BRMS has enhanced the network setup process to allow setting the local receives history and remote receives history values when adding a new system. See the BRMS wiki for more information at https://ibm.biz/brms-enhancements.

Fixes

In 7.3 version later:

  • Cloud disaster recovery incorrectly failing with messages MSGCPF3CDB, MSGCPF500F, and MSGBRM5002 has been fixed.

  • Resolved issue when multiple backups using append parameters TOSEQNBR(*END) and ENDOPT(*LEAVE) in the same job did not append to the correct volume.

  • The BRMS recovery report contained the wrong level of information for libraries starting with the letter 'Q' when using the FlashCopy specific system sync setup for IASP. This issue has been fixed.

 

September 2022

Version: PTF 7.5 SI81337, 7.4 SI81336, 7.3 SI81335

September 15, 2022

Enhancements

In version 7.3 and later:

  • BRMS has been enhanced with a new append media volume selection which verifies mounted volumes are reserved to the job before using them for backups. The purpose of this new volume selection algorithm is to prevent concurrent backup jobs from using the same volume and failing with MSGBRM148A.

  • SQL service enhancements have been added for the BRMS enterprise function. These new services give users the ability to set up nodes in a BRMS enterprise network, schedule and manage BRMS reports from a central system. See the BRMS wiki for more information.

  • BRMS enterprise reporting has been enhanced to support the PRTMOVBRM command for when using the new BRMS SQL services procedures. See the BRMS wiki for more information.

Fixes

In version 7.5:

  • The issue of INZBRM OPTION(*RESET) incorrectly failing when the user has the correct authorization to run the command has been fixed.

In version 7.3 and later:

  • Issue where users incorrectly are allowed to expire volumes assigned to a media class that denies functional usage was fixed.

  • Fixed problem in which multiple calls to the Q1ARTVMED API failed with MSGC2M3014 and MSGMCH3601.

  • The situation where turnkey cloud control groups that run interactively incorrectly may leave files locked in library QUSRBRM.

  • The parameter Option OPTION(*SECUREDDM) with Action ACTION(*SET) on the Initialize BRMS (INZBRM) command has been disabled and will fail with MSGBRM412B. BRMS encourages using the alternate method of implementing the QDDMDRDASERVER special value in the SERVER parameter of the Add Server Authentication Entry (ADDSVRAUTE) command.

  • The Work with Media Policies (WRKPCYBRM *MED) command interface to create or change a media policy with a Media class special value of *ADSM has been disabled and will fail with MSGBRM1174. The reason for this change is that IBM Tivoli Storage Manager (TSM) reached End of Support (EOS) in April of 2015.

  • Problem with running control groups built using the Add Control Group Entry (Q1AADDCGE) API failing with MSGCPD0013 fixed.

 

June 2022

Version: PTF 7.5 SI78291, 7.4 SI78290, 7.3 SI78289

June 16, 2022

Enhancements

In version 7.3 and later:

  • BRMS recovery report has been enhanced to provide improved reporting for H/A environments. This support will provide a way to generate a single BRMS recovery report using tapes from your backup and production systems in an H/A environment.

  • BRMS using IBM Cloud Storage for i has been enhanced to improve BRMS network support. The purpose of this support is to ensure duplicate volume names are not generated when any system in the BRMS network is in restricted state or when the BRMS network synchronization job is not working.

  • BRMS has been enhanced with new SQL services for the BRMS log, media library management, and backup control group information.

  • Enhancements have been made in BRMS to change the GUI only control group attributes for Allow activity overrides, Allow retention overrides, Lotus servers, Integrated Windows servers, and Guest partitions. See the BRMS wiki for more information.

  • BRMS can migrate control groups that contained GUI-generated omits to use object list omits. This function is not the default behavior but can be enabled before using the WRKCTLGBRM *BKU option 3 (Copy). See the BRMS wiki for more information

Fixes

In version 7.3 and later:

  • Issue where parallel backups may report message MSGMCH0601 fixed.

  • Issue where a RSTOBJBRM(*ALL) operation may not restore all the objects which were backed up beginning with the valid naming character $ fixed.

  • DLTLICPGM 5770BR1 fails with message MSGCPF2407 issue fixed.

  • Fixed problem with Control groups QNFSIPLFUL and QNFSIPLINC failing to backup the image catalog directories correctly using the control group attribute IPL after backup *YES.

  • Fixed the function to force an IPL when the control group ended with MSGCPF1099 using data area Q1AIPLSUB and did not IPL when using the control group attribute IPL after backup *NO.

  • Control group backup with IFS (*LINK or link lists) fails with MSGBRM2330 Error number RC3525 issue fixed.

  • Issue with the missed object policy generating an invalid missed objects link list when more than 300 IFS objects fail during the backup fixed.

May 2022

Version 7.5

May 12, 2022

New Features
  • IBM i implemented changes to improve the consistency with the underlying authority required for operational functionality. With respect to BRMS, these changes include:

    • The default authority for BRMS shipped functional usage is changing from default authority *ALLOWED to *DENIED. Use the SETUSRBRM command as a starting point to grant system operators and administrators access to BRMS functions and components. Then use the functional usage model to customize access by user.

    • The default assigned to the database shipped with BRMS is changing from *PUBLIC *USE authority to *PUBLIC *EXCLUDE.

    • The data authority for BRMS shipped flight recording is changing from data authority *RWX to *WX.

  • BRMS is introducing SQL Service interfaces as a new way to view, order, and subset BRMS information.

  • VTL iSCSI attached device support.

  • New support for Ultrium 9 (LTO9) tape drives and media.

Enhancements
  • Enhancements to Backup and Restore include:
    • The default for the Save Object using BRM (SAVBRM) command parameter Asynchronous bring (ASYNCBRING) is changing from *NO to *YES to match the SAV command default.

    • Backup control group support for IFS backups using SAVACTOPT(*ALWCHKPWRT)and SAVACTOPT(*ALL).

    • Backup control group entry support for Save active message queue library.

    • RSTLIBBRM has been enhanced with the STRJRN() and SELECT() parameters.

    • RSTOBJBRM has been enhanced with the STRJRN() parameter.

  • Media Service enhancements include:

    • WRKMEDBRM has been enhanced to select multiple From locations and multiple Media class names.

    • WRKMEDBRM has been enhanced to support OUTPUT(*OUTFILE)and OUTPUT(*OUTSTMF).

    • The Work with Media using BRM (WRKMEDBRM) parameter Select volumes(TYPE) special value *BOTH has been removed and is replaced by special value *ALL.

  • Reporting and Logging enhancements:

    • Recovery report (QP1ARCY) steps have been enhanced to include cloud recovery support for Network Install Using Network File System(NFS) and using DSI VTL iSCSI attached devices.

    • PRTRPTBRM has been enhanced with an EXPDATE() parameter to select which records to include in the report.

    • DSPLOGBRM has been enhanced to support OUTPUT(*OUTFILE)and OUTPUT(*OUTSTMF).

  • Enhancements to BRMS Policies:

    • WRKPCYBRM *SYS option for BRMS to include all messages that occur during BRMS command processing in the BRMS log.

    • WRKPCYBRM *RCY option for check the size of the restore.

    • WRKPCYBRM *BKU option for automatic virtual volume attributes.

    • The Work with Policies using BRM (WRKPCYBRM) TYPE(*BKU) default value for Asynchronous bring is changing from *NO to *YES to match the Save Object (SAV) command.

  • API and Exit Program enhancements include:

    • Reclaim Media (Q1ARCLMED) API gives users the ability to programmatically reclaim a single tape volume.

    • Change Control Group Attributes (Q1ACHGCGA) API enables users to change programmatically the control group attributes.

    • Control Group exit program support for new format BKUI0200.

    • APIs have a default assigned functional authority of *DENIED.

       

December 2021

Version: PTF 7.4 SI77382, 7.3 SI77381

December 15, 2021

Enhancements

In version 7.3 and later:

  • Append volume selection selects volumes having the same media policy retention requested by the backup.

  • A SQL service that provides a view of the control group backup status is available for BRMS.

  • BRMS has been enhanced to manage BRMS SQL services during FlashCopy processing.

Fixes

In version 7.3 and later:

  • Issue where WRKMEDIBRM restores of library objects but may not create the requested restore *OUTFILE set in the recovery policy was fixed.

  • Fixed issue where BRMS parallel backups of an object list using more than 4 stand-alone parallel devices may fail with MSGSQL0100 and MSGCPF6708.

  • BRMS turnkey created virtual device descriptions now are refreshed by the command INZBRM OPTION(*DEVICE) even when they are no longer in use.

  • Email issue - notifications may not be sent when using the BRMS 'from address' function with installed national language versions other than English was fixed.

September 2021

Version: PTF 7.4 SI76738, 7.3 SI76737

September 14th, 2021

Enhancements

In version 7.3 and later:

  • BRMS has been enhanced to support Digital Certificate Manager (DCM) environments when doing cloud disaster recovery using BRMS with IBM Cloud Storage Solutions for i.

  • BRMS has been enhanced to support parallel backup and restores when using IBM Cloud Storage Solutions for i.

  • BRMS has been enhanced to support full system FlashCopy when using IBM Cloud Storage Solutions for i.

  • DUPMEDBRM with SBMOPT(*YES) has been enhanced to delay when submitting multiple jobs to prevent volume selection collisions.

Fixes

In version 7.3 and later:

  • Issue where spooled file backups may fail with message MSGMCH1210 has been fixed.

  • BRMS support for Ultrium 9 (LTO9) tape drives and media has been added.

  • Issue involving BRMS batch restores failing with message MSGCPF0001 has been fixed.

  • The recovery report process was changed to remove an incorrect instruction to set the Allow object differences to *NONE or *FILELVL

NOTE: Starting with the September 2021 BRMS PTFs, only systems at release IBM i 7.3 or later will be supported in a BRMS network. All systems at release levels earlier than 7.3 must be removed from a BRM

June 2021

Version: PTF 7.4 SI76515, 7.3 SI76514, 7.2 SI76513

June 14, 2021

Fixes

In version 7.2 and later:

  • Issue where the BRMS function used to change the 'from address' on email notifications sent by the BRMS log would not use the updated 'from address' has been fixed.

  • The issue where STRMNTBRM and STRRCYBRM may fail with MSGMCH0603 and MSGRNQ0121 if more than 1000 duplicate volumes are used was fixed.

  • Backups using special value *ALLTEST that resolve to more than 300 libraries may run multiple backup commands instead of a single command has been fixed.

NOTE: Due to the official end of support for IBM i release 7.2 on 04-30-2021, the June 2021 PTF SI76513 is the final BRMS PTF for 7.2.

April 2021

Version: PTF 7.4 SI75084, 7.3 SI75083, 7.2 SI75082

April 14, 2021

Enhancements

In version 7.2 and later:

  • BRMS has been enhanced to support the IBM DSI VTL iSCSI device as a cloud backup solution using NFS.

Fixes

In version 7.2 and later:

  • Batch parallel restores of a multiple member file using WRKOBJBRM may not restore all the members issue was fixed.

  • Provided solution for when an *ALLUSR backup of an IASP takes a long time during BRMS outfile processing and the job log contains many MSGCPC221C messages.

  • Fixed problem with BRMS cloud backups of control groups named with the prefix QCLDBIPL using more than 16 volumes failing with MSGOPT1494.

  • Issue with parallel backups using device *MEDCLS not selecting the device with the most expired volumes was fixed.

  • Fixed issue where STRMNTBRM called QICC delete API twice when removing expired cloud volumes.

  • SQL service QUSRBRM.MEDIA_INFO view failing with MSGQRY2283, MSGCPD4019, or MSGSQL0181 for records with date fields earlier than the year 2000 was fixed.

  • DUPMEDBRM completes successfully but may incorrectly report MSGBRM0004 with reason code 14 issue was fixed.

December 2020

Version: PTF 7.4 SI74479, 7.3 SI74478, 7.2 SI74477

December 11, 2020

Enhancements

In version 7.2 and later:

  • BRMS SQL Services now give users the option to view, order, and subset the BRMS log information.
  • BRMS network sync job has been enhanced to improve performance by reducing the number journal entries processed.

Fixes

In version 7.2 and later:

  • In 7.2 and later, the BRMS network sync job QBRMSYNC in subsystem Q1ABRMNET is running slow with messages MSGCPF5009 and MSGCPF5026.

  • In 7.2 and later, WRKSPLFBRM with SLTDATE(*BEGIN) does not show all the spooled files.

  • In 7.2 and later, DSPLOGBRM command using fewer MSGID parameters than the previous DSPLOGBRM command in the same job incorrectly displays the same output.

  • In 7.2 and later, STRRCYBRM with parameters ACTION(*RESTORE) OMITLIB(*DELETE) may incorrectly list deleted libraries on the recovery report.

  • In 7.2 and later, *ALLPROD *CUM backup using MONSWABRM may fail with MSGMCH3402.

  • In 7.2 and later, INZBRM OPTION(*FLASHCOPY) STATE(*ENDPRC) incorrectly starts the BRMS enterprise subsystem Q1ABRMENT and logs MSGBRM1917 when the BRMS Advanced and Network features are not installed.

  • In 7.2 and later, CHKPRDOPT PRDID(5770BR1) incorrectly changes the authorities on the BRMS SQL service objects.

  • In 7.2 and later, backup of BRMS object list with library Q* fails with MSGCPF387 and MSGBRM1820.

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.

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

June 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.
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.
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.
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.
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.
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.
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.
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.
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.
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 IBM Partnership Products