I used RSCS's UFT clients, but had trouble with its server mode, so the
receiving server is the UFTD code in a separate SVM. The command I use
to send a file is:
'EXEC SENDFILE' FN FT FM 'TO' TUSER 'AT 10.0.10.202 ( UFTASYNC NETDATA'
The TCPIP DATA file has this entry: UFTSERVERID RSCS
The setup of the UFTD svm is very simple, setup the PROFILE TCPIP to
reserve the port: 608 TCP UFTD ; UFT Server
Now, my day-to-day needs for Sift/UFTD is between two LPARs on our z890
so it goes across a hypersocket. But I will have to deal with a remote
system eventually and would like to see ALL extra-system communications
include an encryption capability.
/Tom Kern
Rick Troth wrote:
Sift/UFT is another node-to-node transfer mechanism
that leaves the object in the target rdr in a NETDATA format
so it can be received with proper recfm/lrecl/datestamp.
What Tom said.
I don't know the IBM implementation of UFT in VM TCP/IP well,
but I believe it does have a client (SENDFILE) and a server (UFTD).
The older UFTD could easily be listed in SYSTEM NETID
or would even go so far (if priv'd) to fake file origin as RSCS.
Barring direct UFT availability (no UFTD on the receiving end),
SENDFILE allows "ASYNC", but that still requires special queueing
on the sending end. I don't believe the original functionality
is there (to send a file in NETDATA format as a MIME attachment).
May have to dig-up some of the old code.
-- R; <><
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
