IBM Support


Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 APAR (Authorized Program Analysis Report)



Error Description

See Customer Problem Description.                              

Problem Summary

1. In V5R4 and above, BRMS will only support media policy      
retention through the year 2038.   Should this date be exceeded,
BRMS will mark the volume as *PERM.                            
2. In V6R1 and above, when running EXTMEDIBRM on an active      
volume, the MSGBRM1392 has an incorrect volume ID listed (first
2 characters are missing)                                      
3. In V6R1 and above, when open a Backup Control Group, BRMS GUI
will always show the fresh data to users.                      
5. In V5R4 and above, if the last volume is not selected with  
option 9 (verify and work with media) in VFYMOVBRM, BRMS will  
not display the volumes that are selected.                      
6. In V5R4 and above, when running STRMNTBRM, MSGBRM402A        
severity in BRMS log and QSYSOPR message queue does not have the
same severity.                                                  
7. In V6R1 and above, on trying to get a remote volume whilst  
saving QUSRBRM that has spanned, a lock of the QA1AMM will occur
and the BRMS code can not update the MM file until after the    
save. This will result in a failure of MSGCPF37A0.              
8. In V5R4 and above, on cancelling a save job, it is possible  
to leave cartridges in a state of  "in use" to the BRMS job ,  
making the cartridges unavailable for future backups.          
9. In V5R4 and above, after running BRMS commands in a job,    
other commands may fail with a MSGMCH3402, MSGCPF9999 and      
MSGMCH3601 F/QSQCLI.                                            
BRMS usage of the SQL CLI running in our own activation group  
and keeping data sources open causes conflicts with other users
of the CLI in our job that also use SQL and change environment  
To enable other users of the CLI within the same job as BRMS, 2
data area behaviors are being provided.                        
To force BRMS to close its SQL CLI connections after each BRMS  
command for the current signed on job.                          
2) RCLACTGRP ACTGRP(Q1ABRMS)                                    
10. In V5R4 and above, when running reports, like PRTRPTBRM,    
MSGMCH6903, MSGMCH6902, MSGMCH3601 and MSGC2M1212 may be posted.
11. In V5R4 and above, email may not be sent for messages that  
are marked for distribution, when they are written to the BRMS  
log.  This will cause a MSGCPFAF98 message in the QMSF joblog.  
Additional messages MSGTCP5101 RC3025                          
12. In V6R1 and above, on running the STRBKUBRM with an override
for the parallel resources, BRMS was ignoring them and still    
using the control group value. This has been corrected.        
13. In V6R1 and above, the D/T3592 E07's (TS1140) 4 Terabyte    
native capacity has been added to the QP1ALA report (ANZLIBBRM)
for FMT3592A4 and FMT3592A4E.                                  
14. In V7R1 and above, when saving to an expired volume and then
having a retention date that is less than the current date, the
volume will not be used to append backup items to.  This has    
been changed to support appending to this volume, but will be  
expired on the next STREXPBRM or STRMNTBRM with EXPMED(*YES).  
This will make the V6R1 behavior equal to the V7R1 and above    
15. In V5R4 and above, when using BRMS to run the library      
manager for tape cartridges, if a cartridge was not found,      
MSGCPF67D1, BRMS was not handling this and is causing the remote
tape command to be executed over and over again, until the      
cartridge was added.  We will now not update those cartridges.  
16.   In V5R4 and above, when signed on as a user without      
*ALLOBJ special authority, saves to a TSM server may fail with  
17. In V5R4 and above, when running cumulative saves of the IFS
with SAVDLOBRM DLO(*SEARCH) SEQNBR(1) and a MSGCPF902E is      
received, the *MAIL objects will be saved on a new volume rather
than appending to the first.                                    
18. In V5R4 and above, the network status of systems in a BRMS  
network are showing up as offline even though the systems are up
and communicating.                                              
19. In V5R4 and above, restricted state BRMS backups fail with  
MSGBRM148A - unable to get an expired volume from another      
20. In V5R4 and above, when BRMS is used to backup data in the  
restricted state, TCPIP should not be started when it is already
active. MSGCPF3E30 may be posted                                
21. In V5R4 and above, when IFS objects are saved to a BRMS    
volume where the expiration date is less than the current date,
the item in WRKMEDIBRM is incorrectly listed as *LABEL.        
22. In V5R4 and above, BRMS was setting the Advanced Job        
Scheduler description to "BRMS TASK". This has been changed to  
be more descriptive.                                            
23. In V5R4 and above, SAVDLOBRM incorrectly fails with        
MSGCPD0104, Expression not allowed for parameter DLO,  when    
saving folders with special characters.                        
24. In V6R1 and above, when using the BRMS Q1ARMVCGEO API a    
MSGCPF9801 can be sent.  This has been changed to allow removal
of object omits already removed.                                
25. In V5R4 and above, when running SAVSAVFBRM with a parameter
of DEV(*SAVF) on a spoolfile saved item, a MSGBRM1499 will be  
posted that devices could not be allocated.                    
26. In V7R1, when running expiration of volumes in a media set,
a MSGBRM0010 with a reason code of 4 or 5  (RC4 or RC5) can be  
sent.  However, we are changing to allow the main volume to    
expire even if there are affected volumes that can not be      
27. In V5R4 and above, when removing volumes from the BRMS      
inventory on a system that does not own the volume, the volume  
is deleted from the system running the delete but it is not    
deleted on original owning system and ownership is changed to  
the deleting system.                                            
28. In V5R4 and above, when saving libraries to parallel devices
a MSGBRM1674 can be sent when running with a version type media
29. In V6R1 and above (this has been pulled from V5R4), append  
volume selection does not protect volumes that are in verify    
move status. Volumes in verify move status can be picked as    
append candidates after MOVMEDBRM has been ran before the      
volumes have been verified.  To allow the old behavior of      
selecting media in verify move status run the following command:
Note: This check will NOT be made for volumes that have expired.
30. In V5R4 and above, when marking saved items to be duplicated
and duplicating them on a remote system, the duplication mark is
not removed on the owning machine.                              
31. In V5R4 and above, when running a control group with a      
SAVDOMBRM command to a savefile, a MSGCPF0804 may result.      

Problem Conclusion

Load and apply this PTF.                                        
After the BRMS PTF is installed, do the following to enable the
   plug-in for the IBM Systems Director Navigator for i5/OS (web
   or System i Navigator windows client.                        
   Enable the BRMS plug-in for the IBM Systems Director        
   for i5/OS.                                                  
   ==== V6R1 and newer only:                                    
   Note:  ending the http admin servers may affect other        
   From System i:                                              
    1. Enter the command to end the http admin servers:        
       endtcpsvr server(*http) httpsvr(*admin)                  
    2. Wait for the http admin server jobs to end or terminate  
       Use command:  wrkactjob sbs(qhttpsvr)                    
    3. Restart the http admin servers:                          
       strtcpsvr server(*http) httpsvr(*admin)                  
   Enable the BRMS plug-in for System i Navigator Windows/OS    
   ==== Pre-V6R1:                                              
   1) Close the System i Navigator application.                
   2) On the client/PC, uninstall the BRMS plug-in using the    
      Access Express "Selective Setup" utility:  from the      
      "Start", select                                          
      "Programs->IBM iSeries Access for Windows->Selective      
      Follow the instructions on the dialogs to uninstall the  
      plug-in.  Notes:                                          
      a) On the second dialog, select the radio button "Ignore.
         only going to UN-install components".                  
      b) On the next screen, "Component Selection", open the    
         System i Navigator folder; a list of all installed    
         System i Navigator components and plug-ins is          
      c) Deselect the BRMS plug-in to uninstall it (if you do  
         see the BRMS plug-in, it was not properly installed);  
         reboot the PC if requested.                            
   3) Start System i Navigator.                                
   4) Use the System i Navigator "Install Options->Install      
      action. This action is available from the main iSeries    
      Navigator "File" menu and the "My Connections" folder    
      context/pop-up menu.  When prompted for the iSeries system
      to install from, select the iSeries that has the new BRMS
      PTF installed.                                            
   === V6R1 and newer:                                          
   1) Close the System i Navigator application.                
   2) Open a Windows Command Prompt screen.                    
   3) Enter the following command:                              
      cwbinplg /REMOVE=IBM.BRMSPlugin                          
   4) On the client/PC, start the iSeries Navigator.            
   5) Use the System i Navigator "Install Options->Install      
      action. This action is available from the main System i  
      Navigator "File" menu and the "My Connections" folder    
      context/pop-up menu.  When prompted for the iSeries system
      to install from, select the iSeries that has the new BRMS
      PTF installed.                                            

Temporary Fix




PTFs Available

R710 SI43868 PTF Cover Letter   2115

Affected Modules


Affected Publications

Summary Information

Status............................................ CLOSED UR1
HIPER........................................... No
Component.................................. 5770BR100
Failing Module.......................... RCHMGR
Reported Release................... R710
Duplicate Of..............................

System i Support

IBM disclaims all warranties, whether express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. By furnishing this document, IBM grants no licenses to any related patents or copyrights. Copyright © 1996,1997,1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017 IBM Corporation. Any trademarks and product or brand names referenced in this document are the property of their respective owners. Consult the Terms of use link for trademark information

[{"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"},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG15Q","label":"APARs - OS\/400 General"},"Component":"","ARM Category":[],"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"V7R1M0;V9R9M9","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
18 May 2012