IBM Support

SI56278 - BRM-MAINT-INCORROUT Fixes

PTF Cover Letter


PTF ( Program Temporary Fixes ) Cover letter


Order this fix

Abstract

BRM-MAINT-INCORROUT Fixes


Pre/Co-Requisite PTF / Fix List

REQ  LICENSED           PTF/FIX  LEVEL

TYPE PROGRAM  RELEASE   NUMBER   MIN/MAX  OPTION
---- -------- --------- -------  -------  ------
NONE



NOTICE:
-------
Application of this PTF may disable or render ineffective programs that
use system memory addresses not generated by the IBM translator,
including programs that circumvent control technology designed to limit
interactive capacity to purchased levels.  This PTF may be a prerequisite
for future PTFs.  By applying this PTF you authorize and agree to the
foregoing.

This PTF is subject to the terms of the license agreement which
accompanied, or was contained in, the Program for which you are obtaining
the PTF.  You are not authorized to install or use the PTF except as part
of a Program for which you have a valid Proof of Entitlement.

SUBJECT TO ANY WARRANTIES WHICH CAN NOT BE EXCLUDED OR EXCEPT AS EXPLICITLY
AGREED TO IN THE APPLICABLE LICENSE AGREEMENT OR AN APPLICABLE SUPPORT
AGREEMENT, IBM MAKES NO WARRANTIES OR CONDITIONS EITHER EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OR CONDITIONS OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON INFRINGEMENT,
REGARDING THE PTF.

The applicable license agreement may have been provided to you in printed
form and/or may be viewed using the Work with Software Agreements (WRKSFWAGR)
CL command.


APAR Error Description / Circumvention

-------------------------------------------------
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 6.1 and later, the BRMS GUI client does not show more than
630 entries in a control group.
2. In 6.1 and later, if two or more volumes are reclaimed using
the BRMS GUI client, the job may fail with message MSGMCH3601.
3. In 6.1 and later, the BRMS GUI client fails with
java.lang.NullPointerException when creating a report containing
all backup control groups.
4. In 6.1 and later, the Display Log for BRM (DSPLOGBRM) command
may display the incorrect message severity for the Sev field.
5. In 6.1 and later, a save may incorrectly overwrite save data
that was restored in the same job prior to the save.
6. In 6.1 and later, if the Change Media using BRM (CHGMEDBRM)
command is run to take ownership of a volume after receiving
message MSGBRM1518,  the wrong volume may be used in subsequent
BRMS operations in the same job.
7. In 7.2 and later, the BRMS GUI client fails with error
CWLAA6003 when the Messages table is closed.
8. In 6.1 and later, the Initialize BRMS (INZBRM) command with
*VFYSYS specified for the OPTION() parameter does not indicate
there is a communications failure when connecting to a system if
the system does not have an existing relational database
directory entry.
9. In 6.1 and later, the Check Expired Media for BRM (CHKEXPBRM)
command has been enhanced to add additional messages to the BRMS
log, for example MSGBRM1930 and MSGBRM1933.
10. In 7.2 and later,  when the Start Archive using BRM
(STRARCBRM) command is run with *REPORT specified for the Option
(OPTION) parameter for *LNK and *SPL lists, message MSGBRM1943
is not sent to the job log to indicate reports have been
generated.
11. In 6.1 and later, when the Allow alternate input media field
is set to *YES in the system policy, BRMS does not try alternate
saved items during serial restore if the device cannot be
resolved when *MEDCLS is specified for the restore device.
12. In 6.1 and later, if an incorrect password that is longer
than the correct password is entered when signing on to the
console monitor using BRMS, a message is displayed indicating
the password is not correct.  If the correct password is then
entered without clearing the characters after the password, the
signon will still fail with password not correct.
13. In 6.1 and later, when a message is being sent to the BRMS
log and has been identified by the BRMS GUI client to have an
email sent, BRMS may incorrectly send multiple emails.
14. 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 in Step "Update System Name in
BRMS Media Information" if the saved system has been setup with
a BRMS system name.
15. N/A.
16. In 6.1 and later, when the End of media option field is set
to *LEAVE during a save, the save data may incorrectly be
appended to volumes not intended for use by the save even if
Append to media is set to *NO or the sequence number is set to
1.
17. In 6.1 and 7.1, recovery reports (QP1ARCY) created using the
Start Recovery using BRM (STRRCYBRM) or Start Maintenance for
BRM (STRMNTBRM) command have been enhanced to list libraries
from independent auxiliary storage pools (IASP) that have not
been saved using BRMS.
18. In 6.1 and later, parallel restores have been enhanced to
try more than five alternate media sets when the Allow alternate
input media field is set to *YES in system policy.
19. In 6.1 and later, the Move Media using BRM (MOVMEDBRM)
command will cause other BRMS jobs to hang if an unanswered
inquiry message is issued for a volume that is ejected during
the move processing.  BRMS has been enhanced to allow the
inquiry message to be skipped to avoid hanging other BRMS jobs.

To enable this behavior for the all jobs on the system, run the
following command:
CRTDTAARA DTAARA(QUSRBRM/Q1ANMOVINQ) TYPE(*CHAR)
To enable this behavior for the current job, run the following
command:
CRTDTAARA DTAARA(QTEMP/Q1ANMOVINQ) TYPE(*CHAR)
20. In 61 and later, when the Save active wait time field in a
control group is set to *NOCMTBDY, it may not be used for
entries in the control group.
21. In 6.1 and later, when using the Work with Media Information
(WRKMEDIBRM) command with *VOL specified for the Sequence option
(SORT) parameter and a volume specified for the Volume (VOL)
parameter that is owned by a remote system that is down,
incorrect media information may be displayed.
22. In 6.1 and later, the BRMS GUI client does not allow the '~'
character to be used to update path name fields and does not
display the '~' character correctly when displaying a path name
field.
23. In 7.2 and later, when the Start Backup using BRM
(STRBKUBRM) command is used to run a control group with *SIZE
specified for the Sort field, the backup may fail with message
MSGCPF9898 indicating q1aSequence::elementAtPosition: Bad
Positon.
24. In 6.1 and later, when the Save Library using BRM
(SAVLIBBRM) command fails with message MSGCPF3738, the device
listed may be incorrect.
25. In 6.1 and later, when using the Work with Media using BRM
(WRKMEDBRM) command, after running BRMS maintenance, the
cartridge type may be blank for some volumes.
26. In 6.1 and later,  Save Library using BRM (SAVLIBBRM) using
multiple drives, with *UNLOAD or *REWIND specified for the End
option (ENDOPT), may not process the end option incorrectly.
27. In 6.1 and later, restoring libraries or objects from
multiple libraries using Restore Library using BRM (RSTLIBBRM)
or Restore Object using BRM (RSTOBJBRM),  may not restore all
selected data.
28. In 6.1 and later, when applying a BRMS PTF, it may
incorrectly fail with message MSGCPF9898 when checking for
FlashCopy mode.
29. In 6.1 and later, when doing restores from parallel media,
tape device descriptions that do not have *MLB, *OPTMLB,
*TAPMLB, *OPT or *TAP for type, will cause message MSGBRM2208 to
be sent to the job log and the device will not be used.
30. In 6.1 and later, the Start Maintenance for BRM (STRMNTBRM)
command with *YES specified for the Reorganize BRMS database
(RGZBRMDB) parameter has been changed to send message MSGBRM4128
reason code 0099 when problems are encountered during database
reorganization.
31. In 6.1 and later, if a save of library QUSRBRM or objects in
library QUSRBRM spans multiple volumes and then the media from
the save is duplicated using the Duplicate Media using BRM
(DUPMEDBRM) command, it may incorrectly fail with message
MSGCPF6734.
32. In 6.1 and later, using the Change Media using BRM
(CHGMEDBRM) command or the Work With Media (WRKMEDBRM) command
with option 2 to change a volume may incorrectly fail with
message MSGCPD0013.
33. In 6.1 and later, when the Expiration date (EXPDATE)
parameter is specified on the Duplicate Media using BRM
(DUPMEDBRM) command, the DUPMEDBRM may fail with message
MSGBRM0004 return code RC14.
34. In 6.1 and later, when multiple jobs doing backups to IBM i
internal virtual tape and use the same media class, some of the
backups may fail with message MSGCPF41B0.
In 6.1, to reserve media in backup jobs and avoid message
MSGCPF41B0, run the following command:
CRTDTAARA DTAARA(QUSRBRM/Q1ARESMED) TYPE(*CHAR)
In 7.1 and later, data area QUSRBRM/Q1ARESMED is not required.
35. In 7.1 and later, if a value is not specified for the Save
active (SAVACT) parameter when saving library QUSRBRM, the save
may fail with message MSGCPF3761.
36. In 6.1 and later, if a save uses a media policy that has a
value other than *ALL or *ANY for specified for the Storage
location field and the save fails with message BRM415A, the
message may contain an incorrect location.
37. In 6.1 and later, if *REUSE is specified for the Media
contents value of the Remove media information (RMVMEDI)
parameter on the Start Maintenance for BRM (STRMNTBRM) command
or *REUSE is specified for the Media contents (MEDCON) parameter
on the  Remove Media Info from BRM (RMVMEDIBRM) command, the
command may incorrectly fail with message MSGCPF0818.
38. In 6.1 and later, BRMS has been enhanced to allow commands
with parameters that contain the '$', '#' or '@' character in
control group *EXIT entries for jobs that are not using CCSID
37.
To enable the enhancement, run the following command:
CRTDTAARA DTAARA(QUSRBRM/Q1AINVART) TYPE(*CHAR)
39. N/A.
40. In 7.1 and later, when an Enterprise report definition is
created using the BRMS GUI client, it fails with "Object does
not exist".
41. In 7.1 and later, BRMS has been enhanced to support new
Navigator for i interfaces. If the BRMS plugin is missing, load
this BRMS PTF.
42. In 6.1 and later, when the Save media information
(SAVMEDIBRM) parameter on the Duplicate Media using BRM
(DUPMEDBRM) command indicates to save media information, the
media information may be saved with an incorrect expiration
date.
43. In 6.1 and later, when a restore is performed from a save
that used a Tivoli Storage Manager (TSM) server with *MEDCLS
specified for the Device and a value other than *ANY specified
for the Storage location, the restore may incorrectly fail with
message MSGBRM1883.

CORRECTION FOR APAR 'SE61505' :
-------------------------------
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.

CIRCUMVENTION FOR APAR 'SE61505' :
----------------------------------
None.


Activation Instructions


None.




Special Instructions


********************************************************************
THE FOLLOWING ARE SUPERSEDED SPECIAL INSTRUCTIONS. IF THE SUPERSEDED
PTF HAS ALREADY BEEN APPLIED AND ITS SPECIAL INSTRUCTION FOLLOWED,
IT IS NOT NECESSARY TO FOLLOW THAT SPECIAL INSTRUCTION AGAIN.
********************************************************************

SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI51641:
================================================

All BRMS activity must be stopped while this ptf is being applied and
users must signoff and on again before using BRMS after the ptf is
applied.


Default Instructions

THIS PTF CAN BE APPLIED IMMEDIATE OR DELAYED.



Supersedes

PTF/FIX NO(S).  APAR TITLE LINE
--------------  ------------------------------------------------------------
   SI55731      BRM-MAINT-INCORROUT  Fixes
   SI54787      BRM-MAINT-INCORROUT  Fixes
   SI53306      BRM-MAINT-INCORROUT  Fixes
   SI52668      BRM-MAINT-INCORROUT  Fixes
   SI51641      BRM-MAINT-INCORROUT  Fixes
   SI50936      BRM-MAINT-INCORROUT  Fixes

Summary Information

System..............................  i
Models..............................  
Release.............................  V7R2M0
Licensed Program....................  5770BR1
APAR Fixed..........................  View details for APAR SE61505
Superseded by:......................  View fix details for PTF SI79121
Recompile...........................  N
Library.............................  QBRM
MRI Feature ........................  NONE
Cum Level...........................  C5310720


IBM 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, 2018, 2019, 2020, 2021, 2022 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.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"7.2.0","Product":{"code":"SWG60","label":"IBM i"},"Component":"5770BR1","Edition":"","Line of Business":{"code":"LOB57","label":"Power"}}]

Document Information

Modified date:
13 May 2022