FLAM Issue Tracker - FL5
View Issue Details
0000831FL52.2 Subprogram FLUC (CONV)public2016-11-07 09:112016-11-16 09:13
Falk Reichbott 
Falk Reichbott 
normalfeatureN/A
resolvedfixed 
GeneralGeneralGeneral
5.1.13 
5.1.145.1.14 
0000831: Support of more then one write target after conversion
If a file was converted it would be useful to write it to different targets (locally, remote and for ackup purpose).

It makes no sense to convert a file x times to write it to x targets.

The FIO components must support at write an array of net objects and file name strings.
No tags attached.
related to 0000832resolved Falk Reichbott Support more than one write (CONV) or output (XCNV) specification 
Issue History
2016-11-07 09:11Falk ReichbottNew Issue
2016-11-07 09:11Falk ReichbottStatusnew => assigned
2016-11-07 09:11Falk ReichbottAssigned To => Falk Reichbott
2016-11-07 09:36Falk ReichbottRelationship addedrelated to 0000832
2016-11-16 09:13Falk ReichbottNote Added: 0001039
2016-11-16 09:13Falk ReichbottStatusassigned => resolved
2016-11-16 09:13Falk ReichbottFixed in Version => 5.1.14
2016-11-16 09:13Falk ReichbottResolutionopen => fixed

Notes
(0001039)
Falk Reichbott   
2016-11-16 09:13   
The FIO overlay at output you can now be define up to 4 write spezifications within the XCNV command. This means that you can write your converted data to 4 different targets. For example. If you have create a PGP file, you can store this locally on your side, stored the same PGP file per SSH on a remote system and as member of a ZIP or FLAM archive for backup purpose in one step.

flcl xcnv "inp(sav.fil(fio.txt(name='../input/idat/s*.txt')))out(sav.fil(fmt.txt() cnv.chr() cnv.gzp() fio[fl4(name='./output/odat/txtgzp.ad1')zip(name='ssh://<cuser>@192.168.85.22/tst/FL5/ssh/linx32d0/odat/txtgzp.zip' [^])fl4(name='./output/odat/txtgzp.ad2')] fio.blk(name='ssh://<cuser>:limes@192.168.85.169/tst/FL5/ssh/linx32d0/odat/txtgzp.bin' [^])))"