|
|
* 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 |
|