IBM Support

SI42066 - 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, doing a WRKMEDBRM option 13 on a volume
that has incremental saves of SAVDOMBRM, then paging up, BRMS
will fall into a loop and hang.

2. In V5R4 and above, dynamic retrieval of a *STMF in the root
('/') directory will fail with MSGCPFB417.



3. N/A

4. In V6R1 and above, PRTRPTBRM will  only show the duration in
minutes, the seconds information always show zero.

5. In V6R1 and above,  when running BRMS option to change
cartridge status , if tape library is not available, multiple
Q1ASYNTAP dumps are created

6. In V5R4 and above, when saving to a TSM server with
versioning and *PERM at the same time, history is incorrectly
deleted when BRMS maintenance is run

7. In V5R4 and above, when using a BRMS control group to run
saves and the control group attributes are set up to sign off
interactive users, if the user running the backup does not have
*JOBCTL authority, the job trying to sign off users will loop
with MSGCPF1344 - Not authorized to control job&3/&2/&1 -
F/Q1AC0SG T/Q1AC0SG.

8. In V5R4 and above, the date time information of IFS retrieval
is not recorded which will impact other function if they need
the information

9. In V6R1 and above, support is being added to run the
Reorganize BRMS database function of STRMNTBRM with parameter
RGZBRMDB(*YES) to a batch job.

To enable this new function:

CRTDTAARA DTAARA(QUSRBRM/Q1ARGZPFM) TYPE(*CHAR)



To disable this new function:

DLTDTAARA DTAARA(QUSRBRM/Q1ARGZPFM)

10. In V6R1 and above,  on the PRTRPTBRM  command,  if a save
spans over midnight, the duration is off by 24 hours on the
report.

11.  In V5R4 only, MOVMEDBRM OUTPUT(*OUTFILE) produces an empty
file. However, the parameter OUTPUT(*PRINT) works correctly.

12.  In V5R4 and above,  when SWA  backup of *ALLPROD specifying
a  message queue using MONSWABRM, backup will fail because
message queue is not found in QUSRBRM.

13.  Add the following to the Media and Maintenance sections on
the Support->Data areas page
http://www-03.ibm.com/systems/i/support/brms/dataAreas.html



In releases V5R4 and later, it's possible for BRMS volumes to be
owned by a system that is not in the BRMS network. Support has
been added to the STRMNTBRM command to change the owner of
expired BRMS volumes that are not owned by a system in the BRMS
network. The owner will be changed to the system on which the
STRMNTBRM is being run.  To enable this new function, run the
following command:

CRTDTAARA DTAARA(QUSRBRM/Q1ACHGOWNX) TYPE(*CHAR)



To disable this new function, run the following command:

DLTDTAARA DTAARA(QUSRBRM/Q1ACHGOWNX)

Note:  It is recommended to only create the data area on 1
system in a BRMS network...this will help with contention if
multiple systems run STRMNTBRM at the same time.

Note:  If STRMNTBRM is run in restricted state this data area
will be ignored and no volume ownership changes will occur.



Note:  In release IBM i 7.1 or earlier, the following PTFs or
their superseding PTFs are required:

- 7.1 SI42066

- V6R1M0 SI42065

- V5R4 SI42064







14.  In V5R4 and above, program posted in  MSGCPF1E64 is
incorrect when using  Q1AADDCGEO API.

15. In V5R4 and above, if an option 7 (expire) is done on a
volume and then a reclaim is done on a volume in the set, before
a STRTMNTBRM or RMVMEDIBRM is run, a continuation sequence might
get placed on duptap command causing a MSGCPF67FC   message

16. In V6R1 and above, when "Use local system name" was used for
the system name in the Global Policy Properties, General tab, it
failed MSGBRM3C4B. This problem has been fixed.

17. In V5R4 and above, object is refreed when run STRMNTBRM,
even if we define Retrieved object retention to *NOMAX in
retrieve policy.

18. In V6R1 and above, GUI reclaim media wizard, BRMS does not
show the status of the volumes so users cannot identify volumes
in *ERR status.

19. In V5R4 and above,  on doing a wrkmedbrm option 8, the
cartridge is not getting ejected on the move from the tape
library.  This only happens on doing a move where both the
location and container are changed at that same time.

20. In releases V6R1M0 and later, it is possible to display the
status of an individual  BRMS control group by running the
following command:

CALL QBRM/Q1AOLD Parm('CTLGSTATUS' '*DISPLAY'    'xxxxxxxxxx')

where xxxxxxxxxx = control group name requesting



If you wish to see all the control groups, run the following
command:

CALL QBRM/Q1AOLD Parm('CTLGSTATUS' '*DISPLAY')



The command will send a message for each control group that
contains the following information:

- Control Group Name

- Type (*BKU)  backup

- Status:  *SUCCESS/*FAILED/*QUALIFIED

- Save Date/Time:  CYYMMDDHHMMSS

- Job Nbr

- Expiration Date:  CYYMMDD





Note:  In release V6R1M0 or IBM i 7.1,  the following PTFs or
their superseding PTFs are required:

- 7.1 SI42066

- V6R1M0 SI42065

21. When doing a WRKLBRM and select option 4 to  delete a  list
(*FLR, *OBJ, *SPL or *LNK) , BRMS should check that the list is
not listed in any control group



22. In V5R4 and above, BRMS has enhanced the SQL error recovery,
to limit issues when users do not end all BRMS jobs when
applying 57xxBR1 PTFs as directed by the special instructions in
the cover letter.

23. In V5R4, when using parallel saves and specifying *ASPnn,
BRMS is not doing parallel saves or using multiple drives.

24. In V5R4 and above, when running BRMS saves of libraries, a
MSGCPF501B is erroneously posted.

25. N/A

26. In V5R4 and above, if you wish to display on the green
screen panel what aliases (if any)  this systems uses to get to
all the systems in the network via  TCP/IP, SNA, or DRDA...use
this command:



QSYS/CALL QBRM/Q1AOLD PARM('ALIASNAME'  '7')





27. In V5R4 and above, when running Domino 8.5.2 there is a new
directory that needs to be omitted to stop locks on files in
this new directory.  (.../domino/workspace/)

28. In V5R4 and above, Integrated file system objects that are
omitted from being archived, during a STRARCBRM
OPTION(*ARCHIVE), using object list omits or ASP values in
control group entries may be incorrectly deleted without being
saved.

29. In V5R4 and above,  BRMS *LNK lists saved in parallel will
not show any incremental backups *INCR or *CUML on the recovery
report or restore (STRRCYBRM)

30.  In V5R4 and above, when a scratch volume is mounted on a
drive and a BRMS save is ran, BRMS tries to use the volume, but
decides it is not a candidate because the move policy is
different.  A MSGBRM0004 message id is produced.

31. In V5R4 and above, when running DUPMEDBRM to a virtual tape
and reaching the last tape image in the catalog, BRMS was ending
with a MSGBRM4138 and MSGCPF41B3 messages.  This could also
apply to saves.

32.  In V6R1 and above, when running a control group that has a
mix of parallel and serial save items, depending on the order,
one of the volume sets for the parallel save appends, instead of
picking a new volume to start a new volume set.

33. In V6R1 and above, when using the SAV/RST master key, and
having set with a key other then the *DEFAULT, the attention
block is not getting printed out on the BRMS recovery report.

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

CORRECTION FOR APAR SE46067 :
-----------------------------
Load and apply this PTF.

CIRCUMVENTION FOR APAR SE46067 :
--------------------------------
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
--------------  ------------------------------------------------------------
   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 SE46067
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:
04 March 2011