Hi all,
I'm looking for a couple of you to test a script I wrote which
transfers,
via FTP/iX, one or more files from a 3000 to another box (Unix, MPE,
Windows). The file is encrypted, and if the remote system is MPE, the
file
is automatically decrypted after the transfer.
Donna has already done the initial user testing (thanks!) and I've made
a couple of changes based on her input. I'd like to upload this script
to Jazz this week, but I first want to make sure it's usable in your
environments.
I'll take the first couple of folks who reply that they'll use it this
week. I'll email it to you as a .txt file, which should be converted
to a fixed/ASCII file (FROMBYTE) once it's on your 3000.
Thanks for your consideration,
Jeff Vance, vCSY
==========================================================
Here's the help text if you just enter the script name without
arguments:
:sftpput
--- SFTPPUT --- version X.08
SFTPPUT transfers one or more files, via FTP/iX, to the specified remote
system. Most commonly the file(s) will be encrypted prior to being
transferred using the POSIX 'crypt' utility.
Usage:
SFTPPUT fileset, remoteSystem, remoteUser, remoteDir,
encrypt, remoteSysType, remSysHasCrypt
where:
'fileset' (required) a single file or wildcarded fileset which can
supplied in MPE or POSIX syntax. Eg. F@, ./f#, /ACCT/dir/f2
'remotesystem' (required) the name or IP address of the system where
the
file is being transferred. The remote system can be all flavors of
Unix, Windows or MPE, as long as the remote system can decrypt
encrypted files via the POSIX crypt utility. The decryption is done
automatically for MPE systems; whereas, non-MPE systems will need
to run the crypt utility using the key which is displayed to
$stdlist.
'remoteuser" - (required) the user name which FTP will use to connect
to
the remote system. The syntax is: "username[:password]" or
"username[/password]". To suppress password prompting the username
should terminate with a ":" or "/", meaning a null password, eg.
'foo:'. For MPE remote systems the username field consists of
"user.account". If passwords are embedded in MPE user names the
format is: "user/upass.acct/apass" or "user.acct:upass,apass". If
all
passwords are omitted the user may be prompted for the passwords.
The expected user response for MPE passwords is:
"userpass,acctpass".
NOTE: the comma form of an MPE password causes quotes to be
required
for this parameter so that it is treated as a single token.
'remotedir' - (optional) the name of the directory (or group.account)
on
the remote system where the file will be sent. Syntax: "/dir",
"./dir" "../dir", "~user", "group.acct", or "group". If omitted
the
remote user's home directory is assumed.
'encrypt' - (optional) TRUE (default) means to encrypt text files.
FALSE
means no encryption. However, even if 'encrypt' is TRUE, only non-
empty ASCII files will be encrypted.
'remoteSysT' - (optional) "MPE/iX", default, means the remote system is
known to be an MPE system. "Unix" means the remote system is known
to
be a Unix system. '*' means the remote system type will be
determined
by this script, which is extra overhead. If the file is encrypted
and
the remote system is MPE system then a job will be streamed on the
remote system to decrypt the file and do some minor cleanup.
'remSysHasCrypt' - (optional) only applies when the remote system is
MPE.
"Y" (default) indicates that the remote system already has the
crypt
utility, and thus it does not need to be FTP'd across the wire. "N"
means the remote MPE system does not have Crypt, in which case, a
non-PH version is FTP'd to the remote system, executed, and then
removed. If the remote system is not MPE this parameter is
ignored.
|