Archive-Date: Mon, 13 Jun 1994 17:08:21 +0000 Subject: TCPware & Teanlinks Message-ID: <771527301snz@hillside.demon.co.uk> From: Robin@hillside.demon.co.uk (Robin Woodward) Date: Mon, 13 Jun 1994 17:08:21 +0000 Reply-To: Robin@hillside.demon.co.uk Sender: usenet@demon.co.uk Is anybody out there running TCPware with Digitals Teamlinks software? If so are there any known problems when setting the environment up as opposed to using TCP/IP services. Thanks -- Robin Woodward Email: Robin@Hillside.demon.co.uk ================================================================================ Archive-Date: Mon, 13 Jun 1994 17:15:40 +0000 Subject: TCPware's FTP file size in blocks/bytes? Message-ID: <771527740snz@hillside.demon.co.uk> From: Robin@hillside.demon.co.uk (Robin Woodward) Date: Mon, 13 Jun 1994 17:15:40 +0000 Reply-To: Robin@hillside.demon.co.uk Sender: usenet@demon.co.uk We have a program on a SUN system that uses FTP to check the size of files on other UNIX and VAX systems. If the file size has changed action is taken. The VAX's run TCPware's FTP module which returns the file size in blocks but all the UNIX systems return file sizes in bytes. The program needs a responce in bytes (like the ls-l command on UNIX) Has anyone got any ideas or overcome this problem before. Any pointers would be much appreciated. -- Robin Woodward Email: Robin@Hillside.demon.co.uk ================================================================================ Archive-Date: XXX, 18 Jun 1994 23:07:01 -0400 From: volz@process.com (Bernie Volz) Subject: Re: TCPware's FTP file size in blocks/bytes? Message-ID: <1994Jun18.230701.551@process.com> Date: 18 Jun 94 23:07:01 -0400 References: <771527740snz@hillside.demon.co.uk> In article <771527740snz@hillside.demon.co.uk>, Robin@hillside.demon.co.uk (Robin Woodward) writes: > We have a program on a SUN system that uses FTP to check the size of files on > other UNIX and VAX systems. If the file size has changed action is taken. > > The VAX's run TCPware's FTP module which returns the file size in blocks > but all the UNIX systems return file sizes in bytes. > > The program needs a responce in bytes (like the ls-l command on UNIX) > > Has anyone got any ideas or overcome this problem before. > > Any pointers would be much appreciated. > > Robin Woodward Email: Robin@Hillside.demon.co.uk One suggestion would be to use NFS. Another advantage of this is that you could look at more than just the file size (date file was modified) which may be much more meaningful than just the size? If you need to stick with FTP, there really isn't anything easy to do (short of writing your own "DIRECTORY" program - FTP uses that to obtain the data). Other "tricks" include actually getting the file (storing it using a temporary name) and comparing the size (or even contents?) on the UNIX system and renaming it to the proper name if it is different. This probably isn't that great an idea if you have LOTS of files or they may be fairly BIG. Hope that provides some help? - Bernie Volz Process Software Corporation ================================================================================ Archive-Date: XXX, 20 Jun 1994 15:09:33 CDT Subject: MX V4.1 is now available! Message-ID: <1994Jun20.150935.11118@netnews.wku.edu> From: goathunter@alpha.wku.edu (Hunter Goatley) Date: 20 Jun 94 15:09:33 CDT Reply-To: goathunter@alpha.wku.edu (Hunter Goatley) Message Exchange (MX) V4.1 is now available. A full description of MX is included below my sig. V4.1 provides more I/O performance enhancements and a few new features. You can get MX via the following channels: WWW: http://www.wku.edu/www/madgoat/madgoat.html FTP: ftp.wku.edu in [.MX.MX041] ftp.spc.edu in [.MX.MX041] E-mail: SEND MX in the body of a mail message to FILESERV@WKUVX1.WKU.EDU Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.WKU.EDU) ------------------------------------------------------------------------------- [20-JUN-1994] Message Exchange V4.1 Message Exchange (MX) is electronic mail software for OpenVMS VAX systems running VMS V5.0 or later, including OpenVMS V6.0, and OpenVMS AXP systems running OpenVMS AXP V1.0 or later. It supports Internet mail over CMU-OpenVMS TCP/IP, VMS/ULTRIX Connection, TGV MultiNet, Process Software's TCPware, and Wollongong's WIN/TCP and PathWay; BITNET mail over Wingra's Jnet; and UUCP mail over DECUS UUCP. Also included is support for SMTP message transfers over DECnet and X.25 (using VAX P.S.I) and support for L-Soft International's LISTSERV software. MX uses VMS Mail for local message entry and delivery, and includes support for mailing lists and mail-based file servers. Features: * Users send and receive messages using VMS MAIL. Support for "signature" files is included in the VMS MAIL interface. Full support for automatic forwarding with the VMS MAIL SET FORWARD command is included. User-defined alias databases for e-mail addresses is supported. Binary files may be sent through MX to other VMS sites running MX, PMDF, or MultiNet. * Provides SMTP (RFC 821) message transfers over CMU-OpenVMS TCP/IP (aka CMU-Tek TCP/IP), DEC TCP/IP Services for OpenVMS (aka VMS/ULTRIX Connection), TGV MultiNet, TCPware from Process Software, and PathWay and WIN/TCP from Wollongong. Includes support for Internet domain system MX records. Also supports SMTP over DECnet and X.25 (using VAX P.S.I.). * Provides BSMTP message transfers with other BITNET mailers over Jnet, compatible with the CU Mailer package for VM systems. Fully supports BITNET-Internet gateways for non-Internet-connected systems. When combined with the SMTP support, can also provide a BITNET/Internet gateway service. * Interfaces with DECUS UUCP to provide a single mail interface to all mail protocols. Can also gateway between UUCP and other networks. (Not supported under OpenVMS AXP yet because DECUS UUCP has not been ported to AXP yet.) * Provides a mailing list processor with automatic subscription requests. Mailing lists can be configured to restrict postings only to subscribers or list owners, and to restrict the automatic subscription handling. Internet mailing list conventions and a subset of LISTSERV commands are supported. * Supports one or more file servers that can be set up by the system manager to handle automatic distribution of packages of files using mail as the distribution medium. Large transfers can be deferred to off-hours, and daily per-user, per-system, and/or per-server limits can be placed on each server. * Provides interfaces for a site-provided custom mail transport and custom address processing routines. * Provides its own message queueing subsystem. RMS block I/O is used to provide extremely fast queue access with little overhead. Files in this directory: ------------------------ MX041.ZIP The installation kits for MX V4.1 (for use with VMSINSTAL). MX041_SRC.ZIP Source code, in a compressed Zip file. MX041_DOCS_ONLY.ZIP The MX041.K saveset containing the docs. This separate .ZIP file is provided for those who want to start with just the docs. NOTE: The K saveset of the installation kit contains the documentation for MX in PostScript, Bookreader, and plain ASCII formats. <<< You will need the UNZIP program in the [ANONYMOUS.VMS] directory >>> <<< to expand the compressed files. >>> -------------------------------------------------------------------------------- CONTACTING THE AUTHORS Comments, suggestions, and questions about this software can be directed to the current maintainer at one of the following addresses: Mail: Hunter Goatley Western Kentucky University Academic Computing, STH 226 Bowling Green, KY 421201 E-mail: goathunter@WKUVX1.WKU.EDU Phone: 502-745-5251 (e-mail is preferred) The original author of MX is Matthew D. Madison: Mail: Matthew Madison TGV, Inc. E-Mail: (Internet) madison@tgv.com A mailing list for additional support of MX exists. To subscribe, send the following command in the body of a mail message to MXserver@WKUVX1.WKU.EDU: SUBSCRIBE MX-List "Your real name here" The MX-List mailing list is gatewayed to the vmsnet.mail.mx newsgroup. ------------------------------------------------------------------------------- COPYRIGHT NOTICE This software is COPYRIGHT © 1993, 1994, MadGoat Software. ALL RIGHTS RESERVED. Permission is granted to copy and redistribute this software for no commercial gain, providing all copyright notices remain intact. DISCLAIMER This software is provided "AS IS". The authors and their respective employers disclaim all warranties on the software, including without limitation, all implied warranties of merchantability and fitness.