Archive-Date: XXX, 1 Jun 1995 00:01:30 -0400 Subject: Re: DECMessageQ(AXP) and TCPware? Message-ID: <1995Jun1.000130@process.com> From: volz@process.com (Bernie Volz) Date: 1 Jun 95 00:01:30 -0400 References: <3qhs0f$383@ftp.space.net> In article <3qhs0f$383@ftp.space.net>, Joerg Ziegler writes: > Need some help, > > the environment: > > AXP/OpenVMS > TCPware from Process Software Corp. (Version 4.1-2) > DECMessageQ V2.0 > > In DECMessageQ there where supported UCX and Multinet, but we've > heard about that some people runs also successfully with TCPware. > > What have we done: > > We've placed the TCPware's UCX$IPC.OLB and UCX$IPC_SHR.EXE > to sys$common:[syslib] and then > We've modified DMQ$EXE:DMQ$UCX_TCPIP_LD.LNK to generate the link > driver for TCPware, this works successfully. > > But when starting DECMessageQ we receive for the link driver: > > TCPIP_LINK_DRIVER 31-MAY-1995 08:24:44.39 E Failed to start network listener > %SYSTEM-E-BADESCAPE, syntax error in escape sequence. > > We've heard about some inconsistence in UCX emulation within TCPware > for prior version. > > Anybody also running this Configuration? > Anybody knows what to check? > Which version of TCPware is required? > Haven't tried DECmessageQ myself. SS$_BADESCAPE is not a status code that the TCPware drivers use or return, especially BGDRIVER. If one might assume that the status being signalled by DECmessageQ is bogus (it is signalling an "errno" like value instead), then 60 (SS$_BADESCAPE value) maps to ETIMEDOUT (Connection timed out). This doesn't help much since that doesn't make sense for a "network listener" since it just accepts connections; doesn't establish them. I'd suggest upgrading to TCPware V4.1-3 since it has some enhancements to the UCX support over and above what V4.1-2 had. I'll make sure our support group has this so that they might be able to follow up with more details on using DECmessageQ. - Bernie Volz Process Software Corporation ================================================================================ Archive-Date: XXX, 2 Jun 1995 12:41:48 -0400 Subject: TCP/IP Sniffer software Message-ID: <3qnf0c$q32@newsbf02.news.aol.com> From: rlatham338@aol.com (RLatham338) Date: 2 Jun 1995 12:41:48 -0400 Reply-To: rlatham338@aol.com (RLatham338) Sender: root@newsbf02.news.aol.com Looking for TCP/IP sniffer software that can run on a e-net connected dos pc....need something that will just log traffic on segment......anything else will be a plus. ================================================================================ Archive-Date: XXX, 2 Jun 1995 23:33:26 -0400 Subject: Re: TCP/IP Sniffer software Message-ID: <1995Jun2.233326@process.com> From: volz@process.com (Bernie Volz) Date: 2 Jun 95 23:33:26 -0400 References: <3qnf0c$q32@newsbf02.news.aol.com> In article <3qnf0c$q32@newsbf02.news.aol.com>, rlatham338@aol.com (RLatham338) writes: > Looking for TCP/IP sniffer software that can run on a e-net connected dos > pc....need something that will just log traffic on segment......anything > else will be a plus. FTP Software makes a LAN Analyzer product. There are others as well, but don't recall them off-hand. - Bernie Volz Process Software Corporation ================================================================================ Archive-Date: XXX, 5 Jun 1995 17:43:06 GMT Subject: Re: Request info on TCP/IP solutions for VMS Message-ID: <3qvfna$51k@fnnews.fnal.gov> From: morphis@fnalv1.fnal.gov Date: 5 Jun 1995 17:43:06 GMT Reply-To: morphis@fnalv1.fnal.gov References: <3qfv75$95q@aplinfo.jhuapl.edu> In article <3qfv75$95q@aplinfo.jhuapl.edu>, humesdg1@aplcomm.jhuapl.edu (David G. Humes) writes: >Greetings, > >I need to provide TCP/IP connectivity for a small number of VMS systems and >am looking for recommendations for appropriate products. We have used KiNet [snip] >Our TCP/IP connectivity requirements are fairly minimal. We need to be >able to transfer files between the UNIX and VMS systems and would like the >software to be able to handle file and data format conversions. Also we need >to be able to log into the VMS systems from the UNIX hosts and vice versa. >Any recommendations, good or bad, would be most appreciated. Did you get any response? Thre is some debate along these lines in comp.os.vms right now. I haven't heard that much about file and data format conversions, I think that is much more of a VMS issue than a tcpip issue. my interpertation of what I have read: UCX suffers somewhat in the r-utilites area, but if all you want is telnet it is sufficient. smtp sucks, but mx is available and easy to deal with. I personally happen to like UCX's command interface, more VMSish than multinet's. FTP has improved and seems pretty good Multinet good all around product, tends to be more unixish than UCX. Highly favored by those who use it. Wollogon?'s offering (I forgot it's name) used to be considered a dog (though not as bad as UCX used to be) I haven't really heard anything lately. cmu's tcpip free! unsupported, a bit buggy Proccess software's offering (tcpware?) modular, so it may be cheaper if you have limited needs. Seems to be a quality product. Well hopefully, this has been of some use, remember this is an off the top of my head report of what I have read of other peoples opinions. Rpobert Morphis >Dave Humes >> humesdg1@aplcomm.jhuapl.edu << ================================================================================ Archive-Date: XXX, 6 Jun 1995 17:40:58 GMT Subject: Re: How to get a VAX on the net Message-ID: <3r23va$4jq@nntpd.lkg.dec.com> From: Steve Huston Date: 6 Jun 1995 17:40:58 GMT References: <19950605.171841.05@home.foobar.co.uk> Bryan Wells wrote: > The equipment I have access to is : > > VAX 4100 - 100A running OpenVMS 5.2 > DecServer 300 > Tricom Office Server 400 > Hays compatible 14400 baud modem. (snip) > Would I need any extra software, and if so where do I get it. Yes, you need extra software. You need at least a TCP/IP package on the VAX. Depending on what you want to set up, you may need a newer DECserver (I'm not familiar with the IP capabilities of the 300). I'm not familiar with the Tricom Office Server 400, so I'm not sure how that plays. But you'll definitely need TCP/IP software for your VAX. > Is the standard VMS mail capable of internet mailing? (SMTP) No, not by itself. However, most of the TCP/IP packages "hook" into the VMS mail system to enable you to use the regular mail commands to send and receive internet mail - check with vendors of the software to make sure it'll work. There are a number of good ones - TCPware, Multinet are good - there are others, no doubt you'll get some followups or mail from your note. Steve Huston Blue Sky Software Corporation TCP/IP, CORBA, DCE applications and consulting ================================================================================ Archive-Date: XXX, 7 Jun 1995 07:00:59 +1000 Subject: Re: Request info on TCP/IP solutions for VMS Message-ID: <1995Jun7.070059.468@fac> From: wayne@fac.cabot.nf.ca Date: 7 Jun 95 07:00:59 +1000 References: <3qfv75$95q@aplinfo.jhuapl.edu> In article <3qfv75$95q@aplinfo.jhuapl.edu>, humesdg1@aplcomm.jhuapl.edu (David G. Humes) writes: > Greetings, > > I need to provide TCP/IP connectivity for a small number of VMS systems and > am looking for recommendations for appropriate products. We have used KiNet > from Ki Research previously to allow a UNIX host to become a DECNet node, > but now that the majority of our network is TCP/IP it would make more sense > to make our VMS systems TCP/IP hosts. The VMS systems are VAX 8550s that > are currently running VMS 5.5 and are likely to be frozen at 5.5 due to > software that is not supported at higher levels. Our UNIX hosts are Sun or > Sun equivalent systems running SunOS 4.1.3 and we have no immediate plans to > migrate to Solaris 2+. > > Our TCP/IP connectivity requirements are fairly minimal. We need to be > able to transfer files between the UNIX and VMS systems and would like the > software to be able to handle file and data format conversions. Also we need > to be able to log into the VMS systems from the UNIX hosts and vice versa. > Any recommendations, good or bad, would be most appreciated. > > =========================================================================== > Dave Humes >> humesdg1@aplcomm.jhuapl.edu << > =========================================================================== > > > I run TGV's multinet on a number of VAXes running VMS and I find TGV to be excellent. An indication of it's quality is that I do many of the system management/network management duties on these vaxes and I do not have the first iota of a clue as to how to use TGV Multinet. YOu just install it, and it keeps running with VERY little intervention by the sysop. It functions as a POP server, NFS server, in addition to your stated requirements and them some. I would not look any further than TGV for a VMS-based tcpip solution. -- Wayne Hann, Manager, Information Systems Cabot College of App. Arts, Tech & Cont. Ed. St. John's, Nf Canada A1C 5P7 Tel: (709) 758-7005 / Fax: (709) 758-7052 / Email:whann@admin.cabot.nf.ca ================================================================================ Archive-Date: Thu, 08 Jun 1995 10:11:41 PDT Subject: X-Window bandwidth stats. Message-ID: <3r70se$6q7@enterprise.osd.mil> From: Bill Lakner Date: Thu, 08 Jun 95 10:11:41 PDT Content-Type: TEXT/PLAIN; charset=US-ASCII Hello, does anyone know (or have sources for) bandwith usage by typical X-Window sessions? We are in the preliminary design phase for a WAN which will utilize X-Window apps. remotely over the links and need to understand what we're dealing with. Many Thanks in advance. ----------------------------------------------------------- Bill Lakner DynCorp ================================================================================ Archive-Date: XXX, 7 Jun 1995 10:06:36 GMT Subject: [Q] Port from DECnet 4 --> TCP/IP Message-ID: <1995Jun7.100636.1@brest> From: massol@brest Date: 7 Jun 95 10:06:36 GMT Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Hi, We are planning to move from a DECnet 4 network to a TCP/IP one. Thus we are planning to port some application to TCP/IP. I would like to know from some persons who have had some experience in this domain, what are the easiest applications to port and the most difficult ones. Let me give you some more details; we have all the following kind of network access : Transparent task-to-task applications using : - DCL (TYPE ...) - I/O statements in a high-level language (C, Pascal, ...) - RMS in - high-level language - VAX MACRO - System services($QIO) in - high-level language - VAX MACRO Non-transparent task-to-task applications using : - System services($QIO) in - high-level language - VAX MACRO ... well I think we have all the possible kind of network accesses .... !! For all these kinds of accesses can you tell me which one are the most difficult to port and the easiest ones. My opinion is that non-transparent task-to-task might be the easiest to port as it needs only translate the $QIO calls to socket ones (???) whereas for transparent access DECnet handles everything and to port it might need to developp additionnal code (??) For instance with TCP/IP it doesn't seem possible to manipulate remote files (??). I would appreciate any comment regarding a port from DECnet to TCP/IP, especially an average cost (man/day) for every network access listed above (if it is possible to evaluate it !!) ... Thanks very much for any information. Vincent Massol -- -----------------------------+----------------------------------------- Vincent Massol | Internet: massol@vaxli.enst-bretagne.fr Ecole Nationale Superieure | Address : 37, rue de Saussure. des Telecommunications de | 75017 Paris. France. Bretagne. | -----------------------------+----------------------------------------- ================================================================================ Archive-Date: XXX, 5 Jun 1995 20:53:45 CDT Subject: Re: How to get a VAX on the net Message-ID: <1995Jun5.205345.20399@montagar> From: davidc@montagar.com (David L. Cathey) Date: 5 Jun 95 20:53:45 CDT References: <19950605.171841.05@home.foobar.co.uk> In article <19950605.171841.05@home.foobar.co.uk>, Bryan Wells writes: > The equipment I have access to is : > > VAX 4100 - 100A running OpenVMS 5.2 > DecServer 300 > Tricom Office Server 400 > Hays compatible 14400 baud modem. > > How would I set up the above equipment? > IP address > Default gateway > Nameserver You would get these addresses from your service provider. > Mail server... The VAX would be a mail server... > Use a DecServer port with the modem for SLIP. Yes, but you would have to use a DECServer 700, or use the SLIP software from Multinet or equivalent TCP/IP product. > Would I need any extra software, and if so where do I get it. Yes, Multinet (with SLIP/PPP) or equivalent TCP/IP product. > Is the standard VMS mail capable of internet mailing? (SMTP) No, you will want to get MX from ftp.wku.edu and use it to "glue" VAX MAIL to TCP/IP. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - David L. Cathey |Inet: davidc@montagar.com Montagar Software Concepts |UUCP: ...!montagar!davidc P. O. Box 260776 |Fone: (214)-578-5036 Plano TX 75026-0772 |http://www.montagar.com/~davidc/ ================================================================================ Archive-Date: Tue, 13 Jun 1995 15:16:51 PDT Subject: Q: IP over 802.3, How? Message-ID: <3rk3r5$psf@ftp.space.net> From: Joerg Ziegler Date: Tue, 13 Jun 95 15:16:51 PDT Content-Type: TEXT/PLAIN; charset=US-ASCII Need Help: Is it possible to run IP on a VMS system via TCP/IP stacks like Multinet, TCPware, UCX or other over a 802.3 line? Is it supported by any of those products or what should could I do to communicate with nodes speaking 802.3. Is it possible to talk DECnet over 802.3? How? Why is ETHERNET_II the default? Is it? Thanks for help. May be via E-Mail? Best Regards Joerg Ziegler Brain Force Software Products & Services GmbH Phone: +49-89-317004-23 Fax: +49-89-317004-20 E-Mail: ZIEGLER@brainforce.com **************************************************** ** Comments are free, but facts are sacred. ** ** ** **************************************************** ================================================================================ Archive-Date: XXX, 15 Jun 1995 17:34:01 GMT Subject: 'lprm'ing an active print job through TCPware. Message-ID: <3rpqu9$d5@lightning.ditc.npl.co.uk> From: MGK@newton.npl.co.uk (Martin Kiff, Computing Services, NPL) Date: 15 Jun 1995 17:34:01 GMT We use the TCPware lpd print server to service lpr requests from various machines. We've found that we can remove a print job from a queue with 'lprm' (afer we have found it's number with 'lpq') but we cannot cancel and remove a job which has already started. Are we alone with this problem? Regards, Martin Kiff mgk@newton.npl.co.uk ================================================================================ Archive-Date: XXX, 15 Jun 1995 23:38:23 -0400 Subject: Re: Q: IP over 802.3, How? Message-ID: <1995Jun15.233823@process.com> From: volz@process.com (Bernie Volz) Date: 15 Jun 95 23:38:23 -0400 References: <3rk3r5$psf@ftp.space.net> In article <3rk3r5$psf@ftp.space.net>, Joerg Ziegler writes: > Need Help: > > Is it possible to run IP on a VMS system via TCP/IP stacks like Multinet, > TCPware, UCX or other over a 802.3 line? > Is it supported by any of those products or what should could I do > to communicate with nodes speaking 802.3. > > Is it possible to talk DECnet over 802.3? How? > Why is ETHERNET_II the default? Is it? For TCP/IP, the standard really is Ethernet II, not 802.3. There might be a few implementations that support 802.3, but almost everyone that I'm aware of uses Ethernet II format. And, the major point of using TCP/IP is interoperability ... if you speak 802.3 and noone else on your network does, you won't be able to talk. Refer to RFC 894 for details; that's the standard the defines how IP datagrams are sent over Ethernet networks. TCPware does not provide a means to configure this for TCP/IP (it does for the NetWare IPX protocol). TCPware's TCP/IP always uses the Ethernet encapsulation. One other point worth mentioning ... you can use Ethernet II *AND* 802.3 encapsulation for various protocols over the same Ethernet cable (even the same interface). They were designed such that the software can tell whether a packet is 802.3 or Ethernet II. So, if you have an "802.3 ethernet", just set up TCP/IP and start sending packets. - Bernie Volz Process Software Corporation ================================================================================ Archive-Date: XXX, 15 Jun 1995 16:28:28 GMT Subject: Settting up TCPMan Message-ID: <3rpn3c$f23@hermes.acs.unt.edu> From: stephenf@jove.acs.unt.edu (Stephen Andrew Fuqua) Date: 15 Jun 1995 16:28:28 GMT Can anyone help me configure TCPman so that I can run it and Netscape? I am running SLiRP for slip emulation. I need help!! Please e-mail me directly if you have any suggestions... Peace, Stephen A. Fuqua stephenf@jove.acs.unt.edu ================================================================================ Archive-Date: XXX, 23 Jun 1995 00:18:04 GMT Subject: OVMS Foreign mail interface ? Message-ID: <1995Jun23.001804.159@decus> From: k_schumacher@decus.ch (Kurt Schumacher - HIS Software AG) Date: 23 Jun 95 00:18:04 GMT Hello Can anybody give me a pointer on OVMS-Mail foreign mail interface? I'd like to create an image (for example SYS$LIBRARY:PAGE_MAILSHR.EXE) which can be called by VMS-Mail by To: PAGE%"number_here" All I've found are the Mail utility routines in the Utility Routines Manual, but don't think, this can help. thanks Kurt -- +----------------------------------------------------------------------+ | Kurt Schumacher E-Mail: k_schumacher@decus.ch | | PSI-Mail: PSI%(228)47931402::KS | | HIS Software AG Voice: ++41 (0) 1 461 21 11 | | Binzstrasse 7 FAX: ++41 (0) 1 461 21 50 | | CH-8045 Zürich | +----------------------------------------------------------------------+ -- +----------------------------------------------------------------------+ | Kurt Schumacher E-Mail: k_schumacher@decus.ch | | PSI-Mail: PSI%(228)47931402::KS | | HIS Software AG Voice: ++41 (0) 1 461 21 11 | | Binzstrasse 7 FAX: ++41 (0) 1 461 21 50 | | CH-8045 Zürich | +----------------------------------------------------------------------+ ================================================================================ Archive-Date: XXX, 27 Jun 1995 15:04:09 -0400 Subject: Re: OVMS Foreign mail interface ? Message-ID: <1995Jun27.150409@process.com> From: volz@process.com (Bernie Volz) Date: 27 Jun 95 15:04:09 -0400 References: <1995Jun23.001804.159@decus> In article <1995Jun23.001804.159@decus>, k_schumacher@decus.ch (Kurt Schumacher - HIS Software AG) writes: > Hello > > Can anybody give me a pointer on OVMS-Mail foreign mail interface? > > I'd like to create an image (for example SYS$LIBRARY:PAGE_MAILSHR.EXE) > which can be called by VMS-Mail by > > To: PAGE%"number_here" > > All I've found are the Mail utility routines in the Utility Routines Manual, > but don't think, this can help. > I don't believe this interface is documented. Your best bet is to get the OpenVMS Source Listings CDROM and look at how MAIL calls these routines. It basically uses LIB$FIND_IMAGE_SYMBOL to load the MAILSHR and call the main routine. Or, obtain some public-domain software (such as MX) that uses this interface and examine that source code. MX, for example, is on the OpenVMS Freeware CDROM being distributed with OpenVMS V6.2 and is also available on the Internet (ftp.spc.edu). - Bernie Volz Process Software Corporation ================================================================================ Archive-Date: Wed, 28 Jun 1995 20:48:38 GMT Subject: Using TCPWARE with Pegasus Mail/Mercury gateway Message-ID: From: andycheetham@cix.compulink.co.uk ("Andy Cheetham") Date: Wed, 28 Jun 1995 20:48:38 GMT I am trying to set up a Mercury Gateway to link an MHS based system using Pegasus Mail with a VAX running TCPWARE SMTP. Can any give me any hints on how to go about it ? Andy Cheetham Systems Manager Morgan Matroc Ltd ================================================================================ Archive-Date: XXX, 29 Jun 1995 05:51:33 -0400 Subject: Re: Using TCPWARE with Pegasus Mail/Mercury gateway Message-ID: <3stt35$pmm@epicycle.lm.com> From: rytis@telerama.lm.com (Rytis Balciunas) Date: 29 Jun 1995 05:51:33 -0400 References: Andy Cheetham (andycheetham@cix.compulink.co.uk) wrote: : I am trying to set up a Mercury Gateway to link an MHS based system using : Pegasus Mail with a VAX running TCPWARE SMTP. : Can any give me any hints on how to go about it ? Simply "point" Mercury to the node that's running TCPWare (your "smart mailer") in MERCURY.INI. You might want to snag MX from ftp.wku.edu, disable the SMTP portion of TCPware, and use MX instead. It's "free", and gives a heck of a lot more flexibility. -- -------------------------------------------------------------------------- Rytis T. Balciunas (rytis@telerama.lm.com) --------------------------------------------------------------------------