Thompson, Steve (SCI TW) wrote:
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of R.S.
Sent: Monday, August 28, 2006 2:47 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: JCL - Copy Tape
Thompson, Steve (SCI TW) wrote:
How did this tape get created? Was it created on a VSE system? If so
not
all of the label information is filled out and so *YOU* have to supply
the actual physical record size (BLKSIZE) along with the other DCB
info.
UNLESS you are using LBI. In that case, the "LEGACY" BLKSIZE will be 0
but the "new" data areas will be filled out.
AFAIR the LBI does NOT change the meaning of existing fields. It simply
*adds* new field (previously unused) as high-order bytes for BLKSIZE. So
existing block size field still has a meaningful value.
<snip>
We have one guy who has been doing LBI and "huge" block/record support
(I forgot the tech name for this). From his perspective it isn't that
simple. He has seen the BLKSIZE field of the label be H'0' and then the
new fields now contain data. This is probably going to have to mature a
bit.
I was wrong. I confused block count field of HDR1/EOF1/EOV1 with block
size field of HDR2/EOF2/EOV2. Indeed, zero's means you should read bytes
71-80 for block size. BTW: ADRDSSU does not use LBI, but writes 64kB
blocks. It always sets block size as 0. That's why ADRDSSU dumps cannot
be copied using "legal" methods, like IEBGENER.
--
Radoslaw Skorupka
Lodz, Poland
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
