× 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.


  1.  Home
  2. MIDRANGE-L
  3. September 2011

Re: What do I set the block size to on virtual tape to dup to LTO3?

Rob,

Just to confirm, Did you right click on "Tape Resources" or in Tapgrt03?

On the other hand, as soon as we are taking about LTO3 compatible devices
here, wouldn't *VRT256K apply to your case as well?

Regards,

Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries
--



On Tue, Sep 6, 2011 at 2:45 PM, <rob@xxxxxxxxx> wrote:

I don't see that in my iNav. Libraries are different. I see that in Stand
Alone devices.

image pasted, thus BCC to your personal address.


Rob Berendt
--
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: Luis Rodriguez <luisro58@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 09/06/2011 03:08 PM
Subject: Re: What do I set the block size to on virtual tape to
dup to LTO3?
Sent by: midrange-l-bounces@xxxxxxxxxxxx
------------------------------



Rob,

I'm afraid that we don't have tape libs here but, for our single LTO-3, in
the "properties" window, on the third tab ("Capabilities"?) it shows
"Densities and capabilities supported" (loose translation). In the info I
have it shows, for say, *ULTRIUM3:
Optimal Block Size: 262144.
Max Block Size: 262144


So, according to the TechDoc, the block size should be *VRT256K (262,144
bytes):
---
Volumes with a density of *VRT256K use an optimum block size of 256KB and
are compatible with 35xx type devices and the newer QIC tape devices.
---


HTH,


Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries
--



On Tue, Sep 6, 2011 at 1:30 PM, <rob@xxxxxxxxx> wrote:

I tried the iNav hint and got no information.


Rob Berendt
--
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: Luis Rodriguez <luisro58@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 09/06/2011 01:47 PM
Subject: Re: What do I set the block size to on virtual tape to
dup
to LTO3?
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Rob,

I'm afraid that I cannot help you directly on this, but on my "tips"
library
I have filed the following IBM TechDoc:

*Using Virtual Tape on the IBM System i5*



https://www-304.ibm.com/support/docview.wss?uid=nas1a370fba852b0d20f862571240067973e


Tiny URL:
http://tinyurl.com/3k25rqx


Which states:

*Density

The density (format) parameter limits the block size that can be written
to
a virtual tape volume so that the volume will be compatible for
duplication
to your physical tape device.

o

Volumes with a density of *VRT256K use an optimum block size of 256KB and
are compatible with 35xx type devices and the newer QIC tape devices.

o

Volumes with a density of *VRT240K use an optimum block size of 240KB and
are compatible with VXA and 8mm technology devices and the 35xx and newer
QIC devices.

o

Volumes with a density of *VRT64K use an optimum block size of 64KB and
are
compatible with 3490F Model 18 track media, VXA and 8mm technology
devices,
and with the 35xx and newer QIC devices.

o

Volumes with a density of *VRT32K do not use an optimum block size and
are
compatible with all devices.

The virtual tape media cannot be copied to physical media if you choose
an
incompatible block size. Ensure a virtual tape density with a block size
that is compatible with the physical tape devices on your system is
selected
by performing one of the following:

o

In iSeries Navigator, expand Configuration and Service > Hardware > Tape
Devices > Tape Libraries > Tape Resources for tape library devices. Next,
right click on the device that you want to view and select Properties to
display the supported block sizes for your tape device.

o

In iSeries Navigator, expand Configuration and Service > Hardware > Tape
Devices > Stand-Alone Devices for stand alone tape devices. Next, right
click on the device that you want to view and select Properties to
display
the supported block sizes for your tape device.

o

Save a small library to your physical tape drive with the USEOPTBLK
parameter set to *YES. Type DSPTAP DATA(*LABELS) in the command line, and
use the Block Length field to see the block size that was used.

HTH,

o In iSeries Navigator, expand Configuration and Service > Hardware >
Tape
Devices > Tape Libraries > Tape Resources for tape library devices. Next,
right click on the device that you want to view and select Properties to
display the supported block sizes for your tape device. o In iSeries
Navigator, expand Configuration and Service > Hardware > Tape Devices
Stand-Alone
Devices for stand alone tape devices. Next, right click on the device
that
you want to view and select Properties to display the supported block
sizes
for your tape device. o Save a small library to your physical tape drive
with the USEOPTBLK parameter set to *YES. Type DSPTAP DATA(*LABELS) in
the
command line, and use the Block Length field to see the block size that
was
used.
*
Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries
--



On Tue, Sep 6, 2011 at 10:36 AM, <rob@xxxxxxxxx> wrote:

What do I set the block size to on virtual tape to dup to LTO3?

3573 or 3576 will be the physical drives.


Rob Berendt
--
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

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l
.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l

or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.




As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
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.