1 INFO-VAX	Tue, 14 Aug 2001	Volume 2001 : Issue 450       Contents:( Re: Alpha:  an invitation to communicate$ Re: AMD and Samsung could save Alpha. Re: Can queue manager handle 100.000 entries ?. Re: Can queue manager handle 100.000 entries ? Re: CETS invitation / Cloning and snapshotting on an HSG from OpenVMS 3 RE: Cloning and snapshotting on an HSG from OpenVMS 3 Re: Cloning and snapshotting on an HSG from OpenVMS   DECnet-Plus on an alternate disk Does MOD_PERL work on VMS  F.Y.I OpenVMS FAQ address H Re: Free VT terminal emulators supporting DRCS downloadable characters ?3 Re: HELP!  error adding entries to quota file?!?!?! 3 Re: HELP!  error adding entries to quota file?!?!?!   Re: Help! Boot Block Information  Re: Help! Boot Block Information How to add a network printer? ! Re: How to add a network printer? ! Re: How to add a network printer? = Re: I just have to post this - and apoligse later Alpha/Intel = Re: I just have to post this - and apoligse later Alpha/Intel = Re: I just have to post this - and apoligse later Alpha/Intel = Re: I just have to post this - and apoligse later Alpha/Intel = Re: I just have to post this - and apoligse later Alpha/Intel 1 Re: Installing V7.3 on Personal Workstation 500au % Re: Intel running out of hard assets? % Re: Intel running out of hard assets?  Re: Linker-Warnings in VMS 7.3 Re: Linker-Warnings in VMS 7.37 Re: OT: Citroen C5 Re: AMD and Samsung could save Alpha 7 Re: OT: Citroen C5 Re: AMD and Samsung could save Alpha  Re: Press Release  Re: Press Release . Re: Pseudo Terminals to emulate LAT Terminals?. RE: Pseudo Terminals to emulate LAT Terminals?. Re: Pseudo Terminals to emulate LAT Terminals?# Re: Query string problem with CSWS.  SCSI ID on RZ23  Re: SCSI ID on RZ23  Re: SCSI ID on RZ23  Re: Server up?" Re: Storageworks retirement letter" Re: Storageworks retirement letter" Re: Storageworks retirement letter" Re: Storageworks retirement letter" Re: Storageworks retirement letter" Re: Storageworks retirement letter" Re: Storageworks retirement letter Testing new email A Re: The Alpha Systems Customer Update will no longer be published A Re: The Alpha Systems Customer Update will no longer be published A Re: The Alpha Systems Customer Update will no longer be published A Re: The Alpha Systems Customer Update will no longer be published / Re: Using Ghostscript to conv PS to PDF on VMS. / Re: Using Ghostscript to conv PS to PDF on VMS. / Re: Using Ghostscript to conv PS to PDF on VMS. ! Re: VAX/ALPHA FORTRAN and me! :-) # Re: VIRUSES: What about antibodies? % Re: Writing to a DOS floppy under VMS % Re: Writing to a DOS floppy under VMS   F ----------------------------------------------------------------------  % Date: Fri, 10 Aug 2001 17:01:28 -0600  From: yyyc186@mindspring.com1 Subject: Re: Alpha:  an invitation to communicate ; Message-ID: <3b746866$1$lllp186$mr2ice@nntp.mindspring.com>   3 In <3B54B992.A56087CD@videotron.ca>, on 07/17/2001  =    at 06:18 PM, JF Mezei <jfmezei.spamnot@videotron.ca> said:   C >If a brain surgeon can't set the clock on his VCR, do you call him I >incompetent ? If the brain surgeon outsources the maintenance of his VCR H >to his kids because the kids are much better at making the "12:00" stop6 >blinking, do you call the brain surgeon incompetent ?  G If the brain surgeon can't sterilize the scalpal they are about to use, C then they are completely incompetent.  If the brain surgeon doesn't J realize they actually have to have the staples for the staple gun in order0 to seal the incision, then they are incompetent.  H Compaq as seen fit to give away the staples (thanks to G. Q. Oswald) andG soon they will realize that the staple gun doesn't *&^%&^%$*&^%ing work H anymore.  At that point the only remediation will be for shareholders to# file criminal charges with the SEC.    Roland --  ; -----------------------------------------------------------  yyyc186@mindspring.com; -----------------------------------------------------------    ------------------------------   Date: 14 Aug 2001 16:15:33 GMT1 From: bill@triangle.cs.uofs.edu (Bill Gunshannon) - Subject: Re: AMD and Samsung could save Alpha , Message-ID: <9lbir5$2sge$2@info.cs.uofs.edu>  ( In article <9l8tp8$f9p$1@pyrite.mv.net>,*  "Bill Todd" <billtodd@foo.mv.com> writes: |>  M |>          Linux alone likely isn't nearly sufficient to justify the cost of M |> continued Alpha development, though Linux plus Win64 might be if Microsoft ; |> and AMD got together (not that I expect that to happen:    E Let's not forget that all three comon flavors of BSD run ont he Alpha  right out of the box too. 8                                                         M |>                                                          AMD will be lucky / |> if Microsoft even deigns to support x86-64).   E MicroSoft will support whatever puts money in Bill Gates' wallet.  If D Alpha were inthe hands of someone who was willing and able to marketD it effectively there is no reason to believe that MicroSoft wouldn'tE revive efforts to put Windows on it.  Of course, this wouldn't do any ? good for VMS people, but it would be nice to see Alpha survive.    bill   --  J 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>       ------------------------------  % Date: Tue, 14 Aug 2001 09:22:30 +0200 < From: Jan-Erik =?iso-8859-1?Q?S=F6derholm?= <noone@home.com>7 Subject: Re: Can queue manager handle 100.000 entries ? ( Message-ID: <3B78D1B6.54A3E0A5@home.com>   Hi. : As I wrote in another post, my tests showed that the entry/ numbers goes (I'v added dots to ease reading) :   4 1 -> 9999 -> 1.00.0000 -> 1.00.9999 ... -> 9.00.9999) -> 10.00.0000 -> 10.00.0001 -> 10.00.0002   > Someone else sad that position 5 and 6 in the entry number was@ allocated for "queue-manager-ID" or something like that, "00" in9 my examples since I run with just a singel QMAN instance.   C But, what was interesting, was that I actualy could enter > 100.000 9 entries but Hoff wrote that that wasn't possible. (Or was   "not supported", don't remember)  C And, to revert back to the original poster, there was no measurable A slowdown from the first to the 100.000'st entry. The QMAN$JOURNAL  file grow to > 350.000 blocks.   Jan-Erik Sderholm.    Dave Baxter wrote: > H > I have seen this behaviour on my system intermittently.    By default,C > VMS will assign Entry numbers in the range 0-9999.   When 9999 is F > reached, the system will wrap back to 0, continuing to assign unused > numbers within this range. > F > Within our organization we support >1500 print queues and have foundE > that if busy queues are stalled (letting print jobs back up), or if E > queues are set to "/RETAIN" (thus locking up entry numbers), to the G > point that there are no available entry numbers in the default range, D > then the range will jump out to 1000000 - 9999999. (Note:: 10000 - > 999999 are not used.). >  [snip] > 
 > Dave Baxter  > VAX Alpha System Manager > Banner Health Systems.   ------------------------------    Date: 14 Aug 2001 10:21:26 +0200G From: Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de> 7 Subject: Re: Can queue manager handle 100.000 entries ? H Message-ID: <y4lmkn8321.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>  4 hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) writes:  H > :>   Up to five queue managers can be sharing the same queue database.I > :Is this limitation dictated by locking scalability considerations, or  3 > :just the limit of your testing and thus support?  >   Does it matter?   N Operationally, no. Psychologically, yes. Which means: sometimes I just want toH understand why the world is as it is. Professional impairment, you know.   	Jan   ------------------------------  % Date: Tue, 14 Aug 2001 11:29:41 -0500 : From: "Pedro A. Crespo" <pedro.crespo@integris-health.com> Subject: Re: CETS invitation0 Message-ID: <9lbj3n$d59$1@news-central.tiac.net>  6 ...but more importantly, when is the OpenVMS party? :)   (heya Sue - see ya at CETS)    Pedro.    = "Sue Skonetski" <susan.skonetski@compaq.com> wrote in message ) news:iWBc7.3$bB1.2081@news.cpqcorp.net... G > You 're invited to join us in Anaheim,CA on September 9-14 to immerse I > yourself in Compaq-related technology.This year 's symposium covers the H > technical aspects of Compaq 's entire range of enterprise products and> > solutions,including access devices,servers,storage,operatingF > systems,management systems and third-party solutions --including the latestI > news about Compaq 's plans for Alpha and Itanium roadmaps and products.  > G > Featured Speakers include Michael Capellas,Chairman and CEO of Compaq  > J > Computer Corporation,and members of Compaq 's Senior Leadership team,who1 > will be presenting their vision and strategies.  > D > Compaq Enterprise Technical Symposium focuses on Key Technologies: > @ > >Enterprise backup solutions,storage area networking (SAN),and > network-attached storage > H > (NAS),featuring Compaq StorageWorks Tand Compaq S Nworks Tproducts and
 > services > E > >Detailed implementations of Linux,Microsoft Windows NT/2000,Novell  > NetWare,OpenVMS T, >  > and Tru64 TUNIX  > L > >Client computing with Compaq workstations,desktops,portables,and Internet > access devices > E > >Edge of the network applications including technologies,trends and  > strategies for security and  > L > authentication,content serving such as streaming media,replication and web > caching solutions  > G > >Enterprise management solutions,enterprise applications,and industry  > solutions featuring  >  > key Compaq partners. > = > >Applications for e-business,including e-commerce,knowledge  > management,business  > 3 > intelligence,and customer relationship management  > I > >Wireless technologies including Compaq iP Q THandhelds and Blackberry.  > K > >Database solutions,including technologies,architectures and optimization  > with Oracle, > % > Microsoft,and other Compaq partners  >  > >Thin client computing > J > >High Performance Computing (HPC),high availability and clustered server > platforms,featuring  > I > the industry standard ProLiant T,AlphaServer T,and overviews of NonStop 
 > THimalaya T  > I > >IT infrastructures using Compaq DISA and ENSA architectures for highly  > scaleable and  >  > available environments > J > >Airtight solutions for firewalls,data integrity,and enterprise security
 > concerns > K > >Networking strategies and solutions,including wireless,broadband,LAN and  > WAN technologies > L > >Messaging and collaboration solutions that scale from hundreds to tens of > thousands of users > K > >Compaq technology roadmaps and directions,for products ranging from palm  > tops to data >  > center systems > < > Pre-Conference Seminars (for additional fee):September 8-9 > # > Conference Program:September 9-14  > & > Anaheim Convention Center,Anaheim,CA > 9 > $1395.00 (early bird registration,$1495 after August 10  >  > th >  > )includes full conference  > L > access to Compaq Enterprise Technical Symposium 2001 conference events and > 5 > bonus admission to ITUG Summit,co-located with CETS  > D > Visit www.CETS2001.com or and register on the conference portal or >  > call 1-888-639-2990  > 8 > To learn more about this premier educational event and > : > to reserve your place visit www.CETS2001.co or call your >  > Compaq Representative! >  > Featured Speakers  >  > Deep Technical Content >  > Conference Dates > 
 > Location >  > Cost >  > Registration Info  >  >  >    ------------------------------    Date: 14 Aug 2001 04:59:09 -07006 From: andrew.rycroft@intrinsitech.com (Andrew Rycroft)8 Subject: Cloning and snapshotting on an HSG from OpenVMS= Message-ID: <58ba0101.0108140359.2b50b3c1@posting.google.com>    Hi,   C Is it possible to write an OpenVMS command proceudre to utilise the E cloning, and snapshotting features of the ACS software with the RA/MA  Raid solutions ?   Thanks Andrew   ------------------------------  % Date: Tue, 14 Aug 2001 18:46:16 +0200  From: zessin@decus.de < Subject: RE: Cloning and snapshotting on an HSG from OpenVMS* Message-ID: <00A00879.DD1EB419.5@decus.de>   ndrew Rycroft wrote:E > Is it possible to write an OpenVMS command proceudre to utilise the G > cloning, and snapshotting features of the ACS software with the RA/MA  > Raid solutions ?  F You need to send commands to the HSG. Either via the serial console ofG a HSG controller or through the SANworks command scripter via an agent:   4 $ mcr cmdscript -h ds20eu -s hsg_i "show mirrorsets"" STEAM Agent, Version 2.3, Build 77    E Name          Storageset                     Uses             Used by N ------------------------------------------------------------------------------  @ M1            mirrorset                      DISK10000        S16                                              DISK20000  @ M3            mirrorset                      DISK10800        S16                                              DISK40000  @ M9            mirrorset                      DISK60200        D9  A T64M1         mirrorset                      DISK10100        D65 6                                              DISK20100  @ VMS_M1        mirrorset                      DISK20200        D36                                              DISK50200 I-HSG-B> $   3 It's possible to go directly through a device, too:   ( $ mcr cmdscript -f $1$dga103: "show d65"  E     LUN                                      Uses             Used by N ------------------------------------------------------------------------------  2   D65                                        T64M1<         LUN ID:      6000-1FE1-0013-7B90-0009-1180-0071-0020         IDENTIFIER = 165         Switches: B           RUN                    NOWRITE_PROTECT        READ_CACHE0           READAHEAD_CACHE        WRITEBACK_CACHE+           MAXIMUM_CACHED_TRANSFER_SIZE = 32          Access: 4           DS20EO_A1, DS20EO_A2, DS20EO_B1, DS20EO_B2         State:#           ONLINE to this controller            Not reserved           NOPREFERRED_PATH)         Size:             35556389 blocks -         Geometry (C/H/S): ( 7000 / 20 / 254 )  I-HSG-A> $   A There are more features (complete scripts & macro expansion), but  I think you get the idea. See:B http://www.compaq.com/products/sanworks/commandscripter/index.html   --  
 Uwe Zessin   ------------------------------  % Date: Tue, 14 Aug 2001 13:00:24 -0400 " From: "Hal Kuff" <kuff@tessco.com>< Subject: Re: Cloning and snapshotting on an HSG from OpenVMSO Message-ID: <19605219AC1DE032.FD8A07134BDC53C8.0930665C7B4A10D9@lp.airnews.net>   H     There is a storageworks command scripter s/w package... i think it's5 $750... they make it easy on NT and Unix of course...   C "Andrew Rycroft" <andrew.rycroft@intrinsitech.com> wrote in message 7 news:58ba0101.0108140359.2b50b3c1@posting.google.com...  > Hi,  > E > Is it possible to write an OpenVMS command proceudre to utilise the G > cloning, and snapshotting features of the ACS software with the RA/MA  > Raid solutions ? >  > Thanks > Andrew   ------------------------------  % Date: Tue, 14 Aug 2001 11:54:37 -0500 + From: Phil Mendelsohn <mend0070@tc.umn.edu> ) Subject: DECnet-Plus on an alternate disk G Message-ID: <Pine.SOL.4.20.0108141147440.7736-100000@garnet.tc.umn.edu>    Hi,   I I'm learning some ropes of VMS system management.  I have a VAXserver3100 I with a small (RZ23) system disk, but a 2.0GB disk also.  I got Polycenter G to install DECnet Plus on the big drive (DISK$POOL) but want to know if H there are logical names that need to be defined to make sure things find it.   J Is it as easy as adding VMS$COMMON=DISK$POOL:[VMS$COMMON.] to the existing VMS$COMMON logical?   J I am *not* trying to avoid manual reading -- I'm right in the midst of it,H but in this instance I have to be goal oriented:  I need DECnet up, so ID can put TCP/IP up, so I can read the manuals that tell me how to put DECnet up (sorta.)   Thanks for any advise,   Phil Mendelsohn    --  & "Remember, Rome didn't fall in a day."   ------------------------------    Date: 14 Aug 2001 06:19:38 -0700' From: steve.esson@esa.int (hieronymous):" Subject: Does MOD_PERL work on VMS= Message-ID: <fe9697fd.0108140519.233d25be@posting.google.com>1  4 Has anybody been successful in getting this to work?   ------------------------------  % Date: Tue, 14 Aug 2001 15:12:57 +0200n* From: Mike Rechtman <rechtman@tzora.co.il>" Subject: F.Y.I OpenVMS FAQ address+ Message-ID: <3B7923D9.E7A919A1@tzora.co.il>   = Please note that access to the HTML version has changed from A& Decusserve to Encompasserve and is now  + http://Eisner.Encompasserve.org/vms/faq.htme   ~Mikee -- aE ---------------------------------------------------------------------qE Usual disclaimer: All opinions are mine alone, perhaps not even that.k? Mike Rechtman                            *rechtman@tzora.co.il*tG Kibbutz Tzor'a.                          Voice (home):(972)-2-9908337  sB   "20% of a job takes 80% of the time, the rest takes another 80%"E ---------------------------------------------------------------------d* ------ 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+d DI+ D-- G e++ h--- r+++ y+++@e* ---------- END GEEK CODE BLOCK  ----------   ------------------------------  % Date: Tue, 14 Aug 2001 08:47:54 +0200 - From: "Roland Hauk" <roland.hauk@indramat.de>iQ Subject: Re: Free VT terminal emulators supporting DRCS downloadable characters ? - Message-ID: <9lahce$5b91@sunny.mannesmann.de>v  / Try this unsupported freeware from PATHWORKS CDe  " Compaq PATHWORKS 32 VT320 V7.1.0032 http://download.uni-hd.de/ftp/incoming/vt320_7.exe0 ftp://ftp.uni-heidelberg.de/incoming/vt320_7.exe     Hauk   ------------------------------  % Date: Tue, 14 Aug 2001 10:58:50 -0400C2 From: rdeininger@mindspring.com (Robert Deininger)< Subject: Re: HELP!  error adding entries to quota file?!?!?!L Message-ID: <rdeininger-1408011058510001@user-2ive77p.dialup.mindspring.com>  ? In article <3B78395A.EE4FA114@wcu.edu>, pjohnson@wcu.edu wrote:w  D > We have a drive that we have specifically for user accounts.  It'sA gotten full so I tried (for my first time) to create a volume setmG > for it & another.  It appeared to go off w/out a hitch but I wouldn'td< know - not sure how dir, show dev, etc output is supposed to > look for a volume set.   > I > Anyways, we're still having the problem of adding quota for new users. r# From the add quota command, we get:s > 1 > %DISKQ-E-ADDERR, failed to add quota file entryH7 > %SYSTEM-E-DEVICEFULL, device full; allocation failures > , > but when I 'sho dev' on that device, i get > alf_pj>show dev dkb1 > H > Device                  Device           Error    Volume         Free 	 Trans MnteH >  Name                   Status           Count     Label        Blocks	 Count Cnt A > $1$DKB1:         (ALF)  Mounted              0  WSI1           i 550608     1   3? > $1$DKB3:         (ALF)  Mounted              0  WSI3           16205840     1   3 > - > does anyone have any ideas on how to help??r  J You can try SET VOLUME/REBUILD=FORCE in case there is some free space tied up in a dead cache.u  J It appears the quota file may need to be contiguous.  If your disk is veryI fragmented, the system may not be able to find contiguous space to extendiI the file.  If that is the problem, you'll probably have to defragment theb@ disk pretty soon, even if you wiggle out of the current problem.  G If your license/media situation allows it, you should be using Compaq'saJ defragmenter, Disk File Optimizer, or some other method to keep your disks reasonably defragmented.   HELP/MESSAGE DEVICEFULL.   gives some useful information.    2 > please reply via email as well as the newsgroup.   --   Robert Deininger rdeininger@mindspring.comr   ------------------------------  % Date: Tue, 14 Aug 2001 12:22:25 -0400-; From: "Brian Tillman" <tillman_brian@notnoone.notnohow.com>c< Subject: Re: HELP!  error adding entries to quota file?!?!?!$ Message-ID: <3b79509f$1@news.si.com>  G >Anyways, we're still having the problem of adding quota for new users.f# From the add quota command, we get:: >D0 >%DISKQ-E-ADDERR, failed to add quota file entry6 >%SYSTEM-E-DEVICEFULL, device full; allocation failure  H While your disk may have free space on it, it is very fragmented and theK quota file cannot be expanded.  The quota file must be contiguous and therei= simply isn't enough contiguous space on your disk to hold it.r --A Brian Tillman                   Internet: tillman_brian at si.com A Smiths Aerospace                          tillman at swdev.si.comh= 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: Tue, 14 Aug 2001 17:06:54 +0200 (CEST): From: "Gotfryd Smolik, VMS lists" <gotfryd@stanpol.com.pl>) Subject: Re: Help! Boot Block InformationfJ Message-ID: <Pine.LNX.4.21.0108141651580.18272-100000@irys.stanpol.com.pl>  , On Sun, 12 Aug 2001, Robert Deininger wrote:  M >+In article <tne1bnqgqf2nf6@corp.supernews.com>, sword7@speakeasy.org wrote:i [...]-M >+> I have two samples (first three longwords) on my OpenVMS Installation CD   [...].# >+> On the OpenVMS Installation CD:g [...]tK >+I don't think CDs are ODS-2.  They are ODS-3 or -4, I think, which is why # >+the new VMS file system is ODS-5.-  ;  My .02$$: you say about ISO9660/High Siera format, right ?   7  The "vms image" CD-ROM is definitely ODS-2 :), nothingh5 prevents write CD block-by-block with system specific 5 format. The difference is: ISO9600 can be read in any ; "standarised" system, even Windows (also if using PARALLEL t9 directory info in romeo or juliet format) can read ISO :)>  5  But - differrently than PC-BIOS, where boots ISO960003 compatible ElTorito extension - VMS uses the natived ODS-2 to boot ! :)  ?  Fortunatelly (och, someone must somethink drink in High Sierrae8 for the reason ;)) the formats are uses differrent areas: for "data description" and *is* possible get a CD-ROM with both format on it...    Regards - Gotfryd   --  E =====================================================================rF $ ON F$ERROR("LANGUAGE","ENGLISH","IN_MESSAGE").GT.F$ERROR("NORMAL") - 		THEN EXCUSE/OBJECT=MEh. $!                        GS@stanpol.zabrze.plE =====================================================================e   ------------------------------  % Date: Tue, 14 Aug 2001 17:30:14 +0100B4 From: John Laird <john@laird-towers.freeserve.co.uk>) Subject: Re: Help! Boot Block Informations8 Message-ID: <m1kint0t4940p24gsrb9t7tcfuoc2fdhpm@4ax.com>  F On Tue, 14 Aug 2001 14:03:23 +0100, Nic Clews <sendspamhere@127.0.0.1> wrote:   >John Laird wrote: >> tI >> On Mon, 13 Aug 2001 11:43:11 +0100, Nic Clews <sendspamhere@127.0.0.1>a	 >> wrote:/ >> >> With respect, what rubbish !s >t >Thanks for the correction!e  & Hope you didn't think it too harsh :-)  K >> The *second* longword is FC8D0006, not the third as you suggest, but the F >> reason this is not the expected value of 0006FC8D is because *it isH >> defined to be word-swapped on-disk*.  This will almost certainly dateK >> back to pre-Vax days.  Other longword items in ODS-2 format are just theiI >> same - block-counts in file headers come to mind.  For fun, see if the0K >> various non-IEEE floating point layouts make more sense word-swapped tooo >> ;-) > I >The word swap on disk did baffle me, can you explain more about it, likeu >why?a  H 99.9% certain it will be related to PDP-11 compatibility.  16-bit words,E so longwords involve 2 moves, but beggar me if I know why the natural H low part is in fact the higher addressed word.  Someone will shed light,	 no doubt.y  F >(I should add I'm not very familiar with numeric data format storage, >e.g. of IEEE and the like)m  = The 4-byte native Vax floating point format is also logically F word-swapped (that is, the exponent and sign bit apparently sit in theA middle, breaking the mantissa in two).  Again, PDP compatibility.b  9 >> Tim may well not have access to a VMS box, by the way.w > C >Good point, it's partly why I posted the DUMP, but I read it wrong  >myself. Didn't help did it :-)i  H Oh, I dunno.  It made me run WRITEBOOT on my hobbyist system disk, whichF was probably not a bad thing...  (If Tim is listening, many MicrovaxesD and Vaxstations had VMB.EXE in console rom, so you could have a fair6 amount of gibberish in the boot block and still boot.)     	John  -- c
 John Laird Yezerski Roper Ltd   ------------------------------    Date: 14 Aug 2001 08:26:15 -0700, From: dframeli@aus.telusa.com (Dale Frameli)& Subject: How to add a network printer?= Message-ID: <de844d64.0108140726.6bd19a9d@posting.google.com>   E I have a DEC3000 that's runing Alpha OpenVMS v1.5-1H1.  I sucessfullyoB added the DEC3000 to our company network and would now like to addE access to several network printers.  I was able create a print queue,hF but wasn't able to "start" it.  I used the following command to create$ a print queue for our HP LaserJet 5:  % >INITIALIZE/QUEUE/ON=172.17.40.75:PR1N >Queue? my_gc_queueS  F   I have documents sitting in the print queue, but their not printing,F their pending.  The status of the print queue shows "stopped".  At one* point, I saw an invalid device name error.  A   Any idea how I can enable the queue?  Any idea what the invalidn device error was referring to?  5   Please respond directly to: dframeli@aus.telusa.comd   Thanks,t Dale   ------------------------------    Date: 14 Aug 2001 11:49:51 -0500 From: briggs@encompasserve.org* Subject: Re: How to add a network printer?3 Message-ID: <VpKCfAqWTvB7@eisner.encompasserve.org>r  l In article <de844d64.0108140726.6bd19a9d@posting.google.com>, dframeli@aus.telusa.com (Dale Frameli) writes:G > I have a DEC3000 that's runing Alpha OpenVMS v1.5-1H1.  I sucessfullyiD > added the DEC3000 to our company network and would now like to addG > access to several network printers.  I was able create a print queue,oH > but wasn't able to "start" it.  I used the following command to create& > a print queue for our HP LaserJet 5: > & >>INITIALIZE/QUEUE/ON=172.17.40.75:PR1 >>Queue? my_gc_queue > H >   I have documents sitting in the print queue, but their not printing,H > their pending.  The status of the print queue shows "stopped".  At one, > point, I saw an invalid device name error. > C >   Any idea how I can enable the queue?  Any idea what the invalidn  > device error was referring to? > B The problem is that "172.17.40.75:PR1" is not the name of a device on the local VMS node.  F There is no support built into VMS to enable you to do remote printingC on a non-VMS print server.  (Well, unless you count LATSYM -- whichn( might actually be a useful possibility).  G But there _is_ support built into the TCP/IP package that you are usingt on VMS.   I Check out that documentation.  Details of setting up a print queue using,bE for instance, the lpr/lpd protocol will vary with package and releasei level.  7 >   Please respond directly to: dframeli@aus.telusa.com    Ask here, get answers here.    	John Briggs   ------------------------------  % Date: Tue, 14 Aug 2001 19:50:56 +0200n* From: Mike Rechtman <rechtman@tzora.co.il>* Subject: Re: How to add a network printer?+ Message-ID: <3B796500.6F3C258C@tzora.co.il>o  4 This is from home, and my memory is not what it was-   If yu are running UCX:" Try  $ RUN SYS$SYSTEM:UCX$LPRSETUP   On multinet: try MULTINET CONFIG/PRINTERc  A In both cases the printer host is the printer's IP or host-name,  B (With HP printers the remote printer queue is "TEXT" - no quotes.)  
 Good luck,   Mike   Dale Frameli wrote:  > G > I have a DEC3000 that's runing Alpha OpenVMS v1.5-1H1.  I sucessfully D > added the DEC3000 to our company network and would now like to addG > access to several network printers.  I was able create a print queue,5H > but wasn't able to "start" it.  I used the following command to create& > a print queue for our HP LaserJet 5: > ' > >INITIALIZE/QUEUE/ON=172.17.40.75:PR1a > >Queue? my_gc_queued > H >   I have documents sitting in the print queue, but their not printing,H > their pending.  The status of the print queue shows "stopped".  At one, > point, I saw an invalid device name error. > C >   Any idea how I can enable the queue?  Any idea what the invalido  > device error was referring to? > 7 >   Please respond directly to: dframeli@aus.telusa.comr > 	 > Thanks,o > Dale   --  E ---------------------------------------------------------------------hE Usual disclaimer: All opinions are mine alone, perhaps not even that.c? Mike Rechtman                            *rechtman@tzora.co.il*gG Kibbutz Tzor'a.                          Voice (home):(972)-2-9908337   B   "20% of a job takes 80% of the time, the rest takes another 80%"E --------------------------------------------------------------------- * ------ 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+3 DI+ D-- G e++ h--- r+++ y+++@ * ---------- END GEEK CODE BLOCK  ----------   ------------------------------    Date: 14 Aug 2001 10:02:06 +0200G From: Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de> F Subject: Re: I just have to post this - and apoligse later Alpha/IntelH Message-ID: <y4u1zb83y9.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>  / JF Mezei <jfmezei.spamnot@videotron.ca> writes:   * > But isn't EV7 sort of a waste of money ?   No.g  I > The effort put in for lockstep is wasted since Tandem won't run on EV7."  M I wouldn't say wasted, but indeed there currently is no customer in sight for- this particular feature.  O > And the current customers of wildfires won't really be investing in EV7 since , > it isn't compatible with their mainframes.  K Any customer who expected that "just a CPU board swap" would be involved in D upgrading a system from EV6x to EV7 got what he paid for. See below.  O > So who is left to buy EV7s at a time when competing companies will already beI@ > on what, according to Compaq, will be the chip of the future ?  D I don't know. But that's a market question, no a technical question.  4 The EV7, as designed, has two unique selling points:  K - the on-chip inter-processor links, with the necessary control logic to do5"   directory-based coherent memory;  K - the on-chip memory control, driving a large number of Rambus channels and (   allowing a large number of open pages.  H This allows you to build a glueless SMP system - just add memory and I/OF interface chips to the processors. From the point of view of a systemsH architect, the EV7 is a T9000 on steroids, with the support of a siliconI design group that is one of the best in the industry. There is absolutelye$ nothing in sight that is comparable.  L In the context of the current GS systems, EV7 does away with the switches onJ the QBBs, and has a very different memory architecture. Of course, all theI hardware work supportin hot-swap, and all the software work to support a  " large SMP system are still useful.  K In this scenario, lock-stepping is merely a small wart or a small polishingeL of a rough corner (depending on your point of view) that was added later on.   	Jan   ------------------------------    Date: 14 Aug 2001 10:04:18 +0200G From: Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de>sF Subject: Re: I just have to post this - and apoligse later Alpha/IntelH Message-ID: <y4r8uf83ul.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>  / JF Mezei <jfmezei.spamnot@videotron.ca> writes:(  J > Compaq depends on Microsoft and Intel for survival. The later pays a big- > amount of money to help Compaq's marketing.   H In the grand scheme of things, I cannot believe the some-hundred millionI dollars of marketing support is really what is driving a tens-of-billionst company.   	Jan   ------------------------------    Date: 14 Aug 2001 10:07:55 +0200G From: Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de>eF Subject: Re: I just have to post this - and apoligse later Alpha/IntelH Message-ID: <y4ofpj83ok.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>  4 rdeininger@mindspring.com (Robert Deininger) writes:  E > When Wildfire was launched, how many specifics of EV7 had been made-I > public?  I suspect anything they published would have had "preliminary"  > written all over it.  M There were public presentations on EV7, for instance at Microprocessor Forum,gK as early as 1999 (at least). And the title and abstract did not contain any0
 subjunctives.0  E > EV8 was in the "preliminary" state right up until it was cancelled.Q  I Again, architectural details wof EV8 were presented at least in 2000, andc probably before that.    	Jan   ------------------------------  % Date: Tue, 14 Aug 2001 07:34:09 -0700s+ From: "Barry Treahy, Jr." <Treahy@mmaz.com>-F Subject: Re: I just have to post this - and apoligse later Alpha/Intel( Message-ID: <3B7936E1.F213B4F1@mmaz.com>   Jan Vorbrueggen wrote:  1 > JF Mezei <jfmezei.spamnot@videotron.ca> writes:a >.L > > Compaq depends on Microsoft and Intel for survival. The later pays a big/ > > amount of money to help Compaq's marketing.  >eJ > In the grand scheme of things, I cannot believe the some-hundred millionK > dollars of marketing support is really what is driving a tens-of-billionsa
 > company. >W  N It would depend on how short-sighted the leadership of the company were.  MostM corporate US top management is more focused on stock market valuation to keepeM share-holders happy rather than demonstrating long term visionary leadership.eM I suspect part of what contributes to this is the 'day-trading' which is moretN akin to gambling than investing, but for those true investors in a company, ifM they knew that a little profit may need to be sacrificed up front to catapultaL the company into the next S-Wave growth curve, I suspect that they could andM would accept that. For the later to work, the leadership would need to convey1< vision, determination and leadership which Compaq has not...   Just my humble 2 cents...o   Barrye     --  ? Barry Treahy, Jr  *  Midwest Microwave  *  Vice President & CIOi  A E-mail: Treahy@mmaz.com * Phone: 480/314-1320 * FAX: 480/661-7028>   ------------------------------  % Date: Fri, 10 Aug 2001 21:27:57 -0400o2 From: rdeininger@mindspring.com (Robert Deininger)F Subject: Re: I just have to post this - and apoligse later Alpha/IntelL Message-ID: <rdeininger-1008012127580001@user-2ivech6.dialup.mindspring.com>  4 In article <3B745DE8.BF0FF38@videotron.ca>, JF Mezei% <jfmezei.spamnot@videotron.ca> wrote:b   > Robert Deininger wrote:sN > > And those CPU upgrades have since been announced, at least the first batch
 > > of them. n > H > > That has been well-known for quite some time.  The current GS-series6 > > systems are not deemed to be a good match for EV7. > M > I am very disapointed in this. Capellas had made a point to say a couple ofrN > times that if you boght a wildfore now (back during the launch) you would beK > able to add CPU blocks of newer generations of CPUs preserving your multi  > million dollar investment. > M > But now, it seems that this was only applicable to the same generation with  > just a newer faster chip.o  H EV68 is arguably a newer generation.  But it's a silly question anyway. B Unless the so-called commitments promised particular architecturalF features, or specific performance levels, then Compaq could meet these. "commitments" by relabeling the EV68 as a EV7.  C When Wildfire was launched, how many specifics of EV7 had been madeaG public?  I suspect anything they published would have had "preliminary"e written all over it.  F EV8 was in the "preliminary" state right up until it was cancelled.  IJ don't understand how people can talk about "commitments" in the context ofH such incompletely-specified future products.  I still see people whiningJ that Compaq broke a "commitment" to build EV9 and EV10.  Those were almostJ pure vaporware.  I saw a roadmap with EV12 on it.  Did I pay ANY attention to it?  Heck no!  M > I assume that from a legal point of view, Compaq delivered what it claimed.c  I From a legal point of view, "product announcements" and "roadmaps" aren't$ the least bit binding.   F > Perhaps Compaq would be better off continuing to improve EV6 line byH > increasing clock speed which would allow the wildfires to be upgraded.  P I haven't read anywhere that an EV69, or even faster EV68s, have been ruled out.   -- e Robert Deininger rdeininger@mindspring.comt   ------------------------------  % Date: Tue, 14 Aug 2001 18:14:14 +0200h, From: Theo Jakobus <Theo.Jakobus@iaf.fhg.de>: Subject: Re: Installing V7.3 on Personal Workstation 500au) Message-ID: <3B794E56.3000100@iaf.fhg.de>A   Bart Zorn wrote:N > It is not entirely true that you need a SCSI CD ROM to boot OpenVMS on a PWSL > 500au. However, there are many variants of the 500au and some do boot fromJ > the IDE CD (dqa0 or dqb0) and some don't. Maybe someone who really knows- > about the PWS could explain something more!1 > +  From "Version 7.3 Release Notes page 4-5":SP If you are using the Compaq Personal Workstation 433au, 500au, and 600au series O systems, you can boot OpenVMS Version 7.3 from an IDE CD-ROM if the controller  M chip is a Cypress PCI Peripheral Controller. You cannot boot OpenVMS with an nM Intel Saturn I/O (SIO) 82378 chip in your configuration. You must use a SCSI h( CD-ROM if the Intel SIO chip is present.P To determine which IDE chip you have in your configuration, enter the following ' SRM console command: SHOW CONFIGURATIONw  P In my 500au is a Toshiba CD-ROM and I'm lucky there is the Cypress chip. So I'm  able to boot the CD.K I have added an Acer 910 CD-ROM to the IDE channel so I'm able to have the sE "Online Documentation Library" which consists of 2 CDs really online.iN I've added an IBM 34330W (4.2GB) hard disk to the internal SCSI channel which ; doubles the disk capacity (originally there is a RZ2CC-KA).e       Regards, -- d  ; ***********************************************************r; *                                                         *F; *  Theo Jakobus                                           *e; *  Fraunhofer-Institut fuer Angewandte Festkoerperphysik  *o; *  Tullastr. 72                                           *h; *  D-79108 Freiburg                                       *=; *  Germany                                                *N; *  Phone:   +49-(0)761-5159-325                           *L; *  FAX :    +49-(0)761-5159-200                           *s; *  e-mail:  Theo.Jakobus@iaf.fhg.de                       *=; *  http://www.iaf.fhg.de                                  * ; *                                                         *o; ***********************************************************c   ------------------------------   Date: 14 Aug 2001 16:21:37 GMT1 From: bill@triangle.cs.uofs.edu (Bill Gunshannon)w. Subject: Re: Intel running out of hard assets?, Message-ID: <9lbj6h$2sge$4@info.cs.uofs.edu>  G In article <Pine.OSF.4.21.0108131319420.24638-100000@athena.csdco.com>,c%  John Nebel <nebel@csdco.com> writes:  |> cL |> I'd speculate they were more desperate about Alpha than has been admitted6 |> and that Q is in better financial shape than Intel. |>    F Ummmmm.  If Compaq has hitched their wagon to Intel's star and Intel'sC star is a supernova now in the collapsing stage, how is Compaq in a  better position??t   bill   -- eJ 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>       ------------------------------  % Date: Tue, 14 Aug 2001 13:31:16 -0400d- From: JF Mezei <jfmezei.spamnot@videotron.ca>n. Subject: Re: Intel running out of hard assets?, Message-ID: <3B79605D.BB6DBFD2@videotron.ca>   Bill Gunshannon wrote:H > Ummmmm.  If Compaq has hitched their wagon to Intel's star and Intel'sE > star is a supernova now in the collapsing stage, how is Compaq in ay > better position??g    N Nobody's ever been fired for choosing Intel/Microsoft. So Winkler and Capellas	 are safe.i   ------------------------------    Date: 13 Aug 2001 23:07:12 -07009 From: lzoedv@cretschmar-logistik.de (M.Eismann&W.Richard)t' Subject: Re: Linker-Warnings in VMS 7.3y= Message-ID: <6d280ea8.0108132207.36a41b06@posting.google.com>d  [ John Reagan <john.reagan@compaq.com> wrote in message news:<3B77E9AA.6090001@compaq.com>...b > M.Eismann&W.Richard wrote: > >  > > This is amazing too:? > > The linker seems to find the message in some circumstances: * > > %LINK-W-NOMSG, Message number 0064A128* > > %LINK-W-NOMSG, Message number 0064A130T > > %LINK-W-ENTIDMTCH, PAS$ENVIRONMENT_TIME ident of 15-APR-1998 18:46:59 for entity > >  SBR_INTERFACEL > >         in module NKG_GET file NKG_RUNTIME_DEVICE:[LIB]NKG_LIBRARY.OLB;28 > >         does not match ident of  9-JUL-2001 12:51:518 > >         in module BUCHER file LZO_LINK_LIB_DEVICE:[L7 > > I 'd never seen this before! Maybe I was blind ....k > >  > K > That is even stranger.  The code in the linker for printing IDC warnings i > essentially looks like:  > % > IF size of message is less than 250d > THENG >     SIGNAL single ENTIDMTCH message that contains all the information0 > ELSEN >     SIGNAL 4 different messages each containing a portion of the information > H > You sure you only got 2 of the NOMSG messages and not 4?  I don't see  > how that is possible.a  > Oh no! That's only a (little) snapshot of maybe hundreds(!) of2 NOMSG-messages. But sometimes the linker finds the PAS$ENVIRONMENT_TIME-message:d? I wrote the complete linker-output to a file. The file contains-- (complete of 5874 lines!) following messages:1  B LZOA09:[000000.LZOSRC.LE]> search/stat/noout a.txt "Message number	 0064A120"r  E Files searched:                 1       Buffered I/O count:         5eE Records searched:            5874       Direct I/O count:          34.E Characters searched:       249272       Page faults:               30V< Records matched:             1150       Elapsed CPU time:  0 00:00:00.07d< Lines printed:                  0       Elapsed time:      0 00:00:00.07r LZOA09:[000000.LZOSRC.LE]>  B LZOA09:[000000.LZOSRC.LE]> search/stat/noout a.txt "Message number	 0064A128"u  E Files searched:                 1       Buffered I/O count:         5uE Records searched:            5874       Direct I/O count:          34bE Characters searched:       249272       Page faults:               27 < Records matched:             2300       Elapsed CPU time:  0 00:00:00.07 < Lines printed:                  0       Elapsed time:      0 00:00:00.06i  B LZOA09:[000000.LZOSRC.LE]> search/stat/noout a.txt "Message number	 0064A130"   E Files searched:                 1       Buffered I/O count:         5oE Records searched:            5874       Direct I/O count:          34WE Characters searched:       249272       Page faults:               24i< Records matched:             2300       Elapsed CPU time:  0 00:00:00.07r< Lines printed:                  0       Elapsed time:      0 00:00:00.07a  @ LZOA09:[000000.LZOSRC.LE]> search/stat/noout a.txt "pas$environ"  E Files searched:                 1       Buffered I/O count:         5eE Records searched:            5874       Direct I/O count:          34-E Characters searched:       249272       Page faults:               32 < Records matched:              120       Elapsed CPU time:  0 00:00:00.06r< Lines printed:                  0       Elapsed time:      0 00:00:00.06m   ...amazing!y  G > Also, I'm a little surprised by the truncated ENTIDMTCH message.  It PJ > seems that the new code to compute the length doesn't work all the time 4 > either.  Guy will have to track this down as well. > 
 > John Reagano > Compaq Pascal Project Leader   ------------------------------  % Date: Tue, 14 Aug 2001 11:25:33 -04000* From: John Reagan <john.reagan@compaq.com>' Subject: Re: Linker-Warnings in VMS 7.3c) Message-ID: <3B7942ED.6010201@compaq.com>    M.Eismann&W.Richard wrote: > @ > Oh no! That's only a (little) snapshot of maybe hundreds(!) of4 > NOMSG-messages. But sometimes the linker finds the > PAS$ENVIRONMENT_TIME-message:   I Oh, I see.  BTW, it isn't the case that the linker sometimes "finds" the  D message and other times does not.  There are 2 sets of messages the G linker is trying to print.  One where the message is 250 chars or less  G (the old message that sometimes truncates) and other new message where aB there is more than 250 chars to print.  It is that case where the D message file appears to be missing.  It is normal for the linker to C sometimes print the single message and in other times to print the - "group of 4" messages.  F And at this point, I can't tell you if the messages are valid or not. F  From looking at the code in the linker, the actual comparison of the C IDC records was not modified.  If the linker is printing a message 85 (perhaps badly), then I'd guess the message is valid.   H When you did the same build on your previous V7.2-based system, you say % you didn't get any of these messages?(   John Reagan- Compaq Pascal Project Leader   ------------------------------  % Date: Tue, 14 Aug 2001 14:09:14 +0100-% From: Alan Greig <a.greig@virgin.net>B@ Subject: Re: OT: Citroen C5 Re: AMD and Samsung could save Alpha8 Message-ID: <n68ints7n3f8qs0mpq6grvhl7tadi0p5vd@4ax.com>  F On Tue, 14 Aug 2001 12:53:51 +0100, Nic Clews <sendspamhere@127.0.0.1> wrote:   >JF Mezei wrote: >> lO >> You forget that Alpha might have other uses, such as Nintendo game boxes etcMN >> etc. Also, didn't Ford at one point embed alphas in cars ? (or was that the >> powerpc chip ?) >> h >fA >The latest round of Citroen C5 ads in the UK claim, that for the C >'estate' version of the C5, all 19 computers "have been rebooted".   D Just AdWank that... I certainly don't get a pleasant feeling about a> car advertised as having 19 computers which have been rebooted  D I used to own a Fiat Tipo with electronic display. Developed a faultD at one point where it would randomly switch to km/hr instead of mph.! 110 Now am I speeding or not? :-)o  H >This perhaps makes more sense, if you know in the UK we call the trunk, >a boot.  ? I wondered if this was the 'joke' but surely it doesn't have 19 @ computers in the boot? To reach 19 computers they must surely beF counting chips and I wouldn't like to thing all of this is in the boot with the engine at the front.t -- Alan   ------------------------------  % Date: Tue, 14 Aug 2001 12:06:49 -0400c- From: JF Mezei <jfmezei.spamnot@videotron.ca>a@ Subject: Re: OT: Citroen C5 Re: AMD and Samsung could save Alpha, Message-ID: <3B794C98.2CCDB270@videotron.ca>   Alan Greig wrote:IJ > >This perhaps makes more sense, if you know in the UK we call the trunk,
 > >a boot. > A > I wondered if this was the 'joke' but surely it doesn't have 19o > computers in the boot? i  M No ! Heck, I am not in the UK and I understood it.... The car was rebooted...t its boot was redesigned !S   ------------------------------    Date: 14 Aug 2001 13:04:57 +0200G From: Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de>i Subject: Re: Press ReleaseH Message-ID: <y4hevaj412.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>  ( robyoung@my-deja.com (Rob Young) writes:  : >         1)  Value.  Cheaper than high-end servers today.  N The only relevant difference is in the processor. Current IA64 processors costH way more than current Alpha processors. Whether the future brings enoughJ volume to IA64 to drive costs down seems doubtful, especially with Intel's< emphasis on the "server" market (whatever that is) for IA64.  ? >         2)  Shared components.   Racks.  Power Supplies, etc.mB >         3)  Purchasing decisions.  Simple across the board here.4 >         4)  Support.  No specializations required.  , Applies equally well to Alpha-based systems.   	Jan   ------------------------------  % Date: Tue, 14 Aug 2001 12:01:30 -0400p- From: JF Mezei <jfmezei.spamnot@videotron.ca>n Subject: Re: Press Release, Message-ID: <3B794B59.C5A1B7EF@videotron.ca>  D re: those military VMS systems replacing old DG systems in aircraft.  K Would this deal which made the press have been in the works/negotiated wellAN before the June 25 murder of Alpha and announced only now that the software isH operational etc, or would it have just been negotiated with the military* having full knowledge that Alpha is dead ?   ------------------------------    Date: 14 Aug 2001 00:52:02 -0700, From: JanWermusch@hotmail.com (Jan Wermusch)7 Subject: Re: Pseudo Terminals to emulate LAT Terminals?a= Message-ID: <c8f6eefa.0108132352.582d1510@posting.google.com>t  ` JF Mezei <jfmezei.spamnot@videotron.ca> wrote in message news:<3B787C93.5924693@videotron.ca>... > M > If that is your case, you can usually get around by having the users log on G > with a common, captive VMS username and then execute the same command-P > procedure that would have been executed by that master process, at which pointI > the application wouldn't really care about the device type since you'rel: > bypassing the device control done by the master process.    F Hmmm... I think I did not express myself as exact as necessary (one of my personal problems <g>).  B The peripheral devices currently connected to terminal servers are= automatic devices sending material orders to the AXP host and E expecting appropriate answers. Now those devices shall be replaced bye= PCs, not connected to terminal servers, but using TCP/IP (theo2 application actually uses UDP echoing mechanisms).B At the AXP side, the 3rd party process for processing the materialC order request talks to LTA devices that have been configured duringa LAT startup.  , What I am now trying to do is the following:  D 0. Because I cannot play around with the 3rd party app (critical), I8 need to test it on another machine with other processes.E 1. I found a little app, say "LTAAPP", that uses LTA devices the same C way as the 3rd party app does (hopefully). At least it talks to LTAa devices bi-directional.tA 2. I wrote a little TCP program "TCPAPP" listening on port x, say  12345, and let it run.E 3. I now want to create a TNA1234 using reverse telnet, connecting to  port 12345 on the same host.< 4. Now DEFINE/SYS/EXEC LTA5678 TNA1234: (as Nic Clews wrote)> 5. Let the LTAAPP run and send something to the LTA1234 device5 6. Hope that TCPAPP receives the data sent in step 5.-  E Does this make any sense? Please do not kill me if that is too stupidrA for the discussion - the only somewhat deeper experience on VMS I F currently have is in writing UCX based apps for UDP and TCP in FORTRANB 77. Up to now I used LAT only from the customer's perspective when+ configuring devices for other applications.d   Regards  Janb   ------------------------------  % Date: Tue, 14 Aug 2001 09:19:19 +0100a* From: Andrew Robinson <arobinson@hspg.com>7 Subject: RE: Pseudo Terminals to emulate LAT Terminals?iM Message-ID: <CDA4BAD1E10ED41181AC00508B6051D3C3E333@grumpy.internal.hspg.com>V  L We have a very similar set-up on one of our legacy systems - In that we haveI a number of terminals, printers & I/O devices connected to a VAX 3100 viaoG LAT directly. It was done by configuring LTA ports and then using thoseiD ports directly within a pascal program to set-up a dedicated device.J I suspect the original plan was a way of getting round licenses as we have> 22 terminals with only a single interactive VMS user license. G We tried using a PC & Reflections LAT & a few other types, but the maincJ killer was that the VMS application required and expected 24x365 access toJ the terminals / printers etc, & PC's weren't and aren't reliable enough toK work 24x365 (and that was after you had spent a day stopping the PC's goingtG to sleep). After a few weeks of outages, we gave up and put a couple ofiG dedicated terminal servers back just for this system, which has behaved  perfectly ever since. I I know this isn't a solution, but I thought just in case this is how yourpK systems are being used, it would save you all the late nights & pulled hairm2 working out why things aren't working as expected.   Regardsa   Andrew Robinsonp   > -----Original Message-----@ > From: JanWermusch@hotmail.com [mailto:JanWermusch@hotmail.com] > Sent: 14 August 2001 08:52 > To: Info-VAX@Mvb.Saic.Coml9 > Subject: Re: Pseudo Terminals to emulate LAT Terminals?' >  >  < snip > > H > Hmmm... I think I did not express myself as exact as necessary (one of > my personal problems <g>). > D > The peripheral devices currently connected to terminal servers are? > automatic devices sending material orders to the AXP host and-G > expecting appropriate answers. Now those devices shall be replaced by-? > PCs, not connected to terminal servers, but using TCP/IP (thek4 > application actually uses UDP echoing mechanisms).D > At the AXP side, the 3rd party process for processing the materialE > order request talks to LTA devices that have been configured during  > LAT startup. > . > What I am now trying to do is the following: > F > 0. Because I cannot play around with the 3rd party app (critical), I: > need to test it on another machine with other processes.G > 1. I found a little app, say "LTAAPP", that uses LTA devices the samesE > way as the 3rd party app does (hopefully). At least it talks to LTA0 > devices bi-directional.tC > 2. I wrote a little TCP program "TCPAPP" listening on port x, sayo > 12345, and let it run.G > 3. I now want to create a TNA1234 using reverse telnet, connecting ton > port 12345 on the same host.> > 4. Now DEFINE/SYS/EXEC LTA5678 TNA1234: (as Nic Clews wrote)@ > 5. Let the LTAAPP run and send something to the LTA1234 device7 > 6. Hope that TCPAPP receives the data sent in step 5.O > G > Does this make any sense? Please do not kill me if that is too stupidpC > for the discussion - the only somewhat deeper experience on VMS I-H > currently have is in writing UCX based apps for UDP and TCP in FORTRAND > 77. Up to now I used LAT only from the customer's perspective when- > configuring devices for other applications.e > 
 > Regards  > Jani >    ------------------------------  , Date: Tue, 14 Aug 2001 17:14:35 +0200 (CEST): From: "Gotfryd Smolik, VMS lists" <gotfryd@stanpol.com.pl>7 Subject: Re: Pseudo Terminals to emulate LAT Terminals? J Message-ID: <Pine.LNX.4.21.0108141710290.18272-100000@irys.stanpol.com.pl>  # On 13 Aug 2001, Jan Wermusch wrote:   v >+John Laird <john@laird-towers.freeserve.co.uk> wrote in message news:<g1qfnt8q3t8hbhvglhrjipak66d564icp8@4ax.com>... [...]rD >+> You could look at WRQ's Reflection package - quite reasonable VTF >+> emulation and it *can talk LAT*, so your users will create LTAnnnnI >+> devices when they log in, just as they would on the terminal servers. L >+> However, the terminal server and port information for each terminal port >+> will be "fake".  [...] 
 >+Hi John, >+E >+pardon me, but I am getting little bit confused: I just checked the*E >+active reflection sessions on another customer's AXP machine. All I2F >+found was a number of TNA terminals (connected to port x on host y), >+as expected...  (  Reflection *can* connect with LAT, but:6 1. you must have the LAT protocol installed on the PC.8  If you select (with Reflection installation) *only* the6  terminal emulator then you misses the LAT protocol :)B  (check b.ex. in windows "network info" the available prot. stack)7 2. Reflection *can* use LAT, but you must *SELECT* it !I8  Select "connection setup" (on Reflection emulator menu)4  and select LAT. If you see only TCPIP - goto "1" :)    Regards - Gotfryd   -- sE =====================================================================mF $ ON F$ERROR("LANGUAGE","ENGLISH","IN_MESSAGE").GT.F$ERROR("NORMAL") - 		THEN EXCUSE/OBJECT=ME.. $!                        GS@stanpol.zabrze.plE =====================================================================-   ------------------------------  % Date: Tue, 14 Aug 2001 11:35:21 -0400e+ From: "Rick Barry" <barry@star.zko.dec.com>r, Subject: Re: Query string problem with CSWS.2 Message-ID: <fCbe7.106$bB1.13049@news.cpqcorp.net>  ? "Martin Vorlaender" <martin@radiogaga.harz.de> wrote in messageI5 news:3b74b2a1.524144494f47414741@radiogaga.harz.de...g4 > Malcolm Dunnett (nothome@spammers.are.scum) wrote:9 > >  I've run into a problem with the OSUScript module ofe5 > > CSWS. It appears that the query string is getting-7 > > the first character chopped off of it. Eg If I havee
 > > a url of:k > >M/ > >   http://myserver/htbin/procedure?param=abcs > >M: > >  I get a value of "aram=abc" in WWW_QUERY_STRING after > > running CGI_SYMBOLS. > >.2 > >   This brings up a support question - is CSWS: > >    a.) not supported?.< > >    b.) supported under a VMS software support agreement?< > >    c.) supported under a separately purchased agreement? >  > AFAIK, it's b.)a >n   (For Malcolm Dunnett)-  E CSWS is supported by Compaq under the existing VMS support agreement.T  J Regarding this particular problem, we have a fix which will be included in anF CSWS ECO release scheduled for September or October. If you would likeI to receive a temporary patch, please contact the Customer Support Center.R  
 Rick Barry   Compaq Secure Web Server OpenVMS System Software Groups Compaq Computer Corporationt
 Nashua, NH   ------------------------------  # Date: Tue, 14 Aug 2001 15:56:29 GMT = From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-)N Subject: SCSI ID on RZ230 Message-ID: <00A00840.9DBD161F@SendSpamHere.ORG>   Hi,   L I offered to restore a backup to an RZ23.  I received the tape and the driveL FedEx just moments ago but I don't know which pins will permit me to address this drive.   L Any help would be greatly appreciated.  I usually look on Seagate's site but% it appears that the RZ23 is a Conner.f    --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COMh            nJ   "And of course, I'm a genius, so people are naturally drawn to my fiery I   intellect.  Their admiration overwhelms their envy!" -- Calvin & Hobbes    ------------------------------  % Date: Tue, 14 Aug 2001 17:39:40 +0100 4 From: John Laird <john@laird-towers.freeserve.co.uk> Subject: Re: SCSI ID on RZ238 Message-ID: <4lkint876eq6lgnbd1c3nctousmif42ulc@4ax.com>  @ On Tue, 14 Aug 2001 15:56:29 GMT, system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-) wrote:p  M >I offered to restore a backup to an RZ23.  I received the tape and the driveRM >FedEx just moments ago but I don't know which pins will permit me to address  >this drive.  G Address as in SCSI address ?  The 3 pins marked E1,E2,E3 I think (about H an inch behind the other jumper pins, facing out from the circuit board, all by themselves)  M >Any help would be greatly appreciated.  I usually look on Seagate's site but:& >it appears that the RZ23 is a Conner.  G I've never failed to find anything on Seagate's support site - it's oneaH of the very best for anything and everything ever produced by themselvesD or the companies/technologies they took over.   (pause)  Having saidF that, their legacy Conner page is in terms of Conner model numbers :-)  2 Google got an FAQ in one hit "RZ23 scsi jumper"...     	Johne --  
 John Laird Yezerski Roper Ltd   ------------------------------  # Date: Tue, 14 Aug 2001 16:40:57 GMTi= From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-)t Subject: Re: SCSI ID on RZ230 Message-ID: <00A00846.D4455F41@SendSpamHere.ORG>  o In article <4lkint876eq6lgnbd1c3nctousmif42ulc@4ax.com>, John Laird <john@laird-towers.freeserve.co.uk> writes::A >On Tue, 14 Aug 2001 15:56:29 GMT, system@SendSpamHere.ORG (Brian:  >Schenkenberger, VAXman-) wrote: >iN >>I offered to restore a backup to an RZ23.  I received the tape and the driveN >>FedEx just moments ago but I don't know which pins will permit me to address
 >>this drive.e >gH >Address as in SCSI address ?  The 3 pins marked E1,E2,E3 I think (aboutI >an inch behind the other jumper pins, facing out from the circuit board,n >all by themselves)s  J Thanks... I'm off to do the restore... that is if the backup tape is good.   --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COMn            cJ   "And of course, I'm a genius, so people are naturally drawn to my fiery I   intellect.  Their admiration overwhelms their envy!" -- Calvin & HobbesS   ------------------------------  % Date: Fri, 10 Aug 2001 21:32:16 -0400a2 From: rdeininger@mindspring.com (Robert Deininger) Subject: Re: Server up?tL Message-ID: <rdeininger-1008012132170001@user-2ivech6.dialup.mindspring.com>  0 In article <ncWc7.25$bB1.4459@news.cpqcorp.net>,$ hoffman@xdelta.zko.dec.nospam wrote:  H > In article <CIEJLCMNHNNDLLOOGNJIGELCDBAA.tom@kednos.com>, "Tom Linden" <tom@kednos.com> writes: > :Anybody know? > : >   Yes, the tub is filled with brightly colored wrenches.  H When I first read this, I thought I saw the word "wenches".  Which wouldG make the thread somewhat more interesting.  At least if anyone knew them location of the server/tub.F   -- k Robert Deininger rdeininger@mindspring.comp   ------------------------------  % Date: Tue, 14 Aug 2001 09:20:56 +0100m% From: Alan Greig <a.greig@virgin.net>s+ Subject: Re: Storageworks retirement letters8 Message-ID: <4knhntsf20s4krifrgie8742ilbjde7s95@4ax.com>  3 On Mon, 13 Aug 2001 12:04:53 -0500, "Dave Gudewicz"o" <david.gudewicz@abbott.com> wrote:  M >Interesting to note that the HSZ80, while not on the retirement list, is note >on the migration list.   C Yes that worried me so I now have another question open with CompaqgD regarding retirement plans for the HSZ80. I have asked if Compaq canA guarantee there are no current plans to withdraw support for thisJE controller and to explain the change in policy allowing an item to beuC desupported within two years of last sale. Nobody will give me thatt guarantee or explanation.    >Dave... >>: >"Alan Greig" <alan.greig@intl.fmcti.com> wrote in message3 >news:8iffnt8178nrckh0p20hc18b8u9rg52ntl@4ax.com...  >>G >> I've scanned in the letter from Compaq and OCRd it. Here is the texteF >> of the letter. I can email a physical scanned image if anyone needs >> one.r >>	 >> ======e >> >> Compaq Computer Limited >> Worton Grange Imperial Way. >> Reading Berkshire RG2 OTE >> >> >> Telephone 0118 986 8711 >> Fax 01189867969 >> www.compaq.co.ukd >> >> >> >> >>
 >> ALAN GREIGa >> ....s >> Address ommittedt >> ....c >> >> 21st June 2001. >>" >> Dear Software Service Customer, >>G >> Compaq Computer Limited, Customer Services UK and Ireland, wishes toe= >> inform you that we have begun a retirement process for thelF >> distribution and services for the software of the following storage >> hardware items: >>H >> HS1CP, HSD3O, HSD5O, HSJ3O, HSJ4O, HSJ5O, HSZ4O, HSZ5O, HSZ7O, RA41O,G >> AA450, RA3000 wfth HSZ22 (for NT/Alpha, Novell Netware, Sun Solaris,l >> HP-UX, IBM-AIX) >>G >> As a result of this retirement, Compaq SOFTWARE Services (ie license C >> subscription, software update distribution services and software.H >> telephone support) will no longer be available for the above items asF >> of 30th Jan 2002. Note hardware maintenance continues for the above	 >> items.  >>I >> In addition software services for the RA3000 with HSZ22 (for NT/Intel,-H >> VMS/Alpha, Unix/Alpha) will end on 31st July 2003. Again the hardware >> maintenance will continue.b >>H >> A migration path is offered with 50% off the storage controller priceI >> (le HSG8O and HSJ8Os). We can also offer leasing options for those whoeC >> would prefer to lease the new storage controllers and associatedh
 >> equipment.  >>E >> The suggested migration paths for those who wish to upgrade are as  >> follows:  >> >> HSDxx migrate to HSG8Ob" >> HSJxx migrate to HSG8O or HSJ8O >> HSZxx migrate to HSG8O,# >> HS1 CP migrate to HSG8O or HSJ8O " >> RA41O migrate to HSG8O or HSJ8O" >> RA450 migrate to HSG8O or HSJ8O% >> RA3000 with HSZ22 migrate to HSG8Oe >>5 >> The options currently available are the following:eA >> i) Continue with your current storage hardware and continue to 1 >> receive hardware maintenance support services.JE >> ii) Migrate to the relevant HSx8O option and related storage under  >> a leasing arrangement.eC >> iii) Migrate to the relevant HSx8O option as a straight purchase3 >> arrangement.v >>G >> For further information on migration and leasing options please callrH >> our Glasgow call centre on 0845 270 4114 quoting campaign code 01 SML >> >> Yours faithfully, >> >> >> >> >> Trish Sandysc >> Compaq Computer Ltd >> Compaq Customer Services 2 >> Registered Office: Hotharn House 1 Heron Square= >> Richmond Surrey TW9 IEJRegistered n England number 1792087- >> >> >> --  >> Alan4 >g   -- Alan   ------------------------------  % Date: Tue, 14 Aug 2001 09:16:24 +0100 % From: Alan Greig <a.greig@virgin.net>e+ Subject: Re: Storageworks retirement lettern8 Message-ID: <21nhntk11evpodp7cnhlorvb61m5j32gmc@4ax.com>  , On Mon, 13 Aug 2001 12:22:44 -0400, JF Mezei% <jfmezei.spamnot@videotron.ca> wrote:o   >Alan Greig wrote:G >> As a result of this retirement, Compaq SOFTWARE Services (ie license C >> subscription, software update distribution services and softwareuH >> telephone support) will no longer be available for the above items asF >> of 30th Jan 2002. Note hardware maintenance continues for the above	 >> items.y >e >sJ >Shouldn't Compaq first have announced thatthe software was to be declaredE >mature, but continuing software and hardware support with only minoreM >fixes/patches to be made available if need be ? Announce a migration path asrM >was announced and then a year or two later, if migration has gone well, thenb/ >you announce widthdrawal of software support ?r  D Yes, that was the way things used to happen. I'd normally count on aB minimum of five years (and usually much more) between last sale ofC product and end of full support, Compaq have reduced this figure todB two years or less and that;s just not on. People talk about the PCF world way of doing things but most five year old PCs will boot currentE versions of Windows (ME or 2000). A far longer period to obsolescenced than the HSZ70 and HSZ22.,  M >The way I see this, this "180 day transformation" is forcing that departmenteA >to streamline its product line ASAP even at the cost of Compaq's 2 >credibility/trustability in the enterprise field.  A I think so too. Proof that Capellas and Winkler do not understande their enterprise customer base.o   -- Alan   ------------------------------  % Date: Tue, 14 Aug 2001 09:34:52 +0100t% From: Alan Greig <a.greig@virgin.net> + Subject: Re: Storageworks retirement lettert8 Message-ID: <jsnhntgpavqgkkia2aij6gplj0enmh084d@4ax.com>  A On Mon, 13 Aug 2001 22:19:11 GMT, Dirk Munk <munk@home.nl> wrote:l   >e >t >Dave Gudewicz wrote:M > O >> Interesting to note that the HSZ80, while not on the retirement list, is nott >> on the migration list.t >cO >True, and even more remarkable is that the HSJ80 is on the list. Why ? BecausedP >today we received a mailing that the whole CI technology (incl. HSJ80) is goingQ >to be retired. Wouldn't it be great if Compaq could develop a kind of a coherentuK >product strategy ? Mayby the people in charge think in terms of Wintel boxm  D I don't think they can develop a coherent policy because they simplyC don't know what they are doing. Just possibly if customers can wake F Capellas up from his fantasy he might actually pay enough attention to? the Enterprise market to notice what they're doing. But I guessa, staring lovingly at iPAQs is more his style.     -- Alan   ------------------------------  % Date: Tue, 14 Aug 2001 10:34:00 +0100t% From: Alan Greig <a.greig@virgin.net>c+ Subject: Re: Storageworks retirement letter 8 Message-ID: <b2shntkfcgllqh30uf9ung92n5jeq59908@4ax.com>  A On Mon, 13 Aug 2001 22:19:11 GMT, Dirk Munk <munk@home.nl> wrote:    >e >e >Dave Gudewicz wrote:a >'O >> Interesting to note that the HSZ80, while not on the retirement list, is notg >> on the migration list.. >tO >True, and even more remarkable is that the HSJ80 is on the list. Why ? BecauserP >today we received a mailing that the whole CI technology (incl. HSJ80) is goingQ >to be retired. Wouldn't it be great if Compaq could develop a kind of a coherente  F Sorry forgot to add: Any chance you could post a copy of that mailing?     -- Alan   ------------------------------  % Date: Tue, 14 Aug 2001 08:24:36 -0700a' From: David Mathog <mathog@caltech.edu>i+ Subject: Re: Storageworks retirement lettert+ Message-ID: <3B7942B4.FDAFBA9E@caltech.edu>i   Alan Greig wrote::  C > On Mon, 13 Aug 2001 22:19:11 GMT, Dirk Munk <munk@home.nl> wrote:m >. > >h > >  > >Dave Gudewicz wrote:  > > Q > >> Interesting to note that the HSZ80, while not on the retirement list, is notr > >> on the migration list.s > >sQ > >True, and even more remarkable is that the HSJ80 is on the list. Why ? Because R > >today we received a mailing that the whole CI technology (incl. HSJ80) is goingS > >to be retired. Wouldn't it be great if Compaq could develop a kind of a coherenteM > >product strategy ? Mayby the people in charge think in terms of Wintel boxl > F > I don't think they can develop a coherent policy because they simply! > don't know what they are doing.r  R Obviously.  Which raises the question of why the Compaq board lets them muddle on.J They had no problem dumping the previous CEO over problems which pailed in comparison.uP Mr. Rosen must have seen  this coming down the road when he bailed a while back.  % > Just possibly if customers can wakelH > Capellas up from his fantasy he might actually pay enough attention to5 > the Enterprise market to notice what they're doing.   P Such a wake up call will likely come in the form of a precipitous drop in sales.
 I stronglyK suspect that that number's been dialed already and will show up in the next) quarterly report.P  P One  sign that alpha sales may have already slowed is that Compaq is now pushingR (dumping) DS20s through Pioneer-Avnet into the education market at greatly reduced- prices.  This is unusual because historically T (my experience only)  the first tier vendors never offered prices lower than that of the  smallerT vendors, in fact, they usually quoted me list price and wouldn't budge. In this case the big boys seem toS have a lot of machines in stock to dispose of quickly, and since they can sell them M for less than the smaller vendors, Compaq must have given them one heck of an # incentive to unload these systems..:  N Of course, the other reason the prices may have come down could be because theH quality has fallen off as well.  Of 3 DS20s (all Tru64, even though theyS accidentally shipped one with a VMS PAK) that were delivered to a fellow downstairstN only one was fully functional when delivered, a second had some loose internalO connections which were relatively easily diagnosed and repaired,  and the thirdoQ appears to be DOA.  Compaq "Quality" (sic)  now seems to encompass  at least someh Alpha products.s     Regards,   David Mathog mathog@caltech.edu  O *******************************************************************************d *m
 RIH Compaq *tO *******************************************************************************t   ------------------------------  # Date: Tue, 14 Aug 2001 15:34:59 GMT ' From: ben_myers@charter.net (Ben Myers)p+ Subject: Re: Storageworks retirement letterT/ Message-ID: <3b794469.1383453@news.charter.net>e  F Obsolesence is one thing.  Many (ALL?)  of these damned vendors do notA have a clue how much money and effort are involved "throwing out" D their old and quite reliable hardware in exchange for the newer moreF cheaply made stuff.  They just figure you can unplug the old equipmentE and plug in the new.  It does not work that way, even for replacementtD of Wintel desktop systems.  The cost of the hardware has been provenE many times over to be the tip of the iceburg in the famous managementID buzzword phrase "Total Cost of Ownership".  And the cost of hardware5 is an ever-diminishing percentage of TCO... Ben Myers=  C On Tue, 14 Aug 2001 09:16:24 +0100, Alan Greig <a.greig@virgin.net>- wrote:  - >On Mon, 13 Aug 2001 12:22:44 -0400, JF Mezei & ><jfmezei.spamnot@videotron.ca> wrote: >d >>Alan Greig wrote::H >>> As a result of this retirement, Compaq SOFTWARE Services (ie licenseD >>> subscription, software update distribution services and softwareI >>> telephone support) will no longer be available for the above items as G >>> of 30th Jan 2002. Note hardware maintenance continues for the abovew
 >>> items. >> >>K >>Shouldn't Compaq first have announced thatthe software was to be declaredsF >>mature, but continuing software and hardware support with only minorN >>fixes/patches to be made available if need be ? Announce a migration path asN >>was announced and then a year or two later, if migration has gone well, then0 >>you announce widthdrawal of software support ? >pE >Yes, that was the way things used to happen. I'd normally count on a C >minimum of five years (and usually much more) between last sale ofFD >product and end of full support, Compaq have reduced this figure toC >two years or less and that;s just not on. People talk about the PCrG >world way of doing things but most five year old PCs will boot currentlF >versions of Windows (ME or 2000). A far longer period to obsolescence >than the HSZ70 and HSZ22. >tN >>The way I see this, this "180 day transformation" is forcing that departmentB >>to streamline its product line ASAP even at the cost of Compaq's3 >>credibility/trustability in the enterprise field.  >1B >I think so too. Proof that Capellas and Winkler do not understand  >their enterprise customer base. >  >--g >Alan0  	 Ben Myers6 Spirit of Performance, Inc.  73 Westcott Road Harvard, MA 01451  tel: 978-456-3889h eFax: 810-963-0412    PayPal, MC, VISA, AMEX accepted.   ------------------------------  % Date: Tue, 14 Aug 2001 12:17:12 -0400b- From: JF Mezei <jfmezei.spamnot@videotron.ca>t+ Subject: Re: Storageworks retirement lettero, Message-ID: <3B794F07.5B4A6375@videotron.ca>   David Mathog wrote: T > Obviously.  Which raises the question of why the Compaq board lets them muddle on.L > They had no problem dumping the previous CEO over problems which pailed in
 > comparison.vR > Mr. Rosen must have seen  this coming down the road when he bailed a while back.  H Misters Capellas and Winkler gave themselves 180 day "immunity" from the= board, during which they can do as much dammage as they want.a  N Remember that the key to this 180 thing is the purchase of companies that willK give Compaq a 40% growth rate in the software/solutions/support area. GreateK promise. But if at the end of the 180 days, there are indications that theyhI may succeed in buying some profitable companies, then the board will keeps
 these 2 guys.m  H Their job is perfectly safe at least until the end of the year, at whichN point, if they continue at that rate, the "true enterprise" sections will haveL been decimated, and all that is left is what Compaq really wanted all along,0 the wintel divisions (PCs and servers and Ipaq).  R > Such a wake up call will likely come in the form of a precipitous drop in sales.X > I strongly suspect that that number's been dialed already and will show up in the next > quarterly report.e  K Not sure. That single contract with the military might offset all the othernM lost sales. I am quite convinced that Compaq found a way to make the death ofdH Alpha fairly transparent to the financials and that the lost sales won't materialise much.S  M Heck, did Compaq get blasted because VMS sales were actually going down priorgN to last year mini-marketing attempt ? No. And why should it, VMS is an unknownN entity, hidden under layers of bean counter's numbers, so whether it does well5 or bad doesn't really show up on Compaq's financials.O   ------------------------------  + Date: Tue, 14 Aug 2001 12:42:18 -0300 (ART) A From: =?iso-8859-1?q?Fabio=20Cardoso?= <fabiopenvms@yahoo.com.br>s Subject: Testing new email@ Message-ID: <20010814154218.17656.qmail@web20201.mail.yahoo.com>   Just testing   Please ignore !=20   F=E1bio Cardosot  L ___________________________________________________________________________= ____________________ Yahoo! GeoCitiesL Tenha seu lugar na Web. Construa hoje mesmo sua home page no Yahoo! GeoCiti= es. =C9 f=E1cil e gr=E1tis!A http://br.geocities.yahoo.com/   ------------------------------   Date: 14 Aug 2001 12:23:18 GMT- From: kraemer@clri6e.gsi.de (Michael Kraemer) J Subject: Re: The Alpha Systems Customer Update will no longer be published4 Message-ID: <9lb57m$91n$1@sun27.hrz.tu-darmstadt.de>   In article <y4elqej3s6.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>, Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de> writes:= > Kilgallen@eisner.decus.org.nospam (Larry Kilgallen) writes:f > I > > I was under the impression that the VMS enewsletter only came in PDF.t6 > > There is no supported PDF reader shipped with VMS. > L > There is no operating system that I know of that ships with a PDF reader. ? > VMS at least ships with the freeware CD, which contains one. i   So does AIX.   > Good luck on3 > doing this with a standalone Unix or Windoze box.a >  > 	Jan   ------------------------------   Date: 14 Aug 2001 16:23:16 GMT1 From: bill@triangle.cs.uofs.edu (Bill Gunshannon)uJ Subject: Re: The Alpha Systems Customer Update will no longer be published, Message-ID: <9lbj9k$2sge$5@info.cs.uofs.edu>  H In article <y4elqej3s6.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>,J  Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de> writes:> |> Kilgallen@eisner.decus.org.nospam (Larry Kilgallen) writes: |> oJ |> > I was under the impression that the VMS enewsletter only came in PDF.7 |> > There is no supported PDF reader shipped with VMS.Z |>  M |> There is no operating system that I know of that ships with a PDF reader. oL |> VMS at least ships with the freeware CD, which contains one. Good luck on4 |> doing this with a standalone Unix or Windoze box. |> i  C well, if you mean as an integral part of the OS, I would guess youreD right.  But I know FreeBSD ships OS CD's with various PDF viewers on them.1   bill   -- xJ 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: 14 Aug 2001 11:38:30 -05009 From: Kilgallen@eisner.decus.org.nospam (Larry Kilgallen)>J Subject: Re: The Alpha Systems Customer Update will no longer be published3 Message-ID: <OMeKj0w7$nGu@eisner.encompasserve.org>>  ` In article <9lbj9k$2sge$5@info.cs.uofs.edu>, bill@triangle.cs.uofs.edu (Bill Gunshannon) writes:J > In article <y4elqej3s6.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>,L >  Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de> writes:@ > |> Kilgallen@eisner.decus.org.nospam (Larry Kilgallen) writes: > |> wL > |> > I was under the impression that the VMS enewsletter only came in PDF.9 > |> > There is no supported PDF reader shipped with VMS.e > |> iO > |> There is no operating system that I know of that ships with a PDF reader. tN > |> VMS at least ships with the freeware CD, which contains one. Good luck on6 > |> doing this with a standalone Unix or Windoze box. > |> > > E > well, if you mean as an integral part of the OS, I would guess youroF > right.  But I know FreeBSD ships OS CD's with various PDF viewers on > them.d  & MacOS ships with Adobe Acrobat Reader.  @ But my original comment was in reaction to the fact that the VMS$ newsletter ships only in PDF format.   ------------------------------  % Date: Tue, 14 Aug 2001 13:34:07 -0400w- From: JF Mezei <jfmezei.spamnot@videotron.ca>eJ Subject: Re: The Alpha Systems Customer Update will no longer be published, Message-ID: <3B796108.64B947DD@videotron.ca>   Larry Kilgallen wrote:B > But my original comment was in reaction to the fact that the VMS& > newsletter ships only in PDF format.  N And VMS is not supposed to be used on the desktop. Compaq wants you to use oneS of its wintel boxes on yoru desktop with VMS relegated to some large computer room.o  L And with Compaq's pusg to streamline its products, I doubt that you will seeW any push to make VMS more viable on the desktop since it would compete against Windows.   N The only OS that will be allowed by Compaq to live on both the desktop and the! computer room will be Windows/NT.>    M I don't agree with this, but it seems a fact and there isn't much that can beG done to change this.   ------------------------------  % Date: Tue, 14 Aug 2001 08:57:52 +0200>< From: Jan-Erik =?iso-8859-1?Q?S=F6derholm?= <noone@home.com>8 Subject: Re: Using Ghostscript to conv PS to PDF on VMS.( Message-ID: <3B78CBF0.24AE36A3@home.com>  
 Hi. Bradford.d2 Would it be possible to see an "GS -h" output from3 that build of GS ? I would like to see what drivers,4 it's build with. Or it is a "standard" build without
 any changes ?   	 Jan-Erik.S   "Bradford J. Hamilton" wrote:e >  > Hi Jan-Erik, > ; > Here is a code snippet that I use to "distill" PS to PDF.4 [snip, snip] >    ------------------------------  % Date: Tue, 14 Aug 2001 09:02:49 +0200t< From: Jan-Erik =?iso-8859-1?Q?S=F6derholm?= <noone@home.com>8 Subject: Re: Using Ghostscript to conv PS to PDF on VMS.( Message-ID: <3B78CD19.102A57C2@home.com>   Hi. * God to see that you run without any DECW !  @ I just unZIP'ed and run the OPENVMS.COM in the [.SRC] directory.B "$ GS -h" shows that the pdfwrite driver is there. (And X11 is the first in the list.)   E (Hm, may be it would be possible to build a version of GS with *only*f thep pdfwrite driver !?)i  ? Anyway, I'll "destill" the command syntax out of the DCL scriptdC sent by Bradford. But it *do* looks very much like the one I tried.n   Jan-Erik Sderholm.f   Andy Burns wrote:e >  > G > It's been several years since I worked with GS on VMS but I think youvE > need to see what device drivers have been compiled into the versionfF > you have and use "-d xxxxx" qualifiers accordingly .... we certainlyF > compiled a version that did PS->CCITT/T4 without any DECW dependance >  > -- > Andy Burns   ------------------------------  % Date: Tue, 14 Aug 2001 09:52:53 +0100o! From: Andy Burns <andy@burns.net>a8 Subject: Re: Using Ghostscript to conv PS to PDF on VMS.8 Message-ID: <ciphnt4n8jmo95agr0jbn6hkdpfokaoaob@4ax.com>  6 On Tue, 14 Aug 2001 09:02:49 +0200, Jan-Erik Sderholm <noone@home.com> wrote:r  + >God to see that you run without any DECW !l  > I remember years ago trying to persuade the display postscript. extensions to render a ps file to a bitmap :-(  A >I just unZIP'ed and run the OPENVMS.COM in the [.SRC] directory.@C >"$ GS -h" shows that the pdfwrite driver is there. (And X11 is theD >first in the list.) >pF >(Hm, may be it would be possible to build a version of GS with *only* >the >pdfwrite driver !?)  A yes you can recompile it and set the default or only driver to bewF pdfwrite, then you won't need -sDEVICE=xxxx (I remembered wrongly with	 -d=XXXXX)d  @ >Anyway, I'll "destill" the command syntax out of the DCL scriptD >sent by Bradford. But it *do* looks very much like the one I tried.   -- s
 Andy Burns   ------------------------------  % Date: Tue, 14 Aug 2001 18:58:48 +0010n% From: paddy.o'brien@zzz.tg.nsw.gov.aue* Subject: Re: VAX/ALPHA FORTRAN and me! :-)5 Message-ID: <01K74UW2ZMFM003VPK@tgmail.tg.nsw.gov.au>e   Dave Weatherall wrote:  F >On Mon, 13 Aug 2001 16:58:31, Steve Lionel <Steve.Lionel@compaq.com>  >wrote:a >hG >> On Alpha, you MUST use the Fortran compiler's IARGCOUNT (and IARGPTR G >> if desired) intrinsics to get the argument count.  Trying to do thistF >> in a separate assembler routine will fail more likely than not (andF >> the routine would have to be completely rewritten anyway - argumentE >> lists look very different on Alpha.)  If the compiler doesn't knownD >> you're looking at the argument list, it will likely not "home" it= >> (store it to memory in the fashion you're used to on VAX.)> >> rB >> No version of Digital or Compaq Fortran has provided a GET_ARGS >> routine.h >iB >Those were the intrinsics and the VAX/AXP change I was trying to @ >remember. I never had time to check fo yesterday. Thanks Steve.   Have a good holiday in UK.  ; Probably neither of us were right, nor neither of us wrong.p  I My gut reaction about GET_ARGS was because of the oft discussed in c.l.f  F issue on how to get command line arguments.  Paul Lentz' code in that M respect did not give us any real clue.  IIRC from such discussions, GET_ARGS gB is a unixy thing asked about by people porting to other platforms.  G When Paul discovers the code for GET_ARGS, he will obviously see which 3K "arguments" are being referred to -- command line or subroutine.  If it is DK the latter, he will need to follow SL's advise.  If the routine is written tK for VMS and is for the command line, it will either have calls to the CLI$ ,D routines or LIB$GET_FOREIGN and could be in Fortran.  Arguments for L subroutine calls would be in MACRO, so Paul should also look for .MAR files.  M Regardless, Paul needs to locate the routine and work from there.  I repeat,  J look for OPT files or COM files to link (build) the program -- or even an  MMS script.   J As Robert D. suggested, redo the exercise on a VAX and look at the linker G map.  With all the options suggested by various of us, you should have e' enough ammunition to complete the port.u   Good luck from here on.e   Regards, Paddy   ------------------------------  % Date: Tue, 14 Aug 2001 12:43:21 +0200e, From: Didier Morandi <Didier.Morandi@gmx.ch>, Subject: Re: VIRUSES: What about antibodies?& Message-ID: <3B7900CA.D27140C8@gmx.ch>   "John E. Malmberg" wrote:  > J > Vaccines do not kill viruses.  Vaccines pre-trigger the immune system soC > that it can respond more quickly from a virus infection.  This ise( > essentially what a Virus Scanner does. ../..i  
 Nice post. Thanks,h   D.   ------------------------------   Date: 14 Aug 2001 16:18:21 GMT1 From: bill@triangle.cs.uofs.edu (Bill Gunshannon)d. Subject: Re: Writing to a DOS floppy under VMS, Message-ID: <9lbj0d$2sge$3@info.cs.uofs.edu>  ; In article <61B330D3E7DFD3118A740090271EE321713444@TACCSF>,iN  Binyon Steve Contr Det 4 AFC2TIG/ASRCC <Steve.Binyon@kirtland.af.mil> writes: |> aK |> The real question is:  Is it possible to write to a DOS formatted floppyiM |> under the VMS system, much like you can do under Unix (mount -t msdos...)?e6 |> This is under OpenVMS 7.1 running on a Alpha au600. |> a  I Hmmmm....  I wonder if the DOSUtils tools are a candidate for the porting J project??  Might be a good example of the differences in hardware handling between Unix and VMS.n   Comments??  Hoff??   bill   --  J 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>   p   ------------------------------  % Date: Tue, 14 Aug 2001 11:45:04 -0500m+ From: Phil Mendelsohn <mend0070@tc.umn.edu>s. Subject: Re: Writing to a DOS floppy under VMSG Message-ID: <Pine.SOL.4.20.0108141143420.7736-100000@garnet.tc.umn.edu>*  & On 14 Aug 2001, Bill Gunshannon wrote:  = > In article <61B330D3E7DFD3118A740090271EE321713444@TACCSF>,*P >  Binyon Steve Contr Det 4 AFC2TIG/ASRCC <Steve.Binyon@kirtland.af.mil> writes: > |>  M > |> The real question is:  Is it possible to write to a DOS formatted floppyTO > |> under the VMS system, much like you can do under Unix (mount -t msdos...)?M8 > |> This is under OpenVMS 7.1 running on a Alpha au600. > |> m > K > Hmmmm....  I wonder if the DOSUtils tools are a candidate for the portingrL > project??  Might be a good example of the differences in hardware handling > between Unix and VMS.t >  > Comments??  Hoff??  @ Didn't I see mtools ported from UNIX/Linux/GNU?  I think it's on FREEWARE4.0 or 5.0   Phil Mendelsohne   -- n& "Remember, Rome didn't fall in a day."   ------------------------------   End of INFO-VAX 2001.450 ************************