× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: tape volume ID
  • From: Chuck Lewis <clewis@xxxxxxxxxx>
  • Date: Mon, 12 Feb 2001 12:47:13 -0500

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
> +---

+---
| 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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

This mailing list archive is Copyright 1997-2024 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].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.