INFO-VAX Sat, 10 Feb 2007 Volume 2007 : Issue 82 Contents: Re: Help configuring VMS mail with Dynaccess.com Re: Help configuring VMS mail with Dynaccess.com Re: Help configuring VMS mail with Dynaccess.com Re: Help wanted with Pathworks 5.0a Re: Help wanted with Pathworks 5.0a Re: Help wanted with Pathworks 5.0a Re: Help wanted with Pathworks 5.0a Re: Help wanted with Pathworks 5.0a Re: Migrating C application from VMS to LINUX Re: Migrating C application from VMS to LINUX Re: Migrating C application from VMS to LINUX Re: Migrating C application from VMS to LINUX RE: Migrating C application from VMS to LINUX ---------------------------------------------------------------------- Date: 10 Feb 2007 00:48:53 -0800 From: mcbill20@yahoo.com Subject: Re: Help configuring VMS mail with Dynaccess.com Message-ID: <1171097333.882196.82460@h3g2000cwc.googlegroups.com> Well, it all works great now. While it was a good re-learning experience, most of it was unnecessary. It turned out that just shutting down and restarting the entire TCP stack fixed the problems. And, it looks like I had it configured and then reconfigured (for dynaccess.com) correctly but that I had the wrong tariff selected for dynaccess.com. Until JF pointed it out, I didn't realize that the "Heartbeat-A" tariff is the minimum in order to be able to send SMTP. All the "domain mismatch" problems went away when I restarted TCPIP. I'm still not sure I completely understand where the different names are used throughout HP TCPIP. I do know that I had to use a few aliases in the host file in order to be able to receive SMTP mail. When you start from scratch and configure an adapter, the TCPIP $CONFIGURE.COM procedure adds an entry to the host file that is the host name only. Without adding an alias that is the fully qualified "outside" domain name, incoming email gets rejected as SPAM. And without specifying the "outside" domain name as the substitute domain for the SMTP config, outgoing mail gets returned with a "command error 553". Anyway, thank you all for the help. I really appreciate it. Bill ------------------------------ Date: Sat, 10 Feb 2007 15:01:48 +0000 (UTC) From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) Subject: Re: Help configuring VMS mail with Dynaccess.com Message-ID: In article <1171097333.882196.82460@h3g2000cwc.googlegroups.com>, mcbill20@yahoo.com writes: > Well, > it all works great now. While it was a good re-learning experience, > most of it was unnecessary. It turned out that just shutting down and > restarting the entire TCP stack fixed the problems. And, it looks like > I had it configured and then reconfigured (for dynaccess.com) > correctly but that I had the wrong tariff selected for dynaccess.com. > Until JF pointed it out, I didn't realize that the "Heartbeat-A" > tariff is the minimum in order to be able to send SMTP. I think that was I, but who's counting? :-) > All the "domain mismatch" problems went away when I restarted TCPIP. > I'm still not sure I completely understand where the different names > are used throughout HP TCPIP. I do know that I had to use a few > aliases in the host file in order to be able to receive SMTP mail. > When you start from scratch and configure an adapter, the TCPIP > $CONFIGURE.COM procedure adds an entry to the host file that is the > host name only. Without adding an alias that is the fully qualified > "outside" domain name, incoming email gets rejected as SPAM. And > without specifying the "outside" domain name as the substitute domain > for the SMTP config, outgoing mail gets returned with a "command error > 553". Check out TCPIP$SMTP_COMMON:TCPIP$SMTP_LOCAL_ALIASES.TXT. You can put a list of domains in there for which you can receive email. You can also redefine TCPIP$SMTP_COMMON: "TCPIP$SMTP_COMMON" = "SYS$SPECIFIC:[TCPIP$SMTP]" (LNM$SYSTEM_TABLE) = "CLUSTER_TCPIP_SMTP" 1 "CLUSTER_TCPIP_SMTP" = "CLUSTER_DISK:[SYSTEM.TCPIP_SMTP]" (LNM$SYSTEM_TABLE) Thus, one can have one TCPIP$SMTP_LOCAL_ALIASES.TXT, STMP.CONFIG etc for all nodes in the cluster (overriding them with machine-specific ones in SYS$SPECIFIC:[TCPIP$SMTP] (the default translation of "TCPIP$SMTP_COMMON) if necessary). ------------------------------ Date: Sat, 10 Feb 2007 14:51:33 +0000 (UTC) From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) Subject: Re: Help configuring VMS mail with Dynaccess.com Message-ID: In article , JF Mezei writes: > Phillip Helbig---remove CLOTHES to reply wrote: > > I have several NAT routers. All of them are DHCP clients with respect > > to the WAN, and can be DHCP servers with respect to the LAN (I don't use > > DHCP on my VMS machines, though). ALL of them pick up DNS servers when > > they are configured via DHCP. However, only SOME of them will in turn > > act as a nameserver for machines on the LAN. Thus, the ones that don't > > must be getting the DNS servers for some other reason. > > The DNS server(s) are supplied as part of pretty default DHCP and PPP/PPPoE > dialogues. > > A router can accept the DHCP/PPPoE information and do nothing with it. Or > it could use this as part of its own DHCP server , providing those DNS > settings to lan side clients. Right. As I said, I don't have DHCP on my VMS machines (although I could). The nameservers in the router are for that case. > If a router acts as a DNS server, it is probably simply configured to take > packets destined to its IP's port 53 and forward them to one of the DNS > servers. Right. However, not all of them do this, even if they do have a DNS server configured for passing on to their DHCP clients. ------------------------------ Date: 10 Feb 2007 00:51:01 -0800 From: "Antoniov" Subject: Re: Help wanted with Pathworks 5.0a Message-ID: <1171097461.736834.203950@k78g2000cwa.googlegroups.com> Wilm Boerhout wrote: > (This is about VMS 6.2 , UCX 4.0 and Pathworks 5.0a. > Formal support for these products is non-existant) > > I helped a client today with moving his systems to a new location. > > Part of the move was that the servers (VAX, Windows, Unix) and the > routers/switches became part of a new IP subnet (nnn.mmm.229.* --> > nnn.mmm.76.*) > > So after the physical move I reconfigured UCX, providing it with the new > IP-address, gateway, DNS, etc. numbers. After rebooting, access to/from > the system was possible using telnet and ftp. Access from outside the > system to the Pathworks file services was not possible: the Windows > client could not find the network path \\server\service. Needless to say > that this worked before the move. How clients were working before? AFAIK Pathwork 5 can't support Windows XP clients. Windows XP tries to access to server using a protected channel while Pathwork uses unprotected channel, so you configurated all PCs before the move. Are they the same PCs? > > When starting up, the message "File Services use DECnet and TCP" appears > on the console as before. No errors were found in the log files of any > Pathworks modules. The file services show up as registered (PCSA SHOW > FILE SERV /REG), but the only service that shows up with PCSA SHOW FILE > SERV /ACT is the IPC service. Can you start manually the service? > > Questions: > > 1. Do I need to tell Pathworks somehow about the changed IP address? > Access from the client is via TCP/IP as before. Clients do not run > DECnet anymore (they did not do so before the move either) You can also try using NetBIOS (just for check, not for using) > > 2. What is the magic incantation to make REGISTERED file services become > ACTIVE? Have you some Windows W2K or W2K3 server with active directory and/or native mode? > > Thanks, > Wilm Boerhout ------------------------------ Date: Sat, 10 Feb 2007 10:26:36 +0100 From: Wilm Boerhout Subject: Re: Help wanted with Pathworks 5.0a Message-ID: <45cd8fcc$0$14696$ba620dc5@nova.planet.nl> on 10-2-2007 9:51 Antoniov wrote... > How clients were working before? AFAIK Pathwork 5 can't support > Windows XP clients. > Windows XP tries to access to server using a protected channel while > Pathwork uses unprotected channel, so you configurated all PCs before > the move. Are they the same PCs? Some of them are, some of them are not. No difference in behavior. Before the move, PCs were on XP as well. > Can you start manually the service? I could try, if I knew how. PCSA has no command (at least I could not find one in PCSA HELP) to make a single file service active. Or were my eyes too tired last night? > Have you some Windows W2K or W2K3 server with active directory and/or > native mode? Yes. Now and before the move. Why do you ask? Thanks for helping out. /Wilm ------------------------------ Date: Sat, 10 Feb 2007 11:37:03 +0100 From: "H Vlems" Subject: Re: Help wanted with Pathworks 5.0a Message-ID: <45cd9f02$0$27376$bf4948fe@news.tele2.nl> Wilm, the VMS systems and the XP systems moved to the new IP network, right? And all network gear, if any, as well. What protocols are running on the VMS server besides IP, do you run DECnet or NETBEUI? What happens if you run a client without NETBIOS over IP support and stop the NETBEUI service on the PCSA server? Hans BTW where are you located, Nederland? Zo ja, waar ergens? "Wilm Boerhout" schreef in bericht news:45cd8fcc$0$14696$ba620dc5@nova.planet.nl... > on 10-2-2007 9:51 Antoniov wrote... > > > How clients were working before? AFAIK Pathwork 5 can't support > > Windows XP clients. > > Windows XP tries to access to server using a protected channel while > > Pathwork uses unprotected channel, so you configurated all PCs before > > the move. Are they the same PCs? > Some of them are, some of them are not. No difference in behavior. > Before the move, PCs were on XP as well. > > > Can you start manually the service? > I could try, if I knew how. PCSA has no command (at least I could not > find one in PCSA HELP) to make a single file service active. Or were my > eyes too tired last night? > > > Have you some Windows W2K or W2K3 server with active directory and/or > > native mode? > Yes. Now and before the move. Why do you ask? > > Thanks for helping out. > > /Wilm ------------------------------ Date: Sat, 10 Feb 2007 12:09:27 +0100 From: Wilm Boerhout Subject: Re: Help wanted with Pathworks 5.0a Message-ID: <45cda7e7$0$15246$ba620dc5@nova.planet.nl> on 10-2-2007 11:37 H Vlems wrote... > the VMS systems and the XP systems moved to the new IP network, right? And > all network gear, if any, as well. Correct. Everything was laid out redundant ("double") on the old premises, and they moved it in two phases, changing network addresses in each phase. > What protocols are running on the VMS server besides IP, do you run DECnet > or NETBEUI? DECnet is running, NETBEUI I'm not sure, have to check. Mind you, this is an old system. If we cannot get Pathworks to run, we will consider reconfiguring, up to losing Pathworks and DECnet altogether and ftp-transfer the VMS data files to a Windows server nightly. > What happens if you run a client without NETBIOS over IP support and stop > the NETBEUI service on the PCSA server? No idea. I have no access to the customer system at the moment. > BTW where are you located, Nederland? Zo ja, waar ergens? Zeker, Zwolle. /Wilm ------------------------------ Date: Sat, 10 Feb 2007 05:41:10 -0800 From: "Tom Linden" Subject: Re: Help wanted with Pathworks 5.0a Message-ID: On Fri, 09 Feb 2007 13:40:17 -0800, Wilm Boerhout wrote: > (This is about VMS 6.2 , UCX 4.0 and Pathworks 5.0a. > Formal support for these products is non-existant) > > I helped a client today with moving his systems to a new location. > > Part of the move was that the servers (VAX, Windows, Unix) and the > routers/switches became part of a new IP subnet (nnn.mmm.229.* --> > nnn.mmm.76.*) Are these both routable sets? What I do is to give everything a 10.x.x.x address, VMS servers have routable and aliased non-routable, cisco router one port for each. That way it is portable and PCs are not reachable from outside. > > So after the physical move I reconfigured UCX, providing it with the new > IP-address, gateway, DNS, etc. numbers. After rebooting, access to/from > the system was possible using telnet and ftp. Access from outside the > system to the Pathworks file services was not possible: the Windows > client could not find the network path \\server\service. Needless to say > that this worked before the move. > > When starting up, the message "File Services use DECnet and TCP" appears > on the console as before. No errors were found in the log files of any > Pathworks modules. The file services show up as registered (PCSA SHOW > FILE SERV /REG), but the only service that shows up with PCSA SHOW FILE > SERV /ACT is the IPC service. > > Questions: > > 1. Do I need to tell Pathworks somehow about the changed IP address? > Access from the client is via TCP/IP as before. Clients do not run > DECnet anymore (they did not do so before the move either) > > 2. What is the magic incantation to make REGISTERED file services become > ACTIVE? > > Thanks, > Wilm Boerhout -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ ------------------------------ Date: 10 Feb 2007 13:21:09 GMT From: bill@cs.uofs.edu (Bill Gunshannon) Subject: Re: Migrating C application from VMS to LINUX Message-ID: <535v65F1pqppfU1@mid.individual.net> In article <45CD5C12.1090307@comcast.net>, "Richard B. gilbert" writes: > David J Dachtera wrote: >> "Richard B. gilbert" wrote: >> >>>Tad Winters wrote: >>> >>>>"Richard B. gilbert" wrote in >>>>news:45CD2299.9030200@comcast.net: >>>> >>>> [..snip..] >>>> >>>> >>>>>A piece of advice you may have heard once upon a time goes like this: >>>>>Pick the application software you want to use and then buy the >>>>>platform (hardware and software) that it runs on. If you are very >>>>>lucky you may get a choice of platforms. In most cases you buy a PC >>>>>and Windoze. >>>>> >>>> >>>> >>>>I'd always heard you were supposed to select the "best" software you could >>>>afford and then buy whatever hardware (and OS) was required to run it. >>>>With that, I guess you'd expect to see a variety of operating systems at >>>>most companies that had much diversity in products and services. >>>>Apparently, some companies define "best" as M$oft. My definition of >>>>"best" includes accomplishing the task reliably and without negatively >>>>impacting other tasks. >>> >>>Sounds like a different way to say the same thing! Pick the application >>>software that best meets your needs . . . . >>> >>>And total cost of ownership is probably a big factor in many such >>>decisions. If a $700 PC will do the job, do you spend $20K on an Alpha? >> >> >> No - because VMS only runs on the $20K machine, not the $700 machine. >> >> That's the part that ((DEC)Compaq)HP doesn't get. >> > > That's not quite true. My VMS desktop (Alphastation 200 4/233) cost me > only $2000 with VMS, DECWindows, DECnet, and TCP/IP licenses. I also > have an Alphastation 600 that I bought, used, for about $300. (Boeing's > loss was my gain!) > > Sure, if you buy new, top of the line, $20K is only the beginning but > you can do a lot better shopping the used market. Most real businesses don't have that option and even though they get to write off the investment the beancounters want to see those numbers come down. The reduced cost of comodity hardware is rapidly bringing the proprietary era to an end. Either you make your offerings run on the same comodity hardware as your competition or you go the way of the dinosaur. bill -- Bill Gunshannon | de-moc-ra-cy (di mok' ra see) n. Three wolves bill@cs.scranton.edu | and a sheep voting on what's for dinner. University of Scranton | Scranton, Pennsylvania | #include ------------------------------ Date: 10 Feb 2007 14:13:14 GMT From: bill@cs.uofs.edu (Bill Gunshannon) Subject: Re: Migrating C application from VMS to LINUX Message-ID: <53627pF1r0u3cU1@mid.individual.net> In article <45cd26fa$0$49200$14726298@news.sunsite.dk>, Arne Vajhøj writes: > Bill Gunshannon wrote: >> In article <45CC978D.1060709@comcast.net>, >> "Richard B. gilbert" writes: >>> Do you use any VMS libraries not defined in the ANSI C Standard? Lots >>> of luck porting those! >> >> But then, they wouldn't really be C programs, would they? Another reason >> to avoid proprietary extensions. > > If using non ANSI C libraries implies it is not a C program, then > there are not many C programs around ... I was refering to things like RMS calls and QIO calls, which define "VMS" vs. "C" programs. I am also quite sure that was what Mr. Gilbert was refering to as "VMS libraries not defined in the ANSI C Standard". I once wrote a "Pascal" program that made very heavy use of things like the Primos T$AMLC call. While porting it to something like Unix was doable, one would have to accept that while it was mostly written in Pascal it really wasn't strictly "a Pascal program". bill -- Bill Gunshannon | de-moc-ra-cy (di mok' ra see) n. Three wolves bill@cs.scranton.edu | and a sheep voting on what's for dinner. University of Scranton | Scranton, Pennsylvania | #include ------------------------------ Date: 10 Feb 2007 14:19:27 GMT From: bill@cs.uofs.edu (Bill Gunshannon) Subject: Re: Migrating C application from VMS to LINUX Message-ID: <5362jeF1r0u3cU2@mid.individual.net> In article , Kilgallen@SpamCop.net (Larry Kilgallen) writes: > In article <534a8mF1r4fn4U1@mid.individual.net>, bill@cs.uofs.edu (Bill Gunshannon) writes: >> In article , >> Kilgallen@SpamCop.net (Larry Kilgallen) writes: >>> In article <1171017147.288767.101230@a34g2000cwb.googlegroups.com>, "klaus_austria" writes: >>> >>>> I plan to migrate from VMS to Linux. I have lots of c applications >>>> with interprocess communication like global logs and sections. >>>> Do exist any identical tools, to migrate to Linux in an easy way? >>>> I have some SNA connections using the sna protocoll. Is there a chance >>>> in Unix too? >>>> What else could cause problems? >>> >>> To reach people who have done this you might be better off in a Linux >>> newsgroup. >> >> Why would you think that? I doubt anyone in a Linux newsgroup has even >> heard of VMS much less had any experience with it. >> >> Oh wait, that was just a brush-off to another VMS deserter. My mistake. > > Feel free to provide a detailed technical answer to his Linux issues - > in some other forum. Like I said, "just a brush-off to another VMS deserter". I am sure if it were someone asking for the reverse you wouldn't send them off to look in a Linux group. He is still a VMS user stuck with the task of learning the other-world equivalents of VMS proprietary programming practices. I would guess the best place to find help would be among people who actually know what the VMS calls do. Heck, anybody can tell him what the Unix/Linux stuff does. For what it's worth, he is free to contact me via Email and I would be more than willing to take a look at some of his programs to see how difficult, if at all possible, it would be to move them or if he is looking at total re-writes, possibly in another language. (Contrary to popular belief, Unix does support more than C and most of us real Unix programmers know how to use them. :-) bill -- Bill Gunshannon | de-moc-ra-cy (di mok' ra see) n. Three wolves bill@cs.scranton.edu | and a sheep voting on what's for dinner. University of Scranton | Scranton, Pennsylvania | #include ------------------------------ Date: Sat, 10 Feb 2007 11:13:56 -0500 From: =?ISO-8859-1?Q?Arne_Vajh=F8j?= Subject: Re: Migrating C application from VMS to LINUX Message-ID: <45cdef45$0$49199$14726298@news.sunsite.dk> Bill Gunshannon wrote: > In article <45cd26fa$0$49200$14726298@news.sunsite.dk>, > Arne Vajhøj writes: >> Bill Gunshannon wrote: >>> In article <45CC978D.1060709@comcast.net>, >>> "Richard B. gilbert" writes: >>>> Do you use any VMS libraries not defined in the ANSI C Standard? Lots >>>> of luck porting those! >>> But then, they wouldn't really be C programs, would they? Another reason >>> to avoid proprietary extensions. >> If using non ANSI C libraries implies it is not a C program, then >> there are not many C programs around ... > > I was refering to things like RMS calls and QIO calls, which define "VMS" > vs. "C" programs. I am also quite sure that was what Mr. Gilbert was > refering to as "VMS libraries not defined in the ANSI C Standard". And ? There are functions defined in ANSI C and there are functions not defined in ANSI C. On VMS the last ones tend to have a dollar in their names. Windows and Linux uses a different naming convention. But a C program calling RMS or system services are not less a C program, than a C program calling Win32 API or some BSD/SysV API. Arne ------------------------------ Date: Sat, 10 Feb 2007 12:59:28 -0500 From: "Main, Kerry" Subject: RE: Migrating C application from VMS to LINUX Message-ID: > -----Original Message----- > From: Richard B. gilbert [mailto:rgilbert88@comcast.net]=20 > Sent: February 9, 2007 8:41 PM > To: Info-VAX@Mvb.Saic.Com > Subject: Re: Migrating C application from VMS to LINUX >=20 [snip ...] > I have done my share of porting things to VMS. It can be a=20 > bitch. If=20 > you want to see how bad it can get, download the current=20 > version of the=20 > NTP reference implementation from http://ntp.org/ >=20 > VMS Engineering did a port of a ten year old version. I=20 > doubt that it=20 > was easy. I tried to build the current version from source=20 > on VMS V7.2=20 > without success. It wants Unixy things that VMS does not have. >=20 So, you tried porting a 10 year old UNIX application to an OpenVMS release (V7.2) from 1999? That's like saying Windows is no good because you tried Windows NT4 and it did not have all you were looking for. Someone might ask if you had also tried W2K3 as well. ROTFL .. Hey - check out new releases of OpenVMS - much more UNIX compatibility built in these days.=20 Reference: http://h71000.www7.hp.com/portability/ (Home page for UNIX to OpenVMS Portability) http://h71000.www7.hp.com/openvms/integrity/v83features.html (V8.3 and UNIX portability - scroll down) > A piece of advice you may have heard once upon a time goes like this: > Pick the application software you want to use and then buy=20 > the platform=20 > (hardware and software) that it runs on. If you are very=20 > lucky you may=20 > get a choice of platforms. In most cases you buy a PC and Windoze. >=20 Yes, but some people have real applications with real concerns about security and maintaining privacy issues with their data.=20 Because of the constant App re-cert's and re-testing due to the 5-20 security patches released each and every month for Windows and Linux, companies with these security concerns can simply not afford Linux and Windows. And before anyone starts jumping up and down, simply check out RH's security site: https://www.redhat.com/archives/enterprise-watch-list/ (click on thread for each month) And before anyone says "but some are app issues" - it does not matter if the end result is elevated priv's or access to priv'ed data.=20 Regards Kerry Main Senior Consultant HP Services Canada Voice: 613-592-4660 Fax: 613-591-4477 kerryDOTmainAThpDOTcom (remove the DOT's and AT)=20 OpenVMS - the secure, multi-site OS that just works. ------------------------------ End of INFO-VAX 2007.082 ************************