1 INFO-VAX	Wed, 11 Apr 2001	Volume 2001 : Issue 202       Contents: Re: 3rd party memory products  Re: 3rd party memory products  Re: 3rd party memory products  Re: 3rd party memory products  Re: Another Win for OpenVMS  Re: Another Win for OpenVMS  basic + Re: CI based cluster for max I/O perf. How? + Re: CI based cluster for max I/O perf. How? + RE: CI based cluster for max I/O perf. How? + RE: CI based cluster for max I/O perf. How? + RE: CI based cluster for max I/O perf. How?  Re: Compaq & VMS Careers Re: Compaq & VMS Careers Re: Compaq & VMS Careers Re: Compaq & VMS Careers Re: Compaq & VMS Careers Re: Corba on OpenVMS AXP Re: Corba on OpenVMS AXP Directory lexical functions  Re: Directory lexical functions  Re: Directory lexical functions  Re: Directory lexical functions  Re: Directory lexical functions # Re: error installing patch on vax?? # Re: error installing patch on vax?? # Re: error installing patch on vax??  Free Travel and Bizz Opp!  Re: FTP hijacking of VMS sites0 Re: HELP: Problem in DEC BASIC reading IP Socket0 Re: HELP: Problem in DEC BASIC reading IP Socket0 Re: HELP: Problem in DEC BASIC reading IP Socket, How can I get the hardware-id number(newbie)0 Re: How can I get the hardware-id number(newbie)0 Re: How can I get the hardware-id number(newbie)0 Re: How can I get the hardware-id number(newbie)0 Re: How can I get the hardware-id number(newbie)0 Re: How can I get the hardware-id number(newbie)9 Re: How can I get the hardware-id number(newbie) Followup  How not to add patches& Invitation to join the WebSource group- Re: KZCCA Ultrawide SCSI Adapters for the VAX  KZPCA-AA Works fine !  Re: Macro VAX/Alpha ISDN Comms) Math offtopic (WAS: Compaq & VMS Careers) 2 OpenVMS Frequently Asked Questions (FAQ), Part 1/52 OpenVMS Frequently Asked Questions (FAQ), Part 2/52 OpenVMS Frequently Asked Questions (FAQ), Part 3/52 OpenVMS Frequently Asked Questions (FAQ), Part 4/52 OpenVMS Frequently Asked Questions (FAQ), Part 5/53 Re: Q: Converting a VAX 6000-420 to a VAX 6000-620? 3 Re: Q: Converting a VAX 6000-420 to a VAX 6000-620? 3 Re: Q: Converting a VAX 6000-420 to a VAX 6000-620?   Redundant Power Supply on DS20E?$ Re: Redundant Power Supply on DS20E? Sessions and CSWS  Re: Sessions and CSWS  Re: Status of EV7 3 strange behaviour of DIRECTORY with long file names 7 Re: strange behaviour of DIRECTORY with long file names 7 Re: strange behaviour of DIRECTORY with long file names 7 Re: strange behaviour of DIRECTORY with long file names 7 Re: strange behaviour of DIRECTORY with long file names 7 Re: strange behaviour of DIRECTORY with long file names 0 Surgeon Generals Warning- Awesome New Band  1399@ Surgeon Generals Warning- Awesome new band from Cincinnati  1231# TCP/IP 5.0A/ECO 2 FTP "425" Failure  Re: VMS friendly website???  Re: VMS friendly website???  Re: VMS friendly website???  Re: VMS friendly website???  Re: VMS friendly website??? < Why set PYHSICALPAGES? (was: [Q] Adding Memory to a MV 3100)@ Re: Why set PYHSICALPAGES? (was: [Q] Adding Memory to a MV 3100)@ Re: Why set PYHSICALPAGES? (was: [Q] Adding Memory to a MV 3100)  F ----------------------------------------------------------------------  # Date: Tue, 10 Apr 2001 22:12:52 GMT  From: Dirk Munk <munk@home.nl>& Subject: Re: 3rd party memory products' Message-ID: <3AD38563.568D0C48@home.nl>    Tim Llewellyn wrote:   > john nixon wrote:  > L > > Lifetime guarantee with overnite replacement, and Dataram will pay "techN > > time" for replacing it.  Our maintenance contract is with Compaq, and theyE > > are obviously not going to be happy about using 3rd party memory.  > D > you should ask them anyway. I have some dim recollection of Compaq) > agreeing to support some 3rd party RAM.   N That was the case untill may last year. Then Compaq decided that it was not inN their business interest to do this anymore. Doesn't mean Dataram and CamintonnO memory is bad though. It's still excellent stuff, but a bit to cheap for Compaq  :-))       >  >  >  -- 8 > Tim Llewellyn, OpenVMS Infrastructure, Remarcs Project2 > MedAS at the BBC, Whiteladies Road, Bristol, UK.C > Email tim.llewellyn@bbc.co.uk. Home tim.llewellyn@cableinet.co.uk  > C > I speak for myself only and my views in no way represent those of  > MedAS or the BBC.    ------------------------------  # Date: Tue, 10 Apr 2001 22:24:52 GMT  From: Dirk Munk <munk@home.nl>& Subject: Re: 3rd party memory products' Message-ID: <3AD387FE.B13348BC@home.nl>    john nixon wrote:   M > I buy VMS systems because VMS is reliable.  With that in mind, I don't want M > to risk my data integrity by scrimping on memory.  However, paying a factor 5 > of 12 times more for Compaq memory seems excessive.  > L > A 4GB memory option from Compaq for an ES40 costs over $51,000.  I can buyM > similar memory from DataRam for about 1/12th of that.  Since I need four of H > these 4GB options, that adds up to a whole lot of money.  If I buy theL > DataRam memory, I can buy a 4GB option or two for spares.  Can anyone giveK > me any logical reasons for not doing this?  I have very little experience I > with 3rd party memory in Alpha VMS systems.   It seems 3rd party memory K > prices have come down a lot recently, but not Compaq's.  Is Compaq so big J > and slow that they cannot react to market conditions?  If so, that would > explain a lot.  I Compaq doesn't make their own memory modules , but has them made by other O suppliers. We have opted for 4GB Camintonn modules in our ES40's (1 GB dimm's). M They use IBM memory chips, and I suppose we can trust IBM to make good chips. N Camintonn also has lifetime warrenty. At the time we paid about a third of theO Compaq price. I would not go for Kingston, I think the quality of Camintonn and K most likely Dataram too is more consistent and aimed at the high end market : than is the case with Kingston. But this is just my guess.   ------------------------------  # Date: Wed, 11 Apr 2001 00:19:28 GMT / From: StevenU@POBoxes.com (Steven P. Underwood) & Subject: Re: 3rd party memory products2 Message-ID: <3ad3a176.425177335@news.telocity.com>  F My Compaq service contract was renewed last May with Dataram memory inE our DEC 3000-400S Alpha, no questions asked.  We also have an Exabyte E tape drive on this machine.  Our MVII has CMD and Emulex controllers, E Exabyte tape drive and Seagate CMD 1.2GB hard drive.  These both have , gone through many upgrades before I arrived.  ? Our ES40, which was purchased last year, is all DEC^H^H^HCompaq  however.   Steve   A On Tue, 10 Apr 2001 22:12:52 GMT, Dirk Munk <munk@home.nl> wrote:    >  >  >Tim Llewellyn wrote:  >  >> john nixon wrote: >>M >> > Lifetime guarantee with overnite replacement, and Dataram will pay "tech O >> > time" for replacing it.  Our maintenance contract is with Compaq, and they F >> > are obviously not going to be happy about using 3rd party memory. >>E >> you should ask them anyway. I have some dim recollection of Compaq * >> agreeing to support some 3rd party RAM. > O >That was the case untill may last year. Then Compaq decided that it was not in O >their business interest to do this anymore. Doesn't mean Dataram and Camintonn P >memory is bad though. It's still excellent stuff, but a bit to cheap for Compaq >:-))  >  >  >  >> >> >>  --9 >> Tim Llewellyn, OpenVMS Infrastructure, Remarcs Project 3 >> MedAS at the BBC, Whiteladies Road, Bristol, UK. D >> Email tim.llewellyn@bbc.co.uk. Home tim.llewellyn@cableinet.co.uk >>D >> I speak for myself only and my views in no way represent those of >> MedAS or the BBC. >    Steven P. Underwood,DNRC Whitinsville,MA  StevenU@POBoxes.com    ------------------------------  # Date: Wed, 11 Apr 2001 00:21:07 GMT & From: thompson_n.o.s.p.a.m@athenet.net& Subject: Re: 3rd party memory products; Message-ID: <TrNA6.8544$9N5.435789@typhoon.mn.mediaone.net>   J Thus far I have had very good luck with my 4GB card.  I have a test serverI I can harvest a RAM board from in a pinch.  Disk cache software + Dataram  board = excellent performance.  % john nixon <jnixon@cfl.rr.com> wrote:   L : A 4GB memory option from Compaq for an ES40 costs over $51,000.  I can buyM : similar memory from DataRam for about 1/12th of that.  Since I need four of H : these 4GB options, that adds up to a whole lot of money.  If I buy theL : DataRam memory, I can buy a 4GB option or two for spares.  Can anyone give               --     ------------------------------  % Date: Tue, 10 Apr 2001 14:16:03 -0400 # From: Jim Agnew <Agnew@hsc.vcu.edu> $ Subject: Re: Another Win for OpenVMS+ Message-ID: <3AD34DE3.BC93094D@hsc.vcu.edu>   O Also for faster surfin', and to KILL ALL THE AD SITES..  see the following url.    http://www.smartin-designs.com/    the gist of it is to modify your c:\windows\hosts file to set the dns entries for the known ads and spammers to 0.0.0.0 and voila!!!   it makes my pc unstable, tho..  there is another ip address they use, but my pc then hangs while trying to resolve those..  however  on a faster machine...  ? go for it, while it was up my pc was rocket fast and cloaked...    jim   " Shane.F.Smith@Healthnet.com wrote: > J > As many know, I'm a privacy freak. Try www.grc.com as a good start pointH > for information on security and privacy on the net. It's a bit hard toM > navigate, but it's worth the effort. A lot of the best stuff is linked from J > there. www.junkbusters.com is pretty good for privacy news, too, despite > the name.  > L > For the PC surfers among us, check out the PC freeware package Zone Alarm,K > from www.zonelabs.com. It's a very good personal firewall that just about H > sets itself up, if your requirements don't include anything kinky. TheF > kinky stuff only takes a couple of working braincells. Not only doesH > nothing get in that I don't want, I know when something tries /and/ itJ > gives me the option of stopping programs on my machine that try to phone > home on a case by case basis.  > I > As for clearing out Netscape caches, remember all that does is mark the K > space the files took up as free, it doesn't wipe them out. They can still K > be recovered by an undelete utility, for example. I don't go as far as to M > wipe the blocks myself, but the truly paranoid would probably want to get a  > package that does that.  >  > Shane  > H > mathog@seqaxp.bio.caltech.edu (David Mathog) on 04/10/2001 07:46:18 AM > @ > Please respond to mathog@seqaxp.bio.caltech.edu (David Mathog) >  > To:   Info-VAX@Mvb.Saic.Com  > cc:  > ' > Subject:  Re: Another Win for OpenVMS  > K > In article <3ACDDB95.A8437865@hsc.vcu.edu>, Jim Agnew <Agnew@hsc.vcu.edu> 	 > writes: M > >and are you sure that your hard disk has not been read by every one on the < > >web????  ;-)  (i use netscape, and encrypt my checkbook..H > >i figure that's where they can do the most damage, and not be totally > paranoid.) > E > I don't keep any financial information on that computer - it's used K > essentially as a terminal.  Which should be safe enough.  Hmm, probably a G > good idea to clear out the Netscape caches after each session though.  > 
 > Regards, >  > David Mathog > mathog@seqaxp.bio.caltech.edu @ > Manager, sequence analysis facility, biology division, CaltechL > **************************************************************************L > *                                RIP VMS                                 *L > **************************************************************************   ------------------------------  % Date: Tue, 10 Apr 2001 17:37:31 -0500 1 From: "David J. Dachtera" <djesys.nospam@fsi.net> $ Subject: Re: Another Win for OpenVMS' Message-ID: <3AD38B2B.C5E62595@fsi.net>    "Terry C. Shannon" wrote:  > [snip]I > Ah, Netscape... the browser for crash test dummies. I used to use it on N > Windoze, but got sick of the multiple daily browser crashes and went over to@ > Internet Exploder. At least it is more reliable than Netscape.   In what reality?  D I've seen IE do stupid things that NS is too smart to even THINK of!  G ...like forgetting how to go back or forward because it forgot where it ; came from or where it had been but went back at my request.   D Then again, I've seen NS hose up WhineBloze so bad you couldn't even- shut it down (no big accomplishment, really).    --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/   F This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings is to be expected.  @ Feel free to exercise your rights of free speech and expression.  F However, attacks against individual posters, or groups of posters, are strongly discouraged.    ------------------------------  # Date: Tue, 10 Apr 2001 19:39:36 GMT % From: ramirez <ramirezr@sendlove.net>  Subject: basic8 Message-ID: <r4jg701g841hk89k6r5inff4bte5oq2u5a@4ax.com>  6 Does anyone have some 'basic' sample code of using the? lib$cvt_from_internal_time call that they are willing to share?    Thanks a million.    ------------------------------   Date: 10 Apr 2001 20:51:19 GMT' From: prosullivan@aol.com (PROSULLIVAN) 4 Subject: Re: CI based cluster for max I/O perf. How?: Message-ID: <20010410165119.09596.00002217@ng-fu1.aol.com>  N you'll be lucky. Aside from hardwware issues like size of controller cache andB the other favorite - is my battery working - , there are two major. configuration issues for  all controllers HSx.   1. Stripe or chunk size  2. MAX cache transfer size.   L EMC, for example, recommend a tiny stripe size to maximize stripe benefits. M Try playing with max cache transfer size - whack it down to 32 and watch your L disks get busy. Then use vtdpy (with the exportable data - NOT) to see which buses are being thrashed. L Note: with VMS you will need to check your disk cluster size - simple thingsJ like increasing that can reduce fragmentation and speed up IO accordingly.   ------------------------------  # Date: Wed, 11 Apr 2001 00:18:40 GMT & From: thompson_n.o.s.p.a.m@athenet.net4 Subject: Re: CI based cluster for max I/O perf. How?; Message-ID: <ApNA6.8543$9N5.435789@typhoon.mn.mediaone.net>   # I have had good luck with settings:   I MAXIMUM_HOSTS in HSJ to what my actual number of hosts are, CI_4K_PACKETS I and enabling the shadow assist (I can't recall close to the exact name on A this one) and HSJ50 on separate CIPCA & star coupler from HSJ40's   0 WRITEBACK & MAX_CACHED = 1024 on heavy hit disks3 tape drive on HSJ50 (did not have local bus choice)   7 This combination cut hours off my backup & merge times.   ? Most surprising to me the MAXIMUM_HOSTS setting made a very big  difference.    Paul   ------------------------------  % Date: Tue, 10 Apr 2001 20:58:39 -0500 + From: "Main, Kerry" <Kerry.Main@compaq.com> 4 Subject: RE: CI based cluster for max I/O perf. How?R Message-ID: <DC4745D1A85CA04180C83CDC706A9D180D94FD@cthexc02.americas.cpqcorp.net>   re: MAXIMUM_HOSTS   L If I recall correctly (from memory here), this parameter determines how manyL CI nodes will get polled on a regular basis. As an example if the default isJ 15, each polling period, it looks for nodes 0-15. If this parameter is set to 7, : then each polling period, it will only look for nodes 0-7.  G Beware, if I remember a watchout - if you add node 8 someday and forget 7 about this parameter set to 7, you will have problems..    Regards,  
 Kerry Main Senior Consultant  Compaq Canada Inc. Professional Services  Voice: 613-592-4660  Fax  :  819-772-7036 Email: Kerry.Main@Compaq.com     -----Original Message-----& From: thompson_n.o.s.p.a.m@athenet.net) [mailto:thompson_n.o.s.p.a.m@athenet.net]  Sent: April 10, 2001 8:19 PM To: Info-VAX@Mvb.Saic.Com 4 Subject: Re: CI based cluster for max I/O perf. How?    # I have had good luck with settings:   I MAXIMUM_HOSTS in HSJ to what my actual number of hosts are, CI_4K_PACKETS I and enabling the shadow assist (I can't recall close to the exact name on A this one) and HSJ50 on separate CIPCA & star coupler from HSJ40's   0 WRITEBACK & MAX_CACHED = 1024 on heavy hit disks3 tape drive on HSJ50 (did not have local bus choice)   7 This combination cut hours off my backup & merge times.   ? Most surprising to me the MAXIMUM_HOSTS setting made a very big  difference.    Paul   ------------------------------  + Date: Tue, 10 Apr 2001 21:21:53 -0500 (CDT)r/ From: Paul Thompson <thompson@mail.athenet.net>o4 Subject: RE: CI based cluster for max I/O perf. How?A Message-ID: <Pine.LNX.4.21.0104102121100.13622-100000@malacandra>   , Whoops, MAXHOSTS in HSJ was set to 2 then...  ) On Tue, 10 Apr 2001, Paul Thompson wrote:I   > 0 > This also worked with Alphas at nodes 12 & 13. >  >  -- b   ------------------------------  + Date: Tue, 10 Apr 2001 21:20:20 -0500 (CDT) / From: Paul Thompson <thompson@mail.athenet.net>e4 Subject: RE: CI based cluster for max I/O perf. How?A Message-ID: <Pine.LNX.4.21.0104102114270.13622-100000@malacandra>O  2 I have CI nodes 0,1,5,7 & 13 & MAX hosts set to 1.4 I have only one Alpha on the CI any more at node 13.. This also worked with Alphas at nodes 12 & 13.    H Perhaps you are thinking PANUMPOLL or PAMAXPOLL in SYSGEN.  The help for- them sounds very similar to what you mention.o  ' On Tue, 10 Apr 2001, Main, Kerry wrote:T   > re: MAXIMUM_HOSTSs > N > If I recall correctly (from memory here), this parameter determines how manyN > CI nodes will get polled on a regular basis. As an example if the default isL > 15, each polling period, it looks for nodes 0-15. If this parameter is set > to 7, < > then each polling period, it will only look for nodes 0-7. > I > Beware, if I remember a watchout - if you add node 8 someday and forgeti9 > about this parameter set to 7, you will have problems..o > 
 > Regards, >  > Kerry Main > Senior Consultanto > Compaq Canada Inc.   -- i   ------------------------------  % Date: Tue, 10 Apr 2001 14:48:17 -0300A) From: fabio_compaq@ep-bc.petrobras.com.brl! Subject: Re: Compaq & VMS Careers L Message-ID: <OF0BBCDB43.D9CEB91B-ON03256A2A.0061CE25@ep-bc.petrobras.com.br>  : --0__=03256A2A0061CE258f9e8a93df938690918c03256A2A0061CE25* Content-type: text/plain; charset=us-ascii    A The IT industry generally dont cares how do you make X ^  2  in ad program....A8 Sometimes they  prefer to make a loop to count it ......  C What I am trying to say is ... there is no QUALITY in th  IT (soft)C industry anymore !@ If do you want to sale and survive you must program faster ! ! !I So programers dont think !  The great lack in my country are C / C++ good D  programers ! Here people prefer VB to develop because is easy ! ! !3 So we never will be a strong software producer ....   @ The sucess in India is: they love math and we (.BR) are not good@ enthusiast  in math ... probably the way the teachers teach math  in our schools is not good ! ! !  ; And at the end, mathematics people will teach at schools or E the will  work  in specialized  soft companies like geology software.a   Regards    FC              < Linda Luik <p14175@email.sps.mot.com> em 10/04/2001 14:41:42  7 Favor responder a Linda Luik <p14175@email.sps.mot.com>              Info-VAX@Mvb.Saic.Comr      ! Assunto: Re: Compaq & VMS Careersi    G Mathematics is not a very popular program of study. Heck, I think there H were about 12 B.S. and B.A. degrees given in mathematics at ASU the yearH I graduated, 1996. I specialized in computational mathematics and have aH minor in computer science. And, here's a good one! I had a  manager tellH me that a math degree was useless in an IT department. Gee.... would you like fries with that?D   Linda6   Bill Gunshannon wrote: >lD > I hate to point out yet another bad sign, but a couple weeks ago IE > was visiting the Compaq Home Page under Careers and it listed pagescH > of them all over the country.  I went there today to show a particularE > possibility to one of our graduating students (It was a position touE > work on Math Libraries and this student double majored in CS & MathtH > with very high scores.)  There are a grand total of 13 VMS jobs listedF > on the web site.  I guess it won't accomplish much to steer studentsE > in that direction any more.  What happened to all those positions??t >s > bill >e > --E > Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Threel wolvesF > bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. > University of Scranton   |@ > Scranton, Pennsylvania   |         #include <std.disclaimer.h> (See attached file: p14175.vcf)v          : --0__=03256A2A0061CE258f9e8a93df938690918c03256A2A0061CE25( Content-type: application/octet-stream;  	name="p14175.vcf"6 Content-Disposition: attachment; filename="p14175.vcf"! Content-Transfer-Encoding: base64F  L YmVnaW46dmNhcmQgDQpuOkx1aWs7TGluZGENCnRlbDtwYWdlcjoxLjg4OC43NzIuNTIzMA0KdGVsL O2ZheDo0ODAuNjU1LjM1NjkNCnRlbDt3b3JrOjQ4MC42NTUuNDQzMiAgDQp4LW1vemlsbGEtaHRtL bDpGQUxTRQ0KCS1tb3ppbGxhLWNwdDo7MzM0NDs7Ow0Kb3JnOk1vdG9yb2xhICBTUFMgO0lULUNJL TSBtYWlsZHJvcDogTTU1NQ0KdmVyc2lvbjoyLjENCmVtYWlsO2ludGVybmV0OmxpbmRhLmx1aWtAL bW90b3JvbGEuY29tDQp0aXRsZTpSZWdpb25hbCBWTVMgU3lzdGVtcyBBZG1pbnN0cmF0b3IvQmFjL a3VwIEFuYWx5c3QNCmFkcjtxdW90ZWQtcHJpbnRhYmxlOjs7MjIwMCBXLiBCcm9hZHdheSBSb2Fk4 ICA9MEQ9MEE9DQpmbjpMdWlrLCBMaW5kYQ0KZW5kOnZjYXJkDQo=  < --0__=03256A2A0061CE258f9e8a93df938690918c03256A2A0061CE25--   ------------------------------  % Date: Tue, 10 Apr 2001 14:07:17 -0400d+ From: Brendan Welch <brendan_welch@uml.edu>s! Subject: Re: Compaq & VMS Careerso' Message-ID: <3AD34BD5.D5F1616E@uml.edu>   * fabio_compaq@ep-bc.petrobras.com.br wrote: >  > Go to www.jobserver.comI > + > There are more than 500 references of VMSn >   % my browser says that is a bad addresse   --E Brendan Welch, system analyst, Univ. of Massachusetts - Lowell, W1LPGS   ------------------------------    Date: 10 Apr 2001 14:27:19 -0500+ From: young_r@encompasserve.org (Rob Young)o! Subject: Re: Compaq & VMS Careers 3 Message-ID: <SB3ue$0Owzzh@eisner.encompasserve.org>o  a In article <9avghj$3t1@gap.cco.caltech.edu>, mathog@seqaxp.bio.caltech.edu (David Mathog) writes:ac > In article <P+BltrKIqosr@eisner.encompasserve.org>, young_r@encompasserve.org (Rob Young) writes:-c >>In article <9av79r$t2a@gap.cco.caltech.edu>, mathog@seqaxp.bio.caltech.edu (David Mathog) writes:. >> >>> O >>> That's true.  But if 18 really is all the VMS positions they have availabletO >>> it implies that the total number of people working on the OS is very small.rI >>> I'd expect at least a 5-10% yearly turnover (minimum) in any software M >>> development group, and that suggests that there are somewhere between 360tO >>> and 180 people working on VMS.  And given Compaq management's "talents" at nN >>> retaining key personnel a turnover of 20% is not unreasonable, which would? >>> put the total VMS development group size at less than 100. : >>>  >>D >>	From presentations you see over 450 engineers are working on VMS. > M > Really?  That number sounds way too high given the number of job ads.  DoestG > that number also include all the Alpha chip designers, alpha hardwareaM > designers, software folks who are on cross platform projects (ie, all the Ci > compiler people), etc? > >   ( 	Perhaps, and it may indeed be inflated!   >>F >>	Also, 6000 support personnel (suspect they are roping in everyone, 7 >>	i.e. storage folks that support VMS in some regard).  > L > Exactly - the same sort of inflation that I suspect is in the 450 number.  >    	True.   				Robs   ------------------------------  % Date: Tue, 10 Apr 2001 14:46:14 -0400)# From: Jim Agnew <Agnew@hsc.vcu.edu>m! Subject: Re: Compaq & VMS Careers + Message-ID: <3AD354F6.A84CD3B7@hsc.vcu.edu>a   i think it's www.jobserve.coml  ? thanks, but u.s. would be nice...  glad it's better over there.>  * fabio_compaq@ep-bc.petrobras.com.br wrote: >  > Go to www.jobserver.como > + > There are more than 500 references of VMSn > 	 > Regardsv >  > FC > E > rdeininger@mindspring.com (Robert Deininger) em 10/04/2001 13:16:13  > @ > Favor responder a rdeininger@mindspring.com (Robert Deininger) >  >       Info-VAX@Mvb.Saic.Com8 > # > Assunto: Re: Compaq & VMS Careers  > L > In article <9av79r$t2a@gap.cco.caltech.edu>, mathog@seqaxp.bio.caltech.edu > wrote: >  > >rE > > That's true.  But if 18 really is all the VMS positions they havee > available H > > it implies that the total number of people working on the OS is very > small.I > > I'd expect at least a 5-10% yearly turnover (minimum) in any software M > > development group, and that suggests that there are somewhere between 360wK > > and 180 people working on VMS.  And given Compaq management's "talents"  > atH > > retaining key personnel a turnover of 20% is not unreasonable, which > would > > > put the total VMS development group size at less than 100. > >uA > > Microsoft probably has that many working just on Minesweeper!. > J > There have been many more jobs listed recently; I sort of recall 60-80 aH > few months ago.  Trying to extrapolate today's snapshot to a long-termJ > statistic is risky.  As others have noted, Compaq has recently announcedI > layoffs.  There could well be a temporary freeze or slowdown in hiring,,7 > but no real change in long-term hiring goals for VMS.h >  > -- > Robert Deininger > rdeininger@mindspring.coms   ------------------------------  % Date: Tue, 10 Apr 2001 12:14:54 -0700k+ From: Linda Luik <p14175@email.sps.mot.com> ! Subject: Re: Compaq & VMS Careersr0 Message-ID: <3AD35BAE.ACF0C69@email.sps.mot.com>  , This is a multi-part message in MIME format.& --------------10C6544000B26A56E522BE21* Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bitw   I feel your pain!  Lindag  * fabio_compaq@ep-bc.petrobras.com.br wrote: > C > The IT industry generally dont cares how do you make X ^  2  in aZ
 > program....r: > Sometimes they  prefer to make a loop to count it ...... > E > What I am trying to say is ... there is no QUALITY in th  IT (soft)  > industry anymore !B > If do you want to sale and survive you must program faster ! ! !K > So programers dont think !  The great lack in my country are C / C++ goodeF >  programers ! Here people prefer VB to develop because is easy ! ! !5 > So we never will be a strong software producer ....e > B > The sucess in India is: they love math and we (.BR) are not goodB > enthusiast  in math ... probably the way the teachers teach math" > in our schools is not good ! ! ! > = > And at the end, mathematics people will teach at schools orrG > the will  work  in specialized  soft companies like geology software.  > 	 > Regards  >  > FC > > > Linda Luik <p14175@email.sps.mot.com> em 10/04/2001 14:41:42 > 9 > Favor responder a Linda Luik <p14175@email.sps.mot.com>) >  >       Info-VAX@Mvb.Saic.Com  > # > Assunto: Re: Compaq & VMS Careers  > I > Mathematics is not a very popular program of study. Heck, I think therewJ > were about 12 B.S. and B.A. degrees given in mathematics at ASU the yearJ > I graduated, 1996. I specialized in computational mathematics and have aJ > minor in computer science. And, here's a good one! I had a  manager tellJ > me that a math degree was useless in an IT department. Gee.... would you > like fries with that?e >  > Lindaa >  > Bill Gunshannon wrote: > > F > > I hate to point out yet another bad sign, but a couple weeks ago IG > > was visiting the Compaq Home Page under Careers and it listed pagesaJ > > of them all over the country.  I went there today to show a particularG > > possibility to one of our graduating students (It was a position to*G > > work on Math Libraries and this student double majored in CS & Math J > > with very high scores.)  There are a grand total of 13 VMS jobs listedH > > on the web site.  I guess it won't accomplish much to steer studentsG > > in that direction any more.  What happened to all those positions??f > >t > > bill > >: > > --G > > Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Threeh > wolvesH > > bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. > > University of Scranton   |B > > Scranton, Pennsylvania   |         #include <std.disclaimer.h>! > (See attached file: p14175.vcf)o   -- a
 Linda Luik Systems Engineer   Motorola 2200 W. Broadway Rd.	 AZ09-M555t Mesa, Arizona 85202v Phone: 480-655-4432k FAX:   480-655-3659o Pager  1-888-772-5230e linda.luik@motorola.come& --------------10C6544000B26A56E522BE21- Content-Type: text/x-vcard; charset=us-ascii;s  name="p14175.vcf" Content-Transfer-Encoding: 7bitn( Content-Description: Card for Linda Luik  Content-Disposition: attachment;  filename="p14175.vcf"   begin:vcard  n:Luik;Linda tel;pager:1.888.772.5230 tel;fax:480.655.3569 tel;work:480.655.4432    x-mozilla-html:FALSE 	-mozilla-cpt:;3344;;;( org:Motorola  SPS ;IT-CIM maildrop: M555 version:2.1e& email;internet:linda.luik@motorola.com6 title:Regional VMS Systems Adminstrator/Backup Analyst5 adr;quoted-printable:;;2200 W. Broadway Road  =0D=0A=d fn:Luik, Linda	 end:vcard-  ( --------------10C6544000B26A56E522BE21--   ------------------------------  % Date: Wed, 11 Apr 2001 01:47:33 +0300r0 From: Panayiotis Kassapidis <pkassapi@otenet.gr>! Subject: Re: Corba on OpenVMS AXPd) Message-ID: <3AD38D85.327E1357@otenet.gr>c  N There is an ORB we are using for over a year now on two OpenVMS systems. It isM InJoin BROKER available from CriticalPath (http://www.cp.net). I think it wasLO originally developed by ICL as DAIS, then sold to Peer Logic. It was renamed to1F InJoin BROKER when the latter was acquired by CriticalPath. Our parentI organisation (Vodafone) uses it as well. As far as I know we had no majoryO problems, although I must admit I am not the one that deals with it day in, dayr out..    I hope this helps,
 Panayiotis  	 ---------e Panayiotis Kassapidisa UNIX/VMS Servicesi+ Technical / Computer & Information Services  PANAFON Services S.A.c   e-mail: pkassapi@panafon.grn     Jakob Erber wrote:  M > Despite all signs that OpenVMS will be there for a long time to come, thereeI > is still support missing for software, I find vital for an important OSs > plattform. > K > For example, as far as I can see, there is no Corba product available forn3 > VMS, which offers proffessionell support as well.1 >pL > There are some very good freeware Orbs, but can you use them for a mission > critical system? >/ > best regards >g > JakobN   ------------------------------  % Date: Tue, 10 Apr 2001 21:38:52 -0400e* From: Eric Ebinger <eebinger@telocity.com>! Subject: Re: Corba on OpenVMS AXPA8 Message-ID: <002401c0c228$2b1d8850$e900a8c0@teamrdb.com>  G That is...interesting...  There web site doesn't quite agree with that.l, http://www.iona.com/products/orbix3_tech.htm  C Note that Orbix 3.0 states that it is supported on OpenVMS 7.2-1...i   Sigh.h
 Good Luck.   Eric Ebinger ----- Original Message -----" From: Jakob Erber <erberj@post.ch> To: <Info-VAX@Mvb.Saic.Com> % Sent: Tuesday, April 10, 2001 3:49 AM-! Subject: Re: Corba on OpenVMS AXP     K > I just received a mail from IONA, thatthey have nothing to offer for VMS.C > But I will douplecheck.  > thanks > Jakob- > ? > "Eric Ebinger" <eebinger@telocity.com> schrieb im Newsbeitrag.4 > news:003f01c0c15f$d8a5eae0$e900a8c0@teamrdb.com...J > > If you look at the OpenVMS stratigies and directions presentation from > > February 2001iE > > (http://www.openvms.compaq.com/presentations/openvmsstrategy.htm)o= > > You will see that Iona Orbix 2000 is being ported to VMS.n > >i > > Eric Ebinger  > > ----- Original Message -----& > > From: Jakob Erber <erberj@post.ch> > > To: <Info-VAX@Mvb.Saic.Com>p( > > Sent: Monday, April 09, 2001 3:41 AM! > > Subject: Corba on OpenVMS AXPr > >u > > K > > > Despite all signs that OpenVMS will be there for a long time to come,1	 > > there J > > > is still support missing for software, I find vital for an important OS > > > plattform. > > >iK > > > For example, as far as I can see, there is no Corba product availableo > forb7 > > > VMS, which offers proffessionell support as well.f > > > H > > > There are some very good freeware Orbs, but can you use them for a	 > missionm > > > critical system? > > >  > > > best regards > > >s > > > Jakob  > > >c > > >  > > >c > >e >  >h >o   ------------------------------  % Date: Tue, 10 Apr 2001 13:56:15 -0500 I From: "Adam.lewiax@integris-health.com" <adam.lewiax@integris-health.com>a$ Subject: Directory lexical functions. Message-ID: <9avimm$h02@news-central.tiac.net>  I How can I return the number of files in a given directory using a lexicallJ function.    I'd like to do two things.  First return the total numbers ofE files on a given disk then give a break down of each directory total.C  	 Thoughts?e   ------------------------------  % Date: Tue, 10 Apr 2001 21:35:45 +02000> From: "Jean-Francois Marchal" <jean-francois.marchal@x9000.fr>( Subject: Re: Directory lexical functions. Message-ID: <9avn51$j29$1@reader1.imaginet.fr>  B $ Dir /grant gives you the number of files in the target directory   Jean-Franois Marchal  X9000 - LYON (FR)     K "Adam.lewiax@integris-health.com" <adam.lewiax@integris-health.com> a crit 9 dans le message news: 9avimm$h02@news-central.tiac.net...6K > How can I return the number of files in a given directory using a lexical L > function.    I'd like to do two things.  First return the total numbers ofG > files on a given disk then give a break down of each directory total.L >n > Thoughts?  >p >r   ------------------------------  % Date: Tue, 10 Apr 2001 15:41:11 -0400i7 From: David Beatty <David.Beatty@sasSPAMITUPTHEZZZ.com>l( Subject: Re: Directory lexical functions2 Message-ID: <j2HTOl1tF=JXGR34XoZkYctaKPwu@4ax.com>  9 There isn't one; you'll have to perform a DIR [000000...]a7 /TOTAL/SIZE=ALL/OUTPUT=file and parse through the file.e   David R. Beatty   E On Tue, 10 Apr 2001 13:56:15 -0500, "Adam.lewiax@integris-health.com"a( <adam.lewiax@integris-health.com> wrote:  J >How can I return the number of files in a given directory using a lexicalK >function.    I'd like to do two things.  First return the total numbers ofnF >files on a given disk then give a break down of each directory total. >1
 >Thoughts? >A   ------------------------------  # Date: Wed, 11 Apr 2001 00:14:58 GMTa) From: rob.buxton@wcc.govt.nz (Rob Buxton)0( Subject: Re: Directory lexical functions0 Message-ID: <3ad3a113.15325346@news.wcc.govt.nz>  E On Tue, 10 Apr 2001 13:56:15 -0500, "Adam.lewiax@integris-health.com"r( <adam.lewiax@integris-health.com> wrote:  J >How can I return the number of files in a given directory using a lexicalK >function.    I'd like to do two things.  First return the total numbers of F >files on a given disk then give a break down of each directory total. >t
 >Thoughts?  + Don't know about a Lexical Function but....c  * DIRE device:[000000...] /SIZE:ALL  / GRAND  ! Would give you files  on the disk     ) DIRE device:[000000...] /SIZE:ALL  /TOTALr  - Would give a sumamry of files in directories.l  7 Alas, it wouldn't be easy to format into a neat report.    ------------------------------  # Date: Wed, 11 Apr 2001 01:18:25 GMT!2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)( Subject: Re: Directory lexical functions2 Message-ID: <BhOA6.768$fB6.19650@news.cpqcorp.net>  z In article <9avimm$h02@news-central.tiac.net>, "Adam.lewiax@integris-health.com" <adam.lewiax@integris-health.com> writes:J :How can I return the number of files in a given directory using a lexicalK :function.    I'd like to do two things.  First return the total numbers of F :files on a given disk then give a break down of each directory total.  J   There is no lexical nor system service to analyze the entire contents ofJ   a specific directory, OpenVMS utilities and applications simply scan theJ   contents.  In other words, this is possible using a trivial DCL command I   procedure, but not a single lexical.  Here is a quick start at the DCL  0   command procedure that would be required here:         $ x = f$search("",1)     $ files = 0a
     $ alq = 0e
     $ eof = 0t
     $loop:     $ x = f$search("*.*;*",1)t     $ if f$length(x) .ne. 0o
     $ then#     $   alq = alq + f$file(x,"ALQ")a#     $   eof = eof + f$file(x,"EOF")      $   files = files + 1d     $   goto loope     $ endifS0     $ write sys$output "Total Files:   ''files'".     $ write sys$output "Storage (ALQ): ''alq'".     $ write sys$output "Storage (EOF): ''eof'"
     $ exit    
 :Thoughts?  9   Ayup.  I can recommend a book on DCL programming... :-)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: Tue, 10 Apr 2001 17:11:12 -0400-. From: Michael Austin <maustin@nc.prestige.net>, Subject: Re: error installing patch on vax??/ Message-ID: <3AD376F0.FE2F1939@nc.prestige.net>u   Patti Johnson wrote:  N > Hello, I'm new at this and am now trying to apply patches to a couple of ourL > machines.  I'm starting w/ the newer one, a VAX system (7.2).  There's not  > much to the directions... just9 >         @sys$update:vmsinstal patchname locationofpatchpA > Sounds easy enough.  But, when I do so, here's the error I get:y >G8 > %VMSINSTAL-I-RESTORE, Restoring product save set A ...= > %BACKUP-E-READERRS, excessive error rate reading <location>r- > -BACKUP-E-HDRCRC, software header CRC error06 > %BACKUP-I-SPECIFY, specify option (QUIT or CONTINUE)	 > BACKUP>- >-  O Looks like you used BINARY FTP to transfer the file form it's original locationhM to a PC then FTP'ed it to the VAX.  Here is a trick that I have used for moreuO than 10 years to correct file transfer translation problems from KERMIT to FTP..< In fact, I had to use it recently tpo fix this very problem.   $!  Fix funky FTP problems...r@ $write sys$ouput "Ignore all   %BACKUP-W-NOFILES error messages" $loop: $!!PQ $!!        first we find all of the latest versions of savesets in this directoryn  < $!!        that are .A, .B etc...  and strip off the version $!! * $ file = f$element(0,";",f$search("*.%;")) $ if file .eqs. "" then exit $ on severe_error then continueo $!!a; $!!      Next we create an enpty, correctly defined savesetl $!!o! $ back lkjfdssljk 'file'_new/save_ $!!o& $!!      Then we "merge" the two files $!!c $ copy/over 'file'  'file'_new% $!!      And finally rename the filesi $ rename 'file' 'file'_orig  $ rename 'file'_new 'file'
 $goto loop  , Just make sure you have enough disk space...   Michael Austin DBA Consultant     >wN > I'm not sure where to turn for answers... I'd assumed something was wrong w/! > the saveset I'd downloaded fromeE > http://ftp.support.compaq.com/patches/.new/openvms.shtml so I triedtG > downloading again but the error recurred.  It's vaxupdate01_072, btw.n >  > tia> > pj > -- > O > _____________________________________________________________________________MO > Patti Johnson (pj)                                           pjohnson@wcu.edu  > WCU Computer Centera > Cullowhee, N.C. 28723 O > 828-227-3224                         Time spent with a child is never wasted.h   ------------------------------  % Date: Tue, 10 Apr 2001 17:10:07 -0400i. From: Michael Austin <maustin@nc.prestige.net>, Subject: Re: error installing patch on vax??/ Message-ID: <3AD376AE.163EFF9C@nc.prestige.net>a   Patti Johnson wrote:  N > Hello, I'm new at this and am now trying to apply patches to a couple of ourL > machines.  I'm starting w/ the newer one, a VAX system (7.2).  There's not  > much to the directions... just9 >         @sys$update:vmsinstal patchname locationofpatch-A > Sounds easy enough.  But, when I do so, here's the error I get:n >h8 > %VMSINSTAL-I-RESTORE, Restoring product save set A ...= > %BACKUP-E-READERRS, excessive error rate reading <location>v- > -BACKUP-E-HDRCRC, software header CRC errora6 > %BACKUP-I-SPECIFY, specify option (QUIT or CONTINUE)	 > BACKUP>r >:  O Looks like you used BINARY FTP to transfer the file form it's original location M to a PC then FTP'ed it to the VAX.  Here is a trick that I have used for more O than 10 years to correct file transfer translation problems from KERMIT to FTP.e< In fact, I had to use it recently tpo fix this very problem.   $!  Fix funky FTP problems...n@ $write sys$ouput "Ignore all   %BACKUP-W-NOFILES error messages" $loop: $!!tQ $!!        first we find all of the latest versions of savesets in this directorye  < $!!        that are .A, .B etc...  and strip off the version $!!g* $ file = f$element(0,";",f$search("*.%;")) $ if file .eqs. "" then exit $ on severe_error then continue  $!!e; $!!      Next we create an enpty, correctly defined savesetw $!!6! $ back lkjfdssljk 'file'_new/saveM $!!n& $!!      Then we "merge" the two files $!!  $ copy/over 'file'  'file'_new% $!!      And finally rename the filesh $ rename 'file' 'file'_orig  $ rename 'file'_new 'file'
 $goto loop  , Just make sure you have enough disk space...   Michael Austin DBA Consultant     >rN > I'm not sure where to turn for answers... I'd assumed something was wrong w/! > the saveset I'd downloaded fromyE > http://ftp.support.compaq.com/patches/.new/openvms.shtml so I tried,G > downloading again but the error recurred.  It's vaxupdate01_072, btw.r >r > tia  > pj > -- >iO > _____________________________________________________________________________tO > Patti Johnson (pj)                                           pjohnson@wcu.edue > WCU Computer Center4 > Cullowhee, N.C. 28723uO > 828-227-3224                         Time spent with a child is never wasted.3   ------------------------------  % Date: Tue, 10 Apr 2001 17:11:45 -0400f. From: Michael Austin <maustin@nc.prestige.net>, Subject: Re: error installing patch on vax??/ Message-ID: <3AD37711.4A02DF06@nc.prestige.net>n   Patti Johnson wrote:  N > Hello, I'm new at this and am now trying to apply patches to a couple of ourL > machines.  I'm starting w/ the newer one, a VAX system (7.2).  There's not  > much to the directions... just9 >         @sys$update:vmsinstal patchname locationofpatchoA > Sounds easy enough.  But, when I do so, here's the error I get:u >s8 > %VMSINSTAL-I-RESTORE, Restoring product save set A ...= > %BACKUP-E-READERRS, excessive error rate reading <location>e- > -BACKUP-E-HDRCRC, software header CRC error!6 > %BACKUP-I-SPECIFY, specify option (QUIT or CONTINUE)	 > BACKUP>h >u  O Looks like you used BINARY FTP to transfer the file form it's original location.M to a PC then FTP'ed it to the VAX.  Here is a trick that I have used for more O than 10 years to correct file transfer translation problems from KERMIT to FTP.o< In fact, I had to use it recently tpo fix this very problem.   $!  Fix funky FTP problems...d@ $write sys$ouput "Ignore all   %BACKUP-W-NOFILES error messages" $loop: $!! Q $!!        first we find all of the latest versions of savesets in this directory   < $!!        that are .A, .B etc...  and strip off the version $!!o* $ file = f$element(0,";",f$search("*.%;")) $ if file .eqs. "" then exit $ on severe_error then continue  $!!h; $!!      Next we create an enpty, correctly defined saveseta $!!t! $ back lkjfdssljk 'file'_new/save  $!!c& $!!      Then we "merge" the two files $!!e $ copy/over 'file'  'file'_new% $!!      And finally rename the filesu $ rename 'file' 'file'_origt $ rename 'file'_new 'file'
 $goto loop  , Just make sure you have enough disk space...   Michael Austin DBA Consultant     > N > I'm not sure where to turn for answers... I'd assumed something was wrong w/! > the saveset I'd downloaded fromrE > http://ftp.support.compaq.com/patches/.new/openvms.shtml so I triedsG > downloading again but the error recurred.  It's vaxupdate01_072, btw.n >o > tiaj > pj > -- >tO > _____________________________________________________________________________ O > Patti Johnson (pj)                                           pjohnson@wcu.edua > WCU Computer CenterW > Cullowhee, N.C. 28723 O > 828-227-3224                         Time spent with a child is never wasted.c   ------------------------------  % Date: Tue, 10 Apr 2001 12:01:59 +0001| From: bjbeckum@pacbell.net" Subject: Free Travel and Bizz Opp!- Message-ID: <0GBL0088GB95W6@mx.east.saic.com>   m <HTML><FONT  BACK="#ffffff" style="BACKGROUND-COLOR: #ffffff" SIZE=2 PTSIZE=10><B>GET YOUR FREE GIFT WHEN<BR>o VISITING OUR WEB SITE!</B><BR> <BR>C</FONT><FONT  COLOR="#ff0000" BACK="#ffffff" style="BACKGROUND-COLOR: #ffffff" SIZE=2 PTSIZE=10 FAMILY="SANSSERIF" FACE="Arial" LANG="0"><B>Are you being paid what you are worth?</FONT><FONT  COLOR="#000000" BACK="#ffffff" style="BACKGROUND-COLOR: #ffffff" SIZE=2 PTSIZE=10 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></B><BR>c <BR>1 We are living in the most prosperous time in <BR>n2 history. Now is your turn to profit. Learn to <BR>5 earn 6 Figures from home. It is easier than ever!<BR>l <BR>4 <B>Plus, receive your FREE GIFT & FREE Info when<BR> visiting our web site.</B><BR> <BR>K <B><A HREF="http://216.74.100.93/~gtek/portal/">CLICK HERE!</A></B></B><BR>t </FONT><FONT  COLOR="#000000" BACK="#ffffff" style="BACKGROUND-COLOR: #ffffff" SIZE=1 PTSIZE=8 FAMILY="SANSSERIF" FACE="Arial" LANG="0"><BR> <BR> <BR> <BR> <BR> <BR> <BR>V <I>You were sent this message because your address is in our subscriber database. <BR> If you wish to be removed, please <A HREF="mailto:remdat779@yahoo.com?subject=remove biz">click here</A> and we will remove you from our subscriber list.<BR>i <BR> <BR> </I></FONT></HTML>   ------------------------------  % Date: Tue, 10 Apr 2001 21:02:58 -0700d7 From: David Spencer <spencer@pageweavers.spaamfree.com>e' Subject: Re: FTP hijacking of VMS sites B Message-ID: <100420012102586723%spencer@pageweavers.spaamfree.com>  8 In article <9alg6r$bt7$1@hecate.umd.edu>, Lawrence Bleau <bleau@umtof.umd.edu> wrote:  I > Hello, folks.  I just noticed a lot of oddly named files - directories,sO > actually - in my system's anonymous ftp area.  They weren't created by anyoneOD > associate with our site.  One associate of mine gave me his guess: > A > i don't know if this is the case here, but i read articles from A > people who's anonymous ftp areas have been "hijacked" by people A > distributing large files like movies.  typically, a 1MB file iscF > uploaded to check the speed.  if the hijacker thinks the speed is ok? > lots of directories are created and movie parts are uploaded.e > . > see http://www.macintouch.com/ftphijack.html > O > I think this subject deserves some discussion.  It's the first I heard of it, 1 > and I've been managing VMS systems for a while.E > O > Has anyone experienced this phenomenon?  Has is cropped up at VMS sites?  Are0B > there standard ways of combating it?  Should this be in the FAQ? >  > Lawrence Bleau > University of Maryland$ > Physics Dept., Space Physics Group > 301-405-6223 > bleau@umtof.umd.edua  H I saw that article not too long ago. A few months back I decided to justF eliminate anonymous FTP access to my servers for this specific reason.H For a while it was amusing to see what kind of junk was appearing in theG directory; but eventually it grew tiresome. Long gone are the days whenh% the net was a happy friendly place :(u   -- Dave Spencer, PageWeavers   ------------------------------  % Date: Tue, 10 Apr 2001 22:37:42 +0400t4 From: "Ruslan R. Laishev" <Laishev@SMTP.DeltaTel.RU>9 Subject: Re: HELP: Problem in DEC BASIC reading IP Socketo0 Message-ID: <3AD352F6.A183F7D5@SMTP.DeltaTel.RU>   How the IOSB is defined ?e     Michael D. Ober wrote: > J > I am unable to get the number of bytes to return in the IOSB when I readL > from a channel that has been created as an IP Socket.  All other IP Socket > QIO calls are working. > ( > =============== CODE ================= > IPIN = "" @ > RETVAL = SYS$QIOW(0, CLIENT_SOCKET, IO$_READVBLK, LOC(IOSB), & >             , , &l% >             LOC(IPIN), LEN(IPIN), &  >             0, 0, 0, 0)p( > ====================================== >  > IPIN is defined as follows:., >  COMMON (IPBUFFER) STRING IPOUT = 32000, &B >                                          STRING IPIN     = 32000 > I > All other calls to SYS$QIOW are correctly filling the IOSB.  Any ideas?f >  > --	 > Thanks,  > Mike Ober.   --   Cheers, Ruslan.r= +---------------pure personal opinion-----------------------+ 9     RADIUS Server for OpenVMS project - www.radiusvms.com-6       vms-isps@dls.net - Forum for ISP running OpenVMS:   Mobile: +7 (901) 971-3222, AIM nickname:"VMS hardworker"   ------------------------------  % Date: Tue, 10 Apr 2001 14:41:38 -0600m4 From: "Michael D. Ober" <mdo.@.wakeassoc.com.nospam>9 Subject: Re: HELP: Problem in DEC BASIC reading IP Socketi2 Message-ID: <8eKA6.815$QA6.249639@news.uswest.net>  K Sorry about not providing the IOSB structure.  I get all 0's in the IOSB atyK the end of this particular QIOW call and reuse the IOSB variable throughout " this application with no problems.   ! IO STATUS BLOCK STRUCTUREm RECORD TYPE$_IOSBu      WORD CONDITIONl      WORD TRANSFER_COUNT      LONG INFO END RECORD TYPE$_IOSB  DECLARE TYPE$_IOSB IOSBt   --
 Mike Ober.  ? "Ruslan R. Laishev" <Laishev@SMTP.DeltaTel.RU> wrote in messageR* news:3AD352F6.A183F7D5@SMTP.DeltaTel.RU... > How the IOSB is defined ?m >  >i > Michael D. Ober wrote: > >mL > > I am unable to get the number of bytes to return in the IOSB when I readG > > from a channel that has been created as an IP Socket.  All other IP  Socket > > QIO calls are working. > >e* > > =============== CODE =================
 > > IPIN = ""tB > > RETVAL = SYS$QIOW(0, CLIENT_SOCKET, IO$_READVBLK, LOC(IOSB), & > >             , , &1' > >             LOC(IPIN), LEN(IPIN), &i > >             0, 0, 0, 0)m* > > ====================================== > >s > > IPIN is defined as follows:K. > >  COMMON (IPBUFFER) STRING IPOUT = 32000, &D > >                                          STRING IPIN     = 32000 > >hK > > All other calls to SYS$QIOW are correctly filling the IOSB.  Any ideas?i > >t > > -- > > Thanks,a > > Mike Ober. >- > -- > Cheers, Ruslan.w? > +---------------pure personal opinion-----------------------+x; >     RADIUS Server for OpenVMS project - www.radiusvms.comt8 >       vms-isps@dls.net - Forum for ISP running OpenVMS< >   Mobile: +7 (901) 971-3222, AIM nickname:"VMS hardworker"   ------------------------------  % Date: Tue, 10 Apr 2001 16:57:56 -0700o2 From: "Randy Park" <rjpark@mindspring.com.nospaam>9 Subject: Re: HELP: Problem in DEC BASIC reading IP Socketw3 Message-ID: <9b06ui$lk3$1@nntp9.atl.mindspring.net>   ; Pass IOSB by REF rather than LOC(IOSB).  For static stringsh9 the LOC function returns the address of the data, but forg7 dynamic strings the LOC function returns the address of  the string header.  = Michael D. Ober <mdo.@.wakeassoc.com.nospam> wrote in messagea, news:8eKA6.815$QA6.249639@news.uswest.net...J > Sorry about not providing the IOSB structure.  I get all 0's in the IOSB atB > the end of this particular QIOW call and reuse the IOSB variable
 throughout$ > this application with no problems. >a > ! IO STATUS BLOCK STRUCTUREs > RECORD TYPE$_IOSB' >      WORD CONDITIONo >      WORD TRANSFER_COUNT >      LONG INFO > END RECORD TYPE$_IOSB  > DECLARE TYPE$_IOSB IOSBo >a > -- > Mike Ober. > A > "Ruslan R. Laishev" <Laishev@SMTP.DeltaTel.RU> wrote in messageD, > news:3AD352F6.A183F7D5@SMTP.DeltaTel.RU... > > How the IOSB is defined ?a > >c > >, > > Michael D. Ober wrote: > > ><I > > > I am unable to get the number of bytes to return in the IOSB when Ii readI > > > from a channel that has been created as an IP Socket.  All other IP. > Socket > > > QIO calls are working. > > > , > > > =============== CODE ================= > > > IPIN = "" D > > > RETVAL = SYS$QIOW(0, CLIENT_SOCKET, IO$_READVBLK, LOC(IOSB), & > > >             , , &o) > > >             LOC(IPIN), LEN(IPIN), &l > > >             0, 0, 0, 0)e, > > > ====================================== > > > ! > > > IPIN is defined as follows:i0 > > >  COMMON (IPBUFFER) STRING IPOUT = 32000, &F > > >                                          STRING IPIN     = 32000 > > >iF > > > All other calls to SYS$QIOW are correctly filling the IOSB.  Any ideas? > > >  > > > --
 > > > Thanks,o > > > Mike Ober. > >l > > -- > > Cheers, Ruslan. A > > +---------------pure personal opinion-----------------------+ = > >     RADIUS Server for OpenVMS project - www.radiusvms.come: > >       vms-isps@dls.net - Forum for ISP running OpenVMS> > >   Mobile: +7 (901) 971-3222, AIM nickname:"VMS hardworker" >  >o   ------------------------------  # Date: Wed, 11 Apr 2001 01:33:00 GMT 3 From: "David M. Heller" <dheller1@rochester.rr.com>-5 Subject: How can I get the hardware-id number(newbie)s0 Message-ID: <3AD3B4D9.2253810A@rochester.rr.com>   Hi All  F I am trying to install a license-pak for OpenVMS 7.2 on a AlphaStationE 200 4/166. I cannot seem to fine the hardware-id number The number onmD the back of the case is unreadable. Is there a way to get the numberG thru software(I do have OpenVMS 7.2 installed) ??  If the hardware-id #rB is printed somewhere inside the unit where is it and what does theG number look like Ie; how many characters etc. The second question thererD is an entry in the vmslicense.com command to enter a product releaseH date. What date is that exactly or is it not needed for this software. I) have searched the openvms faq to no availa     Thanks in advancep   -- n4 David Heller                                         dheller1@rochester.rr.comR   ------------------------------  % Date: Tue, 10 Apr 2001 20:56:16 -0500r1 From: "David J. Dachtera" <djesys.nospam@fsi.net>o9 Subject: Re: How can I get the hardware-id number(newbie)o' Message-ID: <3AD3B9C0.8E54B2ED@fsi.net>o   "David M. Heller" wrote: >  > Hi All > H > I am trying to install a license-pak for OpenVMS 7.2 on a AlphaStationG > 200 4/166. I cannot seem to fine the hardware-id number The number onnF > the back of the case is unreadable. Is there a way to get the numberI > thru software(I do have OpenVMS 7.2 installed) ??  If the hardware-id #iD > is printed somewhere inside the unit where is it and what does the/ > number look like Ie; how many characters etc.v  * What is asking you for the "hardware id."?   > The second question thereaF > is an entry in the vmslicense.com command to enter a product releaseJ > date. What date is that exactly or is it not needed for this software. I+ > have searched the openvms faq to no availi  F When running VMSLICENSE.COM (or entering the PAK data manually via theE command line), you provide ONLY that information which appears on the G PAK document itself, and then you enter it EXACTLY as it appears on the'! PAK - nothing more, nothing less.t   -- u David J. Dachterad dba DJE Systemsi http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/   F This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings is to be expected.  @ Feel free to exercise your rights of free speech and expression.  F However, attacks against individual posters, or groups of posters, are strongly discouraged._   ------------------------------  % Date: Tue, 10 Apr 2001 21:54:51 -0400 % From: "John Vottero" <John@mvpsi.com>C9 Subject: Re: How can I get the hardware-id number(newbie)4/ Message-ID: <td7ebl7ifq6a84@news.supernews.com>i  K If you're registering a standard VMS license PAK then the PAK will have the: hardware id.  K Most license PAKs don't use the hardware ID.  In that case, just hit returna+ when VMSLICENSE.COM asks for a hardware ID.n    > "David M. Heller" <dheller1@rochester.rr.com> wrote in message* news:3AD3B4D9.2253810A@rochester.rr.com... >  > Hi All >hH > I am trying to install a license-pak for OpenVMS 7.2 on a AlphaStationG > 200 4/166. I cannot seem to fine the hardware-id number The number on F > the back of the case is unreadable. Is there a way to get the numberI > thru software(I do have OpenVMS 7.2 installed) ??  If the hardware-id # D > is printed somewhere inside the unit where is it and what does theI > number look like Ie; how many characters etc. The second question thereoF > is an entry in the vmslicense.com command to enter a product releaseJ > date. What date is that exactly or is it not needed for this software. I+ > have searched the openvms faq to no availr >r >  > Thanks in advancee >f > -- > David Heller > dheller1@rochester.rr.comP   ------------------------------  # Date: Wed, 11 Apr 2001 02:06:03 GMTi3 From: "David M. Heller" <dheller1@rochester.rr.com>l9 Subject: Re: How can I get the hardware-id number(newbie) 0 Message-ID: <3AD3BC99.8D65DEF0@rochester.rr.com>   Thanks for the reply  & When requesting my hobbyist license onG line(http://www.montagar.com/htbin/ohp_hobreg) it asks for a CPU serial D number(it won't work unless I enter a number) When I get the licenseC back via by email it shows that number as being the hardware_id # I A enter all the info exactly as shown in my email and I still get aeG checksum error I've tried about every number that I can find inside then case to no avail!e   -- i4 David Heller                                         dheller1@rochester.rr.comv http://www.mbcrep.com/?47353  ) http://teraformahealth.com/tfh/57601.html    ------------------------------  % Date: Tue, 10 Apr 2001 21:43:05 -0500 1 From: "David J. Dachtera" <djesys.nospam@fsi.net>c9 Subject: Re: How can I get the hardware-id number(newbie)d' Message-ID: <3AD3C4B9.8F6B5394@fsi.net>a   "David M. Heller" wrote: >  > Thanks for the reply > ( > When requesting my hobbyist license onI > line(http://www.montagar.com/htbin/ohp_hobreg) it asks for a CPU serial F > number(it won't work unless I enter a number) When I get the licenseE > back via by email it shows that number as being the hardware_id # IcC > enter all the info exactly as shown in my email and I still get a,I > checksum error I've tried about every number that I can find inside the> > case to no avail!i  F Ah. Then, try to make the best guess you can at what the serial numberE label may say on the back of the machine. That's your "hardware id.".t   --   David J. Dachtera  dba DJE Systemss http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/d  F This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings is to be expected.  @ Feel free to exercise your rights of free speech and expression.  F However, attacks against individual posters, or groups of posters, are strongly discouraged.t   ------------------------------  % Date: Tue, 10 Apr 2001 23:55:57 -0400U- From: JF Mezei <jfmezei.spamnot@videotron.ca>Y9 Subject: Re: How can I get the hardware-id number(newbie)a, Message-ID: <3AD3D5CD.6104AD1E@videotron.ca>   "David J. Dachtera" wrote:H > When running VMSLICENSE.COM (or entering the PAK data manually via theG > command line), you provide ONLY that information which appears on the!I > PAK document itself, and then you enter it EXACTLY as it appears on theL# > PAK - nothing more, nothing less.   L I beleive that the hobbyist licence program on the web does request that youN enter the hardware ID of the target machine. If you are without one, I can see how it would be difficult.  L In reply to the poster, no, you cannot get the hardware ID from the softwareA since the hardware ID is truly a cabinet/box ID and not a CPU id.a  ; How much of the serial number can you make out on the box ?t   ------------------------------  # Date: Wed, 11 Apr 2001 03:11:30 GMTr3 From: "David M. Heller" <dheller1@rochester.rr.com>aB Subject: Re: How can I get the hardware-id number(newbie) Followup0 Message-ID: <3AD3CBF1.95F320BC@rochester.rr.com>   Hi  B Thanks for all the speedy responses. I used the lot number that is8 printed on the bar code label attached to the cpu itself) using that number the registration works.t   Thanks     -- o4 David Heller                                         dheller1@rochester.rr.com    ------------------------------    Date: 10 Apr 2001 17:52:30 -0500+ From: kuhrt@encompasserve.org (Marty Kuhrt)p Subject: How not to add patches 3 Message-ID: <q8wGClGdNnG+@eisner.encompasserve.org>   > I did a nifty job of shooting myself in the foot last week.  I? thought I'd share my adventures so that others may not limp so.-  ; Upgraded a system from 7.1-2 to 7.2-1, which was a painlesskA operation.  I then went to install the CRTL, DV, PCSI, RMS, SCSI,B; and UPDATE patches.  Knowing the PRODUCT command could take < wildcards, I did the update in one swell foop by typing PROD> INSTALL *.  I then answered all the questions and deferred the? reboot(s) until I had all of them done.  Man, did that make for  an unusable system.E  ? Unfortunately, I couldn't figure out an easy way to back out ofw= the patches.  Reinstalling 7.2-1 from the CD over the gutshots= 7.2-1 system pulled all the patches and put me back to squareE? one.  I then installed the patches in the CSC acceptable mannerm< which is UPDATE, reboot, PCSI, SYS, reboot, RMS, reboot, DV,@ reboot, CRTL, reboot.  Tedious, but the system is now working as	 expected.B  @ The moral of the story:  Just because the command has a wildcard& option doesn't mean you should use it.   Gimpy6   ------------------------------  % Date: Tue, 10 Apr 2001 20:06:25 +0000=; From: WebSource moderator <WebSource-owner@yahoogroups.com>Z/ Subject: Invitation to join the WebSource group=6 Message-ID: <986933185.12582.31697.cb@yahoogroups.com>   Hello,  0 You've been invited to join the WebSource group,F an email group hosted by Yahoo! Groups, a free, easy-to-use email gro= up service.   JOIN NOW, IT'S EASY:=20e  : 1) REPLY to this email by clicking "Reply" and then "Send" in your email program<   -OR-  " 2) Go to the Yahoo! Groups site atF    http://groups.yahoo.com/invite/WebSource?email=3Dinfo-vax%40mvb%2E=- saic%2Ecom&iref=3DCfbhKgOlvrBrxJTBTh4mQCYBc2Ai; By joining WebSource, you will be able to exchange messageseC with other group members. Yahoo! Groups also makes it easy to storea- photos and files, coordinate events and more.   8 Here's an introductory message from the group moderator:F ---------------------------------------------------------------------= ---r   Hello,  F Welcome to the WebSource group at Yahoo! Groups, a free, easy-to-use =F email group service.  Please take a moment to review this message and=#  the benefits of becoming a member.s  F Join WebSource today, to receive our FREE newsletter with your Ad in =F it >> The BEST WAY TO PROMOTE YOURSELF AND YOUR PRODUCTS to your TARG=F ETED AUDIENCE is through Newsletters. I promote the WebSource Newslet=F ter not just within the WebSource Group, but outside of it as well.  =F =46rom the seven months of full-time researching the internet to find=F  the best sites, I have learned where the right areas to advertise ar=F e -- and that's what will bring in paying customers and not people wh=F o look for free stuff on your web site then leave.  You will also be =F able to post your own personal messages to all of the WebSource Group=F  and have access to our Files and  Bookmarks >> This section is "THE =F BEST" for business-to-business resources and individuals wanting to w=F ork-from-home --95% of the sites posted in the WebSource Group are ra=F ted and have been nominated by Forbes, Money, Fortune and other well-=, known magazines as the best on the Net.  =20  F The WebSource group consists of website owners, webmasters, business =F professionals, software users, individuals looking for work-from-home=D  opportunities and internet enthusiasts. If these members fit your =F =93Targeted Audience=94 and you want to promote yourself and your bus=> iness to them for FREE right now, then here's how you do it...  F To start sending messages to members of this group, simply send email=  to:=20s   WebSource@yahoogroups.com   F If you do not wish to belong to WebSource, you may unsubscribe by sen= ding an email to:=20  % WebSource-unsubscribe@yahoogroups.com=  F You may also visit the Yahoo! Groups web site to modify your subscrip= tions:    http://groups.yahoo.com/mygroups  F I hope to be helping you succeed with your business ventures "on" and=  "offline" really soon,=     Denise Freeman Moderator, WebSource =20   F ---------------------------------------------------------------------= ---     6 If you do not wish to join the WebSource group, please ignore this invitation.l  F SPECIAL NOTE FROM Yahoo! Groups:  Because Yahoo! Groups values your p= rivacy,lD it is a violation of our service rules for moderators to abuse this= =20AC invitation feature. If you feel this has happened, please notify usd at abuse@yahoogroups.com=20g  F Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/te= rms/ =20-   ------------------------------  # Date: Wed, 11 Apr 2001 01:39:30 GMTl) From: rob.buxton@wcc.govt.nz (Rob Buxton)j6 Subject: Re: KZCCA Ultrawide SCSI Adapters for the VAX0 Message-ID: <3ad3b3c6.20112330@news.wcc.govt.nz>  7 On Tue, 10 Apr 2001 09:46:18 -0700, "Barry Treahy, Jr."l <treahy@mmaz.com> wrote:  @ I had to replace a KZCCA Configuration here with HSD Technology.  E The KZCCA was attached to a VAX 4000-705A. This was part of a Cluster 9 and serving the UltraSCSI Disks to other Cluster Members.R  2 A couple of the other Cluster members were Alphas.  F We had repeated System Crashes with this configuration. After a numberF of Crash Dumps were analysed the understanding was that the PKWDriver,C supplied as part of the KZCCA could not handle being MSCP Served to  the Alphas.u  F The Crashes typically happened when a Backup was running on the Alpha,B pulling Data from the VAX. However, there were crashes under other load conditions.  C During the problem time I ended up increasing npagedyn (I think) as E well as mscp_buffer to very large values. That made the crashes a bitO, more infrequent but didn't stop the crashes.  ? The final solution was to remove the KZCCA, and move to HSD30s.=B We did NOT have I/O Performance issues and so the reduction in I/O throughput was not a concern. C As part of the change I used two HSD Controllers dual-ported to twoRD VAX4000s, thereby offering resilience and sufficient I/O throughput.  / This problems persisted through VMS 6.2 to 7.2.   F So, I would advise extreme caution if using this device in a ClusteredE environment, especially if the devices will be MSCP Served to Alphas.o   Rob.  F >Does anyone on the list have any practical experience or knowledge of2 >the KZCCA Ultrawide SCSI Adapter for VAX systems? >nF >As many of you suggested would become reality, Mr. Marcello's earlierG >offer to help resulted in nothing when I was investigating an XMI SCSIaE >Adapter two months ago and he has ignored my recent 'comment' on the-G >quality of his aid.  Regrettably, the Compaq web site is still equallyhG >useless regarding this 'newer' product.  I've been on hold with CompaqoG >for 20 minutes, I guess they must have a skeleton staff handling theses
 >questions...g >aF >What I'm specifically interested in is the external interface and theI >speed of the bus for external SCSI devices.  It would seem that a lot ofhG >the SCSI adapters upgrades for the VAX provide reasonable internal buscH >performance, but terrible external performance and we will not be using >SW to connect to this.  >OE >Any comments on a source, new or used, that had provided a favorable  >price would be appreciated. >  >TIA.N >  >Barry >D >--$ >S@ >Barry Treahy, Jr  *  Midwest Microwave  *  Vice President & CIO > B >E-mail: Treahy@mmaz.com * Phone: 480/314-1320 * FAX: 480/661-7028 >F >1   ------------------------------  % Date: Tue, 10 Apr 2001 20:49:02 -0400 , From: "islandco.com" <dbturner@islandco.com> Subject: KZPCA-AA Works fine !/ Message-ID: <td7aa53hrl376b@news.supernews.com>c  	 FYI - Alla  C Installed a KZPCA-AA in PWS433, 500 and 600, XP1000 DS20 and AS1200l   Works fine in all instances=  J Reason I posted this is because I saw a note a couple of weeks ago stating( that these didn't work in PWS systems  -J They''re very quick and also work with th U160 disks which for some reason are cheaper than SCSI-2,    F We are evaluating some other cheap boards next week also: 53C895 based U2Wide cards, no name   K WIll post results - this is a replacement for KZPBA-CA if it works for only 
 about $200   DT     -- David Turner Island Computers US CorporationS 2700 Gregory Streeti Savannah GA 31404y Tel: 912 447 6622  Fax:912 201 0096 sales@islandco.com   ------------------------------  % Date: Tue, 10 Apr 2001 20:26:33 +0100p+ From: "antonio.carlini" <arcarlini@iee.org>S' Subject: Re: Macro VAX/Alpha ISDN Commsm& Message-ID: <3AD35E69.3925B37@iee.org>   Andrew Jones wrote:V  ; > I'm not sure if this is the right place, but here goes...e   [snip]  L > But if I change 57600 to 115200 it doesn't seem to work correctly anymore.   Try leaving it alone :-)  K > It doesn't give any errors, but when watching the comms on a line monitoreJ > connected between the DECserver 700 and an ISDN TA is see the following: >  > At 57600.p > > ATE0V1<cr><lf> > < OK <cr><lf>  > > ATD<number><cr><lf>t > < CONNECTr > etcd >  > At 115200. > > junk > < junk > > ATD<number><cr><lf>t > < junk    F > Should look like the 57600, but obviously the speed is not being set > correctly somewhere.  E > The port on the DECserver was set at the appropriate speed on both.   ( > Any help would be greatly appreciated.   What are you trying to do?2 What setup are you using? What is connected where?7 What is the VAX trying to do (comms via LAT at a guess, + but it would be nice not to have to guess).m  0 What speed were the DECserver and ISDN TA set to( in each case? (And the analyser too ...)$ (You don't state the numbers in each0 case, presumably the hardware doesn't agree with& your ideas about what is appropriate).  3 My random guess (based on insuffucient information)w* is that you think you can programmatically- influence the speed between the DS700 and thev/ TA but in fact you can't. Or worse, you flippedy( the DS700 speed but the TA didn't notice+ (maybe it failed to autobaud, or just won'te% go up to 115200, or the DS700 won't).u   Antonio    -- k   ---------------e- Antonio Carlini             arcarlini@iee.orgu   ------------------------------  # Date: Tue, 10 Apr 2001 19:00:42 GMTs+ From: jcring@switch.com (John C. Ring, Jr.)t2 Subject: Math offtopic (WAS: Compaq & VMS Careers), Message-ID: <9avocn$9hd$1@usenet.switch.com>  w In article <OF0BBCDB43.D9CEB91B-ON03256A2A.0061CE25@ep-bc.petrobras.com.br>, fabio_compaq@ep-bc.petrobras.com.br wrote: ) >probably the way the teachers teach matht! >in our schools is not good ! ! !e  O I went part-way through for a degree in secondary education/mathematics before tN switching to straight math.  From my experiences, I believe a good portion of N the problem is actually rather direct: elementary teachers themselves usually 4 hate math, or at least aren't very excited about it.  M Think about it.  Children are sensitive to the emotional state of the adults AM they deal with.  IMO that means they can definately pick up on what subjects  M their teachers are, and are not, excited about teaching.  This has an affect tK on motivation, as young children [even today] generally want to please the sN adults.  This would also account for the gender difference in mathematics, as M studies have indicated that female children are more concerned with approval 0 from adults then male children.o  < >And at the end, mathematics people will teach at schools orF >the will  work  in specialized  soft companies like geology software.  N Maybe, but I work in IT :)  One could argue that mathematics appeals to those J who like to solve problems, and *that* trait applies to a great number of I fields.  Sure, a lot of those folks will not *major* in mathematics, but  M that's due in part to the [IMO] "training over education" tread, rather then c9 because such peole are poor in, and dislike, mathematics.l   ------------------------------  # Date: Tue, 10 Apr 2001 18:01:09 GMTe2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman); Subject: OpenVMS Frequently Asked Questions (FAQ), Part 1/5 2 Message-ID: <FTHA6.748$fB6.19160@news.cpqcorp.net>   Archive-name: dec-faq/vms/part1s Posting-Frequency: monthly Last-modified: 10 Apr 2001 Version: VMS-FAQ-1.TXT(6)e     Changes since last edition ==========================, Numerous URL and minor text updates, plus... Update DOC2      UTL changes> Update INTRO6    Encompass, Generalize the Chapter Information4 Update FILE4     Large directories, reverse deletion% Added  NET1      OpenVMS and Internet # Added  NET2      OpenVMS and Modems.% Update MAIL3     Narnia moves to WKU. 8 Add    MGMT58    Performing SET HOST/MOP in DECnet-Plus?0 Add    MGMT59    Resolving License PAK Problems?5 Add    MGMT60    Changing the OpenVMS Version Number?D@ Add OV1          Make HTML conversions keep the OVERVIEW visible$ Update SOFT1     Various URL changes$ Update SUPP1     Various URL changesF Add    SUPP9     Which DE500 variant works with which OpenVMS version?+ Update VAX3      VAX-11/750 FAQ unreachableb  Update WIRES1    Various changes  Update WIRES2    Various changes  E This is part 1/5 of the Frequently Asked Questions (FAQ) posting for r= the comp.os.vms and comp.sys.dec newsgroups.  (comp.os.vms iseC bidirectionally-gatewayed to the INFO-VAX mailing list - see INTRO3 > for further details.)  It contains answers to frequently askedB questions about Compaq's OpenVMS operating system and the computer> systems on which it runs.  (Please see INTRO5 before posting.)       Table of Contents - Part 1/5 ____________________________     OVERVIEW( ========================================C OV1.     Overview of the OpenVMS FAQ, Updates, Editor, Contact Infot   Introduction( ========================================* INTRO1.  What is the scope of comp.os.vms?= INTRO2.  What other newsgroups carry VMS-related information?n INTRO3.  What is INFO-VAX?< INTRO4.  How do I subscribe to or unsubscribe from INFO-VAX?F INTRO5.  How do I submit a question or a response?  What is etiquette? INTRO6.  What is DECUS?s= INTRO7.  What archives of comp.os.vms/INFO-VAX are available?hD INTRO8.  Who are the corporate contacts for OpenVMS business issues?   General questions about OpenVMS ( ========================================. VMS1.   What is OpenVMS?  What is its history?7 VMS2.   What is the difference between VMS and OpenVMS?l* VMS3.   How do I port from VMS to OpenVMS?* VMS4.   Which is better - OpenVMS or UNIX?= VMS5.   Is Compaq continuing funding and support for OpenVMS?t3 VMS7.   What OpenVMS CD-ROM products are available?r, VMS8.   In what language is OpenVMS written?2 VMS9.   How do I obtain or transfer a VMS license?= VMS10.  What is OpenVMS doing about the Euro currency symbol?-? VMS11.  Why hasn't OpenVMS been ported to Intel (IA32) systems?i? VMS12.  Are there any general-access OpenVMS systems available?h* VMS13.  What version of OpenVMS do I need?* VMS14.  How can I submit OpenVMS Freeware?( VMS15.  Porting applications to OpenVMS?0 VMS16.  How do I join Compaq Solutions Alliance?    ! Documentation and other resourcesf( ========================================: DOC1.   Where can I find online copies of OpenVMS manuals?- DOC2.   What online information is available? 2 DOC3.   What books and publications are available?5 DOC4.   How do I extract a HELP topic to a text file?r6 DOC5.   Does OpenVMS Marketing have an e-mail address?5 DOC6.   What OpenVMS-related WWW sites are available?aB DOC8.   Where can I find info about undocumented OpenVMS features?@ DOC9.   Where is documentation on the DECnet Phase IV protocols?G DOC10.  Where can I learn about how the VMS executive works internally?-D DOC11.  Where can new users find tutorial information about OpenVMS?C DOC12.  How to access the OpenVMS Netscape Navigator documentation?n   OpenVMS System Time ( ========================================8 TIME1.   A brief history of OpenVMS Timekeeping, please?3 TIME2.   How does OpenVMS VAX maintain system time?e' TIME3.   Why does my system time drift?nD TIME4.   Managing Timezones, Timekeeping, UTC, and Daylight Savings?5 TIME5.   How to troubleshoot TDF problems on OpenVMS?r= TIME6.   How can I keep the OpenVMS system time synchronized?7D TIME7.   How can I configure TCP/IP Services NTP as a time provider?1 TIME8.   How can I drift the OpenVMS system time?i; TIME9.   Why does VAX need a SET TIME at least once a year?e@ TIME10.  Why can't I do a SET TIME command?  Help managing DTSS?: TIME11.  Details of the VAX and Alpha system time-keeping?   Table of Contents - Part 2/5 ____________________________   System ManagementP( ========================================# MGMT1.  What is an installed image? 0 MGMT2.  Are there any known viruses for OpenVMS?1 MGMT3.  How do I mount an ISO-9660 CD on OpenVMS?s4 MGMT4.  How do I extract the contents of a PCSI kit?; MGMT5.  I've forgotten the SYSTEM password - what can I do?n9 MGMT6.  How do I connect a PostScript printer via TCP/IP?o; MGMT9.  How do I change the node name of an OpenVMS System?sE MGMT10. What is the correct value for EXPECTED_VOTES in a VMScluster?n< MGMT11. Why doesn't OpenVMS see the new memory I just added?9 MGMT12. How do I write a BACKUP saveset to a remote tape?D3 MGMT13. Tell me about SET HOST/DUP and SET HOST/HSC 4 MGMT14. How do I install DECnet Phase IV on VMS 7.1?< MGMT15. How do I change the text in a user's UIC identifier?3 MGMT16. What are the OpenVMS version upgrade paths?-G MGMT17. Why do I have negative number in the pagefile reservable pages?aC MGMT18. Do I have to update layered products when updating OpenVMS?h3 MGMT19. How do I change the volume label of a disk?7. MGMT20. How do I fix a corrupt BACKUP saveset?, MGMT21. How can I set up a shared directory?8 MGMT23. Why do I get extra blank pages on my HP Printer?C MGMT24. How do I configure ELSA GLoria Synergy graphics on OpenVMS?l: MGMT25. How do I acquire OpenVMS patches, fixes, and ECOs?. MGMT26. How do I rename a DSSI disk (or tape?)1 MGMT27. How do I move the queue manager database?D> MGMT28. How do I set a default IP route or gateway on OpenVMS?C MGMT30. How do I delete an undeletable/unstoppable (RWAST) process?h* MGMT31. How do I reset the error count(s)?A MGMT32. How do I find out if the tape drive supports compression? ? MGMT33. Can I copy SYSUAF to another version? To VAX? To Alpha?-1 MGMT34. How do I delete (timeout) idle processes?-. MGMT35. Why isn't BACKUP/SINCE=BACKUP working?; MGMT36. How can I set up reverse telnet (like reverse LAT)?i? MGMT37. Do I need a PAK for the DECevent (Compaq Analyze) tool?=6 MGMT38. INITIALIZE ACCVIO and ANSI tape label support?/ MGMT39. How do I recover from INSVIRMEM errors?AI MGMT40. How can I prevent a serial terminal line from initiating a login?R6 MGMT41. How does PCSI use the image BUILD_IDENT field?@ MGMT42. How to configure allocation classes and Multi-Path SCSI?@ MGMT43. How can I tell what software (and version) is installed?@ MGMT44. Where can I get Fibre Channel Storage (SAN) information?. MGMT45. How can I split up an OpenVMS Cluster?; MGMT46. What file checksum tools are available for OpenVMS? 8 MGMT47. Configuring Cluster SCS for path load balancing?; MGMT48. What (and where) is the OpenVMS Management Station?o- MGMT49. Determining disk fragmentation level? @ MGMT50. SYSBOOT-I-FILENOTLOC, Unable to locate SYS$CPU_ROUTINES?F MGMT51. How can I customize the DCPS device control for a new printer?D MGMT52. Why do $GETDEV MOUNTCNT and SHOW DEVICE mount counts differ?8 MGMT53. What software is needed for Postscript printers?D MGMT54. Does volume shadowing require a non-zero allocation classes?9 MGMT56. How do I remove a PCSI-installed patch (ECO) kit?l@ MGMT57. SYSINIT-E, error mounting system device, status=0072832C/ MGMT58. Performing SET HOST/MOP in DECnet-Plus?r' MGMT59. Resolving License PAK Problems? , MGMT60. Changing the OpenVMS Version Number?     Table of Contents - Part 3/5 ____________________________   MAIL( ========================================$ MAIL1.  How do I send Internet mail?J MAIL2.  How do I get IN% or MX% added automatically to Internet addresses?K MAIL3.  How do I automatically append a signature file to my mail messages?pA MAIL4.  Do I have to use VMS MAIL?  I like my Unix mailer better.oL MAIL5.  How can I forward my mail?  Can I forward it to an Internet address?9 MAIL6.  How can I forward my mail to a list of addresses?lJ MAIL7.  MAIL keeps saying I have new messages, but I don't.  What do I do?; MAIL8.  How do I extract all of my mail messages to a file?-6 MAIL9.  How do I send or read attachments in VMS MAIL?     Other Utilitiest( ========================================4 UTIL1.  How do I play an audio CD on my workstation?: UTIL2.  How do I access a MS-DOS floppy disk from OpenVMS?L UTIL3.  How do I play sound files on an AlphaStation?  DECsound doesn't work3 UTIL4.  Why is DECmigrate not working with Fortran?e2 UTIL5.  How do I read IBM EBCDIC tapes on OpenVMS?/ UTIL6.  How can I patch an OpenVMS Alpha image?-     DCL and command usage ( ========================================. DCL1.   How do I run a program with arguments?/ DCL2.   How can I redefine control keys in DCL?c* DCL3.   How can I clear the screen in DCL?< DCL4.   Using REPLY/LOG from DCL?  Disabling Console OPCOMs?1 DCL5.   How do I generate a random number in DCL?h% DCL6.   What does the MCR command do?a2 DCL7.   How do I change the OpenVMS system prompt?< DCL8.   Can I do DECnet task-to-task communication with DCL?6 DCL9.   How can I get the width setting of a terminal?/ DCL10.  How can I substitute symbols in a PIPE?n, DCL11.  Use of RUN/DETACH and logical names?8 DCL12.  How to use escape and control characters in DCL?   File System and RMSC( ========================================" FILE1.  How can I undelete a file?B FILE2.  Why does SHOW QUOTA give a different answer than DIR/SIZE?B FILE3.  How do I make sure that my data is safely written to disk?C FILE4.  What are the limits on file specifications and directories?a@ FILE5.  What is the largest disk volume size OpenVMS can access?E FILE6.  What is the maximum file size, and the RMS record size limit?u1 FILE7.  How do I write recordable CDs on OpenVMS? 7 FILE8.  What I/O transfer size limits exist in OpenVMS?o< FILE9.  Can I use ODBC to connect to OpenVMS database files?     ProgrammingC( ========================================: PROG1.  How do I call <routine_name> from <language_name>?9 PROG2.  How do I get the arguments from the command line? = PROG3.  How do I get a formatted error message in a variable?dD PROG4.  How do I link against SYS$SYSTEM:SYS.STB on an Alpha system?8 PROG5.  How do I do a SET DEFAULT from inside a program?M PROG6.  How do I create a shareable image transfer vector on an Alpha system? H PROG7.  How do I turn my Fortran COMMON into a shareable image on Alpha?< PROG8.  How do I convert between IEEE and VAX floating data?= PROG9.  How do I get the argument count in a Fortran routine?e? PROG10. How do I get a unique system ID for licensing purposes?a? PROG11. What is an executable, shareable, system or UWSS image?d/ PROG12. How do I do a file copy from a program?u PROG13. What is a descriptor?k+ PROG14. How many bytes are in a disk block? , PROG15. How many bytes are in a memory page?9 PROG16. How do I create a process under another username?lD PROG17. Why do lib$spawn, lib$set_symbol fail in detached processes?I PROG18. Where can I obtain Bliss, and the libraries and supporting files?e0 PROG19. How can I open a file for shared access?> PROG20. How can I have common sources for messages, constants?C PROG21. How do I activate the OpenVMS Debugger from an application?    Table of Contents - Part 4/5 ____________________________  
 DECwindows( ========================================F DECW1.  How do I let someone else display something on my workstation?9 DECW2.  How do I create a display on another workstation?0F DECW3.  How can I get the information from SHOW DISPLAY into a symbol?0 DECW4.  How do I get a log of a DECterm session?E DECW5.  Problem - the DELETE key deletes forward instead of backward!,- DECW6.  Why is DECwindows Motif not starting?n3 DECW9.  How do I set the title on a DECterm window?oB DECW10. How do I customize DECwindows, including the login screen?4 DECW11. Why doesn't XtAppAddInput() work on OpenVMS?B DECW12. Why do the keyboard arrow keys move the DECwindows cursor?2 DECW13. Why does half my DECwindows display blank?B DECW14. %DECW-W-NODEVICE, No graphics device found on this system?0 DECW15. How can I reset the warning bell volume?2 DECW16. How can alter the DECwindows CDE backdrop?8 DECW17. How can I enable the DECwindows TCP/IP Transport    
 Miscellaneous2( ========================================G MISC2.    Where can I find information on escape and control sequences?pE MISC6.    What does "failure on back translate address request" mean?A8 MISC7.    How to determine the network hardware address?I MISC8.    Why does my system halt when I powercycle the console terminal?rB MISC9.    Why can't I use PPP and RAS to connect to OpenVMS Alpha?@ MISC12.   Does DECprint (DCPS) work with the LRA0 parallel port?; MISC13.   How do I check for free space on a (BACKUP) tape?l* MISC14.   So what happened to sys$cmsuper?< MISC15.   How can I send radio pages from my OpenVMS system?< MISC17.   How do I reset the LAN (DECnet-Plus NCL) counters?6 MISC18.   What are the prefixes for the powers of ten?6 MISC19.   OpenVMS Cluster (SCS) over DECnet?  Over IP?/ MISC20.   Correctly using license PAKs and LMF?nD MISC21.   Third-party disk/tape/controllers/SCSI/widgets on OpenVMS?     Software( ========================================C SOFT1.    Where can I find freeware/shareware/software for OpenVMS?p@ SOFT2.    Where can I find the UNIX <whatever> tool for OpenVMS?I SOFT3.    Where can I get the Netscape Navigator Mozilla.org Web Browser?)+ SOFT4.    Where can I get Java for OpenVMS?TJ SOFT5.    VAX C and DEC C, and other OpenVMS C Programming Considerations?1 SOFT6.    Obtaining user input in DCL CGI script? 1 SOFT7.    How do I get my own batch entry number? 0 SOFT8.    How do I convert to new CMS libraries?B SOFT9.    Where can I get new certificates for Netscape Navigator?3 SOFT10.   Why doesn't DCL symbol substitution work?t+ SOFT12.   Where can I get Perl for OpenVMS? 4 SOFT13.   Where can I get DECmigrate (VEST and TIE)?     Table of Contents - Part 5/5 ____________________________   Alpha and Alpha-based systemso( ========================================, ALPHA1.   What do the letters AXP stand for?A ALPHA2.   What are the OpenVMS differences between VAX and Alpha?,F ALPHA5.   Seeking performance information for Alpha (and VAX) systems?E ALPHA6.   Where can I get updated console firmware for Alpha systems?3D ALPHA7.   How do I boot an AlphaStation without monitor or keyboard?= ALPHA8.   Will OpenVMS run on a Multia? AlphaPC 164LX? 164SX? C ALPHA9.   What is the least expensive system that will run OpenVMS?e< ALPHA10.  Where can I get more information on Alpha systems?, ALPHA11.  What are the APB boot flag values?7 ALPHA12.  What are Alpha console environment variables?e0 ALPHA13.  Will OpenVMS run on a NoName AXPpci33?D ALPHA14.  How do I reload SRM firmware on a half-flash Alpha system?2 ALPHA15.  Will OpenVMS run on the Alpha XL series?G ALPHA16.  Describe Alpha instruction emulation and instruction subsets?uJ ALPHA17.  What is the Accuracy of the Alpha Time of Year (BB_WATCH) Clock?3 ALPHA18.  So how do I open up the DEC 3000 chassis?t! ALPHA19.  What is byte swizzling?s? ALPHA20.  What commands are available in the Alpha SRM console?aA ALPHA21.  How do I switch between AlphaBIOS/ARC and SRM consoles?e@ ALPHA22.  OpenVMS on the Personal Workstation -a and -au series?9 ALPHA23.  OpenVMS and Personal Workstation IDE bootstrap? B ALPHA24.  Which terminal device name is assigned to the COM ports?     VAX and VAX-based systems)( ========================================8 VAX1.   Please explain the back panel of the MicroVAX II< VAX2.   What is the layout of the VAX floating point format?2 VAX3.   Where can I find more info on VAX systems?? VAX4.   Where can I find information on NetBSD for VAX systems?hH VAX5.   What system disk size limit on the MicroVAX and VAXstation 3100?* VAX7.   What are the VMB boot flag values?> VAX9.   Which serial port is the console on the MicroVAX 3100?> VAX10.  How can I set up an alternate console on a VAXstation?  ' Hardware and Software Support resourcesw( ========================================B SUPP1.  Where can I get software and hardware support information?E SUPP2.  Where can I get hardware self-maintenance support assistance?=H SUPP3.  Why does my system halt when I power-cycle the console terminal?? SUPP4.  Can I reuse old keyboards, mice and monitors with a PC?rA SUPP5.  Which video monitor works with which graphics controller? 8 SUPP6.  Where can I get information on storage hardware?< SUPP7.  Problem - My LK401 keyboard unexpectedly autorepeatsI SUPP8.  Problem - My LK411 sends the wrong keycodes or some keys are deads= SUPP9.  Which DE500 variant works with which OpenVMS version?n    ! SCSI-related Hardware informationM( ========================================< SCSI1.  Are the 2X-KZPCA-AA and SN-KZPCA-AA LVD Ultra2 SCSI?, SCSI2.  Resolving DRVERR fatal device error?    F Wiring-, Adapter-, Connector-, and Pinout-related Hardware information( ========================================- WIRES1. Looking for connector wiring pinouts?s: WIRES2. What connectors and wiring adapters are available?2 WIRES3. What is flow control and how does it work?  
 Networking( ========================================. NET1.  How to connect OpenVMS to the Internet?) NET2.  How to connect OpenVMS to a Modem?a  < ------------------------------------------------------------@ OV1.  Overview of the OpenVMS FAQ, Updates, Editor, Contact Info    9   The OpenVMS FAQ is archived in the following locations:_  "     http://www.openvms.compaq.com/.     ftp://rtfm.mit.edu/pub/usenet/comp.os.vms/,     comp.answers and news.answers newsgroups  A   Other internet FAQs are generally available in these locations:   ,     comp.answers and news.answers newsgroups%     ftp://rtfm.mit.edu/pub/usenet/...f  ?   User-created HTML versions of the OpenVMS FAQ are located at:        http://www.kjsl.com/vmsfaq'     http://eisner.decus.org/vms/faq.htmr  I Please do NOT send technical questions to the Frequently Asked Questions sH (FAQ) editor -- well, please do not email any questions that do not alsoG include the answer(s).  Please post these questions to the appropriate  I newsgroup instead -- and see INTRO5 before posting.  To make suggestions  G for changes or additions to this FAQ list, please send mail to the FAQ MH editor at the address listed in the sig file.  Again, the FAQ editor is 0 *not* in a position to answer general questions.   Some general notes:t  L The term "VMS" is synonymous with "OpenVMS".  "Alpha", "AlphaGeneration" or G "AXP" generally refers to any system or product based on or related to  J Compaq's Alpha processor architecture.  OpenVMS manual names mentioned areC those as of V7.2 -- names may be different in other editions of ther documentation set.  H World-Wide Web Universal Resource Locator (URL) notation is used for FTP
 addresses.  F Many people have contributed to this list, directly or indirectly.  InG some cases, an answer has been adapted from one or more postings on theeD comp.os.vms newsgroup.  Our thanks to all of those who post answers.H The name (or names) at the end of an entry indicate that the informationD was taken from postings by those individuals; the text may have beenG edited for this FAQ.  These citations are only given to acknowledge thee
 contribution.h  A Although the editor of this FAQ is an employee of Compaq ComputeraA Corporation, this posting is not an official statement of Compaq.f  L AlphaGeneration, AlphaServer, AlphaStation, Alpha AXP, AXP, DEC, DECstation,J DECsystem, OpenVMS, ULTRIX, VAX and VMS are trademarks of Compaq.  Compaq M and the names of Compaq products are trademarks and/or registered trademarks aL and/or service marks of Compaq Computer Corporation.  OSF/1 is a registered K trademark of the Open Software Foundation.  UNIX is a registered trademark  G in the United States and other countries, licensed exclusively through eK X/Open Company Ltd.  Other names are properties of their respective owners.k      < ------------------------------------------------------------* INTRO1.  What is the scope of comp.os.vms?  E The comp.os.vms newsgroup is the primary newsgroup for discussion of TF Compaq's OpenVMS operating system and the computer systems on which itE runs.  Questions about layered products which run on OpenVMS are also C welcome, though many of them (in particular, language compilers andDC database systems) have more specific newsgroups.  If a question hasa. some relationship to OpenVMS, it belongs here.  < ------------------------------------------------------------= INTRO2.  What other newsgroups carry VMS-related information?r  D The vmsnet.* hierarchy, run by DECUS, contains several newsgroups ofI interest, including vmsnet.misc and vmsnet.alpha, the latter being mostly ; devoted to Alpha topics.  There's also vmsnet.sources (and  J vmsnet.sources.d) to which sources for or pointers to freeware are posted.F See the separate "What is VMSNET" monthly posting for further details.  C The comp.sys.dec newsgroup carries discussions about Compaq systemsh, acquired from Digital Equipment Corporation.  < ------------------------------------------------------------ INTRO3.  What is INFO-VAX?  D INFO-VAX is a mailing list which is bidirectionally gatewayed to theC comp.os.vms newsgroup.  This means that postings to comp.os.vms getOL automatically sent to INFO-VAX subscribers and messages sent to the INFO-VAXK list are automatically posted to comp.os.vms.  INFO-VAX can be a useful way F to participate in the newsgroup if you can't access the group directly through a news reader.  H An important point to keep in mind is that propagation delays vary, bothD within the newsgroup and with INFO-VAX mailings.  It's possible thatI postings may not be delivered for several days and some may appear out ofi order.  < ------------------------------------------------------------< INTRO4.  How do I subscribe to or unsubscribe from INFO-VAX?  H The address for subscription requests, as well as notes intended for theO moderator, is Info-VAX-Request@Mvb.Saic.Com.  Subscription requests are handledsN automatically by a mail server.  This mail server ignores the subject line andL processes each line of the message as a command.  The syntax for subscribing< and unsubscribing and setting digest or non-digest modes is:  s0 SUBSCRIBE INFO-VAX      (ADD is a valid synonym)G UNSUBSCRIBE INFO-VAX	(REMOVE, SIGNOFF, and SIGN-OFF are valid synonyms) 5 SET INFO-VAX DIGEST     (to receive in Digest format)E> SET INFO-VAX NODIGEST   (to receive each message individually)   K Case is irrelevant and attempts to fetch a copy of the mailing list will betJ rejected (I consider the information to be confidential).  Any message notI understood by the mailserver will be forwarded to a human (allegedly) for  manual processing.  				[Mark.Berryman@Mvb.Saic.Com]  > If you are on Bitnet, send a mail message containing the text L "SUBSCRIBE INFO-VAX" to LISTSERV@(nearest listserv system).  To unsubscribe,L send a message containing the text "SIGNOFF INFO-VAX" to the *SAME* listserv	 address.    C If you are on the Internet in the UK, send a message containing theeF word SUBSCRIBE (or UNSUBSCRIBE) to info-vax-request@ncdlab.ulcc.ac.uk.  < ------------------------------------------------------------F INTRO5.  How do I submit a question or a response?  What is etiquette?  J If you are using a news reader, post your question to comp.os.vms.  If youK want to submit through INFO-VAX, send the message to Info-VAX@mvb.saic.com.   J Before posting, please use available local resources, such as the manuals,L HELP and this FAQ first.  Also make a point of reading the release notes forJ the product you're using, generally placed in SYS$HELP.  Often you'll findM the answer, and will save time and effort for all concerned.  (And you won't _ "annoy the natives"...)   8 When posting, please consider the following suggestions:  E     1.  Include a valid e-mail address in the text of your posting oriD         in a "signature" appended to the end.  Reply-to addresses in 	headers often get garbled.s  F     2.  If you are submitting a question, please be as specific as youJ         can.  Include relevant information such as processor type, productF 	versions (OpenVMS and layered products that apply), error message(s),M         DCL command(s) used, and a short, reproducible example of problems.   M         Say what you've tried so far, so that effort isn't duplicated.  Keep  K         in mind that there's not yet a telepathy protocol for the Internet.=M         (The more detailed your description, the better that people can help o          you with your question.)  I     3.  If responding to a posting, include in your reply only as much ofoF         the original posting as is necessary to establish context.  AsE 	a guideline, consider that if you've included more text than you've nE 	added, you've possibly included too much.  Never include signatures = 	and other irrelevant material.   E     4.  Be polite.  If the question isn't worded the way you think isyC         correct or doesn't include the information you want, try to > 	imagine what the problem might be if viewed from the poster's< 	perspective.  Requests for additional information are often> 	better sent through mail rather than posted to the newsgroup.  J     5.  If you have a problem with Compaq (or any other vendor's) product,F         please use the appropriate support channel.  Don't assume that? 	newsgroup postings will get read, will be responded to by the  B         appropriate developers, or will be later followed up on...  I     6.  If you are posting from a web browser, news reader or if you are eI         posting via email sent to INFO-VAX, please turn off MIME, vcard, SI         attachments, and other mechanisms that assume anyone reading the IJ         post has the corresponding capability -- use the text-only option M         of your web browser, news reader, or mailer.  Usenet is traditionallyaF 	a text-only medium, and many comp.os.vms participants will use tools C 	that have this support disabled, or that do not have this support.xC 	If the message uses MIME or attachments or such, the text of your sE 	message will be buried in a large pile of gibberish, and some tools R? 	will send multiple copies of the text within a single posting.   J Before posting your question to the comp.os.vms newsgroup or sending your L message to the INFO-VAX list, also please take the time to review available H etiquette information, such as that included in the following documents:  @   ftp://rtfm.mit.edu/pub/usenet/news.answers/usenet/primer/part1=   ftp://rtfm.mit.edu/pub/usenet/news.answers/usenet/faq/part1OH   ftp://rtfm.mit.edu/pub/usenet/news.answers/usenet/emily-postnews/part1G   ftp://rtfm.mit.edu/pub/usenet/news.answers/usenet/writing-style/part1rG   ftp://rtfm.mit.edu/pub/usenet/news.answers/usenet/posting-rules/part1s  G This information will document the etiquette of newsgroups, as well as GF providing you with the knowledge the vast amount of newsgroup-related E information that is readily available to you, and where to find it...t  < Please ***DO NOT POST SECURITY HOLES OR SYSTEM CRASHERS ***.  I Rather, please report these problems directly to Compaq.  (Why?  So that eJ Compaq has a change to resolve and distribute a fix before other customer L sites can be affected.  Most folks in the newsgroups are honest and deserve M to know about potential security problems, but a few folks can and will make  K nefarious use of this same information.  Other sites will hopefully return _J the favor, and not post information that will potentially compromise YOUR # site and YOUR computer environment.   < ------------------------------------------------------------ INTRO6.  What is DECUS?a  D DECUS, the Digital Equipment Computer Users Society, is a World WideF organization of Information Technology professionals interested in theC products, services, and technologies of Compaq and related vendors.     CJ Membership in the Chapter is free and provides participants with the meansI to enhance their professional development, forums for technical training, G mechanisms for obtaining up-to-date information, advocacy programs, andkG opportunities for informal disclosure and interaction with professionalD colleagues of like interest.  A For further information, see the separate monthly "What is DECUS 5E (Encompass)" posting, or refer to the US DECUS (Encompass) webserver EI at http://www.decus.org/ and to the links to other chapters at that site.s  < ------------------------------------------------------------= INTRO7.  What archives of comp.os.vms/INFO-VAX are available?l  : Everything posted since 1990 is archived and available at:   ftp://crvax.sri.com/info-vax/    					[Arne Vajhj]  < ------------------------------------------------------------D INTRO8.  Who are the corporate contacts for OpenVMS business issues?  <   The following folks are the Compaq corporate contacts for ?   OpenVMS business issues, listed in descending order from the r@   Comoaq Corporate President to the OpenVMS Vice President (VP).     1     Michael Capellas     Compaq President and CEOO9                          Michael.Capellas[-at-]Compaq.Comu  D     Bill Heil            VP, Business Critical Servers Business Unit2                          Bill.Heil[-at-]Compaq.Com  =     Don Harbert          VP, High Performance Server Division 4                          Don.Harbert[-at-]Compaq.Com  8     Rich Marcello        VP, Open Systems Software Group9                          Richard.Marcello[-at-]Compaq.Comr  D   These folks will obviously respond best to cogently-worded OpenVMSG   corporate business issues.  These folks are NOT appropriate contacts oH   for any OpenVMS technical support issues or support requests, nor for ?   any other non-corporate-related, non-business-related issues. 9                                          [Atlant Schmidt]I  < ------------------------------------------------------------. VMS1.   What is OpenVMS?  What is its history?  N OpenVMS, originally called VMS (Virtual Memory System), was first conceived inL 1976 as a new operating system for the then-new, 32-bit, virtual memory lineN of computers, eventually named VAX (Virtual Address eXtension).  The first VAXI model, the 11/780, was code-named "Star", hence the code name for the VMS=M operating system, "Starlet", a name that remains to this day the name for theaI system library files (STARLET.OLB, etc.).  VMS version X0.5 was the firstrN released to customers, in support of the hardware beta test of the VAX-11/780,D in 1977.  VAX/VMS Version V1.0 shipped in 1978, along with the first revenue-ship 11/780s.o  L OpenVMS was designed entirely within Compaq (Digital Equipment Corporation).G The principal designers were Dave Cutler and Dick Hustvedt, with a wideHK variety of other contributors.  OpenVMS was conceived as a 32-bit, virtual tJ memory successor to the RSX-11M operating system for the PDP-11.  Many of K the original designers and programmers of OpenVMS had worked previously on rE RSX-11M, and many concepts from RSX-11M were carried over to OpenVMS.S  F OpenVMS VAX is a 32-bit, multitasking, multiprocessing virtual memory H operating system. Current implementations run on VAX systems from Compaq and other vendors.  G OpenVMS Alpha is a 64-bit multitasking, multiprocessing virtual memory  C operating system. Current implementations run on Alpha systems frome Compaq, and other vendors.   				[Paul Winalski]w 				[Arne Vajhj]n  G For more details on OpenVMS and its features, read the OpenVMS Softwares Product Description at:   !   http://www.compaq.com/info/spd/p:   OpenVMS typically uses SPD 25.01.xx and/or SPD 41.87.xx.  A Additional information on the general features of various OpenVMS=@ releases, release dates, as well as the development project code, names of specific releases, is available at:  G   http://www.openvms.compaq.com/openvms/os/openvms-release-history.html   J Additional historical information -- as well as pictures and a variety of > other trivia -- is available in the VAX 20th anniversary book:  8   http://www.openvms.compaq.com/openvms/20th/vmsbook.pdf  E For information on the FreeVMS project (also see the related software $ licensing topics VMS9, ALPHA4), see:     http://www.free-vms.org/  < ------------------------------------------------------------7 VMS2.   What is the difference between VMS and OpenVMS?   I VMS and OpenVMS are two names for the same operating system.  Originally,.D the operating system was called VAX-11/VMS; it changed to VAX/VMS atE around VAX/VMS V2.0.  When the VMS operating system was ported to the G Alpha platform, it was renamed OpenVMS, for both VAX and Alpha, in part D to signify the high degree of support for industry standards such as5 POSIX, which provides many features of UNIX systems. y  H For those versions with POSIX, an OpenVMS license allows you to install G and run POSIX for OpenVMS at no additional charge; all you need is the oL media and documentation which can be found on the Consolidated Distribution I and On-Line Documentation CD-ROMs.  Support for the POSIX package on morerH recent OpenVMS releases is not available, various parts of POSIX such asI calls from the API are being integrated more directly into OpenVMS.  For c4 more information on POSIX for VMS see question SOFT2  C What became confusing is that the OpenVMS name was introduced firsttF for OpenVMS AXP V1.0 causing the widespread misimpression that OpenVMSF was for Alpha AXP only, while "regular VMS" was for VAX.  In fact, theI official name of the VAX operating system was changed as of V5.5, though  E the name did not start to be actually used in the product until V6.0.   G The proper names for OpenVMS on the two platforms are now "OpenVMS VAX"o@ and "OpenVMS Alpha", the latter having superseded "OpenVMS AXP".   				[Arne Vajhj]d  < ------------------------------------------------------------* VMS3.   How do I port from VMS to OpenVMS?  9 You already did.  Wasn't that easy?  (See question VMS2.)b  < ------------------------------------------------------------* VMS4.   Which is better - OpenVMS or UNIX?  M This question comes up periodically, usually asked by new subscribers who areqM long-time UNIX users. Sometimes, it is ignored totally; other times, it leadsoN to a long series of repetitive messages that convince no one and usually carryD little if any new information.  Please do everyone a favor and avoid- re-starting this perpetual, fruitless debate.n 					[leichter@lrw.com]F  F Seriously, OpenVMS and the better implementations of UNIX are all fineE operating systems, each with its strengths and weaknesses.  If you'reeE in a position where you need to choose, select the one that best fitssC your own requirements, considering, for example, whether or not thee@ layered products or specific OS features you want are available.   					[Steve Lionel]r  < ------------------------------------------------------------= VMS5.   Is Compaq continuing funding and support for OpenVMS?.   Yes.  ? Active development of new OpenVMS releases is underway, as wellP as the continuation of support.c  @ Please see the following URLs for details, roadmaps, and related information:      http://www.compaq.com/openvms/5   http://www.openvms.compaq.com/OPENVMS/strategy.htmltD   http://www.openvms.compaq.com/openvms/roadmap/openvms_roadmaps.htm-   http://www.openvms.compaq.com/openvmstimes/i   http://www.compaq.com/inform/t  < ------------------------------------------------------------' [VMS6 removed, replaced by Y2K section]   < ------------------------------------------------------------3 VMS7.   What OpenVMS CD-ROM products are available?a  $ Various distributions are available.  B For information on the available part numbers and current productsF (OpenVMS distribution kits, media, documentation, etc) and associated K licensing information, please see the OpenVMS Software Product Description / (SPD), available at:  !   http://www.compaq.com/info/spd/a:   OpenVMS typically uses SPD 25.01.xx and/or SPD 41.87.xx.  F The following CD-ROMs contain just the OpenVMS Alpha operating system.> These are bootable, and can be used to run BACKUP from CD-ROM.  >   QA-MT1AP-H8   OpenVMS Alpha V6.1-1H2 hardware release CD-ROM>   QA-MT1AG-H8   OpenVMS Alpha V6.2-1H3 hardware release CD-ROM>   QA-MT1AD-H8   OpenVMS Alpha V7.1-1H1 hardware release CD-ROM?   QA-MT1AR-H8   OpenVMS Alpha V7.1-2 maintenance release CD-ROMs?   QA-MT1AT-H8   OpenVMS Alpha V7.2-1 maintenance release CD-ROMt>   QA-MT1AU-H8   OpenVMS Alpha V7.2-1H1 hardware release CD-ROM  J The following are the consolidated ECO distribution kit subscriptions, andH these provide sites with eight updates of the current ECO kits per year:     QT-3CQAA-C8   OpenVMS Alpha-   QT-3CRAA-C8   OpenVMS VAX-  E OpenVMS VAX and OpenVMS Alpha source listings CD-ROM sets include thefI source listings of most of OpenVMS, and these CD-ROM sets are invaluable oG for any folks working directly with OpenVMS internals, as well as folksg@ interested in seeing examples of various programming interfaces.  4   QB-MT1AB-E8   OpenVMS Alpha Source Listings CD-ROM<   QT-MT1AB-Q8   OpenVMS Alpha Source Listings CD-ROM Updates2   QB-001AB-E8   OpenVMS VAX Source Listings CD-ROM:   QT-001AB-Q8   OpenVMS VAX Source Listings CD-ROM Updates  d< ------------------------------------------------------------, VMS8.   In what language is OpenVMS written?  2 OpenVMS is written in a wide variety of languages.  H In no particular order, OpenVMS components are implemented using Bliss, I Macro, Ada, PLI, VAX and DEC C, Fortran, UIL, VAX and Alpha SDL, Pascal, sG MDL, DEC C++, DCL, Message, and Document.  And this is certainly not a .G complete list. However, the rumor is NOT true that an attempt was made fC to write pieces of OpenVMS in every supported language so that the pG Run-Time Libraries could not be unbundled.  (APL, BASIC, COBOL and RPG n0 are just some of the languages NOT represented!)  I There are a large variety of small and not-so-small tools and DCL commandeI procedures that are used as part of the OpenVMS build, and a source code -K control system capable of maintaining over a hundred thousand source files dH across multiple parallel development projects, and overlapping releases.  < ------------------------------------------------------------2 VMS9.   How do I obtain or transfer a VMS license?  H If you are a DECUS member and are considering acquiring and using a VAX G or Alpha system for hobbyist (non-commercial) use, (free) licenses for iB OpenVMS VAX and OpenVMS Alpha are available to DECUS members.  In D addition to the license, VAX and Alpha distribution CD-ROM kits are H available with OpenVMS, DECwindows Motif, DECnet and TCP/IP networking, - compilers, and a variety of layered products.a  ! For further information, link to:a  #   http://www.montagar.com/hobbyist/m  E Further information on DECUS and on DECUS membership is available at:t     http://www.decus.org/e  E For information on licenses for educational customers, see the CompaqaA CSLG license program and the OpenVMS Educational license program:      http://www.openvmsedu.com/  C To transfer a commercial OpenVMS license from one owner to another,sD or to purchase a commercial license, you can contact Compaq ComputerA Corporation at 1-800-DIGITAL (in North America), or your local ore regional sales office.  E Commercial developers can join the CSA program, and can (potentially)sC receive discounts on various software product licenses and software-D distributions, as well as on hardware purchases.  Please see ALPHA4.   					[Stephen Hoffman]6                                         [Scott Snadow]  < ------------------------------------------------------------= VMS10.  What is OpenVMS doing about the Euro currency symbol?b  B For information on the current status and plans for support of the? European Monetary Union's Euro currency symbol in OpenVMS, see:'  %   http://www.openvms.compaq.com/euro/O  < ------------------------------------------------------------? VMS11.  Why hasn't OpenVMS been ported to Intel (IA32) systems?n   Why?  Business reasons...   B Because there is a belief that there would be no market to justifyA the effort and the expense involved in porting OpenVMS to systemseA using the Intel IA32 architecture.  (Each maintainer of a product.A or package for OpenVMS would have to justify the port to "OpenVMS D IA32", akin to a port from OpenVMS VAX to OpenVMS Alpha.  The effort8 involved in porting OpenVMS from VAX to Alpha was huge.)  B Because every one of the core applications would have to be portedB from Alpha to IA32, and then customer and third-party applications would also have to be ported.   C Because there are design features that required by OpenVMS that arehF not available on IA32, features that would require redesigning OpenVMSB to operate in the environment, making ports rather more difficult.; ASTs and interlocked operators are obvious prerequirements.o  C Because Alpha is faster than Intel IA32 systems -- if OpenVMS is to ? be ported, a port to a slower system is more difficult to sell.   @ Because Intel is expecting to replace IA32 processors with IA64.  B Because hobbyists have been easily able to acquire OpenVMS systems( and the DECUS hobbyist OpenVMS licenses.  @ Because OpenVMS already operates on Compaq and third-party AlphaF systems; specific features in support of third-party vendor-customizedD bootstrap capabilities for use on third-party systems are present in( OpenVMS Alpha V7.1-2 and later releases.  C Because there are assumptions that some of the stability of OpenVMStD arises from the stability of the underlying VAX and Alpha hardware, C and systems based on components such as ISA and random memory SIMMsr might not be as stable.   " But yes, it would be nice to have.  <                                            [Stephen Hoffman]  < ------------------------------------------------------------? VMS12.  Are there any general-access OpenVMS systems available?h   Yes.  
   o Hobbes  ?       Hobbes is a MicroVAX 3100 Model 40 for which free access p>       and accounts are available to OpenVMS enthusiasts. This C       system has BASIC, Pascal, Fortran, and C compilers installed.xD       If you would like an account on Hobbes, please see the FAQ at:  $         http://www.hobbesthevax.com/  5       This system is strictly for non-commercial use.t  E                                      [Scott Squires, Steven Shamlian]p     o OpenVMS Galaxy Test DriveR  B       Compaq currently offers an OpenVMS Galaxy Test Drive system,F       based on an AlphaServer 4100 series configured as two instances @       of the OpenVMS operating system.  For details, please see:  /         http://www.testdrive.compaq.com/galaxy/      o Compaq CSA Test Drive:  &       http://www.testdrive.compaq.com/   < ------------------------------------------------------------* VMS13.  What version of OpenVMS do I need?  6 For information on supported platforms, please see the2 OpenVMS Software Product Description (SPD) for the' particular OpenVMS version of interest.t  !   http://www.compaq.com/info/spd/o:   OpenVMS typically uses SPD 25.01.xx and/or SPD 41.87.xx.  6 For a table of OpenVMS versions for various platforms, please see:e  9   http://www.openvms.compaq.com/openvms/supportchart.htmll  : For information on the Multia, related Alpha single-board : computers, or other officially unsupported systems, please see ALPHA8 and ALPHA13.s  < The following is a rule-of-thumb for Alpha platform support.; The table contains the earliest OpenVMS Alpha release with  9 support for a particular series of Alpha microprocessors:e  $ Microprocessor | OpenVMS   | General%   Generation   | Version   | Comments   G   21064  EV4   : V1.0      : few systems; most EV4 req later; upg avail 5   21164  EV5   : V6.2      : subsequent upg available =   21164A EV56  : V6.2-1H3  : subsequent upg to V7.1 and latertH   21264  EV6   : V7.1-2    : subsequent upg typically to V7.2-1 or laterH   21264A EV67  : V7.1-2    : subsequent upg typically to V7.2-1 or laterE   xxxxxx EV68  : V7.2-1    : believed/probable; currently expectationi    < ------------------------------------------------------------* VMS14.  How can I submit OpenVMS Freeware?  ?   For the guidelines and submission info, please visit the URL:n  @     http://www.openvms.compaq.com/openvms/freeware/cd_guide.html  B   To order a Freeware CD-ROM kit, request part number QA-6KZAA-H8.  < ------------------------------------------------------------( VMS15.  Porting applications to OpenVMS?  C Porting can range from simple to rather complex, and depends on the ' features used on the original platform.D  A This section covers generic porting, and porting from OpenVMS VAXk@ to OpenVMS Alpha.  (Porting from OpenVMS VAX to OpenVMS Alpha is@ often quite simple and involves little more than rebuilding fromF source, though a few applications using features specific to VAX will ( require some additional effort to port.)  A Several manuals on porting from OpenVMS VAX to OpenVMS Alpha are -B available in the OpenVMS documentation set, including information A on porting VAX Macro32 assembler code to the Macro32 compiler on pB OpenVMS Alpha, on management differences, on upgrading privileged   code, and application migration:  %   http://www.openvms.compaq.com:8000/P$   http://www.openvms.compaq.com/doc/+   http://www.openvms.compaq.com/commercial/   : Details on the C programming environment are available at:  9   http://www.openvms.compaq.com/commercial/c/c_index.html   : Details on porting VAX C to Compaq C are are available at:  :   http://www.openvms.compaq.com/commercial/c/index_vax.htm  + An OpenVMS Porting Library is available at:   9   http://www.openvms.compaq.com/ebusiness/Technology.html   A Information on the Enterprise Toolkit, a Visual-based developmentkE environment for developing applications for OpenVMS using a Microsoftu platform, is available at:  ;   http://www.openvms.compaq.com/commercial/et/et_index.htmlp  L Details on DCE, CORBA, BridgeWorks, and COM/DCOM middleware is available at:  :   http://www.openvms.compaq.com/commercial/middleware.html  1 Information on the COE standards is available at:-     http://diicoe.disa.mil/coe/-  C A wide variety of programming development tools and middleware are  A available as commercial products (eg: DECset, IBM MQseries), and  C various tools are also available as shareware or Freeware.  Please  / see other sections of this FAQ, and please see:s  &   http://www.compaq.com/csa/directory/  8< ------------------------------------------------------------0 VMS16.  How do I join Compaq Solutions Alliance?  G The Compaq Solutions Alliance (CSA) is a (free) program that is open tovH and that supports software partners, consultants, and service providers:     http://www.compaq.com/csa/  H CSA provides members with discounts on hardware, porting assistance, and many other benefits.  H For those familiar with the program, the DIGITAL Association of SoftwareG and Application Parterns (ASAP) program has been incorporated into CSA.H  H The Compaq Solutions Alliance Technical Journal (CTJ) is "web-published" monthly, and available at:  3   http://csa.compaq.com/CompaqTechnicalJournal.html   < ------------------------------------------------------------: DOC1.   Where can I find online copies of OpenVMS manuals?  D The Compaq OpenVMS and layered product documentation is copyrighted 	 material.u  C HTML format on-line product documentation sets for specific Compaq s, OpenVMS products are presently available at:  %   http://www.openvms.compaq.com:8000/s$   http://www.openvms.compaq.com/doc/+   http://www.openvms.compaq.com/commercial/s  F Documentation is offered on separately orderable CD-ROM media through J a subscription to the Consolidated On-Line Documentation (ConOLD) product M (see VMS7.)  ConOLD manuals are readable with BNU, a viewer that is supplied  K with the documentation distribution.  BNU can display HTML, Bookreader, and ! documentation in other formats.  n  E MGBOOK, a viewer for Bookreader-format documentation is available foraI character-cell terminals (eg. VTxxx) via the WKU VMS Freeware file servero" -- see question SOFT1 for details. 					[Steve Lionel]h 					[Stephen Hoffman]    < ------------------------------------------------------------- DOC2.   What online information is available?/  M On your OpenVMS system, the HELP command can provide a wealth of information,SJ not only on DCL commands but on system services (HELP System_Services) andJ Run-Time Library routines (HELP RTL_Routines).  The introduction displayedK when you type the HELP command with no additional keywords provides further 	 pointers.   E OpenVMS Marketing runs a WWW server at http://www.compaq.com/openvms/pL (http://www.openvms.compaq.com/).  Here, you will find product information, K strategy documents, the contents of the latest OpenVMS Freeware CD-ROM and w
 much more.  L Software Product Descriptions (SPDs) for most every OpenVMS-related product  Compaq sells is available via:  !   http://www.compaq.com/info/spd/f  L System performance data (see ALPHA5), product infosheets, release notes and  much more are also available.    In addition,     http://search.compaq.com/s  H provides a handy method to search all of Compaq's public web servers for information of any kind.  G Compaq's Customer Services organization also hosts an Internet server. rD Various contract-access and non-contract access ECO (patch) kits are available at the URL:a  7   http://ftp.digital.com.au/pub/ecoinfo/ecoinfo/top.htm %   http://search.service.digital.com/ t   For ftp access use a      ftp://ftp.service.digital.com/  E The Compaq Systems and Options Catalog (SOC) archive is available at:V  1   http://www.digital.com/info/SOHOME/SOHOMEHM.HTMo  G The Systems and Options Catalog has been replaced by Compaq QuickSpecs:   @   http://www.compaq.com/products/quickspecs/productbulletin.html  I The Compaq DSNlink electronic product support network (a good source for  H reporting problems, obtaining patches and ECOs, scanning Compaq support @ databases, searching for example programs, etc) is available at:  (   http://www.support.compaq.com/dsnlink/  H Compaq's Business Link provides product information, prices and permits  online ordering:  &    http://www.businesslink.compaq.com/  E The services provided by BusinessLink are being replaced by other andhB country-specific mechanisms, please see the above URL for details.  C Information on Compaq hardware, software, products and services is  , available through various telephone numbers:  G     1-800-AT-COMPAQ     : voice : Compaq (including DIGITAL and Tandem)m7                                   products and services 9     1-800-DIGITAL	: voice : DIGITAL products and servicesF0     1-800-DEC-2717	: voice : The DECchip Hotline9     1-508-568-6868	: voice : (alternate number for above)s>     1-800-STORWORK      : voice : The Compaq StorageWorks team  G David Mathog offers two HTML documents which contain useful informatione about OpenVMS.  1   http://seqaxp.bio.caltech.edu/www/soft_doc.htmlO  9 The VAXarchive (hardware and software information) is at: &   http://vax.sevensages.org/index.html  I Useful OpenVMS information and an extensive set of links is available at:e   http://www.levitte.org/~ava/  @ A wide variety of Compaq VAX, Alpha, platform and other product B documentation (some introductory, some technical) is available at:  0   http://www.digital.com/lists/master-index.html7   http://www.compaq.com/support/techpubs/qrg/index.htmlt  C The Compaq inFORM magazine and OpenVMS Times newsletters have emailo subscriptions available, see:s  !     http://www.compaq.com/inFORM/w/     http://www.openvms.compaq.com/openvmstimes/-  ) Also see the DFWCUG Longwords newsletter:e       http://www.dfwcug.org/  @ Back issues of the old Digital Technical Journals (DTJs) are at:  7     http://www.research.compaq.com/wrl/DECarchives/DTJ/i  < ------------------------------------------------------------2 DOC3.   What books and publications are available?  C A bibliography of current and recent OpenVMS books is available at:n  ,   http://www.levitte.org/~ava/vms_book.htmlx  C The Butterworth-Heinemann Digital Press imprint offers a number of s* OpenVMS books.  A website is available at:     http://www.bh.com/  ; Information on specific OpenVMS books is also available at:s  2   http://www.openvms.compaq.com/openvms/books.html   Also see DOC10.     < ------------------------------------------------------------E DOC4.   How do I extract the contents of a HELP topic to a text file?D  J To extract all the text of a HELP topic (and its subtopics) to a text fileE for perusal with a text editor, printing out, etc., use the following  command:  7      $ HELP/OUT=filename.txt help-topic [help-subtopic]2  B If the help text you want is not in the standard help library (forC example, it's help for a utility such as MAIL that has its own helpuE library), add /LIBRARY=libname after the HELP verb.  To see the namesh8 of help library files, do a directory of SYS$HELP:*.HLB.  < ------------------------------------------------------------6 DOC5.   Does OpenVMS Marketing have an e-mail address?  F Yes - if you can't get the answers to questions elsewhere, if you haveJ comments or complaints about OpenVMS, send mail to openvms-info@compaq.comI (This address is NOT a support channel, and is solely intended to provide K informal method to communicate directly with members of OpenVMS Marketing.)i  < ------------------------------------------------------------5 DOC6.   What OpenVMS-related WWW sites are available?-  F     http://www.openvms.compaq.com/    (Sponsored by OpenVMS Marketing)C     http://www.montagar.com/          (Sponsored by DECUS - DFWLUG) @     http://www.levitte.org/~ava/      (Sponsored by Arne Vajhj)B     http://www.saiga.com/             (Sponsored by Saiga Systems)?     http://www.tachysoft.com/	      (Sponsored by Wayne Sewell) D     http://www.progis.de/openvms.htm  (Sponsored by proGIS Software)A     http://www.jcameron.com/vms/      (Sponsored by Jeff Cameron)t  A The following web site is sponsored by "The Beave", and provides aC information that is directly relevent to system managers, security rC managers, and others interested in ensuring the continued security r of OpenVMS systems:d  3     http://www.vistech.net/users/beave/hack-vms-faqt  E Suggestions (indirectly) provided by the above include disabling the  > port 11 and 15 stats provided by IP packages such as Multinet.  < ------------------------------------------------------------ DOC7.   removed.  See MGMT25.i  < ------------------------------------------------------------B DOC8.   Where can I find info about undocumented OpenVMS features?  E After all this discussion about undocumented VMS features I started al4 collection of some documentation :-)) about them on   4     http://www.decus.de:8080/www/vms/qaa/undoc.htmlx 						[zinser@axp603.gsi.de]G                                                 [HORN@exchng1.shsu.edu]    Also see the following:u  -     http://www.levitte.org/~ava/vms_tip.htmlxa=                                                 [Arne Vajhj]   C Various examples of undocumented features are also available on thet OpenVMS Freeware:   +     http://www.openvms.compaq.com/freeware/c  < ------------------------------------------------------------@ DOC9.   Where is documentation on the DECnet Phase IV protocols?  E Documentation and Specifications for DECnet Phase IV can be found at:u  0     http://www.openvms.compaq.com/wizard/decnet/  < ------------------------------------------------------------G DOC10.  Where can I learn about how the VMS executive works internally?l  H The OpenVMS Internals and Data Structure manual (IDSM) explains how the F OpenVMS executive works. The book covers the operating system kernel: B process management; memory management; the I/O subsystem; and the H mechanisms that transfer control to, from, and among these. It gives an I overview of a particular area of the system, followed by descriptions of oF the data structures related to that area and details of the code that  implements the area.  H The first edition of the OpenVMS Alpha internals book describes Version H 1.5.  Although there have been several releases of  OpenVMS Alpha since G Version 1.5 (V6.1, V6.2, V7.0, V7.1, etc) and many details in the book aD are no longer accurate, it continues to provide a strong conceptual " description of OpenVMS internals.   I This book has been split into five pieces, each to be updated separately. M The first such volume, published in early 1997, was "OpenVMS Alpha Internals eG and Data Structures: Scheduling and Process Control," which covers the hM Version 7.0 implementation of true multithreading and the changed scheduling a model it implies.e  F The internals books are available through Digital Press, an imprint ofC Butterworth-Heinemann. You can order by phone (from US and Canada,  F 1-800-366-2655, or from elsewhere, 781-904-2500). You can also fax an G order to 1-800-446-6520 or 781-933-6333. The order form and additional o8 information are available on their web site www.bh.com .   ISBN           Title  F 1 55558 156 0  OpenVMS Alpha Internals: Scheduling and Process ControlE 1 55558 120 X  OpenVMS AXP Internals and Data Structures: Version 1.5eA 1 55558 059 9  VAX/VMS Internals and Data Structures: Version 5.2t   					[Ruth Goldenberg]  < ------------------------------------------------------------D DOC11.  Where can new users find tutorial information about OpenVMS?  P First, see if your local site has information on this topic.  Each site can haveM site-specific features and configuration.  Some sites will have site-specific H new user's documentation, covering various site-specific things that areG difficult or impossible for the general OpenVMS documentation to cover.t  L Various introductory manuals are available in the OpenVMS documentation set,J including the OpenVMS User's Guide.  The OpenVMS manuals -- including the ) OpenVMS User's Guide -- are available at:h  %   http://www.openvms.compaq.com:8000/ $   http://www.openvms.compaq.com/doc/+   http://www.openvms.compaq.com/commercial/-  C Some of the OpenVMS books available from the Butterworth-Heinemann h2 Digital Press imprint (http://www.bh.com) include:  ,        Introduction to OpenVMS, 5th Edition,        Lesley Ogilvie Rice        ISBN 1 55558 194 3   /        The OpenVMS User's Guide, Second Editioni        Patrick Holmay         ISBN 1 55558 203 6t          Introduction to OpenVMS        David W Bynon        ISBN 1 878956 61 2   &        OpenVMS System Management Guide        Richard Berry        ISBN 1 55558 143 9c  )        Using DECwindows Motif for OpenVMS         Margie Sherlock        ISBN 1 55558 114 5   3        Writing Real Programs in DCL, Second Edition "        Hoffman and Anagnostopoulos        ISBN 1 55558 191 9t  1   For various features OpenVMS books, please see::4     http://www.openvms.compaq.com/openvms/books.html  B   Various user-maintained websites are also available, including aD   beginner's FAQ, various user-written FAQs, a bibliography of booksD   on OpenVMS, and information on various other hardware and software	   topics:s  -     http://www.levitte.org/~ava/vms_faq.htmlxp.     http://www.levitte.org/~ava/vms_book.htmlx4     http://seqaxp.bio.caltech.edu/www/vms_sheet.html<     http://seqaxp.bio.caltech.edu/www/vms_beginners_faq.html  D   Members of the DECUS DFWLUG maintain a website with many materialsE   available, including an Overview of OpenVMS, an Introduction to DCLt>   and the TPU Editor, Advanced DCL Command Procedures, OpenVMSH   Operations: Batch, Print, Tape, an Introduction to OpenVMS Management,C   to OpenVMS User Management, to OpenVMS Network Management, and to A   OpenVMS Cluster Management.  These training materials have beenaB   presented at various DECUS symposia, and can be downloaded from:  *     http://www.montagar.com/openvms_class/  @   Compaq offers training information and Technical Resource Kits+   (TRKs) and other Training for OpenVMS at::  ,     http://www.compaq.com/training/home.html0     http://www.openvms.compaq.com/wbt/index.html  ?   An OpenVMS certification (testing) program is also available.   (   The following URL has an OpenVMS Quiz:      http://www.jcameron.com/vms/  E   CCSS Interactive Learning has OpenVMS training materials available:-     http://www.CCSScorp.com/      AcerSoft Training information:     http://www.acersoft.com/     MindIQ training information:     http://www.mindiq.com/  < ------------------------------------------------------------? DOC12.  Access to the OpenVMS Netscape Navigator documentation?t  =   The documentation URLs embedded into the browser itself may-:   not operate correctly in all cases, and (for reasons not;   worthy of repeating here) redirects may not be available.n  0   You can manually access the documentation via:3     http://www.openvms.compaq.com:88/netscape/help/f  < ------------------------------------------------------------8 TIME1.   A brief history of OpenVMS Timekeeping, please?  =   Why does OpenVMS regards November 17, 1858 as the beginningn   of time...  D   The modified Julian date adopted by the Smithsonian Astrophysical D   Observatory (SAO) for satellite tracking is Julian Day 2400000.5, 6   which turns out to be midnight on November 17, 1858.  @   SAO started tracking satellites with an 8K (nonvirtual) 36-bit?   IBM 704 in 1957 when Sputnik went into orbit. The Julian day e@   was 2435839 on January 1, 1957. This is 11225377 octal, which C   was too big to fit into an 18-bit field. With only 8K of memory, vE   the 14 bits left over by keeping the Julian date in its own 36-bit aD   word would have been wasted.  SAO also needed the fraction of the B   current day (for which 18 bits gave enough accuracy), so it was A   decided to keep the number of days in the left 18 bits and the  5   fraction of a day in the right 18 bits of one word./  A   Eighteen bits allows the truncated Julian day (the SAO day) to tA   grow as large as 262143, which from November 17, 1858, allowed  B   for 7 centuries. Possibly, the date could only grow as large as @   131071 (using 17 bits), but this still covers 3 centuries and B   leaves the possibility of representing negative time.  The 1858 D   date preceded the oldest star catalogue in use at SAO, which also G   avoided having to use negative time in any of the satellite tracking     calculations.i  D   The original Julian Day (JD) is used by astronomers and expressed D   in days since noon January 1, 4713 B.C.  This measure of time was E   introduced by Joseph Scaliger in the 16th century.  It is named in  E   honor of his father, Julius Caesar Scaliger (note that this Julian wB   Day is different from the Julian calendar that is named for the     Roman Emperor Julius Caesar!).  F   Why 4713 BC?  Scaliger traced three time cycles and found that they C   were all in the first year of their cyle in 4713 B.C.  The three aD   cycles are 15, 19, and 28 years long.  By multiplying these three C   numbers (15 * 19 * 28 = 7980), he was able to represent any date g"   from 4713 B.C. through 3267 A.D.  E   The starting year was before any historical event known to him.  IntE   fact, the Jewish calendar marks the start of the world as 3761 B.C.oG   Today his numbering scheme is still used by astronomers to avoid the uF   difficulties of converting the months of different calendars in use    during different eras.     The following web sites:  F     http://www.openvms.compaq.com/openvms/products/year-2000/leap.html  #     http://www.eecis.udel.edu/~ntp/d     http://www.nist.gov/)     http://www.boulder.nist.gov/timefreq/r/     http://www.tondering.dk/claus/calendar.htmliG     http://es.rice.edu/ES/humsoc/Galileo/Things/gregorian_calendar.htmlo  E   are all good time-related resources, some general and some specificw
   to OpenVMS.a  % 					[Stephen Hoffman, Dale Dellutri]f    < ------------------------------------------------------------3 TIME2.   How does OpenVMS VAX maintain system time?r  ?   VAX systems maintain an interval clock, and a hardware clock.   H   The VAX hardware clock is called the TOY ("Time Of Year") clock.  The F   register associated with the clock is called the TODR ("Time Of Day 
   Register").a  J   The TOY clock -- as used -- stores time relative to January first of theL   current year, starting at at 00:00:00.00.  It is a 100 Hz, 32-bit counter,D   incremented every 10ms, and thus has a capacity of circa 497 days.  H   OpenVMS (on the VAX platform) stores system date information -- and inJ   particular, the current year -- in the system image, SYS$SYSTEM:SYS.EXE.   G   The TOY is used, in conjunction with the base date that is stored andtJ   retrieved from the system image, to initialize the interval clock value #   that is stored in EXE$GQ_SYSTIME.E  M   Once the interval clock is loaded, the system does not typically reference aH   the TOY again, unless a SET TIME (with no parameters) is issued.  The J   interval clock value is updated by a periodic IPL22 or IPL24 (depending I   on the specific implementation) interrupt.  (When these interrupts are rD   blocked as a result of the activity of higher-IPL code -- such as J   extensive driver interrupt activity or a hardware error or a correctableI   (soft) memory error -- the clock will "loose" time, and the time value  8   reported to the user with appear to have slowed down.)  J   On most (all?) VAX systems, the battery that is associated with the TOY I   clock can be disconnected and replaced if (when) it fails -- TOY clock eJ   problems in VAX systems do regularly get tracked back to a failed nicad    or lithium battery pack. 					[Stephen Hoffman]  < ------------------------------------------------------------' TIME3.   Why does my system time drift?c  D   Memory errors, hardware problems, or most anything operating at orD   above IPL 22 or IPL 24 (clock IPL is system family dependent; codeB   executing at or above the clock IPL will block the processing ofE   clock interrupts), can cause the loss of system time.  Clock drift  E   can also be caused by normal (thermal) clock variations and even byh$   the expected level of clock drift.  C   When clock interrupts are blocked as a result of the activity of eD   high-IPL code -- such as extensive driver interrupt activity or a C   hardware error or a correctable (soft) memory error -- the clock sB   will "loose" time, and the time value reported to the user with A   appear to have slowed down.  Correctable memory errors can be aa3   common cause of system time loss, in other words.e  G   Clock drift can also be (deliberately) caused by the activity of the v   DTSS or NTP packages.o  $   Also see ALPHA17, VAX8, and TIME8.  < ------------------------------------------------------------D TIME4.   Managing Timezones, Timekeeping, UTC, and Daylight Savings?  -   You will want to use the command procedure:r  #     SYS$MANAGER:UTC$TIME_SETUP.COM 	  I   to configure the OpenVMS Timezone Differential Factor (TDF) on OpenVMS CH   V6.0 and later.  Select the BOTH option.  This configures the OpenVMS C   TDF settings, though it may or may not configure the TDF and the i=   timezone rules needed or used by other software packages.  t  A   Please do NOT directly invoke the following command procedures:h  =     SYS$MANAGER:UTC$CONFIGURE_TDF.COM   ! do not directly use =     SYS$MANAGER:UTC$TIMEZONE_SETUP.COM  ! do not directly user  G   TCP/IP Services V5.0 and later use the OpenVMS TDF, UTC, and timezoneeF   support.  Earlier versions use a TDF mechanism and timezone databaseG   that is internal to the TCP/IP Services package.  Also on the earlier:G   versions, the TDF must be manually configured within TCP/IP Services,.6   in addition to the OpenVMS configuration of the TDF.  G   DECnet-Plus in V7.3 and later uses the OpenVMS TDF, UTC, and timezonelH   support.  Earlier versions use a TDF TDF mechanism, timezone database,H   and automatic switch-over that is internal to the DECnet-Plus package.A   Also on earlier versions, the TDF must be configured within thelG   DECnet-Plus DECdtss package, in addition to the OpenVMS configurationh
   of the TDF.-  G   Application code using Compaq C (formerly DEC C) will use the OpenVMSoH   UTC and TDF mechanisms when the C code is compiled on OpenVMS V7.0 andJ   later (and when the macro _VMS_V6_SOURCE is NOT defined).  Compaq C doesH   NOT use the OpenVMS UTC and TDF mechanisms when the C code is compiledI   on OpenVMS releases prior to V7.0, or when the preprocessor declarationn   _VMS_V6_SOURCE is declared.o     DCE DTSS TDF details TDB.   E   In OpenVMS Alpha V6.1, V6.2, and V6.2-1Hx, the TDF value is written D   to SYS$BASE_IMAGE.EXE.  With OpenVMS Alpha V7.0 and later and withF   OpenVMS VAX V6.0 and later, SYS$SYSTEM:SYS$TIMEZONE.DAT contains theG   TDF.  This means that OpenVMS Alpha systems will need to have the TDF 2   value reset manually on reboots prior to V7.0.    I   During OpenVMS Bootstrap, the SYSINIT module reads SYS$TIMEZONE.DAT to tI   acquire the TDF for use in the system global cell EXE$GQ_TDF.  This is rH   done to ensure that the system boots with a valid TDF. The UTC system F   services get the TDF from this cell. These services, as well as the I   Compaq C RTL, must have a valid TDF.  (Prior to OpenVMS V7.3, if either-G   DECnet-Plus or DECnet/VAX Extensions is configured and run, the imagegI   DTSS$SET_TIMEZONE.EXE is invoked and can override the TDF and timezone  K   rule settings from SYSINIT or from UTC$TIME_SETUP.COM -- this image runs eK   even if DTSS is disabled.  If the settings do not match, DTSS will reset n'   the values to match its definitions.)m  D   Prior to OpenVMS V7.3, daylight savings time switchover is handledE   automatically only when DCE DTSS or DECnet-Plus DTSS is in use.  InlA   V7.3, OpenVMS can be configured to automatically switch over to/D   daylight savings time, and also generates an event that interestedF   applications can use to detect the switch-over between standard time   and daylight time.  G   The manual switchover between daylight savings time and standard time)E   is correctly accomplished via the SYS$EXAMPLES:DAYLIGHT_SAVINGS.COM    command procedure procedure.  G   If you switch the TDF or daylight savings time setting, you will alsooH   want to restart or reconfigure any time-sensitive applications (those H   not using the time change event in V7.3 and later).  Examples of theseH   applications include the need to restart the NFS client and (yes) NTP.G   (NTP will want to try to "drift" the time (see TIME6), and will find aG   the daylight savings time switch-over to be far too large to "drift".eF   Hence the NTP restart.)  You can also use the (undocumented) TCP/IP $   Services (prior to V5.0) commands:  4     SET TIME/DIFF=[positive or negative TDF integer]     GENERATE TIME   1   to reset the value of the logical name UCX$TDF.-     Prior to V7.3, the command:b        MCR DTSS$SET_TIMEZONE MODIFY  J   can be used to modify the settings of the SYS$TIMEZONE_DAYLIGHT_SAVING, G   SYS$TIMEZONE_DIFFERENTIAL, and SYS$TIMEZONE_NAME system logical namesd!   based on the SYS$TIMEZONE_RULE.	  E   The following are other TDF-related logical names used/available on G   OpenVMS systems, with typical Daylight Savings and Standard Settings v(   for the US Eastern Time (ET) timezone.       $daylight_time: /     $ DEFINE/SYSTEM/EXECUTIVE MAIL$TIMEZONE EDT 8     $ DEFINE/SYSTEM/EXECUTIVE NOTES$TIMEZONE "-0400 EDT"K     $ DEFINE/SYSTEM/EXECUTIVE LISP$DAYLIGHT_SAVING_TIME_P true  ! Not 'EDT'-<     $ DEFINE/SYSTEM/EXECUTIVE LISP$TIME_ZONE 05   ! Constant       $standard_time:E/     $ DEFINE/SYSTEM/EXECUTIVE MAIL$TIMEZONE ESTc8     $ DEFINE/SYSTEM/EXECUTIVE NOTES$TIMEZONE "-0500 EST"K     $ DEFINE/SYSTEM/EXECUTIVE LISP$DAYLIGHT_SAVING_TIME_P false ! Not 'EST'-<     $ DEFINE/SYSTEM/EXECUTIVE LISP$TIME_ZONE 05   ! Constant  9     $ DEFINE/SYSTEM/EXECUTIVE UCX$NFS_TIME_DIFFERENTIAL -nF         'f$integer(f$element(0," ",f$logical("notes$timezone"))/-100)'  F   For information on ZIC and related tools used to manage the OpenVMS E   Timezone database, please see the DEC C Run-time Library Utilities fC   Reference Manual -- though the title would imply otherwise, this tF   particular manual is part of the OpenVMS documentation set, and not :   part of the Compaq C (formerly DEC C) documentation set.  < ------------------------------------------------------------5 TIME5.   How to troubleshoot TDF problems on OpenVMS?v  F   This is an OpenVMS Alpha system prior to V7.0 and the startup is not   invoking the procedure:d  !    SYS$MANAGER:UTC$TIME_SETUP.COMc  D   This is an OpenVMS system prior to V6.0, where there is no OpenVMS   TDF nor UTC available.  D   The version of the application does not use the OpenVMS TDF.  ThisF   includes TCP/IP Services prior to V5.0, applications using Compaq C D   built on or targeting OpenVMS prior to V7.0, and systems using theC   DECnet-Plus DTSS mechanisms prior to the release associated with h   OpenVMS V7.3.  (DCE TDF TBD.)i  K   If you should find either of the following two timezone-related database  )   files located in SYS$SPECIFIC:[SYSEXE]:n  +     - SYS$SPECIFIC:[SYSEXE]SYS$TIMEZONE.DATo/     - SYS$SPECIFIC:[SYSEXE]SYS$TIMEZONE_SRC.DAT   H   These two files are in an erroneous location and must be recreated in    the correct directory:       SYS$COMMON:[SYSEXE].     If the DCL command:   *     DIRECTORY SYS$SYSTEM:SYS$TIMEZONE*.DAT  G   shows these files in SYS$SPECIFIC:[SYSEXE], then delete them and use t2   SYS$MANAGER:UTC$TIME_SETUP.COM to recreate them.  1   On OpenVMS versions prior to V7.3, if the file:G  $     SYS$STARTUP:DTSS$UTC_STARTUP.COM  9   is present on your system, then you may need to invoke:r  -     SYS$UPDATE:DTSS$INSTALL_TIMEZONE_RULE.COMs  @   to recreate the timezone files correctly.  Invoke this commandB   immediately after [re]executing SYS$MANAGER:UTC$TIME_SETUP.COM.)  E   If SYS$UPDATE:DTSS$INSTALL_TIMEZONE_RULE.COM is not present on yourc>   system, then you may need to execute the following commands:  +     DELETE SYS$STARTUP:DTSS$UTC_STARTUP.COMd+     DEASSIGN/SYSTEM/EXEC SYS$TIMEZONE_RULE.o  < ------------------------------------------------------------= TIME6.   How can I keep the OpenVMS system time synchronized?a  F   To help keep more accurate system time or to keep your system clocksG   synchronized, TCP/IP Services NTP, DECnet-Plus DECdtss, DCE DTSS, andhF   other techniques are commonly used.  If you do not have IP access toA   a time-base, then you could use dial-up access to NIST or othere   authoritative site.   C   There exists code around that processes the digital (ie: binary) SD   format time that is available via a modem call into the NIST clockC   (the Automated Computer Telephone Service (ACTS)), and code that  @   grabs the time off a GPS receiver digital link, or a receiver D   (effectively a radio and a codec) that processes the time signals E   from radio station WWV, WWVH, WWVB, or similar.  (Processing these 5@   time protocols often involves little more than reading from anB   EIA232 (RS232) serial line from the receiver, something that is @   possible from most any language as well as directly from DCL.)  C   One example of acquring a time-base involves the IRIG time formattC   (IRIG-A, -B, -G), a binary signal containing the current time in iG   hours, minutes, seconds and days since the start of the current year.oG   IRIG can also contain the time of day as the number of seconds since ~I   midnight.  Compaq Custom Systems and third-party vendors offer various p:   IRIG-based reader/generator modules for OpenVMS systems.  G   Differing time servers (DECnet-Plus DTSS, DCE DTSS, NTP, etc) do not WF   coexist particularly well, particularly if you try to use all these H   together on the same node.  Please pick and use just one.  (If needed,G   you can sometimes configure one package to acquire its timebase from tI   another protocol, but one and only one time server package should have NJ   direct control over the management of and drifting of the local OpenVMS    system time.)a     Useful URLs:8     http://www.boulder.nist.gov/timefreq/service/nts.htm9     http://www.boulder.nist.gov/timefreq/service/acts.htmr)     http://www.boulder.nist.gov/timefreq/i     http://www.time.gov/  < ------------------------------------------------------------D TIME7.   How can I configure TCP/IP Services NTP as a time provider?  C   An NTP time provider provides its idea of the current time to NTPnE   clients via the NTP protocol.  Most systems are NTP clients, but...I  F   NTP has a heirarchy of layers, called strata.  The further away fromG   the actual NTP time source (Internet time servers are at stratum 1), eG   the lower the strata (and the larger the number assigned the statum).   H   NTP explicity configured at stratum one provides time to NTP operatingG   at lower strata, and the provided time is acquired based on the localoB   system time or via some locally-accessable external time source.  J   NTP at other (lower) strata both receive time from higher strata and canK   provide time to lower strata, and automatically adjust the local stratum. J   The highest stratum is one, and the lowest available stratum is fifteen.  H   The TCP/IP Services NTP package can operate at any stratum, and can be>   configured as a peer, as a client, or as a broadcast server.  I   With TCP/IP Services V5.0 and later, the only supported reference clockhI   is the LCL (local system clock).  If your system has an excellent clock F   or if the system time is being controlled by some other time serviceI   (such as DTSS or GPS), you can configure NTP to use the system clock as H   its reference source.  This will mimic the master-clock functionality,F   and will configre NTP as a stratum 1 time server.  To do this, enter+   the following commands in TCPIP$NTP.CONF:m       server 127.127.1.0 prefer      fudge 127.127.1.0 stratum 0   G   For local-master functionality, the commands are very similiar.  Use:o       server 127.127.1.0     fudge 127.127.1.0 stratum 8c  F   The difference between these two is the stratum, and the omission ofE   the prefer keyword.  Specifying a higher stratum allows the node toiG   act as a backup NTP server, or potentially as the sole time server on I   an isolated network.  The server will become active only when all other.F   normal synchronization sources are unavailable.  The use of "prefer"J   causes NTP to always use the specified clock as the time synchronization	   source.g  I   With the TCP/IP Services versions prior to V5.0, the NTP management is AG   rather more primitive.  To configure the local OpenVMS system from anlK   NTP client to an NTP server (on TCP/IP Services versions prior to V5.0),  H   add the following line to the sys$specific:[ucx$ntp]ucx$ntp.conf file:       master-clock 1  E   Also, for TCP/IP Services prior to V5.0, see the NTP template file:   *     SYS$SPECIFIC:[UCX$NTP]UCX$NTP.TEMPLATE  8   For current TCP/IP Services documentation, please see:  '     http://www.openvms.compaq.com:8000/m&     http://www.openvms.compaq.com/doc/    < ------------------------------------------------------------1 TIME8.   How can I drift the OpenVMS system time?e  J   With DECdts and TCP/IP Services NTP, the system time value is "drifted" H   (rather than changed), to avoid the obvious problems that would arise I   with "negative time changes".  The same basic clock drifting technique oK   is used by most (all?) time servers operating on OpenVMS, typically usingf8   the support for this provided directly within OpenVMS.  G   An example of the technique used (on OpenVMS VAX) to drift the systemm4   time is the SETCLOCK tool on the OpenVMS Freeware.  L   For information on the use of the EXE$GL_TIMEADJUST and EXE$GL_TICKLENGTH J   cells on OpenVMS Alpha, see _OpenVMS AXP Internal and Data Structures",    located on page 348.  < ------------------------------------------------------------; TIME9.   Why does VAX need a SET TIME at least once a year?c  K   Because the VAX Time Of Year (TOY) has a resolution of 497 days, the VAX eL   system time is stored using both the TOY and the OpenVMS VAX system image J   SYS.EXE.  Because of the use of the combination of the TOY and SYS.EXE, J   you need to issue a SET TIME command (with no parameters) at least once J   between January 1st and about April 11th of each year, and whenever you K   change system images (due to booting another OpenVMS VAX system, booting hD   the standalone BACKUP image, an ECO that replaces SYS.EXE, etc).    G   The SET TIME command is automatically issued during various standard rK   OpenVMS procedures such as SHUTDOWN, and it can also obviously be issued rH   directly by a suitably privileged user.  Issuing the SET TIME command J   resets the value stored in the TOY, and (if necessary) also updates the K   portion of the time (the current year) saved in the SYS.EXE system image.O  H   This VAX TOY limit is the reason why OpenVMS VAX installation kits andI   standalone BACKUP explicitly prompt for the time during bootstrap, and  G   why the time value can "get weird" if the system crashes outside the sI   497 day window (if no SET TIME was issued to update the saved values), hK   and why the time value can "get weird" if a different SYS$SYSTEM:SYS.EXE o:   is used (alternate system disk, standalone BACKUP, etc).  < ------------------------------------------------------------A TIME10.   Why can't I do a SET TIME command?  Help managing DTSS?r  D If you try to set the system time with the SET TIME command, and see one of the following messages:  # %SET-E-NOTSET, error modifying timeo0 -SYSTEM-F-IVSSRQ, invalid system service request  # %SET-E-NOTSET, error modifying timeaK -SYSTEM-E-TIMENOTSET, time service enabled; enter a time service command toc update the timea    N A: This occurs if the time on the local system is controlled by a time serviceN software, for example the distributed time service software (DTSS) provided asO part of the DECnet/OSI installation. The DTSS software communicates with one ordL more time servers to obtain the current time. It entirely controls the localK system time (for DECnet/OSI, there is a process named DTSS$CLERK for this);cO therefore, the usage of the SET TIME command (and the underlying $SETTIM system, service) is disabled.s  N The first message is displayed on systems running DECnet/OSI V6.1 and earlier.M On systems with newer DECnet/OSI (DECnet-Plus) software, the second (and moret informative) message is given.  I You shouldn't have to change the time manually - you should be doing thisyM through the time server - but if you insist...  you'll have to shutdown DTSS:   	 $ MCR NCLt NCL> DISABLE DTSSa NCL> DELETE DTSS  L This will shutdown DTSS$CLERK. You may then change the system time as usual." To restart the DTSS software, type   @SYS$STARTUP:DTSS$STARTUP   M You'll need a lot of privs : (CMKRNL,SYSPRV,OPER,SYSNAM,PRMMBX,NETMBX,LOG_IO,aD ALTPRI) and must be granted the NET$MANAGE identifer to shutdown and
 restart DTSS.-?                                         [bol@adv.magwien.gv.at]i  N If you wish to "permanently" disable DTSS on a system running DECnet-Plus, theJ above NCL sequence must be performed each time the system is bootstrapped.  M If DTSS is running and no time servers are configured, you can (and will) seeo, the following messages at regular intervals:  8 %%%%%%%%%%%  OPCOM   2-SEP-1999 19:41:20.29  %%%%%%%%%%%" Message from user SYSTEM on UNHEDI> Event: Too Few Servers Detected from: Node LOCAL:.mynode DTSS,-         at: 1999-09-02-19:41:20.296-04:00IinfE         Number Detected=0,         Number Required=1Y7         eventUid   5FA70F4F-616E-11D3-A80E-08002BBEDB0F 7         entityUid  DE9E97DE-6135-11D3-8004-AA000400BD1BT7         streamUid  D6513A46-6135-11D3-8003-AA000400BD1Bm  K You can either configure the appropriate number of time servers, or you cangG disable DTSS, or you can ignore it and (if OPCOM is set to write to the J log via via the logical names in SYLOGICALS.COM/SYLOGICALS.TEMPLATE) clean out OPERATOR.LOG regularly.   : You can also simply disable the display of these messages:  M $ mcr ncl block event dispatcher outbound stream local_stream global filter -w,     ((Node, DTSS), Too Few Servers Detected)  @                                                   [Wayne Sewell]  H If you wish to disable the automatic TDF adjustment for daylight savingsB time (on OpenVMS versions prior to V7.3), you can use the command:  ,   ncl> set dtss automatic TDF change = false  F or alternatively, you can set the local timezone to one that does not 8 include the automatic daylight savings time change-over.  < ------------------------------------------------------------; TIME11.   Details of the VAX and Alpha system time-keeping?p  &   VAX hardware time-keeping details...     TOY clock    ---------TG   This is battery backed up hardware timing circuitry used to keep the vD   correct time of year during rebooting, power failures, and system C   shutdown.  This clock only keeps track of months, days, and time.NG   The time is kept relative to January 1st, at 00:00:00.00 of the year e   the clock was initiailized.e     EXE$GQ_SYSTIME   --------------K   This is the OpenVMS VAX system time cell.  This cell contains the number tK   of 100ns intervals since a known reference.  This cell is incremented by  2   100000 every 10ms by an hardware interval timer.     EXE$GQ_TODCBASE    ---------------TI   This cell contains the time and date the system time was last adjusted vM   by EXE$SETTIME.  It uses the same format as EXE$GQ_SYSTIME.  On adjustment  M   of the system time a copy of EXE$GQ_SYSTIME is stored in this cell in both dM   memory and on disk.  This cell is used to get the year for the system time.U  
   EXE$GL_TODR 
   -----------uK   This cell contains the time and date the system time was last adjusted bysO   EXE$SETTIME. It uses the same format as the time of year clock. On adjustmenthL   of the system time this cell gets saved back to both memory and disk.  TheG   contents of this cell are used to test the validity of the TOY clock.m  L   The system parameters SETTIME and TIMEPROMPTWAIT determine how the system    time will be set.l     IF SETTIME = 0J   THEN the contents of the TOY clock are compared to those of EXE$GL_TODR.  >         IF the TOY clock is more than a day behind EXE$GL_TODR/         THEN the TOY clock is presumed invalid.S  7         IF the TOY clock is within a day of EXE$GL_TODR 6         THEN the system time is calculated as follows:  O         EXE$GQ_SYSTIME = EXE$GQ_TODCBASE + ((TOY_CLOCK - EXE$GL_TODR) * 100000)h  ,   IF SETTIME = 1 or the TOY clock is invalidL   THEN the value of TIMEPROMPTWAIT determines how to reset the time of year.           IF TIMEPROMPTWAIT > 0PM         THEN the user is prompted for the time and date, for a length of timeg0         equal to TIMEPROMPTWAIT microfortnights.           IF TIMEPROMPTWAIT = 0rA         THEN the time of year is the value of EXE$GL_TODR + 10ms.   '         IF TIMEPROMPTWAIT < 0to proceeds         until they do so.e  C         THEN the user is prompted for the time and date and unable T  J   When booting a CD-ROM containing an OpenVMS VAX system, the system will I   typically be deliberately configured prompt the user to input the time  @   -- this is necessary in order to boot with the correct time.    H   If either TIMEPROMPTWAIT or SETTIME are set to zero, OpenVMS VAX will J   use the TOY clock to get the time of year, and the year will be fetched H   from the CD-ROM.  The value of the year on the CD-ROM media (saved in K   the SYS.EXE image) will most likely be that of when the CD-ROM was made, DI   and cannot be changed.  Unless the current year happens to be the same SK   year as that on the CD-ROM, most likely the year will be off.  (Further, SH   with the calculation of Leap Year also being dependent on the current ?   year, there is a possibility that the date could be off too.)E      (   Alpha hardware time-keeping details...  &   Battery-Backed Watch (BB_WATCH) Chip&   ------------------------------------G   This is battery backed up hardware timing circuitry used to keep the XD   correct time of year during rebooting, power failures, and system G   shutdown.  This clock keeps track of date and time in 24 hour binary l	   format.u     EXE$GQ_SYSTIME   --------------M   This is the OpenVMS Alpha system time cell.  This cell contains the number lH   of 100ns intervals since November 17, 1858 00:00:00.00.  This cell is A   incremented by 100000 every 10ms by an hardware interval timer.p     EXE$GQ_SAVED_HWCLOCK   --------------------M   This cell is used by OpenVMS Alpha to keep track of the last time and date sF   that EXE$GQ_SYSTIME was adjusted.  It keeps the same time format as H   EXE$GQ_SYSTIME.  The value in this cell gets updated in memory and on 0   disk, every time EXE$GQ_SYSTIME gets adjusted.  e  G   - The system parameters SETTIME and TIMEPROMPTWAIT determine how the h     system time will be set.  I   - If SETTIME = 0 then EXE$INIT_HWCLOCK reads the hardware clock to set       the system time.           - IF TIMEPROMPTWAIT > 0nJ           THEN the value of TIMEPROMPTWAIT determines how long the user isL           prompted to enter the time and date.  If time expires and no time D           has been entered the system acts as if TIMEPROMPTWAIT = 0.           - IF TIMEPROMPTWAIT = 0SA           THEN the system time is calculated from the contents of$#           EXE$GQ_SAVED_HWCLOCK + 1.            - IF TIMEPROMPTWAIT < 0oG           THEN the user is prompted for the time and date and unable to 4           continue until the information is entered.  J   Unlike the VAX, the Alpha hardware clock tracks the full date and time, H   not just the time of year.  This means it is possible to boot from theH   CD-ROM media without entering the time at the CD-ROM bootstrap.  (ThisD   provided that the time and date have been initialized, of course.)    < ------------------------------------------------------------E TIME12.   UTC vs GMT vs vs UT1/UT1/UT2 TDF?  What are these acronyms?c  F   The results of an international compromise -- though some would say F   an international attempt to increase confusion -- UTC is refered to H   as "Coordinated Universal Time" (though not as CUT) in English and as <   "Temps Universel Coordinn" (though not as TUC) in French.  F   Universal Time UT0 is solar time, UT1 is solar time corrected for a E   wobble in the Earth's orbit, and UT2 is UT1 corrected for seasonal nC   rotational variations in rotation due to the Earth's solar orbit.s  E   GMT -- Greenwich Mean Time -- is UT1.  GMT is the time at the (old) E   Royal Greenwich Observatory (in Greenwich), not to be confused withPD   the Royal Greenwich Observatory located at Herstmonceux Castle in    Sussex, England.  H   UTC is based on an average across multiple atomic clocks, and is kept K   within 0.9 seconds of GMT, through the insertion (or removal) of seconds.kF   In other words, UTC matches GMT plus or minus up to 0.9 seconds, but   UTC is not GMT.f  G   TDF is the Timezone Differential Factor, the interval of time betweencE   the local time and UTC.  Areas that celebrate daylight savings time H   (DST) will see periodic changes to the TDF value, when the switch-overJ   between daylight savings time and standard time occurs.  The switch-overF   itself is entirely left to local governmental folks, and can and hasI   varied by political entity and politics, and the switch-over has varied -   over the years even at the same location.  a  G   If your local OpenVMS system time is off by one hour (or whatever theeG   local DST change) for some or all applications, you probably need to     reset your local TDF.s  D   Further discussions of history and politics, the Royal Observers' G   outbuildings, and the compromise that left the English with the Time  F   Standard (the Prime Meridian) and the French with the standards for F   Distance and Weight (the Metric System) are left to other sources.     Some of these sources:        ftp://elsie.nci.nih.gov/pub/1     http://physics.nist.gov/GenInt/Time/time.htmlk     http://nist.time.gov/    [End of Part 1/5]t  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  # Date: Tue, 10 Apr 2001 18:08:13 GMT 2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman); Subject: OpenVMS Frequently Asked Questions (FAQ), Part 2/5w2 Message-ID: <h_HA6.749$fB6.19160@news.cpqcorp.net>   Archive-name: dec-faq/vms/part2H Posting-Frequency: quarterly Last-modified: 10 Apr 2001 Version: VMS-FAQ-2.TXT(6)p    9 This is the OpenVMS Frequently Asked Questions Part 2/5.  @ Please see Part 1/5 for administrivia, indexing, archiving, etc.      < ------------------------------------------------------------# MGMT1.  What is an installed image?   N The term "install" has two distinct meanings in OpenVMS.  The first relates toN "installing a product", which is done with either the SYS$UPDATE:VMSINSTAL.COMI command procedure or the POLYCENTER Software Installation (PCSI) utility dH (PRODUCT command).  The second meaning relates to the use of the INSTALL( utility, which is what concerns us here.  H The INSTALL utility is used to identify to OpenVMS a specific copy of anG image, either executable or shareable, which is to be given some set ofoK enhanced properties.  For example, when you issue the SET PASSWORD command, I the image SYS$SYSTEM:SETP0.EXE is run.  That image needs to have elevateda# privileges to perform its function.   J The other important attribute is /SHARED.  This means that shareable partsG of the image (typically read-only code and data) are loaded into memory H only once and are shared among all users on a system.  Executable imagesH can be installed /SHARED as well as shareable library images.  (The termE "shareable" has dual meanings here, too.  See the OpenVMS Programming,% Concepts Manual for further details.)1  M It's important to note that there is no such thing as "installing a shareable H image with privileges".  The INSTALL utility will let you do it, but theL privileges you specify will be ignored.  To have a callable routine run withL enhanced privileges that are not available to its caller, you must constructI your routines as "user-written system services" and install the shareableyH image with the /PROTECT qualifier.  See the OpenVMS Programming ConceptsG Manual for more information on user-written system services.  Note alsovK that in many cases the need to grant privileges to an image can be replacedaG with the use of the "Protected Subsystems" feature that grants a rightsiE identifier to an image.  See the OpenVMS Guide to System Security for $ information on Protected Subsystems.  < ------------------------------------------------------------0 MGMT2.  Are there any known viruses for OpenVMS?  N Viruses are very common on PCs because the PC operating systems such as MS-DOSM and MacOS do not implement any sort of scheme to protect the operating systemoJ or the file system against hostile action by programs.  On these operatingK systems, any running program can subvert the operating system and take overtK the hardware, at which point it can do anything it wishes, including hidingo9 copies of itself in other programs or in the file system.-  J This is unlikely on OpenVMS, Unix, and MVS for three reasons.  First, the G operating system runs in a privileged mode in memory that is protected iF against modification by normal user programs.  Any old program cannot D take over the hardware as it can on PC operating systems.  Secondly,C OpenVMS, Unix, and MVS have file systems that can be set up so thateJ non-privileged programs cannot modify system programs and files on disk.  H Both of these protection schemes mean that traditional PC virus schemes I don't work on these OSes.  Third, typical applications and configurationsmG tend to prevent the uncontrolled execution of untrusted code as part of  email messages or web access.A  K It is possible for OpenVMS, etc., to be infected by viruses, but to do so, -I the program containing the virus must be run from a user account that hasTJ amplified privileges.  As long as the system administrator is careful thatK only trusted applications are run from such accounts (and this is generallya+ the case), there is no danger from viruses.  					[Paul Winalski] 					[Stephen Hoffman]  G To protect against viruses and other attempts at system interference orsO misuse, follow the recommendations in the "OpenVMS Guide to System  Security". eJ You may also want to consider optional software products which can monitorJ your system for intrusion or infection attempts.  Computer Associates (CA)% offers various products in this area.o  H Rocksoft offers the Veracity data integrity tool (for info, send mail to demo@rocksoft.com).o  % [Contributions to this list welcomed]u  < ------------------------------------------------------------1 MGMT3.  How do I mount an ISO-9660 CD on OpenVMS?s  5 ISO-9660 support was added in the following releases:s       OpenVMS VAX V6.0     OpenVMS AXP V1.5  @ An add-on ISO-9960 kit was also available for OpenVMS VAX V5.5, = V5.5-1, V5.5-2, and V5.5-2H4.  This requires the installationa? of the F11CD kit from the InfoServer CD, from the Consolidated hB Distribution CD under the InfoServer area, Customer Support Center? kit CSCPAT #1071012, or the F11CD ECO kit.  (Upgrades to V6 and"  later are strongly recommended.)  > By default, OpenVMS senses the specific type of media.  If you> are working with dual-format media -- media that uses both the@ ODS-2 and ISO-9660 formats on the same CD-ROM -- then MOUNT will@ first detect and then default to the ODS-2 format.  If you wish @ to override this and explicitly mount the media using ISO-9660,  use the command:  =     $ MOUNT/MEDIA_FORMAT=CDROM  device-name[:] [volume-label]r  > In most circumstances, you will not need nor will you want to = include an explicit /MEDIA_FORMAT specification.  For furtheru> information, please refer to the OpenVMS MOUNT Utility Manual.= Particularly note the information on the MOUNT /MEDIA_FORMAT   and /UNDEFINED_FAT qualifiers.  9 The MOUNT /UNDEFINED_FAT qualifier is of interest becauseo= ISO-9660 media can be mastered on a wide variety of operatingl@ system platforms, and these platforms do not necessarily supportD the semantics needed for files containing predefined record formats.C The /UNDEFINED_FAT allows you to specify the default attributes for 6 files accessed from volumes using the ISO-9660 format.  + An example which works for most CD-ROMs is:   G     $ MOUNT/MEDIA_FORMAT=CDROM/UNDEFINED_FAT=STREAM:2048 DUA0: FREEWAREa  @ This particular MOUNT command forces access to the CD-ROM media = using the ISO-9660 volume structure, and the use of the MOUNTs> /UNDEFINED_FAT qualifier causes any file whose file attributes? are "undefined" to be returned with "stream" attributes with a m maximum record length 2048.e  @ On OpenVMS, the ISO-9660 format is (internally) considered to be= the ODS-3 file structure, while the High Sierra extensions toSA the standard are considered to be the ODS-4 file structure.  The A= Rock Ridge extensions are not currently available on OpenVMS.    					[Jim Dunham]  					[Stephen Hoffman]  = For details on ODS-1 and ODS-2 file specifications, see Kirby < McCoy's VMS File System Internals Manual from Digital Press, and see:  .   http://pdp-11.trailing-edge.com/www/ods1.txt  C The OpenVMS Freeware V5.0 CD-ROM (and later) is expected to includes< a set of ODS-2 specifications located in the directory ODS2.  < ------------------------------------------------------------4 MGMT4.  How do I extract the contents of a PCSI kit?  ? A growing number of OpenVMS products are being provided in PCSIbE (POLYCENTER Software Installation) kits which are installed using the-F PRODUCT INSTALL command.  These are alternatives to or replacement forD VMSINSTAL kits which were BACKUP savesets.  PCSI kits are not BACKUP< savesets and are structured differently from VMSINSTAL kits.  H If you want to extract product files from a PCSI kit, create a directoryD into which the kit should be expanded and use the following command:  8     $ PRODUCT COPY prodname /SOURCE=[where-the-kit-is] -5       /DEST=[destination-directory] /FORMAT=REFERENCE:  ? A PCSI kit file has a file specification of the following form:l  '     DEC-VAXVMS-FORTRAN-V0603-141-1.PCSIS  G In this example, "FORTRAN" is the "prodname".  PCSI will expand the kiteD files into the directory you specify and subdirectories beneath suchI as [SYSEXE], [SYSLIB], etc., reflecting the eventual destination of filesoH found there.  Most of the actual product files (images, etc.) will be inG the subdirectories.  In the top-level directory will be a file with theaH file type PCSI$DESCRIPTION that specifies where various files should go.G For more details, see the POLYCENTER Software Installation Developer's eE Guide for OpenVMS, which can be found in the OpenVMS documentation onc- the Consolidated Online Documentation CD-ROM.a  < ------------------------------------------------------------; MGMT5.  I've forgotten the SYSTEM password - what can I do?   C If you need to break into an OpenVMS system because you do not have F access to any privileged passwords, such as the password to the SYSTEMG username, you  will need physical access to the system console, and youpB will need to perform a conversational reboot.  Here are the steps:  ?   1.  Halt the system.  Exactly how this is done depends on theyE       specific system model: Depending on the model, this can involveBF       pressing the <HALT> button, entering <CTRL/P> on the console, or.       pressing the <BREAK> key on the console.  G   2.  At the >>> console prompt, use a console command to boot into theeJ       SYSBOOT> utility.  (SYSBOOT allows conversational changes to system I       parameters.)  The syntax for the conversational bootstrap varies byXI       system model -- this typically involves specifying a flag of 1, fore       example:           VAX:
           B/1            B/R5:1           @GENBOOe           Alpha:           b -flags 0,1  I       If your system has a non-zero system root (such as root SYSE, shownhJ       here), you will have to use a console command such as the following:           VAX:           B/E0000001           B/R5:E0000001 7           @<console media procedure name varies widely>t           Alpha:           b -flags e,1     E       If your system has a hardware password (various systems supportOG       a password that prevents unauthorized access to the console), youYF       will need to know theis password and will need to enter it usingF       the LOGIN command at the console.  If you get an "Inv Cmd" errorG       trying to perform a conversational bootstrap, and you do not havesF       the hardware console password for the console LOGIN command, youF       are stuck -- you will need to call for hardware service in orderF       to reset the hardware console password.  The syntax used for the(       console password mechanism varies.  G   3.  Once at the SYSBOOT> prompt, request that OpenVMS read the systemXH       startup commands directly from the system console, that the windowH       system (if any) not be started, and that OpenVMS not record these A       particular parameter changes for subsequent system reboots:            SET/STARTUP OPA0:y         SET WINDOW_SYSTEM 0g         SET WRITESYSPARAMS 0         CONTINUE  H   4.  At the $ prompt, the system will now be accepting startup commandsF       directly from the console.  Type the following two DCL commands:  
         SPAWNe         @SYS$SYSTEM:STARTUPi  I       The result of these two commands will be the normal system startup, D       but you will be left logged in on the console, running under aE       privileged username.  Without the use of the SPAWN command, youa5       would be logged out when the startup completes.o  E       If necessary, you can skip the invocation of the system startupeE       temporarily, and perform tasks such as egistering license PAKs i<       or various other "single-user" maintenance operations.  >   5.  Use the following commands to reset the SYSTEM password:  A         SET DEFAULT SYS$SYSTEM:  ! or wherever SYSUAF.DAT resides           RUN SYS$SYSTEM:AUTHORIZE+         MODIFY SYSTEM /PASSWORD=newpasswordo         EXIT  F       These steps will change the SYSTEM password to the specified new!       newpassword password value.   I    Reboot the system normally -- the SYSTEM password should now be set toe%    the value you specified in Step 5.   M    Some people will suggest a method using the UAFALTERNATE SYSGEN parameter.nL    This approach is not always reliable and is not recommended, as there canK    easily be an alternate user authorization file configured on the system.a  L    For further information on emergency startup and shutdown, as well as forJ    the official OpenVMS documentation on how to change the SYSTEM passwordL    from the console in an emergency, please see the OpenVMS System Manager's+    Manual in the OpenVMS documentation set.M  K    You can also use the conversational bootstrap technique shown above (thetM    steps through Step 3) to alter various system parameters.  At the SYSBOOT> /    prompt, you can enter new parameters values:t        SHOW MAXPROCESSCNTd
      SET . 64o
      CONTINUE   H    The "." is a shorthand notation used for the last parameter examined.   					[Stephen Hoffman]  < ------------------------------------------------------------9 MGMT6.  How do I connect a PostScript printer via TCP/IP?t  H Using UCX as the TCP/IP stack, it is possible to setup queues using the F UCX$TELNETSYM in order to print to postscript printers.  This assumes J however that the printer itself can convert whatever is passed to it into I something intelligible.  As an example, if the printer has an IP address i@ of 123.456.789.101 and jobs should be passed to port 9100 then :G $ INITIALIZE/QUEUE/ON="123.456.789.101:9100"/PROCESSOR=UCX$TELNETSYM  -s
 		my_ip_queue   D The port number of 9100 is typical of HP JetDirect cards but may be ( different for other manufacturers cards.  F As a better alternative, DCPS Version 1.4 and later support IP queues B using either Compaq TCP/IP Services for OpenVMS software or Cisco I Multinet for OpenVMS.  The usage of this type of interface is documented  8 in the Release Notes and the DCPS$STARTUP.TEMPLATE file.  I For general and additional (non-Postscript) IP printing information, see: 4   http://www.openvms.compaq.com/wizard/wiz_1020.html   http://www.wotsit.org/ 					[Steve Reece]5                                         [Arne Vajhj]e  < ------------------------------------------------------------ MGMT7 moved to TIME10.  < ------------------------------------------------------------) MGMT8 removed. superceded by TIME sectionc  < ------------------------------------------------------------; MGMT9.  How do I change the node name of an OpenVMS System?T  D   The first step is to get a BACKUP of the system disk before makingD   any changes -- use the system disk backup procedures as documentedA   in the OpenVMS System Management Manual, making sure to use theo:   procedures and commands appropriate for the system disk.  D   Changing the node name involves a number of steps -- the node nameE   tends to be imbedded in a number of different data files around the 	   system.t  @     Update the SCSNODE in MODPARAMS.DAT, and then run AUTOGEN as7       far as the SETPARAMS phase.  (Do not reboot yet.)n@     Modify the DECnet node name.  (NETCONFIG is the DECnet Phase:       IV tool, and NET$CONFIGURE is the DECnet-Plus tool.)E     Modify the IP node name.  (The TCP/IP Services tool is UCX$CONFIGaE       prior to V5.0, and is TCPIP$CONFIG in V5.0 and later releases.) @     Modify the host node name on the various queues in the queue@       database.  (each queue has a host name, and it defaults toD       the SCS node name of the queue's host system.  See the command*       INIT/QUEUE/ON=node for information.)C     Modify the node name saved in any application databases, or anyeD       local node-conditional operations present in the site-specificA       system startup, etc.  (SEARCH for the node name, specifyingy       all types of files.)B     Rename the SYS$NODE_oldnodename rightslist identifier to match<       the new name.  (Do not change the binary value of this       identifier.)C     Reset any license PAKs that are restricted to the old node name        to the new node name.-@     If the node name is part of a disk volume label, see MGMT19.@     Reboot the node or -- if in a VMScluster -- reboot the whole@       VMScluster.  (This tends to catch any errors immediately.)  G   There are likely a few other areas where the nodename will be stored.y  E   If the system is configured in a VMScluster and you change *either* E   the SCSNODE or the SCSSYSTEMID -- but *not* both values -- then you G   will have to reboot the entire VMScluster.  (The VMScluster remembers->   the mapping between these two values, and will assume that aE   configuration problem has occured if a mismatched pair appears, andhH   will refuse to let a node with a mismatched pair join the VMScluster.)  H   To calculate the correct SCSSYSTEMID value, multiply the DECnet Phase H   IV area number by 1024, and add the DECnet Phase IV node number.  For I   example, the SCSSYSTEMID value for a DECnet node with address 19.22 is N$   19478.  ((19 * 1024) + 22 = 19478)  F   I expect I may have missed one or two configuration tools (or more!)G   that are needed at your site -- the node name tends to get stored all ?   over the place, in layered products, and in local software...i   					[Stephen Hoffman]  < ------------------------------------------------------------E MGMT10. What is the correct value for EXPECTED_VOTES in a VMScluster?f  F The VMScluster connection manager uses the concept of votes and quorumH to prevent disk and memory data corruptions -- when sufficient votes areK present for quorum, then access to resources is permitted.  When sufficienteJ votes are not present, user activity will be blocked.  The act of blockingF user activity is called a "quorum hang", and is better thought of as aG "user data integrity interlock".  This mechanism is designed to preventAJ a partitioned VMScluster, and the resultant massive disk data corruptions.  K On each OpenVMS node in a VMScluster, one sets two values in SYSGEN: VOTES,lI and EXPECTED_VOTES.  The former is how many votes the node contributes toeJ the VMScluster.  The latter is the total number of votes expected when the  full VMScluster is bootstrapped.  G Some sites erroneously attempt to set EXPECTED_VOTES too low, believingvC this will allow when only a subset of voting nodes are present in arJ VMScluster.  It does not.  Further, an erroneous setting in EXPECTED_VOTESI is automatically corrected once VMScluster connections to other nodes areoJ established, meaning user data is at risk of severe corruption only during the initial system bootstrap.G  G One can operate a VMScluster with one, two, or many voting nodes.  WithnH any but the two-node configuration, keeping a subset of the nodes activeA when some nodes fail can be easily configured.  With the two-nodefH configuration, one must use a primary-secondary configuration (where theH primary has all the votes), a peer configuration (where when either node@ is down, the other hangs), or (preferable) a shared quorum disk.  F Use of a quorum disk does slow down VMScluster transitions somewhat --E the addition of a third voting node that contributes the vote(s) that H would be assigned to the quorum disk makes for faster transitions -- butL the use of a quorum disk does mean that either node in a two-node VMScluster6 configuration can operate when the other node is down.  J If you choose to use a quoum disk, a QUORUM.DAT file will be automaticallyH created when OpenVMS first boots and when a quorum disk is specified -- I well, the QUORUM.DAT file will be created when OpenVMS is booted without  , also needing the votes from the quorum disk.  K In a two-node VMScluster with a shared storage interconnect, typically eachnI node has one vote, and the quorum disk also has one vote.  EXPECTED_VOTESf is set to three.  F Using a quorum disk on a non-shared interconnect is unnecessary -- theG use of a quorum disk does not provide any value, and the votes assignedoH to the quorum disk should be assigned to the OpenVMS host serving access to the disk.  D For information on quorum hangs, see the OpenVMS documentation.  ForE information on changing the EXPECTED_VOTES value on a running system,aF see the SET CLUSTER/EXPECTED_VOTES command, and see the OpenVMS systemF console documentation for the processor-specific console commands usedC to trigger the IPC (Interrrupt Priority Level %x0C; IPL C) handler.nE The IPC handler can be used to clear a quorum hang, and to clear diska mount verification hangs.o  F The quorum scheme is a set of "blade guards" deliberately implemented F by OpenVMS Engineering to provide data integrity -- remove these bladeG guards at your peril.  OpenVMS Engineering did not implement the quorum-G mechanism to make your life more difficult -- quorum was implemented too' keep your data from getting scrambled.     						[Stephen Hoffman]   < ------------------------------------------------------------< MGMT11. Why doesn't OpenVMS see the new memory I just added?  I When adding memory to an OpenVMS system, one should check for an existingsI definition of the PHYSICALPAGES (OpenVMS VAX) or PHYSICAL_MEMORY (OpenVMStH Alpha) parameter in the SYS$SYSTEM:MODPARAMS.DAT parameter database, useH a text editor to reset the value in the file to the new correct value as1 required, and then perform the following command:m  /   $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT FEEDBACK0  I This AUTOGEN command will reset various system parameters based on recent J system usage (FEEDBACK), and it will reset the value for the PHYSICALPAGESD parameter to the new value.  It will also reboot the OpenVMS system.   H PHYSICALPAGES and PHYSICAL_MEMORY can also be used to deliberately lowerG the amount of memory available for use by OpenVMS.  This ability can beoH useful in a few specific circumstances, such as testing the behaviour ofG an application in a system environment with a particular (lower) amountn of system memory available.   I PHYSICALPAGES and PHYSICAL_MEMORY can be set to -1 (on OpenVMS Alpha) or cK (better and simpler) the entry can be removed from the MODPARAMS.DAT file, l5 to indicate that all available memory should be used.d   						[Stephen Hoffman]f  < ------------------------------------------------------------9 MGMT12. How do I write a BACKUP saveset to a remote tape?n  G How to do this correctly was described at DECUS a long time ago. On the . node with the tape drive, create SAVE-SET.FDL:   RECORD%         FORMAT                  fixedo$         SIZE                    8192   Then create BACKUP_SERVER.COM:     $ !dA   $ ! BACKUP_SERVER.COM - provide remote tape service for BACKUP.o   $ !    $ set noon   $ set rms/network=16   $ allocate mka500 tapedev 4   $ mount/nounload/over:id/block=8192/assist tapedev2   $ convert/fdl=SAVE-SET sys$net tapedev:save-set.   $ dismount/unload tapedevh
   $ stop/id=0e    A On the node where you want to do the backup, use the DCL command:r     $ backup -      srcfilespec -9      node"user pwd"::"task=backup_server"/block=8192/saveh  H The only thing that doesn't completely work here is multi-reel savesets.G Since the tape is being written through RMS and the magtape ACP, BACKUP E won't see the reel switch and will split an XOR group across the reelhE boundary. As far as I remember, BACKUP will be willing to read such aeE multi-reel save set (directly, not over the net) since the XOR blocks-F are simply ignored on read, but it definitely wouldn't be able to do a" recovery across the reel boundary.  F Unfortunately BACKUP can't read tapes over the network because the RMSD file attributes on a network task access look wrong (variable length	 records).m 						[Stephen Hoffman]v  < ------------------------------------------------------------3 MGMT13. Tell me about SET HOST/DUP and SET HOST/HSCc  K The OpenVMS DCL commands SET HOST/DUP and SET HOST/HSC are used to connect fM to storage controllers via the Diagnostics and Utility Protocol (DUP).  ThesesK commands require that the FYDRIVER device driver be connected.  This devicetL driver connection is typically performed by adding the following command(s) * into the system startup command procedure:       On OpenVMS Alpha:S       $ RUN SYS$SYSTEM:SYSMANn;       SYSMAN> IO CONNECT FYA0/NOADAPTER/DRIVER=SYS$FYDRIVER        On OpenVMS VAX:e       $ RUN SYS$SYSTEM:SYSGENi$       SYSGEN> CONNECT FYA0/NOADAPTER  M Alternatives to the DCL SET HOST/DUP command include the console >>> SET HOSToA command available on various mid- to recent-vintage VAX consoles:o  8     Access to Parameters on an Embedded DSSI controller:?       >>> SET HOST/DUP/DSSI[/BUS:{0:1}] dssi_node_number PARAMSu  @     Access to Directory of tools on an Embedded DSSI controller:?       >>> SET HOST/DUP/DSSI[/BUS:{0:1}] dssi_node_number DIRECTS  4     Access to Parameters on a KFQSA DSSI controller:;       >>> SHOW UQSSP ! to get port_controller_number PARAMS-:       >>> SET HOST/DUP/UQSSP port_controller_number PARAMS  I These console commands are available on most MicroVAX and VAXstation 3xxxnE series systems, and most (all?) VAX 4xxx series systems.  For furtherhK information, see the system documentation and -- on most VAX systems -- see  the console HELP text.  J EK-410AB-MG, _DSSI VAXcluster Installation and Troubleshooting_, is a goodL resource for setting up a DSSI VMScluster on OpenVMS VAX nodes. (This manualJ predates coverage of OpenVMS Alpha systems, but gives good coverage to allJ hardware and software aspects of setting up a DSSI-based VMScluster -- andO most of the concepts covered are directly applicable to OpenVMS Alpha systems.  L This manual specifically covers the hardware, which is something not covered2 by the standard OpenVMS VMScluster documentation.)   Also see MGMT58. 						[Stephen Hoffman]t  < ------------------------------------------------------------4 MGMT14. How do I install DECnet Phase IV on VMS 7.1?  N On OpenVMS V7.1, all DECnet binaries were relocated into separate installationH kits -- you can selectively install the appropriate network: DECnet-PlusK (formerly known as DECnet OSI), DECnet Phase IV, and Compaq TCP/IP Services  (often known as UCX).   L On OpenVMS versions prior to V7.1, DECnet Phase IV was integrated, and thereN was no installation question.  You had to install the DECnet-Plus (DECnet OSI)K package on the system, after the OpenVMS upgrade or installation completed.e  J During an OpenVMS V7.1 installation or upgrade, the installation procedureF will query you to learn if DECnet-Plus should be installed. If you areG upgrading to V7.1 from an earlier release or are installing V7.1 from arK distribution kit, simply answer "NO" to the question asking you if you want L DECnet-Plus.  Then -- after the OpenVMS upgrade or installation completes --L use the PCSI PRODUCT INSTALL command to install the DECnet Phase IV binaries? from the kit provided on the OpenVMS software distribution kit.   F If you already have DECnet-Plus installed and wish to revert, you mustN reconfigure OpenVMS.  You cannot reconfigure the "live" system, hence you mustJ reboot the system using the V7.1 distribution CD-ROM.  Then select the DCL. ($$$ prompt) option.  Then issue the commands:  *     $$$ DEFINE/SYSTEM PCSI$SYSDEVICE DKA0:0     $$$ DEVINE/STSTEM PCSI$SPECIFIC DKA0:[SYS0.]@     $$$ PRODUCT RECONFIGURE VMS /REMOTE/SOURCE=DKA0:[VMS$COMMON]  K The above commands assume that the target system device and system root areLH "DKA0:[SYS0.]".  Replace this with the actual target device and root, asK appropriate.  The RECONFIGURE command will then issue a series of prompts.  M You will want to reconfigure DECnet-Plus off the system, obviously.  You willmM then want to use the PCSI command PRODUCT INSTALL to install the DECnet Phaset+ IV kit from the OpenVMS distribution media.   G Information on DECnet support, and on the kit names, is included in thep4 OpenVMS V7.1 installation and upgrade documentation.   						[Stephen Hoffman]e  < ------------------------------------------------------------< MGMT15. How do I change the text in a user's UIC identifier?  M The text translations of the numeric User Identification Code (UIC) are basedOM on identifiers present in the OpenVMS rightslist.  Documentation on this areag= is included in the _Guide to OpenVMS System Security_ manual.a  J To control the identifiers shown for a user's UIC, you use AUTHORIZE. EachJ user has an associated group identifier, and an identifier specific to the. user.  And each user should have a unique UIC.  F To alter the text of a user or group identifier, use commands such as:       $ RUN SYS$SYSTEM:AUTHORIZE+     UAF> rename/ident oldgroupid newgroupido*     UAF> rename/ident olduserid  newuserid  L If you should find yourself missing an identifier for a particular user, you7 can add one for the user's UIC using a command such as:h  3     UAF> add/ident/value=uic=[group,user] newuseridm  M The UIC user identifier text is assigned when the username is created, and ishN the text of the username.  The UIC group group identifier is assigned when theH first username is created in the UIC group, and the text is based on theM account name specified for the first user created in the group.  The value of L this identifier is [groupnumber, 177777]. To add a missing group identifier, use an asterisk as follows:f  1     UAF> add/ident/value=uic=[group,*] newgroupid-  M You may find cases where an identifier is missing from time to time, as therenJ are cases where the creation of a UIC group name identifier might conflictF with an existing username, or a user identifier might conflict with anM existing group identifier.  When these conflicts arise, the AUTHORIZE utility N will not create the conflicting group and/or user identifier when the username is created.   K You can can add and remove user-specified identifiers, but you should avoid0J changing the numeric values associated with any existing identifiers.  YouL should also avoid reusing UICs or identifiers when you add new users, as anyL existing identifiers that might be present on objects in the system from theM old user will grant the same access to the new user.  Please see the securityt manual for details.a  < ------------------------------------------------------------3 MGMT16. What are the OpenVMS version upgrade paths?   8    Note: See "OpenVMS Alpha Terminology" section, below.  3    OpenVMS Alpha release upgrade (or update) paths:l  (      From V1.0, one can upgrade to V1.5.5      From V1.5, or V1.5-1H1, one can upgrade to V6.1.j(      From V6.1, one can upgrade to V6.2.1      From V6.1, or V6.2, one can upgrade to V7.0. G      From V6.1, V6.2, V6.2-1H(1,2,3), or V7.0, one can upgrade to V7.1.eB      From V6.2, one can update to V6.2-1H1, V6.2-1H2, or V6.2-1H3.F      From V6.2, V6.2-1H(1,2,3), V7.1, V7.1-1H(1,2), or V7.2, to V7.2-1(      From V6.2, ... or V7.2, to V7.2-1H1?      From V7.1, one can update to V7.1-1H(1,2), ... to V7.2-1H1u  >      Some typical OpenVMS Alpha upgrade (or update) paths are:9          V1.0 -> V1.5 -> V6.1 -> (V6.2, V7.0, V7.1, V7.2)c5          V1.5-1H1 -> V6.1 -> (V6.2, V7.0, V7.1, V7.2)           V6.1 -> V7.2e          V6.2 -> V6.2-1H3           V6.2 -> V7.2-1           V6.2-1H(1,2,3) -> V7.1f!          V6.2-1H(1,2,3) -> V7.2-1t          V7.1 -> V7.1-1H(1,2)i          V7.1 -> V7.1-2           V7.1 -> V7.2-1           V7.1-1H(1,2) -> V7.2-1r          V7.2 -> V7.2-1H1e  G      Note that OpenVMS Alpha V7.0 does not include support for hardwareCE      and/or configurations first supported in OpenVMS Alpha V6.2-1H1,TA      V6.2-1H2, or V6.2-1H3; one must upgrade to OpenVMS VAX V7.1.I  F      One cannot update directly to a V6.2-1Hx Limited Hardware ReleaseD      (LHR) from any release prior to the baseline V6.2 release.  TheG      same prohibition holds for performing updates directly to V7.1-1HxyF      from any release prior to V7.1 -- this is not supported, and doesE      not produce the expected results.  The LHR kits can, however, be E      directly booted and can be directly installed, without regard toyC      any operating system that might be present on the target disk.   F      OpenVMS Alpha updates for LHRs (through V7.1-1Hx) require the useF      of VMSINSTAL for the update.  These LHR releases use PCSI for theE      installation, but not for the update.  Non-LHR releases use PCSI !      for installs and upgrades.  w  F      OpenVMS Alpha V7.1-2 and later use PCSI for LHRs and for OpenVMS C      upgrades and for all OpenVMS ECO kit installations.  VMSINSTALeE      OpenVMS ECO kits are not used on OpenVMS Alpha V7.1-2 and later. D      Prior to V7.1-2, VMSINSTAL-based ECO kits are used for OpenVMS.    %    OpenVMS VAX release upgrade paths:l  A      From V5.0 through V5.4-3 inclusive, one can upgrade to V5.5.u?      From V5.5, V5.5-1, or V5.5-2HW, one can upgrade to V5.5-2.e;      From V5.5, V5.5-1, or V5.5-2, one can upgrade to V6.0.e=      From V5.5-2, V5.5-2H4, or V6.0, one can upgrade to V6.1.b1      From V6.0, or V6.1, one can upgrade to V6.2. 1      From V6.1, or V6.2, one can upgrade to V7.0.j7      From V6.1, V6.2, or V7.0, one can upgrade to V7.1.TD      From V6.1, one can upgrade to V7.2 (with VAXBACK ECO for V6.1).  0      Some typical OpenVMS VAX upgrade paths are:8          V5.x -> V5.5 -> V6.0 -> V6.2 -> (V7.0, or V7.1)          V5.5-2HW -> V5.5-22=          V5.5-2, or V5.5-2H4 -> V6.1 -> (V6.2, V7.0, or V7.1)f)          V6.1 -> VAXBACK V6.1 ECO -> V7.2e          V6.2 -> V7.2o  E      Note that OpenVMS VAX V6.0 does not include support for hardwareaC      and/or configurations first added in OpenVMS VAX V5.5-2H4, one-&      must upgrade to OpenVMS VAX V6.1.  G      Note that OpenVMS VAX V5.5-2HW is a pre-release version of V5.5-2.fB      Any system running it should be upgraded to V5.5-2, or later.    $    OpenVMS Cluster Rolling Upgrades:  F      Rolling Upgrades require multiple system disks.  Rolling upgradesL      permit the OpenVMS Cluster to remain available while individual systems1      are being upgraded to a new OpenVMS release.v  L      OpenVMS Cluster rolling upgrades for both OpenVMS VAX and OpenVMS AlphaG      may (will) have different, or additional upgrade requirements, andcC      have requirements around which versions of OpenVMS can coexistp3      in a OpenVMS Cluster than what is listed here.S  K      See the _OpenVMS <platform> Version <Version> Upgrade and Installationb;      Manual_, and the OpenVMS Software Product Descriptionsv  &        http://www.compaq.com/info/spd/?        OpenVMS typically uses SPD 25.01.xx and/or SPD 41.87.xx.V  O      for further details on the rolling upgrade, and for support information.  eI      The documentation for older releases of OpenVMS VAX includes variousEF      platform-specific manuals, manuals that include instructions that>      are specific to installing and upgrading on the platform.    7    OpenVMS and Layered Products -- Support Information:   ?      For information on Prior Version Support (PVS) and Mature WA      Product Support (including information on support end dates o;      for OpenVMS and various layered products), please see:i  =        http://www.compaq.com/services/software/ss_mature.html B        http://www.compaq.com/services/software/ss_pvs_se_amap.htmlB        http://www.compaq.com/services/software/ss_mps_pvs_eur.html  C      For information on supported versions of layered products, andc4      minimum required layered product versions, see:  A        http://www.openvms.compaq.com/openvms/os/swroll/index.htmlo  A      For information on the release history of OpenVMS, includingo>      information on the code names of various releases and the      major features:  L        http://www.openvms.compaq.com/openvms/os/openvms-release-history.html  D      Additional release history information, as well as a variety ofA      other trivia, is available in the VAX 20th anniversary book:r  =        http://www.openvms.compaq.com/openvms/20th/vmsbook.pdfo      OpenVMS Alpha Terminology:d  B      update:    Typically used for Limited Hardware Releases (LHR)A                 releases.  Performed via VMSINSTAL.  Applies onlyE@                 to the OpenVMS release that the LHR is based on,F                 or to an intermediate LHR.  (eg: V7.1-1H2 applies onlyD                 to V7.1-1H1 and to V7.1, not to any other releases.)C                 LHRs within a series are cumulative, containing allnG                 files and features of previous LHRs in the same series.n  F      upgrade:   Performed via PCSI.  Upgrades can typically be appliedE                 to a release-specific (and documented) range of prioro!                 OpenVMS releases.m  F      install:   Performed via PCSI.  With an installation, no existingG                 version of the operating system is assumed present, nordI                 are any files from any copy of the operating system mightaK                 be present preserved, and the entire contents of the targeti=                 disk are destroyed via a disk initialization.e  J      preserve:  Performed via PCSI.  Otherwise similar to an installation,H                 this option skips the disk reinitialization.  User filesI                 on the target disk are preserved.  Any existing operating->                 system files on the target disk are clobbered.  G      LHR:       Limited Hardware Release.  LHRs are specific to and areoD                 targeted at new hardware configurations, and are notF                 shipped to customers with support contracts.  At leastI                 one LHR kit must be specifically acquired when purchasing I                 new hardware, new hardware that is not (yet) supported by H                 any mainline (non-LHR) release.  LHRs have an "H" in theH                 OpenVMS version string, indicating a "Hardware" release.    @   For minimum OpenVMS versions for various platforms, see VMS13.  < ------------------------------------------------------------G MGMT17. Why do I have negative number in the pagefile reservable pages?   E Seeing a negative number in the reservable pages portion of the SHOW fI MEMORY/FULL command can be normal and expected, and is (even) documented pD behaviour.  A pagefile with a negative number of reservable pages isK overcommitted, which is generally goodness assuming that every process with L reserved pages does not try to occupy all of the reserved pagefile  space at the same time. T  L To understand how the pagefile reservation process works, think about  how aN traditional bank operates when accepting customer deposits and  making loans. L It's the same idea with the pagefile space. There is  less money in the bankM vault than the total deposits, because much of  the money has been loaned outeH to other customers of the bank.  And the behaviour parallels that of theM pagefile down to the problems that a  "run on the bank" can cause for bankingdI customers.  (Though there is  no deposit insurance available for pagefile  users.)   L If all of the running applications try to use the reserved space, the systemG manager will need to enlarge the pagefile or add one or more additionalv
 pagefules.  L To determine if the pagefile is excessively overcommitted, watch for "doubleN overcommitment" -- when the reservable space approaches the  negatation of theG available total space -- and watch that the total  amount of free spaceaK available in the pagefile remains adequate.  If  either of these situationsn0 arises, additional pagefile storage is required.  G Additional pagefile information: Additional pagefiles can typically be oJ created and connected on a running OpenVMS system.  New processes and  newN applications will tend to use the new pagefile, and existing  applications canL be restarted to migrate out of the more congested  pagefiles.  Pagefiles areN generally named PAGEFILE.SYS, and multiple  pagefiles are generally configuredM on separate disk spindles to spread  the paging I/O load across the available E disk storage.  When multiple  pagefiles are present on recent OpenVMS-J versions, each pagefile file  should be configured to be approximately the( same total size as the  other pagefiles.  K For additional information on pagefile operations and related commands, seeaH the system management and performance management manuals in the  OpenVMS documentation set. 					[Stephen Hoffman]  < ------------------------------------------------------------C MGMT18. Do I have to update layered products when updating OpenVMS?   K The Software Public Rollout Reports for OpenVMS list the current and futureAL availability of Compaq's software products shipping on the Software ProductsG Library kits (CDROM consolidations) for OpenVMS Alpha and OpenVMS VAX. CK Specifically, the required minimum versions for product support are listed.n  N Comprehensive Public Rollout Information, listing previous product versions asM well as currently shipping versions, has been compiled into a separate set ofbN reports.  The product information is grouped to show Operating System support.  G You may or may not be able to use older versions of local applications,eJ third-party products, and various Compaq layered products with more recentJ versions of OpenVMS.  User-mode code is expected to be upward compatible. N Code executing in a privileged processor mode -- typically either executive orN kernel mode -- may or may not be compatible with more recent OpenVMS versions.  " These reports are updated monthly.   Please see:-<   http://www.openvms.compaq.com/openvms/os/swroll/index.html   					[Stephen Hoffman]  < ------------------------------------------------------------3 MGMT19. How do I change the volume label of a disk?u  G   Dismount the disk, and mount it privately.  If the disk is mounted byaF   more than one node in an OpenVMS Cluster, dismount it from all otherE   nodes.  If this disk is an OpenVMS system disk, shut down all other -   nodes that are bootstrapped from this disk.r  ?   Issue the SET VOLUME/LABEL command, specifying the new label.n  >   On OpenVMS V6.0 and later, issue the following PCSI command:  2     $ PRODUCT REGISTER VOLUME <old-label> <device>  G   To reset the label information stored in the PCSI database to reflect    the new disk volume label.  F   Locate any references in the system startup (typically including theJ   disk MOUNT commands) and any DISK$label references in application files,*   and change the references appropriately.  I   If this is a system disk (for the host or for a satellite), also check  I   the DECnet MOP or LANCP boot database, as well as any references to thet&   disk created by CLUSTER_CONFIG*.COM.  !   Remount the disk appropriately.V 					[Stephen Hoffman]:                                         [John E. Malmberg]  < ------------------------------------------------------------/ MGMT20.  How do I fix a corrupt BACKUP saveset?n  E   BACKUP savesets can be corrupted by FTP file transfers and by toolsuC   such as zip (particularly when the zip tool has not been asked to F   save and restore OpenVMS file attributes or when it does not supportF   OpenVMS file attributes), as well as via other means of corruptions.  D   If you have problems with the BACKUP savesets after unzipping themF   or after an FTP file transfer, you can try restoring the appropriate$   saveset attributes using the tool:  *     $ @RESET_BACKUP_SAVESET_ATTRIBUTES.COM  C   This tool is available on the OpenVMS Freeware (in the [000TOOLS]tD   directory).  The Freeware is available at various sites -- see theF   Freeware location listings elsewhere in the FAQ -- and other similar0   tools are also available from various sources.  E   In various cases, a SET FILE/ATTRIBUTES command can also be used.  tH   As the parameters of this command must be varied as the target BACKUP <   saveset attributes vary, this approach is not recommended.  K   Also see the "SITE VMS", /FDL, and various other file-attributes options CG   available in various FTP tools.  (Not all available FTP tools support    any or all of these options.)l  I   Browser downloads (via FTP) and incorrect (binary or ascii FTP transferoH   modes) are notorious for causing RMS file corruptions and particularlyL   BACKUP saveset corruptions.  You can sometimes help encourage the browser =   to select the correct FTP transfer type code (via RFC1738):5  G     ftp://host/urlname.ext;type=i   ! request ftp image/binary transferiE     ftp://host/urlname.ext;type=a   ! request ftp ascii/text transferf  H   You can also often configure the particular web browser to choose the E   appropriate transfer mode by default, based on the particular file tH   extensions, using a customization menu available in most web browsers.H   You can select that the specific file extentions involved use the FTP I   binary transfer mode, which will reduce the number of corruptions seen.o   					[Stephen Hoffman]  < ------------------------------------------------------------- MGMT21.  How can I set up a shared directory?n  H To set up a shared directory -- where all files created in the directoryH are accessable to the members of specified group of users -- you can use/ an access control list (ACL) and an identifier.,  K The following also shows how to set up a resource identifier, which furtheriJ allows the disk resources to be charged to the specified identifier ratherB than each individual user.  (If you don't want this, then omit theE attributes option on the identifier creation and omit the entry added  in the disk quota database.l  " Add an identifier using AUTHORIZE:3   ADD/IDENTIFER/ATTRIBUTES=RESOURCE groupidentifiern  ? Grant the identifier to each user in the group using AUTHORIZE:w+   GRANT/IDENTIFIER groupidentifier usernamei  A If disk quotas are in use, add an entry via SYSMAN for each disk:aF   DISKQUOTA ADD groupidentifier/PERMQUOTA=pq/OVERDRAFT=od/DEVICE=ddcu:  J Set the shared directory to have an ACL similar to the following using theJ SET SECURITY (V6.0 and later) or SET ACL (versions prior to V6.0) command:(   (DEFAULT_PROTECTION,S:RWED,O:RWED,G,W)O   (IDENTIFIER=groupidentifier,OPTIONS=DEFAULT,ACCESS=READ+WRITE+EXECUTE+DELETE)i?   (IDENTIFIER=groupidentifier,ACCESS=READ+WRITE+EXECUTE+DELETE)d+   (CREATOR,ACCESS=READ+WRITE+ACCESS+DELETE)a  K If there are files already resident in the directory, set their protectionsiL similarly.  (The OPTIONS=DEFAULT, DEFAULT_PROTECTION, and CREATOR ACEs apply to directories.)  L The default protection mask is used to establish the default file protection@ mask, this mask does not prevent the users holding the specifiedK groupidentifier from accessing the file(s), as they can access the file viaeC the explicit identifier granting access that is present in the ACL.d  I For further information, see the OpenVMS Guide to System Security Manual,VL specifically the sections on ACLs and identifiers, and resource identifiers.  < ------------------------------------------------------------ MGMT22 relocated to SUPP3r  < ------------------------------------------------------------8 MGMT23. Why do I get extra blank pages on my HP Printer?  I   For information on configuring telnet print symbiont, on device control.J   libraries such as SYSDEVCTL.TLB, and for ways of dealing with the extra L   blank pages that can arise on various HP printers, please see the OpenVMS =   Ask The Wizard area, starting particularly with topic 1020:V  )     http://www.openvms.compaq.com/wizard/ 6     http://www.openvms.compaq.com/wizard/wiz_1020.html  L   There are a variety of discussions of this and of related printing topics    in the Ask The Wizard area..     Also see MGMT51. 					[Stephen Hoffman]    < ------------------------------------------------------------E MGMT24. Configure ELSA GLoria Synergy or PowerStorm 300/350 graphics?o  E   On OpenVMS Alpha V7.1-2, V7.2, and V7.2-1, acquire the appropriate l;   GRAPHICS PCSI kit, and all prerequisite OpenVMS ECO kits:t  "     VMS712_GRAPHICS-V0300 or later!     VMS72_GRAPHICS-V0100 or lateri"     VMS712_GRAPHICS-V0300 or later     ----  *   The ELSA GLoria Synergy is the PBXGK-BB.  @   On OpenVMS Alpha V7.2-1, the files necessary for this graphics>   controller are located in the distribution CD-ROM directory:       DISK$ALPHA0721:[ELSA.KIT]e  0   Also check for any available (later) ECO kits.  E   An earlier kit (ALP4D20T01_071) (for V7.1, V7.1-1H1, and V7.1-1H2)  E   was once available, but has been superceded and is not recommended. D   Use of V7.1-2 or later (and use of one the above GRAPHICS kits as +   required) is typically the best approach.r  D   OpenVMS V7.2-1H1 and later should directly support the controller.     Additional information: 6     http://www.openvms.compaq.com/wizard/wiz_3419.html6     http://www.openvms.compaq.com/wizard/wiz_5448.html     ----     PowerStorm 300 : PBXGD-ACl   PowerStorm 350 : PBXGD-AEe  @   For support of the PowerStorm 300 and PowerStorm 350 graphics D   controllers, acquire and install the following available ECO kits:     For OpenVMS Alpha V7.1-2:p,     DEC-AXPVMS-VMS712_P350-V0100--4 or later0     DEC-AXPVMS-VMS712_GRAPHICS-V0300--4 or later     For OpenVMS Alpha V7.2-1:a,     DEC-AXPVMS-VMS721_P350-V0100--4 or later0     DEC-AXPVMS-VMS721_GRAPHICS-V0300--4 or later     ----  #   PowerStorm 3D30, PowerStorm 4D20: 6     http://www.openvms.compaq.com/wizard/wiz_2041.html     ----  D   Support for the ELSA GLoria Synergy and the PowerStorm 300 and 350E   controllers is expected to be integrated in the OpenVMS Alpha V7.3 C   and later releases.    					[Stephen Hoffman]  < ------------------------------------------------------------: MGMT25. How do I acquire OpenVMS patches, fixes, and ECOs?  N You can acquire and download kits containing OpenVMS fixes (ECOs) for various 
 releases via:   $   http://search.service.digital.com/+   ftp://ftp.service.digital.com/public/vms/w'   http://ftp.digital.com.au/pub/ecoinfod(   http://ftp/digital.com.au/cgi-bin/grep  3 You can subscribe to an email notification list at:S  :   http://www.support.compaq.com/patches/mailing-list.shtml  5 A quarterly distribution is also available on CD-ROM:       QT-3CQAA-C8      OpenVMS Alpha   QT-3CRAA-C8      OpenVMS VAX  > For a list of OpenVMS ECO kits recently released, you can use:  B     http://Eisner.DECUS.org/conferences/OpenVMS-patches_new_1.HTML  ? You can also sign up for ECO kit email notifications (Digest orl2 individual notifications) directly from Compaq at:  =     http://www1.service.digital.com/patches/mailing-list.htmln  B Examples and ECO kit installation instructions are included in the? cover letter.   For available ECO kits, cover letters and other " associated documentation, look in:  4     ftp://ftp.service.digital.com/public/vms/axp/...4     ftp://ftp.service.digital.com/public/vms/vax/...  G Do NOT attempt to install a VMSINSTAL-based OpenVMS ECO kit on OpenVMS .F Alpha V7.1-2 and later.  While VMSINSTAL itself remains available, it H is not used for OpenVMS Alpha ECO kits starting in OpenVMS Alpha V7.1-2.= OpenVMS Alpha V7.1-2 and later use PCSI for OpenVMS ECO kits.m  0 See MGMT46 for information on ECO kit checksums.   					[Stephen Hoffman]  < ------------------------------------------------------------. MGMT26. How do I rename a DSSI disk (or tape?)  C   If you want to renumber or rename DSSI disks or DSSI tapes, it's t/   easy -- if you know the secret incantation...      From OpenVMS:v       $ RUN SYS$SYSTEM:SYSGENe"     SYSGEN> CONNECT FYA0/NOADAPTER     SYSGEN> ^Z=     $ SET HOST/DUP/SERV=MSCP$DUP/TASK=PARAMS <DSSI-NODE-NAME>t     ...v     PARAMS> STAT CONFhC     <The software version is normally near the top of the display.>r     PARAMS> EXIT     ...e  F   From the console on most 3000- and 4000-class VAX system consoles...>   (Obviously, the system must be halted for these commands...)       Integrated DSSI:  A         >>> SET HOST/DUP/DSSI[/BUS:[0:1]] dssi_node_number PARAMS   
     KFQSA:  <         >>> SET HOST/DUP/UQSSP port_controller_number PARAMS  G   For information on how to get out into the PARAMS subsystem, also seerH   the >>> HELP at the console prompt for the SET HOST syntax, or see theG   HELP on SET HOST /DUP (once you've connected FYDRIVER under OpenVMS).   F   Once you are out into the PARAMS subsystem, you can use the FORCEUNID   option to force the use of the UNITNUM value and then set a uniqueF   UNITNUM inside each DSSI ISE -- this causes each DSSI ISE to use theD   specfied unit number and not use the DSSI node as the unit number.G   Other parameters of interest are NODENAME and ALLCLASS, the node nameH2   and the (disk or tape) cluster allocation class.  H   Ensure that all disk unit numbers used within an OpenVMS Cluster disk G   allocation class are unique, and all tape unit numbers used within ans8   OpenVMS Cluster tape allocation class are also unique. 					[Stephen Hoffman]  < ------------------------------------------------------------1 MGMT27. How do I move the queue manager database?   P   To move the location of the queue database, the SYS$QUEUE_MANAGER.QMAN$QUEUES L   and SYS$QUEUE_MANAGER.QMAN$JOURNAL files, to a disk that is fast(er), has M   plenty of free space, and that is not heavily used.  If the queue database  J   is on a (busy) OpenVMS system disk, you can and probably should move it .   off the system disk to another disk spindle.     To move the queue database:f  O    0. Checkpoint the journal file.  This reduces the file size to the in-memory 8       database size.  This will cause the noted delay.     	$ mcr JBC$COMMAND 	JBC$COMMAND> DIAG 0 7      1. Stop the queue manager   	$STOP/QUEUE/MANAGER/CLUSTER  O    2. Backup the .QMAN$QUEUES and .QMAN$JOURNAL files from the present location        for safety.  	 E 	$ backup SYS$COMMON:[SYSEXE]SYS$QUEUE_MANAGER.QMAN$*  DISK:[DIR]         eN    3. Create a new directory for the queue database.  Insure that this disk isN       accessible to all nodes that can run the queue manager.  If the /ON listK       for the queue manager is "/ON=(*)", the disk must be available to allH       nodes in the cluster     	$ CREATE/DIR fast_disk:[qman]  H    4. Copy the .QMAN$QUEUES and .QMAN$JOURNAL files to the new directory  E 	$ copy SYS$COMMON:[SYSEXE]SYS$QUEUE_MANAGER.QMAN$*  fast_disk:[qman]-  '    5.  Delete the old queue database.     4 	$DELETE SYS$COMMON:[SYSEXE]SYS$QUEUE_MANAGER.QMAN$*  <    6. Restart the queue manager pointing to the new location  & 	$START/QUEUE/MANAGER fast_disk:[qman]   					[Dave Sweeney]n  < ------------------------------------------------------------> MGMT28. How do I set a default IP route or gateway on OpenVMS?  2 If you have TCP/IP Services, then use the command:  %   For TCP/IP Services V5.0 and later:r  4     $ TCPIP SET ROUTE/GATE=x.x.x.x/DEFAULT/PERMANENT  '   For earlier TCP/IP Services versions:w  2     $ UCX SET ROUTE/GATE=x.x.x.x/DEFAULT/PERMANENT  < ------------------------------------------------------------ MGMT29 relocated to ALPHA21e  < ------------------------------------------------------------C MGMT30. How do I delete an undeletable/unstoppable (RWAST) process?s  C "Undeleteable" jobs are usually "undeleteable" for a reason -- thisoE can track back to insufficient process quotas, to a kernel-mode errorrD in OpenVMS or a third-party device driver, or to other odd problems.  D These undeletable jobs typically become of interest because they are@ holding onto a particular resource (eg: tape drive, disk drive, A communications widget) that you need to use...  If the particulariD device supports firmware, ensure that the device firmware is currentG -- TQK50 controllers are known for this when working with old firmware. G (That, and the infamous "MUA4224" firmware bug.)  If this device has a eD driver ECO kit available, acquire and apply it...  If the particular9 relevent host component has an ECO, acquire and apply it.f  D Useful tools include SDA (to see what might be going on) and DECamdsA (which increase and thus potentially fix quota-related problems).cB (nb: Applications with quota leaks will obviously not stay fixed.)  ? If the stuck application is BACKUP, ensure you have the current @ BACKUP ECO and are directly following the V7.1 or (better) V7.2 ; process quota recommendations for operator BACKUP accounts.r  H If the firmware and ECO levels are current, the best approach is to takeI a system crashdump, and pass a copy of the dump file it along to whomeverhH is maintaining the device driver for the particular device/widget/driverK involved, with any details on how you got into this situation.  (The rebootoE involved with taking the crashdump will obviously clear the problem.)i  D There was some kernel-mode code (typically for OpenVMS VAX) that canF reset the device ownership field, but that is rather obviously only anE interim solution -- the real fix is avoiding the loss of the IRP, the D process quota leak, or whatever else is "jamming up" this particular
 process... 					[Stephen Hoffman]  < ------------------------------------------------------------* MGMT31. How do I reset the error count(s)?  F The system reboot is the only supported approach, but it is obviously E undesirable in various situations -- there is presently no supported rC mechanism to reset error counts once the error(s) have been logged.   C As for an unsupported approach -- and be aware of the potential forw causing a system crash...   F To reset the error count, one needs to determine the system address ofE the error count field.  For a device, this is at an offset within theeG device's UCB structure.  On VAX, the field is at an offset symbolicallytG defined as UCB$W_ERRCNT.  On Alpha, this field's offset is symbolically E defined as UCB$L_ERRCNT.  The former is a word in size; the latter iseE a longword.  (Could it be that Alpha devices are more error prone? ;)e  F You now need to locate the system address of the UCB$%_ERRCNT field ofE the device you wish to reset.  Enter SDA.  In the following, you will-E see designations in {} separated by a /.  The first item in braces ismE to be used on the VAX and the second item should be used on an Alpha.o (ie.  {VAX/Alpha})   $ ANALYZE/SYSTEM2 SDA>  READ SYS${SYSTEM/LOADABLE_IMAGES}:SYSDEF.STBF SDA>  SHOW DEVICE <ddnc:>    ! device designation of device with error# SDA>  EVALUATE UCB+UCB${W/L}_ERRCNT 9 Hex = hhhhhhhh   Decimal = -dddddddddd         UCB+offsetn  1 Record the hexadecimal value 'hhhhhhhh' returned.m  G You can now exit from SDA and $ RUN SYS$SHARE:DELTA or do what I prefere to do, issue the following:t   SDA> SPAWN RUN SYS$SHARE:DELTA  I On both VAX and Alpha, the DELTA debugger will be invoked and will ident-pG ify itself.  On Alpha, there will be an Alpha instruction decoded.  ForsI those unfamiliar with DELTA, it does not have a prompt and only one errortI message -- Eh?  (Well, for sake of argument, there might be another error F produced on the console if you're not careful -- aka. a system crash!)  * If you are on a VAX, enter the command: [W* If you are on Alpha, enter the command: [L  H These set the prevailing mode to word and longword respectively.  Remem-% ber the UCB${W/L)_ERRCNT differences?-   Now issue the command 1;Mw  DELTA will respond with 00000001  I You're now poised to ZAP the error count field.  To do so you need to en- H ter the system address and view its contents.  The format of the command to do this is of the form:   <IPID>:<hhhhhhhh>/  I For an IPID, use the IPID of the SWAPPER process.  It is always: 00010001o  . Thus, to ZAP the error count, you would enter:   00010001:hhhhhhhh/  I When you enter the / SDA will return the content of the address hhhhhhhh.rJ This should be the error count (in hexadecimal) of the device in question.I If it is not, you did something wrong and I'd suggest you type a carriage0H return and then enter the command EXIT to get out of DELTA.  Regroup and! see where your session went awry.e  I If you entered your address correctly and the error count was returned asi* in the following example, you can proceed.  J 00010001:80D9C6C8/0001                          ! output on VAX    1 error  J 00010001:80D9C6C8/00000001                      ! output on Alpha  1 error    H You can now ZAP the error count by entering a zero and typing a carriage return.  For example:C    J 00010001:80D9C6C8/0001 0<cr>                    ! output on VAX    1 errorJ 00010001:80D9C6C8/00000001 0<cr>                ! output on Alpha  1 error  0 Now type the command EXIT and a carriage return.<                                       [Brian Schenkenberger]  < ------------------------------------------------------------A MGMT32. How do I find out if the tape drive supports compression?5  6 For various SCSI-based MK-class magnetic tape devices:  6     $ Devdepend2 = F$GETDVI("$n$MKcxxx:","DEVDEPEND2")     $ Comp_sup = %X00200000e     $ Comp_ena = %X00400000n5     $ IF (Devdepend2.AND.Comp_sup).EQ.Comp_sup THEN -r0         WRITE SYS$OUTPUT "Compression supported"5     $ IF (Devdepend2.AND.Comp_ena).EQ.Comp_ena THEN -u.         WRITE SYS$OUTPUT "Compression enabled"  < ------------------------------------------------------------? MGMT33. Can I copy SYSUAF to another version? To VAX? To Alpha?e  > The format of the SYSUAF.DAT, RIGHTSLIST, and associated files= are upward-compatible, and compatible across OpenVMS VAX and d9 OpenVMS Alpha systems.  (This compatibility is a a basic i< requirement of mixed-version OpenVMS Cluster configurations A and OpenVMS upgrades -- for specific support information, please C: see the OpenVMS Cluster rolling upgrade and mixed-version ? requirements.)  That said, it's the contents of the SYSUAF and r6 RIGHTSLIST files that will make this more interesting.  @ The same basic steps necessary for moving RIGHTSLIST and SYSUAF ? files to another node are rather similar to the steps involved eA in merging these files in an OpenVMS Cluster -- see the appendix ZB of the OpenVMS Cluster documentation for details of merging files.C (You might not be merging the contents of two (or more) files, but N? you are effectively merging the contents of the files into the d target system environment.)    Considerations:   >   o applications often hold SYSUAF or RIGHTSLIST open, meaning@     a system reboot is often the best way to activate new files.  >   o the meanings of the RESTRICTED and CAPTIVE flags settings .     on the UAF entries have changed over time.  ?   o the new NET$PROXY.DAT file that is initially created based +>     on the contents of the NETPROXY.DAT during the OpenVMS VAX;     V6.1 upgrade and during the OpenVMS Alpha V6.2 upgrade.+:     This file is maintained in parallel with NETPROXY.DAT.  =   o the RIGHTSLIST identifier values and UIC values that end E?     up scattered around the target system must be rationalized  =     with the contents of the new RIGHTSLIST and SYSUAF files.r  < The lattermost case -- resolving the identifier values -- is= often the most interesting and difficult part.   If you find  > that an identifier value (or identifier name) from the source ? RIGHTSLIST collides with that of an identifier existing on the e? target system, you must first determine if the two identifiers i= perform the same function.  In most cases, they will not.  As-= such, you will have to find and chance all references to the r< identifier value(s) (or name(s)) to resolve the "collision".  > If you encounter a collision, changing both of the identifier > binary values (or names) involved in the collision to new and ? unique values can prevent security problems if you should miss d? a couple of identifiers embedded somewhere on the target systeme= during the whole conversion process -- rather than the wrong a> alphanumeric value for the identifier being displayed, you'll ? simply see the binary format for the identifier displayed, and /? no particular access will be granted.  And any DCL commands or h@ such that reference the old alphanumeric name will fail, rather 7 than silently (and potentially erroneously) succeeding.-  < Similar requirements exist for UIC values, as these too tend: to be scattered all over the system environment.  Like the= binary identifier values, you will find UIC values associateda7 with disks, ACLs, queues, and various other structures.p  < For a list of the various files shared in an OpenVMS Cluster< and that can be involved when relocating an environment from= one node to another (or merging environments into an OpenVMS n> Cluster), please see the SYLOGICALS.TEMPLATE file included in   OpenVMS V7.2 and later releases.  = Procedures to extract the contents of a (potentially corrupt) < queue database are provided on the OpenVMS Freeware (V5) and9 can be used to combine two queue databases together while . shuffling files between OpenVMS Cluster hosts.  ? For related discussions of splitting a cluster into two or for e; removing a node from cluster (political divorce, etc), see:p3   http://www.openvms.compaq.com/wizard/wiz_203.htmlt3   http://www.openvms.compaq.com/wizard/wiz_767.htmln3   http://www.openvms.compaq.com/wizard/wiz_915.html. 					[Stephen Hoffman]  < ------------------------------------------------------------1 MGMT34. How do I delete (timeout) idle processes?o  F   There is no such command integrated within OpenVMS, though there areI   (optional) timers available within certain terminal servers and similarlI   devices, and there is an integrated time-of-day mechanism that providesV.   control over when a user can access OpenVMS.  K   As for available tools, there are DECUS, freeware, and third-party tools VG   known variously as "idle process killers" (IPK) or terminal timeout" rG   programs.  Examples include: Saiga Systems Hitman, Watchdog, MadGoat -F   Watcher (via the MadGoat site or the OpenVMS Freeware), Kblock, the ?   Networking Dynamics tool known as Assassin, and the Zap tool.   ;   A related package (for DECwindows sessions) is xtermlock.-  I   If the forgetful users are in an application menu environment, the menuq9   can potentially be extended to provide this capability.n  < ------------------------------------------------------------. MGMT35. Why isn't BACKUP/SINCE=BACKUP working?  H   If you are seeing more files backed up than previously, you are seeingF   the result of a change that was made to ensure BACKUP can perform anI   incrementation restoration of the files.  In particular, if a directoryoJ   file modification date changes, all files underneath it are included in L   the BACKUP, in order to permit incremental restoration should a directory    file get renamed.n  8   Why has OpenVMS gone through the agony of this change?  H     When a directory is renamed, the modified date is changed.  When theH     restoration needs to restore the directory and its contents, and theK     restoration should not result in the restoration of the older directorynD     name when a series of incremental BACKUPs are restored.  Thus anE     incremental BACKUP operation needs to pick up all of the changes.   0   What can you do to improve BACKUP performance?  H     Use the documented commands in the manual for performing incrementalJ     BACKUPs.  Use the documented incremental procedures.  Don't try to use6     incremental commands in a non-incremental context.  J     Also consider understanding and then using /NOALIAS, which will likelyJ     be a bigger win than will anything to do with the incremental BACKUPs,L     particularly on system disks and any other disks with directory aliases.  ,   Can you get the old BACKUP behaviour back?  E     Yes, please see the /NOINCREMENTAL qualifier available on recent dK     OpenVMS versions (and ECO kits).  Use of this qualifier informs BACKUP sM     that you are aware of the limitations of the old BACKUP behaviour around  "     incremental disk restorations.  I   Consider performing an incremental restoration, to test the procedures.DG   Attempting this is how we found out about the problem that was latentTF   with the old scheme -- the old incremental BACKUP scheme would have J   missed restoring any files under a renamed directory.  Hence the change.  <   See the OpenVMS V6.2 release notes for additional details.  < ------------------------------------------------------------; MGMT36. How can I set up reverse telnet (like reverse LAT)?   H   Though it may seem obvious, Telnet and LAT are quite different -- with*   differing capabilities and design goals.  E   Please see the documentation around the TCP/IP Services for OpenVMS G   TELNET command CREATE_SESSION.  This command is the equivilent of theEG   operations performed in LTLOAD.COM or LAT$SYSTARTUP.COM.  There is noaH   TELNET equivilent to the sys$qio[w] control interface for LTDRIVER (asC   documented in the I/O User's Reference Manual) available, though SD   standard sys$qio[w] calls referencing the created TN device would    likely operate as expected.e  < ------------------------------------------------------------? MGMT37. Do I need a PAK for the DECevent (Compaq Analyze) tool?l  D   DECevent and Compaq Analyze are avalable to customers with supportE   contracts.  The PAK is required only for the advanced functions of lE   DECevent, the basic bits-to-text translation of the error log does  B   not require a license PAK.  Ignore the prompt, in other words.  E   (The PAK should be available to you if you have a hardware support oE   contract or warrantee, and the PAK enables the use of the advanced U@   error analysis and notification capabilities within DECevent.)  5   Please see the DECevent FAQ for additional details:h  A http://www.support.compaq.com/svctools/decevent/DECevent_FAQ.html   ?   The current version of the DECevent (Compaq Analyze) tool cann   be downloaded from:u  7 http://www.support.compaq.com/svctools/st-download.htmlr  < ------------------------------------------------------------6 MGMT38. INITIALIZE ACCVIO and ANSI tape label support?  C A change was made (back in 1988) to (as it was then known) VAX/VMS MD V5.1-1 that added support for the then-new ANSI X3.27-1987 magnetic F tape label standard.  Prior to the ANSI X3.27-1987 standard, the date F field in the ANSI HDR1 record permits dates only as far as the end of D Year 1999.  With ANSI X3.27-1987, dates through Year 1999 and dates & from Years 2000 to 2099 are permitted.  B Versions of INIT.EXE and MTAACP.EXE from VAX/VMS releases prior to> V5.1-1 will potentially have problems properly processing ANSI? magnetic tapes when Y2K and later dates are involved -- the DCLMB INITIALIZE command is known to encounter access violation (ACCVIO) errors.[  C The available solutions include upgrades, or setting the date back. E Direct initialization of the tape with the new headers (via $qio) is .G also clearly possible, though the limitation within the old MTAACP.EXE  2 magtape ACP image is not nearly so easy to bypass.  B                                                [Hoffman, Dachtera]  < ------------------------------------------------------------/ MGMT39. How do I recover from INSVIRMEM errors?   ?   Prior to OpenVMS Alpha V7.0 and on all OpenVMS VAX releases, EC   VIRTUALPAGECNT and PGFLQUOTA limit the amount of virtual address e,   space that is available to each process.    E   Further limiting the amount of address space is the size of system -C   space (S0 and S1 space).  On OpenVMS Alpha versions prior to V7.0-D   and on all OpenVMS VAX releases, VIRTUALPAGECNT and MAXPROCESSCNT E   together determine the size of the page table data structures that uG   occupy large tracts of system space.  When no system virtual address sE   space is available for the stuff that needs it -- this includes theiC   page tables, non-paged pool, and various other structures -- thencE   the values of VIRTUALPAGECNT and MAXPROCESSCNT cannot be increased.g  G   In OpenVMS Alpha V7.0 and later, the page table data structures have  C   been moved out of S0 and S1 space and into page table space.  In fD   OpenVMS Alpha V7.2 and later, certain large data structures found E   in non-paged pool (eg: lock management structures) have been moved )B   into 64-bit space, thus freeing up room in non-paged pool and inG   S0 and S1 space (where non-paged pool resides) while also permitting n    much larger data structures.    < ------------------------------------------------------------I MGMT40. How can I prevent a serial terminal line from initiating a login?i  *   In SYSTARTUP_VMS.COM, issue the command:  ,     SET TERMINAL/NOTYPEAHEAD/PERMANENT ddcu:  @   This will prevent any unsolicited terminal input on ddcu:, andA   this unsolicited input is what triggers JOB_CONTROL to start upUB   LOGINOUT on the terminal.  Once LOGINOUT starts up on the serial>   line, you can see interesting behaviour (eg: audits, processB   creations, etc) as LOGINOUT tries to "chat" with whatever device<   is hooked onto the remote end of the serial terminal line.  < ------------------------------------------------------------6 MGMT41. How does PCSI use the image BUILD_IDENT field?  K   The (undocumented) build ident field in an OpenVMS Alpha image header is  K   16 bytes long, and is used as a counted string of 0-15 characters (ie, a iJ   an .ASCIC string with count in byte 0) and was originally introduced to K   provide information for use by VMSINSTAL patch kits to determine whether [%   an image should be replaced or not.-  H   Starting with OpenVMS Alpha V7.1-2, OpenVMS Engineering uses the PCSI F   utility to package and install ECO kits for OpenVMS.  PCSI uses the I   generation attribute (a 32-bit unsigned integer) specified for files inoN   the product description file (PDF) of a PCSI kit as the basis for performingH   file conflict detection and resolution.  When a product is installed, I   PCSI modifies the build ident field of Alpha image headers to store an tK   encoded form of the generation number.  It also looks at the build ident sL   field of previously installed images to obtain the generation information K   for those files as input to the file conflict processing algorithm. (Onlyi%   images have this field, obviously.)o  J   PCSI interprets the build ident field of a previously installed image as
   follows:  I     - if the string length is 15, the 5th character is a hyphen, and the %J       last ten characters are a ten digit number with leading zeros, then G       the last ten characters are treated as a valid generation number. I     - for V7.1-2 through V7.2-1, inclusive, if the above test fails, the A=       information is obtained from the PCSI product database.{L     - in releases after V7.2-1 and with current PCSI ECO kits, if the above K       test fails, an invalid generation number is treated as 0000000000 so hI       that the ECO kit will simply replace the image rather than assumingv$      the PCSI database is in error.  E   So, what will you see in the image identification displayed via thei   ANALYZE/IMAGE command?  D   For an image that has been built as part of an OpenVMS EngineeringG   system build, you will generally see a build ID string in the format aD   "X6TE-SSB-0000" -- X6TE is the build number for the OpenVMS Alpha D   V7.2-1 release.  This id format is used within the OpenVMS system C   build, and can generally only be seen associated with images thatl'   have not yet been processed via PCSI.c  J   During the installation of V7.2-1, PCSI will modify the image header to J   have a build ident string of "X6TE-0050120000".  During installation of I   an ECO kit containing this image with a generation number of 50130052,  L   for example, PCSI would determine that 50130052 is greater than 50120000, J   and will replace the existing image on the target disk with the version '   of the image included in the ECO kit.a  < ------------------------------------------------------------@ MGMT42. How to configure allocation classes and Multi-Path SCSI?  K The HSZ allocation class is applied to devices, starting with OpenVMS V7.2.nL It is considered a port allocation class (PAC), and all device names with a J PAC have their controller letter forced to "A".  (You might infer from theI the text in the "Guidelines for OpenVMS Cluster Configurations" that thisnJ is something you have to do, though OpenVMS will thoughtfully handle this  renaming for you.)  I You can force the device names back to DKB by setting the HSZ allocation nE class to zero, and setting the PKB PAC to -1.  This will use the host/G allocation class, and will leave the controller letter alone (that is, CL the DK controller letter will be the same as the SCSI port (PK) controller).H Note that this won't work if the HSZ is configured in multibus failover G mode.  In this case, OpenVMS requires that you use an allocation class o for the HSZ.  J When your configuration gets even moderately complex, you must pay carefulK attention to how you assign the three kinds of allocation class: node, port I and HSZ/HSJ, as otherwise you could wind up with device naming conflicts - that can be painful to resolve.   I The display-able path information is for SCSI multi-path, and permits theIG multi-path software to distinguish between different paths to the same $G device.  If you have two paths to $1$DKA100, for example by having two 0I KZPBA controllers and two SCSI buses to the HSZ, you would have two UCBs RE in a multi-path set.  The path information is used by the multi-path n/ software to distinguish between these two UCBs."  L The display-able path information describes the path; in this case, the SCSIL port.  If port is PKB, that's the path name you get.  The device name is no L longer completely tied to the port name; the device name now depends on the G various allocation class settings of the controller, SCSI port or node.i  I The reason the device name's controller letter is forced to "A" when you cL use PACs is because a shared SCSI bus may be configured via different ports M on the various nodes connected to the bus.  The port may be PKB on one node, )J and PKC on the other.  Rather obviously, you will want to have the shared L devices use the same device names on all nodes.  To establish this, you willH assign the same PAC on each node, and OpenVMS will force the controller G letter to be the same on each node. Simply choosing "A" was easier and eF more deterministic than negotiating the controller letter between the I nodes, and also parallels the solution used for this situation when DSSI o or SDI/STI storage was used.  I This information is also described in the Cluster Systems and Guidelines o+ for OpenVMS Cluster Configurations manuals. ;                                                [John Croll]s  < ------------------------------------------------------------@ MGMT43. How can I tell what software (and version) is installed?  A   There is unfortunatly no consistent nor single way to make thistA   determination -- this is one of the reasons that a move to PCSIV   installations is underway.  B   On OpenVMS Alpha, you can use VMSINSTAL.HISTORY and PRODUCT SHOW@   PRODUCT to determine what packages have been installed via the)   VMSINSTAL and PCSI tools, respectively.r  A   To see which OpenVMS Alpha ECO kits have been applied, look in e>   VMSINSTAL.HISTORY on OpenVMS Alpha prior to V7.1-2, and use >   PRODUCT SHOW PRODUCT/FULL on OpenVMS Alpha V7.1-2 and later.  ;   On OpenVMS VAX, you can use PRODUCT SHOW PRODUCT and (forr=   software that is installed via VMSINSTAL on V7.3 and later)e   in VMSINSTAL.HISTORY.i  ;   For products installed on OpenVMS VAX prior to V7.3 usingf@   VMSINSTAL, there is no reliable way to determine what products?   have been installed.  If the product provides a RELEASE_NOTESr=   file (as many do), you can look for the list of these files ?   via DIRECTORY SYS$HELP:*.RELEASE_NOTES.  Again, this approachf@   is NOT reliable: some kits do not provide release notes, some C   system managers will install only the release notes, some system oE   managers will delete release notes, and release notes for multiple s   versions can be present.  E   On most packages, you can generally use ANALYZE/IMAGE on one of thetE   core images, looking at the image identification area.  Some of thee,   product-specific mechanisms available are:  "     DQS   DQS$VERSION logical name     C     CC/VERSION     C++   CXX/VERSIONr    < ------------------------------------------------------------@ MGMT44. Where can I get Fibre Channel Storage (SAN) information?  8   http://www.openvms.compaq.com/openvms/fibre/index.html  < ------------------------------------------------------------. MGMT45. How can I split up an OpenVMS Cluster?  @   Review the VMScluster documentation, and the System ManagementB   documentation.  The following are the key points, but are likely.   not the only things you will need to change.  K   OpenVMS Cluster support is directly integrated into the operating system,fK   and there is no way to remove it.  You can, however, remote site-specifichB   tailoring that was added for a particular cluster configuration.  G   First: Create restorable image BACKUPs of each of the current system sH   disks.  If something gets messed up, you want a way to recover, right?  G   Create standalone BACKUP kits for the OpenVMS VAX systems, and create @   or acquire bootable BACKUP kits for the OpenVMS Alpha systems.  G   Use CLUSTER_CONFIG or CLUSTER_CONFIG_LAN to remove the various systemz>   roots and to shut off boot services and VMScluster settings.  D   Create as many architecture-specific copies of the system disks asD   required.  Realize that the new systems will all likely be bootingC   through root SYS0 -- if you have any system-specific files in anya   other roots, save them.i  E   Relocate the copies of the VMScluster common files onto each of thei   new system disks.o  D   Reset the console parameters and boot flags on each system for use   on a standalone node.b  D   Reset the VAXCLUSTER and NISCS_LOAD_PEA0 parameters to 0 in SYSGEN   and in MODPARAMS.DAT.k  <   Clobber the VMScluster group ID and password using SYSMAN.  9   Reboot the systems seperately, and run AUTOGEN on each.a  B   Shut off MOP services via NCP or LANCP on the boot server nodes.  G   Permanent seperation also requires the duplication of shared files.   <   The following files are typically shared within a cluster:  J   Filename:              default directory (in common root) and file type:/     SYSUAF                      SYS$SYSTEM:.DAT-/     SYSUAFALT                   SYS$SYSTEM:.DAT-/     SYSALF                      SYS$SYSTEM:.DAT?/     RIGHTSLIST                  SYS$SYSTEM:.DAT /     NETPROXY                    SYS$SYSTEM:.DATn/     NET$PROXY                   SYS$SYSTEM:.DAT /     NETOBJECT                   SYS$SYSTEM:.DATr/     NETNODE_REMOTE              SYS$SYSTEM:.DATeL     QMAN$MASTER                 SYS$SYSTEM: (this is a set of related files)/     LMF$LICENSE                 SYS$SYSTEM:.LDB 0     VMSMAIL_PROFILE             SYS$SYSTEM:.DATA/     VMS$OBJECTS                 SYS$SYSTEM:.DATr0     VMS$AUDIT_SERVER            SYS$MANAGER:.DAT0     VMS$PASSWORD_HISTORY        SYS$SYSTEM:.DATA0     NETNODE_UPDATE              SYS$MANAGER:.COM0     VMS$PASSWORD_POLICY         SYS$LIBRARY:.EXE@     LAN$NODE_DATABASE           SYS$SYSTEM:LAN$NODE_DATABASE.DAT  :   Information on changing node names is included in MGMT9.    < ------------------------------------------------------------; MGMT46. What file checksum tools are available for OpenVMS?o  F The undocumented DCL command CHECKSUM is the usual means, and providesJ a rather simple-minded checksum suitable to detect basic file corruptions.E For information and an OpenVMS version of the MD5 checksum tool, see:h  H   http://www.service.digital.com/svctools/decevent/md5-instructions.html  H The OpenVMS Alpha ECO (patch) kit checksums available at the ECO website8 are determined using the following DCL command sequence:  "   CHECKSUM kitname.pcsi-dcx_axpexe   SHOW SYMBOL CHECKSUM$CHECKSUMe  A See MGMT25 for information on acquiring OpenVMS ECO (patch) kits.n  < ------------------------------------------------------------9 MGMT47.  Configuring Cluster SCS for path load balancing?a    G SCS: Systems Communication Services.  The protocol used to communicate dD between VMSCluster systems and between OpenVMS systems and SCS-basedF storage controllers.  (SCSI-based storage controllers do not use SCS.)  I PORT: A communications device, such as DSSI, CI, Ethernet or FDDI.  Each eF CI or DSSI bus is a different local port, named PAA0, PAB0, PAC0 etc. : All Ethernet and FDDI busses make up a single PEA0 port.    F VIRTUAL CIRCUIT: A reliable communications path established between a H pair of ports.  Each port in a VMScluster establishes a virtual circuit & with every other port in that cluster.  7 All systems and storage controllers establish "Virtual  H Circuits" to enable communications between all available pairs of ports.  F SYSAP: A "system application" that communicates using SCS.  Each SYSAPE communicates with a particular remote SYSAP.  Example SYSAPs include:o  *   VMS$DISK_CL_DRIVER connects to MSCP$DISK8     The disk class driver is on every VMSCluster system.;     MSCP$DISK is on all disk controllers and all VMSClustero9     systems that have SYSGEN parameter MSCP_LOAD set to 1-  *   VMS$TAPE_CL_DRIVER connects to MSCP$TAPE8     The tape class driver is on every VMSCluster system.;     MSCP$TAPE is on all tape controllers and all VMSCluster :     systems that have SYSGEN parameter TMSCP_LOAD set to 1  +   VMS$VAXCLUSTER connects to VMS$VAXCLUSTERa>     This SYSAP contains the connection manager, which manages <     cluster connectivity, runs the cluster state transition <     algorithm, and implements the cluster quorum algorithm. <     This SYSAP also handles lock traffic, and various other %     cluster communications functions.i  *   SCS$DIR_LOOKUP connects to SCS$DIRECTORY7     This SYSAP is used to find SYSAPs on remote systemsm     MSCP and TMSCP v?     The Mass Storage Control Protocol and the Tape MSCP serversC=     are SYSAPs that provide access to disk and tape storage, s<     typically operating over SCS protocols.  MSCP and TMSCP ;     SYSAPs exist within OpenVMS (for OpenVMS hosts serving A8     disks and tapes), within CI- and DSSI-based storage >     controllers, and within host-based MSCP- or TMSCP storage >     controllers.  MSCP and TMSCP can be used to serve MSCP and=     TMSCP storage devices, and can also be used to serve SCSId1     and other non-MSCP/non-TMSCP storage devices.n  I SCS CONNECTION: A SYSAP on one node establishes an SCS connection to its rJ counterpart on another node.  This connection will be on ONE AND ONLY ONE " of the available virtual circuits.     ----  E When there are multiple virtual circuits between two OpenVMS systems nF it is possible for the VMS$VAXCLUSTER to VMS$VAXCLUSTER connection to I use any one of these circuits.  All lock traffic between the two systems v1 will then travel on the selected virtual circuit.d  H Each port has a "LOAD CLASS" associated with it.  This load class helps G to determine which virtual circuit a connection will use.  If one port PF has a higher load class than all others then this port will be used.  H If two or more ports have equally high load classes then the connection E will use the first of these that it finds.  Normally all CI and DSSI rF ports have a load class of 14(hex), the Ethernet/FDDI port has a load  class of A(hex).  @ For instance, if you have multiple DSSI busses and an FDDI, the G VMS$VAXCLUSTER connection will chose the DSSI bus as this path has the tG system disk, and thus will always be the first DSSI bus discovered whena the OpenVMS system boots.i  H To force all lock traffic off the DSSI and on to the FDDI, an adjustmentF to the load class value is required, or the SCS port must be disabled.  K Note that with PE ports, you can typically immediately re-enable the path, dG permitting failover to occur should congestion or a problem arise -- a  H running average of the path latency is checked when the virtual circuit K is formed, and at periodic intervals (circa every three seconds), and when  ) a problem with a virtual circuit arises. a  E In the case of PEDRIVER, the driver handles load balancing among the pD available Ethernet and FDDI connections based on the lowest latency E path available to it.  Traffic will be routed through that path untilu* an event occurs that requires a fail-over.  / In all OpenVMS versions, you can use the tools:0     SYS$EXAMPLES:LAVC$STOP_BUS o   SYS$EXAMPLES:LAVC$START_BUS   B These tools permit you to disable or enable all SCS traffic on the on the specified paths.-  E You can also use a prefered path mechanism that tells the local MSCP lH disk driver (DUDRIVER) which path to a disk should be used.  Generally, E this is used with dual-pathed disks, forcing I/O traffic through one nH of the controllers instead of the other.  This can be used to implement 9 a crude form of I/O load balancing at the disk I/O level.T  7 Prior to V7.2, the prefered path feature uses the tool:e     SYS$EXAMPLES:PREFER.MAR   A In OpenVMS V7.2 and later, you can use the following DCL command:      SET PREFERED_PATHt  F The prefered path mechanism does not disable nor affect SCS operations on the non-prefered path.GG                               [Kevin Jenkins, Verell Boaen, John Croll]e  < ------------------------------------------------------------; MGMT48. What (and where) is the OpenVMS Management Station?r  E   For information and current kits for the OpenVMS Management StationnG   (OMS), a PC-based tool that permits you to manage an OpenVMS system, t
   please see:[  9     http://www.openvms.compaq.com/openvms/products/argus/p  < ------------------------------------------------------------: MGMT49. How to determine current disk fragmentation level?  G   The Compaq OpenVMS Disk File Optimizer (DFO) defragmentation package iL   provides a fragmentation monitoring tool, and a DFO product authorization A   key (PAK) is not required for the fragmentation reporting tool:i     $ DEFRAG SHOW/VOLUME ddcu:  G   The DFU tool available on the OpenVMS Freeware can generate a report h   on the disk fragmentation:     DFU> REPORT ddcu:t    < ------------------------------------------------------------@ MGMT50. SYSBOOT-I-FILENOTLOC, Unable to locate SYS$CPU_ROUTINES?  ;   A message at the OpenVMS bootstrap such as the following:.  A %SYSBOOT-I-FILENOTLOC, Unable to locate SYS$CPU_ROUTINES_1C02.EXEe< %SYSBOOT-E-LDFAIL, failed to load execlet, status = 00000910  @   indicates that the particular OpenVMS release does not contain>   support for the target platform.  In this case, OpenVMS doesB   not recognize Alpha family 1C member 02 as a supported platform.A   A later version of OpenVMS might support the platform, or there %   might be no support on any release.S  E   The execlet load failure and other similar bootstrap status values I@   can often be decoded using either of the following techniques:   $ exit %x910" %SYSTEM-W-NOSUCHFILE, no such file $O   $ x = f$message(%x910) $ show symbol xh*   X = "%SYSTEM-W-NOSUCHFILE, no such file" $o  < ------------------------------------------------------------F MGMT51. How can I customize the DCPS device control for a new printer?  E   To customize DCPS for an otherwise unsupported printer, you can tryy   the following sequence:h  H   o Extract the most closely-associated setup modules from the existing E     device control library, DCPS$DEVCTL.TLB.  (For instance, you can eE     probably extract and use the HP LaserJet 4000 series definitions lD     for the HP LaserJet 4050 series.  Each printer will vary, pleaseF     consult the printer documentation for specifics and requirements.)  :   o rename each extracted setup module to a corresponding:       LPS$$UNRECOGNIZED_*e  G   o Insert all of the above-renamed setup modules into a newly-created n7     device control library specific to the new printer:p       $ LIBRARY/TEXT/CREATE -t/           SYS$COMMON:[SYSLIB]HP4050_DEVCTL.TLB u           LPS$$UNRECOGNIZED*  H     The above assumes the filename HP4050_DEVCTL.TLB, alter as required.  H   o Set up your DCPS startup procedures to include a search-list logical     name such as:   1      $ DEFINE/SYSTEM/EXECUTIVE DCPS_HP4050_LIB  - )          SYS$LIBRARY:HP4050_DEVCTL.TLB, -s$          SYS$LIBRARY:DCPS$DEVCTL.TLB  I   o Supply DCPS_HP4050_LIB as the library parameter in the queue startup oG     for this printer, this is the P3 parameter to the command procedure,)     SYS$STARTUP:DCPS$EXECUTION_QUEUE.COM.i  G   o The HP4050_DEVCTL library may/will need to be recreated and modulestF     re-edited and replaced with each DCPS upgrade, particularly if anyG     modules are updated in the original library.  You will also want to D     determine if the upgraded version of DCPS directly supports the      particular printer.o  B   o To customize the processing of file extensions within DCPS (toI     enable or disable graybar output, for instance), use the information n     available in:S  ;       SYS$LIBRARY:DCPS$FILE_EXTENSION_DATA_TYPE.DAT_DEFAULT   %     to create your own site-specific:s  3       SYS$LIBRARY:DCPS$FILE_EXTENSION_DATA_TYPE.DATn     Also see MGMT23.D                                          [Ken Fairfield, with typos G                                          introduced by Stephen Hoffman]h  < ------------------------------------------------------------D MGMT52. Why do $GETDEV MOUNTCNT and SHOW DEVICE mount counts differ?  C   MOUNTCNT returns the local mount count, while SHOW DEVICE returnst   the cluster-wide mount count.s  :                                          [Stephen Hoffman]  < ------------------------------------------------------------8 MGMT53. What software is needed for Postscript printers?  F   The NorthLake PrintKit (http://www.nls.com/) and DECprint SupervisorI   (DCPS; http://www.openvms.compaq.com/openvms/Print/print_sw_prods.html)cC   are common choices for support of Postscript printers on OpenVMS.c  < ------------------------------------------------------------D MGMT54. Does volume shadowing require a non-zero allocation classes?  C   Yes, use of host-based volume shadowing requires that the disk(s)d8   involved be configured in a non-zero allocation class.  >   Edit SYS$SYSTEM:MODPARAMS.DAT to include a declaration of anA   non-zero allocation class, such as setting the host allocation s   class to the value 7:s     ALLOCLASS = 7n  &   Then AUTOGEN the system, and reboot.  B   You should now be able to form the shadow set via a command such   as the following:t  >     MOUNT dsa1007: /SHADOW=($7$dkb300:,$7$dkb500:) volumelabel  D   When operating in an OpenVMS Cluster, this sequence will typicallyB   change the disk names from the SCSNODE prefix (scsnode$dkann) toE   the allocation-class prefix ($7$dkannn).  This may provide you withtF   the opportunity to move to a device-independent scheme using logicalD   name constructs such as the DISK$volumelabel logical names in yourB   startup and application environments; an opportunity to weed out   physical device references.i;                                               [Veli Korkko]s  < ------------------------------------------------------------! MGMT55. section duplicated MGMT28a  < ------------------------------------------------------------9 MGMT56. How do I remove a PCSI-installed patch (ECO) kit?   1 You cannot PRODUCT REMOVE a PCSI patch (ECO) kit.A  E In order to do this, PCSI would have to have copies of all the other SI version of the files from all other patches and products that previously pE were installed.  This can clearly involve a large number of files andUB a large archive of old file versions and a substantial quantity ofC disk space.  While removal is clearly theoretically possible, it isn not currently implemented.  D The following is the supported mechanism to remove a PCSI patch kit.  @ (1) Execute a PRODUCT SHOW PRODUCE <product-name. /FULL command.C     The "MAINTENANCE" column (132 col width) shows the patches thatT.     have been installed.  Keep a copy of this.  @ (2) Re-install the prior FULL version of the product.  This willA     remove all patch kits, setting to product back to "original" t     condition.  @ (3) Re-install all the patches in the list from step 1, *EXCEPT*4     those which you have determined you do not want.  8 The above information also applies to PCSI PARTIAL kits.  < ------------------------------------------------------------@ MGMT57. SYSINIT-E, error mounting system device, status=0072832C  >   This message can arise during an OpenVMS system bootstrap...  E   %MOUNT-F-DIFVOLMNT, different volume already mounted on this device   ;   For details and further information, use the DCL command:e  #     $ HELP/MESSAGE /STATUS=%X72832Cl  < ------------------------------------------------------------/ MGMT58. Performing SET HOST/MOP in DECnet-Plus?   &   First, do MCR NCL SHOW MOP CIRCUIT *  /   Let's say you have a circuit known as FDDI-0.l8   Here is an example of the SET HOST/MOP command syntax:  ;     $ SET HOST/MOP/ADDRESS=08-00-2B-2C-5A-23/CIRCUIT=FDDI-0d     Also see MGMT13.  < ------------------------------------------------------------' MGMT59. Resolving License PAK Problems?   E   The PAK release date, the PAK termination date, and the PAK versionsG   are the usual culprits when a license product authorization key (PAK)k   check failure occurs.s  H   The PAK termination date is the date when the license PAK will expire.  I   The PAK release date is the date of the most recent release date of theoH   software package that will be permitted by the particular license PAK.C   (The release date check is analogous to a product version check.) C   The PAK version indicates the most recent product version that isp   permitted by the license.   E   Having multiple license PAKs registered (and active) can also causeoC   problems if an expired PAK gets loaded.  You will want to DISABLEe.   license PAKs you do not wish to have loaded.  F   Other problems include a failure to register each PAK in all licenseH   databases throughout a multiple-system-disk cluster, with a consistentE   set of /INCLUDE lists specified across each of the duplicated PAKs.t  K   Additionally, you could have an invalid LMF$LICENSE logical name defined.IK   (If no LMF$LICENSE logical name is defined, the standard license databaseG1   named SYS$SYSTEM:LMF$LICENSE.LDB will be used.)L  J   You can display license failures by defining the following logical name:  2     DEFINE/SYS/EXEC LMF$DISPLAY_OPCOM_MESSAGE TRUE  K   Enable your terminal as a license operator (REPLY/ENABLE=LICENSE), defineoF   the LMF$DISPLAY_OPCOM_MESSAGE logical name, and then try the failingH   operation again.  You should see one or more OPCOM messages displayed.  I   If you have the LMF$DISPLAY_OPCOM_MESSAGE logical name defined, you canYF   (will?) see spurious license check failures -- various products willJ   check for multiple licenses, and a few products will check for PAKs thatL   either have not yet been or will not be issued.  Once you figure out whichB   license has failed, you will want to deassign this logical name.  E   Note: that there is no license check failure does NOT indicate that E   the particular product or operation is permissible per the license.   I   To register a license PAK on a DECwindows system when DECwindows cannot K   start (because of an expired license or other licensing problem), follow ML   the steps outlined in section MGMT5 up through step 4 (inclusive).  Using J   the console -- analogous to what is done in step 5 to access the OpenVMSD   AUTHORIZE utility -- use the console to register the license PAKs.  < ------------------------------------------------------------, MGMT60. Changing the OpenVMS Version Number?  D   Fool your friends, baffle your enemies, run the OpenVMS version of   your choice!     OpenVMS Alpha:&     $ SET DEFAULT SYS$COMMON:[SYS$LDR]     $ RUN SYSVER     REPLACE V9.9	     WRITEp
     $ EXIT     OpenVMS VAX:&     $ set default SYS$COMMON:[SYS$LDR])     $ copy SYS.EXE SYS.EXE_IN-CASE-I-FAIL      $ patch SYS.EXEw"     define sys$gq_version=800044b8     set mode ascii     !examine sys$gq_versione     !examine sys$gq_version+4 %     deposit sys$gq_version   = "V9.9"f%     deposit sys$gq_version+4 = "    "h
     update     exit
     $ Exit  )   Then reboot the system at your leisure.7   [End of Part 2/5]r  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  # Date: Tue, 10 Apr 2001 18:10:14 GMT 2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman); Subject: OpenVMS Frequently Asked Questions (FAQ), Part 3/5 2 Message-ID: <a0IA6.750$fB6.19160@news.cpqcorp.net>   Archive-name: dec-faq/vms/part3  Posting-Frequency: quarterly Last-modified: 10 Jul 2001 Version: VMS-FAQ-3.TXT(6)e    9 This is the OpenVMS Frequently Asked Questions Part 3/5. s@ Please see Part 1/5 for administrivia, indexing, archiving, etc.      t< ------------------------------------------------------------$ MAIL1.  How do I send Internet mail?  K The simplest answer on most OpenVMS V6.2 and later systems: just enter the  J Internet (SMTP) address at the "to" prompt in MAIL.  On most such systems,5 this will send your email to the specified recipient.I  L That said, there is no one answer to this question.  Internet mail is built J upon the TCP/IP protocols, which are not directly supported by OpenVMS -- K support requires the installation of a package that understands TCP/IP and  J specifically one that provides the Simple Mail Transport Protocol (SMTP).   P A number of implementations of TCP/IP are available for OpenVMS -- from Compaq, J from third parties, and even a free "support it yourself" form.   The MAILL program  that comes with OpenVMS does not directly support the mail protocolJ used on the  Internet (though it does recognize SMTP addresses in V6.2 andH later), but various  programs have been written that use MAIL's "foreignE protocol" facility to provide  such support -- these tools are callednM transports.  To send mail through a transport,  place the transport specifierm2 at the front, and (typically) quote the address.    H For example, IN%"hoffman@bogushost.compaq.com" -- you *must* include theM quotation  marks -- indicates that IN transport will be used to send the mail M to the address  hoffman@bogushost.compaq.com.  Common names for the transport P are IN%, MX%, and SMTP%. (MX is a widely used, free, mail handler; see question O SOFT1.  SMTP% is used by  Compaq's TCP/IP Services product.)  Other systems mayvM use some other name.  If none  of these prefixes work, please ask your system  manager for assistance.S 					[leichter@lrw.com]C 					[Stephen Hoffman]   See also MAIL2.e  < ------------------------------------------------------------J MAIL2.  How do I get IN% or MX% added automatically to Internet addresses?  E For older OpenVMS releases, you can acquire the MAILSHR_PATCH packageSB (there's one each for VAX and Alpha) from the WKU FILESERV server  (see question SOFT1.).  H As of OpenVMS V6.2, this is not necessary -- simply enter the SMTP emailK address directly.  If the address specified to MAIL contains an embeded "@"sJ character in it (a quoted string is not needed), MAIL will look to see if I the logical name MAIL$INTERNET_TRANSPORT is defined.  If it is, then MAILhJ will use the translation as the transport protocol, otherwise it will use ? the SMTP transport as is used by TCP/IP Services for OpenVMS.  t  B To alter this, for example, if you wanted IN% added, you'd define   MAIL$INTERNET_TRANSPORT as "IN".  < ------------------------------------------------------------K MAIL3.  How do I automatically append a signature file to my mail messages?u  I OpenVMS 7.0 adds the ability to automatically append signature files - in E MAIL, use the SET SIGNATURE command to specify a signature file name.r3 For earlier versions, see the following paragraphs.   K The basic MAIL utility which is shipped with VMS does not have an intrinsictG mechanism for adding signature files.  If you're using an enhanced maileG handling package (e.g PMDF), however, it may have provisions for addinguH signature files to all messages it handles - check the documentation forF details.  In addition, it's common practice to use an editor to handleK addition of `quotation marks' (e.g. >) and signature files to mail messageseK and news postings.  There are several implementations of this for differentcI editors available on the net; for one example, see the MAIL_EDIT package.r   ftp://ftp.wku.edu/vms/narnia/n    					[bailey@genetics.upenn.edu]  F Define the logical MAIL$EDIT to a COM-file, which looks something like the following:   $ IF P1 .NES. "" $ THEN# $    COPY 'P1',<signaturefile> 'P2'a $ ELSE $    COPY <signaturefile> 'P2' $ ENDIFi$ $ DEFINE/NOLOG SYS$INPUT SYS$COMMAND $ <editorname> 'P2't $ EXIT  L Where <signaturefile> is the name of the signature-file (including directoryM and disk) and <editorname> is EDIT/EDT or EDIT/TPU (or your favorite editor).o 					[Arne Vajhj]  < ------------------------------------------------------------A MAIL4.  Do I have to use VMS MAIL?  I like my Unix mailer better.V  M Several Unix mailers have been ported to VMS, some by the vendors of specificnL TCP/IP packages, some by users who have made them freely available.  See theF documentation for your TCP/IP package, and refer to question SOFT1 for5 information about the availability of the free ports.  					[Jerry Leichter]J  < ------------------------------------------------------------L MAIL5.  How can I forward my mail?  Can I forward it to an Internet address?  M You can use the SET FORWARD command within MAIL to specify where you want allnM your mail forwarded to.  Use SHOW FORWARD to see your current forwarding.  Toe* cancel all forwarding, type SET NOFORWARD.  L You can forward your mail to an Internet address, but you have to be carefulL because of the way MAIL handles special characters, such as quotation marks.M First, determine the address you would use to send mail to the place you wantiG to forward to - say, IN%"fred@fred-host.xxx.com".  Take that string andtJ *double all the quotation marks*, producing IN%""fred@fred-host.xxx.com"".L Finally, wrap quotation marks around the outside and use the the result with SET FORWARD:  1 	MAIL>SET FORWARD "IN%""fred@fred-host.xxx.com"""R  + If you do SHOW FORWARD, you should now see:-  = 	Your mail is being forwarded to IN%"fred@fred-host.xxx.com".b 					[leichter@lrw.com]I  C Note that the MAIL$INTERNET_TRANSPORT feature doesn't yet work with F SET FORWARD in that you'll still have to use the syntax above with the quotation marks.  < ------------------------------------------------------------9 MAIL6.  How can I forward my mail to a list of addresses?h  H VMS MAIL does not support forwarding a message to more than one address.L (Older versions of MAIL allowed you to specify such forwarding, but it never worked correctly.)  M Many of the TCP/IP mail packages support forwarding to mailing lists, as doesdJ the free MX mail handling system and the DELIVER mail "extender".  See the8 documentation of your TCP/IP package and question SOFT1. 					[leichter@lrw.com]   < ------------------------------------------------------------J MAIL7.  MAIL keeps saying I have new messages, but I don't.  What do I do?  G The count of new mail messages is kept separately from your mail folder I in SYS$SYSTEM:VMSMAIL_PROFILE.DATA.  It sometimes happens that this count G differs from what's in your mail folder.  If this happens, go into MAILaI and repeat the READ/NEW command until you see no new mail messages.  ThenSG enter the command one more time.  This will resynchronize the counters.H  < ------------------------------------------------------------@ MAIL8.  How do I move all of my mail messages to another system?  N If you are moving to another OpenVMS system, perhaps the best way is to select each folder and do (in MAIL) a:   # 	EXTRACT/APPEND/ALL/MAIL mymail.mail  < Move MYMAIL.MAI to the other system, then do this (in MAIL):   	SET FILE mymail.mai 	COPY/ALL foldername MAIL.MAI   G This will place a copy of all of your messages in the given folder.  IfBI you wanted to maintain the separate folders, do separate EXTRACT commands5G (above) specifying different .mai files, then repeat the SET FILE, COPYe
 for each one.s  H If you are moving to a non-OpenVMS system, the EXTRACT command above canI be used to create a file which you can then copy - how you import it intoL. your mailer is an exercise left to the reader.  < ------------------------------------------------------------6 MAIL9.  How do I send or read attachments in VMS MAIL?  I Is there any way to send or read mail with files as attachments from VMS?i  C Not directly with the OpenVMS MAIL facility, but there are several l other options:  H 1. Install PINE, available commercially from Innosoft or free from Andy F    Harper.  With PINE you can both send and receive MIME messages, if .    you have the appropriate viewers available.      http://www.innosoft.com/p4      http://www.agh.cc.kcl.ac.uk/files/vms/pine-vms/+      ftp://ftp2.kcl.ac.uk/pub/vms/pine-vms/u  K 2. If you're working from an X11 server use the OpenVMS version of NetscapeOI    Navigator.  This option is ok for sending mail, but is not optimal for H    reading it, since Netscape will use POP and remove messages entirely A    the OpenVMS MAIL system, which is not generally what you want.   B 3. MPACK/MUNPACK.  To send a MIME mail, construct the message withH    attachments manually using MPACK.  You cannot send the resulting fileD    directly through MAIL because an extra  blank header line will beI    inserted between your message and the OpenVMS MAIL headers, which willeI    cause the message to appear as plain text in most mail programs.  SomeoD    TCP/IP stacks provide a work around for this problem, and if thatK    doesn't work, you should generally be able to force the message directly I    into the SMTP port of your mail machine.  Examples of both methods are.    in: o:      http://seqaxp.bio.caltech.edu/pub/SOFTWARE/mmail.com   K    To read a MIME mail message, open it in MAIL, extract it to a file, then-;    use MUNPACK to break out and decode the attachments.    h   					[David Mathog]e  ; 4. With OpenVMS V7.2 and later, use the supplied MIME tool.w    < ------------------------------------------------------------4 UTIL1.  How do I play an audio CD on my workstation?  8 If you've installed the DECwindows examples, you'll findD DECW$CDPLAYER.C, .DAT, .EXE, .UIL, and .UID.  Copy the .UID and .DATL files to DECW$USER_DEFAULTS: (typically SYS$LOGIN:), define the logical nameH DECW$CD_PLAYER to be the device name of your CD-ROM drive (eg. DKA400:),G give yourself PHY_IO and DIAGNOSE privileges, and run the .EXE.  (ThesehH privileges are required, as the access to the CD-related extensions willK require the use of the privilege-protected IO$_DIAGNOSE I/O function code.)cI You can also install the image with these privileges.  See the source formB additional details - note that the comments regarding the need forD SYSGEN CONNECT are no longer applicable (at least as of VMS V5.5-2).  F There's also SYS$EXAMPLES:CDROM_AUDIO.C and .EXE, a non-Motif program,F available on OpenVMS VAX, and DECW$EXAMPLES:DECW$CDPLAYER.* on OpenVMS VAX and OpenVMS Alpha.  A The standard OpenVMS IDE DQDRIVER does not support the necessary 2H IO$_DIAGNOSE function required for access to audio CD media (on OpenVMS G versions prior to V7.3), but an updated DQDRIVER device driver (source TJ code and all) with this capability and with the source code of an updated = CD audio player is available on the OpenVMS Freeware website tH (www.openvms.compaq.com/freeware/dqdriver/), and these updates are also 3 expected to be included on Freeware V5.0 and later.h  < ------------------------------------------------------------: UTIL2.  How do I access a MS-DOS floppy disk from OpenVMS?  E The Compaq Advanced Server (formerly known as PATHWORKS) for OpenVMS tG product includes an unsupported and undocumented utility called PCDISK,-A and this tool can read and write various MS-DOS format diskettes.s  H ProGIS in Germany sells a product called VMove which supports DOS files C on many different device types.  For more information, send mail toe info@progis.de.t  H Engineering Software has a product called VAKSAT which will read, write,D and erase files on DOS diskettes.  Available for both VAX and Alpha.0 Contact ed@cityscape.co.uk for more information.  D MadGoat PC Exchange (PCX) is a utility for copying files to and fromD MS-DOS (FAT) format diskettes under VMS, using an RX23 (3.5"), RX26 I (3.5"), or RX33 (5.25") diskette drive.  For 3.5" diskettes, high-densityVF disks can be read or written; double-density disks are read-only. Only- high-density disks are supported on the RX33.u     http://www.madgoat.com/L  < ------------------------------------------------------------L UTIL3.  How do I play sound files on an AlphaStation?  DECsound doesn't work  I The new AlphaStation systems use a different sound board (Microsoft SoundaK System) than the earlier DEC 3000 AXP systems, and DECsound, as supplied byMH DECwindows Motif, doesn't support this board.  Compaq offers an optional) product, Multimedia Services for OpenVMS:-  !   http://www.compaq.com/info/spd/-   J which provides a replacement DECsound for this card as well as many other > features (an AVI and MPEG player, video capture support, etc.)  ( Ensoniq sound support is also available.  < ------------------------------------------------------------3 UTIL4.  Why is DECmigrate not working with Fortran?   : OTS-F-INDATCOR internal data corrupted in Run-time Library  @ This error can arise with Fortran programs if you are running a < recent version of OpenVMS Alpha, and are using DECmigrate toA translate Fortran applications.  The DECmigrate Run-Time Library rA attempts to support mixed translated-native I/O to the same unit aA by sharing the native Fortran RTL's internal data structures, and > in OpenVMS 7.2 these structures changed and the translated RTL was not updated accordingly.  A You can copy DEC$FORRTL.EXE from OpenVMS 7.1, copying it to some tB spare directory, and then defining the logical name DEC$FORRTL to G point to it before running your translated application.  Or rebuilding sA the application to use the available native Fortran compiler.  Or D you can apply the current Fortran RTL kit, which has a fix for this.   See SOFT13.n2                                     [Steve Lionel]  < ------------------------------------------------------------2 UTIL5.  How do I read IBM EBCDIC tapes on OpenVMS?  I IBM boxes can read ANSI-labeled ASCII magtapes.  Fixed-length records andaJ the DCL COPY command can be used to transfer text files around.  Check the IBM documentation for details.  K There exists various freeware around (TAPECOPY, ETAPE, TCOPY, MTEXCH) that  K can read and write EBCDIC tapes.  Visit the DECUS website software archivesdC search engine (via http://www.decus.org/), and search for "EBCDIC".p3                                     [Steve Hoffman]w   One source for ETAPE is:  (   http://www.ualr.edu/ftp/vms/ETAPE_SRC/  7 OpenVMS Freeware V5.0 is expected to include this tool.l5                                     [Fletcher Hearns]o1                                     [Dale Miller]   < ------------------------------------------------------------/ UTIL6.  How can I patch an OpenVMS Alpha image?   &   Using the OpenVMS Freeware tool ZAP:  .     www.openvms.compaq.com/freeware/rms_tools/  ?   tell ZAP to read a block (bucket) of information based on theo<   virtual block number (VBN), using X for hexadecimal.  Dump?   yourself into the OpenVMS debugger with R2 pointing into the U<   buffer, EXAMINE/INSTRUCTION as needed, alter the buffer as@   required, GO to get out of the debugger and back into ZAP, and3   use the ZAP W command to write the updated block.o  >   OpenVMS Freeware V5.0 is expected to have an updated version   of the ZAP tool.    < ------------------------------------------------------------. DCL1.   How do I run a program with arguments?  K The RUN command does not accept arguments.  To pass arguments to a program,S> you must use what is called a "foreign command".  For example:  ! 	$ unzip :== $disk:[dir]unzip.exe  	$ unzip -?s  H The leading $ in the equivilence name for the symbol definition is what G makes the DCL symbol a foreign command. If the device and directory are   omitted, SYS$SYSTEM: is assumed.  D Under OpenVMS V6.2 and later, DCL supports automatic foreign commandG definition via the logical name DCL$PATH:.  An example of a definition   of this logical name is:  >     $ DEFINE DCL$PATH SYS$DISK:[],ddcu:[mytooldir],SYS$SYSTEM:  N DCL will first look for a command in the DCL command table, and if no match isN found and if DCL$PATH is defined, it will then look for command procedures andG executable images with filenames matching the command specified, in the/J directories specified via DCL$PATH.  The first match found is invoked, andH under OpenVMS, the DCL$PATH support will cause a command procedure to be/ activated in preference to an executable image.d  H For more information on foreign commands or on automatic foreign command' support, see the OpenVMS User's Manual.n   See also question PROG2.  L If you want to create a detached process that takes arguments from a commandJ line, it must be run under the control of a command line interpreter (CLI)E (typically DCL).  This is done by placing the command line in a file,aN specifying SYS$SYSTEM:LOGINOUT.EXE as the image to run and the command file as the input.  For example:    	$ OPEN/WRITE CMD TEMP_INPUT.COM$ 	$ WRITE CMD "$ MYCOMMAND arguments" 	$ CLOSE CMD9 	$ RUN/DETACHED SYS$SYSTEM:LOGINOUT /INPUT=TEMP_INPUT.COMa  N Various OpenVMS library calls (such as lib$spawn(), cli$dcl_parse(), and the CK library system() call) require access to a command line interpreter such asoF DCL to perform requested actions, and will not operate if a CLI is not
 available.  J When a CLI is not available, these calls typically return the error statusL SS$_NOCLI.  And as mentioned above, invoke the image LOGINOUT to cause a CLIH (such as DCL) to be mapped into and made available in the context of the target process.p  G For examples of how TCP/IP Services sets up its foreign commands (whichtI includes tools such as uuencode and uudecode), please see the DCL commandn0 procedure SYS$STARTUP:TCPIP$DEFINE_COMMANDS.COM.   Also see DCL11.  					[Stephen Hoffman]  < ------------------------------------------------------------/ DCL2.   How can I redefine control keys in DCL?   C The DCL DEFINE/KEY command allows you to define function and keypadeF keys, but not control keys.  Also, keys you define with DEFINE/KEY areD not recognized inside applications.  Many applications which use the: SMG$ routines for input have a similar DEFINE/KEY feature.  G The terminal driver line-editing control keys, including the use of DEL- for delete, are not modifiable.-  < ------------------------------------------------------------* DCL3.   How can I clear the screen in DCL?  0 The simplest way is the TYPE/PAGE NLA0: command.  > You can set up a symbol to clear the screen in your LOGIN.COM:   $ CLS :== TYPE/PAGE NLA0:O  < ------------------------------------------------------------< DCL4.   Using REPLY/LOG from DCL?  Disabling Console OPCOMs?  @ Your terminal must be enabled as an operator terminal before theA REPLY/LOG command can be used, but a DCL procedure (batch commandN@ file, system startup, etc) does not have an associated terminal.B To make this work, use the following sequence to enable the OPA0: B console as the operator terminal, then the REPLY/LOG command will  be accepted:  "   $ DEFINE/USER SYS$COMMAND _OPA0:
   $ REPLY/LOGI"   $ DEFINE/USER SYS$COMMAND _OPA0:   $ REPLY/ENABLE  H To disable the system console terminal (OPA0:) as an operator terminal,  use the following command:  "   $ DEFINE/USER SYS$COMMAND _OPA0:   $ REPLY/DISABLEl  A Also see SYLOGICALS.COM (and SYLOGICALS.TEMPLATE) for informationoC on configuring the behaviour of OPCOM, including the (default) use w? of the system console (OPA0:) as an operator terminial and the V@ specific contents and behaviour of the system operator log file 
 OPERATOR.LOG.u 						[Arne Vajhj]e 						[Stephen Hoffman]M  < ------------------------------------------------------------1 DCL5.   How do I generate a random number in DCL?i  B Here's my random number generator for inclusion into the OVMS FAQ;@ just do a GOSUB RAND and the global symbol RANDOM will contain aF randomly generated number.  The user/programmer can feed the generator0 a ceiling value (__CEIL) or a new seed (__SEED).  D $! RAND - returns a positive random number ("RANDOM") between 0 and  $!        __CEIL - 1.[ $ RAND:n $c $ IF F$TYPE(__SEED) .EQS. "" $ THEN- $     ! seed the random number generator, ...e $     __NOW = F$CVTIME()& $     __HOUR = 'F$EXTRACT(11,2,__NOW)'( $     __MINUTE = 'F$EXTRACT(14,2,__NOW)'( $     __SECOND = 'F$EXTRACT(17,2,__NOW)'& $     __TICK = 'F$EXTRACT(20,2,__NOW)' $ A $     __SEED == __TICK + (100 * __SECOND) + (6000 * __MINUTE) + -i          (360000 * __HOUR)D $     ! the generator tends to do better with a large, odd seed, ... $     __SEED == (__SEED .OR. 1)- $     ! clean up, ...- $     DELETEX/SYMBOL __NOW $     DELETEX/SYMBOL __HOURM $     DELETEX/SYMBOL __MINUTEt $     DELETEX/SYMBOL __SECONDv $     DELETEX/SYMBOL __TICK  $ ENDIFr $f5 $ IF F$TYPE(__CEIL) .EQS. "" THEN __CEIL = %X3FFFFFFFe $e $ __SEED == __SEED * 69069 + 1 $e7 $ RANDOM == (__SEED.AND.%X3FFFFFFF)/(%X40000000/__CEIL)F $f $ RETURN$ 					[sharris@sdsdmvax.fb3.noaa.gov]  < ------------------------------------------------------------% DCL6.   What does the MCR command do?L  D The MCR command runs the specified image, with a default filespec ofH SYS$SYSTEM:.EXE, and passes any (optional) command line arguments in the2 same manner as a foreign command.  In other words:   	$ MCR FOO BAR   is equivalent to:a   	$ FOO :== $FOO,
 	$ FOO BAR  F It derives from the RSX operating system from which VMS evolved and isI still often used as a shortcut for activating images.  The MCR command is J different from the MCR command line interpreter, which is provided as partI of the optional VAX-11 RSX product that provides RSX emulation under VMS.k  < ------------------------------------------------------------2 DCL7.   How do I change the OpenVMS system prompt?  M You can use the SET PROMPT command for this purpose.  SET PROMPT sets the DCLE prompt to the specified string.x  K When you want to display variable information, you will need to establish a K tie-in that provides the information to the SET PROMPT command as required.t  K If you wish to display the default directory for instance, you will have totL establish a tie between the SET DEFAULT command and the SET PROMPT commands,N as there is no direct way to get the default directory as the DCL prompt.  YouM can easily acquire or create a set of DCL command procedures that perform theaM SET DEFAULT and SET PROMPT for you.  These DCL command procedures often use ai command such as:  !   $ set prompt='f$env("default")'   L More advanced users could implement a system service or other intercept, andF use these tools to intercept the directory change and reset the promptN accordingly.  (This approach likely involves some kernel-mode programming, andG requires write access to various undocumented OpenVMS data structures.)A  E There are related tools available from various sources, including the  following web sites:  $   o ftp://ftp.hhs.dk/pub/vms/setpmt/  -   o ftp://ftp.tmesis.com/sys_service_hook.src   A   o James F. Duff has also made available a Macro32 tool known asaH     TIME_PROMPT, a tool that sets the prompt to the current system time.  D   o Many folks have contributed DCL procedures to perform this task.>     Visit the newsgroup archives for information and examples.  H Information in this section has been acquired from various postings thatG have discussed this topic in the comp.os.vms newsgroup in the past, andVI examples from Arne Vajhoej, Brian Schenkenberger, James Duff, and others.a   				[Stephen Hoffman]/  < ------------------------------------------------------------< DCL8.   Can I do DECnet task-to-task communication with DCL?   Yes, you can do this with DCL.  H The OpenVMS DECnet documentation shows various simple examples using theJ task object and the TYPE command to trigger the execution of a DCL commandJ procedure on a remote node.  A slightly more advanced example of using DCLJ for DECnet task-to-task -- a procedure that acts as both the client and asD the server as appropriate, and that uses a basic form of half-duplex communications -- is included:           $! x.com	         $-@         $! This procedure must be in the user's login directory.B         $! Requires a self-referential (not reverential :-) proxy:L         $!    UAF> add/prox <LocalNode>::<CurrentUser> <CurrentUser>/default?         $! Author: Stephen Hoffman, OpenVMS Engineering, Compaqa	         $a         $ goto 'f$mode()'n         $INTERACTIVE: *         $ open/read/write chan 0::"task=x"         $ write chan "Hello"         $ read chan parameterw         $ close chan$         $ write sys$output parameter         $ exit         $BATCH:n         $OTHER:/         $NETWORK:/&         $ open/read/write chan sys$net         $ read chan parameterM-         $ write chan "''parameter' yourself!"i         $ close chan         $ exit  -   An example of a run of the above procedure:u           $ @x         Hello yourself!t	         $M    L DCL does not include support asynchronous I/O, thus a predetermined protocolH or a predetermined "turn-around" command sequence must be implemented inI order to avoid protocol deadlocks -- cases where both tasks are trying to J write or both tasks are trying to read.  The task that is writing messagesI to the network must write (or write and read) a predetermined sequence ofeJ messages, or it must write a message that tells the reader that it can nowL start writing messages.  (This is the essence of a basic half-duplex network protocol scheme.)r 					[Stephen Hoffman]  < ------------------------------------------------------------6 DCL9.   How can I get the width setting of a terminal?  *   $ width = f$getdvi(terminal,"DEVBUFSIZ")  < ------------------------------------------------------------/ DCL10.  How can I substitute symbols in a PIPE?[  :   Use ampersand substitution, not apostrophe substitution.  G     $ pipe show system | search sys$input opcom | (read sys$input pid ;-C            pid=f$element(0," ",pid) ; define/system opcom_pid &pid)u     $ show log opcom_pid2        "OPCOM_PID" = "0000020B" (LNM$SYSTEM_TABLE);                                            [Norm Lastovica]R  < ------------------------------------------------------------7 DCL11.  Use of RUN/DETACH, LOGINOUT, and logical names?.  6   With a command to create a detached process such as:  <     $ RUN/DETACHED SYS$SYSTEM:LOGINOUT /INPUT=TEMP_INPUT.COM  C   If you are trying to use a logical name as the /INPUT, /OUTPUT orpE   /ERROR on a RUN/DETACH command, then you must translate the logicalaD   name specifications to physical references before passing them, orF   the definitions must reside in a logical name table that is visible    to the newly-created process.   H   Also note that LOGINOUT only creates the SYS$LOGIN, SYS$LOGIN_DEVICE, J   and SYS$SCRATCH logical names if it is processing a login that is based H   on the contents of a SYSUAF record -- without access to the associatedI   SYSUAF record, this information is not available to LOGINOUT.  (If you CI   want to see these particular logical names created, then please specifyc8   the /AUTHORIZE qualifier on the RUN/DETACHED command.)  I   If you do not specify LOGINOUT as the image, then there is no easy way nL   to get these logical names.  Also, any logical names that are used in the G   target image file specification must also be in a logical name table  I   accessable (by default) by the newly-created detached process.  Shared  I   tables include the group (if the process is in the same UIC group) and rK   the system table.  (If the target process is to be in another UIC group,  F   a suitablly privileged user or application can create the necessary B   logical name(s) directly in the other group logical name table.)  D   When in doubt, create a short DCL command file as input, and use aE   SHOW LOGICAL and similar commands to examine the context.  (And userC   physical device and directory references on the RUN/DETACH of the E   LOGINOUT image, when specifying this command file as /INPUT.)  AlsocF   remember to check both security auditing and system accounting when /   troubleshooting problems with the RUN/DETACH.S     Also see DCL1.  < ------------------------------------------------------------8 DCL12.  How to use escape and control characters in DCL?  6   To write a message and then the bell character, use:       $ bell[0,7] = 7y%     $ write sys$output "Hello''bell'"      To write blinking text, use:       $ esc[0,7] = 27-     $ text = "Blinking Text"1     $ write sys$output "''esc'[5m''text'''esc'[m"i  !   Also see sections DECW9, MISC2.   < ------------------------------------------------------------" FILE1.  How can I undelete a file?  G OpenVMS doesn't have an "undelete" function.  However, if you are quickpH to write-protect the disk (or if you can guarantee that no new files getC created or existing files extended), your data is still on the disksG and it may be possible to retrieve it.  The FLORIAN tool available fromnE the WKU Fileserver claims to be able to do this (see question SOFT1.)pF Other alternatives here include the DFU tool, available on the OpenVMS Freeware CD-ROM distribution.D  G If you are setting up a user environment for yourself or for others, ittI is quite easy to use DCL to intercept the DELETE command, using a symbol:   '   $ DEL*ETE :== @SYS$LOGIN:MYDELETE.COMl  J The DELETE symbol will cause the procedure to be invoked whenever the userF enters the DELETE command, and it can copy the file(s) to a "trashcan"K subdirectory before issuing a "real" DELETE on the files.  Other proceduresrG can retrieve the file(s) from the "trashcan" subdirectory, and can (and K should) clean out the "trashcan" as appropriate.  (Realize that this DELETE H symbol can interfere with DELETE/GLOBAL and other similar DCL commands.) 					[Stephen Hoffman]  < ------------------------------------------------------------B FILE2.  Why does SHOW QUOTA give a different answer than DIR/SIZE?  E DIR/SIZE doesn't take into account the size of file headers which are J charged to your quota.  Also, unless you use DIR/SIZE:ALL, you'll see onlyF the "used" size of the file, not the allocated size which is what getsK charged against your quota.  Also, you may have files in other directories.t 					[Steve Lionel]e  ! $ DIR/SIZ=ALL/GRAND [username...]b  6 Grand total of D1 directories, F1 files, B1/B2 blocks.  # $ DIR/SIZ=ALL/GRAND [-]username.DIRv  1 Grand total of 1 directory, 1 file, B3/B4 blocks.H   $ SHOW QUOTA3   User [username] has B5 blocks used, B6 available,o?   of B7 authorized and permitted overdraft of B8 blocks on disks  F If the user has no files in other directories and all file-headers are. only 1 block, then the following should apply:     B5=B2+B4+F1+1_  M If the diskquota is out of synch, then the system-manager can make a rebuild.  					[Arne Vajhj]  G Also be aware that the DIRECTORY/SIZE command can report larger values -D than might otherwise be expected when used to evaluate files and/or H directories that are alias links -- such as the system roots on OpenVMS G system disks -- as the command reports a total that is cumulative over  I all of the files and directories examined, without regard for which ones (M might be alias entries and which are not.  (In other words, a DIRECTORY/SIZE  M of an entire OpenVMS system disk will report a disk useage value larger than eL the (usually more accurate) value reported by the SHOW DEVICE command.  ThisP as a result of the alias entries linking each SYS$SYSDEVICE:[SYSCOMMON]SYS*.DIR K directory file and the SYS$SYSDEVICE:[000000]VMS$COMMON.DIR file together.)-  < ------------------------------------------------------------B FILE3.  How do I make sure that my data is safely written to disk?  E If your application must absolutely guarantee that data is available,nK no matter what, there's really no substitute for RMS Journalling.  However, J you can achieve a good degree of data integrity by issuing a SYS$FLUSH RMSD call at appropriate times (if you're using RMS, that is.)  If you'reM using a high-level language's I/O system, check that language's documentationrF to see if you can access the RMS control blocks for the open file.  InC C you can use fflush followed by fsync.  Note that fsync, which wasIK undocumented for VAX C but is documented for DEC C, takes a file descriptoro as an argument, not a *FILE.  < ------------------------------------------------------------C FILE4.  What are the limits on file specifications and directories?l  G A file specification has an aggregate maximum size of 255 characters atCN present.  The node and device specification may be up to 255 characters each -L file name and file types may be up to 39 characters each.  File versions areK from 1 through 32767, though 0 (latest version), -0 (oldest version) and -niK (n'th previous version) can be used in most contexts.  A file specificationGN may not have more than 8 directories and subdirectories - while it is possibleK to create subdirectories of greater depth, accessing them is problematic in)' most cases and this should be avoided. n  G Application developers should use OpenVMS-supplied routines for parsingmI file specifications - this ensures that changes in what is allowable willTG not tend to break your application.  Consider that various parts of the F file specification may contain quoted strings with embedded spaces andI other punctuation!  Some routines of interest are SYS$FILESCAN, SYS$PARSErI and LIB$TRIM_FILESPEC.  For further information, see the OpenVMS Guide to  File Applications.  F Performance of larger directory files improves (greatly) with OpenVMS I V7.2 and later -- operations on directory files of 128 blocks and larger  F were rather slower on earlier OpenVMS releases due to the smaller sizeE of the directory cache and due to the directory I/O processing logic.g  F For fastest directory deletions, consider a reverse deletion -- deleteH from the last file in the directory to the first.  This reversal speeds G the deletion operation by avoiding unnecessary directory I/O operationsoI as the files are deleted. Tools such as DFU can be used for this purpose,-? as can various available reverse-DELETE DCL command procedures.   < ------------------------------------------------------------@ FILE5.  What is the largest disk volume size OpenVMS can access?  D One Terabyte (2**31 blocks of 2**9 bytes).  Prior to the release of D V6.0, the OpenVMS file system was limited to disk volumes of 8.38 GB( (2**24 blocks, 16777216 blocks) or less.  M On some systems, there are restrictions in the console program that limit the J size of the OpenVMS system disk.  Note that data disks are not affected byH console program limits.  For example, all members of the VAXstation 3100K series are limited to a system disk to 1.073 GB or less due to the console, & though larger data disks are possible.  E Some SCSI disks with capacities larger than 8.58 gigabytes (GB) will  G require the use of an OpenVMS ECO kit (eg: ALPSCSI04_062 or later) for aF new SCSI device drivers.  Failure to use this ECO can cause "rounding E errors" on the SCSI disk device capacity -- OpenVMS will not use nor  J display the full capacity of the drive -- and  "%sysinit-e-error mounting E system device status equals 000008C4" (8C4 -> "%SYSTEM-?-FILESTRUCT, aB unsupported file structure level") errors during bootstrap.  (One E workaround for the bootstrap when the bitmap is located far into the sD disk is the use of INIT/INDEX=BEGIN.)  The problem here involves theG particular extensions and fields used for larger capacity disks within /F the SCSI specifications and within the various intepretations of same. 					[Stephen Hoffman]   For IDE disk drives:  >   o Versions of DQDRIVER *BEFORE* X-15 topped out at 8.455 GB.-     Fixed drivers (>="X-15") were shipped in:   %       OpenVMS Alpha V7.2-1, and laterf%       V7.2 UPDATE V1.0 ECO, and laterj'       V7.1-2 UPDATE V1.0 ECO, and later-'       V7.1-2 UPDATE V3.0 ECO, and later-  <   o The newer DQDRIVER driver operates to disks up to 33 GB ?     without (known) problems, and effectively works with rather;A     larger disks (up to circa 137 GB?) but is known to report an  ;     incorrect number of "cylinders" with disks above 33 GB.g  6   See ALPHA23 for additional IDE DQDRIVER information.  C Be aware that a known restriction in certain older versions of the  ? Alpha SRM Console prevents booting most IDE drives larger than  C 8.455 GB, depending on exactly where the various files are located OB on the volume.  Updated SRM consoles for systems with SRM and IDE A drive support are (will be) available.  (OpenVMS Engineering has W? successfully bootstrapped 20GB IDE disks using the appropriate _ SRM console version.)   C NOTE: All IDE-related disk sizes listed in this section are stated aB in units of "disk (base 10) gigabytes" (1GB = 10^9 bytes) and NOT D in units of "software (base 2) gigabytes" (1GB = 2^30 (1073741824.)  bytes. E:                                           [Atlant Schmidt]  D Be aware that larger disks that are using an extension of SCSI-2 -- D disks that are using a mode page field that the SCSI specifications E normally reserved for tape devices -- to permit a larger disk volume _D size will require a SCSI driver update for OpenVMS, and this change F is part of V7.1-2 and later, and also part of ALPSCSI07_062 and later.F (These larger disks disks will typically report a DRVERR, or will see I the volume size "rounded down".)  SCSI disks larger than 16777216 blocks nF cira 8.455 GB (base ten); 8GB (base two) require this ECO, or require ) the use of OpenVMS Alpha V7.1-2 or later.$     Also see VAX5.  < ------------------------------------------------------------E FILE6.  What is the maximum file size, and the RMS record size limit?   D RMS can store individual files of a size up to the maximum supportedG volume size.  Under OpenVMS V6.0 and later, the volume size and the RMSsD maximum file size limit is 2**31 * 512 bytes -- one terabyte (1 TB).  D "Use a volume set to provide a large, homogeneous public file space.G You must use a volume set to create files that are larger than a single F physical disk volume. (The file system attempts to balance the load onF the volume sets, for example, by creating new files on the volume that  is the least full at the time.)"  G "You can add volumes to an existing volume set at any time. The maximumi* number of volumes in a volume set is 255."  F The RMS formats -- sequential, relative, and indexed -- are limited byE the one terabyte maximum volume size.  RMS relative files are further D limited to a number of records that will fit in 32 bits -- 4 billionE records.   Sequential and indexed formats do not have a record limit.    Also see PROG14. 					[Stephen Hoffman]  < ------------------------------------------------------------= FILE7.  How do I write recordable CD media (CD-R) on OpenVMS?t  B Creation of CD-ROMs using recordable CD media (CD-R) under OpenVMSA typically involves one of two approaches: the use of the optionalsB CD-R (`Scribe') capabilities available for the InfoServer or otherD "offline" hardware packages, or the use of a host-based package such> as the CDWRITE13_VMS utility, an OpenVMS port of a Linux tool.  ; OpenVMS has no integrated support for recording CD-R media..  6 OpenVMS can read both ODS2 and ISO9960 format CD-ROMs.  F InfoServer hardware configurations are no longer availble from Compaq,4 but may potentially be acquired through other means.  E The CDWRITE13_VMS package is one example of a host-based package thatpC can be used to create CD-R media.  The contact for CDWRITE13_VMS issE Dr. Eberhard Heuser-Hofmann.  One website that discusses this packageh is located at:  A   http://www.geocities.com/SiliconValley/Lakes/9999/vmscdwri.htmls  4 Also see the newest linux-cdwrite package, XCDROAST.  = Additional information is available via David J. Dachtera at:k  &   http://www.djesys.com/vms/cdrom.html  	 Also see:s  6   http://www.cd-info.com/CDIC/Technology/CD-R/vms.html  B   http://www.faqs.org/faqs/cdrom/cd-recordable/part1/preamble.html      http://www.tmesis.com/CDrom/     http://www.tditx.com/~odsiso/h  ;                                           [Stephen Hoffman]   B U.S. Design offers a package that includes the tools necessary to F create a CD or DVD-R with either 9660 or ODS-2 format, for standalone @ CD-R or DVD-R drives, for recent OpenVMS versions.  Details are 
 available at:t     http://www.usdesign.com/;                                            [Harry Garonzik]x  < ------------------------------------------------------------7 FILE8.  What I/O transfer size limits exist in OpenVMS?n  G The maximum transfer size is an attribute of the particular I/O device,IE controller and driver combination; there is no inherent limit imposedtE by OpenVMS (other than the fact that, today, byte counts and LBNs are  generally limited to 32 bits).  C The maximum size of a device I/O request is limited by the value inKA UCB$L_MAXBCNT, which is set by the device driver based on variousaD factors.  (Also check the setting of the MAXBUF system parameter for6 buffered I/O transfers, and check the process quotas.)  D Currently, SCSI drivers limit I/O transfers to FE00(16) bytes, 65024K bytes (decimal).  The reasons for this transfer size limitation are largelycC historical.  Similarly, DSSI devices are limited to the same value,nD this for hardware-specific reasons.  Transfers to HSC and HSJ deviceJ controllers via the CI are limited to 1,048,576 bytes.  Client MSCP-servedA devices are limited to 65535 bytes -- to help ensure that the I/OtD fragmentation processing happens on the client and not on the server system.r  H Parts of the OpenVMS I/O subsystem are optimized for data transfers lessF than 64KB, because (obviously) most I/O operations are (substantially)G less than that.  OpenVMS can handle larger transfers, if the driver and  the device can handle it.t   Also see FILE4, FILE5$  4                                         [John Croll]  < ------------------------------------------------------------< FILE9.  Can I use ODBC to connect to OpenVMS database files?  < Yes, you can use various available third-party packages that; permit remote ODBC clients to access RMS files and various 0% commercial databases via the network.d  ? For RMS, consider acquiring one of the packages available from S> EasySoft, Attunity Connect (formerly known as ISG Navigator), 4 Oracle (DB  Integrator), SolutionsIQ, and Synergex.   < For specific commercial databases (other than RMS), contact , the database vendor directly for assistance.    < ------------------------------------------------------------: PROG1.  How do I call <routine_name> from <language_name>?  F Most OpenVMS system services and RTL routines pass string arguments byD descriptor.  Languages which support native string data types createK descriptors automatically; those which do not (eg., C) require that you setl them up explicitly.i 					[eric@tardis.HQ.ileaf.com]o  F There is a lot of information available on how to call system servicesH and Run-Time Library routines, including examples in numerous languages. The best references are:   	Your language's User Manual' 	OpenVMS Programming Environment Manualr$ 	OpenVMS Programming Concepts Manual9 	OpenVMS Programming Interfaces: Calling a System Routinec 	OpenVMS Calling Standards  G In addition, if you are a subscriber to the Compaq Software InformationfJ Network (available to those with a software support contract), the supportH database contains hundreds of worked examples of calling system servicesJ and RTL routines, including the one that seems to trip up almost everyone, SMG$CREATE_MENU. 					[Steve Lionel]e  F Arne Vajhj has put together a collection of OpenVMS example programs. It can be found at:    ftp://ftp.hhs.dk/pub/vms/b 					[Arne Vajhj]  B Additional information and examples for OpenVMS are available via:  '   http://www.openvms.compaq.com/wizard/ )   http://www.openvms.compaq.com/freeware/u   					[Stephen Hoffman]  < ------------------------------------------------------------9 PROG2.  How do I get the arguments from the command line?n  G If you're writing a program and want to accept arguments from a foreignAF command, you can use LIB$GET_FOREIGN to get the command line and parseD it yourself, or if you're programming in C, use the normal argc/argv method.e  J To write an application which uses the normal DCL verb/qualifier/parameterF syntax for invocation, see the description of the CLI$ routines in the3 OpenVMS Callable Utility Routines Reference Manual.w  I It is possible to write an application which can be used both ways; if a  L DCL verb isn't used to invoke the image, the application parses the command H line itself.  One way to do this is to call CLI$GET_VALUE for a required= parameter.  If it is not present (or you get an error), call  @ LIB$GET_FOREIGN to get the command line and do the manual parse.   See also question DCL1.l  < ------------------------------------------------------------= PROG3.  How do I get a formatted error message in a variable?t  D Use the SYS$PUTMSG system service with an action routine that storesG the message line(s) in the variable of your choice.  Be sure the actionAK routine returns a "false" (low bit clear) function value so that SYS$PUTMSGqI doesn't then try to display the message (unless you want it to.)  See thenE description of $PUTMSG in the System Services Reference Manual for an # example of using an action routine.o  < ------------------------------------------------------------D PROG4.  How do I link against SYS$SYSTEM:SYS.STB on an Alpha system?  G LINK/SYSEXE is the OpenVMS Alpha equivalent of linking against SYS.STB.   G Also see PROG11, particularly for pointers to the details on shareable d$ images and shareable image creation.  < ------------------------------------------------------------8 PROG5.  How do I do a SET DEFAULT from inside a program?  H The problem is that SYS$SETDDIR only changes the default directory - NOTI the default disk. The default disk is determined by the logical SYS$DISK.eB If you want to change the default disk within a program, then callJ LIB$SET_LOGICAL to change the logical SYS$DISK. You will need to call bothK LIB$SET_LOGICAL and SYS$SETDDIR to change both default disk and the defaultr
 directory! 					[Arne Vajhj]	y  < ------------------------------------------------------------M PROG6.  How do I create a shareable image transfer vector on an Alpha system?,  K This is something that was greatly simplified for OpenVMS Alpha.  You don'tLL need to create a separate transfer vector module; just use the SYMBOL_VECTORI statement in a linker options file.  For example, if your shareable image J has two routines named FOO and BAR, the linker options file should contain the following line:B  - 	SYMBOL_VECTOR=(FOO=PROCEDURE, BAR=PROCEDURE)   + The Linker manual has more details on this.i  < ------------------------------------------------------------H PROG7.  How do I turn my Fortran COMMON into a shareable image on Alpha?  M You need to add SYMBOL_VECTOR=(<common-name>=PSECT) to your options file.  OnrG OpenVMS VAX all OVR/REL/GBL psects were automatically exported into theoM shareable image's Global Symbol Table.  On OpenVMS Alpha you have to tell theaC linker that you want this done by means of the PSECT keyword in thes% SYMBOL_VECTOR options file statement.m  N This has several advantages over OpenVMS VAX.  First, you don't have to worry F about the address of the psect when you try to create a new, upwardly H compatible version of the shareable image. Second, you can control which= psects, if any, are made visible outside the shareable image.t  K By default, COMMON PSECTs in DEC Fortran for OpenVMS Alpha (as well as mosteL other OpenVMS Alpha compilers) are NOSHR.  On VAX, the default was SHR whichG required you to change the attribute to NOSHR if you wanted your COMMON-G to be in a shareable image but not write-shared by all processes on thes, system.  If you do want write-sharing, use:  	CDEC$ PSECT common-name=SHRM in the Fortran source code (the CDEC$ must be begin in column 1) or a linker nK options file PSECT_ATTR statement to set the COMMON PSECT attribute to SHR.g  / For further information, see the Linker manual.'  < ------------------------------------------------------------< PROG8.  How do I convert between IEEE and VAX floating data?  G In OpenVMS V6.1 and later, the routine CVT$CONVERT_FLOAT is documented  G in the LIB$ Run-Time Library Reference Manual, and can perform floatingVG point conversions between any two of the following floating datatypes: tJ VAX (F,D,G,H), little-endian IEEE (single, double, quad), big-endian IEEE 5 (single, double, quad), CRAY and IBM System\370, etc.a  F DEC Fortran (all platforms) has a feature which will perform automaticK conversion of unformatted data during input or output.  See the DEC Fortran2A documentation for information on "non-native data in I/O" and thea  CONVERT= OPEN statement keyword.  B There are floating-point conversion source code packages available for various platforms.  4 For further floating-point related information, see:  9   http://www.hhs.dk/anonymous/pub/vms/collection/ieee.zip     < ------------------------------------------------------------= PROG9.  How do I get the argument count in a Fortran routine?   E On VAX, many programmers would use a MACRO routine which accessed the E AP register of the caller to get the address of the argument list andsF hence the argument count.  This was not guaranteed to work on VAX, butH usually did.  However, it doesn't work at all on OpenVMS Alpha, as thereH is no AP register.  On Alpha systems, you must use a language's built-inD function to retrieve the argument count, if any.  In Fortran this isA IARGCOUNT, which is also available in DEC Fortran on OpenVMS VAX.e  G Note that omitting arguments to Fortran routines is non-standard and istG unsupported.  It will work in many cases - read the DEC Fortran release ! notes for additional information.   < ------------------------------------------------------------? PROG10. How do I get a unique system ID for licensing purposes?   G Many software developers desire to use a unique hardware ID to "lock" arF given copy of their product to a specific system.  Most VAX and Alpha G systems do not have a unique hardware-set "system ID" that can be used  D for this purpose.  Compaq does not use hardware IDs in its licensingG methods and many users consider a hardware-based licensing scheme to be-9 a negative attribute when considering software purchases.i  J Compaq OpenVMS uses a software-based system called the License Management H Facility (LMF).  This provides for software keys (Product Authorization G Keys or PAKS) which support capacity and user-based license checking.  ,@ Compaq offers an LMF PAK Generator to CSA members -- see ALPHA4.  J However, if a hardware-based method is required, the most common method isF based on an Ethernet adaptor hardware address.  Sample source code for" implementing this is available at:  '   http://www.openvms.compaq.com/wizard/u  < ------------------------------------------------------------? PROG11. What is an executable, shareable, system or UWSS image?a  A    Executable code in OpenVMS typically resides in an image -- an B    image is a file -- the file extension is typically .EXE -- thatA    contains this code.  Common types of images include executable @    images, shareable images, system images, and protected (UWSS)
    images.  @    Executable images are programs that can be directly executed.A       These images can grant enhanced privileges, with an INSTALLr@       of the image with /PRIVILEGE, or can grant enhanced accessA       with the specification of a subsystem identifier on the ACLe        associated with the image.  B    Shareable images contain code executed indirectly, these images>        are referenced from executable images and/or from other=        shareable images.  These images can not grant enhanced ?        privileges, even with the use of INSTALL with /PRIVILEGEh@        or a subsystem identifier.  These shareable images can beA        dynamically activated (a LINK that occurs at run-time) via-@        the LIB$FIND_IMAGE_SYMBOL run-time library (RTL) routine.=        (See `protected images' for information on `privilegedr        shareable images'.)  A    System images are intended to run directly on the VAX or Alphao>        hardware -- these are normally used for the kernel code+        that comprises an operating system. E  F    Protected images -- also refered to as User-Written System ServicesC        (UWSS), or as privileged shareable images -- are similiar invA        some ways to a standard shareable images, but these imagesfA        include a `change mode' handler, and execute in an `inner'sA        processor mode (privileged mode; executive or kernel), andSC        code executing in inner modes has implicit SETPRV privilege.eB        Must be INSTALLed with /PROTECT.  Note that inner-mode code?        has restrictions around calling library routines, arounds?        calling various system services, and around calling coder6        located in other protected or shareable images.  A    Loadable images and device drivers are images that can be useda>    to add code into the OpenVMS kernel.  Pseudo-device driversA    are a particularly convenient way to add executable code, withn>    associated driver-defined data structures, into the kernel.E    The pseudo-device driver includes the UCB and DDB data structures,s?    and a calling interface with support for both privileged and_?    unprivileged access to the driver code via sys$qio[w] calls.   >    A cookbook approach to creating OpenVMS shareable images is1    available at the (admittedly overly long) URL:   *      http://www.openvms.compaq.com/wizard/   					[Stephen Hoffman]  < ------------------------------------------------------------/ PROG12. How do I do a file copy from a program?.  M There are several options available for copying files from within a program.  D Obvious choices include using lib$spawn(), system(), sys$sndjbc() orM sys$creprc() to invoke a DCL COPY command.  Other common alternatives includeiJ using the callable convert routines and the BACKUP application programming interface (V7.1 and later).l   					[Stephen Hoffman]  < ------------------------------------------------------------ PROG13.  What is a descriptor?  K A descriptor is a data structure that describes a string or an array.  EachnI descriptor contains information that describes the type of the data beingnG referenced, the size of the data, and the address of the data.  It alsooI includes a description of the storage used for the data, typically staticv2 or dynamic.   Descriptors are passed by reference.  G The following are examples of creating and using descriptors in C, withfL the use of the angle brackets normally expected by the C include statements * deliberately altered in deference to HTML:       #include {descrip.h}     #include {lib$routines.h}-     #include {stsdef.h}-     int RetStat;     char TxtBuf[TXTSIZ]r%     struct dsc$descriptor StaticDsc = 0       { 0, DSC$K_DTYPE_T, DSC$K_CLASS_S, NULL };#     struct dsc$descriptor DynDsc = s0       { 0, DSC$K_DTYPE_T, DSC$K_CLASS_D, NULL };     int DynDscLen = 255;0     $DESCRIPTOR( ConstDsc, "This is a string" );  /     /* finish setting up a static descriptor */k)     StaticDsc.dsc$w_length      = TXTSIZ;O2     StaticDsc.dsc$a_pointer     = (void *) TxtBuf;  0     /* finish setting up a dynamic descriptor */2     RetStat = lib$sget1_dd( &DynDscLen, &DynDsc );*     if ( !$VMS_STATUS_SUCCESS( RetStat ) )       return RetStat;,  %     /* release the dynamic storage */ '     RetStat = lib$sfree1_dd( &DynDsc ); (     if (!$VMS_STATUS_SUCCESS( RetStat ))       return RetStat;t  G Static descriptors reference storage entirely under application programnJ control, and the contents of the descriptor data structure can be modifiedE as required (by the application).  OpenVMS routines do not modify thenH contents of a static descriptor, nor do they alter the address or lengthI values stored in the static descriptor.  (The term "static" refers to the H descriptor data structure, and not necessarily to the storage referenced by the descriptor.)a  G Dynamic descriptors reference storage under the control of the run-timeoH library, and the contents of a dynamic descriptor data structure -- onceE initialized -- can only be modified under control of run-time librarydF routines.  The dynamic storage referenced by the dynamic descriptor isC allocated and maintained by the run-time library routines.  VariousvH OpenVMS routines do alter the contents of the descriptor data structure,K changing the value for the amount and the address of the storage associated-H with the dynamic descriptor, as required.  Routines can obviously accessC and alter the contents of the storage referenced by the descriptor.t  I OpenVMS languages that include support for strings or arrays are expected I to use descriptors for the particular structure.  Most OpenVMS languages,tJ such as Fortran and BASIC, use descriptors entirely transparently.  Some, H like DEC C, require the programmer to explicitly create and maintain the descriptor.   K For further information on string descriptors, see the _OpenVMS Programming 8 Concepts_ manual, part of the OpenVMS documentation set.   					[Stephen Hoffman]  C Fortran defaults to passing integers by reference and characters by D descriptor.  The following sites discuss mixing Fortran and C source code in the same application:d  =   http://www.hhs.dk/anonymous/pub/vms/misc/FORTRAN_C_CALL.COMc2   ftp://ftp.hhs.dk/pub/vms/misc/FORTRAN_C_CALL.COM6                                         [Arne Vajhoej]  < ------------------------------------------------------------, PROG14.  How many bytes are in a disk block?  G A disk block is the minimum unit of disk storage allocation in OpenVMS.O  B Under OpenVMS VAX and OpenVMS Alpha, the disk volume block size is1 consistent, with each block containing 512 bytes.   D The minimum disk allocation granularity actually permissible (in theI ODS-2 and ODS-5 volume structures commonly used on OpenVMS) is determined E on a per-volume basis, and is typically based on a combination of the-G total number blocks on the disk volume and the total size of the volumedJ storage bitmap.  The allocation granularity is known as the volume clusterG factor -- the cluster factor is the number of blocks in a disk cluster,iB and it is the smallest number of blocks that can be allocated on a particular disk volume.r  B Prior to OpenVMS V7.2, the  maximum permissible size of the bitmapC requires larger cluster factors as volume sizes increase.  StartingcD with V7.2, the bitmap can be larger, and cluster factors as small as one block can be used.  B The number of bytes in a file can be determined by multiplying theD number of blocks allocated for the file times the number of bytes inA a block.  For sequential files (only), the FFB (XAB$W_FFB, in thetC File Header XAB) value can be used to find out how much of the lastt? (XAB$L_EBK) block is used.  FFB and EBK are meaningful only fore@ sequential files, and only in a limited context -- partial blockF allocations are not permitted.  For other file formats, the EOF marker is not meaningful.  C Disk allocations always occur only in units of the cluster factors,rD which can be from one block up to (potentially) clusters of eighteen7 blocks or more, depending on the volume cluster factor.o  H OpenVMS assumes that the device driver and the underlying storage deviceE will present the file system with addressable units of storage of 512oE bytes in size, or the appearance of same.  Various third-party CD-ROMsF devices, for instance, support only 2048 byte blocks, and such devices: are incompatible with the standard OpenVMS device drivers.  B To determine the number of bytes required for a file from DCL, oneB option uses the f$file_attributes item EOF, multiplied by the size@ of a block in bytes (512).  This does not account for the unusedB space in the last block of a sequential file, but it also does not8 have to differentiate sequential files from other files.   					[Stephen Hoffman]  < ------------------------------------------------------------, PROG15. How many bytes are in a memory page?  B A memory page is the minimum unit of memory allocation in OpenVMS.C With OpenVMS VAX, the memory page size matches the disk block size:y it is always 512 bytes.N  F With OpenVMS Alpha, the memory page size is variable, and it can rangeE from 8192 bytes (8 kilobytes) up to 64 kilobytes.  The current systemcF page size can be determined using the sys$getsyi or f$getsyi PAGE_SIZEE item.  Programs with hardcoded constants for the memory page size (oryA page alignment) should always assume a page size of 64 kilobytes.i  D On OpenVMS Alpha, a 512 byte area of memory -- equivilent in size to9 an OpenVMS VAX memory page -- is refered to as a pagelet.    					[Stephen Hoffman]  < ------------------------------------------------------------9 PROG16. How do I create a process under another username?e  G Many server processes can operate within the context of the target user-F using privileges, using calls such as sys$chkpro and (more commonly inH this context) sys$check_access as needed to determine if access would beC permitted for the specified user within the current security model.t  H With OpenVMS V6.2 and later, the persona system services (SYS$PERSONA_*)J can be used to assume the persona of the specified user -- these allow theF server to operate as the specified user, in a controlled fashion.  TheG persona services can be used as a "wrapper" around a sys$creprc processcF creation call, as well -- this will create a seperate process entirely under the assumed persona.  E Information on the persona system services is included in the OpenVMSeI V6.2 new features documentation, and in the OpenVMS V7.1 and later systemiI services documentation.  These system services exist and are supported ina  OpenVMS V6.2 and later releases.  I Typical mechanisms for creating a process under another username include:   =     o personna services around a sys$creprc call.  See above.a>     o via DECnet task-to-task, using explicit specification of5       username and password, or using a DECnet proxy.n<       This creates a network-mode job under the target user.A       The network-mode job might do little more than a RUN/DETACHo<       of an image passed in via task-to-task -- task-to-taskB       communications are fully available using strictly DCL-to-DCL=       processing, or using a compiled language and DCL, etc.)oC     o SUBMIT/USER, or the username argument on the sys$sndjbc call.hA       This creates a batch-mode job under the specified username. ?       The batch-mode job might do little more than a RUN/DETACHe,       of an image passed in via a parameter..     o the UIC argument on the sys$creprc call.B       This mimics the UIC of the target user, and is certainly not+       the prefered mechanism for this task.T     o Via pseudo-terminals...E  J There are likely a few other mechanisms around...  There are various toolsG available from DECUS and other sources that allow various forms of userMJ impersonation, as well.  These tools will require version-dependent kernelF code and enhanced privileges for some of (or all of) their operations.   					[Stephen Hoffman]  < ------------------------------------------------------------E PROG17.  Why do lib$spawn, lib$set_symbol fail in detached processes?e  F The processing within run-time library (RTL) calls such as lib$attach,B lib$disable_ctrl, lib$do_command, lib$enable_ctrl, lib$get_symbol,C lib$run_program, lib$set_symbol, lib$set_logical, and lib$spawn, is H dependent on and requires the presence of a command language interpreterH (CLI), such as DCL.  Without a CLI present in the current process, theseI calls will fail with a "NOCLI, no CLI present to perform function" error.   7 Detached processes typically do not have a CLI present.,  H In place of lib$spawn, sys$creprc can often be used.  The context of theF parent process (symbols and logical names) will not be propogated intoC the subprocess when sys$creprc is used, though when there is no CLIe: present in the process this (lack of) propogation is moot.  I To create a detached process with a CLI, you must specify LOGINOUT as the G target image as discussed elsewhere in the FAQ, or only use these callsmH (and any other calls requiring a CLI) from images that are running in an0 "interactive", "batch", or "other" mode process.   					[Stephen Hoffman]  I Also note that the lib$spawn and the C system call will fail in a CAPTIVEtD login environment.  The lib$spawn call can be gotten to work in this9 environment with the specification of the TRUSTED flag.  g  < ------------------------------------------------------------J PROG18.  Where can I obtain Bliss, and the libraries and supporting files?  < The Bliss language compilers and documentation are available& on the OpenVMS Freeware distributions.  A Bliss language source code that contains the following statement:e  $   LIBRARY 'SYS$LIBRARY:STARLET.L32';  ? or similar requires the presence of the Bliss libraries.  These B libraries are created on the target system using the Bliss require8 files, and are built using the following Bliss commands:  8   STARLET.L32 contains the public interfaces to OpenVMS:  5     $ BLISS /LIBRARY=SYS$COMMON:[SYSLIB]STARLET.L32 --         SYS$LIBRARY:STARLET.REQ   E   LIB.L32 contains both the public and private interfaces to OpenVMS:m  1     $ BLISS /LIBRARY=SYS$COMMON:[SYSLIB]LIB.L32 -P3         SYS$LIBRARY:LIB.REQ+SYS$LIBRARY:STARLET.REQu  4   The equivilent files for Bliss64 are created with:  5     $ BLISS/A64/LIBRARY==SYS$COMMON:[SYSLIB]LIB.L64 - 3         SYS$LIBRARY:LIB.R64+STARLET.REQ+STARLET.R64 9     $ BLISS/A64/LIBRARY==SYS$COMMON:[SYSLIB]STARLET.L64 -u         SYS$LIBRARY:STARLET.R64a  D Some Bliss code may also require the OpenVMS VAX architecture flags.B The following is the equivilent of the Alpha ARCH_DEFS.BLI module:     !o9   ! This is the OpenVMS VAX version of ARCH_DEFS.BLI, andl<   ! contains the architectural definitions for conditionally;   ! compiling OpenVMS Bliss sources for use on VAX systems.-   !-   MACRO VAXPAGE = 1%;    MACRO BIGPAGE = 0%;u  =   MACRO VAX =                     ! = 1 if compiled BLISS/VAXeA           %BLISS(BLISS32V)%;      ! = 0 if not compiled BLISS/VAXh  <   MACRO EVAX =                    ! = 1 if compiled BLISS/E*   !t@   ! A more appropriate definition can only be used with versions=   ! of the Bliss compilers that understand the 32E/64E flags. G   !       %BLISS(BLISS32E) OR %BLISS(BLISS64E)%; ! = 0 if compiled /VAX 8           NOT %BLISS(BLISS32V)%;  ! = 0 if compiled /VAX     MACRO ADDRESSBITS = E           %BPADDR%;               ! = 32 or 64 based on compiler usedT       					[Stephen Hoffman]  < ------------------------------------------------------------0 PROG19. How can I open a file for shared access?  9   When creating a file, it is often useful to allow other,8   applications and utilities -- such as TYPE -- to share;   read access to the file.  This permits you to examine thep'   contents of a log file, for instance.a  8   A C source example that demonstrates how to do this is7   available in topic 2867 in the OpenVMS Ask The Wizard-   area:1  )     http://www.openvms.compaq.com/wizard/   ;   Depending on the environment, you may need to use C calls ;   such as fsync and fflush, and -- in specific cases -- thei   setvbuf(_IONBF) call.    					[Stephen Hoffman]  < ------------------------------------------------------------> PROG20. How can I have common sources for messages, constants?  B   Use the GNM tools on the OpenVMS Freeware to have common sourcesB   for MSG (message) files and SDML (Document) documentation files.A   Use the DOCUMENT command to convert the SDML documentation intot?   the necessary formats (Text, Postscript, HTML, etc).  Use theoC   MESSAGE/SDL tool (latent in OpenVMS) to create an SDL file based nD   on the messages.  Then use the SDL tool (available on the OpenVMS G   Freeware) to convert the SDL file into language-specific definitions.hE   (There is also a converter around to convert SDL into SDML, if you hF   want to get pictures of the data structures for your documentation.)  < ------------------------------------------------------------C PROG21. How do I activate the OpenVMS Debugger from an application?    #include <lib$routines.h>r #include <ssdef.h> #include <string.h>e   main()     { #     char ascic_debug_commands[128];d)     char *dbgcmd = "*show calls;go;exit";r  +     strcpy( ascic_debug_commands, dbgcmd );e:     ascic_debug_commands[0] = (char) strlen( dbgcmd ) - 1;  1     lib$signal(SS$_DEBUG,1,ascic_debug_commands);e  
     return 1;W     }    [End of Part 3/5]l  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  # Date: Tue, 10 Apr 2001 18:12:05 GMT 2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman); Subject: OpenVMS Frequently Asked Questions (FAQ), Part 4/5t2 Message-ID: <V1IA6.751$fB6.19160@news.cpqcorp.net>   Archive-name: dec-faq/vms/part4s Posting-Frequency: quarterly Last-modified: 10 Jul 2001 Version: VMS-FAQ-4.TXT(6)     9 This is the OpenVMS Frequently Asked Questions Part 4/5. d@ Please see Part 1/5 for administrivia, indexing, archiving, etc.    < ------------------------------------------------------------F DECW1.  How do I let someone else display something on my workstation?  M On a workstation, you go into "Customize" menu of the session manager utilitya@ and select "Security".  When the pop-up box appears, you can putK node/user/tranport to allow who can launch an application to the display oni that workstation.A<                                              [Mike Raspuzzi]  M > Yah, but this doesn't seem to work with non-VMS systems.  What do I put in qI > for the transport?  I tried "TCPIP" just for kicks, but it didn't work.-  &         You need a checklist of sorts:  D       1) Make sure  that  you've  specified  the X-windows "display"D          correctly  on  the remote side.  For DECNET it's  somethingD          like NODE::0.0, for TCP/IP it's Node.Domain:0.0, etc.  On aA          unix system, define the DISPLAY environment variable so:a               csh:* 	      # setenv DISPLAY myvax.domain:0.0               sh and ksh:)9               $ DISPLAY=myvax.domain:0.0 ; export DISPLAY-  D       2) If you've verified 1) and things still aren't working, makeD          sure the Security settings on  the  VMS side will allow theD          connection:  Pull  down the "Options" menu in  the  SessionD          Manager, select "Security..."  near  the  bottom.   If  youD          don't  find  your  host  (and  username) listed on the leftD          under "Authorized Users", go to the  right side of the menuD          and   fill   in  the  three  fields,  "Node",   "Username",D          "Transport".  Then click on the Add botton, then the  ApplyD          and  OK  buttons  to  add  the  new  host  to  the security          database.  @           a) There are  various  transports: LOCAL, DECNET, LAT,@              TCPIP,  etc.   Select  the one appropriate  to  the<              client machine's connection to the VMS machine.  9 	  b) If the connection is DECNET, do *NOT* add :: to the$              node name!n  @           c) If the connection is TCPIP, "Username" _must_ be an@              asterisk (*) because the  TCP/IP protocol used does-              not provide the remote username.s  @           d) If the connection is TCPIP, it's best to use a full@              domain name, e.g.,  Node.Subd.Domain.  However, you@              _may_  have  to use the IP address  itself,  rather@              than  the  domain  name  (EWS  requires  this).   I@              generally  add two entries for each TPCIP host, the@              first using the  domain  name,  the  second  the IP              address.o  @           e) There are a  various  3rd  party vendors who supply@              TCP/IP  packages for VMS, including but not limited@              to  TGV  (Multinet)  and  Wollongong  (Pathway  ?).@              Multinet  (and  DEC's  own  UCX) call the transport@              "TCPIP", Wollongong, at least in some incarnations,<              uses "WINTCP".  You need to use the appropriate@              vendor's package transport name  in the "Transport"              field.   D       3) If things _still_  aren't  working, make sure the transportD          you  want  has  been activated for DECwindows.  This  is  aD          system manager job, but you can do the ground work yourself8          before bothering the sysmgr.  Do the following:  4 	    $ DIR SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM  &          If that file exists, then do:  9 	    $ SEARCH SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM -s(             $_    DECW$SERVER_TRANSPORTS  '          You sould find something like:n  9 	    $ decw$server_transports == "DECNET,LOCAL,LAT,TCPIP"t  D          If the transport you want,  e.g., TCPIP, isn't listed, haveD          your  system  manager  make  the  appropriate  changes  andD          restart DECwindows.  If the file doesn't exist, the  sysmgrD          will  have  to  create  it  by  copying  the  correspondingD          .TEMPLATE file  to  .COM  and  uncommenting  the  line that(          defines decw$server_transports.  @           a) If you're wanting  to  use  TCP/IP to connect, make@              sure  TCP/IP is available on the VMS host.   TCP/IP@              is _not_ native to VMS.  You  need  to  be  runningB              either Compaq's TCP/IP or a 3rd party vendor's TCP/IP@              product.   If  you're  not,  none of the above will              help.% 				    [Fairfield@Slac.Stanford.Edu]   K There is a log file created in SYS$MANAGER which tells you which transports-L are loaded, and also tell you what connect attempts were rejected, including: showing what the presented credentials were.  This file isN SYS$MANAGER:DECW$SERVER_0_ERROR.LOG, although the 0 could be another number ifK you have multiple servers on the workstation.  I have found this file to beaI very useful for tracking down what needs to be put in the Session Managers Security entries.u 				    [rabinowitz@bear.com]   < ------------------------------------------------------------9 DECW2.  How do I create a display on another workstation?l  @ $ SET DISPLAY /CREATE /TRANSPORT=net_transport /NODE=remote_node  ) for LAT the command might look like this:l  6 $ SET DISPLAY /CREATE /TRANSPORT=LAT /NODE=REMOTE_NODE   for DECnet:m  2 $ SET DISPLAY /CREATE /TRANSPORT=DECNET /NODE=NODE  
 for TCP/IP  9 $ SET DISPLAY /CREATE /TRANSPORT=TCPIP /NODE=128.12.4.122i  D Note that LAT is typically used for X terminals but can be used fromI OpenVMS to OpenVMS systems on OpenVMS Alpha V6.1 (if you have setup the X K server to allow the LAT transport - check the docs).  LAT will be supportedrD on OpenVMS VAX as a transport for DECwindows in a future OpenVMS VAX release. 					[Mike Raspuzzi]  K There is a log file created in SYS$MANAGER which tells you which transportsvL are loaded, and also tell you what connect attempts were rejected, including: showing what the presented credentials were.  This file isN SYS$MANAGER:DECW$SERVER_0_ERROR.LOG, although the 0 could be another number ifK you have multiple servers on the workstation.  I have found this file to beaI very useful for tracking down what needs to be put in the Session Managerl Security entries.l=                                         [rabinowitz@bear.com]m  < ------------------------------------------------------------F DECW3.  How can I get the information from SHOW DISPLAY into a symbol?  H Use the undocumented SHOW DISPLAY/SYMBOL, and then reference the symbolsC DECW$DISPLAY_NODE,  DECW$DISPLAY_SCREEN, DECW$DISPLAY_SERVER and/orb DECW$DISPLAY_TRANSPORT.c" 					[Fairfield@Slac.Stanford.Edu]  E An example of calling the underlying (and also undocumented) sys$qio o? programming interface for the WSDRIVER (WSAn:) is available at:F  I   http://www.openvms.compaq.com/freeware/srh_examples/DECUS_UNDOC_CLINIC/o  < ------------------------------------------------------------0 DECW4.  How do I get a log of a DECterm session?  L If you are working from a Decterm, you can use the AutoPrint feature. ChooseD the "Printer..." menu item from the "Options" menu, set the printingH destination to the name of the file you want, and set "Auto Print Mode". You are now free to continue.e  M It should be noted that ALL the characters and escape sequences are captured,eO but if you display the log file on a DECterm you will get EXACTLY what you had.8 					[Yaacov Fenster]l  < ------------------------------------------------------------E DECW5.  Problem - the DELETE key deletes forward instead of backward!n  N This has to do with Motif's virtual bindings.  When a Motif application startsD up, it looks at the vendor string returned in the display connectionL information and attempts to match the string to a table of virtual bindings.  N You can override the default bindings in your decw$xdefaults.dat file. Here is9 the entry you would make to get the default VMS bindings.t      *defaultVirtualBindings:\c  osfCancel	:		<Key>F11	\n\  osfLeft	:		<Key>Left	\n\-  osfUp		:		<Key>Up		\n\   osfRight	:		<Key>Right	\n\(  osfDown	:		<Key>Down	\n\e   osfEndLine	:Alt		<Key>Right	\n\!  osfBeginLine	:Alt		<Key>Left	\n\t  osfPageUp	:		<Key>Prior	\n\  osfPageDown	:		<Key>Next	\n\t"  osfDelete	:Shift		<Key>Delete	\n\  osfUndo	:Alt		<Key>Delete	\n\   osfBackSpace	:		<Key>Delete	\n\   osfAddMode	:Shift		<Key>F8		\n\  osfHelp	:		<Key>Help	\n\   osfMenu	:		<Key>F4		\n\  osfMenuBar	:		<Key>F10	\n\   osfSelect	:		<Key>Select	\n\s!  osfActivate	:		<Key>KP_Enter	\n\r!  osfCopy	:Shift		<Key>DRemove	\n\-  osfCut		:		<Key>DRemove	\n\  osfPaste	:		<Key>Insert  	 To merge:s    	$ xrdb :== $decw$utils:xrdb.exe( 	$ xrdb -nocpp -merge decw$xdefaults.dat 					[Fred Kleinsorge]  < ------------------------------------------------------------- DECW6.  Why is DECwindows Motif not starting?a  F First check to see if there is a graphics device, usually a G* device.E (eg: On a DEC 2000 model 300, use the command SHOW DEVICE GQ)  If youa do not find a graphics device:  D a) OpenVMS has failed to find the appropriate IRQ information for anJ    EISA graphics card (on the DEC 2000 series) such as the Compaq QVision,J    and did not autoconfigure it.  Run the correct ECU (for Tru64 UNIX and F    OpenVMS) and reboot.  This is necessary only on EISA-based systems.  I b) You have an EISA-based system (such as the DEC 2000 model 300) and do iI    not have a Compaq QVision video card.  This EISA graphics card should DF    have Compaq printed on it, and identifies itself as a CPQ3011 or a F    CPQ3111.  If it is not one of these two EISA devices, then OpenVMS D    does not support it.  (There are no other supported EISA graphicsI    controllers, and EISA graphics are normally used with DECwindows only h#    on the DEC 2000 series systems.)   C c) You have a PCI-based system and do not have a supported graphicsc>    controller -- examples of supported controllers include the        PowerStorm 3D30      PowerStorm 4D20      PowerStorm 300s      PowerStorm 350S      ELSA GLoria Synergy  D    See MGMT24 for information on some of these graphics controllers.  C d) You have booted the system minimally, or have otherwise disabledf(    the device autoconfiguration process.  ) If there is a G* graphics device present:-  I a) There may have been a severe error in the DECwindows startup. Type theaI    contents of SYS$MANAGER:DECW$SERVER_0_ERROR.LOG for any information onc    errors starting the server.  I b) The system parameter WINDOW_SYSTEM is not set to 1.  This is a common ,D    way for system managers to disable the DECwindows server startup.  E    If you really do not want a workstation system to bootstrap as andDI    to represent itself as a workstation to DECwindows, add the following i     definition to SYLOGICALS.COM:  6      $ DEFINE/SYSTEM/EXEC DECW$IGNORE_WORKSTATION TRUE  E c) You may not have a valid Motif license.    To check for the Motif e    license, type the commands:  "      $ LICENSE LIST DW-MOTIF/FULL %      $ LICENSE LIST NET-APP-SUP*/FULLo  F    and examine the information displayed.  Make sure that one of these)    licenses is present, valid and active..  B d) Check that the DECW$PRIVATE_SERVER_SETUP.COM is correct for the-    graphics controller in use.  For instance:n  =      From the 9FX Vision 330 Owners Guide, EK-V330G-OG pg 2-9g  E      Place the following in DECW$PRIVATE_SERVER_SETUP.COM (copy from tG      .TEMPLATE, if needed).  Have the file in SYS$SPECIFIC:[SYSMGR] or a*      in SYS$COMMON:[SYSMGR] as apropriate.  )        $ DECW$XSIZE_IN_PIXELS == <xvalue>c)        $ DECW$YSIZE_IN_PIXELS == <yvalue>i<        $ DEFINE/SYSTEM DECW$SERVER_REFRESH_RATE <rate in Hz>   Also see DECW14- 					[Kleinsorge, Hoffman]  < ------------------------------------------------------------ DECW7 relocate to SUPP7a  < ------------------------------------------------------------ DECW8 relocated to SUPP8  < ------------------------------------------------------------3 DECW9.  How do I set the title on a DECterm window?m  0 If you are creating a new DECterm window, check ) HELP CREATE /TERMINAL /WINDOW_ATTRIBUTES.   H If you want to change the title of an existing window, use the followingJ control sequences, where <esc> is the ANSI escape code, value decimal 27, - and <text label> is what you want to display:.  : To set the DECterm title, send <esc>]21;<text label><esc>\: To set the icon label, send    <esc>]2L;<text label><esc>\  ? To set both the DECterm title and icon to the full device name::   $  esc[0,7] = 27E $  fulldevnam = F$Edit(F$GetDVI("TT","FULLDEVNAM"),"UPCASE,COLLAPSE") 8 $  write sys$output esc+ "]21;" + fulldevnam + esc + "\"8 $  write sys$output esc+ "]2L;" + fulldevnam + esc + "\"  F You can also change the title and the icon using the Options-Window... menu..   Also see MISC2, DCL12.  < ------------------------------------------------------------B DECW10. How do I customize DECwindows, including the login screen?  L To customize various DECwindows Motif characteristics including the defaultsL used by the SET DISPLAY command, the DECwindows login screen background logoG used (the default is the DIGITAL or Compaq logo), various keymaps, the uM FileView defaults, session manager defaults, the DECwindows login processing,BL DECwindows log file processing, and various other DECwindows attributes, see the example file:   .   SYS$STARTUP:DECW$PRIVATE_APPS_SETUP.TEMPLATE  C This example template file is typically copied over to the filenametM SYS$COMMON:[SYS$STARTUP]DECW$PRIVATE_APPS_SETUP.COM and then modified to meet4 site-specific requirements.   M Additionally, various X tools such as xsetroot, bitmap and xrdb -- some these G can be useful in customizing the appearance of an application or of the A DECwindows Motif display -- are provided in the DECW$UTILS: area.-  M When using DECwindows V1.2-4 and later on OpenVMS Alpha, the default desktop hG is the Common Desktop Environment (CDE).  You can select your prefered dI desktop (CDE or DECwindows Motif) when logging in, or you can change the r= default to the DECwindows Motif desktop using the DCL symbol eK decw$start_new_desktop in the DECwindows private application setup command nI procedure.  See SYS$STARTUP:DECW$PRIVATE_APPS_SETUP.TEMPLATE for further v7 details, and how to create DECW$PRIVATE_APPS_SETUP.COM.   G Note that with DECwindows CDE, the root window is no longer visible by cH default.  The root window is hidden behind the "backdrop" window of the E current CDE workspace.  To make the root window visible, use the CDE aE style manager selection "backdrop none", and use information such as  / that in the OpenVMS FAQ to set the root window.   E To add a new backdrop to the DECwindows CDE environment, the backdrophJ must first be in or be converted into X11 pixmap format.  (This conversionF is often possible using tools such as xv.)  Then (if necessary) createH the default backdrop directory SYS$COMMON:[CDE$DEFAULTS.USER.BACKDROPS].I Place the X11 pixmap file containing the desired image into the backdropsfC directory, ensure that it has a filename extension of .PM.  (The xvrE default filename extension for the X11 pixmap file is .XPM, while CDEhF expects only to see files with .PM.)  Now invoke the CDE style managerF and select a new backdrop.  You will find your image will be placed at+ the end of the list of backdrops available.<  $ 					[Stephen Hoffman]  < ------------------------------------------------------------4 DECW11. Why doesn't XtAppAddInput() work on OpenVMS?  J XtAppAddInput() does work on OpenVMS.  The MIT definition of the X Windows: call XtAppAddInput() includes platform-specific arguments.  J On platforms where C is the typically the primary programming language forE the platform, the file descriptor mask is one of the arguments to the- XtAppAddInput() call.f  I On OpenVMS, the platform-specific arguments to this call include an event-I flag and an IOSB, as these are the traditional OpenVMS constructs used tooI synchronize the completion of asynchronous operations.  While it would beeD easier to port non-OpenVMS C code that calls XtAppAddInput() over toH OpenVMS if the arguments included the C file descriptor, this would makeK the call unusable from other OpenVMS languages, and would make it extremelypA difficult to use OpenVMS features such as ASTs and sys$qio calls.o  K One restriction on the event flag: the event flag chosen must be from event-I flag cluster zero.  When using the traditional lib$get_ef and lib$free_efeG calls to allocate and deallocate event flags, you must first explicitlyuH call lib$free_ef to free up some event flags in event flag cluster zero.K Please see the event flag documentation for specific details on these callscJ and for specific event flags that can be freed in event flag cluster zero.  F Here is some example code that covers calling this routine on OpenVMS:       m->InputID = XtAppAddInput(n         m->AppCtx,         m->InputEF,          m->InputIosb,d         the_callback, 1 );     if ( !((int) m->InputID ))	         {          XtAppErrorMsg(             m->AppCtx,             "invalidDevice",             "XtAppAddInput",             "XtToolkitError", "             "Can't Access Device",             (String *) NULL,              (Cardinal *) NULL );         ...a 					[Stephen Hoffman]  < ------------------------------------------------------------B DECW12. Why do the keyboard arrow keys move the DECwindows cursor?  @ Congratulations, you have just stumbled into "dead rodent" mode.< This DECwindows environment -- where the keyboard arrow keys@ move the mouse cursor and where the [SELECT], [PREV], and [NEXT]B keys emulate the three mouse buttons -- allows rudimentary system 2 operations when the mouse is among the casualties.  A To enter or exit the "dead rodent" mode. press: [CTRL][SHIFT][F3]e  < ------------------------------------------------------------2 DECW13. Why does half my DECwindows display blank?  > This is likely a result of receiving an OPCOM or other console< message on a system that shares the system console with the ( DECwindows graphics workstation display.  ? You can toggle off the console display window using [CTRL/F2], P8 and you can enable a serial console per ALPHA7 or VAX10.  > Also see the console message window application available with@ recent DECwindows versions -- recent DECwindows versions (V1.2-3> and later) will enable this window by default.  For details on< this console message window, see the DECW$CONSOLE_SELECTION 7 option in SYS$STARTUP:DECW$PRIVATE_APPS_SETUP.TEMPLATE.r  > On older releases, you can disable output using the following:  *   SET TERMINAL/PERMANENT/NOBROADCAST OPA0:   DEFINE/USER SYS$COMMAND OPA0:    REPLY/DISABLEa  * Also see VAX9 and MGMT22, as well as DCL4.  < ------------------------------------------------------------B DECW14. %DECW-W-NODEVICE, No graphics device found on this system?   To resolve the following error:   :  %DECW-W-NODEVICE, No graphics device found on this systemA    -DECW-I-NODECW, DECwindows graphics drivers will not be loaded     > 1) Ensure that the SYSGEN parameter WINDOW_SYSTEM is set to 1:  #     $ MCR SYSGEN SHOW WINDOW_SYSTEM(  8    If it is not set to a value of 1, issue the commands:       $ MCR SYSGEN     SYSGEN> USE CURRENTl     SYSGEN> SET WINDOW_SYSTEM 1i     SYSGEN> WRITE ACTIVE     SYSGEN> WRITE CURRENTe     SYSGEN> EXIT     $ REBOOT  E 2) Check the SYSMAN IO PREFIX LIST to ensure that the DECW$ prefix is I    included in the existing list.  If it is not, you will need to add it:        $ MCR SYSMAN     SYSMAN> IO SHOW PREFIXK     SYSMAN> IO SET PREFIX=(DECW$,*)   * = list returned by the show commandr     SYSMAN> IO AUTO/LOGh     SYSMAN> EXITH 3) Ensure that the image SYS$SHARE:DECW$ICBM.EXE is installed in memory.+    If it is not installed, then install it:   +     $ INSTALL LIST/FULL SYS$SHARE:DECW$ICBME  )     $ INSTALL REPLACE SYS$SHARE:DECW$ICBMN  #     $ EDIT SYS$MANAGER:SYCONFIG.COMh  0       $! The following line was added to install-       $! support for the Mach64 Graphics Cardr       $!+       $ INSTALL REPLACE SYS$SHARE:DECW$ICBMy
       $ ^Z       $ SHUTDOWN    REBOOT the system.   E If the system still complains that NO GRAPHICS DEVICES COULD BE FOUNDr then:     4)   o Boot the system as normal      o Login as "system"      o Create the file: =          $ SYS$COMMON:[SYSMGR]DECW$USER_AUTOCONFIG.DAT (W:RE)d7      o Add the following string on the very first line:            CLEAR_PFLAG = ISA_4BYTE      o Save the file      o Set the file protections       o Reboot the system  
      EXAMPLE:M  9      $ create SYS$COMMON:[SYSMGR]DECW$USER_AUTOCONFIG.DATT        CLEAR_PFLAG = ISA_4BYTE	        ^Z   M      $ SET FILE/PROTECTION=(W:RE) SYS$COMMON:[SYSMGR]DECW$USER_AUTOCONFIG.DAT	
      $ REBOOTd   Also see DECW6 					[Kleinsorge, Hoffman]  < ------------------------------------------------------------0 DECW15. How can I reset the warning bell volume?  A   With DECwindows CDE drivers and ECOs starting with ECOs for thesG   DECwindows keyboard driver SYS$IKBDRIVER.EXE in OpenVMS Alpha V7.1-2 oI   and V7.2-1 and with the SYS$IKBDRIVER.EXE included in OpenVMS V7.2-1H1  G   and later, the DECwindows CDE controls will now correctly manage the h&   setting of the warning bell volume.   G   Unfortunately, the equivalent controls in the older DECwindows Motif -D   interface are not compatible and can no longer manage the warning    bell volume.  C   If you need to manage the volume with DECwindows Motif, consider     using the following approach:l  #     $ @decw$utils:decw$define_utilsT     $ xset b 1 100 100  A   The numerics are the volume, pitch, and duration, respectively.o  G   Why?   When OpenVMS first started supporting the PC-style keyboards, oI   the X Windows Server and the keyboard driver interface did not support  A   the pitch and duration, and neither did DECwindows Motif.  The  G   DECwindows keyboard driver was accordingly changed to use the volume eE   from the keyclick setting (keyclick is not available in a PC-style XJ   keyboard) and the bell volume setting to control the pitch and duration.  E   DECwindows CDE does provide sliders for setting pitch and duration,cG   so the keyboard driver and X Windows Server were modified to provide eI   all of the information, and now the DECwindows CDE sliders work.  This hF   change is unfortunately incompatible with the old scheme used on theF   pre-CDE desktops, and the volume controls are now incompatible with 7   the current keyboard drivers.  Hence the use of xset.s  < ------------------------------------------------------------4 DECW16. How can I alter the DECwindows CDE backdrop?  C To select a separate backdrop to be displayed on each screen using n DECwindows CDE:s  # 1. Click on the Appliction Manager. .    This is the drawer icon on the CDE toolbar. 2. Click on Desktop ToolsC= 3. Click on Set Default Screen and select the required screeni 4. Click on the Style Manager.B    This is the one containing the mouse and ttt on the CDE toolbar 5. Now change the background.R  >                                              [Geoff Kingsmill]  < ------------------------------------------------------------8 DECW17. How can I enable the DECwindows TCP/IP Transport  E   To configure the TCP/IP transport for DECwindows, first ensure thatyH   a TCP/IP package is installed and configured.  Then set the DCL symbolE   DECW$SERVER_TRANSPORTS in SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COMlE   to the appropriate local value, based on the comments in that file.   I   If you do not have a copy of SYS$STARTUP:DECW$PRIVATE_SERVER_SETUP.COM,dE   the use the following COPY command to create this file based on theh   provided template file:F  9     COPY SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE --9          SYS$COMMON:[SYSMGR]DECW$PRIVATE_SERVER_SETUP.COMd    < ------------------------------------------------------------ MISC1 relocated to WIRES1t  < ------------------------------------------------------------G MISC2.    Where can I find information on escape and control sequences?   G Information on escape and control sequences can be found in the OpenVMSxC I/O User's Reference Manual, in the section on the terminal driver.lB This section includes details on the general format and content of these sequences.  C Specific details on the escape and control sequences supported by a	A particular serial device are typically found in the documentation A provided with the specific device.  Information on the sequences oF supported by DECwindows DECterm terminal emulator are included in the  DECwindows documentation.o  G Examples of common escape and control sequences -- those typically used:H by the OpenVMS screen management package -- can be found in the OpenVMS $ system file SYS$SYSTEM:SMGTERMS.TXT.  H The following refers to the function keys on the VTxxx series terminals,I and compatibles.  In the following, {CSI} is decimal code 155 and can be dH replaced by the sequence "{ESC}[" (without the quotes) particularly for E seven-bit operations, SS3 is decimal code 143 and can be replaced by -C "{ESC}O" particularly for seven-bit operations.  Older VT1xx seriessF terminals and any other terminals operating with seven-bit characters ? should not be sent eight-bit operators such as {CSI} and {SS3}.n  + PF1={SS3}P PF2={SS3}Q PF3={SS3}R PF4={SS3}SoA KP0={SS3}p KP1={SS3}q KP2={SS3}r KP3={SS3}s KP4={SS3}t KP5={SS3}u I KP6={SS3}v KP7={SS3}w KP8={SS3}x KP9={SS3}y KPCOMMA={SS3}l KPMINUS={SS3}mnI KPPERIOD={SS3}n ENTER={SS3}M DNARROW={CSI}B UPARROW={CSI}A LFARROW={CSI}DtH RTARROW={CSI}C FIND={CSI}1~ INSERT={CSI}2~ REMOVE={CSI}3~ SELECT={CSI}4~I PREV={CSI}5~ NEXT={CSI}6~ F6={CSI}17~ F7={CSI}18~ F8={CSI}19~ F9={CSI}20~Q@ F10={CSI}21~ F11={CSI}23~ F12={CSI}24~ F13={CSI}25~ F14={CSI}26~M HELP={CSI}28~ DO={CSI}29~ F17={CSI}31~ F18={CSI}32~ F19={CSI}33~ F20={CSI}34~i  = An example of working with escape sequences (in DCL) follows:u   $ esc5m = "*[5m" $ esc5m[0,8] = 27d $ esc0m = "*[0m" $ esc0m[0,8] = 27I2 $ write sys$output esc5m + "blinking text" + esc0m  H Documentation on an ANSI terminal relatively similar to the VT525 series is available at:  6   ftp://ftp.boundless.com/pub/text/adds/docs/260_prog/6   ftp://ftp.boundless.com/pub/text/adds/docs/260_user/  < Also see the various documentation and manuals available at:     http://www.vt100.net/e  @ Information on the ReGIS graphics character set is available at:  <   http://www.cs.utk.edu/~shuford/terminal/dec_regis_news.txt   Also:e  -   http://www.boundless.com/Text_Terminals/VT/    Also see DECW9, DCL12.  < ------------------------------------------------------------ MISC3 relocated to SUPP4  < ------------------------------------------------------------ MISC4 relocated to WIRES2e  < ------------------------------------------------------------ MISC5 relocated to ALPHA5w  < ------------------------------------------------------------E MISC6.    What does "failure on back translate address request" mean?n   The error message:  <   BCKTRNSFAIL, failure on the back translate address request  I indicates that the destination node is running DECnet-Plus, and that its OE naming service (DECnet-Plus DECdns, LOCAL node database, etc) cannot eE locate a name to associate with the source node's address.  In other FG words, the destination node cannot determine the node name for the noder. that is the source of the incoming connection.  G Use the DECNET_REGISTER mechanism (on the destination node) to registerED or modify the name(s) and the address(es) of the source node.  Check* the namespace on the source node, as well.  B Typically, the nodes involved are using a LOCAL namespace, and theA node name and address settings are not coherent across all nodes.)C Also check to make sure that the node is entered into its own LOCALYC namespace.  This can be a problem elsewhere, however.  Very rarely, D a cache corruption has been known to cause this error.  To flush the cache, use the command:   1 NCL> flush session control naming cache entry "*"]  C Also check to see that you are using the latest ECO for DECnet-Plus   for the version you are running.  - DECnet-Plus can use the following namespaces: 2   o DECdns: DECnet-Plus distributed name services.;   o LocalFile: a local file containing names and addresses.e/   o DNS/Bind: the IP distributed name services.n   o The UCX local host file.   					[Stephen Hoffman]  < ------------------------------------------------------------8 MISC7.    How to determine the network hardware address?  A   Most Alpha and VAX systems have a console command that displays F   the network hardware address.  Many systems will also have a stickerD   identifying the address, either on the enclosure or on the network   controller itself.  C   The system console power-up messages on a number of VAX and Alpha7B   systems will display the hardware address, particularly on those>   systems with an integrated Ethernet network adapter present.  E   If you cannot locate a sticker on the system, if the system powerupcD   message is unavailable or does not display the address, and if theB   system is at the console prompt, start with the console command:  
   >>> HELP  E   A console command similar to one of the following is typically used "   to display the hardware address:     >>> SHOW DEVICEl   >>> SHOW ETHER   >>> SHOW CONFIGI  D   On the oldest VAX Q-bus systems, the following console command canD   be used to read the address directly off the (DELQA, DESQA, or the=   not-supported-in-V5.5-and-later DEQNA) Ethernet controller:s     >>> E/P/W/N:5 20001920  G   Look at the low byte of the six words displayed by the above command. E   (The oldest VAX Q-bus systems -- such as the KA630 processor modulelD   used on the MicroVAX II and VAXstation II series -- lack a consoleD   HELP command, and these systems typically have the primary networkF   controller installed such that the hardware address value is located+   at the system physical address 20001920.)   F   If the system is a VAX system, and another VAX system on the networkC   is configured to answer Maintenance and Operations Protocol (MOP)CF   bootstrap requests (via DECnet Phase IV, DECnet-Plus, or LANCP), the1   MOM$SYSTEM:READ_ADDR.EXE tool can be requested:y     >>> B/R5:100 ddcu    Bootfile: READ_ADDRf  I   Where ddcu is the name of the Ethernet controller in the above command.eJ   The primarly local DELQA, DESQA, and DEQNA Q-bus controllers are usuallyK   named XQA0.  An attempt to MOP download the READ_ADDR program will ensue,_I   and (if the download is successful) READ_ADDR will display the hardwareS
   address.  G   If the system is running, you can use DECnet or TCP/IP to display the 6   hardware address with one of the following commands.  B     $ MCR NCP SHOW KNOWN LINE CHARACTERISTICS    ! DECnet Phase IV  >     $ MCR NCL SHOW CSMA-CD STATION * ALL STATUS  ! DECnet-Plus  @     $ UCX SHOW INTERFACE/FULL    ! TCP/IP versions prior to V5.0  A     $ TCPIP SHOW INTERFACE/FULL  ! TCP/IP versions V5.0 and latere  G   A program can be created to display the hardware address, reading the F   necessary information from the network device drivers.  An example CF   program for reading the Ethernet hardware address (via sys$qio callsE   to the network device driver(s)) is available at the following URL:t  =     http://www.openvms.compaq.com/wizard/swdev/ethernVMS.htmli  E   To use the DECnet Phase IV configurator tool to watch for MOP SYSIDi%   activity on the local area network:   B   $ NCP SET MODULE CONFIGURATOR KNOWN CIRCUIT SURVEILLANCE ENABLED  E   Let the DECnet configurator run for at least 20 minutes. Then issue    the following commands:$  E   $ NCP SHOW MODULE CONFIGURATOR KNOWN CIRCUIT STATUS TO filename.txt-C   $ NCP SET MODULE CONFIGURATOR KNOWN CIRCUIT SURVEILLANCE DISABLED   E   The resulting file (named filename.txt) can now be searched for theoG   information of interest.  Most DECnet systems will generate MOP SYSIDfH   messages identifying items such as the controller hardware address andE   the controller type, and these messages are generated and multicastA   roughly every ten minutes.  E   Information on the DECnet MOP SYSID messages and other parts of thedF   maintenance protocols is included in the DECnet network architecture,   specifications referenced in section DOC9.  < ------------------------------------------------------------ MISC8 combined into SUPP4   < ------------------------------------------------------------B MISC9.    Why can't I use PPP and RAS to connect to OpenVMS Alpha?  G   OpenVMS Alpha PPP does not presently support authentication, and the sE   Microsoft Windows NT option to disable authentication during a RAS sG   connection apparently doesn't currently work -- RAS connections will bG   require authentication -- and this will thus prevent RAS connections.o@                                                [Stephen Hoffman]  < ------------------------------------------------------------ MISC10 relocated to SUPP5i  < ------------------------------------------------------------@ MISC12.   Does DECprint (DCPS) work with the LRA0 parallel port?  = The parallel printing port LRA0: found on many OpenVMS Alpha d= systems is capable of some bidirectional communications, withI8 enough for basic operations with most parallel printers.  ? DECprint (DCPS) requires more than just the simple handshaking p> provided by the LRA0: port, therefore DCPS does not work with  the LRA0: port.T4                                      [Paul Anderson]  < ------------------------------------------------------------; MISC13.   How do I check for free space on a (BACKUP) tape?-  > You cannot know for certain, though you can certainly estimate the remaining capacity.n  ? Tape media is different than disk media, as disks have a known r= and pre-determined fixed capacity.  Modern disks also appear  > logically perfect, based on bad block revectoring support and ; the extra blocks hidden within the disk structure for theser bad block replacements.t  @ The capacity of tape media is not nearly as pre-determined, and ; the capacity can vary across different tape media (slightly-: different media lengths or different foil markers or other> variations, for instance) and even on the same media over time@ (as bad spots in the media arise).  Tapes can vary the amount of? recording media required, depending on the remaining length of t= the tape, the numbers of correctable and uncorrectable media  C errors that might occur, the numbers and sizes of the inter-record  > gaps and related tape structure overhead, the particular media@ error recovery chosen, the tape density, the efficiently of any > data compression in use, and the storage overhead required by ( BACKUP, tar, and other similar commands.  ? BACKUP using with the default settings results in approximatelyP@ 15% overhead, in terms of saveset size.  (eg: Assuming a 500 KB ' input, the total size would be 575 KB.)A     Assuming no compression:0    4 GB media / 575 KB saveset =  7294 savesets      Assuming 1:2 compression: 0    8 GB media / 575 KB saveset = 14588 savesets   C NB: There are no inter-record gaps on DAT tapes.  (When determininguB media capacity, you have to consider these with nine-track magtapeE media.  Not with DAT (DDS).  However, the block structure underneath CG the variable length record recording is based on a block size of circa EF 124 KB.  Further, writing doubles filemarks and such can cause a loss C of up to the underlying block size.  Thus even though there are no  A inter-record gaps on DAT, larger savesets are still usually best.S  E The compression algorithms used on various devices are generally not NF documented -- further, there is no way to calculate the effective dataF compression ratio, the tape mark overhead, and similar given just the E data to be stored on tape -- short of actually trying it, of course. F  C A typical compression ratio found with "everyday" data is somewhere  around 1:1.8 to 1:2.  D NB: OpenVMS often uses the term COMPACTION for compression control, - as in the qualifier /MEDIA_FORMAT=COMPACTION.oG                                           [Hoffman, Froehlin, Williams]I  < ------------------------------------------------------------* MISC14.   So what happened to sys$cmsuper?  ! There is no SYS$CMSUPR service.     A The typical wisdom for getting into supervisor access mode (from LA user mode) is to execute a routine in executive mode (via a call B> to SYS$CMEXEC and the appropriate privilege) and then issue a > SYS$DCLAST with the ASTADR parameter pointing to your routine > entry point and the ACMODE parameter specified as PSL$C_SUPER.  @ Alternatively, you can reset mode in the call stack return path = and unwind from executive or kernel out into supervisor mode.R:                                     [Brian Schenkenberger]  < ------------------------------------------------------------< MISC15.   How can I send radio pages from my OpenVMS system?  B There are third-party products available to send messages to radioA paging devices (pagers), communicating via various protocols such ) as TAP (Telocator Alphanumeric Protocol).]  C RamPage (Ergonomic Solutions) is one of the available packages that5A can generate and transmit messages to radio pagers.  Target Alert = (Target Systems; formerly the DECalert product) is another.  o? Networking Dynamics Corp has a product called Pager Plus.  The 2B System Watchdog package can also send pages.  The Process SoftwareE package PMDF can route specific email addresses to a paging service,   as well.  @ Many commercial paging services provide email contact addresses @ for their paging customers -- you can simply send email directly
 to the pager.o  E Some people implement the sending of pages to radio pagers by sendingoD commands to a modem to take the "phone" off the "hook", and then theC paging sequence, followed by a delay, and then the same number that A a human would dial to send a numeric page.  (This is not entirely ? reliable, as the modem lacks "call progress detection", and thebE program could simply send the dial sequence when not really connectedn: to the paging company's telephone-based dial-up receiver.)  ? See SOFT1 for information on the available catalog of products.c  < ------------------------------------------------------------ MISC16 relocated to WIRES3  < ------------------------------------------------------------< MISC17.   How do I reset the LAN (DECnet-Plus NCL) counters?   On recent OpenVMS releases:   ;   LANCP> SET DEVICE/DEVICE_SPECIFIC=FUNCTION="CCOU" devnamep    < ------------------------------------------------------------6 MISC18.   What are the prefixes for the powers of ten?  $         Power   Prefix  Abbreviation         10^-18  atto    au         10^-15  femto   ft         10^-12  pico    pe         10^-09  nano    nu         10^-06  micro   -         10^-03  milli   m-         10^-02  centi   c6         10^-01  deci    dn         10^+01  deca    da         10^+02  hecto   hb         10^+03  kilo    ku         10^+06  mega    M          10^+09  giga    GM         10^+12  tera    Ta         10^+15  peta    P.         10^+18  exa     EC    < ------------------------------------------------------------6 MISC19.   OpenVMS Cluster (SCS) over DECnet?  Over IP?  = The OpenVMS Cluster environment operates over various networkk6 protocols, but the core of clustering uses the System : Communications Services (SCS) protocols, and SCS-specific : network datagrams.  Direct (full) connectivity is assumed.  = An OpenVMS Cluster DOES NOT operate over DECnet, nor over IP.E  & No SCS protocol routers are available.  B Many folks have suggested operating SCS over DECnet or IP over theC years, but SCS is too far down in the layers, and any such project tB would entail a major or complete rewrite of SCS and of the DECnet B or IP drivers.  Further, the current DECnet and IP implementationsA have large tracts of code that operate at the application level, sD while SCS must operate in the rather more primitive contexts of the D system and particularly the bootstrap -- to get SCS to operate over E a DECnet or IP connection would require relocating major portions of -B the DECnet or IP stack into the kernel.  (And it is not clear thatC the result would even meet the bandwidth and latency expectations.)f  @ The usual approach for multi-site OpenVMS Cluster configurationsG involves FDDI, Memory Channel (MC2), or a point-to-point remote bridge,MD brouter, or switch.  The connection must be transparent, and it mustC operate at 10 megabits per second or better (Ethernet speed), with c> latency characteristics similar to that of Ethernet or better.< Various sites use FDDI, MC2, ATM, or point-to-point T3 link.    < ------------------------------------------------------------/ MISC20.   Correctly using license PAKs and LMF?l  @   If you have multiple LMF$LICENSE.LDB databases in your OpenVMS@   Cluster, then each and every PAK must be installed in each and@   every license database present in an OpenVMS Cluster.  Even ifA   you use /EXCLUDE or /INCLUDE, you need to have a consistent seteC   of PAKs registered across all licensing databases present in the e   OpenVMS Cluster.  A   If your software license permits it, you can use the following E(   two commands to transfer license PAKs:       $ LICENSE COPY... 5     $ LICENSE ISSUE/PROCEDURE/OUTPUT=file product,...}  A   To display the particular license(s) required (such as when youn=   receive a NOLICENSE error), use the following DCL sequence:        $ SET PROCESS/PRIVILEGE=ALLa     $ REPLY/ENABLE7     $ DEFINE/SYSTEM/EXECUTIVE LMF$DISPLAY_OPCOM_MESSAGEo  F   This logical name will cause all license failures to generate OPCOM F   messages, and this will hopefully show which license(s) you need -- C   there may well also be additional license failures displayed, as SH   various products can check for and can be enabled by multiple license ?   PAKs.  You will want to deassign this logical name when done.9  '   Some of the more common license PAKs:1  B   DECnet Phase IV:   DVNETRTG, DVNETEND, DVNETEXT, or NET-APP-SUP*B   DECnet-Plus:       DVNETRTG, DVNETEND, DVNETEXT, or NET-APP-SUP*)   TCP/IP Services:   UCX, or NET-APP-SUP*u9   OpenVMS Alpha:     OPENVMS-ALPHA and OPENVMS-ALPHA-USER    OpenVMS VAX:       VAX-VMS#   OpenVMS Galaxy:    OPENVMS-GALAXYc-   Cluster (Alpha):   VMSCLUSTER, NET-APP-SUP*e-   Cluster (VAX):     VAXCLUSTER, NET-APP-SUP*:  E   Various NET-APP-SUP (NAS) license packages are available, each withoD   differing collections of products authorized.  See the various NASD   Software Product Description (SPD) documents for specific details.  #     http://www.compaq.com/info/spd/   H   To determine which license PAK is failing (via a license check failure"   OPCOM message), use the command:  <     $ DEFINE/SYSTEM/EXECUTIVE LMF$DISPLAY_OPCOM_MESSAGE TRUE  C   Realize that defining this logical name will cause license checksaF   that are otherwise hidden (unimplemented, latent, or part of a checkF   for any of a series of licenses) to become visible.  In other words,G   expect to see some spurious license check calls when you define this.-  < ------------------------------------------------------------D MISC21.   Third-party disk/tape/controllers/SCSI/widgets on OpenVMS?  I   A wide variety of third-party widgets -- SCSI and IDE disks and tapes, eC   graphics controllers, etc -- are available for various platforms.a  E   If you purchase third-party "generic" SCSI or IDE storage devices, aE   you and your device vendor will be responsible for the testing and dG   the support of the devices.  I would tend to expect that Compaq will tD   address non-standards-compliance problems within OpenVMS (changes F   that will also not prevent operations with other supported devices, A   of course), but you and/or the device vendor and/or the device eF   manufacturer are responsible for finding and fixing problems in the ;   particular third-party device and or controller involved.c  D   In particular, realize that neither SCSI nor IDE is a particularlyB   standard interface, these interfaces tend to be a collection of C   optionally-implemented and standardized interface features.  You eD   should not and can not simply assume that all SCSI nor IDE storageD   devices are interchangeable.  If you want to try to use a generic B   SCSI device, use V6.2 or later, or (better) V7.1-2 or later.  If;   you wish to try to use IDE, use OpenVMS V7.1-2 or later. E  B   On older OpenVMS releases, see the disk capacity limits (FILE5).  F   With SCSI disks on releases prior to V6.2, ensure that you have the D   ARRE and ARWE settings configured correctly (disabled).  (If not, @   you will see DRVERR fatal drive errors and error log entries.)  C   Some SCSI disks set the medium type byte as part of the SCSI sizeaA   field -- this is a SET CAPACITY extension to SCSI specs.  This  -   problem also applies to VAX V7.1 and later.a  F   Disks with SCSI disk sizes past 8.58 GB and/or with the SET CAPACITYA   extension require ALPSCSI07 ECO or the OpenVMS Alpha V7.1-2 or s2   later release.  (See FILE5 for further details.)  E   Based on the displays of the (undocumented) SYS$ETC:SCSI_INFO tool;t1   this tool is present in OpenVMS V6.2 and later:n  E     Issuing 6-byte MODE SENSE QIOW to get current values for page 01hu*            Page Code ................. 01h@            Page Name ................. Read-Write Error Recovery*            Saveable .................. Yes)            Size ...................... 10p>            Hex Data .................. E6 08 50 00 00 00 08 00,                                        00 00  E     The E6 indicates that the AWRE and ARRE bits are set, and this is E     not acceptable on OpenVMS versions prior to V6.2.  Further along o.     in the SCSI_INFO display, if you also see:  H     Issuing 6-byte MODE SENSE QIOW to get changeable values for page 81h*            Page Code ................. 01h@            Page Name ................. Read-Write Error Recovery*            Saveable .................. Yes)            Size ...................... 10 >            Hex Data .................. C0 08 50 00 00 00 08 00,                                        00 00  C     The C0 value means that the AWRE and ARRE values can be changedeC     on this particular SCSI device.  (This is not always the case.)cE     Use RZDISK from the OpenVMS Freeware, and reset the E6 flag byte tE     to hexadecimal 26 (or whatever the remaining mask when you removeY     bits C0) on page one.   B   Each SCSI and IDE host contains non-trivial SCSI and IDE driver E   software, and each device contains equally non-trivial firmware --  E   taken together with the mechanical and electronic components, this lB   software and firmware will determine whether or not a particular#   device will function as expected.i  E   Also note that various devices -- such as various SCSI CD-R deviceseH   -- can implement and can require vendor-specific protocol extensions, C   and these extensions can require modifications to OpenVMS or the KB   addition of various utilities.  In various of these cases, theseE   devices perform functions that will require them to use SCSI or IDEEF   commands that are (hopefully) architecturally-compatible SCSI or IDE2   command extensions.  (Also see UTIL1 and FILE7.)  A   In order for OpenVMS to officially support a particular device,eG   integration and testing work is mandated.  There can be no certainty aH   that any particular device will operate as expected in any particular B   configuration without first performing this (non-trivial) work.   F   It is quite possible to find two devices -- both entirely compliant D   with applicable standards or interface documents -- that will not    interoperate.a  B   The same general statement holds for OpenVMS bootstrapping on anA   unsupported VAX or Alpha platform.  It might or might not work.uE   In particular, please see the OpenVMS Software Product Description FD   (SPD) for the list of platforms supported by OpenVMS.  OpenVMS is F   not supported on the Personal Workstation -a series, on the Digital E   Server series platforms, on the AlphaServer 2100 series 5/375 CPU, rD   on the Multia, and on a variety of other platforms.  (You might orC   might not see success booting OpenVMS on any of these platforms.)l 					[Stephen Hoffman]  < ------------------------------------------------------------C SOFT1.    Where can I find freeware/shareware/software for OpenVMS?h  A Details on many commercial OpenVMS products are available in the c catalog located at:s  &   http://www.compaq.com/csa/directory/     ----  C An OpenVMS Freeware CD-ROM is distributed with OpenVMS, and is also A available separately (QA-6KZAA-H8).  The contents of the OpenVMS .3 Freeware CD-ROM media are also available online at:   /         http://www.openvms.compaq.com/freeware/p         ftp://ftp.montagar.com/ '         ftp://mvb.saic.com/freewarev40/t  F and at various other sites.  The website also includes various updatesF and new packages that become available after the CD-ROM distributions  are created.  4 Submissions to the OpenVMS Freeware can be made via:  7         http://www.openvms.compaq.com/openvms/freeware/-  E To acquire the OpenVMS Freeware CD-ROM distribution, you can order an-C OpenVMS distribution from Compaq (the Freeware is included)(see thenH OpenVMS SPD for part numbers), or you can specifically order a Freeware + distribution from Compaq under part number:s  
   QA-6KZAA-H8b  D The Freeware CD-ROM set contains a large assortment of freeware, andH is a good starting point if looking for utilities.  Many of the packagesI listed below are also on the Freeware CD.  Some of the most oft-requestedtI OpenVMS tools on the Freeware CD include ZIP and UNZIP, GZIP, MMK (make), G PINE, PERL, TAR, UUENCODE and UUDECODE.  Many other tools are available  on the Freeware.  K The UUENCODE and UUDECODE tools and various other tools are also available  C as part of TCP/IP Services package.  (Use the DCL command procedurenI SYS$STARTUP:TCPIP$DEFINE_COMMANDS.COM available on V5.0 and later to set tD up the necessary DCL foreign command symbols used for these and for 1 various other tools provided by TCP/IP Services.)i     ----  J Compaq also has a separate area containing various OpenVMS software tools  located at:r  !   http://ftp.digital.com/pub/VMS/i  J This area is not consistently maintained, and these tools may (or may not H be) the most current versions of the tool.  Please check for more recent: versions before downloading and using any particular tool.     ----  ; Western Kentucky University (and madgoat) OpenVMS archives:r  ,   http://www2.wku.edu/fileserv/fileserv.html   http://www.madgoat.com/e;                                            [Hunter Goatley]h     ----  @ The FILESERV packages are also available via anonymous FTP from:     Via anonymous FTP from:e'     ftp.wku.edu, under [.VMS.FILESERV].a/     ftp.process.com, under [.WKU.VMS.FILESERV].e>     ftp.vms.stacken.kth.se, under [.MIRRORS.WKU.VMS.FILESERV].1     ftp.ctrl-c.liu.se, under [.WKU.VMS.FILESERV].t     ftp.riken.go.jpn3     ftp.vsm.com.au, under kits and kits/decwindows.u/     ftp.vsm.com.au, via the WWW instead of FTP.g  F or via e-mail from FILESERV@WKUVX1.WKU.EDU. Send the commands HELP and>    DIR ALL in the body of a mail message for more information.     ----  L If you get the packages via WWW or FTP, they're in ZIP format which requiresJ the UNZIP (note: this is not Gnu gunzip!) tool to unpack.  You can get ZIP# and UNZIP from the following areas:u  2   http://www.openvms.compaq.com/freeware/000tools/2   http://www.openvms.compaq.com/freeware/000tools/*   ftp://ftp.wku.edu/vms/fileserv/UNZIP.ZIP/   http://www.decus.de:8080/www/vms/sw/zip.htmlxe    http://www.djesys.com/zip.html"   http://www.djesys.com/unzip.html  E or you can request the FILESERV_TOOLS package from the e-mail server.r  D [Beware: The [000TOOLS...] pre-built versions of ZIP on the OpenVMS G Freeware V4 CD-ROM will erroneously return BILF errors on OpenVMS V7.2 aD and later.  Use of the source on the Freeware V4 to rebuild the ZIP I image(s), or acquiring a pre-built ZIP image from one of the above areas "H can avoid this.  The pre-built version of ZIP on the Freeware V4 kit is C older than the included ZIP sources, and it contains a latent bug.]   H Another source of free software is the vmsnet.sources newsgroup (and theJ corresponding vmsnet.sources.d discussion group).  See the monthly postingG "vmsnet.sources archives" for a list of sites which archive submissionsY to vmsnet.sources.     ----  K Arne Vajhj runs an OpenVMS WWW page, with software and other pointers, at:e   http://www.levitte.org/~ava/     ----   Kermit is available at:h$   http://www.columbia.edu/kermit/ or   ftp://kermit.columbia.edu/     ----   ZMODEM is available at: !   ftp://ftp.cs.pdx.edu/pub/zmodemt9 See the FILES file in that directory for further details.tF Note that this freeware version of ZMODEM will interoperate only with 6 ZMODEM software that is licensed from Omen Technology. (Also on Freeware CD)e 				[Steve Lionel]     ----  G A good source of software for DEC boxes (and anything else pretty much)pC is the DECUS library. online catalogs are available as well as someb4 software via ftp.decus.org; there's a gopher server    gopher://gopher.decus.org/ an FTP server:   ftp://ftp.decus.org/ and a WWW server:    http://www.decus.org/o  H Phone for DECUS orders is 508-841-3502. Lots of good stuff from lots of 7 good folks, and copies on media (tapes, CDs) are cheap.e 				[Everhart@Arisia.gce.com]o     ----  G    DECUS SIG Tape collections are available on Mark Berryman's system, t      ftp://mvb.saic.com/     ----  M    David Jones's DECthreads-based HTTP_SERVER World-Wide Web server for VMS.  <      http://kcgl1.eng.ohio-state.edu/www/doc/serverinfo.html 					    [Hunter Goatly]     ----  )    Secure Shell (SSH) Server for OpenVMS:i5      http://kcgl1.eng.ohio-state.edu/~JONESD/ssh/DOC/   )    Secure Shell (SSH) Client for OpenVMS:        http://www.free.lp.se/fish/  /    Information on OpenSSL (SSLeay) for OpenVMS:,#      http://www.free.lp.se/openssl/m8                                             [Leo Demers]       The SSH terminal client FISH:       http://www.free.lp.se/fish/  D    Information on OpenSSL (SSLeay) and OSU Webserver interoperation:-      http://www.ourservers.net/openvms_ports/e     ----  G DECwindows Motif V1.2-3 includes NCSA Mosaic 2.4 built for UCX.  V1.2-4gB includes Spyglass Enhanced Mosaic, which supports many "Netscape" B enhancements.    Netscape Navigator is also available for OpenVMS.     ----  I A port of Mosaic 2.7-4 which supports UCX, Multinet and SOCKETSHR/NETLIB c is available from:    ftp://wvnvms.wvnet.edu/mosaic/     ----  ? Lynx (a character-cell World-Wide-Web reader) is available from-"   ftp://ftp2.cc.ukans.edu/pub/lynx 					    [Steve Lionel]e     ----  = Netscape Navigator and Mozilla web browsers are available at: ;   http://www.openvms.compaq.com/ebusiness/Technology.html      http://www.mozilla.org/      ----  F PGP (Phil Zimmerman's "Pretty Good Privacy") is available from variousH distribution sites, including those listed in the PGP FAQ.   Information. on an OpenVMS download of PGP is available at:   http://www.pgpi.com/(   http://zone.pspt.fi/pgp/platforms/vms/)   http://www.yrl.co.uk/~phil/pds/pds.html      ----  ? An archive of the CENA DECwindows, X Windows, and VMS software -- packages can be found at the following sites:l     http://decwarch.free.fr/    ftp://ftp2.cnam.fr/decwindows/%   ftp://ftp.ctrl-c.liu.se/decwindows/r2   ftp://ftp.vms.stacken.kth.se/mirrors/decwindows/)   http://www.multimania.com/pmoreau/decw/a   (See also Freeware CD) 					    [Patrick Moreau]o     ----  I ImageMagick is an X11 package for display and interactive manipulation ofEE images.  The package includes tools for image conversion, annotation, I compositing, animation, and creating montages.  ImageMagick can read and  I write many of the more popular image formats (e.g. JPEG, TIFF, PNM, XPM, e Photo CD, etc.). D   http://www.imagemagick.org/, (Also on Freeware CD)  					    [cristy@dupont.com]     ----   XV is available from:     ftp://ftp.cis.upenn.edu/pub/xv'   ftp://ftp.digital.com/pub/graphics/xvo   http://www.sanface.com/p8   ftp://www-pi.physics.uiowa.edu/~dyson/xv-3_10a-vms.zip     ----  I Many software packages are available for displaying various bitmap files PJ (.JPG, .GIF, .BMP, etc) on OpenVMS.  Xloadimage, Xli, Xv, ImageMagick are G the most common tools used under OpenVMS.  Various web browsers such aslH Mozilla (qv) can also display various file formats on OpenVMS.  You can 3 find some of these tools at the DECwindows Archive:w  3   http://www.multimania.com/pmoreau/decw/index.html 4   http://www.multimania.com/pmoreau/decw/images.html;                                            [Patrick Moreau]h     ----  - GHOSTSCRIPT and GHOSTVIEW are available from:t.   www.openvms.compaq.com/freeware/ghostscript/,   www.openvms.compaq.com/freeware/ghostview/(   Also available on the Freeware CD-ROM.  	 Also see:v$   http://www.cs.wisc.edu/~ghost/gnu/     ----  @ XPDF, a viewer for PDF (Adobe Acrobat) files, is available from:   http://www.foolabs.com/xpdf/9                                             [Ki Suk Hahn]   <   Beware: the XPDF on OpenVMS Freeware V4 is somewhat dated.     ----    L A Java-based PDF viewer is available from Adobe, and is known to operate on  recent OpenVMS Alpha releases:   http://www.adobe.com/o     ----  H Various OpenVMS-related tools -- both freeware and shareware -- such as ! txt2pdf -- are available from at:o   http://www.sanface.com/e     ----  F The MPEG library version 1.1 is available for OpenVMS VAX and Alpha at3   ftp://ftp.x.org/contrib/vms/mpeglib-11-vms.readme 0   ftp://ftp.x.org/contrib/vms/mpeglib-11-vms.zip 					    [Patrick Moreau]      ----  4 List of FTP Mirror Sites for the DECWINDOWS archive:  A AXP.PSL.KU.DK             (Multinet)  Mirror of CENA DECW archiveeA FTP2.CNAM.FR              (MadGoat)   Mirror of CENA DECW archivey  I ftp.x.org (in /contrib/vms)  not really a mirror, but I try to put all mye new ports at this site.a     ----  5 List of HTTP Mirror Sites for the DECWINDOWS archive:c  ;   http://axp616.gsi.de:8080/wwwar/cena/decwindows/cena.html,  = Some X clients from the OpenVMS Freeware CDROM are located inN# [.DECWINDOWS.CDFREEWARE] directory.P 						[Patrick Moreau]     ----  H I have written and installed on INFO.CS.PUB.RO an 'Archie' clone for VMS7 software. Telnet to that machine, and login as VMSARCI.lM It contains now listings for over 30 ftp servers with >14 GB of VMS software.TH The most useful commands are LIST, which generates a list of scanned ftpG servers, and FIND <string>, whichs looks for a file containing "string"oI in the name; the search modes are only "substring" [default] and "exact",.L and regex search is not supported (so FIND EMACS will work, but FIND *EMACS*< or FIND *EMACS*.* will not). The search is case-insensitive.I Those of you that know other ftp servers with VMS software that I haven'tED found, please let me know. (The program that build the databases canI recursively scan whole servers- as FTP.WKU.EDU, or just some directories-  as NIC.SWITCH.CH /pub/vms)H Sorry, this service is VERY SLOW [by Western standards], because it runsJ on a quite-busy oldie-but-goodie VAXStation 3400 with 20Mb and a RF71, and; the Internet link is only 256 Kpbs (sometimes unavailable).p 						[stfp@roipb.cs.ipb.ro]     ----  9   The Levitte (extended :-) Family (and OpenVMS) website:k     http://www.levitte.org/n      http://www.levitte.org/~ava/     ---p  E   Robert's OpenVMS Hobbyist Systems, including OpenVMS public domain     software and various ports:c       http://www.ourservers.net/  <                                           [Robert Alan Byer]   ----     CalTech Software Archives:?     http://seqaxp.bio.caltech.edu/pub/SOFTWARE/AAA_CONTENTS.TXTw     ----  *   DJE Systems Website (David J. Dachtera) '     http://www.djesys.com/freeware/vms/d     ----     Web servers:7     Apache Webserver (Compaq Secure Web Server (CSWS)):n=       http://www.openvms.compaq.com/ebusiness/Technology.htmlr=       http://www.er6.eng.ohio-state.edu/~jonesd/apache/1_3_9/n     OSU Webserverl?       http://www.er6.eng.ohio-state.edu/www/doc/serverinfo.htmli#       http://www.kjsl.com/archives/s1       email list: VMS-WEB-daemon-Request@KJSL.COMt     WASD Webserver"       http://wasd.vsm.com.au/wasd/     Purveyor Webserver:g1       email list: listserv@cjis.ci.lincoln.ne.us I9          no subject, one line message: SUBSCRIBE PURVEYORf     ----  #   CD-R (CD-Recordable) media tools:2     please see FILE7     ----  "   Grace (WYSIWYG 2D plotting tool),     http://plasma-gate.weizmann.ac.il/Grace/     ----  G   The POV-Ray ("Persistance of Vision" Raytracer) ray-tracing graphics l/   package is available on the OpenVMS Freeware.a     ----  !   Majordomo mailing list handler:o;     http://www.openvms.compaq.com/ebusiness/Technology.htmlz     ----  ;   PINE (OpenVMS tools for sending and receiving MIME mail): *     ftp://ftp2.kcl.ac.uk/pub/vms/pine-vms/3     http://www.agh.cc.kcl.ac.uk/files/vms/pine-vms/w  5   A MIME tool is available in OpenVMS V7.2 and later.r  >   Also see the mmencode base64 encode and decode available at:9     http://nucwww.chem.sunysb.edu/htbin/software_list.cgie        ----  7 Menufinder (menu-driven system management environment):d'    http://www.itre.com/mf/download.html      ----   tcgmsg, pvm, mpi, linda:<   ftp://v36.chemie.uni-konstanz.de/tcgmsg_vms/tcgmsg_vms.zip     ----  E OpenVMS software that can control a Tripp-Lite Uninterruptable Power . Supply (UPS) is available from:.  ;     http://seqaxp.bio.caltech.edu/pub/SOFTWARE/TCONTROL.ZIP :                                             [David Mathog]  B UPShot web-based software for controlling a UPS is available from:(     http://www.tmesis.com/apc/beta.htmlxB                                             [Brian Schenkenberger]       ----  F Examples of using the OpenVMS Foreign MAIL interface are available at:@   http://www.hhs.dk/anonymous/pub/vms/collection/foreignmail.zip1   http://www.hhs.dk/anonymous/pub/vms/nbl/nbl.zipe  :                                             [Arne Vajhoej]     ----  = For tools to manage or to search your OpenVMS MAIL file, see:5=    http://www2.wku.edu/scripts/fileserv/fileserv.com?MLSEARCH   <                                             [Phillip Helbig]     ----? AscToHTM attempts to convert any plain text file to HTML, whilec> AscToTab restricts itself to files that are plain text tables.5 (Versions are also availabe on the OpenVMS Freeware).i.     http://www.jafsoft.com/asctohtm/index.html.     http://www.jafsoft.com/asctotab/index.html1                                             [Jaf]v     ----  = Information on the SAMBA package (PC disk and print services)e is available at:8   http://ifn03.ifn.ing.tu-bs.de/ifn/sonst/samba-vms.html   http://www.samba.org/a  E To subscribe to the SAMBA-VMS mailing list e-mail listproc@samba.org s; with no subject line and the following single line of text:e  #  subscribe samba-vms Your Full Nameo  	 Also see:o   http://lists.samba.org/s     ----   Perl: See SOFT12     ----   XML:  8   Source code of an XML Parser is available from Oracle.     Also see:e  '     http://www.python.org/sigs/xml-sig/t    ?   An XML parser is available as part of OpenVMS V7.3 and later.o     ----  ' GTK+ (The GIMP GUI Tookit) for OpenVMS:e9   http://www.openvms.compaq.com/ebusiness/Technology.htmls     ----  D OpenVMS Porting Library now available - for easier porting of C/C++ " applications from UNIX to OpenVMS:9   http://www.openvms.compaq.com/ebusiness/Technology.html      ----   Mlucas (specialized FFT):g  *   ftp://hogranch.com/pub/mayer/README.html1                                [Robert Deininger]n     ----  G Tools to monitor the terminals and the activity of other OpenVMS users aI (in addition to existing auditing capabilities in OpenVMS) are available. D Peek and Spy (Networking Dynamics) and Contrl (Raxco) are two of theH commercial packages, while the freeware Supervisor package is available  on OpenVMS VAX.o  $   http://www.networkingdynamics.com/   http://www.raxco.com/n     ----   Python for OpenVMS:e     http://www.python.org/'   http://decus.decus.de/~zessin/python/0   Various packages: 6   http://richj.home.mindspring.com/richware/index.html:   http://www3.sympatico.ca/n.rieck/links/cool_vax_vms.html  < ------------------------------------------------------------@ SOFT2.    Where can I find the UNIX <whatever> tool for OpenVMS?   POSIX:B   POSIX-compliant, Compaq-supported versions of POSIX routines and   utilities:  C     lex, yacc, grep, tar, uuencode, uudecode, rcs, man, cpio, make,aA     awk, ar, mail, etc., the POSIX shell, the POSIX C programmingt     interface, etc.   @     POSIX utilities can be used from within the POSIX shell, and4     via the DCL `POSIX/RUN POSIX$BIN:tool.' command.  A     POSIX is a separately-installed package, and is licensed with ?     OpenVMS V5.5 later.  The POSIX installation kit is includedvA     on the consolidated distribution CD-ROM kit, and installationo'     kits are also available separately.a  D     The POSIX package is no longer supported on OpenVMS, components C     of the POSIX standard such as parts of the POSIX API are being cC     added into OpenVMS.  Versions of POSIX generally do not operateM3     on V7.x OpenVMS VAX and OpenVMS Alpha releases.n   C: oH   Common C system and library routines are present in the DEC C run-timeH   library, which is available for V5.5 and later, and is shipped in V6.1I   and later.  DEC C is the upgrade for VAX C, DEC C and VAX C can coexistaJ   on the same system OpenVMS VAX system, and both compilers can be enabled   via the "C" license PAK.  K     Also see SYS$EXAMPLES:, and (if either is installed) the DECW$EXAMPLES:M     and UCX$EXAMPLES: areas.  
 X Windows:%   Various Compaq X Windows utilities:A  G     xwd, xev, mosaic WWW browser, xrdb, bmtoa and atobm, xpr, ico, etc..  B     In DECW$UTILS: in DECwindows Motif V1.2-3 and later.  Also see0     DECW$EXAMPLES: for example X and C programs.  ! Miscellaneous tools and examples:T6   Various unsupported OpenVMS tools and code examples:  D     DWAUTH (X Windows SYSUAF authorize-like tool), various versions	C     of grep, fgrep, yacc, vmstar, uuencode, gawk, etc.  html tools,-B     the mx SMTP mail exchange package, X windows flight simulator,C     the mxrn X windows news reader, the OSU HTTPD WWW server, a WWWh=     gopher browser, etc. are all on the FreeWare V2.0 CD-ROM.   	 IP tools: E   DEC TCP/IP (UCX) contains tools such as ping, uuencode, smtp, snmp,eG   rcp, nfs, tnfs, etc.  OpenVMS V6.2 and UCX V3.3 and later can be usedtF   together in support of the /FTP, /RCP, /RLOGIN, /TELNET, and /TN3270%   qualifiers on various DCL commands.p  4     Also see the various C examples in UCX$EXAMPLES:   					[Stephen Hoffman]  	 vi clones   1   vile, vim and elvis (vi clones) run on OpenVMS.s  $   The current version of vile is 7.1   It's available atd/ 	http://www.clark.net/pub/dickey/vile/vile.html[2 	Versions of VILE are also on the OpenVMS Freeware       vim: vi improved      http://www.polarfox.com/vim/9                                         [Zoltan Arpadffy]s  
 GNU tools:  B   Information on the GNU on VMS (GNV) Project, which aims to port 7   GNU software (BASH, etc) to OpenVMS, is available at:e       http://gnv.sourceforge.net/L     Software info:  '     http://vms.gnu.ai.mit.edu/software/      Software archive:e  .     ftp://vms.gnu.ai.mit.edu/gnu-vms/software/     GCC:  I   A mirror for work performed at the Progis company in Germany in portingN?   GCC (GNU C) to OpenVMS Alpha and OpenVMS VAX is available at:/  '     ftp://vms.gnu.org/progis_mirror/gccm-     http://www.levitte.org/~ava/vms_gnu.htmlx/  K   The latest (known to me) GCC version for VAX/VMS (binaries only) is 2.7.1p   from Pat Rankin's site.   &     ftp://ftp.caltech.edu/pub/rankin/   G                                     [Jason Armistead, Richard Levitte, rC                                     Arne Vajhoej, John E. Malmberg]a  I There are also updated header files for GCC on OpenVMS VAX that allow it .6 to work with TCP/IP Sockets and the Compaq C C RTL at:  (   ftp://ftp.qsl.net/pub/wb8tyw/gcc281_u/  :                                         [John E. Malmberg]    = Some of the available console management options for OpenVMS:u  #   http://www.robomon.com/  (Heroix)n1   http://www.ki.com/products/clim/  (KI Products)v,   http://www.globalmt.com/ (Global Maintech)!   http://www.tditx.com/ (TechSys))0   http://www.cai.com/products/commandit.htm (CA)3                                        [Kerry Main]o  A If you need to change the file modification date and are looking i> for a utility such as the UNIX touch tool, look at DFU on the > OpenVMS Freeware (DFU SET or simular), or use an existing DCL  commands such as:   5   SET FILE/PROTECT=(current_protection_mask) [...]*.*l    @ A table listing translations between UNIX shell and OpenVMS DCL 8 commands was posted to comp.os.vms by Christopher Smith:     http://deja.com/getdoc.xp?.     AN=581596523.1&CONTEXT=953337549.952369155     --  3 The UNIX touch tool is available via various means:e  !   $ RENAME filename.ext;version *w7   http://nucwww.chem.sunysb.edu/helplib/@hvmsapps/TOUCHe.   MadGoat FILE tool (see the MadGoat archives)(     use /REVISION_DATE or /CREATION_DATE)   The DFU tool (see the OpenVMS Freeware)e   The pair: 5     $ set file 'p1' /acl=(ident=[system],access=none)r=     $ set file 'p1' /acl=(ident=[system],access=none) /delete4   SET FILE/VERSION=0   The following hack:d&     $!   Command procedure SETDATE.COM     $!1     $!   Changes the DATES for an input file to a      $!   file named OUTFILE.     $!     $assign/nolog 'p1' outfile(     $convert/fdl=sys$input 'p1' outfile:     date     creation   01-apr-2010     expiration 01-Apr-2012     revision   01-Apr-2011
     backup     ...w,   The following RMS system service sequence:     $open (with xabrdt) (     set the desired values in the xabrdt
     $close  < ------------------------------------------------------------I SOFT3.    Where can I get the Netscape Navigator Mozilla.org Web Browser?n  C Mozilla.org is the open source organization providing Netscape and  B other interested parties with a browser.  Netscape is expected to C commercialize this mozilla.org browser, add additional proprietary nG features, and release it as Netscape Communicator (version number TBD).uG This Netscape Communicator will contain the features that the Internet s6 community expected to see in Netscape Communicator V5.  B OpenVMS Engineering is currently porting Mozilla.org's web browserH to OpenVMS -- OpenVMS baselevels of the browser are currently available  for download.  h  5 The Mozilla.org web browser schedule is available at:b     http://www.mozilla.org/t  > The latest information and current downloads are available at:  9   http://www.openvms.compaq.com/ebusiness/Technology.html   E See section SOFT9 for information on various certificates for V3.003 b= Netscape Navigator; certificates that have presently expired.s 					[Sue Denham]m 					[Stephen Hoffman]  < ------------------------------------------------------------+ SOFT4.    Where can I get Java for OpenVMS?t  D   Java is available on and is included with OpenVMS Alpha, starting F   with the OpenVMS Alpha V7.2 and later releases.  Java download kits :   are available for OpenVMS Alpha V7.1 and later releases.  G   Java is not available on OpenVMS VAX.  As for why: the Java language MH   definition requires a floating point format (IEEE) that is not native E   to VAX, and this would require the emulation of all floating point lH   operations within Java applications.  Further, the C source code used D   to implement for Java itself is heavily dependent on passing IEEE H   floating point values around among the many internal subroutines, and G   adding support for VAX would entail changes to the Compaq C compiler lI   for OpenVMS VAX -- and specifically to the VAX VCG code generator that mH   is used by Compaq C on OpenVMS VAX systems -- in order to add support I   for passing IEEE-format floating point doubles around.  Alternatively, aJ   extensive changes to the Java source code to remove the assumption that -   the double is an IEEE floating point value.p  F   There are currently no plans to make a version of Java available forI   OpenVMS VAX.  (A prototype version of Java was created for OpenVMS VAX,-6   and performance was found to be inadequate at best.)  H   If Java2 or other environment lifts the requirements for IEEE floatingK   point as part of the language definition, this decision may be revisited.w  I   If you are having problems with Display Postscript, you need to upgradepG   your Java kit -- 1.2.2-3 and later remove the requirement for Display E   Postcript extensions, and Java 1.2.2-3 is required with DECwindows i   V1.2-6 and later.w  F   For additional information on Java for Alpha systems, please see theA   OpenVMS documentation (V7.2 and later), and the following site:.  /     http://www.compaq.com/java/alpha/index.htmln  < ------------------------------------------------------------J SOFT5.    VAX C and DEC C, and other OpenVMS C Programming Considerations?  F   VAX C V3.2 was released for OpenVMS VAX systems in 1991.  DEC C V4.0F   replaced VAX C V3.2 in 1993 as the Compaq C compiler for OpenVMS VAXF   systems.  Compaq C is the ANSI C compiler for OpenVMS Alpha systems.E   VAX C predates the ANSI C standards, and has various areas that aredJ   not compliant with ANSI C requirements.  Compaq C is an ANSI C compiler,H   and can also compile most VAX C code when /STANDARD=VAXC is specified.I   Versions of this compiler between V3.2 and V6.0 (exclusive) were known e   as either DEC C or DIGITAL C.a  F   Both compilers can be installed at the same time on the same OpenVMSD   VAX system, allowing a migration from VAX C to DEC C, and allowingF   the same DEC C code to be used on OpenVMS VAX and OpenVMS Alpha.  In0   1999, the C compiler version is Compaq C V6.0.  B   The system manager can choose the system default C compiler whenF   Compaq C is installed on a system with VAX C, and a C programmer canK   explicitly select the required compiler for a any particular compilation.t  K   A current "C" license PAK allows access to both VAX C and Compaq C on the    same OpenVMS VAX system.  M   Various Compaq C versions can be installed on OpenVMS VAX V5.5-2 and later.RL   OpenVMS VAX releases such as V5.5-2 and V6.0 will require the installationK   of a Compaq C RTL kit, a kit that is included with the Compaq C compiler.oI   OpenVMS VAX versions V6.1 and later do not require a seperate RTL kit, nI   but Compaq C RTL ECO kits are available to resolve problems found with h(   the C RTL on various OpenVMS releases.  E   Wwith Compaq C, for automatic resolution of the standard C library rD   routines by the LINKER utility, use the /PREFIX qualifier, such asG   /PREFIX=ALL_ENTRIES.  If a particular application program replaces an E   existing C library routine, use /PREFIX=(ALL_ENTRIES,EXCEPT=(...)).eE   (VAX C required explicit specification of an RTL shareable image orw$   C object library during the link.)  H   When the /PREFIX is requested, the compiler generates a "decc$" prefixI   on the specified symbols.  This prefix allows the LINKER to resolve theIG   external symbols against the symbols present in the DECC$SHR library.,F   The DECC$SHR library is included in the IMAGELIB.OLB shareable imageH   library, and IMAGELIB is searched by default when any program (writtenE   in any language) is LINKed.  Because the standard C library routinenF   names are very likely to match application routines written in otherF   languages, a prefix "decc$" is added to the C symbol names to assureD   their uniqueness; to prevent symbol naming conflicts.  C programs,E   however, can sometimes have private libraries for various purposes, I   and the external routines share the same names as the library routines. F   (This is not recommended, but there are applications around that useE   this technique.)  Thus the need to explicity specify whether or not/E   the "decc$" prefix should be prepended to the external symbol namesq   by the compiler.  F   The qualifiers, and most (all?) with associated pragmas, that may be<   of interest when migrating VAX C code to Compaq C include:       /PREFIX=ALL_ENTRIES B       As mentioned above.  Failure to specificy this qualifier canA       cause the compiler to not add the prefixes for the names ofeE       the C library routines into the references placed in the object E       module, which can in turn cause problems resolving the externals<       symbols in the library when the object code is linked.  $     /ASSUME=WRITABLE_STRING_LITERALSC       Some VAX C programs erroneously write to the string literals.tB       By default, Compaq C does not allow the constants to change.       /SHARE_GLOBALSA       Enables sharing ("shr") of globals and of extern variables.aG       Compaq C sets externs as non-shareable ("noshr"), VAX C as "shr".h       /EXTERN_MODE=COMMON_BLOCKc=       VAX C assumes common block model for external linkages.M       /[NO]MEMBER_ALIGNMENTvA       Refers to the padding placed between member elements withint?       a struct.  Disabling member alignment packs the data mores=       tightly into memory, but this packaging has performanced;       implications, both on OpenVMS VAX and particularly onh       OpenVMS Alpha systems.  E   Permit structure members to be naturally aligned whenever possible,oE   and avoid using /NOMEMBER_ALIGNMENT.  If you need to disable member A   alignment, use the equivilent #pragma to designate the specificmE   structures.  The alignment of structure members normally only comesUB   into play with specific unaligned data structures -- such as theF   sys$creprc quota itemlist -- and with data structures that are usingD   data that was organized by a system using byte or other non-member   alignment.  I   Versions of Compaq C such as V6.0 include the capability to extract the D   contents of the standard header libraries into directories such asG   SYS$SYSROOT:[DECC$LIB...], and provide various logical names that can:G   be defined to control library searches.  With Compaq C versions such pH   as V6.0, the default operations of the compiler match the expectationsC   of most OpenVMS programmers, without requiring any definitions oftG   site-specific library-related logical names.  (And logical names leftlE   from older DEC C versions can sometimes cause the compiler troubles    locating header files.)-  D   Compaq C V5.6 and later include a backport library, a mechanism byF   which Compaq C running on older OpenVMS releases can gain access to G   newer RTL routines added to the RTL in later OpenVMS releases -- the aE   language RTLs ship with OpenVMS itself, and not with the compilers.   F   Example C code is available in SYS$EXAMPLES:, in DECW$EXAMPLES (whenF   the DECwindows examples are installed), in UCX$EXAMPLES (when CompaqE   TCP/IP Services is installed), on the Freeware CD-ROMs, and at web a   sites such asc  )     http://www.openvms.compaq.com/wizard/t     Other common C issues:  F     The localtime() function and various other functions maintain the C     number of years since 1900 in the "struct tm" structure member  G     tm_year.  This field will contain a value of 100 in the year 2000,  F     101 for 2001, etc., and the yearly incrementation of this field is     expected to continue.r  G     The C epoch typically uses a longword (known as time_t) to contain  H     the number of seconds since midnight on 1-Jan-1970.  At the current J     rate of consumption of seconds, this longword is expected to overflow J     (when interpreted as a signed longword) circa 03:14:07 on 19-Jan-2038 J     (GMT), as this time is circa 0x7FFFFFFF seconds since the C base date.G     (The most common solution is to ensure that time_t is an unsigned.)   H     If C does not correctly handle the display of the local system time,J     then check the UTC configuration on OpenVMS -- the most common symptomI     of this is a skew of one hour (or whatever the local daylight savings)J     time change might be).  This skew can be caused by incorrect handling J     of the "is_dst" setting in the application program, or by an incorrectH     OpenVMS UTC configuration on the local system.  (See section TIME4.)  F     When sharing variables with other languages, here is some example      Compaq C code...  	       ...h       #pragma extern_model save.(       #pragma extern_model strict_refdef!       extern int   VMS$GL_FLAVOR;-"       #pragma extern_model restore	       ...-  5     and here is some associated example Bliss code...o  	       ...        EXTERNAL          VMS$GL_FLAVOR,e
       ....       Other common C++ issues:  G     Compaq C++ (a separate compiler from Compaq C) provides both symbol H     mangling and symbol decoration.  Some of the details of working withG     longer symbol names and the resulting symbol name mangling in mixedhE     language environments are listed in the shareable image cookbook,OE     and in the C++ documentation.  Symbol name decoration permits theMJ     overloading of functions (by adding characters to the external symbol J     for the function to indicate the function return type and the argumentI     data types involved), and mixed-language external references can and mL     often do need to disable this decoration via the extern "C" declaration      mechanism:         extern "C"	         {n(         extern int ExternSymbol(void *);-         extern int OtherExternSymbol(void *);o	         }e  G   Also see ALPHA16 for information on /ARCHITECTURE and /OPTIMIZE=TUNE.i  F   See PROG17 for information on the C system and the lib$spawn call in   CAPTIVE environments.C     Also see: 6     http://www.openvms.compaq.com/wizard/wiz_2486.html6     http://www.openvms.compaq.com/wizard/wiz_3803.html   < ------------------------------------------------------------1 SOFT6.    Obtaining user input in DCL CGI script?   E If you choose to use the GET method, then the form data is available a6 in the DCL symbol QUERY_STRING, in URL-encoded format.  E If you use the POST method, then you need to read the form data from  E stdin. For a DCL CGI script running under the Netscape FastTrack web  ? server, you can read the data using the following READ command::     $ READ SYS$COMMAND postdataa   to read the information in.r=                                                 [Colin Blake]   @ The following describes the use of DCL command procedures as CGI  scripts with the OSU web server:  2 http://www.levitte.org/~ava/cgiscripts_other.htmlx>                                                 [Leif Jansson]  < ------------------------------------------------------------1 SOFT7.    How do I get my own batch entry number?6  > To have a batch procedure retrieve its own batch entry number, use the following:  '   $ Entry = F$GETQUI("DISPLAY_ENTRY", -a0       "entry_number","display_entry","this_job")  E Remember that the entry numbers issued by the OpenVMS Job Controller iE are opaque longword values.  Don't assume you know the format of the  1 number, nor the range of numbers you might see...l>                                                 [Peter Weaver]  < ------------------------------------------------------------0 SOFT8.    How do I convert to new CMS libraries?  E A change was made to the format of the CMS database for CMS librariesMC starting with V3.5-03 -- to ensure that earlier versions of CMS arepB unable to access the database once the "conversion" to V3.5-05 andG later is made, you must issue the following two commands when upgradingcB from V3.5-03 and prior.  (The only differences between CMS versionA V3.5-03 and CMS version V3.5-05 involve changes to ensure that np < earlier version of CMS can access the "converted" database.)  B To perform the "conversion", issue the following commands for each CMS library present:  ,     $ RENAME disk:[directory]00CMS.* 01CMS.**     $ COPY NLA0: disk:[directory]00CMS.CMS  B The new file 00CMS.CMS must have the same security settings as theG 01CMS.CMS file, and is created solely to ensure continued compatibility,E with tools that expect to find a 00CMS.CMS file (eg: various versionsa. of the Language-Sensitive text editor LSEDIT).  < ------------------------------------------------------------B SOFT9.    Where can I get new certificates for Netscape Navigator?  @ The URLs that I found for adding/updating root certificates are:  E http://www.entrust.net/customer/generalinfo/import.htm        entrustwD http://www.thawte.com/                                        thwateF https://www.verisign.com/server/prg/browser/root.html         verisign6                                           [Ken Chaney]  > To update certificates in Netscape Navigator V3.03 on OpenVMS, use the following:  8 Here's how to update your Root certificates in Netscape:  0 Thawte Server certificate which expired in 1998:  : 1) Under the Options Menu choose "Security Preferences..."% 2) Select the "Site Certificates" tabP8 3) Select "Thawte Server CA" in the list of certificates, 4) Select "Delete Certificate" and then "OK". 5) Go to http://www.thawte.com/serverbasic.crtL 6) Follow the instructions on the popup dialog box to accept the certificateH    This mostly involves hitting the "Next" button and clicking an acceptI    button and then naming the resulting certificate.  I named it the sames    name as the original.  ; VeriSign/RSA Server certificate which expired Dec 31, 1999:R  : 1) Under the Options Menu choose "Security Preferences..."% 2) Select the "Site Certificates" tabiE 3) Select "Verisign/RSA Secure Server CA" in the list of certificatesd, 4) Select "Delete Certificate" and then "OK"> 5) Go to https://www.verisign.com/server/prg/browser/root.htmlL 6) Follow the instructions on the popup dialog box to accept the certificateH    This mostly involves hitting the "Next" button and clicking an acceptG    button and then naming the resulting certificate.  Verisign suggests      using the name "VeriSign CA".  ;                                           [Vance Haemmerle]t  < ------------------------------------------------------------3 SOFT10.   Why doesn't DCL symbol substitution work?-  F The DCL symbol substitution processing occurs only at the DCL prompt, E not within data and not within files.  If you wish to perform symbol oC substitution in this environment, you typically write a small file rE containing the command(s) and data to be invoked -- potentially only lC the data -- and you then invoke the created procedure or reference t the specified data.a  C In this case, use of a file containing nolinemode commands or other C techniques might be useful -- you will want to ensure that the textoF editor you use does not attempt to use screen mode or similar, as thisD is not generally considered adventageous within a command procedure.  . Tools such as FTP have alternatives: COPY/FTP.  E DCL symbol substitution occurs in two passes, using the ampersand and E the apostrophe.  In most cases, only the apostrophe is necessary.  IntG a few cases -- such as the DCL PIPE command -- you will may need to useTE the ampersand to get the substitution to work.  The following exampletB uses ampersand substitution to transfer the contents of the header into a logical name:  F   $ PIPE CC/VERSION | (READ SYS$PIPE hdr ; DEFINE/JOB/NOLOG hdr &hdr )  G A logical name (in the job logical name table; shared by all processes dG in the current job) was used as DCL symbols cannot be returned back out , from a DCL PIPE or other spawned subprocess.    < ------------------------------------------------------------ SOFT11.   Duplicates MGMT40.  < ------------------------------------------------------------+ SOFT12.   Where can I get Perl for OpenVMS?   F OpenVMS support is included in the standard distribution of Perl, the I popular scripting language created by Larry Wall.  In addition to nearly tE all of the functionality available under Unix, OpenVMS-specific Perl tE modules provide interfaces to many native features, as well as accessoF to Oracle, Ingres, and Sybase databases via the Perl DBI available on  OpenVMS.  G A website useful for getting started with Perl on OpenVMS -- where you  H will find such things as download links, instructions, auxiliary tools, & and sample scripts -- is available at:  !      http://www.sidhe.org/vmsperlt  E If you have a C compiler, the best way to obtain Perl is to download ED and build it yourself.  The latest production quality source kit is  available from:a  /      http://www.perl.com/CPAN/src/stable.tar.gz   I You will need GUNZIP and VMSTAR (both available from the OpenVMS FreewareaG CD, or from other sites) to unpack the archive; once you've done that, r- read the instructions in the README.vms file.   G Binary distributions for most Alpha and VAX environments are available sH on the OpenVMS Freeware CD-ROM and from various websites, including the 
 following:  /      http://www.sidhe.org/vmsperl/prebuilt.htmle2      http://www.openvms.compaq.com/freeware/perl5/  H During active Perl development cycles, test kits are sometimes found at: from:         ftp://ftp.sidhe.org/u  H Watch the mailing list (see below) for details on experimental releases.  I Charles Lane maintains pages on how to write CGI scripts in Perl for the -G OSU HTTP server, as well as more general tips, tricks, and patches for g% building and running Perl on OpenVMS:l  )      http://www.crinoid.com/crinoid.htmlx   G There are OpenVMS-specific Perl modules that implement interfaces to a XH subset of the VMS System Services. With these modules, you can get (and J often set) device, job, queue, user, system, and performance information. F The lock manager, RMS indexed files, screen management utilities, and G Intracluster Communication Services are also accessible via Perl.  The  ( relevant modules are all available from:  3      http://www.perl.com/CPAN/modules/by-module/VMSD  F To subscribe to the OpenVMS Perl mailing list (a discussion forum for A both user support and new development), send an email message to:        vmsperl-subscribe@perl.org  - The mailing list archives may be searched at:n  4     http://www.xray.mpe.mpg.de/mailing-lists/vmsperl;                                               [Craig Berry]h  < ------------------------------------------------------------4 SOFT13.   Where can I get DECmigrate (VEST and TIE)?  @   The DECmigrate image translation tool, a tool that translates >   OpenVMS VAX images for use on OpenVMS Alpha is available at:  <      http://www.support.compaq.com/amt/decmigrate/index.html  '   This tool is not currently supported.      See UTIL4.   [End of Part 4/5]   N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  # Date: Tue, 10 Apr 2001 18:13:56 GMTp2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman); Subject: OpenVMS Frequently Asked Questions (FAQ), Part 5/5h2 Message-ID: <E3IA6.752$fB6.19160@news.cpqcorp.net>   Archive-name: dec-faq/vms/part5c Posting-Frequency: monthly Last-modified: 10 Apr 2001 Version: VMS-FAQ-5.TXT(6)x    9 This is the OpenVMS Frequently Asked Questions Part 5/5. )@ Please see Part 1/5 for administrivia, indexing, archiving, etc.    < ------------------------------------------------------------, ALPHA1.   What do the letters AXP stand for?  I While there are many fanciful "definitions" which have circulated widely,oH the truth is that AXP is not an abbreviation nor an acronym; the lettersC do not mean anything.  They are just three letters chosen to form ae
 trademark.  E When it came time to chose a "marketing name" for the Alpha AXP line, I the company was in a quandary.  The internal "code name" for the project,aK Alpha, was widely known and would seem the ideal choice, but it was alreadyeJ in common use by a number of other companies and could not be trademarked.G A well-known "name search" firm was hired and was asked to come up withmF two lists of possible names.  The first list was intended to evoke theC feeling of "extension to VAX", while the second list was to suggestnG "not a VAX".  Unfortunately, none of the choices offered were any good;qI for example, "VAX 2000" was found on the first list while the second listf< contained "MONDO" (later to be used for a kids' soft drink).  J Shortly before announcement, a decision was made to name the new line ARA,H for Advanced RISC Architecture.  However, an employee in Israel quickly K pointed out that this name, if pronounced in the "obvious" manner, sounded qE very much like an Arabic word with decidely unfortunate connotations.nF Eventually, AXP was selected; the architecture would be referred to as= "Alpha AXP" whereas products themselves would use just "AXP".i  G Use of the AXP term has been phased out in favour of using Alpha.  For eG example, "OpenVMS AXP" is now officially refered to as "OpenVMS Alpha".o  < ------------------------------------------------------------A ALPHA2.   What are the OpenVMS differences between VAX and Alpha?   I Very few.  As of OpenVMS V6.1, the VAX and Alpha platforms are very closeqB to "feature parity".  Most applications can just be recompiled and& run.  Some differences to be aware of:  A     - The default double-precision floating type on OpenVMS Alpha_D       is VAX G_float, whereas on VAX it is usually D_float.  D_float@       is available on Alpha, but D_float values are converted toA       G_float for computations and then converted back to D_floataE       when stored.  Because the G_float type has three fewer fraction E       bits than D_float, some applications may get different results.a;       IEEE float types are also available on OpenVMS Alpha.M  C     - Data alignment is extremely important for best performance onp?       Alpha.  This means that data items should be allocated at C       addresses which are exact multiples of their sizes.  Quadwordl?       alignment will offer the best performance, especially for A       character values and those smaller than 32 bits.  CompilerseB       will naturally align variables where they can and will issue3       warnings if they detect unaligned data items.t  E     - Compaq C is the only C compiler Compaq offers on OpenVMS Alpha.iA       It is compatible with DEC C on OpenVMS VAX, but is somewhatlL       different from the older VAX C compiler most people are familiar with.D       Read up on the /EXTERN_MODEL and /STANDARD qualifiers to avoid       the most common problems.M  K     - The page size on Alpha systems is variable, but is at least 8K bytes.eE       This can have some effect on applications which use the $CRMPSCiB       system service as well as on the display of available memoryF       pages.  The page size is available from $GETSYI(SYI$_PAGE_SIZE).  K There are also a number of manuals which discuss migration to OpenVMS Alpha K available on the documentation CD-ROM media, both in the main documentationa* and in the archived documentation section.  F On more recent OpenVMS Alpha versions, OpenVMS Alpha has begun to add F features and support not available on OpenVMS VAX.  Salient new areas  include the following:  7     - 64-bit addressing in OpenVMS Alpha V7.0 and latern:     - Multi-host SCSI support (SCSI TCQ) in V6.2 and later&     - PCI support (platform-dependent).     - OpenVMS Galaxy support in V7.2 and later  < ------------------------------------------------------------& [ALPHA3 removed, information obsolete]  < ------------------------------------------------------------> [ALPHA4 relocated to VMS16, and out of Alpha hardware section]  < ------------------------------------------------------------F ALPHA5.   Seeking performance information for Alpha (and VAX) systems?  F   Compaq makes a wide range of performance documents available through.   its FTP and WWW Internet servers (see DOC2).  F   The following contain information on current Alpha and VAX products:  2     http://www.compaq.com/alphaserver/servers.html4     http://www.compaq.com/alphaserver/vax/index.html  D   The following sites contain information on various retired VAX and   Alpha products:t  8     http://www.compaq.com/alphaserver/archive/index.html?     http://www.compaq.com/alphaserver/performance/perf_tps.html      Also see CPU2000:o  $     http://www.spec.org/osg/cpu2000/8     http://www.spec.org/osg/cpu2000/results/cpu2000.html    < ------------------------------------------------------------D ALPHA6.  Where can I get updated console firmware for Alpha systems?    = Firmware updates for Compaq Alpha systems are available from:t  ?     ftp://ftp.digital.com/pub/Digital/Alpha/firmware/index.html 5     ftp://ftp.digital.com/pub/Digital/Alpha/firmware/x@     ftp://ftp.digital.com/pub/Digital/Alpha/firmware/readme.html  J The latest and greatest firmware -- if updated firmware has been released C after the most recent firmware CD was distributed -- is located at:_  =     ftp://ftp.digital.com/pub/Digital/Alpha/firmware/interim/q  J Please send your comments and feedback to alpha_server@service.digital.com  F For information on creating bootable floppies containing the firmware,6 and for related tools, please see the following areas:  C   ftp://ftp.digital.com/pub/DEC/Alpha/firmware/utilities/mkboot.txtkF   ftp://ftp.digital.com/pub/DEC/Alpha/firmware/utilities/mkbootarc.txtE   ftp://ftp.digital.com/pub/DEC/Alpha/firmware/utilities/mkntboot.txts  G The SROM firmware loader expects an ODS-2 formatted floppy, see mkboot.rD As for which image to use, the ROM image uses a header and the file F extension .ROM, and the SROM bootable floppy cannot use the .ROM file.  ;                                           [Stephen Hoffman]   A To check the firmware loaded on recent OpenVMS Alpha systems, user the command:  0   $ write sys$output f$getsyi("console_version")0   $ write sys$output f$getsyi("palcode_version")   SDA> CLUE CONFIG7                                           [Clair Grant]V     Also see ALPHA14.l    < ------------------------------------------------------------D ALPHA7.   How do I boot an AlphaStation without monitor or keyboard?  H The AlphaStation series will boot without a keyboard attached.  To use aN serial terminal as the console, issue the console command SET CONSOLE SERIAL -H after that, it will use the terminal.  The DEC 3000 model 300 series hasC a jumper on the motherboard for this purpose.  Various older Alpha  D workstations generally will not (automatically) bootstrap without a F keyboard connected, due to the self-test failure that arises when the  (missing) keyboard test fails.  K The usual settings for the console serial terminal (or PC terminal emulator  acting as a serial console are:w  >   9600 baud, 8 bits, no parity, one stop bit (9600 baud, 8N1).  K The AlphaStation and AlphaServer series use the PC DIN serial connector for F the "COM1" and "COM2" serial lines, see WIRES1 for details and pinout.  < ------------------------------------------------------------< ALPHA8.  Will OpenVMS run on a Multia? AlphaPC 164LX? 164SX?  F Yes, there are a set of unsupported images that permit recent OpenVMS H Alpha versions to bootstrap on the Multia UDB system.  These images and J the associated instructions are available at the OpenVMS Freeware website:  0   http://www.openvms.compaq.com/freeware/multia/  > Instructions are included IN the kits.  READ THE INSTRUCTIONS.  E Some of the restrictions involved when running OpenVMS on the Multia a> system include (but may well not be limited to) the following:  A   o The PCMCIA support was completely removed, because the Intel sB     chip on the Multia was not compatable with the Cirrus chip on      the Alphabook.  @     This means, of course, that you will not see and cannot use !     any PCMCIA cards on a Multia.5  B   o The Multia uses shared interrupts, and as a result, a special B     ZLXp-E series graphics device driver -- one that does not use A     interrupts -- is needed.  This driver is provided in the kit.       o The serial lines don't work.  ?   o If you have a Multia with a PCI slot, you can't use any PCIi"     card that requires interrupts.  @   o The SRM console on this system is very old and very fragile.D     (This SRM console was designed only and strictly for diagnostic ?     use, and was not particularly tested or used with OpenVMS.)n  B   o If things don't work for you, don't expect to see any OpenVMS 6     updates, nor SRM console updates, nor any support.   F The Multia images are not included on the OpenVMS Freeware V4.0 CD-ROMD kit, the kit that was distributed with OpenVMS V7.2.  (These images . became available after Freeware V4.0 shipped.)  ; Other sources of information for OpenVMS on Multia include:/  0   http://www.djesys.com/vms/hobbyist/multia.html2   http://www.djesys.com/vms/hobbyist/mltianot.html1   http://www.djesys.com/vms/hobbyist/support.htmln2   http://www.netbsd.org/Ports/alpha/multiafaq.html   					[Stephen Hoffman];                                         [David J. Dachtera]s  E OpenVMS Alpha is not supported on the AlphaPC 164LX and 164SX series,aC though there are folks that have gotten certain of the LX series toh@ load SRM and bootstrap OpenVMS.  (The Aspen Durango II variant.)@ One problem was reported: IDE bootstraps fail; SCSI is required.   Also see ALPHA13.i  < ------------------------------------------------------------B ALPHA9.  What is the least expensive system that will run OpenVMS?  ? The cheapest systems presently offered by Compaq that will run  C OpenVMS are the AlphaServer DS10 server and the AlphaStation XP900 eB workstation.  Other companies sell Alpha-powered systems and AlphaA motherboards, some of which will run (and can be purchased with) cB OpenVMS -- see the OpenVMS Software Product Description (SPD) for E details on the supported systems and configurations.  There are also SC many used AlphaStation, AlphaServer, and DEC 3000 models available )? which are quite suitable.  For more experienced OpenVMS system v@ managers, the (unsupported) Multia can bootstrap OpenVMS -- see  ALPHA8 for details.g  @ Depending on the OpenVMS version and configuration, the OpenVMS 3 Software Product Description (SPD) is available at:h  !   http://www.compaq.com/info/spd/ :   OpenVMS typically uses SPD 25.01.xx and/or SPD 41.87.xx.  F When purchasing a system, ensure that the system itself is supported, D that the system disk drive is supported or closely compatible, that B the CD-ROM drive is supported or is closely compatable and that itF also specifically supports 512 byte block transfers, and particularly D ensure that video controller is supported.  Use of supported Compaq H hardware will generally reduce the level of integration effort involved.  ; A CD-ROM drive is required for OpenVMS Alpha installations.v  7 CD-ROM drive compatibility information is available at:a.   http://sites.inka.de/pcde/dec-cdrom-list.txt 					[Stephen Hoffman]  < ------------------------------------------------------------< ALPHA10.  Where can I get more information on Alpha systems?  5 Compaq operates an AlphaServer information center at:o  $   http://www.compaq.com/alphaserver/  > Alpha Technical information and documentation is available at:  ,   http://www.support.compaq.com/alpha-tools/)      documentation/current/chip-docs.htmla  1   ftp://ftp.compaq.com/pub/products/alphaCPUdocs/t  .   ftp://ftp.digital.com/pub/DEC/Alpha/systems/  *   http://ftp.digital.com/pub/Digital/info/.      semiconductor/literature/dsc-library.html  #   Platform product documentation:  e#     http://www.compaq.com/info/spd/E     Alpha Systems Update:E1     http://www.compaq.com/alphaserver/fb_acu.htmle  / Information on Multia hardware is available at:e  2   http://www.netbsd.org/Ports/alpha/multiafaq.html   					[Stephen Hoffman]  A Information on current and future Alpha microprocessor designs is-$ also available from AlphaPowered at:  1   http://www.alphapowered.com/alpha_tomorrow.html-+   http://www.alphapowered.com/timeline.html .   http://www.alphapowered.com/ev7-and-ev8.html  = The NetBSD folks maintain some Alpha hardware information at:   /   http://www.netbsd.org/Ports/alpha/models.htmla    < ------------------------------------------------------------, ALPHA11.  What are the APB boot flag values?  ? The following flags are passed (via register R5) to the OpenVMSa@ Alpha primary bootstrap image APB.EXE.  These flags control the & particular behaviour of the bootstrap:     >>> BOOT -FL root,flags         bit      descriptionh9      ---   ----------------------------------------------   -       0    CONV      Conversational bootstrapt3       1    DEBUG     Load SYSTEM_DEBUG.EXE (XDELTA)rP       2    INIBPT    Stop at initial system breakpoints if bit 1 set (EXEC_INIT)>       3    DIAG      Diagnostic bootstrap (loads diagboot.exe)D       4    BOOBPT    Stop at bootstrap breakpoints (APB and Sysboot)F       5    NOHEADER  Secondary bootstrap does not have an image header(       6    NOTEST    Inhibit memory test8       7    SOLICIT   Prompt for secondary bootstrap file@       8    HALT      Halt before transfer to secondary bootstrap)       9    SHADOW    Boot from shadow setd'       10   ISL       LAD/LAST bootstrapo1       11   PALCHECK    Disable PAL rev check haltiA       12   DEBUG_BOOT  Transfer to intermediate primary bootstrapi+       13   CRDFAIL       Mark CRD pages badaA       14   ALIGN_FAULTS  Report unaligned data traps in bootstrapc@       15   REM_DEBUG   Allow remote high-level language debugger@       16   DBG_INIT    Enable verbose boot messages in EXEC_INITM       17   USER_MSGS   Enable subset of verbose boot messages (user messages)h0       18   RSM         Boot is controlled by RSM5       19   FOREIGN     Boot involves a "foreign" diskr  H   If you want to set the boot flags "permanently" use the SET BOOT_FLAGS   command, e.g.r            >>> SET BOOT_OSFLAGS 0,1    < ------------------------------------------------------------7 ALPHA12.  What are Alpha console environment variables?s  = Alpha systems have a variety of variables with values set up i; within the SRM system console.  These environment variablese; control the particular behaviour of the console program and/? the system hardware, the particular console interface presentedaB to the operating system, various default values for the operating < system bootstrap, and related control mechanisms -- in other> words, "the environment variables provide an easily extensible. mechanism for managing complex console state."  < The specific environment variables differ by platform and by: firmware version -- the baseline set is established by the Alpha Architecture:m  :   AUTO_ACTION ("BOOT", "HALT", "RESTART", any other value ;   assumed to be HALT),  BOOT_DEV, BOOTDEF_DEV, BOOTED_DEV,  8   BOOT_FILE, BOOTED_FILE, BOOT_OSFLAGS, BOOTED_OSFLAGS, :   BOOT_RESET ("ON", "OFF"), DUMP_DEV, ENABLE_AUDIT ("ON", 1   "OFF"), LICENSE, CHAR_SET, LANGUAGE, TTY_DEV.  t  = OpenVMS Galaxy firmware can add console environment variables-B beginning with such strings as LP_* and HP_*, and each particular > console implementation can (and often does) have various sorts9 of platform-specific extensions beyond these variables...d  C The contents of a core set of environment variables are accessable uB from OpenVMS using the f$getenv lexical and the sys$getenv system B service. (These calls are first documented in V7.2, but have been B around for quite a while.)  Access to arbitary console environment> variables is rather more involved, and not directly available.9                                         [Stephen Hoffman]   < ------------------------------------------------------------0 ALPHA13.  Will OpenVMS run on a NoName AXPpci33?  < Information on bootstrapping OpenVMS (using Multia files) on9 the (unsupported) NoName AXPpci33 module is available at:r  /   http://www.jyu.fi/~kujala/vms-in-axppci33.txte  2 Tips for using the Multia files with the AXPpci33:  ?   o You have to use the Multia kit and follow the directions in ?     ALPHA8, but do *not* load the Multia SRM firmware into the f@     AXPpci33.  Rather, download and use the latest firmware for :     the AXPpci33 from the Compaq firmware website instead.  (   o 64 MB memory is generally necessary.  A   o you cannot use any PCI cards, and if you plan on networking, w?     you need to find an ISA Ethernet card supported by OpenVMS.o  @   o When the AXPpci33 board bootstraps, it will dump some stuff A     like a crash dump, but it will continue and -- so far -- thisr)     hasn't caused any particular hassles.   C   o The system shutdown and reboot procedures do not work properly.l  A   o The serial console is reported to not work, though the serialnB     ports apparently do work.  The status of the parallel port is      unknown.  A   o Rumour has it that you have one of the AXPpci33 motherboards  ?     with the PS/2 mouse and keyboard connectors and a VGA card aE     (one that will work under DECwindows) and you can run DECwindows       on the system. h8                                       [Robert Alan Byer]  < ------------------------------------------------------------D ALPHA14.  How do I reload SRM firmware on a half-flash Alpha system?  I   Some of the AlphaStation series systems are "half-flash" boxes, meaning-G   only one set of firmware (SRM or AlphaBIOS) can be loaded in flash atdG   a time.  Getting back to the SRM firmware when AlphaBIOS (or ARC) is V'   loaded can be a little interesting...o  I   That said, this usually involves shuffling some files, and then gettingdH   into the AlphaBIOS firmware update sequence, and then entering "update   srm" at the apu-> prompt.   I   To shuffle the files, copy the target SRM firmware file (as200_v7_0.exelK   is current) to a blank, initialized, FAT-format floppy under the filenamet   A:\FWUPDATE.EXEr  G   From the AlphaBIOS Setup screen, select the Upgrade AlphaBIOS option.e5   Once the firmware update utility gets going, enter:t        Apu-> update srms  0            Answer "y" to the "Are you ready...?"        Apu-> quit   K   You've reloaded the flash.  Now powercycle the box to finish the process.h     Also see ALPHA6.  < ------------------------------------------------------------2 ALPHA15.  Will OpenVMS run on the Alpha XL series?  4   No.  OpenVMS does not support the Alpha XL series.  D   OpenVMS can not, will not, and does not bootstrap on the Alpha XL C   series.  The Alpha XL series was targeted for use (only) with thea)   Microsoft Windows NT operating system.t  D   For the list of boxes officially supported by OpenVMS, please see 1   the OpenVMS Software Product Description (SPD).X  #     http://www.compaq.com/info/spd/m<     OpenVMS typically uses SPD 25.01.xx and/or SPD 41.87.xx.  I   If you are very lucky, sometimes a particular unsupported Alpha box or oH   motherboard will resemble a supported box sufficiently closely and canE   thus mimic that system and bootstrap.  (No such family resemblancesiF   exist for the XL.)  If you are  exceedingly lucky, somebody here in H   OpenVMS Engineering will have put together a bootstrap kit -- such as H   that for the Multia.  (No Miata-like OpenVMS bootstrap kit exists for 
   the XL.)  < ------------------------------------------------------------G ALPHA16.  Describe Alpha instruction emulation and instruction subsets?   G   The Alpha architecture is upward- and downward-compatible, and newer eE   instructions are emulated on older platforms, for those cases wherenB   the compiler is explicitly requested to generate the newer Alpha   instructions.   F   In particular, OpenVMS Alpha V7.1 and later include the instruction C   emulation capabilities necessary for the execution of newer Alpha .   instructions on older Alpha microprocessors.  G   Alpha instructions are available in groups (or subsets).  Obviously, -C   there is the base instruction set that is available on all Alpha 6E   microprocessors.   Then, the following are the current instruction -E   extension groups (or subsets) that are available on some of various    recent Alpha microprocessors:        byte/word extension (BWX):-       LDBU, LDWU, SEXTB, SEXTW, STB, and STW.n  3     floating-point and square root extension (FIX):oH       FTOIS, FTOIT, ITOFF, ITOFS, ITOFT, SQRTF, SQRTG, SQRTS, and SQRTT.       count extension (CIX):       CTLZ, CTPOP, and  CTTZ.l        multi-media extension (MVI):F       MAXSB8, MAXSW4, MAXUB8, MAXUW4, MINSB8, MINSW4, MINUB8, MINUW4, +       PERR, PKLB, PKWB, UNPKBL, and UNPKBW.r  H   The typical instruction subset that provides the biggest win -- and ofH   course, your mileage may vary -- is typically the instruction set thatM   is provided by the EV56 and later; specifically, the byte-word instruction -4   subset.  To select this subset, use the following:    -      /ARCHITECTURE=EV56/OPTIMIZE=TUNE=GENERICh    D   The /ARCHITECTURE controls the maximum instruction subset that theF   compiler will generally use, while the /OPTIMIZE=TUNE controls both G   the instruction-level scheduling and also the instructions generated iJ   inside loops -- any code resulting from /OPTIMIZE=TUNE that is specific H   to an instruction subset will be generated only inside loops and will I   also be "protected" by an AMASK-based tesst that permits the execution /E   of the proper code for the particular current Alpha microprocessor.e    kI   Typically /OPTIMIZE=TUNE=GENERIC is the appropriate choice for tuning, eC   and the /ARCHITECTURE selects the minimum target architecture for ,   general use throughout the generated code.  J   Code generated for later architectures and instruction subsets will run I   on older Alpha systems due to the emulation, but if /ARCHITECTURE is a lI   significant benefit, then the emulation might be a performance penalty.   F   Please see the OpenVMS Ask The Wizard area for the source code of a H   (non-privileged) tool that looks at the instruction subsets available H   on the particular Alpha microprocessor that the tool is run on.  This H   tool demonstrates the use of the Alpha AMASK and IMPLVER instructions.  < ------------------------------------------------------------J ALPHA17.  What is the Accuracy of the Alpha Time of Year (BB_WATCH) Clock?  J   The specification for maximum clock drift in the Alpha hardware clock isL   50 ppm, that's less than +/-.000050 seconds of drift per second, less thanJ   +/-.000050 days of drift per day, or less than +/-.000050 years of driftJ   per year, etc.   (eg: An error of one second over a day-long interval isJ   roughly 11ppm, or 1000000/(24*60*60).)   Put another way, this is .005%,?   which is around 130 seconds per month or 26 minutes per year.   M   The software-maintained system time can drift more, primarily due to other  K   system activity.  Typical causes of drift include extensive high-IPL codedK   (soft memory errors, heavy activity at device IPLs, etc) that are causingb7   the processing of the clock interrupts to be blocked.r     Also see VAX8, TIME6.l  < ------------------------------------------------------------3 ALPHA18.  So how do I open up the DEC 3000 chassis?   @ After removing those two little screws, tilt the back end of the1 top shell upwards -- then you can remove the lid.1  :                                            [Felix Kreisel]  < ------------------------------------------------------------! ALPHA19.  What is byte swizzling?e  K "Swizzling" is the term used to describe the operation needed to do partialtN longword (i.e. byte or word) accesses to I/O space on those systems that don'tN support it directly. It involved shifting the offset into an address space by L 5 (or 7 for one older system), and ORing this into the base address. It thenF required the size of the operation to be ORed into the low order bits.  N That is, because the EV4 and EV5 CPUs did not bring bits 0 and 1 off the chip,O to do programmed I/O for bytes/words, the information on the size/offset of thehJ transfer was encoded into the address data. The data itself then had to beG shifted into the correct "byte lane" (i.e. its actual position within a 
 longword).  O The EV56 CPU supports the byte/word instructions however only some EV56 systems M support byte/word accesses to I/O space. Even on an EV56 system that supportsrM byte/word accesses to I/O space, the relevant OpenVMS routines do not supports byte/word access to I/O space.  M EV6 systems (with the exception of the AlphaServer GS60 and AlphaServer GS140tO series, for reasons of platform compatability) support a flat, byte addressable 
 I/O space.  N If a device driver uses CRAM or IOC$WRITE_IO/IOC$READ_IO, then OpenVMS will doF the right thing without changing the driver - OpenVMS will swizzle and unswizzle as needed.  O To use byte/word operations on MEMORY, you need to tell the compiler to use theeH EV56 or EV6 architecture (/ARCHITECTURE=EV56). Memory operations did notM swizzle, but the compiler would do long/quad access, and extract/insert byteswL as needed. Using /ARCHITECTURE=EV56 allows smaller, more efficient byte/word access logic to memory.y  M If the application is directly doing I/O space access across a range of AlphalM systems (like the graphics servers), then the driver will need to know how tooB do swizzling for old platforms, and byte access for new platforms.  G                                         [Fred Kleinsorge, Derek Garson]t  < ------------------------------------------------------------? ALPHA20.  What commands are available in the Alpha SRM console?o  F In addition to the normal BOOT commands and such (see ALPHA11 for someE details) and the normal contents of the console HELP text, operations-G such as I/O redirection and floppy disk access are possible at the SRM t console prompt:e  I 1. Format a FAT floppy, and insert it into the AlphaStation floppy drive.o  6 2. Perform the following at AlphaStation SRM Console :      >>> show * > env.dat9    >>> show conf > conf.datp%    >>> cat env.dat > fat:env.dat/dva0p'    >>> cat conf.dat > fat:conf.dat/dva0(  B 3. You may use the SRM "ls" to display the contents of the floppy.      >>> ls fat:env.dat/dva0    >>> ls fat:conf.dat/dva0s  @ 4. You can now transfer the FAT-format floppy to another system.  < ------------------------------------------------------------@ ALPHA21. How do I switch between AlphaBIOS/ARC and SRM consoles?  G The specific steps required vary by system.  You must first ensure thatnG the particular Alpha system is supported by OpenVMS (see the SPD), thattG all core I/O components (graphics, disk controllers, etc) in the system D are supported by OpenVMS (see the SPD), and that you have an OpenVMSG distribution, that you have the necessary license keys (PAKs), and thate+ you have the necessary SRM firmware loaded.m  F A typical sequence used for switching over from the AlphaBIOS graphics# console to the SRM console follows:5  3   1. Press <F2> to get to the AlphaBIOS setup menu.   #   2. Pick the "CMOS Setup..." item.s  9   3. Press <F6> to get to the "Advanced CMOS Setup" menu.   ?   4. Change the "Console Selection" to "OpenVMS Console (SRM)".V  ;   5. Press <F10>, <F10>, then <Enter> to save your changes.i     6. Power-cycle the system.  I Most Alpha systems support loading both the AlphaBIOS/ARC console and the-F SRM console at the same time, but systems such as the AlphaStation 255D are "half-flash" systems and do not support the presence of both theE AlphaBIOS/ARC and SRM console firmware at the same time.  If you havehG a "half-flash" system, you must load the SRM firmware from floppy, fromwD a network download, or from a firmware CD-ROM.  Following the normalE AlphaBIOS or ARC firmware update sequence to the APU prompt, and then/B explictly select the target console.  In other words, power up theE system to the AlphaBIOS or ARC console, use the supplementary optionslC to select the installation of new firmware (typically from CD-ROM),E? and then rather than using a sequence which updates the currente	 firmware:m       Apu-> update
       -or-     Apu-> update ARC     Apu-> verify     Apu-> quit     Power-cycle the system  @ Use the following sequence to specifically update (and load) SRM, from AlphaBIOS/ARC on a "half-flash" system:       Apu-> update SRM     Apu-> verify     Apu-> quit     Power-cycle the system  @ Use the following sequence to specifically update (and load) the8 AlphaBIOS/ARC console from SRM on a "half-flash" system:       >>> b -fl 0,A0 ddcuw$     BOOTFILE: firmware_boot_file.exe       Apu-> update ARC     Apu-> verify     Apu-> quit     Power-cycle the system  A Once you have the SRM loaded, you can directly install OpenVMS ori= Tru64 UNIX on the system.  Do not allow Windows NT to write a.@ "harmless" signature to any disk used by OpenVMS, Tru64 UNIX, orA Linux, as this will clobber a key part of the disk.  (On OpenVMS,-B you can generally recover from this "harmless" action by using the WRITEBOOT tool.)  D If you have a "full-flash" system and want to select the SRM consoleD from the AlphaBIOS or ARC console environment, select the "Switch toI OpenVMS or Tru64 UNIX console" item from the "set up the system" submenu. D Then power-cycle the system.  If you have a "full-flash" system withB the SRM console and want to select AlphaBIOS/ARC, use the command:      >>> set os_type NTI   and power-cycle the system.S  C For information on acquiring firmware, see ALPHA6.  For information E on OpenVMS license PAKs (for hobbyist use) see VMS9.  For informations on the Multia, see ALPHA8.  C Information on enabling and using the failsafe firmware loader for hE various systems -- this tool is available only on some of the variousiF Alpha platforms -- is available in the hardware documentation for the G system.  This tool is used/needed when the firmware has been corrupted,r and cannot load new firmware.g  F The full list of AlphaBIOS key sequences -- these sequences are neededE when using an LK-series keyboard with AlphaBIOS, as AlphaBIOS expectss a PC-style keyboard:            F1   Ctrl/A          F2   Ctrl/B          F3   Ctrl/C          F4   Ctrl/D          F5   Ctrl/E          F6   Ctrl/F          F7   Ctrl/P          F8   Ctrl/R          F9   Ctrl/T         F10   Ctrl/U      Insert   Ctrl/V      Delete   Ctrl/W   Backspace   Ctrl/H      Escape   Ctrl/[      Return   Ctrl/M    LineFeed   Ctrl/J%    (Plus) +   upselect (some systems)l'   (Minus) -   downselect (some systems)l         TAB   down arrow    SHIFT+TAB  up arrow  < ------------------------------------------------------------@ ALPHA22.  OpenVMS on the Personal Workstation -a and -au series?  F Though OpenVMS is not supported on the Personal Workstation -a series F platforms, OpenVMS might or might not bootstrap on the platform.  (If H you attempt this, you must ensure that all graphics and I/O controllers ( in the system are supported by OpenVMS.)  < ------------------------------------------------------------9 ALPHA23.  OpenVMS and Personal Workstation IDE bootstrap?   C OpenVMS will boot and is supported on the Personal Workstation -au OC series platforms, though OpenVMS will require a SCSI CD-ROM if the FC Intel Saturn I/O (SIO) IDE chip is present in the configuration -- AE only the Cypress IDE controller chip is supported by OpenVMS for IDE n bootstraps.r  = If you have an -au series system, you can determine which IDE , chip you have using the SRM console command:     SHOW CONFIGURATION  B If you see "Cypress PCI Peripheral Controller", you can bootstrap A OpenVMS from IDE storage.  If you see "Intel SIO 82378", you williC need to use and bootstrap from SCSI.  (A procedure to load DQDRIVERe@ on the Intel SIO -- once the system has bootstrapped from a SCSIC device -- is expected to be included as part of the contents of thes/ DQDRIVER directory on Freeware V5.0 and later.)t  < ------------------------------------------------------------B ALPHA24.  Which terminal device name is assigned to the COM ports?  >   COM2 is normally TTA0:.  COM1 is normally TTB0: if the AlphaA   workstation is booted with the SRM console environment variablen@   set to graphics, and is OPA0: if the console is set to serial.  < ------------------------------------------------------------8 VAX1.   Please explain the back panel of the MicroVAX II  J The MicroVAX-series console bulkhead was used with the KA630, KA650, KA655 processors.l  B There are three controls on the console bulkhead of these systems:  *   Triangle-in-circle-paddle: halt enable. -     dot-in-circle: halt (<break>) is enabled,.-                    and auto-boot is disabled. 2     dot-not-in-circle: halt (<break>) is disabled,,                    and auto-boot is enabled.  5   Three-position-rotary: power-up bootstrap behaviour3     arrow: normal operation.      face: language inquiry mode.)     t-in-circle: infinite self-test loop.t  4   Eight-position-rotary: console baud rate selection4     select the required baud rate; read at power-up.  pJ There are several different bulkheads involved, including one for the BA23E and BA123 enclosures, and one for the S-box (BA2xx) series enclosure. L The console bulkheads typically used either the MMJ serial line connection, H or the MicroVAX DB9 (not the PC DB9 pinout), please see the descriptions@ of these in section WIRES1.  For available adapters, see WIRES2.  M Also present on the console bulkhead is a self-test indicator: a single-digit K LED display. This matches the final part of the countdown displayed on the  N console or workstation, and can be used by a service organization to determineM the nature of a processor problem.  The particular countdown sequence varies eM by processor type, consult the hardware or owner's manual for the processor, SG or contact the local hardware service organization for information the sM self-test sequence for a particular processor module. Note that self-tests 2,eM 1 and 0 are associated with the transfer of control from the console program e" to the (booting) operating system.9                                         [Stephen Hoffman]2  < ------------------------------------------------------------< VAX2.   What is the layout of the VAX floating point format?  K The VAX floating point format is derived from one of the PDP-11 FP formats,rH which helps explain its strange layout.  There are four formats defined:H F 32-bit single-precision, D and G 64-bit double-precision and H 128-bitI quadruple precision.  For all formats, the lowest addressed 16-bit "word"oF contains the sign and exponent (and for other than H, some of the mostK significant fraction bits).  Each successive higher-addressed word containseN the next 16 lesser-significant fraction bits.  Bit 15 of the first word is theF sign, 1 for negative, 0 for positive.  Zero is represented by a biasedM exponent value of zero and a sign of zero; the fraction bits are ignored (buthJ on Alpha, non-zero fraction bits in a zero value cause an error.)  A valueK with biased exponent zero and sign bit 1 is a "reserved operand" - touching I it causes an error - fraction bits are ignored.  There are no minus zero,e% infinity, denormalized or NaN values.u  M For all formats, the fraction is normalized and the radix point assumed to becJ to the left of the MSB, hence 0.5 <= f < 1.0.  The MSB, always being 1, isK not stored.  The binary exponent is stored with a bias varying with type ine' bits 14:n of the lowest-addressed word.   L   Type    Exponent bits    Exponent bias    Fraction bits (including hidden)L   ==========================================================================4    F           8                128               244    D           8                128               564    G          11               1024               534    H          15              16384              113  D The layout for D is identical to that for F except for 32 additional fraction bits.  J Example:  +1.5 in F float is hex 000040C0 (fraction of .11[base 2], biased exponent of 129) 					[Steve Lionel]o  < ------------------------------------------------------------5 VAX3.   Where can I find more info about VAX systems?n  " Compaq runs a VAX "InfoCenter" at:  (   http://www.compaq.com/alphaserver/vax/  1 Jim Agnew maintains a MicroVAX/VAXstation FAQ at:   3   http://anacin.nsc.vcu.edu/~jim/mvax/mvax_faq.htmli  " The VAXstation 3100 Owner's Guide:  7   http://www.whiteice.com/~williamwebb/intro/DOC-i.htmlp  ; A field guide to PDP-11 (and VAX) Q-bus and UNIBUS modules D can be found at:  8   http://metalab.unc.edu//pub/academic/computer-science/+     history/pdp-11/hardware/field-guide.txtI  9 Various VAX historical information (also see VMS1) can bee	 found at::  +   http://telnet.hu/hamster/vax/e_index.htmle  < ------------------------------------------------------------? VAX4.   Where can I find information on NetBSD for VAX systems?   / Gunnar Helliesen maintains a NetBSD VAX FAQ at:r   http://vaxine.bitcon.no/  < ------------------------------------------------------------H VAX5.   What system disk size limit on the MicroVAX and VAXstation 3100?  M System disks larger than 1.073 gigabytes (GB) -- 1fffff hexidecimal blocks -- L are not supported on any member of the VAXstation 3100 series and on certainH older members of the MicroVAX 3100 series, and are not reliable on theseJ affected systems.  (See below to identify the affected systems -- the moreE recent members of the MicroVAX 3100 series systems are NOT affected.)i  M Various of the SCSI commands used by the boot drivers imbedded in the consolerI PROM on all members of the VAXstation 3100 series use "Group 0" commands,eI which allow a 21 bit block number field, which allows access to the firstuJ 1fffff hexidecimal blocks of a disk.  Any disk references past 1fffff willL wrap -- this wrapping behaviour can be of particular interest when writing aN system crashdump file, as this can potentially lead to system disk corruptionsA should any part of the crashdump file be located beyond 1.073 GB.u  N More recent systems and console PROMs use "Group 1" SCSI commands, which allow a 32 bit block number field.  L There was a similar limitation among the oldest of the MicroVAX 3100 series,M but a console boot PROM was phased into production and was made available for I field retrofits -- this PROM upgrade allows the use of the "Group 1" SCSIaN commands, and thus larger system disks.  There was no similar PROM upgrade for the VAXstation 3100 series.-  ( Systems that are affected by this limit:G   o VAXstation 3100 series, all members.  No PROM upgrade is available.BB   o MicroVAX 3100 models 10 and 20.  No PROM upgrade is available.E   o MicroVAX 3100 models 10e and 20e.  Only systems with console VMB  B     versions prior to V6.4 are affected.  A PROM upgrade for these-     specific systems is (was once) available.e  	 Also see:g7   http://www.whiteice.com/~williamwebb/intro/DOC-i.htmlo   Also see FILE5.0 						[Stephen Hoffman]o  < ------------------------------------------------------------  VAX6.  replaced by TIME section.  < ------------------------------------------------------------) VAX7.  What are the VMB boot flag values?s  ? The following flags are passed (via register R5) to the OpenVMS,> VAX primary bootstrap image VMB.EXE.  These flags control the & particular behaviour of the bootstrap:  > The exact syntax is console-specific, recent VAX consoles tend to use the following:-     >>> BOOT/R5:flagso  @   Bit     Meaning                                               @   ---     -------                                               N                                                                               @    0      RPB$V_CONV                                            @           Conversational boot. At various points in the         @           system boot procedure, the bootstrap code             @           solicits parameter and other input from the           @           console terminal.  If the DIAG is also on then        @           the diagnostic supervisor should enter "MENU"         @           mode and prompt user for the devices to test.           @    1      RPB$V_DEBUG                                           @           Debug.  If this flag is set, VMS maps the code        @           for the XDELTA debugger into the system page          @           tables of the running system.                         @                                                                 @    2      RPB$V_INIBPT                                          @           Initial breakpoint. If RPB$V_DEBUG is set, VMS        @           executes a BPT instruction immediately after          @           enabling mapping.                                     ?                                                                h@    3      RPB$V_BBLOCK                                          @           Secondary boot from the boot block.  Secondary        @           bootstrap is a single 512-byte block, whose LBN       @           is specified in R4.                                   @                                                                 @    4      RPB$V_DIAG                                            @           Diagnostic boot.  Secondary bootstrap is image        @           called [SYSMAINT]DIAGBOOT.EXE.                        @                                                                 @    5      RPB$V_BOOBPT                                          @           Bootstrap breakpoint. Stops the primary and           @           secondary bootstraps with a breakpoint                @           instruction before testing memory.                      @    6      RPB$V_HEADER                                          @           Image header. Takes the transfer address of the       @           secondary bootstrap image from that file's            @           image header.  If RPB$V_HEADER is not set,            @           transfers control to the first byte of the            @           secondary boot file.                                  @                                                                 @    7      RPB$V_NOTEST                                          @           Memory test inhibit. Sets a bit in the PFN bit        @           map for each page of memory present.  Does not        @           test the memory.                                      @                                                                 @    8      RPB$V_SOLICT                                          @           File name. VMB prompts for the name of a              @           secondary bootstrap file.                             @                                                                 @    9      RPB$V_HALT                                            @           Halt before transfer.  Executes a HALT                @           instruction before transferring control               @           to the secondary bootstrap.                           @                                                                 @   10      RPB$V_NOPFND                                          @           No PFN deletion (not implemented; intended to         @           tell VMB not to read a file from the boot device      @           that identifies bad or reserved memory pages,         @           so that VMB does not mark these pages as valid        @           in the PFN bitmap).                                   @                                                                 @   11      RPB$V_MPM                                             @           Specifies that multi-port memory is to be used        @           for the total EXEC memory requirement.  No local      @           memory is to be used.  This is for tightly-coupled    @           multi-processing.  If the DIAG is also on, then       @           the diagnostic supervisor enters "AUTOTEST" mode.     @                                                                 @   12      RPB$V_USEMPM                                          @           Specifies that multi-port memory should be used in    @           addition to local memory, as though both were one     @           single pool of pages.                                 @                                                                 @   13      RPB$V_MEMTEST                                         @           Specifies that a more extensive algorithm be used     @           when testing main memory for hardware                 @           uncorrectable (RDS) errors.                           @                                                                 @   14      RPB$V_FINDMEM                                         @           Requests use of MA780 memory if MS780 is              @           insufficient for booting.  Used for 11/782            @           installations.                                        @                                                                 @   <31:28> RPB$V_TOPSYS                                          @           Specifies the top level directory number for          @           system disks with multiple systems.                     y< ------------------------------------------------------------A VAX8.   What is the Accuracy of VAX the Time of Year (TOY) Clock?   A   The VAX Time-Of-Year (TOY) clock (used to save the time over a lA   reboot or power failure) is specified as having an accuracy of I;   .0025%.  This is a drift of roughly 65 seconds per month.   C   The VAX Interval Time is used to keep the running time, and this nF   has a specified accuracy of .01%.  This is a drift of approximately    8.64 seconds per day.e  E   Any high-IPL activity can interfere with the IPL 22 or IPL 24 (this-D   depends on the VAX implementation) clock interrupts -- activities B   such as extensive device driver interrupts or memory errors are    known to slow the clock.     Also see ALPHA17, TIME6.  < ------------------------------------------------------------> VAX9.   Which serial port is the console on the MicroVAX 3100?  G Just to keep life interesting, the MicroVAX 3100 has some "interesting"oA console ports behaviours based on the setting of the BREAK enablenC switch.  When the console is not enabled to respond to BREAK, MMJ-1aD is the console port.  MMJ-3 will (confusingly) output the results ofC the selftest in parallel with MMJ-1. When the console is enabled tor@ respond to BREAK, MMJ-3 becomes the console port, and MMJ-1 willD (confusingly) output the results of selftest in parallel with MMJ-3.  < ------------------------------------------------------------> VAX10.  How can I set up an alternate console on a VAXstation?  A Most VAXstation systems have a switch -- often labeled S3 -- thatM6 enables one of the serial lines as the system console.  $ Also see ALPHA7, DECW13, and MGMT22.  < ------------------------------------------------------------/ VAX11.  What are the VAX processor (CPU) codes?-      CPU:    Platform:    -----   ---------)    KA41-A : MicroVAX 3100 Model 10 and 20V*    KA41-B : VAXserver 3100 Model 10 and 20    KA41-C : InfoServer+    KA41-D : MicroVAX 3100 Model 10e and 20ee,    KA41-E : VAXserver 3100 Model 10e and 20e+    KA42-A : VAXstation 3100 Model 30 and 40 +    KA42-B : VAXstation 3100 Model 38 and 48-$    KA43-A : VAXstation 3100 Model 76)    KA45   : MicroVAX 3100 Model 30 and 40 $    KA46   : VAXstation 4000 Model 60"    KA47   : MicroVAX 3100 Model 80    KA48   : VAXstation 4000 VLCO(    KA49-A : VAXstation 4000 Model 90/90A$    KA49-B : VAXstation 4000 Model 95$    KA49-C : VAXstation 4000 Model 96"    KA50   : MicroVAX 3100 Model 90"    KA51   : MicroVAX 3100 Model 95    KA52   : VAX 4000 Model 100    KA53   : VAX 4000 Model 105    KA54   : VAX 4000 Model 106"    KA55   : MicroVAX 3100 Model 85"    KA56   : MicroVAX 3100 Model 96    KA57   : VAX 4000 Model 108"    KA58   : MicroVAX 3100 Model 88"    KA59   : MicroVAX 3100 Model 98    KA85   : VAX 8500    KA86   : VAX 8600    KA88   : VAX 8800&    KA600  : VAX 4000-50 (aka VAXbrick)/    KA610  : MicroVAX I, VAXstation I (aka KD32)t    KA620  : rtVAX (VAXeln)    KA62A  : VAX 6000-200    KA62B  : VAX 6000-300&    KA630  : MicroVAX II, VAXstation II(    KA640  : MicroVAX 3300, MicroVAX 3400G    KA650  : VAXstation 3200, MicroVAX 3500, MicroVAX 3600, MicroVAX III     KA64A  : VAX 6000-4007    KA655  : MicroVAX 3800, MicroVAX 3900, MicroVAX III+T    KA65A  : VAX 6000-500'    KA660  : VAX 4000-200, VAX 4 upgrader    KA66A  : VAX 6000-600    KA670  : VAX 4000-300    KA675  : VAX 4000-400    KA680  : VAX 4000-500    KA681  : VAX 4000-500A-    KA690  : VAX 4000-600    KA691  : VAX 4000-605A     KA692  : VAX 4000-700Ai    KA693  : VAX 4000-605Ae    KA694  : VAX 4000-705A     KA730  : VAX-11/730    KA750  : VAX-11/750"    KA780  : VAX-11/780, VAX-11/782    KA785  : VAX-11/785    KA7AA  : VAX 7000-600    KA7AB  : VAX 7000-700    KA7AC  : VAX 7000-800    KA800  : VAXrta    KA820  : VAX 8200, VAX 8300    KA825  : VAX 8250, VAX 8350    KA865  : VAX 86506                                      [Antonio Carlini]  < ------------------------------------------------------------B SUPP1.  Where can I get software and hardware support information?  D Contact Compaq Customer Support.  Services and information, manuals,A guides, downloads, and various other information is available at:h      http://www.compaq.com/support/  : Various hardware and system documentation is available at:  ?   http://www.compaq.com/support/techpubs/user_reference_guides/d1   http://www.adenzel.demon.nl/vaxes/microvax3100/i2   http://www.adenzel.demon.nl/vaxes/infoserver150/  C TSM (Terminal Server Manager), DEChub, DECserver, etc. information:a  9   http://www.compaq.com/support/digital_networks_archive/i      < ------------------------------------------------------------E SUPP2.  Where can I get hardware self-maintenance support assistance?i  C The Compaq Assisted Services program is available to customers thatoH wish to maintain their own systems (self-maintenance), but that require F some assistance with acquiring hardware diagnostics, hardware manuals,# and with hardware swaps and spares:c  %   http://www.digital.com/info/DAHOME/f%   http://www.digital.com/DAS-Catalog/o  < ------------------------------------------------------------G SUPP3. Why does my system halt when I power-cycle the console terminal?a  <   Various VAX and Alpha consoles are designed to process the.   BREAK signal, treating it as a HALT request.  @   A BREAK is a deliberately-generated serial line framing error.  F   When a serial line device such as a terminal powers up (or sometimesD   when powering down) it can generate framing errors.  These framing2   errors are indistingushable from a BREAK signal.  ?   When a BREAK is received on a serial line console for varioussB   VAX systems -- including most VAXstation, MicroVAX, and VAX 4000A   series -- it is typically interpreted as a HALT.  Alpha systemsnC   will also often process a BREAK in a similar fashion, halting then	   system.t  @   There is no uniform or generally-available way to disable thisA   behaviour on every VAX or Alpha system.  On some systems, BREAK A   processing can be disabled in favor of [CTRL/P], or [CTRL/P] iss%   the only way to halt the processor.f  C   The most common way to avoid these halts is to disable the serialoA   line console or to simply not power-cycle the console terminal.uG   There is certain important system state information that is displayediC   only on the console, OpenVMS expects to always have access to thes   system console.      Also see MGMT5.o  < ------------------------------------------------------------? SUPP4.  Can I reuse old keyboards, mice and monitors with a PC?   F Older Compaq keyboards (those with the DIGITAL logo and the RJ modularF jacks), older Compaq mice (those with the DIGITAL logo and with the RJI modular jacks, or with a DIN connector with pins in a configuration other=D than the PC-standard DIN connector pin orientation), and older videoD monitors (with RGB synch-on-green video signaling) all use signalingJ formats and/or communications protocols that differ from the PC standards,H and are not (easily) interchangable nor (easily) compatible with typicalK PC peripheral device controllers.  LK201, LK401, VSXXX, VR260, VR290, etc.,f& are incompatible with most PC systems.  F Newer Compaq keyboards (those with with PC-style DIN plugs, and CompaqF or DIGITAL logo), newer Compaq mice (with PC-pin DIN plugs, and CompaqB or DIGITAL logo), and newer video monitors (multi-synch) are oftenE interchangeable with "industry standard" PC systems, and can often bepH used with most PC peripheral device controllers. LK461, LK471, PC7XS-CA,8 VRC16, VRC21, etc., are compatible with most PC systems.  K Rule of thumb: if the peripheral device component was sold for use with theaK DEC 2000 (DECpc 150 AXP), an AlphaServer series, an AlphaStation series, or E more recent Alpha system, it will probably  work with a PC peripheralfH controller.  If the peripheral device component was sold for use with anJ VT420 or older terminal, most VAX, most VAXstation, and most Alpha systemsJ with names in the format `DEC <four-digit-number>', it probably won't work on a PC.  N Note that the above is a general guideline, and should not be read to indicateM that any particular peripheral device will or will not work in any particular N configuration, save for those specific configurations the device is explicitly
 supported in.19                                         [Stephen Hoffman]e    K Software Integrators sells a video adapter card called Gemini P1 which will0I drive many of the older Compaq (DIGITAL-logo) fixed-frequency monitors one a PC system:     http://www.si87.com/    J The Digital part number 29-32540-01 converts the output from the RGB cableJ (3 BNC, synch-on-green) that comes with the VAXstation 3100 and VAXstation) 4000 series to a female SVGA D connector.r  ? This will allow PC Multisync monitors with the needed frequencylC specifications to be used with the VAXstations.  It may work with ad> VAXstation 2000 series, but I have not tried that combination.<                                           [John E. Malmberg]  I The protocol definition for the old DIGITAL keyboard and mouse interfaceshJ is buried at the back of the QDSS section in the old VAXstation II manual,G specifically, in the back of the VCB02 Video Subsystem Technical Manual F (EK-104AA-TM).  The keyboard wiring and protocol is in appendix B, andE occupies circa 44 pages.  The mouse is in appendix C, circa 12 pages.i     Also see SUPP5  < ------------------------------------------------------------A SUPP5.  Which video monitor works with which graphics controller?m  K   To determine the answer to the "will this monitor work with this graphics F   controller?" question, please first locate the resolution(s) and theI   frequencies that are possible/supported at both ends of the video cable H   (on the monitor and the graphics controller, in other words), and thenG   determine if there are any matching settings available.  If there are.L   multiple matches, you will need to determine which one is most appropriate   for your needs./  M   You will also need to determine if the video monitor or graphics controllerhL   requires the 3 BNC signaling with the synchronization signals on the greenM   wire, or the 5 BNC signalling common on many PCs, or other connections such-G   as the DB15 video connector or USB connector used on various systems.w  I   If there are no matches, you will likely need to change the hardware at (   one or both ends of the "video cable".  J   The refresh frequencies for many devices have been posted to comp.os.vmsG   and/or other newsgroups.  Search the archives for details.  Also see:o       http://www.repairfaq.org/ "     http://www.mirage-mmc.com/faq/H     http://www.geocities.com/SiliconValley/Foothills/4467/fixedsync.html2     http://saturn.tlug.org/sunstuff/ffmonitor.html/     http://hawks.ha.md.us/hardware/monitor.html      Also see SUPP4.   < ------------------------------------------------------------8 SUPP6.  Where can I get information on storage hardware?  < Information on various Compaq OpenVMS and other disk storage; hardware and controllers, and related technical information / on SCSI, device jumpers, etc., is available at:o     http://theref.aquascape.com/  < ------------------------------------------------------------< SUPP7.  Problem - My LK401 keyboard unexpectedly autorepeats  # There are several modes of failure:f  K a) Pressing 2 and 3 keys at the same time causes one key to autorepeat when L    released.  Check the hardware revision level printed on the bottom of theL    keyboard.  If the revision level is C01, the keyboard firmware is broken.K    Call field service to replace the keyboard with any revision level other     than C01.  I b) Pressing certain keys is always broken.  Typical sympypoms are: deleterN    always causes a autorepeat, return needs to be pressed twice, etc.  This isI    frequently caused by having keys depressed while the keyboard is being L    initialized.  Pressing ^F2 several times or unplugging and replugging theK    keyboard frequently fix this problem.  There is a patch available to fixoJ    this problem [contact the CSC for information - a CSCPAT number will be'    included here when available. - Ed.]   L c) A key that was working spontaneously stops working correctly. This may beN    either (a) or (b) or it may be bad firmware.  Ensure that you have the mostI    recent firmware installed on your CPU.  An old version of the DEC 3000.4    firmware had a bug that could cause this symptom.9                                         [Fred Kleinsorge]O  < ------------------------------------------------------------I SUPP8.  Problem - My LK411 sends the wrong keycodes or some keys are deadt  N Check the firmware revision on the keyboard.  Hardware revision B01 introducedM an incompatability with the device driver which causes the keyboard to not be F recognized correctly.  There is a patch available to fix this problem:H [AXPDRIV06_061] - the fix is also included in OpenVMS V6.2.  The rev A015 keyboard, and the LK450 should work without problems. 9                                         [Fred Kleinsorge]e1                                         [inazu_k]   < ------------------------------------------------------------= SUPP9.  Which DE500 variant works with which OpenVMS version?   E   Ensure you have a version of the Alpha SRM console with support for H   the DE500 series device.  Apply ALL mandatory ECO kits for the OpenVMSF   version in use, and also apply the CLUSIO, ALPBOOT, and ALPLAN kits,:   and apply any available ALPCPU ECO kit for the platform.  
   DE500-XA'    auto-detection, no auto-negotiation, @    OpenVMS V6.2-1H1 and ALPBOOT ECO, also V7.0 and later and ECO,    Device hardware id 02000011 and 02000012.$    Component part number 54-24187-01  
   DE500-AA$    auto-detection, auto-negotiation,F    OpenVMS V6.2 and ALPBOOT and ALPLAN ECOs, or V7.1 and later and ECO,    Device hardware id 02000020 and 20000022.$    Component part number 54-24502-01  
   DE500-BA$    auto-detection, auto-negotiation,C    OpenVMS V6.2-1H3 and CLUSIO, ALPBOOT, ALPLAN and ALPCPU ECOs, or       V7.1-1H1 or later and ECO. =    Device hardware id 02000030 (check connector, vs DE500-FA) -      (other values on old Alpha SRM firmware) $    Component part number 54-24602-01  -   DE500-FA (100 megabit fibre optic Ethernet)e     OpenVMS V7.1-1H1 and later>     Device hardware id 02000030 (check connector, vs DE500-BA)7       (other values possible on old Alpha SRM firmware)s%     Component part number 54-24899-01t  G   To check the DE500 device hardware id from OpenVMS, use the following 
   command:       $ ANALYZE/SYSTEM     SDA> SHOW LAN/DEVICE=EWcu:  &   The "hardware id" will be displayed.  H   To set the DE500 speed via the Alpha SRM console environment variable:  &    EWx0_MODE setting           Meaning?    --------------------------  -------------------------------- 9    Twisted-Pair                10 Mbit/sec, nofull_duplex 7    Full Duplex, Twisted-Pair   10 Mbit/sec, full_duplexE9    AUI                         10 Mbit/sec, nofull_duplex 9    BNC                         10 Mbit/sec, nofull_duplex :    Fast                        100 Mbit/sec, nofull_duplex8    FastFD (Full Duplex)        100 Mbit/sec, full_duplex=    Auto-Negotiate              Negotiation with remote device   0   To override the console setting and use LANCP:       $ RUN SYS$SYSTEM:LANCP      LANCP> SET DEV EWA0/SPEED=10-     LANCP> SET DEV EWA0/SPEED=100/full_duplex   K   Fast Ethernet (100Base, 100 megabit) controllers such as the DE500 series M   have a pair of connections available -- while traditional Ethernet (10Base,rH   10 megabit) is inherently a half-duplex protocol, Fast Ethernet can beJ   configured to use one or both of the available connections, depending onK   the controller.  Fast Ethernet can thus be half- or full-duplex depending8I   on the configuration and the capabilities of the network controller and F   the Ethernet network plant.  Some Fast Ethernet controllers can alsoJ   operate at traditional Ethernet speeds, these controllers are thus often,   refered to as 10/100 Ethernet controllers.    < ------------------------------------------------------------< SCSI1.  Are the 2X-KZPCA-AA and SN-KZPCA-AA LVD Ultra2 SCSI?  3   Both of these controllers are Ultra2 low-voltage -&   differential (LVD) SCSI controllers.  < ------------------------------------------------------------, SCSI2.  Resolving DRVERR fatal device error?  =   If this is on an OpenVMS version prior to V6.2, please see  ;   the AWRE and ARRE information included in section MISC21.c    < ------------------------------------------------------------- WIRES1. Looking for connector wiring pinouts?a   DECconnect DEC-423 MMJ pinout:     1: Data Terminal Ready (DTR)   2: Transmit (TXD)L   3: Transmit Ground (TXD-)t   4: Receive Ground (RXD-)   5: Receive (RXD)   6: Data Set Ready (DSR)r      +------------------+h    | 1  2  3  4  5  6 |e    +------------+    ++r                 +____+    / The PC-compatible DB9 connector pinout follows:-     1: Data Carrier Detect (DCD)   2: Received Data   3: Transmit Data   4: Data Terminal Ready (DTR)   5: Ground    6: Data Set Ready (DSR)n   7: Request To Send (RTS)   8: Clear To Send
   9: floatinga  C The MicroVAX DB9 console connector pinout predates the PC-style DB9sD pinout, and uses a then-common (older) standard pinout, and uses the# following EIA-232-standard signals:e     1: Protective Ground   2: Transmited Data   3: Received Data   4: Request To Send (RTS)   5: Data Terminal Ready (DTR)   6: Data Set Ready (DSR)g   7: Signal Ground8   8: Shorted to pin 9 on MicroVAX and VAXstation 2000...3   9:    ...series systems, otherwise left floating.   E   When pin 8 is shorted to pin 9, this is a BCC08 (or variant) cable.   = The BC16E-nn (where -nn indicates the cable length) cable keyf< impliicitly "flips over" (crosses-over) the signal wires, so1 all DECconnect MMJ connectors are wired the same.-  
            //-:            ----                                       ----:            |  |---------------------------------------|  |:            ----                                       ----:                                                         \\  0 The BC16-E-nn cross-over wiring looks like this:  ;             Terminal                                   Host4:             MMJ                                        MMJ  =          DTR 1 --->-------------->----------------->--- 6 DSRd=          TXD 2 --->-------------->----------------->--- 5 RXDX9              3 ---------------------------------------- 4 9              4 ---------------------------------------- 3 =          RXD 5 ---<--------------<-----------------<--- 2 TXDr=          DSR 6 ---<--------------<-----------------<--- 1 DTR      The BN24H looks like this:            MMJ       RJ45K             1---------86           2---------23           3---------1            4---------36           5---------6M           6---------7i   The BN24J looks like this:            MMJ       RJ45              1---------7K           2---------68           3---------30           4---------1X           5---------2r           6---------8k  	 Also see:K  4  http://www.openvms.compaq.com/wizard/padapters.html%  http://www.airborn.com.au/rs232.htmlX)  For adapters and connectors, see WIRES2.0  9                                         [Stephen Hoffman] 7                                         [Mike Thompson] 6                                         [William Webb]  < ------------------------------------------------------------: WIRES2. What connectors and wiring adapters are available?    J The H8571-B converts the (non-2000-series) MicroVAX DB9 to MMJ DECconnect.G The MicroVAX 2000 and VAXstation 2000 requires a BCC08 cable (which has0C the 8-9 short, see WIRES1) and the H8571-D for use with DECconnect.   G More recent Compaq (Compaq or DIGITAL logo) systems will use either the I DECconnect MMJ wiring or (on all recent system designs) the PC-compatible  DB9 pinout.    DECconnect MMJ adapters:  3     Part:      Converts BC16E MMJ male to fit into:   2     H8571-C  25 pin DSUB Female to MMJ, Unfiltered.     H8571-D  EIA232 25 pin male (modem-wired) 0     H8571-E  25 pin DSUB Female to MMJ, Filtered/     H8571-J  PC/AT 9 pin male (PC serial port) p4     H8572-0  BC16E MMJ double-female (MMJ extender) +     H8575-A  EIA232 25 pin female (common) o5     H8575-B  EIA232 9 pin male (MicroVAX II console) h4     H8575-D  25 Pin to MMJ W/EOS and ESD Protection *     H8577-AA 6 pin Female MMJ to 8 pin MJ 4     BC16E-** MMJ cable, available in various lengths    D Numerous additional adapters and cables are available from the _OPENK DECconnect Building Wiring Components and Applications Catalog_, as well as,' descriptions of the above-listed parts.   J The H8571-A and H8575-A are MMJ to DB25 (female) and are wired as follows:  	 Also see:-4  http://www.openvms.compaq.com/wizard/padapters.html  L Jameco offers a USB-A to PS/2 Mini DIN 6 Adapter (as part 168751), for thoseC folks wishing to (try to) use PS/2 Keyboards via USB-A connections.o  9                                         [Stephen Hoffman]a6                                         [Eric Dittman]  < ------------------------------------------------------------2 WIRES3. What is flow control and how does it work?  % XON/XOFF is one kind of flow control.-  B In ASCII, XON is the [CTRL/Q] character, and XOFF is the [CTRL/S].  F XON/XOFF flow control is typically associated with asynchronous serialG line communications.  XON/XOFF is an in-band flow control, meaning that + the flow control is mixed in with the data.l  I CTS/RTS is another type of flow control, and is sometimes called hardwarepG flow control.  Out-of-band means that seperate lines/pins from the datae3 lines (pins) are used to carry the CTS/RTS signals.K  G Both kinds of flow control are triggered when a threshold is reached insJ the incoming buffer.  The flow control is suppose to reach the transmitterG in time to have it stop transmitting before the receiver buffer is full E and data is lost.  Later, after a sufficient amount of the receiver's E buffer is freed up, the resume flow control signal is sent to get thea transmitter going again.  F DECnet Phase IV on OpenVMS VAX supports the use of asynchronous serialI communications as a network line.  The communication devices (eg. modems,hE and drivers) *must not* be configured for XON/XOFF flow control.  TheeD incidence of these (unexpected) in-band characters will corrupt dataG packets.  Further, the serial line device drivers might normally removeoF the XON and XOFF characters from the stream for terminal applications,E but DECnet configures the driver to pass *all* characters through and-F requires that all characters be permitted.  (The communication devicesF must pass through not only the XON and XOFF characters, they must passE *all* characters including the 8-bit characters.  If data compressionoG is happening, it must reproduce the source stream exactly.  No addition > or elimination of null characters, and full data transparency.  I An Ethernet network is rather different than an asynchronous serial line.)E Ethernet specifies the control of data flow on a shared segment using B CSMA/CD (Carrier Sense Multiple Access, with Collision Detect)  AnF Ethernet station that is ready to transmit listens for a clear channelK (Carrier Sense).  When the channel is clear, the station begins to transmit J by asserting a carrier and encoding the packet appropriately.  The stationG concurrently listens to its own signal, to permit the station to detectGG if another station began to transmit at the same time -- this is calledaJ collision detection.  (The collision corrupts the signal in a way that canH reliably be detected.)  Upon detecting the collision, both stations willB stop transmitting, and will back off and try again a little later.H (You can see a log of this activity in the DECnet NCP network counters.)  G DECnet provides its own flow control, above and beyond the flow control I of the physical layer (if any).  The end nodes handshake at the beginningeG to establish a transmit window size -- and a transmitter will only sendaG that much data before stopping and waiting for an acknowledgement.  TheoG acknowledgement is only sent when the receiver has confirmed the packettD is valid.  (A well-configured DECnet generally avoids triggering any1 underlying (out-of-band) flow control mechanism.)i=                                                [David Rabahy]p  < ------------------------------------------------------------. NET1.  How to connect OpenVMS to the Internet?  A Some tutorial information and tips for connecting OpenVMS systemsd! to the Internet are available at:o  !   http://www.tmesis.com/internet/e  < ------------------------------------------------------------) NET2.  How to connect OpenVMS to a Modem?o  2   http://www.openvms.compaq.com/wizard/wiz_81.html4   http://www.openvms.compaq.com/wizard/wiz_1839.html4   http://www.openvms.compaq.com/wizard/wiz_2177.html4   http://www.openvms.compaq.com/wizard/wiz_3605.html   etcl   [End of Part 5/5]e  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  # Date: Tue, 10 Apr 2001 19:45:50 GMTd% From: bdc@world.std.com (Brian Chase)c< Subject: Re: Q: Converting a VAX 6000-420 to a VAX 6000-620?& Message-ID: <GBLDKE.69I@world.std.com>  ' In article <3AD20ED8.2AD9E3B9@iee.org>, * antonio.carlini <arcarlini@iee.org> wrote: > Paul Repacholi wrote:a1 > > "antonio.carlini" <arcarlini@iee.org> writes:g  J > > > So I think the short answer is: T2019 and that widget you plug in atI > > > the back (sorry, no part number ... I can hit the IPBs if you thinkr* > > > you might have it but are not sure). > > 5 > > Two blue power buses that go to the bottom slots?o > > E > > 17-002751-01 abd another cumming hidden under the main power bus.i >/5 > I cannot find a number for the powerbus cable and Io4 > the manual does not say anything about playng with6 > any other cables. (I'll read more carefully if Brian' > actually gets all the bits together!)h  F I'm fairly close, I think.  But then I'm only about a week into my VAXG 6000 hardware experience.  At the very least I think I can get ahold ofi6 all the pieces I need once I figure out what they are.  9 > I stumbled across a step-by-step description of exactlygA > how to apply the upgrade in the VAX 6000-600 cpu install guide.1< > The part number for the complete kit is H9657-CX (H9657-CU6 > is the full power upgrade kit that includes swapping3 > out PSUs). I seriously doubt that either of theseo- > are still orderable ... but you never know.d  H Yeah, and even if they were, I doubt I could afford them.  I'm trying toF do this on a shoestring budget.  This isn't for supporting any kind ofF legacy application.  It's a hobbyist thing.  (I wonder what VAX adminsI from a decade ago would say to the idea of running a VAX 6000 at home forf fun?).  J If I knew what the parts list for the H9657-CX kit was, that'd pretty muchG give me the information I'd want.  And actually, I'd be curious to knowh0 what the parts list for the H9657-CU kit is too.  * > If you have a H7242 regulator it already, > supplies 3.3V so no upgrade is needed. You2 > may need to diddle with the +3.3V-inhibit cable.% > (You never know, you may be lucky)./  E Well, from what I can immediately see PSU-wise, I've got 3x H7214, 2x-E H7215, and 1x H7206.  I really don't know what a H7242 is or where ita@ would fit in the VAX 6000... unless this is another name for the
 T2019(???)  I You don't mention it, but will I need to swap out the XMI-1 card cage foreH an XMI-2 one?  I got an off-newsgroup e-mail stating that I'd need to doJ this in conjuction with PSU replacements.  My guess would be that the main< difference between them is their electrical characteristics.  F Another possible route for me is to just get all the PSU and card cageI guts from a VAX 6000-6xx, transplanting them to my VAX 6000-4xx.  This iscH of course assuming that the two systems cabinents are simillar enough to accomodate such a procedure.   -brian.F -- eF --- Brian Chase | bdc@world.std.com | http://world.std.com/~bdc/ -----I I'm sorry, but you're starting to become incoherent.  SCOTTY!  HIS SIGNALtF IS BREAKING UP!  ROUTE BACKUP POWER FROM THE WARP DRIVE TO THE PATTERNB BUFFER'S HEISENBERG COMPENSATOR!  WE'RE LOSING HIS PATTERN!  -- K.   ------------------------------  # Date: Tue, 10 Apr 2001 20:03:47 GMTm% From: bdc@world.std.com (Brian Chase) < Subject: Re: Q: Converting a VAX 6000-420 to a VAX 6000-620?& Message-ID: <GBLEEB.Hz7@world.std.com>  ' In article <GBJuoy.J1L@spcuna.spc.edu>, * Terry Kennedy  <terry@gate.tmk.com> wrote:; > In comp.os.vms antonio.carlini <arcarlini@iee.org> wrote:   ; > > I stumbled across a step-by-step description of exactlysC > > how to apply the upgrade in the VAX 6000-600 cpu install guide.r> > > The part number for the complete kit is H9657-CX (H9657-CU8 > > is the full power upgrade kit that includes swapping5 > > out PSUs). I seriously doubt that either of theseA/ > > are still orderable ... but you never know.M  E Okay, well I guess next time I'll read all the messages in the threads first.  I >  H9657-CU was cancelled on 8-Nov-1999. But you wouldn't want to pay the H > $15,345.00 list price plus $4,329.00 mandatory installation anyway 8-(  > FWIW, the part description is: >0B > "VAX 6000 Power and Packaging Upgrade to complete H9657-CA level >  o XMI-2 Card Cage >  o 3.3 Volt Power Regulator  >  o XBIA+ Modulev >  o XTC Module"   Okay, so I'd need...      VAX 6000-600 CPUs	(check)l   VAX 6000-600 RAM	(check)'   XMI-2 card cage	(part number anyone?)a'   T2019 3.3V Power Reg	(Same as H7242?) 5   XBIA+ Module		(XMI half of the XMI<->VAXBI bridge?)O   XTC Module		(What is this?),  <   And then any necessary cables to hook this stuff together.  , > > If you have a H7242 regulator it already. > > supplies 3.3V so no upgrade is needed. You4 > > may need to diddle with the +3.3V-inhibit cable.' > > (You never know, you may be lucky).e > 6 >   H7242 is still available, $413.00, 1 day lead time% >   The XBIA+ (DWMBB-AB) is cancelledaK >   I think the XTC is 20-29176-01, claims to be available, $150.00, but noEA >   lead time (which usually means it's been "stealth cancelled")2  J I'm beginning to think it'll be cheaper to just freight ship the the wholeD VAX 6000-600 chasis than to scrounge all the necessary bits to do anE upgrade.  And hey, then I'd have *two* VAX 6000s in the basement.  MyhI neighbors are going to start wondering about me... more than they alreadys do.o   -brian.  -- iF --- Brian Chase | bdc@world.std.com | http://world.std.com/~bdc/ -----I I'm sorry, but you're starting to become incoherent.  SCOTTY!  HIS SIGNALNF IS BREAKING UP!  ROUTE BACKUP POWER FROM THE WARP DRIVE TO THE PATTERNB BUFFER'S HEISENBERG COMPENSATOR!  WE'RE LOSING HIS PATTERN!  -- K.   ------------------------------  % Date: Tue, 10 Apr 2001 23:52:07 +0100-+ From: "antonio.carlini" <arcarlini@iee.org>-< Subject: Re: Q: Converting a VAX 6000-420 to a VAX 6000-620?' Message-ID: <3AD38E97.3AB5244E@iee.org>    Brian Chase wrote: >  > ! >   VAX 6000-600 CPUs     (check)c! >   VAX 6000-600 RAM      (check) / >   XMI-2 card cage       (part number anyone?) * >   T2019 3.3V Power Reg  (Same as H7242?)? >   XBIA+ Module          (XMI half of the XMI<->VAXBI bridge?) ) >   XTC Module            (What is this?)w > > >   And then any necessary cables to hook this stuff together.  1 The above basically turns your XMI-1 chassis intoE. an XMI-2 chassis by changing all the bits that are different between the two.  , Except that if you go this route you *don't*( use the T2019 and you *do* use the H7242( (which replaces one the the H7214 IIRC).  / You also get to remove lots of bits and replace  them with other bits.   * If you want battery backup you may need to do stuff with the H405 too.d  & The *easy* route is to pick up a T2019. from ebay or wherever. Make sure it comes with* the (blue?) powerbus cabling. The T2019 is( an XMI module like any other XMI module,+ except it sits in slot 2 and blocks slot 1.r  ) The upside is that you will have time for , a life. The downside is that you essentially& lose 2 slots and can support at most 4# KA65A or KA66A CPUs. Is this really-" a problem :-) (Plus you cannot use battery backup).  L > I'm beginning to think it'll be cheaper to just freight ship the the wholeF > VAX 6000-600 chasis than to scrounge all the necessary bits to do anG > upgrade.  And hey, then I'd have *two* VAX 6000s in the basement.  MytK > neighbors are going to start wondering about me... more than they alreadys > do.   - I would go for the ready-built chassis. Apart 0 from anything else it would look *so* impressive in the basement. -   Antonio1   -- n   ---------------i- Antonio Carlini             arcarlini@iee.org    ------------------------------   Date: 11 Apr 2001 02:29:44 GMT) From: leslie@clio.rice.edu (Jerry Leslie))) Subject: Redundant Power Supply on DS20E?D' Message-ID: <9b0fio$ker$1@joe.rice.edu> & Keywords: ds20e,power_supply,redundant  ; A customer is trying to ascertain that everything purchased / for three DS20E systems was actually delivered.)  B The quote for the three systems mentions three KN310-BCs, one for A each DS20E, and describes them as DS20E Redundant Power Supplies.(  A The AlphaServer DS20E/AlphaStation DS20E Reference Guide mentionscC that a minimum of two power supplies are required, and a third may o be added for redundancy.  C We're willing to open the systems up, but need to know what to lookv for.     Thanks in advance,   --Jerry Leslie        F P.S.: This site's security requires an account & password for outbound,       web access access, which I don't have.   ------------------------------  % Date: Tue, 10 Apr 2001 22:15:48 -0500r+ From: Shael Richmond <ksrich@bellsouth.net>e- Subject: Re: Redundant Power Supply on DS20E? - Message-ID: <3AD3CC64.6C68F620@bellsouth.net>    Jerry Leslie wrote:l > = > A customer is trying to ascertain that everything purchasedn1 > for three DS20E systems was actually delivered.  > C > The quote for the three systems mentions three KN310-BCs, one for C > each DS20E, and describes them as DS20E Redundant Power Supplies.  > C > The AlphaServer DS20E/AlphaStation DS20E Reference Guide mentions D > that a minimum of two power supplies are required, and a third may > be added for redundancy. > E > We're willing to open the systems up, but need to know what to look  > for. >   E You don't have to open the systems up.  Just pop off the front cover.>E The power supplies are on the left side.  Check the fans because whenXA there are only two supplies there is a dummy module as the third.    Shael4   ------------------------------    Date: 10 Apr 2001 18:11:12 -0500+ From: kuhrt@encompasserve.org (Marty Kuhrt)  Subject: Sessions and CSWS3 Message-ID: <K6dxbPzHI7q7@eisner.encompasserve.org>e  = I've been working with CSWS V1.0-1 on my AlphaStation running 9 V7.2-1 (and patches) and had some questions about session-; tracking.  Instead of flopping about on the Apache site and 1 various Java sites, I thought I'd ask here first.   ? What are CSWS users using to track and manage sessions?  What I-@ mean by that is, how are you making the basically stateless HTTP@ session statefull?  I've seen some examples using Java and JservA functions, but was wondering if there was a DCL or C variation onr@ the theme.  I would rather not reinvent the wheel if there is an7 easily available solution out there in VMSland already.    TIA, Marty    ------------------------------  % Date: Tue, 10 Apr 2001 21:14:37 -0400-- From: JF Mezei <jfmezei.spamnot@videotron.ca>- Subject: Re: Sessions and CSWS, Message-ID: <3AD3AFF7.8231B230@videotron.ca>   Marty Kuhrt wrote:A > What are CSWS users using to track and manage sessions?  What InB > mean by that is, how are you making the basically stateless HTTP > session statefull? 5  O It truly depends on your application and how you want to deal with the clients.m  A If you just want to control access to pages, you can use the HTTPmJ authentication. First time in a session a user accesses a page, the serverE send a control message back that causes the browser to pop up a quickiJ username/password combi. From then on, each HTTP request from that browserH will have the username/password included in the HTTP header, and the web! server will authenticate for you.   N But if you have an application that does transactional stuff, it may be easierL for the application to include a hidden field in the forms that contains theM session context. You can have the application context id as a hidden field in81 a form, or as a URL encoded field next to the urloB (eg: http://www.chocolate.com/recipes/great.com?id=8382728939303 )  L This lets you control session expiration, and you can also have nicer/slowerD screens for login information which combine ability to register etc.   ------------------------------  # Date: Wed, 11 Apr 2001 05:09:40 GMTs$ From: plugh@NO.SPAM.PLEASE (Caveman) Subject: Re: Status of EV70 Message-ID: <oGRA6.328$zq1.157648@nnrp2.sbc.net>  1 In article <969dkb$sp0$1@ausnews.austin.ibm.com>, ) McCalpin <mccalpin@austin.ibm.com> wrote: 1 >In article <961bk4$odm$1@pegasus.csx.cam.ac.uk>,m* >Nick Maclaren <nmm1@cus.cam.ac.uk> wrote: >>B >>The Hitachi SR2201 has 4 MB/sec per MFlop, all the way from main@ >>memory (actually it bypasses cache in pseudovectorising mode).B >>Experience is that this was more than adequate (except for a few> >>inner loops), but that dropping below 2 starts to be a major >>bottleneck.  c >eE >Only if you don't have large caches (or don't know how to use them).d [...}o  A Actually I would argue with both of you that you are both way too  caught up in technology.  @ First of all, there are very few sparsely populated problem sets@ which can't be reduced dramatically in computational workload by@ a creative human mind.  On the other hand, cache and RAM tend toA be each something which has to be made use of in some nonportableb manner.h  E Cache requires maximizing locality of reference and reuse of results,oE while RAM requires optimum stride if it's interleaved enough, say 512L ways.f  F On the other hand, neither is all that useful when you're dealing withF the increasingly usual case of a supercomputer (ab)used in timesharingG operating mode, or programmed by a grad student who doesn't have a cluemC as to any of the above, not a slam against free labor, just that ithF takes a lot of experience to master these relationships and the talent. pool is rather shallow in the Real World (tm).     --  D      "A great deal of intelligence can be invested in ignorance when%       the need for illusion is deep."a           -- Saul Bellow   ------------------------------  % Date: Tue, 10 Apr 2001 19:57:26 +0200a> From: "Jean-Francois Marchal" <jean-francois.marchal@x9000.fr>< Subject: strange behaviour of DIRECTORY with long file names. Message-ID: <9avhcn$i38$1@reader1.imaginet.fr>  > I tried to create some long file names to test an application. Created 3 files ...r, What I get after that is pretty strange ....( For what reason do I see 3 directories ?     $ sh def   x9000$cus:[infotel.files]r $ dir *.diri! %DIRECT-W-NOFILES, no files found  $e $ dire  # Directory X9000$CUS:[Infotel.files]     H Ceci_est_un_exemple_de_fichier_comportant^_toutes_sortes_de_caractres_aH ccentus_et_spciaux^.dans_son_nom_^&_dans_son_extension_permis_par_la.aH vec_un_MAXIMUM--DE--254_caractres__sans_compter_tous_les_
 autres_a;1   Total of 1 file.  * Directory DSA2:[X9000.CUS.][Infotel.files]    H Ceci_est_un_exemple_de_fichier_comport~[52466,7,0].avec_un_MAXIMUM--DE--> 254_caractres__sans_compter_tous_les_autres_a;1  H Ceci_est_un_exemple_de_fichier_comport~[52467,6,0].avec_un_MAXIMUM--DE--> 254_caractres__sans_compter_tous_les_autres__;1   Total of 2 files.a  # Directory X9000$CUS:[Infotel.files]   B create_relative.txt;1                   create_relative_file.com;29 DECC$CRTL.OLB;3     DECC$RTLDEF.TLB;3   LMF$LICENSE.LDB;1e5 rmsrel1.EXE;1       rmsrel1.for;3       rmsrel1.OBJ;1o* rudy.dat;1          tcpip$ftp_server.bck;1 VMS$LAYERED.DAT;1    Total of 11 files.  ' Grand total of 3 directories, 14 files.s $t   ------------------------------  # Date: Tue, 10 Apr 2001 18:22:17 GMTn2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)@ Subject: Re: strange behaviour of DIRECTORY with long file names2 Message-ID: <tbIA6.753$fB6.19160@news.cpqcorp.net>  o In article <9avhcn$i38$1@reader1.imaginet.fr>, "Jean-Francois Marchal" <jean-francois.marchal@x9000.fr> writes:-? :I tried to create some long file names to test an application.H :Created 3 files ...- :What I get after that is pretty strange ....n) :For what reason do I see 3 directories ?t  H   Use the SHOW DEFAULT command, and look for a search list logical name G   with three translations.  If so, this is the expected (but definitelyoD   odd) behaviour of default directories and wildcard specifications.  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: Tue, 10 Apr 2001 14:39:53 -0400-7 From: David Beatty <David.Beatty@sasSPAMITUPTHEZZZ.com>.@ Subject: Re: strange behaviour of DIRECTORY with long file names2 Message-ID: <E1PTOhJ7sjODzjwV11RfN+OPE9bm@4ax.com>  5 How about a SHOW LOGICAL X9000$CUS/FULL ?  Looks likeiE the logical has three translations, the second and third of which aret
 concealed.   David R. Beattyg  ; On Tue, 10 Apr 2001 19:57:26 +0200, "Jean-Francois Marchal"h' <jean-francois.marchal@x9000.fr> wrote:(  ? >I tried to create some long file names to test an application.o >Created 3 files ...- >What I get after that is pretty strange ....a) >For what reason do I see 3 directories ?2 >- >a	 >$ sh defc >  x9000$cus:[infotel.files] >$ dir *.dir" >%DIRECT-W-NOFILES, no files found >$ >$ dir >n$ >Directory X9000$CUS:[Infotel.files] >a >tI >Ceci_est_un_exemple_de_fichier_comportant^_toutes_sortes_de_caractres_auI >ccentus_et_spciaux^.dans_son_nom_^&_dans_son_extension_permis_par_la.aII >vec_un_MAXIMUM--DE--254_caractres__sans_compter_tous_les_a >autres_a;1c >g >Total of 1 file.h >i+ >Directory DSA2:[X9000.CUS.][Infotel.files]  >  >tI >Ceci_est_un_exemple_de_fichier_comport~[52466,7,0].avec_un_MAXIMUM--DE--g? >254_caractres__sans_compter_tous_les_autres_a;1o >hI >Ceci_est_un_exemple_de_fichier_comport~[52467,6,0].avec_un_MAXIMUM--DE--i? >254_caractres__sans_compter_tous_les_autres__;1h >o >Total of 2 files. > $ >Directory X9000$CUS:[Infotel.files] >nC >create_relative.txt;1                   create_relative_file.com;2n: >DECC$CRTL.OLB;3     DECC$RTLDEF.TLB;3   LMF$LICENSE.LDB;16 >rmsrel1.EXE;1       rmsrel1.for;3       rmsrel1.OBJ;1+ >rudy.dat;1          tcpip$ftp_server.bck;1  >VMS$LAYERED.DAT;1 >a >Total of 11 files.f >u( >Grand total of 3 directories, 14 files. >$ >5 >X   ------------------------------  % Date: Tue, 10 Apr 2001 21:32:52 +0200l> From: "Jean-Francois Marchal" <jean-francois.marchal@x9000.fr>@ Subject: Re: strange behaviour of DIRECTORY with long file names. Message-ID: <9avmvk$j14$1@reader1.imaginet.fr>  + The logical name has a single translation :Y   $ sh log x9000$cus /fullA    "X9000$CUS" [super] = "DSA2:[X9000.CUS.]" [concealed,terminal]3    (LNM$SYSTEM_TABLE)d  I before I created my long file names, the directory listed as only one ...e  A I must add that i dint insert the ~[52466,7,0] in the file names.oG They appeared after a rename on an initial file to have a longer name !X  ( Doesn't look like a normal behaviour ...> I kept a copy of everything trough a decterm print to file ...: One of the intermediate dirs on the same current directory	 gave me :e       Directory DSA2:[36550,8,0]   !!! Really strange  	 VMS 7.2-1t   Jean-Franois Marchal  X9000 - LYON (FR)A    L "Hoff Hoffman" <hoffman@xdelta.zko.dec.nospam> a crit dans le message news:' tbIA6.753$fB6.19160@news.cpqcorp.net...rH > In article <9avhcn$i38$1@reader1.imaginet.fr>, "Jean-Francois Marchal"( <jean-francois.marchal@x9000.fr> writes:A > :I tried to create some long file names to test an application.. > :Created 3 files .../ > :What I get after that is pretty strange .... + > :For what reason do I see 3 directories ?P >AI >   Use the SHOW DEFAULT command, and look for a search list logical name I >   with three translations.  If so, this is the expected (but definitely F >   odd) behaviour of default directories and wildcard specifications. > ( >  ---------------------------- #include' <rtfaq.h> -----------------------------dL >       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com, >  --------------------------- pure personal# opinion --------------------------- 1 >    Hoff (Stephen) Hoffman   OpenVMS Engineerings hoffman#xdelta.zko.dec.com >e   ------------------------------  % Date: Tue, 10 Apr 2001 15:38:40 -0400 7 From: David Beatty <David.Beatty@sasSPAMITUPTHEZZZ.com>u@ Subject: Re: strange behaviour of DIRECTORY with long file names2 Message-ID: <NGHTOrgvE4QMsuyjw0uw37qYnYto@4ax.com>  * Make that first and third translations ...  0 On Tue, 10 Apr 2001 14:39:53 -0400, David Beatty+ <David.Beatty@sasSPAMITUPTHEZZZ.com> wrote:l   >,6 >How about a SHOW LOGICAL X9000$CUS/FULL ?  Looks likeF >the logical has three translations, the second and third of which are >concealed.l >l >David R. Beatty >e< >On Tue, 10 Apr 2001 19:57:26 +0200, "Jean-Francois Marchal"( ><jean-francois.marchal@x9000.fr> wrote: >0@ >>I tried to create some long file names to test an application. >>Created 3 files ...a. >>What I get after that is pretty strange ....* >>For what reason do I see 3 directories ? >> >>
 >>$ sh def >>  x9000$cus:[infotel.files]n
 >>$ dir *.dirc# >>%DIRECT-W-NOFILES, no files found  >>$f >>$ dir  >>% >>Directory X9000$CUS:[Infotel.files]3 >> >>J >>Ceci_est_un_exemple_de_fichier_comportant^_toutes_sortes_de_caractres_aJ >>ccentus_et_spciaux^.dans_son_nom_^&_dans_son_extension_permis_par_la.aJ >>vec_un_MAXIMUM--DE--254_caractres__sans_compter_tous_les_ >>autres_a;1 >> >>Total of 1 file. >>, >>Directory DSA2:[X9000.CUS.][Infotel.files] >> >>J >>Ceci_est_un_exemple_de_fichier_comport~[52466,7,0].avec_un_MAXIMUM--DE--@ >>254_caractres__sans_compter_tous_les_autres_a;1 >>J >>Ceci_est_un_exemple_de_fichier_comport~[52467,6,0].avec_un_MAXIMUM--DE--@ >>254_caractres__sans_compter_tous_les_autres__;1 >> >>Total of 2 files.. >>% >>Directory X9000$CUS:[Infotel.files]  >>D >>create_relative.txt;1                   create_relative_file.com;2; >>DECC$CRTL.OLB;3     DECC$RTLDEF.TLB;3   LMF$LICENSE.LDB;1T7 >>rmsrel1.EXE;1       rmsrel1.for;3       rmsrel1.OBJ;1M, >>rudy.dat;1          tcpip$ftp_server.bck;1 >>VMS$LAYERED.DAT;1E >> >>Total of 11 files. >>) >>Grand total of 3 directories, 14 files.  >>$1 >> >>   ------------------------------  % Date: Tue, 10 Apr 2001 21:57:39 +0200R> From: "Jean-Francois Marchal" <jean-francois.marchal@x9000.fr>@ Subject: Re: strange behaviour of DIRECTORY with long file names. Message-ID: <9avoe3$j9m$1@reader1.imaginet.fr>  7 Sorry .. I do not understand what you are suggesting ..y  ? X9000$CUS has only one translation, and DSA2 on which it reliese8 is the name of the disk, without any synomym anywhere ..  K "David Beatty" <David.Beatty@sasSPAMITUPTHEZZZ.com> a crit dans le messageo- news: NGHTOrgvE4QMsuyjw0uw37qYnYto@4ax.com...u > , > Make that first and third translations ... >n2 > On Tue, 10 Apr 2001 14:39:53 -0400, David Beatty- > <David.Beatty@sasSPAMITUPTHEZZZ.com> wrote:' >  > >h8 > >How about a SHOW LOGICAL X9000$CUS/FULL ?  Looks likeH > >the logical has three translations, the second and third of which are
 > >concealed.i > >  > >David R. Beatty > >k> > >On Tue, 10 Apr 2001 19:57:26 +0200, "Jean-Francois Marchal"* > ><jean-francois.marchal@x9000.fr> wrote: > >.B > >>I tried to create some long file names to test an application. > >>Created 3 files ...o0 > >>What I get after that is pretty strange ...., > >>For what reason do I see 3 directories ? > >> > >> > >>$ sh def > >>  x9000$cus:[infotel.files]  > >>$ dir *.dirc% > >>%DIRECT-W-NOFILES, no files foundU > >>$h	 > >>$ dir  > >>' > >>Directory X9000$CUS:[Infotel.files]k > >> > >>L > >>Ceci_est_un_exemple_de_fichier_comportant^_toutes_sortes_de_caractres_aL > >>ccentus_et_spciaux^.dans_son_nom_^&_dans_son_extension_permis_par_la.aL > >>vec_un_MAXIMUM--DE--254_caractres__sans_compter_tous_les_ > >>autres_a;1 > >> > >>Total of 1 file. > >>. > >>Directory DSA2:[X9000.CUS.][Infotel.files] > >> > >>L > >>Ceci_est_un_exemple_de_fichier_comport~[52466,7,0].avec_un_MAXIMUM--DE--B > >>254_caractres__sans_compter_tous_les_autres_a;1 > >>L > >>Ceci_est_un_exemple_de_fichier_comport~[52467,6,0].avec_un_MAXIMUM--DE--B > >>254_caractres__sans_compter_tous_les_autres__;1 > >> > >>Total of 2 files.e > >>' > >>Directory X9000$CUS:[Infotel.files]s > >>F > >>create_relative.txt;1                   create_relative_file.com;2= > >>DECC$CRTL.OLB;3     DECC$RTLDEF.TLB;3   LMF$LICENSE.LDB;1d9 > >>rmsrel1.EXE;1       rmsrel1.for;3       rmsrel1.OBJ;1B. > >>rudy.dat;1          tcpip$ftp_server.bck;1 > >>VMS$LAYERED.DAT;1u > >> > >>Total of 11 files. > >>+ > >>Grand total of 3 directories, 14 files.h > >>$n > >> > >> >e   ------------------------------  + Date: Tue, 10 Apr 2001 19:51:43 +0000 (UTC)l From: eeccmc@net-stafferss.com9 Subject: Surgeon Generals Warning- Awesome New Band  1399 / Message-ID: <9avo8f$226o$604@news2.seidata.com>y   Hello everyone,tG   my name is Jason Appleton and I am the Manager for a new Group called  Surgeon Generals Warning.-K I would like some constructive criticisim about this band if any of u wouldl: like to help out. All I ask it that you check out the siteL www.jasonappleton.net  and listen to the 2 demo songs on The Vibe page. ThenL just drop me an e-mail and let me know what you think and if you would buy aL CD from them. Also, if you would like to be part of the mailing list for SGWI and recieve gig dates, band info, and possibly even links to new and free H MP3's. Add in your e-mail that you would like to join the newsletter. ItK will only be sent out when important changes are made and things happen. WeeG dont want to spam everyone with a bunch of junk you wont care about. SoeK anyway, if you love new Music that is studio quality and would like to helpeL out, It would be much appreciated. Maybe in the future if we play a gig near& you, we will send you free tickets. :)K Thank you everyone for your support, and we hope you enjoy the band Surgeon  Generals Warning.-   -- Jason Appleton
 Opulent MusicA Manager-SGW:  ( tcsmsmwdswwvuinyhinhpucbopqmveetpggwlgux   ------------------------------  + Date: Wed, 11 Apr 2001 02:03:17 +0000 (UTC)s From: opzeko@net-stafferss.comI Subject: Surgeon Generals Warning- Awesome new band from Cincinnati  1231s/ Message-ID: <9b0e15$2g4l$604@news2.seidata.com>o   Surgeon Generals Warning is a new band with remarkable talent, and we want to know what you think too. Please check out www.jasonappleton.net and go to The Vibe page, listen to a couple of their tracks and let us know what you think and maybe if you would buy a CD if it were in stores.. If You like them, well send you a link to download free MP3s of the bands newest songs. We could use your help, also maybe some day if we book a gig in your area, well send you you tickets for the show for you and 3 friends."  Just a thought. :) Thank You all.B eqyhjzcuqfobxkzxbhbzkolqilgegnlenyqlgndtilbdzdzikgvlmcoycbsxlnsjsd   ------------------------------   Date: 11 Apr 2001 00:22:00 GMT) From: leslie@clio.rice.edu (Jerry Leslie)t, Subject: TCP/IP 5.0A/ECO 2 FTP "425" Failure' Message-ID: <9b0838$cnl$1@joe.rice.edu>e Keywords: vms,alpha,ftp,425,ucxs  ? FTP's from an ALPHA running TCP/IP 5.0A - ECO 2 work once afteri reboot, and then fail with:i  5   425-Can't build data connection for 149.183.27.53,0 ,   425 remote node is not currently reachable  G where 149.183.27.53 is the IP address of the ALPHA, which is reachable,m per an FTP to itself.   . Is this a known problem fixed by a later ECO ?  4 --Jerry Leslie     (my opinions are strictly my own)  N ============================================================================== <OLYSC3>tcpip show version  A   DIGITAL TCP/IP Services for OpenVMS Alpha Version V5.0A - ECO 2m?   on a COMPAQ AlphaServer DS20E 500 MHzP running OpenVMS V7.2-1e   <OLYSC3>tcpip show interface>                                                        PacketsK Interface   IP_Addr         Network mask      Receive          Send     MTU.  K  WE0        149.183.27.53   255.255.255.0        9082          7118    1500sK  LO0        127.0.0.1       255.0.0.0             187           187       0t   <OLYSC3>ftp 128.42.105.4* 220 riceng FTP Server (Version 4.1) Ready. Connected to 128.42.105.4." Name (128.42.105.4:system): leslie' 331 Username LESLIE requires a Passwordf	 Password:g 230 User logged in.1
 FTP> ascii 200 TYPE set to ASCII. FTP> get login.com z.z 200 TYPE set to IMAGE. 200 PORT command successful.3 425-Can't build data connection for 149.183.27.53,0>* 425 remote node is not currently reachable	 FTP> quith 221 Goodbye.   ------------------------------  % Date: Tue, 10 Apr 2001 14:48:34 -0400a# From: Jim Agnew <Agnew@hsc.vcu.edu>.$ Subject: Re: VMS friendly website???+ Message-ID: <3AD35582.E0868CC2@hsc.vcu.edu>)    works for w95b and netscape 4.77   ja   Island Computers US Corp wrote:  > < > OUt of curiosity - anyone checked out website this morningG > We had a fella redo it for Netscape so it should work a little bettero > Still uses frames though...  >  > DT > --! > Island Computers US Corporation  > 2700 Gregory Street' > Suite 150d > Savannah GA 31404a > Tel: 912 447 6622  > Fax: 912 201 0096  > sales@islandco.com > www.islandco.com > E > This message and any files transmitted with it are confidential andhL > may be privileged and/or subject to the provisions of privacy legislation.J > They are intended solely for the use of the individual or entity to whomG > they are addressed. If the reader of this message is not the intendedh > recipient,I > please notify Island Computers US Corp immediately and then delete this 
 > message.K > You are notified that reliance on, disclosure of, distribution or copyingl  > of this message is prohibited.   ------------------------------  # Date: Tue, 10 Apr 2001 19:11:49 GMTt, From: peterw@u.genie.co.uk (Peter Watkinson)$ Subject: Re: VMS friendly website???< Message-ID: <3ad35a20.5731007@newshost.netscapeonline.co.uk>  > On Tue, 10 Apr 2001 12:52:53 -0400, "Island Computers US Corp" <dbturner@islandco.com> wrote:  ; >OUt of curiosity - anyone checked out website this morning-F >We had a fella redo it for Netscape so it should work a little better >Still uses frames though... >v >$ >DT@   Hi Dave,  E Pete opens up sewer lid crawls out and croaks - "looks OK in Netscape.C and IE Alpha NT" - crawls back under lid and returns to the depths.   B PS don't sell the Low Cost Alphas too quick I want one for VMS and Tru64.  	  regards,      Peter WatkinsonI Email: peterw@u.genie.co.uki( Internet: http://you.genie.co.uk/peterw/A Windsurf International.com http://www.windsurf-international.com/a* PW Navigate.com http://www.pwnavigate.com/   ------------------------------   Date: 10 Apr 2001 19:53:26 GMT1 From: bill@triangle.cs.uofs.edu (Bill Gunshannon)r$ Subject: Re: VMS friendly website???, Message-ID: <9avobm$1dmt$1@info.cs.uofs.edu>  ( In article <3AD34425.6433F5A3@ohio.edu>,0  "Richard D. Piccard" <piccard@ohio.edu> writes: |> aK |> You have achieved something truly unique in the way of Macintosh-hostile6 |> pages:  n  0 Maybe, but Macintosh friendly wasn't their goal.   bill   -- _J Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>       ------------------------------  # Date: Tue, 10 Apr 2001 20:39:45 GMT.+ From: rjordan@mars.mcs.net (Richard Jordan)f$ Subject: Re: VMS friendly website???4 Message-ID: <lcKA6.7825$JN5.179730@news.goodnet.com>  L >|> You have achieved something truly unique in the way of Macintosh-hostile
 >|> pages: >r1 >Maybe, but Macintosh friendly wasn't their goal.I  F The previous iteration (on MacOS 9.x, Netscape V4.7) had a workaround.E Click on a frame menu item (alpha, memory, whatever), wait for 'done'tE (where you'd be presented with a blank central frame) then resize the D navigator window slightly.  Instant page view.  Everytime you change pages, jiggle the size again.e  : Not home now so no idea how it will work with the changes.   Rich Jordanc rjordan@mcs.nett   ------------------------------  % Date: Tue, 10 Apr 2001 22:32:04 -0400h2 From: rdeininger@mindspring.com (Robert Deininger)$ Subject: Re: VMS friendly website???L Message-ID: <rdeininger-1004012232040001@user-2iveccc.dialup.mindspring.com>  @ In article <3AD34425.6433F5A3@ohio.edu>, piccard@ohio.edu wrote:  J > You have achieved something truly unique in the way of Macintosh-hostileM > pages:  no matter how wide I make my browser window (Mac Netscape 4.76), at-I > least up to twice as wide as can print without cropping, I still have ae3 > horizontal scroll bar for the main-content frame.R   Haven't tried from VMS yet.R  - CyberDog 2.0 does ok with the site on my Mac.z   -- N Robert Deininger rdeininger@mindspring.comX   ------------------------------  % Date: Tue, 10 Apr 2001 15:25:38 -0500d/ From: Chris Scheers <chris@applied-synergy.com>BE Subject: Why set PYHSICALPAGES? (was: [Q] Adding Memory to a MV 3100) 3 Message-ID: <3AD36C42.D3959E24@applied-synergy.com>t  G I'm probably missing something obvious (that would be nothing new), but.( why does AUTOGEN even set PHYSICALPAGES?  D I thought that PHYSICALPAGES (and PHYSICAL_MEMORY) were only used to" restrict memory for special needs.  H For normal operation, they should be left at their maximum (and default) values.o     JF Mezei wrote:C   > Ram Rajadhyaksha wrote:_ > >rM > > I have added 64 Mb to our MV 3100/95. The SHOW MEMORY command at the bootnO > > prompt shows (correctly) 128 Mb total. However, OpenVMS 6.2 still sees only
 > > 64 Mb. >  > try: > $MC SYSGEN > SYSGEN> SHOW PHYSICALPAGES > I > This will tell you how many physical pages VMS really thinks there are._ > you could try5
 > USE CURRENTu  > SET PHYSICALPAGES = new number > WRITE CURRENTn > 5 > and then reboot to see if VMS sees your new memory._ > O > But eventually, you will want to run AUTOGEN to ensure that it adjusts plentyn; > of other parameters  to take advantage of the new memory.D > P > You can run AUTOGEN in such a way that it doesn't modify any system parametersQ > and just plays with its own stuff. (@SYSUPDATE:AUTOGEN HELP will give you info)   G ----------------------------------------------------------------------- $ Chris Scheers, Applied Synergy, Inc.  C Voice: 817-237-3360            Internet: chris@applied-synergy.com     Fax: 817-237-3074    ------------------------------  # Date: Tue, 10 Apr 2001 21:10:02 GMT 2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)I Subject: Re: Why set PYHSICALPAGES? (was: [Q] Adding Memory to a MV 3100)s2 Message-ID: <KEKA6.763$fB6.19365@news.cpqcorp.net>  e In article <3AD36C42.D3959E24@applied-synergy.com>, Chris Scheers <chris@applied-synergy.com> writes:[H :I'm probably missing something obvious (that would be nothing new), but) :why does AUTOGEN even set PHYSICALPAGES?e  I   If you were to ask me, I'd likely comment that this particular AUTOGEN iG   behaviour looks to be a (mis)feature.  That said, part of the intent gI   behind this change was to simply get you to look at your MODPARAMS.DAT eG   file and also to encourage you to run an AUTOGEN pass -- particularlyo   when you add physical memory.e  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Tue, 10 Apr 2001 17:34:46 -0400o- From: JF Mezei <jfmezei.spamnot@videotron.ca>iI Subject: Re: Why set PYHSICALPAGES? (was: [Q] Adding Memory to a MV 3100)e, Message-ID: <3AD37C6C.FAD469E5@videotron.ca>   Chris Scheers wrote: > I > I'm probably missing something obvious (that would be nothing new), butF* > why does AUTOGEN even set PHYSICALPAGES? > F > I thought that PHYSICALPAGES (and PHYSICAL_MEMORY) were only used to$ > restrict memory for special needs.    M When I started with VMS, I was under the impression that you only played withnH PHYSICALPAGES when you needed to simulated lower memory availability andM otherwise you'd never set it. As such, I woudl have expected (back then) thateJ PHYSICALPAGES would be set to "0"  to tell the system to use all available memory by default.  J But looking at various systems, PHYSICALPAGES seems to be written into theA parameters (both ACTIVE and CURRENT) with te actual memory value.   N Wouldn't it have been possible to have PHYSICAL PAGES set to "0" in the storedH parameters and then when the system boots, the active parameter reflectsI actual physical memory unless overrriden by a non-zero stored parameter ?i  E What happens when the stores PHYSICALPAGES is greater than the actualiN available memory ? Does VMS automatically adjust the memory size to match realK memory, or does it blindly assume that SYSGEN'S paramemer is correct at thee0 risk of writin to non existant physical memory ?   ------------------------------   End of INFO-VAX 2001.202 ************************