My enhancement request suggested to writing until EOV, then back up to the 
beginning of that VM:Backup domain, close the tape (with all the usual 
EOV, and cross-linked User Header and Trailer Labels), and re-write that 
domain on the fresh tape.  It got more complex when a single domain would 
not fit on a single tape, but with newer tape technologies that may no 
longer be a significant problem.  Food for fresh thoughts.

Mike Walter 
Hewitt Associates 
Any opinions expressed herein are mine alone and do not necessarily 
represent the opinions or policies of Hewitt Associates.




"Stracka, James (GTS)" <[EMAIL PROTECTED]> 

Sent by: "The IBM z/VM Operating System" <[email protected]>
06/06/2008 10:35 AM
Please respond to
"The IBM z/VM Operating System" <[email protected]>



To
[email protected]
cc

Subject
Re: Backup: Twinning Tapes to Remote Tape Unit






Now that is interesting.  How does that OS/390 utility know where the
EOT reflector is located unless it spins the entire tape first?

-----Original Message-----
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of McKown, John
Sent: Friday, June 06, 2008 9:48 AM
To: [email protected]
Subject: Re: Backup: Twinning Tapes to Remote Tape Unit


Curiousity question, because I don't know VM:Backup, is there a way to
tell VM:Backup to only use n% of a tape? Our z/OS backup utility can be
told to do this. If this is possible, then you could fill a tape up to,
say, 80% and be fairly confident that the second tape would be long
enough to hold that data.
--------------------------------------------------------

This message w/attachments (message) may be privileged, confidential or 
proprietary, and if you are not an intended recipient, please notify the 
sender, do not use or share it and delete it. Unless specifically 
indicated, this message is not an offer to sell or a solicitation of any 
investment products or other financial product or service, an official 
confirmation of any transaction, or an official statement of Merrill 
Lynch. Subject to applicable law, Merrill Lynch may monitor, review and 
retain e-communications (EC) traveling through its networks/systems. The 
laws of the country of each sender/recipient may impact the handling of 
EC, and EC may be archived, supervised and produced in countries other 
than the country in which you are located. This message cannot be 
guaranteed to be secure or error-free. This message is subject to terms 
available at the following link: http://www.ml.com/e-communications_terms/
. By messaging with Merrill Lynch you consent to the foregoing.
--------------------------------------------------------




The information contained in this e-mail and any accompanying documents may 
contain information that is confidential or otherwise protected from 
disclosure. If you are not the intended recipient of this message, or if this 
message has been addressed to you in error, please immediately alert the sender 
by reply e-mail and then delete this message, including any attachments. Any 
dissemination, distribution or other use of the contents of this message by 
anyone other than the intended recipient is strictly prohibited. All messages 
sent to and from this e-mail address may be monitored as permitted by 
applicable law and regulations to ensure compliance with our internal policies 
and to protect our business. E-mails are not secure and cannot be guaranteed to 
be error free as they can be intercepted, amended, lost or destroyed, or 
contain viruses. You are deemed to have accepted these risks if you communicate 
with us by e-mail. 


Reply via email to