The first track would contain the Directory block, the EOF Directory
block, and the rest with PDS data blocks.
On Sun, Nov 17, 2024 at 3:44?PM Andre via groups.io
<procritic@...> wrote:
Well OK, then please provide your calculations concerning this problem.
Why there is free space at the end of PDS dataset that takes more than 2480 bytes?
You have said: " A pds has 256 byte blocks with a gap between each block. Then there is one block that makes end of file of the directory."
There is nothing more far from the truth, you can clearly see in hex dump of DASD that there is no 256 blocks apart from directory one,
No gaps at all. The PDS takes two blocks 27920 bytes each(1 track). Those blocks can have 349 lines of text each,
and this text stored on DASD as is, no gaps included. The only gap is between two blocks and it is 8 bytes.
Andre
On Mon, Nov 18, 2024 at 12:26 AM, laddiehanus wrote:
I have mislead no one. I have been working with this since 1982. There is overhead that can’t be seen with the tools that are publicly available.
Laddie Hanus
--
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?
