1 INFO-VAX	Sat, 06 Oct 2001	Volume 2001 : Issue 555       Contents: Re: Alternate vendor memory.8 Re: Can I restore system disk shadow set without reboot?8 Re: Can I restore system disk shadow set without reboot?# Re: Comments on Compaq presentation # Re: Comments on Compaq presentation # Re: Comments on Compaq presentation & Re: Compaq Service FTP1 Server Broken?& Re: Compaq Service FTP1 Server Broken?& Re: Compaq Service FTP1 Server Broken?+ Re: DEClaser Fonts? (was Re: Printer fonts) > Re: Export Controls and Security Ratings (was: Re: VAX 7000's)! Re: Full printer support at last? ! Re: Full printer support at last? ! Re: Full printer support at last? 	 Re: HSD05 	 Re: HSD05  HSZ40 Firmware Needed K Re: I WILL QUIT USING VMS WHEN THE MILITARY DOES - IN 2015 OR MAYBE LONGER!  Re: Itanium and OpenVMS  Re: Itanium and OpenVMS  Re: Itanium and OpenVMS  Re: Lkwset before CMKRNL& Re: Major VMS reseller says VMS legacy& Re: Major VMS reseller says VMS legacy& Re: Major VMS reseller says VMS legacy& Re: Major VMS reseller says VMS legacyP Re: Meta, giga, yadda yadda yadda (was Re: Comments on Compaq        presentatioP Re: Meta, giga, yadda yadda yadda (was Re: Comments on Compaq presentation) pres Microsoft Reliability At MSN Re: Need help with RMS One more disk for a Alphaserver # Oracle/OpenVMS Itanium quote on web ' Re: Oracle/OpenVMS Itanium quote on web ' Re: Oracle/OpenVMS Itanium quote on web ' Re: Oracle/OpenVMS Itanium quote on web ' Re: Oracle/OpenVMS Itanium quote on web ' Re: Oracle/OpenVMS Itanium quote on web ' Re: Oracle/OpenVMS Itanium quote on web * Re: PC LA70 driver (was: Re: LA-70 Driver) Re: PGP for OpenVMS?? : Re: Problem With VMS Backup Save-Set Spanning Tape Volumes: Re: Problem With VMS Backup Save-Set Spanning Tape Volumes: Re: Problem With VMS Backup Save-Set Spanning Tape Volumes: Re: Problem With VMS Backup Save-Set Spanning Tape Volumes: Re: Problem With VMS Backup Save-Set Spanning Tape Volumes: Re: Problem With VMS Backup Save-Set Spanning Tape Volumes prot codes LP? Re: prot codes LP? prot codes LP? Re: prot codes LP? Re: prot codes LP? Re: prot codes LP? Re: prot codes LP? Re: Question on VMS Virus   Re: Reset error account on Alpha  Re: Reset error account on Alpha  Re: Reset error account on Alpha  Re: Reset error account on AlphaI Re: V7.3 XFC Crash (was: Re: [VMS V7.3 Alpha] my first crash since months  Re: VMS 5.4 supported? WP 5.1+ Docs Re: WP 5.1+ Docs  F ----------------------------------------------------------------------  " Date: Fri, 5 Oct 2001 21:54:43 GMT( From: Terry Kennedy <terry@gate.tmk.com>% Subject: Re: Alternate vendor memory. ' Message-ID: <GKr677.ELL@spcuna.spc.edu>     Dirk Munk <munk@home.nl> writes:I >>   So? DEC has always done the same thing - the last letter (the "Y" in L >> "M####-XY" indicated what memory manufacturer's chips were on the board).J >> In fact, they charged more for out-of-warranty repair on some versions,I >> simply because later on they found that manufacturer's chips were less  >> reliable. > O > You're absolutely right, but at least it was visible from the partnumber that O > different brand of chips were used, or different speed sometimes (60 ns or 70  > ns).  K   I think that Kingston (I can't speak for the other vendors) does the same J thing. A DEC part number like "MS11-LB" doesn't tell you what parts are onH the card, only the card type (PDP-11, parity, etc.). The M8743-xx numberF tells you what chips are on there (if you have the secret decoder 8-).  I   Kingston does the exact same thing. A part number like KTV-MS310/512 is E used to describe the module type, while a number like 9902188-005.A01 F describes the exact revision, chip vendor, board artwork rev, etc. AndF with Kingston you can specify on your order that you want/don't want a specific revision.  H   BTW, I've aways found the Kingston folks very helpful - as an example,H a couple years ago I called and wanted to know the loading on the memoryG drivers for 2 64MB vs. 1 128MB part and they put the design engineer on 
 the phone.  K >>   Now you're being a little fast and loose with the term "module". There M >> are 3 components in a ready-for-sale SIMM - the memory chips, the PC board I >> they are mounted on, and the assembly/testing/warranty (well, actually K >> these days there are things like the SPD on there, but that isn't really 
 >> relevant).  > M > That is very relevant, because many memory (=DIMM) manufacturers don't fill N > their SPD with acurate information. In that case a system may not be able toP > use the right settings for its memory access.  Some companies even use another > companies manufucturer code.  <   I meant it wasn't relevant to the manufacturing process...  K > No, Kingston may buy complete DIMM's from a manufacturer and sell them as I > Kingston. So the same Kingston partnumber may refer to totaly different L > modules with hopefully the same characteristics (even if the specs are the > same).  L   In maybe 5000 pieces of assorted Kingston memory, I've never seen one that6 didn't use a Kingston PCB. So it is likely quite rare.  K >>   All three of these could have quality ranging from excellent to awful. M >> The more a manufacturer has control over the whole process, the better and L >> more consistent the end result is likely to be. But there isn't much dif-? >> frence between a high-end assembler and a chip manufacturer.  > P > True, but DIMM modules with the same chips from one company may differ quite aB > lot from a DIMM module with the same chips from another company.  '   I think you're agreeing with me here.   4         Terry Kennedy             http://www.tmk.com2         terry@tmk.com             New York, NY USA   ------------------------------   Date: 5 Oct 2001 13:51:48 -0700 - From: afeldman@gfigroup.com (Alan E. Feldman) A Subject: Re: Can I restore system disk shadow set without reboot? = Message-ID: <af1e4ce6.0110051251.1f60af19@posting.google.com>   t John Laird <john@laird-towers.freeserve.co.uk> wrote in message news:<0i7rrtsljauid2r68dlbbg8nc7kqbiv4b9@4ax.com>...2 > On Fri, 05 Oct 2001 13:28:06 +0200, Frank Heckel$ > <Frank.Heckel@de.bosch.com> wrote: > $ > >Steve.Spires@yellgroup.com wrote: > >>  R > >> Can I restore the system disk shadow set from this position without a reboot? > >>   > > G > >Simply mount the second disk to the shadow set. Once you did this it I > >will be rememberd by the system, so the shadow set is complete after a ? > >reboot without the mount statement in the startup procedure.   A You shouldn't have a mount statement for the adding memebers to a F system disk shadow set in the startup procedure! See the warning aboutB this in the Volume Shadowing manual. Disregarding this warning can result in loss of data.    > E > This is how someone built the shadowed system disk set in the first I > place, Steve !  (Although I admit the manual is not exactly specific on  > dealing with system disks.)   F Normally when one is setting up a system disk shadow set for the firstF time, one manually adds members after the boot. IIRC the shadow set isE reconstructed properly in subsequent boots. In any case, I'd heed the  warning mentioned above.  F I may be able to try this on my test machine later (it's tied up doingE something right now) and if I get a chance I'll try your scenario and C see if you can safely create a system disk shadow set after booting ; with system disk shadowing turned off and report back here.    [snip]   Disclaimer: JMHO Alan E. Feldman  afeldman&gfigroup.com    ------------------------------   Date: 5 Oct 2001 16:49:17 -0700 - From: afeldman@gfigroup.com (Alan E. Feldman) A Subject: Re: Can I restore system disk shadow set without reboot? = Message-ID: <af1e4ce6.0110051549.1d7f29e0@posting.google.com>   W Steve.Spires@yellgroup.com wrote in message news:<00256ADC.004306A5.00@quegw01.btyp>...  [snip]O > I had to apply some patches to one of our nodes, I took one device out of the P > system disk shadow set, applied the patches on the remaining single member set > and rebooted.  > P > Unfortunately I was over-zealous and did the following; set SHADOW_SYS_DISK toO > 0, and commented out the shadow set mount command from our startup mount disk C > procedure. SHADOW_SYS_DISK is dymanic, so that can be reset to 1.   E Take out that mount command! Do not put commands in your startup that E add members to the *system disk* shadow set!!! See the warning in the B Volume Shadowing manual. Disregarding this warning can cause disksC with more current data to be overwritten by a disk with older data. E Not only should you not do it, but you don't need to. When you reboot F a system, the system disk shadow set is automatically reconstructed toE the state it was in just prior to the shutdown. You do have to wait a E few minutes for any needed copy or merge operations to begin, though.   E Here's the warning copied from the Volume Shadowing manual on the VMS  website:   Caution   E Do not add members to a system disk shadow set in startup procedures. F Doing so can result in loss of data under the following circumstances:  A A system is operating normally with a multiple member system disk  shadow set.   F The original boot device is removed from the shadow set but remains as a functioning disk.   1 The system continues with the remaining members.    % The system is shut down or it fails.    C The system is rebooted using the original boot device (which is now  out of date).    B The boot process determines that the boot device is not consistentC with the other shadow set members and, therefore, does not add them  into the shadow set.  B This behavior preserves the up-to-date data on the other members.   B A MOUNT command in the startup procedure adds the other shadow set& members to the system disk shadow set.  E A copy operation from the boot device to the other shadow set members ' is initiated, thereby overwriting them.         YIPES!    P > So, I have the situation where I have the system up, but no system disk shadow9 > set. I can't get a window to reboot for some time so...  > O > Can I restore the system disk shadow set from this position without a reboot?  [snip]  F No, you can't because the system disk is already mounted. I even tried> it on my test system, but it doesn't work. And since you can'tD dismount the system disk without shutting down, I am afraid you willA have to wait for the next reboot window. My 6.2 system parameters = documentation doesn't list SHADOW_SYS_DISK as dynamic, but it E obviously is, but it doesn't matter because you have to reboot for it  to take effect.    Disclaimer: JMHO Alan E. Feldman  afeldman&gfigroup.com    ------------------------------  % Date: Fri, 05 Oct 2001 15:02:05 -0400 - From: JF Mezei <jfmezei.spamnot@videotron.ca> , Subject: Re: Comments on Compaq presentation, Message-ID: <3BBE03AA.992ED828@videotron.ca>   Simon Clubley wrote:N > >Carly (yes, he called her by that name) agreed to honour Compaq's contracts > >with customers.  L What is important is that it was mentioned twice by the same person. What itQ tells me is tha Compaq are aware that customers don't trust the merger or Compaq.   = > > Suggestion that customers should get things on paper now. C > Get what on paper ? Hardware maintainence or future VMS support ?   M It was not specified. I have a feeling that there was a strong message here.  N Lets speculate here: lets assume that the president of Compaq Canada knew thatM certain Compaq products would be sold/killed as a result of the HP merger (or N to allow the merger to be approved by the govt).  He can't say that of course,G but he gives a subtle hint to customers to get support firmed on paper, K especially if your current support contract is to expire on the year of the  merger being completed.   N Now, this guy would not be privy to what is really going on in terms of CompaqL selling off products to other firms, but he might have a clue about upcomingG product retirement announcements (consider the news on c.o.v. that some 2 storageworks products were retired "prematurely").  N I have a feeling that DII-COE may be more important that it looks. If you signM DII-COE, you are effectively shielded from Curly and Carly's antics for about M 10 years. If you don't sign it, you are at their mercy if they decide to sell ! VMS to MS to be cannabalised etc.   F > "cult" ? Makes us sound like a bunch of people holding onto obsoleteJ > technology instead of embracing the new wonderful world of Microsoft andK > their superior technology. [And yes, I am been sarcastic, I'm a VMS fan.]   K But if that is how we are viewed, then that is how we are viewed. Note that J "cult" does have some advantages when you consider that it was "cult" that. allowed Apple to survive during its hard times) because the "cult" was so loyal to Apple.   G > [Somehow though, I don't see Microsoft been allowed to buy VMS, thank  > goodness...]  I Why not ? They alreadty have about half of VMS's technologies. And Compaq N could sell the VMS engineers to Microsoft. Look at the Alpha thing. They foundK a way to structure the deal to make it palatable to anti-competition folks.    ------------------------------  # Date: Fri, 05 Oct 2001 19:44:16 GMT 3 From: Tim Llewellyn <tim.llewellyn@cableinet.co.uk> , Subject: Re: Comments on Compaq presentation/ Message-ID: <3BBE0D2A.DE1F5FAF@cableinet.co.uk>    John Santos wrote:    > > Here is the official list: > >       megabyte > >       gigabyte > >       terabyte > >       hexabyte > >       petabyte. > >       exabyte  (he made fun of that one !) > >       zettabyte / > >       yottabyte (24 zeros in that number !)  > H > I've heard of terabytes, petabytes and exabytes (both flavors) before,F > but I don't remember hexabytes.  Counting from megabyte has 6 zeros,F > yottabyte should have 27 zeros, so I wonder if there's an extra size > in there?  > 2 > What comes after yottabyte?  Whollottabyte?  ;-) > : no, the sensible thing to do is to redefine the base unit. A Giga Exabyte anybody?    --   Tim.Llewellyn@cableinet.co.uk     C Standard disclaimer applies. My views in no way represent those of  ! my employers or service provider.    ------------------------------  % Date: Fri, 05 Oct 2001 23:03:30 -0400 ' From: Howard S Shubs <howard@shubs.net> , Subject: Re: Comments on Compaq presentation< Message-ID: <howard-028BCF.23032905102001@enews.newsguy.com>  , In article <3BBD68AF.8936D2D8@videotron.ca>,/  JF Mezei <jfmezei.spamnot@videotron.ca> wrote:   2 > And finally, he said something most interesting:I > He said that Microsoft is aware that Windows has some ways to go before M > getting to the scalability/availability. And he mentioned that he was under M > NDA, but that we should not be surprised if Microsoft were to buy something C > soon to help it get there. (I see VMS->Microsoft the same way as   > Alpha->Intel)   M I could get used to dealing with Compaq.  I have no problem with the idea of  H working with HP.  Microsoft... would at the very least take more effort. --   Howard S ShubsD "Run in circles, scream and shout!"  "I hope you have good backups!"   ------------------------------  " Date: Fri, 5 Oct 2001 18:04:14 GMT' From: Rick Dyson <Rick-Dyson@UIowa.EDU> / Subject: Re: Compaq Service FTP1 Server Broken? ) Message-ID: <3BBDF61E.A66BBEAA@UIowa.EDU>   # > Let me try and unconfuse you. :-)  > O > [I have not tried it on VMS, but I've duplicated your problem, interactively, ' > on Win98, with the MSDOS FTP client.]  >  > > M > >       Interactively, I have no problem using this site via Anonymous FTP. K > >However, the command procedure I have used for years suddenly won't work ? > >for me anymore.  I use TCPIP v5.0A ECO2 from OpenVMS v7.2-1.  > > , > >$ Define /User_Mode Sys$Input Sys$CommandA > >$ FTP /UserName = Anonymous /Password = "rick-dyson@uiowa.edu"  > D > You need anonymous in lower case, quoted to preserve the case. :-)  ( Bingo!  That fixed it.  I changed it to:   	/UserName = "anonymous"   and it is working.  
 Good Eye!!   Thanks!    ------------------------------  # Date: Fri, 05 Oct 2001 18:51:32 GMT 2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)/ Subject: Re: Compaq Service FTP1 Server Broken? / Message-ID: <Uinv7.27$RL6.110@news.cpqcorp.net>   S In article <3BBDB02C.926C8A03@UIowa.EDU>, Rick Dyson <Rick-Dyson@UIowa.EDU> writes:e  J   Argh.  Unmarked "courtesy" email.  Grumble.  Now I get to head off into K   my mail folder and dig up the private email reply that I sent in regards o
   to this.   ..G :	I see others also have noticed the failed access to the old server ifoJ :they have an authorized account.  Later, I noticed Anonyous FTP also quit :working, too. :S@ :	Maybe I just caught the server as it was being taken off-line? :sI :	Will all ECOs be available via Anonymous FTP?  I.e, in the public area?l ..  <   Ok, here's what I sent when I responded to this last time:   	--i  D   I know the ECO folks have been shuffling processes around, and theD   movement of materials over to the compaq.com domain is continuing.C   (I have also noticed a lack of forwards to the new URLs, and haveuF   requested this be addressed.  I've also started to track the changesH   made to the OpenVMS-relevent URLs in updates to the FAQ and in changes:   made to the URLs that are posted at the OpenVMS website.  A   I am not particularly familiar with the non-anonymous logins toe   the ECO area.   G   There is a contact at the ECO website that should get problem reportsr   to the correct person.   	eN  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  $ Date: Fri, 5 Oct 2001 18:53:54 -0400  From: John Santos <JOHN@egh.com>/ Subject: Re: Compaq Service FTP1 Server Broken?r6 Message-ID: <1011005184823.37040B-100000@Ives.egh.com>  % On Fri, 5 Oct 2001, Rick Dyson wrote:n  % > > Let me try and unconfuse you. :-)u > > Q > > [I have not tried it on VMS, but I've duplicated your problem, interactively,m) > > on Win98, with the MSDOS FTP client.]a > >  > > >lO > > >       Interactively, I have no problem using this site via Anonymous FTP. M > > >However, the command procedure I have used for years suddenly won't workuA > > >for me anymore.  I use TCPIP v5.0A ECO2 from OpenVMS v7.2-1.p > > > . > > >$ Define /User_Mode Sys$Input Sys$CommandC > > >$ FTP /UserName = Anonymous /Password = "rick-dyson@uiowa.edu"t > > F > > You need anonymous in lower case, quoted to preserve the case. :-) > * > Bingo!  That fixed it.  I changed it to: >  > 	/UserName = "anonymous" >  > and it is working. >  > Good Eye!! > 	 > Thanks!g  C Maybe this explains the original problem with non-anonymous logins.7  C It looks like they've changed their FTP server to be case-sensitiveC@ about usernames and possibly passwords.  The original poster has? been snipped out of this thread, but can you verify the case ofeA the username and password originally supplied by DECCOMPAQHP, ando= make sure you are preserving it (with quotes if supplied on an> command line?)  Also, it might be that some FTP clients always@ upcase or downcase usernames and passwords (but if so, how would; they work with Unix servers, which have used case-sensitivet6 passwords forever, IIRC?)  Which client are you using?   -- s John Santoso Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------  # Date: Fri, 05 Oct 2001 18:48:51 GMTc2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)4 Subject: Re: DEClaser Fonts? (was Re: Printer fonts). Message-ID: <ngnv7.26$RL6.24@news.cpqcorp.net>  Q In article <1002285849.791796@news.hrp.no>, "Terje Bodal" <terjeb@hrp.no> writes:hK :Does anyone know how to find out wich fonts is available on the postscript,M :printer and how to load additinonal fonts. I have a problem printing cyrilicyA :characters on a dec laser using the Arial isolatin cyrilic font.      Which DEClaser?   2   How much memory does the printer have installed?:   Specific details of the particular problems encountered?    N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  # Date: Fri, 05 Oct 2001 19:29:51 GMTv2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)G Subject: Re: Export Controls and Security Ratings (was: Re: VAX 7000's)i/ Message-ID: <PSnv7.36$RL6.174@news.cpqcorp.net>s  i In article <9pk11v$35h$1@tyfon.itea.ntnu.no>, Roar =?iso-8859-1?Q?Thron=E6s?= <roart@nvg.ntnu.no> writes: I :It might be that there are other reasons than software that recent 7800sg :are wanted by the government?  E   Most commonly (and not unsurprisingly) for data center replication nE   efforts, though there are obviously various other reasons possible.   J :Some computer hardware seem to have military classification, but it seems@ :to be difficult finding (the right) information on such things.  H   This is likely a reference to the theoretical performance rating of a 9   particular computer, as calculated for export controls.r  F :And looking at http://www.radium.ncsc.mil/tpep/epl/epl-by-class.html,@ :it does not seem to cover newer VMS versions (-> hardware too).  H   The NCSC security evaluations are not relevent to and not particularlyE   related to the performance-based computer hardware export controls.f  J :At http://www.openvms.compaq.com/openvms/os/openvms71.html it says B1 andL :C2, but I have not found any newer. (With AS 8400 as the best/newest Alpha)? :How long does it take to acquire classifications as B1 and C2?k  H   How long is in units of money and time, measured in years and buckets.G   (Even the ratings maintenance -- RAMP -- process takes a substantial s   investment.)  ! :Will 7.3 have B1 (just curious)?-  F   There are other approaches outside of the NCSC process and there areG   other security ratings evaluations, and (if there are folks that are bH   interested in this area) I can individual folks into contact with the 9   appropriate security folks here in OpenVMS Engineering.i  N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------   Date: 5 Oct 2001 14:29:04 -0500r- From: Kilgallen@SpamCop.net (Larry Kilgallen)s* Subject: Re: Full printer support at last?3 Message-ID: <pkHiYgv7QXqW@eisner.encompasserve.org>d  n In article <051020011249413424%paul.r.anderson@compaq.com>, Paul Anderson <paul.r.anderson@compaq.com> writes:G > In article <782cd74d.0110050759.5f4cf6bf@posting.google.com>, Stanley   > Hippler <stan@lsua.edu> wrote: > / >> Any idea when DCPS will support the hp 9000?m > I > The HP LaserJet 9000 is planned to be supported in DCPS V2.1, scheduled  > for Q1 2002.   What is a LaserJet 9000 ?y  # I don't find it on the HP web site.h   ------------------------------  % Date: Fri, 05 Oct 2001 16:16:13 -0400m0 From: Paul Anderson <paul.r.anderson@compaq.com>* Subject: Re: Full printer support at last?; Message-ID: <051020011616138654%paul.r.anderson@compaq.com>   C In article <pkHiYgv7QXqW@eisner.encompasserve.org>, Larry Kilgallenc <Kilgallen@SpamCop.net> wrote:   > What is a LaserJet 9000 ?m% > I don't find it on the HP web site.-  F The 9000 is a 50-PPM printer.  There is information on their web site;E choose "Products & Services", "Printers", "For Business Black & White 
 Printers".   Paul   -- D  Paul Anderson   OpenVMS Engineering.   Compaq Computer Corporationl   ------------------------------   Date: 5 Oct 2001 15:31:52 -0500.- From: Kilgallen@SpamCop.net (Larry Kilgallen)e* Subject: Re: Full printer support at last?3 Message-ID: <ZSP3yZFYEuoS@eisner.encompasserve.org>e  n In article <051020011616138654%paul.r.anderson@compaq.com>, Paul Anderson <paul.r.anderson@compaq.com> writes:E > In article <pkHiYgv7QXqW@eisner.encompasserve.org>, Larry Kilgallen   > <Kilgallen@SpamCop.net> wrote: >  >> What is a LaserJet 9000 ?& >> I don't find it on the HP web site. > H > The 9000 is a 50-PPM printer.  There is information on their web site;G > choose "Products & Services", "Printers", "For Business Black & Whitei > Printers".   Thanks.  Got it.  B Silly me, I had selected the choice that read "LaserJet Printers".   ------------------------------  # Date: Fri, 05 Oct 2001 18:33:52 GMT " From: Alfred Falk <falk@arc.ab.ca> Subject: Re: HSD059 Message-ID: <Xns91317FCE52824falkarcabca@205.233.108.180>p  @ dittman@dittman.net wrote in news:gh6v7.24724$S27.1304828@e420r- atl2.usenetserver.com:  A > I have a couple of HSD05 controllers.  I need to configure them B > correctly, but I don't have a manual.  Does anyone have a manual > available? > F > If not, what are the settings for the dip switches inside the HSD05? > E > I connected one to my VAX 4000/500 on DSSI bus 1.  From the consoletF > problem (>>>) I can see the HSD05 and the connected drives, but onceH > I boot VMS neither the drives nor the HSD05 can be seen.  I'm guessingH > I have something configured wrong, but without a manual I can't figure > out what is wrong.   Configuration switches:g!     	#    	definition    	Default 1     	-    	---------------    	------------------eF     	1    	MSB of DSSI ID    	open   (DSSI ID=0) Must be unique on bus"     	2    	NSB of DSSI ID    	open"     	3    	LSB of DSSI ID    	open0     	4    	MSB of SCSI ID    	Closed (SCSI ID=7)      	5    	    	    	    	Closed$     	6    	LSB of SCSI ID    	closed     	7    	spare    	    	open     	8    	spare    	    	open     	9    	spare    	    	open?     	10    	Active SCSI Term    	closed (terminators installed)   , You may need to do some software configuring From >>> enter command     	SET HOST/DUP/DSSI/BUS:n a     	  n is DSSI bus ID, 0 or 1b&     	  a is DSSI id for the controller) When asked for "Task Name?" enter params.p$ Try  SHOW /ALL to see all parameters Interesting ones are:h!     	NODENAME    	Name of the HSD -     	DISK_ALCS    	Allocation class for diskstE     	    	    	0 is fine if not in a cluster, otherwise maybe same aso     	    	    	VAX host.)     	TAPE_ALCS	Allocation class for tapes @     	UNIT_OFFSET   default is 0.  Helps with multiple DSSI buses     	a@ Use SET commands to change parameters (looks a lot like SYSGEN).1 When done, enter WRITE and then RESTART commands.   @ ----------------------------------------------------------------A   A L B E R T A         Alfred Falk               falk@arc.ab.ca z@ R E S E A R C H         Information Systems Dept   (780)450-5185+   C O U N C I L         250 Karl Clark Road81                         Edmonton, Alberta, Canadae http://www.arc.ab.ca/   T6N 1E4r  http://www.arc.ab.ca/staff/falk/   ------------------------------  # Date: Fri, 05 Oct 2001 18:36:28 GMT  From: dittman@dittman.nete Subject: Re: HSD05A Message-ID: <M4nv7.28151$S27.1471339@e420r-atl2.usenetserver.com>    dittman@dittman.net wrote:A : I have a couple of HSD05 controllers.  I need to configure themiB : correctly, but I don't have a manual.  Does anyone have a manual : available?  ) I now have a copy of the manual.  Thanks.e -- : Eric Dittman dittman@dittman.netC= Check out the DEC Enthusiasts Club at http://www.dittman.net/i   ------------------------------  # Date: Sat, 06 Oct 2001 02:58:23 GMTd From: dittman@dittman.nety Subject: HSZ40 Firmware NeededA Message-ID: <jruv7.23054$6i7.1576995@e420r-atl1.usenetserver.com>l  G I am looking for an updated HSZ40 PCM card.  My current version is 2.7,rE which is pretty out-of-date.  Does anyone have any extras that are ofy* a more recent release they'd like to sell?   -- t Eric Dittman dittman@dittman.netc= Check out the DEC Enthusiasts Club at http://www.dittman.net/t   ------------------------------  $ Date: Fri, 5 Oct 2001 15:09:10 -04002 From: "Sue Skonetski" <susan.skonetski@compaq.com>T Subject: Re: I WILL QUIT USING VMS WHEN THE MILITARY DOES - IN 2015 OR MAYBE LONGER!/ Message-ID: <yynv7.33$RL6.166@news.cpqcorp.net>d   Alan,    I didr   Suee  2 "Alan Greig" <a.greig@virgin.net> wrote in message2 news:nivorts69s6svcbb2903f6v28rqf5nfetj@4ax.com...3 > On Thu, 4 Oct 2001 10:50:57 -0400, "Peter Weaver"s! > <peter.weaver@stelco.ca> wrote:  >l@ > >"Sue Skonetski" <susan.skonetski@compaq.com> wrote in message/ > >news:sl_u7.1073$YP.26045@news.cpqcorp.net...h	 > >> Bob,i > >>C > >> I just wanted to let you know that I sent your note to the VMSa engineeringoI > >> group here in ZK today.  Talk about making a persons day.  Thank youd very7 > >> much for posting this note.  We feel the same way.w > >>...I > >tL > >How about sending it to all of the marketing and sales people. If I could beK > >so bold to speak for others, I would say that most of the people in thisSK > >newsgroup feel the same way. We need to get the marketing people feelingu thee+ > >same way and get this out to the masses.n >lA > Exactly! In fact why not forward it to Capellas and Winkler for:0 > comment? That's a serious question by the way. >n > -- > Alan   ------------------------------  * Date: Fri, 5 Oct 2001 21:55:13 +0000 (UTC) From: david20@alpha1.mdx.ac.uk  Subject: Re: Itanium and OpenVMS+ Message-ID: <9pla81$hpb$1@aquila.mdx.ac.uk>   q In article <20011005113757.86138.qmail@web20201.mail.yahoo.com>, Fabio Cardoso <fabiopenvms@yahoo.com.br> writes: 8 >Today I think in a few advantages of porting OpenVMS=20 >to Itanium. >a7 >OpenVMS, Windows 64 and Unix/Linux will have in commonf >,2 >the Itanium processor -so they can share the same >code. > * >I believe will be easier to port software1 >between these platforms. I am not saying we will 2 >run MS Office under OpenVMS or Unix/Linux, but in, >terms of Server Applications will be great./ >Despite the internals differences of the OSes, 6 >probably, the great number of applications not ported5 >to OpenVMS can get a boost...And sometimes I imagine - >OpenVMS applications being ported to W64 and- >Unix/Linux. >- >    Fabio,  - Why are you trotting out this rubbish again ?uI The fact the operating systems all run on the same chip has little if anyg bearing on software porting.L All these OS's ran on Alpha (Windows 64 was developed on Alpha and NT ran on Alpha for a number of years).     
 David Webb VMS and Unix team leader CCSS Middlesex University   ------------------------------  * Date: Fri, 5 Oct 2001 17:02:24 -0700 (PDT). From: Fabio Cardoso <fabiopenvms@yahoo.com.br>  Subject: Re: Itanium and OpenVMS@ Message-ID: <20011006000224.86422.qmail@web20201.mail.yahoo.com>   Davido  3 I am not a PhD in operating systems and hardware=20 3 architecture and I know what is portability betweenl& operating systems in diff. processors.  8 If all these OSes will run in the same processor, why=204 their applications couldnt share the same libraries?5 What I am saying now is consolidate and integrate thed "calls".  , It is different from porting from VAX/VMS or# Solaris/HPUX/AIX to Windows 2000...D  4 If the operating systems are in the same level of=203 hardware, a project should be developed to make theA coexistence.  - If three operating systems can share the sameh2 processor architecture (Itanium), I believe in the/ near future the differents OSes  will share oneS- processor and memory area. Any doubts? Nobodyl+ implemented yet? Nobody developed a draft ?y/ I am not talking specificaly in Interprocessinga5 implementations, but in a specific hard/soft layer=20r to do this work. Am I crazy ??1 Would a database running in OpenVMS or Unix underI4 Itanium integrate to a Windows 64 application in the6 same NUMA machine or use only one processor/menory are for both OSes? Am I nuts ?   Regardsc   FC=20      =20 # --- david20@alpha1.mdx.ac.uk wrote:/ > In article >m5 <20011005113757.86138.qmail@web20201.mail.yahoo.com>, 2 > Fabio Cardoso <fabiopenvms@yahoo.com.br> writes:/ > >Today I think in a few advantages of portingn > OpenVMS=3D20 > >to Itanium. > >m2 > >OpenVMS, Windows 64 and Unix/Linux will have in > common > >s4 > >the Itanium processor -so they can share the same > >code. > >n, > >I believe will be easier to port software3 > >between these platforms. I am not saying we willd4 > >run MS Office under OpenVMS or Unix/Linux, but in. > >terms of Server Applications will be great.1 > >Despite the internals differences of the OSes,c1 > >probably, the great number of applications notd > ported/ > >to OpenVMS can get a boost...And sometimes Ig	 > imagine / > >OpenVMS applications being ported to W64 andt > >Unix/Linux. > >	 > >a >=20 > Fabio, >=20/ > Why are you trotting out this rubbish again ? 4 > The fact the operating systems all run on the same > chip has little if any > bearing on software porting.- > All these OS's ran on Alpha (Windows 64 wasa" > developed on Alpha and NT ran on" > Alpha for a number of years).=20 >=20 >=20 > David Webb > VMS and Unix team leader > CCSS > Middlesex University     =3D=3D=3D=3D=3DaL =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3Da F=E1bio dos Santos Cardoso OpenVMS System Manager Rio de Janeiro - Brazilt fabiopenvms@yahoo.com.brL =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D   2 __________________________________________________ Do You Yahoo!?L NEW from Yahoo! GeoCities - quick and easy web site hosting, just $8.95/mon= th. # http://geocities.yahoo.com/ps/info1O   ------------------------------  % Date: Fri, 05 Oct 2001 20:51:53 -0400 - From: JF Mezei <jfmezei.spamnot@videotron.ca>   Subject: Re: Itanium and OpenVMS, Message-ID: <3BBE55A8.DC3FE950@videotron.ca>   Fabio Cardoso wrote:7 > If all these OSes will run in the same processor, whyS6 > their applications couldnt share the same libraries?  M Consider VMS has shared libraries. So when your program calls "printf" with a M bunch of arguments, the argument list is built according to VMS standards and H then the program branches to the address of the printf routine, but thatI address comes from a transfer vector included at the top of the shareable T image which tells it where inside the shareable image that "printf" code is located.  I Consider that the concept of shareable images may exist in other OSs, butmL their format and method to branch to them isn't the same and the way to pass arguments is also different.   ------------------------------  # Date: Fri, 05 Oct 2001 19:03:32 GMTt2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)! Subject: Re: Lkwset before CMKRNLi. Message-ID: <8unv7.31$RL6.72@news.cpqcorp.net>  k In article <f660c23e.0110050716.591a2519@posting.google.com>, nilakantan_m@hotmail.com (Nilakantan) writes:r  E :I have a piece of code to be executed in kernel mode .I need to lockeC :this piece of code before I issue CMKRNL call so as to prevent anyy :pagefault at this IPL.   C   You would have to have kernel-mode code that operates at elevatedeF   IPL -- kernel-mode code running at IPL zero (the default) tolerates    pagefaults quite nicely.  . :The description of system service LKWSET saysB :that multiple calls to lkwset should be issued to lock executableD :piece of code.I locked my code only once and and even after that my; :system crashed (PGFIPLHI).What should I do to avoid systemI; :crash?Should multiple calls to lkwset must to avoid crash.n  H   First, you have told us what you believe is a solution (and have askedJ   for help with the proposed solution), but you have not told us what the I   specific problem is.  Alternatives may well be possible here, and your  F   proposed approach may or may not address your (unspecified) problem.  I   There is an example over in Ask The Wizard topic (3803) that shows how oH   to lock both the procedure code and the procedure descriptor into the F   working set memory, and this is the MINIMUM you need to lock down.    I   If the code is operating in kernel-mode, you will also have to use somelG   specific (and different than normal) approaches toward building your dI   code.  You cannot call standard RTL routines when in kernel-mode code, -H   for instance.  Further, you cannot call any exec-mode system services.  D   Alternative approaches such as execlets or (my personal favorite) G   pseudo device drivers are also available.  But the options depend on H   the particular problem.n  N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  # Date: Fri, 05 Oct 2001 19:35:36 GMTo3 From: Tim Llewellyn <tim.llewellyn@cableinet.co.uk> / Subject: Re: Major VMS reseller says VMS legacyt/ Message-ID: <3BBE0B22.F6BEA18D@cableinet.co.uk>r   "Terry C. Shannon" wrote:i  " > M > "Effective transitional and migration to Microsoft environments (from VMS)"mM > is an oxymoron. Just ask the US Veterans Administration and others who haved > come back to VMS.   h? We shouldn't have to ask them, we should be told, by COmpaq/HP.    regardsi   -- f Tim.Llewellyn@cableinet.co.uk  r  C Standard disclaimer applies. My views in no way represent those of /! my employers or service provider.y   ------------------------------   Date: 5 Oct 2001 15:29:16 -0500a- From: Kilgallen@SpamCop.net (Larry Kilgallen) / Subject: Re: Major VMS reseller says VMS legacyo3 Message-ID: <$i02q9UocicN@eisner.encompasserve.org>o  e In article <3BBE0B22.F6BEA18D@cableinet.co.uk>, Tim Llewellyn <tim.llewellyn@cableinet.co.uk> writes:o >  >  > "Terry C. Shannon" wrote:e >  " >> lN >> "Effective transitional and migration to Microsoft environments (from VMS)"N >> is an oxymoron. Just ask the US Veterans Administration and others who have >> come back to VMS. >   A > We shouldn't have to ask them, we should be told, by COmpaq/HP.B  @ Divulging customer confidences is not the way to keep customers.- Governments are very fussy about such things.nE Remember, there are a lot of taxpayers ready to ask probing questionssC like "why did they waste our money on unproven technology like NT?"e   ------------------------------  % Date: Fri, 05 Oct 2001 20:57:53 -0500 1 From: "David J. Dachtera" <djesys.nospam@fsi.net> / Subject: Re: Major VMS reseller says VMS legacy ' Message-ID: <3BBE6520.40BFD9D7@fsi.net>-   Larry Kilgallen wrote: > g > In article <3BBE0B22.F6BEA18D@cableinet.co.uk>, Tim Llewellyn <tim.llewellyn@cableinet.co.uk> writes:d > >m > >- > > "Terry C. Shannon" wrote:  > >  " > >>P > >> "Effective transitional and migration to Microsoft environments (from VMS)"P > >> is an oxymoron. Just ask the US Veterans Administration and others who have > >> come back to VMS. > >1C > > We shouldn't have to ask them, we should be told, by COmpaq/HP.a > B > Divulging customer confidences is not the way to keep customers./ > Governments are very fussy about such things.:G > Remember, there are a lot of taxpayers ready to ask probing questionsrE > like "why did they waste our money on unproven technology like NT?"2  > Sadly, much of the tax-paying public thinks NT *IS* a "proven"F technology. After, umpteen-billion businesses *CAN'T* be wrong, right?  C "What? You mean you're *NOT* supposed to have to reboot every three:C days? ...hours? ...minutes? You mean UNIVAC *NEVER* blue-screened?"a   -- d David J. Dachtera  dba DJE Systemsi http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/a   ------------------------------  # Date: Sat, 06 Oct 2001 02:18:39 GMT04 From: "Terry C. Shannon" <terryshannon@mediaone.net>/ Subject: Re: Major VMS reseller says VMS legacyB= Message-ID: <3Stv7.85942$vq.16047841@typhoon.ne.mediaone.net>s  < "David J. Dachtera" <djesys.nospam@fsi.net> wrote in message! news:3BBE6520.40BFD9D7@fsi.net...e > Larry Kilgallen wrote: > >rA > > In article <3BBE0B22.F6BEA18D@cableinet.co.uk>, Tim Llewellynn' <tim.llewellyn@cableinet.co.uk> writes:F > > >i > > >c > > > "Terry C. Shannon" wrote:5 > > >  " > > >>L > > >> "Effective transitional and migration to Microsoft environments (from VMS)"aI > > >> is an oxymoron. Just ask the US Veterans Administration and othersl who have > > >> come back to VMS. > > >sE > > > We shouldn't have to ask them, we should be told, by COmpaq/HP.  > >PD > > Divulging customer confidences is not the way to keep customers.1 > > Governments are very fussy about such things.hI > > Remember, there are a lot of taxpayers ready to ask probing questionscG > > like "why did they waste our money on unproven technology like NT?"e >r@ > Sadly, much of the tax-paying public thinks NT *IS* a "proven"H > technology. After, umpteen-billion businesses *CAN'T* be wrong, right?  D It depends. My old ISP, Software Tool and Die in Brookline, MA, usesK SGI/Irix systems. Definitely legacy, but they're almost always up. (They'veo, had brief outages during hardware upgrades.)  K My current ISP, Mediaone, reportedly uses Wintel gear. System outages, maileK failures, and Usenet inaccessibility are far too frequent, especially given G the outrageous prices the Broadband Bandits charge. So much for NT as a  proven technology.  I Ah well. Scott McNealy had it right when he described Windows XP as beinge/ "capable of running all your favorite viruses."e   ------------------------------   Date: 5 Oct 2001 17:02:59 -0700 - From: afeldman@gfigroup.com (Alan E. Feldman) Y Subject: Re: Meta, giga, yadda yadda yadda (was Re: Comments on Compaq        presentatio = Message-ID: <af1e4ce6.0110051602.7c5aa438@posting.google.com>   \ norm.raphael@jamesbury.com wrote in message news:<C2256ADC.005D31B9.00@jklh21.valmet.com>..., > eplan@kapsch.net on 10/05/2001 06:37:10 AM >  >   >                American System3 > NAME                  VALUE IN  NUMBER  NUMBER OFn3 >                       POWERS    OF      GROUPS OFS3 >                       OF TEN    ZEROS   THREE 0'Sa5 >                                         AFTER 1,000c > + > million                 10^6    6       1i [snip], > vigintillion            10^63   63      20  C According to the number table at www.webster.com there is one more:    centillion = 10^303e   There are also         googol = 10^100o   and   )     googolplex = 10^google = 10^(10^100) i  E These last two numbers have entries in the dictionary, but are not ina the number table.V  D [ Yes, I checked the spelling and it *is* googol, at least accordingA to www.webster.com. So the famous search engine spells their namem differently! ]   Disclaimer: JMHO Alan E. Feldman  afeldman&gfigroup.coma   ------------------------------  % Date: Sat, 06 Oct 2001 01:56:13 -0400-' From: Jim Becker <jbecker@ui.urban.org> Y Subject: Re: Meta, giga, yadda yadda yadda (was Re: Comments on Compaq presentation) prese, Message-ID: <3BBE9CFD.5B2D5F45@ui.urban.org>  E > Subject:  Meta, giga, yadda yadda yadda (was Re: Comments on Compaqt >       presentation)6  * And then there's this batch of prefixes...- http://physics.nist.gov/cuu/Units/binary.htmlc   --
 Jim Becker+ The Urban Institute (http://www.urban.org/)H' Encompass (http://www.encompassus.org/)9. ESILUG (http://encompasserve.org/lugs/esilug/)   ------------------------------   Date: 6 Oct 2001 04:49:47 GMTn) From: leslie@clio.rice.edu (Jerry Leslie) % Subject: Microsoft Reliability At MSN ' Message-ID: <9pm2hb$9pd$1@joe.rice.edu>n+ Keywords: hotmail,microsoft,reliability,noti  J The attached article indicates how unreliable Microsoft operating systems H are. But the PHBs keep buying the stuff, although this may indicate some ray of hope:  8   http://news.zdnet.co.uk/story/0,,t269-s2096347,00.htmlD   ZDNet |UK| - News - Story - Windows fails to storm the data centre  4 --Jerry Leslie     (my opinions are strictly my own)N ==============================================================================E Newsgroups: comp.os.ms-windows.win95.misc,comp.os.ms-windows.nt.misc,tI comp.os.ms-windows.nt.advocacy,comp.os.ms-windows,comp.os.ms-windows.misc * From: justsayno2nt <justsayno2nt@here.com>& Subject: Re: Reasons for using Windows+ X-Nntp-Posting-Host: e232061.rtn.boeing.comc* Content-Type: text/plain; charset=us-ascii( Message-ID: <3B559E01.120AA8E4@here.com>6 Sender: nntp@news.boeing.com (Boeing NNTP News Access) Content-Transfer-Encoding: 7bit.  Organization: The Boeing Company X-Accept-Language: en2 References: <cd199975.0107100611.1c1a0373@posting.google.com>  <3B5307EE.27739B73@here.com> <3B531DB1.EFA57A6F@mediaone.net> <2E/U7wEqqeTN092yn@home.com> <3B543030.421E8B46@mediaone.net> <3g357.41335$C81.3460561@bgtnsc04-news.ops.worldnet.att.net>i Mime-Version: 1.0 # Date: Wed, 18 Jul 2001 14:32:33 GMTu; X-Mailer: Mozilla 4.76 [en]C-CCK-MCD Boeing Kit  (Win98; U).	 Lines: 19t   > F > Speaking of wallowing in ignorance, what happened when MS decided toF > run Hotmail on "the best, most advanced, OS and software developmentD > environment on the planet"? Seems this "advanced" OS just couldn't > take the load. >  >         Jerryp  D Glad, you brought that up! There is nothing like a real world test.   B I once interviewed a guy for a programming position whose previousA job was an NT sysadmin for MSN. He said every one had to carry a eC beeper and respond immediately to to server problems. The reason he A wanted to leave was that the meantime between failure of any one 5B NT server in the network was a couple of minutes. In other words, @ his beeper was going off constantly. He told me that his manager? threaten to fire any of them immediately if they leaked to the b- press about how unstable the MSN network was.    ------------------------------  % Date: Fri, 05 Oct 2001 14:31:26 -0400 - From: JF Mezei <jfmezei.spamnot@videotron.ca>n Subject: Re: Need help with RMSs, Message-ID: <3BBDFC7D.23100162@videotron.ca>   Andrew Dodd wrote: > G > I don't read C - writing this thing would be so much easier in BASIC.M > N > A FIND does not read data from the file, a GET does. So a FIND followed by aD > GET followed by an UPDATE will write back the buffer that was just > retrieved.  L But the documentation (V5, grey binders) does state that a $FIND can be usedJ to position the "cursor" to enable a $UPDATE of that record. (I have never done this).h  I Since the actual data would already be in the person's memory (as per hisaN description), the $GET would just waste resources if it isn't needed. Besides,E if you are going to do a $GET, then you don't need a $FIND before it.    ------------------------------  + Date: Fri, 05 Oct 2001 17:22:06 -0300 (EST)i From: becherini@vortex.ufrgs.br-( Subject: One more disk for a Alphaserver, Message-ID: <01100517220666@vortex.ufrgs.br>  : Received:	by vortex.ufrgs.br (V5.0A-1, OpenVMS V7.2 Alpha)+ From:		Fabio Becherini <becherini@ufrgs.br>1 Reply-to:	<becherini@ufrgs.br>< Comments:	@vortex.ufrgs.br, vortex(46.451)::, psi%........::2 References:	BR, TCHE, UFRGS, CPD network, Cia-INFO- Organization:	Cia-INFO /DRS /CPD-UFRGS /UFRGSO< ____________________________________________________________    	 	Hi guys,t  6 	We have an AlphaServer 800 5/500 running OpenVMS V7.28 	with 3 (three) "9.0 (nine) Gb Ultra Wide SCSI Hot Swap"' 	disks, no RAID, with 27 Gb total area.d  * 	As the Alphaserver has 4 slots for disks,$ 	we have a free slot for 1 more disk 	in the main cabinet, right ?k   	The questions are:   # 		- How great can be this last diske# 		  in this cabinet ? (9-18-36 ...)u    		- How much $$$ does it costs ?   	Thanks & Best regards,r  <   __________________________________________________________=  |                                                          |a=  | Fabio Becherini                 Fabio.Becherini@ufrgs.br |/=  |                              Webmaster, Postmaster UFRGS |e=  |                 Grupo de Suporte a Sistemas Operacionais |o=  | Centro de Atendimento a Incidentes de Seguranca da UFRGS |c=  |     Coordenacao da Cia-INFO (c) Ophicin@ das Informacoes |2=  |__________________________________________________________|e=  |                                                          | =  |    CPD-UFRGS - Centro de Processamento de Dados da UFRGS |i=  |                                Divisao de Rede e Suporte |u=  |                Universidade Federal do Rio Grande do Sul | =  |                     (55)(51) 3316-5041 / 3331-1215 (fax) |a=  |   Rua Ramiro Barcelos, 2574 - Porto Alegre - RS - Brasil |e=  |__________________________________________________________|M   ------------------------------  $ Date: Fri, 5 Oct 2001 15:14:50 -04002 From: "Sue Skonetski" <susan.skonetski@compaq.com>, Subject: Oracle/OpenVMS Itanium quote on web/ Message-ID: <SDnv7.34$RL6.140@news.cpqcorp.net>    Dear Newsgroup,n  E I just got this (so what's new) and thought you might want to see it.n   sueU      G Please note that the OpenVMS Itanium quote is now live on the followingu site:g  & http://www.compaq.com/partners/oracle/   ------------------------------  # Date: Fri, 05 Oct 2001 19:53:16 GMTnB From: Simon Clubley <simon_clubley@remove_me.excite.com-Earth.UFP>0 Subject: Re: Oracle/OpenVMS Itanium quote on web6 Message-ID: <Mcov7.17757$ev2.27907@www.newsranger.com>  - On Fri, 5 Oct 2001 15:14:50 -0400, in article=9 <SDnv7.34$RL6.140@news.cpqcorp.net>, Sue Skonetski wrote:= >3 >Dear Newsgroup, > F >I just got this (so what's new) and thought you might want to see it. >B >sue >aH >Please note that the OpenVMS Itanium quote is now live on the following >site: >3' >http://www.compaq.com/partners/oracle/_ >_  " The key section from that page is:  K ===========================================================================// OpenVMS Receives Strong Endorsement from Oracle   K September 7, 2001--"Oracle and Compaq have a long and successful history ofmI delivering enterprise solutions to our OpenVMS customers. In July, OracleSI released Rdb 7.1 for OpenVMS. Oracle also expects to release Oracle9i forfJ OpenVMS later this month, faster than ever before! Finally, given Compaq'sI recently announced plans to consolidate its 64-bit servers on the ItaniumhJ Processor Family, our engineering teams have already begun to work closelyM together to establish plans for the delivery of future releases of Oracle andd Rdb on OpenVMS Itanium."  8 Juan C. Jones, Vice President, System Platforms DivisionK ===========================================================================m  K This is excellent news. As someone who does not use these products, but whoaM knows that they are a couple of the required products for the VMS on IPF port'D to be viable, this sends a strong positive message about VMS on IPF.  K Has this not been mentioned here before now, or did I miss the announcement@' in the mass of postings about the WTC ?j   Simon.     -- o; Simon Clubley, simon_clubley@remove_me.excite.com-Earth.UFP K In the task of removing Microsoft from the marketplace, I have discovered atE truly remarkable plan, but this signature is too small to contain it.d   ------------------------------   Date: 5 Oct 2001 15:27:07 -0500C- From: Kilgallen@SpamCop.net (Larry Kilgallen) 0 Subject: Re: Oracle/OpenVMS Itanium quote on web3 Message-ID: <iP82mhmV$BEp@eisner.encompasserve.org>e  { In article <Mcov7.17757$ev2.27907@www.newsranger.com>, Simon Clubley <simon_clubley@remove_me.excite.com-Earth.UFP> writes:s  M > This is excellent news. As someone who does not use these products, but whooO > knows that they are a couple of the required products for the VMS on IPF portHF > to be viable, this sends a strong positive message about VMS on IPF.   Me too.o  . > Has this not been mentioned here before now,  D It has not been committed _anywhere_ before now, although there have4 been many requests to Oracle from the customer base.   ------------------------------  # Date: Fri, 05 Oct 2001 20:41:42 GMTp4 From: "Terry C. Shannon" <terryshannon@mediaone.net>0 Subject: Re: Oracle/OpenVMS Itanium quote on web= Message-ID: <aWov7.85186$vq.15779469@typhoon.ne.mediaone.net>e  : "Larry Kilgallen" <Kilgallen@SpamCop.net> wrote in message- news:iP82mhmV$BEp@eisner.encompasserve.org...oF > In article <Mcov7.17757$ev2.27907@www.newsranger.com>, Simon Clubley6 <simon_clubley@remove_me.excite.com-Earth.UFP> writes: >pK > > This is excellent news. As someone who does not use these products, buts who L > > knows that they are a couple of the required products for the VMS on IPF portH > > to be viable, this sends a strong positive message about VMS on IPF. >o	 > Me too.s >o0 > > Has this not been mentioned here before now, >dF > It has not been committed _anywhere_ before now, although there have6 > been many requests to Oracle from the customer base.  K Correct. I suspect that the release has been backdated as things were still-" up in the air as of mid-September.  ) A very positive development nevertheless.    ------------------------------  % Date: Fri, 05 Oct 2001 18:53:00 -0400-- From: JF Mezei <jfmezei.spamnot@videotron.ca> 0 Subject: Re: Oracle/OpenVMS Itanium quote on web, Message-ID: <3BBE39CB.253832D5@videotron.ca>   Larry Kilgallen wrote:F > It has not been committed _anywhere_ before now, although there have6 > been many requests to Oracle from the customer base.  C Pardon the devil's advocate, but I didn't see any commitment in theeI announcement, just an announcement that Oracle was working with Compaq to K study the project. The way I read it, they are doing a feasability study at  this point in time.@  ( Note that this is still a positive news.  K Much has been said that user level applications will just recompile fine onrL the new platform. For a middleware such as Oracle, is there any idea of whatF percentage of Oracle would just recompile on the new platform and what< percentage would need to be changed in any significant way ?   ------------------------------  % Date: Fri, 05 Oct 2001 21:26:49 -0500y1 From: "David J. Dachtera" <djesys.nospam@fsi.net> 0 Subject: Re: Oracle/OpenVMS Itanium quote on web' Message-ID: <3BBE6BE9.85731518@fsi.net>s   Sue Skonetski wrote: >  > Dear Newsgroup,. > G > I just got this (so what's new) and thought you might want to see it.  >  > sue  > I > Please note that the OpenVMS Itanium quote is now live on the following  > site:c > ( > http://www.compaq.com/partners/oracle/  C Many thanx for bringing this and other items to our attention. Youro@ posts are much appreciated, at least by me - can't speak for the	 others...m   --   David J. Dachtera  dba DJE Systems- http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/y   ------------------------------   Date: 5 Oct 2001 21:55:01 -0500 + From: young_r@encompasserve.org (Rob Young)a0 Subject: Re: Oracle/OpenVMS Itanium quote on web3 Message-ID: <32MW5iZuSwBW@eisner.encompasserve.org>n  [ In article <3BBE6BE9.85731518@fsi.net>, "David J. Dachtera" <djesys.nospam@fsi.net> writes:e > Sue Skonetski wrote: >> i >> Dear Newsgroup, >> nH >> I just got this (so what's new) and thought you might want to see it. >> d >> sue >> aJ >> Please note that the OpenVMS Itanium quote is now live on the following >> site: >> C) >> http://www.compaq.com/partners/oracle/e > E > Many thanx for bringing this and other items to our attention. YoursB > posts are much appreciated, at least by me - can't speak for the > others...i >   < 	Anyone that has spent time chatting with Sue knows that she< 	is good people.  She is sincere, her storyline is the same.' 	You can't say enough nice things . . .b   				Robn   ------------------------------  # Date: Fri, 05 Oct 2001 18:34:41 GMTo2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)3 Subject: Re: PC LA70 driver (was: Re: LA-70 Driver)d/ Message-ID: <53nv7.24$RL6.189@news.cpqcorp.net>w  Q In article <3BBCE024.E50631D8@home.com>, Andy Csepely <kicsi2l8@home.com> writes:oF :I'm in need of a windows driver for an LA-70 printer. Any thoughts? I1 :looked on some sites but was unable to find one.a  F   Wrong newsgroup -- this is the OpenVMS newsgroup, and not the random   PC widget driver newsgroup.n  H   OpenVMS treats the LA70 as a standard serial printer device, and does (   not require specialzed drivers for it.  H   You'll want to ask the Windows folks which of the gazillions of serialH   printers you should use -- the LA50, LA75 and various other serial LA %   printer drivers will probably work.5  .   The archives of PC drivers are available at:  +     http://www4.support.compaq.com/support/   F   If you follow the links to the printer links, you'll find directions<   for the LA75, which I'd tend to expect would suffice here.  N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------   Date: 5 Oct 2001 18:32:59 GMTi1 From: bill@triangle.cs.uofs.edu (Bill Gunshannon)n Subject: Re: PGP for OpenVMS??, Message-ID: <9pkucr$2ado$1@info.cs.uofs.edu>  ( In article <3bbcaf6a@news.kapsch.co.at>,-  eplan@kapsch.net (Peter LANGSTOEGER) writes:mh |> In article <3BBC8D8E.D73768CC@cableinet.co.uk>, Tim Llewellyn <tim.llewellyn@cableinet.co.uk> writes: |> >Peter LANGSTOEGER wrote: |> >> [ |> >> In article <3BBC7AC3.A82E3E64@caltech.edu>, David Mathog <mathog@caltech.edu> writes:rP |> >> >Since I'm now living without VMS, it's also completely unsupported by me. |> >>  |> >> Oh my god.7 |> >> Donate him an cheap/modern Alpha, please, ASAP !!c |> >> 	 |> >> :-)l |> > f. |> >Why? He'll probably just slap linux on it. |> > |> >:-)  |> 0M |> Not likely. SUSE drops Alpha support, RedHat will sometimes follow (RSN ?):R |> So, after Tru64 is no longer, OpenVMS is the only rest for an Alpha system :-)) |>  C Not really.  FreeBSD works quite nicely on Alpha and I have seen noj" rumblings of it being dropped yet.  ; But I would expect his preference would be VMS anyway.  :-)o   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: Fri, 5 Oct 2001 18:11:46 GMT' From: Rick Dyson <Rick-Dyson@UIowa.EDU>0C Subject: Re: Problem With VMS Backup Save-Set Spanning Tape Volumest) Message-ID: <3BBDF7E2.AB6A1AE5@UIowa.EDU>    "Richard L. Dyson" wrote:g > O > I have been asked to lend a hand in trying to restore some data from a multi-nI > tape DAT backup (4 volumes I believe) where we may have a spot part way % > through tape #1 that can't be read.*  B 	It turned out there was a "bad spot" parity error, unable to readM past on each of the three full tapes of the volume set.  I was told they wereaM all virgin tapes.  The fourth tape finished to completion, but generated somecM other error the owner did not remember what it was... :)  The original backupM didg not do verify!  Q > Is it going to be possible to plow through the bad spot and continue on through57 > the other 3 tapes, etc.?  Or will we just be screwed?d  K 	I did try someones suggestion to <crtl>-Y and spawn to set magtape/skip... N and then return and try to continue.  I had no success there, so I just always QUIT when the parity errors hit./  J 	I was able to restart the backup command with the beginning of each tape.  L 	Does anyone know about TLZ04 drivers?  Are they able to use 120m DDS2 tapesO on VAX/OpenVMS v6.2?  I found it curious that 3 of 3 virgin tapes all failed toR beP able to read all the way to the end.  Though 2 did seem to read much longer than onee of them.   Thanks for all the help!  N The user seemed to be able to get over 2/3 of the data and all of the critical data, & though that was mostly just dumb luck!   Rick   ------------------------------  % Date: Fri, 05 Oct 2001 15:05:05 -0400U4 From: John Malmberg <Malmberg@dskwld.zko.dec.compaq>C Subject: Re: Problem With VMS Backup Save-Set Spanning Tape Volumes=2 Message-ID: <3BBE0461.50407@dskwld.zko.dec.compaq>   Rick Dyson wrote:e  H  > Does anyone know about TLZ04 drivers?  Are they able to use 120m DDS2  > tapes on VAX/OpenVMS v6.2?s  D The TLZ04 can only use 60m DDS2 tapes.  It is a hardware limitation.  ?  > I found it curious that 3 of 3 virgin tapes all failed to besB  > able to read all the way to the end.  Though 2 did seem to read   > much longer than one of them.  ? Based on past discussions in this Newsgroup, that is one of the  expected error conditions.   -Johna Personal Opinion Onlym malmberg@dskwld.zko.dec.compaq   ------------------------------  % Date: Fri, 05 Oct 2001 15:07:13 -040094 From: John Malmberg <Malmberg@dskwld.zko.dec.compaq>C Subject: Re: Problem With VMS Backup Save-Set Spanning Tape Volumes84 Message-ID: <3BBE04E1.2090005@dskwld.zko.dec.compaq>   Correction:a  C The TLZ04 can only use 60m DDS tapes.  It is a hardware limitation.D   >  > -Johni > Personal Opinion Only   > malmberg@dskwld.zko.dec.compaq >    ------------------------------   Date: 5 Oct 2001 20:16:42 GMTt- From: Joe Heimann <heimann@nog.ecs.umass.edu>oC Subject: Re: Problem With VMS Backup Save-Set Spanning Tape Volumest, Message-ID: <9pl4fa$9mu$2@odo.ecs.umass.edu>  ( Rick Dyson <Rick-Dyson@uiowa.edu> wrote: > "Richard L. Dyson" wrote:i >> aP >> I have been asked to lend a hand in trying to restore some data from a multi-J >> tape DAT backup (4 volumes I believe) where we may have a spot part way& >> through tape #1 that can't be read.  D > 	It turned out there was a "bad spot" parity error, unable to readO > past on each of the three full tapes of the volume set.  I was told they weretO > all virgin tapes.  The fourth tape finished to completion, but generated somehO > other error the owner did not remember what it was... :)  The original backup- > did- > not do verify!  I Sounds like a problem we had with a bum TLZ06 drive.  It would write what.I would be reported in the error log as a soft error, but when it came timeoG to read through that point on the tape, it was a hard error that could   not be read past.s  R >> Is it going to be possible to plow through the bad spot and continue on through8 >> the other 3 tapes, etc.?  Or will we just be screwed?  M > 	I did try someones suggestion to <crtl>-Y and spawn to set magtape/skip...)P > and then return and try to continue.  I had no success there, so I just always > QUIT > when the parity errors hit.i  L > 	I was able to restart the backup command with the beginning of each tape.  N > 	Does anyone know about TLZ04 drivers?  Are they able to use 120m DDS2 tapesQ > on VAX/OpenVMS v6.2?  I found it curious that 3 of 3 virgin tapes all failed to- > beR > able to read all the way to the end.  Though 2 did seem to read much longer than > oner
 > of them.  J TLZ04 drives are only able to handle 60m DDS tapes.  The 90m and 120m onesI are too thin for the drive's transport to handle reliably.  The drive canFH stretch or snap the longer tapes in the worst case, and in the best caseJ they may not be written properly.  You need at lease a TLZ06 drive for 90m" tapes, and a TLZ07 for 120m tapes.  H As for new tapes, they have the highest oxide loss on first use, so thatC can dirty up the heads and interfere with both writing and reading.r   > Thanks for all the help!  P > The user seemed to be able to get over 2/3 of the data and all of the critical > data,o( > though that was mostly just dumb luck!   > Rick   Joe Heimanna   heimann@ecs.umass.eduk   ------------------------------  " Date: Fri, 5 Oct 2001 21:51:27 GMT' From: Rick Dyson <Rick-Dyson@UIowa.EDU>iC Subject: Re: Problem With VMS Backup Save-Set Spanning Tape Volumes ) Message-ID: <3BBE2B5F.FBDA35D6@UIowa.EDU>_   John Malmberg wrote: >  > Rick Dyson wrote:  > J >  > Does anyone know about TLZ04 drivers?  Are they able to use 120m DDS2 >  > tapes on VAX/OpenVMS v6.2?  > F > The TLZ04 can only use 60m DDS2 tapes.  It is a hardware limitation. > A >  > I found it curious that 3 of 3 virgin tapes all failed to bemD >  > able to read all the way to the end.  Though 2 did seem to read" >  > much longer than one of them. > A > Based on past discussions in this Newsgroup, that is one of the  > expected error conditions.  @ 	I just found out I was wrong on the tape drive model.  He had a, TLZ07 drive.  Are 120m DDS2 tapes OK for it?   rick   ------------------------------  " Date: Fri, 5 Oct 2001 21:54:31 GMT' From: Rick Dyson <Rick-Dyson@UIowa.EDU> C Subject: Re: Problem With VMS Backup Save-Set Spanning Tape Volumesl) Message-ID: <3BBE2C17.302C3E28@UIowa.EDU>|  L > TLZ04 drives are only able to handle 60m DDS tapes.  The 90m and 120m onesK > are too thin for the drive's transport to handle reliably.  The drive can J > stretch or snap the longer tapes in the worst case, and in the best caseL > they may not be written properly.  You need at lease a TLZ06 drive for 90m$ > tapes, and a TLZ07 for 120m tapes.  G 	Great.  I didn't read ahead, and just asked about the TLZ07...  ThanksiJ for the confirmation.  It *should* have worked, but apparently didn't very well...l  J > As for new tapes, they have the highest oxide loss on first use, so thatE > can dirty up the heads and interfere with both writing and reading.j  E 	This is what I have always known about video and audio tape and then2K I assumed was true for DAT, 8mm, DLT, etc.  Virgin tapes were the worst for  "fuzz".$   Rick   ------------------------------  # Date: Fri, 05 Oct 2001 17:53:24 GMTs2 From: "frank brown" <frank.brown@ci.seattle.wa.us> Subject: prot codes LP?a1 Message-ID: <osmv7.51$4U5.3568@news-west.eli.net>w   $ SHOW DEV/FUL PKA0: ...:& Dev Prot   S:WRLP,O:RWLP,G:RWLP,W:RWLP ..._L All help and documentation samples I've seen use only RWED protection codes. What, pray tell, are L and P?=   -Frank Brown Seattle Fire Dept. http://www.inwa.net/~frog/   ------------------------------  # Date: Fri, 05 Oct 2001 18:34:49 GMTy1 From: "Mark D. Jilson" <jilly@clarityconnect.com>S Subject: Re: prot codes LP? 2 Message-ID: <3BBDFD98.D2F8FB16@clarityconnect.com>  B See HELP SET SECURITY /PROTECTION and look at the access types for DEVICES.   frank brown wrote: >  > $ SHOW DEV/FUL PKA0: > ...t( > Dev Prot   S:WRLP,O:RWLP,G:RWLP,W:RWLP > ...aN > All help and documentation samples I've seen use only RWED protection codes. > What, pray tell, are L and P?u >  > -Frank Brown > Seattle Fire Dept. > http://www.inwa.net/~frog/   -- rD 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: Fri, 5 Oct 2001 11:40:18 -0700 (PDT) From: Lorin@LockTrack.coma Subject: prot codes LP?a. Message-ID: <01100511401849@lto.locktrack.com>  C On a device (not a file), the meaning of the E(xecute) and D(elete)  protection mask bits become:  '   L - Logical device access and control.  (   P - Physical device access and control  @ i.e., that user class may access and control the logical or(and) physical device.   regards,   Lorint   ------------------------------  # Date: Fri, 05 Oct 2001 19:09:33 GMT = From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-)a Subject: Re: prot codes LP?w0 Message-ID: <00A03138.33CBEF78@SendSpamHere.ORG>  f In article <osmv7.51$4U5.3568@news-west.eli.net>, "frank brown" <frank.brown@ci.seattle.wa.us> writes: >$ SHOW DEV/FUL PKA0:t >.... ' >Dev Prot   S:WRLP,O:RWLP,G:RWLP,W:RWLPd >.... M >All help and documentation samples I've seen use only RWED protection codes.o >What, pray tell, are L and P? >o
 >-Frank Browns >Seattle Fire Dept.i >http://www.inwa.net/~frog/  >e >o   L: Logical  P: Physicale   --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 & Hobbese   ------------------------------  # Date: Fri, 05 Oct 2001 19:53:43 GMTb2 From: "frank brown" <frank.brown@ci.seattle.wa.us> Subject: Re: prot codes LP?l1 Message-ID: <bdov7.57$4U5.4008@news-west.eli.net>i  K There is no SET SECURITY on my VMS 5.5-2 system...maybe it was added later.w Thanks anyway. -Frank  < "Mark D. Jilson" <jilly@clarityconnect.com> wrote in message, news:3BBDFD98.D2F8FB16@clarityconnect.com...D > See HELP SET SECURITY /PROTECTION and look at the access types for
 > DEVICES. >e > frank brown wrote: > >  > > $ SHOW DEV/FUL PKA0: > > ...s* > > Dev Prot   S:WRLP,O:RWLP,G:RWLP,W:RWLP > > ...oI > > All help and documentation samples I've seen use only RWED protectiont codes.! > > What, pray tell, are L and P?o > >t > > -Frank Brown > > Seattle Fire Dept. > > http://www.inwa.net/~frog/ >o > --F > Jilly - Working from Home in the Chemung River Valley - Lockwood, NY/ > - jilly@clarityconnect.com - Brett Bodine fanv- > - Mark.Jilson@Compaq.com - since 1975 or so-- > - http://www.jilly.baka.com               -0   ------------------------------  # Date: Fri, 05 Oct 2001 19:54:38 GMTa2 From: "frank brown" <frank.brown@ci.seattle.wa.us> Subject: Re: prot codes LP? 1 Message-ID: <2eov7.58$4U5.4056@news-west.eli.net>    That makes sense...thank you.h -Frank  & <Lorin@LockTrack.com> wrote in message( news:01100511401849@lto.locktrack.com...E > On a device (not a file), the meaning of the E(xecute) and D(elete)o > protection mask bits become: >t) >   L - Logical device access and controlr > * >   P - Physical device access and control >sB > i.e., that user class may access and control the logical or(and) > physical device. >r
 > regards,	 >   Lorinl   ------------------------------  % Date: Fri, 05 Oct 2001 21:23:46 -0500,1 From: "David J. Dachtera" <djesys.nospam@fsi.net>u Subject: Re: prot codes LP?p' Message-ID: <3BBE6B32.4AA8167D@fsi.net>o   frank brown wrote: > M > There is no SET SECURITY on my VMS 5.5-2 system...maybe it was added later.   : Haven't seen V5.5-2 for a while. Try one or more of these:   $ HELP SET PROTECTION    $ HELP SET DEVICE /PROTECTION    $ HELP SET VOLUME /PROTECTIONu  D Last time I tried making a "stand-alone" ("minimal") CD of V5.5-2 it+ puked. Haven't tried it lately. I wonder...t   --   David J. Dachterae dba DJE Systemse http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/l   ------------------------------   Date: 5 Oct 2001 19:38:44 GMT.1 From: bill@triangle.cs.uofs.edu (Bill Gunshannon)-" Subject: Re: Question on VMS Virus, Message-ID: <9pl284$2ckk$1@info.cs.uofs.edu>  = In article <8af17fe1.0110040559.1ca80847@posting.google.com>, ?  alphaman-nixspam@hsv.sungardtrust.com (Aaron Sakovich) writes:-T |> david20@alpha2.mdx.ac.uk wrote in message news:<9pcjm6$k67$1@aquila.mdx.ac.uk>... |> > R@ |> > Could you give a pointer to where these VMS hack sites are. |> > e |> > David Webbn |> n8 |>  http://www.phreak.org/archives/security/faqs/vax.txt |> yE |> It's dated (with all the standard implications and disclaimers duerG |> dated material), but this is a common file that is the root of other  |> docs on the net.s  D Is that one that has the tip on breaking into an RSTS/E machine thatD requires nothing special beyond physical access to the console.  :-)   billE PS.  the method specified does not work beyond V9.7 as far as I know.    --  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: Fri, 05 Oct 2001 18:32:14 GMT11 From: "Mark D. Jilson" <jilly@clarityconnect.com> ) Subject: Re: Reset error account on Alpha 2 Message-ID: <3BBDFCFD.C4650EE0@clarityconnect.com>  9 ;Fixed to work on VAX as well as pre 7.2-1 Alpha systems.c  (     .TITLE  ZDEC Zero Device Error Count     .IDENT  /1.2/  ;++d ;  ; Title:+ ;   ZDEC.MAR - Zero-out device error count.n ;m
 ; Version:	 ;   1-003t ;i ; Facility:  ;   System Management Tools. ;e ; Abstract:p? ;   This program zeros-out the device error count stored in the = ;   UCB for a particular device. This is useful when you wish 1 ;   reset this value without booting the machine.l ;n3 ;   THIS PROGRAM IS UNSUPPORTED AND PROVIDED AS IS,  ;   USE AT OWN RISK. ;o ;   Building sequence: ;n ;       $ macro/list zdec # ;       $ link/map/full/sysexe zdec5 ;  ;   Calling sequence:i ;s$ ;       $ ZDEC := $mydev:[mydir]ZDEC" ;       $ ZDEC [/OVERRIDE]  device ;u ; Environment:? ;   CMKRNL privilege required, I/O data base is locked, programh ;   executed at elevated IPL.f ;e	 ; Author:-7 ;   Mark Oakley DuPont Experimental Station 12-Nov-1984-: ;   This program is based upon the VARY program written by* ;   Gary Grebus of Battelle Columbus Labs. ;- ; Modifications: ;pH ;  17-Nov-1984  Mark Oakley Added /OVERRIDE to handle allocated devices. ; A ;  25-Nov-1985  Mark Oakley Modified to correctly secure physical- terminal@ ;               name that is associated with a virutal terminal. ;dG ;  23-May-1986  Mark Oakley Modified to zero-out CPU and memory errors.$ ;o? ;  14-Jul-1988  Ted Nieland     Modified to work under VMS 5.0.  ;lF ;  15-Jul-2001  Paul Gallo  Compaq Computer Corporation, CSC, Colorado ;C9 ;               Modified to work under OpenVMS Alpha 7.x.o ;>F ;  19-Jul-2001  Paul Gallo  Compaq Computer Corporation, CSC, Colorado ;A6 ;               Modified to return errors to the user. ;tF ;  20-Jul-2001  Paul Gallo  Compaq Computer Corporation, CSC, Colorado ;r= ;               Modified for multipath devices, as we need to/< ;               clear the errors on each device in the path. ;h ;--'    %         .SBTTL  Symbols, Macros, Data>  1         .LIBRARY            /SYS$LIBRARY:LIB.MLB/,  =         $TPADEF                     ; Symbols for LIB$TPARSE.l@         $SSDEF                      ; Symbols for return status.=         $UCBDEF                     ; Symbols for device ucb.nB         $STSDEF                     ; Symbols for returned status.8         $DEVDEF                     ; Symbols for device characteristics.B         $DVIDEF                     ; Symbols for $GETDVI service.>         $DCDEF                      ; Symbols for device type. .if df  DEV$V_MPDEV_SECONDARYnH         $MPDEVDEF                   ; Symbols for multipath information. .endc- ;- ; Macro to handle return codes.6 ;T#         .MACRO  ON_ERR  THERE,?HEREE         BLBS    R0,HEREm         BRW THEREv HERE:   .ENDM   ON_ERR  3         .PSECT  ZDEC_DATA,RD,WRT,NOEXE,LONG,SHR,PICc  B CMD_BUF:                            ; Buffer to hold command line.         .BLKB   80 CMD_BUF_SIZ = . - CMD_BUFD  A CMD_BUF_DESC:                       ; Descriptor to command line.          .LONG    CMD_BUF_SIZ         .ADDRESS CMD_BUF   PROMPT:"         .ASCID  /Device: /  A PARSE_BLK:                          ; Parse block for LIB$TPARSE.I         .LONG   TPA$K_COUNT0G         .LONG   TPA$M_ABBREV        ; Permit unambiguous abbreviations.t         .BLKB   TPA$K_LENGTH0-8b  D OVERRIDE:                           ; Zero out allocated devices, if set.         .LONG   0t  F LOG_DEV_DESC:                       ; Descriptor for device on command line.          .BLKQ   1s  E CPU_STG:                            ; Used to compare against commanda
 line parm.         .ASCII  /CPU/   E MEM_STG:                            ; Used to compare against commande
 line parm.         .ASCII  /MEMORY/    A DEV_BUF:                            ; Buffer to hold device name.n         .BLKB   40 DEV_BUF_SIZ = . - DEV_BUFo  C DEV_BUF_DESC:                       ; Descriptor pointing to devicef name.i         .LONG    DEV_BUF_SIZ         .ADDRESS DEV_BUF  ? PID:                                ; Owner of device (if any)..         .BLKL   1t  > DEV_ITEM_LIST:                      ; Device list for $GETDVI.D         .WORD    DEV_BUF_SIZ        ; Make sure we a have a physical device name.-         .WORD    DVI$_DEVNAM         .ADDRESS DEV_BUF         .ADDRESS DEV_BUF_DESCbD         .WORD    4                  ; See if someone has this device
 allocated.         .WORD    DVI$_PIDe         .ADDRESS PID         .LONG    0         .WORD    4;         .WORD    DVI$_DEVCLASS      ; Check for a terminal.y         .ADDRESS DEV_CLASS         .LONG    07         .LONG    0                  ; End if item list.   F TT_ITEM_LIST:                       ; Item list if we have a terminal.D         .WORD    DEV_BUF_SIZ        ; Make sure we a have a physical device name.>"         .WORD    DVI$_TT_PHYDEVNAM         .ADDRESS DEV_BUF         .ADDRESS DEV_BUF_DESC          .LONG    0  
 DEV_CLASS:         .LONG   1O  C K_ARG:                              ; Argument list for kernel-mode- routine.8         .LONG    1                  ; Just one argument.F         .ADDRESS DEV_BUF_DESC       ; Pass descriptor for device name.             .SBTTL  State Table 5         .PSECT  ZDEC_STATES,RD,NOWRT,EXE,LONG,SHR,PIC   )         $INIT_STATE STATE_TABLE,KEY_TABLES           $STATE  START          $TRAN   '/',QUAL.         $TRAN   TPA$_SYMBOL,DEV,,,LOG_DEV_DESC"         $TRAN   TPA$_EOS,TPA$_EXIT           $STATE  DEVe"         $TRAN   TPA$_EOS,TPA$_EXIT         $TRAN   '/',QUAL         $TRAN   ':',COLONP           $STATE  COLONv         $TRAN   '/',QUAL"         $TRAN   TPA$_EOS,TPA$_EXIT           $STATE  QUAL'         $TRAN   'OVERRIDE',,,1,OVERRIDEa$         $TRAN   'NOOVERRIDE',,CLR_OV           $STATE.         $TRAN   TPA$_SYMBOL,DEV,,,LOG_DEV_DESC"         $TRAN   TPA$_EOS,TPA$_EXIT           $END_STATE                 .SBTTL  Main program3         .PSECT  ZDEC_CODE,RD,NOWRT,EXE,LONG,SHR,PICs0         .ENTRY  ZDEC,^M<R2,R3,R4,R5,R6,R7,R8,R9>   ;a ; Get the command line.s ; 8         PUSHAL  CMD_BUF_DESC            ; Return length.A         PUSHAL  PROMPT                  ; Prompt for device name.t=         PUSHAL  CMD_BUF_DESC            ; Place to hold line.g$         CALLS   #3,G^LIB$GET_FOREIGN         ON_ERR  ERR_EXIT  ?         PUSHAL  CMD_BUF_DESC            ; Upper case the input.r         PUSHAL  CMD_BUF_DESC         CALLS   #2,G^STR$UPCASEo         ON_ERR  ERR_EXIT  H         MOVL    CMD_BUF_DESC,-          ; Set length of string to parse.)                 PARSE_BLK+TPA$L_STRINGCNTaB         MOVL    CMD_BUF_DESC+4,-        ; Set address of string to parse.)                 PARSE_BLK+TPA$L_STRINGPTRsD         PUSHAL  KEY_TABLE               ; Parse the command line for?         PUSHAL  STATE_TABLE             ; qualifier and device.          PUSHAL  PARSE_BLKo4 .if ndf  TPA$Q_NUMBER                   ; Not on VAX         CALLS   #3,G^LIB$TPARSE. .iffE         CALLS   #3,G^LIB$TABLE_PARSE    ; Alpha version of LIB$TPARSEt .endc          ON_ERR  ERR_EXIT ; 7 ; First, check if we are zeroing-out the cpu or memory.  ;b         MOVQ    LOG_DEV_DESC,R6.8         CMPC3   R6,(R7),CPU_STG         ; Is it the cpu?         BNEQ    20$s         BRW DO_CPU   20$:;         CMPC3   R6,(R7),MEM_STG         ; Is it the memory?e         BNEQ    40$e         BRW DO_MEM 40$:     ;cD ; Get the physical device name, and see if this device has an owner. ;m         $GETDVI_S -pG                 DEVNAM=LOG_DEV_DESC,-   ; Command line has device name.0$                 ITMLST=DEV_ITEM_LIST         ON_ERR  ERR_EXIT  @         CMPL    #DC$_TERM,DEV_CLASS     ; Did we get a terminal?         BNEQ    50$rC         $GETDVI_S -                     ; Yes, make sure we get the ?             DEVNAM=LOG_DEV_DESC,-       ; physical device name.t             ITMLST=TT_ITEM_LIST          ON_ERR  ERR_EXIT   50$:         TSTL    PID-         BEQL    60$-H         TSTL    OVERRIDE                ; Device is allocated, see if we9         BGTR    60$                     ; should proceed.pH         MOVL    #SS$_DEVALLOC,R0        ; Device is allocated, exit with0         BRW     ERR_EXIT                ; error. 60$:   DO_DEV: E         $CMKRNL_S -                     ; Enter k-mode to zero device/ error 0                 ROUTIN=ZERO_DEV,-       ; count.                 ARGLST=K_ARG         ON_ERR  ERR_EXIT         BRW     EXIT   DO_CPU:lH         $CMKRNL_S -                     ; Enter k-mode to zero cpu error count.             ROUTIN=ZERO_CPU          ON_ERR  ERR_EXIT         BRW     EXIT   DO_MEM:,E         $CMKRNL_S -                     ; Enter k-mode to zero memory  errorr0                 ROUTIN=ZERO_MEM         ; count.         ON_ERR  ERR_EXIT         BRW     EXIT  	 ERR_EXIT:-B         $EXIT_S R0                      ; Return the error, if any   EXIT:D9         RET                             ; Return normally-            .SBTTL  ZERO_DEV Routine ;++3 ;2 ; Functional Description: 9 ;   This routine zeros out the error count in the UCB for9 ;   a specified device.o ;h ; Calling Sequence:a* ;   $CMKRNL_S ROUTIN=ZERO_DEV,ARGLST=K_ARG ;t; ;       where K_ARG is an argument list. This list containsb; ;       the number of arguments passes (always 1), followeda; ;       by the address of a descriptor pointing to the name. ;       of a device. ;d ; Formal Parameters:$ ;   Descriptor for name of a device. ;f ; Implicit Inputs: ;   I/O database.  ;a ; Implicit Outputs:e& ;   Device error count is set to zero. ;  ; Completion Status: ;   Returned in R0.  ;  ; Side Effects:sC ;   I/O database is locked (routine runs in kernel mode at elevatede	 ;   IPL).w ;b ;--i    "         .ENTRY  ZERO_DEV,^M<R2,R4>  F         MOVL    G^CTL$GL_PCB,R4         ;; Our PCB address is input to SCH 4                                         ;; routines.A         JSB G^SCH$IOLOCKW               ;; Lock the I/O database.l  B         MOVL    4(AP),R1                ;;; Address of device name descriptor.tF         JSB     G^IOC$SEARCHDEV         ;;; Get UCB address for device into R1.         ON_ERR  ZERO_DEV_EXITs  D         TSTL    UCB$L_PID(R1)           ;;; Make sure device did not become6         BEQL    80$                     ;;; allocated.G         TSTL    OVERRIDE                ;;; Device is allocated, see ifM we;         BGTR    80$                     ;;; should proceed.R          MOVL    #SS$_DEVALLOC,R0         BRW ZERO_DEV_EXITn 80$:>         MOVL    #SS$_NORMAL,R0          ; Set a success status   .if df  DEV$V_MPDEV_MEMBERH         BBS #DEV$V_MPDEV_MEMBER,UCB$L_DEVCHAR(R1),90$ ; Multipath device ?R .endcW   .if df  ucb$w_errcntE         CLRW    UCB$W_ERRCNT(R1)        ;;; Zero out the error count.h .iffE         CLRL    UCB$L_ERRCNT(R1)        ;;; Zero out the error count.p Alphai .endc/  )         BRW ZERO_DEV_EXIT               ;t   .if df  DEV$V_MPDEV_MEMBERE 90$:                                    ; We have a multipath  devices  7         MOVL    UCB$PS_SUD(R1),R4       ; R4 is our SUDaG         BEQL    ZERO_DEV_EXIT           ; Should never occur, but checkt anyway.         MOVL    SUD$PS_MPDEV_PRIMARY_UCB(R4),-D                 R1                      ; Start with the primary UCBG         BEQL    ZERO_DEV_EXIT           ; Should never occur, but check  anywayG         CLRL    UCB$L_ERRCNT(R1)        ; Zero the error count, primary  path.c: 100$:   MOVL    UCB$PS_SUD(R1),R4       ; Get the next SUD6         BEQL    ZERO_DEV_EXIT           ; Exit if zero+         MOVL    SUD$PS_MPDEV_NEXT_UCB(R4),--:                 R1                      ; Get the next UCB<         BEQL    ZERO_DEV_EXIT           ; Exit if zero, done@         CLRL    UCB$L_ERRCNT(R1)        ; Clear the error count, secondaries.B         BRB 100$                        ; Go check for next device .endce ZERO_DEV_EXIT:<         PUSHL   R0                      ;;; Remember status.E         JSB     G^SCH$IOUNLOCK          ;;; Unlock I/O database (drop  IPL).y         POPL    R0           RETa    =         .ENTRY  CLR_OV,^M<>     ;;; Move to the code PSECT ##t         CLRL    OVERRIDE         MOVL    #SS$_NORMAL,R0         RETm        +         .SBTTL  ZERO_CPU, ZERO_MEM RoutinesX ;++t ;E ;  Functional Description:A ;   Routines to zero-out error-count location for cpu and memory.  ;r ;  Calling Sequence: ;   $CMKRNL_S ROUTIN=ZERO_CPUn ;   $CMKRNL_S ROUTIN=ZERO_MEM- ;- ;  Input Parameters:	 ;   None.r ;0 ;  Output Parameters:b	 ;   None.a ;b ;  Implicit Inputs:.8 ;   Global sysmbols, EXE$GL_MCHKERRS for cpu errors, and% ;   EXE$GL_MEMERRS for memory errors.  ;h ;  Implicit Outputs:	 ;   None.5 ;2 ;  Procedures called:a	 ;   None.w ;h ;  Completion Status: & ;   Returned in R0, always successful. ;  ;  Side Effects:	 ;   None.9 ;2 ;--6           .ENTRY  ZERO_CPU,^M<>P:         CLRL    EXE$GL_MCHKERRS     ; Zero out cpu errors.         MOVL    #SS$_NORMAL,R0         RET            .ENTRY  ZERO_MEM,^M<> =         CLRL    EXE$GL_MEMERRS      ; Zero out memory errors.e         MOVL    #SS$_NORMAL,R0         RETl           .END    ZDEC   --  D 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: Fri, 5 Oct 2001 17:12:12 -0400  From: norm.raphael@jamesbury.com) Subject: Re: Reset error account on Alpha-4 Message-ID: <C2256ADC.007432F5.00@jklh21.valmet.com>  * Won't link on VAX as /SYSEXE not VAX valid ================ $ link zdece& %LINK-W-NUDFSYMS, 6 undefined symbols:" %LINK-I-UDFSYM,         CTL$GL_PCB' %LINK-I-UDFSYM,         EXE$GL_MCHKERRSr& %LINK-I-UDFSYM,         EXE$GL_MEMERRS% %LINK-I-UDFSYM,         IOC$SEARCHDEVf# %LINK-I-UDFSYM,         SCH$IOLOCKWd$ %LINK-I-UDFSYM,         SCH$IOUNLOCK8 %LINK-W-USEUNDEF, undefined symbol CTL$GL_PCB referenced,         in psect ZDEC_CODE offset %X000001580         in module ZDEC file ddcu:[dir]ZDEC.OBJ;19 %LINK-W-USEUNDEF, undefined symbol SCH$IOLOCKW referenced ,         in psect ZDEC_CODE offset %X0000015F0         in module ZDEC file ddcu:[dir]ZDEC.OBJ;1; %LINK-W-USEUNDEF, undefined symbol IOC$SEARCHDEV referencede,         in psect ZDEC_CODE offset %X000001690         in module ZDEC file ddcu:[dir]ZDEC.OBJ;1: %LINK-W-USEUNDEF, undefined symbol SCH$IOUNLOCK referenced,         in psect ZDEC_CODE offset %X000001980         in module ZDEC file ddcu:[dir]ZDEC.OBJ;1= %LINK-W-USEUNDEF, undefined symbol EXE$GL_MCHKERRS referenceda,         in psect ZDEC_CODE offset %X000001B00         in module ZDEC file ddcu:[dir]ZDEC.OBJ;1< %LINK-W-USEUNDEF, undefined symbol EXE$GL_MEMERRS referenced,         in psect ZDEC_CODE offset %X000001BC0         in module ZDEC file ddcu:[dir]ZDEC.OBJ;1 $ link zdec/sysexeO %DCL-W-IVQUAL, unrecognized qualifier - check validity, spelling, and placementf	  \SYSEXE\  $s ===============0        2 jilly@clarityconnect.com on 10/05/2001 02:32:14 PM  * Please respond to jilly@clarityconnect.com   To:   Info-VAX@mvb.saic.com  cc:p* Subject:  Re: Reset error account on Alpha        9 ;Fixed to work on VAX as well as pre 7.2-1 Alpha systems.:  (     .TITLE  ZDEC Zero Device Error Count     .IDENT  /1.2/  ;++n ;  ; Title:+ ;   ZDEC.MAR - Zero-out device error count.W ;n
 ; Version:	 ;   1-003p ;a ; Facility:s ;   System Management Tools. ;I ; Abstract:t? ;   This program zeros-out the device error count stored in thet= ;   UCB for a particular device. This is useful when you wish>1 ;   reset this value without booting the machine.o ;r3 ;   THIS PROGRAM IS UNSUPPORTED AND PROVIDED AS IS,s ;   USE AT OWN RISK. ;c ;   Building sequence: ;  ;       $ macro/list zdecf# ;       $ link/map/full/sysexe zdeca ;  ;   Calling sequence:n ;n$ ;       $ ZDEC := $mydev:[mydir]ZDEC" ;       $ ZDEC [/OVERRIDE]  device ;t ; Environment:? ;   CMKRNL privilege required, I/O data base is locked, program| ;   executed at elevated IPL.  ; 	 ; Author:s7 ;   Mark Oakley DuPont Experimental Station 12-Nov-1984 : ;   This program is based upon the VARY program written by* ;   Gary Grebus of Battelle Columbus Labs. ;t ; Modifications: ;hH ;  17-Nov-1984  Mark Oakley Added /OVERRIDE to handle allocated devices. ;AA ;  25-Nov-1985  Mark Oakley Modified to correctly secure physicali terminal@ ;               name that is associated with a virutal terminal. ; G ;  23-May-1986  Mark Oakley Modified to zero-out CPU and memory errors.y ;m? ;  14-Jul-1988  Ted Nieland     Modified to work under VMS 5.0.t ;dF ;  15-Jul-2001  Paul Gallo  Compaq Computer Corporation, CSC, Colorado ;u9 ;               Modified to work under OpenVMS Alpha 7.x.t ;mF ;  19-Jul-2001  Paul Gallo  Compaq Computer Corporation, CSC, Colorado ; 6 ;               Modified to return errors to the user. ;rF ;  20-Jul-2001  Paul Gallo  Compaq Computer Corporation, CSC, Colorado ;e= ;               Modified for multipath devices, as we need toO< ;               clear the errors on each device in the path. ;e ;--O    %         .SBTTL  Symbols, Macros, Datad  1         .LIBRARY            /SYS$LIBRARY:LIB.MLB/u  =         $TPADEF                     ; Symbols for LIB$TPARSE. @         $SSDEF                      ; Symbols for return status.=         $UCBDEF                     ; Symbols for device ucb.eB         $STSDEF                     ; Symbols for returned status.8         $DEVDEF                     ; Symbols for device characteristics.B         $DVIDEF                     ; Symbols for $GETDVI service.>         $DCDEF                      ; Symbols for device type. if df  DEV$V_MPDEV_SECONDARYH         $MPDEVDEF                   ; Symbols for multipath information. endc ;e ; Macro to handle return codes.  ; #         .MACRO  ON_ERR  THERE,?HEREe         BLBS    R0,HERE1         BRW THEREl HERE:   .ENDM   ON_ERR  3         .PSECT  ZDEC_DATA,RD,WRT,NOEXE,LONG,SHR,PIC   B CMD_BUF:                            ; Buffer to hold command line.         .BLKB   80 CMD_BUF_SIZ = . - CMD_BUF   A CMD_BUF_DESC:                       ; Descriptor to command line.          .LONG    CMD_BUF_SIZ         .ADDRESS CMD_BUF   PROMPT:          .ASCID  /Device: /  A PARSE_BLK:                          ; Parse block for LIB$TPARSE.T         .LONG   TPA$K_COUNT0G         .LONG   TPA$M_ABBREV        ; Permit unambiguous abbreviations.          .BLKB   TPA$K_LENGTH0-8   D OVERRIDE:                           ; Zero out allocated devices, if set.         .LONG   0e  F LOG_DEV_DESC:                       ; Descriptor for device on command line.e         .BLKQ   1D  E CPU_STG:                            ; Used to compare against command 
 line parm.         .ASCII  /CPU/e  E MEM_STG:                            ; Used to compare against command 
 line parm.         .ASCII  /MEMORY/    A DEV_BUF:                            ; Buffer to hold device name.          .BLKB   40 DEV_BUF_SIZ = . - DEV_BUF   C DEV_BUF_DESC:                       ; Descriptor pointing to device, name.N         .LONG    DEV_BUF_SIZ         .ADDRESS DEV_BUF  ? PID:                                ; Owner of device (if any).          .BLKL   1_  > DEV_ITEM_LIST:                      ; Device list for $GETDVI.D         .WORD    DEV_BUF_SIZ        ; Make sure we a have a physical device name.v         .WORD    DVI$_DEVNAM         .ADDRESS DEV_BUF         .ADDRESS DEV_BUF_DESCLD         .WORD    4                  ; See if someone has this device
 allocated.         .WORD    DVI$_PID          .ADDRESS PID         .LONG    0         .WORD    4;         .WORD    DVI$_DEVCLASS      ; Check for a terminal.E         .ADDRESS DEV_CLASS         .LONG    07         .LONG    0                  ; End if item list.   F TT_ITEM_LIST:                       ; Item list if we have a terminal.D         .WORD    DEV_BUF_SIZ        ; Make sure we a have a physical device name.s"         .WORD    DVI$_TT_PHYDEVNAM         .ADDRESS DEV_BUF         .ADDRESS DEV_BUF_DESCu         .LONG    0  
 DEV_CLASS:         .LONG   1U  C K_ARG:                              ; Argument list for kernel-moder routine.8         .LONG    1                  ; Just one argument.F         .ADDRESS DEV_BUF_DESC       ; Pass descriptor for device name.             .SBTTL  State Table 5         .PSECT  ZDEC_STATES,RD,NOWRT,EXE,LONG,SHR,PIC   )         $INIT_STATE STATE_TABLE,KEY_TABLE            $STATE  STARTh         $TRAN   '/',QUAL.         $TRAN   TPA$_SYMBOL,DEV,,,LOG_DEV_DESC"         $TRAN   TPA$_EOS,TPA$_EXIT           $STATE  DEV "         $TRAN   TPA$_EOS,TPA$_EXIT         $TRAN   '/',QUAL         $TRAN   ':',COLON            $STATE  COLON          $TRAN   '/',QUAL"         $TRAN   TPA$_EOS,TPA$_EXIT           $STATE  QUAL'         $TRAN   'OVERRIDE',,,1,OVERRIDE $         $TRAN   'NOOVERRIDE',,CLR_OV           $STATE.         $TRAN   TPA$_SYMBOL,DEV,,,LOG_DEV_DESC"         $TRAN   TPA$_EOS,TPA$_EXIT           $END_STATE                 .SBTTL  Main program3         .PSECT  ZDEC_CODE,RD,NOWRT,EXE,LONG,SHR,PICI0         .ENTRY  ZDEC,^M<R2,R3,R4,R5,R6,R7,R8,R9>   ;E ; Get the command line.  ;N8         PUSHAL  CMD_BUF_DESC            ; Return length.A         PUSHAL  PROMPT                  ; Prompt for device name. =         PUSHAL  CMD_BUF_DESC            ; Place to hold line. $         CALLS   #3,G^LIB$GET_FOREIGN         ON_ERR  ERR_EXIT  ?         PUSHAL  CMD_BUF_DESC            ; Upper case the input.W         PUSHAL  CMD_BUF_DESC         CALLS   #2,G^STR$UPCASEL         ON_ERR  ERR_EXIT  H         MOVL    CMD_BUF_DESC,-          ; Set length of string to parse.)                 PARSE_BLK+TPA$L_STRINGCNT B         MOVL    CMD_BUF_DESC+4,-        ; Set address of string to parse.)                 PARSE_BLK+TPA$L_STRINGPTRSD         PUSHAL  KEY_TABLE               ; Parse the command line for?         PUSHAL  STATE_TABLE             ; qualifier and device.R         PUSHAL  PARSE_BLKE3 if ndf  TPA$Q_NUMBER                   ; Not on VAX$         CALLS   #3,G^LIB$TPARSE  iffAE         CALLS   #3,G^LIB$TABLE_PARSE    ; Alpha version of LIB$TPARSEa endc         ON_ERR  ERR_EXIT ;D7 ; First, check if we are zeroing-out the cpu or memory.R ;4         MOVQ    LOG_DEV_DESC,R6 8         CMPC3   R6,(R7),CPU_STG         ; Is it the cpu?         BNEQ    20$          BRW DO_CPU   20$:;         CMPC3   R6,(R7),MEM_STG         ; Is it the memory?_         BNEQ    40$c         BRW DO_MEM 40$:     ; D ; Get the physical device name, and see if this device has an owner. ;_         $GETDVI_S -eG                 DEVNAM=LOG_DEV_DESC,-   ; Command line has device name.R$                 ITMLST=DEV_ITEM_LIST         ON_ERR  ERR_EXIT  @         CMPL    #DC$_TERM,DEV_CLASS     ; Did we get a terminal?         BNEQ    50$aC         $GETDVI_S -                     ; Yes, make sure we get the ?             DEVNAM=LOG_DEV_DESC,-       ; physical device name.L             ITMLST=TT_ITEM_LIST          ON_ERR  ERR_EXIT   50$:         TSTL    PID          BEQL    60$ H         TSTL    OVERRIDE                ; Device is allocated, see if we9         BGTR    60$                     ; should proceed. H         MOVL    #SS$_DEVALLOC,R0        ; Device is allocated, exit with0         BRW     ERR_EXIT                ; error. 60$:   DO_DEV:oE         $CMKRNL_S -                     ; Enter k-mode to zero deviceM error60                 ROUTIN=ZERO_DEV,-       ; count.                 ARGLST=K_ARG         ON_ERR  ERR_EXIT         BRW     EXIT   DO_CPU:hH         $CMKRNL_S -                     ; Enter k-mode to zero cpu error count.             ROUTIN=ZERO_CPUt         ON_ERR  ERR_EXIT         BRW     EXIT   DO_MEM: E         $CMKRNL_S -                     ; Enter k-mode to zero memory  error 0                 ROUTIN=ZERO_MEM         ; count.         ON_ERR  ERR_EXIT         BRW     EXIT  	 ERR_EXIT:iB         $EXIT_S R0                      ; Return the error, if any   EXIT:k9         RET                             ; Return normally             .SBTTL  ZERO_DEV Routine ;++L ;T ; Functional Description:R9 ;   This routine zeros out the error count in the UCB for0 ;   a specified device.I ;  ; Calling Sequence:e* ;   $CMKRNL_S ROUTIN=ZERO_DEV,ARGLST=K_ARG ; ; ;       where K_ARG is an argument list. This list containsV; ;       the number of arguments passes (always 1), followed ; ;       by the address of a descriptor pointing to the name  ;       of a device. ;  ; Formal Parameters:$ ;   Descriptor for name of a device. ;  ; Implicit Inputs: ;   I/O database.  ;  ; Implicit Outputs: & ;   Device error count is set to zero. ;T ; Completion Status: ;   Returned in R0.  ;  ; Side Effects:oC ;   I/O database is locked (routine runs in kernel mode at elevatedN	 ;   IPL).X ;  ;--     "         .ENTRY  ZERO_DEV,^M<R2,R4>  F         MOVL    G^CTL$GL_PCB,R4         ;; Our PCB address is input to SCH 4                                         ;; routines.A         JSB G^SCH$IOLOCKW               ;; Lock the I/O database.   B         MOVL    4(AP),R1                ;;; Address of device name descriptor. F         JSB     G^IOC$SEARCHDEV         ;;; Get UCB address for device into R1.         ON_ERR  ZERO_DEV_EXITs  D         TSTL    UCB$L_PID(R1)           ;;; Make sure device did not become6         BEQL    80$                     ;;; allocated.G         TSTL    OVERRIDE                ;;; Device is allocated, see ifn we;         BGTR    80$                     ;;; should proceed.           MOVL    #SS$_DEVALLOC,R0         BRW ZERO_DEV_EXIT  80$:>         MOVL    #SS$_NORMAL,R0          ; Set a success status   if df  DEV$V_MPDEV_MEMBERtH         BBS #DEV$V_MPDEV_MEMBER,UCB$L_DEVCHAR(R1),90$ ; Multipath device ?t endc   if df  ucb$w_errcnteE         CLRW    UCB$W_ERRCNT(R1)        ;;; Zero out the error count.a iff E         CLRL    UCB$L_ERRCNT(R1)        ;;; Zero out the error count.  Alpha  endc  )         BRW ZERO_DEV_EXIT               ;^   if df  DEV$V_MPDEV_MEMBERPE 90$:                                    ; We have a multipath  device;  7         MOVL    UCB$PS_SUD(R1),R4       ; R4 is our SUD G         BEQL    ZERO_DEV_EXIT           ; Should never occur, but check  anyway.         MOVL    SUD$PS_MPDEV_PRIMARY_UCB(R4),-D                 R1                      ; Start with the primary UCBG         BEQL    ZERO_DEV_EXIT           ; Should never occur, but check  anywayG         CLRL    UCB$L_ERRCNT(R1)        ; Zero the error count, primary  path.S: 100$:   MOVL    UCB$PS_SUD(R1),R4       ; Get the next SUD6         BEQL    ZERO_DEV_EXIT           ; Exit if zero+         MOVL    SUD$PS_MPDEV_NEXT_UCB(R4),-0:                 R1                      ; Get the next UCB<         BEQL    ZERO_DEV_EXIT           ; Exit if zero, done@         CLRL    UCB$L_ERRCNT(R1)        ; Clear the error count, secondaries.B         BRB 100$                        ; Go check for next device endc ZERO_DEV_EXIT:<         PUSHL   R0                      ;;; Remember status.E         JSB     G^SCH$IOUNLOCK          ;;; Unlock I/O database (dropD IPL).          POPL    R0           RETP    =         .ENTRY  CLR_OV,^M<>     ;;; Move to the code PSECT ##t         CLRL    OVERRIDE         MOVL    #SS$_NORMAL,R0         RETU        +         .SBTTL  ZERO_CPU, ZERO_MEM Routinesn ;++o ;r ;  Functional Description:A ;   Routines to zero-out error-count location for cpu and memory.  ;  ;  Calling Sequence: ;   $CMKRNL_S ROUTIN=ZERO_CPU  ;   $CMKRNL_S ROUTIN=ZERO_MEMu ;n ;  Input Parameters:	 ;   None.  ;  ;  Output Parameters:R	 ;   None.  ;o ;  Implicit Inputs:m8 ;   Global sysmbols, EXE$GL_MCHKERRS for cpu errors, and% ;   EXE$GL_MEMERRS for memory errors.V ;I ;  Implicit Outputs:	 ;   None.  ;O ;  Procedures called:_	 ;   None.  ;  ;  Completion Status: & ;   Returned in R0, always successful. ;L ;  Side Effects:	 ;   None.  ;t ;--e           .ENTRY  ZERO_CPU,^M<>R:         CLRL    EXE$GL_MCHKERRS     ; Zero out cpu errors.         MOVL    #SS$_NORMAL,R0         RETk           .ENTRY  ZERO_MEM,^M<>V=         CLRL    EXE$GL_MEMERRS      ; Zero out memory errors.a         MOVL    #SS$_NORMAL,R0         RET            .END    ZDEC   --H Jilly     - Working from Home in the Chemung River Valley - Lockwood, NY@      - jilly@clarityconnect.com               - Brett Bodine fan;      - Mark.Jilson@Compaq.com            - since 1975 or so 0      - http://www.jilly.baka.com               -   ------------------------------  # Date: Fri, 05 Oct 2001 21:33:01 GMTo2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)) Subject: Re: Reset error account on AlphaT/ Message-ID: <hGpv7.46$RL6.139@news.cpqcorp.net>r  W In article <C2256ADC.007432F5.00@jklh21.valmet.com>, norm.raphael@jamesbury.com writes:E  + :Won't link on VAX as /SYSEXE not VAX validM  H   LINK/SYSEXE on OpenVMS Alpha is equivalent to a LINK that includes theE   system symbol table (+SYS$SYSTEM:SYS.STB/SELECTIVE) on OpenVMS VAX.     $ $ ARCH_TYPE = F$GETSYI("ARCH_TYPE") & $ IF ARCH_TYPE .EQ. 1  ! VAX type code $ Then, $   LINK ZDEC + SYS$SYSTEM:SYS.STB/SELECTIVE $ EndIfo( $ IF ARCH_TYPE .EQ. 2  ! Alpha type code $ Then $   LINK /SYSEXE ZDECE $ EndIfO+ $ IF ARCH_TYPE .EQ. 3  ! Itanium type code?  $ ThenH $   write sys$output "this code has not been checked on OpenVMS Itanium" $ EndIf     N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  $ Date: Fri, 5 Oct 2001 18:00:39 -0400  From: norm.raphael@jamesbury.com) Subject: Re: Reset error account on AlphaX4 Message-ID: <C2256ADC.00789F53.00@jklh21.valmet.com>  ) Thanks.  I'll update the comments within.         7 hoffman@xdelta.zko.dec.nospam on 10/05/2001 05:33:01 PM-  / Please respond to hoffman@xdelta.zko.dec.nospam    To:   Info-VAX@mvb.saic.comS cc: * Subject:  Re: Reset error account on Alpha        O In article <C2256ADC.007432F5.00@jklh21.valmet.com>, norm.raphael@jamesbury.comZ writes:o  + :Won't link on VAX as /SYSEXE not VAX validd  H   LINK/SYSEXE on OpenVMS Alpha is equivalent to a LINK that includes theE   system symbol table (+SYS$SYSTEM:SYS.STB/SELECTIVE) on OpenVMS VAX.C    # $ ARCH_TYPE = F$GETSYI("ARCH_TYPE")D& $ IF ARCH_TYPE .EQ. 1  ! VAX type code $ Then, $   LINK ZDEC + SYS$SYSTEM:SYS.STB/SELECTIVE $ EndIfn( $ IF ARCH_TYPE .EQ. 2  ! Alpha type code $ Then $   LINK /SYSEXE ZDECl $ EndIfL+ $ IF ARCH_TYPE .EQ. 3  ! Itanium type code?f $ ThenH $   write sys$output "this code has not been checked on OpenVMS Itanium" $ EndIfe    N  ---------------------------- #include <rtfaq.h> -----------------------------J       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.comN  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  # Date: Fri, 05 Oct 2001 18:20:09 GMTf2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)R Subject: Re: V7.3 XFC Crash (was: Re: [VMS V7.3 Alpha] my first crash since months. Message-ID: <tRmv7.20$RL6.64@news.cpqcorp.net>  W In article <3bbcdf72$1@news.kapsch.co.at>, eplan@kapsch.net (Peter LANGSTOEGER) writes:AN :Does it indicate a hardware problem or is it one of the said problems related3 :to the new XFC (as SDA>SHOW CRASH also pretends) ?r :c" :Current Operating Stack (KERNEL):R :                       00000000.7B08D200    FFFFFFFF.831C3360  CACHE$IOPOST+00020C :                       00000000.7B08D208    00000000.811F5B80  PCBlQ :                       00000000.7B08D210    FFFFFFFF.802F5F80  SYS$XFCACHE+1DF80m> :                       00000000.7B08D218    00000000.7B08D220R :                SP =>  00000000.7B08D220    FFFFFFFF.831C33F8  CACHE$IOPOST+000B8> :                       00000000.7B08D228    00000000.7B08D262> :                       00000000.7B08D230    00000000.7B08D26E> :                       00000000.7B08D238    00000000.7B08D26C> :                       00000000.7B08D240    00000000.7B08D266> :                       00000000.7B08D248    FFFFFFFF.81293650Q :                       00000000.7B08D250    FFFFFFFF.000005B4  BUG$_XQPERR+00004aV :                       00000000.7B08D258    FFFFFFFF.802F0EF8  CACHE$TRUNCATE_C+00188N :                       00000000.7B08D260    FFFFFFFF.831C38E8  CACHE$TRUNCATE ..    H   There are crashes found in XFC configurations in V7.3, both when using3   the base XFC and when using the XFC V1.0 ECO kit.6  J   Switch to VIOC caching prior to the availability of the XFC V2.0 ECO kitH   for OpenVMS V7.3, using the VCC_FLAGS system parameter.  (Some detailsD   are covered in the CETS2001 OpenVMS Hints and Kinks presentation.)  N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Fri, 05 Oct 2001 17:20:10 -0400-2 From: norm lastovica <norman.lastovica@oracle.com> Subject: Re: VMS 5.4 supported?B* Message-ID: <3BBE240A.A2F248BD@oracle.com>  < I don't believe that vms v5.4 is supported at all.  VMS V7.3G is the current supported VMS version.  check out www.openvms.compaq.com  too.   Linda wrote: > E > I've inherited a Microvax 3100 that I know very little about.  It's G > not in my hands yet so the info I have is limited, but I believe it's.G > running VMS 5.4 and UCX (ver unknown).  Can anyone tell me if VMS 5.4 A > is still supported?  If not, what would be the most current andDF > supported level that can run on a 3100?  This is all new to me, so I/ > thank you in advance for your kind responses.l   -- n> norman lastovica / oracle rdb engineering / usa / 610.696.4685   ------------------------------  % Date: Fri, 05 Oct 2001 16:11:10 -0700 5 From: Christopher Jovais <cjovais@radiology.ucsf.edu>  Subject: WP 5.1+ Docsu2 Message-ID: <3BBE3E0D.B6BACFC3@radiology.ucsf.edu>   Hello,  = I have a Canadian friend who is looking for documentation fortH WordPerfect for OpenVMS V5.1+.  She needs the System Manager's Guide andH the Reference manual in particular but if you have more she'll take thatD as well.  Anyone have and wish to unload some old documentation?  Of! course she'll pay for shipping...e   Best.b   ------------------------------  # Date: Sat, 06 Oct 2001 00:25:06 GMT = From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-)  Subject: Re: WP 5.1+ Docs_0 Message-ID: <00A03164.492E7AB9@SendSpamHere.ORG>  j In article <3BBE3E0D.B6BACFC3@radiology.ucsf.edu>, Christopher Jovais <cjovais@radiology.ucsf.edu> writes: >Hello,e >r> >I have a Canadian friend who is looking for documentation forI >WordPerfect for OpenVMS V5.1+.  She needs the System Manager's Guide and I >the Reference manual in particular but if you have more she'll take that E >as well.  Anyone have and wish to unload some old documentation?  Of " >course she'll pay for shipping... >c >Best.    G Why doesn't she just contact the folks responsible for WordPerfect for  ? OpenVMS and ask them for the documentation she'd like or needs?    --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COMD             J   "And of course, I'm a genius, so people are naturally drawn to my fiery I   intellect.  Their admiration overwhelms their envy!" -- Calvin & HobbesW   ------------------------------   End of INFO-VAX 2001.555 ************************