Yes, use and create the data area in your save job QTEMP/Q1ADMEDPCY as per the document.
On our Production LPAR, we have one control group for all our daily full save, retention of 45 days.
Four times a month, we have the need to retain the save for 13 months.
Month end save is Perm.
We were successfully able to override the STRBKUBRM save for the different retentions, but not the AutoDup.
IBM DCR request created a data area for this purpose.
In my AJS BRMS save job, we set the data area, which then controls the AutoDup
50 CRTDTAARA DTAARA(QTEMP/Q1ADMEDPCY) TYPE(*CHAR) LEN(10) VALUE('CYCBR...
60 CHGOBJOWN OBJ(QTEMP/Q1ADMEDPCY) OBJTYPE(*DTAARA) NEWOWN(QBRMS)
How to Override the Auto Duplication To Media Policy for STRBKUBRM
The control group specified on the Start Backup using BRM (STRBKUBRM) command determines which media policy will be used during the backup. The Automatic duplication fields in the media policy determine whether media used for a backup will automatically be duplicated. The To media policy field for Automatic duplication is used to specify the media policy of the output volumes.
In releases IBM i 6.1 and later, to override the media policy that is specified in the Automatic duplication To media policy field when STRBKUBRM is run, do the following.
CRTDTAARA DTAARA(QTEMP/Q1ADMEDPCY) TYPE(*CHAR) LEN(10) VALUE(nnnnnnnnnn) QSYS/CHGOBJOWN OBJ(QTEMP/Q1ADMEDPCY) OBJTYPE(*DTAARA) NEWOWN(QBRMS)
Where nnnnnnnnnn is the media policy that will be used as the to media policy on the auto-duplication.
Note: In releases IBM i 7.1 and IBM i 6.1, the following PTFs or their superseding PTFs are required:
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Kevin Monceaux
Sent: Thursday, August 20, 2015 2:32 PM
To: Midrange Systems Technical Discussion
Subject: Re: DUPTTAP, DUPMEDBRM and/or AutoDup usage/issues
On Thu, Aug 13, 2015 at 08:51:57PM +0000, Paul Fenstermacher wrote:
4. Early on in using auto dup we found that the submitted auto dup job
would use the media policy that was just used for the save as the "to"
media policy rather than the one we specified.
We seem to be having the same problem where I work. We're fairly new to BRMS and still getting the kinks out of our setup. Is there a fix for the above problem? Is using data area Q1ADMEDPCY to override the AutoDup media policy a work around for the problem? Most of our LPARs running BRMS are at 7.2, one is at 7.1. We're mostly running backups on just one of the 7.2 LPARs at the moment until we get our media and move policies working the way we want.