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.
| 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 V7R1 and above, support has been added to the IBM
Navigator for i to allow the following BRMS tasks to be
scheduled:
- New backup control groups
- New move policy
- Save of all save files
2. In V5R4 and above, when the Duplicate Media using BRM
(DUPMEDBRM) command is used to duplicate a BRMS volume and the
output sequence spans volumes, the save timestamp of saved item
may be incorrect. This can cause expiration or deletion of these
saved items to fail with message MSGMCH3601.
3. In V7R1 and above, if the Start Maintenance for BRM
(STRMNTBRM) command is run while BRMS backups are being run in
other jobs, maintenance may corrupt the save history for the
active backups.
4. In V6R1 and above, performance has been improved when doing
backups using control groups containing *LNKOMTLTS and/or
*LTSOMTONL entries to save Domino objects.
5. In V7R1 and above, backups may send message MSGBRM170A for
the output volume. This problem will be fixed after running
maintenance.
6. In V6R1 and above, support has been added to allow
incremental saves to be restored, without restoring a full save,
when *SAVDATE is specified for the Save level (SAVLVL) parameter
on the Restore Library using BRM (RSTLIBBRM) command.
To enable this function in current job, run the following
commands in the same job:
CRTDTAARA DTAARA(QTEMP/Q1AALWPART) TYPE(*CHAR) LEN(1)
To enable this function in all jobs, run the following commands
in any job:
CRTDTAARA DTAARA(QUSRBRM/Q1AALWPART) TYPE(*CHAR) LEN(1)
7. In V5R4 and above, when viewing save history created by a
SAVxxxBRM command, the output from the Work with Media
Information (WRKMEDIBRM) command will show an incorrect date for
the Expiate Date field if the expiration date is greater than
2038.
8. In V5R4 and above, when *BKU is specified for the File group
type (GRPTYPE) parameter on the Duplicate Media using BRM
(DUPMEDBRM) command, saved items with a save type of *CUML,
*INCR and *QBRM are not duplicated.
9. In V6R1 and above, when multiple restores are started using
the Start Recovery using BRM (STRRCYBRM) command, it may cause
the Restore Deferred Objects (RSTDFROBJ) command to be run. If
the STRRCYBRM command is used to submit the restores to batch,
the RSTDFROBJ command may be run before the restore batch jobs
complete. Objects that are restored after the RSTDFROBJ command
is run will not be processed by the RSTDFROBJ command.
10. In V5R4 and above, when viewing Saved Items using the Work
with Media Information (WRKMEDIBRM) command, the Save Type field
may be incorrectly set to *FILE.
11. In V5R4 and above, when *SCHHST is specified for the From
volume identifier (VOL) parameter on the Duplicate Media using
BRM (DUPMEDBRM) command, message MSGCPA4268 may be in the job
log.
12. In V5R4 and above, when spooled files are restored from a
Tivoli Storage Manager (TSM) server using the Work with Media
Information (WRKMEDIBRM) command, message MSGCPF3795 may be in
the job log.
13. In V5R4 and above, detached journal receivers created by
BRMS processes may not be deleted when running the Start
Maintenance for BRM (STRMNTBRM) command with *YES specified for
the Change BRM journal receivers (CHGJRN) parameter.
14. In V5R4 and above, media is not expired correctly if message
MSGBRM0010 with reason 1 is in the job log when running the
Start Maintenance for BRM (STRMNTBRM) command with *YES
specified for the Expire media (EXPMED) parameter.
15. In V5R4 and above, save files in library QUSRBRM with names
like Q######### (where '#' is a number) may not be correctly
deleted by the Start Maintenance for BRM (STRMNTBRM) command.
16. In V5R4 and above, the Display ASP Information using BRM
(DSPASPBRM) command may not show correct information for an IASP
that is varied-on.
17. In V5R4 and above, the Start Backup using BRM (STRBKUBRM)
command may force a full backup for a *LINK control group entry
when an incremental backup is attempted.
18. In V5R4 and above, when the Work with Media Information
(WRKMEDIBRM) command is run and option 4 is selected to remove a
Saved Item, it may fail with message MSGCPF5032, MSGSQL0913 or
MSGCPF9803.
19. In V5R4 and above, performance has been improved for remote
operations. For example, if the From system (FROMSYS) parameter
is used on a BRMS command.
20. In V5R4 and above, the Work with Media using BRM (WRKMEDBRM)
command may not display all the volumes enrolled in the BRMS
inventory.
21. In V5R4 and above, when attempting to restore individual
objects using the Work with Media Information (WRKMEDIBRM)
command and then taking options 9, 9, 9, 7 for a saved item
created by duplicating a parallel save, objects may not be
listed.
22. In V5R4 and above, when installing the BRMS product using
the Initialize BRMS (INZBRM) command with OPTION(*RUNPRDINZ)
before the Initialize BRMS (INZBRM) command with
OPTION(*ESTPRDINZ) has been run, message MSGMCH3601 may be in
the joblog.
23. In V5R4 and V6R1, when option 4 is selected to change a BRMS
network group after running the Work with Policies using BRM
(WRKPCYBRM) command with parameter TYPE(*SYS), the Receive media
info field may not be correct. Additionally, some BRMS
information may not be correctly synchronized throughout the
BRMS network. For example, if running remote duplication using
the Duplicate Media using the BRM (DUPMEDBRM) command, media
information from the duplication may not be correctly
synchronized.
24. In V5R4 and above, support has been added to allow devices
to be selected in order by English (CCSID 37) characters when
*MEDCLS is specified for a device. To enable this function, run
the following command:
CRTDTAARA DTAARA(QUSRBRM/Q1ATAPSLCT) TYPE(*CHAR) LEN(1)
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 SI51029 
4143
R720 SI50936 
4101
Affected Modules
Affected Publications
Summary Information
| Status............................................ | CLOSED UR1 |
| HIPER........................................... | No |
| Component.................................. | 5770BR100 |
| Failing Module.......................... | RCHMGR |
| Reported Release................... | R720 |
| 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
Document Information
Modified date:
07 June 2014