1 INFO-VAX	Fri, 02 Nov 2001	Volume 2001 : Issue 610       Contents: Re: Alpha 2100s for free Re: Alpha 2100s for free, Re: Another missed opportunity for Alpha/VMS/ Re: assaults on web servers from the billyworld $ BEWARE OF  VMS721_CLIUTL V2,.0 PATCH( Re: BEWARE OF  VMS721_CLIUTL V2,.0 PATCH" Re: Blockbuster uses Alpha systems" RE: Blockbuster uses Alpha systems" Re: Blockbuster uses Alpha systems" Re: Blockbuster uses Alpha systems" Re: Blockbuster uses Alpha systems" Re: Blockbuster uses Alpha systems" Re: Blockbuster uses Alpha systems" Re: Blockbuster uses Alpha systems" Re: Blockbuster uses Alpha systems" Re: Blockbuster uses Alpha systems" Re: Blockbuster uses Alpha systems Re: Compaq Ada for VMS Re: Compaq Ada for VMS Re: Compaq Ada for VMS Re: Compaq Ada for VMS Re: Compaq goes back to school Re: Compaq goes back to school Compaq guarantees? Re: Compaq guarantees? Re: Compaq guarantees? Re: Compaq guarantees? Re: Compaq guarantees? Re: Compaq guarantees? Re: Compaq guarantees? Re: Compaq guarantees? Re: Compaq guarantees? Re: Compaq guarantees? Re: DEC C and DECUS  Re: DEC C and DECUS  Re: DEC C and DECUS ! Re: DHCP client software for VMS? ! Re: DHCP client software for VMS?  Free HSC40 Parts Re: host-based shadow questionM How to connect a DS20 to a Fibre  channel SAN switch an that one to a hsg80?? P Re: How to connect a DS20 to a Fibre  channel SAN switch an that one to a hsg80?: Re: Kerberos Client on OpenVMS, CSWS/APACHE, MOD_AUTH_KERB LANCP Counts Re: news servers Re: Pathworks32  Re: remote booting a VXT! Re: savesets,  CDs and attributes ' set account for accounting log purposes + Re: set account for accounting log purposes + Re: set account for accounting log purposes + Re: set account for accounting log purposes  Re: SET TERM/INQ Re: SET TERM/INQ Re: SET TERM/INQ Re: SET TERM/INQ% Re: SYS$EXAMPLES:DAYLIGHT_SAVINGS.COM  Re: Undo disk Initialize
 unsubcribe* Re: V7.2-2 in Canada? Release date in USA?$ Re: Web Browser for OpenVMS 1.5-1H1?& Re: X.25 profile documentation wanted.  F ----------------------------------------------------------------------  % Date: Fri, 02 Nov 2001 09:52:49 +0000 % From: Alan Greig <a.greig@virgin.net> ! Subject: Re: Alpha 2100s for free 8 Message-ID: <ssq4ut4tk6is6l1e18lt0buvqb807vkher@4ax.com>  ; On 1 Nov 2001 19:41:20 GMT, bill@triangle.cs.uofs.edu (Bill  Gunshannon) wrote:  A >In article <20011101154746.91357.qmail@web20206.mail.yahoo.com>, 2 > Fabio Cardoso <fabiopenvms@yahoo.com.br> writes:( >|> Donate both of them to a University. >|>  > ( >I'll even volunteer my University.  :-)  D My former employer (the University of Abertay Dundee) turned off itsE last VMS Alphaserver (2100) a few months ago. They made no attempt to F find a new home for it. Instead a member of IT staff was instructed toE "drill holes" through it to prevent its re-use. No it never contained C especially sensitive data, The site had been almost exclusively DEC D from 1977 (DEC-20) through 1997 but now has almost no DEC/Compaq kit@ or IT staff who would even think of going down a Compaq route in future.    >bill    -- Alan   ------------------------------   Date: 2 Nov 2001 16:31:14 +0100 O From: pmoreau@dev.ath.cena.fr (Patrick MOREAU, CENA Athis, Tel: 01.69.57.64.40) ! Subject: Re: Alpha 2100s for free   Message-ID: <SbmcHRxOLet0@sable>  9 In article <ssq4ut4tk6is6l1e18lt0buvqb807vkher@4ax.com>,  ' Alan Greig <a.greig@virgin.net> writes:  [...] F > My former employer (the University of Abertay Dundee) turned off itsG > last VMS Alphaserver (2100) a few months ago. They made no attempt to H > find a new home for it. Instead a member of IT staff was instructed toG > "drill holes" through it to prevent its re-use. No it never contained E > especially sensitive data, The site had been almost exclusively DEC F > from 1977 (DEC-20) through 1997 but now has almost no DEC/Compaq kitB > or IT staff who would even think of going down a Compaq route in	 > future.  > -- > Alan  J At work, my main server is a 2100 4/275 (under VMS 6.2, I also have a 1000O 4/200 under 7.2-1). The 2100 is very robust, I had uptimes longer than 600 days  with this box !!   Patrick  --O =============================================================================== N pmoreau@ath.cena.fr  (CENA)     ______      ___   _           (Patrick MOREAU)4 moreau_p@decus.fr (DECUS)       / /   /     / /|  /|J CENA/Athis-Mons FRANCE         / /___/     / / | / |   __   __   __   __  N BP 205                        / /         / /  |/  |  |  | |__| |__  |__| |  |N 94542 ORLY AEROGARE CEDEX    / /   ::    / /       |  |__| | \  |__  |  | |__|N http://www.ath.cena.fr/~pmoreau/            http://www.multimania.com/pmoreau/O ===============================================================================    ------------------------------   Date: 2 Nov 2001 07:46:13 -0600 - From: koehler@encompasserve.org (Bob Koehler) 5 Subject: Re: Another missed opportunity for Alpha/VMS 3 Message-ID: <g2Zn7ONZj$ok@eisner.encompasserve.org>   \ In article <3BE1F9F5.1F0F1271@videotron.ca>, JF Mezei <jfmezei.spamnot@videotron.ca> writes: > Hoff Hoffman wrote: H >>   Accordingly, DIGITAL Semiconductor produced the Alpha DECchip chipsI >>   for the upper end of the market and produced the StrongARM chips for  >>   the lower end.  > K > Why wouldn't NASA have selected StrongArm for its satellite/probes then ?   G    There was the mistaken notion that the reason flight software was so A    expensive was that it was running on those custom built CPUs.  E    Someone figured that if one had the same processor in flight as in B    a PC (or Mac, or other "popular" platform) that it would reduceB    cost.  Classic mistake of only looking at the hardware, as suchF    decisions are often made by folks with only hardware backgrounds.  J    Programming a 386 under DOS is not the same as writing for an embedded 
    system.  C    So a VAX has flown but a StrongARM hasn't been considered AFAIK. E    Other "controller" chips have flown which are already popular with     the hardware folks.  L > Also, what is involved in producing a hardened version of a CPU ? Just theA > casing of the chip, or is it also inside at the silicon level ?   D    Casing won't work, unless you can launch several tons of lead.  AD    small casing can't stop a high power cosmic ray, it can cause it C    to cascade to thousands of lower power cosmic rays, all of which %    cause as much hassle as the first.   A    A wide variety of techniques are used to rad harden, including :    derating the chip's speed.  Slower operations are less =    susceptable to seeing the narrow spikes of a cosmic ray as B    meaningfull.  For example, we have some 33 Mhz 386 operating atC    25 Mhz to improve rad hardening.  What kind of circuits are used B    in the surrounding electronics are also important.  We're stillG    flying some magnetic core memory on older spacecraft, that is quite  E    hard against cosmic rays and doesn't require reloading after power     off.    ------------------------------  % Date: Fri, 02 Nov 2001 07:40:24 -0800 % From: Dean Woodward <deanw@rdrop.com> 8 Subject: Re: assaults on web servers from the billyworld( Message-ID: <3BE2BE68.BD0FCCA@rdrop.com>   Nigel Arnot wrote: >  > > vance@alumni.caltech.edu (Vance R. Haemmerle) writes in article <9rfjrs$kg5@gap.cco.caltech.edu> dated 28 Oct 2001 00:35:08 GMT: > > L > > I think the best way to slow down a virus like this would be to hang itsJ > > HTTP connection.  This isn't tcp-compliant, but if you could make yourP > > machine drop the connection without telling the attacking machine, the virus > > would hang, right? > > O > > With existing software, I think mapping the billy-weak URLs to a very large N > > file on a very slow disk would be the closest thing.  Future viruses might& > > disconnect after a timeout though. > > 2 > Could this be a new use for a floppy disk drive?  B Anyone else out there a 'Reboot' fan, and think of Al's Slow Food?  6 (If you don't understand, I probably can't explain...)   ------------------------------  % Date: Fri, 02 Nov 2001 11:17:25 +0100 : From: Karl Rohwedder <extern.karl.rohwedder@volkswagen.de>- Subject: BEWARE OF  VMS721_CLIUTL V2,.0 PATCH * Message-ID: <3BE272B5.60104@volkswagen.de>  H I've installed the CLIUTL Pactch DEC-AXPVMS-VMS721_CLIUTL-V0200--4.PCSI.  C Afterwards the SHOW QUEUE display is scrambled and looks like this:   / Batch queue WZB04_BAT_QUE_3_1, idle, on WZB04::     <WZB04 Service Queue>  5    Entry  Jobname         Username             Status 5    -----  -------         --------             ------       913l    AnoFTP DNC-Serv  no privilege                         File: SYSTEM  Holding until  2-NOV-2001 11:17:55.14      914l    AnoFTP DNC-Serv  no privilege                         File: SYSTEM  Holding until  2-NOV-2001 11:17:55.17o      510 SAVPAR        no privilege                         File: SYSTEM  Holding until  2-NOV-2001 14:30:00.00 o      830 RVSCHK        no privilege                         File: SYSTEM  Holding until  2-NOV-2001 21:00:00.00 j      343 BAX_JOB       no privilege                         File: BAX_ACCOUNT  Holding until  2-NOV-2001 2   ...   S After renaminf QUEMAN.EXE_OLD to QUEMAN.EXE and reinstalling it, everything is o.k.  --    - mit freundlichen Gruessen | with best regards    Karl RohwedderB iT-Ingenieurteam     | Ellernbruch 11       | D-38112 BraunschweigA Telefon: 0531/515521 | Telefax: 0531/515531 | Mobil: 0172/5434843 E   E-Mail: rohwedder@decus.decus.de           | iT-IngTeam@t-online.de ,           karl.rohwedder@it-ingenieurteam.de DATEX-P: 4505018005::ROHWEDDER   ------------------------------  # Date: Fri, 02 Nov 2001 13:49:18 GMT & From: "john nixon" <jnixon@cfl.rr.com>1 Subject: Re: BEWARE OF  VMS721_CLIUTL V2,.0 PATCH < Message-ID: <yvxE7.5581$4Q3.1710944@typhoon.tampabay.rr.com>  C I don't really want to apply this eco.  What I want is to apply the  fiber-scsi eco.   K But the fibre-scsi eco says if you want all the benefits ,you need to apply  the SYS and MOUNT96 ecos. L     But the MOUNT96 eco says you need the CLIUTL eco (which I wasn't able to find till today)G         And now, the CLIUTL eco suggests adding the AUDSRV eco, which I  have't even looked for yet. E             I wonder what additional eco the AUDSRV eco will ask for.   L Retirement (for me, not for our VMS systems) is becoming a real possibility.4 And if this keeps up, maybe for our VMS systems too.    G "Karl Rohwedder" <extern.karl.rohwedder@volkswagen.de> wrote in message $ news:3BE272B5.60104@volkswagen.de...J > I've installed the CLIUTL Pactch DEC-AXPVMS-VMS721_CLIUTL-V0200--4.PCSI. > E > Afterwards the SHOW QUEUE display is scrambled and looks like this:  > 1 > Batch queue WZB04_BAT_QUE_3_1, idle, on WZB04::  >    <WZB04 Service Queue> > 7 >    Entry  Jobname         Username             Status 7 >    -----  -------         --------             ------ 
 >      913G >    AnoFTP DNC-Serv  no privilege                         File: SYSTEM % Holding until  2-NOV-2001 11:17:55.14 
 >      914G >    AnoFTP DNC-Serv  no privilege                         File: SYSTEM % Holding until  2-NOV-2001 11:17:55.17 J >      510 SAVPAR        no privilege                         File: SYSTEM% Holding until  2-NOV-2001 14:30:00.00 J >      830 RVSCHK        no privilege                         File: SYSTEM% Holding until  2-NOV-2001 21:00:00.00 C >      343 BAX_JOB       no privilege                         File: ( BAX_ACCOUNT  Holding until  2-NOV-2001 2 >  > ...  > B > After renaminf QUEMAN.EXE_OLD to QUEMAN.EXE and reinstalling it, everything is o.k. > -- > / > mit freundlichen Gruessen | with best regards  >  > Karl RohwedderD > iT-Ingenieurteam     | Ellernbruch 11       | D-38112 BraunschweigC > Telefon: 0531/515521 | Telefax: 0531/515531 | Mobil: 0172/5434843 G >   E-Mail: rohwedder@decus.decus.de           | iT-IngTeam@t-online.de . >           karl.rohwedder@it-ingenieurteam.de  > DATEX-P: 4505018005::ROHWEDDER >  >    ------------------------------   Date: 2 Nov 2001 07:11:52 GMT - From: djweath@attglobal.net (Dave Weatherall) + Subject: Re: Blockbuster uses Alpha systems 5 Message-ID: <DTiotGxQ0bj6-pn2-6LHYbgDlp9iP@localhost>   , On Thu, 1 Nov 2001 08:25:09, Phillip Helbig + <HELBPHI@sysdev.deutsche-boerse.com> wrote:    > > What is Blockbuster ???? > I > I think it is a chain of video-tape (and, today, probably DVD as well)   > rental stores in the U.S.   F They are in Munich too. I've never been in one but maybe I should justF to see if VMS is still at work. I did see a VT terminal talking to VMSE at a hospital earlier this year. There were 5 pc's in the office too  C but the VT was on and the lady booking my father-in-law did use it.    --   Cheers - Dave.   ------------------------------  + Date: Fri, 02 Nov 2001 10:18:45 +0100 (MET) 9 From: Phillip Helbig <HELBPHI@sysdev.deutsche-boerse.com> + Subject: RE: Blockbuster uses Alpha systems ; Message-ID: <01KA830BQR6W90UTW5@sysdev.deutsche-boerse.com>   I > I wouldn't count what they do as censoring the films.  True, they don't H > carry every movie ever made (they don't have "Debbie Does Dallas", forN > example), but neither does a public library carry every book ever published.N > They have limited shelf space and must stock those films they believe are inN > highest demand.  Censoring a film means editing the film to remove or modify- > parts of it.  Blockbuster does not do that.   ? Sure, they don't carry them all---I meant changing the content.    Somewhere under   +    http://www.suntimes.com/index/ebert.html   D this topic has come up several times, when readers noticed that the F Blockbuster version was different from what they remembered seeing in  the cinema.   F A Northernlight search on +blockbuster +video +film +censor* turns up ) 3147 hits.  Take a look at the second one   #    http://bbv0.tripod.com/bbbv.html   F I can't verify this information (I live in Germany where films aren't E even censored for television) but have heard it many times from many   different sources.   ------------------------------  % Date: Fri, 02 Nov 2001 05:14:40 -0500 - From: JF Mezei <jfmezei.spamnot@videotron.ca> + Subject: Re: Blockbuster uses Alpha systems , Message-ID: <3BE2720F.53253EB0@videotron.ca>   Phillip Helbig wrote: E > this topic has come up several times, when readers noticed that the G > Blockbuster version was different from what they remembered seeing in 
 > the cinema.   @ That would be similar to CDs you buy at Wallmart which have beenM modified/edited to remove any expressions that Wallmart doesn't like in order  for wallmart to carry the CD.    ------------------------------  % Date: Fri, 02 Nov 2001 10:56:52 +0000 ( From: Nic Clews <sendspamhere@127.0.0.1>+ Subject: Re: Blockbuster uses Alpha systems ) Message-ID: <3BE27BF4.D60ACA30@127.0.0.1>    JF Mezei wrote:  >  > Phillip Helbig wrote: G > > this topic has come up several times, when readers noticed that the I > > Blockbuster version was different from what they remembered seeing in  > > the cinema.  > B > That would be similar to CDs you buy at Wallmart which have beenO > modified/edited to remove any expressions that Wallmart doesn't like in order  > for wallmart to carry the CD.    Hang on a darn second!  B If you really want to find out more about how theatre versions andE general release versions are different, read some of the write up and A comparisons by someone who is fully familiar with this subject at B http://dvdfever.co.uk/ (NOTE: there are problems with the server IG understand [obviously not VMS], so book mark it and check in a few days  2-nov-2001)   F The top and bottom of it is that the audience potential is considered.C Freeze framing and rewinding in a cinema is not often done during a D performance, however the censors take this into consideration when a% film is going on distributed release.   F But what JF says has also seen to be true, retailers do sometimes haveH their own special versions, sometimes cosmetic, sometimes more sinister!   --  ( Regards, Nic Clews CSC Computer Sciences nclews at csc dot com    ------------------------------  % Date: Fri, 02 Nov 2001 11:03:22 +0000 ! From: Andy Burns <andy@burns.net> + Subject: Re: Blockbuster uses Alpha systems 8 Message-ID: <u9v4ut8g1vcklk3rj1p3d3kqa5gbqb655h@4ax.com>  F On Fri, 02 Nov 2001 10:56:52 +0000, Nic Clews <sendspamhere@127.0.0.1> wrote:  C >If you really want to find out more about how theatre versions andtF >general release versions are different, read some of the write up andB >comparisons by someone who is fully familiar with this subject atC >http://dvdfever.co.uk/ (NOTE: there are problems with the server IlH >understand [obviously not VMS], so book mark it and check in a few days >2-nov-2001)  F Not problems with the servewr, someone got his site pulled due to some( "unsavoury" material that was there ....     --  
 Andy Burns   ------------------------------  % Date: Fri, 02 Nov 2001 11:50:40 +0000V( From: Nic Clews <sendspamhere@127.0.0.1>+ Subject: Re: Blockbuster uses Alpha systemsg) Message-ID: <3BE28890.760DEB3F@127.0.0.1>    Andy Burns wrote:t > H > Not problems with the servewr, someone got his site pulled due to some* > "unsavoury" material that was there ....   Ah, the censors chopper!   (And I censored my apostrophe) -- a( Regards, Nic Clews CSC Computer Sciences nclews at csc dot comn   ------------------------------   Date: 2 Nov 2001 06:34:42 -0600e- From: Kilgallen@SpamCop.net (Larry Kilgallen)r+ Subject: Re: Blockbuster uses Alpha systemsn3 Message-ID: <fzZb5thRy2nh@eisner.encompasserve.org>e  e In article <DTiotGxQ0bj6-pn2-6LHYbgDlp9iP@localhost>, djweath@attglobal.net (Dave Weatherall) writes:b. > On Thu, 1 Nov 2001 08:25:09, Phillip Helbig - > <HELBPHI@sysdev.deutsche-boerse.com> wrote:k >  >> > What is Blockbuster ????  >> eJ >> I think it is a chain of video-tape (and, today, probably DVD as well)  >> rental stores in the U.S. > H > They are in Munich too. I've never been in one but maybe I should just! > to see if VMS is still at work.I  D Perhaps in Munich the clerks are smarter and would be able to answerD complex technical questions like "where is the computer keyboard ?".A Around Boston I have not had good luch with Blockbuster clerks on.0 much easier questions (about their merchandise).   ------------------------------  % Date: Fri, 02 Nov 2001 12:18:04 +0000a% From: Alan Greig <a.greig@virgin.net>r+ Subject: Re: Blockbuster uses Alpha systems:8 Message-ID: <2e35utgtuip19if343320o1ges8ortda04@4ax.com>  F On Fri, 02 Nov 2001 10:56:52 +0000, Nic Clews <sendspamhere@127.0.0.1> wrote:   >JF Mezei wrote: >> t >> Phillip Helbig wrote:H >> > this topic has come up several times, when readers noticed that theJ >> > Blockbuster version was different from what they remembered seeing in >> > the cinema. >> mC >> That would be similar to CDs you buy at Wallmart which have beenuP >> modified/edited to remove any expressions that Wallmart doesn't like in order  >> for wallmart to carry the CD. >n >Hang on a darn second!f >sC >If you really want to find out more about how theatre versions and F >general release versions are different, read some of the write up andB >comparisons by someone who is fully familiar with this subject atC >http://dvdfever.co.uk/ (NOTE: there are problems with the server ImH >understand [obviously not VMS], so book mark it and check in a few days >2-nov-2001)  > Not sure what the current domain name is but one of the oldestD DVD/Laserdisc sites in the UK is/was run by a friend of mine and, atF one time, ran on a university DEC 3000-400 under OSF/1. The machine isE actually still up and running and has been in continuous operation assF a web server since 1993. Still hosts some of his old personal pages. IA believe there have been no hardware or software crashes since thed system went online 8 years ago!m  E I am absolutely sure that he would happily accept a donated new Alpha D with commercial VMS license if Compaq were to send him one. AlthoughF he works with Unix and NT these days he did work with VMS way back and quite likes it.1  G >The top and bottom of it is that the audience potential is considered.kD >Freeze framing and rewinding in a cinema is not often done during aE >performance, however the censors take this into consideration when a0& >film is going on distributed release. >hG >But what JF says has also seen to be true, retailers do sometimes have=I >their own special versions, sometimes cosmetic, sometimes more sinister!    -- Alan   ------------------------------  % Date: Fri, 02 Nov 2001 14:38:48 +0000p( From: Nic Clews <sendspamhere@127.0.0.1>+ Subject: Re: Blockbuster uses Alpha systems ) Message-ID: <3BE2AFF8.C913DECC@127.0.0.1>    JF Mezei wrote: N > But do they stock the original movie, of the one edited for television ? ABCL > aired some good movie the other week and I had to stop watching it becauseL > every minute or so, they had a very poorly done dubbing job to remove someN > words that network thinks are unacceptable. This is extremely annoying. (whyO > then have the warning that the movie contains coarse language if they removedb > any coarse words ?).  F Not that it's part of my entertainment diet, but the significant otherH watches "Jerry Springer Uncut", which has large amounts of bleeped words  and video effect masked visuals.   What's 'uncut' about that?' Is the editing done before syndication?c -- r( Regards, Nic Clews CSC Computer Sciences nclews at csc dot comk   ------------------------------  $ Date: Fri, 2 Nov 2001 12:23:36 -0500; From: "Brian Tillman" <tillman_brian@notnoone.notnohow.com>s+ Subject: Re: Blockbuster uses Alpha systemst$ Message-ID: <3be2d68e$1@news.si.com>  @ >Sure, they don't carry them all---I meant changing the content. >  >Somewhere under > , >   http://www.suntimes.com/index/ebert.html > D >this topic has come up several times, when readers noticed that theF >Blockbuster version was different from what they remembered seeing in >the cinema.  J That's not Blockbuster changing the movie, though, that's the film company changing the movie.  --A Brian Tillman                   Internet: tillman_brian at si.comoA Smiths Aerospace                          tillman at swdev.si.coma= 3290 Patterson Ave. SE, MS      Addresses modified to prevent.< Grand Rapids, MI 49512-1991     SPAM.  Replace "at" with "@"8        This opinion doesn't represent that of my company   ------------------------------  % Date: Fri, 02 Nov 2001 17:59:33 +0000 ! From: Andy Burns <andy@burns.net>c+ Subject: Re: Blockbuster uses Alpha systemsc8 Message-ID: <7gn5ut06poia3d2hn3b7on3b500l205dbj@4ax.com>  F On Fri, 02 Nov 2001 11:50:40 +0000, Nic Clews <sendspamhere@127.0.0.1> wrote:   >Ah, the censors chopper!   ; here's the google cache (minus the images of course) of thep "offending" page  ...s  Z www.google.com/search?q=cache:vdOiTLF8rkY:www.dvdfever.co.uk/reviews/tesinter.shtml+&hl=en  D and the article about the person bragging about getting it pulled is here ...  Q http://groups.google.com/groups?q=james+cooper+warning+dvdfever&hl=en&sa=N&tab=wgi     -- y
 Andy Burns   ------------------------------  $ Date: Fri, 2 Nov 2001 09:42:19 +0100$ From: "Jakob Erber" <erberj@post.ch> Subject: Re: Compaq Ada for VMS- Message-ID: <3be25c6b$1@hcwe67>   , This is a multi-part message in MIME format.  + ------=_NextPart_000_00D4_01C16382.AA0C36B0  Content-Type: text/plain;l 	charset="iso-8859-1"E+ Content-Transfer-Encoding: quoted-printable:  J I wonder, if we can get any save commitment from Compaq in the middle of = the merger with HP.cE This uncertainty makes even us, traditional VMS customers, thinking =t' about moving to Unix of another vendor. I   "Charlie McCutcheon" <charlie.mccutcheon@NOSPAMcompaq.com> schrieb im =m6 Newsbeitrag news:3BE1C283.BC0A39E4@NOSPAMcompaq.com...J   >The only issue is as far as I've been told they will not be producing = an=20 "   >Ada95 version of Compaq ADA.=20)   Sorry, Ada 95 is not the only issue.=20e  E   And yes, Compaq Ada will never be upgraded to the Ada 95 language =nH version.  If you need Ada 95, we recommend GNAT Pro, provided by ACT.=20  B   OpenVMS management is actively working on the issue of Ada for =F Itanium.  I won't hazzard to guess the result at this point...  8-)=20     Charlie=20    =20    + ------=_NextPart_000_00D4_01C16382.AA0C36B0  Content-Type: text/html; 	charset="iso-8859-1"k+ Content-Transfer-Encoding: quoted-printable   > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD>3 <META content=3D"text/html; charset=3Diso-8859-1" =  http-equiv=3DContent-Type>9 <META content=3D"MSHTML 5.00.2919.6307" name=3DGENERATOR>Z <STYLE></STYLE>i </HEAD>Z <BODY bgColor=3D#ffffff>C <DIV><FONT face=3DArial size=3D2>I wonder, if we can get any save =- commitment from=208 Compaq in the middle of the merger with HP.</FONT></DIV>B <DIV><FONT face=3DArial size=3D2>This uncertainty makes even us, = traditional VMS=20H customers, thinking about moving to Unix of another vendor.</FONT></DIV> <BLOCKQUOTE=20J style=3D"BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: =, 0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">%   <DIV>"Charlie McCutcheon" &lt;<A=20S   = J href=3D"mailto:charlie.mccutcheon@NOSPAMcompaq.com">charlie.mccutcheon@NO= SPAMcompaq.com</A>&gt;=203   schrieb im Newsbeitrag <A=20   = J href=3D"news:3BE1C283.BC0A39E4@NOSPAMcompaq.com">news:3BE1C283.BC0A39E4@N=& OSPAMcompaq.com</A>...</DIV>&gt;The=20I   only issue is as far as I've been told they will not be producing an=20 )   <BR>&gt;Ada95 version of Compaq ADA.=20I3   <P>Sorry, Ada 95 is <B>not</B> the only issue.=20uI   <P>And yes, Compaq Ada will never be upgraded to the Ada 95 language=20 I   version.&nbsp; If you need Ada 95, we recommend GNAT Pro, provided by =  ACT.=20aF   <P>OpenVMS management is actively working on the issue of Ada for=20>   Itanium.&nbsp; I won't hazzard to guess the result at this = point...&nbsp; 8-)=20<7   <P>Charlie <BR>&nbsp; </P></BLOCKQUOTE></BODY></HTML>   - ------=_NextPart_000_00D4_01C16382.AA0C36B0--@   ------------------------------   Date: 2 Nov 2001 06:39:35 -0600h- From: Kilgallen@SpamCop.net (Larry Kilgallen)  Subject: Re: Compaq Ada for VMSu3 Message-ID: <SeMsaWoyPCDR@eisner.encompasserve.org>n  F In article <3be25c6b$1@hcwe67>, "Jakob Erber" <erberj@post.ch> writes:  . > This is a multi-part message in MIME format.  & Please don't post MIME to comp.os.vms.  L > I wonder, if we can get any save commitment from Compaq in the middle of = > the merger with HP.   C I would think the people working on the merger are at a much highereC level than those who make decisions about language support.    ThisyA might be different if we were talking about Unix, where there ared( two different Unix departments to merge.   ------------------------------  % Date: Fri, 02 Nov 2001 09:45:56 -0500T> From: Charlie McCutcheon <charlie.mccutcheon@NOSPAMcompaq.com> Subject: Re: Compaq Ada for VMS 0 Message-ID: <3BE2B1A4.2DF3D8F7@NOSPAMcompaq.com>  & --------------D49FA4D13954645D70B30037* Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit    Jakob Erber wrote:  G > I wonder, if we can get any save commitment from Compaq in the middle G > of the merger with HP.This uncertainty makes even us, traditional VMS = > customers, thinking about moving to Unix of another vendor.S  5 I doubt the HP merger will effect this decision much.S  G It is a goal for OpenVMS management to have an Ada on Itanium, but thati not have to be Compaq Ada.   CharlieR      & --------------D49FA4D13954645D70B30037) Content-Type: text/html; charset=us-ascii  Content-Transfer-Encoding: 7bit   > <!doctype html public "-//w3c//dtd html 4.0 transitional//en"> <html> <body bgcolor="#FFFFFF"> Jakob Erber wrote:% <blockquote TYPE=CITE><style></style>e" <font face="Arial"><font size=-1>IF wonder, if we can get any save commitment from Compaq in the middle ofF the merger with HP.</font></font><font face="Arial"><font size=-1>ThisK uncertainty makes even us, traditional VMS customers, thinking about moving 5 to Unix of another vendor.</font></font></blockquote>T  < <p><br>I doubt the HP merger will effect this decision much.J <p>It is a goal for OpenVMS management to have an Ada on Itanium, but that not have to be Compaq Ada.
 <p>Charlie
 <br>&nbsp;
 <br>&nbsp; </body>t </html>   ( --------------D49FA4D13954645D70B30037--   ------------------------------  % Date: Fri, 02 Nov 2001 16:49:36 +00000( From: Nic Clews <sendspamhere@127.0.0.1> Subject: Re: Compaq Ada for VMS ) Message-ID: <3BE2CEA0.6B329002@127.0.0.1>n  Z > >      "Charlie McCutcheon" <charlie.mccutcheon@NOSPAMcompaq.com> schrieb im Newsbeitrag. > >      Sorry, Ada 95 is not the only issue.  > > o > >      And yes, Compaq Ada will never be upgraded to the Ada 95 language version.  If you > > need Ada 95, wel. > >      recommend GNAT Pro, provided by ACT.  > > | > >      OpenVMS management is actively working on the issue of Ada for Itanium.  I won't > > hazzard to guess the result at > >      this point...  8-)  > >   b > I wonder, if we can get any save commitment from Compaq in the middle of the merger with > > HP.q > This uncertainty makes even us, traditional VMS customers, thinking about moving to Unix > > of another vendor.s  n3 (tried to get correct attribution despite the html)o  H This isn't the right forum (hopefully we are talking to the right peopleC at the right level and I appreciate the official position being puthH here, this proves Compaq are a listening company), but the basic problem is this.  F If a large user of the Ada 83 standard has long term future investmentE decisons to take, which in this day in age could easily involve inter  continental collaborations...e  E If they are forced to reinvent everything they have so far under VMS, H just to be able to buy Itanium systems, there will be no VMS alternativeF at investment levels that would require strong smelling salts to bringC round Scottish sales execs, in the timescales this user is involvedn) with, they may well turn around and say:-t  F "Well if we've got to put so much work into it under the VMS platform,C which we have to justify to OUR internal management, we may just be 4 forced, or do the job anyway under somebodies UNIX."  G Bye bye VMS customers. (And their preferred UNIX supplier may not HP oro Compaq).   Go ahead, make their day.< -- e( Regards, Nic Clews CSC Computer Sciences nclews at csc dot comt   ------------------------------   Date: 2 Nov 2001 13:43:12 GMTg1 From: bill@triangle.cs.uofs.edu (Bill Gunshannon)h' Subject: Re: Compaq goes back to schoole, Message-ID: <9ru7tg$2kb1$1@info.cs.uofs.edu>  * In article <3BE1A561.74694526@dplanet.ch>,)  John McLean <mcleanj@dplanet.ch> writes:h |> .E |> I was pleased to see in the "success stories" an article about theeK |> library system at Penn State University.  The extended article says  "We H |> use Compaq Alpha VMS Servers for all locally mounted databases," saidJ |> Michael Bender, Senior Systems Engineer. "Compaq Alpha UNIX Servers runK |> our Web sites. And Compaq ProLiant Servers (Series  6000, 5500, 3000 and 6 |> 1500) serve as our Windows NT and Novell servers."  |> a  H Yes, but for every success story there is also a failure story (Hmmm. is" this a corolary of Newton's Law??)  J A briefing paper passed out by our head of IT yesterday included this gem:K   5. VMS operating system...we're beginning to look at potential transitionaO       plans away from VMS to other operating systems in a three-year timeframe.m  C A parking lot conversation with the next lower level of mamnagementeF responsible for this said the front runner was IBM (funny really, thisG was a totally Blue shop administratively when I came here ~15 years agorF and VMS displaced them.) and the primary reason was the uncertainty of4 the future of VMS.  We currently use Oracle and SCT.   bill   -- iJ Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>   a   ------------------------------  % Date: Fri, 02 Nov 2001 14:47:58 +0000 % From: Alan Greig <a.greig@virgin.net> ' Subject: Re: Compaq goes back to schools8 Message-ID: <lmb5utcvf7efe61j6ah4tvt2uofb4vffcb@4ax.com>  ; On 2 Nov 2001 13:43:12 GMT, bill@triangle.cs.uofs.edu (Bill  Gunshannon) wrote:   >bK >A briefing paper passed out by our head of IT yesterday included this gem:8L >  5. VMS operating system...we're beginning to look at potential transitionP >      plans away from VMS to other operating systems in a three-year timeframe.  D So will. Rich Marcello and Mark Gorham turn up at your University toE push VMS? I bet not. At my old university employer DEC sales actuallymD told them to phase out VMS. Wonder if Compaq sales have said similar behind Rich and Mark's back.  D >A parking lot conversation with the next lower level of mamnagementG >responsible for this said the front runner was IBM (funny really, thisdH >was a totally Blue shop administratively when I came here ~15 years agoG >and VMS displaced them.) and the primary reason was the uncertainty of05 >the future of VMS.  We currently use Oracle and SCT.:  F What uncertain future of VMS? It's got a very bright future or so RichE and Mark keep telling us. Funny thing is there's even some people whoo
 believe them.   D I've said this before folks but the battle to save VMS has been lostE because the opposing forces think they have a truce. Want to overturnc9 that then wake up, smell the coffee and re-enter battle. -  ? Anyone reading this working for the military or other sensitivemC application? Think you have guarantees? Boy do Capellas and FiorinauA think you're stupid. But they won't care if you take legal actiono< later as both of them will have cashed in their millions for6 destroying HP and Compaq long before you get to court.  < Did it bother Palmer that he destroyed DEC? Of course not...     -- Alan   ------------------------------  % Date: Fri, 02 Nov 2001 10:10:46 +0000a% From: Alan Greig <a.greig@virgin.net>D Subject: Compaq guarantees?s8 Message-ID: <usr4uto8ljgrf5svf253r9vl6b79hjo4k9@4ax.com>   Just found the following:uR http://www.compaq.com/hps/ipf-enterprise/download/customer_assurance_facts_1.0.doc  B I'll leave comments for later save for one: Am I reading correctly@ that if HP terminate VMS only one year of support is guaranteed? Here's the paragraph:s  ) "AlphaServer Product Continuity GuaranteehC If the EV68 AlphaServer ES or GS family, from which you purchase or1@ lease a product, is terminated following the consummation of theF proposed merger with HP, the customer may receive a trade-in credit onC a replacement product that amounts to 110% of the original purchase D price.(2)  Also, the terminated product will continue to be servicedD and supported for five years following end-of-life notification if a5 hardware product, or one year if a software product."e   And here's the whole thing.   
 Fact Sheet The Compaq AlphaServer   Customer Assurance Program    D Compaq Computer Corporation is setting a new standard for commitmentB to customer satisfaction by being the only vendor to offer a broadD based money-back satisfaction guarantee. This exclusive guarantee is, available with all new AlphaServer systems.   A The Compaq AlphaServer Customer Assurance Program underscores ourcC overwhelming commitment to AlphaServer systems. We will ensure theytF continue to deliver significant business value for your business today@ and in the future, as the product line transitions to the 64-bitE industry standard architecture with the Itanium processor family andh' the company's proposed merger with HP. s  D This program delivers a comprehensive suite of investment protectionC initiatives, which instill confidence, reduce risk, and will assurenC you that your current and future investments in AlphaServer systemslC and Compaq operating systems are secure. Specific components of theh suite include:  * Money Back Customer Satisfaction Guarantee@ If the transition to an Itanium processor family system running> OpenVMS or the planned converged enterprise UNIX does not meetC customer expectations, Compaq will take back the Itanium processor 0 family system and refund its purchase price(1)    ( AlphaServer Product Continuity GuaranteeC If the EV68 AlphaServer ES or GS family, from which you purchase or @ lease a product, is terminated following the consummation of theF proposed merger with HP, the customer may receive a trade-in credit onC a replacement product that amounts to 110% of the original purchasemD price.(2)  Also, the terminated product will continue to be servicedD and supported for five years following end-of-life notification if a5 hardware product, or one year if a software product. s  $ Storage Product Continuity Guarantee@ If a StorageWorks or SANworks product you purchase is terminatedD following the consummation of the proposed HP merger, as a result of; the merger, the customer may receive a trade-in credit on a A replacement product that amounts to 110% of the original purchase 
 price.(2)    v  = Technology Refresh Incentives and Guaranteed Trade-In Values.t< Compaq will commit to guaranteed trade-in values for currentD AlphaServer systems being traded-in on a next generation AlphaServer- or an Itanium processor family-based system.    Transition Leasing? Compaq Financial Services will offer, in specific countries, an"E attractive lease which guarantees fixed scheduled payments across theuB transition from AlphaServer to an Itanium processor family system; running OpenVMS or the planned converged enterprise UNIX.  e     Compaq Software License Credits-E Compaq is committed to providing cost effective OS & layered softwarelD license transfers from AlphaServer systems to the Itanium processor? family systems.  The Operating System is included in the systemrE trade-in program and license sharing between mixed architectures willwA be supported.   Layered products license trade-ins are subject tot< available programs being offered at the time of transition.   ! Support for ISV License TransferseE Compaq is working closely with all of our ISV partners to ensure thatkF ISVs continue to support and deliver new functionality to customers onC current and future AlphaServer based systems. In addition, Compaq & D Intel are working closely to assist third-party ISVs in planning forE and transitioning their applications to the Compaq Itanium processor.> family-based systems. We are confident that they will have theD necessary tools, support resources, and other support to be ready toE deliver their applications on Itanium processor family-based OpenVMSn8 and the converged Unix systems when customers require.    ( Transition Tools, Resources and ServicesD Compaq will deliver a comprehensive service and support portfolio to+ help with customer and partner transitions.A  @ Compaq will provide the following, at no charge to the customers purchasing Itanium systems:i5 	Architecture Workshops to provide up to two days of8E semi-customized planning sessions to help qualified customers lay out 2 a transition plan for their current environment.  ? 	White papers that provide "How To" transitioning information i: 	On-Line support information, including remote Test DriveB systems that allow customers and partners to have direct access toE equipment to load their software through a secure connection and test  it. > 	Consulting expertise centers jointly staffed with Compaq and@ Intel experts to assist customers with design and implementation issues.e> 	Porting centers (planned for New England, the West Coast andB Reading, England) where you can test and validate your application< environment on the latest AlphaServer and Itanium processor family-based equipment.  o  ? In addition to the above free services, Compaq has an extensivedB portfolio of chargeable services available to customers to further% assist in transitions. These include:.. 	Training courses for partners and customers < 	Advanced System Architecture consulting for highly complex
 solutions ? 	Transition Assessment Services to provide a detailed analysis.B and review of customers software environment identifying tasks and+ sizing of effort to transition to Itanium.r9 	Consolidation Assessment Services - Assess the businesseE benefits to customers of combining their migration activities with ITz Consolidation.  4 	Transition/Consolidation Implementation Services -B VAX-to-Alpha, Alpha-to-Itanium, OpenVMS to Tru64/enterprise UNIX,F Tru64 UNIX-to-enterprise UNIX, Competitors UNIX-to-enterprise UNIX.   5 	Integration Services - application integration withr; middleware, eBusiness and Storage/Database technologies andh infrastructure5 	Program/Project Management Services - Best in ClassHD personnel/processes to support the customers in managing large-scale- transitions or integration projects in-house. @ 	Tuning and Optimization Services - help customers get the most out of their IT environmente= 	Specific Consulting Services - provide consulting expertisei? for specific industry, operational or technology customer needsi? 	Detailed Enterprise Architectural Planning Services - provideKC in-depth analysis and planning of customer environments moving themM forward as technology evolvesF> 	Compaq Financial Service's Transition Lease - in addition to@ locking in a level payment and fixed term transition solution toC either tomorrow's next generation AlphaServer or Itanium processori< family solution, this bundled solution contains a variety ofC transition services including an architectural workshop, transition0B assessment service, installation and setup, and service credits on selected systems.   < Compaq is so confident in the AlphaServer products plans andE technological directions that we are providing customers and partners A with a variety of investment protections, trade-in guarantees and B monetary guarantees along with comprehensive tools, resources, and? services and support to ensure a seamless transition to running;B OpenVMS or the new converged enterprise UNIX environment on future( Itanium processor family-based systems.  @ This comprehensive suite of investment protection initiatives isB available to customers and partners who purchase a new AlphaServer< -based system running Tru64 UNIX or OpenVMS today, and whoE anticipate transitioning to an Itanium processor family-based systemoF running OpenVMS or the new enterprise UNIX environments in the future.      ? (1) This is subject to agreed acceptance criterion and customert environment evaluation..  > (2) This offer expires 12 months after the consummation of the proposed merger.      -- Alan   ------------------------------  % Date: Fri, 02 Nov 2001 06:43:49 -0500e- From: JF Mezei <jfmezei.spamnot@videotron.ca>g Subject: Re: Compaq guarantees?d, Message-ID: <3BE286EE.C0812C27@videotron.ca>   Alan Greig wrote:rT > http://www.compaq.com/hps/ipf-enterprise/download/customer_assurance_facts_1.0.doc > D > I'll leave comments for later save for one: Am I reading correctlyB > that if HP terminate VMS only one year of support is guaranteed?  H That is what the text says. But in all fairness, unless this document isN signed as a legal contract, I don't believe any commitment made in it, whetherM good or bad. For one thing, Compaq has become irrelevant and anything it doeseL between now and the merger is moot since HP will be free to change things asL it wants. I am reminded by a "suggestion" by the local Compaq folks during aM presentation to customers a few weeks ago where twice the suggestion was madenM to get contracts signed on paper now. (eg: before merger) because there was ar* commitment to honour all signed contracts.  M If you need long term VMS support for your systems, then sign and pay for thei DII-COE package.   ##A > family systems.  The Operating System is included in the system=G > trade-in program and license sharing between mixed architectures willfC > be supported.   Layered products license trade-ins are subject toi= > available programs being offered at the time of transition./ ##  J So it seems that you'll have to buy new versions of your layered products.J Also, it will be interesting to see how long those trade-in programms will< allwo you to keep the old alpha and try the new intel thing.   ------------------------------  % Date: Fri, 02 Nov 2001 13:41:17 +0000 ( From: Nic Clews <sendspamhere@127.0.0.1> Subject: Re: Compaq guarantees?b) Message-ID: <3BE2A27D.7CBD1E69@127.0.0.1>-   JF Mezei wrote:0 >  > Alan Greig wrote:-V > > http://www.compaq.com/hps/ipf-enterprise/download/customer_assurance_facts_1.0.doc > >.F > > I'll leave comments for later save for one: Am I reading correctlyD > > that if HP terminate VMS only one year of support is guaranteed? > J > That is what the text says. But in all fairness, unless this document isP > signed as a legal contract, I don't believe any commitment made in it, whetherO > good or bad. For one thing, Compaq has become irrelevant and anything it does N > between now and the merger is moot since HP will be free to change things asN > it wants. I am reminded by a "suggestion" by the local Compaq folks during aO > presentation to customers a few weeks ago where twice the suggestion was madetO > to get contracts signed on paper now. (eg: before merger) because there was aa, > commitment to honour all signed contracts.  > I'm baffled. Mind you, some would say it doesn't take much :-)  E Seriously, perhaps they should be careful in their wording, and wheretE misinterpretation, or literal misunderstanding can occur, they shoulds clarify.  G From what I understand, the literal meaning you've applied above is noto correct.  A If you've got it --> If you'll pay for it --> They'll support it.n  G In their statement, there is no implication "you" are continuing to payn6 for that support. That would change the situation, no?  E In statements, there are minimum time periods stated, but no absoluteo maximums. Free lunches go cold.b  G I dunno, some people make it their business to find the black side of an
 sunny day. --  ( Regards, Nic Clews CSC Computer Sciences nclews at csc dot come   ------------------------------  # Date: Fri, 02 Nov 2001 13:45:55 GMTuB From: Simon Clubley <simon_clubley@remove_me.excite.com-Earth.UFP> Subject: Re: Compaq guarantees?w5 Message-ID: <nsxE7.9934$xS6.13250@www.newsranger.com>b  . On Fri, 02 Nov 2001 10:10:46 +0000, in article? <usr4uto8ljgrf5svf253r9vl6b79hjo4k9@4ax.com>, Alan Greig wrote:e >eC >I'll leave comments for later save for one: Am I reading correctlysA >that if HP terminate VMS only one year of support is guaranteed?: >Here's the paragraph: >n* >"AlphaServer Product Continuity GuaranteeD >If the EV68 AlphaServer ES or GS family, from which you purchase orA >lease a product, is terminated following the consummation of thenG >proposed merger with HP, the customer may receive a trade-in credit oncD >a replacement product that amounts to 110% of the original purchaseE >price.(2)  Also, the terminated product will continue to be servicedvE >and supported for five years following end-of-life notification if a 6 >hardware product, or one year if a software product." >b  ? That's how I read it (VMS support guarantees on Alpha) as well.   K Next question. Why are only the EV68 series machines mentioned ? What aboute other current machines ?  G So, if I am interpreting the above correctly, HP could drop VMS supporteH on Alpha with only one year's notice and stop all Alpha hardware support after 5 years.  F How does this compare with the PDP-10 situation ? If I remember my DECA history correctly (I have never used the PDP-10), the termination K announcement was made in 1983, and at that time, there was a committment toiL a further 5 years of active software development, and then a further 5 years of support.i  K I am also concerned about footnote number 2, because as I see it, this justpG means that HP could terminate VMS on Alpha at 12 months+1 day after thee- merger completes without financial penalties.o  J [What is a termination date anyway ? Is it the day on which you _actually_K stop selling Alpha systems, or the day that you _announce_ you plan to stop = selling Alpha systems at some specified date in the future ?].  G It's interesting to note that the financial guarantee only specifies "a E replacement product" and not a "IA64 machine running VMS", so there'ssK nothing to stop HP from specifying, in theory, that the replacement machine  is a NT system of some kind.   >i+ >Money Back Customer Satisfaction Guarantee A >If the transition to an Itanium processor family system runningu? >OpenVMS or the planned converged enterprise UNIX does not meetoD >customer expectations, Compaq will take back the Itanium processor1 >family system and refund its purchase price(1)  R > @ >(1) This is subject to agreed acceptance criterion and customer >environment evaluation.  < I notice that just _what_ the criteria are is not specified.   >r? >(2) This offer expires 12 months after the consummation of the  >proposed merger.n >  >--  >Alane   Simon.   --  ; Simon Clubley, simon_clubley@remove_me.excite.com-Earth.UFPaK In the task of removing Microsoft from the marketplace, I have discovered acE truly remarkable plan, but this signature is too small to contain it.n   ------------------------------  % Date: Fri, 02 Nov 2001 09:51:17 -0500S- From: JF Mezei <jfmezei.spamnot@videotron.ca>a Subject: Re: Compaq guarantees?n+ Message-ID: <3BE2B2D8.551D075@videotron.ca>s  G > >price.(2)  Also, the terminated product will continue to be servicedhG > >and supported for five years following end-of-life notification if ay8 > >hardware product, or one year if a software product."  K I note the omission of the "at least" in there. From a legal pespective, isa this significant ?  N Are we to read that Compaq commits to stop supporting 5 years after a hardwareN is retired no matter what, or that it commits to support for at least 5 years, more if there is still demand ?o  N I am really surprised that they could not match software support with hardware1 and specify only one year. That *looks* VERY BAD.-  E If HP were to sell VMS as a viable product to Redhat, would contracts4J automatically transfer to Redhat or would Compaq still be bound to deliverN those contracts already signed ? This might explain why they only put that oneN year commitment for software. They are stuck with Alpha since, being dead withX no value, they can't sell it.  But they could still sell VMS and other layered products.    M > I am also concerned about footnote number 2, because as I see it, this justsI > means that HP could terminate VMS on Alpha at 12 months+1 day after theo/ > merger completes without financial penalties.   K Don't forget that some organisations may have signed DII-COE contracts thatHK garantee support for their systems for something like 10 years. It would bea: most interesting to see how those contracts would survive.  M Perhaps HP intends to drop any software not protected under previously signedfL DII-COE contracts, support them for one year and be done with them. Nut letsG speculate that the white house signed DII-COE, that would mean that VMSqM ALL-IN-1 and other related products would essentially be assured survival forsQ 10 years, but other Digital layered products for VMS would be gone within a year.n  K So perhaps the trick is to find out what layered products the military usesuN for VMS, and fear for the survival fo those products not used by the military.    M > nothing to stop HP from specifying, in theory, that the replacement machinev > is a NT system of some kind.  L Interesting. HP knows that killing VMS would result in those customers goingL to Sun or IBM.  But if they kill VMS and shove a free NT box with all the NTI software to replace the VMS stuff, wouldn't they end up retaining a larged percentage of VMS customers ?r   ------------------------------   Date: 2 Nov 2001 09:06:00 -0600e+ From: young_r@encompasserve.org (Rob Young)  Subject: Re: Compaq guarantees?n3 Message-ID: <jk3NLAxhCTq8@eisner.encompasserve.org>   [ In article <3BE2B2D8.551D075@videotron.ca>, JF Mezei <jfmezei.spamnot@videotron.ca> writes:C   > M > Don't forget that some organisations may have signed DII-COE contracts thattA > garantee support for their systems for something like 10 years.o  + 	I believe DII-COE is a 15 year commitment.    				Roba   ------------------------------  % Date: Fri, 02 Nov 2001 14:55:27 +0000S% From: Alan Greig <a.greig@virgin.net>t Subject: Re: Compaq guarantees?l8 Message-ID: <2ic5utsc0nftad3vb8drb71j2cmothdabg@4ax.com>  F On Fri, 02 Nov 2001 13:41:17 +0000, Nic Clews <sendspamhere@127.0.0.1> wrote:     > F >Seriously, perhaps they should be careful in their wording, and whereF >misinterpretation, or literal misunderstanding can occur, they should	 >clarify.v >dH >From what I understand, the literal meaning you've applied above is not	 >correct.u   Nic,  D I am absolutely sure they have been very careful with the wording. I= just wish you would accept (at the very least) that there's at= possibility my interpretations are correct and apply pressurerD accordingly and *keep that pressure up until the day the Itanum port hits the market*   >hB >If you've got it --> If you'll pay for it --> They'll support it. >oH >In their statement, there is no implication "you" are continuing to pay7 >for that support. That would change the situation, no?y >mF >In statements, there are minimum time periods stated, but no absolute  >maximums. Free lunches go cold. >iH >I dunno, some people make it their business to find the black side of a >sunny day.e  @ I'm a realist Nic with a good track record of seeing through the DEC/Compaq smokescreens.     -- Alan   ------------------------------  % Date: Fri, 02 Nov 2001 15:30:02 +0000N% From: Alan Greig <a.greig@virgin.net>d Subject: Re: Compaq guarantees?i8 Message-ID: <oqe5ut8t9bpdnvubtvh5ida05jjb10kk37@4ax.com>  0 On Fri, 02 Nov 2001 13:45:55 GMT, Simon Clubley  > G >How does this compare with the PDP-10 situation ? If I remember my DECnB >history correctly (I have never used the PDP-10), the terminationL >announcement was made in 1983, and at that time, there was a committment toM >a further 5 years of active software development, and then a further 5 yearsf >of support.  E PDP-10 support did continue for the promised time period but that wasiD Ken's DEC and Compaq/HP had no say. Presumably DEC felt this was theD very least they could do given the bad feelings over broken apparent "Jupiter" promises.a  L >I am also concerned about footnote number 2, because as I see it, this justH >means that HP could terminate VMS on Alpha at 12 months+1 day after the. >merger completes without financial penalties. >uK >[What is a termination date anyway ? Is it the day on which you _actually_L >stop selling Alpha systems, or the day that you _announce_ you plan to stop> >selling Alpha systems at some specified date in the future ?] >lH >It's interesting to note that the financial guarantee only specifies "aF >replacement product" and not a "IA64 machine running VMS", so there'sL >nothing to stop HP from specifying, in theory, that the replacement machine >is a NT system of some kind.o >  >>, >>Money Back Customer Satisfaction GuaranteeB >>If the transition to an Itanium processor family system running@ >>OpenVMS or the planned converged enterprise UNIX does not meetE >>customer expectations, Compaq will take back the Itanium processorm2 >>family system and refund its purchase price(1)   >>A >>(1) This is subject to agreed acceptance criterion and customera >>environment evaluation.g >p= >I notice that just _what_ the criteria are is not specified.o >s >>@ >>(2) This offer expires 12 months after the consummation of the >>proposed merger. >> a >>-- >>Alan >t >Simon.d   -- Alan   ------------------------------   Date: 2 Nov 2001 11:53:43 -0600e- From: koehler@encompasserve.org (Bob Koehler)i Subject: Re: Compaq guarantees?t3 Message-ID: <bgRA6tjJb0$X@eisner.encompasserve.org>v  [ In article <3BE2B2D8.551D075@videotron.ca>, JF Mezei <jfmezei.spamnot@videotron.ca> writes:TH >> >price.(2)  Also, the terminated product will continue to be servicedH >> >and supported for five years following end-of-life notification if a9 >> >hardware product, or one year if a software product."  > M > I note the omission of the "at least" in there. From a legal pespective, is  > this significant ? >   G    Is this really different from what we have now?  How long did CompaqtE    support VMS 7.1 when VMS 7.2 shipped?  IIRC Compaq promises a five %    year EOL support for hardware now.t  >    DII-COE and existing contracts probably prevent Compaq fromB    dropping all support for VMS.  IANAL, but I don't think there'sD    anyway for HP to buy Compaq without buying those contracts.  TheyB    could support only the last version if further development ever    becomes unprofittable./  E    There's no way you're going to convince me that HP's going to walkoE    away from VMS' current profitability.  At worst they might sell ito    off.h          ------------------------------  # Date: Fri, 02 Nov 2001 18:39:01 GMTtB From: Simon Clubley <simon_clubley@remove_me.excite.com-Earth.UFP> Subject: Re: Compaq guarantees?d6 Message-ID: <9LBE7.10366$xS6.14431@www.newsranger.com>  . On Fri, 02 Nov 2001 15:30:02 +0000, in article? <oqe5ut8t9bpdnvubtvh5ida05jjb10kk37@4ax.com>, Alan Greig wrote:  >i1 >On Fri, 02 Nov 2001 13:45:55 GMT, Simon Clubley F >>H >>How does this compare with the PDP-10 situation ? If I remember my DECC >>history correctly (I have never used the PDP-10), the terminationrM >>announcement was made in 1983, and at that time, there was a committment tonN >>a further 5 years of active software development, and then a further 5 years
 >>of support.s >sF >PDP-10 support did continue for the promised time period but that wasE >Ken's DEC and Compaq/HP had no say. Presumably DEC felt this was thedE >very least they could do given the bad feelings over broken apparent  >"Jupiter" promises. >t  E I know that Compaq/HP had nothing to do with it :-), but now you havehH confirmed the support periods, it makes the point that DEC supported oldD equipment/software for long periods, while CPQ, even with enterprise6 customers, seems to have a very PC lifetime mentality.  L [BTW, this is only history to me (I started working on DEC systems in 1987),G but the thing that I always respected about the PDP-10 cancellation wassN that DEC sent someone to standup in front of the PDP-10 users at DECUS to makeI the announcement. When VMS finally gets cancelled, hopefully _many_ yearswA from now, we will probably find out about it in a press release.]j   >--a >Alanc   Simon.   -- n; Simon Clubley, simon_clubley@remove_me.excite.com-Earth.UFPpK In the task of removing Microsoft from the marketplace, I have discovered anE truly remarkable plan, but this signature is too small to contain it.0   ------------------------------  % Date: Fri, 02 Nov 2001 10:05:50 -0500u- From: "Richard D. Piccard" <piccard@ohio.edu>o Subject: Re: DEC C and DECUS( Message-ID: <3BE2B64B.E5DAB05B@ohio.edu>  G And if you are looking for errant users, you can remove the often-large ' number of system files from the report:y   $ SHOW DEVICE/FILE/NOSYS  disk  #                                 RDPh     Alan Greig wrote:s  1 > On Wed, 31 Oct 2001 10:08:41 -0700, "DigiDemon"d  > <digidemon@hotmail.com> wrote: > F > >haven't a clue what those are :-D).  What I AM looking for is for aH > >proggie that will find open files.  When I do a nightly backup of theL > >DEC, I will recieve some messages about certain files not being backed upJ > >due to them being open.  Now some I can understand (log files open willG > >most likely be open by the system account yes?)  But some aren't logeH > >files...and I'm guessing it's some user that has something open.  I'dA > >like to find out which user so I can smartly chastise them ;-)  >r+ > Are you aware of $ SHOW DEVICE/FILE disk:  >k > SHOW >  >   DEVICESe >  >     /FILES >sH >        Requires SYSPRV (system privilege) or BYPASS privileges to list >        read-protected files. >eG >        Displays a list of the names of all files open on a volume andaH >        their associated process name and process identification (PID).G >        The specified device must be a mounted Files-11 volume. If thewH >        specified volume is a multivolume set, the files on each volume >        in the set are listed.h >e > >eK > >And thanks for the GNU links...I will see if with the help of them I can : > >install SSH and have everything running like a champ :) > >m > >James >s > -- > Alan   --B ==================================================================B Dick Piccard                           Academic Technology ManagerB piccard@ohio.edu                                 Computer ServicesB http://oak.cats.ohiou.edu/~piccard/                Ohio University   ------------------------------  % Date: Fri, 02 Nov 2001 10:39:04 -0500 - From: JF Mezei <jfmezei.spamnot@videotron.ca>n Subject: Re: DEC C and DECUS+ Message-ID: <3BE2BE07.A39D053@videotron.ca>    "Richard D. Piccard" wrote:o > I > And if you are looking for errant users, you can remove the often-largei) > number of system files from the report:g >   > $ SHOW DEVICE/FILE/NOSYS  disk   My favorite:  : PIPE SHOW DEV/FILES/NOSYS disk | Search sys$input <string>  L where string can be a filename (to find who has it opened) or a user/process5 name to find what files it has opened on that volume.    ------------------------------  % Date: Fri, 02 Nov 2001 16:55:45 +0000o( From: Nic Clews <sendspamhere@127.0.0.1> Subject: Re: DEC C and DECUS) Message-ID: <3BE2D011.30D04238@127.0.0.1>r   JF Mezei wrote:a > My favorite: > < > PIPE SHOW DEV/FILES/NOSYS disk | Search sys$input <string> > N > where string can be a filename (to find who has it opened) or a user/process7 > name to find what files it has opened on that volume.a  D I was trying to contribute to this thread when Netscape dumped on me before I posted day or 2 ago.i  D I wrote a command file which did the SH DEV/FILES, found the processG ID's used logical names to discover what database was open (this is howmH it worked), use commands to close down that database, occasionally rogueF processes were left, then stop/id those against a second SH DEV/FILES, then it was all clean.  E I called it STOP_ROGUES.COM and it was designed to remove testing andyF acceptance proceses from working against the ondisk backup copy of the  database, prior to a backup run.   -- g( Regards, Nic Clews CSC Computer Sciences nclews at csc dot comu   ------------------------------   Date: 2 Nov 2001 06:55:20 -0800 ( From: bob@instantwhip.com (Bob Ceculski)* Subject: Re: DHCP client software for VMS?= Message-ID: <d7791aa1.0111020655.5c674cb6@posting.google.com>r  a Beyonder <beyonder@vrx.net> wrote in message news:<ks53utg5sdft7of3s95ivg12ges6htdrul@4ax.com>...wF > is there any way or software for VMS to set it up so it can get it's > IP address via DHCP ?e > % > something like DHCPCd or something?a >  > can anyone help? >  > Thanks >  > Ba >  > B > -----=  Posted via Newsfeeds.Com, Uncensored Usenet News  =-----C > http://www.newsfeeds.com - The #1 Newsgroup Service in the World! B >  Check out our new Unlimited Server. No Download or Time Limits!B > -----==  Over 80,000 Newsgroups - 19 Different Servers!  ==-----  ' tcpware 5.5 for vms has dhcp client ...e   ------------------------------  % Date: Fri, 02 Nov 2001 06:57:45 -0800 % From: Dean Woodward <deanw@rdrop.com>p* Subject: Re: DHCP client software for VMS?) Message-ID: <3BE2B469.ACCD4AF6@rdrop.com>o   Beyonder wrote:l > 9 > Like I'm going to find anything that obscure on ebay...i  G They go across there on a regular basis, actually.  DOCUMENTATION kits,eG too.  Sadly, the only reliable way to find them is to search for DEC ord$ COMPAQ and wade through the results.  D > I'm going to hate trying to navigate the compaq site to find it...   ------------------------------  " Date: Fri, 2 Nov 2001 14:39:11 GMT' From: Rick Dyson <Rick-Dyson@UIowa.EDU>h Subject: Free HSC40 Partsn) Message-ID: <3BE2B00F.2A226D30@UIowa.EDU>r  F     Free HSC40 boards/parts!  We are literally throwing this equipmentH away.  If anyone is interested in any of these parts, please let me knowE ASAP and they are yours, IF YOU PAY FOR SHIPPING.  They are all pulls I from an HSC40 that was functioning when it was turned off.  No guaranteesh on them.  They are "AS IS".e  '     QTY PART #      REV     DESCRIPTION".     --- --------    ---     ------------------"       1 L0117-AA    A       MEMORY+       1 L0111-YA    A       I/O CONT. PROC.t-       2 L0108-YA    C       DISK DATA CHANNELt,       1 L0119-YA    F4      D/T DATA CHANNEL-       1 L0107-YA    F       CI PORT PROCESSORe*       1 L0109-00    E       CI PORT BUFFER(       1 L0118-00    B       CI PORT LINK  H     Preference will be given to anyone who wants all or most of them, so+ I don't have to ship to multiple addresses.t   Regards,
 Rick Dyson --J Richard L. Dyson                                      rick-dyson@uiowa.eduJ  _   _  _____                      http://www-pi.physics.uiowa.edu/~dyson/J | | | ||_   _|  Senior Systems Analyst   --   INFORMM-Cerner Systems Group2 | | | |  | |    The University of Iowa Health CareJ | \_/ | _| |_   Health Care Information Systems BT1000 GH  O: 319/384-7016J  \___/ |_____|  Iowa City, IA 52242-1052                 FAX: 319/384-7020   ------------------------------  # Date: Fri, 02 Nov 2001 15:41:35 GMT11 From: "Mark D. Jilson" <jilly@clarityconnect.com>i' Subject: Re: host-based shadow questione2 Message-ID: <3BE2BEE8.1BC71EEF@clarityconnect.com>  F This is correct.  A volume label may be up to 12 characters and an SCSC node name is 6 characters thus too many characters for a lock valuei" block.  $n$label is 15 characters.   Keith Parris wrote:t > ~ > Phillip Helbig <HELBPHI@sysdev.deutsche-boerse.com> wrote in message news:<01KA6WLFSLIQ8YAE79@sysdev.deutsche-boerse.com>...L > > Since allocation-port names ($n$) only make sense for dual-ported disks,I > > is it necessary to use these names, rather than the NODE$ names, wheniB > > specifying the members of a shadow set?  This is stated in the6 > > documentation, but I see no obvious reason for it. > G > I'm told it is because Volume Shadowing uses lock value blocks (whichtB > are limited to 16 bytes in size), and there is at least one caseD > where, given the data that needed to be included in the lock valueH > block, there was enough room for an allocation class field, but not anB > entire SCS nodename, in the space available for the device name.E > ------------------------------------------------------------------- E > Keith Parris | parris at encompasserve dot org | VMS consulting on:jE > Clusters, Disaster Tolerance, Internals, Performance, Storage & I/Of   -- oD Jilly	- Working from Home in the Chemung River Valley - Lockwood, NY0 	- jilly@clarityconnect.com			- Brett Bodine fan. 	- Mark.Jilson@Compaq.com			- since 1975 or so, 	- http://www.jilly.baka.com               -   ------------------------------   Date: 2 Nov 2001 07:51:10 -0800i From: richv@mail4u.nl (Rich)V Subject: How to connect a DS20 to a Fibre  channel SAN switch an that one to a hsg80??= Message-ID: <a38c070e.0111020751.5ede742e@posting.google.com>e   Hi all,t  E I recieved some beautifull equipment over here, an Alpha server DS20,tE a hsg80 including 256Mb cache and a fibrechannel San. I do now how todA connect the hsg to the server. But i haven't a single clue how toi/ connect the SAN between them. Can anybody help?u   Youre help is apriciated,h   Rich   ------------------------------  $ Date: Fri, 2 Nov 2001 18:18:13 +0100, From: "Bart Zorn" <B.Zorn@TrueBit.nospam.nl>Y Subject: Re: How to connect a DS20 to a Fibre  channel SAN switch an that one to a hsg80?r) Message-ID: <9rukmc$or$1@news1.xs4all.nl>B  ) "Rich" <richv@mail4u.nl> wrote in messageb7 news:a38c070e.0111020751.5ede742e@posting.google.com...u	 > Hi all,e >uG > I recieved some beautifull equipment over here, an Alpha server DS20,-G > a hsg80 including 256Mb cache and a fibrechannel San. I do now how toeC > connect the hsg to the server. But i haven't a single clue how toj1 > connect the SAN between them. Can anybody help?e >B > Youre help is apriciated,  >M > Rich  C I will assume that by 'SAN' you really mean Fibre Channel Switches.g  I In that case, it is really simple. If you have one FC switch, you connecteJ all ports of the HSG80 and all FC ports on the DS20 (OK, I also assume the@ DS20 has one or two KGPSA or similar controllers) to the switch.  L If you have two switches, then that only makes sense if the DS20 also has atK least two FC controllers. In that case, you connect one port of the DS20 to@L one port of each of the switches. The same goes for each of the HSG80's. OneK controller has the two ports NEXT to each other (if you have the HSG80 in ad horizontal position, that is).  K You will have to use a terminal connection to the console port of the HSG80h to configure the disks.rL Finally, if you want to boot the DS20 off of the HSG80's, then you will have# to use the WWIDMGR console program.   I This story is, however, far from complete. You really can't do it withouttJ either reading the documentation or hiring someone who has experience with configuration like this!   Regards,  	 Bart Zornu   ------------------------------   Date: 2 Nov 2001 07:34:31 -0800o" From: horn@shsu.edu (James T Horn)C Subject: Re: Kerberos Client on OpenVMS, CSWS/APACHE, MOD_AUTH_KERBy= Message-ID: <843706dc.0111020734.3aab2df4@posting.google.com>   f "Rick Barry" <barry@star.zko.dec.com> wrote in message news:<EPbE7.1193$RL6.17487@news.cpqcorp.net>...- > <david20@alpha2.mdx.ac.uk> wrote in messages' > news:9rpird$m77$1@aquila.mdx.ac.uk...e > [snip]C > > Just downloaded and setup the Kerberos Security Client for VMS.q > >e3 > > Good news it included a full Kerberos 5 Server.-F > > Bad news it didn't seem to do anything to modify Telnet , FTP etc.G > > Contacted Compaq. Seems DEC TCPIP services will not have Kerberizedn >  versionsj= > > of Telnet, FTP etc until at least DEC TCPIP Services 5.3.b > > I > > Why on earth bother to release this (with the Title Kerberos Securityn
 >  Client)) > > without Kerberizing Telnet, FTP etc ?e > >i > > David Webb > > VMS and Unix team leader > > CCSS > > Middlesex University > L > We made the choice to ship the Kerberos client/server rather than wait forN > Kerberized"applications. That way, users/ISVs will have a supported KerberosI > API to begin porting their favorite Kerberos app plus they'd have a KDCt > running on VMS.  > * > Kerberized Telnet, etc. are coming next. >  > Rick Barry > OpenVMS engineeringc > Compaq Computer Corporation2 > Nashua, NH  E How can I find information concerning the porting our applications tot Kerberos authentication?   ------------------------------  % Date: Fri, 02 Nov 2001 10:49:28 -0600a= From: Arlen Williams <remove.arlen.williams@remove.sabre.com>l Subject: LANCP Counts . Message-ID: <3BE27A38.290F7451@remove.eds.com>  H Is it possible to do the equivalent of the following command from within
 a program?   mcr lancp sho dev /count  F I want to look for network device errors. I think I can figure out howH to do it with NML and look at the NCP counts, but not all of our network? devices are configured for DECnet so they don't show up in NCP.   D I know I could create a job and do it from DCL, but I was looking at! doing it directly from my C code.>   ------------------------------  # Date: Fri, 02 Nov 2001 11:10:40 GMTr1 From: CSABA  HARANGOZO   <csabah@zipworld.com.au>r Subject: Re: news serversn5 Message-ID: <QavE7.298$Ef.29286@nasal.pacific.net.au>j  : Phillip Helbig <HELBPHI@sysdev.deutsche-boerse.com> wrote: [...snip...]  	 	Phillip,c  < 	Please visit these sites, there you can find many free NNTP% 	servers, some will accept postings :r   	http://newssearch.pilum.net 	http://www.jammed.com9 	http://www.muenz.com   ( this might no longer there... )-  D 	The first one is quite good, has a lot of European servers as well. 	Hope this helps...  					Cheers,     Csaba  I    ----------------------------------------------------------------------<E    * Csaba I. Harangozo     |    'To err is human', said the hedgehog E    * csabah@zipworld.com.au |           as he dismounted a wirebrush.bI    ----------------------------------------------------------------------t;    EARTH::AUSTRALIA:[SYDNEY]HARANGOZO.CSABA;1, delete? [N]:d   ------------------------------  $ Date: Fri, 2 Nov 2001 09:11:11 +0100, From: "Bart Zorn" <B.Zorn@TrueBit.nospam.nl> Subject: Re: Pathworks32* Message-ID: <9rtkkk$6c6$1@news1.xs4all.nl>   It's V7.2.1.1777   Regards,  	 Bart Zorn   2 <paddy.o'brien@zzz.tg.nsw.gov.au> wrote in message/ news:01KA8E4153UA0075IW@tgmail.tg.nsw.gov.au...t > On behalf of a colleague:m > E > Can anyone advise which version of eXcursions ships with the latesty versionP > of Pathworks32 (ver 7.2).  >s > Regards, Paddy >    ------------------------------  $ Date: Fri, 2 Nov 2001 12:41:31 -0500; From: "Brian Tillman" <tillman_brian@notnoone.notnohow.com>n! Subject: Re: remote booting a VXTa$ Message-ID: <3be2dac1$1@news.si.com>  B >Can I boot the VXT at location B while leaving everything else atD >location A?  If so, can this be done over the internet?  By dialingF >router-to-router?  In either case, do I need to make sure the routers5 >route certain protocols?  Which protocols can I use?r  J If your router passes the MOP protocol you should be able to.  However, be@ aware that the VXT may want to create its page/swap files on theD Infoserver's hard drive.  Apgeing over the ISDN may not be pleasant. --A Brian Tillman                   Internet: tillman_brian at si.comhA Smiths Aerospace                          tillman at swdev.si.comd= 3290 Patterson Ave. SE, MS      Addresses modified to preventu< Grand Rapids, MI 49512-1991     SPAM.  Replace "at" with "@"8        This opinion doesn't represent that of my company   ------------------------------   Date: 2 Nov 2001 06:31:02 -0600P- From: Kilgallen@SpamCop.net (Larry Kilgallen) * Subject: Re: savesets,  CDs and attributes3 Message-ID: <nnbEEBXckcqt@eisner.encompasserve.org>   [ In article <3BE21635.8FFCC3DE@fsi.net>, "David J. Dachtera" <djesys.nospam@fsi.net> writes:  > Larry Kilgallen wrote:  G > I'm unaware of any non-(former-)DEC o.s. that provides native supportvI > for both RMS and ISO-9660. So, I'd be hard-pressed to say how you would 8 > write an ISO-9660 image while preserving RMS metadata.  E You write your formatting program to fill in the ISO-9660 fields with-% the proper data for record type, etc.e  H > 'Bout the only way I can see to do that would be MKISOFS_VMS, assumingG > one had the necessary tech. doc.'s to modify it and have it place RMSe9 > metadata in the appropriate cells so RMS would find it.-  F I don't know that program, but yes, if you have a program that doesn't( do what you want, you need to modify it.  I > Then again, given how one MOUNTs an ISO-9660 disc, I don't see how thatbH > could be enabled without mucho changes to the OpenVMS system software.? > See HELP MOUNT /MEDIA and/or the appropriate source listings.D  F If VMS does not handle this correctly, then indeed DEQ has work to do,0 but the fields are there in the ISO-9660 format.  ? >> Which other operating systems have native ISO-9660 writing ?y > F > At the risk of awakening Andrew, I believe Solaris does, at the very+ > least, but I'm probably wrong about that.o  # That's useful information.  Thanks.-   ------------------------------  $ Date: Fri, 2 Nov 2001 09:07:15 -00004 From: "Chris Sharman" <chris.sharman@ccagroup.co.uk>0 Subject: set account for accounting log purposesB Message-ID: <1004691882.13125.0.nnrp-14.9e989e7e@news.demon.co.uk>  I I've had a piece of kernel mode code that I've used for some years to setn2 account name (to "Dialup") for the accounting log.   This is the core of it:y         movzbl  (r7)+, r6    ; jib$t_account         asciis  C         movc5   r6, (r7), #^a" ", #jib$s_account, jib$t_account(r5)s   ; ctl$t_account         ascii   >         movc5   r6, (r7), #^a" ", #ctl_acclen, g^ctl$t_account   1$:     movl    #1, r0         ret   4 It's worked fine on both VAX & Alpha for many years.D Now (new machine, VMS 7.3) it fills in the JIB, but ctl$t_account is unchanged at image exit !!3 And no, it doesn't crash either - I'd have noticed. " I tried relinking it, to no avail.A Any suggestions ?? Is it something to do with $persona services ?1K Is there another field I need to fill in, or should I use the persona stuffn' for a permanent (until logout) change ?t   Thanks,  ChrisA   ------------------------------   Date: 2 Nov 2001 06:45:05 -0600a- From: Kilgallen@SpamCop.net (Larry Kilgallen)l4 Subject: Re: set account for accounting log purposes3 Message-ID: <7ifVW$FtvlIl@eisner.encompasserve.org>=  y In article <1004691882.13125.0.nnrp-14.9e989e7e@news.demon.co.uk>, "Chris Sharman" <chris.sharman@ccagroup.co.uk> writes:   K > I've had a piece of kernel mode code that I've used for some years to seti4 > account name (to "Dialup") for the accounting log.  F > Now (new machine, VMS 7.3) it fills in the JIB, but ctl$t_account is > unchanged at image exit !!  C > Any suggestions ?? Is it something to do with $persona services ?i  E Absolutely.  You really need to read the full description (start withmG the V7.2 release notes) of Alpha kernel changes to implement per-thread 	 security./  G When you think you have read it all, try HELP INSTALL ADD/ARB_SUPPORT .    ------------------------------  $ Date: Fri, 2 Nov 2001 15:13:16 -00004 From: "Chris Sharman" <chris.sharman@ccagroup.co.uk>4 Subject: Re: set account for accounting log purposesB Message-ID: <1004713843.28350.0.nnrp-02.9e989e7e@news.demon.co.uk>   Thanks for that.I Documentation not all that clear, but it appears that all I need to do isr $persona_modify(0, ...); No more kernel code - great !/   Thanks, Chris Sharman   : "Larry Kilgallen" <Kilgallen@SpamCop.net> wrote in message- news:7ifVW$FtvlIl@eisner.encompasserve.org...eK > In article <1004691882.13125.0.nnrp-14.9e989e7e@news.demon.co.uk>, "Chrisu/ Sharman" <chris.sharman@ccagroup.co.uk> writes:o >II > > I've had a piece of kernel mode code that I've used for some years to, setd6 > > account name (to "Dialup") for the accounting log. >bH > > Now (new machine, VMS 7.3) it fills in the JIB, but ctl$t_account is > > unchanged at image exit !! >eE > > Any suggestions ?? Is it something to do with $persona services ?  > G > Absolutely.  You really need to read the full description (start witheI > the V7.2 release notes) of Alpha kernel changes to implement per-thread  > security.a > I > When you think you have read it all, try HELP INSTALL ADD/ARB_SUPPORT .c   ------------------------------   Date: 2 Nov 2001 09:19:49 -0600 - From: Kilgallen@SpamCop.net (Larry Kilgallen) 4 Subject: Re: set account for accounting log purposes3 Message-ID: <lFZtKpxsgZBs@eisner.encompasserve.org>n  y In article <1004713843.28350.0.nnrp-02.9e989e7e@news.demon.co.uk>, "Chris Sharman" <chris.sharman@ccagroup.co.uk> writes:e > Thanks for that.K > Documentation not all that clear, but it appears that all I need to do iso > $persona_modify(0, ...);  2 Of course that requires privilege (IMPERSONATE ?).   > No more kernel code - great !f  & But you formerly were using CMKRNL :-)   ------------------------------  + Date: Fri, 02 Nov 2001 09:48:35 +0100 (MET)t9 From: Phillip Helbig <HELBPHI@sysdev.deutsche-boerse.com>- Subject: Re: SET TERM/INQp; Message-ID: <01KA82UKSM8I90UTW5@sysdev.deutsche-boerse.com>   E > > Why does SET TERMINAL/INQUIRE take much longer when issued from a0& > > DECterm than from a real terminal? > M > In my experience, SET TERM/INQUIRE is MUCH faster on a decterm running on a6, > VAXstation 3100-30 than on a VT320 or 220.  J I am connected to several (rather fast---GS140 etc) machines both through F DECterms running on a DEC 3000 - M300X and through a VT520.  I notice D that the SET TERM/INQU is MUCH quicker from the VT 520 (I'll have toH check a VT320 and perhaps even a VT102 at home) than from the DECterm.  F I notice an eXcursion window is also fast.  Perhaps it is because the . 3000 M300X is so slow (slower than the VT520)?   ------------------------------  % Date: Fri, 02 Nov 2001 05:13:12 -05002- From: JF Mezei <jfmezei.spamnot@videotron.ca>! Subject: Re: SET TERM/INQ , Message-ID: <3BE271B7.A5F2F4A8@videotron.ca>   Phillip Helbig wrote:lK > I am connected to several (rather fast---GS140 etc) machines both through G > DECterms running on a DEC 3000 - M300X and through a VT520.  I noticeo8 > that the SET TERM/INQU is MUCH quicker from the VT 520  C When I wriote a script for my PSION to login and respond to the SET-I TERM/INQUIRE prompts, the way it seemed to work is that the host make oneOJ inquiry and if there isn't a response inside of a certain timeout, it thenN makes another inquiry (older terminals which don't recognize the first prompt)
 and so on.  M In your decterm config, ( OPTIONS -> GENERAL) try setting it to VT300 mode, 8fM bits, and also try setting the Terminal ID to DECTERM.  Maybe if it is set totJ a "lower" terminal, DECterm waits for the later prompts before responding.   ------------------------------  $ Date: Fri, 2 Nov 2001 12:39:20 -0500; From: "Brian Tillman" <tillman_brian@notnoone.notnohow.com>  Subject: Re: SET TERM/INQe$ Message-ID: <3be2da3e$1@news.si.com>  B >Why does SET TERMINAL/INQUIRE take much longer when issued from a# >DECterm than from a real terminal?m  K You shouldn't be doing a SET TERM/INQ from a DECterm.  Put the following in , the INTERACTIVE portion of your SYLOGIN.COM:  K  $ if f$getdvi( "sys$command", "devtype" ) .eq. 0 then set terminal/inquirei --A Brian Tillman                   Internet: tillman_brian at si.comsA Smiths Aerospace                          tillman at swdev.si.com = 3290 Patterson Ave. SE, MS      Addresses modified to prevent < Grand Rapids, MI 49512-1991     SPAM.  Replace "at" with "@"8        This opinion doesn't represent that of my company   ------------------------------   Date: 2 Nov 2001 12:14:43 -0600s- From: Kilgallen@SpamCop.net (Larry Kilgallen)o Subject: Re: SET TERM/INQo3 Message-ID: <CYcDl3UrtvZ4@eisner.encompasserve.org>e  b In article <3be2da3e$1@news.si.com>, "Brian Tillman" <tillman_brian@notnoone.notnohow.com> writes:C >>Why does SET TERMINAL/INQUIRE take much longer when issued from a,$ >>DECterm than from a real terminal? > M > You shouldn't be doing a SET TERM/INQ from a DECterm.  Put the following in . > the INTERACTIVE portion of your SYLOGIN.COM: > M >  $ if f$getdvi( "sys$command", "devtype" ) .eq. 0 then set terminal/inquire   @ That has no effect when one uses the DECterm to SET HOST/DTE and% subsequently encounters a VMS system.c   ------------------------------   Date: 2 Nov 2001 07:11:51 GMT-- From: djweath@attglobal.net (Dave Weatherall)a. Subject: Re: SYS$EXAMPLES:DAYLIGHT_SAVINGS.COM5 Message-ID: <DTiotGxQ0bj6-pn2-mdTH1dKZlJZM@localhost>,  > On Thu, 1 Nov 2001 20:53:24, martin@radiogaga.harz.de (Martin  Vorlaender) wrote:  2 > Mark D. Jilson (jilly@clarityconnect.com) wrote: > > Bart Zorn wrote:P > > > At least the MET time zone rule (again, still, whatever) is wrong (OpenVMSL > > > V7.3). It changes the DST on the 4th Sunday of March/October, where itN > > > should be the LAST Sunday. Last weekend it didn't make a difference, but > > > next March it will.a > >0I > > My understanding is that you are seeing the rule for the current yearlL > > and when 2002 rolls around you will see the correct rule for that year. K > > In other words the rule is correct for 2001 and you cannot see what thec< > > rule will be for 2002 unless the actual time is in 2002. > 5 > Errr... no. Unless they change some files, that is.e > F > The timezone rules are in files in SYS$COMMON:[SYS$TIMEZONE.SYSTEM],M > with the sources to these (binary) files being in SYS$COMMON:[SYS$TIMEZONE.:H > SYSTEM. SOURCES] (pre7.3 it's SYS$ZONEINFO). This is pointed to by the+ > logical SYS$TZDIR. In 7.2 it says for METl > A > # Zone  NAME            GMTOFF  RULES/SAVE      FORMAT  [UNTIL]17 > Zone    MET             1:00    M-Eur           MET%s  > K > # Rule  NAME    FROM  TO    TYPE  IN    ON       AT      SAVE    LETTER/S I > Rule    M-Eur   1986  max   -     Mar   lastSun  2:00s   1:00    " DST"hD > Rule    M-Eur   1996  max   -     Oct   lastSun  2:00s   0       - > E > which is the correct rule. This gets compiled into a TZ string likeM > & >    MET-1MET DST-2,M3.5.0/2,M10.5.0/3 > J > where the "5.0" stands for "last sunday". It does read "4.0" in VMS 7.3, > which means "4th sunday".n > J > Read all about it in the System Manager's Manual, the C Run-Time LibraryI > Reference Manual, and the C Run-Time Library Utilities Reference Manualu# > (this one also in the OS docset).k   MartinF               I suppose 5.0 means  "fifth actual" or "last possible". F e.g in a month with five sundays (1, 8, 15, 22, 29), as opposed to one with four  (4, 11, 18, 25)..   Had me wondering for a minute.   -- o Cheers - Dave.   ------------------------------  % Date: Fri, 02 Nov 2001 10:34:37 +0200o* From: Mike Rechtman <rechtman@tzora.co.il>! Subject: Re: Undo disk Initialized* Message-ID: <3BE25A9D.2050300@tzora.co.il>  ,  From the page it seems to apply to W2K only  
 Van wrote:  w > system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-) wrote in message news:<00A0456F.C7A4E7D9@SendSpamHere.ORG>...a > V >>In article <3BDFF7FB.A6739EE7@127.0.0.1>, Nic Clews <sendspamhere@127.0.0.1> writes: >> >>>Piyush Avichal wrote: - >>>-P >>>>Does anyone know of any software or know how to undo the initialization of aS >>>>disk. One of our users has accidently initilized an optical disk. It hasnt been.7 >>>>written to so the data should still be on the disk.< >>>> >>$ BACKUP  ;) >> >> >>B >>>Why are you giving users enough privileges to initialise disks? >>>.+ >>PeeCee or unix admin background no doubt.7 >> >>I >>>There's no UNFORMAT command available. My first stab at recovering therG >>>data would be to create a partition identical in size to the opticaleI >>>disk, do a BACKUp/physical, then try a number of the freeware UNDELETEtJ >>>programs. Providing they don't depend on the INDEXF.SYS and can pick up, >>>the file headers, you may have some luck. >>>sH >>Nearly all of the VMS undelete utilities rely upon the INDEXF.SYS fileJ >>being intact.   During a "DELETE", the bitmaps are modified but the file. >>header data remains more or less unchanged.  >>I >>Having no INDEXF.SYS to tie things together, it would be a *monumental*eJ >>task to scavenge the disk block by block to associate the data that each4 >>contains with some previously defined association. >> >  > Hi,oH > I know very good undeleted utilities R-STUDIO.I used its for restoringG > of my files deleted accidantly because hard disk partition structuresB > was damaged.A > My files have been restored.This program has a few utilites foraD > restoring types of file systems. Look site http://www.r-tt.com for > more information > Best regards >      -- -E ---------------------------------------------------------------------e; Usual disclaimer: All opinions are mine alone, perhaps not  
 even that.? Mike Rechtman                            *rechtman@tzora.co.il*e/ Kibbutz Tzor'a.                          Voice   (home):(972)-2-99083377    "20% of a job takes 80% of the time, the rest takes   another 80%"E ---------------------------------------------------------------------l* ------ GEEK CODE BLOCK (Version: 3.1)-----( GCM/CS d(-)pu s:+>:- a++ C++ U-- L-- W++' N++ K? w--- V+++$ PS+ PE-- t X- tv-- b+m DI+ D-- G e++ h--- r+++ y+++@n* ---------- END GEEK CODE BLOCK  ----------   ------------------------------  $ Date: Fri, 2 Nov 2001 09:01:39 -0000* From: Marley Claire <ClaireMa@musgrave.ie> Subject: unsubcribenR Message-ID: <F1C3D1EC4417D311871000508B2C3E2301C1D443@exchange2.musgravegroup.net>   unsubscribe-   ------------------------------  % Date: Fri, 02 Nov 2001 08:34:11 -0700,* From: Terry Aardema <taardema@nrcan.gc.ca>3 Subject: Re: V7.2-2 in Canada? Release date in USA?p' Message-ID: <3BE2BCF3.1FB1@nrcan.gc.ca>/   Peter Weaver wrote:m > - > Have any Canadian sites received 7.2-2 yet?t > M > I seem to recall that some people in the newsgroup reported receiving their   > copies in September. I checkedL > http://www.openvms.compaq.com/openvms/announce722.html but Compaq in theirJ > infinite wisdom decided to tell me today's date rather than the date theK > page was last updated. (Mind you, if I look at the "Updated" meta data in-N > the HTML code I would have to believe the 7.2-2 was announced "13-03-2000.") > L > We are being told that shipping in Canada will not start until 7-DEC-2001,N > but I hope that someone is giving us the wrong information and that shipping > has already started.  B You are being told incorrect information; I received our 7.3 Kit aE couple/three months ago, followed by the 7.2-2 kit two or three weeks5A ago. As for where our shop is, took-a-look at the sig. block, eh!   
 Terry Aardemav Systems and Network ManagernB Natural Resources Canada\Canadian Forest Service\Northern Forestry Centre Edmonton, Alberta, CANADA- taardema@nrcan.gc.ca   ------------------------------   Date: 2 Nov 2001 11:14:27 GMTm3 From: vance@alumni.caltech.edu (Vance R. Haemmerle) - Subject: Re: Web Browser for OpenVMS 1.5-1H1?., Message-ID: <9rtv6j$6hk@gap.cco.caltech.edu>  = In article <de844d64.0111011244.3f4a6170@posting.google.com>,n- Dale Frameli <dframeli@aus.telusa.com> wrote:uF >Is there a web browser that's compatible with OpenVMS v1.5-1H1?  It'sF >doesn't have to have all the bells and whistles, just as long as it'sD >functional :)  When I say functional, I mean it can browse webpagesA >and download files.  Maybe Netscape has an obsolete VMS friendly.D >version of their browser in their archives?  VMS Mosaic?  Something >else maybe?  8   The current version of VMS Mosaic (3.6-2) available atC http://wvnvms.wvnet.edu/vmswww/vms_mosaic.html says it's compatable I with OpenVMS V1.5...  (from ftp://alpha.wvnet.edu/mosaic/README.VMS-3_6):R  A VMS Mosaic has been generated and tested on VAXes running OpenVMSy@ 5.4 thru 7.2 and on Alpha systems using OpenVMS V1.5 thru 7.2-1.= The systems have used UCX, CMU, MultiNet, Pathway, TCPware oru< SOCKETSHR with NETLIB.  CMU TCP/IP is supported via LIBCMUII> or SOCKETSHR.  The program has been compiled with VAX C, DEC CB (both VAX and Alpha) and GNU C (VAX version 2.7.1 only).  Versions2 1.1 thru 1.2-5 of DECwindows Motif are supported.   H It's an excellent browser considering that source is available.  In factG I recently used it a lot for web sites that Mozilla wasn't working with F until the 0.9.5 version.  If compiled with OpenSSL, you can connect toH https sites for which Netscape 3.03 Gold has a security library problem.   -- Vance HaemmerleI vance@alumni.caltech.edu   ------------------------------  % Date: Fri, 02 Nov 2001 09:07:05 +0000 % From: Alan Greig <a.greig@virgin.net>h/ Subject: Re: X.25 profile documentation wanted.o8 Message-ID: <94o4utg1f36n0maoqbjl8nse9ouqcfbthk@4ax.com>  C On Thu, 01 Nov 2001 23:14:11 +0000, "a.carlini" <arcarlini@iee.org>e wrote:   >N >a >Alan Greig wrote:C >> When was the last sale date for the DECNIS? If it was later thanpH >> 1-FEB-1996 then support should not have ended on 1-FEB-2001 accordingD >> to the letter we received signed by Michael Capellas. An absoluteG >> minimum of 5 years hardware and software support should be available>H >> after date of last sale although I am still awaiting clarification onA >> Storageworks items which have ben retired from full support in  >> violation of this promise.b > ? >I don't have an official date handy but 1996 is way too early.-  >1998/1999 would be much closer.  C In that case I'd suggest anyone unhappy with the end of support foru@ the DECNIS contacts Compaq and remind them Michael Capellas  hasD promised to provide *full* support for Enterprise systems (includingD associated  controllers, networking etc) for a minimum of five years/ after last sale for both hardware and software.h  B It's about time Compaq proved that at least some of their promisesE were actually made in good faith and not just a case of "say anything$C just long enough to placate the gullible while we complete our real6 plans"..  D >> Or did the DECNIS go to DNPG? If so do they not still support it? > , >By now, DECnis support may be being done by' >DNPG - but since your support contracti  @ I've checked and there doesn't seem any obvious reference to the DECNIS on the DNPG site.  ( >(if any) will be with COMPAQ, it should1 >not matter to you where the call gets redirectedg >after that. >o >Antonio   -- Alan   ------------------------------   End of INFO-VAX 2001.610 ************************