FLAM Issue Tracker - FL5
View Issue Details
0000912FL54. Element, Byte, Record or other APIpublic2018-03-05 08:032018-08-01 08:39
Falk Reichbott 
Falk Reichbott 
0000912: Support multiple writes on the byte interface
The multiple writes (and outputs) known form the UP and FLCL untility are also useful on the byte, records and stream interfaces.

Esspecially the flucFS and z/OS subsystem will have advantage of this.

The data is read from memory and neutralized once and can then multiple times written to files or other targets.
No tags attached.
related to 0000888resolved Ulrich Schwab Support an application transparent file conversion, compression and encryption solution like z/OS-Subsys for open systems 
Issue History
2018-03-05 08:03Falk ReichbottNew Issue
2018-03-05 08:03Falk ReichbottStatusnew => assigned
2018-03-05 08:03Falk ReichbottAssigned To => Falk Reichbott
2018-03-08 18:48Falk ReichbottRelationship addedrelated to 0000888
2018-08-01 08:39Falk ReichbottNote Added: 0001162
2018-08-01 08:39Falk ReichbottStatusassigned => resolved
2018-08-01 08:39Falk ReichbottFixed in Version => 5.1.18
2018-08-01 08:39Falk ReichbottResolutionopen => fixed

Falk Reichbott   
2018-08-01 08:39   
All memory to file APIs which are used to write original data, supporting now multiple write overlays or output objects.

This is useful to write the same data in different formats in one step to different files. For example: The same Text is written in UTF-8 with 0x0A as delimiter to a GZIP file for UNIX, in CP1252 with 0x0D0A to a ZIP-Archive for Windows and another one in EBCDIC (IBM1141) as record (no delimiter) to a FLAM archive for z/OS.