Re: tape volume ID

[D.BALE@xxxxxxxxxxxxx]

I guess I've always just used the default EXPDATE(*PERM) on the save
operations and dealt with initializing the tape when I need it again.

I suppose I could wrap a CHKTAP and a INZTAP together in a program to retrieve
the volume ID via CHKTAP and initialize the tape with that.  If there's no
volume ID or the tape is uninitialized, assign a new volume ID based on a
"next number" scheme.  Any thoughts on that idea?

Dan Bale
IT - AS/400
Handleman Company
248-362-4400  Ext. 4952

-------------------------- Original Message --------------------------

Dan,

I think what people are saying is that if the data on the tape is expired
it will just write over it and you do not have to initialize the tape.

Rob Berendt

==================
Remember the Cole!


-------------------------- Original Message --------------------------

Using what command?  If INZTAP, don't you still have to specify the NEWVOL
parameter?

Dan Bale
IT - AS/400
Handleman Company
248-362-4400  Ext. 4952

-------------------------- Original Message --------------------------
Of course, if you wanted to reuse a tape and it's expiry date hadn't been
reached, you could always specify SEQNBR(1) CLEAR(*ALL)

...Neil


Chuck Lewis <clewis@iquest.net>
Sent by: owner-midrange-l@midrange.com
2001/02/12 12:47
Please respond to MIDRANGE-L


        To:     MIDRANGE-L@midrange.com, D.BALE@handleman.com
        cc:
        Subject:        Re: tape volume ID


Dan

What I do is initialize a tape with a unique volume ONCE. Start with 000000
(or
000001 if you aren't into IBM numbering <BG>)...

I have a file that keeps track of all of this (you can buy packages to do
this
too). My backups save with an expiration date calculated 21 days from the
day
they
are running (via a program) so they do not need to be reinitialized when
they
are
due to be used again (the expiration date has passed).

You can go into System Service Tools (STRSST) and take 1. Start a service
tool
and
then take 1. Product activity log and then take either 4. Work with
removable
media
lifetime statistics or 5. Display or print removable media session
statistics.
Either way you will see WHY you want to keep Volume ID's unique - this will
show
you the statistics of among other things, errors for each tape used.

HTH !

Chuck

D.BALE@handleman.com wrote:

> I've seen a "standard operating procedure" over the years of initializing
> tapes for backup using a new/different volume ID every time a tape is
used
> (usually the current date value).  Does doing this defeat the ability of
the
> AS/400 to detect bad tapes over a period of time?  "Problem Analysis" is
a
> term that pops into my head for some reason.  It seems to me that the
Volume
> ID should be set once per tape, and never used again on another tape.
Yes?
No?
>
> As I'm just getting involved in this again for the first time in five
years,
> my memory's still a little shaky on the subject, but I seem to remember
> thinking that if INZTAP didn't require a NEWVOL entry everytime you
needed to
> initialize a tape, it would be easier to keep the *SAME volume ID.  Is
there
a
> good reason why *SAME is not a valid value for the NEWVOL parameter?
>
> Dan Bale
> IT - AS/400
> Handleman Company
> 248-362-4400  Ext. 4952
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---