FLAM Issue Tracker - FL5
View Issue Details
0000658FL52.2 Subprogram FLUC (CONV)public2015-03-12 14:432016-08-18 10:43
Falk Reichbott 
Tilo Eckert 
0000658: Write converted data of FLUC direct with SSH to remote system
A customer use secure copy (ssh scp) to copy data from USS to distributed systems. These data are currently converted with a lot of tools an own written programs. All these conversions can be done with FLUC in one step. The requirement is now, if FLAM can support also the last step, means the scp to the over platform.
No tags attached.
Issue History
2015-03-12 14:43Falk ReichbottNew Issue
2015-03-12 14:43Falk ReichbottStatusnew => assigned
2015-03-12 14:43Falk ReichbottAssigned To => Ulrich Schwab
2015-03-16 17:57Falk ReichbottSummaryWrite converted data of FLUC direct to secure copy => Write converted data of FLUC direct with SSH to remote system
2015-03-16 17:57Falk ReichbottDescription Updatedbug_revision_view_page.php?rev_id=215#r215
2015-03-16 18:04Falk ReichbottNote Added: 0000769
2015-06-29 10:17Falk ReichbottTarget Version5.2 => 5.1
2015-07-09 18:46Falk ReichbottTarget Version5.1 => 5.1.09
2015-08-13 18:47Falk ReichbottTarget Version5.1.09 => 5.1.11
2015-10-29 10:06Falk ReichbottAssigned ToUlrich Schwab => Tilo Eckert
2015-12-07 08:29Falk ReichbottTarget Version5.1.11 => 5.1.12
2016-05-12 18:44Falk ReichbottTarget Version5.1.12 => 5.1.13
2016-08-18 10:43Falk ReichbottNote Added: 0001018
2016-08-18 10:43Falk ReichbottStatusassigned => resolved
2016-08-18 10:43Falk ReichbottFixed in Version => 5.1.13
2016-08-18 10:43Falk ReichbottResolutionopen => fixed

Falk Reichbott   
2015-03-16 18:04   
This requirement can be realised with the SSH SFTP interface. A integration in FIOBLK, FIOTXT and FIOREC is possible. A integration in FIOFL4 requires an own deticated User-IO (Device 8) in the FLAM4 kernel.The support for FLAMFILEs can be implemented later.

The senario of the customer use only FIOBLK to read and write open formats from and to remote systems. Means a extension of FIOBLK will be enoght in this case.

The directory support at read (wildcards) and write (creat directories) can also be exteneted with the integration of the SSH library.

Target revision for this support will be 5.1.7 (around september 2015)
Falk Reichbott   
2016-08-18 10:43   
* The communication parameters can be specified via properties (net.ssh() object) or as part of the URL (see below)
* Supports public key (if no password given) or password authentication
* Record oriented datasets are written remotely like the record I/O works on Windows and Unix systems
* URL prefix: file='ssh://user:password@hostname:port//path/file.xxx' [^]
** The ssh:// prefix indicates remote access to via SSH
** The user is optional, the default is the current login user ID
*** e.g. name='ssh://:password@hostname/path/file.xxx' [^]
** You can use replacements in the connection parameter
*** e.g. file='ssh://<cuser>@hostname//~/myfile.txt [^]
**** <cuser> are replaced with lower case login user id
**** ~ are replaced with the local home directory, which must available also on host side in this case
** The password is optional, the default is public key authentication
*** e.g. name='ssh://hostname//path/file.*/?*/member.*' [^]
** The hostname is mandatory
** The port is optional, the default is 22
** Host and remote file path are separated by a slash
** Absolute paths require another slash (i.e. // after the hostname)
*** Otherwise, the path is relative to the current directory after login to the SSH server
* Currently FLAM4FILEs are not supported (special user I/O required, will be supported later)
* Static allocations (DD:NAME) are not supported with remote access
* All other kind of files (log, info, report, ....) except the invers command file used in the command syntax are also supported with SSH (URL only, no properties)
* Only files of the command line executer (configuration, properties, trace, inverse, ...) must be locally