IBM Support

SI54787 - 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, when the Duplicate Media using BRM
(DUPMEDBRM) command fails with message MSGCPF6761, the volume is
not identified.
2. In 6.1 and later, the Save Object using BRM (SAVBRM) command
and integrated file system lists (*LNK) have been enhanced to
allow backslash character '\' to be specified as the delimiter
in a path name. To enable the enhancement, run the following
command:
CRTDTAARA DTAARA(QUSRBRM/Q1ACVTBSLS) TYPE(*CHAR)
3. In 7.1 and later, Enterprise reports that are set up to run
on a schedule may incorrectly run in a loop every 30 seconds.
The loop may incorrectly cause many spooled files to be created
and may cause the system job table limit to be exceeded.
4. In 6.1 and later, add support for new tape device D/T3592
model E08.
5. In 6.1 and later, when running the Save Objects using BRM
(SAVOBJBRM) command in parallel mode the save will always use
parallel-parallel save format instead of checking the user
specified parallel type.
6. In 6.1 and later, when *YES is specified for the Initialize
media (INZ) parameter on the Add Media to BRM (ADDMEDBRM)
command, the command may fail with message MSGBRM3D1D.
7. In 7.2 and later, when using the BRMS GUI client to display
many devices, it may hang.
8. N/A.
9. In 6.1 and later, when using the BRMS GUI client to reclaim
remote media, the reclaim may fail with message MSGMCH1202.
10. In 6.1 and later, when the Start Archive using BRM
(STRARCBRM) command is run using an archive control group with
*YES specified for Objects able to be freed and *NO specified
for Retain object description, messages MSGCPF0948 and
MSGCPF1005 may be incorrectly sent to the job log.
11. In 6.1 and later, the Restore Deferred Objects (RSTDFROBJ)
command inconsistently sends messages to either the job log or
the BRMS log (Display Log for BRM (DSPLOGBRM)). The messages
should only be sent to the BRMS log.
12. In 6.1 and later, when *YES is specified for the Mark
volumes for duplication field and *YES is specified for the Mark
history for duplication field in a media policy, once one
duplication has been performed both the volume and history
duplication are unmarked.
13. In 6.1 and later, when *YES is specified for the Mark
history for duplication field in a media policy and the media
policy is specified for the Media policy (MEDPCY) parameter on
the Save Save Files using BRM (SAVSAVFBRM) command, the history
that is created is not marked for duplication.
14. In 6.1 and later, the Duplicate Media using BRM (DUPMEDBRM)
command has been enhanced with additional diagnostic messages.
15. In 6.1 and later, when automatic duplication is run for
media that was created during an incremental back, the media
policy specified for the Media policy for Full backups field is
incorrectly used instead of the media policy specified for Media
policy for Incremental backups field.
16. In 6.1 and later, when a control group is run using the
Start Backup using BRM (STRBKUBRM) command and the control group
has *IMMED specified for the IPL after backup - How to end
field, the IPL may not be performed.
17. In 6.1 and later, when the QP1ABS report is created by
running the Print Report using BRM (PRTRPTBRM) command, the
dates in the report may be incorrect.
18. In 6.1 and later, when the Text (TEXT) parameter on the Set
Media Controls using BRM (SETMEDBRM) command is used to set the
text on media and the media is then duplicated with the
Duplicate Media using BRM (DUPMEDBRM) command, the text is not
duplicated to the target media.
19. N/A.
20. N/A.
21. In 7.2, when the Work with ASP Descriptions (WRKASPBRM)
command is run and option 2=Change is specified for an entry, it
fails with message MSGBRM2112.
22. In 6.1 and later, the Save Object using BRM (SAVBRM) command
may send a message to the job log without a message identifier.
The message will contain random data, for example '1 0 0'.
23. In 6.1 and later, the Initialize BRMS (INZBRM) command has
been enhanced to allow the following values on the Option
(OPTION) parameter to verify BRMS network communications:
6.1 - *VFYNET and *VFYSYS
7.1 and later - *VFYENT, *VFYNET, and *VFYSYS
24. In 6.1 and later, BRMS operations may fail with message
MSGMCH6903.
25. N/A.
26. In 6.1 and later, the Work with Media using BRM
(WRKMEDIBRM), Start Recovery using BRM (STRRCYBRM) and RSTxxxBRM
commands will support specifying a system for the From system
(FROMSYS) parameter that is doing a FlashCopy.
27. In 6.1 and later, when the Start Backup using BRM
(STRBKUBRM) command is run to backup a control group that has
*UNLOAD or *REWIND specified for the End of media option field,
other jobs may fail with message MSGBRM1039. For example, if the
control group has a media policy, that uses Automatic
duplication fields, specified for the Media policy field, the
automatic duplication job may fail with message MSGBRM1039.
28. In 6.1 and later, *IBM entries in backup control groups have
been enhanced to allow independent auxiliary storage pool (IASP)
values to be specified for the ASP Device field.
29. In 6.1 and later, the total volumes from the Work with Media
using BRM (WRKMEDBRM) command and the Check Expired Media for
BRM (CHKEXPBRM) command, may produce different results.
30. In 7.1 and later, the Move Media using BRM (MOVMEDBRM)
command may fail incorrectly with message MSGBRM6717.
31. In 7.2, the BRMS installation batch job or the Initialize
BRMS (INZBRM) command with *RUNPRDINZ specified for the Option
(OPTION) parameter may fail with messages MSGCPF3219 or
MSGCPF3162 and MSGBRM40A5.
32. N/A.
33. In 6.1 and later, some recoveries have been enhanced to
prompt the user to load required volumes when they are not
available instead of failing with a message indicating why the
volumes are not available, for example - MSGCPF412C, MSGCPF412D,
MSGCPF412F, MSGBRM1147, MSGBRM412F, etc.
34. In 6.1 and later, when the Add List Entry (Q1AADDLSTE) API
is used to add a link to a *LNK list, the list may contain
duplicate entries.
35. In 7.2, backups that have *INCR or *CUML specified for the
Type of save (SAVTYPE) parameter and *ALL specified for the
Spooled file data (SPLFDTA) parameter have been enhanced to save
new spooled files.
36. In 7.1 and later, if a scheduled Enterprise report fails
when it runs, it may not be rescheduled to be run on a future
date. Since the report is not rescheduled, it will be run in an
infinite loop until it is successful.
37. In 6.1 and later, the Force full backup days field in a
control group does not correctly force a full save when an
incremental save is run using the Start Backup using BRM
(STRBKUBRM) command.
38. In 6.1 and later, if a volume is removed from the BRMS
inventory using the Remove Media Volumes from BRM (RMVMEDBRM)
command or by specifying option 4=Remove on the Work with Media
using BRM (WRKMEDBRM) command, subsequent move operations using
the Move Media using BRM (MOVMEDBRM) may not work as expected.
39. In 6.1 and later, if an IBM i is being hosted by another IBM
i and a tape media library device is being used, backups may
fail with message MSGBRM1392. To enable the fix for this
problem, run the following commands:
QSYS/CRTDTAARA DTAARA(QUSRBRM/Q1AIHOSTI) TYPE(*CHAR)
QSYS/CHGOBJOWN OBJ(QUSRBRM/Q1AIHOSTI) OBJTYPE(*DTAARA)
NEWOWN(QBRMS)
40. In 6.1 and later, when the QSYS/CALL QBRM/Q1AOLD
PARM('DEVUSESTS ' 'xxxxxx') command is run to determine device
utilization in a BRMS network, the Run Query (RUNQRY) command is
used to generate a report. The use of RUNQRY can be overridden
to use CPYF by running the following commands:
QSYS/CRTDTAARA DTAARA(QUSRBRM/Q1ANRUNQRY) TYPE(*CHAR)
QSYS/CHGOBJOWN OBJ(QUSRBRM/Q1ANRUNQRY) OBJTYPE(*DTAARA)
NEWOWN(QBRMS)
41. In 6.1 and later, when the Restore Library using BRM
(RSTLIBBRM) command is run with a remote system specified for
From system (FROMSYS) parameter, the remote system has *LIB
specified for the BRMS Media Information Local Receives field
and the remote system is down, the restore will fail with
message MSGBRM1177.
42. In 6.1 and later, the Change Media using BRM (CHGMEDBRM)
command and option 2=Change on the Work with Media using BRM
(WRKMEDBRM) command have been enhanced to allow dates after the
year 2038 to be specified for the Expiration data (EXPDATE)
parameter.
43. In 6.1 and later, when the Work with Spooled Files using BRM
(WRKSPLF) command is used to restore multiple spooled files from
media that was created with a parallel save, not all of the
spooled files will be restored.
44. In 6.1 and later, when *RCY is specified for the Policy type
(TYPE) parameter on the Work with Policies using BRM (WRKPCYBRM)
command and PF4=Prompt is used for a field other than the
Recovery device, the device list is incorrectly displayed.
45. In 6.1 and later, if the BRMS network feature is not
installed, the Print Report using BRM (PRTRPTBRM) command
incorrectly fails with message MSGBRM1917 when the local system
is specified for the From system (FROMSYS) parameter.
46. In 6.1 and above, if the Start Maintenance for BRM
(STRMNTBRM) command is run with *YES specified for the Expire
media set volumes (EXPSETMED) parameter, media sets may be
expired incorrectly.
47. In 6.1 and later, if saved history for QFILE is on media
with other saves that use versioning for expiration, the QFILE
saved history may not get expired correctly.
48. In 6.1 and later, the Move Media using BRM (MOVMEDBRM) and
Verify Moves using BRM (VFYMOVBRM) commands have been enhanced
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.
49. In 7.1 and later, IFS restores from parallel save media may
fail with message MSGCPD3825.

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