IBM Support

SE60901 - BRM-MAINT-INCORROUT Fixes

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)

Abstract

BRM-MAINT-INCORROUT Fixes

Error Description

See Customer Problem Description.                              

Problem Summary

It is important to keep all systems in a BRMS network at the    
same level of BRMS PTFs.                                        
Fixes included in this PTF may reference enhancements. More    
information on these enhancements can be found on the BRMS web  
page:                                                          
www.ibm.com/developerworks/ibmi/brms                            
Additionally also review the media web page:                    
www.ibm.com/developerworks/ibmi/media                          
                                                               
Fixes in this PTF:                                              
1. In 7.2, when using the Start Backup using BRM (STRBKUBRM)    
command to backup a control group that has *LIB or *OBJ        
specified for the Automatically backup media information field  
and *SIZE specified for the Sort by field, STRBKUBRM may fail  
with message MSGCPF3C81.                                        
2. In 6.1 and later, when the Work with Policies using BRM      
(WRKPCYBRM) command is run with *SYS specified for the Policy  
type (TYPE) parameter and option 1 is selected to Display or    
Change system policy, the Page Down key may incorrectly attempt
to connect to another system.                                  
3. In 6.1 and later, the BRMS GUI client may fail              
NullPointerException when displaying BRMS devices.              
4. In 6.1 and later, BRMS backups have been enhanced to add    
message MSGCPF3741 to the BRMS log when an object is not saved.
5. In 6.1 and later, if a backup is run with more than 300      
object omits, it will fail with message MSGMCH1210.            
6. In 6.1 and later, if the Initialize Tape (INZTAP) command or
Work with Media using BRM (WRKMEDBRM) command with option 10 is
used to initialize a volume that is enrolled in BRMS and the    
volume is not available, BRMS may incorrectly attempt to        
initialize an alternate volume.                                
7. In 7.2, the Start Recovery using BRM (STRRCYBRM) command may
incorrectly fail with message MSGCPF5004.                      
8. In 6.1 and later, BRMS operations may fail with message      
MSGSQL0206 if previous BRMS fixes (PTF) were applied on a system
that was in FlashCopy mode.                                    
9. In 6.1 and later, the Display Log for BRM (DSPLOGBRM) command
may display the incorrect message severity for the Sev field.  
10. In 6.1 and later, the Add Control Group Entry (Q1AADDCGE)  
API has been enhanced to allow independent auxiliary storage    
pools (IASP) to be specified for the ASP Device field on *IBM  
control group entries.                                          
11. In 7.2, when a backup list or archive list is updated using
the BRMS GUI client, it may fail with an error that indicates  
the operation is incompatible with                              
com.ibm.as400.brmsgui.BrmObjectBackupObjectListItem.            
12. In 7.2, the Start Recovery using BRM (STRRCYBRM) command has
been enhanced with additional independent auxiliary storage pool
(IASP) support.                                                
13. In 6.1 and later, the BRMS GUI client has been enhanced to  
allow multiple items from backup lists and archive lists to be  
selected so they can be moved.                                  
14. In 6.1 and later, user libraries that start with # should be
encrypted, but they are not encrypted.  Note: This change does  
not include System/36 libraries: #CGULIB, #DSULIB, #SEULIB,    
#COBLIB, #RPGLIB, #DFULIB and #SDALIB.  These user defined      
libraries will not be encrypted.                                
15. In 6.1 and later, when running backups that use parallel    
media, the save job log may incorrectly contain message        
MSGBRM1483 and the save will incorrectly use additional scratch
volumes.                                                        
16. In 7.2, when running a backup using the Start Backup using  
BRM (STRBKUBRM) command, the STRBKUBRM may finish successfully  
but the job log may incorrectly contain message MSGMCH3601.    
17. In 6.1 and later, when running the Work with Polices using  
BRM (WRKPCYBRM) command with *ARC specified for the Type (TYPE)
parameter and the page down key is pressed, it may fail with    
message MSGMCH3601.                                            
18. In 6.1 and later, the Change Media using BRM (CHGMEDBRM)    
command has been enhanced to support Location (LOC) and        
Container (CNR) parameters that can be used to move a single    
volume to a different location.                                
19. In 6.1 and later, when *MEDCLS is specified for the device  
on a restore, the restore may incorrectly fail with message    
MSGBRM1883.                                                    
20. In 6.1 and later, the recovery report (QP1ARCY), created by
running command Start Recovery using BRM (STRRCYBRM) command    
with *REPORT specified for the Action (ACTION) parameter, may  
contain an incorrect value for the Object Not saved field if the
save was done using parallel media.                            
21. In 6.1 and later, the recovery report (QP1ARCY), created by
running command Start Recovery using BRM (STRRCYBRM) command    
with *REPORT specified for the Action (ACTION) parameter, may  
contain incorrect information for the Recover BRMS Related Media
Information recovery step.                                      
22. In 6.1 and later, BRMS operations may fail with message    
MSGMCH0601 or message MSGMCH3601.                              
23. N/A.                                                        
24. N/A.                                                        
25. In 6.1 and later, for improved backup performance, BRMS has
been enhanced to use other available volumes before retrying    
media that was rejected during a previous save in the same job.
26. In 6.1 and later, after successfully activating a system in
the BRMS network and then selecting option 4. Change network    
group is selected for the Work Policy using BRM (WRKPCYBRM)    
command with *SYS specified for the Policy type (TYPE)          
parameter, Offline is incorrectly displayed for the System      
Status field.                                                  
27. In 6.1 and later, BRMS has been enhanced with additional    
error recovery processing when a remote system loses connection.
28. In 6.1 and later, BRMS has been enhanced by changing the    
default notification period from 30 seconds to one hour to      
reduce the number of messages that are sent when BRMS cannot    
connect to a system in the BRMS network.  The Notify period    
field can be changed when option 4. Change network group is    
selected for the Work Policy using BRM (WRKPCYBRM) command with
*SYS specified for the Policy type (TYPE) parameter.            
29. In 6.1 and later, temporary user space objects are created  
and used during BRMS operations.  The temporary user spaces are
incorrectly moved to library QRPLOBJ if BRMS recreates the user
spaces during subsequent BRMS operations.                      
30. In 6.1 and later, when BRMS object lists are backed up using
the Save Object List using BRM (SAVOBJLBRM) or Start Backup    
using BRM (STRBKUBRM) commands, the save may fail with message  
MSGMCH0603.                                                    
31. In 6.1 and later, BRMS restores have been enhanced to prompt
the user to load required volumes when they are not available  
instead of failing with a message indicating the volumes are not
available, for example - MSGCPF412C, MSGCPF412D, MSGCPF412F,    
MSGBRM1147, MSGBRM412F, etc.                                    
32. In 6.1 and later, BRMS has been enhanced to send message    
MSGCPI3822 to the BRMS log whenever it is sent to the job log  
during BRMS operations.                                        
33. N/A.                                                        
34. In 6.1 and later, when the system is being powered down or  
the job is ended immediately, a volume that is being used by    
BRMS may no longer be available for use.  If no other media is  
available this would incorrectly cause message MSGBRM148A to be
sent for operations that try to use the media class that        
contains the volume.                                            
35. In 6.1 and later, if the BRMS GUI client fails because an  
object is locked, message MSGCPF9803 may contain the wrong file
name in the message data.                                      
36. In 6.1 and later, the Start Media Balancing for BRM        
(STRBALBRM) command has been enhanced to take ownership of a    
volume before updating it.                                      
37. In 6.1 and later, the Duplicate Media using BRM (DUPMEDBRM)
command does not allow duplication of media that is owned by    
another system in the BRMS network and is in a media class with
the Shared media field set to *NO.                              
38. In 6.1 and later, native restores from BRMS save files may  
fail with authorization error message MSGCPF9820 or MSGCPF9822.
39. In 6.1 and later, the Check Expired Media for BRM          
(CHKEXPBRM) command incorrectly includes media that is owned by
other systems in the BRMS network and is in media classes with  
the Shared media field set to *NO.                              
40. In 6.1 and later, the Move Media using BRM (MOVMEDBRM) and  
Verify Moves using BRM (VFYMOVBRM) commands have been changed to
run the Remove Tape Cartridge (RMVTAPCTG) command for volumes  
that are in media libraries when the media libraries are not    
configured on the local system but are configured on other      
systems in the BRMS network.  To enable this function, data area
QUSRBRM/Q1ARMTEJT must exist.  Run the following command to    
create the data area:                                          
CRTDTAARA DTAARA(QUSRBRM/Q1ARMTEJT) TYPE(*CHAR)                
41. In 6.1 and later, the Move Media using BRM (MOVMEDBRM) and  
Verify Moves using BRM (VFYMOVBRM) commands may end before all  
volumes have been moved if there is an error ejecting a volume  
that is being moved out of a tape media library on another      
system in the BRMS network.                                    
42. In 6.1 and later, BRMS may use the incorrect profile to run
tape media library operations on other systems in the BRMS      
network and fail with message MSGCPF9190.                      

Problem Conclusion

Load and apply this PTF.                                        
After the BRMS PTF is installed, do the following to enable the
                                                               
                                                               
  BRMS                                                          
  plug-in for the IBM Systems Director Navigator for i5/OS (web
                                                               
  brower)                                                      
  or System i Navigator windows client.                        
                                                               
  Enable the BRMS plug-in for the IBM Systems Director Navigator
                                                               
  for i5/OS.                                                    
  ==== V6R1 and newer only:                                    
  Note:  ending the http admin servers may affect other non-BRMS
                                                               
  users.                                                        
  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  
  them.                                                        
      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    
  client.                                                      
  ==== Pre-V6R1:                                                
  1) Close the System i Navigator application.                  
  2) On the client/PC, uninstall the BRMS plug-in using the    
Client                                                          
                                                               
      Access Express "Selective Setup" utility:  from the      
Windows                                                        
      "Start", select                                          
      "Programs->IBM iSeries Access for Windows->Selective      
Setup".                                                        
                                                               
      Follow the instructions on the dialogs to uninstall the  
BRMS                                                            
                                                               
      plug-in.  Notes:                                          
      a) On the second dialog, select the radio button "Ignore.
I'm                                                            
        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 displayed.
                                                               
      c) Deselect the BRMS plug-in to uninstall it (if you do  
not                                                            
        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      
Plug-in"                                                        
      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      
Plug-in"                                                        
      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

Comments

Circumvention


PTFs Available

R710 SI55621 PTF Cover Letter   5142
R720 SI55731 PTF Cover Letter   5135

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.2.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;V7R2M0;V9R9M9","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
30 May 2015