IBM Support

SI41206 - 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  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, INZBRM OPTION(*MERGE) does not add the
*LINK object level detail if the saves were done on the same day
on the from and to systems.
2. MSGMCH0601 randomly occurs on doing client operations to the
server.
3. In V5R4 and above, duplicating media using DUPMEDBRM with the
parameter SAVMEDI(xxxx). After the duplication is complete, the
text of the duplicated media does not match the text of the
original volume.


4. In V5R4 only, spooled files that are saved in parallel with
output queues using the SAVLIBBRM or SAVOBJBRM commands cannot
be restored as they are not associated with output  queues.
5. In V5R4 and above, when a system is in flash copy mode , it
still receives updates from other systems in the BRMS network
when SNA is available or TCP/IP alias's are being used.
6. In V6R1 and above, when using BRMS with multiple sync ids, a
MSGCPF2410 is posted even though all checkpoints are correctly
reached as expected
7. In V5R4 and above,WRKMEDIBRM is listing libraries as *NONE
even though they have being saved via BRMS
8. In V6R1 and above, saving data to an optical device  fails
with MSGOPT1331.
9. In V5R4 and above, WRKMEDBRM option 8 (movement) doesn't
check if ok to move to the location and the container and will
move it to the location and later error on the container.  We
need to check both at the same time.
10. In V6R1 and above,  when running incremental saves of
journal receivers via SAVOBJLBRM, MSGCPF3746 is posted with
incorrect date.
11. In V5R4 and above, volume selection is not able to reserve
enough volumes when multiple back-end DUPMEDBRM to VTL are
running on different systems at the same time.
12  In V7R1 and above, when maintenance is running, the network
updates on all the remote systems are held, which may cause some
updates to be lost..
13. In v5r4m0 and above, STRARCBRM may incorrectly process
integrated file system objects.
14. N/A
15. In v5r4 and above, Domino DAOS does not run separated the
first time the server is saved.

16. In v5r4 and above, archive's using parallel devices were
failing with a message MSGBRM1241 stating "....value blank for
media policy not found."
17.  Parallel Archive control group failing when a folder list.
MSGCPD0078  -Value '*MEDDFN   ' for parameter DEV not a valid
name.
18. In v6r1 and above, support * for auxiliary storage pool
device fields when adding entries to backup or archive control
groups. Also, support * for the Auxiliary storage pool device
(ASPDEV) parameter on SAVLIBBRM, SAVOBJBRM and SAVOBJLBRM.
Using * is equivalent to using the combination of *SYSBAS and
*CURASPGRP.
19. In v5r4 an above,  if using the INZBRM  *FLASHCOPY  (v6r1
and above) or  QBRM/Q1AOLD ('FLSSYSSTS' ...),
the value for the Enable FlashCopy in the System Policy, will
automatically be set to *YES, when this command or call
interface is used.
20. In 6.1, when restoring an IFS object with private
authorities saved, via WRKMEDIBRM, opt 9, opt. 9, opt. 9 and
opt. 7, and specifying on the recovery defaults to restore the
private authorities, the authorities are not restored.
21.  For customers using the new Flash copy BRMS system
synchronization function as described on our webpage,  there was
a problem found when running the recovery report, and libraries
not showing up.  If the customer ran the report with the OMITLIB
parameter *NONE on the STRRCYBRM command, then the libraries
would show on the recovery report.  The report was treating
libraries as deleted when they weren't.  These libraries were
just on varied off I-Asp's, so the report thought they were
deleted because it couldn't get to them.
22. In v5r4 and above, if we restore a not deleted object with
RSTOBJBRM OPTION(*OLD), BRMS will send a MSGCPF3770 and no other
objects are restored
23. In V5R4 and above, Media Uses count not be increased when
spanning volume.
24. Overriding the 'Detail retention days' parameter on the
RMVMEDIBRM command for IFS objects

In releases IBM i 7.1 and earlier, the 'Detail retention days'
parameter on the RMVMEDIBRM command applies to detail history
for library objects, spooled files, folders and IFS objects.
There is no way to change the retention days specifically for
IFS objects using the command.  This override is being provided
to change the detail history retention days for IFS objects.

To override the detail history retention days for IFS objects,
use the following command, where nnnn is the number of days the
IFS detail history will be retained after a save.
CALL PGM(QBRM/Q1AOLD) PARM('PARMOVR' '*ADD' 'LNKDTL' 'nnnn')

To remove the override:
CALL PGM(QBRM/Q1AOLD) PARM('PARMOVR' '*REMOVE ' 'LNKDTL')

To show the override:
CALL PGM(QBRM/Q1AOLD) PARM('PARMOVR' '*DISPLAY' 'LNKDTL')

Notes:
1. In releases IBM i 7.1 and earlier, this override is available
with the following PTFs or their superseding PTFs:
-7.1 SI41206
-V6R1M0 SI41205
-V5R4M0 SI41204

25. In v5r4 and above,  conversion issues with the BRMS Database
can occur, to get around this problem:

Try this call first:

QSYS/CALL QBRM/Q1AOLD PARM('INSTALL   ' 'ALTERTBL ' 'Y' '01'
'01' '65535'
'TEXTFLDS ' 'QUSRBRM   '    'N')

If that doesn't work try this one with a 'Y' at the end:
QSYS/CALL QBRM/Q1AOLD PARM('INSTALL   ' 'ALTERTBL ' 'Y' '01'
'01' '65535'
'TEXTFLDS ' 'QUSRBRM   '    'Y')

The job log may contain some DB messages about loss of data
(like CPA32B2) or other info messages(like CPI3210) which can be
ignored.

26. In v5r4 and above, When specifing *ALL to send BRMS messages
to an additional message queue,  MSGRNX0100 and MSGRNX0100 may
be posted and all messages may not be sent.
27. In v5r4m0 and above,  a backup may  fail with a MSGMCH0601
if using a control group with an *ALLDTCRCV. entry and the
system contains a journal that has a large number (1000's or
more) of journaled IFS objects.
28. Enable TSM Retry

TSM operations can return errors that may be resolved if they
are retried.  BRMS does not normally retry TSM operations.  To
enable the retries for TSM operations in BRMS the following
command can be ran.   In this example, the third parameter
indicates to retry operations for 60 seconds:  CALL
PGM(QBRM/Q1AOLD) PARM('TSMRETRY  ' '*SET    ' '00060')

The BRMS TSM retry time can be displayed with the following
command:
CALL PGM(QBRM/Q1AOLD) PARM('TSMRETRY  ' '*DISPLAY')

The BRMS TSM retry function can be disabled with the following
command:
CALL PGM(QBRM/Q1AOLD) PARM('TSMRETRY  ' '*REMOVE ')

Note:  In release IBM i 7.1 or earlier, the following PTFs or
their superseding PTFs are required:
- 7.1 SI41206
- V6R1M0 SI41205
- V5R4M0 SI41204

29. In V5R4 and above, when running a control group, that tries
to go to restricted state but doesn't reach, a MSGCPF1099 may be
posted when trying to start the controlling subsystem because
the control subsystem is still trying to end.  The only way to
get out of this state is to IPL the system.  A force IPL option
has been made available in this PTF.  This force IPL option,
will IPL the system when these 2 conditions are both true:
1.  When a *DTAARA QUSRBRM/Q1AIPLSUB exists.
2.  When BRMS attempts to start the controlling subsystem in the
post backup processing, and receives a CPF1099.

The IPL values used are the ones defined in the control group,
which can be pointing to the BRMS backup policy or even the BRMS
system policy.  The control group DOES NOT need to be set to IPL
*YES in order for this to work.
30. In v6r1m0 and above, INZBRM OPTION(*SECUREDDM) fails with
MSGBRM4023 if the signed on user does not have proper authority
to the command, even though it was called from a program using
an adopted profile that did have the correct authority.
31. N/A

32. N/A

33. In v5r4 and above, email messages are not sent out after an
IPL on a system that has the network feature but is not in a
BRMS network.
34. In V5R4 and above, when the BRMS System Policy is set to use
Alternate Media ,  STRRCYBRM or  WRKMEDIBRM option 7 to restore
will fail the original media is unavailable and the  duplicate
media is available.
35. In V5R4 and above, when running a remote duplication
(DUPMEDBRM FROMSYS(remote-system)), media information may not be
correct on the system the duplication was ran for.  The
duplicate media, may still show as expired.
36. In V5R4 and above, BRMS GUI restores which require APYJRNCHG
may fail with:
java.lang.NullPointerException
com.ibm.as400.brmsgui.BrmApiRTVVOLSET.processReceiver(BrmApiRTVV
OLSET.java:137)


To 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.

CORRECTION FOR APAR 'SE44968' :
-------------------------------
Load and apply this PTF.

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


Activation Instructions


None.




Special Instructions


All BRMS activity must stop and BRMS/400 users must signoff while this
ptf is being applied


Default Instructions

THIS PTF CAN BE APPLIED IMMEDIATE OR DELAYED.



Supersedes

PTF/FIX NO(S).  APAR TITLE LINE
--------------  ------------------------------------------------------------
   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 SE44968
Superseded by:......................View fix details for PTF SI71641
Recompile...........................N
Library.............................QBRM
MRI Feature ........................NONE
Cum Level...........................C1116710


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 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.

[{"Type":"MASTER","Line of Business":{"code":"LOB08","label":"Cognitive Systems"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"7.1.0"},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG15V","label":"PTF Cover Letters - OS\/400 General"},"Component":"","ARM Category":[],"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"V7R1M0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
30 November 2010