1 INFO-VAX	Tue, 12 Apr 2005	Volume 2005 : Issue 203       Contents: (history of) BACKUP/ALIAS  Re: (history of) BACKUP/ALIAS  Re: (history of) BACKUP/ALIAS  Re: (history of) BACKUP/ALIAS  Re: (history of) BACKUP/ALIAS  Re: (history of) BACKUP/ALIAS  Re: (history of) BACKUP/ALIAS  Re: (history of) BACKUP/ALIAS  Re: (history of) BACKUP/ALIAS  Re: (history of) BACKUP/ALIAS  Re: (history of) BACKUP/ALIAS  600au and mmov Re: 600au and mmov2 Aging Alpha Processor Gets Companion Product Boost6 Re: Aging Alpha Processor Gets Companion Product Boost7 RE: Broken VAXstation 4000 VLC (was Re: Broken vax4000) L Re: Configuring multi-port NIC on DS10 with DECNET-Plus and TCPIP 5.3 5.35.3 Re: DCPS 2.3, %DCPS-F-STREAMUSE 4 Re: Finding The Right Path For Your VMS Applications4 Re: Finding The Right Path For Your VMS Applications5 Re: Frustration!  EB64+ too old to run OpenVMS 7.3-1? 5 Re: Frustration!  EB64+ too old to run OpenVMS 7.3-1? 4 Re: Frustration! EB64+ too old to run OpenVMS 7.3-1?4 Re: Frustration! EB64+ too old to run OpenVMS 7.3-1?4 Re: High File Watermarking question for Hoff Hoffman4 Re: High File Watermarking question for Hoff Hoffman Re: loging in and out user?   Re: Multiprocessor Microvax II ?  Re: Multiprocessor Microvax II ?  Re: Multiprocessor Microvax II ?  Re: Multiprocessor Microvax II ? Re: OpenVMS FAQ Errata OpenVMS FAQ Errata Re: OpenVMS FAQ Errata3 OpenVMS Frequently Asked Questions (FAQ), Part 1/11 4 OpenVMS Frequently Asked Questions (FAQ), Part 10/114 OpenVMS Frequently Asked Questions (FAQ), Part 11/113 OpenVMS Frequently Asked Questions (FAQ), Part 2/11 3 OpenVMS Frequently Asked Questions (FAQ), Part 3/11 3 OpenVMS Frequently Asked Questions (FAQ), Part 4/11 3 OpenVMS Frequently Asked Questions (FAQ), Part 5/11 3 OpenVMS Frequently Asked Questions (FAQ), Part 6/11 3 OpenVMS Frequently Asked Questions (FAQ), Part 7/11 3 OpenVMS Frequently Asked Questions (FAQ), Part 8/11 3 OpenVMS Frequently Asked Questions (FAQ), Part 9/11  OT: Race for dual core 8086s/ Re: Procedure for installing PERL modules (LWP) / Re: Procedure for installing PERL modules (LWP)  Re: Remote printing woes.  Re: RRD43 and CD-RW  Re: RRD43 and CD-RW  Re: RRD43 and CD-RW  Re: RRD43 and CD-RW  Re: RRD43 and CD-RW  Re: RRD43 and CD-RW  Re: RRD43 and CD-RW  Re: RRD43 and CD-RW  Re: RRD43 and CD-RW  Re: RRD43 and CD-RW  Re: RRD43 and CD-RW  Re: RRD43 and CD-RW  Re: RRD43 and CD-RW  Re: Site down? Re: Site down? Re: Site down? Re: Sort Directory by Date Re: Sort Directory by Date Re: Sort Directory by Date Re: Suggestion for FAQ Re: Suggestion for FAQ Re: Suggestion for FAQ Tape drive ejecting  third-party SCSI disks with VMS # Re: third-party SCSI disks with VMS # Re: third-party SCSI disks with VMS 4 Trivia challenge (Was: Multiprocessor Microvax II ?) UAF search for last login date" Re: UAF search for last login date Re: VMS 8.2 or 7.3-2 Re: VMS 8.2 or 7.3-2 Re: VMS 8.2 or 7.3-2* Want a FREE IPOD? it works!!!!!!!!!!!!!!!!E Re: Which release notes say sts$manager:utc$configure_tdf is obsolete ' Windoze better than linux says analyst! + Re: Windoze better than linux says analyst!   Re: [TCPIP V5.4 ECO4] SFTP rants  Re: [TCPIP V5.4 ECO4] SFTP rants  Re: [TCPIP V5.4 ECO4] SFTP rants  Re: [TCPIP V5.4 ECO4] SFTP rants  F ----------------------------------------------------------------------  + Date: Sun, 10 Apr 2005 07:18:09 +0000 (UTC) P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)" Subject: (history of) BACKUP/ALIAS$ Message-ID: <d3ajvh$sh3$1@online.de>  C Does anyone have a complete description of a) what the behaviour of C /ALIAS is/was with each version of VMS (VAX and ALPHA, if there's a G difference) and b) whether this corresponded to the description in HELP  of that same version of VMS?  E I gather that /ALIAS "preserves the old behaviour", which apparently  I means that if there are multiple entries for a file (or directory), then  F they are treated equivalently, i.e. all are copied to SEPARATE output F files (different file-IDs).  With /NOALIAS, only the primary entry is  copied, right?  E If the above is correct, I can see that one might sometimes want the  I /ALIAS behaviour and sometimes the /NOALIAS behaviour.  Neither is ideal  G from my point of view, but presumably these are the only possibilities   with /NOIMAGE.  + What really confuses me, though, is /IMAGE.   > The HELP for 7.2-1 and 7.3-1 is identical.  The 7.3-2 HELP for6 BACKUP/ALIAS contains the following additional stuff:   (                                     NOTE  A         Use the /ALIAS qualifier only when you are restoring very ?         old savesets (from OpenVMS Version 6.2 or earlier). The A         current default behavior is correct in nearly every other          situation.    D Also, the following is present in HELP for BACKUP/IMAGE in 7.2-1 and 7.3-1, but gone in 7.3-2:   E      Specifying the /IMAGE qualifier without also specifying /NOALIAS B      can result in incomplete disk or file restoration operations.D      Therefore, Compaq strongly recommends that you specify /NOALIAS>      with /IMAGE when performing image mode backup operations.  = Did the behaviour actually change, or just the documentation?   > It seems really bizarre that BACKUP/IMAGE would not produce a E functionally equivalent copy of a disk.  By "functionally equivalent  C copy", I mean a copy in which non-primary file entries are neither  F ignored nor copied as regular files (new file-ID on the output disk), I but rather in which non-primary entries on the source disk correspond to  D non-primary entries on the target disk.  However, HELP before 7.3-2   certainly gives this impression.  H Also, what does "restoring very old savesets" mean?  Does it refer to a ) non-image restore or to an image restore.   > Let me phrase the question another way: If I do a disk-to-diskG (non-saveset) backup, was there ever a time when specifying /IMAGE but  H specifying neither /ALIAS nor /NOALIAS resulted in something other than  a functionally equivalent copy?    ------------------------------    Date: 10 Apr 2005 20:06:15 -0700$ From: "AEF" <spamsink2001@yahoo.com>& Subject: Re: (history of) BACKUP/ALIASC Message-ID: <1113188775.488826.170280@z14g2000cwz.googlegroups.com>   / Phillip Helbig---remove CLOTHES to reply wrote: E > Does anyone have a complete description of a) what the behaviour of E > /ALIAS is/was with each version of VMS (VAX and ALPHA, if there's a D > difference) and b) whether this corresponded to the description in HELP > of that same version of VMS?     Not I.    F > I gather that /ALIAS "preserves the old behaviour", which apparentlyE > means that if there are multiple entries for a file (or directory),  thenG > they are treated equivalently, i.e. all are copied to SEPARATE output   G > files (different file-IDs).  With /NOALIAS, only the primary entry is    > copied, right?  G You need to be more specific: disk to tape, tape to disk, disk to disk? @ /image, non-image? What do you mean by "copy multiple entries toC seaparate output files (diff. file-ID's)". I think that would apply % only to non-image restore operations.      > F > If the above is correct, I can see that one might sometimes want theD > /ALIAS behaviour and sometimes the /NOALIAS behaviour.  Neither is ideal : > from my point of view, but presumably these are the only
 possibilities  > with /NOIMAGE.     Neither is ideal for what?    - > What really confuses me, though, is /IMAGE.  > @ > The HELP for 7.2-1 and 7.3-1 is identical.  The 7.3-2 HELP for7 > BACKUP/ALIAS contains the following additional stuff:  > * >                                     NOTE > C >         Use the /ALIAS qualifier only when you are restoring very A >         old savesets (from OpenVMS Version 6.2 or earlier). The C >         current default behavior is correct in nearly every other  >         situation.    D It means to use /alias only for v6.2 save sets and older. Otherwise,D fuhgedaboutit. (forget about it). Actually, I have 6.2 on some of myD systems and *for image backups* with /NOALIAS it copies only primaryB files from disk to tape but without any alias qual (but still withF /image) it for some reason copies *some* of the alias entries to tape.C Still, I'm not sure why you'd ever need to use /ALIAS for a restore C operation unless you are doing a selective or non-image restore and 6 need to use or find out the alias names, respectively.    F > Also, the following is present in HELP for BACKUP/IMAGE in 7.2-1 and > 7.3-1, but gone in 7.3-2:  > G >      Specifying the /IMAGE qualifier without also specifying /NOALIAS D >      can result in incomplete disk or file restoration operations.F >      Therefore, Compaq strongly recommends that you specify /NOALIAS@ >      with /IMAGE when performing image mode backup operations. > ? > Did the behaviour actually change, or just the documentation?      I can't help you with this one.     ? > It seems really bizarre that BACKUP/IMAGE would not produce a F > functionally equivalent copy of a disk.  By "functionally equivalentD > copy", I mean a copy in which non-primary file entries are neitherG > ignored nor copied as regular files (new file-ID on the output disk),   G > but rather in which non-primary entries on the source disk correspond  toE > non-primary entries on the target disk.  However, HELP before 7.3-2 " > certainly gives this impression. > G > Also, what does "restoring very old savesets" mean?  Does it refer to  a + > non-image restore or to an image restore.  > @ > Let me phrase the question another way: If I do a disk-to-diskD > (non-saveset) backup, was there ever a time when specifying /IMAGE but D > specifying neither /ALIAS nor /NOALIAS resulted in something other than! > a functionally equivalent copy?     G I don't think the alias qualifier makes any difference for disk-to-disk E image backups. If it does, I'd use /NOALIAS -- I mean, why recopy the  files that have aliases?  3 What are you trying to do? What is your motivation?    ------------------------------  + Date: Mon, 11 Apr 2005 05:40:28 +0000 (UTC) P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)& Subject: Re: (history of) BACKUP/ALIAS$ Message-ID: <d3d2kc$n5h$1@online.de>  C In article <1113188775.488826.170280@z14g2000cwz.googlegroups.com>, ' "AEF" <spamsink2001@yahoo.com> writes:    J > You need to be more specific: disk to tape, tape to disk, disk to disk ?   Disk-to-disk, /IMAGE/NOSAVESET.   B > /image, non-image? What do you mean by "copy multiple entries toE > seaparate output files (diff. file-ID's)". I think that would apply ' > only to non-image restore operations.   C Yes, so would I, but the HELP specifically mentions the combination  /IMAGE/NOALIAS.   H > > If the above is correct, I can see that one might sometimes want theL > > /ALIAS behaviour and sometimes the /NOALIAS behaviour.  Neither is idealJ > > from my point of view, but presumably these are the only possibilities > > with /NOIMAGE. >  > Neither is ideal for what?  G If I have a file with an alias, usually I would want the backup to have H the file with an alias, i.e. neither copy it twice nor ignore the alias.   F > It means to use /alias only for v6.2 save sets and older. Otherwise,F > fuhgedaboutit. (forget about it). Actually, I have 6.2 on some of myF > systems and *for image backups* with /NOALIAS it copies only primaryD > files from disk to tape but without any alias qual (but still withH > /image) it for some reason copies *some* of the alias entries to tape.E > Still, I'm not sure why you'd ever need to use /ALIAS for a restore E > operation unless you are doing a selective or non-image restore and 8 > need to use or find out the alias names, respectively.  H I can see why, on non-image restore, one might want one behaviour or the* other, but surely /IMAGE should be /IMAGE.  I > I don't think the alias qualifier makes any difference for disk-to-disk G > image backups. If it does, I'd use /NOALIAS -- I mean, why recopy the  > files that have aliases? > 5 > What are you trying to do? What is your motivation?   G If I have a file with an alias, usually I would want the backup to have H the file with an alias, i.e. neither copy it twice nor ignore the alias.  I > I don't think the alias qualifier makes any difference for disk-to-disk G > image backups. If it does, I'd use /NOALIAS -- I mean, why recopy the  > files that have aliases?  H The HELP sounds like there are two alternatives: copy alias entries intoF more than one output file (BAD, especially if the alias is a directoryE like [.syscommon]/[vms$common]) or IGNORE them (whatever that means).   5 > What are you trying to do? What is your motivation?   D Simplicity itself: disk-to-disk, /IMAGE/NOSAVESET copy.  Just make aC functional copy of the disk.  In this case, a system disk.  In this F case, one wants neither duplicates of alias entries, nor does one want them to be ignored.   G I did /IMAGE and specified neither /ALIAS nor /NOALIAS.  That means the C default is /ALIAS, although "Compaq strongly recommends" specifying A /ALIAS.  The output disk LOOKED OK, i.e. [.SYS0]SYSCOMMON.DIR and - [000000]VMS$COMMON.DIR have the same file-ID.   H I think a) this is really confusing and b) not explained in the HELP whyH in the world /IMAGE should take this qualifier at all; after all, if one9 makes an /IMAGE backup, then one wants an identical copy.    ------------------------------    Date: 11 Apr 2005 06:52:14 -0700$ From: "AEF" <spamsink2001@yahoo.com>& Subject: Re: (history of) BACKUP/ALIASC Message-ID: <1113227534.434344.279640@l41g2000cwc.googlegroups.com>   / Phillip Helbig---remove CLOTHES to reply wrote: E > In article <1113188775.488826.170280@z14g2000cwz.googlegroups.com>, ( > "AEF" <spamsink2001@yahoo.com> writes: > E > > You need to be more specific: disk to tape, tape to disk, disk to  disk ? > ! > Disk-to-disk, /IMAGE/NOSAVESET.     A The /alias qualifier is primarily for disk-to-tape operations (or G disk-to-save_set). So don't worry about it. Either use /NOALIAS or just  skip it entirely.    > D > > /image, non-image? What do you mean by "copy multiple entries toG > > seaparate output files (diff. file-ID's)". I think that would apply ) > > only to non-image restore operations.  > E > Yes, so would I, but the HELP specifically mentions the combination  > /IMAGE/NOALIAS.      So use /IMAGE/NOALIAS.     > F > > > If the above is correct, I can see that one might sometimes want the E > > > /ALIAS behaviour and sometimes the /NOALIAS behaviour.  Neither  is ideal> > > > from my point of view, but presumably these are the only
 possibilities  > > > with /NOIMAGE. > >  > > Neither is ideal for what? > D > If I have a file with an alias, usually I would want the backup to haveC > the file with an alias, i.e. neither copy it twice nor ignore the  alias.    > I don't see why there would be a problem. You can check if the= operation worked using BACKUP/IMAGE/COMPARE and do it in both E directions if you're really that concerned about it. Also you can use G DIRECTORY (with no qualifiers!) to count all the files on each disk and  see if they match.   > = > > It means to use /alias only for v6.2 save sets and older. 
 Otherwise,E > > fuhgedaboutit. (forget about it). Actually, I have 6.2 on some of  my@ > > systems and *for image backups* with /NOALIAS it copies only primary F > > files from disk to tape but without any alias qual (but still withD > > /image) it for some reason copies *some* of the alias entries to tape. G > > Still, I'm not sure why you'd ever need to use /ALIAS for a restore G > > operation unless you are doing a selective or non-image restore and : > > need to use or find out the alias names, respectively. > F > I can see why, on non-image restore, one might want one behaviour or the , > other, but surely /IMAGE should be /IMAGE.    F If you're talking about that warning about incompleteness if you don'tF use /noalias, I have no clue. I can't think of a case where that wouldA happen. I'd think that non-image disk-to-disk operations would be  immune to such worries.    > > > > I don't think the alias qualifier makes any difference for disk-to-diskE > > image backups. If it does, I'd use /NOALIAS -- I mean, why recopy  the  > > files that have aliases? > > 7 > > What are you trying to do? What is your motivation?  > D > If I have a file with an alias, usually I would want the backup to haveC > the file with an alias, i.e. neither copy it twice nor ignore the  alias.     Not to worry, if you ask me.   > > > > I don't think the alias qualifier makes any difference for disk-to-diskE > > image backups. If it does, I'd use /NOALIAS -- I mean, why recopy  the  > > files that have aliases? > E > The HELP sounds like there are two alternatives: copy alias entries  into> > more than one output file (BAD, especially if the alias is a	 directory G > like [.syscommon]/[vms$common]) or IGNORE them (whatever that means).     D I don't recall this being in the help. When you copy to tape with anF image backup it is a waste of resources to copy alias entries. All theC needed information to reconstruct alias entries is contained in the C .DIR files. You will only get alias entries copied to more than one B file per file if you do a non-image restore from a save set exceptE those where /NOALIAS was either specified or in effect by default. So # don't worry about it! Be happy! :-)    > 7 > > What are you trying to do? What is your motivation?  > F > Simplicity itself: disk-to-disk, /IMAGE/NOSAVESET copy.  Just make aE > functional copy of the disk.  In this case, a system disk.  In this C > case, one wants neither duplicates of alias entries, nor does one  want > them to be ignored.     C You won't have either problem -- just don't use /ALIAS. Also, it is G easy to check by using DIRECTORY [*...] *with no qualifiers* (don't use A a DIR symbol that contains qualifiers or it will slow things down  considerably!).     E > I did /IMAGE and specified neither /ALIAS nor /NOALIAS.  That means  the E > default is /ALIAS, although "Compaq strongly recommends" specifying C > /ALIAS.  The output disk LOOKED OK, i.e. [.SYS0]SYSCOMMON.DIR and / > [000000]VMS$COMMON.DIR have the same file-ID.  > F > I think a) this is really confusing and b) not explained in the HELP why F > in the world /IMAGE should take this qualifier at all; after all, if one ; > makes an /IMAGE backup, then one wants an identical copy.     @ I agree it's confusing. There is a feedback link for comments on OpenVMS docs. Have you used it?    ------------------------------    Date: 11 Apr 2005 12:06:26 -0700$ From: "AEF" <spamsink2001@yahoo.com>& Subject: Re: (history of) BACKUP/ALIASB Message-ID: <1113246386.802560.87530@g14g2000cwa.googlegroups.com>  
 AEF wrote:1 > Phillip Helbig---remove CLOTHES to reply wrote: G > > In article <1113188775.488826.170280@z14g2000cwz.googlegroups.com>, * > > "AEF" <spamsink2001@yahoo.com> writes: > >  [...] @ > I don't see why there would be a problem. You can check if the? > operation worked using BACKUP/IMAGE/COMPARE and do it in both G > directions if you're really that concerned about it. Also you can use E > DIRECTORY (with no qualifiers!) to count all the files on each disk  and  > see if they match.    7 Uh, make that DIRECTORY/TOTAL with no other qualifiers.      [...] E > You won't have either problem -- just don't use /ALIAS. Also, it is E > easy to check by using DIRECTORY [*...] *with no qualifiers* (don't  use C > a DIR symbol that contains qualifiers or it will slow things down  > considerably!).     D Again, make that DIRECTORY/TOTAL with no other qualifiers. Sorry for	 the goof.    [...]    ------------------------------  + Date: Mon, 11 Apr 2005 22:28:47 +0000 (UTC) P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)& Subject: Re: (history of) BACKUP/ALIAS$ Message-ID: <d3etmv$imo$1@online.de>  G > > Yes, so would I, but the HELP specifically mentions the combination  > > /IMAGE/NOALIAS.  >  > So use /IMAGE/NOALIAS.  H What it actually does under what circumstances I'm not sure---I haven't F tried out all the combinations.  But the HELP says that /NOALIAS will C IGNORE alias file entries---I don't want them ignored, I want them  G copied, not as files, but as aliases.  I can't see why anyone doing an  $ image copy would want anything else.   @ > I don't see why there would be a problem. You can check if the? > operation worked using BACKUP/IMAGE/COMPARE and do it in both G > directions if you're really that concerned about it. Also you can use I > DIRECTORY (with no qualifiers!) to count all the files on each disk and  > see if they match.  B Apparently, it worked as "expected", even though I didn't specify A /NOALIAS.  In that case, why does "Compaq strongly recommend" it?   F > I don't recall this being in the help. When you copy to tape with anH > image backup it is a waste of resources to copy alias entries. All theE > needed information to reconstruct alias entries is contained in the F > ..DIR files. You will only get alias entries copied to more than oneD > file per file if you do a non-image restore from a save set exceptG > those where /NOALIAS was either specified or in effect by default. So % > don't worry about it! Be happy! :-)   I Maybe "ignore" should be changed to "processed correctly".  And maybe it  8 should be disallowed with /IMAGE, at least with /NOSAVE.   ------------------------------  % Date: Mon, 11 Apr 2005 19:59:03 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> & Subject: Re: (history of) BACKUP/ALIASB Message-ID: <1113263933.04b45633dd4aea42ddf1c3a9d3b04760@teranews>  / Phillip Helbig---remove CLOTHES to reply wrote: G > tried out all the combinations.  But the HELP says that /NOALIAS will D > IGNORE alias file entries---I don't want them ignored, I want themH > copied, not as files, but as aliases.  I can't see why anyone doing an& > image copy would want anything else.  3 The help text and documentation are very confusing.     C However, onsider that the alias is really just an extra record in a 8 directory file. (is there also an entry in indexf.sys ?)  F If backup gets the contents of the directory file, when that directory> file is restored, it will have a pointer to the original file.    H Perhaps the help text should simply state that /NOALIAS will not processF the CONTENTS of alias file in order to avoid the contents being backedD up multiple times.. This woudl make it easier to understand that the& alias entry itself would be preserved.   ------------------------------    Date: 11 Apr 2005 17:58:22 -0700$ From: "AEF" <spamsink2001@yahoo.com>& Subject: Re: (history of) BACKUP/ALIASC Message-ID: <1113267502.831703.137260@l41g2000cwc.googlegroups.com>    JF Mezei wrote: 1 > Phillip Helbig---remove CLOTHES to reply wrote: D > > tried out all the combinations.  But the HELP says that /NOALIAS willF > > IGNORE alias file entries---I don't want them ignored, I want themG > > copied, not as files, but as aliases.  I can't see why anyone doing  an( > > image copy would want anything else.    F What happens is that the data for alias files are ignored. The aliases ARE copied as aliases.   > 5 > The help text and documentation are very confusing.  >  > E > However, onsider that the alias is really just an extra record in a  > directory file.   G Correct. Using /IMAGE/ALIAS to build a save set will save an extra copy F of the file (in the save set) per alias entry for that file. This just wastes time.  F Normally you want BACKUP/IMAGE to get only one copy of each file (to a@ save set), including all the .DIR files. In a restore operation,B BACKUP/IMAGE then restores all the files, including the .DIR filesC (which contain all the alias entries if any). This will restore all  aliases.           >---o---<   E As I've said before, the only advantage I can see to copying the same G file repeatedly (to a save set), once for each of its aliases (and once D for the primary entry!), is that you can then use /SELECT to restoreD said file by any of its alias names. In some situations you may want: that, but it's going to cost you in extra processing time.    * > (is there also an entry in indexf.sys ?)   No.    > > > If backup gets the contents of the directory file, when that	 directory @ > file is restored, it will have a pointer to the original file.  A Correct, assuming /IMAGE is used during both the save and restore  operations.    >  > B > Perhaps the help text should simply state that /NOALIAS will not process A > the CONTENTS of alias file in order to avoid the contents being  backedF > up multiple times.. This woudl make it easier to understand that the( > alias entry itself would be preserved.  D OK. Even better: Explicitly state that skipping the alias files with+ /NOALIAS will not prevent a proper restore.    ------------------------------    Date: 11 Apr 2005 18:23:35 -0700$ From: "AEF" <spamsink2001@yahoo.com>& Subject: Re: (history of) BACKUP/ALIASB Message-ID: <1113269015.042171.66050@f14g2000cwb.googlegroups.com>  / Phillip Helbig---remove CLOTHES to reply wrote: E > Does anyone have a complete description of a) what the behaviour of E > /ALIAS is/was with each version of VMS (VAX and ALPHA, if there's a D > difference) and b) whether this corresponded to the description in HELP > of that same version of VMS? > F > I gather that /ALIAS "preserves the old behaviour", which apparentlyE > means that if there are multiple entries for a file (or directory),  thenG > they are treated equivalently, i.e. all are copied to SEPARATE output   G > files (different file-IDs).  With /NOALIAS, only the primary entry is    > copied, right? > F > If the above is correct, I can see that one might sometimes want theD > /ALIAS behaviour and sometimes the /NOALIAS behaviour.  Neither is ideal : > from my point of view, but presumably these are the only
 possibilities  > with /NOIMAGE. > - > What really confuses me, though, is /IMAGE.  > @ > The HELP for 7.2-1 and 7.3-1 is identical.  The 7.3-2 HELP for7 > BACKUP/ALIAS contains the following additional stuff:  > * >                                     NOTE > C >         Use the /ALIAS qualifier only when you are restoring very A >         old savesets (from OpenVMS Version 6.2 or earlier). The C >         current default behavior is correct in nearly every other  >         situation. > F > Also, the following is present in HELP for BACKUP/IMAGE in 7.2-1 and > 7.3-1, but gone in 7.3-2:  > G >      Specifying the /IMAGE qualifier without also specifying /NOALIAS D >      can result in incomplete disk or file restoration operations.F >      Therefore, Compaq strongly recommends that you specify /NOALIAS@ >      with /IMAGE when performing image mode backup operations. > ? > Did the behaviour actually change, or just the documentation?     : The behavior changed. Here is what I found in the 7.2 doc:   |||||  vvvvv   D Specifying the /IMAGE qualifier without also specifying /NOALIAS canD result in incomplete disk or file restoration operations. Therefore,E Compaq strongly recommends that you specify /NOALIAS with /IMAGE when ( performing image mode backup operations.     Note  P --------------------------------------------------------------------------------D If you do not specify /NOALIAS, the /ALIAS qualifier is activated by default.    D [*** OK, at this point I am still confused. Why is it recommended toD NOT use the default? However, the remainder below makes sense to me. ***]    D When you create a save set using /IMAGE and /ALIAS (explicitly or byG default) in OpenVMS Versions 6.2 and 7.0, BACKUP saves only one copy of E a file: either the alias file entry or the primary file entry. If the C primary file entry is not saved in the save set, subsequent restore C operations for this save set would restore the file using its alias G entry, causing the file header of the created file to contain the wrong 
 file name.  E If you use /NOALIAS to restore a volume from a save set created using > /ALIAS in Version 6.2 or 7.0, the volume might be incompletelyB restored. If BACKUP previously saved alias file entries instead ofD primary file entries, the alias file entries would be omitted from a volume restored using /NOALIAS.   C To safely restore a save set created using /ALIAS in Version 6.2 or ! 7.0, use the following procedure:   < Restore the save set using the /IMAGE and /ALIAS qualifiers.E Correct file entries by renaming the offending files, as shown in the  following example:    ? $ RENAME DISK:[000000]VMS$COMMON.DIR DISK:[000000]SYSCOMMON.DIR ? $ RENAME DISK:[000000]SYSCOMMON.DIR DISK:[000000]VMS$COMMON.DIR     = In this example, VMS$COMMON.DIR is the primary file entry and & SYSCOMMON.DIR is the alias file entry.  @ Starting with OpenVMS Version 7.1, if you specify /IMAGE without? /NOALIAS, BACKUP saves both the primary and alias file entries.    ^^^^^  |||||     ? I think what probably happend here is the following: In certain @ versions of BACKUP (6.2 and 7.0), /ALIAS wasn't doing what you'dA expect. According to the above, it would save aliased files under F either the primary OR the alias name. So upon restore if you specifiedE noalias you would lose the file altogether! I suspect that under such C circumstances that BACKUP was just walking the directory structure, D copying any alias file under whatever directory it first found it atF which point it would mark the file as saved in its "file list map madeC from INDEXF.SYS" and not copy data for that file-id if it was found : again later in the save operation. (This would explain howG SYSCOMMON.DIR supplanted VMS$COMMON.DIR as the primary name for a file, ) as SYSCOMMON comes first alphabetically.)   D Hence the need to use /ALIAS when restoring from save sets made with@ /ALIAS under VMS 6.2 or 7.0. The rest of the time you should use /NOALIAS. Okay?    > ? > It seems really bizarre that BACKUP/IMAGE would not produce a F > functionally equivalent copy of a disk.  By "functionally equivalentD > copy", I mean a copy in which non-primary file entries are neitherG > ignored nor copied as regular files (new file-ID on the output disk),   G > but rather in which non-primary entries on the source disk correspond  toE > non-primary entries on the target disk.  However, HELP before 7.3-2 " > certainly gives this impression. > G > Also, what does "restoring very old savesets" mean?  Does it refer to  a + > non-image restore or to an image restore.    It says 6.2 or older.    > @ > Let me phrase the question another way: If I do a disk-to-diskD > (non-saveset) backup, was there ever a time when specifying /IMAGE but D > specifying neither /ALIAS nor /NOALIAS resulted in something other than  ! > a functionally equivalent copy?   
 See above.   ------------------------------  # Date: Tue, 12 Apr 2005 04:51:55 GMT   From: John Santos <john@egh.com>& Subject: Re: (history of) BACKUP/ALIAS+ Message-ID: <LtI6e.10183$Zn3.6608@trnddc02>   
 AEF wrote: > JF Mezei wrote:  > 1 >>Phillip Helbig---remove CLOTHES to reply wrote:  >>C >>>tried out all the combinations.  But the HELP says that /NOALIAS  >  > will > E >>>IGNORE alias file entries---I don't want them ignored, I want them F >>>copied, not as files, but as aliases.  I can't see why anyone doing >  > an > ' >>>image copy would want anything else.  >  >  > H > What happens is that the data for alias files are ignored. The aliases > ARE copied as aliases. >   D It helps to remember that directories are *files*, and that an alias5 is an entry in a directory file (as you imply below.)   B So ignoring the alias file *is* what you want it to do.  The aliasC directory entry (in the directory file) will get backed up with the A directory file anyway.  (Unless the directory itself is an alias, E which just pushes things one level up the directory tree, so restores  still work okay.)    > 5 >>The help text and documentation are very confusing.  >> >>E >>However, onsider that the alias is really just an extra record in a  >>directory file.  >  > I > Correct. Using /IMAGE/ALIAS to build a save set will save an extra copy H > of the file (in the save set) per alias entry for that file. This just > wastes time. > H > Normally you want BACKUP/IMAGE to get only one copy of each file (to aB > save set), including all the .DIR files. In a restore operation,D > BACKUP/IMAGE then restores all the files, including the .DIR filesE > (which contain all the alias entries if any). This will restore all 
 > aliases. >  >         >---o---<A > G > As I've said before, the only advantage I can see to copying the same I > file repeatedly (to a save set), once for each of its aliases (and onceyF > for the primary entry!), is that you can then use /SELECT to restoreF > said file by any of its alias names. In some situations you may want< > that, but it's going to cost you in extra processing time. >  >  > * >>(is there also an entry in indexf.sys ?) >  >  > No.v >  > > >>If backup gets the contents of the directory file, when that >  > directorya > @ >>file is restored, it will have a pointer to the original file. >  > C > Correct, assuming /IMAGE is used during both the save and restore 
 > operations.S >  >  >>B >>Perhaps the help text should simply state that /NOALIAS will not > 	 > process  > A >>the CONTENTS of alias file in order to avoid the contents beingo >  > backed > F >>up multiple times.. This woudl make it easier to understand that the( >>alias entry itself would be preserved. >  > F > OK. Even better: Explicitly state that skipping the alias files with- > /NOALIAS will not prevent a proper restore.m  @ Yes, because there are 3 things associated with any file: 1) theA CONTENTS, 2) the FILE HEADER (in indexf.sys) and 3) the DIRECTORY 5 entry (entries for an aliased file) that point to it.a  ? The directory entries get saved and restored as contents of the D directory .DIR file, independently of the file itself or its header.@ (This is why an image backup preserves lost files, which have no directory entries at all.)  D If HELP just said /NOALIAS doesn't process the contents of the file,A as proposed above, then it leaves the FILE HEADER in an ambiguousQC situation.  "Ignores the file" implies it ignores both the CONTENTS ? and the HEADER, which reflects the real situation.  (But if you ? don't think about the fact that directory entries are stored inq> separate .DIR files, you start wondering about what happens toB them, which I think is what started this thread in the 1st place!)  ; BTW, the /NOBACKUP attribute causes backup to save the FILEn> HEADER but not the CONTENTS.  (And again the directory entries= get saved in the .DIR file.)  Anyone know what happens if you " set /NOBACKUP on a directory file?       -- 4 John Santos  Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------  % Date: Tue, 12 Apr 2005 01:02:42 -0400R- From: JF Mezei <jfmezei.spamnot@teksavvy.com>i& Subject: Re: (history of) BACKUP/ALIASB Message-ID: <1113282158.f9f64de369e466a72e842acfff2ba649@teranews>  % Another suggestion for the help text:f  H Should the help/documentation state that /NOLIAS should only be used forD /IMAGE backups and that if used for non /IMAGE backups, not all fileF contents in a directory targetted by the backup would be copied to the	 saveset ?f   ------------------------------  % Date: Sun, 10 Apr 2005 23:27:49 -06002( From: "r.m" <nospam@rmendoza.copper.net> Subject: 600au and mmovw- Message-ID: <425a0b51$1_3@newsfeed.slurp.net>a  D I am trying to get mmov running on a 600au.  After installing 8.2 I B installed MMOV 2.2, and added to the sys$user_config.dat file the * following, like the release notes mention:   device  = "ES1888 Sound Card"     name    = AU     driver  = MMOV$ESSDRIVERn    adapter = XBUS-    id      = ES1888-
 end_device  F rebooted and nothing, the mmov server is running but no au* device is B created, can't run any of the audio utils obviously, and the logs @ indicate no errors.  I tried taking all of the devices that use G MSBDRIVER out of sys$user_config.dat since the release notes mention a t4 conflict if the are both enabled but it didn't help.  &  From SRM the ES1888 device is listed.  6 Anybody have any hints and advice to get mmov working?   Rene.f   ------------------------------    Date: 10 Apr 2005 23:14:18 -0700; From: "johnhreinhardt@yahoo.com" <johnhreinhardt@yahoo.com>p Subject: Re: 600au and mmoveB Message-ID: <1113200058.129707.58570@f14g2000cwb.googlegroups.com>  
 r.m wrote:E > I am trying to get mmov running on a 600au.  After installing 8.2 IyC > installed MMOV 2.2, and added to the sys$user_config.dat file thei  G V8.2 requires a newer version of MMOV which AFAIK has not been releasedi yet.  See this thread....rt http://groups-beta.google.com/group/comp.os.vms/browse_frm/thread/dc6996e631d8ff7e/11fa7d7a7c508c38#11fa7d7a7c508c38   ------------------------------  % Date: Sun, 10 Apr 2005 19:42:32 +0200E- From: Didier Morandi <prenom.nom@freesurf.fr>i; Subject: Aging Alpha Processor Gets Companion Product Boost 4 Message-ID: <4259658d$0$22162$626a14ce@news.free.fr>  2 Aging Alpha Processor Gets Companion Product Boost Information Week 7-APR-2005   S http://www.informationweek.com/story/showArticle.jhtml?articleID=160502090&tid=5978   H With the days of the 64-bit Alpha processor seemingly numbered, Nemonix B Engineering is stepping into the breach with a product that works  alongside the aging CPUs.  By W. David Gardnerc TechWeb.como  H With the days of the 64-bit Alpha processor seemingly numbered with but I 700,000 users, Nemonix Engineering is stepping into the breech as one of pH the few firms to field a product that works alongside the legendary but  no longer well supported CPU.   F Nemonix has unveiled a dual Gigabit Ethernet controller for Alpha, as B the first entry in a planned program of continued support for the D processor. Daniel Bumbarger, Nemonix' founder, said he believes his ? company is the sole firm developing new products for the Alpha.-  I "This is the first of several products we want to bring to market," said eG Rich Williams, the firm's vice president of strategic alliances, in an oD interview. "We started by supporting the VAX and that's been a good F market for us. We expect the same type of market is developing around  the Alpha."o  G The Alpha has had a long and circuitous march. Developed over a decade mG ago by the Digital Equipment Corp. as its flagship for the future, the sB machine was initially hampered by a lack of native mode software. : Digital was subsequently sold to Compaq Computer and then F Hewlett-Packard acquired Compaq and, along with it, the Alpha. But HP E already had the 64-bit Itanium, which it developed with Intel. Thus, r Alpha languished.i  G Williams noted that HP is still selling new Alphas, but the computer's eH manufacturing line is scheduled to go dead in 2006. HP will support the G family through 2011. Nemonix plans to design an array of products that o; will keep the Alpha in operation well beyond that, he said.n  E "We are ardent supporters of OpenVMS," Williams said noting that the iA robust and stable operating system is still one of the strongest fI features of the Alpha. VMS had a logical progression in Digital, growing  - almost organically from the VAX to the Alpha.e  I The new Nemonix controller was developed in collaboration with HP. Prior ?I to its release, users of AlphaServer DS, ES, and GS systems were limited  H to 100Mbps of built-in network capability as well as restricted network A expansion capacity, Nemonix said. The controller has two Gigabit y: Ethernet ports on a single plug-and-play 64-bit PCIX card.  F Priced at $899, the controller also supports HP OpenVMS Version 7.3-2 C Alpha and above for AlphaServers, HP OpenVMS Cluster control, UCX,   TCP/IP, Multinet and DECnet.  G Moving forward, Nemonix believes it can build an ongoing business over fE what will soon be a legacy processor. "VAX customers have Alphas and  H they want to keep them," said Williams. "There's a lot of customers out  there for us."     FYI.   D. -- u,        Didier MORANDI - Expert informaticien0   13 chemin du Gu, 1213 Petit-Lancy (GE) Suisse0 Tl. : +33(0)6 7983 6418 ~ www.didiermorandi.com   ------------------------------  % Date: Mon, 11 Apr 2005 01:36:08 +0200 & From: Paul Sture <paul.sture@decus.ch>? Subject: Re: Aging Alpha Processor Gets Companion Product Boost2, Message-ID: <3btrj7F6iapc0U1@individual.net>   Didier Morandi wrote:u  4 > Aging Alpha Processor Gets Companion Product Boost > Information Week 7-APR-2005  > V > http://www.informationweek.com/story/showArticle.jhtml?articleID=160502090&tid=5978  >  >   G Sorry, Didier, not criticising you, but this is a somewhat dodgy piece h of journalism here...e  J > With the days of the 64-bit Alpha processor seemingly numbered, Nemonix C > Engineering is stepping into the breach with a product that works.*                                     ^^^^^^ breach n.* 1.  a.  	An opening, a tear, or a rupture.:      b.  	A gap or rift, especially in or as if in a solid;                  structure such as a dike or fortification.k   OK so far...   > alongside the aging CPUs.o > By W. David Gardnero
 > TechWeb.com  > J > With the days of the 64-bit Alpha processor seemingly numbered with but J > 700,000 users, Nemonix Engineering is stepping into the breech as one ofA                                                            ^^^^^^h breech n.= 1.  	The lower rear portion of the human trunk; the buttocks.i- 2.  	a.  	 A breech presentation or delivery.a& 	b.  	 A fetus in breech presentation.   Oops...h  J > the few firms to field a product that works alongside the legendary but  > no longer well supported CPU.r >    <snip>  K > The new Nemonix controller was developed in collaboration with HP. Prior vK > to its release, users of AlphaServer DS, ES, and GS systems were limited dJ > to 100Mbps of built-in network capability as well as restricted network C > expansion capacity, Nemonix said. The controller has two Gigabit o< > Ethernet ports on a single plug-and-play 64-bit PCIX card. >   G Eh? So what the hell were those gigabit cards I was using back in 2001?   D http://h18000.www1.hp.com/products/quickspecs/10479_na/10479_na.HTML  ) "Gigabit Ethernet NICs for Alpha Systems"   H > Priced at $899, the controller also supports HP OpenVMS Version 7.3-2 E > Alpha and above for AlphaServers, HP OpenVMS Cluster control, UCX, e > TCP/IP, Multinet and DECnet. > I > Moving forward, Nemonix believes it can build an ongoing business over 2G > what will soon be a legacy processor. "VAX customers have Alphas and eJ > they want to keep them," said Williams. "There's a lot of customers out  > there for us." > E Oh please, gimme a break. There are a lot of Alpha customers with no >' VAXes. Is this crud journalism or what?:   ------------------------------  # Date: Mon, 11 Apr 2005 19:10:14 GMT # From: hoff@hp.nospam (Hoff Hoffman)S@ Subject: RE: Broken VAXstation 4000 VLC (was Re: Broken vax4000)1 Message-ID: <qYz6e.3481$4D.1599@news.cpqcorp.net>)  M In article <42542E53.C8E2985C@mist.com>, GreyCloud <cumulus@mist.com> writes:  :Hoff Hoffman wrote:  < :Getting the appropriate connector is going to be a problem.  C   If you are careful and if friction is currently your friend, use  C   a standard modular jack sans the key.  But getting an adapter foriB   the serial console (FAQ has parts) or getting a bag of MMJs and :   the appropriate die and crimping tools is the way to go.  9 :The backside status leds change state during startup andt :eventually are not lit up.e :Does this mean anything??  ?   The console output means a whole lot more -- the LEDs do haveoA   meaning and I have a listing of those around somewhere, but I'dgA   tend to expect the codes to mean you should look at the consolerB   output and see what that indicates.  The LEDs are indicators for   low-level hardware failures.  = :I also understand that there is onboard audio but no speaker*8 :connected to it.  It is said that the startup self test, :chirps upon successful completion of tests.  B   My first interest and my first troubleshooting target here wouldB   be the console output.  Not the speaker, and not the LEDs.  Yes,@   I know you don't have the adapter for the console serial line.?   Your other option is to use the graphics console display, andhA   flipping S3 to send your console output that way is a potentialaC   option -- having the serial console enabled is, however, what I'deC   generally chose for management and even for operational purposes.o  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: Sun, 10 Apr 2005 14:53:20 GMTa# From: Beach Runner <bob@nospam.com>tU Subject: Re: Configuring multi-port NIC on DS10 with DECNET-Plus and TCPIP 5.3 5.35.3s: Message-ID: <A5b6e.27793$vd.25986@tornado.tampabay.rr.com>   Grealy, Patrick J wrote: > Hi,oF > We have OpenVMS 7.3-1, cluster with two DS10s, running TCPIP 5.3 andF > DECNET-Plus. When the system was installed last year, each DS10 cameJ > with dual-port network card. We configured TCPIP with only one interfaceH > and one IP address on each machine but we had all four ports connectedC > to our network. I assumed the second port on each machine was foroH > redundancy and not being unused. However, that is not the case and nowH > our network security folks want to know the function of each port. HowJ > can I examine how each network card is configured or, at the very least,J > obtain the MAC addresses? Does each card have two separate addresses? DoE > I need to shutdown each box and do "show config" at the >>> prompt?-	 > Thanks,- > Pat G.   ------------------------------    Date: 11 Apr 2005 07:51:18 -0700 From: tiina.ayris@abagri.com( Subject: Re: DCPS 2.3, %DCPS-F-STREAMUSEC Message-ID: <1113231078.564778.188810@z14g2000cwz.googlegroups.com>E  D Thanks, Paul, I've redefined DCPS$MAX_STREAMS to 1 and restarted all6 dcps printers. And hey presto, they stop&start nicely. Thanks again for your help.m Tiinac   ------------------------------  % Date: Sun, 10 Apr 2005 22:33:28 +0200A2 From: Gautier Write-only <gautier@fakeaddress.nil>= Subject: Re: Finding The Right Path For Your VMS Applications / Message-ID: <42598D98.D243176C@fakeaddress.nil>p  J > >> (4) PASCAL - We did the data controller for Australia (point to pointH > >> communications) - Rdb RDML, PASCAL, X25 and X29 (using AST's) - DECJ > >> PASCAL is simply incompatible with every other pascal - so we have to   Larry Kilgallen:  H > In my experience, _every_ Pascal is different from every other Pascal.H > They all took different routes before ISO standard Pascal brought some > of the missing pieces.  N True - cf some reflexions about the fragmentation of Pascal in dialects there:4 http://homepage.sunrise.ch/mysunrise/gdm/pascada.htm  D > But any language with support for RMS indexed files is going to beF > different from an implementation on a non-VMS platform.  This is notG > a problem until the programmer decides to use those features that therE > operating system and the language have conspired to make available.  > $ > >> write a PASCAL to C translator.L > > I suspect the translated code doesn't look as that which might have beenN > > written, by a human.  So how do you debug the code in the new environment, > F > The first step would be to run the full coverage test suite the shop9 > has been maintaining all along for the old language :-)u > < > > what does the source tree look like, is it still Pascal? > I > There is a company that will do Ada to C translation, but they strongly I > point out the resultant C is _not_ readily maintainable and the suggest ; > keeping the source as Ada and re-translating for changes.   O BTW, a good solution for Pascal sources is to follow the language evolution and A translate them to Ada; you can get rid of the Pascal sources oncerG the Ada code is running well. As a gift you end in a STANDARD language. ) You can download a free translator there:g  8 http://homepage.sunrise.ch/mysunrise/gdm/gsoft.htm#p2ada  > ______________________________________________________________> Gautier     --     http://www.mysunrise.ch/users/gdm/index.htm> Ada programming -- http://www.mysunrise.ch/users/gdm/gsoft.htm  8 NB: For a direct answer, e-mail address on the Web site!   ------------------------------  % Date: Mon, 11 Apr 2005 01:59:05 +0200 & From: Paul Sture <paul.sture@decus.ch>= Subject: Re: Finding The Right Path For Your VMS Applicationsh, Message-ID: <3btstuF6j1cuoU1@individual.net>   Gautier Write-only wrote:i  I >>>>(4) PASCAL - We did the data controller for Australia (point to pointoG >>>>communications) - Rdb RDML, PASCAL, X25 and X29 (using AST's) - DEChI >>>>PASCAL is simply incompatible with every other pascal - so we have tol >  >  > Larry Kilgallen: >  > H >>In my experience, _every_ Pascal is different from every other Pascal.H >>They all took different routes before ISO standard Pascal brought some >>of the missing pieces. >  > P > True - cf some reflexions about the fragmentation of Pascal in dialects there:6 > http://homepage.sunrise.ch/mysunrise/gdm/pascada.htm >  > D >>But any language with support for RMS indexed files is going to beF >>different from an implementation on a non-VMS platform.  This is notG >>a problem until the programmer decides to use those features that the E >>operating system and the language have conspired to make available.e >> >># >>>>write a PASCAL to C translator.y >>> K >>>I suspect the translated code doesn't look as that which might have beenpM >>>written, by a human.  So how do you debug the code in the new environment,  >>F >>The first step would be to run the full coverage test suite the shop9 >>has been maintaining all along for the old language :-)  >> >>; >>>what does the source tree look like, is it still Pascal?  >>I >>There is a company that will do Ada to C translation, but they strongly I >>point out the resultant C is _not_ readily maintainable and the suggestA; >>keeping the source as Ada and re-translating for changes.w >  > Q > BTW, a good solution for Pascal sources is to follow the language evolution andsC > translate them to Ada; you can get rid of the Pascal sources onceLI > the Ada code is running well. As a gift you end in a STANDARD language. + > You can download a free translator there:T > : > http://homepage.sunrise.ch/mysunrise/gdm/gsoft.htm#p2ada > @ > ______________________________________________________________@ > Gautier     --     http://www.mysunrise.ch/users/gdm/index.htm@ > Ada programming -- http://www.mysunrise.ch/users/gdm/gsoft.htm > : > NB: For a direct answer, e-mail address on the Web site!  A A very useful looking site thanks. I wish I'd found it before :-)    ------------------------------  % Date: Sun, 10 Apr 2005 00:19:33 -0700 - From: Jake Hamby <jhamby IS AT pobox DOT com>n> Subject: Re: Frustration!  EB64+ too old to run OpenVMS 7.3-1?8 Message-ID: <nokh51d3vofk8uo09kaglmf3oqe7bg7a3o@4ax.com>  6 On Sat, 09 Apr 2005 18:47:39 -0400, "John E. Malmberg" <wb8tyw@qsl.network> wrote:1 >8E >OpenVMS 7.3-1 is old of course.  OpenVMS 8.2 is the current release.2  F Yes, and it would be nice if I could download a copy of OpenVMS 8.2 toC use with my hobbyist license, but I can't, so I'm stuck with 7.3-1.O   Thanks to all for your replies.o   -Jake'   ------------------------------  # Date: Mon, 11 Apr 2005 18:57:56 GMTo# From: hoff@hp.nospam (Hoff Hoffman)o> Subject: Re: Frustration!  EB64+ too old to run OpenVMS 7.3-1?0 Message-ID: <UMz6e.3478$4D.727@news.cpqcorp.net>  w In article <d301m2$gc7$1@online.de>, helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) writes:oG :In article <3Yy4e.2985$vH.1818@news.cpqcorp.net>, hoff@hp.nospam (Hoff  :Hoffman) writes:  : D :>   I would personally aim for an AlphaStation series, including anC :>   XP900, XP1000 or equivalent box.  I would not acquire an Alpha-D :>   system with less than an EV56 processor, and I would prefer and7 :>   would look for an EV6-class processor, or better. S : G :Why?  Obviously, these are more powerful machines.  Assuming, however,@C :that one doesn't need the power, is there a reason to say "EV56 or I :later, preferably EV6 or later"?  One such reason would be that VMS 8.2 tG :won't support older ALPHAs (a few were dropped in 7.3-2); any idea if e :this will be the case?   D   OpenVMS Alpha V8.2 shipped some time ago (well, in my universe :-)D   -- I and others are busy on future releases), and the SPD is here:  H   http://h18000.www1.hp.com/products/quickspecs/12156_div/12156_div.HTML  C   The SPD contains the lists of systems that are supported, and thetA   planned changes in support.  I'm not aware of any Alpha systems C   where support was dropped in OpenVMS Alpha V8.2, off-hand.  There D   are five single-board computers and five other older Alpha systemsD   that will last see support on V8.2, but AFAIK there is no officialC   blanket requirement for any particular Alpha microprocessor core.C  E   The comments around the preferences are my own.  I would not choose.D   to acquire an Alpha system with less than an EV56 processor, and IE   would prefer and would look for an EV6-class processor, or better.  D   For some applications, a 150 MHz 21064 EV4 box would be just fine.   But not for my typical usage.o  . :In particular, I have (at home) EV4 and EV45 D :systems (and lots of VAXes); it would be nice to have at least 8.2 E :supported on them (as a hobbyist, I am not concerned with "official aH :support" in the sense of help if something goes wrong, but rather with 1 :being able to expect the configuration to work).S  G   There are tools you may/will want to use that can effectively require0E   access to byte-word.  Mozilla is one, and there are other examples.tE   You most certainly can continue to run on the older boxes, but such3C   can be very slow.  I was happily running an AlphaStation 255 long G   beyond its useful life -- until I ran into several of these byte-word =   applications.  I ended up scrounging up a system upgrade.     G   There is also presently a US$2K special on an Integrity rx1620 series H   box, including a training class.  Or is it a training class for US$2K,H   including an Integrity rx1620?  (This tends to hold down the prices of   Alpha systems, of course.)  H   There is at least one third-party product that assumes EV56, and thereG   are OpenVMS device drivers that assume EV6-class bus addressing, too.wH   This means that you can encounter some products and some devices which*   will effectively require newer hardware.  E   There are also newer buses and such available on the newer systems. J   You can find IDE/ATAPI connections on many of these boxes, for instance.G   (I have an AlphaStation XP1000 with all manner of odd and unsupportede7   devices hanging off the IDE/ATAPI bus, for instance.)a  ;   There is no presently OpenVMS VAX V8.2 release available.1  N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faqoN  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.comi   ------------------------------    Date: 10 Apr 2005 08:11:39 -0700; From: "johnhreinhardt@yahoo.com" <johnhreinhardt@yahoo.com>e= Subject: Re: Frustration! EB64+ too old to run OpenVMS 7.3-1? C Message-ID: <1113145899.184362.234010@l41g2000cwc.googlegroups.com>o   Jake Hamby wrote: D > On Sun, 10 Apr 2005 00:19:33 -0700, Jake Hamby <jhamby IS AT pobox DOT/
 > com> wrote:b >dE > I'm going to try to find a reseller to purchase a copy if it is not ? > ridiculously expensive.  If it is under $120 then it may be au9 > worthwhile investment in terms of avoiding frustration.  >e > -Jakec  E Prepare your self for sticker shock.  IIRC, the OS distribution alonetD is about $350 and the latest SPL is about $1050.  Since the HobbyistF License allows you to get your binaries from any source, your best betF is to post your name, contact info and approximate geographic location> (or whatever you feel comfortable posting) with a plea for theF distributions you want.  If you're lucky, somebody local will have one= that you can borrow and copy.  Otherwise you may have to maketG arrangements to e-mail or download the software.  I got lucky and had ag- nearby HP VMS Ambassador lend me his to copy..     HTH,     John H. Reinhardt    ------------------------------  % Date: Sun, 10 Apr 2005 18:55:08 -0700e- From: Jake Hamby <jhamby IS AT pobox DOT com>f= Subject: Re: Frustration! EB64+ too old to run OpenVMS 7.3-1?n8 Message-ID: <h4mj51tmdtfp3rhhvgk38tasdblsg2r58v@4ax.com>  9 On 10 Apr 2005 08:11:39 -0700, "johnhreinhardt@yahoo.com" ! <johnhreinhardt@yahoo.com> wrote:a  F >Prepare your self for sticker shock.  IIRC, the OS distribution aloneE >is about $350 and the latest SPL is about $1050.  Since the Hobbyist.G >License allows you to get your binaries from any source, your best bet G >is to post your name, contact info and approximate geographic location-? >(or whatever you feel comfortable posting) with a plea for the0G >distributions you want.  If you're lucky, somebody local will have one9> >that you can borrow and copy.  Otherwise you may have to makeH >arrangements to e-mail or download the software.  I got lucky and had a. >nearby HP VMS Ambassador lend me his to copy.  B Okay, I'm in the Los Angeles area.  If anyone can help me out, I'dE sincerely appreciate it.  E-Mail me at jhamby AT pobox DOT com if youa$ can help me out.  Thanks in advance!   -JakeI   ------------------------------  # Date: Mon, 11 Apr 2005 18:28:02 GMT # From: hoff@hp.nospam (Hoff Hoffman)i= Subject: Re: High File Watermarking question for Hoff Hoffman 1 Message-ID: <Skz6e.3473$4D.2911@news.cpqcorp.net>l  Z In article <BE787C79.B0C0%roktsci@comcast.net>, Jeff Cameron <roktsci@comcast.net> writes:  =   Relevent OpenVMS source listings module: [SYS]SYSACPFDT.LISh  D :On a disk with High File Watermarking enabled, blocks are zeroed on :allocation/extent.   I   When shared, yes.  When non-shared/SQO, usually no.  (There are variousrI   criteria which must be met for the non-shared/SQO HWM I/O optimizationsiH   to be permitted, and OpenVMS looks for these -- if all of the criteriaH   are not met, OpenVMS switches over into -- for lack of a specific term8   for the condition -- the shared HWM operational mode.)  L :In the case of sequential files, the bytes between the logical and physicalD :EOF are also zeroed when the logical file mark location is written.  J   When shared, yes, blocks are overwritten with the security erase patternJ   (erased) when allocated.  When non-shared/SQO, no -- where there is someI   control over the file access, OpenVMS optimizes how it manages the HWM.lH   (This is an optimization, as this avoids extra I/O in support of HWM.)  J   When non-shared, blocks are overwritten when the write is beyond the HWMG   and when no application data overwrite operation is pending; when theu3   disk storage could be exposed to disk scavenging.e  H   As a general rule, the EOF isn't particularly relevent nor interestingJ   to the whole HWM implementation.  The HWM (and a New HWM value, when theI   pattern erasure is in progress) is maintained separately.   Whether theoI   file is open non-shared sequential-access only (SQO), is, however, veryn   interesting to OpenVMS.-  H   Write I/O operations and (when shared) file allocations adjust the HWM%   upward, as appropriate.  Obviously.a  C   In SQO operations, read I/O operations between HWM and EOF get a  J   synthesized overwritten buffer, whether or not the data has been writtenG   by the application.  (In shared operations, the contents have already/   been overwritten.)  -   Reads past EOF get an EOF error, of course.d  K   There are cases when HWM can and does get expensive.  One classic exampleeJ   is a write to a record a very long ways beyond the former last record inK   in a relative file -- HWM has to write the erasure pattern over all bytessI   between the old HWM and the new HWM, and stall any I/Os between the oldi9   and the new pending completion of the security erasure.a   	--   L   The overwrite operation might be with zeroes, or it might not.  Please seeG   the $erapat system service for related details on the pattern erasurenJ   operations.  Please don't assume you'll find zeros in the erased area of   a file, in other words.N   	--   H   This particular code is subject to one of the more famous "hairy code"=   source code comments lurking anywhere within OpenVMS, FWIW.t    N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faqNN  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.comf   ------------------------------  % Date: Mon, 11 Apr 2005 15:29:28 -0400n( From: Bill Todd <billtodd@metrocast.net>= Subject: Re: High File Watermarking question for Hoff Hoffmant= Message-ID: <ltqdndXKKNGETcffRVn-sw@metrocastcablevision.com>e   Hoff Hoffman wrote:e   ...   M >   There are cases when HWM can and does get expensive.  One classic examplenL >   is a write to a record a very long ways beyond the former last record inM >   in a relative file -- HWM has to write the erasure pattern over all byteslK >   between the old HWM and the new HWM, and stall any I/Os between the oldi; >   and the new pending completion of the security erasure.a  F And then RMS has to write most of the same blocks again to format the H relative file record slot control bits (I suppose if the slots are very F large RMS can get away with writing only the first disk block of each D slot, but whether it bothers with this optimization I have no idea).  F If the erasure pattern were guaranteed to leave the slot control byte G the way RMS would like to see it for a never-occupied slot, that would uD be convenient - and allowing specification on a per-file basis of a A 'fill character' to be used in such cases should not be all that rE difficult to support (not that the popularity of Relative files that qD actually encounter this as a problem would necessarily justify even H minor effort in this area).  But a more complete approach would combine E this with sparse file support - or at least track such never-written kI areas within a file such that they could be handled similarly to the way bI reads beyond the HWM are handled (though once you've done that, it's not sC clear why you wouldn't treat sparseness as well, since most of the eI overhead would already have been incurred - and in either case a minimum rB 'hole' granularity could be defined to balance fill-in-the-blocks , overhead against index file space overhead).  ? Not that I'm holding my breath, mind you.  Just an observation.n   - bill   ------------------------------  % Date: Mon, 11 Apr 2005 20:18:54 -0500-2 From: David J Dachtera <djesys.nospam@comcast.net>$ Subject: Re: loging in and out user?+ Message-ID: <425B21FE.B1217216@comcast.net>S   Craig Marburger wrote: > K > I have not seen any login or outs.  Do I need to change a setting here orm > not? >  > MDAXP > SHOW AUDIT/ALL > List of audit journals:n$ >   Journal name:           SECURITY2 >   Journal owner:          (system audit journal)E >   Destination:            SYS$COMMON:[SYSMGR]SECURITY.AUDIT$JOURNALa# >   Monitoring:             enabled M >     Warning thresholds,   Block count:    100     Duration:    2 00:00:00.0sM >     Action thresholds,    Block count:     25     Duration:    0 00:30:00.0a > + > Security auditing server characteristics:  >   Database version:       4.4s) >   Backlog (total):        100, 200, 300   >   Backlog (process):      5, 2  >   Server processing intervals:) >     Archive flush:        0 00:01:00.00r) >     Journal flush:        0 00:05:00.00t) >     Resource scan:        0 00:05:00.00e5 >   Final resource action:  purge oldest audit events  > ! > Security archiving information:   >   Archiving events:       none >   Archive destination: > + > System security alarms currently disabledh > / > System security audits currently enabled for:t >   ACL  >   Authorization. >   Connection >   Audit:         illformed7 >   Breakin:       dialup,local,remote,network,detachedl >   Login:         local,remotet  E Try adding "network" here. TELNET logins sometimes show up as networkp logins.   H >   Logfailure:    batch,dialup,local,remote,network,subprocess,detached	 > MDAXP >P  H Note also that if users are connecting to a service - such as a databaseE or other application - on your VMS system, such logins are beyond the # scope of the Security Audit server.    -- f David J Dachtera dba DJE Systemso http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page:o" http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/a  " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/s   Coming soon:& Unofficial OpenVMS Marketing Home Page   ------------------------------  % Date: Tue, 12 Apr 2005 00:42:57 +0200b- From: Alex van Denzel <vandenzel@hotmail.com>w) Subject: Re: Multiprocessor Microvax II ?e6 Message-ID: <425afd71$0$2277$dbd41001@news.wanadoo.nl>   prep@prep.synonet.com wrote:  B >>I stumbled across this a while back.  IIRC, you could have up to >>four KA630s in a system.  : No-one tried to patch simh-vax with more than one cpu yet?   -- Alex.S   ------------------------------  # Date: Mon, 11 Apr 2005 23:25:13 GMT>& From: hoffman@hp.nospam (Hoff Hoffman)) Subject: Re: Multiprocessor Microvax II ? 2 Message-ID: <tHD6e.3528$851.2446@news.cpqcorp.net>  d In article <42570858.5020907@applied-synergy.com>, Chris Scheers <chris@applied-synergy.com> writes:  -   re: Multiprocessor MicroVAX II KA630 series     H   I have previously posted a reply or two on this topic, but that was a G   few years ago now.  I've attached (most of) two of the semi-relevent e   postings below.a   	--   J   To recap, KA630 was capable of a primary and three secondary processors H   -- each of the secondaries was entirely fed, watered and cared for by F   the primary, and the secondaries could act largely as Q-bus compute 3   peripherals or intelligent co-processors or such.   F   The KA640 was nicer here, as it had more memory, and it had built-inI   network and storage I/O.  It was still significant work, and I am awareeI   of no one (outside of what was then known as DIGITAL) that had created i7   the necessary system software for this configuration.s  G   OpenVMS VAX Symmetric Multiprocessing (SMP) does not support this, ashG   the hardware configuration is not Symmetric -- the secondaries do notpE   have any control over Q-bus activities and such, and are limited tooG   interrupting the primary when attention or I/O is required.  (In some F   ways, this multi-processor MicroVAX configuration is remaniscent of C   Asymmetric Multiprocessing (ASMP); akin to the VAX-11/782 series.-D   There was a family of multiprocessor VAXstation systems, but thoseF   were not widely seen in the field.  I'll leave the identification ofH   the two models of the SMP-capable and Q-bus-capable family as a triviaH   question.  There was a second and very rare BI-based VAXstation, but IE   don't know if anyone ever configured and ran it as a dual.  Anothero   trivia question.)   J   It is certainly conceivable that a customized system image be downloadedG   into a secondary processor (via NI, or the console's boot-ROM-seeking5E   bootstrap and the shared memory, or otherwise) and to then start up0I   processing for the OpenVMS system -- conceivably, you could even create G   and load a version of Linux or NetBSD into a secondary, assuming you 2H   could find an appropriate port and were willing to write some code forH   both the port and for OpenVMS -- the former to ring up the primary forG   most or all I/O, and the latter to service the requests.  But I don'tnF   know of any customers that have ever implemented or even tried this.    N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faqfN  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.com.     	--d  3 From: hoff...@xdelta.enet.dec.com (Stephen Hoffman)e Newsgroups: comp.sys.dec" Subject: Re: MVII & multiple CPU's Date: 20 Jul 1994 15:21:47 GMT+ Organization: Digital Equipment Corporationj	 Lines: 510 Distribution: world-( Message-ID: <30jfeb$1nn@jac.zko.dec.com>, References: <30i44s$4us@newserv.ksu.ksu.edu>7 Reply-To: hoff...@xdelta.enet.dec.com (Stephen Hoffman)  NNTP-Posting-Host: XDELTAd X-Newsreader: mxrn 6.18-16      E   I haven't tried this combination, nor would I recommend it, nor cannD   I say that it works, nor can I predict if you will damage yourself0   and/or various modules.  "Caveat Configurator"  ; In article <30i44s$...@newserv.ksu.ksu.edu>, electro@godiva- (Eric L Patterson) writes:  J |>What are the boards involved in installing more than one processer in a  |>MVII  I   Assuming you mean plugging a second KA630 processor into the backplane,2F   you will have to reset the second KA630 to a non-arbiter (and to theE   first of three alternate CSR/IPCR addresses), and plug it in to theyH   Q-bus.  The arbiter IPCR is at 20001F40, and the three auxillaries areJ   located at 1F42, 44, and 46.  (These addresses are for the KA655 system;I   I think these also hold for the KA630. On the KA655 module, the arbiterWB   selection is via the 20 pin console config & display connector.)  D   The memory interconnection will be a problem, as the KA630 has oneC   megabyte on-board and it expects both itself and the memory to bepB   sitting on Q22/CD slots, and it doesn't expect to share the CD. D   I'll have to take a look at the specs -- if I still have a copy --E   but you're probably going to be limited to the megabyte resident onrC   the KA630 module.  (You may be able to use a second BA23 to get alC   second, seperate CD -- but I haven't tried this and don't know ifA   it will work.)  F   The module can be bootstrapped via shared memory or via an (EE)PROM.A   (You'll need to write your own bootstrap and operating system.)    H   You will not be able to get OpenVMS SMP running on this system, as theG   internal system design (and specifically the memory subsystem) is not.H   fully symmetric -- interprocessor communications is available only via5   shared memory windows and interprocessor doorbells.p  G   My personal preference for this sort of asymmetric configurtion wouldmH   lean toward the KA640 or the KA660 processors -- those processors haveK   integrated DSSI and network connections, as well as more on-board memory.e  H   If you want to pursue this task, you'll need a copy of the appropriateH   processor technical manual.  It should have the PROM footprint and theG   arbiter selection switch settings, as well as most of the information I   you'll need about the module to write your own operating system for it.u     ...o    3 From: hoff...@xdelta.enet.dec.com (Stephen Hoffman)a Subject: Re: Dual CPU uVaxII?r Date: 1995/07/21. Message-ID: <3uorfj$cim@nntpd.lkg.dec.com>#1/1 X-Deja-AN: 106706872 distribution: worldeI references: <3ujn22$bvb@explorer.csc.com> <3unhat$qcp@mrnews.mro.dec.com>i$ organization: Digital Equipment Corp7 reply-to: hoff...@xdelta.enet.dec.com (Stephen Hoffman)d newsgroups: comp.sys.dec    H In article <3ujn22$...@explorer.csc.com>, rmsm...@csc.com (Robert Smith) writes:o  E >Is it possible to set up a uVax II (BA123) with two CPUs in the box/x >on the bus?  H   Yes (as other posters have indicated), but the resulting configurationF   would be a multiprocessor -- not a symmetric multiprocessor (SMP) --K   system. For an OpenVMS SMP system to run, all processors must have accesseH   to all of the system's main memory -- and that's not possible with theI   KA630 multiprocessor.  (One *could* get this to run like a network on anI   (shared) Q-bus, but one would have to write a whole lot of non-trivial, =   hard-to-debug, and highly-privileged low-level VAX code...)o  K   The KA640 processor -- used in the MicroVAX 3300 and MicroVAX 3400 series3K   systems -- is likely a much better choice for a home-grown multiprocessordL   system than the KA630, as it has four times (4MB) the on-board memory, andK   it has on-board network and I/O connections.  It's also far more commonlypJ   available as a "native" S-box module (in other words, it has the correctJ   S-box handle and DMA grant wiring) -- all slots are Q22/CD in the S-box,H   which avoids the need for multiple BA23/BA123 enclosures to get enough+   Q22/CD slots for the processor module(s).e  J   These configurations are not supported by any Digital operating system IJ   am aware of, and would be one heck of a lot of work to implement...  TheL   technical details are present in the appropriate EK-KA6xx-xx CPU technicalG   manual.  And while working inside the enclosure(s), one can fry one's H   hardware or one's self if not careful -- this project is not for folksF   inexperienced with Q-bus hardware or low-level system programming...   	...   ------------------------------  % Date: Mon, 11 Apr 2005 20:09:34 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com>.) Subject: Re: Multiprocessor Microvax II ?hB Message-ID: <1113264564.f1eb2f6cf14e80c1ed322c25d3bc5f09@teranews>   Hoff Hoffman wrote:iI >   I have previously posted a reply or two on this topic, but that was a H >   few years ago now.  I've attached (most of) two of the semi-relevent >   postings below..  G Thanks for the information. And there I was, thinking i could double myeB all mighty microvax II's incredible power and compete head to head against IA64 :-)  H So when can I expect a Q-bus interconnect between 2 microvax II to carry SCS packets ? :-) :-) :-)p  B I find it interesting that the engineers would have gone so far toC design the KA630 to have some multiprocessor dunctionality, withoutnF going the extra step to make it usable. (Hence my original question if it had evert been used).  H Did decserver 200s use a KA630 board, or did they have their own specialB CPU motherboards ? Perhas the multiprocessor was designed for such applications ?   ------------------------------  # Date: Tue, 12 Apr 2005 03:13:51 GMTT  From: John Santos <john@egh.com>) Subject: Re: Multiprocessor Microvax II ?t, Message-ID: <P1H6e.13926$ox3.13433@trnddc03>   JF Mezei wrote:  > Hoff Hoffman wrote:e > I >>  I have previously posted a reply or two on this topic, but that was aaH >>  few years ago now.  I've attached (most of) two of the semi-relevent >>  postings below.e >  > I > Thanks for the information. And there I was, thinking i could double myTD > all mighty microvax II's incredible power and compete head to head > against IA64 :-) > J > So when can I expect a Q-bus interconnect between 2 microvax II to carry > SCS packets ? :-) :-) :-)- > D > I find it interesting that the engineers would have gone so far toE > design the KA630 to have some multiprocessor dunctionality, without H > going the extra step to make it usable. (Hence my original question if > it had evert been used). > J > Did decserver 200s use a KA630 board, or did they have their own specialD > CPU motherboards ? Perhas the multiprocessor was designed for such > applications ?  D IIRC, DS200's used an M68000 processor.  I've got a dead one down in; the basement - might look inside later if I get bored.  :-)e   --   John Santosn Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------  % Date: Tue, 12 Apr 2005 00:51:27 +0200e- From: Alex van Denzel <vandenzel@hotmail.com>t Subject: Re: OpenVMS FAQ Errataa7 Message-ID: <425aff6f$0$67429$dbd41001@news.wanadoo.nl>    Hoff Hoffman wrote:   K >   There are probably a few other things I've forgotten, and I've receivedaK >   a text-formatting problem report earlier today -- I'm certain there aresK >   updates and corrections needed in this edition of the FAQ, and I expectaL >   there are some stale URLs.  If you find a problem within this edition ofI >   the FAQ -- and preferably with the answer or the correction -- pleasen >   send it along.  Thanks!r  F At least in item 14.17 (Where can I get software and hardware support I information?) the links to http://www.adenzel.demon.nl/vaxes... are dead.   G I took them down a few years ago already and didn't put much effort in g new VAX pages yet.  B But all the same, I'm honoured to be mentioned in the OpenVMS FAQ.  % Greetings, and keep up the good work.e   -- Alex.    ------------------------------  # Date: Mon, 11 Apr 2005 20:23:33 GMT-# From: hoff@hp.nospam (Hoff Hoffman)- Subject: OpenVMS FAQ Errata 1 Message-ID: <91B6e.3499$IL.3402@news.cpqcorp.net>m  I   The usual Postscript, text and HTML format files containing the OpenVMS-J   FAQ should appear at the HP OpenVMS FAQ website over the next few days, H   assuming the OpenVMS web master's schedule permits, and should also beH   appearing at various other web sites around the 'net as the respectiveG   owners and/or system managers realize that the new FAQ edition is nowg   available.  1   The main, official OpenVMS FAQ web site URL is:r  '     <http://www.hp.com/go/openvms/faq/>-  I   I've provided "pre-gurgitated" Stream-LF HTML files and such within thetI   provided zip archives for this new edition of the FAQ, to allow direct WK   services of the FAQ off various web servers requiring that format.  FWIW.iG   These files will be available at the OpenVMS website within the week.e  K   The MD5 tools referenced in the FAQ have now appeared on the Freeware web J   site; look on the Freeware V7.0 FTP directory.  I expect to be providingH   these or similar MD5 tools on the next Freeware distribution, as well.H   The next edition of the FAQ should have a more direct reference to the    availability of the MD5 tools.  I   There are probably a few other things I've forgotten, and I've receivedsI   a text-formatting problem report earlier today -- I'm certain there are8I   updates and corrections needed in this edition of the FAQ, and I expectUJ   there are some stale URLs.  If you find a problem within this edition ofG   the FAQ -- and preferably with the answer or the correction -- pleases   send it along.  Thanks!t  N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faqnN  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.com(   ------------------------------  % Date: Mon, 11 Apr 2005 16:30:30 -0400c- From: JF Mezei <jfmezei.spamnot@teksavvy.com>( Subject: Re: OpenVMS FAQ ErratasB Message-ID: <1113251438.ebb566ba3c58e5793852706696de03c2@teranews>   Hoff Hoffman wrote: 3 >   The main, official OpenVMS FAQ web site URL is:h > ) >     <http://www.hp.com/go/openvms/faq/>f    B Since www.hp.com/go/vms works to get to the main page, perhaps you shoudl ask that , 	www.hp.com/go/vms/faq also be made to work.  E Remember that outside of HP, in the real world, "VMS" is still widelyn, used and more recognised than the open word.   ------------------------------  # Date: Mon, 11 Apr 2005 19:35:25 GMT - From: hoffman@xdelta.hp.nospam (Hoff Hoffman)d< Subject: OpenVMS Frequently Asked Questions (FAQ), Part 1/111 Message-ID: <1kA6e.3484$4D.1650@news.cpqcorp.net>    Archive-name: dec-faq/vms/part1o Posting-Frequency: quarterly Last-modified: 11 Apr 2005 Version: VMSFAQ_20050411-01.TXTe      ?                    The OpenVMS Frequently Asked Questions (FAQ)                             ABSTRACTe  J                    This document contains answers to many common questionsG                    on the OpenVMS operating system, and covers OpenVMS,lA                    and OpenVMS running on Itanium, Alpha, and VAXn                    hardware.  E                    This document is available in various formats, andpG                    the text-format version of this FAQ is generally theu,                    easiest format to search.        =                    Revision/Update Information   OpenVMS V8.2l  I                    Revision/Update Information:  Revision Date/April 2005                                           FAQ e  g                            J           ________________________________________________________________             Contents  J                 __________________________________________________________J                 PREFACE                                                  i  J                 __________________________________________________________J                 OPENVMS FREQUENTLY ASKED QUESTIONS (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-related:J                           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-3l  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 Business J                           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 _  _                              Contentsy        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-3  J                 __________________________________________________________J                 2.3   WHAT'S IN A NAME? TERMINOLOGY AND PRODUCTS?      2-3J                 2.3.1     How do I port from VMS to OpenVMS?           2-4  J                 __________________________________________________________J                 2.4   WHICH IS BETTER, OPENVMS OR UNIX?                2-4  J                 __________________________________________________________>                 2.5   IS HP CONTINUING FUNDING AND SUPPORT FORJ                       OPENVMS?                                         2-5  J                 __________________________________________________________J                 2.6   WHAT OPENVMS DISTRIBUTION KITS ARE AVAILABLE?    2-5B                 2.6.1     Where can I download OpenVMS and LayeredJ                           Product Kits?                                2-8  J                 __________________________________________________________J                 2.7   IN WHAT LANGUAGE IS OPENVMS WRITTEN?             2-8  J                 __________________________________________________________J                 2.8   OBTAINING AND TRANSFERING OPENVMS LICENSES?      2-9=                 2.8.1     Questions asked by Hobbyist OpenVMSaJ                           licensees?                                   2-9J                 2.8.2     OpenVMS Educational and CSLG licenses?      2-10>                 2.8.3     What developer and partner licensingJ                           programs are available?                     2-10@                 2.8.4     How do I obtain or transfer an OpenVMSJ                           license?                                    2-11  J                 __________________________________________________________<                 2.9   DOES OPENVMS SUPPORT THE EURO CURRENCYJ                       SYMBOL?                                         2-11  J                 __________________________________________________________F                 2.10  OPENVMS PORTS? ITANIUM? PORTS TO IA-32, EM64T ORJ                       AMD64 SYSTEMS?                                  2-11                      ivo s                                 Contentsa        J                 __________________________________________________________>                 2.11  ARE THERE ANY NETWORK-ACCESSIBLE OPENVMSJ                       SYSTEMS?                                        2-15  J                 __________________________________________________________J                 2.12  WHAT VERSION OF OPENVMS DO I NEED?              2-16  J                 __________________________________________________________J                 2.13  HOW CAN I SUBMIT OPENVMS FREEWARE?              2-18  J                 __________________________________________________________J                 2.14  PORTING APPLICATIONS TO OPENVMS?                2-18  J                 __________________________________________________________F                 2.15  WHAT RESOURCES ARE AVAILABLE TO OPENVMS SOFTWAREJ                       DEVELOPERS?                                     2-19  J                 __________________________________________________________E                 2.16  MEMORY MANAGEMENT, RESOURCE MANAGEMENT, PROCESSmJ                       SCHEDULING, ETC?                                2-20  J                 __________________________________________________________J                 2.17  BASIC UNITS OF MEASUREMENT?                     2-21J                 2.17.1    How many bytes are in a disk block?         2-22J                 2.17.2    How many bytes are in a memory page?        2-23@                 2.17.3    How do I convert? Disk Blocks? KB, MB,J                           GB, TB?                                     2-24  J           ________________________________________________________________J           CHAPTER 3  DOCUMENTATION                                     3-1  J                 __________________________________________________________?                 3.1   WHERE CAN I FIND ONLINE COPIES OF OPENVMSrJ                       MANUALS?                                         3-1  J                 __________________________________________________________>                 3.2   WHAT ONLINE INFORMATION AND WEBSITES AREJ                       AVAILABLE?                                       3-2  J                 __________________________________________________________H                 3.3   HOW DO I EXTRACT THE CONTENTS OF A HELP TOPIC TO AJ                       TEXT FILE?                                       3-5  J                 __________________________________________________________;                 3.4   DOES OPENVMS MARKETING HAVE AN E-MAILmJ                       ADDRESS?                                         3-5  J                                                                          v S  i                              Contentse        J                 __________________________________________________________?                 3.5   WHERE CAN I LEARN ABOUT OPENVMS EXECUTIVEvJ                       INTERNALS?                                       3-5  J                 __________________________________________________________I                 3.6   WHERE CAN NEW USERS FIND TUTORIAL INFORMATION ABOUTsJ                       OPENVMS?                                         3-6J                 3.6.1     Tutorial Websites?                           3-6J                 3.6.2     Books and Tutorials?                         3-8  J                 __________________________________________________________J                 3.7   WHAT OPENVMS MAILING LISTS ARE AVAILABLE?        3-9  J                 __________________________________________________________D                 3.8   WHAT IS THIS ASK THE WIZARD WEBSITE I'VE HEARDJ                       ABOUT?                                          3-11  J                 __________________________________________________________D                 3.9   WHERE CAN I FIND THE LATEST C RUN-TIME LIBRARYJ                       MANUALS?                                        3-12  J           ________________________________________________________________J           CHAPTER 4  TIME AND TIMEKEEPING                              4-1  J                 __________________________________________________________=                 4.1   A BRIEF HISTORY OF OPENVMS TIMEKEEPING,nJ                       PLEASE?                                          4-17                 4.1.1     Details of the OpenVMS system J                           time-keeping?                                4-2F                 4.1.1.1      VAX hardware time-keeping details..., 4-3,                 4.1.1.1.1     TOY clock, 4-31                 4.1.1.1.2     EXE$GQ_SYSTIME, 4-3t2                 4.1.1.1.3     EXE$GQ_TODCBASE, 4-3.                 4.1.1.1.4     EXE$GL_TODR, 4-4H                 4.1.1.2      Alpha hardware time-keeping details..., 4-5G                 4.1.1.2.1     Battery-Backed Watch (BB_WATCH) Chip, 4-5 1                 4.1.1.2.2     EXE$GQ_SYSTIME, 4-6o7                 4.1.1.2.3     EXE$GQ_SAVED_HWCLOCK, 4-6tI                 4.1.1.3      Why does VAX need a SET TIME at least once ao'                              year?, 4-7 >                 4.1.2     How does OpenVMS VAX maintain systemJ                           time?                                        4-7                        vih y                                 Contentsa        J                 __________________________________________________________J                 4.2   KEEPING THE OPENVMS SYSTEM TIME SYNCHRONIZED?    4-9<                 4.2.1     Why do my cluster batch jobs startJ                           early?                                      4-10J                 4.2.2     Why does my OpenVMS system time drift?      4-11<                 4.2.3     Resetting the system time into theJ                           past?                                       4-12<                 4.2.4     How can I drift the OpenVMS systemJ                           time?                                       4-12A                 4.2.5     How can I configure TCP/IP Services NTPhJ                           as a time provider?                         4-13  J                 __________________________________________________________H                 4.3   MANAGING TIMEZONES, TIMEKEEPING, UTC, AND DAYLIGHTJ                       SAVINGS?                                        4-158                 4.3.1     Creating and Managing TimezoneJ                           Definitions?                                4-17<                 4.3.2     Timezones and Time-related LogicalJ                           Names?                                      4-18=                 4.3.3     How to troubleshoot TDF problems on J                           OpenVMS?                                    4-209                 4.3.4     Customizing your TDF (Timezone)-J                           Setting?                                    4-21  J                 __________________________________________________________G                 4.4   WHY DOES THE SET TIME COMMAND FAIL? HELP MANAGING J                       DTSS?                                           4-22  J                 __________________________________________________________D                 4.5   SETTING TIME ON ALPHASERVER ES47, ES80, GS1280J                       CONSOLE?                                        4-24  J                 __________________________________________________________F                 4.6   UTC VS GMT VS VS UT1/UT1/UT2 TDF? WHAT ARE THESEJ                       ACRONYMS?                                       4-26  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                                                                        vii    e                              Contents         J                 __________________________________________________________J                 5.3   SOURCES OF OPENVMS SECURITY INFORMATION?         5-4  J                 __________________________________________________________J                 5.4   HOW DO I MOUNT AN ISO-9660 CD ON OPENVMS?        5-4  J                 __________________________________________________________J                 5.5   HOW DO I EXTRACT THE CONTENTS OF A PCSI KIT?     5-6  J                 __________________________________________________________J                 5.6   EMERGENCY (CONVERSATIONAL) SYSTEM STARTUP?       5-7C                 5.6.1     I've forgotten the SYSTEM password - whatnJ                           can I do?                                   5-11A                 5.6.2     My product licenses have expired - whatoJ                           can I do?                                   5-11  J                 __________________________________________________________A                 5.7   HOW DO I CHANGE THE NODE NAME OF AN OPENVMS J                       SYSTEM?                                         5-12  J                 __________________________________________________________C                 5.8   WHY DOESN'T OPENVMS SEE THE NEW MEMORY I JUSTsJ                       ADDED?                                          5-14  J                 __________________________________________________________>                 5.9   HOW DO I CHANGE THE TEXT IN A USER'S UICJ                       IDENTIFIER?                                     5-15  J                 __________________________________________________________J                 5.10  WHAT ARE THE OPENVMS VERSION UPGRADE PATHS?     5-16J                 5.10.1    OpenVMS Alpha Upgrade (or Update) Paths     5-16J                 5.10.2    OpenVMS I64 Upgrade Paths                   5-19J                 5.10.3    OpenVMS VAX Release Upgrade Paths           5-19J                 5.10.4    OpenVMS Cluster Rolling Upgrade Paths       5-20=                 5.10.5    OpenVMS Product Version and Support$J                           Information                                 5-217                 5.10.6    OpenVMS Alpha and I64 UpgradeaJ                           Terminology                                 5-22  J                 __________________________________________________________E                 5.11  WHY DO I HAVE A NEGATIVE NUMBER IN THE PAGEFILE J                       RESERVABLE PAGES?                               5-23  J                 __________________________________________________________H                 5.12  DO I HAVE TO UPDATE LAYERED PRODUCTS WHEN UPDATINGJ                       OPENVMS?                                        5-24                      viiio                                   Contentsr        J                 __________________________________________________________J                 5.13  HOW DO I CHANGE THE VOLUME LABEL OF A DISK?     5-25  J                 __________________________________________________________J                 5.14  HOW CAN I SET UP A SHARED DIRECTORY?            5-26  J                 __________________________________________________________=                 5.15  WHY DO I GET EXTRA BLANK PAGES ON MY HP J                       PRINTER?                                        5-27  J                 __________________________________________________________?                 5.16  DRIVERS AND CONFIGURATION OF NEW GRAPHICSoJ                       CONTROLLERS?                                    5-28J                 5.16.1    The ELSA GLoria Synergy                     5-28J                 5.16.2    PowerStorm 300, PowerStorm 350              5-29J                 5.16.3    PowerStorm 3D30, PowerStorm 4D20            5-29J                 5.16.4    Radeon 7500                                 5-30  J                 __________________________________________________________C                 5.17  HOW CAN I ACQUIRE OPENVMS PATCHES, FIXES, AND.J                       ECOS?                                           5-30  J                 __________________________________________________________J                 5.18  HOW DO I MOVE THE QUEUE MANAGER DATABASE?       5-31  J                 __________________________________________________________H                 5.19  HOW DO I DELETE AN UNDELETABLE/UNSTOPPABLE (RWAST)J                       PROCESS?                                        5-32  J                 __________________________________________________________J                 5.20  HOW DO I RESET THE ERROR COUNT(S)?              5-33  J                 __________________________________________________________B                 5.21  HOW DO I FIND OUT IF THE TAPE DRIVE SUPPORTSJ                       COMPRESSION?                                    5-35  J                 __________________________________________________________F                 5.22  CAN I COPY SYSUAF TO ANOTHER VERSION? TO VAX? TOJ                       ALPHA?                                          5-35  J                 __________________________________________________________J                 5.23  HOW DO I DELETE (TIMEOUT) IDLE PROCESSES?       5-38  J                 __________________________________________________________C                 5.24  DO I NEED A PAK FOR THE DECEVENT (HP ANALYZE)oJ                       TOOL?                                           5-38  J                                                                         ix o                                 Contents         J                 __________________________________________________________;                 5.25  INITIALIZE ACCVIO AND ANSI TAPE LABEL J                       SUPPORT?                                        5-39  J                 __________________________________________________________J                 5.26  HOW DO I RECOVER FROM INSVIRMEM ERRORS?         5-39  J                 __________________________________________________________C                 5.27  HOW CAN I PREVENT A SERIAL TERMINAL LINE FROM.J                       INITIATING A LOGIN?                             5-40  J                 __________________________________________________________=                 5.28  HOW DOES PCSI USE THE IMAGE BUILD_IDENTrJ                       FIELD?                                          5-40  J                 __________________________________________________________C                 5.29  HOW CAN I TELL WHAT SOFTWARE (AND VERSION) ISaJ                       INSTALLED?                                      5-42  J                 __________________________________________________________@                 5.30  WHAT FILE CHECKSUM TOOLS ARE AVAILABLE FORJ                       OPENVMS?                                        5-43  J                 __________________________________________________________@                 5.31  WHAT (AND WHERE) IS THE OPENVMS MANAGEMENTJ                       STATION?                                        5-43  J                 __________________________________________________________A                 5.32  HOW TO DETERMINE CURRENT DISK FRAGMENTATIONdJ                       LEVEL?                                          5-43  J                 __________________________________________________________<                 5.33  SYSBOOT-I-FILENOTLOC, UNABLE TO LOCATEJ                       SYS$CPU_ROUTINES?                               5-44  J                 __________________________________________________________G                 5.34  HOW CAN I CUSTOMIZE THE DCPS DEVICE CONTROL FOR AtJ                       NEW PRINTER?                                    5-45  J                 __________________________________________________________J                 5.35  WHY DO $GETDEV MOUNTCNT AND SHOW DEVICE MOUNT COUNTSJ                       DIFFER?                                         5-46  J                 __________________________________________________________<                 5.36  WHAT SOFTWARE IS NEEDED FOR POSTSCRIPTJ                       PRINTERS?                                       5-46                      x ,  d                              Contentst        J                 __________________________________________________________B                 5.37  HOW DO I REMOVE A PCSI-INSTALLED PATCH (ECO)J                       KIT?                                            5-46  J                 __________________________________________________________>                 5.38  SYSINIT-E, ERROR MOUNTING SYSTEM DEVICE,J                       STATUS=0072832C                                 5-47  J                 __________________________________________________________J                 5.39  RESOLVING LICENSE PAK PROBLEMS?                 5-47  J                 __________________________________________________________J                 5.40  CHANGING THE OPENVMS VERSION NUMBER?            5-49  J                 __________________________________________________________@                 5.41  HOW TO PREVENT USERS FROM CHOOSING OBVIOUSJ                       PASSWORDS?                                      5-50  J                 __________________________________________________________<                 5.42  PLEASE HELP ME WITH THE OPENVMS BACKUPJ                       UTILITY?                                        5-52J                 5.42.1    Why isn't BACKUP/SINCE=BACKUP working?      5-52F                 5.42.1.1     Why has OpenVMS gone through the agony of/                              this change?, 5-52oA                 5.42.1.2     Can you get the old BACKUP behaviouro(                              back?, 5-529                 5.42.2    What can I do to improve BACKUPaJ                           performance?                                5-53J                 5.42.3    Why is BACKUP not working as expected?      5-53J                 5.42.4    How do I fix a corrupt BACKUP saveset?      5-55>                 5.42.5    How do I write a BACKUP saveset to aJ                           remote tape?                                5-56<                 5.42.6    How to perform a DoD security diskJ                           erasure?                                    5-57J                 5.42.7    How to enable telnet virtual terminals?     5-59J                 5.42.7.1     Volume Shadowing MiniCopy vs MiniMerge?, 5-59.                 5.42.7.1.1    Mini-Copy?, 5-60/                 5.42.7.1.2    Mini-Merge?, 5-61g  J                 __________________________________________________________J                 5.43  PLEASE EXPLAIN DELETE/ERASE AND FILE LOCKS?     5-61  J                 __________________________________________________________J                 5.44  MANAGING FILE VERSIONS?                         5-62  J                                                                         xi                                   Contentsw        J           ________________________________________________________________J           CHAPTER 6  INFORMATION ON MAIL                               6-1  J                 __________________________________________________________I                 6.1   MAIL KEEPS SAYING I HAVE NEW MESSAGES, BUT I DON'T.sJ                       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-3  J                 __________________________________________________________J                 7.4   HOW DO I READ IBM EBCDIC TAPES ON OPENVMS?       7-3  J                 __________________________________________________________J                 7.5   HOW CAN I PATCH AN OPENVMS ALPHA IMAGE?          7-4  J           ________________________________________________________________J           CHAPTER 8  DCL DETAILS                                       8-1  J                 __________________________________________________________J                 8.1   DCL SYMBOLS AND OPENVMS LOGICAL NAMES?           8-1  J                 __________________________________________________________J                 8.2   HOW DO I RUN A PROGRAM WITH ARGUMENTS?           8-3  J                 __________________________________________________________J                 8.3   HOW CAN I CLEAR THE SCREEN IN DCL?               8-5                      xii                                   Contentse        J                 __________________________________________________________A                 8.4   USING REPLY/LOG FROM DCL? DISABLING CONSOLEiJ                       OPCOMS?                                          8-5  J                 __________________________________________________________J                 8.5   HOW DO I GENERATE A RANDOM NUMBER IN DCL?        8-6  J                 __________________________________________________________J                 8.6   WHAT DOES THE MCR COMMAND DO?                    8-7  J                 __________________________________________________________J                 8.7   HOW DO I CHANGE THE OPENVMS SYSTEM PROMPT?       8-7  J                 __________________________________________________________E                 8.8   CAN I DO DECNET TASK-TO-TASK COMMUNICATION WITHeJ                       DCL?                                             8-8  J                 __________________________________________________________:                 8.9   HOW CAN I GET THE WIDTH SETTING OF AJ                       TERMINAL?                                        8-9  J                 __________________________________________________________J                 8.10  WHY DOESN'T DCL SYMBOL SUBSTITUTION WORK?        8-9  J                 __________________________________________________________J                 8.11  HOW CAN I SUBSTITUTE SYMBOLS IN A PIPE?         8-10  J                 __________________________________________________________>                 8.12  USE OF RUN/DETACH, LOGINOUT, AND LOGICALJ                       NAMES?                                          8-10  J                 __________________________________________________________A                 8.13  HOW TO USE ESCAPE AND CONTROL CHARACTERS INwJ                       DCL?                                            8-11  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                                                                       xiii -  H                              Contentsd        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 RECORDrJ                       SIZE LIMIT?                                      9-7  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-106                 9.7.2     Use of RRD42 and other olderJ                           (embossed-media) CD drives?                 9-12A                 9.7.3     Creating Bootable OpenVMS I64 CD or DVD-J                           Media? SYS$SETBOOT?                         9-13  J                 __________________________________________________________<                 9.8   WHAT I/O TRANSFER SIZE LIMITS EXIST INJ                       OPENVMS?                                        9-14  J                 __________________________________________________________C                 9.9   CAN I USE ODBC TO CONNECT TO OPENVMS DATABASE/J                       FILES?                                          9-14  J                 __________________________________________________________J                 9.10  IF MY DISKS ARE SHOWN AS VIOC COMPATIBLE, AM I USINGJ                       XFC?                                            9-15  J                 __________________________________________________________7                 9.11  RMS SEQUENTIAL FILES AND PLATFORM J                       PORTABILITY?                                    9-15  J           ________________________________________________________________J           CHAPTER 10  OPENVMS PROGRAMMING INFORMATION                 10-1  J                 __________________________________________________________G                 10.1  MODULAR PROGRAMMING, FACILITY PREFIXES AND SYMBOL J                       NAMING?                                         10-1                      xiv o  t                              Contents         J                 __________________________________________________________9                 10.2  CAN I HAVE A SOURCE CODE EXAMPLE OFiJ                       CALLING...?                                     10-2  J                 __________________________________________________________A                 10.3  HOW DO I GET THE ARGUMENTS FROM THE COMMAND J                       LINE?                                           10-4  J                 __________________________________________________________A                 10.4  HOW DO I GET A FORMATTED ERROR MESSAGE IN A_J                       VARIABLE?                                       10-5  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 A_J                       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-7  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  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-10  J                                                                         xv                                   Contents         J                 __________________________________________________________=                 10.14 HOW DO I CREATE A PROCESS UNDER ANOTHER-J                       USERNAME?                                      10-12  J                 __________________________________________________________G                 10.15 WHY DO LIB$SPAWN, LIB$SET_SYMBOL FAIL IN DETACHED J                       PROCESSES?                                     10-13  J                 __________________________________________________________E                 10.16 WHERE CAN I OBTAIN BLISS, AND THE LIBRARIES AND J                       SUPPORTING FILES?                              10-14  J                 __________________________________________________________J                 10.17 HOW CAN I OPEN A FILE FOR SHARED ACCESS?       10-15  J                 __________________________________________________________A                 10.18 HOW CAN I HAVE COMMON SOURCES FOR MESSAGES, J                       CONSTANTS?                                     10-16  J                 __________________________________________________________D                 10.19 HOW DO I ACTIVATE THE OPENVMS DEBUGGER FROM ANJ                       APPLICATION?                                   10-16  J                 __________________________________________________________J                 10.20 DEALING WITH ENDIAN-NESS?                      10-17  J                 __________________________________________________________J                 10.21 HOW TO RESOLVE LINK-I-DATMISCH ERRORS?         10-17  J                 __________________________________________________________:                 10.22 HP C AND OTHER OPENVMS C PROGRAMMINGJ                       CONSIDERATIONS?                                10-18J                 10.22.1   Other common C issues                      10-21J                 10.22.2   Other common C++ issues                    10-23  J                 __________________________________________________________J                 10.23 STATUS OF PROGRAMMING TOOLS ON OPENVMS VAX?    10-25  J                 __________________________________________________________?                 10.24 CHOOSING A VERSION NUMBER FOR APPLICATION J                       CODE?                                          10-26  J                 __________________________________________________________J                 10.25 SELECTING A PROCESS DUMP DIRECTORY?            10-27  J                 __________________________________________________________J                 10.26 ACCESS TO ITANIUM ASSEMBLER?                   10-28                      xvi                                   Contents         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                 __________________________________________________________J                 11.5  WHY IS DECWINDOWS MOTIF NOT STARTING?           11-4  J                 __________________________________________________________J                 11.6  HOW DO I SET THE TITLE ON A DECTERM WINDOW?     11-6  J                 __________________________________________________________H                 11.7  HOW DO I CUSTOMIZE DECWINDOWS, INCLUDING THE LOGINJ                       SCREEN?                                         11-77                 11.7.1    How do I customize DECwindowsMJ                           keymapping?                                11-10@                 11.7.2    Why does the DELETE key delete forwardJ                           instead of backward?                       11-10  J                 __________________________________________________________J                 11.8  WHY DOESN'T XTAPPADDINPUT()  WORK ON OPENVMS?  11-12  J                 __________________________________________________________H                 11.9  WHY DO THE KEYBOARD ARROW KEYS MOVE THE DECWINDOWSJ                       CURSOR?                                        11-13  J                 __________________________________________________________J                 11.10 WHY DOES HALF MY DECWINDOWS DISPLAY BLANK?     11-13  J                 __________________________________________________________H                 11.11 %DECW-W-NODEVICE, NO GRAPHICS DEVICE FOUND ON THISJ                       SYSTEM?                                        11-14  J                                                                       xvii    I                              Contents?        J                 __________________________________________________________J                 11.12 HOW CAN I RESET THE WARNING BELL VOLUME?       11-16  J                 __________________________________________________________J                 11.13 HOW CAN I ALTER THE DECWINDOWS CDE BACKDROP?   11-17  J                 __________________________________________________________<                 11.14 HOW CAN I ENABLE THE DECWINDOWS TCP/IPJ                       TRANSPORT                                      11-17  J                 __________________________________________________________E                 11.15 CAN I USE DECWINDOWS 1.2-* ON OPENVMS V7.3-2 OR_J                       LATER?                                         11-17  J                 __________________________________________________________J                 11.16 HOW TO ADD FONTS INTO DECWINDOWS?              11-18  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  CORRECTLY USING LICENSE PAKS AND LMF?           12-4  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                          xviii T  B                              Contents         J                 __________________________________________________________J                 13.2  WHERE CAN I FIND UNIX TOOLS FOR OPENVMS?       13-15J                 13.2.1    C system and library routines              13-15J                 13.2.2    X Windows utilities and routines           13-15J                 13.2.3    TCP/IP Tools and Utilities for OpenVMS?    13-16J                 13.2.4    The vi text editor                         13-16J                 13.2.5    The Emacs Text Editor                      13-16J                 13.2.6    Various GNU tools                          13-170                 13.2.6.1     GCC compiler, 13-17  J                 __________________________________________________________J                 13.3  WHAT IS THE STATUS OF PL/I ON OPENVMS?         13-18  J                 __________________________________________________________J                 13.4  WHERE CAN I GET THE MOZILLA WEB BROWSER?       13-18  J                 __________________________________________________________J                 13.5  WHERE CAN I GET JAVA FOR OPENVMS?              13-19  J                 __________________________________________________________J                 13.6  OBTAINING USER INPUT IN DCL CGI SCRIPT?        13-20  J                 __________________________________________________________A                 13.7  HOW CAN A BATCH JOB GET ITS OWN BATCH ENTRY_J                       NUMBER?                                        13-21  J                 __________________________________________________________J                 13.8  HOW DO I CONVERT TO NEW CMS OR DTM LIBRARIES?  13-21  J                 __________________________________________________________J                 13.9  WHERE CAN I GET PERL FOR OPENVMS?              13-22  J                 __________________________________________________________F                 13.10 OBTAINING THE DECMIGRATE (AEST OR VEST, AND TIE)J                       TRANSLATOR?                                    13-24  J                 __________________________________________________________F                 13.11 WHERE CAN I GET ZIP, UNZIP, SELF-EXTRACTING ZIP,J                       ETC?                                           13-25  J                 __________________________________________________________J                 13.12 ARE VAX HARDWARE EMULATORS AVAILABLE?          13-26    J                                                                        xix                                   Contents0        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-3  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-4J                 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-5J                 14.3.3.1     Which terminal device name is assigned to the-                              COM ports?, 14-5_D                 14.3.3.2     Which serial port is the console on the1                              MicroVAX 3100?, 14-5 G                 14.3.3.3     How can I set up an alternate console on a .                              VAXstation?, 14-6J                 14.3.3.4     Please explain the back panel of the MicroVAX%                              II, 14-6 <                 14.3.4    What are Alpha console environmentJ                           variables?                                  14-8J                 14.3.5    What are the boot control flag values?      14-9I                 14.3.5.1     What are the I64 IPB boot flag values?, 14-9.=                 14.3.5.2     What are the Alpha APB boot flag +                              values?, 14-10 J                 14.3.5.3     What are the VAX VMB boot flag values?, 14-12?                 14.3.6    How do I boot an AlphaStation withoutHJ                           monitor or keyboard?                       14-15;                 14.3.7    Downloading and using SRM console_J                           Firmware?                                  14-16I                 14.3.7.1     Where can I get updated console firmware for 2                              Alpha systems?, 14-16I                 14.3.7.2     How do I reload SRM firmware on a half-flashH1                              Alpha system?, 14-17 J                 14.3.7.3     How do I switch between AlphaBIOS/ARC and SRM-                              consoles?, 14-18aJ                 14.3.8    Console Management Options                 14-21                      xx9                                   Contentsl        J                 14.3.9    Why do my EFI Boot Aliases Fail?           14-22A                 14.3.10   Can OpenVMS access the EFI console Boot J                           Aliases?                                   14-22;                 14.3.11   Downloading and using EFI Console J                           Firmware?                                  14-22  J                 __________________________________________________________J                 14.4  WHAT PLATFORMS WILL OPENVMS OPERATE ON?        14-24J                 14.4.1    on the Alpha Multia?                       14-26J                 14.4.2    on AlphaPC 164LX? AlphaPC 164SX?           14-28B                 14.4.2.1     on the NoName AXPpci33 system?, 14-28J                 14.4.3    on the Alpha XL series?                    14-29@                 14.4.4    OpenVMS on the Personal Workstation -aJ                           and -au series?                            14-29H                 14.4.4.1     OpenVMS on the Whitebox Windows-Only series*                              Alpha?, 14-31G                 14.4.4.2     OpenVMS and Personal Workstation ATA (IDE) .                              bootstrap?, 14-32J                 14.4.5    On the Intel Itanium IA-64 platform?       14-32:                 14.4.5.1     Where can I get Intel Itanium0                              information?, 14-33  J                 __________________________________________________________F                 14.5  WHAT IS THE LEAST EXPENSIVE SYSTEM THAT WILL RUNJ                       OPENVMS?                                       14-33  J                 __________________________________________________________?                 14.6  WHERE CAN I GET MORE INFORMATION ON ALPHA J                       SYSTEMS?                                       14-34  J                 __________________________________________________________J                 14.7  DESCRIBE ALPHA INSTRUCTION EMULATION AND INSTRUCTIONJ                       SUBSETS?                                       14-35  J                 __________________________________________________________J                 14.8  SO HOW DO I OPEN UP THE DEC 3000 CHASSIS?      14-37  J                 __________________________________________________________J                 14.9  WHAT IS BYTE SWIZZLING?                        14-37  J                 __________________________________________________________B                 14.10 WHAT IS THE LAYOUT OF THE VAX FLOATING POINTJ                       FORMAT?                                        14-39  J                                                                        xxi _  _                              Contents_        J                 __________________________________________________________J                 14.11 WHERE CAN I FIND MORE INFO ABOUT VAX SYSTEMS?  14-40  J                 __________________________________________________________D                 14.12 WHERE CAN I FIND INFORMATION ON NETBSD FOR VAXJ                       SYSTEMS?                                       14-40  J                 __________________________________________________________E                 14.13 WHAT SYSTEM DISK SIZE LIMIT ON THE MICROVAX AND8J                       VAXSTATION 3100?                               14-40  J                 __________________________________________________________J                 14.14 WHAT ARE THE VAX PROCESSOR (CPU) CODES?        14-42  J                 __________________________________________________________C                 14.15 WHERE CAN I GET SOFTWARE AND HARDWARE SUPPORT_J                       INFORMATION?                                   14-43  J                 __________________________________________________________G                 14.16 WHERE CAN I GET HARDWARE SELF-MAINTENANCE SUPPORT_J                       ASSISTANCE?                                    14-44  J                 __________________________________________________________D                 14.17 WHY DOES MY SYSTEM HALT WHEN I POWER-CYCLE THEJ                       CONSOLE TERMINAL?                              14-45  J                 __________________________________________________________I                 14.18 CAN I REUSE OLD KEYBOARDS, MICE AND MONITORS WITH ASJ                       PC?                                            14-45  J                 __________________________________________________________C                 14.19 WHICH VIDEO MONITOR WORKS WITH WHICH GRAPHICSLJ                       CONTROLLER?                                    14-47  J                 __________________________________________________________<                 14.20 WHERE CAN I GET INFORMATION ON STORAGEJ                       HARDWARE?                                      14-49  J                 __________________________________________________________=                 14.21 WHY DOES MY LK401 KEYBOARD UNEXPECTEDLYTJ                       AUTOREPEAT?                                    14-49  J                 __________________________________________________________I                 14.22 PROBLEM - MY LK411 SENDS THE WRONG KEYCODES OR SOMEIJ                       KEYS ARE DEAD                                  14-50                      xxii-                                   Contents_        J                 __________________________________________________________B                 14.23 WHICH DE500 VARIANT WORKS WITH WHICH OPENVMSJ                       VERSION?                                       14-50  J                 __________________________________________________________0                 14.24 THIRD-PARTY OR UNSUPPORTEDJ                       DISK/TAPE/CONTROLLERS/SCSI/WIDGETS?            14-529                 14.24.1   Lists of third-party widgets on J                           OpenVMS?                                   14-55A                 14.24.2   Are the 2X-KZPCA-AA and SN-KZPCA-AA LVD J                           Ultra2 SCSI?                               14-55J                 14.24.3   Resolving DRVERR fatal device error?       14-56  J                 __________________________________________________________J                 14.25 LOOKING FOR CONNECTOR WIRING PIN-OUTS?         14-56  J                 __________________________________________________________=                 14.26 WHAT CONNECTORS AND WIRING ADAPTERS ARE J                       AVAILABLE?                                     14-59  J                 __________________________________________________________J                 14.27 WHAT IS FLOW CONTROL AND HOW DOES IT WORK?     14-61  J                 __________________________________________________________J                 14.28 CD AND DVD DEVICE REQUIREMENTS?                14-63  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 viaSJ                           TCP/IP?                                     15-2<                 15.2.4    How do I set a default IP route orJ                           gateway on OpenVMS?                         15-3?                 15.2.5    How can I set up reverse telnet (like J                           reverse LAT)?                               15-4C                 15.2.6    Why can't I use PPP and RAS to connect to J                           OpenVMS Alpha?                              15-4  J                                                                      xxiii o  w                              Contents         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 HARDWARECJ                       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 VMSeJ                           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 ProtocolTJ                           Details?                                   15-11D                 15.6.1.1     OpenVMS Cluster (SCS) over DECnet? Over'                              IP?, 15-11 B                 15.6.1.2     Configuring Cluster SCS for path load.                              balancing?, 15-129                 15.6.1.2.1    Cluster Terminology?, 15-12TD                 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-16I                 15.6.2.1     What is the correct value for EXPECTED_VOTESM4                              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-193<                 15.6.3    Tell me about SET HOST/DUP and SETJ                           HOST/HSC                                   15-20J                 15.6.4    How do I rename a DSSI disk (or tape?)     15-22?                 15.6.5    Where can I get Fibre Channel StorageVJ                           (SAN) information?                         15-23                      xxiv_                                   Contents         B                 15.6.6    Which files must be shared in an OpenVMSJ                           Cluster?                                   15-23J                 15.6.7    How can I split up an OpenVMS Cluster?     15-24J                 15.6.8    Details on Volume Shadowing?               15-26E                 15.6.8.1     Does volume shadowing require a non-zero_7                              allocation classes?, 15-26     J           ________________________________________________________________           INDEX   J           ________________________________________________________________           TABLES  J                 1-1   Core Websites                                    1-1  J                 1-2   INFO-VAX Mail Server Commands                    1-4  J                 2-1   OpenVMS Alpha Media Kits                         2-6  J                 2-2   OpenVMS I64 Order Numbers                        2-6  J                 2-3   OpenVMS I64 Media Suffix                         2-7  J                 2-4   OpenVMS Source Listings Kits                     2-7  J                 2-5   OpenVMS Alpha Version Rule-Of-Thumb             2-17  J                 3-1   OpenVMS Websites                                 3-2  J                 3-2   OpenVMS Tutorial and Documentation Websites      3-6  J                 3-3   DP Books                                         3-8  J                 3-4   OpenVMS Mailing Lists                           3-10  J                 11-1  X Windows Display Commands                      11-1  J                 14-1  I64 Conversational Bootstrap Flags             14-10  J                 14-2  Alpha Conversational Bootstrap Flags           14-11  J                 14-3  VAX Conversational Bootstrap Flags             14-12  J                 14-4  DE500 Speed and Duplex Settings                14-51  J                 14-5  DEC MMJ Pin-out                                14-56  J                 14-6  PC DB9 Pin-out                                 14-57  J                 14-7  MicroVAX DB9 Pin-out                           14-58  J                 14-8  DECconnect MMJ Connectors and Adapters         14-59  J                 15-1  Cluster Common Shared Files                    15-23  J                                                                        xxv O  O                  J           ________________________________________________________________             Preface_                                                                                    J                                                                          i _  _                  J           ________________________________________________________________  2           OpenVMS Frequently Asked Questions (FAQ)    G                    This is the OpenVMS Frequently Asked Questions (FAQ)SF                    posting for the comp.os.vms and comp.sys.dec usenet                    newsgroups.  ?                                Suggestions and Updates Welcome!_  ?                       Please send your suggestions for changes,AF                       additions, or corrections directly to FAQ Editor1                       (hoff{atsign}hp{period}com)   =                                  No Support Questions, Please   C                       Please do not send technical questions to the_F                       FAQ Editor (hoff{atsign}hp{period}com) . The FAQD                       Editor (hoff{atsign}hp{period}com) is not in aB                       position to answer general questions, nor toE                       provide general product support. Rather, please G                       post your questions to the appropriate newsgroup, F                       or please contact your preferred hardware and/or@                       software support organization(s) directly.  B                       Your understanding in this matter is greatly"                       appreciated.  B                    If you believe any particular discussion worthyB                    of inclusion in a future edition of the FAQ andG                    particularly once you have or know both the question I                    and the answer, please then send the entire discussion J                    along to the FAQ Editor (hoff{atsign}hp{period}com) for'                    potential inclusion.d  J                    Do note that the FAQ Editor (hoff{atsign}hp{period}com)F                    takes URL link continuity seriously, and strives toD                    maintain current links. This is, however, a largeD                    task, and it is only becoming more difficult. URLA                    link continuity is also something that you canSD                    assist with, of course. If you should find a deadE                    link or a stale URL pointer, please notify the FAQ_C                    Editor (hoff{atsign}hp{period}com) . If you haveOC                    or can find the current, correct or updated URL, A                    of course, that greatly assists the FAQ Editor_  J                                                                        iii V             ;                    OpenVMS Frequently Asked Questions (FAQ)         F                    (hoff{atsign}hp{period}com) in maintaining the most(                    current set of links.                      Thank you!A  =                                 Post to Newsgroups With Care!   @                       Please consider reading Section 1.3 before=                       posting to the comp.os.vms or any otherAG                       newsgroups. (What you post can come back to haunt_                       you.)_  '           _____________________________            Contributors  E                    Many people have contributed to this FAQ, directly C                    and/or indirectly. In many cases, part or all of F                    an answer included in the FAQ has been adapted fromE                    one or more postings from the comp.os.vms or otherAJ                    newsgroup-this though individual citations and specificE                    quotations are generally not included in this FAQ._H                    (The FAQ Editor (hoff{atsign}hp{period}com) wishes toF                    thank to all of those folks who post answers to theH                    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.   C                    Paul Anderson, Jason Armistead, Zoltan Arpadffy,_C                    John AtoZ, Bailey, Jeremy Begg, Colin Blake, KenOB                    Blaylock, Kenneth Block, Bol, Craig Berry, MarkH                    Berryman, Jim Becker, Verell Boaen, Bol, Jim Brankin,C                    Richard Brodie, Robert Alan Byer, Jeff Campbell,ED                    Scott Campbell, Antonio Carlini, Keith Cayemberg,E                    Ken Chaney, Cristy, John Croll, David J. Dachtera,_C                    Robert Deininger, Dale Dellutri, Leo Demers, SueGC                    Denham, Thomas Dickey, Eric Dittman, Jim Dunham, G                    Eric, Glenn Everhart, Ken Fairfield, Yaacov Fenster,_B                    Gunther Froehlin, Harry Garonzik, Derek Garson,                      ivT I  O          ;                    OpenVMS Frequently Asked Questions (FAQ)         E                    John Gillings, Andy Goldstein, Clair Grant, Hunter_J                    Goatley, Ruth Goldenberg, Vance Haemmerle, Ki Suk Hahn,E                    SHarris, Fletcher Hearns, Phillip Helbig, Hein van H                    den Heuvel, Stephen Hoffman, Eberhard Heuser-Hofmann,D                    Sue Holt, Horn, Jaf, Leif Jansson, Kevin Jenkins,F                    Don Jones, Henry Juengst, inazu_k, Geoff Kingsmill,I                    Fred Kleinsorge, Felix Kreisel, Veli Korkko, Ruslan R. J                    Laishev, Norm Lastovica, p_lee, Jerry Leichter, RichardG                    Levitte, Steve Lionel, Kerry Main, John E. Malmberg,nJ                    David Mathog, Dale Miller, Dick Munroe, Patrick Moreau,J                    Morrison, otis, George Pagliarulo, Keith Parris, Plass,F                    pvhp, David Rabahy, Stan Rabinowitz, Mike Raspuzzi,H                    Steve Reece, Ian Ring, Aaron Sakovich, Warren Sander,F                    Mark Schafer, Brian Schenkenberger, Atlant Schmidt,F                    Wayne Sewell, Steven Shamlian, Sue Skonetski, ScottB                    Snadow, Scott Squires, stfp, Dave Sweeney, MikeI                    Thompson, Arne Vajhj, Martin Vorlnder, Peter Weaver, E                    William Webb, Williams, Paul Winalski, Uwe Zinser.   D                    Again, any omission from this list and any errorsE                    or misspellings are entirely unintentional. PleaseAG                    notify the FAQ Editor (hoff{atsign}hp{period}com) of_D                    any omissions, corrections, or updates that mightD                    be needed within this list. And thanks to each ofG                    these individuals for their assistance and for their_D                    contributions, and particularly for sharing their                    expertise.   D           __________________________________________________________(           FAQ Archives and FAQ Locations  J                    The OpenVMS FAQ is archived in (at least) the following                    locations:   7                    o  http://www.hp.com/go/openvms/faq/_  @                    o  ftp://rtfm.mit.edu/pub/usenet/comp.os.vms/  )                    o  news://comp.answers-  )                    o  news://news.answers_  *                    o  http://www.faqs.org/  ,                    o  http://www.google.com/  0                    o  http://www.kjsl.com/vmsfaq  J                                                                          v               ;                    OpenVMS Frequently Asked Questions (FAQ)         9                    o  http://eisner.decus.org/vms/faq.htm_  0                    o  http://www.hoffmanlabs.org  G                    Other internet FAQs are generally available in these_                    locations:_  )                    o  news://comp.answers   )                    o  news://news.answers   4                    o  ftp://rtfm.mit.edu/pub/usenet/  *                    o  http://www.faqs.org/  ,                    o  http://www.google.com/  D           __________________________________________________________5           FAQ File Formats and Production Information_  C                    This FAQ is available in ASCII text, Postscript,EF                    Bookreader, and HTML, and potentially in other fileJ                    formats. Certain formats, such as the Adobe Acrobat PDFF                    conversion from the Postscript format, are providedC                    downstream from the FAQ text formatting, and are_5                    provided and maintained by others.   I                    As the HTML-format FAQ is not a single monolithic (and I                    accordingly large) HTML file, it is the most difficult B                    format to search using the most common standardF                    (platform-local) tools. Accordingly, the FAQ EditorF                    (hoff{atsign}hp{period}com) recommends downloading,A                    using and searching the ASCII text FAQ format._  D                    The OpenVMS FAQ is maintained in DECdocument SDMLH                    format and all FAQ maintenance and the primary outputC                    file format conversions are performed on OpenVMS_G                    systems. For information on the DECdocument product, 5                    please contact Touch Technologies._                              vi_ _  _          ;                    OpenVMS Frequently Asked Questions (FAQ)       D           __________________________________________________________6           Old FAQ Section Notations Available in Index  I                    For the folks that are familiar with older editions of_H                    this FAQ and specifically for those folks looking forH                    the older section name keywords, please see the indexH                    entries located under FAQ Sections (Old). These olderE                    section names include the prefixes DCL, DECW, DOC, I                    FILES, MISC, MGMT, INTRO, SOFT, VMS, etc., followed byf&                    the section number.  D           __________________________________________________________           The Fine Print  F                    Corrections and suggestions are welcome. Should youJ                    believe you can provide better stewardship of this FAQ,G                    or should you have strong feelings over the content,OH                    structure, organization or implementation of the FAQ,D                    do realize you may be offered the editorship. TheF                    editor maintains this document as a free service to)                    the OpenVMS community.   C                    While the information contained here is believed_G                    correct, the use of any and all information acquiredHD                    from this document is entirely at the risk of theD                    user(s). If your system should crash or your dataF                    should become corrupted or the answer(s) found hereJ                    should be found erroneous, that is solely your risk and'                    your responsibility.H  B                    Though the editor of this FAQ is an employee ofE                    Hewlett-Packard Company (HP), this posting and theAF                    information contained within this FAQ are is not anH                    official statement of HP, nor a commitment by HP. AllG                    information, comments or opinions included, cited or G                    otherwise referenced here may or may not reflect the_H                    stated opinions of HP, of the editor, or of any other                    entity.  J                    All trademarks, registered trademarks, servicemarks andJ                    registered servicemarks used or referenced here are theF                    properties of their respective owner(s) or holders.D                    Please route any corrections, requests or relatedH                    updates to the FAQ Editor (hoff{atsign}hp{period}com)  J                                                                        vii _  _          ;                    OpenVMS Frequently Asked Questions (FAQ)I        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.  ;                    The master copy of this FAQ is posted at   6                    o  http://www.hp.com/go/openvms/faq  F                    Translations of this FAQ into various languages mayD                    be available, please contact the maintainer(s) ofE                    any translated document for assistance or feedback F                    involving the particular translated edition of this                    FAQ.N                                                                                  viii_ _  _                    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 in                     Table 1-1:_  J           ________________________________________________________________"           Table 1-1  Core Websites  J           ________________________________________________________________J           URL_______Contents______________________________________________  B           Core OpenVMS Information, including roadmaps and release           schedules   1                     http://www.hp.com/go/openvms/   8           OpenVMS and Core Layered Product Documentation  5                     http://www.hp.com/go/openvms/doc/i  G           Core OpenVMS Support Search Engine URLs, the ITRC support andGC           discussion forums, and the ITRC FTP-accessable Patch Area_  D                     http://askq.compaq.com/ (Natural Language Search                     Assistant)  +                     http://www.itrc.hp.com/_  :                     ftp://ftp.itrc.hp.com/openvms_patches/             The OpenVMS Freeware  :                     http://www.hp.com/go/openvms/freeware/  .           The OpenVMS Hobbyist License Program  J           __________http://www.openvmshobbyist.org/_______________________  J                                                                        1-1 N  S                              Introduction       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 using_D                    OpenVMS operating system. Key among these are theF                    comp.os.vms newsgroup and the vmsnet.* heirarchy of                    newsgroups.  '           _____________________________R@           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 compilers J                    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.  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).   J                    Also of interest are resources and conferencing systemsH                    including Encompasserve (formerly known as DECUServe)7                    and Ken Farmer's OpenVMS.Org forums:   0                    o  telnet://eisner.decus.org/  -                    o  http://www.openvms.org/i                      1-2                                   IntroductionW      '           _____________________________ 7           1.2.3  What newsgroup archives are available?   >                    Extensive archives of INFO-VAX mailings andE                    comp.os.vms postings are archived and available at 6                    SRI: ftp://crvax.sri.com/info-vax/.  I                    Google also has extensive newsgroup archives availablel                    ath  ,                    o  http://www.google.com/  '           _____________________________a3           1.2.4  What is the INFO-VAX mailing list?b  F                    INFO-VAX is a mailing list which is bidirectionallyE                    gatewayed to the comp.os.vms newsgroup. This means I                    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 through1G                    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.   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.-  '           _____________________________nF           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 are D                    handled automatically by a mail server. This mailE                    server ignores the subject line and processes eachp4                    line of the message as a command.  J                                                                        1-3    n                              Introduction-        H                    The syntax for subscribing and unsubscribing, as wellF                    as setting various parameters on your subscription,                    is:  J           ________________________________________________________________2           Table 1-2  INFO-VAX Mail Server Commands  J                    _______________________________________________________J                    Command____________________Description_________________  I                    HELP                       Acquire information on mail 4                                               server  F                    SUBSCRIBE INFO-VAX         Join to the mailing list  D                    UNSUBSCRIBE INFO-VAX       Leave the mailing list  E                    SET INFO-VAX DIGEST        Select periodic omnibus I                                               mail messages from the mail J                                               server, rather than multipleJ                                               individual messages for each6                                               posting.  G                    SET INFO-VAX NODIGEST      Separate mail delivery of A                                               each message posted1  H                    SET INFO-VAX NOMAIL        Establish an email addressI                                               for posting, though not for >                                               receiving, mail.  H                    SET INFO-VAX MAIL          Establish an email addressF                                               for both posting and forE                                               receiving mail from the J           ____________________________________mailing_list._______________  A                    The mail server is not case-sensitive; case is E                    irrelevant. Settings and policies can be retrievedn>                    from the mail server, typically using HELP.  J                    The INFO-VAX moderator can be contacted directly at the?                    email address Mark.Berryman[at]Mvb.Saic.Com._                          1-4 _                                 IntroductionR      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 information I                    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 allow3J                    you to quickly find the answer to your own question-andG                    more quickly than waiting for a response to questionRD                    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 hasOE                    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:1  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 permanentRE                       fixture of the network. And using the available F                       search engines, a fixture that is easy to locateH                       and to correlate. (Do not assume that all tools orF                       archives will honor the do-not-cache attributes,J                       either-postings marked as such can be among the most<                       interesting ones to cache, after all.)  I                       For details on some of the many available archives,S/                       please see Section 1.2.3.L    J                                                                        1-5 w  e                              Introduction         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,ND                       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 information_G                       such as processor type, product versions (OpenVMSPI                       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 so H                       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 replySJ                       only as much of the original posting as is necessaryI                       to establish context. As a guideline, consider that E                       if you've included more text than you've added, F                       you've possibly included too much. Never include?                       signatures and other irrelevant material.   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 whatxF                       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 otherkC                       vendor's) product, please use the appropriate C                       support channel. Do not assume that newsgroupnI                       postings will get read, will be responded to by the_J                       appropriate developers, or will be later followed up                       upon.                       1-6                                   Introduction4        H                    o  If you are posting from a web browser, news readerG                       or if you are posting via email sent to INFO-VAX,oI                       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, and_G                       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 or H                       such, the text of your message will be buried in aG                       large pile of gibberish, and some tools will send J                       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, mostcI                       newsreaders include a filter or killfile mechanism,sB                       and many mail clients have similar filteringE                       capabilities. Please do not "flame"-to email or1G                       to post vitriol - any individual that might annoy_F                       you, please enable and filter all of that user'sG                       postings. Posting of vitriol and of "flames" will I                       eventually come back to haunt you; netizens and theiJ                       net itself have a very large and a very long memory.G                       Similarly, readers that decide that your postings F                       are not worthy of reading will similarly tend toH                       filter or to killfile all of your postings. Please0                       play nice, in other words.  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:   4                    widftp://rtfm.mit.edu/pub/usenet/6                       news.answers/usenet/primer/part1  4                    widftp://rtfm.mit.edu/pub/usenet/3                       news.answers/usenet/faq/part1   4                    widftp://rtfm.mit.edu/pub/usenet/>                       news.answers/usenet/emily-postnews/part1  J                                                                        1-7 _   -- _  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: Mon, 11 Apr 2005 19:56:38 GMT # From: hoff@hp.nospam (Hoff Hoffman) = Subject: OpenVMS Frequently Asked Questions (FAQ), Part 10/11 1 Message-ID: <WDA6e.3494$IL.2475@news.cpqcorp.net>M    Archive-name: dec-faq/vms/part10 Posting-Frequency: quarterly Last-modified: 11 Apr 2005 Version: VMSFAQ_20050411-10.TXT                  7                    Information on Networks and Clusters         D                    And for earlier TCP/IP Services versions, use the                    command:M                      $ UCX;                    SET ROUTE/GATE=x.x.x.x/DEFAULT/PERMANENT   '           _____________________________ E           15.2.5  How can I set up reverse telnet (like reverse LAT)?   G                    Though it may seem obvious, Telnet and LAT are quite J                    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 for F                    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._  '           _____________________________fJ           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 willSH                    require authentication-and this will thus prevent RAS                    connections.   E                    Future versions of OpenVMS and TCP/IP Services mayoI                    add this, and future versions of Microsoft Windows mayoB                    permit operations with authentication disabled.  D           __________________________________________________________.           15.3  OpenVMS and DECnet Networking?  H                    The following sections contain information on OpenVMS)                    and DECnet networking.d                          15-4) T  F          7                    Information on Networks and Clusters       '           _____________________________g2           15.3.1  Can DECnet-Plus operate over IP?  C                    Yes. To configure DECnet-Plus to operate over IPtG                    transport and over IP backbone networks, install andpG                    configure DECnet-Plus, and install and configure theaJ                    PWIP mechanism available within the currently-installedI                    IP stack. Within TCP/IP Services, this is a PWIPDRIVER G                    configuration option within the UCX$CONFIG (versions G                    prior to V5.0) or TCPIP$CONFIG (with V5.0 and later) &                    configuration tool.  '           _____________________________aG           15.3.2  What does "failure on back translate address request"t                   mean?s  %                    The error message:   M                    BCKTRNSFAIL, failure on the back translate address requests  I                    indicates that the destination node is running DECnet-nI                    Plus, and that its naming service (DECnet-Plus DECdns,aD                    LOCAL node database, etc) cannot locate a name toE                    associate with the source node's address. In otheraH                    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.   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 sureAI                    that the node is entered into its own LOCAL namespace. I                    This can be a problem elsewhere, however. Very rarely, I                    a cache corruption has been known to cause this error.r7                    To flush the cache, use the command:   '                    $ RUN SYS$SYSTEM:NCL_?                    flush session control naming cache entry "*"n    J                                                                       15-5 t             7                    Information on Networks and Clusterse        J                    Also check to see that you are using the latest ECO forG                    DECnet-Plus for the version you are running. DECnet-a9                    Plus can use the following namespaces:   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.t  '           _____________________________r9           15.3.3  Performing SET HOST/MOP in DECnet-Plus?i  B                    First, issue the NCL command SHOW MOP CIRCUIT *  '                    $ RUN SYS$SYSTEM:NCLe%                    SHOW MOP CIRCUIT *   A                    Assume that you have a circuit known as FDDI-0nD                    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.d  J                    The system console power-up messages on a number of VAXG                    and Alpha systems will display the hardware address,OC                    particularly on those systems with an integratedJ4                    Ethernet network adapter present.                      15-6u G  e          7                    Information on Networks and Clustersl        C                    If you cannot locate a sticker on the system, ifhD                    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:                      HELPk  G                    A console command similar to one of the following isiB                    typically used to display the hardware address:                      SHOW DEVICE                     SHOW ETHERNET                    SHOW CONFIG  I                    On the oldest VAX Q-bus systems, the following console G                    command can be used to read the address directly off G                    the (DELQA, DESQA, or the not-supported-in-V5.5-and- 4                    later DEQNA) Ethernet controller:  %                    E/P/W/N:5 20001920l  E                    Look at the low byte of the six words displayed bytH                    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 networkeF                    controller installed such that the hardware addressB                    value is located at the system physical address                    20001920.)g  H                    If the system is a VAX system, and another VAX systemE                    on the network is configured to answer Maintenance C                    and Operations Protocol (MOP) bootstrap requests D                    (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 inwF                    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.   J                                                                       15-7               7                    Information on Networks and Clusters         B                    If the system is running, you can use DECnet orE                    TCP/IP to display the hardware address with one ofs*                    the following commands.  %                    $! DECnet Phase IV '                    $ RUN SYS$SYSTEM:NCP 2                    SHOW KNOWN LINE CHARACTERISTICS  !                    $! DECnet-Plus '                    $ RUN SYS$SYSTEM:NCL/4                    SHOW CSMA-CD STATION * ALL STATUS  3                    $! TCP/IP versions prior to V5.0_                    $ 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 hardware B                    address, reading the necessary information fromC                    the network device drivers. A complete example CFI                    program for reading the Ethernet or IEEE 802.3 network H                    controller hardware address (via sys$qio calls to theH                    OpenVMS network device driver(s)) is available at the!                    following URL:f  :                    o  http://www.hp.com/go/openvms/wizard/  H                    To use the DECnet Phase IV configurator tool to watchD                    for MOP SYSID activity on the local area network:  '                    $ RUN SYS$SYSTEM:NCPoM                    SET MODULE CONFIGURATOR KNOWN CIRCUIT SURVEILLANCE ENABLED   H                    Let the DECnet Phase IV configurator run for at leastD                    20 minutes, and preferably longer. Then issue the&                    following commands:  '                    $ RUN SYS$SYSTEM:NCP P                    SHOW MODULE CONFIGURATOR KNOWN CIRCUIT STATUS TO filename.txtN                    SET MODULE CONFIGURATOR KNOWN CIRCUIT SURVEILLANCE DISABLED                      15-8_ _  _          7                    Information on Networks and Clustersi        E                    The resulting file (named filename.txt) can now betH                    searched for the information of interest. Most DECnetG                    systems will generate MOP SYSID messages identifying H                    items such as the controller hardware address and theH                    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.   '           _____________________________sJ           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   '           _____________________________s>           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 (formerly G                    known as DECnet OSI), DECnet Phase IV, and HP TCP/IP 1                    Services (often known as UCX).o  I                    On OpenVMS versions prior to V7.1, DECnet Phase IV wasiJ                    integrated, and there was no installation question. YouI                    had to install the DECnet-Plus (DECnet/OSI) package onaH                    the system, after the OpenVMS upgrade or installation                    completed.o  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.1yE                    from a distribution kit, simply answer "NO" to the,J                    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 DECnetnI                    Phase IV binaries from the kit provided on the OpenVMSd-                    software distribution kit.   J                                                                       15-9               7                    Information on Networks and Clusters         E                    If you already have DECnet-Plus installed and wish F                    to revert, you must reconfigure OpenVMS. You cannotG                    reconfigure the "live" system, hence you must reboot F                    the system using the V7.1 distribution CD-ROM. ThenE                    select the DCL ($$$ prompt) option. Then issue thei                    commands:  9                    $$$ DEFINE/SYSTEM PCSI$SYSDEVICE DKA0: ?                    $$$ DEFINE/SYSTEM PCSI$SPECIFIC DKA0:[SYS0.]fO                    $$$ PRODUCT RECONFIGURE VMS /REMOTE/SOURCE=DKA0:[VMS$COMMON]d  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 DECnetfD                    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 System D                    Watchdog package can also send pages. The ProcessA                    Software package PMDF can route specific email_:                    addresses to a paging service, as well.                      15-10               7                    Information on Networks and Clusters         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._  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.   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.s  '           _____________________________ B           15.6.1  OpenVMS Cluster Communications Protocol Details?  D                    The following sections contain information on theI                    OpenVMS System Communications Services (SCS) Protocol.eJ                    Cluster terminology is available in Section 15.6.1.2.1.  '           _____________________________ ?           15.6.1.1  OpenVMS Cluster (SCS) over DECnet? Over IP?C  H                    The OpenVMS Cluster environment operates over variousE                    network protocols, but the core of clustering usesoF                    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, norW                    over IP._  9                    No SCS protocol routers are available.a  J                                                                      15-11               7                    Information on Networks and Clusters         F                    Many folks have suggested operating SCS over DECnetC                    or IP over the years, but SCS is too far down in B                    the layers, and any such project would entail aE                    major or complete rewrite of SCS and of the DECnetaD                    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 inG                    the rather more primitive contexts of the system andnJ                    particularly the bootstrap-to get SCS to operate over aI                    DECnet or IP connection would require relocating majornF                    portions of the DECnet or IP stack into the kernel.G                    (And it is not clear that the result would even meetc;                    the bandwidth and latency expectations.)y  D                    The usual approach for multi-site OpenVMS ClusterI                    configurations involves FDDI, Memory Channel (MC2), oraJ                    a point-to-point remote bridge, brouter, or switch. TheI                    connection must be transparent, and it must operate atlJ                    10 megabits per second or better (Ethernet speed), withI                    latency characteristics similar to that of Ethernet orlI                    better. Various sites use FDDI, MC2, ATM, or point-to- !                    point T3 link.e  '           _____________________________ D           15.6.1.2  Configuring Cluster SCS for path load balancing?  I                    This section discusses OpenVMS Cluster communications, J                    cluster terminology, related utilities, and command and&                    control interfaces.  '           _____________________________T*           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 differentnG                    local port, named PAA0, PAB0, PAC0 etc. All Ethernett>                    and FDDI busses make up a single PEA0 port.                        15-12 _  _          7                    Information on Networks and ClustersI        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 "VirtualEA                    Circuits" to enable communications between allS,                    available pairs of ports.  H                    SYSAP: A "system application" that communicates usingH                    SCS. Each SYSAP communicates with a particular remote1                    SYSAP. Example SYSAPs include:v  ;                    VMS$DISK_CL_DRIVER connects to MSCP$DISK G                    The disk class driver is on every VMSCluster system. J                    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$TAPEsG                    The tape class driver is on every VMSCluster system.oJ                    MSCP$TAPE is on all tape controllers and all VMSClusterI                    systems that have SYSGEN parameter TMSCP_LOAD set to 1n  <                    VMS$VAXCLUSTER connects to VMS$VAXCLUSTERD                    This SYSAP contains the connection manager, whichG                    manages cluster connectivity, runs the cluster stateaJ                    transition algorithm, and implements the cluster quorumG                    algorithm. This SYSAP also handles lock traffic, andsB                    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 TMSCP F                    The Mass Storage Control Protocol and the Tape MSCPE                    servers are SYSAPs that provide access to disk and H                    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- I                    based storage controllers, and within host-based MSCP-sF                    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.   J                                                                      15-13               7                    Information on Networks and Clusters         I                    SCS CONNECTION: A SYSAP on one node establishes an SCSpF                    connection to its counterpart on another node. ThisJ                    connection will be on ONE AND ONLY ONE of the available$                    virtual circuits.  '           _____________________________u5           15.6.1.2.2  Cluster Communications Control?c  G                    When there are multiple virtual circuits between twonH                    OpenVMS systems it is possible for the VMS$VAXCLUSTERG                    to VMS$VAXCLUSTER connection to use any one of thesedJ                    circuits. All lock traffic between the two systems will?                    then travel on the selected virtual circuit.   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 ittJ                    finds. Prior to enhancements found in V7.3-1 and later,H                    the load class is static and normally all CI and DSSII                    ports have a load class of 14(hex), while the Ethernet H                    and FDDI ports will have a load class of A(hex). WithG                    V7.3-1 and later, the load class values are dynamic.   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 must                     be disabled.   D                    In addition to the load class mechanisms, you canC                    also use the "preferred path" mechanisms of MSCPdE                    and TMSCP services. This allows you to control thedH                    SCS connections used for serving remote disk and tapeI                    storage. The preferred path mechanism is most commonlyaF                    used to explicitly spread cluster I/O activity overH                    hosts and/or storage controllers serving disk or tapeJ                    storage in parallel. This can be particularly useful if                      15-14 i             7                    Information on Networks and Clusterse        J                    your hosts or storage controllers individually lack theH                    necessary I/O bandwidth for the current I/O load, andI                    must thus aggregate bandwidth to serve the cluster I/O                     load.  E                    For related tools, see various utilities includingdI                    LAVC$STOP_BUS and LAVC$START_BUS, and see DCL commandsu0                    including SET PREFERRED_PATH.  '           _____________________________iI           15.6.1.2.3  Cluster Communications Control Tools and Utilities?   C                    In most OpenVMS versions, you can use the tools:o  0                    o  SYS$EXAMPLES:LAVC$STOP_BUS  1                    o  SYS$EXAMPLES:LAVC$START_BUSe  F                    These tools permit you to disable or enable all SCS9                    traffic on the on the specified paths.   I                    You can also use a preferred path mechanism that tells I                    the local MSCP disk class driver (DUDRIVER) which path I                    to a disk should be used. Generally, this is used with H                    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 thea"                    disk I/O level.  E                    Prior to V7.2, the preferred path feature uses thea                    tool:  -                    o  SYS$EXAMPLES:PREFER.MAR   G                    In OpenVMS V7.2 and later, you can use the following                     DCL command:f  '                    $ SET PREFERRED_PATH   D                    The preferred path mechanism does not disable norC                    affect SCS operations on the non-preferred path.d  D                    With OpenVMS V7.3 and later, please see the SCACPG                    utility for control over cluster communications, SCSwH                    virtual circuit control, port selection, and related.  J                                                                      15-15               7                    Information on Networks and Clusters       '           _____________________________g4           15.6.2  Cluster System Parameter Settings?  H                    The following sections contain details of configuring5                    cluster-related system parameters.   '           _____________________________aE           15.6.2.1  What is the correct value for EXPECTED_VOTES in aa                     VMScluster?   E                    The VMScluster connection manager uses the concept F                    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 calledaG                    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 resultantsI                    massive disk data corruptions. The quorum mechanism is H                    expressly intended to prevent your data from becoming&                    severely corrupted.  E                    On each OpenVMS node in a VMScluster, one sets twodC                    values in SYSGEN: VOTES, and EXPECTED_VOTES. ThenG                    former is how many votes the node contributes to theaF                    VMScluster. The latter is the total number of votesE                    expected when the full VMScluster is bootstrapped.a  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. ItoG                    does not. Further, an erroneous setting in EXPECTED_fC                    VOTES is automatically corrected once VMScluster H                    connections to other nodes are established; user dataG                    is at risk of severe corruptions during the earliestOG                    and most vulnerable portion of the system bootstrap,b@                    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 nodes C                    fail can be easily configured. With the two-node B                    configuration, one must use a primary-secondaryI                    configuration (where the primary has all the votes), a                       15-16 7  _          7                    Information on Networks and Clusters-        J                    peer configuration (where when either node is down, theF                    other hangs), or (preferable) a shared quorum disk.  A                    Use of a quorum disk does slow down VMSclustergA                    transitions somewhat - the addition of a thirdeF                    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.   1                                              Note   A                       The quorum disk must be on a non-host-based ?                       shadowed disk, though it can be protected D                       with controller-based RAID. Because host-basedB                       volume shadowing depends on the lock managerD                       and the lock manager depends on the connectionC                       manager and the connection manager depends oniA                       quorum, it is not technically feasible (nor F                       even particularly reliable) to permit host-basedB                       volume shadowing to protect the quorum disk.  G                    If you choose to use a quoum disk, a QUORUM.DAT fileLC                    will be automatically created when OpenVMS first H                    boots and when a quorum disk is specified - well, theI                    QUORUM.DAT file will be created when OpenVMS is bootedaG                    without also needing the votes from the quorum disk.n  A                    In a two-node VMScluster with a shared storageaF                    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 diskSH                    should be assigned to the OpenVMS host serving access                    to the disk.   C                    For information on quorum hangs, see the OpenVMS A                    documentation. For information on changing theoD                    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 OpenVMSo  J                                                                      15-17    -          7                    Information on Networks and Clustersd        J                    system console documentation for the processor-specificG                    console commands used to trigger the IPC (Interrrupt-C                    Priority Level %x0C; IPL C) handler. (IPC is notcE                    available on OpenVMS I64 V8.2.) AMDS, Availability C                    Manager, and the IPC handler can each be used toiD                    clear a quorum hang. Use of AMDS and AvailabilityJ                    Manager is generally recommended over IPC, particularlyH                    because IPC can cause CLUEXIT bugchecks if the systemG                    should remain halted beyond the cluster sanity timernJ                    limits, and because some Alpha consoles and most (all?)E                    Integrity consoles do not permit a restart after an                    halt.  ?                    The quorum scheme is a set of "blade guards"eE                    deliberately implemented by OpenVMS Engineering tohF                    provide data integrity-remove these blade guards atD                    your peril. OpenVMS Engineering did not implementG                    the quorum mechanism to make a system manager's lifewH                    more difficult- the quorum mechanism was specificallyH                    implemented to keep your data from getting scrambled.  '           _____________________________ E           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 anddH                    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 serverseF                    providing a path to the same device should have theE                    same allocation class (at the port, controller, or !                    server level).C  E                    Each disk (or tape) unit number used within a non- G                    zero disk (or tape) allocation class must be unique,5F                    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.u                      15-18               7                    Information on Networks and Clusters         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:.)_  '           _____________________________SH           15.6.2.2.1  How to configure allocation classes and Multi-Path                       SCSI?   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 might I                    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.)   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 portmI                    (PK) controller). Note that this won't work if the HSZaI                    is configured in multibus failover mode. In this case,eH                    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 toeJ                    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 thedH                    HSZ, you would have two UCBs in a multi-path set. TheI                    path information is used by the multi-path software toQ6                    distinguish between these two UCBs.  J                                                                      15-19 b             7                    Information on Networks and Clusters-        G                    The displayable path information describes the path; F                    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, H                    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 OpenVMSbE                    will force the controller letter to be the same onoE                    each node. Simply choosing "A" was easier and more G                    deterministic than negotiating the controller letteraJ                    between the nodes, and also parallels the solution usedF                    for this situation when DSSI or SDI/STI storage was                    used.  E                    To enable port allocation classes, see the SYSBOOTCE                    command SET/BOOT, and see the DEVICE_NAMING systemo                    parameter.f  D                    This information is also described in the Cluster=                    Systems and Guidelines for OpenVMS ClusterI*                    Configurations manuals.  '           _____________________________S=           15.6.3  Tell me about SET HOST/DUP and SET HOST/HSCS  I                    The OpenVMS DCL commands SET HOST/DUP and SET HOST/HSC$E                    are used to connect to storage controllers via theCI                    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:a  $                    On OpenVMS Alpha:  !           $ RUN SYS$SYSTEM:SYSMANa?           SYSMAN> IO CONNECT FYA0/NOADAPTER/DRIVER=SYS$FYDRIVERn                      15-20 i  l          7                    Information on Networks and Clusterso        "                    On OpenVMS VAX:  !           $ RUN SYS$SYSTEM:SYSGENa(           SYSGEN> CONNECT FYA0/NOADAPTER  G                    Alternatives to the DCL SET HOST/DUP command include I                    the console SET HOST command available on various mid-O2                    to recent-vintage VAX consoles:  G                    Access to Parameters on an Embedded DSSI controller:   ?           SET HOST/DUP/DSSI[/BUS:{0:1}] dssi_node_number PARAMS   C                    Access to Directory of tools on an Embedded DSSI                     controller:  ?           SET HOST/DUP/DSSI[/BUS:{0:1}] dssi_node_number DIRECTT  C                    Access to Parameters on a KFQSA DSSI controller:   ;           SHOW UQSSP ! to get port_controller_number PARAMSo:           SET HOST/DUP/UQSSP port_controller_number PARAMS  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 they%                    console HELP text.d  A                    EK-410AB-MG, _DSSI VAXcluster Installation and C                    Troubleshooting_, is a good resource for setting C                    up a DSSI VMScluster on OpenVMS VAX nodes. (ThiseE                    manual predates coverage of OpenVMS Alpha systems,cG                    but gives good coverage to all hardware and software_I                    aspects of setting up a DSSI-based VMScluster-and mostrE                    of the concepts covered are directly applicable to I                    OpenVMS Alpha systems. This manual specifically coversEF                    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 thed0                    OpenVMS host see Section 5.7.    J                                                                      15-21 P             7                    Information on Networks and ClustersV      '           _____________________________o8           15.6.4  How do I rename a DSSI disk (or tape?)  G                    If you want to renumber or rename DSSI disks or DSSIdI                    tapes, it's easy-if you know the secret incantation...                        From OpenVMS:  *                    $ RUN SYS$SYSTEM:SYSGEN1                    SYSGEN> CONNECT FYA0/NOADAPTER                     SYSGEN> ^Z L                    $ 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> EXIT                     ...  D                    From the console on most 3000- and 4000-class VAXD                    system consoles... (Obviously, the system must be0                    halted for these commands...)  #                    Integrated DSSI:   H                    SET HOST/DUP/DSSI[/BUS:[0:1]] dssi_node_number PARAMS                      KFQSA:i  C                    SET HOST/DUP/UQSSP port_controller_number PARAMSt  D                    For information on how to get out into the PARAMSE                    subsystem, also see the HELP at the console promptaG                    for the SET HOST syntax, or see the HELP on SET HOSTiG                    /DUP (once you've connected FYDRIVER under OpenVMS).e  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 DSSI I                    ISE-this causes each DSSI ISE to use the specfied unitYG                    number and not use the DSSI node as the unit number.CJ                    Other parameters of interest are NODENAME and ALLCLASS,J                    the node name and the (disk or tape) cluster allocation                    class.   C                    Ensure that all disk unit numbers used within anhH                    OpenVMS Cluster disk allocation class are unique, andG                    all tape unit numbers used within an OpenVMS Cluster H                    tape allocation class are also unique. For details on                      15-22 v  s          7                    Information on Networks and Clusters         I                    the SCS name of the OpenVMS host, see Section 5.7. Fore?                    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  '           _____________________________ C           15.6.6  Which files must be shared in an OpenVMS Cluster?   G                    The following files are expected to be common across_H                    all nodes in a cluster environment, and though SYSUAFA                    is very often common, it can also be carefullyvD                    coordinated-with matching UIC values and matchingC                    binary identifier values across all copies. (The G                    most common use of multiple SYSUAF files is to allowaI                    different quotas on different nodes. In any event, thelJ                    binary UIC values and the binary identifier values mustI                    be coordinated across all SYSUAF files, and must match I                    the RIGHTSLIST file.) In addition to the list of files H                    (and directories, in some cases) shown in Table 15-1,F                    please review the VMScluster documentation, and the3                    System Management documentation.m  J           ________________________________________________________________1           Table 15-1  Cluster Common Shared Files   J                    _______________________________________________________J                    Filename___________________Default_Specification_______  =                    SYSUAF                     SYS$SYSTEM:.DATr  =                    SYSUAFALT                  SYS$SYSTEM:.DATa  =                    SYSALF                     SYS$SYSTEM:.DATt  =                    RIGHTSLIST                 SYS$SYSTEM:.DATi  =                    NETPROXY                   SYS$SYSTEM:.DATf  =                    NET$PROXY                  SYS$SYSTEM:.DATl  =                    NETOBJECT                  SYS$SYSTEM:.DAT   =                    NETNODE_REMOTE             SYS$SYSTEM:.DAT   H                    QMAN$MASTER                SYS$SYSTEM:; this is a set>                                               of related files  J                                                                      15-23               7                    Information on Networks and Clusters       J           ________________________________________________________________9           Table 15-1 (Cont.)  Cluster Common Shared Files_  J                    _______________________________________________________J                    Filename___________________Default_Specification_______  =                    LMF$LICENSE                SYS$SYSTEM:.LDBr  >                    VMSMAIL_PROFILE            SYS$SYSTEM:.DATA  =                    VMS$OBJECTS                SYS$SYSTEM:.DATm  >                    VMS$AUDIT_SERVER           SYS$MANAGER:.DAT  >                    VMS$PASSWORD_HISTORY       SYS$SYSTEM:.DATA  >                    NETNODE_UPDATE             SYS$MANAGER:.COM  >                    VMS$PASSWORD_POLICY        SYS$LIBRARY:.EXE  =                    LAN$NODE_DATABASE          SYS$SYSTEM:.DATs  >                    VMS$CLASS_SCHEDULE         SYS$SYSTEM:.DATA  H                    SYS$REGISTRY               SYS$SYSTEM:; this is a setJ           ____________________________________of_related_files____________  I                    In addition to the documentation, also see the currentrG                    version of the file SYS$STARTUP:SYLOGICALS.TEMPLATE. F                    Specifically, please see the most recent version ofJ                    this file available, starting on or after OpenVMS V7.2.  G                    A failure to have common or (in the case of multiple F                    SYSUAF files) synchronized files can cause problemsG                    with batch operations, with the SUBMIT/USER command,eJ                    with the general operations with the cluster alias, andE                    with various SYSMAN and related operations. ObjectrC                    protections and defaults will not necessarily be D                    consistent, as well. This can also lead to systemI                    security problems, including unintended access denialssG                    and unintended object accesses, should the files andeJ                    particularly should the binary identifier values become                    skewed.  '           _____________________________t8           15.6.7  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.                      15-24 o             7                    Information on Networks and Clustersn        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, youk0                    want a way to recover, right?  D                    Create standalone BACKUP kits for the OpenVMS VAXF                    systems, and create or acquire bootable BACKUP kits1                    for the OpenVMS Alpha systems.t  I                    Use CLUSTER_CONFIG or CLUSTER_CONFIG_LAN to remove the I                    various system roots and to shut off boot services and '                    VMScluster settings.c  E                    Create as many architecture-specific copies of thewI                    system disks as required. Realize that the new systemsSF                    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                    Reset the VAXCLUSTER and NISCS_LOAD_PEA0 parameters to 4                    0 in SYSGEN and in MODPARAMS.DAT.  E                    Clobber the VMScluster group ID and password using                     SYSMAN.  J                    Reboot the systems seperately, and run AUTOGEN on each.  E                    Shut off MOP services via NCP or LANCP on the boott                     server nodes.  H                    Permanent seperation also requires the duplication ofI                    shared files. For a list of the files commonly shared,a-                    please see Section 15.6.6.a  J                    Also see the topics on "cluster divorce" in the Ask The                    Wizard area.   :                    o  http://www.hp.com/go/openvms/wizard/  J                                                                      15-25    C          7                    Information on Networks and Clusters         D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the available B                    ATW Wizard.zip archive, please see Section 3.8.  D                    Information on changing node names is included in                    Section 5.7.e  '           _____________________________ .           15.6.8  Details on Volume Shadowing?  I                    This section contains information on host-based volume J                    shadowing; on the disk mirroring capabilities available"                    within OpenVMS.  '           _____________________________ G           15.6.8.1  Does volume shadowing require a non-zero allocation                      classes?  C                    Yes, use of host-based Volume Shadowing requires$H                    that the disk(s) involved be configured in a non-zero$                    allocation class.  I                    Edit SYS$SYSTEM:MODPARAMS.DAT to include a declarationSG                    of an non-zero allocation class, such as setting the 8                    host allocation class to the value 7:                       ALLOCLASS = 7  7                    Then AUTOGEN the system, and reboot.   F                    You should now be able to form the shadow set via a1                    command such as the following:h  O                    $ MOUNT dsa1007: /SHADOW=($7$dkb300:,$7$dkb500:) volumelabelC  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 opportunity G                    to move to a device-independent scheme using logical G                    name constructs such as the DISK$volumelabel logical I                    names in your startup and application environments; an F                    opportunity to weed out physical device references.  I                    Allocation class one is used by Fibre Channel devices; J                    it can be best to use another non-zero allocation classH                    even if Fibre Channel is not currently configured and)                    not currently planned.U                      15-26 $  C                            J           ________________________________________________________________           Index     4           1858                              AMD,2-13=             17-Nov-1858,4-1                 AMD64,2-12,  2-13t=           2000                                Terminology,2-4i8           __Year,5-39___________________    ANSI C,10-183           A                                 AP,10-7 7           ______________________________    Apache,13-8 9           Access Control List Entry,        APB.EXE,14-10l7              5-13                           Archie,13-7u:           ACCVIO,5-39                       Archival MediaE           ACE,5-13                            DVDarchive/restore,9-10l=           ACPI,14-25                        Archive.Org,14-49 ?           Acrobat,13-7                      ARCH_DEFS.REQ,10-14 A           ACS,5-60                          Argument Pointer,10-7hE           ACTS,4-9                          ARRE,14-53,  14-54, 14-56cE           Adobe                             ARWE,14-53,  14-54, 14-56   0             Acrobat,13-7                    ASAP  6             PDF,13-7                          See DSPPG           Advanced Server,5-4               Ask The Wizard,3-11,  5-27,bJ           AEST,13-18,  13-24                   5-29, 5-30, 5-37, 8-8, 9-3,F           Agnew, Jim,14-40                     10-2, 10-4, 10-8, 10-9,I           Allocation Class                     10-16, 10-21, 10-25, 15-1,d@             Fibre Channel,15-26                15-2, 15-3, 15-266             Non-Zero,15-26                    See ITRC6             Volume Shadowing,15-26          ASMP,14-15F           ALLOCLASS system parameter,       Asymmetric Multiprocessing              15-266           Alpha,2-13                          See ASMPH             Terminology,2-4                 ATA,7-1,  9-5, 14-28, 14-32,J           AlphaPC 164LX,14-28                  14-52, 14-53, 14-54, 14-55,;           AlphaPC 164SX,14-28                  14-63, 14-64 ?           AlphaServer ES47                  ATAPI,14-63,  14-64 7             Time,4-24                       Athlon,2-13sH           AlphaServer ES80                  ATW,3-11,  5-27, 5-29, 5-30,J             Time,4-24                          5-37, 8-8, 9-3, 10-2, 10-4,H           AlphaServer GS1280                   10-8, 10-9, 10-16, 10-21,G             Time,4-24                          10-25, 15-1, 15-2, 15-3, 4           AlphaStation XP1000,14-48            15-266           AMASK,14-36,  14-37                 See ITRC8           Ambassador,1-10                   AUTOGEN,5-14  J                                                                    Index-1                                   Index        C           Automatic foreign command,8-3     Boot Alias,14-9,  14-22s>           Automatic Foreign Command,8-4     Boot Aliases,14-22;           AVI,7-3                           Bootblock,14-20 5           ______________________________    Bootstrap 9           B                                   Alpha,14-10 6           ______________________________      I64,14-97           Backdoor,5-10                       VAX,14-12tB           Backdrop,11-8                     BOOT_OPTIONS.COM,14-228           Backdrops,11-8                    Browser,13-4C           BACKUP,5-20,  9-16                Byers, Robert Alan,13-8 ;           BACKUP/IGNORE=INTERLOCK,5-54      Byte lane,14-38a7           Bad Block Handling,9-3            bzip2,13-25 J           BADLIB,13-22                      ______________________________-           BADTYPSTR,13-22                   CoJ           bash,13-17                        ______________________________;           Batch,13-21                       C,10-18,  10-25 F           BB_WATCH,4-5                        Compaq C Compiler,10-18,6           BC16E,14-56,  14-60                    10-25J           BCC08,14-59                         DEC C Compiler,10-18,  10-25B           BCKTRNSFAIL,15-5                    Device Drivers,10-22I           Berryman, Mark,1-4,  13-3           HP C Compiler,10-18,  10-25-B           Bi-Endian,10-17                     VAX C Compiler,10-183           Big-Endian,10-17                  C2,5-51c:           BIND,15-6                         CA,5-3,  14-212           Blackbox,14-57                    Caesar8           Bliss                               Julius,4-28             Architecture Flags,10-14        CalTech,13-8I             BLISS32E,10-14                  Campus Software License Grant_6             BLISS32I,10-14                    See CSLGJ             BLISS32V,10-14                  Carrier Sense Multiple Access,E             BLISS64E,10-14                     with Collision Detect, 4             BLISS64I,10-14                     14-62.             Compiler,10-14                  CDA             Rebuilding System Libraries,      embossed media,9-12eC                10-14                          Recording,9-8,  14-55o8           Block                             CD-Audio,7-19             Disk,2-24                       CD Player,7-1fB           BMC,14-33                         CD-R,9-8,  13-9, 14-55>           BN24H,14-58                       CD-R/RW,9-7,  9-10F           BN24J,14-58                       CDRECORD,9-7,  9-8, 14-55,4           BNC,14-47                            14-64?           BNU Bookreader,3-1                CDRECORD-ProDVD,9-8            Bookreader             BNU,3-1i             MGBOOK,3-1                      Index-2 t                                 Index        I           CDRTOOLS,9-7,  9-8, 14-64         Conversational bootstrap,5-7,eA           CD-RW,9-8,  13-9, 14-55              14-9, 14-10, 14-15 5           CDWRITE,9-8                       COPY,10-9V6           CGI,13-20                         CPAN,13-246           CHARON-VAX,13-26                  CRAM,14-388           CHECKSUM,5-43                     $creprc,10-9/           CHECKSUM/ALGORITHM=MD5,5-43       CSAl6           Clam,5-4                            See DSPP5           cli$get_value,10-4                CSLG,2-10 9           Clock                             CSMA/CD,14-62C5             TODR,4-5,  4-7                  CSWB,13-4t5             TOY,4-5,  4-7                     See SWBf  J           Clockmeister, Ulysses T.          ______________________________  -             See Time                        D J           CLUEXIT,15-18                     ______________________________6           Cluster                           4D20,14-486             Disk,2-24                       3D30,14-48C           Cluster Load Balancing,15-14      Dachtera, David J.,13-8n?           Cluster Terminology,15-12         Data Remanence,5-57i:           CMA$RTL.EXE,10-25                 Datatrieve,3-4:           CMS,13-21                         DATMISCH,10-17G           00CMS,13-21                       Daylight Savings Time,4-15, @           01CMS,13-21                          4-21, 4-27, 10-22F           Columbia University,13-3          DAYLIGHT_SAVINGS.COM,4-15,3           COM1,14-5,  14-16                    4-17aD           COM2,14-5,  14-16                 DB9,14-57,  14-59, 14-60?           COMMON,10-6                       DCE DTS,4-10,  4-16 9           Compaq,5-38                       DCL,3-3,  3-7   H           Compaq Secure Web Browser           Automatic foreign command,  4             See SWB                              8-3A           Composer                            Foreign command,8-3nC             Mozilla,13-18                     Lexical functions,8-3o6           Computer Associates,5-3,            PIPE,8-99              14-21                            Symbols,8-1t8           console,14-6,  14-15              DCL$PATH,8-45           Console,14-5                      DCPS,12-3 5             VAXstation 3100,9-4             DCX,13-25c4           Console Backdoor,5-10             DDB,10-98           CONSOLE environment variable,     DEASSIGN,8-3A              14-15                          Deathrow Cluster,2-16n4           Contrl,13-12                      DebuggerH                                               Signalling SS$_DEBUG,10-16  J                                                                    Index-3    k                              Index        J           DEC-423,14-56                     DEVICE_NAMING system parameter5           DECalert,15-10                       ,15-20rF           DECC$CRTL.EXE,10-25               DFU,5-63,  9-1, 9-4, 13-13>           DECconnect,14-56                  DIAGBOOT.EXE,14-139           DECdns,15-6                       DIAGNOSE,5-38 =           DECdocument,vi                    Dictionary attack ;           DECDTLOGO,11-9                      Password,5-50iJ           DECdtss,4-9                       DIGITAL Network Products Group5           DECevent,5-38                        ,14-44w@           DECmigrate,13-18,  13-24,         Digital Synergy,13-9G              13-26                          Digital Versatile Disk,9-11s5           DECnet,14-63                      Discountsn6             Asynchronous,14-62                See DSPP0             DECNET_REGISTER,15-5            Disk8             MOP,15-6                          Block,2-24:           DECprint,12-3                       Cluster,2-24A           DECsound,7-3                        Data Remanence,5-57p:           DEC Test Manager,13-22              Erasure,5-579           DECthreads,10-25                    Sector,2-24 ;           DECUS,1-9                           Security,5-57   >             See User Group                  Disk Mirroring,9-2B             Hobbyist Licenses,2-9             See Volume Shadowing1           DECUServe,1-2                     DisksuJ           DECUS Software Library,13-3         ATA,7-1,  9-5, 14-28, 14-32,E           DECW$CDPLAYER,7-1                      14-52, 14-53, 14-54,n6           DECW$CDPLAYER.C,14-64                  14-55D           DECW$EXAMPLES:DECW$CDPLAYER.C       Bad Block Handling,9-38              ,14-64                           CD-R,14-55@           DECW$KEYMAP Logical Name,           CD-R/RW,9-7,  9-10?              11-10                            CD-Recordable,9-8cA           DECwindows Transport,11-17          DVD+R/RW,9-7,  9-10 ;           DECwindows V1.2-6,11-17             dvd200i,14-55 A           DECwindows V1.3,11-17               DVD-R/RW,9-7,  9-10M@           DEFINE,8-3                          DVD-Recordable,9-8<           DELETE                              FAT Format,7-28             Undelete,9-1                      Floppy,7-2J           Descriptor,10-10                    IDE,7-1,  9-5, 14-28, 14-32,E           Deutsch,1-2                            14-52, 14-53, 14-54,   6           Developer Programs                     14-55  ;             See DSPP                          Jumpers,14-49s6           Device Driver,10-9                  MSCP,9-3;           Device Drivers                      PC Format,7-2 F             C,10-22                           PlexWriter,14-55,  14-63              Floating Point,10-22                      Index-4                                   Index        D           Disks (cont'd)                    DTSS$NTP_PROVIDER.C,4-10F             SCSI,9-3,  9-14, 14-2,          DTSS$SET_TIMEZONE.EXE,4-16E                14-28, 14-32, 14-34,         DTSS$UTC_STARTUP.COM,4-20e0                14-41, 14-49, 14-52,         Dump;                14-53, 14-54, 14-55,           Process,10-27 5                14-56                        DVD,14-55l;             SCSI-2,9-6                        Recording,9-8 B             Volume Set,9-7                  DVD+R,9-8,  9-10, 13-98             Zip,14-55                       DVD+R/RW,9-7D           Disk Shadowing,9-2                DVD+RW,9-8,  13-9, 14-649           Distribution Kits,2-8             dvd200i,14-55sC           DJE Systems,13-8                  DVDarchive/restore,9-10-<           DKDRIVER,14-63,  14-64            DVD-R,9-8,  13-9?           DLT VS80,14-54                    DVD-R/RW,9-7,  9-10 9           DNDRIVER,14-64                    DVD-RAM,14-64 F           DNPG,14-44                        DVDRTOOLS,9-7,  9-8, 14-64=           DNS,15-6                          DVD-RW,9-8,  13-9 J           DOCUMENT,10-16                    DVDwrite,9-7,  9-8, 9-9, 14-648             See DECdocument                 Dvorak,11-10G           DoD,5-57                          Dynamic System Recognition,k4           DOD_ERAPAT,5-58                      14-25J           Download Kits,2-8                 ______________________________-           DQDRIVER,7-1,  9-5, 14-32,        EmJ                                             ______________________________3              14-55, 14-63, 14-64            EB,2-24a6           Driver                            EBCDIC,7-3E             Device,10-9                     e-Business Infrastructure :           DRVERR,14-53,  14-56                 Package,2-7/           DSPP,2-11,  2-15, 2-20            ECOr7           DSR,14-25                           kits,5-31o>           DSSI,5-58                         Edit Version,10-26I           DST,4-15,  4-17, 4-21, 4-27,      EFI,5-8,  14-9, 14-20, 14-22,a;              10-22                             14-23, 14-33 G           DTM,13-21,  13-22                 EFI Boot Alias,14-9,  14-22 9           00DTM,13-22                       EIA-232,14-57 D           01DTM,13-22                       ELSA GLoria Synergy,5-284           DTSS,4-9,  4-10, 4-16             ELV,5-387             DTSS$CLERK,4-22                 elvis,13-16 =             Too Few Servers Detected,       EM64T,2-12,  2-13 =                4-23                           Terminology,2-4i7           DTSS$CLERK,4-22                   Emacs,13-16 ?           DTSS$INSTALL_TIMEZONE_RULE.COM    embossed media,9-12 5              ,4-20                          Encompass   <                                               See User GroupC                                               Hobbyist Licenses,2-9   J                                                                    Index-5    e                              Index        I           Encompasserve,1-2,  2-16          Extensible Firmware InterfaceP5           Encompass Software Library,         See EFI J              13-3                           ______________________________-           Endian-ness,10-17                 FhJ           Engineering Software,7-2          ______________________________9           Ensoniq,7-3                       f$getenv,14-8i7           Enterex                           f$parse,8-2 8             Hobbyist Licenses,2-9           f$trnlnm,8-39           Enterprise Operating              f$unique,5-63r@              Environment                    Facility Prefix,10-2>             See EOE                         FAQ Sections (Old)G           EOE,2-6                             DCL$PATH Logical Name,8-4 6           EPIC,14-33                          DCL1,8-38           $erapat,5-58                        DCL10,8-108           Erasure,5-57                        DCL11,8-108           Ergonomic Solutions,15-10           DCL12,8-116           Error analysis,5-38                 DCL3,8-56           Error Log Viewer                    DCL4,8-56                                               DCL5,8-66             See ELV                           DCL6,8-76           ES47                                DCL7,8-76             Time,4-24                         DCL8,8-86           ES80                                DCL9,8-9E             Time,4-24                         DECw$IGNORE_WORKSTATION.B           ETAPE,7-3                              Logical Name,11-58           Ethernet,14-62                      DECw1,11-19           Event Flags,11-12                   DECw10,11-7e:           EWS,11-3                            DECw11,11-12:           Exabyte,2-24                        DECw12,11-13:           Examples,10-3                       DECw13,11-13:           EXE$GL_TICKLENGTH,4-13              DECw14,11-14:           EXE$GL_TIMEADJUST,4-13              DECw15,11-16:           EXE$GL_TODR,4-4                     DECw16,11-17:           EXE$GQ_SAVED_HWCLOCK,4-6            DECw17,11-178           EXE$GQ_SYSTIME,4-3,  4-6            DECw2,11-38           EXE$GQ_TDF,4-16                     DECw3,11-38           EXE$GQ_TODCBASE,4-3                 DECw4,11-49           EXE$SETTIME,4-4                     DECw5,11-10e8           Executable Image,10-8               DECw6,11-48           EXPECTED_VOTES system               DECw9,11-6=              parameter,15-16                  DECwindows,11-1   6           Explicitly Parallel                 Doc1,3-17              Instruction Computing            Doc10,3-5 7             See EPIC                          Doc11,3-6o7                                               Doc13,3-9                       Index-6                                   Index        G           FAQ Sections (Old) (cont'd)       FAQ Sections (Old) (cont'd)t  9             Doc14,3-11                        Mgmt32,5-35 9             Doc2,3-2                          Mgmt33,5-35w9             Doc4,3-5                          Mgmt34,5-38e9             Doc5,3-5                          Mgmt35,5-52 9             File1,9-1                         Mgmt36,15-4 9             File2,9-1                         Mgmt37,5-38m9             File3,9-2                         Mgmt38,5-39S9             File4,9-3                         Mgmt39,5-39 7             File5,9-4                         Mgmt4,5-6_9             File6,9-7                         Mgmt40,5-40a9             File7,9-7,  9-10                  Mgmt41,5-40a:             File8,9-14                        Mgmt42,15-199             File9,9-14                        Mgmt43,5-42 :             Intro1,1-2                        Mgmt44,15-23:             Intro2,1-2                        Mgmt45,15-249             Intro3,1-3                        Mgmt46,5-43nI             Intro4,1-3                        Mgmt47,15-12,  15-14, 15-15o9             Intro5,1-5                        Mgmt48,5-43d9             Intro6,1-8                        Mgmt49,5-43 >             Intro7,1-3                        Mgmt5,5-7,  5-119             Intro8,1-9                        Mgmt50,5-4409             Mgmt1,5-1                         Mgmt51,5-45r9             Mgmt10,15-16                      Mgmt52,5-46:9             Mgmt11,5-14                       Mgmt53,5-46O:             Mgmt12,5-56                       Mgmt54,15-269             Mgmt13,15-20                      Mgmt56,5-46e9             Mgmt14,15-9                       Mgmt57,5-47 9             Mgmt15,5-15                       Mgmt58,15-6 9             Mgmt16,5-16                       Mgmt59,5-47 8             Mgmt17,5-23                       Mgmt6,15-29             Mgmt18,5-24                       Mgmt60,5-49l:             Mgmt19,5-25                       Mgmt61,15-189             Mgmt2,5-2                         Mgmt62,5-50C9             Mgmt20,5-55                       Mgmt63,5-59S9             Mgmt21,5-26                       Mgmt64,5-53l8             Mgmt23,5-27                       Mgmt9,5-129             Mgmt24,5-28                       Misc12,12-3m9             Mgmt25,5-30                       Misc13,12-3d:             Mgmt26,15-22                      Misc15,15-109             Mgmt27,5-31                       Misc17,15-9s:             Mgmt28,15-3                       Misc19,15-118             Mgmt3,5-4                         Misc2,12-19             Mgmt30,5-32                       Misc20,12-4a9             Mgmt31,5-33                       Misc4,14-59d  J                                                                    Index-7 d                                 Index        G           FAQ Sections (Old) (cont'd)       FAQ Sections (Old) (cont'd)e  8             Misc6,15-5                        Time4,4-158             Misc7,15-6                        Time5,4-207             Misc9,15-4                        Time6,4-9b8             Prog1,10-2                        Time7,4-138             Prog10,10-7                       Time8,4-127             Prog11,10-8                       Time9,4-7 7             Prog12,10-9                       Util1,7-1 7             Prog13,10-10                      Util2,7-2 7             Prog14,2-22                       Util3,7-3 7             Prog15,2-23                       Util5,7-3 7             Prog16,10-12                      Util6,7-4I6             Prog17,10-13                      VAX8,4-36             Prog18,10-14                      VMS1,2-18             Prog19,10-15                      VMS10,2-118             Prog2,10-4                        VMS11,2-118             Prog20,10-16                      VMS12,2-158             Prog21,10-16                      VMS13,2-168             Prog22,10-17                      VMS14,2-188             Prog23,10-17                      VMS15,2-188             Prog3,10-5                        VMS16,2-198             Prog4,10-5                        VMS17,2-206             Prog5,10-5                        VMS2,2-36             Prog7,10-5                        VMS3,2-46             Prog8,10-6                        VMS4,2-46             Prog9,10-7                        VMS5,2-56             Soft1,13-1                        VMS7,2-56             Soft10,8-9                        VMS8,2-8=             Soft12,13-22                      VMS9,2-9,  2-11 ;             Soft13,13-24                    Farmer, Ken,1-2n9             Soft14,13-25                    FAT Disks,7-2 5             Soft2,13-15                     FFT,13-12 9             Soft3,13-18                     $filescan,9-4 ;             Soft4,13-19                     FILE tool,13-13t>             Soft5,10-18                     File Versions,5-62:             Soft6,13-20                     Firmware,14-235             Soft7,13-21                     FISH,13-3 D             Soft8,13-21                     Flat-panel display,14-48?             Time1,4-1                       Floating Point,10-6NB             Time10,4-22,  4-24                Device Drivers,10-226             Time11,4-2                      Floppy,7-27             Time12,4-26                     FLORIAN,9-1n6             Time13,4-21                     $flush,9-2             Time2,4-7r             Time3,4-11                      Index-8    t                              Index        J           FOE,2-6                           ______________________________-           Fonts,11-18                       H J           Foreign command,8-3               ______________________________A           Foreign Command,8-4               H8571-A,14-60,  14-61 A           Fortran,10-7                      H8571-B,14-59,  14-60 A           Foundation Operating              H8571-C,14-59,  14-60rA              Environment                    H8571-D,14-59,  14-60S9             See FOE                         H8571-E,14-60 9           Freeware,9-4,  10-4, 10-16        H8571-J,14-60 9             SETCLOCK,4-13                   H8572-0,14-60hA           ftso,13-25                        H8575-A,14-60,  14-61 9           ftsv,13-25                        H8575-B,14-60e9           ______________________________    H8575-D,14-60 9           G                                 H8575-E,14-60 :           ______________________________    H8577-AA,14-60<           GB,2-24                           half-flash,14-19@           $getdvi,10-2                      Hard Partitions,14-84           $getjpi,10-2                      Hardware@           $getqui,5-51                        Serial Number,10-7D           $getsyi,10-2,  14-2               Harmless signature,14-20?           Gigabyte,2-24                     $hash_password,5-51 5           GKDRIVER,14-64                    HBMM,5-60eC           GKTEST.C,14-64                    Helliesen, Gunnar,14-40i>           Global Maintech,14-21             Hemker, Mark,13-108           gmake,13-13                       Heroix,14-21E           GMT,4-27                          Heuser-Hofmann, Eberhard,i6           GNM,10-16                            Dr.,9-99           GNU,13-17                         Hobbyist,2-10t0           GnuPG,13-5                        HourE           GNU Privacy Guard,13-5              Off By One,4-21,  4-27,_6           GNV,13-17                              10-22  D           Google,1-3                        HP OpenVMS for Integrity6           GPG,13-5                             Servers  =           Grace,13-9                          See OpenVMS I64 7           GS1280                            HP-UX,10-17S6             Time,4-24                       HSG80,5-60:           GTK,13-11                         ht://Dig,13-136           GUID,14-22                        HTML,10-16<           gzip,13-25                        HTTP_SERVER,13-3      J                                                                    Index-9                                   Index        J           ______________________________    Interrrupt Priority Level %x0C6           I                                    Handler;           ______________________________      See IPC,15-18 7           I64,2-13,  14-25, 14-33           Inv Cmd,5-8 :             Terminology,2-4,  14-33         INVRECTYP,5-20D           IA-32,2-12,  2-14                 IO$_DIAGNOSE,7-1,  14-64=             Terminology,2-4                 IOC$READ_IO,14-38_>           IA-64                             IOC$WRITE_IO,14-388             Terminology,2-4                 Iomega,14-558           IA-64 Architecture,2-13,          IPB.EXE,14-95              14-25, 14-33                   IPC,15-18 6           IARGCOUNT,10-7                    IRC Client;           iasi64,10-28                        Mozilla,13-18 4           IDE,7-1,  9-5, 14-28, 14-32,      IRIG,4-9@              14-52, 14-53, 14-54, 14-55,    ISO-9660,9-9,  14-230              14-63                          ISVN6           Identifier,5-2                      See DSPPG             Subsystem,10-8                  Itanium,2-13,  2-14, 14-25, 4           Image                                14-33=             Executable,10-8                   Terminology,2-4AD             Loadable,10-9                   Itanium Processor Family             Protected,10-89             Shareable,10-8                    See Itanium_A             System,10-8                     ITRC,1-1,  3-12, 5-30 E             UWSS,10-8                         FTP ECO site,1-1,  5-30 A           IMAGELIB.OLB,10-17                  Support Forums,5-30iJ           ImageMagick,13-6                  ______________________________-           IMAGENAME.DMP,10-27               J J           IMPLVER,14-37                     ______________________________6           InfoServer,9-10                   J2EE,13-198             Scribe,9-9                      Jameco,14-616           INFO-VAX,1-3,  1-7                Java,13-19<           INITIALIZE,5-39                   JBC$COMMAND,5-313           INITIALIZE/ERASE,5-58             JCL,7-3O;           Install,5-22                      JDK,2-7,  13-19n:           INSTALL,10-8,  10-9               JetDirect,15-2=           INSTALL utility,5-1               Jones, David,13-3 5           Integrity,2-12,  2-14, 14-33      Jouk,13-2 :             Terminology,2-4                 Julian Day,4-19           Integrity rx2600,14-60            Jumpers,14-49l             Intel,2-13,  2-14s             Interex_               See User Group                      Index-10i p                                 Index        A           ______________________________    lib$table_parse,10-15M<           K                                 lib$tparse,10-15A           ______________________________    lib$trim_filespec,9-4 9           KA630,14-6                        LIB.L32,10-14o9           KA650,14-6                        LIB.L64,10-14a9           KA655,14-6                        LIB.R64,10-14p9           Kb,2-25                           LIB.REQ,10-14eF           KB,2-24,  2-25                    License,5-12,  10-7, 11-5,3           Kednos,13-18                         12-5sE           Kerberos,5-51,  11-18             License Unit Requirements >           Kermit,13-3                          Table,2-9, 5-49:           Keyboard                          Licensing,10-7>             Dvorak,11-10                    Licensing ProgramsE           Key Mapping,11-10                   Campus Software Licensee;           ki,14-21                               Grant,2-10oD           Kilobit,2-25                        Developers,2-11,  2-20>           Kilobyte,2-24,  2-25                DSPP,2-11,  2-20>           KI Products,14-21                   Educational,2-10;           Kits,2-8                            Hobbyist,2-10t9           KVM switch,14-46                  Liebert,13-10eE           ______________________________    Limited Hardware Release,i4           L                                    10-26(           ______________________________5           LAN$NODE_DATABASE,15-24             See LHRa7           LAVC$START_BUS,15-15              linda,13-10 2           LAVC$STOP_BUS,15-15               Linker9           LBX,11-18                           COMMON,10-6i=           LCD,14-48                           PSECT_ATTR,10-6t@           LCD flat-panel display,14-46        SYMBOL_VECTOR,10-6A           Levitte,13-8                        SYS$BASE_IMAGE,10-5A:           Lexical functions,8-3               SYS.STB,10-5:           LHR,5-23,  10-26                    /SYSEXE,10-58           lib$find_image_symbol,10-8        LINKER,10-17A           lib$free_ef,11-12                 Linux shell,3-3,  3-7eG           lib$get_ef,11-12                  LISP$DAYLIGHT_SAVING_TIME_Pb@           lib$get_foreign,10-4                 Logical Name,4-19H           lib$get_symbol.,8-3               LISP$TIME_ZONE Logical Name,3           lib$set_logical,10-5                 4-19 ?           lib$set_symbol,8-3                Little-Endian,10-17 7           lib$sfree1_dd,10-10               LK201,14-46 7           lib$sget1_dd,10-10                LK401,14-46 7           LIB$SIGNAL,10-16                  LK461,14-46 ?           lib$spawn,10-9                    LK463,14-46,  14-61   J                                                                   Index-11                                   Index        E           LK46W,14-46                       Logical Partitioning,14-8t9           LK471,14-46                       LOGINOUT,5-10,6           LMF,2-10,  5-12, 10-7, 11-5,      lPars,14-84              12-5                           lpd,15-14           LMF$DISPLAY_OPCOM_MESSAGE         lpr,15-16              Logical Name,12-5              LRA0:,12-37           LMF$LICENSE,15-24                 LTO-1,14-54n;           LNM$GROUP,8-2                     LURT,2-9,  5-49d5           LNM$JOB,8-2                       LVD,14-55 7           LNM$PROCESS,8-2                   164LX,14-28_5           LNM$SYSTEM,8-2                    Lynx,13-4 J           Loadable Image,10-9               ______________________________-           LOAD_PWD_POLICY system            M J              parameter,5-50                 ______________________________7           LocalFile,15-6                    MA780,14-15EE           Logical Name                      MadGoat,5-38,  7-2, 13-2, 4             DCL$PATH,8-4                       13-13G             DECW$IGNORE_WORKSTATION,        MAIL$TIMEZONE Logical Name, 3                11-5                            4-19O6             DECW$KEYMAP,11-10               MAIL10,6-35             LISP$DAYLIGHT_SAVING_TIME_P,    MAIL7,6-1 5                4-19                         MAIL9,6-1 :             LISP$TIME_ZONE,4-19             Mail Count,6-1E             LMF$DISPLAY_OPCOM_MESSAGE,      Maintenance Version,10-26t:                12-5                         Majordomo,13-9?             MAIL$TIMEZONE,4-19              Major Version,10-26a6             NOTES$TIMEZONE,4-19             make,13-13@             SYS$DISK,10-5                   Management ProcessorE             SYS$LOGIN,8-10                    DECconnect MMJ Adapter, 6             SYS$LOGIN_DEVICE,8-10                14-60G             SYS$SCRATCH,8-10                Mature Product Support,5-21n2             SYS$TIMEZONE_DAYLIGHT_SAVING    MAXBUFC                ,4-19                          system parameter,9-14 J             SYS$TIMEZONE_DIFFERENTIAL,      MAXPROCESSCNT system parameter4                4-19                            ,5-103             SYS$TIMEZONE_NAME,4-19,         Mb,2-25d:                4-22                         MB,2-24,  2-254             TZ,4-22                         MBM,4-244             UCX$NFS_TIME_DIFFERENTIAL,      MCOE,2-6:                4-19                         MD5,5-3,  5-438             UCX$TDF,4-19                    Megabit,2-259           Logical Names                     Megabyte,2-24 :             Compared to DCL Symbols,8-2     Megabytes,2-25                      Index-12  I  1                              Index        7           Menufinder,13-9                   MTAACP,5-39 6           MESSAGE Compiler,10-16            MTEXCH,7-38           MGBOOK Bookreader,3-1             MUA4224,5-328           MGPCX,7-2                         Multia,14-26C           microfortnight,2-25               Multimedia Services,7-3V9           MIME,13-9                         Multinet,15-3 ;           Minicopy,5-59                     Multiprocessing >           Minimerge,5-59                      See ASMP and SMP7           Mini-Merge,5-60                   MySQL,13-13 J           Minor Version,10-26               ______________________________-           Mirroring,9-2                     N   J             See Volume Shadowing            ______________________________<           MISC4,14-57,  14-59               NAM$C_MAXRSS,9-3=           Mission Critical Operating        NAML$C_MAXRSS,9-3 5              Environment                    NCSA,13-4 5             See MCOE                        NCSC,5-57,8           Mlucas,13-12                      NCSC C2,5-51>           MMJ,14-56,  14-59                 NCSC Class C2,5-10A           mmk,13-13                         NET$DISABLE_DTSS,4-23 ;           MMOV,7-3                          NET$PROXY,15-24 5           Modified Modular Jack,14-56       NET1,15-1 5             See MMJ                         NET2,15-1 8           MODPARAMS.DAT,15-25,  15-26       NetBeans,2-78           Montagar,13-1                     NetBSD,14-35:           MOP,15-6                          Netnews Client;           Mosaic,13-4                         Mozilla,13-18 @           Mozilla,6-2,  13-4, 13-19         NETNODE_REMOTE,15-24@             Also see SWB                    NETNODE_UPDATE,15-24;             Composer,13-18                  NETOBJECT,15-24 :             IRC Client,13-18                NETPROXY,15-24J             Netnews Client,13-18            Netscape Navigator,6-2,  13-19E           MP,14-33                          Networking Dynamics,5-38, ;             DECconnect MMJ Adapter,            13-12, 15-10S>                14-60                        New Mail Count,6-14           MPEG,7-3                          NIC,15-2B           mpi,13-10                         NISCS_LOAD_PEA0 system>           MS780,14-15                          parameter,15-254           MSCP,15-13                        NIST,4-95           MSCP$DISK,15-13                   NOCLI,8-5 8           MSCP$TAPE,15-13                   NODECW,11-14:           MSCP_LOAD system parameter,       NODEVICE,11-14:              15-13                          NOLICENSE,5-10  J                                                                   Index-13 _  _                              Index        J           NONEWMAIL,6-1                     ______________________________-           NOTES$TIMEZONE Logical Name,      PrJ              4-19                           ______________________________0           NOTSET,4-22                       Page9           17-Nov-1858,4-1                     Memory,2-23a7           nPars,4-24                          Size,2-23A3           NTP,4-10                          Pagelet_:           ______________________________      defined,2-23<           O                                 Pager Plus,15-10:           ______________________________    Page Size,14-2:           ODBC,9-14                         PAGE_SIZE,2-238           ODS-2,9-3,  9-9                   Paging,15-10H           ODS-5,9-3,  9-9                   PAK,2-10,  5-12, 10-7, 11-5,3           Ohio State University,13-3           12-5 >           OPA0:,5-10,  14-5, 14-6, 14-15    PAKGEN,10-7,  12-5@           OpenECS,2-16                      PALcode,14-4,  14-168           OpenVMS.Org,1-2                   PA-RISC,2-136           OpenVMS Alpha                     $parse,9-4;             Terminology,2-3                 Parse Style,9-3 8           OpenVMS Alpha Upgrades,5-16       Partitioning7           OpenVMS AXP                         Hard,14-8r:             Terminology,2-3                   Logical,14-87           OpenVMS Galaxy,14-2                 Soft,14-8_:           OPENVMS-HOBBYIST,2-10               Virtual,14-8  <           OpenVMS I64,2-2,  14-33           Partner Programs6             Terminology,2-3,  14-33           See DSPP4           OpenVMS I64 Upgrades,5-19         Password  D           OpenVMS Upgrade                     Dictionary attack,5-50C             See Update, Upgrade and           Purdy Polynomial,5-51 5                Install                      Patch,7-4,  3           OpenVMS VAX                       Patches   :             Terminology,2-3                   See ECO kits9           OpenVMS VAX Upgrades,5-19         PATHWORKS,5-4D3           Opteron,2-13                      PB,2-24 I           OSU,13-3                          PBXGB-AA PowerStorm 3D30,5-29 I           Outbuildings                      PBXGB-CA PowerStorm 4D20,5-291H             See Time                        PBXGD-AE PowerStorm 350,5-29F           Overwrite,5-57                    PBXGK-BB PowerStorm 3D10T,3                                                5-28 :                                             PC7XS-CA,14-466                                             PCDISK,7-28                                             PC Disks,7-2                      Index-14     Y                              Index        =           PCF,11-18                         Printing (cont'd) 9           PCSI,5-42,  10-27                   telnet,15-1e  F           PCSI Install                      Prior Version Support,5-21>             See Install                     Process Dump,10-27I           PCSI Upgrade                      Process Software,13-2,  15-3, 4             See Upgrade                        15-10F           PCX,7-2                           Product Authorization Key,E           PDF,3-1,  13-7                       5-12, 10-7, 11-5, 12-5_E           Peek,13-12                        Product Registration,10-2LE           Pentium,2-14                      PRODUCT SHOW PRODUCT,5-42 6           Perl,2-7,  13-11, 13-22           ProDVD,9-8>           Petabyte,2-24                     ProGIS,7-2,  13-17  @           PGP,13-5                          Programming Examples  :           PHYSICALPAGES system parameter      See Examples@              ,5-14                          Protected Image,10-8D           PHYSICAL_MEMORY system            Protected Subsystems,5-2;              parameter,5-14                 PSECT_ATTR,10-6M<           PINE,13-9                         Purdy Polynomial;           pin-out,14-59                       Password,5-51 6           Pioneer,14-63                     PURGE,5-628           PIPE,8-9                          $putmsg,10-55           PL/I,13-18                        pvm,13-10C4           Plextor,14-55,  14-63             PVS,5-215           pm,11-8                           PWIP,15-5 8           PMDF,15-10                        Python,13-12J           PMU,4-24                          ______________________________-           POLYCENTER Software Product       Q J              Install Utility                ______________________________=             See PCSI                        $qio,10-9,  11-12 =           Port,15-12                        QMAN$JOURNAL,5-315=           Postscript,10-16                  QMAN$MASTER,15-24 :           POV-Ray,13-9                      QuickSpecs,3-48           PowerStorm 300,5-29               QUORUM,15-17J           PowerStorm 350,5-29               ______________________________-           PowerStorm 3D10T,5-28             RCJ                                             ______________________________D           PowerStorm 3D30,5-29,  14-48      Radeon 7500,5-30,  14-489           PowerStorm 4D20,5-29,  14-48      RamPage,15-10 4           PPP,15-4                          RAS,15-47           Preatorian Cluster,2-16           Raxco,13-12E<           Pretty Good Privacy,13-5          RIGHTSLIST,15-247           Printing                          Rlogin,5-59              DCPS,12-31             lpr,15-1             Parallel Port,12-3  J                                                                   Index-15                                   Index        ?           RMS,9-14                          Search Engine,13-13a2           RMS Journaling,9-2                Sector7           RMS Sequential Record Format,       Disk,2-245=              9-15                           Secure Shell,13-3 >           Roadmap,2-13                      Secure Web Browser5           robomon,14-21                       See SWB @           Rocksoft,5-3                      Security,5-10,  5-57  D           Royal Greenwich Observatory         Dictionary attack,5-50:             See Time                          NCSC C2,5-51;           RRD42,9-12                          Password,5-50l<           RS-232,14-57                      Security MUP,5-3E           rx2600,14-60                      Self-extracting zip,13-25,I           RZDISK,14-54                      Sequential Record Format,9-15 >           RZTOOLS,5-58                      Serial Number,10-7G           ______________________________    SETBOOT,9-13,  14-20, 14-22tG           S                                 SET BOOTBLOCK,9-13,  14-20, 4           ______________________________       14-229           S3 Switch,14-6                    SETCLOCK,4-13EI           SAIC,1-4,  13-1, 13-3             SET DEVICE/RESET=ERROR_COUNT,C3           Saiga Systems,5-38                   5-33W=           Samba,5-4                         SET FILE/CACHING_ E           SAMBA,13-11                          ATTRIBUTES=NO_CACHING, 2           SAO,4-1                              9-8D           SCACP,15-15                       SET PREFERRED_PATH,15-15G           Scaliger                          SET PREFERRED_PATH command,o4             Julius Caesar,4-2                  15-15G           Scaliger, Joseph,4-2              SET PROCESS/PARSE_STYLE,9-3E8           Scribe                            $SETTIM,4-22J             InfoServer,9-9                  SET TIME,4-5,  4-7, 4-8, 4-12,9           SCS,15-11,  15-12                    4-22, 4-24-A           SCSI,9-14,  14-2, 14-28,          SET TIME/CLUSTER,4-12cI              14-32, 14-34, 14-41, 14-49,    SETTIME system parameter,4-4,e2              14-52, 14-53, 14-54, 14-55,       4-5B              14-56, 14-63, 14-64            $set_system_event,4-125           SCSI-2,9-6                        SFX,13-25D9           SCSI_INFO,14-53                   Shadowing,9-20?           SCSNODE system parameter,         Shareable image,5-1 @              5-12, 5-14, 15-26              Shareable Image,10-8;           SCSSYSTEMID system parameter,     shell,3-3,  3-7'F              5-14                           SHOW MEMORY/CACHE command,3           SDL,10-16                            9-15 ;           SDML,vi,  10-16                   Signature,14-222                      Index-16, -   --    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.com9   ------------------------------  # Date: Mon, 11 Apr 2005 19:57:47 GMT # From: hoff@hp.nospam (Hoff Hoffman) = Subject: OpenVMS Frequently Asked Questions (FAQ), Part 11/11 1 Message-ID: <%EA6e.3495$IL.1915@news.cpqcorp.net>3    Archive-name: dec-faq/vms/part11 Posting-Frequency: quarterly Last-modified: 11 Apr 2005 Version: VMSFAQ_20050411-11.TXT4                                   Index        <           SIMH,13-26                        Storage (cont'd)A           SMB,13-11                           DVD-R/RW,9-7,  9-10 @           smg$create_menu,10-4                DVD-Recordable,9-8<           SMG$GET_TERM_DATA,12-1              FAT Format,7-28           Smithsonian Astrophysical           Floppy,7-2=              Observatory,4-1                  Free Space,12-3-J           SMP,14-15                           IDE,7-1,  9-5, 14-28, 14-32,E           $sndjbc,10-9                           14-52, 14-53, 14-54, 6           SOAP,2-7,  13-8                        14-55;           SOC,3-4                             PC Format,7-2 D           Soft Partitions,14-8                Remaining on Tape,12-3F           Sophos,5-4                          SCSI,9-14,  14-2, 14-28,E           SPIA,10-27                             14-32, 14-34, 14-41,   E           SPIU                                   14-49, 14-52, 14-53,   D             See PCSI                             14-54, 14-55, 14-568           Spy,13-12                           SCSI-2,9-6<           Spyglass,13-4                       Volume Set,9-77           SQP,2-8                           Stream,9-15 9           SRI,1-3,  13-26                   StreamLF,9-15 E           SRM,4-24,  14-15, 14-16           Subsystem Identifier,10-8L<             Acronym,14-4                    Supervisor,13-12=             System Reference Manual,        Supnik, Bob,13-26i3                14-4                         Support H           SS$_DEBUG,10-16                     Prior Version Support,5-215           SS$_NOCLI,8-5                     SWB,13-19m;           SSH,13-3                          Swizzling,14-37s7             FISH,13-3                       164SX,14-28 F           SSL,2-7                           SYI$_PAGE_SIZE,2-23,  14-2F             SSLeay,13-4                     SYLOGICALS.COM,4-23,  8-6,3           SSLeay,13-4                          11-5 E           Stark, Tim,13-26                  SYLOGICALS.TEMPLATE,4-23, J           STARLET.L32,10-14                    5-37, 5-59, 6-1, 8-6, 15-243           STARLET.L64,10-14                 Symbols H           STARLET.R64,10-14                   Compared to Logical Names,4           STARLET.REQ,10-14                      8-15           Storage                             DCL,8-1_?             ATA,7-1,  9-5, 14-28, 14-32,    Symbol Substitution 6                14-52, 14-53, 14-54,           PIPE,8-9>                14-55                        SYMBOL_VECTOR,10-6E             CD-R,14-55                      Symmetric Multiprocessing65             CD-R/RW,9-7,  9-10                See SMPy@             CD-Recordable,9-8               synch-on-green,14-47             Disk Settings,14-49              DVD+R/RW,9-7,  9-10L  J                                                                   Index-17    e                              Index        H           sys$acm,5-51                      SYS$TIMEZONE.DAT,4-16,  4-20H           SYS$BASE_IMAGE,10-5               SYS$TIMEZONE_DAYLIGHT_SAVING@           SYS$BASE_IMAGE.EXE,4-16              Logical Name,4-19E           sys$creprc,10-9                   SYS$TIMEZONE_DIFFERENTIAL @           SYS$DIAGNOSTICS.SYS,9-13             Logical Name,4-19E           SYS$DISK Logical Name,10-5        SYS$TIMEZONE_NAME Logical >           SYS$DKDRIVER,14-63,  14-64           Name,4-19, 4-22B           SYS$DNDRIVER,14-64                SYS$TIMEZONE_RULE,4-17E           SYS$DQDRIVER,7-1,  9-5, 14-32,    SYS$TIMEZONE_SRC.DAT,4-20 :              14-55, 14-63, 14-64            sys$trnlnm,8-3=           SYS$EFI.SYS,9-13,  14-9           SYS$WSDRIVER,11-3 8           sys$erapat,5-58                   SYS.STB,10-58           SYS$EXAMPLES:DAYLIGHT_            SYSALF,15-247              SAVINGS.COM,4-15, 4-17         SYSAP,15-13 E           SYS$EXAMPLES:GKTEST.C,14-64       SYSBOOT,5-7,  5-11, 15-20w7           sys$filescan,9-4                  SYSGEN,5-11E8           sys$flush,9-2                     SYSLOG,13-107           sys$getdvi,10-2                   System Disk A           sys$getenv,14-8                     VAXstation 3100,9-4,=           sys$getjpi,10-2                   System Image,10-8 =           sys$getsyi,2-23,  10-2            System parameters =           SYS$GKDRIVER,14-64                  ALLOCLASS,15-26 A           SYS$LIB_C.TLB,10-22                 DEVICE_NAMING,15-20VB           SYS$LOGIN Logical Name,8-10         EXPECTED_VOTES,15-16B           SYS$LOGIN_DEVICE Logical Name       LOAD_PWD_POLICY,5-509              ,8-10                            MAXBUF,9-14 @           sys$parse,9-4                       MAXPROCESSCNT,5-10=           SYS$PIPE,8-9                        MSCP_LOAD,15-131C           SYS$PROCDMP,10-27                   NISCS_LOAD_PEA0,15-25 @           SYS$PROTECTED_PROCDMP,10-27         PHYSICALPAGES,5-14B           sys$putmsg,10-5                     PHYSICAL_MEMORY,5-14H           sys$qio,10-9,  11-12                SCSNODE,5-12,  5-14, 15-26>           SYS$REGISTRY,15-24                  SCSSYSTEMID,5-14?           SYS$SCRATCH Logical Name,8-10       SETTIME,4-4,  4-5 F           SYS$SETBOOT.EXE,9-13,  14-20,       TIMEPROMPTWAIT,4-4,  4-5>              14-22                            TMSCP_LOAD,15-13>           sys$setddir,10-5                    UAFALTERNATE,5-9>           SYS$SETTIM,4-22                     VAXCLUSTER,15-259           sys$set_system_event,4-18           VOTES,15-16 G           sys$sndjbc,10-9                     WINDOW_SYSTEM,5-9,  11-5, 6           SYS$STARTUP:DTSS$STARTUP.COM,          11-14@              4-23                             WRITESYSPARAMS,5-9                        Index-181 2                                 Index        9           Systems and Options Catalog,      Time (cont'd) E              3-4                              Clock Drift,4-11,  4-1339           System Service,10-8                 Dial-up,4-9 D           SYSUAF,5-50,  15-24                 DST,4-21,  4-27, 10-22>             Bypass,5-10                       DTSS,4-10,  4-16G             Corrupt,5-10                      Error modifying time,4-22 6           SYSUAFALT,15-24                     GMT,4-27<           SYSUAFALT.DAT,5-10                  Greenwich,4-276           ______________________________      IPL,4-116           T                                   IRIG,4-98           ______________________________      Julian,4-1A           TAP,15-10                           Julian Calendar,4-2 =           TAPECOPY,7-3                        Julian Date,4-1 <           Tapes                               Julian Day,4-16             Compaction,12-4                   NIST,4-99             Compression,12-4                  NOTSET,4-22 6             Conversion,7-3                    NTP,4-10J             EBCDIC,7-3                        Off By One Hour,4-21,  4-27,6             Free Space,12-3                      10-22A           Target Systems,15-10                Prime Meridian,4-27 ;           TB,2-24                             SETCLOCK,4-13gC           tcgmsg,13-10                        SET TIME Command,4-22 6           TCL,13-13                           TDF,4-16=           TCOPY,7-3                           TIMENOTSET,4-22 G           TCQ,14-2                            Time service enabled,4-22gA           TDF,4-16                            Timezone Rules,4-22 <           TECsys,14-21                        TODR,4-5,  4-7;           telnet,15-1                         TOY,4-5,  4-7 6           Telnet,5-59                         UT0,4-276           Telocator Alphanumeric              UT1,4-276              Protocol,15-10                   UT2,4-27J           Terabyte,2-24                       UTC,4-16,  4-21, 4-27, 10-22;           Terminal emulator                 TIMENOTSET,4-22 A             VTstar,11-4                     TIMEPROMPTWAUT system5A           Terminal Server Manager,13-12        parameter,4-4, 4-5 5           Test-Drive,2-15                   Timezones D           Test Manager,13-22                  SYS$TIMEZONE_NAME,4-225           Text,10-16                          TZ,4-22 F           TFT2025,14-48                       zic compiler,4-18,  4-217           TIE,13-24                         TMSCP,15-13,H           Time                              TMSCP_LOAD system parameter,4             ACTS,4-9                           15-13!             AlphaServer ES47,4-24 !             AlphaServer ES80,4-24-#             AlphaServer GS1280,4-24   J                                                                   Index-19                                   Index        I           TODR,4-5,  4-7                    user-written system services, 2           Tomcat,2-7                           5-14           Too Few Servers Detected,4-23     UT0,4-274           Touch,13-13                       UT1,4-274           Touch Technologies,vi             UT2,4-27;           TOY Clock,4-5,  4-7               UTC,4-16,  4-275F           TPAMAC.REQ,10-15                  UTC$CONFIGURE_TDF.COM,4-15G           Trailing Edge,13-26               UTC$TIMEZONE_SETUP.COM,4-15 D           Tripp-Lite,13-10                  UTC$TIME_SETUP.COM,4-15,E           TrueType,11-19                       4-16, 4-18, 4-20, 4-21 9           TS10,13-26                        uudecode,13-2 9           TSM,13-12                         uuencode,13-2 ;           TT2$M_DISCONNECT,5-59             UWSS,5-1,  10-8 J           TTF,11-19                         ______________________________-           TTY_DEFCHAR2,5-59                 V J           TV,13-24                          ______________________________=           TZ Logical Name,4-22              Vajhj, Arne,13-2n6           ______________________________    VAKSAT,7-2/           U                                 VAX =           ______________________________      Terminology,2-4l3           U.S. Design,9-10                  VAX/VMS =           UAFALTERNATE,5-10                   Terminology,2-3-<           UAFALTERNATE system parameter     VAX-11/782,14-158              ,5-9                           VAXBACK,5-20F           UCB,10-9                          VAXcluster Console System,4           UCX$NFS_TIME_DIFFERENTIAL            14-21H              Logical Name,4-19              VAXCLUSTER system parameter,4           UCX$TDF Logical Name,4-19            15-25=           UDDI,2-7                          VAXCRTL.EXE,10-25 >           Ultrium 230,14-54                 VAX Emulator,13-26;           undelete,9-1                      VAXstation 3100n9           unixODBC,9-15                       Console,9-4aF           UNIX shell,3-3,  3-7                System Disk Capacity,9-4:           unzip,14-23                       VCC_FLAGS,9-155           Update,5-22                       VCS,14-21 8           Upgrade,5-22                      Veracity,5-3C           UPS,13-10                         Version Numbering,10-26 8           UPShot,13-10                        Edit,10-26?           USB,14-61,  14-64                   Maintenance,10-26 9           User Group                          Major,10-26 9             DECUS,1-9                         Minor,10-26 9             Encompass,1-9                   Versions,5-62 F             Interex,1-9                     Very Long Instruction Word  6                                               See VLIW                      Index-20  d  r                              Index        7           VEST,13-18,  13-24                VRC21,14-46 7           VFC,9-15                          VSXXX,14-461I           vi,13-16                          VTstar terminal emulator,11-4 4           vile,13-16                        VXT,11-3J           vim,13-16                         ______________________________-           VIOC,9-15                         WMJ           VIOC Compatable Mode,9-15         ______________________________>           Virtual Circuit,15-13             Web Archives,14-497           Virtual Partitioning,14-8         Web Browser   5           Virtual Terminal,5-59               See SWB 7           VLIW,14-33                          CSWB,13-4 7           VMB,14-12                           Lynx,13-439           VMove,7-2                           Mosaic,13-41B           VMS$AUDIT_SERVER,15-24              Mozilla,13-4,  13-18;           VMS$CLASS_SCHEDULE,15-24            Netscape,13-4 F           VMS$DISK_CL_DRIVER,15-13            Netscape Navigator,13-196           VMS$OBJECTS,15-24                 Web server9           VMS$PASSWORD_HISTORY,15-24          Apache,13-8 6           VMS$PASSWORD_POLICY,15-24           OSU,13-8;           VMS$TAPE_CL_DRIVER,15-13            Purveyor,13-9 7           VMS$VAXCLUSTER,15-13                WASD,13-9 :           VMS73_XFC,9-15                    Webserver,13-3H           VMSINSTAL,5-42                    Western Kentucky University,  3           VMSINSTAL Update                     13-2_9             See Update                      WINDOW_SYSTEM D           VMSLICENSE,5-12                     system parameter,11-5,6           VMSMAIL_PROFILE,15-24                  11-14J           VMS_FLAGS,14-9                    WINDOW_SYSTEM system parameter3           VMS_LOADER.EFI,5-8,  14-9            ,5-9 8           _VMS_V6_SOURCE,4-16               Wiring,14-59;           Vols in Full XFC mode,9-15        WIZARD.ZIP,3-11 4           Volume Set,9-7                    WKU,13-2:           Volume Shadowing,15-26            WRITEBOOT,9-13?             Allocation Class,15-26          WRITEBOOT.EXE,14-20-F             Full Copy,5-60                  Write History Logging,5-59A             Full Merge,5-61                 WRITESYSPARAMS system <             Minicopy,5-59                      parameter,5-99             Minimerge,5-59                  WSDRIVER,11-364           VOTES system parameter,15-16      WWW,13-4A           vPars,4-24,  14-2, 14-8           www.archive.org,14-49            VR260,14-460           VR290,14-46n           VRC16,14-46   J                                                                   Index-21 -                                 Index        :           ______________________________    X Windows,11-1C           X                                 X Windows Terminal,11-3 J           ______________________________    ______________________________-           X11,11-18                         Y J           X11R5,11-18                       ______________________________4           X11R6.6,11-18                     Y2K,5-398           XDR,10-17                         Yamhill,2-13:           XFC,9-15                          Year 2000,5-39J           XLNperformance,5-38               ______________________________-           XLNsystems,5-38                   ZcJ           XML,2-7,  10-17, 13-11            ______________________________3           XOFF,14-61                        ZAP,7-4 D           XON,14-61                         zic compiler,4-18,  4-21@           XOR,5-43                          Zimmerman, Phil,13-5<           XP1000,14-48                      zip,9-16,  13-255           XPDF,3-1,  13-7                   Zip,14-55oC           xpm,11-8                            Self-extracting,13-25-7           XtAppAddInput,11-12               ZMODEM,13-3y           xv,11-8e                                                                      Index-22  --    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.comf   ------------------------------  # Date: Mon, 11 Apr 2005 19:40:20 GMT & From: hoffman@hp.nospam (Hoff Hoffman)< Subject: OpenVMS Frequently Asked Questions (FAQ), Part 2/111 Message-ID: <EoA6e.3485$IL.1713@news.cpqcorp.net>    Archive-name: dec-faq/vms/part2  Posting-Frequency: quarterly Last-modified: 11 Apr 2005 Version: VMSFAQ_20050411-02.TXT                                    Introduction         4                    widftp://rtfm.mit.edu/pub/usenet/=                       news.answers/usenet/writing-style/part1a  4                    widftp://rtfm.mit.edu/pub/usenet/=                       news.answers/usenet/posting-rules/part1e  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                                              Note   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 and_F                       distribute a fix before other customer sites can"                       be affected.  A                       Most folks in the newsgroups are honest andr>                       deserve to know about potential securityA                       problems, but a few folks can and will make C                       nefarious use of this same information. Other ?                       sites will hopefully return the courtesy, =                       and will not post information that willH?                       potentially compromise your site and yourd+                       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 ofdE                    Compaq and of the former DIGITAL. Encompass offers I                    newsletters, the Encompass website, and offers various4F                    gatherings and related services, including symposia9                    events and local users group meetings.   I                    Encompass is a descendent of the organization known as G                    DECUS, the Digital Equipment Computer Users Society.K                      1-8    O                              Introduction-        F                    For more information on Encompass, please visit the&                    Encompass web site:  1                    o  http://www.encompassus.org/   F                    The organization comprised of customers of Hewlett-J                    Packard Company (HP) that is probably most analogous to9                    the Encompass organization is Interex:C  -                    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.A  D           __________________________________________________________7           1.5  OpenVMS Support, Questions and Comments?   F                    The following section includes contacts for OpenVMSG                    Feedback, and information on how to obtain technical '                    support information.3  '           _____________________________ @           1.5.1  Corporate contacts for OpenVMS Business Issues?  J                    The HP corporate contact for OpenVMS business issues isI                    Ann McQuaid, the HP General Manager directly in charge-D                    of OpenVMS and OpenVMS Engineering, while featureF                    requests and other related matters should be routedE                    to MaryJane Vazquez, the OpenVMS Business Manager.e  H                    Ann and MaryJane will quite obviously respond best toJ                    cogently-worded OpenVMS corporate-level business issuesE                    or requests. With all due respect to all involved, H                    neither Ann nor MaryJane are appropriate contacts forF                    technical support matters nor for technical supportJ                    requests, nor for any other non-corporate-related, non-J                    business-related issues-these questions are best routedG                    to the local or regional customer support center; to @                    the support, technical and engineering teams.  H                    To reach Ann or MaryJane via electronic mail, place aH                    dot between the first and the surname, and append the*                    expected HP.COM domain.  J                                                                        1-9                                   Introduction       '           _____________________________r%           1.5.2  OpenVMS Ambassadors?   G                    The OpenVMS Ambassadors are senior HP engineers withrH                    advanced technical knowledge and advanced training inI                    OpenVMS, with detailed knowledge of current and futureSH                    OpenVMS releases and product plans, and with contactsE                    directly with the HP and ISV hardware and software C                    engineering organizations developing OpenVMS andMJ                    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.c  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.M  '           _____________________________CD           1.5.3  Contact for OpenVMS Marketing Issues and Questions?  *                    Please see Section 3.4.  '           _____________________________d;           1.5.4  Contact URLs for OpenVMS Technical Issues?   E                    For technical issues and technical support, pleaseeF                    contact your software support organization, or yourF                    local HP Customer Support Center or HP Reseller. In?                    North America, you can call 1-800-HP-INVENT.,  J                    Please remember to review and to bookmark the following                     support URLs:  3                    o  http://www.hp.com/go/openvms/,  -                    o  http://askq.compaq.com/   :                    o  http://www.hp.com/go/openvms/wizard/  <                    o  ftp://ftp.itrc.hp.com/openvms_patches/                        1-10c -                       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 Address3                    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._  >                    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 wide0G                    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. Current A                    implementations run on VAX systems from HP andpC                    other vendors, as well as on hardware emulators;IF                    for additional information on emulators, please see$                    Section 13.12 and    J                                                                        2-1               &                    General Information        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.   B                    OpenVMS has also been ported to the Intel IA-64A                    architecture, and specifically to HP Integrity G                    systems using microprocessors from the Intel Itanium2F                    Processor Family. This implementation of OpenVMS isI                    officially known as "HP OpenVMS for Integrity Servers",F                    and more commonly as "OpenVMS I64", and it operatesC                    in the native Itanium IA-64 architecture and 64- D                    bit environment. OpenVMS I64 provides support forJ                    applications requiring 32- or 64-bit virtual addressingI                    capabilities entirely within the native 64-bit Itanium J                    execution environment. (For details on this and related;                    terminology, please see Section 14.4.5.)e  G                    For more details on OpenVMS and its features, pleasepD                    read the OpenVMS Software Product Description at:  9                    o  http://h18000.www1.hp.com/info/spd/a  H                       OpenVMS typically uses SPD 25.01.xx, SPD 41.87.xx,'                       and SPD 82.35.xx.r  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- *                       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:S  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:a  .                    o  http://www.free-vms.org/  5                    o  http://www.openvmshobbyist.org/                       2-2    I          &                    General Information        0                    o  http://www.openvmsedu.com/  H                    Also please see the related software licensing topicsB                    Section 2.8.4, Section 2.8.1, and Section 2.15.  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 VAX G                    and Alpha (and for the Itanium Processor Family), in J                    part to signify the high degree of support for industryH                    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 see9!                    question SOFT2e  E                    What became confusing is that the OpenVMS name wassD                    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.   D           __________________________________________________________:           2.3  What's in a Name? Terminology and Products?  H                    The proper names for OpenVMS on the various platformsI                    are "OpenVMS VAX", "OpenVMS Alpha", and "OpenVMS I64". H                    Use of "OpenVMS AXP" and of "VAX/VMS" are deprecated.  J                                                                        2-3               &                    General Information        F                    The VAX and Alpha terms are largely interchangeablyB                    used as the names of platforms, of processor orH                    microprocessor implementations, and of the respective+                    computing architectures.   G                    Somewhat confusing to long-time OpenVMS users, IntelgJ                    IA-32, IA-64, and EM64T, and AMD AMD64 are the names ofG                    various computing architectures and of architectural C                    extensions. Only. These are not the names of any 9                    implementations, nor of any platforms.   J                    Intel Itanium is the name of a family of microprocessorF                    implementations of the Intel IA-64 architecture, asF                    Intel Pentium and Xeon are the names of families ofD                    microprocessor implementations of Intel IA-32 and9                    (potentially) of the EM64T extensions._  G                    I64 is the generic name for the various HP Integrity J                    platforms supported by HP OpenVMS for Integrity ServersJ                    (and more commonly as "OpenVMS I64"); for the platformsD                    supported by OpenVMS I64. (For additional related;                    terminology, please see Section 14.4.5.)   '           _____________________________ 3           2.3.1  How do I port from VMS to OpenVMS?   @                    You already did. Wasn't that easy? Please see+                    Section 2.2 for details.-  D           __________________________________________________________0           2.4  Which is better, OpenVMS or UNIX?  H                    This question comes up periodically, usually asked byI                    new subscribers amd new posters who are long-time UNIXgE                    or Linux users. Sometimes, the question is ignoredpE                    totally; other times, it leads to a long series ofeG                    repetitive messages that convince no one and usually9J                    carry little if any new information. Please do everyoneJ                    a favor and avoid re-starting this perpetual, fruitless                    debate.  G                    That said, OpenVMS and the better implementations ofrE                    UNIX are all fine operating systems, each with its7D                    strengths and weaknesses. If you're in a positionE                    where you need to choose, select the one that best H                    fits your own requirements, considering, for example,                      2-4 e  a          &                    General Information        E                    whether or not the layered products or specific OS G                    features you want are available, and considering the F                    expected cost-of-ownership over the lifetime of the'                    system installation.   D           __________________________________________________________@           2.5  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, +                    and related information:u  3                    o  http://www.hp.com/go/openvms/   D           __________________________________________________________<           2.6  What OpenVMS distribution kits are available?  7                    Various distributions are available.e  I                    For the most current information on the available part E                    numbers and current products (OpenVMS distributionUH                    kits, media, documentation, etc) and the most currentC                    associated licensing information, please see the E                    current OpenVMS Software Product Description (SPD) *                    document, available at:  9                    o  http://h18000.www1.hp.com/info/spd/y  H                       OpenVMS typically uses SPD 25.01.xx, SPD 41.87.xx,'                       and SPD 82.35.xx.   C                    The CD-ROMs listed in Table 2-1 contain just the G                    OpenVMS Alpha operating system. The operating system I                    distribution kits are bootable, and can be used to run J                    BACKUP from the optical media, as well as performing an+                    installation or upgrade.         J                                                                        2-5 t  t          &                    General Information        J           ________________________________________________________________-           Table 2-1  OpenVMS Alpha Media Kitsu  J                    _______________________________________________________J                    Part______________Description__________________________  D                    QA-MT1AG-H8       OpenVMS Alpha V6.2-1H3 hardwareF                                      release CD-ROM; also requires QA-1                                      MT1AA-H8.6.2$  E                    QA-MT1AR-H8       OpenVMS Alpha V7.1-2 maintenance$3                                      release CD-ROMA  E                    QA-MT1AT-H8       OpenVMS Alpha V7.2-1 maintenance 3                                      release CD-ROME  E                    QA-MT1AU-H8       OpenVMS Alpha V7.2-2 maintenancem3                                      release CD-ROMY  G                    QA-MT3AA-H8       OpenVMS Alpha and VAX products andm<                                      documentation on CD-ROM  H                    QA-MT3AE-H8       OpenVMS Alpha and VAX documentationJ           ___________________________on_CD-ROM____________________________  F                    OpenVMS I64 is distributed on DVD-ROM media, and isF                    bootable. OpenVMS I64 licensing is implemented on aG                    per-processor-socket basis, with the classic license G                    tiers based on the numbers of processor sockets that,E                    can be present. Further, three general product andED                    licensing groupings are optionally available withD                    OpenVMS I64, the Foundation Operating EnvironmentI                    (FOE), the Enterprise Operating Environment (EOE), and H                    (as/when/if available) the Mission Critical OperatingH                    Environment (MCOE). Seperate per-product licenses areG                    generally also available for various of the products,;                    within the Operating Environment groups.D  J           ________________________________________________________________.           Table 2-2  OpenVMS I64 Order Numbers  J                    _______________________________________________________J                    Part______________Description__________________________  <                    BA322AA#???       OpenVMS I64 FOE Product  <                    BA323AA#???       OpenVMS I64 EOE Product  J           _________BA324AA#???_______OpenVMS_I64_MCOE_Product_____________                      2-6               &                    General Information        D                    The product suffix required for the order numbersA                    listed in Table 2-2 can be found in Table 2-3.-  J           ________________________________________________________________-           Table 2-3  OpenVMS I64 Media Suffix5  J                    _______________________________________________________J                    Suffix____________Description__________________________  C                    A18               OpenVMS I64 FOE V8.2 DVD media,  >                    AJR               OE media kit on DVD media  J           _________0D1_______________Factory_installation_________________  H                    The OpenVMS VAX, OpenVMS Alpha and OpenVMS I64 sourceD                    listings sets referenced in Table 2-4 include theI                    source listings of most of OpenVMS, and these machine-mF                    readable distributions are invaluable for any folksJ                    working directly with OpenVMS internals, as well as forI                    folks interested in seeing examples of various OpenVMS *                    programming interfaces.  J           ________________________________________________________________1           Table 2-4  OpenVMS Source Listings Kits_  J                    _______________________________________________________J                    Part______________Description__________________________  J                    QB-MT1AB-E8       OpenVMS Alpha Source Listings kit and,                                      license  J                    QT-MT1AB-Q8       OpenVMS Alpha Source Listings Updates  H                    BA422AA           OpenVMS I64 Source Listings kit and,                                      license  H                    QB-001AB-E8       OpenVMS VAX Source Listings kit and,                                      license  H                    QT-001AB-Q8       OpenVMS VAX Source Listings Updates  H                    BA422AA           OpenVMS I64 source listings kit andJ           ___________________________license______________________________  I                    Additional OpenVMS packages and technologies including D                    NetBeans, XML, SOAP, UDDI, JDK, Perl, Tomcat, SSLG                    and such are discussed within the OpenVMS e-Business-I                    Infrastructure Package SPD 80.58.xx. Again, please see I                    the OpenVMS SPD and the documents and parts referenced :                    there for the most current information.  J                                                                        2-7               &                    General Information      '           _____________________________-G           2.6.1  Where can I download OpenVMS and Layered Product Kits?O  D                    HP customers with commercial licenses and supportG                    contracts can download software product distribution 6                    kits from the following HP website:  *                    o  http://www1.sqp.com/  E                    You can also find pointers to the Software RolloutZG                    Report and to the OpenVMS SPD listings via the above                     SQP website.   D                    Information on obtaining and transfering licensesG                    is available in Section 2.6 and Section 2.8.4, while H                    information on the OpenVMS Hobbyist licensing programI                    and on obtaining hobbyist product distribution kits is $                    in Section 2.8.1.  D           __________________________________________________________3           2.7  In what language is OpenVMS written?e  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, DEC I                    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 are ?                    just some of the languages NOT represented!)   F                    There are a large variety of small and not-so-smallI                    tools and DCL command procedures that are used as part I                    of the OpenVMS build, and a source code control system H                    capable of maintaining over a hundred thousand sourceG                    files across multiple parallel development projects, ,                    and overlapping releases.                              2-8 l             &                    General Information      D           __________________________________________________________:           2.8  Obtaining and Transfering OpenVMS licenses?  ?                    The following sections describe hobbyist and9J                    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, F                    please see Section 2.8.4. OpenVMS Hobbyist licensesB                    are discussed in Section 2.8.1. For informationC                    on the licensing implementation, troubleshooting G                    licensing problems, on the License Unit Requirements F                    Table (LURT), and other related details, please seeI                    Section 5.39. For configuring and troubleshooting LMF, $                    see Section 12.4.  '           _____________________________n?           2.8.1  Questions asked by Hobbyist OpenVMS licensees?6  E                    If you are a member of an HP-recognized user group G                    (eg: Encompass, Enterex, DECUS), and are considering-J                    acquiring and using a VAX, Alpha or (soon) IA-64 systemD                    for hobbyist (non-commercial) use, (free) licenseE                    product authorization keys (PAKs) for OpenVMS VAX, J                    OpenVMS Alpha, (soon) OpenVMS I64, and layered products!                    are available.1  C                    In addition to the license keys, OpenVMS VAX and B                    Alpha distribution CD-ROM distribution kits areC                    available with OpenVMS, DECwindows Motif, DECnet B                    and TCP/IP networking, compilers, and a varietyD                    of layered products. (A hobbyist distribution forD                    OpenVMS I64 is expected.) (While the hobbyist CD-F                    ROM distributions are intended for and tailored forJ                    OpenVMS Hobbyists, the contents and capabilities of theI                    Hobbyist installation kits included within the OpenVMS H                    Hobbyist distribution do not differ from the standardJ                    distribution installation kits. The products are chosenE                    to reflect the most popular products and the space +                    available on the media.)1  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).1  J                                                                        2-9 D  -          &                    General Information        ;                    For further information, please link to:t  5                    o  http://www.openvmshobbyist.org/   D                    On the OpenVMS Hobbyist license registration formD                    at the above website (as of August 2004), you areJ                    offered the choice of the "OpenVMS VAX" license(s), theI                    "OpenVMS Alpha" license(s), and the "Layered Products"OG                    licenses. You will want the operating system license D                    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.o  G                    For vendors wishing to license products specifically0E                    for hobbyist use (and to not issue hobbyist PAKs),6F                    the program provides hobbyists with the license PAK$                    OPENVMS-HOBBYIST.  B                    If you plan to use a hardware emulator (eg: VAXG                    emulator) on a Microsoft Windows platform, make sure C                    you have an OpenVMS distribution kit that can be9G                    installed and/or booted with the particular emulator I                    package you plan to use. For additional information onIG                    emulators, please see Section 13.12 and particularly A                    please see the emulator-related documentation.   '           _____________________________ 7           2.8.2  OpenVMS Educational and CSLG licenses?   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:0  0                    o  http://www.openvmsedu.com/  '           _____________________________LB           2.8.3  What developer and partner licensing programs are                  available?_  F                    Commercial software developers can join the HP DSPPC                    program, and can (potentially) receive discounts D                    on various software product licenses and softwareC                    distributions, as well as on hardware purchases.1  0                    o  http://www.hp.com/go/dspp/                      2-10     f          &                    General Information        I                    The DSPP program is the descendent of the DIGITAL ISVN H                    and DIGITAL ASAP programs and the Compaq CSA program,J                    and the analogous developer and partner programs at HP.    H                    Please see Section 2.15 for additional details on the                     DSPP program.  ?                    For information on the OpenbVMS Hobbyist andSC                    OpenVMS Educational license programs, please seea!                    Section 2.8.1.   '           _____________________________j@           2.8.4  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, youAG                    can contact HP at regional sales office or reseller.   J                    For information on the hobbyist license program, please%                    see Section 2.8.1.t  D           __________________________________________________________=           2.9  Does OpenVMS support the Euro currency symbol?   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.  D           __________________________________________________________F           2.10  OpenVMS Ports? Itanium? Ports to IA-32, EM64T or AMD64                 systems?  H                    OpenVMS has been ported to and is operational on fourI                    architectures: VAX, Alpha, IA-64, and IA-32. The firsttD                    three have available native ports of OpenVMS, theG                    fourth is available via emulation. VAX is the oldestsE                    architecture, and limited to 32-bit virtual and up E                    to 34-bit physical addressing. The Alpha and IA-64 D                    architectures are both 64-bit architectures, withE                    64-bit virtual addressing available. The available F                    IA-32 emulation is provided for the OpenVMS VAX andE                    other VAX operating systems, and provides a 32-bitoE                    VAX environment. For additional information on the_7                    emulation, please see Section 13.12.o  J                                                                       2-11 s  a          &                    General Information        H                    As for (the lack of) a native port for IA-32, OpenVMSF                    Engineering presently and continues to believe thatD                    there would be insufficient market (read: profit,E                    customer interest) to justify the cost involved insF                    a native port of OpenVMS to systems using the IntelF                    IA-32 architecture. In addition to the direct costsJ                    involved in any port and in addition to the substantialD                    effort involved in moving backwards from a 64-bitI                    environment on Alpha and on IA-64 to a 32-bit platform J                    (such as IA-32), and the exceedingly non-trivial deviceH                    qualification costs and the costs in moving backwardsE                    into older PCI and I/O environments (IA-32 systemsoG                    more than a few years old have equivalently aged I/OdH                    support and buses), each organization and each personF                    maintaining a product or a package for OpenVMS willF                    have to justify a port to "OpenVMS IA-32", "OpenVMSG                    EM64T" or "OpenVMS AMD64", akin to the decisions andnH                    the effort involved in porting a product from OpenVMSD                    VAX to OpenVMS Alpha, or the port to OpenVMS I64.  E                    Platform ports of many of the various products can_G                    be easy, and many of the ports of applications using F                    documented OpenVMS features are expected to requireH                    little more than a source rebuild. Other products canE                    and do depend on platform-specific or undocumented_A                    features, and the associated ports can be moreeG                    involved. Regardless, ports of operating systems areiE                    very large and involved projects. The prerequisitedG                    product requirements for an OpenVMS operating system,B                    port are also non-trivial, as well-compilers inF                    particular are obviously required, and the suite ofI                    compilers provided must maintain a very high degree ofsJ                    source-level compatibility across the platforms. In theG                    case of the HP Integrity port, OpenVMS I64 V8.0 usedtG                    cross-compilers and cross-tools operating on OpenVMSiJ                    Alpha systems, while V8.2 and later have various native'                    compilers available.,  E                    The OpenVMS I64 port was centrally built using thesI                    existing OpenVMS Alpha environment and around the work E                    and the knowledge from the OpenVMS Alpha port, andsG                    OpenVMS Engineering fully expects that customers andnG                    ISVs will use and will continue to use OpenVMS AlphanI                    systems to assist with their own ports to OpenVMS I64.C                      2-12                &                    General Information        E                    OpenVMS Engineering fully expects to see customers_J                    using mixed-architecture clusters and fully shared file$                    systems, as well.  E                    OpenVMS Engineering is well aware of the AMD AMD64 I                    (64-bit) platform and processors. (At least one of thegG                    available VAX emulators can reportedly utilize parts G                    of the AMD64 instruction set, please contact the VAX E                    emulator vendor(s) or maintainer(s) for assistancevF                    and details on their products.) OpenVMS EngineeringE                    is also well aware of the Intel EM64T platform andaJ                    processors. There are no plans to provide a native portG                    of HP OpenVMS for any systems based on the AMD AMD64o1                    nor Intel EM64T architectures.n  J                    As part of the work leading to the Itanium port, seniorG                    engineers had extensively evaluated the products andeI                    the architectures available across the high-end 64-bit J                    computing space, and chose to target Itanium for 64-bitI                    environments-this while under the Compaq organization.oH                    This included looking at IA-32. HP (a co-developer ofF                    Itanium with Intel) had seperately chosen to targetD                    Intel Itanium for its high-end computer products.F                    Compaq then announced plans for the future of AlphaD                    through EV7-series products and platforms, and HPD                    (entirely seperately) announced plans for PA-RISCF                    products and platforms. The Itanium target has beenE                    maintained consistently since the Itanium port was F                    announced by Compaq, and has also been consistentlyJ                    maintained by HP and by the combined company. For thoseJ                    folks prefering to follow the schedules and the productG                    deliveries, OpenVMS Engineering had OpenVMS I64 V8.0_E                    ready (internally) ahead of schedule-and with more_F                    features available within the release than had beenG                    originally planned for the release. (For informationyC                    on and for schedules of future OpenVMS releases,nJ                    please see the roadmap that is available at the OpenVMS                    website.)  H                    OpenVMS I64 itself does not require and does not planF                    to utilize the Itanium IA-32 32-bit environment forH                    the operation of OpenVMS itself. OpenVMS I64 V8.0 andF                    later run natively on the Itanium processor family,C                    with no use of IA-32 instructions. While OpenVMSi  J                                                                       2-13 i             &                    General Information        C                    can and does support 32-bit OpenVMS applications E                    and addressing on Itanium, this is done with sign-hH                    extension addressing techniques entirely analogous toF                    what was done with 32-bit applications operating inH                    the 64-bit Alpha environment. Both OpenVMS 32-bit andH                    64-bit applications operate within the native ItaniumG                    instruction set and run-time environment, and do not 5                    use the Itanium IA-32 environment.   H                    But yes, a native IA-32 port or a native AMD AMD64 orF                    Intel EM64T port of OpenVMS would certainly be niceE                    to have-this, of course, following the traditionalSI                    Linux preference for having a Linux port available forrE                    most (all?) computer architectures known, and evengC                    for certain high-end refrigerators and toasters,mD                    and similar appliance-like devices. (The downsideC                    of this all-encompassing approach: this requiresuC                    near-infinite engineering and support costs from F                    the various vendors involved, and the qualificationF                    efforts and costs of most everything-everywhere. OrH                    reduced or eliminated testing and support efforts. OrG                    an unfortunate combination of these two. These costsvG                    are huge, and the benefits derived from the work areoF                    comparatively small when given the comparable costsH                    of more targeted (and thus supported and supportable)G                    hardware configurations-the platform targets are and D                    must be carefully selected and considered by eachI                    vendor. Put another way, there are no plans to provide I                    a native port of HP OpenVMS for systems based on Intel G                    IA-32 processors, nor for systems based on AMD AMD64 @                    nor Intel EM64T architectures and processors.  B                    All this material having been written, have youE                    looked at the system configurations and pricing of I                    the available HP Integrity Intel Itanium systems? Low- H                    end computer hardware is clearly a commodity product,F                    and the systems are priced, serviced, upgraded, andE                    replaced accordingly. Intel Itanium is a commodity G                    microprocessor presently used in platforms available G                    from various hardware vendors, including (obviously) J                    from HP. Further, Itanium is a microprocessor availableF                    from and supported by Intel, a semiconductor vendorC                    known for exceedingly high-volume microprocessoraC                    fabrication process and production capabilities.                       2-14                &                    General Information        I                    For information on supported platforms and processors,sF                    please see the OpenVMS Software Product Description                    (SPD) at:  9                    o  http://h18000.www1.hp.com/info/spd/X  H                       OpenVMS typically uses SPD 25.01.xx, SPD 41.87.xx,'                       and SPD 82.35.xx.o  >                    Please see Section 14.4.5 for Intel Itanium                    terminology.   D           __________________________________________________________A           2.11  Are there any network-accessible OpenVMS systems?w  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 OpenVMS J                       enthusiasts. This system has BASIC, Pascal, Fortran,E                       and C compilers installed. If you would like an >                       account on Hobbes, please see the FAQ at  4                      o  http://www.hobbesthevax.com/  /                    o  OpenVMS Galaxy Test-DriveeF                       HP currently offers an OpenVMS Galaxy Test-DriveA                       system, based on an AlphaServer 4100 seriesrJ                       configured as two instances of the OpenVMS operating8                       system. For details, please visit:  4                      o  http://www.testdrive.hp.com/  (                    o  HP DSPP Test-DriveC                       The HP DSPP program offers various test-drivec@                       systems, including an HP Integrity Itanium>                       development system and an HP OpenVMS I64D                       installation on an HP Integrity rx2600 server.G                       (The DSPP program can offers discount, LMF PAKGENaD                       PAK generation support, and other benefits forF                       developers.) For details on the DSPP program andC                       on the test-drive systems, please see section 5                       Section 2.8.3 and please visit:v  4                      o  http://www.testdrive.hp.com/  /                      o  http://www.hp.com/dspp/t  J                                                                       2-15               &                    General Information        E                       The test-drive systems do require registration, ;                       though access to the systems is free.d  #                    o  EncompasservefG                       Encompasserve offers free access an OpenVMS Alphan                       system.o  2                      o  telnet://eisner.decus.org/                      o  OpenECSoH                       OpenECS offers free access to a VAX 6000 model 530:                       system. If interested, please visit:  1                      o  http://vax6k.openecs.org/'  *                    o  The Deathrow ClusterJ                       The maintainers of the Deathrow Cluster offer accessD                       to an OpenVMS VAX and an OpenVMS Alpha system,.                       configured in a cluster.  5                      o  telnet://deathrow.vistech.net   ;                    o  The Preatorian Public OpenVMS Cluster J                       The maintainers of the Deathrow Cluster offer accessE                       to an OpenVMS Alpha cluster. Details are at thet+                       website listed below:   2                      o  http:://www.preatorian.net  D           __________________________________________________________2           2.12  What version of OpenVMS do I need?  E                    For information on supported platforms, please see I                    the OpenVMS Software Product Description (SPD) for theh:                    particular OpenVMS version of interest.  9                    o  http://h18000.www1.hp.com/info/spd/   H                       OpenVMS typically uses SPD 25.01.xx, SPD 41.87.xx,'                       and SPD 82.35.xx.i  I                    For a table of the minimum and (as applicable) maximumPJ                    OpenVMS versions required for various platforms, pleaseG                    see the hardware support chart at HP OpenVMS websiteoJ                    and (as available) the following (potentially volatile;'                    intra-website) link:   ;                    o  http://h71000.www7.hp.com/openvms/hw_ '                       supportchart.htmln                      2-16s               &                    General Information        ?                    For information on the Multia, related Alpha >                    single-board computers, or other officiallyE                    unsupported systems, please see Section 14.4.1 andd$                    Section 14.4.2.1.  F                    The following is a rule-of-thumb for Alpha platformE                    support. The table Table 2-5 contains the earliestpF                    OpenVMS Alpha release with support for a particular3                    series of Alpha microprocessors:s  J           ________________________________________________________________8           Table 2-5  OpenVMS Alpha Version Rule-Of-Thumb  J                    _______________________________________________________4                                MicroprocessorOpenVMSJ                    Generic_____Generation____Version_____General_Comments_  E                    EV4         21064         V1.0        few systems; I                                                          most EV4 requirerG                                                          later; upgradeeB                                                          available  C                    EV5         21164         V6.2        subsequentcJ                                                          upgrade available  C                    EV56        21164A        V6.2-1H3    subsequent H                                                          upgrade to V7.1B                                                          and later  C                    EV6         21264         V7.1-2      subsequent J                                                          upgrade typicallyE                                                          to V7.2-1 or_>                                                          later  C                    EV67        21264A        V7.1-2      subsequenteJ                                                          upgrade typicallyE                                                          to V7.2-1 orw>                                                          later  K                    EV68        21264B, C     V7.2-1      believed/probable; E                                and D                     currently an D                                                          unconfirmedJ           _______________________________________________expectation______  ?                    Specific hardware present and various systemmJ                    configurations can require OpenVMS Alpha releases later6                    than those referenced in Table 2-5.  J                                                                       2-17 c  e          &                    General Information      D           __________________________________________________________2           2.13  How can I submit OpenVMS Freeware?  G                    For the guidelines and submission info, please visitn                    the URL:   <                    o  http://www.hp.com/go/openvms/freeware/  C                    To order the current OpenVMS Freeware CD-ROM kit H                    (shipping and handling charges apply), please request+                    part number QA-6KZAA-H8.d  D           __________________________________________________________0           2.14  Porting applications to OpenVMS?  G                    Porting can range from simple to rather complex, andGI                    depends on the features used on the original platform._  I                    This section covers generic porting, and porting among G                    OpenVMS VAX OpenVMS Alpha, and OpenVMS I64. (Porting_C                    among OpenVMS VAX, OpenVMS Alpha and OpenVMS I64_F                    is often quite simple and involves little more thanJ                    rebuilding from source, though a few applications usingI                    features specific to the platform or the architecture, J                    or using undocumented or unsupported interfaces can andG                    likely will require some additional effort to port.)e  I                    Several manuals on porting from OpenVMS VAX to OpenVMSCH                    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:n  7                    o  http://www.hp.com/go/openvms/doc/_  H                    Documentation on porting to OpenVMS I64 is available,                    as well.   I                    Details on the C programming environment are available                     at:  C                    o  http://www.openvms.compaq.com/commercial/c/c_h                        index.html                      2-18b r  n          &                    General Information        I                    Details on porting VAX C to HP C are are available at:V  G                    o  http://www.openvms.compaq.com/commercial/c/index_                        vax.htmt  >                    An OpenVMS Porting Library is available at:  M                    o  http://www.openvms.compaq.com/ebusiness/Technology.html   H                    Information on the Enterprise Toolkit, a Visual-basedJ                    development environment for developing applications forG                    OpenVMS using a Microsoft platform, is available at:_  E                    o  http://www.openvms.compaq.com/commercial/et/et__                        index.html  C                    Details on DCE, CORBA, BridgeWorks, and COM/DCOM_.                    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/   F                    A wide variety of programming development tools andG                    middleware are available as commercial products (eg: C                    DECset, IBM WebSphere MQ-formerly MQseries), and_F                    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.15  What resources are available to OpenVMS software                 developers?   G                    The HP Developer and Software Product Partner (DSPP) D                    program is open to and intended to support and toH                    assist HP OpenVMS software partners, consultants, and%                    service providers:o  -                    o  http://www.hp.com/dspp/   J                    DSPP provides members with various benefits, please see+                    the website for details.l  J                                                                       2-19 M             &                    General Information        G                    For those not familiar with the DSPP program or with G                    its history, the DIGITAL Association of Software and_F                    Application Partners (ASAP) program and the DIGITALF                    Independent Software Vendors Network (ISVN) programI                    were incorporated into the Compaq CSA program, and the J                    CSA program has subsequently been incorporated into the#                    HP DSPP program.   I                    Please see Section 2.8.3 for additional details on the                      DSPP program.  D           __________________________________________________________?           2.16  memory management, resource management, process                   scheduling, etc?  I                    So you have been instructed to write a school researchsC                    paper on OpenVMS, and you need technical content_F                    on the OpenVMS Virtual Memory System, on any memoryG                    segmentation, on OpenVMS Resource Management, on thePF                    OpenVMS File System, on the OpenVMS user interface,                    etc.s  E                    Invariably, your professor/instructor/teacher willeD                    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)a  0                    o  Interprocess comunications  B                    o  Process or system synchronization constructs  =                    o  Memory management and/or virtual memorya$                       implementation  0                    o  RMS or XQP file structures  )                    o  Resource managements  +                    o  History of HP OpenVMSo  C                    o  History of Compaq and/or of Digital Equipmentl'                       Corporation (DEC)e                      2-20h b             &                    General Information        E                    Any particular presentation or research paper, and C                    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 and_G                    scholastic research projects really has little to doiE                    with the subject matter, it is a task specificallynD                    intended to teach the student(s) (eg: you) how toE                    perform the research. The instructor already knowsVG                    most of (all of?) the information that you have been,$                    asked to collect.  D                    For very technical details on OpenVMS and OpenVMSI                    internals, the book you want is the Internals and DatanE                    Structures Manual (IDSM), available in your schooleH                    or computing center library, and the IDSM can also beG                    purchased. Additional technical details of the Alpha I                    microprocessor are available in the Alpha ArchitectureaG                    Reference Manual documentation that is available fordG                    download. (Pointers to Alpha technical documentation A                    are available in Section 14.6, and elsewhere.)   I                    For higher-level (less technical) details, the OpenVMSlJ                    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.i  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 performoI                    at least basic research on your own, regardless of thee                    topic.   D           __________________________________________________________+           2.17  Basic Units of Measurement?r  H                    OpenVMS and the underlying hardware use various unitsJ                    of measurement for disk and memory storage, and relatedC                    abbreviations also typically exist. This sectioneC                    covers the most common units, and the associatedg!                    abbreviations.i  J                                                                       2-21 a  d          &                    General Information      '           _____________________________e5           2.17.1  How many bytes are in a disk block?E  C                    A disk block is the minimum unit of disk storageX)                    allocation in OpenVMS.   G                    Under OpenVMS VAX and OpenVMS Alpha, the disk volume G                    block size is consistent, with each block containingO                    512 bytes.4  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 totalrD                    size of the volume storage bitmap. The allocationE                    granularity is known as the volume cluster factor-oG                    the cluster factor is the number of blocks in a disksH                    cluster, and it is the smallest number of blocks that@                    can be allocated on a particular disk volume.  I                    Prior to OpenVMS V7.2, the maximum permissible size oftG                    the bitmap requires larger cluster factors as volumelH                    sizes increase. Starting with V7.2, the bitmap can beH                    larger, and cluster factors as small as one block can                    be used.   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 sequential G                    files (only), the FFB (XAB$W_FFB, in the File Header E                    XAB) value can be used to find out how much of theiB                    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 the E                    cluster factors, which can be from one block up to E                    (potentially) clusters of eighteen blocks or more, H                    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.)                       2-22d               &                    General Information        A                    OpenVMS assumes that the device driver and theBI                    underlying storage device will present the file systemXJ                    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 filelG                    from DCL, one option uses the f$file_attributes item I                    EOF, multiplied by the size of a block in bytes (512).iI                    This does not account for the unused space in the lastsH                    block of a sequential file, but it also does not haveF                    to differentiate sequential files from other files.  '           _____________________________p6           2.17.2  How many bytes are in a memory page?  I                    A memory page is the minimum unit of memory allocationeE                    in OpenVMS. With OpenVMS VAX, the memory page sizeeG                    matches the disk block size: it is always 512 bytes.t  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 ae-                    page size of 64 kilobytes.e  I                    On OpenVMS I64, the memory page size is also variable,sB                    ranging from 4096 bytes (4 kilobytes) up to 256I                    megabytes (MB) and potentially up to 4 gigabytes (GB).sI                    As with OpenVMS Alpha, sys$getsyi and f$getsyi and theaI                    PAGE_SIZE itemcode can and should be used to determine_H                    the current system page size. In general, OpenVMS I64B                    will use a page size of 8 kilobytes, or larger.  G                    On OpenVMS Alpha and on OpenVMS I64, a 512 byte area I                    of memory- equivalent in size to an OpenVMS VAX memoryr;                    page-is often refered to as a "pagelet".n      J                                                                       2-23 _  _          &                    General Information      '           _____________________________y@           2.17.3  How do I convert? Disk Blocks? KB, MB, GB, TB?  I                    The smallest granularity of disk storage addressing is J                    called a disk block, or sometimes a disk sector. GroupsE                    of disk blocks are usually organized together intolF                    the smallest unit of storage that can be allocated,E                    and this unit is called a disk cluster. The numberDG                    of blocks in a cluster is the cluster factor, and isdC                    established when the disk volume is initialized.,  I                    Each individual disk block is composed of five hundred I                    twelve (512) bytes, or one-half kilobyte. Each byte isuI                    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 disk F                    storage, while disk storage capacity specificationsH                    from most storage vendors will generally use base ten                    notation.  F                    An OpenVMS disk block is 512 bytes in size; this is:                    one-half kilobyte in base two notation.  @                    The following table describes the prefix, theH                    abbreviation, and the associated base ten (as used byJ                    marketing and by storage vendors) and base two (OpenVMS?                    and various other operating systems) values.t  A                       Base Ten                           Base TwonO                       --------------------------------   ----------------------yO             Kilobyte  (KB)  10**3                 1000   2**10             1024iO             Megabyte  (MB)  10**6              1000000   2**20          1048576sO             Gigabyte  (GB)  10**9           1000000000   2**30       1073741824 O             Terabyte  (TB)  10**12       1000000000000   2**40    1099511627776 O             Petabyte  (PB)  10**15    1000000000000000   2**50 1125899906842624(O             Exabyte   (EB)  10**18 1000000000000000000   2**60 ****************i  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 orsE                    hexadecimal, respectively) value, the value is far D                    nicer. Specifically, the value is 10000000000 andF                    40000000 when represented in octal and hexadecimal,                     respectively.                         2-24               &                    General Information        5                                          FAQ Notationt  E                       Within the OpenVMS FAQ, a thousand bits (eithersE                       assuming base two or base ten, as determined bypE                       the context) is refered to as a kilobit, and ispF                       always represented by the appreviation Kb, whileF                       a thousand bytes is refered to as a kilobyte andE                       is always abbreviated as KB. Similar notationaltF                       usage also holds for Megabits (Mb) and Megabytes<                       (MB), and for the various other units.  D                    OpenVMS operating system references to system andE                    storage are generally to the base-two version (eg:iD                    1024, in the case of a kilobyte or kilobit) whileJ                    storage hardware references and hardware specificationsD                    are generally to the base-ten version (eg: 1000).  I                    To convert OpenVMS disk blocks to (base two) kilobytes E                    (KB; 1024 bytes), simply divide by two. To convertoI                    blocks to (base two) megabytes, divide by 2048. Blocks2C                    to (base two) gigabytes (GB), divide by 2097152.eI                    These particular divisions can also be performed usingsH                    bitshifts: to divide a value by two, shift the binary7                    value rightward by one bit position.   J                    To convert OpenVMS disk blocks to (base ten) kilobytes,4                    divide by approximately 1.953125.  G                    For those folks with an interest in odd applications F                    for prefixes, and particularly for those folks alsoE                    rummaging around deep within the OpenVMS operating H                    system, a microfortnight is approximately one second.                        J                                                                       2-25                         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 isc(                    copyrighted material.  E                    HTML format on-line product documentation sets forfG                    specific HP OpenVMS products are presently availablen                    at:  7                    o  http://www.hp.com/go/openvms/doc/b  J                    Documentation is offered on separately orderable CD-ROMG                    media through a subscription to the Consolidated On-rI                    Line Documentation (ConOLD) product (see Section 2.6.) I                    ConOLD manuals are readable with BNU, a viewer that is H                    supplied with the documentation distribution. BNU canG                    display HTML, Bookreader, and documentation in othern                    formats.n  G                    MGBOOK, a viewer for Bookreader-format documentationwH                    is available for character-cell terminals (eg. VTxxx)F                    via the WKU VMS Freeware file server - see question,                    Section 13.1 for details.  D                    Information on the XPDF DECwindows PDF viewer forF                    OpenVMS is available in Section 13.1, and XPDF kitsF                    are available on various Freeware distributions. AnG                    alternative on OpenVMS Alpha uses the Adobe Java PDF E                    viewer, though this viewer is generally considered E                    to be both slower and more resource-intensive when /                    compared to the XPDF viewer.s            J                                                                        3-1                                    Documentation      D           __________________________________________________________B           3.2  What online information and websites are available?  G                    On your OpenVMS system, the HELP command can provide D                    a wealth of information, not only on DCL commandsD                    but on system services (HELP System_Services) andE                    Run-Time Library routines (HELP RTL_Routines). The H                    introduction displayed when you type the HELP commandI                    with no additional keywords provides further pointers.   9                    OpenVMS Marketing runs a web server at 0                    http://www.hp.com/go/openvms/  D                    Here, you will find product information, strategyJ                    documents, product roadmaps, the contents of the latest4                    OpenVMS Freeware CD-ROM and more.  J           ________________________________________________________________%           Table 3-1  OpenVMS Websites   J           ________________________________________________________________J           URL_______Sponsor_______________________________________________             HP OpenVMS Marketing  1                     http://www.hp.com/go/openvms/o             Encompass DFWCUG  3                     http://www.openvmshobbyist.org/i             Arne Vajhj   0                     http://www.levitte.org/~ava/             Saiga Systemss  )                     http://www.saiga.com/r             Wayne Sewell  -                     http://www.tachysoft.com/              proGIS Software,  4                     http://www.progis.de/openvms.htm             Jeff Cameron  0                     http://www.jcameron.com/vms/  B           David Mathog's (quite useful) information about OpenVMS.  C                     http://seqaxp.bio.caltech.edu/www/soft_doc.html              Cracking                      3-2                                    Documentation      J           ________________________________________________________________-           Table 3-1 (Cont.)  OpenVMS Websitess  J           ________________________________________________________________J           URL_______Sponsor_______________________________________________             "The Beave" F           Includes system cracking information that can be of interestI           to OpenVMS System Managers, and to OpenVMS Network and Security            Managers.m  C                     http://www.vistech.net/users/beave/hack-vms-faq              Undocumented Featuresn             DECUS Deutchland  D                     http://www.decus.de:8080/www/vms/qaa/undoc.htmlx             Arne Vajhjs  =                     http://www.levitte.org/~ava/vms_tip.htmlxo  H           The OpenVMS Freeware contains various examples of undocumented!           features and interfacesn  :                     http://www.hp.com/go/openvms/freeware/  G           Comparision of UNIX and Linux shell commands and DCL Commandse  G                     http://www.mcsr.olemiss.edu/unixhelp/VMStoUNIX.htmlu             Bibliographies  >                     http://www.levitte.org/~ava/vms_book.htmlx             Introductory  I                     Please see Table 3-2 for listings of introductory weba0                     sites and related materials.             Programmingr  $           An OpenVMS Programming FAQ  @                     http://www.pdv-systeme.de/users/martinv/VMS_(                     Programming_FAQ.html             Networking  I           Tutorial information and tips for connecting OpenVMS systems to            the Internet  3                     http://www.tmesis.com/internet/   F           Documentation and Specifications for DECnet Phase IV, DECnet:           task-to-task DCL examples, and a whole lot more.  8                     http://www.hp.com/go/openvms/wizard/  J                                                                        3-3 r  i                               Documentation      J           ________________________________________________________________-           Table 3-1 (Cont.)  OpenVMS Websites   J           ________________________________________________________________J           URL_______Sponsor_______________________________________________  "           HP OpenVMS Documentation  J                     Please see Table 3-2 for listings of documentation web0                     sites and related materials.             System Performance  %                     See Section 14.2.              Patch (ECO) Kits  B                     For the HP Services FTP server hosting VariousG                     contract-access and non-contract access ECO (patch)b3                     kits, see section Section 5.17.              Catalogs and Pricing  7           HP Product QuickSpecs and product informationt  9                     http://www.hp.com/go/productbulletin/   :           The HP Systems and Options Catalog (SOC) archive  3                     http://www.compaq.com/products/ =                     quickspecs/soc_archives/SOC_Archives.html   (           Hardware and Software Archives  E           The VAXarchive, including hardware and software information   8                     http://vax.sevensages.org/index.html  &           A VAX to Alpha upgrade diary  J                     http://www3.sympatico.ca/n.rieck/docs/alpha_diary.html  =           Scanned versions of old DIGITAL manuals from DFWCUGe  >                     http://www.montagar.com/~patj/dec/hcps.htm  E           A wide variety of HP VAX, Alpha, platform and other product ;           documentation. Some introductory, some technical.   I                     http://www.compaq.com/support/techpubs/qrg/index.htmlt  %           dtrwiz's Datatrieve website.  J           __________http://dtrwiz.home.netcom.com/________________________                      3-4 a  n                               Documentation      D           __________________________________________________________F           3.3  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]   C                    If the help text you want is not in the standard E                    help library (for example, it's help for a utilitysC                    such as MAIL that has its own help library), addnC                    /LIBRARY=libname after the HELP verb. To see the A                    names of help library files, do a directory of "                    SYS$HELP:*.HLB.  D           __________________________________________________________=           3.4  Does OpenVMS Marketing have an e-mail address?e  B                    Yes - if you can't get the answers to marketingJ                    questions elsewhere, if you have comments or complaintsJ                    about OpenVMS, send mail to openvms-info{atsign}hp.com.G                    This address is not a support channel, and is solelyiE                    intended to provide informal method to communicatee>                    directly with members of OpenVMS Marketing.  D           __________________________________________________________C           3.5  Where can I learn about OpenVMS executive internals?   B                    The OpenVMS Internals and Data Structure manualC                    (IDSM) explains how the OpenVMS executive works.vG                    The book covers the operating system kernel: processpH                    management; memory management; the I/O subsystem; andE                    the mechanisms that transfer control to, from, andeI                    among these. It gives an overview of a particular areasF                    of the system, followed by descriptions of the dataJ                    structures related to that area and details of the code,                    that implements the area.  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,vJ                    V6.2, V7.0, V7.1, etc) and many details in the book areG                    no longer accurate, it continues to provide a strongt?                    conceptual description of OpenVMS internals.   J                                                                        3-5 t                                  Documentation        H                    This book has been split into five pieces, each to beG                    updated separately. The first such volume, published B                    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 it_                    implies._  D                    The internals books are available through Digital)                    Press, see Section 3.6_  D           __________________________________________________________B           3.6  Where can new users find tutorial information about                OpenVMS?l  H                    First, see if your local site has information on thisG                    topic. Each site can have site-specific features andVH                    configuration. Some sites will have site-specific newG                    user's documentation, covering various site-specificlJ                    things that are difficult or impossible for the general2                    OpenVMS documentation to cover.  '           _____________________________ #           3.6.1  Tutorial Websites?   @                    Various websites with OpenVMS information areE                    available; Table 3-2 contains some suggested URLs.   J           ________________________________________________________________@           Table 3-2  OpenVMS Tutorial and Documentation Websites  J                    _______________________________________________________J                    URL_______Sponsor______________________________________                      Introductory   <                    http://www.levitte.org/~ava/vms_faq.htmlx  C                    http://seqaxp.bio.caltech.edu/www/vms_sheet.html   C                    http://seqaxp.bio.caltech.edu/www/vms_beginners_                     faq.html   ;                              Various introductory materials.  9                    http://www.montagar.com/openvms_class/a                      3-6 e  y                               Documentation      J           ________________________________________________________________H           Table 3-2 (Cont.)  OpenVMS Tutorial and Documentation Websites  J                    _______________________________________________________J                    URL_______Sponsor______________________________________  E                              Members of the Encompass DFWCUG maintain7E                              a website with many materials available, A                              including an Overview of OpenVMS, an D                              Introduction to DCL and the TPU Editor,E                              Advanced DCL Command Procedures, OpenVMS ?                              Operations: Batch, Print, Tape, anfC                              Introduction to OpenVMS Management, toC@                              OpenVMS User Management, to OpenVMSG                              Network Management, and to OpenVMS Cluster F                              Management. These training materials haveF                              been presented at various DECUS symposia.  F                    http://www.mcsr.olemiss.edu/unixhelp/VMStoUNIX.html  H                              A comparison table of various command-levelJ                              tasks, with information on the UNIX and LinuxE                              shell command(s), and on the OpenVMS DCLg(                              command(s).  +                    HP OpenVMS Documentationd  4                    http://www.hp.com/go/openvms/doc/  H                              Various introductory guides as well as moreJ                              advanced manuals are available in the OpenVMSC                              and layered product documentation set.k  &                    HP OpenVMS Training  ;                    http://www.compaq.com/training/home.htmlO?                    http://www.openvms.compaq.com/wbt/index.html   I                              HP offers training information and TechnicaloH                              Resource Kits (TRKs) and other Training forH                              OpenVMS. An OpenVMS certification (testing)7                              program is also available.i  /                    http://www.jcameron.com/vms/h  ,                              An OpenVMS Quiz  +                    http://www.CCSScorp.com/l  B                              CCSS Interactive Learning has OpenVMS/                              training materials   J                                                                        3-7 c  h                               Documentation      J           ________________________________________________________________H           Table 3-2 (Cont.)  OpenVMS Tutorial and Documentation Websites  J                    _______________________________________________________J                    URL_______Sponsor______________________________________  +                    http://www.acersoft.com/o  G                              AcerSoft Training information, and Shannon +                              Knows Punditry   )                    http://www.mindiq.com/e  8                              MindIQ training information  ,                    http://www.quadratrix.be/  G                              Quadratrix; OpenVMS training, products andeG                              services; affiliated with Global Knowledge J           ___________________and_KeyJob___________________________________  '           _____________________________w%           3.6.2  Books and Tutorials?w  B                    Some of the OpenVMS books that are or have been;                    available from the Digital Press imprinte  (                    o  http://www.bh.com/  +                    are listed in Table 3-3:   J           ________________________________________________________________           Table 3-3  DP Booksr  J           ________________________________________________________________J           Title_and_Author_____________________ISBN_______________________  <           Getting Started with OpenVMS System  1-55558-281-8           Management           David Donald Miller   <           Introduction to OpenVMS, 5th         1-55558-194-3           Editions           Lesley Ogilvie Rice   <           Introduction to OpenVMS              1-878956-61-2           David W Bynone  <           OpenVMS Alpha Internals: Scheduling  1-55558-156-0           and Process Control                       3-8 O  V                               Documentation      J           ________________________________________________________________%           Table 3-3 (Cont.)  DP Booksm  J           ________________________________________________________________J           Title_and_Author_____________________ISBN_______________________  <           OpenVMS AXP Internals and Data       1-55558-120-X!           Structures: Version 1.5r  <           OpenVMS System Management Guide      1-55558-143-9           Baldwin, et al  <           The OpenVMS User's Guide, Second     1-55558-203-6           Editionp           Patrick Holmay  <           Using DECwindows Motif for OpenVMS   1-55558-114-5           Margie Sherlockr  <           VAX/VMS Internals and Data           1-55558-059-9!           Structures: Version 5.2l  <           Writing Real Programs in DCL,        1-55558-191-9           Second Edition%           Hoffman and Anagnostopoulosd  <           Writing OpenVMS Alpha Device         1-55558-133-1           Drivers in CJ           Sherlock_and_Szubowicz__________________________________________  J                    For various featured OpenVMS books, also please see the5                    books link at the OpenVMS website:s  2                    o  http://www.hp.com/go/openvms  F                    For a bibliography of various OpenVMS books, please                    see:   @                    o  http://www.levitte.org/~ava/vms_book.htmlx  D           __________________________________________________________8           3.7  What OpenVMS mailing lists are available?  I                    Various OpenVMS mailing lists are available, with someq@                    of the available lists detailed in Table 3-4.  J                                                                        3-9    v                               Documentation        J           ________________________________________________________________*           Table 3-4  OpenVMS Mailing Lists  J           ________________________________________________________________J           Subscription____________________Interest_Area___________________  >           OpenVMS Freeware archive        FSupdate@goatley.comI           announcement list               FSupdate-request@goatley.com[1]   F           Two-way echo of                 VMSnet-Internals@goatley.com;           vmsnet.internals                VMSnet-Internals- @                                           request@goatley.com[1]  ?           OpenVMS Alpha Internals         Alpha-IDS@goatley.com J           discussions                     Alpha-IDS-request@goatley.com[1]  ?           BLISS discussions               BLISSters@goatley.com J                                           BLISSters-request@goatley.com[1]  C           Process Software MultiNet       Info-MultiNet@process.com 8           mailing list (news gateway)     Info-MultiNet-@                                           request@process.com[1]  B           Process Software TCPware        Info-TCPware@process.com7           mailing list (news gateway)     Info-TCPware-i@                                           request@process.com[1]  ?           Process Software PMDF mailing   Info-PMDF@process.comcJ           list (news gateway)             Info-PMDF-request@process.com[1]  F           The SRI CHARON-VAX VAX          CHARON-VAX-Users@process.com;           emulator package                CHARON-VAX-Users-o@                                           request@process.com[1]  :           Info-Zip's Zip & UnZip          Info-Zip@wku.eduE           discussion list                 Info-Zip-Request@wku.edu[1]v  <           RADIUS-VMS, a RADIUS server     radius-vms@dls.netG           for OpenVMS discussion forum    radius-vms-request@dls.net[1].  :           Internet Service Providers      vms-isps@dls.netE           (ISPs) running OpenVMS          vms-isps-request@dls.net[1]   J           ________________________________________________________________H           [1]This is the subscription address. Usually, you will want toF           send a mail message with no subject line, and a SUBSCRIBE or7           HELP command in the body of the mail message.r                      3-10o e  l                               Documentation      J           ________________________________________________________________2           Table 3-4 (Cont.)  OpenVMS Mailing Lists  J           ________________________________________________________________J           Subscription____________________Interest_Area___________________  A           Users of Mark Daniel's WASD     http://wasd.vsm.com.au/ $           web server for OpenVMS VAX'           and Alpha exists. Information_$           about this list server and(           details on how to subscribe to'           the list are available at thee           referenced website.   U           VMS Forum                       http://www.neurophys.wisc.edu/comp/ava/vms_oJ           ________________________________forum.htmlx_____________________  D           __________________________________________________________D           3.8  What is this Ask The Wizard website I've heard about?  E                    The HP OpenVMS Ask The Wizard (ATW) website was an I                    informal area discussing OpenVMS, containing questionsi;                    and answers on a wide variety of topics.n  :                    o  http://www.hp.com/go/openvms/wizard/  D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the availablekB                    ATW Wizard.zip archive, please see Section 3.8.  I                    To access a cited topic directly, use the URL filenamebI                    WIZ_topic-number.HTML, or use the topic search engine.sD                    Cited topics are shown in parentheses, and act asG                    unique topic addresses. These should not be confusedlE                    with the relative topic numbers shown at the site.zI                    For example, the topic (1020) can be accessed directlyiH                    using the URL filename wiz_1020.html, at the web site8                    that the following URL resolves into:  :                    o  http://www.hp.com/go/openvms/wizard/  E                    A zip archive (named wizard.zip) containing all of G                    the available topics and questions can be downloaded D                    from the above URL. The wizard.zip zip archive isH                    completely regenerated when/if existing topics postedE                    out to the ATW website are updated. Copies of this D                    wizard.zip archive also generally ship out on the-                    OpenVMS Freeware, as well.   J                                                                       3-11 t     --  mN  ---------------------------- #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.come   ------------------------------  # Date: Mon, 11 Apr 2005 19:42:57 GMTt- From: hoffman@xdelta.hp.nospam (Hoff Hoffman) < Subject: OpenVMS Frequently Asked Questions (FAQ), Part 3/111 Message-ID: <5rA6e.3486$IL.2561@news.cpqcorp.net>    Archive-name: dec-faq/vms/part3  Posting-Frequency: quarterly Last-modified: 11 Apr 2005 Version: VMSFAQ_20050411-03.TXT(      a                               Documentation        I                    New (informal) questions and discussions are now being H                    directed away from the ATW area to the ITRC area, and>                    specifically to the ITRC discussion forums:  -                    o  http://www.itrc.hp.com/   D           __________________________________________________________F           3.9  Where can I find the latest C run-time library manuals?  G                    The C run-time library (RTL) reference documentationlG                    has been moved from the C language documentation setrH                    to the OpenVMS documentation set. For the most recentE                    version of the C RTL documentation and the OpenVMSeF                    standard C library, please see the OpenVMS manuals.  H                    In addition to the user-mode C RTL, there is a secondI                    kernel-mode RTL accessable to drivers on OpenVMS AlphabJ                    and OpenVMS I64. For details on this second library andG                    on the duplicate symbol errors that can be triggered I                    when this library is referenced during an incorrectly-eF                    specified LINK command, please see Section 10.22.1.F                    For general information on this kernel RTL, see theJ                    Digital Press book Writing OpenVMS Device Drivers in C.H                    For details, please see the associated OpenVMS source)                    listings distribution.   7                    o  http://www.hp.com/go/openvms/doc/2                                                      3-12r a  s                    J                    _______________________________________________________  '           4        Time and Timekeepingt      C                    This chapter discusses time, timekeeping, system D                    time synchronization, clock skew and clock drift,I                    implications of using SUBMIT/AFTER=TOMORROW, and others'                    time-related topics.   D           __________________________________________________________>           4.1  A brief history of OpenVMS Timekeeping, please?  D                    Why does OpenVMS regards November 17, 1858 as the'                    beginning of time...s  F                    The modified Julian date adopted by the SmithsonianI                    Astrophysical Observatory (SAO) for satellite trackingnJ                    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.eI                    The Julian day was 2435839 on January 1, 1957. This isaJ                    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 wouldoH                    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 18l$                    bits of one word.  I                    Eighteen bits allows the truncated Julian Day (the SAO G                    day) to grow as large as 262143, which from November H                    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 theyF                    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                                                                        4-1 a  v          '                    Time and Timekeeping         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 for 5                    the Roman Emperor Julius Caesar!).   E                    Why 4713 BC? Scaliger traced three time cycles and F                    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 from0.                    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 start G                    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 use )                    during different eras.e  +                    The following web sites:y  J                    o  http://www.openvms.compaq.com/openvms/products/year-$                       2000/leap.html  5                    o  http://www.eecis.udel.edu/~ntp/   *                    o  http://www.nist.gov/  ;                    o  http://www.boulder.nist.gov/timefreq/t  A                    o  http://www.tondering.dk/claus/calendar.html   L                    o  http://es.rice.edu/ES/humsoc/Galileo/Things/gregorian_#                       calendar.htmli  H                    are all good time-related resources, some general and,                    some specific to OpenVMS.  '           _____________________________ <           4.1.1  Details of the OpenVMS system time-keeping?                      4-2               '                    Time and TimekeepingM      '           _____________________________h7           4.1.1.1__VAX_hardware_time-keeping details...a             4.1.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.J                    The VAX Time-Of-Year (TOY) clock (used to save the timeI                    over a reboot or power failure) is specified as havingdH                    an accuracy of 0.0025%. This is a drift of roughly 65%                    seconds per month.t  J                    The VAX Interval Time is used to keep the running time,G                    and this has a specified accuracy of .01%. This is ai?                    drift of approximately 8.64 seconds per day.a  F                    Any high-IPL activity can interfere with the IPL 22E                    or IPL 24 (this depends on the VAX implementation)aG                    clock interrupts-activities such as extensive device G                    driver interrupts or memory errors are known to slowp                    the clock.   '           _____________________________ #           4.1.1.1.2  EXE$GQ_SYSTIME   F                    This is the OpenVMS VAX system time cell. This cellG                    contains the number of 100ns intervals since a knownnF                    reference. This cell is incremented by 100000 every6           _________10ms_by_an_hardware_interval timer.  $           4.1.1.1.3  EXE$GQ_TODCBASE  G                    This cell contains the time and date the system timecE                    was last adjusted by EXE$SETTIME. It uses the samedH                    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.      J                                                                        4-3 n  o          '                    Time and Timekeeping       '           _____________________________t            4.1.1.1.4  EXE$GL_TODR  G                    This cell contains the time and date the system time E                    was last adjusted by EXE$SETTIME. It uses the same I                    format as the time of year clock. On adjustment of thefG                    system time this cell gets saved back to both memorytG                    and disk. The contents of this cell are used to testr1                    the validity of the TOY clock. C                    The system parameters SETTIME and TIMEPROMPTWAIT =                    determine how the system time will be set.i  ?                    o  IF SETTIME = 0 and the TOY clock is valid H                       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_TODR F                         THEN the system time is calculated as follows:  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 = 0wI                         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 configured H                    prompt the user to input the time - this is necessary:                    in order to boot with the correct time.                      4-4 S  r          '                    Time and Timekeepingo        G                    If either TIMEPROMPTWAIT or SETTIME are set to zero,oE                    OpenVMS VAX will use the TOY clock to get the timewA                    of year, and the year will be fetched from the D                    distribution medium. The value of the year on theG                    distribution medium (saved within the SYS.EXE image) I                    will most likely be that of when the kit was mastered, I                    and cannot be changed. Unless the current year happensuH                    to be the same year as that on the distribution, mostH                    likely the year will be incorrect. (Further, with theG                    calculation of Leap Year also being dependent on the E                    current year, there is a possibility that the date 0                    could be incorrect, as well.)  '           ______________________________9           4.1.1.2__Alpha_hardware_time-keeping details..._  9           4.1.1.2.1  Battery-Backed Watch (BB_WATCH) ChipT  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. F                    The BB_WATCH time is used to initialize the runningF                    system time during bootstrap, and the BB_WATCH timeF                    is read when the SET TIME command is issued with noG                    parameters; when the running system time is reset toiG                    the value stored in the BB_WATCH. The running system F                    time is written into the BB_WATCH when the SET TIME6                    command is issued with a parameter.  I                    The specification for maximum clock drift in the AlphapE                    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 lessnG                    than 0.000050 years of drift per year, etc. (eg: AnwJ                    error of one second over a day-long interval is roughlyG                    11ppm, or 1000000/(24*60*60).) Put another way, this H                    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) that  J                                                                        4-5 _  _          '                    Time and TimekeepingV        H                    are causing the processing of the clock interrupts to                    be blocked.  '           ______________________________#           4.1.1.2.2  EXE$GQ_SYSTIMEm  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.e  )           4.1.1.2.3  EXE$GQ_SAVED_HWCLOCKt  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, everyg5                    time EXE$GQ_SYSTIME gets adjusted..  F                    o  The system parameters SETTIME and TIMEPROMPTWAIT@                       determine how the system time will be set.  $                    o  If SETTIME = 0G                       then EXE$INIT_HWCLOCK reads the hardware clock tot*                       set the system time.  -                      o  IF TIMEPROMPTWAIT > 0nG                         THEN the value of TIMEPROMPTWAIT determines how C                         long the user is prompted to enter the timepF                         and date. If time expires and no time has beenI                         entered the system acts as if TIMEPROMPTWAIT = 0.c  -                      o  IF TIMEPROMPTWAIT = 0/C                         THEN the system time is calculated from thes=                         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.  F                    Unlike the VAX, the Alpha hardware clock tracks theF                    full date and time, not just the time of year. ThisE                    means it is possible to boot from the CD-ROM media,E                    without entering the time at the CD-ROM bootstrap.eB                    (This provided that the time and date have been+                    initialized, of course.)                       4-6 f  e          '                    Time and Timekeeping         F                    IA-64 (Itanium) hardware time-keeping details to be                    added...T  '           _____________________________pE           4.1.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 of I                    497 days, the VAX system time is stored using both the H                    TOY and the OpenVMS VAX system image SYS.EXE. BecauseH                    of the use of the combination of the TOY and SYS.EXE,F                    you need to issue a SET TIME command (with the timeI                    parameter specified) at least once between January 1st F                    and about April 11th of each year, and whenever youG                    change system images (due to booting another OpenVMS_J                    VAX system, booting the standalone BACKUP image, an ECO/                    that replaces SYS.EXE, etc).   C                    The SET TIME command (with the current time as a D                    parameter) is automatically issued during variousG                    standard OpenVMS procedures such as SHUTDOWN, and it F                    can also obviously be issued directly by a suitablyH                    privileged user. Issuing the SET TIME command (with aI                    parameter) resets the value stored in the TOY, and (if G                    necessary) also updates the portion of the time (the C                    current year) saved in the SYS.EXE system image.   C                    This VAX TOY limit is the reason why OpenVMS VAXiE                    installation kits and standalone BACKUP explicitlyrI                    prompt for the time during bootstrap, and why the timeOJ                    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).  '           _____________________________ ;           4.1.2  How does OpenVMS VAX maintain system time?   I                    VAX systems maintain an interval clock, and a hardware                     clock.   E                    The VAX hardware clock is called the TOY ("Time OfsJ                    Year") clock. The register associated with the clock is<                    called the TODR ("Time Of Day Register").  J                                                                        4-7               '                    Time and Timekeepingg        H                    The TOY clock-as used-stores time relative to JanuaryI                    first of the current year, starting at at 00:00:00.00.fJ                    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 date E                    information-and in particular, the current year-in 8                    the system image, SYS$SYSTEM:SYS.EXE.  E                    The TOY is used, in conjunction with the base datefI                    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 into the runningoE                    system as part of the system bootstrap, the system_G                    does not typically reference the TOY again, unless a H                    SET 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, and.J                    the time value reported to the user with appear to have                     slowed down.)  F                    When SET TIME is issued with no parameters, the TOYE                    clock is loaded into the system clock; the runningeD                    system clock is set to the time stored in the TOYE                    clock. This assumes the TOY clock is more accurateLB                    than the system clock, as is normally the case.  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.                                4-8 p  a          '                    Time and Timekeepinge      D           __________________________________________________________<           4.2  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,E                    DECnet-Plus DTSS (sometimes known as DECdtss), DCEuI                    DTS, and other techniques are commonly used. If you dofG                    not or cannot have IP access to one of the availableiH                    time-base servers on the Internet, then you could useI                    dial-up access to NIST or other authoritative site, or I                    you can use a direct connection to a local authorativem                    clock.   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 I                    Telephone Service (ACTS) service), and code that grabsmJ                    the time off a GPS receiver digital link, or a receiverG                    (effectively a radio and a codec) that processes the G                    time signals from radio stations WWV, WWVH, WWVB, ore                    similar.   C                    Processing the serial or hardware time protocols I                    often involves little more than reading from an EIA232wH                    (RS232) serial line from the receiver, something thatE                    is possible from most any language. Information on G                    correctly drifting the OpenVMS system clock to matchaI                    the time-base time is available within the logic of at 6                    least one OpenVMS Freeware package.  D                    One example of acquring a time-base through localD                    integrated hardware involves the IRIG time formatC                    (IRIG-A, -B, -G), a binary signal containing the_C                    current time in hours, minutes, seconds and daysoE                    since the start of the current year. IRIG can also/I                    contain the time of day as the number of seconds sinceaF                    midnight. HP Custom Systems and third-party vendorsE                    have variously offered IRIG-based reader/generatorM/                    modules for OpenVMS systems.h  C                    One of the easiest approaches is a network-basedeF                    GPS or other similar receiver. Basically, this is aF                    network server box that provides an NTP server withG                    the necessary hardware for external synchronization._B                    In addition to the antenna and the receiver andI                    processing components, these devices provide a networke  J                                                                        4-9               '                    Time and Timekeeping         F                    interface (NIC) and support for an NTP time server,D                    and applications including the NTP support withinD                    TCP/IP Services and within various third-party IPJ                    stacks can then be used to synchronize with the the NTPH                    information provided by time-base receivers. No otherG                    host software is required, and no host configuration F                    steps and no host software beyond NTP are required.  J                    Differing time servers (DECnet-Plus DTSS, DCE DTS, NTP,I                    etc) do not coexist particularly well, particularly if F                    you try to use all these together on the same node.D                    Please pick and use just one. (If needed, you canJ                    sometimes configure one package to acquire its timebaseJ                    from another protocol, but one and only one time serverI                    package should have direct control over the managementpG                    of and drifting of the local OpenVMS system time. IneG                    the specific case of DECnet-Plus DTSS, older product9J                    versions and versions V7.3 and later provide a providerJ                    module, a module which permits DTSS to acquire its timeI                    from NTP. For details on this, please see the commentsr6                    in the module DTSS$NTP_PROVIDER.C.)  I                    Unlike DECnet-Plus, TCP/IP Services NTP is not capablemF                    of connecting to a time-base other than the networkG                    time base or the local system clock. Third-party and D                    open source NTP implementations are available for$                    OpenVMS, as well.                      Useful URLs:r  J                    o  http://www.boulder.nist.gov/timefreq/service/nts.htm  K                    o  http://www.boulder.nist.gov/timefreq/service/acts.htms  ;                    o  http://www.boulder.nist.gov/timefreq/o  *                    o  http://www.time.gov/  '           _____________________________/:           4.2.1  Why do my cluster batch jobs start early?  J                    Your system time is skewed across your cluster members,I                    and the cluster member performing the queue managementiI                    tasks has a system time set later than the system time 7                    of the member running the batch job.                       4-10                '                    Time and Timekeeping         >                    This behaviour is most noticable when usingD                    SUBMIT/AFTER=TOMORROW and similar constructs, andE                    use of /AFTER="TOMMOROW+00:01:00" or such is often_F                    recommended as a way to avoid this. The combinationI                    time value specified should be larger than the maximum H                    expected time skew. In the example shown, the maximum@                    cluster clock skew is assumed less than 1:00.  D                    You can also maintain your system times in betterE                    synchronization, with available tools described in -                    Section 4.2 and elsewhere.s  '           _____________________________@7           4.2.2  Why does my OpenVMS system time drift?   E                    Memory errors, hardware problems, or most anythingtG                    operating at or above IPL 22 or IPL 24 (clock IPL isnF                    system family dependent; code executing at or aboveC                    the clock IPL will block the processing of clock.H                    interrupts), can cause the loss of system time. ClockE                    drift can also be caused by normal (thermal) clock E                    variations and even by the expected level of clockc                    drift.   G                    When clock interrupts are blocked as a result of the-E                    activity of high-IPL code-such as extensive driverRJ                    interrupt activity or a hardware error or a correctableG                    (soft) memory error-the clock will "loose" time, and[J                    the time value reported to the user with appear to haveI                    slowed down. Correctable memory errors can be a commonAG                    cause of system time loss, in other words. Heavy PCIi8                    bus traffic can also cause lost time.  I                    One bug in this area involved the behaviour of certaingI                    graphics controllers including the ELSA GLoria Synergy_F                    PBXGK-BB; the PowerStorm 3D10T effectively stallingH                    the PCI bus. See Section 5.16 for details on the ELSAG                    GLoria Synergy controller, and make certain you havei:                    the current GRAPHICS ECO kit installed.  G                    Clock drift can also be (deliberately) caused by the_8                    activity of the DTSS or NTP packages.  A                    Also see Section 4.1.1.2.1, Section 4.1.1, and_!                    Section 4.2.4._  J                                                                       4-11 _  _          '                    Time and TimekeepingW      '           _____________________________ 9           4.2.3  Resetting the system time into the past?t  G                    You can resynchronize system time using DCL commandssC                    such as SET TIME and SET TIME/CLUSTER, but thesecD                    commands can and obviously will cause the currentJ                    system time to be set backwards when the specified timeH                    predates the current system time. This time-resettingD                    operation can cause application problems, and canG                    adversely effect applications using absolute timers,hF                    applications that assume time values will always beA                    unique and ascending values, and applications.o  G                    Setting the time backwards by values of even an houroH                    has caused various run-time problems for applicationsH                    and layered products. For this reason, this techniqueJ                    was not considered supported during the Year 2000 (Y2K)C                    testing; a system or cluster reboot was stronglyUB                    recommended as the correct means to avoid these                    problems.  J                    Application programmers are encouraged to use the time-I                    related and TDF-related events that are available with F                    the $set_system_event system service, and/or to useF                    UTC or similar time, as these techniques can permitE                    the application to better survive retrograde clock F                    events. (There is an ECO to repair problems seen inI                    the DECnet-Plus support for generating TDF events fromeI                    DTSS, and this applies to V7.3 (expected to be in ECO4nG                    and later) V7.3-1 (expected to be in ECO3 and later)eG                    and V7.3-2 (expected to be in ECO1 and later). ApplynJ                    the most current DECnet-Plus ECO kits for these OpenVMSJ                    releases, for best TDF event support from DECnet-Plus.)  7                    See Section 4.2.4 and Section 4.2.1.e  '           _____________________________ 9           4.2.4  How can I drift the OpenVMS system time?-  G                    With DECdts and TCP/IP Services NTP, the system time I                    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 is.I                    used by most (all?) time servers operating on OpenVMS,MI                    typically using the support for this provided directlyn"                    within OpenVMS.                      4-12L 6  e          '                    Time and Timekeeping         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.   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 theD                    switch between DST and standard time. (Do look atE                    either not switching to daylight time, or (better)MJ                    using UTC as your time-base, if this change-over is not2                    feasible for your environment.)  7                    See Section 4.2.4 and Section 4.2.3.a  '           _____________________________ B           4.2.5  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 systemsi*                    are NTP clients, but...  D                    NTP has a heirarchy of layers, called strata. TheI                    further away from the actual NTP time source (Internet.G                    time servers are at stratum 1), the lower the strataeC                    (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 somen;                    locally-accessible external time source.e  E                    NTP at other (lower) strata both receive time fromoF                    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 anydI                    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.2.n  J                                                                       4-13               '                    Time and Timekeeping         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 similar I                    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:  ,                    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, andeJ                    the omission of the prefer keyword. Specifying a higherI                    stratum allows the node to act as a backup NTP server,aH                    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 theuF                    specified clock as the time synchronization source.  C                    With the TCP/IP Services versions prior to V5.0,oB                    the NTP management is rather more primitive. ToA                    configure the local OpenVMS system from an NTPrG                    client to an NTP server (on TCP/IP Services versionso@                    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 NTPr!                    template file:.  9                    SYS$SPECIFIC:[UCX$NTP]UCX$NTP.TEMPLATEa                      4-14s h             '                    Time and Timekeepingh        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 thehE                    SYS$EXAMPLES:DAYLIGHT_SAVINGS procedure. (Further,iA                    there is a known bug in SYS$EXAMPLES:DAYLIGHT_dG                    SAVINGS.COM in V7.3, please obtain the available ECOe                    kit.)  B                    For current TCP/IP Services and related OpenVMS-                    documentation, please see:/  7                    o  http://www.hp.com/go/openvms/doc/   D           __________________________________________________________J           4.3  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                       usec  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,eD                    the TDF must be manually configured within TCP/IPE                    Services, in addition to the OpenVMS configuratione                    of the TDF.  F                    DECnet-Plus in V7.3 and later uses the OpenVMS TDF,G                    UTC, and timezone support, and displays its timezonetI                    prompts using UTC$TIME_SETUP.COM. Earlier versions useaH                    a TDF TDF mechanism, timezone database, and automaticB                    switch-over that is internal to the DECnet-Plus  J                                                                       4-15 m  a          '                    Time and Timekeepingi        E                    package. Also on earlier versions, the TDF must berH                    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 TDFnI                    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 preprocessorM:                    declaration _VMS_V6_SOURCE is declared.  C                    DCE DTS TDF management details to be determined.   F                    In OpenVMS Alpha V6 releases (V6.1, V6.2, V6.2-1Hx,H                    etc), the TDF value is written to SYS$BASE_IMAGE.EXE.I                    With OpenVMS Alpha V7.0 and later and with OpenVMS VAX G                    V6.0 and later, SYS$SYSTEM:SYS$TIMEZONE.DAT contains.F                    the TDF. This means that OpenVMS Alpha systems willD                    need to have the TDF value reset manually-usuallyE                    within SYSTARTUP_VMS.COM-on reboots prior to V7.0.a  E                    During OpenVMS Bootstrap, the SYSINIT module readsgE                    SYS$TIMEZONE.DAT to acquire the TDF for use in thetH                    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 andEJ                    NET$CONFIGURE.COM), DTSS will reset the values to match$                    its definitions.)  J                    Prior to OpenVMS V7.3, daylight savings time switchoverH                    is handled automatically only when DCE DTS or DECnet-J                    Plus DTSS is in use. In V7.3, OpenVMS can be configuredC                    to automatically switch over to daylight savingswD                    time, and also generates an event that interested                      4-16     0          '                    Time and Timekeeping         I                    applications can use to detect the switch-over between 3                    standard time and daylight time.   F                    The manual switchover between daylight savings timeF                    and standard time is correctly accomplished via theF                    SYS$EXAMPLES:DAYLIGHT_SAVINGS.COM command procedure                    procedure.c  1                                              Notec  D                       NTP (alone) does NOT provide automatic switch-                       over.   1                                              NoteS  A                       The DST switch-over does NOT drift the time ?                       value; the switch-over applies the entireeG                       difference as a unit, as is standard and expected @                       practice. (Do look at either not switching@                       to daylight time, or (better) using UTC as@                       your time-base, if this one-hour change isA                       not feasible within your environment.) (For E                       information associated with drifting the systen 6                       time, please see Section 4.2.4.)  J                    If you switch the TDF or daylight savings time setting,I                    you will also want to restart or reconfigure any time- C                    sensitive applications (those not using the time_F                    differential factor (TDF) change event available inF                    V7.3 and later). Examples of these applications canJ                    include the need to restart the NFS client and NTP. (InH                    the case of NTP, will want to try to "drift" the timeI                    (see Section 4.2 and see Section 4.2.4), and will find I                    that the daylight savings time switch-over will exceed J                    the NTP-defined maximum threshold allowed for drifting.6                    Hence the NTP restart is required.)  '           _____________________________ <           4.3.1  Creating and Managing Timezone Definitions?  F                    One issue with the UTC implementation on OpenVMS isG                    the behaviour of C functions and other programs thatiG                    use SYS$TIMEZONE_RULE; the OpenVMS mechanism assumessF                    all control over the timezone and the daylight timeI                    switchover. This allows calculation of the time by the 6                    C library and various applications.  J                                                                       4-17 d             '                    Time and Timekeeping         H                    This can be incompatible with a system or applicationG                    that requires manual modifications to the DST or TDF1C                    settings, or that requires a local or customized5A                    timezone definition. For such a site to ensuremD                    the timekeeping is correct, the site must provideF                    procedure that sets the local time and the TDF when7                    the SYS$TIMEZONE_RULE says to do it.d  I                    If a site requires a non-standard time switch-over, as H                    in coordinating with a shift change or due to changesD                    in the local or regional timezone rules, the siteG                    will need to use the zic compiler to create a customg!                    timezone rule.u  F                    Additionally, applications may need to have specialG                    actions taken or actions queued just before the time I                    change takes effect. If the application source code isnH                    available, one of the best ways to handle this is viaH                    the TDF and time-change notification events availableG                    via the OpenVMS sys$set_system_event system service.E  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 theTF                    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)T%                    documentation set.o  >                    For related information, see Section 4.3.4.  '           _____________________________W:           4.3.2  Timezones and Time-related Logical Names?  D                    Various logical names are used to manage time andF                    timezones, and you should avoid direct modificationD                    of these logical names as the implementations areF                    subtle and quick to change. As discussed in sectionD                    Section 4.3.3, you will want to use the followingA                    command procedure to maintain the time and the                     timezone:  4                    o  SYS$MANAGER:UTC$TIME_SETUP.COM                      4-18K 1             '                    Time and Timekeeping         H                    If you want to venture into uncharted territories andF                    modify the TDF used within older releases of TCP/IPI                    Services-within releases prior V5.0-you can attempt tor;                    use the following undocumented commands:,  C                    SET TIME/DIFF=[positive or negative TDF integer]l                     GENERATE TIME  B                    to reset the value of the logical name UCX$TDF.  6                    Prior to OpenVMS 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.c  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"tZ                    $ DEFINE/SYSTEM/EXECUTIVE LISP$DAYLIGHT_SAVING_TIME_P true  ! Not 'EDT'K                    $ DEFINE/SYSTEM/EXECUTIVE LISP$TIME_ZONE 05   ! ConstantM                    $"                    $standard_time:>                    $ DEFINE/SYSTEM/EXECUTIVE MAIL$TIMEZONE ESTG                    $ DEFINE/SYSTEM/EXECUTIVE NOTES$TIMEZONE "-0500 EST"aZ                    $ DEFINE/SYSTEM/EXECUTIVE LISP$DAYLIGHT_SAVING_TIME_P false ! Not 'EST'K                    $ DEFINE/SYSTEM/EXECUTIVE LISP$TIME_ZONE 05   ! Constantc                    $H                    $ DEFINE/SYSTEM/EXECUTIVE UCX$NFS_TIME_DIFFERENTIAL -U                        'f$integer(f$element(0," ",f$logical("notes$timezone"))/-100)'t  F                    For information on modifying these timezone logical@                    names and on managing the timezone rules, see!                    Section 4.3.1.   J                                                                       4-19 a  t          '                    Time and Timekeeping       '           _____________________________,=           4.3.3  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:l  1                    SYS$MANAGER:UTC$TIME_SETUP.COM   J                    This is an OpenVMS system prior to V6.0, where there is4                    no OpenVMS TDF nor UTC available.  B                    The version of the application does not use theF                    OpenVMS TDF. This includes TCP/IP Services prior toF                    V5.0, applications using HP C built on or targetingG                    OpenVMS prior to V7.0, and systems using the DECnet- G                    Plus DTSS mechanisms prior to the release associated H                    with OpenVMS V7.3. (DCE DTS TDF management details to"                    be determined.)  A                    If you should find either of the following twoi=                    timezone-related database files located ino)                    SYS$SPECIFIC:[SYSEXE]:   ;                    o  SYS$SPECIFIC:[SYSEXE]SYS$TIMEZONE.DAT   ?                    o  SYS$SPECIFIC:[SYSEXE]SYS$TIMEZONE_SRC.DAT1  H                    These two files are in an erroneous location and must9                    be recreated in the correct directory:d  &                    SYS$COMMON:[SYSEXE]  &                    If the DCL command:  ;                    $ DIRECTORY SYS$SYSTEM:SYS$TIMEZONE*.DAT   J                    shows these files in SYS$SPECIFIC:[SYSEXE], then deleteJ                    them and use SYS$MANAGER:UTC$TIME_SETUP.COM to recreate                    them.  B                    On OpenVMS versions prior to V7.3, if the file:  5                    $ SYS$STARTUP:DTSS$UTC_STARTUP.COM   J                    is present on your system, then you may need to invoke:  ?                    $ @SYS$UPDATE:DTSS$INSTALL_TIMEZONE_RULE.COMi  C                    to recreate the timezone files correctly. Invoked?                    this command immediately after [re]executingr3                    SYS$MANAGER:UTC$TIME_SETUP.COM.)n                      4-20n n  r          '                    Time and Timekeeping         F                    If SYS$UPDATE:DTSS$INSTALL_TIMEZONE_RULE.COM is notG                    present on your system, then you may need to execute *                    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.6, Section 4.3 and Section 10.22.1.h  '           _____________________________ 9           4.3.4  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 ai:                    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  F                    The OpenVMS source files for the timezone rules are                    stored here:   ;                    SYS$COMMON:[SYS$ZONEINFO.SYSTEM.SOURCES]   J                    You'll then want to use zic to create your own timezone                    definition.  @                    The zic compiler is documented in the OpenVMSB                    Documentation Set, in the HP C Run-Time LibraryF                    Reference Manual. (Despite the name of this manual,I                    it is part of the OpenVMS documentation set and not ofh"                    the C manuals.)  :                    Once you have created the new rule, useC                    SYS$MANAGER:UTC$TIME_SETUP.COM to select the neweJ                    timezone-with V7.3 and later, this tool will notice theG                    new timezone and will offer it, on earlier releases,e?                    you may/will have to hack the tool somewhat.r  J                                                                       4-21 ,  e          '                    Time and Timekeeping         1                                              Note   A                       As mentioned in Section 4.3.2, please don't F                       modify or redefine the TZ logical name (found onE                       older configurations), or the SYS$TIMEZONE_NAME C                       logical name, or any other time- or timezone-cF                       related logical names directly yourself. Rather,F                       please use the zic compiler and/or the UTC$TIME_*                       SETUP.COM procedure.  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/  >                    For related information, see Section 4.3.1.  D           __________________________________________________________F           4.4  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 requestt  6                    %SET-E-NOTSET, error modifying time>                    -SYSTEM-E-TIMENOTSET, time service enabled;D                      enter a time service command to update the time  A                    This occurs if the time on the local system is E                    controlled by a time service software, for example H                    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 the I                    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-22     s          '                    Time and Timekeepinge        G                    You shouldn't have to change the time manually - youiH                    should be doing this through the time server - but if>                    you insist... you'll have to shutdown DTSS:  '                    $ RUN SYS$SYSTEM:NCLm                    DISABLE DTSS                     DELETE DTSS  I                    This will shutdown DTSS$CLERK. You may then change the F                    system time as usual. To restart the DTSS software,                    type   .                    $ @SYS$STARTUP:DTSS$STARTUP  E                    You will need a number of privileges to ussue thisaG                    command, and you must also be granted the NET$MANAGEC=                    identifer to shutdown and to restart DTSS.P  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 logicaleJ                    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 presentiG                    and defined sufficiently early in the OpenVMS system_:                    bootstrap sequence for it to function.)  I                    If DTSS is running and no time servers are configured,oC                    you can (and will) see the following messages ate%                    regular intervals:   K                    %%%%%%%%%%%  OPCOM   2-SEP-1999 19:41:20.29  %%%%%%%%%%% 5                    Message from user SYSTEM on UNHEDI Q                    Event: Too Few Servers Detected from: Node LOCAL:.mynode DTSS, @                            at: 1999-09-02-19:41:20.296-04:00Iinf-                            Number Detected=0,m,                            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 ituG                    and (if OPCOM is set to write to the log via via thebG                    logical names in SYLOGICALS.COM/SYLOGICALS.TEMPLATE) 4                    clean out OPERATOR.LOG regularly.  J                                                                       4-23    d          '                    Time and Timekeeping         C                    You can also simply disable the display of theses                    messages:  '                    $ run sys$system:nclcH                    block event dispatcher outbound stream local_stream -&                        global filter -?                        ((Node, DTSS), Too Few Servers Detected)m  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:ncln8                    set dtss automatic TDF change = false  J                    or alternatively, you can set the local timezone to oneG                    that does not include the automatic daylight savings $                    time change-over.  D                    OpenVMS V7.3 and later simplify time and timezone                    management.  D           __________________________________________________________F           4.5  Setting time on AlphaServer ES47, ES80, GS1280 console?  B                    To set the base system time on an member of theD                    AlphaServer ES47, AlphaServer ES80 or AlphaServerC                    GS1280 series system family, you must access the @                    Platform Management Utility (PMU). The PMU isH                    implemented within this family of related AlphaServerE                    systems, and is part of a layer providing servicesnD                    beyond those of the traditional Alpha SRM consoleH                    layer, and within a layer architecturally implementedF                    beneath the SRM console. In particular, the PMU andD                    related management components are used to provideF                    services across multiple vPars or nPars partitions.G                    In particular, the SRM obtains and manages the localeF                    system time on these systems as a delta time offsetD                    from the underlying base system time. Neither theG                    SRM console nor OpenVMS directly accesses nor alterscH                    the underlying base system time nor other information3                    maintained within the PMU layer.u                        4-24r t  g          '                    Time and Timekeepingn        A                    The PMU uses the System Management components,aI                    centrally including the Backplane Manager (MBM) moduleiD                    found in each drawer, user interface, PCI and CPUH                    management components, and the interconnections amongG                    these provided by the private system management LAN. J                    When the system has power applied and the main breakers/                    are on, the MBMs are active.   G                    The PMU offers a command line interface for a serialoI                    communications or telnet connection and allows commandcI                    and control of the MBM, and of the server. The PMU andAG                    the MBM system management components are responsible +                    for the following tasks:l  I                    o  Show the system configuration and provide the basico*                       debugging capability  C                    o  Initiate the firmware update or load the test &                       firmware version  C                    o  Power on or off, halt, or reset the system or                        partitiono  C                    o  The system partitioning and cabling functionsp  E                    o  Displays of the health of hardware environment,3G                       including such constructs as fans, power suppliesp?                       and environmental and temperature values.s  4                    o  Remote server management tasks  ?                    o  The connection to the virtual SRM console)  8                    o  Set and show the base system time.  I                    You can use the MBM commands SHOW TIME and SET TIME totI                    view and to manipulate the base system time. The deltavH                    time value for the primary MBM will be indicated, andJ                    it is this value in conjunction with the base time thatH                    is used to generate the time available to OpenVMS viaH                    the SRM console. If you issue a SET TIME=time commandH                    from OpenVMS, the delta time will change, but not theJ                    MBM base system time. If you change the MBM base systemI                    time, the calculated time available to OpenVMS via thenG                    SRM console(s) will change. (Resetting the base timeMH                    thus involves changing the base system time, and thenJ                    issuing SET TIME=time command(s) to each of the OpenVMS  J                                                                       4-25 G  c          '                    Time and Timekeeping         G                    vPars or nPars environments to adjust the respectiveFI                    delta time values.) Rebooting, resetting or issuing anm;                    MBM SET TIME will reset the system time.   E                    The time and data values stored in the primary MBM I                    and replicated in the zero or more secondary MBMs that F                    might be present within the system are coordinated.  J                    To enter the PMU from the SRM console, and to exit back                    to SRM:  ;                    MBM - (PMU, Platform Management Utility)v  8                      From SRM P00> enter {Esc} {Esc} MBMH                      CTRL/[ CTRL/[ MBM           (MBM must be uppercase)A                      MBM> connect                (to exit to SRM)p  F                    The <CTRL/[> is the escape character. Use the citedF                    key sequences to enter the PMU. You can also accessJ                    the PMU through a modem, or from a terminal or terminalF                    emulator or terminal server connected to the serverC                    management LAN. Having the server management LAN F                    bridged to an untrusted LAN can be unwise, however,E                    and with risks analogous to those of configuring a J                    traditional VAX or Alpha console serial line to an open9                    terminal server or to a dial-in modem.   -                    See the AlphaServer GS1280   D           __________________________________________________________I           4.6  UTC vs GMT vs vs UT1/UT1/UT2 TDF? What are these acronyms?   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 UTC I                    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 UT2 I                    is UT1 corrected for seasonal rotational variations inu;                    rotation due to the Earth's solar orbit.                       4-26l    s          '                    Time and Timekeepingh        B                    GMT-Greenwich Mean Time-is UT1. GMT is the timeC                    at the classic site of the since-disbanded RoyaleJ                    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, through I                    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 that0J                    celebrate daylight savings time (DST) will see periodicI                    changes to the TDF value, when the switch-over betweennB                    daylight savings time and standard time occurs.C                    The switch-over itself is entirely left to localeJ                    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.  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 sectionse4                    Section 4.3 and Section 10.22.1.)  I                    Further discussions of history and politics, the Royal0H                    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 and H                    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.htmlT  +                    o  http://nist.time.gov/r          J                                                                       4-27                         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 INSTALLt;                    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 toG(                    perform its function.  G                    The other important attribute is /SHARED. This meansMI                    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 fori$                    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 privilegesMJ                    you specify will be ignored. To have a callable routineF                    run with enhanced privileges that are not availableE                    to its caller, you must construct your routines as D                    "user-written system services" (UWSS) and installC                    the shareable image with the /PROTECT qualifier. G                    See the OpenVMS Programming Concepts Manual for moretI                    information on user-written system services. Note alsoVH                    that in many cases the need to grant privileges to an  J                                                                        5-1               0                    System Management Information        G                    image can be replaced with the use of the "Protected6I                    Subsystems" feature that grants a rights identifier toUI                    an image. See the OpenVMS Guide to System Security fore7                    information on Protected Subsystems.t  D           __________________________________________________________7           5.2  Are there any known viruses for OpenVMS?   E                    Viruses and worms are common on personal computers.B                    because the operating systems involved, such asC                    the Microsoft MS-DOS, Windows 95, Windows 98 andaC                    Windows ME variants, do not particularly protectSB                    the operating system or the file system againstD                    hostile action by programs. Microsoft Windows NT,G                    Windows 2000 and Windows XP do implement protectionsUF                    for specific configurations and do implement memoryE                    protection models, but many users of these systems.F                    choose to operate with full adminstrator access andG                    thus the available protections are entirely defeatedtF                    and entirely not relevent, and any program that canH                    activate itself or can cause the user to activate theJ                    code can subvert the operating system and take over theJ                    hardware, at which point the malicious code can do mostH                    anything it wishes, including hiding copies of itselfJ                    in other programs or in the file system, redistributingI                    itself via mail, IM, or network connections, or can beCH                    used as a zombie in staging attacks on other systems.  F                    This is less likely with multi-user systems such asD                    OpenVMS, Unix, Linux, MVS and other platforms forI                    various reasons. First, the operating system runs in a F                    privileged mode in memory that is protected againstD                    modification by normal user programs. Any programD                    cannot simply take over the hardware as it can onF                    operating systems without security and particularlyD                    without memory page protections. Secondly, multi-D                    user systems can be set up so that non-privilegedF                    programs cannot modify system programs and files onH                    disk, and this is normal for most installations. BothJ                    of these protection schemes mean that traditional viralF                    infections don't work on these OSes. Third, typicalF                    applications and configurations tend to prevent theC                    uncontrolled execution of untrusted code as part F                    of received mail messages or web access; one of the                      5-2               0                    System Management Information        C                    central vulnerabilities of the Microsoft Windows F                    platform involves its intentionally easy ability toD                    dynamically (and transparently) activate code andD                    macros that are embedded within mail messages and%                    within data files.   J                    It is possible for OpenVMS and other multi-user systemsH                    to become infected by viruses or worms, but to do so,F                    the program containing the virus must be run from aI                    user account that has amplified privileges. So long as H                    the system administrator is careful that only trustedD                    applications are run from such accounts (and thisE                    is generally the case) and so long as there are no E                    OpenVMS system security breaches (due to malicious F                    operator activity, OpenVMS errors, or errors withinD                    trusted and privileged product packages) there isG                    no of modifications to the operating system or other >                    protected files from the virus or the worm.  F                    The FAQ maintainer is aware of a few (and very old)E                    DECnet worms that have affected OpenVMS systems oncG                    DECnet networks ("WANK" was one), but is aware of noi?                    OpenVMS viruses that are loose in the field.   C                    To protect against viruses and other attempts at C                    system interference or misuse, please follow thehJ                    security recommendations in the OpenVMS Guide to SystemE                    Security. Additionally, you will want to keep yourUF                    OpenVMS ECOs current and you will want to apply allG                    mandatory ECO kits and any security MUPs for OpenVMSlE                    and OpenVMS products, and you will want to keep tovG                    OpenVMS releases with Prior Version Support (PVS) or E                    with Current Version Support. (This is obviously a I                    general system maintenance recommendation, in additionsE                    to being a good system security recommendation-newnH                    security features and capabilities are implemented inG                    more recent OpenVMS releases, for instance.) You may I                    also want to consider optional software products whichoE                    can monitor your system for intrusion or infection D                    attempts. Computer Associates (CA) offers various>                    products in this area, as to other vendors.  H                    Rocksoft offers the Veracity data integrity tool (forG                    info, send mail to demo@rocksoft.com). MD5 tools aree"                    also available.  J                                                                        5-3               0                    System Management Information        C                    Tools to scan OpenVMS file systems for Microsoft B                    Windows infections are and have been available,E                    including a commercial package from Sophos , and aiD                    port of the open source Clam Antivirus scanner atE                    http://www.clamav.net/ and with an OpenVMS port aty?                    http://fafner.dyndns.org/~alexey/clamav.zip.e  C                    These scanning tools are particularly useful foraH                    systems running Samba or Advanced Server (PATHWORKS),G                    as these servers tend to have a higher population ofiF                    files intended for Microsoft Windows systems users,D                    and as common virus and worm attacks can find andJ                    infect files on the file shares that these products canJ                    provide. These infections do not target OpenVMS itself,H                    though the OpenVMS server (and any other platform andH                    any other server capable of storing files for WindowsE                    systems) can silently host files containing commono0                    Microsoft Windows infections.  D           __________________________________________________________7           5.3  Sources of OpenVMS security information?n  J                    Where can I get information on OpenVMS system security?  6                    o  http://www.hp.com/go/openvms/doc  S                    o  http://www.blacksheepnetworks.com/security/resources/openvms/K  D           __________________________________________________________8           5.4  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-9660 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 theI                    InfoServer area, or the F11CD ECO kit. (Upgrades to V6 7                    and later are strongly recommended.)d                      5-4 e  S          0                    System Management Information        I                    By default, OpenVMS senses the specific type of media. G                    If you are working with dual-format media-media thatfG                    uses both the ODS-2 and ISO-9660 formats on the sameiG                    CD-ROM-then MOUNT will first detect and then defaultgH                    to the ODS-2 format. If you wish to override this andE                    explicitly mount the media using ISO-9660, use theF                    command:E  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_T"                    FAT qualifiers.  D                    The MOUNT /UNDEFINED_FAT qualifier is of interestC                    because ISO-9660 media can be mastered on a wide C                    variety of operating system platforms, and theseSE                    platforms do not necessarily support the semantics,I                    needed for files containing predefined record formats.oG                    The /UNDEFINED_FAT allows you to specify the defaultiG                    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 thesH                    CD-ROM media using the ISO-9660 volume structure, andG                    the use of the MOUNT /UNDEFINED_FAT qualifier causesMG                    any file whose file attributes are "undefined" to be0J                    returned with "stream" attributes with a maximum record                    length 2048.h  B                    On OpenVMS, the ISO-9660 format is (internally)G                    considered to be the ODS-3 file structure, while thesH                    High Sierra extensions to the standard are consideredA                    to be the ODS-4 file structure. The Rock RidgeiE                    extensions are not currently available on OpenVMS.7    J                                                                        5-5               0                    System Management Information        F                    For details on ODS-1 and ODS-2 file specifications,E                    see Kirby McCoy's VMS File System Internals ManualSF                    (published by Digital Press, but potentially out of#                    print), and see:e  B                    o  http://pdp-11.trailing-edge.com/www/ods1.txt  B                    o  Look for the Freeware V5.0 directory ODS2 at<                       http://www.hp.com/go/openvms/freeware/  D           __________________________________________________________;           5.5  How do I extract the contents of a PCSI kit?e  J                    A growing number of OpenVMS products are being providedH                    in PCSI (POLYCENTER Software Installation) kits whichI                    are installed using the PRODUCT INSTALL command. TheseOH                    are alternatives to or replacement for VMSINSTAL kitsG                    which were BACKUP savesets. PCSI kits are not BACKUPiI                    savesets and are structured differently from VMSINSTAL                     kits.  C                    If you want to extract product files from a PCSICG                    kit, create a directory into which the kit should be :                    expanded and use the following command:  G                    $ PRODUCT COPY prodname /SOURCE=[where-the-kit-is] -eF                        /DEST=[destination-directory] /FORMAT=REFERENCE  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 productnF                    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 theT<                    Consolidated Online Documentation CD-ROM.                      5-6 t  g          0                    System Management Information      D           __________________________________________________________9           5.6  Emergency (Conversational) System Startup?   F                    If you need to perform system management operationsD                    on an OpenVMS system and cannot access the systemB                    through normal means-the password on the SYSTEMA                    username was forgetten and no other privileged F                    usernames are available, or one or more core systemD                    product authorization key (PAK) software licensesE                    are unavailable or expired-then you must perform a 8                    conversational (emergency) bootstrap.  &                    Here are the steps:  G                    1  Halt the system. Exactly how this is done dependsMD                       on the specific system model: Depending on theI                       model, this can involve pressing the <HALT> button,tG                       entering <CTRL/P> on the console, or pressing them1                       <BREAK> key on the console.   E                    2  At the console prompt, use a console command toeD                       boot into the SYSBOOT utility. (SYSBOOT allowsH                       conversational changes to system parameters.) (TheE                       console syntax for the conversational bootstrap H                       varies by system model and by system architecture-D                       this typically involves specifying a flag withH                       the lowest bit set. See Section 14.3.5 for related,                       details.) For example:  E                       On VAX, use one of the following three commands E                       depending on the particular model of VAX systemn                       involved:e                         B/R5:1                       B/1a                       @GENBOO:                         On Alpha:   "                       b -flags 0,1  E                       If your system has a non-zero system root (such_G                       as root SYSE, shown here), you will have to use aa<                       console command such as the following:  J                                                                        5-7 g  s          0                    System Management Information                               On VAX:R                          B/E0000001#                       B/R5:E0000001rC                       @<console media procedure name varies widely>v                         On Alpha:e  "                       b -flags e,1  J                       On the IA-64 architecture systems, you can establishG                       and manage an EFI boot alias for a conversational D                       bootstrap as discussed in Section 14.3.5.1 andG                       in Section 14.3.10, or you can use VMS_LOADER.EFI I                       interactively as shown here. Of the core mechanisms G                       discussed in Section 14.3.5.1, the following uses F                       an EFI Shell command to perform a conversationalE                       bootstrap of root SYSE via the partition device G                       fsn:. There are alternative mechanisms available.m  <                       fsn:\efi\vms\vms_loader.efi -flags e,1  B                       If your Alpha system has a hardware passwordG                       (various systems support a password that preventsDH                       unauthorized access to the console), you will needF                       to know theis password and will need to enter itH                       using the LOGIN or similar command at the console.G                       If you get an "Inv Cmd" error trying to perform adG                       conversational bootstrap, and you do not have the.E                       hardware console password for the console LOGIN:F                       command, you are stuck-you will need to call forF                       hardware service for assistance in resetting theG                       hardware console password. The implementation andrH                       the syntax used for the console password mechanism2                       does vary by implementation.  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)aG                       not be started, and that OpenVMS not record theseCH                       particular parameter changes for subsequent system                       reboots:                        5-8 ,  u          0                    System Management Information        '                       SET/STARTUP OPA0: )                       SET WINDOW_SYSTEM 0t*                       SET WRITESYSPARAMS 0                       CONTINUE  G                    4  At the $ prompt, the system will now be acceptingeJ                       startup commands directly from the console. Type the1                       following two DCL commands:m                         $ SPAWN +                       $ @SYS$SYSTEM:STARTUPw  F                    5  You should now see the dollar ($) prompt of DCL.  I                       The result of these two commands will be the normal D                       system startup, but you will be left logged inF                       on the console, running under a fully privilegedI                       username. Without the use of the SPAWN command, you E                       would be logged out when the startup completes.   E                       Perform the task(s) required, such as resetting F                       the password on the SYSTEM username as describedI                       in Section 5.6.1 or registering one or more licenseBG                       product authorization keys (PAKs) as described in $                       Section 5.6.2.  G                    6  Once you log out of this session, the system willMH                       complete the startup and can be used normally. YouF                       can choose to reboot the system, but that is not                        necessary.  C                    Some system managers will suggest a method using D                    the UAFALTERNATE system parameter rather than theD                    SET/STARTUP OPA0: command shown. This approach isH                    not always available and is accordingly less commonlyH                    recommended, as there can easily be an alternate userD                    authorization database (SYS$SYSTEM:SYSUAFALT.DAT)G                    configured on the system. With a system manager that F                    has configured an alternate SYSUAFALT.DAT file, theF                    UAFALTERNATE method will fail-well, assuming you doH                    not know the password of a privileged username stored3                    within SYSUAFALT.DAT, of course.     J                                                                        5-9    a          0                    System Management Information        G                    The UAFALTERNATE system parameter is used to triggeryG                    what is sometimes known as the console backdoor. The_H                    OPA0: system console is critical to system operationsF                    and system security, and will allow access when theF                    SYSUAF system authorization database is unavailableG                    or corrupted, when core product license PAKs are notiI                    registered, expired or disabled (NOLICENSE errors), oreI                    in various other cases of system failures. All this ismH                    in addition to the role of the console in the displayD                    of certain system-critical event messages. AccessG                    to the OPA0: console has a security exposure that iscF                    equivalent to direct access to the system hardware.  C                    When LOGINOUT detects an error (such as a SYSUAFnC                    corruption, by a missing SYSUAF, missing productPF                    licenses, or other trigger), it will prevent accessF                    to the OpenVMS system from all terminals except theC                    system console. The OPA0: system console will besD                    allowed access, and the resulting process will beF                    fully privileged. Resetting the UAFALTERNATE systemI                    parameter-in the absence of an alternate SYSUAF systemPI                    authorization database-will cause the console backdoor E                    to be opened simply because LOGINOUT cannot locateyC                    SYS$SYSTEM:SYSUAFALT.DAT. When the authorizationtE                    database cannot be located, access will be granteda)                    from the console only.   C                    For further information on emergency startup and @                    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 documentationc                    set.o  D                    For information and recommendations on setting upE                    OpenVMS system security, please see the NCSC ClassaF                    C2 appendix of the Guide to OpenVMS System SecurityA                    manual, also in the OpenVMS documentation set.   J                    You can also use the conversational bootstrap techniqueG                    shown earlier (the steps until SET/STARTUP) to alter E                    various system parameters, as well. At the SYSBOOTo?                    prompt, you can enter new parameters values:                       5-10p i  n          0                    System Management Information        %                    SHOW MAXPROCESSCNT                     SET . 64h                    CONTINUEp  D                    The <.> is a shorthand notation used for the last@                    parameter examined within SYSGEN and SYSBOOT.  '           _____________________________aD           5.6.1  I've forgotten the SYSTEM password - what can I do?  D                    If you have forgotten or do not have the password@                    for the SYSTEM username, you must perform theH                    conversational bootstrap as described in Section 5.6,F                    and must enter the following commands once you have1                    reached the dollar ($) prompt:d  S                    $ SET DEFAULT SYS$SYSTEM:  ! or wherever your SYSUAF.DAT residesy-                    $ RUN SYS$SYSTEM:AUTHORIZE 6                    MODIFY SYSTEM /PASSWORD=newpassword                    EXITM  @                    You have now reset the password on the SYSTEM                    username.  '           _____________________________ B           5.6.2  My product licenses have expired - what can I do?  G                    If you have a system with no licenses for OpenVMS or I                    for OpenVMS users and thus cannot log into the OpenVMS F                    system normally, you should be able to log into theF                    console serial terminal-this is the terminal deviceE                    known as OPA0:-and perform the commands necessary.   I                    For systems that are not configured with an accessable F                    console serial terminal-as can be the case with howB                    some DECwindows workstations are configured-youF                    must log in over the network or from a local serialB                    connection. If you cannot log in over a networkE                    connection (SET HOST, telnet, etc) or from anotheraE                    local serial terminal connection, you will have torI                    halt the system and perform a conversational bootstrapsC                    as described in Section 5.6. You must then enter E                    licensing-related commands once the conversationalo?                    bootstrap has reached the dollar ($) prompt..  J                                                                       5-11 c   --    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.comw   ------------------------------  # Date: Mon, 11 Apr 2005 19:45:34 GMTi- From: hoffman@xdelta.hp.nospam (Hoff Hoffman)n< Subject: OpenVMS Frequently Asked Questions (FAQ), Part 4/111 Message-ID: <ytA6e.3487$IL.1146@news.cpqcorp.net>    Archive-name: dec-faq/vms/part4_ Posting-Frequency: quarterly Last-modified: 11 Apr 2005 Version: VMSFAQ_20050411-04.TXT                0                    System Management Information        F                    Use the following DCL command to invoke a menu thatJ                    allows you to manage and to register new or replacement                     license PAKs:  +                    $ @SYS$UPDATE:VMSLICENSEp  J                    You have now registered the license PAKs. Direct use ofH                    the DCL commands LICENSE and SHOW LICENSE and such is,                    also obviously available.  B                    If you wish to connect a serial console on yourG                    DECwindows workstation, please see Section 14.3.3.3,nD                    Section 14.3.6, Section 11.10, and Section 14.17.  H                    For information on troubleshooting DECwindows, please$                    see Section 11.5.  D           __________________________________________________________B           5.7  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 procedurest@                    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 run9D                       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 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'srE                       host system. See the command INIT/QUEUE/ON=nodeeE                       for information.) Site-specific startup commandoE                       procedures can explicitly specify the (local orlG                       even the current) node on the /ON parameter in anv3                       INIT/QUEUE/START/ON= command.                       5-12o l  e          0                    System Management Information        C                    o  Modify the node name saved in any application.I                       databases, or any local node-conditional operationshG                       present in the site-specific system startup, etc.tH                       (SEARCH for the node name, specifying all types of                       files.)a  I                    o  Use the AUTHORIZE utility command RENAME/IDENTIFIER C                       to rename the SYS$NODE_oldnodename rightslistmD                       identifier to match the new node name. (Do notE                       change the binary value of this identifier, andy4                       do not delete the identifier.)  F                       If you have erroneously deleted or duplicate theG                       identifier, you can locate existing references to H                       the binary identifier value using the Freeware DFUG                       package, and specifically the commands SEARCH/ACE_I                       and /OWNER. You must (re)create the correctly-namedsE                       identifier using the binary value that is ofteniG                       stored in various Access Control List Entry (ACE)tH                       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 them9                       old node name to the new node name.e  J                    o  If the node name is part of a disk volume label, see#                       Section 5.13.L  F                    o  Reboot the node or-if in a VMScluster-reboot theG                       whole VMScluster. (This tends to catch any errors #                       immediately.)   H                    o  Modify the IP node name. (The TCP/IP Services toolI                       is UCX$CONFIG prior to V5.0, and is TCPIP$CONFIG in I                       V5.0 and later releases.) Note that TCP/IP Services H                       ties the IP host name to the current SCSNODE valueJ                       within its database. Thus if SCSNODE is changed, theH                       IP host name reconfiguration must occur only afterI                       a system reboot. Accordingly, it is best to performnH                       the TCP/IP Services host name reconfiguration step'                       after the reboot.       J                                                                       5-13               0                    System Management Information        H                    There are likely a few other areas where the nodenameJ                    will be stored. Local procedures and data files are oneG                    such example, and various sites will have the systemtI                    name loaded in the operator control panel via the OCP_aI                    TEXT console environment variable available at the SRMt;                    prompt on some Alpha systems is another.u  F                    If the system is configured in a VMScluster and youG                    change either the SCSNODE or the SCSSYSTEMID-but notTF                    both values-then you will have to reboot the entireD                    VMScluster. (The VMScluster remembers the mappingC                    between these two values, and will assume that atD                    configuration problem has occured if a mismatchedE                    pair appears, and will refuse to let a node with aS8                    mismatched pair join the VMScluster.)  G                    To calculate the correct SCSSYSTEMID value, multiplybC                    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)   E                    This may well have missed one or two configurationaI                    tools (or more!) that are needed at your site-the nodeoJ                    name tends to get stored all over the place, in layered5                    products, and in local software...s  >                    Also see Section 15.6.3 and Section 15.6.4.  D           __________________________________________________________C           5.8  Why doesn't OpenVMS see the new memory I just added?s  F                    When adding memory to an OpenVMS system, you shouldH                    check for an existing definition of the PHYSICALPAGESC                    (OpenVMS VAX) or PHYSICAL_MEMORY (OpenVMS Alpha) F                    parameter in the SYS$SYSTEM:MODPARAMS.DAT parameterH                    database, use a text editor to reset the value in theF                    file to the new correct value as required, and then1                    perform the following command:   @                    $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT FEEDBACK  A                    This AUTOGEN command will reset various systemnF                    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.                      5-14a g  t          0                    System Management Information        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 aeH                    particular (lower) amount of system memory available.  I                    PHYSICALPAGES and PHYSICAL_MEMORY can be set to -1 (onoJ                    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.t  D           __________________________________________________________C           5.9  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 identifierscF                    present in the OpenVMS rightslist. Documentation onH                    this area is included in the _Guide to OpenVMS System$                    Security_ manual.  E                    To control the identifiers shown for a user's UIC, G                    you use AUTHORIZE. Each user has an associated groupyJ                    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, use $                    commands such as:  -                    $ RUN SYS$SYSTEM:AUTHORIZEt:                    UAF> rename/ident oldgroupid newgroupid9                    UAF> rename/ident olduserid  newuseridr  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 thisoH                    identifier is [groupnumber, 177777]. To add a missing@                    group identifier, use an asterisk as follows:  J                                                                       5-15 n  e          0                    System Management Information        @                    UAF> add/ident/value=uic=[group,*] newgroupid  I                    You may find cases where an identifier is missing fromGF                    time to time, as there are cases where the creationE                    of a UIC group name identifier might conflict withnC                    an existing username, or a user identifier mightyI                    conflict with an existing group identifier. When theseaI                    conflicts arise, the AUTHORIZE utility will not createoH                    the conflicting group and/or user identifier when the'                    username is created.s  I                    You can can add and remove user-specified identifiers,oC                    but you should avoid changing the numeric valueseG                    associated with any existing identifiers. You shouldtF                    also avoid reusing UICs or identifiers when you addG                    new users, as any existing identifiers that might benJ                    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.   D           __________________________________________________________;           5.10__What_are_the_OpenVMS_version upgrade paths?   9           5.10.1  OpenVMS Alpha Upgrade (or Update) Paths                                                             5-16                0                    System Management Information                            From V1.0,t/                        you can upgrade to V1.5.f*                    From V1.5, or V1.5-1H1,/                        you can upgrade to V6.1.S                    From V6.1, /                        you can upgrade to V6.2. &                    From V6.1, or V6.2,/                        you can upgrade to V7.0. <                    From V6.1, V6.2, V6.2-1H(1,2,3), or V7.0,/                        you can upgrade to V7.1.u                    From V6.2,sI                        you can update to V6.2-1H1, V6.2-1H2, or V6.2-1H3. J                    From V6.2, V6.2-1H(1,2,3), V7.1, V7.1-1H(1,2), or V7.2,!                        to V7.2-1.t*                    From V6.2, ... or V7.2,+                        to V7.2-1H1, to 7.3. A                    From V7.1, you can update to V7.1-1H(1,2), ... +                        to V7.2-1H1, to 7.3.dC                    From V7.3, V7.2-2, V7.2-1H1, V7.2-1, and V7.1-2,e>                        you can upgrade to V7.3-1 or to V7.3-2.                    From V7.3-1,r<                        you can upgrade to V7.3-2 or to V8.2.                    From V7.3-2, /                        you can upgrade to V8.2._  G                    Some typical OpenVMS Alpha upgrade (or update) pathsu                    are:i                                  J                                                                       5-17 o  t          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-1H3 !                    V6.2 -> V7.2-1a                    V6.2 -> V7.3:)                    V6.2-1H(1,2,3) -> V7.1 +                    V6.2-1H(1,2,3) -> V7.2-1 !                    V7.1 -> V7.1-2 !                    V7.1 -> V7.2-1 )                    V7.1-1H(1,2) -> V7.1-2,)                    V7.1-1H(1,2) -> V7.2-1 #                    V7.1-2 -> V7.3-1t#                    V7.2 -> V7.2-1H1 )                    V7.2 -> V7.3 -> V7.3-1D+                    V7.2-1 -> (V7.3, V7.3-1)a3                    V7.2-2 -> (V7.3, V7.3-1, V7.3-2) +                    V7.3 -> (V7.3-1, V7.3-2) +                    V7.3-1 -> (V7.3-2, V8.2) !                    V7.3-2 -> V8.2I  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 must9                    upgrade to OpenVMS VAX V7.1, or later.   C                    One cannot update directly to a V6.2-1Hx Limited G                    Hardware Release (LHR) from any release prior to the D                    baseline V6.2 release. The same prohibition holdsC                    for performing updates directly to V7.1-1Hx from]G                    any release prior to V7.1-this is not supported, and F                    does not produce the expected results. The LHR kitsG                    can, however, be directly booted and can be directly I                    installed, without regard to any operating system that 7                    might be present on the target disk.   F                    Users of OpenVMS Alpha V7.1-1H1 and V7.1-1H2 shouldB                    upgrade to at least V7.1-2, and preferably to a-                    supported OpenVMS release.   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 and                     upgrades.                      5-18e s             0                    System Management Information        C                    OpenVMS Alpha V7.1-2 and later use PCSI for LHRsTC                    and for OpenVMS upgrades and for all OpenVMS ECO G                    kit installations; V7.1-2 and later use upgrades and H                    not updates. VMSINSTAL OpenVMS ECO kits (updates) areG                    not used on OpenVMS Alpha V7.1-2 and later; prior to I                    V7.1-2, VMSINSTAL-based ECO (update) kits are used for                     OpenVMS.m  '           _____________________________ +           5.10.2  OpenVMS I64 Upgrade Paths   D                    OpenVMS I64 V8.2 is the first production release.D                    OpenVMS I64 V8.0 and V8.1 were intended for earlyH                    adopters of OpenVMS on Integrity servers, and are not8                    considered to be production releases.  G                    To utilize OpenVMS I64 V8.2, you must perform a full F                    installation of V8.2. No supported upgrade path (toF                    V8.2) is available from previous releases; there isI                    no upgrade from OpenVMS I64 E8.2, nor from the earlier )                    V8.1 or V8.0 releases.y  F                    Future OpenVMS I64 releases are expected to provideG                    a traditional PCSI-based upgrade path from specified E                    previous releases of OpenVMS I64, analogous to the E                    long-standing tradition of OpenVMS Alpha upgrades.   '           _____________________________ 3           5.10.3  OpenVMS VAX Release Upgrade Paths_  *                    From V5.0 through V5.4-/           3 inclusive, one can upgrade to V5.5. .                    From V5.5, V5.5-1, or V5.5-)           2HW, one can upgrade to V5.5-2.OI                    From V5.5, V5.5-1, or V5.5-2, one can upgrade to V6.0.d%                    From V5.5-2, V5.5-s0           2H4, or V6.0, one can upgrade to V6.1.?                    From V6.0, or V6.1, one can upgrade to V6.2.s?                    From V6.1, or V6.2, one can upgrade to V7.0.nE                    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).      J                                                                       5-19 n             0                    System Management Information        >                    Some typical OpenVMS VAX upgrade paths are:  E                    V5.x -> V5.5 -> V6.0 -> V6.2 -> (V7.1, V7.2, V7.3)S%                    V5.5-2HW -> V5.5-2tG                    V5.5-2, or V5.5-2H4 -> V6.1 -> (V6.2, V7.0, or V7.1)O@                    V6.1 -> V6.1 with VAXBACK ECO -> (V7.2, V7.3)                    V6.2 -> V7.2                     V6.2 -> V7.3k  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 thesI                    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.  '           _____________________________ 7           5.10.4  OpenVMS Cluster Rolling Upgrade Pathsy  J                    Rolling Upgrades require multiple system disks. RollingJ                    upgrades permit the OpenVMS Cluster to remain availableG                    while individual systems are being upgraded to a new #                    OpenVMS release.s  D                    OpenVMS Cluster rolling upgrades for both OpenVMSF                    VAX and OpenVMS Alpha may (will) have different, orI                    additional upgrade requirements, and have requirementstD                    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 Product C                    Descriptions for OpenVMS and for OpenVMS Clustero                    software:                      5-20  o  i          0                    System Management Information        9                    o  http://h18000.www1.hp.com/info/spd/   H                       OpenVMS typically uses SPD 25.01.xx, SPD 41.87.xx,'                       and SPD 82.35.xx.m  F                    for further details on the rolling upgrade, and forC                    support information. The documentation for older3E                    releases of OpenVMS VAX includes various platform- F                    specific manuals, manuals that include instructionsG                    that are specific to installing and upgrading on the                     platform.  '           _____________________________ A           5.10.5  OpenVMS Product Version and Support Informationn  E                    For information on Prior Version Support (PVS) andfC                    Mature Product Support (including information on D                    support end dates for OpenVMS and various layered)                    products), please see:   :                    o  http://www.hp.com/hps/os/os_pvs.html  ;                    o  http://www.hp.com/hps/os/os_ovms.htmla  3                    o  http://www.hp.com/go/openvms/X  I                    For information on the supported and required versions H                    of layered products, and the minimum required layeredJ                    product versions for various configurations, please seeF                    the Software Rollout Report (SWROLL), available at:  B                    o  http://h71000.www7.hp.com/openvms/os/swroll/  I                    For additional related information, see Section 2.6.1.   E                    For information on the release history of OpenVMS, E                    including information on the code names of various 3                    releases and the major features:t  G                    o  http://www.openvms.compaq.com/openvms/os/openvms- *                       release-history.html  G                    Additional release history information, as well as arH                    variety of other trivia, is available in the VAX 20th$                    anniversary book:  L                    o  http://www.openvms.compaq.com/openvms/20th/vmsbook.pdf  J                                                                       5-21 n  h          0                    System Management Information      '           _____________________________ ;           5.10.6  OpenVMS Alpha and I64 Upgrade Terminologym  C                    OpenVMS Alpha and OpenVMS I64 use the POLYCENTERoJ                    Software Product Install Utility, occasionly refered toG                    as SPIU and rather more commonly known as PCSI. PCSI I                    is a component of the OpenVMS operating system, and iseG                    available on OpenVMS VAX, OpenVMS Alpha, and OpenVMSr                    I64.   D                    The following terms apply to OpenVMS Alpha and toE                    OpenVMS I64 Upgrades and Installations using PCSI:   J                    o  UPDATE: Typically used for Limited Hardware ReleasesF                       (LHR) releases. Performed via VMSINSTAL. AppliesG                       only to the OpenVMS release that the LHR is basednJ                       on, or to an intermediate LHR. (eg: V7.1-1H2 appliesD                       only to V7.1-1H1 and to V7.1, not to any otherE                       releases.) LHRs within a series are cumulative,:H                       containing all files and features of previous LHRs)                       in the same series.   E                       VMSINSTAL-based Updates and VMSINSTAL-based ECO G                       kits are not generally used to upgrade OpenVMS onEI                       releases of OpenVMS Alpha V7.1-2 and later, nor areeH                       thse used on OpenVMS I64; only PCSI-based UpgradesH                       and Installs are used. VMSINSTAL remains availableI                       for other uses and other products; for upgrades and J                       installations of products other than OpenVMS itself.  I                    o  UPGRADE: Performed via PCSI. Upgrades can typically E                       be applied directly to a release-specific range F                       of earlier OpenVMS releases. The product releaseI                       documentation specifies the prior OpenVMS releases; A                       if your release is not one of the specified D                       releases, you will have to perform one or moreG                       additional upgrades (through intermediate OpenVMS J                       releases) to reach one of the prerequisite releases.  H                    o  INSTALL: Performed via PCSI. With an installation,D                       no existing version of the operating system isI                       assumed present, nor are any files from any copy ofdJ                       the operating system might be present preserved, andJ                       the entire contents of the target disk are destroyed0                       via a disk initialization.                      5-22U L  N          0                    System Management Information        E                    o  PRESERVE: Performed via PCSI. Otherwise similarvD                       to an installation, this option skips the diskE                       reinitialization. User files on the target diskiH                       are preserved. Any existing operating system files7                       on the target disk are clobbered.   I                    o  LHR: Limited Hardware Release. LHRs are specific toUJ                       and are targeted at new hardware configurations, andJ                       are not shipped to customers with support contracts.H                       At least one LHR kit must be specifically acquiredE                       when purchasing new hardware, new hardware thatSF                       is not (yet) supported by any mainline (non-LHR)F                       release. LHRs have an "H" in the OpenVMS version>                       string, indicating a "Hardware" release.  J                       You will not generally want to continue using an LHRI                       once a subsequent OpenVMS release is available; youtG                       will want to upgrade off the LHR at your earliest,"                       convenience.  J                    For minimum OpenVMS versions for various platforms, see                     Section 2.12.  D           __________________________________________________________J           5.11  Why do I have a negative number in the pagefile reservable                 pages?  C                    Seeing a negative number in the reservable pagesyH                    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 assumingvI                    that every process with reserved pages does not try toeH                    occupy all of the reserved pagefile space at the same                    time.  E                    To understand how the pagefile reservation processpJ                    works, think about how a traditional bank operates whenI                    accepting customer deposits and making loans. It's theiI                    same idea with the pagefile space. There is less moneyeJ                    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 thenI                    pagefile down to the problems that a "run on the bank" G                    can cause for banking customers. (Though there is no C                    deposit insurance available for pagefile users.)   J                                                                       5-23               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 pagefilewJ                    remains adequate. If either of these situations arises,;                    additional pagefile storage is required.   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,rE                    and multiple pagefiles are generally configured on G                    separate disk spindles to spread the paging I/O loadwC                    across the available disk storage. When multiple I                    pagefiles are present on recent OpenVMS versions, eachrI                    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.b  D           __________________________________________________________B           5.12  Do I have to update layered products when updating                 OpenVMS?  G                    The Software Public Rollout Reports for OpenVMS listlE                    the current and future availability of HP softwarehE                    products shipping on the OpenVMS Software Products H                    Library kits (CDROM consolidations) for OpenVMS AlphaI                    and/or OpenVMS VAX. Specifically, the required minimum ;                    versions for product support are listed.                       5-24r    m          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 ofsF                    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 processor E                    mode-typically either executive or kernel mode-may D                    or may not be compatible with more recent OpenVMS                    versions.  F                    These Software Rollout (SWROLL) Reports are updated)                    regularly. Please see:V  B                    o  http://h71000.www7.hp.com/openvms/os/swroll/  >                    For related information, see Section 2.6.1.  D           __________________________________________________________;           5.13  How do I change the volume label of a disk?n  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.w  I                    Issue the SET VOLUME/LABEL command, specifying the new.                    label.o  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 devicef  I                    Locate any references in the system startup (typicallykH                    including the disk MOUNT commands) and any DISK$labelB                    references in application files, and change the,                    references appropriately.  J                                                                       5-25    C          0                    System Management Information        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.  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.q  2                    Remount the disk appropriately.  D           __________________________________________________________4           5.14  How can I set up a shared directory?  G                    To set up a shared directory-where all files created D                    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:   D                    ADD/IDENTIFER/ATTRIBUTES=RESOURCE groupidentifier  G                    Grant the identifier to each user in the group usingi                    AUTHORIZE:.  <                    GRANT/IDENTIFIER groupidentifier username  I                    If disk quotas are in use, add an entry via SYSMAN for                     each disk:r  2                    DISKQUOTA ADD groupidentifier -<                      /PERMQUOTA=pq/OVERDRAFT=od/DEVICE=ddcu:  I                    Set the shared directory to have an ACL similar to the G                    following using the SET SECURITY (V6.0 and later) or <                    SET ACL (versions prior to V6.0) command:                      5-26d i  r          0                    System Management Information        9                    (DEFAULT_PROTECTION,S:RWED,O:RWED,G,W) @                    (IDENTIFIER=groupidentifier,OPTIONS=DEFAULT,-6                      ACCESS=READ+WRITE+EXECUTE+DELETE)1                    (IDENTIFIER=groupidentifier, - 6                      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,e@                    DEFAULT_PROTECTION, and CREATOR ACEs apply to                     directories.)  C                    The default protection mask is used to establishmG                    the default file protection mask, this mask does notoJ                    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.15  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 OpenVMS H                    Ask The Wizard area, starting particularly with topic                    (1020):  :                    o  http://www.hp.com/go/openvms/wizard/  D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the availabletB                    ATW Wizard.zip archive, please see Section 3.8.  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).   )                    Also see Section 5.34.   J                                                                       5-27               0                    System Management Information      D           __________________________________________________________F           5.16  Drivers and Configuration of New Graphics Controllers?  ?                    This section contains information on various G                    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.   '           ______________________________)           5.16.1  The ELSA GLoria Synergyn  I                    On OpenVMS Alpha V7.1-2, V7.2, and V7.2-1, acquire thegF                    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 PowerStormF                    3D10T. Please ensure you have the most current ECOsE                    for this and other graphics controllers installed;GG                    check for and install the current GRAPHICS kit. (SeesH                    Section 4.2.2 for some unexpectedly related details.)  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.   C                    An earlier kit (ALP4D20T01_071) (for V7.1, V7.1- F                    1H1, and V7.1-1H2) was once available, but has beenC                    superceded and is not recommended. Use of V7.1-2wF                    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.                      5-28b e  o          0                    System Management Information        G                    Additional information is available in topics (3419) 9                    and (5448) in the Ask The Wizard area:h  :                    o  http://www.hp.com/go/openvms/wizard/  D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the available B                    ATW Wizard.zip archive, please see Section 3.8.  I                    Support for the ELSA GLoria Synergy is integrated intoe6                    all current OpenVMS Alpha releases.  '           _____________________________ 0           5.16.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 350dJ                    graphics controllers, acquire and install the following&                    available ECO kits:  ,                    For OpenVMS Alpha V7.1-2:  =                    o  DEC-AXPVMS-VMS712_P350-V0100-4 or later   A                    o  DEC-AXPVMS-VMS712_GRAPHICS-V0300-4 or later   ,                    For OpenVMS Alpha V7.2-1:  =                    o  DEC-AXPVMS-VMS721_P350-V0100-4 or laterf  A                    o  DEC-AXPVMS-VMS721_GRAPHICS-V0300-4 or laterr  D                    Support for the PowerStorm 300 and PowerStorm 350I                    series graphics controllers is integrated into currente*                    OpenVMS Alpha releases.  '           _____________________________ 2           5.16.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.hp.com/go/openvms/wizard/  J                                                                       5-29 m  i          0                    System Management Information        D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the availableiB                    ATW Wizard.zip archive, please see Section 3.8.  '           _____________________________            5.16.4  Radeon 7500s  I                    Install the current GRAPHICS ECO kit for OpenVMS AlphaaI                    V7.2-2 or V7.3-1 for support of the Radeon 7500 seriesn4                    PCI and AGP graphics controllers.  F                    Support for this controller (without an ECO kit) isG                    first integrated into and available in OpenVMS AlphalE                    V7.3-2. (Please do always install the most currentsH                    GRAPHICS ECO kit whenever one is available, however.)  D           __________________________________________________________C           5.17  How can I acquire OpenVMS patches, fixes, and ECOs?   G                    You can acquire and download kits containing OpenVMS H                    fixes (ECOs) for various releases, as well as relatedD                    support information, via the ITRC support center:  -                    o  http://www.itrc.hp.com/   <                    o  ftp://ftp.itrc.hp.com/openvms_patches/  E                    Some systems with Internet firewalls may/will havedE                    to use passive mode FTP to access the above sites._J                    Assuming recent/current versions of the TCP/IP Services=                    package, the DCL FTP command necessary is:   F                    $ DIRECTORY/FTP/ANONYMOUS/PASSIVE ftp.itrc.hp.com::  I                    You can subscribe to an email notification list at the                     ITRC site.   H                    For a list of OpenVMS ECO kits recently released, you                    can use:c  J                    o  http://Eisner.DECUS.org/conferences/OpenVMS-patches_                        new_1.HTML  E                    Examples and ECO kit installation instructions are B                    included in the cover letter. For ECO kit emailD                    notifications, lists of available ECO kits, coverG                    letters and other associated documentation, look in:,  -                    o  http://www.itrc.hp.com/2                      5-30,    V          0                    System Management Information        <                    o  ftp://ftp.itrc.hp.com/openvms_patches/  G                    For additional information, please see Section 5.17.   F                    Do NOT attempt to install a VMSINSTAL-based OpenVMSC                    ECO kit on OpenVMS Alpha V7.1-2 and later. WhilegE                    VMSINSTAL itself remains available, it is not used G                    for OpenVMS Alpha ECO kits starting in OpenVMS AlphaFF                    V7.1-2. OpenVMS Alpha V7.1-2 and later use PCSI for$                    OpenVMS ECO kits.  I                    See Section 5.30 for information on ECO kit checksums.   D           __________________________________________________________9           5.18  How do I move the queue manager database?   B                    To move the location of the queue database, the?                    SYS$QUEUE_MANAGER.QMAN$QUEUES and SYS$QUEUE_ J                    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..  .                    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 7   ,                    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]  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 foriF                       the queue manager is "/ON=(*)", the disk must be;                       available to all nodes in the clusters  J                                                                       5-31 h  H          0                    System Management Information        3                       $ CREATE/DIR fast_disk:[qman]e  J                    5  Copy the .QMAN$QUEUES and .QMAN$JOURNAL files to the#                       new directoryU  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.19  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 process H                    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 devicepE                    supports firmware, ensure that the device firmwaretI                    is current - TQK50 controllers are known for this whenrE                    working with old firmware. (That, and the infamousdG                    "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, acquire                      and apply it.  G                    Useful tools include SDA (to see what might be goingSG                    on) and DECamds (which increase and thus potentiallysF                    fix quota-related problems). (nb: Applications with>                    quota leaks will obviously not stay fixed.)  J                    If the stuck application is BACKUP, ensure you have theI                    current BACKUP ECO and are directly following the V7.1dJ                    or (better) V7.2 or later process quota recommendationsI                    for operator BACKUP accounts. Quota details are in the 3                    OpenVMS System Manager's Manual.                       5-325    V          0                    System Management Information        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 OpenVMSiF                    VAX) that can reset the device ownership field, butE                    that is rather obviously only an interim solution-7D                    the real fix is avoiding the loss of the IRP, theG                    process quota leak, or whatever else is "jamming up" -                    this particular process...   D           __________________________________________________________2           5.20  How do I reset the error count(s)?  I                    The system reboot is the only supported approach prior F                    to V7.3-2, but a reboot is obviously undesirable inE                    various situations-there is presently no supportedeI                    mechanism to reset error counts once the error(s) havedE                    been logged on these older releases. On V7.3-2 and 6                    later, you can use the DCL command:  1                    $ SET DEVICE/RESET=ERROR_COUNTg  E                    As for an unsupported approach-and be aware of themD                    potential for triggering a system crash, you needE                    to determine the system address of the error count G                    field. For a device, this is at an offset within the E                    device's UCB structure. On VAX, the field is at an I                    offset symbolically defined as UCB$W_ERRCNT. On Alpha, H                    this field's offset is symbolically defined as UCB$L_H                    ERRCNT. The former is a word in size; the latter is a                    longword.  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 beeH                    used on the VAX and the second item should be used on.                    an Alpha. (ie. {VAX/Alpha})  J                                                                       5-33 M  a          0                    System Management Information        #                    $ ANALYZE/SYSTEMeE                    SDA>  READ SYS${SYSTEM/LOADABLE_IMAGES}:SYSDEF.STBrC                    SDA>  ! SHOW DEVICE the device with the error(s) ,                    SDA>  SHOW DEVICE <ddnc:>6                    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 or ?                    do what I prefer to do, issue the following:r  1                    SDA> SPAWN RUN SYS$SHARE:DELTA   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 ifI                    you're not careful. This second error is more commonlyt,                    known as a system crash.)  =                    If you are on a VAX, enter the command: [Wy  =                    If you are on Alpha, enter the command: [L   E                    These set the prevailing mode to word and longwordp@                    respectively. Remem- ber the UCB${W/L)_ERRCNT                    differences?   ,                    Now issue the command 1;M  3                    DELTA will respond with 00000001d  I                    You are now poised to ZAP the error count field. To dooI                    so you need to en- ter the system address and view itsuG                    contents. The format of the command to do this is ofw                    the form:  !                    IPID:hhhhhhhh/e  J                    For an IPID, use the IPID of the SWAPPER process. It is#                    always: 00010001   A                    Thus, to ZAP the error count, you would enter:   %                    00010001:hhhhhhhh/                       5-34                0                    System Management Information        F                    When you enter the / SDA will return the content ofG                    the address hhhhhhhh. This should be the error countaG                    (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 get1H                    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.   D                    00010001:80D9C6C8/0001   ! output on VAX, 1 error  J                    00010001:80D9C6C8/00000001   ! output on Alpha, 1 error  I                    You can now ZAP the error count by entering a zero ando9                    typing a carriage return. For example:   N                    00010001:80D9C6C8/0001 0<return>   ! output on VAX. 1 error  T                    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.21  How do I find out if the tape drive supports compression?a  I                    For various SCSI-based MK-class magnetic tape devices:   E                    $ Devdepend2 = F$GETDVI("$n$MKcxxx:","DEVDEPEND2") *                    $ Comp_sup = %X00200000*                    $ Comp_ena = %X00400000D                    $ IF (Devdepend2.AND.Comp_sup).EQ.Comp_sup THEN -?                        WRITE SYS$OUTPUT "Compression supported"tD                    $ IF (Devdepend2.AND.Comp_ena).EQ.Comp_ena THEN -=                        WRITE SYS$OUTPUT "Compression enabled"   D           __________________________________________________________G           5.22  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 compatible F                    across OpenVMS VAX and OpenVMS Alpha systems. (ThisC                    compatibility is a a basic requirement of mixed- E                    version OpenVMS Cluster configurations and OpenVMS H                    upgrades-for specific support information, please see  J                                                                       5-35               0                    System Management Information        H                    the OpenVMS Cluster rolling upgrade and mixed-versionE                    requirements.) That said, it's the contents of the G                    SYSUAF and RIGHTSLIST files that will make this more                     interesting.   G                    The same basic steps necessary for moving RIGHTSLISTaF                    and SYSUAF files to another node are rather similarE                    to the steps involved in merging these files in antJ                    OpenVMS Cluster-see the appendix of the OpenVMS ClusterI                    documentation for details of merging files. (You mightSJ                    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.)t  "                    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.s  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 OpenVMSaD                       Alpha V6.2 upgrade. This file is maintained in1                       parallel with NETPROXY.DAT.n  J                    o  the RIGHTSLIST identifier values and UIC values thatG                       end up scattered around the target system must bepJ                       rationalized with the contents of the new RIGHTSLIST'                       and SYSUAF files.   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 thecH                    same function. In most cases, they will not. As such,E                    you will have to find and chance all references tovF                    the identifier value(s) (or name(s)) to resolve the                    "collision".                       5-36s e  a          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 of F                    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 fortE                    the identifier displayed, and no particular accessoE                    will be granted. And any DCL commands or such thatgH                    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 OpenVMS C                    Cluster and that can be involved when relocatingsF                    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 theo'                    Ask The Wizard area:   :                    o  http://www.hp.com/go/openvms/wizard/  D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the available B                    ATW Wizard.zip archive, please see Section 3.8.    J                                                                       5-37 d  o          0                    System Management Information      D           __________________________________________________________9           5.23  How do I delete (timeout) idle processes?   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 providesu?                    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.aI                    Also available is the XLNperformance system managementl,                    utility, from XLNsystems.  A                    A related package (for DECwindows sessions) iss                    xtermlock.s  D                    If the forgetful users are in an application menuG                    environment, the menu can potentially be extended to +                    provide this capability.i  D           __________________________________________________________C           5.24  Do I need a PAK for the DECevent (HP Analyze) tool?c  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 basicmE                    bits-to-text translation of the error log does notOE                    require a license PAK. Ignore the prompt, in otherrI                    words. (The PAK should be available to you if you haveeH                    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 and &                    downloads: Analyze)  =                    o  http://www.compaq.com/support/svctools/y  D                    Also see the tool that is available on V7.3-2 and                    later.   &                    $ ANALYZE/ERROR/ELV                      5-38l t             0                    System Management Information      D           __________________________________________________________>           5.25  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-aJ                    new ANSI X3.27-1987 magnetic tape label standard. PriorI                    to the ANSI X3.27-1987 standard, the date field in thecH                    ANSI HDR1 record permits dates only as far as the endI                    of Year 1999. With ANSI X3.27-1987, dates through YeariH                    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 andaI                    later dates are involved-the DCL INITIALIZE command is G                    known to encounter access violation (ACCVIO) errors.   G                    The available solutions include upgrades, or settingAH                    the date back. Direct initialization of the tape withG                    the new headers (via $qio) is also clearly possible,aJ                    though the limitation within the old MTAACP.EXE magtape=                    ACP image is not nearly so easy to bypass.s  D           __________________________________________________________7           5.26  How do I recover from INSVIRMEM errors?e  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 eachc                    process.   F                    Further limiting the amount of address space is theE                    size of system space (S0 and S1 space). On OpenVMSrF                    Alpha versions prior to V7.0 and on all OpenVMS VAXF                    releases, VIRTUALPAGECNT and MAXPROCESSCNT togetherG                    determine the size of the page table data structuresoD                    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-pagedEH                    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 data H                    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-39 L  e          0                    System Management Information        G                    64-bit space, thus freeing up room in non-paged pool H                    and in S0 and S1 space (where non-paged pool resides)E                    while also permitting much larger data structures.S  D           __________________________________________________________J           5.27  How can I prevent a serial terminal line from initiating a                 login?  ;                    In SYSTARTUP_VMS.COM, issue the command:i  =                    $ SET TERMINAL/NOTYPEAHEAD/PERMANENT ddcu:e  F                    This will prevent any unsolicited terminal input onE                    ddcu:, and this unsolicited input is what triggerssI                    JOB_CONTROL to start up LOGINOUT on the terminal. Once E                    LOGINOUT starts up on the serial line, you can seeoH                    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 terminal                     line.  D           __________________________________________________________>           5.28  How does PCSI use the image BUILD_IDENT field?  E                    The (undocumented) build ident field in an OpenVMSrF                    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)pG                    and was originally introduced to provide informationSJ                    for use by VMSINSTAL patch kits to determine whether an3                    image should be replaced or not.   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 (aFF                    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 andTI                    resolution. When a product is installed, PCSI modifiesdH                    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. (Only66                    images have this field, obviously.)                      5-40  t             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 ten H                       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 kit H                       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?l  I                    For an image that has been built as part of an OpenVMSCE                    Engineering system build, you will generally see alH                    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.0  F                    During the installation of V7.2-1, PCSI will modifyC                    the image header to have a build ident string ofcC                    "X6TE-0050120000". During installation of an ECO E                    kit containing this image with a generation numberhF                    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.t              J                                                                       5-41 h             0                    System Management Information      D           __________________________________________________________H           5.29  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,F                     respectively.  I                    To see which OpenVMS Alpha ECO kits have been applied,aF                    look in VMSINSTAL.HISTORY on OpenVMS Alpha prior toG                    V7.1-2, and use PRODUCT SHOW PRODUCT/FULL on OpenVMS1*                    Alpha V7.1-2 and later.  G                    On OpenVMS VAX, you can use PRODUCT SHOW PRODUCT andrH                    (for software that is installed via VMSINSTAL on V7.33                    and later) in VMSINSTAL.HISTORY.S  F                    For products installed on OpenVMS VAX prior to V7.3I                    using VMSINSTAL, there is no reliable way to determinesD                    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 DIRECTORYBH                    SYS$HELP:*.RELEASE_NOTES. Again, this approach is NOTI                    reliable: some kits do not provide release notes, some:G                    system managers will install only the release notes, F                    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/VERSIONr  7                    o  TCP/IP TCPIP SHOW VERSION command                       5-42  t  l          0                    System Management Information      D           __________________________________________________________C           5.30  What file checksum tools are available for OpenVMS?l  H                    The undocumented (prior to V8.2) DCL command CHECKSUMJ                    is the usual means, and provides a rather simple-mindedF                    checksum suitable to detect basic file corruptions.G                    Starting with V8.2, additional algorithms beyond then4                    classic XOR scheme are available.  E                    One of the most common schemes beyond the CHECKSUM G                    XOR scheme is MD5, and information and a source codecD                    example are available via the MD5 RFC. As of thisH                    writing, pre-built versions of MD5 are expected to beH                    made available at or via the OpenVMS Freeware websiteI                    ( http://www.hp.com/go/openvms/freeware/ ), and MD5 is G                    expected to be made available on an OpenVMS Freeware J                    release after V7.0. Also see the CHECKSUM/ALGORITHM=MD55                    command on OpenVMS V8.2 and later.a  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_axpexe_2                    $ SHOW SYMBOL CHECKSUM$CHECKSUM  H                    See Section 5.17 for information on acquiring OpenVMS$                    ECO (patch) kits.  D           __________________________________________________________C           5.31  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.32  How to determine current disk fragmentation level?  ;                    The HP OpenVMS Disk File Optimizer (DFO) C                    defragmentation package provides a fragmentation G                    monitoring tool, and a DFO product authorization key H                    (PAK) is not required for the fragmentation reporting                    tool:  -                    $ DEFRAG SHOW/VOLUME ddcu:_  J                                                                       5-43 e  a          0                    System Management Information        E                    The DFU tool available on the OpenVMS Freeware canE?                    generate a report on the disk fragmentation:a  $                    DFU> REPORT ddcu:  D           __________________________________________________________H           5.33  SYSBOOT-I-FILENOTLOC, Unable to locate SYS$CPU_ROUTINES?  G                    A message at the OpenVMS Alpha bootstrap such as thei                    following:   :                    %SYSBOOT-I-FILENOTLOC, Unable to locate.                      SYS$CPU_ROUTINES_1C02.EXE=                    %SYSBOOT-E-LDFAIL, failed to load execlet,a&                      status = 00000910  F                    indicates that the particular OpenVMS Alpha releaseG                    does not contain support for the target platform. In2H                    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 bootstrapnI                    status values can often be decoded using either of the=(                    following techniques:                      $ exit %x910l5                    %SYSTEM-W-NOSUCHFILE, no such file                     $  )                    $ x = f$message(%x910)S"                    $ show symbol x=                      X = "%SYSTEM-W-NOSUCHFILE, no such file"                     $  -                    Also see Section 14.4.4.1.                               5-44                0                    System Management Information      D           __________________________________________________________E           5.34  How can I customize the DCPS device control for a newA                 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,uF                       DCPS$DEVCTL.TLB. (For instance, you can probablyA                       extract and use the HP LaserJet 4000 seriesaG                       definitions for the HP LaserJet 4050 series. EachqC                       printer will vary, please consult the printer D                       documentation for specifics and requirements.)  =                    o  rename each extracted setup module to a $                       corresponding:  )                       LPS$$UNRECOGNIZED_*g  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 -r>                           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.TLBl  E                    o  Supply DCPS_HP4050_LIB as the library parameterlA                       in the queue startup for this printer, thissB                       is the P3 parameter to the command procedure;                       SYS$STARTUP:DCPS$EXECUTION_QUEUE.COM.b  C                    o  The HP4050_DEVCTL library may/will need to befG                       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 DCPS ?                       directly supports the particular printer.   J                                                                       5-45               0                    System Management Information        D                    o  To customize the processing of file extensionsG                       within DCPS (to enable or disable graybar output, F                       for instance), use the information available in:  K                       SYS$LIBRARY:DCPS$FILE_EXTENSION_DATA_TYPE.DAT_DEFAULT   4                    to create your own site-specific:  @                    SYS$LIBRARY:DCPS$FILE_EXTENSION_DATA_TYPE.DAT  )                    Also see Section 5.15.o  D           __________________________________________________________D           5.35  Why do $GETDEV MOUNTCNT and SHOW DEVICE mount counts                 differ?_  E                    MOUNTCNT returns the local mount count, while SHOW ?                    DEVICE returns the cluster-wide mount count.e  D           __________________________________________________________@           5.36  What software is needed for Postscript printers?  D                    The NorthLake PrintKit (www.nls.com) and DECprintF                    Supervisor (DCPS) are common choices for support of2                    Postscript printers on OpenVMS.  )                    o  http://www.nls.com/h  H                    o  http://www.openvms.compaq.com/openvms/Print/print_#                       sw_prods.htmla  A                    You may also require the installation of an IPr#                    transport stack.   E                    Also please see Section 15.2.2 and Section 15.2.3.   D           __________________________________________________________A           5.37  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 agG                    substantial quantity of disk space. While removal ishF                    clearly theoretically possible, it is not currently                    implemented.n                      5-46h (             0                    System Management Information        G                    The following is the supported mechanism to remove ae"                    PCSI patch kit.  H                    1  Execute a PRODUCT SHOW PRODUCT product-name. /FULLJ                       command. The "maintenance" column (132 column width)H                       shows the patches that have been installed. Keep a+                       copy of this listing.   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 product 3                       back to "original" condition.l  I                    4  Re-install all the patches in the list from step 1, H                       except those patches which you have determined you"                       do not want.  E                    The above information also applies to PCSI PARTIALe                    kits.  D           __________________________________________________________H           5.38  SYSINIT-E, error mounting system device, status=0072832C  B                    This message can arise during an OpenVMS system                    bootstrap...u  V                    %MOUNT-F-DIFVOLMNT, different volume already mounted on this device  C                    For details and further information, use the DCL                     command:a  2                    $ HELP/MESSAGE /STATUS=%X72832C  D           __________________________________________________________/           5.39  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.d  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.)   J                                                                       5-47               0                    System Management Information        D                    The PAK version indicates the most recent product<                    version that is permitted by the license.  G                    Having multiple license PAKs registered (and active) I                    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-wH                    disk cluster, with a consistent set of /INCLUDE lists@                    specified across each of the duplicated PAKs.  F                    Additionally, you could have an invalid LMF$LICENSEC                    logical name defined. (If no LMF$LICENSE logicalbG                    name is defined, the standard license database namede<                    SYS$SYSTEM:LMF$LICENSE.LDB will be used.)  C                    You can display license failures by defining the0*                    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 name0F                    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. OnceOI                    you figure out which license has failed, you will want_1                    to deassign this logical name.y  1                                              Note   G                       That there are no license check failures does not G                       indicate that the particular product or operation D                       or use is permissible per applicable licensing?                       agreements. Please consult the applicable D                       agreement(s) for licensing-related information'                       and requirements.o                      5-48                0                    System Management Information        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.6 up through the usehF                    of the AUTHORIZE command. In place of the AUTHORIZEI                    command, use the console to register the license PAKs.AJ                    Also see Section 12.4 for licensing and troubleshooting                    information.n  E                    For information on licensing and on the numbers ofCJ                    license units required for various products and variousH                    platforms, the License Unit Requirements Table (LURT)#                    is available at:e  C                    o  http://www.compaq.com/products/software/info/h  D           __________________________________________________________4           5.40  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]                     $ RUN SYSVERa                    REPLACE V9.9                     WRITE                    $ EXITi  *                    On OpenVMS VAX systems:  5                    $ set default SYS$COMMON:[SYS$LDR] 8                    $ copy SYS.EXE SYS.EXE_IN-CASE-I-FAIL"                    $ patch SYS.EXE1                    define sys$gq_version=800044b8 !                    set mode ascii *                    !examine sys$gq_version,                    !examine sys$gq_version+44                    deposit sys$gq_version   = "V9.9"4                    deposit sys$gq_version+4 = "    "                    update                     exit                     $ Exit   :                    Then reboot the system at your leisure.  J                                                                       5-49               0                    System Management Information      D           __________________________________________________________E           5.41  How to prevent users from choosing obvious passwords?a  G                    To prevent users from selecting obvious passwords on F                    OpenVMS, you will want to use the reserved passwordI                    (password screening) mechanism. Effectively, you merge D                    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 passwordcG                    database (VMS$PASSWORD_DICTIONARY.DATA), and detailsfD                    of how to merge your list of prohibited passwordsG                    into the database, please see the associated chapteraE                    in the OpenVMS security manual. For details of thedC                    password expiration mechanism, see the AUTHORIZEe1                    command qualifier /PWDEXPIRED.   I                    You can also implement a site-specific password filter C                    with the information provided in the back of the D                    OpenVMS Programming Concepts manual. The passwordG                    filter permits you to establish particular and site-oF                    specific password requirements. For details, pleaseC                    see the system parameter LOAD_PWD_POLICY and thenG                    programming concepts manual, and see the examples indE                    SYS$EXAMPLES:. (Examples and documentation on V7.3rE                    and later reflect both platforms, the examples areCF                    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 "dictionaryJ                    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, G                    a "dictionary attack" also has the unfortunate side-oI                    effect of exposing the password to the user-while thiswF                    is clearly the goal of a system cracker, authorizedH                    privileged and non-privileged system users should not                      5-50      --    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.comt   ------------------------------  # Date: Mon, 11 Apr 2005 19:47:59 GMTn# From: hoff@hp.nospam (Hoff Hoffman) < Subject: OpenVMS Frequently Asked Questions (FAQ), Part 5/111 Message-ID: <PvA6e.3488$IL.2302@news.cpqcorp.net>i   Archive-name: dec-faq/vms/part5  Posting-Frequency: quarterly Last-modified: 11 Apr 2005 Version: VMSFAQ_20050411-05.TXTo    h          0                    System Management Information        G                    know nor have access to the (cleartext) passwords oft                    other users.c  D                    Accordingly, OpenVMS does not store the cleartestE                    password. Further, OpenVMS uses a password hashingSJ                    algorithm, not an encryption algorithm. This means thatJ                    storage of a cleartext password is deliberated avoided,I                    and the cleartext value is deliberately very difficultlF                    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 resultso<                    of the password hash unique to each user.  I                    Regardless of the use of a password hashing scheme, ifxJ                    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.   E                    If you should require a user to verify a password, F                    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 hashedOE                    value (using a call to $hash_password) against therH                    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 donG                    not maintain the cleartext password in memory longer H                    than required. (Use of sys$acm on V7.3-1 and later is                     recommended.)  A                    Kerberos authentication (client and server) is F                    available on OpenVMS V7.3 and later. Integration ofG                    Kerberos support into various Compaq and into third- .                    party products is expected.  A                    External authentication is available in V7.3-1_D                    and later, with support for user-written external6                    authentication in V7.3-2 and later.  C                    If you are simply looking for OpenVMS access and D                    the SYSTEM and all other privileged passwords areI                    forgotten or otherwise unavailable, please see section D                    Section 5.6 and/or the OpenVMS documentation set.  H                    Also please see the NCSC C2 guidelines in the OpenVMS#                    security manual.X  J                                                                       5-51    2          0                    System Management Information      D           __________________________________________________________?           5.42__Please_help_me_with_the OpenVMS BACKUP utility?s  8           5.42.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 toeJ                    ensure BACKUP can perform an incrementation restorationC                    of the files. In particular, if a directory filetI                    modification date changes, all files underneath it areoI                    included in the BACKUP, in order to permit incrementalPC                    restoration should a directory file get renamed._  '           _____________________________ J           5.42.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 should G                    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, tosD                    test the procedures. This testing was how OpenVMSC                    Engineering found out about the problem that wastB                    latent with the old BACKUP selection scheme-theB                    old incremental BACKUP scheme would have missedG                    restoring any files under a renamed directory. Hence F                    the change to the selection mechanisms mentioned in"                    Section 5.42.1.  '           _____________________________ >           5.42.1.2  Can you get the old BACKUP behaviour back?  I                    Yes, please see the /NOINCREMENTAL qualifier available D                    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 around-1                    incremental disk restorations.a                            5-52                0                    System Management Information      '           _____________________________e>           5.42.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.   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.g  '           _____________________________ 8           5.42.3  Why is BACKUP not working as expected?  C                    First, please take the time to review the BACKUPaE                    documentation, and particularly the BACKUP command_F                    examples. Then please download and install the mostI                    current BACKUP eco kit. Finally, please please set theiJ                    process quotas per the System Management documentation.B                    These steps tend to resolve most problems seen.  A                    BACKUP has a very complex interface, and thereaC                    are numerous command examples and extensive userdH                    documentation available. For a simpler user interfaceC                    for BACKUP, please see the documentation for thep'                    BACKUP$MANAGER tool.t  E                    As for recent BACKUP changes, oddities, bugs, etc:e  I                    o  A change made in OpenVMS V6.2 WILL cause more fileseE                       to be included into a file-based BACKUP saveset E                       using /SINCE=BACKUP as all files underneath anytE                       directory with a sufficiently recent (selected)fG                       date will be included in the saveset. This change.F                       was deliberate and intentional, and was mandatedE                       by the need to provide a functional incrementaln"                       restoration.  E                       Without the inclusion of these apparently-extra G                       files, an incremental saveset can NOT be reliably                        restored.   J                                                                       5-53 i  e          0                    System Management Information        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?)i*                       the BACKUP ECO kits.  >                    When working with BACKUP, you will want to:  E                    o  Ensure you have your process quotas set per theeF                       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.h  G                    o  Learn about the /NOINCREMENTAL (new) and /NOALIAS E                       (V6.2 and later) command qualifiers. The formeriH                       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 selected,9                       and thus included into the saveset.t  F                       Learn what /IGNORE=INTERLOCK means. This commandG                       probably does not provide what you think it does-oG                       those file system interlocks that this command iscH                       ignoring were implemented for a reason, after all.G                       Ignoring these interlocks can lead to missed data H                       and potentially to corruptions to individual filesH                       stored within the output saveset, corruptions thatE                       may or may not be reported. For details on this F                       BACKUP command qualifier, please see the Ask The*                       Wizard topic (2467).  =                    When working with the BACKUP callable API:S  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 repairednI                       via a BACKUP ECO kit. Do NOT build your applicationa                      5-54                0                    System Management Information        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.   '           _____________________________n8           5.42.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.h  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 usings                    the tool:  >                    $ @RESET_BACKUP_SAVESET_FILE_ATTRIBUTES.COM  E                    This tool is available on the OpenVMS Freeware (inmG                    the [000TOOLS] directory). The Freeware is availablesF                    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, 4                    this approach is not recommended.  I                    Also see the "SITE VMS", /FDL, and various other file- J                    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 ormF                    ascii FTP transfer modes) are notorious for causingG                    RMS file corruptions and particularly BACKUP saveseteD                    corruptions. You can sometimes help encourage theG                    browser to select the correct FTP transfer type codei!                    (via RFC1738):n  A                    o  ftp://host/urlname.ext;type=i ! request ftp +                       image/binary transfere  J                                                                       5-55 o  e          0                    System Management Information        A                    o  ftp://host/urlname.ext;type=a ! request ftp )                       ascii/text transferi  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 aaI                    customization menu available in most web browsers. YouaH                    can select that the specific file extentions involvedJ                    use the FTP binary transfer mode, which will reduce the.                    number of corruptions seen.  '           _____________________________ C           5.42.5  How do I write a BACKUP saveset to a remote tape?B  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:_                      RECORD 8                            FORMAT                  fixed7                            SIZE                    8192   1                    Then create BACKUP_SERVER.COM:e                      $ !R                    $ ! BACKUP_SERVER.COM - provide remote tape service for BACKUP.                    $ !                    $ set noon '                    $ set rms/network=16_,                    $ allocate mka500 tapedevE                    $ mount/nounload/over:id/block=8192/assist tapedev C                    $ convert/fdl=SAVE-SET sys$net tapedev:save-set.a,                    $ dismount/unload tapedev                    $ stop/id=0  G                    On the node where you want to do the backup, use thee                    DCL command:r                      $ backup - $                        srcfilespec -K                        node"user pwd"::"task=backup_server"/block=8192/save                           5-56                0                    System Management Information        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 and_E                    the magtape ACP, BACKUP won't see the media switchRH                    and will split an XOR group across the reel boundary.E                    BACKUP might well be willing to read such a multi-OF                    reel or multi-cartridge saveset (directly, not overE                    the net) as the XOR blocks are effectively ignoredaI                    until and unless needed for error recovery operations.aI                    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 includep+                    variable length records.   '           _____________________________n=           5.42.6  How to perform a DoD security disk erasure?o  ?                    Sometimes refered to as disk, tape, or media G                    declassification, as formatting, as pattern erasure,eC                    or occasionally by the generic reference of data G                    remanence. Various references to the US Deparment ofLJ                    Defence (DoD) or NCSC "Rainbow Books" documentation are-                    also seen in this context.   G                    While this erasure task might initially appear quite G                    easy, basic characteristics of the storage media and F                    of the device error recovery and bad block handlingH                    can make this effort far more difficult than it might$                    initially appear.  F                    Obviously, data security and sensitivity, the costsB                    of exposure, applicable legal or administrativeB                    requirements (DoD, HIPPA or otherwise), and theG                    intrinsic value of the data involved are all centraleH                    factors in this discussion and in the decision of theI                    appropriate resolution, as is the value of the storage %                    hardware involved.s  C                    With data of greater value or with data exposureeF                    (sometimes far) more costly than the residual valueI                    of the disk storage involved, the physical destructioneB                    of the platters may well be the most expedient,  J                                                                       5-57 R  G          0                    System Management Information        G                    economical, and appropriate approach. The unintendedbI                    exposure of a bad block containing customer healthcare F                    data or of credit card numbers can quite be costly,G                    of course, both in terms of the direct loss, and the D                    longer-term and indirect costs of such exposures.  F                    Other potential options include the Freeware RZDISKE                    package, the OpenVMS INITIALIZE/ERASE command (andhE                    potentially in conjunction with the $erapat systemXC                    service) and OpenVMS Ask The Wizard (ATW) topics0G                    including (841), (3926), (4286), (4598), and (7320). D                    For additional information on sys$erapat, see theF                    OpenVMS Programming Concepts manual and the OpenVMSH                    VAX examples module SYS$EXAMPLES:DOD_ERAPAT.MAR. SomeH                    disk controllers and even a few disks contain supportG                    for data erasure. Some DSSI Disk ISEs, for instance.   D                    For the prevention of casual disk data exposures,C                    a generic INITIALIZE/ERASE operation is probably ?                    sufficient. This is not completely reliable, E                    particularly if the data is valuable, or if legal, A                    administrative or contractual restrictions are E                    stringent-there may well be revectored blocks that G                    are not overwritten or not completely overwritten by I                    this erasure, as discussed above, and these blocks can H                    obviously contain at least part of most any data thatI                    was stored on the disk - but this basic disk overwrite H                    operation is likely sufficient to prevent the typical+                    information disclosures.i  C                    You will want to consult with your site security I                    officer, your corporate security or legal office, with_E                    HP Services or your prefered service organization,VE                    or with a firm that specializes in erasure or data I                    declassification tasks. HP Services does traditionally @                    offer a secure disk declassification service.                                    5-58_ _  _          0                    System Management Information      '           _____________________________r9           5.42.7  How to enable telnet virtual terminals?   D                    To enable virtual terminal support for telnet andA                    rlogin devices, add the following logical namew3                    definitions into SYLOGICALS.COM:v  B                    $ DEFINE/SYSTEM/EXECUTIVE TCPIP$RLOGIN_VTA TRUEB                    $ DEFINE/SYSTEM/EXECUTIVE TCPIP$TELNET_VTA TRUE  I                    See SYS$STARTUP:SYLOGICALS.TEMPLATE for details on thes6                    typical contents of SYLOGICALS.COM.  I                    In SYSTARTUP_VMS.COM, ensure that a command similar too,                    the following is invoked:  a                    $ SYSMAN IO CONNECT VTA0/NOADAPTER/DRIVER=SYS$LOADABLE_IMAGES:SYS$TTDRIVER.EXE   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:   )                    TTY_DEFCHAR2 = %X20000e  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  '           _____________________________T;           5.42.7.1  Volume Shadowing MiniCopy vs MiniMerge?   F                    MiniMerge support has been available for many yearsG                    with OpenVMS host-based volume shadowing, so long asaH                    you had MSCP controllers (eg: HSC, HSJ, or HSD) whichH                    supported the Volume Shadowing Assist known as "Write$                    History Logging".  B                    If you are interested in mini-merge and similarE                    technologies, please see the Fibre Channel webpage 7                    and the information available there:   B                    o  http://www.openvms.compaq.com/openvms/fibre/  J                                                                       5-59 x  t          0                    System Management Information        C                    Mini-Merge support was originally intended to be F                    controller-based and was expected with HSG80 seriesJ                    storage controllers and was expected to require ACS 8.7,                    and OpenVMS Alpha V7.3-1.  D                    Host-based Mini-Merge (HBMM) is now available forE                    specific OpenVMS releases via a shadowing ECO kit,fF                    and is also present in OpenVMS V8.2 and later. HBMMI                    applies to the HSG80 series and-like host-based volume I                    shadowing-to most other (all other?) supported storage_                    devices._  E                    The following sections describe both Mini-Copy and G                    Mini-Merge, and can provide a basis for discussions.   '           _____________________________l            5.42.7.1.1  Mini-Copy?  I                    A Shadowing Full Copy occurs when you add a disk to an G                    existing shadowset using a MOUNT command; the entire E                    contents of the disk are effectively copied to thesF                    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- F                    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)lI                    that you're planning to remove a disk from a shadowsetgB                    but re-add it later, OpenVMS will keep a bitmapE                    tracking what areas of the disk have been modifiedhH                    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-nG                    map indicates are now out-of-date. OpenVMS does this H                    with a read source / write target algorithm, which isG                    much faster than the shenanigans the Full Copy does,DI                    so even if all of the disk has changed, a Mini-Copy is +                    faster than a Full Copy.                       5-60C E  d          0                    System Management Information      '           _____________________________ !           5.42.7.1.2  Mini-Merge?d  F                    A Shadowing Merge is initiated when an OpenVMS nodeI                    in the cluster (which had a shadowset mounted) crashes H                    or otherwise leaves unexpectedly, without dismountingI                    the shadowset first. In this case, OpenVMS must ensure I                    that the data is identical, since Shadowing guarantees D                    that the data on the disks in a shadowset will beJ                    identical. In a regular Merge operation, Shadowing usesJ                    an algorithm similar to the Full Copy algorithm (exceptE                    that it can choose either of the members' contents H                    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 theiH                    area containing the read data, then allow the read to                    occur.   B                    A Merge can be very time-consuming and very I/OH                    intensive. If a node crashes, the surviving nodes canF                    query to determine what exact areas of the disk theF                    departed node was writing to just before the crash,H                    and thus Shadowing only needs to merge just those fewF                    areas, so this tends to take seconds, as opposed toI                    potentially requiring many minutes or even hours for ae&                    regular full Merge.  D           __________________________________________________________;           5.43  Please explain DELETE/ERASE and File Locks?   D                    DELETE/ERASE holds the file lock and also holds aG                    lock on the parent directory for the duration of the F                    erasure. This locking can obviously cause an accessC                    conflict on either the file or on the directory-_E                    it might well pay to rename files into a temporarynF                    directory location before issuing the DELETE/ERASE,G                    particularly for large files and/or for systems with D                    multiple overwrite erase patterns in use; for anyH                    systems where the DELETE/ERASE erasure operation will                     take a while.        J                                                                       5-61               0                    System Management Information      D           __________________________________________________________'           5.44  Managing File Versions?r  A                    Some applications will automatically roll file E                    version numbers over, and some will require manual J                    intervention. Some will continue to operate without theI                    ability to update the version, and some will be unable I                    to continue. Some sites will specifically (attempt to)sH                    create a file with a version of ;32767 to prevent the5                    creation of additional files, too.   D                    To monitor and resolve file versions, you can use&                    commands including:  6                    $ SET FILE/VERSION_LIMIT=n filename>                    $ SET DIRECTORY/VERSION_LIMIT=n [directory]  E                    And you can also monitor file version numbers, andoI                    can report problems with ever-increasing file versionssG                    to the organization(s) supporting the application(s)wH                    generating files with ever-increasing version numbersA                    for details on potential problems, and for anyuG                    recommendations on resetting the version numbers forsE                    the particular product or package. If required, ofs                    course.  F                    The following pair of DCL commands-though obviouslyC                    subject to timing windows- can be used to renameeG                    all the versions of a file back down to a contiguousr6                    sequence of versions starting at 1:  4                    $ RENAME file.typ;*   RENAME.TMP;2                    $ RENAME RENAME.TMP;* file.typ;  H                    The key to the success of this RENAME sequence is theH                    specification of (only) the trailing semicolon on theC                    second parameter of each of the RENAME commands.m  E                    You may also see the numbers of files reduced withgF                    DELETE commands, with multiple directories, or withA                    PURGE commands such as the following examples:o  '                    $ PURGE/BEFORE="-2-" ,                    $ PURGE/BEFORE="TODAY-2-"#                    $ PURGE/KEEP=10"p                      5-62                0                    System Management Information        H                    You can use DFU (Freeware) to quickly and efficientlyD                    scan for all files with large(r) version numbers:  2                    DFU SEARCH/VERSION=MINIMUM=nnnn  D                    If you are creating or supporting an application,G                    selecting temporary or log file filenames from amongoH                    a set of filenames-selecting filenames based on time,E                    on process id, on the day of week, week number, or J                    month, on the f$unique lexical (V7.3-2 and later), etc-H                    is often useful, as this approach more easily permitsG                    on-line adjustments to the highest file versions anddC                    easily permits on-line version compression usingfD                    techniques shown above. With differing filenames,D                    you are less likely to encounter errors resultingE                    from files that are currently locked. You can alsosG                    detect the impending version number limit within thehH                    application, and can clean up older versions and roll@                    the next file version creation to ;1 or such.  (                    Also see Section 9.4.                                              J                                                                       5-63 a                       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, thenpD                    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_hE                    PROFILE.DATA. It sometimes happens that this counteF                    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 maileG                    messages. Then enter the command one more time. Thisn3                    will resynchronize the counters.   G                    If you are operating in a cluster and find your maileC                    counts inconsistent across cluster members, youraJ                    customer is likely missing a definition of the VMSMAIL_D                    PROFILE logical name-and is probably also missingE                    definitions of other logical names associated withrE                    other shared files-or has one or more inconsistentpI                    definitions of this and likely of other logical names.o  C                    For details on the configuration data files thata>                    must be shared within a cluster, please seeE                    SYS$STARTUP:SYLOGICALS.TEMPLATE on V7.2 and later.c  D           __________________________________________________________=           6.2  How do I send or read attachments in VMS MAIL?a  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:   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 they4                       appropriate viewers available.  /                      o  http://www.process.com/   G                      o  http://www.agh.cc.kcl.ac.uk/files/vms/pine-vms/   >                      o  ftp://ftp2.kcl.ac.uk/pub/vms/pine-vms/  G                    o  If you are working from an X Windows display, younJ                       can use the OpenVMS version of Netscape Navigator orJ                       Mozilla. The mail download protocol chosen to accessH                       the mail server from the Navigator or Mozilla mailH                       client can be POP or IMAP, with the former causingH                       messages to be downloaded while the latter permitsF                       messages to be retained on the mail server. Most8                       folks prefer IMAP for this reason.  G                    o  MPACK/MUNPACK. To send a MIME mail, construct theiH                       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 provide I                       a work around for this problem, and if that doesn't E                       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,sE                       extract it to a file, then use MUNPACK to breakn5                       out and decode the attachments.   G                       MPACK/MUNPACK tools are also available on OpenVMS $                       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/IPs8                    Services V5.1 and later SMTP servers.  "                    Use a firewall.  G                    On earlier TCP/IP Services releases, some simple DCLcF                    can reportedly prevent relay SMTP spam. Use the UCXG                    command SHOW SERVICE SMTP/FULL to find the directorysE                    containing the UCX$SMTP_RECV_STARTUP.COM file, and ,                    insert the following DCL:             $       !            $       ! Block spam.a           $       ! P           $       MY_ADDRESS_LONG[0,32]=F$INTEGER(F$TRNLNM("SYS$REM_NODE")-"::")R           $       MY_ADDRESS=F$FAO("!UB.!UB.!UB.!UB",F$CVUI(0,8,MY_ADDRESS_LONG),-M                    F$CVUI(8,8,MY_ADDRESS_LONG),F$CVUI(16,8,MY_ADDRESS_LONG),-_2                    F$CVUI(24,8,MY_ADDRESS_LONG))'">           $       MY_ADDRESS_REVERSE=F$FAO("!UB.!UB.!UB.!UB",-N                    F$CVUI(24,8,MY_ADDRESS_LONG),F$CVUI(16,8,MY_ADDRESS_LONG),-M                    F$CVUI(8,8,MY_ADDRESS_LONG),F$CVUI(0,8,MY_ADDRESS_LONG))'"nS           $       WRITE SYS$OUTPUT F$TIME()+" "+F$TRNLNM("SYS$REM_NODE")+MY_ADDRESS D           $       UCX SHOW HOST 'MY_ADDRESS_REVERSE'.INPUTS.ORBS.ORG!           $       IF $STATUS.EQ.1l           $       THEN?           $         WRITE SYS$OUTPUT "SPAM from relay rejected"l           $         EXIT           $       ENDIF I           $       UCX SHOW HOST 'MY_ADDRESS_REVERSE'.SPAMSOURCES.ORBS.ORGe!           $       IF $STATUS.EQ.1            $       THENA           $         WRITE SYS$OUTPUT "SPAM source relay rejected"            $         EXIT           $       ENDIF            $       !F!           $       ! Run receiver.w           $       ! 6           $       run sys$system:ucx$smtp_receiver.exe           $       goto exita      J                                                                        6-3 c  i                    J                    _______________________________________________________  +           7        Information on Utilitiest      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 DIAGNOSEBF                    privileges, and run the .EXE. (These privileges areG                    required, as the access to the CD-related extensionstG                    will require the use of the privilege-protected IO$_ D                    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).   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 ands!                    OpenVMS Alpha.h  E                    The standard OpenVMS ATA (IDE) SYS$DQDRIVER device=A                    driver does not support the necessary does nothC                    support the necessary IO$_DIAGNOSE function codem@                    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 audioeF                    player is available on the OpenVMS Freeware websiteA                    (www.hp.com/go/openvms/freeware/, look for the)D                    directory /dqdriver/), and these updates are alsoE                    included on OpenVMS Freeware V5.0, and OpenVMS ECO C                    kits containing newer versions of the driver are E                    available. Freeware V6.0 has a version of DQDRIVER F                    that is newer than that of the OpenVMS Alpha V7.3-2  J                                                                        7-1               +                    Information on Utilities         J                    release, with additional capabilities and with improved%                    error diagnostics.h  D                    OpenVMS Alpha V7.3 and later include a version ofH                    SYS$DQDRIVER with the necessary IO$_DIAGNOSE support.  D           __________________________________________________________C           7.2  How do I access a Microsoft Windows floppy disk froms                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 whichoI                    supports DOS files on many different device types. ForlA                    more information, send mail to info@progis.de.s  C                    Engineering Software has a product called VAKSAT H                    which will read, write, and erase files on MS-DOS FATG                    diskettes. Available for both VAX and Alpha. Contact ;                    ed@cityscape.co.uk for more information.   E                    MadGoat PC Exchange (PCX) is a utility for copying G                    files to and from MS-DOS and Microsoft Windows (FAT) H                    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.   -                    o  http://www.madgoat.com/   F                    The Freeware package WINFX is available on Freeware?                    V6.0, and can read the FAT volume structure.   <                    o  http://www.hp.com/go/openvms/freeware/                              7-2    h          +                    Information on Utilitiest      D           __________________________________________________________E           7.3  How do I play sound files on an AlphaStation? DECsound                 doesn't work.  F                    Various of the more recent AlphaStation systems useH                    a different sound board (Microsoft Sound System) thanE                    the earlier DEC 3000 series systems, and DECsound,rC                    as supplied by DECwindows Motif, doesn't support G                    this board nor this interface. HP offers an optionalCC                    product, Multimedia Services (MMOV) for OpenVMS:r  9                    o  http://h18000.www1.hp.com/info/spd/e  H                       OpenVMS typically uses SPD 25.01.xx, SPD 41.87.xx,'                       and SPD 82.35.xx.e  J                    which provides a replacement for DECsound for this cardJ                    as well as many other features (an AVI and MPEG player,/                    video capture support, etc.)e  ;                    Ensoniq sound support is also available.   D           __________________________________________________________9           7.4  How do I read IBM EBCDIC tapes on OpenVMS?A  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 berI                    used to transfer fixed-record-size text files out ontosG                    tape media, or to read from fixed-record tape media.CG                    Please consult the IBM documentation for the detailsuJ                    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. C                    Visit the Encompasserve (DECUS) website software E                    archives search engine and search for "EBCDIC" for                     details.   0                    o  http://www.encompassus.org  B                    OpenVMS does not include an integrated tool forG                    EBCDIC tape processing, but does provide a characterlE                    conversion API useful within application programs.   J                                                                        7-3 e  n          +                    Information on Utilitiesr        +                    One source for ETAPE is:   <                    o  http://www.ualr.edu/ftp/vms/ETAPE_SRC/  G                    The OpenVMS Freeware V5.0 distribution included thise'                    ETAPE tool, as well.o  D           __________________________________________________________6           7.5  How can I patch an OpenVMS Alpha image?  7                    Using the OpenVMS Freeware tool ZAP:R  H                    o  Look for the RMS_TOOLS directory on Freeware V5.0:<                       http://www.hp.com/go/openvms/freeware/  C                    tell ZAP to read a block (bucket) of information G                    based on the virtual block number (VBN), using X forUG                    hexadecimal. Dump yourself into the OpenVMS debugger H                    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    k                    J                    _______________________________________________________             8        DCL Details      D           __________________________________________________________5           8.1  DCL Symbols and OpenVMS Logical Names?   J                    DCL symbols are programming-style variables implementedD                    within the DCL command interpreter, and these areC                    used both for programming and to provide command B                    verb synonyms. Symbols are local to the commandE                    interpreter operating within a particular process,dJ                    and are not shared. Lists of symbols can be copied intoG                    subprocesses during a subprocess creation operation,rE                    but these symbols are neither copied back into thetD                    parent process when the subprocess exits, nor are8                    symbols ever shared across processes.  D                    Symbols can be specified in and utilized in basicH                    mathematical operations, and bit-level operations areF                    available with the f$cvsi and f$cvui bit extractionB                    lexical functions, and with the square-bracketsF                    notation for bit insertion (see Section 8.13 for anG                    example), and with bitwise operators. Symbols are of_H                    two basic types, STRING and INTEGER, and these (or anJ                    undefined symbol) can be differentiated with the f$typeF                    lexical function. DCL symbols can also be used as aI                    mechanism to abbreviate a DCL command verb, or an easy 9                    way to invoke a DCL command procedure.t  B                    Symbols can have local or global scope within aE                    process, and scope is affected by nested procedure G                    calls and DCL constructs such as CALL and SET SCOPE, D                    but such discussions are beyond the scope of this                    section.r  G                    OpenVMS Logical names can store device names, device E                    and directory specifications, rooted or searchlist H                    specifications, and full filenames. Logical names canE                    also store arbitrary data, but there are no native I                    mathematical or bitwise operators available. Analogous E                    to DCL symbols, process-local logical names can be H                    copied into subprocesses during a subprocess creation  J                                                                        8-1    h                              DCL Details        G                    operation, but these process-local logical names areaG                    neither copied back into the parent process when theoE                    subprocess exits, nor are these logical names evert                    shared.  H                    Logical names are implemented deep within the OpenVMSI                    executive, and are organized into logical name tables.iE                    Logical names can be stored in tables private to aeG                    process( LNM$PROCESS, the process-local logical namemJ                    table) , that can be shared among processes in the sameH                    job tree ( LNM$JOB, the job logical name table) or inJ                    logical name tables that are shared among larger groupsE                    of processes (eg: LNM$GROUP, the UIC group logical J                    name table and LNM$SYSTEM, the system-wide logical nameJ                    table). Logical names are centrally intended to provideE                    various I/O-related capabilities, including device J                    independence and configuration customization-correctly-H                    written application programs can use logical names toJ                    avoid embedding specific device or device and directoryJ                    specifications, and to allow filename and configuration"                    customizations.  I                    One of the most powerful capabilities of logical namesSG                    beyond the device independence provided involves thekC                    defaulting capabilities; you can use RMS parsingtD                    (directly, or with mechanisms such as the f$parseH                    lexical function) to provide a filename and a defaultH                    filename. To provide the mechanism that allows SYSUAFD                    to be located in an arbitrary position or even anA                    arbitrary filename, a construct similar to thee%                    following is used:r  >                    $ UAF = F$PARSE("SYSUAF","SYS$SYSTEM:.DAT")  C                    This design allows the logical name SYSUAF to be H                    optionally defined, and - when present-to specify theE                    particular location and name of the file. Portions F                    of the full file specification that are omitted areI                    retrieved using the default translation of SYS$SYSTEM:a-                    and the file type of .DAT.   G                    Logical names also have assigned processor modes, as H                    some translations must be trustworthy. In the exampleI                    above, only trusted and privileged system users should I                    be able to redirect the SYSUAF authorization database,                       8-2                                   DCL Details        G                    so any definition of the SYSUAF logical name must beaJ                    made in EXECUTIVE mode in a trusted logical name table.  G                    As for common OpenVMS terminology, logical names areoH                    "defined" and the associated processing is refered toH                    as "translation", while symbols are "equated" and theI                    associated processing is refered to as "substitution". D                    "Lexical functions" are processing routines builtH                    into DCL, and typically prefixed with f$. Many of theI                    lexical functions are built upon correspondingly-namedt3                    system services, though not all.A  G                    Symbol substitution occurs only when the DCL command D                    interpreter is reading and processing the commandI                    input; for information on DCL symbol substitution, see I                    Section 8.10. For program access, see the RTL routinesG6                    lib$set_symbol and lib$get_symbol.)  J                    For information on logical name translation, please seeH                    f$trnlnm lexical function and the DCL commands DEFINEF                    and DEASSIGN, as well as underlying system servicesF                    such as sys$trnlnm. Logical name translation occursE                    when requested, or as the file or I/O operation is                     started.g  E                    Please see the OpenVMS User's Guide in the OpenVMS H                    documentation set for a far more detailed description'                    of these constructs.   E                    For related materials, please see Section 8.10 and                      Section 8.11.  D           __________________________________________________________5           8.2  How do I run a program with arguments?l  E                    The RUN command does not accept arguments. To pass F                    arguments to a program, you must use what is calledF                    a "foreign command", and either an explicit commandF                    as shown here, or an automatic foreign command. For                    example:S  3                    $ unzip :== $disk:[dir]unzip.exe                     $ unzip -?l  J                                                                        8-3 8  e                              DCL Details        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 automatic B                    foreign command definition via the logical nameG                    DCL$PATH. An example of a definition of this logical                     name is:o  M                    $ DEFINE DCL$PATH SYS$DISK:[],ddcu:[mytooldir],SYS$SYSTEM:n  G                    DCL will first look for a command in the DCL command_E                    table, and if no match is found and if DCL$PATH isFH                    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 tosE                    be activated in preference to an executable image.t  A                    For more information on foreign commands or on E                    automatic foreign command support, see the OpenVMSh!                    User's Manual.   )                    See also Section 10.3.o  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) (typicallyiF                    DCL). This is done by placing the command line in aH                    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.                       8-4                                   DCL Details        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.e  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.12.a  D           __________________________________________________________1           8.3  How can I clear the screen in DCL?   C                    The simplest way is the TYPE/PAGE NLA0: command.c  F                    You can set up a symbol to clear the screen in your                    LOGIN.COM:r  ,                    $ CLS :== TYPE/PAGE NLA0:  D           __________________________________________________________B           8.4  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:  3                    $ DEFINE/USER SYS$COMMAND _OPA0:i                    $ REPLY/LOG3                    $ DEFINE/USER SYS$COMMAND _OPA0: !                    $ REPLY/ENABLE   G                    To disable the system console terminal (OPA0:) as an_@                    operator terminal, use the following command:  3                    $ DEFINE/USER SYS$COMMAND _OPA0:R"                    $ REPLY/DISABLE  J                                                                        8-5                                   DCL Details        H                    Also see SYLOGICALS.COM (and SYLOGICALS.TEMPLATE) forE                    information on configuring the behaviour of OPCOM, D                    including the (default) use of the system consoleD                    (OPA0:) as an operator terminial and the specificI                    contents and behaviour of the system operator log files                     OPERATOR.LOG.  D           __________________________________________________________8           8.5  How do I generate a random number in DCL?  @                    With V7.3-2 and later, f$unique can be usefulF                    here. Alternatively, here is a pseudo-random numberH                    generator, just do a GOSUB RAND and the global symbolG                    RANDOM will contain a randomly generated number. YoulH                    can feed the generator a ceiling value (__CEIL)  or a%                    new seed (__SEED).S  M           $! RAND - returns a positive random number ("RANDOM") between 0 ande           $!        __CEIL - 1. -           $! sharris-at-sdsdmvax.fb3.noaa.govl           $ RAND:e           $ &           $ IF F$TYPE(__SEED) .EQS. ""           $ THEN7           $     ! seed the random number generator, ...e"           $     __NOW = F$CVTIME()0           $     __HOUR = 'F$EXTRACT(11,2,__NOW)'2           $     __MINUTE = 'F$EXTRACT(14,2,__NOW)'2           $     __SECOND = 'F$EXTRACT(17,2,__NOW)'0           $     __TICK = 'F$EXTRACT(20,2,__NOW)'           $ K           $     __SEED == __TICK + (100 * __SECOND) + (6000 * __MINUTE) + - $                    (360000 * __HOUR)N           $     ! the generator tends to do better with a large, odd seed, ...)           $     __SEED == (__SEED .OR. 1)t           $     ! clean up, ...r$           $     DELETEX/SYMBOL __NOW%           $     DELETEX/SYMBOL __HOURn'           $     DELETEX/SYMBOL __MINUTE '           $     DELETEX/SYMBOL __SECOND %           $     DELETEX/SYMBOL __TICKp           $ ENDIF,           $ ?           $ IF F$TYPE(__CEIL) .EQS. "" THEN __CEIL = %X3FFFFFFFL                      8-6                                   DCL Details                   $ (           $ __SEED == __SEED * 69069 + 1           $ A           $ RANDOM == (__SEED.AND.%X3FFFFFFF)/(%X40000000/__CEIL)a           $            $ RETURN  D           __________________________________________________________,           8.6  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 ishI                    intended to activate RSX compatibility mode utilities.mE                    When used on OpenVMS, the command is most commonly G                    used to run the specified image and-because the tool 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 similare8                    to a foreign command. In other words:                       $ MCR FOO BAR  $                    is equivalent to:  "                     $ FOO :== $FOO                     $ FOO BARo  I                    MCR is not documented. Use of a foreign command or the H                    DCL$PATH mechanism is preferred. For details on this,#                    see Section 8.2.   D           __________________________________________________________9           8.7  How do I change the OpenVMS system prompt?i  G                    You can use the SET PROMPT command for this purpose.dJ                    SET PROMPT sets the DCL prompt to the specified string.  E                    When you want to display variable information, you D                    will need to establish a tie-in that provides theE                    information to the SET PROMPT command as required.   C                    If you wish to display the default directory for E                    instance, you will have to establish a tie between J                    the SET DEFAULT command and the SET PROMPT commands, asI                    there is no direct way to get the default directory as   J                                                                        8-7                                   DCL Details        I                    the DCL prompt. You can easily acquire or create a setnI                    of DCL command procedures that perform the SET DEFAULT_G                    and SET PROMPT for you. These DCL command procedures'/                    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. B                    (This approach likely involves some kernel-modeD                    programming, and requires write access to various9                    undocumented OpenVMS data structures.)d  J                    There are related tools available from various sources,5                    including the following web sites:d  6                    o  ftp://ftp.hhs.dk/pub/vms/setpmt/  ?                    o  ftp://ftp.tmesis.com/sys_service_hook.srcn  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 tolE                       perform this task. Visit the newsgroup archivesc3                       for information and examples.   D           __________________________________________________________C           8.8  Can I do DECnet task-to-task communication with DCL?   1                    Yes, you can do this with DCL.n  H                    The OpenVMS DECnet documentation shows various simpleI                    examples using the task object and the TYPE command to H                    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.hp.com/go/openvms/wizard/  D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the availableiB                    ATW Wizard.zip archive, please see Section 3.8.                      8-8                                   DCL Details        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 avoid J                    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 cannH                    now start writing messages. (This is the essence of a>                    basic half-duplex network protocol scheme.)  D           __________________________________________________________=           8.9  How can I get the width setting of a terminal?   ;                    $ width = f$getdvi(terminal,"DEVBUFSIZ")   D           __________________________________________________________9           8.10  Why doesn't DCL symbol substitution work?   E                    The DCL symbol substitution processing occurs only D                    at the DCL prompt, not within data and not withinG                    files. If you wish to perform symbol substitution in E                    this environment, you typically write a small file D                    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.t  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 notnH                    attempt to use screen mode or similar, as this is notE                    generally considered adventageous within a commandi                    procedure.   A                    Tools such as FTP have alternatives: COPY/FTP.   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 )l  J                                                                        8-9    l                              DCL Details        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 or ,                    other spawned subprocess.  D                    For related materials, please see Section 8.1 and                     Section 8.11.  D           __________________________________________________________7           8.11  How can I substitute symbols in a PIPE?-  E                    Use DCL ampersand substitution, and not apostropheO                     substitution.  M           $ pipe show system | search sys$input opcom | (read sys$input pid ;.F               pid=f$element(0," ",pid) ; define/system opcom_pid &pid)           $ show log opcom_pid9               "OPCOM_PID" = "0000020B" (LNM$SYSTEM_TABLE)'  D           __________________________________________________________?           8.12  Use of RUN/DETACH, LOGINOUT, and logical names?E  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,MB                    /OUTPUT or /ERROR on a RUN/DETACH command, thenE                    you must translate the logical name specifications"E                    to physical references before passing them, or the J                    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 namessH                    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,CF                    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-created                       8-10t h  D                              DCL Details        H                    detached process. Shared tables include the group (ifG                    the process is in the same UIC group) and the systemtH                    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 thef3                    other group logical name table.)$  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 LOGINOUT G                    image, when specifying this command file as /INPUT.) D                    Also remember to check both security auditing andG                    system accounting when troubleshooting problems withm"                    the RUN/DETACH.  (                    Also see Section 8.2.  D           __________________________________________________________@           8.13  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:   "                    $ esc[0,7] = 27+                    $ text = "Blinking Text"p@                    $ write sys$output "''esc'[5m''text'''esc'[m"  @                    Also see sections Section 11.6, Section 12.1.                      J                                                                       8-11                         J                    _______________________________________________________             9        Files      D           __________________________________________________________)           9.1  How can I undelete a file?s  H                    OpenVMS doesn't have an "undelete" function. However,G                    if you are quick to write-protect the disk or if yourJ                    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 onD<                    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 DELETEvG                    command, and it can copy the file(s) to a "trashcan".E                    subdirectory before issuing a "real" DELETE on the(H                    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 andy/                    other similar DCL commands.)   D           __________________________________________________________I           9.2  Why does SHOW QUOTA give a different answer than DIR/SIZE?d  G                    DIRECTORY/SIZE doesn't take into account the size of F                    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,_;                    you may have files in other directories.s  J                                                                        9-1    r                              Files        ;                    $ DIRECTORY/SIZE=ALL/GRAND [username...]oI                    Grand total of D1 directories, F1 files, B1/B2 blocks.n=                    $ DIRECTORY/SIZZ=ALL/GRAND [-]username.DIRfD                    Grand total of 1 directory, 1 file, B3/B4 blocks.                    $ SHOW QUOTA C                    User [username] has B5 blocks used, B6 available P                    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, H                    then the system-manager can force a quota rebuild-dueE                    to various factors, the quota file can potentially.F                    drift from the actual use over time, and a periodicE                    rebuild can be performed at appropriate intervals.   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 that F                    is cumulative over all of the files and directoriesC                    examined, without regard for which ones might be F                    alias entries and which are not. (In other words, aG                    DIRECTORY/SIZE of an entire OpenVMS system disk willeF                    report a disk useage value larger than the (usuallyC                    more accurate) value reported by the SHOW DEVICErI                    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.)r  D           __________________________________________________________I           9.3  How do I make sure that my data is safely written to disk?   E                    If your application must absolutely guarantee that7G                    data is available, no matter what, there's really no I                    substitute for RMS Journaling and host- or controller-pJ                    based shadowing. However, you can achieve a good degreeG                    of data integrity by issuing a SYS$FLUSH RMS call atlG                    appropriate times (if you're using RMS, that is.) If_I                    you're using a high-level language's I/O system, check                       9-2    l                              Files        I                    that language's documentation to see if you can access.I                    the RMS control blocks for the open file. In C you canc0                    use fflush followed by fsync.  E                    For details on disk bad block handling on MSCP andmH                    on SCSI disk devices, please see Ask The Wizard (ATW)                     topic (6926).  :                    o  http://www.hp.com/go/openvms/wizard/  D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the availableeB                    ATW Wizard.zip archive, please see Section 3.8.  D           __________________________________________________________J           9.4  What are the limits on file specifications and directories?  H                    A file specification has an aggregate maximum size ofE                    255 characters (NAM$C_MAXRSS) at present, assuming C                    ODS-2 limits and traditional DCL process parsing C                    settings (SET PROCESS/PARSE_STYLE). The node and I                    device 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, thoughaG                    0 (latest version), -0 (oldest version) and -n (n'th I                    previous version) can be used in most contexts. A filebI                    specification may not have more than 8 directories andnI                    subdirectories or-with a rooted directory, two sets ofeH                    eight are possible-and while it is possible to createH                    subdirectories of greater depth, accessing them underH                    ODS-2 is somewhat problematic in most cases, and thus%                    should be avoided.   =                    Under ODS-5 with extended DCL parsing (SET C                    PROCESS/PARSE_STYLE), the filename length limits F                    are up around 4,095 (NAML$C_MAXRSS) characters, and=                    directories can be around 255 levels deep.   E                    Application developers should use OpenVMS-suppliedeJ                    routines for parsing file specifications - this ensuresE                    that changes in what is allowable will not tend to I                    break your application. Consider that various parts of I                    the file specification may contain quoted strings withpG                    embedded spaces and other punctuation! Some routineslH                    of interest are SYS$FILESCAN, SYS$PARSE and LIB$TRIM_  J                                                                        9-3                                   Files        E                    FILESPEC. For further information, see the OpenVMS,.                    Guide to File Applications.  A                    Performance of larger directory files improvesaF                    (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 directory (                    I/O processing logic.  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 availablen9                    reverse-DELETE DCL command procedures.c  )                    Also see Section 5.44.   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 anyo9                    particular file is 0x03FFFFFFF blocks.y  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 consolenJ                    program that limit the size of the OpenVMS system disk.C                    Note that data disks are not affected by consoleeB                    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 readsJ                    the OpenVMS bootstrap files, and these same drivers areF                    also used by OpenVMS to write the system crashdump.                        9-4                                   Files        D                    There are numerous discussions of this VAXstationE                    3100 in the comp.os.vms newsgroup archives. PleaseUI                    use Google newsgroup search to search the archives foraG                    further details, for discussions of the workarounds,eG                    and for details of the potential for a simple failediD                    bootstrap and particularly for discussions of theB                    potential for severe system disk corruptions on                    crashes.o  C                    Some SCSI disks with capacities larger than 8.58 H                    gigabytes (GB) will require the use of an OpenVMS ECOE                    kit (eg: ALPSCSI04_062 or later; see Section 14.24 G                    for details) for new SCSI device drivers. Failure to G                    use this ECO can cause "rounding errors" on the SCSI H                    disk device capacity-OpenVMS will not use nor displayG                    the full capacity of the drive-and "%sysinit-e-error F                    mounting system device status equals 000008C4" (8C4G                    -> "%SYSTEM-?-FILESTRUCT, unsupported file structureiG                    level") errors during bootstrap. (One workaround forgH                    the bootstrap when the bitmap is located far into theI                    disk is the use of INIT/INDEX=BEGIN.) The problem heresI                    involves the particular extensions and fields used fornG                    larger capacity disks within the SCSI specificationsnA                    and within the various intepretations of same.s  -                    For ATA (IDE) disk drives:c  J                    o  Versions of SYS$DQDRIVER *BEFORE* X-15 topped out at                       8.455 GB.   G                       Fixed drivers (equal or greater than "X-15") werei!                       shipped in:   7                      o  OpenVMS Alpha V7.2-1, and latero  7                      o  V7.2 UPDATE V1.0 ECO, and laters  9                      o  V7.1-2 UPDATE V1.0 ECO, and laterr  9                      o  V7.1-2 UPDATE V3.0 ECO, and later   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 137 G                       GB) but is known to report an incorrect number ofs9                       "cylinders" with disks above 33 GB.s  J                                                                        9-5 l  d                              Files        G                    See Section 14.4.4.2 for additional ATA SYS$DQDRIVER8                    information.i  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 the D                    volume. Updated SRM consoles for systems with SRMG                    and ATA (IDE) drive support are (will be) available. E                    (OpenVMS Engineering has successfully bootstrappedxI                    20GB ATA (IDE) disks using the appropriate SRM console                     version.)  1                                              Notei  A                       All disk-related listed in this section arefD                       stated in units of "disk (base ten) gigabytes"G                       (1 GB = 10^9 bytes) and not in units of "softwarer@                       (base two) gigabytes" (1 GB = 2^30; 1 GB =F                       1073741824.) bytes. Please see Section 14.24 forC                       details of the nomenclature and of the units.   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 forrH                    tape devices-to permit a larger disk volume size willE                    require a SCSI driver update for OpenVMS, and thislG                    change is part of V7.1-2 and later, and also part of E                    ALPSCSI07_062 and later. (These larger disks disksrI                    will typically report a DRVERR, or will see the volumeiH                    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.   C                    Applications written in C can be limited to file F                    sizes of two gigabytes and less, as a result of theG                    use of longword values within C file operations, andtD                    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 applicationseG                    using native C I/O to file sizes of two gigabytes oreI                    less, or these applications must use native RMS or XQP 1                    calls for specific operations.                       9-6                                   Files        9                    Also see Section 14.13, Section 14.24.S  D           __________________________________________________________E           9.6  What is the maximum file size, and the RMS record size                 limit?p  E                    RMS can store individual files of a size up to thewH                    maximum supported volume size. Under OpenVMS V6.0 andG                    later, the volume size and the RMS maximum file size B                    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 createuD                    files that are larger than a single physical diskH                    volume. (The file system attempts to balance the loadI                    on the volume sets, for example, by creating new files F                    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 is                     255."  E                    The RMS formats-sequential, relative, and indexed-cG                    are limited by the one terabyte maximum volume size.tH                    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._  :                    Also see Section 2.17.1, Section 14.24.  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?o  B                    Recording (writing) of CD and DVD optical mediaF                    requires a recording or media mastering applicationB                    or tool, and both commercial and non-commercialH                    options are available. Please see CDRECORD (both non-G                    DVD and DVD versions are available, and at least oneSJ                    commercial version is available), and also see DVDwriteE                    (commercial) or DVDRECORD (open source). A port of G                    CDRECORD is present in OpenVMS V7.3-1 and later; see                     Section 9.7.R  J                                                                        9-7                                   Files        F                    o  Acquire a comparatively recent SCSI-based or ATAE                       (IDE) CD-R or DVD-R/RW or DVD+R/RW drive. OlderaH                       drives can be very problematic, while newer drivesI                       are readily available, and are cheap and very fast.oJ                       Related device requirements information is available'                       in Section 14.28.   C                    o  Get the most recent LDDRIVER available on the_B                       Freeware. Versions of LDDRIVER are latent inB                       OpenVMS Alpha V7.3-1 and later. (Look withinD                       SYS$MANAGER:CDRECORD.COM for related details.)  A                       Use of the current ECO kit for LDDRIVER (asDE                       available), or of the version of LD distributedlF                       with V8.2 (kitted on Freeware V7.0 as LD071), orD                       later is prefered. (If you are not running theH                       specified version, you will want to upgrade or youH                       will want to use the DCL command SET FILE/CACHING_E                       ATTRIBUTES=NO_CACHING on the LD partition file._G                       This is a workaround for an incompatibility foundrI                       between older LDDRIVER versions and the XFC cachingRG                       support.) Alternatively, you can acquire and loadN9                       the VD64 package from the Freeware.   H                    o  Get CDRECORD or CDWRITE or other similar recording                       tool._  ?                       CDRECORD (part of CDRTOOLS), CDWRITE, andU<                       DVDRECORD (part of DVDRTOOLS) packagesB                       (DVDRECORD is a fork of CDRECORD) are freely=                       available, and versions of CDRECORD are_D                       available on the Freeware V6.0 distribution. (I                       http://www.hp.com/go/openvms/freeware/ ) An OpenVMS I                       port of the cmcd CD audio ripper is also reportedlyT9                       available. http://www.amb.org/xmcd/   J                       Versions of CDRECORD (non-DVD) are latent in OpenVMSD                       Alpha V7.3-1 and later. Commercial versions ofH                       CDDRECORD-with DVD capabilities-are also availableJ                       for various platforms, and particularly a variant of8                       CDRECORD known as CDRECORD-ProDVD.  ?                       Beware the tool chosen: some versions andiF                       configurations of CDRECORD can record DVD media,I                       as can the DVDRECORD package, as can the commercialcH                       DVDwrite package. Many versions of CDRECORD cannotI                       record DVD media, including the version of CDRECORDc                      9-8 u                                 Files        D                       latent within OpenVMS and the version found onE                       Freeware V6.0; these versions cannot record DVDd                       media.  F                    o  Build the contents of the disk on the LD or VD64'                       device partition.o  J                    o  Use the chosen recording tool to record the contentsC                       of the LD or VD64 partition directly onto the %                       optical medium.   C                    Alternatively, consider the following command on 2                    OpenVMS Alpha V7.3-1 and later:  1                    @SYS$MANAGER:CDRECORD.COM HELP,  H                    While folks have had success getting PC-based CD-R/RWE                    or DVD-R/RW or DVD+R/RW tools to work with OpenVMSOH                    partitions, it is far easier and more reliable to useJ                    the OpenVMS-based versions of these tools and directly-I                    attached devices. If you use a Windows-based tool, youiG                    will want to specifically select its raw mode, imagenI                    mode, or block-copy mode, depending on the terminologydD                    within the particular tool. The transfer mode andG                    selections is variously refered to as a disk-at-once H                    (DAO) 2048-byte block ISO Mode 1 raw/image/block data'                    disk recording mode.e  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 packagesdH                    will be included in this), or the use of a host-basedI                    package such as the CDRECORD or CDWRITE13_VMS or othertE                    utilities, including OpenVMS ports of common open-aF                    source tools made available by Dr. Eberhard Heuser-F                    Hofmann and various others. Commercial packages andE                    options are also available. Dr. Heuser-Hofmann has G                    DVDwrite , a commercial package which can record DVDs@                    media. ( http://home.tiscali.de/dvd4openvms )  E                    OpenVMS can read ODS-2, ODS-5, and ISO-9660 formatuF                    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.)   J                                                                        9-9   --    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: Mon, 11 Apr 2005 19:49:38 GMT.# From: hoff@hp.nospam (Hoff Hoffman)n< Subject: OpenVMS Frequently Asked Questions (FAQ), Part 6/110 Message-ID: <mxA6e.3489$IL.793@news.cpqcorp.net>   Archive-name: dec-faq/vms/part6e Posting-Frequency: quarterly Last-modified: 11 Apr 2005 Version: VMSFAQ_20050411-06.TXT     t                              Files        C                    InfoServer hardware configurations are no longereE                    available from HP, but may potentially be acquiredPE                    through other means; as used equipment. InfoServeriG                    support also has very specific CD-R recording device D                    prerequisites, and these recording devices are no.                    longer generally available.  H                    Packages related to the use of DVD archiving are alsoF                    available, see the multi-volume capabilities of the/                    DVDarchive/restore Freeware.   R                    http://www.geocities.com/SiliconValley/Lakes/9999/vmscdwri.html  G                    Additional information is available at the followingq                    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/t  G                    U.S. Design offers a package that includes the tools.I                    necessary to create a CD or DVD-R with either ISO-9660oE                    or ODS-2 format, for standalone CD-R/RW, DVD-R, or_H                    DVD+R/RW drives, for recent OpenVMS versions. Details$                    are available at:  .                    o  http://www.usdesign.com/  B                    Also see Section 9.7.2 for details on access to9                    recorded media on older CD-ROM drives.   '           _____________________________ 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 CDyI                    media was physically stamped, a recording process that(F                    is now largely reserved to the highest-volume media-                    reproduction requirements.e                      9-10     c                              Files        E                    CD-R is CD Recordable, a write-once storage mediumrG                    that can be read by all but the oldest of CD drives;sH                    a format which can be read and often even recorded by%                    most CD-RW drives.n  H                    CD-RW is CD ReWritable, a format which is readable byI                    many CD drives and by most CD-R drives, and with media H                    that can be recorded and re-recorded by CD-RW drives.  G                    CD media recording speeds are listed as multiples ofhF                    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 DVDeI                    and particularly first-generation DVD players may havee6                    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, olderH                    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), E                    the resulting recorded media is generally readable G                    (playable) in all recent DVD drives and DVD players, H                    regardless of type. (Compatibility is best within theF                    same media-series devices of course, but be certainG                    to verify compatibility across devices regardless of   J                                                                       9-11 N  V                              Files        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, thecI                    differences in DVD media costs are becoming irrelevent D                    for all but the production of huge volumes of DVD                    media.n  J                    The rated DVD recording speeds are in multiples of 1353G                    kilobytes per second, thus a DVD 1X drive is roughly F                    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) I                    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.  '           _____________________________sI           9.7.2  Use of RRD42 and other older (embossed-media) CD drives?l  I                    The RRD42 series SCSI CD-ROM drive is sufficiently olddF                    that it can have problems processing CD-R and CD-RWF                    media. Other very old CD drives can have equivalentG                    media compatibility problems when attempting to readtI                    (much) newer CD media and newer CD media technologies.sG                    These older CD drives are generally intended for useiF                    with the so-called embossed media, rather than withI                    non-embossed recorded (recordable) media now in common                     circulation._  G                    Please consider using a slightly-less-ancient CD-ROMuH                    or CD-R or CD-RW drive when working with non-embossed%                    recorded CD media.e  E                    To paraphrase one knowledgable-though deliberatelyoF                    nameless-storage engineer, "The RRD42 drive is just2                    past the drooling idiot stage".                        9-12t                                   Files      '           _____________________________A?           9.7.3  Creating Bootable OpenVMS I64 CD or DVD Media?                   SYS$SETBOOT?   E                    If you are creating a bootable CD or DVD media for E                    use with OpenVMS I64, you will want to specify the_I                    SYS$SETBOOT block size of 2048, and you will also want_G                    a disk cluster factor that is a multiple of four viasG                    INITIALIZE/CLUSTER=4 (or 8, or...), or you will wanteE                    to ensure that SYS$EFI.SYS and SYS$DIAGNOSTICS.SYS F                    are aligned to a multiple of four blocks; to a 2048E                    byte boundary. This alignment and this blocking isdI                    only necessary for OpenVMS I64, and only when creating <                    optical media OpenVMS I64 for bootstraps.  I                    The default 512-byte block setting used by SYS$SETBOOTrI                    is the correct and expected value for traditional disk,5                    bootstraps on OpenVMS I64 systems.   G                    Once the boot files are loaded, OpenVMS I64 operatesiH                    with 512-byte blocks; as is the case with ATAPI disksG                    on OpenVMS Alpha, all application code will only seemC                    512-byte blocks on optical media on OpenVMS I64.   =                    OpenVMS I64 V8.2 and later are expected to A                    have a version of SYS$SETBOOT that will flag a G                    misaligned SYS$EFI.SYS and (if present) a misaligned ,                    SYS$DIAGNOSTICS.SYS file.  G                    For information on SYS$SETBOOT and the SET BOOTBLOCKiA                    command, please see Section 14.3.9 and see theyG                    OpenVMS documentation. The purpose and intent of thepF                    SYS$SETBOOT.EXE image and the SET BOOTBLOCK commandF                    is analogous to the WRITEBOOT.EXE image on existing9                    OpenVMS VAX and OpenVMS Alpha systems._  E                    For information on CD and DVD optical media drivesnG                    on OpenVMS, please see Section 14.28. For additionaltJ                    related information on creating bootable OpenVMS media,:                    please see Ask The Wizard topic (9820).          J                                                                       9-13    o                              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 driver=E                    combination; there is no inherent limit imposed byiH                    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 are E                    limited to 65535 bytes-to help ensure that the I/O I                    fragmentation processing happens on the client and not (                    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 ando,                    the device can handle it.  5                    Also see Section 9.4, Section 9.5.p  D           __________________________________________________________C           9.9  Can I use ODBC to connect to OpenVMS database files?m  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),eE                    SolutionsIQ, OpenLink Software (OpenLink Universalt.                    Data Access), and Synergex.                      9-14h -                                 Files        4                    The unixODBC package available atF                    http://www.unixodbc.org has variously been found to/                    operate on OpenVMS, as well.M  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 reportedtF                    in full XFC mode; all disks shown will be listed in*                    "VIOC Compatable Mode".  I                    If you have the OpenVMS system parameter VCC_FLAGS setoG                    to 2 and are using OpenVMS Alpha V7.3-1 or later, orfG                    are using OpenVMS Alpha V7.3 with the VMS73_XFC V2.0rJ                    ECO kit or later or with the UPDATE kits, you are using                    XFC.a  D                    Another confusion: the XFC product version is andI                    remains V1.0 in all released configurations, please doaJ                    not confuse the internal XFC product version (displayedJ                    by various commands) with the version number associatedH                    with the various ECO kit(s). XFC V1.0 does not permitI                    volumes to enter full XFC caching, as displayed by the J                    "Vols in Full XFC mode" portion of the DCL command SHOW'                    MEMORY/CACHE output.   D           __________________________________________________________>           9.11  RMS Sequential Files and Platform Portability?  F                    When working with mixed platforms, you will want toI                    become familiar with the various RMS sequential recordaH                    formats, including Variable with Fixed Control (VFC),G                    stream, stream LF, and stream CR, among other record                     formats.d  J                                                                       9-15 u  2                              Files        <                    Switching formats uses CONVERT/FDL or SETB                    FILE/ATTRIBUTES. The former converts files, theH                    latter resets attributes. Text editors tend to selectE                    attributes when creating new files that may or may F                    not meet requirements. If the default attributes doG                    not match your requirements, create a stub file, SET H                    FILE/ATTR, then edit the existing file. (Most editorsA                    will preserve attributes on an existing file.)   H                    When working with Windows, stream is usually the bestC                    choice for sequential file operations. Stream LF F                    is most commonly used with UNIX and C applications.H                    Windows and UNIX tend not to be able to directly readG                    files of "unexpected" sequential RMS record formats.   F                    VFC is a common OpenVMS format, encoding the recordI                    length into the record. It is this extra data that cancJ                    cause corruption-like problems when viewed without RMS;I                    either directly via $qio or via the file system API on J                    other operating system platforms. You will want to lookF                    at the low-level record formats, and at the RMS andJ                    the Files and Applications documentation in the OpenVMS                    manuals.l  C                    If transfering through other platforms, use of arI                    current version of Zip (with the "-Vv" or "-V" option) E                    and unzip, or use of a BACKUP saveset will contain H                    and maintain the RMS file and record attributes. (ForF                    BACKUP and its own attributes requirements, see the%                    restoration tool.)2                                                9-16F F  o                    J                    _______________________________________________________  2           10       OpenVMS Programming Information      D           __________________________________________________________I           10.1  Modular Programming, Facility Prefixes and Symbol Naming?   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 locatedtF                       in shared directories. The prefix and the use ofI                       the dollar sign (<$>) and the underscore (<_>) helphF                       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 FreewareiH                       SDL package, and the GNM package. These permit youI                       to generate include files and message documentationrF                       akin to that of OpenVMS, providing users of your:                       product with a familiar environment.  I                    o  For product installations, consider use of the PCSIuJ                       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 namedl=                       SYS$STARTUP:prefix$STARTUP.COM, and thee:                       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 product G                    you distributinng to other customer sites, send your   J                                                                       10-1               2                    OpenVMS Programming Information        F                    request in a mail message addressed to product[-at-J                    sign-]hylndr.sqp.zko.dec.com, requesting the submission@                    form and details of the registration process.  1                                              Notet  A                       Please do not request facility prefixes for @                       products that local to your business, yourA                       site, or your system. Facility prefixes andiA                       message codes and the facility registration A                       process are intended solely for HP productsnA                       and Partner Products (and yes, even OpenVMSsA                       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.22, please also see the Ask The Wizard topicF                    (1661), and for information on debugging an OpenVMS8                    application, please see topic (7552).  :                    o  http://www.hp.com/go/openvms/wizard/  D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the available B                    ATW Wizard.zip archive, please see Section 3.8.  D           __________________________________________________________?           10.2  Can I have a source code example of calling...?)  J                    Please use the available SEARCH command on OpenVMS, andE                    please remember to search the available resources,dD                    including the support databases and the newsgroupI                    archives. Please also realize that most OpenVMS systemrJ                    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 notkF                    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/3  <                    o  http://www.hp.com/go/openvms/freeware/                      10-2t               2                    OpenVMS Programming Information        ,                    o  http://www.google.com/  C                    OpenVMS programming documentation, including the H                    numerous example programs found in recent versions ofI                    the OpenVMS Programming Concepts manual, is available:e  7                    o  http://www.hp.com/go/openvms/doc/   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.   J                    There is extensive information available on how to callG                    OpenVMS system services and OpenVMS Run-Time LibraryiF                    routines, including examples in numerous languages.;                    Among the best available references are:   1                    o  Your language's User Manuall  <                    o  OpenVMS Programming Environment Manual  9                    o  OpenVMS Programming Concepts Manualf  F                    o  OpenVMS Programming Interfaces: Calling a System                       Routine   .                    o  OpenVMS Calling Standard  C                    In addition, you can also locate answers, sourcesG                    code examples and related discussions in the Natural =                    Language Search Assistant (AskQ) database:_  -                    o  http://askq.compaq.com/   A                    In this area, you will find the source code of @                    programming examples for calls to many of theH                    OpenVMS system services (and from various programming?                    languages), including calls to core services G                    sys$getjpi[w], sys$getsyi[w] and sys$qio[w], as well I                    as source code examples for calls to many other system J                    services and run-time library routines, and examples of  J                                                                       10-3 .  h          2                    OpenVMS Programming Information        H                    one of the more difficult calling interfaces found onH                    OpenVMS systems, that of the smg$create_menu routine.  G                    Arne Vajhj has put together a collection of OpenVMST8                    example programs. It can be found at:  /                    o  ftp://ftp.hhs.dk/pub/vms/a  F                    Additional information and examples for OpenVMS are!                    available via:e  :                    o  http://www.hp.com/go/openvms/wizard/  D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the availablehF                    ATW Wizard.zip archive, please see Section 3.8. and                    via:4  <                    o  http://www.hp.com/go/openvms/freeware/  D           __________________________________________________________A           10.3  How do I get the arguments from the command line?D  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 invoke9E                    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 getrJ                    an error), call LIB$GET_FOREIGN to get the command line+                    and do the manual parse.t  (                    See also Section 8.2.                      10-4a b             2                    OpenVMS Programming Information      D           __________________________________________________________E           10.4  How do I get a formatted error message in a variable?M  C                    Use the SYS$PUTMSG system service with an actionEJ                    routine that stores the message line(s) in the variableE                    of your choice. Be sure the action routine returns C                    a "false" (low bit clear) function value so thateE                    SYS$PUTMSG doesn't then try to display the messageeJ                    (unless you want it to.) See the description of $PUTMSGI                    in the System Services Reference Manual for an exampleL.                    of using an action routine.  D           __________________________________________________________D           10.5  How do I link against SYS$SYSTEM:SYS.STB on an Alpha                 system?V  I                    LINK/SYSEXE is the OpenVMS Alpha equivalent of linkinglF                    against SYS.STB. This links against the base image:%                    SYS$BASE_IMAGE.EXEo  G                    Also see Section 10.11, particularly for pointers to F                    the details on shareable images and shareable imageH                    creation, and see Section 10.22 for details of inner-G                    mode floating point requirements, of data alignment, G                    requirements for use of /NOSYSLIB, and other relatedvH                    inner-mode programming details, and see Section 10.111                    for image-related information.   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 call F                    LIB$SET_LOGICAL to change the logical SYS$DISK. YouI                    will need to call both LIB$SET_LOGICAL and SYS$SETDDIRgI                    to change both default disk and the default directory!e  D           __________________________________________________________I           10.7  How do I turn my Fortran COMMON into a shareable image onD                 Alpha?  F                    You need to add SYMBOL_VECTOR=(<common-name>=PSECT)G                    to your options file. On OpenVMS VAX all OVR/REL/GBL H                    psects were automatically exported into the shareableI                    image's Global Symbol Table. On OpenVMS Alpha you haveuF                    to tell the linker that you want this done by means  J                                                                       10-5               2                    OpenVMS Programming Information        I                    of the PSECT keyword in the SYMBOL_VECTOR options filer                    statement.g  G                    This has several advantages over OpenVMS VAX. First, I                    you don't have to worry about the address of the psectsD                    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 theV#                    shareable image.d  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 wantedeH                    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 inpJ                    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 LibrarycC                    Reference Manual, and can perform floating pointfH                    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 which C                    will perform automatic conversion of unformatted B                    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.                      10-6- -  -          2                    OpenVMS Programming Information        G                    For further floating-point related information, see:   M                    o  http://www.hhs.dk/anonymous/pub/vms/collection/ieee.zipf  D           __________________________________________________________E           10.9  How do I get the argument count in a Fortran routine?r  E                    On VAX, many programmers would use a MACRO routineeB                    which accessed the AP register of the caller toE                    get the address of the argument list and hence thecJ                    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 isG                    IARGCOUNT, which is also available in DEC Fortran on                     OpenVMS VAX.   F                    Note that omitting arguments to Fortran routines isC                    non-standard and is unsupported. It will work in/F                    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 notRE                    use hardware IDs in the licensing methods, as manyoI                    users consider a hardware-based licensing scheme to beVJ                    negative attribute when considering software purchases.  E                    HP OpenVMS uses a software-based system called the.G                    License Management Facility (LMF). This provides forCE                    software keys (Product Authorization Keys or PAKS).J                    which support capacity and user-based license checking.D                    HP offers an LMF PAK Generator to CSA members-see                     Section 2.13.  I                    For information on licensing, please see Section 12.4.(  J                                                                       10-7               2                    OpenVMS Programming Information        G                    However, if a hardware-based method is required, theCE                    most common method is based on an Ethernet adaptor H                    hardware address. Sample source code for implementing(                    this is available at:  :                    o  http://www.hp.com/go/openvms/wizard/  D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the available B                    ATW Wizard.zip archive, please see Section 3.8.  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 types I                    of images include executable images, shareable images, >                    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 can D                    grant enhanced access with the specification of aF                    subsystem identifier on the ACL associated with the                    image.e  E                    Shareable images contain code executed indirectly,hE                    these images are referenced from executable imagestG                    and/or from other shareable images. These images canaF                    not grant enhanced privileges, even with the use ofE                    INSTALL with /PRIVILEGE or a subsystem identifier.iF                    These shareable images can be dynamically activatedE                    (a LINK that occurs at run-time) via the LIB$FIND_ D                    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-arerH                    similiar in some ways to a standard shareable images,H                    but these images include a `change mode' handler, and                      10-8n e             2                    OpenVMS Programming Information        I                    execute in an `inner' processor mode (privileged mode; J                    executive or kernel), and code executing in inner modesH                    has implicit SETPRV privilege. Must be INSTALLed withG                    /PROTECT. Note that inner-mode code has restrictionseJ                    around calling library routines, around calling variousF                    system services, and around calling code located in7                    other protected or shareable images.n  I                    Loadable images and device drivers are images that cangG                    be used to add code into the OpenVMS kernel. Pseudo-eF                    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 apI                    calling interface with support for both privileged and H                    unprivileged access to the driver code via sys$qio[w]                    calls.s  D                    A cookbook approach to creating OpenVMS shareable2                    images is available at the URL:  :                    o  http://www.hp.com/go/openvms/wizard/  D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the availableeB                    ATW Wizard.zip archive, please see Section 3.8.  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 usingeG                    lib$spawn(),  system(), sys$sndjbc() or sys$creprc()dJ                    to invoke a DCL COPY command. Other common alternativesF                    include using the callable convert routines and theE                    BACKUP application programming interface (V7.1 anda                    later).              J                                                                       10-9 r             2                    OpenVMS Programming Information      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 theaJ                    storage used for the data, typically static or dynamic.7                    Descriptors are passed by reference.T  C                    The following are examples of creating and using G                    descriptors in C, with the use of the angle bracketsL@                    normally expected by the C include statements=                    deliberately altered in deference to HTML:   +                        #include {descrip.h}k0                        #include {lib$routines.h}*                        #include {stsdef.h}#                        int RetStat; *                        char TxtBuf[TXTSIZ]8                        struct dsc$descriptor StaticDsc =C                          { 0, DSC$K_DTYPE_T, DSC$K_CLASS_S, NULL }; 5                        struct dsc$descriptor DynDsc =tC                          { 0, DSC$K_DTYPE_T, DSC$K_CLASS_D, NULL };s+                        int DynDscLen = 255;aC                        $DESCRIPTOR( ConstDsc, "This is a string" );o  B                        /* finish setting up a static descriptor */<                        StaticDsc.dsc$w_length      = TXTSIZ;E                        StaticDsc.dsc$a_pointer     = (void *) TxtBuf;O  C                        /* finish setting up a dynamic descriptor */eE                        RetStat = lib$sget1_dd( &DynDscLen, &DynDsc );Y=                        if ( !$VMS_STATUS_SUCCESS( RetStat ) )S(                          return RetStat;  8                        /* release the dynamic storage */:                        RetStat = lib$sfree1_dd( &DynDsc );;                        if (!$VMS_STATUS_SUCCESS( RetStat ))n(                          return RetStat;  F                    Static descriptors reference storage entirely underG                    application program control, and the contents of theVH                    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 alterr                      10-10               2                    OpenVMS Programming Information        D                    the address or length values stored in the staticJ                    descriptor. (The term "static" refers to the descriptorE                    data structure, and not necessarily to the storager1                    referenced by the descriptor.)   B                    Dynamic descriptors reference storage under theG                    control of the run-time library, and the contents ofcH                    a dynamic descriptor data structure-once initialized-I                    can only be modified under control of run-time libraryLJ                    routines. The dynamic storage referenced by the dynamicI                    descriptor is allocated and maintained by the run-timeBF                    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 storageG                    associated with the dynamic descriptor, as required.tJ                    Routines can obviously access and alter the contents of<                    the storage referenced by the descriptor.  E                    OpenVMS languages that include support for stringssD                    or arrays are expected to use descriptors for theE                    particular structure. Most OpenVMS languages, such A                    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, seerG                    the OpenVMS Programming Concepts manual, part of thei-                    OpenVMS documentation set.e  D                    Fortran defaults to passing integers by referenceD                    and characters by descriptor. The following sitesG                    discuss mixing Fortran and C source code in the samec                    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            J                                                                      10-11               2                    OpenVMS Programming Information      D           __________________________________________________________B           10.14  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 suchSD                    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 currentv"                    security model.  B                    With OpenVMS V6.2 and later, the persona systemE                    services (SYS$PERSONA_*) can be used to assume thelJ                    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" aroundmH                    a sys$creprc process creation call, as well-this willG                    create a seperate process entirely under the assumeds                    persona.t  I                    Information on the persona system services is includedtB                    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 arep@                    supported in OpenVMS V6.2 and later releases.  J                    Typical mechanisms for creating a process under another$                    username include:  E                    o  personna services around a sys$creprc call. See7                       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 job G                       under the target user. The network-mode job mighteI                       do little more than a RUN/DETACH of an image passedFE                       in via task-to-task-task-to-task communicationsiC                       are fully available using strictly DCL-to-DCL G                       processing, or using a compiled language and DCL,                        etc.)d  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 doeI                       little more than a RUN/DETACH of an image passed in &                       via a parameter.                      10-12 i  w          2                    OpenVMS Programming Information        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.   -                    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.15  Why do lib$spawn, lib$set_symbol fail in detached                  processes?   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 CLI H                    present in the current process, these calls will failE                    with a "NOCLI, no CLI present to perform function"                     error.t  J                    Detached processes typically do not have a CLI present.  G                    In place of lib$spawn, sys$creprc can often be used.hI                    The context of the parent process (symbols and logicalsI                    names) will not be propogated into the subprocess whenlJ                    sys$creprc is used, though when there is no CLI presentE                    in the process this (lack of) propogation is moot.   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 (andeH                    any other calls requiring a CLI) from images that areH                    running in an "interactive", "batch", or "other" mode                    process._  E                    Also note that the lib$spawn and the C system callaJ                    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.V  J                                                                      10-13 r  i          2                    OpenVMS Programming Information      D           __________________________________________________________@           10.16  Where can I obtain Bliss, and the libraries and"                  supporting files?  E                    The Bliss language compilers and documentation areoC                    available on the OpenVMS Freeware distributions.c  I                    Bliss language source code that contains the following.                    statement:   7                      LIBRARY 'SYS$LIBRARY:STARLET.L32';(  @                    or similar requires the presence of the BlissG                    libraries. These libraries are created on the targeteF                    system using the Bliss require files, and are built6                    using the following Bliss commands:  I                    STARLET.L32 contains the public interfaces to OpenVMS:   H                        $ BLISS /LIBRARY=SYS$COMMON:[SYSLIB]STARLET.L32 -2                            SYS$LIBRARY:STARLET.REQ  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:o  G                        $ BLISS/A64/LIBRARY=SYS$COMMON:[SYSLIB]LIB.L64 - F                            SYS$LIBRARY:LIB.R64+STARLET.REQ+STARLET.R64K                        $ BLISS/A64/LIBRARY=SYS$COMMON:[SYSLIB]STARLET.L64 -u2                            SYS$LIBRARY:STARLET.R64  C                    Some Bliss code may also require the OpenVMS VAX F                    architecture flags. The following is the equivilent5                    of the Alpha ARCH_DEFS.REQ module:i                                  10-14    u          2                    OpenVMS Programming Information                   ! A           ! This is the OpenVMS VAX version of ARCH_DEFS.REQ, and D           ! contains the architectural definitions for conditionallyC           ! compiling OpenVMS Bliss sources for use on VAX systems. D           ! (If you should encounter compilation errors here, please>           ! seriously consider upgrading your Bliss compiler.)           !            MACRO VAXPAGE = 1%;t           MACRO BIGPAGE = 0%;a           !uE           MACRO VAX =                     ! = 1 if compiled BLISS/VAXoI                   %BLISS(BLISS32V)%;      ! = 0 if not compiled BLISS/VAXp  Y           MACRO EVAX =                    ! = 1 if compiled BLISS/E* (Obsolete, old name) V                   (%BLISS(BLISS32E) OR %BLISS(BLISS64E))%; ! = 0 if compiled /VAX /Inn  T           MACRO ALPHA =                   ! = 1 if compiled BLISS/E* (New arch name)V                   (%BLISS(BLISS32E) OR %BLISS(BLISS64E))%; ! = 0 if compiled /VAX /Inn  T           MACRO IA64 =                    ! = 1 if compiled BLISS/I* (New arch name)Y                   (%BLISS(BLISS32I) OR %BLISS(BLISS64I))%; ! = 0 if compiled /VAX or /Anna             MACRO ADDRESSBITS = M                   %BPADDR%;               ! = 32 or 64 based on compiler used   G                    Some Bliss code may require the definition files fortF                    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.REQ.  D           __________________________________________________________9           10.17  How can I open a file for shared access?n  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 iseJ                    available in topic (2867) in the OpenVMS Ask The Wizard                    area:  :                    o  http://www.hp.com/go/openvms/wizard/  J                                                                      10-15               2                    OpenVMS Programming Information        D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the available B                    ATW Wizard.zip archive, please see Section 3.8.  F                    Depending on the environment, you may need to use CI                    calls such as fsync and fflush, and-in specific cases- ,                    the setvbuf(_IONBF) call.  D           __________________________________________________________G           10.18  How can I have common sources for messages, constants?a  D                    Use the GNM tools on the OpenVMS Freeware to haveB                    common sources for MSG (message) files and SDMLC                    (Document) documentation files. Use the DOCUMENTmE                    command to convert the SDML documentation into the G                    necessary formats (Text, Postscript, HTML, etc). UsehH                    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 SDLeJ                    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.19  How do I activate the OpenVMS Debugger from an                   application?n  ,                    #include {lib$routines.h}%                    #include {ssdef.h} &                    #include {string.h}                      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;                        }                      10-16    t          2                    OpenVMS Programming Information      D           __________________________________________________________*           10.20  Dealing with Endian-ness?  F                    OpenVMS VAX, OpenVMS Alpha and OpenVMS I64 (as wellH                    as all Microsoft Windows implementations) all supportG                    and all use the little-endian byte ordering. Certain B                    Alpha microprocessors and certain Intel ItaniumH                    processors can be configured to operate in big-endianE                    and potentially in bi-endian mode. HP-UX typically '                    operates big-endian.m  G                    With little-endian byte order, the least significantnH                    byte is always the first byte; the byte at the lowestC                    address. With big-endian byte ordering, the byte J                    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 DatawF                    Representation) libraries. One of the more recentlyE                    introduced network formats, and one that is seeingnB                    extensive press and marketing coverage, is XML.  D           __________________________________________________________7           10.21  How to resolve LINK-I-DATMISCH errors?I  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 that,F                    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:9  K           $ 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.  J                                                                      10-17               2                    OpenVMS Programming Information      D           __________________________________________________________E           10.22  HP C and other OpenVMS C Programming Considerations?e  E                    VAX C V3.2 was released for OpenVMS VAX systems inaI                    1991. DEC C V4.0 replaced VAX C V3.2 in 1993 as the HPoG                    C compiler for OpenVMS VAX systems. HP C is the ANSIoG                    C compiler for OpenVMS Alpha systems. VAX C predates'G                    the ANSI C standards, and has various areas that aretJ                    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 compiler_I                    between V3.2 and V6.5 (exclusive) were known as DEC C,a+                    DIGITAL C, and Compaq C.   J                    Both compilers can be installed at the same time on theI                    same OpenVMS VAX system, allowing a migration from VAXSJ                    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 CSJ                    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._  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 RTLdF                    kit, a kit that is included with the HP C compiler.G                    OpenVMS VAX versions V6.1 and later do not require anH                    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 libraryeH                    routine, use /PREFIX=(ALL_ENTRIES,EXCEPT=(...)). (VAXH                    C required explicit specification of an RTL shareable>                    image or C object library during the link.)                        10-18               2                    OpenVMS Programming Information        H                    When the /PREFIX is requested, the compiler generatesI                    a "decc$" prefix on the specified symbols. This prefix D                    allows the LINKER to resolve the external symbolsG                    against the symbols present in the DECC$SHR library.tG                    The DECC$SHR library is included in the IMAGELIB.OLByG                    shareable image library, and IMAGELIB is searched bytH                    default when any program (written in any language) isG                    LINKed. Because the standard C library routine namesaH                    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:  D                    o  Failure to specify the prefixing qualifier (onH                       certain and usually older versions of C) can causeH                       the compiler to not add the prefixes for the namesC                       of the C library routines into the references D                       placed in the object module, which can in turnF                       cause problems resolving the external symbols inA                       the library when the object code is linked:              /PREFIX=ALL_ENTRIESt  I                    o  Some VAX C programs erroneously write to the stringeC                       literals. By default, HP C does not allow the *                       constants to change.  *           /ASSUME=WRITABLE_STRING_LITERALS  F                    o  Enables sharing ("shr") of globals and of externC                       variables. HP C sets externs as non-shareable 0                       ("noshr"), VAX C as "shr".             /SHARE_GLOBALS  J                                                                      10-19               2                    OpenVMS Programming Information        C                    o  VAX C assumes common block model for external                        linkages.s  #           /EXTERN_MODE=COMMON_BLOCKi  J                    o  Refers to the padding placed between member elementsG                       within a struct. Disabling member alignment packs A                       the data more tightly into memory, but thiseE                       packaging has performance implications, both on C                       OpenVMS VAX and particularly on OpenVMS Alpha                        systems.             /[NO]MEMBER_ALIGNMENTo  G                    o  Enable all manner of useful compiler diagnostics:   N           /WARN=ENABLE=(LEVEL4,QUESTCODE)/STANDARD=PORT/ACCEPT=NOVAXC_KEYWORDS  E                       You can disable extraneous diagnostics with the                         following:  #                       #ifdef __DECC *                       #pragma message saveK                       #pragma message disable /* insert message tag here */                        #endif  C                    Permit structure members to be naturally alignedp@                    whenever possible, and avoid using /NOMEMBER_F                    ALIGNMENT. If you need to disable member alignment,G                    use the equivilent #pragma to designate the specific_J                    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-member                     alignment.i  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 suchmH                    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 from                      10-20 a  n          2                    OpenVMS Programming Information        H                    older DEC C versions can sometimes cause the compiler3                    troubles locating header files.)   D                    HP C V5.6 and later include a backport library, aC                    mechanism by which HP C running on older OpenVMSoG                    releases can gain access to newer RTL routines addediI                    to the RTL in later OpenVMS releases-the language RTLs/H                    ship with OpenVMS itself, and not with the compilers.  C                    Example C code is available in SYS$EXAMPLES:, infB                    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.hp.com/go/openvms/wizard/  D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the availableuB                    ATW Wizard.zip archive, please see Section 3.8.  '           _____________________________ (           10.22.1  Other common C issues  H                    The localtime()  function and various other functionsI                    maintain the number of years since 1900 in the "structhJ                    tm" structure member tm_year. This field will contain aI                    value of 100 in the year 2000, 101 for 2001, etc., andeI                    the yearly incrementation of this field is expected toe                    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 (wheniF                    interpreted as a signed longword) circa 03:14:07 onF                    19-Jan-2038 (GMT), as this time is circa 0x7FFFFFFFB                    seconds since the C base date. (The most commonE                    solution is to ensure that time_t is an unsigned.)d  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 application  J                                                                      10-21 l             2                    OpenVMS Programming Information        H                    program, or by an incorrect OpenVMS UTC configurationB                    on the local system. (See section Section 4.3.)  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 withvI                    OpenVMS Alpha high-IPL kernel-mode code such as device I                    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.   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. F                    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 are F                    subject to change (and that can accordingly lead toD                    requirements for the recompilation of application                    code).a  H                    In addition to the user-mode C Run-Time Library (RTL)C                    mentioned in the OpenVMS C RTL documentation andsH                    referenced over in Section 3.9, there is a second andH                    parallel kernel-mode RTL accessable to device driversE                    and other kernel code on OpenVMS Alpha and OpenVMSaE                    I64. The most common time this second C library is F                    noticed is when C code is (erroneously) linked withH                    /SYSEXE/SYSLIB, and duplicate symbol errors typicallyI                    then arise. As code running in supervisor-, executive- E                    or kernel-mode context cannot call out a user-mode C                    RTL or other user-mode library, you will want to G                    respecify the command as LINK /SYSEXE/NOSYSLIB. ThiscI                    will eliminate the duplicate symbol errors, since onlyfJ                    the kernel-mode library will be referenced, and it willG                    also avoid calling out into the user-mode libraries.i                      10-22               2                    OpenVMS Programming Information        G                    When sharing variables with other languages, here isr,                    some example HP C code...                            ...2                          #pragma extern_model save;                          #pragma extern_model strict_refdef 4                          extern int   VMS$GL_FLAVOR;5                          #pragma extern_model restore#                          ...  D                    and here is some associated example Bliss code...                            ...!                          EXTERNAL *                             VMS$GL_FLAVOR,                          ....   '           _____________________________ *           10.22.2  Other common C++ issues  B                    HP C++ (a separate compiler from HP C) providesC                    both symbol mangling and symbol decoration. Some E                    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 for D                    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" declaratione                    mechanism:   #                          extern "C"c                            {;                            extern int ExternSymbol(void *);i@                            extern int OtherExternSymbol(void *);                            }  I                    Also see Section 14.7 for information on /ARCHITECTURE &                    and /OPTIMIZE=TUNE.  H                    See Section 10.15 for information on the C system and>                    the lib$spawn call in CAPTIVE environments.  J                                                                      10-23    t          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:d                          i = i++;r"                        a[i] = i++;)                        foo( i, i++, --i);c  I                    are undefined and can have (adverse) implications when I                    porting the C code to another C compiler or to another I                    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":sF                    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 function J                    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 do 4                    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 and F                    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:r  9                    $ CC sourcea+SYS$LIBRARY:SYS$LIB_C/LIB_  I                    You can also define DECC$TEXT_LIBRARY to reference theu                    library.   C                    You will want to review the Programming Concepts H                    manual, and specifically take a quick look at Chapter                    21.                      10-24 i  o          2                    OpenVMS Programming Information        G                    And some general background: the STARLET definitionsiG                    (and thus the sys$starlet_c.tlb library) contain theWF                    symbols and the definitions that are independent ofE                    the OpenVMS version. The LIB definitions (and thusoF                    sys$lib_c) contain symbols and definitions that canI                    be dependent on the OpenVMS version. You won't need toTI                    rebuild your code after an OpenVMS upgrade if you haveaH                    included definitions from STARLET. The same cannot beI                    said for some of the definitions in LIB-you might needrG                    to rebuild your code. (The UCB structure can and hassB                    changed from release to release, for instance.)  I                    Recent versions of C automatically search sys$starlet_cD                    c.tlb. Explicit specification of sys$lib_c.tlb is                    required.  E                    Also see the Ask The Wizard website topics (2486),c&                    (3803), and (1661):  :                    o  http://www.hp.com/go/openvms/wizard/  D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the availableiB                    ATW Wizard.zip archive, please see Section 3.8.  A                    See Section 9.5 for information on the C off_tkH                    limitations, resolved in OpenVMS V7.3-1 and later andG                    in ECO kits available for specific OpenVMS releases.iI                    The use of a longword for off_t restricts applicationsiG                    using native C I/O to file sizes of two gigabytes or-I                    less, or these applications must use native RMS or XQPL1                    calls for specific operations.   D           __________________________________________________________<           10.23  Status of Programming Tools on OpenVMS VAX?  G                    DECthreads V7.3 and the HP C compiler (also known as E                    Compaq C and DEC C) V6.4 are presently expected to E                    be the last updates and the last releases of thesewH                    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 willeE                    continue to be available on OpenVMS VAX. The VAX C H                    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.  J                                                                      10-25 e             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.  D           __________________________________________________________@           10.24  Choosing a Version Number for Application Code?  G                    One of the common rules-of-thumb used for choosing a I                    displayed version number string for a new version of a G                    layered product or an application, its implications, F                    and its expected effects on client applications and"                    users, follows:  G                    o  No functional and no application-visible changes,sC                       bugfixes only-the edit number is incremented.eI                       These tend to be very small, very isolated, or ECO- H                       level changes. These can also be distributions forG                       specific hardware configurations or platforms, as J                       is the case with an OpenVMS Limited Hardware ReleaseG                       (LHR). Application rebuilds are not expected, and G                       there is an assumption that general user-provided H                       application-related regression testing will not be                       required.c  B                    o  Minimal functional and very few user-visibleJ                       changes-the maintenance number is incremented. TheseF                       tend to be very small or even ECO-level changes,G                       though somewhat larger than an edit-level change.bI                       Application rebuilds are not expected, and there isAJ                       an assumption that user-provided application-related>                       regression testing will not be required.  D                    o  Various small and upward-compatible functionalF                       changes-the minor version number is incremented.J                       The changes are user-visible, and are intended to beJ                       user-visible. Application rebuilds are not expected.H                       Some application programmers may choose to perform'                       regression tests.   D                    o  Large and/or potentially incompatible changes-C                       the major version number is incremented. SomehD                       applications might need to be rebuilt. VariousD                       application programmers will choose to performH                       regression tests of their respective applications.                      10-26 s  e          2                    OpenVMS Programming Information        E                    For additional version-numbering materials and foreF                    information on assigning module generation numbers,G                    please see the OpenVMS (POLYCENTER) Software ProducteH                    Installation Utility-variously refered to by acronymsE                    including PCSI and SPIA-reference manual available 8                    within the OpenVMS documentation set.  A                    Of course, all of this is obviously subject to F                    interpretation, particularly around the distinctionF                    between large and small changes and such. The scaleE                    of the application is also a factor, as larger and E                    more complex applications will tend toward smaller I                    increments and will tend to see the maintenance number J                    incremented, while new releases of smaller applicationsJ                    will tend to see the minor version incremented somewhat#                    more frequently.   I                    The goal of all this is to provide a guide to relative F                    scale of changes and the associated effort involvedH                    in an upgrade for the user and/or for the application                    programmer.  D           __________________________________________________________4           10.25  Selecting a Process Dump Directory?  E                    You can customize the device and directory for theeI                    process dump by defining the logical names SYS$PROCDMP D                    and SYS$PROTECTED_PROCDMP. The former is for non-E                    privileged dumps, while the latter is the location @                    where privileged image dumps are written, andI                    preferably an area protected against untrusted access.c                    For example:A  5                    $ define SYS$PROCDMP SYS$ERRORLOG:(E                    $ define /exec SYS$PROTECTED_PROCDMP SYS$ERRORLOG:S  I                    The abouve presumes that the SYS$ERRORLOG logical name .                    points to a valid location.  H                    There is presently no means to change the name of theF                    generated dump file from IMAGENAME.DMP to somethingD                    else. Accordingly, you will want to use differentD                    target directories for this purpose, particularlyC                    if there is more than one application or processb5                    potentially writing process dumps.   J                                                                      10-27 L  T          2                    OpenVMS Programming Information      D           __________________________________________________________-           10.26  Access to Itanium Assembler?L  @                    If you are interested in accessing the nativeE                    Intel Itanium assembler within the OpenVMS I64 GNVeG                    environment-and since the iasi64 assembler is a Unix I                    program and GNV is a Unix environment for OpenVMS I64-tE                    you can simply copy iasi64.ext into your gnu:[bin]o@                    directory in place of "as.", and of "AS.EXE".  I                    Alternately and probably also better, you can write ansG                    "as." script to invoke the iasi64.exe image from its D                    particular prefered location on the local system.  :                    A typical "as." script looks like this:  1                    path/iasi64.exe $1 $2 $3 $4 $5                                                                             10-28 F  a                    J                    _______________________________________________________             11       DECwindows       D           __________________________________________________________A           11.1  How do I let someone else display something on my                  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 cannI                    select the host node, username, and tranport that will F                    allow you to launch an application that targets the'                    workstation display.t  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-windowsSC                       "display" correctly on the remote host. For aLJ                       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 -aJ           ___________________/TRANSPORT=TCPIP/SERVER=server/SCREEN=screen_  E                    o  If you have verified the command is correct andUG                       things are still not working, ensure the Security F                       settings on the OpenVMS host side will allow the  J                                                                       11-1 _  _                              DECwindows         G                       incoming connection: Pull down the "Options" menu J                       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 toI#                       add an entry.e  I                      o  There are various transports available, includingnF                         LOCAL, DECNET, LAT, and TCPIP. You must SelectA                         the transport appropriate to the incomingh#                         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, G                         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 uselC                         a full domain name (e.g. Node.Subd.Domain). C                         However, you may have to use the IP address C                         itself, if your host does not have a way to D                         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 host E                         name and one that specifies the host address.h  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 beenl>                         activated for use with DECwindows. SeeG                         Section 11.14 for details of configuring TCP/IPB'                         as a transport.n  G                    o  There is a log file created in SYS$MANAGER: whichhC                       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-2o d  t                              DECwindowsa        I                       have found this file to be very useful for trackingdF                       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?   I                    To create a display from an OpenVMS host to a remote X J                    Windows display, use one of the following DCL commands:  S                    $ SET DISPLAY /CREATE /TRANSPORT=net_transport /NODE=remote_node I                    $ 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.14.e  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?   E                    Use the undocumented SHOW DISPLAY/SYMBOL, and then I                    reference the symbols DECW$DISPLAY_NODE, DECW$DISPLAY_ C                    SCREEN, DECW$DISPLAY_SERVER and/or DECW$DISPLAY_                     TRANSPORT.b  A                    An example of calling the underlying (and alsobF                    undocumented) sys$qio programming interface for the4                    WSDRIVER (WSAn:) is available at:  9                    http://www.hp.com/go/openvms/freeware/   H           Look in the Freeware V4.0 directory /srh_examples/DECUS_UNDOC_           CLINIC/.    J                                                                       11-3 i  r                              DECwindowsI      D           __________________________________________________________8           11.4  How do I get a log of a DECterm session?  H                    If you are working from a DECwindows DECterm terminalF                    emulator, you can use the AutoPrint feature. ChooseJ                    the "Printer..." menu item from the "Options" menu, setG                    the printing destination to the name of the file you G                    want, and set "Auto Print Mode". You are now free to                     continue.  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 seee9                    exactly what was originally displayed.   E                    You can also use the "Print Screen" screen capture H                    available in the DECwindows session manager menus, ifJ                    you simply wish to snapshot a particular portion of the%                    X Windows display.e  I                    If you are using the Freeware VTstar terminal emulatoreH                    package, you will find a similar logging mechanism is*                    available in the menus.  D           __________________________________________________________5           11.5  Why is DECwindows Motif not starting?t  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 a #                    graphics device:   D                    o  OpenVMS has failed to find the appropriate IRQC                       information for an EISA graphics card (on the G                       DEC 2000 series) such as the HP (Compaq) QVision,oG                       and did not autoconfigure it. Run the correct ECUsF                       (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)aH                       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 not D                       support it. (There are no other supported EISAJ                       graphics controllers, and EISA graphics are normally                      11-4n                                   DECwindowsr        F                       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  Radeon 7500   8                      o  PowerStorm 3D30, PowerStorm 4D20  )                      o  3DLabs Oxygen VX1e  I                       See Section 5.16 for further information on some of 1                       these graphics controllers.   C                    o  You have booted the system minimally, or have E                       otherwise disabled the device autoconfigurationr                       process.  <                    If there is a G* graphics device present:  ?                    o  There may have been a severe error in the >                       DECwindows startup. Type the contents ofA                       SYS$MANAGER:DECW$SERVER_0_ERROR.LOG for anyo@                       information on errors starting the server.  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 istE                       not particularly reliable as DECwindows can nowb-                       "correct" this setting.   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:g  G                       $ DEFINE/SYSTEM/EXEC DECW$IGNORE_WORKSTATION TRUEs  G                    o  You may not have a valid DECwindows Motif licensesG                       loaded. To check for the two most common types of F                       Motif product authorization keys (PAKs), use the-                       following DCL commands:   2                       $ LICENSE LIST DW-MOTIF/FULL6                       $ LICENSE LIST NET-APP-SUP*/FULL  J                                                                       11-5 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: Mon, 11 Apr 2005 19:51:30 GMT # From: hoff@hp.nospam (Hoff Hoffman) < Subject: OpenVMS Frequently Asked Questions (FAQ), Part 7/111 Message-ID: <6zA6e.3490$IL.1872@news.cpqcorp.net>    Archive-name: dec-faq/vms/part7  Posting-Frequency: quarterly Last-modified: 11 Apr 2005 Version: VMSFAQ_20050411-07.TXTc                                   DECwindowsb        F                       and examine the information displayed. Make sureF                       that one of these licenses is present, valid and                       active.R  E                       For information on registering software licensel@                       product authorization keys (PAKs) when youE                       cannot log into the system directly, please seel$                       Section 5.6.2.  E                    o  Check that the DECW$PRIVATE_SERVER_SETUP.COM isEE                       correct for the graphics controller in use. Fore                       instance:u  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] orsG                       in SYS$COMMON:[SYSMGR] as appropriate; the formeroC                       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.11. Details of the PowerStormtI                       3D30 and 4D20 settings are available in the OpenVMSc*                       Ask The Wizard area.  D           __________________________________________________________;           11.6  How do I set the title on a DECterm window?   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, J                    use the following control sequences, where <esc> is theJ                    ANSI escape code, value decimal 27, and "text label" is,                    what you want to display:  G                    To set the DECterm title, send the escape character, J                    then the characters "]21;", then the text label string,G                    and then an escape character followed by a backslash                     character.                       11-6o m  g                              DECwindowsp        I                    To set the icon label, send the escape character, thenaE                    the characters "]2L;", then the icon label string,nG                    and then an escape character followed by a backslashe                    character.r  E                    To set both the DECterm title and icon to the fullpG                    device name, you can use the following DCL commands:t             $  esc[0,7] = 27O           $  fulldevnam = F$Edit(F$GetDVI("TT","FULLDEVNAM"),"UPCASE,COLLAPSE") B           $  write sys$output esc+ "]21;" + fulldevnam + esc + "\"B           $  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.13.  D           __________________________________________________________J           11.7  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,H                    the DECwindows login screen background logo used (theG                    default is the DIGITAL, Compaq, or HP logo), variousfH                    keymaps (also see Section 11.7.2 and Section 11.7.1),C                    the FileView defaults, session manager defaults, G                    the DECwindows login processing, DECwindows log file,G                    processing, and various other DECwindows attributes,r(                    see the example file:  A                    $ SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.TEMPLATE   I                    This example template file is typically copied over to E                    the filename SYS$COMMON:[SYSMGR]DECW$PRIVATE_APPS_ D                    SETUP.COM and then modified to meet site-specific                     requirements.  I                    Additionally, various X tools such as xsetroot, bitmapsG                    and xrdb-some these can be useful in customizing theMJ                    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 DesktopiC                    Environment (CDE). You can select your preferredtE                    desktop (CDE or DECwindows Motif) when logging in,mB                    or you can change the default to the DECwindows  J                                                                       11-7 c                                 DECwindows         E                    Motif desktop using the DCL symbol decw$start_new_ F                    desktop in the DECwindows private application setupH                    command procedure. See SYS$MANAGER:DECW$PRIVATE_APPS_H                    SETUP.TEMPLATE for further details, and how to create/                    DECW$PRIVATE_APPS_SETUP.COM.P  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 usedI                    information such as that in the OpenVMS FAQ to set the                     root window.F  >                    To add a new backdrop to the DECwindows CDEC                    environment, the backdrop must first be in or be E                    converted into X11 pixmap format. (This conversion F                    is often possible using tools such as xv.) Then (ifC                    necessary) create the default backdrop directory F                    SYS$COMMON:[CDE$DEFAULTS.USER.BACKDROPS]. Place theH                    X11 pixmap file containing the desired image into theE                    backdrops directory, ensure that it has a filename G                    extension of .PM. (The xv default filename extension E                    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 findnF                    your image will be placed at the end of the list of'                    backdrops available.   F                    If you require a message be included on the initialG                    display-where the start session display and the logorJ                    appears-you can use either of the following approaches:  F                    o  The simplest approach requires OpenVMS V7.3-2 orC                       later, and the corresponding DECwindows V1.3- D                       1 kit or later. You will want to create a fileG                       named SYS$COMMON:[SYSMGR]DECW$GREET.TXT, and thisPE                       will be displayed in a popup-with an OK button- G                       when the login box is displayed. This is intendedoD                       specifically for applications requiring such a                       display.                          11-8                                    DECwindows         C                    o  The second approach involves copying the file )                       XRESOURCES.DAT fromc  M                       SYS$SYSDEVICE:[VMS$COMMON.CDE$DEFAULTS.SYSTEM.CONFIG.C]              into the directory  K                       SYS$SYSDEVICE:[VMS$COMMON.CDE$DEFAULTS.USER.CONFIG.C]s  E           and editing the copy. Specifically, look for the following:   3                       Dtlogin*greeting.labelString:c  H                       The line is normally commented out, and by default*                       contains the string:  ,                       Welcome to %localhost%  G                       You can change this text to something akin to theu                        following:  <           Dtlogin*greeting.labelString:  Welcome to Heck \n\L           This is a Trusted System owned by the Rulers of the planet Zark\n\
           \n\m           We Come In Peace\n\            \n@           If you want Privacy, you've come to the wrong place\n\           \n  A                       The lines of text will be centered for you.v  F                       In most DECwindows versions, you will be able toI                       onbtain only about eight (8) lines of text. ChangesrH                       have been implemented in DECwindows V1.3 and laterG                       that permit up to about twenty-five (25) lines ofo                       text.   I                    The login logo is stored as an XPM bitmap image in thelg                    text file SYS$SYSROOT:[SYSCOMMON.CDE$DEFAULTS.SYSTEM.APPCONFIG.ICONS.C]DECDTLOGO.PM,n                    and it can be changed. Copy the file to SYS$SYSROOT:[SYSCOMMON.CDE$DEFAULTS.USER.APPCONFIG.ICONS.C]DECDTLOGO.PM, H                    as DECwindows upgrades can replace the system version                     of this file.  I                    On DECwindows V1.3-1 and later (and possibly on V1.3), H                    both DECwindows CDE and DECwindows Motif displays useI                    this logo file. On older releases, only the DECwindowseC                    CDE displays used this logo file, while the logo G                    used for the Motif login display was hard-coded into E                    the package and the only available override is the   J                                                                       11-9                                   DECwindows         H                    DECW$LOGINLOGO command procedure mechanism within theH                    customized, site-specific DECW$PRIVATE_APPS_SETUP.COM                    file.  G                    Look at the contents of the DECDTLOGO.PM file and atnF                    other *.XPM files and tools for additional details.  '           _____________________________ ;           11.7.1  How do I customize DECwindows keymapping?t  J                    Various keymaps can be implemented on OpenVMS and otherD                    X Windows systems, allowing the implementation ofE                    a Dvorak-style or other alternate keymappings. ForgE                    details, see the available X Windows documentationaG                    (this is the documentation associated with X WindowsnD                    itself, and not the product documentation for theB                    OpenVMS operating system nor for the DECwindowsC                    X Windows implementation) and see the DECwindowssA                    *.DECW$KEYMAP (text-format) files found in the 5                    DECwindows DECW$KEYMAP: directory.w  H                    For other keymapping information, see Section 11.7.2.  '           _____________________________WC           11.7.2  Why does the DELETE key delete forward instead of                    backward?e  I                    See the SET TERMINAL/BACKSPACE command on OpenVMS V8.2                     and later.   J                    This behaviour involves the Motif virtual key bindings.J                    When a Motif application starts, it looks at the vendorH                    string returned in the display connection informationI                    and attempts to match the string to a table of virtual,                    bindings.  @                    You can override the default bindings in yourG                    decw$xdefaults.dat file. Here is the entry you would_8                    make to get the default VMS bindings.                              11-10    3                              DECwindows         ,                    *defaultVirtualBindings:\*                     osfCancel :  <F11> \n\)                     osfLeft :  <Left> \n\ &                     osfUp  :  <Up> \n\+                     osfRight :  <Right> \n\ )                     osfDown :  <Down> \n\A0                     osfEndLine :Alt  <Right> \n\1                     osfBeginLine :Alt  <Left> \n\ ,                     osfPageUp :  <Prior> \n\-                     osfPageDown :  <Next> \n\r2                     osfDelete :Shift  <Delete> \n\.                     osfUndo :Alt  <Delete> \n\0                     osfBackSpace :  <Delete> \n\/                     osfAddMode :Shift  <F8> \n\ )                     osfHelp :  <Help> \n\1'                     osfMenu :  <F4> \n\ +                     osfMenuBar :  <F10> \n\ -                     osfSelect :  <Select> \n\ 1                     osfActivate :  <KP_Enter> \n\n1                     osfCopy :Shift  <DRemove> \n\ ,                     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.   G                    Also see the DECxterm directory of Freeware V5.0 for E                    details on connecting to OpenVMS from various UNIXo                    platforms.   H                    For other keymapping information, see Section 11.7.1.              J                                                                      11-11 e                                 DECwindowsf      D           __________________________________________________________<           11.8  Why doesn't XtAppAddInput() work on OpenVMS?  F                    Yes, XtAppAddInput()  does work on OpenVMS. The MITC                    definition of the X Windows call XtAppAddInput()e8                    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 the.)                    XtAppAddInput()  call.r  F                    On OpenVMS, the platform-specific arguments to thisG                    call include an event flag and an IOSB, as these areuI                    the traditional OpenVMS constructs used to synchronizehF                    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.b  E                    Here is some example code that covers calling thisd&                    routine on OpenVMS:                                        11-12                                   DECwindowsn        2                        m->InputID = XtAppAddInput(%                            m->AppCtx,o&                            m->InputEF,(                            m->InputIosb,-                            the_callback, 1 ); 1                        if ( !((int) m->InputID ))s                            {)                            XtAppErrorMsg(n)                                m->AppCtx,t/                                "invalidDevice", /                                "XtAppAddInput",n0                                "XtToolkitError",5                                "Can't Access Device",l/                                (String *) NULL,h3                                (Cardinal *) NULL );                             ...  D           __________________________________________________________J           11.9  Why do the keyboard arrow keys move the DECwindows cursor?  E                    Congratulations, you have just stumbled into "dead F                    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>a  D           __________________________________________________________;           11.10  Why does half my DECwindows display blank?   I                    This is likely a result of receiving an OPCOM or otherRE                    console message on a system that shares the systemsC                    console with the DECwindows graphics workstationv                    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-13                                   DECwindowso        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 in @                    SYS$STARTUP:DECW$PRIVATE_APPS_SETUP.TEMPLATE.  F                    On older releases, you can disable output using the                    following:6  =                    $ SET TERMINAL/PERMANENT/NOBROADCAST OPA0:n2                    $ DEFINE/USER SYS$COMMAND OPA0:"                    $ REPLY/DISABLE  I                    Also see Section 14.3.3.2, Section 14.17, and Also seeE                    Section 8.4,a  D           __________________________________________________________C           11.11  %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 loaded1  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:sysgeno!                       USE CURRENTe)                       SET WINDOW_SYSTEM 1 "                       WRITE ACTIVE#                       WRITE CURRENTe                       EXIT  -                       Then reboot the system.   H                    o  On OpenVMS Alpha, ensure the SYSMAN IO PREFIX LISTI                       is set correctly, and specifically ensure the DECW$ G                       prefix is included in the existing list. If it is 3                       not, you will need to add it:h                      11-14 c                                 DECwindowse        !           $ run sys$system:sysman            IO SHOW PREFIXI           IO SET PREFIX=(DECW$,*)   * = list returned by the show commande           IO AUTO/LOG            EXIT  F                    o  Ensure that the image SYS$SHARE:DECW$ICBM.EXE isG                       installed in memory. If it is not installed, then !                       install it:n  1           $ INSTALL LIST/FULL SYS$SHARE:DECW$ICBMe/           $ INSTALL REPLACE SYS$SHARE:DECW$ICBM )           $ EDIT SYS$MANAGER:SYCONFIG.COM_  4           $! The following line was added to install1           $! support for the Mach64 Graphics Card            $!/           $ 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, NotB                       graphics device found on this system", then:  1                      o  Boot the system as normal_  (                      o  Login as SYSTEM.  E                      o  Create the file SYS$COMMON:[SYSMGR]DECW$USER_dI                         AUTOCONFIG.DAT. Protection must permit world reade                         access.   H                      o  Add the following string on the very first line:  !           CLEAR_PFLAG = ISA_4BYTE   %                      o  Save the file   0                      o  Set the file protections  D           $ SET PROTECTION=W:RE SYS$MANAGER:DECW$USER_AUTOCONFIG.DAT  )                      o  Reboot the systemu  )                    Also see Section 11.5.t  J                                                                      11-15 e  t                              DECwindows       D           __________________________________________________________9           11.12  How can I reset the warning bell volume?A  J                    With DECwindows CDE drivers and ECOs starting with ECOsG                    for the DECwindows keyboard driver SYS$IKBDRIVER.EXE B                    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:I  2                    $ @decw$utils:decw$define_utils%                    $ xset b 1 100 100   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 in F                    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 onnH                    the pre-CDE desktops, and the volume controls are nowH                    incompatible with the current keyboard drivers. Hence#                    the use of xset.                               11-16    a                              DECwindowsy      D           __________________________________________________________=           11.13  How can I alter the DECwindows CDE backdrop?   H                    To select a separate backdrop to be displayed on each/                    screen using DECwindows CDE:S  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 requiredV                       screen  A                    o  Click on the Style Manager. This is the one E                       containing the mouse and ttt on the CDE toolbarD  0                    o  Now change the background.  D           __________________________________________________________A           11.14  How can I enable the DECwindows TCP/IP TransportS  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_ A                    TRANSPORTS in SYS$MANAGER:DECW$PRIVATE_SERVER_ E                    SETUP.COM to the appropriate local value, based onnJ                    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:  A           $ COPY SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE -_=           $_ SYS$COMMON:[SYSMGR]DECW$PRIVATE_SERVER_SETUP.COMA  D           __________________________________________________________G           11.15  Can I use DECwindows 1.2-* on OpenVMS V7.3-2 or later?m  *                    The short answer is no.  F                    OpenVMS Alpha V7.3-2 only supports DECwindows MotifF                    V1.3 and later. If you require DECwindows V1.2-6 orI                    earlier, then you are limited to operations on OpenVMSt5                    Alpha V7.3-1 and earlier releases.a  F                    The central technical reason involves depdendenciesJ                    among the parts of the X11 subsystem that are deliveredI                    with the base OpenVMS operating system including the X G                    Windows display server and the transport images, andI  J                                                                      11-17                                   DECwindowse        I                    the parts of the DECwindows product that are delivered H                    within the DECwindows installation kits including theD                    client libraries and the DECwindows applications.  H                    DECwindows V1.3 and later made substantial changes toH                    the transport layer, and these required correspondingI                    changes to both the associated client and server code.tI                    OpenVMS Alpha V7.3-2 includes the server and transportdE                    with the V1.3 modifications. These changes were inCH                    support of the upgrade of Xlib from X11R5 to X11R6.6,I                    and transport-level changes associated with support of 1                    the Kerberos and LBX features.n  J                    If you attempt to load DECwindows V1.2-6 images onto anG                    OpenVMS Alpha V7.3-2 or later system, the DECwindows F                    libraries will not function with with system imagesH                    and will particularly not function with the transport                    layer.b  D           __________________________________________________________2           11.16  How to add Fonts into DECwindows?  F                    The following assumes DECwindows V1.3-1 and OpenVMSJ                    Alpha V7.3-2 and later unless stated otherwise, and canG                    permit fonts of various formats to be added into the *                    DECwindows environment.  E                    The recommended location for user font files is toaC                    place them in the directories which are reservedo@                    for this purpose, typically located below the7                    SYS$COMMON:[SYSFONT.DECW] directory.f  8                    SYS$COMMON:[SYSFONT.DECW.USER_100DPI]7                    SYS$COMMON:[SYSFONT.DECW.USER_75DPI]   J                    The above are recommended for PCF files of 100 Dots PerE                    Inch (DPI) and of 75 DPI resolution, respectively.d  8                    SYS$COMMON:[SYSFONT.DECW.USER_COMMON]  E                    The above is recommended for other PCF files, such H                    as terminal (character cell) fonts, and fonts used by)                    specific applications.   :                    SYS$COMMON:[SYSFONT.DECW.USER_CURSOR16]:                    SYS$COMMON:[SYSFONT.DECW.USER_CURSOR32]                      11-18                                   DECwindowsa        9                    The above are recommended for cursors.   8                    SYS$COMMON:[SYSFONT.DECW.USER_SPEEDO]  7                    SPEEDO is recommended for SPD files.   :                    SYS$COMMON:[SYSFONT.DECW.USER_TRUETYPE]  B                    USER_TRUETYPE is recommended for TrueType (TTF)E                    fonts. Fonts placed in this directory should be inr0                    the "Windows / Linux" format.  H                    The directory will contain the font files themselves,B                    and a data file that describes each font in theH                    directory. This file is named DECW$FONT_DIRECTORY.DATJ                    or DECW$FONT_DIRECTORY_extension.DAT, where "extension"C                    is replaced by the type of font (100DPI, SPEEDO,d)                    TRUETYPE, TYPE1, etc.)   J                    Make sure that the file protection on the font files is:                    set to allow world access to the fonts.  D                    For example: to add TrueType fonts to DECwindows,I                    place the font files in SYS$COMMON:[SYSFONT.DECW.USER_                     TRUETYPE]  <                    A directory listing might look like this:  ;           Directory SYS$COMMON:[SYSFONT.DECW.USER_TRUETYPE]   Z           ARKOI8N.TTF;1                            46KB/48KB        5-MAR-1995 04:00:00.00Z           backstage.ttf;1                          55KB/56KB       19-JUL-2004 09:42:20.92Z           IDAutomationHC39M_Free.ttf;1             27KB/32KB       29-JUL-2003 11:25:48.00
           ...nZ           texsi.ttf;1                             133KB/136KB      25-MAY-2003 15:31:11.00Z           texw.ttf;1                              150KB/152KB      25-MAY-2003 15:32:33.00  *           Total of 37 files, 3.09MB/3.23MB  =                    The case of the filename is not important.   E                    TrueType fonts should be in Stream_LF file format.   F                    To generate the appropriate DECW$FONT_DIRECTORY.DATA                    file for most font formats, issue the command:t  ,                    $ FONTCOMPILER /DIRECTORY  J                                                                      11-19    E                              DECwindows         H                    The above may or may not operate with TrueType files,F                    and you will likely have to generate the DECW$FONT_F                    DIRECTORY_TRUETYPE.DAT file manually. A sample file                    follows:-             37O           BACKSTAGE.ttf -Grfonts-Backstage-bold-r-normal--0-0-0-0-p-0-iso8859-1Vd           IDAutomationHC39M_Free.ttf -IDAutomation-HC39M-medium-r-normal--0-0-0-0-m-0-misc-Barcode39L           SUSESerif-Bold.ttf -Suse-Suse-bold-r-normal--0-0-0-0-p-0-iso8859-1O           SUSESerif-Roman.ttf -Suse-Suse-medium-r-normal--0-0-0-0-p-0-iso8859-1 O           SUSESans-Bold.ttf -Suse-Suse-bold-r-normal-sans-0-0-0-0-p-0-iso8859-1 V           SUSESans-BoldOblique.ttf -Suse-Suse-bold-o-normal-sans-0-0-0-0-p-0-iso8859-1T           SUSESans-Oblique.ttf -Suse-Suse-medium-o-normal-sans-0-0-0-0-p-0-iso8859-1R           SUSESans-Roman.ttf -Suse-Suse-medium-r-normal-sans-0-0-0-0-p-0-iso8859-1X           SUSESansMono-Bold.ttf -Suse-Suse Mono-bold-r-normal-sans-0-0-0-0-m-0-iso8859-1
           ... S           MCTIMEBI.TTF -UOregon-MAC C Times-bold-i-normal--0-0-0-0-p-0-macedonian-0iT           MCTIMEI.TTF -UOregon-MAC C Times-medium-i-normal--0-0-0-0-p-0-macedonian-0  D                    The first line of this data file is the number ofF                    font file entries which follow. Each entry consistsG                    of the font file name, and a font description. TherehG                    are fourteen fields in the description, separated by.E                    hyphens (dashes, "-"). Fields may contain embeddedU)                    spaces. The fields are   F                    o  Foundry: the name of the company or person which(                       produced the font.  H                    o  Family: the name of the Typeface (what most people,                       will call the "font").  H                    o  Weight: How "heavy" the type appears. Normal fontsC                       are "medium" or "regular", variations includeo3                       "bold", "demi", "light", etc.   H                    o  Slant: "r" for regular, "i" for italic, or "o" for                       oblique.  J                    o  Width: "normal", "wide", "narrow", "condensed", etc.  F                    o  Style: normally left empty, it can also identifyG                       variations on a basic family such as "sans" (sans2G                       serifs; without the serif, the ending and usuallyiH                       pointed portion of the stroke). Fonts of different?                       styles can be grouped in the same family.d                      11-20 o  r                              DECwindows         G                    o  Sizes: the next four fields identify the size and H                       scale of individual characters for fonts that haveG                       fixed point sizes. For fonts which scale (such as >                       TrueType), the four fields are all zero.  H                    o  Spacing: "p" for proportional, "m" for monospaced,0                       or "c" for character cell.  F                       Note: although DECwindows can identify differentI                       spacings within a family, the author has found that J                       mixing monospaced and proportional fonts in the sameH                       family may cause some proportional font options toH                       not appear in a font selection menu within NotepadG                       (only). (A fix for this is expected in DECwindowsp&                       V1.5 and later.)  G                    o  The next field is always zero for TrueType fonts.t  J                    o  Character Set: the last two fields identify the nameI                       and version number of the character set representedaJ                       within the font. For many applications, these fields-                       are informational only."  H                    The next step is to update the list of fonts known to6                    DECwindows, using the xset utility.  1                    $ mc decw$utils:xset fp rehashm  D                    It is also possible to reset the font list to the                    default:_  2                    $ mc decw$utils:xset fp default  E                    This is useful if you need to recover from errors.   F                    The Notepad utility, normally available through theJ                    "Applications" menu in Session Manager, is a convenientA                    way to see if the font is available. Start the H                    application, select "Options", then select "Font...".E                    In the "Family (Foundry)" window, you will see the J                    list of fonts available. User-added TrueType fonts willJ                    normally be at the end of this list. Select the desiredF                    font family, then select the Size (dpi) (which willF                    always be 0(0) for TrueType fonts), and the variousJ                    font options (Weight, Slant, Width, etc.) should appearH                    in the next window. You should then be able to selectH                    the desired font and click <OK> or <Apply> to use it,A                    or <Cancel> to exit without changing the font.   J                                                                      11-21                                   DECwindowsu        H                    If you don't see all of the fonts you added, check toI                    see that the number at the beginning of the DECW$FONT_ I                    DIRECTORY*.DAT file is correct, that the files are set F                    to world (or appropriate) access, and that TrueType1                    fonts are in Stream_LF format.   G                    Some applications require entering a full font name,nC                    which will look like the font description entry.n  H                    Please keep in mind that not all applications can useD                    every font which may be available on your system.C                    For example, DECterm is designed to use families D                    of fonts specifically designed for character cellD                    applications. Other fonts (specifically TrueType)F                    may work erratically, and may result in an unusableC                    display. It is best to use only monospaced fonts B                    specifically intended for DECterm with DECterm.  F                    The SYS$COMMON:[SYSFONT.DECW.USER_TRUETYPE] doesn'tD                    exist on OpenVMS VAX V7.3 with DECwindows V1.2-6,E                    but the procedure above does appear to work if the F                    directory is created and the instructions above are                    followed.                                                              11-22 F                       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 beTG                    found in the OpenVMS I/O User's Reference Manual, innG                    the chapter on the terminal driver. The chapter alsouH                    includes details on the general format and content of#                    these sequences.   G                    Specific details on the escape and control sequences H                    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 ine0                    the DECwindows documentation.  C                    Examples of common escape and control sequences-pH                    those typically used by the OpenVMS screen managementB                    package-can be found in the OpenVMS system fileE                    SYS$SYSTEM:SMGTERMS.TXT. (This file can be queried I                    under program control using SMG$GET_TERM_DATA, and you B                    don't need to use all of SMG to use this call.)  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 keyboards G                    found on compatible terminals. (Though note that thesF                    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} isCG                    decimal code 155 and can be replaced by the sequencecH                    "{ESC}[" (without the quotes) particularly for seven-E                    bit operations, SS3 is decimal code 143 and can bedB                    replaced by "{ESC}O" particularly for seven-bitC                    operations. Older VT1xx series terminals and any F                    other terminals operating with seven-bit characters  J                                                                       12-1               ,                    Miscellaneous Information        G                    should not be sent eight-bit operators such as {CSI}                     and {SS3}.   5           PF1={SS3}P PF2={SS3}Q PF3={SS3}R PF4={SS3}S K           KP0={SS3}p KP1={SS3}q KP2={SS3}r KP3={SS3}s KP4={SS3}t KP5={SS3}u S           KP6={SS3}v KP7={SS3}w KP8={SS3}x KP9={SS3}y KPCOMMA={SS3}l KPMINUS={SS3}maS           KPPERIOD={SS3}n ENTER={SS3}M DNARROW={CSI}B UPARROW={CSI}A LFARROW={CSI}DnR           RTARROW={CSI}C FIND={CSI}1~ INSERT={CSI}2~ REMOVE={CSI}3~ SELECT={CSI}4~S           PREV={CSI}5~ NEXT={CSI}6~ F6={CSI}17~ F7={CSI}18~ F8={CSI}19~ F9={CSI}20~sJ           F10={CSI}21~ F11={CSI}23~ F12={CSI}24~ F13={CSI}25~ F14={CSI}26~W           HELP={CSI}28~ DO={CSI}29~ F17={CSI}31~ F18={CSI}32~ F19={CSI}33~ F20={CSI}34~a  G                    An example of working with escape sequences (in DCL)U                    follows:G  #                    $ esc5m = "*[5m"s$                    $ esc5m[0,8] = 27#                    $ esc0m = "*[0m" $                    $ esc0m[0,8] = 27E                    $ write sys$output esc5m + "blinking text" + esc0mo  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 manuals                      available at:  +                    o  http://www.vt100.net/   E                    Information on the ReGIS graphics character set isr                     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/l  7                    Also see Section 11.6, Section 8.13._                      12-2     7          ,                    Miscellaneous Information      D           __________________________________________________________F           12.2  Does DECprint (DCPS) work with the LRA0 parallel port?                      No.  A                    The parallel printing port LRA0: found on many I                    OpenVMS Alpha systems is capable of some bidirectionaluH                    communications, with enough for basic operations with*                    most parallel printers.  E                    DECprint (DCPS) requires more than just the simple I                    handshaking provided by the LRA0: port, therefore DCPSD5                    does not work with the LRA0: port.   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.   D                    Tape media is different than disk media, as disksI                    have a known and pre-determined fixed capacity. ModernvJ                    disks also appear logically perfect, based on bad blockI                    revectoring support and the extra blocks hidden withinhG                    the disk structure for these bad block replacements.h  C                    The capacity of tape media is not nearly as pre- I                    determined, and the capacity can vary across different B                    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 and C                    uncorrectable media errors that might occur, theiI                    numbers and sizes of the inter-record gaps and related F                    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.   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.)   +                    Assuming no compression: >                    4 GB media / 575 KB saveset = 7294 savesets  J                                                                       12-3 l  r          ,                    Miscellaneous Information        ,                    Assuming 1:2 compression:?                    8 GB media / 575 KB saveset = 14588 savesetsb  1                                              Note   G                       There are no inter-record gaps on DAT tapes. WheneF                       determining media capacity, you have to considerB                       these gaps with nine-track magtape media andC                       other formats with gaps. This is not the case D                       with DAT (DDS), as the format has no recordingC                       gaps. However, the block structure underneath F                       the variable length record recording is based onD                       a block size of circa 124 KB. Further, writingD                       doubles filemarks and such can cause a loss ofG                       up to the underlying block size. Thus even though C                       there are no inter-record gaps on DAT, largero6                       savesets are still usually best.  I                    The compression algorithms used on various devices arerG                    generally not documented-further, there is no way topF                    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, ofs                    course.  I                    A typical compression ratio found with "everyday" data 4                    is somewhere around 1:1.8 to 1:2.  1                                              Noten  @                       OpenVMS often uses the term COMPACTION forF                       compression control, as in the qualifier /MEDIA_(                       FORMAT=COMPACTION.  D           __________________________________________________________5           12.4  Correctly using license PAKs and LMF?   D                    If you have multiple LMF$LICENSE.LDB databases inE                    your OpenVMS Cluster, then each and every PAK must J                    be installed in each and every license database presentE                    in an OpenVMS Cluster. Even if you use /EXCLUDE or F                    /INCLUDE, you need to have a consistent set of PAKsG                    registered across all licensing databases present in '                    the OpenVMS Cluster.n                      12-4                ,                    Miscellaneous Information        G                    If your software license permits it, you can use theoC                    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 aspI                    when you receive a NOLICENSE error), use the followingm                     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 variousUH                    products can check for and can be enabled by multipleG                    license PAKs. You will want to deassign this logical_"                    name when done.  8                    Some of the more common license PAKs:  L             DECnet Phase IV:   DVNETRTG, DVNETEND, DVNETEXT, or NET-APP-SUP*L             DECnet-Plus:       DVNETRTG, DVNETEND, DVNETEXT, or NET-APP-SUP*3             TCP/IP Services:   UCX, or NET-APP-SUP*eC             OpenVMS Alpha:     OPENVMS-ALPHA and OPENVMS-ALPHA-USERe&             OpenVMS VAX:       VAX-VMS-             OpenVMS Galaxy:    OPENVMS-GALAXY 7             Cluster (Alpha):   VMSCLUSTER, NET-APP-SUP* 7             Cluster (VAX):     VAXCLUSTER, NET-APP-SUP*   A                    Various NET-APP-SUP (NAS) license packages are_I                    available, each with differing collections of productsyC                    authorized. See the various NAS Software ProductsD                    Description (SPD) documents for specific details.  9                    o  http://h18000.www1.hp.com/info/spd/   H                       OpenVMS typically uses SPD 25.01.xx, SPD 41.87.xx,'                       and SPD 82.35.xx.n  C                    To determine which license PAK is failing (via aFI                    license check failure OPCOM message), use the command:.  K                    $ DEFINE/SYSTEM/EXECUTIVE LMF$DISPLAY_OPCOM_MESSAGE TRUE   J                                                                       12-5               ,                    Miscellaneous Information        ?                    Realize that defining this logical name willCA                    cause license checks that are otherwise hiddentE                    (unimplemented, latent, or part of a check for anymG                    of a series of licenses) to become visible. In otheriE                    words, expect to see zero or more spurious license G                    check calls when you define this, in addition to the 4                    check for the particular license.  F                    For information on PAKGEN and on generating licenseE                    PAKs, please see Section 10.10. For information on F                    obtaining commercial and hobbyist licenses, and forJ                    additional adminstrative information on LMF, please see3                    Section 2.8.4 and Section 2.8.1.,                                                                                  12-6e v  h                    J                    _______________________________________________________  -           13       Finding and using Software       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/  J                    o  The OpenVMS Freeware is is distributed with OpenVMS,J                       and is also available for download at various sites,.                       including the following:  >                      o  http://www.hp.com/go/openvms/freeware/  /                      o  ftp://ftp.montagar.com/   7                      o  ftp://mvb.saic.com/freewarev40/i  B                       and at various other sites. The website alsoD                       includes various updates and new packages thatE                       become available after the CD-ROM distributions "                       are created.  E                       Submissions to the OpenVMS Freeware can be made                        via:  >                      o  http://www.hp.com/go/openvms/freeware/  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-H8I  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 includeG                       ZIP and UNZIP and GZIP (please see Section 13.11,.I                       MMK (make), PINE, PERL, TAR, UUENCODE and UUDECODE. E                       Many other tools are available on the Freeware.a  J                                                                       13-1    i          -                    Finding and using Software_        A                    o  The UUENCODE and UUDECODE tools and various F                       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.)t  D                    o  OpenVMS software (formerly at Western KentuckyG                       University (WKU) is now available via Madgoat andb4                       via Process Software archives:  A                      o  http://www.process.com/openvms/index.htmlI  /                      o  http://www.madgoat.com/   B                    o  The FILESERV packages are also available via)                       anonymous FTP from:e  ;                      o  ftp://ftp.process.com/vms-freeware/   C                      o  ftp.process.com, under [.WKU.VMS.FILESERV].n  5                      o  ftp.vms.stacken.kth.se, under 4                         [.MIRRORS.WKU.VMS.FILESERV].  E                      o  ftp.ctrl-c.liu.se, under [.WKU.VMS.FILESERV].   '                      o  ftp.riken.go.jpa  G                      o  ftp.vsm.com.au, under kits and kits/decwindows.   C                      o  ftp.vsm.com.au, via the WWW instead of FTP.e  E                       The packages are also available via e-mail from F                       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, withn6                       software and other pointers, at:  4                      o  http://www.levitte.org/~ava/  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:   =                      o  http://nchrem.tnw.tudelft.nl/openvms/                       13-2  p  i          -                    Finding and using Softwaree        G                    o  The Kermit file transfer package is available at:c  7                      o  http://www.columbia.edu/kermit/t  2                      o  ftp://kermit.columbia.edu/  -                    o  ZMODEM is available at:k  7                      o  ftp://ftp.cs.pdx.edu/pub/zmodem   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 ispJ                       licensed from Omen Technology. (This package is alsoJ                       available on various of the Freeware distributions.)  C                    o  A good source of software for OpenVMS systems F                       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/e  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 OSU                         webserver:  .                      o  http://kcgl1.eng.ohio-9                         state.edu/www/doc/serverinfo.htmlS  <                    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:   3                      o  http://www.free.lp.se/fish/   E                       SSH V2 support is included with TCP/IP ServicesOJ                       V5.4 and later, and support is likely also available=                       within available third-party IP stacks._  J                                                                       13-3 i  w          -                    Finding and using Software         H                       For information on the SSH key file configuration,?                       see topic 151.22 and following in the VMSr>                       notes conference on the Deathrow ClusterC                       (deathrow.vistech.net and openvms-rocks.com).n  B                       Information on OpenSSL (SSLeay) for OpenVMS:  6                      o  http://www.free.lp.se/openssl/  3                      o  http://www.free.lp.se/fish/   H                       Information on OpenSSL (SSLeay) and OSU Web server%                       interoperation:r  @                      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 SecureaI                       Web Browser (CSWB) kit is a packaged version of thee6                       Mozilla.org Mozilla Web Browser.  I                    o  A port of the NCSA Mosaic web browser that supportsfG                       TCP/IP Services, Multinet and SOCKETSHR/NETLIB isg%                       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 are #                       available at:e  O                      o  http://www.openvms.compaq.com/ebusiness/Technology.html   /                      o  http://www.mozilla.org/n                      13-4     e          -                    Finding and using Software         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:m  -                      o  http://www.ipgpp.org/   ;                      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/h  B                    o  GNU Privacy Guard (GPG, GnuPG) is available.  C                       Search the comp.os.vms newsgroup archives for1C                       information regarding GnuPG; the source code, G                       binaries for various platforms, and documentation +                       are all available at:e  -                      o  http://www.gnupg.org/O  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 OpenVMSfH                       Alpha, but an investigation of an OpenVMS VAX port8                       is reportedly under consideration.  G                    o  An archive of the CENA DECwindows, X Windows, andOI                       VMS software packages can be found at the followingw                       sites:  0                      o  http://decwarch.free.fr/  6                      o  ftp://ftp2.cnam.fr/decwindows/  ;                      o  ftp://ftp.ctrl-c.liu.se/decwindows/e  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)  J                                                                       13-5 R  8          -                    Finding and using Software-        .                      o  ftp2.cnam.fr (MadGoat)  F                       ftp.x.org (in /contrib/vms) is effectively not aG                       mirror, but it does have various OpenVMS packages 2                       from the DECwindows archive.  H                       A list of the http mirror sites for the DECwindows.                       archive is available at:  Q                      o  http://axp616.gsi.de:8080/wwwar/cena/decwindows/cena.html   I                       Various of these packages are also available on the                        Freeware.   C                    o  ImageMagick is an X11 package for display andRE                       interactive manipulation of images. The packagemF                       includes tools for image conversion, annotation,D                       compositing, animation, and creating montages.E                       ImageMagick can read and write many of the moreeG                       popular image formats (e.g. JPEG, TIFF, PNM, XPM,d&                       Photo CD, etc.).  3                      o  http://www.imagemagick.org/e  F                       Versions of ImageMagick are also included on the                       Freeware.c  C                    o  XV is a image viewing and editing tool and is9%                       available from:-  6                      o  ftp://ftp.cis.upenn.edu/pub/xv  /                      o  http://www.sanface.com/9  A                      o  ftp://www-pi.physics.uiowa.edu/~dyson/xv/-  I                    o  Many software packages are available for displaying-E                       various bitmap files (.JPG, .GIF, .BMP, etc) onoG                       OpenVMS. Xloadimage, Xli, Xv, ImageMagick are theSG                       most common tools used under OpenVMS. Various webtD                       browsers such as Mozilla (qv) can also displayH                       various file formats on OpenVMS. You can find some?                       of these tools at the DECwindows Archive:o  I                      o  http://www.multimania.com/pmoreau/decw/index.htmlT  J                      o  http://www.multimania.com/pmoreau/decw/images.html                      13-6t n  e          -                    Finding and using SoftwareE        G                    o  GHOSTSCRIPT (gs) and GHOSTVIEW (gv) are availablei>                       from the Freeware V5.0 and Freeware V6.0$                       distributions:  >                      o  http://www.hp.com/go/openvms/freeware/  B                       Versions are also available on the Freeware.                         Also see:h  :                      o  http://www.cs.wisc.edu/~ghost/gnu/  G                    o  XPDF, a DECwindows viewer for PDF (Adobe Acrobat) /                       files, is available from:o  4                      o  http://www.foolabs.com/xpdf/  F                       Software and installation kits for XPDF are also0                       available on the Freeware.  H                       Beware: the XPDF tool included on OpenVMS FreewareG                       V4.0 is dated, and has been found to have variousiJ                       bugs. Use the Freeware V5.0 version of the XPDF kit,(                       or (better) later.  F                       A Java-based PDF viewer is available from Adobe,E                       and is known to operate on recent OpenVMS Alpha                        releases:t  -                      o  http://www.adobe.com/   E                    o  Various OpenVMS-related tools-both freeware and0F                       shareware-such as txt2pdf-are available from at:  /                      o  http://www.sanface.com/s  C                    o  The MPEG library version 1.1 is available fors.                       OpenVMS VAX and Alpha at  I                      o  ftp://ftp.x.org/contrib/vms/mpeglib-11-vms.readmeu  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.aF                       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                                                                       13-7 A  x          -                    Finding and using 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;eI                       the search modes are only "substring" [default] andsI                       "exact", and regex search is not supported (so FIND I                       EMACS will work, but FIND *EMACS* or FIND *EMACS*.* @                       will not). The search is case-insensitive.  G                       The maintainer of the site (stfp@roipb.cs.ipb.ro) F                       requests that anyone submit notifications of FTPJ                       servers with OpenvMS software that are not listed on                       the site.s  D                    o  The Levitte (extended :-) Family (and OpenVMS)                       website:  /                      o  http://www.levitte.org/   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_i$                         CONTENTS.TXT  =                    o  DJE Systems Website (David J. Dachtera)   ;                      o  http://www.djesys.com/freeware/vms/r  "                    o  Web Servers:  C                       Apache Web server (HP Secure Web Server (SWS,n&                       formerly 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/u  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.html                       13-8a s  a          -                    Finding and using SoftwareL        5                      o  http://www.kjsl.com/archives/r  C                      o  email list: VMS-WEB-daemon-Request@KJSL.COMt  %                       WASD Web server   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 PURVEYORo  9                       FastCGI software is available from:s  9                      o  http://www.DigitalSynergyInc.com/a  E                    o  CD-R (CD-Recordable) media tools are available,t-                       please see Section 9.7.   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.h  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/r  I                       A MIME tool is available in OpenVMS V7.2 and later.   D                       Also see the mmencode base64 encode and decode#                       available at:r  E                      o  http://nucwww.chem.sunysb.edu/htbin/software_T                          list.cgi  ?                    o  Menufinder (menu-driven system management #                       environment):   <                      o  http://www.itre.com/mf/download.html  J                                                                       13-9               -                    Finding and using Softwarec        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 availableo                       from:n  O                      o  http://seqaxp.bio.caltech.edu/pub/SOFTWARE/TCONTROL.ZIP   H                       UPShot web-based software for controlling a UPS is%                       available from:   <                      o  http://www.tmesis.com/apc/beta.htmlx  J                       OpenVMS software for controlling Liebert UPS devices=                       are available from the Liebert website:a  =                      o  http://www.liebert.com/apc/beta.htmlxs  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.zip)  H                    o  For tools to manage or to search your OpenVMS MAIL                        file, see:  U                      o  http://vms.process.com/scripts/fileserv/fileserv.com?MLSEARCHd  I                    o  AscToHTM attempts to convert any plain text file toiI                       HTML, while AscToTab restricts itself to files that H                       are plain text tables. (Versions are also availabe/                       on the OpenVMS Freeware).s  B                      o  http://www.jafsoft.com/asctohtm/index.html  B                      o  http://www.jafsoft.com/asctotab/index.html                      13-10 S             -                    Finding and using SoftwareP        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/~  >                      o  http://www.hp.com/go/openvms/freeware/  G                       To subscribe to the SAMBA-VMS mailing list e-mail E                       listproc@samba.org with no subject line and thef4                       following single line of text:  8                       subscribe samba-vms Your Full Name                         Also see:c  /                      o  http://lists.samba.org/   E                    o  The Perl language is available for OpenVMS, seen/                       Section 13.9 for details.   3                    o  XML is available for OpenVMS.   D                       Source code of an XML Parser is available from                       Oracle.l                         Also see:/  ;                      o  http://www.python.org/sigs/xml-sig/a  H                       An XML parser is available as part of OpenVMS V7.3                        and later.  G                    o  Python kit, and resource, and documentation sitesa                       include:  D                      o  http://www.pi-net.dyndns.org/anonymous/kits/  4                      o  http://vmspython.dyndns.org/  .                      o  http://www.python.org/  =                    o  GTK+ (The GIMP GUI Tookit) for OpenVMS:_  O                      o  http://www.openvms.compaq.com/ebusiness/Technology.htmlf  J                                                                      13-11 _             -                    Finding and using Softwarea        D                    o  The OpenVMS Porting Library now available, andG                       is intended to permit easier porting of C and C++i@                       applications from UNIX systems to OpenVMS:  O                      o  http://www.openvms.compaq.com/ebusiness/Technology.html.  ,                       GTK is also available.  /                    o  Mlucas (specialized FFT):s  @                      o  ftp://hogranch.com/pub/mayer/README.html  E                    o  Tools to monitor the terminals and the activity_E                       of other OpenVMS users (in addition to existingrF                       auditing capabilities in OpenVMS) are available.C                       Peek and Spy (Networking Dynamics) and Contrl G                       (Raxco) are two of the commercial packages, whileiE                       the freeware Supervisor package is available onf"                       OpenVMS VAX.  :                      o  http://www.networkingdynamics.com/  -                      o  http://www.raxco.com/e  )                    o  Python for OpenVMS:   .                      o  http://www.python.org/  4                       Also see the OpenVMS Freeware.  3                    o  Various packages for OpenVMS:d  L                      o  http://richj.home.mindspring.com/richware/index.html  H                      o  http://www3.sympatico.ca/n.rieck/links/cool_vax_                          vms.html  E                    o  TSM (Terminal Server Manager) is available via:   G                      o  http://www.compaq.com/support/digital_networks_ 6                         archive/servers/tsm/index.html  0                      o  Look at Freeware V5.0 at>                         http://www.hp.com/go/openvms/freeware/  G                      o  Beware: The TSM saveset shipped on the FreewarehA                         V5.0 disk media is known to be corrupted. C                         Download a new copy of the saveset from thesE                         Freeware V5.0 FTP server or from the Freewareo%                         V5.0 website.e                      13-12    B          -                    Finding and using Software         &                    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- =                         3.22/mysql-3.22.25-clients-vms.readme   E                       For additional information related to the mySQL C                       port, please search the comp.os.vms newsgroup E                       archives. A MySQL port is also available on the '                       OpenVMS Freeware.   >                      o  http://www.hp.com/go/openvms/freeware/  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 suchn                       as:   K                       $ SET FILE/PROTECT=(current_protection_mask) [...]*.*e  I                    o  A table listing translations between UNIX shell andsG                       OpenVMS DCL commands was posted to comp.os.vms byuJ                       Christopher Smith some time ago. This page should beC                       available from the google newsgroup archives.m  I                       For information on and the status of the OpenOfficet3                       port for OpenVMS, please see:   5                      o  http://www.oooovms.dyndns.orge  I                    o  The UNIX touch tool is available via various means:   5                       $ RENAME filename.ext;version *   M                      o  http://nucwww.chem.sunysb.edu/helplib/@hvmsapps/TOUCHp  B                       MadGoat FILE tool (see the MadGoat archives)  J                                                                      13-13 _  _          -                    Finding and using Software         :                    o  use /REVISION_DATE or /CREATION_DATE  =                    o  The DFU tool (see the OpenVMS Freeware)y                      o  The pair:n  ;           $ set file 'p1' /acl=(ident=[system],access=none) C           $ set file 'p1' /acl=(ident=[system],access=none) /delete   *                       $ SET FILE/VERSION=0  /                    o  The following touch hack:s  ,           $!   Command procedure SETDATE.COM           $!7           $!   Changes the DATES for an input file to a "           $!   file named OUTFILE.           $!$           $assign/nolog 'p1' outfile.           $convert/fdl=sys$input 'p1' outfile:           date            creation   01-apr-2010            expiration 01-Apr-2012            revision   01-Apr-2011           backup
           ...E  @                    o  The following RMS system service sequence:  B                      o  sys$open(),  with the XABRDT XAB structure                          chained.  E                      o  set the desired values within the XABRDT XAB.E  #                      o  sys$close()R  H                    Various OpenVMS tools and utilities are available at:  <                    o  http://wwwvms.mppmu.mpg.de/vmssig/src/  H                    OpenVMS ports of the xmcd and MPlayer tools have also.                    been reported as available.                        13-14 l             -                    Finding and using Softwaree      D           __________________________________________________________8           13.2  Where can I find UNIX tools for OpenVMS?  A                    There is an OpenVMS DCL and UNIX shell command .                    comparison table posted at:  E                    o  http://avmp01.mppmu.mpg.de/vmsdoc/UNIX_VMS_CMD_                        XREF.HTMLP  '           _____________________________ /           13.2.1  C system and library routines   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) E                    the DECW$EXAMPLES: and TCPIP$EXAMPLES (or prior to .                    V5.0, UCX$EXAMPLES:) areas.  '           _____________________________y2           13.2.2  X Windows utilities and routines  @                    Various X Windows utilities are available forG                    DECwindows. DECwindows is an implementation of the XuJ                    Windows environment and libraries, and provides variousF                    libraries, and provides various desktop interfaces,1                    including COE, Motif, and XUI.   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. F                    Examples include the older DWAUTH (X Windows SYSUAFG                    authorize-like tool) tool, various versions of grep, H                    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 OSUiJ                    HTTPD WWW server, a WWW gopher browser, etc. are all on6                    the various Freeware distributions.  J                                                                      13-15     --    N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faq3N  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.comr   ------------------------------  # Date: Mon, 11 Apr 2005 19:53:16 GMTn# From: hoff@hp.nospam (Hoff Hoffman) < Subject: OpenVMS Frequently Asked Questions (FAQ), Part 8/111 Message-ID: <MAA6e.3492$IL.1544@news.cpqcorp.net>e   Archive-name: dec-faq/vms/part8  Posting-Frequency: quarterly Last-modified: 11 Apr 2005 Version: VMSFAQ_20050411-08.TXTl               -                    Finding and using Softwaren      '           _____________________________p9           13.2.3  TCP/IP Tools and Utilities for OpenVMS?o  I                    TCP/IP Services (formerly known as UCX) contains toolswF                    such as ping, uuencode, smtp, snmp, rcp, nfs, tnfs,                    etc.   I                    OpenVMS V6.2 and later includes DCL-integrated supportoB                    for various IP tools, with commands such as SETE                    HOST/TELNET, and COPY/FTP. This interface requiresrJ                    the installation of an IP stack, and UCX V3.3 and laterE                    as well as any current third-party IP stack can beeG                    used. Once the IP stack is installed and configured,eJ                    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:.  '           _____________________________n$           13.2.4  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:   D                    o  http://www.clark.net/pub/dickey/vile/vile.html  #                    vim: vi improvede  2                    o  http://www.polarfox.com/vim/  '           _____________________________ '           13.2.5  The Emacs Text Editora  I                    OpenVMS ports of versions of the Emacs text editor can J                    be found on various OpenVMS Freeware distributions (eg:J                    Freeware V7 has a port of Emacs 21.2), and at web sites                    including:   H                    o  http://www.glug.org/people/ttn/software/emacs-for-                       vms/  C                    "Emacs isn't a text editor, it's a way of life."C                      13-16               -                    Finding and using Softwarer      '           _____________________________d#           13.2.6  Various GNU tools   E                    Information on the GNU on VMS (GNV) Project, which H                    aims to port GNU software (bash, flex, bison, etc) to,                    OpenVMS, is available at:  1                    o  http://gnv.sourceforge.net/c  !                    Software info:p  9                    o  http://vms.gnu.ai.mit.edu/software/   $                    Software archive:  @                    o  ftp://vms.gnu.ai.mit.edu/gnu-vms/software/  H                    Various GNU tools are also available on the Freeware.  '           _____________________________             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:R  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/f  I                    There are also updated header files for GCC on OpenVMSoH                    VAX that allow it to work with TCP/IP Sockets and the                    HP C RTL at:n  <                    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 forsF                    non-commercial users, and these and other tools areE                    available to commercial developers via the HP DSPP H                    partner program. (See Section 2.15 for information on                    DSPP.)e  J                                                                      13-17 V             -                    Finding and using Software.      D           __________________________________________________________6           13.3  What is the status of PL/I on OpenVMS?  G                    Kednos now owns and supports the former DIGITAL PL/I G                    compiler and run-time support on OpenVMS, and is the/E                    contact for product status, support and associated                     plans.t  C                    As of this writing, (older) versions of the PL/IiD                    run-time library and associated supporting imagesH                    remain available on OpenVMS VAX and on OpenVMS Alpha,G                    including the DECmigrate VEST translated images run-oI                    time support on OpenVMS Alpha, though neither the PL/InG                    shareable image nor the DECmigrate (AEST) translatedsD                    image support for the PL/I run-time are availableC                    (from HP) on nor present on OpenVMS I64 systems.eE                    Newer versions of the PL/I run-time library may be C                    (are?) available from Kednos for various OpenVMS:G                    platforms; please contact Kednos for product details $                    and availability.  +                    o  http://www.kednos.come  D           __________________________________________________________8           13.4  Where can I get the Mozilla Web Browser?  G                    Mozilla.org is an open source organization providing E                    HTML-related tools; software that is the basis for J                    various utilities including the Mozilla web browser and8                    the Secure Web Browser (SWB) package.  >                    OpenVMS Engineering is continuously portingJ                    Mozilla.org's web browser to OpenVMS, and OpenVMS portsE                    of the current Mozilla baselevels and releases areVG                    available. The OpenVMS Mozilla port includes the web I                    browser, the mail client, the Composer HTML editor, an H                    IRC chat client, a netnews (NNTP) reader, and various                    other tools.p  G                    The Mozilla web browser download and the development H                    and release schedules for this and for other Mozilla-2                    related tools are available at:  -                    o  http://www.mozilla.org/                       13-18 a  f          -                    Finding and using Softwaren        B                    The available Secure Web Browser (SWB) kit is aC                    packaged version of the Mozilla Web Browser, and(J                    typically the SWB version number matches the underlying#                    Mozilla version.w  C                    A hardware configuration appropriate for MozillaSE                    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.  <                    Mozilla is not available for OpenVMS VAX.  I                    Various versions of the Netscape Navigator web browser 6                    are based on the Mozilla code-base.  D           __________________________________________________________1           13.5  Where can I get Java for OpenVMS?   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 codezI                    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 doubles G                    around. Alternatively, extensive changes to the Java J                    source code to remove the assumption that the double is0                    an IEEE floating point value.  J                                                                      13-19               -                    Finding and using Software         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 foundt.                    to be inadequate. At best.)  G                    If Java2 or other environment lifts the requirementsvB                    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 remove/H                    the requirement for Display Postcript extensions, andF                    Java 1.2.2-3 is required with DECwindows V1.2-6 and                    later.n  H                    For additional information on Java for Alpha systems,I                    please see the OpenVMS documentation (V7.2 and later), *                    and the following site:  A                    o  http://www.compaq.com/java/alpha/index.html   E                    HP Secure Web Server (SWS, formerly CSWS) includestH                    CSWS_JAVA, which provides the following Apache TomcatC                    technologies: JavaServer Pages 1.1, Java ServletmE                    2.2, and MOD_JK. Also available is CSWS_PHP, a PHP/J                    implementation. (SWS is based on the Apache web server.                    See SOFT1.)  D           __________________________________________________________7           13.6  Obtaining user input in DCL CGI script?   E                    If you choose to use the GET method, then the formfG                    data is available in the DCL symbol QUERY_STRING, in &                    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:   .                    $ 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:o  H                    o  http://www.levitte.org/~ava/cgiscripts_other.htmlx                      13-20    n          -                    Finding and using Software         I                    DCL CGI is also discussed in the Writing Real ProgramsmB                    in DCL book, and in the Ask The Wizard website.  D           __________________________________________________________C           13.7  How can a batch job get its own batch entry number?k  I                    To have a batch procedure retrieve its own batch entryt-                    number, use the following:   8                    $ Entry = F$GETQUI("DISPLAY_ENTRY", -A                        "entry_number","display_entry","this_job")   H                    Remember that the entry numbers issued by the OpenVMSG                    Job Controller are always opaque longword values. DovF                    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. You 8                    should simply assume opaque longword.  D           __________________________________________________________=           13.8  How do I convert to new CMS or DTM libraries?a  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 no earlier version offG                    CMS can access the "converted" database, and corruptw                    it.)   C                    To perform the "conversion", issue the following/9                    commands for each CMS library present:   ;                    $ RENAME disk:[directory]00CMS.* 01CMS.* 9                    $ COPY NLA0: disk:[directory]00CMS.CMSd  E                    The new file 00CMS.CMS must have the same securitylH                    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).   J                                                                      13-21 e  s          -                    Finding and using Softwaren        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 the &                    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 additional #                    details on this.   F                    To perform the equivalent "conversion" for DEC TestJ                    Manager (DTM) V3.5 and prior versions to V3.6 and laterJ                    versions, issue the following DCL commands for each DTM#                    library present:   ;                    $ RENAME disk:[directory]00DTM.* 01DTM.* 9                    $ COPY NLA0: disk:[directory]00DTM.DTM   E                    Like CMS, this change is intended to prevent older F                    versions of DTM from accessing newer libraries, andH                    corrupting the contents. Like CMS, once the librariesE                    are renamed, they cannot and should not be renamed I                    back to the older names; like CMS, the changes are not '                    downward-compatible.t  G                    To convert version 1 (ancient) DTM and CMS librariescJ                    forward, please see the DTM CONVERT and the CMS CONVERT                    commands.  D           __________________________________________________________1           13.9  Where can I get Perl for OpenVMS?a  >                    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.                      13-22 c  e          -                    Finding and using Softwared        D                    A website useful for getting started with Perl onF                    OpenVMS-where you will find such things as downloadC                    links, instructions, auxiliary tools, and samplee+                    scripts-is available at:r  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:   @                    o  http://www.perl.com/CPAN/src/stable.tar.gz  G                    You will need GUNZIP and VMSTAR (both available from C                    the OpenVMS Freeware CD, or from other sites) to F                    unpack the archive; once you've done that, read the7                    instructions in the README.vms file.L  >                    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  <                    o  http://www.hp.com/go/openvms/freeware/  G                    During active Perl development cycles, test kits areo,                    sometimes found at: from:  *                    o  ftp://ftp.sidhe.org/  D                    Watch the mailing list (see below) for details on)                    experimental releases.   C                    Charles Lane maintains pages on how to write CGIWF                    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 implementlE                    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.tI                    The lock manager, RMS indexed files, screen managementaI                    utilities, and Intracluster Communication Services ares  J                                                                      13-23 c             -                    Finding and using Software         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 (aoA                    discussion forum for both user support and new B                    development), send an email message to vmsperl-%                    subscribe@perl.org   @                    The mailing list archives may be searched at:  F                    o  http://www.xray.mpe.mpg.de/mailing-lists/vmsperl  D           __________________________________________________________A           13.10  Obtaining the DECmigrate (AEST or VEST, and TIE)                   translator?  I                    The DECmigrate image translation family provides toolsmG                    that translate OpenVMS VAX images for use on OpenVMSrJ                    Alpha, and OpenVMS Alpha images for use on OpenVMS I64,,                    Details are available at:  Q                    o  http://h71000.www7.hp.com/openvms/products/omsva/omsva.html   E                    VEST is the name sometimes given to the DECmigrate D                    translation tool for VAX images, AEST is the nameF                    given to the Alpha translation tools, and TIE namesF                    the DECmigrate run-time environment within OpenVMS.G                    (If you've ever noticed images with filenames endingcJ                    with _TV and wondered what this meant, these images areJ                    part of TIE.) And yes, you can use AEST to re-translateJ                    images that were translated using VEST; you can perform7                    a second translation of a VAX image./  D                    Please see Section 13.12 for related information.F                    Please see the website for the most current detailsG                    on availability and plans and status of translations -                    for OpenVMS I64 platforms.t                              13-24               -                    Finding and using Software       D           __________________________________________________________F           13.11  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 associatedSI                    unzip tool to unpack it. You can get ZIP and UNZIP and F                    related and similar tools from the following areas:  <                    o  http://www.hp.com/go/openvms/freeware/  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.htmlxa  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 thew!                    e-mail server.   I                    Beware: The [000TOOLS...] pre-built versions of ZIP onrI                    the OpenVMS Freeware V4 CD-ROM will erroneously return H                    BILF errors on OpenVMS V7.2 and later. Use the sourceE                    on the Freeware V4 to rebuild the ZIP image(s), or J                    (better) acquire a far newer Zip kit from a more recentG                    Freeware, or elsewhere. The pre-built version of ZIP H                    on the Freeware V4 kit is older than the included ZIP4                    sources, and comparatively buggy.  B                    Directions for creating and using the sfx self-J                    extracting zip file compression mechanism are available9                    in the unzip kit that is available at:   :                    o  Look in a recent unzip* directory at<                       http://www.hp.com/go/openvms/freeware/  J                    o  With the UNZIP542 directory from Freeware V5.0, look0                       for the file UNZIPSFX.TXT.  H                    If you want to build the zip images for yourself (eg:F                    for an older OpenVMS version), pull over the entire8                    contents of a recent unzip directory.  <                    o  http://www.hp.com/go/openvms/freeware/  '                    and invoke LINK.COM.   J                                                                      13-25               -                    Finding and using Software         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.a  D           __________________________________________________________6           13.12  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/   0                    o  Bob Supnik's Trailing Edge4                       http://simh.trailing-edge.com/  E                    VAX emulators that operate on PC systems and/or onoG                    OpenVMS Alpha systems are available. For informationrD                    on an alternative to using a VAX emulator- on theH                    available DECmigrate VAX executable image translator-,                    please see Section 13.10.                                                  13-26    p                    J                    _______________________________________________________  '           14       Hardware Information0      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,G                    the OpenVMS VAX and OpenVMS Alpha platforms achieved I                    "feature parity". Subsequent work has seen significant/H                    enhancements and new features added on OpenVMS Alpha.I                    OpenVMS I64 started with "feature parity" with OpenVMSeC                    Alpha at the V8.2 release, and OpenVMS Alpha andeC                    OpenVMS I64 are based on and built from the same F                    source pool. (There are low-level platform-specificJ                    differences, and there is platform-specific code withinF                    the shared source code pool.) Most applications can.                    just be recompiled and run.  3                    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 it H                       is usually D_float. D_float is available on Alpha,E                       but D_float values are converted to G_float fornJ                       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 mayNF                       get different results. IEEE float types are also1                       available on OpenVMS Alpha.s  J                    o  The preferred floating point format on the Alpha and9                       on the IA-64 architectures is IEEE..  D                    o  Data alignment is extremely important for bestF                       performance on OpenVMS Alpha and on OpenVMS I64.G                       This means that data items should be allocated ataI                       addresses which are exact multiples of their sizes.hI                       Quadword alignment will offer the best performance,eG                       especially for character values and those smaller B                       than 32 bits. Compilers will naturally align  J                                                                       14-1    E          '                    Hardware Information         F                       variables where they can and will issue warnings:                       if they detect unaligned data items.  F                    o  HP C is the only C compiler HP offers on OpenVMSJ                       Alpha and on OpenVMS I64, and is a direct descendantE                       of Compaq C and DEC C on OpenVMS Alpha. HP C is F                       highly compatible with DEC C on OpenVMS VAX, butD                       does differ somewhat in its syntax and supportF                       when compared with the older VAX C compiler mostH                       OpenVMS VAX programmers are traditionally familiarF                       with. Read up on the /EXTERN_MODEL and /STANDARDG                       qualifiers to avoid the most common problems, and H                       see the documentation in the DEC C for OpenVMS VAXG                       manuals around migrating from VAX C to DEC C. (InaI                       addition to HP C, there have been open-source ports ;                       such as Gnu C available for OpenVMS.)E  A                    o  The page size on Alpha and IA-64 systems is E                       variable, but is at least 8 kilobytes. This can D                       have some effect on applications which use theI                       $CRMPSC system service as well as on the display of H                       available memory pages. The page size is availableE                       from $GETSYI using the SYI$_PAGE_SIZE itemcode.   C                    There are also a number of manuals which discuss J                    migration to OpenVMS Alpha and to OpenVMS I64 availableA                    in the OpenVMS documentation, both in the main I                    documentation and (depending on the age of the manuals C                    involved) in the archived documentation section.   B                    As mentioned earlier, more recent OpenVMS AlphaC                    and OpenVMS I64 releases have added features and0I                    support that are not available on OpenVMS VAX. Salient 3                    additions include the following:2  H                    o  64-bit addressing in OpenVMS Alpha V7.0 and later,)                       and on OpenVMS I64.   J                    o  Multi-host SCSI support (SCSI TCQ) in V6.2 and later  6                    o  PCI support (platform-dependent)  J                    o  OpenVMS Galaxy (vPars) support in OpenVMS Alpha V7.2                       and laterm                      14-2t o  l          '                    Hardware Information         >                    Please see Section 14.4.5 for Intel Itanium                    terminology.   D           __________________________________________________________C           14.2  Seeking performance information for Alpha (and VAX)_                 systems?  A                    HP makes a wide range of performance documentssE                    available through its FTP and WWW Internet servers %                    (see Section 3.2).   H                    The following contain information on Integrity, AlphaE                    and VAX products, with the VAX information largely E                    accessable via archive-related links at the Alpha-e-                    related product web pages:   2                    o  http://www.hp.com/go/server/  F                    o  http://www.compaq.com/alphaserver/vax/index.html  H                    The following sites are reachable via the AlphaServerH                    information pages, and contain information on various2                    retired VAX and Alpha products:  J                    o  http://www.compaq.com/alphaserver/archive/index.html  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 AlphauE                    consoles, and details related to console commands,s<                    serial lines, and configuration settings.      J                                                                       14-3 p  )          '                    Hardware Information       '           _____________________________ G           14.3.1  What commands are available in the Alpha SRM console?e  H                    In addition to the normal BOOT commands and such (seeD                    Section 14.3.5.2 for some details) and the normalE                    contents of the console HELP text, operations such4I                    as I/O redirection and floppy disk access are possible -                    at the SRM console prompt:   A                    1  Format a FAT floppy, and insert it into the 0                       AlphaStation floppy drive.  I                    2  Perform the following at AlphaStation SRM Console :   -                          >>> show * > env.dat 1                          >>> show conf > conf.data;                          >>> cat env.dat > fat:env.dat/dva0o=                          >>> cat conf.dat > fat:conf.dat/dva0P  E                    3  You may use the SRM "ls" command to display thes-                       contents of the floppy.   0                          >>> ls fat:env.dat/dva01                          >>> ls fat:conf.dat/dva0t  C                    4  You can now transfer the FAT-format floppy tou%                       another system.   '           _____________________________n6           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 by I                    higher-level operating system or application software, I                    functions which may not be directly available in AlphalC                    hardware. PALcode is implemented using available D                    Alpha instructions and using the Alpha processor,E                    though PALcode operates in a mode which simplifiesvC                    programming. PALcode is also permitted access torE                    processor-specific and otherwise internal featurescG                    of a particular Alpha microprocessor implementation;/H                    microprocessor-specific features which are not easilyF                    accessable to operating system or application code.                      14-4  F  i          '                    Hardware Information_      '           _____________________________NJ           14.3.3  Alpha COM ports and VAX console serial line information?  E                    This section contains information on the Alpha COMeH                    communication ports, and related settings, as well asJ                    on the VAX console bulkhead and VAX console serial line                    connection.  '           _____________________________ E           14.3.3.1  Which terminal device name is assigned to the COMg                     ports?  D                    COM2 is normally TTA0:. COM1 is normally TTB0: ifG                    the Alpha workstation is booted with the SRM console H                    environment variable set to graphics, and is OPA0: if0                    the console is set to serial.  I                    On the DEC 2000 series (sometimes incorrectly known by J                    the name of the system as sold for Microsoft Windows NTG                    Alpha; as the DECpc 150 AXP series) on older OpenVMStG                    Alpha releases, COM1 through COM4 are known as OPA0:aH                    through OPA3:. On all current OpenVMS releases, theseG                    ports are serviced by the terminal driver and not by /                    the console OPDRIVER driver.w  J                    Often the easiest way to determine the OpenVMS terminalF                    name assigned to the port is to connect a terminal,G                    log in interactively, and look at the output of SHOWaG                    TERMINAL. (Device names can vary by OpenVMS version, E                    as well as by the SRM console environment variable                     selection.)  G                    For serial console hardware and related information,7G                    and for pin-outs and related information, please see 2                    Section 14.3 and Section 14.25.  '           _____________________________hJ           14.3.3.2  Which serial port is the console on the MicroVAX 3100?  G                    Just to keep life interesting, the MicroVAX 3100 hasoD                    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 F                    the results of the selftest in parallel with MMJ-1.I                    When the console is enabled to respond to BREAK, MMJ-3   J                                                                       14-5 a  b          '                    Hardware Information         I                    becomes the console port, and MMJ-1 will (confusingly) I                    output the results of selftest in parallel with MMJ-3.r  '           _____________________________bJ           14.3.3.3  How can I set up an alternate console on a VAXstation?  H                    Most VAXstation series systems and a few Alpha seriesI                    systems have a switch - most often labeled S3, largely.H                    for historical reasons-that enables one of the serialE                    lines as the system console device; as OPA0:. This J                    disables console output to the graphics display. (For a@                    related behaviour, please see Section 11.10.)  H                    All VAXstation 3100 series systems provide a S3 slideG                    switch, though the oldest may be missing the cut-out D                    through the enclosure that provides access to theJ                    switch. The slide switch is located near the diagnosticH                    LED display. (The slide switch is accessable with the"                    cover removed.)  G                    Various members of the DEC 3000 series Alpha systemseJ                    also have a similarly-labled S3 switch for selection of)                    the alternate console.   I                    The particular port that becomes the console can vary. G                    The printer MMJ connection is used on all VAXstation D                    3100 series. On VAXstation II, the console DB9 isI                    used, rather than the graphics display. On most (all?) I                    AlphaStation series systems, typically the COM1 serialT,                    port becomes the console.  >                    Also see Section 14.3.6, Section 11.10, andH                    Section 14.17. Beware the two different DB9 pin-outs;9                    see Section 14.26 for related details.   J                    For information on registering software license productG                    authorization keys (PAKs), please see Section 5.6.2.5  '           _____________________________eD           14.3.3.4  Please explain the back panel of the MicroVAX II  J                    The MicroVAX-series console bulkhead interface was usedF                    with the KA630, as well as with the KA650 and KA655                    processors.                      14-6u o  n          '                    Hardware Informationi        F                    There are three controls on the console bulkhead of!                    these systems:   <                      Triangle-in-circle-paddle: halt enable.@                        dot-in-circle: halt (<break>) is enabled,@                                       and auto-boot is disabled.E                        dot-not-in-circle: halt (<break>) is disabled,a?                                       and auto-boot is enabled.s  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, F                    and one for the S-box (BA2xx) series enclosure. TheI                    console bulkheads typically used either the MMJ serial G                    line connection, or the MicroVAX DB9 (not the PC DB9 D                    pin-out), please see the descriptions of these inE                    section Section 14.25. For available adapters, seeV!                    Section 14.26.i  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 organizationtF                    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 servicenF                    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 control.F                    from the console program to the (booting) operating                    system.          J                                                                       14-7 i  e          '                    Hardware Informationo      '           _____________________________y?           14.3.4  What are Alpha console environment variables?l  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,oB                    various default values for the operating systemE                    bootstrap, and related control mechanisms-in otherCF                    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:_  J                    AUTO_ACTION ("BOOT", "HALT", "RESTART", any other valueK                    assumed to be HALT),  BOOT_DEV, BOOTDEF_DEV, BOOTED_DEV,dH                    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.  B                    OpenVMS Galaxy (vPars) firmware can add consoleD                    environment variables beginning with such strings@                    as LP_* and HP_*, and each particular consoleI                    implementation can (and often does) have various sortstJ                    of platform-specific extensions beyond these variables.H                    These variables allow both vPars (virtual partitions)I                    and lPars and lPars (logical partition) support; vParsoE                    is a generic name for soft partitioning constructs H                    such as OpenVMS Galaxy, while lPars is a generic name;                    applied to hard partitioning constructs.   H                    The contents of a core set of SRM console environmentH                    variables are accessible from OpenVMS Alpha using theF                    f$getenv lexical and the sys$getenv system service.F                    (These calls are first documented in V7.2, but haveD                    been present in OpenVMS Alpha for many releases.)G                    Access to arbitary SRM console environment variables_I                    is rather more involved, and not directly available toOI                    application software operating outside of kernel-mode..                        14-8a m  o          '                    Hardware Information       '           _____________________________ 8           14.3.5  What are the boot control flag values?  F                    Integrity, VAX and Alpha primary bootstraps supportD                    flag values; a mechanism which permits the systemF                    manager to perform specific customizations or site-F                    specific debugging of the OpenVMS system bootstrap.B                    While very similar, there are differences among@                    the boot flag implementations for the various!                    architectures.   '           _____________________________a:           14.3.5.1  What are the I64 IPB boot flag values?  H                    The OpenVMS I64 primary bootstrap flags are processedD                    within the IA-64 primary bootstrap image IPB.EXE;A                    within the SYS$EFI.SYS structures. The primary E                    bootstrap boot flags are largely parallel to thosehE                    of OpenVMS Alpha (see Section 14.3.5.2, though the I                    console and the console mechanisms used to specify the I                    boot command, the boot flags, and boot command optionsM&                    do differ markedly.  H                    You can specify the boot flags via an EFI environmentJ                    variable VMS_FLAGS , or via the boot alias boot optionsF                    mechanism, or by appending the requested boot flags<                    onto the specification of VMS_LOADER.EFI.  I                    To set the bootstrap flags environment variable at the )                    EFI shell prompt, use:E  -                    Shell> SET VMS_FLAGS "0,1"   B                    When you register an EFI boot alias (please seeE                    Section 14.4.5 for Intel Itanium terminology), youeG                    will be asked if you want to enter boot options, andtG                    what type. To add boot flags to a boot alias, selectiJ                    Unicode as the boot options type, and enter an SRM-likeG                    options string, such as the conversational bootstrape5                    selected by the following example:                       -flages 0,1  G                    For related information on managing EFI boot aliases @                    from OpenVMS I64, please see Section 14.3.10.  J                                                                       14-9               '                    Hardware Informationt        G                    When using VMS_LOADER.EFI to request boot flags, you B                    will want to specify the invocation as follows:  5                    fsn:\efi\vms\vms_loader -flags 0,1   F                    The above shows a conversational bootstrap request.  ?                    Typical boot flags are listed in Table 14-1.M  J           ________________________________________________________________8           Table 14-1  I64 Conversational Bootstrap Flags  J                    _______________________________________________________J                    Bit_______Example_Mnemonic__________Description________  E                    0         0,1     CONV              Conversational @                                                        bootstrap  C                    1         0,2     DEBUG             Load SYSTEM_eI                                                        DEBUG.EXE (XDELTA)e  F                    2         0,4     INIBPT            Stop at initialI                                                        system breakpoints_  E                    16        0,10000 DBG_INIT          Enable verboseOI                                                        bootstrap messages   H                    17        0,20000 USER_MSGS         Enable additionalJ           _____________________________________________bootstrap_messages_  I                    For a conversational bootstrap of the OpenVMS I64 root G                    SYS4 associated with the fs2: EFI file system device B                    with full bootstrap messaging enabled, specify:  9                    fs2:\efi\vms\vms_loader -flags 4,30001n  '           _____________________________ <           14.3.5.2  What are the Alpha APB boot flag values?  J                    The flags listed in Table 14-2 are passed (via registerC                    R5) to the OpenVMS Alpha primary bootstrap image H                    APB.EXE. These flags control the particular behaviour$                    of the bootstrap.  &                    BOOT -FL root,flags                      14-10               '                    Hardware Information         J           ________________________________________________________________:           Table 14-2  Alpha Conversational Bootstrap Flags  J                    _______________________________________________________J                    Bit_____Mnemonic__________Description__________________  E                    0       CONV              Conversational bootstrap   B                    1       DEBUG             Load SYSTEM_DEBUG.EXE5                                              (XDELTA)   C                    2       INIBPT            Stop at initial systemeE                                              breakpoints if bit 1 set 8                                              (EXEC_INIT)  H                    3       DIAG              Diagnostic bootstrap (loads:                                              diagboot.exe)  J                    4       BOOBPT            Stop at bootstrap breakpoints>                                              (APB and Sysboot)  I                    5       NOHEADER          Secondary bootstrap does notwA                                              have an image header   @                    6       NOTEST            Inhibit memory test  A                    7       SOLICIT           Prompt for secondary ;                                              bootstrap file   D                    8       HALT              Halt before transfer to@                                              secondary bootstrap  A                    9       SHADOW            Boot from shadow set   ?                    10      ISL               LAD/LAST bootstrap   G                    11      PALCHECK          Disable PAL rev check halt   E                    12      DEBUG_BOOT        Transfer to intermediate >                                              primary bootstrap  ?                    13      CRDFAIL           Mark CRD pages badi  H                    14      ALIGN_FAULTS      Report unaligned data traps9                                              in bootstrapn  D                    15      REM_DEBUG         Allow remote high-level>                                              language debugger  I                    16      DBG_INIT          Enable verbose boot messagesV9                                              in EXEC_INITa  J                    17      USER_MSGS         Enable subset of verbose bootE                                              messages (user messages)-  F                    18      RSM               Boot is controlled by RSM  J                                                                      14-11 p  e          '                    Hardware Information_      J           ________________________________________________________________B           Table 14-2 (Cont.)  Alpha Conversational Bootstrap Flags  J                    _______________________________________________________J                    Bit_____Mnemonic__________Description__________________  J           _________19______FOREIGN___________Boot_involves_a_foreign_disk_  G                    If you want to set the boot flags "permanently", use74                    the SET BOOT_FLAGS command, e.g.:  +                    >>> SET BOOT_OSFLAGS 0,1t  '           _____________________________i:           14.3.5.3  What are the VAX VMB boot flag values?  D                    The flags described in Table 14-3 are passed (viaJ                    register R5) to the OpenVMS VAX primary bootstrap imageH                    VMB.EXE. These flags control the particular behaviour$                    of the bootstrap.  J           ________________________________________________________________8           Table 14-3  VAX Conversational Bootstrap Flags  J                    _______________________________________________________J                    Bit_____Mnemonic__________Description__________________  D                    0       CONV              Conversational boot. AtI                                              various points in the systemiJ                                              boot procedure, the bootstrapD                                              code solicits parameterE                                              and other input from the_F                                              console terminal. If DIAGH                                              is set, then the diagnosticH                                              supervisor should enter itsJ                                              menu mode and prompt user forA                                              the devices to test.o  H                    1       DEBUG             Debug. If this flag is set,F                                              OpenVMS VAX maps the codeI                                              for the XDELTA debugger intoxJ                                              the system page tables of the<                                              running system.                        14-12 e  .          '                    Hardware Informationu      J           ________________________________________________________________@           Table 14-3 (Cont.)  VAX Conversational Bootstrap Flags  J                    _______________________________________________________J                    Bit_____Mnemonic__________Description__________________  J                    2       INIBPT            Initial breakpoint. If RPB$V_F                                              DEBUG is set, OpenVMS VAXG                                              executes a BPT instruction G                                              immediately after enablingP5                                              mapping.   I                    3       BBLOCK            Secondary boot from the boot G                                              block. Secondary bootstrap H                                              is a single 512-byte block,J                                              whose LBN is specified in R4.  G                    4       DIAG              Diagnostic boot. SecondarytH                                              bootstrap is the DiagnosticH                                              Supervisor image; the imageD                                              [SYSMAINT]DIAGBOOT.EXE.  H                    5       BOOBPT            Bootstrap breakpoint. StopsF                                              the primary and secondaryF                                              bootstraps with an XDELTAI                                              breakpoint instruction priori@                                              to the memory test.  D                    6       HEADER            Image header. Takes theD                                              transfer address of theF                                              secondary bootstrap imageC                                              from that file's imageaH                                              header. If the RPB$V_HEADERI                                              bit is not set, the image isdE                                              assumed to have no image_C                                              header, and control is?I                                              transfered to the first byte H                                              of the secondary boot file.  H                    7       NOTEST            Memory test inhibit. Sets aG                                              bit in the PFN bit map for I                                              each page of memory present.tF                                              Does not test the memory.  G                    8       SOLICT            File name. VMB prompts foroD                                              the name of a secondary<                                              bootstrap file.  J                                                                      14-13 e  C          '                    Hardware Information       J           ________________________________________________________________@           Table 14-3 (Cont.)  VAX Conversational Bootstrap Flags  J                    _______________________________________________________J                    Bit_____Mnemonic__________Description__________________  B                    9       HALT              Halt before transfer.H                                              Executes a HALT instructionH                                              before transferring controlH                                              to the secondary bootstrap.  A                    10      NOPFND            No PFN deletion (noteE                                              implemented; intended toSH                                              tell VMB not to read a fileF                                              from the boot device thatG                                              identifies bad or reservedlF                                              memory pages, so that VMBI                                              does not mark these pages as F                                              valid in the PFN bitmap).  B                    11      MPM               Specifies that multi-F                                              port memory is to be usedF                                              for the total EXEC memoryI                                              requirement. No local memory,C                                              is to be used. This isoG                                              for tightly-coupled multi- J                                              processing. If the RPB$V_DIAGJ                                              bit is also enabled, then theI                                              Diagnostic Supervisor enters ?                                              its AUTOTEST mode.   F                    12      USEMPM            Specifies that multi-portE                                              memory should be used inaI                                              addition to local memory, asaH                                              though both were one single;                                              pool of pages.   B                    13      MEMTEST           Specifies that a moreH                                              extensive algorithm be usedI                                              when testing main memory for I                                              hardware uncorrectable (RDS) 4                                              errors.                          14-14    H          '                    Hardware Information       J           ________________________________________________________________@           Table 14-3 (Cont.)  VAX Conversational Bootstrap Flags  J                    _______________________________________________________J                    Bit_____Mnemonic__________Description__________________  F                    14      FINDMEM           Requests the use of MA780I                                              multiport memory if the maintI                                              MS780 memory is insufficientXC                                              for booting. This is arC                                              remnant of the supportEF                                              for the VAX-11/782 seriesF                                              system and its AsymmetricC                                              Multiprocessing (ASMP)aE                                              environment. Support for H                                              the VAX-11/782 and for ASMPH                                              was withdrawn with the V5.0H                                              release; with the advent ofF                                              Symmetric MultiprocessingJ           ___________________________________(SMP)_support._______________  C                    The exact syntax is console-specific, recent VAXs6                    consoles tend to use the following:  &                      >>> BOOT/R5:flags  '           _____________________________uB           14.3.6  How do I boot an AlphaStation without monitor or                   keyboard?   G                    The AlphaStation series will boot without a keyboard E                    attached. To use a serial terminal as the console, C                    issue the SRM console command SET CONSOLE SERIAL F                    followed by the console INIT command. Once this SRMD                    command sequence has been invoked and the CONSOLEJ                    environment variable is set to SERIAL, the Alpha systemE                    will use the serial terminal. (Set the environment4E                    variable to GRAPHICS to select the console display 4                    output via the graphics display.)  F                    The DEC 3000 series has a jumper on the motherboardE                    for this purpose. Various older Alpha workstationsPI                    generally will not (automatically) bootstrap without a H                    keyboard connected, due to the self-test failure thatA                    arises when the (missing) keyboard test fails.t  J                                                                      14-15 _  _          '                    Hardware Informationk        I                    The usual settings for the console serial terminal (or G                    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 systemoH                    consoles are capable of 57600 baud. See the COM2_BAUDI                    console environment variable, and ensure that you have 7                    current SRM firmware version loaded.   D                    The AlphaStation and AlphaServer series use a PC-H                    compatible DB9 serial connector for the COM1 and COM2H                    serial lines (and for the OPA0: console line, if thatH                    was configured via SRM), please see Section 14.25 for'                    details and pin-out.l  J                    For information on registering software license productG                    authorization keys (PAKs), please see Section 5.6.2.   @                    For a related behaviour of DECwindows, please<                    see Section 11.10. For information on theF                    VAXstation alternate console mechanisms, please see$                    Section 14.3.3.3.  '           _____________________________ =           14.3.7  Downloading and using SRM console Firmware?   E                    This section discusses downloading and using Alpha >                    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.htmle  G                    o  ftp://ftp.digital.com/pub/Digital/Alpha/firmware/   R                    o  ftp://ftp.digital.com/pub/Digital/Alpha/firmware/readme.html                      14-16 d             '                    Hardware Information         G                    The latest and greatest firmware-if updated firmware J                    has been released after the most recent firmware CD was-                    distributed-is located at:o  O                    o  ftp://ftp.digital.com/pub/Digital/Alpha/firmware/interim/   F                    For information on creating Alpha bootable floppiesI                    containing the firmware, and for related tools, pleasea+                    see the following areas:R  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.txtn  F                    The SROM firmware loader expects an ODS-2 formattedI                    floppy, see mkboot. As for which image to use, the ROMtG                    image uses a header and the file extension .ROM, andnE                    the SROM bootable floppy cannot use the .ROM file.n  G                    To check the firmware loaded on recent OpenVMS Alpha ,                    systems, use the command:  A                    $ write sys$output f$getsyi("console_version")sA                    $ write sys$output f$getsyi("palcode_version")h#                    SDA> CLUE CONFIGc  C                    Also see Section 14.3.7.2. For information on HPyE                    Integrity EFI firmware upgrades and for a sequenceeH                    useful in generating CD-R or CD-RW media containing aC                    firmware disk image, please see Section 14.3.11.w  '           _____________________________mF           14.3.7.2  How do I reload SRM firmware on a half-flash Alpha                     system?n  E                    Some of the AlphaStation series systems are "half-lI                    flash" boxes, meaning only one set of firmware (SRM or G                    AlphaBIOS) can be loaded in flash at a time. GettingiF                    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, F                    and then getting into the AlphaBIOS firmware updateH                    sequence, and then entering "update srm" at the apu->                    prompt.  J                                                                      14-17    n          '                    Hardware Information         J                    To shuffle the files, copy the target SRM firmware fileG                    (as200_v7_0.exe is current) to a blank, initialized,rG                    FAT-format floppy under the filename A:\FWUPDATE.EXEh  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.a  '           _____________________________rA           14.3.7.3  How do I switch between AlphaBIOS/ARC and SRMn                     consoles?   G                    The specific steps required vary by system. You must C                    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 thea1                    necessary SRM firmware loaded.c  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.l                      14-18 K  M          '                    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 aresG                    "half-flash" systems and do not support the presence_H                    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 networkaE                    download, or from a firmware CD-ROM. Following thehF                    normal AlphaBIOS or ARC firmware update sequence toG                    the APU prompt, and then explictly select the targetlF                    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-c'                        Apu-> update ARC #                        Apu-> verify !                        Apu-> quits-                        Power-cycle the systema  I                    Use the following sequence to specifically update (andrI                    load) SRM from AlphaBIOS/ARC on a "half-flash" system:o  '                        Apu-> update SRMi#                        Apu-> verifyX!                        Apu-> quite-                        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:s  *                        >>> b -fl 0,A0 ddcu7                        BOOTFILE: firmware_boot_file.exe7  '                        Apu-> update ARC #                        Apu-> verifyr!                        Apu-> quit -                        Power-cycle the systemc    J                                                                      14-19 2             '                    Hardware Information         I                    Once you have the SRM loaded, you can directly installTD                    OpenVMS or Tru64 UNIX on the system. Do not allowD                    Microsoft Windows NT or other operating system(s)F                    to write a "harmless" signature to any disk used byG                    OpenVMS Alpha or OpenVMS VAX, as this will clobber atH                    key part of the disk; this will overwrite the OpenVMSH                    bootblock. (On OpenVMS Alpha and OpenVMS VAX, you canJ                    generally recover from this so-called "harmless" action3                    by using the WRITEBOOT.EXE tool.   G                    Using OpenVMS I64 and the EFI console, the bootblock F                    structures are expected to be compatible with thoseE                    of Microsoft Windows and other Integrity operating J                    systems; please see the discussion of the SET BOOTBLOCKJ                    command and the SYS$SETBOOT.EXE image in Section 9.7.3,J                    in Section 14.3.9, and in the OpenVMS documentation for$                    related details.)  G                    If you have a "full-flash" system and want to selectrD                    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 top9                    select AlphaBIOS/ARC, use the command:s  (                       >>> set os_type NT  .                    and power-cycle the system.  =                    For information on acquiring firmware, seetG                    Section 14.3.7.1. For information on OpenVMS licensetA                    PAKs (for hobbyist use) see Section 2.8.1. For A                    information on the Multia, see Section 14.4.1.r  J                    Information on enabling and using the failsafe firmwareI                    loader for various systems-this tool is available onlyoI                    on some of the various Alpha platforms-is available innJ                    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-thesetH                    sequences are needed when using an LK-series keyboardB                    with AlphaBIOS, as AlphaBIOS expects a PC-style                    keyboard:                      14-20               '                    Hardware Informationr        '                             F1   Ctrl/A_'                             F2   Ctrl/Ba'                             F3   Ctrl/C '                             F4   Ctrl/D '                             F5   Ctrl/E '                             F6   Ctrl/Fo'                             F7   Ctrl/P '                             F8   Ctrl/Ri'                             F9   Ctrl/To'                            F10   Ctrl/Ul'                         Insert   Ctrl/Vp'                         Delete   Ctrl/W '                      Backspace   Ctrl/Hh'                         Escape   Ctrl/[o'                         Return   Ctrl/M '                       LineFeed   Ctrl/Jv8                       (Plus) +   upselect (some systems):                      (Minus) -   downselect (some systems)+                            TAB   down arrowe)                       SHIFT+TAB  up arrowo  '           _____________________________i,           14.3.8  Console Management Options  E                    Options to collect multiple consoles into a singleBG                    server are available, with both hardware options andeG                    software packages that can provide advanced featuresE$                    and capabilities.  G                    Some of the available console management options for                     OpenVMS:F  5                    o  Heroix: http://www.robomon.com/   C                    o  KI Products: http://www.ki.com/products/clim/   ?                    o  Global Maintech: http://www.globalmt.com/   3                    o  TECsys: http://www.tditx.com/   C                    o  CA: http://www.cai.com/products/commandit.htm   D                    Computer Associates is the owner of what was onceG                    known as the VAXcluster Console System (VCS) consolenI                    management package, and has integrated this capabilityr8                    into the CA management product suite.  J                                                                      14-21 e             '                    Hardware Informationn      '           _____________________________t2           14.3.9  Why do my EFI Boot Aliases Fail?  I                    OpenVMS I64 boot aliases contain signature information D                    referencing the specific volume, meaning that theB                    entries are specific to the disk volume and not@                    the disk device. This also means that certainG                    operations, such as the SET BOOTBLOCK command or the G                    RUN SYS$SETBOOT.EXE operation that can rewrite these J                    volume signatures (signature or GUID values) can render2                    existing boot aliases unusable.  D                    If your boot aliases do not function as expected,C                    first try removing and re-adding them; this will?A                    resynchronize the boot aliases with the volumesJ                    contents. If you are using the SET BOOTBLOCK command orH                    the RUN SYS$SETBOOT.EXE operation to rewrite the diskI                    bootblock, you can request that the current signatures J                    (if any) be preserved, and this will typically maintainA                    the validity of your EFI console boot aliases.   '           ______________________________C           14.3.10  Can OpenVMS access the EFI console Boot Aliases?l  I                    For access to the EFI console environment from OpenVMSpG                    I64, see the BOOT_OPTIONS.COM command procedure, and.J                    the EFI SET, SHOW and BCFG mechanisms. Details on theseF                    are in the System Manager's and particularly in the5                    System Manager's Utilities manual.,  F                    For related information on boot aliases, please see$                    Section 14.3.5.1.  '           _____________________________ >           14.3.11  Downloading and using EFI Console Firmware?  H                    HP Integrity EFI system firmware can be downloaded inI                    the form of a bootable image master, unzipped and then F                    burned onto CD or DVD media (please see Section 9.7E                    for details of recording optical media directly on H                    OpenVMS), and the system can then generally be bootedD                    off the created media to perform the EFI firmware                    upgrade.                         14-22 l  e          '                    Hardware Informationt        I                    The HP Integrity Server website is accesssable via thetH                    following URL, and the available services and supportI                    information there has links to the available platform-tJ                    specific firmware images and upgrade-related materials:  5                    o  http://www.hp.com/go/integrity/g  J                    To use the following sequence, you will need a writableG                    or rewritable CD drive and software, and a blank CD-ME                    R or CD-RW disk. If you use CD writer software for D                    another platform, you will want to use the block,E                    binary, ISO or raw mode operations appropriate forMI                    the particular chosen recording package. The followingpC                    directions assume use of OpenVMS and native CD-RmF                    capabilities, please see Section 9.7 for associated                    details.   B                    1  First, you must acquire the Integrity serverG                       firmware from the above URL. Select the platform, D                       and navigate to the supporting information andG                       specifically to the Download Drivers and Software                        link  J                    2  Select Cross operating system (BIOS, Firmware, etc.)  F                    3  Locate the appropriate ISO-format firmware file.G                       There are several firmware file formats available D                       and there are also various off-line diagnosticB                       images, choose the ISO-format firmware file.  E                    4  Read the directions for the firmware file, then G                       download the ISO-format firmware (zip-compressed)0F                       file. A binary-mode FTP transfer should be used.  E                    5  Unzip the file into the corresponding .ISO data2H                       file. Somewhat confusingly, the .ISO extension canE                       indicate either a block-oriented raw image of acI                       disk, or a disk with the ISO-9660 volume structure.sC                       In this case, the former is intended and thistG                       file contains a a block copy or disk image of thefH                       firmware disk for the platform, and may or may notH                       be an ISO-9660 volume structure. The unzip tool isF                       available on the OpenVMS Freeware and elsewhere;I                       please see Section 13.11 for details and locations.   J                                                                      14-23    o          '                    Hardware Informationt        D                    6  Use CDRECORD or other available recording toolE                       (please see Section 9.7 for related details) to_H                       burn a CD-R or CD-RW disk, specifying the ISO file;                       as the source for the burn operation._  F                    7  Shut the Integrity Server system down to the EFI$                       console level.  G                    8  Unload the recorded CD media from the CD-R drive, F                       label it, and load it into the Integrity consoleE                       drive. This assuming the disk was not generated H                       directly on an Integrity CD-R/RW-capable drive, of                       course.i  G                    9  Using the EFI shell, display the current firmware /                       version using the commands                         info fw   D                   10  Exit the EFI shell and select the boot optionsC                       maintenance menu; create a boot alias for the F                       removable media drive for the CD; for the newly-,                       created firmware disk.  E                   11  Boot it. Follow the directions displayed by the H                       firmware loader and related documentation, heedingC                       the release notes that were reviewed earlier.   E                   12  Perform a cold restart of the Integrity server.   J                    For information on Alpha SRM console firmware upgrades,-                    please see Section 14.3.7.   D           __________________________________________________________7           14.4  What platforms will OpenVMS operate on?a  I                    For the list of boxes that are officially and formally C                    supported by OpenVMS Engineering, please see thei>                    OpenVMS Software Product Description (SPD).  9                    o  http://h18000.www1.hp.com/info/spd/   H                       OpenVMS typically uses SPD 25.01.xx, SPD 41.87.xx,'                       and SPD 82.35.xx.                       14-24               '                    Hardware Informationt        J                    Sometimes a particular and officially unsupported AlphaH                    box or Alpha motherboard will sufficiently resemble aH                    supported box that the platform can effectively mimicE                    and can bootstrap OpenVMS. Alternatively, somebody D                    (usually one or more engineers within the OpenVMSH                    Engineering group) will have put together a bootstrapC                    kit - such as the kit for the Alpha Multia-which @                    permits OpenVMS to bootstrap on the platform.  C                    Contrary to the assumptions of some folks, there_A                    are platform-level differences even within theaE                    VAX and within the Alpha platforms- hardware-level_I                    differences that can require moderate to extensive new_G                    coding within OpenVMS. Within a platform series, andfI                    particularly within Alpha platforms (and those few VAXnJ                    systems) that support Dynamic System Recognition (DSR),1                    OpenVMS can usually bootstrap.   A                    DSR is a mechanism by which OpenVMS can gatherVG                    platform-specific information, and DSR is the reason4F                    why newer Alpha systems can be more easily and moreF                    commonly supported on older OpenVMS Alpha releases.G                    DSR is implemented with OpenVMS Alpha code, with SRM G                    console code, and with platform non-volatile memory.   E                    OpenVMS users with experience on older OpenVMS VAX_F                    releases and VAX hardware will recall that then-newF                    VAX systems either required an OpenVMS VAX upgrade,F                    or that earlier releases would mis-identified then-E                    newer VAX systems-such as the case of the VAX 7000 F                    model 800 being (mis)identified as a VAX 7000 modelE                    600 when bootstrapped on OpenVMS VAX V5.5-2. (This F                    (mis)identification was the outcome of a deliberateI                    engineering effort to permit the VAX 7000 model 800 to J                    bootstrap on V5.5-2; the system manager could configureF                    the VAX 7000 model 800 to (mis)identify itself as aH                    model 600, to permit the system to bootstrap on V5.5-F                    2.) OpenVMS VAX and VAX platforms lack DSR support.  C                    OpenVMS I64 (please see Section 14.4.5 for Intel I                    Itanium terminology) supports a platform-level feature D                    similar to the OpenVMS Alpha DSR mechanism, basedF                    on the ACPI interface and the byte-code interpreterF                    implemented within OpenVMS, within the EFI console,F                    and particularly within non-volatile memory located  J                                                                      14-25 _  _          '                    Hardware InformationB        I                    on (byte-code interpreter compliant) PCI I/O hardware._H                    ACPI tables provide the information that was formerlyI                    retrieved from DSR and from the SRM, and the byte-codenJ                    interpreter can (theoretically) permit at least limitedG                    operations with (compliant) PCI hardware, whether ortH                    not OpenVMS has a driver for the particular hardware.  B                    The byte code interpreter may or may not permitC                    operations with any particular PCI hardware, andoG                    may or may not have sufficient performance for localaH                    requirements, and PCI hardware may or may not includeF                    the necessary ROM-based drivers in the PCI hardwareB                    non-volatile storage. (The intent of this IntelE                    platform-level effort is to move the host softwareiE                    drivers out onto the specific PCI hardware, and tooE                    permit the same byte code to operate regardless ofIF                    the particular host platform.) At least the initialH                    releases of OpenVMS I64 will not have support for theH                    byte code interpreter nor for arbitrary PCI or systemH                    hardware, but will have support for ACPI-based system;                    identification and system configuration.   '           _____________________________ &           14.4.1  on the Alpha Multia?  I                    Yes, there are a set of unsupported images that permittF                    specific OpenVMS Alpha versions to bootstrap on theE                    Multia UDB system. These images and the associatedaE                    instructions are available at the OpenVMS FreewareD                    website:   <                    o  http://www.hp.com/go/openvms/freeware/  7           Look in the Freeware V5.0 /multia/ directory.   B                    Instructions are included IN the kits. READ THE(                    INSTRUCTIONS. PLEASE!  I                    Some of the restrictions involved when running OpenVMSoD                    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.                       14-26 C             '                    Hardware Information         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, H                       a special ZLXp-E series graphics device driver-oneI                       that does not use interrupts-is needed. This driver -                       is provided in the kit.   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 seeeG                       any OpenVMS updates, nor SRM console updates, norM"                       any support.  F                    o  Do not expect to see any new versions of OpenVMSI                       on the Multia nor on any other unsupported systems. H                       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 Multiao                    include:   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.html   F                    o  http://www.netbsd.org/Ports/alpha/multiafaq.html  F                    o  http://www.brouhaha.com/~eric/computers/udb.html  J                                                                      14-27    U          '                    Hardware Information       '           _____________________________u2           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 bootstrapSI                    OpenVMS. (The Aspen Durango II variant, specifically.)e  E                    One problem has been generally reported: ATA (IDE)tG                    bootstraps will fail; SCSI storage and a SCSI CD-ROMr&                    device is required.  -                    Also see Section 14.4.2.1.   '           _____________________________ 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 the H                       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.e  :                    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 cardv+                       supported by OpenVMS.   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.  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.                       14-28 n  N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faqaN  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.comy   ------------------------------  # Date: Mon, 11 Apr 2005 19:55:00 GMTe# From: hoff@hp.nospam (Hoff Hoffman) < Subject: OpenVMS Frequently Asked Questions (FAQ), Part 9/110 Message-ID: <oCA6e.3493$IL.507@news.cpqcorp.net>   Archive-name: dec-faq/vms/part9  Posting-Frequency: quarterly Last-modified: 11 Apr 2005 Version: VMSFAQ_20050411-09.TXTo               '                    Hardware Informatione        E                    o  Rumour has it that you have one of the AXPpci33uC                       motherboards with the PS/2 mouse and keyboardyC                       connectors and a VGA card (one that will workyE                       under DECwindows) and you can run DECwindows ona!                       the system.e  '           _____________________________ )           14.4.3  on the Alpha XL series?5                      No.  J                    OpenVMS Engineering does not formally support the AlphaH                    XL series, nor will OpenVMS (informally) bootstrap on'                    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 operatinge                    system.  J                    The Alpha XL platform does not resemble other supported                    platforms.   '           _____________________________SH           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.s  H                    If you wish to attempt this, you must ensure that allE                    graphics and all I/O controllers in the system areoF                    supported by OpenVMS. You must also ensure that you9                    have the most current firmware loaded.d  G                    Here are some salient differences within the various /                    Personal Workstation series:   C                    o  The -a series was designed and was tested for.G                       Windows NT use. Only. It is not supported for usen#                       with OpenVMS.e  I                    o  The -au series was designed and tested for Windows, C                       OpenVMS, and Tru64 UNIX compatibility, and is 4                       considered a supported system.  J                                                                      14-29 m             '                    Hardware Informations        I                    o  There are at two different and distinct variants ofiJ                       the family, and usually refered to by their internal-                       hardware project names.   G                      o  The Miata MX5. The Miata MX5 variant has no USBrF                         ports and no on-board SCSI. The on-board IntelI                         SIO chipset is not supported by OpenVMS, and thuseF                         OpenVMS cannot bootstrap ATAPI CD-ROM devices.  I                         That said, the Miata MX5 -a series typically cameeI                         with DEC branded Adaptec 2940UW SCSI controllers,mE                         Matrox Millennium graphics cards, no L3 cachebI                         module, and an Toshiba IDE CD-Rom. Some came witheE                         very high end Powerstorm graphics card if the I                         system was destined to do CAD or movie rendering.o  C                         Graphics and other I/O can and does vary bym                          package.  B                         The Miata MX5 is not supported by OpenVMS.  H                      o  The Miata GL. The Miata GL variant has USB portsF                         and on-board SCSI and bootstraps using the on-E                         board Cypress IDE chipset and an ATAPI CD-ROMlI                         are supported by OpenVMS. The Miata GL -a variantuE                         is need not be configured with an add-on SCSInG                         controller, given both the ability to bootstrap @                         from ATAPI CD-ROM and the on-board SCSI.  C                         Graphics and other I/O can and does vary by                           package.  H                         Various of the Miata GL systems are supported by                          OpenVMS.  G                    For obvious reasons, most folks will prefer and willDI                    select a Miata GL system, given the choice between theaJ                    Miata MX5 and the Miata GL series. And as for your nextJ                    question, you cannot necessarily nor easily distinguishF                    the Miata MX5 from the Miata GL based solely on the                     model number.  <                    See Section 14.4.4.2 for related details.                      14-30 a  e          '                    Hardware Information       '           _____________________________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 only J                    for use with the Microsoft Windows NT operating system.  C                    On some of the "Whitebox" systems, the following,G                    sequence of console commands can potentially be used G                    to convert the system over to unsupported use by anduG                    for OpenVMS Hobbyist users. (But please note that ifOE                    you wish to attempt this, you must ensure that all.E                    graphics and all I/O controllers in the system are:J                    supported by OpenVMS, and you must ensure that you haveI                    the most current SRM firmware loaded. (For informationuI                    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 will4G                    be entirely unsupported and may or may not be stable                     and useful.)   "                    set os_type vmsD                    cat nvram  ! too see what is in this, if anything                    edit nvram %                    10 set srm_boot on,                    20 e                     initg  E                    If your nvram has other contents, you will need topE                    change the line numbers (10 and 20) to reflect thenJ                    contents of your configuration. To obtain documentationE                    on the commands of the console editor, enter the ?M-                    command within the editor.c  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 supportedkE                    by OpenVMS, though the AlphaServer 800 series is aoJ                    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.33.n  J                                                                      14-31 8  K          '                    Hardware Informationt      '           _____________________________tI           14.4.4.2  OpenVMS and Personal Workstation ATA (IDE) bootstrap?t  J                    OpenVMS will boot and is supported on specific PersonalH                    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 CypresslF                    IDE controller chip is supported by OpenVMS for IDEI                    bootstraps. (Configurations with the Intel SIO are notMA                    generally considered to be supported systems.)r  F                    If you have an -au series system, you can determineI                    which IDE chip you have using the SRM console command:t  '                      SHOW CONFIGURATIONI  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-is I                    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 IntelM;                    SIO, and thus cannot bootstrap from IDE.   :                    See Section 14.4.4 for related details.  '           _____________________________ 6           14.4.5  On the Intel Itanium IA-64 platform?  =                    OpenVMS has been ported to the Intel IA-64 E                    architecture; to HP Integrity systems based on thef2                    Intel Itanium Processor Family.  F                    The first release of OpenVMS I64 was V8.0, with theF                    first general release of OpenVMS I64 known as V8.2.6                    Yes, there was a V8.1 release, too.  J                    Some Intel and HP terminology: Itanium Processor FamilyD                    is the name of the current implementation; of theC                    current Intel microprocessor family implementing C                    the IA-64 architecture. IA-64 is the name of the F                    Intel architecture implementing the VLIW (Very LongE                    Instruction Word) design known as EPIC (Explicitly 3                    Parallel Instruction Computing).e                      14-32 S  p          '                    Hardware Information         J                    I64 is the name of a family of HP computer systems thatF                    use Intel Itanium processors and that are supportedI                    by "HP OpenVMS for Integrity Servers" (and itself more E                    commonly known as "OpenVMS I64"); by one of the HPSH                    operating systems that runs on HP Integrity hardware.  I                    The Extensible Firmware Interface (EFI) is the name ofwG                    the console environment for Itanium systems, and thetF                    Baseboard Management Console (BMC) and the optionalJ                    Management Processor (MP) are the most typical hardware6                    interfaces into the system console.  '           _____________________________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 docoumentation .                    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-d6                       64/Downloads/archSysSoftware.pdf  9                    o  ftp://download.intel.com/design/IA- /                       64/Downloads/24870101.pdf   H                    The Intel Extensible Firmware Interface (EFI) console!                    documentation:)  D                    o  http://www.pentium.de/technology/efi/index.htm  >                    Please see Section 14.4.5 for Intel Itanium                    terminology.   D           __________________________________________________________I           14.5  What is the least expensive system that will run OpenVMS?i  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-rI                    see the OpenVMS Software Product Description (SPD) for   J                                                                      14-33               '                    Hardware Information         G                    details on the supported systems and configurations. J                    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:  7                    o  http://www.hp.com/go/openvms/doc/   J                    When purchasing a system, ensure that the system itselfH                    is supported, that the system disk drive is supportedF                    or closely compatible, that the optical (CD or DVD)G                    drive is supported or is closely compatable and thatsE                    (in the case of SCSI devices) it also specifically C                    supports 512-byte block transfers; no equivalenteH                    requirement exists for IDE devices. Also particularlyH                    ensure that the video controller is supported. Use ofH                    supported HP hardware will generally reduce the level2                    of integration effort involved.  F                    A CD-ROM, CD-R or DVD drive is required for OpenVMSF                    Alpha installations, and a DVD-ROM or recordable orG                    rewritable DVD DVD drive is required for OpenVMS I64t!                    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:  1                    o  http://www.hp.com/go/servere  C                    Alpha Technical information and documentation ise                     available at:  E                    o  ftp://ftp.compaq.com/pub/products/alphaCPUdocs/   H                    o  http://h18000.www1.hp.com/products/software/alpha-                       tools/                      14-34               '                    Hardware Informationr        B                    o  ftp://ftp.digital.com/pub/DEC/Alpha/systems/  1                    o  http://ftp.digital.com/pub/u@                       Digital/info/semiconductor/literature/dsc-"                       library.html  +                    o  Alpha Systems Update:?C                       http://www.compaq.com/alphaserver/fb_acu.html   B                    Software Product Description (SPD) information,<                    including platform support documentation:  9                    o  http://h18000.www1.hp.com/info/spd/s  H                       OpenVMS typically uses SPD 25.01.xx, SPD 41.87.xx,'                       and SPD 82.35.xx.   B                    Information on Multia hardware is available at:  F                    o  http://www.netbsd.org/Ports/alpha/multiafaq.html  G                    Information on DEC 3000 series hardware is availableo                    at:  L                    o  http://www.phys.ufl.edu/~prescott/linux/alpha/dec3000-"                       sysinfo.html  L                    o  http://www.phys.ufl.edu/~prescott/linux/alpha/dec3000-                       docs.html   @                    o  http://ftp.netbsd.org/pub/NetBSD/misc/dec-%                       docs/index.htmla  B                    The NetBSD folks maintain useful Alpha hardware"                    information at:  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 onSF                    older platforms, for those cases where the compilerF                    is explicitly requested to generate the newer Alpha                     instructions.  J                                                                      14-35               '                    Hardware Information         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 similar %                    kernel-mode code.)C  A                    Alpha instructions are available in groups (or I                    subsets). Obviously, there is the base instruction setnH                    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.S  E                    o  floating-point and square root extension (FIX):gF                       FTOIS, FTOIT, ITOFF, ITOFS, ITOFT, SQRTF, SQRTG,'                       SQRTS, and SQRTT.   ,                    o  count extension (CIX):,                       CTLZ, CTPOP, and CTTZ.  2                    o  multi-media extension (MVI):E                       MAXSB8, MAXSW4, MAXUB8, MAXUW4, MINSB8, MINSW4, C                       MINUB8, MINUW4, PERR, PKLB, PKWB, UNPKBL, and                        UNPKBW.   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-level H                    scheduling and also the instructions generated insideG                    loops-any code resulting from /OPTIMIZE=TUNE that is F                    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 of                      14-36               '                    Hardware Information         C                    the proper code for the particular current Alpha "                    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.o  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.  @                    Please see Section 10.22 and Section 14.9 forA                    additional details and related considerations.   D           __________________________________________________________9           14.8  So how do I open up the DEC 3000 chassis?e  H                    After removing those two little screws, tilt the backG                    end of the top shell upwards-then you can remove thei                    lid.i  D           __________________________________________________________'           14.9  What is byte swizzling?_  I                    "Swizzling" is the term used to describe the operationnD                    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.  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 theoG                    transfer was encoded into the address data. The datalG                    itself then had to be shifted into the correct "byte   J                                                                      14-37 a  o          '                    Hardware Informationr        E                    lane" ; into the required offset position within ae%                    longword transfer;r  I                    The EV56 microprocessor supports byte/word instructioneI                    references in memory space, however only specific EV56hI                    systems can support byte/word accesses into I/O space;rF                    device drivers may or may not be able to utilize toE                    byte/word instructions to access device registers.AH                    Further, even on an EV56 system with hardware supportF                    for byte/word accesses into I/O space, the relevantF                    OpenVMS routines typically do not support byte/word)                    access into I/O space.-  D                    Systems based on the EV6 microprocessor (with the@                    salient exception of the AlphaServer GS60 andD                    AlphaServer GS140 series, for reasons of platformF                    compatability) support a flat, byte addressable I/O                    space.l  I                    If a device driver uses CRAM or IOC$WRITE_IO/IOC$READ_nH                    IO, then OpenVMS will correctly process the swizzlingE                    requirements without requiring changes the driver;aG                    OpenVMS will transparently swizzle and unswizzle the E                    I/O space references, if needed for the particularcI                    target platform. (Access and use of these routines may G                    or may not be feasible within the requirements for a H                    particular device driver, with the decision typicallyG                    based on the target performance requirements and the0G                    expected frequency of device references and thus therH                    expected frequency of calls to these or other similar                    routines.)   E                    To use byte/word operations on MEMORY, you need to H                    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.  G                    If the application is directly referencing I/O spaceoI                    access across a range of Alpha systems such as is done J                    with the X Windows device drivers, then the driver willF                    need to know how to do swizzling for old platforms,H                    and byte access for new platforms. Device drivers for                      14-38 t  v          '                    Hardware Information         G                    new graphics controllers can specifically target and H                    specifically require platforms based on EV6 and laterI                    Alpha microprocessors because of this requirement, for                     instance.  @                    Please see Section 10.22 and Section 14.7 forA                    additional details and related considerations.a  D           __________________________________________________________E           14.10  What is the layout of the VAX floating point format?y  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 signIG                    and exponent (and for other than H, some of the mostrF                    significant fraction bits). Each successive higher-I                    addressed word contains the next 16 lesser-significantyI                    fraction bits. Bit 15 of the first word is the sign, 1 G                    for negative, 0 for positive. Zero is represented byfF                    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 -kF                    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 and I                    less than 1.0. The MSB, always being 1, is not stored. I                    The binary exponent is stored with a bias varying with B                    type in bits 14:n of the lowest-addressed word.  E             FP      Exponent    Exponent    Mantissa (Fraction) bits, B             Type      Bits        Bias        including hidden bitF             ==========================================================6              F         8           128              246              D         8           128              566              G        11          1024              536              H        15         16384             113  J                                                                      14-39               '                    Hardware Informationf        I                    The layout for D is identical to that for F except fora/                    32 additional fraction bits.   H                    Example: +1.5 in F float is hex 000040C0 (fraction of7                    .11[base 2], biased exponent of 129)   D           __________________________________________________________>           14.11  Where can I find more info about VAX systems?  F                    o  HP provides limited VAX platform information viaH                       links at the AlphaServer website, itself available                       via:2                       http://www.hp.com/go/server/  G                    o  Jim Agnew maintains a MicroVAX/VAXstation FAQ at:uG                       http://anacin.nsc.vcu.edu/~jim/mvax/mvax_faq.htmlr  8                    o  The VAXstation 3100 Owner's Guide:E                       http://www.whiteice.com/~williamwebb/intro/DOC-c                       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:t?                       http://telnet.hu/hamster/vax/e_index.html   D           __________________________________________________________H           14.12  Where can I find information on NetBSD for VAX systems?  A                    Gunnar Helliesen maintains a NetBSD VAX FAQ at   .                    o  http://vaxine.bitcon.no/  D           __________________________________________________________@           14.13  What system disk size limit on the MicroVAX and!                  VAXstation 3100??  G                    System disks larger than 1.073 gigabytes (GB)-1fffffaJ                    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.)                      14-40               '                    Hardware Information4        H                    Various of the SCSI commands used by the boot driversE                    imbedded in the console PROM on all members of theiG                    VAXstation 3100 series use "Group 0" commands, which3I                    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 ahF                    system crashdump file, as this can potentially leadD                    to system disk corruptions should any part of the=                    crashdump file be located beyond 1.073 GB.e  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 of D                    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. G                    There was no similar PROM upgrade for the VAXstation                     3100 series.   ;                    Systems that are affected by this limit:o  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 with H                       console VMB versions prior to V6.4 are affected. AH                       PROM upgrade for these specific systems is (or was&                       once) available.                      Also seee  E                    o  http://www.whiteice.com/~williamwebb/intro/DOC-u                       i.html  (                    Also see Section 9.5.      J                                                                      14-41 e  :          '                    Hardware InformationS      D           __________________________________________________________8           14.14  What are the VAX processor (CPU) codes?                CPU:    Platform:              -----   ---------3              KA41-A : MicroVAX 3100 Model 10 and 20o4              KA41-B : VAXserver 3100 Model 10 and 20               KA41-C : InfoServer5              KA41-D : MicroVAX 3100 Model 10e and 20e 6              KA41-E : VAXserver 3100 Model 10e and 20e5              KA42-A : VAXstation 3100 Model 30 and 40 5              KA42-B : VAXstation 3100 Model 38 and 48e.              KA43-A : VAXstation 3100 Model 763              KA45   : MicroVAX 3100 Model 30 and 40a.              KA46   : VAXstation 4000 Model 60,              KA47   : MicroVAX 3100 Model 80)              KA48   : VAXstation 4000 VLC 2              KA49-A : VAXstation 4000 Model 90/90A.              KA49-B : VAXstation 4000 Model 95.              KA49-C : VAXstation 4000 Model 96,              KA50   : MicroVAX 3100 Model 90,              KA51   : MicroVAX 3100 Model 95(              KA52   : VAX 4000 Model 100(              KA53   : VAX 4000 Model 105(              KA54   : VAX 4000 Model 106,              KA55   : MicroVAX 3100 Model 85,              KA56   : MicroVAX 3100 Model 96(              KA57   : VAX 4000 Model 108,              KA58   : MicroVAX 3100 Model 88,              KA59   : MicroVAX 3100 Model 98              KA85   : VAX 8500              KA86   : VAX 8600              KA88   : VAX 88000              KA600  : VAX 4000-50 (aka VAXbrick)9              KA610  : MicroVAX I, VAXstation I (aka KD32)r$              KA620  : rtVAX (VAXeln)"              KA62A  : VAX 6000-200"              KA62B  : VAX 6000-3000              KA630  : MicroVAX II, VAXstation II2              KA640  : MicroVAX 3300, MicroVAX 3400Q              KA650  : VAXstation 3200, MicroVAX 3500, MicroVAX 3600, MicroVAX IIId"              KA64A  : VAX 6000-400A              KA655  : MicroVAX 3800, MicroVAX 3900, MicroVAX III+ "              KA65A  : VAX 6000-500                      14-42               '                    Hardware Informationd        1              KA660  : VAX 4000-200, VAX 4 upgrade "              KA66A  : VAX 6000-600"              KA670  : VAX 4000-300"              KA675  : VAX 4000-400"              KA680  : VAX 4000-500#              KA681  : VAX 4000-500At"              KA690  : VAX 4000-600#              KA691  : VAX 4000-605A #              KA692  : VAX 4000-700An#              KA693  : VAX 4000-605Ao#              KA694  : VAX 4000-705Ao               KA730  : VAX-11/730               KA750  : VAX-11/750,              KA780  : VAX-11/780, VAX-11/782               KA785  : VAX-11/785"              KA7AA  : VAX 7000-600"              KA7AB  : VAX 7000-700"              KA7AC  : VAX 7000-800              KA800  : VAXrta(              KA820  : VAX 8200, VAX 8300(              KA825  : VAX 8250, VAX 8350              KA865  : VAX 8650  D           __________________________________________________________>           14.15  Where can I get software and hardware support                  information?t  J                    Please contact the HP Customer Support Center. ServicesC                    and information, manuals, guides, downloads, andgI                    various other information is available via the support                     link at:g  9                    o  http://www.hp.com/products/openvms/b  I                    Various hardware and system documentation is availableU                    at:  B                    o  http://www.compaq.com/support/techpubs/user_'                       reference_guides/   E                    o  http://www.adenzel.demon.nl/vaxes/microvax3100/i  F                    o  http://www.adenzel.demon.nl/vaxes/infoserver150/  J                                                                      14-43 o  t          '                    Hardware Information         I                    TSM (Terminal Server Manager), DEChub, DECserver, etc.a                    information:a  E                    o  http://www.compaq.com/support/digital_networks_p                       archive/  D                    The owner and maintainer of current DECserver andE                    related hardware is DIGITAL Network Products Groupc                    (DNPG):  *                    o  http://www.dnpg.com/  D           __________________________________________________________B           14.16  Where can I get hardware self-maintenance support                  assistance?  D                    The HP Parts Directory and the HP Parts ReferenceE                    Guide (arguably the most direct descendents of the G                    HP Assisted Services program, of the Compaq Assisted_E                    Services program, and of the now-ancient DECmaileryC                    program) are available to customers that wish tooC                    maintain their own system(s) (self-maintenance),MF                    but that wish some level of assistance in acquiringD                    specific parts, hardware diagnostics and hardwareC                    manuals for the system(s), and that wish to havedJ                    access to spares and module-level repairs for customer-3                    performed hardware module swaps:c  1                    o  http://www.hp.com/go/parts/   2                    o  http://www.hp.com/buy/parts/  H                    The HP Parts Reference Guide replaces the CAS-CatalogH                    and DAS-Catalog parts catalogs and related resources.  I                    Details of the available self-maintenance programs and G                    services can vary by geography and by the particular I                    services channel(s), and current program specifics are 0                    available via the above URLs.                              14-44               '                    Hardware Informations      D           __________________________________________________________G           14.17  Why does my system halt when I power-cycle the consolel                  terminal?  I                    Various VAX and Alpha consoles are designed to process C                    the BREAK signal, treating it as a HALT request.   J                    A BREAK is a deliberately-generated serial line framing                    error.   ?                    When a serial line device such as a terminal E                    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 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 theK                    processor.H  I                    The most common way to avoid these halts is to disable G                    the serial line console or to simply not power-cycle C                    the console terminal. There is certain importantlE                    system state information that is displayed only oniH                    the console, OpenVMS expects to always have access to&                    the system console.  (                    Also see Section 5.6.  D           __________________________________________________________H           14.18  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 the F                    DIGITAL logo and with the RJ modular jacks, or withE                    a DIN connector with pins in a configuration othereG                    than the PC-standard DIN connector pin orientation),rD                    and older video monitors (with RGB synch-on-greenD                    video signaling) all use signaling formats and/orC                    communications protocols that differ from the PC   J                                                                      14-45 p  e          '                    Hardware Information         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-yH                    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 "industry C                    standard" PC systems, and can often be used with G                    most PC peripheral device controllers. LK461, LK463, G                    LK46W, LK471, PC7XS-CA, VRC16, VRC21, TFT-series LCD F                    flat-panel displays, etc., are typically reasonablyD                    compatible with most PC systems, and will usuallyI                    perform as expected within the limits of the hardware. E                    (For details of CRT and LCD display compatibility,p-                    please see Section 14.19.)t  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 abG                    PC peripheral controller or with a PC-compatible KVMtF                    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 theCI                    format DEC [four-digit-number], it probably won't works>                    on a PC system or with a PC-compatible KVM.  I                    Note that the above is a general guideline, and shouldhI                    not be read to indicate that any particular peripheralmA                    device will or will not work in any particularwH                    configuration, save for those specific configurations9                    the device is explicitly supported in.t  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 PCa                    system:  *                    o  http://www.si87.com/                      14-46 2  0          '                    Hardware Information         D                    The DIGITAL (classic 2-5-2-style) part number 29-J                    32549-01 converts the output from the RGB cable (3 BNC,J                    synch-on-green) that comes with the VAXstation 3100 andG                    VAXstation 4000 series to a female SVGA D connector._D                    You may be able to find third-party converters orF                    adapters (3 BNCs with synch-on-green signaling to 5=                    BNCs with VGA/SVGA, or to 15-pin VGA/SVGA.n  E                    This adapter will allow PC multisync monitors withlF                    the needed frequency specifications to be used withI                    the VAXstation series synch-on-green video connection.tF                    It may well also work with a VAXstation 2000 seriesA                    systems, but specifics and performance of thateI                    combination are not immediately known at this writing.d  G                    The protocol definition for the old DIGITAL keyboard I                    and mouse interfaces is buried at the back of the QDSS I                    section in the old VAXstation II manual, specifically,nE                    in the back of the VCB02 Video Subsystem TechnicalaI                    Manual (EK-104AA-TM). The keyboard wiring and protocolaE                    is in appendix B, and occupies circa 44 pages. Thet:                    mouse is in appendix C, circa 12 pages.  *                    Also see Section 14.19.  D           __________________________________________________________J           14.19  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?"gJ                    question, please first locate the resolution(s) and theG                    frequencies that are possible/supported at both endspI                    of the video cable (on the display and on the graphics E                    controller, in other words), and then determine ifSJ                    there are any matching settings available. If there areI                    multiple matches, you will need to determine which one 6                    is most appropriate for your needs.  G                    You will also need to determine if the video monitorHF                    or graphics controller requires the 3 BNC signalingF                    with the synchronization signals on the green wire,F                    or the 5 BNC signaling common on many PCs, or otherF                    connections such as the DB15 video connector or USBD                    connector used on various systems. (BNC signalingF                    is comparatively old, but prevalent with many olderG                    hobbyist AlphaStation or VAXstation configurations.)   J                                                                      14-47 6  h          '                    Hardware Information         J                    If there are no matches, you will likely need to changeG                    the hardware at one or both ends of the video cable.c  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/   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 display A                    resolution and (for LCD displays) also set the G                    controller refresh rate to 60Hz. Check your graphicswD                    controller and your display documentation for anyD                    device-specific requirements and/or configuration#                    recommendations.   G                    Some of the older graphics controllers around do not/G                    necessarily generate stable signals at 60 Hz, if the J                    controller can even generate that refresh rate; you mayG                    end up upgrading to a less-old controller. (At leasteI                    some of the PowerStorm 3D30 and PowerStorm 4D20 series E                    controllers, for instance, are not necessarily thefF                    best choice for 60 Hz operations with an LCD, basedD                    on empirical testing with an AlphaStation XP1000,F                    PowerStorm 3D30, and a TFT2025 series LCD. DegradedC                    or mismatched signals produce degraded displays,aH                    obviously. The newest graphics controllers compatibleC                    with your particular system are generally betterrH                    choices here for use with LCD; the Radeon 7500 seriesC                    is a good choice for most EV6-class AlphaStation.)                    systems, for instance.   *                    Also see Section 14.18.                      14-48 w             '                    Hardware Informationl      D           __________________________________________________________A           14.20  Where can I get information on storage hardware?u  F                    Information on various HP (Compaq, DIGITAL) OpenVMSG                    and other disk storage hardware and controllers, andaI                    related technical information on SCSI, device jumpers,a)                    etc., is available at:   2                    o  http://theref.aquascape.com/  1                                              Note   B                       the aquascape website appears to have becomeD                       unavailable, and the FAQ maintainer is unawareD                       of a new or replacement server. You may or mayF                       not have some success looking for this or of anyF                       other now-unavailable sites using the world-wide&                       web archives at:  0                       o  http://www.archive.org/  D           __________________________________________________________D           14.21  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 causes D                       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.v  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 ^F2tD                       several times or unplugging and replugging theG                       keyboard frequently fix this problem. (Ensure youoE                       have current ECO kits applied; there is a patcha5                       available to fix this problem.)   H                    o  A key that was working spontaneously stops workingG                       correctly. This may be either of the two previouslF                       cases, or it may be bad console firmware. EnsureF                       that you have the most recent firmware installed  J                                                                      14-49 r  e          '                    Hardware Informationo        I                       on your Alpha system. In particular, an old versioneI                       of the DEC 3000 SRM firmware is known to have a bug @                       that can cause this keyboard misbehaviour.  D           __________________________________________________________I           14.22  Problem - My LK411 sends the wrong keycodes or some keyss                  are deads  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.23  Which DE500 variant works with which OpenVMS version?  E                    Ensure you have a version of the Alpha SRM consolesF                    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, andeG                    apply any available ALPCPU ECO kit for the platform.b                      o  DE500-XA:                       auto-detection, no auto-negotiation,E                       OpenVMS V6.2-1H1 and ALPBOOT ECO, also V7.0 and $                       later and ECO.?                       Device hardware id 02000011 and 02000012.a7                       Component part number 54-24187-01a                      o  DE500-AA7                       auto-detection, auto-negotiation,oG                       OpenVMS V6.2 and ALPBOOT and ALPLAN ECOs, or V7.1 (                       and later and ECO.?                       Device hardware id 02000020 and 20000022.h7                       Component part number 54-24502-01r                        14-50 f  t          '                    Hardware Informationn                            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-01e  A                    o  DE500-FA (100 megabit fibre optic Ethernet)c0                       OpenVMS V7.1-1H1 and laterF                       Device hardware id 02000030 (check connector, vsG                       DE500-BA) (other values possible on old Alpha SRMn                       firmware) 7                       Component part number 54-24899-01d  J                    To check the DE500 device hardware id from OpenVMS, use)                    the following command:   #                    $ ANALYZE/SYSTEM -                    SDA> SHOW LAN/DEVICE=EWcu:   7                    The "hardware id" will be displayed.t  E                    To set the DE500 speed and duplex settings via the I                    associated Alpha SRM console environment variable, see                     Table 14-4.  J           ________________________________________________________________5           Table 14-4  DE500 Speed and Duplex Settingsn  J           ________________________________________________________________J           EWx0_MODE_setting_________________Meaning_______________________  F           Twisted-Pair                      10 Mbit/sec, nofull_duplex  D           Full Duplex, Twisted-Pair         10 Mbit/sec, full_duplex  F           AUI                               10 Mbit/sec, nofull_duplex  F           BNC                               10 Mbit/sec, nofull_duplex  G           Fast                              100 Mbit/sec, nofull_duplex   E           FastFD (Full Duplex)              100 Mbit/sec, full_duplex   J           Auto-Negotiate____________________Negotiation_with_remote_device  A                    To override the console setting and use LANCP:   J                                                                      14-51 O             '                    Hardware Informationt                    $ RUN SYS$SYSTEM:LANCP&           LANCP> SET DEV EWA0/SPEED=103           LANCP> SET DEV EWA0/SPEED=100/full_duplex   C                    Fast Ethernet (100Base, 100 megabit) controllerstF                    such as the DE500 series have a pair of connectionsC                    available-while traditional Ethernet (10Base, 10iF                    megabit) is inherently a half-duplex protocol, FastG                    Ethernet can be configured to use one or both of themF                    available connections, depending on the controller.A                    Fast Ethernet can thus be half- or full-duplexwF                    depending on the configuration and the capabilitiesE                    of the network controller and the Ethernet network I                    plant. Some Fast Ethernet controllers can also operatewH                    at traditional Ethernet speeds, these controllers areH                    thus often refered to as 10/100 Ethernet controllers.  D           __________________________________________________________+           14.24  Third-party or Unsupportede4                  disk/tape/controllers/SCSI/widgets?  I                    A wide variety of third-party and formally-unsupported_G                    widgets-SCSI and ATA (IDE) disks and tapes, graphicsyG                    controllers, etc-are obviously widely available, andt1                    are used on various platforms.   H                    If you purchase third-party or unsupported or genericI                    SCSI or ATA (IDE) storage devices, you and your devicetE                    vendor will be responsible for the testing and theaE                    support of the devices. In general, you can expecttI                    that HP will address non-standards-compliance problemsdE                    within OpenVMS (changes that will also not preventsG                    operations with other supported devices, of course),dE                    but you and/or the device vendor and/or the device F                    manufacturer are responsible for finding and fixingG                    problems in the particular third-party device and or '                    controller involved.a  I                    In particular, realize that neither SCSI nor ATA (IDE)aI                    is a particularly standard interface, these interfacesrH                    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)                      14-52    t          '                    Hardware Informationg        H                    V7.1-2 or later. If you wish to try to use ATA (IDE),/                    use OpenVMS V7.1-2 or later.   J                    On older OpenVMS releases, see the disk capacity limits!                    (Section 9.5).a  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 DRVERR==                    fatal drive errors and error log entries.)   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.   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:  K           Issuing 6-byte MODE SENSE QIOW to get current values for page 01hr0                  Page Code ................. 01hF                  Page Name ................. Read-Write Error Recovery0                  Saveable .................. Yes/                  Size ...................... 10VD                  Hex Data .................. E6 08 50 00 00 00 08 002                                              00 00  I                    The E6 shown indicates that the AWRE and ARRE bits are/F                    set, and this is incompatible with OpenVMS versionsE                    prior to V6.2. Further along in the same SCSI_INFO ,                    display, if you also see:  N           Issuing 6-byte MODE SENSE QIOW to get changeable values for page 81h0                  Page Code ................. 01hF                  Page Name ................. Read-Write Error Recovery0                  Saveable .................. Yes/                  Size ...................... 10vD                  Hex Data .................. C0 08 50 00 00 00 08 002                                              00 00  J                                                                      14-53 a  a          '                    Hardware Informationt        G                    The C0 value means that the AWRE and ARRE values can_F                    be changed on this particular SCSI device. (This isI                    not always the case.) If the bits are set, you can usekI                    RZDISK from the OpenVMS Freeware, and can reset the E6bI                    flag byte to hexadecimal 26 (or whatever the remainingo=                    mask when you remove bits C0) on page one.o  D                    Each SCSI and ATA (IDE) host contains non-trivialI                    SCSI and IDE driver software, and each device containscH                    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.  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 cancF                    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) command F                    extensions. (Also see Section 7.1 and Section 9.7.)  I                    Some SCSI tapes lack odd-byte transfer support, making J                    operations with OpenVMS problematic at best, as OpenVMSE                    expects odd-byte support. Examples of such include H                    LTO-1 devices such as the HP Ultrium 230 series tape,I                    and the DLT VS80 series tapes. Due to the lack of odd- I                    byte transfer support, LTO-1 devices are not supported H                    by OpenVMS. LTO devices in the LTO-2 and later seriesE                    do reportedly presently all have odd-byte transfer H                    support, and operations are reportedly rather easier.:                    Do check for formal support, of course.  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 entirelyaC                    compliant with applicable standards or interfacew8                    documents-that will not interoperate.                      14-54    A          '                    Hardware Information         ?                    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.24.1  Lists of third-party widgets on OpenVMS?   J                    Various folks have successfully used common third-partyH                    disk disk devices with OpenVMS, such as the ATA (IDE)H                    and SCSI variants of the Iomega Zip250 removable disk                    device.  E                    Common SCSI CD-R/CD-RW devices such as the Plextor F                    PlexWriter 12/10/32S SCSI series and the HP DVD200iF                    series (recording CD-R) have also been successfullyD                    utilized with various AlphaStation and VAXstationG                    systems, and with tools such as CDRECORD. (A Plextor8F                    PlexWriter burn of 614400000 bytes (300000 sectors)B                    requires just over six minutes at 12x, using anD                    AlphaStation XP1000 666 MHz EV67 system UltraSCSIF                    host.) (See Section 9.7 for detailed discussions ofH                    recording optical media on OpenVMS, and the available                    tools.)  G                    If you choose to attempt to use third-party devices,MH                    ensure that you have the most current OpenVMS versionB                    and the most current ECO kit(s) applied. In theF                    specific case of the ATA (IDE) Iomega Zip250 drive,D                    ensure that you have the most current revision of*                    SYS$DQDRIVER installed.  '           _____________________________ G           14.24.2  Are the 2X-KZPCA-AA and SN-KZPCA-AA LVD Ultra2 SCSI?   H                    Yes. Both of these controllers are Ultra2 low-voltage7                    differential (LVD) SCSI controllers.0  J                                                                      14-55 o             '                    Hardware Information7      '           _____________________________77           14.24.3  Resolving DRVERR fatal device error?   I                    If this is on an OpenVMS version prior to V6.2, please7H                    see the AWRE and ARRE information included in section!                    Section 14.24.A  D           __________________________________________________________7           14.25  Looking for connector wiring pin-outs?_  E                    The DECconnect DEC-423 Modified Modular Jack (MMJ)rH                    appears similar to a telphone or network modular jac,I                    though with the key offset to one side. The DECconnect I                    MMJ connector pin-out is listed in Table 14-5, with anrJ                    end-on view of the connector pins and the connector key                    shown below.t  J           ________________________________________________________________%           Table 14-5  DEC MMJ Pin-out   J                    _______________________________________________________J                    Pin_____Description____________________________________  4                    1       Data Terminal Ready (DTR)  )                    2       Transmit (TXD)n  1                    3       Transmit Ground (TXD-)   0                    4       Receive Ground (RXD-)  (                    5       Receive (RXD)  J           _________6_______Data_Set_Ready_(DSR)___________________________  !              +------------------+i!              | 1  2  3  4  5  6 |o!              +------------+    ++i                            +____+  D                    The BC16E-nn (where the "-nn" indicates the cableG                    length) cabling and keying "flips over" or "crosses-uI                    over" the signal wires, and this allows all DECconnectdG                    MMJ connections to be wired identically; the ends of_G                    the BC16E are symmetrical and fully interchangeable,tE                    and allows either end of the cable to be connectedtG                    either to the terminal or to the host. Specifically,sB                    the BC16E-nn cross-over wiring looks like this:                      14-56 e             '                    Hardware Information-        7                   Terminal                         Hostc6                   MMJ                              MMJ  9                DTR 1 --->---------->----------->--- 6 DSRt9                TXD 2 --->---------->----------->--- 5 RXD 5                    3 ------------------------------ 4e5                    4 ------------------------------ 3t9                RXD 5 ---<----------<-----------<--- 2 TXDu9                DSR 6 ---<----------<-----------<--- 1 DTRd  F                    DECconnect parts and connections are available fromF                    HP, and MMJ crimping dies for use in typical telco-J                    style crimping tools, and MMJ connectors, are availableH                    from Blackbox and from other communications equipment                    vendors.a  I                    The PC-compatible DB9 connector pin-out found on AlphaeH                    and Integrity COM serial ports-and on most PC systems+                    is listed in Table 14-6.   J           ________________________________________________________________$           Table 14-6  PC DB9 Pin-out  J                    _______________________________________________________J                    Pin_____Description____________________________________  4                    1       Data Carrier Detect (DCD)  (                    2       Received Data  (                    3       Transmit Data  4                    4       Data Terminal Ready (DTR)  !                    5       Groundg  /                    6       Data Set Ready (DSR)r  0                    7       Request To Send (RTS)  (                    8       Clear To Send  J           _________9_______floating_______________________________________  F                    The MicroVAX DB9 console connector pin-out predatesB                    the PC-style DB9 pin-out (adapters discussed inE                    Section 14.26), and uses a then-common (and older)sI                    standard pin-out, and uses the EIA-232 series standardi/                    signals shown in Table 14-7.d  J                                                                      14-57    i          '                    Hardware Informatione        J           ________________________________________________________________*           Table 14-7  MicroVAX DB9 Pin-out  J                    _______________________________________________________J                    Pin_____Description____________________________________  ,                    1       Protective Ground  *                    2       Transmited Data  (                    3       Received Data  0                    4       Request To Send (RTS)  4                    5       Data Terminal Ready (DTR)  /                    6       Data Set Ready (DSR)e  (                    7       Signal Ground  F                    8       Shorted to pin 9 on MicroVAX and VAXstation"                            2000...  J           _________9_______...series_systems,_otherwise_left_floating.____  F                    When pin 8 is shorted to pin 9, this is a BCC08 (orH                    variant) cable, most commonly used as a console cableJ                    on the MicroVAX 2000 and VAXstation 2000 series. (OtherJ                    systems may or may not tolerate connecting pin 8 to pin                    9.)  -                    The BN24H looks like this:r  &                         MMJ       RJ45  $                          1---------8$                          2---------2$                          3---------1$                          4---------3$                          5---------6$                          6---------7  -                    The BN24J looks like this:   &                         MMJ       RJ45  $                          1---------7$                          2---------6$                          3---------3$                          4---------1$                          5---------2$                          6---------8                      14-58               '                    Hardware InformationV                            Also see:  :                    o  http://www.hp.com/go/openvms/wizard/  :                    o  http://www.airborn.com.au/rs232.html  5                    o  http://www.stanq.com/cable.htmlm  E                    o  For adapters and connectors, see Section 14.26.   D           __________________________________________________________C           14.26  What connectors and wiring adapters are available?T  H                    The H8571-B and H8575-B convert the (non-2000-series)B                    MicroVAX DB9 to the DECconnect DEC-423 ModifiedD                    Modular Jack (MMJ) pin-out; to the MMJ DECconnectG                    wiring system. The MicroVAX 2000 and VAXstation 2000,G                    requires a BCC08 cable (which has the 8-9 short, seeiI                    Section 14.25) and the H8571-C or the H8571-D DB25-to-mI                    MMJ adapter for use with DECconnect. (For a discussiontH                    of the console bulkhead on the MicroVAX II series andF                    on other closely-related series systems, please see%                    Section 14.3.3.4.)u  H                    Somewhat less ancient HP (HP, Compaq or DIGITAL logo)D                    systems will use either the DECconnect MMJ wiringD                    directly or-on most (all?) recent system designs-H                    the PC-compatible DB9 9-pin pin-out; the PC-style COM8                    serial port interface and connection.  G                    There are two DB9 9-pin pin-outs, that of the H8571- E                    B and similar for the MicroVAX and other and older H                    systems, and that of the H8571-J for the PC-style COMJ                    port, AlphaStation, Integrity, and other newer systems.G                    The older MicroVAX DB9 and the PC-style DB9 pin-outst&                    are not compatible.  J           ________________________________________________________________<           Table 14-8  DECconnect MMJ Connectors and Adapters  J                    _______________________________________________________J                    Part________Converts_BC16E_MMJ_male_to_fit_into________  B                    H8571-A     EIA232 DB25 25-pin female (common).J                                Functionally similar to the H8575-A, thoughD                                the H8575-A has better ESD shielding.  J                                                                      14-59               '                    Hardware Informationr      J           ________________________________________________________________D           Table 14-8 (Cont.)  DECconnect MMJ Connectors and Adapters  J                    _______________________________________________________J                    Part________Converts_BC16E_MMJ_male_to_fit_into________  F                    H8571-B     Older MicroVAX (other than the MicroVAXI                                2000) DB9 EIA232 serial port. FunctionallylI                                similar to the H8575-B, though the H8575-B H                                has better ESD shielding. Note: Cannot beJ                                used on a PC, Alpha nor Integrity DB9 9-pin)                                connector.-  D                    H8571-C     25 pin DSUB Female to MMJ, Unfiltered  ?                    H8571-D     EIA232 25 pin male (modem-wired)   B                    H8571-E     25 pin DSUB Female to MMJ, Filtered  I                    H8571-J     PC, Alpha, Integrity 9 pin (DB9) male (PC-fJ                                style COM serial port) Note: Cannot be usedH                                on the older MicroVAX DB9 9-pin connector  E                    H8572-0     BC16E MMJ double-female (MMJ extender)0  B                    H8575-A     EIA232 DB25 25-pin female (common).J                                Functionally similar to the H8571-A, thoughD                                the H8575-A has better ESD shielding.  F                    H8575-B     Older MicroVAX (other than the MicroVAXI                                2000) DB9 EIA232 serial port. Functionally I                                similar to the H8571-B, though the H8575-B H                                has better ESD shielding. Note: Cannot beJ                                used on a PC, Alpha nor Integrity DB9 9-pin(                                connector  G                    H8575-D     25 Pin to MMJ with better ESD Protectione  @                    H8575-D     25 Pin to MMJ with better and ESD)                                Protection   A                    H8575-E     25 Pin Integrity rx2600 Management C                                Processor (MP) port to MMJ, with ESD )                                Protection   ;                    H8577-AA    6 pin Female MMJ to 8 pin MJr  F                    BC16E-**    MMJ cable with connectors, available inJ           _____________________various_lengths____________________________  H                    Numerous additional adapters and cables are availableG                    from the (now out of print) OPEN DECconnect BuildingP                      14-60    n          '                    Hardware Information         I                    Wiring Components and Applications Catalog, as well as :                    descriptions of the above-listed parts.  J                    The DECconnect wiring system has insufficient signalingG                    for modems, and particularly lacks support for modem #                    control signals.w  G                    The H8571-A and H8575-A are MMJ to DB25 (female) andiG                    other connector wiring diagrams and adapter-, cable-eD                    and pin-out-related discussions are available at:  :                    o  http://www.hp.com/go/openvms/wizard/  H                    Jameco has offered a USB-A to PS/2 Mini DIN 6 AdapterH                    (as part 168751), for those folks wishing to (try to)<                    use PS/2 Keyboards via USB-A connections.  I                    The LK463 USB keyboard is also a potential option, forsF                    those wishing to connect an OpenVMS keyboard to USBI                    systems or (via the provided adapter) to PS/2 systems.mF                    The LK463 provides the classic OpenVMS keyboard andF                    keyboard layout on USB-based system configurations,B                    including operations with the USB connection onI                    specific Alpha systems (and specifically on those withsG                    supported USB connections) and on Integrity servers.   I                    For information on the Alpha console COM port(s) or on A                    the VAX console port, please see Section 14.3.   D           __________________________________________________________;           14.27  What is flow control and how does it work?i  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 withtJ                    asynchronous serial line communications. XON/XOFF is anI                    in-band flow control, meaning that the flow control isw*                    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 linesw@                    (pins) are used to carry the CTS/RTS signals.  J                                                                      14-61 y  h          '                    Hardware Information         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 tosJ                    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.r  E                    DECnet Phase IV on OpenVMS VAX supports the use ofhB                    asynchronous serial communications as a networkD                    line; of asynch DECnet. The communication devicesC                    (eg. modems, and drivers) must not be configuredqD                    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 through F                    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 characterspI                    including the 8-bit characters. If data compression is J                    happening, it must reproduce the source stream exactly.J                    No addition or elimination of null characters, and full%                    data transparency.b  B                    An Ethernet network is rather different than anC                    asynchronous serial line. Ethernet specifies theiI                    control of data flow on a shared segment using CSMA/CDnI                    (Carrier Sense Multiple Access, with Collision Detect)sH                    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. TheiE                    station concurrently listens to its own signal, to H                    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 theyG                    collision, both stations will stop transmitting, andeG                    will back off and try again a little later. (You canmG                    see a log of this activity in the DECnet NCP networke                    counters.)                       14-62               '                    Hardware Information         I                    DECnet provides its own flow control, above and beyondnG                    the flow control of the physical layer (if any). TheiD                    end nodes handshake at the beginning to establishE                    a transmit window size-and a transmitter will only_F                    send that much data before stopping and waiting forG                    an acknowledgement. The acknowledgement is only sent J                    when the receiver has confirmed the packet is valid. (AI                    well-configured DECnet generally avoids triggering any D                    underlying (out-of-band) flow control mechanism.)  D           __________________________________________________________0           14.28  CD and DVD device requirements?  J                    Read access to DVD-ROM, DVD+R/RW, DVD-R/RW, CD-ROM, andJ                    CD-R/RW devices on ATAPI (IDE) connections is generallyJ                    handled transparently by SYS$DQDRIVER, and SYS$DQDRIVERD                    will transparently de-block the media-native 2048E                    byte disk blocks with the 512-byte blocks expected_=                    by OpenVMS and by native OpenVMS software.5  J                    Read access to DVD-ROM, DVD+R/RW, DVD-R/RW, CD-ROM, andI                    CD-R/RW devices on SCSI is handled by DKDRIVER, thoughoJ                    SYS$DKDRIVER will not transparently de-block the nativeJ                    2048-byte disk blocks into the 512-byte blocks expectedI                    by OpenVMS. The drive or external software is expectedAF                    to provide this de-blocking, thus either a 512-byteJ                    block capable drive (such as all RRD-series SCSI CD-ROMH                    drives) is required, or host software is required forH                    a 2048-byte block drive. Third-party SCSI drives withI                    UNIX references in their support documentation or with H                    explicit 512-byte selectors or swiches will generallyD                    (but not always, of course) operate with OpenVMS.  F                    At least some of the Plextor PlexWriter SCSI drivesI                    can be successfully accessed (for read and write) fromnF                    OpenVMS, as can at least one Pioneer SCSI DVD driveF                    (for CD media). The Pioneer SCSI DVD drive switchesF                    to 2048 byte blocks for DVD media, and a block-sizeG                    conversion tool (written by Glenn Everhart) or other /                    similar tool can be applied.a  I                    OpenVMS also has supported HP DVD drives for the ATAPIt                    (IDE) bus.E  J                                                                      14-63    t          '                    Hardware Information-        A                    For some related information (and details on a1<                    commercial DVDwrite package), please see:  C                    o  http://home.tiscali.de/dvd4openvms/supported_o#                       hardware.html   F                    No device driver currently presently permits directH                    block-oriented recording on DVD-RAM nor DVD+RW media,<                    nor other recordable or rewritable media.  B                    Recording (writing) of CD and DVD optical mediaF                    requires a recording or media mastering applicationJ                    or tool, and both commercial and non-commercial optionsH                    are available. See Section 9.7 for related details onI                    CDRECORD (both non-DVD and DVD versions are available,_E                    and at least one commercial version is available),uH                    and also see DVDwrite (commercial) or DVDRECORD (open                    source).   A                    For information on the GKDRIVER (SYS$GKDRIVER) I                    generic SCSI device driver and of the the IO$_DIAGNOSE H                    $qio[w] interfaces (of SYS$DKDRIVER, SYS$DNDRIVER andE                    SYS$DQDRIVER) that are utilized by most CD and DVD I                    recording tools to send commands to SCSI, USB or ATAPI G                    devices (most USB and ATA devices-or more correctly, I                    most ATAPI devices-can use SCSI-like command packets), H                    please see the SYS$EXAMPLES:GKTEST.C example, and seeG                    DECW$EXAMPLES:DECW$CDPLAYER.C example and please see E                    the various associated sections of the OpenVMS I/OO+                    User's Reference Manual.n  H                    For information on creating bootable optical media on5                    OpenVMS, please see Section 9.7.3.0                                          14-64 (  B                    J                    _______________________________________________________  7           15       Information on Networks and Clustersr      H                    The following sections contain information on OpenVMSG                    Networking with IP and DECnet, and on clustering andhE                    volume shadowing, on Fibre Channel, and on relatedn/                    products and configurations.u  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.   :                    o  http://www.hp.com/go/openvms/wizard/  D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the available_B                    ATW Wizard.zip archive, please see Section 3.8.  D           __________________________________________________________*           15.2  OpenVMS and IP Networking?  H                    The following sections contain information on OpenVMSD                    and IP networking, as well as IP printing topics.  '           _____________________________r9           15.2.1  How to connect OpenVMS to the Internet?n  D                    Some tutorial information and tips for connectingD                    OpenVMS systems to the Internet are available at:  5                    o  http://www.tmesis.com/internet/   '           _____________________________ .           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.   J                                                                       15-1    p          7                    Information on Networks and Clusters         F                    With current OpenVMS IP implementations, the choiceE                    of telnet or lpr/lpd really amounts to determining J                    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 directlyWH                    attached to the network. If your present printer doesI                    not have a NIC or a JetDirect, acquire an internal (ifyJ                    available) or external NIC or JetDirect. Or replace theI                    printer. And obviously, most any operating system thateE                    can serve its local printers usually also providesiD                    a client that can access remote network-connected                    printers.  C                    Please see the Ask The Wizard (ATW) area topics-IH                    starting with topic (1020)-for additional information0                    on IP-based network printing.  :                    o  http://www.hp.com/go/openvms/wizard/  D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the availableNB                    ATW Wizard.zip archive, please see Section 3.8.  J                    Please see Section 15.2.3 for information on Postscript                    printing.  '           _____________________________ C           15.2.3  How do I connect a PostScript printer via TCP/IP?   I                    Using TCP/IP Services (UCX) as the TCP/IP stack, it is.G                    possible to configure queues using the UCX$TELNETSYM0E                    (TCP/IP Services prior to V5.0) or TCPIP$TELNETSYM H                    (with V5.0 and later) in order to print to PostscriptI                    printers. This assumes however that the printer itself F                    can convert whatever is passed to it into somethingH                    intelligible. As an example, if the printer has an IP                      15-2     e          7                    Information on Networks and Clusters         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" -.2                        /PROCESSOR=UCX$TELNETSYM  -"                        my_ip_queue  A                    $ INITIALIZE/QUEUE/ON="123.456.789.101:9100" - 4                        /PROCESSOR=TCPIP$TELNETSYM  -"                        my_ip_queue  E                    The port number of 9100 is typical of HP JetDirect E                    cards but may be different for other manufacturers                     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,rG                    and the DCPS$STARTUP.TEMPLATE startup template file.i  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.hp.com/go/openvms/wizard/  D                    For additional information on the OpenVMS Ask TheG                    Wizard (ATW) area and for a pointer to the available G                    ATW Wizard.zip archive, please see Section 3.8. Also                     see:i  ,                    o  http://www.wotsit.org/  ?                    Please see Section 15.2.2 for pointers to an /                    introduction to IP printing.a  '           _____________________________tH           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/PERMANENTp  J                                                                       15-3 s   -- s  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: Mon, 11 Apr 2005 20:28:43 -0400l- From: JF Mezei <jfmezei.spamnot@teksavvy.com>o% Subject: OT: Race for dual core 8086s B Message-ID: <1113265709.5054c9add17bffdd710f2f6a4bd3f22e@teranews>  E AMD announced it would release dual core 64 bit 8086s. Now, Intel haseG leaked news that it may release its dual core 8086 before that, leaving  IA64 behind in the dust.  H Another example of how competition in the 8086 space will force Intel toE bring its 64 bit 8086 up and that it won't be able to keep the marketeH spaces for IA64 and 8086 separate for very long. Already IA64 was pushedD aside for workstation and low/mid range systems, leaving it only for "big iron" systems.p   ------------------------------    Date: 10 Apr 2005 22:41:30 -0700 From: mcbill20@yahoo.com8 Subject: Re: Procedure for installing PERL modules (LWP)C Message-ID: <1113198090.060117.103750@o13g2000cwo.googlegroups.com>X   Craig A. Berry wrote:  <snip> > ? > This depends on the definition of "work better."  If you need  mod_perlD > for performance reasons, then the rather ancient HP version is the onlyC > port I'm aware of.  If you just need Perl (which will do anythingiF > mod_perl will do but with more image activations), there are optionsE > that are likely to work better for what you are trying to do.  I'veA goteD > a VMS-friendly build-from-source kit for Perl 5.8.4 where you justE > submit a batch job to build and install, and some binary kits builtrE > from that kit.  These include some non-core extensions like LWP ande itsoC > dependencies as well as a number of VMS-specific extensions. Some  nice< > person made sure these kits got on the latest freeware CD: > 5 > http://h71000.www7.hp.com/freeware/freeware70/perl/n >iD > Send mail to vmsperl-subscribe AT perl DOT org to join discussions: > about porting and using Perl and Perl extensions on VMS.  E Thanks for the info. I'll take a lok at that kit. Do you know offhand @ if there should be any issues/problems with running two separateG versions of PERL? (That is, I'd like to keep the mod_perl and CSWS from < HP the way they are but use the newer PERL for other tings.)   Thanks.  Bill   ------------------------------  % Date: Mon, 11 Apr 2005 07:50:09 -0500s6 From: "Craig A. Berry" <craigberry@mac.com.spamfooler>8 Subject: Re: Procedure for installing PERL modules (LWP)D Message-ID: <craigberry-568F71.07500811042005@news.isp.giganews.com>  C In article <1113198090.060117.103750@o13g2000cwo.googlegroups.com>,I  mcbill20@yahoo.com wrote:   > Do you know offhandiB > if there should be any issues/problems with running two separateI > versions of PERL? (That is, I'd like to keep the mod_perl and CSWS fromI> > HP the way they are but use the newer PERL for other tings.)  F There should be no trouble at all.  Just define the PERL_ROOT logical 1 name differently for the different installations.n   ------------------------------  # Date: Mon, 11 Apr 2005 19:01:55 GMTv, From: "warren sander" <warren.sander@hp.com>" Subject: Re: Remote printing woes.1 Message-ID: <DQz6e.3479$VO.1766@news.cpqcorp.net>_  + while not an OpenVMS program. Get 'hoverip'A< http://www.hoverdesk.net/freeware.htm slide down to hover ip  J then on a windows system you can do a port scan of the printer to see what ports are open....   -warrenI  2 "David Gray" <police@spamcop.net> wrote in message2 news:jtlc51trvtad4bc77qkepck7ukgb739aib@4ax.com...
 > Hi John, >  > ? > On 6 Apr 2005 09:59:34 -0500, briggs@encompasserve.org wrote:_ >_F > >In article <2er75116f0k131tvja1cmc02tiqme062sv@4ax.com>, David Gray <police@spamcop.net> writes:# > >[David Dachtera (I think) asked]7J > >>>By the way: can you Telnet to the printer? ...on port 515? ...on port
 > >>>9100? > >>3 > >> No I cannot telnet to either of the two ports._ > >_? > >How quickly does the connection fail?  And with what status?t >wD > I don's have access to the firewall but I'm assured that telnet isE > enabled to ports 9100, 10001, 515 & 23.   Trying to connect to portoH > 515 fails immedialtely, the rest after about 10 seconds.  Entering the > password makes no difference.  > ! > TELNET> connect 209.92.84.20 23t+ > %TELNET-I-TRYING, Trying ... 209.92.84.20 ; > %TELNET-I-SESSION, Session 01, host 209.92.84.20, port 23 * > -TELNET-I-ESCAPE, Escape character is ^]! > Raptor Firewall Secure Gateway._ >_' > Cannot connect to destination system.4 > / > %TELNET-E-INETERROR, Internet interface error_E > -SYSTEM-F-CONNECFAIL, connect to network object timed-out or failed_ >s# > TELNET> connect 209.92.84.20 9100_+ > %TELNET-I-TRYING, Trying ... 209.92.84.20m= > %TELNET-I-SESSION, Session 01, host 209.92.84.20, port 9100 * > -TELNET-I-ESCAPE, Escape character is ^]/ > %TELNET-S-REMCLOSED, Remote connection closedo= > -TELNET-I-SESSION, Session 01, host 209.92.84.20, port 9100  > $ > TELNET> connect 209.92.84.20 10001+ > %TELNET-I-TRYING, Trying ... 209.92.84.20-> > %TELNET-I-SESSION, Session 01, host 209.92.84.20, port 10001* > ^}$[DET-I-ESCAPE, Escape character is ^]/ > %TELNET-E-INETERROR, Internet interface errornE > -SYSTEM-F-CONNECFAIL, connect to network object timed-out or failedi >a" > TELNET> connect 209.92.84.20 515+ > %TELNET-I-TRYING, Trying ... 209.92.84.20a< > %TELNET-I-SESSION, Session 01, host 209.92.84.20, port 515* > -TELNET-I-ESCAPE, Escape character is ^]/ > %TELNET-S-REMCLOSED, Remote connection closedf< > -TELNET-I-SESSION, Session 01, host 209.92.84.20, port 515	 > TELNET>a > 6 > I can telnet using DOS to port 23 without a problem. > F > >PING or TRACEROUTE will diagnose most routing issues not associated
 > >with ACLs.  >eC > I can TRACERT through to the printer without a problem but get no = > response from PING even though it's supposed to be allowed.  >  > Cheers > Dave.s >  > G > >With Unix and Multinet, the status that I get when the server is not1; > >listening on the specified port is "connection refused".- > >-J > >A router ACL (ICMP host unreachable, administratively prohibited) gives2 > >me a "No route to host" diagnostic on Multinet. > >- > > John Briggs  >    ------------------------------    Date: 11 Apr 2005 07:39:48 -0500; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler)C Subject: Re: RRD43 and CD-RW3 Message-ID: <Rrgj0KY6OyBH@eisner.encompasserve.org>i  v In article <d38f8m$jc$1@online.de>, helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) writes:J > I am almost 100% sure that I have successfully used once-writable CDs onH > an RRD43 connected to a VAX 4000/100A.  I also have an RRD43 connectedJ > to a DEC 3000/600, but it seems unable to read the SAME CDs.  On the oneE > hand, it is an ALPHA, not a VAX, and on the other hand it is now at G > 7.2-1 whereas the VAX is at 7.3.  On the other hand, I'm pretty sure  = > that the VAX console could read the CD (i.e. boot from it)._ > H > Since the CD is identical and the CD drive is the same model (RRD43), H > why does it work in one case and not the other?  VMS version?  Can it K > work on VAX and not on ALPHA?  Can it work from the console and not from   > VMS? > E    I've never been able to get any kind of writeable CD to read on anl,    RRD43.  I suspect you're mis-remembering.   ------------------------------  % Date: Mon, 11 Apr 2005 11:35:56 -0400 , From: "Richard Tomkins" <tomkinsr@istop.com> Subject: Re: RRD43 and CD-RW$ Message-ID: <425a9a1e$1_2@127.0.0.1>  I FWIW, I have just installed NetBSD 1.6 and then 2.0 on a MV3100 Model 10,B7 KA41-B, using a RRD43. The NetBSD came in as ISO imagest    burned using a Yamaha and Roxio.      H My past experience has shown that some CD-Writers do not have sufficientF strength in th elaser to adequately burn an image reliably. Most oftenL though, the problem is the media. A lot of inexpensive stuff refuses to work6 on CD-ROM drives. I typcally use Sony or Maxell media.      K Just came across this nice chart of CD-ROMS that work with DIGITAL systems._   Hope it's useful._      J Inofficial and incomplete list of third party cdroms that work with DEC's.  J --------------------------------------------------------------------------  
 31.03.2005  D This list is maintained by Dennis Grevenstein. email contact info isL "cdromlist@pcde.inka.de" You can find an up to date version of this document7 here: http://sites.inka.de/pcde/help/dec-cdrom-list.txt    I. Introduction   H The question "what cdrom will work with my old DEC?" is heard often. TheL problem is that non-x86 workstations and especially DEC's will normally needI special cdroms that support special features. Many vendors released theircI own branded cdroms for their hardware. But you will have to pay much more_J money to get a slow DEC branded cdrom for your workstation than for a fastK modern or a real cheap old standard cdrom drive. So here is some sort of anv@ answer for all who are looking for a third party cdrom for a DECE workstation. If the list gets longer(I hope so), I may release a html  version.       II. Some general information.e  E As most Unix workstations, DEC's will need a cdrom that is capable ofHF reading 512 bytes/sector, but most PC style cdrom's can only read 2048L bytes/sector. Often there is a jumper to enable this mode. If not, the cdromI must support the "MODE SELECT" command that is send by the PROM to enable I the 512 bytes/sector mode. But often, even if a cdrom supports all of the L above and can be used with other workstation platforms e.g. Sun and SGI, the& cdrom will not work with DEC hardware.      # III. drives that are known to work.   H I decided to differentiate between VAX, MIPS based DECstations and AlphaG based workstations because of some irregularities. The Alpha section is I pretty small right now and Alphas should be compatible with cdroms in thenI VAX or DECstation section, but a general rule could be: If a drive is nottF listed as working in your category, don't get it. Sometimes cdroms areE tested with more than one version of an OS. In these cases the oldestc; version that was bootet or installed succesfully is listed.r  	 III.1 VAXn  / Vendor model # operating system hardware tested_  L ----------------------------------------------------------------------------   -e  ' Apple CD300e VMS VAXstation, Infoserver1  L ----------------------------------------------------------------------------   -D  4 HP C2944D OpenVMS 6.2 uVAX 3100, VAXstation 4000/90,   4000/60, 4000/VLC   9 Note: Did not work with a VAXstation 3100/40. Be careful!r  L ----------------------------------------------------------------------------   -t  0 Matsushita CR-506-B VMS-5.5-2 VAXstation 3100/30  L ----------------------------------------------------------------------------   -t  * NEC Multispin 3xi OpenVMS 7.2 VAX 4000/300  L ----------------------------------------------------------------------------   -t  ' Panasonic CR506B VMS VAXstation 4000/90s  L ----------------------------------------------------------------------------   -t  ) Pioneer DR-U124X OpenVMS 7.2 uVAX 3100/80   L ----------------------------------------------------------------------------   -   ' Pioneer DR-U06S OpenVMS 6.1 various VAX   L ----------------------------------------------------------------------------   -   ( Pioneer DR-U12X OpenVMS 7.2 uVAX 3100/30  L ----------------------------------------------------------------------------   -   - Pioneer DR-466 OpenVMS 7.1 VAXstation 3100/30   L ----------------------------------------------------------------------------   -   & Plextor 12/20 OpenVMS 7.2 uVAX 3100/80  L ----------------------------------------------------------------------------   -C  . Plextor PX-63CS OpenVMS 7.2 VAXstation 3100/30  L ----------------------------------------------------------------------------   -_  9 Plextor PX-32TSi OpenVMS 7.1 uVAX3100, VAXstation 4000/60e   VAXstation 4000/90  L ----------------------------------------------------------------------------   -_  " Sony CDU541 VMS VAXstation 4000/90  L ----------------------------------------------------------------------------   -     Sony CDU561 Ultrix 4.5 uVAX 3100  L ----------------------------------------------------------------------------   -t  - Sony CDU-8012B OpenVMS 7.2 VAXstation 4000/90   3 Note: There is a Sun OEM Version of this drive too.   L ----------------------------------------------------------------------------   -_  , Toshiba XM-4101B OpenVMS 7.3 VAXstation 3100   Note: OEMed by DEC as RRD43-AA  L ----------------------------------------------------------------------------   -_  ( Toshiba XM-6401B OpenVMS 6.1 various VAX  L ----------------------------------------------------------------------------   -1  - Toshiba XM-5701TA OpenVMS 7.1 VAXstation 3100   L ----------------------------------------------------------------------------   -   ( Toshiba XM-5701B OpenVMS 6.1 various VAX  L ----------------------------------------------------------------------------   -n  ' Toshiba XM-5401 OpenVMS 6.2 various VAX   L ----------------------------------------------------------------------------   -   : Toshiba XM-3401B OpenVMS 7.1,Ultrix 4.5 VAXstation 3100/30  L ----------------------------------------------------------------------------   -   1 Toshiba TXM-3401E1 OpenVMS 7.2 VAXstation 4000/90t  + Note: Has problems reading hand made CD-R'sa  L ----------------------------------------------------------------------------   -o   Toshiba XM-3301B VMS uVAX 3100  L ----------------------------------------------------------------------------   -   ( Toshiba XM-3201B OpenVMS 7.2 various VAX  L ----------------------------------------------------------------------------   -   * Toshiba TXM-3301E1 OpenVMS 7.2 various VAX  L ----------------------------------------------------------------------------   -e       III.2 DECstations   G DECstations seem to be really tricky, especially if you want to install H Ultrix. Normally Ultrix/MIPS can only be installed using an original DECI cdrom. Typically your DECstation will boot of a compatible cdrom, but the J install programm will crash. If it is not compatible with a DECstation theL boot will fail completely. I can't say much about NetBSD, but my DR-466 doesH not work with NetBSD 1.4.1 at all, but works fine with NetBSD 1.5. OtherH people said that some older Toshiba cdroms work with VAXen, but not with DECstations.  / Vendor model # operating system hardware tested   L ----------------------------------------------------------------------------   -   2 Matsushita CR-503 NetBSD 1.4.1 DECstation 5000/260  L ----------------------------------------------------------------------------   -M  / Plextor PX-12CSi NetBSD 1.5 DECstation 5000/133J  L ----------------------------------------------------------------------------   -_  * Plextor PX-32TSi NetBSD DECstation 5000/33  L ----------------------------------------------------------------------------   -   - Pioneer DR-466 NetBSD 1.5 DECstation 5000/150   L ----------------------------------------------------------------------------   -   > Sony CDU-8012 Ultrix 4.2 and 4.5 DECstation 5000/260, 5000/150  / Note: Sun OEM Version Model 411 DECstation 2100t  J The old Sun model 411 cdrom seems to be special. It can be used to installL Ultrix/RISC and it is sometimes even detected as a DEC RRD42. However, it is: not any cheaper than a DEC branded cdrom when bought used.  L ----------------------------------------------------------------------------   -        III.3 Alphat  K There seems to be a special problem with older Plextor cdroms, even if theyd work with VAXen. Be careful.  / Vendor model # operating system hardware testedv  L ----------------------------------------------------------------------------   -r   Apple CD300e VMS DEC3000  L ----------------------------------------------------------------------------   -   $ NEC Multispin 4Xi OpenVMS 7.2 Multia  L ----------------------------------------------------------------------------   -e  ) Pioneer DR-U06S OpenVMS 7.1 various AlphaB  L ----------------------------------------------------------------------------   -    Pioneer DR-466 OSF1 3.2 DEC3000l  L ----------------------------------------------------------------------------   -n  , Plextor PX-40TSi VMS Multia,Alphastation 200  L ----------------------------------------------------------------------------   -i  9 Teac CDR58S OSF1 3.2,OpenVMS 7.2 DEC3000,AlphaServer1000Ae   Note: 8X CD-writer  L ----------------------------------------------------------------------------   -r  ) Toshiba XM-5401 OpenVMS 6.2 various Alpha,  L ----------------------------------------------------------------------------   -_  * Toshiba XM-5701B OpenVMS 7.1 various Alpha  L ----------------------------------------------------------------------------   -o  @ Toshiba XM-6401TA OpenVMS 6.2 PWS500au, Alphastation 400,DEC3000  L ----------------------------------------------------------------------------   -r  ? Toshiba XM-6401B OpenVMS 7.1 various Alpha, EXCEPT DEC 2000/300e  L ----------------------------------------------------------------------------   -a  ) Toshiba XM-3201 OpenVMS 7.2 various Alpha   L ----------------------------------------------------------------------------   -n  , Toshiba TXM-3301E1 OpenVMS 7.2 various Alpha  L ----------------------------------------------------------------------------   -n       IV. Other resources   F The Sun cdrom FAQ may be useful. It provides some general information,E allthough this FAQ does not care, if a cdrom works with DEC hardware.h   http://saturn.tlug.org/suncdfaqw      2 V. thanks, suggestions and all the other things...  9 Many thanks to all who contributed to build up this list.o  K This list is by no means complete. So if you have ever used a non-DEC cdromuK that is not shown here with a DEC workstation, please send some informationrH to "cdromlist@pcde.inka.de". If you have other suggestions or complains, feel free to mail them too.i       Regards, Richard Tomkins              / "AEF" <spamsink2001@yahoo.com> wrote in message = news:1113230378.428927.182100@g14g2000cwa.googlegroups.com...  >  > Ben Myers wrote:E > > From the experiences I have had with older CD-ROM drives, I woulde > have to agree C > > that the RRD43 is too old to read write-once CDs, let along the  > rewritable kind. >C >.D > Really? I read them on a regular basis on my RRD43 and have had noH > problems. The problem I *do* have is that I can't read the CD-R on theF > other drive that wrote it! (Well, on occasion I've gotten high errorI > counts but I attributed that to scratching of the CD-R's when they weredG > stacked on the pole. But I don't currently have this problem with the   > latest set of stacked CD-R's.) >h >t > [...]t >i      O ----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==----aS http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ NewsgroupseK ----= East and West-Coast Server Farms - Total Privacy via Encryption =----    ------------------------------    Date: 11 Apr 2005 08:40:12 -0700; From: "johnhreinhardt@yahoo.com" <johnhreinhardt@yahoo.com>a Subject: Re: RRD43 and CD-RWB Message-ID: <1113234012.093043.29400@g14g2000cwa.googlegroups.com>   Ben Myers wrote:C > From the experiences I have had with older CD-ROM drives, I would 
 have to agreenA > that the RRD43 is too old to read write-once CDs, let along thet rewritable kind. >  > ? > Anybody have experiences to report for the newer 12x RRD46, a  Toshiba-made unitaC > with DEC-specific firmware?  Do the RRD46's work on the older DEC  boxes?  If so,F > and upgrading from an RRD43 to an RRD46 is an option, I still have a
 few RRD46s   Ben,G   I have RRD46's in my AS800's and RRD47's in my AS1200's and both worknA just fine with CD-R's that I have made.  I have not tried a CD-RWa though on either.    ------------------------------  # Date: Mon, 11 Apr 2005 15:33:45 GMT 5 From: ben_myers_spam_me_not @ charter.net (Ben Myers)o Subject: Re: RRD43 and CD-RW0 Message-ID: <425a97fa.10968488@nntp.charter.net>  F Success reading media burned with a CD burner depends very much on theO tolerances an individual drive (both burner and reader) operates at, the choice P of media used for burning, and the operating system that reads the burned media.M Good that you have an exception there.  But I'll stick by the generalization,  granting the exceptions.  O Another generalization with some likely exceptions:  The newer the CD-ROM drivenB the more likely it is to read burned CDs successfully... Ben Myers  D On 11 Apr 2005 07:39:38 -0700, "AEF" <spamsink2001@yahoo.com> wrote:   >  >Ben Myers wrote: D >> From the experiences I have had with older CD-ROM drives, I would >have to agreeB >> that the RRD43 is too old to read write-once CDs, let along the >rewritable kind.a >a >hC >Really? I read them on a regular basis on my RRD43 and have had nonG >problems. The problem I *do* have is that I can't read the CD-R on the E >other drive that wrote it! (Well, on occasion I've gotten high errorkH >counts but I attributed that to scratching of the CD-R's when they wereF >stacked on the pole. But I don't currently have this problem with the >latest set of stacked CD-R's.)  >  >  >[...] >u   ------------------------------  % Date: Mon, 11 Apr 2005 17:01:53 +0100_- From: John Laird <nospam@laird-towers.org.uk>  Subject: Re: RRD43 and CD-RW8 Message-ID: <bl7l51tpdo48b1suve7ugp6c79b1q5q6ql@4ax.com>  9 On 11 Apr 2005 08:40:12 -0700, "johnhreinhardt@yahoo.com"/! <johnhreinhardt@yahoo.com> wrote:n   >Ben Myers wrote: D >> From the experiences I have had with older CD-ROM drives, I would >have to agreeB >> that the RRD43 is too old to read write-once CDs, let along the >rewritable kind.k >> >>@ >> Anybody have experiences to report for the newer 12x RRD46, a >Toshiba-made unitD >> with DEC-specific firmware?  Do the RRD46's work on the older DEC >boxes?  If so, G >> and upgrading from an RRD43 to an RRD46 is an option, I still have a  >few RRD46s  >  >Ben,DH >  I have RRD46's in my AS800's and RRD47's in my AS1200's and both workB >just fine with CD-R's that I have made.  I have not tried a CD-RW >though on either.  I I've had no trouble with CD-R's in RRD-43s (or their Toshiba equivalent).-H Seem to recall reading somewhere that quad-speed drives and up should beE okay with recordable media, but there's no reliable rule of thumb forrD rewriteable ones (my car player is fine, but a newer hi-fi box failsI dismally).  For safety, even if there is no scientific evidence, I alwayssJ record audio and data CDs intended for older players/drives at low speeds. (4x typically).w   -- i- Ask not what your computer can do for you... s   Mail john rather than nospam...    ------------------------------    Date: 11 Apr 2005 11:32:20 -0700; From: "johnhreinhardt@yahoo.com" <johnhreinhardt@yahoo.com>  Subject: Re: RRD43 and CD-RWB Message-ID: <1113244340.885794.18880@z14g2000cwz.googlegroups.com>   Ben Myers wrote:C > From the experiences I have had with older CD-ROM drives, I would8
 have to agreerA > that the RRD43 is too old to read write-once CDs, let along ther rewritable kind. >r >o? > Anybody have experiences to report for the newer 12x RRD46, a  Toshiba-made unitVC > with DEC-specific firmware?  Do the RRD46's work on the older DEC  boxes?  If so,F > and upgrading from an RRD43 to an RRD46 is an option, I still have a
 few RRD46s  E I have a couple RRD46's and some RRD47's and they all read the CD-R's G that I've made without a problem.  I have not tried any CD-RW's though.c   ------------------------------  # Date: Mon, 11 Apr 2005 19:23:55 GMTh# From: hoff@hp.nospam (Hoff Hoffman)o Subject: Re: RRD43 and CD-RW1 Message-ID: <f9A6e.3483$4D.3241@news.cpqcorp.net>r  v In article <d38f8m$jc$1@online.de>, helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) writes:  F :...once-writable CDs on an RRD43 ... but it seems unable to read the E :SAME CDs...  Since the CD is identical and the CD drive is the same  B :model (RRD43), why does it work in one case and not the other?...  H   Older CD drives can tend to have problems with newer CD writeable and G   CD rewriteable media, in my experience.  The media reflectivity of atRI   least some of the writeable and rewriteable substrates is comparatively J   marginal, and as the older CD-ROM drives were centrally designed for theH   CD-ROM format and reflectivity.  (Looking at the specs and at how thisH   recording stuff was retrofit, it is somewhat amazing to me that it allH   works as well as it does.  But I digress.)  This can lead to the usualH   drive-specific "fun", and to cases where some media is not readable in   a whole group of drives.  F   I'd look at a different recording media formulation, and potentially6   at a different recording drive for the media source.  F   As for upgrades, I've had success with the Plextor PlexWriter seriesD   SCSI CD-R/RW drives, as have some other folks.  A newer RRD-seriesF   drive or newer SCSI CD-ROM drive would be another obvious option forC   an upgrade, and will be somewhat cheaper than a SCSI CD-recorder.   G   And the obvious test -- find out if the problem moves with the drive, ;   or with the system.  I'd tend to assume the former, here.   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.comd   ------------------------------    Date: 11 Apr 2005 13:57:20 -0700+ From: williams.dan@gmail.com (Dan Williams)o Subject: Re: RRD43 and CD-RW= Message-ID: <26c11a64.0504111257.3959ba45@posting.google.com>r  G >    I've never been able to get any kind of writeable CD to read on anu. >    RRD43.  I suspect you're mis-remembering.  S I've copied licenses to a cd and read them in whilst installing on a few occasions.    Dan    ------------------------------  % Date: Mon, 11 Apr 2005 18:12:18 -0400 , From: "Richard Tomkins" <tomkinsr@istop.com> Subject: Re: RRD43 and CD-RW$ Message-ID: <425af704$3_2@127.0.0.1>  K I wonder if those new LightScribe drives with the high power lasers from HPW might burn really well?a  8 "Dan Williams" <williams.dan@gmail.com> wrote in message7 news:26c11a64.0504111257.3959ba45@posting.google.com..._I > >    I've never been able to get any kind of writeable CD to read on ann0 > >    RRD43.  I suspect you're mis-remembering. >sJ > I've copied licenses to a cd and read them in whilst installing on a few
 occasions. >  > Dang      O ----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==----OS http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups K ----= East and West-Coast Server Farms - Total Privacy via Encryption =----a   ------------------------------  # Date: Mon, 11 Apr 2005 22:42:02 GMT # From: hoff@hp.nospam (Hoff Hoffman)  Subject: Re: RRD43 and CD-RW2 Message-ID: <_2D6e.3524$y21.1086@news.cpqcorp.net>  S In article <425af704$3_2@127.0.0.1>, "Richard Tomkins" <tomkinsr@istop.com> writes:aL :I wonder if those new LightScribe drives with the high power lasers from HP :might burn really well?  5   I'm not certain of the intent of the cited comment.   G   The LightScribe drives probably won't help an RRD43 with its problemsIC   reading from non-pressed media -- older CD drives can and do have H   problems reading newer recordable media.  Sometimes there are firmwareF   upgrades, and sometimes you end up swapping the drive, and sometimesF   you can find a media formulation that the particular drive can read.  G   At its most hideously simple, CD and DVD drives work by using a laseriE   diode to read the different reflectance of a pit and a flat spot on D   mechanically pressed substrate, and recordable media simulates theH   appearance of these physical pits and these flat spots through changes3   to the optical substrate of the recordable media.n  I   Like the groove on each side of a classic pressed vinyl album (and I'llnI   ignore discussions of that three-grooved Monty Python album -- and no, iG   I'm not parting with my copy), there is a single spiral track on eachaH   side of CD and DVD media, and a pattern of pits and flat spots records:   the data (or the sound, the movie or...) onto the track.  H   If the RRD43 cannot properly detect what look like pits, then the diskH   will not be particularly readable.  This could be due to the media, orG   to problems with the drive, or yes, possibly with the recorder.  EvenmH   the best recorder on the market cannot necessarily counteract problemsG   within the reader or within the media -- accordingly, my first target A   for a device swap would be the CD reader and not the CD writer.   N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faqbN  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.comk   ------------------------------  # Date: Tue, 12 Apr 2005 01:14:57 GMTa5 From: ben_myers_spam_me_not @ charter.net (Ben Myers)  Subject: Re: RRD43 and CD-RW0 Message-ID: <425b20ee.46033297@nntp.charter.net>  N I can't help but comment that this explanation is the pits!  :)  ... Ben Myers  F On Mon, 11 Apr 2005 22:42:02 GMT, hoff@hp.nospam (Hoff Hoffman) wrote:  T >In article <425af704$3_2@127.0.0.1>, "Richard Tomkins" <tomkinsr@istop.com> writes:M >:I wonder if those new LightScribe drives with the high power lasers from HP  >:might burn really well?o >o6 >  I'm not certain of the intent of the cited comment. >nH >  The LightScribe drives probably won't help an RRD43 with its problemsD >  reading from non-pressed media -- older CD drives can and do haveI >  problems reading newer recordable media.  Sometimes there are firmwarelG >  upgrades, and sometimes you end up swapping the drive, and sometimes G >  you can find a media formulation that the particular drive can read.  > H >  At its most hideously simple, CD and DVD drives work by using a laserF >  diode to read the different reflectance of a pit and a flat spot onE >  mechanically pressed substrate, and recordable media simulates theSI >  appearance of these physical pits and these flat spots through changes 4 >  to the optical substrate of the recordable media. > J >  Like the groove on each side of a classic pressed vinyl album (and I'llJ >  ignore discussions of that three-grooved Monty Python album -- and no, H >  I'm not parting with my copy), there is a single spiral track on eachI >  side of CD and DVD media, and a pattern of pits and flat spots recordse; >  the data (or the sound, the movie or...) onto the track.u >sI >  If the RRD43 cannot properly detect what look like pits, then the diskrI >  will not be particularly readable.  This could be due to the media, oriH >  to problems with the drive, or yes, possibly with the recorder.  EvenI >  the best recorder on the market cannot necessarily counteract problemssH >  within the reader or within the media -- accordingly, my first targetB >  for a device swap would be the CD reader and not the CD writer. >tO > ---------------------------- #include <rtfaq.h> -----------------------------rL >    For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faqO > --------------------------- pure personal opinion ---------------------------mF >        Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.com >a   ------------------------------  # Date: Tue, 12 Apr 2005 03:42:07 GMTe5 From: ben_myers_spam_me_not @ charter.net (Ben Myers)  Subject: Re: RRD43 and CD-RW0 Message-ID: <425b432b.54800492@nntp.charter.net>  P Right.  I had assumed that the RRD46's would be new enough to read CDs burned on! decent quality media... Ben Myers_  C On Tue, 12 Apr 2005 03:40:35 GMT, John Santos <john@egh.com> wrote:    >Ben Myers wrote: R >> From the experiences I have had with older CD-ROM drives, I would have to agreeS >> that the RRD43 is too old to read write-once CDs, let along the rewritable kind.R >> G >> .R >> Anybody have experiences to report for the newer 12x RRD46, a Toshiba-made unitS >> with DEC-specific firmware?  Do the RRD46's work on the older DEC boxes?  If so,-R >> and upgrading from an RRD43 to an RRD46 is an option, I still have a few RRD46sS >> in my warehouse, gleaned from a lot of DEC gear that Compaq sold off a few years-I >> ago.  At this point, I don't need tons of money to part with them.  If[P >> interested, contact me off-line.  Shipping costs may be important, and I'm in- >> the U.S... Ben Myers ben_myers@charter.netc >>   >jD >How old is "older"?  I once bought a lot of 3 RRD46's on Ebay.  PutG >two of them in AlphaStation 200 4/100's (one VMS and one DEC Unix) andoG >the third I hooked up to an HSD05 on connected to a VAX 4000-200.  AlllE >work fine.  Definitely can boot the Alphas from them.  I think I canxA >boot the VAX as well, but it's been a real long time, so I'm notn	 >certain.t >8G >I'm pretty sure we used an RRD46 (another one, on an AlphaServer 1200)0E >recently to test reading a CD-R that was burned on a PC.  Don't knowo >what brand CD-R, etc. >, >aN >> On 11 Apr 2005 07:39:48 -0500, koehler@eisner.nospam.encompasserve.org (Bob >> Koehler) wrote: >> 7 >> ry >>>In article <d38f8m$jc$1@online.de>, helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) writes:g >>>wL >>>>I am almost 100% sure that I have successfully used once-writable CDs onJ >>>>an RRD43 connected to a VAX 4000/100A.  I also have an RRD43 connectedL >>>>to a DEC 3000/600, but it seems unable to read the SAME CDs.  On the oneG >>>>hand, it is an ALPHA, not a VAX, and on the other hand it is now atwI >>>>7.2-1 whereas the VAX is at 7.3.  On the other hand, I'm pretty sure e? >>>>that the VAX console could read the CD (i.e. boot from it).y >>>>J >>>>Since the CD is identical and the CD drive is the same model (RRD43), J >>>>why does it work in one case and not the other?  VMS version?  Can it M >>>>work on VAX and not on ALPHA?  Can it work from the console and not from r >>>>VMS? >>>> >>>nG >>>  I've never been able to get any kind of writeable CD to read on ana. >>>  RRD43.  I suspect you're mis-remembering. >>>w >> / >> n >i >  >--  >John Santos >Evans Griffiths & Hart, Inc.o >781-861-0670 ext 539    ------------------------------  # Date: Tue, 12 Apr 2005 03:40:35 GMT.  From: John Santos <john@egh.com> Subject: Re: RRD43 and CD-RW+ Message-ID: <TqH6e.12139$9i7.6663@trnddc04>e   Ben Myers wrote:Q > From the experiences I have had with older CD-ROM drives, I would have to agreeuR > that the RRD43 is too old to read write-once CDs, let along the rewritable kind. >  > Q > Anybody have experiences to report for the newer 12x RRD46, a Toshiba-made unitmR > with DEC-specific firmware?  Do the RRD46's work on the older DEC boxes?  If so,Q > and upgrading from an RRD43 to an RRD46 is an option, I still have a few RRD46s0R > in my warehouse, gleaned from a lot of DEC gear that Compaq sold off a few yearsH > ago.  At this point, I don't need tons of money to part with them.  IfO > interested, contact me off-line.  Shipping costs may be important, and I'm ino, > the U.S... Ben Myers ben_myers@charter.net >   C How old is "older"?  I once bought a lot of 3 RRD46's on Ebay.  Put F two of them in AlphaStation 200 4/100's (one VMS and one DEC Unix) andF the third I hooked up to an HSD05 on connected to a VAX 4000-200.  AllD work fine.  Definitely can boot the Alphas from them.  I think I can@ boot the VAX as well, but it's been a real long time, so I'm not certain.  F I'm pretty sure we used an RRD46 (another one, on an AlphaServer 1200)D recently to test reading a CD-R that was burned on a PC.  Don't know what brand CD-R, etc.     M > On 11 Apr 2005 07:39:48 -0500, koehler@eisner.nospam.encompasserve.org (Bob  > Koehler) wrote:l >  > x >>In article <d38f8m$jc$1@online.de>, helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) writes: >>K >>>I am almost 100% sure that I have successfully used once-writable CDs oncI >>>an RRD43 connected to a VAX 4000/100A.  I also have an RRD43 connectedaK >>>to a DEC 3000/600, but it seems unable to read the SAME CDs.  On the one>F >>>hand, it is an ALPHA, not a VAX, and on the other hand it is now atH >>>7.2-1 whereas the VAX is at 7.3.  On the other hand, I'm pretty sure > >>>that the VAX console could read the CD (i.e. boot from it). >>>pI >>>Since the CD is identical and the CD drive is the same model (RRD43), iI >>>why does it work in one case and not the other?  VMS version?  Can it  L >>>work on VAX and not on ALPHA?  Can it work from the console and not from  >>>VMS?9 >>>4 >>F >>  I've never been able to get any kind of writeable CD to read on an- >>  RRD43.  I suspect you're mis-remembering.r >> >  >      -- _ John Santost Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------  # Date: Mon, 11 Apr 2005 11:26:37 GMTt! From: Nigel Barker <nigel@hp.com>s Subject: Re: Site down?28 Message-ID: <48nk515m6nivekpo6ku69la0lvo59qio7i@4ax.com>  : On Mon, 11 Apr 2005 11:23:20 +0200, Jean-Franois Pironne  <jf.pieronne@laposte.net> wrote:   >David J Dachtera wrote:  >> Jean-Franois Pironne wrote: >> T >[snip]E >> ,J >> With a little chicanery, you could probably finagle a way to manipulateG >> the hardware flowcontrol signals of a serial port to operate a relayOK >> that would temporarily interrupt power to the DSL modem. Otherwise, JF'saF >> suggestions about X10 would be one way to go, especially if you are+ >> considering a larger automation project.- >> r >i
 >What is X10?N  L It is a home automation protocol. Allows you to operate lights etc by remote? control or by computer. Check out http://www.x10.com/home2.htmlE  I Googling comp.os.vms I found some pointers to VMS software to control X10c devices  http://groups-beta.google.com/group/comp.os.vms/browse_frm/thread/dc9c34c397e636c1/d2822d3836ff8670?q=openvms+x10&rnum=1#d2822d3836ff8670P   -- Nigel Barker Live from the sunny Cote d'Azuro   ------------------------------  # Date: Mon, 11 Apr 2005 17:04:52 GMTw! From: Nigel Barker <nigel@hp.com>p Subject: Re: Site down?h8 Message-ID: <ofbl515ou219o9eikm37bspgettrr6o0v6@4ax.com>  D On Mon, 11 Apr 2005 11:26:37 GMT, Nigel Barker <nigel@hp.com> wrote:  ; >On Mon, 11 Apr 2005 11:23:20 +0200, Jean-Franois Pironnee! ><jf.pieronne@laposte.net> wrote:o >u >>David J Dachtera wrote:y! >>> Jean-Franois Pironne wrote:t >>>  >>[snip] >>> K >>> With a little chicanery, you could probably finagle a way to manipulate H >>> the hardware flowcontrol signals of a serial port to operate a relayL >>> that would temporarily interrupt power to the DSL modem. Otherwise, JF'sG >>> suggestions about X10 would be one way to go, especially if you area, >>> considering a larger automation project. >>>  >> >>What is X10? > M >It is a home automation protocol. Allows you to operate lights etc by remoten@ >control or by computer. Check out http://www.x10.com/home2.html > J >Googling comp.os.vms I found some pointers to VMS software to control X10 >devices >http://groups-beta.google.com/group/comp.os.vms/browse_frm/thread/dc9c34c397e636c1/d2822d3836ff8670?q=openvms+x10&rnum=1#d2822d3836ff8670  
 Jean-Franoise   Aussi une site francaise? http://www.maison-intelligente.fr/boutique/index.asp?motcle=x10    -- Nigel Barker Live from the sunny Cote d'Azura   ------------------------------  % Date: Mon, 11 Apr 2005 23:51:18 +0200A1 From: =?ISO-8859-1?Q?Jean-Fran=E7ois_Pi=E9ronne?=M Subject: Re: Site down?n7 Message-ID: <425af15a$0$19312$8fcfb975@news.wanadoo.fr>R   Nigel Barker wrote: F > On Mon, 11 Apr 2005 11:26:37 GMT, Nigel Barker <nigel@hp.com> wrote: >  > < >>On Mon, 11 Apr 2005 11:23:20 +0200, Jean-Franois Pironne" >><jf.pieronne@laposte.net> wrote: >> >> >>>David J Dachtera wrote: >>>a! >>>>Jean-Franois Pironne wrote:e >>>> >>>M	 >>>[snip]  >>> K >>>>With a little chicanery, you could probably finagle a way to manipulatemH >>>>the hardware flowcontrol signals of a serial port to operate a relayL >>>>that would temporarily interrupt power to the DSL modem. Otherwise, JF'sG >>>>suggestions about X10 would be one way to go, especially if you areu, >>>>considering a larger automation project. >>>> >>>  >>>What is X10?  >>N >>It is a home automation protocol. Allows you to operate lights etc by remoteA >>control or by computer. Check out http://www.x10.com/home2.html  >>K >>Googling comp.os.vms I found some pointers to VMS software to control X10-	 >>devices- >>http://groups-beta.google.com/group/comp.os.vms/browse_frm/thread/dc9c34c397e636c1/d2822d3836ff8670?q=openvms+x10&rnum=1#d2822d3836ff8670n >  >  > Jean-Franoisf >  > Aussi une site francaiseA > http://www.maison-intelligente.fr/boutique/index.asp?motcle=x10  >   , Thanks for the pointers, I will take a look.   > -- > Nigel Barker! > Live from the sunny Cote d'Azure  
 Jean-Franoisi   ------------------------------  # Date: Mon, 11 Apr 2005 13:05:39 GMTo( From: "Hein" <hein.nomail@hp.nomail.com># Subject: Re: Sort Directory by Date 1 Message-ID: <DCu6e.3417$6n.2742@news.cpqcorp.net>o  ? "Martin Vorlaender" <martin@radiogaga.harz.de> wrote in messages5 news:42577546.524144494f47414741@radiogaga.harz.de...r) > Hein <hein.nomail@hp.nomail.com> wrote:c) > > Btw Peter...  your stuff shows up in:tD > > http://www.pdv-systeme.de/users/martinv/VMS_Programming_FAQ.html >rG > While following this thread, I dug through my archives and found thisaC > jewel again which probably is the great-grandfather of it all ;-)    Hey, that's me! Cute!  :-).rK I actually found and earlier reference in an Digital/HP internal notes filetL COMMAND_PROCEDURES, topic 745, Feb-1991 by Eric Osman. A question was raisedL but unanswerred in that note, as to why use the last 2 chars, not all three,J for the month collating sequence. Well, surely that is because of July andK June having the same leading two chars, so that would require 3 chars. ThatiG actual start byte does not matter, as long as it is unique (JAN/JUN and K APR/MAR have the same 3rd char in english:-). Two chars compare quicker anda< write quicker, but may indeed not be worth the obfuscation .  F Anyway.... all this to report that Guy Peleg picked up on this, and isL considering/investigating to put some sort functions (dates, sizes) directlyI into Directory. No promisses/commitments, but Guy has been coming throughsI very nively indeed in the past. Your cards, letters (and perhpas beers ate2 the bootcamp) for Guy are surely appreciated. :-).    ? > From: vandenheuvel@eps.enet.dec.com (Hein RMS van den Heuvel)- > Date: 18 JUN 96 00:08:03 :V) > $ sort 'tmp' sys$output:/spec=sys$input- > /collating_sequence= >-G (sequence=("AN","EB","AR","PR","AY","UN","UL","UG","EP","CT","OV","EC",V   ------------------------------  % Date: Mon, 11 Apr 2005 13:16:04 -0400a4 From: "Peter Weaver" <newsgroup@weaverconsulting.ca># Subject: Re: Sort Directory by Date-, Message-ID: <3bvpmoF6hqptjU1@individual.net>   Hein wrote:iA > "Martin Vorlaender" <martin@radiogaga.harz.de> wrote in message-7 > news:42577546.524144494f47414741@radiogaga.harz.de... * >> Hein <hein.nomail@hp.nomail.com> wrote:) >>> Btw Peter...  your stuff shows up in:-D >>> http://www.pdv-systeme.de/users/martinv/VMS_Programming_FAQ.html >>H >> While following this thread, I dug through my archives and found thisD >> jewel again which probably is the great-grandfather of it all ;-) >- > Hey, that's me! Cute!  :-).-  4 And very nice too. Way better than anything I write.  B > I actually found and earlier reference in an Digital/HP internalE > notes file COMMAND_PROCEDURES, topic 745, Feb-1991 by Eric Osman. A E > question was raised but unanswerred in that note, as to why use the-F > last 2 chars, not all three, for the month collating sequence. Well,E > surely that is because of July and June having the same leading two G > chars, so that would require 3 chars. That actual start byte does not-D > matter, as long as it is unique (JAN/JUN and APR/MAR have the sameF > 3rd char in english:-). Two chars compare quicker and write quicker,/ > but may indeed not be worth the obfuscation .   F My first attempt I used all three characters and the sort bombed, so ID checked the documentation and it states that you can only use one orF two characters. Then I noticed that the documentation had a sample forF sorting by months with the second and third characters so I copied it.   > H > Anyway.... all this to report that Guy Peleg picked up on this, and isE > considering/investigating to put some sort functions (dates, sizes)eE > directly into Directory. No promisses/commitments, but Guy has beensD > coming through very nively indeed in the past. Your cards, lettersE > (and perhpas beers at the bootcamp) for Guy are surely appreciated.  > :-).   Great!  < Well, here are my two procedures one using the LNM$DT_FORMATG (which I posted last year and which started this thread) and one not. I1J struggled with this for several hours Friday night, the /OMIT line did notC work at all when I first tried it, then it worked if I took out the06 /COLLATING_SEQUENCE. Then I found that by changing theA /COLLATING_SEQUENCE to different values the /OMIT would sometimesrJ work and sometimes not. After checking the documentation for the 10th timeD I added the FOLD and TIE_BREAK commands and it just started working.J I am not sure if both of these are needed, but I see that Hein's procedure only has the FOLD.  M I sent these to Norm Friday night and this morning he responded with one last-D fix that added in FILENAME3 to replace my use of the NULL character.  F Hope someone finds these useful, but next time someone sends me a noteN saying "I found this procedure you posted last year and I was wondering if you3 could change it to..." I am just going to say "No."-    6 $! ------------------ CUT HERE -----------------------/ $ v='f$verify(f$trnlnm("SHARE_UNPACK_VERIFY"))'2 $! $! This archive created: $!  Name : SORT_DIR-% $!  By   : peter@weaverconstulting.ca-" $!  Date : 11-APR-2005 12:55:47.87I $!  Using: VMS_SHARE 8.5-1, (C) 1993 Andy Harper, Kings College London UK- $!: $! Credit is due to these people for their original ideas:" $!    James Gray, Michael Bednarek $! $! To unpack this archive:A $!    Minimum of VMS 4.4 (VAX) / OpenVMS 1.0 (Alpha) is required.DB $!    Remove the headers of the first part, up to `cut here' line.* $!    Execute file as a command procedure. $!9 $! The following file(s) will be created after unpacking:l/ $!       1. [.TMP]SORT_DIR_BY_DATE_NORMAL.COM;367 $!       2. [.TMP]SORT_DIR_BY_DATE_WITH_DT_FORMAT.COM;1  $! $ set="set"O% $ set symbol/scope=(nolocal,noglobal)b* $ f="SYS$SCRATCH:."+f$getjpi("","PID")+";"/ $ if f$trnlnm("SHARE_UNPACK") .nes. "" then $ -a!  f=f$parse("SHARE_UNPACK_TEMP",f)-$ $ e="write sys$error  ""%UNPACK"", "$ $ w="write sys$output ""%UNPACK"", "6 $ if .not. f$trnlnm("SHARE_UNPACK_LOG") then $ w = "!"/ $ if f$getsyi("CPU") .gt. 127 then $ goto start- $ ve=f$getsyi("version")7 $ if ve-f$extract(0,1,ve) .ges. "4.4" then $ goto start-* $ e "-E-OLDVER, Must run at least VMS 4.4" $ v=f$verify(v)-	 $ exit 44 M $unpack:subroutine!P1=file,P2=chksum,P3=attrib,P4=size,P5=fileno,P6=filetotal-+ $ if f$parse(P1) .nes. "" then $ goto dirok  $ dn=f$parse(P1,,,"DIRECTORY")) $ w "-I-CREDIR, Creating directory ''dn'"- $ create/dir 'dn'- $ if $status then $ goto dirok8 $ e "-E-CREDIRFAIL, Unable to create ''dn' File skipped"
 $ delete 'f'*0 $ exit $dirok:  $ x=f$search(P1)' $ if x .eqs. "" then $ goto file_absent + $ e "-W-EXISTS, File ''P1' exists. Skipped" 
 $ delete 'f'*r $ exit
 $file_absent:iL $ w "-I-UNPACK, Unpacking ", P5, " of ", P6, " - ", P1, " - ", P4, " Blocks" $ n=P1 $ if P3 .nes. "" then $ n=f-7 $ if .not. f$verify() then $ define/user sys$output nl:-: $ EDIT/TPU/NOSEC/NODIS/COM=SYS$INPUT/NOJOURNAL 'f'/OUT='n'J PROCEDURE GetHex(s,p)LOCAL x1,x2;x1:=INDEX(t,SUBSTR(s,p,1))-1;x2:=INDEX(t,N SUBSTR(s,p+1,1))-1;RETURN 16*x1+x2;ENDPROCEDURE;PROCEDURE SkipPartsep LOCAL m;J LOOP m:=MARK(NONE);EXITIF m=END_OF(CURRENT_BUFFER);DELETE(m);EXITIF INDEX(6 ERASE_LINE,"-+-+-+-+-+-+-+-+")=1;ENDLOOP;ENDPROCEDURE;O PROCEDURE ProcessLine LOCAL c,s,l,b,n,p;s := ERASE_LINE;c := SUBSTR(s,1,1);s :=MN  s-c;IF c = "X" THEN SPLIT_LINE; ENDIF;MOVE_HORIZONTAL(-1);l := LENGTH(s);p :=M  1;LOOP EXITIF p > l;c := SUBSTR(s,p,1);p := p+1;CASE c FROM ' ' TO '`' ['`']-H : COPY_TEXT(ASCII(GetHex(s,p))); p:=p+2;[' ']: p:=p+1;[INRANGE,OUTRANGE]G : COPY_TEXT(c);ENDCASE;ENDLOOP;ENDPROCEDURE;PROCEDURE Decode(b)LOCAL m;-J POSITION(BEGINNING_OF(b));LOOP m:=MARK(NONE);EXITIF m=END_OF(b);DELETE(m);N IF INDEX(CURRENT_LINE,"+-+-+-+-+-+-+-+-")=1 THEN SkipPartSep;ELSE ProcessLine;N MOVE_HORIZONTAL(1);ENDIF;ENDLOOP;ENDPROCEDURE;SET(FACILITY_NAME,"UNPACK");SET(F SUCCESS,OFF);SET(INFORMATIONAL,OFF);t:="0123456789ABCDEF";f:=GET_INFO(G COMMAND_LINE,"file_name");o:=CREATE_BUFFER(f,f);Decode(o);WRITE_FILE(o,a+ GET_INFO(COMMAND_LINE,"output_file"));QUIT;- $ if p3 .eqs. "" then $ goto dl- $ open/write fdl &f  $ write fdl "RECORD" $ write fdl P3 $ close fdl-2 $ w "-I-CONVRFM, Converting record format to ", P3 $ convert/fdl='f' 'f'-1 'f'o% $ fa=f$getdvi(f$parse(f),"ALLDEVNAM")l& $ Pa=f$getdvi(f$parse(P1),"ALLDEVNAM")/ $ if fa .eqs. Pa then $ rename &f 'f$parse(P1)'-- $ if fa .nes. Pa then $ copy &f 'f$parse(P1)'7 $dl: delete 'f'* $ checksum 'P1'0( $ if checksum$checksum .nes. P2 then $ --   e "-E-CHKSMFAIL, Checksum of ''P1' failed."  $ exit $ endsubroutine  $start:u $! $ create 'f' X$!-7 X$!`20`20`20`20`20`20Sorts`20a`20directory`20by`20date.-& X$!`20`20`20`20`20`20PRW`2010-MAY-2004 X$!2O X$!`20`20`20`20`20`20Modified`20by`20Peter`20Weaver`207-APR-2005`20to`20not`EF0- Vuse`20LIB$DT_FORMATO X$!`09Modified`20by`20Peter`20Weaver`208-APR-2005`20to`20fix`20the`20many`20buge Vs`20introduced . X$!`09`09`09with`20the`207-APR`20modifications X$!tN X$!`09Note`20that`20this`20only`20works`20if`20the`20terminal`20is`20set`20for V`2080`20characters`20and. X$!`09wrap`20is`20one. X$!cO X$!`20Define`20it`20just`20incase`20someone`20has`20something`20different`20`20u. V`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20 X$!e# X$`20ASSIGN`20LIB$DATE_FORMAT_001,-d! X`20`20`20LIB$TIME_FORMAT_001`20-c! X`20`20`20LIB$DT_FORMAT/USER_MODEe X$!s6 X$`20directx`20-`20`20!`20Ignore`20any`20DIR`20symbols X`20`20`20/date=modified`20-`20 ' X`20`20`20/width=(file:80,display:132)- C X`20`20`20/out=sys$scratch:sort_date_'f$getjpi("","PID")'.tmp`20'p1. X$! D X$`20sort`20sys$scratch:sort_date_'f$getjpi("","PID")'.tmp`20tt:`20-& X`20`20`20`20/specification=sys$input: X!O X!`09The`20FOLD`20and`20TIE_BREAK`20are`20very`20important,`20when`20the`20/OMIk VT`20was`20addedO X!`09it`20did`20not`20work`20until`20FOLD`20and`20TIE_BREAK`20were`20added`20an  Vd`20the`20/OMIT X!`09was`20sometimes`20ignored.n X!  X/collating_sequence=(sequence=(L X"AN","EB","AR","PR","AY","UN","UL","UG","EP","CT","OV","EC","`20","0"-"9"), XFOLD,TIE_BREAK) X!O X!`09Setup`20the`20fields,`20split`20the`20filename`20so`20we`20can`20use`20twot V`20lines`20fors X!`09longer`20names) X!+ X/field=(name=filename1,position:1,size:19)e, X/field=(name=filename2,position:20,size:60)+ X/field=(name=filename3,position:1,size:79)#* X/field=(name=dayfield,position:83,size:4), X/field=(name=monthfield,position:87,size:2)+ X/field=(name=yearfield,position:90,size:4) + X/field=(name=timefield,position=94,siz:12)r' X/field=(name=dash1,position:85,size:1)d' X/field=(name=dash2,position:89,size:1) ( X/field=(name=colon1,position:97,size:1)) X/field=(name=colon2,position:100,size:1)gN X/condition=(name=nodate,test=(dash1`20ne`20"-"`20and`20dash2`20ne`20"-"`20and V`20. Xcolon1`20ne`20":"`20and`20colon1`20ne`20":"))/ X/condition=(name=longname,test=(filename2`20netM X"`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`201O V`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20o1 V`20`20`20`20`20`20`20`20`20"))`20!`2060`20spacesn X/key=yearfieldo X/key=monthfield X/key=dayfield X/key=timefield  X/omit=(condition=nodate) < X/data=(if`20longname`20then`20filename3`20else`20filename1) X!+ X!`20then`2022`20spaces`20else`202`20spaces  X!M X/data=(if`20longname`20then`20"`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20 * V`20`20`20`20`20`20`20"`20else`20"`20`20") X/data=dayfield  X/data=monthfieldc
 X/data="-" X/data=yearfield X/data=timefieldN X$`20delete/nolog/noconfirm`20sys$scratch:sort_date_'f$getjpi("","PID")'.tmp.* VeD $ call unpack [.TMP]SORT_DIR_BY_DATE_NORMAL.COM;3 348177386 "" 5 1 2 $! $ create 'f' X$!c( X$!`09Sorts`20a`20directory`20by`20date. X$!`09PRW`2010-MAY-2004t X$!r# X$`20ASSIGN`20LIB$DATE_FORMAT_037,-e! X`20`20`20LIB$TIME_FORMAT_001`20- ! X`20`20`20LIB$DT_FORMAT/USER_MODEp6 X$`20directx`20-`20`20!`20Ignore`20any`20DIR`20symbols X`20`20`20/date=modified- ' X`20`20`20/width=(file:80,display:132)-nC X`20`20`20/out=sys$scratch:sort_date_'f$getjpi("","PID")'.tmp`20'p1EA X$`20sort`20sys$scratch:sort_date_'f$getjpi("","PID")'.tmp`20tt:-o& X`20`20`20`20/specification=sys$input:+ X/field=(name=filename1,position:1,size:19)a, X/field=(name=filename2,position:20,size:60), X/field=(name=datefield,position:83,size:22)O X/condition=(name=shortname,test=(filename2`20eq`20"`20`20`20`20`20`20`20`20`20eO V`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20tO V`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20"))o V`20!`2060`20spaces-N X/condition=(name=longname,test=(filename2`20ne`20"`20`20`20`20`20`20`20`20`20O V`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20-O V`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20"))p V`20!`2060`20spacesk X/include=(condition=shortname,  Xkey=datefield,5 Xdata=filename1,  Xdata="`20`20",`20!`202`20spaces Xdata=datefield) X/include=(condition=longname, Xkey=datefield,a Xdata=filename1, Xdata=filename2,O Xdata="`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20`20",`20!o V`2022`20spacesh Xdata=datefield)M X$`20delete/nolog/noconfirm`20sys$scratch:sort_date_'f$getjpi("","PID")'.tmp.hL $ call unpack [.TMP]SORT_DIR_BY_DATE_WITH_DT_FORMAT.COM;1 123536074 "" 3 2 2 $ v=f$verify(v)f $ exit   -- e Peter Weaver Weaver Consulting Services Inc.  Canadian VAR for CHARON-VAXD www.weaverconsulting.cao   ------------------------------    Date: 11 Apr 2005 14:16:37 -0700' From: "DL Phillips" <whohe@whoever.com>t# Subject: Re: Sort Directory by Date C Message-ID: <1113254197.403584.232130@z14g2000cwz.googlegroups.com>n   Hein wrote:CE > Anyway.... all this to report that Guy Peleg picked up on this, andg isE > considering/investigating to put some sort functions (dates, sizes)d directlyC > into Directory. No promisses/commitments, but Guy has been coming  throughbB > very nively indeed in the past. Your cards, letters (and perhpas beers at4 > the bootcamp) for Guy are surely appreciated. :-). >d  E I wonder if Guy knows that DCL had this ability decades ago. I'd been G spending some time on an RT-11 project when I sat down at an 11/780 andm/ typed in a command that I'd come to appreciate:1  " DIR/ORDER=DATE/REVERSE *.(DAT,FIL)  G Oh, right. I'm on VMS. Why would I expect DEC'S most expensive system's-E DCL to be at least as capable as their least expensive one? I guess I & was fooled by the name DCL. Stupid me.   Well, better late than never.r    -Doug   ------------------------------    Date: 10 Apr 2005 21:17:12 -0700$ From: "AEF" <spamsink2001@yahoo.com> Subject: Re: Suggestion for FAQsC Message-ID: <1113193032.173818.301090@f14g2000cwb.googlegroups.com>C   Paul Sture wrote:D" > Peter 'EPLAN' LANGSTOEGER wrote: >o@ > > In article <4258221C.EBFCDB87@comcast.net>, David J Dachtera# <djesys.nospam@comcast.net> writes:a > >c > >>AEF wrote: > >>F > >>>[snip] there are just too many useful aspects to logical names to- > >>>sum them up in a short descriptive term.- > >>A > >>For my money, the "short descriptive term" we currently use -  "logical* > >>name" - seems to sum it up quite well.    G In general, that is quite correct. However, in this case we were tryingf? to come up with a description that would help newbies learn theiD differences between symbols and logical names. Calling logical names9 logical names isn't very helpful in this particular case.c    
 > > How abouta > > @ > > Logical - synonym in the kernel, organized in nested tables, protected inE > > 4 access modes, used mostly for (part of) filenames, but also forr variousaF > > (config) parameters (timeouts, licenses, geometry, logical search, ...)    F Nested tables? Doesn't sound quite right to me. Well, in part it does,4 but not for the process,job,group,system part of it.  . What is the config parameter "logical search"?  ? As for filenames, logical names can be used for *any* subset offD file-spec components. You can even use them for version numbers! And= what about the fact that logical names are also automatically D translated when used in the following contexts: logical name tables,B including the process and system directory tables; mail addresses;= queue names; queue manager names; queue form names; and queued characteristic names?c  D What about search lists, including LNM$FILE_DEV and LNM$DIRECTORIES?B Other special purpose logical names like SYS$INPUT and family, andD SYS$DISK? (ok, I forgot some of these features, too). And what aboutE the fact that they are translated iteratively? There's quite a lot too logical names!   >bG > A good summary, but add device names through to a full file spec, andh  7 > instead of logical search, perhaps use "search path"?-    F Search path? He listed "logical search" under configuration paramters./ Are you referring to search list logical names?.  = Oh! And then there are concealed device logical names (rootedlB directories, you know what I mean)! Well, that sort of falls underB file-spec components, but this is certainly not obvious from that!    C > > Symbol - synonym in the DCL CLI, organized in global and local,( used mostlyoF > > for (part of) DCL commands, but also for various (DCL programming) >  > variables.c    F Why "mostly for DCL commands"? I disagree with the "mostly" part. TheyA are basically variables in DCL with a few extra special purposes. F Otherwise they behave pretty much like variables in other languages inG that they can be in expressions with various operators (whereas logical2 names cannot).   > >aE > "various" sounds as though there are a limited number of predefined-8 > ones. Leave that word out and the description is fine.    ) I agree that "various" should be dropped.H  B OK, I guess I'm nitpicking here in the sense that you can't easilyF *briefly* summarize what logical names are and do without missing someF stuff, but all the stuff is so cool that you don't want to miss any ofD it! I suppose one could lump various subsets of all these aspects ofE logical names into fewer things that at least give the flavor of whatc logical names are.   ------------------------------    Date: 10 Apr 2005 21:18:09 -0700$ From: "AEF" <spamsink2001@yahoo.com> Subject: Re: Suggestion for FAQnC Message-ID: <1113193089.815609.279880@l41g2000cwc.googlegroups.com>r  3 This might show up twice. If it does, my apologies.-   Paul Sture wrote: " > Peter 'EPLAN' LANGSTOEGER wrote: >r@ > > In article <4258221C.EBFCDB87@comcast.net>, David J Dachtera# <djesys.nospam@comcast.net> writes:. > >r > >>AEF wrote: > >>F > >>>[snip] there are just too many useful aspects to logical names to- > >>>sum them up in a short descriptive term.h > >>A > >>For my money, the "short descriptive term" we currently use -t "logical* > >>name" - seems to sum it up quite well.    G In general, that is quite correct. However, in this case we were tryingm? to come up with a description that would help newbies learn thesD differences between symbols and logical names. Calling logical names9 logical names isn't very helpful in this particular case.t    
 > > How aboutd > >d@ > > Logical - synonym in the kernel, organized in nested tables, protected inE > > 4 access modes, used mostly for (part of) filenames, but also forf variouslF > > (config) parameters (timeouts, licenses, geometry, logical search, ...)    F Nested tables? Doesn't sound quite right to me. Well, in part it does,< but not for the process,job,group,system,clutser part of it.  . What is the config parameter "logical search"?  ? As for filenames, logical names can be used for *any* subset ofsD file-spec components. You can even use them for version numbers! And= what about the fact that logical names are also automaticallyiD translated when used in the following contexts: logical name tables,B including the process and system directory tables; mail addresses;= queue names; queue manager names; queue form names; and queuei characteristic names?c  D What about search lists, including LNM$FILE_DEV and LNM$DIRECTORIES?B Other special purpose logical names like SYS$INPUT and family, andD SYS$DISK? (ok, I forgot some of these features, too). And what aboutE the fact that they are translated iteratively? There's quite a lot to  logical names!   >eG > A good summary, but add device names through to a full file spec, andi  7 > instead of logical search, perhaps use "search path"?i    F Search path? He listed "logical search" under configuration paramters./ Are you referring to search list logical names?-  = Oh! And then there are concealed device logical names (rootednB directories, you know what I mean)! Well, that sort of falls underB file-spec components, but this is certainly not obvious from that!    C > > Symbol - synonym in the DCL CLI, organized in global and local,6 used mostlyhF > > for (part of) DCL commands, but also for various (DCL programming) >  > variables.e    F Why "mostly for DCL commands"? I disagree with the "mostly" part. TheyA are basically variables in DCL with a few extra special purposes.sF Otherwise they behave pretty much like variables in other languages inG that they can be in expressions with various operators (whereas logicalc names cannot).   > > E > "various" sounds as though there are a limited number of predefinedn8 > ones. Leave that word out and the description is fine.    ) I agree that "various" should be dropped.m  B OK, I guess I'm nitpicking here in the sense that you can't easilyF *briefly* summarize what logical names are and do without missing someF stuff, but all the stuff is so cool that you don't want to miss any ofD it! I suppose one could lump various subsets of all these aspects ofE logical names into fewer things that at least give the flavor of whats logical names are.   ------------------------------  % Date: Mon, 11 Apr 2005 16:07:58 -0400f- From: JF Mezei <jfmezei.spamnot@teksavvy.com>g Subject: Re: Suggestion for FAQsB Message-ID: <1113250081.346b4f0085deb1bac7e11e237d183069@teranews>  
 AEF wrote:I > In general, that is quite correct. However, in this case we were tryingoA > to come up with a description that would help newbies learn ther0 > differences between symbols and logical names.  E Symbols exist at the DCL level and are specific to a process. Not all D processes have access to DCL. The DCL command parser performs symbolF substitution prior to invoking a command. Symbols exist in two scopes:A user and supervisor. At the user level, a symbol defined inside atG command procedure does not survive when the command procedure exits. AttA the supervisor level, the symbol survives through the life of them process. ( = versus == )    H Logical names exist at the operating system level and are organised intoB tables. A process has a table which defines which tables are to beG searched by default when the process attempts logical name translation.tG (for instance, there is a process, job, group, system  tables which are-F searched by default). Tables can be protected and each logical name isF defined in a mode. A user mode logical will cease to exist at the nextF image exit. The job table spans all subrocesses and the master processD for a user. Both job and process tables disaprear when the user logsE out.  By default, logical names are defines at the supervisor level.  F The higher modes such as kernel and executive can be used to protect aB logical name from modification by users who do not have sufficientB privileges. A few system layers such as the file system and deviceE handler will do implicit logical name translation on your behalf. TheuE file system is special in that it will perform recursive logical namelA translation to obtain a full file specification and also allows an6 partial directory specification to appear as a device.   ------------------------------    Date: 11 Apr 2005 12:55:13 -0700% From: "issinoho" <issinoho@gmail.com>o Subject: Tape drive ejectingC Message-ID: <1113249313.922976.297850@o13g2000cwo.googlegroups.com>l  B I mistakenly put a DDS-4 (150M/20Gb) tape in my TLZ07 and after itG whirred and spun for a minute VMS reported an IO error. Problem is thatnF since then anytime I put a standard DDS-2 tape in it immediately spits6 it back out. I've tried powering down but to no avail.  F Could the longer tape somehow have damaged the drive? The device looks fine under VMS as follows,   KYLIE::sh dev /full mkb500:n  B Magtape KYLIE$MKB500:, device type TLZ07, is online, file-oriented device,wG     available to cluster, error logging is enabled, controller supportso?     compaction (compaction  disabled), device supports fastskipc	 (per_io).8  <     Error count                    0    Operations completed       001     Owner process                 ""    Owner UICo [SYSTEM]0     Owner process ID        00000000    Dev Prot S:RWPL,O:RWPL,G:R,W-;     Reference count                0    Default buffer sizer    2048 .     Density                  default    Format	 Normal-11s  C   Volume status:  no-unload on dismount, position lost, odd parity.s             ' Any suggestions on other things to try?f   ------------------------------  + Date: Sun, 10 Apr 2005 07:33:48 +0000 (UTC)oP From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)( Subject: third-party SCSI disks with VMS$ Message-ID: <d3akss$sh3$2@online.de>  I I'm going through old hardware and checking which third-party SCSI disks pH seem to work.  So far, I couple of Fujitsu disks seem to work fine, and E also a Micropolis.  The only one which doesn't seem to work is a NEC mF D3847 (part number 134-506656-301).  Instead of showing up as DKA100, I say, it shows up as DKA101, DKA102,...DKA107, both at the console and on  I VMS.  (I remember seeing this once with a tape drive AT THE CONSOLE, but g" it looked and worked OK from VMS.)  $ Is anyone using a NEC disk with VMS?  F Is it possible that some jumpers other than those for the SCSI-ID can  make it work with VMS?   ------------------------------  # Date: Sun, 10 Apr 2005 12:18:49 GMT " From:   VAXman-  @SendSpamHere.ORG, Subject: Re: third-party SCSI disks with VMS0 Message-ID: <00A4212E.6305453C@SendSpamHere.ORG>  w In article <d3akss$sh3$2@online.de>, helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) writes:oJ >I'm going through old hardware and checking which third-party SCSI disks I >seem to work.  So far, I couple of Fujitsu disks seem to work fine, and mF >also a Micropolis.  The only one which doesn't seem to work is a NEC G >D3847 (part number 134-506656-301).  Instead of showing up as DKA100, tJ >say, it shows up as DKA101, DKA102,...DKA107, both at the console and on J >VMS.  (I remember seeing this once with a tape drive AT THE CONSOLE, but # >it looked and worked OK from VMS.)e  H I had a firmware revision of a Yamaha CD-RW that did the same thing.  ItG would function as loong as you used the 0 sub-lun.  The others were, aso  I could refer to them, phantoms.   -- uK VAXman- A Bored Certified VMS Kernel Mode Hacker   VAXman(at)TMESIS(dot)COMh            k5   "Well my son, life is like a beanstalk, isn't it?"     ------------------------------  % Date: Tue, 12 Apr 2005 07:57:34 +0200t( From: "Rudolf Wingert" <win@fom.fgan.de>, Subject: Re: third-party SCSI disks with VMS3 Message-ID: <000c01c53f24$8589f2b0$994614ac@wat153>)   Hello,  G I did see the same behavior years ago. The problem was not the disk, it-= was the cable. At first, use different cables, to check this.o   Best regards R. Wingert    ------------------------------  % Date: Mon, 11 Apr 2005 22:40:04 -0500a/ From: Chris Scheers <chris@applied-synergy.com>C= Subject: Trivia challenge (Was: Multiprocessor Microvax II ?)a, Message-ID: <3c0u7lF6hhicdU1@individual.net>   Hoff Hoffman wrote:a  I >   OpenVMS VAX Symmetric Multiprocessing (SMP) does not support this, astI >   the hardware configuration is not Symmetric -- the secondaries do notnG >   have any control over Q-bus activities and such, and are limited to I >   interrupting the primary when attention or I/O is required.  (In some H >   ways, this multi-processor MicroVAX configuration is remaniscent of E >   Asymmetric Multiprocessing (ASMP); akin to the VAX-11/782 series.sF >   There was a family of multiprocessor VAXstation systems, but thoseH >   were not widely seen in the field.  I'll leave the identification ofJ >   the two models of the SMP-capable and Q-bus-capable family as a triviaJ >   question.  There was a second and very rare BI-based VAXstation, but IG >   don't know if anyone ever configured and ran it as a dual.  Another- >   trivia question.)o  @ Well, there were the various 3520 and 3540 models. (VAXstation,  MicroVAX, VAXserver)  H VMS also references 3560, 3580, and 35A0 models.  Were these ever built?  . I believe the BI box was the VAXstation 8250L.   -- eG -----------------------------------------------------------------------n$ Chris Scheers, Applied Synergy, Inc.  B Voice: 817-237-3360            Internet: chris@applied-synergy.com    Fax: 817-237-3074   ------------------------------    Date: 11 Apr 2005 14:37:44 -0700 From: flamingomn@hotmail.com' Subject: UAF search for last login dateoC Message-ID: <1113255464.329595.280480@l41g2000cwc.googlegroups.com>e   hi.l  , i'm trying not to 'reinvent the wheel' here.D i'm trying to find a DCL .cOM that will read the sysuaf.lis and pullD out users that haven't logged in in xdays.  the xdays should be a P1
 parameter.  ! i've got an ALPHA with OVMS7.3-2.oG i've copied the SCANUAF from decus and was wondering if that would workl in my enivironment?m   thanks.m anna   ------------------------------  % Date: Mon, 11 Apr 2005 20:35:29 -0600 ( From: "r.m" <nospam@rmendoza.copper.net>+ Subject: Re: UAF search for last login date - Message-ID: <425b346d$1_3@newsfeed.slurp.net>i   flamingomn@hotmail.com wrote:c   > hi.t > . > i'm trying not to 'reinvent the wheel' here.F > i'm trying to find a DCL .cOM that will read the sysuaf.lis and pullF > out users that haven't logged in in xdays.  the xdays should be a P1 > parameter. > # > i've got an ALPHA with OVMS7.3-2. I > i've copied the SCANUAF from decus and was wondering if that would work  > in my enivironment?c  I Is scanuaf written in BASIC?  If so then it is probably the same program cH I have been using since about 6.something maybe 7.something, and I last F used it on a 7.3-1 system a little over a year ago.  Haven't tried it I since we upgraded to 7.3-2 but I don't see why it wouldn't work.  Not at  . work at the moment so can't take a look at it.   Rene.    ------------------------------    Date: 11 Apr 2005 19:29:51 +01006 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER) Subject: Re: VMS 8.2 or 7.3-2n* Message-ID: <425ad02f@NEWS.LANGSTOEGER.AT>  ] In article <M0w6e.21563$7Q4.20432@clgrps13>, "Jerry Alan Braga" <jabraga@flanagan.ca> writes:eN >Just got by 8.2 distribution and was wondering since I would like to upgrade * >from 7.3-1 what is the best at this time. >/D >Upgrade to 7.3-2 with all patches and wait for 8.2 to become stable >Upgrade right to 8.2   D This depends heavily on the layered products you (want/plan to) use.I OpenVMS V8.2 seems quite stable so far, at least similar stable as V7.3-2 > (and at least to me). Newer features would suggest using V8.2.  H But, if you need BASIC, CSWS V2, DECram, DECset, MMOV, Open3D, PATHWORKSL (vs. AdvSrv) or TCPIP nonscalable kernel, or "$" in TCPIP SSH usernames, ...F then you have to still wait (or install OpenVMS Alpha V7.3-2 now) - orL try older LP versions on V8.2 yourself (they might work) and run unsuported.   Notes>G 1) there are no plans for PATHWORKS for OpenVMS V8.2 (only for AdvSrv). C 2) there are no plans for TCPIP nonscalable kernel for OpenVMS V8.2p? 	I hope, there are plans to improve performance (5.4 is faster)rH 3) there might be some 3rd party applications not ready for V8.2 as well; 	(eg. Multinet/TCPware, ORACLE RDB - all currently in beta)a   -- o Peter "EPLAN" LANGSTOEGERW% Network and OpenVMS system specialistt E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------  # Date: Mon, 11 Apr 2005 20:56:26 GMTt& From: John Reagan <john.reagan@hp.com> Subject: Re: VMS 8.2 or 7.3-2.1 Message-ID: <_vB6e.3507$5Y.1875@news.cpqcorp.net>6    Peter 'EPLAN' LANGSTOEGER wrote:  J > But, if you need BASIC, CSWS V2, DECram, DECset, MMOV, Open3D, PATHWORKSN > (vs. AdvSrv) or TCPIP nonscalable kernel, or "$" in TCPIP SSH usernames, ...H > then you have to still wait (or install OpenVMS Alpha V7.3-2 now) - orN > try older LP versions on V8.2 yourself (they might work) and run unsuported. >   D I work with the BASIC folks.  I know of no problems with the latest I BASIC on V8.2.  I also use most of DECset quite extensively on V8.2 with 2 no observable problems.   B Can you share some of the problems you've seen so we can fix them?   -- 4 John Reagan7/ HP Pascal/{A|I}MACRO for OpenVMS Project Leader@ Hewlett-Packard Company    ------------------------------  % Date: Tue, 12 Apr 2005 01:01:20 +0000r7 From: David B Sneddon - bigpond <dbsneddon@bigpond.com>  Subject: Re: VMS 8.2 or 7.3-2r* Message-ID: <425B1DE0.7040304@bigpond.com>  & Jerry Alan Braga mentioned in passing:O > Just got by 8.2 distribution and was wondering since I would like to upgrade  + > from 7.3-1 what is the best at this time.R > E > Upgrade to 7.3-2 with all patches and wait for 8.2 to become stablen > Upgrade right to 8.2  . I am having a problem after upgrading to V8.2.; I suspect my problem is very particular to my configuration ' (which seems to me to be quite normal).o= The problem occurs when I enable shadowing on the system disk = and then try to start DECwindows -- the result is a UNXSIGNAL @ bugcheck... fully reproducible (however, being a hobbyist system I have no way to escalate it)e   Details available at  K http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=842851    Regards, Dave -- gB David B Sneddon (dbs) VMS Systems Programmer dbsneddon@bigpond.comB Sneddo's quick guide ...   http://www.users.bigpond.com/dbsneddon/B DBS freeware   http://www.users.bigpond.com/dbsneddon/software.htm   ------------------------------    Date: 11 Apr 2005 16:51:40 -0700 From: pbking15@hotmail.com3 Subject: Want a FREE IPOD? it works!!!!!!!!!!!!!!!!:C Message-ID: <1113263500.819847.304120@l41g2000cwc.googlegroups.com>e   Hey-  A Check out this great site that is giving away totally FREE iPods!E  + I've joined and I think you should as well.   F It's a completely legitimate offer, and this company has already given away $4 million in FREE stuff!  G All you have to do is join, complete an online offer, and refer friendso to do the same. That's it!  G Here is my referral link. To help me get my iPod, click this exact link1- to join, or copy and paste it into a browser:l$ http://www.freeiPods.com/?r=16874647   ------------------------------  # Date: Tue, 12 Apr 2005 04:17:59 GMT/  From: John Santos <john@egh.com>N Subject: Re: Which release notes say sts$manager:utc$configure_tdf is obsolete, Message-ID: <XZH6e.13930$ox3.11095@trnddc03>   John Laird wrote:e6 > On Sat, 09 Apr 2005 14:12:48 -0500, David J Dachtera$ > <djesys.nospam@comcast.net> wrote: >  > B >>Remember, NTP makes no announcement that a change is imminent... >>- >>Times that follow should be considered GMT: 7 >>07:59:59.99 - NTP prepares to make a clock adjustmentsE >>08:00:00.01 - User's code executes adjusting the clock +/- 01:00:00g) >>08:00:00:03 - NTP makes its adjustmentso >  > L > On Alphas at least, in normal running, some NTPs (and that is not a uniqueM > entity but an implementation by some TCP/IP vendor) adjust the clock slowlydL > by alterning the tick increment.  This is probably done at raised IPL, and> > could easily be (to the outside) world, an atomic operation. > M > Some implementations of NTP may be prepared to "jump" the clock, especiallyeI > by times roughly approximating to 1 hour, but I have certainly met somee4 > which refuse to shift a clock that is too far out. > M > You used the word "morass" elsewhere.  I tend to agree.  My (cough spit) MS K > machines have never failed to work as expected, without any intervention.o  & Everyone can feel a little better  :-)  C One fall my PC fell back an hour every time it hit 2 AM.  The next t? afternoon, it was still between 1AM and 2AM.  I watched it ticktE forward to 2AM and then fall back to 1AM again...  I think I manually C reset the time to make it stop doing this.  The next fall it workedw@ okay, so presumably some windows update patch fixed it.  (No NTPC involved here; this was before I had DSL, so there wasn't permanent  network access, just dialup.)    -- I John Santost Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------    Date: 11 Apr 2005 16:11:51 -0700 From: bob@instantwhip.como0 Subject: Windoze better than linux says analyst!C Message-ID: <1113261111.223374.109870@z14g2000cwz.googlegroups.com>e  / and since windoze is garbage, that doesn't looks/ good for linux/unix ... how about a vms is beste article? :)b  ) http://www.theinquirer.net/?article=22460F   ------------------------------  % Date: Mon, 11 Apr 2005 22:04:50 -0700h+ From: "Barry Treahy, Jr." <Treahy@MMaz.com>p4 Subject: Re: Windoze better than linux says analyst!' Message-ID: <425B56F2.9030001@MMaz.com>n   bob@instantwhip.com wrote:  0 >and since windoze is garbage, that doesn't look0 >good for linux/unix ... how about a vms is best >article? :) > * >http://www.theinquirer.net/?article=22460 >- >  - > D No different than the religious wars of 80's with VMS vs Unix, just  different actors, same story...!   Barryp   -- a  < Barry Treahy, Jr                     E-mail: Treahy@MMaz.com< Midwest Microwave, Inc.                  Phone: 480/314-1320< Vice President & CIO                      FAX:  480/661-7028  I                        ... but it's a DRY HEAT!                          !   ------------------------------  % Date: Mon, 11 Apr 2005 09:48:44 -0400o% From: Shugbear <shugbear@comcast.net> ) Subject: Re: [TCPIP V5.4 ECO4] SFTP rantso, Message-ID: <3bvdfvF6ihu1gU1@individual.net>    VAXman- @SendSpamHere.ORG wrote:g > In article <425572e0$1@NEWS.LANGSTOEGER.AT>, peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER) writes:  >  >><RANT> >>   [snip] >>H >>Please consider paying some bucks to PSC and get a better toolset thanH >>continue porting yourself for yet another couple of years. Or at leastO >>coordinate with them so that we can run TCPWARE$SFTP2.EXE on top of TCPIP ;-), >   < 	Or you could purchase the PSC SSH implementation and run it
 on TCPIP -  % http://www.process.com/tcpip/ssh.htmly   -- iK +-------------------------------------------------------------------------+RD Michael Corbett                           Email: Corbett@process.comB Process Software                          Phone: 800 722-7770 x369B 959 Concord St.                                  508 879-6994 x369= Framingham MA 01701-4682                  FAX:   508 879-0042e   ------------------------------  % Date: Mon, 11 Apr 2005 11:28:58 -0400r% From: Shugbear <shugbear@comcast.net>0) Subject: Re: [TCPIP V5.4 ECO4] SFTP rantsx, Message-ID: <3bvjbuF6jefgiU1@individual.net>    VAXman- @SendSpamHere.ORG wrote:   > J > Sounds like a blatant advert!  ... and sadly, the only solution for now. >   @ 	I thought it would be helpful to point out to those reading theF thread that they can run the SSH/SFTP implementation found in TCPware,H and referenced in the original post, on systems running TCP/IP services.- If I offended you or anyone else I apologize.,  	 sincerely1 Mike   --  K +-------------------------------------------------------------------------+ID Michael Corbett                           Email: Corbett@process.comB Process Software                          Phone: 800 722-7770 x369B 959 Concord St.                                  508 879-6994 x369= Framingham MA 01701-4682                  FAX:   508 879-0042    ------------------------------    Date: 11 Apr 2005 21:05:10 +01006 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER)) Subject: Re: [TCPIP V5.4 ECO4] SFTP rantsE, Message-ID: <425ae686$1@NEWS.LANGSTOEGER.AT>  T In article <3bvdfvF6ihu1gU1@individual.net>, Shugbear <shugbear@comcast.net> writes:! >VAXman- @SendSpamHere.ORG wrote:+h >> In article <425572e0$1@NEWS.LANGSTOEGER.AT>, peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER) writes:	 >>><RANT>; >>>  >[snip]F >>>TI >>>Please consider paying some bucks to PSC and get a better toolset thannI >>>continue porting yourself for yet another couple of years. Or at least,P >>>coordinate with them so that we can run TCPWARE$SFTP2.EXE on top of TCPIP ;-) >tH >	Or you could purchase the PSC SSH implementation and run it on TCPIP - >o& >http://www.process.com/tcpip/ssh.html  K If it would have been my decision, then TCPware probably wouldn't have beenLG ousted here. But it was years ago, and it was to remove finger pointing G ("it must be supported by VMS engineering"). So, if you succeed sellingf? it to them, it would solve my current SSH/SFTP/SCP problems ;-)    -- ' Peter "EPLAN" LANGSTOEGERb% Network and OpenVMS system specialist$ E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------  # Date: Tue, 12 Apr 2005 00:42:00 GMTt" From:   VAXman-  @SendSpamHere.ORG) Subject: Re: [TCPIP V5.4 ECO4] SFTP rantsR0 Message-ID: <00A4225F.5FDA6B37@SendSpamHere.ORG>  T In article <3bvjbuF6jefgiU1@individual.net>, Shugbear <shugbear@comcast.net> writes:! >VAXman- @SendSpamHere.ORG wrote:0 >2 >> 2K >> Sounds like a blatant advert!  ... and sadly, the only solution for now.2 >> 0 >tA >	I thought it would be helpful to point out to those reading the0G >thread that they can run the SSH/SFTP implementation found in TCPware,_I >and referenced in the original post, on systems running TCP/IP services.D. >If I offended you or anyone else I apologize.  F Not at all Mike.  Not offended at all.  I probably should have added a0 ;) or :) after my "Sounds like a blatant advert!   -- 'K VAXman- A Bored Certified VMS Kernel Mode Hacker   VAXman(at)TMESIS(dot)COMt            '5   "Well my son, life is like a beanstalk, isn't it?"     ------------------------------   End of INFO-VAX 2005.203 ************************