IBM Support

SI40005 - 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 V6R1 and above,  an MSGMCH0601 or MSGMCH3601 might occur
while running STRBKUBRM

2. In V6R1 and above, when adding an IP address longer than 10
characters long in BRMS GUI, it fails "Name too long"

3. In V5R4 and above,  In V5R4 and above, if expiration date of
the expired volume used is set to a date more in the future than
that of what the  media policy will set it to,  the expiration
date of volume will not be changed to the correct date specified
by the media policy when the volume is first saved to .

4. In V5R4 and above,Running archive control group with
OPTION(*REPORT) several

MSGCPA4067 are logged in joblog and in the QSYSOPR message queue

and are automatically answered 'C'. This problem occurs only if

the control groups tries to process a link list that has some

omits.

5. In V5R4 and above on running an install from a save of the
BR1 LPP a MSGCPF3181 error may posted.  .(need to load PTF and
redo a save of the LPP on source system)

6. In V5R4 and above,when saving data to a TSM server from
different systems in a BRMS network, and the history information
is shared, it's possible that BRMS will try restore the from the
incorrect library when WRKOBJBRM or RSTOBJBRM is used.

MSGCPF3801 and MSGCPF3780 messages may be posted

7, In V5R4 and above,after running a INZBRM OPTION(*CHGSYSNAM)
spool file restore fail with MSGCPF3770 message.

8. In V6R1 and above, getting a MSGBRM0004 when using SETMEDBRM
and running native save commands to append data to tape.

9. In  V5R4 and above,  if a domino backup uses a savefile with
no device (*NONE)  specified,  a MSGBRM1442 message is sent.

10. In V5R4 and above, when running a control group with a
special value list entry for *LNKOMTONL or *LTSOMTONL, the
Domino server crashes because of locks on the transaction log
directory.


CORRECTION FOR APAR SE43562 :
-----------------------------
Load and apply this ptf.

CIRCUMVENTION FOR APAR SE43562 :
--------------------------------
None.


DESCRIPTION OF PROBLEM FIXED FOR APAR SE44227 :
-----------------------------------------------
12. In release i7.1 and earlier there is not a way to specify
the update history parameter on save commands. A new program
call is provided to allow update history to be changed when
saving library  and IFS objects.  See the Q1AOLD call for
PARMOVR here
http://www-03.ibm.com/systems/i/support/brms/bestPractice.html .

13. In release v6r1 and above, the iNav client reports show a
wrong product id.

14. In V5R4 and above, when in restricted state and using BRMS
GUI to send email alerts, if this fails, a control group with
*LINK will fail with a MSGCPF4101 .

15. In V6R1 and above, when the option "Back Up specific Items"
is used in the iNav client, the parameter options changed in the
Prompt panel are not updated in the command string.

16. In V5R4 and above, BRMS will lock the members of the objects
when doing archive report, STRARCBRM ACTION(*REPORT), which
could impact applications or users using the files that BRMS is
checking..

17. In V5R4 and above, BRMS can not retrieve object from a
duplicated volume when original volume is not available.

18. In V6R1 and above, when using menu option to collect BRMS
statistics (new at R610) and report does not print.  MSGMCH6903
and MSGMCH3601 are issued

19. In V5R4 and above,when archiving objects to a TSM server
using BRMS and then when a user with *USE authority to the
object  tries to use dynamic retrieval of *SBMJOB or *DELAY, the
restore of the object from the TSM server will fail with
authority errors

20. In V5R4 and above, When running a SAVMEDIBRM or
automatically saving the recovery information (SAVMEDI) in a
control group, the media uses

(WRKMEDBRM option 5) is incorrectly incremented.

21. In V5R4 and above, the MARKDUP parameter in DUPMEDBRM will
be overridden by media policy when media information is saved
(SAVMEDI)

22. In V5R4 and above, if an exception occurs during the
reorganization of  the physical files when STRMNTBRM is running,
it will cancel the whole maintenance job.

23. In V5R4 and above, recovery report incorrectly lists all
saves of link lists ( including  *LNKOMTLTS, *LNKOMTONL and
*LTSOMTONL)  items instead of just latest one.

24. In V6R1 and above, when we upgrade BRMS from a lower
release, archives may fail with MSGBRM10A1.



25. In V6R1 and above, when changing the category of a volume
from WRKMLMBRM (Option 6) on multiple volumes, user is prompted
for each volume. In prior releases did not prompt each volume.

We will be going back to the old behavior, however, to force
prompting the user can run this command that will apply to all
brms jobs and get the V6R1/V7R1 behavior back:

CRTDTAARA DTAARA(QUSRBRM/Q1ACTGPMPT) TYPE(*DEC) LEN(1)



Or to turn it off can run this:

DLTDTAARA DTAARA(QUSRBRM/Q1ACTGPMPT)



26. In V5R4 and above,  If there are more than 9999 libraries in
the not saved attention list , STRRCYBRM or STRMNTBRM will fail
with MSGMCH0603

27. In V5R4 and above, GUI getting " Device 'device-name' is not
compatible with media pool 'media pool-name' " error on control
group properties when hit OK.

28. In V7R1 and below, restoring spool files fail with
MSGCPF3770 when the time zone has changed on the system since
the last save was performed.

29. Due to problems after loading the BRMS PTF and keeping QBRM
in the library list, this will now be taken out of the library
list.

30. In V5r4 and above,  if multiple backups are started at
exactly the same time, STRBKUBRM, MSGCPF1023 F/Q1AC0BK followed
by a MSGBRM1820 may be posted because data area BRMS uses is
already created.

31. In releases prior to V7R1 when running a BRMS GUI client at
V7R1, the BRMS log dialog to display the messages in the BRMS
log incorrectly shows the control group field. When a value is
entered for the control group, message SQL0206 is sent. The
control group cannot be displayed in releases prior to V7R1.

32.  In releases prior to V7R1 when running a BRMS GUI client at
V7R1, the options to run maintenance as part of a control group
incorrectly display the options to Run Move policies, Expire
media sets and Reorganize BRMS files. These options should not
be displayed in releases prior to V7R1.

33. In the BRMS September 2010 PTF (see below for numbers)  and
with the Domino 8.5.2 release, you can now separate out the
domino databases (nsf files) from the directory attach object
services(DAOS) objects (nlo files).  This allows you to do full
and incremental backup in a mixed fashion.  Maybe you want a
full save of the databases every day, but incremental saves on
the weekdays of the DAOS objects, this is now possible.



BRMS has enhanced the weekly activity to support two new backup
activities to go with the 2 current ways to back them up.
Currently, when you select an 'F' for a full, you get both a
full save of the domino databases and a full save of the DAOS
objects.  If you select an 'I' for incremental save you will get
an incremental save of both.

The two new backup activities are:

'N'  for a  full save of the domino databases but an
incremental save of the DAOS objects

'D' for an incremental save of the domino databases but a full
save of the DAOS objects.

Note: 'N' and 'D' are the defaults, but can be customized.



To enable this function, you will need to create a data area:

CRTDTAARA DTAARA(QUSRBRM/Q1ADAOSSEP) TYPE(*DEC) LEN(1)



It may be possible, in a future ptf, to eliminate the need for
this data area.



The recovery report(QP1ARCY) generated by the Start Recovery
using BRMS  (STRRCYBRM) and Work with Media
Information(WRKMEDIBRM) will be enhanced to display 2 new save
types:

*DAOSF  -  A full save of the DAOS objects for that Domino
server

*DAOSI   -  An incremental save of the DAOS objects for that
Domino server.

Note: If you use 'N' and/or  'D', BRMS will run in separated
mode , regardless of data area



Overriding the presentation characters for Domino Databases  and
DAOS weekly backup activity

Use the following command to override the default presentation
characters that are used to represent domino databases and DAOS
object saves in weekly activity fields.  The default, 'N' is
used to represent 'Domino Database full backups and incremental
DAOS  object  backups' and 'D' is used to represent Domino
Database  incremental  backups and full DAOS object  backups'.

CALL PGM(QBRM/Q1AOLD) PARM('DAOSCHARS ' '*SET    ' ' 'N' 'D')




To show the override values for presentation characters that are
used to represent Domino and DAOS, use the following command:

CALL PGM(QBRM/Q1AOLD) PARM('DAOSCHARS ' '*DISPLAY' ' ')




Note: The presentation character overrides for Domino and DAOS
will only be available in releases IBM i 7.1 and earlier. In
releases following IBM i 7.1, interfaces will be provided on
BRMS commands.



Note:  The BRMS client will not allow changing of control groups
until the releases following IBM i 7.1.



The following PTFs or their superseding PTFs are required:

- V7R1M0 SI40005

- V6R1M0 SI40006

- V5R4M0 SI40001

34. In V6R1 and above, backups fail with an MSGSQ30080 during
volume selection if BRMS has to go to a remote system to find a
volume. PTF SI40765(V7R1M0) or it's superseding PTF is also
required

35. In V5R4 and above, when doing a verifying media via i
Navigator (GUI) of a volume that is in the tape library in a
INSERTED status , the status is not changed to AVAILABLE


CORRECTION FOR APAR SE44227 :
-----------------------------
Load and apply this ptf.

CIRCUMVENTION FOR APAR SE44227 :
--------------------------------
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
--------------  ------------------------------------------------------------
   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 SE43562
View details for APAR SE44227
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:
13 September 2010