1 INFO-VAX	Sat, 07 Jul 2001	Volume 2001 : Issue 374       Contents: A little weekend humour  Alpha 2100A blue screen :-(  Another OpemVMS newbie!  RE: Another OpemVMS newbie!  Re: Another OpemVMS newbie!  Re: axp 150 memory help  Re: axp 150 memory help ( Re: Compaq switches to IA-64 (VAX float)) Re: Difference between an 8820 and 8820-N 3 Re: Disable DELETE, RENAME, and PURGE command verbs  Re: DSL for OpenVMS  Re: Experience with EMC storage  Re: Experience with EMC storage  Re: IA64 Rocks My World  Re: IA64 Rocks My World  Network Printers Re: Network Printers Re: Network Printers" Re: New Mailbox 0.7 (anyone using) Printer hookups P Re: Sending a double (floating-point) field over tcp from OpenVMS 7.2 to Tru64 41 Re: Some thoughts on the recent turn of events... 1 Re: The death of VMS has been greatly exaggerated 1 Re: The death of VMS has been greatly exaggerated * the tcp node name versus the vms node name. Re: the tcp node name versus the vms node name  F ----------------------------------------------------------------------  $ Date: Sat, 7 Jul 2001 05:21:35 -0400, From: "islandco.com" <dbturner@islandco.com>  Subject: A little weekend humour/ Message-ID: <tkdkt91c0grsba@news.supernews.com>   8 Let's see if I understand how America works lately . . .  H If a woman burns her thighs on the hot coffee she was holding in her lap while # driving, she blames the restaurant.   H If your teen-age son kills himself, you blame the rock 'n' roll music or musician he liked.  H If you smoke three packs a day for 40 years and die of lung cancer, your family blames the tobacco company.   K If your daughter gets pregnant by the football captain you blame the school  for  poor sex education.   L If your neighbor crashes into a tree while driving home drunk, you blame the
 bartender.  K If your cousin gets AIDS because the needle he used to shoot up with heroin  was = dirty, you blame the government for not providing clean ones.   F If your grandchildren are brats without manners, you blame television.  L If your friend is shot by a deranged madman, you blame the gun manufacturer.  K And if a crazed person breaks into the cockpit and tries to kill the pilots  atL 35,000 feet, and the passengers kill him instead, the mother of the deceased blames the airline.   L I must have lived too long to understand the world as it is anymore. So if IJ die while my old, wrinkled ass is parked in front of this computer, I want you  to blame Bill Gates, OK?   ------------------------------   Date: 7 Jul 2001 09:31:13 -0700 1 From: jason_odonnell@erinet.com (Jason O'Donnell) $ Subject: Alpha 2100A blue screen :-(= Message-ID: <5c8ffd05.0107070831.70f2fe58@posting.google.com>    All,  D I recently acquired an Alpha 2100A.  I ran into a problem booting it up.  Description:   E The OPC shows the CPUs as having one pass and one fail.  I pulled the 8 failed CPU card and moved the good one to the CPU0 slot.  A It seems to run through the OPC fine and get to the "Model 4/275" D printout.  At this point the system should be turned over to the OS.  F However, the console I have attached shows nothing but blue screen.  IE tried a VGA monitor, mouse and keyboard set, then I tried a simple VT  terminal.  Nothing.   = My next thought is to reload the firmware.  The owners manual F (downloaded from Compaq) shows the FSL dipswitches.  However, I cannot@ find them or even jumpers instead.  ARGH.  So, I cannot find theB overwrite switch.  Could the board be newer and not have a switch?  C Any suggestions about what may be wrong and how I can check for it?    Thanks in advance!   JMOD   ------------------------------  $ Date: Sat, 7 Jul 2001 14:25:43 +0100, From: "Mat Riain" <matei@no.spam.eircom.net>  Subject: Another OpemVMS newbie!3 Message-ID: <b8E17.14463$Fk7.128947@news.indigo.ie>    Hello!  L Can someone point out some resources to help a total OpenVMS newbie along onL his way?  I am primarily interested in admin tasks, like add/removing users,  setting permissions, etc. in DCL  J I've seen sites with commands, but nothing referring to the aforementioned tasks.   Thanks!    ------------------------------  % Date: Sat, 07 Jul 2001 10:26:54 -0500 * From: WILLIAM WEBB <WWEBB1@email.usps.gov>$ Subject: RE: Another OpemVMS newbie!- Message-ID: <0033000028561441000002L012*@MHS>    =0ACongratulations!   A You have discovered what many consider to be the finest operating  system on the planet.    First of all, the VMS FAQ:4 http://www.openvms.compaq.com/wizard/openvms_faq.txt   Second, the documentation:- http://www.openvms.compaq.com:8000/index.html   6 That having been said, what other operating system has arcana like the following?  3 VAX:  When you care enough to steal the very best-- 7 http://microscopy.fsu.edu/creatures/pages/russians.html   0 Characterization of Organic Illumination SystemsE http://www.research.compaq.com/wrl/techreports/html/TN-13/pickle.html    Hope this helps.   WWWebb   > -----Original Message-----1 > From: Info-VAX-Request@Mvb.Saic.Com at INTERNET ' > Sent: Saturday, July 07, 2001 9:37 AM F > To: Webb, William W - Raleigh, NC; Info-VAX@Mvb.Saic.Com at INTERNET" > Subject: Another OpemVMS newbie! >  >  > Hello! > > > Can someone point out some resources to help a total OpenVMS > newbie along on : > his way?  I am primarily interested in admin tasks, like > add/removing users, " > setting permissions, etc. in DCL > = > I've seen sites with commands, but nothing referring to the  > aforementioned > tasks. > 	 > Thanks!  >=   ------------------------------  % Date: Sat, 07 Jul 2001 17:04:34 +0100   From: Paul Sture <paul@sture.ch>$ Subject: Re: Another OpemVMS newbie!+ Message-ID: <VA.000003fe.4a67e04b@sture.ch>   D In article <b8E17.14463$Fk7.128947@news.indigo.ie>, Mat Riain wrote:. > From: "Mat Riain" <matei@no.spam.eircom.net> > Newsgroups: comp.os.vms " > Subject: Another OpemVMS newbie!& > Date: Sat, 7 Jul 2001 14:25:43 +0100 >  > Hello! > N > Can someone point out some resources to help a total OpenVMS newbie along onN > his way?  I am primarily interested in admin tasks, like add/removing users," > setting permissions, etc. in DCL > L > I've seen sites with commands, but nothing referring to the aforementioned > tasks. > 	 > Thanks!  > ? At www.openvms.compaq.com you will find links to the following:   & o - Primer for OpenVMS System Managers% o - OpenVMS FAQ - recommended reading  o - OpenVMS Documentation   J Please note that the last item in the list is, unlike offerings from otherG manufacturers, very comprehensive and useful. Please take some time to  A familiarise yourself with it - you'll quickly find it invaluable.    ___ 
 Paul Sture Switzerland    ------------------------------  # Date: Sat, 07 Jul 2001 12:53:10 GMT . From: brown_du@eisner.decus.org (Duncan Brown)  Subject: Re: axp 150 memory help1 Message-ID: <3b47054c.30110309@news.telocity.com>   9 On Sat, 07 Jul 2001 04:55:04 GMT, gobo20@lycos.com wrote:   C >trying to add memory to an axp 150.  i have been told that 72 pin, D >true parity, 70 ns, 36 bit wide 4 or 16 mb simms would work.  for aE >max memory of 128mb.  generic sticks of this sort go for 10-15 bucks F >mail order.  when i check with vendors such as kingsington, they haveF >kits with dec equiv part numbers and want ~$140 for a four stick 64mb >kit.  > E >so i'm confused.  will the generic stick not work?  do i really need F >to purchase one of these oem kits?  (i know they must be installed in! >llike sets of 4, for two banks.)  > F >also, what is the max memory for this guy?  i was told 128, but there >are kits for 256.  D I have two of these, and I don't think I have any DEC memory left inE them at all!  Your specs above are all correct.  I know (from trying) D that 8MB sticks do not work; I never had any 32MB sticks to try so ID don't know about that - I have been living under the assumption that? they're maxed out at 128MB, which has been plenty for my needs.   C The bank slots are physically interleaved, so if you are putting in D 80MB (4*4MB in one bank, 4*16MB in the other) make sure you get themB in the right slots; obviously if you are just filling it with 16MB sticks, there's no problem.    Duncan   ------------------------------  % Date: Sat, 07 Jul 2001 15:55:51 +0100 4 From: John Laird <john@laird-towers.freeserve.co.uk>  Subject: Re: axp 150 memory help8 Message-ID: <0j8ektsqcnc0pfo3a3bv1531orq1bu62ec@4ax.com>  9 On Sat, 07 Jul 2001 04:55:04 GMT, gobo20@lycos.com wrote:   C >trying to add memory to an axp 150.  i have been told that 72 pin, D >true parity, 70 ns, 36 bit wide 4 or 16 mb simms would work.  for aE >max memory of 128mb.  generic sticks of this sort go for 10-15 bucks F >mail order.  when i check with vendors such as kingsington, they haveF >kits with dec equiv part numbers and want ~$140 for a four stick 64mb >kit.  > 3 >so i'm confused.  will the generic stick not work?   D It should - your info is correct.  Just to prove how non-proprietaryH this is, I have two salvaged axp150 4Mb cards running quite happily in aF VLC.  No *way* were the official DEC part numbers even close for these two wildly different machines.     	John  --  
 John Laird Yezerski Roper Ltd   ------------------------------   Date: 7 Jul 2001 08:43:42 GMT - From: djweath@attglobal.net (Dave Weatherall) 1 Subject: Re: Compaq switches to IA-64 (VAX float) 5 Message-ID: <DTiotGxQ0bj6-pn2-OVtbFiDunUnY@localhost>   E On Thu, 5 Jul 2001 18:31:44, "Richard D. Piccard" <piccard@ohio.edu>   wrote:   >  >  > Nigel Arnot wrote: > 
 > > [snip] > L > > I also wonder why anyone really wants non-IEEE float, except as a way ofJ > > accessing old files or writing new ones compatible with an old format,F > > or just possibly to talk to a VAX. All these are best addressed byF > > converting the float data as you read or write it, and letting the% > > rest of the code use native IEEE.  > K > An example where bit-for-bit replication might matter:  the FAA-certified P > simulation software for ground-control radio antenna radiation patterns, whichP > is used to choose locations for the antennas, given local terrain and buildingN > locations, to ensure that all places you can taxi a plane will have adequateP > signal.  My understanding is that they require re-certification by replicatingO > the accepted results for a suite of input data combinations.   I would expect E > other examples in the field of cancer radiation treatment planning.  > P > Not that you couldn't do it with IEEE format floating number calculations, butL > rather that having guaranteed bit-for-bit identical results would speed upR > re-certification, since you wouldn't have to decide whether the differences were2 > significant if there were NO differences at all.   I have a similar situation.   B One or our programs creates stimulation files that contain scaled F integer data only. The program works on Alpha and Vax. I cannot always: get zero differences when DIFFing the output from the two D architectures. The difference comes down to the D_FLOAT and G_FLOAT F types of doubles, not to mention any F_FLOAT derivatives, and how they5 get rounded/truncated when scaled to 16 bit integers.   B Similarly, if I were to need to go to double-IEEE to get the same F precision as F_Float on VAX then that would cause other problems. Not C insurmountable but another large round of testing/qualification is  	 required.   D I my perception wrong here - a single precision DEC F_Float is more F precise than its IEEE equivalent but the IEEE can have larger maximum  and minimum values.    --   Cheers - Dave.   ------------------------------   Date: 7 Jul 2001 08:43:38 GMT - From: djweath@attglobal.net (Dave Weatherall) 2 Subject: Re: Difference between an 8820 and 8820-N5 Message-ID: <DTiotGxQ0bj6-pn2-QvhLM6EC6XoB@localhost>   C On Wed, 4 Jul 2001 19:38:24, "antonio.carlini" <arcarlini@iee.org>   wrote:   >  >  > dittman@dittman.net wrote: > > < > > Is the only difference between an 8820 and an 8820-N the> > > console system?  From the document the 8820 has a MicroVAX> > > II and the 8820-N has a Pro380.  What card was used as the( > > system interface in the MicroVAX II? > 2 > I've never been near either of these systems, so1 > take with an appropriate pinch of salt, but ...  > ) > The VAX 8820-N was a 2 CPU box with no  2 > expansion potential (it was really a VAX 8800). & > The VAX 8820 was a 2 CPU that could 2 > (with the addition of a few more boxes I think)  > become a 3 CPU or 4 CPU box. > 1 > I *guess* it was all in the expansion potential 0 > that the box came with. I'm not 100% sure that1 > the 8820-N was just a new name for the VAX 8800 0 > (and with the number of bits and bobs in those4 > things you'd have a long parts list to check ...). > 	 > Antonio   E When we'd moved everybody else over to Alpha I had an 8820 to myself  F and the 2 other members of my group. Marvellous, the Alpha was quickerE in absolute terms, we still use it, but with 2 cpus & 256M of memory  . between 3/4 people the 8820 was a  joy to use.   --   Cheers - Dave.   ------------------------------   Date: 7 Jul 2001 08:43:40 GMT - From: djweath@attglobal.net (Dave Weatherall) < Subject: Re: Disable DELETE, RENAME, and PURGE command verbs5 Message-ID: <DTiotGxQ0bj6-pn2-uh3NHDT0TR4O@localhost>   ? On Fri, 6 Jul 2001 01:50:16, rdeininger@mindspring.com (Robert   Deininger) wrote:   O > In article <3b450553.2045791@news.wcc.govt.nz>, rob.buxton@wcc.govt.nz wrote:  > C > > A variation on the theme is to create a separate version of the < > > DCLTables minus the commands specified. say short_tables > K > The downside here is the DCL table gets stale.  Any product or OS install J > is likely to update the real version, and then you need to copy, modify,* > and re-install it for the special users.  D We do this kind of thing during STARTUP. Although that was more out  ignorance than planning...  E > > Once done the Users UAF Entry is modified so that they access the E > > short_tables. This prevents them easily being able to subvert the  > > mechanism.   > J > If they know how to write a CLD and SET COMMAND, they can make new verbsK > that access the orgininal DELETE, etc. images.  So protecting those files " > against access is also required. > K > Personally, I think the best solution for users who can't be trusted with K > their own files is DISUSER.  But some sites do have special requirements.   	 Agreed...   F If its other people's stuff, which really ought to be protected by theA more normal VMS methods,  then maybe the STOP /SALARY command is  
 called for...    --   Cheers - Dave.   ------------------------------   Date: 7 Jul 2001 08:53:16 -0700 1 From: jason_odonnell@erinet.com (Jason O'Donnell)  Subject: Re: DSL for OpenVMS= Message-ID: <5c8ffd05.0107070753.417da3b4@posting.google.com>   I > But I'd assume he hasn't as he asked if there was an OpenVMS driver for K > *any* DSL PCI card.  I'd assume he's looking for a driver before he buys.   E You are right, I am exploring the DSL possibilities, but I do not yet A have a PCI card.  My first thought was a direct connection to the B OpenVMS box.  So, I was asking if anybody had a driver written for@ *any* card.  While I could write my own driver, I was hoping oneA already existed and driver writing is more work than I want to do 
 write now.  F It seems everyone uses a DSL router, like a cisco 675 or alcatel 1000,E to make the connection instead.  So that is the route(pun intended) I D will have to go; unless, somebody gets real ambitious and decides toF write a driver.  If anyone does or they find somebody who already has, please let me know.    Thanks for all of your help!   JMOD   ------------------------------  # Date: Sat, 07 Jul 2001 06:09:33 GMT . From: "mulp" <michaelpettengill@earthlink.net>( Subject: Re: Experience with EMC storage@ Message-ID: <xIx17.19$qa6.6319@newsread1.prod.itd.earthlink.net>  1 "Scott Vieth" <svieth@wi.rr.com> wrote in message # news:3B466C1D.64FCBE47@wi.rr.com... E > really liked the management software.  Kicked the hell out of SWCC.   K That's like saying that roller blades are superior to a brick for commuting  30 miles to work.   D SWCC was known by all engineers, including the ones working on it asF virtually useless.  Problem reports seem to generate even more glowingL product brochures rather than adding engineering resources to the project to make it even marginally useful.    ------------------------------  % Date: Sat, 07 Jul 2001 12:11:50 -0500e1 From: "David J. Dachtera" <djesys.nospam@fsi.net>i( Subject: Re: Experience with EMC storage' Message-ID: <3B4742D6.65B8A6ED@fsi.net>    mulp wrote:  > 3 > "Scott Vieth" <svieth@wi.rr.com> wrote in messagei% > news:3B466C1D.64FCBE47@wi.rr.com...wG > > really liked the management software.  Kicked the hell out of SWCC.w > M > That's like saying that roller blades are superior to a brick for commutingn > 30 miles to work.k > F > SWCC was known by all engineers, including the ones working on it asH > virtually useless.  Problem reports seem to generate even more glowingN > product brochures rather than adding engineering resources to the project to! > make it even marginally useful.s  E IMO, one of the biggest drawbacks was the lack of a command-line SWCC-G client for OpenVMS. We've been screaming for years (some of us, anyway)aF for a way to command HSx controllers from a batch job in a supported /> supportable way, rather than using hacks like HSDSA-SCRIPT andG pseudo-terminals (FTAu: devices) in subprocesses, either from DCL or ink
 perl scripts.   @ VMS and related peripherals *MUST* be managed from VMS, not fromB BillyWare or anything else, except that those other platforms be a; secondary consideration, rather than a primary requirement.    -- n David J. Dachterau dba DJE Systemss http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/t  F This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings is to be expected.  @ Feel free to exercise your rights of free speech and expression.  F However, attacks against individual posters, or groups of posters, are strongly discouraged.,   ------------------------------   Date: 7 Jul 2001 00:05:29 -0700r/ From: Brannon_Batson@yahoo.com (Brannon Batson)t  Subject: Re: IA64 Rocks My World= Message-ID: <4495ef1f.0107062305.7210e314@posting.google.com>   a JF Mezei <jfmezei.spamnot@videotron.ca> wrote in message news:<3B463F1C.D376B1D2@videotron.ca>...s > Bill Todd wrote:8 > >  WildFire is a serious mistake. It isn't competitiveB > > > because it is too costly to build, its big and it isn't fast
 > > > enough.h > > K > > That must be why Compaq had its recent spate of super-computer wins (ate) > > least one of them against SUN, IIRC).- > M > I am curious. I have personally never cares for Wildfires. Neat technology,O > but very small market.  D I do not understand this statement.  Which part of the technology do> you consider 'neat'? and why does that make it a niche market?  C I hope that this isn't a sidewise shot at NUMA in general--which is E not so much 'neat' as it is necessary.  I also claim that in N years,nB even most small systems (2-4 nodes) will be ccNUMA--with N as some finite number < 10.   A As for Wildfire's particular implementation of a ccNUMA--it is annD incredibly interesting, though complex, system.  The cache coherenceE protocol of Wildfire should be studied in multiprocessor architecturee. courses--as it is chalk full of trade-offs andF architecture/implementation decisions (whether all the right decisionsF were made is an open question, but I think those guys did a good job).  > Compared to EV7, though, I don't think you can find two ccNUMAC protocols that are more different.  Maybe I'll write a paper one ofgF these days contrasting Wildfire, EV7, and EV8 protocols.  The point isD that the design space in ccNUMA is very large--and Wildfire, while a4 solid system, was just the starting point for Alpha.  , > [snip question about Wildfire vs. HP 9000]   BrannonD not speaking for Compaq@   ------------------------------   Date: 7 Jul 2001 07:48:59 GMTt( From: nmm1@cus.cam.ac.uk (Nick Maclaren)  Subject: Re: IA64 Rocks My World0 Message-ID: <9i6etb$a5h$1@pegasus.csx.cam.ac.uk>  , In article <3B463F1C.D376B1D2@videotron.ca>,/ JF Mezei  <jfmezei.spamnot@videotron.ca> wrote:i >Bill Todd wrote:n7 >>  WildFire is a serious mistake. It isn't competitiveuA >> > because it is too costly to build, its big and it isn't fast  >> > enough. >> rJ >> That must be why Compaq had its recent spate of super-computer wins (at( >> least one of them against SUN, IIRC). > L >I am curious. I have personally never cares for Wildfires. Neat technology, >but very small market.o  @ Both of what I call the Fireblights (i.e. Wildfire and Starfire)? are inferior attempts to emulate SGI Origins.  I wouldn't touch  them for supercomputing.  ? An indication of that is the vast majority of the supercomputer = contracts that Compaq got were based on ES40/ES45 and even DSa- boards, usually with a Quadrics interconnect.o     Regards, Nick Maclaren,* University of Cambridge Computing Service,> New Museums Site, Pembroke Street, Cambridge CB2 3QG, England. Email:  nmm1@cam.ac.uk/ Tel.:  +44 1223 334761    Fax:  +44 1223 334679R   ------------------------------  $ Date: Sat, 7 Jul 2001 17:00:07 +0900& From: "David Lee" <phongle@kornet.net> Subject: Network Printerse+ Message-ID: <9i6fes$of1$1@news1.kornet.net>e  H Sorry to post this silly questions, but I am kind of new to this job andK confusing about the type of printer I should buy and of course I don't wantsK to buy the wrong one.  I have a couple Alpha workstations that connected tobL an ES-40 Server, running OpenVMS 7.2, my system also support both Decnet and TCP/IP.  I want-E to hook up a network printer so that they all can share.  I have beenu looking at theI web, particulartly HP and Lexmark network printers.  None of the printers@> mentioned in their advertisement supporting OpenVMS platforms. My questions are, K are there any printers out there that support this OpenVMS platform?  Or do ( I have to purchase printers from Compaq?
 Thank you.   ------------------------------  % Date: Sat, 07 Jul 2001 05:12:35 -0400s- From: Jack Patteeuw <jjpatteeuw@peoplepc.com>  Subject: Re: Network Printers , Message-ID: <3B46D283.DFA49179@peoplepc.com>   David Lee wrote: ...n > My questions are, M > are there any printers out there that support this OpenVMS platform?  Or do * > I have to purchase printers from Compaq?     Well, that depends ...  J None of the "PC type" network printers will work 100% with OpenVMS.  Your 3 simplest solution is to buy a printer from Genicom.tI (http://www.genicom.com/usa/products/page.htm)  Stick with ones that haver a part number starting with LN  F There are other solutions, but they require additional software on the
 OpenVMS side.a  
 Jack Patteeuw    ------------------------------  % Date: Sat, 07 Jul 2001 10:12:25 -0400 ( From: Hamlyn Mootoo <univms@bigfoot.com> Subject: Re: Network Printersu+ Message-ID: <3B4718C9.DB3DB699@bigfoot.com>3  H Most printers that have internal network cards supporting reverse telnetG and/or LPD will work.  HP and Lexmark printers both work well with VMS.eB This also depends on what you want to print on these printers.  If9 you're going to print graphics from VMS I would go with ak' postscipt-capable HP or Lexmark myself.    HM   David Lee wrote: > J > Sorry to post this silly questions, but I am kind of new to this job andM > confusing about the type of printer I should buy and of course I don't want M > to buy the wrong one.  I have a couple Alpha workstations that connected towN > an ES-40 Server, running OpenVMS 7.2, my system also support both Decnet and > TCP/IP.  I wantoG > to hook up a network printer so that they all can share.  I have beeno > looking at theK > web, particulartly HP and Lexmark network printers.  None of the printersl@ > mentioned in their advertisement supporting OpenVMS platforms. > My questions are,cM > are there any printers out there that support this OpenVMS platform?  Or do * > I have to purchase printers from Compaq? > Thank you.   ------------------------------  $ Date: Sat, 7 Jul 2001 08:50:32 +0200> From: "Jean-Francois Marchal" <jean-francois.marchal@x9000.fr>+ Subject: Re: New Mailbox 0.7 (anyone using)l. Message-ID: <9i6bd0$jbo$1@reader1.imaginet.fr>  2 I've been told the problem should have been fixed.) You might download the corrected version.5   Jean-Franois Marchald X9000 - LYON (FR).  J "Zane H. Healy" <healyzh@shell1.aracnet.com> a crit dans le message news:6 C%u17.58279$2u2.1130968@e420r-sjo2.usenetserver.com.../ > Jerry Alan Braga <jabraga@flanagan.ca> wrote:o  > > Has anyone got this working. >e > > Config:2 >n > > OpenVMS 7.1-1H2n > > Compaq TCPIP 5.1 ECO-1 > > Compaq C V6.4-005  >xL > > I downloaded the new version and installed it. but I try to run it I get theh# > > banner but then this stack dumpi >o > > $mc mlb_main >i? > > %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtualk > > address=000000000000* > > 000A, PC=000000000003AE60, PS=0000001B; > >                         Version 0.7 -  ESME Sudria 2001a > L > I'm getting a slightly different result, but it gets a SYSTEM-F-ACCVIO forH > me also.  I'm running OpenVMS V7.2, TCPIP V5.0, and Compaq C V6.4-005. I'veA > got Mailbox 0.6 running on the system already (out of differentd directories,H > and I really like it other than the way it handles *large* mailboxes). >a > Zane >    ------------------------------  $ Date: Sat, 7 Jul 2001 16:57:14 +0900& From: "David Lee" <phongle@kornet.net> Subject: Printer hookups+ Message-ID: <9i6f9f$no4$1@news1.kornet.net>i  H Sorry to post this silly questions, but I am kind of new to this job andK confusing about the type of printer I should buy and of course I don't wantcK to buy the wrong one.  I have a couple Alpha workstations that connected tojL an ES-40 Server, running OpenVMS 7.2, my system also support both Decnet and TCP/IP.  I wantsE to hook up a network printer so that they all can share.  I have been  looking at theI web, particulartly HP and Lexmark network printers.  None of the printers > mentioned in their advertisement supporting OpenVMS platforms. My questions are,sK are there any printers out there that support this OpenVMS platform?  Or do ( I have to purchase printers from Compaq?
 Thank you.   ------------------------------   Date: 7 Jul 2001 08:43:36 GMTr- From: djweath@attglobal.net (Dave Weatherall)cY Subject: Re: Sending a double (floating-point) field over tcp from OpenVMS 7.2 to Tru64 4i5 Message-ID: <DTiotGxQ0bj6-pn2-JddKBEV66duI@localhost>   D On Tue, 3 Jul 2001 19:47:43, dvoigt@talarian.com (Dave Voigt) wrote:  E > I have a customer that is receiving the double on the Tru64 machine G > incorrectly. Incorrectly, meaning that one of the bytes is zeroed outtH > when it should have a number in it. This missing byte makes the actual7 > number being represented slightly off. For example, a G > 4.712000000000000e+03 is sent from the VMS program and is received byoE > the Tru64 program as 4.608000000000000e+03. The bytes for 4712 look G > like this: {0 0 0 0 0 104 -78 64} and 4608 look like this: {0 0 0 0 0nH > 0 -78 64}. There is number conversion done on the Tru64 side to handleG > DecG real-format to IEEE real-format, but I don't believe that that'snH > the problem. The reason for this is that this problem doesn't occur atH > my companies site but it does at the customer's. The customer is usingH > the following compilers: Compaq C++ V6.2-048 for OpenVMS V7.2-1 on VMSG > 7.2 and Compaq C++ V6.2-024 for Digital UNIX V4.0F(Rev.1229) on Tru64 H > 4.0. My company is using Dec C V6.0-001 on OpenVMS Alpha V7.2-1 on VMSE > 7.2 and Compaq C++ V6.2 for Tru64 UNIX on Tru64 5.0. I'm looking to-D > find out if there are any known problems related to the compilers,F > hardware or anything else that could affect real numbers. Has anyone4 > seen strange behavior like this with real numbers?  D The above implies that the customer is compiling something himself. E Are you sure he's not (accidently or deliberatel) using /D_float for t; his compilations? This might have the effect you're seeing.s   -- t Cheers - Dave.   ------------------------------  % Date: Sat, 07 Jul 2001 13:10:49 -0400a' From: Jim Becker <jbecker@ui.urban.org>i: Subject: Re: Some thoughts on the recent turn of events..., Message-ID: <3B474299.AFCFEDB2@ui.urban.org>  D Not exactly a reply to Ken's message -- I'm just swiping his subject line...   E Our organization was, before the recent turn of events, just about too@ buy another Alpha running OpenVMS. We're not a big shop, so thisF wasn't a trivial decision. We like VMS and we like the Alpha, but when= a vendor announces plans to discontinue one platform and port B "everything" to another platform to be made by some other company,? it's just good business sense for us to re-assess our decision.   C If we know that sooner or later the only way to go beyond the AlphaoF platform is to port to some other platform, why should we buy an AlphaA now? If we'll have to port anyway, we have to ask ourselves whichtD platform will be the most sensible one to port to, and when it would# make the most sense to do the port..  B I suspect we're going to buy this Alpha anyway, because we need itF sooner than we could port everything, but here are the sorts of things1 that would help us think we're not at a dead end:DF - Porting tools: We'd want to know that Compaq has a good set of toolsD and documentation to assist us in our Alpha/Itanium porting efforts.C We can cross our fingers that we'll like what comes out, and we can C cite historical precedent (VAX to Alpha), but that's not as good as # actually having the stuff in place.sA - Ease of porting: We'd like concrete, practical evidence that ifbD we're going to port anywhere, porting to VMS on the Itanium would beD the easiest port. Right now, we can guess that will be the case, butC since the operating system hasn't been ported, we're only guessing.t@ - Layered product rollout schedule: We'd like to see a specific,? product-by-product rollout schedule for VMS layered products on D Itanium. And of course we'd like to see the products we need on thatD schedule. Compaq's statements that it will port "everything" are notE very reassuring, because past experience has taught that "everything"eD really means "well, everything that we can get our hands on and that' we think is worth the time and effort." E - ISV support: We'd like to see concrete plans from the ISV communitytD saying they will stick with the VMS platform. Even better, we'd likeA to see new ISVs attracted to the VMS platform. So far, we haven'tnE heard much. Compaq's assurances that it wants lots of success on thisr front don't help much.E - Alpha support: We'd like to see that Compaq will be able to support0A the Alpha _well_ for as long as we keep Alphas around. Compaq has:A announced support will continue, but we don't know how strong and.0 committed (and affordable) that support will be.C - Delivery from Intel: We'd like to see some concrete evidence thataB Intel is really going to deliver sufficient quantities in a timelyE manner. So far, we can only test our faith in Intel's reliability and. consistency. Ahem.E - Server packaging: There's more to life than just the CPU. We'd liked? to see that Compaq's server packaging in the Itanium arena willwB produce worthy successors to the Alpha line, and not just "little" servers with faster chips.F - Market viability: Time will tell, but we'd like to see evidence that> VMS on Itanium will have sufficient presence and support to beB sustainable. I'm not asking for huge market share, but just enoughF presence and support to show that the patient is healthy and likely to live and evolve a while longer.t  B So where does this leave us? It leaves us crossing our fingers andD hoping that in a few years, we won't view our Alphas as albatrosses.C It leaves us hoping that Compaq and Intel are going to make good ono their plans and promises.$   --
 Jim Becker+ The Urban Institute (http://www.urban.org/)i' Encompass (http://www.encompassus.org/)4. ESILUG (http://encompasserve.org/lugs/esilug/)   ------------------------------  # Date: Sat, 07 Jul 2001 06:16:27 GMTg. From: "mulp" <michaelpettengill@earthlink.net>: Subject: Re: The death of VMS has been greatly exaggerated@ Message-ID: <%Ox17.25$qa6.2667@newsread1.prod.itd.earthlink.net>  ? "Robert Deininger" <rdeininger@mindspring.com> wrote in message F news:rdeininger-0607012153100001@user-2iveaga.dialup.mindspring.com...D > I guess that's good and bad news.  If they could port once by justJ > compiling, they can almost certainly port the module the same way again.0 > That's good, since it leads to a quicker port. >-: > The bad part is that they missed a chance to upgrade theL > quality/maintainability of these modules, and will probably miss many such > chances again this time.  I Very little investment was made to VAX tools and environment.  To rewriteiJ MACRO-32 into C would have not only been a lot of work, it would also have/ made the code non-common between the platforms.c  I And even a decade ago when resources were much more plentiful compared totC today, the resources were limited when it came to porting to Alpha.e   ------------------------------   Date: 7 Jul 2001 08:43:35 GMTs- From: djweath@attglobal.net (Dave Weatherall) : Subject: Re: The death of VMS has been greatly exaggerated5 Message-ID: <DTiotGxQ0bj6-pn2-ue4McZKypYvq@localhost>a  < On Fri, 6 Jul 2001 13:27:34, Arne =?iso-8859-1?Q?Vajh=F8j?=  <arne.vajhoej@gtech.com> wrote:g   > John Vottero wrote:aJ > > When I said "32 bit chip", I meant a chip that uses 32 bits to addressP > > physical memory.  I don't know how you really decide if a chip is 32, 34, 369 > > or 64 bit.  Maybe pick it up and look underneath?  :)t > C > I have never before heard about a definition of a CPU being X bit 2 > because it can access X bits of physical memory. > : > I think everyone consider VAX a 32 bit CPU. Its physical? > memory capabilities started below 32 bit and ended at 34 bit.O > @ > The X bit is virtual memory addressing capability not physical > memory addressing capability.o > 6 > The VAX virtual addres was 32 bit from start to end.  F I have always taken the view that the term 'nn-bit computer' referred F to its 'basic' register size. Z80/8080/6800 = 8 bit, pdp11/8086/6800 =6 16 bit, vax/80386/68020/ = 32 bit, Alpha,IA64 = 64bit.  5 The 8 bitters above had 16 bit adressing tho' (IIRC).7  D Alphas aren't quick because of an  ability to address 2*63 bytes of F memory (although that can bring an advantage to many applications). I F had the impression it was down to how it uses the 64bit registers and F the 64bit data bus to load/store 1 quad or 2 long or 4 word or 8 bytesD on one cycle. Hence, one of the needs for smart compilers. i.e. the & optimal arrangement of data in memory.   -- e Cheers - Dave.   ------------------------------   Date: 7 Jul 2001 10:00:26 CDTi= From: wayne@tachysoft.xxx.320117.killspam.015d (Wayne Sewell)d3 Subject: the tcp node name versus the vms node name . Message-ID: <jDtSEaHye7t6@tachxxsoftxxconsult>  M Do people generally create dns entries for vms machines matching the vms nodewL name?  In other words, if the result of f$getsyi("nodename") is bozo, is the2 fully qualified dns entry always bozo.domain.name?  O I personally don't see how one could function any other way, but there may veryt9 well be sites out there who don't follow this convention.c  L Since all of the vms stacks will automatically append the domain name to dns$ lookups as needed, I'm assuming that  # 	$ this_node = f$getsyi("NODENAME")  	$ nslookup 'this_node'o  L will always work, assuming the correct domain name (the one matching the dns, entries) has been configured into the stack.  O Is this an invalid assumption?  Are there sites out there in which the tcp nodeiL name minus domain is different from the vms node name?  If so, what would be the reason for doing this?  L Yes, I understand that the tcp node name can be longer than a vms node name,$ but is that worth all the confusion?     Wayneh   --  O =============================================================================== M Wayne Sewell, Tachyon Software Consulting  (281)812-0738  wayne@tachysoft.xxxc: http://www.tachysoft.xxx/www/tachyon.html and wayne.html  K change .xxx to .com in addresses above, assuming you are not a spambot  :-)DO ===============================================================================o? Flounder: "I can't believe I threw up in front of Dean Wormer."v>    Otter: "Face it, Flounder.  You threw up *on* Dean Wormer."   ------------------------------  % Date: Sat, 07 Jul 2001 13:40:07 -0400 ' From: Jim Becker <jbecker@ui.urban.org>o7 Subject: Re: the tcp node name versus the vms node names, Message-ID: <3B474977.7C84B2E2@ui.urban.org>   Wayne Sewell wrote:a > O > Do people generally create dns entries for vms machines matching the vms nodeiN > name?  In other words, if the result of f$getsyi("nodename") is bozo, is the4 > fully qualified dns entry always bozo.domain.name? [snip]  E It's been a near-universal rule in my experience, but I did deal witho@ one site that didn't follow that practice. Someone there got theB notion that giving a box the same name in all contexts was somehowC confusing. Odd. Before I got the hang of their nomenclature, I kept.B feeling like I was in _Through the Looking Glass_ (Lewis Carroll):  @   `Or else it doesn't, you know.  The name of the song is called "HADDOCKS' EYES."'  A   `Oh, that's the name of the song, is it?' Alice said, trying tos feel interested.  ?   `No, you don't understand,' the Knight said, looking a littlebA vexed.  `That's what the name is CALLED.  The name really IS "THEe AGED AGED MAN."'  ?   `Then I ought to have said "That's what the SONG is called"?'t Alice corrected herself.  >   `No, you oughtn't:  that's quite another thing!  The SONG is? called "WAYS AND MEANS":  but that's only what it's CALLED, your know!'  =   `Well, what IS the song, then?' said Alice, who was by thisr time completely bewildered.t  ?   `I was coming to that,' the Knight said.  `The song really IS.9 "A-SITTING ON A GATE":  and the tune's my own invention.'    --
 Jim Becker+ The Urban Institute (http://www.urban.org/)t' Encompass (http://www.encompassus.org/)-. ESILUG (http://encompasserve.org/lugs/esilug/)   ------------------------------   End of INFO-VAX 2001.374 ************************