1 INFO-VAX	Wed, 31 May 2000	Volume 2000 : Issue 303       Contents:7 Re: "VMS on Wildfire" Slides from NELUG meeting May 4th N Re: Absolute fastest way to get a 100% correct record count for RMS     files?
 Re: AES V2.2E 
 Re: AES V2.2E  Re: Capellas supports Microsoft  Re: Comments on ABS v3.0, Re: Compaq not as bad as Andrew says (wish?), Re: Compaq not as bad as Andrew says (wish?) Compaq not ignoring VMS." Current Release Oracle for OpenVMS& Re: Current Release Oracle for OpenVMS& Re: Current Release Oracle for OpenVMS& Re: Current Release Oracle for OpenVMS Re: DECserver 90L+ Problem Re: DECserver 90L+ Problem Re: DECserver 90L+ Problem Re: Efficient Sleep function Re: ES40 Configuration Re: ES40 Configuration Re: ES40 Configuration Re: ES40 Configuration Re: ES40 Configuration( Re: External authentication in a cluster( Re: External authentication in a cluster( Re: External authentication in a cluster Re: FTP problem  Re: FTP Server Logs.* FW: OpenVMS vs Tru64 Pathworks performance Re: General discussion comment Re: General discussion comment' Re: HLL (or DCL) ADMIN SEND equivalent? I Re: Hoff or Andy G., Please! Re: VAX VMS 7.2 Bug? ;backup/image/(no)alias ( How do I fix RMS corruption of MAIL.MAI?, Re: How do I fix RMS corruption of MAIL.MAI?A I/O cache - HSZ, was Re: Compaq not as bad as Andrew says (wish?)  INFO-VAX-REQUEST Re: looking for blast.com  Re: looking for blast.com  RE: looking for blast.com  Re: MicroVMS 4.4 Re: MicroVMS 4.4 Re: MicroVMS 4.4 Re: Migrating from VMS to AIX  Re: Migrating from VMS to AIX  Re: Motif - Version? Re: MOZILLA M16 ? # Re: none urgent cobol exit question * Re: OpenVMS vs Tru64 Pathworks performance* Re: OpenVMS vs Tru64 Pathworks performance* Re: OpenVMS vs Tru64 Pathworks performance* Re: OpenVMS vs Tru64 Pathworks performance PATCHs
 Re: PATCHs- Please ignore, just testing rules of exchange / POS/credit card verification with OpenVMS Alpha  Re: Problem with resource locks  Re: Problem with resource locks  Re: Problem with resource locks  Pruebas ' Re: Remote Print From Vax/VMS to AS/400 ' Re: Remote Print From Vax/VMS to AS/400  SBS PCI-VME adaptor  Telnet and License Re: Telnet and License Re: Telnet and License Re: Telnet and License Re: Telnet and License Unneeed RMS overhead with C  Re: Unneeed RMS overhead with C  Re: Unneeed RMS overhead with C  UNSUB INFO-VAX Re: UNSUB INFO-VAX
 VAX on Intel?  Re: VAX on Intel? - Re: VAX VMS 7.2 Bug? ; backup/image/(no)alias - Re: VAX VMS 7.2 Bug? ; backup/image/(no)alias @ VAXCluster Principles book (was Re: Problem with resource locks)D Re: VAXCluster Principles book (was Re: Problem with resource locks) Re: Wildfire Announcement  Re: Wildfire Announcement  Re: Wildfire Announcement  Re: Wildfire Announcement  RE: Wildfire Announcement  Re: Wildfire Announcement  X Font Server for VMS  Re: X Font Server for VMS   F ----------------------------------------------------------------------  % Date: Wed, 31 May 2000 13:38:31 +0100 - From: Tim Llewellyn <tim.llewellyn@bbc.co.uk> @ Subject: Re: "VMS on Wildfire" Slides from NELUG meeting May 4th( Message-ID: <393507C7.4E1FEEA@bbc.co.uk>   Paul Sture wrote:   > > In article <C22568E9.005A6362.00@jklh21.valmet.com>,  wrote: >  > >  > > Soon to be fixed!  > > M > > [BSOD's notwithstanding, it is no less unsafe to "turn off" a VMS machine  > > without first ? > > performing an orderly shutdown than it is a Wintel machine. P > > You never shut down an OpenVMS cluster, but you do sometimes shut down a VMSD > > machine. The "beauty part" is that they are not the same thing.] > > N > Sorry, but I have to correct you there. NT employs a "lazy write" technique.  J Just as well UPS's are standard kit for servers these days, then isn't it.  -- 6 Tim Llewellyn, OpenVMS Infrastructure, Remarcs Project0 MedAS at the BBC, Whiteladies Road, Bristol, UK.A Email tim.llewellyn@bbc.co.uk. Home tim.llewellyn@cableinet.co.uk   A I speak for myself only and my views in no way represent those of  MedAS or the BBC.    ------------------------------    Date: 31 May 2000 12:03:37 +0200G From: Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de> W Subject: Re: Absolute fastest way to get a 100% correct record count for RMS     files? H Message-ID: <y4u2ffujd2.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>  , David A Froble <davef@tsoft-inc.com> writes:  L > Are you saying that for an indexed file, the buffer(s) allocated when the ; > file is opened are the size of the buckets for the file?    ) Exactly. To quote from the RMS manual at  B http://www.openvms.digital.com:8000/72final/4523/4523pro_010.html:   "7.11 RAB$B_MBC field   E The multiblock count (MBC) field applies only to sequential disk file 
 operations. "    	Jan   ------------------------------  % Date: Wed, 31 May 2000 13:30:06 +0100 - From: Tim Llewellyn <tim.llewellyn@bbc.co.uk>  Subject: Re: AES V2.2E) Message-ID: <393505CE.A49E2332@bbc.co.uk>    Rudolf Wingert wrote:    > Hello, > M > yes we have AES 2.2E running here in Ettlingen (Germany). In case of having N > ISDN we do use an Elsa ISDN TLpro ISDN terminal adapter. This one works fineF > for us. I do have a few problem with the changed behavior of DSN ITSF > (only one line buffer for line editing) and that ther is no documen-K > tation of complete new one AES. That's a normal UNIX problem (the new AES B > is the UNIX version build for OpenVMS), bad or no documentation. >   M Aw my god, why DO they do this. Why not port the VMS version to unix? To much 
 functionality  perhaps?   >  > Regards Rudolf Wingert   --6 Tim Llewellyn, OpenVMS Infrastructure, Remarcs Project0 MedAS at the BBC, Whiteladies Road, Bristol, UK.A Email tim.llewellyn@bbc.co.uk. Home tim.llewellyn@cableinet.co.uk   A I speak for myself only and my views in no way represent those of  MedAS or the BBC.    ------------------------------  % Date: Wed, 31 May 2000 06:54:28 -0700 ? From: Mike Price <mike.priceNOmiSPAM@littlewoods.co.uk.invalid>  Subject: Re: AES V2.2E9 Message-ID: <04f3035e.38753166@usw-ex0103-086.remarq.com>   ? Thanks - I wouldn't have to go through the pain of working that 
 one out!!!  L * Sent from RemarQ http://www.remarq.com The Internet's Discussion Network *G The fastest and easiest way to search and participate in Usenet - Free!    ------------------------------   Date: 31 May 2000 02:24 CST ' From: carl@gerg.tamu.edu (Carl Perkins) ( Subject: Re: Capellas supports Microsoft- Message-ID: <31MAY200002245636@gerg.tamu.edu>   \ In article <392EB67C.C852923C@tsoft-inc.com>, David A Froble <davef@tsoft-inc.com> writes... }"Ebinger . Eric" wrote: }>   }> > -----Original Message----- : }> > From: Terry C. Shannon [mailto:shannon@world.std.com]K }> > Well, a significant number of Americans feel otherwise. They voted for < }> > Clinton twice. And some would vote for him again if the }> > Constitution didn't }> > proscribe same. }> > }>  B }> Actually, it's an AMENDMENT to the constitution that limits the: }> an individuals time as president to (roughly) 10 years. }>   }> Eric Ebinger   }> Dynamics Research Corporation } N }More specifically, 2 consecutive terms.  However, I believe that after a termP }out of office, an ex president can then return for another two terms, should heO }be so stupid.  It appears that after several years of reflection, no-ones been O }crazy enough to want to subject themselves to the experience again.  There was P }Nixon, running and winning in 68, after being Ike's VP and losing to JFK in 60,< }but history has been rather harsh on his thought processes. }  }Dave   F You are mistaken. It is 2 terms. Not 2 consecutive terms. Any instanceF where the VP (or other person farther down the list) becomes PresidentI for more than 2 years counts, in effect, as a term. Thus the actual limit G is 2 terms + 2 years = 10 years (since a term is 4 years - if this were ? changed the maximum time in office would change along with it).    The actual text of the thing:       AMENDMENT XXII (1951)    G    Section 1. No person shall be elected to the office of the President G    more than twice, and no person who has held the office of President, I    or acted as President, for more than two years of a term to which some G    other person was elected President shall be elected to the office of F    President more that once. But this Article shall not apply to any  H    person holding the office of President when this Article was proposedG    by Congress, and shall not prevent any person who may be holding the F    office of President, or acting as President, during the term withinB    which this Article becomes operative from holding the office ofF    President or acting as President during the remainder of such term.  I    Section 2. This article shall be inoperative unless it shall have been I    ratified as an amendment to the Constitution by the legislatures of    G    three-fourths of the several States within seven years from the date 4    of its submission to the States by the Congress.    --- Carl   ------------------------------  % Date: Wed, 31 May 2000 08:06:07 -0500 1 From: "Dave Gudewicz" <david.gudewicz@abbott.com> ! Subject: Re: Comments on ABS v3.0 8 Message-ID: <8h32he$3db$1@fizban.fizban.pprd.abbott.com>  C Thanks for the comments.  I look forward to your benchmark results.    Dave...   J <itjck01@my-deja.com> wrote in message news:8h1der$vn6$1@nnrp1.deja.com...: > In article <8gm3kv$71u$1@fizban.fizban.pprd.abbott.com>,6 >   "Dave Gudewicz" <david.gudewicz@abbott.com> wrote:B > > We've been trying for a few months now to get ABS v3.0a to run
 > > reliably.  > > G > > Policy engine failures, media off-line and several other items seem  > > to be preventing this. > > = > > Support has been involved all along.  Still no solutions.  > > * > > We heard there's a 3.0b out there now. > > F > > Anyone here using - or put another way - trying to use this stuff? > >  > > Dave...  > >  > >  > 3 > ABS 3.0b is on the June 2000 Cosolidated CD-DIST.  > J > We hired Compaq to come in and install and configure about 2 months ago. > I > Comparing to our current backup software (ISE Media/BCKMGR/SCHEDULE) we F > have fould ABS to be very much less integrated.  I have had to writeH > DCL script to use the Media Robot Utility software to inject and ejectE > tapes to our TL896, and then follow up with Media Device Management I > System commands to keep it in sync with what we did in MRU.  We use MRU H > so we do not have to open up TL896 door, but rather use injection port > and ejection port. > I > We had some code beyond 3.0b put in to allow us to do media compression D > with our tape drives, and this has worked out well allowing better > throughput to tape.  > I > To date, and this is only about a month into it, ABS 3.0b (yeah, we got B > 3.0b ahead of CD distribution) has done ok.  I have not seen theD > problems the others have posted, but then again I am not using ABS% > completely yet nor for a long time.  > G > I expect to do benchmark on tape backup performance in a few days.  I / > will try to post, once I have done benchmark.  >  > :) jck >  > --& > Free personal opinion is what I post >  > ( > Sent via Deja.com http://www.deja.com/ > Before you buy.    ------------------------------   Date: 31 May 2000 15:33:26 GMT2 From: mathog@seqaxp.bio.caltech.edu (David Mathog)5 Subject: Re: Compaq not as bad as Andrew says (wish?) , Message-ID: <8h3bc6$2gl@gap.cco.caltech.edu>  X In article <aTT5NM+KjsR7@eisner.decus.org>, young_r@eisner.decus.org (Rob Young) writes:b >In article <8h0n8i$d7t@gap.cco.caltech.edu>, mathog@seqaxp.bio.caltech.edu (David Mathog) writes:U >> In article <8gs3ga$jbg$1@pyrite.mv.net>, "Bill Todd" <billtodd@foo.mv.com> writes:  >>> J >>>And of course that last dovetails neatly with your own observation thatM >>>people seldom bother with much performance optimization:  for such typical N >>>non-performance-optimized applications, Unix therefore makes more efficientJ >>>use of the hardware than VMS does, hence is correctly perceived as more >>>cost-effective. >>  H >> Exactly.  And it all boils down to (essentially) a SINGLE difference M >> between the OS's.   On a typical lightly loaded, memory rich, workstation, C >> Linux (and probably most other Unices, but I can't say for sure) D >> automatically utilize the unused portions of memory to cache file >> operations.     <SNIP>   > . >	So things aren't moving fast enough for you? > @ >	Caching gets much improved in the next go round of VMS (unlessE >	I've mixed up roadmaps or am misremembering).  How did this happen? E >	Senior engineer at a DECUS explained that: "remember, VIOC was just B >	a stop-gap measure... it wasn't supposed to be around this long"B >	or something similar.  Relase notes showed new sysgen parametersF >	for write behind caching and write delay.  Something to look forwardE >	to.  So how did this happen?  Fork in the road called Spiralog from  >	what I understand. >   G I'm not counting any of those chickens before they hatch.  Remember the I buildup for Spiralog, and how many of us ended up using that?  Meanwhile, K back at the farm, for the sorts of applications which I (and everybody else H in my field run) Linux and Tru64 "out of the box" outperform VMS "out ofD the box" on identical hardware by a wide margin on systems which areK "lightly loaded".  This is true for virtually every application which "runs H faster on Unix than on OpenVMS".  Moreover, it's likely that much of theK weakness we see in FTP server and SMB server performance on OpenVMS are due B to this single difference (with the rest being due to TCP/IP stack, incompatibilities with the client systems.)   G The point I'm trying to make is that virtually all of the difference in G performance one sees between Unix and OpenVMS is due to the presence of D file caching on the former and its absence on the latter.  This is aG problem which is easily identified and SHOULD BE RECTIFIED.  (Really it H should have been addressed many years ago but that's another harangue.) F Right now, as others have said, the only Compaq supplied product whichE could improve the situation is an HSZ or some other dedicated storage 2 controller - but who can afford those for a DS10?   K Nor am I saying that OpenVMS file caching need be exactly like that on Unix H - it just needs to give most of the benefits, and do so without the needH for case by case RMS twiddling.  Clearly it must preserve the capabilityJ for doing all of the things RMS does now, which really are appropriate andG useful on heavily loaded systems where there is no extra RAM around for  file caching.   B >	So maybe in a year or less, we put the limited caching behind usG >	for those that are at 7.3 and higher and maybe move on to complaining = >	that VMS is so primitive because a lot still has to be done E >	at a command line.  How primitive.  MS-DOS is dead... I want things % >	to look and feel just like Windows.  >   I Oh come on.  It's perfectly fair to point out that on small systems under G typical loads for such systems the file caching mechanisms used by Unix E (and WNT) do result in real increases in system performance, and it's G equally fair to point out that many pieces of software ported from Unix K implicitly assume this behavior and so run less efficiently on OpenVMS than K they do on Unix.  This thread has nothing to do with GUIs vs. command line, F it's about the real 2X to 3X performance boost that you get with file  caching.   Regards,   David Mathog mathog@seqaxp.bio.caltech.edu ? Manager, sequence analysis facility, biology division, Caltech     ------------------------------  % Date: Wed, 31 May 2000 13:08:01 -0400 " From: Dan Sugalski <dan@sidhe.org>5 Subject: Re: Compaq not as bad as Andrew says (wish?) 8 Message-ID: <4.3.1.0.20000531130614.00c1df00@24.8.96.48>  . At 03:33 PM 5/31/00 +0000, David Mathog wrote:: >This thread has nothing to do with GUIs vs. command line,F >it's about the real 2X to 3X performance boost that you get with file	 >caching.   G Just out of curiosity, do you see any sorts of speedup from doing this:    $ SET RMS/BUFFER=255/BLOCK=127  ? before running the programs that perform less than wonderfully?    					Dan  I --------------------------------------"it's like this"-------------------02 Dan Sugalski                          even samurai? dan@sidhe.org                         have teddy bears and evens;                                       teddy bears get drunk?   ------------------------------  % Date: Wed, 31 May 2000 10:31:12 +0100m8 From: John Macallister <J.Macallister1@physics.ox.ac.uk>! Subject: Compaq not ignoring VMS.eL Message-ID: <B8D7D072032FD411BE7A0090279FA2401ED594@ppnt41.physics.ox.ac.uk>  J During the the last few weeks I received a mail shot from Compaq (actuallyL multiple copies of the same mail shot) about three new systems. At least twoE of them came with VMS. I don't see that as ignoring VMS. In fact it'scH mentioning VMS where it really matters i.e. in the literature from which& people are actually making decisions.    John  B Name: John B. Macallister  E-mail: j.macallister1@physics.ox.ac.ukH Post: Nuclear and Astrophysics Laboratory, Keble Road, Oxford OX1 3RH,UKA Phone: +44-1865-273388 (direct)  273333 (reception)  273418 (Fax)e   ------------------------------  % Date: Wed, 31 May 2000 07:13:43 -0500o" From: Earl Lakia <lakia@ipact.com>+ Subject: Current Release Oracle for OpenVMS ) Message-ID: <393501F7.3A25A0B7@ipact.com>c  7 Does anyone know what the latest version of Oracle thatM8 runs on OpenVMS?  I thought it was Oracle 7.3.  However,< one of my customers said he got a quote from Oracle for 8.0.  A Oracle's web site is difficult to find the answer.  When I searchV9 for OpenVMS I get all the RDB releases.  Sometimes Oracler8 sales are less than knowledgeable of their own products.   --
 Earl D. LakiaL0 Senior Staff Engineer         Web: www.ipact.com4 Snail Mail:                   Email: lakia@ipact.com
 IPACT Inc.1 260 S. Campbell St.           Phone: 219-464-7212p Valparaiso, IN 46383   ------------------------------  % Date: Wed, 31 May 2000 07:44:12 -0500e1 From: "Dave Gudewicz" <david.gudewicz@abbott.com>i/ Subject: Re: Current Release Oracle for OpenVMS 8 Message-ID: <8h318a$375$1@fizban.fizban.pprd.abbott.com>  6 Oracle 8 is indeed available for OpenVMS.  Details at:# http://platforms.oracle.com/compaq//   Dave...0  - Earl Lakia <lakia@ipact.com> wrote in message # news:393501F7.3A25A0B7@ipact.com...c9 > Does anyone know what the latest version of Oracle thate: > runs on OpenVMS?  I thought it was Oracle 7.3.  However,> > one of my customers said he got a quote from Oracle for 8.0. > C > Oracle's web site is difficult to find the answer.  When I searchg; > for OpenVMS I get all the RDB releases.  Sometimes Oracle : > sales are less than knowledgeable of their own products. >) > -- > Earl D. Lakiap2 > Senior Staff Engineer         Web: www.ipact.com6 > Snail Mail:                   Email: lakia@ipact.com > IPACT Inc.3 > 260 S. Campbell St.           Phone: 219-464-7212n > Valparaiso, IN 46383 >n >c   ------------------------------  # Date: Wed, 31 May 2000 13:11:26 GMT-% From: Alan Greig <agreig@my-deja.com>-/ Subject: Re: Current Release Oracle for OpenVMS8) Message-ID: <8h331i$5rv$1@nnrp1.deja.com>l  ) In article <393501F7.3A25A0B7@ipact.com>,"%   Earl Lakia <lakia@ipact.com> wrote:s9 > Does anyone know what the latest version of Oracle that : > runs on OpenVMS?  I thought it was Oracle 7.3.  However,> > one of my customers said he got a quote from Oracle for 8.0. >aC > Oracle's web site is difficult to find the answer.  When I search ; > for OpenVMS I get all the RDB releases.  Sometimes Oraclel: > sales are less than knowledgeable of their own products.  F Oracle 8.0.5 is the latest with Oracle 8i due for release any day now.@ Oracle have not dropped VMS so new releases continue to show up.   > -- > Earl D. Lakia"2 > Senior Staff Engineer         Web: www.ipact.com6 > Snail Mail:                   Email: lakia@ipact.com > IPACT Inc.3 > 260 S. Campbell St.           Phone: 219-464-7212e > Valparaiso, IN 46383 >s >,   -- --
 Alan Greig    & Sent via Deja.com http://www.deja.com/ Before you buy.    ------------------------------  # Date: Wed, 31 May 2000 14:24:09 GMTB3 From: "Gord Coulman" <nospam_gcoulman@ccinet.ab.ca>y/ Subject: Re: Current Release Oracle for OpenVMSm8 Message-ID: <dg9Z4.8402$6x.190172@news0.telusplanet.net>  I 8.0.5 needs a patch.  It then becomes 8.0.5.0.1  I think you can download ! the patch from Oracle's ftp site.t   Gord.o  ' >   Earl Lakia <lakia@ipact.com> wrote:e9 > Does anyone know what the latest version of Oracle that  > runs on OpenVMSe   ------------------------------  % Date: Wed, 31 May 2000 09:24:27 +0200s5 From: Oswald Knoppers <Oswald.Knoppers@whitehouse.nl>a# Subject: Re: DECserver 90L+ Problemm, Message-ID: <3934BE2B.5F929E4@whitehouse.nl>   Eric Dittman wrote:   G > I create the port and set the port, but a mcr latcp show port LTAxxx:oF > shows the target port and node name as specified but the actual portB > and node name are blank.  The local port state is also inactive.  G On the ds90l+ you have to set the port to printer in order to access itf from remote.   Regards,   Oswald   ------------------------------  # Date: Wed, 31 May 2000 10:08:33 GMTn= From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-)T# Subject: Re: DECserver 90L+ Problemv0 Message-ID: <009EAE4F.1CE317BA@SendSpamHere.ORG>  u In article <it_Y4.15298$v7.1041339@news-west.usenetserver.com>, Eric Dittman <dittman@narnia.int.dittman.net> writes:r, >Peter LANGSTOEGER <eplan@kapsch.net> wrote:w >: In article <ODTY4.12542$v7.902607@news-west.usenetserver.com>, Eric Dittman <dittman@narnia.int.dittman.net> writes:t9 >:>I've got a DS90L+ that I'm trying to connect to remote 8 >:>devices.  I've set the name to TS90 in the DS90L+ and: >:>created a LAT terminal pointing to PORT_8 (which is the6 >:>name of port 8).  The system (OpenVMS Alpha V7.2-1)7 >:>can't find the DS90L+ so the LAT terminal never getse; >:>created.  I can SET HOST/MOP TS90 and connect.  Is there-; >:>something else that must be done?  I've also got a DS70008 >:>that I am able to create LAT terminals on, so I'm not- >:>sure what I'm doing wrong with the DS90L+.D >0L >: MOP is not LAT. If you can reach the DS90L with MOP doesn't mean LAT will >: be working. >f> >I know that MOP is not LAT.  I mentioned that I could connect< >via MOP because if I didn't someone would ask if I'd tested& >whether it had Ethernet connectivity. >eB >: Where did you enter the name of the DS90L ? In the MOP(=DECnet): >: 	database on VMS or additionally in the DS90L+ server ? >:6 >I put the name in the MOP database and in the DS90L+. >6H >: Did you configure the server name in the permanent _and_ the volatileA >: 	database of the DS90 ? In other words did you reboot the DS90> >: 	after the configuration ?- >  >Yes.F >:4 >: Do you have LAT enabled on your VMS host system ?- >: 	What does $ MC LATCP SHOW CHAR show you ?t1 >: 	What does $ MC LATCP SHOW SERVICES show you ?o >wB >Yes LAT works.  If I use a terminal connected to the DS90L+ I can >connect to the VMS system.t >lQ >: Is LAT a protocol you network still transmits (not filtered in the switches) ?  >s >Yes (see above).1 >eM >: Why do you think, a LAT port can't be created to a non-responding server ?fA >: 	It can be created (eg. during boot time) but it can't be used C >: 	without a connection to the destination, then (which may happen,6 >: 	many times during the uptime of the VMS system) !! >eF >I create the port and set the port, but a mcr latcp show port LTAxxx:E >shows the target port and node name as specified but the actual port A >and node name are blank.  The local port state is also inactive.h  I That doesn't mean that the port is not properly configured or will not ben functional.m   Here's my port I just created:( ----------------------------------------K Local Port Name:   _LTA5:            Local Port Type:  Application (Queued), Local Port State:  Inactivei Connected Link:+  9  Target Port Name:     PORT_3           Actual Port Name: 9  Target Node Name:     DS90L1           Actual Node Name:i<  Target Service Name:                   Actual Service Name:( ----------------------------------------  J I plug in a loopback connector to port 3 on the DECserver 90L+ and issue a( SET HOST/DTE LTA5, the above changes to:  ( ----------------------------------------K Local Port Name:   _LTA5:            Local Port Type:  Application (Queued)e Local Port State:  ActiveP Connected Link:    LAT$LINKt  D  Target Port Name:     PORT_3           Actual Port Name:     PORT_3D  Target Node Name:     DS90L1           Actual Node Name:     DS90L1<  Target Service Name:                   Actual Service Name:( ----------------------------------------   J Why don't you check your setup out in the same fashion.  BTW, you need theJ loopback or you get hung up in the SET HOST/DTE.  DEC used to provide themK with some MMJ equipment.  You can make on easily by connecting the lines ofr, a MMJ plug together thusly:  1-6; 2-5; 3-4;    --N VAXman- OpenVMS APE certification number: AAA-0001           VAXman@TMESIS.COM  L GNU Freeware -- What does the GNU *really* stand for?  Garbage!  Not Usable!   ------------------------------  # Date: Wed, 31 May 2000 16:33:35 GMT 3 From: Eric Dittman <dittman@narnia.int.dittman.net> # Subject: Re: DECserver 90L+ Probleme? Message-ID: <z9bZ4.19986$v7.1254311@news-west.usenetserver.com>f  6 Oswald Knoppers <Oswald.Knoppers@whitehouse.nl> wrote: : Eric Dittman wrote:k  H :> I create the port and set the port, but a mcr latcp show port LTAxxx:G :> shows the target port and node name as specified but the actual port C :> and node name are blank.  The local port state is also inactive.o  I : On the ds90l+ you have to set the port to printer in order to access itl : from remote.   Thanks, Oswald, that fixed it!   -- o Eric Dittman dittman@dittman.netp   ------------------------------  % Date: Wed, 31 May 2000 09:29:09 +0100t* From: "Richard Brodie" <R.Brodie@rl.ac.uk>% Subject: Re: Efficient Sleep functiony, Message-ID: <8h2igl$17m6@newton.cc.rl.ac.uk>  K <bbrzwski@my-deja.com> wrote in message news:8h0tfs$inp$1@nnrp1.deja.com...r  + > for(int i=1; i<=1000; i++) Sleep(0)  30msa- > for(int i=1; i<=1000; i++) Sleep(1)  1953mse  F What I imagine is happening is that the timer fires immediately in theJ first case. In the second it waits 1ms first; however you have just missed- one, so you have to wait another .95 seconds.   F Timers are chained off the hardware interval timer. Every n ms it goesL round looking to see what jobs it has to do. You can't get finer granularityH than this rate. My copy of I&DS gives 10ms but I guess it must be 1ms on Alpha.   ------------------------------    Date: 31 May 2000 11:30:52 +0200G From: Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de>a Subject: Re: ES40 ConfigurationaH Message-ID: <y4zop7ukvn.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>  + "John E. Malmberg" <wb8tyw@qsl.net> writes:s  0 > Otherwise if a bad device jams a channel [...]  L How often does that really happen - a disk jamming the channel for all otherL devices? I would have thought that to be an extremely rare failure mode, and; easily recovered from by disconnecting it from the channel.    	Jan   ------------------------------  % Date: Wed, 31 May 2000 11:22:51 +0100j  From: steven.reece@quintiles.com Subject: Re: ES40 Configuration-> Message-ID: <802568F0.00391819.00@qedilc01.qedi.quintiles.com>   Dan Sugalski wrote:vJ >>>7) If the system's on a reliable UPS (and it is, *right*?), then enableI write-back caching on all the drives. You *will* see a win on drives thatu% are written to with any frequency.<<<o  K But you might not want to do that on disks related to Oracle (that's OracleaP Classic, not RDB).  Whenever we have a problem with Oracle we get told "turn offH write back caching".  We say "but we've never had it on the disks in ourP ESA10000s".  They then respond with any other cache (almost taken at random) andP say "is it on?" to which we respond "yes, but it makes no difference to what the< Oracle stuff is doing" and we still get told to take it off.   Result ?I We have no caching anywhere with our Oracle setups.  Performance may suckEN because of it when the database loads get up but that's not for me to questionK (I only try to maintain the viability of the systems - I don't do apps likex databases).y   Steve.   ------------------------------  % Date: Wed, 31 May 2000 07:33:22 -0400o" From: Dan Sugalski <dan@sidhe.org> Subject: Re: ES40 Configurationo8 Message-ID: <4.3.1.0.20000531073037.028c9b80@24.8.96.48>  < At 11:22 AM 5/31/00 +0100, steven.reece@quintiles.com wrote:     >Dan Sugalski wrote:L > >>>7) If the system's on a reliable UPS (and it is, *right*?), then enableJ >write-back caching on all the drives. You *will* see a win on drives that& >are written to with any frequency.<<< >lL >But you might not want to do that on disks related to Oracle (that's OracleH >Classic, not RDB).  Whenever we have a problem with Oracle we get told G >"turn off write back caching".  We say "but we've never had it on the o
 >disks in ouroF >ESA10000s".  They then respond with any other cache (almost taken at G >random) and say "is it on?" to which we respond "yes, but it makes no  H >difference to what the Oracle stuff is doing" and we still get told to 
 >take it off.u  J Oracle doesn't know what the heck it's talking about, then. It's possible J that some other manufacturer has a cache problem (EMC or Sun, perhaps, or J someone's software RAID), but it works fine for StorageWorks devices. You G can shoot yourself by yanking the power or a drive before the cache is  F flushed, but operationally? No difference, just the speed boost and a ( larger danger window in case of failure.   					Dan  I --------------------------------------"it's like this"-------------------a2 Dan Sugalski                          even samurai? dan@sidhe.org                         have teddy bears and evenh;                                       teddy bears get drunkh   ------------------------------  % Date: Wed, 31 May 2000 07:24:22 -0500 ) From: "John E. Malmberg" <wb8tyw@qsl.net>o Subject: Re: ES40 Configurationt/ Message-ID: <sja0noho5pj170@corp.supernews.com>w  D Jan Vorbrueggen <jan#fsnif.neuroinformatik.ruhr-uni-bochum.de> wrote
 in messageB news:y4zop7ukvn.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de...1 > "John E. Malmberg" <wb8tyw@qsl.network> writes:U > 2 > > Otherwise if a bad device jams a channel [...] >sH > How often does that really happen - a disk jamming the channel for all other J > devices? I would have thought that to be an extremely rare failure mode, ande= > easily recovered from by disconnecting it from the channel.R  J I have not seen it on an HSG or HSZ array.  It may be a rare failure mode,K but one that is very possible.  It all depends on how critical your data is $ to you, and your degree of paranoia.  K If such a failure occurs, by the time you physically remove the device fromvI the channel, if another disk in the raid set is on the same channel, then F you have potentially lost data on the RAID set.  At the least you have- downtime on anything accessing that RAID set.f  E I have seen a channel lost on a backplane RAID controller a few timeseL because of cabling problems.  If more than one member of the RAID set was on) that channel, it would have been noticed.a  L Also there are performance reasons for only putting one member of a RAID set on each channel.   -John  wb8tyw@qsl.network   ------------------------------   Date: 31 May 2000 10:31:42 PDTT From: Fairfield@SLAC.Stanford.EDU (Ken Fairfield; SLAC: 650-926-2924; FAX: 926-3515) Subject: Re: ES40 Configurationc3 Message-ID: <iPT82g3izbjb@mccdev.slac.stanford.edu>-  I In article <y4zop7ukvn.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>, <M     Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de> writes:-- > "John E. Malmberg" <wb8tyw@qsl.net> writes:> > 1 >> Otherwise if a bad device jams a channel [...]i > N > How often does that really happen - a disk jamming the channel for all otherN > devices? I would have thought that to be an extremely rare failure mode, and= > easily recovered from by disconnecting it from the channel./  #         I expect it is rare, but...t  H         The one case of controller  crashes  I've  encountered (in 3 1/2H     years)  with  my dual-redundant HSJ50's (in an SW300) was  a  failedH     RZ29B.  Fortunately, I had booted the AS4100 from the CDrom (as partH     of a VMS upgrade) and was  trying  to  copy  (BACKUP)  one  disk  toH     another  in  the SW300.  Part way into the BACKUP (5 or 10 minutes),H     the controller that happened to be  accessing one of the disks beingH     copied/written  would crash (causing the BACKUP to fail) and reboot.H     Then the other controller would do the same.  It turns out that  oneH     of  the  two disks being accessed by BACKUP was on the same SCSI busH     as the failing (failed) RZ29B, and  that failing disk must have beenH     doing  something  nasty on the bus.  Result: controller crash.   I'mH     just glad it happened  at  a  time  when  it  really  didn't  affect-     anything (like running the accelerator!).a  E         Moral: a bad device on a SCSI bus can wreak havoc.  Beware...p               -Ken -- RM  Kenneth H. Fairfield            |  Internet: Fairfield@SLC.Slac.Stanford.Edu3:  SLAC, 2575 Sand Hill Rd, MS 46  |  Voice:    650-926-2924:  Menlo Park, CA  94025           |  FAX:      650-926-3515N  -----------------------------------------------------------------------------B  These opinions are mine, not SLAC's, Stanford's, nor the DOE's...   ------------------------------  % Date: Wed, 31 May 2000 05:31:09 -0700u5 From: Richard  <maher_rjNOmaSPAM@hotmail.com.invalid>c1 Subject: Re: External authentication in a clustern9 Message-ID: <089f08e0.54f5ef8f@usw-ex0108-061.remarq.com>m   Hi,l  8 I don't have web addresses for you but the following are easy to find:-   Compaq's own web site -e  : Open Systems Standards Tracking Report. Vol 7 No 11 Nov 988 (Transaction Internet Protocol: Gateway to Heterogeneous( Internet Transactions) by Keith B. Evans  9 It's ironic that Keith (who wrote the book) now works for 1 Compaq (since it aquired Tandem) But he's not VMSg7 engineering so we won't be talking to him! Yeah that'll : learn 'em! I'd rather see Rich Marcello being cajoled into9 swapping the ACMS and RTR deckchairs on the V.M.S TITANICt *NOT*!   Transaction Internet Protocolp8 (A heterogeneous, two-phase commit protocol that ensures' the integrity of internet transactions)m  ; I especially like the paragraph "Compaq's leadership in TIPe
 development".n   Microsoft's web site -   DtcGetTransactionManagerEx  3 Using Microsoft Distributed Transaction Coordinator   0 Using MS DTC with other TIP Transaction Managers$ See especially "TIP Usage Scenarios"   WWW somewhere -s  ( See also RFCs 2372 (brilliant) and 2371.   And lots, lots more. . .  9 Like most people here, I live an die (professionally) VMSe9 and I can tell you that nothing will effect its longevity ; more than TIP. This functionality *alone* would put a break ; on 80% to 90% of the decommisioning currently going on herec in London banks.   Regards Richard Maher      * Sent from AltaVista http://www.altavista.com Where you can also find related Web Pages, Images, Audios, Videos, News, and Shopping.  Smart is Beautifulc   ------------------------------  % Date: Wed, 31 May 2000 07:01:19 -0700c5 From: Richard  <maher_rjNOmaSPAM@hotmail.com.invalid>i1 Subject: Re: External authentication in a clustert9 Message-ID: <000d0278.6c7b5fb8@usw-ex0108-061.remarq.com>o   Hi,t  9 I thought I should provide some background information ont4 TIP. If anyone else has more information then please provide it.   7 Firstly, let me point out that VMS or more specificallyg: ACMSxp already has a TIP capability *now*! So well done to: the bright engineers involved as well as the shrewd person9 who gets their development bugets approved. It is however 8 limited in that the txn has to be started on Windows20007 and then propogated to VMS. (Opting for pragmatism overa9 principle this is probably not the end of the world but I:6 don't like it!) The other main problem with the ACMSxp; implementation is performance. The multiplexing features ofo9 TIP have not been implemented and XP has to keep it's own,9 log file and presumably maintain it's own monitor processo9 (es). Which we all know (at least me, the people involvedo5 on the VMS side of Compaq, and hopefully most of you)u5 should rightly be the responsibility of ***DECdtm***..  9 But more importantly, and what is gut wrenchingly bad, ist8 that *on VMS* we can take an extremely open and flexible6 two-pipe standard like TIP and wrap it up in an ACMSxp: everywhere one-pipe cloak! (And you people slag off Gates?7 He should come to VMS engineering to learn how to treatd: customers. "We're leaving money on the table. How long can8 the VMS cash cow last? Let's milk it one more time! Make5 'em buy ACMSxp Make 'em buy RTR! Where's the money in ; something that's bundled with the OS?" Rightly or wrongly I 9 still believe the only reason the DECdtm branch managmento6 services were never published was to force people into9 buying ACMS :-( If Microsoft were VMS engineering then it 0 would have said COM+ was the only way to get TIP; functionality but instead it provides easy access to an MTSe3 transaction's URL. So on Tandem and soon to be Unixr8 machines an application programmer can simply TIP_PULL()7 and get internet-wide 2PC (Please don't flame me on thea8 Microsoft stuff. I don't care about Bill Gate's. I don't; even own a PC and I do own a VAX and my VMS credentials aren9 as big as evryone elses. I use it as an example because I : believe it to be true and I want it to hit home, no hurt!)  ; And in case anyone has missed it you *DON'T NEED* TUXEDO or:8 ENCINA! If I were BEA or Transarc/IBM then I'd be really2 worried! TIP doesn't care in the slightest how you: propogate the txn URL to a participating node that's up to7 you. And if you do look at Microsoft's web site for TIP-: information you will see words like parallelism (something< that for a long time should have been possible with DECdtm!)9 with multiple processes whether or not on different nodes0% updating there data at the same time.m  9 Does Compaq not want to upset BEA? Did DEC pay for TUXEDOS; to be ported to VMS or was it BEA initiative? (Don't get meh; wrong I think it's great TUXEDO is on VMS regardless I justM like to know what things cost)  7 Anyway my point is this, VMS is not an island and needsd5 TIP. The obvious, and correct, home for TIP on VMS ist3 DECdtm. DECdtm needs to be upgraded to be 1) TCP/IP?; compliant 2) XA compliant so that non-Rdb-DBMS-RMS resourcet; managers can participate in the 2PC on VMS 3) TIP compliantn; (obviously). I believe a lot of work for points 1 and 2 has  already been done.  : Please contact your compaq reps. Tell them you want DECdtm9 out of moth-balls. You want TIP. You want VMS to continues its come back.   Regards Richard Maher.  : PS. The DECdtm SPD is factually incorrect in its claim the5 DECdtm is *uniquely* integrated/bundled (whatever theo8 wording) with the operating system. They may have copied, it, please don't let them be the best at it.       * Sent from AltaVista http://www.altavista.com Where you can also find related Web Pages, Images, Audios, Videos, News, and Shopping.  Smart is Beautifult   ------------------------------  % Date: Wed, 31 May 2000 07:02:41 -0700m5 From: Richard  <maher_rjNOmaSPAM@hotmail.com.invalid>h1 Subject: Re: External authentication in a clusterm9 Message-ID: <0e9c446b.6cd6eba2@usw-ex0108-061.remarq.com>h   Hi,a  9 I thought I should provide some background information one4 TIP. If anyone else has more information then please provide it.n  7 Firstly, let me point out that VMS or more specificallyh: ACMSxp already has a TIP capability *now*! So well done to: the bright engineers involved as well as the shrewd person9 who gets their development bugets approved. It is howevert8 limited in that the txn has to be started on Windows20007 and then propogated to VMS. (Opting for pragmatism over 9 principle this is probably not the end of the world but I 6 don't like it!) The other main problem with the ACMSxp; implementation is performance. The multiplexing features ofN9 TIP have not been implemented and XP has to keep it's own 9 log file and presumably maintain it's own monitor processs9 (es). Which we all know (at least me, the people involved-5 on the VMS side of Compaq, and hopefully most of you)55 should rightly be the responsibility of ***DECdtm***.o  9 But more importantly, and what is gut wrenchingly bad, isr8 that *on VMS* we can take an extremely open and flexible6 two-pipe standard like TIP and wrap it up in an ACMSxp: everywhere one-pipe cloak! (And you people slag off Gates?7 He should come to VMS engineering to learn how to treat-: customers. "We're leaving money on the table. How long can8 the VMS cash cow last? Let's milk it one more time! Make5 'em buy ACMSxp Make 'em buy RTR! Where's the money in ; something that's bundled with the OS?" Rightly or wrongly Is9 still believe the only reason the DECdtm branch managmentA6 services were never published was to force people into9 buying ACMS :-( If Microsoft were VMS engineering then itr0 would have said COM+ was the only way to get TIP; functionality but instead it provides easy access to an MTSM3 transaction's URL. So on Tandem and soon to be Unixt8 machines an application programmer can simply TIP_PULL()7 and get internet-wide 2PC (Please don't flame me on thed8 Microsoft stuff. I don't care about Bill Gate's. I don't; even own a PC and I do own a VAX and my VMS credentials area9 as big as evryone elses. I use it as an example because In: believe it to be true and I want it to hit home, no hurt!)  ; And in case anyone has missed it you *DON'T NEED* TUXEDO ore8 ENCINA! If I were BEA or Transarc/IBM then I'd be really2 worried! TIP doesn't care in the slightest how you: propogate the txn URL to a participating node that's up to7 you. And if you do look at Microsoft's web site for TIP0: information you will see words like parallelism (something< that for a long time should have been possible with DECdtm!)9 with multiple processes whether or not on different nodes % updating there data at the same time.   9 Does Compaq not want to upset BEA? Did DEC pay for TUXEDOi; to be ported to VMS or was it BEA initiative? (Don't get me ; wrong I think it's great TUXEDO is on VMS regardless I juste like to know what things cost)  7 Anyway my point is this, VMS is not an island and needs.5 TIP. The obvious, and correct, home for TIP on VMS ise3 DECdtm. DECdtm needs to be upgraded to be 1) TCP/IPw; compliant 2) XA compliant so that non-Rdb-DBMS-RMS resourcet; managers can participate in the 2PC on VMS 3) TIP compliantm; (obviously). I believe a lot of work for points 1 and 2 hasy already been done.  : Please contact your compaq reps. Tell them you want DECdtm  out of moth-balls. You want TIP.   Regards Richard Maher.  : PS. The DECdtm SPD is factually incorrect in its claim the5 DECdtm is *uniquely* integrated/bundled (whatever thee8 wording) with the operating system. They may have copied, it, please don't let them be the best at it.       * Sent from AltaVista http://www.altavista.com Where you can also find related Web Pages, Images, Audios, Videos, News, and Shopping.  Smart is Beautiful    ------------------------------  % Date: Wed, 31 May 2000 09:27:42 +020005 From: Oswald Knoppers <Oswald.Knoppers@whitehouse.nl>4 Subject: Re: FTP problem- Message-ID: <3934BEEE.77316B73@whitehouse.nl>e   Antony Wardle wrote:  eC > I am having a problem with ftp'ing out from an OpenVMS 7.1 systemeB > and ucx 4.2eco2. Does anyone know if there is an outgoing limit?  F There are lots of limits. But without the actual error message it is aH bit hard to guess. You can start by looking at the output of a 'ucx showH comm/mem' command and check if you have any waits or drops on one of the
 buffer types.g   Regards,   Oswald   ------------------------------  + Date: Wed, 31 May 2000 11:29:30 -0400 (AST)a? From: "Carlos A. =??Q?Jim=E9nez?=" <C_JIMENEZ@UPR1.UPR.CLU.EDU>p Subject: Re: FTP Server Logs.r1 Message-ID: <01JQ1QXMXFF6004X7Z@UPR1.UPR.CLU.EDU>l  $ to maintain the same number of files   set file/version_limit = n   n = 1,2,3,4,5,6 ---P    7 limit the files to a version especify in the value of ne     Att.  	 Carlos J.    ------------------------------  % Date: Wed, 31 May 2000 07:53:59 -0400n! From: Dan Allen <dallen@nist.gov>t3 Subject: FW: OpenVMS vs Tru64 Pathworks performance3: Message-ID: <NEBBIALHDHJMJINPGMOAAEAPCDAA.dallen@nist.gov>  H  Actually, by all reports, the best performing file server for a Windows environment6   is a NetApps (AXP based) filer.    Dan  -----Original Message----- @ From: Mark Iline - Info-VAX account [mailto:ivax@meng.ucl.ac.uk]# Sent: Tuesday, May 30, 2000 2:27 PMw To: Info-VAX@Mvb.Saic.Come3 Subject: Re: OpenVMS vs Tru64 Pathworks performancei    G From:	MX%"rpjung@mb.sympatico.ca"  "Randy Jung" 28-MAY-2000 03:20:17.60k  D Cheers for the comparison, but we really need to be lookig at recentC versions. I understand that recent versions of ASDU (Tru64 PW) have I significantly increased performance over earlier versions (several 100%).y  L > As someone mentioned, the best performing server for a Windows environment( > will probably be a Winodows NT server.  E This isn't an accurate comparison, but installing Office97 off a filed service gives something like:d   Elapsed time	Server platform( 5 minutes	NTAS 4 (450 MHz Proliant 1600) 2 minutes	ASDU (PW500AU)* >10 minutes	PW 6.0 dual CPU DS20, VMS7.1-2  & All servers on 100Mbit switched ports.     Mark   ------------------------------  % Date: Wed, 31 May 2000 03:02:10 -0400b* From: David A Froble <davef@tsoft-inc.com>' Subject: Re: General discussion comment - Message-ID: <3934B8F2.7B710C1C@tsoft-inc.com>.   "David J. Dachtera" wrote:  L You're starting to bother me a bit.  Now I have to defend Bill, something heM usually doesn't need, and I'd rather spend the time (if I have to spend it atd all) beating on him. :-)   > Bill Todd wrote: > > M > > VMS as you know it is in no danger of disappearing any time soon, so youra > > livelihood is secure.m > F > Come look for an OpenVMS job here in Metro Chicago. You may discover > otherwise.  > So, someone else got there first, likes it, and isn't leaving?  9 > > But it also has no likelihood of growing market sharepL > > by continuing business as usual (the past decade-plus should be adequateH > > proof of that, despite hardware that *should* have helped it do so). > F > Exactly what we've been pounding on Compaq about (and Digital beforeJ > them) for a *VERY* long time now. I think we're starting to make a dent,J > but that's less than half a step in a journey of several hundred million > miles.  M Things are starting to happen.  Since it appears that Compaq management is nodL longer seeking to 'kill' VMS, I'd rather approach it as a partnership than a confrontation.  H > > Extending (rather than morphing) VMS to be more palatable to a widerC > > audience can only improve matters, both for you and for Compaq.d > I > Agreed. However, would you care to elucidate the concept of "extending"sI > an o.s. which is already a superset of most of the others we encounter?   / So, you're saying there's no need for VMS V7.3?n   > > > M > > > OpenVMS feeds, houses and supports us and our families. Assault that ineE > > > *ANY* way, and you *WILL* provoke a confrontation - guaranteed.p > >mP > > If asserting that VMS is not perfect and trying to improve it constitutes an > > assault, so be it.  @ Nothing is perfect, but the pursuit of perfection is very valid.  I > Well, improving it is one thing. Let's continue rather than expand this3I > because I think you have a point further down that needs clarification.a > D > > David J. Dachtera <djesys.nospam@earthlink.net> wrote in message+ > > news:39333AF1.7CF905CC@earthlink.net...n > >h > > >rG > > > My advice? Knock off the confrontations. Period. They are neitherl! > > > appropriate nor productive.    What, and spoil Bill's fun?.  E > > > 2. There's room in the world for other o.s.-es - just not here.f   Better to know your enemy.  2 > > > This is "comp.os.vms", not "comp.os-dujour". > > >dF > > > If you want to proselytize on the merits, advantages, etc. otherL > > > o.s.-es, feel free to participate in other newsgroups, but be preparedM > > > to encounter an equal (or possibly greater) degree of bigotry regarding > > > > those systems in those groups. It's not unique to c.o.v.  P Ignoring the merits of other operating systems is like sticking your head in the sand.P  L > > No, I'll continue to feel free to point out their comparative advantagesO > > here:  VMS is a lot more capable of incorporating their strengths than theyiH > > are of incorporating VMS's (the old 'quality built in, not added on'P > > advantage), so VMS is the logical place to start if you want to wind up with/ > > a system that's superior in *all* respects.n  E Better to know your enemy.  Nothing wrong with pursuit of perfection.d  A > Yeah... So? You seem to agree with the great bulk of the c.o.v.c+ > participants. So, why the confrontations?e  O The mans gotta have some fun.  He's got to have enjoyed your kneejerk response.a  M > > The definition of 'proselytizing' involves conversion, not extension.  IfaN > > you think I've been encouraging people to convert to other systems, you've > > missed the point entirely.    Bill is active in promoting VMS.  F > Indeed. Would you care to clarify EXACTLY what your point is? PleaseJ > state your case succinctly and to the point. Where necessary, do like my7 > 6th grade teacher said: "Be specific, cite examples".n > C > Again, how can you EXTEND that which is already a SUPERSET of the3	 > others?0  B So, there's no need for VMS V7.3????  Should we dispose of the VMS developers????  I > As a host of has-been vendors have discovered, you can side step almost0H > everything in the OpenVMS environment that makes it look and feel likeI > OpenVMS (but why would you?). You can do physical I/Os and bypass ODS-2aF > as well as RMS. You can write your own device drivers and everythingD > else that uses the OpenVMS kernel without any of its outer layers. > I > PORTING UN*X-land software to OpenVMS is one thing (i.e., getting it totG > compile and run clean). INTEGRATING a program (read:application) with D > OpenVMS (ODS, RMS, DLM, etc.) is something else entirely. Just ask+ > Informix why they dropped their VMS port.s > G > _THAT_, IMHO, is where we should be focussing. Make applications moren? > intelligent, rather than dumbing OpenVMS down to their level.t > J > About the only "extension" I can see for OpenVMS is a more open approachE > to graphics card drivers as well as SCSI device drivers. OpenVMS isgE > *WAY* behind the curve on device support in these areas. One way toSF > mitigate that might be to get HSx's to talk to (de-facto) "standard"H > SCSI disks and then let OpenVMS talk to the HSx's. Not an "affordable"* > approach, but still better than nothing.  P Well, I believe Rob has mentioned the capability of specifying the use of better# file caching that's headed our way.i  O As for device support, when you're being careful and qualifying devices, you'llrI never catch up with those who just throw in a new devvice and cross theirt/ fingers, if they worry even that much about it.u  P I can see the use of a verbal user interface, should such ever become practical.  O Without going into more detail possibilities, I just want to say that your post N invoked the memory of the head of the US patent office in I believe 1890 or inO that time frame, that decided that the office should be closed since everything.J that could be invented had already been invented.  If you look at what hasJ occured since 1890, I believe that you should find it hard to say that VMS cannot be extended.n  J No flame intended here.  It's just that if you go back and read your post,* you'll say "I can't believe I wrote that".   Dave   -- s4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596; 170 Grimplin Road               E-Mail: davef@tsoft-inc.comt Vanderbilt, PA  15486a   ------------------------------    Date: 31 May 2000 11:47:08 +0200G From: Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de>a' Subject: Re: General discussion commentaH Message-ID: <y4wvkbuk4j.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>  I It seems to me that the crucial point is "Tru64 with its more lightweight M filesystem": that implies, to me, that using RMS naively in that application hH is a problem, especially if you're programming via, say, the C RTL. In a1 sense, you're buying more than you've asked for. V   	Jan   ------------------------------   Date: 31 May 2000 15:25:40 GMT6 From: DAVISM@er6.eng.ohio-state.edu (Michael T. Davis)0 Subject: Re: HLL (or DCL) ADMIN SEND equivalent?: Message-ID: <8h3atk$45k$1@charm.magnus.acs.ohio-state.edu>  G In article <8gt4vm$qco$1@mailint03.im.hou.compaq.com>, "Pathworks News"t% <Daniel.Grund@notformail.com> writes:k   >Mike,I >What exactly is it what you want to do, besides send messages with ADMINo >SEND ?  >   ? 	I have written a "foreign mail protocol" which is used to sendsL notifications to users that they have new E-mail on the server.  (Right now,J all it supports is notification via the FINGER protocol.)  I would like toH implement a means whereby I could send a message via ADMINISTER SEND (or6 equivalent) to a user to notify him/her of new E-mail.   >--c
 >Daniel Grundr >n >CompaqI >Customer Services# >Microsoft Certified Support Centree2 >Pathworks/Advanced Server Expertise Centre Europe >' >The NetherlandsD >"Michael T. Davis" <DAVISM@er6.eng.ohio-state.edu> wrote in message5 >news:8grjht$837$1@charm.magnus.acs.ohio-state.edu...t >>H >> Is there some other means to sending a message to a PC which would beF >> handled by its WinPopup/Messenger service from a VMS system running	 >Advancedb# >> Server, besides ADMINISTER SEND?n >> >>[...]t   Mike --K              Michael T. Davis              |    Systems Specialist: ChE,MSElN   E-mail: davism@er6.eng.ohio-state.edu    | Departmental Networking/ComputingJ            -or- DAVISM+@osu.edu            |     The Ohio State UniversityJ http://www.er6.eng.ohio-state.edu/~davism/ |     197 Watts, (614) 292-6928   ------------------------------  # Date: Wed, 31 May 2000 11:43:41 GMTp- From: "Richard D. Piccard" <piccard@ohio.edu>ER Subject: Re: Hoff or Andy G., Please! Re: VAX VMS 7.2 Bug? ;backup/image/(no)alias( Message-ID: <3934FAEC.18C4B160@ohio.edu>   Hoff,   L 	Thanks for responding so quickly; I am already comforted by what you wrote!  	 						RDPn     Hoff Hoffman wrote:n > Z > In article <393413D4.962816CC@ohio.edu>, "Richard D. Piccard" <piccard@ohio.edu> writes:I > :I am concerned that a gratuitous incompatible change in the meaning ofyJ > :the BACKUP command has been inflicted on the user community, or that an7 > :error in the documentation has been inflicted on us.  > I >   If BACKUP/IMAGE needs /NOALIAS to work, then it should default to it.eI >   (This DCL syntax change is something that I personally consider to beaI >   a bug in OpenVMS -- Andy and/or I need to do some research on this tot' >   figure out what happened, and why.)i > P >  --------------------------- pure personal opinion ---------------------------N >    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   -- sB ==================================================================B Dick Piccard                           Academic Technology ManagerB piccard@ohio.edu                                 Computer ServicesB http://oak.cats.ohiou.edu/~piccard/                Ohio University   ------------------------------  % Date: Wed, 31 May 2000 10:12:06 -0600o1 From: Glen Martin <GLENMARK@utxvms.cc.utexas.edu>l1 Subject: How do I fix RMS corruption of MAIL.MAI?t4 Message-ID: <3934E576.6F77A3AC@utxvms.cc.utexas.edu>  B I'm running OpenVMS Alpha v6.2, and my MAIL.MAI file appears to beB corrupted. I have the option of restoring from backup, but I wouldD prefer to repair the file if possible to avoid losing messages. I amE aware of DSNlink articles addressing this, but my attempts to dial-up * DSN ITS are failing (unrelated problem)...  1 Here is what I get when I try to access the file:    $ mail   You have 79 new messages.T   MAIL> set file mail.badN   MAIL> set folder NEWMAIL= %MAIL-E-READERR, error reading DISK$3:[GLENMARK.MAIL]MAIL.BADa5 -RMS-F-CHK, bucket format check failed for VBN = 1186a( %MAIL-I-SELECTED, 1043 messages selected  sB ANALYZE/DISK/REPAIR does not fix the problem, and a simple CONVERTE chokes on the aforementioned error, resulting in a new MAIL file with D recent messages missing. Searching through old comp.os.vms messages,> I've seen references to converting a corrupted indexed file toD sequential and back again, but I can't seem to generate a proper FDLC file due to the corruption. Here is the result of ANALYZE/FILE/RMS e   $ analyze/rms mail.bad                              lF Check RMS File Integrity                     31-MAY-2000 10:09:04.21   Page 1  DISK$3:[GLENMARK.MAIL]MAIL.BAD;2     FILE HEADERS  3         File Spec: DISK$3:[GLENMARK.MAIL]MAIL.BAD;2          File ID: (19295,155,0)         Owner UIC: [GLENMARK] ;         Protection:  System: RW, Owner: RW, Group: , World:n0         Creation Date:   19-NOV-1999 16:56:40.01?         Revision Date:   31-MAY-2000 10:04:01.46, Number: 42620c'         Expiration Date: none specifiedT0         Backup Date:     31-MAY-2000 01:01:01.010         Contiguity Options:  contiguous-best-try!         Performance Options: noneo!         Reliability Options: noner!         Journaling Enabled:  noneo     RMS FILE ATTRIBUTESX  "         File Organization: indexed         Record Format: variablex         Record Attributes:!         Maximum Record Size: 2048m8         Blocks Allocated: 24595, Default Extend Size: 15         Bucket Size: 5!         File Monitoring: disabledh         Global Buffer Count: 0     FIXED PROLOG  6         Number of Areas: 3, VBN of First Descriptor: 3         Prolog Version: 3A  + AREA DESCRIPTOR #0 (VBN 3, offset %X'0000')I           Bucket Size: 5         Reclaimed Bucket VBN: 0iE         Current Extent Start: 24581, Blocks: 15, Used: 5, Next: 24586m#         Default Extend Quantity: 15i         Total Allocation: 23885t  + AREA DESCRIPTOR #1 (VBN 3, offset %X'0040')                   p         Bucket Size: 5         Reclaimed Bucket VBN: 0iD         Current Extent Start: 24576, Blocks: 5, Used: 5, Next: 24581"         Default Extend Quantity: 5         Total Allocation: 220i  + AREA DESCRIPTOR #2 (VBN 3, offset %X'0080')v           Bucket Size: 3         Reclaimed Bucket VBN: 0nD         Current Extent Start: 24271, Blocks: 5, Used: 3, Next: 24274      F Check RMS File Integrity                     31-MAY-2000 10:09:04.33   Page 2  DISK$3:[GLENMARK.MAIL]MAIL.BAD;2    "         Default Extend Quantity: 3         Total Allocation: 490y  * KEY DESCRIPTOR #0 (VBN 1, offset %X'0000')  4         Next Key Descriptor VBN: 2, Offset: %X'0000':         Index Area: 1, Level 1 Index Area: 1, Data Area: 0         Root Level: 2*1         Index Bucket Size: 5, Data Bucket Size: 5h         Root VBN: 1331         Key Flags:'                 (0)  KEY$V_DUPKEYS    0.'                 (3)  KEY$V_IDX_COMPR  0a'                 (4)  KEY$V_INITIDX    0t'                 (6)  KEY$V_KEY_COMPR  0s'                 (7)  KEY$V_REC_COMPR  1-         Key Segments: 1-         Key Size: 8a         Minimum Record Size: 8;         Index Fill Quantity: 2560, Data Fill Quantity: 2560F"         Segment Positions:       0"         Segment Sizes:           8$         Data Type: unsigned quadword         Name: ""          First Data Bucket VBN: 62 ***  VBN 1186:  Bucket check byte is out of phase.: ***  VBN 1186:  Invalid key of reference in bucket header.? ***  VBN 1186:  Invalid bucket address sample in bucket header.k@ ***  VBN 1186:  Invalid first free byte offset in bucket header.6 ***  VBN 1186:  Invalid level number in bucket header.+ ***  VBN 1186:  Reserved flag bit 2 is set.-1 ***  VBN 1186:  VBN free space offset is invalid. 9 ***  VBN 1186:  Next-bucket pointer out of range of file.U5 Unrecoverable error encountered in structure of file.D      The analysis uncovered 9 errors.          Any ideas, or am I stuck?f   Glen   ------------------------------  % Date: Wed, 31 May 2000 13:19:32 -0400a' From: "Bill Todd" <billtodd@foo.mv.com> 5 Subject: Re: How do I fix RMS corruption of MAIL.MAI? ( Message-ID: <8h3hd5$afj$1@pyrite.mv.net>  K If you can't CONVERT the file to a sequential one to retrieve its contents,rK that makes it likely that the corrupt bucket is in the user data level.  IflG so, you can (often) get at least most of the records out of the file bymA writing a short program that retrieves records sequentially untilaH encountering the corrupt bucket, then, using the key for the last recordA successfully retrieved, starts probing randomly, incrementing (or L equivalent, for a string key) the key value until a probe succeeds, and then# continuing sequentially from there.0  G Given that most of the bucket header starting at VBN 1186 appears to begI trash, there may well be nothing to be gained from examining that bucket.hK And while you could follow the bucket chain and attempt to repair it enough)G to allow CONVERT to run, describing how to do that is considerably morev  complex than the approach above.  
 Good luck,   - bill  < Glen Martin <GLENMARK@utxvms.cc.utexas.edu> wrote in message. news:3934E576.6F77A3AC@utxvms.cc.utexas.edu...D > I'm running OpenVMS Alpha v6.2, and my MAIL.MAI file appears to beD > corrupted. I have the option of restoring from backup, but I wouldF > prefer to repair the file if possible to avoid losing messages. I amG > aware of DSNlink articles addressing this, but my attempts to dial-upe, > DSN ITS are failing (unrelated problem)... > 3 > Here is what I get when I try to access the file:m >  > $ mail >a > You have 79 new messages.t >  > MAIL> set file mail.badh >  > MAIL> set folder NEWMAIL? > %MAIL-E-READERR, error reading DISK$3:[GLENMARK.MAIL]MAIL.BADt7 > -RMS-F-CHK, bucket format check failed for VBN = 1186r* > %MAIL-I-SELECTED, 1043 messages selected >gD > ANALYZE/DISK/REPAIR does not fix the problem, and a simple CONVERTG > chokes on the aforementioned error, resulting in a new MAIL file withvF > recent messages missing. Searching through old comp.os.vms messages,@ > I've seen references to converting a corrupted indexed file toF > sequential and back again, but I can't seem to generate a proper FDLD > file due to the corruption. Here is the result of ANALYZE/FILE/RMS >e > $ analyze/rms mail.bad >hF > Check RMS File Integrity                     31-MAY-2000 10:09:04.21 > Page 1" > DISK$3:[GLENMARK.MAIL]MAIL.BAD;2 >  >e
 > FILE HEADER  >t5 >         File Spec: DISK$3:[GLENMARK.MAIL]MAIL.BAD;2d  >         File ID: (19295,155,0) >         Owner UIC: [GLENMARK]a= >         Protection:  System: RW, Owner: RW, Group: , World: 2 >         Creation Date:   19-NOV-1999 16:56:40.01A >         Revision Date:   31-MAY-2000 10:04:01.46, Number: 42620a) >         Expiration Date: none specifiedm2 >         Backup Date:     31-MAY-2000 01:01:01.012 >         Contiguity Options:  contiguous-best-try# >         Performance Options: none # >         Reliability Options: noneo# >         Journaling Enabled:  noney >  >r > RMS FILE ATTRIBUTES3 > $ >         File Organization: indexed! >         Record Format: variables >         Record Attributes:# >         Maximum Record Size: 2048t: >         Blocks Allocated: 24595, Default Extend Size: 15 >         Bucket Size: 5# >         File Monitoring: disabled   >         Global Buffer Count: 0 >  >s > FIXED PROLOG >s8 >         Number of Areas: 3, VBN of First Descriptor: 3 >         Prolog Version: 3i > - > AREA DESCRIPTOR #0 (VBN 3, offset %X'0000')  >t >         Bucket Size: 5! >         Reclaimed Bucket VBN: 0pG >         Current Extent Start: 24581, Blocks: 15, Used: 5, Next: 24586n% >         Default Extend Quantity: 15K! >         Total Allocation: 23885. >e- > AREA DESCRIPTOR #1 (VBN 3, offset %X'0040')e >  >         Bucket Size: 5! >         Reclaimed Bucket VBN: 0eF >         Current Extent Start: 24576, Blocks: 5, Used: 5, Next: 24581$ >         Default Extend Quantity: 5 >         Total Allocation: 220f >u- > AREA DESCRIPTOR #2 (VBN 3, offset %X'0080')  >. >         Bucket Size: 3! >         Reclaimed Bucket VBN: 0gF >         Current Extent Start: 24271, Blocks: 5, Used: 3, Next: 24274 >e >e > F > Check RMS File Integrity                     31-MAY-2000 10:09:04.33 > Page 2" > DISK$3:[GLENMARK.MAIL]MAIL.BAD;2 >i >s$ >         Default Extend Quantity: 3 >         Total Allocation: 490u >o, > KEY DESCRIPTOR #0 (VBN 1, offset %X'0000') >g6 >         Next Key Descriptor VBN: 2, Offset: %X'0000'< >         Index Area: 1, Level 1 Index Area: 1, Data Area: 0 >         Root Level: 2,3 >         Index Bucket Size: 5, Data Bucket Size: 5  >         Root VBN: 1331 >         Key Flags:) >                 (0)  KEY$V_DUPKEYS    0n) >                 (3)  KEY$V_IDX_COMPR  0n) >                 (4)  KEY$V_INITIDX    0 ) >                 (6)  KEY$V_KEY_COMPR  0f) >                 (7)  KEY$V_REC_COMPR  1o >         Key Segments: 1g >         Key Size: 8'  >         Minimum Record Size: 8= >         Index Fill Quantity: 2560, Data Fill Quantity: 2560c$ >         Segment Positions:       0$ >         Segment Sizes:           8& >         Data Type: unsigned quadword >         Name: """ >         First Data Bucket VBN: 64 > ***  VBN 1186:  Bucket check byte is out of phase.< > ***  VBN 1186:  Invalid key of reference in bucket header.A > ***  VBN 1186:  Invalid bucket address sample in bucket header. B > ***  VBN 1186:  Invalid first free byte offset in bucket header.8 > ***  VBN 1186:  Invalid level number in bucket header.- > ***  VBN 1186:  Reserved flag bit 2 is set.s3 > ***  VBN 1186:  VBN free space offset is invalid.e; > ***  VBN 1186:  Next-bucket pointer out of range of file.t7 > Unrecoverable error encountered in structure of file.e >i > " > The analysis uncovered 9 errors. >  >p > Any ideas, or am I stuck?a >  > Glen   ------------------------------  + Date: Wed, 31 May 2000 06:48:14 -0600 (MDT)e) From: John Nebel <nebel@ATHENA.CSDCO.COM>yJ Subject: I/O cache - HSZ, was Re: Compaq not as bad as Andrew says (wish?)G Message-ID: <Pine.OSF.4.21.0005290703080.19409-100000@athena.csdco.com>o   Bill,   J This is an attempt to address some of your points to bring what appears to0 be a one-sided point of view into better balance  E "But you need to double up on the controllers, each with stable writelJ cache, and have them communicate to avoid losing dirty data due to a cache failure"  A You probably didn't realize that HSZs are typically configured indJ dual-redundant mode with battery power sufficient for a 12-hour outage forG the caches which can be mirrored on one another and are configured thate way by default.t  J The controller can make i/o optimizations at a lower cost than the host asG its only job managing the disks.  HSZ22 is pretty cheap if ones storagee= needs are in the range of 100-500gb.  The street price of theeH newly-obsolete HSZ70 is also pretty resonable in the low terabyte range.J The three 80 series controllers have more speed and other features and are priced accordingly.t  J Unix can be darn difficult to tune - I'd never say it was easier then VMS.  J You assume away the most difficult part of the problem: "(as long as there7 are lulls during which you can dump the data to disk)."i  I One series of tests I performed with Unix on a couple of Alphas (2100 andoF ES40) with various controllers (multiple host-based, HSZ50, HSZ70) andI file systems (UFS, UFS+LSM), the HSZs were the only way to keep up with ae DS3 news feed.  H So it was a case of hardware to the rescue when nothing else worked, notC even the supposedly efficient Unix file system.  Turns out that thefF payment for host-caching, the periodic fsync, will seriously lower theJ average i/o rate in a write-mostly environment unless there is some pretty( massive controller cache to absorb it.    I There are some other payments for the Unix file system: backup/restore is H extremely time-consuming if there are many files - once a file system isH on a disk it it requires major down time to move it. Boots after crashesH can take over a hour due to fsck in the above INN environment, and thereC is the problem that the operating system has to be tuned to allow amB large-enough cache for fsck leading to an occasional reboot-never.  D Over-all, given HSxxx controllers, VMS and Unix, both of which I useJ extensively, have file systems with equivalent speed.  Personally I prefer2 the VMS one - it is a lot less hassle in practice.  
 John Nebel    % On Sun, 28 May 2000, Bill Todd wrote:-   > 7 > Keith Brown <kbrown780@usfamily.net> wrote in messagem( > news:3931BE9C.B78D355F@usfamily.net... >  > ...u > 	 > > Bill,( > >LB > > If you use HSxx controllers on your systems whether it be UnixB > > or VMS (we use them on both at my shop) the file caching issue+ > > is mute because the controller does it.r > M > Hardware to the rescue!  But as always that's a relatively expensive way to 2 > obtain performance when software can do the job. > L > Not that it always can:  when you want guaranteed persistence coupled withH > fast writes at high volume, stable write-back caching is the only realL > solution (as long as there are lulls during which you can dump the data toN > disk).  But you need to double up on the controllers, each with stable writeL > cache, and have them communicate to avoid losing dirty data due to a cacheK > failure (assuming you're using some kind of redundancy at the actual diskCK > level to guard against single points of failure), and that gets expensivesN > compared to software alternatives that require no special hardware (save forA > a sliver of NVRAM somewhere to make RAID recovery fast after anhG > interruption - which you actually only need if you can't tolerate thetF > latency of writing a log record for each write request that can't be: > batch-logged with other contemporaneous write requests). > N > Until hardware RAID (especially including copious amounts of stable cache inK > a no-single-point-of-failure dual configuration) prices come *'way* down, H > systems that ensure file system integrity while optionally trading offI > up-to-the-second persistence for overall better performance will remain,L > popular for applications that demand no stronger guarantees.  This may notL > make a great deal of sense, given how completely the cost of operating andJ > managing systems dwarfs the cost of purchasing them, but up-front systemN > price shows little indication of becoming irrelevant in typical environments > in spite of this.  >  > - bill >  > >4 > > -- > > Keith Brownh > > kbrown780@usfamily.net >  >  >    ------------------------------  % Date: Wed, 31 May 2000 10:59:54 -0400o) From: "Viens, Daniel" <DVIENS@adm.me.org>d Subject: INFO-VAX-REQUESTtI Message-ID: <DE5D35643522D411B7C10008C791D522187DB2@bdmb_5003.adm.me.org>f   UNSUB INFO-VAX   ------------------------------  % Date: Wed, 31 May 2000 01:02:33 -0400a- From: JF Mezei <jfmezei.spamnot@videotron.ca>b" Subject: Re: looking for blast.com+ Message-ID: <39349CD1.7EE97B2@videotron.ca>   B > > Does anyone have a copy of blast.com that they could email me.E > > It was posted here back in 1994-5 and I can't find it in the FAQsh  L Do you mean the BLAST serial file transfer protocol, or some other product ?   ------------------------------   Date: 31 May 2000 12:37:42 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)" Subject: Re: looking for blast.com6 Message-ID: <8h312m$4gv$1@mailint03.im.hou.compaq.com>   In article <1137A4A23A51D311B2D600105A1D5213019AEE50@seantexch.unitedad.com>, Terry Marosites <TMarosites@unitedad.com> writes:m  ? :Does anyone have a copy of blast.com that they could email me.iB :It was posted here back in 1994-5 and I can't find it in the FAQs  G   If the referenced blast tool is the tool that was used to blast MAIL pK   to OpenVMS users, and a favorite way for various folks to get themselves dI   tossed off of systems, I have a copy stashed away.  And no, I will not rE   provide nor post the tool here, for what should be obvious reasons. H   And yes, folks using this tool can generally be (easily) tracked down.J   (Mere possession of the tool was grounds for retribution at some sites.)  C   If you want to send email, please use the available API for MAIL.D  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Wed, 31 May 2000 08:32:26 -0700r/ From: Terry Marosites <TMarosites@unitedad.com>a" Subject: RE: looking for blast.comM Message-ID: <1137A4A23A51D311B2D600105A1D5213019AEE53@seantexch.unitedad.com>l  
 Hello All,H    Sorry for the confusion, this DCL procedure called blast.com used theK phone utility transfer utility. It broadcast a message to a user. I want tolH remove oper privileges from developers. The current compile&link utilityK that they use does a reply with the status. I want to replace this with the G blast procedure.  And yes Hoff this too can cause problems in the wrong J hands that is way I asked for an email copy. The procedure is a great toolH but like many things can be misused. 99% of my users are captive and the would not have access to it.    
 Thanks all Terry    -----Original Message-----J From: hoffman@xdelta.zko.dec.nospam [mailto:hoffman@xdelta.zko.dec.nospam]% Sent: Wednesday, May 31, 2000 5:38 AMi To: Info-VAX@Mvb.Saic.Comt" Subject: Re: looking for blast.com    
 In articleH <1137A4A23A51D311B2D600105A1D5213019AEE50@seantexch.unitedad.com>, Terry+ Marosites <TMarosites@unitedad.com> writes:d  ? :Does anyone have a copy of blast.com that they could email me. B :It was posted here back in 1994-5 and I can't find it in the FAQs  F   If the referenced blast tool is the tool that was used to blast MAILJ   to OpenVMS users, and a favorite way for various folks to get themselvesH   tossed off of systems, I have a copy stashed away.  And no, I will notE   provide nor post the tool here, for what should be obvious reasons. H   And yes, folks using this tool can generally be (easily) tracked down.J   (Mere possession of the tool was grounds for retribution at some sites.)  C   If you want to send email, please use the available API for MAIL.'  2  --------------------------- pure personal opinion --------------------------- L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com    5 *****************************************************     5 *****************************************************k4 Any views or opinions are solely those of the author) and do not necessarily represent those ofd United News& Media. 5 *****************************************************04 The information transmitted is intended only for the1 person or entity to which it is addressed and may 3 contain confidential and/or privileged material. If 3 you are not the intended recipient of this message,2. please do not read, copy, use or disclose this3 communication and notify the sender immediately. It*0 should be noted that any review, retransmission,2 dissemination or other use of, or taking action in- reliance upon, this information by persons or - entities other than the intended recipient is  prohibited.I5 *****************************************************  **   ------------------------------  ! Date: Tue, 30 May 00 21:02:05 GMTe From: heimann@ecs.umass.edue Subject: Re: MicroVMS 4.4 , Message-ID: <8h29tj$5bh$1@odo.ecs.umass.edu>  6 In Article <02bb01bfc7f0$eadc2e40$020a0a0a@xile.realm>+ "John E. Malmberg" <wb8tyw@qsl.net> writes:u8 >Robert Deininger <rdeininger@mindspring.company> wrote: >*H >> How does one clean a TK70 drive?  First step seems to be removing theJ >> dust-bunnies with tongs.  Then what?  The head doesn't seem accessible., >> Would a DLT cleaning cart work in a TK70? > L >If you push hard enough it will go in.  The service people will not be veryM >amused but after they pry it out, the TK70 drive appears to still be usable.: >BI >There is a specific cleaning kit for TK50/TK70 drives.  It has a plasticfM >guide and a number of cleaning strips with some solution.  I do not have theh5 >part numbers, but it should not be too hard to find.   F I ended up cleaning TK50 heads by wetting down lint free cleaner clothE with head cleaner and then pulling it through the head gap.  That wascG enough to get the drive to write without parity errors.  The top of the$D drive has to come off to access that area.  Never could find out theG part number for TK50/70 cleaning cartridges, Field Service seemed to beiB the only ones who could get them when the drives were on contract.   Joe Heimanns   heimann@ecs.umass.edut   ------------------------------   Date: 31 May 2000 03:01 CSTn' From: carl@gerg.tamu.edu (Carl Perkins)g Subject: Re: MicroVMS 4.4d- Message-ID: <31MAY200003012547@gerg.tamu.edu>l  1 David B Sneddon <dbsneddon@bigpond.com> writes...h6 }At 10:33 AM 27-05-2000 -0500, John E. Malmberg wrote:9 }>Robert Deininger <rdeininger@mindspring.company> wrote:  }>I }>> How does one clean a TK70 drive?  First step seems to be removing the K }>> dust-bunnies with tongs.  Then what?  The head doesn't seem accessible. - }>> Would a DLT cleaning cart work in a TK70?w }>M }>If you push hard enough it will go in.  The service people will not be veryaN }>amused but after they pry it out, the TK70 drive appears to still be usable. }>J }>There is a specific cleaning kit for TK50/TK70 drives.  It has a plasticN }>guide and a number of cleaning strips with some solution.  I do not have the6 }>part numbers, but it should not be too hard to find. }> }>-Johnr }>wb8tyw@qsl.network } ! }Just happen to have one handy...  }  }        22-00436-01 } : }Contains a "positioning cartridge" and 10 bottles/strips. }Sutiable for TK50/TK70/TZ30 } 	 }Regards,t }Dave.  F The other style part number is TKXX-HC for the full kit (10 cleanings)C and TKXXR-HC for a refil kit (20 cleanings, but doesn't include theI positioning cartridge).g  	 --- Carl M   ------------------------------    Date: 31 May 2000 11:10:35 -04004 From: "Robert Deininger" <rdeininger@mindspring.com> Subject: Re: MicroVMS 4.4s* Message-ID: <B55AA3AD-40899@165.247.43.92>  : On Tue, May 30, 2000 5:02 PM, heimann@ecs.umass.edu wrote:7 >In Article <02bb01bfc7f0$eadc2e40$020a0a0a@xile.realm>o, >"John E. Malmberg" <wb8tyw@qsl.net> writes:9 >>Robert Deininger <rdeininger@mindspring.company> wrote:a >>I >>> How does one clean a TK70 drive?  First step seems to be removing therK >>> dust-bunnies with tongs.  Then what?  The head doesn't seem accessible. - >>> Would a DLT cleaning cart work in a TK70?  >>H >>If you push hard enough it will go in.  The service people will not be veryF >>amused but after they pry it out, the TK70 drive appears to still be usable.  >>J >>There is a specific cleaning kit for TK50/TK70 drives.  It has a plasticJ >>guide and a number of cleaning strips with some solution.  I do not have the96 >>part numbers, but it should not be too hard to find. >0  I Thanks to everyone for the info.  I ended up taking the cover off a spareaI TK70 and cleaning the whole tape path with q-tips and alcohol. As soon asiF I have a spare moment, I'll swap the clean one into the running system) and see how the old tapes are holding up.a   ---------------------------E Robert Deininger rdeininger@mindspring.com:   ------------------------------  % Date: Wed, 31 May 2000 03:11:29 -0400 * From: David A Froble <davef@tsoft-inc.com>& Subject: Re: Migrating from VMS to AIX- Message-ID: <3934BB21.EFF362C4@tsoft-inc.com>    maztang@my-deja.com wrote: > H > We are looking into converting our one remaining VMS system to AIX forF > ease of support and consistency amongst our mid-range servers.  I'veG > found Sector7's software for running RMS and DCL on unix systems, andSI > Boston Business Computing's VCL and EDT+.  Are there any other products G > out there along these lines?  RMS and DCL are what we really need, totG > make the transition as smooth as possible.  We'd like to have as many B > choices as possible to test before we make a commitment with one4 > vendor.  Any help you all can give would be great. > 	 > Thanks.  >  > Jayx > ( > Sent via Deja.com http://www.deja.com/ > Before you buy.l  P Any help?  Ok.  If you really want ease of support and consistancy, convert your AIX systems to VMS.   . An answer you'd have to expect on comp.os.vms.   Dave   -- ,4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596; 170 Grimplin Road               E-Mail: davef@tsoft-inc.coms Vanderbilt, PA  15486e   ------------------------------  % Date: Wed, 31 May 2000 09:21:00 -0400V! From: JGraf <sales@asoft-dev.com> & Subject: Re: Migrating from VMS to AIX) Message-ID: <393511BC.5910@asoft-dev.com>d   Jay,  G In addition to BBC's EDT+ there is nu/TPU from a/Soft Development Inc.  ; If you are interested in using the EVE editor with full TPU D functionality on AIX you can visit our web site www.asoft-dev.com or call us at 603-432-3388.  
 Best regards,   
 James Graf sales@asoft-dev.com  603-432-3388   maztang@my-deja.com wrote: > H > We are looking into converting our one remaining VMS system to AIX forF > ease of support and consistency amongst our mid-range servers.  I'veG > found Sector7's software for running RMS and DCL on unix systems, and I > Boston Business Computing's VCL and EDT+.  Are there any other products G > out there along these lines?  RMS and DCL are what we really need, to G > make the transition as smooth as possible.  We'd like to have as manyrB > choices as possible to test before we make a commitment with one4 > vendor.  Any help you all can give would be great. > 	 > Thanks.s >  > Jayt > ( > Sent via Deja.com http://www.deja.com/ > Before you buy..   ------------------------------  % Date: Wed, 31 May 2000 08:23:50 -0400e[ From: jamese@beast.dtsw.army.mil (Ed James, TCS Inc, 410-295-1919, ed.james@telecomsys.com)n Subject: Re: Motif - Version?n0 Message-ID: <00053108235090@beast.dtsw.army.mil>  5 martin@RADIOGAGA.HARZ.DE (Martin Vorlaender) wrote in 2 <392eb88f.524144494f47414741@radiogaga.harz.de> on  Fri, 26 May 2000 19:46:55 +0200:  & > Philipp Gasser (ga@adasys.ch) wrote:. > : - I ve got an OpenVMS - Installation (6.2)D > : Now, Im interested in the Motif - Version, but where/and how can  > : I find out this information. >  > $ @SYS$UPDATE:DECW$VERSIONSt   This sets symbols:   $ @SYS$UPDATE:DECW$VERSIONSo $ sho symbol decw$*version*w& DECW$APPS_VERSION == "DW V1.2-4960312"& DECW$PROG_VERSION == "DW V1.2-4960312"' DECW$SERVER_VERSION == "DW V7.1-961126"u) DECW$TOOLKIT_VERSION == "DW V1.2-4960313"c! DECW$VERSION == "DW V1.2-4960312"'& DECW$XLIB_VERSION == "DW V1.2-4960312"& DECW$XPORT_VERSION == "DW T6.2-961126"  . Add a non-null P1 argument for printed output:  ' $ @SYS$UPDATE:DECW$VERSIONS non-null-p1 % DECwindows ident is			DW V1.2-4960312t* DECwindows server ident is		DW V7.1-961126- DECwindows transport ident is		DW T6.2-961126j) DECwindows xlib ident is		DW V1.2-4960312a1 DECwindows motif toolkit ident is	DW V1.2-49603130) DECwindows apps ident is		DW V1.2-4960312e0 DECwindows programming ident is		DW V1.2-4960312  : Ed James                           ed.james@telecomsys.com5 TeleCommunications Systems, Inc.   voice 410-295-1919c5 275 West Street, Suite 400         fax   410-280-1094i Annapolis, MD 21401-1740   ------------------------------  # Date: Wed, 31 May 2000 11:21:23 GMTl' From: Colin Blake <colin@theblakes.com>i Subject: Re: MOZILLA M16 ?- Message-ID: <3934F606.FC204858@theblakes.com>2   Peter LANGSTOEGER wrote:  5 > I know that M16 and M17 are not out, yet. But why ?e  W M16 is meant to be the "feature complete" milestone. The dates were pushed out to allowoX time for everything to come in. The tree closed last week and is currently going through7 "stabilization". Shouldn't be more than a few days now.n  I > And the milestone list did get updated the last weeks more than once...   T If the milestone list were up to date, M16 would have shipped over two weeks ago :-)   ------------------------------  % Date: Wed, 31 May 2000 04:50:09 -0700 5 From: Richard  <maher_rjNOmaSPAM@hotmail.com.invalid>r, Subject: Re: none urgent cobol exit question9 Message-ID: <0295861e.4a4512c1@usw-ex0108-061.remarq.com>a   Hi,a  ; I could be completely wrong but something in the back of myd6 mind says the standard may have been reversed. Sorry I: don't have recent versions but I'd suggest doing a $search1 through the release notes for DEC cobol at least.x  7 As mentioned earlier you probably want to do a lib$stopl9 with the status that made you want to $exit 4 but as longr4 as you note that the severity will be forced and any condition handlers called.  ; On that note, I believe on Alpha DEC cobol inserts a static08 cond handler at compile time and traps any lib$establish; calls and gets the static handler to call the quasi dynamicu6 handlers. Has anyone have any advice/problems on this.  2 I've got a cond handler that correctly handles the; lib$_eomwarn status so that lib$find_image_symbol does what ; it should and it also check's for ss$_debug and a few othere0 things. I need to port this to Alpha. Has anyone; experienced any problems with DEC COBOL with cond handlers?o  2 I know about the format change sigargs? (or was it: mechargs?) but thankfully that doesn't affect me too much.   Regards Richard maher.     * Sent from AltaVista http://www.altavista.com Where you can also find related Web Pages, Images, Audios, Videos, News, and Shopping.  Smart is Beautifulc   ------------------------------  % Date: Wed, 31 May 2000 09:10:43 +0200o= From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com> 3 Subject: Re: OpenVMS vs Tru64 Pathworks performanceg) Message-ID: <3934BAF3.CB058CAC@gtech.com>r   David Mathog wrote: k > In article <3931229D.2349BC38@gtech.com>, Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com> writes:nG > >  - VMS systems usually do much less caching than Unix & Win systemswF > >    and it costs performance (but you are happy for it if the power > >    goes !) > M > This keeps coming up and I'm pretty sure that it's WRONG for a typical fileuM > serving application. Imagine Jane user works on some Microsoft document and)L > hits "save" every 10 minutes.  The time to transfer the file up to the VMSH > machine is 1 minute, and it's 10 seconds to the other machine (Unix orH > WNT).  If the power fails during the transfer interval the network andK > remote PC will both fail and the file will be corrupted on either OS, andeK > the slower one has a 6X larger window of opportunity for such failure, sog? > on average, would end up corrupting files 6X more frequently.c   ????  " I do not understand that analysis.   Using your example:    - save every 10 minute5   - 1 minute with write-through caching (the VMS way) 0   - 10 seconds with write-back caching (NT/Unix)  9 And let us assume that the write-back caching is lazy, so.8 that it takes 3 minutes to actually get it written back.   Then the analysis is simple.   Response time seen by user:    VMS     : 1 minut-   NT/Unix : 10 seconds  5 Risk probabilities in case of a server powre-failure:f  8                                       VMS        NT/Unix  4 no problem because the                90%        70% data is on the platesp  5 the user sees the problem             10%        1.6%e  and can save to another location  6 the user does not see the problem     0%         28.4% and looses the documente   You see the point !-   Arne   ------------------------------  % Date: Wed, 31 May 2000 03:20:54 -0400z* From: David A Froble <davef@tsoft-inc.com>3 Subject: Re: OpenVMS vs Tru64 Pathworks performancen- Message-ID: <3934BD56.A3B43B49@tsoft-inc.com>A  $ Mark Iline - Info-VAX account wrote: > K > From:   MX%"rpjung@mb.sympatico.ca"  "Randy Jung" 28-MAY-2000 03:20:17.60e > F > Cheers for the comparison, but we really need to be lookig at recentE > versions. I understand that recent versions of ASDU (Tru64 PW) havesK > significantly increased performance over earlier versions (several 100%).a > N > > As someone mentioned, the best performing server for a Windows environment* > > will probably be a Winodows NT server. > G > This isn't an accurate comparison, but installing Office97 off a filee > service gives something like:r > ! > Elapsed time    Server platform 0 > 5 minutes       NTAS 4 (450 MHz Proliant 1600)  > 2 minutes       ASDU (PW500AU)0 > >10 minutes     PW 6.0 dual CPU DS20, VMS7.1-2 > ( > All servers on 100Mbit switched ports. >  > Mark  P Having been through the file caching arguments, I've got to observe that there'sK something really screwed up in Pathworks.  VMS disk activity isn't all that L slow, and to blame it is ignoring the problems in Pathworks.  I have no ideaP what the real problems are.  What I do know is that while in-memory file cachingL isn't currently the best on VMS, the disks used on VMS systems are no slower! than those used on other systems.e  O As I've stated before, I gave up on Pathworks some years ago.  Mostly because IoM personally feel that serving files to windoz systems is a waste of a good VMS O system.  Bigotry aside, it is a valid application, and as the comparisons show,rE Pathworks just isn't getting the job done.  Sign of a bad applicationi implementation.    Dave   -- T4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596; 170 Grimplin Road               E-Mail: davef@tsoft-inc.comi Vanderbilt, PA  15486    ------------------------------   Date: 31 May 2000 14:49:34 GMT2 From: mathog@seqaxp.bio.caltech.edu (David Mathog)3 Subject: Re: OpenVMS vs Tru64 Pathworks performance , Message-ID: <8h38pu$2gl@gap.cco.caltech.edu>  Z In article <3934BD56.A3B43B49@tsoft-inc.com>, David A Froble <davef@tsoft-inc.com> writes: > Q >Having been through the file caching arguments, I've got to observe that there'skL >something really screwed up in Pathworks.  VMS disk activity isn't all thatM >slow, and to blame it is ignoring the problems in Pathworks.  I have no ideaf >what the real problems are.  0 The most likely cause of write slowdown is this:   1 client sends packett 2 server receives packetT 3 server writes it to disk, waiting for the write to complete (fprintf() or write())= 4 server signals client that it is ok to send the next packeto  H If this code came over verbatim from Unix it will be really slow on VMS.I That's because step 3 is very fast on Unix (it goes to file cache, unlesspJ they've gone to great lengths to do otherwise) and so it completes nearly L instantaneously.  On VMS, on the other hand, unless the RMS parameters have K been set on the application to allow buffering it's going to take at least *K 10 milliseconds, possibly more to return.  Worse, it will tend to cause theoG file to extend by tiny increments, which is the slowest possible way to*N write a file.  At the very least step 3 on VMS should be rewritten to use QIOsM (without waiting for completion) to write to a file with buffering turned on.f  G Similarly, for read performance, if the application doesn't use a high tG multiblockcount (a no brainer here, but...) it will have at least a 2X nK poorer read performance compared to a real disk read on other OS's.  If theeH file is being read from file cache on Unix that will be much faster than( any disk read could possibly be on VMS.   I So, it could well be that virtually all of the performance penalty we see*B with Pathworks on OpenVMS is a direct result of running code whichK implicitly assumes file caching for its efficiency being run on an OS whichd doesn't provide it.   G Does anybody out there have Perfect Cache from Raxco running on a disk 1G served by Advanced Server?  If this theory is correct it should perform ( very similarly to what's seen on Tru64.   K We can't know what Advanced Server does, but Samba is in the public domain.eN Can one of the Samba for VMS developers comment on what this version of Samba ) does for write optimization, if anything?    Regards,   David Mathog mathog@seqaxp.bio.caltech.edug? Manager, sequence analysis facility, biology division, Caltech yJ **************************************************************************J *                                RIP VMS                                 *J **************************************************************************   ------------------------------  # Date: Wed, 31 May 2000 17:13:45 GMTh2 From: malmberg@eisner.decus.org (John E. Malmberg)3 Subject: Re: OpenVMS vs Tru64 Pathworks performance ' Message-ID: <FvFp6y.92q@news.decus.org>i  , In article <8h38pu$2gl@gap.cco.caltech.edu>,: mathog@seqaxp.bio.caltech.education (David Mathog) writes: >eL >We can't know what Advanced Server does, but Samba is in the public domain.O >Can one of the Samba for VMS developers comment on what this version of Samba  * >does for write optimization, if anything? >-  J SAMBA on UNIX if built with mmap() support will use that for accessing theE file to be transfered.  Unfortunately that option can only be used on.L STREAM-LF files for OpenVMS. None of the record reformulation is done, as itI reads the file in raw mode.  Standard VMS text formats will not transfer.m    M The released versions of SAMBA for VMS that I am aware of do not do any writee* optimization.  They do do some read ahead.    H To implment oplocks in SAMBA 2.0.6 for VMS, I needed to open the file inA "ctx=rec" mode.  RMS locks require locking on an existing record.o  M This causes some "interesting" side effects on how certain types of RMS filesh are written to.a  M As a result, I had to implement a read/write buffer in order to implement thee" ability to write() partial blocks.  E Setting the size of this buffer to 32K really speeded things up, whennC transfering an 8 Megabyte fixed 512 byte block file back and forth.wA [New optional feature - specify file structure by file extension]2  P The fastest transfer times I got were when a bug stopped all physical writes to  disk from occuring :-)    M I implemented these routines as a shared image instead of patching SAMBA.  It ? should be usuable for porting other UNIX/LINUX programs to VMS.'  J I am currently interactively running a version of SAMBA 2.0.6 SMBD that is; basically feature and bug compatable with the UNIX version.   B The two major issues besides packaging it up for distribution are:  C 1. No ODS-5 support implemented, or case preservation of filenames.M  L 2. SAMBA opens all files that it has write access to as read/write even whenL the client requests only read access.  This has to do with the way that UNIXN file locking works.  To make this friendlier to the VMS environment, I have toJ put in patches in both the file opening code as is in the 2.0.3 release, I$ also have to patch the locking code.     -John  wb8ytw@qsl.network   ------------------------------  % Date: Wed, 31 May 2000 15:03:27 +0000 - From: ezzaoudi med <m.ezzaoudi@digitem.co.ma>e Subject: PATCHs - Message-ID: <393529BF.E5EF18BA@digitem.co.ma>>  & Where can I find patches for OpenVMS ?	 Thank you.   ------------------------------  % Date: Wed, 31 May 2000 17:16:31 +0100i4 From: Adrian Birkett <abirkett.@unnecessary.csc.com> Subject: Re: PATCHsf3 Message-ID: <39353ADE.6C4BADC8@unnecessary.csc.com>    Try;  2  http://www.service.digital.com/patches/index.html   Regards,   Adep   ------------------------------  % Date: Wed, 31 May 2000 19:03:41 +0200i( From: "Bruin, J.M. de" <Bruin@WT.TNO.NL>6 Subject: Please ignore, just testing rules of exchangeA Message-ID: <D680D25E5D2BD411AC060008C7F37BC247DB@wt15.wt.tno.nl>-  K ---------------------------------------------------------------------------aH Mark de Bruin                                   Voice : +31 15 269 69 05H TNO Crash Safety Centre                         Fax   : +31 15 257 21 04K Laboratories                                    GSM   : +31 653 44 21 45    G Innovations, Information & Communication        E-mail: bruin@wt.tno.nlt7 Room: GBS 1.1                                   URL   :n http://www.automotive.tno.nl0 P.O. Box 6033                                   
 2600 JA Delftn The NetherlandsM   ------------------------------  # Date: Wed, 31 May 2000 17:17:32 GMTs From: itjck01@my-deja.comv8 Subject: POS/credit card verification with OpenVMS Alpha) Message-ID: <8h3hf0$gfb$1@nnrp1.deja.com>o  7 Does anyone know what credit card verification software F packages/services are being used on OpenVMS Alpha?  I would appreciateE hearing the good, bad, and ugly of what folks are using in this area.   C Our desire is interactive credit card verification (on the order of.@ seconds) that has some sort of API that we can interface to.  WeD believe the following are available for OpenVMS in the way of credit# card verfication software/services:e   PAYLINX. ICVERIFY
 PAYMENTECH  6 Anyone know of any others or have comment on the above software/services?   :) jck --$ Free personal opinion is what I post    & Sent via Deja.com http://www.deja.com/ Before you buy.t   ------------------------------    Date: 31 May 2000 11:23:54 +0200G From: Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de>i( Subject: Re: Problem with resource locksH Message-ID: <y43dmzvzrp.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>  . "Adrian Lumsden" <A.Lumsden@xdt.co.uk> writes:  B > This lets MP's EX lock complete to EX. SPs then enqueue a NL->CRI > conversion with completion AST. If MP subsequently dies, the completionsB > AST fires and SPs know that MP has gone away and can wait for it
 > to restart.g  K Make sure this conversion has the flag telling the DLM that this lock isn't F blocking. Otherwise, you will be triggering useless deadlock searches.  G > Moral?? Always create your locks as NL first and then manipulate theml > with conversions.   L Yes, I think this is the way it is supposed to be. See the other reply aboutN EXPEDIATE to make the initial grant happen - in fact, I would consider this toL be a (small) design bug: obtaining a new NL mode lock should always succeed;' that certainly is my naive expectation.   M HH: is there a "DLM cookbook", possibly internal to the VMS group? That would5G certainly be useful, as I can't see that the documentation for the lock-? services can handle all the different application scenarios and./ considerations. An entry for the FAQ, I'm sure.4   	Jan   ------------------------------  % Date: Wed, 31 May 2000 17:24:43 +0200a< From: Georges SZAFRANSKI <szafranski@lutece.evt.cpqcorp.net>( Subject: Re: Problem with resource locks5 Message-ID: <39354ADB.99AD060@lutece.evt.cpqcorp.net>t   > O > HH: is there a "DLM cookbook", possibly internal to the VMS group? That wouldUI > certainly be useful, as I can't see that the documentation for the lockWA > services can handle all the different application scenarios and_1 > considerations. An entry for the FAQ, I'm sure.= > 
 >         Janc  ; Why don't you start with chap 6 of VAXcluster principles ? V Author Roy G. Davies DP ISBN 1-55558-112-99 PH ISBN 0-13-064338-6l   georges szafranski   ------------------------------    Date: 31 May 2000 18:32:59 +0200G From: Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de>w( Subject: Re: Problem with resource locksH Message-ID: <y4wvkasmro.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>  > Georges SZAFRANSKI <szafranski@lutece.evt.cpqcorp.net> writes:  = > Why don't you start with chap 6 of VAXcluster principles ?   > Author Roy G. Davies > DP ISBN 1-55558-112-9e > PH ISBN 0-13-064338-6   E Just by the title, it must be massively out of date. How long has the2L EXPEDIATE flag existed? Practically every major (and some minor) VMS releaseG has modified the logic behind lock tree mastering and remastering. Nah,  an update is surely required.s   	Jan   ------------------------------  # Date: Wed, 31 May 2000 11:32:54 GMTw From: alois@intercom.es  Subject: Pruebas7 Message-ID: <GL6Z4.5501$jq6.19439@telenews.teleline.es>.   Pruebasw   ------------------------------   Date: 31 May 2000 08:07:14 GMT3 From: gartmann@immunbio.mpg.de (Christoph Gartmann)i0 Subject: Re: Remote Print From Vax/VMS to AS/4000 Message-ID: <8h2h7i$k4n$1@n.ruf.uni-freiburg.de>  P In article <39347960.9ACCE846@you.com>, "Walter G. Bennett" <me@you.com> writes:D >I am trying to send reports from a Vax computer to an AS/400 output >queue.,C >I was able to send a report to the printer queue but was unable tolH >display or print the report.  The error I received on the AS/400 statedE >that the file was ASCII meant for a PC Printer.  The report was sentmG >using a DCL PRINT command that contained the system name and the queuey >name. >rC >Is there another /PARAMETER that I should include to translate the$ >report to the proper format?e  H You should be a bit more specific. Which software is involved (Operating# System, TCP/IP package, DCPS?,...)?   K If I assume that you want to print standard ASCII text you should know thataM the AS400 uses IBM's EBCDIC character encoding scheme whereas VMS uses ASCII.l- Thus, you'll need some sort of a conversion. e   Regards,    Christoph Gartmann   H -----------------------------------------------------------------------+H | Max-Planck-Institut fuer      Phone   : +49-761-5108-464   Fax: -452 |H | Immunbiologie                                                        |H | Postfach 1169                 Internet: gartmann@immunbio.mpg.de     |H | D-79011  Freiburg, FRG                                               |H +------------ http://www.immunbio.mpg.de/english/menue.html -----------+   ------------------------------  % Date: Wed, 31 May 2000 06:57:07 -0400a2 From: "Richard B. Gilbert" <DRAGON@COMPUSERVE.COM>0 Subject: Re: Remote Print From Vax/VMS to AS/4007 Message-ID: <200005310657_MC2-A6F9-853B@compuserve.com>S  J         If the AS/400 printer uses the EBCDIC character code, you are out=  E of luck!   You would have to translate your file from ASCII to EBCDIChJ before the printer could do anything useful with it.  It sounds as if tha= tB is exactly the problem!     + Message text written by "Walter G. Bennett"4D >I am trying to send reports from a Vax computer to an AS/400 output queue.B I was able to send a report to the printer queue but was unable toG display or print the report.  The error I received on the AS/400 statedtD that the file was ASCII meant for a PC Printer.  The report was sentF using a DCL PRINT command that contained the system name and the queue name.r  B Is there another /PARAMETER that I should include to translate the report to the proper format?<e   ------------------------------  + Date: Wed, 31 May 2000 12:49:32 +0100 (MET)U7 From: "Carl Gunnar Linden, MSL Sweden." <system@msi.se>n Subject: SBS PCI-VME adaptor) Message-ID: <009EAE87.2127F16F.77@msi.se>o  L  I would like to get in touch with anybody who is using a SBS PCI-VME BridgeN Adaptor (Model 617) fitted with the Dual Port Ram option . The thing I want toI know is if the DWPVC PCI-VME Adapter Driver V2.0 can be used with OpenVMSp 7.2-1 . H In http://www.openvms.compaq.com/wizard/wiz_3513.html someone complainedK about system crashes using OpenVMS 7.2 . If the author of that message seest this please contact me.s   Carl Gunnar Linden Manne Siegbahn Laboratorye at Stockholm Universityn
 Sweden       s E-mail: linden@msi.sem   ------------------------------  % Date: Wed, 31 May 2000 13:39:03 +0000a- From: ezzaoudi med <m.ezzaoudi@digitem.co.ma>  Subject: Telnet and License - Message-ID: <393515F7.75AE8AEA@digitem.co.ma>e   Hi, ; I have probleme with telnet in Alpha OpenVMS configuration.rH When 200 users are connected with Telnet , no new connexion is possible.  . But I can do connection by Decnet ( set host).7 with UCX>SHOW SERVICE TELNET /FULL   I have a limit=320o= I have a UCX license with UNIT=1050 .  Is it the probleme ???3 An Alpha VMS license = 15  An Alpha VMS users license = 75-   Thank you .c   ------------------------------  % Date: Wed, 31 May 2000 16:07:13 +0100B- From: Tim Llewellyn <tim.llewellyn@bbc.co.uk>o Subject: Re: Telnet and Licenseu) Message-ID: <39352AA1.A54C5070@bbc.co.uk>0  A Did you tune your VMS box for that number of  telnet connections?o  I There are some tuning formulae in Chapter 1 of the UCX Installation GuideTB (section 1.2.7 in the version on the VMS 7.2 docs CD). Each telnet
 connection6 uses up a socket (maybe more than one, I am not sure).  < Maybe if you post the output from UCX SHOW COMM/MEM we might/ be able to help further diagnose your problems.e  L If you can log in by DECNET but not IP I doubt it is a VMS licencsing issue,  3 and I'm not aware of any user-limited UCX licences.    HTHT   ezzaoudi med wrote:1   > Hi, = > I have probleme with telnet in Alpha OpenVMS configuration. J > When 200 users are connected with Telnet , no new connexion is possible. >i0 > But I can do connection by Decnet ( set host).9 > with UCX>SHOW SERVICE TELNET /FULL   I have a limit=320P? > I have a UCX license with UNIT=1050 .  Is it the probleme ???i > An Alpha VMS license = 15 ! > An Alpha VMS users license = 75e >a
 > Thank you .    --6 Tim Llewellyn, OpenVMS Infrastructure, Remarcs Project0 MedAS at the BBC, Whiteladies Road, Bristol, UK.A Email tim.llewellyn@bbc.co.uk. Home tim.llewellyn@cableinet.co.ukt  A I speak for myself only and my views in no way represent those ofo MedAS or the BBC.h   ------------------------------   Date: 31 May 2000 15:26:15 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) Subject: Re: Telnet and License 6 Message-ID: <8h3aun$82s$1@mailint03.im.hou.compaq.com>  ] In article <393515F7.75AE8AEA@digitem.co.ma>, ezzaoudi med <m.ezzaoudi@digitem.co.ma> writes:e< :I have probleme with telnet in Alpha OpenVMS configuration.  #   The usual set of questions apply:-        What TCP/IP version and ECO?  !     What OpenVMS Alpha version?  e  8     The full text of the error(s) messages seen, if any?  I :When 200 users are connected with Telnet , no new connexion is possible.s  G   This is probably not a TCP/IP licensing issue, though other licenses sE   (eg: OpenVMS user licensing) could *potentially* be involved.  The  F   text of the error message can help with this determination, as this F   could just as easily be a case of insufficient process slots or some   other limitation.t   :I have a limit=320t  C   Did you (explicitly or implicitly) restart TCP/IP Services since .   setting the limit to 320?w  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Wed, 31 May 2000 17:27:12 +0200 5 From: Oswald Knoppers <Oswald.Knoppers@whitehouse.nl>w Subject: Re: Telnet and Licenses- Message-ID: <39352F50.F43B5CD4@whitehouse.nl>s   ezzaoudi med wrote:a >  > Hi,o= > I have probleme with telnet in Alpha OpenVMS configuration.nJ > When 200 users are connected with Telnet , no new connexion is possible. > 0 > But I can do connection by Decnet ( set host).9 > with UCX>SHOW SERVICE TELNET /FULL   I have a limit=320w? > I have a UCX license with UNIT=1050 .  Is it the probleme ???i > An Alpha VMS license = 15*! > An Alpha VMS users license = 75s  D My guess would be the total service limit set to 200. You should seeB this in a 'show comm' command. This limit can be increased without restarting UCX.c   Regards,   Oswald   ------------------------------  % Date: Wed, 31 May 2000 18:49:29 +0200a$ From: Jacek Tobiasz <jtb@atm.com.pl> Subject: Re: Telnet and Licensed? Message-ID: <00May31.184932met_dst.14344@gateway.hq.atm.com.pl>n   Oswald Knoppers wrote: >  > ezzaoudi med wrote:  > >b > > Hi,V? > > I have probleme with telnet in Alpha OpenVMS configuration.eL > > When 200 users are connected with Telnet , no new connexion is possible.   Any OPCOM messaage ?   > > 2 > > But I can do connection by Decnet ( set host).; > > with UCX>SHOW SERVICE TELNET /FULL   I have a limit=320 A > > I have a UCX license with UNIT=1050 .  Is it the probleme ???f > > An Alpha VMS license = 15l# > > An Alpha VMS users license = 75s > F > My guess would be the total service limit set to 200. You should seeD > this in a 'show comm' command. This limit can be increased without > restarting UCX.o  % Yes, you mean Device_sockets ? Right.   > Btw. I was told a story about some limit on telnet connections> with UCX (4.1/4.2 ?) It was about 200. Do not remeber details.! (there was no way to increase it)*   regards* Jacek*   ------------------------------  % Date: Wed, 31 May 2000 10:36:35 -0400 " From: Dan Sugalski <dan@sidhe.org>$ Subject: Unneeed RMS overhead with C8 Message-ID: <4.3.1.0.20000531103238.00e495c0@24.8.96.48>  1 At 11:47 AM 5/31/00 +0200, Jan Vorbrueggen wrote:aJ >It seems to me that the crucial point is "Tru64 with its more lightweightM >filesystem": that implies, to me, that using RMS naively in that applicationhI >is a problem, especially if you're programming via, say, the C RTL. In aM1 >sense, you're buying more than you've asked for.r  G This is definitely true, and something that the C RTL team ought to be  J working on, honestly. The RTL should keep one cluster in flight in or out I for files opened naively (i.e. with a plain open or fopen, with no extra sL doodads to speak of) and I bet we'd see a nice performance boost with plain  ported software.   					Dan  I --------------------------------------"it's like this"------------------- 2 Dan Sugalski                          even samurai? dan@sidhe.org                         have teddy bears and evenm;                                       teddy bears get drunke   ------------------------------   Date: 31 May 2000 15:37:33 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)( Subject: Re: Unneeed RMS overhead with C6 Message-ID: <8h3bjt$82s$2@mailint03.im.hou.compaq.com>  ] In article <4.3.1.0.20000531103238.00e495c0@24.8.96.48>, Dan Sugalski <dan@sidhe.org> writes:n2 :At 11:47 AM 5/31/00 +0200, Jan Vorbrueggen wrote:K :>It seems to me that the crucial point is "Tru64 with its more lightweightwN :>filesystem": that implies, to me, that using RMS naively in that applicationJ :>is a problem, especially if you're programming via, say, the C RTL. In a2 :>sense, you're buying more than you've asked for. :iH :This is definitely true, and something that the C RTL team ought to be K :working on, honestly. The RTL should keep one cluster in flight in or out nJ :for files opened naively (i.e. with a plain open or fopen, with no extra M :doodads to speak of) and I bet we'd see a nice performance boost with plain t :ported software.   G   This arguably isn't C, nor best fixed in the C RTL.  The default RMS .H   defaults suck, bluntly.  The RMS defaults were determined a long time B   ago in a cluster far, far away, and many of the relevent system F   constraints (eg: available physical memory, etc) have changed.  The    RMS defaults have not.  I   There have been various discussions around various (potential) changes hG   to the RMS defaults, with a key concern being compatibility -- we do  F   not want an existing application to see decreased performance, or toF   see weird application failure(s) due to changes to the RMS defaults.  G   More than a few applications have seen dramatic improvements with the2G   addition of some simple RMS extensions on the C (f)open call, either hF   requesting better buffering or (when appropriate) requesting SQO or E   similar RMS performance options.  But the default values chosen by j#   RMS itself need a careful look...D  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Wed, 31 May 2000 13:03:33 -0400u" From: Dan Sugalski <dan@sidhe.org>( Subject: Re: Unneeed RMS overhead with C8 Message-ID: <4.3.1.0.20000531125418.01e89630@24.8.96.48>  . At 03:37 PM 5/31/00 +0000, Hoff Hoffman wrote:  G >In article <4.3.1.0.20000531103238.00e495c0@24.8.96.48>, Dan Sugalski   ><dan@sidhe.org> writes:3 >:At 11:47 AM 5/31/00 +0200, Jan Vorbrueggen wrote:7L >:>It seems to me that the crucial point is "Tru64 with its more lightweightO >:>filesystem": that implies, to me, that using RMS naively in that application K >:>is a problem, especially if you're programming via, say, the C RTL. In av3 >:>sense, you're buying more than you've asked for.  >:H >:This is definitely true, and something that the C RTL team ought to beK >:working on, honestly. The RTL should keep one cluster in flight in or outcJ >:for files opened naively (i.e. with a plain open or fopen, with no extraM >:doodads to speak of) and I bet we'd see a nice performance boost with plains >:ported software. >dH >   This arguably isn't C, nor best fixed in the C RTL.  The default RMSI >   defaults suck, bluntly.  The RMS defaults were determined a long timerC >   ago in a cluster far, far away, and many of the relevent systemtG >   constraints (eg: available physical memory, etc) have changed.  Then >   RMS defaults have not.  F Oh, without a doubt. I was looking at things from a C RTL perspective  mainly because:o  K 1) C's default I/O routines are less well integrated into RMS than all the o other languages I've seen K 2) Access to the RMS stuff in the context of the default I/O system's more -& black art in C than in other languagesK 3) Most of the code that sees the big hit is C, ported from other platformscK 4) Backwards compatibility wouldn't be compromised nearly as much. (If you sJ were using the defaults anyway, it would make sense that the RTL could do C whatever it wanted--hey, this is C, after all, and the RTL changes t behaviour at the drop of a hat)nI 5) It would be a relatively easy upgrade--just another behaviour changed   with a C RTL ECO+ 6) I use C more than any other language. :)s  L #6 is arguably the big reason, being honest. But it seems as if the default K RMS parameters get tweaked a lot less often with C than they do with other .L languages. The fact that the docs on how to do this with parameters to open H are best described as abysmal might have something to do with it, but...  H Just for chuckles I may play with the parameters some with perl and see  what the differences are.   J >   There have been various discussions around various (potential) changesH >   to the RMS defaults, with a key concern being compatibility -- we doH >   not want an existing application to see decreased performance, or toH >   see weird application failure(s) due to changes to the RMS defaults.  L Even a (well documented, heavily promoted) command that needed to be issued I like, say, SET RMS/FAST would be nice. Could be left off by default, but a@ those of us who don't have compatibility issues could set it in J SYLOGIN.COM, while those folks who do could leave it off. (Or make it the G default, with a SET RMS/COMPATIBLE command (or /NOFAST) to turn it off)k  I >   More than a few applications have seen dramatic improvements with the,H >   addition of some simple RMS extensions on the C (f)open call, eitherG >   requesting better buffering or (when appropriate) requesting SQO oryF >   similar RMS performance options.  But the default values chosen by% >   RMS itself need a careful look...u  H Please, *please* get this bumped up to high priority. (P-1 anyone?) The 3 faster VMS' default I/O performance is, the better.e   					Dan  I --------------------------------------"it's like this"-------------------i2 Dan Sugalski                          even samurai? dan@sidhe.org                         have teddy bears and even-;                                       teddy bears get drunkr   ------------------------------  % Date: Wed, 31 May 2000 10:29:49 -0400s) From: "Viens, Daniel" <DVIENS@adm.me.org>5 Subject: UNSUB INFO-VAX3I Message-ID: <DE5D35643522D411B7C10008C791D522187DB1@bdmb_5003.adm.me.org>    UNSUB INFO-VAX   ------------------------------   Date: 31 May 2000 17:03:41 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) Subject: Re: UNSUB INFO-VAXd6 Message-ID: <8h3gld$a53$1@mailint03.im.hou.compaq.com>  u In article <DE5D35643522D411B7C10008C791D522187DB1@bdmb_5003.adm.me.org>, "Viens, Daniel" <DVIENS@adm.me.org> writes:q :UNSUB INFO-VAXt  D   You are submitting messages to the list, not requests to the list D   server.   For details on how to unsubscribe from INFO-VAX, please E   see the message you received when you signed up, or please see the 2<   information in the OpenVMS FAQ.  The FAQ is available via:  "     http://www.openvms.compaq.com/  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Wed, 31 May 2000 07:59:16 -0400t& From: "Jeff Killeen" <Jeff@Killeen.cc> Subject: VAX on Intel?% Message-ID: <3934fd1b@news.toast.net>d   http://www.charon-vax.com/   --     Jeff Killeen - www.Killeen.ccnE =====================================================================e   ------------------------------  % Date: Wed, 31 May 2000 15:22:43 +0200v3 From: Eric Hollander <eric.hollander@NOSPAMeds.com>  Subject: Re: VAX on Intel?) Message-ID: <39351223.433A@NOSPAMeds.com>n   Jeff Killeen wrote:s >  > http://www.charon-vax.com/ >  > -- >  > Jeff Killeen - www.Killeen.cceG > =====================================================================- Does it exist ? VAX in INTEL ? -- - Eric Hollander  F Wie de toekomst als tegenwind ervaart, loopt in de verkeerde richting.- (E.M.C. Michiels, Universiteit van Amsterdam)   0 ************************************************0 To reply thru E-mail, remove NOSPAM from address0 ************************************************   ------------------------------  # Date: Wed, 31 May 2000 10:27:48 GMTp) From: "Neil Rieck" <n.rieck@sympatico.ca>-6 Subject: Re: VAX VMS 7.2 Bug? ; backup/image/(no)alias8 Message-ID: <EO5Z4.5603$uw6.73353@news20.bellglobal.com>  = Robert Deininger <rdeininger@mindspring.com> wrote in message-& news:B55845DC-57E60F@165.247.41.201... <snip> > H > Before upgrading from 5.5-2 to 7.1, I had to deal with this problem onG > a microvax.  It was much more messed up than the example described. IhD > think it had been subjected to the sick backlink problem, and thenH > upgraded once or twice.  It was REALLY weird.  And it worked perfectlyD > for years.  I took the time to fix everything before upgrading.  I4 > didn't want to test the limits of directory chaos. >pI > This BACKUP/NOALIAS issue is getting more confusing all the time.  EacheF > new version of the manual confuses me more.  The documentation folksE > really need to expalain 1) exactly when to use /alias and /noalias,eH > 2) exactly how to make a perfect backup copy of a disk, and 3) exactly* > how to do a perfect restore of a backup. >rH > I used to think /noalias was only needed to RESTORE image backups made@ > by a slightly sick version of backup from version 6.something. >eF > Why would I want to make a copy of the system disk that doesn't have > all the aliases? >d > ---------------------------o > Robert Deininger > rdeininger@mindspring.comd >6  I agree with you 100%.PD Once upon a time (grin) VMS HELP and paper documentation was totallyL understandable while UNIX MAN pages were not (considering that the MAN pagesL are written in my native language, I believed that this was some kind of jobB protection scheme by UNIX people). Today, UNIX MAN pages are stillC unintelligible and VMS info seems to be creeping in that direction.m  
 Neil Rieck* Kitchener(New Berlin?)/Waterloo/Cambridge, Ontario, Canada.! http://www3.sympatico.ca/n.rieck/0   ------------------------------  # Date: Wed, 31 May 2000 11:26:56 GMT:) From: "Neil Rieck" <n.rieck@sympatico.ca>.6 Subject: Re: VAX VMS 7.2 Bug? ; backup/image/(no)alias8 Message-ID: <4G6Z4.1446$dK2.75167@news20.bellglobal.com>  2 Neil Rieck <n.rieck@sympatico.ca> wrote in message2 news:EzNY4.9606$WV.531182@news20.bellglobal.com... > John,S* > I think you may be on to something here. > K > First off, if I execute ANA/DISK on the suspect source disk (which backedl up@ > just fine under VMS 6.2 by the way), no problems are reported. >-D > However, if I do a BACKUP/IMAGE on this same disk and then execute ANA/DISKA > on the target disk, many errors are reported. If I then execute G > ANA/DISK/REPAIR on the target disk, then all my missing files are nowo foundnI > in [SYS$LOST}. At this point I could probably rename the [SYSLOST] tree  backA > to VMS$COMMON and try a boot of the target (after first runningS > WRITEBOOT.EXE of course).o >cH > (BTW - this means that BACKUP/IMAGE was working all along but that the- > proper directory entries have been skipped)g > I > I think I'll start by first comparing the directory structure of my VAXCH > system disk (which had been progressively upgraded from VMS 5.4) to my Alphau< > system disk (which contains a new VMS 7.2-1 installation). >i  K For anyone following this thread, here are the results of running DIR/ALIASuJ from DFU ("Disk File Utility" from the Freeware CD-ROM) on the troublesomeF VAX and the working Alpha. It would seem that the VAX system disk is aI little messed up but this doesn't explain why so many files are seeminglytG dropped by BACKUP/IMAGE. (unless there is a bug in BACKUP 7.2 that onlyc7 allows a perfect copy when there is no alias confusion)V  K Whatever the reason for my problems, it would be nice if future versions of,F BACKUP issued some sort of "ALIAS cross linked directory" warning whenL copying from any suspect disk. This little feature may could be a life saver for someone.  
 Neil Rieck* Kitchener(New Berlin?)/Waterloo/Cambridge, Ontario, Canada.! http://www3.sympatico.ca/n.rieck/o  ' ---------------------------------------e& KAWC15 (VAX VMS 7.2 upgraded from 5.4)  C %DFU-I-INDSCAN, Making directory table for DSA0:[000000...] (DSA0:)m+ %DFU-I-DIRSCAN, Scanning 190 directories...vH DSA0:[000000]SYSMAINT.DIR;1 is alias for DSA0:[VMS$COMMON]SYSMAINT.DIR;1' DSA0:[SYSEXE]SYSBOOT.EXE;1 is alias fore% DSA0:[VMS$COMMON.SYSEXE]SYSBOOT.EXE;1aE DSA0:[SYS0]SYSCOMMON.DIR;1 is alias for DSA0:[000000]VMS$COMMON.DIR;1?  & %DFU-S-DONE, Directories scanned : 190' --------------------------------------- ( KAWC05 (Alpha VMS 7.2-1 initial install)  J %DFU-I-INDSCAN, Making directory table for DKB0:[000000...] (KAWC05$DKB0:)+ %DFU-I-DIRSCAN, Scanning 244 directories...e. KAWC05$DKB0:[SYS0]SYSCOMMON.DIR;1 is alias for KAWC05$DKB0:[000000]VMS$COMMON.e DIR;1u  & %DFU-S-DONE, Directories scanned : 244' ---------------------------------------i   ------------------------------  % Date: Wed, 31 May 2000 18:01:23 +0000 $ From: Steve.Spires@yellowpages.co.ukI Subject: VAXCluster Principles book (was Re: Problem with resource locks)e/ Message-ID: <002568F0.0063183A.00@quegw01.btyp>l  = Contact:   Tel: 3063  -  VSSG, 1st Floor, Bridge Street Plaza    I agree wholeheartedly!r  O So, anyone at Compaq or interested and knowledgable parties... Are we likely tosM see an update to this tome? The original is good, if a little expensive here, J but an updated alpha-ised version (relevant to OVMS 7.n?) would be better.   Steve Spires VMS System Manager BT/Yellow Pagesx        L Jan Vorbrueggen <jan@fsnif.neuroinformatik.ruhr-uni-bochum.de> on 31/05/2000 16:32:59    To:        Info-VAX@MVB.SAIC.COM+ cc:         (bcc: Steve Spires/YellowPages)tM From:      Jan Vorbrueggen <jan@fsnif.neuroinformatik.ruhr-uni-bochum.de>, 31=            May 2000, 4:32 p.m.   Re: Problem with resource locksh        > Georges SZAFRANSKI <szafranski@lutece.evt.cpqcorp.net> writes:  < > Why don't you start with chap 6 of VAXcluster principles ? > Author Roy G. Davies > DP ISBN 1-55558-112-9  > PH ISBN 0-13-064338-6s  E Just by the title, it must be massively out of date. How long has the1L EXPEDIATE flag existed? Practically every major (and some minor) VMS releaseG has modified the logic behind lock tree mastering and remastering. Nah,A an update is surely required.         Jan   ------------------------------   Date: 31 May 2000 17:22:36 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)M Subject: Re: VAXCluster Principles book (was Re: Problem with resource locks)i6 Message-ID: <8h3hos$ad0$1@mailint03.im.hou.compaq.com>  V In article <002568F0.0063183A.00@quegw01.btyp>, Steve.Spires@yellowpages.co.uk writes:P :So, anyone at Compaq or interested and knowledgable parties... Are we likely toN :see an update to this tome? The original is good, if a little expensive here,K :but an updated alpha-ised version (relevant to OVMS 7.n?) would be better.u  I   I've passed along a set of similar requests to the author a while back. A   I do not know what the current plans for an update to the book.*  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Wed, 31 May 2000 01:18:25 -04001- From: JF Mezei <jfmezei.spamnot@videotron.ca>o" Subject: Re: Wildfire Announcement, Message-ID: <3934A087.4AB1906D@videotron.ca>   "Main, Kerry" wrote:I > "Compaq and Oracle have embraced the Internet as the standard model forrK > computing, and today are taking customers to the forefront of e-business.a  N During the Wildfire announcement, both the local reps and the Capellas-EllisonK speaches outlined Oracle's commitment to True-64. (top tier stuff). VMS wasu" never mentioned along with Oracle.   ------------------------------  % Date: Wed, 31 May 2000 11:04:54 +0100wB From: Andrew Harrison SUNUK Consultancy <andrew.nospam@uk.sun.com>" Subject: Re: Wildfire Announcement* Message-ID: <3934E3C5.6A879D5C@uk.sun.com>   "Main, Kerry" wrote:   > Hello Andrew ..v >sK > Just catching up on email and could not let you slide still more fud into . > the newsgroup without some sort of response: >rC > >>> Compaq have not given OpenVMS the shot in the arm that peopleGL > expected/hoped for and have treated it no better or worse than Digital did > in the Bob era.<<< >gI > Check out the followng url and see if you recognize some of these names0K > (like ETrade- one of top onlne investing site, Northernlight - the number1" > one Internet search engine etc):6 > <http://www.openvms.digital.com/gsseries/index.html> >  > Or in the press:I > <http://www.boston.com/dailyglobe2/150/business/Hardware+.shtml> Bostona > Globe on Alpha May 29, 2000e >l( > On Alpha/OpenVMS/Tru64 and ISV supportN > <http://www1.compaq.com/pressrelease/0,1494,wp%7E14583_2%21ob%7E30093_1_1,00 > .html>K > "Larry Ellison, Chairman and Chief Executive Officer, Oracle Corporation,R > said: I > "Compaq and Oracle have embraced the Internet as the standard model forhK > computing, and today are taking customers to the forefront of e-business.sL > Oracle software, coupled with the power of Compaq's AlphaServer GS series,F > creates one of the industry's most robust and reliable platforms for > e-business." >R  H Compaq pays Oracle a considerable amount of money for the OpenVMS, Tru64N ports of Oracle, you should get something back for your investment and Larry'sL kind words are part of the deal. Don't read anything else into it than that.  H Larry has said almost exactly the same things about Sun's, HP, and IBM's) its all about promoting the Oracle brand.    > From same url:C > "ISV Recruitment Program: Compaq is working closely with existing G > application partners, such as Oracle and SAP, and emerging ISVs(5) to G > deliver full e-business solutions for Compaq's Tru64 UNIX and OpenVMSo > operating systems."s  F Really, so who is Compaq working with to get e-Business apps availableH on OpenVMS. It isn't WebSphere, iPlanet, Ariba, Commerceone, BroadvisionN ATG, HP. The only major supplier of eBusiness applications infrastructure thatB I know of that supports OpenVMS is BEA, but then if you want to doB personalisation say using ATG Dynamo with BEA WebLogic what should= you do since Dynamo does not run on OpenVMS or Tru64 for that3 matter.0  G Get real, you can't even use OpenVMS as a simple Web server in a lot ofRB these environments because people like BroadVision require Nescape3 Enterprise Server and they provide an NSAPI plugin.r  A How about SSL crypto accelerators and key vaults got any of those : for OpenVMS, how about a WAP gateway, are you working with= any of the gateway suppliers. If this wasn't so sad you wouldiI have to laugh Compaq has its own AXL200 PCI crypto accelerator which they B support on Novell, NT, Tru64, Solaris and Linux (but not OpenVMS).A How about a certificate management system, this is basic plumbingnC if you haven't got these components you don't even get to enter thee race let alone finish.  > Come on Kerry these quotes are content free, there is precious@ little evidence that anything is actually happening. Sure Apache9 is coming out, but delivering Apache on OpenVMS isn't thed basis of an eBusiness strategy.e  ; People on this newsgrou have complained that "anti OpenVMS" ? posts effect their livelyhood and no doubt they will think thatu my post is "anti OpenVMS".  D They are wrong, I am ambivilent about OpenVMS, it isn't a competitorK to Solaris and is unlikely to be if your posts are the best there is. Sadlya$ I consider it to be mostly harmless.  < What isn't harmless it the people on this newsgroup who need= OpenVMS to survive for their own careers to prosper being fedeB a diet of marketing blurb without substance which makes them think= that perhaps they are safe and perhaps Compaq will secure theS> future of OpenVMS. The fact is that over the last 2 years what% has happened to make them think this.s  E Apache being ported (great its freeware why would this be a huge win))I Mozilla being ported (Netscape 4.x.x should have been on OpenVMS form the  start)< Compaq very occasionally mentioning OpenVMS in the odd pressN release (Wow how much does it cost for someone to add OpenVMS to NT and Tru64)    J > Now, if I was really into fud, I would post the 1997 Sun announcement onG > Sparc III (now not expected in large servers until 2001), or questionrH > whether a single solution vendor is more capable than a multi-solutionM > vendor to respond to Customers requirements, but I am not into that type ofh > stuff, so I won't.  G Why bother, this isn't about how Sun manages its product development or H how it markets Solaris/SPARC its about how Compaq preserves and developsD OpenVMS. What's the point of trying to throw FUD at Sun when Compaqs( own house is in such a disordered state.  K Do you thing that throwing FUD at Sun is going to improve OpenVMS's chancese of survival ??  I 99% of people who buy Sun's have either not ever heard of OpenVMS or havei excludedK it from their choice of platfrom for good reasons like the Compaq rep never 	 mentionedtK it or the software they need does not run on it. Do you honestly think thate bashinge, Sun is going to make them look at OpenVMS ??  D Isn't this just an easy excuse to avoid addressing the real issues ?  * Question: Where is the OpenVMS ISV program Ans:          Bash Sun3 Question: Where are the OpenVMS eCommerce solutions  Ans:          Bash SunE Question: How about giving OpenVMS away for free on Workgroup Serversh Ans:         Bash SunvM Question: When are Compaq going to get their own products like AXL200 runninga  on OpenVMS  Ans:          Bash SunH Question: How about bundling a free version of UCX with the Free OpenVMS licenses Ans:          Bash Sun  K Great, this really works for me, bashing Sun given the relative position of E Sun and Compaq is easy for someone from Sun to defend. Coming up with J something a bit more tangible to any of these perfectly sensible questionsG might give Sun and Compaqs other competition more cause for thought and I might be a bit more likely to preserve the jobs of the people who rely onsF OpenVMS on this newsgroup. As it is Rob yourself and the other OpenVMS@ boosters are in my opinion doing these people a huge disservice.   Regards    > Andrew Harrison  > Enterprise IT Architectc >U   ------------------------------  % Date: Wed, 31 May 2000 12:46:52 +01000B From: Andrew Harrison SUNUK Consultancy <andrew.nospam@uk.sun.com>" Subject: Re: Wildfire Announcement* Message-ID: <3934FBAB.C223FB36@uk.sun.com>  ( Andrew Harrison SUNUK Consultancy wrote:  H > Really, so who is Compaq working with to get e-Business apps availableJ > on OpenVMS. It isn't WebSphere, iPlanet, Ariba, Commerceone, BroadvisionP > ATG, HP. The only major supplier of eBusiness applications infrastructure thatD > I know of that supports OpenVMS is BEA, but then if you want to doD > personalisation say using ATG Dynamo with BEA WebLogic what should? > you do since Dynamo does not run on OpenVMS or Tru64 for thate	 > matter.i >l  F Following your own posts up is bad practice, but I forgot to point outB that the only vendor that supports OpenVMS at all in the eCommerce@ space (BEA) only does it partially. The basic WebLogic server isD available for OpenVMS but Enterprise Server, Personalisation Server,> Commerce Server are not available for OpenVMS. Commerce Server< and Personalisation Server arn't available for Tru64 either.  B So if you were building a big eCommerce application you would haveA the choice of going to Compaq for OpenVMS to host a service based-@ on Weblogic Server but would have to go to someone else (Sun, HPF etc) for all the other pieces. Or you could simply get everything from. one vendor and not bother with OpenVMS at all.     Regardsl Andrew Harrison  Enterprise IT Architecto   ------------------------------  # Date: Wed, 31 May 2000 14:29:39 GMT=0 From: "Terry C. Shannon" <shannon@world.std.com>" Subject: Re: Wildfire Announcement% Message-ID: <FvFHq2.rr@world.std.com>l  G "Andrew Harrison SUNUK Consultancy" <andrew.nospam@uk.sun.com> wrote inv, message news:3934E3C5.6A879D5C@uk.sun.com... > "Main, Kerry" wrote: >* > > Hello Andrew ..a > >eH > > Just catching up on email and could not let you slide still more fud into0 > > the newsgroup without some sort of response: > >1E > > >>> Compaq have not given OpenVMS the shot in the arm that peopleVJ > > expected/hoped for and have treated it no better or worse than Digital did0 > > in the Bob era.<<< > >iK > > Check out the followng url and see if you recognize some of these names5F > > (like ETrade- one of top onlne investing site, Northernlight - the number$ > > one Internet search engine etc):8 > > <http://www.openvms.digital.com/gsseries/index.html>  I The Sun folks would rather you did not pay any attention to E*Trade. TheydD fought like hell for that account, and lost. To, umm, OpenVMS/Alpha.  D Whatever, it should be obvious to all and sundry that Sun has done aJ magnificent job capturing both mindshare and marketshare in the enterpriseG server space. Did you happen to see Smiling Scott on CNN MONEYLINE lastmI night? If not, it's worth resurrecting the film clip so you can see how a H company who knows how to market can prevail over firms offering superior technology.   L How is this possible? Beats me... why not lure some of those Sucker Moms out< of their SUVS and ask 'em why they voted for Clinton, twice.   ------------------------------  % Date: Wed, 31 May 2000 11:52:46 -0300.1 From: "Boyle, Darren" <boyledj@bankofbermuda.com>e" Subject: RE: Wildfire AnnouncementK Message-ID: <F150836441C5D311A11700508B6FF01A983500@bdant024.bda.bobda.com>r  5 > From: 	Terry C. Shannon[SMTP:shannon@world.std.com] K > night? If not, it's worth resurrecting the film clip so you can see how aiJ > company who knows how to market can prevail over firms offering superior
 > technology.g > 3 That's been happening for years, look at McDonalds.s - Darren    F **********************************************************************C This message and any files transmitted with it are confidential andeJ may be privileged and/or subject to the provisions of privacy legislation.M They are intended solely for the use of the individual or entity to whom they L are addressed. If the reader of this message is not the intended recipient, B please notify the sender immediately and then delete this message.I You are notified that reliance on, disclosure of, distribution or copying4 of this message is prohibited.   Bank of Bermuda F **********************************************************************   ------------------------------  # Date: Wed, 31 May 2000 17:46:04 GMTe0 From: "Terry C. Shannon" <shannon@world.std.com>" Subject: Re: Wildfire Announcement& Message-ID: <FvFqM1.31o@world.std.com>  < "Boyle, Darren" <boyledj@bankofbermuda.com> wrote in messageE news:F150836441C5D311A11700508B6FF01A983500@bdant024.bda.bobda.com...i6 > > From: Terry C. Shannon[SMTP:shannon@world.std.com]K > > night? If not, it's worth resurrecting the film clip so you can see howt a L > > company who knows how to market can prevail over firms offering superior > > technology.C > >M5 > That's been happening for years, look at McDonalds.o  A And look at the corpulence and obesity that has resulted from thep= FoulArches! Directly proportional to the divorce rate, sez I!h   ------------------------------  % Date: Wed, 31 May 2000 10:46:44 +0200w. From: Tim Oakley <t.oakley@maury-imprimeur.fr> Subject: X Font Server for VMS2 Message-ID: <3934D174.6413E860@maury-imprimeur.fr>  > <!doctype html public "-//w3c//dtd html 4.0 transitional//en"> <html> &nbsp;< <br>I want to run a font server under VMS 7.1-2 and UCX 4.2.F <p>Is a font server included with UCX (i can't find it), or is there a8 known free/share ware implementation of 'xfs' for VMS. ? <p>TFYP k<p>&curren;&curren;&curren;&curren;&curren;&curren;&curren;&curren;&curren;&curren;&curren;&curren;&curren;&curren;&curren;&curren;&curren;&curren;&curren;&curren;&curren;&curren;&curren;&curren;&curren;&curren;&curren;&curren;&curren;&curren;&curren;&curren;&curren;&curren;&curren;&curren;&curren;&curren;&curren;&curren;&curren;&curren;&curren;&curren;&curren;i <br>Tim OAKLEY <br>MAURY-Imprimeur, <br>Z.I, Route d'Etampes <br>45330 MALESHERBES Cedex-
 <br>France <p>Tel: (33) 02.38.32.34.38o <br>Fax: (33) 02.38.32.37.70' <br>Email : t.oakley@maury-imprimeur.frD> <p>"OpenVMS is today what Microsoft hope Windows 5000 will be" <br>&nbsp;</html>s   ------------------------------   Date: 31 May 2000 12:40:53 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)" Subject: Re: X Font Server for VMS6 Message-ID: <8h318l$4gv$2@mailint03.im.hou.compaq.com>  c In article <3934D174.6413E860@maury-imprimeur.fr>, Tim Oakley <t.oakley@maury-imprimeur.fr> writes:n      Please turn off HTML.  Thanks.  9 :I want to run a font server under VMS 7.1-2 and UCX 4.2.CD :Is a font server included with UCX (i can't find it), or is there a9 :known free/share ware implementation of 'xfs' for VMS. ?U  E   The OpenVMS Wizard was asked the same question recently -- the font-I   server startup mechanism is described in the DECwindows private server 0H   setup template procedure.  Also, please move to TCP/IP V5.0A.  I will I   ask that the answer queued over in the Ask The Wizard area be canceled.0  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------   End of INFO-VAX 2000.303 ************************