FLAM Issue Tracker - FL5
View Issue Details
0001000FL51.2 FLCCpublic2020-06-12 16:542022-10-28 13:48
Falk Reichbott 
Falk Reichbott 
System Zz/OSV2R40
0001000: Separate logical record format and length from physical (falloc()) at write
At write it would be usefule, that the FALLOC descripts the physical file and DSORG/RECF/RECL on the base level descript the logical file written. The parameter are the default for falloc if falloc not defined, this means that the logical DCBs are also the physical DCBs at default. So the syntax for read.record() are identical with write.record() and the falloc object are only an additional object which could define, if the logical and physical view differs.
No tags attached.
Issue History
2020-06-12 16:54Falk ReichbottNew Issue
2020-06-12 16:54Falk ReichbottStatusnew => assigned
2020-06-12 16:54Falk ReichbottAssigned To => Falk Reichbott
2020-08-19 16:53Falk ReichbottTarget Version5.1.23 => 5.1.24
2020-09-21 09:12Falk ReichbottNote Added: 0001335
2021-01-22 17:05Falk ReichbottTarget Version5.1.24 => 5.1.26
2021-04-30 12:05Falk ReichbottTarget Version5.1.26 => 5.1.27
2022-03-09 10:43Falk ReichbottTarget Version5.1.27 => 5.1.28
2022-10-28 13:48Falk ReichbottTarget Version5.1.28 => 5.1.29

Falk Reichbott   
2020-09-21 09:12   
This requirement is really helpful but we can not solve this backward compatible. With the best solution the FALLOC() object is a replacement of the static allocation, which describts the physical file format and the new file organization, record format and record length defines the logical format written to the physical file and if no physical definition done, then the logical will be use for the physical as default. This was the plan, but for all customers using static allocation for the physical representation and the FALLOC() object to describ the logical, this solution will not backward compatible and all these job steps needs to be adjusted, because of the behavior change of the FALLOC() object.