IBM Support

SI42925 - 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, when running RSTLIBBRM, RSTOBJBRM, or
RSTBRM a MSGCPF41B0 message is sent...even if there are
alternative volumes to use.
2. In V5R4 and above, when running SAVLIBBRM and the current
release is input in the form of VxRxMx, MSGBRM4122 is posted
stating that the release is not valid
3. In V5R4 and above, QGPL Library save will hang on a spanning
volume due to the trace feature being turned on in the system
policy.  This PTF will change to turn this field off (*NO) on
any install or STRMNTBRM.
4. In V5R4 and above, when running BRMS maintenance, it's
possible a MSGMCH1210 F/ExSndPm x'000AE0 T/Q1ARRH may be
received because a BRMS backup may be running at the same time.
5. In V5R4 and above, IFS save errors like MSGCPF3823 do not
cause a control group to fail with a MSGBRM10A1, MSGBRM15A1 or
MSGBRM16A1.
6. In V5R4 and above, when we retrieve an IFS file on iASP from
media, a MSGSQL0206 and MSGCPFB620 are posted, even though the
file is retrieved and useable.
7. In V5R4 and above, when running spoolfile list(s) saves to a
TSM server a MSGCPFB8C4 maybe sent.
8. In V5R4 and above, systems running domino might have their
STRMNTBRM job hang in the domino server.
This PTF will not fix the domino hang, but will help be smarter
about which servers we ask for DAOS info from.
9. In V5R4 and above, when running a RMVLOGEBRM SLTDATE(*BEGIN
*END), no BRMS log entries are removed.
10. In V5R4 and above, when running SAVDOMBRM as exits from a
BRMS control group, there is no longer a requirement of library
qualifying the SAVDOMBRM command.
11. In V5R4 and above, volume selection does not protect volumes
that are in verify move status. Volumes in verify move status
can be picked as append candidates after MOVMEDBRM has been ran
before the volumes have been verified.  To allow the old
behavior of selecting media in verify move status run the
following command:
CRTDTAARA DTAARA(QUSRBRM/Q1ANOVFYM) TYPE(*CHAR).
12.  In V6R1 and above, when running WRKSPLFBRM on trying to
restore a spoolfile a MSGCPF5013 is sent.
13. In V5R4 and above,
SAVLIBBRM using an image catalog does not handle the Virtual
Tape Volume not available error - MSGCPF41B4 or Virtual tape
volume not found - MSGCPF41B5
14.   In V5R4 and above, SAVLIBBRM using internal virtual tape
does not select the correct tape to append to.
15. In V5R4 and above, when saving libraries to parallel device
resources (i.e. SAVLIBBRM or using control groups), BRMS does
not honor the USEOPTBLK parm.
16. In V5R4 and above, when running STRMNTBRM a MSGCPF3CAA might
be sent if the system has a lot of libraries.
17. In V5R4 and above, when doing a WRKSPLFBRM, OUTPUT(*), it is
not the same as OUTPUT(*PRINT).  This PTF will also change the
OUTPUT(*) to not list entries from duplicate volumes.
If a data area QTEMP/Q1ASPLFDUP is created, then all original
items and duplication's are displayed.
18. In releases IBM 7.1 and earlier, media movement is not
allowed for volumes that are marked for duplication.  The
following interfaces can be used to override this behavior and
allow movement for volumes that are marked for duplication.
This is useful for device TS7650 and other virtual tape
libraries which require virtual volumes to be moved during the
duplication process.

To override a move policy to allow movement when a volume is
marked for duplication:
CALL QBRM/Q1AOLD PARM ('MOVMRKDUP '  '*SET      '  'move
policy'  'Y')

To remove the override for a move policy that allows movement
when a volume is marked for duplication:
CALL QBRM/Q1AOLD PARM ('MOVMRKDUP '  '*SET      '  'move
policy'  'N')

To display all overrides for move policies that allows movement
when a volume is marked for duplication:
CALL QBRM/Q1AOLD PARM ('MOVMRKDUP '  '*DISPLAY  ')

To remove all overrides for move policies that allows movement
when a volume is marked for duplication:
CALL QBRM/Q1AOLD PARM ('MOVMRKDUP ' '*CLEAR    ')

Restriction: In releases IBM i 7.1 and earlier, there will be no
synchronization of this behavior to other systems in the BRMS
network.  Each system wishing to use this new function will need
to run the commands above. In releases following IBM i 7.1, this
restriction will be removed.

.

Note: The move policy override to allow movement when a volume
is marked for duplication will only be available in releases IBM
i 7.1 and earlier. In releases following IBM i 7.1, similar
interfaces will be provided on BRMS commands. The following PTFs
or their superseding PTFs are required:

* 7.1 SI40005
* V6R1M0 SI40006
* V5R4M0 SI40001
19. In V6R1 and above, when running SAVSYSBRM OMIT (*SYSDTA),
the save fails because BRMS is finding the controlling subsystem
is up
20. In V5R4 and above, when selecting the option to omit
"Additional information for basic user disk pools" or *USRASPAUT
in GUI, the omit is ignored, MSGBRM2170 and/or MSGBRM2171 are
still in the joblog indicating that the data is being saved.
21. In V5R4 and above, if the tape media library is held, media
is not ejected. This PTF will not change this behavior but will
post a MSGBRM1703 indicating that the tape media library is
held.
22. In V5R4 and above, when switching from *NONE to *LIB on the
Receive Media Information value in the System Policy on a
specific system, can cause major problems with storage, CPU
usage and BRMS Network sync delays. Therefore, BRMS will no
longer submit remote commands on other systems in the network to
reflect existing saved history.
23. In V5R4 and above, if you save parallel IFS(SAVBRM)  or
parallel Domino save and the request has parallel resources set
with min/max different and SEQNBR(1) or Append to Media  is *NO
...not all the media files will start at sequence number 1.
24. In V5R4 only,  on saving a  control group using parallel
resources , if there is *LNK list in the control group and the
min/max  are different,  we might append to the some media
files, even though no appending was asked for.
25. In V5R4 and above, when removing a volume that is not owned
by the system doing the remove may cause problems. With this
PTF, if the owning system is not in the BRMS network, then the
media will be removed.  If the owning system is in the BRMS
network, the local system will attempt to take ownership of the
volume before the remove is attempted. If the local system
cannot take ownership of the volume, the media will not be
removed and a MSGBRM1533 message is sent in V5R4 and in V6R1 and
above message MSGBRM0004 is sent.
26.  In V5R4 and above, the creation date on media is still
being updated when starting a backup prior to the defined "Day
start time" in the BRMS System policy, and finishing with a
QUSRBRM save after that start of day time.
27. In V5R4 and above, after moving a virtual volume to another
location and doing another save...BRMS will still use the moved
volume.  The volume selection algorithm has been changed to
insure the location is valid.  This will only apply to specific
locations...i.e. can not be *ANY for a location.
28. In V6R1 and above when running a control group a MSGMCH0601
message might appear in the job log, yet the control group
works.  This message will be removed as it is not a problem.
29. In V5R4 and above, spool files archived by BRMS, cannot be
restored when it had been archived by a user and the user
profile has been deleted.  This also applies to restores of
spoolfiles saved in V5R3 and earlier.
30. In V5R4 and above the BRMS Flight recorders have been
requested to default to 50 Meg from 10 Meg.  If you wish to keep
it at 10 Meg, please run this command:
CRTDTAARA DTAARA(QUSRBRM/Q1AMAXFR) TYPE(*CHAR) LEN(9)
VALUE('010000000')
Or you can set it to the size you wish:
http://www-03.ibm.com/systems/i/support/brms/dataAreas.html#Main
tenance
31. In V6R1 and above, BRMS will change to select volumes that
have been expired the longest.
32. In V6R1 and above, BRMS may use too many tapes if doing a
parallel control group backup and asking to start all parallel
volume sets at Tape File Sequence Number 1.
If there is a *LOAD in a control group that does parallel saves,
more volumes than expected will still be used if using the Auto
Duplication function.  The circumvention is to turn off auto
duplication until a fix is provided in a BRMS PTF.
Notes:
1. The need for *LOAD might not be valid anymore with the new
function. If you had added a *LOAD due to parallel saves and
sequence number 1 issues, the *LOAD can be removed.
2. The *MEDDFN type objects that BRMS creates in QTEMP will now
be owned by QBRMS and he following messages will be posted in
the joblog:
MSGCPI2201
MSGCPC2201
MSGCPC2202
MSGCPC2206
33.  In V6R1 and above, BRMS will fail with an MSGBRM3015 error,
when the first item is a *EXIT that is not blank (action item in
the Pre-Exit) in a control group that has a SAVDOMBRM in it.
34. In V5R4 and above, when restoring spoolfiles saved via
parallel resources, BRMS will use *SEARCH and this will cause
*LEAVE to fail with a MSGCPF3780


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

CIRCUMVENTION FOR APAR 'SE47180' :
----------------------------------
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
--------------  ------------------------------------------------------------
   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 SE47180
Superseded by:......................View fix details for PTF SI71641
Recompile...........................N
Library.............................QBRM
MRI Feature ........................NONE
Cum Level...........................C1270710


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:
15 June 2011