Excellent! I was not sure if that would work with the original volume removed. Nice work


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Tuesday, August 23, 2016 3:12 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: DUPMEDBRM vs recovery reports

I forgot an option on the report
That fixed it.

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

From: Rob Berendt <rob@xxxxxxxxx>
To: midrange-l@xxxxxxxxxxxx
Date: 08/23/2016 03:00 PM
Subject: DUPMEDBRM vs recovery reports
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>

Migrating tape media from LTO4.
Did a DUPMEDBRM of our last system save (June) to LTO5. It's a
multivolume set.
WRKMEDBRM shows the new dup
Volume Creation Expiration Move Media Dup
Serial Status Date Date Location Date Class Sts
G00009 + *ACT 06/11/16 05/28/17 GRRTVTL *NONE ULTRIUM5 *
G00010 + *ACT 06/11/16 05/28/17 GRRTVTL *NONE ULTRIUM5 *
G00012 + *ACT 06/12/16 05/28/17 GRRTVTL *NONE ULTRIUM5 *

6=Work with serial set
shows these tapes.

Deleted the LTO4 volumes.

Go to print the recovery reports and I get:

Summary report:
Recovery Volume Summary Report

Detailed report:
----- Attention ---------------------------------------------------
The Licensed Internal Code has not been saved.
Each section kind of has the same thing.

This isn't helping my SOX audit...

Rob Berendt

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].