The ZOS File is completely different from the Unix/Linux/Windows file systems.
For the type of processing done on the Mainframe, it is a lot more efficient.
PERFORMANCE - The operating system is optermized for Cobol Batch record orientated
processing. Two obvious advantages
These days this is minor but 50 years ago it was significant.
While there are many other file types than VB/FB on the mainframe, they
In Fixed Block records, all records have exactly the same size
FB File (constant recordlength records, no eol marker) This is Constants.IO_FIXED_LENGTH_RECORDS:
(Record 1 --------------------)
(Record 2 --------------------)
(Record 3 --------------------)
(Record 4 --------------------)
ogically a VB File (length at the start of the record) This is Constants.IO_VB:
(Record Length)(Record 1 ----------------------------)
(Record Length)(Record 2 ----------)
(Record Length)(Record 3 ----------------------)
(Record Length)(Record 4 ---------------)
Physically on a disk a VB file is devided up into blocks so you actually have (Constants.VB_DUMP):
(bdw)(rdw)[record](rdw)[record ](rdw)[record ](rdw)[record ](rdw)[record]
(bdw)(rdw)[record](rdw)[record ](rdw)[record](rdw)[record ](rdw)[record ]
(bdw)(rdw)[record](rdw)[record ](rdw)[record ](rdw)[record ](rdw)[record]
Where
It will depend how you tranmit a VB file wether you get it as
Constants.VB, Constants.VB_DUMP or