Bruce Crabill <BRUCE@UMDD.bitnet> (02/26/90)
I've cleaned up the UMDTCP files on our LISTSERV. I have created two
packages NETPRINT and TCPTEST. With these, a requestor may get all
the files related with NETPRINT using:
TELL LISTSERV AT UMDD SEND NETPRINT PACKAGE
or all the files related with TCPTEST and UDPTEST using:
TELL LISTSERV AT UMDD SEND TCPTEST PACKAGE
To make it less confusing for the FAL users (which I will admit out number
the UMDWISC users), the modules sent in the packages are the FAL versioned
modules. UMDWISC users will need to additionally request NETPRINT UMDWISC,
TCPTEST UMDWISC, and UDPTEST UMDWISC and rename them to NETPRINT MODULE,
TCPTEST MODULE, and UDPTEST MODULE when they are received.
To refresh your memory as to our offerings:
NETPRINT - A program that will allow CMS users to print files
to TCP/IP attached printers. It supports the LPR,
MDQS and NDQS protocols.
TCPTEST - A program that performs various testing functions
using TCP. May be used to generate and/or receive
TCP data while collecting performance numbers.
UDPTEST - A program that performs various testing functions
using UDP. May be used to generate and/or receive
UDP data while collecting performance numbers.
All the files on LISTSERV have been refreshed to the current versions that
I have. For the most part, there haven't been any exciting changes, with
the exception that TCPTEST will now use TcpFSend and TcpFReceive in the
FAL version (the NOFRTNS options will cause it to use the older TcpSend
and TcpReceive routines).
Bruce