Anonymous | Login | Signup for a new account | 2024-12-10 02:44 CET |
My View | View Issues | Change Log | Roadmap | Search |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
0001000 | FL5 | 1.2 FLCC | public | 2020-06-12 16:54 | 2022-10-28 13:48 | ||||||||
Reporter | Falk Reichbott | ||||||||||||
Assigned To | Falk Reichbott | ||||||||||||
Priority | normal | Severity | feature | Reproducibility | N/A | ||||||||
Status | assigned | Resolution | open | ||||||||||
Platform | System Z | OS | z/OS | OS Version | V2R40 | ||||||||
Product Version | 5.1.22 | ||||||||||||
Target Version | 5.1.29 | Fixed in Version | |||||||||||
Summary | 0001000: Separate logical record format and length from physical (falloc()) at write | ||||||||||||
Description | 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. | ||||||||||||
Tags | No tags attached. | ||||||||||||
Attached Files | |||||||||||||
Notes | |
(0001335) Falk Reichbott (administrator) 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. |
Issue History | |||
Date Modified | Username | Field | Change |
2020-06-12 16:54 | Falk Reichbott | New Issue | |
2020-06-12 16:54 | Falk Reichbott | Status | new => assigned |
2020-06-12 16:54 | Falk Reichbott | Assigned To | => Falk Reichbott |
2020-08-19 16:53 | Falk Reichbott | Target Version | 5.1.23 => 5.1.24 |
2020-09-21 09:12 | Falk Reichbott | Note Added: 0001335 | |
2021-01-22 17:05 | Falk Reichbott | Target Version | 5.1.24 => 5.1.26 |
2021-04-30 12:05 | Falk Reichbott | Target Version | 5.1.26 => 5.1.27 |
2022-03-09 10:43 | Falk Reichbott | Target Version | 5.1.27 => 5.1.28 |
2022-10-28 13:48 | Falk Reichbott | Target Version | 5.1.28 => 5.1.29 |
Copyright © 2000 - 2024 MantisBT Team |