1 INFO-VAX	Mon, 17 Apr 2000	Volume 2000 : Issue 215       Contents:+ Re: 36 Gb disk drive question (supported ?) 2 Anyone running IngresII V2.0 and Alpha VMS 7.1-2 ? RE: Availability ManagerH Booting, problems and professionals (Was : Re: DN-V L1 routing	 licence) Re: CXML and SETI  Re: CXML and SETI , Re: DECW$DEVICE-I-NODEVICE and no decwindows, Re: DECW$DEVICE-I-NODEVICE and no decwindows Re: DN-V L1 routing licence ! Re: Dropping DECnet..don't do it!  Re: ebay to drop Sun? + Re: Equivalent VMS command to Unix "touch"? 	 excursion  Re: FS: AlphaBook 2 Re: Galaxy (or perhaps Wildfire) and shared memory2 Re: Galaxy (or perhaps Wildfire) and shared memory+ Re: Highest OpenVMS version supporting VWS? K Re: How can you find the exact size of a file in bytes using a VMS command? J Re: How can you find the exact size of a file in bytes using a VMScommand? Re: how test the network ?P Re: how to communicate with CICS directly nor through CICS TransactionServer for) Re: How to map PCI configuration register  Re: HSJ80 experience? & monitor modes what do this stats mean?* Re: monitor modes what do this stats mean? Re: netscape 6+ Open source, was: re: So who will buy VMS ?  Re: RMS errors+ Re: Scheduler & PSDC alternatives, OT on CP  Security question  Re: Security question  Re: Security question  Re: So who will buy VMS ?  Re: So who will buy VMS ?  Re: So who will buy VMS ?  Software Update.& Re: Sun considers VMS a "mainframe" OS3 Re: UCX "SET NOHOST/NOCONFIRM" Wipes Out Host Table ( Re: Warning: circuitsurgeon is a ripoff!( Re: Warning: circuitsurgeon is a ripoff! Re: Web server for VAX/VMS Re: Web server for VAX/VMS8 Re: What are some reasons for different size executables8 Re: What are some reasons for different size executables8 Re: What are some reasons for different size executables6 Re: Why are there no French people in this newsgroup ? Re: XADRIVER documentation?   F ----------------------------------------------------------------------  / Date: Mon, 17 Apr 2000 09:49:08 +0200 (MET DST) & From: Rudolf Wingert <win@fom.fgan.de>4 Subject: Re: 36 Gb disk drive question (supported ?)/ Message-ID: <200004170651.IAA25790@fom.fgan.de>    Hello,   Marcin Szczecinski wrotes:   >>> ( > We did only see the following problem:6 >         (any arithmik error, may be divided by zero)  ? I can see the same problem, but have no idea how to resolve it.  Any suggestions? <<<   B Not at all. This is not a block count error. AFAIK it is a problemE of cylinder count (we do have the very old 5 1/4" Seagate disk, which C do work with OpenVMS. But the new one IBM 9.1DGHS did not. The only E difference is the geometry of both. Not the number of blocks.) or so.   8 We did not found any patch or solution for that problem.   Regards Rudolf Wingert   ------------------------------  % Date: Mon, 17 Apr 2000 05:48:28 -0700 @ From: John Cowell <john.p.cowellNOjoSPAM@btinternet.com.invalid>; Subject: Anyone running IngresII V2.0 and Alpha VMS 7.1-2 ? 9 Message-ID: <0e561dc0.6e532780@usw-ex0110-075.remarq.com>    Folks,  : we have a user who wants to run IngresII 2.0/9808 on Alpha: VMS. The box currently has VMS version 7.1-2 installed but9 the user has been told by CA that there are problems with ; this version of VMS and IngresII 2.0/9808. CA say that this : version of Ingres is OK with Alpha VMS 7.1 and 7.2 but not5 with 7.1-2. Anybody come across this before ? Anybody ; successfully running this combination ? For various reasons  we can't go to VMS 7.2.      Many thanks, John Cowell, 
 ICL A&TC, UK.    

* 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: 17 Apr 2000 19:51:14 +0200* From: eplan@kapsch.net (Peter LANGSTOEGER)! Subject: RE: Availability Manager * Message-ID: <38fb4f12$1@news.kapsch.co.at>  x In article <910612C07BCAD1119AF40000F86AF0D8052841FD@kaoexc4.kao.dec.com>, "Main, Kerry" <Kerry.Main@Compaq.com> writes:J >Availability Manager is not a traditional performance monitoring product,M >but rather a proactive tool which is targetted at identifying AND optionally > >fixing issues before they impact the production environment.   ! Isn't that the same for DECamds ?   K >Also note - "An important advantage of the Availability Manager is that it M >uses its own network protocol; unlike most performance monitors, it does not M >rely on TCP/IP or any other standard protocol. Therefore, even if a standard M >protocol is unavailable, the Availability Manager can continue to operate. "   ! Isn't that the same for DECamds ?   C btw: Does AM use the same protocol as AMDS, or only a similar one ?    >Btw - the cost is free.  ! Isn't that the same for DECamds ?    >Reference: : >http://WWW.OPENVMS.DIGITAL.COM/openvms/products/availman/G >http://WWW.OPENVMS.DIGITAL.COM/openvms/products/availman/AVAILMAN.HTML   * So, where's your point of DECamds vs. AM ?   --  < Peter "EPLAN" LANGSTOEGER           Tel.    +43 1 81111-2651; Network and OpenVMS system manager  Fax.    +43 1 81111-888 < FBFV/Information Services           E-mail  eplan@kapsch.netF <<< KAPSCH AG  Wagenseilgasse 1     PSImail PSI%(0232)281001141::EPLANH A-1121 VIENNA  AUSTRIA              "I'm not a pessimist, I'm a realist"N "VMS is today what Microsoft wants Windows NT V8.0 to be!" Compaq, 22-Sep-1998   ------------------------------  % Date: Mon, 17 Apr 2000 14:56:22 +0100   From: steven.reece@quintiles.comQ Subject: Booting, problems and professionals (Was : Re: DN-V L1 routing	 licence) > Message-ID: <802568C4.004CCC71.00@qedilc01.qedi.quintiles.com>  . VAXman (system at sendspamhere dot org) wrote:M >>>I strongly agree.  Whether licensing issues or simple configuration script I error, there is no reason the system should crash.  This particular crash I occurs during the boot and the machine required standalone booting to get 7 in to remove the configuration commands for routing.<<<   N But I've had at least one occasion where I was building and patching a clusterN (MC+NI+SCSI cluster, VMS V7.1-1H2) where one of the ALPSYS patches rendered myO clustered system unbootable with a cluster database corruption.  As the systems O were less than two days old I didn't even have the 24x7 support that I now have M in place.  To be fair though, although the person that answered the phone and N logged the call within Compaq told me that I would probably have to wait untilP Monday morning (it being about 9pm on Friday evening) I did get a call back from the local RDC that evening.   P Fortunately, by the time I got the call back I'd tried booting one of the AlphasP standalone (which worked since it wasn't loading the cluster database of course)P and then added the next patch on the FIS list (which was either the ALPSYSA02 orL ALPSYSB02, I forget which) which corrected the problem and let me boot up as3 normal, forming a cluster and then adding nodes in.    The moral of the story?   P We may gripe and moan when things like this happen (I know the air in my machineN room was blue) but at least we can get out of the situation.  I doubt that theK same could be said or done quite so easily with the New Tramp on the block. M Added to which we usually are sensible enough that even if we do log calls to N the local CSC we keepthinking about the problem after the call has been loggedP and can discuss a solution with the Compaq guys/girls when they call back.  This9 is why we think of ourselves as Professionals, after all.    Steve.   ------------------------------  % Date: Mon, 17 Apr 2000 10:59:02 -0400 , From: Steve Lionel <Steve.Lionel@compaq.com> Subject: Re: CXML and SETI8 Message-ID: <lg9mfs02nn816lckrhfc7oof0matjvduua@4ax.com>  2 On Sun, 16 Apr 2000 02:22:57 -0400, David A Froble <davef@tsoft-inc.com> wrote:    P >It would probably be counter-productive, but I'd like to see Compaq release theO >ultra fast SETI client.  It would then force the SETI people to decide whether ; >they wanted results, or are just another political entity.   C The SETI project does not want us to release the version of the 1.3 A client that uses CXML, and the rules are that 2.x clients are not F allowed to use vendor-supplied FFT routines - you have to use the code= as they supply it.  The SETI folks claim that the "science is @ compromised" if different FFT code is used.  Personally, I don't@ understand that, but it's their project and they get to make the rules.    - Steve Lionel (mailto:Steve.Lionel@compaq.com)  Fortran Engineering & Compaq Computer Corporation, Nashua NH  6 Compaq Fortran web site: http://www.compaq.com/fortran   ------------------------------   Date: 17 Apr 2000 15:18:30 GMT* From: helbig@astro.rug.nl (Phillip Helbig) Subject: Re: CXML and SETI. Message-ID: <8dfa06$bel$2@info.service.rug.nl>  g In article <lg9mfs02nn816lckrhfc7oof0matjvduua@4ax.com>, Steve Lionel <Steve.Lionel@compaq.com> writes:   + > The SETI folks claim that the "science is B > compromised" if different FFT code is used.  Personally, I don'tB > understand that, but it's their project and they get to make the > rules.  I It's probably more a case of "if we allow people to substitute their own  E code, we don't have the resources to make sure that it really is the  I same mathematically and numerically to within the interesting accuracy",  @ i.e. not compromised because it is "bad", but because it is not H something which they can personally vouch for if they had to.  Sure, in 6 an individual case, but this could be a Pandora's box.   ------------------------------  % Date: Mon, 17 Apr 2000 11:32:34 +0200 , From: Tony Champagne <tchampagne@genicom.be>5 Subject: Re: DECW$DEVICE-I-NODEVICE and no decwindows * Message-ID: <38FADA32.FF6A9766@genicom.be>   I wish it was just soo simple .  However it makes sence .  But doing a SET CONSOLE Graphics it returns ILL CMD .+ Help set console shows serial (1)or VGA (2) 5 So I tried set console 2 , Boot VMS and no DECWindows 6 Then tried set console 1, Boot VMS and no DECWindows .0 The error after the VMS boot is still the same .  ; Comments still welcome to get this machine up and running .   
 Luc Verhoelst    Fred Kleinsorge wrote:  N > This seems like an easy one... the DEC2000 is one of the few platforms whereN > the console was written by a group unfamiliar with the SRM and workstations.K > If you boot the system from the serial port, it configures the HW Restart G > Paramater Block to use a Type 2 Console Terminal Block - and does not F > connect the mouse and keyboard drivers.  No mouse & keyboard console > drivers, no DECwindows.  > K > This has been a restriction since the day the platform first shipped.  If M > you want to use the graphics, do a SET CONSOLE GRAPHICS followed by an INIT  > at the console.  > L > lucverhoelst@my-deja.com wrote in message <8cuvbl$a3q$1@nnrp1.deja.com>...1 > >I installed VMS 7.1 on a DEC2000 model 300 AXP I > >This was a Fresh install , including format of the disk and during the K > >installation the layered product DECWINDOWS was selected and installed .  > >  > >Rom version 2.2 > >SRM FW version 370 / > >Doing a show config on the boot prompt I see  > >1  ISA   VGA OK6 > >The installation completed all on the Blue screen .8 > >The VMS startup terminates correctly (job terminated)" > >but the DECWindows do not start/ > >On the end of the startup there is a message 4 > >DECW$DEVICE-I-Nodevice, no graphics devices found > > : > >The License for VMS and DW-Motif are loaded and active.# > >I can login on the OPA0: device.  > >Rund DECW$Configure I get > >Number of Screens 0" > >Screen devices and order : NONE > > $ > >Using MC SYSGEN> Windows_system 1 > > ) > >So the windows parameter is set to 1 .  > > # > >Any suggestions how to proceed ?  > >  > > ) > >Sent via Deja.com http://www.deja.com/  > >Before you buy.   ------------------------------  % Date: Mon, 17 Apr 2000 13:12:52 -0400 5 From: "Fred Kleinsorge" <kleinsorge@star.zko.dec.com> 5 Subject: Re: DECW$DEVICE-I-NODEVICE and no decwindows + Message-ID: <8dfgjv$ihm$1@lead.zk3.dec.com>   F Wow, it's that old that it still has that syntax.  Do a set console 2, followed by G a INIT command, and then when the >>> comes up on the VGA console, boot  from there.       A Tony Champagne wrote in message <38FADA32.FF6A9766@genicom.be>...   >I wish it was just soo simple . >However it makes sence . ! >But doing a SET CONSOLE Graphics  >it returns ILL CMD . , >Help set console shows serial (1)or VGA (2)6 >So I tried set console 2 , Boot VMS and no DECWindows7 >Then tried set console 1, Boot VMS and no DECWindows . 1 >The error after the VMS boot is still the same .  > < >Comments still welcome to get this machine up and running . >  >Luc Verhoelst >  >Fred Kleinsorge wrote:  > I >> This seems like an easy one... the DEC2000 is one of the few platforms  where A >> the console was written by a group unfamiliar with the SRM and 
 workstations. L >> If you boot the system from the serial port, it configures the HW RestartH >> Paramater Block to use a Type 2 Console Terminal Block - and does notG >> connect the mouse and keyboard drivers.  No mouse & keyboard console  >> drivers, no DECwindows. >>L >> This has been a restriction since the day the platform first shipped.  IfI >> you want to use the graphics, do a SET CONSOLE GRAPHICS followed by an  INIT >> at the console. >>, >> lucverhoelst@my-deja.com wrote in message  <8cuvbl$a3q$1@nnrp1.deja.com>...2 >> >I installed VMS 7.1 on a DEC2000 model 300 AXPJ >> >This was a Fresh install , including format of the disk and during theL >> >installation the layered product DECWINDOWS was selected and installed . >> > >> >Rom version 2.2  >> >SRM FW version 3700 >> >Doing a show config on the boot prompt I see >> >1  ISA   VGA OK 7 >> >The installation completed all on the Blue screen . 9 >> >The VMS startup terminates correctly (job terminated) # >> >but the DECWindows do not start 0 >> >On the end of the startup there is a message5 >> >DECW$DEVICE-I-Nodevice, no graphics devices found  >> >; >> >The License for VMS and DW-Motif are loaded and active. $ >> >I can login on the OPA0: device. >> >Rund DECW$Configure I get  >> >Number of Screens 0 # >> >Screen devices and order : NONE  >> >% >> >Using MC SYSGEN> Windows_system 1  >> >* >> >So the windows parameter is set to 1 . >> >$ >> >Any suggestions how to proceed ? >> > >> >* >> >Sent via Deja.com http://www.deja.com/ >> >Before you buy.  >    ------------------------------  # Date: Mon, 17 Apr 2000 10:18:58 GMT = From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-) $ Subject: Re: DN-V L1 routing licence0 Message-ID: <009E8BBD.473636E0@SendSpamHere.ORG>  l In article <200004162231_MC2-A16C-1D20@compuserve.com>, "Richard B. Gilbert" <DRAGON@compuserve.com> writes:
 >{...snip...}  > K >        A bugcheck is not an acceptable response to any kind of licensing=  > C >problem or to having two Ethernet adapters configured or . . . . =   J I strongly agree.  Whether licensing issues or simple configuration scriptI error, there is no reason the system should crash.  This particular crash J occurs during the boot and the machine required standalone booting to get 4 in to remove the configuration commands for routing.   --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: Mon, 17 Apr 2000 08:52:24 GMT 0 From: carlini@true.lkg.dec.com (Antonio Carlini)* Subject: Re: Dropping DECnet..don't do it!* Message-ID: <8deips$kuv@usenet.pa.dec.com>  Q In article <Ft02M3.FE4@spcuna.spc.edu>, Terry Kennedy <terry@gate.tmk.com> wrote:   K >  As someone else pointed out, there isn't any reason Compaq couldn't have ( >made their version work under Phase IV.   True - it's just code right :-)   M Getting the RFC859 support into Phase IV would be a tad hard as Phase IV has  K no OSI Transport. Getting something compatible with Phase/IP (or whatever)  N into DECnet Phase IV would be technically possible (I imagine). The stumbling 4 block will be finding someone willing to pay for it.
               # > It can't be that hard (I remember L >when DECnot / Phase/IP was born, Ken Adelman from TGV called me up and said9 >"Hey, I've got this really neat hack, wanna try it?" 8-)   K All new features are trivial to implement once you've finished writing and 7J testing the code. Is the Phase/IP stuff even publically documented? Could 9 COMPAQ add it to Phase IV without having to pay whomever?L   >SJ >  I suspect that the Compaq Phase IV code is only touched to fix criticalJ >bugs, and they don't want to make enhancements to it. Not to mention that1 >Phase IV improvements would undermine Phase V...V  J I believe the Phase IV code is in maintenance mode. I'm sure if you offer L enough money someone will crack the seals and start working on it. I bet it N would be cheaper for you to simply purchase whatever product it is that gives 
 you Phase/IP.a  L In defence of the DECnet-over-IP stuff: it is all publically documented (in K the above RFC) and it works over any IP stack that uses the "standard PWIP uN interface" (I don't know what it is called). It needs OSITP which pretty much  precludes Phase IV ...   AntonioS  I Antonio Carlini                            Mail: carlini@true.lkg.dec.comh# DECnet-Plus for OpenVMS Engineering66 COMPAQ                                     Reading, UK   ------------------------------  % Date: Mon, 17 Apr 2000 15:16:27 +0100eB From: Andrew Harrison SUNUK Consultancy <andrew.nospam@uk.sun.com> Subject: Re: ebay to drop Sun?* Message-ID: <38FB1CBB.ECCCEC83@uk.sun.com>   Arne Vajhj wrote:  * > Andrew Harrison SUNUK Consultancy wrote:E > > The Sun number is old, using old slower Sun CPU's, an E10000 with G > > a slower backplane and longer latency than the current machine, old B > > storage, an old version of Informix and an old version of SAP. > >uB > > The GS320 ran a new version of Oracle, SAP etc and hasn't been2 > > released yet, hardly a meaningfull comparison. > >eH > > Incedentally the Fujitsu box that is ahead of the GS320 is basicallyA > > an E10000 clone, it uses SPARC CPU's, runs Solaris, its CPU's-D > > are almost identical in performance as the E10000's and it has a* > > similar cross-bar switch architecture. > >:D > > So you conclusions are that a yet to be released Alpha server isB > > slightly slower than currently available SPARC/Solaris system. >  > ???? > H > Can we agree on that assumptions/guesses/estimates etc. are completely	 > useless & > when it comes to benchmark results ? >aD > Assumptions that newer E10K's are faster than the older E10K's and? > that the Fujitso is "almost" identical etc. are just hot air.w >o  C Wow, a person who doesn't realise he is in a glass house armed withu a brick.  > Why not email Kerry and point out to him that all his Wildfire performance . posts amount to exacly what you accuse Sun of.   >tF > If you have a faster E10K, then do a new benchmark test and prove it, > instead of assuring us that it is faster ! >:  F Incedentally we do have a faster E10K and we did benchmark it, we just didn'tG bother doing the benchmark for the 2 tier version of the benchmark just0H for the 3 tier. The reasons for doing the 3 tier benchmark in preference toH the 2 tier one will be obvious to anyone who has any experience of large SAP deployments.   The results:  ,                     Old E10K        New E10K% SAP SD     14,400              19,3600  . The old result used SAP R/3 3.1 the new result3 used 4.0B which requires quite a lot more resource.d  2 So yes we have benchmarked the old and the new and yes the new is faster.  3 As for the Fujitsu, their CPU's are almost the samey4 speed as Sun's according to their SPECint95 results,7 their backplane architecture is very very similar, theyi4 use the same OS, we have customer who have run their6 own apps and they deliver almost identical throughput.  0 So why what would be the basis of anyones claims1 that the Fujitsu is a much faster system than the: E10K ?   Regardse Andrew Harrison3 Enterprise IT Architecta   ------------------------------  % Date: Mon, 17 Apr 2000 13:35:57 +0200c= From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com>t4 Subject: Re: Equivalent VMS command to Unix "touch"?) Message-ID: <38FAF71D.32F52EA9@gtech.com>h  " "Guttenberg, Charlie (MED)" wrote:I > I'm want to be able to update the last-modified dates of all files in as > directory.A > Unix provides the "touch" command for this.  Does VMS provide av > counterpart?  
 Not directly.u   But many workarounds exist.n    See the following link for some:  * http://www.levitte.org/~ava/tip/touch.html   Arne   ------------------------------  % Date: Mon, 17 Apr 2000 13:49:15 -0400i+ From: "Bob Ricci" <maxx0623@concentric.net>' Subject: excursion< Message-ID: <000401bfa895$40fc4010$585b5cc0@socrates.Subway>  K Does anyone have compaq's excursion 3.0 for windows nt 4.0 running and ableaI to connect to a Sun solaris 2.6 server. I keep gettingan error adding thea	 font patht- couldnt add font path /etc/dt/config/xfonts/Ca;                                     /usr/dt/config/xfonts/C 5                                    tcp/cliff.com:7100 D it then brings up the CDE desktop to Solaris asking for username and+ password but doesnt recognize the password. & i must have an invalid path somewhere!	 bob riccil ricci_r@subway.com   ------------------------------   Date: 17 Apr 2000 13:06:14 GMT* From: helbig@astro.rug.nl (Phillip Helbig) Subject: Re: FS: AlphaBook. Message-ID: <8df286$92g$1@info.service.rug.nl>  < In article <38FA753D.45BD6979@triton.com.no.spam>, Jay Olson! <jjo@triton.com.no.spam> writes: c  G > After several years of devoted service, I am now selling my AlphaBook	* > (and will tote around a DS10L instead).   H Now there's an idea!  I always wanted an ALPHABOOK, although the non-LK A keyboard was a disadvantage.  Surely it can't be technically too iI difficult to hook up a DS10L to a laptop-type screen and (perhaps even a pH proper) keyboard, and thus come up with a VMS laptop!  Expensive in the G sense that the DS10L is expensive, but as it is based on the DS10L and <G is not a custom job, perhaps there is the possibility to get something gA at a reasonable price.  Of course, a lot more power than the old S ALPHABOOK as well.   ------------------------------    Date: 17 Apr 2000 17:17:46 +0200G From: Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de>u; Subject: Re: Galaxy (or perhaps Wildfire) and shared memoryhH Message-ID: <y4aeisiwo5.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>  ) "Bill Todd" <billtodd@foo.mv.com> writes:l  K > In particular, if an MB write-flush causes data to be written all the wayrN > back to main memory, thus completely eliminating inter-partition connectionsI > at any cache level (of the kind that exist in some SMP architectures tonG > allow inter-processor data-sharing without the latency of main-memory L > accesses), then my concern that inter-cache connections between processorsG > executing in different partitions might compromise fault-isolation issM > groundless:  the only inter-partition connection will be through the sharedmE > memory itself, which will presumably pass along any necessary cachesL > invalidations as write activity occurs (though my understanding of exactlyH > how this occurs is regrettably fuzzy), and the hardware connecting theI > caches to main memory is presumably already sufficiently robust to keep D > local faults from affecting access by others to any shared memory.  L As I understand how a Wildfire system works, that is however not the case inN general: it is using a directory-based M(O)ESI scheme, isn't it? In that case,H at least some memory operations "reach through" into another processor'sM caches, with the processor possibly belonging to a different instance, unless D the properties, with respect to coherence and sharing, of the memoryI constituting the shared properties make that impossible - which, I'd say, J implies making them not-cached, as Bill has been saying all along. In thisK scenario, I have always thought of Byzantine failure modes as the ones that L make life worrisome, and the worry here is that both hardware _and_ software might behave in such a way.   - Is Leslie Lamport still with DEC^H^H^HCompaq?s   Jan,   ------------------------------   Date: 17 Apr 2000 15:24:59 GMT* From: helbig@astro.rug.nl (Phillip Helbig); Subject: Re: Galaxy (or perhaps Wildfire) and shared memoryn. Message-ID: <8dfacb$bel$4@info.service.rug.nl>  H In article <y4aeisiwo5.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>,A Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de>q writes:   / > Is Leslie Lamport still with DEC^H^H^HCompaq?s  E http://www.research.digital.com/SRC/personal/Leslie_Lamport/home.html-   ------------------------------  % Date: Mon, 17 Apr 2000 13:04:44 -0400t5 From: "Fred Kleinsorge" <kleinsorge@star.zko.dec.com> 4 Subject: Re: Highest OpenVMS version supporting VWS?+ Message-ID: <8dfg59$dck$1@lead.zk3.dec.com>x  I As far as I know, this is all supported by Touch Technologies.  I have noaI idea of it's status, but believe the support had extended past V7.1.  VWSrH itself runs only on older VAX based workstations.  The X11 stuff, calledH UISX, runs on any VAX, and rumour has it on Alpha (I had done an initial5 port of it just for yucks before it was sent to TTI).r   _Fredk    A Joseph Huber wrote in message <8d7dl8$2pli$1@kiosk.rzg.mpg.de>...w/ >In Article <200004140510.HAA29039@fom.fgan.de>r) >Rudolf Wingert <win@fom.fgan.de> writes:i >>Hello,G >>all the previous answers are incorrect. AFAIK the latest VMS version,n whichdI >>supports the VWS (VAX workstation software), was V5.3. But there was an-G >>migration pakage, which allowed to use VWS with DECwindows Motif. HowpE >>long this supports VWS, I don't know, because we changed all appli- 1 >>cation software with the migration tool to X11.i >i@ >This might be true for the "official support", but it just runs3 >without the Motif-migration package "unsupported":n >e6 >OpenVMS V7.2  on node MPIW11  14-APR-2000 17:24:13.69G >  Pid    Process Name    State  Pri      I/O       CPU       Page fltsE Pagess >    ...G >2D400067 VWS$DISPLAYMGR  HIB      7      128   0 00:00:02.47       631e 390s' >$ remote mpiw11 mcr sysgen show windowsL >WINDOW_SYSTEM                   2          0         0         2 Pure-numbe Dn# >                               ^^^o >This is VWS, not DECW.o >uI >We do run only one application program, and are just happy it works, who  knows. >--i0 >Joseph "Sepp" Huber,MPI Physik,Muenchen,Germany: >huber@mppmu.mpg.de  URL http://wwwvms.mppmu.mpg.de/~huber   ------------------------------  # Date: Mon, 17 Apr 2000 12:11:13 GMTr From: briggs@eisner.decus.orghT Subject: Re: How can you find the exact size of a file in bytes using a VMS command?' Message-ID: <2000Apr17.081113.1@eisner>   I In article <8dcl1l$k0$1@nnrp1.deja.com>, Rick <rw712@my-deja.com> writes:e@ > The reason I asked the question was to determine if a file wasD > transfered to a VMS box correctly using FTP. It was an Oracle dumpF > file, and the individual transfered the file using ASCII mode. Well,H > that did a bit of translation on it's own, which would modify the fileH > (such as converting CRNL to NL), but not so much as to change the sizeH > of the file by a number of blocks. How could I tell easily if the fileI > had been altered? Oh, I did not expect this person to transfer a binarywH > file use text mode... It took quite a while to figure out that was the0 > cause of the odd messages in loading the dump.  H Hindsight being 20/20, the first sanity check should have been to verifyF that the resulting file was fixed-512 with null carriage control, thusM making pretty sure that a binary transfer was used.  My FTP client (Multinet)tI produces files of variable length records when pulling toward VMS with antH ASCII transfer and files with 512 byte fixed length records when pulling with binary transfers.  K Given that the resulting file is fixed-512, one can compute the file "size"r< in bytes by checking F$FILE_ATTRIBUTES("filename","EOF") and$ F$FILE_ATTRIBUTES("filename","FFB").   If FFB = 0 then size = EOF*512' If FFB != 0 then size = (EOF-1)*512+FFBd  G Given that the resulting file has variable length records with carriagecF return carriage control, the only way to compute the file length is toC scan it sequentially.  $ SEARCH /STAT is one way to do the requiredc scan..  A If the source file was on a Unix platform then the file "size" istG ( total length of all records + total number of records ).  For example   ! $ SEARCH /STAT TEST.TXT "" /WIN=0e" DISK1420:[VAXS09.V7.RFC]TEST.TXT;1  E Files searched:                 1       Buffered I/O count:         7eE Records searched:               3       Direct I/O count:           1mE Characters searched:           12       Page faults:               17lH Records matched:                3       Elapsed CPU time:  0 00:00:00.01H Lines printed:                  3       Elapsed time:      0 00:00:00.02   12 + 3 = 15 bytes in this case.o  & 	John Briggs			briggs@eisner.decus.org   ------------------------------  % Date: Mon, 17 Apr 2000 13:38:09 +02002= From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com>dS Subject: Re: How can you find the exact size of a file in bytes using a VMScommand?T) Message-ID: <38FAF7A1.E9F67AF1@gtech.com>e   Rick wrote: D > Sorry to ask such a stupid question, but I have been searching andG > connot figure it out. I want to know the exact size (number of bytes).A > of a(ny) file in VMS? Is it possible or is the finest degree ofl > granularity a block?  ' The information about bytes are stored.l  F The DIRECTORY command can not display it, but there are other methods.  1 F$FILE_ATTRIBUTES with items EOF and FFB are one.>   Arne   ------------------------------  / Date: Mon, 17 Apr 2000 10:36:29 +0200 (MET DST)I& From: Rudolf Wingert <win@fom.fgan.de># Subject: Re: how test the network ?r/ Message-ID: <200004170739.JAA27335@fom.fgan.de>(   Hello,  I my favorit simple test is DTSEND. With this test I found often the reasonhI for worse network performance. One problem was the NIC. Sometimes the NIC>H produces slow performance without any reason. If it is only one NIC withF slow performance, change the NIC (call service). Also do play with theG PIPELINE QUOTA under DECnet IV. Sometimes less quota will get more per-SH formance. What network do you have? If you will have a switched network,D how is the switch configured. If you will see during DTSEND test oneF error for every pakage, may be the flow control of the switch is miss- configured.-  D I did see in a TCP/IP Release Notes that there is also a TCP/IP test4 tool. Also do some switches have Rmon functionality.   Regards Rudolf Wingert   ------------------------------  # Date: Mon, 17 Apr 2000 07:55:23 GMTM% From: "P.Lj" <plj@byron.ext.telia.se>BY Subject: Re: how to communicate with CICS directly nor through CICS TransactionServer fora2 Message-ID: <38FAC325.93E6A8DA@byron.ext.telia.se>   Hi  H I've heard of a case where it was impossible to get a working connectionB between two IBM-machines, a VAX between them fixed the problem and Digitals communication softwaret   /P.Lj    Roger Barnett wrote:  < > Depending on what you actually want to do, you may be able  > to use a CORBA-based approach. >c  > Try Iona   http://www.iona.com0 > or check the OMG web site   http://www.omg.org2 > for other companies that support CICS platforms. >  > -- > Roger Barnettl   ------------------------------  % Date: Mon, 17 Apr 2000 13:00:28 -0400a5 From: "Fred Kleinsorge" <kleinsorge@star.zko.dec.com>l2 Subject: Re: How to map PCI configuration register+ Message-ID: <8dffso$96f$1@lead.zk3.dec.com>@  K If you are trying to read/write PCI configuration space, you are better offr< using the services designed for it:  ioc$read_pci_config andH ioc$write_pci_config.  You should be able to find this documented in the driver book by Margie Sherlock.d  I You will need to be in kernel mode, and have a pointer to the ADP for thea@ PCI bus you are trying to access, and the slot number (actually,J crb$l_node).  You probably want the PCI 2.1 specification, or at least the5 devices documentation on it's config space registers.   I These calls are typically done from a driver, which already has access tomJ the ADP and CRB.  But I suppose someone with a slight amount of work could9 do it from an application (with a change mode to kernel).i   _Fred     0 Carl Gunnar Linden, MSL Sweden. wrote in message  <009E8976.923D19AC.55@msi.se>...  G    Does anyone know how to use the system service routine SYS$CRMPSC toaI map the configuration register of a device on the PCI-bus in a PWS 500au?   K    Is there any documentation available concerning the hardware of the PWS?    ------------------------------  # Date: Mon, 17 Apr 2000 15:37:17 GMTn, From: kaplow_r@eisner.decus.org (Bob Kaplow) Subject: Re: HSJ80 experience?' Message-ID: <2000Apr17.113717.1@eisner>n  S In article <38F5197C.EE02CD2E@mediaone.net>, Ed Wilts <ewilts@mediaone.net> writes:rJ > The CI is propietary technology but you can purchase a license to do theF > same things the HSJ does.  I ran a pair of CMD Hawks for a while andF > they were rock solid.  While the early HSJ-40 controllers were being  + Ever check the CIPCA? They are made by CMS.i  I > replaced every 6 months or so, the Hawks just kept on going and going. iJ > They'd both run over 3 years without a hardware call when I left my lastJ > job.  MTI also makes CI-SCSI controllers, but the ones we evaluated wereF > absolute crap and I wouldn't even recommend them to my competition. I > Others have somewhat satisfactory experiences with MTI, but others have.H > also had experiences like mine (watch your cluster hosts crash).  OursD > were thanfully evaluation units which we obviously returned to theJ > vendor.  CMD has since come out with newer CI controllers to replace the2 > Hawks but I don't know what they've done lately.  D We had mixed success with the MTI Stingrays. We got them because the= HSC95/K.SCSI combination was junk. They've had assorted minor L incompatabilities, but never kept up with the times. We had to have seperateI stars for HSJ and MTI, as they had some nasty interactions. Finally, theyhI weren't even cost competitive with DEC. We're still running one as a tapes server, the rest got scrapped.   	Bob Kaplow	  E SPAM:	spamrecycle@ChooseYourmail.com	uce@ftc.gov	postmaster@127.0.0.1t   ------------------------------  # Date: Mon, 17 Apr 2000 12:16:05 GMTr From: joecarlos@yahoo.com (Joe)c/ Subject: monitor modes what do this stats mean??5 Message-ID: <8F1955027joeyahoocom@news.supernews.com>m  1                           OpenVMS Monitor Utility 4                             TIME IN PROCESSOR MODES ,                                  on node joe3                             17-APR-2000 08:14:32.68h  L                                        CUR        AVE        MIN        MAX   K     Interrupt State                   0.66       1.32       0.00       9.00e  K     MP Synchronization                0.00       0.00       0.00       0.00h  K     Kernel Mode                       1.66       7.62       0.00      58.00r  K     Executive Mode                    0.66       4.49       0.00      28.33d  K     Supervisor Mode                   0.66       0.12       0.00       3.00s  K     User Mode                        96.00       8.22       0.00      99.00n  K     Compatibility Mode                0.00       0.00       0.00       0.00e  K     Idle Time                         0.00      78.20       0.00     100.00                     Thanks!   ------------------------------  # Date: Mon, 17 Apr 2000 14:16:33 GMTe From: cd_root@my-deja.come3 Subject: Re: monitor modes what do this stats mean?b) Message-ID: <8df6bk$mdu$1@nnrp1.deja.com>   A Unless you're diagnosing a problem that is happening *right now*,yE concentrate on the AVG column over a period of time.  The information C presented is a snapshot of what is seen during the MONITOR session.s jc    5 In article <8F1955027joeyahoocom@news.supernews.com>,t"   joecarlos@yahoo.com (Joe) wrote:3 >                           OpenVMS Monitor Utility 5 >                             TIME IN PROCESSOR MODESr. >                                  on node joe5 >                             17-APR-2000 08:14:32.685 > 7 >                                        CUR        AVEj MIN        MAX >c7 >     Interrupt State                   0.66       1.32D 0.00       9.00E >g7 >     MP Synchronization                0.00       0.00a 0.00       0.00u >tB >     Kernel Mode                       1.66       7.62       0.00 58.00  > B >     Executive Mode                    0.66       4.49       0.00 28.33t >u7 >     Supervisor Mode                   0.66       0.12k 0.00       3.00p >wB >     User Mode                        96.00       8.22       0.00 99.00- > 7 >     Compatibility Mode                0.00       0.00  0.00       0.00r >nB >     Idle Time                         0.00      78.20       0.00 100.00 >S >                  Thanks! >a    & Sent via Deja.com http://www.deja.com/ Before you buy.n   ------------------------------   Date: 17 Apr 2000 17:42:57 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) Subject: Re: netscape 6 6 Message-ID: <8dfif1$f6k$1@mailint03.im.hou.compaq.com>  C   The product probably to be known as Netscape 6 is expected to be  A   available for OpenVMS Alpha, and will be based on the existing oH   Mozilla series of baselevels presently available -- the M15 baselevel '   is due out within the next day or so.-  H   The Netscape version of Mozilla adds some features that are presently H   lacking -- central among these are specific security-related features.  H   No OpenVMS VAX version of Mozilla nor of the Mozilla-related Netscape     browser is presently expected.   F   I will be posting an update on this topic in the next edition of theG   OpenVMS FAQ.  (I need to update the details of this topic in the FAQ  E   if for no other reason than to update the release schedule data...)d  E   There is a Mozilla FAQ being added to the OpenVMS website, as well.1  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Mon, 17 Apr 2000 13:48:06 +0000 / From: Nigel Arnot <sysmgr@maxwell.ph.kcl.ac.uk>l4 Subject: Open source, was: re: So who will buy VMS ?7 Message-ID: <009E8BFC.05FDA5DF.22@maxwell.ph.kcl.ac.uk>a   > Nigel Arnot wrote: > >  > <big snip> > # > > or (b) if they have to go Unix,uH > > they'll go Linux and never be held to ransom by an O/S vendor again, > H > But then they'd be held ransom by whomever they depend upon for Linux : > support (a very nebulous entity) and no, I won't accept $ > the statement thatit's open source< > and they can 'do it themselves'.  Working on an operating  > system is not the sameO > as working on an application system, and many shops cannot even do that well.a >   ; The big difference is that there's no source-code monopoly.l  K If you get trouble with NT, you rely on Microsoft for a fix (or on whatevern< entities Microsoft is willing to share the source code with)  E If you get trouble with VMS or Tru64, you rely on Compaq for a fix. I C trust Compaq rather more than Microsoft, but it's still a monopoly.r  < With Linux, there are many competing organisations providingG support. If you get trouble with one of them, you can fire them. In the J last resort, you can tackle it in-house or hire a contractor to fix it forL you. You can't ever find that your next years support contract is a lot moreJ than you'd budgeted, and that your only other choice is going unsupported.  E Certainly, it's an utterly different culture to a commercial O/S, buta it seems to work.O  + > Dave, who has serious doubts about Linux.s  @ So did I, to start with. I didn't find anything to confirm them.  I My Redhat servers haven't suffered any unprovoked crashes in nearly threehI years now, across four releases. I've yet to experience any problems thatuL didn't already have public-domain solutions when I looked for them. And I'veH had less problems than I had with Ultrix and HPUX (as of 3-5 years ago).  K Main thing wrong with Linux is that it's not VMS. But then, VMS isn't free.    	Yours,a
 		Nigel Arnotr- 		NRA@MAXWELL.PH.KCL.AC.UK                   e  7 		"In the beginning there was nothing, which exploded."H   ------------------------------  # Date: Mon, 17 Apr 2000 15:48:21 GMT  From: cd_root@my-deja.coma Subject: Re: RMS errorsi) Message-ID: <8dfbnu$srp$1@nnrp1.deja.com>e  ? You need to find the NEXT data bucket after 447472 (it *may* be>D 447472+21 == 447483).  Use ANALYZE/RMS/INTER and POSI/BUCKET to findF out.  Then patch the PREVIOUS bucket (it *may* be 447472-21 == 447451)A and make it's NEXT bucket be 447483 (or whatever is appropriate). 
 Good Luck! jc  / In article <38F60BC4.9329DC32@nc.prestige.net>,m1   Michael Austin <maustin@nc.prestige.net> wrote:1. > This is a multi-part message in MIME format.( > --------------ABC54902C11C5D1E9318FFB3, > Content-Type: text/plain; charset=us-ascii! > Content-Transfer-Encoding: 7bit3 >cE > Getting closer... I finally figured out that the data bucket begins.! at VBN 447472 and is 21 blocks inbD > size.  VBN 447475 is all 0's (looks like a BBR). Now,  within this# VBN it contained 14 record that areeE > parts of an index.  What do I need to patch in order to "skip" thisI& block of data?   How do I get the lastC > record in VBN 447474 to jump to 447476 or would that be too easy.e! Bucket at VBN 239914 contains thegD > pointers to VBN447475  How would I correct these?  I logged a call# with RMS support but have not heard  > back from them yet.v >sD > How do you use zap to correct these issues?  I couldn't figure out how to enter new data.  Thanks.t >e > Thanks again.t >e > hein@eps.zko.dec.c*m wrote:h > B > > In article <38F53D61.B60BEEA0@nc.prestige.net>, Michael Austin# <maustin@nc.prestige.net> writes...d1 > > >This is a multi-part message in MIME format.t+ > > >--------------39844262B9DCD08AFBB9C658 / > > >Content-Type: text/plain; charset=us-asciie$ > > >Content-Transfer-Encoding: 7bit > > > D > > >After patching the CHECK byte, I was able to most of it to come back > >  > >         Cool!  > > 2 > > > (VBN 447472). There is still a severe error: > > >AG > > >***  VBN 447472:  Key and/or data bytes do not fit in primary dataw record.s: > > >Unrecoverable error encountered in structure of file. > > G > > probably a similar cause as the check byte, a partial bucket write,TH > > but this time making a compress record run into random data, causing > > rms to loose track.h > >n< > > >How do you  know what the CHECK BYTE is supposed to be./ > > > In one copy of the file the check byte isdD > > > 25, in the corrupt one it was 27.  I know the check byte is in$ the first long word in the VBN, from8 > > >where does it get the byte that it compares it too? > >i@ > > The very last byte. Both are updated each time the bucket is updated.F > > Use ANA/RMS/INT pos/buck to read, of the 'zap' tool. (i'll include it here) > >IG > > >I was unable to determine why all the problems with VBN 239914 (85  errors). > >sA > > >***  VBN 238822:  Record at offset %X'1573' has a missing ore illegal RRV. > >C+ > > Well, I'd probably switch to plan B ...oF > > Look's like that bucket wants it NEXT FREE byte to be set to x1573 :-).E > > Actaully, the 'tail' of the previous record is proably brokn, ando youHE > > probably want to set the free byte one record before the reportedx place. > >s > > ;rF > > ; Simplistic tool to Read, Verify, Modify and Rewrite Indexed file buckets. > > ;e= > > ; Main use is to PATCH remote or very large indexed file. 2 > > ; as it reads & writes only the blocks needed. > >e) > > ; Have fun, Hein van den Heuvel, 1985 D > > ; 1996: Add Next, Size, and X command. Default first bucket from
 XAB$L_DVB. > > ; 	 > > cr=13(	 > > lf=10 $ > >         .PSECT  help,noexe,nowrt > > help:   .ASCID  <cr><lf>-h > > / > > "       ##   read VBN ##."<cr><lf><cr><lf>-t; > > "       X    followed by hexadecimal number to read VBNt
 ##."<cr><lf>-l@ > > "       S    followed by number to set bucket size = size to read."<cr><lf>-B? > > "       D    to get into the debugger. Bucket pointed to by 
 R2."<cr><lf>-e9 > > "       GO   While in the Debugger to get back to the  prompt."<cr><lf>-s@ > > "       W    Write out the bucket (back at prompt)"<cr><lf>-9 > > "       F    format data as bucket header for indexedo file."<cr><lf>-i? > > "       <CR> reads next (or first) bucket."<cr><lf><cr><lf>f > >s" > >         .PSECT  code,exe,nowrt > >         .ENTRY  START, ^M<>e  > >         PUSHAL  FILENAME_SIZ# > >         PUSHAQ  FILENAME_PROMPTR > >         PUSHAQ  FILENAME) > >         CALLS   #3, G^LIB$GET_FOREIGN ? > >         MOVB    FILENAME_SIZ, FAB+FAB$B_FNS     ;Insert the 
 filename sizedH > >         $OPEN   FAB=FAB                         ;Open the input fileC > >         BLBC    R0, BYE                         ;See you later!:= > >         CMPB    FAB+FAB$B_ORG, #FAB$C_IDX       ;Indexed?  > >         BNEQ    10$ @ > >         MOVAL   XAB, FAB+FAB$L_XAB              ;Hook up Xab@ > >         $DISPLAY FAB=FAB                        ;Fill in XabC > >         BLBC    R0, BYE                         ;See you later! A > >         MOVL    XAB+XAB$L_DVB, NEXT_BUCKET      ;Start bucketRH > >         MOVZBL  XAB+XAB$B_DBS, BUCKET_SIZE      ;Pick up bucket size< > > 10$:    $CONNECT RAB=RAB                        ;Connect? > >         BLBS    R0, SET_SIZE                    ;Go for it!a > >         MOVL    R0, R10 C > > DONE:   $CLOSE  FAB=FAB                         ;Close the fileS@ > >         BLBS    R10, BYE                        ;Last status > >         MOVL    R10, R0y > > BYE:    RET  > > E > > SIZE:   INCL    VBN+4                           ;Skip S character$ > >         DECW    VBNs5 > >         PUSHAL  BUCKET_SIZE                     ;-@ > >         PUSHAL  VBN                             ;INput againA > >         CALLS   #2, G^OTS$CVT_TU_L              ;Convert fromr decimals  > >         BLBS    R0, SET_SIZE! > >         PUSHAQ  CONVERT_ERRORs > >         BRW     GIVE_ERROR > > DONE1:  BRW     DONE
 > > SET_SIZE: D > >         ASHL    #9, BUCKET_SIZE, R0             ;Multiply by 512H > >         MOVW    R0, RAB+RAB$W_USZ               ;Set up size of read > > MAIN_LOOP:@ > >         MOVL    RAB+RAB$L_STS, R10              ;exit statusA > >         MOVL    #VBN_LEN, VBN                   ;Init len  ine
 descriptorA > >         MOVAL   VBN_BUF, VBN+4                  ;Init addr ini
 descriptorG > >         PUSHAQ  VBN                             ;Output LEN back ine
 descriptor; > >         PUSHAQ  VBN_PROMPT                      ;PromptT; > >         PUSHAQ  VBN                             ;Bufferl; > >         CALLS   #3, G^LIB$GET_INPUT             ;Get itf: > >         BLBC    R0, DONE1                       ;Done?E > >         TSTW    VBN                             ;Default command?: > >         BNEQ    10$i > >         BRW     READ= > > 10$:    CMPB    #^A"9", VBN_BUF                 ;Numeric?b > >         BLSSU   20$ 5 > >         BRW     NUMBER                          ; F > > 20$:    BICB2   #32, VBN_BUF                    ;Upcase (the blunt way)# > >         CMPB    #^A"S", VBN_BUFw > >         BNEQ    30$a > >         BRW     SIZE# > > 30$:    CMPB    #^A"W", VBN_BUFu > >         BNEQ    40$C > >         BRW     WRITE # > > 40$:    CMPB    #^A"E", VBN_BUFc > >         BNEQ    50$t > >         BRW     DONE# > > 50$:    CMPB    #^A"F", VBN_BUFo > >         BNEQ    60$a" > >         BRW     FORMAT_INDEXED# > > 60$:    CMPB    #^A"D", VBN_BUF2 > >         BEQL    DEBUGs# > >         CMPB    #^A"X", VBN_BUF  > >         BEQL    HEXC > >         PUSHAQ  HELP > >         BRW     GIVE_ERROR > >c > > DEBUG:  MOVAB   BUF, R2o% > >         MOVZWL  RAB+RAB$W_RSZ, R3u% > >         MOVL    RAB+RAB$L_BKT, R4s > >         PUSHL   #SS$_DEBUG$ > >         CALLS   #1, g^LIB$SIGNAL > >         BRW     MAIN_LOOPn > >n > > NUMBER: PUSHAL  NEXT_BUCKETo@ > >         PUSHAL  VBN                             ;INput againA > >         CALLS   #2, G^OTS$CVT_TU_L              ;Convert fromm decimala > >         BLBS    R0, READ! > >         PUSHAQ  CONVERT_ERRORo > >         BRW     GIVE_ERROR > > E > > HEX:    INCL    VBN+4                           ;Skip X character  > >         DECW    VBNa > >         PUSHAL  NEXT_BUCKETu@ > >         PUSHAL  VBN                             ;INput againE > >         CALLS   #2, G^OTS$CVT_TZ_L              ;Convert from hexn > >         BLBS    R0, READ! > >         PUSHAQ  CONVERT_ERRORs > >         BRW     GIVE_ERROR > >o > > WRITE:  $WRITE  RAB=RABn > >         BLBC    R0, OOPS > >         BRW     MAIN_LOOPo > > < > > READ:   MOVL    NEXT_BUCKET, RAB+RAB$L_BKT      ;set VBND > >         $READ   RAB=RAB                         ;Read the bucket > >         BLBC    R0, OOPS  > >         BRW     FORMAT_OTHER > >.  > > OOPS:   CMPL    R0,#RMS$_EOF > >         BEQL    20$s! > >         PUSHAL  RAB+RAB$L_STVn! > >         PUSHAL  RAB+RAB$L_STSe! > >         PUSHAL  RAB+RAB$L_BKTo > >         PUSHAL  IO_ERROR( > >         CALLS   #4, G^LIB$PUT_OUTPUT > >         BRW     MAIN_LOOPi > >h > > 20$:    PUSHAL  ENDOF_ERRORH > >         BRW     GIVE_ERROR > >k > > FORMAT_OTHER:e, > >         ADDL2   BUCKET_SIZE, NEXT_BUCKET@ > >         PUSHL   BUF+0                           ;15     data@ > >         PUSHL   BUF+4                           ;14     data@ > >         PUSHL   BUF+8                           ;13     data@ > >         PUSHL   BUF+12                          ;12     data@ > >         PUSHL   BUF+16                          ;11     data@ > >         PUSHL   BUF+20                          ;10     data@ > >         PUSHL   BUF+24                          ;9      data@ > >         PUSHL   BUF+28                          ;8      data6 > >         PUSHAL  BUF                             ;7B > >         PUSHL   #40                             ;6 ascii bytes> > >         MOVL    #FAO_OUTBUF_L, FAO_OUTBUF_D     ;init size6 > >         PUSHL   RAB+RAB$W_RSZ                   ;56 > >         PUSHL   RAB+RAB$L_BKT                   ;46 > >         PUSHAL  FAO_OUTBUF_D                    ;36 > >         PUSHAL  FAO_OUTBUF_D                    ;26 > >         PUSHAL  FAO_OTHER                       ;1" > >         CALLS   #15, G^SYS$FAO  > >         PUSHAL  FAO_OUTBUF_D( > >         CALLS   #1, g^LIB$PUT_OUTPUT > >m= > >         CMPB    FAB+FAB$B_ORG, #FAB$C_IDX       ;Indexed? " > >         BEQL    FORMAT_INDEXED > >         BRW     MAIN_LOOPM > >r > > FORMAT_INDEXED:o% > >         MOVL    BUF+8,NEXT_BUCKEToA > >         PUSHL   BUF+13                          ;12     FlagssA > >         PUSHL   BUF+12                          ;11     Level @ > >         PUSHL   BUF+1                           ;10     AreaE > >         PUSHL   BUF+6                           ;9      Last/next1A > >         PUSHL   BUF+4                           ;8      InUse % > >         MOVZWL  RAB+RAB$W_USZ, R1tD > >         PUSHL   BUF+8                           ;7      Next vbnF > >         PUSHL   BUF-1(R1)                       ;6      Checkb-endH > >         PUSHL   BUF+0                           ;5      Checkb-startF > >         PUSHL   BUF+2                           ;4      Vbn Sample> > >         MOVL    #FAO_OUTBUF_L, FAO_OUTBUF_D     ;init size6 > >         PUSHAL  FAO_OUTBUF_D                    ;36 > >         PUSHAL  FAO_OUTBUF_D                    ;26 > >         PUSHAL  FAO_INDEXED                     ;1" > >         CALLS   #12, G^SYS$FAO  > >         PUSHAL  FAO_OUTBUF_D > >2 > > GIVE_ERROR:1( > >         CALLS   #1, G^LIB$PUT_OUTPUT > >         BRW     MAIN_LOOPa > >o" > >         .PSECT  data,noexe,wrt > > BUF::   .BLKB   512*64D > > FAB:    $FAB    FAC = <BRO,GET,PUT>, -          ;Allow block I/O read AND write? > >                 FNA = FILENAME_BUF, -           ;Address ofh filename stringr# > >                 SHR = <UPI,PUT>fC > > RAB:    $RAB    FAB = FAB, -                    ;Associated FABi> > >                 ROP = <BIO>, -                  ;block I/O
 ProcessingA > >                 UBF = BUF                       ;Input buffer  > > XAB:    $XABKEYi > >t; > > CONVERT_ERROR:  .ASCID  "Error converting block number"rE > > IO_ERROR:       .ASCID  "Error reading VBN !XL, STS=!XL, STV=!XL" 0 > > ENDOF_ERROR:    .ASCID  "Beyond End Of File"5 > > FILENAME_PROMPT:.ASCID  "Please enter filename: "  > > NEXT_BUCKET:    .LONG   1  > > BUCKET_SIZE:    .LONG   13D > > FILENAME:       .LONG   80,FILENAME_BUF ;input buffer descriptorH > > FILENAME_SIZ:   .WORD   0               ;Receives length of filename > > FILENAME_BUF:   .BLKB   80G > > VBN_PROMPT:     .ASCID  "(##, X##, S##, Debug, Format, Write, Exit).	 Option: "  > > VBN_LEN = 20 > > VBN:            .BLKL   2 # > > VBN_BUF:        .BLKB   VBN_LEN H > > FAO_INDEXED:    .ASCID  "Checks=/!XW/!XB/!XB/, Next=!XL, Use=!XW, "-@ > >                         "Id=!XW, Area=!XB, Lvl=!XB, Flg=!XB"F > > FAO_OTHER:      .ASCID  "VBN=!XL, RSZ=!XW, Data: <!AF> !/ Dump: !8 (9XL)" > > FAO_OUTBUF_L =  200 ( > > FAO_OUTBUF_A:   .BLKB   FAO_OUTBUF_L( > > FAO_OUTBUF_D:   .LONG   FAO_OUTBUF_L) > >                 .ADDRESS FAO_OUTBUF_A7 > >         .END    STARTm >o( > --------------ABC54902C11C5D1E9318FFB3/ > Content-Type: text/x-vcard; charset=us-ascii;6 >  name="maustin.vcf"m! > Content-Transfer-Encoding: 7bitt. > Content-Description: Card for Michael Austin" > Content-Disposition: attachment; >  filename="maustin.vcf"o > 
 > begin:vcardo > n:Austin;Michael > tel;work:704-947-1089a > x-mozilla-html:FALSE > org:Michael Austin, Inc  > adr:;;;;;;
 > version:2.1o- > email;internet:michaelaustininc@hotmail.com  > title:Presidenta > x-mozilla-cpt:;0 > fn:Michael E. Austin > end:vcardo >e* > --------------ABC54902C11C5D1E9318FFB3-- >r >t    & Sent via Deja.com http://www.deja.com/ Before you buy.b   ------------------------------  # Date: Mon, 17 Apr 2000 15:15:28 GMTA From: itjck01@my-deja.come4 Subject: Re: Scheduler & PSDC alternatives, OT on CP) Message-ID: <8df9q0$qg8$1@nnrp1.deja.com>t   .d <snip> .  >aF > We also evaluated the new Compaq ECP tool, which is the old Capicity Planner-F > with a new data collector. It's still a long way from what PSPA gave us, butfD > it's gradually improving. The advisor isn't there, but some of the graphic- > displays are there.1 >p' > Mostly, we're bak to using MONITOR...  >s
 > 	Bob Kaplowk >a2 > SPAM:	spamrecycle@ChooseYourmail.com	uce@ftc.gov 	postmaster@127.0.0.10 >8  E Certainly would agree with your comments about CP v5.1A.  I have beenbC pushing for recognition of the new fibre cards (KGPSA-xx), and havenD been told not until the next version (5.2).  Of course, given that IB purchased CP v5.1 by version, I think I am going to scream for newD license since the product did not work as advertised.  It is gettingF there.  There is still the improper data collection and/or recognition! of VIO cache, and other problems.a  A This is going off topic of the originator's post, but does anyone 5 have a list of problems/wants/known bugs of CP v5.1a?s  A I am just getting into capacity planning, and would like to avoid % pitfalls that others have discovered.n   :) jck JKoska@bender.como    & Sent via Deja.com http://www.deja.com/ Before you buy.r   ------------------------------  % Date: Mon, 17 Apr 2000 17:59:33 +0100r/ From: "Peter Jones" <news@pkjones0.demon.co.uk>  Subject: Security question@ Message-ID: <955990732.7807.0.nnrp-14.9e98fc27@news.demon.co.uk>  J We have a requirement at work to allow a number of users to ftp files onto) an Alpha with the following restrictions:e: - They need to be able to ftp files to a single directory.5 - They must not have access to any other directories.i" - Each user has his own directory.F - In addition, another completely independent process must have "rwed") privileges on all these user directories.o  J I have been told that this is not possible under VMS, the last point being the problem. Is this true?  - Any help or suggestions would be appreciated.h Pete   ------------------------------  % Date: Mon, 17 Apr 2000 13:25:20 -0400n" From: Dan Sugalski <dan@sidhe.org> Subject: Re: Security question6 Message-ID: <4.3.0.20000417131617.01d1dd80@24.8.96.48>  - At 05:59 PM 4/17/00 +0100, Peter Jones wrote:iK >We have a requirement at work to allow a number of users to ftp files ontoo* >an Alpha with the following restrictions:; >- They need to be able to ftp files to a single directory.e6 >- They must not have access to any other directories.# >- Each user has his own directory.@G >- In addition, another completely independent process must have "rwed"e* >privileges on all these user directories. >eK >I have been told that this is not possible under VMS, the last point beingd >the problem. Is this true?h  I Nope, not true at all. Security under VMS is a lot finer-grained and far  H more flexible than you'll find on most OSes. (Certainly better than any G Unix variant you might come across) The easiest thing to do is throw a @K default ACL on the directories that'll get the files that grants access to -< the account running the independent process. Something like:  C $ SET FILE FOO.DIR/ACL=(IDENT=SOME_ACCOUNT,OPT=DEFAULT,ACC=R+E+W+D) 7 $ SET FILE FOO.DIR/ACL=(IDENT=SOME_ACCOUNT,ACC=R+E+W+D)n  J where foo.dir is one of the directories holding files and SOME_ACCOUNT is F either the account that needs access or an identifier granted to that J account. The first line sets it so any files created get the ACL granted, J while the second gives access to the directory as a whole. (You need both)  I It'd be a good idea to check out "The OpenVMS Guide to System Security",  , part of the VMS docset. It's on-line of off . http://www.openvms.compaq.com:8000/index.html.   					Dan  L ----------------------------------------------------------------------------L Dan Sugalski                          General and VMS-specific perl training
 dan@sidhe.orge>                                       Mail me for more details   ------------------------------  # Date: Mon, 17 Apr 2000 17:24:10 GMTr2 From: kilgallen@eisner.decus.org (Larry Kilgallen) Subject: Re: Security question' Message-ID: <2000Apr17.132410.1@eisner>   r In article <955990732.7807.0.nnrp-14.9e98fc27@news.demon.co.uk>, "Peter Jones" <news@pkjones0.demon.co.uk> writes:L > We have a requirement at work to allow a number of users to ftp files onto+ > an Alpha with the following restrictions:d< > - They need to be able to ftp files to a single directory.7 > - They must not have access to any other directories. $ > - Each user has his own directory.    H > - In addition, another completely independent process must have "rwed"+ > privileges on all these user directories.o > L > I have been told that this is not possible under VMS, the last point being > the problem. Is this true?  E 1. What you said is not true -- look up Access Control Entries in thec    documentation.i  E 2. What you probably meant to say is also not true -- look up Defaulto/    Access Control Entries in the documentation.h  H Access on VMS, of course, is controlled by UIC (and Identifiers granted)G to that UIC, not by process, so to have a particular process get accessaI you must arrange to run that process with the proper UIC and Identifiers.    ------------------------------  % Date: Mon, 17 Apr 2000 12:45:50 +0000 / From: Nigel Arnot <sysmgr@maxwell.ph.kcl.ac.uk> " Subject: Re: So who will buy VMS ?6 Message-ID: <009E8BF3.52CF0C1D.2@maxwell.ph.kcl.ac.uk>   > < > Nigel Arnot <sysmgr@maxwell.ph.kcl.ac.uk> wrote in message2 > news:009E8987.DA5E7AC9.3@maxwell.ph.kcl.ac.uk... >  > ...e > N > > But what's so stupid about this for Compaq is that for every customer suchJ > > as the above, there will be many who don't even bother getting a quote > fromL > > Compaq for VMS because they know about the pricing, and who don't botherH > > getting a quote from Compaq for Tru64 because (a) some other Unix isL > > already prevalent in their organisation, or (b) if they have to go Unix,K > > they'll go Linux and never be held to ransom by an O/S vendor again, or M > > (c) they'd prefer never to buy anything from Compaq again, after the pain " > > of being forced away from VMS! > N > Isn't it a tad premature to draw such conclusions without comparing both theC > VMS and Tru64 pricing in this range to that of competing systems?n > M > I mean, it's possible (I certainly don't know - but do you?) that the Tru64hI > price is *lower* than any comparable competing Unix solution (includingpF > hardware, of course), and that the VMS price is competitive as well. > K > If that were true, then it would simply mean that Compaq was aggressivelyfN > pushing Tru64 against its main competition in this market segment - hardly aG > 'stupid' move - and keeping VMS competitive as well, allowing for its  > superior qualities.A  @ Trouble is, that in many cases VMS's "superior qualities" aren'tJ regognised by the decision-makers. Or that if they are, they aren't valued9 as highly as the extra price that Compaq assigns to them.   ) None of my cases (a) to (c) are actually  K about the relative price-competitiveness of Tru64 against other proprietaryIF unix. They are reasons why any quotation for VMS that's more expensiveE than Tru64 can directly result in a migration to a non-Compaq system, ! even if Tru64 *is* competitive.     I Case (a): the higher pricing for VMS causes it to be ruled out. Corporate G   policy then causes some unix other than Tru64 to be selected, becauseAN   the support cost will be a lot lower given that the staff already know aboutI   it (or alternatively, to be selected because that's the policy dictated J   by some PHM that you can't be bothered to argue against after losing the   internal battle for VMS).   K Case (b): you can't compete with Linux on price (and in my experience it's  ,   no less reliable than proprietary Unixes).  " Case (c): surely self-explanatory.  A I've seen (a) in operation. Initially there was a mixture of VMS  J and Solaris. The quote for VMS was ruled out for costing more than Tru64. H The quote for Tru64 wasn't good enough to overcome the "devil you know" J advantage that Solaris had. Yes, the politics were ugly and the decisions I were being taken by know-nothings who just needed an excuse to knock VMS  G out of the running. But by pricing VMS higher, Compaq just played into ZD these peoples hands (and thanks to Digital under Palmer, there are a lot of such people out there).   > K > This points out that the only currently-visible stupidity is this kind oftM > knee-jerk reaction to a perceived internal slight.  There may or may not beiE > cause for disturbance, but if there is no one has yet exhibited it.i  I We'll have to agree to disagree. When Compaq demands X+Y for VMS compared H to X for Tru64 on the same hardware, that extra +Y can be the straw thatD breaks the camel's back, and loses the sale, the site, or the whole J organisation. Small upside, larger downside, and no way back if they lose.   	Yours, 
 		Nigel Arnot - 		NRA@MAXWELL.PH.KCL.AC.UK                      7 		"In the beginning there was nothing, which exploded."Q   ------------------------------  % Date: Mon, 17 Apr 2000 15:46:46 +0100 B From: Andrew Harrison SUNUK Consultancy <andrew.nospam@uk.sun.com>" Subject: Re: So who will buy VMS ?* Message-ID: <38FB23D6.1A889437@uk.sun.com>   Phillip Helbig wrote:u  H > In article <2000Apr13.141435.1@eisner>, kaplow_r@eisner.decus.org (Bob > Kaplow) writes:I > _ > > In article <8d503v$30f$1@info.service.rug.nl>, helbig@astro.rug.nl (Phillip Helbig) writes:0G > > > What about other unix?  Is Tru64 really that much better than the M > > > others?  If not, why not go with another unix?  THEN you could write to N > > > Compaq and say `I would have spent $800,000 on a Compaq product, runningN > > > VMS, to be too expensive compared to $700,000 for a unix machine.  Thus,M > > > I will go with unix.  But having made that step, I see {IBM|SUN|HP|SGI}AM > > > offers me a box for $600,000, so I'm going with that', which would makeAL > > > it clear that Compaq is losing A LOT of money if there are more peopleN > > > like you (also considering that presumably future purchases will be fromM > > > the competition as well).  Unless, of course, the extra money they makeLN > > > on folks who buy VMS even if it is more expensive more than makes up for	 > > > it.  > > O > > Well, once we convert from VMS to UNIX, I guess it really doesn't matter toNI > > us if it's AIX, Solaris, HPUX, or whatever. One major application has M > > already gone from VMS to HPUX. Another is on HPUX because the vendor only I > > supports HPUX and AIX. Another is on Solaris because that vendor only  > > supports SUN and AIX.  > J > My point exactly.  I can understand Compaq pricing VMS higher than unix.H > You get what you pay for.  A "legacy automobile" like a Mercedes costsG > more than a Korean compact.  I don't know what price of VMS optimisesE) > their profits, long, short or mid-term.  >A  ; No, sorry you may think this but the market does not. It is 5 abundantly clear that Compaq/DEC's customer base does % not buy the Mercedes/Hyundai analogy.   : Nor is it clear that there is any great technical argument= that can justify it. Sure OpenVMS clustering is more advanced_6 than UNIX clustering but on the otherhand UNIX supportC for things like IP/DHCP/Java etc etc is much better than OpenVMS's.   ; It is also unclear that the market really values the things 4 where OpenVMS is ahead like OpenVMS clusters because2 UNIX clusters as an example are "good enough". The- example of the German Stock Exchange dropping+, OpenVMS because its Java support is not good+ enough is one example of where this idea of + differential pricing/value falls in a heap.   , Compaq seem to be pricing OpenVMS at a level/ that they feel the die-hard OpenVMS core marketa< will stand, they are not pricing it to sell it competitively2 if the Tru64/OpenVMS pricing is anything to go by.  1 The fact that OpenVMS revenues declined only very 5 slightly in real terms (didn't grow at all) last yearU8 according to IDC seems to indicate that this strategy is working.     Regards  Andrew Harrisons Enterprise IT ArchitectO   ------------------------------   Date: 17 Apr 2000 15:23:25 GMT* From: helbig@astro.rug.nl (Phillip Helbig)" Subject: Re: So who will buy VMS ?. Message-ID: <8dfa9d$bel$3@info.service.rug.nl>  @ In article <38FB23D6.1A889437@uk.sun.com>, Andrew Harrison SUNUK/ Consultancy <andrew.nospam@uk.sun.com> writes:    L > > My point exactly.  I can understand Compaq pricing VMS higher than unix.J > > You get what you pay for.  A "legacy automobile" like a Mercedes costsI > > more than a Korean compact.  I don't know what price of VMS optimises + > > their profits, long, short or mid-term.X > = > No, sorry you may think this but the market does not. It isU7 > abundantly clear that Compaq/DEC's customer base does ' > not buy the Mercedes/Hyundai analogy.1 > . > Compaq seem to be pricing OpenVMS at a level1 > that they feel the die-hard OpenVMS core market+> > will stand, they are not pricing it to sell it competitively4 > if the Tru64/OpenVMS pricing is anything to go by. > 3 > The fact that OpenVMS revenues declined only very 7 > slightly in real terms (didn't grow at all) last year : > according to IDC seems to indicate that this strategy is
 > working.  % It seems we're saying the same thing.   < > Nor is it clear that there is any great technical argument? > that can justify it. Sure OpenVMS clustering is more advanced,8 > than UNIX clustering but on the otherhand UNIX supportE > for things like IP/DHCP/Java etc etc is much better than OpenVMS's.   H It depends on what you want.  What do people use clusters for?  What do  people use java for?  2    http://www.astro.umd.edu/~sgeier/phase_out.html   ------------------------------    Date: 17 Apr 2000 11:12:08 -0500/ From: jlauret@?.chem.sunysb.edu (Jerome LAURET)e Subject: Software Update.1. Message-ID: <38fb29c8_3@dilbert.ic.sunysb.edu>    Software updated from  @  http://nucwww.chem.sunysb.edu/htbin/software_list.cgi?sort=date   Newe  I    LYNX  2.8.2:   Has  patch  for smooth Multinet compilation.  AttemptedRI    some SSL plug-in but it's incomplete (and does  not  currently  work). ?    Make files modified to account for SSL compilation and link.      Updated   I    VIM5.6D  :   This  Vi  Improved is the 5.6 version with patch level 60OI    applied + some fixes in the make file (original distribution  fail  to '    compile with some MMS/MMK versions).S  I    CHKSUM  :   Added wildcard possibility for VMS and several options (inPI    addition to the  BSD  calculation)  to  emulate  cksum  and  Unix  sumUI    algorithm  (SysV and CRC).  The environment variable CHKSUM_OPTION maytI    be used to  set  the  default  algorithm.   See  help  file  for  Unixe(    'sum'/'cksum' vs chksum equivalences.J    On April 14th I have addded the MD5 checksum as in the done in the GNU H    implementation of MD5. If you  took this package on 13-Apr-2000, the L    provided executable was for OpenVMS7.2 .  I repacked it now with the 6.2     version.,  B    GS_UTILS : Added PDF2PS.COM script. Revised version for Gs6.0 .  I    DELTREE  V01-771:  deltree_deep lowercase logical changed to uppercase I    (cannot  be  undefined   externaly   otherwise).    Some   performanceFI    assessement.   This  maintainance  version  should  be 10% faster thanF$    preceding one. Worth updating ...  *    DCC V2.5m : Please  refer to  the      O    <A HREF="http://nucwww.chem.sunysb.edu/dccboard/wwwboard.html">DCC Board</A>o-    for more information on version changes.""i     Retired software      None this time.       -- a6                   Jerome LAURET S.U.N.Y. @ Stony Brook$        ,,,,,      Dept. of Chemistry+       ( o o )     Stony Brook NY 11794-3400h;   ---m---U---m---------------------------------------------n&   E-mail: jlauret@mail.chem.sunysb.edu<   URL   : http://nucwww.chem.sunysb.edu/jlauret/jlauret.html   ------------------------------  % Date: Mon, 17 Apr 2000 16:13:43 +0100vB From: Andrew Harrison SUNUK Consultancy <andrew.nospam@uk.sun.com>/ Subject: Re: Sun considers VMS a "mainframe" OS2* Message-ID: <38FB2A27.DB492486@uk.sun.com>   Bob Bowles wrote:   * > Andrew Harrison SUNUK Consultancy wrote:I > >> Most commercial UNIX's have batch support, batch control systems andpI > > batch scheduler classes nowdays, they also have things like fairshareo > > schedulers.o >wH > Don't get me wrong, I think CRON is pretty nifty, use it all the time. >'B > But where can I find batch support on Solaris?  Is it out of the> > box with the OS?  Or a commonly added 3rd party application? >M  J Tbere is a batch class for the sheduler, but this is probably not what you  / mean. I assume you mean a batch control system.1  ; This does not come out of the box unless you count CRON/AT.s  < You need an additional product, Maestro, AutoSys etc are all commercial batch products.     RegardsP Andrew Harrison  Enterprise IT Architecte   ------------------------------  # Date: Mon, 17 Apr 2000 08:01:29 GMTg4 From: LESLIE@209-16-45-102.insync.net (Jerry Leslie)< Subject: Re: UCX "SET NOHOST/NOCONFIRM" Wipes Out Host Table( Message-ID: <txzK4.3665$eu.59402@insync>  * Jerry Leslie (leslie@clio.rice.edu) wrote:; : The following UCX command wipes out the local host table:o : ! :     $ ucx set nohost /noconfirmv : G : This seems like a bug since no host was specified, per the UCX "help" I : on "set host", included below. The command should require an "*"; e.g.:- : # :     $ ucx set nohost /noconfirm *0 : 
 : The system:r :  :     $ ucx show version : D :       Digital TCP/IP Services for OpenVMS VAX Version V4.2 - ECO 38 :       on a VAXstation 4000-96 running OpenVMS V7.1     :   F BTW, this "feature" was in a DCL script where the host name was passed= in as a parameter, P1, so the actual like of DCL looked like:a  &       $ ucx set nohost /noconfirm 'P1'  4 --Jerry Leslie     (my opinions are strictly my own)   ------------------------------  % Date: Mon, 17 Apr 2000 11:42:28 +0200v= From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com>b1 Subject: Re: Warning: circuitsurgeon is a ripoff!a) Message-ID: <38FADC84.7916CD88@gtech.com>    Beyonder wrote:sF > > I just went through all your posts to comp.os.vms in this thread ! > >  > > No sig in any of the posts.  > > One post signed with B..) > > All the rest of the posts signed Dan.g > > E > > It is difficult not to get the impression that you have a relaxed, > > attitude to "facts". > G > it is difficult not to get the impression that you have a limited IQ. D > or any clue about facts, or are even interested in facts, truth orC > anything else other than you seem to like to argue about senelesst	 > things.r  * Let us just see your original claim again:  ; #and I've posted my real name, even in full, several times."  ; So you think I have a limited IQ, because I do not consider  "first name" = "full name" ?   :-)n   Arne   ------------------------------  % Date: Mon, 17 Apr 2000 11:39:10 +0200l= From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com>e1 Subject: Re: Warning: circuitsurgeon is a ripoff!t) Message-ID: <38FADBBE.FD2BD8AA@gtech.com>c   Beyonder wrote:hB > > However, just because it arrived in a defective state does not$ > > mean it was defective when sent. > C > ah but in this case it does. if you knew anything about shipping,O3 > packing, and "drop tests" you might realize this.    ????  C > > Things are damaged in shipping all the time. Even non-mechancaloB > > things. A few months ago, I had a book damaged in shipping (itI > > had a couple of chunks taken out of it). Did I make moronic statemntsfG > > like, "It arrived damaged therefore you must have sent me a damagedeE > > book"? Of course not - I'm not an idiot. I am well aware that thebE > > package did not teleport from the sender to my mailbox. There wasaE > > a considerable amount of stuff that happened in between its beingoI > > sent and its arrival (some of which was obviously rather unpleasant).- > K > we're not taling about a stupid book, we're talking about a drive mounted 3 > inside a system. too completely different things.    Yes.  H A drive is much more likely to be damaged during transport than a book !   Arne   ------------------------------  % Date: Mon, 17 Apr 2000 13:42:57 +0200a= From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com>0# Subject: Re: Web server for VAX/VMSe) Message-ID: <38FAF8C1.613D8457@gtech.com>m   Dave Pampreen wrote:M > I have a VAX 7820 and a MicroVAX 3190.  I would like to put a web server onaB > them.  Most of the reading I have done says ALPHA ALPHA ALPHA... > M > Does anyone know of one for VAX?    I don't quite have the luxury to get any. > alpha just yet, but give me a bit of time :)  A I know that OSU works fine on VMS VAX. I am also pretty sure thatc WASD works fine on VMS VAX.   = And that is probably the two most widely used HTTPD's on VMS.   ? Only the ones from Compaq seems to have problems with VMS VAX !p   Arne   ------------------------------  # Date: Mon, 17 Apr 2000 12:57:59 GMTu. From: Michael Austin <maustin@nc.prestige.net># Subject: Re: Web server for VAX/VMS / Message-ID: <38FB1809.DB47B206@nc.prestige.net>s  , This is a multi-part message in MIME format.& --------------C818676B00E8AAE69757494B* Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bitc  H You can add the CERN web server  from www.w3c.org to the list of VAX WebJ servers.  I do not beleive this is being maintained any longer (I could beK wrong), but the version avaialable for VMS6.1 has been very stable for  theu limited uses I have seen.V   Michael Austin     Dave Pampreen wrote:   > Hi everyone! > M > I have a VAX 7820 and a MicroVAX 3190.  I would like to put a web server on.B > them.  Most of the reading I have done says ALPHA ALPHA ALPHA... >tM > Does anyone know of one for VAX?    I don't quite have the luxury to get anh. > alpha just yet, but give me a bit of time :) >o > Dave Pampreeno > GKN Automotive, Inc.  & --------------C818676B00E8AAE69757494B- Content-Type: text/x-vcard; charset=us-ascii;   name="maustin.vcf"r Content-Transfer-Encoding: 7bitn, Content-Description: Card for Michael Austin  Content-Disposition: attachment;  filename="maustin.vcf"    begin:vcard  n:Austin;Michael h tel;work:704-947-1089y x-mozilla-html:FALSE org:Michael Austin, Inc 
 adr:;;;;;; version:2.1o+ email;internet:michaelaustininc@hotmail.comw title:President  x-mozilla-cpt:;0 fn:Michael E. Austin	 end:vcard   ( --------------C818676B00E8AAE69757494B--   ------------------------------  # Date: Mon, 17 Apr 2000 10:03:57 GMT 0 From: carlini@true.lkg.dec.com (Antonio Carlini)A Subject: Re: What are some reasons for different size executablesh* Message-ID: <8den02$os0@usenet.pa.dec.com>  Z In article <4.3.0.20000414111919.01d4ac70@24.8.96.48>, Dan Sugalski <dan@sidhe.org> wrote:E >It's also possible that the compiler's taking advantage of built-in uM >instructions when targeting the 78xx machine where it needs to emulate them qL >on the 4705, but I don't know if that's the case. (Building on Alphas when E >targeting an EV5 gets you different code than when targeting an EV4)a  N The VAX 78xx and the VAX 4705 are both based on the NVAX chip family so there L are no differences. Even if they were different chips, I don't think any of N the compilers give you a chance to "target" anything and they certainly don't L silently assume "I'm building on an NVAX machine, I bet I'll never run on a  Rigel".t  M With Alpha you can choose to target a particular architecture but even there cO it doesn't matter what the architecture of the build machine is. If you target rG EV6 while building on an EV4 box you get the same executable (assuming nI *everything* else is the same) as you would were you to target EV6 while b building on an EV67 box.  N The explanation will be the usual one that turns up almost every time someone 1 tells you "I have two identical systems ...". :-)a   Antonio   I Antonio Carlini                            Mail: carlini@true.lkg.dec.comp# DECnet-Plus for OpenVMS Engineerings6 COMPAQ                                     Reading, UK   ------------------------------  % Date: Mon, 17 Apr 2000 13:34:47 +0200t= From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com> A Subject: Re: What are some reasons for different size executablesd) Message-ID: <38FAF6D7.45403592@gtech.com>i   John Nixon wrote:nH > One of our resident, constantly complaining ex-unix programmers is nowN > screaming because we are forcing him to begin developing VAX code  (DECC) onM > a development system instead of  developing right on the production system.. > M > His first stab at this was to build code on the dev VAX.  He is complainingtK > about the fact that executables on the development system are larger thanbI > they are on the production VAX, even though the VMS version is the same 4 > (7.1) and the DECC Compiler versions are the same. > N > He is comparing "used" space rather than "allocated" space, so the different' > disk cluster sizes are not the issue.d > G > Other than compiler or linker options, such as /DEBUG,  what are somedM > reasons that the executables would be different sizes on different machinesLK > (VAX 78xxs vs VAX 4705).   Should these different sizes be a warning of aw > potential problem?  A Same VMS version, same C compiler version, same compiler and link  optionsn0 used shall/must/will give same executable size !   Something must be different !l   Arne   ------------------------------  % Date: Mon, 17 Apr 2000 08:16:16 -0400 " From: Dan Sugalski <dan@sidhe.org>A Subject: Re: What are some reasons for different size executablesn6 Message-ID: <4.3.0.20000417081439.01d09c70@24.8.96.48>  1 At 10:03 AM 4/17/00 +0000, Antonio Carlini wrote:oE >In article <4.3.0.20000414111919.01d4ac70@24.8.96.48>, Dan Sugalski I ><dan@sidhe.org> wrote:oF > >It's also possible that the compiler's taking advantage of built-inN > >instructions when targeting the 78xx machine where it needs to emulate themM > >on the 4705, but I don't know if that's the case. (Building on Alphas whenaG > >targeting an EV5 gets you different code than when targeting an EV4)6 >0N >The VAX 78xx and the VAX 4705 are both based on the NVAX chip family so thereL >are no differences. Even if they were different chips, I don't think any ofN >the compilers give you a chance to "target" anything and they certainly don'tL >silently assume "I'm building on an NVAX machine, I bet I'll never run on a >Rigel". >rM >With Alpha you can choose to target a particular architecture but even there I >it doesn't matter what the architecture of the build machine is. If you   >targetHG >EV6 while building on an EV4 box you get the same executable (assumingoI >*everything* else is the same) as you would were you to target EV6 whileI >building on an EV67 box.c  K Right, but if you've got CC set to be CC/arch=host or something you'll get cH different executables on different machines. That's what I was thinking K could possibly be the problem here. Since the CPUs are the same that's not a& it, of course, but it was a thought...   					Dan  I --------------------------------------"it's like this"-------------------t2 Dan Sugalski                          even samurai? dan@sidhe.org                         have teddy bears and evena;                                       teddy bears get drunkr   ------------------------------  % Date: Mon, 17 Apr 2000 13:10:05 +0100n- From: Tim Llewellyn <tim.llewellyn@bbc.co.uk>o? Subject: Re: Why are there no French people in this newsgroup ?V) Message-ID: <38FAFF1D.C1AC086E@bbc.co.uk>t   Paul Sture wrote:i  e >  My Swiss German boss claims that he doesn't like English (although he's pretty good at it), but he.  > prefers to program in English.  J Is that some new fangled 5th generation progamming language, that English? :-)m     --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.ukd  A I speak for myself only and my views in no way represent those ofV MedAS or the BBC.i   ------------------------------  # Date: Mon, 17 Apr 2000 10:07:08 GMTt0 From: carlini@true.lkg.dec.com (Antonio Carlini)$ Subject: Re: XADRIVER documentation?* Message-ID: <8den66$os0@usenet.pa.dec.com>  V In article <slrn8fcv5l.b3o.rivie@server.logan.teraglobal>, rivie@teraglobal.com wrote:  ; >Say, guys, is there any currently extant documentation for)5 >XADRIVER, the DR11-W driver for VAX/VMS? It is still92 >supplied as an example driver, but seems to have 2 >disappeared from the I/O User's Reference Manual.  7 I have not looked, but if it's gone, I guess it's gone.e  3 >Failing that, would old versions of the I/O User'sn. >Reference Manual be covered under the blanket- >permission to copy old software manuals thata- >allows (for example) the PDP-8 manuals to be  >traded around?   N Not for another twenty years or so :-) The easiest thing would be to dig up a L copy of the documentation that you would like to use and ask COMPAQ whether N they would mind you using it. The worst they can say is "No" and then you get  to hire a tech writer ...h  C Or you could beg for XADRIVER and its docs to get dropped onto the n Freeware CD.   Antonioc  I Antonio Carlini                            Mail: carlini@true.lkg.dec.com # DECnet-Plus for OpenVMS Engineeringn6 COMPAQ                                     Reading, UK   ------------------------------   End of INFO-VAX 2000.215 ************************