IBM Support

SI53306 - 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 7.1 and later, the system job tables may fill up due to
BRMS Enterprise. When the system job tables fill up, no new jobs
can be started on the system.
2. In 7.2, recovery reports (QP1ARCY) created using the Start
Recovery using BRM (STRRCYBRM) or Start Maintenance for BRM
(STRMNTBRM) command have been enhanced to   use the Configure
Device ASP (CFGDEVASP) command to configure independent
auxiliary storage pools (IASP). The step to IPL the system to
configure IASPs has been removed from recovery reports.
3. N/A
4. In V6R1 and later, pressing F4 to prompt on the System
(SYSNAME) parameter for the Add Media to BRM (ADDMEDBRM) command
does not show the systems in the BRMS network.
5. In V6R1 and 7.1, when using the Duplicate Media using BRM
(DUPMEDBRM) command to duplicate multiple volumes at the same
time after calling the DUPBATCH *SET function (CALL
PGM(QBRM/Q1AOLD) PARM('DUPBATCH' '*SET' 'aa')), the job may fail
with message MSGCPD0063.
In 7.2 and above, when using the Duplicate Media using BRM
(DUPMEDBRM) command to duplicate multiple volumes at the same
time by specifying the Submit batch options (SBMOPT) parameter,
the job may fail with message MSGCPD0063.
6. In V6R1 and later, when running the Start Maintenance for BRM
(STRMNTBRM) command, saved items and the associated save files
may be incorrectly deleted.
7. In V6R1 and later, the List Control Group Entries (Q1ALSTCGE)
API may fail with message MSGMCH0601.
8. In V6R1 and later, messages MSGBRM1472 and MSGBRM1516 may not
correctly display available volumes.
9. In V6R1 and later, the Work with Media Library Media
(WRKMLMBRM) command may fail with message MSGMCH1210.
10. In V6R1 and later, when using option 7 to restore an object
with a remote system specified for the From system (FROMSYS)
parameter on the Work with Media Information (WRKMEDIBRM)
command, the restore may fail with message MSGBRM4126.
11. In V6R1 and later, when saving the system to optical media
using a *SAVSYS control group entry or the Save System using BRM
(SAVSYSBRM) command, the optical media may not be included in
the recovery report.
12. In 7.1 and later, when saving to a memory stick or *RDX
drive configured as an optical device, the save will fail with
message MSGCPF9898.
13. In V6R1 and later, when a save is running that includes
objects in QUSRSYS, other BRMS jobs may fail with message
MSGCPF3CD9.
14. In V6R1 and later, when running the Work with Media using
BRM (WRKMEDBRM) command with option 2 or the Change Media using
BRM (CHGMEDBRM) command to change the owner of an expired
volume, saved items may not be cleaned up correctly for the
original system.
15. In V6R1 and later, the Start Maintenance for BRM (STRMNTBRM)
command may incorrectly delete the output files for other jobs
that are saving integrated file system (IFS) objects.
16. In V6R1 and later, when saving to optical, RDX or USB
devices using the Save System using BRM (SAVSYSBRM) command, the
save may fail with message MSGCPF388C.
17. In V6R1 and later, the Display Log for BRM (DSPLOGBRM) may
display incorrect values for the message Program and Area
fields.
18. In V6R1 and later, the Print Report using BRM (PRTRPTBRM)
command has been enhanced to support multiple values on the From
system (FROMSYS) parameter. The PRTRPTBRM command has also been
enhanced to support the Use save files (USESAVF) and TSM
(USEADSM) parameters.
19. In V6R1 and later, the Work with Media Information
(WRKMEDIBRM) command may display incorrect values in the Objects
Saved and Objects Not Saved fields for spooled file Saved Items
that were saved in parallel-parallel format.
20. In V6R1 and later, when a save spans the time specified in
the Day start time field for the system policy, the save may
fail with message MSGBRM0004 which contains reason code 13.
21. In V6R1 and later, when running the Duplicate Media using
BRM (DUPMEDBRM) command with *FROMVOL specified for the
Expiration date (EXPDATE) parameter, the duplication may fail
with message MSGBRM0004 which contains reason code 14.
22. In V6R1 and later, the Initialize Media using BRM
(INZMEDBRM) command may fail with message MSGCPF67A0.
23. N/A
24. In V6R1 and later, when a system is removed from a BRMS
network with *RENAME specified for the Remove media field on the
Confirm Remove of Network Systems screen, the saved spool file
information is not updated correctly.
25. In V6R1 and later, when running the Duplicate Media using
BRM (DUPMEDBRM) command that correctly duplicates all expected
saved items, the duplication may incorrectly fail with message
MSGBRM4137.
26. In 7.2 and later, BRMS has been enhanced to remove limits on
the number of BRMS object types (media policies, media classes,
etc) that can be created/used and BRMS commands have been
enhanced to display a larger list of choices when a command is
prompted and F4 is pressed for a parameter.
27. In V6R1 and later, BRMS job QBRMSYNC in subsystem Q1ABRMNET
may fail with message MSGCPE3401 and MSGCPD3E34.
28. In 7.1 and later, output queues that are created when
Enterprise reports are run may not be correctly cleaned up.
Reports may fail with message MSGCPF3353 to indicate output
queue QUSRBRM/QZHUBT999 already exists.
29. In V6R1 and later, the performance of Restore Object using
BRM (RSTBRM) command has been improved when *LIST is specified
for the Objects (OBJ) parameter and *DAOS is specified for the
List (LIST) parameter.
30. In V6R1 and later, when the recovery policy uses the Apply
journaled changes fields to indicate to run the Apply Journal
Changes (APYJRNCHG) command after a restore completes, the
recoveries have been enhanced to include additional information
when errors occur during apply journal changes.
31. In V6R1 and later, Media Balancing Report (QP1AMBL) reports
generated by the Start Media Balancing for BRM (STRBALBRM)
command may show incorrect values for the Number of media
available field.
32.In V6R1 and later, save of Domino Attachment and Object
Service (DAOS) objects has been enhanced to improve performance
when restoring individual DAOS objects. See the BRMS Wiki for
DAOS save configuration information.
33. In V6R1 and later, when a native save is attempted after
running the Set Media Controls using BRM (SETMEDBRM) command,
the save may fail with message MSGBRM148A.
34. In V6R1 and later, when the Restore Library using BRM
(RSTLIBBRM) command is run with *SAVDATE specified for the Save
level (SAVLVL) parameter, message MSGBRM1677 incorrectly
indicates save level 1 is being restored.
35. In 7.1 and later, if data area Q1ANSTRPSN in QTEMP is
created, BRMS disables fast positioning for spooled file
restore.
36. In 7.2, BRMS object lists have been enhanced to provide omit
capability and allow *ALLUSR as a valid value for the library
name field. The enhancement provides individual library save
timestamps instead of the same timestamp for the *ALLUSR
libraries.
37. In 7.2, save operations using Sort by (SORT) with *SIZE have
been enhanced to improve performance.
38. In V6R1 and later, when BRMS operations use media End option
*LEAVE, subsequent operations may not append to the correct
media or may fail with message MSGCPF412F.
Note: In release V6R1, data area QUSRBRM/Q1ARESMED must also
be created. In releases 7.1 and later, the data area is not
required.
39. In V6R1 and later, when expiring a volume set containing
volume without associated history information, the history
information is not updated correctly for the beginning volume.
40. In V6R1 and above, when *UNLOAD is specified for the From
end option (FROMENDOPT) parameter on the Duplicate Media using
BRM (DUPMEDBRM) command, some volumes may not be unloaded.
41. In V6R1 and later, using the Work with Media using BRM
(WRKMEDBRM) or Change Media using BRM (CHGMEDBRM) command to
change the owner of volume may cause different systems to write
to the same volume. This can occur when systems in the BRMS
network are in restricted state.
42. In 7.2 and later, control group entries *ALLCHGRCV and
*ALLDTCRCV have been enhanced to exclude entries with *EXC
specified for the Inc/Exc field when object lists QCHGJRNRCV and
QDTCJRNRCV are used to specify journals.
43. In V6R1 and later, control group entries *ALLCHGRCV and
*ALLDTCRCV have been enhanced to process journals in libraries
that start with 'Q' when they are specified in object lists
QCHGJRNRCV and QDTCJRNRCV.

CORRECTION FOR APAR SE59093 :
-----------------------------
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 SE59093 :
--------------------------------
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
--------------  ------------------------------------------------------------
   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 SE59093
Superseded by:......................  View fix details for PTF SI79121
Recompile...........................  N
Library.............................  QBRM
MRI Feature ........................  NONE
Cum Level...........................  C5135720


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