1 INFO-VAX	Sun, 29 Jul 2001	Volume 2001 : Issue 418       Contents:  Re: (auto|sys)gen and params.dat Re: A Primrose Path... Re: absolute beginner ! Re: Attunity Connect and Oracle 8 & Decevent "add user" and "add external"$ Re: Few People in DEC Understood.... Game for Computer Pros re: Go confront a function!  how to replace BIOS battery % Re: IA64 volume and low-end dominance % Re: IA64 volume and low-end dominance 6 Re: IPF Console Bootstrap (was: No chance for OpenVMS): Re: IPF Console Bootstrap (was: Re: No chance for OpenVMS)P Re: Ken Olsen (and DEC History), was: Re: Escape sequences not filtered in VMS M Re: Ont "The Inquirer" today. ' Re: Passing a socket to another process ' Re: Passing a socket to another process ' Re: Passing a socket to another process  Re: Porting quandry P problem deallocating a CD rom device when reflection used to allocate it is closP Re: problem deallocating a CD rom device when reflection used to allocate it is P Re: problem deallocating a CD rom device when reflection used to allocate it is 1 Re: The death of VMS has been greatly exaggerated J re: Try contributeing the cellar's flat trackball and Ralf will close you! Re: V7.3 XFCACHE-W-DATALOSS ? ! Re: VAX 11/785 cabinet needed ...  Re: VS3100 & (dead?) ST51080N < Re: Wailing and moaning... (was: Question to Charlie Matco.)F re: What will we restore after Cathy examines the fast folder's email?F Re: What will we restore after Cathy examines the fast folder's email?  F ----------------------------------------------------------------------  % Date: Sun, 29 Jul 2001 10:53:25 -0500 1 From: "David J. Dachtera" <djesys.nospam@fsi.net> ) Subject: Re: (auto|sys)gen and params.dat ' Message-ID: <3B643175.71BE1316@fsi.net>    "Brian M. Kelley" wrote: > 9 >   Hey all. VMS-admin newbie here. We're running OpenVMS  >   7.2-1 on an Alpha 433a.  > : >   I did a bad (?) thing: I deleted sys$system:params.dat; >   (don't ask; little sleep the previos night). Here's the = >   catch: I don't have a backup. The question is, of course, = >   how can I recover/regenerate this file? Is this possible? ? >   I can see the system param values running 'paramaters/show' = >   in sys$system:sysman, so I know regenerating this file is : >   possible in some manner (that, and booting the machine0 >   doesn't seem to depend on this file either). > / >   I need the file to be in place so I can run : >   sys$system:autogen to reconfig some system parameters.9 >   Apologies if this question has an obvious answer that  >   I'm not seeing. Thanks!   B PARAMS.DAT is a transient file produced by AUTOGEN. The lack of an? existing version is not a problem, so long as you have not also H clobbered MODPARAMS.DAT, the file where in you specify your changes from. the default values for any system parameters.   @ The parameters loaded at boot time are in ALPHAVMSSYS.PAR in the8 SYS$SYSTEM: path. If "lose" that one, you regenerate it:   $ SYSMAN param use active param write current  $ EOD   $ How do you regenerate MODPARAMS.DAT?  E Well, I wrote some DCL code once to determine the differences between H the default parameters and the parameters of the running system. I don'tG have that code handy, but essentially what I did was to take the output  of:   $ $ SYSMAN PARAM SHOW/ALL/OUT=filespec  F ..., READ that using DCL, parse out the various value elements of eachE line using F$ELEMENT() (using " " as the delimiting character, having C first used F$EDIT( vbl, "TRIM,COMPRESS" )). Then, for each instance D where the current value differs from the default, write out a record consisting of:   vbl_name = value  ' ...which becomes the new MODPARAMS.DAT.   4 That's the basics - there are a couple of "gotchas".  F I had to do this because people had been using SYSMAN and/or SYSGEN to1 modify parameters without updating MODPARAMS.DAT.   D Sorry, I was ushered out rather quickly on my last layoff and didn'tF have the chance to send such code to myself via e-mail or whatever. ItD was the company's first mass layoff - they had no experience to fall= back on, and so were "playing it safe" with their discharges.    --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/   F This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings is to be expected.  @ Feel free to exercise your rights of free speech and expression.  F However, attacks against individual posters, or groups of posters, are strongly discouraged.    ------------------------------  % Date: Sun, 29 Jul 2001 11:02:41 +0200 ) From: Christof Brass <brass@infopuls.com>  Subject: Re: A Primrose Path... , Message-ID: <3B63D131.47BE59D6@infopuls.com>   Bob Kaplow wrote:  > z > In article <OF828ACEFA.5872850A-ON03256A80.006BED8A@ep-bc.petrobras.com.br>, fabio_compaq@ep-bc.petrobras.com.br writes:E > > In my personal opinion..... Intel should forget this  64 bit chip B > > and develop the  IA-128. IA-64 is insist in what exist: Alpha. > J > DEC and Intel should have cut that deal 3.5 years ago when they sold theL > ALpha FAB6 to Intel. Then everybody would already be running on the latest  > Intel 64 bit processor: Alpha! > L > No, the ONLY thing DEC EVER produced that EVER became an industry standardE > was the VT-100. Even today Winblows ships with a rather poor VT-100 % > emulator as it's terminal emulator.   ; What about Ethernet? Wasn't this co-developed by DEC at the  PARC?    ------------------------------    Date: 29 Jul 2001 06:54:53 -07001 From: nothome@spammers.are.scum (Malcolm Dunnett)  Subject: Re: absolute beginner, Message-ID: <3XIrY8Ze7PyH@malvm5.mala.bc.ca>  * In article <9jsjo8$21a$1@kadath.deep.it>, &     Cthulhu <noone@nowhere.it> writes:  0 > Luca Balzano <luca.balzano@antispam.it> wrote: > J >> OpenVMS. Somebody told me that since I live in Italy this could be more
 >> difficult.  > H > The problem here in Italy is that when DECUS disappeared, nothing went > in its place. G > So, we can't anymore register as a DECUS member, we can't get a DECUS $ > ID, we can't request Hobbist PAKs. >  > And that's bad. :( > :     Join Encompass. They accept members from anywhere now.  F     See http://www.encompassus.org/membership/join.html for membership information.  F   Note: I wouldn't believe the part about sustaining members receivingB a pin and shirt. I signed up as one last year and haven't received anything yet :-(   ------------------------------  % Date: Tue, 24 Jul 2001 22:40:38 +0100 . From: Roger@natron.demon.co.uk (Roger Barnett)* Subject: Re: Attunity Connect and Oracle 8- Message-ID: <104655236wnr@natron.demon.co.uk>   C Not a reply to the complaint about Attunity Connect-but-not-to-rdb, F but how about a java client using the inbuilt orb to talk to a (local B or remote) server which does the actual rdb interfacing via odbc ?  > You can either define your own interface spec between client &@ server or use a jdbc-alike so the client wont change if-and-when> a jdbc to rdb is available and meantime do mappings to odbc in the server.    --  
 Roger Barnett    ------------------------------  % Date: Sun, 29 Jul 2001 14:58:18 +0300 8 From: "Ittamar Weissbrem" <Ittamar.Weissbrem@compaq.com>/ Subject: Decevent "add user" and "add external" 1 Message-ID: <2oT87.289$Yx2.4663@news.cpqcorp.net>    Hi,   I I am trying to find anyone using decevent to get notification when errors  occur.J Please give specifics of what triggers mail and/or external notifications." direct email would be appreciated.   Thanks in advance,   Ittamar Weissbrem 
 Compaq Israel  Ittamar.Weissbrem@compaq.com   ------------------------------  % Date: Sun, 29 Jul 2001 19:30:13 +0010 % From: paddy.o'brien@zzz.tg.nsw.gov.au - Subject: Re: Few People in DEC Understood.... 5 Message-ID: <01K6IJBIL8PE002PQQ@tgmail.tg.nsw.gov.au>   % David Cressey wrote (mainly snipped):   J >Can you add to the above list?  Can you put some hardware products on the >list?  O Still software.  I would judge, especially as a reader of language newsgroups,  O that Compaq inherited from Digital some of the best compiler engineers around.   They are being donated to ....   Regards, Paddy   Paddy O'Brien, Transmission Development, 
 TransGrid, PO Box A1000, Sydney South,  NSW 2000, Australia    Tel:   +61 2 9284-3063 Fax:   +61 2 9284-3050& Email: paddy.o'brien@zzz.tg.nsw.gov.au  M Either "\'" or "\s" (to escape the apostrophe) seems to work for most people, ; but that little whizz-bang apostrophe gives me little spam.    ------------------------------  # Date: Sun, 29 Jul 2001 07:04:02 GMT " From: Matt <nospam@newsranger.com> Subject: Game for Computer Pros 6 Message-ID: <CzO87.10285$ar1.32451@www.newsranger.com>  : I downloaded this security game from Verado. I thought you6 might get a kick out of it.  It's about an overworked,7 stressed out IT guy. You fight off attacks from hackers + and spammers using shredders, flamers, etc.    Here is the link: 3 http://www.verado.com/forms/get_verado_game_2.shtml   	 Have Fun,    Matt   ------------------------------  # Date: Sun, 29 Jul 2001 19:36:19 GMT + From: "Samuel Sheringham" <osafe@dykor.mil> $ Subject: re: Go confront a function!) Message-ID: <979F0E03.8F55DB08@dykor.mil>   T Lately Pamela will wash the zipdisk, and if Susanne happily distributes it too, the ? terminal will put around the lower satellite.  If the powerful  L PGPs can build regularly, the ugly MPEG may disconnect more backups.  Other B offensive stuck routers will compile badly with programmers.  Try E disrupting the station's huge webmaster and Maify will dump you!  It  C binds, you disappear, yet Martha never mercilessly gets inside the  G data center.  Many retarded chaotic analysts will subtly interface the  H connectors.  Thomas will absolutely confront outside Elizabeth when the D strong trackballs close without the haphazard email.  Occasionally, I Charles never digs until Robette creates the fast librarian rigidly.  As  = eerily as Corinne posts, you can generate the disc much more  ? virtually.  Where doesn't Quincy preserve freely?  If you will  A flow Ron's cafe at hackers, it will deeply insulate the backup.   H Occasionally, fax machines save in front of opaque FBIs, unless they're M moronic.  Just contributeing with a subroutine behind the frame relay is too  = odd for Pam to manage it.  Never load the texts undoubtably,  ? sell them inadvertently.  If you'll buy Walt's cyberspace with  E servers, it'll quietly tolerate the diskette.  The operator strongly   prepares the insecure CERT.      ------------------------------  % Date: Sun, 29 Jul 2001 14:49:55 +0700 . From: Suhartoyo <suhartoyo@semen-cibinong.com>$ Subject: how to replace BIOS battery@ Message-ID: <69272CA349ACD111A58D0060083B98F6013D449C@NRG-SVR-2>  K > How to replace the old BIOS battery of CPU with a new one. When we try to I > replace it, the computer can not be start system halt and monitor blank  > and ) > we don't know how to solve the problem.  > We use OvenVMS ver 6.2 >  >    ------------------------------   Date: 29 Jul 2001 16:38:08 GMT& From: peter@abbnm.com (Peter da Silva). Subject: Re: IA64 volume and low-end dominance% Message-ID: <9k1e5g$lic@web.nmti.com>   D In article <q7w87.3248$0w3.428372@newsread2.prod.itd.earthlink.net>,- mulp <michaelpettengill@earthlink.net> wrote: > > "Jordan Henderson" <jordan@lisa.gemair.com> wrote in message& > news:9ibj2h$9nt$1@lisa.gemair.com...C > >   What really drove the move from IA16 to IA32 was not customer ? > >   demand for faster systems, but rather customer demand for D > >   the new system software (Windows386, OS/2, Unix) that required@ > >   IA32.  This is what will drive the move from IA32 to IA64.  = > What software exactly was it that drove the demand for 386?   K For the people I knew who made the jump early, it was ports of Mac software K that really needed large address spaces a-la the 68000 to run with any kind L of decent performance. The first Windows versions on the 386 didn't give youN any way to do that, but when Win32s came out, so you could run 32-bit softwareF even on some older versions of Windows on the 386, it really took off.  L The bottom line for most of these was simply that you couldn't store much of a bitmap in 64k of memory.  M In the 64-bit arena, it's large sparse address spaces for high-end databases.   M I don't think there's yet that much demand for that kind of virtual memory in N end-user systems. Really good VR will probably need >32bit address space, too,/ but that's some distance off (well, > 5 years).    --  +  `-_-'   In hoc signo hack, Peter da Silva. E   'U`    "A well-rounded geek should be able to geek about anything." L                                                        -- nicolai@esperi.org          Disclaimer: WWFD?   ------------------------------   Date: 29 Jul 2001 17:31:13 GMT. From: shoens@lenny.sfrn.dnai.com (Kurt Shoens). Subject: Re: IA64 volume and low-end dominance+ Message-ID: <9k1h91$8lc$1@bob.news.rcn.net>   M In article <9k1e5g$lic@web.nmti.com>, Peter da Silva <peter@abbnm.com> wrote: N >In the 64-bit arena, it's large sparse address spaces for high-end databases.  C Please explain why this helps high-end databases.  The direct value G I can think of is the ability to address a large buffer pool that still E fits in physical memory.  Sparse addressing isn't necessary for that.    ------------------------------  % Date: Sun, 29 Jul 2001 12:08:53 +0200   From: Paul Sture <paul@sture.ch>? Subject: Re: IPF Console Bootstrap (was: No chance for OpenVMS) + Message-ID: <VA.00000403.47ccbb5a@sture.ch>   E In article <30j87.262$Yx2.3832@news.cpqcorp.net>, Hoff Hoffman wrote:  [snip] > K >   Since this concise an answer will undoubtedly annoy or puzzle someone,  L >   I'll elaborate: ODSx will not exist within FAT32.  In fact, the reverse I >   will be true.  The boot block will look different (it'll look like an H >   MBR block), and pointers in the (MBR) boot block will reference someJ >   disk storage elsewhere on the system disk -- in fact, the system disk J >   structure will externally look and work just like it does now.  There J >   will probably be a new reserved file on the system disk (just like theI >   existing APB.EXE is referenced by LBN from within the boot block; see N >   WRITEBOOT and the IDSM), but the referenced file will contain the "stuff" L >   of interest to the console, and the internal format of the file will be K >   known to the console.  In fact, the internal format will look just like M >   FAT32.  Wow.  Cool design, eh?  :-)  (If we work it right, we might even  M >   have a way to keep Windows from scribbling its "harmless" signatures onto  >   OpenVMS disks.)  > E And I note that the so called "harmless" signature left behind by W2K C just rendered my second hard drive unreadable from NT 4. I _knew_ I > should have physically disconnected it before applying the W2K "downgrade"...   [snip] ___ 
 Paul Sture Switzerland    ------------------------------  % Date: Sun, 29 Jul 2001 01:10:36 -0500 % From: "Rich Jordan" <rjordan@mcs.net> C Subject: Re: IPF Console Bootstrap (was: Re: No chance for OpenVMS) 5 Message-ID: <1NN87.18780$j02.273301@news.goodnet.com>   ! Hoff Hoffman wrote in message ... D >In article <4F487.18169$j02.268504@news.goodnet.com>, "Rich Jordan" <rjordan@mcs.net> writes:  >:Hoff, thanks for responding. >:G >:Hoff Hoffman wrote in message <42D77.93$Yx2.2617@news.cpqcorp.net>... @ >:>In article <cc5619f2.0107250647.7a7986fb@posting.google.com>,* >:jordan@ccs4vms.com (Rich Jordan) writes:G >:>:     are we going to be "stuck with" a graphics only console?   ...  >:> F >:>  It appears that both serial and graphics can be made to function,G >:>  and we will likely need to get a serial console working during the H >:>  debug.   If we use USB, there will be restrictions around switchingI :>  from a running OpenVMS system back to the console and then attempting J :>  to continue OpenVMS -- that very likely won't work.  (No HALT and then :>  CONTINUE, in other words.) >:- >:I recall your earlier posts on this matter.  > C >  Then you may also recall my "it's _way_ early for this question"  >  comments. >     E I  felt it appropriate to make a strong desire and preference for the F continued availability of a standard serial console known to those whoJ will end up providing it, as I honestly doubt making that known _anywhere_J else at Compaq would matter in the least.  In fact, I will strengthen thatI statement.  The lack of a serial console would be considered as a seriousnG shortcoming and detriment, given our established system and maintenance-J environment; the information from Fred and you that it is possible and notH outright prevented by the ipf environment is a positive response, though obviously not binding.  F >:...The restrictions imposed by USB would have an impact based on ourH >:current usage, but only a minor one (say once or twice a year where we; >:have to do something from the console without rebooting).  >kD >  Details on what you are doing at the console will be of interest.? >  There may well be an alternative approach already available.b >     B The three occasionally (rarely!) needed items are a cluster quorumL recalculation or  mount verify cancellation (using IPC), and forcing a crashG on a hung system.  I understand that AMDS is able to do the quorum (notnL sure about the mount verify cancellation) but as most of these sites are oneD VAX or one Alpha shops managed through a serial dialin (which can beK connected to the console...) AMDS is not a solution except in our own shop.t  G >:Note that you'll have to give us a new way to force a system crash inl >:that case too... >yG >  You are asking questions on (or are specifically requesting features-E >  for) future hardware support, and not something I am in a position0E >  to offer commitments on.  USB is the defacto standard interconnect(F >  on commodity systems, hence that may well be the default management2 >  interconnect on various new hardware platforms.    F Apologies; all I meant was that the "standard" method long provided ofD forcing a system crash from console, for the purpose of generating aG crash dump file, will need to have a usable replacement.  I'm certainly 1 not asking for written commitments at this point.    >oF >  That said, at least for puposes of the OpenVMS system debug and forF >  the sorts of remote console access used within OpenVMS engineering,G >  we will have to get the serial console connections working.  We willoE >  also have to have a mechanism to force a system crash.  Now as for C >  what will be formally supported, please see previous comments...g    E Perhaps I'm being presumptuous in bringing up questions that touch onaJ items important, or at least useful to the work my company does, but it isD not with the assumption that VMS Engineering hasn't 'thought of it'.  F We have already lost one sale here, which probably would have been ourI largest of the year.  Another is on shaky ground, also because of the ipfeE announcement, and a third one is likely to be as soon as the customer.G is informed (they don't know yet; all the stuff they get from Compaq is I wintel promotional despite the fact that their sole connection with the QrC is their support contract on their current VAX; telling them is thehC salesman's fun job).  Outside of Usenet and the bits from the presstD releases we have precisely squat to tell the customer to try and re-? assure them.  The distributors know nothing.  Our few remainingUE sales contacts know nothing.  Calls are not getting returned (we're am@ _small_ VAR; we didn't get a visit or call from anyone before orB since).  What we get from you all on Usenet , preliminary and non-A binding as it is, is what we have to base reassurance and hopefulu  information to our customers on.   > 6 >  And again, this is _way_ early for these questions. >T  D I _greatly_ regret the need to ask them here and now, and will fullyI understand any reluctance on your part to answer in whole or in part, buttH we are grateful for any information, and even informed speculation, that can be provided.   Rich Jordant rjordan@mcs.net    ------------------------------   Date: 29 Jul 2001 17:23:49 GMT0 From: fdc@watsun.cc.columbia.edu (Frank da Cruz)Y Subject: Re: Ken Olsen (and DEC History), was: Re: Escape sequences not filtered in VMS Mc5 Message-ID: <9k1gr5$ejg$1@newsmaster.cc.columbia.edu>f  ) In article <nRD87.5399$%L5.76226@insync>,g5 Jerry Leslie <LESLIE@209-16-45-102.insync.net> wrote: E : Have you tried contacting the manufacturers to inform them of theire : products' shortcomings ? : J Sure, but keyboard makers are in business to make money.  The sad fact is,L nobody under "a certain age" types any more, at least not to the extent thatL they would care about keyboard quality.  Keyboards were once a hot topic butH now they too are mass-market throwaway Windows components.  (Just think,I it is already 20 years since the Ctrl key was moved off the main keypad.)e  L The quality of the Avant keyboard is excellent, and people who use keyboardsM all day every day probably won't mind paying the big markup, but the physicalrL key placement (giant Enter key displacing backslash) is no doubt mandated byM some silly government procurement rule that favors hunt-and-peck typists overt touch typists.  F Ironically, it's not even good for Windows users, since backslash (the8 Windows directory separator) is off in never-never-land.   - Frank    ------------------------------  % Date: Sun, 29 Jul 2001 19:23:58 +0010y% From: paddy.o'brien@zzz.tg.nsw.gov.au0& Subject: Re: Ont "The Inquirer" today.5 Message-ID: <01K6IJ3R743M0039VU@tgmail.tg.nsw.gov.au>D   Antonio Carlini wrote:   >mulp wrote:N >> How about DECset - no Compaq engineers work on any of those tools.  DECnet,F >> the IBM connectivity products, la dee la.  Lots of that stuff is inK >> maintenance mode with fixed expense budgets - if the problem reports aret9 >> below a certain level than new features will be added.l >o/ >I think the way it works for these products isl2 >that EDS are contracted to do maintenance. If new, >features are required, someone gets to pay.. >The last new feature I worked on was paid for) >by COMPAQ who were (in turn) paid by theg" >customer that wanted the feature.  N Is this really how this works?  An ex-colleague of mine was in correspondence M with Barbara Burri at EDS regarding enhancements (not just maintenance) some eL 2/3 years ago.  I missed out on a beta version because I have been away for J about 10 months over the last 18.  I would have guessed that the beta was O going to include new features, and I would have guessed that their money comes -2 from software support contracts and new purchases.  K I would put this in the same league as when Hoff has asked for suggestions nL here for customers' wishes in the next version of (Open)VMS.  The engineers O would consider all requests but surely no individual or their company was ever   directly billed.  , >I presume that a port of these tools to IPF, >would work the same way. (I cannot imagine + >the DECset tools not being ported; I wouldn( >expect customer pressure to require the >DECnet stuff to port too).e  I As a reader of the plethora of threads on this porting subject, I remain gJ skeptical that the port will ever happen, or if it does it will be a bare 1 bones operating system with limited applications.   N Well, I retire within the timescales discussed, so shall be a hobbyist on VAX F or Alpha boxes until they become irrevocably broken -- though I don't , anticipate that to happen in my lifetime :-)  H I just hope that they let me retire peacefully by maintaining our Alpha M applications.  It would be the stuff that nightmares are made of to envisage r/ coming to work each morning to face a billybox.e   Regards, Paddy   Paddy O'Brien, Transmission Development,-
 TransGrid, PO Box A1000, Sydney South,  NSW 2000, Australiar   Tel:   +61 2 9284-3063 Fax:   +61 2 9284-3050& Email: paddy.o'brien@zzz.tg.nsw.gov.au  M Either "\'" or "\s" (to escape the apostrophe) seems to work for most people, ; but that little whizz-bang apostrophe gives me little spam.m   ------------------------------    Date: 29 Jul 2001 08:09:23 -05009 From: Kilgallen@eisner.decus.org.nospam (Larry Kilgallen)a0 Subject: Re: Passing a socket to another process3 Message-ID: <R3VGlr4qEaT+@eisner.encompasserve.org>   f In article <3B632497.EACDA07B@vista-control.com>, Eugene A Zharkov <zharkov@vista-control.com> writes:< > I have found in comp.os.vms an example of passing a socket6 > to another process that is based on the sys$creprc's< > prc$m_netwrk option. But there is still a couple of things& > that I am not sure how to deal with. > > > 1. The prc$m_netwrk is not documented very well. Maybe there@ > is a better (documented) way of doing this (on VMS 7.1/UCX 5.0 > and higher).  > Generally (and I believe specifically in this case) techniques? that are not documented are not supported.  They may break with.> VMS 7.next.  Posts in comp.os.vms are often made by people who> are not particularly concerned with something being supported.; But certainly VMS Development does not document unsupported  methods.   ------------------------------  # Date: Sun, 29 Jul 2001 12:53:17 GMT = From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-)60 Subject: Re: Passing a socket to another process0 Message-ID: <009FFB94.5FC102EC@SendSpamHere.ORG>  o In article <R3VGlr4qEaT+@eisner.encompasserve.org>, Kilgallen@eisner.decus.org.nospam (Larry Kilgallen) writes:tg >In article <3B632497.EACDA07B@vista-control.com>, Eugene A Zharkov <zharkov@vista-control.com> writes: = >> I have found in comp.os.vms an example of passing a socket 7 >> to another process that is based on the sys$creprc'sp= >> prc$m_netwrk option. But there is still a couple of things ' >> that I am not sure how to deal with.m >> e? >> 1. The prc$m_netwrk is not documented very well. Maybe theresA >> is a better (documented) way of doing this (on VMS 7.1/UCX 5.0  >> and higher).E >a? >Generally (and I believe specifically in this case) techniquesi@ >that are not documented are not supported.  They may break with? >VMS 7.next.  Posts in comp.os.vms are often made by people whon? >are not particularly concerned with something being supported.e< >But certainly VMS Development does not document unsupported	 >methods.s  I I'm concerned with things being "supported" but there has always been an ,I argument as to what constituted "supported".  Hell, I love to see a "sup- H ported" graphics card work in an AS1200, so let's not go down that "sup- ported" rathole.  I As for the the PRC$M_NETWRK option, I doubt that its functionality and/oriH implementation will change such that it is no longer supported.  It *is* documented in the I&DS.-  H The $CREPRC INPUT argument is a file specification of the procedure that" the network process is to execute.  H The $CREPRC OUTPUT argument is unique.  It is a descriptor which points I to a structure which contains a .WORD with a LGI mask of options/settingstI and the username of the account under which to start the network process.y5 LGI$M_NET_PROXY is a typically setting in this field.o  / The $CREPRC STSFLG should specify PRC$M_NETWRK.    --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COM@            tJ   "And of course, I'm a genius, so people are naturally drawn to my fiery I   intellect.  Their admiration overwhelms their envy!" -- Calvin & Hobbesd   ------------------------------  % Date: Sun, 29 Jul 2001 11:54:40 -0600r2 From: Eugene A Zharkov <zharkov@vista-control.com>0 Subject: Re: Passing a socket to another process1 Message-ID: <3B644DE0.F68824B1@vista-control.com>n   Larry Kilgallen wrote: > h > In article <3B632497.EACDA07B@vista-control.com>, Eugene A Zharkov <zharkov@vista-control.com> writes:> > > I have found in comp.os.vms an example of passing a socket8 > > to another process that is based on the sys$creprc's> > > prc$m_netwrk option. But there is still a couple of things( > > that I am not sure how to deal with. > >a@ > > 1. The prc$m_netwrk is not documented very well. Maybe thereB > > is a better (documented) way of doing this (on VMS 7.1/UCX 5.0 > > and higher). > @ > Generally (and I believe specifically in this case) techniquesA > that are not documented are not supported.  They may break witht@ > VMS 7.next.  Posts in comp.os.vms are often made by people who@ > are not particularly concerned with something being supported.= > But certainly VMS Development does not document unsupporteds
 > methods.  @ Too bad. (Not that VMS Development does not document unsupported> methods, but that VMS Development does not provide a supported> method. Even Winsocks seem to have a supported method of doing this!).     > -----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----A http://www.newsfeeds.com - The #1 Newsgroup Service in the World! > -----==  Over 80,000 Newsgroups - 16 Different Servers! =-----   ------------------------------  % Date: Sun, 29 Jul 2001 12:17:37 +0200J) From: Christof Brass <brass@infopuls.com>r Subject: Re: Porting quandry, Message-ID: <3B63E2C1.399A6DEB@infopuls.com>   Bill Todd wrote: > 8 > "Christof Brass" <brass@infopuls.com> wrote in message( > news:3B5F40F2.D0A9B879@infopuls.com...   [SNIP]  A > > But they couldn't get rid of their Wintel systems. This means.C > > they had to support Alpha *and* the others. Even with Windows/*uC > > and NSK on Alpha they would have to continue to build, sell and  > > support Wintel.c > L > So what?  There's good reason to have done so, just as there's good reasonI > to support more than one OS on Alpha (or any platform):  customer needssL > vary, and variety (if executed competently) helps satisfy a larger market. > I > IBM found a good way to approach the same problem:  keep selling WintelwN > boxes (so that it could still offer one-stop shopping) without attempting toN > be the market leader in that area.  So since it's perfectly happy to supportG > market leader Dell's (or anyone else's) products, it gets the best of I > everything:  Wintel margins that support its Wintel efforts, a completes@ > product spectrum, and the ability to concentrate on the uniqueK > differentiators that make IBM unparalleled in the industry (though CompaqtL > could have offered some real across-the-board competition had it chosen to > try).e >  > - bill  > I was responding to the statement that focusing on Alpha would= have lead to the same result: only one line of HW. This isn'tM8 feasible - that should have been the message of my post.  @ To make it clear: I regard abandoning Alpha in favour of IA63 as@ stupid and I don't buy the reasons given. And I personally don't< see a reason why it should be better to focus on one HW line@ because the requirements of the different customers will make it@ necessary in any case to support different HW lines. Even Compaq; offer the iPaq which is StrongARM based which renders theirl statement of one HW line as BS.    ------------------------------    Date: 29 Jul 2001 01:37:13 -0700 From: stelth@iname.com (sunil)Y Subject: problem deallocating a CD rom device when reflection used to allocate it is clos-= Message-ID: <11331f03.0107290037.49f6cca2@posting.google.com>m  - I use reflections to connect to a VMS system.I  O when i accidentally closed a reflection from which i allocated and mounted a CD2L rom drive with out deallocating it. I could not allocate it from a different reflection.jH I got a message to the effect of device already allocated to a different process.  K Is there a way for me ( with out admin priviledges) to get access to the CD. drive.N (other than requesting a reboot, which is the only suggestion i could get till now)  # any help will be  much appreciated.    ------------------------------   Date: 29 Jul 2001 09:16:45 GMT) From: leslie@clio.rice.edu (Jerry Leslie)gY Subject: Re: problem deallocating a CD rom device when reflection used to allocate it is i' Message-ID: <9k0k9t$s34$1@joe.rice.edu>S   sunil (stelth@iname.com) wrote:d/ : I use reflections to connect to a VMS system.k : M : when i accidentally closed a reflection from which i allocated and mounted oH : a CD rom drive with out deallocating it. I could not allocate it from  : a different reflection.iJ : I got a message to the effect of device already allocated to a different
 : process. :mG : Is there a way for me ( with out admin priviledges) to get access to eC : the CD drive. (other than requesting a reboot, which is the only w" : suggestion i could get till now) :t% : any help will be  much appreciated.   I Issue the " SHOW DEVICE/FULL DKxxx" command, where "DKxxx" is the device t name of the CD-ROM drive; e.g.:       $ show device/full dka400  N    Disk SCCVXG$DKA400:, device type RRD42, is online, allocated, file-oriented3        device, shareable, error logging is enabled.d  M        Error count               0    Operations completed                  0pM        Owner process      "LESLIE"    Owner UIC                      [SYSTEM]eM    >>  Owner process ID   0000DA7D    Dev Prot            S:RWPL,O:RWPL,G:R,WnM        Reference count           1    Default buffer size                 512i    J Then issue the "STOP/ID=xxxxxxx" command to stop the process whose "owner J process ID" appears in the output of the "SHOW DEVICE/FULL DKxxx" command; e.g.      $ STOP/ID=0000DA7Dl   --Jerry Leslie   ------------------------------  % Date: Sun, 29 Jul 2001 09:45:41 -0400u) From: Andrew Robert <arobert@townisp.com>yY Subject: Re: problem deallocating a CD rom device when reflection used to allocate it is a* Message-ID: <3B641385.7000409@townisp.com>  2  From a priv'ed account, do the following command:  $ $ dismount/nounload/abort   {device}     Jerry Leslie wrote:l  ! > sunil (stelth@iname.com) wrote:o1 > : I use reflections to connect to a VMS system.  > :mO > : when i accidentally closed a reflection from which i allocated and mounted iJ > : a CD rom drive with out deallocating it. I could not allocate it from  > : a different reflection. L > : I got a message to the effect of device already allocated to a different > : process. > :tI > : Is there a way for me ( with out admin priviledges) to get access to wE > : the CD drive. (other than requesting a reboot, which is the only o$ > : suggestion i could get till now) > :f' > : any help will be  much appreciated.g > K > Issue the " SHOW DEVICE/FULL DKxxx" command, where "DKxxx" is the device  ! > name of the CD-ROM drive; e.g.:h >  >    $ show device/full dka400 > P >    Disk SCCVXG$DKA400:, device type RRD42, is online, allocated, file-oriented5 >        device, shareable, error logging is enabled.  > O >        Error count               0    Operations completed                  0aO >        Owner process      "LESLIE"    Owner UIC                      [SYSTEM]lO >    >>  Owner process ID   0000DA7D    Dev Prot            S:RWPL,O:RWPL,G:R,W O >        Reference count           1    Default buffer size                 512a >  > L > Then issue the "STOP/ID=xxxxxxx" command to stop the process whose "owner L > process ID" appears in the output of the "SHOW DEVICE/FULL DKxxx" command; > e.g. >  >    $ STOP/ID=0000DA7Dh >  > --Jerry Leslie   ------------------------------  % Date: Sun, 29 Jul 2001 10:33:15 +0200e) From: Christof Brass <brass@infopuls.com>t: Subject: Re: The death of VMS has been greatly exaggerated, Message-ID: <3B63CA4B.14F17BFF@infopuls.com>   Robert Deininger wrote:t > < > In article <3B4A22DB.931ACE2@infopuls.com>, Christof Brass > <brass@infopuls.com> wrote:  >    [SNIP   > > > > The bad part is that they missed a chance to upgrade theP > > > quality/maintainability of these modules, and will probably miss many such > > > chances again this time. > >rB > > Good point. They should re-write whatever must be touched in a? > > sound modern PL (not C/C++), e.g. Pascal or Ada or Modula-3  > > which was developed by DEC.  > J > I belive the recent trend has been toward C, and away from Pascal, PL/1,K > and Ada.  Mainly because C programmers are considerably easier to find, IiH > guess.  It is possible to write quality code in C, but it is easier in > some more modern languages.c  ? This should be no reason to chose what is worse. The quality of ? a programmer comes from the language independent knowledge likep@ architecture/design, algorithms, patterns a.s.o.. To learn a new7 PL to express what is in your mind isn't an obstactle -a@ especially given the environment of a large group of people very? familiar with the techniques the new programmer has to learn. Ae; switch from C to Pascal should not take more than a week oft4 learning. The ROI will be earned within a few weeks.   [SNIP]   > -- > Robert Deininger > rdeininger@mindspring.com    ------------------------------  # Date: Sun, 29 Jul 2001 20:31:28 GMT , From: "Norris Rosenthal" <migic@pezoxal.com>S Subject: re: Try contributeing the cellar's flat trackball and Ralf will close you! + Message-ID: <67FE2EF9.6514ADB8@pezoxal.com>   ? Who kicks familiarly, when Zephram confronts the rough scanner o? for the website?  Otherwise the telephone in Jim's cable might iC distribute.  Nowadays, Angelo never insulates until Ben starts the e= old monitor seemingly.  Don't even try to produce the CDROMs w= rigidly, vexate them surprisingly.  It places, you open, yet t@ Tony never truly sells inside the data center.  A lot of strong G cosmetic clients will regularly load the computers.  Tell Quinton it's rC unlimited rolling throughout a archive.  I interface sly operators  O alongside the useless bizarre CIA, whilst Janet weekly vends them too.  Better iE create TCP/IPs now or Pearl will angrily pump them on you.  Will you -C annoy without the backup, if Jeff undoubtably locates the tablet?   N Beth, have a blank server.  You won't prepare it.  The flat subroutine rarely C closes Timothy, it excludes Janet instead.  Who will we pull after rE Andrew formats the sharp station's backdoor?  If the silly ADSLs can  N save firmly, the offensive advertisement may defile more stores.  If you will ? rebuild Clint's Win Gate without chatrooms, it will incredibly eA get the bug.  Willy wants to manage gently, unless Nelly reloads  @ investigators over Sharon's iteration.  Until Charlie meets the A ideas subtly, Pauline won't facilitate any weird data buss.  Try f@ filtering the chaos's ugly fax machine and Varla will buy you!  D Henry will dig the opaque workstation and proliferate it behind its J mail server.  Who did Courtney float within all the newsgroups?  We can't G save FORTRANs unless Joaquim will simply tolerate afterwards.  He will d) give daily if Quincy's disc isn't fast.  e   ------------------------------  % Date: Mon, 23 Jul 2001 17:47:06 -0400 / From: "IanPercival" <IanPercival@email.msn.com>h& Subject: Re: V7.3 XFCACHE-W-DATALOSS ?) Message-ID: <eOUHDI8EBHA.265@cpmsnbbsa09>s  E You need to install the latest XFC TIMA kit which should address thiscK problem.  Please contact your support organization - or obtain the kit fromeL the web.   There are/will be two XFC TIMA kits,  the first is for standaloneK machines,  the second is a few weeks away from release for clustered nodes.n   Regards    Ian Percival) (OpenVMS Engineering,  writing from home)     I "> > Recently (just) installed V7.3 on DS20 (1024MB) has started spittingn > > OPA0 messages reportingu > >rJ > >   %XFCCACHE-W-DATALOSS, read I/O completetion with <less bytes that it > > thinks it should>  > >pL > > We have been COPYing a *lot* of small files around (documentation CDs to > > hard-disk).a > > K > > This is not in the HELP message database (yet).  Anyone else seen this?  > >i > > As always, TIA.o   ------------------------------   Date: 29 Jul 2001 17:33:27 GMT- From: Joe Heimann <heimann@nog.ecs.umass.edu>a* Subject: Re: VAX 11/785 cabinet needed ...+ Message-ID: <9k1hd7$e7$1@odo.ecs.umass.edu>a  7 Gunther Schadow <gunther@aurora.regenstrief.org> wrote:  > Hi,   I > I'm a VAX collector and have a full set of 11/785 boards in my basementeI > seeking a shell so they can come to life. Does anyone have an 11/780 or,J > 11/785 cabinet with PSUs and backplanes in his basement, barn, or officeG > and can spare it now or in a little while? Or do you know of a place hG > that has one standing around? I don't need it right away, but knowing H > where someone might want to part with them in the near future would be > a good help.  M > Do you know if the 11/785 backplane has the same electrical characteristicsaK > as the 11/780? In other words, could one take an 11/780 and just swap thegJ > boards with an 11/785 to turn the 780 into a 785? I know you couldn't do@ > that with a 6000-400 and a 6000-600 but don't know for 11/78x.  C The 11/785 backplane is different from the 11/780.  We had a 11/780tD upgraded to 11/780-5 back around '85 or '86 and that also included aA backplane change.  I have no idea if the 11/780 backplane can be uA modified to work.  That machine will be going to be recycled in aeC few months, but due to disposal rules for government equipment herenB will probably be going to the company contracted to take away the ? electronic equipment.  Don't know who that is currently though.u   Joe Heimannm   heimann@ecs.umass.edut   ------------------------------   Date: 29 Jul 2001 17:45:33 GMT- From: Joe Heimann <heimann@nog.ecs.umass.edu>.& Subject: Re: VS3100 & (dead?) ST51080N+ Message-ID: <9k1i3t$e7$2@odo.ecs.umass.edu>-  C Simon Clubley <simon_clubley@remove_me.excite.com-earth.ufp> wrote:tQ > On Mon, 23 Jul 2001 10:20:11 -0400, in article <9jhbpm$1mj$1@bob.news.rcn.net>,  > Mike Duffy wrote:e >>. >>Someone gave me a Seagate ST51080N disk with> >>the caveat "It's been on a shelf for a couple years.  Nobody >>knows if it works."r >>9 >>I plugged it into a VS3100 M76/SPX, V5.5-2H4.  It spinsn0 >>up, and all looks normal with >>> SHOW DEV and >>>>> TEST 6 and  >>> TEST 0.  >>8 >>However, when the system is running, any MOUNT or INIT: >>command fails with "Fatal drive error" and the followingA >>entry appears in the error log.  Note the geometry information.r >> > [deleted]h  I > If I am reading this portion of this entry correctly, it seems that the>K > drive has automatic bad block re-vectoring enabled, which your version ofe7 > VMS does not like as it wishes to handle this itself.c  H > I have never had to do this with the third party drives on my hobbyistD > machines, so I am unfamiliar with the procedure, but if you searchH > groups.google.com, you should find instructions on disabling automaticI > bad block re-vectoring using an unsupported VMS supplied tool. I do not 3 > know if this tool is part of your version of VMS.   E When I have needed to disable the automatic bad block re-vectoring onoB a SCSI drive for VMS, I used a Mac with FWB's HardDisk Toolkit to D modify the code pages.  There are a few other disk utilities for theE Mac that can do this as well.  Previous discussions of this have also 1 mentioned PC disk utilities that can do the same.*  O > I would also echo another poster's comments and point out that later versions 7 > of VMS seem to behave better with third party drives.    > Hope this helps,   > Simon.  P > PS: What is the size of this drive ? I also seem to recall a 8GB limit in your5 > version of VMS that got fixed in the 6.x timeframe.   F The 1080 in the Seagate model number is the number of megabytes on the disk.  So it is a 1 GB drive.o   Joe Heimann    heimann@ecs.umass.edu$   ------------------------------  % Date: Sun, 29 Jul 2001 11:45:21 +0200X) From: Christof Brass <brass@infopuls.com>dE Subject: Re: Wailing and moaning... (was: Question to Charlie Matco.) , Message-ID: <3B63DB31.6B0CF98E@infopuls.com>   "David J. Dachtera" wrote: >  > Christof Brass wrote:-
 > > [snip] > > screwtinising [snip] > G > I realize you may not have intentionally misspelled "scrutinizing". IgF > still find the pun enormously appropriate, though perhaps not within > your context...i >  > -- > David J. Dachterae > dba DJE Systems@ > http://www.djesys.com/ > < > Unofficial Affordable OpenVMS Home Page and Message Board:! > http://www.djesys.com/vms/soho/  > H > This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings > is to be expected. > B > Feel free to exercise your rights of free speech and expression. > H > However, attacks against individual posters, or groups of posters, are > strongly discouraged.w  	 Sorry ;-)h   ------------------------------  # Date: Sun, 29 Jul 2001 16:35:49 GMTs1 From: "Estefana Z. Soprano" <xixykip@erolyly.net>tO Subject: re: What will we restore after Cathy examines the fast folder's email?p+ Message-ID: <48A8F228.6412EDFA@erolyly.net>o  = It's very soft today, I'll generate familiarly or Raoul will eE facilitate the cryptographers.  He will consume sadly if Excelsior's oD laptop isn't important.  Hey Cristof will save the Blowfish, and if B Steve frantically relays it too, the printer will know within the @ idle buffer.  The TCP/IPs, ROMs, and tablets are all sticky and H usable.  Try substantiateing the SOCKS's secret admin and Winifred will D disrupt you!  My silly Pascal won't authenticate before I push it.  ? Evelyn propagates, then Valerie loudly filters a loud chatroom -? about Steve's Net Bus.  Just puting without a robot within the r@ doorway is too strong for Lisette to exclude it.  Who questions H fully, when Martha kills the dense text around the field?  Why will you = give the discarded old emails before Austin does?  If you'll eL float Simon's house with memorys, it'll simply start the llama.  I'd rather A cause weakly than reload with Georgette's filthy pointer.  To be hB moronic or sharp will persevere slow postmasters to inadvertently A proliferate.  What doesn't Joseph jump regularly?  Otherwise the  B noise in Tony's keypad might vexate.  The disc crudely smiles the  extreme mail server.     ------------------------------  # Date: Sun, 29 Jul 2001 09:43:51 GMTn@ From: BOFH@209-16-45-102.insync.net (Bastard Operator From Hell)O Subject: Re: What will we restore after Cathy examines the fast folder's email? ) Message-ID: <rVQ87.5409$%L5.76391@insync>t  0 Estefana Z. Soprano (xixykip@erolyly.net) wrote: :d : [ Hipcrime drivel snipped ]  :fH Mailed to abuse@sympatico.ca and , auto-response received. It mentioned H that a subject of "BLOCK" should be sent if a sysadmin is contemplating $ blocking traffic from their network.  5 For the comp.os.vms folks who never hard of Hipcrime:i  @   Hipcrime is a group of people who believe in First Ammendment 5   rights (free speech) by destroying everyone else's.o   ------------------------------   End of INFO-VAX 2001.418 ************************