todsn creates truncated intermediate blocks for recfm=u or v

General discussion of the Co:Z Toolkit
Post Reply
Jeno
Posts: 23
Joined: Wed Oct 03, 2007 5:28 am

todsn creates truncated intermediate blocks for recfm=u or v

Post by Jeno »

Hello,

running coz107, instead of creating half-track blocks, todsn still creates intermediate short blocks. Thus, Writting 8*27920=223360 bytes, an extra 9th block will be created. There seems to be no correlation with the file content. Writting a file containing all 'A' truncates at the same point as a file filled with '00'x...'ff'x.

Here are the first 6 blocks from RECFM=U,BLKSIZE=27998, RECFM=U,BLKSIZE=27920 and RECFM=VB,LRECL=27920,BLKSIZE=27924:

  • >l dump maxlen(32)
    PDS140I DUMP RECORD 1 LENGTH 27,998 TTR 000001
    PDS140I DUMP RECORD 2 LENGTH 27,998 TTR 000002
    PDS140I DUMP RECORD 3 LENGTH 27,998 TTR 000101
    PDS140I DUMP RECORD 4 LENGTH 27,998 TTR 000102
    PDS140I DUMP RECORD 5 LENGTH 19,080 TTR 000201
    PDS140I DUMP RECORD 6 LENGTH 27,998 TTR 000202


    >l dump maxlen(32)
    PDS140I DUMP RECORD 1 LENGTH 27,920 TTR 000001
    PDS140I DUMP RECORD 2 LENGTH 27,920 TTR 000002
    PDS140I DUMP RECORD 3 LENGTH 27,920 TTR 000101
    PDS140I DUMP RECORD 4 LENGTH 27,920 TTR 000102
    PDS140I DUMP RECORD 5 LENGTH 19,392 TTR 000201
    PDS140I DUMP RECORD 6 LENGTH 27,920 TTR 000202


    >L DUMP MAXLEN(16)
    PDS140I DUMP RECORD 1 LENGTH 27,924 TTR 000001
    PDS140I DUMP RECORD 2 LENGTH 27,924 TTR 000002
    PDS140I DUMP RECORD 3 LENGTH 27,924 TTR 000101
    PDS140I DUMP RECORD 4 LENGTH 27,924 TTR 000102
    PDS140I DUMP RECORD 5 LENGTH 19,416 TTR 000201
    PDS140I DUMP RECORD 6 LENGTH 27,924 TTR 000202
In the above cases, a truncation occurs after 131072 bytes written. This is exactlly 128kB that I assume is your buffer size ;)

Hope this makes sense,
best regards and have a nice Week-end
Jenö
dovetail
Site Admin
Posts: 2022
Joined: Thu Jul 29, 2004 12:12 pm

Post by dovetail »

Thanks for reporting this. There is a bug when source lines > 128k are "flowed" into records. As you point out, they are not broken at the maximum record length as they should be.

We will try to address this and fix it asap.
dovetail
Site Admin
Posts: 2022
Joined: Thu Jul 29, 2004 12:12 pm

Post by dovetail »

We have fixed this in the 1.0.8 z/OS maintenance release.

See: http://www.dovetail.com/forum/viewtopic.php?t=695

Thanks for reporting this problem.
Post Reply