PTF Cover Letter
PTF ( Program Temporary Fixes ) Cover letter
BRM-MAINT-INCORROUT Fixes
Pre/Co-Requisite PTF / Fix List
REQ LICENSED PTF/FIX LEVEL
TYPE PROGRAM REL 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
-------------------------------------------------
1. In V5R4 and above, when running EXTMEDIBRM and a BRMS backup
at the same time, MSGCPF415E may be posted.
2. In V5R4 and above, when marking or unmarking a saved item for
duplication, (options 18 and 19 in WRKMEDIBRM), the spanning
volumes are not marked or unmarked.
3. In V5R4 and above, WRKSPLFBRM will take a long time when a
lot of spool files have been saved.
4. In V5R4 and above, there may be a MSGMCH3601 when saving IFS
objects.
5. In V6R1 and above, when changing the expiration date on an
active volume using CHGMEDBRM, a MSGCPD0013 might be posted.
6. In V5R4 and above, when using WRKSPLFBRM to restore spool
files, the files to be restored may not be the ones selected by
the user and the restore may fail.
7. In V5R4 and above, when removing a system from the BRMS
network and selecting a 4 on all the systems on one system, will
cause the system to be removed from one other system in the BRMS
network. This is incorrect and should be removed manually on one
of the other systems in the BRMS network
8. In V6R1 and above, if appending using versioning and an
append candidate is not already loaded in the tape drive, BRMS
will use a scratch volume and not a valid append candidate.
SAVSAVFBRM might get a MSGBRM148A.
9. In V6R1 and above, the Q1ASYNTAP job queue can be overrun
with jobs.
10. In V6R1 and above, when specifying PERIOD((*AVAIL *CURRENT)
(*AVAIL *END)) on the PRTRPTBRM command, nothing is printed in
the report.
11. In V5R4 and above, you can now change the BRMS flight
recorder size via a call interface:
QUSRBRM/Q1AMAXFR
This data area is now supported via a call interface:
To change the flight recorder size (in megabytes) to 001-999
issue this command:
CALL PGM(QBRM/Q1AOLD) PARM('FRSIZE ' '*SET' 'XXX' )
- Where XXX is equal to 001 - 999 Note: 0s must be added to
the front of the numbers
To show the current flight recorder size issue this command:
CALL PGM(QBRM/Q1AOLD) PARM('FRSIZE ' '*DISPLAY' )
Note:
The flight recorder size will be available in releases IBM i
7.1 and earlier using this interface. This function will be put
into the system policy in a future release.
12 In V5R4 and above, volumes might not be selected for backups
and messages MSGBRM148A and MSGBRM0004 might be seen.
13. In V6R1 and above, override support for the new ASYNCBRING
key on the QsrSave API to help improve IFS save performance is
now possible using one of the following commands:
To enable the new ASYNCBRING key:
CALL PGM(QBRM/Q1AOLD) PARM('PARMOVR' '*ADD' 'ASYNCBRING' '*YES')
To disable the new ASYNCBRING key:
CALL PGM(QBRM/Q1AOLD) PARM('PARMOVR' '*ADD' 'ASYNCBRING' '*NO ')
To remove the override, use the following command (default is
*NO):
CALL PGM(QBRM/Q1AOLD) PARM('PARMOVR' '*REMOVE ' 'ASYNCBRING')
To show the current override being used, use the following
command:
CALL PGM(QBRM/Q1AOLD) PARM('PARMOVR' '*DISPLAY' 'ASYNCBRING')
Note: In releases following IBM i 7.1, interfaces will be
provided on BRMS commands, but this override will be honored.
The following PTFs or their superseding PTFs are required:
BRMS:
7.1 SI44710
V6R1M0 SI44709
IBM i OS:
For release 6.1.0 (with 6.1.0 SLIC)
MF53846
SI44587
SI44589
SI44739
For release 6.1.0 (with 6.1.1 SLIC)
MF53847
SI44587
SI44589
SI44739
For release 7.1.0
MF53848
SI44588
SI44590
SI44688
Other IBM i PTFs to help IFS save performance:
- 6.1.0: MF52495
- 6.1.1: MF52284
- 7.1.0: MF52772
14. In V7R1 Systems Director Navigator plugin, the scheduled
tasks always display scheduled status. This has been changed for
tasks scheduled to run once. For these tasks, BRMS now displays
the status of the last attempted submission (complete, error or
cancelled).
15. In V5R4 and above, saving multiple spoolfile lists in the
same control group might use multiple volumes. MSGBRM0004 RC
14will be posted in the joblog
16. In V5R4 and above, when running a SAVOBJ command and using a
volume that is in the BRMS inventory, BRMS will error with
MSGBRM3D1D RC7.
17. In V5R4 and above, when saving BRMS save files via
SAVSAVFBRM, BRMS may error with a MSGBRM148A.
18. In V5R4 and above, when saving QUSRBRM on i5 OS internal
virtual tapes and the save spans, there is an assertion and the
history record may be incorrect.
19. In V5R4 and above, when saving a domino server containing
more than 100 domino files in one directory which have a long
path (longer than 256), a MSGMCH3601 may be posted.
20. In V5R4 and above, when running a SAVSYS via BRMS, and a
MSGCPF9999 is posted, BRMS is incorrectly sending a MSGBRM1082
indicating that the SAVSYS was a success.
21. In V5R4 and above, after a volume has being used in a serial
or parallel set, a '+' sign will be shown next to the volume in
the WRKMEDBRM screen. When the volume is reused after it has
been expired, the '+' sign is not removed.
22. When appending to a volume that has a expiration date less
then the current expiration of the save, the volume is not
updated. This causes media to expire sooner then it should, and
items on that media are then also expired even though their
expiration is much further out.
23. In V5R4 and above, MSGCPF2419 might be sent on using the
BRMS client to display the BRMS log. Further enhancements will
be added in a future PTF.
24. In V5R4 and above, override support for the DTACPR parameter
is now supported for saves to save file within BRMS.
*HIGH/*MEDIUM/*LOW/*DEV/*NO/*YES are all valid values.
To enable the new save file DTACPR parameter to a *HIGH: CALL
PGM(QBRM/Q1AOLD) PARM('PARMOVR' '*ADD' 'SAVFDTACPR' '*HIGH ')
To enable the new save file DTACPR parameter to a *MEDIUM: CALL
PGM(QBRM/Q1AOLD) PARM('PARMOVR' '*ADD' 'SAVFDTACPR' '*MEDIUM
')
To enable the new save file DTACPR parameter to a *LOW: CALL
PGM(QBRM/Q1AOLD) PARM('PARMOVR' '*ADD' 'SAVFDTACPR' '*LOW ')
To enable the new save file DTACPR parameter to a *YES: CALL
PGM(QBRM/Q1AOLD) PARM('PARMOVR' '*ADD' 'SAVFDTACPR' '*YES ')
To enable the new save file DTACPR parameter to a *NO: CALL
PGM(QBRM/Q1AOLD) PARM('PARMOVR' '*ADD' 'SAVFDTACPR' '*NO ')
To enable the new save file DTACPR parameter to a *DEV: CALL
PGM(QBRM/Q1AOLD) PARM('PARMOVR' '*ADD' 'SAVFDTACPR' '*DEV ')
To remove the override, use the following command:
CALL PGM(QBRM/Q1AOLD) PARM('PARMOVR' '*REMOVE ' 'SAVFDTACPR')
To show the current override being used, use the following
command:
CALL PGM(QBRM/Q1AOLD) PARM('PARMOVR' '*DISPLAY' 'SAVFDTACPR')
25. Enabled functional authority on media classes to prohibit
output operations on media the user does not have authority to.
CORRECTION FOR APAR 'SE49427' :
-------------------------------
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 'SE49427' :
----------------------------------
None.
Activation Instructions
None.
Special Instructions
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
-------------- ------------------------------------------------------------
SI43868 BRM-MAINT-INCORROUT Fixes
SI42925 BRM-MAINT-INCORROUT Fixes
SI42066 BRM-MAINT-INCORROUT Fixes
SI42449 BRM-BACKUP-INCORROUT OWNERSHIP OF MEDIA IS CHANGED AFTER BAC
SI41206 BRM-MAINT-INCORROUT Fixes
SI40005 BRM-MAINT-INCORROUT Fixes
SI40005 BRM-MAINT-INCORROUT Fixes
SI38740 BRM-MAINT-INCORROUT Fixes
SI38740 BRM-MAINT-INCORROUT Fixes
SI37987 BRM-MAINT-INCORROUT Fixes
SI37264 BRM-MAINT-INCORROUT Fixes
SI37264 BRM-MAINT-INCORROUT LARGE AMOUNT OF RECORDS PUT INTO QA1ANET
SI35676 BRM-BACKUP-MSGBRM400F WHEN RUNNING A CONTROL GROUP WITH A *S
SI35676 BRM-MAINT-INCORROUT Fixes
SI35676 BRM-MAINT-INCORROUT Fixes
SI35676 BRM-MAINT-INCORROUT Fixes
SI35676 BRM-MAINT-INCORROUT Client Fixes
Summary Information
System.............................. | i |
Models.............................. | |
Release............................. | V7R1M0 |
Licensed Program............... | 5770BR1 |
APAR Fixed.......................... | View details for APAR SE49427 |
Superseded by:...................... | View fix details for PTF SI71641 |
Recompile........................... | N |
Library............................. | QBRM |
MRI Feature ........................ | NONE |
Cum Level........................... | C2115710 |
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 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.
Was this topic helpful?
Document Information
Modified date:
18 November 2011