1 INFO-VAX	Tue, 14 Oct 2003	Volume 2003 : Issue 569       Contents:( Re: "Old" patch site no longer updated !( Re: "Old" patch site no longer updated !( Re: "Old" patch site no longer updated !( Re: "Old" patch site no longer updated ! Re: %MOUNT-W-INCONSIZE, Anyone interested in a media player for VMS?$ Re: anyone running 7.3-1 with 64 MB?$ Re: anyone running 7.3-1 with 64 MB?3 Re: Convert C file descriptor to VMS channel number A Re: DII COE and C Portability (was: Re: If HP had any brains ...) - Re: ITRC Patch Download FAQ for OpenVMS users # Re: Laptop, Reflections, delete key  Re: Latest VMS Critical Upgrade  Re: MD5 source code ?  Re: MD5 source code ?  Re: MD5 source code ?  nagios plugin for vms  Re: ODBTP on VMS ? Re: PMGC-B card on DEC3000/M600  Re: PMGC-B card on DEC3000/M600  Re: PMGC-B card on DEC3000/M600  Re: Sickening, isn't it?& Re: Slow Shadow Copy with 36 GB drives' submitting a VMS batch job from Windows A RE: TCPIP anti-spam mechanisms (was: Latest VMS Critical Upgrade) E Re: RE: TCPIP anti-spam mechanisms (was: Latest VMS Critical Upgrade) E RE: RE: TCPIP anti-spam mechanisms (was: Latest VMS Critical Upgrade)  TCPIP versions and patches Re: TCPIP versions and patches Re: TCPIP versions and patches) The Uptimes Project -- VMS does very well - Re: The Uptimes Project -- VMS does very well - Re: The Uptimes Project -- VMS does very well - Re: The Uptimes Project -- VMS does very well = Re: The VAX/VMS to Itanium Migration Letter, Vol. 1 Number 1. = RE: The VAX/VMS to Itanium Migration Letter, Vol. 1 Number 1. % VMS decc FreeTDS compilation question ) Re: VMS decc FreeTDS compilation question ( Re: where to buy memory for DEC3000/M3008 Re: White paper: CHARON-VAX cluster w/ shared SCSI disks8 Re: White paper: CHARON-VAX cluster w/ shared SCSI disks8 Re: White paper: CHARON-VAX cluster w/ shared SCSI disks  F ----------------------------------------------------------------------  # Date: Mon, 13 Oct 2003 19:04:38 GMT # From: hoff@hp.nospam (Hoff Hoffman) 1 Subject: Re: "Old" patch site no longer updated ! 2 Message-ID: <aHCib.6936$_y1.1859@news.cpqcorp.net>  S In article <bmb7rq$ehd$1@news1.tilbu1.nb.home.nl>, Dirk Munk <munk@home.nl> writes: 4 :In case you still check the "old" compaq patch site : 6 :http://ftp.support.compaq.com/patches/public/vms/axp/ : Q :for new patches, then please be advised that new patches are no longer added to   :this site!  : 7 :You will have to go to the new software & patches site   E   Please review recent discussions of this topic here in comp.os.vms.   J   George Pagliarulo posted a large write-up (FAQ) on this topic within the   last week or two.   J   I've recently updated and regenerated the OpenVMS FAQ for release duringI   October (this month), for various and sundry reasons including the ECO  K   URL change-over to itrc -- well, and also including various other new and I   changed URLs, new Freeware, new OpenVMS releases, and other reasons for     the FAQ update, but I digress.  J :I tried the 'zipped' patch retrieval, but that was no success. I did not A :get the full kit, after some time the transmission just stopped.  : ( :Using 'right-click on ftp' worked fine. : N :Furthermore it is not possible to sort the patches by date, nor is the patch N :publication date visible on the search page. Both ommisions are quite a pain.S :I already complained about this yesterday, so we'll have to wait for the response.   *   Here are the two URLs involved for this:       http://www.itrc.hp.com*     ftp://ftp.itrc.hp.com/openvms_patches/  N   If you have a firewall that requires it, you may need to enable passive-mode)   FTP transfers to access the patch site.   J   Dig up George's posting (via Google newsgroup search, or otherwise) for     far more detailed information.    N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faq N  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.com    ------------------------------  # Date: Mon, 13 Oct 2003 21:37:10 GMT 2 From: "George Pagliarulo" <georgepag@adelphia.net>1 Subject: Re: "Old" patch site no longer updated ! 2 Message-ID: <aWEib.6949$QE1.5475@news.cpqcorp.net>  J The old site IS still supported and patches are being added.  What you areK seeing that was not visible before is the lag time in getting a patch up on K the old site.  It often takes 2 to 3 days or more for it to appear from the H time it is released by VMS.  With the new site, the time from release to posting is less than 24 hours.   George      + "Dirk Munk" <munk@home.nl> wrote in message , news:bmb7rq$ehd$1@news1.tilbu1.nb.home.nl...5 > In case you still check the "old" compaq patch site  > 7 > http://ftp.support.compaq.com/patches/public/vms/axp/  > H > for new patches, then please be advised that new patches are no longer added to > this site! > 8 > You will have to go to the new software & patches site >  > http://www1.aclabs.com/  > 6 > to get the latest patches for (at least) VMS 7.3-1 . > J > I tried the 'zipped' patch retrieval, but that was no success. I did not get the : > full kit, after some time the transmission just stopped. > ) > Using 'right-click on ftp' worked fine.  > H > Furthermore it is not possible to sort the patches by date, nor is the patch I > publication date visible on the search page. Both ommisions are quite a  pain. J > I already complained about this yesterday, so we'll have to wait for the	 response.  >    ------------------------------  + Date: Mon, 13 Oct 2003 22:47:05 +0000 (UTC) P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)1 Subject: Re: "Old" patch site no longer updated ! $ Message-ID: <bmfa19$ncv$1@online.de>  F In article <aWEib.6949$QE1.5475@news.cpqcorp.net>, "George Pagliarulo"! <georgepag@adelphia.net> writes:    L > The old site IS still supported and patches are being added.  What you areM > seeing that was not visible before is the lag time in getting a patch up on M > the old site.  It often takes 2 to 3 days or more for it to appear from the J > time it is released by VMS.  With the new site, the time from release to  > posting is less than 24 hours.  E How long will this continue to be the case (i.e. that it is updated)?    ------------------------------  + Date: Mon, 13 Oct 2003 22:48:27 +0000 (UTC) P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)1 Subject: Re: "Old" patch site no longer updated ! $ Message-ID: <bmfa3r$ncv$2@online.de>  G In article <aHCib.6936$_y1.1859@news.cpqcorp.net>, hoff@hp.nospam (Hoff  Hoffman) writes:    L >   I've recently updated and regenerated the OpenVMS FAQ for release duringK >   October (this month), for various and sundry reasons including the ECO  M >   URL change-over to itrc -- well, and also including various other new and K >   changed URLs, new Freeware, new OpenVMS releases, and other reasons for " >   the FAQ update, but I digress.  , >   Here are the two URLs involved for this: >  >     http://www.itrc.hp.com, >     ftp://ftp.itrc.hp.com/openvms_patches/  4 Thanks for the pointers (especially the second one).   ------------------------------  # Date: Mon, 13 Oct 2003 21:53:45 GMT 1 From: Bob Blunt <robert.blunt@hp.donotspamme.com>  Subject: Re: %MOUNT-W-INCONSIZE 2 Message-ID: <J9Fib.6950$DI1.2659@news.cpqcorp.net>  / Phillip Helbig---remove CLOTHES to reply wrote: > > In article <liCgb.6512$px1.6029@news.cpqcorp.net>, Bob Blunt, > <robert.blunt@hp.donotspamme.com> writes:  >  > I >>Phillip, to which connector on the "big block" is your BA350 attached?   >  >  > To the DSSI connector. >  > D >>If connected to the Centronics, I'm surprised that you're getting H >>DSSI-type disks...  If connected to one of the other connectors, then G >>all bets are off, IMHO.  The two really big connectors in the center  I >>with the three rows of pins/sockets are for Q-Bus expansion (using and  4 >>configuring the Q-Bus can be an "adventure," btw). >  > J > Right.  As the old saying goes (allegedly advice of an English nobleman F > to his son), try everything once---except incest and folk dancing.  1 > Perhaps QBUS should be added to that list!  :-)  >  > G >>IIRC, there were some VAX4000-10x systems that were either available  I >>with an embedded HSD05/HSD10s or the HSDs were an option.  This option  K >>would consume one of the internal drive slots on the "top shelf" and the  H >>internal drives would probably then be SCSI instead of DSSI.  None of J >>the "embedded" HSD controllers were intended to be extended to external J >>devices.  I believe the model number of this HSD was HSD10-EN and these K >>seem to have been more common on newer variants of the 4000-10x like the   >>-106(A) and -108(A). >  > K > That seems to be what I have.  There appears to be an internal DSSI bus,  K > which works fine, and the external one via the big plug on the back, the  I > one which also has SCSI and QBUS connectors.  I am hoping to use the 6  I > disks in the BA350 via DSSI and a further set of disks on the SCSI bus.   F Um, So you have SCSI disks directly attached to the DSSI connector on C the back of the VAX4000-100, correct?  That just seems loaded with  I potential problems...  To be honest, I'm suprised the disks "show up" at  F all.  Unless you obtain a HSD05 or HSD10 and mount it into the BA350, H those disks aren't ever going to work properly because the disks aren't F "native" DSSI and any internal HSD isn't configured to drive external  SCSI disks.   E Basically, without a HSD between those BA350 disks and the VAX, it's  F unsure how they'd show up to the system (or how they're going to work G properly).  For the short-term, I'd recommend trying to locate a cable  E to hook to the Centronics-style SCSI connector for testing purposes.  G For long-term connection to the DSSI, I'd try to find a HSD05 or HSD10  F to plug into the BA350 or try to find a controller shelf with a HSD30  (or 40 or 50).   bob    ------------------------------  % Date: Mon, 13 Oct 2003 12:58:38 -0700 0 From: Mark Berryman <Mark.Berryman@Mvb.Saic.Com>5 Subject: Anyone interested in a media player for VMS? ' Message-ID: <3f8aa17e$1@cpns1.saic.com>   G I have ported mplayer (the media player for Linux systems) to VMS.  It  E is capable of playing a wide-range of audio/video formats, including  I acting as a DVD player.  Unfortunately, most of the optimizations in the  H code assume a GNU C compiler and an Intel/AMD hardware platform.  There E are only a handful of Alpha optimizations.  The result is video that  " plays too slowly, even on my DS10.  I Right now I am looking at finding all of the code that was optimized for  D MMX and writeing a version optimized for Alpha.  I was wondering if A there was anyone out there willing to lend a hand with this.  My  G understanding of the Alpha instruction set is sufficient to read crash  I dumps but doesn't really extend to a knowledge of instruction latency or  A scheduling.  (I do have a copy of the Alpha Architecture manual).   A I've also discovered that Motif V1.3 includes a Direct-Rendering  G extension.  Can anyone point me to any info on how to make use of this?    Thanks,   
 Mark Berryman   H P.S.  If there are any Motif for VMS maintainers reading this, it would I be really helpful if VMS supported the Xv extension.  This appears to be  E how Linux on Alpha is able to get such good performance with mplayer  C since, among other things, it eliminates the need for a YUV to RGB   conversion.    ------------------------------  + Date: Mon, 13 Oct 2003 22:52:11 +0000 (UTC) P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)- Subject: Re: anyone running 7.3-1 with 64 MB? $ Message-ID: <bmfaar$ncv$3@online.de>  F In article <yeBib.6920$9e1.771@news.cpqcorp.net>, hoff@hp.nospam (Hoff Hoffman) writes:    J > :I have an ALPHAstation 255/233 with 64 MB at 7.2-1.  I plan to upgrade K > :to 7.3-1 soon, possibly this weekend.  Is anyone actually running 7.3-1  ) > :with just 64 MB?  Is it even possible?  > C >   The SPD has the official supported minimum memory requirements.   . Does anyone have a valid, direct link offhand?  C I just wasted a lot of time at http://ftp.itrc.hp.com/ so am a bit  H frustrated.  Why is the official source of VMS patches not visible from F the VMS machines which need those patches?  The site recommends IE or G Netscape, new versions, neither of which exists for VMS.  It does work  @ with Mozilla (from VMS).  However, there is no Mozilla for VAX. H (Thankfully, I have VAXes and ALPHAs clustered; that makes life easier.)  = I finally got to ftp://ftp.itrc.hp.com/openvms_patches .  :-|   > I would have appreciated the gesture of a direct link to this.  I [Since originally writing this post, I have seen Hoff's comments that he  I put the URL in the FAQ etc.  Thanks and keep up the good work!  I though  H it best to keep my original whining tone, though.  I have to say that I + find the HP web pages very badly designed.]   F Plus: 2 instead of 4 files per patch (no checksum and just one format @ for the readme).  Mailing list (digest or individual) for patch ; notifications.  Minus: 7.3 and 7.3-1 in the same directory.   G >   Performance can be _way_ better with free memory.  OpenVMS VAX runs F >   better with free physical memory.  OpenVMS Alpha runs *far* better >   with free memory available.    I DO plan to buy some!  M >   If you can get a newer (and faster) Alpha box for little or no additional O >   cash outlay, rather than upgrading the memory within this 233 MHz EV45 box?   I I've spent a lot of money (for a hobbyist) on hardware recently.  I WILL  G give a good home to fast machines which consume little power!  :-)  On  I the other hand, most of what I do doesn't need that many resources.  I'm   more concerned with stability.  F Back to the URLs: I plan to update all of my bookmarks soon.  Many of I these are to DEC/Compaq URLs which don't work anymore.  Does anyone have  - any idea how stable the current HP links are?   G It seems to me to be a bad idea to have something like WWW7 show up in  @ the URL.  Will it ALWAYS be WWW7?  This is what one gets if one   bookmarks the URL as it appears.  H Perhaps this is an attempt to force one to look at ads for printers and 	 what not.   G I did think twice when entering an email address for signing up to the  G patch stuff.  I remember someone mentioned on comp.os.vms a while back  H that he started getting spam to an address he had only used for private E correspondence with DEC/Compaq/HP.  I hope that doesn't happen to me.    ------------------------------  # Date: Tue, 14 Oct 2003 01:42:23 GMT 5 From: rdeininger@mindspringdot.com (Robert Deininger) - Subject: Re: anyone running 7.3-1 with 64 MB? L Message-ID: <rdeininger-1310032152040001@user-uinj0g2.dialup.mindspring.com>  D In article <bm8tp1$guf$3@online.de>, helbig@astro.multiCLOTHESvax.de1 (Phillip Helbig---remove CLOTHES to reply) wrote:   H >I have an ALPHAstation 255/233 with 64 MB at 7.2-1.  I plan to upgrade I >to 7.3-1 soon, possibly this weekend.  Is anyone actually running 7.3-1  ' >with just 64 MB?  Is it even possible?   D I've run V7.3-1 on clustered DEC 3000-400 systems with 64 MB in eachI system.  It worked.  (Some cluster diagnostic/tracing code would not work  properly, however.)    96 MB is far more comfortable.   ------------------------------  % Date: Mon, 13 Oct 2003 12:26:42 -0700 0 From: Mark Berryman <Mark.Berryman@Mvb.Saic.Com>< Subject: Re: Convert C file descriptor to VMS channel number' Message-ID: <3f8a9a02$1@cpns1.saic.com>    Hoff Hoffman wrote: \ > In article <3f86c4a8$1@cpns1.saic.com>, Mark Berryman <Mark.Berryman@Mvb.Saic.Com> writes:I > :I am in the process of making a program written for Unix available on  H > :VMS.  As part of this, I need to write the VMS version of some IOCTL J > :calls.  I'm not allowed to touch what the Unix code hands me (which is J > :an Integer File Descriptor from an open call), nor would modifying the H > :open call be practical since it is all the calls to IOCTL that would . > :need to change, not the result of the open. > E >   The open call can optionally give you back the FAB and RAB, which G >   is what you need here and what C utilizes to access the files -- if E >   you don't modify the calling code but can jacket/#define the open E >   calls into your own open calls, you can then add the acc= routine / >   call which returns the RMS data structures.   B Unfortunately, I have since learned that I can be passed STDIN or < STDOUT.  In other words, there is no open call to intercept.  C >   If one of the C engineers see this, they might know of a way to E >   directly convert the fd to a channel -- I don't.  AFAIK, there is C >   no API into this stuff -- for typical file I/O, C uses RMS, and C >   leaves RMS to manage the I/O channels.  AFAIK, C itself doesn't 2 >   know the I/O channel involved, in other words.  G I hope one of them does.  Finding some way to translate the FD appears   to be my only option.    > D >   Short of opening a parallel channel or getting the ioctl() callsD >   added into what OpenVMS provides -- or using the jackets or such* >   -- you are unfortunately rather stuck.  B Please consider this a wish to implement the raw SCSI ioctl call. G (You're not busy doing anything else right now, right? (meager attempt   at humor here)).  
 Mark Berryman    ------------------------------  # Date: Mon, 13 Oct 2003 19:59:03 GMT # From: hoff@hp.nospam (Hoff Hoffman) J Subject: Re: DII COE and C Portability (was: Re: If HP had any brains ...)2 Message-ID: <buDib.6940$_y1.5107@news.cpqcorp.net>  g In article <3F8ABF8E.2091B044@blueyonder.co.uk>, Tim Llewellyn <tim.llewellyn@blueyonder.co.uk> writes:  :  :  :Bob Ceculski wrote: :>  ? :> now that VMS has coe functionality, they would save a ton of > :> money by forgetting the tur64 to hp unix port and just port@ :> everything to OpenVMS itanium ... like I said if they had any
 :> brains ...  : ? :Bob, have you considered "their" objectives might be different 
 :to your own?   F   Folks like choices, and we have OpenVMS I64 on Integrity, as well asG   having HP-UX, Linux, and Microsoft Windows available on the platform.   H   Features of Tru64 UNIX are being integrated into HP-UX, and various of6   these features have also found their way into Linux.  I   As for OpenVMS and the DII COE work, DII COE has a very specific target F   audience and target market and I know that the folks here in HP thatI   sell into the market have provided these details to many of our current G   and our potential  OpenVMS customers.  We've shown DII COE at various G   tradeshows, for instance, and at more general OpenVMS events where we J   happen to know various of the industry-related folk are in attendence.    I   I've certainly been talking about DII COE for some years now in various H   of my presentations, specifically the V7.2-6C1 and V7.2-6C2 releases, J   and references to the integration of various of the features from these F   releases into V7.3-1 and later.  I know that the product manager forI   the portability work has been discussing it for several years now, too.   J   What most folks here might think of when DII COE is referenced (and whatJ   I expect Bob Ceculski is referencing) is more akin to POSIX and the moreJ   current and more recent work on GNV and bash and the C run-time library,I   and I don't see that being a big advertising point -- on its own.  Most J   customer folks are interested in and will be using pieces of the DII COEJ   work, but most folks aren't nearly as interested in its entirety; in theH   other parts of the work -- few folks here are probably planning to useH   the COE segment installer, for instance.  I believe that most folks doH   and will want specific tools and utilities and programming interfaces.  (   For DII COE details involving OpenVMS:  A     http://h71000.www7.hp.com/solutions/government/coe/index.html   F   For details on GNV and related Portability work within OpenVMS, see:  2     http://h71000.www7.hp.com/portability/gnv.html  J   There is certainly an overlap here among the DII COE and the portabilityH   work and the features, but I'd expect more folks here really want the    portability work.   N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faq N  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.com    ------------------------------  # Date: Mon, 13 Oct 2003 17:59:12 GMT , From: "warren sander" <warren.sander@hp.com>6 Subject: Re: ITRC Patch Download FAQ for OpenVMS users2 Message-ID: <QJBib.6927$Br1.4402@news.cpqcorp.net>   Best I can do is:   < http://h71000.www7.hp.com/serv_support.html has a pointer toH http://h71000.www7.hp.com/itrc_patch_download_faq.html which is the FAQ.   -warren    --  K --------------------------------------------------------------------------- 7 Warren Sander                   WW E-Marketing (HP.COM) B Hewlett-Packard Company         Work:  warren.sander@remove.hp.comK 200 Forest Street MR01-3/K8     Personal: sander.ma.ultranet@remove.rcn.com . Marlboro, MA 01752              (508) 467-48755    My opinions are my own and I only speak for myself *          Read http://www.hp.com/go/openvmsK ---------------------------------------------------------------------------     3 "David M Smith" <dsmit115@csc.com> wrote in message 2 news:13olov4tgu1abaqodq8npbckum69d3gooa@4ax.com...7 > On Thu, 02 Oct 2003 18:52:25 GMT, "George Pagliarulo"  <georgepag@adelphia.net> > wrote: > G > >   I've compiled the questions and comments I've received from users  about J > >the new ITRC patch download site into an FAQ.  Hopefully this will help the G > >transition to the new site go smoother and answer a lot of lingering 
 > >questions.  > >  > >George Pagliarulo > >Hewlett-Packard Company > J > Thanks for putting this together -- can you also post it on the ITRC web site? I L > spent awhile trying to find it there today, with no success. My best guess was 0 > the FAQ section on the site but no luck there.K > ------------------------------------------------------------------------- K > David M. Smith 302.391.8533                       dsmit115 at csc dot com K > Computer Sciences Corporation     (Opinions are those of the writer only) K > -------------------------------------------------------------------------    ------------------------------  % Date: Mon, 13 Oct 2003 20:27:04 -0500 1 From: "David J. Dachtera" <djesys.nospam@fsi.net> , Subject: Re: Laptop, Reflections, delete key' Message-ID: <3F8B50E8.72C95917@fsi.net>    "Bradford J. Hamilton" wrote:  > ] > In article <3F89E43C.580D0D99@fsi.net>, "David J. Dachtera" <djesys.nospam@fsi.net> writes:  > !snip! > ! D > !Reflection (singular, see the title bar of the product window for< > !verification) is still the Cadillac of terminal programs. > D > I must humbly disagree.  Kermit has more features, at lower cost.   6 Of course, Kermit is not primarily a terminal program.  C You'll likely also find that Reflection/2 and /4 are about the only F terminal programs on the market that do smooth scrolling (where that's4 important - most folks don't need or care about it).   --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------  + Date: Mon, 13 Oct 2003 22:51:30 -0500 (CDT)  From: sms@antinode.org( Subject: Re: Latest VMS Critical Upgrade) Message-ID: <03101322513008@antinode.org>    From: Roy Omond <Roy@Omond.net>   D > > [... add a hook to TCPIP to allow manager/user configured e-mail > > message rejection ...] > > + > >    Easy?  Hard?  Troublesome?  Useless?  > 8 > Easy. It's already available, and it's called DELIVER.  3    Not exactly.  As the DELIVER documentation says:   J     (1)  DELIVER changes the "From:" address of any message it delivers orJ          forwards  to  the address of the owner of the MAIL.DELIVERY file.J          The original "From:" address is not lost entirely -- it is merged5          into the subject line of the message.  [...]   G I'd like to keep the From address intact, for obvious reasons (REPLY).    F    DELIVER is handy for automating some stuff, but, unless I'm missingE the obvious (again), it seems to do too much damage to a mail message  for convenient, normal use.   G    Also, I notice that DELIVER_STARTUP.COM always uses INSTALL REPLACE, E which causes warnings if the image is not already installed.  This is G easy to fix by testing f$file_attributes( image, "KNOWN") and using ADD % or REPLACE as appropriate, of course.   H    Also, DELIVER_STARTUP.COM seems to re-install SYS$SYSTEM:MAIL.EXE andH SYS$SYSTEM:MAIL_SERVER.EXE with more priileges than VMS normally does, ID assume with no reason nowadays (V7.3-1 Alpha).  Or is my kit old and out-of-date?  H ------------------------------------------------------------------------  4    Steven M. Schweda               (+1) 651-699-98183    382 South Warwick Street        sms@antinode.org     Saint Paul  MN  55105-2547    ------------------------------  # Date: Mon, 13 Oct 2003 22:58:07 GMT 6 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER) Subject: Re: MD5 source code ?1 Message-ID: <36Gib.5884$Lo.106401@news.chello.at>   j In article <drk3ov814jqfbrs9qtp7b2oqg7l4cvfq0k@4ax.com>, Milton <mbhewitt@optonline.SPAMBLOCK.net> writes:Z >On Mon, 06 Oct 2003 17:13:35 GMT, peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER) wrote:L >>Does anyone have a source code ready which does a MD5 checksum of an input3 >>file and puts the hash/checksum in a DCL symbol ?  >>O >>I know I could do it myself but I'm lazy^Wshort of time and ask here first...  > H >The undocumented DCL command CHECKSUM is the usual means,and provides aI >rather simple-minded checksum suitable to detect basic file corruptions.  > 2 >CHECKSUM filename $ SHOW SYMBOL CHECKSUM$CHECKSUM  : And exactly this functionality I like to replace with MD5.: Checksum unfortunately doesn't fulfill the requirements...  G >For information about an OpenVMS version of the MD5checksum tool, see: ? >http://www.support.compaq.com/svctools/md5-instructions.html     7 Not really. It works with files and not with symbols...   " Thanks anyway. Seems I've to bite.   --   Peter "EPLAN" LANGSTOEGER % Network and OpenVMS system specialist  E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------  # Date: Mon, 13 Oct 2003 23:22:17 GMT 6 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER) Subject: Re: MD5 source code ?1 Message-ID: <JsGib.6231$Lo.111176@news.chello.at>   y In article <ae0ff0f7430ba61d419caf5d28645e01@news.teranews.com>, "Craig A. Berry" <craigberry@mac.com.spamfooler> writes: m >In article <3phgb.81032$qU6.1291982@news.chello.at>, peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER) wrote: M >> Does anyone have a source code ready which does a MD5 checksum of an input 4 >> file and puts the hash/checksum in a DCL symbol ? > H >It's pretty simple in Perl using extensions that are included with the  >core package: >  >$ type get_md5.pl >use strict; >use VMS::DCLsym;  >use Digest::MD5;  > : >open F, $ARGV[0] or die "Cannot open file $ARGV[0] : $!";7 >my $digest = Digest::MD5->new->addfile(*F)->hexdigest; M >VMS::DCLsym->new->setsym('MD5$MD5', $digest) or die "Cannot set symbol: $!";  >exit; >$& >$ perl get_md5.pl sys$login:login.com >$ show symbol md5$md5/ >  MD5$MD5 = "db6aa5d44c8172b38193d8c3d1dc9aa0"  >$   Nice. H But then I've to install PERL instead of copying a single .EXE and I betD this eats CPU (and IO) if called umpteen thousand times in a loop...   Nevertheless, 1st try:  % $ perl get_md5.pl sys$login:login.com O Can't locate Digest/MD5.pm in @INC (@INC contains: /perl_root/lib/VMS_AXP/5_6_1 P perl_root:[lib] perl_root:[lib.site_perl.VMS_AXP] perl_root:[lib.site_perl] /per- l_root/lib/site_perl .) at get_md5.pl line 3. 7 BEGIN failed--compilation aborted at get_md5.pl line 3. + %RMS-F-SYN, file specification syntax error   / So, not out of the box. I hunt it down later...    --   Peter "EPLAN" LANGSTOEGER % Network and OpenVMS system specialist  E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------  # Date: Tue, 14 Oct 2003 01:47:19 GMT 6 From: "Craig A. Berry" <craigberry@mac.com.spamfooler> Subject: Re: MD5 source code ?@ Message-ID: <8ea7eacfaf6b8c7b4471c20148312e71@news.teranews.com>  1 In article <JsGib.6231$Lo.111176@news.chello.at>, 8  peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER) wrote:  M > In article <ae0ff0f7430ba61d419caf5d28645e01@news.teranews.com>, "Craig A.  0 > Berry" <craigberry@mac.com.spamfooler> writes:M > >In article <3phgb.81032$qU6.1291982@news.chello.at>, peter@langstoeger.at  % > >(Peter 'EPLAN' LANGSTOEGER) wrote: O > >> Does anyone have a source code ready which does a MD5 checksum of an input 6 > >> file and puts the hash/checksum in a DCL symbol ? > > J > >It's pretty simple in Perl using extensions that are included with the  > >core package:  ' > $ perl get_md5.pl sys$login:login.com 5 > Can't locate Digest/MD5.pm in @INC (@INC contains:    F Oops.  I guess Digest::MD5 was an add-on until Perl 5.8.0 and later.  @ In any case you can find it via <http://search.cpan.org>.  Your G performance speculation depends on whether the major hit is in program  = loading, file reading, or algorithm time; if the latter, the  D calculation is done in C via a Perl extension, so there wouldn't be ? much difference.  There are certainly advantages to one of the  F standalone C programs others have mentioned, but the Perl version has H its place, especially if you decided to move the entire script from DCL  to Perl.   ------------------------------    Date: 13 Oct 2003 14:47:22 -0700& From: trevor_obba@yahoo.co.uk (trevor) Subject: nagios plugin for vms= Message-ID: <59615909.0310131347.41b1af50@posting.google.com>   D We've been using Nagios(Netsaint) for a few weeks to monitor a whole bunch ofA hosts around our work place, but now the management have asked me B if I can also arrange to monitor the two VMS systems we still have? around. I have search the internet for nagios plugin that I can B install on a our nagios server to mornitor and do the usual checks- such as disk space, load average, availabity.    can you help? please   ------------------------------  # Date: Tue, 14 Oct 2003 01:54:53 GMT 6 From: "Craig A. Berry" <craigberry@mac.com.spamfooler> Subject: Re: ODBTP on VMS ? @ Message-ID: <2f61118cbf6b3703f73598bf9d8ae48c@news.teranews.com>  3 In article <AB4CE668651116503818F36547E7493E@nntp>, >  "Ruslan R. Laishev" <Laishev{at}DeltaTelelecom{dot}RU> wrote:   > www.freetds.org ?   C That will only help him if the target database is MS SQL Server or  * Sybase, which I don't see him mentioning.    > Dieter Ro?bach wrote:  > ( > > I have two questions about unixODBC: > > L > > 1. is there a "official" port for OpenVMS, or do I have to do it myself?  < Neither.  VMS build procedures are included in the standard A distribution.  A bit of tweaking may be necessary if something's  H changed since I last looked at it, but there's no reason to do the port  yourself as it's already done.  G > > 2. has anybody tried it together with the ODBC support of CSWS_PHP? ( > >    That would be a need combination!  ' Yes it would.  No, I have not tried it.    ------------------------------    Date: 13 Oct 2003 12:43:41 -0700* From: denny.rich@swagelok.com (Denny Rich)( Subject: Re: PMGC-B card on DEC3000/M600< Message-ID: <d28306e.0310131143.4aa395db@posting.google.com>   Bart,   7 Thank you for the reply.  I'll give this a try tonight.    Regards, denny    lederman@star.enet.dec.DISABLE-JUNK-EMAIL.com (Bart Z. Lederman) wrote in message news:<2Bxib.6896$p_.6105@news.cpqcorp.net>... k > In article <d28306e.0310121621.3226d511@posting.google.com>, denny.rich@swagelok.com (Denny Rich) writes:  > D > >I have a Sandpiper (DEC3000/M600) with a PMAGC-B Turbochannel I/OH > >card, and a VRT19-HA monitor.  The card is running firmware V1.2, and% > >the Sandpiper is running VMS7.3-1.  > > A > >When I boot VMS, VMs complains about DECW$DEVICE-I-NODEVICE No  > >graphics device found.e > >OE > >VMS on the Sandpiper reports a GVA0: device, but it is offline.  InF > >edited a number of DECW$*.COM files to add a device "GV", but to no	 > >avail.n > B > The document I have available on graphics devices indicates thatG > you have to install the Open3D kit to get the driver for this device.nB > There is a pointer to the kit in the "Ask The Wizard" section ofC > the OpenVMS web page.  A search on "open3d" will get you pointerst > to several articles. >  >  > -- .* >  B. Z. Lederman   Personal Opinions Only > : >  Posting to a News group does NOT give anyone permission: >  to send me advertising by E-mail or put me on a mailing >  list of any kind. > 7 >  Please remove the "DISABLE-JUNK-EMAIL" if you have aB7 >  legitimate reason to E-mail a response to this post.    ------------------------------    Date: 13 Oct 2003 16:10:43 -0700* From: denny.rich@swagelok.com (Denny Rich)( Subject: Re: PMGC-B card on DEC3000/M600< Message-ID: <d28306e.0310131510.220a4da6@posting.google.com>   Bart,iE Thank you. The OPEN3D kit did the trick. One reboot, and I was on thei air with DECWindows.  
 Thanks again.c   dennye       lederman@star.enet.dec.DISABLE-JUNK-EMAIL.com (Bart Z. Lederman) wrote in message news:<2Bxib.6896$p_.6105@news.cpqcorp.net>...lk > In article <d28306e.0310121621.3226d511@posting.google.com>, denny.rich@swagelok.com (Denny Rich) writes:p > D > >I have a Sandpiper (DEC3000/M600) with a PMAGC-B Turbochannel I/OH > >card, and a VRT19-HA monitor.  The card is running firmware V1.2, and% > >the Sandpiper is running VMS7.3-1.i > >nA > >When I boot VMS, VMs complains about DECW$DEVICE-I-NODEVICE Noo > >graphics device found.0 > > E > >VMS on the Sandpiper reports a GVA0: device, but it is offline.  ICF > >edited a number of DECW$*.COM files to add a device "GV", but to no	 > >avail.e > B > The document I have available on graphics devices indicates thatG > you have to install the Open3D kit to get the driver for this device.pB > There is a pointer to the kit in the "Ask The Wizard" section ofC > the OpenVMS web page.  A search on "open3d" will get you pointers< > to several articles. >  >  > -- D* >  B. Z. Lederman   Personal Opinions Only > : >  Posting to a News group does NOT give anyone permission: >  to send me advertising by E-mail or put me on a mailing >  list of any kind. > 7 >  Please remove the "DISABLE-JUNK-EMAIL" if you have a 7 >  legitimate reason to E-mail a response to this post.    ------------------------------  # Date: Tue, 14 Oct 2003 00:58:45 GMT 5 From: rdeininger@mindspringdot.com (Robert Deininger)n( Subject: Re: PMGC-B card on DEC3000/M600L Message-ID: <rdeininger-1310032108260001@user-uinj0g2.dialup.mindspring.com>  < In article <d28306e.0310121621.3226d511@posting.google.com>,+ denny.rich@swagelok.com (Denny Rich) wrote:w   >Hello,sB >I have a Sandpiper (DEC3000/M600) with a PMAGC-B Turbochannel I/OF >card, and a VRT19-HA monitor.  The card is running firmware V1.2, and# >the Sandpiper is running VMS7.3-1.e  3 That is the latest version of FW for the card, BTW.f  ? As Bart pointed out, the Open3D kit contains the device driver.g  F On my V7.3 system, I also have a version of SYS$GVADRIVER.EXE that wasD clearly (from the date and the image ident) built and/or kitted withI OpenVMS V7.3.  I can't tell at the moment whether the Open3D installationeG procedure linked the driver, or it's lurking somewhere in the V7.3 kit.e   ------------------------------  % Date: Mon, 13 Oct 2003 23:15:21 -0400:* From: "Bill Todd" <billtodd@metrocast.net>! Subject: Re: Sickening, isn't it?,2 Message-ID: <TYecnTVrzMfb9xaiU-KYjQ@metrocast.net>  A "Tim Llewellyn" <tim.llewellyn@blueyonder.co.uk> wrote in message * news:3F8AC0B7.7EF6C21E@blueyonder.co.uk... >e >t > Howard Shubs wrote:    ...-  H > > You are what you eat, therefore, I'm a vegetable!  Cows and chickens > > and Pop Tarts are too. >O; > And I thought I was the only veggie comp.os.vms reader...-  I Well, you might be one degree of separation closer to being a veggie thanp> Howard - if his point is that the relationship is recursive...   - bill   ------------------------------  # Date: Mon, 13 Oct 2003 22:11:31 GMTa1 From: Bob Blunt <robert.blunt@hp.donotspamme.com>p/ Subject: Re: Slow Shadow Copy with 36 GB drivesb2 Message-ID: <nqFib.6954$HH1.3317@news.cpqcorp.net>  
 Jim wrote:L > I have HP support stumped on this one so I thought someone here could help > me.h > M > We recently upgraded a pair of HSJ40 controllers to firmware version V37J-1mN > so that we could replace our aging 2GB and 4GB drives with new 36 GB drives.H > We are running VMS 6.2 and applied the latest shadowing patch (ALPSHAD	 > 14_62.)  > M > Note:  We can't upgrade to a new version of VMS without paying our softwaren > vendor huge $$$. > H > Everything works fine except that shadow copies take about 24 hours toN > complete.  Other drives, such as 9 GB drives take about 2 hours to complete. > L > Is this an inherent problem with VMS 6.2 and large drives or is there some! > tweak that we missed somewhere?. > L > Help would be appreciated since we need to keep this ancient monster alive > for another year :  )r >  > Sincerely, >  > Jim GouldI >  >   C Check both new drives to make sure that they haven't ended up with  G writeback cache turned OFF.  The worst I've seen is when one IS cached oH and the other isn't.  This has to be enabled when initalizing the drive I for use in the HSJ and in my experience the default is writeback caching l	 disabled.a   bobo   ------------------------------  % Date: Mon, 13 Oct 2003 23:00:20 +0100-$ From: "Martin" <w_orbit@hotmail.com>0 Subject: submitting a VMS batch job from Windows; Message-ID: <3f8b2057$0$65594$65c69314@mercury.nildram.net>l  J Hi.  We've begun implementation of Windows based client applications but aL lot of our batch processes remain on VMS.  I need a way to submit batch jobsI on VMS from the new clients.  My initial thought was to create a VMS .comuJ file on the client containing the submit details, ftp that to a secure VMSJ user account whose login.com implememted a wait for X seconds to allow ftpJ to complete then used the generated .com file to submit the batch job with8 the specified parameters passed from the Windows client.  $ Is there a better method that this ?   Tiaw Martin   ------------------------------  % Date: Mon, 13 Oct 2003 15:40:11 -0700-# From: "Tom Linden" <tom@kednos.com>2J Subject: RE: TCPIP anti-spam mechanisms (was: Latest VMS Critical Upgrade)9 Message-ID: <CIEJLCMNHNNDLLOOGNJIKENPIDAA.tom@kednos.com>o  J The problem with that rule, at least for me, is that I get legitimate mail4 in html format (including from HP pertaining to VMS)   >-----Original Message-----e0 >From: Wayne Sewell [mailto:wayne@tachysoft.com]' >Sent: Monday, October 13, 2003 8:08 AMt >To: Info-VAX@Mvb.Saic.ComB >Subject: Re: TCPIP anti-spam mechanisms (was: Latest VMS Critical	 >Upgrade)d >  >i >>> B >>> With both levels of interception in operation hardly anything  >breaks through toB >>> appear in vms mail any more.  Scanning for "text/html" in the  >*body* of the" >>> message stops nearly all spam. >>3 >>Wow !  How does that string get into the _body_ ?f >t >pC >It's been my observation that it appears *mostly* in the body.  I -
 >have a check1? >for it in the header, but it really hasn't had that many hits.p >e >m >Rule ID: 1146$ >    Header: Content-Type: text/htmlD >    Added: 13-MAR-2003 17:57:54.12, Ref count: 262, Last ref date:  >11-OCT-2003 >01:40:24.22 >--- >. >Rule ID: 1196% >    Header: Content-Type: text/html*lD >    Added: 29-MAR-2003 19:07:32.15, Ref count: 162, Last ref date:  >12-OCT-2003 >00:57:51.61 >--- >t >eA >Hmm, appears I have redundant rules.  I'll remove the first one.h >e >o> >In any case, these counts are small compared to the messages  >intercepted by thef >check for html in the body. >lJ >What I usually see is "text/alternative" or some shit in the header, thenA >"text/plain" and "text/html" in the body.  I think you only see   >"text/html" inh? >the header if the message is entirely html with no plain text.d >y >WayneD >===================================================================
 >============p< >Wayne Sewell, Tachyon Software Consulting  (281)812-0738    >wayne@tachysoft.com< >http://www.tachysoft.com/www/tachyon.html and wayne.html   D >===================================================================
 >============pI >Randolph Duke (in Trading Places): "Mother always said you were greedy."a2 >   Mortimer Duke: "She meant it as a compliment!" >  >---' >Incoming mail is certified Virus Free.D; >Checked by AVG anti-virus system (http://www.grisoft.com).iA >Version: 6.0.518 / Virus Database: 316 - Release Date: 9/11/2003  >> ---t& Outgoing mail is certified Virus Free.: Checked by AVG anti-virus system (http://www.grisoft.com).@ Version: 6.0.518 / Virus Database: 316 - Release Date: 9/11/2003   ------------------------------  % Date: Mon, 13 Oct 2003 19:00:12 -0500t( From: Wayne Sewell <wayne@tachysoft.com>N Subject: Re: RE: TCPIP anti-spam mechanisms (was: Latest VMS Critical Upgrade)/ Message-ID: <00A27544.B179CDC8.1@tachysoft.com>m  $ >From: "Tom Linden" <tom@kednos.com> >X-Newsgroups: comp.os.vmsK >Subject: RE: TCPIP anti-spam mechanisms (was: Latest VMS Critical Upgrade)t: >Message-ID: <CIEJLCMNHNNDLLOOGNJIKENPIDAA.tom@kednos.com>& >Date: Mon, 13 Oct 2003 15:40:11 -0700. >Organization: Info-VAX<==>comp.os.vms Gateway$ >X-Gateway-Source-Info: Mailing List
 >Lines: 74  >Content-Transfer-Encoding: 7bit/ >Content-Type: text/plain; charset="iso-8859-1"r >MIME-Version: 1.0( >Reply-To: "Tom Linden" <tom@kednos.com> >X-Gateway-From: mvb.saic.com  >To: Info-VAX@Mvb.Saic.Com >eK >The problem with that rule, at least for me, is that I get legitimate maile5 >in html format (including from HP pertaining to VMS)r >c    I Not a problem.  I can still get mail from hp even with the rule in place.    ---'
 Rule ID: 1707      Sender: *@HP.COM.     Accept messages with these characteristicsL     Added:  4-SEP-2003 22:04:06.65, Ref count: 8, Last ref date: 23-SEP-2003 13:58:48.911 ---    The command to do this is:   add rej/accept=as_is *@hp.comi      N In MX, all address-based rules override all header-based rules, because if theM address is rejected (or accepted in this case), the header is not seen by the) server at all.    I I have very few legitmate correspondents with text/html in the header (asaI opposed to the body).  It's trivial to make an accept rule for each.  ThesF unwashed of the internet, i.e. the spammers, continue to be blocked ifF text/html appears in the headers, while valid users cruise on through.       >> >>Rule ID: 1146.% >>    Header: Content-Type: text/htmllE >>    Added: 13-MAR-2003 17:57:54.12, Ref count: 262, Last ref date: m
 >>11-OCT-2003 
 >>01:40:24.22g >>---h >> >>Rule ID: 1196e& >>    Header: Content-Type: text/html*E >>    Added: 29-MAR-2003 19:07:32.15, Ref count: 162, Last ref date: a
 >>12-OCT-2003 
 >>00:57:51.61e >>---o >>O =============================================================================== N Wayne Sewell, Tachyon Software Consulting  (281)812-0738   wayne@tachysoft.com; http://www.tachysoft.com/www/tachyon.html and wayne.html   hO ===============================================================================MH Randolph Duke (in Trading Places): "Mother always said you were greedy."1    Mortimer Duke: "She meant it as a compliment!"    ------------------------------  % Date: Mon, 13 Oct 2003 17:06:53 -0700c# From: "Tom Linden" <tom@kednos.com>tN Subject: RE: RE: TCPIP anti-spam mechanisms (was: Latest VMS Critical Upgrade)9 Message-ID: <CIEJLCMNHNNDLLOOGNJIOEOEIDAA.tom@kednos.com>t  = Thanks that seems easier than continually writing expressions > based on from: rules to only stay one step behind.  Of course,= then you would need to maintain a list of sites from whom youc will accept html       >-----Original Message----- 0 >From: Wayne Sewell [mailto:wayne@tachysoft.com]' >Sent: Monday, October 13, 2003 5:00 PMn >To: Info-VAX@Mvb.Saic.ComF >Subject: Re: RE: TCPIP anti-spam mechanisms (was: Latest VMS Critical	 >Upgrade)  >h >P% >>From: "Tom Linden" <tom@kednos.com>m >>X-Newsgroups: comp.os.vmsyL >>Subject: RE: TCPIP anti-spam mechanisms (was: Latest VMS Critical Upgrade); >>Message-ID: <CIEJLCMNHNNDLLOOGNJIKENPIDAA.tom@kednos.com>i' >>Date: Mon, 13 Oct 2003 15:40:11 -0700o/ >>Organization: Info-VAX<==>comp.os.vms Gatewayh% >>X-Gateway-Source-Info: Mailing List  >>Lines: 74t! >>Content-Transfer-Encoding: 7bite0 >>Content-Type: text/plain; charset="iso-8859-1" >>MIME-Version: 1.0X) >>Reply-To: "Tom Linden" <tom@kednos.com>u >>X-Gateway-From: mvb.saic.com >>To: Info-VAX@Mvb.Saic.Comp >>L >>The problem with that rule, at least for me, is that I get legitimate mail6 >>in html format (including from HP pertaining to VMS) >> >h > J >Not a problem.  I can still get mail from hp even with the rule in place. >  >--- >Rule ID: 1707 >    Sender: *@HP.COMy/ >    Accept messages with these characteristicsaA >    Added:  4-SEP-2003 22:04:06.65, Ref count: 8, Last ref date:a >23-SEP-2003 >13:58:48.91 >--- >n >The command to do this is:e >e >add rej/accept=as_is *@hp.com >u >  > @ >In MX, all address-based rules override all header-based rules, >because if theaB >address is rejected (or accepted in this case), the header is not >seen by the >server at all.  >e >SJ >I have very few legitmate correspondents with text/html in the header (asJ >opposed to the body).  It's trivial to make an accept rule for each.  TheG >unwashed of the internet, i.e. the spammers, continue to be blocked iftG >text/html appears in the headers, while valid users cruise on through.a >a >r >n >>>  >>>Rule ID: 1146& >>>    Header: Content-Type: text/htmlE >>>    Added: 13-MAR-2003 17:57:54.12, Ref count: 262, Last ref date:d >>>11-OCT-2003 >>>01:40:24.22 >>>--- >>>w >>>Rule ID: 1196' >>>    Header: Content-Type: text/html* E >>>    Added: 29-MAR-2003 19:07:32.15, Ref count: 162, Last ref date:w >>>12-OCT-2003 >>>00:57:51.61 >>>--- >>>wD >===================================================================
 >============n9 >Wayne Sewell, Tachyon Software Consulting  (281)812-0738  >wayne@tachysoft.com9 >http://www.tachysoft.com/www/tachyon.html and wayne.htmliD >===================================================================
 >============ I >Randolph Duke (in Trading Places): "Mother always said you were greedy." 2 >   Mortimer Duke: "She meant it as a compliment!" >k >---' >Incoming mail is certified Virus Free.h; >Checked by AVG anti-virus system (http://www.grisoft.com).HA >Version: 6.0.518 / Virus Database: 316 - Release Date: 9/11/2003- >- ---a& Outgoing mail is certified Virus Free.: Checked by AVG anti-virus system (http://www.grisoft.com).@ Version: 6.0.518 / Virus Database: 316 - Release Date: 9/11/2003   ------------------------------  + Date: Mon, 13 Oct 2003 23:01:16 +0000 (UTC)lP From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)# Subject: TCPIP versions and patches $ Message-ID: <bmfars$ncv$4@online.de>  H This weekend, I plan to upgrade both VAX (I have one at 7.3 already but H one still at 7.2) and ALPHA (from 7.2-1) to 7.3 (VAX) and 7.3-1 (ALPHA).- After that, I'll apply the necessary patches.a  H I have TCPIP 5.1 on the VAX 7.3 CD I plan to use for the upgrade.  I seeD that there are patches both for 5.1 and for 5.3.  Is the 5.3 patch aF "full kit", i.e. could I install the patch and thereby upgrade to 5.3,D or do I have to properly install 5.3 first (which, presumably, would$ mean borrowing a newer VAX 7.3 CD).   D Presumably, VMS 7.2-1 --> 7.3-1 and TCPIP 5.0A --> 5.3 on ALPHA are  valid upgrade paths.    D When a new OS CD appears with the consolidated distribution, if the E version of the OS is the same, are all the binaries the same, or are S@ some patches included?  If so, is it possible to see which ones?   ------------------------------  # Date: Tue, 14 Oct 2003 00:00:57 GMTi/ From: sol gongola <solomon.gongola@verizon.net>l' Subject: Re: TCPIP versions and patchesl+ Message-ID: <3F8B3D09.DB721C38@verizon.net>C  / Phillip Helbig---remove CLOTHES to reply wrote:f > I > This weekend, I plan to upgrade both VAX (I have one at 7.3 already but J > one still at 7.2) and ALPHA (from 7.2-1) to 7.3 (VAX) and 7.3-1 (ALPHA)./ > After that, I'll apply the necessary patches.a > J > I have TCPIP 5.1 on the VAX 7.3 CD I plan to use for the upgrade.  I seeF > that there are patches both for 5.1 and for 5.3.  Is the 5.3 patch aH > "full kit", i.e. could I install the patch and thereby upgrade to 5.3,F > or do I have to properly install 5.3 first (which, presumably, would% > mean borrowing a newer VAX 7.3 CD).o > E > Presumably, VMS 7.2-1 --> 7.3-1 and TCPIP 5.0A --> 5.3 on ALPHA are, > valid upgrade paths. > E > When a new OS CD appears with the consolidated distribution, if the F > version of the OS is the same, are all the binaries the same, or areB > some patches included?  If so, is it possible to see which ones?  E The distribution kits contain a master index, listing the contents of  the B distribution and each items version number, Product identifier, CD number,aC Location (directory) on the CD, and status (NEW, Updated), and alsof8 a list of items that were removed from the distribution.   sol gongolar adl data systems inc.Y dobbs ferry, nyi   ------------------------------  % Date: Mon, 13 Oct 2003 22:09:58 -0500a5 From: "Martin P.J. Zinser" <zinser@zinser.no-ip.info> ' Subject: Re: TCPIP versions and patchesf9 Message-ID: <bmfpe7$lmm9c$1@ID-209632.news.uni-berlin.de>a  / Phillip Helbig---remove CLOTHES to reply wrote:-J > This weekend, I plan to upgrade both VAX (I have one at 7.3 already but J > one still at 7.2) and ALPHA (from 7.2-1) to 7.3 (VAX) and 7.3-1 (ALPHA)./ > After that, I'll apply the necessary patches.M > J > I have TCPIP 5.1 on the VAX 7.3 CD I plan to use for the upgrade.  I seeF > that there are patches both for 5.1 and for 5.3.  Is the 5.3 patch aH > "full kit", i.e. could I install the patch and thereby upgrade to 5.3,F > or do I have to properly install 5.3 first (which, presumably, would& > mean borrowing a newer VAX 7.3 CD).  > G No, you need the 5.3 product installation first and put the ECO on top. G The ECOs itself are cumulative (i.e. install ECO 2 immediatly, no need X to put ECO 1 in first.   Greetings, Martinf   ------------------------------  % Date: Mon, 13 Oct 2003 11:42:39 -0700E( From: Alan Frisbie <Abuse@NelsonUSA.com>2 Subject: The Uptimes Project -- VMS does very well, Message-ID: <3F8AF21F.8010104@NelsonUSA.com>  ; If you have not checked out The Uptimes Project lately, youV might like to:  1      http://uptimes.wonko.com/stats.php?op=activet  8 VMS currently holds three of the top five positions, and9 five of the top 20.   (OK, I'm simply proud of being ablee to keep it up 672 days.   :-)   8 If anyone knows the project manager or engineers for the8 AlphaServer 1000A, please tell them that all five of the. top VMS systems are AlphaServer 1000A systems.  6 It is also amusing to note that the average uptime for0 Windows systems is just slightly over four days.  9 If you are proud of your system's uptime, please considere9 adding it to the group.   You can send packets either vian6 HTTP (port 80), or via UDP to port 49153.   The client7 software (written in C) is available on their web site.u   Alan   ------------------------------  # Date: Mon, 13 Oct 2003 22:03:23 GMTo< From: "John E. Malmberg" <Malmberg@dskwld.zko.dec.compaq.hp>6 Subject: Re: The Uptimes Project -- VMS does very well2 Message-ID: <LiFib.6952$7S1.5512@news.cpqcorp.net>   Alan Frisbie wrote:i= > If you have not checked out The Uptimes Project lately, youh > might like to: > 2 >     http://uptimes.wonko.com/stats.php?op=active > : > VMS currently holds three of the top five positions, and; > five of the top 20.   (OK, I'm simply proud of being ablee > to keep it up 672 days.   :-)t  ) http://uptimes.wonko.com/stats.php?op=allc  H Apparently the uptime statistics for the top listing was collected by a @ LINUX system that retrieved them through an interactive session.  ' Yes there really is a VMS 4.5A release.o  8 > It is also amusing to note that the average uptime for2 > Windows systems is just slightly over four days.  I Can you get them to merge the VMS uptime with the OpenVMS uptime for the -
 averages? :-)-   -John ! malmberg@dskwld.zko.dec.compaq.hpe Personal Opinion Onlyg   ------------------------------  % Date: Mon, 13 Oct 2003 20:40:42 -0400-% From: "John Vottero" <John@mvpsi.com>e6 Subject: Re: The Uptimes Project -- VMS does very well/ Message-ID: <vomhgbq2t8hrc1@news.supernews.com>   5 "Alan Frisbie" <Abuse@NelsonUSA.com> wrote in messageh& news:3F8AF21F.8010104@NelsonUSA.com...= > If you have not checked out The Uptimes Project lately, youp > might like to: >c3 >      http://uptimes.wonko.com/stats.php?op=activeh > : > VMS currently holds three of the top five positions, and; > five of the top 20.   (OK, I'm simply proud of being able- > to keep it up 672 days.   :-)- >-: > If anyone knows the project manager or engineers for the: > AlphaServer 1000A, please tell them that all five of the0 > top VMS systems are AlphaServer 1000A systems. > 8 > It is also amusing to note that the average uptime for2 > Windows systems is just slightly over four days.  F And that includes the obvious hacks.  There's a Windows XP system thatL claims it's been up for over 11,000 days.  I wonder which is harder, keeping7 Windows up for that long or getting it to boot in 1972!.   ------------------------------  % Date: Mon, 13 Oct 2003 23:07:52 -0500 ( From: Wayne Sewell <wayne@tachysoft.com>6 Subject: Re: The Uptimes Project -- VMS does very well/ Message-ID: <00A27567.4A9C328A.8@tachysoft.com>v  & >From: "John Vottero" <John@mvpsi.com> >X-Newsgroups: comp.os.vms7 >Subject: Re: The Uptimes Project -- VMS does very well & >Date: Mon, 13 Oct 2003 20:40:42 -0400= >Organization: Posted via Supernews, http://www.supernews.com 0 >Message-ID: <vomhgbq2t8hrc1@news.supernews.com> >X-Priority: 3 >X-MSMail-Priority: Normal7 >X-Newsreader: Microsoft Outlook Express 6.00.2800.1158t9 >X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 % >X-Complaints-To: abuse@supernews.com 
 >Lines: 24* >Reply-To: "John Vottero" <John@mvpsi.com> >X-Gateway-From: mvb.saic.com. >To: Info-VAX@Mvb.Saic.Com >X-Gateway-Source-Info: USENET >o6 >"Alan Frisbie" <Abuse@NelsonUSA.com> wrote in message' >news:3F8AF21F.8010104@NelsonUSA.com...-> >> If you have not checked out The Uptimes Project lately, you >> might like to:- >>4 >>      http://uptimes.wonko.com/stats.php?op=active >>; >> VMS currently holds three of the top five positions, ando< >> five of the top 20.   (OK, I'm simply proud of being able  >> to keep it up 672 days.   :-) >>; >> If anyone knows the project manager or engineers for thea; >> AlphaServer 1000A, please tell them that all five of theR1 >> top VMS systems are AlphaServer 1000A systems.c >>9 >> It is also amusing to note that the average uptime forl3 >> Windows systems is just slightly over four days.  >eG >And that includes the obvious hacks.  There's a Windows XP system thataM >claims it's been up for over 11,000 days.  I wonder which is harder, keepingl8 >Windows up for that long or getting it to boot in 1972! >(    M An even more ludicrous bogus entry is that which claims an uptime of 16 years.H running VMS 4.5A.   That in itself might be possible (don't remember the. release date of 4.5), but on an i686 cpu?  :-)O ===============================================================================0N Wayne Sewell, Tachyon Software Consulting  (281)812-0738   wayne@tachysoft.com; http://www.tachysoft.com/www/tachyon.html and wayne.html   yO ===============================================================================aH Randolph Duke (in Trading Places): "Mother always said you were greedy."1    Mortimer Duke: "She meant it as a compliment!"t   ------------------------------  # Date: Tue, 14 Oct 2003 02:08:01 GMT # From: "John Smith" <a@nonymous.com>mF Subject: Re: The VAX/VMS to Itanium Migration Letter, Vol. 1 Number 1.K Message-ID: <5UIib.326724$Lnr1.315356@news01.bloor.is.net.cable.rogers.com>d   Hoff Hoffman wrote:e >-H >   PL/1 is a Kednos product, and questions on PL/I status and plans and% >   support should be directed there.t >o  K My understanding of the status of the PL/1 compiler is that HP would preferbL to see customers translate their PL/1 code to C or C++, and that HP plans toJ offer zero porting assistance to Kednos with any issues related to the GEM	 compiler.P  I We know that those organizations that use PL/1 tend to be large corporate J customers (Ford, National Semi) and other small organizations like the NSAK and defense agencies in other nations, as well as telecom and other serious,B organizations (Allstate, State Farm, Zurich, Northwestern Mutual).  I Some VMS - PL/1 users have made their feelings known on the matter as theeD following makes clear (attribution removed to protect the innocent):  F " I got a call from Sun a couple of weeks ago concerning HP's mythicalJ announcement that OpenVMS had been EOL'd. By now, I suspect most remaining8 OpenVMS customers are on to this re-occurring deception.L Unfortunately, it will be Digital/Compaq/HP's pathetic treatment of the PL/1L compiler that will eventually drive our company to another vendor. (No,we'reE not converting it to C++ so we can run on IPF. If we have to performatJ large-scale conversion, it'll be away from the company that forced us intoI the conversion). Based on what other divisions are doing in this company,t/ there's a good chance that vendor will be Sun."t      K Now HP may think that pissing off several hundred large corporate customers>I that use PL/1 is a good idea, but for most if not all of these customers, J translating robust PL/1 code that is most likely the core processing logicC of their businesses into buffer overrun prone C and C++ simply is ae non-starter.  E These same customer collectively run what probably amounts to severaleI thousand Alpha/VMS systems. So not only does HP piss these customers off,kG but they also wind up with a proposition that there is no PL/1 compliereG available for any proposed IA64 system from HP. Presto chango - bye byetK sales revenue for several thousand replacement systems; bye bye service and 1 maintenance revenue for several thousand systems.o  @ Can HP really afford to piss away this much revenue? I guess so.      K According to Kednos, what HP needs to do is to provide access to the latest H GEM, allocate some resources to maybe do a few things to ensure that theH debugger, for example, will continue to work with PL/I.  This may not be8 entirely within HP's purview since it may involve Intel. So, to make it simpleeD Step 1.  Get access to the latest GEM (Base level 43 or thereabouts)E Step 2.  Integrate with PL/I front-end on Alpha, run regression testsc& step 3.  Update debugger, if required.) step 4.  Do same on Itanium (HW required)h  K What's all this going to cost HP? A few hundred thousand bucks? Less than aoK tank of gas for the HP corporate jet. Less than the cost of one 10cm x 10cmnL logo on the helmet of Juan Montoya for one Formula 1 race. Kednos will be inI for many times that for their efforts. As I understand it, Kednos is more_L than willing to port to IA64/VMS, but needs HP to do some lifting at its end so Kendos can do its part.  L As far as I know, requests from Kendos to HP have been brushed aside without much consideration.y   ------------------------------  % Date: Mon, 13 Oct 2003 20:00:39 -0700 # From: "Tom Linden" <tom@kednos.com>oF Subject: RE: The VAX/VMS to Itanium Migration Letter, Vol. 1 Number 1.9 Message-ID: <CIEJLCMNHNNDLLOOGNJIOEOJIDAA.tom@kednos.com>a  I Thank you for the supportive arguments.  Ironically it was licensing PL/IeI to Digital in 1978 that gave them a boost of legitimacy into the world ofiA corporate computing in the first place. In fact, I believe it wasoH Ford that was the catalyst IIRC.  We had helped Prime get major businessE there at the expense of Digital because there was no PL/I on the VAX.e  E After PL/I was ported to the VAX that situation changed to the benfitN of Digital.i  I We have had the discussion before in this group about moving PL/I code to-I C or C++ and I think the consensus is that this is unworkable and stupid.aK I have written the only PL/I to C translator that works and that was to usemJ a code generator based on a C abstract machine.  We know how to use it (OnK Tru64) but you would not want to use it as a tool for porting, nor would wejG even entertain that notion.  On Tru64 we had to write our own debugger.@  I We have a portable code generator that is probably as good as GEM, but ittI would take some effort to provide the hardware grammar and test, but most0G importantly, it would not be integrated into the VMS language tools setiF (I hope that is not an oxymoron)  and that is a pity.  Starlet and SDLA are really great concepts, but it appears that HP doesn't get it.T  B I have to confess that I was never a big fan of Alpha, nor am I ofD Itanium, I have seen too many flash in the pans in the last 40 yearsB and there is nothing extraordinary with either.  VAX OTOH was well	 designed.l  D Summa summarum,  without GEM we will not port PL/I to Itanium.  ThisD Itanium adventure could well put HP out of business if pursued alongF the present lines.  What is the imperative for a corporate customer to( buy it?  Retain Trust is just snake oil.   Tom>   >-----Original Message-----o) >From: John Smith [mailto:a@nonymous.com]o' >Sent: Monday, October 13, 2003 7:08 PMh >To: Info-VAX@Mvb.Saic.ComG >Subject: Re: The VAX/VMS to Itanium Migration Letter, Vol. 1 Number 1.u >d >e >Hoff Hoffman wrote: >>I >>   PL/1 is a Kednos product, and questions on PL/I status and plans andb& >>   support should be directed there. >> > L >My understanding of the status of the PL/1 compiler is that HP would preferA >to see customers translate their PL/1 code to C or C++, and thato >HP plans toK >offer zero porting assistance to Kednos with any issues related to the GEM4
 >compiler. >.J >We know that those organizations that use PL/1 tend to be large corporateK >customers (Ford, National Semi) and other small organizations like the NSAaL >and defense agencies in other nations, as well as telecom and other seriousC >organizations (Allstate, State Farm, Zurich, Northwestern Mutual).t > J >Some VMS - PL/1 users have made their feelings known on the matter as theE >following makes clear (attribution removed to protect the innocent):- >-G >" I got a call from Sun a couple of weeks ago concerning HP's mythicalrK >announcement that OpenVMS had been EOL'd. By now, I suspect most remaining 9 >OpenVMS customers are on to this re-occurring deception.aA >Unfortunately, it will be Digital/Compaq/HP's pathetic treatmente >of the PL/1C >compiler that will eventually drive our company to another vendor.n
 >(No,we'reF >not converting it to C++ so we can run on IPF. If we have to performaK >large-scale conversion, it'll be away from the company that forced us intooJ >the conversion). Based on what other divisions are doing in this company,0 >there's a good chance that vendor will be Sun." >s >e >cL >Now HP may think that pissing off several hundred large corporate customersJ >that use PL/1 is a good idea, but for most if not all of these customers,K >translating robust PL/1 code that is most likely the core processing logiceD >of their businesses into buffer overrun prone C and C++ simply is a
 >non-starter.  > F >These same customer collectively run what probably amounts to severalJ >thousand Alpha/VMS systems. So not only does HP piss these customers off,H >but they also wind up with a proposition that there is no PL/1 complierH >available for any proposed IA64 system from HP. Presto chango - bye byeL >sales revenue for several thousand replacement systems; bye bye service and2 >maintenance revenue for several thousand systems. > A >Can HP really afford to piss away this much revenue? I guess so.6 >3 >2 >1L >According to Kednos, what HP needs to do is to provide access to the latestI >GEM, allocate some resources to maybe do a few things to ensure that the I >debugger, for example, will continue to work with PL/I.  This may not bet9 >entirely within HP's purview since it may involve Intel.S >So, to make it simpleE >Step 1.  Get access to the latest GEM (Base level 43 or thereabouts)hF >Step 2.  Integrate with PL/I front-end on Alpha, run regression tests' >step 3.  Update debugger, if required.e* >step 4.  Do same on Itanium (HW required) >tL >What's all this going to cost HP? A few hundred thousand bucks? Less than aL >tank of gas for the HP corporate jet. Less than the cost of one 10cm x 10cmB >logo on the helmet of Juan Montoya for one Formula 1 race. Kednos >will be innJ >for many times that for their efforts. As I understand it, Kednos is moreB >than willing to port to IA64/VMS, but needs HP to do some lifting >at its enda >so Kendos can do its part.m >d? >As far as I know, requests from Kendos to HP have been brushed  >aside without >much consideration. >A >  >y >h >  >  >l >t >t >e >---' >Incoming mail is certified Virus Free.-; >Checked by AVG anti-virus system (http://www.grisoft.com).0A >Version: 6.0.518 / Virus Database: 316 - Release Date: 9/11/2003a >o ---3& Outgoing mail is certified Virus Free.: Checked by AVG anti-virus system (http://www.grisoft.com).@ Version: 6.0.518 / Virus Database: 316 - Release Date: 9/11/2003   ------------------------------  % Date: Mon, 13 Oct 2003 15:06:54 -0500J* From: Patrick Spinler <pspinler@yahoo.com>. Subject: VMS decc FreeTDS compilation question( Message-ID: <3F8B05DE.8050700@yahoo.com>  
 Hello all:  H I'm trying to compile a sybase client C program using Compaq C V6.4-005 ? on OpenVMS Alpha V7.3-1 against FreeTDS 0.61_2 downloaded from ,D <http://www.freetds.org>.  We're trying to use it to replace the no + longer valid sybase openclient for openvms.W  H When I compile a program, I'm getting errors like the following (please  forgive line wrapping):V   -------------------------  cc /decc tsslistener  -fU /STAND=VAXC/FLOAT=IEEE_FLOAT/WARNING=(DISABLE=(LONGEXTERN,MISSINGRETURN,PROTOSCOPE))-a\ /INCLUDE=(CTS_PROGRAMMER:[PSPINLER.SRC.FREETDS.FREETDS-0_61_2.INCLUDE],CTS:[SOURCE.INCLUDE])  e openClientStatus=ct_con_props(pConnection,CS_SET,CS_USERNAME,gpTSSListenerUsername,CS_NULLTERM,NULL);h6 .....................................................^I %CC-E-BADMCRORECURS, Recursive expansion of macro "CS_USERNAME" exceeded   1024 levels and was terminated.iG at line number 664 in file CTS:[SOURCE.CPP.TSS_LISTENER]TSSLISTENER.C;5  -------------------------y  G CS_USERNAME happens to be defined in freetds's include file CSPUBLIC.H t as the following:A   -------------------------m /* Properties */ enum { 	CS_USERNAME = 1, G /* These defines looks weird but programs can test support for defines, B     compiler can check enum and there are no define side effecs */ #define CS_USERNAME CS_USERNAMEe -------------------------3  A Can anyone suggest how I can work around this and other, similar .F compilation issues with the definitions CS_PASSWORD, CS_HOSTNAME, and 5 the apparently non-existing CS_SERVERNAME constants ?0   Thanks,  -- Pat   ------------------------------  # Date: Mon, 13 Oct 2003 22:06:55 GMTi< From: "John E. Malmberg" <Malmberg@dskwld.zko.dec.compaq.hp>2 Subject: Re: VMS decc FreeTDS compilation question2 Message-ID: <3mFib.6953$7S1.2384@news.cpqcorp.net>   Patrick Spinler wrote: >  > C > Can anyone suggest how I can work around this and other, similar hH > compilation issues with the definitions CS_PASSWORD, CS_HOSTNAME, and 7 > the apparently non-existing CS_SERVERNAME constants ?r  G Remove the #defines if there already is a token with that name, unless -3 something else is testing to see if a macro exists.3  H If you have to keep the #defines in, give the other tokens unique names.   -John ! malmberg@dskwld.zko.dec.compaq.hpf Personal Opinion Onlye   ------------------------------  # Date: Tue, 14 Oct 2003 01:35:17 GMT 5 From: rdeininger@mindspringdot.com (Robert Deininger)o1 Subject: Re: where to buy memory for DEC3000/M300eL Message-ID: <rdeininger-1310032144570001@user-uinj0g2.dialup.mindspring.com>  < In article <d28306e.0310121726.1f6bdd02@posting.google.com>,+ denny.rich@swagelok.com (Denny Rich) wrote:t  F >Like the original message but my system is: DEC 3000/M300. Looks likeE >72pin PC stuff. What specs? is it really 34 bit?  and I know if have . >to add it in pairs. But what sort of memory ? >n >thanks. >n >denny  * You have to add the memory SIMMs in pairs.  % There are two kinds of memory option:5  8 MB SIMMs (16 MB kit)e 32 MB SIMMs (64 MB kit)e  ! Maximum memory is 4 kits, 256 MB.t   Memory loading rules:   D 1. 32 MB kits must be installed before 8 MB kits.  (This lets the FW7 arrange the memory with no holes in the address space.)a   2. Do not skip any slots.n    M The memory specs I have (from the system programmer's manual) are as follows:A  G The 8 MB SIMM is 2Mx36 bits (32 data bits, 4 parity bits) using 1Mx4biti DRAM chips.o  H The 32 MB SIMM is 8Mx36 bits (32 data bits, 4 parity bits) using 4Mx4bit DRAM chips.a      F The memory configuration hardware in this system is extremely simple. J Each of the 4 memory banks has 1 bit, which tells the hardware whether theH bank contains a 8 MB or a 32 MB kit.  There's no specific representationD for an empty memory bank; the FW has to figure that out by trial and> error.  That is why the configuration rules are so inflexible.   ------------------------------  % Date: Mon, 13 Oct 2003 10:45:32 -0700i( From: Alan Frisbie <Abuse@NelsonUSA.com>A Subject: Re: White paper: CHARON-VAX cluster w/ shared SCSI diskss, Message-ID: <3F8AE4BC.4070103@NelsonUSA.com>   Wilm Boerhout wrote:  I > I welcome your questions, comments and suggestions on the white paper, -> > available from http://www.vxcompany.com/im , bottom of page. >   % Too bad the site requires javascript.j   Alan   ------------------------------  % Date: Mon, 13 Oct 2003 19:51:17 +020045 From: Wilm Boerhout <wboerhoutOLD@PAINTvxcompany.com>oA Subject: Re: White paper: CHARON-VAX cluster w/ shared SCSI diskse* Message-ID: <bmeoqn$rbp$1@reader10.wxs.nl>  I Sorry 'bout that - my employer holds a different opinion - see below for V the reverse.  + I put a copy on my private web location at t3 http://home.planet.nl/~boerh075/SCSI_VAXcluster.pdfi  G You can pick it up from there I guess - opinions on the contents still e
 welcome...   Alan Frisbie wrote:  > Wilm Boerhout wrote: > J >> I welcome your questions, comments and suggestions on the white paper, ? >> available from http://www.vxcompany.com/im , bottom of page., >> > ' > Too bad the site requires javascript.< >  > Alan >    -- c
 Wilm Boerhoutt VX Company, The Netherlandst   wboerhoutOLD@PAINTvxcompany.com '   (remove OLD PAINT from reply address)c  ' *** my opinions are strictly my own ***t   ------------------------------  % Date: Mon, 13 Oct 2003 21:43:42 -0400e( From: David Froble <davef@tsoft-inc.com>A Subject: Re: White paper: CHARON-VAX cluster w/ shared SCSI disksn, Message-ID: <3F8B54CE.7000003@tsoft-inc.com>   Michael Moroney wrote:  2 > "Rob Lyons" <rob.lyons@resilientsys.com> writes: >  > p >>Thanks for getting the word out to the rest of us who were not able to attend the Dutch Technical Update Days. >> >  >>I suggest the name for your configuration is LAVC with shared SCSI or a Mixed Interconnect Cluster since the interconnect that >>carries the cluster traffic names the cluster type, by convention.  The term "SCSI-cluster" incorrectly implies that the SCSI bus is >>carrying SCA cluster traffic.' >> > K > Well, no, to be picky the term LAVC was obsolete with VMS V5.  In the old D > days (VMS V4.x) 'big vax' clusters (CI) were different beasts fromF > microvax clusters (LAVC) running MicroVMS.  Nowadays 'a cluster is a > cluster is a cluster'.    Q Ok, being picky, I'll disagree.  A cluster has always been a cluster, regardless 5M of the interconnect used for moving data and for DLM traffic.  The only real tM difference that I'm aware of with the LAVC was the name.  Use of Ethernet to  P build a cluster was not limited to the MV systems.  It's a bit like looking for % a difference between VMS and OpenVMS.d  L What the CI did was allow direct access to storage by each system.  Systems Q without such an interconnect were forced to serve all disks from the system they y were/are connected.=    D > re base note: Since Charon-VAX emulates a VAX not Alpha and sharedD > SCSI was never on VAX, the VAX SCSI drivers may assume they're theE > only thing accessing the bus and there may some 'strangeness' seen.  > But interesting nonetheless. >   N I'm with you on wondering about 2 masters on the SCSI bus.  I don't know much P about differential SCSI, well, SCSI in general, and therefore don't know if the ( differential SCSI hardware handles such.  Q I haven't worked with any of the emulators yet.  With VMS systems sitting on the )Q shelf because this one person can barely justify running 3 VMS systems, the need uO for alternate hardware has not yet occured.  But, as new x86 based systems and wN capabilities become available, thoughts of using some of the new capabilities . with VAX emulators is as you say, interesting.   Dave   -- :4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com 170 Grimplin Roado Vanderbilt, PA  15486d   ------------------------------   End of INFO-VAX 2003.569 ************************