1 INFO-VAX	Thu, 03 Jul 2003	Volume 2003 : Issue 364       Contents:6 Re: Compaq Solutions Aliance - Do it still existing  ? Re: cxx performance J Re: HP Webcast this morning on Next-Generation Intel Itanium 2  processorsI Re: HP Webcast this morning on Next-Generation Intel Itanium 2 processors P Re: HP Webcast this morning on Next-Generation Intel Itanium 2 processors proces# Re: HP World (was HP to drop hpux?) # Re: HP World (was HP to drop hpux?) 
 iSCSI anyone?   LTO-2 Ultrium tape drive and VMS$ Re: LTO-2 Ultrium tape drive and VMS$ RE: LTO-2 Ultrium tape drive and VMS Re: Mount a backup /image ) New Oracle documents available on the web " OpenVMS FAQ and FAQ Website Errata2 OpenVMS Frequently Asked Questions (FAQ), Part 1/92 OpenVMS Frequently Asked Questions (FAQ), Part 2/92 OpenVMS Frequently Asked Questions (FAQ), Part 3/92 OpenVMS Frequently Asked Questions (FAQ), Part 4/92 OpenVMS Frequently Asked Questions (FAQ), Part 5/92 OpenVMS Frequently Asked Questions (FAQ), Part 6/92 OpenVMS Frequently Asked Questions (FAQ), Part 7/92 OpenVMS Frequently Asked Questions (FAQ), Part 8/92 OpenVMS Frequently Asked Questions (FAQ), Part 9/9K Re: OpenVMS Pearl - OpenVMS V8.0, first release on Itanium, ships  today!!! 1 OpenVMS Technical Journal 2nd issue now available 5 Re: OpenVMS Technical Journal 2nd issue now available  Re: Running VMS off CD Re: Running VMS off CD% Updated Host-Based MiniMerge Schedule F Re: VAX support (was: Re: OpenVMS Technical Seminar Highlights (some))F Re: VAX support (was: Re: OpenVMS Technical Seminar Highlights (some))F Re: VAX support (was: Re: OpenVMS Technical Seminar Highlights (some))F RE: VAX support (was: Re: OpenVMS Technical Seminar Highlights (some))F RE: VAX support (was: Re: OpenVMS Technical Seminar Highlights (some))F RE: VAX support (was: Re: OpenVMS Technical Seminar Highlights (some))F RE: VAX support (was: Re: OpenVMS Technical Seminar Highlights (some))F Re: VAX support (was: Re: OpenVMS Technical Seminar Highlights (some))F Re: VAX support (was: Re: OpenVMS Technical Seminar Highlights (some))F RE: VAX support (was: Re: OpenVMS Technical Seminar Highlights (some))F RE: VAX support (was: Re: OpenVMS Technical Seminar Highlights (some))F RE: VAX support (was: Re: OpenVMS Technical Seminar Highlights (some))F Re: VAX support (was: Re: OpenVMS Technical Seminar Highlights (some))F Re: VAX support (was: Re: OpenVMS Technical Seminar Highlights (some))F RE: VAX support (was: Re: OpenVMS Technical Seminar Highlights (some))F RE: VAX support (was: Re: OpenVMS Technical Seminar Highlights (some))4 VAX Vup Listing not available on HP - where is it ??8 Re: VAX Vup Listing not available on HP - where is it ??8 Re: VAX Vup Listing not available on HP - where is it ??8 Re: VAX Vup Listing not available on HP - where is it ??9 VMS makes "General News" section of HP's "Customer Times" = Re: VMS makes "General News" section of HP's "Customer Times" = Re: VMS makes "General News" section of HP's "Customer Times" = Re: VMS makes "General News" section of HP's "Customer Times"  Re: what is VMS advanced Server  Re: what is VMS advanced Server  Re: what is VMS advanced Server  Re: what is VMS advanced Server   F ----------------------------------------------------------------------  + Date: Thu, 03 Jul 2003 11:11:53 +0200 (MET) 9 From: Phillip Helbig <HELBPHI@sysdev.deutsche-boerse.com> ? Subject: Re: Compaq Solutions Aliance - Do it still existing  ? ; Message-ID: <01KXTJ1AGU82APKEWT@sysdev.deutsche-boerse.com>   F > A desktop should help you manage the large system, not the other way
 > around.   D Reminds me of Seymour Cray's famous remark when told that Apple had C bought a Cray to design the next Apple: "I just bought an Apple to   design the next Cray."   ------------------------------   Date: 3 Jul 2003 09:10:07 -0700 ) From: ejohnson@factset.com (Eric Johnson)  Subject: Re: cxx performance= Message-ID: <ef79676b.0307030810.538dd437@posting.google.com>   Y Nic Clews <sendspamhere@[127.0.0.1]> wrote in message news:<bdu8hu$375$1@lore.csc.com>...   H > WSDEF and WSQUO, do they have to be so different? For a process to useJ > its quota and to grow to it, the process needs to pagefault above PFRATHC > every AWSTIME each QUANTUM to have a single WSINC which means the H > swapper may have to consume operating system overhead, add to that theF > real time which passes while the process gets itself "up to size". AF > WSQUO = WSDEF means that the process does not have to go through theJ > working set growth phase, only if there is 'free memory' to grow towards > WSEXTENT.   C These are good thoughts, unfortunately persuing them will take some ; time so I won't be able to provide a response anytime soon.   
 -Eric Johnson + ejohnson at f a c t s e t no spam dot c o m    ------------------------------  # Date: Thu, 03 Jul 2003 08:40:57 GMT 4 From: brad@.gateway.2wire.net (Bradford J. Hamilton)S Subject: Re: HP Webcast this morning on Next-Generation Intel Itanium 2  processors + Message-ID: <t_RMa.2658$Ix2.1216@rwcrnsc54>   _ In article <lvCcnfzUXKQmM56iXTWJjg@metrocast.net>, "Bill Todd" <billtodd@metrocast.net> writes:  >  <snip>> L >My impression is that the concept (and implementation) of hard partitioningG >long predates any DECpaq implementation:  it has been a feature of IBM @ >mainframes for quite a while, and I think moved into some other0 >non-mainframe systems before it came to DECpaq. > J >Galaxy's significant contribution was IIRC softer partitioning, includingL >the ability to migrate individual processors dynamically from one partitionI >to another in tens of microseconds, thus opening the door to *extremely* L >fine-grained dynamic load-balancing.  So one good question would be whether> >the Itanic MP hardware will continue to support this feature. >   L Thanks for the corrections from you and Rob.  I was a little frustrated thatG I had heard the announcement about partitoning, but heard no mention of , OpenVMS, hence my comment tacked on the end.   O I'm glad to hear that hp will support OpenVMS in that space (Superdome) in the  M future, contingent on Dale's qualification in his response to my inquiry.  As O you state above, Galaxy (APMP?) in that environment would be interesting, if it  were supported.    >- bill     A _________________________________________________________________ 0 Bradford J. Hamilton			"All opinions are my own"? bMradAhamiPltSon-at-coMmcAast.nPeSt	"Lose the MAPS, and replace 3 (please note the new e-mail address)	'-at-' with @"    ------------------------------  # Date: Thu, 03 Jul 2003 15:16:06 GMT 9 From: "Fred Kleinsorge" <my-last-name@stardotzko.dec.com> R Subject: Re: HP Webcast this morning on Next-Generation Intel Itanium 2 processors2 Message-ID: <WMXMa.3873$3f3.1461@news.cpqcorp.net>  & Found anyone who returns your respect?  5 "Bill Todd" <billtodd@metrocast.net> wrote in message , news:OeCdnQnBMY2fBZ6iXTWJiw@metrocast.net... > F > "Fred Kleinsorge" <my-last-name@stardotzko.dec.com> wrote in message- > news:mwBMa.3758$cS1.162@news.cpqcorp.net...  > > 9 > > "Bill Todd" <billtodd@metrocast.net> wrote in message 0 > > news:0BudncjFdqTCk5-iXTWJkA@metrocast.net... > > > I > > > Nope.  I suspect that if/when the Alpha team finally rescues Itanic  from > > its J > > > current core in 3 - 4 more years I'll have nothing left to disparage > here? > > > except cHumPaq's ethics (and the occasional dimwit post).  > > >  > > H > > You would reduce the occasional part by at least half if you stopped > > posting. > I > I'm happy to leave such judgements to people whom I respect.  And don't  give( > a shit about the judgements of others. >  > - bill >  >  >    ------------------------------  % Date: Thu, 03 Jul 2003 02:39:14 -0400 * From: JF Mezei <jfmezei.spamnot@istop.com>Y Subject: Re: HP Webcast this morning on Next-Generation Intel Itanium 2 processors proces ) Message-ID: <3F03CF92.8D76A789@istop.com>    Bill Todd wrote:K > Galaxy's significant contribution was IIRC softer partitioning, including M > the ability to migrate individual processors dynamically from one partition & > to another in tens of microseconds,   L What about shared memory between instances of VMS ? doesn't galaxy allow twoP instances of VMS to communicate via shared memory instead of ethernet or fibre ?   ------------------------------   Date: 3 Jul 2003 00:10:53 -0700 1 From: keithparris_NOSPAM@yahoo.com (Keith Parris) , Subject: Re: HP World (was HP to drop hpux?)= Message-ID: <cf15391e.0307022310.7717f4ac@posting.google.com>   [ JF Mezei <jfmezei.spamnot@istop.com> wrote in message news:<3F037CE5.A0ACFE62@istop.com>... K > Linux could do to HP-=UX and AIX and possibly Solaris what NT did to VMS.   C At one point not so long ago, I was thoroughly convinced that Linux @ meant the death of all proprietary UNIXes.  Now I think that was probably naive.   F There is a lot of added value in each of the proprietary UNIX systems,@ and very little incentive for their owners to move that advancedF technology into Linux and open-source it.  All their competitors wouldC benefit from their investment.  Just look at how upset SCO is right C now about the possibility of any Unix intellectual property or code  having moved into Linux.  B Can you see HP giving TruClusters code away to Linux?  (Compaq didD give away the NonStop Clusters for Unixware code, but I suspect that@ was probably only because it lost out in internal competition toE TruClusters.  But that's speculation on my part; I wasn't working for  Compaq when that happened.)   E HP sells ServiceGuard on Linux, but the ServiceGuard code is not open D source  (just like Oracle runs on Linux but that doesn't make Oracle
 open-source.)   < I now have serious doubts as to whether unfunded, spare-timeB enthusiasts can take Linux beyond where funded companies with paidB software engineers (and patent attorneys) can take the proprietary% UNIXes.  How can Linux ever catch up?   ; I suspect Linux will simply continue to provide a low-cost, , lower-capability entry point for Unix users.   ------------------------------  % Date: Thu, 03 Jul 2003 05:55:22 -0400 * From: JF Mezei <jfmezei.spamnot@istop.com>, Subject: Re: HP World (was HP to drop hpux?)) Message-ID: <3F03FD85.E7BDB6AB@istop.com>    Keith Parris wrote: E > At one point not so long ago, I was thoroughly convinced that Linux B > meant the death of all proprietary UNIXes.  Now I think that was > probably naive.   F Who could have thought that NT would kill VMS even though it is vastly' inferior, not even in the same league ?   H > There is a lot of added value in each of the proprietary UNIX systems,B > and very little incentive for their owners to move that advanced, > technology into Linux and open-source it.   N And there was very little incentive for Palmer to donate all of VMS's valuableK organs to  Microsoft, for Curly to donate all of Alpha's valuable organs to  Intel.    N Consider how HP-Compaq decided that the only way to survive was to cannabaliseJ their own products and choose at a very early stage the platforms/products& that they though would become popular.  M There is plenty of precedents already set, so if HP were to decide that Linux G will eventually eviscerate the underbelly of HP-UX, then I would not be K surprised to see HP start to donate lots of stuff to Linux, or perhaps make N proprietary add-ons to Linux to allow it to compete HP-branded against Solaris etc.     > All their competitors would   > benefit from their investment.  J Not if HP makes an HP branded version of Linux distribution which includesN lots of bells and whistles that runs only on IA64 things, preventing them from? being used on competitor's platforms (who won't be using IA64).   9 > Can you see HP giving TruClusters code away to Linux?     K Yes, that is the problem.  Carly and company make and repeat the point that G they want to build commodity stuff and get away from proprietary stuff.   > > I now have serious doubts as to whether unfunded, spare-timeD > enthusiasts can take Linux beyond where funded companies with paidD > software engineers (and patent attorneys) can take the proprietary' > UNIXes.  How can Linux ever catch up?   N HP, IBM and Dell could compete to fund universities, essentially paying hungry2 students to play with linux to develop new stuff.   = > I suspect Linux will simply continue to provide a low-cost, . > lower-capability entry point for Unix users.    L Yes, that is logical. And it was logical that windows should remain low end.H But you have people like Winkler at HP who do not subscribe to logic andA prefer to use gut feelings which are influenced by trade rags and  gartner-style predictions.   ------------------------------  # Date: Thu, 03 Jul 2003 17:02:58 GMT ; From: "John Gemignani, Jr." <jon-nope@thiswontworkossc.net>  Subject: iSCSI anyone?= Message-ID: <6lZMa.26115$Jw6.9846123@news1.news.adelphia.net>   H Is there anyone interested in running software-based iSCSI client and/orH server on OpenVMS?  I have some rather advanced work in this area and amJ seeking suggestions and needs on the way to productization.  In fact, when, ready, I could use a few test sites as well.   -John    --  
 ~~~~~~~~~~~~~  email: john AT o s s c DOT net   ------------------------------   Date: 3 Jul 2003 03:16:37 -0700 ) From: P.Young@unsw.EDU.AU (Patrick Young) ) Subject: LTO-2 Ultrium tape drive and VMS = Message-ID: <55f85d77.0307030216.550bbcd3@posting.google.com>   > We just received a Dell PowerVault 132T. LTO-2 library as Dell? are giving these to us quite cheaply. HP? got any OpenVMS ES47s  going cheap :-)   ! Works a treat under OpenVMS 7.3-1   : Just did some tests on an old AS600 with an Adaptec 29160.  @ Basically it looks like you get around 31MB/sec uncompressed and# anything up to 64MB/sec compressed:   / Random data compressed write to the tape drive:    $ r test+ %MOUNT-I-MOUNTED,  mounted on _TEST$MKA100:  Data to write (MB) : 2047  Time taken         :00:00:54.67  MB per second      : 37.4428   Fill every block with "A"s:    $ r test+ %MOUNT-I-MOUNTED,  mounted on _TEST$MKA100:  Data to write (MB) : 2047  Time taken         :00:00:31.81  MB per second      : 64.3508   Uncompressed random write:   $ r test+ %MOUNT-I-MOUNTED,  mounted on _TEST$MKA100:  Data to write (MB) : 2047  Time taken         :00:01:05.43  MB per second      : 31.2853   Stuff looks like:    $ sho mag mk100   H Magtape TEST$MKA100:, device type IBM ULTRIUM-TD2, is online, allocated,J     deallocate on dismount, mounted foreign, record-oriented device, file-O     oriented device, available to cluster, error logging is enabled, controller P     supports compaction (compaction enabled), device supports fastskip (per_io).  O     Error count                    0    Operations completed             874436 O     Owner process           "_TNA3:"    Owner UIC                      [SYSTEM] O     Owner process ID        0000009C    Dev Prot            S:RWPL,O:RWPL,G:R,W O     Reference count                3    Default buffer size               32767   O     Volume label            "      "    Relative volume no.                   0 O     Record size                    0    Transaction count                     1 O     Mount status             Process    Mount count                           1 $     ACP process name              ""O     Density                  default    Format                        Normal-11      Volume status:  odd parity.    $ robot show robot gk:   Robot Name: gk: Type: SCSI  4 Media Robot Identifier: DELL    PV-132T         109D   Slots:          23 Drives:         1  Inports:        1  Outports:       1  Transports:     1   ( Test proggie (lines will probably wrap):  F     %include "lib$routines" %from %library "sys$library:basic$starlet"A     %include "starlet" %from %library "sys$library:basic$starlet"   4     declare integer constant block_count = 65536%, &K                              block_size = 32767%      ! 2 GB to be written.   2     declare string constant tape_device = "mk100:"  ;     declare basic$quadword end_time, start_time, time_taken   :     declare integer content_count, count_blocks, data_size  #     declare string time_taken_ascii   6     map (data_block) string block_content = block_size  =     ! Generate random block content of characters A through Z   
     randomize   (     for content_count = 1% to block_sizeM         let mid$(block_content, content_count, 1%) = chr$(int((rnd * 26%) + &              65%))      next content_count       ! Mount tape  J     call lib$spawn("mount/foreign " + tape_device + "/blocksize=" + str$ &2         (block_size) + "/media_format=compaction")  K     open tape_device for output as file #1%, map data_block, organization &          sequential fixed       ! Get time       call sys$gettim(start_time)        ! Write blocks  (     for count_blocks = 1% to block_count           put #1%        next count_blocks        ! Get time       call sys$gettim(end_time)        ! Subtract time   8     call lib$sub_times(end_time, start_time, time_taken),     let time_taken_ascii = string$(11%, 32%)6     call sys$asctim(,time_taken_ascii, time_taken, 1%)       ! Report details  9     let data_size = block_count * block_size / 1024% ^ 2%   +     print "Data to write (MB) :"; data_size 2     print "Time taken         :"; time_taken_ascii  O     print "MB per second      :"; data_size / (val(mid$(time_taken_ascii, 7%, & 9         5%)) + val(mid$(time_taken_ascii, 4%, 2%)) * 60%)        ! Dismount tape   
     close #1%   6     call lib$spawn("dismount/nounload " + tape_device)       end program    ------------------------------   Date: 3 Jul 2003 06:53:19 -0700 % From: Bart.Zorn@xs4all.nl (Bart Zorn) - Subject: Re: LTO-2 Ultrium tape drive and VMS = Message-ID: <a98cd882.0307030553.25b2a4ba@posting.google.com>    Interesting!  D I understood that the problem with LTO drives until now is that they@ do not support small blocks and thus cannot support ANSI labels.  0 Did you try to use BACKUP to write to the drive?   Thanks,   	 Bart Zorn   n P.Young@unsw.EDU.AU (Patrick Young) wrote in message news:<55f85d77.0307030216.550bbcd3@posting.google.com>...@ > We just received a Dell PowerVault 132T. LTO-2 library as DellA > are giving these to us quite cheaply. HP? got any OpenVMS ES47s  > going cheap :-)  > # > Works a treat under OpenVMS 7.3-1  > < > Just did some tests on an old AS600 with an Adaptec 29160. > B > Basically it looks like you get around 31MB/sec uncompressed and% > anything up to 64MB/sec compressed:  > 1 > Random data compressed write to the tape drive:  > 
 > $ r test- > %MOUNT-I-MOUNTED,  mounted on _TEST$MKA100:  > Data to write (MB) : 2047 ! > Time taken         :00:00:54.67  > MB per second      : 37.4428 >  > Fill every block with "A"s:  > 
 > $ r test- > %MOUNT-I-MOUNTED,  mounted on _TEST$MKA100:  > Data to write (MB) : 2047 ! > Time taken         :00:00:31.81  > MB per second      : 64.3508 >  > Uncompressed random write: > 
 > $ r test- > %MOUNT-I-MOUNTED,  mounted on _TEST$MKA100:  > Data to write (MB) : 2047 ! > Time taken         :00:01:05.43  > MB per second      : 31.2853 >  > Stuff looks like:  >  > $ sho mag mk100  > J > Magtape TEST$MKA100:, device type IBM ULTRIUM-TD2, is online, allocated,L >     deallocate on dismount, mounted foreign, record-oriented device, file-Q >     oriented device, available to cluster, error logging is enabled, controller R >     supports compaction (compaction enabled), device supports fastskip (per_io). > Q >     Error count                    0    Operations completed             874436 Q >     Owner process           "_TNA3:"    Owner UIC                      [SYSTEM] Q >     Owner process ID        0000009C    Dev Prot            S:RWPL,O:RWPL,G:R,W Q >     Reference count                3    Default buffer size               32767  > Q >     Volume label            "      "    Relative volume no.                   0 Q >     Record size                    0    Transaction count                     1 Q >     Mount status             Process    Mount count                           1 & >     ACP process name              ""Q >     Density                  default    Format                        Normal-11  >  >   Volume status:  odd parity.  >  > $ robot show robot gk: >  > Robot Name: gk: Type: SCSI > 6 > Media Robot Identifier: DELL    PV-132T         109D >  > Slots:          23 > Drives:         1  > Inports:        1  > Outports:       1  > Transports:     1  > * > Test proggie (lines will probably wrap): > H >     %include "lib$routines" %from %library "sys$library:basic$starlet"C >     %include "starlet" %from %library "sys$library:basic$starlet"  > 6 >     declare integer constant block_count = 65536%, &M >                              block_size = 32767%      ! 2 GB to be written.  > 4 >     declare string constant tape_device = "mk100:" > = >     declare basic$quadword end_time, start_time, time_taken  > < >     declare integer content_count, count_blocks, data_size > % >     declare string time_taken_ascii  > 8 >     map (data_block) string block_content = block_size > ? >     ! Generate random block content of characters A through Z  >  >     randomize  > * >     for content_count = 1% to block_sizeO >         let mid$(block_content, content_count, 1%) = chr$(int((rnd * 26%) + &  >             65%))  >     next content_count >  >     ! Mount tape > L >     call lib$spawn("mount/foreign " + tape_device + "/blocksize=" + str$ &4 >         (block_size) + "/media_format=compaction") > M >     open tape_device for output as file #1%, map data_block, organization &  >         sequential fixed >  >     ! Get time > ! >     call sys$gettim(start_time)  >  >     ! Write blocks > * >     for count_blocks = 1% to block_count >  >         put #1%  >  >     next count_blocks  >  >     ! Get time >  >     call sys$gettim(end_time)  >  >     ! Subtract time  > : >     call lib$sub_times(end_time, start_time, time_taken). >     let time_taken_ascii = string$(11%, 32%)8 >     call sys$asctim(,time_taken_ascii, time_taken, 1%) >  >     ! Report details > ; >     let data_size = block_count * block_size / 1024% ^ 2%  > - >     print "Data to write (MB) :"; data_size 4 >     print "Time taken         :"; time_taken_ascii > Q >     print "MB per second      :"; data_size / (val(mid$(time_taken_ascii, 7%, & ; >         5%)) + val(mid$(time_taken_ascii, 4%, 2%)) * 60%)  >  >     ! Dismount tape  >  >     close #1%  > 8 >     call lib$spawn("dismount/nounload " + tape_device) >  >     end program    ------------------------------  $ Date: Thu, 3 Jul 2003 10:19:15 -0400# From: "Dan Allen" <dallen@nist.gov> - Subject: RE: LTO-2 Ultrium tape drive and VMS : Message-ID: <JFEPKAPBPMDFDBOIANGDOEGCDJAA.dallen@nist.gov>   > -----Original Message-----. > From: Bart Zorn [mailto:Bart.Zorn@xs4all.nl]' > Sent: Thursday, July 03, 2003 9:53 AM  > To: Info-VAX@Mvb.Saic.Com / > Subject: Re: LTO-2 Ultrium tape drive and VMS  >  >  > Interesting! > F > I understood that the problem with LTO drives until now is that theyB > do not support small blocks and thus cannot support ANSI labels. >   D 	First I've heard that. Previous posts here have identified odd byteD 	transfers as the problem - supposedly supported by LTO-2. I have anG 	LTO-2 library on a Dell Windows server here and using Veritas it's PDF % 	(about 70MB/sec without any tuning).    	Dan   2 > Did you try to use BACKUP to write to the drive? > 	 > Thanks,  >  > Bart Zorn  > p > P.Young@unsw.EDU.AU (Patrick Young) wrote in message news:<55f85d77.0307030216.550bbcd3@posting.google.com>...B > > We just received a Dell PowerVault 132T. LTO-2 library as DellC > > are giving these to us quite cheaply. HP? got any OpenVMS ES47s  > > going cheap :-)  > > % > > Works a treat under OpenVMS 7.3-1  > > > > > Just did some tests on an old AS600 with an Adaptec 29160. > > D > > Basically it looks like you get around 31MB/sec uncompressed and' > > anything up to 64MB/sec compressed:  > > 3 > > Random data compressed write to the tape drive:  > >  > > $ r test/ > > %MOUNT-I-MOUNTED,  mounted on _TEST$MKA100:  > > Data to write (MB) : 2047 # > > Time taken         :00:00:54.67   > > MB per second      : 37.4428 > >  > > Fill every block with "A"s:  > >  > > $ r test/ > > %MOUNT-I-MOUNTED,  mounted on _TEST$MKA100:  > > Data to write (MB) : 2047 # > > Time taken         :00:00:31.81   > > MB per second      : 64.3508 > >  > > Uncompressed random write: > >  > > $ r test/ > > %MOUNT-I-MOUNTED,  mounted on _TEST$MKA100:  > > Data to write (MB) : 2047 # > > Time taken         :00:01:05.43   > > MB per second      : 31.2853 > >  > > Stuff looks like:  > >  > > $ sho mag mk100  > > L > > Magtape TEST$MKA100:, device type IBM ULTRIUM-TD2, is online, allocated,N > >     deallocate on dismount, mounted foreign, record-oriented device, file-S > >     oriented device, available to cluster, error logging is enabled, controller T > >     supports compaction (compaction enabled), device supports fastskip (per_io). > > S > >     Error count                    0    Operations completed             874436 S > >     Owner process           "_TNA3:"    Owner UIC                      [SYSTEM] S > >     Owner process ID        0000009C    Dev Prot            S:RWPL,O:RWPL,G:R,W S > >     Reference count                3    Default buffer size               32767  > > S > >     Volume label            "      "    Relative volume no.                   0 S > >     Record size                    0    Transaction count                     1 S > >     Mount status             Process    Mount count                           1 ( > >     ACP process name              ""S > >     Density                  default    Format                        Normal-11  > > ! > >   Volume status:  odd parity.  > >  > > $ robot show robot gk: > >  > > Robot Name: gk: Type: SCSI > > 8 > > Media Robot Identifier: DELL    PV-132T         109D > >  > > Slots:          23 > > Drives:         1  > > Inports:        1  > > Outports:       1  > > Transports:     1  > > , > > Test proggie (lines will probably wrap): > > J > >     %include "lib$routines" %from %library "sys$library:basic$starlet"E > >     %include "starlet" %from %library "sys$library:basic$starlet"  > > 8 > >     declare integer constant block_count = 65536%, &O > >                              block_size = 32767%      ! 2 GB to be written.  > > 6 > >     declare string constant tape_device = "mk100:" > > ? > >     declare basic$quadword end_time, start_time, time_taken  > > > > >     declare integer content_count, count_blocks, data_size > > ' > >     declare string time_taken_ascii  > > : > >     map (data_block) string block_content = block_size > > A > >     ! Generate random block content of characters A through Z  > >  > >     randomize  > > , > >     for content_count = 1% to block_sizeQ > >         let mid$(block_content, content_count, 1%) = chr$(int((rnd * 26%) + &  > >             65%))  > >     next content_count > >  > >     ! Mount tape > > N > >     call lib$spawn("mount/foreign " + tape_device + "/blocksize=" + str$ &6 > >         (block_size) + "/media_format=compaction") > > O > >     open tape_device for output as file #1%, map data_block, organization &  > >         sequential fixed > >  > >     ! Get time > > # > >     call sys$gettim(start_time)  > >  > >     ! Write blocks > > , > >     for count_blocks = 1% to block_count > >  > >         put #1%  > >  > >     next count_blocks  > >  > >     ! Get time > > ! > >     call sys$gettim(end_time)  > >  > >     ! Subtract time  > > < > >     call lib$sub_times(end_time, start_time, time_taken)0 > >     let time_taken_ascii = string$(11%, 32%): > >     call sys$asctim(,time_taken_ascii, time_taken, 1%) > >  > >     ! Report details > > = > >     let data_size = block_count * block_size / 1024% ^ 2%  > > / > >     print "Data to write (MB) :"; data_size 6 > >     print "Time taken         :"; time_taken_ascii > > S > >     print "MB per second      :"; data_size / (val(mid$(time_taken_ascii, 7%, & = > >         5%)) + val(mid$(time_taken_ascii, 4%, 2%)) * 60%)  > >  > >     ! Dismount tape  > >  > >     close #1%  > > : > >     call lib$spawn("dismount/nounload " + tape_device) > >  > >     end program    ------------------------------  $ Date: Thu, 3 Jul 2003 09:51:34 +0200 From: "vn" <zool@zool.com>" Subject: Re: Mount a backup /image4 Message-ID: <3f03e082$0$29666$626a54ce@news.free.fr>  & Yes it's a standalone backup of a VAX.J I made a confusion between the backup /image where /select qualifier isn'tL allowed and a simple backup restore of this image saveset without the /image# qualifier where select is admitted.   K It's definitely useless to spend time to mount a saveset like a device when  so simple ways exists.  	 Thank you       G "Bob Koehler" <koehler@eisner.nospam.encompasserve.org> a crit dans le 9 message de news: VrMXJNFCeO8+@eisner.encompasserve.org... K > In article <3f030c3a$0$29623$626a54ce@news.free.fr>, "vn" <zool@zool.com>  writes:  > > Hi,  > > J > > Is it possible to mount a saveset on a tape, saved with backup /image, like > > a device ? > 2 >    No, unless you intend to write a lot of code. > A > > Or is there any solution to recover a single file in a backup * > > /image without restore an entire disk? > A >    Yes.  You can recover any single file from any backup except H >    /physical by using /select.  A save set created /image is fine with* >    restore using /select and not /image. > E >    The only situation you need to worry about is the VAX Standalone G >    BACKUP.  That software always does /image.  But it would be absurd E >    to boot Standalone BACKUP to do a single file restore even if it I >    could do it.  There's no problem using the online VMS BACKUP command D >    to /select even if the /image was made using Standalone BACKUP. >    ------------------------------   Date: 3 Jul 2003 07:41:03 -0700 1 From: susan_skonetski@hotmail.com (Sue Skonetski) 2 Subject: New Oracle documents available on the web= Message-ID: <857e9e41.0307030641.68781cdd@posting.google.com>    Dear Newsgroup, C I can not include the file so you will have to look on the web.  As F always you are getting this real time, so it may take a little bit for0 it to make it on the web and around the company.  
 Warm Regards,  Sue * __________________________________________  F Can you please use the attache .doc file to update our Oracle web pageE (http://h71000.www7.hp.com/solutions/oracle/index.html)? It should go F under "business partner relationship", replacing the "Oracle  OpenVMS0 statement of direction (October 2002)" document.   B Also, under "ORACLE database solutions on OpenVMS" you can place aG pointer to this URL http://www.oracle.com/peoplesoft/Rdb_CaseStudyE.pdf ? with title "Nine Years Later: Thousands of Satisfied Oracle Rdb  Customers".    E Sue, You may want to distribute the above to your distribution lists, ? internal and external ones. The first documents Oracle Server's F continued support of OpenVMS/Alpha platform and porting to Itanium.TheF second is a great document about Oracle's continued support of the Rdb product    ------------------------------  # Date: Thu, 03 Jul 2003 17:27:49 GMT & From: hoffman@hp.nospam (Hoff Hoffman)+ Subject: OpenVMS FAQ and FAQ Website Errata 2 Message-ID: <pIZMa.3901$bl3.1737@news.cpqcorp.net>  K   Text, Postscript, Bookreader, HTML, and related formats and the aggregate I   FAQ zip archive for the June 2003 edition of the OpenVMS FAQ should all    be available at the:  %     http://www.hp.com/go/openvms/faq/   J   website Real Soon Now -- this is a new (direct) URL referencing the FAQ,J   too.  (If you have pointers to the FAQ at your website(s), please update%   them to use this new (direct) URL.)   I   Yes, I know that the version of the FAQ that is presently posted at the I   FAQ website is not (yet) the June 2003 edition.  (I decided to post the I   text-format FAQ without first waiting for the OpenVMS FAQ website to be    updated.  Get over it. :-)  J   FAQ-related comments and corrections and updates are welcome, of course.  N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faq N  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.com    ------------------------------  # Date: Thu, 03 Jul 2003 17:09:19 GMTe2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman); Subject: OpenVMS Frequently Asked Questions (FAQ), Part 1/9e2 Message-ID: <3rZMa.3891$bl3.3745@news.cpqcorp.net>                                           >                    The OpenVMS Frequently Asked Questions(FAQ)                            ABSTRACTe  J                    This document contains answers to many common questionsG                    on the OpenVMS operating system, and covers OpenVMS,eA                    and OpenVMS running on Itanium, Alpha, and VAX/                    hardware.        ?                    Revision/Update Information   OpenVMS V7.3-1t  H                    Revision/Update Information:  Revision Date/June 2003                                                  FAQ t  9                            J           ________________________________________________________________             Contents  J                 __________________________________________________________J                 PREFACE                                                  i  J                 __________________________________________________________J                 OPENVMS FAQ                                            iii  J           ________________________________________________________________J           CHAPTER 1  INTRODUCTION                                      1-1  J                 __________________________________________________________J                 1.1   WHAT CORE OPENVMS URLS DO YOU NEED TO KNOW?      1-1  J                 __________________________________________________________J                 1.2   WHAT ARE THE OPENVMS USENET NEWSGROUPS?          1-2>                 1.2.1     What is the scope of the comp.os.vmsJ                           newsgroup?                                   1-2;                 1.2.2     What newsgroups carry VMS-relatedAJ                           information?                                 1-2J                 1.2.3     What newsgroup archives are available?       1-3J                 1.2.4     What is the INFO-VAX mailing list?           1-3F                 1.2.4.1      How do I subscribe to or unsubscribe from+                              INFO-VAX?, 1-4(  J                 __________________________________________________________J                 1.3   WHAT IS [N]ETIQUETTE?                            1-5  J                 __________________________________________________________J                 1.4   WHAT OPENVMS USER GROUP(S) ARE AVAILABLE?        1-8  J                 __________________________________________________________J                 1.5   OPENVMS SUPPORT, QUESTIONS AND COMMENTS?         1-9A                 1.5.1     Corporate contacts for OpenVMS BusinessaJ                           Issues?                                      1-9J                 1.5.2     OpenVMS Ambassadors?                        1-10B                 1.5.3     Contact for OpenVMS Marketing Issues andJ                           Questions?                                  1-10<                 1.5.4     Contact URLs for OpenVMS TechnicalJ                           Issues?                                     1-10      J                                                                        iii e  g                              Contents         J           ________________________________________________________________J           CHAPTER 2  GENERAL INFORMATION                               2-1  J                 __________________________________________________________J                 2.1   WHAT IS OPENVMS? WHAT IS ITS HISTORY?            2-1  J                 __________________________________________________________<                 2.2   WHAT IS THE DIFFERENCE BETWEEN VMS ANDJ                       OPENVMS?                                         2-2J                 2.2.1     How do I port from VMS to OpenVMS?           2-3  J                 __________________________________________________________J                 2.3   WHICH IS BETTER, OPENVMS OR UNIX?                2-3  J                 __________________________________________________________>                 2.4   IS HP CONTINUING FUNDING AND SUPPORT FORJ                       OPENVMS?                                         2-4  J                 __________________________________________________________?                 2.5   WHAT OPENVMS CD-ROM DISTRIBUTION KITS ARE J                       AVAILABLE?                                       2-4  J                 __________________________________________________________J                 2.6   IN WHAT LANGUAGE IS OPENVMS WRITTEN?             2-6  J                 __________________________________________________________J                 2.7   OBTAINING AND TRANSFERING OPENVMS LICENSEES?     2-6=                 2.7.1     Questions asked by Hobbyist OpenVMSrJ                           licensees?                                   2-7J                 2.7.2     OpenVMS Educational and CSLG licenses?       2-8@                 2.7.3     How do I obtain or transfer an OpenVMSJ                           license?                                     2-8  J                 __________________________________________________________<                 2.8   DOES OPENVMS SUPPORT THE EURO CURRENCYJ                       SYMBOL?                                          2-8  J                 __________________________________________________________E                 2.9   WHY HASN'T OPENVMS BEEN PORTED TO INTEL (IA-32) J                       SYSTEMS?                                         2-9  J                 __________________________________________________________>                 2.10  ARE THERE ANY NETWORK-ACCESSIBLE OPENVMSJ                       SYSTEMS?                                         2-9  J                 __________________________________________________________J                 2.11  WHAT VERSION OF OPENVMS DO I NEED?              2-10                      ivo    t                              Contentsi        J                 __________________________________________________________J                 2.12  HOW CAN I SUBMIT OPENVMS FREEWARE?              2-11  J                 __________________________________________________________J                 2.13  PORTING APPLICATIONS TO OPENVMS?                2-12  J                 __________________________________________________________F                 2.14  WHAT RESOURCES ARE AVAILABLE TO OPENVMS SOFTWAREJ                       DEVELOPERS?                                     2-13  J                 __________________________________________________________E                 2.15  MEMORY MANAGEMENT, RESOURCE MANAGEMENT, PROCESSrJ                       SCHEDULING, ETC?                                2-14  J           ________________________________________________________________J           CHAPTER 3  DOCUMENTATION                                     3-1  J                 __________________________________________________________?                 3.1   WHERE CAN I FIND ONLINE COPIES OF OPENVMS J                       MANUALS?                                         3-1  J                 __________________________________________________________>                 3.2   WHAT ONLINE INFORMATION AND WEBSITES AREJ                       AVAILABLE?                                       3-1  J                 __________________________________________________________;                 3.3   OPENVMS PRODUCT INFORMATION TELEPHONE J                       NUMBERS?                                         3-5  J                 __________________________________________________________H                 3.4   HOW DO I EXTRACT THE CONTENTS OF A HELP TOPIC TO AJ                       TEXT FILE?                                       3-6  J                 __________________________________________________________;                 3.5   DOES OPENVMS MARKETING HAVE AN E-MAILiJ                       ADDRESS?                                         3-6  J                 __________________________________________________________?                 3.6   WHERE CAN I LEARN ABOUT OPENVMS EXECUTIVEmJ                       INTERNALS?                                       3-6  J                 __________________________________________________________I                 3.7   WHERE CAN NEW USERS FIND TUTORIAL INFORMATION ABOUT7J                       OPENVMS?                                         3-7J                 3.7.1     Tutorial Websites?                           3-7J                 3.7.2     Books and Tutorials?                         3-9  J                                                                          v o  e                              Contentsb        J                 __________________________________________________________J                 3.8   WHAT OPENVMS MAILING LISTS ARE AVAILABLE?       3-10  J                 __________________________________________________________D                 3.9   WHAT IS THIS ASK THE WIZARD WEBSITE I'VE HEARDJ                       ABOUT?                                          3-12  J                 __________________________________________________________>                 3.10  ACCESS TO THE OPENVMS NETSCAPE NAVIGATORJ                       DOCUMENTATION?                                  3-13  J           ________________________________________________________________J           CHAPTER 4  TIME AND TIMEKEEPING                              4-1  J                 __________________________________________________________F                 4.1   UTC VS GMT VS VS UT1/UT1/UT2 TDF? WHAT ARE THESEJ                       ACRONYMS?                                        4-1  J                 __________________________________________________________=                 4.2   A BRIEF HISTORY OF OPENVMS TIMEKEEPING,sJ                       PLEASE?                                          4-27                 4.2.1     Details of the OpenVMS system0J                           time-keeping?                                4-4F                 4.2.1.1      VAX hardware time-keeping details..., 4-4,                 4.2.1.1.1     TOY clock, 4-41                 4.2.1.1.2     EXE$GQ_SYSTIME, 4-4t2                 4.2.1.1.3     EXE$GQ_TODCBASE, 4-4.                 4.2.1.1.4     EXE$GL_TODR, 4-4H                 4.2.1.2      Alpha hardware time-keeping details..., 4-5G                 4.2.1.2.1     Battery-Backed Watch (BB_WATCH) Chip, 4-6u1                 4.2.1.2.2     EXE$GQ_SYSTIME, 4-6e7                 4.2.1.2.3     EXE$GQ_SAVED_HWCLOCK, 4-6dI                 4.2.1.3      Why does VAX need a SET TIME at least once a '                              year?, 4-7'>                 4.2.2     How does OpenVMS VAX maintain systemJ                           time?                                        4-7  J                 __________________________________________________________J                 4.3   KEEPING THE OPENVMS SYSTEM TIME SYNCHRONIZED?    4-8J                 4.3.1     Why does my OpenVMS system time drift?      4-10<                 4.3.2     How can I drift the OpenVMS systemJ                           time?                                       4-10A                 4.3.3     How can I configure TCP/IP Services NTP J                           as a time provider?                         4-11                      viv m  .                              Contentso        J                 __________________________________________________________H                 4.4   MANAGING TIMEZONES, TIMEKEEPING, UTC, AND DAYLIGHTJ                       SAVINGS?                                        4-13=                 4.4.1     How to troubleshoot TDF problems onkJ                           OpenVMS?                                    4-169                 4.4.2     Customizing your TDF (Timezone)sJ                           Setting?                                    4-17  J                 __________________________________________________________G                 4.5   WHY DOES THE SET TIME COMMAND FAIL? HELP MANAGINGnJ                       DTSS?                                           4-18  J           ________________________________________________________________J           CHAPTER 5  SYSTEM MANAGEMENT INFORMATION                     5-1  J                 __________________________________________________________J                 5.1   WHAT IS AN INSTALLED IMAGE?                      5-1  J                 __________________________________________________________J                 5.2   ARE THERE ANY KNOWN VIRUSES FOR OPENVMS?         5-2  J                 __________________________________________________________J                 5.3   HOW DO I MOUNT AN ISO-9660 CD ON OPENVMS?        5-3  J                 __________________________________________________________J                 5.4   HOW DO I EXTRACT THE CONTENTS OF A PCSI KIT?     5-4  J                 __________________________________________________________E                 5.5   I'VE FORGOTTEN THE SYSTEM PASSWORD - WHAT CAN I J                       DO?                                              5-5  J                 __________________________________________________________A                 5.6   HOW DO I CHANGE THE NODE NAME OF AN OPENVMSDJ                       SYSTEM?                                          5-8  J                 __________________________________________________________C                 5.7   WHY DOESN'T OPENVMS SEE THE NEW MEMORY I JUSTeJ                       ADDED?                                          5-10  J                 __________________________________________________________>                 5.8   HOW DO I CHANGE THE TEXT IN A USER'S UICJ                       IDENTIFIER?                                     5-10    J                                                                        vii :  .                              Contents         J                 __________________________________________________________J                 5.9   WHAT ARE THE OPENVMS VERSION UPGRADE PATHS?     5-12J                 5.9.1     OpenVMS Alpha Upgrade (or Update) Paths     5-12J                 5.9.2     OpenVMS VAX Release Upgrade Paths           5-14J                 5.9.3     OpenVMS Cluster Rolling Upgrade Paths       5-15=                 5.9.4     OpenVMS Product Version and SupporteJ                           Information                                 5-15J                 5.9.5     OpenVMS Alpha Terminology                   5-16  J                 __________________________________________________________E                 5.10  WHY DO I HAVE A NEGATIVE NUMBER IN THE PAGEFILE J                       RESERVABLE PAGES?                               5-17  J                 __________________________________________________________H                 5.11  DO I HAVE TO UPDATE LAYERED PRODUCTS WHEN UPDATINGJ                       OPENVMS?                                        5-18  J                 __________________________________________________________J                 5.12  HOW DO I CHANGE THE VOLUME LABEL OF A DISK?     5-19  J                 __________________________________________________________J                 5.13  HOW CAN I SET UP A SHARED DIRECTORY?            5-20  J                 __________________________________________________________=                 5.14  WHY DO I GET EXTRA BLANK PAGES ON MY HP J                       PRINTER?                                        5-21  J                 __________________________________________________________?                 5.15  DRIVERS AND CONFIGURATION OF NEW GRAPHICSiJ                       CONTROLLERS?                                    5-21J                 5.15.1    The ELSA GLoria Synergy                     5-22J                 5.15.2    PowerStorm 300, PowerStorm 350              5-23J                 5.15.3    PowerStorm 3D30, PowerStorm 4D20            5-23J                 5.15.4    Radeon 7500                                 5-23  J                 __________________________________________________________C                 5.16  HOW CAN I ACQUIRE OPENVMS PATCHES, FIXES, ANDlJ                       ECOS?                                           5-24  J                 __________________________________________________________J                 5.17  HOW DO I MOVE THE QUEUE MANAGER DATABASE?       5-25  J                 __________________________________________________________H                 5.18  HOW DO I DELETE AN UNDELETABLE/UNSTOPPABLE (RWAST)J                       PROCESS?                                        5-26                      viii                                    Contents         J                 __________________________________________________________J                 5.19  HOW DO I RESET THE ERROR COUNT(S)?              5-27  J                 __________________________________________________________B                 5.20  HOW DO I FIND OUT IF THE TAPE DRIVE SUPPORTSJ                       COMPRESSION?                                    5-29  J                 __________________________________________________________F                 5.21  CAN I COPY SYSUAF TO ANOTHER VERSION? TO VAX? TOJ                       ALPHA?                                          5-29  J                 __________________________________________________________J                 5.22  HOW DO I DELETE (TIMEOUT) IDLE PROCESSES?       5-32  J                 __________________________________________________________C                 5.23  DO I NEED A PAK FOR THE DECEVENT (HP ANALYZE) J                       TOOL?                                           5-32  J                 __________________________________________________________;                 5.24  INITIALIZE ACCVIO AND ANSI TAPE LABELtJ                       SUPPORT?                                        5-33  J                 __________________________________________________________J                 5.25  HOW DO I RECOVER FROM INSVIRMEM ERRORS?         5-33  J                 __________________________________________________________C                 5.26  HOW CAN I PREVENT A SERIAL TERMINAL LINE FROM J                       INITIATING A LOGIN?                             5-34  J                 __________________________________________________________=                 5.27  HOW DOES PCSI USE THE IMAGE BUILD_IDENT6J                       FIELD?                                          5-34  J                 __________________________________________________________C                 5.28  HOW CAN I TELL WHAT SOFTWARE (AND VERSION) IS J                       INSTALLED?                                      5-36  J                 __________________________________________________________@                 5.29  WHAT FILE CHECKSUM TOOLS ARE AVAILABLE FORJ                       OPENVMS?                                        5-37  J                 __________________________________________________________@                 5.30  WHAT (AND WHERE) IS THE OPENVMS MANAGEMENTJ                       STATION?                                        5-37  J                 __________________________________________________________A                 5.31  HOW TO DETERMINE CURRENT DISK FRAGMENTATION,J                       LEVEL?                                          5-37  J                                                                         ix                                   Contents         J                 __________________________________________________________<                 5.32  SYSBOOT-I-FILENOTLOC, UNABLE TO LOCATEJ                       SYS$CPU_ROUTINES?                               5-38  J                 __________________________________________________________G                 5.33  HOW CAN I CUSTOMIZE THE DCPS DEVICE CONTROL FOR A J                       NEW PRINTER?                                    5-38  J                 __________________________________________________________J                 5.34  WHY DO $GETDEV MOUNTCNT AND SHOW DEVICE MOUNT COUNTSJ                       DIFFER?                                         5-40  J                 __________________________________________________________<                 5.35  WHAT SOFTWARE IS NEEDED FOR POSTSCRIPTJ                       PRINTERS?                                       5-40  J                 __________________________________________________________B                 5.36  HOW DO I REMOVE A PCSI-INSTALLED PATCH (ECO)J                       KIT?                                            5-40  J                 __________________________________________________________>                 5.37  SYSINIT-E, ERROR MOUNTING SYSTEM DEVICE,J                       STATUS=0072832C                                 5-41  J                 __________________________________________________________J                 5.38  RESOLVING LICENSE PAK PROBLEMS?                 5-41  J                 __________________________________________________________J                 5.39  CHANGING THE OPENVMS VERSION NUMBER?            5-43  J                 __________________________________________________________@                 5.40  HOW TO PREVENT USERS FROM CHOOSING OBVIOUSJ                       PASSWORDS?                                      5-43  J                 __________________________________________________________<                 5.41  PLEASE HELP ME WITH THE OPENVMS BACKUPJ                       UTILITY?                                        5-45J                 5.41.1    Why isn't BACKUP/SINCE=BACKUP working?      5-45F                 5.41.1.1     Why has OpenVMS gone through the agony of/                              this change?, 5-46oA                 5.41.1.2     Can you get the old BACKUP behaviour (                              back?, 5-469                 5.41.2    What can I do to improve BACKUPiJ                           performance?                                5-46J                 5.41.3    Why is BACKUP not working as expected?      5-47J                 5.41.4    How do I fix a corrupt BACKUP saveset?      5-48                      x m  a                              Contents         >                 5.41.5    How do I write a BACKUP saveset to aJ                           remote tape?                                5-50J                 5.41.6    How to perform a security disk erasure?     5-51J                 5.41.7    How to enable telnet virtual terminals?     5-51    J           ________________________________________________________________J           CHAPTER 6  INFORMATION ON MAIL                               6-1  J                 __________________________________________________________I                 6.1   MAIL KEEPS SAYING I HAVE NEW MESSAGES, BUT I DON'T.0J                       WHAT DO I DO?                                    6-1  J                 __________________________________________________________>                 6.2   HOW DO I SEND OR READ ATTACHMENTS IN VMSJ                       MAIL?                                            6-1  J                 __________________________________________________________J                 6.3   HOW CAN I BLOCK SMTP MAIL RELAY SPAM?            6-3  J           ________________________________________________________________J           CHAPTER 7  INFORMATION ON UTILITIES                          7-1  J                 __________________________________________________________J                 7.1   HOW DO I PLAY AN AUDIO CD ON MY WORKSTATION?     7-1  J                 __________________________________________________________J                 7.2   HOW DO I ACCESS A MICROSOFT WINDOWS FLOPPY DISK FROMJ                       OPENVMS?                                         7-2  J                 __________________________________________________________C                 7.3   HOW DO I PLAY SOUND FILES ON AN ALPHASTATION? J                       DECSOUND DOESN'T WORK.                           7-2  J                 __________________________________________________________J                 7.4   WHY IS DECMIGRATE NOT WORKING WITH FORTRAN?      7-3  J                 __________________________________________________________J                 7.5   HOW DO I READ IBM EBCDIC TAPES ON OPENVMS?       7-3  J                 __________________________________________________________J                 7.6   HOW CAN I PATCH AN OPENVMS ALPHA IMAGE?          7-4    J                                                                         xi                                   Contents         J           ________________________________________________________________J           CHAPTER 8  DCL DETAILS                                       8-1  J                 __________________________________________________________J                 8.1   HOW DO I RUN A PROGRAM WITH ARGUMENTS?           8-1  J                 __________________________________________________________J                 8.2   HOW CAN I CLEAR THE SCREEN IN DCL?               8-2  J                 __________________________________________________________A                 8.3   USING REPLY/LOG FROM DCL? DISABLING CONSOLEtJ                       OPCOMS?                                          8-2  J                 __________________________________________________________J                 8.4   HOW DO I GENERATE A RANDOM NUMBER IN DCL?        8-3  J                 __________________________________________________________J                 8.5   WHAT DOES THE MCR COMMAND DO?                    8-4  J                 __________________________________________________________J                 8.6   HOW DO I CHANGE THE OPENVMS SYSTEM PROMPT?       8-5  J                 __________________________________________________________E                 8.7   CAN I DO DECNET TASK-TO-TASK COMMUNICATION WITHDJ                       DCL?                                             8-6  J                 __________________________________________________________:                 8.8   HOW CAN I GET THE WIDTH SETTING OF AJ                       TERMINAL?                                        8-6  J                 __________________________________________________________J                 8.9   HOW CAN I SUBSTITUTE SYMBOLS IN A PIPE?          8-7  J                 __________________________________________________________>                 8.10  USE OF RUN/DETACH, LOGINOUT, AND LOGICALJ                       NAMES?                                           8-7  J                 __________________________________________________________A                 8.11  HOW TO USE ESCAPE AND CONTROL CHARACTERS IN J                       DCL?                                             8-8                            xii t  _                              Contentse        J           ________________________________________________________________J           CHAPTER 9  FILES                                             9-1  J                 __________________________________________________________J                 9.1   HOW CAN I UNDELETE A FILE?                       9-1  J                 __________________________________________________________F                 9.2   WHY DOES SHOW QUOTA GIVE A DIFFERENT ANSWER THANJ                       DIR/SIZE?                                        9-1  J                 __________________________________________________________J                 9.3   HOW DO I MAKE SURE THAT MY DATA IS SAFELY WRITTEN TOJ                       DISK?                                            9-2  J                 __________________________________________________________D                 9.4   WHAT ARE THE LIMITS ON FILE SPECIFICATIONS ANDJ                       DIRECTORIES?                                     9-3  J                 __________________________________________________________F                 9.5   WHAT IS THE LARGEST DISK VOLUME SIZE OPENVMS CANJ                       ACCESS?                                          9-4  J                 __________________________________________________________G                 9.6   WHAT IS THE MAXIMUM FILE SIZE, AND THE RMS RECORDuJ                       SIZE LIMIT?                                      9-6  J                 __________________________________________________________B                 9.7   HOW DO I WRITE CD-RECORDABLE OR DVD MEDIA ONJ                       OPENVMS?                                         9-7J                 9.7.1     CD and DVD notation, terminology?            9-9  J                 __________________________________________________________<                 9.8   WHAT I/O TRANSFER SIZE LIMITS EXIST INJ                       OPENVMS?                                        9-11  J                 __________________________________________________________C                 9.9   CAN I USE ODBC TO CONNECT TO OPENVMS DATABASE J                       FILES?                                          9-11  J                 __________________________________________________________J                 9.10  IF MY DISKS ARE SHOWN AS VIOC COMPATIBLE, AM I USINGJ                       XFC?                                            9-12    J                                                                       xiii u  n                              Contentsp        J           ________________________________________________________________J           CHAPTER 10  OPENVMS PROGRAMMING INFORMATION                 10-1  J                 __________________________________________________________G                 10.1  MODULAR PROGRAMMING, FACILITY PREFIXES AND SYMBOL J                       NAMING?                                         10-1  J                 __________________________________________________________9                 10.2  CAN I HAVE A SOURCE CODE EXAMPLE OF-J                       CALLING...?                                     10-2  J                 __________________________________________________________A                 10.3  HOW DO I GET THE ARGUMENTS FROM THE COMMANDwJ                       LINE?                                           10-4  J                 __________________________________________________________A                 10.4  HOW DO I GET A FORMATTED ERROR MESSAGE IN AuJ                       VARIABLE?                                       10-4  J                 __________________________________________________________J                 10.5  HOW DO I LINK AGAINST SYS$SYSTEM:SYS.STB ON AN ALPHAJ                       SYSTEM?                                         10-5  J                 __________________________________________________________=                 10.6  HOW DO I DO A SET DEFAULT FROM INSIDE AsJ                       PROGRAM?                                        10-5  J                 __________________________________________________________F                 10.7  HOW DO I TURN MY FORTRAN COMMON INTO A SHAREABLEJ                       IMAGE ON ALPHA?                                 10-5  J                 __________________________________________________________D                 10.8  HOW DO I CONVERT BETWEEN IEEE AND VAX FLOATINGJ                       DATA?                                           10-6  J                 __________________________________________________________B                 10.9  HOW DO I GET THE ARGUMENT COUNT IN A FORTRANJ                       ROUTINE?                                        10-6  J                 __________________________________________________________C                 10.10 HOW DO I GET A UNIQUE SYSTEM ID FOR LICENSING J                       PURPOSES?                                       10-7  J                 __________________________________________________________F                 10.11 WHAT IS AN EXECUTABLE, SHAREABLE, SYSTEM OR UWSSJ                       IMAGE?                                          10-8                      xiv                                   Contents.        J                 __________________________________________________________J                 10.12 HOW DO I DO A FILE COPY FROM A PROGRAM?         10-9  J                 __________________________________________________________J                 10.13 WHAT IS A DESCRIPTOR?                           10-9  J                 __________________________________________________________J                 10.14 HOW MANY BYTES ARE IN A DISK BLOCK?            10-11  J                 __________________________________________________________J                 10.15 HOW MANY BYTES ARE IN A MEMORY PAGE?           10-13  J                 __________________________________________________________=                 10.16 HOW DO I CREATE A PROCESS UNDER ANOTHER J                       USERNAME?                                      10-13  J                 __________________________________________________________G                 10.17 WHY DO LIB$SPAWN, LIB$SET_SYMBOL FAIL IN DETACHED J                       PROCESSES?                                     10-14  J                 __________________________________________________________E                 10.18 WHERE CAN I OBTAIN BLISS, AND THE LIBRARIES AND J                       SUPPORTING FILES?                              10-15  J                 __________________________________________________________J                 10.19 HOW CAN I OPEN A FILE FOR SHARED ACCESS?       10-17  J                 __________________________________________________________A                 10.20 HOW CAN I HAVE COMMON SOURCES FOR MESSAGES,_J                       CONSTANTS?                                     10-17  J                 __________________________________________________________D                 10.21 HOW DO I ACTIVATE THE OPENVMS DEBUGGER FROM ANJ                       APPLICATION?                                   10-17  J                 __________________________________________________________J                 10.22 DEALING WITH ENDIAN-NESS?                      10-18  J                 __________________________________________________________J                 10.23 HOW TO RESOLVE LINK-I-DATMISCH ERRORS?         10-19  J                 __________________________________________________________>                 10.24 COMPAQ C AND OTHER OPENVMS C PROGRAMMINGJ                       CONSIDERATIONS?                                10-19J                 10.24.1   Other common C issues                      10-22J                 10.24.2   Other common C++ issues                    10-24  J                                                                         xv                                   Contents         J                 __________________________________________________________J                 10.25 STATUS OF PROGRAMMING TOOLS ON OPENVMS VAX?    10-26    J           ________________________________________________________________J           CHAPTER 11  DECWINDOWS                                      11-1  J                 __________________________________________________________G                 11.1  HOW DO I LET SOMEONE ELSE DISPLAY SOMETHING ON MY J                       WORKSTATION?                                    11-1  J                 __________________________________________________________:                 11.2  HOW DO I CREATE A DISPLAY ON ANOTHERJ                       WORKSTATION?                                    11-3  J                 __________________________________________________________J                 11.3  HOW CAN I GET THE INFORMATION FROM SHOW DISPLAY INTOJ                       A SYMBOL?                                       11-3  J                 __________________________________________________________J                 11.4  HOW DO I GET A LOG OF A DECTERM SESSION?        11-4  J                 __________________________________________________________G                 11.5  WHY DOES THE DELETE KEY DELETE FORWARD INSTEAD OF_J                       BACKWARD?                                       11-4  J                 __________________________________________________________J                 11.6  WHY IS DECWINDOWS MOTIF NOT STARTING?           11-5  J                 __________________________________________________________J                 11.7  HOW DO I SET THE TITLE ON A DECTERM WINDOW?     11-8  J                 __________________________________________________________H                 11.8  HOW DO I CUSTOMIZE DECWINDOWS, INCLUDING THE LOGINJ                       SCREEN?                                         11-8  J                 __________________________________________________________J                 11.9  WHY DOESN'T XTAPPADDINPUT()  WORK ON OPENVMS?  11-10  J                 __________________________________________________________H                 11.10 WHY DO THE KEYBOARD ARROW KEYS MOVE THE DECWINDOWSJ                       CURSOR?                                        11-11  J                 __________________________________________________________J                 11.11 WHY DOES HALF MY DECWINDOWS DISPLAY BLANK?     11-11  J                 __________________________________________________________H                 11.12 %DECW-W-NODEVICE, NO GRAPHICS DEVICE FOUND ON THISJ                       SYSTEM?                                        11-12                      xvi                                   Contents         J                 __________________________________________________________J                 11.13 HOW CAN I RESET THE WARNING BELL VOLUME?       11-14  J                 __________________________________________________________J                 11.14 HOW CAN I ALTER THE DECWINDOWS CDE BACKDROP?   11-15  J                 __________________________________________________________<                 11.15 HOW CAN I ENABLE THE DECWINDOWS TCP/IPJ                       TRANSPORT                                      11-15  J           ________________________________________________________________J           CHAPTER 12  MISCELLANEOUS INFORMATION                       12-1  J                 __________________________________________________________H                 12.1  WHERE CAN I FIND INFORMATION ON ESCAPE AND CONTROLJ                       SEQUENCES?                                      12-1  J                 __________________________________________________________F                 12.2  DOES DECPRINT (DCPS) WORK WITH THE LRA0 PARALLELJ                       PORT?                                           12-3  J                 __________________________________________________________A                 12.3  HOW DO I CHECK FOR FREE SPACE ON A (BACKUP)_J                       TAPE?                                           12-3  J                 __________________________________________________________J                 12.4  SO WHAT HAPPENED TO SYS$CMSUPER?                12-4  J                 __________________________________________________________J                 12.5  CORRECTLY USING LICENSE PAKS AND LMF?           12-5  J           ________________________________________________________________J           CHAPTER 13  FINDING AND USING SOFTWARE                      13-1  J                 __________________________________________________________F                 13.1  WHERE CAN I FIND FREEWARE/SHAREWARE/SOFTWARE FORJ                       OPENVMS?                                        13-1              J                                                                       xvii S                                 Contents?        J                 __________________________________________________________J                 13.2  WHERE CAN I FIND UNIX TOOLS FOR OPENVMS?       13-14;                 13.2.1    POSIX-compliant versions of POSIX J                           routines and utilities                     13-14J                 13.2.2    C system and library routines              13-14J                 13.2.3    X Windows utilities and routines           13-14J                 13.2.4    TCP/IP Tools and Utilities for OpenVMS?    13-15J                 13.2.5    The vi text editor                         13-15J                 13.2.6    Various GNU tools                          13-160                 13.2.6.1     GCC compiler, 13-16J                 13.2.7    Console Management Options                 13-17  J                 __________________________________________________________J                 13.3  WHERE CAN I GET THE MOZILLA WEB BROWSER?       13-17  J                 __________________________________________________________J                 13.4  WHERE CAN I GET JAVA FOR OPENVMS?              13-18  J                 __________________________________________________________J                 13.5  OBTAINING USER INPUT IN DCL CGI SCRIPT?        13-19  J                 __________________________________________________________A                 13.6  HOW CAN A BATCH JOB GET ITS OWN BATCH ENTRYbJ                       NUMBER?                                        13-19  J                 __________________________________________________________J                 13.7  HOW DO I CONVERT TO NEW CMS LIBRARIES?         13-20  J                 __________________________________________________________C                 13.8  WHERE CAN I GET NEW CERTIFICATES FOR NETSCAPEAJ                       NAVIGATOR?                                     13-21  J                 __________________________________________________________J                 13.9  WHY DOESN'T DCL SYMBOL SUBSTITUTION WORK?      13-22  J                 __________________________________________________________J                 13.10 WHERE CAN I GET PERL FOR OPENVMS?              13-23  J                 __________________________________________________________=                 13.11 OBTAINING THE DECMIGRATE (VEST AND TIE)_J                       TRANSLATOR?                                    13-24  J                 __________________________________________________________F                 13.12 WHERE CAN I GET ZIP, UNZIP, SELF-EXTRACTING ZIP,J                       ETC?                                           13-25                      xviii    _                              Contents_        J                 __________________________________________________________J                 13.13 ARE VAX HARDWARE EMULATORS AVAILABLE?          13-26    J           ________________________________________________________________J           CHAPTER 14  HARDWARE INFORMATION                            14-1  J                 __________________________________________________________H                 14.1  WHAT ARE THE OPENVMS DIFFERENCES AMONG VAX, ALPHA,J                       AND IA-64?                                      14-1  J                 __________________________________________________________I                 14.2  SEEKING PERFORMANCE INFORMATION FOR ALPHA (AND VAX) J                       SYSTEMS?                                        14-2  J                 __________________________________________________________J                 14.3  CONSOLE COMMANDS, SERIAL LINES, AND CONTROLS?   14-3B                 14.3.1    What commands are available in the AlphaJ                           SRM console?                                14-3J                 14.3.2    What does SRM mean? What is PALcode?        14-4@                 14.3.3    Alpha COM ports and VAX console serialJ                           line information?                           14-4J                 14.3.3.1     Which terminal device name is assigned to the-                              COM ports?, 14-4 D                 14.3.3.2     Which serial port is the console on the1                              MicroVAX 3100?, 14-4 G                 14.3.3.3     How can I set up an alternate console on a .                              VAXstation?, 14-5J                 14.3.3.4     Please explain the back panel of the MicroVAX%                              II, 14-5A<                 14.3.4    What are Alpha console environmentJ                           variables?                                  14-6J                 14.3.5    What are the boot control flag values?      14-7=                 14.3.5.1     What are the Alpha APB boot flag *                              values?, 14-7I                 14.3.5.2     What are the VAX VMB boot flag values?, 14-87?                 14.3.6    How do I boot an AlphaStation without_J                           monitor or keyboard?                       14-11;                 14.3.7    Downloading and using SRM console J                           Firmware?                                  14-11I                 14.3.7.1     Where can I get updated console firmware forI2                              Alpha systems?, 14-11I                 14.3.7.2     How do I reload SRM firmware on a half-flash 1                              Alpha system?, 14-121  J                                                                        xix                                   ContentsU        J                 14.3.7.3     How do I switch between AlphaBIOS/ARC and SRM-                              consoles?, 14-13O  J                 __________________________________________________________J                 14.4  WHAT PLATFORMS WILL OPENVMS OPERATE ON?        14-16J                 14.4.1    on the Alpha Multia?                       14-16J                 14.4.2    on AlphaPC 164LX? AlphaPC 164SX?           14-18B                 14.4.2.1     on the NoName AXPpci33 system?, 14-18J                 14.4.3    on the Alpha XL series?                    14-19@                 14.4.4    OpenVMS on the Personal Workstation -aJ                           and -au series?                            14-19H                 14.4.4.1     OpenVMS on the Whitebox Windows-Only series*                              Alpha?, 14-20G                 14.4.4.2     OpenVMS and Personal Workstation ATA (IDE)E.                              bootstrap?, 14-21J                 14.4.5    On the Intel Itanium IA-64 platform?       14-21:                 14.4.5.1     Where can I get Intel Itanium0                              information?, 14-22  J                 __________________________________________________________F                 14.5  WHAT IS THE LEAST EXPENSIVE SYSTEM THAT WILL RUNJ                       OPENVMS?                                       14-22  J                 __________________________________________________________?                 14.6  WHERE CAN I GET MORE INFORMATION ON ALPHA J                       SYSTEMS?                                       14-23  J                 __________________________________________________________J                 14.7  DESCRIBE ALPHA INSTRUCTION EMULATION AND INSTRUCTIONJ                       SUBSETS?                                       14-24  J                 __________________________________________________________D                 14.8  WHAT IS THE ACCURACY OF THE ALPHA TIME OF YEARJ                       (BB_WATCH) CLOCK?                              14-26  J                 __________________________________________________________J                 14.9  SO HOW DO I OPEN UP THE DEC 3000 CHASSIS?      14-26  J                 __________________________________________________________J                 14.10 WHAT IS BYTE SWIZZLING?                        14-26  J                 __________________________________________________________B                 14.11 WHAT IS THE LAYOUT OF THE VAX FLOATING POINTJ                       FORMAT?                                        14-28                      xx_ _  _                              Contents         J                 __________________________________________________________J                 14.12 WHERE CAN I FIND MORE INFO ABOUT VAX SYSTEMS?  14-29  J                 __________________________________________________________D                 14.13 WHERE CAN I FIND INFORMATION ON NETBSD FOR VAXJ                       SYSTEMS?                                       14-29  J                 __________________________________________________________E                 14.14 WHAT SYSTEM DISK SIZE LIMIT ON THE MICROVAX ANDhJ                       VAXSTATION 3100?                               14-29  J                 __________________________________________________________H                 14.15 WHAT IS THE ACCURACY OF VAX THE TIME OF YEAR (TOY)J                       CLOCK?                                         14-30  J                 __________________________________________________________J                 14.16 WHAT ARE THE VAX PROCESSOR (CPU) CODES?        14-31  J                 __________________________________________________________C                 14.17 WHERE CAN I GET SOFTWARE AND HARDWARE SUPPORTOJ                       INFORMATION?                                   14-32  J                 __________________________________________________________G                 14.18 WHERE CAN I GET HARDWARE SELF-MAINTENANCE SUPPORTSJ                       ASSISTANCE?                                    14-33  J                 __________________________________________________________D                 14.19 WHY DOES MY SYSTEM HALT WHEN I POWER-CYCLE THEJ                       CONSOLE TERMINAL?                              14-33  J                 __________________________________________________________I                 14.20 CAN I REUSE OLD KEYBOARDS, MICE AND MONITORS WITH AOJ                       PC?                                            14-34  J                 __________________________________________________________C                 14.21 WHICH VIDEO MONITOR WORKS WITH WHICH GRAPHICS J                       CONTROLLER?                                    14-36  J                 __________________________________________________________<                 14.22 WHERE CAN I GET INFORMATION ON STORAGEJ                       HARDWARE?                                      14-37  J                 __________________________________________________________=                 14.23 WHY DOES MY LK401 KEYBOARD UNEXPECTEDLY J                       AUTOREPEAT?                                    14-37  J                                                                        xxi    U                              Contents         J                 __________________________________________________________I                 14.24 PROBLEM - MY LK411 SENDS THE WRONG KEYCODES OR SOME J                       KEYS ARE DEAD                                  14-38  J                 __________________________________________________________B                 14.25 WHICH DE500 VARIANT WORKS WITH WHICH OPENVMSJ                       VERSION?                                       14-38  J                 __________________________________________________________G                 14.26 THIRD-PARTY DISK/TAPE/CONTROLLERS/SCSI/WIDGETS ON J                       OPENVMS?                                       14-409                 14.26.1   Lists of third-party widgets onSJ                           OpenVMS?                                   14-42A                 14.26.2   Are the 2X-KZPCA-AA and SN-KZPCA-AA LVD_J                           Ultra2 SCSI?                               14-43J                 14.26.3   Resolving DRVERR fatal device error?       14-43  J                 __________________________________________________________@                 14.27 HOW DO I CONVERT? DISK BLOCKS? KB, MB, GB,J                       TB?                                            14-43  J                 __________________________________________________________J                 14.28 LOOKING FOR CONNECTOR WIRING PINOUTS?          14-45  J                 __________________________________________________________=                 14.29 WHAT CONNECTORS AND WIRING ADAPTERS ARE J                       AVAILABLE?                                     14-47  J                 __________________________________________________________J                 14.30 WHAT IS FLOW CONTROL AND HOW DOES IT WORK?     14-48  J           ________________________________________________________________J           CHAPTER 15  INFORMATION ON NETWORKS AND CLUSTERS            15-1  J                 __________________________________________________________J                 15.1  HOW TO CONNECT OPENVMS TO A MODEM?              15-1  J                 __________________________________________________________J                 15.2  OPENVMS AND IP NETWORKING?                      15-1J                 15.2.1    How to connect OpenVMS to the Internet?     15-1J                 15.2.2    Connecting to an IP Printer?                15-1C                 15.2.3    How do I connect a PostScript printer via J                           TCP/IP?                                     15-2<                 15.2.4    How do I set a default IP route orJ                           gateway on OpenVMS?                         15-3                      xxii                                    Contents_        ?                 15.2.5    How can I set up reverse telnet (like7J                           reverse LAT)?                               15-4C                 15.2.6    Why can't I use PPP and RAS to connect to_J                           OpenVMS Alpha?                              15-4  J                 __________________________________________________________J                 15.3  OPENVMS AND DECNET NETWORKING?                  15-4J                 15.3.1    Can DECnet-Plus operate over IP?            15-5>                 15.3.2    What does "failure on back translateJ                           address request" mean?                      15-5J                 15.3.3    Performing SET HOST/MOP in DECnet-Plus?     15-6  J                 __________________________________________________________;                 15.4  HOW TO DETERMINE THE NETWORK HARDWARE J                       ADDRESS?                                        15-6B                 15.4.1    How do I reset the LAN (DECnet-Plus NCL)J                           error counters?                             15-9A                 15.4.2    How do I install DECnet Phase IV on VMSyJ                           7.1?                                        15-9  J                 __________________________________________________________B                 15.5  HOW CAN I SEND (RADIO) PAGES FROM MY OPENVMSJ                       SYSTEM?                                        15-10  J                 __________________________________________________________J                 15.6  OPENVMS, CLUSTERS, VOLUME SHADOWING?           15-11A                 15.6.1    OpenVMS Cluster Communications Protocol J                           Details?                                   15-11D                 15.6.1.1     OpenVMS Cluster (SCS) over DECnet? Over'                              IP?, 15-11vB                 15.6.1.2     Configuring Cluster SCS for path load.                              balancing?, 15-129                 15.6.1.2.1    Cluster Terminology?, 15-12 D                 15.6.1.2.2    Cluster Communications Control?, 15-14F                 15.6.1.2.3    Cluster Communications Control Tools and/                               Utilities?, 15-15 J                 15.6.2    Cluster System Parameter Settings?         15-15I                 15.6.2.1     What is the correct value for EXPECTED_VOTESO4                              in a VMScluster?, 15-16D                 15.6.2.2     Explain disk (or tape) allocation class-                              settings?, 15-18_E                 15.6.2.2.1    How to configure allocation classes and 5                               Multi-Path SCSI?, 15-18_<                 15.6.3    Tell me about SET HOST/DUP and SETJ                           HOST/HSC                                   15-20  J                                                                      xxiii                                   Contents?        J                 15.6.4    How do I rename a DSSI disk (or tape?)     15-21?                 15.6.5    Where can I get Fibre Channel StoragePJ                           (SAN) information?                         15-22J                 15.6.6    How can I split up an OpenVMS Cluster?     15-22J                 15.6.7    Details on Volume Shadowing?               15-24E                 15.6.7.1     Does volume shadowing require a non-zero 7                              allocation classes?, 15-24_9                 15.6.7.2     Volume Shadowing MiniCopy vs .                              MiniMerge?, 15-25.                 15.6.7.2.1    MiniCopy?, 15-26/                 15.6.7.2.2    MiniMerge?, 15-26.    J           ________________________________________________________________           INDEX_  J           ________________________________________________________________           TABLES  J                 1-1   Core Websites                                    1-1  J                 2-1   OpenVMS Media Kits                               2-5  J                 2-2   OpenVMS ECO Kits                                 2-5  J                 2-3   OpenVMS Source Listings CD-ROM Kits              2-6  J                 2-4   OpenVMS Alpha Version Rule-Of-Thumb             2-11  J                 3-1   OpenVMS Websites                                 3-2  J                 3-2   Telephone Numbers                                3-5  J                 3-3   OpenVMS Tutorial Websites                        3-7  J                 3-4   DP Books                                         3-9  J                 3-5   OpenVMS Mailing Lists                           3-10  J                 11-1  X Windows Display Commands                      11-1                            xxiv_ _  _                  J           ________________________________________________________________             Preface_                                                                                    J                                                                          i _  _                  J           ________________________________________________________________             OpenVMS FAQ     G                    This is the OpenVMS Frequently Asked Questions (FAQ) F                    posting for the comp.os.vms and comp.sys.dec usenet                    newsgroups.  J                    The OpenVMS FAQ is archived in (at least) the following                    locations:_  4                    o  http://www.openvms.compaq.com/  @                    o  ftp://rtfm.mit.edu/pub/usenet/comp.os.vms/  >                    o  comp.answers and news.answers newsgroups  *                    o  http://www.faqs.org/  ,                    o  http://www.google.com/  0                    o  http://www.kjsl.com/vmsfaq  9                    o  http://eisner.decus.org/vms/faq.htmS  G                    Other internet FAQs are generally available in these                     locations:   >                    o  comp.answers and news.answers newsgroups  7                    o  ftp://rtfm.mit.edu/pub/usenet/...   *                    o  http://www.faqs.org/  ,                    o  http://www.google.com/  ?                                Suggestions and Updates Welcome!   @                       Please send suggestions for changes or for=                       additions to the FAQ to the FAQ Editor.S  =                                 Please! No Support Questions!   C                       Please do not send technical questions to the E                       FAQ Editor. The FAQ editor is not in a position A                       to answer general questions, nor to provide_D                       support. Rather, please post your questions toB                       the appropriate newsgroup, or please contactE                       your support organization. Please also consider_  J                                                                        iii L  R                              OpenVMS FAQ        ?                       reading Section 1.3 before posting to the_!                       newsgroups._  ;                       Your understanding in this is greatlyP"                       appreciated.  D           __________________________________________________________           Contributors  E                    Many people have contributed to this FAQ document, F                    directly and indirectly. In many cases, part or allI                    of an answer included in the FAQ has been adapted from_E                    one or more postings from the comp.os.vms or otherIE                    newsgroup-though individual citations and specificEE                    quotations are generally not included in this FAQ._H                    (The FAQ editor wishes to thank to all of those folksD                    who post answers to the newsgroups, and that have<                    contributed to the contents of this FAQ.)  H                    The following is an incomplete list of the folks thatJ                    have contributed directly or indirectly to the contentsJ                    of the OpenVMS FAQ. Additions, corrections, and updatesF                    to this list of contributors and to the contents ofD                    the FAQ itself are welcome, and all omissions andH                    misspellings are unintentional. Thanks to each of theG                    contributors here, and to all of the folks that have A                    participated in the FAQ and in the newsgroups._  H                    Paul Anderson, Jason Armistead, Zoltan Arpadffy, JohnH                    AtoZ, Bailey, Jeremy Begg, Colin Blake, Ken Blaylock,F                    Bol, Craig Berry, Mark Berryman, Jim Becker, VerellE                    Boaen, Bol, Richard Brodie, Robert Alan Byer, Jeff F                    Campbell, Antonio Carlini, Ken Chaney, Cristy, JohnC                    Croll, David J. Dachtera, Robert Deininger, Dale C                    Dellutri, Leo Demers, Sue Denham, Thomas Dickey,_F                    Eric Dittman, Jim Dunham, Eric, Glenn Everhart, KenE                    Fairfield, Yaacov Fenster, Gunther Froehlin, Harry F                    Garonzik, Derek Garson, John Gillings, Clair Grant,G                    Hunter Goatley, Ruth Goldenberg, Vance Haemmerle, KiEF                    Suk Hahn, SHarris, Fletcher Hearns, Phillip Helbig,H                    Hein van den Heuvel, Stephen Hoffman, Sue Holt, Horn,J                    Jaf, Leif Jansson, Kevin Jenkins, Henry Juengst, inazu_F                    k, Geoff Kingsmill, Fred Kleinsorge, Felix Kreisel,I                    Veli Korkko, Ruslan R. Laishev, Norm Lastovica, p_lee,_G                    Jerry Leichter, Richard Levitte, Steve Lionel, KerryS                      iv                                    OpenVMS FAQ        E                    Main, John E. Malmberg, David Mathog, Dale Miller,_E                    Dick Munroe, Patrick Moreau, Morrison, otis, KeithBF                    Parris, Plass, pvhp, David Rabahy, Stan Rabinowitz,D                    Mike Raspuzzi, Steve Reece, Aaron Sakovich, BrianG                    Schenkenberger, Atlant Schmidt, Wayne Sewell, Steven H                    Shamlian, Sue Skonetski, Scott Snadow, Scott Squires,I                    stfp, Dave Sweeney, Mike Thompson, Arne Vajhj, Martin_H                    Vorlnder, Peter Weaver, William Webb, Williams, Paul(                    Winalski, Uwe Zinser.  A                    Again, any omission from this list is entirely E                    unintentional, please notify the FAQ editor of any C                    omissions, corrections, or updates needed within E                    this list. And thanks to each of these individuals H                    for their assistance and for their contributions, andD                    particularly for sharing their OpenVMS expertise.  D           __________________________________________________________           The Fine Print  E                    All trademarks, all registered trademarks, and allOJ                    servicemarks used or referenced here are the properties;                    of their respective owner(s) or holders.   J                    The redistribution, reposting and/or the web-serving ofH                    complete and unaltered copies of this FAQ document isD                    permitted. Other uses only with prior permission.  C                    While the information contained here is believed G                    correct, the use of any and all information acquired D                    from this document is entirely at the risk of the                    user(s)._  B                    Though the editor of this FAQ is an employee ofA                    Hewlett-Packard Company (HP), this posting and D                    the information contained within are not official$                    statements of HP.              J                                                                          v _  _                    J                    _______________________________________________________             1        Introduction_      D           __________________________________________________________:           1.1  What core OpenVMS URLs do you need to know?  D                    If you have no other OpenVMS URLs bookmarked, youC                    will want to be familiar with the URLs listed in1                    Table 1-1:B  J           ________________________________________________________________"           Table 1-1  Core Websites  J                    _______________________________________________________J                    URL_______Contents_____________________________________  5                              Core OpenVMS Information   6                    http://www.hp.com/products/openvms/  G                              OpenVMS Future Release Contents, SchedulesC  I                    http://www.openvms.compaq.com/openvms/roadmap/openvms__                    roadmaps.htm   =                              OpenVMS and Core Layered Product *                              Documentation  5                    http://www.openvms.compaq.com/doc/_6                    http://www.openvms.compaq.com:8000/<                    http://www.openvms.compaq.com/commercial/  I                              Core OpenVMS Support Search Engine URLs, FTP '                              Patch Area_  *                    http://askq.compaq.com/H                    http://ftp.support.compaq.com.au/pub/ecoinfo/ecoinfo/B                    ftp://ftp.support.compaq.com/public/vms/vax/...B                    ftp://ftp.support.compaq.com/public/vms/axp/...  1                              The OpenVMS Freeware_  J                                                                        1-1 I                                 Introduction       J           ________________________________________________________________*           Table 1-1 (Cont.)  Core Websites  J                    _______________________________________________________J                    URL_______Contents_____________________________________  :                    http://www.openvms.compaq.com/freeware/  1                              The OpenVMS Hobbyist   J           _________http://www.openvmshobbyist.org/________________________  D           __________________________________________________________6           1.2  What are the OpenVMS Usenet Newsgroups?  H                    There are a huge number of newsgroups available, someE                    of which discuss topics of interest to folks usingSD                    OpenVMS operating system. Key among these are theF                    comp.os.vms newsgroup and the vmsnet.* heirarchy of                    newsgroups.  '           _____________________________T@           1.2.1  What is the scope of the comp.os.vms newsgroup?  E                    The comp.os.vms newsgroup is the primary newsgroup_H                    for discussion of the HP OpenVMS operating system andI                    the computer systems on which it runs. Questions about J                    layered products which run on OpenVMS are also welcome,I                    though many of them (in particular, language compilersTJ                    and database systems) have more specific newsgroups. IfJ                    a question has some relationship to OpenVMS, it belongs"                    in comp.os.vms.  '           _____________________________ ?           1.2.2  What newsgroups carry VMS-related information?_  F                    The vmsnet.* hierarchy is operated by the EncompassF                    users group (formerly known as DECUS), and containsH                    various newsgroups of interest, including vmsnet.misc$                    and vmsnet.alpha.  I                    Sprechen Sie Deutsch? Besuchen Sie bitte den newsgroup_"                    de.comp.os.vms.                        1-2 I  W                              Introduction         I                    The comp.sys.dec newsgroup carries general discussions_F                    about various HP computer systems, and specificallyB                    systems that were acquired by HP as part of theF                    acquisition of Compaq, systems which had previouslyH                    been acquired by Compaq as part of the acquisition of;                    Digital Equipment Corporation (DIGITAL).1  J                    Also of interest are resources and conferencing systemsI                    including Encompasserve (formerly known as DECUServe),1J                    Ken Farmer's OpenVMS.Org forums, and the Compaq Working                    Group folks:C  0                    o  telnet://eisner.decus.org/  -                    o  http://www.openvms.org/   8                    o  http://www.compaqworkinggroup.org/  '           _____________________________ 7           1.2.3  What newsgroup archives are available?_  >                    Extensive archives of INFO-VAX mailings andB                    comp.os.vms postings are archived and available@                    at ftp://crvax.sri.com/info-vax/. Google also@                    has extensive newsgroup archives available at*                    http://www.google.com/.  '           _____________________________A3           1.2.4  What is the INFO-VAX mailing list?   F                    INFO-VAX is a mailing list which is bidirectionallyE                    gatewayed to the comp.os.vms newsgroup. This meansHI                    that postings to comp.os.vms get automatically sent to I                    INFO-VAX subscribers and messages sent to the INFO-VAX I                    list are automatically posted to comp.os.vms. INFO-VAX F                    can be a useful way to participate in the newsgroupE                    if you can't access the newsgroup directly through G                    a newsreader. Note that INFO-VAX is a closed mailing J                    list, which means that only subscribers may post to it.G                    Please see Section 1.2.4.1 for information on how to I                    subscribe, and how you can subscribe such that you can I                    post from multiple addresses but still receive no more 1                    than one copy of the mailings._  J                                                                        1-3                                   Introduction_        E                    Please remember that propogation delays can and do J                    vary, meaning that mailings and postings may be delayedC                    or even lost. It is quite possible that postings G                    may not be delivered for several days, and that some_B                    postings will appear out of the expected order.  D                    For details on the available archives, please see!                    Section 1.2.3.   '           _____________________________ F           1.2.4.1  How do I subscribe to or unsubscribe from INFO-VAX?  E                    The address for subscription requests is Info-VAX-_E                    Request[at]Mvb.Saic.Com. Subscription requests are3D                    handled automatically by a mail server. This mailE                    server ignores the subject line and processes each 4                    line of the message as a command.  H                    The syntax for subscribing and unsubscribing, as wellJ                    as setting various parameters on your subscription, is:  C                    SUBSCRIBE INFO-VAX      (ADD is a valid synonym)-Z                    UNSUBSCRIBE INFO-VAX (REMOVE, SIGNOFF, and SIGN-OFF are valid synonyms)H                    SET INFO-VAX DIGEST     (to receive in Digest format)Q                    SET INFO-VAX NODIGEST   (to receive each message individually)tV                    SET INFO-VAX NOMAIL     (to establish an email address for posting,I                                              though not receiving, mail.) Z                    SET INFO-VAX MAIL       (to establish an email address for both postingA                                              and receiving mail.)   A                    The mail server is not case-sensitive; case is_F                    irrelevant. Attempts to fetch copies of the mailingD                    list are rejected for reasons of confidentiality.G                    Any message not understood by the mailserver will be 1                    returned entirely unprocessed.   J                    The INFO-VAX moderator can be contacted directly at the?                    email address Mark.Berryman[at]Mvb.Saic.Com.   G                    If you are on Bitnet, send a mail message containing H                    the text SUBSCRIBE INFO-VAX to LISTSERVE[at][nearest-C                    Listserv-system). To unsubscribe, send a message C                    containing the text SIGNOFF INFO-VAX to the same #                    Listserv system._                      1-4 _  _                              IntroductionY        G                    If you are on the Internet in the UK, send a message_H                    containing the word SUBSCRIBE or UNSUBSCRIBE to info-4                    vax-request[at]ncdlab.ulcc.ac.uk.  D           __________________________________________________________$           1.3  What is [n]etiquette?  D                    Before posting or emailing a question, please useE                    the available local resources, such as the OpenVMS_G                    manuals, the HELP, and the resources and informationEI                    in and referenced by this FAQ. Please use these first. F                    Also please specifically read the release notes andH                    (if appropriate) the cover letter for the product youH                    are using. (The release notes are generally placed inI                    SYS$HELP:.) Quite often, these simple steps will allow_J                    you to quickly find the answer to your own question-andG                    more quickly than waiting for a response to question_D                    posted to a newsgroup, too. These steps will saveF                    you time, and will also help ensure you have a goodF                    reputation with the folks that might be included toF                    answer one of your future questions, a question notI                    covered in these resources. Put another way, if you do G                    not want your questions to be ignored in the future- G                    and please remember that the folks in the newsgroups F                    do not have to answer your questions-you won't wantG                    to "annoy the natives" by asking a question that has E                    already been answered far more times more than you E                    might have realized, or a question whose answer is A                    readily available had you made a small effort.   >                    When posting, please consider the following                    suggestions:   F                    o  There is no particularly reliable way to recall,H                       erase, delete, or otherwise hide a message once itF                       is emailed or once posted. Once your message hasG                       reached an external email server or multiple news I                       servers, the entire text is effectively a permanentPE                       fixture of the network. And using the available J                       search engines, a fixture that is easy to locate and#                       to correlate.   I                       For details on some of the many available archives,b/                       please see Section 1.2.3.   J                                                                        1-5 l  ?                              Introductionr        H                    o  Include a valid e-mail address in the text of yourF                       posting or in a "signature" appended to the end.F                       Reply-to addresses in headers often get garbled.H                       Anonymous addresses can also simply be ignored, asI                       fake addresses are regularly used by folks that arenH                       "trolling" and by folks that are spamming. (ThoughE                       to avoid spam-harvesting of your email address, D                       consider adding characters or a field into theJ                       address-but remember to include details around whichJ                       characters or fields should be removed or altered ifA                       you decide to be particularly clever here.)   D                    o  If you are submitting a question, please be asG                       specific as you can. Include relevant informationNG                       such as processor type, product versions (OpenVMSiI                       and layered products that apply), error message(s), D                       DCL command(s) used, and a short, reproducibleC                       example of problems. Say what you've tried soXH                       far, so that effort isn't duplicated. Keep in mindG                       that there's not yet a telepathy protocol for the H                       Internet. (The more detailed your description, theJ                       better that people can help you with your question.)  G                    o  If responding to a posting, include in your reply J                       only as much of the original posting as is necessaryI                       to establish context. As a guideline, consider thateE                       if you've included more text than you've added,1F                       you've possibly included too much. Never include?                       signatures and other irrelevant material.T  D                    o  Please be polite. If the question isn't wordedE                       the way you think is correct or doesn't include_C                       the information you want, try to imagine whatEF                       the problem might be if viewed from the poster'sC                       perspective. Requests for additional detailed_D                       information are often better sent through mail:                       rather than posted to the newsgroup.  A                    o  If you have a problem with HP (or any other C                       vendor's) product, please use the appropriate C                       support channel. Do not assume that newsgroup I                       postings will get read, will be responded to by the J                       appropriate developers, or will be later followed up                       upon.                       1-6 S                                 Introduction_        H                    o  If you are posting from a web browser, news readerG                       or if you are posting via email sent to INFO-VAX,_I                       please turn off MIME, vcard, attachments, and other D                       mechanisms that assume anyone reading the postH                       has the corresponding capability-use the text-onlyI                       option of your web browser, news reader, or mailer._E                       Usenet is traditionally a text-only medium, andHG                       many comp.os.vms participants will use tools that_J                       have this support disabled, or that do not have thisI                       support. If the message uses MIME or attachments orTH                       such, the text of your message will be buried in aG                       large pile of gibberish, and some tools will send1J                       multiple copies of the text within a single posting.  H                    o  If you find that the postings of a particular userE                       are uninteresting, annoying, or off-topic, most4I                       newsreaders include a filter or killfile mechanism, B                       and many mail clients have similar filteringH                       capabilities. Please do not "flame"-to email or toI                       post vitriol - any individual that might annoy you, J                       please enable and filter all of that users postings.H                       Posting of vitriol and flames will eventually comeG                       back to haunt you. Similarly, readers that decide G                       that your postings are not worthy of reading will I                       similarly tend to filter or to killfile all of your A                       postings. Please play nice, in other words.3  B                    Before posting your question to the comp.os.vmsJ                    newsgroup or sending your message to the INFO-VAX list,J                    also please take the time to review available etiquetteF                    information, such as that included in the following                    documents:   T                    o  ftp://rtfm.mit.edu/pub/usenet/news.answers/usenet/primer/part1  Q                    o  ftp://rtfm.mit.edu/pub/usenet/news.answers/usenet/faq/part1_  N                    o  ftp://rtfm.mit.edu/pub/usenet/news.answers/usenet/emily-$                       postnews/part1  P                    o  ftp://rtfm.mit.edu/pub/usenet/news.answers/usenet/writing-!                       style/part1_  P                    o  ftp://rtfm.mit.edu/pub/usenet/news.answers/usenet/posting-!                       rules/part1   J                                                                        1-7 _  _                              Introduction         B                    This information will document the etiquette ofJ                    newsgroups, as well as providing you with the knowledgeH                    the vast amount of newsgroup-related information thatG                    is readily available to you, and where to find it..._  1                                              Note2  A                       Please do not post security holes or system                        crashers  F                       Rather, please report these problems directly toE                       HP. Why? So that HP has a chance to resolve andIF                       distribute a fix before other customer sites can"                       be affected.  A                       Most folks in the newsgroups are honest and_>                       deserve to know about potential securityA                       problems, but a few folks can and will make C                       nefarious use of this same information. Othery?                       sites will hopefully return the courtesy, =                       and will not post information that willP?                       potentially compromise your site and your?+                       computer environment.   D           __________________________________________________________8           1.4  What OpenVMS user group(s) are available?  C                    Encompass, the Enterprise Computing Association,,F                    is a user group comprised of information technologyG                    professionals that are interested in the Enterprise-_C                    oriented products, services, and technologies ofPE                    Compaq and of the former DIGITAL. Encompass offers_I                    newsletters, the Encompass website, and offers variousIF                    gatherings and related services, including symposia9                    events and local users group meetings._  I                    Encompass is a descendent of the organization known asNG                    DECUS, the Digital Equipment Computer Users Society._  F                    For more information on Encompass, please visit the&                    Encompass web site:  1                    o  http://www.encompassus.org/_                      1-8                                   Introduction         F                    The organization comprised of customers of Hewlett-J                    Packard Company (HP) that is probably most analogous to9                    the Encompass organization is Interex:n  -                    o  http://www.interex.org/   B                    Like Encompass, Interex offers various servicesF                    and events of interest to folks that presently workG                    with and/or that wish to learn about HP products and I                    offerings. Please see the Interex website for details.   D           __________________________________________________________7           1.5  OpenVMS Support, Questions and Comments?t  F                    The following section includes contacts for OpenVMSG                    Feedback, and information on how to obtain technical '                    support information.   '           _____________________________ @           1.5.1  Corporate contacts for OpenVMS Business Issues?  H                    The following folks are the HP corporate contacts forF                    OpenVMS business issues, listed in descending orderI                    from Carleton (Carly) Fiorina to the Vice President of 8                    the OpenVMS Engineering organization:  #                    o  Carly Fiorinad  %                    o  Peter Blackmore   $                    o  Scott Stallard  &                    o  Richard Marcello  !                    o  Mark Gorham_  C                    These folks will quite obviously respond best toTC                    cogently-worded OpenVMS corporate-level business C                    issues. These folks are NOT appropriate contactsIG                    for any OpenVMS technical support issues nor for anysH                    OpenVMS technical support requests, nor for any otherF                    non-corporate-related, non-business-related issues.    J                                                                        1-9 _  _                              Introduction5      '           _____________________________ %           1.5.2  OpenVMS Ambassadors?   G                    The OpenVMS Ambassadors are senior HP engineers with_H                    advanced technical knowledge and advanced training inI                    OpenVMS, with detailed knowledge of current and futurelH                    OpenVMS releases and product plans, and with contactsE                    directly with the HP and ISV hardware and softwareCC                    engineering organizations developing OpenVMS and1J                    OpenVMS hardware platforms, as well as layered productsG                    and tools. Further, Ambassadors are experienced with B                    integrating HP OpenVMS and application-specificB                    products and ISV applications to solve specific)                    business requirements.   F                    OpenVMS Ambassadors are based throughout the world.  F                    Your HP sales representative or HP reseller will beG                    able connect you with your local OpenVMS Ambassador.   '           _____________________________5D           1.5.3  Contact for OpenVMS Marketing Issues and Questions?  *                    Please see Section 3.5.  '           _____________________________l;           1.5.4  Contact URLs for OpenVMS Technical Issues?5  E                    For technical issues and technical support, please F                    contact your software support organization, or yourF                    local HP Customer Support Center or HP Reseller. In?                    North America, you can call 1-800-OK-COMPAQ.   J                    Please remember to review and to bookmark the following                     support URLs:  <                    o  http://www.openvms.compaq.com/support/  -                    o  http://askq.compaq.com/   ;                    o  http://www.openvms.compaq.com/wizard/   E                    o  ftp://ftp.support.compaq.com/public/vms/vax/...   E                    o  ftp://ftp.support.compaq.com/public/vms/axp/...                       1-10a c  o                    J                    _______________________________________________________  &           2        General Information      D           __________________________________________________________4           2.1  What is OpenVMS? What is its history?  J                    OpenVMS, originally called VMS (Virtual Memory System),H                    was first conceived in 1976 as a new operating systemC                    for the then-new, 32-bit, virtual memory line of C                    computers, eventually named VAX (Virtual Address                     eXtension).  J                    The first VAX model, the 11/780, was code-named "Star",D                    hence the code name for the VMS operating system,F                    "Starlet", a name that remains to this day the nameD                    for the system library files (STARLET.OLB, etc.).  H                    VMS version X0.5 was the first released to customers,J                    in support of the hardware beta test of the VAX-11/780,G                    in 1977. VAX/VMS Version V1.0 shipped in 1978, along 7                    with the first revenue-ship 11/780s.t  >                    OpenVMS was designed entirely within HP andC                    specifically within the former Digital Equipment H                    Corporation (DIGITAL). Two of the principal designersI                    were Dave Cutler and Dick Hustvedt, though with a wide G                    variety of other contributors. OpenVMS was conceived D                    as a 32-bit, virtual memory successor to the RSX-C                    11M operating system for the PDP-11. Many of the_D                    original designers and programmers of OpenVMS hadG                    worked previously on RSX-11M, and many concepts from 8                    RSX-11M were carried over to OpenVMS.  I                    OpenVMS VAX is a 32-bit, multitasking, multiprocessing ;                    virtual memory operating system. CurrenttG                    implementations run on VAX systems from HP and other                     vendors.e  J                    OpenVMS Alpha is a 64-bit multitasking, multiprocessing;                    virtual memory operating system. Current J                    implementations run on Alpha systems from HP, and other                    vendors.   J                                                                        2-1 r  t          &                    General Information        E                    Work to port OpenVMS to systems based on the IntelrE                    IA-64 architecture and specifically to the Itanium :                    Processor Family is presently underway.  G                    For more details on OpenVMS and its features, pleasetD                    read the OpenVMS Software Product Description at:  5                    o  http://www.compaq.com/info/spd/ D                       OpenVMS typically uses SPD 25.01.xx and/or SPD                       41.87.xx.   D                    Additional information on the general features ofJ                    various OpenVMS releases, release dates, as well as theJ                    development project code names of specific releases, is                     available at:  G                    o  http://www.openvms.compaq.com/openvms/os/openvms-e*                       release-history.html  H                    Additional historical information-as well as picturesH                    and a variety of other trivia-is available in the VAX)                    20th anniversary book:   L                    o  http://www.openvms.compaq.com/openvms/20th/vmsbook.pdf  J                    For information on the FreeVMS project, and on hobbyistC                    and educational versions of OpenVMS, please see:_  .                    o  http://www.free-vms.org/  5                    o  http://www.openvmshobbyist.org/   0                    o  http://www.openvmsedu.com/  H                    Also please see the related software licensing topicsB                    Section 2.7.3, Section 2.7.1, and Section 2.14.  D           __________________________________________________________>           2.2  What is the difference between VMS and OpenVMS?  G                    VMS and OpenVMS are two names for the same operating F                    system. Originally, the operating system was calledF                    VAX-11/VMS; it changed to VAX/VMS at around VAX/VMSH                    V2.0. When the VMS operating system was ported to theG                    Alpha platform, it was renamed OpenVMS, for both VAXiG                    and Alpha (and for the Itanium Processor Family), inAJ                    part to signify the high degree of support for industry                      2-2 t  N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faq N  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.com    ------------------------------  # Date: Thu, 03 Jul 2003 17:11:00 GMT 2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman); Subject: OpenVMS Frequently Asked Questions (FAQ), Part 2/9e2 Message-ID: <EsZMa.3892$bl3.1441@news.cpqcorp.net>    i          &                    General Information        H                    standards such as POSIX, which provides many features#                    of UNIX systems.   D                    For those versions with POSIX, an OpenVMS licenseE                    allows you to install and run POSIX for OpenVMS at F                    no additional charge; all you need is the media andG                    documentation which can be found on the Consolidated J                    Distribution and On-Line Documentation CD-ROMs. SupportH                    for the POSIX package on more recent OpenVMS releasesI                    is not available, various parts of POSIX such as calls G                    from the API are being integrated more directly into E                    OpenVMS. For more information on POSIX for VMS see !                    question SOFT2a  E                    What became confusing is that the OpenVMS name wasdD                    introduced first for OpenVMS AXP V1.0 causing theF                    widespread misimpression that OpenVMS was for AlphaF                    AXP only, while "regular VMS" was for VAX. In fact,D                    the official name of the VAX operating system wasJ                    changed as of V5.5, though the name did not start to be;                    actually used in the product until V6.0.S  D                    The proper names for OpenVMS on the two platformsH                    are now "OpenVMS VAX" and "OpenVMS Alpha", the latter3                    having superseded "OpenVMS AXP".i  '           _____________________________v3           2.2.1  How do I port from VMS to OpenVMS?W  @                    You already did. Wasn't that easy? Please see+                    Section 2.2 for details.i  D           __________________________________________________________0           2.3  Which is better, OpenVMS or UNIX?  H                    This question comes up periodically, usually asked byI                    new subscribers amd new posters who are long-time UNIX E                    or Linux users. Sometimes, the question is ignored E                    totally; other times, it leads to a long series of G                    repetitive messages that convince no one and usuallymJ                    carry little if any new information. Please do everyoneJ                    a favor and avoid re-starting this perpetual, fruitless                    debate.  J                                                                        2-3 n  n          &                    General Information        G                    That said, OpenVMS and the better implementations ofWE                    UNIX are all fine operating systems, each with itsrJ                    strengths and weaknesses. If you're in a position whereI                    you need to choose, select the one that best fits your I                    own requirements, considering, for example, whether or G                    not the layered products or specific OS features you &                    want are available.  D           __________________________________________________________@           2.4  Is HP continuing funding and support for OpenVMS?                      Yes.   J                    Active development of new OpenVMS releases is underway,:                    as well as the continuation of support.  G                    Please see the following URLs for details, roadmaps,a+                    and related information:   4                    o  http://www.openvms.compaq.com/  I                    o  http://www.openvms.compaq.com/OPENVMS/strategy.htmli  L                    o  http://www.openvms.compaq.com/openvms/roadmap/openvms_"                       roadmaps.htm  A                    o  http://www.openvms.compaq.com/openvmstimes/_  3                    o  http://www.compaq.com/inform/   D           __________________________________________________________C           2.5  What OpenVMS CD-ROM distribution kits are available?h  7                    Various distributions are available.   @                    For information on the available part numbersC                    and current products (OpenVMS distribution kits, F                    media, documentation, etc) and associated licensingG                    information, please see the OpenVMS Software Product 3                    Description (SPD), available at:   5                    o  http://www.compaq.com/info/spd/ D                       OpenVMS typically uses SPD 25.01.xx and/or SPD                       41.87.xx.r                      2-4               &                    General Information        C                    The CD-ROMs listed in Table 2-1 contain just thecF                    OpenVMS Alpha operating system. These are bootable,=                    and can be used to run BACKUP from CD-ROM.m  J           ________________________________________________________________'           Table 2-1  OpenVMS Media Kits   J                    _______________________________________________________J                    Part______________Description__________________________  D                    QA-MT1AP-H8       OpenVMS Alpha V6.1-1H2 hardware3                                      release CD-ROM_  D                    QA-MT1AG-H8       OpenVMS Alpha V6.2-1H3 hardware3                                      release CD-ROMp  D                    QA-MT1AD-H8       OpenVMS Alpha V7.1-1H1 hardware3                                      release CD-ROMy  E                    QA-MT1AR-H8       OpenVMS Alpha V7.1-2 maintenance_3                                      release CD-ROMr  E                    QA-MT1AT-H8       OpenVMS Alpha V7.2-1 maintenanceu3                                      release CD-ROM   D                    QA-MT1AU-H8       OpenVMS Alpha V7.2-1H1 hardwareJ           ___________________________release_CD-ROM_______________________  D                    The table Table 2-2 contains the consolidated ECOJ                    distribution kit subscriptions, and these provide sitesG                    with eight updates of the current ECO kits per year:s  J           ________________________________________________________________%           Table 2-2  OpenVMS ECO Kits   J                    _______________________________________________________J                    Part______________Description__________________________  2                    QT-3CQAA-C8       OpenVMS Alpha  J           _________QT-3CRAA-C8_______OpenVMS_VAX__________________________  D                    The OpenVMS VAX and OpenVMS Alpha source listingsE                    CD-ROM sets listed in Table 2-3 include the source_E                    listings of most of OpenVMS, and these CD-ROM setsrE                    are invaluable for any folks working directly witheD                    OpenVMS internals, as well as folks interested inE                    seeing examples of various programming interfaces.r  J                                                                        2-5               &                    General Information        J           ________________________________________________________________8           Table 2-3  OpenVMS Source Listings CD-ROM Kits  J                    _______________________________________________________J                    Part______________Description__________________________  I                    QB-MT1AB-E8       OpenVMS Alpha Source Listings CD-ROMi  I                    QT-MT1AB-Q8       OpenVMS Alpha Source Listings CD-ROMd,                                      Updates  G                    QB-001AB-E8       OpenVMS VAX Source Listings CD-ROM   G                    QT-001AB-Q8       OpenVMS VAX Source Listings CD-ROM J           ___________________________Updates______________________________  D           __________________________________________________________3           2.6  In what language is OpenVMS written?/  E                    OpenVMS is written in a wide variety of languages.   A                    In no particular order, OpenVMS components are_H                    implemented using Bliss, Macro, Ada, PLI, VAX and DECG                    C, Fortran, UIL, VAX and Alpha SDL, Pascal, MDL, DECsI                    C++, DCL, Message, and Document. And this is certainly F                    not a complete list. However, the rumor is NOT trueI                    that an attempt was made to write pieces of OpenVMS in J                    every supported language so that the Run-Time LibrariesI                    could not be unbundled. (APL, BASIC, COBOL and RPG areA?                    just some of the languages NOT represented!)g  F                    There are a large variety of small and not-so-smallI                    tools and DCL command procedures that are used as partFI                    of the OpenVMS build, and a source code control systemsH                    capable of maintaining over a hundred thousand sourceG                    files across multiple parallel development projects, ,                    and overlapping releases.  D           __________________________________________________________;           2.7  Obtaining and Transfering OpenVMS licensees?e  ?                    The following sections describe hobbyist andoJ                    educational license programs, as well as information on5                    commercial licenses and transfers.m  F                    For information on the available commercial OpenVMSE                    licenses and for information on license transfers, C                    please see Section 2.7.3. For information on thetF                    licensing implementation, troubleshooting licensing                      2-6               &                    General Information        C                    problems, on the License Unit Requirements Tableg@                    (LURT), and other related details, please see                     Section 5.38.  '           _____________________________.?           2.7.1  Questions asked by Hobbyist OpenVMS licensees?a  E                    If you are a member of an HP-recognized user group_G                    (eg: Encompass, Enterex, DECUS), and are consideringm@                    acquiring and using a VAX or Alpha system forH                    hobbyist (non-commercial) use, (free) license productE                    authorization keys (PAKs) for OpenVMS VAX, OpenVMSr=                    Alpha, and layered products are available.i  C                    In addition to the license keys, OpenVMS VAX andmB                    Alpha distribution CD-ROM distribution kits areC                    available with OpenVMS, DECwindows Motif, DECnetrB                    and TCP/IP networking, compilers, and a varietyB                    of layered products. (While the hobbyist CD-ROMB                    distributions are intended for and tailored forF                    OpenVMS Hobbyists, the contents and capabilities ofE                    the Hobbyist installation kits included within the G                    OpenVMS Hobbyist distribution do not differ from theoH                    standard distribution installation kits. The productsJ                    are chosen to reflect the most popular products and the1                    space available on the media.)   J                    If you have questions on what else is authorized by theI                    license agreement and on what other distribution mediaoH                    is available to you, well, please read the applicable1                    software license agreement(s).s  ;                    For further information, please link to:   5                    o  http://www.openvmshobbyist.org/T  D                    On the OpenVMS Hobbyist license registration formE                    at the above website (as of January 2003), you areIJ                    offered the choice of the "OpenVMS VAX" license(s), theI                    "OpenVMS Alpha" license(s), and the "Layered Products"sG                    licenses. You will want the operating system licensenD                    for your particular OpenVMS platform and you willF                    want the "Layered Products" licenses. You will wantE                    to select and to acquire two sets of license PAKs.n  J                                                                        2-7 U  R          &                    General Information        G                    For vendors wishing to license products specifically_E                    for hobbyist use (and to not issue hobbyist PAKs),rF                    the program provides hobbyists with the license PAK$                    OPENVMS-HOBBYIST.  '           _____________________________P7           2.7.2  OpenVMS Educational and CSLG licenses?i  F                    For information on OpenVMS licenses for educational?                    customers, please see the HP Campus Software G                    License Grant (CSLG) license program and the OpenVMS /                    Educational license program:y  0                    o  http://www.openvmsedu.com/  '           _____________________________ @           2.7.3  How do I obtain or transfer an OpenVMS license?  J                    To transfer a commercial OpenVMS license from one ownerG                    to another, or to purchase a commercial license, you H                    can contact HP at 1-800-OK-COMPAQ (in North America),F                    or your local or regional sales office or reseller.  F                    Commercial software developers can join the HP DSPPC                    program, and can (potentially) receive discounts D                    on various software product licenses and softwareJ                    distributions, as well as on hardware purchases. Please8                    see Section 2.14 for details on DSPP.  I                    The DSPP program is the descendent of the DIGITAL ASAPa6                    program and the Compaq CSA program.  ?                    For information on the OpenbVMS Hobbyist andaC                    OpenVMS Educational license programs, please seey!                    Section 2.7.1.   D           __________________________________________________________=           2.8  Does OpenVMS support the Euro currency symbol?r  H                    OpenVMS can generate the %xA4 character code used forG                    the Euro, and the DECwindows DECterm can display the.J                    glyph. Please check with the vendor of your terminal or<                    terminal emulator for additional details.                      2-8 n  P          &                    General Information        C                    For additional information on the support of theiJ                    European Monetary Union Euro currency glyph on OpenVMS,                    please see:  9                    o  http://www.openvms.compaq.com/euro/e  D           __________________________________________________________G           2.9  Why hasn't OpenVMS been ported to Intel (IA-32) systems?r  +                    Why? Business reasons...   B                    There is presently a belief that there would beC                    insufficient market to justify the cost involvedaD                    in porting OpenVMS to systems using the Intel IA-C                    32 architecture. In addition to the direct costseE                    involved in any port, each maintainer of a product F                    or a package for OpenVMS has to justify the port toJ                    "OpenVMS Pentium" or to OpenVMS I64 (on Intel Itanium),I                    akin to the required justifications for a product port-5                    from OpenVMS VAX to OpenVMS Alpha.   ?                    But yes, it would certainly be nice to have.   8                    And yes, both OpenVMS Engineering and?                    OpenVMS management are well aware of the AMDlE                    Opteron/Hammer/AMD64 platform, and have also heard @                    many of the various "Yamhill" rumors as well.  F                    For an alternative approach (using a VAX emulator),,                    please see Section 13.13.  D           __________________________________________________________A           2.10  Are there any network-accessible OpenVMS systems?   E                    Yes, though various restrictions can and do apply.                       o  HobbesB                       Hobbes is a MicroVAX 3100 Model 40 for whichG                       free access and accounts are available to OpenVMSlJ                       enthusiasts. This system has BASIC, Pascal, Fortran,E                       and C compilers installed. If you would like anr>                       account on Hobbes, please see the FAQ at3                       http://www.hobbesthevax.com/.   J                                                                        2-9    o          &                    General Information        /                    o  OpenVMS Galaxy Test DriveiF                       HP currently offers an OpenVMS Galaxy Test DriveA                       system, based on an AlphaServer 4100 series @                       configured as two instances of the OpenVMS?                       operating system. For details, please seed=                       http://www.testdrive.compaq.com/galaxy/   '                    o  HP CSA Test Drive 6                       http://www.testdrive.compaq.com/  #                    o  Encompasserve 0                       telnet://eisner.decus.org/                      o  OpenECS H                       OpenECS offers free access to a VAX 6000 model 530:                       system. If interested, please visit:/                       http://vax6k.openecs.org/e  D           __________________________________________________________2           2.11  What version of OpenVMS do I need?  E                    For information on supported platforms, please see I                    the OpenVMS Software Product Description (SPD) for the :                    particular OpenVMS version of interest.  5                    o  http://www.compaq.com/info/spd/ D                       OpenVMS typically uses SPD 25.01.xx and/or SPD                       41.87.xx.a  I                    For a table of OpenVMS versions for various platforms,y                    please see:  M                    o  http://www.openvms.compaq.com/openvms/supportchart.html   ?                    For information on the Multia, related Alpha >                    single-board computers, or other officiallyE                    unsupported systems, please see Section 14.4.1 and $                    Section 14.4.2.1.  F                    The following is a rule-of-thumb for Alpha platformE                    support. The table Table 2-4 contains the earliestoF                    OpenVMS Alpha release with support for a particular3                    series of Alpha microprocessors:                       2-10h t  p          &                    General Information        J           ________________________________________________________________8           Table 2-4  OpenVMS Alpha Version Rule-Of-Thumb  J                    _______________________________________________________F                    Microprocessor                              GeneralJ                    Generation____________OpenVMS_Version_______Comments___  B                    21064 EV4             V1.0                  fewG                                                                systems; G                                                                most EV4 F                                                                requireE                                                                later; F                                                                upgradeH                                                                available  I                    21164 EV5             V6.2                  subsequentaF                                                                upgradeH                                                                available  I                    21164A EV56           V6.2-1H3              subsequenteI                                                                upgrade toeG                                                                V7.1 andeD                                                                later  I                    21264 EV6             V7.1-2                subsequentuF                                                                upgradeH                                                                typicallyH                                                                to V7.2-1G                                                                or lateru  I                    21264A EV67           V7.1-2                subsequenttF                                                                upgradeH                                                                typicallyH                                                                to V7.2-1G                                                                or later   Q                    xxxxxx EV68           V7.2-1                believed/probable;sH                                                                currentlyJ           _____________________________________________________expectation  D           __________________________________________________________2           2.12  How can I submit OpenVMS Freeware?  G                    For the guidelines and submission info, please visit                     the URL:t  H                    o  http://www.openvms.compaq.com/openvms/freeware/cd_                        guide.html  J                                                                       2-11 l  r          &                    General Information        C                    To order the current OpenVMS Freeware CD-ROM kitiH                    (shipping and handling charges apply), please request+                    part number QA-6KZAA-H8._  D           __________________________________________________________0           2.13  Porting applications to OpenVMS?  G                    Porting can range from simple to rather complex, andoI                    depends on the features used on the original platform.t  H                    This section covers generic porting, and porting fromJ                    OpenVMS VAX to OpenVMS Alpha. (Porting from OpenVMS VAXF                    to OpenVMS Alpha is often quite simple and involvesD                    little more than rebuilding from source, though aG                    few applications using features specific to VAX willn;                    require some additional effort to port.)r  I                    Several manuals on porting from OpenVMS VAX to OpenVMSrH                    Alpha are available in the OpenVMS documentation set,I                    including information on porting VAX Macro32 assembler D                    code to the Macro32 compiler on OpenVMS Alpha, onH                    management differences, on upgrading privileged code,-                    and application migration:-  9                    o  http://www.openvms.compaq.com:8000/s  8                    o  http://www.openvms.compaq.com/doc/  ?                    o  http://www.openvms.compaq.com/commercial/   I                    Details on the C programming environment are available                     at:  C                    o  http://www.openvms.compaq.com/commercial/c/c_a                        index.html  I                    Details on porting VAX C to HP C are are available at:s  G                    o  http://www.openvms.compaq.com/commercial/c/index_                        vax.htm   >                    An OpenVMS Porting Library is available at:  M                    o  http://www.openvms.compaq.com/ebusiness/Technology.html                       2-12                &                    General Information        H                    Information on the Enterprise Toolkit, a Visual-basedJ                    development environment for developing applications forG                    OpenVMS using a Microsoft platform, is available at:g  E                    o  http://www.openvms.compaq.com/commercial/et/et_i                        index.html  C                    Details on DCE, CORBA, BridgeWorks, and COM/DCOMd.                    middleware is available at:  N                    o  http://www.openvms.compaq.com/commercial/middleware.html  D                    Information on the COE standards is available at:  1                    o  http://diicoe.disa.mil/coe/c  F                    A wide variety of programming development tools andG                    middleware are available as commercial products (eg:OC                    DECset, IBM WebSphere MQ-formerly MQseries), andVF                    various tools are also available as shareware or asG                    Freeware. Please see other sections of this FAQ, and                     please see:  :                    o  http://www.compaq.com/csa/directory/  D           __________________________________________________________@           2.14  What resources are available to OpenVMS software                 developers?e  I                    The HP developer program DSPP is a program open to andnH                    intended to support and to assist HP OpenVMS software@                    partners, consultants, and service providers:  -                    o  http://www.hp.com/dspp/t  J                    DSPP provides members with various benifits, please see@                    the website for details. many other benefits.  C                    For those familiar with the program, the DIGITALuJ                    Association of Software and Application Partners (ASAP)D                    program has been incorporated into the Compaq CSAF                    program, and CSA has subsequently been incorporated,                    into the HP DSPP program.  J                                                                       2-13    H          &                    General Information      D           __________________________________________________________?           2.15  memory management, resource management, process                   scheduling, etc?  I                    So you have been instructed to write a school research C                    paper on OpenVMS, and you need technical content F                    on the OpenVMS Virtual Memory System, on any memoryG                    segmentation, on OpenVMS Resource Management, on the F                    OpenVMS File System, on the OpenVMS user interface,                    etc.a  E                    Invariably, your professor/instructor/teacher willaD                    ask you a series of questions. Most commonly, theH                    questions will request descriptions of one or more ofH                    the following items, and at varying levels of detail:  5                    o  process scheduling algorithm(s).  0                    o  Interprocess comunications  B                    o  Process or system synchronization constructs  =                    o  Memory management and/or virtual memory $                       implementation  0                    o  RMS or XQP file structures  )                    o  Resource management_  +                    o  History of HP OpenVMS   C                    o  History of Compaq and/or of Digital EquipmentV'                       Corporation (DEC)   E                    Any particular presentation or research paper, andnC                    particularly a scholastic presentation, can have F                    many different potential target audiences, and veryD                    different presentation levels. Further, the usualE                    underlying reason for scholastic presentations andeG                    scholastic research projects really has little to do"E                    with the subject matter, it is a task specificallysD                    intended to teach the student(s) (eg: you) how toE                    perform the research. The instructor already knowsuG                    most of (all of?) the information that you have been $                    asked to collect.                      2-14     t          &                    General Information        D                    For very technical details on OpenVMS and OpenVMSI                    internals, the book you want is the Internals and Data(E                    Structures Manual (IDSM), available in your schoolCH                    or computing center library, and the IDSM can also beG                    purchased. Additional technical details of the AlphabI                    microprocessor are available in the Alpha ArchitecturesG                    Reference Manual documentation that is available for G                    download. (Pointers to Alpha technical documentationSA                    are available in Section 14.6, and elsewhere.)r  I                    For higher-level (less technical) details, the OpenVMSiJ                    documentation set is available on-line. The ProgrammingH                    Concepts and the File Systems manual are probably theJ                    best manuals to start with, depending on the particular9                    level of detail the research requires.v  H                    And please understand the hesitation of various folksD                    to provide you with a completely-written researchH                    report on your topic. Why? We might have to work withI                    you after you graduate-you need to know how to perform I                    at least basic research on your own, regardless of the                     topic.r                                            J                                                                       2-15 r  e                    J                    _______________________________________________________              3        Documentation      D           __________________________________________________________A           3.1  Where can I find online copies of OpenVMS manuals?   I                    The HP OpenVMS and HP Layered Product documentation is (                    copyrighted material.  E                    HTML format on-line product documentation sets foraG                    specific HP OpenVMS products are presently available                     at:  9                    o  http://www.openvms.compaq.com:8000/   8                    o  http://www.openvms.compaq.com/doc/  ?                    o  http://www.openvms.compaq.com/commercial/r  J                    Documentation is offered on separately orderable CD-ROMG                    media through a subscription to the Consolidated On-/I                    Line Documentation (ConOLD) product (see Section 2.5.)cI                    ConOLD manuals are readable with BNU, a viewer that is H                    supplied with the documentation distribution. BNU canG                    display HTML, Bookreader, and documentation in othert                    formats.   G                    MGBOOK, a viewer for Bookreader-format documentation H                    is available for character-cell terminals (eg. VTxxx)F                    via the WKU VMS Freeware file server - see question,                    Section 13.1 for details.  D           __________________________________________________________B           3.2  What online information and websites are available?  G                    On your OpenVMS system, the HELP command can provideuD                    a wealth of information, not only on DCL commandsD                    but on system services (HELP System_Services) andE                    Run-Time Library routines (HELP RTL_Routines). TherH                    introduction displayed when you type the HELP commandI                    with no additional keywords provides further pointers.-  J                                                                        3-1 l  e                               Documentation        9                    OpenVMS Marketing runs a WWW server at-F                    http://www.openvms.compaq.com/. Here, you will findC                    product information, strategy documents, product H                    roadmaps, the contents of the latest OpenVMS Freeware#                    CD-ROM and more.u  J           ________________________________________________________________%           Table 3-1  OpenVMS Websitesr  J                    _______________________________________________________J                    URL_______Sponsor______________________________________  1                    http://www.openvms.compaq.com/ 8                    http://www.openvms.compaq.com/wizard/B                    http://www.openvms.compaq.com/wizard/wizard.zip  1                              HP OpenVMS Marketingi  2                    http://www.openvmshobbyist.org/  -                              Encompass DFWCUG.  /                    http://www.levitte.org/~ava/o  (                              Arne Vajhj  (                    http://www.saiga.com/  *                              Saiga Systems  ,                    http://www.tachysoft.com/  (                              Wayne Sewel  3                    http://www.progis.de/openvms.htm   9                              Sponsored by proGIS Softwaree  /                    http://www.jcameron.com/vms/i  )                              Jeff Cameron   B                    http://seqaxp.bio.caltech.edu/www/soft_doc.html  F                              David Mathog's (useful) information about%                              OpenVMS.                       Cracking   B                    http://www.vistech.net/users/beave/hack-vms-faq  (                              "The Beave"J                              Includes system cracking information that canG                              be of interest to OpenVMS System Managers,hJ                              and to OpenVMS Network and Security Managers.  (                    Undocumented Features                      3-2 o  e                               Documentation      J           ________________________________________________________________-           Table 3-1 (Cont.)  OpenVMS Websites_  J                    _______________________________________________________J                    URL_______Sponsor______________________________________  C                    http://www.decus.de:8080/www/vms/qaa/undoc.htmlx   -                              DECUS Deutchlands  <                    http://www.levitte.org/~ava/vms_tip.htmlx  (                              Arne Vajhj  :                    http://www.openvms.compaq.com/freeware/  B                              The OpenVMS Freeware contains variousB                              examples of undocumented features and'                              interfaces   !                    Bibliographies   =                    http://www.levitte.org/~ava/vms_book.htmlx                       Introductory   <                    http://www.levitte.org/~ava/vms_faq.htmlx  C                    http://seqaxp.bio.caltech.edu/www/vms_sheet.htmlt  C                    http://seqaxp.bio.caltech.edu/www/vms_beginners_i                    faq.html                       Programming  ?                    http://www.pdv-systeme.de/users/martinv/VMS_e'                    Programming_FAQ.html   7                              An OpenVMS Programming FAQo                      Networkingv  2                    http://www.tmesis.com/internet/  I                              Tutorial information and tips for connectingr<                              OpenVMS systems to the Internet  ?                    http://www.openvms.compaq.com/wizard/decnet/   H                              Documentation and Specifications for DECnet%                              Phase IV   +                    HP OpenVMS Documentationr  6                    http://www.openvms.compaq.com:8000/5                    http://www.openvms.compaq.com/doc/a<                    http://www.openvms.compaq.com/commercial/  J                                                                        3-3 m                                  Documentation      J           ________________________________________________________________-           Table 3-1 (Cont.)  OpenVMS Websites_  J                    _______________________________________________________J                    URL_______Sponsor______________________________________  H                              Various introductory guides as well as moreJ                              advanced manuals are available in the OpenVMSC                              and layered product documentation set.   2                    http://www.compaq.com/info/spd/  J                              Software Product Descriptions (SPDs) for mostD                              every OpenVMS-related product HP sells.  %                    System Performance   .                              See Section 14.2.  #                    Patch (ECO) Kits   C                              For the HP Services FTP server hosting E                              Various contract-access and non-contractiA                              access ECO (patch) kits, see sectiont*                              Section 5.16.  '                    Catalogs and Pricing_  Q                    http://www.compaq.com/products/quickspecs/productbulletin.html_  J                              HP Product QuickSpecs and product information  A                    http://www.compaq.com/products/quickspecs/soc_ -                    archives/SOC_Archives.htmla  E                              The HP Systems and Options Catalog (SOC) $                              archive  6                    http://www.businesslink.compaq.com/  A                              Pointers to country-specific product.C                              information, pricing, and related. The G                              services formerly provided by BusinessLink B                              are being replaced by these and otherH                              country-specific mechanisms, please see the-                              URL for details.                       PublicationsV  >                    http://www.openvms.compaq.com/openvmstimes/  9                              The OpenVMS Times Newslettere  )                    http://www.dfwcug.org/O  <                              The DFWCUG Quadwords Newsletter                      3-4    w                               Documentation      J           ________________________________________________________________-           Table 3-1 (Cont.)  OpenVMS Websites   J                    _______________________________________________________J                    URL_______Sponsor______________________________________  F                    http://www.research.compaq.com/wrl/DECarchives/DTJ/  F                              Back issues of the (discontinued) Digital4                              Technical Journal (DTJ)  0                    http://www.compaq.com/inFORM/  <                              The HP (Compaq) inFORM Magazine  1                    Hardware and Software Archivesv  7                    http://vax.sevensages.org/index.html   C                              The VAXarchive, including hardware and 1                              software informations  I                    http://www3.sympatico.ca/n.rieck/docs/alpha_diary.html2  9                              A VAX to Alpha upgrade diary   =                    http://www.montagar.com/~patj/dec/hcps.htm_  I                              Scanned versions of old DIGITAL manuals from #                              DFWCUG_  A                    http://www.digital.com/lists/master-index.html_  H                    http://www.compaq.com/support/techpubs/qrg/index.html  F                              A wide variety of HP VAX, Alpha, platformB                              and other product documentation. SomeJ           ___________________introductory,_some_technical.________________  D           __________________________________________________________=           3.3  OpenVMS Product Information Telephone Numbers?_  E                    Information on HP hardware, software, products and_I                    services is available through telephone numbers listeds                     in Table 3-2:  J           ________________________________________________________________&           Table 3-2  Telephone Numbers  J                    _______________________________________________________J                    Telephone_________Description__________________________  F                    1-800-AT-COMPAQ   HP (Compaq, including DIGITAL andB                                      Tandem) products and services  J                                                                        3-5 S                                  Documentation      J           ________________________________________________________________.           Table 3-2 (Cont.)  Telephone Numbers  J                    _______________________________________________________J                    Telephone_________Description__________________________  J           _________1-800-STORWORK____The_HP_StorageWorks_team_____________  D           __________________________________________________________F           3.4  How do I extract the contents of a HELP topic to a text                file?  C                    To extract all the text of a HELP topic (and its D                    subtopics) to a text file for perusal with a textI                    editor, printing out, etc., use the following command:   E                    $ HELP/OUT=filename.txt help-topic [help-subtopic]u  C                    If the help text you want is not in the standard E                    help library (for example, it's help for a utilityiC                    such as MAIL that has its own help library), addnC                    /LIBRARY=libname after the HELP verb. To see theeA                    names of help library files, do a directory ofi"                    SYS$HELP:*.HLB.  D           __________________________________________________________=           3.5  Does OpenVMS Marketing have an e-mail address?h  B                    Yes - if you can't get the answers to marketingJ                    questions elsewhere, if you have comments or complaintsG                    about OpenVMS, send mail to openvms-info@compaq.com.bG                    This address is not a support channel, and is solelyHE                    intended to provide informal method to communicateE>                    directly with members of OpenVMS Marketing.  D           __________________________________________________________C           3.6  Where can I learn about OpenVMS executive internals?   B                    The OpenVMS Internals and Data Structure manualC                    (IDSM) explains how the OpenVMS executive works.iG                    The book covers the operating system kernel: processMH                    management; memory management; the I/O subsystem; andE                    the mechanisms that transfer control to, from, and,I                    among these. It gives an overview of a particular area F                    of the system, followed by descriptions of the dataJ                    structures related to that area and details of the code,                    that implements the area.                      3-6                                    Documentation        H                    The first edition of the OpenVMS Alpha internals bookJ                    describes Version 1.5. Although there have been severalE                    releases of OpenVMS Alpha since Version 1.5 (V6.1, J                    V6.2, V7.0, V7.1, etc) and many details in the book areG                    no longer accurate, it continues to provide a strong ?                    conceptual description of OpenVMS internals.c  H                    This book has been split into five pieces, each to beG                    updated separately. The first such volume, publishedpB                    in early 1997, was "OpenVMS Alpha Internals andD                    Data Structures: Scheduling and Process Control,"F                    which covers the Version 7.0 implementation of trueE                    multithreading and the changed scheduling model ith                    implies.e  D                    The internals books are available through Digital)                    Press, see Section 3.7   D           __________________________________________________________B           3.7  Where can new users find tutorial information about                OpenVMS?s  H                    First, see if your local site has information on thisG                    topic. Each site can have site-specific features andaH                    configuration. Some sites will have site-specific newG                    user's documentation, covering various site-specificiJ                    things that are difficult or impossible for the general2                    OpenVMS documentation to cover.  '           _____________________________ #           3.7.1  Tutorial Websites?L  @                    Various websites with OpenVMS information areE                    available; Table 3-3 contains some suggested URLs.p  J           ________________________________________________________________.           Table 3-3  OpenVMS Tutorial Websites  J                    _______________________________________________________J                    URL_______Sponsor______________________________________                      Introductory   <                    http://www.levitte.org/~ava/vms_faq.htmlx  C                    http://seqaxp.bio.caltech.edu/www/vms_sheet.html   J                                                                        3-7                                    Documentation      J           ________________________________________________________________6           Table 3-3 (Cont.)  OpenVMS Tutorial Websites  J                    _______________________________________________________J                    URL_______Sponsor______________________________________  C                    http://seqaxp.bio.caltech.edu/www/vms_beginners_                     faq.html   ;                              Various introductory materials   9                    http://www.montagar.com/openvms_class/F  E                              Members of the Encompass DFWCUG maintainEE                              a website with many materials available,7A                              including an Overview of OpenVMS, an_D                              Introduction to DCL and the TPU Editor,E                              Advanced DCL Command Procedures, OpenVMSs?                              Operations: Batch, Print, Tape, anaC                              Introduction to OpenVMS Management, tor@                              OpenVMS User Management, to OpenVMSG                              Network Management, and to OpenVMS Cluster F                              Management. These training materials haveF                              been presented at various DECUS symposia.  +                    HP OpenVMS Documentation   6                    http://www.openvms.compaq.com:8000/5                    http://www.openvms.compaq.com/doc/_<                    http://www.openvms.compaq.com/commercial/  H                              Various introductory guides as well as moreJ                              advanced manuals are available in the OpenVMSC                              and layered product documentation set.   &                    HP OpenVMS Training  ;                    http://www.compaq.com/training/home.html ?                    http://www.openvms.compaq.com/wbt/index.html   I                              HP offers training information and Technical H                              Resource Kits (TRKs) and other Training forH                              OpenVMS. An OpenVMS certification (testing)7                              program is also available.   /                    http://www.jcameron.com/vms/a  ,                              An OpenVMS Quiz  +                    http://www.CCSScorp.com/d                      3-8 g  d                               Documentation      J           ________________________________________________________________6           Table 3-3 (Cont.)  OpenVMS Tutorial Websites  J                    _______________________________________________________J                    URL_______Sponsor______________________________________  B                              CCSS Interactive Learning has OpenVMS/                              training materialss  +                    http://www.acersoft.com/o  G                              AcerSoft Training information, and Shannon +                              Knows Punditry   )                    http://www.mindiq.com/s  J           ___________________MindIQ_training_information__________________  '           _____________________________ %           3.7.2  Books and Tutorials?l  B                    Some of the OpenVMS books that are or have been;                    available from the Digital Press imprintt  (                    o  http://www.bh.com/  +                    are listed in Table 3-4:   J           ________________________________________________________________           Table 3-4  DP Booksr  J                    _______________________________________________________J                    Title_and_Author__________________________ISBN_________  J                    Introduction to OpenVMS, 5th Edition      1 55558 194 3&                    Lesley Ogilvie Rice  J                    Introduction to OpenVMS                   1 878956 61 2                     David W Bynon  J                    OpenVMS Alpha Internals: Scheduling and   1 55558 156 0"                    Process Control  J                    OpenVMS AXP Internals and Data            1 55558 120 X*                    Structures: Version 1.5  J                    OpenVMS System Management Guide           1 55558 143 9                     Richard Berry  J                    The OpenVMS User's Guide, Second Edition  1 55558 203 6!                    Patrick Holmayr  J                                                                        3-9 t  m                               Documentation      J           ________________________________________________________________%           Table 3-4 (Cont.)  DP Books   J                    _______________________________________________________J                    Title_and_Author__________________________ISBN_________  J                    Using DECwindows Motif for OpenVMS        1 55558 114 5"                    Margie Sherlock  J                    VAX/VMS Internals and Data Structures:    1 55558 059 9                    Version 5.2  J                    Writing Real Programs in DCL, Second      1 55558 191 9                    EditionJ           _________Hoffman_and_Anagnostopoulos____________________________  G                    For various featured OpenVMS books, also please see:   F                    o  http://www.openvms.compaq.com/openvms/books.html  F                    For a bibliography of various OpenVMS books, please                    see:   @                    o  http://www.levitte.org/~ava/vms_book.htmlx  D           __________________________________________________________8           3.8  What OpenVMS mailing lists are available?  I                    Various OpenVMS mailing lists are available, with some @                    of the available lists detailed in Table 3-5.  J           ________________________________________________________________*           Table 3-5  OpenVMS Mailing Lists  J                    _______________________________________________________J                    Subscription______________________________Interest_Area  Q                    OpenVMS Freeware archive announcement     FSupdate@goatley.com                     list F                                                              FSupdate-S                                                              request@goatley.com[1]   J                    _______________________________________________________I                    [1]This is the subscription address. Usually, you will H                    want to send a mail message with no subject line, andF                    a SUBSCRIBE or HELP command in the body of the mail                    message.                       3-10     1                               Documentation      J           ________________________________________________________________2           Table 3-5 (Cont.)  OpenVMS Mailing Lists  J                    _______________________________________________________J                    Subscription______________________________Interest_Area  D                    Two-way echo of vmsnet.internals          VMSnet-R                                                              Internals@goatley.com  D                                                              VMSnet-G                                                              Internals- S                                                              request@goatley.com[1]n  C                    OpenVMS Alpha Internals discussions       Alpha-aL                                                              IDS@goatley.com  G                                                              Alpha-IDS- S                                                              request@goatley.com[1]   R                    BLISS discussions                         BLISSters@goatley.com  G                                                              BLISSters-_S                                                              request@goatley.com[1]_  B                    Process Software MultiNet mailing list    Info-Q                    (news gateway)                            MultiNet@process.comi  B                                                              Info-F                                                              MultiNet-S                                                              request@process.com[1]   B                    Process Software TCPware mailing list     Info-P                    (news gateway)                            TCPware@process.com  J                                                              Info-TCPware-S                                                              request@process.com[1]_  B                    Process Software PMDF mailing list (news  Info-M                    gateway)                                  PMDF@process.com   G                                                              Info-PMDF- S                                                              request@process.com[1]   J                    _______________________________________________________I                    [1]This is the subscription address. Usually, you will H                    want to send a mail message with no subject line, andF                    a SUBSCRIBE or HELP command in the body of the mail                    message.   J                                                                       3-11 p  M                               Documentation      J           ________________________________________________________________2           Table 3-5 (Cont.)  OpenVMS Mailing Lists  J                    _______________________________________________________J                    Subscription______________________________Interest_Area  H                    The SRI CHARON-VAX VAX emulator package   CHARON-VAX-N                                                              Users@process.com  D                                                              CHARON-G                                                              VAX-Users-aS                                                              request@process.com[1]   B                    Info-Zip's Zip & UnZip discussion list    Info-H                                                              Zip@wku.eduF                                                              Info-Zip-O                                                              Request@wku.edu[1]o  D                    RADIUS-VMS, a RADIUS server for OpenVMS   radius-H                    discussion forum                          vms@dls.netH                                                              radius-vms-O                                                              request@dls.net[1]r  A                    Internet Service Providers (ISPs)         vms- I                    running OpenVMS                           isps@dls.nettF                                                              vms-isps-O                                                              request@dls.net[1]a  T                    Users of Mark Daniel's WASD web server    http://wasd.vsm.com.au/4                    for OpenVMS VAX and Alpha exists.9                    Information about this list server andm:                    details on how to subscribe to the list;                    are available at the referenced website.i  h                    VMS Forum                                 http://www.neurophys.wisc.edu/comp/ava/vms_H                                                              forum.htmlxJ                    _______________________________________________________I                    [1]This is the subscription address. Usually, you will/H                    want to send a mail message with no subject line, andF                    a SUBSCRIBE or HELP command in the body of the mail                    message.sJ           ________________________________________________________________  D           __________________________________________________________D           3.9  What is this Ask The Wizard website I've heard about?  D                    The HP OpenVMS Ask The Wizard (ATW) website is anF                    informal area containing questions and answers on a*                    wide variety of topics.                      3-12  F  t                               Documentation        ;                    o  http://www.openvms.compaq.com/wizard/   E                    o  http://www.openvms.compaq.com/wizard/wizard.zipC  F                    For additional information, please see Section 3.9.  I                    To access a cited topic directly, use the URL filename J                    WIZ_topic-number.HTML. For example, topic (1020) can be3                    accessed directly using the URL:_  H                    o  http://www.openvms.compaq.com/wizard/wiz_1020.html  G                    A zip archive containing all of the available topics J                    and questions can be downloaded from the following URL:  E                    o  http://www.openvms.compaq.com/wizard/wizard.zip   G                    The wizard.zip zip archive is completely regenerated G                    when new batches of topics are posted out to the ATW                     website.t  B                    Before posting a question to the Ask The WizardG                    area, please read and please heed the posting rules- C                    and please remember to search this document, the H                    OpenVMS FAQ. And if you have a question that requiresC                    an answer, or if your question has time-critical F                    constraints or business constraints, please contact;                    the HP customer support center directly.c  D           __________________________________________________________G           3.10  Access to the OpenVMS Netscape Navigator documentation?   J                    The documentation URLs embedded into the browser itselfC                    may not operate correctly in all cases, and (for F                    reasons not worthy of repeating here) redirects may$                    not be available.  A                    You can manually access the documentation via:   E                    o  http://www.openvms.compaq.com:88/netscape/help/   I                    For information on the Mozilla web browser, please see                      Section 13.3.  J                                                                       3-13 i  r                    J                    _______________________________________________________  '           4        Time and Timekeepingi      D           __________________________________________________________I           4.1  UTC vs GMT vs vs UT1/UT1/UT2 TDF? What are these acronyms?l  D                    The results of an international compromise-thoughF                    some would say an international attempt to increaseH                    confusion-UTC is refered to as "Coordinated UniversalE                    Time" (though not as CUT) in English and as "Temps F                    Universel Coordinn" (though not as TUC) in French.G                    (No particular information exists to explain why UTCCI                    was chosen over the equally nonsensical TCU, according H                    to Ulysses T. Clockmeister, one of the diplomats thatB                    helped establish the international compromise.)  F                    Universal Time UT0 is solar time, UT1 is solar timeG                    corrected for a wobble in the Earth's orbit, and UT2tI                    is UT1 corrected for seasonal rotational variations in ;                    rotation due to the Earth's solar orbit.s  B                    GMT-Greenwich Mean Time-is UT1. GMT is the timeC                    at the classic site of the since-disbanded RoyalsJ                    Greenwich Observatory; at the most widely-known tourist4                    attraction of Greenwich, England.  D                    UTC is based on an average across multiple atomicI                    clocks, and is kept within 0.9 seconds of GMT, throughaI                    the insertion (or removal) of seconds. In other words, G                    UTC matches GMT plus or minus up to 0.9 seconds, but "                    UTC is not GMT.  H                    TDF is the Timezone Differential Factor, the intervalE                    of time between the local time and UTC. Areas that J                    celebrate daylight savings time (DST) will see periodicI                    changes to the TDF value, when the switch-over between_B                    daylight savings time and standard time occurs.C                    The switch-over itself is entirely left to local J                    governmental folks, and can and has varied by politicalF                    entity and politics, and the switch-over has varied<                    over the years even at the same location.  J                                                                        4-1 e  S          '                    Time and Timekeeping         B                    If your local OpenVMS system time is off by oneF                    hour (or whatever the local DST change) for some orD                    all applications, you probably need to reset yourG                    local TDF. (For related details, please see sections 4                    Section 4.4 and Section 10.24.1.)  I                    Further discussions of history and politics, the RoyalcH                    Observers' outbuildings, and the compromise that leftJ                    the English with the Time Standard (the Prime Meridian)E                    and the French with the standards for Distance andeH                    Weight (the Metric System) are left to other sources.J                    Some of these other sources include the following URLs:  2                    o  ftp://elsie.nci.nih.gov/pub/  C                    o  http://physics.nist.gov/GenInt/Time/time.htmlS  +                    o  http://nist.time.gov/_  D           __________________________________________________________>           4.2  A brief history of OpenVMS Timekeeping, please?  D                    Why does OpenVMS regards November 17, 1858 as the'                    beginning of time...   F                    The modified Julian date adopted by the SmithsonianI                    Astrophysical Observatory (SAO) for satellite tracking J                    is Julian Day 2400000.5, which turns out to be midnight(                    on November 17, 1858.  J                    SAO started tracking satellites with an 8K (nonvirtual)G                    36-bit IBM 704 in 1957 when Sputnik went into orbit. I                    The Julian day was 2435839 on January 1, 1957. This isvJ                    11225377 octal, which was too big to fit into an 18-bitJ                    field. With only 8K of memory, the 14 bits left over byG                    keeping the Julian date in its own 36-bit word would H                    have been wasted. SAO also needed the fraction of theH                    current day (for which 18 bits gave enough accuracy),F                    so it was decided to keep the number of days in theI                    left 18 bits and the fraction of a day in the right 18_$                    bits of one word.  I                    Eighteen bits allows the truncated Julian Day (the SAOwG                    day) to grow as large as 262143, which from NovemberpH                    17, 1858, allowed for 7 centuries. Possibly, the dateF                    could only grow as large as 131071 (using 17 bits),C                    but this still covers 3 centuries and leaves the                       4-2 n  a          '                    Time and Timekeeping         F                    possibility of representing negative time. The 1858I                    date preceded the oldest star catalogue in use at SAO, H                    which also avoided having to use negative time in any:                    of the satellite tracking calculations.  J                    The original Julian Day (JD) is used by astronomers andI                    expressed in days since noon January 1, 4713 B.C. This G                    measure of time was introduced by Joseph Scaliger in H                    the 16th century. It is named in honor of his father,G                    Julius Caesar Scaliger (note that this Julian Day is G                    different from the Julian calendar that is named foro5                    the Roman Emperor Julius Caesar!).t  E                    Why 4713 BC? Scaliger traced three time cycles andpF                    found that they were all in the first year of theirH                    cyle in 4713 B.C. The three cycles are 15, 19, and 28J                    years long. By multiplying these three numbers (15 * 19G                    * 28 = 7980), he was able to represent any date from .                    4713 B.C. through 3267 A.D.  J                    The starting year was before any historical event knownG                    to him. In fact, the Jewish calendar marks the startmG                    of the world as 3761 B.C. Today his numbering scheme I                    is still used by astronomers to avoid the difficulties I                    of converting the months of different calendars in usec)                    during different eras.   +                    The following web sites:   J                    o  http://www.openvms.compaq.com/openvms/products/year-$                       2000/leap.html  5                    o  http://www.eecis.udel.edu/~ntp/e  *                    o  http://www.nist.gov/  ;                    o  http://www.boulder.nist.gov/timefreq/r  A                    o  http://www.tondering.dk/claus/calendar.htmle  L                    o  http://es.rice.edu/ES/humsoc/Galileo/Things/gregorian_#                       calendar.htmlq  H                    are all good time-related resources, some general and,                    some specific to OpenVMS.  J                                                                        4-3 n  A          '                    Time and Timekeeping       '           _____________________________ <           4.2.1__Details_of_the_OpenVMS system time-keeping?  7           4.2.1.1__VAX_hardware_time-keeping details...              4.2.1.1.1  TOY clock  F                    This is battery backed up hardware timing circuitryJ                    used to keep the correct time of year during rebooting,G                    power failures, and system shutdown. This clock only J                    keeps track of months, days, and time. The time is keptJ                    relative to January 1st, at 00:00:00.00 of the year the*           _________clock_was_initiailized.  #           4.2.1.1.2  EXE$GQ_SYSTIME3  F                    This is the OpenVMS VAX system time cell. This cellG                    contains the number of 100ns intervals since a knownaF                    reference. This cell is incremented by 100000 every6           _________10ms_by_an_hardware_interval timer.  $           4.2.1.1.3  EXE$GQ_TODCBASE  G                    This cell contains the time and date the system timeuE                    was last adjusted by EXE$SETTIME. It uses the same H                    format as EXE$GQ_SYSTIME. On adjustment of the systemJ                    time a copy of EXE$GQ_SYSTIME is stored in this cell inH                    both memory and on disk. This cell is used to get the,           _________year_for_the_system_time.              4.2.1.1.4  EXE$GL_TODR  G                    This cell contains the time and date the system timenE                    was last adjusted by EXE$SETTIME. It uses the same I                    format as the time of year clock. On adjustment of the G                    system time this cell gets saved back to both memoryaG                    and disk. The contents of this cell are used to testn1                    the validity of the TOY clock. C                    The system parameters SETTIME and TIMEPROMPTWAITt=                    determine how the system time will be set.S             IF SETTIME = 0H                       THEN the contents of the TOY clock are compared toJ                       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..  G                      o  IF the TOY clock is within a day of EXE$GL_TODRyF                         THEN the system time is calculated as follows:                      4-4               '                    Time and TimekeepingL        H                      o  EXE$GQ_SYSTIME = EXE$GQ_TODCBASE + ((TOY_CLOCK -.                         EXE$GL_TODR) * 100000)  @                    o  IF SETTIME = 1 or the TOY clock is invalidH                       THEN the value of TIMEPROMPTWAIT determines how toD                       reset the time of year.  IF TIMEPROMPTWAIT > 0H                         THEN the user is prompted for the time and date,D                         for a length of time equal to TIMEPROMPTWAIT(                         microfortnights.  -                      o  IF TIMEPROMPTWAIT = 0_I                         THEN the time of year is the value of EXE$GL_TODRn                         + 10ms.   -                      o  IF TIMEPROMPTWAIT < 0_4                         to proceed until they do so.  G                      o  THEN the user is prompted for the time and datee"                         and unable  J                    When booting a CD-ROM containing an OpenVMS VAX system,G                    the system will typically be deliberately configuredhH                    prompt the user to input the time - this is necessary:                    in order to boot with the correct time.  G                    If either TIMEPROMPTWAIT or SETTIME are set to zero, H                    OpenVMS VAX will use the TOY clock to get the time ofF                    year, and the year will be fetched from the CD-ROM.J                    The value of the year on the CD-ROM media (saved withinF                    the SYS.EXE image) will most likely be that of whenI                    the CD-ROM was made, and cannot be changed. Unless therF                    current year happens to be the same year as that onJ                    the CD-ROM, most likely the year will be off. (Further,I                    with the calculation of Leap Year also being dependent G                    on the current year, there is a possibility that the *                    date could be off too.)  '           ______________________________9           4.2.1.2  Alpha hardware time-keeping details...           J                                                                        4-5 o  t          '                    Time and Timekeeping       '           _____________________________t9           4.2.1.2.1  Battery-Backed Watch (BB_WATCH) Chipl  F                    This is battery backed up hardware timing circuitryJ                    used to keep the correct time of year during rebooting,H                    power failures, and system shutdown. This clock keepsC           _________track_of_date_and_time in 24 hour binary format.s  #           4.2.1.2.2  EXE$GQ_SYSTIME   H                    This is the OpenVMS Alpha system time cell. This cellH                    contains the number of 100ns intervals since NovemberD                    17, 1858 00:00:00.00. This cell is incremented byC           _________100000_every_10ms_by an hardware interval timer._  )           4.2.1.2.3  EXE$GQ_SAVED_HWCLOCK_  J                    This cell is used by OpenVMS Alpha to keep track of theJ                    last time and date that EXE$GQ_SYSTIME was adjusted. ItJ                    keeps the same time format as EXE$GQ_SYSTIME. The valueI                    in this cell gets updated in memory and on disk, every 5                    time EXE$GQ_SYSTIME gets adjusted._  F                    o  The system parameters SETTIME and TIMEPROMPTWAIT@                       determine how the system time will be set.  D                    o  If SETTIME = 0 then EXE$INIT_HWCLOCK reads the<                       hardware clock to set the system time.  -                      o  IF TIMEPROMPTWAIT > 0 G                         THEN the value of TIMEPROMPTWAIT determines how C                         long the user is prompted to enter the time F                         and date. If time expires and no time has beenI                         entered the system acts as if TIMEPROMPTWAIT = 0.   -                      o  IF TIMEPROMPTWAIT = 0eC                         THEN the system time is calculated from they=                         contents of EXE$GQ_SAVED_HWCLOCK + 1._  -                      o  IF TIMEPROMPTWAIT < 0 G                         THEN the user is prompted for the time and date G                         and unable to continue until the information is                           entered.  G           Unlike the VAX, the Alpha hardware clock tracks the full dateoH           and time, not just the time of year. This means it is possibleH           to boot from the CD-ROM media without entering the time at theF           CD-ROM bootstrap. (This provided that the time and date have'           been initialized, of course.)_                      4-6 _  _          '                    Time and TimekeepingO        F                    IA-64 (Itanium) hardware time-keeping details to be                    added...   '           _____________________________eE           4.2.1.3  Why does VAX need a SET TIME at least once a year?   I                    Because the VAX Time Of Year (TOY) has a resolution ofuE                    497 days, the VAX system time is stored using bothoD                    the TOY and the OpenVMS VAX system image SYS.EXE.G                    Because of the use of the combination of the TOY andtF                    SYS.EXE, you need to issue a SET TIME command (withG                    no parameters) at least once between January 1st and I                    about April 11th of each year, and whenever you change D                    system images (due to booting another OpenVMS VAXF                    system, booting the standalone BACKUP image, an ECO/                    that replaces SYS.EXE, etc).S  F                    The SET TIME command is automatically issued duringH                    various standard OpenVMS procedures such as SHUTDOWN,D                    and it can also obviously be issued directly by aI                    suitably privileged user. Issuing the SET TIME commandiI                    resets the value stored in the TOY, and (if necessary)fJ                    also updates the portion of the time (the current year)5                    saved in the SYS.EXE system image.s  C                    This VAX TOY limit is the reason why OpenVMS VAX E                    installation kits and standalone BACKUP explicitlynI                    prompt for the time during bootstrap, and why the time J                    value can "get weird" if the system crashes outside theJ                    497 day window (if no SET TIME was issued to update theH                    saved values), and why the time value can "get weird"G                    if a different SYS$SYSTEM:SYS.EXE is used (alternate 8                    system disk, standalone BACKUP, etc).  '           _____________________________c;           4.2.2  How does OpenVMS VAX maintain system time?t  I                    VAX systems maintain an interval clock, and a hardwarer                    clock.   E                    The VAX hardware clock is called the TOY ("Time OflJ                    Year") clock. The register associated with the clock is<                    called the TODR ("Time Of Day Register").  J                                                                        4-7    a          '                    Time and Timekeeping         H                    The TOY clock-as used-stores time relative to JanuaryI                    first of the current year, starting at at 00:00:00.00._J                    It is a 100 Hz, 32-bit counter, incremented every 10ms,=                    and thus has a capacity of circa 497 days.   C                    OpenVMS (on the VAX platform) stores system datefE                    information-and in particular, the current year-ine8                    the system image, SYS$SYSTEM:SYS.EXE.  E                    The TOY is used, in conjunction with the base datenI                    that is stored and retrieved from the system image, to_H                    initialize the interval clock value that is stored in"                    EXE$GQ_SYSTIME.  E                    Once the interval clock is loaded, the system doesrF                    not typically reference the TOY again, unless a SETD                    TIME (with no parameters) is issued. The intervalF                    clock value is updated by a periodic IPL22 or IPL24H                    (depending on the specific implementation) interrupt.H                    (When these interrupts are blocked as a result of theG                    activity of higher-IPL code-such as extensive driver J                    interrupt activity or a hardware error or a correctableG                    (soft) memory error-the clock will "loose" time, andnJ                    the time value reported to the user with appear to have                     slowed down.)  B                    On most (all?) VAX systems, the battery that isH                    associated with the TOY clock can be disconnected andE                    replaced if (when) it fails-TOY clock failures are J                    quite commonly caused by a failed nickel-cadmium (NiCd)B                    or lithium battery, or by a failed Dallas chip.  D           __________________________________________________________<           4.3  Keeping the OpenVMS system time synchronized?  D                    To help keep more accurate system time or to keepH                    your system clocks synchronized, TCP/IP Services NTP,F                    DECnet-Plus DECdtss, DCE DTSS, and other techniquesG                    are commonly used. If you do not have IP access to anJ                    time-base, then you could use dial-up access to NIST or,                    other authoritative site.  F                    There exists code around that processes the digitalC                    (ie: binary) format time that is available via a I                    modem call into the NIST clock (the Automated Computer E                    Telephone Service (ACTS)), and code that grabs the                       4-8 i  l          '                    Time and Timekeepingm        F                    time off a GPS receiver digital link, or a receiverC                    (effectively a radio and a codec) that processes G                    the time signals from radio station WWV, WWVH, WWVB,_E                    or similar. (Processing these time protocols oftennC                    involves little more than reading from an EIA232_H                    (RS232) serial line from the receiver, something thatI                    is possible from most any language as well as directlyS                    from DCL.)V  C                    One example of acquring a time-base involves the E                    IRIG time format (IRIG-A, -B, -G), a binary signalrI                    containing the current time in hours, minutes, secondsrE                    and days since the start of the current year. IRIG_D                    can also contain the time of day as the number ofG                    seconds since midnight. HP Custom Systems and third- J                    party vendors offer various IRIG-based reader/generator/                    modules for OpenVMS systems.t  @                    Differing time servers (DECnet-Plus DTSS, DCED                    DTSS, NTP, etc) do not coexist particularly well,D                    particularly if you try to use all these togetherF                    on the same node. Please pick and use just one. (IfE                    needed, you can sometimes configure one package to_F                    acquire its timebase from another protocol, but oneF                    and only one time server package should have directE                    control over the management of and drifting of the E                    local OpenVMS system time. In the specific case ofuH                    DECnet-Plus DTSS, older product versions and versionsE                    V7.3 and later provide a provider module, a module G                    which permits DTSS to acquire its time from NTP. For I                    details on this, please see the comments in the module (                    DTSS$NTP_PROVIDER.C.)                      Useful URLs:   J                    o  http://www.boulder.nist.gov/timefreq/service/nts.htm  K                    o  http://www.boulder.nist.gov/timefreq/service/acts.htmn  ;                    o  http://www.boulder.nist.gov/timefreq/_  *                    o  http://www.time.gov/    J                                                                        4-9 _  _          '                    Time and Timekeeping_      '           _____________________________ 7           4.3.1  Why does my OpenVMS system time drift?1  E                    Memory errors, hardware problems, or most anythingtG                    operating at or above IPL 22 or IPL 24 (clock IPL is5F                    system family dependent; code executing at or aboveC                    the clock IPL will block the processing of clockAH                    interrupts), can cause the loss of system time. ClockE                    drift can also be caused by normal (thermal) clocktE                    variations and even by the expected level of clockr                    drift.O  G                    When clock interrupts are blocked as a result of thepE                    activity of high-IPL code-such as extensive driver_J                    interrupt activity or a hardware error or a correctableG                    (soft) memory error-the clock will "loose" time, andaJ                    the time value reported to the user with appear to haveI                    slowed down. Correctable memory errors can be a common_=                    cause of system time loss, in other words.   G                    Clock drift can also be (deliberately) caused by the 8                    activity of the DTSS or NTP packages.  <                    Also see Section 14.8, Section 14.15, and!                    Section 4.3.2.o  '           _____________________________ 9           4.3.2  How can I drift the OpenVMS system time?   G                    With DECdts and TCP/IP Services NTP, the system timecI                    value is "drifted" (rather than changed), to avoid the_H                    obvious problems that would arise with "negative timeG                    changes". The same basic clock drifting technique istI                    used by most (all?) time servers operating on OpenVMS,hI                    typically using the support for this provided directly "                    within OpenVMS.  D                    An example of the technique used (on OpenVMS VAX)G                    to drift the system time is the SETCLOCK tool on the $                    OpenVMS Freeware.  J                    For information on the use of the EXE$GL_TIMEADJUST andH                    EXE$GL_TICKLENGTH cells on OpenVMS Alpha, see OpenVMSI                    AXP Internal and Data Structures, located on page 348.                       4-10a y  m          '                    Time and Timekeeping         H                    For those areas which switch between daylight savingsF                    time (DST) and standard time, the time value is notH                    drifted. The time is adjusted by the entire interval.F                    This procedure is inherent in the definition of the8                    switch between DST and standard time.  '           _____________________________IB           4.3.3  How can I configure TCP/IP Services NTP as a time                  provider?  H                    An NTP time provider provides its idea of the currentI                    time to NTP clients via the NTP protocol. Most systemse*                    are NTP clients, but...  D                    NTP has a heirarchy of layers, called strata. TheI                    further away from the actual NTP time source (InternetwG                    time servers are at stratum 1), the lower the strata C                    (and the larger the number assigned the statum).   H                    NTP explicity configured at stratum one provides timeJ                    to NTP operating at lower strata, and the provided timeI                    is acquired based on the local system time or via some(;                    locally-accessible external time source.   E                    NTP at other (lower) strata both receive time fromrF                    higher strata and can provide time to lower strata,J                    and automatically adjust the local stratum. The highestF                    stratum is one, and the lowest available stratum is                    fifteen.   E                    The TCP/IP Services NTP package can operate at any I                    stratum, and can be configured as a peer, as a client, I                    or as a broadcast server. NTP can also provide time to_?                    a DECnet-Plus DTSS network, see Section 4.3.l  J                    With TCP/IP Services V5.0 and later, the only supportedF                    reference clock is the LCL (local system clock). IfF                    your system has an excellent clock or if the systemF                    time is being controlled by some other time serviceF                    or peripheral (such as DTSS services, GPS services,E                    a cesium clock, a GPIB controller or other similarSI                    time-related peripheral), you can configure NTP to use_F                    the system clock as its reference source. This willJ                    mimic the master-clock functionality, and will configreH                    NTP as a stratum 1 time server. To do this, enter the8                    following commands in TCPIP$NTP.CONF:  J                                                                       4-11               '                    Time and Timekeeping         ,                    server 127.127.1.0 prefer.                    fudge 127.127.1.0 stratum 0  H                    For local-master functionality, the commands are very!                    similiar. Use:   %                    server 127.127.1.0 .                    fudge 127.127.1.0 stratum 8  G                    The difference between these two is the stratum, and J                    the omission of the prefer keyword. Specifying a higherI                    stratum allows the node to act as a backup NTP server, H                    or potentially as the sole time server on an isolatedG                    network. The server will become active only when all H                    other normal synchronization sources are unavailable.C                    The use of "prefer" causes NTP to always use the F                    specified clock as the time synchronization source.  C                    With the TCP/IP Services versions prior to V5.0, B                    the NTP management is rather more primitive. ToA                    configure the local OpenVMS system from an NTP.G                    client to an NTP server (on TCP/IP Services versions @                    prior to V5.0), add the following line to the;                    sys$specific:[ucx$ntp]ucx$ntp.conf file:   !                    master-clock 1   G                    Also, for TCP/IP Services prior to V5.0, see the NTP !                    template file:   9                    SYS$SPECIFIC:[UCX$NTP]UCX$NTP.TEMPLATE_  H                    Note that NTP does not provide for a Daylight SavingsF                    Time (DST) switch-over, that switch must arise fromI                    the timezone rules on the local system and/or from thedE                    SYS$EXAMPLES:DAYLIGHT_SAVINGS procedure. (Further,_A                    there is a known bug in SYS$EXAMPLES:DAYLIGHT_ G                    SAVINGS.COM in V7.3, please obtain the available ECO                     kit.)  B                    For current TCP/IP Services and related OpenVMS-                    documentation, please see:   9                    o  http://www.openvms.compaq.com:8000/   8                    o  http://www.openvms.compaq.com/doc/  ?                    o  http://www.openvms.compaq.com/commercial/                       4-12p w  N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faqsN  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.com,   ------------------------------  # Date: Thu, 03 Jul 2003 17:12:10 GMT_2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman); Subject: OpenVMS Frequently Asked Questions (FAQ), Part 3/9c2 Message-ID: <KtZMa.3893$bl3.2093@news.cpqcorp.net>               '                    Time and Timekeeping       D           __________________________________________________________J           4.4  Managing Timezones, Timekeeping, UTC, and Daylight Savings?  >                    You will want to use the command procedure:  4                    o  SYS$MANAGER:UTC$TIME_SETUP.COM  H                    to configure the OpenVMS Timezone Differential FactorC                    (TDF) on OpenVMS V6.0 and later. Select the BOTH D                    option. This configures the OpenVMS TDF settings,E                    though it may or may not configure the TDF and the B                    timezone rules needed or used by other softwareH                    packages. Please do NOT directly invoke the following&                    command procedures:  I                    o  SYS$MANAGER:UTC$CONFIGURE_TDF.COM ! do not directly_                       use   J                    o  SYS$MANAGER:UTC$TIMEZONE_SETUP.COM ! do not directly                       use   F                    TCP/IP Services V5.0 and later use the OpenVMS TDF,H                    UTC, and timezone support. Earlier versions use a TDFJ                    mechanism and timezone database that is internal to theI                    TCP/IP Services package. Also on the earlier versions,/D                    the TDF must be manually configured within TCP/IPE                    Services, in addition to the OpenVMS configurationS                    of the TDF.  F                    DECnet-Plus in V7.3 and later uses the OpenVMS TDF,G                    UTC, and timezone support, and displays its timezone_I                    prompts using UTC$TIME_SETUP.COM. Earlier versions use H                    a TDF TDF mechanism, timezone database, and automaticB                    switch-over that is internal to the DECnet-PlusE                    package. Also on earlier versions, the TDF must be H                    configured within the DECnet-Plus DECdtss package, inD                    addition to the OpenVMS configuration of the TDF.  B                    Application code using HP C (formerly Compaq C,C                    formerly DEC C) will use the OpenVMS UTC and TDF I                    mechanisms when the C code is compiled on OpenVMS V7.0 F                    and later (and when the macro _VMS_V6_SOURCE is NOTF                    defined). HP C does NOT use the OpenVMS UTC and TDFD                    mechanisms when the C code is compiled on OpenVMSC                    releases prior to V7.0, or when the preprocessor :                    declaration _VMS_V6_SOURCE is declared.  J                                                                       4-13 a  t          '                    Time and Timekeepingr        ,                    DCE DTSS TDF details TDB.  E                    In OpenVMS Alpha V6.1, V6.2, and V6.2-1Hx, the TDFeG                    value is written to SYS$BASE_IMAGE.EXE. With OpenVMS E                    Alpha V7.0 and later and with OpenVMS VAX V6.0 andnG                    later, SYS$SYSTEM:SYS$TIMEZONE.DAT contains the TDF.lJ                    This means that OpenVMS Alpha systems will need to haveI                    the TDF value reset manually-usually within SYSTARTUP_o4                    VMS.COM-on reboots prior to V7.0.  E                    During OpenVMS Bootstrap, the SYSINIT module reads E                    SYS$TIMEZONE.DAT to acquire the TDF for use in the H                    system global cell EXE$GQ_TDF. This is done to ensureH                    that the system boots with a valid TDF (a value whichD                    may be zero). The UTC system services get the TDFF                    from this cell. These services, as well as the HP CF                    RTL, must have a valid TDF. (Prior to OpenVMS V7.3,D                    if either DECnet-Plus or DECnet/VAX Extensions isF                    configured and run, the image DTSS$SET_TIMEZONE.EXEH                    is invoked and can override the TDF and timezone ruleD                    settings from SYSINIT or from UTC$TIME_SETUP.COM-C                    this image runs even if DTSS is disabled. If the C                    settings do not match (due to inconsistencies in C                    timezone specification in UTC$TIME_SETUP.COM and J                    NET$CONFIGURE.COM), DTSS will reset the values to match$                    its definitions.)  J                    Prior to OpenVMS V7.3, daylight savings time switchoverI                    is handled automatically only when DCE DTSS or DECnet- J                    Plus DTSS is in use. In V7.3, OpenVMS can be configuredC                    to automatically switch over to daylight savingseD                    time, and also generates an event that interestedI                    applications can use to detect the switch-over betweene3                    standard time and daylight time.u  F                    The manual switchover between daylight savings timeF                    and standard time is correctly accomplished via theF                    SYS$EXAMPLES:DAYLIGHT_SAVINGS.COM command procedure                    procedure._  G                    Note: NTP (alone) does NOT provide automatic switch-e                    over.  D                    Note: The DST switch-over does NOT drift the timeJ                    value; the switch-over applies the entire difference as                    a unit.                      4-14o s  l          '                    Time and Timekeeping         J                    If you switch the TDF or daylight savings time setting,I                    you will also want to restart or reconfigure any time-tC                    sensitive applications (those not using the time F                    differential factor (TDF) change event available inJ                    V7.3 and later). Examples of these applications includeI                    the need to restart the NFS client and (yes) NTP. (NTPoJ                    will want to try to "drift" the time (see Section 4.3),I                    and will find the daylight savings time switch-over toaG                    be far too large to "drift". Hence the NTP restart.) F                    You can also use the (undocumented) TCP/IP Services,                    (prior to V5.0) commands:  C                    SET TIME/DIFF=[positive or negative TDF integer]                      GENERATE TIME  B                    to reset the value of the logical name UCX$TDF.  .                    Prior to V7.3, the command:  <                    $ SETTZ :== $SYS$SYSTEM:DTSS$SET_TIMEZONE!                    $ SETTZ MODIFY   J                    can be used to modify the settings of the SYS$TIMEZONE_B                    DAYLIGHT_SAVING, SYS$TIMEZONE_DIFFERENTIAL, andF                    SYS$TIMEZONE_NAME system logical names based on the%                    SYS$TIMEZONE_RULE.s  D                    The following are other TDF-related logical namesB                    used/available on OpenVMS systems, with typicalD                    Daylight Savings and Standard Settings for the US.                    Eastern Time (ET) timezone.  "                    $daylight_time:>                    $ DEFINE/SYSTEM/EXECUTIVE MAIL$TIMEZONE EDTG                    $ DEFINE/SYSTEM/EXECUTIVE NOTES$TIMEZONE "-0400 EDT"mZ                    $ DEFINE/SYSTEM/EXECUTIVE LISP$DAYLIGHT_SAVING_TIME_P true  ! Not 'EDT'K                    $ DEFINE/SYSTEM/EXECUTIVE LISP$TIME_ZONE 05   ! Constant                     $"                    $standard_time:>                    $ DEFINE/SYSTEM/EXECUTIVE MAIL$TIMEZONE ESTG                    $ DEFINE/SYSTEM/EXECUTIVE NOTES$TIMEZONE "-0500 EST" Z                    $ DEFINE/SYSTEM/EXECUTIVE LISP$DAYLIGHT_SAVING_TIME_P false ! Not 'EST'K                    $ DEFINE/SYSTEM/EXECUTIVE LISP$TIME_ZONE 05   ! Constant                     $H                    $ DEFINE/SYSTEM/EXECUTIVE UCX$NFS_TIME_DIFFERENTIAL -U                        'f$integer(f$element(0," ",f$logical("notes$timezone"))/-100)'   J                                                                       4-15 n  i          '                    Time and Timekeeping         J                    For information on ZIC and related tools used to manageF                    the OpenVMS Timezone database, please see the DEC CI                    Run-time Library Utilities Reference Manual-though themF                    title would imply otherwise, this particular manualD                    is part of the OpenVMS documentation set, and notG                    part of the HP C (formerly Compaq C, formerly DEC C) %                    documentation set.   '           _____________________________p=           4.4.1  How to troubleshoot TDF problems on OpenVMS?   H                    This is an OpenVMS Alpha system prior to V7.0 and the9                    startup is not invoking the procedure:   1                    SYS$MANAGER:UTC$TIME_SETUP.COMr  J                    This is an OpenVMS system prior to V6.0, where there is4                    no OpenVMS TDF nor UTC available.  J                    The version of the application does not use the OpenVMSD                    TDF. This includes TCP/IP Services prior to V5.0,H                    applications using HP C built on or targeting OpenVMSH                    prior to V7.0, and systems using the DECnet-Plus DTSSJ                    mechanisms prior to the release associated with OpenVMS'                    V7.3. (DCE TDF TBD.)e  A                    If you should find either of the following twoe=                    timezone-related database files located in )                    SYS$SPECIFIC:[SYSEXE]:c  ;                    o  SYS$SPECIFIC:[SYSEXE]SYS$TIMEZONE.DAT   ?                    o  SYS$SPECIFIC:[SYSEXE]SYS$TIMEZONE_SRC.DAT   H                    These two files are in an erroneous location and must9                    be recreated in the correct directory:   &                    SYS$COMMON:[SYSEXE]  &                    If the DCL command:  ;                    $ DIRECTORY SYS$SYSTEM:SYS$TIMEZONE*.DATr  J                    shows these files in SYS$SPECIFIC:[SYSEXE], then deleteJ                    them and use SYS$MANAGER:UTC$TIME_SETUP.COM to recreate                    them.                      4-16h y  m          '                    Time and Timekeeping$        B                    On OpenVMS versions prior to V7.3, if the file:  5                    $ SYS$STARTUP:DTSS$UTC_STARTUP.COMo  J                    is present on your system, then you may need to invoke:  ?                    $ @SYS$UPDATE:DTSS$INSTALL_TIMEZONE_RULE.COM_  C                    to recreate the timezone files correctly. Invoke ?                    this command immediately after [re]executing 3                    SYS$MANAGER:UTC$TIME_SETUP.COM.)t  F                    If SYS$UPDATE:DTSS$INSTALL_TIMEZONE_RULE.COM is notG                    present on your system, then you may need to executeo*                    the following commands:  <                    $ DELETE SYS$STARTUP:DTSS$UTC_STARTUP.COM<                    $ DEASSIGN/SYSTEM/EXEC SYS$TIMEZONE_RULE.  H                    If your system time is being reported as being off byJ                    one hour (or whatever the local DST change), please seeI                    sections Section 4.1, Section 4.4 and Section 10.24.1.h  '           _____________________________r9           4.4.2  Customizing your TDF (Timezone) Setting?   I                    Individual, local, and regional differences on the use J                    (or the lack of use) of Daylight Savings Time (DST) are                     quite common.  B                    If you need to add (or remove) daylight savingsF                    time for your area or otherwise alter the rules forG                    your local area, you will probably end up creating aX:                    variation to an existing timezone rule.  H                    The necessary zone line to add for WhereEverLand will5                    probably look something like this:   R                    # Zone  NAME            GMTOFF  RULES/SAVE      FORMAT  [UNTIL]L                    Zone    WhereEver       2:00    -               WhereEver  G                    The OpenVMS source file for the timezone rules here:   ;                    SYS$COMMON:[SYS$ZONEINFO.SYSTEM.SOURCES]H  B                    You'll then want to ZIC this to create your own&                    timezone definiton.  J                                                                       4-17               '                    Time and Timekeeping         I                    ZIC is documented in the OpenVMS Documentation Set, innG                    the HP C Run-Time Library Reference Manual. (DespiteeD                    the name of the manual, it is part of the OpenVMS<                    documentation set and not the C manuals.)  :                    Once you have created the new rule, useC                    SYS$MANAGER:UTC$TIME_SETUP.COM to select the new J                    timezone-with V7.3 and later, this tool will notice theG                    new timezone and will offer it, on earlier releases, F                    you may/will have to hack the tool somewhat. (Don'tG                    even think of trying to define the TZ or other time- <                    related logical names directly yourself.)  J                    For various timezone rules, see the tar.gz files (these:                    are gzipped tar archives) available at:  2                    o  ftp://elsie.nci.nih.gov/pub/  D           __________________________________________________________F           4.5  Why does the SET TIME command fail? Help managing DTSS?  F                    If you try to set the system time with the SET TIMEB                    command, and see one of the following messages:  6                    %SET-E-NOTSET, error modifying timeC                    -SYSTEM-F-IVSSRQ, invalid system service request   6                    %SET-E-NOTSET, error modifying timen                    -SYSTEM-E-TIMENOTSET, time service enabled; enter a time service command to update the time  A                    This occurs if the time on the local system isoE                    controlled by a time service software, for exampleoH                    the distributed time service software (DTSS) providedD                    as part of the DECnet-Plus installation. The DTSSF                    software communicates with one or more time serversG                    to obtain the current time. It entirely controls the1I                    local system time (for DECnet-Plus, there is a process_F                    named DTSS$CLERK for this); therefore, the usage ofJ                    the SET TIME command (and the underlying $SETTIM system(                    service) is disabled.  D                    The first message is displayed on systems runningF                    DECnet-Plus V6.1 and earlier. On systems with newerJ                    DECnet-Plus software, the second (and more informative)$                    message is given.                      4-18     t          '                    Time and Timekeeping         G                    You shouldn't have to change the time manually - youfH                    should be doing this through the time server - but if>                    you insist... you'll have to shutdown DTSS:  '                    $ RUN SYS$SYSTEM:NCL                     DISABLE DTSSd                    DELETE DTSS  I                    This will shutdown DTSS$CLERK. You may then change the F                    system time as usual. To restart the DTSS software,                    types  .                    $ @SYS$STARTUP:DTSS$STARTUP  E                    You will need a number of privileges to ussue this G                    command, and you must also be granted the NET$MANAGEC=                    identifer to shutdown and to restart DTSS.   H                    If you wish to "permanently" disable DTSS on a systemF                    running DECnet-Plus, the above NCL sequence must beF                    performed each time the system is bootstrapped. (OnI                    DECnet-Plus V7.3 and later, you can define the logicalfJ                    name NET$DISABLE_DTSS to disable the DTSS startup. ThisH                    logical name must be defined in the command procedureG                    SYLOGICALS.COM, as this logical name must be present G                    and defined sufficiently early in the OpenVMS systeme:                    bootstrap sequence for it to function.)  I                    If DTSS is running and no time servers are configured,_C                    you can (and will) see the following messages atT%                    regular intervals:   K                    %%%%%%%%%%%  OPCOM   2-SEP-1999 19:41:20.29  %%%%%%%%%%% 5                    Message from user SYSTEM on UNHEDIoQ                    Event: Too Few Servers Detected from: Node LOCAL:.mynode DTSS, @                            at: 1999-09-02-19:41:20.296-04:00Iinf-                            Number Detected=0, ,                            Number Required=1J                            eventUid   5FA70F4F-616E-11D3-A80E-08002BBEDB0FJ                            entityUid  DE9E97DE-6135-11D3-8004-AA000400BD1BJ                            streamUid  D6513A46-6135-11D3-8003-AA000400BD1B  J                    You can either configure the appropriate number of timeI                    servers, or you can disable DTSS, or you can ignore it G                    and (if OPCOM is set to write to the log via via theUG                    logical names in SYLOGICALS.COM/SYLOGICALS.TEMPLATE)y4                    clean out OPERATOR.LOG regularly.  J                                                                       4-19 a  (          '                    Time and Timekeeping         C                    You can also simply disable the display of theseX                    messages:  '                    $ run sys$system:nclhV                    block event dispatcher outbound stream local_stream global filter -?                        ((Node, DTSS), Too Few Servers Detected)t  F                    If you wish to disable the automatic TDF adjustmentJ                    for daylight savings time (on OpenVMS versions prior to2                    V7.3), you can use the command:  '                    $ run sys$system:ncl 8                    set dtss automatic TDF change = false  J                    or alternatively, you can set the local timezone to oneG                    that does not include the automatic daylight savingsa$                    time change-over.  D                    OpenVMS V7.3 and later simplify time and timezone                    management.                                                                    4-20  a                       J                    _______________________________________________________  0           5        System Management Information      D           __________________________________________________________*           5.1  What is an installed image?  B                    The term "install" has two distinct meanings inH                    OpenVMS. The first relates to "installing a product",I                    which is done with either the SYS$UPDATE:VMSINSTAL.COM ?                    command procedure or the POLYCENTER Software E                    Installation (PCSI) utility (PRODUCT command). The C                    second meaning relates to the use of the INSTALL ;                    utility, which is what concerns us here.   E                    The INSTALL utility is used to identify to OpenVMS D                    a specific copy of an image, either executable orG                    shareable, which is to be given some set of enhanced B                    properties. For example, when you issue the SETF                    PASSWORD command, the image SYS$SYSTEM:SETP0.EXE isG                    run. That image needs to have elevated privileges top(                    perform its function.  G                    The other important attribute is /SHARED. This means I                    that shareable parts of the image (typically read-only J                    code and data) are loaded into memory only once and areH                    shared among all users on a system. Executable imagesH                    can be installed /SHARED as well as shareable libraryH                    images. (The term "shareable" has dual meanings here,G                    too. See the OpenVMS Programming Concepts Manual for $                    further details.)  H                    It's important to note that there is no such thing asF                    "installing a shareable image with privileges". TheI                    INSTALL utility will let you do it, but the privilegesiJ                    you specify will be ignored. To have a callable routineI                    run with enhanced privileges that are not available to_I                    its caller, you must construct your routines as "user-SE                    written system services" and install the shareablerE                    image with the /PROTECT qualifier. See the OpenVMSrC                    Programming Concepts Manual for more information B                    on user-written system services. Note also thatC                    in many cases the need to grant privileges to anh  J                                                                        5-1 e  t          0                    System Management Information        G                    image can be replaced with the use of the "ProtectediI                    Subsystems" feature that grants a rights identifier touI                    an image. See the OpenVMS Guide to System Security for 7                    information on Protected Subsystems.   D           __________________________________________________________7           5.2  Are there any known viruses for OpenVMS?(  J                    Viruses are very common on PCs because the PC operatingH                    systems such as MS-DOS and MacOS do not implement anyD                    sort of scheme to protect the operating system orF                    the file system against hostile action by programs.B                    On these operating systems, any running programE                    can subvert the operating system and take over the I                    hardware, at which point it can do anything it wishes,lI                    including hiding copies of itself in other programs org&                    in the file system.  G                    This is unlikely on OpenVMS, Unix, and MVS for three A                    reasons. First, the operating system runs in aoF                    privileged mode in memory that is protected againstH                    modification by normal user programs. Any old programJ                    cannot take over the hardware as it can on PC operatingF                    systems. Secondly, OpenVMS, Unix, and MVS have fileD                    systems that can be set up so that non-privilegedC                    programs cannot modify system programs and fileshF                    on disk. Both of these protection schemes mean thatI                    traditional PC virus schemes don't work on these OSes.cI                    Third, typical applications and configurations tend totJ                    prevent the uncontrolled execution of untrusted code as8                    part of email messages or web access.  F                    It is possible for OpenVMS, etc., to be infected byJ                    viruses, but to do so, the program containing the virusE                    must be run from a user account that has amplified,E                    privileges. As long as the system administrator isrF                    careful that only trusted applications are run fromH                    such accounts (and this is generally the case), there-                    is no danger from viruses.t  J                    To protect against viruses and other attempts at systemE                    interference or misuse, follow the recommendations E                    in the "OpenVMS Guide to System Security". You maytI                    also want to consider optional software products which E                    can monitor your system for intrusion or infectioni                      5-2 _  _          0                    System Management Information        D                    attempts. Computer Associates (CA) offers various)                    products in this area.a  H                    Rocksoft offers the Veracity data integrity tool (for9                    info, send mail to demo@rocksoft.com).   D           __________________________________________________________8           5.3  How do I mount an ISO-9660 CD on OpenVMS?  H                    ISO-9660 support was added in the following releases:  &                    o  OpenVMS VAX V6.0  &                    o  OpenVMS AXP V1.5  H                    An add-on ISO-9960 kit was also available for OpenVMSH                    VAX V5.5, V5.5-1, V5.5-2, and V5.5-2H4. This requiresH                    the installation of the F11CD kit from the InfoServerF                    CD, from the Consolidated Distribution CD under theF                    InfoServer area, Customer Support Center kit CSCPATF                    #1071012, or the F11CD ECO kit. (Upgrades to V6 and3                    later are strongly recommended.)t  I                    By default, OpenVMS senses the specific type of media.(G                    If you are working with dual-format media-media thatNG                    uses both the ODS-2 and ISO-9660 formats on the sameaG                    CD-ROM-then MOUNT will first detect and then default_H                    to the ODS-2 format. If you wish to override this andE                    explicitly mount the media using ISO-9660, use the                     command:d  L                    $ MOUNT/MEDIA_FORMAT=CDROM  device-name[:] [volume-label]  D                    In most circumstances, you will not need nor will@                    you want to include an explicit /MEDIA_FORMATJ                    specification. For further information, please refer toJ                    the OpenVMS MOUNT Utility Manual. Particularly note theI                    information on the MOUNT /MEDIA_FORMAT and /UNDEFINED_M"                    FAT qualifiers.  D                    The MOUNT /UNDEFINED_FAT qualifier is of interestC                    because ISO-9660 media can be mastered on a wideEC                    variety of operating system platforms, and thesenE                    platforms do not necessarily support the semanticsuI                    needed for files containing predefined record formats. G                    The /UNDEFINED_FAT allows you to specify the defaulto  J                                                                        5-3    n          0                    System Management Information        G                    attributes for files accessed from volumes using the #                    ISO-9660 format.   >                    An example which works for most CD-ROMs is:  V                    $ MOUNT/MEDIA_FORMAT=CDROM/UNDEFINED_FAT=STREAM:2048 DUA0: FREEWARE  E                    This particular MOUNT command forces access to theeH                    CD-ROM media using the ISO-9660 volume structure, andG                    the use of the MOUNT /UNDEFINED_FAT qualifier causescG                    any file whose file attributes are "undefined" to bedJ                    returned with "stream" attributes with a maximum record                    length 2048.t  B                    On OpenVMS, the ISO-9660 format is (internally)G                    considered to be the ODS-3 file structure, while the H                    High Sierra extensions to the standard are consideredA                    to be the ODS-4 file structure. The Rock Ridge E                    extensions are not currently available on OpenVMS.   F                    For details on ODS-1 and ODS-2 file specifications,E                    see Kirby McCoy's VMS File System Internals Manual F                    (published by Digital Press, but potentially out of#                    print), and see:   B                    o  http://pdp-11.trailing-edge.com/www/ods1.txt  M                    o  http://www.openvms.compaq.com/freeware/freeware50/ods2/P  D           __________________________________________________________;           5.4  How do I extract the contents of a PCSI kit?   J                    A growing number of OpenVMS products are being providedH                    in PCSI (POLYCENTER Software Installation) kits whichI                    are installed using the PRODUCT INSTALL command. TheserH                    are alternatives to or replacement for VMSINSTAL kitsG                    which were BACKUP savesets. PCSI kits are not BACKUP I                    savesets and are structured differently from VMSINSTALh                    kits.  C                    If you want to extract product files from a PCSIoG                    kit, create a directory into which the kit should ben:                    expanded and use the following command:  G                    $ PRODUCT COPY prodname /SOURCE=[where-the-kit-is] -uF                        /DEST=[destination-directory] /FORMAT=REFERENCE                      5-4 t             0                    System Management Information        B                    A PCSI kit file has a file specification of the"                    following form:  6                    DEC-VAXVMS-FORTRAN-V0603-141-1.PCSI  E                    In this example, "FORTRAN" is the "prodname". PCSI C                    will expand the kit files into the directory you G                    specify and subdirectories beneath such as [SYSEXE],.F                    [SYSLIB], etc., reflecting the eventual destinationC                    of files found there. Most of the actual product F                    files (images, etc.) will be in the subdirectories.E                    In the top-level directory will be a file with the J                    file type PCSI$DESCRIPTION that specifies where variousH                    files should go. For more details, see the POLYCENTERG                    Software Installation Developer's Guide for OpenVMS, I                    which can be found in the OpenVMS documentation on the <                    Consolidated Online Documentation CD-ROM.  D           __________________________________________________________B           5.5  I've forgotten the SYSTEM password - what can I do?  J                    If you need to break into an OpenVMS system because youG                    do not have access to any privileged passwords, such H                    as the password to the SYSTEM username, you will needF                    physical access to the system console, and you willH                    need to perform a conversational reboot. Here are the                    steps:t  G                    1  Halt the system. Exactly how this is done depends_D                       on the specific system model: Depending on theI                       model, this can involve pressing the <HALT> button,rG                       entering <CTRL/P> on the console, or pressing the 1                       <BREAK> key on the console.N  E                    2  At the console prompt, use a console command toED                       boot into the SYSBOOT utility. (SYSBOOT allowsG                       conversational changes to system parameters.) TherG                       syntax for the conversational bootstrap varies byaG                       system model-this typically involves specifying a:-                       flag of 1, for example:v  E                       On VAX, use one of the following three commands/E                       depending on the particular model of VAX system-                       involved:-  J                                                                        5-5 m  /          0                    System Management Information                               B/R5:1                       B/1                        @GENBOOh                         On Alpha:-  "                       b -flags 0,1  E                       If your system has a non-zero system root (suchVG                       as root SYSE, shown here), you will have to use al<                       console command such as the following:                         On VAX:                           B/E0000001#                       B/R5:E0000001 C                       @<console media procedure name varies widely>                          On Alpha:s  "                       b -flags e,1  E                       If your system has a hardware password (variousg>                       systems support a password that preventsC                       unauthorized access to the console), you will H                       need to know theis password and will need to enterC                       it using the LOGIN command at the console. IftD                       you get an "Inv Cmd" error trying to perform aG                       conversational bootstrap, and you do not have themE                       hardware console password for the console LOGIN.F                       command, you are stuck-you will need to call forE                       hardware service in order to reset the hardware G                       console password. The syntax used for the console 0                       password mechanism varies.  F                    3  Once at the SYSBOOT prompt, request that OpenVMSH                       read the system startup commands directly from theE                       system console, that the window system (if any)sG                       not be started, and that OpenVMS not record thesedH                       particular parameter changes for subsequent system                       reboots:  '                       SET/STARTUP OPA0: )                       SET WINDOW_SYSTEM 0 *                       SET WRITESYSPARAMS 0                       CONTINUE                      5-6               0                    System Management Information        G                    4  At the $ prompt, the system will now be accepting J                       startup commands directly from the console. Type the1                       following two DCL commands:a                         $ SPAWNo+                       $ @SYS$SYSTEM:STARTUP   I                       The result of these two commands will be the normal G                       system startup, but you will be left logged in on G                       the console, running under a privileged username. H                       Without the use of the SPAWN command, you would be<                       logged out when the startup completes.  F                       If necessary, you can skip the invocation of theH                       system startup temporarily, and perform tasks suchJ                       as egistering license PAKs or various other "single-3                       user" maintenance operations.   D                    5  Use the following commands to reset the SYSTEM                       password:D  Q                       $ SET DEFAULT SYS$SYSTEM:  ! or wherever SYSUAF.DAT resides 0                       $ RUN SYS$SYSTEM:AUTHORIZE9                       MODIFY SYSTEM /PASSWORD=newpassword                        EXIT  H                       These steps will change the SYSTEM password to the?                       specified new newpassword password value.t  G                       Reboot the system normally-the SYSTEM password isA5                       now set to the specified value.V  >                    Some people will suggest a method using theF                    UAFALTERNATE SYSGEN parameter. This approach is notC                    always reliable and is not recommended, as thereiE                    can easily be an alternate user authorization file ,                    configured on the system.  C                    For further information on emergency startup ands@                    shutdown, as well as for the official OpenVMSJ                    documentation on how to change the SYSTEM password fromF                    the console in an emergency, please see the OpenVMSG                    System Manager's Manual in the OpenVMS documentation                     set.a  J                                                                        5-7 .  -          0                    System Management Information        J                    You can also use the conversational bootstrap techniqueJ                    shown above (the steps through Step 3) to alter variousJ                    system parameters. At the SYSBOOT prompt, you can enter)                    new parameters values:   %                    SHOW MAXPROCESSCNTv                    SET . 64                     CONTINUEi  D                    The "." is a shorthand notation used for the last&                    parameter examined.  D           __________________________________________________________B           5.6  How do I change the node name of an OpenVMS System?  B                    The first step is to get a BACKUP of the systemE                    disk before making any changes-use the system disk H                    backup procedures as documented in the OpenVMS SystemG                    Management Manual, making sure to use the procedures @                    and commands appropriate for the system disk.  H                    Changing the node name involves a number of steps-theJ                    node name tends to be imbedded in a number of different0                    data files around the system.  G                    o  Update the SCSNODE in MODPARAMS.DAT, and then run D                       AUTOGEN as far as the SETPARAMS phase. (Do not"                       reboot yet.)  D                    o  Modify the DECnet node name. (NETCONFIG is theD                       DECnet Phase IV tool, and NET$CONFIGURE is the(                       DECnet-Plus tool.)  H                    o  Modify the IP node name. (The TCP/IP Services toolI                       is UCX$CONFIG prior to V5.0, and is TCPIP$CONFIG inn/                       V5.0 and later releases.)   H                    o  Modify the host node name on the various queues inF                       the queue database. (each queue has a host name,I                       and it defaults to the SCS node name of the queue'stI                       host system. See the command INIT/QUEUE/ON=node for #                       information.)   C                    o  Modify the node name saved in any applicationcI                       databases, or any local node-conditional operationsgG                       present in the site-specific system startup, etc. H                       (SEARCH for the node name, specifying all types of                       files.)                       5-8 $  _          0                    System Management Information        I                    o  Use the AUTHORIZE utility command RENAME/IDENTIFIERDC                       to rename the SYS$NODE_oldnodename rightslistSD                       identifier to match the new node name. (Do notE                       change the binary value of this identifier, andl4                       do not delete the identifier.)  F                       If you have erroneously deleted or duplicate theG                       identifier, you can locate existing references tonH                       the binary identifier value using the Freeware DFUG                       package, and specifically the commands SEARCH/ACEII                       and /OWNER. You must (re)create the correctly-namedEE                       identifier using the binary value that is oftenFG                       stored in various Access Control List Entry (ACE)$H                       structures and object owner fields associated withF                       files and objects present in the OpenVMS system.  G                    o  Reset any license PAKs that are restricted to theL9                       old node name to the new node name.   J                    o  If the node name is part of a disk volume label, see#                       Section 5.12.Y  F                    o  Reboot the node or-if in a VMScluster-reboot theG                       whole VMScluster. (This tends to catch any errors #                       immediately.)   H                    There are likely a few other areas where the nodename"                    will be stored.  F                    If the system is configured in a VMScluster and youG                    change either the SCSNODE or the SCSSYSTEMID-but notRF                    both values-then you will have to reboot the entireD                    VMScluster. (The VMScluster remembers the mappingC                    between these two values, and will assume that a D                    configuration problem has occured if a mismatchedE                    pair appears, and will refuse to let a node with ap8                    mismatched pair join the VMScluster.)  G                    To calculate the correct SCSSYSTEMID value, multiplyaC                    the DECnet Phase IV area number by 1024, and add D                    the DECnet Phase IV node number. For example, theI                    SCSSYSTEMID value for a DECnet node with address 19.22 7                    is 19478. ((19 * 1024) + 22 = 19478)   J                                                                        5-9    s          0                    System Management Information        E                    This may well have missed one or two configurationrI                    tools (or more!) that are needed at your site-the nodeiJ                    name tends to get stored all over the place, in layered5                    products, and in local software...   >                    Also see Section 15.6.3 and Section 15.6.4.  D           __________________________________________________________C           5.7  Why doesn't OpenVMS see the new memory I just added?   C           When adding memory to an OpenVMS system, one should check B           for an existing definition of the PHYSICALPAGES (OpenVMSB           VAX) or PHYSICAL_MEMORY (OpenVMS Alpha) parameter in theH           SYS$SYSTEM:MODPARAMS.DAT parameter database, use a text editorD           to reset the value in the file to the new correct value as;           required, and then perform the following command:e@                    $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT FEEDBACK  A                    This AUTOGEN command will reset various system1F                    parameters based on recent system usage (FEEDBACK),D                    and it will reset the value for the PHYSICALPAGESF                    parameter to the new value. It will also reboot the"                    OpenVMS system.  H                    PHYSICALPAGES and PHYSICAL_MEMORY can also be used toH                    deliberately lower the amount of memory available forF                    use by OpenVMS. This ability can be useful in a fewH                    specific circumstances, such as testing the behaviourC                    of an application in a system environment with a H                    particular (lower) amount of system memory available.  I                    PHYSICALPAGES and PHYSICAL_MEMORY can be set to -1 (onUJ                    OpenVMS Alpha) or (better and simpler) the entry can beH                    removed from the MODPARAMS.DAT file, to indicate that7                    all available memory should be used.l  D           __________________________________________________________C           5.8  How do I change the text in a user's UIC identifier?_  <                    The text translations of the numeric UserE                    Identification Code (UIC) are based on identifiers F                    present in the OpenVMS rightslist. Documentation onH                    this area is included in the _Guide to OpenVMS System$                    Security_ manual.                      5-10m o  o          0                    System Management Information        E                    To control the identifiers shown for a user's UIC,aG                    you use AUTHORIZE. Each user has an associated groupnJ                    identifier, and an identifier specific to the user. And6                    each user should have a unique UIC.  G                    To alter the text of a user or group identifier, useW$                    commands such as:  -                    $ RUN SYS$SYSTEM:AUTHORIZEc:                    UAF> rename/ident oldgroupid newgroupid9                    UAF> rename/ident olduserid  newuserid   H                    If you should find yourself missing an identifier forH                    a particular user, you can add one for the user's UIC+                    using a command such as:   B                    UAF> add/ident/value=uic=[group,user] newuserid  D                    The UIC user identifier text is assigned when theH                    username is created, and is the text of the username.F                    The UIC group group identifier is assigned when theF                    first username is created in the UIC group, and theF                    text is based on the account name specified for theE                    first user created in the group. The value of this,H                    identifier is [groupnumber, 177777]. To add a missing@                    group identifier, use an asterisk as follows:  @                    UAF> add/ident/value=uic=[group,*] newgroupid  I                    You may find cases where an identifier is missing frommF                    time to time, as there are cases where the creationE                    of a UIC group name identifier might conflict witheC                    an existing username, or a user identifier might/I                    conflict with an existing group identifier. When these I                    conflicts arise, the AUTHORIZE utility will not create H                    the conflicting group and/or user identifier when the'                    username is created.f  I                    You can can add and remove user-specified identifiers, C                    but you should avoid changing the numeric values G                    associated with any existing identifiers. You should F                    also avoid reusing UICs or identifiers when you addG                    new users, as any existing identifiers that might behJ                    present on objects in the system from the old user willH                    grant the same access to the new user. Please see the/                    security manual for details.   J                                                                       5-11               0                    System Management Information      D           __________________________________________________________:           5.9__What_are_the_OpenVMS_version upgrade paths?  8           5.9.1  OpenVMS Alpha Upgrade (or Update) Paths                      From V1.0,t/                        you can upgrade to V1.5.s*                    From V1.5, or V1.5-1H1,/                        you can upgrade to V6.1.                     From V6.1,V/                        you can upgrade to V6.2. &                    From V6.1, or V6.2,/                        you can upgrade to V7.0.a<                    From V6.1, V6.2, V6.2-1H(1,2,3), or V7.0,/                        you can upgrade to V7.1.                     From V6.2,hI                        you can update to V6.2-1H1, V6.2-1H2, or V6.2-1H3.tJ                    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, to 7.3A                    From V7.1, one can update to V7.1-1H(1,2), ...o*                        to V7.2-1H1, to 7.3C                    From V7.3, V7.2-2, V7.2-1H1, V7.2-1, and V7.1-2, /                        you can update to V7.3-1S  G                    Some typical OpenVMS Alpha upgrade (or update) pathst                    are:c                                                      5-12                0                    System Management Information        I                    V1.0 -> V1.5 -> V6.1 -> (V6.2, V7.0, V7.1, V7.2, V7.3) E                    V1.5-1H1 -> V6.1 -> (V6.2, V7.0, V7.1, V7.2, V7.3) #                    V6.2 -> V6.2-1H3o!                    V6.2 -> V7.2-1D                    V6.2 -> V7.3n)                    V6.2-1H(1,2,3) -> V7.1m+                    V6.2-1H(1,2,3) -> V7.2-1p!                    V7.1 -> V7.1-2n!                    V7.1 -> V7.2-1p)                    V7.1-1H(1,2) -> V7.1-2,)                    V7.1-1H(1,2) -> V7.2-1 #                    V7.1-2 -> V7.3-1l#                    V7.2 -> V7.2-1H1 )                    V7.2 -> V7.3 -> V7.3-1u#                    V7.2-1 -> V7.3-1S!                    V7.2-2 -> V7.3 !                    V7.3 -> V7.3-1u#                    V7.2-2 -> V7.3-1s  H                    Note that OpenVMS Alpha V7.0 does not include supportH                    for hardware and/or configurations first supported inJ                    OpenVMS Alpha V6.2-1H1, V6.2-1H2, or V6.2-1H3; one must/                    upgrade to OpenVMS VAX V7.1.   C                    One cannot update directly to a V6.2-1Hx Limited G                    Hardware Release (LHR) from any release prior to theuD                    baseline V6.2 release. The same prohibition holdsC                    for performing updates directly to V7.1-1Hx from3G                    any release prior to V7.1-this is not supported, and1F                    does not produce the expected results. The LHR kitsG                    can, however, be directly booted and can be directlyeI                    installed, without regard to any operating system thati7                    might be present on the target disk.m  D                    OpenVMS Alpha updates for LHRs (through V7.1-1Hx)E                    require the use of VMSINSTAL for the update. These J                    LHR releases use PCSI for the installation, but not forI                    the update. Non-LHR releases use PCSI for installs andd                    upgrades.  C                    OpenVMS Alpha V7.1-2 and later use PCSI for LHRs G                    and for OpenVMS upgrades and for all OpenVMS ECO kitrI                    installations. VMSINSTAL OpenVMS ECO kits are not used F                    on OpenVMS Alpha V7.1-2 and later. Prior to V7.1-2,A                    VMSINSTAL-based ECO kits are used for OpenVMS.   J                                                                       5-13 n  s          0                    System Management Information      '           _____________________________l2           5.9.2  OpenVMS VAX Release Upgrade Paths  *                    From V5.0 through V5.4-/           3 inclusive, one can upgrade to V5.5.o.                    From V5.5, V5.5-1, or V5.5-)           2HW, one can upgrade to V5.5-2. I                    From V5.5, V5.5-1, or V5.5-2, one can upgrade to V6.0. %                    From V5.5-2, V5.5- 0           2H4, or V6.0, one can upgrade to V6.1.?                    From V6.0, or V6.1, one can upgrade to V6.2.e?                    From V6.1, or V6.2, one can upgrade to V7.0._E                    From V6.1, V6.2, or V7.0, one can upgrade to V7.1. R                    From V6.1, one can upgrade to V7.3 (with VAXBACK ECO for V6.1).  >                    Some typical OpenVMS VAX upgrade paths are:  E                    V5.x -> V5.5 -> V6.0 -> V6.2 -> (V7.1, V7.2, V7.3) %                    V5.5-2HW -> V5.5-2OG                    V5.5-2, or V5.5-2H4 -> V6.1 -> (V6.2, V7.0, or V7.1)C@                    V6.1 -> V6.1 with VAXBACK ECO -> (V7.2, V7.3)                    V6.2 -> V7.2                     V6.2 -> V7.3c  J                    Note that OpenVMS VAX V6.0 does not include support forH                    hardware and/or configurations first added in OpenVMSF                    VAX V5.5-2H4, one must upgrade to OpenVMS VAX V6.1.  J                    Note that OpenVMS VAX V5.5-2HW is a pre-release versionI                    of V5.5-2. Any system running it should be upgraded to $                    V5.5-2, or later.  H                    If you attempt a direct upgrade from OpenVMS VAX V6.1D                    to V7.2 or later without having first applied theH                    VAXBACK ECO kit to your V6.1 system, you will receive$                    an error message:  G                    %BACKUP-E-INVRECTYP, invalid record type in save set   C                    and the upgrade will fail. Acquire and apply thetI                    VAXBACK ECO kit for OpenVMS VAX V6.1. OpenVMS VAX V6.2 H                    and later do not require an application of an ECO for0                    an upgrade to V7.2 and later.                        5-14                0                    System Management Information      '           _____________________________b6           5.9.3  OpenVMS Cluster Rolling Upgrade Paths  J                    Rolling Upgrades require multiple system disks. RollingJ                    upgrades permit the OpenVMS Cluster to remain availableG                    while individual systems are being upgraded to a newc#                    OpenVMS release.e  D                    OpenVMS Cluster rolling upgrades for both OpenVMSF                    VAX and OpenVMS Alpha may (will) have different, orI                    additional upgrade requirements, and have requirementsmD                    around which versions of OpenVMS can coexist in a<                    OpenVMS Cluster than what is listed here.  J                    See the OpenVMS Upgrade and Installation Manual for theG                    particular release, and the OpenVMS Software ProductrC                    Descriptions for OpenVMS and for OpenVMS Cluster                     software:  5                    o  http://www.compaq.com/info/spd/iD                       OpenVMS typically uses SPD 25.01.xx and/or SPD                       41.87.xx.i  F                    for further details on the rolling upgrade, and forC                    support information. The documentation for oldernE                    releases of OpenVMS VAX includes various platform- F                    specific manuals, manuals that include instructionsG                    that are specific to installing and upgrading on thee                    platform.  '           _____________________________s@           5.9.4  OpenVMS Product Version and Support Information  E                    For information on Prior Version Support (PVS) andsC                    Mature Product Support (including information on D                    support end dates for OpenVMS and various layered)                    products), please see:   A                    o  http://www.compaq.com/services/software/ss_l!                       mature.htmle  H                    o  http://www.compaq.com/services/software/ss_pvs_se_                       amap.html   I                    o  http://www.compaq.com/services/software/ss_mps_pvs_s                       eur.html  J                                                                       5-15               0                    System Management Information        C                    For information on supported versions of layered A                    products, and minimum required layered product !                    versions, see:   P                    o  http://www.openvms.compaq.com/openvms/os/swroll/index.html  E                    For information on the release history of OpenVMS,cE                    including information on the code names of variousc3                    releases and the major features:f  G                    o  http://www.openvms.compaq.com/openvms/os/openvms-n*                       release-history.html  G                    Additional release history information, as well as a H                    variety of other trivia, is available in the VAX 20th$                    anniversary book:  L                    o  http://www.openvms.compaq.com/openvms/20th/vmsbook.pdf  '           _____________________________(*           5.9.5  OpenVMS Alpha Terminology  J                    The following terms apply to OpenVMS Alpha upgrades and!                    installations.                       o  UpdateH                       Typically used for Limited Hardware Releases (LHR)H                       releases. Performed via VMSINSTAL. Applies only toI                       the OpenVMS release that the LHR is based on, or totH                       an intermediate LHR. (eg: V7.1-1H2 applies only toG                       V7.1-1H1 and to V7.1, not to any other releases.) E                       LHRs within a series are cumulative, containing I                       all files and features of previous LHRs in the sames                       series.o                      o  UpgradesC                       Performed via PCSI. Upgrades can typically be_J                       applied to a release-specific (and documented) range0                       of prior OpenVMS releases.                      o  InstallrB                       Performed via PCSI. With an installation, noI                       existing version of the operating system is assumedlE                       present, nor are any files from any copy of theaJ                       operating system might be present preserved, and theJ                       entire contents of the target disk are destroyed via,                       a disk initialization.                      5-16t n             0                    System Management Information                            o  preserveA                       Performed via PCSI. Otherwise similar to anl>                       installation, this option skips the diskE                       reinitialization. User files on the target disk H                       are preserved. Any existing operating system files7                       on the target disk are clobbered._                      o  LHRDH                       Limited Hardware Release. LHRs are specific to andJ                       are targeted at new hardware configurations, and areI                       not shipped to customers with support contracts. At]J                       least one LHR kit must be specifically acquired whenG                       purchasing new hardware, new hardware that is not H                       (yet) supported by any mainline (non-LHR) release.E                       LHRs have an "H" in the OpenVMS version string, 6                       indicating a "Hardware" release.  A           For minimum OpenVMS versions for various platforms, see            Section 2.11.A  D           __________________________________________________________J           5.10  Why do I have a negative number in the pagefile reservable                 pages?  C                    Seeing a negative number in the reservable pages H                    portion of the SHOW MEMORY/FULL command can be normalF                    and expected, and is (even) documented behaviour. AF                    pagefile with a negative number of reservable pagesI                    is overcommitted, which is generally goodness assuming I                    that every process with reserved pages does not try tohH                    occupy all of the reserved pagefile space at the same                    time.  E                    To understand how the pagefile reservation processEJ                    works, think about how a traditional bank operates whenI                    accepting customer deposits and making loans. It's thelI                    same idea with the pagefile space. There is less moneyqJ                    in the bank vault than the total deposits, because muchF                    of the money has been loaned out to other customersG                    of the bank. And the behaviour parallels that of the I                    pagefile down to the problems that a "run on the bank"eG                    can cause for banking customers. (Though there is noiC                    deposit insurance available for pagefile users.)   J                                                                       5-17 o  u          0                    System Management Information        D                    If all of the running applications try to use theJ                    reserved space, the system manager will need to enlargeH                    the pagefile or add one or more additional pagefules.  >                    To determine if the pagefile is excessivelyD                    overcommitted, watch for "double overcommitment"-F                    when the reservable space approaches the negatationB                    of the available total space-and watch that theG                    total amount of free space available in the pagefileeJ                    remains adequate. If either of these situations arises,;                    additional pagefile storage is required.T  H                    Additional pagefile information: Additional pagefilesF                    can typically be created and connected on a runningJ                    OpenVMS system. New processes and new applications willJ                    tend to use the new pagefile, and existing applicationsH                    can be restarted to migrate out of the more congestedI                    pagefiles. Pagefiles are generally named PAGEFILE.SYS, E                    and multiple pagefiles are generally configured ondG                    separate disk spindles to spread the paging I/O loadtC                    across the available disk storage. When multiple I                    pagefiles are present on recent OpenVMS versions, each I                    pagefile file should be configured to be approximately >                    the same total size as the other pagefiles.  D                    For additional information on pagefile operationsB                    and related commands, see the system managementD                    and performance management manuals in the OpenVMS%                    documentation set.[  F                    With OpenVMS V7.3 and later, the displays have beenB                    changed and these negative values are no longer                    visible.n  D           __________________________________________________________B           5.11  Do I have to update layered products when updating                 OpenVMS?  G                    The Software Public Rollout Reports for OpenVMS listRE                    the current and future availability of HP softwareSE                    products shipping on the OpenVMS Software ProductsoH                    Library kits (CDROM consolidations) for OpenVMS AlphaI                    and/or OpenVMS VAX. Specifically, the required minimum ;                    versions for product support are listed.                       5-18e t  r          0                    System Management Information        D                    Comprehensive Public Rollout Information, listingJ                    previous product versions as well as currently shippingE                    versions, has been compiled into a separate set ofoF                    reports. The product information is grouped to show,                    Operating System support.  F                    You may or may not be able to use older versions ofH                    local applications, third-party products, and variousH                    HP OpenVMS layered products with more recent versionsF                    of OpenVMS. User-mode code is expected to be upwardG                    compatible. Code executing in a privileged processorcE                    mode-typically either executive or kernel mode-mayOD                    or may not be compatible with more recent OpenVMS                    versions.  C                    These reports are updated regularly. Please see:   P                    o  http://www.openvms.compaq.com/openvms/os/swroll/index.html  D           __________________________________________________________;           5.12  How do I change the volume label of a disk?t  I                    Dismount the disk, and mount it privately. If the disk J                    is mounted by more than one node in an OpenVMS Cluster,G                    dismount it from all other nodes. If this disk is an J                    OpenVMS system disk, shut down all other nodes that are/                    bootstrapped from this disk.   I                    Issue the SET VOLUME/LABEL command, specifying the newa                    label.V  F                    On OpenVMS V6.0 and later, issue the following PCSIG                    command to reset the label information stored within J                    the PCSI database to reflect the new disk volume label:  =                    $ PRODUCT REGISTER VOLUME old-label deviced  I                    Locate any references in the system startup (typically H                    including the disk MOUNT commands) and any DISK$labelB                    references in application files, and change the,                    references appropriately.  B                    If this is a system disk (for the host or for aF                    satellite), also check the DECnet MOP or LANCP bootJ                    database, as well as any references to the disk created*                    by CLUSTER_CONFIG*.COM.  J                                                                       5-19               0                    System Management Information        H                    If Compaq Analyze is in use, check the system startupB                    procedures for the Compaq Analyze tool. CertainG                    versions of Compaq Analyze will record specific disk ?                    volume labels within the startup procedures.e  2                    Remount the disk appropriately.  D           __________________________________________________________4           5.13  How can I set up a shared directory?  G                    To set up a shared directory-where all files createdrD                    in the directory are accessible to the members ofI                    specified group of users-you can use an access controlT0                    list (ACL) and an identifier.  D                    The following also shows how to set up a resourceF                    identifier, which further allows the disk resourcesH                    to be charged to the specified identifier rather thanF                    each individual user. (If you don't want this, thenH                    omit the attributes option on the identifier creationG                    and omit the entry added in the disk quota database.   A                    Add an identifier using the AUTHORIZE utility:h  D                    ADD/IDENTIFER/ATTRIBUTES=RESOURCE groupidentifier  G                    Grant the identifier to each user in the group usingr                    AUTHORIZE:a  <                    GRANT/IDENTIFIER groupidentifier username  I                    If disk quotas are in use, add an entry via SYSMAN for                     each disk:s  W                    DISKQUOTA ADD groupidentifier/PERMQUOTA=pq/OVERDRAFT=od/DEVICE=ddcu:   I                    Set the shared directory to have an ACL similar to theaG                    following using the SET SECURITY (V6.0 and later) or <                    SET ACL (versions prior to V6.0) command:  9                    (DEFAULT_PROTECTION,S:RWED,O:RWED,G,W) `                    (IDENTIFIER=groupidentifier,OPTIONS=DEFAULT,ACCESS=READ+WRITE+EXECUTE+DELETE)P                    (IDENTIFIER=groupidentifier,ACCESS=READ+WRITE+EXECUTE+DELETE)<                    (CREATOR,ACCESS=READ+WRITE+ACCESS+DELETE)  H                    If there are files already resident in the directory,I                    set their protections similarly. (The OPTIONS=DEFAULT,o@                    DEFAULT_PROTECTION, and CREATOR ACEs apply to                     directories.)                      5-20u s             0                    System Management Information        C                    The default protection mask is used to establisheG                    the default file protection mask, this mask does notaJ                    prevent the users holding the specified groupidentifierJ                    from accessing the file(s), as they can access the fileF                    via the explicit identifier granting access that is&                    present in the ACL.  D                    For further information, see the OpenVMS Guide toG                    System Security Manual, specifically the sections on B                    ACLs and identifiers, and resource identifiers.  D           __________________________________________________________@           5.14  Why do I get extra blank pages on my HP Printer?  H                    For information on configuring telnet print symbiont,I                    on device control libraries such as SYSDEVCTL.TLB, and J                    for ways of dealing with the extra blank pages that canG                    arise on various HP printers, please see the OpenVMSvH                    Ask The Wizard area, starting particularly with topic                    (1020):  ;                    o  http://www.openvms.compaq.com/wizard/a  E                    o  http://www.openvms.compaq.com/wizard/wizard.zip_  F                    For additional information, please see Section 3.9.  D                    There are a variety of discussions of this and ofF                    related printing topics in the Ask The Wizard area,/                    in addition to topic (1020).i  )                    Also see Section 5.33.g  D           __________________________________________________________F           5.15  Drivers and Configuration of New Graphics Controllers?  ?                    This section contains information on variousnG                    graphics controllers supported by OpenVMS Alpha, and F                    specifically information on where and how to obtainF                    device drivers for specific early OpenVMS releases-E                    device drivers for controllers are integrated into B                    and shipped with OpenVMS Alpha, but versions ofH                    these device drivers are sometimes made available for5                    specific earlier OpenVMS releases.   J                                                                       5-21    U          0                    System Management Information      '           _____________________________ )           5.15.1  The ELSA GLoria Synergyn  I                    On OpenVMS Alpha V7.1-2, V7.2, and V7.2-1, acquire the F                    appropriate GRAPHICS PCSI kit, and all prerequisite$                    OpenVMS ECO kits:  4                    o  VMS712_GRAPHICS-V0300 or later  3                    o  VMS72_GRAPHICS-V0100 or later   4                    o  VMS712_GRAPHICS-V0300 or later  J                    The ELSA GLoria Synergy is the PBXGK-BB; the PowerStorm                    3D10T.n  H                    On OpenVMS Alpha V7.2-1, the files necessary for thisF                    graphics controller are located in the distribution$                    CD-ROM directory:  ,                    DISK$ALPHA0721:[ELSA.KIT]  A                    Also check for any available (later) ECO kits.o  C                    An earlier kit (ALP4D20T01_071) (for V7.1, V7.1-oF                    1H1, and V7.1-1H2) was once available, but has beenC                    superceded and is not recommended. Use of V7.1-2fF                    or later (and use of one the above GRAPHICS kits as<                    required) is typically the best approach.  F                    OpenVMS V7.2-2 and later mainline releases directly*                    support the controller.  G                    Additional information is available in topics (3419)g9                    and (5448) in the Ask The Wizard area:   ;                    o  http://www.openvms.compaq.com/wizard/   E                    o  http://www.openvms.compaq.com/wizard/wizard.zip   F                    For additional information, please see Section 3.9.  I                    Support for the ELSA GLoria Synergy is integrated into 6                    all current OpenVMS Alpha releases.                      5-22     e          0                    System Management Information      '           _____________________________ 0           5.15.2  PowerStorm 300, PowerStorm 350  @                    The PowerStorm 300 is the PBXGD-AC, while the2                    PowerStorm 350 is the PBXGD-AE.  G                    For support of the PowerStorm 300 and PowerStorm 350cJ                    graphics controllers, acquire and install the following&                    available ECO kits:  ,                    For OpenVMS Alpha V7.1-2:  =                    o  DEC-AXPVMS-VMS712_P350-V0100-4 or latert  A                    o  DEC-AXPVMS-VMS712_GRAPHICS-V0300-4 or laterS  ,                    For OpenVMS Alpha V7.2-1:  =                    o  DEC-AXPVMS-VMS721_P350-V0100-4 or laters  A                    o  DEC-AXPVMS-VMS721_GRAPHICS-V0300-4 or latern  D                    Support for the PowerStorm 300 and PowerStorm 350I                    series graphics controllers is integrated into currenta*                    OpenVMS Alpha releases.  '           _____________________________u2           5.15.3  PowerStorm 3D30, PowerStorm 4D20  F                    PowerStorm 3D30 (PBXGB-AA), PowerStorm 4D20 (PBXGB-H                    CA) information is available in Ask The Wizard topics*                    including topic (2041):  ;                    o  http://www.openvms.compaq.com/wizard/   E                    o  http://www.openvms.compaq.com/wizard/wizard.zip   F                    For additional information, please see Section 3.9.  '           _____________________________i           5.15.4  Radeon 7500T  I                    Install the current GRAPHICS ECO kit for OpenVMS Alpha(I                    V7.2-2 or V7.3-1 for support of the Radeon 7500 seriese                    controller.  F                    Support for this controller (without an ECO kit) isH                    expected to be first integrated into and available in(                    OpenVMS Alpha V7.3-2.  J                                                                       5-23 t  d          0                    System Management Information      D           __________________________________________________________C           5.16  How can I acquire OpenVMS patches, fixes, and ECOs?   G                    You can acquire and download kits containing OpenVMSdH                    fixes (ECOs) for various releases, as well as related,                    support information, via:  8                    o  http://search.service.digital.com/  >                    o  ftp://ftp.support.compaq.com/public/vms/  K                    o  http://ftp.support.compaq.com.au/pub/ecoinfo/ecoinfo/m  =                    o  http://ftp/digital.com.au/cgi-bin/grep/e  -                    o  http://askq.compaq.com/t                      TheH                    http://ftp.support.compaq.com.au/pub/ecoinfo/ecoinfo/J                    URL can be particularly useful, as it includes a searchE                    engine capable of returning the mandatory ECO kits I                    for each release. Also see the information on requiredsG                    ECOs available from the support database, accessibleoH                    via http://askq.compaq.com/. Specifically, search forF                    articles with the words "incorporated" and "need to)                    install" in the title.   F                    You can subscribe to an email notification list at:  D                    o  http://www.support.compaq.com/patches/mailing-                        list.shtml  H                    A quarterly distribution is also available on CD-ROM:  /                    o  QT-3CQAA-C8 OpenVMS AlphaH  -                    o  QT-3CRAA-C8 OpenVMS VAXr  H                    For a list of OpenVMS ECO kits recently released, you                    can use:e  J                    o  http://Eisner.DECUS.org/conferences/OpenVMS-patches_                        new_1.HTML  G                    You can also sign up for ECO kit email notifications H                    (Digest or individual notifications) directly from HP                    at:  F                    o  http://www1.service.digital.com/patches/mailing-                       list.html                       5-24A O  E          0                    System Management Information        E                    Examples and ECO kit installation instructions aresH                    included in the cover letter. For available ECO kits,I                    cover letters and other associated documentation, look                     in:  >                    o  ftp://ftp.support.compaq.com/public/vms/  K                    o  http://ftp.support.compaq.com.au/pub/ecoinfo/ecoinfo/   G                    For additional information, please see Section 5.16.   F                    Do NOT attempt to install a VMSINSTAL-based OpenVMSC                    ECO kit on OpenVMS Alpha V7.1-2 and later. While/E                    VMSINSTAL itself remains available, it is not usedeG                    for OpenVMS Alpha ECO kits starting in OpenVMS AlphaeF                    V7.1-2. OpenVMS Alpha V7.1-2 and later use PCSI for$                    OpenVMS ECO kits.  I                    See Section 5.29 for information on ECO kit checksums.   D           __________________________________________________________9           5.17  How do I move the queue manager database?f  B                    To move the location of the queue database, the?                    SYS$QUEUE_MANAGER.QMAN$QUEUES and SYS$QUEUE_aJ                    MANAGER.QMAN$JOURNAL files, to a disk that is fast(er),J                    has plenty of free space, and that is not heavily used.F                    If the queue database is on a (busy) OpenVMS systemD                    disk, you can and probably should move it off the7                    system disk to another disk spindle.r  .                    To move the queue database:  H                    1  Checkpoint the journal file. This reduces the fileJ                       size to the in-memory database size. This will cause&                       the noted delay.  2                       $ RUN SYS$SYSTEM:JBC$COMMAND+                       JBC$COMMAND> DIAG 0 7s  ,                    2  Stop the queue manager  2                       $ STOP/QUEUE/MANAGER/CLUSTER  J                    3  Backup the .QMAN$QUEUES and .QMAN$JOURNAL files from6                       the present location for safety.  V                       $ backup SYS$COMMON:[SYSEXE]SYS$QUEUE_MANAGER.QMAN$*  DISK:[DIR]  J                                                                       5-25    a          0                    System Management Information        D                    4  Create a new directory for the queue database.F                       Insure that this disk is accessible to all nodesI                       that can run the queue manager. If the /ON list for_F                       the queue manager is "/ON=(*)", the disk must be;                       available to all nodes in the clusterg  3                       $ CREATE/DIR fast_disk:[qman]t  J                    5  Copy the .QMAN$QUEUES and .QMAN$JOURNAL files to the#                       new directory   Z                       $ copy SYS$COMMON:[SYSEXE]SYS$QUEUE_MANAGER.QMAN$*  fast_disk:[qman]  4                    6  Delete the old queue database.  L                       $ DELETE SYS$COMMON:[SYSEXE]SYS$QUEUE_MANAGER.QMAN$*;*  C                    7  Restart the queue manager pointing to the newe                       location  <                       $ START/QUEUE/MANAGER fast_disk:[qman]  D           __________________________________________________________B           5.18  How do I delete an undeletable/unstoppable (RWAST)                 process?  E                    "Undeleteable" jobs are usually "undeleteable" for G                    a reason-this can track back to insufficient processtH                    quotas, to a kernel-mode error in OpenVMS or a third-A                    party device driver, or to other odd problems.   F                    These undeletable jobs typically become of interestF                    because they are holding onto a particular resourceF                    (eg: tape drive, disk drive, communications widget)C                    that you need to use... If the particular device7E                    supports firmware, ensure that the device firmware7I                    is current - TQK50 controllers are known for this when E                    working with old firmware. (That, and the infamous G                    "MUA4224" firmware bug.) If this device has a driver D                    ECO kit available, acquire and apply it... If theI                    particular relevant host component has an ECO, acquire2                     and apply it.  G                    Useful tools include SDA (to see what might be goingVG                    on) and DECamds (which increase and thus potentially F                    fix quota-related problems). (nb: Applications with>                    quota leaks will obviously not stay fixed.)                      5-26e p  t          0                    System Management Information        J                    If the stuck application is BACKUP, ensure you have theI                    current BACKUP ECO and are directly following the V7.1 J                    or (better) V7.2 or later process quota recommendationsI                    for operator BACKUP accounts. Quota details are in thel3                    OpenVMS System Manager's Manual.   G                    If the firmware and ECO levels are current, the best J                    approach is to take a system crashdump, and pass a copyH                    of the dump file along to whomever is maintaining theH                    device driver for the particular device/widget/driverF                    involved, with any details on how you got into thisB                    situation. (The reboot involved with taking the?                    crashdump will obviously clear the problem.)   I                    There was some kernel-mode code (typically for OpenVMSrF                    VAX) that can reset the device ownership field, butE                    that is rather obviously only an interim solution- D                    the real fix is avoiding the loss of the IRP, theG                    process quota leak, or whatever else is "jamming up"p-                    this particular process...s  D           __________________________________________________________2           5.19  How do I reset the error count(s)?  H                    The system reboot is the only supported approach, butJ                    it is obviously undesirable in various situations-thereE                    is presently no supported mechanism to reset error_=                    counts once the error(s) have been logged.a  E                    As for an unsupported approach-and be aware of the :                    potential for causing a system crash...  G                    To reset the error count, one needs to determine the I                    system address of the error count field. For a device, J                    this is at an offset within the device's UCB structure.I                    On VAX, the field is at an offset symbolically defined D                    as UCB$W_ERRCNT. On Alpha, this field's offset isF                    symbolically defined as UCB$L_ERRCNT. The former isI                    a word in size; the latter is a longword. (Could it be1>                    that Alpha devices are more error prone? ;)  J                    You now need to locate the system address of the UCB$%_F                    ERRCNT field of the device you wish to reset. EnterF                    SDA. In the following, you will see designations inI                    {} separated by a /. The first item in braces is to be   J                                                                       5-27 s  t          0                    System Management Information        H                    used on the VAX and the second item should be used on.                    an Alpha. (ie. {VAX/Alpha})  #                    $ ANALYZE/SYSTEMrE                    SDA>  READ SYS${SYSTEM/LOADABLE_IMAGES}:SYSDEF.STBuY                    SDA>  SHOW DEVICE <ddnc:>    ! device designation of device with errorp6                    SDA>  EVALUATE UCB+UCB${W/L}_ERRCNTL                    Hex = hhhhhhhh   Decimal = -dddddddddd         UCB+offset  D                    Record the hexadecimal value 'hhhhhhhh' returned.  I                    You can now exit from SDA and $ RUN SYS$SHARE:DELTA orp?                    do what I prefer to do, issue the following:c  1                    SDA> SPAWN RUN SYS$SHARE:DELTAk  D                    On both VAX and Alpha, the DELTA debugger will beF                    invoked and will ident- ify itself. On Alpha, thereB                    will be an Alpha instruction decoded. For thoseG                    unfamiliar with DELTA, it does not have a prompt and_J                    only one error message-Eh? (Well, for sake of argument,J                    there might be another error produced on the console if;                    you're not careful-aka. a system crash!)t  =                    If you are on a VAX, enter the command: [Wm  =                    If you are on Alpha, enter the command: [Le  E                    These set the prevailing mode to word and longwordS@                    respectively. Remem- ber the UCB${W/L)_ERRCNT                    differences?o  ,                    Now issue the command 1;M  3                    DELTA will respond with 00000001a  I                    You are now poised to ZAP the error count field. To do I                    so you need to en- ter the system address and view itseG                    contents. The format of the command to do this is ofr                    the form:  !                    IPID:hhhhhhhh/e  J                    For an IPID, use the IPID of the SWAPPER process. It is#                    always: 00010001p  A                    Thus, to ZAP the error count, you would enter:1  %                    00010001:hhhhhhhh/r                      5-28r ,  d          0                    System Management Information        F                    When you enter the / SDA will return the content ofG                    the address hhhhhhhh. This should be the error counttG                    (in hexadecimal) of the device in question. If it is J                    not, you did something wrong and I'd suggest you type aI                    carriage return and then enter the command EXIT to get H                    out of DELTA. Regroup and see where your session went                    awry.  F                    If you entered your address correctly and the errorJ                    count was returned as in the following example, you can                    proceed.p  ]                    00010001:80D9C6C8/0001                          ! output on VAX    1 error   ]                    00010001:80D9C6C8/00000001                      ! output on Alpha  1 error   I                    You can now ZAP the error count by entering a zero and 9                    typing a carriage return. For example:   X                    00010001:80D9C6C8/0001 0<return>           ! output on VAX    1 error  X                    00010001:80D9C6C8/00000001 0<return>       ! output on Alpha  1 error  C                    Now type the command EXIT and a carriage return.   4                    Alternatively, reboot the system.  D           __________________________________________________________I           5.20  How do I find out if the tape drive supports compression?   I                    For various SCSI-based MK-class magnetic tape devices:   E                    $ Devdepend2 = F$GETDVI("$n$MKcxxx:","DEVDEPEND2")o*                    $ Comp_sup = %X00200000*                    $ Comp_ena = %X00400000D                    $ IF (Devdepend2.AND.Comp_sup).EQ.Comp_sup THEN -?                        WRITE SYS$OUTPUT "Compression supported" D                    $ IF (Devdepend2.AND.Comp_ena).EQ.Comp_ena THEN -=                        WRITE SYS$OUTPUT "Compression enabled"   D           __________________________________________________________G           5.21  Can I copy SYSUAF to another version? To VAX? To Alpha?   @                    The format of the SYSUAF.DAT, RIGHTSLIST, andI                    associated files are upward-compatible, and compatibleeF                    across OpenVMS VAX and OpenVMS Alpha systems. (ThisC                    compatibility is a a basic requirement of mixed-iE                    version OpenVMS Cluster configurations and OpenVMS1H                    upgrades-for specific support information, please see  J                                                                       5-29 c  a          0                    System Management Information        H                    the OpenVMS Cluster rolling upgrade and mixed-versionE                    requirements.) That said, it's the contents of theyG                    SYSUAF and RIGHTSLIST files that will make this more)                    interesting.p  G                    The same basic steps necessary for moving RIGHTSLIST F                    and SYSUAF files to another node are rather similarE                    to the steps involved in merging these files in an J                    OpenVMS Cluster-see the appendix of the OpenVMS ClusterI                    documentation for details of merging files. (You might J                    not be merging the contents of two (or more) files, butH                    you are effectively merging the contents of the files7                    into the target system environment.)   "                    Considerations:  H                    o  applications often hold SYSUAF or RIGHTSLIST open,F                       meaning a system reboot is often the best way to)                       activate new files.   F                    o  the meanings of the RESTRICTED and CAPTIVE flagsI                       settings on the UAF entries have changed over time.   J                    o  the new NET$PROXY.DAT file that is initially createdJ                       based on the contents of the NETPROXY.DAT during theE                       OpenVMS VAX V6.1 upgrade and during the OpenVMSoD                       Alpha V6.2 upgrade. This file is maintained in1                       parallel with NETPROXY.DAT.g  J                    o  the RIGHTSLIST identifier values and UIC values thatG                       end up scattered around the target system must be"J                       rationalized with the contents of the new RIGHTSLIST'                       and SYSUAF files.p  G                    The lattermost case-resolving the identifier values- G                    is often the most interesting and difficult part. If I                    you find that an identifier value (or identifier name) F                    from the source RIGHTSLIST collides with that of anE                    identifier existing on the target system, you mustaE                    first determine if the two identifiers perform thenH                    same function. In most cases, they will not. As such,E                    you will have to find and chance all references to F                    the identifier value(s) (or name(s)) to resolve the                    "collision".                       5-30r r             0                    System Management Information        E                    If you encounter a collision, changing both of the B                    identifier binary values (or names) involved inE                    the collision to new and unique values can prevent C                    security problems if you should miss a couple ofoF                    identifiers embedded somewhere on the target systemF                    during the whole conversion process-rather than theD                    wrong alphanumeric value for the identifier beingE                    displayed, you'll simply see the binary format forrE                    the identifier displayed, and no particular accessTE                    will be granted. And any DCL commands or such thatpH                    reference the old alphanumeric name will fail, ratherJ                    than silently (and potentially erroneously) succeeding.  J                    Similar requirements exist for UIC values, as these tooH                    tend to be scattered all over the system environment.G                    Like the binary identifier values, you will find UICoJ                    values associated with disks, ACLs, queues, and various$                    other structures.  G                    For a list of the various files shared in an OpenVMSeC                    Cluster and that can be involved when relocating F                    an environment from one node to another (or mergingH                    environments into an OpenVMS Cluster), please see theH                    SYLOGICALS.TEMPLATE file included in OpenVMS V7.2 and"                    later releases.  G                    Procedures to extract the contents of a (potentially F                    corrupt) queue database are provided on the OpenVMSE                    Freeware (V5) and can be used to combine two queue C                    databases together while shuffling files between )                    OpenVMS Cluster hosts.e  J                    For related discussions of splitting a cluster into twoJ                    or for removing a node from cluster (political divorce,I                    etc), see topics (203), (767), (915) and others in theh'                    Ask The Wizard area:r  ;                    o  http://www.openvms.compaq.com/wizard/   E                    o  http://www.openvms.compaq.com/wizard/wizard.zip   F                    For additional information, please see Section 3.9.    J                                                                       5-31 o             0                    System Management Information      D           __________________________________________________________9           5.22  How do I delete (timeout) idle processes?c  F                    There is no such command integrated within OpenVMS,F                    though there are (optional) timers available withinJ                    certain terminal servers and similar devices, and thereG                    is an integrated time-of-day mechanism that providest?                    control over when a user can access OpenVMS.   E                    As for available tools, there are DECUS, freeware, I                    and third-party tools known variously as "idle process I                    killers" (IPK) or "terminal timeout" programs, as well J                    as various other names. Examples include: Saiga SystemsE                    Hitman, Watchdog, MadGoat Watcher (via the MadGoat H                    site or the OpenVMS Freeware), Kblock, the NetworkingE                    Dynamics tool known as Assassin, and the Zap tool.nI                    Also available is the XLNperformance system managementi,                    utility, from XLNsystems.  A                    A related package (for DECwindows sessions) ise                    xtermlock.o  D                    If the forgetful users are in an application menuG                    environment, the menu can potentially be extended tou+                    provide this capability.   D           __________________________________________________________C           5.23  Do I need a PAK for the DECevent (HP Analyze) tool?   D                    DECevent and HP (Compaq) Analyze are available toH                    customers with support contracts. The PAK is requiredI                    only for the advanced functions of DECevent, the basic-E                    bits-to-text translation of the error log does notVE                    require a license PAK. Ignore the prompt, in othereI                    words. (The PAK should be available to you if you havesH                    a hardware support contract or warrantee, and the PAKE                    enables the use of the advanced error analysis and >                    notification capabilities within DECevent.)  C                    Please see the following website for details ande&                    downloads: Analyze)  =                    o  http://www.compaq.com/support/svctools/h                        5-32     N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faqmN  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.coma   ------------------------------  # Date: Thu, 03 Jul 2003 17:13:08 GMTP2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman); Subject: OpenVMS Frequently Asked Questions (FAQ), Part 4/9c2 Message-ID: <EuZMa.3894$bl3.3439@news.cpqcorp.net>    t          0                    System Management Information      D           __________________________________________________________>           5.24  INITIALIZE ACCVIO and ANSI tape label support?  F                    A change was made (back in 1988) to (as it was thenI                    known) VAX/VMS V5.1-1 that added support for the then-oJ                    new ANSI X3.27-1987 magnetic tape label standard. PriorI                    to the ANSI X3.27-1987 standard, the date field in the H                    ANSI HDR1 record permits dates only as far as the endI                    of Year 1999. With ANSI X3.27-1987, dates through YearoH                    1999 and dates from Years 2000 to 2099 are permitted.  C                    Versions of INIT.EXE and MTAACP.EXE from VAX/VMS J                    releases prior to V5.1-1 will potentially have problemsG                    properly processing ANSI magnetic tapes when Y2K and I                    later dates are involved-the DCL INITIALIZE command is_G                    known to encounter access violation (ACCVIO) errors.   G                    The available solutions include upgrades, or setting H                    the date back. Direct initialization of the tape withG                    the new headers (via $qio) is also clearly possible, J                    though the limitation within the old MTAACP.EXE magtape=                    ACP image is not nearly so easy to bypass.e  D           __________________________________________________________7           5.25  How do I recover from INSVIRMEM errors?   E                    Prior to OpenVMS Alpha V7.0 and on all OpenVMS VAX J                    releases, VIRTUALPAGECNT and PGFLQUOTA limit the amountE                    of virtual address space that is available to each                     process.g  F                    Further limiting the amount of address space is theE                    size of system space (S0 and S1 space). On OpenVMScF                    Alpha versions prior to V7.0 and on all OpenVMS VAXF                    releases, VIRTUALPAGECNT and MAXPROCESSCNT togetherG                    determine the size of the page table data structures D                    that occupy large tracts of system space. When noJ                    system virtual address space is available for the stuffI                    that needs it-this includes the page tables, non-pagedtH                    pool, and various other structures-then the values ofH                    VIRTUALPAGECNT and MAXPROCESSCNT cannot be increased.  G                    In OpenVMS Alpha V7.0 and later, the page table dataTH                    structures have been moved out of S0 and S1 space andJ                    into page table space. In OpenVMS Alpha V7.2 and later,H                    certain large data structures found in non-paged poolH                    (eg: lock management structures) have been moved into  J                                                                       5-33 T  A          0                    System Management Information        G                    64-bit space, thus freeing up room in non-paged poolnH                    and in S0 and S1 space (where non-paged pool resides)E                    while also permitting much larger data structures.e  D           __________________________________________________________J           5.26  How can I prevent a serial terminal line from initiating a                 login?  ;                    In SYSTARTUP_VMS.COM, issue the command:   =                    $ SET TERMINAL/NOTYPEAHEAD/PERMANENT ddcu:h  F                    This will prevent any unsolicited terminal input onE                    ddcu:, and this unsolicited input is what triggersdI                    JOB_CONTROL to start up LOGINOUT on the terminal. Once_E                    LOGINOUT starts up on the serial line, you can seeaH                    interesting behaviour (eg: audits, process creations,H                    etc) as LOGINOUT tries to "chat" with whatever deviceG                    is hooked onto the remote end of the serial terminalt                    line.  D           __________________________________________________________>           5.27  How does PCSI use the image BUILD_IDENT field?  E                    The (undocumented) build ident field in an OpenVMStF                    Alpha image header is 16 bytes long, and is used asH                    a counted string of 0-15 characters (ie, as an .ASCICG                    string, a string with the character count in byte 0)vG                    and was originally introduced to provide information J                    for use by VMSINSTAL patch kits to determine whether an3                    image should be replaced or not.g  J                    Starting with OpenVMS Alpha V7.1-2, OpenVMS EngineeringH                    uses the PCSI utility to package and install ECO kitsE                    for OpenVMS. PCSI uses the generation attribute (a F                    32-bit unsigned integer) specified for files in theF                    product description file (PDF) of a PCSI kit as theC                    basis for performing file conflict detection and I                    resolution. When a product is installed, PCSI modifies H                    the build ident field of Alpha image headers to storeJ                    an encoded form of the generation number. It also looksJ                    at the build ident field of previously installed imagesJ                    to obtain the generation information for those files asI                    input to the file conflict processing algorithm. (Only_6                    images have this field, obviously.)                      5-34h 7  2          0                    System Management Information        H                    PCSI interprets the build ident field of a previously.                    installed image as follows:  F                    o  if the string length is 15, the 5th character isE                       a hyphen, and the last ten characters are a teneH                       digit number with leading zeros, then the last tenJ                       characters are treated as a valid generation number.  H                    o  for V7.1-2 through V7.2-1, inclusive, if the aboveF                       test fails, the information is obtained from the,                       PCSI product database.  H                    o  in releases after V7.2-1 and with current PCSI ECOJ                       kits, if the above test fails, an invalid generationI                       number is treated as 0000000000 so that the ECO kitrH                       will simply replace the image rather than assuming4                       the PCSI database is in error.  D                    So, what will you see in the image identification;                    displayed via the ANALYZE/IMAGE command?t  I                    For an image that has been built as part of an OpenVMS E                    Engineering system build, you will generally see aaH                    build ID string in the format "X6TE-SSB-0000"-X6TE isI                    the build number for the OpenVMS Alpha V7.2-1 release. J                    This id format is used within the OpenVMS system build,H                    and can generally only be seen associated with images=                    that have not yet been processed via PCSI.   F                    During the installation of V7.2-1, PCSI will modifyC                    the image header to have a build ident string of5C                    "X6TE-0050120000". During installation of an ECOrE                    kit containing this image with a generation numbertF                    of 50130052, for example, PCSI would determine thatJ                    50130052 is greater than 50120000, and will replace theH                    existing image on the target disk with the version of5                    the image included in the ECO kit.               J                                                                       5-35 V  0          0                    System Management Information      D           __________________________________________________________H           5.28  How can I tell what software (and version) is installed?  I                    There is unfortunately no consistent nor single way to J                    make this determination-this is one of the reasons that<                    a move to PCSI installations is underway.  F                    On OpenVMS Alpha, you can use VMSINSTAL.HISTORY andG                    PRODUCT SHOW PRODUCT to determine what packages have C                    been installed via the VMSINSTAL and PCSI tools,                      respectively.  I                    To see which OpenVMS Alpha ECO kits have been applied, F                    look in VMSINSTAL.HISTORY on OpenVMS Alpha prior toG                    V7.1-2, and use PRODUCT SHOW PRODUCT/FULL on OpenVMS *                    Alpha V7.1-2 and later.  G                    On OpenVMS VAX, you can use PRODUCT SHOW PRODUCT andiH                    (for software that is installed via VMSINSTAL on V7.33                    and later) in VMSINSTAL.HISTORY..  F                    For products installed on OpenVMS VAX prior to V7.3I                    using VMSINSTAL, there is no reliable way to determine D                    what products have been installed. If the productB                    provides a RELEASE_NOTES file (as many do), youE                    can look for the list of these files via DIRECTORY_H                    SYS$HELP:*.RELEASE_NOTES. Again, this approach is NOTI                    reliable: some kits do not provide release notes, somecG                    system managers will install only the release notes,sF                    some system managers will delete release notes, andF                    release notes for multiple versions can be present.  H                    On most packages, you can generally use ANALYZE/IMAGEB                    on one of the core images, looking at the imageD                    identification area. Some of the product-specific,                    mechanisms available are:  2                    o  DQS DQS$VERSION logical name  "                    o  C CC/VERSION  %                    o  C++ CXX/VERSIONU  7                    o  TCP/IP TCPIP SHOW VERSION command                       5-36l f  t          0                    System Management Information      D           __________________________________________________________C           5.29  What file checksum tools are available for OpenVMS?h  E                    The undocumented DCL command CHECKSUM is the usualcF                    means, and provides a rather simple-minded checksumA                    suitable to detect basic file corruptions. ForaI                    information and an OpenVMS version of the MD5 checksum.                    tool, see:   A                    o  http://www.support.compaq.com/svctools/md5- '                       instructions.html   H                    The OpenVMS Alpha ECO (patch) kit checksums availableH                    at the ECO website are determined using the following(                    DCL command sequence:  5                    $ CHECKSUM kitname.pcsi-dcx_axpexer2                    $ SHOW SYMBOL CHECKSUM$CHECKSUM  H                    See Section 5.16 for information on acquiring OpenVMS$                    ECO (patch) kits.  D           __________________________________________________________C           5.30  What (and where) is the OpenVMS Management Station?   C                    For information and current kits for the OpenVMS I                    Management Station (OMS), a PC-based tool that permits ?                    you to manage an OpenVMS system, please see:   K                    o  http://www.openvms.compaq.com/openvms/products/argus/   D           __________________________________________________________B           5.31  How to determine current disk fragmentation level?  ;                    The HP OpenVMS Disk File Optimizer (DFO).C                    defragmentation package provides a fragmentationoG                    monitoring tool, and a DFO product authorization keyoH                    (PAK) is not required for the fragmentation reporting                    tool:  -                    $ DEFRAG SHOW/VOLUME ddcu:   E                    The DFU tool available on the OpenVMS Freeware can ?                    generate a report on the disk fragmentation:p  $                    DFU> REPORT ddcu:  J                                                                       5-37 t             0                    System Management Information      D           __________________________________________________________H           5.32  SYSBOOT-I-FILENOTLOC, Unable to locate SYS$CPU_ROUTINES?  G                    A message at the OpenVMS Alpha bootstrap such as theE                    following:R  T                    %SYSBOOT-I-FILENOTLOC, Unable to locate SYS$CPU_ROUTINES_1C02.EXEO                    %SYSBOOT-E-LDFAIL, failed to load execlet, status = 00000910   F                    indicates that the particular OpenVMS Alpha releaseG                    does not contain support for the target platform. IniH                    this case, OpenVMS does not recognize Alpha family 1CH                    member 02 as a supported platform. A later version ofH                    OpenVMS might support the platform, or there might beF                    no support on any release. Ensure that you have theH                    most current firmware, and review the minimum version1                    requirements for the platform.   G                    The execlet load failure and other similar bootstrapEI                    status values can often be decoded using either of then(                    following techniques:                      $ exit %x910A5                    %SYSTEM-W-NOSUCHFILE, no such file                     $  )                    $ x = f$message(%x910) "                    $ show symbol x=                      X = "%SYSTEM-W-NOSUCHFILE, no such file"y                    $  -                    Also see Section 14.4.4.1.s  D           __________________________________________________________E           5.33  How can I customize the DCPS device control for a news                 printer?  J                    To customize DCPS for an otherwise unsupported printer,6                    you can try the following sequence:  G                    o  Extract the most closely-associated setup modules ?                       from the existing device control library,MF                       DCPS$DEVCTL.TLB. (For instance, you can probablyA                       extract and use the HP LaserJet 4000 seriesEG                       definitions for the HP LaserJet 4050 series. Each7C                       printer will vary, please consult the printer D                       documentation for specifics and requirements.)                      5-38_ _  _          0                    System Management Information        =                    o  rename each extracted setup module to as$                       corresponding:  )                       LPS$$UNRECOGNIZED_*   J                    o  Insert all of the above-renamed setup modules into aJ                       newly-created device control library specific to the"                       new printer:  -                       $ LIBRARY/TEXT/CREATE -d>                           SYS$COMMON:[SYSLIB]HP4050_DEVCTL.TLB,                           LPS$$UNRECOGNIZED*  G                       The above assumes the filename HP4050_DEVCTL.TLB,)(                       alter as required.  F                    o  Set up your DCPS startup procedures to include a7                       search-list logical name such as:   B                       $ DEFINE/SYSTEM/EXECUTIVE DCPS_HP4050_LIB  -:                           SYS$LIBRARY:HP4050_DEVCTL.TLB, -5                           SYS$LIBRARY:DCPS$DEVCTL.TLBi  E                    o  Supply DCPS_HP4050_LIB as the library parametereA                       in the queue startup for this printer, this B                       is the P3 parameter to the command procedure;                       SYS$STARTUP:DCPS$EXECUTION_QUEUE.COM.   C                    o  The HP4050_DEVCTL library may/will need to be G                       recreated and modules re-edited and replaced with D                       each DCPS upgrade, particularly if any modulesH                       are updated in the original library. You will alsoG                       want to determine if the upgraded version of DCPSr?                       directly supports the particular printer.e  D                    o  To customize the processing of file extensionsG                       within DCPS (to enable or disable graybar output,uF                       for instance), use the information available in:  K                       SYS$LIBRARY:DCPS$FILE_EXTENSION_DATA_TYPE.DAT_DEFAULTt  4                    to create your own site-specific:  @                    SYS$LIBRARY:DCPS$FILE_EXTENSION_DATA_TYPE.DAT  )                    Also see Section 5.14.   J                                                                       5-39    v          0                    System Management Information      D           __________________________________________________________D           5.34  Why do $GETDEV MOUNTCNT and SHOW DEVICE mount counts                 differ?   E                    MOUNTCNT returns the local mount count, while SHOWd?                    DEVICE returns the cluster-wide mount count.i  D           __________________________________________________________@           5.35  What software is needed for Postscript printers?  ?                    The NorthLake PrintKit (http://www.nls.com/)t1                    and DECprint Supervisor (DCPS;_E                    http://www.openvms.compaq.com/openvms/Print/print_tC                    sw_prods.html) are common choices for support ofy2                    Postscript printers on OpenVMS.  A                    You may also require the installation of an IPi#                    transport stack.   E                    Also please see Section 15.2.2 and Section 15.2.3.d  D           __________________________________________________________A           5.36  How do I remove a PCSI-installed patch (ECO) kit?   D                    You cannot PRODUCT REMOVE a PCSI patch (ECO) kit.  I                    In order to remove an ECO kit, PCSI would have to have D                    copies of all the other version of the files fromF                    all other patches and products that previously wereH                    installed. This can clearly involve a large number ofG                    files and a large archive of old file versions and a G                    substantial quantity of disk space. While removal istF                    clearly theoretically possible, it is not currently                    implemented.o  G                    The following is the supported mechanism to remove af"                    PCSI patch kit.  I                    1  Execute a PRODUCT SHOW PRODUCE <product-name. /FULL J                       command. The "maintenance" column (132 column width)H                       shows the patches that have been installed. Keep a+                       copy of this listing.a  J                    2  Acquire kits for all of the maintenance kits listed.  G                    3  Re-install the prior FULL version of the product. I                       This will remove all patch kits, setting to productS3                       back to "original" condition.S                      5-40  e  e          0                    System Management Information        I                    4  Re-install all the patches in the list from step 1,dH                       except those patches which you have determined you"                       do not want.  E                    The above information also applies to PCSI PARTIAL                     kits.  D           __________________________________________________________H           5.37  SYSINIT-E, error mounting system device, status=0072832C  B                    This message can arise during an OpenVMS system                    bootstrap...w  V                    %MOUNT-F-DIFVOLMNT, different volume already mounted on this device  C                    For details and further information, use the DCLg                    command:m  2                    $ HELP/MESSAGE /STATUS=%X72832C  D           __________________________________________________________/           5.38  Resolving License PAK Problems?   F                    The PAK release date, the PAK termination date, andH                    the PAK version are the usual culprits when a licenseH                    product authorization key (PAK) check failure occurs.  H                    The PAK termination date is the date when the license#                    PAK will expire.   F                    The PAK release date is the date of the most recentD                    release date of the software package that will beH                    permitted by the particular license PAK. (The releaseG                    date check is analogous to a product version check.)eD                    The PAK version indicates the most recent product<                    version that is permitted by the license.  G                    Having multiple license PAKs registered (and active)oI                    can also cause problems if an expired PAK gets loaded. H                    You will want to DISABLE license PAKs you do not wish"                    to have loaded.  H                    Other problems include a failure to register each PAKI                    in all license databases throughout a multiple-system-nH                    disk cluster, with a consistent set of /INCLUDE lists@                    specified across each of the duplicated PAKs.  J                                                                       5-41    t          0                    System Management Information        F                    Additionally, you could have an invalid LMF$LICENSEC                    logical name defined. (If no LMF$LICENSE logical G                    name is defined, the standard license database named0<                    SYS$SYSTEM:LMF$LICENSE.LDB will be used.)  C                    You can display license failures by defining the *                    following logical name:  C                    $ DEFINE/SYS/EXEC LMF$DISPLAY_OPCOM_MESSAGE TRUE   =                    Enable your terminal as a license operator B                    (REPLY/ENABLE=LICENSE), define the LMF$DISPLAY_G                    OPCOM_MESSAGE logical name, and then try the failing D                    operation again. You should see one or more OPCOM&                    messages displayed.  I                    If you have the LMF$DISPLAY_OPCOM_MESSAGE logical name_F                    defined, you can (will?) see spurious license checkD                    failures-various products will check for multipleH                    licenses, and a few products will check for PAKs thatG                    either have not yet been or will not be issued. Once I                    you figure out which license has failed, you will want 1                    to deassign this logical name.m  H                    Note: that there is no license check failure does NOTG                    indicate that the particular product or operation is /                    permissible per the license.i  C                    To register a license PAK on a DECwindows system_F                    when DECwindows cannot start (because of an expiredH                    license or other licensing problem), follow the stepsE                    outlined in section Section 5.5 up through the usedF                    of the AUTHORIZE command. In place of the AUTHORIZEI                    command, use the console to register the license PAKs.mJ                    Also see Section 12.5 for licensing and troubleshooting                    information.o  E                    For information on licensing and on the numbers of J                    license units required for various products and variousH                    platforms, the License Unit Requirements Table (LURT)#                    is available at:d  C                    o  http://www.compaq.com/products/software/info/s                      5-42  S             0                    System Management Information      D           __________________________________________________________4           5.39  Changing the OpenVMS Version Number?  J                    Fool your friends, baffle your enemies, run the OpenVMS*                    version of your choice!  ,                    On OpenVMS Alpha systems:  5                    $ SET DEFAULT SYS$COMMON:[SYS$LDR]t                    $ RUN SYSVER                     REPLACE V9.9n                    WRITE                    $ EXIT   *                    On OpenVMS VAX systems:  5                    $ set default SYS$COMMON:[SYS$LDR]e8                    $ copy SYS.EXE SYS.EXE_IN-CASE-I-FAIL"                    $ patch SYS.EXE1                    define sys$gq_version=800044b8 !                    set mode asciio*                    !examine sys$gq_version,                    !examine sys$gq_version+44                    deposit sys$gq_version   = "V9.9"4                    deposit sys$gq_version+4 = "    "                    update                     exit$                    $ Exiti  :                    Then reboot the system at your leisure.  D           __________________________________________________________E           5.40  How to prevent users from choosing obvious passwords?h  G                    To prevent users from selecting obvious passwords ongF                    OpenVMS, you will want to use the reserved passwordI                    (password screening) mechanism. Effectively, you mergetD                    your list of reserved passwords into the existingJ                    reserved words database maintained by OpenVMS. (You canH                    also then require all users to reset their passwords-F                    via the pre-expired password mechanism-thus forcingE                    users to select new passwords.) For details on the I                    password screening mechanism, of the reserved password G                    database (VMS$PASSWORD_DICTIONARY.DATA), and detailsfD                    of how to merge your list of prohibited passwordsG                    into the database, please see the associated chapter E                    in the OpenVMS security manual. For details of the   J                                                                       5-43 o             0                    System Management Information        C                    password expiration mechanism, see the AUTHORIZEn1                    command qualifier /PWDEXPIRED.   I                    You can also implement a site-specific password filtereC                    with the information provided in the back of thesD                    OpenVMS Programming Concepts manual. The passwordG                    filter permits you to establish particular and site-rF                    specific password requirements. For details, pleaseC                    see the system parameter LOAD_PWD_POLICY and thesG                    programming concepts manual, and see the examples iniE                    SYS$EXAMPLES:. (Examples and documentation on V7.3 E                    and later reflect both platforms, the examples arerF                    found only on OpenVMS VAX kits on earlier releases.J                    The capabilities have existed on both the VAX and Alpha0                    platforms for some time now.)  B                    To verify current passwords, you can also use aH                    technique known to system crackers as the "dictionaryH                    attack"-the mechanism that makes this attack somewhatJ                    more difficult on OpenVMS is the hashing scheme used onH                    OpenVMS, and the file protections used for the SYSUAFJ                    authorization database. Given a dictionary of words andH                    the unprotected contents of the SYSUAF file, a searchI                    for obvious passwords can be performed. Interestingly,PG                    a "dictionary attack" also has the unfortunate side-.I                    effect of exposing the password to the user-while this F                    is clearly the goal of a system cracker, authorizedH                    privileged and non-privileged system users should notG                    know nor have access to the (cleartext) passwords of                     other users.s  D                    Accordingly, OpenVMS does not store the cleartestE                    password. Further, OpenVMS uses a password hashingiJ                    algorithm, not an encryption algorithm. This means thatJ                    storage of a cleartext password is deliberated avoided,I                    and the cleartext value is deliberately very difficult/F                    to obtain. The hash is based on a Purdy Polynomial,G                    and the hash itself includes user-specific values in I                    addition to the password, values that make the results <                    of the password hash unique to each user.  I                    Regardless of the use of a password hashing scheme, if J                    a copy of your password file should become available toH                    a system cracker, you will want to force all users to1                    use new passwords immediately.                       5-44     i          0                    System Management Information        E                    If you should require a user to verify a password,eF                    use the username, the user's salt value (this valueD                    is acquired via $getuai) and the user's specifiedG                    cleartext password, and compare the resulting hashedmE                    value (using a call to $hash_password) against theaH                    saved hashed password value (this value also acquiredF                    via $getqui). For reasons of security, avoid savingG                    a cleartext password value in any data files, and dooG                    not maintain the cleartext password in memory longertE                    than required. (Use of $ACM on V7.3-1 and later isX                     recommended.)  A                    Kerberos authentication (client and server) iseF                    available on OpenVMS V7.3 and later. Integration ofG                    Kerberos support into various Compaq and into third-e.                    party products is expected.  A                    External authentication is available in V7.3-1_D                    and later, with support for user-written external?                    authentication expected in V7.3-2 and later.r  C                    If you are simply looking for OpenVMS access andeD                    the SYSTEM and all other privileged passwords areI                    forgotten or otherwise unavailable, please see sectioneD                    Section 5.5 and/or the OpenVMS documentation set.  C                    Also please see the C2 guidelines in the OpenVMSl#                    security manual.   D           __________________________________________________________?           5.41__Please_help_me_with_the OpenVMS BACKUP utility?   8           5.41.1  Why isn't BACKUP/SINCE=BACKUP working?  J                    If you are seeing more files backed up than previously,I                    you are seeing the result of a change that was made to.J                    ensure BACKUP can perform an incrementation restorationC                    of the files. In particular, if a directory fileoI                    modification date changes, all files underneath it are-I                    included in the BACKUP, in order to permit incremental C                    restoration should a directory file get renamed.a      J                                                                       5-45 f  @          0                    System Management Information      '           _____________________________-J           5.41.1.1  Why has OpenVMS gone through the agony of this change?  D                    When a directory is renamed, the modified date isE                    changed. When the restoration needs to restore the I                    directory and its contents, and the restoration shouldiG                    not result in the restoration of the older directory J                    name when a series of incremental BACKUPs are restored.H                    Thus an incremental BACKUP operation needs to pick up&                    all of the changes.  E                    Consider performing an incremental restoration, to D                    test the procedures. This testing was how OpenVMSC                    Engineering found out about the problem that was.B                    latent with the old BACKUP selection scheme-theB                    old incremental BACKUP scheme would have missedG                    restoring any files under a renamed directory. HencewF                    the change to the selection mechanisms mentioned in"                    Section 5.41.1.  '           _____________________________O>           5.41.1.2  Can you get the old BACKUP behaviour back?  I                    Yes, please see the /NOINCREMENTAL qualifier availableoD                    on recent OpenVMS versions (and ECO kits). Use ofF                    this qualifier informs BACKUP that you are aware ofE                    the limitations of the old BACKUP behaviour arounds1                    incremental disk restorations._  '           _____________________________ >           5.41.2  What can I do to improve BACKUP performance?  @                    Use the documented commands in the manual forE                    performing incremental BACKUPs. Use the documented G                    incremental procedures. Don't try to use incremental 9                    commands in a non-incremental context.m  G                    Also consider understanding and then using /NOALIAS, J                    which will likely be a bigger win than will anything toJ                    do with the incremental BACKUPs, particularly on systemD                    disks and any other disks with directory aliases.  D                    See the OpenVMS V6.2 release notes for additional                    details.o                      5-46  t             0                    System Management Information      '           _____________________________o8           5.41.3  Why is BACKUP not working as expected?  8                    First, PLEASE READ THE BACKUP MANUAL.  A                    Second, PLEASE GET THE CURRENT BACKUP ECO KIT.M  ?                    Third, PLEASE SET THE PROCESS QUOTAS PER THEr!                    DOCUMENTATION.n  A                    BACKUP has a very complex interface, and thereAC                    are numerous command examples and extensive usersH                    documentation available. For a simpler user interfaceC                    for BACKUP, please see the documentation for the '                    BACKUP$MANAGER tool.   E                    As for recent BACKUP changes, oddities, bugs, etc:   I                    o  A change made in OpenVMS V6.2 WILL cause more files E                       to be included into a file-based BACKUP saveset E                       using /SINCE=BACKUP as all files underneath any E                       directory with a sufficiently recent (selected) G                       date will be included in the saveset. This change F                       was deliberate and intentional, and was mandatedE                       by the need to provide a functional incrementalu"                       restoration.  E                       Without the inclusion of these apparently-extrahG                       files, an incremental saveset can NOT be reliably                        restored..  D                    o  As part of the OpenVMS V6.2 change, the /SINCEF                       command-without the specification of the =BACKUPF                       keyword-selected more files than it should have.F                       This is a bug. This bug has been remedied in theI                       OpenVMS BACKUP source code and in some of (all of?)_*                       the BACKUP ECO kits.  >                    When working with BACKUP, you will want to:  E                    o  Ensure you have your process quotas set per the F                       recommendations in the OpenVMS System ManagementH                       documentation. Deviation from these values can andF                       will lead to access violation (ACCVIO) and other)                       untoward behaviour.   J                    o  Get the current BACKUP ECO kit and install it BEFORE?                       you attempt to troubleshoot any problems.r  J                                                                       5-47 i             0                    System Management Information        G                    o  Learn about the /NOINCREMENTAL (new) and /NOALIAS(E                       (V6.2 and later) command qualifiers. The formertH                       qualifier returns to the pre-V6.2 behaviour of theG                       /SINCE file selection mechanism, while the latter E                       (specified with /IMAGE) reduces the replication H                       of files on system disks and other disks with fileJ                       alias and directory alias entries. Both of these canG                       reduce the numbers of files that will be selectedg9                       and thus included into the saveset.   F                       Learn what /IGNORE=INTERLOCK means. This commandG                       probably does not provide what you think it does-yG                       those file system interlocks that this command iseH                       ignoring were implemented for a reason, after all.G                       Ignoring these interlocks can lead to missed dataoH                       and potentially to corruptions to individual filesH                       stored within the output saveset, corruptions thatE                       may or may not be reported. For details on thisaF                       BACKUP command qualifier, please see the Ask The*                       Wizard topic (2467).  =                    When working with the BACKUP callable API:   J                    o  Build your applications with the most current BACKUPH                       API available. Changes made to the V7.1-2 and V7.2H                       API were incompatible with the V7.1 and V7.2-1 andG                       later APIs, and this incompatibility was repaired0I                       via a BACKUP ECO kit. Do NOT build your application F                       with the versions of the BACKUP API that shippedJ                       with V7.1-2 and V7.2, as these are incompatible withF                       the BACKUP API constants that were used on other                       versions.b  '           _____________________________ 8           5.41.4  How do I fix a corrupt BACKUP saveset?  I                    BACKUP savesets can be corrupted by FTP file transfers F                    and by tools such as zip (particularly when the zipF                    tool has not been asked to save and restore OpenVMSF                    file attributes or when it does not support OpenVMSB                    file attributes), as well as via other means of                    corruptions.                         5-48C w             0                    System Management Information        F                    If you have problems with the BACKUP savesets afterH                    unzipping them or after an FTP file transfer, you canI                    try restoring the appropriate saveset attributes usingt                    the tool:  >                    $ @RESET_BACKUP_SAVESET_FILE_ATTRIBUTES.COM  E                    This tool is available on the OpenVMS Freeware (in G                    the [000TOOLS] directory). The Freeware is available F                    at various sites-see the Freeware location listingsH                    elsewhere in the FAQ-and other similar tools are also2                    available from various sources.  F                    In various cases, a SET FILE/ATTRIBUTES command canJ                    also be used. As the parameters of this command must beG                    varied as the target BACKUP saveset attributes vary,h4                    this approach is not recommended.  I                    Also see the "SITE VMS", /FDL, and various other file-OJ                    attributes options available in various FTP tools. (NotF                    all available FTP tools support any or all of these                    options.)  G                    Browser downloads (via FTP) and incorrect (binary oraF                    ascii FTP transfer modes) are notorious for causingG                    RMS file corruptions and particularly BACKUP saveset D                    corruptions. You can sometimes help encourage theG                    browser to select the correct FTP transfer type code !                    (via RFC1738):d  A                    o  ftp://host/urlname.ext;type=i ! request ftpS+                       image/binary transfert  A                    o  ftp://host/urlname.ext;type=a ! request ftpL)                       ascii/text transfer   J                    You can also often configure the particular web browserF                    to choose the appropriate transfer mode by default,C                    based on the particular file extensions, using a I                    customization menu available in most web browsers. You H                    can select that the specific file extentions involvedJ                    use the FTP binary transfer mode, which will reduce the.                    number of corruptions seen.  J                                                                       5-49               0                    System Management Information      '           _____________________________rC           5.41.5  How do I write a BACKUP saveset to a remote tape?a  G                    How to do this correctly was described at DECUS long:G                    ago. On the OpenVMS host with the tape drive, create 3                    the following SAVE-SET.FDL file:E                      RECORDo8                            FORMAT                  fixed7                            SIZE                    8192e  1                    Then create BACKUP_SERVER.COM:_                      $ !R                    $ ! BACKUP_SERVER.COM - provide remote tape service for BACKUP.                    $ !                    $ set noonS'                    $ set rms/network=16s,                    $ allocate mka500 tapedevE                    $ mount/nounload/over:id/block=8192/assist tapedev C                    $ convert/fdl=SAVE-SET sys$net tapedev:save-set.u,                    $ dismount/unload tapedev                    $ stop/id=0  G                    On the node where you want to do the backup, use the                     DCL command:E                      $ backup -e$                        srcfilespec -K                        node"user pwd"::"task=backup_server"/block=8192/save:  F                    One area which does not function here is the volumeH                    switch; multi-reel or multi-cartridge savesets. SinceG                    the tape is being written through DECnet and RMS andtE                    the magtape ACP, BACKUP won't see the media switch_H                    and will split an XOR group across the reel boundary.E                    BACKUP might well be willing to read such a multi- F                    reel or multi-cartridge saveset (directly, not overE                    the net) as the XOR blocks are effectively ignored I                    until and unless needed for error recovery operations. I                    BACKUP likely will not be able to perform an XOR-based @                    recovery across reel or cartridge boundaries.  I                    Unfortunately BACKUP can't read tapes over the network D                    because the RMS file attributes on a network taskE                    access look wrong; the attributes reported include +                    variable length records.a                      5-50     t          0                    System Management Information      '           _____________________________O9           5.41.6  How to perform a security disk erasure?o  ?                    Sometimes refered to as disk, tape, or media G                    declassification, as formatting, as pattern erasure,-C                    or occasionally by the generic reference of datanF                    remanence. While initially easy, characteristics ofE                    the media and of the device error recovery and badUI                    block handling can make this effort far more difficulta2                    than it might initially appear.  J                    Security and sensitivity of the data is central to thisF                    discussion, as is the value of the storage hardwareE                    involved-with data of greater value than the disksaE                    involved, physical destruction of the platters mayaE                    be the most expedient, economical, and appropriatep                    approach.  F                    Other potential options include the Freeware RZDISKE                    package, the OpenVMS INITIALIZE/ERASE command (and E                    potentially in conjunction with the $erapat system E                    service) and OpenVMS Ask The Wizard topics such as =                    (841), (3926), (4286), (4598), and (7320).e  '           _____________________________t9           5.41.7  How to enable telnet virtual terminals?e  D                    To enable virtual terminal support for telnet andA                    rlogin devices, add the following logical nameL3                    definitions into SYLOGICALS.COM:   B                    $ DEFINE/SYSTEM/EXECUTIVE TCPIP$RLOGIN_VTA TRUEB                    $ DEFINE/SYSTEM/EXECUTIVE TCPIP$TELNET_VTA TRUE  I                    See SYS$STARTUP:SYLOGICALS.TEMPLATE for details on the 6                    typical contents of SYLOGICALS.COM.  I                    In SYSTARTUP_VMS.COM, ensure that a command similar to ,                    the following is invoked:  a                    $ SYSMAN IO CONNECT VTA0/NOADAPTER/DRIVER=SYS$LOADABLE_IMAGES:SYS$TTDRIVER.EXEs  J                    In MODPARAMS.DAT, add the following line or (if alreadyH                    present) mask the specified hexidecimal value into anJ                    existing TTY_DEFCHAR2, and perform a subsequent AUTOGEN+                    with an eventual reboot:r  )                    TTY_DEFCHAR2 = %X20000i  J                                                                       5-51 v  ,          0                    System Management Information        2                    This value is TT2$M_DISCONNECT.  F                    On older TCP/IP Services-versions prior to V5.0-youB                    will have to perform the following UCX command:                      $ UCX4                    UCX> SET CONF COMM/REMOTE=VIRTUAL                                                                                              5-52                          J                    _______________________________________________________  &           6        Information on Mail      D           __________________________________________________________J           6.1  MAIL keeps saying I have new messages, but I don't. What do                I do?  J                    if you see the %MAIL-W-NONEWMAIL, no new messages errorG                    reported when MAIL indicates you have messages, then D                    the NEWMAIL count has become skewed from reality.  D                    The count of new mail messages is kept separatelyC                    from your mail folder, and is stored in VMSMAIL_VE                    PROFILE.DATA. It sometimes happens that this count F                    differs from what is stored in your mail folder. IfD                    this arises, invoke MAIL and repeatedly enter theF                    READ/NEW command (or press the keypad hyphen key onG                    an LK-compatible keyboard) until you see no new mail G                    messages. Then enter the command one more time. This 3                    will resynchronize the counters.y  G                    If you are operating in a cluster and find your maillC                    counts inconsistent across cluster members, youroJ                    customer is likely missing a definition of the VMSMAIL_D                    PROFILE logical name-and is probably also missingE                    definitions of other logical names associated withpE                    other shared files-or has one or more inconsistenteI                    definitions of this and likely of other logical names._  C                    For details on the configuration data files that >                    must be shared within a cluster, please seeE                    SYS$STARTUP:SYLOGICALS.TEMPLATE on V7.2 and later.   D           __________________________________________________________=           6.2  How do I send or read attachments in VMS MAIL?_  F                    Is there any way to send or read mail with files as(                    attachments from VMS?      J                                                                        6-1    n          &                    Information on Mail        I                    Not directly with the OpenVMS MAIL facility, but there_-                    are several other options:s  H                    o  Install PINE, available commercially from InnosoftF                       or free from Andy Harper. With PINE you can bothE                       send and receive MIME messages, if you have thes4                       appropriate viewers available.  /                      o  http://www.process.com/P  G                      o  http://www.agh.cc.kcl.ac.uk/files/vms/pine-vms/h  >                      o  ftp://ftp2.kcl.ac.uk/pub/vms/pine-vms/  D                    o  If you are working from an X11 server, use theG                       OpenVMS version of Netscape Navigator or Mozilla. J                       The mail download protocol chosen to access the mailJ                       server from the Navigator or Mozilla mail client canI                       be POP or IMAP, with the former causing messages to H                       be downloaded while the latter permits messages toG                       be retained on the mail server. Most folks prefer +                       IMAP for this reason.n  G                    o  MPACK/MUNPACK. To send a MIME mail, construct the H                       message with attachments manually using MPACK. YouJ                       cannot send the resulting file directly through MAILI                       because an extra blank header line will be inserted H                       between your message and the OpenVMS MAIL headers,J                       which will cause the message to appear as plain textG                       in most mail programs. Some TCP/IP stacks providetI                       a work around for this problem, and if that doesn'taE                       work, you should generally be able to force the F                       message directly into the SMTP port of your mail?                       machine. Examples of both methods are in:   L                      o  http://seqaxp.bio.caltech.edu/pub/SOFTWARE/mmail.com  C                       To read a MIME mail message, open it in MAIL,eE                       extract it to a file, then use MUNPACK to break 5                       out and decode the attachments.h  G                       MPACK/MUNPACK tools are also available on OpenVMSh$                       Freeware V5.0.  D                    o  With OpenVMS V7.2 and later, use the MIME tool,                       supplied with OpenVMS.                      6-2 _  _          &                    Information on Mail      D           __________________________________________________________4           6.3  How can I block SMTP mail relay spam?  G                    Use the anti-spam capabilities present in the TCP/IP,8                    Services V5.1 and later SMTP servers.  "                    Use a firewall.  G                    On earlier TCP/IP Services releases, some simple DCL F                    can reportedly prevent relay SMTP spam. Use the UCXG                    command SHOW SERVICE SMTP/FULL to find the directoryrE                    containing the UCX$SMTP_RECV_STARTUP.COM file, andn,                    insert the following DCL:                      $       !(                    $       ! Block spam.                    $       !Y                    $       MY_ADDRESS_LONG[0,32]=F$INTEGER(F$TRNLNM("SYS$REM_NODE")-"::") [                    $       MY_ADDRESS=F$FAO("!UB.!UB.!UB.!UB",F$CVUI(0,8,MY_ADDRESS_LONG),-mV                             F$CVUI(8,8,MY_ADDRESS_LONG),F$CVUI(16,8,MY_ADDRESS_LONG),-;                             F$CVUI(24,8,MY_ADDRESS_LONG))'"lG                    $       MY_ADDRESS_REVERSE=F$FAO("!UB.!UB.!UB.!UB",-cW                             F$CVUI(24,8,MY_ADDRESS_LONG),F$CVUI(16,8,MY_ADDRESS_LONG),- V                             F$CVUI(8,8,MY_ADDRESS_LONG),F$CVUI(0,8,MY_ADDRESS_LONG))'"\                    $       WRITE SYS$OUTPUT F$TIME()+" "+F$TRNLNM("SYS$REM_NODE")+MY_ADDRESSM                    $       UCX SHOW HOST 'MY_ADDRESS_REVERSE'.INPUTS.ORBS.ORGd*                    $       IF $STATUS.EQ.1                    $       THENoH                    $         WRITE SYS$OUTPUT "SPAM from relay rejected"!                    $         EXITl                     $       ENDIFR                    $       UCX SHOW HOST 'MY_ADDRESS_REVERSE'.SPAMSOURCES.ORBS.ORG*                    $       IF $STATUS.EQ.1                    $       THEN J                    $         WRITE SYS$OUTPUT "SPAM source relay rejected"!                    $         EXIT                      $       ENDIF                    $       !*                    $       ! Run receiver.                    $       !?                    $       run sys$system:ucx$smtp_receiver.exes$                    $       goto exit      J                                                                        6-3 e  y                    J                    _______________________________________________________  +           7        Information on Utilities       D           __________________________________________________________;           7.1  How do I play an audio CD on my workstation?   F                    If you've installed the DECwindows examples, you'llD                    find DECW$CDPLAYER.C, .DAT, .EXE, .UIL, and .UID.F                    Copy the .UID and .DAT files to DECW$USER_DEFAULTS:B                    (typically SYS$LOGIN:), define the logical nameF                    DECW$CD_PLAYER to be the device name of your CD-ROMI                    drive (eg. DKA400:), give yourself PHY_IO and DIAGNOSEuF                    privileges, and run the .EXE. (These privileges areG                    required, as the access to the CD-related extensionsiG                    will require the use of the privilege-protected IO$_iD                    DIAGNOSE I/O function code.) You can also installF                    the image with these privileges. See the source forH                    additional details - note that the comments regardingG                    the need for SYSGEN CONNECT are no longer applicable /                    (at least as of VMS V5.5-2).e  D                    There's also SYS$EXAMPLES:CDROM_AUDIO.C and .EXE,E                    a non-Motif program, available on OpenVMS VAX, and C                    DECW$EXAMPLES:DECW$CDPLAYER.* on OpenVMS VAX andc!                    OpenVMS Alpha.   E                    The standard OpenVMS ATA (IDE) SYS$DQDRIVER device A                    driver does not support the necessary does not C                    support the necessary IO$_DIAGNOSE function codei@                    that is required for access to audio CD mediaD                    commands (on OpenVMS versions prior to V7.3), but@                    an updated SYS$DQDRIVER device driver (sourceB                    code and all) with this capability and with theC                    source code of an updated DECW$CDPLAYER CD audio F                    player is available on the OpenVMS Freeware websiteI                    (www.openvms.compaq.com/freeware/dqdriver/), and thesegF                    updates are also included on OpenVMS Freeware V5.0,H                    and OpenVMS ECO kits containing newer versions of the(                    driver are available.  D                    OpenVMS Alpha V7.3 and later include a version ofH                    SYS$DQDRIVER with the necessary IO$_DIAGNOSE support.  J                                                                        7-1    t          +                    Information on UtilitiesS      D           __________________________________________________________C           7.2  How do I access a Microsoft Windows floppy disk from0                OpenVMS?   G                    The HP Advanced Server (formerly known as PATHWORKS) B                    for OpenVMS product includes an unsupported andH                    undocumented utility called PCDISK, and this tool canH                    read and write various Microsoft MS-DOS and Microsoft0                    Windows FAT-format diskettes.  G                    ProGIS in Germany sells a product called VMove which_I                    supports DOS files on many different device types. ForsA                    more information, send mail to info@progis.de.o  C                    Engineering Software has a product called VAKSATrH                    which will read, write, and erase files on MS-DOS FATG                    diskettes. Available for both VAX and Alpha. Contactt;                    ed@cityscape.co.uk for more information.i  E                    MadGoat PC Exchange (PCX) is a utility for copyingeG                    files to and from MS-DOS and Microsoft Windows (FAT)wH                    format diskettes under OpenVMS, using an RX23 (3.5"),H                    RX26 (3.5"), or RX33 (5.25") diskette drive. For 3.5"H                    diskettes, high-density disks can be read or written;H                    double-density disks are read-only. Only high-density3                    disks are supported on the RX33.a  -                    o  http://www.madgoat.com/   D           __________________________________________________________E           7.3  How do I play sound files on an AlphaStation? DECsound                 doesn't work.  E                    The new AlphaStation systems use a different sound F                    board (Microsoft Sound System) than the earlier DECD                    3000 series systems, and DECsound, as supplied byJ                    DECwindows Motif, doesn't support this board. HP offersH                    an optional product, Multimedia Services for OpenVMS:  5                    o  http://www.compaq.com/info/spd/ D                       OpenVMS typically uses SPD 25.01.xx and/or SPD                       41.87.xx.a  I                    which provides a replacement DECsound for this card as G                    well as many other features (an AVI and MPEG player, /                    video capture support, etc.)e  ;                    Ensoniq sound support is also available.t                      7-2               +                    Information on Utilitiesl      D           __________________________________________________________:           7.4  Why is DECmigrate not working with Fortran?  B                    %OTS-F-INDATCOR internal data corrupted in Run-           time Library  H                    This error can arise with Fortran programs if you areE                    running a recent version of OpenVMS Alpha, and areiJ                    using DECmigrate to translate Fortran applications. TheH                    DECmigrate Run-Time Library attempts to support mixedH                    translated-native I/O to the same unit by sharing theH                    native Fortran RTL's internal data structures, and inJ                    OpenVMS 7.2 these structures changed and the translated3                    RTL was not updated accordingly.   H                    You can copy DEC$FORRTL.EXE from OpenVMS 7.1, copyingD                    it to some spare directory, and then defining theH                    logical name DEC$FORRTL to point to it before runningA                    your translated application. Or rebuilding theoB                    application to use the available native FortranE                    compiler. Or you can apply the current Fortran RTLF1                    kit, which has a fix for this.   %                    See Section 13.11.o  D           __________________________________________________________9           7.5  How do I read IBM EBCDIC tapes on OpenVMS?r  J                    Most (all?) IBM EBCDIC-based systems can read and writeD                    ANSI-labeled ASCII magtapes. Fixed-length recordsF                    (MOUNT /FOREIGN /BLOCKSIZE=512 /RECORDSIZE=512, forE                    one-block records) and the DCL COPY command can be I                    used to transfer fixed-record-size text files out ontouG                    tape media, or to read from fixed-record tape media.aG                    Please consult the IBM documentation for the detailseJ                    and command syntax needed when reading and writing ANSIF                    media using IBM JCL or other applicable IBM command                    language.  I                    There exists various freeware around (TAPECOPY, ETAPE, G                    TCOPY, MTEXCH) that can read and write EBCDIC tapes.hC                    Visit the Encompasserve (DECUS) website softwaresF                    archives search engine (via http://www.decus.org/),7                    and search for "EBCDIC" for details.s  B                    OpenVMS does not include an integrated tool forG                    EBCDIC tape processing, but does provide a charactersE                    conversion API useful within application programs.u  J                                                                        7-3 o  i          +                    Information on Utilitiese        +                    One source for ETAPE is:r  <                    o  http://www.ualr.edu/ftp/vms/ETAPE_SRC/  G                    The OpenVMS Freeware V5.0 distribution included this '                    ETAPE tool, as well.o  D           __________________________________________________________6           7.6  How can I patch an OpenVMS Alpha image?  7                    Using the OpenVMS Freeware tool ZAP:d  E                    o  www.openvms.compaq.com/freeware/freeware50/rms_t                       tools/  C                    tell ZAP to read a block (bucket) of informationcG                    based on the virtual block number (VBN), using X forsG                    hexadecimal. Dump yourself into the OpenVMS debuggereH                    with R2 pointing into the buffer, EXAMINE/INSTRUCTIONI                    as needed, alter the buffer as required, GO to get out G                    of the debugger and back into ZAP, and use the ZAP W_6                    command to write the updated block.                                                                7-4 s                       J                    _______________________________________________________             8        DCL Details      D           __________________________________________________________5           8.1  How do I run a program with arguments?   E                    The RUN command does not accept arguments. To pass H                    arguments to a program, you must use what is called a2                    "foreign command". For example:  3                    $ unzip :== $disk:[dir]unzip.exel                    $ unzip -?a  G                    The leading $ in the equivilence name for the symbol D                    definition is what makes the DCL symbol a foreignD                    command. If the device and directory are omitted,*                    SYS$SYSTEM: is assumed.  G                    Under OpenVMS V6.2 and later, DCL supports automaticiB                    foreign command definition via the logical nameH                    DCL$PATH:. An example of a definition of this logical                    name is:   M                    $ DEFINE DCL$PATH SYS$DISK:[],ddcu:[mytooldir],SYS$SYSTEM:n  G                    DCL will first look for a command in the DCL commandTE                    table, and if no match is found and if DCL$PATH is H                    defined, it will then look for command procedures andH                    executable images with filenames matching the commandH                    specified, in the directories specified via DCL$PATH.G                    The first match found is invoked, and under OpenVMS,eI                    the DCL$PATH support will cause a command procedure to E                    be activated in preference to an executable image.w  A                    For more information on foreign commands or on E                    automatic foreign command support, see the OpenVMS_!                    User's Manual.   )                    See also Section 10.3.   F                    If you want to create a detached process that takesJ                    arguments from a command line, it must be run under theI                    control of a command line interpreter (CLI) (typically F                    DCL). This is done by placing the command line in a  J                                                                        8-1                                   DCL Details        H                    file, specifying SYS$SYSTEM:LOGINOUT.EXE as the imageI                    to run and the command file as the input. For example:   2                    $ OPEN/WRITE CMD TEMP_INPUT.COM6                    $ WRITE CMD "$ MYCOMMAND arguments"                    $ CLOSE CMDK                    $ RUN/DETACHED SYS$SYSTEM:LOGINOUT /INPUT=TEMP_INPUT.COM   F                    Various OpenVMS library calls (such as lib$spawn(),E                    cli$dcl_parse(),  and the C library system() call) G                    require access to a command line interpreter such as I                    DCL to perform requested actions, and will not operate -                    if a CLI is not available.   E                    When a CLI is not available, these calls typically F                    return the error status SS$_NOCLI. And as mentionedH                    above, invoke the image LOGINOUT to cause a CLI (suchF                    as DCL) to be mapped into and made available in the1                    context of the target process.T  J                    For examples of how TCP/IP Services sets up its foreignB                    commands (which includes tools such as uuencodeF                    and uudecode), please see the DCL command procedure9                    SYS$STARTUP:TCPIP$DEFINE_COMMANDS.COM.   )                    Also see Section 8.10.   D           __________________________________________________________1           8.2  How can I clear the screen in DCL?e  C                    The simplest way is the TYPE/PAGE NLA0: command.I  F                    You can set up a symbol to clear the screen in your                    LOGIN.COM:   ,                    $ CLS :== TYPE/PAGE NLA0:  D           __________________________________________________________B           8.3  Using REPLY/LOG from DCL? Disabling Console OPCOMs?  H                    Your terminal must be enabled as an operator terminalF                    before the REPLY/LOG command can be used, but a DCLF                    procedure (batch command file, system startup, etc)E                    does not have an associated terminal. To make this G                    work, use the following sequence to enable the OPA0: G                    console as the operator terminal, then the REPLY/LOG ,                    command will be accepted:                      8-2 =  K                              DCL Details        3                    $ DEFINE/USER SYS$COMMAND _OPA0:i                    $ REPLY/LOG3                    $ DEFINE/USER SYS$COMMAND _OPA0:c!                    $ REPLY/ENABLE   G                    To disable the system console terminal (OPA0:) as an @                    operator terminal, use the following command:  3                    $ DEFINE/USER SYS$COMMAND _OPA0: "                    $ REPLY/DISABLE  H                    Also see SYLOGICALS.COM (and SYLOGICALS.TEMPLATE) forE                    information on configuring the behaviour of OPCOM,AD                    including the (default) use of the system consoleD                    (OPA0:) as an operator terminial and the specificI                    contents and behaviour of the system operator log file                      OPERATOR.LOG.  D           __________________________________________________________8           8.4  How do I generate a random number in DCL?  J                    Here is a random number generator, just do a GOSUB RANDG                    and the global symbol RANDOM will contain a randomlylI                    generated number. You can feed the generator a ceilingE:                    value (__CEIL)  or a new seed (__SEED).                                      J                                                                        8-3 s  w                              DCL Details        V                    $! RAND - returns a positive random number ("RANDOM") between 0 and(                    $!        __CEIL - 1.6                    $! sharris-at-sdsdmvax.fb3.noaa.gov                    $ RAND:                    $/                    $ IF F$TYPE(__SEED) .EQS. ""r                    $ THENs@                    $     ! seed the random number generator, ...+                    $     __NOW = F$CVTIME()r9                    $     __HOUR = 'F$EXTRACT(11,2,__NOW)' ;                    $     __MINUTE = 'F$EXTRACT(14,2,__NOW)' ;                    $     __SECOND = 'F$EXTRACT(17,2,__NOW)'l9                    $     __TICK = 'F$EXTRACT(20,2,__NOW)'                     $T                    $     __SEED == __TICK + (100 * __SECOND) + (6000 * __MINUTE) + --                             (360000 * __HOUR)kW                    $     ! the generator tends to do better with a large, odd seed, ...t2                    $     __SEED == (__SEED .OR. 1)(                    $     ! clean up, ...-                    $     DELETEX/SYMBOL __NOWC.                    $     DELETEX/SYMBOL __HOUR0                    $     DELETEX/SYMBOL __MINUTE0                    $     DELETEX/SYMBOL __SECOND.                    $     DELETEX/SYMBOL __TICK                    $ ENDIF                    $H                    $ IF F$TYPE(__CEIL) .EQS. "" THEN __CEIL = %X3FFFFFFF                    $1                    $ __SEED == __SEED * 69069 + 1m                    $J                    $ RANDOM == (__SEED.AND.%X3FFFFFFF)/(%X40000000/__CEIL)                    $                    $ RETURN_  D           __________________________________________________________,           8.5  What does the MCR command do?  H                    The MCR is an artifact of RSX compatibility mode, theH                    operating system from which OpenVMS is descended. MCRE                    is the Monitor Console Routine, and the command is I                    intended to activate RSX compatibility mode utilities.iE                    When used on OpenVMS, the command is most commonly G                    used to run the specified image and-because the tooli                      8-4                                   DCL Details        G                    detects the image is not a compatibility-mode image- D                    it acts as a form of RUN command with the defaultH                    file specification of SYS$SYSTEM:.EXE. MCR passes anyI                    (optional) command line arguments in a fashion similart8                    to a foreign command. In other words:                       $ MCR FOO BAR  $                    is equivalent to:  "                     $ FOO :== $FOO                     $ FOO BAR   I                    MCR is not documented. Use of a foreign command or theaH                    DCL$PATH mechanism is preferred. For details on this,#                    see Section 8.1.s  D           __________________________________________________________9           8.6  How do I change the OpenVMS system prompt?   G                    You can use the SET PROMPT command for this purpose. J                    SET PROMPT sets the DCL prompt to the specified string.  E                    When you want to display variable information, youlD                    will need to establish a tie-in that provides theE                    information to the SET PROMPT command as required.t  C                    If you wish to display the default directory forsE                    instance, you will have to establish a tie betweenBJ                    the SET DEFAULT command and the SET PROMPT commands, asI                    there is no direct way to get the default directory aseI                    the DCL prompt. You can easily acquire or create a setoI                    of DCL command procedures that perform the SET DEFAULTaG                    and SET PROMPT for you. These DCL command procedurest/                    often use a command such as:   :                    $ set prompt='f$environment("default")'  J                    More advanced users could implement a system service orH                    other intercept, and use these tools to intercept theE                    directory change and reset the prompt accordingly.sB                    (This approach likely involves some kernel-modeD                    programming, and requires write access to various9                    undocumented OpenVMS data structures.)s  J                    There are related tools available from various sources,5                    including the following web sites:a  6                    o  ftp://ftp.hhs.dk/pub/vms/setpmt/  J                                                                        8-5                                   DCL Details        ?                    o  ftp://ftp.tmesis.com/sys_service_hook.srci  J                    o  James F. Duff has also made available a Macro32 toolJ                       known as TIME_PROMPT, a tool that sets the prompt to.                       the current system time.  C                    o  Many folks have contributed DCL procedures toRE                       perform this task. Visit the newsgroup archivesC3                       for information and examples.   D           __________________________________________________________C           8.7  Can I do DECnet task-to-task communication with DCL?   1                    Yes, you can do this with DCL.s  H                    The OpenVMS DECnet documentation shows various simpleI                    examples using the task object and the TYPE command tooH                    trigger the execution of a DCL command procedure on aH                    remote node. An example DCL command procedure that isH                    rather more advanced than using the TYPE command as aB                    trigger is included in the Ask The Wizard area:  ;                    o  http://www.openvms.compaq.com/wizard/   E                    o  http://www.openvms.compaq.com/wizard/wizard.zip   F                    For additional information, please see Section 3.9.  H                    DCL does not include support asynchronous I/O, thus aJ                    predetermined protocol or a predetermined "turn-around"I                    command sequence must be implemented in order to avoideJ                    protocol deadlocks-cases where both tasks are trying toH                    write or both tasks are trying to read. The task thatJ                    is writing messages to the network must write (or writeH                    and read) a predetermined sequence of messages, or itI                    must write a message that tells the reader that it canBH                    now start writing messages. (This is the essence of a>                    basic half-duplex network protocol scheme.)  D           __________________________________________________________=           8.8  How can I get the width setting of a terminal?   ;                    $ width = f$getdvi(terminal,"DEVBUFSIZ")                       8-6 _  O                              DCL Details      D           __________________________________________________________6           8.9  How can I substitute symbols in a PIPE?  E                    Use DCL ampersand substitution, and not apostrophee                     substitution.  V                    $ pipe show system | search sys$input opcom | (read sys$input pid ;O                        pid=f$element(0," ",pid) ; define/system opcom_pid &pid)a'                    $ show log opcom_pid B                        "OPCOM_PID" = "0000020B" (LNM$SYSTEM_TABLE)  D           __________________________________________________________?           8.10  Use of RUN/DETACH, LOGINOUT, and logical names?   G                    With a command to create a detached process such as:   K                    $ RUN/DETACHED SYS$SYSTEM:LOGINOUT /INPUT=TEMP_INPUT.COM   I                    If you are trying to use a logical name as the /INPUT,oB                    /OUTPUT or /ERROR on a RUN/DETACH command, thenE                    you must translate the logical name specificationsmE                    to physical references before passing them, or thepJ                    definitions must reside in a logical name table that is8                    visible to the newly-created process.  F                    Also note that LOGINOUT only creates the SYS$LOGIN,H                    SYS$LOGIN_DEVICE, and SYS$SCRATCH logical names if itI                    is processing a login that is based on the contents of,J                    a SYSUAF record-without access to the associated SYSUAFI                    record, this information is not available to LOGINOUT. E                    (If you want to see these particular logical namesEH                    created, then please specify the /AUTHORIZE qualifier0                    on the RUN/DETACHED command.)  D                    If you do not specify LOGINOUT as the image, thenI                    there is no easy way to get these logical names. Also, F                    any logical names that are used in the target imageD                    file specification must also be in a logical nameE                    table accessible (by default) by the newly-createddH                    detached process. Shared tables include the group (ifG                    the process is in the same UIC group) and the systemrH                    table. (If the target process is to be in another UICH                    group, a suitablly privileged user or application canG                    create the necessary logical name(s) directly in theT3                    other group logical name table.)O  J                                                                        8-7 t  e                              DCL Details        D                    When in doubt, create a short DCL command file asE                    input, and use a SHOW LOGICAL and similar commands G                    to examine the context. (And use physical device and_I                    directory references on the RUN/DETACH of the LOGINOUTIG                    image, when specifying this command file as /INPUT.)_D                    Also remember to check both security auditing andG                    system accounting when troubleshooting problems with "                    the RUN/DETACH.  (                    Also see Section 8.1.  D           __________________________________________________________@           8.11  How to use escape and control characters in DCL?  G                    To write a message and then the bell character, use:   "                    $ bell[0,7] = 74                    $ write sys$output "Hello''bell'"  /                    To write blinking text, use:s  "                    $ esc[0,7] = 27+                    $ text = "Blinking Text"e@                    $ write sys$output "''esc'[5m''text'''esc'[m"  @                    Also see sections Section 11.7, Section 12.1.                                                        8-8 m  a                    J                    _______________________________________________________             9        Files      D           __________________________________________________________)           9.1  How can I undelete a file?y  H                    OpenVMS doesn't have an "undelete" function. However,G                    if you are quick to write-protect the disk or if yougJ                    can guarantee that no new files get created or existingE                    files extended, your data is still on the disk and F                    it may be possible to retrieve it. The FLORIAN toolJ                    available from various websites can potentially recoverJ                    the file, see question Section 13.1 for pointers. OtherG                    alternatives here include the DFU tool, available on_<                    the OpenVMS Freeware CD-ROM distribution.  H                    If you are setting up a user environment for yourselfJ                    or for others, it is quite easy to use DCL to intercept6                    the DELETE command, using a symbol:  8                    $ DEL*ETE :== @SYS$LOGIN:MYDELETE.COM  @                    The DELETE symbol will cause the procedure toA                    be invoked whenever the user enters the DELETE G                    command, and it can copy the file(s) to a "trashcan" E                    subdirectory before issuing a "real" DELETE on theeH                    files. Other procedures can retrieve the file(s) fromJ                    the "trashcan" subdirectory, and can (and should) cleanH                    out the "trashcan" as appropriate. (Realize that thisE                    DELETE symbol can interfere with DELETE/GLOBAL andh/                    other similar DCL commands.)p  D           __________________________________________________________I           9.2  Why does SHOW QUOTA give a different answer than DIR/SIZE?o  G                    DIRECTORY/SIZE doesn't take into account the size ofaF                    file headers which are charged to your quota. Also,G                    unless you use DIRECTORY/SIZE:ALL, you will see only F                    the "used" size of the file, not the allocated sizeG                    which is what gets charged against your quota. Also,v;                    you may have files in other directories.e  J                                                                        9-1                                   Files        ;                    $ DIRECTORY/SIZE=ALL/GRAND [username...] I                    Grand total of D1 directories, F1 files, B1/B2 blocks.e=                    $ DIRECTORY/SIZZ=ALL/GRAND [-]username.DIR D                    Grand total of 1 directory, 1 file, B3/B4 blocks.                    $ SHOW QUOTAtC                    User [username] has B5 blocks used, B6 availableSP                    of B7 authorized and permitted overdraft of B8 blocks on disk  D                    If the user has no files in other directories andH                    all file-headers are only 1 block, then the following                     should apply:  "                      B5=B2+B4+F1+1  G                    If the diskquota has drifted out of synchronization,OH                    then the system-manager can force a quota rebuild-dueE                    to various factors, the quota file can potentiallyNF                    drift from the actual use over time, and a periodicE                    rebuild can be performed at appropriate intervals.M  D                    Also be aware that the DIRECTORY/SIZE command canH                    report larger values than might otherwise be expectedF                    when used to evaluate files and/or directories thatF                    are alias links-such as the system roots on OpenVMSC                    system disks-as the command reports a total thatlF                    is cumulative over all of the files and directoriesC                    examined, without regard for which ones might bevF                    alias entries and which are not. (In other words, aG                    DIRECTORY/SIZE of an entire OpenVMS system disk willpF                    report a disk useage value larger than the (usuallyC                    more accurate) value reported by the SHOW DEVICEnI                    command. This as a result of the alias entries linking H                    each SYS$SYSDEVICE:[SYSCOMMON]SYS*.DIR directory fileD                    and the SYS$SYSDEVICE:[000000]VMS$COMMON.DIR file                    together.)I  D           __________________________________________________________I           9.3  How do I make sure that my data is safely written to disk?   E                    If your application must absolutely guarantee that G                    data is available, no matter what, there's really no I                    substitute for RMS Journaling and host- or controller- J                    based shadowing. However, you can achieve a good degreeG                    of data integrity by issuing a SYS$FLUSH RMS call atRG                    appropriate times (if you're using RMS, that is.) IfTI                    you're using a high-level language's I/O system, check'                      9-2 B  R                              Files        I                    that language's documentation to see if you can accessSI                    the RMS control blocks for the open file. In C you can 0                    use fflush followed by fsync.  E                    For details on disk bad block handling on MSCP and H                    on SCSI disk devices, please see Ask The Wizard (ATW)                     topic (6926).  ;                    o  http://www.openvms.compaq.com/wizard/   E                    o  http://www.openvms.compaq.com/wizard/wizard.zip   F                    For additional information, please see Section 3.9.  D           __________________________________________________________J           9.4  What are the limits on file specifications and directories?  E                    A file specification has an aggregate maximum size D                    of 255 characters at present. The node and deviceC                    specification may be up to 255 characters each -_F                    file name and file types may be up to 39 charactersG                    each. File versions are from 1 through 32767, thoughsG                    0 (latest version), -0 (oldest version) and -n (n'thAI                    previous version) can be used in most contexts. A fileAE                    specification may not have more than 8 directories:F                    and subdirectories - while it is possible to createE                    subdirectories of greater depth, accessing them iseH                    problematic in most cases and this should be avoided.  E                    Application developers should use OpenVMS-suppliedtJ                    routines for parsing file specifications - this ensuresE                    that changes in what is allowable will not tend todI                    break your application. Consider that various parts ofsI                    the file specification may contain quoted strings with G                    embedded spaces and other punctuation! Some routines H                    of interest are SYS$FILESCAN, SYS$PARSE and LIB$TRIM_E                    FILESPEC. For further information, see the OpenVMS .                    Guide to File Applications.  A                    Performance of larger directory files improvesoF                    (greatly) with OpenVMS V7.2 and later-operations onG                    directory files of 128 blocks and larger were rather H                    slower on earlier OpenVMS releases due to the smallerG                    size of the directory cache and due to the directorys(                    I/O processing logic.  J                                                                        9-3                                   Files        F                    For fastest directory deletions, consider a reverseI                    deletion-delete from the last file in the directory to I                    the first. This reversal speeds the deletion operation F                    by avoiding unnecessary directory I/O operations asH                    the files are deleted. Tools such as the Freeware DFUI                    can be used for this purpose, as can various available 9                    reverse-DELETE DCL command procedures.S  D           __________________________________________________________G           9.5  What is the largest disk volume size OpenVMS can access?   @                    One Terabyte (TB; 2**31 blocks of 2**9 bytes;D                    0x07FFFFFFF blocks). 255 volumes in a volume set.E                    The largest contiguous allocation possible for anyd9                    particular file is 0x03FFFFFFF blocks.   H                    Prior to the release of V6.0, the OpenVMS file systemH                    was limited to disk volumes of 8.38 GB (2**24 blocks,,                    16777216 blocks) or less.  I                    On some systems, there are restrictions in the consoleuJ                    program that limit the size of the OpenVMS system disk.C                    Note that data disks are not affected by console B                    program limits. For example, all members of theF                    VAXstation 3100 series are limited to a system diskH                    to 1.073 GB or less due to the console, though largerF                    data disks are possible. This limit due to the SCSII                    drivers used by and built into the console ROM to readAJ                    the OpenVMS bootstrap files, and these same drivers areE                    also used by OpenVMS to write the system crashump.n  D                    There are numerous discussions of this VAXstationE                    3100 in the comp.os.vms newsgroup archives. Please(I                    use Google newsgroup search to search the archives for G                    further details, for discussions of the workarounds,tG                    and for details of the potential for a simple failednD                    bootstrap and particularly for discussions of theB                    potential for severe system disk corruptions on                    crashes._  C                    Some SCSI disks with capacities larger than 8.58oH                    gigabytes (GB) will require the use of an OpenVMS ECOE                    kit (eg: ALPSCSI04_062 or later; see Section 14.26iG                    for details) for new SCSI device drivers. Failure tosG                    use this ECO can cause "rounding errors" on the SCSIiH                    disk device capacity-OpenVMS will not use nor display                      9-4 o  p                              Files        G                    the full capacity of the drive-and "%sysinit-e-error.F                    mounting system device status equals 000008C4" (8C4G                    -> "%SYSTEM-?-FILESTRUCT, unsupported file structure G                    level") errors during bootstrap. (One workaround for H                    the bootstrap when the bitmap is located far into theI                    disk is the use of INIT/INDEX=BEGIN.) The problem here I                    involves the particular extensions and fields used for_G                    larger capacity disks within the SCSI specificationstA                    and within the various intepretations of same.a  -                    For ATA (IDE) disk drives:   J                    o  Versions of SYS$DQDRIVER *BEFORE* X-15 topped out at                       8.455 GB.   G                       Fixed drivers (equal or greater than "X-15") weret!                       shipped in:   7                      o  OpenVMS Alpha V7.2-1, and laters  7                      o  V7.2 UPDATE V1.0 ECO, and laterh  9                      o  V7.1-2 UPDATE V1.0 ECO, and later   9                      o  V7.1-2 UPDATE V3.0 ECO, and latere  H                    o  The newer SYS$DQDRIVER driver operates to disks upH                       to 33 GB without (known) problems, and effectivelyE                       works with rather larger disks (up to circa 137iG                       GB) but is known to report an incorrect number ofL9                       "cylinders" with disks above 33 GB.n  G                    See Section 14.4.4.2 for additional ATA SYS$DQDRIVERs                    information.   E                    Be aware that a known restriction in certain older J                    versions of the Alpha SRM Console prevents booting mostF                    ATA (IDE) drives larger than 8.455 GB, depending onE                    exactly where the various files are located on therD                    volume. Updated SRM consoles for systems with SRMG                    and ATA (IDE) drive support are (will be) available.cE                    (OpenVMS Engineering has successfully bootstrapped,I                    20GB ATA (IDE) disks using the appropriate SRM console                     version.)  J                                                                        9-5    N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faqwN  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.com    ------------------------------  # Date: Thu, 03 Jul 2003 17:14:04 GMT 2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman); Subject: OpenVMS Frequently Asked Questions (FAQ), Part 5/9i1 Message-ID: <wvZMa.3895$bl3.677@news.cpqcorp.net>g    v                              Files        J                    NOTE: All ATA-related disk sizes listed in this sectionH                    are stated in units of "disk (base ten) gigabytes" (1G                    GB = 10^9 bytes) and NOT in units of "software (basefH                    two) gigabytes" (1 GB = 2^30 (1073741824.) bytes. See!                    Section 14.26.3  I                    Be aware that larger disks that are using an extension D                    of SCSI-2- disks that are using a mode page fieldG                    that the SCSI-2 specifications normally reserved forwH                    tape devices-to permit a larger disk volume size willE                    require a SCSI driver update for OpenVMS, and this_G                    change is part of V7.1-2 and later, and also part of E                    ALPSCSI07_062 and later. (These larger disks disks I                    will typically report a DRVERR, or will see the volumelH                    size "rounded down".) SCSI disks larger than 16777216J                    blocks cira 8.455 GB (base ten); 8GB (base two) requireJ                    this ECO, or require the use of OpenVMS Alpha V7.1-2 or                    later.i  C                    Applications written in C can be limited to filedF                    sizes of two gigabytes and less, as a result of theG                    use of longword values within C file operations, andaD                    specifically off_t. This restriction is lifted inH                    OpenVMS V7.3-1 and later, and with the application ofJ                    the C ECO kits available for specific earlier releases.I                    The use of a longword for off_t restricts applications_G                    using native C I/O to file sizes of two gigabytes or I                    less, or these applications must use native RMS or XQP 1                    calls for specific operations.s  9                    Also see Section 14.14, Section 14.26.   D           __________________________________________________________E           9.6  What is the maximum file size, and the RMS record sizei                limit?m  E                    RMS can store individual files of a size up to thenH                    maximum supported volume size. Under OpenVMS V6.0 andG                    later, the volume size and the RMS maximum file sizeVB                    limit is 2**31 * 512 bytes-one terabyte (1 TB).  D                    "Use a volume set to provide a large, homogeneousI                    public file space. You must use a volume set to create D                    files that are larger than a single physical diskH                    volume. (The file system attempts to balance the load                      9-6    t                              Files        I                    on the volume sets, for example, by creating new filessF                    on the volume that is the least full at the time.)"  H                    "You can add volumes to an existing volume set at anyI                    time. The maximum number of volumes in a volume set isS                    255."  E                    The RMS formats-sequential, relative, and indexed-bG                    are limited by the one terabyte maximum volume size.FH                    RMS relative files are further limited to a number ofF                    records that will fit in 32 bits-4 billion records.F                    Sequential and indexed formats do not have a record                    limit.a  9                    Also see Section 10.14, Section 14.26.o  D           __________________________________________________________D           9.7  How do I write CD-Recordable or DVD media on OpenVMS?  F                    How to create CD-R, CD-RW, DVD-R, DVD+R, DVD-RW, or+                    DVD+RW media on OpenVMS?   F                    o  Acquire a comparatively recent SCSI-based or ATAE                       (IDE) CD-R or DVD-R/RW or DVD+R/RW drive. Older G                       drives can be problematic, while newer drives are =                       readily available, cheap and very fast.   J                    o  Get LDDRIVER from the Freeware. Versions of LDDRIVERI                       are latent in OpenVMS Alpha V7.3-1 and later. (Look C                       within SYS$MANAGER:CDRECORD.COM for details.),  H                    o  Get CDRECORD or CDWRITE or other similar recordingG                       tool. (CDRECORD and CDWRITE are freely available, B                       though versions are not on the Freeware V5.0I                       distribition; the URLs are referenced later in thisWJ                       section). Versions of CDRECORD are latent in OpenVMS-                       Alpha V7.3-1 and later.   E                    o  Build the contents of the disk on the LD device                         partition.  I                    o  Use the CDRECORD or CDWRITE or other tool to recordtH                       the contents of the LD partition directly onto the*                       CD-R or CD-RW media.  J                                                                        9-7 s  t                              Files        C                    Alternatively, consider the following command one2                    OpenVMS Alpha V7.3-1 and later:  1                    @SYS$MANAGER:CDRECORD.COM HELPH  H                    While folks have had success getting PC-based CD-R/RWE                    or DVD-R/RW or DVD+R/RW tools to work with OpenVMSyH                    partitions, it is far easier and more reliable to useJ                    the OpenVMS-based versions of these tools and directly-$                    attached devices.  A                    More details: Creation of CD recordable or DVD D                    recordable media under OpenVMS typically involvesF                    one of two approaches: the use of the optional CD-RJ                    (`Scribe') capabilities available for the InfoServer orG                    other "offline" hardware packages (PC-based packages H                    will be included in this), or the use of a host-basedI                    package such as the CDRECORD or CDWRITE13_VMS or other G                    utilities, OpenVMS ports of common open-source tools D                    made available by Dr. Eberhard Heuser-Hofmann and                    others.  E                    OpenVMS can read ODS-2, ODS-5, and ISO-9960 formatSF                    CD-ROMs. (If you are very careful, you can create aH                    dual-format CD-R; a CD-R with both ODS-2 and ISO-96607                    or both ODS-5 and ISO-9660 or both.)   C                    InfoServer hardware configurations are no longerPE                    available from HP, but may potentially be acquiredS:                    through other means; as used equipment.  R                    http://www.geocities.com/SiliconValley/Lakes/9999/vmscdwri.html  G                    Additional information is available at the followingc                    sites:n  :                    o  http://www.djesys.com/vms/cdrom.html  J                    o  http://www.cd-info.com/CDIC/Technology/CD-R/vms.html  8                    o  http://www.faqs.org/faqs/cdrom/cd-4                       recordable/part1/preamble.html  2                    o  http://www.tmesis.com/CDrom/  3                    o  http://www.tditx.com/~odsiso/o                      9-8 r  d                              Files        G                    U.S. Design offers a package that includes the tools I                    necessary to create a CD or DVD-R with either ISO-9660 E                    or ODS-2 format, for standalone CD-R/RW, DVD-R, ortH                    DVD+R/RW drives, for recent OpenVMS versions. Details$                    are available at:  .                    o  http://www.usdesign.com/  '           _____________________________ 2           9.7.1  CD and DVD notation, terminology?  D                    CD-ROM is pre-recorded Compact Disk media, and isE                    the original and oldest CD format. The original CD I                    media was physically stamped, a recording process thatEF                    is now largely reserved to the highest-volume media-                    reproduction requirements.   E                    CD-R is CD Recordable, a write-once storage medium,G                    that can be read by all but the oldest of CD drives;CH                    a format which can be read and often even recorded by%                    most CD-RW drives.$  H                    CD-RW is CD ReWritable, a format which is readable byI                    many CD drives and by most CD-R drives, and with mediaeH                    that can be recorded and re-recorded by CD-RW drives.  G                    CD media recording speeds are listed as multiples of_F                    150 kilobytes per second, so a 10X drive records atH                    1500 kilobytes (1.5 megabytes) per second. 600 MB (70H                    minutes) and 700 MB (80 minutes) recording capacitiesH                    are both widely available. The minutes designation isF                    derived from the traditional audio-format recording4                    capacity of the particular media.  H                    DVD-R/RW is the older of two common Digital VersatileF                    Disk recording formats, and the DVD-R Recordable orJ                    DVD-RW ReWritable media can be read by many DVD drives.E                    As with CD-R formats in older CD drives, older DVD.I                    and particularly first-generation DVD players may have 6                    problems reading this media format.  B                    DVD+R/RW is the newer of the two common DigitalB                    Versatile Disk recording formats, and the DVD+RD                    Recordable or DVD+RW ReWritable media can be readD                    by many DVD drives. Akin to DVD-R/RW media, older  J                                                                        9-9 o  o                              Files        H                    and particularly first-generation DVD drives can have6                    problems reading this media format.  F                    The DVD Plus-series drives and media tend to recordD                    faster than Minus drives, as (as of this writing)F                    the Plus (+) drives do not require an initial mediaI                    formatting pass and the Minus (-) drives do. While the G                    appropriate Plus (+) or Minus (-) DVD raw media must E                    be chosen for the particular DVD recorder (and DVD_H                    recording drives that are compatible with and capableE                    of using both Plus and Minus media are available),oE                    the resulting recorded media is generally readableoG                    (playable) in all recent DVD drives and DVD players,aH                    regardless of type. (Compatibility is best within theF                    same media-series devices of course, but be certainG                    to verify compatibility across devices regardless of F                    the particular device or particular recording media                    chosen.)   F                    Presently Plus (+) media is slightly more expensiveD                    than Minus (-), but with the prices of all CD andE                    all DVD media continuing to consistently fall, the I                    differences in DVD media costs are becoming irreleventAD                    for all but the production of huge volumes of DVD                    media.   J                    The rated DVD recording speeds are in multiples of 1353G                    kilobytes per second, thus a DVD 1X drive is roughlyaF                    equivalent to a CD 9X drive in I/O requirements and"                    transfer speed.  H                    DVD drive recording speed can and does vary. DVD diskJ                    drive recording speed is limited by the rated recordingG                    speed of the media used, so the slower (and cheaper)eI                    DVD media will not record any more quickly in a fasteraD                    drive. A 2.4X DVD drive loaded with 1X media will                     record at 1X.                                  9-10/                                   Files      D           __________________________________________________________>           9.8  What I/O transfer size limits exist in OpenVMS?  C                    The maximum transfer size is an attribute of the ?                    particular I/O device, controller and driverME                    combination; there is no inherent limit imposed byyH                    OpenVMS (other than the fact that, today, byte counts>                    and LBNs are generally limited to 32 bits).  F                    The maximum size of a device I/O request is limitedE                    by the value in UCB$L_MAXBCNT, which is set by the J                    device driver based on various factors. (Also check theJ                    setting of the MAXBUF system parameter for buffered I/O<                    transfers, and check the process quotas.)  J                    Currently, SCSI drivers limit I/O transfers to FE00(16)E                    bytes, 65024 bytes (decimal). The reasons for this C                    transfer size limitation are largely historical. I                    Similarly, DSSI devices are limited to the same value, G                    this for hardware-specific reasons. Transfers to HSC D                    and HSJ device controllers via the CI are limitedE                    to 1,048,576 bytes. Client MSCP-served devices arerE                    limited to 65535 bytes-to help ensure that the I/ODI                    fragmentation processing happens on the client and note(                    on the server system.  G                    Parts of the OpenVMS I/O subsystem are optimized forrE                    data transfers less than 64KB, because (obviously)sJ                    most I/O operations are (substantially) less than that.I                    OpenVMS can handle larger transfers, if the driver andi,                    the device can handle it.  5                    Also see Section 9.4, Section 9.5.   D           __________________________________________________________C           9.9  Can I use ODBC to connect to OpenVMS database files?   J                    Yes, you can use various available third-party packagesJ                    that permit remote ODBC clients to access RMS files and@                    various commercial databases via the network.  B                    For RMS, consider acquiring one of the packagesF                    available from EasySoft, Attunity Connect (formerlyC                    known as ISG Navigator), Oracle (DB Integrator),I-                    SolutionsIQ, and Synergex.   J                                                                       9-11 t  t                              Files        E                    For specific commercial databases (other than RMS, G                    of course), contact the database vendor directly for                     assistance.  D           __________________________________________________________I           9.10  If my disks are shown as VIOC Compatible, am I using XFC?   2                    Yes, you are using XFC caching.  I                    Disks that are using XFC caching use communication and F                    coordination protocols that are compatible with theF                    older VIOC caching implementation. With the initialD                    implementation of XFC on OpenVMS, you can use theE                    command SHOW MEMORY/CACHE to see no disks reportediF                    in full XFC mode; all disks shown will be listed in(                    VIOC Compatable Mode.  I                    If you have the OpenVMS system parameter VCC_FLAGS sethG                    to 2 and are using OpenVMS Alpha V7.3-1 or later, orlG                    are using OpenVMS Alpha V7.3 with the VMS73_XFC V2.0R7                    ECO kit or later, you are using XFC.g                                                                  9-12  o  w                    J                    _______________________________________________________  2           10       OpenVMS Programming Information      D           __________________________________________________________I           10.1  Modular Programming, Facility Prefixes and Symbol Naming?c  G                    Please first review the OpenVMS Programming Concepts G                    Manual and the Guide to Modular Programming manuals. F                    Both are available within the OpenVMS documentationE                    set, and provide details of the expected norms for $                    OpenVMS programs.  D                    o  Learn about the facility prefix, and use a theJ                       appropriate prefix uniformly throughout all externalG                       symbols, all logical names, and all files located F                       in shared directories. The prefix and the use ofI                       the dollar sign (<$>) and the underscore (<_>) helpeF                       avoid collisions with other products. Use of theE                       dollar sign is reserved to registered products.   G                    o  Please consider use of tools such as the FreewaresH                       SDL package, and the GNM package. These permit youI                       to generate include files and message documentation F                       akin to that of OpenVMS, providing users of your:                       product with a familiar environment.  I                    o  For product installations, consider use of the PCSIlJ                       installation utility, and provide a product-specificB                       configuration DCL command procedure (usuallyE                       SYS$MANAGER:prefix$CONFIG.COM) if configuration "                       is required.  ?                    o  The product startup file is usually named =                       SYS$STARTUP:prefix$STARTUP.COM, and the :                       shutdown file (if needed) is usually6                       SYS$STARTUP:prefix$SHUTDOWN.COM.  D                    OpenVMS provides a registry for facility prefixesE                    and for MESSAGE message compiler codes. To request E                    a prefix and a message facility code for a producttI                    you are reselling, send your request in a mail messageiI                    addressed to product[-at-sign-]hylndr.sqp.zko.dec.com,   J                                                                       10-1 _  _          2                    OpenVMS Programming Information        D                    requesting the submission form and details of the(                    registration process.  1                                              Notei  A                       Please do not request facility prefixes fore@                       products that local to your business, yourA                       site, or your system. Facility prefixes and A                       message codes and the facility registrationlA                       process are intended solely for HP productsoA                       and Partner Products (and yes, even OpenVMSfA                       Freeware packages) that will be distributed =                       across multiple OpenVMS customer sites.   C                    For a list of common coding bugs, please see the H                    remainder of this section of the FAQ and specificallyJ                    Section 10.24, please also see the Ask The Wizard topicF                    (1661), and for information on debugging an OpenVMS8                    application, please see topic (7552).  ;                    o  http://www.openvms.compaq.com/wizard/n  E                    o  http://www.openvms.compaq.com/wizard/wizard.zipn  F                    For additional information, please see Section 3.9.  D           __________________________________________________________?           10.2  Can I have a source code example of calling...?e  J                    Please use the available SEARCH command on OpenVMS, andE                    please remember to search the available resources,LD                    including the support databases and the newsgroupI                    archives. Please also realize that most OpenVMS system_J                    services use similar calling sequences, meaning that anJ                    example of calling sys$getjpi can be used as an exampleI                    for sys$getsyi and sys$getdvi. Students: please do not F                    expect folks to write your homework for you. As for$                    search resources:  4                    o  SEARCH SYS$EXAMPLES:*.* target  6                    o  SEARCH TCPIP$EXAMPLES:*.* target  -                    o  http://askq.compaq.com/   =                    o  http://www.openvms.compaq.com/freeware/   ,                    o  http://www.google.com/                      10-2  F  s          2                    OpenVMS Programming Information        C                    OpenVMS programming documentation, including thelH                    numerous example programs found in recent versions ofI                    the OpenVMS Programming Concepts manual, is available:   9                    o  http://www.openvms.compaq.com:8000/h  8                    o  http://www.openvms.compaq.com/doc/  ?                    o  http://www.openvms.compaq.com/commercial/   J                    As for details of argument passing, most OpenVMS systemE                    services and RTL routines pass string arguments by D                    descriptor. Languages which support native stringE                    data types create descriptors automatically; those E                    which do not (eg., C) require that you set them up G                    explicitly. For further details on using descriptors H                    and particularly for using descriptors from C, please%                    see Section 10.13.o  J                    There is extensive information available on how to callG                    OpenVMS system services and OpenVMS Run-Time LibraryeF                    routines, including examples in numerous languages.;                    Among the best available references are:s  1                    o  Your language's User Manualk  <                    o  OpenVMS Programming Environment Manual  9                    o  OpenVMS Programming Concepts Manual   F                    o  OpenVMS Programming Interfaces: Calling a System                       Routinet  .                    o  OpenVMS Calling Standard  J                    In addition, if you are a subscriber to the HP SoftwareJ                    Information Network (available to those with a softwareC                    support contract), the support database contains I                    hundreds of worked examples of calling system servicesCI                    and RTL routines, including the one that seems to tripI7                    up almost everyone, SMG$CREATE_MENU.e  G                    Arne Vajhj has put together a collection of OpenVMS_8                    example programs. It can be found at:  /                    o  ftp://ftp.hhs.dk/pub/vms/p  J                                                                       10-3 o  t          2                    OpenVMS Programming Information        F                    Additional information and examples for OpenVMS are!                    available via:r  ;                    o  http://www.openvms.compaq.com/wizard/   E                    o  http://www.openvms.compaq.com/wizard/wizard.zipt  J                    For additional information, please see Section 3.9. and                    via:   =                    o  http://www.openvms.compaq.com/freeware/   D           __________________________________________________________A           10.3  How do I get the arguments from the command line?   A                    If you're writing a program and want to accept I                    arguments from a foreign command, you can use LIB$GET_ I                    FOREIGN to get the command line and parse it yourself, J                    or if you're programming in C, use the normal argc/argv                    method.  D                    To write an application which uses the normal DCLF                    verb/qualifier/parameter syntax for invocation, seeF                    the description of the CLI$ routines in the OpenVMS>                    Callable Utility Routines Reference Manual.  F                    It is possible to write an application which can beE                    used both ways; if a DCL verb isn't used to invoke E                    the image, the application parses the command line J                    itself. One way to do this is to call CLI$GET_VALUE forI                    a required parameter. If it is not present (or you get J                    an error), call LIB$GET_FOREIGN to get the command line+                    and do the manual parse.e  (                    See also Section 8.1.  D           __________________________________________________________E           10.4  How do I get a formatted error message in a variable?r  C                    Use the SYS$PUTMSG system service with an actioncJ                    routine that stores the message line(s) in the variableE                    of your choice. Be sure the action routine returnsoC                    a "false" (low bit clear) function value so that E                    SYS$PUTMSG doesn't then try to display the messagekJ                    (unless you want it to.) See the description of $PUTMSGI                    in the System Services Reference Manual for an exampled.                    of using an action routine.                      10-4e t  e          2                    OpenVMS Programming Information      D           __________________________________________________________D           10.5  How do I link against SYS$SYSTEM:SYS.STB on an Alpha                 system?   I                    LINK/SYSEXE is the OpenVMS Alpha equivalent of linking F                    against SYS.STB. This links against the base image:%                    SYS$BASE_IMAGE.EXEl  G                    Also see Section 10.11, particularly for pointers todF                    the details on shareable images and shareable image                    creation.  D           __________________________________________________________@           10.6  How do I do a SET DEFAULT from inside a program?  C                    The problem is that SYS$SETDDIR only changes the H                    default directory - NOT the default disk. The defaultJ                    disk is determined by the logical SYS$DISK. If you wantI                    to change the default disk within a program, then calllF                    LIB$SET_LOGICAL to change the logical SYS$DISK. YouI                    will need to call both LIB$SET_LOGICAL and SYS$SETDDIRnI                    to change both default disk and the default directory!_  D           __________________________________________________________I           10.7  How do I turn my Fortran COMMON into a shareable image ony                 Alpha?  F                    You need to add SYMBOL_VECTOR=(<common-name>=PSECT)G                    to your options file. On OpenVMS VAX all OVR/REL/GBLiH                    psects were automatically exported into the shareableI                    image's Global Symbol Table. On OpenVMS Alpha you havekF                    to tell the linker that you want this done by meansI                    of the PSECT keyword in the SYMBOL_VECTOR options fileh                    statement.p  G                    This has several advantages over OpenVMS VAX. First,NI                    you don't have to worry about the address of the psectmD                    when you try to create a new, upwardly compatibleJ                    version of the shareable image. Second, you can controlE                    which psects, if any, are made visible outside the #                    shareable image.C  F                    By default, COMMON PSECTs in HP Fortran for OpenVMSH                    Alpha (as well as most other OpenVMS Alpha compilers)H                    are NOSHR. On VAX, the default was SHR which requiredE                    you to change the attribute to NOSHR if you wanteda  J                                                                       10-5               2                    OpenVMS Programming Information        H                    your COMMON to be in a shareable image but not write-H                    shared by all processes on the system. If you do want&                    write-sharing, use:  .                    CDEC$ PSECT common-name=SHR  I                    in the Fortran source code (the CDEC$ must be begin in J                    column 1) or a linker options file PSECT_ATTR statement<                    to set the COMMON PSECT attribute to SHR.  B                    For further information, see the Linker manual.  D           __________________________________________________________D           10.8  How do I convert between IEEE and VAX floating data?  F                    In OpenVMS V6.1 and later, the routine CVT$CONVERT_C                    FLOAT is documented in the LIB$ Run-Time Library C                    Reference Manual, and can perform floating pointvH                    conversions between any two of the following floatingH                    datatypes: VAX (F,D,G,H), little-endian IEEE (single,I                    double, quad), big-endian IEEE (single, double, quad), 0                    CRAY and IBM System\370, etc.  I                    HP Fortran (all OpenVMS platforms) has a feature whichuC                    will perform automatic conversion of unformattedeB                    data during input or output. See the HP FortranG                    documentation for information on "non-native data in @                    I/O" and the CONVERT= OPEN statement keyword.  B                    There are floating-point conversion source code<                    packages available for various platforms.  G                    For further floating-point related information, see:"  M                    o  http://www.hhs.dk/anonymous/pub/vms/collection/ieee.zipM  D           __________________________________________________________E           10.9  How do I get the argument count in a Fortran routine?a  E                    On VAX, many programmers would use a MACRO routine B                    which accessed the AP register of the caller toE                    get the address of the argument list and hence theeJ                    argument count. This was not guaranteed to work on VAX,F                    but usually did. However, it doesn't work at all onF                    OpenVMS Alpha, as there is no AP register. On AlphaJ                    systems, you must use a language's built-in function toJ                    retrieve the argument count, if any. In Fortran this is                      10-6                2                    OpenVMS Programming Information        G                    IARGCOUNT, which is also available in DEC Fortran on                     OpenVMS VAX.s  F                    Note that omitting arguments to Fortran routines isC                    non-standard and is unsupported. It will work intF                    many cases - read the DEC Fortran release notes for*                    additional information.  D           __________________________________________________________H           10.10  How do I get a unique system ID for licensing purposes?  B                    Many software developers desire to use a uniqueF                    hardware ID to "lock" a given copy of their productF                    to a specific system. Most VAX and Alpha systems doF                    not have a unique hardware-set "system ID" that canG                    be used for this purpose. HP OpenVMS products do not-E                    use hardware IDs in the licensing methods, as manyaI                    users consider a hardware-based licensing scheme to be J                    negative attribute when considering software purchases.  E                    HP OpenVMS uses a software-based system called theAG                    License Management Facility (LMF). This provides foreE                    software keys (Product Authorization Keys or PAKS)0J                    which support capacity and user-based license checking.D                    HP offers an LMF PAK Generator to CSA members-see                     Section 2.12.  I                    For information on licensing, please see Section 12.5.   G                    However, if a hardware-based method is required, the E                    most common method is based on an Ethernet adaptoreH                    hardware address. Sample source code for implementing(                    this is available at:  ;                    o  http://www.openvms.compaq.com/wizard/a  E                    o  http://www.openvms.compaq.com/wizard/wizard.zipi  F                    For additional information, please see Section 3.9.          J                                                                       10-7               2                    OpenVMS Programming Information      D           __________________________________________________________H           10.11  What is an executable, shareable, system or UWSS image?  B                    Executable code in OpenVMS typically resides inD                    an image-an image is a file-the file extension isG                    typically .EXE-that contains this code. Common typesfI                    of images include executable images, shareable images,a>                    system images, and protected (UWSS) images.  F                    Executable images are programs that can be directlyH                    executed. These images can grant enhanced privileges,G                    with an INSTALL of the image with /PRIVILEGE, or canoD                    grant enhanced access with the specification of aF                    subsystem identifier on the ACL associated with the                    image.   E                    Shareable images contain code executed indirectly, E                    these images are referenced from executable images G                    and/or from other shareable images. These images cansF                    not grant enhanced privileges, even with the use ofE                    INSTALL with /PRIVILEGE or a subsystem identifier. F                    These shareable images can be dynamically activatedE                    (a LINK that occurs at run-time) via the LIB$FIND_gD                    IMAGE_SYMBOL run-time library (RTL) routine. (SeeD                    `protected images' for information on `privileged&                    shareable images'.)  D                    System images are intended to run directly on theH                    VAX or Alpha hardware-these are normally used for theB                    kernel code that comprises an operating system.  J                    Protected images-also refered to as User-Written SystemI                    Services (UWSS), or as privileged shareable images-are H                    similiar in some ways to a standard shareable images,H                    but these images include a `change mode' handler, andI                    execute in an `inner' processor mode (privileged mode;mJ                    executive or kernel), and code executing in inner modesH                    has implicit SETPRV privilege. Must be INSTALLed withG                    /PROTECT. Note that inner-mode code has restrictions J                    around calling library routines, around calling variousF                    system services, and around calling code located in7                    other protected or shareable images.R                          10-8M               2                    OpenVMS Programming Information        I                    Loadable images and device drivers are images that canrG                    be used to add code into the OpenVMS kernel. Pseudo-DF                    device drivers are a particularly convenient way toF                    add executable code, with associated driver-definedF                    data structures, into the kernel. The pseudo-deviceI                    driver includes the UCB and DDB data structures, and aiI                    calling interface with support for both privileged andMH                    unprivileged access to the driver code via sys$qio[w]                    calls.r  D                    A cookbook approach to creating OpenVMS shareable2                    images is available at the URL:  ;                    o  http://www.openvms.compaq.com/wizard/   E                    o  http://www.openvms.compaq.com/wizard/wizard.zipe  F                    For additional information, please see Section 3.9.  D           __________________________________________________________8           10.12  How do I do a file copy from a program?  H                    There are several options available for copying filesG                    from within a program. Obvious choices include using G                    lib$spawn(),  system(), sys$sndjbc() or sys$creprc() J                    to invoke a DCL COPY command. Other common alternativesF                    include using the callable convert routines and theE                    BACKUP application programming interface (V7.1 and                     later).  D           __________________________________________________________&           10.13  What is a descriptor?  B                    A descriptor is a data structure that describesA                    a string or an array. Each descriptor contains H                    information that describes the type of the data beingD                    referenced, the size of the data, and the addressE                    of the data. It also includes a description of the J                    storage used for the data, typically static or dynamic.7                    Descriptors are passed by reference.'  C                    The following are examples of creating and usingrG                    descriptors in C, with the use of the angle brackets @                    normally expected by the C include statements=                    deliberately altered in deference to HTML:   J                                                                       10-9               2                    OpenVMS Programming Information        +                        #include {descrip.h}r0                        #include {lib$routines.h}*                        #include {stsdef.h}#                        int RetStat;d*                        char TxtBuf[TXTSIZ]8                        struct dsc$descriptor StaticDsc =C                          { 0, DSC$K_DTYPE_T, DSC$K_CLASS_S, NULL }; 5                        struct dsc$descriptor DynDsc =aC                          { 0, DSC$K_DTYPE_T, DSC$K_CLASS_D, NULL };s+                        int DynDscLen = 255;/C                        $DESCRIPTOR( ConstDsc, "This is a string" );   B                        /* finish setting up a static descriptor */<                        StaticDsc.dsc$w_length      = TXTSIZ;E                        StaticDsc.dsc$a_pointer     = (void *) TxtBuf;I  C                        /* finish setting up a dynamic descriptor *//E                        RetStat = lib$sget1_dd( &DynDscLen, &DynDsc ); =                        if ( !$VMS_STATUS_SUCCESS( RetStat ) ) (                          return RetStat;  8                        /* release the dynamic storage */:                        RetStat = lib$sfree1_dd( &DynDsc );;                        if (!$VMS_STATUS_SUCCESS( RetStat ))y(                          return RetStat;  F                    Static descriptors reference storage entirely underG                    application program control, and the contents of theiH                    descriptor data structure can be modified as requiredG                    (by the application). OpenVMS routines do not modify.I                    the contents of a static descriptor, nor do they alterrD                    the address or length values stored in the staticJ                    descriptor. (The term "static" refers to the descriptorE                    data structure, and not necessarily to the storage 1                    referenced by the descriptor.)   B                    Dynamic descriptors reference storage under theG                    control of the run-time library, and the contents of H                    a dynamic descriptor data structure-once initialized-I                    can only be modified under control of run-time library$J                    routines. The dynamic storage referenced by the dynamicI                    descriptor is allocated and maintained by the run-timeeF                    library routines. Various OpenVMS routines do alterJ                    the contents of the descriptor data structure, changingJ                    the value for the amount and the address of the storage                      10-10 e  1          2                    OpenVMS Programming Information        G                    associated with the dynamic descriptor, as required.eJ                    Routines can obviously access and alter the contents of<                    the storage referenced by the descriptor.  E                    OpenVMS languages that include support for stringsoD                    or arrays are expected to use descriptors for theE                    particular structure. Most OpenVMS languages, suchmA                    as Fortran and BASIC, use descriptors entirely-J                    transparently. Some, like DEC C, require the programmerD                    to explicitly create and maintain the descriptor.  E                    For further information on string descriptors, see G                    the OpenVMS Programming Concepts manual, part of thet-                    OpenVMS documentation set.   D                    Fortran defaults to passing integers by referenceD                    and characters by descriptor. The following sitesG                    discuss mixing Fortran and C source code in the same                     application:   I                    o  http://www.hhs.dk/anonymous/pub/vms/misc/FORTRAN_C_                        CALL.COM  F                    o  ftp://ftp.hhs.dk/pub/vms/misc/FORTRAN_C_CALL.COM  D           __________________________________________________________4           10.14  How many bytes are in a disk block?  C                    A disk block is the minimum unit of disk storagen)                    allocation in OpenVMS.   G                    Under OpenVMS VAX and OpenVMS Alpha, the disk volume G                    block size is consistent, with each block containing                     512 bytes.a  C                    The minimum disk allocation granularity actually H                    permissible (in the ODS-2 and ODS-5 volume structuresJ                    commonly used on OpenVMS) is determined on a per-volumeH                    basis, and is typically based on a combination of theG                    total number blocks on the disk volume and the totaleD                    size of the volume storage bitmap. The allocationE                    granularity is known as the volume cluster factor-cG                    the cluster factor is the number of blocks in a diskPH                    cluster, and it is the smallest number of blocks that@                    can be allocated on a particular disk volume.  J                                                                      10-11 c  i          2                    OpenVMS Programming Information        I                    Prior to OpenVMS V7.2, the maximum permissible size of G                    the bitmap requires larger cluster factors as volume H                    sizes increase. Starting with V7.2, the bitmap can beH                    larger, and cluster factors as small as one block can                    be used.e  E                    The number of bytes in a file can be determined by J                    multiplying the number of blocks allocated for the fileG                    times the number of bytes in a block. For sequentialpG                    files (only), the FFB (XAB$W_FFB, in the File HeaderfE                    XAB) value can be used to find out how much of the B                    last (XAB$L_EBK) block is used. FFB and EBK areD                    meaningful only for sequential files, and only inF                    a limited context-partial block allocations are notG                    permitted. For other file formats, the EOF marker is "                    not meaningful.  E                    Disk allocations always occur only in units of thedE                    cluster factors, which can be from one block up tosE                    (potentially) clusters of eighteen blocks or more,tH                    depending on the volume cluster factor. (OpenVMS V7.2G                    and later optionally provide for a cluster factor of E                    one up to volumes of approximately 137 gigabytes.)   A                    OpenVMS assumes that the device driver and thekI                    underlying storage device will present the file systemdJ                    with addressable units of storage of 512 bytes in size,H                    or the appearance of same. Various third-party CD-ROMH                    devices, for instance, support only 2048 byte blocks,F                    and such devices are incompatible with the standard*                    OpenVMS device drivers.  G                    To determine the number of bytes required for a filenG                    from DCL, one option uses the f$file_attributes itemhI                    EOF, multiplied by the size of a block in bytes (512). I                    This does not account for the unused space in the last H                    block of a sequential file, but it also does not haveF                    to differentiate sequential files from other files.                                10-12    i          2                    OpenVMS Programming Information      D           __________________________________________________________5           10.15  How many bytes are in a memory page?n  I                    A memory page is the minimum unit of memory allocationaE                    in OpenVMS. With OpenVMS VAX, the memory page size G                    matches the disk block size: it is always 512 bytes.   H                    With OpenVMS Alpha, the memory page size is variable,D                    and it can range from 8192 bytes (8 kilobytes) upG                    to 64 kilobytes. The current system page size can be H                    determined using the sys$getsyi or f$getsyi PAGE_SIZEI                    item. Programs with hardcoded constants for the memory G                    page size (or page alignment) should always assume a -                    page size of 64 kilobytes.)  I                    On OpenVMS Alpha, a 512 byte area of memory-equivilent I                    in size to an OpenVMS VAX memory page-is refered to as                     a pagelet.   D           __________________________________________________________B           10.16  How do I create a process under another username?  J                    Many server processes can operate within the context ofE                    the target user using privileges, using calls suchOD                    as sys$chkpro and (more commonly in this context)J                    sys$check_access as needed to determine if access wouldI                    be permitted for the specified user within the currenti"                    security model.  B                    With OpenVMS V6.2 and later, the persona systemE                    services (SYS$PERSONA_*) can be used to assume themJ                    persona of the specified user-these allow the server toJ                    operate as the specified user, in a controlled fashion.I                    The persona services can be used as a "wrapper" aroundCH                    a sys$creprc process creation call, as well-this willG                    create a seperate process entirely under the assumedS                    persona.   I                    Information on the persona system services is included B                    in the OpenVMS V6.2 new features documentation,D                    and in the OpenVMS V7.1 and later system servicesE                    documentation. These system services exist and are @                    supported in OpenVMS V6.2 and later releases.    J                                                                      10-13               2                    OpenVMS Programming Information        J                    Typical mechanisms for creating a process under another$                    username include:  E                    o  personna services around a sys$creprc call. Seep                       above.  =                    o  via DECnet task-to-task, using explicit F                       specification of username and password, or usingE                       a DECnet proxy. This creates a network-mode joblG                       under the target user. The network-mode job mighteI                       do little more than a RUN/DETACH of an image passed<E                       in via task-to-task-task-to-task communicationsoC                       are fully available using strictly DCL-to-DCL G                       processing, or using a compiled language and DCL,i                       etc.)F  B                    o  SUBMIT/USER, or the username argument on theJ                       sys$sndjbc call. This creates a batch-mode job underI                       the specified username. The batch-mode job might dosI                       little more than a RUN/DETACH of an image passed in &                       via a parameter.  J                    o  the UIC argument on the sys$creprc call. This mimicsJ                       the UIC of the target user, and is certainly not the7                       prefered mechanism for this task.r  -                    o  Via pseudo-terminals...   D                    There are likely a few other mechanisms around...I                    There are various tools available from DECUS and other J                    sources that allow various forms of user impersonation,F                    as well. These tools will require version-dependentJ                    kernel code and enhanced privileges for some of (or all(                    of) their operations.  D           __________________________________________________________B           10.17  Why do lib$spawn, lib$set_symbol fail in detached                  processes?d  E                    The processing within run-time library (RTL) calls H                    such as lib$attach, lib$disable_ctrl, lib$do_command,D                    lib$enable_ctrl, lib$get_symbol, lib$run_program,E                    lib$set_symbol, lib$set_logical, and lib$spawn, is F                    dependent on and requires the presence of a commandI                    language interpreter (CLI), such as DCL. Without a CLIeH                    present in the current process, these calls will fail                      10-14 y             2                    OpenVMS Programming Information        E                    with a "NOCLI, no CLI present to perform function"d                    error.   J                    Detached processes typically do not have a CLI present.  G                    In place of lib$spawn, sys$creprc can often be used. I                    The context of the parent process (symbols and logical I                    names) will not be propogated into the subprocess whensJ                    sys$creprc is used, though when there is no CLI presentE                    in the process this (lack of) propogation is moot.r  D                    To create a detached process with a CLI, you mustD                    specify LOGINOUT as the target image as discussedE                    elsewhere in the FAQ, or only use these calls (and/H                    any other calls requiring a CLI) from images that areH                    running in an "interactive", "batch", or "other" mode                    process.0  E                    Also note that the lib$spawn and the C system call J                    will fail in a CAPTIVE login environment. The lib$spawnJ                    call can be gotten to work in this environment with the5                    specification of the TRUSTED flag.   D           __________________________________________________________@           10.18  Where can I obtain Bliss, and the libraries and"                  supporting files?  E                    The Bliss language compilers and documentation aregC                    available on the OpenVMS Freeware distributions.p  I                    Bliss language source code that contains the followinge                    statement:o  7                      LIBRARY 'SYS$LIBRARY:STARLET.L32';E  @                    or similar requires the presence of the BlissG                    libraries. These libraries are created on the targetaF                    system using the Bliss require files, and are built6                    using the following Bliss commands:  I                    STARLET.L32 contains the public interfaces to OpenVMS:n  H                        $ BLISS /LIBRARY=SYS$COMMON:[SYSLIB]STARLET.L32 -2                            SYS$LIBRARY:STARLET.REQ  J                                                                      10-15 o  v          2                    OpenVMS Programming Information        J                    LIB.L32 contains both the public and private interfaces                    to OpenVMS:  D                        $ BLISS /LIBRARY=SYS$COMMON:[SYSLIB]LIB.L32 -F                            SYS$LIBRARY:LIB.REQ+SYS$LIBRARY:STARLET.REQ  E                    The equivilent files for Bliss64 are created with:y  G                        $ BLISS/A64/LIBRARY=SYS$COMMON:[SYSLIB]LIB.L64 -oF                            SYS$LIBRARY:LIB.R64+STARLET.REQ+STARLET.R64K                        $ BLISS/A64/LIBRARY=SYS$COMMON:[SYSLIB]STARLET.L64 -l2                            SYS$LIBRARY:STARLET.R64  C                    Some Bliss code may also require the OpenVMS VAXoF                    architecture flags. The following is the equivilent5                    of the Alpha ARCH_DEFS.REQ module:r                      !J                    ! This is the OpenVMS VAX version of ARCH_DEFS.REQ, andM                    ! contains the architectural definitions for conditionally L                    ! compiling OpenVMS Bliss sources for use on VAX systems.M                    ! (If you should encounter compilation errors here, please G                    ! seriously consider upgrading your Bliss compiler.)                     !&                    MACRO VAXPAGE = 1%;&                    MACRO BIGPAGE = 0%;                    !N                    MACRO VAX =                     ! = 1 if compiled BLISS/VAXR                            %BLISS(BLISS32V)%;      ! = 0 if not compiled BLISS/VAX  b                    MACRO EVAX =                    ! = 1 if compiled BLISS/E* (Obsolete, old name)_                            (%BLISS(BLISS32E) OR %BLISS(BLISS64E))%; ! = 0 if compiled /VAX /Inn   ]                    MACRO ALPHA =                   ! = 1 if compiled BLISS/E* (New arch name)I_                            (%BLISS(BLISS32E) OR %BLISS(BLISS64E))%; ! = 0 if compiled /VAX /Inn   ]                    MACRO IA64 =                    ! = 1 if compiled BLISS/I* (New arch name)Pb                            (%BLISS(BLISS32I) OR %BLISS(BLISS64I))%; ! = 0 if compiled /VAX or /Ann  &                    MACRO ADDRESSBITS =V                            %BPADDR%;               ! = 32 or 64 based on compiler used  G                    Some Bliss code may require the definition files fordF                    the OpenVMS older LIBRTL routine lib$tparse, or the.                    newer lib$table_parse call:  G                        $ BLISS /LIBRARY=SYS$COMMON:[SYSLIB]TPAMAC.L32 -_1                            SYS$LIBRARY:TPAMAC.REQa                      10-16               2                    OpenVMS Programming Information      D           __________________________________________________________9           10.19  How can I open a file for shared access?d  J                    When creating a file, it is often useful to allow otherH                    applications and utilities-such as TYPE-to share readF                    access to the file. This permits you to examine the8                    contents of a log file, for instance.  I                    A C source example that demonstrates how to do this is J                    available in topic (2867) in the OpenVMS Ask The Wizard                    area:  ;                    o  http://www.openvms.compaq.com/wizard/e  E                    o  http://www.openvms.compaq.com/wizard/wizard.zipa  F                    For additional information, please see Section 3.9.  F                    Depending on the environment, you may need to use CI                    calls such as fsync and fflush, and-in specific cases-I,                    the setvbuf(_IONBF) call.  D           __________________________________________________________G           10.20  How can I have common sources for messages, constants?   D                    Use the GNM tools on the OpenVMS Freeware to haveB                    common sources for MSG (message) files and SDMLC                    (Document) documentation files. Use the DOCUMENTaE                    command to convert the SDML documentation into theeG                    necessary formats (Text, Postscript, HTML, etc). UseaH                    the MESSAGE/SDL tool (latent in OpenVMS) to create anH                    SDL file based on the messages. Then use the SDL toolI                    (available on the OpenVMS Freeware) to convert the SDLlJ                    file into language-specific definitions. (There is alsoF                    a converter around to convert SDL into SDML, if youG                    want to get pictures of the data structures for your_"                    documentation.)  D           __________________________________________________________?           10.21  How do I activate the OpenVMS Debugger from ann                  application?S  ,                    #include {lib$routines.h}%                    #include {ssdef.h} &                    #include {string.h}  J                                                                      10-17 s  d          2                    OpenVMS Programming Information                            main()_                        {6                        char ascic_debug_commands[128];<                        char *dbgcmd = "*show calls;go;exit";  >                        strcpy( ascic_debug_commands, dbgcmd );J                        ascic_debug_commands[0] = (char) strlen( dbgcmd ) -           1;  D                        lib$signal(SS$_DEBUG,1,ascic_debug_commands);                           return 1;                        }  D           __________________________________________________________*           10.22  Dealing with Endian-ness?  H                    OpenVMS on VAX, OpenVMS on Alpha and OpenVMS on IntelD                    IA-64 platforms (as well as all Microsoft WindowsE                    implementations and platforms) all support and all E                    use the little-endian byte ordering. Certain AlphaoG                    microprocessors and certain Intel Itanium processorslA                    can be configured to operate in big-endian andeJ                    potentially in bi-endian mode. HP-UX typically operates                    big-endian.  G                    With little-endian byte order, the least significant H                    byte is always the first byte; the byte at the lowestC                    address. With big-endian byte ordering, the byteoJ                    storage order in memory is dependent on the size of theH                    data (byte, word, longword) that is being referenced.  F                    Endian-ness is a problem has been solved many times@                    before. Some of the typical solutions include@                    htonl/htons and ntohl/ntohs in the standard CE                    library and the TCP/IP Services XDR (eXternal DataVF                    Representation) libraries. One of the more recentlyE                    introduced network formats, and one that is seeingeB                    extensive press and marketing coverage, is XML.                              10-18               2                    OpenVMS Programming Information      D           __________________________________________________________7           10.23  How to resolve LINK-I-DATMISCH errors?-  D                    The message LINK-I-DATMISCH is informational, andH                    indicates that the version of the specified shareableF                    image found in the system shareable image directoryI                    does not match the version of the shareable image thatfF                    was originally loaded into IMAGELIB.OLB, one of theF                    OpenVMS libraries typically searched by the LINKER.  I                    From a privileged username, you can usually completely_=                    repair this via the following DCL command:l  T                    $ LIB/REPLACE/SHARE SYS$LIBRARY:IMAGELIB.OLB SYS$SHARE:LIBRTL.EXE  E                    This command assumes that the shareable image that H                    was found in the SYS$SHARE: area is valid and upward-I                    compatiable, and that the image has simply replaced an @                    older version without also updating IMAGELIB.  D           __________________________________________________________I           10.24  Compaq C and other OpenVMS C Programming Considerations?   E                    VAX C V3.2 was released for OpenVMS VAX systems inwI                    1991. DEC C V4.0 replaced VAX C V3.2 in 1993 as the HPuG                    C compiler for OpenVMS VAX systems. HP C is the ANSInG                    C compiler for OpenVMS Alpha systems. VAX C predates G                    the ANSI C standards, and has various areas that are-J                    not compliant with ANSI C requirements. HP C is an ANSIH                    C compiler, and can also compile most VAX C code whenI                    /STANDARD=VAXC is specified. Versions of this compilermI                    between V3.2 and V6.5 (exclusive) were known as DEC C,_+                    DIGITAL C, and Compaq C.g  J                    Both compilers can be installed at the same time on theI                    same OpenVMS VAX system, allowing a migration from VAX J                    C to DEC C, and allowing the same DEC C code to be used4                    on OpenVMS VAX and OpenVMS Alpha.  E                    The system manager can choose the system default CtJ                    compiler when HP C is installed on a system with VAX C,H                    and a C programmer can explicitly select the required=                    compiler for a any particular compilation.   H                    A current "C" license PAK allows access to both VAX C;                    and HP C on the same OpenVMS VAX system.r  J                                                                      10-19    D          2                    OpenVMS Programming Information        H                    Various HP C versions can be installed on OpenVMS VAXH                    V5.5-2 and later. OpenVMS VAX releases such as V5.5-2G                    and V6.0 will require the installation of a HP C RTLoF                    kit, a kit that is included with the HP C compiler.G                    OpenVMS VAX versions V6.1 and later do not require acH                    seperate RTL kit, but HP C RTL ECO kits are availableF                    to resolve problems found with the C RTL on various$                    OpenVMS releases.  H                    With HP C, for automatic resolution of the standard CJ                    library routines by the LINKER utility, use the /PREFIXJ                    qualifier, such as /PREFIX=ALL_ENTRIES. If a particularE                    application program replaces an existing C library H                    routine, use /PREFIX=(ALL_ENTRIES,EXCEPT=(...)). (VAXH                    C required explicit specification of an RTL shareable>                    image or C object library during the link.)  H                    When the /PREFIX is requested, the compiler generatesI                    a "decc$" prefix on the specified symbols. This prefixsD                    allows the LINKER to resolve the external symbolsG                    against the symbols present in the DECC$SHR library.iG                    The DECC$SHR library is included in the IMAGELIB.OLBeG                    shareable image library, and IMAGELIB is searched by H                    default when any program (written in any language) isG                    LINKed. Because the standard C library routine names H                    are very likely to match application routines writtenI                    in other languages, a prefix "decc$" is added to the C/F                    symbol names to assure their uniqueness; to preventD                    symbol naming conflicts. C programs, however, canI                    sometimes have private libraries for various purposes, D                    and the external routines share the same names asF                    the library routines. (This is not recommended, butJ                    there are applications around that use this technique.)H                    Thus the need to explicity specify whether or not theE                    "decc$" prefix should be prepended to the external 0                    symbol names by the compiler.  B                    The qualifiers, and most (all?) with associatedF                    pragmas, that may be of interest when migrating VAX*                    C code to HP C include:  )                    o  /PREFIX=ALL_ENTRIES                         10-20    n          2                    OpenVMS Programming Information        C                       As mentioned above. Failure to specificy thiswE                       qualifier can cause the compiler to not add thetF                       prefixes for the names of the C library routinesF                       into the references placed in the object module,D                       which can in turn cause problems resolving theE                       external symbols in the library when the object %                       code is linked.   6                    o  /ASSUME=WRITABLE_STRING_LITERALS  I                       Some VAX C programs erroneously write to the string C                       literals. By default, HP C does not allow thea*                       constants to change.  $                    o  /SHARE_GLOBALS  F                       Enables sharing ("shr") of globals and of externC                       variables. HP C sets externs as non-shareable 0                       ("noshr"), VAX C as "shr".  /                    o  /EXTERN_MODE=COMMON_BLOCKe  C                       VAX C assumes common block model for externale                       linkages.   +                    o  /[NO]MEMBER_ALIGNMENTU  J                       Refers to the padding placed between member elementsG                       within a struct. Disabling member alignment packssA                       the data more tightly into memory, but thisaE                       packaging has performance implications, both onsC                       OpenVMS VAX and particularly on OpenVMS Alphaa                       systems.  C                    Permit structure members to be naturally alignedi@                    whenever possible, and avoid using /NOMEMBER_F                    ALIGNMENT. If you need to disable member alignment,G                    use the equivilent #pragma to designate the specificdJ                    structures. The alignment of structure members normallyD                    only comes into play with specific unaligned dataD                    structures-such as the sys$creprc quota itemlist-H                    and with data structures that are using data that wasG                    organized by a system using byte or other non-memberr                    alignment.   J                                                                      10-21               2                    OpenVMS Programming Information        J                    Versions of HP C such as V6.0 include the capability toH                    extract the contents of the standard header librariesF                    into directories such as SYS$SYSROOT:[DECC$LIB...],H                    and provide various logical names that can be definedG                    to control library searches. With HP C versions suchRH                    as V6.0, the default operations of the compiler matchH                    the expectations of most OpenVMS programmers, withoutF                    requiring any definitions of site-specific library-F                    related logical names. (And logical names left fromH                    older DEC C versions can sometimes cause the compiler3                    troubles locating header files.)s  D                    HP C V5.6 and later include a backport library, aC                    mechanism by which HP C running on older OpenVMSeG                    releases can gain access to newer RTL routines addedeI                    to the RTL in later OpenVMS releases-the language RTLsdH                    ship with OpenVMS itself, and not with the compilers.  C                    Example C code is available in SYS$EXAMPLES:, in_B                    DECW$EXAMPLES (when the DECwindows examples areG                    installed), in TCPIP$SERVICES (or on older releases, J                    UCX$EXAMPLES) when HP TCP/IP Services is installed), onA                    the Freeware CD-ROMs, and at web sites such as   ;                    o  http://www.openvms.compaq.com/wizard/e  E                    o  http://www.openvms.compaq.com/wizard/wizard.zip   F                    For additional information, please see Section 3.9.  '           _____________________________e(           10.24.1  Other common C issues  H                    The localtime()  function and various other functionsI                    maintain the number of years since 1900 in the "structxJ                    tm" structure member tm_year. This field will contain aI                    value of 100 in the year 2000, 101 for 2001, etc., and I                    the yearly incrementation of this field is expected tor                    continue.  H                    The C epoch typically uses a longword (known as time_E                    t) to contain the number of seconds since midnight G                    on 1-Jan-1970. At the current rate of consumption of G                    seconds, this longword is expected to overflow (when F                    interpreted as a signed longword) circa 03:14:07 onF                    19-Jan-2038 (GMT), as this time is circa 0x7FFFFFFF                      10-22 s             2                    OpenVMS Programming Information        B                    seconds since the C base date. (The most commonE                    solution is to ensure that time_t is an unsigned.)a  D                    If C does not correctly handle the display of theF                    local system time, then check the UTC configurationJ                    on OpenVMS-the most common symptom of this is a skew ofH                    one hour (or whatever the local daylight savings timeI                    change might be). This skew can be caused by incorrect F                    handling of the "is_dst" setting in the applicationH                    program, or by an incorrect OpenVMS UTC configurationB                    on the local system. (See section Section 4.4.)  G                    Floating point is prohibited in OpenVMS Alpha inner- F                    mode (privileged) code, and in any process or otherF                    execution context that does not have floating pointE                    enabled. C programmers developing and working with.I                    OpenVMS Alpha high-IPL kernel-mode code such as devicerI                    drivers will want to become familiar with the floating J                    point processing available in the environment, and withJ                    the C compiler qualifier /INSTRUCTION_SET=[NO]FLOATING_H                    POINT. Device drivers and other similar kernel-mode CH                    code must be compiled with /INSTRUCTION_SET=FLOATING_9                    POINT and /EXTERN_MODEL=STRICT_REFDEF.a  F                    Additionally, the SYS$LIBRARY:SYS$LIB_C.TLB/LIBRARYH                    parameter will be needed to be appended to the moduleI                    specification or declared via the C compiler's include H                    library logical name mechanism when the C compiler isI                    resolving kernel-mode data structures and definitions.tF                    This library contains OpenVMS kernel-mode and otherC                    system declaractions, and particularly a mixture D                    of undocumented definitions and declarations, andE                    particularly definitions and declarations that arecF                    subject to change (and that can accordingly lead toD                    requirements for the recompilation of application                    code).   G                    When sharing variables with other languages, here is ,                    some example HP C code...          J                                                                      10-23               2                    OpenVMS Programming Information                                  ...2                          #pragma extern_model save;                          #pragma extern_model strict_refdef 4                          extern int   VMS$GL_FLAVOR;5                          #pragma extern_model restorei                          ...  D                    and here is some associated example Bliss code...                            ...!                          EXTERNAL *                             VMS$GL_FLAVOR,                          ....s  '           _____________________________e*           10.24.2  Other common C++ issues  B                    HP C++ (a separate compiler from HP C) providesC                    both symbol mangling and symbol decoration. SometE                    of the details of working with longer symbol names_B                    and the resulting symbol name mangling in mixedD                    language environments are listed in the shareableG                    image cookbook, and in the C++ documentation. Symbol G                    name decoration permits the overloading of functions C                    (by adding characters to the external symbol fornD                    the function to indicate the function return typeD                    and the argument data types involved), and mixed-H                    language external references can and often do need toI                    disable this decoration via the extern "C" declaration                     mechanism:t  #                          extern "C"m                            {;                            extern int ExternSymbol(void *); @                            extern int OtherExternSymbol(void *);                            }  I                    Also see Section 14.7 for information on /ARCHITECTURE &                    and /OPTIMIZE=TUNE.  H                    See Section 10.17 for information on the C system and>                    the lib$spawn call in CAPTIVE environments.                        10-24               2                    OpenVMS Programming Information        D                    Constructs such as the order of incrementation orF                    decrementation and the order of argument processingJ                    within an argument list are all implementation-defined.?                    This means that C coding constructs such as:                           i = i++; "                        a[i] = i++;)                        foo( i, i++, --i);d  I                    are undefined and can have (adverse) implications wheniI                    porting the C code to another C compiler or to anotherpI                    platform. In general, any combination of ++, -, =, +=, J                    -=, *=, etc operators that will cause the same value toJ                    be modified multiple times (between what the ANSI/ISO CJ                    standard calls "sequence points") produce undefined and3                    implementation-specific results.   E                    Within C, the following are the "sequence points": F                    the ";" at the end of a C statment, the ||, &&, ?:,F                    and comma operators, and a call to a function. NoteH                    specifically that = is NOT a sequence point, and thatG                    the individual arguments contained within a functionoJ                    argument list can be processed from right to left, from8                    left to right, or at any random whim.  E                    HP C for OpenVMS VAX (formerly DEC C) and VAX C doV4                    differ in the related processing.  F                    So you are looking for OpenVMS-specific definitions#                    (include files)?s  @                    UCBDEF.H, PCBDEF.H and other OpenVMS-specificG                    definitions-these are considered part of OpenVMS andnF                    not part of the C compiler kit-are available on all1                    recent OpenVMS Alpha releases.   D                    To reference the version-dependent symbol libraryH                    sys$share:sys$lib_c.tlb, use a command similar to the-                    following for compilation:   9                    $ CC sourcea+SYS$LIBRARY:SYS$LIB_C/LIB   I                    You can also define DECC$TEXT_LIBRARY to reference the                     library.u  C                    You will want to review the Programming ConceptsiH                    manual, and specifically take a quick look at Chapter                    21.  J                                                                      10-25 _  _          2                    OpenVMS Programming Information        G                    And some general background: the STARLET definitionsuG                    (and thus the sys$starlet_c.tlb library) contain the F                    symbols and the definitions that are independent ofE                    the OpenVMS version. The LIB definitions (and thustF                    sys$lib_c) contain symbols and definitions that canI                    be dependent on the OpenVMS version. You won't need torI                    rebuild your code after an OpenVMS upgrade if you haveeH                    included definitions from STARLET. The same cannot beI                    said for some of the definitions in LIB-you might neednG                    to rebuild your code. (The UCB structure can and has)B                    changed from release to release, for instance.)  I                    Recent versions of C automatically search sys$starlet_eD                    c.tlb. Explicit specification of sys$lib_c.tlb is                    required.  E                    Also see the Ask The Wizard website topics (2486),e&                    (3803), and (1661):  ;                    o  http://www.openvms.compaq.com/wizard/   E                    o  http://www.openvms.compaq.com/wizard/wizard.zipa  F                    For additional information, please see Section 3.9.  A                    See Section 9.5 for information on the C off_t H                    limitations, resolved in OpenVMS V7.3-1 and later andG                    in ECO kits available for specific OpenVMS releases. I                    The use of a longword for off_t restricts applicationsaG                    using native C I/O to file sizes of two gigabytes ortI                    less, or these applications must use native RMS or XQPl1                    calls for specific operations.e  D           __________________________________________________________<           10.25  Status of Programming Tools on OpenVMS VAX?  G                    DECthreads V7.3 and the HP C compiler (also known asoE                    Compaq C and DEC C) V6.4 are presently expected tosE                    be the last updates and the last releases of thesetH                    development packages for use on OpenVMS VAX. The run-G                    time support for both DECthreads (CMA$RTL) and for C G                    (DECC$CRTL) will continue to be maintained, and will E                    continue to be available on OpenVMS VAX. The VAX C3H                    V3.2 compiler is the final VAX C compiler release forH                    OpenVMS VAX, and the VAX C Run-Time Library (VAXCRTL)6                    will also continue to be available.                      10-26    u          2                    OpenVMS Programming Information        ?                    New development and new features and product F                    enhancements continue for the OpenVMS Alpha and the<                    OpenVMS IA-64 DECthreads and C compilers.                                                                                  J                                                                      10-27                         J                    _______________________________________________________             11       DECwindows       D           __________________________________________________________A           11.1  How do I let someone else display something on mys                 workstation?  I                    On a workstation, you will want to use the "Customize" A                    menu of the session manager utility and select C                    "Security". When the pop-up box appears, you candI                    select the host node, username, and tranport that willIF                    allow you to launch an application that targets the'                    workstation display.y  B                    If this does not provide you with access to the:                    display, You need a checklist of sorts:  C                    o  Make sure that you've specified the X-windows C                       "display" correctly on the remote host. For a J                       DECnet transport, the specification uses two colons,H                       while the TCP/IP transport typically uses one. TheF                       X Windows server and the X Windows screen followH                       the host specification, delimited by a period. For                       example:  J           ________________________________________________________________0           Table 11-1  X Windows Display Commands  J                    _______________________________________________________J                    Shell_____Command______________________________________                      csh  <                              # setenv DISPLAY vms.domain:0.0                      sh and ksh   H                              # $ DISPLAY=vms.domain:0.0 ; export DISPLAY                      DCL  C                              $ SET DISPLAY/CREATE/NODE=vms.domain -nJ           ___________________/TRANSPORT=TCPIP/SERVER=server/SCREEN=screen_  E                    o  If you have verified the command is correct and G                       things are still not working, ensure the Security F                       settings on the OpenVMS host side will allow the  J                                                                       11-1 o  n                              DECwindowst        G                       incoming connection: Pull down the "Options" menubJ                       in the Session Manager, and select "Security...". IfJ                       you do not find your host and username and transportI                       listed among the authorized users, you will need toe#                       add an entry.   I                      o  There are various transports available, including F                         LOCAL, DECNET, LAT, and TCPIP. You must SelectA                         the transport appropriate to the incoming #                         connection."  D                      o  If the transport is "DECnet", do NOT add the;                         double colon (::) to the node name.   D                      o  If the transport is "TCPIP", "Username" mustG                         be an asterisk (*). Why? Because unlike DECnet,tG                         the TCP/IP protocol does not provide the remote_H                         username information in the incoming connection.  G                      o  If the connection is "TCPIP", it is best to usenC                         a full domain name (e.g. Node.Subd.Domain).eC                         However, you may have to use the IP addresssC                         itself, if your host does not have a way tonD                         resolve the address via DNS. If you have theH                         luxury of fixed addresses (eg: you are not usingH                         DHCP), then it can be helpful to add two entriesI                         for each TCP/IP host, one that specifies the hostlE                         name and one that specifies the host address.g  F                      o  There are various TCP/IP packages for OpenVMS,B                         and you must use syntax appropriate to the,                         transport installed.  D                      o  If a TCP/IP connection is still not working,C                         ensure that the transport you want has been >                         activated for use with DECwindows. SeeG                         Section 11.15 for details of configuring TCP/IP '                         as a transport.   G                    o  There is a log file created in SYS$MANAGER: which C                       can tell you which transports are loaded, andeH                       also tell you what connect attempts were rejected,F                       including showing what the presented credentialsC                       were. This file is SYS$MANAGER:DECW$SERVER_0_ G                       ERROR.LOG, although the 0 could be another number H                       if you have multiple servers on the workstation. I                      11-2M A                                 DECwindowse        I                       have found this file to be very useful for trackingrF                       down what needs to be put in the Session Manager'                       Security entries.   D           __________________________________________________________A           11.2  How do I create a display on another workstation?t  I                    To create a display from an OpenVMS host to a remote XpJ                    Windows display, use one of the following DCL commands:  S                    $ SET DISPLAY /CREATE /TRANSPORT=net_transport /NODE=remote_nodeMI                    $ SET DISPLAY /CREATE /TRANSPORT=LAT /NODE=remote_node L                    $ SET DISPLAY /CREATE /TRANSPORT=DECnet /NODE=remote_nodeK                    $ SET DISPLAY /CREATE /TRANSPORT=TCPIP /NODE=remote_nodeO  J                    Note that LAT is typically used only for the VXT seriesD                    X Windows terminals, but it can also be used fromJ                    OpenVMS to OpenVMS systems on various OpenVMS releases,J                    such as on OpenVMS Alpha V6.1 and later. For details onG                    configuring the TCP/IP transport, see Section 11.15.   H                    If you are interested in X Windows terminals and haveH                    an older VAXstation system around, please see the EWS,                    package on Freeware V5.0.  D           __________________________________________________________F           11.3  How can I get the information from SHOW DISPLAY into a                 symbol?r  E                    Use the undocumented SHOW DISPLAY/SYMBOL, and thenBI                    reference the symbols DECW$DISPLAY_NODE, DECW$DISPLAY_lC                    SCREEN, DECW$DISPLAY_SERVER and/or DECW$DISPLAY_A                    TRANSPORT.   A                    An example of calling the underlying (and also F                    undocumented) sys$qio programming interface for the4                    WSDRIVER (WSAn:) is available at:  Z                    http://www.openvms.compaq.com/freeware/srh_examples/DECUS_UNDOC_CLINIC/          J                                                                       11-3 t  t                              DECwindows       D           __________________________________________________________8           11.4  How do I get a log of a DECterm session?  E                    If you are working from a Decterm, you can use the G                    AutoPrint feature. Choose the "Printer..." menu item H                    from the "Options" menu, set the printing destinationH                    to the name of the file you want, and set "Auto Print7                    Mode". You are now free to continue.p  D                    It should be noted that all of the characters andH                    escape sequences are captured, but if you display theE                    resulting log file on a DECterm, then you will see.9                    exactly what was originally displayed._  D           __________________________________________________________A           11.5  Why does the DELETE key delete forward instead ofM                 backward?   E                    This involves the Motif virtual key bindings. When E                    a Motif application starts, it looks at the vendor H                    string returned in the display connection informationI                    and attempts to match the string to a table of virtualt                    bindings.  @                    You can override the default bindings in yourG                    decw$xdefaults.dat file. Here is the entry you wouldS8                    make to get the default VMS bindings.                                                        11-4     a                              DECwindowsL        ,                    *defaultVirtualBindings:\*                     osfCancel :  <>F11 \n\)                     osfLeft :  <>Left \n\_'                     osfUp  :  <>Up  \n\_+                     osfRight :  <>Right \n\e)                     osfDown :  <>Down \n\ 0                     osfEndLine :Alt  <>Right \n\1                     osfBeginLine :Alt  <>Left \n\ ,                     osfPageUp :  <>Prior \n\-                     osfPageDown :  <>Next \n\ 2                     osfDelete :Shift  <>Delete \n\.                     osfUndo :Alt  <>Delete \n\0                     osfBackSpace :  <>Delete \n\0                     osfAddMode :Shift  <>F8  \n\)                     osfHelp :  <>Help \n\d(                     osfMenu :  <>F4  \n\+                     osfMenuBar :  <>F10 \n\d-                     osfSelect :  <>Select \n\m1                     osfActivate :  <>KP_Enter \n\ 1                     osfCopy :Shift  <>DRemove \n\i,                     osfCut  :  <>DRemove \n\(                     osfPaste :  <>Insert                      To merge:  2                    $ xrdb :== $decw$utils:xrdb.exe:                    $ xrdb -nocpp -merge decw$xdefaults.dat  F                    Also note that the DECW$UTILS:DECW$DEFINE_UTILS.COMH                    procedure can be used to establish the xrdb and other                    symbols.l  G                    Also see the DECxterm directory of Freeware V5.0 for E                    details on connecting to OpenVMS from various UNIXl                    platforms.f  D           __________________________________________________________5           11.6  Why is DECwindows Motif not starting?   D                    First check to see if there is a graphics device,E                    usually a G* device. (eg: On a DEC 2000 model 300, G                    use the command SHOW DEVICE GQ) If you do not find ao#                    graphics device:   D                    o  OpenVMS has failed to find the appropriate IRQC                       information for an EISA graphics card (on the   J                                                                       11-5    f                              DECwindowse        G                       DEC 2000 series) such as the HP (Compaq) QVision, G                       and did not autoconfigure it. Run the correct ECU F                       (for Tru64 UNIX and OpenVMS) and reboot. This is;                       necessary only on EISA-based systems.   D                    o  You have an EISA-based system (such as the DECC                       2000 model 300) and do not have a HP (Compaq)SH                       QVision video card. This EISA graphics card shouldF                       have Compaq printed on it, and identifies itselfD                       as a CPQ3011 or a CPQ3111. If it is not one ofC                       these two EISA devices, then OpenVMS does notsD                       support it. (There are no other supported EISAJ                       graphics controllers, and EISA graphics are normallyF                       used with DECwindows only on the DEC 2000 series                       systems.)   D                    o  You have a PCI-based system, and do not have aI                       supported graphics controller-examples of supported 8                       controllers include the following:  '                      o  PowerStorm 3D30B  '                      o  PowerStorm 4D20   &                      o  PowerStorm 300  &                      o  PowerStorm 350  +                      o  ELSA GLoria Synergya  )                      o  3DLabs Oxygen VX1n  I                       See Section 5.15 for further information on some oft1                       these graphics controllers._  C                    o  You have booted the system minimally, or haveaE                       otherwise disabled the device autoconfiguration                        process.  <                    If there is a G* graphics device present:  ?                    o  There may have been a severe error in theo>                       DECwindows startup. Type the contents ofA                       SYS$MANAGER:DECW$SERVER_0_ERROR.LOG for any @                       information on errors starting the server.                      11-6t N  N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faqeN  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.com    ------------------------------  # Date: Thu, 03 Jul 2003 17:15:07 GMT 2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman); Subject: OpenVMS Frequently Asked Questions (FAQ), Part 6/9l2 Message-ID: <vwZMa.3896$bl3.1879@news.cpqcorp.net>    o                              DECwindows         F                    o  The system parameter WINDOW_SYSTEM is not set toH                       1. While this was a common way for system managersE                       to disable the DECwindows server startup, it is E                       not particularly reliable as DECwindows can now -                       "correct" this setting.o  F                       If you really do not want an OpenVMS system withE                       workstation hardware to bootstrap and configure-@                       itself as a workstation, add the following3                       definition to SYLOGICALS.COM:o  G                       $ DEFINE/SYSTEM/EXEC DECW$IGNORE_WORKSTATION TRUEe  G                    o  You may not have a valid DECwindows Motif licensetG                       loaded. To check for the two most common types oflF                       Motif product authorization keys (PAKs), use the-                       following DCL commands:   2                       $ LICENSE LIST DW-MOTIF/FULL6                       $ LICENSE LIST NET-APP-SUP*/FULL  F                       and examine the information displayed. Make sureF                       that one of these licenses is present, valid and                       active.L  E                    o  Check that the DECW$PRIVATE_SERVER_SETUP.COM isEE                       correct for the graphics controller in use. Form                       instance:   E                       The following is from the 9FX Vision 330 Owners G                       Guide, EK-V330G-OG pg 2-9. Place the following in H                       DECW$PRIVATE_SERVER_SETUP.COM, creatibng .COM fromF                       .TEMPLATE if necessary. Locate the DECW$PRIVATE_G                       SERVER_SETUP.COM file in SYS$SPECIFIC:[SYSMGR] or G                       in SYS$COMMON:[SYSMGR] as appropriate; the former C                       file is used for this system within a cluster C                       configuration, and the latter is used for all H                       systems that do not also have a local copy of this4                       file in SYS$SPECIFIC:[SYSMGR].  6                       $ DECW$XSIZE_IN_PIXELS == xvalue6                       $ DECW$YSIZE_IN_PIXELS == yvalueI                       $ DEFINE/SYSTEM DECW$SERVER_REFRESH_RATE rate_in_Hz   G                       Also see Section 11.12. Details of the PowerStormmI                       3D30 and 4D20 settings are available in the OpenVMS *                       Ask The Wizard area.  J                                                                       11-7                                   DECwindowst      D           __________________________________________________________;           11.7  How do I set the title on a DECterm window?d  B                    If you are creating a new DECterm window, check  =                    $ HELP CREATE /TERMINAL /WINDOW_ATTRIBUTES   I                    If you want to change the title of an existing window,cJ                    use the following control sequences, where <esc> is theJ                    ANSI escape code, value decimal 27, and "text label" is,                    what you want to display:  2                    To set the DECterm title, send:             <esc> '                    ]21;text label<esc>\V  /                    To set the icon label, send:              <esc>a'                    ]2L;text label<esc>\   E                    To set both the DECterm title and icon to the full                     device name:s  #                    $  esc[0,7] = 27 X                    $  fulldevnam = F$Edit(F$GetDVI("TT","FULLDEVNAM"),"UPCASE,COLLAPSE")K                    $  write sys$output esc+ "]21;" + fulldevnam + esc + "\"sK                    $  write sys$output esc+ "]2L;" + fulldevnam + esc + "\"   G                    You can also change the title and the icon using the *                    Options-Window... menu.  :                    Also see Section 12.1 and Section 8.11.  D           __________________________________________________________J           11.8  How do I customize DECwindows, including the login screen?  H                    To customize various DECwindows Motif characteristicsJ                    including the defaults used by the SET DISPLAY command,C                    the DECwindows login screen background logo used D                    (the default is the DIGITAL, Compaq, or HP logo),J                    various keymaps, the FileView defaults, session managerH                    defaults, the DECwindows login processing, DECwindowsD                    log file processing, and various other DECwindows4                    attributes, see the example file:  A                    $ SYS$STARTUP:DECW$PRIVATE_APPS_SETUP.TEMPLATEs                      11-8     p                              DECwindowsh        F                    This example template file is typically copied overH                    to the filename SYS$COMMON:[SYS$STARTUP]DECW$PRIVATE_I                    APPS_SETUP.COM and then modified to meet site-specificm                     requirements.  I                    Additionally, various X tools such as xsetroot, bitmaprG                    and xrdb-some these can be useful in customizing theoJ                    appearance of an application or of the DECwindows Motif@                    display-are provided in the DECW$UTILS: area.  D                    When using DECwindows V1.2-4 and later on OpenVMSC                    Alpha, the default desktop is the Common Desktop C                    Environment (CDE). You can select your preferred E                    desktop (CDE or DECwindows Motif) when logging in,oB                    or you can change the default to the DECwindowsE                    Motif desktop using the DCL symbol decw$start_new_nF                    desktop in the DECwindows private application setupH                    command procedure. See SYS$STARTUP:DECW$PRIVATE_APPS_H                    SETUP.TEMPLATE for further details, and how to create/                    DECW$PRIVATE_APPS_SETUP.COM.   D                    Note that with DECwindows CDE, the root window isC                    no longer visible by default. The root window is E                    hidden behind the "backdrop" window of the current J                    CDE workspace. To make the root window visible, use theG                    CDE style manager selection "backdrop none", and use I                    information such as that in the OpenVMS FAQ to set the6                    root window.r  >                    To add a new backdrop to the DECwindows CDEC                    environment, the backdrop must first be in or berE                    converted into X11 pixmap format. (This conversion-F                    is often possible using tools such as xv.) Then (ifC                    necessary) create the default backdrop directoryeF                    SYS$COMMON:[CDE$DEFAULTS.USER.BACKDROPS]. Place theH                    X11 pixmap file containing the desired image into theE                    backdrops directory, ensure that it has a filenamevG                    extension of .PM. (The xv default filename extensioneE                    for the X11 pixmap file is .XPM, while CDE expects/H                    only to see files with .PM.) Now invoke the CDE styleC                    manager and select a new backdrop. You will find F                    your image will be placed at the end of the list of'                    backdrops available.   J                                                                       11-9 m  t                              DECwindows       D           __________________________________________________________<           11.9  Why doesn't XtAppAddInput() work on OpenVMS?  F                    Yes, XtAppAddInput()  does work on OpenVMS. The MITC                    definition of the X Windows call XtAppAddInput() 8                    includes platform-specific arguments.  D                    On platforms where C is the typically the primaryB                    programming language for the platform, the fileA                    descriptor mask is one of the arguments to theo)                    XtAppAddInput()  call.t  F                    On OpenVMS, the platform-specific arguments to thisG                    call include an event flag and an IOSB, as these are I                    the traditional OpenVMS constructs used to synchronize F                    the completion of asynchronous operations. While itH                    would be easier to port non-OpenVMS C code that callsD                    XtAppAddInput()  over to OpenVMS if the argumentsF                    included the C file descriptor, this would make theH                    call unusable from other OpenVMS languages, and wouldF                    make it extremely difficult to use OpenVMS features2                    such as ASTs and sys$qio calls.  D                    One restriction on the event flag: the event flagJ                    chosen must be from event flag cluster zero. When usingF                    the traditional lib$get_ef and lib$free_ef calls toF                    allocate and deallocate event flags, you must firstJ                    explicitly call lib$free_ef to free up some event flagsH                    in event flag cluster zero. Please see the event flagH                    documentation for specific details on these calls andF                    for specific event flags that can be freed in event%                    flag cluster zero.e  E                    Here is some example code that covers calling thisi&                    routine on OpenVMS:                                        11-10 u  f                              DECwindows         2                        m->InputID = XtAppAddInput(%                            m->AppCtx, &                            m->InputEF,(                            m->InputIosb,-                            the_callback, 1 );o1                        if ( !((int) m->InputID ))                             {)                            XtAppErrorMsg( )                                m->AppCtx,t/                                "invalidDevice",a/                                "XtAppAddInput", 0                                "XtToolkitError",5                                "Can't Access Device",r/                                (String *) NULL, 3                                (Cardinal *) NULL );i                            ...  D           __________________________________________________________C           11.10  Why do the keyboard arrow keys move the DECwindowse                  cursor?  E                    Congratulations, you have just stumbled into "deadoF                    rodent" mode. This DECwindows environment-where theF                    keyboard arrow keys move the mouse cursor and whereJ                    the [SELECT], [PREV], and [NEXT] keys emulate the threeJ                    mouse buttons-allows rudimentary system operations when5                    the mouse is among the casualties.   A                    To enter or exit "dead rodent" mode, enter the -                    following: <CTRL/SHIFT/F3>f  D           __________________________________________________________;           11.11  Why does half my DECwindows display blank?   I                    This is likely a result of receiving an OPCOM or otherdE                    console message on a system that shares the system C                    console with the DECwindows graphics workstation                     display._  F                    You can toggle off the console display window usingD                    <CTRL/F2> and you can enable a serial console per6                    Section 14.3.6 or Section 14.3.3.3.    J                                                                      11-11                                   DECwindowsn        B                    Also see the console message window applicationG                    available with recent DECwindows versions-DECwindows.D                    versions V1.2-3 and later will enable this windowB                    by default. For details on this console messageC                    window, see the DECW$CONSOLE_SELECTION option ini@                    SYS$STARTUP:DECW$PRIVATE_APPS_SETUP.TEMPLATE.  F                    On older releases, you can disable output using the                    following:   =                    $ SET TERMINAL/PERMANENT/NOBROADCAST OPA0: 2                    $ DEFINE/USER SYS$COMMAND OPA0:"                    $ REPLY/DISABLE  I                    Also see Section 14.3.3.2, Section 14.19, and Also see                     Section 8.3,   D           __________________________________________________________C           11.12  %DECW-W-NODEVICE, No graphics device found on this                   system?  2                    To resolve the following error:  L                    %DECW-W-NODEVICE, No graphics device found on this systemQ                    -DECW-I-NODECW, DECwindows graphics drivers will not be loadede  G                    o  Ensure that the system parameter WINDOW_SYSTEM is G                       set to 1. If it is not set to a value of 1, issue #                       the commands:   -                       $ run sys$system:sysgene!                       USE CURRENT )                       SET WINDOW_SYSTEM 1s"                       WRITE ACTIVE#                       WRITE CURRENT;                       EXIT  -                       Then reboot the system.n  H                    o  On OpenVMS Alpha, ensure the SYSMAN IO PREFIX LISTI                       is set correctly, and specifically ensure the DECW$IG                       prefix is included in the existing list. If it ise3                       not, you will need to add it:                       11-12 l  i                              DECwindows         -                       $ run sys$system:sysmand$                       IO SHOW PREFIXU                       IO SET PREFIX=(DECW$,*)   * = list returned by the show commandn!                       IO AUTO/LOGe                       EXIT  F                    o  Ensure that the image SYS$SHARE:DECW$ICBM.EXE isG                       installed in memory. If it is not installed, thenn!                       install it:   =                       $ INSTALL LIST/FULL SYS$SHARE:DECW$ICBM ;                       $ INSTALL REPLACE SYS$SHARE:DECW$ICBM 5                       $ EDIT SYS$MANAGER:SYCONFIG.COMm  @                       $! The following line was added to install=                       $! support for the Mach64 Graphics Cardn                       $!;                       $ INSTALL REPLACE SYS$SHARE:DECW$ICBM                        $ ^Z  -                       Then reboot the system.   I                       The ICBM mechanism is not used on and not needed by 6                       more recent DECwindows versions.  I                    o  If the system still complains "%DECW-W-NODEVICE, NosB                       graphics device found on this system", then:  1                      o  Boot the system as normals  (                      o  Login as SYSTEM.  E                      o  Create the file SYS$COMMON:[SYSMGR]DECW$USER_RI                         AUTOCONFIG.DAT. Protection must permit world readA                         access.   H                      o  Add the following string on the very first line:  0                          CLEAR_PFLAG = ISA_4BYTE  %                      o  Save the file   0                      o  Set the file protections  S                          $ SET PROTECTION=W:RE SYS$MANAGER:DECW$USER_AUTOCONFIG.DATS  )                      o  Reboot the system   )                    Also see Section 11.6.E  J                                                                      11-13 i  h                              DECwindowsf      D           __________________________________________________________9           11.13  How can I reset the warning bell volume?   J                    With DECwindows CDE drivers and ECOs starting with ECOsG                    for the DECwindows keyboard driver SYS$IKBDRIVER.EXEoB                    in OpenVMS Alpha V7.1-2 and V7.2-1 and with theE                    SYS$IKBDRIVER.EXE included in OpenVMS V7.2-1H1 and H                    later, the DECwindows CDE controls will now correctlyA                    manage the setting of the warning bell volume.   F                    Unfortunately, the equivalent controls in the olderH                    DECwindows Motif interface are not compatible and can<                    no longer manage the warning bell volume.  J                    If you need to manage the volume with DECwindows Motif,9                    consider using the following approach:   2                    $ @decw$utils:decw$define_utils%                    $ xset b 1 100 100w  D                    The numerics are the volume, pitch, and duration,                     respectively.  J                    Why? When OpenVMS first started supporting the PC-styleJ                    keyboards, the X Windows Server and the keyboard driverH                    interface did not support the pitch and duration, andH                    neither did DECwindows Motif. The DECwindows keyboardH                    driver was accordingly changed to use the volume fromE                    the keyclick setting (keyclick is not available inQF                    a PC-style keyboard) and the bell volume setting to2                    control the pitch and duration.  H                    DECwindows CDE does provide sliders for setting pitchE                    and duration, so the keyboard driver and X Windows J                    Server were modified to provide all of the information,J                    and now the DECwindows CDE sliders work. This change isI                    unfortunately incompatible with the old scheme used on H                    the pre-CDE desktops, and the volume controls are nowH                    incompatible with the current keyboard drivers. Hence#                    the use of xset.S                              11-14 .  o                              DECwindowse      D           __________________________________________________________=           11.14  How can I alter the DECwindows CDE backdrop?   H                    To select a separate backdrop to be displayed on each/                    screen using DECwindows CDE:d  J                    o  Click on the Application Manager. This is the drawer.                       icon on the CDE toolbar.  ,                    o  Click on Desktop Tools  I                    o  Click on Set Default Screen and select the required                        screen  A                    o  Click on the Style Manager. This is the one E                       containing the mouse and ttt on the CDE toolbar_  0                    o  Now change the background.  D           __________________________________________________________A           11.15  How can I enable the DECwindows TCP/IP Transport   D                    To configure the TCP/IP transport for DECwindows,F                    first ensure that a TCP/IP package is installed andC                    configured. Then set the DCL symbol DECW$SERVER_hA                    TRANSPORTS in SYS$MANAGER:DECW$PRIVATE_SERVER_nE                    SETUP.COM to the appropriate local value, based on J                    the comments in that file. If you do not have a copy ofI                    SYS$STARTUP:DECW$PRIVATE_SERVER_SETUP.COM, the use the J                    following COPY command to create this file based on the*                    provided template file:  J                    $ COPY SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE -F                    $_ SYS$COMMON:[SYSMGR]DECW$PRIVATE_SERVER_SETUP.COM                      J                                                                      11-15                         J                    _______________________________________________________  ,           12       Miscellaneous Information      D           __________________________________________________________B           12.1  Where can I find information on escape and control                 sequences?  E                    Information on escape and control sequences can beCG                    found in the OpenVMS I/O User's Reference Manual, in G                    the chapter on the terminal driver. The chapter also H                    includes details on the general format and content of#                    these sequences.   G                    Specific details on the escape and control sequencesmH                    supported by a particular serial device are typicallyH                    found in the documentation provided with the specificD                    device. Information on the sequences supported byG                    DECwindows DECterm terminal emulator are included inl0                    the DECwindows documentation.  C                    Examples of common escape and control sequences- H                    those typically used by the OpenVMS screen managementB                    package-can be found in the OpenVMS system file+                    SYS$SYSTEM:SMGTERMS.TXT.   G                    The following refers to the function keys on the LK- I                    series keyboards found on the VT-series terminals such F                    as the VT220 and VT510, and the LK-series keyboardsG                    found on the OpenVMS workstations, and the keyboardsTG                    found on compatible terminals. (Though note that thepF                    keyboard itself does not generate the sequence, theG                    terminal or terminal emulator generates the sequence I                    in response to user input.) In the following, {CSI} is G                    decimal code 155 and can be replaced by the sequenceaH                    "{ESC}[" (without the quotes) particularly for seven-E                    bit operations, SS3 is decimal code 143 and can besB                    replaced by "{ESC}O" particularly for seven-bitC                    operations. Older VT1xx series terminals and any F                    other terminals operating with seven-bit charactersG                    should not be sent eight-bit operators such as {CSI}                     and {SS3}.o  J                                                                       12-1 e  e          ,                    Miscellaneous Information        >                    PF1={SS3}P PF2={SS3}Q PF3={SS3}R PF4={SS3}ST                    KP0={SS3}p KP1={SS3}q KP2={SS3}r KP3={SS3}s KP4={SS3}t KP5={SS3}u\                    KP6={SS3}v KP7={SS3}w KP8={SS3}x KP9={SS3}y KPCOMMA={SS3}l KPMINUS={SS3}m\                    KPPERIOD={SS3}n ENTER={SS3}M DNARROW={CSI}B UPARROW={CSI}A LFARROW={CSI}D[                    RTARROW={CSI}C FIND={CSI}1~ INSERT={CSI}2~ REMOVE={CSI}3~ SELECT={CSI}4~ \                    PREV={CSI}5~ NEXT={CSI}6~ F6={CSI}17~ F7={CSI}18~ F8={CSI}19~ F9={CSI}20~S                    F10={CSI}21~ F11={CSI}23~ F12={CSI}24~ F13={CSI}25~ F14={CSI}26~D`                    HELP={CSI}28~ DO={CSI}29~ F17={CSI}31~ F18={CSI}32~ F19={CSI}33~ F20={CSI}34~  G                    An example of working with escape sequences (in DCL)l                    follows:c  #                    $ esc5m = "*[5m"w$                    $ esc5m[0,8] = 27#                    $ esc0m = "*[0m"c$                    $ esc0m[0,8] = 27E                    $ write sys$output esc5m + "blinking text" + esc0m   J                    Documentation on an ANSI terminal relatively similar to4                    the VT525 series is available at:  J                    o  ftp://ftp.boundless.com/pub/text/adds/docs/260_prog/  J                    o  ftp://ftp.boundless.com/pub/text/adds/docs/260_user/  A                    Also see the various documentation and manualsl                     available at:  +                    o  http://www.vt100.net/n  E                    Information on the ReGIS graphics character set is_                     available at:  H                    o  http://www.cs.utk.edu/~shuford/terminal/dec_regis_                       news.txt                      Also:  A                    o  http://www.boundless.com/Text_Terminals/VT/t  7                    Also see Section 11.7, Section 8.11.L                          12-2p    D          ,                    Miscellaneous Information      D           __________________________________________________________F           12.2  Does DECprint (DCPS) work with the LRA0 parallel port?  A                    The parallel printing port LRA0: found on many I                    OpenVMS Alpha systems is capable of some bidirectionalnH                    communications, with enough for basic operations with*                    most parallel printers.  E                    DECprint (DCPS) requires more than just the simplelI                    handshaking provided by the LRA0: port, therefore DCPS55                    does not work with the LRA0: port.d  D           __________________________________________________________A           12.3  How do I check for free space on a (BACKUP) tape?.  H                    You cannot know for certain, though you can certainly3                    estimate the remaining capacity.O  D                    Tape media is different than disk media, as disksI                    have a known and pre-determined fixed capacity. ModerntJ                    disks also appear logically perfect, based on bad blockI                    revectoring support and the extra blocks hidden within G                    the disk structure for these bad block replacements.   C                    The capacity of tape media is not nearly as pre- I                    determined, and the capacity can vary across differentwB                    tape media (slightly different media lengths orB                    different foil markers or other variations, forI                    instance) and even on the same media over time (as bad J                    spots in the media arise). Tapes can vary the amount ofG                    recording media required, depending on the remaining E                    length of the tape, the numbers of correctable andiC                    uncorrectable media errors that might occur, theoI                    numbers and sizes of the inter-record gaps and relatedhF                    tape structure overhead, the particular media errorH                    recovery chosen, the tape density, the efficiently ofH                    any data compression in use, and the storage overheadG                    required by BACKUP, tar, and other similar commands.n  D                    BACKUP using with the default settings results inH                    approximately 15% overhead, in terms of saveset size.H                    (eg: Assuming a 500 KB input, the total size would be                    575 KB.)a  +                    Assuming no compression:e>                    4 GB media / 575 KB saveset = 7294 savesets  J                                                                       12-3               ,                    Miscellaneous Information        ,                    Assuming 1:2 compression:?                    8 GB media / 575 KB saveset = 14588 savesets   E                    Note: There are no inter-record gaps on DAT tapes. I                    (When determining media capacity, you have to considerSD                    these with nine-track magtape media. Not with DATA                    (DDS). However, the block structure underneath E                    the variable length record recording is based on a G                    block size of circa 124 KB. Further, writing doubles C                    filemarks and such can cause a loss of up to the G                    underlying block size. Thus even though there are noeF                    inter-record gaps on DAT, larger savesets are still                     usually best.  I                    The compression algorithms used on various devices are G                    generally not documented-further, there is no way toeF                    calculate the effective data compression ratio, theF                    tape mark overhead, and similar given just the dataG                    to be stored on tape-short of actually trying it, ofM                    course.  I                    A typical compression ratio found with "everyday" data<4                    is somewhere around 1:1.8 to 1:2.  C                    Note: OpenVMS often uses the term COMPACTION for C                    compression control, as in the qualifier /MEDIA_ %                    FORMAT=COMPACTION.b  D           __________________________________________________________0           12.4  So what happened to sys$cmsuper?  2                    There is no SYS$CMSUPR service.  H                    The typical wisdom for getting into supervisor accessC                    mode (from user mode) is to execute a routine in C                    executive mode (via a call to SYS$CMEXEC and the J                    appropriate privilege) and then issue a SYS$DCLAST withF                    the ASTADR parameter pointing to your routine entryE                    point and the ACMODE parameter specified as PSL$C_i                    SUPER.   F                    Alternatively, you can reset mode in the call stackF                    return path and unwind from executive or kernel out(                    into supervisor mode.                      12-4i t  a          ,                    Miscellaneous Information      D           __________________________________________________________5           12.5  Correctly using license PAKs and LMF?   D                    If you have multiple LMF$LICENSE.LDB databases inE                    your OpenVMS Cluster, then each and every PAK mustuJ                    be installed in each and every license database presentE                    in an OpenVMS Cluster. Even if you use /EXCLUDE oroF                    /INCLUDE, you need to have a consistent set of PAKsG                    registered across all licensing databases present inh'                    the OpenVMS Cluster.   G                    If your software license permits it, you can use theaC                    following two commands to transfer license PAKs:   $                    $ LICENSE COPY...D                    $ LICENSE ISSUE/PROCEDURE/OUTPUT=file product,...  I                    To display the particular license(s) required (such as I                    when you receive a NOLICENSE error), use the following                      DCL sequence:  .                    $ SET PROCESS/PRIVILEGE=ALL!                    $ REPLY/ENABLE F                    $ DEFINE/SYSTEM/EXECUTIVE LMF$DISPLAY_OPCOM_MESSAGE  D                    This logical name will cause all license failuresF                    to generate OPCOM messages, and this will hopefullyF                    show which license(s) you need- there may well alsoG                    be additional license failures displayed, as various0H                    products can check for and can be enabled by multipleG                    license PAKs. You will want to deassign this logicalr"                    name when done.  8                    Some of the more common license PAKs:  U                      DECnet Phase IV:   DVNETRTG, DVNETEND, DVNETEXT, or NET-APP-SUP*aU                      DECnet-Plus:       DVNETRTG, DVNETEND, DVNETEXT, or NET-APP-SUP* <                      TCP/IP Services:   UCX, or NET-APP-SUP*L                      OpenVMS Alpha:     OPENVMS-ALPHA and OPENVMS-ALPHA-USER/                      OpenVMS VAX:       VAX-VMS 6                      OpenVMS Galaxy:    OPENVMS-GALAXY@                      Cluster (Alpha):   VMSCLUSTER, NET-APP-SUP*@                      Cluster (VAX):     VAXCLUSTER, NET-APP-SUP*    J                                                                       12-5 e  S          ,                    Miscellaneous Information        A                    Various NET-APP-SUP (NAS) license packages aretI                    available, each with differing collections of products-C                    authorized. See the various NAS Software ProductdD                    Description (SPD) documents for specific details.  5                    o  http://www.compaq.com/info/spd/8D                       OpenVMS typically uses SPD 25.01.xx and/or SPD                       41.87.xx.   C                    To determine which license PAK is failing (via aWI                    license check failure OPCOM message), use the command:s  K                    $ DEFINE/SYSTEM/EXECUTIVE LMF$DISPLAY_OPCOM_MESSAGE TRUEr  ?                    Realize that defining this logical name will A                    cause license checks that are otherwise hiddennE                    (unimplemented, latent, or part of a check for anytG                    of a series of licenses) to become visible. In othertI                    words, expect to see some spurious license check calls (                    when you define this.  F                    For information on PAKGEN and on generating license2                    PAKs, please see Section 10.10.                                                              12-6     i                    J                    _______________________________________________________  -           13       Finding and using SoftwareL      D           __________________________________________________________I           13.1  Where can I find freeware/shareware/software for OpenVMS?   E                    o  Details on many commercial OpenVMS products are :                       available in the catalog located at:  <                      o  http://www.compaq.com/csa/directory/  D                    o  An OpenVMS Freeware CD-ROM is distributed withJ                       OpenVMS, and is also available separately (QA-6KZAA-F                       H8). The contents of the OpenVMS Freeware CD-ROM9                       media are also available online at:O  ?                      o  http://www.openvms.compaq.com/freeware/C  /                      o  ftp://ftp.montagar.com/f  7                      o  ftp://mvb.saic.com/freewarev40/S  B                       and at various other sites. The website alsoD                       includes various updates and new packages thatE                       become available after the CD-ROM distributionsy"                       are created.  E                       Submissions to the OpenVMS Freeware can be made                        via:  G                      o  http://www.openvms.compaq.com/openvms/freeware/l  J                       To acquire the OpenVMS Freeware CD-ROM distribution,H                       you can order an OpenVMS distribution from HP (theH                       Freeware is included)(see the OpenVMS SPD for partH                       numbers), or you can specifically order a Freeware=                       distribution from HP under part number:   #                      o  QA-6KZAA-H8   I                       The Freeware CD-ROM set contains a large assortment J                       of freeware, and is a good starting point if lookingF                       for utilities. Many of the packages listed belowH                       are also on the Freeware CD. Some of the most oft-H                       requested OpenVMS tools on the Freeware CD includeE                       ZIP and UNZIP and GZIP (please see SOFT14), MMK   J                                                                       13-1               -                    Finding and using Software         J                       (make), PINE, PERL, TAR, UUENCODE and UUDECODE. Many@                       other tools are available on the Freeware.  A                    o  The UUENCODE and UUDECODE tools and variousoF                       other tools are also available as part of TCP/IPF                       Services package. (Use the DCL command procedureH                       SYS$STARTUP:TCPIP$DEFINE_COMMANDS.COM available onH                       V5.0 and later to set up the necessary DCL foreignJ                       command symbols used for these and for various other9                       tools provided by TCP/IP Services.)   D                    o  OpenVMS software (formerly at Western KentuckyG                       University (WKU) is now available via Madgoat and_4                       via Process Software archives:  A                      o  http://www.process.com/openvms/index.html   /                      o  http://www.madgoat.com/t  B                    o  The FILESERV packages are also available via)                       anonymous FTP from:   ;                      o  ftp://ftp.process.com/vms-freeware/   C                      o  ftp.process.com, under [.WKU.VMS.FILESERV].   5                      o  ftp.vms.stacken.kth.se, underg4                         [.MIRRORS.WKU.VMS.FILESERV].  E                      o  ftp.ctrl-c.liu.se, under [.WKU.VMS.FILESERV].u  '                      o  ftp.riken.go.jpi  G                      o  ftp.vsm.com.au, under kits and kits/decwindows.T  C                      o  ftp.vsm.com.au, via the WWW instead of FTP.   E                       The packages are also available via e-mail frompF                       FILESERV@PROCESS.COM. Send the commands HELP andI                       DIR ALL in the body of a mail message to this email G                       address for further information on retrieving the                        files.  C                    o  Arne Vajhj operates an OpenVMS website, withd6                       software and other pointers, at:  4                      o  http://www.levitte.org/~ava/                      13-2  d  l          -                    Finding and using Software         G                    o  Jouk maintains a summary of various public-domain F                       and open-source software ports, and specifically?                       ports of packages for use on OpenVMS, at:t  =                      o  http://nchrem.tnw.tudelft.nl/openvms/   G                    o  The Kermit file transfer package is available at:d  7                      o  http://www.columbia.edu/kermit/   2                      o  ftp://kermit.columbia.edu/  -                    o  ZMODEM is available at:$  7                      o  ftp://ftp.cs.pdx.edu/pub/zmodemT  F                       See the FILES file in that directory for furtherH                       details. Note that this freeware version of ZMODEMI                       will interoperate only with ZMODEM software that isiJ                       licensed from Omen Technology. (This package is alsoJ                       available on various of the Freeware distributions.)  C                    o  A good source of software for OpenVMS systemsnF                       and for various other platforms is the EncompassH                       (formerly known as DECUS) library. Online catalogs@                       are available as well as some software via  +                      o  ftp://ftp.decus.org   2                      o  gopher://gopher.decus.org/  -                      o  http://www.decus.org/u  F                    o  DECUS SIG Tape collections are available on Mark(                       Berryman's system,  +                      o  ftp://mvb.saic.com/.  G                    o  David Jones's DECthreads-based HTTP_SERVER World- I                       Wide Web server for OpenVMS, often known as the OSUn                        webserver:  .                      o  http://kcgl1.eng.ohio-9                         state.edu/www/doc/serverinfo.htmlx  <                    o  Secure Shell (SSH) Server for OpenVMS:  H                      o  http://kcgl1.eng.ohio-state.edu/~JONESD/ssh/DOC/  A                       Secure Shell (SSH) FISH Client for OpenVMS:f  3                      o  http://www.free.lp.se/fish/   B                       Information on OpenSSL (SSLeay) for OpenVMS:  J                                                                       13-3 _  _          -                    Finding and using Software         6                      o  http://www.free.lp.se/openssl/  3                      o  http://www.free.lp.se/fish/e  H                       Information on OpenSSL (SSLeay) and OSU Web server%                       interoperation:e  @                      o  http://www.ourservers.net/openvms_ports/  H                       OpenSSL is included with OpenVMS V7.3-1 and later.  F                    o  DECwindows Motif V1.2-3 includes NCSA Mosaic 2.4F                       built for TCP/IP Services (UCX). V1.2-4 includesF                       Spyglass Enhanced Mosaic, which supports many ofI                       the Netscape enhancements. Versions of the NetscapetH                       Navigator and particularly the Mozilla Web BrowserG                       are also available for OpenVMS. The Compaq SecurewI                       Web Browser (CSWB) kit is a packaged version of theA>                       Mozilla.org Mozilla Web Browser. <(CSWB)  I                    o  A port of the NCSA Mosaic web browser that supportslG                       TCP/IP Services, Multinet and SOCKETSHR/NETLIB isk%                       available from:   6                      o  ftp://wvnvms.wvnet.edu/mosaic/  A                       Versions of the Mosaic web browser are also 0                       available on the Freeware.  H                    o  Lynx (a character-cell World-Wide-Web web browser)'                       is available from   8                      o  ftp://ftp2.cc.ukans.edu/pub/lynx  I                       Versions of Lynx, a character-cell web browser, are =                       also available on the OpenVMS Freeware.   I                    o  The Netscape Navigator and Mozilla web browsers ared#                       available at:n  O                      o  http://www.openvms.compaq.com/ebusiness/Technology.html   /                      o  http://www.mozilla.org/c  E                    o  PGP (Phil Zimmerman's "Pretty Good Privacy") is J                       available from various distribution sites, includingI                       those listed in the PGP FAQ. Information on PGP and H                       on OpenVMS downloads of PGP is available. Relevant#                       URLs include:   -                      o  http://www.ipgpp.org/                       13-4  I  t          -                    Finding and using Software         ;                      o  http://web.mit.edu/network/pgp.html   ,                      o  http://www.pgpi.com/  ?                      o  http://www.yrl.co.uk/~phil/pds/pds.html   +                      o  http://www.nai.com/   B                    o  GNU Privacy Guard (GPG, GnuPG) is available.  C                       Search the comp.os.vms newsgroup archives foriC                       information regarding GnuPG; the source code,_G                       binaries for various platforms, and documentationa+                       are all available at:   -                      o  http://www.gnupg.org/   J                       The OpenVMS source code and OpenVMS Alpha images can"                       be found at:  H                      o  http://saf.bio.caltech.edu/pub/SOFTWARE/openvms/  B                      o  ftp://ftp.process.com/vms-freeware/mathog/  G                       As of this writing, the port only runs on OpenVMS H                       Alpha, but an investigation of an OpenVMS VAX port8                       is reportedly under consideration.  G                    o  An archive of the CENA DECwindows, X Windows, and_I                       VMS software packages can be found at the followingo                       sites:  0                      o  http://decwarch.free.fr/  6                      o  ftp://ftp2.cnam.fr/decwindows/  ;                      o  ftp://ftp.ctrl-c.liu.se/decwindows/h  H                      o  ftp://ftp.vms.stacken.kth.se/mirrors/decwindows/  ?                      o  http://www.multimania.com/pmoreau/decw/   G                       Other FTP mirror sites for the DECwindows archive                        include:  0                      o  axp.psl.ku.dk (Multinet)  .                      o  ftp2.cnam.fr (MadGoat)  F                       ftp.x.org (in /contrib/vms) is effectively not aG                       mirror, but it does have various OpenVMS packagesw2                       from the DECwindows archive.  H                       A list of the http mirror sites for the DECwindows.                       archive is available at:  J                                                                       13-5               -                    Finding and using Software         Q                      o  http://axp616.gsi.de:8080/wwwar/cena/decwindows/cena.htmlf  I                       Various of these packages are also available on the                        Freeware.S  C                    o  ImageMagick is an X11 package for display and E                       interactive manipulation of images. The package F                       includes tools for image conversion, annotation,D                       compositing, animation, and creating montages.E                       ImageMagick can read and write many of the more G                       popular image formats (e.g. JPEG, TIFF, PNM, XPM,r&                       Photo CD, etc.).  3                      o  http://www.imagemagick.org/e  F                       Versions of ImageMagick are also included on the                       Freeware.   C                    o  XV is a image viewing and editing tool and is %                       available from:   6                      o  ftp://ftp.cis.upenn.edu/pub/xv  /                      o  http://www.sanface.com/W  A                      o  ftp://www-pi.physics.uiowa.edu/~dyson/xv/   I                    o  Many software packages are available for displayingoE                       various bitmap files (.JPG, .GIF, .BMP, etc) onSG                       OpenVMS. Xloadimage, Xli, Xv, ImageMagick are thelG                       most common tools used under OpenVMS. Various websD                       browsers such as Mozilla (qv) can also displayH                       various file formats on OpenVMS. You can find some?                       of these tools at the DECwindows Archive:   I                      o  http://www.multimania.com/pmoreau/decw/index.htmlC  J                      o  http://www.multimania.com/pmoreau/decw/images.html  G                    o  GHOSTSCRIPT (gs) and GHOSTVIEW (gv) are availablem                       from:s  J                      o  http://www.openvms.compaq.com/freeware/freeware50/  B                       Versions are also available on the Freeware.                         Also see:   :                      o  http://www.cs.wisc.edu/~ghost/gnu/                      13-6M G  S          -                    Finding and using Softwaren        F                    o  XPDF, a viewer for PDF (Adobe Acrobat) files, is%                       available from:   4                      o  http://www.foolabs.com/xpdf/  5                       Also available on the Freeware.r  H                       Beware: the XPDF tool included on OpenVMS FreewareG                       V4.0 is dated, and has been found to have variousnJ                       bugs. Use the Freeware V5.0 version of the XPDF kit,                       or later.i  F                       A Java-based PDF viewer is available from Adobe,E                       and is known to operate on recent OpenVMS Alpha                        releases:   -                      o  http://www.adobe.com/   E                    o  Various OpenVMS-related tools-both freeware and F                       shareware-such as txt2pdf-are available from at:  /                      o  http://www.sanface.com/E  C                    o  The MPEG library version 1.1 is available for .                       OpenVMS VAX and Alpha at  I                      o  ftp://ftp.x.org/contrib/vms/mpeglib-11-vms.readme.  F                      o  ftp://ftp.x.org/contrib/vms/mpeglib-11-vms.zip  J                       Various MPEG players and related tools are available&                       on the Freeware.  E                    o  An Archie clone is available at INFO.CS.PUB.RO._F                       Telnet to that machine, and login as VMSARCI. ItH                       contains now listings for over 30 ftp servers with<                       over 14 gigabytes of OpenVMS software.  J                       The most useful commands are LIST, which generates aJ                       list of scanned ftp servers, and FIND string, whichsG                       looks for a file containing "string" in the name;nI                       the search modes are only "substring" [default] andiI                       "exact", and regex search is not supported (so FINDlI                       EMACS will work, but FIND *EMACS* or FIND *EMACS*.*t@                       will not). The search is case-insensitive.  G                       The maintainer of the site (stfp@roipb.cs.ipb.ro)dF                       requests that anyone submit notifications of FTPJ                       servers with OpenvMS software that are not listed on                       the site.   J                                                                       13-7 t  l          -                    Finding and using Softwares        D                    o  The Levitte (extended :-) Family (and OpenVMS)                       website:  /                      o  http://www.levitte.org/r  4                      o  http://www.levitte.org/~ava/  B                    o  Robert Alan Byer's OpenVMS Hobbyist Systems,J                       including OpenVMS public domain software and various                       ports:  2                      o  http://www.ourservers.net/  0                    o  CalTech Software Archives:  G                      o  http://seqaxp.bio.caltech.edu/pub/SOFTWARE/AAA_f$                         CONTENTS.TXT  =                    o  DJE Systems Website (David J. Dachtera)   ;                      o  http://www.djesys.com/freeware/vms/   "                    o  Web Servers:  F                       Apache Web server (HP (Compaq) Secure Web Server                       (CSWS)):  O                      o  http://www.openvms.compaq.com/ebusiness/Technology.html   0                      o  http://www.er6.eng.ohio-7                         state.edu/~jonesd/apache/1_3_9/   B                       The SOAP Toolkit is available at the OpenVMS                       website.  $                       OSU Web server  0                      o  http://www.er6.eng.ohio-9                         state.edu/www/doc/serverinfo.htmlt  5                      o  http://www.kjsl.com/archives/   C                      o  email list: VMS-WEB-daemon-Request@KJSL.COMt  %                       WASD Web serverr  4                      o  http://wasd.vsm.com.au/wasd/  *                       Purveyor Web server:  F                      o  email list: listserv@cjis.ci.lincoln.ne.us, noE                         subject, one line message: SUBSCRIBE PURVEYORe  9                       FastCGI software is available from:t  9                      o  http://www.DigitalSynergyInc.com/                       13-8                -                    Finding and using Software_        E                    o  CD-R (CD-Recordable) media tools are available, -                       please see Section 9.7.t  6                    o  Grace (WYSIWYG 2D plotting tool)  @                      o  http://plasma-gate.weizmann.ac.il/Grace/  J                    o  The POV-Ray ("Persistance of Vision" Raytracer) ray-J                       tracing graphics package is available on the OpenVMS                       Freeware.   5                    o  Majordomo mailing list handler:   O                      o  http://www.openvms.compaq.com/ebusiness/Technology.html   H                    o  PINE (OpenVMS tools for sending and receiving MIME                       mail):  >                      o  ftp://ftp2.kcl.ac.uk/pub/vms/pine-vms/  G                      o  http://www.agh.cc.kcl.ac.uk/files/vms/pine-vms/_  I                       A MIME tool is available in OpenVMS V7.2 and later.   D                       Also see the mmencode base64 encode and decode#                       available at:_  E                      o  http://nucwww.chem.sunysb.edu/htbin/software_a                          list.cgi  ?                    o  Menufinder (menu-driven system managementr#                       environment):d  <                      o  http://www.itre.com/mf/download.html  B                    o  SYSLOGCLIENT (a client for processing SYSLOGF                       requests) has been provided for download by Mark                        Hemker at:  B                      o  http://home.insightbb.com/~hemker/vms.html  .                    o  tcgmsg, pvm, mpi, linda:  @                      o  ftp://v36.chemie.uni-konstanz.de/tcgmsg_*                         vms/tcgmsg_vms.zip  D                    o  OpenVMS software that can control a Tripp-LiteE                       Uninterruptable Power Supply (UPS) is availabled                       from:u  O                      o  http://seqaxp.bio.caltech.edu/pub/SOFTWARE/TCONTROL.ZIPl  J                                                                       13-9 E  p          -                    Finding and using Software         H                       UPShot web-based software for controlling a UPS is%                       available from:e  <                      o  http://www.tmesis.com/apc/beta.htmlx  J                       OpenVMS software for controlling Liebert UPS devices=                       are available from the Liebert website:   =                      o  http://www.liebert.com/apc/beta.htmlxo  J                    o  Examples of using the OpenVMS Foreign MAIL interface'                       are available at:t  V                      o  http://www.hhs.dk/anonymous/pub/vms/collection/foreignmail.zip  G                      o  http://www.hhs.dk/anonymous/pub/vms/nbl/nbl.zipt  H                    o  For tools to manage or to search your OpenVMS MAIL                        file, see:  U                      o  http://vms.process.com/scripts/fileserv/fileserv.com?MLSEARCHt  I                    o  AscToHTM attempts to convert any plain text file toiI                       HTML, while AscToTab restricts itself to files thattH                       are plain text tables. (Versions are also availabe/                       on the OpenVMS Freeware).i  B                      o  http://www.jafsoft.com/asctohtm/index.html  B                      o  http://www.jafsoft.com/asctotab/index.html  F                    o  Information on the SAMBA package, a package thatF                       provides SMB-based Microsoft Windows PC disk andB                       print services for OpenVMS, is available at:  F                      o  http://ifn03.ifn.ing.tu-bs.de/ifn/sonst/samba-                          vms.html  -                      o  http://www.samba.org/K  G                       To subscribe to the SAMBA-VMS mailing list e-mail}E                       listproc@samba.org with no subject line and theR4                       following single line of text:  8                       subscribe samba-vms Your Full Name                         Also see:~  /                      o  http://lists.samba.org/C  E                    o  The Perl language is available for OpenVMS, seeC0                       Section 13.10 for details.                      13-10               -                    Finding and using SoftwareL        3                    o  XML is available for OpenVMS.m  D                       Source code of an XML Parser is available from                       Oracle.                          Also see:   ;                      o  http://www.python.org/sigs/xml-sig/   H                       An XML parser is available as part of OpenVMS V7.3                        and later.  =                    o  GTK+ (The GIMP GUI Tookit) for OpenVMS:u  O                      o  http://www.openvms.compaq.com/ebusiness/Technology.htmlt  D                    o  The OpenVMS Porting Library now available, andG                       is intended to permit easier porting of C and C++ @                       applications from UNIX systems to OpenVMS:  O                      o  http://www.openvms.compaq.com/ebusiness/Technology.html   ,                       GTK is also available.  /                    o  Mlucas (specialized FFT):   @                      o  ftp://hogranch.com/pub/mayer/README.html  E                    o  Tools to monitor the terminals and the activityoE                       of other OpenVMS users (in addition to existing F                       auditing capabilities in OpenVMS) are available.C                       Peek and Spy (Networking Dynamics) and ContrlDG                       (Raxco) are two of the commercial packages, while E                       the freeware Supervisor package is available ons"                       OpenVMS VAX.  :                      o  http://www.networkingdynamics.com/  -                      o  http://www.raxco.com/p  )                    o  Python for OpenVMS:)  .                      o  http://www.python.org/  4                       Also see the OpenVMS Freeware.  3                    o  Various packages for OpenVMS:   L                      o  http://richj.home.mindspring.com/richware/index.html  H                      o  http://www3.sympatico.ca/n.rieck/links/cool_vax_                          vms.html  J                                                                      13-11 i  O          -                    Finding and using Softwarem        E                    o  TSM (Terminal Server Manager) is available via:t  G                      o  http://www.compaq.com/support/digital_networks_n6                         archive/servers/tsm/index.html  J                      o  http://www.openvms.compaq.com/freeware/freeware50/  G                      o  Beware: The TSM saveset shipped on the Freeware I                         V5.0 disk media is busted. Download a new copy of >                         the saveset from the Freeware website.  &                    o  TCL for OpenVMS:  D                      o  ftp://sapodilla.rsmas.miami.edu/pub/VMS-tcl/  J                    o  make, gmake, mmk and other build tools are available&                       on the Freeware.  J                    o  An OpenVMS port of the ht://Dig web search engine is#                       available at:   5                      o  ftp://ftp.pdv-systeme.de/vms/   >                    o  A mySQL database client is available at:  A                      o  http://mysql.holywar.net/Downloads/MySQL- :                         3.22/mysql-3.22.25-clients-vms.zip  A                      o  http://mysql.holywar.net/Downloads/MySQL-f=                         3.22/mysql-3.22.25-clients-vms.readmen  E                       For additional information related to the mySQLtC                       port, please search the comp.os.vms newsgroupf                       archives.   F                    o  If you need to change the file modification dateJ                       and are looking for a utility such as the UNIX touchH                       tool, look at DFU on the OpenVMS Freeware (DFU SETG                       or simular), or use an existing DCL commands such                        as:   K                       $ SET FILE/PROTECT=(current_protection_mask) [...]*.*n  I                    o  A table listing translations between UNIX shell and G                       OpenVMS DCL commands was posted to comp.os.vms by J                       Christopher Smith some time ago. This page should beC                       available from the google newsgroup archives.                       13-12 m  a          -                    Finding and using Software,        I                    o  The UNIX touch tool is available via various means:o  5                       $ RENAME filename.ext;version *r  M                      o  http://nucwww.chem.sunysb.edu/helplib/@hvmsapps/TOUCHa  B                       MadGoat FILE tool (see the MadGoat archives)  :                    o  use /REVISION_DATE or /CREATION_DATE  :                    The DFU tool (see the OpenVMS Freeware)                      The pair:  D                    $ set file 'p1' /acl=(ident=[system],access=none)L                    $ set file 'p1' /acl=(ident=[system],access=none) /delete  '                    $ SET FILE/VERSION=0a  &                    The following hack:  5                    $!   Command procedure SETDATE.COM                     $!h@                    $!   Changes the DATES for an input file to a+                    $!   file named OUTFILE.u                    $!<-                    $assign/nolog 'p1' outfilet7                    $convert/fdl=sys$input 'p1' outfile:                     date )                    creation   01-apr-2010h)                    expiration 01-Apr-2012R)                    revision   01-Apr-2011_                    backup_                    ...  =                    The following RMS system service sequence:T  H                    o  sys$open(), with the XABRDT XAB structure chained.  C                    o  set the desired values within the XABRDT XAB.)  !                    o  sys$close()     J                                                                      13-13 p  r          -                    Finding and using Software       D           __________________________________________________________8           13.2__Where_can_I_find_UNIX_tools for OpenVMS?  J           13.2.1  POSIX-compliant versions of POSIX routines and utilities  F                    lex, yacc, grep, tar, uuencode, uudecode, rcs, man,H                    cpio, make, awk, ar, mail, etc., the POSIX shell, the6                    POSIX C programming interface, etc.  D                    POSIX utilities can be used from within the POSIXE                    shell, and via the DCL `POSIX/RUN POSIX$BIN:tool.'                     command.   ?                    POSIX is a separately-installed package, and A                    is licensed with OpenVMS V5.5 later. The POSIX C                    installation kit is included on the consolidated E                    distribution CD-ROM kit, and installation kits are -                    also available separately.   G                    The POSIX package is no longer supported on OpenVMS,dH                    components of the POSIX standard such as parts of theF                    POSIX API are being added into OpenVMS. Versions ofI                    POSIX generally do not operate on V7.x OpenVMS VAX and *                    OpenVMS Alpha releases.  '           _____________________________o/           13.2.2  C system and library routinest  J                    Common C system and library routines are present in theJ                    DEC C run-time library, which is available for V5.5 andH                    later, and is shipped in V6.1 and later. DEC C is theH                    upgrade for VAX C, DEC C and VAX C can coexist on theI                    same system OpenVMS VAX system, and both compilers can 6                    be enabled via the "C" license PAK.  G                    Also see SYS$EXAMPLES:, and (if either is installed)yE                    the DECW$EXAMPLES: and TCPIP$EXAMPLES (or prior to,.                    V5.0, UCX$EXAMPLES:) areas.  '           _____________________________ 2           13.2.3  X Windows utilities and routines  @                    Various X Windows utilities are available forG                    DECwindows. DECwindows is an implementation of the XeJ                    Windows environment and libraries, and provides variousF                    libraries, and provides various desktop interfaces,1                    including COE, Motif, and XUI.E                      13-14    e          -                    Finding and using Software         G                    xwd, xev, mosaic web browser, xrdb, bmtoa and atobm,:D                    xpr, ico, etc. are available. Look in DECW$UTILS:A                    in DECwindows Motif V1.2-3 and later. Also see ?                    DECW$EXAMPLES: for example X and C programs.   G                    Miscellaneous tools and examples are also available.oF                    Examples include the older DWAUTH (X Windows SYSUAFG                    authorize-like tool) tool, various versions of grep,lH                    fgrep, yacc, vmstar, uuencode, gawk, etc. html tools,F                    the mx SMTP mail exchange package, X windows flightE                    simulator, the mxrn X windows news reader, the OSU8J                    HTTPD WWW server, a WWW gopher browser, etc. are all on6                    the various Freeware distributions.  '           _____________________________W9           13.2.4  TCP/IP Tools and Utilities for OpenVMS?u  I                    TCP/IP Services (formerly known as UCX) contains toolsOF                    such as ping, uuencode, smtp, snmp, rcp, nfs, tnfs,                    etc.   I                    OpenVMS V6.2 and later includes DCL-integrated support(B                    for various IP tools, with commands such as SETE                    HOST/TELNET, and COPY/FTP. This interface requires J                    the installation of an IP stack, and UCX V3.3 and laterE                    as well as any current third-party IP stack can beGG                    used. Once the IP stack is installed and configured, J                    the DCL command qualifiers such as /FTP, /RCP, /RLOGIN,H                    /TELNET, and /TN3270 are available on the various DCL                    commands.  G                    Various C programming examples in TCPIP$EXAMPLES and_@                    (on releases prior to V5.0) in UCX$EXAMPLES:.  '           _____________________________e$           13.2.5  The vi text editor  D                    vile, vim and elvis are all clones of the vi text6                    editor, and all operate on OpenVMS.  I                    Versions of vile are available on the Freeware and at:e  D                    o  http://www.clark.net/pub/dickey/vile/vile.html  J                                                                      13-15 e             -                    Finding and using Softwarei        #                    vim: vi improved   2                    o  http://www.polarfox.com/vim/  '           _____________________________g#           13.2.6  Various GNU toolst  E                    Information on the GNU on VMS (GNV) Project, whichhH                    aims to port GNU software (bash, flex, bison, etc) to,                    OpenVMS, is available at:  1                    o  http://gnv.sourceforge.net/   !                    Software info:   9                    o  http://vms.gnu.ai.mit.edu/software/m  $                    Software archive:  @                    o  ftp://vms.gnu.ai.mit.edu/gnu-vms/software/  H                    Various GNU tools are also available on the Freeware.  '           _____________________________O            13.2.6.1  GCC compiler  G                    A mirror for work performed at the ProGIS company in F                    Germany in porting GCC (GNU C) to OpenVMS Alpha and/                    OpenVMS VAX is available at:p  9                    o  ftp://vms.gnu.org/progis_mirror/gcc   ?                    o  http://www.levitte.org/~ava/vms_gnu.htmlx   7                    o  ftp://ftp.caltech.edu/pub/rankin/   I                    There are also updated header files for GCC on OpenVMSiH                    VAX that allow it to work with TCP/IP Sockets and the                    HP C RTL at:   <                    o  ftp://ftp.qsl.net/pub/wb8tyw/gcc281_u/  D                    The HP C compiler and other development tools areE                    part of the OpenVMS Hobbyist licensing program for F                    non-commercial users, and these and other tools areE                    available to commercial developers via the HP DSPP H                    partner program. (See Section 2.14 for information on                    DSPP.)E                      13-16 o             -                    Finding and using Softwaret      '           _____________________________a,           13.2.7  Console Management Options  G                    Some of the available console management options for                     OpenVMS:e  6                    o  http://www.robomon.com/ (Heroix)  D                    o  http://www.ki.com/products/clim/ (KI Products)  @                    o  http://www.globalmt.com/ (Global Maintech)  4                    o  http://www.tditx.com/ (TECsys)  D                    o  http://www.cai.com/products/commandit.htm (CA)  D           __________________________________________________________8           13.3  Where can I get the Mozilla Web Browser?  G                    Mozilla.org is an open source organization providingaE                    HTML-related tools; software that is the basis for G                    various utilities including the Mozilla web browser.   >                    OpenVMS Engineering is continuously portingJ                    Mozilla.org's web browser to OpenVMS, and OpenVMS portsE                    of the current Mozilla baselevels and releases areuG                    available. The OpenVMS Mozilla port includes the webjI                    browser, the mail client, the Composer HTML editor, ansH                    IRC chat client, a netnews (NNTP) reader, and various                    other tools.k  G                    The Mozilla web browser download and the developmentOH                    and release schedules for this and for other Mozilla-2                    related tools are available at:  -                    o  http://www.mozilla.org/i  J                    The available Compaq Secure Web Browser (CSWB) kit is a?                    packaged version of the Mozilla Web Browser.e  C                    A hardware configuration appropriate for MozillaoE                    generally involves an OpenVMS Alpha system with an F                    EV56 Alpha microprocessor, or an EV6 or more recentF                    processor, and with 256 megabytes of system memory.F                    The performance of Mozilla on EV5-based and earlierF                    Alpha microprocessor systems is generally viewed asH                    inadequate, this due to the extensive use of an AlphaF                    instruction subset that is first available with the2                    EV56 microprocessor generation.  J                                                                      13-17               -                    Finding and using Software         <                    Mozilla is not available for OpenVMS VAX.  I                    Various versions of the Netscape Navigator web browser 6                    are based on the Mozilla code-base.  F                    See section Section 13.8 for information on variousD                    certificates for the Netscape Navigator V3.03 webE                    browser; certificates that have presently expired.p  D           __________________________________________________________1           13.4  Where can I get Java for OpenVMS?w  D                    Java is available on and is included with OpenVMSH                    Alpha, starting with the OpenVMS Alpha V7.2 and laterI                    releases. Java download kits are available for OpenVMS 1                    Alpha V7.1 and later releases.   H                    Java is not available on OpenVMS VAX. As for why: theE                    Java language definition requires a floating point J                    format (IEEE) that is not native to VAX, and this wouldI                    require the emulation of all floating point operations G                    within Java applications. Further, the C source codegI                    used to implement for Java itself is heavily dependent I                    on passing IEEE floating point values around among the H                    many internal subroutines, and adding support for VAXH                    would entail changes to the HP C compiler for OpenVMSJ                    VAX-and specifically to the VAX VCG code generator thatI                    is used by HP C on OpenVMS VAX systems-in order to add I                    support for passing IEEE-format floating point doublesaG                    around. Alternatively, extensive changes to the Java/J                    source code to remove the assumption that the double is0                    an IEEE floating point value.  I                    There are currently no plans to make a version of Java J                    available for OpenVMS VAX. (A prototype version of JavaI                    was created for OpenVMS VAX, and performance was foundn.                    to be inadequate. At best.)  G                    If Java2 or other environment lifts the requirements B                    for IEEE floating point as part of the language>                    definition, this decision may be revisited.  J                    If you are having problems with Display Postscript, youI                    need to upgrade your Java kit-1.2.2-3 and later removewH                    the requirement for Display Postcript extensions, andF                    Java 1.2.2-3 is required with DECwindows V1.2-6 and                    later.o                      13-18 h  s          -                    Finding and using Software         H                    For additional information on Java for Alpha systems,I                    please see the OpenVMS documentation (V7.2 and later),o*                    and the following site:  A                    o  http://www.compaq.com/java/alpha/index.htmlx  F                    HP (Compaq) Secure Web Server (CSWS) includes CSWS_C                    JAVA, which provides the following Apache Tomcat/H                    technologies: JavaServer Pages 1.1, Java Servlet 2.2,G                    and MOD_JK. (CSWS is based on the Apache web server.                     See SOFT1.)  D           __________________________________________________________7           13.5  Obtaining user input in DCL CGI script?c  E                    If you choose to use the GET method, then the formwG                    data is available in the DCL symbol QUERY_STRING, ind&                    URL-encoded format.  H                    If you use the POST method, then you need to read theE                    form data from stdin. For a DCL CGI script running H                    under the Netscape FastTrack web server, you can read=                    the data using the following READ command:g  .                    $ READ SYS$COMMAND postdata  .                    to read the information in.  A                    The following describes the use of DCL command E                    procedures as CGI scripts with the OSU web server:   H                    o  http://www.levitte.org/~ava/cgiscripts_other.htmlx  G           DCL CGI is also discussed in the Writing Real Programs in DCLi2           book, and in the Ask The Wizard website.  D           __________________________________________________________C           13.6  How can a batch job get its own batch entry number?p  I                    To have a batch procedure retrieve its own batch entry -                    number, use the following:   8                    $ Entry = F$GETQUI("DISPLAY_ENTRY", -A                        "entry_number","display_entry","this_job")   J                                                                      13-19    o          -                    Finding and using Software         H                    Remember that the entry numbers issued by the OpenVMSG                    Job Controller are always opaque longword values. Do F                    not assume you know the format of the entry number,H                    nor the range of entry numbers you might see, nor theE                    algorithm that is used to assign enty numbers. Youe8                    should simply assume opaque longword.  D           __________________________________________________________6           13.7  How do I convert to new CMS libraries?  F                    A change was made to the format of the CMS databaseD                    for CMS libraries starting with V3.5-03-to ensureH                    that earlier versions of CMS are unable to access theI                    database once the "conversion" to V3.5-05 and later is)G                    made, you must issue the following two commands when J                    upgrading from V3.5-03 and prior. (The only differencesF                    between CMS version V3.5-03 and CMS version V3.5-05G                    involve changes to ensure that np earlier version ofm<                    CMS can access the "converted" database.)  C                    To perform the "conversion", issue the following 9                    commands for each CMS library present:   ;                    $ RENAME disk:[directory]00CMS.* 01CMS.*t9                    $ COPY NLA0: disk:[directory]00CMS.CMS   E                    The new file 00CMS.CMS must have the same security H                    settings as the 01CMS.CMS file, and is created solelyD                    to ensure continued compatibility with tools thatH                    expect to find a 00CMS.CMS file (eg: various versionsA                    of the Language-Sensitive text editor LSEDIT).,  F                    If you choose to install and use the longer variantJ                    names support that is available with CMS V4.1 or later,H                    you cannot mix earlier CMS versions within a cluster.F                    If you attempt to mix older and newer versions, youH                    will typically see the following BADLIB and BADTYPSTRI                    error sequence when accessing the CMS library from theo&                    older CMS versions:  L                    %CMS-F-BADLIB, there is something wrong with your libraryN                    -CMS-F-BADTYPSTR, header block type is 145; it should be 17  G                    Please see the CMS V4.1 release notes for additionalg#                    details on this.                       13-20 p  l          -                    Finding and using Softwaren      D           __________________________________________________________H           13.8  Where can I get new certificates for Netscape Navigator?  J                    The URLs that are available for adding or updating root$                    certificates are:  L                    o  http://www.entrust.net/customer/generalinfo/import.htm                       entrusti  3                    o  http://www.thawte.com/ thwateo  K                    o  https://www.verisign.com/server/prg/browser/root.htmlH                       verisign  H                    To update certificates in Netscape Navigator V3.03 on.                    OpenVMS, use the following:  C                    Thawte Server certificate which expired in 1998:   =                    1  Under the Options Menu choose "Securityp%                       Preferences..."   8                    2  Select the "Site Certificates" tab  >                    3  Select "Thawte Server CA" in the list of"                       certificates  ?                    4  Select "Delete Certificate" and then "OK"o  A                    5  Go to http://www.thawte.com/serverbasic.crte  E                    6  Follow the instructions on the popup dialog boxdE                       to accept the certificate This involves hitting F                       the "Next" button and clicking an accept button,D                       and then naming the resulting certificate. TheE                       certificate is usually named with the same name &                       as the original.  H                    VeriSign/RSA Server certificate which expired 31-Dec-                    1999:  =                    1  Under the Options Menu choose "Securityh%                       Preferences..."h  8                    2  Select the "Site Certificates" tab  H                    3  Select "Verisign/RSA Secure Server CA" in the list%                       of certificates   ?                    4  Select "Delete Certificate" and then "OK"o  Q                    5  Go to https://www.verisign.com/server/prg/browser/root.html/  J                                                                      13-21 a  s          -                    Finding and using Softwaren        H                    6  Follow the instructions on the popup dialog box toF                       accept the certificate This involves hitting theF                       "Next" button and clicking an accept button, andE                       then naming the resulting certificate. Verisign <                       suggests using the name "VeriSign CA".  D           __________________________________________________________9           13.9  Why doesn't DCL symbol substitution work?c  E                    The DCL symbol substitution processing occurs onlyaD                    at the DCL prompt, not within data and not withinG                    files. If you wish to perform symbol substitution inlE                    this environment, you typically write a small filenD                    containing the command(s) and data to be invoked-D                    potentially only the data-and you then invoke theE                    created procedure or reference the specified data.v  D                    In this case, use of a file containing nolinemodeH                    commands or other techniques might be useful-you willG                    want to ensure that the text editor you use does notfH                    attempt to use screen mode or similar, as this is notE                    generally considered adventageous within a commandt                    procedure.   A                    Tools such as FTP have alternatives: COPY/FTP.o  F                    DCL symbol substitution occurs in two passes, usingH                    the ampersand and the apostrophe. In most cases, onlyJ                    the apostrophe is necessary. In a few cases-such as theJ                    DCL PIPE command-you will may need to use the ampersandI                    to get the substitution to work. The following example J                    uses ampersand substitution to transfer the contents of2                    the header into a logical name:  W                    $ PIPE CC/VERSION | (READ SYS$PIPE hdr ; DEFINE/JOB/NOLOG hdr &hdr ))  H                    A logical name (in the job logical name table; sharedG                    by all processes in the current job) was used as DCL I                    symbols cannot be returned back out from a DCL PIPE orn,                    other spawned subprocess.                            13-22 e  S          -                    Finding and using Software       D           __________________________________________________________2           13.10  Where can I get Perl for OpenVMS?  >                    OpenVMS support is included in the standardG                    distribution of Perl, the popular scripting language C                    created by Larry Wall. In addition to nearly all.F                    of the functionality available under Unix, OpenVMS-J                    specific Perl modules provide interfaces to many nativeE                    features, as well as access to Oracle, Ingres, and J                    Sybase databases via the Perl DBI available on OpenVMS.  D                    A website useful for getting started with Perl onF                    OpenVMS-where you will find such things as downloadC                    links, instructions, auxiliary tools, and sample +                    scripts-is available at:   2                    o  http://www.sidhe.org/vmsperl  C                    If you have a C compiler, the best way to obtain H                    Perl is to download and build it yourself. The latestC                    production quality source kit is available from:e  @                    o  http://www.perl.com/CPAN/src/stable.tar.gz  G                    You will need GUNZIP and VMSTAR (both available fromvC                    the OpenVMS Freeware CD, or from other sites) toEF                    unpack the archive; once you've done that, read the7                    instructions in the README.vms file.v  >                    Binary distributions for most Alpha and VAXI                    environments are available on the OpenVMS Freeware CD- J                    ROM and from various websites, including the following:  @                    o  http://www.sidhe.org/vmsperl/prebuilt.html  C                    o  http://www.openvms.compaq.com/freeware/perl5/   G                    During active Perl development cycles, test kits are ,                    sometimes found at: from:  *                    o  ftp://ftp.sidhe.org/  D                    Watch the mailing list (see below) for details on)                    experimental releases.   J                                                                      13-23 k  a          -                    Finding and using Softwareh        C                    Charles Lane maintains pages on how to write CGI F                    scripts in Perl for the OSU HTTP server, as well asJ                    more general tips, tricks, and patches for building and+                    running Perl on OpenVMS:   :                    o  http://www.crinoid.com/crinoid.htmlx  I                    There are OpenVMS-specific Perl modules that implement/E                    interfaces to a subset of the VMS System Services. J                    With these modules, you can get (and often set) device,I                    job, queue, user, system, and performance information. I                    The lock manager, RMS indexed files, screen management I                    utilities, and Intracluster Communication Services are I                    also accessible via Perl. The relevant modules are all "                    available from:  D                    o  http://www.perl.com/CPAN/modules/by-module/VMS  C                    To subscribe to the OpenVMS Perl mailing list (atA                    discussion forum for both user support and new B                    development), send an email message to vmsperl-%                    subscribe@perl.orgw  @                    The mailing list archives may be searched at:  F                    o  http://www.xray.mpe.mpg.de/mailing-lists/vmsperl  D           __________________________________________________________D           13.11  Obtaining the DECmigrate (VEST and TIE) translator?  E                    The DECmigrate image translation tool, a tool thatTI                    translates OpenVMS VAX images for use on OpenVMS Alphab#                    is available at:   C                    o  http://www.openvms.compaq.com/products/omsva/   E                    VEST is the name sometimes given to the DECmigratepH                    translation tool, while TIE names the DECmigrate run-$                    time environment.  G                    Please see Section 7.4 and Section 13.13 for related                     information.s                        13-24    N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faq N  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.com    ------------------------------  # Date: Thu, 03 Jul 2003 17:16:10 GMTs2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman); Subject: OpenVMS Frequently Asked Questions (FAQ), Part 7/9o1 Message-ID: <uxZMa.3897$bl3.445@news.cpqcorp.net>a    b          -                    Finding and using Software       D           __________________________________________________________F           13.12  Where can I get Zip, Unzip, self-extracting zip, etc?  D                    Many packages are provided in ZIP, GZIP, or BZIP2G                    format, which requires you to acquire the associated I                    unzip tool to unpack it. You can get ZIP and UNZIP andgF                    related and similar tools from the following areas:  Q                    o  http://www.openvms.compaq.com/freeware/freeware50/000tools/T  N                    o  http://www.openvms.compaq.com/freeware/freeware50/bzip2/  M                    o  http://www.openvms.compaq.com/freeware/freeware50/info-v                       zip/  Q                    o  http://www.openvms.compaq.com/freeware/freeware40/000tools/l  H                    o  ftp://ftp.process.com/vms-freeware/unzip.alpha_exe  F                    o  ftp://ftp.process.com/vms-freeware/unzip.vax_exe  C                    o  http://www.decus.de:8080/www/vms/sw/zip.htmlx   4                    o  http://www.djesys.com/zip.html  6                    o  http://www.djesys.com/unzip.html  I                    or you can request the FILESERV_TOOLS package from then!                    e-mail server.   6                    Beware: The [000TOOLS...] pre-built=                    versions of ZIP on the OpenVMS Freeware V4CG                    (http://www.openvms.compaq.com/freeware/freeware40/) H                    CD-ROM will erroneously return BILF errors on OpenVMSG                    V7.2 and later. Use of the source on the Freeware V4/H                    to rebuild the ZIP image(s), or acquiring a pre-builtH                    ZIP image from one of the above areas can avoid this.I                    The pre-built version of ZIP on the Freeware V4 kit iseI                    older than the included ZIP sources, and it contains a                     latent bug.]i  C                    Directions for creaating and using the sfx self-.J                    extracting zip file compression mechanism are available9                    in the unzip kit that is available at:   Q                    o  http://www.openvms.compaq.com/freeware/freeware50/unzip542/                        Specifically:  ]                    o  http://www.openvms.compaq.com/freeware/freeware50/UNZIP542/UNZIPSFX.TXTi  J                                                                      13-25               -                    Finding and using Softwarer        H                    If you want to build the zip images for yourself (eg:F                    for an older OpenVMS version), pull over the entire                    contents of:a  U                    o  http://www.openvms.compaq.com/freeware/freeware50/unzip542/vms-                        binaries/.  '                    and invoke LINK.COM.   C                    HP OpenVMS Engineering uses a tool known as FTSV F                    for creating self-extracting compressed files usingB                    the OpenVMS DCX compression tools, as seen withH                    various OpenVMS ECO (patch) kits. sfx provides betterF                    compression than does DCX. The FTSV and its relatedJ                    FTSO package have only limited availability outside HP,1                    and are not standard products.   D           __________________________________________________________6           13.13  Are VAX Hardware Emulators Available?  G                    Software-based emulators of the VAX architecture and I                    for specific VAX hardware platforms are available from #                    various sources:   $                    o  SRI CHARON-VAX0                       http://www.softresint.com/  &                    o  Tim Stark's TS10;                       http://sourceforge.net/projects/ts10/U  0                    o  Bob Supnik's Trailing Edge4                       http://simh.trailing-edge.com/  E                    VAX emulators that operate on PC systems and/or on.G                    OpenVMS Alpha systems are available. For information D                    on an alternative to using a VAX emulator- on theH                    available DECmigrate VAX executable image translator-,                    please see Section 13.11.                                13-26                         J                    _______________________________________________________  '           14       Hardware Information       D           __________________________________________________________F           14.1  What are the OpenVMS differences among VAX, Alpha, and                 IA-64?  F                    In terms of software, very few. As of OpenVMS V6.1,I                    the VAX and Alpha platforms are very close to "feature I                    parity". OpenVMS on IA-64 is expected to have "feature:G                    parity" with OpenVMS Alpha, and is based on the same H                    source pool. Most applications can just be recompiled<                    and run. Some differences to be aware of:  C                    o  The default double-precision floating type on E                       OpenVMS Alpha is VAX G_float, whereas on VAX ithH                       is usually D_float. D_float is available on Alpha,E                       but D_float values are converted to G_float forlJ                       computations and then converted back to D_float whenF                       stored. Because the G_float type has three fewerG                       fraction bits than D_float, some applications may F                       get different results. IEEE float types are also1                       available on OpenVMS Alpha.   F                    o  The preferred floating point format on Alpha and$                       IA-64 is IEEE.  D                    o  Data alignment is extremely important for bestF                       performance on Alpha. This means that data itemsF                       should be allocated at addresses which are exactG                       multiples of their sizes. Quadword alignment will J                       offer the best performance, especially for characterF                       values and those smaller than 32 bits. CompilersG                       will naturally align variables where they can and G                       will issue warnings if they detect unaligned data                        items.  F                    o  HP C is the only C compiler HP offers on OpenVMSG                       Alpha, and is a direct descendant of Compaq C andtI                       DEC C on OpenVMS Alpha. HP C is compatible with DECaF                       C on OpenVMS VAX, but is somewhat different fromG                       the older VAX C compiler most people are familiar   J                                                                       14-1 n  t          '                    Hardware Informationy        F                       with. Read up on the /EXTERN_MODEL and /STANDARDF                       qualifiers to avoid the most common problems. InJ                       additon to HP C, there are open-source ports such as2                       Gnu C available for OpenVMS.  A                    o  The page size on Alpha and IA-64 systems is E                       variable, but is at least 8 kilobytes. This canlD                       have some effect on applications which use theI                       $CRMPSC system service as well as on the display ofiH                       available memory pages. The page size is available3                       from $GETSYI(SYI$_PAGE_SIZE).f  C                    There are also a number of manuals which discussy>                    migration to OpenVMS Alpha available on the?                    documentation CD-ROM media, both in the mainsB                    documentation and in the archived documentation                    section.I  G                    On more recent OpenVMS Alpha versions, OpenVMS Alpha I                    has begun to add features and support not available ontH                    OpenVMS VAX. Salient new areas include the following:  G                    o  64-bit addressing in OpenVMS Alpha V7.0 and latero  J                    o  Multi-host SCSI support (SCSI TCQ) in V6.2 and later  6                    o  PCI support (platform-dependent)  >                    o  OpenVMS Galaxy support in V7.2 and later  D           __________________________________________________________C           14.2  Seeking performance information for Alpha (and VAX)s                 systems?  A                    HP makes a wide range of performance documents E                    available through its FTP and WWW Internet servers.%                    (see Section 3.2).M  I                    The following contain information on current Alpha ands                     VAX products:  D                    o  http://www.compaq.com/alphaserver/servers.html  F                    o  http://www.compaq.com/alphaserver/vax/index.html  E                    The following sites contain information on various,2                    retired VAX and Alpha products:  J                    o  http://www.compaq.com/alphaserver/archive/index.html                      14-2     H          '                    Hardware Information         I                    o  http://www.compaq.com/alphaserver/performance/perf__                       tps.html  $                    Also see CPU2000:  6                    o  http://www.spec.org/osg/cpu2000/  J                    o  http://www.spec.org/osg/cpu2000/results/cpu2000.html  D           __________________________________________________________=           14.3  Console Commands, Serial Lines, and Controls?   E                    This section contains information on VAX and Alpha E                    consoles, and details related to console commands, <                    serial lines, and configuration settings.  '           _____________________________rG           14.3.1  What commands are available in the Alpha SRM console?n  H                    In addition to the normal BOOT commands and such (seeD                    Section 14.3.5.1 for some details) and the normalE                    contents of the console HELP text, operations such I                    as I/O redirection and floppy disk access are possible -                    at the SRM console prompt:L  A                    1  Format a FAT floppy, and insert it into theh0                       AlphaStation floppy drive.  I                    2  Perform the following at AlphaStation SRM Console :e  -                          >>> show * > env.datf1                          >>> show conf > conf.dat ;                          >>> cat env.dat > fat:env.dat/dva0t=                          >>> cat conf.dat > fat:conf.dat/dva0   E                    3  You may use the SRM "ls" command to display theS-                       contents of the floppy.p  0                          >>> ls fat:env.dat/dva01                          >>> ls fat:conf.dat/dva0g  C                    4  You can now transfer the FAT-format floppy ton%                       another system.h  J                                                                       14-3               '                    Hardware Information       '           _____________________________ 6           14.3.2  What does SRM mean? What is PALcode?  H                    The abbreviation SRM is derived from the Alpha SystemC                    Reference Manual, the specification of the Alpha <                    architecture and the associated firmware.  D                    PALcode is a name assigned to a particular set ofB                    functions provided by the SRM firmware. PALcodeE                    is used to provide low-level functions required byCI                    higher-level operating system or application software, I                    functions which may not be directly available in Alpha C                    hardware. PALcode is implemented using available D                    Alpha instructions and using the Alpha processor,E                    though PALcode operates in a mode which simplifiesXC                    programming. PALcode is also permitted access to E                    processor-specific and otherwise internal featurescG                    of a particular Alpha microprocessor implementation;sH                    microprocessor-specific features which are not easilyF                    accessable to operating system or application code.  '           _____________________________iJ           14.3.3  Alpha COM ports and VAX console serial line information?  E                    This section contains information on the Alpha COM H                    communication ports, and related settings, as well asJ                    on the VAX console bulkhead and VAX console serial line                    connection.  '           _____________________________nE           14.3.3.1  Which terminal device name is assigned to the COM                      ports?  D                    COM2 is normally TTA0:. COM1 is normally TTB0: ifG                    the Alpha workstation is booted with the SRM consolecH                    environment variable set to graphics, and is OPA0: if0                    the console is set to serial.  '           ______________________________J           14.3.3.2  Which serial port is the console on the MicroVAX 3100?  G                    Just to keep life interesting, the MicroVAX 3100 haszD                    some "interesting" console ports behaviours basedF                    on the setting of the BREAK enable switch. When theD                    console is not enabled to respond to BREAK, MMJ-1G                    is the console port. MMJ-3 will (confusingly) output,                      14-4                '                    Hardware Informationr        F                    the results of the selftest in parallel with MMJ-1.I                    When the console is enabled to respond to BREAK, MMJ-3 I                    becomes the console port, and MMJ-1 will (confusingly) I                    output the results of selftest in parallel with MMJ-3.d  '           _____________________________ J           14.3.3.3  How can I set up an alternate console on a VAXstation?  F                    Most VAXstation systems have a switch-often labeledH                    S3-that enables one of the serial lines as the system                    console.   G                    Various members of the DEC 3000 series Alpha systemshJ                    also have a similarly-labled S3 switch for selection of)                    the alternate console.   >                    Also see Section 14.3.6, Section 11.11, and!                    Section 14.19.   '           _____________________________ D           14.3.3.4  Please explain the back panel of the MicroVAX II  I                    The MicroVAX-series console bulkhead was used with the 2                    KA630, KA650, KA655 processors.  F                    There are three controls on the console bulkhead of!                    these systems:5  <                      Triangle-in-circle-paddle: halt enable.@                        dot-in-circle: halt (<break>) is enabled,@                                       and auto-boot is disabled.E                        dot-not-in-circle: halt (<break>) is disabled,r?                                       and auto-boot is enabled.   H                      Three-position-rotary: power-up bootstrap behaviour/                        arrow: normal operation. 3                        face: language inquiry mode..<                        t-in-circle: infinite self-test loop.  G                      Eight-position-rotary: console baud rate selection_G                        select the required baud rate; read at power-up.   B                    There are several different bulkheads involved,C                    including one for the BA23 and BA123 enclosures, B                    and one for the S-box (BA2xx) series enclosure.F                    The console bulkheads typically used either the MMJC                    serial line connection, or the MicroVAX DB9 (not   J                                                                       14-5    r          '                    Hardware Informationd        E                    the PC DB9 pinout), please see the descriptions of G                    these in section WIRES1. For available adapters, see !                    Section 14.29.f  F                    Also present on the console bulkhead is a self-testJ                    indicator: a single-digit LED display. This matches theJ                    final part of the countdown displayed on the console orI                    workstation, and can be used by a service organization F                    to determine the nature of a processor problem. TheD                    particular countdown sequence varies by processorC                    type, consult the hardware or owner's manual fornG                    the processor, or contact the local hardware servicecF                    organization for information the self-test sequenceJ                    for a particular processor module. Note that self-testsI                    2, 1 and 0 are associated with the transfer of controlXF                    from the console program to the (booting) operating                    system.  '           _____________________________.?           14.3.4  What are Alpha console environment variables?f  H                    Alpha systems have a variety of variables with valuesJ                    set up within the SRM system console. These environmentD                    variables control the particular behaviour of theJ                    console program and the system hardware, the particularG                    console interface presented to the operating system,iB                    various default values for the operating systemE                    bootstrap, and related control mechanisms-in otherhF                    words, "the environment variables provide an easilyD                    extensible mechanism for managing complex console                    state."  H                    The specific environment variables differ by platformJ                    and by firmware version-the baseline set is established-                    by the Alpha Architecture:S  J                    AUTO_ACTION ("BOOT", "HALT", "RESTART", any other valueK                    assumed to be HALT),  BOOT_DEV, BOOTDEF_DEV, BOOTED_DEV,aH                    BOOT_FILE, BOOTED_FILE, BOOT_OSFLAGS, BOOTED_OSFLAGS,J                    BOOT_RESET ("ON", "OFF"), DUMP_DEV, ENABLE_AUDIT ("ON",@                    "OFF"), LICENSE, CHAR_SET, LANGUAGE, TTY_DEV.                          14-6C G  c          '                    Hardware Informationh        F                    OpenVMS Galaxy firmware can add console environmentJ                    variables beginning with such strings as LP_* and HP_*,F                    and each particular console implementation can (andF                    often does) have various sorts of platform-specific7                    extensions beyond these variables...a  F                    The contents of a core set of environment variablesI                    are accessible from OpenVMS using the f$getenv lexicaldF                    and the sys$getenv system service. (These calls areE                    first documented in V7.2, but have been around forhI                    quite a while.) Access to arbitary console environmentsF                    variables is rather more involved, and not directly                    available.   '           _____________________________ 8           14.3.5  What are the boot control flag values?  E                    Both VAX and Alpha primary bootstraps support flag G                    values; a mechanism which permits the system manager F                    to perform specific customizations or site-specificH                    debugging of the OpenVMS system bootstrap. While veryG                    similar, there are differences between VAX and Alpha (                    systems in this area.  '           _____________________________F<           14.3.5.1  What are the Alpha APB boot flag values?  F                    The following flags are passed (via register R5) toE                    the OpenVMS Alpha primary bootstrap image APB.EXE.aF                    These flags control the particular behaviour of the                    bootstrap:i  &                    BOOT -FL root,flags  ,                         bit      descriptionL                         ---   ----------------------------------------------                J                                                                       14-7    r          '                    Hardware Informationh        @                          0    CONV      Conversational bootstrapF                          1    DEBUG     Load SYSTEM_DEBUG.EXE (XDELTA)c                          2    INIBPT    Stop at initial system breakpoints if bit 1 set (EXEC_INIT))Q                          3    DIAG      Diagnostic bootstrap (loads diagboot.exe) W                          4    BOOBPT    Stop at bootstrap breakpoints (APB and Sysboot)tY                          5    NOHEADER  Secondary bootstrap does not have an image headeru;                          6    NOTEST    Inhibit memory testcK                          7    SOLICIT   Prompt for secondary bootstrap fileoS                          8    HALT      Halt before transfer to secondary bootstrap <                          9    SHADOW    Boot from shadow set:                          10   ISL       LAD/LAST bootstrapD                          11   PALCHECK    Disable PAL rev check haltT                          12   DEBUG_BOOT  Transfer to intermediate primary bootstrap>                          13   CRDFAIL       Mark CRD pages badT                          14   ALIGN_FAULTS  Report unaligned data traps in bootstrapS                          15   REM_DEBUG   Allow remote high-level language debuggerhS                          16   DBG_INIT    Enable verbose boot messages in EXEC_INITa`                          17   USER_MSGS   Enable subset of verbose boot messages (user messages)C                          18   RSM         Boot is controlled by RSMrH                          19   FOREIGN     Boot involves a "foreign" disk  J                    If you want to set the boot flags "permanently" use the/                    SET BOOT_FLAGS command, e.g.   +                    >>> SET BOOT_OSFLAGS 0,1m  '           _____________________________ :           14.3.5.2  What are the VAX VMB boot flag values?  F                    The following flags are passed (via register R5) toC                    the OpenVMS VAX primary bootstrap image VMB.EXE.1F                    These flags control the particular behaviour of the                    bootstrap:_  C                    The exact syntax is console-specific, recent VAX 6                    consoles tend to use the following:  &                      >>> BOOT/R5:flags  $                      Bit     Meaning$                      ---     -------                          14-8t s  e          '                    Hardware Informationr        '                       0      RPB$V_CONVoJ                              Conversational boot. At various points in theF                              system boot procedure, the bootstrap codeH                              solicits parameter and other input from theK                              console terminal.  If the DIAG is also on thenhJ                              the diagnostic supervisor should enter "MENU"J                              mode and prompt user for the devices to test.  (                       1      RPB$V_DEBUGK                              Debug.  If this flag is set, VMS maps the code I                              for the XDELTA debugger into the system page":                              tables of the running system.  )                       2      RPB$V_INIBPTwK                              Initial breakpoint. If RPB$V_DEBUG is set, VMShI                              executes a BPT instruction immediately aftero.                              enabling mapping.  )                       3      RPB$V_BBLOCKcK                              Secondary boot from the boot block.  SecondarymL                              bootstrap is a single 512-byte block, whose LBN0                              is specified in R4.  '                       4      RPB$V_DIAGnK                              Diagnostic boot.  Secondary bootstrap is imageh;                              called [SYSMAINT]DIAGBOOT.EXE.   )                       5      RPB$V_BOOBPTSH                              Bootstrap breakpoint. Stops the primary andC                              secondary bootstraps with a breakpoint ?                              instruction before testing memory.e  )                       6      RPB$V_HEADER L                              Image header. Takes the transfer address of theG                              secondary bootstrap image from that file'seG                              image header.  If RPB$V_HEADER is not set,eG                              transfers control to the first byte of theo1                              secondary boot file.   )                       7      RPB$V_NOTEST.K                              Memory test inhibit. Sets a bit in the PFN bit K                              map for each page of memory present.  Does not -                              test the memory.c  )                       8      RPB$V_SOLICTuE                              File name. VMB prompts for the name of a 6                              secondary bootstrap file.  J                                                                       14-9 ,  u          '                    Hardware Informationc        '                       9      RPB$V_HALT C                              Halt before transfer.  Executes a HALT D                              instruction before transferring control8                              to the secondary bootstrap.  )                      10      RPB$V_NOPFNDrJ                              No PFN deletion (not implemented; intended toM                              tell VMB not to read a file from the boot deviceeJ                              that identifies bad or reserved memory pages,K                              so that VMB does not mark these pages as valid 0                              in the PFN bitmap).  &                      11      RPB$V_MPMK                              Specifies that multi-port memory is to be usedeM                              for the total EXEC memory requirement.  No localyO                              memory is to be used.  This is for tightly-coupledeL                              multi-processing.  If the DIAG is also on, thenN                              the diagnostic supervisor enters "AUTOTEST" mode.  )                      12      RPB$V_USEMPMeO                              Specifies that multi-port memory should be used indN                              addition to local memory, as though both were one2                              single pool of pages.  *                      13      RPB$V_MEMTESTN                              Specifies that a more extensive algorithm be usedB                              when testing main memory for hardware8                              uncorrectable (RDS) errors.  *                      14      RPB$V_FINDMEME                              Requests use of MA780 memory if MS780 iseG                              insufficient for booting.  Used for 11/782n+                              installations.s  )                      <31:28> RPB$V_TOPSYSuI                              Specifies the top level directory number for @                              system disks with multiple systems.                                  14-10 l  p          '                    Hardware Information       '           _____________________________ B           14.3.6  How do I boot an AlphaStation without monitor or                   keyboard?   G                    The AlphaStation series will boot without a keyboardOE                    attached. To use a serial terminal as the console,lC                    issue the SRM console command SET CONSOLE SERIALsF                    followed by the console INIT command. Once this SRMF                    command sequence has been invoked, the Alpha system0                    will use the serial terminal.  F                    The DEC 3000 series has a jumper on the motherboardE                    for this purpose. Various older Alpha workstations/I                    generally will not (automatically) bootstrap without aRH                    keyboard connected, due to the self-test failure thatA                    arises when the (missing) keyboard test fails.'  I                    The usual settings for the console serial terminal (oreG                    PC terminal emulator acting as a serial console are:   O                    9600 baud, 8 bits, no parity, one stop bit (9600 baud, 8N1).   D                    AlphaServer 4100 and derivative series platforms,G                    and AlphaServer GS80, GS160, and GS320 series system H                    consoles are capable of 57600 baud. See the COM2_BAUDI                    console environment variable, and ensure that you have 7                    current SRM firmware version loaded.:  E                    The AlphaStation and AlphaServer series use the PC H                    DIN serial connector for the "COM1" and "COM2" serialC                    lines, see Section 14.28 for details and pinout.a  '           _____________________________u=           14.3.7  Downloading and using SRM console Firmware?n  E                    This section discusses downloading and using AlphaO>                    console firmware, sometimes called PALcode.  '           _____________________________ F           14.3.7.1  Where can I get updated console firmware for Alpha                     systems?  F                    Firmware updates for HP Alpha systems are available                    from:  Q                    o  ftp://ftp.digital.com/pub/Digital/Alpha/firmware/index.htmlu  G                    o  ftp://ftp.digital.com/pub/Digital/Alpha/firmware/e  J                                                                      14-11 S  d          '                    Hardware Informationu        R                    o  ftp://ftp.digital.com/pub/Digital/Alpha/firmware/readme.html  G                    The latest and greatest firmware-if updated firmware J                    has been released after the most recent firmware CD was-                    distributed-is located at:r  O                    o  ftp://ftp.digital.com/pub/Digital/Alpha/firmware/interim/e  @                    For information on creating bootable floppiesI                    containing the firmware, and for related tools, pleaseg+                    see the following areas:   W                    o  ftp://ftp.digital.com/pub/DEC/Alpha/firmware/utilities/mkboot.txt_  Z                    o  ftp://ftp.digital.com/pub/DEC/Alpha/firmware/utilities/mkbootarc.txt  Y                    o  ftp://ftp.digital.com/pub/DEC/Alpha/firmware/utilities/mkntboot.txt   F                    The SROM firmware loader expects an ODS-2 formattedI                    floppy, see mkboot. As for which image to use, the ROMoG                    image uses a header and the file extension .ROM, and E                    the SROM bootable floppy cannot use the .ROM file.,  G                    To check the firmware loaded on recent OpenVMS Alpha ,                    systems, use the command:  A                    $ write sys$output f$getsyi("console_version") A                    $ write sys$output f$getsyi("palcode_version")e#                    SDA> CLUE CONFIG-  -                    Also see Section 14.3.7.2.Q  '           _____________________________-F           14.3.7.2  How do I reload SRM firmware on a half-flash Alpha                     system?O  E                    Some of the AlphaStation series systems are "half- I                    flash" boxes, meaning only one set of firmware (SRM orHG                    AlphaBIOS) can be loaded in flash at a time. GettingoF                    back to the SRM firmware when AlphaBIOS (or ARC) is8                    loaded can be a little interesting...  I                    That said, this usually involves shuffling some files,1F                    and then getting into the AlphaBIOS firmware updateH                    sequence, and then entering "update srm" at the apu->                    prompt.                      14-12               '                    Hardware InformationI        J                    To shuffle the files, copy the target SRM firmware fileG                    (as200_v7_0.exe is current) to a blank, initialized,wG                    FAT-format floppy under the filename A:\FWUPDATE.EXEr  F                    From the AlphaBIOS Setup screen, select the UpgradeJ                    AlphaBIOS option. Once the firmware update utility gets                     going, enter:  (                         Apu-> update srm  C                               Answer "y" to the "Are you ready...?"   "                         Apu-> quit  H                    You've reloaded the flash. Now power-cycle the box to&                    finish the process.  -                    Also see Section 14.3.7.1.   '           _____________________________nA           14.3.7.3  How do I switch between AlphaBIOS/ARC and SRMS                     consoles?   G                    The specific steps required vary by system. You mustbC                    first ensure that the particular Alpha system is H                    supported by OpenVMS (see the SPD), that all core I/OF                    components (graphics, disk controllers, etc) in theJ                    system are supported by OpenVMS (see the SPD), and thatF                    you have an OpenVMS distribution, that you have theG                    necessary license keys (PAKs), and that you have the.1                    necessary SRM firmware loaded.n  F                    A typical sequence used for switching over from theI                    AlphaBIOS graphics console to the SRM console follows:   D                    1  Press <F2> to get to the AlphaBIOS setup menu.  4                    2  Pick the "CMOS Setup..." item.  J                    3  Press <F6> to get to the "Advanced CMOS Setup" menu.  H                    4  Change the "Console Selection" to "OpenVMS Console                       (SRM)".:  C                    5  Press <F10>, <F10>, then <Enter> to save yourr                       changes.  -                    6  Power-cycle the system.   J                                                                      14-13 f  r          '                    Hardware Information         >                    Most Alpha systems support loading both theH                    AlphaBIOS/ARC console and the SRM console at the sameE                    time, but systems such as the AlphaStation 255 areiG                    "half-flash" systems and do not support the presencevH                    of both the AlphaBIOS/ARC and SRM console firmware atH                    the same time. If you have a "half-flash" system, youI                    must load the SRM firmware from floppy, from a networkiE                    download, or from a firmware CD-ROM. Following theeF                    normal AlphaBIOS or ARC firmware update sequence toG                    the APU prompt, and then explictly select the targetiF                    console. In other words, power up the system to theJ                    AlphaBIOS or ARC console, use the supplementary optionsH                    to select the installation of new firmware (typicallyF                    from CD-ROM), and then rather than using a sequence6                    which updates the current firmware:  #                        Apu-> update                           -or- '                        Apu-> update ARCo#                        Apu-> verify'!                        Apu-> quit/-                        Power-cycle the system   I                    Use the following sequence to specifically update (andiI                    load) SRM from AlphaBIOS/ARC on a "half-flash" system:   '                        Apu-> update SRMa#                        Apu-> verifyo!                        Apu-> quita-                        Power-cycle the system   I                    Use the following sequence to specifically update (and G                    load) the AlphaBIOS/ARC console from SRM on a "half- !                    flash" system:   *                        >>> b -fl 0,A0 ddcu7                        BOOTFILE: firmware_boot_file.exeo  '                        Apu-> update ARC_#                        Apu-> verify !                        Apu-> quitd-                        Power-cycle the system                         14-14    m          '                    Hardware Information         I                    Once you have the SRM loaded, you can directly install D                    OpenVMS or Tru64 UNIX on the system. Do not allowI                    Windows NT to write a "harmless" signature to any disk F                    used by OpenVMS, Tru64 UNIX, or Linux, as this willG                    clobber a key part of the disk. (On OpenVMS, you can I                    generally recover from this "harmless" action by usingp'                    the WRITEBOOT tool.)X  G                    If you have a "full-flash" system and want to selecthD                    the SRM console from the AlphaBIOS or ARC consoleF                    environment, select the "Switch to OpenVMS or Tru64B                    UNIX console" item from the "set up the system"F                    submenu. Then power-cycle the system. If you have aG                    "full-flash" system with the SRM console and want toy9                    select AlphaBIOS/ARC, use the command:p  (                       >>> set os_type NT  .                    and power-cycle the system.  =                    For information on acquiring firmware, see G                    Section 14.3.7.1. For information on OpenVMS license A                    PAKs (for hobbyist use) see Section 2.7.3. ForeA                    information on the Multia, see Section 14.4.1.t  J                    Information on enabling and using the failsafe firmwareI                    loader for various systems-this tool is available onlysI                    on some of the various Alpha platforms-is available invJ                    the hardware documentation for the system. This tool isH                    used/needed when the firmware has been corrupted, and,                    cannot load new firmware.  A                    The full list of AlphaBIOS key sequences-thesefH                    sequences are needed when using an LK-series keyboardB                    with AlphaBIOS, as AlphaBIOS expects a PC-style                    keyboard:                J                                                                      14-15               '                    Hardware Information         '                             F1   Ctrl/Ay'                             F2   Ctrl/Bd'                             F3   Ctrl/C '                             F4   Ctrl/Dh'                             F5   Ctrl/E '                             F6   Ctrl/Fo'                             F7   Ctrl/P '                             F8   Ctrl/R '                             F9   Ctrl/T-'                            F10   Ctrl/Ui'                         Insert   Ctrl/Va'                         Delete   Ctrl/Wt'                      Backspace   Ctrl/H '                         Escape   Ctrl/[l'                         Return   Ctrl/M '                       LineFeed   Ctrl/J 8                       (Plus) +   upselect (some systems):                      (Minus) -   downselect (some systems)+                            TAB   down arrowa)                       SHIFT+TAB  up arrow   D           __________________________________________________________7           14.4  What platforms will OpenVMS operate on?   I                    For the list of boxes that are officially and formallyhC                    supported by OpenVMS Engineering, please see ther>                    OpenVMS Software Product Description (SPD).  5                    o  http://www.compaq.com/info/spd/ D                       OpenVMS typically uses SPD 25.01.xx and/or SPD                       41.87.xx.u  '           _____________________________ &           14.4.1  on the Alpha Multia?  I                    Yes, there are a set of unsupported images that permit F                    specific OpenVMS Alpha versions to bootstrap on theE                    Multia UDB system. These images and the associated E                    instructions are available at the OpenVMS Freewaref                    website:   O                    o  http://www.openvms.compaq.com/freeware/freeware50/multia/e  B                    Instructions are included IN the kits. READ THE(                    INSTRUCTIONS. PLEASE!                      14-16               '                    Hardware Informationl        I                    Some of the restrictions involved when running OpenVMS D                    on the Multia system include (but may well not be-                    limited to) the following:   H                    o  The PCMCIA support was completely removed, becauseJ                       the Intel chip on the Multia was not compatable with7                       the Cirrus chip on the Alphabook.m  F                       This means, of course, that you will not see and>                       cannot use any PCMCIA cards on a Multia.  I                       The Multia uses shared interrupts, and as a result,sH                       a special ZLXp-E series graphics device driver-oneI                       that does not use interrupts-is needed. This drivers-                       is provided in the kit.t  2                    o  The serial lines don't work.  I                    o  If you have a Multia with a PCI slot, you can't use <                       any PCI card that requires interrupts.  D                    o  The SRM console on this system is very old andB                       very fragile. (This SRM console was designedG                       only and strictly for diagnostic use, and was not @                       particularly tested or used with OpenVMS.)  G                    o  If things don't work for you, don't expect to seeoG                       any OpenVMS updates, nor SRM console updates, nors"                       any support.  F                    o  Do not expect to see any new versions of OpenVMSI                       on the Multia nor on any other unsupported systems.pH                       If such new versions do appear and do work, please9                       consider it as a pleasant surprise.   D                    The Multia images are not included on the OpenVMSI                    Freeware V4.0 CD-ROM kit, the kit that was distributed J                    with OpenVMS V7.2. (These images became available after*                    Freeware V4.0 shipped.)  E                    Other sources of information for OpenVMS on Multiaa                    include:o  D                    o  http://www.djesys.com/vms/hobbyist/multia.html  F                    o  http://www.djesys.com/vms/hobbyist/mltianot.html  E                    o  http://www.djesys.com/vms/hobbyist/support.htmlo  F                    o  http://www.netbsd.org/Ports/alpha/multiafaq.html  J                                                                      14-17 r  d          '                    Hardware Informatione        F                    o  http://www.brouhaha.com/~eric/computers/udb.html  '           _____________________________ 2           14.4.2  on AlphaPC 164LX? AlphaPC 164SX?  J                    OpenVMS Alpha is not supported on the AlphaPC 164LX andH                    164SX series, though there are folks that have gottenE                    certain of the LX series to load SRM and bootstrap I                    OpenVMS. (The Aspen Durango II variant, specifically.)   E                    One problem has been generally reported: ATA (IDE) G                    bootstraps will fail; SCSI storage and a SCSI CD-ROM &                    device is required.  -                    Also see Section 14.4.2.1.A  '           _____________________________ 2           14.4.2.1  on the NoName AXPpci33 system?  I                    Information on bootstrapping OpenVMS (using the MultiaaJ                    files described in Section 14.4.1) on the (unsupported):                    NoName AXPpci33 module is available at:  C                    o  http://www.jyu.fi/~kujala/vms-in-axppci33.txt   <           Tips for using the Multia files with the AXPpci33:  C                    o  You have to use the Multia kit and follow theOH                       directions in ALPHA8, but do *not* load the MultiaJ                       SRM firmware into the AXPpci33. Rather, download andJ                       use the latest firmware for the AXPpci33 from the HP5                       Alpha firmware website instead.s  :                    o  64 MB memory is generally necessary.  F                    o  you cannot use any PCI cards, and if you plan onG                       networking, you need to find an ISA Ethernet card +                       supported by OpenVMS.i  F                    o  When the AXPpci33 board bootstraps, it will dumpH                       some stuff like a crash dump, but it will continueB                       and-so far-this hasn't caused any particular                       hassles.  F                    o  The system shutdown and reboot procedures do not$                       work properly.                      14-18 h  t          '                    Hardware Informations        H                    o  The serial console is reported to not work, thoughH                       the serial ports apparently do work. The status of3                       the parallel port is unknown.   E                    o  Rumour has it that you have one of the AXPpci33WC                       motherboards with the PS/2 mouse and keyboard C                       connectors and a VGA card (one that will work E                       under DECwindows) and you can run DECwindows on !                       the system._  '           _____________________________ )           14.4.3  on the Alpha XL series?   D                    No. OpenVMS does not support the Alpha XL series.  G                    OpenVMS can not, will not, and does not bootstrap on H                    the Alpha XL series. The Alpha XL series was targetedI                    for use (only) with the Microsoft Windows NT operatings                    system.  @                    If you are very lucky, sometimes a particularE                    unsupported Alpha box or motherboard will resemble J                    a supported box sufficiently closely and can thus mimicJ                    that system and bootstrap. (No such family resemblancesC                    exist for the XL.) If you are exceedingly lucky,AE                    somebody here in OpenVMS Engineering will have putnH                    together a bootstrap kit-such as that for the Multia.F                    (No Miata-like OpenVMS bootstrap kit exists for the                    XL.)b  '           _____________________________ H           14.4.4  OpenVMS on the Personal Workstation -a and -au series?  B                    Though OpenVMS is not supported on the PersonalJ                    Workstation -a series platforms, OpenVMS might or might1                    not bootstrap on the platform.   H                    If you wish to attempt this, you must ensure that allE                    graphics and all I/O controllers in the system are.F                    supported by OpenVMS. You must also ensure that you9                    have the most current firmware loaded.       J                                                                      14-19 e             '                    Hardware InformationA      '           _____________________________rF           14.4.4.1  OpenVMS on the Whitebox Windows-Only series Alpha?  D                    Though OpenVMS is not supported on the "Whitebox"D                    series of Alpha platforms, OpenVMS might or mightD                    not bootstrap on the platform. These systems wereG                    specifically configured, targeted and supported onlyiJ                    for use with the Microsoft Windows NT operating system.  C                    On some of the "Whitebox" systems, the followingfG                    sequence of console commands can potentially be usedtG                    to convert the system over to unsupported use by andtG                    for OpenVMS Hobbyist users. (But please note that iflE                    you wish to attempt this, you must ensure that allnE                    graphics and all I/O controllers in the system arebJ                    supported by OpenVMS, and you must ensure that you haveI                    the most current SRM firmware loaded. (For information I                    on locating and downloading the most current Alpha SRM G                    firmware, please see Section 14.3.7.1.) And you must I                    realize that the resulting Whitebox configuration will G                    be entirely unsupported and may or may not be stable                     and useful.)r  "                    set os_type vmsD                    cat nvram  ! too see what is in this, if anything                    edit nvramc%                    10 set srm_boot on                     20 es                    initl  E                    If your nvram has other contents, you will need toTE                    change the line numbers (10 and 20) to reflect theeJ                    contents of your configuration. To obtain documentationE                    on the commands of the console editor, enter the ?p-                    command within the editor.f  J                    The above sequence was reportedly tested on the DIGITALD                    Server 3300 series, a relative of the AlphaServerG                    800 series. The DIGITAL Server 3300 is not supported E                    by OpenVMS, though the AlphaServer 800 series is a J                    supported platform. The sequence may or may not work onJ                    other platforms, and may or may not work on the DIGITAL(                    Server 3300 platform.  )                    Also see Section 5.32.S                      14-20               '                    Hardware Information       '           _____________________________TI           14.4.4.2  OpenVMS and Personal Workstation ATA (IDE) bootstrap?,  E                    OpenVMS will boot and is supported on the PersonalEH                    Workstation -au series platforms, though OpenVMS willJ                    require a SCSI CD-ROM if the Intel Saturn I/O (SIO) IDEI                    chip is present in the configuration- only the CypressrF                    IDE controller chip is supported by OpenVMS for IDE                    bootstraps.  F                    If you have an -au series system, you can determineI                    which IDE chip you have using the SRM console command:a  '                      SHOW CONFIGURATIONr  J                    If you see "Cypress PCI Peripheral Controller", you canH                    bootstrap OpenVMS from IDE storage. If you see "IntelF                    SIO 82378", you will need to use and bootstrap fromH                    SCSI. (A procedure to load DQDRIVER on the Intel SIO-I                    once the system has bootstrapped from a SCSI device-isnI                    expected to be included as part of the contents of the_B                    DQDRIVER directory on Freeware V5.0 and later.)  G                    Many of the -a series systems will include the Intels;                    SIO, and thus cannot bootstrap from IDE.r  '           _____________________________ 6           14.4.5  On the Intel Itanium IA-64 platform?  =                    OpenVMS is being ported to the Intel IA-64 I                    architecture; to HP systems based on the Intel Itaniumh$                    Processor Family.  E                    The first release of OpenVMS I64 is V8.0, with thehF                    first general release of OpenVMS I64 expected to be                    V8.2.  J                    Some Intel and HP terminology: Itanium Processor FamilyD                    is the name of the current implementation; of theG                    current Intel microprocessor family implementing the E                    IA-64 architecture. IA-64 is the name of the Intel G                    and HP architecture implementing the VLIW (Very Long E                    Instruction Word) design known as EPIC (Explicitly F                    Parallel Instruction Computing). I64 is the name ofF                    a family of HP computer systems using Intel Itanium                    processors.  J                                                                      14-21    p          '                    Hardware InformationN      '           _____________________________i>           14.4.5.1  Where can I get Intel Itanium information?  I                    Intel Itanium Processor Family and IA-64 Architecture, A                    Hardware, Software, and related docoumentationi.                    materials are available at:  D                    o  ftp://download.intel.com/design/IA-64/manuals/  F                    o  ftp://download.intel.com/design/IA-64/Downloads/  9                    o  ftp://download.intel.com/design/IA- 6                       64/Downloads/archSysSoftware.pdf  9                    o  ftp://download.intel.com/design/IA- /                       64/Downloads/24870101.pdfc  H                    The Intel Extensible Firmware Interface (EFI) console!                    documentation:   8           http://www.pentium.de/technology/efi/index.htm  D           __________________________________________________________I           14.5  What is the least expensive system that will run OpenVMS?d  F                    The cheapest systems that are or have been recentlyD                    offered by HP that will run OpenVMS Alpha are theB                    AlphaServer DS10 server, the AlphaStation XP900F                    workstation, the AlphaStation VS10 workstation, andG                    the AlphaStation XP1000 workstation. Other companies J                    sell Alpha-powered systems and Alpha motherboards, someI                    of which will run (and can be purchased with) OpenVMS-,I                    see the OpenVMS Software Product Description (SPD) foreG                    details on the supported systems and configurations.aJ                    There are also many used AlphaStation, AlphaServer, andF                    DEC 3000 models available which are quite suitable.D                    For more experienced OpenVMS system managers, theA                    (unsupported) Multia can bootstrap OpenVMS-see .                    Section 14.4.1 for details.  J                    Depending on the OpenVMS version and configuration, theJ                    OpenVMS Software Product Description (SPD) is available                    at:  9                    o  http://www.openvms.compaq.com:8000/   8                    o  http://www.openvms.compaq.com/doc/                      14-22 n  e          '                    Hardware Informatione        ?                    o  http://www.openvms.compaq.com/commercial/   C                    When purchasing a system, ensure that the systemfE                    itself is supported, that the system disk drive is I                    supported or closely compatible, that the CD-ROM drivetI                    is supported or is closely compatable and that (in the F                    case of SCSI devices) it also specifically supportsF                    512 byte block transfers; no equivalent requirementH                    exists for IDE devices. Also particularly ensure thatI                    the video controller is supported. Use of supported HPiJ                    hardware will generally reduce the level of integration#                    effort involved.f  F                    A CD-ROM, CD-R or DVD drive is required for OpenVMS'                    Alpha installations.   J                    CD-ROM drive compatibility information is available at:  B                    o  http://sites.inka.de/pcde/dec-cdrom-list.txt  D           __________________________________________________________B           14.6  Where can I get more information on Alpha systems?  D                    HP operates an AlphaServer information center at:  8                    o  http://www.compaq.com/alphaserver/  H           Alpha Technical information and documentation is available at:  E                    o  ftp://ftp.compaq.com/pub/products/alphaCPUdocs/   :                    o  http://www.support.compaq.com/alpha-@                       tools/documentation/current/chip-docs.html  B                    o  ftp://ftp.digital.com/pub/DEC/Alpha/systems/  [                    o  http://ftp.digital.com/pub/Digital/info/semiconductor/literature/dsc-h"                       library.html  +                    o  Alpha Systems Update:lC                       http://www.compaq.com/alphaserver/fb_acu.htmlo  B                    Software Product Description (SPD) information,<                    including platform support documentation:  5                    o  http://www.compaq.com/info/spd/yD                       OpenVMS typically uses SPD 25.01.xx and/or SPD                       41.87.xx.B  J                                                                      14-23               '                    Hardware Information.        B                    Information on Multia hardware is available at:  F                    o  http://www.netbsd.org/Ports/alpha/multiafaq.html  I                    Information on current and future Alpha microprocessoroB                    designs is also available from AlphaPowered at:  E                    o  http://www.alphapowered.com/alpha_tomorrow.htmlo  ?                    o  http://www.alphapowered.com/timeline.html   B                    o  http://www.alphapowered.com/ev7-and-ev8.html  I           The NetBSD folks maintain useful Alpha hardware information at:c  C                    o  http://www.netbsd.org/Ports/alpha/models.html   D           __________________________________________________________D           14.7  Describe Alpha instruction emulation and instruction                 subsets?  B                    The Alpha architecture is upward- and downward-E                    compatible, and newer instructions are emulated onyF                    older platforms, for those cases where the compilerF                    is explicitly requested to generate the newer Alpha                     instructions.  J                    In particular, OpenVMS Alpha V7.1 and later include theG                    instruction emulation capabilities necessary for the G                    execution of newer Alpha instructions on older Alpha G                    microprocessors. (Instruction emulation capabilities D                    are available for user-mode application code, andG                    are not available to device drivers or other similare%                    kernel-mode code.)   A                    Alpha instructions are available in groups (or I                    subsets). Obviously, there is the base instruction set H                    that is available on all Alpha microprocessors. Then,F                    the following are the current instruction extensionD                    groups (or subsets) that are available on some of8                    various recent Alpha microprocessors:  0                    o  byte/word extension (BWX):=                       LDBU, LDWU, SEXTB, SEXTW, STB, and STW.t  E                    o  floating-point and square root extension (FIX): F                       FTOIS, FTOIT, ITOFF, ITOFS, ITOFT, SQRTF, SQRTG,'                       SQRTS, and SQRTT.n                      14-24 r             '                    Hardware Informatione        ,                    o  count extension (CIX):,                       CTLZ, CTPOP, and CTTZ.  2                    o  multi-media extension (MVI):E                       MAXSB8, MAXSW4, MAXUB8, MAXUW4, MINSB8, MINSW4,tC                       MINUB8, MINUW4, PERR, PKLB, PKWB, UNPKBL, andq                       UNPKBW.h  C                    The typical instruction subset that provides the F                    biggest win-and of course, your mileage may vary-isH                    typically the instruction set that is provided by theJ                    EV56 and later; specifically, the byte-word instructionD                    subset. To select this subset, use the following:  ;                    /ARCHITECTURE=EV56/OPTIMIZE=TUNE=GENERIC   E                    The /ARCHITECTURE controls the maximum instruction E                    subset that the compiler will generally use, while I                    the /OPTIMIZE=TUNE controls both the instruction-leveldH                    scheduling and also the instructions generated insideG                    loops-any code resulting from /OPTIMIZE=TUNE that issF                    specific to an instruction subset will be generatedD                    only inside loops and will also be "protected" byD                    an AMASK-based test that permits the execution ofC                    the proper code for the particular current Alphat"                    microprocessor.  F                    Typically /OPTIMIZE=TUNE=GENERIC is the appropriateG                    choice for tuning, and the /ARCHITECTURE selects the_I                    minimum target architecture for general use throughout &                    the generated code.  D                    generated for later architectures and instructionE                    subsets will run on older Alpha systems due to the C                    emulation, but if /ARCHITECTURE is a significant E                    benefit, then the emulation might be a performance                     penalty.e  E                    Please see the OpenVMS Ask The Wizard area for the/G                    source code of a (non-privileged) tool that looks at.F                    the instruction subsets available on the particularJ                    Alpha microprocessor that the tool is run on. This toolF                    demonstrates the use of the Alpha AMASK and IMPLVER                     instructions.  J                                                                      14-25 d  r          '                    Hardware Informationt        A                    Please see Section 10.24 and Section 14.10 fortA                    additional details and related considerations./  D           __________________________________________________________I           14.8  What is the Accuracy of the Alpha Time of Year (BB_WATCH)                  Clock?  I                    The specification for maximum clock drift in the AlphaaE                    hardware clock is 50 parts per million (ppm), that F                    is less than 0.000050 seconds of drift per second,E                    less than 0.000050 days of drift per day, or lessuG                    than 0.000050 years of drift per year, etc. (eg: AneJ                    error of one second over a day-long interval is roughlyG                    11ppm, or 1000000/(24*60*60).) Put another way, thislH                    is .005%, which is around 130 seconds per month or 26$                    minutes per year.  J                    The software-maintained system time can drift more thanH                    this, primarily due to other system activity. TypicalH                    causes of drift include extensive high-IPL code (softJ                    memory errors, heavy activity at device IPLs, etc) thatH                    are causing the processing of the clock interrupts to                    be blocked.  7                    Also see Section 14.15, Section 4.3.   D           __________________________________________________________9           14.9  So how do I open up the DEC 3000 chassis?n  H                    After removing those two little screws, tilt the backG                    end of the top shell upwards-then you can remove then                    lid.   D           __________________________________________________________(           14.10  What is byte swizzling?  I                    "Swizzling" is the term used to describe the operationrD                    needed to do partial longword (i.e. byte or word)D                    accesses to I/O space on those systems that don'tG                    support it directly. It involved shifting the offset J                    into an address space by 5 (or 7 for one older system),I                    and ORing this into the base address. It then required J                    the size of the operation to be ORed into the low order                    bits.                      14-26 e  g          '                    Hardware Information         F                    That is, because the EV4 and EV5 CPUs did not bringF                    bits 0 and 1 off the chip, to do programmed I/O forI                    bytes/words, the information on the size/offset of the G                    transfer was encoded into the address data. The data G                    itself then had to be shifted into the correct "byte3F                    lane" (i.e. its actual position within a longword).  C                    The EV56 CPU supports the byte/word instructionssC                    however only some EV56 systems support byte/wordeE                    accesses to I/O space. Even on an EV56 system that I                    supports byte/word accesses to I/O space, the relevant J                    OpenVMS routines do not support byte/word access to I/O                    space.s  J                    EV6 systems (with the exception of the AlphaServer GS60H                    and AlphaServer GS140 series, for reasons of platformF                    compatability) support a flat, byte addressable I/O                    space.   I                    If a device driver uses CRAM or IOC$WRITE_IO/IOC$READ_ C                    IO, then OpenVMS will do the right thing without A                    changing the driver - OpenVMS will swizzle andm'                    unswizzle as needed.M  E                    To use byte/word operations on MEMORY, you need toaH                    tell the compiler to use the EV56 or EV6 architectureB                    (/ARCHITECTURE=EV56). Memory operations did not?                    swizzle, but the compiler would do long/quad D                    access, and extract/insert bytes as needed. UsingD                    /ARCHITECTURE=EV56 allows smaller, more efficient4                    byte/word access logic to memory.  H                    If the application is directly doing I/O space accessE                    across a range of Alpha systems (like the graphicscH                    servers), then the driver will need to know how to doG                    swizzling for old platforms, and byte access for newo                    platforms.   @                    Please see Section 10.24 and Section 14.7 forA                    additional details and related considerations.         J                                                                      14-27               '                    Hardware Informatione      D           __________________________________________________________E           14.11  What is the layout of the VAX floating point format?   D                    The VAX floating point format is derived from oneD                    of the PDP-11 FP formats, which helps explain itsH                    strange layout. There are four formats defined: F 32-H                    bit single-precision, D and G 64-bit double-precisionF                    and H 128-bit quadruple precision. For all formats,G                    the lowest addressed 16-bit "word" contains the sign G                    and exponent (and for other than H, some of the most F                    significant fraction bits). Each successive higher-I                    addressed word contains the next 16 lesser-significant(I                    fraction bits. Bit 15 of the first word is the sign, 1tG                    for negative, 0 for positive. Zero is represented byAF                    a biased exponent value of zero and a sign of zero;D                    the fraction bits are ignored (but on Alpha, non-F                    zero fraction bits in a zero value cause an error.)F                    A value with biased exponent zero and sign bit 1 isG                    a "reserved operand" - touching it causes an error -FF                    fraction bits are ignored. There are no minus zero,8                    infinity, denormalized or NaN values.  F                    For all formats, the fraction is normalized and theJ                    radix point assumed to be to the left of the MSB, henceG                    the following range: 0.5 less than or equal to f andrI                    less than 1.0. The MSB, always being 1, is not stored.nI                    The binary exponent is stored with a bias varying withaB                    type in bits 14:n of the lowest-addressed word.  N                      FP      Exponent    Exponent    Mantissa (Fraction) bits,K                      Type      Bits        Bias        including hidden bitnO                      =========================================================="?                       F         8           128              24M?                       D         8           128              56v?                       G        11          1024              53 ?                       H        15         16384             113   I                    The layout for D is identical to that for F except for"/                    32 additional fraction bits.t  H                    Example: +1.5 in F float is hex 000040C0 (fraction of7                    .11[base 2], biased exponent of 129)p                          14-28               '                    Hardware Information       D           __________________________________________________________>           14.12  Where can I find more info about VAX systems?  4                    o  HP runs a VAX "InfoCenter" at:<                       http://www.compaq.com/alphaserver/vax/  G                    o  Jim Agnew maintains a MicroVAX/VAXstation FAQ at:hG                       http://anacin.nsc.vcu.edu/~jim/mvax/mvax_faq.htmlh  8                    o  The VAXstation 3100 Owner's Guide:E                       http://www.whiteice.com/~williamwebb/intro/DOC-e                       i.html  H                    o  A field guide to PDP-11 (and VAX) Q-bus and UNIBUS.                       modules can be found at:D                       http://metalab.unc.edu//pub/academic/computer-E                       science/history/pdp-11/hardware/field-guide.txt   B                    o  Various VAX historical information (also see3                       Section 2.1) can be found at: ?                       http://telnet.hu/hamster/vax/e_index.html   D           __________________________________________________________H           14.13  Where can I find information on NetBSD for VAX systems?  8           Gunnar Helliesen maintains a NetBSD VAX FAQ atD           http://vaxine.bitcon.no/._________________________________  @           14.14  What system disk size limit on the MicroVAX and!                  VAXstation 3100?C  G                    System disks larger than 1.073 gigabytes (GB)-1fffffnJ                    hexidecimal blocks - are not supported on any member ofJ                    the VAXstation 3100 series and on certain older membersD                    of the MicroVAX 3100 series, and are not reliableD                    on these affected systems. (See below to identifyF                    the affected systems-the more recent members of theB                    MicroVAX 3100 series systems are NOT affected.)  H                    Various of the SCSI commands used by the boot driversE                    imbedded in the console PROM on all members of the G                    VAXstation 3100 series use "Group 0" commands, which I                    allow a 21 bit block number field, which allows access H                    to the first 1fffff hexidecimal blocks of a disk. AnyF                    disk references past 1fffff will wrap-this wrappingI                    behaviour can be of particular interest when writing a_F                    system crashdump file, as this can potentially lead  J                                                                      14-29               '                    Hardware Informationa        D                    to system disk corruptions should any part of the=                    crashdump file be located beyond 1.073 GB.S  F                    More recent systems and console PROMs use "Group 1"J                    SCSI commands, which allow a 32 bit block number field.  E                    There was a similar limitation among the oldest ofID                    the MicroVAX 3100 series, but a console boot PROMH                    was phased into production and was made available forJ                    field retrofits-this PROM upgrade allows the use of theI                    "Group 1" SCSI commands, and thus larger system disks.oG                    There was no similar PROM upgrade for the VAXstation,                    3100 series.h  ;                    Systems that are affected by this limit:   J                    o  VAXstation 3100 series, all members. No PROM upgrade#                       is available.a  H                    o  MicroVAX 3100 models 10 and 20. No PROM upgrade is                        available.  I                    o  MicroVAX 3100 models 10e and 20e. Only systems withrH                       console VMB versions prior to V6.4 are affected. AH                       PROM upgrade for these specific systems is (or was&                       once) available.                      Also see H                    http://www.whiteice.com/~williamwebb/intro/DOC-i.html  (                    Also see Section 9.5.  D           __________________________________________________________J           14.15  What is the Accuracy of VAX the Time of Year (TOY) Clock?  J                    The VAX Time-Of-Year (TOY) clock (used to save the timeI                    over a reboot or power failure) is specified as having H                    an accuracy of 0.0025%. This is a drift of roughly 65%                    seconds per month.S  J                    The VAX Interval Time is used to keep the running time,E                    and this has a specified accuracy of .01%. This is E                    a drift of approximately 8.64 seconds per day. Any E                    high-IPL activity can interfere with the IPL 22 or H                    IPL 24 (this depends on the VAX implementation) clockH                    interrupts-activities such as extensive device driverD                    interrupts or memory errors are known to slow the                    clock.i                      14-30               '                    Hardware Information         6                    Also see Section 14.8, Section 4.3.  D           __________________________________________________________8           14.16  What are the VAX processor (CPU) codes?  '                       CPU:    Platform: '                       -----   ---------o<                       KA41-A : MicroVAX 3100 Model 10 and 20=                       KA41-B : VAXserver 3100 Model 10 and 20 )                       KA41-C : InfoServer >                       KA41-D : MicroVAX 3100 Model 10e and 20e?                       KA41-E : VAXserver 3100 Model 10e and 20ei>                       KA42-A : VAXstation 3100 Model 30 and 40>                       KA42-B : VAXstation 3100 Model 38 and 487                       KA43-A : VAXstation 3100 Model 761<                       KA45   : MicroVAX 3100 Model 30 and 407                       KA46   : VAXstation 4000 Model 60X5                       KA47   : MicroVAX 3100 Model 80O2                       KA48   : VAXstation 4000 VLC;                       KA49-A : VAXstation 4000 Model 90/90At7                       KA49-B : VAXstation 4000 Model 95S7                       KA49-C : VAXstation 4000 Model 96 5                       KA50   : MicroVAX 3100 Model 9045                       KA51   : MicroVAX 3100 Model 95 1                       KA52   : VAX 4000 Model 100 1                       KA53   : VAX 4000 Model 105M1                       KA54   : VAX 4000 Model 106r5                       KA55   : MicroVAX 3100 Model 85 5                       KA56   : MicroVAX 3100 Model 96 1                       KA57   : VAX 4000 Model 108a5                       KA58   : MicroVAX 3100 Model 88e5                       KA59   : MicroVAX 3100 Model 98t'                       KA85   : VAX 8500 '                       KA86   : VAX 8600u'                       KA88   : VAX 8800 9                       KA600  : VAX 4000-50 (aka VAXbrick)dB                       KA610  : MicroVAX I, VAXstation I (aka KD32)-                       KA620  : rtVAX (VAXeln)w+                       KA62A  : VAX 6000-200M+                       KA62B  : VAX 6000-300 9                       KA630  : MicroVAX II, VAXstation IIn;                       KA640  : MicroVAX 3300, MicroVAX 3400tZ                       KA650  : VAXstation 3200, MicroVAX 3500, MicroVAX 3600, MicroVAX III+                       KA64A  : VAX 6000-400   J                                                                      14-31               '                    Hardware Information         J                       KA655  : MicroVAX 3800, MicroVAX 3900, MicroVAX III++                       KA65A  : VAX 6000-500o:                       KA660  : VAX 4000-200, VAX 4 upgrade+                       KA66A  : VAX 6000-600 +                       KA670  : VAX 4000-300i+                       KA675  : VAX 4000-400 +                       KA680  : VAX 4000-500T,                       KA681  : VAX 4000-500A+                       KA690  : VAX 4000-600 ,                       KA691  : VAX 4000-605A,                       KA692  : VAX 4000-700A,                       KA693  : VAX 4000-605A,                       KA694  : VAX 4000-705A)                       KA730  : VAX-11/730s)                       KA750  : VAX-11/750 5                       KA780  : VAX-11/780, VAX-11/782_)                       KA785  : VAX-11/785a+                       KA7AA  : VAX 7000-600S+                       KA7AB  : VAX 7000-700 +                       KA7AC  : VAX 7000-800 %                       KA800  : VAXrta 1                       KA820  : VAX 8200, VAX 8300g1                       KA825  : VAX 8250, VAX 8350c'                       KA865  : VAX 8650   D           __________________________________________________________>           14.17  Where can I get software and hardware support                  information?   J                    Please contact the HP Customer Support Center. ServicesC                    and information, manuals, guides, downloads, and I                    various other information is available via the support                     link at:   9                    o  http://www.hp.com/products/openvms/t  I                    Various hardware and system documentation is availablen                    at:  B                    o  http://www.compaq.com/support/techpubs/user_'                       reference_guides/e  E                    o  http://www.adenzel.demon.nl/vaxes/microvax3100/n  F                    o  http://www.adenzel.demon.nl/vaxes/infoserver150/                      14-32 r  g          '                    Hardware Informationm        I                    TSM (Terminal Server Manager), DEChub, DECserver, etc.                     information:/  E                    o  http://www.compaq.com/support/digital_networks_.                       archive/  D                    The owner and maintainer of current DECserver andE                    related hardware is DIGITAL Network Products Groupe                    (DNPG):  *                    o  http://www.dnpg.com/  D           __________________________________________________________B           14.18  Where can I get hardware self-maintenance support                  assistance?  C                    The HP Assisted Services (CAS) program (a directgE                    descendent of the program once known as DECmailer)eH                    is available to customers that wish to maintain theirG                    own system(s) (self-maintenance), but that wish someeH                    level of assistance in acquiring hardware diagnosticsH                    and hardware manuals for the system(s), and that wishH                    to have access to spares and module-level repairs for<                    customer-performed hardware module swaps:  8                    o  http://www.compaq.com/CAS-Catalog/  D           __________________________________________________________G           14.19  Why does my system halt when I power-cycle the consoleu                  terminal?  I                    Various VAX and Alpha consoles are designed to process C                    the BREAK signal, treating it as a HALT request.R  J                    A BREAK is a deliberately-generated serial line framing                    error.t  ?                    When a serial line device such as a terminalbE                    powers up (or sometimes when powering down) it can D                    generate framing errors. These framing errors are8                    indistingushable from a BREAK signal.  D                    When a BREAK is received on a serial line consoleE                    for various VAX systems-including most VAXstation, @                    MicroVAX, and VAX 4000 series-it is typicallyG                    interpreted as a HALT. Alpha systems will also often   J                                                                      14-33 h  o          '                    Hardware Information         D                    process a BREAK in a similar fashion, halting the                    system.  D                    There is no uniform or generally-available way toJ                    disable this behaviour on every VAX or Alpha system. OnJ                    some systems, BREAK processing can be disabled in favorG                    of [CTRL/P], or [CTRL/P] is the only way to halt ther                    processor.p  I                    The most common way to avoid these halts is to disable3G                    the serial line console or to simply not power-cycle C                    the console terminal. There is certain importantoE                    system state information that is displayed only on H                    the console, OpenVMS expects to always have access to&                    the system console.  (                    Also see Section 5.5.  D           __________________________________________________________H           14.20  Can I reuse old keyboards, mice and monitors with a PC?  F                    Older HP keyboards (those with the DIGITAL logo andG                    the RJ modular jacks), older HP mice (those with thesF                    DIGITAL logo and with the RJ modular jacks, or withE                    a DIN connector with pins in a configuration otheroG                    than the PC-standard DIN connector pin orientation), D                    and older video monitors (with RGB synch-on-greenD                    video signaling) all use signaling formats and/orC                    communications protocols that differ from the PC E                    standards, and are not (easily) interchangable nor H                    (easily) compatible with typical PC peripheral deviceH                    controllers. The LK201 and LK401 keyboards, the VSXXXG                    series mice, the VR260 and VR290 monitors, etc., are F                    incompatible with most PC systems and with most KVM                    switches.  G                    Newer HP (and Compaq) keyboards (those with with PC- H                    style DIN plugs, and the HP, Compaq or DIGITAL logo),D                    newer HP mice (with PC-pin DIN plugs, and the HP,D                    Compaq or DIGITAL logo), and newer video monitorsI                    (multi-synch) are often interchangeable with "industry6C                    standard" PC systems, and can often be used withnG                    most PC peripheral device controllers. LK461, LK463,mG                    LK46W, LK471, PC7XS-CA, VRC16, VRC21, TFT-series LCDiF                    flat-panel displays, etc., are typically reasonablyD                    compatible with most PC systems, and will usually                      14-34 h  a          '                    Hardware Informationc        I                    perform as expected within the limits of the hardware. E                    (For details of CRT and LCD display compatibility,p-                    please see Section 14.21.)a  D                    Rule of thumb: if the peripheral device componentF                    was sold for use with the DEC 2000 (DECpc 150 AXP),F                    an AlphaServer series, an AlphaStation series, or aI                    more recent Alpha system, it will probably work with ahG                    PC peripheral controller or with a PC-compatible KVMiF                    switch. If the peripheral device component was soldJ                    for use with an VT420 or older terminal, most VAX, mostG                    VAXstation, and most Alpha systems with names in the6I                    format DEC [four-digit-number], it probably won't worko>                    on a PC system or with a PC-compatible KVM.  I                    Note that the above is a general guideline, and should I                    not be read to indicate that any particular peripheralwA                    device will or will not work in any particularmH                    configuration, save for those specific configurations9                    the device is explicitly supported in.   B                    Software Integrators sells a video adapter cardF                    called Gemini P1 which will drive many of the olderE                    HP (DIGITAL-logo) fixed-frequency monitors on a PC                     system:  *                    o  http://www.si87.com/  J                    The DIGITAL part number 29-32540-01 converts the outputH                    from the RGB cable (3 BNC, synch-on-green) that comesI                    with the VAXstation 3100 and VAXstation 4000 series to -                    a female SVGA D connector.r  E                    This adapter will allow PC multisync monitors with)F                    the needed frequency specifications to be used withI                    the VAXstation series synch-on-green video connection.fF                    It may well also work with a VAXstation 2000 seriesA                    systems, but specifics and performance of thathI                    combination are not immediately known at this writing.m  G                    The protocol definition for the old DIGITAL keyboardMI                    and mouse interfaces is buried at the back of the QDSS I                    section in the old VAXstation II manual, specifically, E                    in the back of the VCB02 Video Subsystem Technical I                    Manual (EK-104AA-TM). The keyboard wiring and protocol   J                                                                      14-35 2  n          '                    Hardware Informationt        E                    is in appendix B, and occupies circa 44 pages. The :                    mouse is in appendix C, circa 12 pages.  *                    Also see Section 14.21.  D           __________________________________________________________J           14.21  Which video monitor works with which graphics controller?  J                    To determine the answer to the "will this video monitorI                    or this LCD panel work with this graphics controller?"fJ                    question, please first locate the resolution(s) and theG                    frequencies that are possible/supported at both endssI                    of the video cable (on the display and on the graphicsrE                    controller, in other words), and then determine if J                    there are any matching settings available. If there areI                    multiple matches, you will need to determine which onep6                    is most appropriate for your needs.  J                    You will also need to determine if the video monitor orH                    graphics controller requires the 3 BNC signaling withJ                    the synchronization signals on the green wire, or the 5J                    BNC signalling common on many PCs, or other connectionsI                    such as the DB15 video connector or USB connector usedt&                    on various systems.  J                    If there are no matches, you will likely need to changeG                    the hardware at one or both ends of the video cable.e  E                    The refresh frequencies for many devices have been.H                    posted to comp.os.vms and/or other newsgroups. Search6                    the archives for details. Also see:  /                    o  http://www.repairfaq.org/o  4                    o  http://www.mirage-mmc.com/faq/  Z                    o  http://www.geocities.com/SiliconValley/Foothills/4467/fixedsync.html  D                    o  http://saturn.tlug.org/sunstuff/ffmonitor.html  A                    o  http://hawks.ha.md.us/hardware/monitor.html   E                    LCD-based and plasma-based flat-panel displays are E                    generally compatible with all recent OpenVMS Alpha B                    systems and supported graphics controllers. ForF                    best results, you should generally set the graphicsG                    controller to match the native LCD or plasma displayoA                    resolution and (for LCD displays) also set then                      14-36 o             '                    Hardware Informationl        G                    controller refresh rate to 60Hz. Check your graphicswD                    controller and your display documentation for anyD                    device-specific requirements and/or configuration#                    recommendations.i  *                    Also see Section 14.20.  D           __________________________________________________________A           14.22  Where can I get information on storage hardware?_  F                    Information on various HP (Compaq, DIGITAL) OpenVMSG                    and other disk storage hardware and controllers, anduI                    related technical information on SCSI, device jumpers, )                    etc., is available at:p  2                    o  http://theref.aquascape.com/  D           __________________________________________________________D           14.23  Why does my LK401 keyboard unexpectedly autorepeat?  6                    There are several modes of failure:  C                    o  Pressing 2 and 3 keys at the same time causeseD                       one key to autorepeat when released. Check theF                       hardware revision level printed on the bottom ofE                       the keyboard. If the revision level is C01, the H                       keyboard firmware is broken. Call field service toH                       replace the keyboard with any revision level other                       than C01.   E                    o  Pressing certain keys is always broken. Typical F                       symptoms are: delete always causes a autorepeat,D                       return needs to be pressed twice, etc. This isF                       frequently caused by having keys depressed whileE                       the keyboard is being initialized. Pressing ^F2yD                       several times or unplugging and replugging theG                       keyboard frequently fix this problem. (Ensure youtE                       have current ECO kits applied; there is a patchT5                       available to fix this problem.)R  H                    o  A key that was working spontaneously stops workingG                       correctly. This may be either of the two previous F                       cases, or it may be bad console firmware. EnsureF                       that you have the most recent firmware installedI                       on your Alpha system. In particular, an old version I                       of the DEC 3000 SRM firmware is known to have a buge@                       that can cause this keyboard misbehaviour.  J                                                                      14-37 y  N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faqtN  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.comi   ------------------------------  # Date: Thu, 03 Jul 2003 17:17:17 GMTl2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman); Subject: OpenVMS Frequently Asked Questions (FAQ), Part 8/9h2 Message-ID: <xyZMa.3899$bl3.2546@news.cpqcorp.net>               '                    Hardware InformationE      D           __________________________________________________________I           14.24  Problem - My LK411 sends the wrong keycodes or some keysd                  are dead   H                    Check the firmware revision on the keyboard. HardwareF                    revision B01 introduced an incompatability with theD                    device driver which causes the keyboard to not beF                    recognized correctly. There is a patch available toF                    fix this problem: [AXPDRIV06_061] - the fix is alsoJ                    included in OpenVMS V6.2. The rev A01 keyboard, and the6                    LK450 should work without problems.  C                    If you are working from another operating system E                    platform, please see the DECxterm tool and related 8                    information on OpenVMS Freeware V5.0.  D           __________________________________________________________F           14.25  Which DE500 variant works with which OpenVMS version?  E                    Ensure you have a version of the Alpha SRM consoleiF                    with support for the DE500 series device. Apply ALLI                    mandatory ECO kits for the OpenVMS version in use, and G                    also apply the CLUSIO, ALPBOOT, and ALPLAN kits, and G                    apply any available ALPCPU ECO kit for the platform.-                      o  DE500-XA:                       auto-detection, no auto-negotiation,E                       OpenVMS V6.2-1H1 and ALPBOOT ECO, also V7.0 ando$                       later and ECO.?                       Device hardware id 02000011 and 02000012._7                       Component part number 54-24187-01h                      o  DE500-AA7                       auto-detection, auto-negotiation,fG                       OpenVMS V6.2 and ALPBOOT and ALPLAN ECOs, or V7.1s(                       and later and ECO.?                       Device hardware id 02000020 and 20000022. 7                       Component part number 54-24502-01d                      o  DE500-BA7                       auto-detection, auto-negotiation, F                       OpenVMS V6.2-1H3 and CLUSIO, ALPBOOT, ALPLAN and@                       ALPCPU ECOs, or V7.1-1H1 or later and ECO.F                       Device hardware id 02000030 (check connector, vsH                       DE500-FA) (other values on old Alpha SRM firmware)7                       Component part number 54-24602-01                       14-38 e             '                    Hardware Informationc        A                    o  DE500-FA (100 megabit fibre optic Ethernet)m0                       OpenVMS V7.1-1H1 and laterF                       Device hardware id 02000030 (check connector, vsG                       DE500-BA) (other values possible on old Alpha SRMo                       firmware) 7                       Component part number 54-24899-01_  J                    To check the DE500 device hardware id from OpenVMS, use)                    the following command:w  #                    $ ANALYZE/SYSTEMd-                    SDA> SHOW LAN/DEVICE=EWcu:h  7                    The "hardware id" will be displayed._  C                    To set the DE500 speed via the Alpha SRM console (                    environment variable:  9                       EWx0_MODE setting           Meaning R                       --------------------------  --------------------------------L                       Twisted-Pair                10 Mbit/sec, nofull_duplexJ                       Full Duplex, Twisted-Pair   10 Mbit/sec, full_duplexL                       AUI                         10 Mbit/sec, nofull_duplexL                       BNC                         10 Mbit/sec, nofull_duplexM                       Fast                        100 Mbit/sec, nofull_duplex K                       FastFD (Full Duplex)        100 Mbit/sec, full_duplex P                       Auto-Negotiate              Negotiation with remote device  A                    To override the console setting and use LANCP:   )                    $ RUN SYS$SYSTEM:LANCPs/                    LANCP> SET DEV EWA0/SPEED=10a<                    LANCP> SET DEV EWA0/SPEED=100/full_duplex  C                    Fast Ethernet (100Base, 100 megabit) controllers F                    such as the DE500 series have a pair of connectionsC                    available-while traditional Ethernet (10Base, 10 F                    megabit) is inherently a half-duplex protocol, FastG                    Ethernet can be configured to use one or both of the F                    available connections, depending on the controller.A                    Fast Ethernet can thus be half- or full-duplex F                    depending on the configuration and the capabilitiesE                    of the network controller and the Ethernet networkrI                    plant. Some Fast Ethernet controllers can also operatelH                    at traditional Ethernet speeds, these controllers areH                    thus often refered to as 10/100 Ethernet controllers.  J                                                                      14-39               '                    Hardware Information       D           __________________________________________________________B           14.26  Third-party disk/tape/controllers/SCSI/widgets on                  OpenVMS?e  E                    A wide variety of third-party widgets-SCSI and ATA G                    (IDE) disks and tapes, graphics controllers, etc-are E                    obviously widely available and are used on various                     platforms.s  D                    If you purchase third-party "generic" SCSI or ATAD                    (IDE) storage devices, you and your device vendorF                    will be responsible for the testing and the supportI                    of the devices. In general, you can expect that CompaqhH                    will address non-standards-compliance problems withinI                    OpenVMS (changes that will also not prevent operationseD                    with other supported devices, of course), but youJ                    and/or the device vendor and/or the device manufacturerE                    are responsible for finding and fixing problems in F                    the particular third-party device and or controller                    involved.  I                    In particular, realize that neither SCSI nor ATA (IDE) I                    is a particularly standard interface, these interfaces H                    tend to be a collection of optionally-implemented andJ                    standardized interface features. You should not and canH                    not simply assume that all SCSI nor ATA (IDE) storageI                    devices are interchangeable. If you want to try to use H                    a generic SCSI device, use V6.2 or later, or (better)H                    V7.1-2 or later. If you wish to try to use ATA (IDE),/                    use OpenVMS V7.1-2 or later.e  J                    On older OpenVMS releases, see the disk capacity limits!                    (Section 9.5).   D                    With SCSI disks on releases prior to V6.2, ensureF                    that you have the ARRE and ARWE settings configuredE                    correctly (disabled). (If not, you will see DRVERRt=                    fatal drive errors and error log entries.)r  F                    Some SCSI disks set the medium type byte as part ofJ                    the SCSI size field-this is a SET CAPACITY extension toH                    SCSI specs. This problem also applies to VAX V7.1 and                    later.                         14-40    f          '                    Hardware Information         F                    Disks with SCSI disk sizes past 8.58 GB and/or withJ                    the SET CAPACITY extension require ALPSCSI07 ECO or theJ                    OpenVMS Alpha V7.1-2 or later release. (See Section 9.5(                    for further details.)  >                    Based on the displays of the (undocumented)J                    SYS$ETC:SCSI_INFO tool; this tool is present in OpenVMS"                    V6.2 and later:  X                        Issuing 6-byte MODE SENSE QIOW to get current values for page 01h=                               Page Code ................. 01h S                               Page Name ................. Read-Write Error Recovery =                               Saveable .................. Yes <                               Size ...................... 10Q                               Hex Data .................. E6 08 50 00 00 00 08 00 ?                                                           00 00   H                    The E6 indicates that the AWRE and ARRE bits are set,J                    and this is not acceptable on OpenVMS versions prior toG                    V6.2. Further along in the SCSI_INFO display, if you                     also see:  [                        Issuing 6-byte MODE SENSE QIOW to get changeable values for page 81h_=                               Page Code ................. 01heS                               Page Name ................. Read-Write Error RecoveryC=                               Saveable .................. Yesr<                               Size ...................... 10Q                               Hex Data .................. C0 08 50 00 00 00 08 00v?                                                           00 00   G                    The C0 value means that the AWRE and ARRE values canCF                    be changed on this particular SCSI device. (This isD                    not always the case.) Use RZDISK from the OpenVMSF                    Freeware, and reset the E6 flag byte to hexadecimalJ                    26 (or whatever the remaining mask when you remove bits#                    C0) on page one.i  D                    Each SCSI and ATA (IDE) host contains non-trivialI                    SCSI and IDE driver software, and each device containseH                    equally non-trivial firmware- taken together with theF                    mechanical and electronic components, this softwareJ                    and firmware will determine whether or not a particular4                    device will function as expected.  J                                                                      14-41               '                    Hardware Information         F                    Also note that various devices-such as various SCSIF                    CD-R devices -can implement and can require vendor-I                    specific protocol extensions, and these extensions canoF                    require modifications to OpenVMS or the addition ofF                    various utilities. In various of these cases, theseF                    devices perform functions that will require them toF                    use SCSI or ATA (IDE) commands that are (hopefully)G                    architecturally-compatible SCSI or ATA (IDE) commandeF                    extensions. (Also see Section 7.1 and Section 9.7.)  J                    In order for OpenVMS to officially support a particularJ                    device, integration and testing work is mandated. ThereF                    can be no certainty that any particular device willF                    operate as expected in any particular configurationD                    without first performing this (non-trivial) work.  I                    It is quite possible to find two devices-both entirely C                    compliant with applicable standards or interface 8                    documents-that will not interoperate.  ?                    The same general statement holds for OpenVMS I                    bootstrapping on an unsupported VAX or Alpha platform. H                    It might or might not work. In particular, please seeE                    the OpenVMS Software Product Description (SPD) for F                    the list of platforms supported by OpenVMS. OpenVMSB                    is not supported on the Personal Workstation -aE                    series, on the Digital Server series platforms, on H                    the AlphaServer 2100 series 5/375 CPU, on the Multia,F                    on the AlphaServer DS20L, and on a variety of otherI                    platforms. (You might or might not see success booting 6                    OpenVMS on any of these platforms.)  '           _____________________________ ;           14.26.1  Lists of third-party widgets on OpenVMS?u  E                    Various folks have successfully used common third-rD                    party disk disk devices with OpenVMS, such as theC                    ATA (IDE) and SCSI variants of the Iomega Zip250 H                    removable disk device. Common SCSI CD-R/CD-RW devicesG                    such as the Plextor PlexWriter 12/10/32S SCSI series D                    have also been successfully utilized with variousF                    AlphaStation and VAXstation systems, and with toolsG                    such as CDRECORD. (A Plextor burn of 614400000 bytes E                    (300000 sectors) requires just over six minutes at                       14-42    V          '                    Hardware Information         H                    12x, using an AlphaStation XP1000 666 MHz EV67 system#                    UltraSCSI host.)f  G                    If you choose to attempt to use third-party devices,oG                    ensure that you have the current OpenVMS version and E                    the current ECO kit(s) applied. In the case of the H                    ATA (IDE) Zip250 drive, ensure that you have the most>                    current revision of SYS$DQDRIVER installed.  '           _____________________________wG           14.26.2  Are the 2X-KZPCA-AA and SN-KZPCA-AA LVD Ultra2 SCSI?p  H                    Yes. Both of these controllers are Ultra2 low-voltage7           _________differential_(LVD)_SCSI controllers.   7           14.26.3  Resolving DRVERR fatal device error?   I                    If this is on an OpenVMS version prior to V6.2, pleasemH                    see the AWRE and ARRE information included in section!                    Section 14.26._  D           __________________________________________________________?           14.27  How do I convert? Disk Blocks? KB, MB, GB, TB?   I                    The smallest granularity of disk storage addressing isAJ                    called a disk block, or sometimes a disk sector. GroupsE                    of disk blocks are usually organized together into F                    the smallest unit of storage that can be allocated,E                    and this unit is called a disk cluster. The number:G                    of blocks in a cluster is the cluster factor, and isoC                    established when the disk volume is initialized.0  I                    Each individual disk block is composed of five hundred I                    twelve (512) bytes, or one-half kilobyte. Each byte is I                    comprised of eight bits. A bit represents the smallest J                    unit of information, typically refered to as a one or a                    zero.  C                    OpenVMS tends to uses base two notation for disk0F                    storage, while disk storage capacity specificationsD                    from most storage vendors (including Compaq) will3                    generally use base ten notation.   F                    An OpenVMS disk block is 512 bytes in size; this is:                    one-half kilobyte in base two notation.  J                                                                      14-43               '                    Hardware Information         @                    The following table describes the prefix, theH                    abbreviation, and the associated base ten (marketing)1                    and base two (OpenVMS) values.8  G                                Base Ten                        Base Two U                                -----------------------------   ---------------------- U                      Kilobyte  (KB)  10**3              1000   2**10             1024 U                      Megabyte  (MB)  10**6           1000000   2**20          1048576IU                      Gigabyte  (GB)  10**9        1000000000   2**30       1073741824 U                      Terabyte  (TB)  10**12    1000000000000   2**40    1099511627776 U                      Petabyte  (PB)  10**15 1000000000000000   2**50 1125899906842624   D                    The base ten representation of the 2**40 value isF                    1099511627776, which is obviously rather ugly. WhenC                    viewed as a base eight or base sixteen (octal or E                    hexadecimal, respectively) value, the value is far D                    nicer. Specifically, the value is 10000000000 andF                    40000000 when represented in octal and hexadecimal,                     respectively.  F                    Notational note: Within the OpenVMS FAQ, a thousandF                    bits is a kilobit, and is always represented by theJ                    appreviation Kb, while a Kilobyte is always representedG                    as KB. OpenVMS operating system references to system:D                    and storage are generally to the base-two versionI                    (eg: 1024, in the case of a kilobyte or kilobit) whileVJ                    storage hardware references and hardware specificationsD                    are generally to the base-ten version (eg: 1000).  I                    To convert OpenVMS disk blocks to (base two) kilobytesXE                    (KB; 1024 bytes), simply divide by two. To convert I                    blocks to (base two) megabytes, divide by 2048. Blocks_C                    to (base two) gigabytes (GB), divide by 2097152.sI                    These particular divisions can also be performed using H                    bitshifts: to divide a value by two, shift the binary8                    value rightwards by one bit position.  J                    To convert OpenVMS disk blocks to (base ten) kilobytes,4                    divide by approximately 1.953125.  G                    And for those rummaging around deep within SYSGEN, a >                    microfortnight is approximately one second.                        14-44 w  m          '                    Hardware Information       D           __________________________________________________________6           14.28  Looking for connector wiring pinouts?  &                    The DECconnect DEC-1           423 Modified Modular Jack (MMJ) pinout:   1                      1: Data Terminal Ready (DTR) &                      2: Transmit (TXD).                      3: Transmit Ground (TXD-)-                      4: Receive Ground (RXD-)a%                      5: Receive (RXD) ,                      6: Data Set Ready (DSR)  *                       +------------------+*                       | 1  2  3  4  5  6 |*                       +------------+    ++)                                    +____+t  B                    The PC-compatible DB9 connector pinout follows:  1                      1: Data Carrier Detect (DCD)t%                      2: Received Data %                      3: Transmit Data 1                      4: Data Terminal Ready (DTR)r                      5: Ground,                      6: Data Set Ready (DSR)-                      7: Request To Send (RTS)a%                      8: Clear To Send                        9: floating  I                    The MicroVAX DB9 console connector pinout predates the J                    PC-style DB9 pinout, and uses a then-common (and older)I                    standard pinout, and uses the following EIA-232 seriesl$                    standard signals:  )                      1: Protective Ground '                      2: Transmited Data/%                      3: Received Data_-                      4: Request To Send (RTS) 1                      5: Data Terminal Ready (DTR)-,                      6: Data Set Ready (DSR)%                      7: Signal GroundAK                      8: Shorted to pin 9 on MicroVAX and VAXstation 2000...tF                      9:    ...series systems, otherwise left floating.  J                                                                      14-45               '                    Hardware Information         X                      When pin 8 is shorted to pin 9, this is a BCC08 (or variant) cable,S                      most commonly used as a console cable on the MicroVAX 2000 andET                      VAXstation 2000 series.  (Other systems may or may not tolerate0                      connecting pin 8 to pin 9.)  F                    The BC16E-nn (where -nn indicates the cable length)H                    cable key impliicitly "flips over" (crosses-over) theE                    signal wires, so all DECconnect MMJ connectors are "                    wired the same.                          //n@                        ----                                 ----@                        |  |---------------------------------|  |@                        ----                                 ----A                                                                \\   B                    The BC16E-nn cross-over wiring looks like this:  @                            Terminal                         Host?                            MMJ                              MMJT  B                         DTR 1 --->---------->----------->--- 6 DSRB                         TXD 2 --->---------->----------->--- 5 RXD>                             3 ------------------------------ 4>                             4 ------------------------------ 3B                         RXD 5 ---<----------<-----------<--- 2 TXDB                         DSR 6 ---<----------<-----------<--- 1 DTR  -                    The BN24H looks like this:_  &                         MMJ       RJ45  $                          1---------8$                          2---------2$                          3---------1$                          4---------3$                          5---------6$                          6---------7  -                    The BN24J looks like this:o                            14-46    a          '                    Hardware Information         &                         MMJ       RJ45  $                          1---------7$                          2---------6$                          3---------3$                          4---------1$                          5---------2$                          6---------8                      Also see:  I                    o  http://www.openvms.compaq.com/wizard/padapters.htmlp  :                    o  http://www.airborn.com.au/rs232.html  5                    o  http://www.stanq.com/cable.html   E                    o  For adapters and connectors, see Section 14.29.   D           __________________________________________________________C           14.29  What connectors and wiring adapters are available?k  F                    The H8571-B converts the (non-2000-series) MicroVAXJ                    DB9 to MMJ DECconnect. The MicroVAX 2000 and VAXstationH                    2000 requires a BCC08 cable (which has the 8-9 short,B                    see Section 14.28) and the H8571-D for use with                    DECconnect.  F                    More recent HP (HP, Compaq or DIGITAL logo) systemsG                    will use either the DECconnect MMJ wiring or (on all G                    recent system designs) the PC-compatible DB9 pinout.   +                    DECconnect MMJ adapters:i  F                        Part:      Converts BC16E MMJ male to fit into:  E                        H8571-C  25 pin DSUB Female to MMJ, Unfiltered @                        H8571-D  EIA232 25 pin male (modem-wired)C                        H8571-E  25 pin DSUB Female to MMJ, Filtered A                        H8571-J  PC/AT 9 pin male (PC serial port)pF                        H8572-0  BC16E MMJ double-female (MMJ extender)=                        H8575-A  EIA232 25 pin female (common) G                        H8575-B  EIA232 9 pin male (MicroVAX II console)iF                        H8575-D  25 Pin to MMJ W/EOS and ESD Protection<                        H8577-AA 6 pin Female MMJ to 8 pin MJG                        BC16E-** MMJ cable, available in various lengthsc  J                                                                      14-47 n  4          '                    Hardware Information         H                    Numerous additional adapters and cables are availableG                    from the _OPEN DECconnect Building Wiring ComponentsoH                    and Applications Catalog_, as well as descriptions of*                    the above-listed parts.  G                    The H8571-A and H8575-A are MMJ to DB25 (female) anda(                    are wired as follows:                      Also see:  I                    o  http://www.openvms.compaq.com/wizard/padapters.html   G                    Jameco offers a USB-A to PS/2 Mini DIN 6 Adapter (asSH                    part 168751), for those folks wishing to (try to) useF                    PS/2 Keyboards via USB-A connections. The LK463 USBI                    keyboard is also a potential option, for those wishing H                    to connect an OpenVMS keyboard to USB systems or (via9                    the provided adapter) to PS/2 systems.   D           __________________________________________________________;           14.30  What is flow control and how does it work?t  8                    XON/XOFF is one kind of flow control.  G                    In ASCII, XON is the <CTRL/Q> character, and XOFF is                      the <CTRL/S>.  E                    XON/XOFF flow control is typically associated withhJ                    asynchronous serial line communications. XON/XOFF is anI                    in-band flow control, meaning that the flow control isf*                    mixed in with the data.  B                    CTS/RTS is another type of flow control, and isF                    sometimes called hardware flow control. Out-of-bandE                    means that seperate lines/pins from the data lines @                    (pins) are used to carry the CTS/RTS signals.  B                    Both kinds of flow control are triggered when aH                    threshold is reached in the incoming buffer. The flowI                    control is suppose to reach the transmitter in time to-J                    have it stop transmitting before the receiver buffer isJ                    full and data is lost. Later, after a sufficient amountH                    of the receiver's buffer is freed up, the resume flowF                    control signal is sent to get the transmitter going                    again.                       14-48 r  r          '                    Hardware Information         E                    DECnet Phase IV on OpenVMS VAX supports the use of B                    asynchronous serial communications as a networkD                    line; of asynch DECnet. The communication devicesC                    (eg. modems, and drivers) must not be configured D                    for XON/XOFF flow control. The incidence of theseD                    (unexpected) in-band characters will corrupt dataC                    packets. Further, the serial line device drivers D                    might normally remove the XON and XOFF charactersH                    from the stream for terminal applications, but DECnetG                    configures the driver to pass all characters throughoF                    and requires that all characters be permitted. (TheG                    communication devices must pass through not only the I                    XON and XOFF characters, they must pass all charactersnI                    including the 8-bit characters. If data compression istJ                    happening, it must reproduce the source stream exactly.J                    No addition or elimination of null characters, and full%                    data transparency.o  B                    An Ethernet network is rather different than anC                    asynchronous serial line. Ethernet specifies theeI                    control of data flow on a shared segment using CSMA/CD I                    (Carrier Sense Multiple Access, with Collision Detect)tH                    An Ethernet station that is ready to transmit listensH                    for a clear channel (Carrier Sense). When the channelH                    is clear, the station begins to transmit by assertingG                    a carrier and encoding the packet appropriately. ThedE                    station concurrently listens to its own signal, toyH                    permit the station to detect if another station beganH                    to transmit at the same time-this is called collisionE                    detection. (The collision corrupts the signal in atI                    way that can reliably be detected.) Upon detecting therG                    collision, both stations will stop transmitting, and G                    will back off and try again a little later. (You cannG                    see a log of this activity in the DECnet NCP networkn                    counters.)n  I                    DECnet provides its own flow control, above and beyonduG                    the flow control of the physical layer (if any). TheeD                    end nodes handshake at the beginning to establishE                    a transmit window size-and a transmitter will onlyrF                    send that much data before stopping and waiting forG                    an acknowledgement. The acknowledgement is only sentcJ                    when the receiver has confirmed the packet is valid. (A  J                                                                      14-49               '                    Hardware Information_        I                    well-configured DECnet generally avoids triggering any1D                    underlying (out-of-band) flow control mechanism.)                                                                                                        14-50                         J                    _______________________________________________________  7           15       Information on Networks and Clusters       H                    The following sections contain information on OpenVMSG                    Networking with IP and DECnet, and on clustering andwE                    volume shadowing, on Fibre Channel, and on related /                    products and configurations.r  D           __________________________________________________________2           15.1  How to connect OpenVMS to a Modem?  J                    Please see the Ask The Wizard area topics starting with5                    (81), (1839), (2177), (3605), etc.e  ;                    o  http://www.openvms.compaq.com/wizard/   E                    o  http://www.openvms.compaq.com/wizard/wizard.zipe  F                    For additional information, please see Section 3.9.  D           __________________________________________________________*           15.2  OpenVMS and IP Networking?  H                    The following sections contain information on OpenVMSD                    and IP networking, as well as IP printing topics.  '           _____________________________l9           15.2.1  How to connect OpenVMS to the Internet?   D                    Some tutorial information and tips for connectingD                    OpenVMS systems to the Internet are available at:  5                    o  http://www.tmesis.com/internet/   '           _____________________________i.           15.2.2  Connecting to an IP Printer?  D                    To connect a printer via the IP telnet or lpr/lpdJ                    protocols, you will need to install and configure an IPH                    stack on OpenVMS, and configure the appropriate print                    queue.n  J                                                                       15-1 g  h          7                    Information on Networks and Clustersu        F                    With current OpenVMS IP implementations, the choiceE                    of telnet or lpr/lpd really amounts to determiningZJ                    which of these works better with the particular printer                    involved.  H                    To support network printing, the printer must includeG                    an internal or external NIC or JetDirect; an adapter :                    connecting the network and the printer.  H                    While it is normally possible to use a host-connectedJ                    printer-when the host supports an LPD or telnet daemon,H                    and OpenVMS and most other operating systems have theF                    ability to serve locally-attached printers to otherF                    hosts on the network-it is generally far easier andG                    far more effective to use a printer that is directlyoH                    attached to the network. If your present printer doesI                    not have a NIC or a JetDirect, acquire an internal (if J                    available) or external NIC or JetDirect. Or replace theI                    printer. And obviously, most any operating system thatiE                    can serve its local printers usually also provides D                    a client that can access remote network-connected                    printers.  J                    please see the Ask The Wizard area topics-starting withF                    topic (1020)-for additional information on IP-based$                    network printing.  ;                    o  http://www.openvms.compaq.com/wizard/   E                    o  http://www.openvms.compaq.com/wizard/wizard.zipa  F                    For additional information, please see Section 3.9.  J                    Please see Section 15.2.3 for information on Postscript;                    printing. comment>(--------------------)   '           _____________________________ C           15.2.3  How do I connect a PostScript printer via TCP/IP?o  I                    Using TCP/IP Services (UCX) as the TCP/IP stack, it issG                    possible to configure queues using the UCX$TELNETSYM E                    (TCP/IP Services prior to V5.0) or TCPIP$TELNETSYMpH                    (with V5.0 and later) in order to print to PostscriptI                    printers. This assumes however that the printer itselfnF                    can convert whatever is passed to it into somethingH                    intelligible. As an example, if the printer has an IP                      15-2e r  s          7                    Information on Networks and Clustersr        J                    address of 123.456.789.101 and jobs should be passed to#                    port 9100 then :   A                    $ INITIALIZE/QUEUE/ON="123.456.789.101:9100" -A2                        /PROCESSOR=UCX$TELNETSYM  -"                        my_ip_queue  A                    $ INITIALIZE/QUEUE/ON="123.456.789.101:9100" -s4                        /PROCESSOR=TCPIP$TELNETSYM  -"                        my_ip_queue  E                    The port number of 9100 is typical of HP JetDirect0E                    cards but may be different for other manufacturersn                    cards.   F                    As a better alternative, DCPS Version 1.4 and laterD                    support IP queues using either HP TCP/IP ServicesD                    for OpenVMS software or Process Software MultinetF                    for OpenVMS. The usage of this type of interface isI                    documented in the DCPS documentation or release notes, G                    and the DCPS$STARTUP.TEMPLATE startup template file.   J                    For general and additional (non-Postscript) IP printingH                    information, please see topic (1020) and other topicsH                    referenced in that topic elsewhere within the Ask The                    Wizard area.   ;                    o  http://www.openvms.compaq.com/wizard/   E                    o  http://www.openvms.compaq.com/wizard/wizard.zip   F                    For additional information, please see Section 3.9.                    Also see:  ,                    o  http://www.wotsit.org/  ?                    Please see Section 15.2.2 for pointers to an /                    introduction to IP printing.   '           _____________________________aH           15.2.4  How do I set a default IP route or gateway on OpenVMS?  H                    If you have TCP/IP Services, then use the command for2                    TCP/IP Services V5.0 and later:                      $ TCPIP;                    SET ROUTE/GATE=x.x.x.x/DEFAULT/PERMANENT   J                                                                       15-3 e  a          7                    Information on Networks and Clustersl        D                    And for earlier TCP/IP Services versions, use the                    command:d                      $ UCX;                    SET ROUTE/GATE=x.x.x.x/DEFAULT/PERMANENT   '           _____________________________EE           15.2.5  How can I set up reverse telnet (like reverse LAT)?e  G                    Though it may seem obvious, Telnet and LAT are quiteeJ                    different-with differing capabilities and design goals.  J                    Please see the documentation around the TCP/IP ServicesJ                    for OpenVMS TELNET command CREATE_SESSION. This commandC                    is the equivilent of the operations performed in_F                    LTLOAD.COM or LAT$SYSTARTUP.COM. There is no TELNETE                    equivilent to the sys$qio[w] control interface fortF                    LTDRIVER (as documented in the I/O User's ReferenceF                    Manual) available, though standard sys$qio[w] callsI                    referencing the created TN device would likely operate                     as expected.d  '           _____________________________ J           15.2.6  Why can't I use PPP and RAS to connect to OpenVMS Alpha?  B                    OpenVMS Alpha IP PPP does not presently supportF                    authentication, and the Microsoft Windows NT optionD                    to disable authentication during a RAS connectionI                    apparently doesn't currently work-RAS connections will H                    require authentication-and this will thus prevent RAS                    connections./  E                    Future versions of OpenVMS and TCP/IP Services maygI                    add this, and future versions of Microsoft Windows mayiB                    permit operations with authentication disabled.  D           __________________________________________________________.           15.3  OpenVMS and DECnet Networking?  H                    The following sections contain information on OpenVMS)                    and DECnet networking.i                          15-4u n  a          7                    Information on Networks and Clusters(      '           _____________________________t2           15.3.1  Can DECnet-Plus operate over IP?  C                    Yes. To configure DECnet-Plus to operate over IP G                    transport and over IP backbone networks, install and G                    configure DECnet-Plus, and install and configure thepJ                    PWIP mechanism available within the currently-installedI                    IP stack. Within TCP/IP Services, this is a PWIPDRIVEReG                    configuration option within the UCX$CONFIG (versions G                    prior to V5.0) or TCPIP$CONFIG (with V5.0 and later) &                    configuration tool.  '           _____________________________SG           15.3.2  What does "failure on back translate address request"e                   mean?a  %                    The error message:   M                    BCKTRNSFAIL, failure on the back translate address requestt  I                    indicates that the destination node is running DECnet-wI                    Plus, and that its naming service (DECnet-Plus DECdns,tD                    LOCAL node database, etc) cannot locate a name toE                    associate with the source node's address. In otherlH                    words, the destination node cannot determine the nodeG                    name for the node that is the source of the incoming                     connection.  H                    Use the DECNET_REGISTER mechanism (on the destinationB                    node) to register or modify the name(s) and theF                    address(es) of the source node. Check the namespace/                    on the source node, as well.m  B                    Typically, the nodes involved are using a LOCALH                    namespace, and the node name and address settings areI                    not coherent across all nodes. Also check to make sure.I                    that the node is entered into its own LOCAL namespace. I                    This can be a problem elsewhere, however. Very rarely,AI                    a cache corruption has been known to cause this error.n7                    To flush the cache, use the command:h  '                    $ RUN SYS$SYSTEM:NCL ?                    flush session control naming cache entry "*"b    J                                                                       15-5               7                    Information on Networks and Clustersa        J                    Also check to see that you are using the latest ECO forG                    DECnet-Plus for the version you are running. DECnet-.9                    Plus can use the following namespaces:a  D                    o  DECdns: DECnet-Plus distributed name services.  B                    o  LocalFile: a local file containing names and                        addresses.  D                    o  DNS/BIND: the TCP/IP distributed name services                        mechanism.  @                    o  The TCP/IP Services (UCX) local host file.  >                    Of these, searching DNS/BIND and LocalFile,>                    respectively, is often the most appropriate!                    configuration.   '           _____________________________)9           15.3.3  Performing SET HOST/MOP in DECnet-Plus?   B                    First, issue the NCL command SHOW MOP CIRCUIT *  '                    $ RUN SYS$SYSTEM:NCLt%                    SHOW MOP CIRCUIT *l  A                    Assume that you have a circuit known as FDDI-0iD                    displayed. Here is an example of the SET HOST/MOP<                    command syntax utilized for this circuit:  J                    $ SET HOST/MOP/ADDRESS=08-00-2B-2C-5A-23/CIRCUIT=FDDI-0  +                    Also see Section 15.6.3.   D           __________________________________________________________>           15.4  How to determine the network hardware address?  I                    Most Alpha and most VAX systems have a console command C                    that displays the network hardware address. Many C                    systems will also have a sticker identifying the E                    address, either on the enclosure or on the network %                    controller itself.a  J                    The system console power-up messages on a number of VAXG                    and Alpha systems will display the hardware address,1C                    particularly on those systems with an integratedc4                    Ethernet network adapter present.                      15-6r s  n          7                    Information on Networks and Clustersc        C                    If you cannot locate a sticker on the system, ifnD                    the system powerup message is unavailable or doesG                    not display the address, and if the system is at the-B                    console prompt, start with the console command:                      HELP   G                    A console command similar to one of the following ismB                    typically used to display the hardware address:                      SHOW DEVICE                     SHOW ETHERNET                    SHOW CONFIG  I                    On the oldest VAX Q-bus systems, the following consoletG                    command can be used to read the address directly offnG                    the (DELQA, DESQA, or the not-supported-in-V5.5-and-t4                    later DEQNA) Ethernet controller:  %                    E/P/W/N:5 20001920   E                    Look at the low byte of the six words displayed by H                    the above command. (The oldest VAX Q-bus systems-suchH                    as the KA630 processor module used on the MicroVAX IIH                    and VAXstation II series-lack a console HELP command,G                    and these systems typically have the primary network F                    controller installed such that the hardware addressB                    value is located at the system physical address                    20001920.)a  H                    If the system is a VAX system, and another VAX systemE                    on the network is configured to answer MaintenanceeC                    and Operations Protocol (MOP) bootstrap requestsbD                    (via DECnet Phase IV, DECnet-Plus, or LANCP), theB                    MOM$SYSTEM:READ_ADDR.EXE tool can be requested:                       B/R5:100 ddcu&                    Bootfile: READ_ADDR  G                    Where ddcu is the name of the Ethernet controller in F                    the above command. The primarly local DELQA, DESQA,F                    and DEQNA Q-bus controllers are usually named XQA0.H                    An attempt to MOP download the READ_ADDR program willG                    ensue, and (if the download is successful) READ_ADDR 5                    will display the hardware address.e  J                                                                       15-7 p             7                    Information on Networks and Clustersv        B                    If the system is running, you can use DECnet orE                    TCP/IP to display the hardware address with one ofI*                    the following commands.  %                    $! DECnet Phase IV '                    $ RUN SYS$SYSTEM:NCPr2                    SHOW KNOWN LINE CHARACTERISTICS  !                    $! DECnet-Plus '                    $ RUN SYS$SYSTEM:NCLo4                    SHOW CSMA-CD STATION * ALL STATUS  3                    $! TCP/IP versions prior to V5.0S                    $ UCX&                    SHOW INTERFACE/FULL  4                    $! TCP/IP versions V5.0 and later                    $ TCPIP&                    SHOW INTERFACE/FULL  C                    A program can be created to display the hardwareiF                    address, reading the necessary information from theC                    network device drivers. An example C program forsE                    reading the Ethernet hardware address (via sys$qiotI                    calls to the network device driver(s)) is available ats%                    the following URL:d  O                    o  http://www.openvms.compaq.com/wizard/swdev/ethernVMS.html   H                    To use the DECnet Phase IV configurator tool to watchD                    for MOP SYSID activity on the local area network:  '                    $ RUN SYS$SYSTEM:NCP M                    SET MODULE CONFIGURATOR KNOWN CIRCUIT SURVEILLANCE ENABLEDl  H                    Let the DECnet Phase IV configurator run for at leastD                    20 minutes, and preferably longer. Then issue the&                    following commands:  '                    $ RUN SYS$SYSTEM:NCPoP                    SHOW MODULE CONFIGURATOR KNOWN CIRCUIT STATUS TO filename.txtN                    SET MODULE CONFIGURATOR KNOWN CIRCUIT SURVEILLANCE DISABLED  E                    The resulting file (named filename.txt) can now be H                    searched for the information of interest. Most DECnetG                    systems will generate MOP SYSID messages identifying H                    items such as the controller hardware address and the                      15-8a    e          7                    Information on Networks and Clusters8        H                    controller type, and these messages are generated and7                    multicast roughly every ten minutes.   I                    Information on the DECnet MOP SYSID messages and other H                    parts of the maintenance protocols is included in theH                    DECnet network architecture specifications referenced#                    in section DOC9.   '           _____________________________ J           15.4.1  How do I reset the LAN (DECnet-Plus NCL) error counters?  .                    On recent OpenVMS releases:  )                    $ RUN SYS$SYSTEM:LANCP E                    SET DEVICE/DEVICE_SPECIFIC=FUNCTION="CCOU" devname   '           _____________________________e>           15.4.2  How do I install DECnet Phase IV on VMS 7.1?  F                    On OpenVMS V7.1, all DECnet binaries were relocatedF                    into separate installation kits-you can selectivelyI                    install the appropriate network: DECnet-Plus (formerlyeG                    known as DECnet OSI), DECnet Phase IV, and HP TCP/IPo1                    Services (often known as UCX).   I                    On OpenVMS versions prior to V7.1, DECnet Phase IV was J                    integrated, and there was no installation question. YouI                    had to install the DECnet-Plus (DECnet/OSI) package on H                    the system, after the OpenVMS upgrade or installation                    completed.l  F                    During an OpenVMS V7.1 installation or upgrade, theD                    installation procedure will query you to learn ifH                    DECnet-Plus should be installed. If you are upgradingI                    to V7.1 from an earlier release or are installing V7.1 E                    from a distribution kit, simply answer "NO" to theaJ                    question asking you if you want DECnet-Plus. Then-afterF                    the OpenVMS upgrade or installation completes - useI                    the PCSI PRODUCT INSTALL command to install the DECnetuI                    Phase IV binaries from the kit provided on the OpenVMSp-                    software distribution kit.M  E                    If you already have DECnet-Plus installed and wishoF                    to revert, you must reconfigure OpenVMS. You cannotG                    reconfigure the "live" system, hence you must rebootyF                    the system using the V7.1 distribution CD-ROM. Then  J                                                                       15-9 _  _          7                    Information on Networks and Clusters         E                    select the DCL ($$$ prompt) option. Then issue thel                    commands:  9                    $$$ DEFINE/SYSTEM PCSI$SYSDEVICE DKA0: ?                    $$$ DEFINE/SYSTEM PCSI$SPECIFIC DKA0:[SYS0.] O                    $$$ PRODUCT RECONFIGURE VMS /REMOTE/SOURCE=DKA0:[VMS$COMMON]e  J                    The above commands assume that the target system deviceH                    and system root are "DKA0:[SYS0.]". Replace this withE                    the actual target device and root, as appropriate. F                    The RECONFIGURE command will then issue a series ofH                    prompts. You will want to reconfigure DECnet-Plus offG                    the system, obviously. You will then want to use the E                    PCSI command PRODUCT INSTALL to install the DECnet5D                    Phase IV kit from the OpenVMS distribution media.  J                    Information on DECnet support, and on the kit names, isH                    included in the OpenVMS V7.1 installation and upgrade!                    documentation.   I                    Subsequent OpenVMS upgrade and installation procedures H                    can and do offer both DECnet Phase IV and DECnet-Plus!                    installations.   D           __________________________________________________________D           15.5  How can I send (radio) pages from my OpenVMS system?  >                    There are third-party products available toB                    send messages to radio paging devices (pagers),B                    communicating via various protocols such as TAPF                    (Telocator Alphanumeric Protocol); paging packages.  H                    RamPage (Ergonomic Solutions) is one of the availableF                    packages that can generate and transmit messages toG                    radio pagers. Target Alert (Target Systems; formerlyiH                    the DECalert product) is another. Networking DynamicsC                    Corp has a product called Pager Plus. The SystemnD                    Watchdog package can also send pages. The ProcessA                    Software package PMDF can route specific email):                    addresses to a paging service, as well.  H                    Many commercial paging services provide email contactF                    addresses for their paging customers-you can simplyF                    send or forward email directly to the email address)                    assigned to the pager.                       15-10               7                    Information on Networks and Clusters         F                    Some people implement the sending of pages to radioD                    pagers by sending commands to a modem to take theH                    "phone" off the "hook", and then the paging sequence,G                    followed by a delay, and then the same number that a H                    human would dial to send a numeric page. (This is notG                    entirely reliable, as the modem lacks "call progress-D                    detection", and the program could simply send theH                    dial sequence when not really connected to the paging?                    company's telephone-based dial-up receiver.)-  D                    See Section 13.1 for information on the available'                    catalog of products.l  D           __________________________________________________________4           15.6  OpenVMS, Clusters, Volume Shadowing?  H                    The following sections contain information on OpenVMSF                    and Clusters, Volume Shadowing, and Cluster-related%                    system parameters.J  '           _____________________________ B           15.6.1  OpenVMS Cluster Communications Protocol Details?  D                    The following sections contain information on theI                    OpenVMS System Communications Services (SCS) Protocol.   '           _____________________________4?           15.6.1.1  OpenVMS Cluster (SCS) over DECnet? Over IP?   H                    The OpenVMS Cluster environment operates over variousE                    network protocols, but the core of clustering uses F                    the System Communications Services (SCS) protocols,D                    and SCS-specific network datagrams. Direct (full)+                    connectivity is assumed.   G                    An OpenVMS Cluster does not operate over DECnet, nor2                    over IP.   9                    No SCS protocol routers are available.n  F                    Many folks have suggested operating SCS over DECnetC                    or IP over the years, but SCS is too far down inrB                    the layers, and any such project would entail aE                    major or complete rewrite of SCS and of the DECnetcD                    or IP drivers. Further, the current DECnet and IPI                    implementations have large tracts of code that operate F                    at the application level, while SCS must operate in  J                                                                      15-11 P  :          7                    Information on Networks and Clusters         G                    the rather more primitive contexts of the system and J                    particularly the bootstrap-to get SCS to operate over aI                    DECnet or IP connection would require relocating majoreF                    portions of the DECnet or IP stack into the kernel.G                    (And it is not clear that the result would even meet(;                    the bandwidth and latency expectations.)M  D                    The usual approach for multi-site OpenVMS ClusterI                    configurations involves FDDI, Memory Channel (MC2), or J                    a point-to-point remote bridge, brouter, or switch. TheI                    connection must be transparent, and it must operate at J                    10 megabits per second or better (Ethernet speed), withI                    latency characteristics similar to that of Ethernet or I                    better. Various sites use FDDI, MC2, ATM, or point-to- !                    point T3 link.a  '           _____________________________ D           15.6.1.2  Configuring Cluster SCS for path load balancing?  I                    This section discusses OpenVMS Cluster communications,wJ                    cluster terminology, related utilities, and command and&                    control interfaces.  '           _____________________________ *           15.6.1.2.1  Cluster Terminology?  I                    SCS: Systems Communication Services. The protocol used H                    to communicate between VMSCluster systems and betweenE                    OpenVMS systems and SCS-based storage controllers. C                    (SCSI-based storage controllers do not use SCS.)   C                    PORT: A communications device, such as DSSI, CI,_G                    Ethernet or FDDI. Each CI or DSSI bus is a differentfG                    local port, named PAA0, PAB0, PAC0 etc. All Ethernetk>                    and FDDI busses make up a single PEA0 port.  B                    VIRTUAL CIRCUIT: A reliable communications pathF                    established between a pair of ports. Each port in aF                    VMScluster establishes a virtual circuit with every.                    other port in that cluster.  I                    All systems and storage controllers establish "Virtual A                    Circuits" to enable communications between all ,                    available pairs of ports.                      15-12               7                    Information on Networks and Clusters         H                    SYSAP: A "system application" that communicates usingH                    SCS. Each SYSAP communicates with a particular remote1                    SYSAP. Example SYSAPs include:   ;                    VMS$DISK_CL_DRIVER connects to MSCP$DISKiG                    The disk class driver is on every VMSCluster system.bJ                    MSCP$DISK is on all disk controllers and all VMSClusterH                    systems that have SYSGEN parameter MSCP_LOAD set to 1  ;                    VMS$TAPE_CL_DRIVER connects to MSCP$TAPEtG                    The tape class driver is on every VMSCluster system. J                    MSCP$TAPE is on all tape controllers and all VMSClusterI                    systems that have SYSGEN parameter TMSCP_LOAD set to 1   <                    VMS$VAXCLUSTER connects to VMS$VAXCLUSTERD                    This SYSAP contains the connection manager, whichG                    manages cluster connectivity, runs the cluster state J                    transition algorithm, and implements the cluster quorumG                    algorithm. This SYSAP also handles lock traffic, andcB                    various other cluster communications functions.  ;                    SCS$DIR_LOOKUP connects to SCS$DIRECTORY F                    This SYSAP is used to find SYSAPs on remote systems  !                    MSCP and TMSCPaF                    The Mass Storage Control Protocol and the Tape MSCPE                    servers are SYSAPs that provide access to disk andaH                    tape storage, typically operating over SCS protocols.J                    MSCP and TMSCP SYSAPs exist within OpenVMS (for OpenVMSG                    hosts serving disks and tapes), within CI- and DSSI-cI                    based storage controllers, and within host-based MSCP- F                    or TMSCP storage controllers. MSCP and TMSCP can beH                    used to serve MSCP and TMSCP storage devices, and canJ                    also be used to serve SCSI and other non-MSCP/non-TMSCP#                    storage devices.e  I                    SCS CONNECTION: A SYSAP on one node establishes an SCSwF                    connection to its counterpart on another node. ThisJ                    connection will be on ONE AND ONLY ONE of the available$                    virtual circuits.        J                                                                      15-13 r  d          7                    Information on Networks and Clustersn      '           _____________________________ 5           15.6.1.2.2  Cluster Communications Control?r  G                    When there are multiple virtual circuits between twolH                    OpenVMS systems it is possible for the VMS$VAXCLUSTERG                    to VMS$VAXCLUSTER connection to use any one of theseeJ                    circuits. All lock traffic between the two systems will?                    then travel on the selected virtual circuit.l  H                    Each port has a "LOAD CLASS" associated with it. ThisF                    load class helps to determine which virtual circuitG                    a connection will use. If one port has a higher load H                    class than all others then this port will be used. IfH                    two or more ports have equally high load classes thenE                    the connection will use the first of these that itnJ                    finds. Normally all CI and DSSI ports have a load classJ                    of 14(hex), while the Ethernet and FDDI ports will have*                    a load class of A(hex).  E                    For instance, if you have multiple DSSI busses and H                    an FDDI, the VMS$VAXCLUSTER connection will chose theF                    DSSI bus as this path has the system disk, and thusH                    will always be the first DSSI bus discovered when the(                    OpenVMS system boots.  C                    To force all lock traffic off the DSSI and on to D                    the FDDI, for instance, an adjustment to the loadE                    class value is required, or the DSSI SCS port mustw                    be disabled.   I                    Note that with PE ports, you can typically immediately J                    re-enable the path, permitting failover to occur shouldI                    congestion or a problem arise-a running average of the F                    path latency is checked when the virtual circuit isG                    formed, and at periodic intervals (circa every three F                    seconds), and when a problem with a virtual circuit                    arises.  C                    In the case of PEDRIVER, the driver handles loadpB                    balancing among the available Ethernet and FDDII                    connections based on the lowest latency path availableaH                    to it. Traffic will be routed through that path until=                    an event occurs that requires a fail-over.n                        15-14               7                    Information on Networks and Clusters       '           _____________________________gI           15.6.1.2.3  Cluster Communications Control Tools and Utilities?   C                    In most OpenVMS versions, you can use the tools:l  0                    o  SYS$EXAMPLES:LAVC$STOP_BUS  1                    o  SYS$EXAMPLES:LAVC$START_BUS:  F                    These tools permit you to disable or enable all SCS9                    traffic on the on the specified paths.t  I                    You can also use a preferred path mechanism that tells I                    the local MSCP disk class driver (DUDRIVER) which pathiI                    to a disk should be used. Generally, this is used withaH                    dual-pathed disks, forcing I/O traffic through one ofI                    the controllers instead of the other. This can be used I                    to implement a crude form of I/O load balancing at theu"                    disk I/O level.  E                    Prior to V7.2, the preferred path feature uses them                    tool:  -                    o  SYS$EXAMPLES:PREFER.MARp  G                    In OpenVMS V7.2 and later, you can use the followingr                    DCL command:u  '                    $ SET PREFERRED_PATHn  D                    The preferred path mechanism does not disable norC                    affect SCS operations on the non-preferred path.b  D                    With OpenVMS V7.3 and later, please see the SCACPG                    utility for control over cluster communications, SCStH                    virtual circuit control, port selection, and related.  '           _____________________________ 4           15.6.2  Cluster System Parameter Settings?  H                    The following sections contain details of configuring5                    cluster-related system parameters.r      J                                                                      15-15 r             7                    Information on Networks and Clustersr      '           _____________________________bE           15.6.2.1  What is the correct value for EXPECTED_VOTES in ai                     VMScluster?o  E                    The VMScluster connection manager uses the concepttF                    of votes and quorum to prevent disk and memory dataD                    corruptions-when sufficient votes are present forF                    quorum, then access to resources is permitted. WhenJ                    sufficient votes are not present, user activity will beG                    blocked. The act of blocking user activity is called G                    a "quorum hang", and is better thought of as a "user H                    data integrity interlock". This mechanism is designedI                    to prevent a partitioned VMScluster, and the resultant_I                    massive disk data corruptions. The quorum mechanism ispH                    expressly intended to prevent your data from becoming&                    severely corrupted.  E                    On each OpenVMS node in a VMScluster, one sets two C                    values in SYSGEN: VOTES, and EXPECTED_VOTES. The G                    former is how many votes the node contributes to the F                    VMScluster. The latter is the total number of votesE                    expected when the full VMScluster is bootstrapped.   G                    Some sites erroneously attempt to set EXPECTED_VOTES F                    too low, believing that this will allow when only aI                    subset of voting nodes are present in a VMScluster. It0G                    does not. Further, an erroneous setting in EXPECTED_ C                    VOTES is automatically corrected once VMScluster H                    connections to other nodes are established; user dataG                    is at risk of severe corruptions during the earliest0G                    and most vulnerable portion of the system bootstrap, @                    before the connections have been established.  F                    One can operate a VMScluster with one, two, or manyI                    voting nodes. With any but the two-node configuration, G                    keeping a subset of the nodes active when some nodessC                    fail can be easily configured. With the two-nodefB                    configuration, one must use a primary-secondaryI                    configuration (where the primary has all the votes), acJ                    peer configuration (where when either node is down, theF                    other hangs), or (preferable) a shared quorum disk.                            15-16 s  p          7                    Information on Networks and Clusters0        A                    Use of a quorum disk does slow down VMScluster A                    transitions somewhat - the addition of a third F                    voting node that contributes the vote(s) that wouldB                    be assigned to the quorum disk makes for fasterE                    transitions-but the use of a quorum disk does mean J                    that either node in a two-node VMScluster configuration;                    can operate when the other node is down.   G                    If you choose to use a quoum disk, a QUORUM.DAT file_C                    will be automatically created when OpenVMS firstwH                    boots and when a quorum disk is specified - well, theI                    QUORUM.DAT file will be created when OpenVMS is booted G                    without also needing the votes from the quorum disk./  A                    In a two-node VMScluster with a shared storage F                    interconnect, typically each node has one vote, andG                    the quorum disk also has one vote. EXPECTED_VOTES is                      set to three.  F                    Using a quorum disk on a non-shared interconnect isH                    unnecessary-the use of a quorum disk does not provideG                    any value, and the votes assigned to the quorum disk H                    should be assigned to the OpenVMS host serving access                    to the disk.e  C                    For information on quorum hangs, see the OpenVMS A                    documentation. For information on changing the D                    EXPECTED_VOTES value on a running system, see theB                    SET CLUSTER/EXPECTED_VOTES command, and see theF                    documentation for the AMDS and Availability ManagerC                    tools. Also of potential interest is the OpenVMS J                    system console documentation for the processor-specificG                    console commands used to trigger the IPC (Interrrupt J                    Priority Level %x0C; IPL C) handler. AMDS, AvailabilityI                    Manager, and the IPC handler can each be used to clear I                    a quorum hang. Use of AMDS and Availability Manager is G                    generally recommended over IPC, particularly because G                    IPC can cause CLUEXIT bugchecks if the system should H                    remain halted beyond the cluster sanity timer limits.  ?                    The quorum scheme is a set of "blade guards" E                    deliberately implemented by OpenVMS Engineering to F                    provide data integrity-remove these blade guards atD                    your peril. OpenVMS Engineering did not implementG                    the quorum mechanism to make a system manager's lifes  J                                                                      15-17 _  _          7                    Information on Networks and Clusters         H                    more difficult- the quorum mechanism was specificallyH                    implemented to keep your data from getting scrambled.  '           _____________________________oE           15.6.2.2  Explain disk (or tape) allocation class settings?t  E                    The allocation class mechanism provides the system I                    manager with a way to configure and resolve served andsH                    direct paths to storage devices within a cluster. AnyG                    served device that provides multiple paths should be G                    configured using a non-zero allocation class, either E                    at the MSCP (or TMSCP) storage controllers, at the H                    port (for port allocation classes), or at the OpenVMSE                    MSCP (or TMSCP) server. All controllers or servers F                    providing a path to the same device should have theE                    same allocation class (at the port, controller, or !                    server level).   E                    Each disk (or tape) unit number used within a non-nG                    zero disk (or tape) allocation class must be unique, F                    regardless of the particular device prefix. For theH                    purposes of multi-path device path determination, anyJ                    disk (or tape) device with the same unit number and theH                    same disk (or tape) allocation class configuration is1                    assumed to be the same device.   B                    If you are reconfiguring disk device allocationH                    classes, you will want to avoid the use of allocationF                    class one ($1$) until/unless you have Fibre ChannelJ                    storage configured. (Fibre Channel storage specifically@                    requires the use of allocation class $1$. eg:                    $1$DGA0:.)   '           _____________________________ H           15.6.2.2.1  How to configure allocation classes and Multi-Path                       SCSI?o  B                    The HSZ allocation class is applied to devices,F                    starting with OpenVMS V7.2. It is considered a portJ                    allocation class (PAC), and all device names with a PACI                    have their controller letter forced to "A". (You mightsI                    infer from the the text in the "Guidelines for OpenVMS J                    Cluster Configurations" that this is something you haveF                    to do, though OpenVMS will thoughtfully handle this%                    renaming for you.)r                      15-18 a             7                    Information on Networks and Clustersa        H                    You can force the device names back to DKB by settingH                    the HSZ allocation class to zero, and setting the PKBJ                    PAC to -1. This will use the host allocation class, andG                    will leave the controller letter alone (that is, the I                    DK controller letter will be the same as the SCSI portnI                    (PK) controller). Note that this won't work if the HSZ I                    is configured in multibus failover mode. In this case,cH                    OpenVMS requires that you use an allocation class for                    the HSZ.   H                    When your configuration gets even moderately complex,C                    you must pay careful attention to how you assign F                    the three kinds of allocation class: node, port andF                    HSZ/HSJ, as otherwise you could wind up with deviceC                    naming conflicts that can be painful to resolve.   @                    The display-able path information is for SCSIE                    multi-path, and permits the multi-path software to J                    distinguish between different paths to the same device.E                    If you have two paths to $1$DKA100, for example by_I                    having two KZPBA controllers and two SCSI buses to thetH                    HSZ, you would have two UCBs in a multi-path set. TheI                    path information is used by the multi-path software tor6                    distinguish between these two UCBs.  G                    The displayable path information describes the path;hF                    in this case, the SCSI port. If port is PKB, that'sF                    the path name you get. The device name is no longerH                    completely tied to the port name; the device name nowJ                    depends on the various allocation class settings of the1                    controller, SCSI port or node..  D                    The reason the device name's controller letter isF                    forced to "A" when you use PACs is because a sharedH                    SCSI bus may be configured via different ports on theJ                    various nodes connected to the bus. The port may be PKBG                    on one node, and PKC on the other. Rather obviously,tH                    you will want to have the shared devices use the sameD                    device names on all nodes. To establish this, youE                    will assign the same PAC on each node, and OpenVMS E                    will force the controller letter to be the same onSE                    each node. Simply choosing "A" was easier and moreoG                    deterministic than negotiating the controller lettereJ                    between the nodes, and also parallels the solution used  J                                                                      15-19               7                    Information on Networks and Clusters         F                    for this situation when DSSI or SDI/STI storage was                    used.  E                    To enable port allocation classes, see the SYSBOOT E                    command SET/BOOT, and see the DEVICE_NAMING system,                    parameter.s  D                    This information is also described in the Cluster=                    Systems and Guidelines for OpenVMS Clusterv*                    Configurations manuals.  '           _____________________________ =           15.6.3  Tell me about SET HOST/DUP and SET HOST/HSCt  I                    The OpenVMS DCL commands SET HOST/DUP and SET HOST/HSC E                    are used to connect to storage controllers via the I                    Diagnostics and Utility Protocol (DUP). These commands H                    require that the FYDRIVER device driver be connected.J                    This device driver connection is typically performed byJ                    adding the following command(s) into the system startup%                    command procedure:l  $                    On OpenVMS Alpha:  *                    $ RUN SYS$SYSTEM:SYSMANH                    SYSMAN> IO CONNECT FYA0/NOADAPTER/DRIVER=SYS$FYDRIVER  "                    On OpenVMS VAX:  *                    $ RUN SYS$SYSTEM:SYSGEN1                    SYSGEN> CONNECT FYA0/NOADAPTER   G                    Alternatives to the DCL SET HOST/DUP command includepI                    the console SET HOST command available on various mid- 2                    to recent-vintage VAX consoles:  G                    Access to Parameters on an Embedded DSSI controller:r  H                    SET HOST/DUP/DSSI[/BUS:{0:1}] dssi_node_number PARAMS  C                    Access to Directory of tools on an Embedded DSSI                     controller:  H                    SET HOST/DUP/DSSI[/BUS:{0:1}] dssi_node_number DIRECT  C                    Access to Parameters on a KFQSA DSSI controller:T  D                    SHOW UQSSP ! to get port_controller_number PARAMSC                    SET HOST/DUP/UQSSP port_controller_number PARAMS                       15-20 d  t          7                    Information on Networks and ClustersU        H                    These console commands are available on most MicroVAXJ                    and VAXstation 3xxx series systems, and most (all?) VAXH                    4xxx series systems. For further information, see theG                    system documentation and-on most VAX systems-see the %                    console HELP text.)  A                    EK-410AB-MG, _DSSI VAXcluster Installation and C                    Troubleshooting_, is a good resource for settingmC                    up a DSSI VMScluster on OpenVMS VAX nodes. (This E                    manual predates coverage of OpenVMS Alpha systems,eG                    but gives good coverage to all hardware and softwareTI                    aspects of setting up a DSSI-based VMScluster-and most E                    of the concepts covered are directly applicable to I                    OpenVMS Alpha systems. This manual specifically coversfF                    the hardware, which is something not covered by the>                    standard OpenVMS VMScluster documentation.)  G                    Also see Section 15.3.3, and for the SCS name of theA0                    OpenVMS host see Section 5.6.  '           _____________________________ 8           15.6.4  How do I rename a DSSI disk (or tape?)  G                    If you want to renumber or rename DSSI disks or DSSIiI                    tapes, it's easy-if you know the secret incantation...d                       From OpenVMS:  *                    $ RUN SYS$SYSTEM:SYSGEN1                    SYSGEN> CONNECT FYA0/NOADAPTER                     SYSGEN> ^ZeL                    $ SET HOST/DUP/SERV=MSCP$DUP/TASK=PARAMS <DSSI-NODE-NAME>                    ...$                    PARAMS> STAT CONFR                    <The software version is normally near the top of the display.>                    PARAMS> EXITC                    ...  D                    From the console on most 3000- and 4000-class VAXD                    system consoles... (Obviously, the system must be0                    halted for these commands...)  #                    Integrated DSSI:e  H                    SET HOST/DUP/DSSI[/BUS:[0:1]] dssi_node_number PARAMS  J                                                                      15-21 _  _          7                    Information on Networks and Clusters                             KFQSA:1  C                    SET HOST/DUP/UQSSP port_controller_number PARAMSi  D                    For information on how to get out into the PARAMSE                    subsystem, also see the HELP at the console promptEG                    for the SET HOST syntax, or see the HELP on SET HOSToG                    /DUP (once you've connected FYDRIVER under OpenVMS).7  F                    Once you are out into the PARAMS subsystem, you canJ                    use the FORCEUNI option to force the use of the UNITNUMG                    value and then set a unique UNITNUM inside each DSSIVI                    ISE-this causes each DSSI ISE to use the specfied unit G                    number and not use the DSSI node as the unit number. J                    Other parameters of interest are NODENAME and ALLCLASS,J                    the node name and the (disk or tape) cluster allocation                    class.o  C                    Ensure that all disk unit numbers used within anpH                    OpenVMS Cluster disk allocation class are unique, andG                    all tape unit numbers used within an OpenVMS ClusterlH                    tape allocation class are also unique. For details onI                    the SCS name of the OpenVMS host, see Section 5.6. For ?                    details of SET HOST/DUP, see Section 15.6.3.n  '           _____________________________ J           15.6.5  Where can I get Fibre Channel Storage (SAN) information?  L                    o  http://www.openvms.compaq.com/openvms/fibre/index.html  '           _____________________________ 8           15.6.6  How can I split up an OpenVMS Cluster?  F                    Review the VMScluster documentation, and the SystemF                    Management documentation. The following are the keyF                    points, but are likely not the only things you will"                    need to change.  J                    OpenVMS Cluster support is directly integrated into theJ                    operating system, and there is no way to remove it. YouH                    can, however, remote site-specific tailoring that was@                    added for a particular cluster configuration.  H                    First: Create restorable image BACKUPs of each of theI                    current system disks. If something gets messed up, you 0                    want a way to recover, right?                      15-22               7                    Information on Networks and Clusters         D                    Create standalone BACKUP kits for the OpenVMS VAXF                    systems, and create or acquire bootable BACKUP kits1                    for the OpenVMS Alpha systems..  I                    Use CLUSTER_CONFIG or CLUSTER_CONFIG_LAN to remove thesI                    various system roots and to shut off boot services and '                    VMScluster settings.   E                    Create as many architecture-specific copies of the I                    system disks as required. Realize that the new systems F                    will all likely be booting through root SYS0-if youJ                    have any system-specific files in any other roots, save                    them.  J                    Relocate the copies of the VMScluster common files onto0                    each of the new system disks.  F                    Reset the console parameters and boot flags on each7                    system for use on a standalone node.i  I                    Reset the VAXCLUSTER and NISCS_LOAD_PEA0 parameters toe4                    0 in SYSGEN and in MODPARAMS.DAT.  E                    Clobber the VMScluster group ID and password usingr                    SYSMAN.  J                    Reboot the systems seperately, and run AUTOGEN on each.  E                    Shut off MOP services via NCP or LANCP on the boot                      server nodes.  E                    Permanent seperation also requires the duplicationnD                    of shared files. For a list of the files commonlyA                    shared, please see the most current version ofpF                    SYS$STARTUP:SYLOGICALS.TEMPLATE, and specifically aJ                    version from OpenVMS V7.2 or later. The following files9                    are typically shared within a cluster:               J                                                                      15-23 d  u          7                    Information on Networks and Clustersg        ]                      Filename:              default directory (in common root) and file type: B                        SYSUAF                      SYS$SYSTEM:.DATB                        SYSUAFALT                   SYS$SYSTEM:.DATB                        SYSALF                      SYS$SYSTEM:.DATB                        RIGHTSLIST                  SYS$SYSTEM:.DATB                        NETPROXY                    SYS$SYSTEM:.DATB                        NET$PROXY                   SYS$SYSTEM:.DATB                        NETOBJECT                   SYS$SYSTEM:.DATB                        NETNODE_REMOTE              SYS$SYSTEM:.DAT_                        QMAN$MASTER                 SYS$SYSTEM: (this is a set of related files)_B                        LMF$LICENSE                 SYS$SYSTEM:.LDBC                        VMSMAIL_PROFILE             SYS$SYSTEM:.DATAtB                        VMS$OBJECTS                 SYS$SYSTEM:.DATC                        VMS$AUDIT_SERVER            SYS$MANAGER:.DATJC                        VMS$PASSWORD_HISTORY        SYS$SYSTEM:.DATAMC                        NETNODE_UPDATE              SYS$MANAGER:.COMfC                        VMS$PASSWORD_POLICY         SYS$LIBRARY:.EXEVS                        LAN$NODE_DATABASE           SYS$SYSTEM:LAN$NODE_DATABASE.DAT_  J                    Also see the topics on "cluster divorce" in the Ask The                    Wizard area.u  ;                    o  http://www.openvms.compaq.com/wizard/o  E                    o  http://www.openvms.compaq.com/wizard/wizard.zips  F                    For additional information, please see Section 3.9.  D                    Information on changing node names is included in                    Section 5.6.   '           _____________________________ .           15.6.7  Details on Volume Shadowing?  I                    This section contains information on host-based volume J                    shadowing; on the disk mirroring capabilities available"                    within OpenVMS.  '           _____________________________aG           15.6.7.1  Does volume shadowing require a non-zero allocationr                     classes?  C                    Yes, use of host-based Volume Shadowing requiresPH                    that the disk(s) involved be configured in a non-zero$                    allocation class.                      15-24 t  n          7                    Information on Networks and Clusters         I                    Edit SYS$SYSTEM:MODPARAMS.DAT to include a declarationrG                    of an non-zero allocation class, such as setting thes8                    host allocation class to the value 7:                       ALLOCLASS = 7  7                    Then AUTOGEN the system, and reboot.n  F                    You should now be able to form the shadow set via a1                    command such as the following:t  O                    $ MOUNT dsa1007: /SHADOW=($7$dkb300:,$7$dkb500:) volumelabeli  F                    When operating in an OpenVMS Cluster, this sequenceH                    will typically change the disk names from the SCSNODEH                    prefix (scsnode$dkann) to the allocation-class prefixI                    ($7$dkannn). This may provide you with the opportunityeG                    to move to a device-independent scheme using logicalpG                    name constructs such as the DISK$volumelabel logical I                    names in your startup and application environments; anoF                    opportunity to weed out physical device references.  I                    Allocation class one is used by Fibre Channel devices;aJ                    it can be best to use another non-zero allocation classH                    even if Fibre Channel is not currently configured and)                    not currently planned.l  '           ______________________________;           15.6.7.2  Volume Shadowing MiniCopy vs MiniMerge?   F                    MiniMerge support has been available for many yearsG                    with OpenVMS host-based volume shadowing, so long as H                    you had MSCP controllers (eg: HSC, HSJ, or HSD) whichF                    supported the Volume Shadowing Assist called "Write$                    History Logging".  B                    If you want minimerges on HSG80 (Fibre Channel)B                    controllers, please see the "Fibre Channel in aG                    Disaster-Tolerant OpenVMS Cluster System" whitepapers                    at:  J                    o  http://www.openvms.compaq.com/openvms/fibre/fc_hbvs_                        dtc_wp.pdf  H                    Minimerge support on HSG80 is expected to require ACSI                    8.7 and OpenVMS Alpha V7.3-1, assuming the developmente*                    goes according to plan.  J                                                                      15-25 u  a          7                    Information on Networks and Clusters         D                    The following sections describe both MiniCopy andF                    MiniMerge, and can provide a basis for discussions.  '           _____________________________            15.6.7.2.1  MiniCopy?a  I                    A Shadowing Full Copy occurs when you add a disk to aneG                    existing shadowset using a MOUNT command; the entire E                    contents of the disk are effectively copied to the F                    new member (using an algorithm that goes through inF                    127-block increments and reads one member, comparesH                    with the target disk, and if the data differs, writesD                    the data to the target disk and loops back to theC                    read step, until the data is equal for that 127-rF                    block section). (This is one of the reasons why theG                    traditional recommendation for adding new volumes to F                    a shadowset was to use a BACKUP/PHYSICAL copy of anF                    existing shadowset volume, simply because the readsJ                    then usually matched and thus shadowing usually avoided,                    the need for the writes.)  G                    If you warn OpenVMS ahead of time (at dismount time)iI                    that you're planning to remove a disk from a shadowsetRB                    but re-add it later, OpenVMS will keep a bitmapE                    tracking what areas of the disk have been modifiedsH                    while the disk was out of the shadowset, and when youH                    re-add it later with a MOUNT command OpenVMS only hasI                    to update the areas of the returned disk that the bit-CG                    map indicates are now out-of-date. OpenVMS does thisiH                    with a read source / write target algorithm, which isG                    much faster than the shenanigans the Full Copy does, H                    so even if all of the disk has changed, a MiniCopy is+                    faster than a Full Copy.   '           _____________________________             15.6.7.2.2  MiniMerge?  F                    A Shadowing Merge is initiated when an OpenVMS nodeI                    in the cluster (which had a shadowset mounted) crashescH                    or otherwise leaves unexpectedly, without dismountingI                    the shadowset first. In this case, OpenVMS must ensure I                    that the data is identical, since Shadowing guarantees1D                    that the data on the disks in a shadowset will beJ                    identical. In a regular Merge operation, Shadowing uses                      15-26 n  l          7                    Information on Networks and Clusterse        J                    an algorithm similar to the Full Copy algorithm (exceptE                    that it can choose either of the members' contentssH                    as the source data, since both are considered equallyJ                    valid), and scans the entire disk. Also, to make thingsF                    worse, for any read operations in the area ahead ofG                    what has been merged, Shadowing will first merge the H                    area containing the read data, then allow the read to                    occur.   B                    A Merge can be very time-consuming and very I/OH                    intensive, so some controllers have Shadowing AssistsF                    to make it faster. If the controllers support WriteD                    History Logging, the controllers record the areasG                    (LBNs) that are the subject of Shadowing writes, and G                    if a node crashes, the surviving nodes can query themG                    controllers to find out what exact areas of the diskcJ                    the departed node was writing to just before the crash,H                    and thus Shadowing only needs to merge just those fewE                    areas, so this tends to take seconds as opposed to -                    hours for a regular Merge.D                                                J                                                                      15-27 d  N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faq N  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.com    ------------------------------  # Date: Thu, 03 Jul 2003 17:18:23 GMTf2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman); Subject: OpenVMS Frequently Asked Questions (FAQ), Part 9/9u2 Message-ID: <zzZMa.3900$bl3.3344@news.cpqcorp.net>                                 J           ________________________________________________________________           Index     H           1858                              ATW,3-12,  3-13, 5-21, 5-22,J             17-Nov-1858,4-2                    5-23, 5-31, 8-6, 9-3, 10-2,G           2000                                 10-4, 10-7, 10-9, 10-17, H           __Year,5-33___________________       10-22, 10-26, 15-1, 15-2,  :           A                                    15-3, 15-248           ______________________________    AUTOGEN,5-10I           Access Control List Entry,5-9     Automatic Foreign Command,8-1n3           ACCVIO,5-33                       AVI,7-2S5           ACE,5-9                           awk,13-14VJ           ACTS,4-8                          ______________________________-           Agnew, Jim,14-29                  BnJ           Allocation Class                  ______________________________:             Fibre Channel,15-25             Backdrops,11-9H             Non-Zero,15-24,  15-25          BACKUP/IGNORE=INTERLOCK,5-48B             Volume Shadowing,15-24          Bad Block Handling,9-38           ALLOCLASS system parameter,       BADLIB,13-20;              15-25                          BADTYPSTR,13-20u6           AlphaPC 164LX,14-18               bash,13-167           AlphaPC 164SX,14-18               Batch,13-19e8           AMASK,14-25                       BB_WATCH,4-6?           Ambassador,1-10                   BC16E,14-46,  14-47 7           AMD,2-9                           BCC08,14-47n<           ANSI C,10-19                      BCKTRNSFAIL,15-5E           AP,10-6                           Berryman, Mark,1-4,  13-3 ;           Apache,13-8                       Bi-Endian,10-18r<           ar,13-14                          Big-Endian,10-185           Archie,13-7                       BIND,15-6t7           ARCH_DEFS.REQ,10-16               bison,13-14c1           Argument Pointer,10-6             Block 8           ARRE,14-40,  14-41, 14-43           Disk,14-437           ARWE,14-40,  14-41, 14-43         BN24H,14-46 7           ASAP                              BN24J,14-46 5             See DSPP                        BNC,14-35i>           Ask The Wizard,3-12,  3-13,       BNU Bookreader,3-16              5-21, 5-22, 5-23, 5-31,        Bookreader5              8-6, 9-3, 10-2, 10-4, 10-7,      BNU,3-1 8                                               MGBOOK,3-18              10-9, 10-17, 10-22, 10-26,     Browser,13-4C              15-1, 15-2, 15-3, 15-24        Byers, Robert Alan,13-8            ATA,7-1,  9-5   J                                                                    Index-1 o  o                              Index        D           bzip2,13-25                       Columbia University,13-37           ______________________________    COMMON,10-6s7           C                                 Compaq,5-32 F           ______________________________    Compaq Secure Web Browser,4           C,10-19,  10-26                      13-174             Compaq C Compiler,10-19,        Composer;                10-26                          Mozilla,13-17iE             DEC C Compiler,10-19,  10-26    Computer Associates,13-17 9             Device Drivers,10-23            console,14-11r3             HP C Compiler,10-19,  10-26     Console A             VAX C Compiler,10-19              VAXstation 3100,9-4 8           CA,13-17                          Contrl,13-115           Caesar                            COPY,10-9 6             Julius,4-3                      CPAN,13-246           CalTech,13-8                      cpio,13-148           Carrier Sense Multiple Access,    $creprc,10-9/              with Collision Detect,         CSA 6              14-49                            See DSPP4           CD                                CSLG,2-89             Recording,9-7,  14-43           CSMA/CD,14-49 6           CD-Audio,7-1                      CSWB,13-17J           CD Player,7-1                     ______________________________-           CD-R,9-7,  13-9, 14-43            DDJ           CD-R/RW,9-7,  9-9                 ______________________________C           CDRECORD,9-7,  14-43              Dachtera, David J.,13-8a:           CD-RW,9-7,  13-9, 14-43           DATMISCH,10-19F           CDWRITE,9-7                       Daylight Savings Time,4-2,@           CGI,13-19                            4-12, 4-17, 10-23E           CHARON-VAX,13-26                  DAYLIGHT_SAVINGS.COM,4-12h=           cli$get_value,10-4                DB9,14-45,  14-47u/           Clock                             DCL 8             TODR,4-5,  4-7                    PIPE,13-22E             TOY,4-5,  4-7                   DCL$PATH Logical Name,8-1   4           Clockmeister, Ulysses T.          DCL1,8-15             See Time                        DCL10,8-7m5           Cluster                           DCL11,8-7f5             Disk,14-43                      DCL12,8-8 4           Cluster Load Balancing,15-14      DCL3,8-24           Cluster Terminology,15-12         DCL4,8-24           CMA$RTL.EXE,10-26                 DCL5,8-34           CMS,13-20                         DCL6,8-44           $cmsupr,12-4                      DCL7,8-5                      Index-2 n                                 Index        ;           DCL8,8-6                          DECwindows,11-1s2           DCL9,8-6                          DELETE:           DCPS,12-3                           Undelete,9-1<           DCX,13-26                         Descriptor,10-107           DDB,10-9                          Deutsch,1-2 >           Debugger                          Device Driver,10-8:             Signalling SS$_DEBUG,10-18      Device Drivers5           DEC-423,14-45                       C,10-23 B           DECalert,15-10                      Floating Point,10-23J           DECC$CRTL.EXE,10-26               DEVICE_NAMING system parameter5           DECconnect,14-45                     ,15-20o@           DECdns,15-6                       DFU,9-1,  9-4, 13-129           DECevent,5-32                     DIAGNOSE,5-32eJ           DECmigrate,7-3,  13-24, 13-26     DIGITAL Network Products Group5           DECnet,14-49                         ,14-33e@             Asynchronous,14-49              Digital Synergy,13-8F             DECNET_REGISTER,15-5            Digital Versatile Disk,9-90             MOP,15-6                        Disk9           DECprint,12-3                       Block,14-43o;           DECthreads,10-26                    Cluster,14-43 :           DECUS,1-8                           Sector,14-43  >             See User Group                  Disk Mirroring,9-2B             Hobbyist Licenses,2-7             See Volume Shadowing1           DECUServe,1-3                     Disks ;           DECUS Software Library,13-3         ATA,7-1,  9-5 D           DECW$CDPLAYER,7-1                   Bad Block Handling,9-38           DECW$IGNORE_WORKSTATION             CD-R,14-42?              Logical Name,11-7                CD-R/RW,9-7,  9-9r?           DECW1,11-1                          CD-Recordable,9-7g@           DECW10,11-8                         DVD+R/RW,9-7,  9-9@           DECW11,11-10                        DVD-R/RW,9-7,  9-9<           DECW12,11-11                        FAT Format,7-28           DECW13,11-11                        Floppy,7-2I           DECW14,11-12                        IDE,7-1,  9-5, 14-40, 14-43 ;           DECW15,11-14                        Jumpers,14-37t6           DECW16,11-15                        MSCP,9-3;           DECW17,11-15                        PC Format,7-2 E           DECW2,11-3                          SCSI,9-3,  9-11, 14-37,l6           DECW3,11-3                             14-438           DECW4,11-4                          SCSI-2,9-6<           DECW5,11-4                          Volume Set,9-77           DECW6,11-5                          Zip,14-42m           DECW9,11-8  J                                                                    Index-3                                   Index        9           Disk Shadowing,9-2                ECO kits,5-25l5           DJE Systems,13-8                  EFI,14-22 9           DNPG,14-33                        EIA-232,14-45 D           DNS,15-6                          ELSA GLoria Synergy,5-227           DOC1,3-1                          elvis,13-15 5           DOC10,3-6                         Encompasss<           DOC11,3-7                           See User GroupC           DOC12,3-13                          Hobbyist Licenses,2-7s=           DOC13,3-10                        Encompasserve,1-3rG           DOC14,3-12                        Encompass Software Library,o3           DOC2,3-1                             13-3a=           DOC4,3-6                          Endian-ness,10-18 D           DOC5,3-6                          Engineering Software,7-27           DOC6,3-5                          Ensoniq,7-2v3           DOCUMENT,10-17                    Enterex C           DQDRIVER,7-1,  9-5, 14-43           Hobbyist Licenses,2-7t6           Driver                            EPIC,14-218             Device,10-8                     $erapat,5-51E           DRVERR,14-40,  14-43              Ergonomic Solutions,15-10 ?           DSPP,2-8,  2-13                   Error analysis,5-32i5           DST,4-2,  4-12, 4-17, 10-23       ETAPE,7-3e:           DTSS,4-9                          Ethernet,14-49=             DTSS$CLERK,4-18                 Event Flags,11-10 4             Too Few Servers Detected,       EWS,11-3B                4-19                         EXE$GL_TICKLENGTH,4-10B           DTSS$CLERK,4-18                   EXE$GL_TIMEADJUST,4-10;           DTSS$INSTALL_TIMEZONE_RULE.COM    EXE$GL_TODR,4-4uD              ,4-17                          EXE$GQ_SAVED_HWCLOCK,4-6D           DTSS$NTP_PROVIDER.C,4-9           EXE$GQ_SYSTIME,4-4,  4-6;           DTSS$SET_TIMEZONE.EXE,4-14        EXE$GQ_TDF,4-14 ?           DTSS$UTC_STARTUP.COM,4-17         EXE$GQ_TODCBASE,4-4 ;           DVD+R,9-9,  13-9                  EXE$SETTIME,4-4 A           DVD+R/RW,9-7                      Executable Image,10-8 A           DVD+RW,13-9                       EXPECTED_VOTES systemi>           DVD-R,13-9                           parameter,15-16?           DVD-R/RW,9-7,  9-9                Explicitly Parallel,D           DVD-RW,13-9                          Instruction Computing6           ______________________________      See EPIC           E I           ______________________________    Extensible Firmware Interfacen  5           EBCDIC,7-3                          See EFI 
           ECOh             Search Engine,5-24                      Index-4 n  n                              Index        6           ______________________________    GnuPG,13-5B           F                                 GNU Privacy Guard,13-55           ______________________________    GNV,13-16H6           Facility Prefix,10-2              Google,1-34           Farmer, Ken,1-3                   GPG,13-56           FAT Disks,7-2                     Grace,13-96           FFT,13-11                         grep,13-145           FILE1,9-1                         GTK,13-11 6           FILE2,9-1                         gzip,13-25J           FILE3,9-2                         ______________________________-           FILE4,9-3                         HqJ           FILE5,9-4                         ______________________________9           FILE6,9-6                         H8571-A,14-48t9           FILE7,9-7,  9-9                   H8571-B,14-47t9           FILE8,9-11                        H8571-C,14-47o9           FILE9,9-11                        H8571-D,14-47H9           $filescan,9-3                     H8571-E,14-47 9           FILE tool,13-13                   H8571-J,14-47 9           FISH,13-3                         H8572-0,14-47 A           flex,13-14                        H8575-A,14-47,  14-48t9           Floating Point,10-6               H8575-B,14-47p9             Device Drivers,10-23            H8575-D,14-47o:           Floppy,7-2                        H8577-AA,14-474           FLORIAN,9-1                       Hardware@           $flush,9-2                          Serial Number,10-7C           Foreign Command,8-1               Helliesen, Gunnar,14-29 =           Fortran,10-7                      Hemker, Mark,13-9U8           Freeware,9-4,  10-4, 10-17        Heroix,13-17E             SETCLOCK,4-10                   Heuser-Hofmann, Eberhard, 6           ftso,13-26                           Dr.,9-88           ftsv,13-26                        Hobbyist,2-80           ______________________________    HourJ           G                                   Off By One,4-2,  4-17, 10-237           ______________________________    HP-UX,10-18 :           GB,14-43                          ht://Dig,13-126           $getdvi,10-2                      HTML,10-17<           $getjpi,10-2                      HTTP_SERVER,13-3J           $getsyi,10-2                      ______________________________-           Global Maintech,13-17             I J           gmake,13-12                       ______________________________=           GMT,4-1                           I64,14-21,  14-22 5           GNM,10-17                         IA-32,2-9i           GNU,13-16   J                                                                    Index-5    l                              Index        J           IA-64 Architecture,14-21,         ______________________________-              14-22                          JtJ           IARGCOUNT,10-7                    ______________________________6           IDE,7-1,  9-5                     J2EE,13-186           Identifier                        Java,13-18<             Subsystem,10-8                  JBC$COMMAND,5-253           Image                             JCL,7-3 5             Executable,10-8                 JDK,13-18e:             Loadable,10-8                   JetDirect,15-2=             Protected,10-8                  Jones, David,13-3t5             Shareable,10-8                  Jouk,13-3s:             System,10-8                     Julian Day,4-29             UWSS,10-8                       Jumpers,14-37 J           IMAGELIB.OLB,10-19                ______________________________-           ImageMagick,13-6                  K J           IMPLVER,14-25                     ______________________________4           InfoServer,9-8                    KB,14-437             Scribe,9-8                      Kermit,13-3i4           INFO-VAX,1-3,  1-4, 1-7           ki,13-17=           INITIALIZE,5-33                   KI Products,13-17hD           INSTALL,10-8                      KVM switch,14-34,  14-35J           Interex                           ______________________________-             See User Group                  L J                                             ______________________________@           INTRO1,1-2                        LAVC$START_BUS,15-14?           INTRO2,1-2                        LAVC$STOP_BUS,15-14 I           INTRO3,1-3                        LCD flat-panel display,14-35, 4           INTRO4,1-4                           14-378           INTRO5,1-5                        Levitte,13-85           INTRO6,1-8                        lex,13-14oF           INTRO7,1-3                        lib$find_image_symbol,10-8=           INTRO8,1-9                        lib$free_ef,11-10m<           IO$_DIAGNOSE,7-1                  lib$get_ef,11-10@           IOMega,14-42                      lib$get_foreign,10-4@           IRC Client                        lib$set_logical,10-5?             Mozilla,13-17                   lib$sfree1_dd,10-10s>           IRIG,4-9                          lib$sget1_dd,10-10<           ISO-9960,9-8                      LIB$SIGNAL,10-18:           Itanium,14-21,  14-22             lib$spawn,10-9  A           Itanium Processor Family          lib$table_parse,10-16 <             See Itanium                     lib$tparse,10-16A                                             lib$trim_filespec,9-3a9                                             LIB.L32,10-16V                      Index-6 d  s                              Index        A           LIB.L64,10-16                     Logical Name (cont'd)eJ           LIB.R64,10-16                       LISP$DAYLIGHT_SAVING_TIME_P,5           LIB.REQ,10-16                          4-15AA           License,10-7,  12-5                 LISP$TIME_ZONE,4-15 H           License Unit Requirements           LMF$DISPLAY_OPCOM_MESSAGE,5              Table,2-7, 5-42                     12-5d@           Licensing,10-7                      MAIL$TIMEZONE,4-15A           Licensing Programs                  NOTES$TIMEZONE,4-15 ;             Campus Software License           SYS$DISK,10-5 ;                Grant,2-8                      SYS$LOGIN,8-7eB             Educational,2-8                   SYS$LOGIN_DEVICE,8-7=             Hobbyist,2-8                      SYS$SCRATCH,8-7nJ           Liebert,13-10                       SYS$TIMEZONE_DAYLIGHT_SAVING6           linda,13-9                             ,4-15H           Linker                              SYS$TIMEZONE_DIFFERENTIAL,5             COMMON,10-6                          4-15 D             PSECT_ATTR,10-6                   SYS$TIMEZONE_NAME,4-15H             SYMBOL_VECTOR,10-5                UCX$NFS_TIME_DIFFERENTIAL,5             SYS$BASE_IMAGE,10-5                  4-15.:             SYS.STB,10-5                      UCX$TDF,4-154             /SYSEXE,10-5                    lpd,15-14           LINKER,10-19                      lpr,15-16           LISP$DAYLIGHT_SAVING_TIME_P       LRA0:,12-3;              Logical Name,4-15              LURT,2-7,  5-42 5           LISP$TIME_ZONE Logical Name,      LVD,14-43e7              4-15                           164LX,14-18 5           Little-Endian,10-18               Lynx,13-4 J           LK201,14-34                       ______________________________-           LK401,14-34                       MyJ           LK461,14-35                       ______________________________E           LK463,14-35,  14-48               MadGoat,5-32,  7-2, 13-2,:4           LK46W,14-35                          13-13G           LK471,14-35                       MAIL$TIMEZONE Logical Name, 3           LMF,2-8,  10-7, 11-7, 12-5           4-15r6           LMF$DISPLAY_OPCOM_MESSAGE         MAIL10,6-35              Logical Name,12-5              MAIL7,6-1 5           Loadable Image,10-8               MAIL9,6-1i:           LOAD_PWD_POLICY system            Mail Count,6-1:              parameter,5-44                 Majordomo,13-9>           LocalFile,15-6                    make,13-12,  13-145           Logical Name                      man,13-14 2             DCL$PATH,8-1                    MAXBUFC             DECW$IGNORE_WORKSTATION,          system parameter,9-11                 11-7M  J                                                                    Index-7                                   Index        8           MAXPROCESSCNT system parameter    MGMT45,15-227              ,5-8                           MGMT46,5-37OG           MB,14-43                          MGMT47,15-12,  15-14, 15-15 7           Menufinder,13-9                   MGMT48,5-37 7           MESSAGE Compiler,10-17            MGMT49,5-37h5           MGBOOK Bookreader,3-1             MGMT5,5-5 7           MGMT1,5-1                         MGMT50,5-38d7           MGMT10,15-16                      MGMT51,5-38 7           MGMT11,5-10                       MGMT52,5-40s7           MGMT12,5-50                       MGMT53,5-40S8           MGMT13,15-20                      MGMT54,15-247           MGMT14,15-9                       MGMT56,5-40n7           MGMT15,5-10                       MGMT57,5-4157           MGMT16,5-12                       MGMT58,15-6t7           MGMT17,5-17                       MGMT59,5-41o6           MGMT18,5-18                       MGMT6,15-27           MGMT19,5-19                       MGMT60,5-43p8           MGMT2,5-2                         MGMT61,15-187           MGMT20,5-48                       MGMT62,5-43m8           MGMT21,5-20                       MGMT63,15-257           MGMT23,5-21                       MGMT64,5-47l5           MGMT24,5-21                       MGMT9,5-8 5           MGMT25,5-24                       MGPCX,7-2t@           MGMT26,15-21                      microfortnight,14-445           MGMT27,5-25                       MIME,13-9i:           MGMT28,15-3                       Minicopy,15-25;           MGMT3,5-3                         Minimerge,15-25r9           MGMT30,5-26                       Mirroring,9-2 B           MGMT31,5-27                         See Volume Shadowing7           MGMT32,5-29                       MISC12,12-3 7           MGMT33,5-29                       MISC13,12-3I7           MGMT34,5-32                       MISC14,12-4 8           MGMT35,5-45                       MISC15,15-107           MGMT36,15-4                       MISC17,15-9e8           MGMT37,5-32                       MISC19,15-116           MGMT38,5-33                       MISC2,12-17           MGMT39,5-33                       MISC20,12-5s6           MGMT4,5-4                         MISC6,15-56           MGMT40,5-34                       MISC7,15-66           MGMT41,5-34                       MISC9,15-48           MGMT42,15-18                      Mlucas,13-11D           MGMT43,5-36                       MMJ,14-45,  14-46, 14-475           MGMT44,15-22                      mmk,13-12i                      Index-8 e                                 Index        7           Modified Modular Jack,14-45       NOTSET,4-18 ;           MODPARAMS.DAT,15-23,  15-25       17-Nov-1858,4-2 3           Montagar,13-1                     NTP,4-9oJ           MOP,15-6                          ______________________________-           Mosaic,13-4                       OPJ           Mozilla,13-4                      ______________________________5             Composer,13-17                  ODBC,9-11p5             IRC Client,13-17                ODS-2,9-8 5             Netnews Client,13-17            ODS-5,9-8 F           MPEG,7-2                          Ohio State University,13-37           mpi,13-9                          OPA0:,14-11 ;           MSCP_LOAD system parameter,       OpenVMS.Org,1-3 @              15-13                          OPENVMS-HOBBYIST,2-87           MTAACP,5-33                       Opteron,2-9t4           MTEXCH,7-3                        OSU,13-3  8           Multia,14-16                      Outbuildings6           Multinet,15-3                       See TimeJ           MySQL,13-12                       ______________________________-           ______________________________    P J           N                                 ______________________________<           ______________________________    Pager Plus,15-108           NCSA,13-4                         Paging,15-10F           NET$DISABLE_DTSS,4-19             PAK,2-8,  10-7, 11-7, 12-5>           NET1,15-1                         PAKGEN,10-7,  12-5@           NET2,15-1                         PALcode,14-4,  14-116           NetBSD,14-24                      $parse,9-35           Netnews Client                    Patch,7-4 @             Mozilla,13-17                     Search Engine,5-24;           Netscape Navigator,3-13,          Patch kits,5-25T4              13-18                          PB,14-439           Networking Dynamics,5-32,         PBXGB-AA,5-23 9              13-11, 15-10                   PBXGB-CA,5-23i9           New Mail Count,6-1                PBXGD-AE,5-23N9           NIC,15-2                          PBXGK-BB,5-22V:           NISCS_LOAD_PEA0 system            PC7XS-CA,14-356              parameter,15-23                PCDISK,7-28           NIST,4-8                          PC Disks,7-25           NOCLI,8-2                         PCSI,5-36 3           NODECW,11-12                      PCX,7-2E6           NODEVICE,11-12                    Peek,13-117           NONEWMAIL,6-1                     Pentium,2-9 >           NOTES$TIMEZONE Logical Name,      Perl,13-10,  13-234              4-15                           PGP,13-4  J                                                                    Index-9                                   Index        8           PHYSICALPAGES system parameter    PROG22,10-188              ,5-10                          PROG23,10-196           PHYSICAL_MEMORY system            PROG3,10-46              parameter,5-10                 PROG4,10-56           PINE,13-9                         PROG5,10-56           PIPE,13-22                        PROG7,10-56           Plextor,14-42                     PROG8,10-66           pm,11-9                           PROG9,10-6>           PMDF,15-10                        ProGIS,7-2,  13-16@           Postscript,10-17                  Protected Image,10-8;           POV-Ray,13-9                      PSECT_ATTR,10-6o8           PowerStorm 300,5-23               $putmsg,10-44           PowerStorm 350,5-23               pvm,13-95           PowerStorm 3D10T,5-22             PWIP,15-5b8           PowerStorm 3D30,5-23              Python,13-11J           PowerStorm 4D20,5-23              ______________________________-           PPP,15-4                          Q J           Pretty Good Privacy,13-4          ______________________________=           Printing                          $qio,10-9,  11-10 =             DCPS,12-3                       QMAN$JOURNAL,5-25 :             lpr,15-1                        QuickSpecs,3-48             Parallel Port,12-3              QUORUM,15-17J             telnet,15-1                     ______________________________-           Process Software,13-2,  15-3,     R J              15-10                          ______________________________<           Product Authorization Key,        Radeon 7500,5-239              10-7, 11-7, 12-5               RamPage,15-10m4           Product Registration,10-2         RAS,15-47           PRODUCT SHOW PRODUCT,5-36         Raxco,13-11d5           PROG1,10-2                        rcs,13-14 7           PROG10,10-7                       Rlogin,5-51n4           PROG11,10-8                       RMS,9-11>           PROG12,10-9                       RMS Journaling,9-29           PROG13,10-9                       robomon,13-17   G           PROG14,10-11                      Royal Greenwich Observatory   6           PROG15,10-13                        See Time8           PROG16,10-13                      RS-232,14-458           PROG17,10-14                      RZDISK,14-41             PROG18,10-15           PROG19,10-17           PROG2,10-4           PROG20,10-17           PROG21,10-17                      Index-10a i  M                              Index        @           ______________________________    smg$create_menu,10-3E           S                                 Smithsonian Astrophysical >           ______________________________       Observatory,4-28           SAIC,1-4,  13-1, 13-3             $sndjbc,10-95           Saiga Systems,5-32                SOAP,13-8 3           SAMBA,13-10                       SOC,3-4r6           SAO,4-2                           SOFT1,13-18           SCACP,15-15                       SOFT10,13-228           Scaliger                          SOFT12,13-238             Julius Caesar,4-3               SOFT13,13-248           Scaliger, Joseph,4-3              SOFT14,13-257           Scribe                            SOFT2,13-14c7             InfoServer,9-8                  SOFT3,13-17p7           SCS,15-11,  15-12                 SOFT4,13-18g7           SCSI,9-11,  14-37                 SOFT5,10-19 7           SCSI-2,9-6                        SOFT6,13-19 7           SCSI_INFO,14-41                   SOFT7,13-19r?           SCSNODE system parameter,5-8,     SOFT9,13-20,  13-21t5              5-9, 15-25                     Spy,13-11r9           SCSSYSTEMID system parameter,     Spyglass,13-4_;              5-9                            SRI,1-3,  13-26 5           SDL,10-17                         SRM,14-11s:           SDML,10-17                          Acronym,14-4F           Search Engine,13-12                 System Reference Manual,5             ECO,5-24                             14-4u;             Patch,5-24                      SS$_DEBUG,10-1879           Sector                            SS$_NOCLI,8-2 4             Disk,14-43                      SSH,13-37           Secure Shell,13-3                   FISH,13-3a/           Serial Number,10-7                SSLp9           SETCLOCK,4-10                       SSLeay,13-3 7           SET PREFERRED_PATH command,       SSLeay,13-3 <              15-15                          Stark, Tim,13-26=           $SETTIM,4-18                      STARLET.L32,10-15I=           SET TIME,4-18                     STARLET.L64,10-16i=           SETTIME system parameter,4-4,     STARLET.R64,10-16 E              4-5                            STARLET.REQ,10-15,  10-16 3           Shadowing,9-2                     Storagee;           Shareable Image,10-8                ATA,7-1,  9-5e8           SHOW MEMORY/CACHE command,          CD-R,14-42?              9-12                             CD-R/RW,9-7,  9-9 ?           SIMH,13-26                          CD-Recordable,9-7 A           SMB,13-10                           Disk Settings,14-37u@                                               DVD+R/RW,9-7,  9-9@                                               DVD-R/RW,9-7,  9-9  J                                                                   Index-11    s                              Index        ;           Storage (cont'd)                  sys$putmsg,10-4 @             FAT Format,7-2                  sys$qio,10-9,  11-10H             Floppy,7-2                      SYS$SCRATCH Logical Name,8-7<             Free Space,12-3                 sys$setddir,10-5;             IDE,7-1,  9-5, 14-40, 14-43     SYS$SETTIM,4-18 ;             PC Format,7-2                   sys$sndjbc,10-9 I             Remaining on Tape,12-3          SYS$STARTUP:DTSS$STARTUP.COM, 3             SCSI,9-11,  14-37, 14-43           4-19oH             SCSI-2,9-6                      SYS$TIMEZONE.DAT,4-14,  4-16H             Volume Set,9-7                  SYS$TIMEZONE_DAYLIGHT_SAVING@           Subsystem Identifier,10-8            Logical Name,4-15E           Supervisor,13-11                  SYS$TIMEZONE_DIFFERENTIALe@           Supnik, Bob,13-26                    Logical Name,4-15E           Swizzling,14-26                   SYS$TIMEZONE_NAME Logical 8           164SX,14-18                          Name,4-15E           SYLOGICALS.COM,4-19,  8-3,        SYS$TIMEZONE_SRC.DAT,4-16 8              11-7                           SYS.STB,10-59           SYLOGICALS.TEMPLATE,4-19,         SYSBOOT,15-20d7              5-31, 5-51, 6-1, 8-3, 15-23    SYSLOG,13-9 7           Symbol Substitution               System DiskhA             PIPE,13-22                        VAXstation 3100,9-4s=           SYMBOL_VECTOR,10-5                System Image,10-8 =           synch-on-green,14-35              System parameters =           SYS$BASE_IMAGE,10-5                 ALLOCLASS,15-25 A           SYS$BASE_IMAGE.EXE,4-14             DEVICE_NAMING,15-20 B           sys$cmsupr,12-4                     EXPECTED_VOTES,15-16B           sys$creprc,10-9                     LOAD_PWD_POLICY,5-449           SYS$DISK Logical Name,10-5          MAXBUF,9-11d?           SYS$DQDRIVER,7-1,  9-5, 14-43       MAXPROCESSCNT,5-8v=           SYS$EXAMPLES:DAYLIGHT_              MSCP_LOAD,15-13iC              SAVINGS.COM,4-12                 NISCS_LOAD_PEA0,15-23 @           sys$filescan,9-3                    PHYSICALPAGES,5-10B           sys$flush,9-2                       PHYSICAL_MEMORY,5-10F           sys$getdvi,10-2                     SCSNODE,5-8,  5-9, 15-25=           sys$getjpi,10-2                     SCSSYSTEMID,5-9 ?           sys$getsyi,10-2                     SETTIME,4-4,  4-5 F           SYS$LIB_C.TLB,10-23                 TIMEPROMPTWAIT,4-4,  4-5>           SYS$LOGIN Logical Name,8-7          TMSCP_LOAD,15-13>           SYS$LOGIN_DEVICE Logical Name       UAFALTERNATE,5-7>              ,8-7                             VAXCLUSTER,15-239           sys$parse,9-3                       VOTES,15-16 G           SYS$PIPE,13-22                      WINDOW_SYSTEM,5-6,  11-7,06                                                  11-12@                                               WRITESYSPARAMS,5-6                      Index-120 l  3                              Index        9           Systems and Options Catalog,      Time (cont'd)_9              3-4                              NOTSET,4-18 5           System Service,10-8                 NTP,4-9,I           ______________________________      Off By One Hour,4-2,  4-17,,6           T                                      10-23@           ______________________________      Prime Meridian,4-2;           TAP,15-10                           SETCLOCK,4-10 C           TAPECOPY,7-3                        SET TIME Command,4-18_6           Tapes                               TDF,4-13=             Compaction,12-4                   TIMENOTSET,4-18 G             Compression,12-4                  Time service enabled,4-18 <             Conversion,7-3                    TODR,4-5,  4-7;             EBCDIC,7-3                        TOY,4-5,  4-7 5             Free Space,12-3                   UT0,4-1 5           tar,13-14                           UT1,4-1n5           Target Systems,15-10                UT2,4-1eH           TB,14-43                            UTC,4-1,  4-2, 4-13, 4-17,6           tcgmsg,13-9                            10-236           TCL,13-12                           ZIC,4-175           TCOPY,7-3                         TIME1,4-2u7           TDF,4-13                          TIME10,4-18 6           TECsys,13-17                      TIME11,4-46           telnet,15-1                       TIME12,4-17           Telnet,5-51                       TIME13,4-1745           Telocator Alphanumeric            TIME2,4-7 6              Protocol,15-10                 TIME3,4-106           Terminal Server Manager,13-12     TIME4,4-136           Text,10-17                        TIME5,4-165           TIE,13-24                         TIME6,4-816           Time                              TIME7,4-116             ACTS,4-8                        TIME8,4-105             Clock Drift,4-10                TIME9,4-7 ;             Dial-up,4-8                     TIMENOTSET,4-181A             DST,4-2,  4-17, 10-23           TIMEPROMPTWAUT system-A             DTSS,4-9                           parameter,4-4, 4-5 H             Error modifying time,4-18       TMSCP_LOAD system parameter,4             GMT,4-1                            15-13:             Greenwich,4-1                   TODR,4-5,  4-7I             IPL,4-10                        Too Few Servers Detected,4-19 7             IRIG,4-9                        Touch,13-12 ?             Julian,4-2                      TOY Clock,4-5,  4-7,<             Julian Calendar,4-3             TPAMAC.REQ,10-16             Julian Date,4-2              Julian Day,4-2             NIST,4-8  J                                                                   Index-13 ,  2                              Index        J           Trailing Edge,13-26               ______________________________-           Tripp-Lite,13-9                   V J           TS10,13-26                        ______________________________=           TSM,13-12                         Vajhj, Arne,13-2p6           TT2$M_DISCONNECT,5-52             VAKSAT,7-2H           TTY_DEFCHAR2,5-52                 VAXCLUSTER system parameter,4           ______________________________       15-23=           U                                 VAXCRTL.EXE,10-26C>           ______________________________    VAX Emulator,13-26;           U.S. Design,9-9                   VAXstation 3100 9           UAFALTERNATE system parameter       Console,9-4 F              ,5-7                             System Disk Capacity,9-4:           UCB,10-9                          VCC_FLAGS,9-12  F           UCX$NFS_TIME_DIFFERENTIAL         Very Long Instruction Word  6              Logical Name,4-15                See VLIW6           UCX$TDF Logical Name,4-15         VEST,13-244           undelete,9-1                      vi,13-156           UPS,13-9,  13-10                  vile,13-155           UPShot,13-10                      vim,13-15 5           User Group                        VIOC,9-12_A             DECUS,1-9                       Virtual Terminal,5-51 6             Encompass,1-8,  1-9             VLIW,14-215             Interex,1-9                     VMove,7-2 4           UT0,4-1                           VMS1,2-15           UT1,4-1                           VMS10,2-8 5           UT2,4-1                           VMS11,2-9 5           UTC,4-1,  4-13                    VMS12,2-9-6           UTC$CONFIGURE_TDF.COM,4-13        VMS13,2-106           UTC$TIMEZONE_SETUP.COM,4-13       VMS14,2-116           UTC$TIME_SETUP.COM,4-13,          VMS15,2-126              4-14, 4-16, 4-18               VMS16,2-136           UTIL1,7-1                         VMS17,2-144           UTIL2,7-2                         VMS2,2-24           UTIL3,7-2                         VMS3,2-34           UTIL4,7-3                         VMS4,2-34           UTIL5,7-3                         VMS5,2-44           UTIL6,7-4                         VMS7,2-4:           uudecode,13-2,  13-14             VMS73_XFC,9-124           uuencode,13-2,  13-14             VMS8,2-6:           UWSS,10-8                         VMS9,2-7,  2-8:                                             VMSINSTAL,5-36?                                             _VMS_V6_SOURCE,4-13 :                                             Volume Set,9-7                      Index-14E n  s                              Index        A           Volume Shadowing,15-24            WRITESYSPARAMS systeme<             Allocation Class,15-24             parameter,5-64             Full Copy,15-26                 WWW,13-4J             Full Merge,15-27                ______________________________-             Minicopy,15-25                  XiJ             Minimerge,15-25                 ______________________________5           VOTES system parameter,15-16      XDR,10-18-4           VR260,14-34                       XFC,9-12?           VR290,14-34                       XLNperformance,5-32 ;           VRC16,14-35                       XLNsystems,5-32F=           VRC21,14-35                       XML,10-18,  13-11 6           VSXXX,14-34                       XOFF,14-485           VXT,11-3                          XON,14-48-4           ______________________________    xpm,11-9?           W                                 XtAppAddInput,11-10T3           ______________________________    xv,11-9 :           Web Browser                       X Windows,11-1C             Compaq Secure Web Browser,      X Windows Terminal,11-3sJ                13-17                        ______________________________-             CSWB,13-4,  13-17               YrJ             Lynx,13-4                       ______________________________4             Mosaic,13-4                     Y2K,5-336             Mozilla,13-4,  13-17            yacc,13-147             Netscape,13-4                   Yamhill,2-9P:             Netscape Navigator,3-13,        Year 2000,5-33J                13-18                        ______________________________-           Web server                        Z J             Apache,13-8                     ______________________________3             OSU,13-8                        ZAP,7-4 4             Purveyor,13-8                   ZIC,4-17@             WASD,13-8                       Zimmerman, Phil,13-45           Webserver,13-3                    zip,13-2577           Western Kentucky University,      ZMODEM,13-3,                13-2            WINDOW_SYSTEM "             system parameter,11-7,                11-12(           WINDOW_SYSTEM system parameter              ,5-6            WIZARD.ZIP,3-13,           WKU,13-2%           Write History Logging,15-253  J                                                                   Index-15  N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faq N  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.comI   ------------------------------   Date: 3 Jul 2003 10:57:36 -070021 From: keithparris_NOSPAM@yahoo.com (Keith Parris),T Subject: Re: OpenVMS Pearl - OpenVMS V8.0, first release on Itanium, ships  today!!!= Message-ID: <cf15391e.0307030957.2c61fde2@posting.google.com>O  ` "David J. Dachtera" <djesys.nospam@fsi.net> wrote in message news:<3F00F7F9.3B43DF13@fsi.net>...3 > Any chance this might be available for hobbyists?s > ! > Low-cost (less than $50US) CDs?   C Not quite at the price level you requested, but close: How about an A Early Adopter Kit on CD for US$75?  (Stay tuned for a part number  soon.)   ------------------------------   Date: 3 Jul 2003 06:43:17 -0700 1 From: susan_skonetski@hotmail.com (Sue Skonetski) : Subject: OpenVMS Technical Journal 2nd issue now available= Message-ID: <857e9e41.0307030543.4f0ce2b1@posting.google.com>    Dear Newsgroup,o  E It is my pleasure to announce the availability of the second issue of E the OpenVMS Technical Journal (VTJ).  The first issue of VTJ receivedrF over 20,000 views and 1362 automatic subscriptions. We have also addedB  a new regular feature "Best of the HP Customer Support Center" to. cover questions regularly received by the CSC.  D For this issue please visit: :<http://www.hp.com/go/openvms/journal>  C All articles are available in HTML and PDF and you may download ZIP  files of the entire journal.  F As with any project, VTJ is only possible because of an excellent team@ and excellent team work.  The core team for this project is Joan@ Winslow, Steve Hoffman and of course Warren Sander our excellentF OpenVMS Web Master.  Special thanks to Warren and the writing team forE the enormous amount of work that they did for  this issue.  As always  your feedback is very welcome.  @ This issue of VTJ is excellent with  over 150 pages of technicalA information written by authors who work with VMS every day.  This $ issue contains the following topics:  1 A Survey of Cluster Technologies - by  Ken Moreau D Local Area Network Cluster Interconnect Monitoring - by Keith Parris1 Internet Technologies for OpenVMS - by Ken Moreau = Configuring TCP/IP for High Availability - by Matt Muggeridge9D DCPI for OpenVMS a  Technical Introduction to a "System Microscope"  by Anders Johanssonl@ RMS Performance: Duplicate key chains - by  Hein van den Heuvel ? A Customer Case Study of Oracle Rdb Database Consolidation - by  Vischio Giovanni, and customers ? Best of the HP Customer Support Center - by Mark (Jilly) Jilsonn1 Best of Ask the Wizard -  by Steve (Hoff) HoffmaneB Server-Agnostic Perl/DCL CGI Programming with WASD and OSU by Dick# Munroe, Cottage Software Works, Inc   
 Warm Regards,I Sue    ------------------------------  % Date: Thu, 03 Jul 2003 17:42:40 +0200 $ From: Michael Unger <unger@decus.de>> Subject: Re: OpenVMS Technical Journal 2nd issue now available4 Message-ID: <be1lrr$9v1m$2@ID-152801.news.dfncis.de>  * On 03-Jul-2003 15:43, Sue Skonetski wrote:   > Dear Newsgroup,  > G > It is my pleasure to announce the availability of the second issue of G > the OpenVMS Technical Journal (VTJ).  The first issue of VTJ received H > over 20,000 views and 1362 automatic subscriptions. We have also addedD >  a new regular feature "Best of the HP Customer Support Center" to0 > cover questions regularly received by the CSC. > F > For this issue please visit: :<http://www.hp.com/go/openvms/journal> > E > All articles are available in HTML and PDF and you may download ZIP, > files of the entire journal. >  > [...]   < ... and the entire document as a single PDF file too. Great!   Michael-   --    @ Please do *not* send "Security Patch Notifications" or "SecurityA Updates"; this system isn't running a Micro$oft operating system. = And don't annoy me <mailto:postmaster@[127.0.0.1]> please ;-)8   ------------------------------   Date: 3 Jul 2003 10:39:24 -000044 From: Doc.Cypher <Use-Author-Address-Header@[127.1]> Subject: Re: Running VMS off CDi6 Message-ID: <20030703103924.25295.qmail@nym.alias.net>  ; On Wed, 02 Jul 2003, Dean Woodward <deanw@rdrop.com> wrote:A >David J. Dachtera wrote: J >> If you've got lots of RAM, I suppose you could hack up a /STARTUP proc.D >> that copies the distribution up to a RAMdisk before assigning keyE >> logicals and such and then proceeding, ... but then there goes the  >> write-lock. >-J >The advantage here lies in what happens when you power-cycle the box. If E >it booted from read-only media and copied stuff to RAMdisk, all the   >cracker's efforts go *poof*...  > E >If you run purely from RO media, then the system is invulnerable to  C >having files loaded/changed/replaced. Exploits that tweak running  H >software are still possible, which leads me to a mildly amusing vision G >of script kiddies trying to crack a VMS box that way. Not saying it's v0 >impossible, but I bet it'd be damn frustrating.  8 You don't read the alt.privacy newsgroup do you Dean? :)K [Where boot from RO media, encrypted filesystems, etc. are regular topics.]   N Thanks for clearly explaining the advantages of this sort of setup.  CompaniesH lie SuSE offer their Linux-based firewall that runs off CD, a VMS off CDM distribution that when first booted allowed you to write local config data to 1 a floppy would be the ultimate turnkey secure OS.   G On a slightly related note, does anyone know of a package (available to K Hobbyists) which gives similar functionality to the *ix package "tripwire"?_     Doc. -- _K OpenVMS.         Eight out of ten hackers prefer *other* operating systems.    ------------------------------  $ Date: Thu, 3 Jul 2003 10:13:03 -0400, From: "Island" <dbturner@nospamislandco.com> Subject: Re: Running VMS off CDa/ Message-ID: <vg8ejec0vtmkea@news.supernews.com>   * You could always use a zip drive/jaz drive  $ You can write lock those can't you ?   They are pretty quick too !    DT   ------------------------------   Date: 3 Jul 2003 06:53:01 -0700 1 From: susan_skonetski@hotmail.com (Sue Skonetski)d. Subject: Updated Host-Based MiniMerge Schedule= Message-ID: <857e9e41.0307030553.43dd5f89@posting.google.com>i   Dear Newsgroup,   E Please note this updated information.  This looks much better in richB txt or word.  
 Warm Regards,_ Sue_  < ____________________________________________________________+ Host-Based MiniMerge Schedule Now Available_  C The OpenVMS Engineering and Business Management group would like to F announce the schedule for Host-Based MiniMerge capability.  As most ofB you know, the teams have been spending virtually all of their timeD over the past 3 months doing design, "proof of concept" and scheduleF development for this important feature.  We are now ready to make this4 information available to the OpenVMS user community.  F Overview  The purpose of the Host-Based MiniMerge feature is to allow= a "minimum" MERGE of only shadow set changes (rather than the1D currently-required "full" MERGE) when a member of an OpenVMS clusterB is removed and re-introduced into a cluster.  A similar capability< exists today for CI-based storage, and this new "host-based"E implementation will allow a MiniMerge to occur on any type of storage = that is utilized in a Host-Based Volume Shadowing shadow set.   ? Technical Description - This implementation utilizes the "write A bitmap" technology used for MiniCopy functionality today, to keep < track of shadow set data changes while a shadowset member isF temporarily removed from a shadowset.  With MiniCopy, when a shadowsetE member is brought back in, Shadowing is able to copy only the changedoE areas of the disk, thus resulting in a much faster restoration of the0F shadow set member into the shadowset.  By using similar "write bitmap"D technology to track the changes being made by each node in a cluster@ to the members of a shadowset, then at the time a node fails andF leaves the cluster, it is possible to identify those specific areas onC the shadowset that were being written to by the node at the time it F failed.  As such, where the failure might have resulted in data endingE up different on different members of the shadowset, Shadowing can now E merge just those areas which were in the process of being modified at @ the time the node failed (in a MiniMerge operation), rather thanB having to scan the entire disk looking for potential discrepancies9 caused by the node's failure (in a Full Merge operation).1  D Schedule/Version Summary - Below is a schedule with major milestonesA for this engineering effort.  The important date is that customer E availability of this feature will be on 25-March-2004 for the OpenVMS A V7.3-1 customer base.  Support for OpenVMS V7.3-2 will be shortly  thereafter.E  > We will do periodic updates to the field of the status of thisC engineering effort, and also solicit candidates for beta testing of A this feature, which is scheduled to occur at the end of 2003.  If : there are any questions, please contact either Jim JanetosF (Engineering Manager, jim.janetos@hp.com), or Andy Schneider (Business  Manager, andy.schneider@hp.com).  , Host-Based MiniMerge Schedule 					  6/30/03   Task Name	Start	Completion! HBMM Features (code and debug) 		 8 Minimerge from a bitmap (essentials)	6/20/2003	8/15/2003 Bitmap Reset 	6/19/2003	9/25/03   Merge Priority	6/24/2003	9/25/03' Master Bitmap Policy	6/19/2003	10/01/03F5 HBMM code and debug phase complete 	06/17/03	10/20/03 0 Performance characterization	06/17/2003	10/09/03$ User documentation 	7/14/03	11/20/034 Internal testing and Qualification	10/10/03	12/29/03& External Field Test 	12/31/03 	3/24/04. V7.3-1 Based Production Kit available		3/25/04   ------------------------------  + Date: Thu, 03 Jul 2003 11:00:29 +0200 (MET) 9 From: Phillip Helbig <HELBPHI@sysdev.deutsche-boerse.com> O Subject: Re: VAX support (was: Re: OpenVMS Technical Seminar Highlights (some)) ; Message-ID: <01KXTINLFCLEAPKEWT@sysdev.deutsche-boerse.com>   H > There are many other packages that didn't get rescued and are still on > VAX only.    Do you have a list?   D Perhaps HP should port this list to Itanium in order to attract the E customers which are still on VAX only because of software lacking on   ALPHA.   ------------------------------   Date: 3 Jul 2003 05:14:21 -0500L- From: Kilgallen@SpamCop.net (Larry Kilgallen)0O Subject: Re: VAX support (was: Re: OpenVMS Technical Seminar Highlights (some))03 Message-ID: <rGjo8XFLo3Cv@eisner.encompasserve.org>L  w In article <01KXTINLFCLEAPKEWT@sysdev.deutsche-boerse.com>, Phillip Helbig <HELBPHI@sysdev.deutsche-boerse.com> writes: I >> There are many other packages that didn't get rescued and are still onF
 >> VAX only.   >  > Do you have a list?-   For languages:   VAX Scan Dibol  LISP OPS5 RPG1  F > Perhaps HP should port this list to Itanium in order to attract the G > customers which are still on VAX only because of software lacking on   > ALPHA.  3 Third party packages are probably a larger problem.    ------------------------------  % Date: Thu, 03 Jul 2003 08:52:16 -0400A* From: "Stanley F. Quayle" <stan@stanq.com>O Subject: Re: VAX support (was: Re: OpenVMS Technical Seminar Highlights (some)) . Message-ID: <3F03EEC0.16088.5026FFD@localhost>  - On 3 Jul 2003 at 5:14, Larry Kilgallen wrote:GK > >> There are many other packages that didn't get rescued and are still on  > >> VAX only. e > >  > > Do you have a list?  >  > For languages: > 
 > VAX Scan > Dibol0 > LISP > OPS5 > RPG0  ? What about PL/I?  Owned by someone else now, does that "count"?   1 There is an Alpha Dibol compiler, not sold by HP.   ' And SRI makes an Alpha version of SCAN. 
 --Stan Quayle  Quayle Consulting Inc.  
 ----------C Stanley F. Quayle, P.E. N8SQ  +1 614-868-1363  Fax: +1 614 868-167151 8572 North Spring Ct. NW, Pickerington, OH  43147 = Preferred address:  stan@stanq.com       http://www.stanq.com7   ------------------------------  $ Date: Thu, 3 Jul 2003 06:16:03 -0700# From: "Tom Linden" <tom@kednos.com>TO Subject: RE: VAX support (was: Re: OpenVMS Technical Seminar Highlights (some)) 9 Message-ID: <CIEJLCMNHNNDLLOOGNJIAEFOHIAA.tom@kednos.com>   7 PL/I has been on Alpha all along, fully supported.  see  www.kednos.com   >-----Original Message----- 0 >From: Stanley F. Quayle [mailto:stan@stanq.com]& >Sent: Thursday, July 03, 2003 5:52 AM >To: Info-VAX@Mvb.Saic.ComH >Subject: Re: VAX support (was: Re: OpenVMS Technical Seminar Highlights >(some)) >  > . >On 3 Jul 2003 at 5:14, Larry Kilgallen wrote:L >> >> There are many other packages that didn't get rescued and are still on >> >> VAX only.  >> > >> > Do you have a list? >> >> For languages:  >> >> VAX Scani >> Dibol >> LISP  >> OPS51 >> RPG > @ >What about PL/I?  Owned by someone else now, does that "count"? > 2 >There is an Alpha Dibol compiler, not sold by HP. > ( >And SRI makes an Alpha version of SCAN. >--Stan Quayle >Quayle Consulting Inc.- >  >----------TD >Stanley F. Quayle, P.E. N8SQ  +1 614-868-1363  Fax: +1 614 868-16712 >8572 North Spring Ct. NW, Pickerington, OH  43147> >Preferred address:  stan@stanq.com       http://www.stanq.com >  >  >---' >Incoming mail is certified Virus Free. ; >Checked by AVG anti-virus system (http://www.grisoft.com). A >Version: 6.0.489 / Virus Database: 288 - Release Date: 6/10/2003  >I ---5& Outgoing mail is certified Virus Free.: Checked by AVG anti-virus system (http://www.grisoft.com).@ Version: 6.0.489 / Virus Database: 288 - Release Date: 6/10/2003   ------------------------------  % Date: Thu, 03 Jul 2003 10:02:26 -0400i* From: "Stanley F. Quayle" <stan@stanq.com>O Subject: RE: VAX support (was: Re: OpenVMS Technical Seminar Highlights (some)) . Message-ID: <3F03FF32.11111.542AF4F@localhost>  9 > PL/I has been on Alpha all along, fully supported.  see  > www.kednos.com  ? This was originally a DEC product that got spun off during the _E transition.  That's why I asked if it counted -- since a DEC license o would be worthless...   F Dibol and SCAN were killed off during the transition to Alpha.  Other & companies have created new versions...  
 --Stan Quayle  Quayle Consulting Inc.  
 ----------C Stanley F. Quayle, P.E. N8SQ  +1 614-868-1363  Fax: +1 614 868-1671 1 8572 North Spring Ct. NW, Pickerington, OH  43147p= Preferred address:  stan@stanq.com       http://www.stanq.comA   ------------------------------  $ Date: Thu, 3 Jul 2003 07:05:31 -0700# From: "Tom Linden" <tom@kednos.com> O Subject: RE: VAX support (was: Re: OpenVMS Technical Seminar Highlights (some)) 9 Message-ID: <CIEJLCMNHNNDLLOOGNJIGEGAHIAA.tom@kednos.com>    >-----Original Message----- 0 >From: Stanley F. Quayle [mailto:stan@stanq.com]& >Sent: Thursday, July 03, 2003 7:02 AM >To: Info-VAX@Mvb.Saic.ComH >Subject: RE: VAX support (was: Re: OpenVMS Technical Seminar Highlights >(some)) >  > : >> PL/I has been on Alpha all along, fully supported.  see >> www.kednos.com_ > @ >This was originally a DEC product that got spun off during the F >transition.  That's why I asked if it counted -- since a DEC license  >would be worthless...  J That is true, but that is not the same thing.  Whereas Dibol, for example,$ was never ported to Alpha, PL/I was.  < But to set the record straight it was originally licensed toA Digital in 1978.  When we took it over 1999, it just came home:-)l   >1G >Dibol and SCAN were killed off during the transition to Alpha.  Other 1' >companies have created new versions...  >- >--Stan Quayle >Quayle Consulting Inc.  >  >----------DD >Stanley F. Quayle, P.E. N8SQ  +1 614-868-1363  Fax: +1 614 868-16712 >8572 North Spring Ct. NW, Pickerington, OH  43147> >Preferred address:  stan@stanq.com       http://www.stanq.com >  >  >---' >Incoming mail is certified Virus Free.A; >Checked by AVG anti-virus system (http://www.grisoft.com).-A >Version: 6.0.489 / Virus Database: 288 - Release Date: 6/10/2003  >  ---D& Outgoing mail is certified Virus Free.: Checked by AVG anti-virus system (http://www.grisoft.com).@ Version: 6.0.489 / Virus Database: 288 - Release Date: 6/10/2003   ------------------------------   Date: 3 Jul 2003 09:23:46 -0500 - From: Kilgallen@SpamCop.net (Larry Kilgallen)1O Subject: RE: VAX support (was: Re: OpenVMS Technical Seminar Highlights (some)) 3 Message-ID: <+hRq30mfsBVy@eisner.encompasserve.org>   [ In article <3F03FF32.11111.542AF4F@localhost>, "Stanley F. Quayle" <stan@stanq.com> writes:r: >> PL/I has been on Alpha all along, fully supported.  see >> www.kednos.com9 > A > This was originally a DEC product that got spun off during the pG > transition.  That's why I asked if it counted -- since a DEC license   > would be worthless...   G A DEC license for DEC C on Alpha in the same time period would also not4G count, since DEC licenses do not include a "right to use new versions". F Of course if you are talking about LMF enforcement that is a different calculation than what is legal.7  I If one wanted an "upgrade" price, maybe Kednos offered that at some time. : Having never bought from Kednos, I do not know the prices.   ------------------------------   Date: 3 Jul 2003 09:19:30 -0500,- From: Kilgallen@SpamCop.net (Larry Kilgallen) O Subject: Re: VAX support (was: Re: OpenVMS Technical Seminar Highlights (some)) 3 Message-ID: <KlyE7tHeTD8v@eisner.encompasserve.org>_  [ In article <3F03EEC0.16088.5026FFD@localhost>, "Stanley F. Quayle" <stan@stanq.com> writes: / > On 3 Jul 2003 at 5:14, Larry Kilgallen wrote: L >> >> There are many other packages that didn't get rescued and are still on >> >> VAX only.  >> > J >> > Do you have a list? >> 5 >> For languages:  >>   >> VAX Scan4 >> Dibol >> LISPl >> OPS52 >> RPG > A > What about PL/I?  Owned by someone else now, does that "count"?_  : DEC ported it to Alpha and then sold it to another vendor.D It is now in the hands of a different vendor (Kednos) and Tom LindenA of Kednos participates in this newsgroup.  There are periodic newnD versions of PL/I for VAX and Alpha, with the most recent new featureC I can think of being support for the VMS Hobbyist program.  So I doD) not think "still on VAX only" applies :-)   3 > There is an Alpha Dibol compiler, not sold by HP.   @ Ok, not knowing Dibol I have no idea how much better/worse it is compared to what is on VAX.   ) > And SRI makes an Alpha version of SCAN.   C I gather you have not written any complex Scan programs if you have @ found lack of debugger support is not a major showstopper.  WithD many languages debugging is just like with another language, but theC Event structure supported for VAX Scan is really required for those1I sorts of programs, much like the Ada Tasking support in the VMS debugger.    ------------------------------  % Date: Thu, 03 Jul 2003 11:32:38 -04000* From: "Stanley F. Quayle" <stan@stanq.com>O Subject: Re: VAX support (was: Re: OpenVMS Technical Seminar Highlights (some)) . Message-ID: <3F041456.12650.595451E@localhost>  - On 3 Jul 2003 at 9:19, Larry Kilgallen wrote: 5 > > There is an Alpha Dibol compiler, not sold by HP._B > Ok, not knowing Dibol I have no idea how much better/worse it is > compared to what is on VAX.   E I know of one site that uses it, and they say there are all sorts of  C useful extensions.  They support both VAX and Alpha customers, and  - the Alpha version is just recompile-and-link.   @ They require their developers to do all work on VAX so that the F extensions won't "accidentally" be used -- personally, I think coding  standards might help...o  E > I gather you have not written any complex Scan programs if you have B > found lack of debugger support is not a major showstopper.  WithF > many languages debugging is just like with another language, but theE > Event structure supported for VAX Scan is really required for those9K > sorts of programs, much like the Ada Tasking support in the VMS debugger.   E It's been a long time since I've written any SCAN programs.  I agree 2F that good debugger support is important.  Have the debugger internals < have ever been documented to support third-party extensions?  B My guess about going to ELF/DWARF on Itanium means that you could C have third-party debuggers pretty easily.  Not that gdb is easy to   use...  
 --Stan Quayle, Quayle Consulting Inc.  
 ----------C Stanley F. Quayle, P.E. N8SQ  +1 614-868-1363  Fax: +1 614 868-1671 1 8572 North Spring Ct. NW, Pickerington, OH  43147 = Preferred address:  stan@stanq.com       http://www.stanq.com    ------------------------------  % Date: Thu, 03 Jul 2003 11:40:29 -0400 * From: "Stanley F. Quayle" <stan@stanq.com>O Subject: RE: VAX support (was: Re: OpenVMS Technical Seminar Highlights (some)) . Message-ID: <3F04162D.12167.59C73C7@localhost>  ( On 3 Jul 2003 at 7:05, Tom Linden wrote:> > But to set the record straight it was originally licensed toC > Digital in 1978.  When we took it over 1999, it just came home:-)3  1 Hope they took good care of it in the meantime...           
 --Stan Quayle  Quayle Consulting Inc.  
 ----------C Stanley F. Quayle, P.E. N8SQ  +1 614-868-1363  Fax: +1 614 868-1671E1 8572 North Spring Ct. NW, Pickerington, OH  43147 = Preferred address:  stan@stanq.com       http://www.stanq.com    ------------------------------  $ Date: Thu, 3 Jul 2003 11:51:11 -0400/ From: "Hank Vander Waal" <hvanderw@mansply.com> O Subject: RE: VAX support (was: Re: OpenVMS Technical Seminar Highlights (some)),? Message-ID: <MDEGJFAOHGLNLHONIEBMGEMHCMAA.hvanderw@mansply.com>,   my .02 on DBL / DIBOL   E DBL is indeed a very nice compiler  - a step or 2 above the Vax DIBOL ( Compiles and runs very fast on Alpha VMS4 Just ask Bob C.  he writes with it all the time ! :)  G but sure do miss the VMS debug support - DBL has it's own debug program   E nice to be able to move it from platform to another without main codeA changes7   Hank Vander Waal   ------------------------------   Date: 3 Jul 2003 11:20:09 -0500$- From: Kilgallen@SpamCop.net (Larry Kilgallen)eO Subject: RE: VAX support (was: Re: OpenVMS Technical Seminar Highlights (some)) 3 Message-ID: <NzxfsaRznIGb@eisner.encompasserve.org>   [ In article <3F04162D.12167.59C73C7@localhost>, "Stanley F. Quayle" <stan@stanq.com> writes:P* > On 3 Jul 2003 at 7:05, Tom Linden wrote:? >> But to set the record straight it was originally licensed to$D >> Digital in 1978.  When we took it over 1999, it just came home:-) > 3 > Hope they took good care of it in the meantime...i  B From a PL/I perspective probably not, because they rewrote some of the Alpha stuff in C :-)   ------------------------------   Date: 3 Jul 2003 11:19:07 -0500N- From: Kilgallen@SpamCop.net (Larry Kilgallen) O Subject: Re: VAX support (was: Re: OpenVMS Technical Seminar Highlights (some))N3 Message-ID: <ecb$BP5lQpHy@eisner.encompasserve.org>   [ In article <3F041456.12650.595451E@localhost>, "Stanley F. Quayle" <stan@stanq.com> writes: / > On 3 Jul 2003 at 9:19, Larry Kilgallen wrote: 6 >> > There is an Alpha Dibol compiler, not sold by HP.C >> Ok, not knowing Dibol I have no idea how much better/worse it is  >> compared to what is on VAX. > G > I know of one site that uses it, and they say there are all sorts of IE > useful extensions.  They support both VAX and Alpha customers, and r/ > the Alpha version is just recompile-and-link.  > B > They require their developers to do all work on VAX so that the H > extensions won't "accidentally" be used -- personally, I think coding  > standards might help...c > F >> I gather you have not written any complex Scan programs if you haveC >> found lack of debugger support is not a major showstopper.  With4G >> many languages debugging is just like with another language, but the F >> Event structure supported for VAX Scan is really required for thoseL >> sorts of programs, much like the Ada Tasking support in the VMS debugger. > G > It's been a long time since I've written any SCAN programs.  I agree  H > that good debugger support is important.  Have the debugger internals > > have ever been documented to support third-party extensions?  A My study of the debugger source listings has never been more thanY@ cursory, but I do not believe the VMS Debugger currently has any= plugin capability for adding extensions, regardless of whose.   ? The notion of sharing code between the debugger, Heap Analyzer, C PCA(?), System Code Debugger and SDA seems daunting enough, withouta adding plugin capability.   B Even back when the language groups were responsible for supporting? their language in the debugger, I was under the impression they > just checked them into the source pool for the debugger rather  than built them as an extension.   ------------------------------   Date: 3 Jul 2003 16:56:26 GMT ( From: bill@cs.uofs.edu (Bill Gunshannon)O Subject: Re: VAX support (was: Re: OpenVMS Technical Seminar Highlights (some)) 4 Message-ID: <be1n7q$a4ku$1@ID-135708.news.dfncis.de>  3 In article <NzxfsaRznIGb@eisner.encompasserve.org>,-0 	Kilgallen@SpamCop.net (Larry Kilgallen) writes:] > In article <3F04162D.12167.59C73C7@localhost>, "Stanley F. Quayle" <stan@stanq.com> writes:A+ >> On 3 Jul 2003 at 7:05, Tom Linden wrote:1@ >>> But to set the record straight it was originally licensed toE >>> Digital in 1978.  When we took it over 1999, it just came home:-)  >> o4 >> Hope they took good care of it in the meantime... > D > From a PL/I perspective probably not, because they rewrote some of > the Alpha stuff in C :-)   I just have to ask....  * Is the PL/I compiler written in PL/I?  :-)   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>   1   ------------------------------  $ Date: Thu, 3 Jul 2003 09:59:24 -0700# From: "Tom Linden" <tom@kednos.com>-O Subject: RE: VAX support (was: Re: OpenVMS Technical Seminar Highlights (some)) 9 Message-ID: <CIEJLCMNHNNDLLOOGNJIIEGEHIAA.tom@kednos.com>    >-----Original Message----- E >From: bill@gw5.cs.uofs.edu [mailto:bill@gw5.cs.uofs.edu]On Behalf Oft >Bill Gunshannon& >Sent: Thursday, July 03, 2003 9:56 AM >To: Info-VAX@Mvb.Saic.ComH >Subject: Re: VAX support (was: Re: OpenVMS Technical Seminar Highlights >(some)) >S >e4 >In article <NzxfsaRznIGb@eisner.encompasserve.org>,1 >	Kilgallen@SpamCop.net (Larry Kilgallen) writes:2= >> In article <3F04162D.12167.59C73C7@localhost>, "Stanley F. ! >Quayle" <stan@stanq.com> writes: , >>> On 3 Jul 2003 at 7:05, Tom Linden wrote:A >>>> But to set the record straight it was originally licensed to F >>>> Digital in 1978.  When we took it over 1999, it just came home:-) >>>-5 >>> Hope they took good care of it in the meantime...  >>E >> From a PL/I perspective probably not, because they rewrote some ofo >> the Alpha stuff in C :-)_ >D >I just have to ask....  > + >Is the PL/I compiler written in PL/I?  :-)   C Yes.  It was originally written in subset G without preprocessor toP	 faciltate J porting.  Cutler, et.al. rewrote the lexer in macro to make it faster (bad choiceG in my view) and rewrote the the runtime likewise in Macro.  When it wasl	 ported to-I alpha, the macro routines were rewritten in C.  At that point they should 	 have donet it in PL/I but...      >D >bill  >  >-- K >Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolves E >bill@cs.scranton.edu     |  and a sheep voting on what's for dinner.  >University of Scranton   | ? >Scranton, Pennsylvania   |         #include <std.disclaimer.h>  >  >---' >Incoming mail is certified Virus Free. ; >Checked by AVG anti-virus system (http://www.grisoft.com).1A >Version: 6.0.489 / Virus Database: 288 - Release Date: 6/10/2003N >T --- & Outgoing mail is certified Virus Free.: Checked by AVG anti-virus system (http://www.grisoft.com).@ Version: 6.0.489 / Virus Database: 288 - Release Date: 6/10/2003   ------------------------------  $ Date: Thu, 3 Jul 2003 10:06:08 -0700# From: "Tom Linden" <tom@kednos.com>6O Subject: RE: VAX support (was: Re: OpenVMS Technical Seminar Highlights (some))R9 Message-ID: <CIEJLCMNHNNDLLOOGNJICEGFHIAA.tom@kednos.com>    >-----Original Message-----tE >From: bill@gw5.cs.uofs.edu [mailto:bill@gw5.cs.uofs.edu]On Behalf OfL >Bill Gunshannon& >Sent: Thursday, July 03, 2003 9:56 AM >To: Info-VAX@Mvb.Saic.ComH >Subject: Re: VAX support (was: Re: OpenVMS Technical Seminar Highlights >(some)) >4 > 4 >In article <NzxfsaRznIGb@eisner.encompasserve.org>,1 >	Kilgallen@SpamCop.net (Larry Kilgallen) writes: > >> In article <3F04162D.12167.59C73C7@localhost>, "Stanley F. ! >Quayle" <stan@stanq.com> writes:p, >>> On 3 Jul 2003 at 7:05, Tom Linden wrote:A >>>> But to set the record straight it was originally licensed to F >>>> Digital in 1978.  When we took it over 1999, it just came home:-) >>> 5 >>> Hope they took good care of it in the meantime...  >>  E >> From a PL/I perspective probably not, because they rewrote some of  >> the Alpha stuff in C :-)  >  >I just have to ask....  > + >Is the PL/I compiler written in PL/I?  :-)-  G Should have added, that the progenitor of this compiler was the MulticsED PL/I which was the first bootstrapping compiler.  BTW, Digital Press7 produce a book on the implementation of PL/I on the VAX B "Engineering a Compiler - VAX-11 Code Generation and Optimization"9 Anklam,Cutler,Heinen, MacLaren"  1982  ISBN 0-932376-19-32 >  >bill  >T >-- K >Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolves E >bill@cs.scranton.edu     |  and a sheep voting on what's for dinner.  >University of Scranton   | B >Scranton, Pennsylvania   |         #include <std.disclaimer.h>    >, >---' >Incoming mail is certified Virus Free. ; >Checked by AVG anti-virus system (http://www.grisoft.com).2A >Version: 6.0.489 / Virus Database: 288 - Release Date: 6/10/20036 >  --- & Outgoing mail is certified Virus Free.: Checked by AVG anti-virus system (http://www.grisoft.com).@ Version: 6.0.489 / Virus Database: 288 - Release Date: 6/10/2003   ------------------------------   Date: 3 Jul 2003 06:40:04 -0700 + From: paul_hallam@hotmail.com (Paul Hallam) = Subject: VAX Vup Listing not available on HP - where is it ??u< Message-ID: <5ed44bd3.0307030540.db77a99@posting.google.com>  = Does anyone know what HP have done with the old VAX/Alpha VUP  comparison listings.F I need to get the VUP ratings for Vax 7000/700A, 7000/710 and 7000/7205 but the lists are no longer available on the HP site.6  
 Anyone help ?    Many thanks,   Paul Hallam    ------------------------------  % Date: Thu, 03 Jul 2003 08:48:33 -0500m( From: Michael Rice <marice@whiteice.com>A Subject: Re: VAX Vup Listing not available on HP - where is it ?? / Message-ID: <vg8d1ocbhta504@corp.supernews.com>   ' On 7/3/2003 8:40 AM, Paul Hallam wrote: ? > Does anyone know what HP have done with the old VAX/Alpha VUP_ > comparison listings.H > I need to get the VUP ratings for Vax 7000/700A, 7000/710 and 7000/7207 > but the lists are no longer available on the HP site.  >  > Anyone help ?  > 
 > Many thanks  > 
 > Paul Hallam   " Here are a couple that might help:  ! http://www.pyramiddec.com/vup.htm - http://www.algonet.se/~tucker/VaxCPUtable.txt_   ------------------------------  % Date: Thu, 03 Jul 2003 09:55:09 -0400 8 From: Jim Agnew - VCU/MCV Neurosurgery <jpagnew@vcu.edu>A Subject: Re: VAX Vup Listing not available on HP - where is it ?? ' Message-ID: <3F0435BD.34335931@vcu.edu>c   i have part of what you want at 1 http://anacin.nsc.vcu.edu/~jim/mvax/vax-perf.htmlN   jimr     Paul Hallam wrote: > ? > Does anyone know what HP have done with the old VAX/Alpha VUP_ > comparison listings.H > I need to get the VUP ratings for Vax 7000/700A, 7000/710 and 7000/7207 > but the lists are no longer available on the HP site.8 >  > Anyone help ?  > 
 > Many thanks  > 
 > Paul Hallam    --  F "4,000 years ago I made a mistake."  Elrond Half-Elven, in "Fellowship of the Ring"  F "I try not to be right any more than necessary". -- Larry Wall, author of the Perl Language   ------------------------------  % Date: Thu, 03 Jul 2003 12:51:19 -0500 ( From: brandon@dalsemi.com (John Brandon)A Subject: Re: VAX Vup Listing not available on HP - where is it ?? 1 Message-ID: <03070312511950@dscis6-0.dalsemi.com>   ' On 7/3/2003 8:40 AM, Paul Hallam wrote: ? > Does anyone know what HP have done with the old VAX/Alpha VUP5 > comparison listings.H > I need to get the VUP ratings for Vax 7000/700A, 7000/710 and 7000/7207 > but the lists are no longer available on the HP site./ >  > Anyone help ?- > 
 > Many thankse > 
 > Paul Hallam-  M Why not use the TPS (Trans Per Sec) that is available for both VAX and Alpha?f  ? http://h18002.www1.hp.com/alphaserver/performance/perf_tps.html1         J*o*h*n B*r*a*n*d*o*ni VMS Systems Administratora* firstname.lastname.spam.me.not@dalsemi.com   ------------------------------   Date: 3 Jul 2003 10:39:21 -000014 From: Doc.Cypher <Use-Author-Address-Header@[127.1]>B Subject: VMS makes "General News" section of HP's "Customer Times"4 Message-ID: <20030703103921.495.qmail@nym.alias.net>   A little bird sent me this...o  D http://www.hp.com/products1/evolution/customertimes/pdfs/general.pdf   page 2:: ===========  Transitioning - simply!   N Simplification is the name of the game with HP's new Software License Trade-InM and Transfer Policies for operating environments and HP application products.S  > HP's policy has you well covered by offering transition paths:  7 * From HP-UX PA-RISC to HP-UX Integrity or OpenVMS I64.g  K * From Tru64 UNIX/Alpha to HP-UX PA-RISC, HP-UX Integrity, or OpenVMS I64.o  N * From OpenVMS/VAX or Alpha to OpenVMS I64, HP-UX PA-RISC, or HP-UX Integrity.  F * From MPE/iX e3000 to HP-UX PA-RISC, HP-UX Integrity, or OpenVMS I64.  G NOTE THAT THE OPTIONS INCLUDE MOVING **TO** VMS FROM OTHER PLATFORMS...        Interesting Times indeed.e     Doc. -- .K OpenVMS.         Eight out of ten hackers prefer *other* operating systems.l   ------------------------------   Date: 3 Jul 2003 15:49:16 -0000i4 From: Doc.Cypher <Use-Author-Address-Header@[127.1]>F Subject: Re: VMS makes "General News" section of HP's "Customer Times"6 Message-ID: <20030703154916.20943.qmail@nym.alias.net>  D On 3 Jul 2003, Doc.Cypher <Use-Author-Address-Header@[127.1]> wrote:  E >http://www.hp.com/products1/evolution/customertimes/pdfs/general.pdff   Uhm, okay...  ; Next time I post something like this I'll Base64 encode it..  D The difficulties reading it would at least provoke some reaction. :)     Doc. -- eK OpenVMS.         Eight out of ten hackers prefer *other* operating systems.g   ------------------------------   Date: 3 Jul 2003 11:22:35 -0500 - From: Kilgallen@SpamCop.net (Larry Kilgallen)bF Subject: Re: VMS makes "General News" section of HP's "Customer Times"3 Message-ID: <nuitGDgDtGnB@eisner.encompasserve.org>i  m In article <20030703154916.20943.qmail@nym.alias.net>, Doc.Cypher <Use-Author-Address-Header@[127.1]> writes::F > On 3 Jul 2003, Doc.Cypher <Use-Author-Address-Header@[127.1]> wrote: > F >>http://www.hp.com/products1/evolution/customertimes/pdfs/general.pdf >  > Uhm, okay... > = > Next time I post something like this I'll Base64 encode it.a > F > The difficulties reading it would at least provoke some reaction. :)  . You don't think PDF is enough trouble for us ?   ------------------------------   Date: 3 Jul 2003 17:25:21 -0000 4 From: Doc.Cypher <Use-Author-Address-Header@[127.1]>F Subject: Re: VMS makes "General News" section of HP's "Customer Times"6 Message-ID: <20030703172521.18214.qmail@nym.alias.net>  = On 3 Jul 2003, Kilgallen@SpamCop.net (Larry Kilgallen) wrote: B >In article <20030703154916.20943.qmail@nym.alias.net>, Doc.Cypher, ><Use-Author-Address-Header@[127.1]> writes:G >> On 3 Jul 2003, Doc.Cypher <Use-Author-Address-Header@[127.1]> wrote:w >>  G >>>http://www.hp.com/products1/evolution/customertimes/pdfs/general.pdfe >> t >> Uhm, okay...e >> p> >> Next time I post something like this I'll Base64 encode it. >>  G >> The difficulties reading it would at least provoke some reaction. :)  > / >You don't think PDF is enough trouble for us ?u   Good point.I  L I did think there was enough in the quoted section to get some reaction.  OrD are certain posters still looking for faults in the entire document?  L AFAIK this is the first in a very long time that migration *to* VMS has been9 suggested without a lot of qualifications attached to it.<  G I know... One swallow etc., but if we bash HP for small, positive steps-% they'll just start ignoring us again.r     Doc. -- <K OpenVMS.         Eight out of ten hackers prefer *other* operating systems.-   ------------------------------   Date: 3 Jul 2003 05:09:40 -0500,- From: Kilgallen@SpamCop.net (Larry Kilgallen)d( Subject: Re: what is VMS advanced Server3 Message-ID: <0cJfwnPhwXoV@eisner.encompasserve.org>.  g In article <vg7e69af1e5o0f@corp.supernews.com>, "Brad McCusker" <brad.mccuskerNosp@Mcompaq.com> writes:e   <top-posting corrected>e  C > "Kesav Tadimeti" <Kesav_Tadimeti@KeaneIndia.com> wrote in messageeG > news:8EA11405E59BD611BA7100104B93C26001A044F3@exdel01.del.mgsl.com...d >> Hello allI >> What exactly is the VMS advanced server & how is it different from theoJ >> normal VMS? Does VMS also have a concept of workstation and server like >> windows?E   <top-posting corrected>   J > Advanced Server for OpenVMS is the name of the SMB file and print serverM > that runs on VMS (in other words, its a Windows NT/2000 compatible file andi? > print server).  It used to be known as PATHWORKS for OpenVMS.t >  > Brad McCusker  > OpenVMS Engineeringo  B For some of us, "Advanced Server" is an unfortunate naming choice.@ Some allege the name is supposed to sound familiar to to WindowsA users, but I would say Kesav Tadimeti has defeated that argument.fA The same stuff formerly was called "Pathworks", which was equally  obscure.  B As for your second question, the distinction between a workstation@ and a server tends to be less in VMS than in Windows.  Of courseA something must have a display to be called a workstation (not alli> VMS systems have that), but the software differences to make a> workstation happen to be present on a lot of VMS servers these= days.  Most VMS servers have a license for more than a single  user, but there are exceptions.l   ------------------------------  % Date: Thu, 03 Jul 2003 12:03:50 +0100e* From: Nic Clews <sendspamhere@[127.0.0.1]>( Subject: Re: what is VMS advanced Server& Message-ID: <be12o5$dl$1@lore.csc.com>   Kesav Tadimeti wrote:-  H > What exactly is the VMS advanced server & how is it different from theI > normal VMS? Does VMS also have a concept of workstation and server like 
 > windows?  > Brad's "the man" to give you the answer about Advanced Server.  B As to workstation or server concepts, the answer is more vague. AsG opposed to Windows, you use the same software for a server (which we'll_A define as being potentially back-room, lots of storage, centrallyeA managed, multiple CPU, probably clustered multiple servers) and anC workstation (which we'll define as the graphics head is the primaryn@ display, single CPU and lower end local direct attached storage,C possibly clustered with a server as above over a single or multiple, network interfaces)n  G The difference in the way they run is in the setup of system parameterskF if they are clustered, voting strategies, distributed lock management, availability considerations.  G However it gets very, very vague. You can have graphics cards on servergF systems, and workstations that do not have graphics cards. Systems canH share the same operating system software disk (network / lan booting) orA have their own. THe "security domain" resides in the cluster with-H multiple systems, otherwise it is per system where by and large physical6 access has it. It is a very flexible operating system.  C Licensing classes is one area of distinction, servers fall into theeB workgroup and enterprise  levels of server, the workstation is the lowest and cheapest class.  H I'm not sure if to you I've either cleared or muddied the water, howeverH you could run Advanced Server on either a workstation or a server class,F or both, there is no demarcation between systems. Typically, folks runE little test environments and do things on workstations that typicallysF don't affect the larger number of users expected on server systems yet- this is transparent to whatever is being run.e  E To be fair, the real distinction is clustered or not clustered, where E the clustering is many multiple (to 96 systems supported) in a sharedw- everything environment, or merely standalone.   A Even the word "cluster" is worlds apart from what is offered by ai* Windows system. Or others for that matter.   I'll stop woffling now.o   -- g? Regards, Nic Clews a.k.a. Mr. CP Charges, CSC Computer Sciences  nclews at csc dot coml   ------------------------------  $ Date: Thu, 3 Jul 2003 08:19:00 -04005 From: "Brad McCusker" <brad.mccuskerNosp@Mcompaq.com>e( Subject: Re: what is VMS advanced Server/ Message-ID: <vg87pr9qghgi9e@corp.supernews.com>w  : "Larry Kilgallen" <Kilgallen@SpamCop.net> wrote in message- news:0cJfwnPhwXoV@eisner.encompasserve.org...sA > In article <vg7e69af1e5o0f@corp.supernews.com>, "Brad McCusker" ' <brad.mccuskerNosp@Mcompaq.com> writes:  >r > D > For some of us, "Advanced Server" is an unfortunate naming choice.B > Some allege the name is supposed to sound familiar to to WindowsC > users, but I would say Kesav Tadimeti has defeated that argument. C > The same stuff formerly was called "Pathworks", which was equallys
 > obscure. >M  I ohhh... I lived that nightmare.  I don't care to get into that "rename oriH not to rename, and if we rename, rename it to what" discussion again for0 anything.  There was no good answer to that one.  L (for those that might wonder where that "Advanced Server" name came from, itL is the brand name that AT&T used for its file and print server product whichI is what we licensed and ported to VMS to create PATHWORKS V5 and beyond.)r   ------------------------------  # Date: Thu, 03 Jul 2003 12:40:55 GMT1) From: Patrick Young <P.Young@unsw.EDU.AU>1( Subject: Re: what is VMS advanced Server< Message-ID: <rvVMa.722$JI4.10288@news-server.bigpond.net.au>   Nic Clews wrote: > D > As to workstation or server concepts, the answer is more vague. AsI > opposed to Windows, you use the same software for a server (which we'll(C > define as being potentially back-room, lots of storage, centrally0  > I don't like the term "server". I make it a point to inform my@ users they are using a workstation. In the machine room (No, not; server room), there is a badge on the front of each VMS boxiJ supplied by Compaq saying "workstation" - being a cluster of workstations.  7 The Tru64 8400 "AlphaServer" is a bit hard to cover up.-  7 "Server" smells too much like Novell and Window(tm) for 
 my liking.   ------------------------------   End of INFO-VAX 2003.364 ************************