Radoslaw, Each block of data your application writes to tape gets a block ID
assigned from the tape hardware. While the block count is simply a
sequential counter of blocks written, the block ID includes information that
helps the hardware identify the actual physical position on the tape. Some
ins
W dniu 2011-06-23 18:23, Mike Wood pisze:
Radoslaw, The block count is now split between 2 fields in the data set
trailer label. 10 bytes in total (IBM SL). Limit used to be 99, now you
get 10 digit limit.
So, it depends on the block size and media capacity when the limit is
reached. The lab
Radoslaw, The block count is now split between 2 fields in the data set
trailer label. 10 bytes in total (IBM SL). Limit used to be 99, now you
get 10 digit limit.
So, it depends on the block size and media capacity when the limit is
reached. The label standard changed some time ago and DFSMS
On 6/21/2011 10:51 AM, Minoru Massaki wrote:
> As Mike told, in real 3490E, block count in block ID (32-bits) is 22-bits
> long.
> High order 10-bits in 3490E block ID is used other purpose.
> In case of 3590 as well as 3592, the block count is 32-bits long.
>
> But in 3490E emulation mode of 35
Well, now I recall the limitation was related to block count.
However I still see no reason why it's a problem for STK T1 but not
for emulated drives. From operating system point of view it should be no
difference between real and emulated drive!
Mike wrote "Depending on how the data is accesse
As Mike told, in real 3490E, block count in block ID (32-bits) is 22-bits long.
High order 10-bits in 3490E block ID is used other purpose.
In case of 3590 as well as 3592, the block count is 32-bits long.
But in 3490E emulation mode of 3590/3592, you can use 32-bits block count.
I think that ST
Radoslaw, I believe the 'limit' that most likely causes problems is the
block ID.
3490/3590 devices use different formats. If you look at the doc for the NOTE
and POINT macros for sequential data sets in DFSMS pubs you will get some
idea of the differences.
Basically, the 3490 blkid limited the num
W dniu 2011-06-20 19:15, Mike Schwab pisze:
I know our STK9840C 40GB drives were defined as IBM 3590.
That's OK, but (at least for 9840A and B) you could define them as 3490
as well. Also other types of hardware and emulated tape drives do offer
such definition.
However my question just out
2011/6/20 R.S. :
> First, I'm talking about emulation, not about real drives.
>
> Many "modern" (that means: newer than 3490E) drives are defined in IODF as
> UNIT=3490. That covers both real and emulated tape drives. Usually volume
> size for such tape drives is bigger than original ECCST (cartrid
I know our STK9840C 40GB drives were defined as IBM 3590.
2011/6/20 R.S. :
> First, I'm talking about emulation, not about real drives.
>
> Many "modern" (that means: newer than 3490E) drives are defined in IODF as
> UNIT=3490. That covers both real and emulated tape drives. Usually volume
> size
First, I'm talking about emulation, not about real drives.
Many "modern" (that means: newer than 3490E) drives are defined in IODF
as UNIT=3490. That covers both real and emulated tape drives. Usually
volume size for such tape drives is bigger than original ECCST
(cartridge used in 3490E).
I
11 matches
Mail list logo
