1 INFO-VAX	Tue, 26 Sep 2000	Volume 2000 : Issue 538       Contents: Re: AlphaPC164 & decwindows , Re: Alphaserver 4100 + KGPSA (Fiber Channel), RE: Alphaserver 4100 + KGPSA (Fiber Channel), Re: Alphaserver 4100 + KGPSA (Fiber Channel), RE: Alphaserver 4100 + KGPSA (Fiber Channel) Re: Changing System Password1 Re: Clustering VAXstation with dead serial driver  Compaq postcard  Re: Compaq postcard  Re: Compaq postcard B Re: DEC 36Gb disks cheap ! DO NOT READ IF YOU WANT TO PAY TOO MUCH Re: DECserver 90M Doc  Re: DECserver 90M Doc * Re: detached process can't output anything* Re: detached process can't output anything  Re: duh... max filename lenth???  Re: duh... max filename lenth??? E-MAIL PROCESSORS NEEDED!! Re: elsa configuration problem& Re: Freeware for extracting Mime filesF Re: How to connect Digital line printer (LP29 or LP37) to HP JetDirectF Re: How to connect Digital line printer (LP29 or LP37) to HP JetDirectF Re: How to connect Digital line printer (LP29 or LP37) to HP JetDirect Re: Incremental backup blues; Re: Interesting result from Copy/Log with version limit set % More OpenVMS advertising (from the Q)  Re: MULTIA + OpenVMS Re: MULTIA + OpenVMS New OpenVMS Books  Re: New OpenVMS Books % Re: No more SYSDUMP.DMP? No more NTP?  Re: NTP with UCX 4.2 OpenVMS 7.3  Re: OpenVMS 7.3  Re: OpenVMS features (future) * Re: Porting Support (was Compaq VMS promo)! Postscript file operations on VMS % Re: Postscript file operations on VMS  Re: Press Release  Re: Press Release $ Re: reading VMS files with Delphi...  Re: remote login using .com file4 Re: Replacing system disk, will licenses still work?4 Re: Replacing system disk, will licenses still work?4 Re: Replacing system disk, will licenses still work?% Re: restart an Alpha ETN42-CA machine % Re: restart an Alpha ETN42-CA machine 
 Safety SPD
 Re: set watch 1 Re: Son of BUT... (Re: Why are these files open?) 1 Re: Son of BUT... (Re: Why are these files open?)  Spring 2000 VMS sigtapes Re: Spring 2000 VMS sigtapes Re: Spring 2000 VMS sigtapes Re: SRAM Corruption Thread Re: SRAM Corruption Thread Re: Suggested VMS new feature! Re: Suggested VMS new feature! Re: Suggested VMS new feature!! Re: Sun Hardware problems persist K Re: Top "F" Reasons OpenVMS isn't going to Die  (WAS:Re: [VMS] VAX isdying) K Re: Top "F" Reasons OpenVMS isn't going to Die  (WAS:Re: [VMS] VAX isdying)  use of LIB$GET_VM  Re: use of LIB$GET_VM  Re: use of LIB$GET_VM  Re: VMSNET.* hierarchy ?, Re: Why is it so hard to port things to VMS?, Re: Why is it so hard to port things to VMS?, Re: Why is it so hard to port things to VMS?, Re: Why is it so hard to port things to VMS?, Re: Why is it so hard to port things to VMS?, Re: Why is it so hard to port things to VMS?, Re: Why is it so hard to port things to VMS?, Re: Why is it so hard to port things to VMS?  F ----------------------------------------------------------------------  % Date: Mon, 25 Sep 2000 20:34:52 -0400 ) From: yyyc186.illegaltospam_@flashcom.net $ Subject: Re: AlphaPC164 & decwindows9 Message-ID: <39cfef48$1$lllp186$mr2ice@news.flashcom.com>   1 In <8qnj3e$e2u$1@mordred.cc.jyu.fi>, on 09/25/00  :    at 08:34 PM, Osmo Kujala <kujala@kanto.cc.jyu.fi> said:  H I had to apply both the hardware ECO and the Elsa ECO before I could get8 to that stage.  Your system must have been more current.   Roland  + >yyyc186.illegaltospam_@flashcom.net wrote:   K >> What autoconfig command did you use to get Decwindows to see the device?    >$ mcr sysman io autoconfig    >/OK --  ; ----------------------------------------------------------- D yyyc186@flashcom.net              To Respond delete ".illegaltospam"6                             MR/2 Internet Cruiser 1.528                             For a Microsoft free univers; -----------------------------------------------------------    ------------------------------  # Date: Mon, 25 Sep 2000 22:01:38 GMT  From: Dirk Munk <munk@home.nl>5 Subject: Re: Alphaserver 4100 + KGPSA (Fiber Channel) ' Message-ID: <39CFCB3F.4C71CE49@home.nl>   * fabio_compaq@ep-bc.petrobras.com.br wrote: > J > Do you know if the Alphaserver 4100 (OpenVMS 7.2 and 7.1-1H2) works fine > withE > the KGPSA adapter. We will migrate our storage from a Storage Works  > (nowadays  > SCSI) to an EMC array (FC).   H The KGPSA adapters are supported in the Alpha 4000 series AFAIK, but youH will need the latest firmware in the Alpha. But if it is wise to connectD them to a EMC cabinet is a very different matter. VMS is known to beC very demanding on the correct implementation of storage, so we have C decided to use the HSG80 and not to try an experiment with EMC. The = HSG80 is also a whole lot cheaper and faster compared to EMC.      > 
 > Regards, >  > Fabio Cardoso  > Analista de Suporte * > Compaq / Petrobras - Macae - RJ - Brasil   ------------------------------  % Date: Mon, 25 Sep 2000 13:14:17 -0400 : From: "Koska, John C. (LNG-MBC)" <John.C.Koska@bender.com>5 Subject: RE: Alphaserver 4100 + KGPSA (Fiber Channel) K Message-ID: <91A9507020DBD311992F0008C709517C545B89@MBCALBEXC00.BENDER.COM>    > -----Original Message-----+ > From: fabio_compaq@ep-bc.petrobras.com.br . > [mailto:fabio_compaq@ep-bc.petrobras.com.br]* > Sent: Monday, September 25, 2000 8:34 AM > To: Info-VAX@mvb.saic.com 3 > Subject: Alphaserver 4100 + KGPSA (Fiber Channel)  > @ > Do you know if the Alphaserver 4100 (OpenVMS 7.2 and 7.1-1H2) A > works fine with the KGPSA adapter. We will migrate our storage  < > from a Storage Works (nowadays SCSI) to an EMC array (FC). > 
 > Regards, >  > Fabio Cardoso  > Analista de Suporte * > Compaq / Petrobras - Macae - RJ - Brasil >   < The AlphaServer 4100, OpenVMS, and the KGPSA will work fine > and are supported. I don't know about EMC array fibre channel < working with the former.  I doubt it is supported by Compaq.  > I do know from personal experience that fast wide differentialB SCSI EMC array/Symmetrix with an AlphaServer 4100 running OpenVMS > 7.1 to 7.2-1 was not reliable and poor performing in my hands.  D You might want to take a look at www.deja.com and search comp.os.vmsA on "EMC" and/or "Symmetrix" among other search terms to see what  ; the various issues might be with using EMC storage with an   AlphaServer.  @ At my site, we went  FROM   an EMC FWD SCSI Symmetrix    TO   a C StorageWorks fibre channel solution with about a 2.5 fold increase  A in I/O performance, and much greater reliability and flexibility.   5 Why not simply upgrade to StorageWorks fibre channel?    :) jck   ------------------------------  # Date: Tue, 26 Sep 2000 00:32:21 GMT $ From: Scott Vieth <svieth@wi.rr.com>5 Subject: Re: Alphaserver 4100 + KGPSA (Fiber Channel) ) Message-ID: <39CFEEDA.561F1E32@wi.rr.com>   * fabio_compaq@ep-bc.petrobras.com.br wrote:  J > Do you know if the Alphaserver 4100 (OpenVMS 7.2 and 7.1-1H2) works fine > withE > the KGPSA adapter. We will migrate our storage from a Storage Works  > (nowadays  > SCSI) to an EMC array (FC).   3 GASP!  You're migrating *to* EMC from StorageWorks?   G Geez!  Sound the alarms!  Get the Compaq storage salesdudes out of bed! & Get this man an ESA12000 to play with!  K Take a long, hard look at the StorageWorks fc solutions before you crawl in C bed with EMC.  The array itself is pretty kick-ass and the "layered 	 products" L that work with the storage (like Enterprise Volume Manager, Data Replication  2 Manager and SecurePath) are the icing on the cake.  ! -Scott, happy ESA12000 owner  :^)    ------------------------------  % Date: Tue, 26 Sep 2000 00:53:58 -0400 + From: "Main, Kerry" <Kerry.Main@compaq.com> 5 Subject: RE: Alphaserver 4100 + KGPSA (Fiber Channel) J Message-ID: <910612C07BCAD1119AF40000F86AF0D80528481D@kaoexc4.kao.dec.com>   Fabio,  L You should find most of the information you are looking for at the following	 web site: 7 http://www.openvms.digital.com/openvms/fibre/index.html    Regards,  
 Kerry Main Senior Consultant,
 Compaq Canada  Professional Services  Voice : 613-592-4660 FAX   : 819-772-7036 Email : kerry.main@compaq.com        -----Original Message-----) From: fabio_compaq@ep-bc.petrobras.com.br , [mailto:fabio_compaq@ep-bc.petrobras.com.br]( Sent: Monday, September 25, 2000 8:34 AM To: Info-VAX@Mvb.Saic.Com 1 Subject: Alphaserver 4100 + KGPSA (Fiber Channel)       H Do you know if the Alphaserver 4100 (OpenVMS 7.2 and 7.1-1H2) works fine withC the KGPSA adapter. We will migrate our storage from a Storage Works 	 (nowadays  SCSI) to an EMC array (FC).    Regards,  
 Fabio Cardoso  Analista de Suporte ( Compaq / Petrobras - Macae - RJ - Brasil   ------------------------------  % Date: Mon, 25 Sep 2000 18:07:03 +0200 = From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com> % Subject: Re: Changing System Password ) Message-ID: <39CF7827.DE67758E@gtech.com>    Mary Bennett wrote: . > Alright, I admit it, senility is setting in. > L > I have a VAX 3100/40 which I just repaired running VMS 5.5-2.  I haven't aK > clue what the SYSTEM password is and can't remember how to change it from  > the boot.  > F > If anyone can remember what ALL of the commands are from the >>> I'd8 > appreciate it. (I don't want to blow my image at WIS).   See the VMS FAQ !   ? (there are a link at http://www.levitte.org/~ava/vms_faq.htmlx)    Arne   ------------------------------  # Date: Mon, 25 Sep 2000 23:16:23 GMT / From: atlas@world.std.com (Alexander R Svirsky) : Subject: Re: Clustering VAXstation with dead serial driver& Message-ID: <G1GtzF.CwM@world.std.com>  H Robert, thanks for the suggestion.  I'll give it a try before I actually attempt a hardware fix.    Alex  3 Robert Deininger (rdeininger@mindspring.com) wrote: Y : In article <G1EK34.AnK@world.std.com>, atlas@world.std.com (Alexander R Svirsky) wrote:   I : > I would like to cluster a VAXstation 3100 M30 with an apparently dead I : > serial port driver.  Problem symptoms in serial console configuration  : > include the following:     : > Questions - M : > How do I find the ethernet ID if I can't read test output on the console? L : > Might there be a sticker on the board somewhere?  Also, before I heat upL : > my iron, do these symptoms describe a problem that may not be present in : > the serial driver?    H : I _think_ (no time to try it now) that you can set up a MOP bootserverQ : on your other node and it will tell you the ethernet address.  When you attempt D : an ethernet boot on the sick node, it sends some sort of multicastH : request, and every MOP server within range will start to respond.  TheG : the ethernet address of the requestor is known to the server, it will G : send the correct file over the net, otherwise it will end the service L : request.  But the server logs an OPCOM message in either case, and I think= : the message includes the ethernet address of the requestor.    : --   : Robert Deininger : rdeininger@mindspring.com  --  C Alexander_R_Svirsky_____________________________atlas@world.std.com    ------------------------------  # Date: Tue, 26 Sep 2000 00:56:24 GMT " From: psy@get2net.dk (Bent Wagner) Subject: Compaq postcard3 Message-ID: <slrn8suv6r.131.psy@psy.bronderslev.dk>   
 Hello all.  ( Today i received a postcard from Compaq.  1 On the front there was a picture of a parachuter, , and the text 'Open it'  -- open a postcard??  , On the back there was a text telling me that they all thought i was crazy.   + Well - it appears that Compaq think so too, , as they later in the text tell me to pack my own parachute and jump.   . In the past i have received weird things in my& mail, but this is almost a winner :-))   Bent Wagner  psy@get2net.dk   ------------------------------  % Date: Mon, 25 Sep 2000 21:25:10 -0500 7 From: "David J. Dachtera" <djesys.nospam@earthlink.net>  Subject: Re: Compaq postcard- Message-ID: <39D00906.A3353657@earthlink.net>    Bent Wagner wrote: >  > Hello all. > * > Today i received a postcard from Compaq. > 3 > On the front there was a picture of a parachuter, . > and the text 'Open it'  -- open a postcard?? > . > On the back there was a text telling me that > they all thought i was crazy.  > - > Well - it appears that Compaq think so too, . > as they later in the text tell me to pack my > own parachute and jump.  > 0 > In the past i have received weird things in my( > mail, but this is almost a winner :-))  D Going back to an earlier discussion here of "roll your own" o.s.-es,H this may be someone's idea of comparing UN*X (Linux, *BSD, etc.) to VMS.  B If this is the best that the new V.P. of Marketing and Co. have toH offer, I'd recommend that Compaq stockholders who lurk here get together> and demand the ouster of such personnel as may be appropriate.   --   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: Mon, 25 Sep 2000 21:06:22 -0700 ! From: Koloth <koloth@tmisnet.com>  Subject: Re: Compaq postcard+ Message-ID: <39D020BE.3035435F@tmisnet.com>   H Didn't Compaq hire the same advertisement firm that was trying to market OpenVMS under Digital?I The same people that brought you the, "Hell hath no fury?"  and the other L confusing ads.  Why can Compaq hire the firm that does IBM or Apple ads?  It4 least they would be understandable and fun to watch.  * They should be spaced as soon as possible.   Cass   "David J. Dachtera" wrote:   > Bent Wagner wrote: > >  > > Hello all. > > , > > Today i received a postcard from Compaq. > > 5 > > On the front there was a picture of a parachuter, 0 > > and the text 'Open it'  -- open a postcard?? > > 0 > > On the back there was a text telling me that! > > they all thought i was crazy.  > > / > > Well - it appears that Compaq think so too, 0 > > as they later in the text tell me to pack my > > own parachute and jump.  > > 2 > > In the past i have received weird things in my* > > mail, but this is almost a winner :-)) > F > Going back to an earlier discussion here of "roll your own" o.s.-es,J > this may be someone's idea of comparing UN*X (Linux, *BSD, etc.) to VMS. > D > If this is the best that the new V.P. of Marketing and Co. have toJ > offer, I'd recommend that Compaq stockholders who lurk here get together@ > and demand the ouster of such personnel as may be appropriate. >  > -- > David J. Dachtera  > 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.    ------------------------------  # Date: Tue, 26 Sep 2000 01:02:07 GMT $ From: Scott Vieth <svieth@wi.rr.com>K Subject: Re: DEC 36Gb disks cheap ! DO NOT READ IF YOU WANT TO PAY TOO MUCH ) Message-ID: <39CFF5D9.128C09D4@wi.rr.com>   : Hell, I was paying less than that when I bought a bunch of- those drives from Great Lakes six months ago.    -Scott   Island Computers wrote:    > OK - I am posting another ad > 2 > DS-RZ1FC-VW 36GB 10KRPM Storageworks Drive $1575 > A > These are BRAND NEW SEALED BOXES WITH FULL COMPAQ WARRANTY !!!!  >  > David  > -  > David Turner! > Island Computers US Corporation  > 2700 Gregory Street  > Savannah GA 31404  > Tel: 912 447 6622  > Fax:912 201 0096 > sales@islandco.com   ------------------------------  % Date: Mon, 25 Sep 2000 21:28:28 +0100 6 From: "antonio.carlini" <antonio.carlini@ntlworld.com> Subject: Re: DECserver 90M Doc, Message-ID: <39CFB56C.AA08B903@ntlworld.com>   "David J. Dachtera" wrote:H > Hey! Found a link to a .PDF of DECserver 90 M doc. in an eBay posting:) > http://www.leavens.net/dec/dsrvh-om.pdf   ? As I'm at the end of a slow modem at the moment I cannot check  > exactly which manual that is (I assume it's the Owner's Guide)D and I cannot check the 90M manual available (along with many others) at     http://www.dnpg.com/products  0 but it might save you trawling ebay auctions :-)   Antonioi   ---------------l- Antonio Carlini             arcarlini@iee.orgh   ------------------------------  # Date: Mon, 25 Sep 2000 21:43:11 GMT = From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-)o Subject: Re: DECserver 90M Doc0 Message-ID: <009F0AA0.894A1BA9@SendSpamHere.ORG>  e In article <39CFB56C.AA08B903@ntlworld.com>, "antonio.carlini" <antonio.carlini@ntlworld.com> writes:E >r >  >"David J. Dachtera" wrote:sI >> Hey! Found a link to a .PDF of DECserver 90 M doc. in an eBay posting:.* >> http://www.leavens.net/dec/dsrvh-om.pdf >m@ >As I'm at the end of a slow modem at the moment I cannot check ? >exactly which manual that is (I assume it's the Owner's Guide)DE >and I cannot check the 90M manual available (along with many others)D >atl >n >  http://www.dnpg.com/productst    just a javascript error there...    --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COM             oO city, n., 1. a place where trees are cut down and streets are named after them.A   ------------------------------  % Date: Mon, 25 Sep 2000 18:31:48 -0400 ) From: John Santos <jasantos@ultranet.com>e3 Subject: Re: detached process can't output anythinge= Message-ID: <MPG.14399c5bf8d40c2d98977d@news.ma.ultranet.com>M  F In article <#052F2pJAHA.66@cpmsnbbsa09>, cstranslations@email.msn.com  says... ! > What language is is written in?eF > How is it generating output (language specific or direct RMS calls)? > What does the program do?sN > Have you run it under the debugger to trace it's execution (is it processing. > the data and attempting to generate output)? >  > joee > N > <defdannyd@my-deja.com> wrote in message news:8qm1kh$n34$1@nnrp1.deja.com...K > > I am having a problem similar to some I have seen in this group in that H > > I have a detached process taht is having trouble logging any output.G > > The bigger issue I am having is that I don't use logicals at all. IuI > > specify an output file on the command using the /output qualifier andeC > > the process itself creates a log file to use for nonfatal error K > > messages. Both files get created in the expected location and both haveWI > > protections of (rwd,rwd,rwd,rwd) and yet no output comes out, ever. I G > > flush after every output operation. I even sent about a meg of data K > > through it thinking it might be some kind of buffering issue, but stillr! > > nothing. Any ideas? Thanks...h > >o
 > > Dan C.  A I have seen a problem where nothing gets written to sys$output if A sys$input doesn't exist.  IIRC, specifying "/input=NL:" worked tosG fix this.  I think it started doing this at about VMS V7.0.  This mighth( only apply to programs written in BASIC.   --   John Santoss   ------------------------------   Date: 25 Sep 2000 22:58:55 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)3 Subject: Re: detached process can't output anythingj6 Message-ID: <8qolbf$9l8$3@mailint03.im.hou.compaq.com>  i In article <MPG.14399c5bf8d40c2d98977d@news.ma.ultranet.com>, John Santos <jasantos@ultranet.com> writes:sK defdannyd@my-deja.com> wrote in message news:8qm1kh$n34$1@nnrp1.deja.com...EH :I am having a problem similar to some I have seen in this group in thatE :I have a detached process taht is having trouble logging any output.tD :The bigger issue I am having is that I don't use logicals at all. II :specify an output file on the command using the /output qualifier and...-  L   If you have a DECwindows display available somewhere, use CREATE/TERMINAL M   or the DECw$Term_Port API call, and pass along the created terminal device r<   as the SYS$OUTPUT device for the under-creation process.    I   Alternatively, use an unallocated serial line device as the target for  H   the debugger, setting up the DBG$INPUT and DBG$OUTPUT logical names toH   reference the device -- these logical names must be defined in a table!   visible to the created process.C  J   The process can now be built with and debugged via the OpenVMS debugger.  M   If running a recent version of OpenVMS, you can also use the client-server GH   debugger -- linking into the application under debug from a local or aI   remote OpenVMS client debugger, or from one of the PC debugger clients.h  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Mon, 25 Sep 2000 18:02:40 +0200,= From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com>m) Subject: Re: duh... max filename lenth???o) Message-ID: <39CF771F.CF5F0147@gtech.com>    Jim Agnew wrote: > guys, i've not only clean forgotten what the max filename and filetype is for vms, i've no idea where it is in the grey wall...,' > anyone know of the top of their head?a  ( 39.39 for ODS-2 and 255 or 256 for ODS-5   Arne   ------------------------------  % Date: Mon, 25 Sep 2000 15:30:32 -0400D# From: Jim Agnew <agnew@hsc.vcu.edu>0) Subject: Re: duh... max filename lenth???-+ Message-ID: <39CFA7D8.F6A9EFAE@hsc.vcu.edu>b  6 Thanks to all who replied, too many to mention here...  V the definitive answer for 5.5-2 is 39.39 chars for a filename.  plenty to work with...   thanks to you all.   Jim    Jim Agnew wrote: >  > guys, i've not only clean forgotten what the max filename and filetype is for vms, i've no idea where it is in the grey wall...e' > anyone know of the top of their head?C >  > Jime >  > (blushing.. i KNEW this once)s   ------------------------------   Date: Mon, 25 Sep 2000 17:51:01   From: <proj.21dm@consultant.com># Subject: E-MAIL PROCESSORS NEEDED!!r8 Message-ID: <369.396413.682446@proj.21dm@consultant.com>  8 E-mail processing company looking for e-mail processors C immediately, to sustain explosive growth. Earn $2,000, $6,000 part a? time monthly. Free start-up, Not MLM, no experience necessary. 7@ Send an e-mail to: proj.21dm@consultant.com with SHOW ME in the A subject line. We want serious inquiries who want to make serious M money!!   m  r     n  t     r  t  s         ------------------------------  % Date: Mon, 25 Sep 2000 13:31:58 -0700S0 From: Mark Berryman <Mark.Berryman@Mvb.Saic.Com>' Subject: Re: elsa configuration problemb$ Message-ID: <276973814@Mvb.Saic.Com>   Jean-Franois Marchal wrote: > + > Here is a problem I got this week-end ... 7 > New DS10 with factory installed 7.2-1 and Motif 1.2.5 / > Elsa graphic adapter, with 21" Compaq Monitora > 	 > I added $ >     $ DECW$XSIZE_IN_PIXELS == 1280$ >     $ DECW$YSIZE_IN_PIXELS == 1024" > in decw$private_server_setup.com > A > Since this modification, display is starting at one inch of theo< > left border of the screen. sounds like the frquency wasn't > correctly set up.2 > 3 > I just tryed at my office with a DEC 21" monitor.eA > The display is now like a barrel, with a larger top, bottom and  > left margin (not right). > @ > What can I do to correct this and usr full 1280x1024 display ?  D Do not make these changes in the decw$private_server_setup.com file.  D You should have a file called: sys$manager:decw$device_config_gz.com  F Make the changes in that file, including the change for refresh rate. B (How to make the changes is documented in the file.)  Then restart DECwindows.e  
 Mark Berrymanp Mark.Berryman@Mvb.Saic.Com   ------------------------------  % Date: Mon, 25 Sep 2000 17:59:11 +0200 = From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com>5/ Subject: Re: Freeware for extracting Mime filesc) Message-ID: <39CF764F.F8E755EF@gtech.com>    "Miller, Daniel" wrote:DF > Does anyone know of freeware which allows mime files to be extractedI > from mail?  We have UUENCODE/UUDECODE, but not found anything for mime.l  $ Look for MPACK/MUNPACK or MMENCODE !   Arne   ------------------------------  # Date: Mon, 25 Sep 2000 21:47:01 GMT, From: Dirk Munk <munk@home.nl>O Subject: Re: How to connect Digital line printer (LP29 or LP37) to HP JetDirecto' Message-ID: <39CFC7C9.A4089895@home.nl>m   Arto Tanninen wrote: > E > Could I use BC27Z RapidPrint 200 to Dataproduct Line Printer Cable?   - According to the specifications on this page:.  N http://www.hms.labinf.it/pagine/home/hms/prodotti/dec/gesrete/prt_rp200ds.html  H the RapidPrint 200 also support the Dataproducts interface. But you will need a new cable.e   Regards,   Dirk    g   >  > Arto > 9 > "Arto Tanninen" <arto.tanninen@icl.fi> wrote in messages( > news:vECz5.33$bb.4319@read2.inet.fi... > > Hi,e > > N > > I would like to connect Digital LP29 and LP37 to network via HP JetDirect.J > > Printers are now connecting to DECserver 250 with cable BC27A. I'm nowE > > looking for parallel cable DB25-DB37 or DB25-DB50 or some kind ofc > converter. > >t > > Could you help me. > >i > > Arto > > arto.tanninen@icl.fi > >a > >3   ------------------------------  # Date: Tue, 26 Sep 2000 00:27:03 GMT $ From: Scott Vieth <svieth@wi.rr.com>O Subject: Re: How to connect Digital line printer (LP29 or LP37) to HP JetDirectf) Message-ID: <39CFEDA1.A47A2FE6@wi.rr.com>c  H The RapidPrint box works well.  I've used it with the DEC line printers.0 It's very similar to setting up a JetDirect box.   -Scott   Dirk Munk wrote:   > Arto Tanninen wrote: > >eG > > Could I use BC27Z RapidPrint 200 to Dataproduct Line Printer Cable?S >s/ > According to the specifications on this page:d >rP > http://www.hms.labinf.it/pagine/home/hms/prodotti/dec/gesrete/prt_rp200ds.html >oJ > the RapidPrint 200 also support the Dataproducts interface. But you will > need a new cable.d >i
 > Regards, >. > Dirk >  >  >a > >e > > Arto > >r; > > "Arto Tanninen" <arto.tanninen@icl.fi> wrote in message * > > news:vECz5.33$bb.4319@read2.inet.fi...	 > > > Hi,i > > >pP > > > I would like to connect Digital LP29 and LP37 to network via HP JetDirect.L > > > Printers are now connecting to DECserver 250 with cable BC27A. I'm nowG > > > looking for parallel cable DB25-DB37 or DB25-DB50 or some kind ofh > > converter. > > >  > > > Could you help me. > > >h
 > > > Arto > > > arto.tanninen@icl.fi > > >  > > >e   ------------------------------  % Date: Mon, 25 Sep 2000 21:11:23 -0500i7 From: "David J. Dachtera" <djesys.nospam@earthlink.net> O Subject: Re: How to connect Digital line printer (LP29 or LP37) to HP JetDirect , Message-ID: <39D005CB.E771023@earthlink.net>   Scott Vieth wrote: > J > The RapidPrint box works well.  I've used it with the DEC line printers.2 > It's very similar to setting up a JetDirect box.  F In my search to replace DECserver250s, we tried the RP-200s. Two major	 problems:v  H  1. The printer MUST be on-line when the print job starts, or the RP-200G will reject the connection request. This can result in a delay of up to G three minutes or more in actually starting to print when the printer is_; then put on-line (MULTINET_STREAM_SYMBIONT, Multinet V4.1A,  OpenVMS-Alpha V6.2-1H3).  D 2. The RP-200 has a *VERY* large data buffer. In case of a paper jamF mid-job, restarting the print job may result in significant data loss.F The job will restart well after the point in the data stream where the paper jam actually occurred.  D Caveats offered for your evaluation based on my personal experience. Your mileage may vary.   -- t David J. Dachterah dba DJE Systemsw 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.k   ------------------------------  # Date: Mon, 25 Sep 2000 23:35:45 GMTh* From: Alan E. Feldman <alan48@my-deja.com>% Subject: Re: Incremental backup bluesr) Message-ID: <8qongg$qd4$1@nnrp1.deja.com>s   Hello,  D This is what I recommend also (see quote below). HOWEVER, there is aF gotcha. If a user uses BACKUP to copy a file from another disk to yourD target disk, and the file's modification date is before the date youC use in the /SINCE=date qualifier, then that file will not be saved. F Using /SINCE=BACKUP will not miss such files. But in the VMS V5 manualG they recommend /SINCE=date for weekly incremental, and /SINC=BACKUP for  dailys(sp?).  E But even /SINCE=BACKUP will miss a file if it was copied from another E disk using BACKUP/RECORD and the backup date happens to be later than  the modification date!   It's always something.  7 In article <200009231631_MC2-B46D-12D5@compuserve.com>,e5   "Richard B. Gilbert" <DRAGON@compuserve.com> wrote:r? >         You can still do incremental or differential backups!a > F >         Just note the time you broke the shadow sets and, instead of > /SINCE=3DBACKUP, use > /SINCE=3D'TIME_OF_SPLIT'!i >i2 > Message text written by INTERNET:_RAQ_@yahoo.comC > >The way we do backups today is to shut down the DB's, splitt thes shadowG > sets, restart the DB's, and then let the backup run on the "inactive" 4 > shadows set members. This gives us alot of uptime. >2H > Problem is, we cant do incremental backup, since the recording pass isE > done to the "inactive" disks. When remounting the shadow member theiE > former "inactive" member with the recording pass gets overwritten -  > fair enough. >p > How could this be improved?l --E Why does "intellectual property" contain the adjective "intellectual"i$ when most of it isn't?! Really, now.   Disclaimer: JMHO Alan E. Feldmanf alan48  &-)    work: afeldmans dellnet.com    gfinet.com     & Sent via Deja.com http://www.deja.com/ Before you buy.    ------------------------------  % Date: Tue, 26 Sep 2000 07:44:41 +0200 0 From: Didier Morandi <Didier.Morandi@Easynet.fr>D Subject: Re: Interesting result from Copy/Log with version limit set* Message-ID: <39D037C8.EF4403CA@Easynet.fr>   "Dale A. Marcy" wrote: > ../.. K >      I checked the production directory and there were only 7 files therenO > instead of the 11 I copied with success messages on each one.  I deleted them O > and repeated several times until I figured out that there was a version limit P > of 7 set on the production directory.  It makes sense after figuring that out,. > but it had me confused for a couple minutes.  C Looks like you may submit an SPR. I think VMS should send a warninge@ message telling the user what happened due to the version limit.   My 2 $   D.   ------------------------------  % Date: Mon, 25 Sep 2000 16:18:12 -0500i* From: WILLIAM WEBB <WWEBB1@email.usps.gov>. Subject: More OpenVMS advertising (from the Q)- Message-ID: <0033000005168827000002L072*@MHS>g   =0A:E      I just got a postcard in the mail from the Q with the following:d        Front of Postcard:iA      =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3Do
      Open it.e  .      [graphic of skydiver, somewhat distorted]  *      Compaq OpenVMS on AlphaServer Systems  @      If you have the courage to jump, you have the power to fly.          Back of Postcard:A      =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D3$      They all thought you were crzy.  H      But you did it.  You threw yourself headfirst into the future. You=  H      decide to build a business at a time when all of the rules went ou= te      the window.  E      It used to be nine to five.  Now it's 24x7x365.  It used to be a H      store-front on Main Street, now it's a laptop anywhere on the plan= et.EH      It's called hypercompetition, and it's your compute capability tha= tuF      decides whether you're flying or just headed for the ground.  TheH      criteria for the e-commerce era IT platform are brutally simple: a= llH      performance, all the time.  Compaq OpenVMS on AlphaServer systems = isH      enterprise computing designed to defy gravity.  There's no downtim= erD      because the OpenVMS operating system runs multiple instances ofE      software at the same time.  Meaning you make upgrades or changes B      without interrupting on-going operations.  Running OpenVMS onH      AlphaServer systems further ensures high availability, as AlphaSer= veruH      systems have become synonymous with speed, agility, and reliabilit= y.E      So go ahead, jump.  Pack your own parachute.  And find out aboutc.      OpenVMS on AlphaServer systems right now.        www.compaq.com/openvms-        [AlphaPowered graphic]          # # #e  @      Cool to see VMS mentioned without one of those "other" OSs.        Way to go, guys.m        WWWebbR   =i   ------------------------------  # Date: Tue, 26 Sep 2000 01:19:33 GMT 2 From: "Zane H. Healy" <healyzh@shell1.aracnet.com> Subject: Re: MULTIA + OpenVMS,6 Message-ID: <FQSz5.771$F93.288765@typhoon.aracnet.com>  3 Robert Deininger <rdeininger@mindspring.com> wrote: E > Interestingly, the turbochannel boxes seem, on average, quite a bit/K > cheaper than the PCI boxes of the same horsepower.  I think the obscurityhJ > helps lower the price.  And there seems to be no shortage of inexpensiveK > graphics, SCSI, ethernet, and even FDDI turbochannel options.  Higher-end J > graphics boards aren't too common, but I think VMS doesn't support them 	 > anyway..  G Actually for a Hobbyist I can think of only one card that isn't readilyTI available, and that's a 100Mbit ethernet card.  However, as far as I know I it's just plain not available.  As for the higher-end graphics cards theyeL don't seem to be available to the Hobbyist on PCI systems either.  I suspectJ hobbyists might also have an easier time getting additional SCSI cards forB their Turbochannel systems.  It took me well over a year to get anL affordable narrow card supported by VMS.  I must admit I've not tried to getI my hands on any Turbochannel cards yet, but I keep seeing them available.t  E If it wasn't for the lack of 100Mbit the DEC3000 is a very attractiveeF hobbyist server.  My 3000/300LX served in that capacity quite well forJ several months until I got a DE500 for my AlphaStation 200 4/233, at which point it became the server.r  = > I've gotten the impression that DEC sold a LOT of 3000-xxx sB > turbochannel systems, and they are starting to retire in droves.  J I've gotten that impression as well, which is partially why I believe them; to be a better system for a Hobbyist VMS box than a Multia.h   			Zanes   ------------------------------  % Date: Mon, 25 Sep 2000 23:50:26 -0400o2 From: rdeininger@mindspring.com (Robert Deininger) Subject: Re: MULTIA + OpenVMStL Message-ID: <rdeininger-2509002350260001@user-2ive7tt.dialup.mindspring.com>  j In article <FQSz5.771$F93.288765@typhoon.aracnet.com>, "Zane H. Healy" <healyzh@shell1.aracnet.com> wrote:  5 > Robert Deininger <rdeininger@mindspring.com> wrote:rG > > Interestingly, the turbochannel boxes seem, on average, quite a bitrM > > cheaper than the PCI boxes of the same horsepower.  I think the obscurityIL > > helps lower the price.  And there seems to be no shortage of inexpensiveM > > graphics, SCSI, ethernet, and even FDDI turbochannel options.  Higher-end L > > graphics boards aren't too common, but I think VMS doesn't support them  > > anyway.m > I > Actually for a Hobbyist I can think of only one card that isn't readilyaK > available, and that's a 100Mbit ethernet card.  However, as far as I know ! > it's just plain not available. 8  H There is (was?) at least one available.  I think it might have been fromH Nemonix, but don't hold me to that.  When I priced it several years ago,D it was several thousand dollars.  I tried to explain to the guy thatI they were asking more for the card than the value of any machine it couldt4 go in, but he didn't seem to think it was a problem.   -- a Robert Deininger rdeininger@mindspring.coma   ------------------------------  % Date: Mon, 25 Sep 2000 16:30:41 -0300y) From: fabio_compaq@ep-bc.petrobras.com.br  Subject: New OpenVMS BooksL Message-ID: <OF1AF34E09.7B4815E9-ON83256965.006AF64F@ep-bc.petrobras.com.br>  A There are two new OpenVMS books at Amazon.com (not yet published)a  e Introduction to OpenVMS (June / 00) I requested  this but I was informed it still not published .....a  5 Writing Openvms Alpha Device Drivers in C  (Sep / 00)   
 Fabio Cardoson Analista de Suporteo   ------------------------------  % Date: Tue, 26 Sep 2000 00:16:59 -0400v2 From: rdeininger@mindspring.com (Robert Deininger) Subject: Re: New OpenVMS BooksL Message-ID: <rdeininger-2609000016590001@user-2ive7tt.dialup.mindspring.com>  w In article <OF1AF34E09.7B4815E9-ON83256965.006AF64F@ep-bc.petrobras.com.br>, fabio_compaq@ep-bc.petrobras.com.br wrote:-  C > There are two new OpenVMS books at Amazon.com (not yet published)  >   7 > Writing Openvms Alpha Device Drivers in C  (Sep / 00)-    I This one must be a new edition.  I've had a copy of the book for a couplerI of years, but there may well be some new stuff for VMS 7.?, and certainly  some new hardware information.   -- C Robert Deininger rdeininger@mindspring.com:   ------------------------------   Date: 25 Sep 2000 21:45:19 GMT& From: Cthulhu <cthulhu@kadath.deep.it>. Subject: Re: No more SYSDUMP.DMP? No more NTP?( Message-ID: <8qoh1f$pi$1@kadath.deep.it>  1 Richard B. Gilbert <DRAGON@compuserve.com> wrote:-  H >         If TCP/IP starts before DECnet phase 4, DECnet will change theK > Ethernet address and all sorts of strange things may happen on the TCP/IPD > side.E  + Ah, that's interesting... I'll try, thanks!o   	debatchingly, 	   Cthulhu    -- i  G        Ph'nglui mglw'nafh Cthulhu http://www.rlyeh.it wgah'nagl fhtgan! # 		        <cthulhu at rlyeh dot it>g   ------------------------------  % Date: Tue, 26 Sep 2000 04:53:00 +0100   From: Paul Sture <paul@sture.ch> Subject: Re: NTP with UCX 4.2l+ Message-ID: <VA.000000e1.264f43c9@sture.ch>C  D In article <wCby5.640$O7.18456@ozemail.com.au>, Antony Wardle wrote:; > From: "Antony Wardle" <antony.wardle@nnnoospam.met.co.nz>. > Newsgroups: comp.os.vmsc > Subject: Re: NTP with UCX 4.2e' > Date: Thu, 21 Sep 2000 11:25:17 +1200n > 9 > We've got it working here with the same version and 7.1o > E > WOn't be upgrading (again) to 5.0a until we can get some assurancestA > about NFS. That aside, the rest of the machines on 5.0a seem to7  > be working a whole lot better. > C > You need 5.0a if you have any linux boxes that telnet to your vms ? > hosts. We found that each telnet session would use 30% of the H > cpu, therefore 3 telnets, would have your whole cpu all to themselves. > J You should be so lucky. My MV3100 grinds to a halt with one session trying< to login. Even Monitor at priority 31 doesn't get a look in.  G Back to UCX unless I can get hold of a copy of 5.0A (or just don't use e	 telnet...  >    ___w
 Paul Sture Switzerland-   ------------------------------  % Date: Mon, 25 Sep 2000 14:21:26 -0300 ) From: fabio_compaq@ep-bc.petrobras.com.br2 Subject: OpenVMS 7.3L Message-ID: <OFEDDD4B4F.FFCC2A64-ON83256965.005F2C0C@ep-bc.petrobras.com.br>  G Any date to the release of OpenVMS 7.3 ? Do you have any idea about thee
 improvments ?t  0 Fun: It should be called OpenVMS 2000 or 2K !!!!  
 Fabio Cardosof Analista de Suporten   ------------------------------    Date: 25 Sep 2000 21:20:29 -05009 From: Kilgallen@eisner.decus.org.nospam (Larry Kilgallen)r Subject: Re: OpenVMS 7.3+ Message-ID: <tWbMh5gArZQR@eisner.decus.org>   x In article <OFEDDD4B4F.FFCC2A64-ON83256965.005F2C0C@ep-bc.petrobras.com.br>, fabio_compaq@ep-bc.petrobras.com.br writes:I > Any date to the release of OpenVMS 7.3 ? Do you have any idea about thea > improvments ?   > Their SDK #1 kit is available for purchase now, and looking at< that one should be able to get an idea of what _might_ be in; V7.3.  (One would hope that if something could not be fullyi@ debugged during the test period they would refrain from shipping it until next time.)  > They sayd there would be an SDK #2 kit, and I believe that has@ not shipped yet, so I would presume we can say the final release is "not soon".   ------------------------------  % Date: Mon, 25 Sep 2000 14:50:03 -0400 0 From: Paul Anderson <paul.r.anderson@compaq.com>& Subject: Re: OpenVMS features (future)C Message-ID: <paul.r.anderson-E207EE.14500325092000@news.compaq.com>>  G In article <39cda2b4$0$30002$2c3edae7@news.voyager.net>, Jack Patteeuw D <jjpatteeuw@voyager.net> wrote:8  F > One of the things that "slick-Bob" got rid of to woo Compaq was the G > printing group. Now everyone need to understand I am **NOT** talking nG > about printers. I **AM** talking about all of the necessary "pieces" /D > to get data from a computer system and on to paper in a reliable, D > supportabel manner. One fantastic feature of LPS printer is being E > able to "log in" to them and "read" the front panel. It's great to eC > tell a user in another building that the reason he can't get his  E > printout is because there is no paper in the printer, (or a jam in e > area 2 or ...).e  G Most printers today have an internal Web page that can be used to show n! status and configure the printer.B  H Also, most printer management is being done via SNMP with products such F as Genicom's Remote Control Software, produced by the afore-mentioned ( printing group while we were at Genicom.  I I agree that PrintServer printers had many features years ago that other i( printers are just now beginning to have.  ? > Genicom tried to "keep the faith", but that didn't last long.t  I Genicom is still around, and making new LN series printers.  It's Compaq  H that decided (again) to leave the printer hardware business.  (They had G left the business in 1995 and a half-done project of theirs was bought i) by Digital and became the DEClaser 3500.)s  ? > What we really need is support for all of the "user" feature /A > (single/double side, number up, ANSI, Postscript, forms, etc.) tC > supported on the latest version of "popular" printer such as HP, n0 > Lexmark, etc. Notice I said "latest versions".  G Now that there is no in-house brand to protect, expect DCPS to support  I other vendors' printers more aggressively.  We are now creating the list  5 of printers we will include in the next DCPS version.t   Paul   -- D,    Paul Anderson, OpenVMS Engineering (DCPS),    Compaq Computer Corporation, Littleton MA   ------------------------------  % Date: Tue, 26 Sep 2000 04:45:05 +0100v  From: Paul Sture <paul@sture.ch>3 Subject: Re: Porting Support (was Compaq VMS promo)i+ Message-ID: <VA.000000e0.264804a8@sture.ch>-  B In article <8qnoil$9nk$1@info.cs.uofs.edu>, Bill Gunshannon wrote:3 > From: bill@triangle.cs.uofs.edu (Bill Gunshannon)t > Newsgroups: comp.os.vmst5 > Subject: Re: Porting Support (was Compaq VMS promo)C  > Date: 25 Sep 2000 14:47:49 GMT > Reply-To: bill@cs.uofs.edu > - > In article <VA.000000d7.17534fa1@sture.ch>,e% >  Paul Sture <paul@sture.ch> writes:i > |>  M > |> As someone who has tried to use StarOffice, I must add my 2 cents. It isTR > |> far from the panacea which folks here maybe think it is. I have tried variousZ > |> versions over the last 18 months, including the free CD from Sun, and that particularZ > |> version failed with being unable to import such a basic thing as tab delimited files. > R > Well, just to keep things balanced, I have installed it on numerous RedHat LinuxS > and Windows95/98 systems without a hitch.  It isn't MS Office, but it offers mosta > of the functionality.a >l
 Fair comment.i   > |> tV > |> I note that the Sun Linux version also failed the basic test of running accordingW > |> to the installation instructions, although the installation procedure _was_ slick. ] > |> (Invoking it was not per the instructions - you have to go down an extra directory levelpU > |> before typing "soffice" - far from trivial as I effectively had to do a completeea > |> disk search to find out where the thing was (and yes, a search of "soffice" produces all the M > |> files contained in a directory tree of that name), not friendly at all).a > N > Yes, but as has been proposed, one of the requirements of the VMS port wouldM > be documentation.  In my humble opinion, that means accurate and functional4L > documentation.  Lack of good documentation is as much the bane of the free* > software world as poor coding practices. >I Agreed.d > |> sX > |> My most recent experience with StarOffice came with Suse Linux V7.0 (last weekend).d > |> According to the literature, they (the way it's written, it sounds like Suse did it themselves)_ > |> have done extra work on import/export filters, but I cannot tell as yet, because the thingfT > |> doesn't run after installation, stating that some shared libraries are missing. > P > That's most likely a Linux thing rather than a StarOffice thing. even the mostO > current configurations come in different and incompatable configurations. Onel8 > would linkt that would not be a problem with VMS.  :-) > J Yep. :-) Of course, VMS could throw up link id mismatches and the like :-) > |> <M > |> I'm sorry, but if those currently distributing the thing cannot get the rL > |> installation right, there's a lot of hard work to be done. OK, I've gotR > |> my 60 days free support from Suse to help me, but it's still "not there yet". > P > Two points.  One.  What incentive do the current distributors have to care one > way or the other??    _ In Suse 7.0's case, StarOffice is one of the highlights featured on the outside of the box, ande^ choosing the installation of "Default with Office" leaves out those libraries, so, yes I would/ think they have some incentive to get it right.s  ? A pity, because it spoilt what was a _very slick_ installation.r  = >Two. That's the reason for suggesting a grant to pay for the P > porting.  Free is nice, but you get what you pay for.  The advantage here is aK > major portion of the grunt work of development has been done, not only on P > StarOffice, but on a lot of other packages as well.  While not a trivial task,N > porting to VMS is probably a lot less intensive than writing equivalent apps > from scratch.  >  > |> ,N > |> > :My suggestion was for someone, Compaq (except they don't seem to care M > |> > :much)... to put together a grant to provide some ... schools who are DQ > |> > :interested with some hardware and software and funding to hire promising k* > |> > :students to actaully do the ports. > |> > eK > |> >   A good idea, though there is an associated cost beyond the obviousdN > |> >   financials -- we would want to work with and support the effort, and M > |> >   to track the progress of the porting work.  I'll suggest this optioniO > |> >   as part of some other related (and currently unspecified) discussions uL > |> >   pending or associated with this particular group of customers.  We O > |> >   have already provided hardware and support to individuals and groups, -M > |> >   assistance for the folks that have been porting particular software 1E > |> >   packages over to OpenVMS -- ample precedent, in other words.g > Q > Requiring periodic reports or even periodic public announcements and maybe evenlR > code releases would seem to me to be well within the domain of whatever grant is	 > made.  3 > 	 > |> >   DW > |> Well, I'd rather see Compaq taking an interest in the WordPerfect office suite :-) [ > |> Quite some risk of incurring Redmond's wrath, but potential income from day one on thep > |> PC front... > O > WordPerfect Office was available for VMS at one time.  But again, people seemDL > to be zeroing in on a single application and now even a proprietary one.    \ I believe that the version of WP available on VMS was the "good for it's day" DOS lookalike.G WP for Linux is somewhere on this box, although I've yet to try it out.f     > MyM > proposal was for taking the wealth of free software that is making Linux soaN > popular and putting that on VMS.  If all we're going to see is another $5000N > application, we will still be discussing why no one wants to use VMS 5 yearsQ > from now.  It wasn't the availability of WordPerfect for Linux that contributedlD > to it's popularity.  They were a johnny-come-lately in that arena. > X OK, I was thinking along the lines of Compaq doing with WP what Sun are doing with SO... > |> rU > |> I note that for some time, Corel have been struggling financially, and have justtW > |> this week found a mystery investor. I sincerely wish it were Compaq, but only timeg > |> will tell.n > |> nM > |> Whoever it turns out to be may be receptive to the idea of a VMS port...= > K > Which as i said above, is highly unlikely to change anything form what we  > have right now.d   ___ 
 Paul Sture Switzerland    ------------------------------  % Date: Mon, 25 Sep 2000 19:35:46 -0400 - From: JF Mezei <jfmezei.spamnot@videotron.ca>g* Subject: Postscript file operations on VMS, Message-ID: <39CFE141.871EA1F5@videotron.ca>  H Yesterday, I needed to convert some image data whihc was encoded as RGBW 78byte sequencesK (78 bytes red, 78 bytes Green, 78 bytes Blue, 78 bytes grayscale) into just.L RGB. This was very easy on Postscript (since these were part of a postscriptI file), except that that CDA viewer on VMS doesn't supoprt file operationsnE (attempting to write to a VMS file with the writehexstring statement)h  E I ended up doing this on a MAC with the acrobat disliller which, upon 0 executing the code, wrote my data to a mac file.  K Is there some V'S based postcript software that ia capable of handling filel operations ?   ------------------------------    Date: 25 Sep 2000 21:24:47 -05009 From: Kilgallen@eisner.decus.org.nospam (Larry Kilgallen) . Subject: Re: Postscript file operations on VMS+ Message-ID: <eSSYrKleQPE9@eisner.decus.org>o  \ In article <39CFE141.871EA1F5@videotron.ca>, JF Mezei <jfmezei.spamnot@videotron.ca> writes:J > Yesterday, I needed to convert some image data whihc was encoded as RGBW > 78byte sequencesM > (78 bytes red, 78 bytes Green, 78 bytes Blue, 78 bytes grayscale) into justnN > RGB. This was very easy on Postscript (since these were part of a postscriptK > file), except that that CDA viewer on VMS doesn't supoprt file operationslG > (attempting to write to a VMS file with the writehexstring statement)c > G > I ended up doing this on a MAC with the acrobat disliller which, uponL2 > executing the code, wrote my data to a mac file. > M > Is there some V'S based postcript software that ia capable of handling fileh > operations ?  H You could ask that Applied Synergy include it in V1.1 of the PDF Viewer.C Postscript is quite similar to PDF, and that product is still underh development.   ------------------------------  % Date: Mon, 25 Sep 2000 18:25:33 +0100   From: steven.reece@quintiles.com Subject: Re: Press ReleaseH Message-ID: <OFD7228861.7BC0E6EE-ON80256965.005F99D6@qedi.quintiles.com>  . So NT Systems people don't play for long then?E BTW, I have got two, I got one in Vienna (that seems to be a lot moret liberal than the UK too).    Alan Greig wrote:$G >>>Well we did actually get two. Our NT Systems manager received one ascE well much to his surprise. He suggested that Microsoft could send out B their own but with the covering note saying: "One of our customers> recently reminded me how often you have to reboot NT so here's. something to play with while your waiting".<<<   ------------------------------  % Date: Mon, 25 Sep 2000 18:11:33 -0700n! From: Koloth <koloth@tmisnet.com>o Subject: Re: Press Release+ Message-ID: <39CFF7C5.D9FDEDD6@tmisnet.com>d  F This is a little OT.  But at our last DECUS LUG meeting we were asking) people for topics to future LUG meetings. I One person asked, in a truly genuine way, if there was any way to improve J the up time of Windows NT.  There was a stunned silence as all the OpenVMSH people looked at each other in disbelief.  Needless to say we had a good laugh.  ! steven.reece@quintiles.com wrote:v  0 > So NT Systems people don't play for long then?G > BTW, I have got two, I got one in Vienna (that seems to be a lot morei > liberal than the UK too).t >e > Alan Greig wrote:rI > >>>Well we did actually get two. Our NT Systems manager received one as-G > well much to his surprise. He suggested that Microsoft could send out_D > their own but with the covering note saying: "One of our customers@ > recently reminded me how often you have to reboot NT so here's0 > something to play with while your waiting".<<<   ------------------------------  % Date: Mon, 25 Sep 2000 18:06:09 +0200i= From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com>p- Subject: Re: reading VMS files with Delphi... ) Message-ID: <39CF77F1.17E980B5@gtech.com>-   Pedro Viena wrote:C > Is there any way to read VMS files using Borland Delphi in a PC ?s  C You are not very specific about what you want, but here are my bestD suggestion:-% - install PathWorks on the VMS systemn< - create a share on the VMS system and map a drive on the PC2 - just open the file as any other file from delphi   Arne   ------------------------------  % Date: Mon, 25 Sep 2000 18:08:48 +0200p= From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com>() Subject: Re: remote login using .com filei) Message-ID: <39CF788F.67F9D27D@gtech.com>l   krish wrote:K >  I have two machine "A" and "B" at different destinations. Sitting at A iwI > want to run a .COM file , that will automatically execute a   .exe file-L > residing at "B". One way of doing this is specifying a command line insideA > the .COM with "command" decnet-nodename, username and password.  > 3 >  eg     $ dir 2.889"user password"::dka0:[000000]  > K > But i would like to know if there is any equivalent way of doing it usingE > TCP/IP protocol.  - DECnet are way ahead of TCP/IP at this level.s  B The closest TCP/IP feature will probably be NFS mounting of disks,+ but that can be a major task to implement !n   Arne   ------------------------------  % Date: Mon, 25 Sep 2000 17:58:07 +0200 = From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com>-= Subject: Re: Replacing system disk, will licenses still work?0) Message-ID: <39CF760E.A55FCCD8@gtech.com>j   Charles Gilley wrote:lP > I want to cold-spare a system drive on a VAX4300.  I make a stand-alone backupL > tape of the existing system image and blast it onto a replacement disk.  I7 > would think that the licenses should still load, yes?c   Yes.  O > Under what hardware circumstances would the licenses not load, replacement ofiO > motherboard?  Network card?  From unix-land, many licenses like to tie to theu. > physical network address.  Does VMS do this?  H If you replace the motherboard with another type of (bigger) motherboard
 it may break.   F A new board of the same type, firmware upgrade, change of netcard etc., will not break licenses from Digital/Compaq.   Arne   ------------------------------  # Date: Mon, 25 Sep 2000 23:00:09 GMTs. From: Murray.Dawson@anu.edu.au (Murray Dawson)= Subject: Re: Replacing system disk, will licenses still work?a3 Message-ID: <39cfd77c.63734120@newshost.anu.edu.au>n  2 On Mon, 25 Sep 2000 00:04:07 -0400, David A Froble <davef@tsoft-inc.com> wrote:   >Murray Dawson wrote:  >> -5 >> On Fri, 22 Sep 2000 01:36:28 -0400, David A Froble: >> <davef@tsoft-inc.com> wrote:e >> p >> >Charles Gilley wrote:O >> >>7T >> >> I want to cold-spare a system drive on a VAX4300.  I make a stand-alone backupP >> >> tape of the existing system image and blast it onto a replacement disk.  I; >> >> would think that the licenses should still load, yes?a >> >/ >> >Even better, do an IMAGE copy disk to disk.- >> -H >> Forgive my ignorance, but how would you go about doing an IMAGE copy? >> s
 >> Thanks, >> Murray Dawson >R0 >First, I'll refer you to the FINE help utility. >s ...  <snip some helpful info>  > Thanks for all your help guys - I think I might give it a try.E I'm a Unix guy and I've just inherited a VMS telescope control system7E and it's non-functional backup machine (the SCSI disk is dead). I waskC going to take the disk out of the good machine and dump it to a newa@ disk using dd on a Unix box, but now I'll try doing it in place.   Ta,s
 Murray Dawsonn   ------------------------------  % Date: Mon, 25 Sep 2000 21:33:23 -0500i7 From: "David J. Dachtera" <djesys.nospam@earthlink.net>D= Subject: Re: Replacing system disk, will licenses still work?r- Message-ID: <39D00AF3.613FD81B@earthlink.net>n   Murray Dawson wrote: > 4 > On Mon, 25 Sep 2000 00:04:07 -0400, David A Froble > <davef@tsoft-inc.com> wrote: >  > >Murray Dawson wrote:O > >>7 > >> On Fri, 22 Sep 2000 01:36:28 -0400, David A Froble4! > >> <davef@tsoft-inc.com> wrote:n > >> > >> >Charles Gilley wrote:@ > >> >>gV > >> >> I want to cold-spare a system drive on a VAX4300.  I make a stand-alone backupR > >> >> tape of the existing system image and blast it onto a replacement disk.  I= > >> >> would think that the licenses should still load, yes?t > >> >1 > >> >Even better, do an IMAGE copy disk to disk.  > >>J > >> Forgive my ignorance, but how would you go about doing an IMAGE copy? > >> > >> Thanks, > >> Murray Dawson > > 2 > >First, I'll refer you to the FINE help utility. > >  > ...o > <snip some helpful info> > @ > Thanks for all your help guys - I think I might give it a try.G > I'm a Unix guy and I've just inherited a VMS telescope control systemtG > and it's non-functional backup machine (the SCSI disk is dead). I wastE > going to take the disk out of the good machine and dump it to a newgB > disk using dd on a Unix box, but now I'll try doing it in place.  - You'll want to look through the on-line HELP.g  F Unlike "man", you don't need to know what you're looking for - you can: get a list of topics and sub-topics at each level of HELP.   --   David J. Dachterao dba DJE Systemst http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/h  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: 25 Sep 2000 18:33:15 -05002 From: malmberg@eisner.decus.org (John E. Malmberg). Subject: Re: restart an Alpha ETN42-CA machine+ Message-ID: <6bIFtNBQIGWt@eisner.decus.org>s  * In article <39CF8BB7.B9B8F070@Easynet.fr>,2 Didier Morandi <Didier.Morandi@Easynet.fr> writes: <snip>  = I have a similar looking box next to me right now.  But it isi designated ETM10-AD.  N I have no idea if this is or is not what you have, but here is a descripton of it.   E It is basically a system custom made out of the following components:0  % System Cabinet, floppy, power, cdrom.u  7 Processorless backplane that accepts standard PC cards.-8 I have not opened it in a while so I do not remember the
 exact layout.u  C It has a card known as a PICMG SBC that has an ALPHA on it and somel4 memory, plus the keyboard, mouse, and a serial port.  * A video card and network card are present.  . SCSI is available internally and possibly IDE.  F The PICMG SBC processor cards were designed for imbedded applications,! not normal desktop or server use.>  C The box I have in front of me was assembled as a demonstration unitnE of the components and was intended for doing the software developments2 of applications to be hosted on the target system.  * And now the answer to everyone's question:  F According to the OpenVMS S.P.D., there are 4 PICMG SBC models that areD supported.  If your unit contains one of them, and the other options9 in your system are supported, then you can put VMS on it.   N Opening up your case would probably be the next step so that you can determineL what you have exactly.  If it is indeed a PICMG SBC based system, one of theI things to try searching for on the Compaq Web sites is "Modular Computing 
 Component"   -Johni wb8tyw@qsl.network   ------------------------------   Date: 25 Sep 2000 22:09:51 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman). Subject: Re: restart an Alpha ETN42-CA machine6 Message-ID: <8qoiff$9d1$1@mailint03.im.hou.compaq.com>  ] In article <39CF4BAC.72616030@Easynet.fr>, Didier Morandi <Didier.Morandi@Easynet.fr> writes: ? :I was given a few months ago an ALPHA desktop type ETN42-CA...y  B   This part number was assigned to the Alpha 21066 series 233 MHz    processor motherboard.  : :without terminal or anything else. No cable, no nothing.  .., :(is there a system console on a ETN42-CA?).     As the SRM requires it, yes.  H :I have some difficulties to do the correct cabling. Should I use port A+ :and connect it to the COM1 port of the PC?i  +   Get the PC side straightened out first.     8 :what should be the parameters? 8-0-N/XonXoff as usual?   /   That would be my assumption.  9600 baud, too.o  F   Both systems *probably* use the DB9 PC pinout.  I do not know if youC   will need a null-modem (cross-over) cable, but would guess "yes".a  ; :All of this doesn't give any noise on the terminal screen.i  E   Flip the transmit and receive (cross-over).  Then try another port.sF   Or better, go get yourself a break-out box -- having access to this =   tool is invaluable to anyone working on serial line wiring.r  G :I also tried to connect the PC on the printer port, as before when onemH :has a vaxstation without terminal :-). I selected the speed from 300 to :19200, no more success.  C   Don't bother with baud rate to start with, just look for garbage sB   output -- if/when you see garbage on the display, _then_ try theC   baud rate.  And start with 9600 baud, as that is the most common      speed used for Alpha consoles.  A :Could someone tell me what is the regular hardware configuration  :requested to use an ETN42-CA? o  >   OpenVMS does not officially support the ETN42-CA platform.    /   OpenVMS may or may not work on this platform.n  H   I have no idea if OpenVMS has even a chance of bootstrapping, but the G   21066 Alpha microprocessor was used in the Tadpole ALPHAbook, in the o%   Multia, and in the AXPpci33 widget.o  < :(what is is, btw, a real Alpha or a PC with an ALPHA chip?)  E   The 21066 microprocessor used in the ETN42-CA was intended to be a iD   lower-cost and more highly integrated version of the 21064 series B   microprocessor, but it is as much a real Alpha microprocessor as7   any other.  Just a rather more rarely seen example...g  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Mon, 25 Sep 2000 19:13:18 -0500>, From: "Glenn C. Everhart" <Everhart@GCE.com> Subject: Safety SPDa' Message-ID: <39CFA3CE.5AF8172F@GCE.com>n  ; I was surprised to get an email that someone thought SafetytA replaces the DELETE command. That is not the case; it changes theh. filesystem semantics a bit for selected disks.  > Here is my SPD. If someone is interested in paying for support8 that can be arranged, but in general I just give it out.   Glenn Everhart Everhart@gce.com               Software           Productp           Descriptiong             Safety V1.4a9           Comprehensive Data Safety for your VMS systems.e  -           from General Cybernetic Engineeringe             Executive Summary:  E           There are many perils your data faces, and loss of data cane costD           time, money, and jobs. Intruders, disgruntled insiders, orF           hidden flaws in installed software can destroy records. What is1           more, mistaken losses occur constantly.   E           Safety protects your system and your critical data in threec           ways:o  B           1. A comprehensive security system adds extra checks for accessB           to VMS files so that access by intruders or by people inC           non-job-required ways can be regulated or prevented. Thisi allowsG           your business - critical data to finally be protected againstxA           misuse, tampering, or abuse. Access from programs doing G           background dirty work (viruses, Trojans, worms, and the like,L orB           even programs with security holes which can be exploitedD           remotely (like Java browsers)) can also be blocked withoutG           damaging normal use. This active protection works three ways:r byC           checking integrity    of your files against tampering, byjF           preventing of  untrusted images from  gaining privilege, and byH           regulating what other parts of the system an image may access.  D           2. A deletion protection system provides a way to undelete filestF           which were deleted by mistake and to optionally copy deletedE           files to backup facilities before removal. Unlike all othera VMSrH           "undelete" programs on the market, this facility does not relyA           on finding the disk storage that contained the file and H           reclaiming it before it is overwritten. Rather, it changes theD           semantics of the file system delete to use a "wastebasket"F           system and captures the file intact. Thus, this system worksH           reliably. No others do. This facility is also useful where youB           have a requirement to keep all files of a certain set of types,E           since the backup function can be used to capture such filesy@           while permitting otherwise normal system function. The shelvingC           or linking functions are also available for moving copiesnE           offline if this is desired. The  Safety protection features  areiC           fully integrated with the DPS subsystem, so that deletionh?           protection does not involve destroying file security.o  E           3.  When space runs out, hasty decisions about what to keep-H           online often must be made, and the risk of accidentally losingA           something important is high.   Safety protects you fromr runningoE           out of space. Space can be monitored and older items in thetC           wastebasket deleted if it is becoming low, without manualoF           intervention. In addition, Safety  is able to "shelve" files soH           that they are stored anywhere else desired on your system, andD           they are brought back automatically when accessed. Thus noF           manual arrangements need be made for reloading them.  Safety canaC           also keep the files on secondary storage, keeping a "softo link"tF           to the files at their original site so they will be accessed onH           the secondary storage instead. Also,    Safety can store filesD           compressed, or can store them on secondary storage so that readC           access is done on the secondary storage, but write access  causesG           the file to be copied back to its original site. Standard VMSiG           utilities are used for all file movement, and moved files are-G           also directly accessible in their swapped sites with standardvH           VMS utilities. The VMS file system remains completely valid at           all times.  G           Safety gives you a full complement of tools  for dealing witheC           space issues automatically according to your site policy.m TheseiE           facilities are safe and easily understood.  A comprehensive B           utility is provided by which you set your site policy to selectF           which files are and are not eligible for automatic shelving.C           Also you are provided with screen oritented utilities fortF           selecting files to shelve at any time. Access to the shelved9           files of course causes unshelving if the normal2 shelving-by-copyC           mode is used. Also, a simple set of rules permit locatingaD           shelved or softlink target files at any time, even withoutC           Safety running.   Safety at no time invalidates your filecE           structures for normal VMS access...not even for an instant.f  H           In addition Safety contains functions to speed file access and%           inhibit disk fragmentation.l  ?           The major subsystems of Safety will now be described.a'           The Security Function System:v           Summary:E           Managing access to data critical to your business using ACLiA           facilities in native VMS can be cumbersome and still iseE           vulnerable to intruders or people acting in excess of theirm           authority.  F           Want to be sure your critical records can't be accessed save atB           authorized places, times, and with the programs that are>           supposed to access them (instead of, say, COPY.EXE)?  E           Want to have protection against privileged users bypasssing-           access controls?  ?           Want to be able to password protect individual files?<  ?           Want to be able to invisibly hide selected files fromi!           unauthorized intruders?5  E           Have you read that attacks on machines can happen because au JavaF           browser points at a web site that damages the system (as hasF           been reported in the press)? Want to be able to protect your           systems?  G           The Safety security subsystem builds in facilities permittingnF           all of these, and is not vulnerable to intruders who disable theoG           AUDIT facility as all other commercial packages which purporte to           monitor access are.r  G           Description: When your business depends on critical files, or =           when you are obliged by law or contract to maintainsC           confidentiality of data on your system, in most cases theo?           options provided by VMS for securing this data can beo
 cumbersome%           and far too coarse-grained.   G           The problem is that certain kinds of access to data are often @           needed by people in a shop, but other access should be	 prevented H           and audited. Moreover, the wide system access that can come as aaH           result of having system privileges often does not mean that itA           should be used to browse or disclose data stored on the  system. E           A system manager will in general not, for example, have any1G           valid reason to browse the customer contact file, the payrollcG           database, or a contract negotiation file, save in a few casess@           where these files need to be repaired or reloaded from backups.E           Likewise, a payroll clerk may need read and write access to  theeE           payroll file, but not in general with the COPY utility, nor  fromG           a modem, nor in most cases at 4AM. Finally, a person who mustt?           have privileges to design a driver and test it shouldo
 ordinarily6           not have the run of the file system as well.  B           Given examples like these, it is easy to see that simpleG           authorization of user access to files is inadequate. While itt isE           possible to build systems that grant identifiers to attempte someD           extra control, these can be circumvented by privilege, andE           create very long ACLs which become impossible to administeru over-           a long period as users come and go.R  A           What is needed is a mechanism that is secure, cannot be7E           circumvented by turning on privileges, and which provides a E           simple to administer and fine grained control that lets you G           specify who can get at your critical files, with what images,s@           when, from where, and with what privileges. It is also	 desirabletH           to be able to control what privileges the images ever see, andB           to be able to check critical command files or images forC           tampering before use, so that they cannot be used as backs doors>?           to your system. It should be possible to demand extraiG           authentication for particular files as well, and to prevent a>F           malicious user from even seeing a particularly critical file,           unless he can be permitted access.  H           The Safety security subsystem is a VMS add-in security packageF           which provides abilities to control security problems due toB           intruders, to damage or loss by system "insiders" (usersC           exceeding their authority), and to covert code (worms anduE           viruses). It provides a much easier management interface tor@           handle security permissions than bare VMS and providesA           facilities permitting control over even privileged filehD           accesses, for cases where there are privileged users whoseG           access should be limited. Unlike systems which only intercepttF           the AUDIT output, EACF can and does protect against ANY file=           accesses, and can protect files against deletion byO unauthorizedD           people or programs in real time as well as against access.  <           The Safety security subsystem offers the following
 capabilities:a  D           * Files can be  password protected individually. If a file openD           or delete is attempted for such a file and no password has been,           entered, the open or delete fails.  F           * Access can be controlled by time of day. Added protections canrF           be in place only some of the time, access can be denied someF           times of day, write accesses can be denied at certain times, or<           various other modalities of access can be allowed.  F           * You can control  who may access a file, where  they may be (orxH           may not be),  with what images  they may or may not access theC           file, and with what privileges  the file may be accessed.  Thus, D           for instance, it is trivial to allow a clerk access to theF           payroll file with the payroll programs, but    not with COPY orF           BACKUP, not on dialup lines, and not if they have unexpectedE           privileges. The privilege checks can be helpful where therec areeH           consultants working on a system who should be denied access toD           sensitive corporate information but who need privileges toD           develop programs, or in similar circumstances. You specify whatF           privileges are permitted for opening the file, and a processA           with excess privileges is prevented  from access. Vitala businessD           data access should not always be implied by someone havingF           privilege. With this system you can be sure your proprietaryF           plans or data stay in house, and are available only to thoseE           with business reasons to need them, not to everyone needing H           system privileges for unrelated reasons. Unlike packages usingG           the VMS Audit facility's output (which can be silently turnediF           off by public domain code),   Safety cannot  be circumvented byG           well known means. Its controls are designed to leave evidence  of*           what was done with them as well.  A           * You can specify that images able to run portable codek (applett>           viewing programs or programs with powerful scripting
 languages)B           trigger a "paranoid mode" system. When this is triggeredG           (normally when the "loading" image is active), all file openseG           by the process running the triggering image are filtered by aaF           script. This script can be different for different programs,B           and is site customized. The furnished sample script willF           broadcast the identity of user and of files being opened. It is>           trivial to arrange to limit this to unusual files or
 filesystem=           areas.  The script can also veto the open. Thus then recommendedoD           way to treat web browsers is to limit their file access so theyH           may read system areas and a scratch area, and may write only aG           scratch area. (The script is informed whether the open is forpF           read or for write.) This "low-integrity-image" mode in whichH           all file opens are checked with a site script which can reportF           or veto access. This can be used to track or regulate what aE           Java applet can do, in case someone happens to browse a web-B           site which exploits a Java hole to browse your system or damageF           it. The site script can of course arrange for further Safety'           controls, among other things.m  H           * You can  hide files from unauthorized access. If someone notG           authorized to access a file tries to open it, they can be setA to>           open instead some other file anywhere on the system.
 Meanwhile,H           Safety generates alarms and can execute site specific commandsG           to react to the illegal access before it can happen. This canE beC           helpful in gathering evidence of what a saboteur is up to H           without exposing real sensitive files to danger. Normal access%           goes through transparently.   F           * You can arrange that opening a file  grants identifiers to theuA           process that opens it and that closing it revokes thesehH           identifiers. Set an interpretive file to do this and set it toF           be openable only by the interpreter and you have a protected<           subsystem capability that works for 4GLs which are
 interpretive.nG           (Safety identifier granting, privilege modification, and baser=           priority alteration is protected by a cryptographicu;           authenticator preventing forging or duplication.)e  E           * You can actively prevent covert code ( viruses and worms)t from;           running in two ways. First,   Safety can attach a0
 cryptographicsG           checksum to a file such that the file will not open if it hassD           been tampered with. Second,  Safety can attach a privilege maskB           to a file which will replace all privilege masks for the processfF           that opens it. By setting such a mask to minimal privileges, youfB           can ensure that an untrusted image will never see a veryD           privileged environment, and thus will be unable to performH           privilege-based intrusions into your system even if run from a$           privileged user's account.  <           * You can  control base priority by image. Thus, a particularlyE           CPU intensive image can be made to run at lower than normalh base3           priority even if it is run interactively.E  H           * You can run a site-chosen script to further refine selectionH           criteria. (Some facilities for doing additional checking while$           an image runs exist also.)  A           Safety  allows you to exempt certain images (e.g., disk-H           defragmenters) from access checks, and it is possible to put aG           process into a temporary override mode also (leaving a record-E           this was done) where this is needed.     Safety  facilitiesC arer@           controllable per disk, and impose generally negligible	 overhead.FH           Safety  will work with any VMS file structure using the normalH           driver interfaces. Also,   Safety  marking information residesE           sufficiently in kernel space that it cannot be removed fromeD           lower access modes, yet it uses a limited amount of memory$           regardless of volume size.  E           Best of all, the Safety  protection is provided  within the  fileD           system  and does not depend on the audit facility. Thus itH           prevents file access or loss   before it happens, and does notG           have to react to it afterwards.      Safety allows all of itsr@           security provisions to be managed together in a simpleE           screen-oriented display in which files, or groups of files,  canlC           be tagged with the desired security profiles or edited aslE           desired.  Safety  protections are in addition to normal VMSo fileF           protections, which are left completely intact. Therefore, noE           existing security is broken or even altered. Safety  simply  addsE           additional checking which finally provides a usable machine D           encoding of "need to know" for the files where it matters.      3           The Safety Deletion Protection Subsystem.u    @           Description: The Safety  Deletion Protection System is designedC           to provide protection against accidental deletion of fileo typesiD           chosen by the site, and to allow files to be routed by theE           system to backup media before they are finally removed from. the C           system. This is accomplished by an add-in to the VMS filey systemC           so that security holes are not introduced by the system'si           action.   F           The user interface is an  UNDELETE command which permits one orH           more files to be restored to their original locations providedC           it is issued within the site-chosen time window after theoB           undesired deletion took place. In addition, an   EXPUNGE commandU?           is provided which allows files to be deleted at once,eH           irretrievably, where space for such is required. Provision forD           automatic safe-storing of files prior to final deletion is%           present also in Safety DPS.   E           Safety DPS is implemented as a VMS file system add-in whichtE           functions by intercepting the DELETE operation and allowingi the G           file to be deleted to be copied or renamed to a "wastebasket"qG           holding area pending final action, and to be disposed of by ahH           disposal agent. The supplied agent will allow a site script toE           save the files if this is desired, and then finally deletesn anyfG           files which have been deleted more than some number N seconds F           ago. If the UNDELETE command is given, the file(s) undeleted aredH           replaced in their original sites. The supplied system can alsoH           be configured to rename files to a wastebasket area or to copyF           them directly, for undeletion by systems people only. (These@           options are faster than the site command file option.)  F           Safety DPS can be configured to omit certain file types fromE           deletion protection (for example, *.LIS* or *.MAP* could beeH           omitted), to include only certain files in the protected sets,E           or both. This can reduce the overhead of saving files which  aredF           likely to be easily recreated, or tailor the system for suchB           actions as saving all mail files (by selecting *.MAI for           inclusion).l  H           In addition, Safety DPS monitors free space on disks, and when a F           file create or extend would cause space exhaustion,   Safety DPSeE           runs a site script. By setting this script to perform final H           deletions, Safety DPS can be run in a purely automatic mode inF           which deleted files are saved as long as possible, but never@           less than some minimum period (e.g., 5 or 10 minutes).  F           Safety DPS files can be stored in any location accessible toE           VMS. If they are renamed, they must reside on the same disks theyG           came from. Otherwise they can be stored in any desired place.l  H           Safety DPS is installed and configured using a screen oriented@           configuration utility to set it up, and basically runs$           unattended once installed.        0           The Safety Storage Migration Subsystem               Description:  G           Safety has the ability to move files to secondary storage andeB           automatically retrieve them when they are accessed. This backingtG           can be similar to what HSM systems call "shelving", though ittD           can be done in multiple levels, or it can be done in a way whichvG           permits files moved to secondary storage to be accessed thereb asC           though the files remained online. This resembles what aren called>           "soft links" in Unix systems, in that file opens areB           transparently redirected to a file stored somewhere elseH           reachable on the system, and the channel reset to the originalG           device on close. A "readonly link" mode acts like a soft linkaE           for readonly access, and like an unshelve operation where as fileD           is opened read/write, should this be desired. Full control over3           this shelving and unshelving is provided.   G           This provides a great deal of flexibility in reclaiming spacenF           when the Safety space monitoring function detects that space isH           needed. Not only can previously deleted files be finally movedH           to backup destinations and deleted, but the system can migrateF           seldom accessed files to nearline storage transparently. TheG           site policy can drive this, or utilities provided can be used            instead.  C           Where it is chosen to run  Safety in a lights-out fashionl (withsB           Safety reacting to low disk situations by emptying older deleteddE           files from the wastebasket and/or file migration to backing C           store), the policy chosen for controlling such setting is D           handled by a full-screen, easily used, tool which sets theA           policy. Should still greater flexibility be needed, theo scripts F           used for a number of operations are supplied together with a?           full description of the command line interface of theo
 underlyingH           software. This facilitates linking      Safety file management?           functions with other packages should such be desired.   C           Safety can be run in a mode where there is essentially no F           overhead at all imposed (just a few instructions added alongC           some paths and no disk access) for any files except thosen whichdE           need softlinks or possible unshelving. There is no limit to  howoC           many files may be so marked on a disk. A fullscreen setups scriptG           allows one to select the   Safety run modes. Even if   Safetyl isD           forced to examine all files for its markings, the overheadG           imposes no added disk access and costs only a tiny added timedF           (typically a percent or two) in open intensive applications. In>           addition, Safety can be turned off or back on at any
 convenientH           point should this be desired. (This must be done using specialD           tools provided for use by those specially authorized to do so.)             Support:  A           Safety runs on VAX VMS 5.5 or greater or AXP VMS 6.1 or. greater.G           The same facilities exist across all systems. Safety  must be G           installed on each cluster node of a VMScluster where it is to  beD           used but imposes no restrictions on types of disk it works for.G           Safety will work with any file structure used by VMS, so long  asH           a disk class device is used to hold it. It is specifically NOT*           limited to use with ODS-2 disks.    F           Safety  is available for 45 day trial use licenses or can beH           licensed permanently. Safety is available for 45 day trial useF           licenses or can be licensed permanently.  Safety is required onG           every node of a cluster using it, or its benefits will not be H           available on nodes not having the software running. Apart fromE           this, there are no problems with having Safety available ond onlyG           part of a VMS cluster. (Actually the version out there has nor? 	  license expiration; it just runs. This is a kind of old SPD.aB           For support you need to get in touch though. THAT is not free.)        &           Safety  is brought to you by  (           General Cybernetic Engineering           Glenn C. Everharta           156 Clark Farm Roadc            Smyrna, Delaware 19977           302 659 0460 voice           302 659 5870 fax  A           For orders, contact the above address or Sales@GCE.COM.i8           For technical information contact Info@GCE.Com    -           For support contact Support@GCE.Comi   ------------------------------  % Date: Mon, 25 Sep 2000 17:58:43 +0200h= From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com>s Subject: Re: set watch) Message-ID: <39CF7632.20C96F03@gtech.com>i   dejamalc@my-deja.com wrote:l? > Are there any other options for "set watch" other than FILE ?i   To my best knowledge: no !   Arne   ------------------------------  % Date: Mon, 25 Sep 2000 20:51:32 +0000e- From: SysAdmin <djesys.nospam@fsi.net.mapson> : Subject: Re: Son of BUT... (Re: Why are these files open?). Message-ID: <39CFBAD4.B07758F1@fsi.net.mapson>   bill robertson wrote:  >  > bill robertson wrote:  > 2 > > So, how do I get rid of those INSTALL entries? > T > I received a number of posts in response to this, which I'll attempt to summarize: > : > "David J. Dachtera" <djesys.nospam@earthlink.net> writesK > | "That I know of, the only way to clear these out is gonna be a reboot."i > W > I can't say with absolute certainty, but I believe, that the system has been rebootedf9 > several times since these version 1 files were present.o  ) Umm, sorry, guy, but that's not possible.   H These are in-memory data structures that are created AFTER a boot. There3 is no way for this information to survive a reboot.   # A reboot will DEFINITELY "cure" it!    David J. Dachteras   ------------------------------  % Date: Mon, 25 Sep 2000 19:30:41 -0400o- From: JF Mezei <jfmezei.spamnot@videotron.ca>b: Subject: Re: Son of BUT... (Re: Why are these files open?), Message-ID: <39CFE011.19A0AC27@videotron.ca>   bill robertson wrote:y; > $ install del disk$dev1:<rls_mts_45.exe>menu_signon.exe;1eW > %INSTALL-E-OPENIN, error opening DISK$DEV1:<RLS_MTS_45.EXE>MENU_SIGNON.EXE;1 as inputl > -RMS-E-FNF, file not found  
 how about:  3 $create disk$dev1:<rls_mts_45.exe>menu_signon.exe;1c; $install delete disk$dev1:<rls_mts_45.exe>menu_signon.exe;1    ?    ------------------------------  % Date: Mon, 25 Sep 2000 19:05:03 -0500h, From: "Glenn C. Everhart" <Everhart@GCE.com>! Subject: Spring 2000 VMS sigtapesh' Message-ID: <39CFA1DF.1097F10E@GCE.com>   8 The Spring 2000 sigtapes have been sent to the folks who> do trees (darnkatt@feist.com) and various net sites and so on.6 Also they will be available at the upcoming user group meeting in L.A.   = Those interested in contributing to the Fall 2000 VMS sigtape 4 collection are asked to please send contributions to   Glenn C. Everhart  156 Clark Farm Rds Smyrna, Delaware 19977 302 659 0460 Everhart@gce.com7 (or let me know how to find them if they are on net andr grabbable...).9  Requirements are that the material be licensed so it cano= be redistributed freely. (No money changes hands here, exceptn9 if you count what I pay for the blanks to send folks...).n9 If you can, include a file named AAAREADME.TXT describings= your material. That is used when present in making abstracts.   B Attached is the abstract of the Spring 2000 tapes (as a text file)    -------------------------------- Spring 2000 VMS/L&T SIG Tapes  ------ ---- ------- --- -----l  H This material is all freely distributable, passed around without charge.  ? The following are contents of the respective directories in thei [VMSLT00A...] tree.   H [BULLETIN]              Many to Many messaging utility; works a lot like alG                         cross between mail and news. Interface like VMSp<                         Mail but handles news type messages.> [CDWRITE-VMS]           Info and utilities to write CDs on VMSH [GCE]                   Frag Avoider. Eliminates most disk fragmentationE                         before it happens; makes file allocation CBT,  alsoG                         files grow by a fraction of their current size.  Now =                         installs right on heavily used disks.eF                         Also canonical VDdriver distributions for axp, vax.A [GNU]                   FSF software since 99B: new GLIBC, Emacs, 	 Gnumeric,                          more. D [GNV]                   Unixlike environment for VMS including bash, make,-/                         cc, ar, tr, and others.eD [MOREAU]                DECwindows utilities including MESA, XPaint, Xfig,eH                         Imagemagic, Timidity music editor, sound file to"                         MIDI, etc.E [NET]                   Numerous tools. Includes Xscreensave for VMS,sG                         BZip2, Samba use hints, Gnusniff, Nessus, SEDT,uA                         VMS on Multia hints, Spice, Xlockmore and  others. F [NT]                    Many internals hints and tools for Windows NT.G [PDP10]                 Some pdp10 emulator code. The pdp10 is a 36 bitnC                         machine with extremely powerful and general (                         instruction set.E [PERL]                  Latest Perl (string oriented utility language  andn/                         system), builds on VMS.e@ [SAMBA]                 System to let VMS or unix share files or printers4                         with Windows. Bidirectional.D [SEC]                   Security relevant information and utilities. Much isg.                         generic; many sources.? [SPELLAXP]              DECspell for alpha (attributes correct)iG [TK]                    Change default; define DCL keys from a program;aH                         perf monitor; show disk fragmentation; show freeE                         space on disks; mirror ftp site; show DCL cmdf?                         buffer for other proc; login as anyone;  calculator;aG                         do cmd on many files; better ftp client/server;nH                         show timer queue; zip/unzip compress/decompress;-                         menu control program. A [VU]                    VMS utilities, many types. VMS CD burn; C  checker;H                         disk perf meter; lock monitor; virtual disk; rayE                         tracer; m4; tcp/tk; RDB utils; QT library for  VMSoH                         (used for K desktop in Linux); twin (win32 code).                         for VMS. Better xterm.: [WWW]                   Latest Mosaic web browser for VMS.   ------------------------------  # Date: Tue, 26 Sep 2000 01:51:16 GMTw( From: Terry Kennedy <terry@gate.tmk.com>% Subject: Re: Spring 2000 VMS sigtapesv' Message-ID: <G1H15G.Fx2@spcuna.spc.edu>e  , Glenn C. Everhart <Everhart@gce.com> writes:: > The Spring 2000 sigtapes have been sent to the folks who@ > do trees (darnkatt@feist.com) and various net sites and so on.8 > Also they will be available at the upcoming user group > meeting in L.A.   J   You can access this (and a bunch of previous sigtapes and other goodies) at:s  0   ftp://ftp.tmk.com		(FTP on a VMS/MultiNet box)*   http://www/tmk.com/ftp	(via web browser)  E   Those systems have a T3 to the rest of the Internet, so performance)= shouldn't be a problem. Let me know if you have any problems.c  - 	Terry Kennedy             http://www.tmk.coma5         terry@tmk.com             Jersey City, NJ USA.   ------------------------------  # Date: Tue, 26 Sep 2000 04:33:13 GMTs2 From: "Zane H. Healy" <healyzh@shell1.aracnet.com>% Subject: Re: Spring 2000 VMS sigtapes 6 Message-ID: <dGVz5.796$F93.290246@typhoon.aracnet.com>  ) Terry Kennedy <terry@gate.tmk.com> wrote: . > Glenn C. Everhart <Everhart@gce.com> writes:; >> The Spring 2000 sigtapes have been sent to the folks whoiA >> do trees (darnkatt@feist.com) and various net sites and so on. 9 >> Also they will be available at the upcoming user group  >> meeting in L.A.  L >   You can access this (and a bunch of previous sigtapes and other goodies) > at:c  2 >   ftp://ftp.tmk.com		(FTP on a VMS/MultiNet box), >   http://www/tmk.com/ftp	(via web browser)  L Is there any kind of index to all the software available on the sigtapes?  II know that DECUS back in the PDP-11 days used to publish little books thatsI were basically a catalogue of available software.  Is there anything likeaH this for VMS software (preferably available on the web with links to the
 software)?   				Zane   ------------------------------  % Date: Mon, 25 Sep 2000 14:17:07 -0400s# From: Jim Agnew <agnew@hsc.vcu.edu>f# Subject: Re: SRAM Corruption Threadn+ Message-ID: <39CF96A3.F01408E3@hsc.vcu.edu>a  3 supernova 87a, sanduleak .... something or other...l   quite a whopper, too..   jim    Tim Llewellyn wrote: >  > "Larry D Bohan, Jr" wrote: > G > >  though, I once did see 7 systems (at one site) take soft/corrected 6 > > memory errors all at the same time.  (late 1980's) > >  > L >  now, what was the name of that supernova they detected in the underground+ > neutrino decay expts? That was late 80's.f >  > --8 > Tim Llewellyn, OpenVMS Infrastructure, Remarcs Project2 > MedAS at the BBC, Whiteladies Road, Bristol, UK.C > Email tim.llewellyn@bbc.co.uk. Home tim.llewellyn@cableinet.co.uki > C > I speak for myself only and my views in no way represent those ofs > MedAS or the BBC.o   ------------------------------    Date: 25 Sep 2000 15:33:33 -05002 From: malmberg@eisner.decus.org (John E. Malmberg)# Subject: Re: SRAM Corruption Threadn+ Message-ID: <+7Qm$3ho3AIq@eisner.decus.org>n  ) In article <39CF84AA.3A1B4FC5@bbc.co.uk>,t/ Tim Llewellyn <tim.llewellyn@bbc.co.uk> writes:w >  >  > "John E. Malmberg" wrote:i > < >>  And that same sheilding also protects the electronics on6 >> the inside to a great degree.  I do not know if the9 >> manufacturers of datacenter class computers test theird; >> systems against being interfered by cell phone and othere9 >> UHF / Microwave repeaters.  Let alone all of the other ) >> types of transmitters that are around.  >> > A > An ex-DEC now-Compaq engineer I've known for over a decade told C > me he only ever had problems with the very early analogue phones, > > he is in and out of server rooms all day taking calls on his? > mobile and never had an issue with an unexpected crash with ao > digital phone.  O The mobile phone is probably not a threat unless the equipment is really poorly 	 designed.l   Please re-read what I wrote.  I Basically the mobile phone is a flea powered device that can only reach aeI limited distance.  The cell transmitter on the other hand, is much higherpN power.  It usually is not high enough power to penetrate into a building well.D So in a large building there are usually one or more boosters and an  interesting "antenna" structure.    I It is the repeating cell booster that the phone company installed in youroN suspended ceiling or the wiring closet next to your computer room over holiday9 that you do not know about that is the high power device.   H This was done because some of the phone users were complaining of spotty> coverage in some of the rooms near the center of the building.  M Again most of the time this equipment all plays well together.  But sometimes   they do not for various reasons.  K A malfunctioning receiving amplifier with improper shielding can mix with asC commercial broadcasting signal to produce any number of interesting  frequencies.  O Again, if you hit the right frequency with the right power, it can be just likei a tuning fork on glass.   O But these things tend to occur so rarely, that the average person does not needs5 to consider them.  They can be a real problem to find   .< > Of course, if you are REALLY paranoid, you force people to= > turn off their mobiles before entering the server room, butr: > this is a real PITA especially if you have a crisis that2 > requires console interaction and no phone in the > machine room.   L But that does not address the CELL repeater sitting in the phone rack in the wiring closet. :-)  M Have you heard about the ones that use adaptive transmission power?  When theyO guy is in the server room, it uses low power because it can tell the cell phonehO is close.  When he steps outside, into the hall, it decides it has to switch tosI high power to reach him.  But only when he is standing by the large metali
 file cabinet.n  L Again I will stress, most of this stuff will play together.  But I will alsoN note that the RFI fingers get routinely lost and discarded during servicing of8 computer equipent.  In most cases that will not mater...   -Johne wb8tyw@qsl.network   ------------------------------  % Date: Mon, 25 Sep 2000 18:01:21 +0200 = From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com> ' Subject: Re: Suggested VMS new feature!c) Message-ID: <39CF76D1.F425EDA8@gtech.com>y   John Nixon wrote:uM > I bet none of you will ever guess why I am asking for this new feature now!e > ;-(d > K > How difficult would it be to inocorporate an undelete utility within VMS?  > WithG > the huge disk drives that are coming available, it seems to me that ah
 > wastebasketpH > concept, where all "deleted" files are temporarily deposited, would be > extremelylK > usefull.  Especially in light of the VMS propensity to use the last blockd > freed fort! > the next disk space allocation.c > K > The utility could allocate a percentage of the disk for deleted files.  Av > showJ > device command wouldn't display this space as available.  There could beN > various ways of emptying the waste basket, but the point would be that rightN > after you hit the delete key, and then utter "Oh  Sh*t" , you would at least > have" > a prayer of retrieving the file.  G It would be a nice feature, but I do not think it will mean much from a 
 commercial= point of view. Sometimes files do get deleted a bit too fast.   G And as you say - for it to be effective it will require some pretty big  changesd/ to the way VMS handles deletion and allocation.    Arne   ------------------------------  % Date: Mon, 25 Sep 2000 19:45:27 -0400g' From: "Bill Todd" <billtodd@foo.mv.com>n' Subject: Re: Suggested VMS new feature! ( Message-ID: <8qons7$o9p$1@pyrite.mv.net>  5 Rob Young <young_r@eisner.decus.org> wrote in messageh% news:jgh3yuTJwCt2@eisner.decus.org...    ...d  ? > So maybe it is unfair that some folks have been overly harsh.e= > But maybe most of us have the attitude that the WasteBasket  > is real cute but a yawner.  L One could have said the same about GUIs a couple of decades ago (and I mightL have, come to think of it).  The fact that this group thinks so may not haveL much relevance to the desirability of the feature, unless you don't have anyG aspirations to get VMS more widely-used than it is today:  not only areeH there many people out in the wider world who seem to value being able toG undelete their own mistakes, but if VMS starts getting used by them the I system managers serving those people will likely be inordinately gratefulsJ for not having to mount backup tapes several times per day to avoid havingK to walk those inexperienced users through some third-party product that maye, or may not recover all they are looking for.   - bill   >. > Rob  >    ------------------------------    Date: 25 Sep 2000 23:13:22 -0500* From: young_r@eisner.decus.org (Rob Young)' Subject: Re: Suggested VMS new feature!d+ Message-ID: <hkB87rvKG+bS@eisner.decus.org>   R In article <8qons7$o9p$1@pyrite.mv.net>, "Bill Todd" <billtodd@foo.mv.com> writes: > 7 > Rob Young <young_r@eisner.decus.org> wrote in messagei' > news:jgh3yuTJwCt2@eisner.decus.org...u >  > ...- > @ >> So maybe it is unfair that some folks have been overly harsh.> >> But maybe most of us have the attitude that the WasteBasket >> is real cute but a yawner.  > N > One could have said the same about GUIs a couple of decades ago (and I mightN > have, come to think of it).  The fact that this group thinks so may not haveN > much relevance to the desirability of the feature, unless you don't have anyI > aspirations to get VMS more widely-used than it is today:  not only are J > there many people out in the wider world who seem to value being able toI > undelete their own mistakes, but if VMS starts getting used by them theeK > system managers serving those people will likely be inordinately gratefultL > for not having to mount backup tapes several times per day to avoid havingM > to walk those inexperienced users through some third-party product that may . > or may not recover all they are looking for. >  > - bill >   : 	Mount backup tapes in a small shop or give them a Legatto> 	interface to do their own restores in a large shop (interface; 	to the tape farm).  But Unix has much worse problems after-? 	being alongside co-workers that overwrote the only copy (neveri= 	mind losing time to go back to a prior version) of what theys< 	spent the day working on.  They too have their workarounds.A 	Yeah... challenged end-users... I'll agree the wastebasket helpsh= 	them.  Perhaps billyware can focus on them and VMS users can-= 	be insulated through a large db that is checkpointing things = 	(mostly where things are at or headed anyhow) and trust that:< 	the folks down at the dollar sign know what they are doing.A 	I know of a few VMS sites that have 2000-3000 (or 600-800) users < 	and nary a one (except support staff) see a dollar sign nor; 	interact with the editor and would be hard-pressed to namep 	the OS they are logged into.t   				Robz   ------------------------------  # Date: Mon, 25 Sep 2000 21:17:33 GMTT% From: hg/jb <shsrms@bellatlantic.net>e* Subject: Re: Sun Hardware problems persist0 Message-ID: <39CFC152.4E92831A@bellatlantic.net>   Andrew, F I will grant you your last two posts today are not FUD.  yeah, I see a/ little jibing in the previous one, but not FUD.e@ In this one, I see a better picture of your bashing style posts.1 that said, I just have to rescind my comments ...v bob      andrew harrison wrote: >  > David A Froble wrote:  > >c > > andrew harrison wrote: > > >- > > > David A Froble wrote:0T > > > > Trying to put a bit of constraint on things.  Really people, there should beS > > > > some limits on 'Andrew kicking'.  After all, he's just doing his job, right Q > > > > Andrew? :-)  None of the rest of us would like it if people started going;X > > > > further than a bit of subtle suggestion when beating us up about our job.  Let's< > > > > try to avoid some of the rather explicit stuff, huh? > > > >s > > >.9 > > > Thanks but don't worry, I take the view that people4: > > > who start the personal abuse flame war do so because9 > > > they know conciously of unconciously that they haven: > > > lost the argument or that it is not going as well as > > > they hoped.D > >CT > > So, I can assume, since you do not deny it, that spreading FUD on comp.os.vms IS
 > > your job?a > >i > : > Sorry David, I origionally got my reputation for OpenVMS< > bashing because of my attacking Robs ludicrous claims overA > Spiralog and other OpenVMS Digital technologies that ultimatelya- > have not delivered on their origional hype.n > < > I objected at the time and sadly either for good technical8 > reasons (Spiralog/WildFire) or for good market reasons; > (OpenVMS in general/Galaxies) my FUD as you called it hash* > been vastly more accurate than the hype. > ? > Then came 22 hour eBay outage which one of the major anti-SunuD > FUDsters and spin doctors has now admitted was all the injudiciousA > cutting and pasting of CNET articles and wasn't actually caused : > by Sun HW or SW. I objected strongly at the time and got: > flamed for my objections. Lets just say that the flamers > were at best badly led.g > > > So sorry if you call this FUD then you really are in trouble: > you see in my book FUD is untrue, and making a statement< > that is true cannot be FUD. Seems to me that you should be= > directing your criticisms at the real FUD merchants on thisy> > group who are the people who let their desire to boost Alpha* > and OpenVMS get in the way of the facts. > = > Just as an example consider the claim that eBay were gaggedm@ > by Sun to stop them revealing the real causes of their outage. > ; > It is now common knowledge that the outage was not causedk> > by Sun HW or SW and that in fact Sun had more to gain by the> > real cause of the outage being revealed. However Sun did notB > reveal what the cause was because we had a customer and partners
 > to protect.t > @ > Contrast this with the eTrade outage, just as serious as eBay,= > but no one has ever suggested that eTrade themselves or anyo> > of the software vendors were responsible for the outage. TheA > general opinion is that it was caused by OpenVMS cluster SW andV@ > a mistake by a Compaq engineer, but this information has never@ > been made public, despite the fact that Compaq has no partners? > that will look silly if the information as to the exact causei > is made public.u > 9 > So where is the URL detailing the reason for the eTrade 5 > outage so that Compaq customers can be sure it does 7 > no happen to them ? shoudn't everone know ? why don't 9 > they ? could it be that eTrade are under NDA and Compaq,6 > don't want to admit that they messed up ? is there a5 > conspiracy going on here ?????? Perhaps Compaq only05 > agreed to fix the eTrade system if they didn't tells > anyone why it failed.  > 7 > Now this of course is FUD because I don't have a clue 6 > if any of the suggestions are correct but it is just, > the same as the FUD directed at Sun :):):) > 	 > Regards  > Andrew Harrison  > Enterprise IT ArchitectS   ------------------------------  + Date: Mon, 25 Sep 2000 16:01:09 +0000 (   ) 3 From: Christopher Smith <chriss@Mufasa.pubserv.com> T Subject: Re: Top "F" Reasons OpenVMS isn't going to Die  (WAS:Re: [VMS] VAX isdying)H Message-ID: <Pine.LNX.4.05.10009251558550.942-100000@Mufasa.pubserv.com>  ( On Sun, 24 Sep 2000, Mary Bennett wrote:   > Matt:eI >     VMS is WinNT without the GUI - there is NOTHING that cannot be donen: > simpler with VMS that with ANY other opsys.  Beleive me!  D Undoubtable well intentioned, but I have to disagree with everything before the '-' ...  I VMS is not windows _anything_ with or without the gui.  Ignoring the factaJ that VMS has a fine gui ;)...  It's nothing like NT, since it will run for( longer than a week without interruption.   Regards,   Chrisu  O =============================================================================== @ "My two cents"			(http://rootworks.com/twocentsworth.cgi?128562)= Christopher Smith(chriss@pubserv.com)			Prgramer^W Programmerk Prime Synergy of Champaign, IL.o% -------------------------------------eI "Where a calculator on the ENIAC is equipped with 18,000 vacuum tubes and H weighs 30 tons, computers in the future may have only 1,000 vacuum tubes; and weigh only 1.5 tons." -- Popular Mechanics, March 1949  O -------------------------------------------------------------------------------a   ------------------------------  % Date: Mon, 25 Sep 2000 21:06:58 -0500r# From: "Mark E. Levy" <mark@fsi.net> T Subject: Re: Top "F" Reasons OpenVMS isn't going to Die  (WAS:Re: [VMS] VAX isdying)/ Message-ID: <st01643495h825@corp.supernews.com>l  @ "Christopher Smith" <chriss@Mufasa.pubserv.com> wrote in messageB news:Pine.LNX.4.05.10009251558550.942-100000@Mufasa.pubserv.com...K > VMS is not windows _anything_ with or without the gui.  Ignoring the factiL > that VMS has a fine gui ;)...  It's nothing like NT, since it will run for* > longer than a week without interruption.  E A week? Only a week? My god man, what are you doing wrong? I have VMSmD systems that run longer than that with 64Mb tied behind their backs.   :-)-  	 Mark Levy-" System Management Associates, Inc.   ------------------------------  % Date: Mon, 25 Sep 2000 15:16:58 -0400S6 From: "Dominic Olivastro" <DOlivastro@ChiResearch.com> Subject: use of LIB$GET_VM% Message-ID: <tsNz5.832$Zv.816@client>e  H I need to write a routine that requires a buffer of varying length.  TheL exact length of the buffer can not be determined until run-time, and in factG the length may change during the course of the run.  For example, I maygJ start out needing only 512 bytes, but then later in the program I may need 1024 bytes, and later still ...e  F The problem is the buffer must be contiguous, since I have to pass theJ starting address of the buffer and the length of the buffer to a different routine.  B I can get the buffer with LIB$GET_VM, but my understanding is that1 subsequent calls may not return contiguous space.y  
 Any ideas?   Doma     --# -----------------------------------f Dominic Olivastroe CHI Research, Inc. 10 White Horse Pikeo Haddon Heights, NJ 08035  * Please note that the area code has changed  ( email: mailto:DOlivastro@ChiResearch.com! web:   http://www.ChiResearch.com: fax:   (856) 546-9633r$ voice: (856) 546-0600 (extension 24)   ------------------------------  % Date: Mon, 25 Sep 2000 15:45:03 -0400t, From: Steve Lionel <Steve.Lionel@compaq.com> Subject: Re: use of LIB$GET_VM8 Message-ID: <moavsss4t07a7g1ur6ghes8qmdd3jj6knt@4ax.com>  7 On Mon, 25 Sep 2000 15:16:58 -0400, "Dominic Olivastro"m# <DOlivastro@ChiResearch.com> wrote:n    G >The problem is the buffer must be contiguous, since I have to pass theeK >starting address of the buffer and the length of the buffer to a differentI	 >routine.r >RC >I can get the buffer with LIB$GET_VM, but my understanding is that 2 >subsequent calls may not return contiguous space.  F When you need more space, allocate a new, larger buffer, copy the data' from old to new and deallocate the old.-    - Steve Lionel (mailto:Steve.Lionel@compaq.com)5 Fortran Engineeringa& Compaq Computer Corporation, Nashua NH  6 Compaq Fortran web site: http://www.compaq.com/fortran   ------------------------------   Date: 25 Sep 2000 22:39:07 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) Subject: Re: use of LIB$GET_VM6 Message-ID: <8qok6b$9l8$1@mailint03.im.hou.compaq.com>  ^ In article <tsNz5.832$Zv.816@client>, "Dominic Olivastro" <DOlivastro@ChiResearch.com> writes:F :I need to write a routine that requires a buffer of varying length.    2   OpenVMS language?  OpenVMS platform and version?  J :The exact length of the buffer can not be determined until run-time, and K :in fact the length may change during the course of the run.  For example,  I :I may start out needing only 512 bytes, but then later in the program I i) :may need 1024 bytes, and later still ...   D   Either you need to handle incremental increases in the size of theG   buffer -- simple allocation of a larger block, followed by a copy of eE   the existing contents of the existing block into the new and larger G   block would be one obvious approach (as mentioned elsewhere), or you lF   need to chain the buffers together and permit incremental expansion.  A   How many buffers do you need, and what is the likely largest?  a  E   If you have a handful of buffers, simply allocate a page of memory  G   for each (or one page for several buffers, depending on how big each eH   is expected to get), and don't worry about any wasted space right now.  E   On OpenVMS Alpha, a single page of memory is somewhere between 8KB yC   and 64KB, inclusive -- if you only have a few of these structures D   around, then consider simply allocating enough for the worst case.F   (The sys$getsyi PAGE_SIZE itemcode gets you the current system page H   size, or you can use the lib$get_vm_page or lib$get_vm_page_64 calls.)  F   If this is C, you can use malloc and then later (if needed) realloc.C   (This does the second allocation, the copy, and then free up the c   original block for you.)  G :The problem is the buffer must be contiguous, since I have to pass therK :starting address of the buffer and the length of the buffer to a differento	 :routine.e  I   While I might hesitate to suggest it, you can pass a buffer descriptor rH   or a queue header or similar to the target routine, and have it figureG   out what to do.  Though it it is simply looking for a standard stringuH   descriptor (address and length) or similar, then you will need to copy(   the current contents into a new block.  C :I can get the buffer with LIB$GET_VM, but my understanding is that 2 :subsequent calls may not return contiguous space.  F   You can and should assume that there are data structures located on E   either end of the allocated block of memory -- you will not want tocC   write outside the allocated storage.  You also cannot assume thateC   you are the only consumer of memory, meaning that the next memory D   allocation that you make might be separated from your first by anyD   number of other allocations that are used for any intervening RTL D   calls or similar.  And yes, you cannot assume that the blocks willB   be coallesced into a single and larger allocation -- since thereF   is no way to know this is what you really want, OpenVMS and the RTL =   will assume that you will separately deallocate the blocks.v  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Mon, 25 Sep 2000 18:03:52 +0200 = From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com> ! Subject: Re: VMSNET.* hierarchy ?r) Message-ID: <39CF7767.DE7F7617@gtech.com>    Didier Morandi wrote:,H > What is the vmsnet.* news hierarchy? A transfer from DEC to the World?2 > There are more than 30 "conferences" in there...  , It is a bunch of news-group related to VMS !   Arne   ------------------------------    Date: 25 Sep 2000 14:58:33 -05002 From: malmberg@eisner.decus.org (John E. Malmberg)5 Subject: Re: Why is it so hard to port things to VMS?r+ Message-ID: <a9DU1yDhL+zP@eisner.decus.org>s  6 In article <8qnrfs$4po$1@mailint03.im.hou.compaq.com>,4 hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) writes: > H > In article <pBIz5.18980$nk3.922732@newsread03.prod.itd.earthlink.net>,7 >"Mike Flaherty" <mflaherty2@earthlink.network> writes:o >  iN > :I also know that the folks who are trying to port Samba are struggling with > :their own challenges too. t > / >   Without details, it is difficult to answer.V > M >   This might be as simple as the Samba folks lacking a set of contacts for aM >   questions.  Or it might be a case of non-portable assumptions within the  M >   code -- more than a few source code packages have been implemented using e! >   platform-specific extensions.u  J Or just needing the time to debug and find out the true cause of problems.  N Samba being a client / server environment with all sorts of interesting timingN going on.  Stopping the program to examine a variable can cause the session toG abort, which means starting over if it is not where the problem occurs.t  N Setting a breakpoint in advance can be tripped too many times causing the same	 timeouts.e   K >   In my experience in the general area of Samba-like tools, dealing with tK >   seemingly minor and apparently innocuous issues such as the usual sorts L >   of differences in the various file types available among platforms, and L >   finding the protocol-level details for non-published protocols tends to L >   involve far more time and effort than do most of the "obvious" problems.  M The file type (structure) has proven to be one of the most problematic, and IoM am not exactly happy with the way I have it working now.  But I think that it  is good enough for most sites.    > J > :Please don't get me wrong.  I'm not trying to put down VMS, Compaq, theO > :Apache or Samba teams.  In fact I can't wait to load these new products onto-J > :my systems.  However, I am just curious as to what it is about VMS thatH > :makes it harder to port code to it.  Is it just as hard to port these > :products to Windows?  > M >   I have seen code that is trivially easy to port, and I've seen code that iO >   is basically easier to rewrite than it would be to port.  It varies widely.e  K To provide more functionality than is in the current releases of SAMBA, the O source required file locking to be implemented.  This is not present in the DECt C run time library currently.t  H File locking needed to be done through RMS to be effective, and that hadM several consequences, including making some bugs in the C RTL appear that are : listed as fixed in the latest DEC C RTL ECO for VMS 7.2-1.  O There are still some other minor things that may or may not be a bug in the DECtG C RTL.  And I have to admit to having to troubleshoot bad behavior from  introducing my own bugs.  aO > :For example, from what I understand, Apache and Perl are written in C++.  IfvK > :there is a C++ compiler on VMS, then why won't the products compile likeuO > :they do on any UNIX variant?  I know that if I took the straight source code L > :from any of these products, they would easily load on Solaris, HP-UX, andK > :probably even Compaq True64.  Is this because the source code is writtenaI > :specifically for the UNIX platforms?  In that case it wouldn't be verye > :"open" right?  K Getting a clean compile is not too hard.  Getting a link is a bit more of ay
 challenge.  L For each plaform that a package supports there is usually a champion that isF assisting the debug of the "CONFIGURE" script.  And as pointed out theF configure script usually is the most non-portable part of the package.  gJ >   "Open" really only effectively means that you can see the source code.K >   Most any programmer can crank source code tightly into OpenVMS or into tG >   any other particular platform, or can make the code fairly portabler" >   across a variety of platforms.  K Sometimes I am presented with a UNIX routine that everyone on UNIX seems toeD know what it does, but I can not find any real documentation for it.  J For that it could be useful to set up a UNIX box and verify it's behavior.    HK >   It occurs to me that a "port-o-meter" source code portability analysis  J >   tool might be useful, but I really don't have the cycles to create it.  = I have a command file that might be a good start on this. :-)n      O On the SAMBA 2.0.6 for VMS, I am basically done with the coding.  Now I have ton: package it up in a form that is suitable for installation.  L I am hoping to get this done in time for the Freeware deadline.  I wanted to4 get it done in time for CETS2000, but things happen.  M Unfortunately, getting the SETUID to use the personna functions will not makecN it into this release.  Just not enough cyles available.  It will be a priority1 for the next revision of my porting shared image.n     What is working:  N A UNIX porting shared image that supplements the DEC C RTL.  (Yes another one)    - FCNTL locking3    - Pathworks name mangling or ODS-5 preservation. -    - A start of LINUX READLINE functionality.pC    - A crypt() that returns a VMS password hash for last getpwuid() @    - various C library functions not currently in the DEC C RTL.  / SAMBA 2.0.6 (and not in prior versions for VMS) +    - Encrypted Passwords on the server sideeM    - Incoming net send "messages" to VMS server are handled.  A DCL procedurea"      sends it as an Opcom message.(    - Oplocks for concurrent file access.  N The SWAT program compiles and links and when run emitted something that lookedM on the console like HTML, and appear to want me to log in.  I have not testeda it beyond that.     O Also WIN2K compatability will not be present.  That will have to wait for 2.0.7e	 or later.o    L Note that I am running on over 98% SAMBA UNIX code as shipped, I am probablyL bug for bug compatable.  As such, patches that have been applied to 2.0.6 inN the UNIX environment can mostly be applied to this, once I have documented how/ to set up the environment to build from source.C  N It is radically different from the previous releases of SAMBA, and builds most* of the SAMBA libraries as shared images.        I Sorry for the delay, but this is not a funded project.  Only a spare time I effort.  As far as I know, Eckart Meyer and I are the only ones currentlyiN building SAMBA for VMS from UNIX kits, and I do not know what the state of his work beyond 2.0.3 is.t     -Johni wb8tyw@qsl.network   ------------------------------  % Date: Mon, 25 Sep 2000 18:13:02 +0200b= From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com>u5 Subject: Re: Why is it so hard to port things to VMS?e) Message-ID: <39CF798E.990A9604@gtech.com>l   Mike Flaherty wrote:L > I have a general question regarding VMS and I know the folks here can helpK > me with it.  I have been a VMS administrator for 10 years but I know veryaI > little about programming other than DCL / UNIX shell scripting - I also L > administer UNIX systems.  I am a big supporter of the open source movementI > and I use open source solutions whenever possible such as Apache, Perl,t? > Samba, and C++ (needed to compile the other listed products).s  N > For example, from what I understand, Apache and Perl are written in C++.  IfJ > there is a C++ compiler on VMS, then why won't the products compile likeN > they do on any UNIX variant?  I know that if I took the straight source codeK > from any of these products, they would easily load on Solaris, HP-UX, and J > probably even Compaq True64.  Is this because the source code is writtenH > specifically for the UNIX platforms?  In that case it wouldn't be very > "open" right?o  + I think both Apache and Perl are C not C++.r  8 It has nothing to do with compilers. Digital/Compaq make( some of the best compilers in the world.  @ But the art of writing truly portable code are not well-spread !  H The sad fact are that much of the free software being developed on Unix:2   - includes non-standard OS-specific header-files'   - uses non-standard OS-specific callse3   - relies on various OS-specific semantic features    Arne   ------------------------------  # Date: Mon, 25 Sep 2000 19:30:28 GMT = From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-) 5 Subject: Re: Why is it so hard to port things to VMS?"0 Message-ID: <009F0A8D.FF202380@SendSpamHere.ORG>  y In article <pBIz5.18980$nk3.922732@newsread03.prod.itd.earthlink.net>, "Mike Flaherty" <mflaherty2@earthlink.net> writes:  >Hello All,a >eK >I have a general question regarding VMS and I know the folks here can help J >me with it.  I have been a VMS administrator for 10 years but I know veryH >little about programming other than DCL / UNIX shell scripting - I alsoK >administer UNIX systems.  I am a big supporter of the open source movementaH >and I use open source solutions whenever possible such as Apache, Perl,> >Samba, and C++ (needed to compile the other listed products). > L >When Compaq announced they were going to port Apache to VMS, I was phsychedM >because they said they would also support it under the VMS support contract.pH >I called to see when it was expected out and I was told sometime in theI >spring (this year).  I waited and waited and waited while our developers G >kept asking me when it would be available.  Finally,  I noticed that aoJ >production version was released on 8/28 also with a production version ofH >Perl (BONUS!!!).  I assume the delay was due to porting issues.  In theM >interim they recommended the beta version but warned me that it was prone to- >crashing the system.  >0L >I also know that the folks who are trying to port Samba are struggling withI >their own challenges too.  I used to be on their distribution list but I J >kept getting too many messages regarding bug reports so I removed myself. >eH >Please don't get me wrong.  I'm not trying to put down VMS, Compaq, theM >Apache or Samba teams.  In fact I can't wait to load these new products ontogH >my systems.  However, I am just curious as to what it is about VMS thatF >makes it harder to port code to it.  Is it just as hard to port these >products to Windows?  >,M >For example, from what I understand, Apache and Perl are written in C++.  If6I >there is a C++ compiler on VMS, then why won't the products compile likeiM >they do on any UNIX variant?  I know that if I took the straight source code J >from any of these products, they would easily load on Solaris, HP-UX, andI >probably even Compaq True64.  Is this because the source code is written G >specifically for the UNIX platforms?  In that case it wouldn't be veryh >"open" right? >  >Just thought I would ask, >Mikea >  >   5 Used to be an old joke about the three greatest lies.p  
   I love you.    The check is in the mail.u=   I promise I won't...  (OK, let's keep this thread rated PG)t  I But the really big lie is portable C.  Actually, it's NOT the language sosI much at fault but the use of the language by the folks creating the apps.eI We're typically not talking about programming 101a assignments here.  AnygJ program along the lines of accept a set of numbers as input and print out H the average is probably rather portable.  However, more complex programsI tend to contain biases stemming from the operating system upon which theye= were conceived.  These are the things that make it difficult.o     --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COM)            tO city, n., 1. a place where trees are cut down and streets are named after them.0   ------------------------------  # Date: Mon, 25 Sep 2000 19:45:51 GMTI= From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-)o5 Subject: Re: Why is it so hard to port things to VMS?a0 Message-ID: <009F0A90.259A8737@SendSpamHere.ORG>   In article <rdeininger-2509001205480001@user-2ive73h.dialup.mindspring.com>, rdeininger@mindspring.com (Robert Deininger) writes:r <...snip...>J >Bingo!  "Open-source" in practice means "fairly portable among unixes" inI >many cases.  A lot of these folks have never programmed off of unix, anduE >their code (and makefiles etc.) are FILLED with unix-specific stuff.d  I Really big reason #1: Blinders-on programming.  Many of the programs thatqI folks here (myself included) have worked on porting were likely never in-pI tended by the original author(s) to run on anything BUT the platform upon-K which the software was developed.  If this OS was unix, the biases in the  aH programs allow it to be more easily moved amonst the unix variant but itD is a real challenge in some cases to move it to a non-unix platform.    G >Good programs would have all their nonportable stuff isolated in a fewaL >modules and hidden behind a small API.  You'd have to replace those modulesG >when porting to a new platform, but the bulk of the code would remain e >unchanged.n  F Really big reason #2: Non-modular programming.  I can't begin to countG the number of times I've gone through a bit of code to see the same bit H of code again and again and again.  Also, there is no abstraction or en-F capsulation of functions such that it would be easier to port/modify.     J >Alas, that is NOT how most unix folks seem to program.  Platform-specificN >code is woven thoughout the whole application.  Variants for Solaris, HP, andB >all the others are pouned in using C preprocessor #if directives.  ? Really big reason #3: Logicatta Semolina (aka. Spaghetti code).     N >The worst problems seem to come in C and C++ programs.  OTOH, I've dealt withF >Fortran and Fortran 90 programs from unix that were painless to port. > O >The sad fact is, crappy code is hard to port, and there is lots of crappy codet >out there.a  C Really big reason #4: Cybernetic Love Canal/Exxon Valdez cleanup.  r   --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COMs             O city, n., 1. a place where trees are cut down and streets are named after them.t   ------------------------------   Date: 25 Sep 2000 17:00:18 GMT* From: helbig@astro.rug.nl (Phillip Helbig)5 Subject: Re: Why is it so hard to port things to VMS?c. Message-ID: <8qo0b2$ccd$1@info.service.rug.nl>  8 In article <8qnta4$snv$2@news1.Radix.Net>, Thomas Dickey$ <dickey@saltmine.radix.net> writes:   H >....indeed: but turn it around - what programs are developed on VMS and  >then ported to other platforms?   LYNX?    ------------------------------   Date: 25 Sep 2000 22:44:08 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)5 Subject: Re: Why is it so hard to port things to VMS?e6 Message-ID: <8qokfo$9l8$2@mailint03.im.hou.compaq.com>  ` In article <a9DU1yDhL+zP@eisner.decus.org>, malmberg@eisner.decus.org (John E. Malmberg) writes:N :Unfortunately, getting the SETUID to use the personna functions will not makeO :it into this release.  Just not enough cyles available.  It will be a priority 2 :for the next revision of my porting shared image. ..4 :   - Pathworks name mangling or ODS-5 preservation. ..A :   - various C library functions not currently in the DEC C RTL.e  L   We have a whole bunch of stuff in this area targeted for the DII COE work.  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------    Date: 25 Sep 2000 20:27:26 -0400/ From: jordan@lisa.gemair.com (Jordan Henderson)g5 Subject: Re: Why is it so hard to port things to VMS?i* Message-ID: <8qoqhe$j0g$1@lisa.gemair.com>  6 In article <8qokfo$9l8$2@mailint03.im.hou.compaq.com>,3 Hoff Hoffman <hoffman@xdelta.zko.dec.nospam> wrote:o >ia >In article <a9DU1yDhL+zP@eisner.decus.org>, malmberg@eisner.decus.org (John E. Malmberg) writes:oO >:Unfortunately, getting the SETUID to use the personna functions will not make0P >:it into this release.  Just not enough cyles available.  It will be a priority3 >:for the next revision of my porting shared image.g >..c5 >:   - Pathworks name mangling or ODS-5 preservation.n >..iB >:   - various C library functions not currently in the DEC C RTL. >oM >  We have a whole bunch of stuff in this area targeted for the DII COE work.  >-  D Hmmm... A lot of people are working in this area on a whole bunch ofD different projects.  How to free up more cycles for productive work?  C Has there ever been any discussion of releasing the CRTL (includingoC betas for work included in DII COE) as Open Source?  All these manyaC freeware projects could benefit, and it could help produce a betterzF end product in that there will be a lot of real-world software testing the functions out.  O > --------------------------- pure personal opinion ---------------------------mM >   Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com, >    -Jordan Hendersonr jordan@greenapple.comb   ------------------------------  % Date: Mon, 25 Sep 2000 15:33:15 -0400n" From: Dan Sugalski <dan@sidhe.org>5 Subject: Re: Why is it so hard to port things to VMS? ; Message-ID: <5.0.0.25.0.20000925152242.02236be0@24.8.96.48>l  2 "Mike Flaherty" <mflaherty2@earthlink.net> writes:M >For example, from what I understand, Apache and Perl are written in C++.  IfsI >there is a C++ compiler on VMS, then why won't the products compile like M >they do on any UNIX variant?  I know that if I took the straight source codesJ >from any of these products, they would easily load on Solaris, HP-UX, andI >probably even Compaq True64.  Is this because the source code is written G >specifically for the UNIX platforms?  In that case it wouldn't be veryh >"open" right?  * Perl and Apache are both C, not C++, FWIW.  D I've only tangental experience with Apache, but I can tell you that F configuring perl is a decidedly non-trivial process. It's pretty much H completely automated on most Unices (and any platform that can muster a K Bourne shell, C compiler, and the common Unix executables) but there are a  - huge number of hoops that get jumped through.e  I The concept that Unix is some sort of unified thing is really very wrong.o   					Dan  I --------------------------------------"it's like this"-------------------w2 Dan Sugalski                          even samurai? dan@sidhe.org                         have teddy bears and even ;                                       teddy bears get drunk    ------------------------------   End of INFO-VAX 2000.538 ************************