Rob,
WRKLOCBRM, great cmd.
Thanks
Paul
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, June 20, 2013 10:51 AM
To: Midrange Systems Technical Discussion
Subject: RE: BRMS moving
Paul,
We have more expired tapes than we have slots in our tape library. Then again we only have 59 slots in the 'logical' library allocated to BRMS. We make our home location KVLCMPROOM.
WRKLOCBRM
Location Volumes Containers Text
GRTCMPROOM 0 0 Garrett computer room
IBM 3 0 IBM Corporation, Rochester MN
IRONMTN 120 0 Iron Mountain
KVLCMPROOM 48 0 Kendallville computer room
TAPGRT01 0 0 Entry created by BRM configuration
TAPKVL01 49 0 Entry created by BRM configuration
TAPKVL02 0 0 SCSI 3573 L2U LTO3
We kind of like WRKLOCBRM to match what the GUI says on the tape library.
Media Storage Cartridges Cartridges
Name Type Slots in Storage Drives in Drives
TAPKVL01 LTO 59 43 3 0
and DSPTAPSTS TAPKVL01
Library device . . : TAPKVL01
Number of resources: 3
Total slots . . . : 59
Available slots . : 16
This tells me it's holding (59-16) or 43 cartridges.
Which tells me I have a wee bit of auditing to do...
If our BOFH was a production inventory clerk excrement would have hit the fan long ago for telling the system that stuff was moved around before it was done.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>,
Date: 06/20/2013 09:57 AM
Subject: RE: BRMS moving
Sent by: midrange-l-bounces@xxxxxxxxxxxx
Vincent,
We keep volumes in the library after a save.
In order to do this, I had to set up a fake sequence in the move policy,
DAILY45
Our duplicated volumes go off site, they have a different move policy,
DAILY10D
The other setting that is important here is your *home location, in our
case TAPMLB01.
When volumes expire, this is where movement will put the volume.
In our case, we wanted expired volumes to be moved back to TAPMLB01.
Home location for media . . . . . . . . TAPMLB01
Move policy . . . . . . . . . . : DAILY45
Home location . . . . . . . . . : *SYSPCY
Use container . . . . . . . . . : *NO
Verify moves . . . . . . . . . : *NO
Calendar for working days . . . : *ALLDAYS
Calendar for move days . . . . : *ALLDAYS
Text . . . . . . . . . . . . . : Pencor05 Daily Full
Seq Location Duration Container Action
10 TAPMLB01 *EXP
Move policy . . . . . . . . . . : DAILY10D
Home location . . . . . . . . . : *SYSPCY
Use container . . . . . . . . . : *NO
Verify moves . . . . . . . . . : *NO
Calendar for working days . . . : *ALLDAYS
Calendar for move days . . . . : *ALLDAYS
Text . . . . . . . . . . . . . : Pencor05 Daily Full DUP
Seq Location Duration Container Action
10 THIRDST 10
20 TAPMLB01 *EXP
Paul
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, June 20, 2013 7:17 AM
To: Midrange Systems Technical Discussion
Subject: RE: BRMS moving
The more I look at this the more I am sure that Becky and I are on the
right track.
First of all, you change the expiration date on the data on the tapes you
want to write over, which really flabbergasts me. This takes the data on
the tapes from expired to active.
Then you run a move media. Well, the first thing the system is going to
say is, "Hey, we've got some active data here. We better move these tapes
offsite. Let's start chucking them into the I/O slot(s)."
And, only after you've ejected the tapes, you try to start a save?
Can you see what's wrong with this process?
I think it all begins with you monkeying around with the expired dates.
That means the data on the tapes. It does not mean "gee these tapes are
really old and should be tossed into the trash".
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail
to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: "Bakutis, Becky" <BBakutis@xxxxxxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 06/19/2013 05:07 PM
Subject: RE: BRMS moving
Sent by: midrange-l-bounces@xxxxxxxxxxxx
I agree with Rob's comment below and I was always told not to use the
MOVMED(*YES) parameter on the STRMNTBRM command because it may do
unpredictable things. So I created a separate job to run the MOVMED
process after all systems have completed BRMS activities.
"Perhaps you only want to use the MOVMED(*YES) option on the day when you
are ready to physically remove the tapes from the library."
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vincent Forbes
Sent: Wednesday, June 19, 2013 11:07 AM
To: Midrange Discussion
Subject: BRMS moving
I am having trouble with BRMS moving. I get expired tapes, move them to
TAPMLB01, change them {CHGMEDBRM} to have a new expiry date & move policy
{DAILYSAVES}. The backup picks one of the tapes loaded works fine.
STRBKUBRM CTLGRP(BRMSDAILY) SBMJOB(*NO) RETENTION(*CTLGRPATR 35)
After this command...
STRMNTBRM RMVMEDI(*REUSE) MOVMED(*YES) RGZBRMDB(*YES)
It gets a CPA401E "Library device storage slots full (C R)". Only "C"
works. The tape drive is a 3573/040 with 12 slots & only 6 are used.
After this, all of the tapes in TAPMLB01 are moved to various locations.
I want the tapes to remain in TAPMLB01 for the week. What am I missing?
Vincent
V6R1M0 Change System Policy
Type choices, press Enter.
Media policy . . . . . . . . . . . . . . DAILYSAVES Name, F4 for list
Devices . . . . . . . . . . . . . . . . TAPMLB01 Name, F4 for list
Home location for media . . . . . . . . TAPMLB01 Name, F4 for list
Media class . . . . . . . . . . . . . . ULTRIUM4 Name, F4 for list
Sign off interactive users . . . . . . . *YES *YES, *NO
Sign off limit . . . . . . . . . . . . . 30 0-999 minutes
Output queue . . . . . . . . . . . . . . *PRTF Name, *PRTF
Library . . . . . . . . . . . . . . . Name, *LIBL</x>
Day start time . . . . . . . . . . . . . 0:00:00 Time
Media monitor . . . . . . . . . . . . . *YES *YES, *NO
Shared inventory delay . . . . . . . . . 60 30-9999 seconds
Auto enroll media . . . . . . . . . . . *NO *NO, *YES
Default usage. . . . . . . . . . . . . . *YES *NO, *YES
Change Backup Policy
Type choices, press Enter.
Media policy for full backups . . . . . DAILYSAVES Name, F4 for list
Media policy for
incremental backups . . . . . . . . . DAILYSAVES Name, F4 for list
Backup devices . . . . . . . . . . . . . TAPMLB01 Name, F4 for list
Default weekly activity . . . . . . . . FFFFFFF SMTWTFS(F/I)
Incremental type . . . . . . . . . . . . *CUML *CUML, *INCR
Force full backup days . . . . . . . . . *NOMAX 0-365, *NOMAX
Sign off interactive users . . . . . . . *SYSPCY *YES, *NO, *SYSPCY
Sign off limit . . . . . . . . . . . . . *SYSPCY 0-999 minutes,
*SYSPCY
Save journaled objects when
saving changed objects . . . . . . . . *NO *YES, *NO
Change Move Policy
Move policy . . . . . . . . . : DAILYSAVES
Home location . . . . . . . . . VAULT Name, *SYSPCY, *ORIGIN, F4
list
Use container . . . . . . . . . *NO *YES, *NO
Verify moves . . . . . . . . . . *NO *YES, *NO
Calendar for working days . . . *ALLDAYS Name, *ALLDAYS, F4 for
list
Calendar for move days . . . . . *ALLDAYS Name, *ALLDAYS, F4 for
list
Text . . . . . . . . . . . . . . Dailysaves - Move Policy
Type choices, press Enter.
Seq Location Duration Container Action
10 TAPMLB01 5
20 IRONMOUNT 35
Display Backup Control Group Entries
Group . . . . . . . . . . : BRMSDAILY
Default activity . . . . : *BKUPCY
Text . . . . . . . . . . : Daily System Backup
Weekly Retain Save SWA
Backup List ASP Activity Object While Message Sync
Seq Items Type Device SMTWTFS Detail Active Queue ID
10 *EXIT *******
20 *SAVSECDTA FFFFFFF *YES
30 *SAVCFG FFFFFFF *YES
40 *ALLUSR *SYSBAS FFFFFFF *YES *SYSDFN *LIB *NONE
50 *ALLDLO FFFFFFF *YES *NO
60 *LINK *ALLAVL FFFFFFF *YES *NO
70 *EXIT *******
midrange.com
