1 INFO-VAX	Sun, 13 Jul 2003	Volume 2003 : Issue 383       Contents: DEC 3000 M 400 ASIC error  Re: DEC 3000 M 400 ASIC error + Re: Network Slowness related to packet size % Re: New lexical function F$DELTA_TIME  Re: PDP-11 OS Release Dates  Re: PDP-11 OS Release Dates  Re: PDP-11 OS Release Dates  Re: PDP-11 OS Release Dates  Re: PDP-11 OS Release Dates & Re: Slow Decnet Speeds, help requested@ TCP client program fails on TCP/IP Services, works with MultiNet Re: VMS to Windows 2000   F ----------------------------------------------------------------------    Date: 12 Jul 2003 13:33:15 -0500; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) " Subject: DEC 3000 M 400 ASIC error3 Message-ID: <3pSeoSIZDUgl@eisner.encompasserve.org>   E    I'm getting the following during the power on tests on my hobbyist     DEC 3000 M 400 Alpha:         ASIC ?? 002 0020  H    System boots and runs fine, just won't autoboot because of the error.  H    Anyone know what's wrong with this ASIC, what I can or need to do to !    prevent eventual hard failure?    ------------------------------  % Date: Sat, 12 Jul 2003 20:49:30 +0100 " From: "Gary" <gmcd@totalise.co.uk>& Subject: Re: DEC 3000 M 400 ASIC error. Message-ID: <beponi$mi6$1@news6.svr.pol.co.uk>   Bob,  @ I have DEC 3000/300 and the Hardware Reference Guide section 8-3 Console-Level Problems states   I ASIC - Ensure the proper seating of the CPU module and reexecute the ASIC  diagnostic to verify.   G Also the manual refers to a DEC 3000/300 Series AXP Service Guide for a K complete listing of the hex codes, their binary (LED) equivalent, and their K meaning. This suggests there is Service Guide for your model too? I checked D quickly on Google and found this reference which may be some further assistance?  It appears to be all there is.  D http://liberti.dhs.org/public/computing/hardware/dec3000/dec3000.pdf   HTH,   Gary.   H "Bob Koehler" <koehler@eisner.nospam.encompasserve.org> wrote in message- news:3pSeoSIZDUgl@eisner.encompasserve.org...  > G >    I'm getting the following during the power on tests on my hobbyist  >    DEC 3000 M 400 Alpha: >  >       ASIC ?? 002 0020 > J >    System boots and runs fine, just won't autoboot because of the error. > I >    Anyone know what's wrong with this ASIC, what I can or need to do to # >    prevent eventual hard failure?  >    ------------------------------  # Date: Sat, 12 Jul 2003 18:45:44 GMT % From: j_radnor@hotmail.com (J Radnor) 4 Subject: Re: Network Slowness related to packet size: Message-ID: <0IYPa.22335$Tx.1146300@news20.bellglobal.com>   Thanks for your reply Csaba.  N Yes it is a very repeatable test. I'm convinced it's hardware/network  related6 but thought I'd ask here in case anyone had any ideas.  I apologies for dual post, I used Google Post and didn't see first one, so  
 posted again.    John     > I >        I've run the above test between two our standalone nodes, thrice D >        actually, and the times were about 5 seconds for all tests.6 >        ( VMS 7.3-1, running default DECnet config. ) > K >        Might be some config issue at your site, or there might've been a  B >        network hiccup. Have you run your procedure a few times ? > H >                                                        Cheers,   Csaba > K > ------------------------------------------------------------------------- I >  CSABA I. HARANGOZO  |d|i|g|i|t|a|l|  csabah(at)zipworld(dot)com(dot)au K > ------------------------------------------------------------------------- < >   EARTH::AUSTRALIA:[SYDNEY]HARANGOZO.CSABA;1, delete? [N]: > % > When the going gets tough, upgrade.    ------------------------------  % Date: Sat, 12 Jul 2003 14:50:16 -0500 1 From: "David J. Dachtera" <djesys.nospam@fsi.net> . Subject: Re: New lexical function F$DELTA_TIME' Message-ID: <3F106677.4ED50A33@fsi.net>    Carl Perkins wrote:  > 3 > Following up my own post, since I made a mistake.  > N > Above I said "You are allowed to have a space in the hour filed if the first? > digit is a 0, but not anything else" but that is not correct.  > G > You can have a space in the hour field, as long as removing the space  > makes it a valid hour: > ; > $ write sys$output f$cvtime( "1 1:023:0045.67", "delta" )  > 0 11:023:0045.67  * WHOA!!! THAT looks like a major bug to me!  ; > $ write sys$output f$cvtime( "2 1:023:0045.67", "delta" )  > 0 21:023:0045.67 > ; > $ write sys$output f$cvtime( "3 1:023:0045.67", "delta" ) B > %DCL-W-IVDTIME, invalid delta time - use DDDD-HH:MM:SS.CC format >  \3 1:023:0045.67\ > G > This failed because there are not 31 hours in the day. In the various D > examples with non-zero first dgits from other people up above theyC > attempted 3 digit hours (with a space before the last two), which ! > is why they didn't work. [snip]    --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------    Date: 12 Jul 2003 13:21:59 -0500; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) $ Subject: Re: PDP-11 OS Release Dates3 Message-ID: <J8WpLCPkzI96@eisner.encompasserve.org>   E In article <beon58$gl9$1@bob.news.rcn.net>, jmfbahciv@aol.com writes:  > A > Speculation:  I think it would have been difficult to trademark " > a generic name like OS-whatever.  B    Didn't stop IBM from selling OS 360/whatever for lots of years.   ------------------------------  % Date: Sat, 12 Jul 2003 16:23:59 -0400 . From: Glenn Everhart <Everhart-nospam@gce.com>$ Subject: Re: PDP-11 OS Release Dates+ Message-ID: <bepocl$m92$1@bob.news.rcn.net>   D I seem to recall some discussions of an "OS-11" code name inside DEC? fpr RT11, which was initially often thought of and spoken of as  "OS-8 with the interrupts on".  C DOS-11 existed from the earliest pdp11s,  starting maybe 1971 or so F and by 1976 it was up to V10, used a variant of the RSX11D taskbuilderE as its linker, and had a fair bit of software in the DECUS library to F do interesting stuff with it. It was used to boot early RSTS and some I other pdp11 OSs and its internals had somewhat in common with RSX11C and  8 later RSX11B. (RSX11A was an entirely different animal.)E The main problem DOS had was that it used .read and .write calls for  H most of its I/O. While its low level I/O was reasonably fast, .read and G .write did at least scores if not hundreds of instructions per byte in  I formatting and checking for all the funny options those services had. As  H a result when RT11 came along, and had apps do their own I/O, it looked F blindingly faster. A decent record system in DOS would of course have  equalized this.   - I sometimes think of RMS when recalling this.    Glenn Everhart     Paul Sture wrote: ^ > In article <110720032007475862%elliott@yrl.co.uk>, Elliott Roper <elliott@yrl.co.uk> writes: > A >>In article <bekbut$3m2$1@aton.pcde.inka.de>, Dennis Grevenstein  >><dennis@pcde.inka.de> wrote: >> >>4 >>>In alt.sys.pdp11 healyzh@noaracnetspam.com wrote: >>> K >>>>Is OS-11 related to RT-11?  I think this is the first I've heard of it.  >>>  >>> 2 >>>It's mentioned in some RT-11 guide I have here. >>>I don't know it myself. >>E >>It has been a long time, so I might be wrong. ISTR there was not an H >>OS-11 but there was a DOS-11 in the very early PDP-11 days. There were! >>remnants of it in the RSTS CIL.  >>, >>Yep. I found this on Deja-Google from 1994 >>J >>http://www.google.com/groups?q=DOS-11&start=10&hl=en&lr=&ie=UTF-8&safe=o2 >>ff&selm=940927100650.62%40arisia.gce.com&rnum=13 >># >>If Everhart said it, it is right.  >>F >>Show complete thread when you get there. Some famous names are still >>around here. >  > I > Thanks for that link. It brought back fond memories of RT-11, including 4 > ones of RSX feeling tardy at times in contrast :-)   ------------------------------  ( Date: Sat, 12 Jul 2003 22:59 +0100 (BST)9 From: duncan@macdonald.compulink.co.uk (Duncan Macdonald) $ Subject: Re: PDP-11 OS Release DatesA Message-ID: <memo.20030712225940.1144A@macdonald.compulink.co.uk>   J When did the PDP-11 diagnostic supervisor (XXDP if my memory is correct - B been many years since I last used it) first see the light of day ?' And what (if anything was it based on).    ------------------------------  % Date: Sat, 12 Jul 2003 18:46:06 -0400 * From: "Stanley F. Quayle" <stan@stanq.com>$ Subject: Re: PDP-11 OS Release Dates- Message-ID: <3F10576E.20544.6182BA@localhost>   E While everyone's remembering their PDP-11 experiences, this might be  B a good time for a Shameless Plug (tm) for CHARON-11 -- the PDP-11 = version of CHARON-VAX.  There are still PDP-11's out there...   
 --Stan Quayle  Quayle Consulting Inc.  
 ----------C Stanley F. Quayle, P.E. N8SQ  +1 614-868-1363  Fax: +1 614 868-1671 1 8572 North Spring Ct. NW, Pickerington, OH  43147 = Preferred address:  stan@stanq.com       http://www.stanq.com    ------------------------------  % Date: Sat, 12 Jul 2003 20:24:42 -0400 . From: Glenn Everhart <Everhart-nospam@gce.com>$ Subject: Re: PDP-11 OS Release Dates+ Message-ID: <beq6gm$p36$1@bob.news.rcn.net>    Duncan Macdonald wrote: L > When did the PDP-11 diagnostic supervisor (XXDP if my memory is correct - D > been many years since I last used it) first see the light of day ?) > And what (if anything was it based on). ? XXDP was a continuation of the old PTS (paper tape diagnostics) : suite enabled for magtape. Had a little in common with DOSA (DOS-11) for appearance but was its own thing internally. I first B saw it c. 1972 (since I was working with a group that had bought aA pdp11/45 with no paper tape anywhere). It was pretty new then and @ DEC field service had trouble with diagnostics initially becauseA not all that much had been moved to tape at first. (They went and 3 borrowed an ASR33 teletype for that stuff for us..)    ------------------------------  # Date: Sat, 12 Jul 2003 19:11:43 GMT % From: j_radnor@hotmail.com (J Radnor) / Subject: Re: Slow Decnet Speeds, help requested : Message-ID: <r4ZPa.22350$Tx.1150035@news20.bellglobal.com>  = Thanks Colin, will take your suggestions to our Network guys.    Appreciate the reply.   M Apologies for the dual post, as I used Google Post and couldn't see my first   article, so posted again.    John    N In article <piBPa.8483$8g6.65105117@news-text.cableinet.net>, "Colin Butcher" 2 <colin_DOT.butcher_AT@xdelta_DOT.co_DOT.uk> wrote:K >Could be lots of things. Start by substituting a piece of cross-over cable 8 >for the corporate network, then build it up from there. > H >Check that everything is self consistent at both ends - DECnet settingsL >(pipeline quota, segment size, segment buffer size, line buffers to maximum >....).  > > >Check system performance at both ends (CPU,, IO Memory etc.). > D >Check ethernet adapter speed & duplex settings - don't rely on autoM >negotiation. Set 100Mbit/sec full duplex explicitly on the Alphas and on the 
 >switches. > > >Consider using DECnet-Plus (Phase V) to get more information. > L >Consider using a network protocol and traffic analyser (you'll need to turn >on switch port mirroring).  >  >Lots to work through. > < >Maybe even call for outside help to come and work with you. > B >----------------------------------------------------------------- >Hope this helps, Colin.* >colin DOT butcher AT xdelta DOT co DOT ukM >Systems Archaeologist - Investigation & troubleshooting of older systems and 
 >networks. >  >  >  >    ------------------------------  % Date: Sun, 13 Jul 2003 12:58:01 +0930 % From: Jeremy Begg <jeremy@vsm.com.au> I Subject: TCP client program fails on TCP/IP Services, works with MultiNet * Message-ID: <3F10D1C1.1838D013@vsm.com.au>   Hi,   M I'm working on a control program to run under OpenVMS Alpha, which interracts M with an ethernet/serial communications board made by Moxa Technologies (their  DE-311M board,N http://www.moxa.com/product/Serial_Device_Servers/Embedded/NPort_DE_311M.htm).  L The Moxa board, configured in "TCP Server" mode, passes whatever it receivesL on a TCP port straight out to its serial port.  I've configured the board soM that anything it receives on the serial port is sent out the network when the I serial port receives a CR character.  For testing, I've set up a loopback L connector and VT420 terminal on the serial port (so that I can see the bytes coming out of the serial port).   M My control program is compiled with Compaq C V6.5-001 on OpenVMS Alpha V7.3.  L It opens a connection to the Moxa board (with TCP_KEEPALIVE set) and in testM mode sends lines of random text, using the send() routine.  Each line is from K 1-128 bytes plus a trailing CR.  After sending the string it reads from the K network using the recv() routine and compares what it received with what it  sent.   N When I test it on the same system it was compiled on, which is an AlphastationM 255/300 running TCP/IP Services 5.1 ECO 4, it works for a while (1-3 hours or D so) before failing; in every case, the recv() routine returns -1 andF strerror(errno) returns "connection timed out".  The data on the VT420L terminal indicates that the last command sent by the test program never madeH it to the Moxa's serial port; either the Moxa dropped the packet, or theJ packet never made it to the Moxa board.  If the program closes the networkN connection and opens a new one, it carries on sending & receiving commands for' another few hours before failing again.   N As it happens, I have a pair of Alphaservers running MultiNet so I thought I'dF try running it there.  On my Alphaserver 800 running OpenVMS V7.3 withM MultiNet 4.4, the program has been running for over 21 hours without a single  error.  L This would seem to indicate a problem in either the TCP/IP Services stack orB the built-in Ethernet port on my Alphastation.  However I use thisL Alphastation as my "home" machine (to receive email etc) and haven't noticed# random hangs in other applications.   J The eventual target system for this application is running MultiNet so I'mM hopeful that it will work properly there too.  But I'm worried that I haven't , found the cause of the failure, only a cure.  A Has anyone had a similar experience, which they were able to fix?    Thanks,            Jeremy Begg   =   +---------------------------------------------------------+ =   |            VSM Software Services Pty. Ltd.              | =   |                 http://www.vsm.com.au/                  | =   |       "OpenVMS Systems Management & Programming"        | =   |---------------------------------------------------------| =   | P.O.Box 402, Walkerville, |  E-Mail:  jeremy@vsm.com.au | =   | South Australia 5081      |   Phone:  +61 8 8221 5188   | =   |---------------------------|  Mobile:  0414 422 947      | =   |  A.C.N. 068 409 156       |     FAX:  +61 8 8221 7199   | =   +---------------------------------------------------------+    ------------------------------  % Date: Sat, 12 Jul 2003 17:47:18 -0400 . From: Glenn Everhart <Everhart-nospam@gce.com>  Subject: Re: VMS to Windows 2000+ Message-ID: <bept8r$3r2$1@bob.news.rcn.net>   E Most likely the .doc files are something sensible on VMS (ASCII text? < VMS Document? DECwrite?), the .exe files will be VMS images,D and in general the extensions tell nothing at all about what programG should open the files. The file attributes are stored elsewhere in VMS, B in file headers. Trying to infer file attributes from part of the  filename is a Windows-ism.  E Zip is a decent way to move files between windows and VMS, within the E limitations of the record (!!??) structures Windows understands. Some D file types (e.g., .OBJ) will be garbled and Windows will go through G ridiculous gyrations on some others (.mar for example) but at least you H can get mostly-usable representations of the data over. Making sense of B it is a different problem. Lotsa luck trying, for example, to get I anything on Windows to understand a DECWrite file natively. (If you have  C the format converters, DECwrite can be made to create an .rtf that  F Windows will understand, though the reverse does not in general work.)  I If someone ports openoffice to VMS, I expect some of this tower of Babel   to get easier to deal with.  Jim Strehlow wrote:   ] > "KC" <kevin.n.coyle@compaq.com> wrote in message news:<7AAPa.73$E%3.42@news.cpqcorp.net>...  > M >>I just became involved in converting an existing application that exists on L >>VMS to a brand new application that is running on windows 2000. One of theK >>features of the old vms application was that it contained many attachment L >>files (such as .doc, .jpeg, .bin?, .exe???) that the users wish to migrate0 >>over to the new application on windows 2000... >  > . > Those may be valid Windows-compatible files.? > Some developers and users who liked PATHWORKS created OpenVMS B > directories accessible by Microsoft Windows 98 and Windows 2000.E > The developer/user mapped a Microsoft Windows directory to OpenVMS.  > 4 > So the .doc may well be a Microsoft Word document.' > The .jpeg files may well be pictures.  > C > To mass move the files off of OpenVMS elsewhere, you might use an E > OpenVMS ZIP utility, file transfer the files to a Microsoft Windows C > 2000 box using any one of several VT100 OpenVMS emulator software ) > programs (smartTerm, Reflection, etc.), * > and unzip on your Windows 2000 computer. > ( > JH Strehlow, Data911, Alameda, CA, USA   ------------------------------   End of INFO-VAX 2003.383 ************************