# From: hoffman@xdelta.zko.dec.nospam & Sent: Friday, January 07, 2000 9:54 PM To: Info-VAX@Mvb.Saic.Com ; Subject: OpenVMS Frequently Asked Questions (FAQ), Part 4/4        Archive-name: dec-faq/vms/part4  Posting-Frequency: monthly Last-modified: 7 January 2000  Version: VMS-FAQ-4.TXT(3)    Overview ========E This is part 4/4 of the Frequently Asked Questions (FAQ) posting for  < the comp.os.vms and vmsnet.misc newsgroups.  (comp.os.vms isC bidirectionally-gatewayed to the INFO-VAX mailing list - see INTRO3 > for further details.)  It contains answers to frequently askedB questions about Compaq's OpenVMS operating system and the computer> systems on which it runs.  (Please see INTRO5 before posting.)  9   The OpenVMS FAQ is archived in the following locations:   :     http://www.openvms.digital.com/wizard/openvms_faq.html9     ftp://ftp.digital.com/pub/Digital/dec-faq/OpenVMS.txt 1     ftp://ftp.digital.com/pub/Digital/dec-faq/vms :     ftp://rtfm.mit.edu/pub/usenet/news.answers/dec-faq/vms,     comp.answers and news.answers newsgroups  A   Other internet FAQs are generally available in these locations:   ,     comp.answers and news.answers newsgroups%     ftp://rtfm.mit.edu/pub/usenet/...   ?   User-created HTML versions of the OpenVMS FAQ are located at:        http://www.kjsl.com/vmsfaq'     http://eisner.decus.org/vms/faq.htm   H Please do NOT send technical questions to the Frequently Asked QuestionsH (FAQ) editor -- well, please do not email any questions that do not alsoF include the answer(s).  Please post these questions to the appropriateH newsgroup instead -- and see INTRO5 before posting.  To make suggestionsF for changes or additions to this FAQ list, please send mail to the FAQH editor at hoffman@xdelta.zko.dec.com.  Again, the FAQ editor is *not* in' a position to answer general questions.    Some general notes:   K The term "VMS" is synonymous with "OpenVMS".  "Alpha", "AlphaGeneration" or F "AXP" generally refers to any system or product based on or related toJ Compaq's Alpha processor architecture.  OpenVMS manual names mentioned areC those as of V7.2 -- names may be different in other editions of the  documentation set.  H World-Wide Web Universal Resource Locator (URL) notation is used for FTP
 addresses.  F Many people have contributed to this list, directly or indirectly.  InG some cases, an answer has been adapted from one or more postings on the D comp.os.vms newsgroup.  Our thanks to all of those who post answers.H The name (or names) at the end of an entry indicate that the informationD was taken from postings by those individuals; the text may have beenG edited for this FAQ.  These citations are only given to acknowledge the 
 contribution.   A Although the editor of this FAQ is an employee of Compaq Computer A Corporation, this posting is not an official statement of Compaq.   L AlphaGeneration, AlphaServer, AlphaStation, Alpha AXP, AXP, DEC, DECstation,I DECsystem, OpenVMS, ULTRIX, VAX and VMS are trademarks of Compaq.  Compaq L and the names of Compaq products are trademarks and/or registered trademarksK and/or service marks of Compaq Computer Corporation.  OSF/1 is a registered J trademark of the Open Software Foundation.  UNIX is a registered trademarkF in the United States and other countries, licensed exclusively throughK X/Open Company Ltd.  Other names are properties of their respective owners.    Table of Contents - Part 4/4 ____________________________    
 DECwindows( ========================================  F DECW1.  How do I let someone else display something on my workstation?9 DECW2.  How do I create a display on another workstation? F DECW3.  How can I get the information from SHOW DISPLAY into a symbol?0 DECW4.  How do I get a log of a DECterm session?E DECW5.  Problem - the DELETE key deletes forward instead of backward! 7 DECW6.  Problem - On a DEC2000-300, Motif doesn't start < DECW7.  Problem - My LK401 keyboard unexpectedly autorepeatsI DECW8.  Problem - My LK411 sends the wrong keycodes or some keys are dead 3 DECW9.  How do I set the title on a DECterm window? B DECW10. How do I customize DECwindows, including the login screen?4 DECW11. Why doesn't XtAppAddInput() work on OpenVMS?B DECW12. Why do the keyboard arrow keys move the DECwindows cursor?  
 Miscellaneous ( ========================================- MISC1.  Looking for connector wiring pinouts? E MISC2.  Where can I find information on escape and control sequences? ? MISC3.  Can I reuse old keyboards, mice and monitors with a PC? : MISC4.  What connectors and wiring adapters are available?F MISC5.  Where can I find performance info and specs for older systems?C MISC6.  What does "failure on back translate address request" mean? 6 MISC7.  How to determine the network hardware address?G MISC8.  Why does my system halt when I powercycle the console terminal? @ MISC9.  Why can't I use PPP and RAS to connect to OpenVMS Alpha?A MISC10. Which video monitor works with which graphics controller? 8 MISC11. Where can I get information on storage hardware?3 MISC12. Does DCPS work with the LRA0 parallel port? 9 MISC13. How do I check for free space on a (BACKUP) tape? ( MISC14. So what happened to sys$cmsuper?: MISC15. How can I send radio pages from my OpenVMS system?2 MISC16. What is flow control and how does it work?: MISC17. How do I reset the LAN (DECnet-Plus NCL) counters?4 MISC18. What are the prefixes for the powers of ten?   Software( ========================================A SOFT1.  Where can I find freeware/shareware/software for OpenVMS? > SOFT2.  Where can I find the UNIX <whatever> tool for OpenVMS?G SOFT3.  Where can I get the Netscape Navigator Mozilla.org Web Browser? ) SOFT4.  Where can I get Java for OpenVMS? H SOFT5.  VAX C and DEC C, and other OpenVMS C Programming Considerations?/ SOFT6.  Obtaining user input in DCL CGI script? / SOFT7.  How do I get my own batch entry number? . SOFT8.  How do I convert to new CMS libraries?@ SOFT9.  Where can I get new certificates for Netscape Navigator?1 SOFT10. Why doesn't DCL symbol substitution work?     < ------------------------------------------------------------F DECW1.  How do I let someone else display something on my workstation?  M On a workstation, you go into "Customize" menu of the session manager utility @ and select "Security".  When the pop-up box appears, you can putK node/user/tranport to allow who can launch an application to the display on  that workstation. " 					[raspuzzi@mrlat.enet.dec.com]  M > Yah, but this doesn't seem to work with non-VMS systems.  What do I put in  I > for the transport?  I tried "TCPIP" just for kicks, but it didn't work.   &         You need a checklist of sorts:  D       1) Make sure  that  you've  specified  the X-windows "display"D          correctly  on  the remote side.  For DECNET it's  somethingD          like NODE::0.0, for TCP/IP it's Node.Domain:0.0, etc.  On aA          unix system, define the DISPLAY environment variable so:   & 	    # setenv DISPLAY myvax.domain:0.0  D       2) If you've verified 1) and things still aren't working, makeD          sure the Security settings on  the  VMS side will allow theD          connection:  Pull  down the "Options" menu in  the  SessionD          Manager, select "Security..."  near  the  bottom.   If  youD          don't  find  your  host  (and  username) listed on the leftD          under "Authorized Users", go to the  right side of the menuD          and   fill   in  the  three  fields,  "Node",   "Username",D          "Transport".  Then click on the Add botton, then the  ApplyD          and  OK  buttons  to  add  the  new  host  to  the security          database.  @           a) There are  various  transports: LOCAL, DECNET, LAT,@              TCPIP,  etc.   Select  the one appropriate  to  the<              client machine's connection to the VMS machine.  9 	  b) If the connection is DECNET, do *NOT* add :: to the               node name!   @           c) If the connection is TCPIP, "Username" _must_ be an@              asterisk (*) because the  TCP/IP protocol used does-              not provide the remote username.   @           d) If the connection is TCPIP, it's best to use a full@              domain name, e.g.,  Node.Subd.Domain.  However, you@              _may_  have  to use the IP address  itself,  rather@              than  the  domain  name  (EWS  requires  this).   I@              generally  add two entries for each TPCIP host, the@              first using the  domain  name,  the  second  the IP              address.   @           e) There are a  various  3rd  party vendors who supply@              TCP/IP  packages for VMS, including but not limited@              to  TGV  (Multinet)  and  Wollongong  (Pathway  ?).@              Multinet  (and  DEC's  own  UCX) call the transport@              "TCPIP", Wollongong, at least in some incarnations,<              uses "WINTCP".  You need to use the appropriate@              vendor's package transport name  in the "Transport"              field.   D       3) If things _still_  aren't  working, make sure the transportD          you  want  has  been activated for DECwindows.  This  is  aD          system manager job, but you can do the ground work yourself8          before bothering the sysmgr.  Do the following:  4 	    $ DIR SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM  &          If that file exists, then do:  9 	    $ SEARCH SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM - (             $_    DECW$SERVER_TRANSPORTS  '          You sould find something like:   9 	    $ decw$server_transports == "DECNET,LOCAL,LAT,TCPIP"   D          If the transport you want,  e.g., TCPIP, isn't listed, haveD          your  system  manager  make  the  appropriate  changes  andD          restart DECwindows.  If the file doesn't exist, the  sysmgrD          will  have  to  create  it  by  copying  the  correspondingD          .TEMPLATE file  to  .COM  and  uncommenting  the  line that(          defines decw$server_transports.  @           a) If you're wanting  to  use  TCP/IP to connect, make@              sure  TCP/IP is available on the VMS host.   TCP/IP@              is _not_ native to VMS.  You  need  to  be  runningB              either Compaq's TCP/IP or a 3rd party vendor's TCP/IP@              product.   If  you're  not,  none of the above will              help.% 				    [Fairfield@Slac.Stanford.Edu]   K There is a log file created in SYS$MANAGER which tells you which transports L are loaded, and also tell you what connect attempts were rejected, including: showing what the presented credentials were.  This file isN SYS$MANAGER:DECW$SERVER_0_ERROR.LOG, although the 0 could be another number ifK you have multiple servers on the workstation.  I have found this file to be I very useful for tracking down what needs to be put in the Session Manager  Security entries.  				    [rabinowitz@bear.com]   < ------------------------------------------------------------9 DECW2.  How do I create a display on another workstation?   @ $ SET DISPLAY /CREATE /TRANSPORT=net_transport /NODE=remote_node  ) for LAT the command might look like this:   6 $ SET DISPLAY /CREATE /TRANSPORT=LAT /NODE=REMOTE_NODE   for DECnet:   2 $ SET DISPLAY /CREATE /TRANSPORT=DECNET /NODE=NODE  
 for TCP/IP  9 $ SET DISPLAY /CREATE /TRANSPORT=TCPIP /NODE=128.12.4.122   D Note that LAT is typically used for X terminals but can be used fromI OpenVMS to OpenVMS systems on OpenVMS Alpha V6.1 (if you have setup the X K server to allow the LAT transport - check the docs).  LAT will be supported D on OpenVMS VAX as a transport for DECwindows in a future OpenVMS VAX release." 					[raspuzzi@mrlat.enet.dec.com]  K There is a log file created in SYS$MANAGER which tells you which transports L are loaded, and also tell you what connect attempts were rejected, including: showing what the presented credentials were.  This file isN SYS$MANAGER:DECW$SERVER_0_ERROR.LOG, although the 0 could be another number ifK you have multiple servers on the workstation.  I have found this file to be I very useful for tracking down what needs to be put in the Session Manager  Security entries. =                                         [rabinowitz@bear.com]   < ------------------------------------------------------------F DECW3.  How can I get the information from SHOW DISPLAY into a symbol?  H Use the undocumented SHOW DISPLAY/SYMBOL, and then reference the symbolsC DECW$DISPLAY_NODE,  DECW$DISPLAY_SCREEN, DECW$DISPLAY_SERVER and/or  DECW$DISPLAY_TRANSPORT. " 					[Fairfield@Slac.Stanford.Edu]  E An example of calling the underlying (and also undocumented) sys$qio  ? programming interface for the WSDRIVER (WSAn:) is available at:   J   http://www.openvms.digital.com/freeware/srh_examples/DECUS_UNDOC_CLINIC/  < ------------------------------------------------------------0 DECW4.  How do I get a log of a DECterm session?  L If you are working from a Decterm, you can use the AutoPrint feature. ChooseD the "Printer..." menu item from the "Options" menu, set the printingH destination to the name of the file you want, and set "Auto Print Mode". You are now free to continue.   M It should be noted that ALL the characters and escape sequences are captured, O but if you display the log file on a DECterm you will get EXACTLY what you had.   					[fenster@star.enet.dec.com]  < ------------------------------------------------------------E DECW5.  Problem - the DELETE key deletes forward instead of backward!   N This has to do with Motif's virtual bindings.  When a Motif application startsD up, it looks at the vendor string returned in the display connectionL information and attempts to match the string to a table of virtual bindings.  N You can override the default bindings in your decw$xdefaults.dat file. Here is9 the entry you would make to get the default VMS bindings.       *defaultVirtualBindings:\   osfCancel	:		<Key>F11	\n\  osfLeft	:		<Key>Left	\n\   osfUp		:		<Key>Up		\n\   osfRight	:		<Key>Right	\n\   osfDown	:		<Key>Down	\n\    osfEndLine	:Alt		<Key>Right	\n\!  osfBeginLine	:Alt		<Key>Left	\n\   osfPageUp	:		<Key>Prior	\n\  osfPageDown	:		<Key>Next	\n\ "  osfDelete	:Shift		<Key>Delete	\n\  osfUndo	:Alt		<Key>Delete	\n\   osfBackSpace	:		<Key>Delete	\n\   osfAddMode	:Shift		<Key>F8		\n\  osfHelp	:		<Key>Help	\n\   osfMenu	:		<Key>F4		\n\  osfMenuBar	:		<Key>F10	\n\   osfSelect	:		<Key>Select	\n\ !  osfActivate	:		<Key>KP_Enter	\n\ !  osfCopy	:Shift		<Key>DRemove	\n\   osfCut		:		<Key>DRemove	\n\  osfPaste	:		<Key>Insert  	 To merge:     	$ xrdb :== $decw$utils:xrdb.exe( 	$ xrdb -nocpp -merge decw$xdefaults.dat# 					[kleinsorge@star.enet.dec.com]   < ------------------------------------------------------------7 DECW6.  Problem - On a DEC2000-300, Motif doesn't start   N Check for a GQ device by doing a SHOW DEVICE G at the DCL prompt.  If there is no GQA0 device:   L a) VMS failed to find the appropriate IRQ information for the Compaq QVisionK    and did not autoconfigure it.  Run the correct ECU (for OSF and VMS) and 
    reboot.  M b) You do not have a Compaq QVision video card.  This card should have Compaq M    printed on it, and identifies itself as a CPQ3011 or a CPQ3111.  If it is  N    not one of these 2 devices (as of 7/1/94 and version 6.1) then VMS does not    support it.   If there is a GQA0 device:  I a) There may have been a severe error in the DECwindows startup. Type the I    contents of SYS$MANAGER:DECW$SERVER_0_ERROR.LOG for any information on     errors starting the server.  L b) The sysgen parameter WINDOW_SYSTEM is not set to 1.  This is a common way5    used by system managers to disable server startup.   M c) You may not have a valid Motif license.    To check for the Motif license, I    type LICENSE LIST DW-MOTIF/FULL and examine the information displayed. 2    Make sure that it is present, valid and active.# 					[kleinsorge@star.enet.dec.com]   < ------------------------------------------------------------< DECW7.  Problem - My LK401 keyboard unexpectedly autorepeats  # There are several modes of failure:   K a) Pressing 2 and 3 keys at the same time causes one key to autorepeat when L    released.  Check the hardware revision level printed on the bottom of theM    keyboard.  If the revision level is C01, the keyboard firmware is broken.  L    Call field service to replace the keyboard with any revision level other     than C01.  J b) Pressing certain keys is always broken.  Typical sympypoms are: delete N    always causes a autorepeat, return needs to be pressed twice, etc.  This isI    frequently caused by having keys depressed while the keyboard is being L    initialized.  Pressing ^F2 several times or unplugging and replugging theL    keyboard frequently fix this problem.  There is a patch available to fix K    this problem [contact the CSC for information - a CSCPAT number will be  '    included here when available. - Ed.]   L c) A key that was working spontaneously stops working correctly. This may beN    either (a) or (b) or it may be bad firmware.  Ensure that you have the mostJ    recent firmware installed on your CPU.  An old version of the DEC 3000 4    firmware had a bug that could cause this symptom.# 					[kleinsorge@star.enet.dec.com]   < ------------------------------------------------------------I DECW8.  Problem - My LK411 sends the wrong keycodes or some keys are dead   N Check the firmware revision on the keyboard.  Hardware revision B01 introducedM an incompatability with the device driver which causes the keyboard to not be F recognized correctly.  There is a patch available to fix this problem:I [AXPDRIV06_061] - the fix is also included in OpenVMS V6.2.  The rev A01  5 keyboard, and the LK450 should work without problems. # 					[kleinsorge@star.enet.dec.com] " 					[inazu_k@ewbv21.enet.dec.com]  < ------------------------------------------------------------3 DECW9.  How do I set the title on a DECterm window?   0 If you are creating a new DECterm window, check ) HELP CREATE /TERMINAL /WINDOW_ATTRIBUTES.   H If you want to change the title of an existing window, use the followingM control sequences, where <esc> is the ANSI escape code, value decimal 27, and # <text> is what you want to display:   4 To set the DECterm title, send <esc>]21;<text><esc>\4 To set the icon label, send    <esc>]2L;<text><esc>\  6 For example, DCL to display "My DECterm" in title bar:
 $ ESC[0,8]=27 0 $ WRITE SYS$OUTPUT "''ESC']21;My DECterm''ESC'\" 					[p_lee@decus.ch]   F You can also change the title and the icon using the Options-Window... menu.   < ------------------------------------------------------------B DECW10. How do I customize DECwindows, including the login screen?  L To customize various DECwindows Motif characteristics including the defaultsL used by the SET DISPLAY command, the DECwindows login screen background logoG used (the default is the DIGITAL or Compaq logo), various keymaps, the  M FileView defaults, session manager defaults, the DECwindows login processing, L DECwindows log file processing, and various other DECwindows attributes, see the example file:   .   SYS$STARTUP:DECW$PRIVATE_APPS_SETUP.TEMPLATE  C This example template file is typically copied over to the filename M SYS$COMMON:[SYS$STARTUP]DECW$PRIVATE_APPS_SETUP.COM and then modified to meet  site-specific requirements.   M Additionally, various X tools such as xsetroot, bitmap and xrdb -- some these G can be useful in customizing the appearance of an application or of the A DECwindows Motif display -- are provided in the DECW$UTILS: area.   M When using DECwindows V1.2-4 and later on OpenVMS Alpha, the default desktop  G is the Common Desktop Environment (CDE).  You can select your prefered  I desktop (CDE or DECwindows Motif) when logging in, or you can change the  = default to the DECwindows Motif desktop using the DCL symbol  K decw$start_new_desktop in the DECwindows private application setup command  I procedure.  See SYS$STARTUP:DECW$PRIVATE_APPS_SETUP.TEMPLATE for further  7 details, and how to create DECW$PRIVATE_APPS_SETUP.COM.   G Note that with DECwindows CDE, the root window is no longer visible by  H default.  The root window is hidden behind the "backdrop" window of the E current CDE workspace.  To make the root window visible, use the CDE  E style manager selection "backdrop none", and use information such as  / that in the OpenVMS FAQ to set the root window.   E To add a new backdrop to the DECwindows CDE environment, the backdrop J must first be in or be converted into X11 pixmap format.  (This conversionF is often possible using tools such as xv.)  Then (if necessary) createH the default backdrop directory SYS$COMMON:[CDE$DEFAULTS.USER.BACKDROPS].I Place the X11 pixmap file containing the desired image into the backdrops C directory, ensure that it has a filename extension of .PM.  (The xv E default filename extension for the X11 pixmap file is .XPM, while CDE F expects only to see files with .PM.)  Now invoke the CDE style managerF and select a new backdrop.  You will find your image will be placed at+ the end of the list of backdrops available.     					[Stephen Hoffman]  < ------------------------------------------------------------4 DECW11. Why doesn't XtAppAddInput() work on OpenVMS?  J XtAppAddInput() does work on OpenVMS.  The MIT definition of the X Windows: call XtAppAddInput() includes platform-specific arguments.  J On platforms where C is the typically the primary programming language forE the platform, the file descriptor mask is one of the arguments to the  XtAppAddInput() call.   I On OpenVMS, the platform-specific arguments to this call include an event I flag and an IOSB, as these are the traditional OpenVMS constructs used to I synchronize the completion of asynchronous operations.  While it would be D easier to port non-OpenVMS C code that calls XtAppAddInput() over toH OpenVMS if the arguments included the C file descriptor, this would makeK the call unusable from other OpenVMS languages, and would make it extremely A difficult to use OpenVMS features such as ASTs and sys$qio calls.   K One restriction on the event flag: the event flag chosen must be from event I flag cluster zero.  When using the traditional lib$get_ef and lib$free_ef G calls to allocate and deallocate event flags, you must first explicitly H call lib$free_ef to free up some event flags in event flag cluster zero.K Please see the event flag documentation for specific details on these calls J and for specific event flags that can be freed in event flag cluster zero.  F Here is some example code that covers calling this routine on OpenVMS:       m->InputID = XtAppAddInput(          m->AppCtx,         m->InputEF,          m->InputIosb,          the_callback, 1 );     if ( !((int) m->InputID ))	         {          XtAppErrorMsg(             m->AppCtx,             "invalidDevice",             "XtAppAddInput",             "XtToolkitError", "             "Can't Access Device",             (String *) NULL,              (Cardinal *) NULL );         ...  					[Stephen Hoffman]  < ------------------------------------------------------------B DECW12. Why do the keyboard arrow keys move the DECwindows cursor?  @ Congratulations, you have just stumbled into "dead rodent" mode.< This DECwindows environment -- where the keyboard arrow keys@ move the mouse cursor and where the [SELECT], [PREV], and [NEXT]B keys emulate the three mouse buttons -- allows rudimentary system 2 operations when the mouse is among the casualties.  A To enter or exit the "dead rodent" mode. press: [CTRL][SHIFT][F3]   < ------------------------------------------------------------- MISC1.  Looking for connector wiring pinouts?    DECconnect DEC-423 MMJ pinout:     1: Data Terminal Ready (DTR)   2: Transmit (TXD)    3: Transmit Ground (TXD-)    4: Receive Ground (RXD-)   5: Receive (RXD)   6: Data Set Ready (DSR)       +------------------+     | 1  2  3  4  5  6 |     +------------+    ++                  +____+    / The PC-compatible DB9 connector pinout follows:      1: Data Carrier Detect (DCD)   2: Received Data   3: Transmit Data   4: Data Terminal Ready (DTR)   5: Ground    6: Data Set Ready (DSR)    7: Request To Send (RTS)   8: Clear To Send
   9: floating   C The MicroVAX DB9 console connector pinout predates the PC-style DB9 D pinout, and uses a then-common (older) standard pinout, and uses the# following EIA-232-standard signals:      1: Protective Ground   2: Transmited Data   3: Received Data   4: Request To Send (RTS)   5: Data Terminal Ready (DTR)   6: Data Set Ready (DSR)    7: Signal Ground8   8: Shorted to pin 9 on MicroVAX and VAXstation 2000...3   9:    ...series systems, otherwise left floating.     > The BC16E-nn (where -nn indicates the cable length) cable key = impliicitly "flips over" (crosses-over) the signal wires, so  1 all DECconnect MMJ connectors are wired the same.   
            // :            ----                                       ----:            |  |---------------------------------------|  |:            ----                                       ----:                                                         \\  0 The BC16-E-nn cross-over wiring looks like this:  ;             Terminal                                   Host :             MMJ                                        MMJ  =          DTR 1 --->-------------->----------------->--- 6 DSR =          TXD 2 --->-------------->----------------->--- 5 RXD 9              3 ---------------------------------------- 4 9              4 ---------------------------------------- 3 =          RXD 5 ---<--------------<-----------------<--- 2 TXD =          DSR 6 ---<--------------<-----------------<--- 1 DTR   	 Also see:   N  http://www.partner.digital.com:9003/public/cheat_sheets/cables/padapters.html9  http://www.networks.digital.com.au/dr/npgc/opdec-mn.html (  For adapters and connectors, see MISC4.   					[Stephen Hoffman]7                                         [Mike Thompson]   < ------------------------------------------------------------E MISC2.  Where can I find information on escape and control sequences?   G Information on escape and control sequences can be found in the OpenVMS C I/O User's Reference Manual, in the section on the terminal driver. B This section includes details on the general format and content of these sequences.  C Specific details on the escape and control sequences supported by a A particular serial device are typically found in the documentation A provided with the specific device.  Information on the sequences  F supported by DECwindows DECterm terminal emulator are included in the  DECwindows documentation.   G Examples of common escape and control sequences -- those typically used H by the OpenVMS screen management package -- can be found in the OpenVMS $ system file SYS$SYSTEM:SMGTERMS.TXT.  H The following refers to the function keys on the VTxxx series terminals,I and compatibles.  In the following, <CSI> is decimal code 155 and can be  H replaced by the sequence "<ESC>[" (without the quotes) particularly for E seven-bit operations, SS3 is decimal code 143 and can be replaced by  C "<ESC>O" particularly for seven-bit operations.  Older VT1xx series F terminals and any other terminals operating with seven-bit characters ? should not be sent eight-bit operators such as <CSI> and <SS3>.   + PF1=<SS3>P PF2=<SS3>Q PF3=<SS3>R PF4=<SS3>S A KP0=<SS3>p KP1=<SS3>q KP2=<SS3>r KP3=<SS3>s KP4=<SS3>t KP5=<SS3>u I KP6=<SS3>v KP7=<SS3>w KP8=<SS3>x KP9=<SS3>y KPCOMMA=<SS3>l KPMINUS=<SS3>m I KPPERIOD=<SS3>n ENTER=<SS3>M DNARROW=<CSI>B UPARROW=<CSI>A LFARROW=<CSI>D H RTARROW=<CSI>C FIND=<CSI>1~ INSERT=<CSI>2~ REMOVE=<CSI>3~ SELECT=<CSI>4~I PREV=<CSI>5~ NEXT=<CSI>6~ F6=<CSI>17~ F7=<CSI>18~ F8=<CSI>19~ F9=<CSI>20~ @ F10=<CSI>21~ F11=<CSI>23~ F12=<CSI>24~ F13=<CSI>25~ F14=<CSI>26~M HELP=<CSI>28~ DO=<CSI>29~ F17=<CSI>31~ F18=<CSI>32~ F19=<CSI>33~ F20=<CSI>34~   < ------------------------------------------------------------? MISC3.  Can I reuse old keyboards, mice and monitors with a PC?   G Older Compaq keyboards (those with the DIGITAL logo and the RJ modular  G jacks), older Compaq mice (those with the DIGITAL logo and with the RJ  J modular jacks, or with a DIN connector with pins in a configuration other E than the PC-standard DIN connector pin orientation), and older video  E monitors (with RGB synch-on-green video signaling) all use signaling  J formats and/or communications protocols that differ from the PC standards,I and are not (easily) interchangable nor (easily) compatible with typical  L PC peripheral device controllers.  LK201, LK401, VSXXX, VR260, VR290, etc., & are incompatible with most PC systems.  F Newer Compaq keyboards (those with with PC-style DIN plugs, and CompaqF or DIGITAL logo), newer Compaq mice (with PC-pin DIN plugs, and CompaqC or DIGITAL logo), and newer video monitors (multi-synch) are often  F interchangeable with "industry standard" PC systems, and can often be I used with most PC peripheral device controllers. LK461, LK471, PC7XS-CA,  8 VRC16, VRC21, etc., are compatible with most PC systems.  K Rule of thumb: if the peripheral device component was sold for use with the K DEC 2000 (DECpc 150 AXP), an AlphaServer series, an AlphaStation series, or F more recent Alpha system, it will probably  work with a PC peripheral I controller.  If the peripheral device component was sold for use with an  K VT420 or older terminal, most VAX, most VAXstation, and most Alpha systems  K with names in the format `DEC <four-digit-number>', it probably won't work   on a PC.  N Note that the above is a general guideline, and should not be read to indicateM that any particular peripheral device will or will not work in any particular N configuration, save for those specific configurations the device is explicitly
 supported in.  					[Stephen Hoffman]  K Software Integrators sells a video adapter card called Gemini P1 which will J drive many of the older Compaq (DIGITAL-logo) fixed-frequency monitors on  a PC system:     http://www.si87.com/   Also see MISC10.  < ------------------------------------------------------------: MISC4.  What connectors and wiring adapters are available?    J The H8571-B converts the (non-2000-series) MicroVAX DB9 to MMJ DECconnect.H The MicroVAX 2000 and VAXstation 2000 requires a BCC08 cable (which has 7 the 8-9 short) and the H8571-D for use with DECconnect.   H More recent Compaq (Compaq or DIGITAL logo) systems will use either the J DECconnect MMJ wiring or (on all recent system designs) the PC-compatible  DB9 pinout.    DECconnect MMJ adapters:  3     Part:      Converts BC16E MMJ male to fit into:      ,     H8575-A    EIA232 25 pin female (common)6     H8575-B    EIA232 9 pin male (MicroVAX II console)/     H8571-D    EIA232 25 pin male (modem-wired) 0     H8571-J    PC/AT 9 pin male (PC serial port)-     H8572-0    0BC16E MMJ male (MMJ extender)   6     BC16E-**   MMJ cable, available in various lengths  D Numerous additional adapters and cables are available from the _OPENK DECconnect Building Wiring Components and Applications Catalog_, as well as ' descriptions of the above-listed parts.   J The H8571-A and H8575-A are MMJ to DB25 (female) and are wired as follows:  	 Also see: N  http://www.partner.digital.com:9003/public/cheat_sheets/cables/padapters.html9  http://www.networks.digital.com.au/dr/npgc/opdec-mn.html   L Jameco offers a USB-A to PS/2 Mini DIN 6 Adapter (as part 168751), for thoseC folks wishing to (try to) use PS/2 Keyboards via USB-A connections.   " For wiring and pinouts, see MISC4. 					[Stephen Hoffman]6                                         [Eric Dittman]  < ------------------------------------------------------------F MISC5.  Where can I find performance info and specs for older systems?  
 See ALPHA5  < ------------------------------------------------------------C MISC6.  What does "failure on back translate address request" mean?   C The destination node is running DECnet-Plus, and its naming service @ cannot locate a name to assocate with the source node's address.A In other words, the destination node cannot determine the name of  the source node.  G Use the DECNET_REGISTER mechanism (on the destination node) to register D or modify the name(s) and the address(es) of the source node.  Check# the source node namespace, as well.   B Typically, the nodes involved are using a LOCAL namespace, and theA node name and address settings are not coherent across all nodes. C Also check to make sure that the node is entered into its own LOCAL C namespace.  This can be a problem elsewhere, however.  Very rarely, D a cache corruption has been known to cause this error.  To flush the cache, use the command:   1 NCL> flush session control naming cache entry "*"   C Also check to see that you are using the latest ECO for DECnet-Plus   for the version you are running.  - DECnet-Plus can use the following namespaces: 2   o DECdns: DECnet-Plus distributed name services.;   o LocalFile: a local file containing names and addresses. /   o DNS/Bind: the IP distributed name services.    o The UCX local host file.   					[Stephen Hoffman]  < ------------------------------------------------------------5 MISC7. How to determine the network hardware address?   A   Most Alpha and VAX systems have a console command that displays F   the network hardware address.  Many systems will also have a stickerD   identifying the address, either on the enclosure or on the network   controller itself.  C   The system console power-up messages on a number of VAX and Alpha B   systems will display the hardware address, particularly on those>   systems with an integrated Ethernet network adapter present.  E   If you cannot locate a sticker on the system, if the system powerup D   message is unavailable or does not display the address, and if theB   system is at the console prompt, start with the console command:  
   >>> HELP  E   A console command similar to one of the following is typically used "   to display the hardware address:     >>> SHOW DEVICE    >>> SHOW ETHER   >>> SHOW CONFIG   D   On the oldest VAX Q-bus systems, the following console command canD   be used to read the address directly off the (DELQA, DESQA, or the=   not-supported-in-V5.5-and-later DEQNA) Ethernet controller:      >>> E/P/W/N:5 20001920  G   Look at the low byte of the six words displayed by the above command. E   (The oldest VAX Q-bus systems -- such as the KA630 processor module D   used on the MicroVAX II and VAXstation II series -- lack a consoleD   HELP command, and these systems typically have the primary networkF   controller installed such that the hardware address value is located+   at the system physical address 20001920.)   F   If the system is a VAX system, and another VAX system on the networkC   is configured to answer Maintenance and Operations Protocol (MOP) F   bootstrap requests (via DECnet Phase IV, DECnet-Plus, or LANCP), the1   MOM$SYSTEM:READ_ADDR.EXE tool can be requested:      >>> B/R5:100 ddcu    Bootfile: READ_ADDR   I   Where ddcu is the name of the Ethernet controller in the above command. J   The primarly local DELQA, DESQA, and DEQNA Q-bus controllers are usuallyK   named XQA0.  An attempt to MOP download the READ_ADDR program will ensue, I   and (if the download is successful) READ_ADDR will display the hardware 
   address.  G   If the system is running, you can use DECnet or TCP/IP to display the 6   hardware address with one of the following commands.  B     $ MCR NCP SHOW KNOWN LINE CHARACTERISTICS    ! DECnet Phase IV  >     $ MCR NCL SHOW CSMA-CD STATION * ALL STATUS  ! DECnet-Plus  @     $ UCX SHOW INTERFACE/FULL    ! TCP/IP versions prior to V5.0  A     $ TCPIP SHOW INTERFACE/FULL  ! TCP/IP versions V5.0 and later   G   A program can be created to display the hardware address, reading the F   necessary information from the network device drivers.  An example CF   program for reading the Ethernet hardware address (via sys$qio callsE   to the network device driver(s)) is available at the following URL:   >     http://www.openvms.digital.com/wizard/swdev/ethernVMS.html  E   To use the DECnet Phase IV configurator tool to watch for MOP SYSID %   activity on the local area network:   B   $ NCP SET MODULE CONFIGURATOR KNOWN CIRCUIT SURVEILLANCE ENABLED  E   Let the DECnet configurator run for at least 20 minutes. Then issue    the following commands:   E   $ NCP SHOW MODULE CONFIGURATOR KNOWN CIRCUIT STATUS TO filename.txt C   $ NCP SET MODULE CONFIGURATOR KNOWN CIRCUIT SURVEILLANCE DISABLED   E   The resulting file (named filename.txt) can now be searched for the G   information of interest.  Most DECnet systems will generate MOP SYSID H   messages identifying items such as the controller hardware address andE   the controller type, and these messages are generated and multicast    roughly every ten minutes.  E   Information on the DECnet MOP SYSID messages and other parts of the F   maintenance protocols is included in the DECnet network architecture,   specifications referenced in section DOC9.  < ------------------------------------------------------------G MISC8.  Why does my system halt when I powercycle the console terminal?   <   Various VAX and Alpha consoles are designed to process the.   BREAK signal, treating it as a HALT request.  @   A BREAK is a deliberately-generated serial line framing error.  F   When a serial line device such as a terminal powers up (or sometimesD   when powering down) it can generate framing errors.  These framing2   errors are indistingushable from a BREAK signal.  ?   When a BREAK is received on a serial line console for various B   VAX systems -- including most VAXstation, MicroVAX, and VAX 4000A   series -- it is typically interpreted as a HALT.  Alpha systems C   will also often process a BREAK in a similar fashion, halting the 	   system.   @   There is no uniform or generally-available way to disable thisA   behaviour on every VAX or Alpha system.  On some systems, BREAK B   processing can be disabled in favor of [CTRL/P], or [CTRL/P] is %   the only way to halt the processor.   C   The most common way to avoid these halts is to disable the serial A   line console or to simply not power-cycle the console terminal. G   There is certain important system state information that is displayed C   only on the console, OpenVMS expects to always have access to the    system console. @                                                [Stephen Hoffman]  < ------------------------------------------------------------@ MISC9.  Why can't I use PPP and RAS to connect to OpenVMS Alpha?  G   OpenVMS Alpha PPP does not presently support authentication, and the  E   Microsoft Windows NT option to disable authentication during a RAS  G   connection apparently doesn't currently work -- RAS connections will  G   require authentication -- and this will thus prevent RAS connections. @                                                [Stephen Hoffman]  < ------------------------------------------------------------A MISC10. Which video monitor works with which graphics controller?   L   To determine the answer to the "will this monitor work with this graphics F   controller?" question, please first locate the resolution(s) and theJ   frequencies that are possible/supported at both ends of the video cable H   (on the monitor and the graphics controller, in other words), and thenH   determine if there are any matching settings available.  If there are M   multiple matches, you will need to determine which one is most appropriate     for your needs.   N   You will also need to determine if the video monitor or graphics controller M   requires the 3 BNC signaling with the synchronization signals on the green  N   wire, or the 5 BNC signalling common on many PCs, or other connections such G   as the DB15 video connector or USB connector used on various systems.   J   If there are no matches, you will likely need to change the hardware at (   one or both ends of the "video cable".  J   The refresh frequencies for many devices have been posted to comp.os.vmsG   and/or other newsgroups.  Search the archives for details.  Also see:        http://www.repairfaq.org/ <     http://plop.phys.cwru.edu/repairfaq/REPAIR/F_monfaq.html"     http://www.mirage-mmc.com/faq/     Also see MISC3.   < ------------------------------------------------------------8 MISC11. Where can I get information on storage hardware?  < Information on various Compaq OpenVMS and other disk storage; hardware and controllers, and related technical information / on SCSI, device jumpers, etc., is available at:      http://theref.aquascape.com/  < ------------------------------------------------------------> MISC12. Does DECprint (DCPS) work with the LRA0 parallel port?  = The parallel printing port LRA0: found on many OpenVMS Alpha  = systems is capable of some bidirectional communications, with 8 enough for basic operations with most parallel printers.  ? DECprint (DCPS) requires more than just the simple handshaking  > provided by the LRA0: port, therefore DCPS does not work with  the LRA0: port. 4                                      [Paul Anderson]  < ------------------------------------------------------------9 MISC13. How do I check for free space on a (BACKUP) tape?   > You cannot know for certain, though you can certainly estimate the remaining capacity.   ? Tape media is different than disk media, as disks have a known  = and pre-determined fixed capacity.  Modern disks also appear  > logically perfect, based on bad block revectoring support and ; the extra blocks hidden within the disk structure for these  bad block replacements.   @ The capacity of tape media is not nearly as pre-determined, and ; the capacity can vary across different tape media (slightly : different media lengths or different foil markers or other> variations, for instance) and even on the same media over time@ (as bad spots in the media arise).  Tapes can vary the amount of? recording media required, depending on the remaining length of  = the tape, the numbers of correctable and uncorrectable media  C errors that might occur, the numbers and sizes of the inter-record  > gaps and related tape structure overhead, the particular media@ error recovery chosen, the tape density, the efficiently of any > data compression in use, and the storage overhead required by ( BACKUP, tar, and other similar commands.  ? BACKUP using with the default settings results in approximately @ 15% overhead, in terms of saveset size.  (eg: Assuming a 500 KB ' input, the total size would be 575 KB.)      Assuming no compression:0    4 GB media / 575 KB saveset =  7294 savesets      Assuming 1:2 compression: 0    8 GB media / 575 KB saveset = 14588 savesets   C NB: There are no inter-record gaps on DAT tapes.  (When determining B media capacity, you have to consider these with nine-track magtapeE media.  Not with DAT (DDS).  However, the block structure underneath  G the variable length record recording is based on a block size of circa  F 124 KB.  Further, writing doubles filemarks and such can cause a loss C of up to the underlying block size.  Thus even though there are no  A inter-record gaps on DAT, larger savesets are still usually best.   E The compression algorithms used on various devices are generally not  F documented -- further, there is no way to calculate the effective dataF compression ratio, the tape mark overhead, and similar given just the E data to be stored on tape -- short of actually trying it, of course.    C A typical compression ratio found with "everyday" data is somewhere  around 1:1.8 to 1:2.  D NB: OpenVMS often uses the term COMPACTION for compression control, - as in the qualifier /MEDIA_FORMAT=COMPACTION. G                                           [Hoffman, Froehlin, Williams]   < ------------------------------------------------------------4 MISC14. OpenVMS Cluster (SCS) over DECnet?  Over IP?  = The OpenVMS Cluster environment operates over various network 6 protocols, but the core of clustering uses the System : Communications Services (SCS) protocols, and SCS-specific : network datagrams.  Direct (full) connectivity is assumed.  = An OpenVMS Cluster DOES NOT operate over DECnet, nor over IP.   & No SCS protocol routers are available.  B Many folks have suggested operating SCS over DECnet or IP over theC years, but SCS is too far down in the layers, and any such project  B would entail a major or complete rewrite of SCS and of the DECnet B or IP drivers.  Further, the current DECnet and IP implementationsA have large tracts of code that operate at the application level,  D while SCS must operate in the rather more primitive contexts of the D system and particularly the bootstrap -- to get SCS to operate over E a DECnet or IP connection would require relocating major portions of  B the DECnet or IP stack into the kernel.  (And it is not clear thatC the result would even meet the bandwidth and latency expectations.)   @ The usual approach for multi-site OpenVMS Cluster configurationsG involves FDDI, Memory Channel (MC2), or a point-to-point remote bridge, D brouter, or switch.  The connection must be transparent, and it mustC operate at 10 megabits per second or better (Ethernet speed), with  > latency characteristics similar to that of Ethernet or better.< Various sites use FDDI, MC2, ATM, or point-to-point T3 link.    < ------------------------------------------------------------( MISC14. So what happened to sys$cmsuper?  ! There is no SYS$CMSUPR service.     A The typical wisdom for getting into supervisor access mode (from  A user mode) is to execute a routine in executive mode (via a call  > to SYS$CMEXEC and the appropriate privilege) and then issue a > SYS$DCLAST with the ASTADR parameter pointing to your routine > entry point and the ACMODE parameter specified as PSL$C_SUPER.  @ Alternatively, you can reset mode in the call stack return path = and unwind from executive or kernel out into supervisor mode. :                                     [Brian Schenkenberger]  < ------------------------------------------------------------: MISC15. How can I send radio pages from my OpenVMS system?  B There are third-party products available to send messages to radioA paging devices (pagers), communicating via various protocols such ) as TAP (Telocator Alphanumeric Protocol).   C RamPage (Ergonomic Solutions) is one of the available packages that A can generate and transmit messages to radio pagers.  Target Alert = (Target Systems; formerly the DECalert product) is another.   ? Networking Dynamics Corp has a product called Pager Plus.  The  < System Watchdog package can also send pages.  PMDF can route6 specific email addresses to a paging service, as well.  @ Many commercial paging services provide email contact addresses @ for their paging customers -- you can simply send email directly
 to the pager.   ? See SOFT1 for information on the available catalog of products.   < ------------------------------------------------------------2 MISC16. What is flow control and how does it work?  % XON/XOFF is one kind of flow control.   B In ASCII, XON is the [CTRL/Q] character, and XOFF is the [CTRL/S].  G XON/XOFF flow control is typically associated with asynchronous serial  H line communications.  XON/XOFF is an in-band flow control, meaning that + the flow control is mixed in with the data.   J CTS/RTS is another type of flow control, and is sometimes called hardware H flow control.  Out-of-band means that seperate lines/pins from the data 5 lines (pins) are used to carry the CTS/RTS signals.     H Both kinds of flow control are triggered when a threshold is reached in J the incoming buffer.  The flow control is suppose to reach the transmitterH in time to have it stop transmitting before the receiver buffer is full E and data is lost.  Later, after a sufficient amount of the receiver's F buffer is freed up, the resume flow control signal is sent to get the  transmitter going again.  G DECnet Phase IV on OpenVMS VAX supports the use of asynchronous serial  J communications as a network line.  The communication devices (eg. modems, F and drivers) *must not* be configured for XON/XOFF flow control.  The D incidence of these (unexpected) in-band characters will corrupt dataH packets.  Further, the serial line device drivers might normally remove F the XON and XOFF characters from the stream for terminal applications,E but DECnet configures the driver to pass *all* characters through and G requires that all characters be permitted.  (The communication devices  F must pass through not only the XON and XOFF characters, they must passE *all* characters including the 8-bit characters.  If data compression G is happening, it must reproduce the source stream exactly.  No addition > or elimination of null characters, and full data transparency.  I An Ethernet network is rather different than an asynchronous serial line. F Ethernet specifies the control of data flow on a shared segment using B CSMA/CD (Carrier Sense Multiple Access, with Collision Detect)  AnG Ethernet station that is ready to transmit listens for a clear channel  L (Carrier Sense).  When the channel is clear, the station begins to transmit J by asserting a carrier and encoding the packet appropriately.  The stationG concurrently listens to its own signal, to permit the station to detect G if another station began to transmit at the same time -- this is called K collision detection.  (The collision corrupts the signal in a way that can  H reliably be detected.)  Upon detecting the collision, both stations willB stop transmitting, and will back off and try again a little later.H (You can see a log of this activity in the DECnet NCP network counters.)  H DECnet provides its own flow control, above and beyond the flow control J of the physical layer (if any).  The end nodes handshake at the beginning G to establish a transmit window size -- and a transmitter will only send H that much data before stopping and waiting for an acknowledgement.  The H acknowledgement is only sent when the receiver has confirmed the packet D is valid.  (A well-configured DECnet generally avoids triggering any1 underlying (out-of-band) flow control mechanism.) =                                                [David Rabahy]   < ------------------------------------------------------------: MISC17. How do I reset the LAN (DECnet-Plus NCL) counters?   On recent OpenVMS releases:   ;   LANCP> SET DEVICE/DEVICE_SPECIFIC=FUNCTION="CCOU" devname     < ------------------------------------------------------------4 MISC18. What are the prefixes for the powers of ten?  $         Power   Prefix  Abbreviation         10^-18  atto    a          10^-15  femto   f          10^-12  pico    p          10^-09  nano    n          10^-06  micro             10^-03  milli   m          10^-02  centi   c          10^-01  deci    d          10^+01  deca    da         10^+02  hecto   h          10^+03  kilo    k          10^+06  mega    M          10^+09  giga    G          10^+12  tera    T          10^+15  peta    P          10^+18  exa     E     < ------------------------------------------------------------A SOFT1.  Where can I find freeware/shareware/software for OpenVMS?   A Details on many commercial OpenVMS products are available in the   catalog located at:   -   http://www.partner.digital.com/www-catalog/   ? An OpenVMS Freeware CD is distributed with OpenVMS, and is also = available seperately as part of the OpenVMS hobbyist program. / The OpenVMS Freeware CD is available online at:   0         http://www.openvms.digital.com/freeware/         ftp://ftp.montagar.com/ '         ftp://mvb.saic.com/freewarev40/ $         http://freeware.acornsw.com/   and at various other sites.   4 Submissions to the OpenVMS Freeware can be made via:  ?         http://www.openvms.digital.com/openvms/freeware/cd.html   I To order the Freeware, you can order an OpenVMS distribution from Compaq, F or you can order the Freeware itself via the OpenVMS hobbyist website:  )         http://www.montagar.com/hobbyist/   D The Freeware CD-ROM set contains a large assortment of freeware, andH is a good starting point if looking for utilities.  Many of the packagesI listed below are also on the Freeware CD.  Some of the most oft-requested I OpenVMS tools on the Freeware CD include ZIP and UNZIP, GZIP, MMK (make), G PINE, PERL, TAR, UUENCODE and UUDECODE.  Many other tools are available  on the Freeware.  J Compaq also has a separate area containing various OpenVMS software tools  located at:   !   http://ftp.digital.com/pub/VMS/   . Hunter Goatley runs a VMS freeware fileserver:     http://www.madgoat.com/   @ The FILESERV packages are also available via anonymous FTP from:  &   ftp.wku.edu, under [.VMS.FILESERV]. 4   ftp.spc.edu, under [.MACRO32.SAVESETS] and [.MX]. >   ftp.vms.stacken.kth.se, under [.MIRRORS..WKU.VMS.FILESERV]. 8   ftp.shsu.edu, under pub/vms/mx and pub/vms/utilities. (   nic.switch.ch, under /mirror/vms/spc. 6   ftp.technion.ac.il, under /pub/unsupported/vms/spc.    ftp.riken.go.jp   F or via e-mail from FILESERV@WKUVX1.WKU.EDU. Send the commands HELP and>    DIR ALL in the body of a mail message for more information.  L If you get the packages via WWW or FTP, they're in ZIP format which requiresJ the UNZIP (note: this is not Gnu gunzip!) tool to unpack.  You can get ZIP# and UNZIP from the following areas:   .   ftp://ftp.wku.edu/vms/unzip.exe        ! VAX0   ftp://ftp.wku.edu/vms/unzip.alpha_exe  ! Alpha*   ftp://ftp.wku.edu/vms/fileserv/UNZIP.ZIP/   http://www.decus.de:8080/www/vms/sw/zip.htmlx ,   http://home.earthlink.net/~djesys/zip.html.   http://home.earthlink.net/~djesys/unzip.html  E or you can request the FILESERV_TOOLS package from the e-mail server.   D [Beware: The [000TOOLS...] pre-built versions of ZIP on the OpenVMS G Freeware V4 CD-ROM will erroneously return BILF errors on OpenVMS V7.2  D and later.  Use of the source on the Freeware V4 to rebuild the ZIP I image(s), or acquiring a pre-built ZIP image from one of the above areas  H can avoid this.  The pre-built version of ZIP on the Freeware V4 kit is C older than the included ZIP sources, and it contains a latent bug.]   H Another source of free software is the vmsnet.sources newsgroup (and theJ corresponding vmsnet.sources.d discussion group).  See the monthly postingG "vmsnet.sources archives" for a list of sites which archive submissions  to vmsnet.sources.  F CompuServe users should check out the libraries of the VAXFORUM forum.  K Arne Vajhj runs an OpenVMS WWW page, with software and other pointers, at:    http://www.levitte.org/~ava/   Kermit is available at: $   http://www.columbia.edu/kermit/ or   ftp://kermit.columbia.edu/   ZMODEM is available at: !   ftp://ftp.cs.pdx.edu/pub/zmodem 9 See the FILES file in that directory for further details. F Note that this freeware version of ZMODEM will interoperate only with 6 ZMODEM software that is licensed from Omen Technology. (Also on Freeware CD)  				[Steve Lionel]  G A good source of software for DEC boxes (and anything else pretty much) C is the DECUS library. online catalogs are available as well as some 4 software via ftp.decus.org; there's a gopher server    gopher://gopher.decus.org/ an FTP server:   ftp://ftp.decus.org/ and a WWW server:    http://www.decus.org/   3 Some DECUS library CD-ROMs are available online at: :     http://www.acornsw.com/www/acorn/cdrom-via-www.html or      gopher://gopher.acornsw.com/ 				[munroe@dmc.com]  F Phone for orders is 508 841 3502. Lots of good stuff from lots of good2 folks, and copies on media (tapes, CDs) are cheap. 				[Everhart@Arisia.gce.com]   J    MPJZ's Hyper-Software-List for OpenVMS is Martin P.J. Zinser's list of     additional software.   .      http://axp616.gsi.de:8080/www/vms/sw.html  (    Chris Higgins's VMS Software List II 6      http://csvax1.ucc.ie/www/vms_sw_list/sw_list.html  G    DECUS SIG Tape collections are available on Mark Berryman's system,        ftp://mvb.saic.com   M    David Jones's DECthreads-based HTTP_SERVER World-Wide Web server for VMS.  <      http://kcgl1.eng.ohio-state.edu/www/doc/serverinfo.html  $ 					    [goathunter@WKUVX1.WKU.EDU]  )    Secure Shell (SSH) Server for OpenVMS: 5      http://kcgl1.eng.ohio-state.edu/~JONESD/ssh/DOC/   )    Secure Shell (SSH) Client for OpenVMS:        http://www.free.lp.se/fish/  /    Information on OpenSSL (SSLeay) for OpenVMS: #      http://www.free.lp.se/openssl/ 8                                             [Leo Demers]  D    Information on OpenSSL (SSLeay) and OSU Webserver interoperation:#      http://www.levitte.org/~byerra >                                             [Robert Alan Byer]  G DECwindows Motif V1.2-3 includes NCSA Mosaic 2.4 built for UCX.  V1.2-4 B includes Spyglass Enhanced Mosaic, which supports many "Netscape" B enhancements.    Netscape Navigator is also available for OpenVMS.  I A port of Mosaic 2.7-4 which supports UCX, Multinet and SOCKETSHR/NETLIB   is available from:    ftp://wvnvms.wvnet.edu/mosaic/  ? Lynx (a character-cell World-Wide-Web reader) is available from "   ftp://ftp2.cc.ukans.edu/pub/lynx 					    [Steve Lionel]   L Netscape Navigator will be available as part of the OpenVMS Internet Product! Suite.  For further details, see: @   http://www.openvms.digital.com/openvms/products/ips/index.html  F PGP (Phil Zimmerman's "Pretty Good Privacy") is available from variousH distribution sites, including those listed in the PGP FAQ.   Information. on an OpenVMS download of PGP is available at:   http://www.pgpi.com/(   http://zone.pspt.fi/pgp/platforms/vms/)   http://www.yrl.co.uk/~phil/pds/pds.html   D An archive of DECwindows and X Windows software can be found at the  following sites:  1   http://www2.cenaath.cena.dgac.fr/ftp/index.html 2   http://www2.cenaath.cena.dgac.fr/ftp/decwindows/    ftp://axp.psl.ku.dk/decwindows   ftp://ftp2.cnam.fr/decwindows $   ftp://ftp.et.tudelft.nl/decwindows$   ftp://ftp.ctrl-c.liu.se/decwindows<   http://axp616.gsi.de:8080/wwwar/cena/decwindows/cena.html    (See also Freeware CD) 					    [Patrick Moreau]   I ImageMagick is an X11 package for display and interactive manipulation of E images.  The package includes tools for image conversion, annotation, N compositing, animation, and creating montages.  ImageMagick can read and writeL many of the more popular image formats (e.g. JPEG, TIFF, PNM, XPM, Photo CD, etc.).  =   ftp://ftp.x.org/contrib/vms/ImageMagick/ImageMagick-3.3.zip  (Also on Freeware CD)  					    [cristy@dupont.com]   XV is available from:     ftp://ftp.cis.upenn.edu/pub/xv'   ftp://ftp.digital.com/pub/graphics/xv    http://www.sanface.com/   - GHOSTSCRIPT and GHOSTVIEW are available from: )   ftp://ftp.digital.com/pub/VMS/ghostview   3 Version 2.3 of GhostView-VMS is now available from: +   ftp://iphthf.physik.uni-mainz.de/pub/vms/ * 					   [plass@dipmza.physik.uni-mainz.de]  @ XPDF, a viewer for PDF (Adobe Acrobat) files, is available from:   http://www.foolabs.com/xpdf/9                                             [Ki Suk Hahn]   L A Java-based PDF viewer is available from Adobe, and is known to operate on  recent OpenVMS Alpha releases:   http://www.adobe.com/   H Various OpenVMS-related tools -- both freeware and shareware -- such as ! txt2pdf -- are available from at:    http://www.sanface.com/   F The MPEG library version 1.1 is available for OpenVMS VAX and Alpha at3   ftp://ftp.x.org/contrib/vms/mpeglib-11-vms.readme 0   ftp://ftp.x.org/contrib/vms/mpeglib-11-vms.zip 					    [Patrick Moreau]   4 List of FTP Mirror Sites for the DECWINDOWS archive:3 ===================================================   A AXP.PSL.KU.DK             (Multinet)  Mirror of CENA DECW archive A FTP.ET.TUDELFT.NL         (MadGoat)   Mirror of CENA DECW archive A FTP2.CNAM.FR              (MadGoat)   Mirror of CENA DECW archive   I ftp.x.org (in /contrib/vms)  not really a mirror, but I try to put all my  new ports at this site.   5 List of HTTP Mirror Sites for the DECWINDOWS archive: 4 ====================================================  ;   http://axp616.gsi.de:8080/wwwar/cena/decwindows/cena.html   = Some X clients from the OpenVMS Freeware CDROM are located in # [.DECWINDOWS.CDFREEWARE] directory.  						[Patrick Moreau]    H I have written and installed on INFO.CS.PUB.RO an 'Archie' clone for VMS7 software. Telnet to that machine, and login as VMSARCI. M It contains now listings for over 30 ftp servers with >14 GB of VMS software. H The most useful commands are LIST, which generates a list of scanned ftpG servers, and FIND <string>, whichs looks for a file containing "string" I in the name; the search modes are only "substring" [default] and "exact", L and regex search is not supported (so FIND EMACS will work, but FIND *EMACS*< or FIND *EMACS*.* will not). The search is case-insensitive.I Those of you that know other ftp servers with VMS software that I haven't D found, please let me know. (The program that build the databases canI recursively scan whole servers- as FTP.WKU.EDU, or just some directories-  as NIC.SWITCH.CH /pub/vms)H Sorry, this service is VERY SLOW [by Western standards], because it runsJ on a quite-busy oldie-but-goodie VAXStation 3400 with 20Mb and a RF71, and; the Internet link is only 256 Kpbs (sometimes unavailable).  						[stfp@roipb.cs.ipb.ro]  : Perl 5 (object oriented, blah blah) is available for VMS. $ The primary development ftp site is:  #     ftp://genetics.upenn.edu/perl5/   L But this site is mirrored by more than 47 CPAN sites around the world. Each A CPAN site is accesible via a cgi-bin script at the perl homesite:        http://www.perl.com/CPAN/   3 (PERL can also be found on the OpenVMS Freeware CD)   P Charles Lane maintains a web page on how to write cgi-bin scripts in perl 5 for  VMS at:   :     http://duphy4.physics.drexel.edu/duphy4/cgi_info.htmlx  H and I maintain a web page on how to obtain and compile perl5 for VMS at:  1     http://w4.lns.cornell.edu/~pvhp/perl/VMS.html   F                                           [pvhp@lns62.lns.cornell.edu]     MadGoat Software Archives:     http://www.madgoat.com/   /   Western Kentucky University OpenVMS archives: #     ftp://ftp.wku.edu/vms/fileserv/   9   The Levitte (extended :-) Family (and OpenVMS) website:      http://www.levitte.org/       http://www.levitte.org/~ava/#     http://www.levitte.org/~byerra/      CalTech Software Archives:?     http://seqaxp.bio.caltech.edu/pub/SOFTWARE/AAA_CONTENTS.TXT   *   DJE Systems Website (David J. Dachtera) 3     http://home.earthlink.net/~djesys/freeware/vms/      Web servers:     Apache web server:A       http://www.openvms.digital.com/openvms/products/ips/apache/ =       http://www.er6.eng.ohio-state.edu/~jonesd/apache/1_3_9/      OSU Webserver ?       http://www.er6.eng.ohio-state.edu/www/doc/serverinfo.html #       http://www.kjsl.com/archives/ 1       email list: VMS-WEB-daemon-Request@KJSL.COM   #   CD-R (CD-Recordable) media tools:      please see FILE7  "   Grace (WYSIWYG 2D plotting tool),     http://plasma-gate.weizmann.ac.il/Grace/  K   POV-Ray ("Persistance of Vision" Raytracer) ray-tracing graphics package: 8     http://www.lp.se/~byerra/povray/povray_contents.html  =                                           [Peter Langstoeger]   !   Majordomo mailing list handler: B     http://www.openvms.digital.com/openvms/products/ips/majordomo/  ;   PINE (OpenVMS tools for sending and receiving MIME mail): *     ftp://ftp2.kcl.ac.uk/pub/vms/pine-vms/3     http://www.agh.cc.kcl.ac.uk/files/vms/pine-vms/   6 Menufinder (menu-driven system management environment)"    (currently free on OpenVMS VAX)%    http://www.itre.com/mf/  (Italian) 2    http://www.itre.com/mf/index_en.html  (English)  < ------------------------------------------------------------> SOFT2.  Where can I find the UNIX <whatever> tool for OpenVMS?   POSIX:B   POSIX-compliant, Compaq-supported versions of POSIX routines and   utilities:  C     lex, yacc, grep, tar, uuencode, uudecode, rcs, man, cpio, make, A     awk, ar, mail, etc., the POSIX shell, the POSIX C programming      interface, etc.   @     POSIX utilities can be used from within the POSIX shell, and4     via the DCL `POSIX/RUN POSIX$BIN:tool.' command.  A     POSIX is a separately-installed package, and is licensed with ?     OpenVMS V5.5 later.  The POSIX installation kit is included A     on the consolidated distribution CD-ROM kit, and installation '     kits are also available separately.   D     The POSIX package is no longer supported on OpenVMS, components C     of the POSIX standard such as parts of the POSIX API are being  C     added into OpenVMS.  Versions of POSIX generally do not operate 3     on V7.x OpenVMS VAX and OpenVMS Alpha releases.    C:  H   Common C system and library routines are present in the DEC C run-timeH   library, which is available for V5.5 and later, and is shipped in V6.1I   and later.  DEC C is the upgrade for VAX C, DEC C and VAX C can coexist J   on the same system OpenVMS VAX system, and both compilers can be enabled   via the "C" license PAK.  K     Also see SYS$EXAMPLES:, and (if either is installed) the DECW$EXAMPLES:      and UCX$EXAMPLES: areas.  
 X Windows:%   Various Compaq X Windows utilities:   G     xwd, xev, mosaic WWW browser, xrdb, bmtoa and atobm, xpr, ico, etc.   B     In DECW$UTILS: in DECwindows Motif V1.2-3 and later.  Also see0     DECW$EXAMPLES: for example X and C programs.  ! Miscellaneous tools and examples: 6   Various unsupported OpenVMS tools and code examples:  D     DWAUTH (X Windows SYSUAF authorize-like tool), various versions	C     of grep, fgrep, yacc, vmstar, uuencode, gawk, etc.  html tools, B     the mx SMTP mail exchange package, X windows flight simulator,C     the mxrn X windows news reader, the OSU HTTPD WWW server, a WWW =     gopher browser, etc. are all on the FreeWare V2.0 CD-ROM.   	 IP tools: E   DEC TCP/IP (UCX) contains tools such as ping, uuencode, smtp, snmp, G   rcp, nfs, tnfs, etc.  OpenVMS V6.2 and UCX V3.3 and later can be used F   together in support of the /FTP, /RCP, /RLOGIN, /TELNET, and /TN3270%   qualifiers on various DCL commands.   4     Also see the various C examples in UCX$EXAMPLES:   					[Stephen Hoffman]  	 vi clones   1   Both vile and elvis (vi clones) run on OpenVms.   $   The current version of vile is 7.1   It's available at / 	http://www.clark.net/pub/dickey/vile/vile.html $ 	ftp://ftp.clark.net/pub/dickey/vile 	ftp://id.wing.net/pub/pgf/vile    					[Thomas Dickey]
 GNU tools:  I   Information on the GNU on VMS Project, which aims to port GNU software     to VMS, is available at:       http://vms.gnu.ai.mit.edu/%     ftp://vms.gnu.ai.mit.edu/gnu-vms/      Software info:  '     http://vms.gnu.ai.mit.edu/software/      Software archive:   .     ftp://vms.gnu.ai.mit.edu/gnu-vms/software/   GCC:  M   The Progis company in Germany has ported GCC (GNU C) to OpenVMS Alpha.  You 3   can also find a recent OpenVMS VAX version there.        http://www.progis.de/   K   The latest (known to me) GCC version for VAX/VMS (binaries only) is 2.7.1    from Pat Rankin's site.   &     ftp://ftp.caltech.edu/pub/rankin/    					[Jason Armistead]  = Some of the available console management options for OpenVMS:   1   http://www.robomon.com/robocentral.htm (Heroix) 1   http://www.ki.com/products/clim/  (KI Products) ,   http://www.globalmt.com/ (Global Maintech)!   http://www.tditx.com/ (TechSys) 0   http://www.cai.com/products/commandit.htm (CA)3                                        [Kerry Main]   A If you need to change the file modification date and are looking  > for a utility such as the UNIX touch tool, look at DFU on the > OpenVMS Freeware (DFU SET or simular), or use an existing DCL  commands such as:   5   SET FILE/PROTECT=(current_protection_mask) [...]*.*   < ------------------------------------------------------------G SOFT3.  Where can I get the Netscape Navigator Mozilla.org Web Browser?   > OpenVMS Engineering is currently porting mozilla.org's browserF to OpenVMS -- OpenVMS baselevels are currently available for download.C Mozilla.org is the open source organization providing Netscape and  B other interested parties with a browser.  Netscape is expected to C commercialize this mozilla.org browser, add additional proprietary  G features, and release it as Netscape Communicator (version number TBD). G This Netscape Communicator will contain the features that the Internet  6 community expected to see in Netscape Communicator V5.  D Mozilla.org has announced that it will release a beta version of itsE browser in mid-Autumn 1999.  Soon after, Netscape may/will release a  G beta version of Netscape Communicator based on the mozilla.org browser. F We expect the beta version of Netscape Communicator to be available onH OpenVMS about 1 month after its release by Netscape.  A customer qualityG version of this browser is scheduled for release by mozilla.org in late K December 1999; soon after, Netscape will release a customer quality version B of Netscape Communicator.  We expect to release a customer quality: version of Netscape Communicator on OpenVMS in early 2000.  1 The mozilla.org browser schedule is available at:   !   http://www.mozilla.org/project/   > The latest information and current downloads are available at:  6   http://www.openvms.digital.com/openvms/products/ips/  H Please be aware that various certificates for V3.003 Netscape Navigator G are presently expired, or are starting to expire.  This can potentially G cause problems for certificate-based access pending the acquisition of   new certifcates.   					[Sue Denham]  					[Stephen Hoffman]  < ------------------------------------------------------------) SOFT4.  Where can I get Java for OpenVMS?   D   Java is available on and is included with OpenVMS Alpha, starting F   with the OpenVMS Alpha V7.2 and later releases.  Java download kits :   are available for OpenVMS Alpha V7.1 and later releases.  G   Java is not available on OpenVMS VAX.  As for why: the Java language  H   definition requires a floating point format (IEEE) that is not native E   to VAX, and this would require the emulation of all floating point  H   operations within Java applications.  Further, the C source code used D   to implement for Java itself is heavily dependent on passing IEEE H   floating point values around among the many internal subroutines, and G   adding support for VAX would entail changes to the Compaq C compiler  I   for OpenVMS VAX -- and specifically to the VAX VCG code generator that  H   is used by Compaq C on OpenVMS VAX systems -- in order to add support I   for passing IEEE-format floating point doubles around.  Alternatively,  J   extensive changes to the Java source code to remove the assumption that -   the double is an IEEE floating point value.   F   There are currently no plans to make a version of Java available forI   OpenVMS VAX.  (A prototype version of Java was created for OpenVMS VAX, 6   and performance was found to be inadequate at best.)  H   If Java2 or other environment lifts the requirements for IEEE floatingK   point as part of the language definition, this decision may be revisited.   F   For additional information on Java for Alpha systems, please see theA   OpenVMS documentation (V7.2 and later), and the following site:   0     http://www.digital.com/java/alpha/index.html  < ------------------------------------------------------------H SOFT5.  VAX C and DEC C, and other OpenVMS C Programming Considerations?  F   VAX C V3.2 was released for OpenVMS VAX systems in 1991.  DEC C V4.0F   replaced VAX C V3.2 in 1993 as the Compaq C compiler for OpenVMS VAXF   systems.  Compaq C is the AMSI C compiler for OpenVMS Alpha systems.E   VAX C predates the ANSI C standards, and has various areas that are J   not compliant with ANSI C requirements.  Compaq C is an ANSI C compiler,H   and can also compile most VAX C code when /STANDARD=VAXC is specified.I   Versions of this compiler between V3.2 and V6.0 (exclusive) were known     as either DEC C or DIGITAL C.   F   Both compilers can be installed at the same time on the same OpenVMSD   VAX system, allowing a migration from VAX C to DEC C, and allowingF   the same DEC C code to be used on OpenVMS VAX and OpenVMS Alpha.  In0   1999, the C compiler version is Compaq C V6.0.  B   The system manager can choose the system default C compiler whenF   Compaq C is installed on a system with VAX C, and a C programmer canK   explicitly select the required compiler for a any particular compilation.   K   A current "C" license PAK allows access to both VAX C and Compaq C on the    same OpenVMS VAX system.  M   Various Compaq C versions can be installed on OpenVMS VAX V5.5-2 and later. L   OpenVMS VAX releases such as V5.5-2 and V6.0 will require the installationK   of a Compaq C RTL kit, a kit that is included with the Compaq C compiler. I   OpenVMS VAX versions V6.1 and later do not require a seperate RTL kit,  I   but Compaq C RTL ECO kits are available to resolve problems found with  (   the C RTL on various OpenVMS releases.  E   Wwith Compaq C, for automatic resolution of the standard C library  D   routines by the LINKER utility, use the /PREFIX qualifier, such asG   /PREFIX=ALL_ENTRIES.  If a particular application program replaces an E   existing C library routine, use /PREFIX=(ALL_ENTRIES,EXCEPT=(...)). E   (VAX C required explicit specification of an RTL shareable image or $   C object library during the link.)  H   When the /PREFIX is requested, the compiler generates a "decc$" prefixI   on the specified symbols.  This prefix allows the LINKER to resolve the G   external symbols against the symbols present in the DECC$SHR library. F   The DECC$SHR library is included in the IMAGELIB.OLB shareable imageH   library, and IMAGELIB is searched by default when any program (writtenE   in any language) is LINKed.  Because the standard C library routine F   names are very likely to match application routines written in otherF   languages, a prefix "decc$" is added to the C symbol names to assureD   their uniqueness; to prevent symbol naming conflicts.  C programs,E   however, can sometimes have private libraries for various purposes, I   and the external routines share the same names as the library routines. F   (This is not recommended, but there are applications around that useE   this technique.)  Thus the need to explicity specify whether or not E   the "decc$" prefix should be prepended to the external symbol names    by the compiler.  F   The qualifiers, and most (all?) with associated pragmas, that may be<   of interest when migrating VAX C code to Compaq C include:       /PREFIX=ALL_ENTRIES B       As mentioned above.  Failure to specificy this qualifier canA       cause the compiler to not add the prefixes for the names of E       the C library routines into the references placed in the object E       module, which can in turn cause problems resolving the external <       symbols in the library when the object code is linked.  $     /ASSUME=WRITABLE_STRING_LITERALSC       Some VAX C programs erroneously write to the string literals. B       By default, Compaq C does not allow the constants to change.       /SHARE_GLOBALSA       Enables sharing ("shr") of globals and of extern variables. G       Compaq C sets externs as non-shareable ("noshr"), VAX C as "shr".        /EXTERN_MODE=COMMON_BLOCK =       VAX C assumes common block model for external linkages.        /[NO]MEMBER_ALIGNMENT A       Refers to the padding placed between member elements within ?       a struct.  Disabling member alignment packs the data more =       tightly into memory, but this packaging has performance ;       implications, both on OpenVMS VAX and particularly on        OpenVMS Alpha systems.  E   Permit structure members to be naturally aligned whenever possible, E   and avoid using /NOMEMBER_ALIGNMENT.  If you need to disable member A   alignment, use the equivilent #pragma to designate the specific E   structures.  The alignment of structure members normally only comes B   into play with specific unaligned data structures -- such as theF   sys$creprc quota itemlist -- and with data structures that are usingD   data that was organized by a system using byte or other non-member   alignment.  I   Versions of Compaq C such as V6.0 include the capability to extract the D   contents of the standard header libraries into directories such asG   SYS$SYSROOT:[DECC$LIB...], and provide various logical names that can G   be defined to control library searches.  With Compaq C versions such  H   as V6.0, the default operations of the compiler match the expectationsC   of most OpenVMS programmers, without requiring any definitions of G   site-specific library-related logical names.  (And logical names left E   from older DEC C versions can sometimes cause the compiler troubles    locating header files.)   F   Example C code is available in SYS$EXAMPLES:, in DECW$EXAMPLES (whenF   the DECwindows examples are installed), in UCX$EXAMPLES (when CompaqE   TCP/IP Services is installed), on the Freeware CD-ROMs, and at web     sites such as   *     http://www.openvms.digital.com/wizard/  < ------------------------------------------------------------/ SOFT6.  Obtaining user input in DCL CGI script?   E If you choose to use the GET method, then the form data is available  6 in the DCL symbol QUERY_STRING, in URL-encoded format.  E If you use the POST method, then you need to read the form data from  E stdin. For a DCL CGI script running under the Netscape FastTrack web  ? server, you can read the data using the following READ command:      $ READ SYS$COMMAND postdata    to read the information in. =                                                 [Colin Blake]   @ The following describes the use of DCL command procedures as CGI  scripts with the OSU web server:  2 http://www.levitte.org/~ava/cgiscripts_other.htmlx>                                                 [Leif Jansson]  < ------------------------------------------------------------/ SOFT7.  How do I get my own batch entry number?   > To have a batch procedure retrieve its own batch entry number, use the following:  '   $ Entry = F$GETQUI("DISPLAY_ENTRY", - 0       "entry_number","display_entry","this_job")  E Remember that the entry numbers issued by the OpenVMS Job Controller  E are opaque longword values.  Don't assume you know the format of the  1 number, nor the range of numbers you might see... >                                                 [Peter Weaver]  < ------------------------------------------------------------. SOFT8.  How do I convert to new CMS libraries?  E A change was made to the format of the CMS database for CMS libraries C starting with V3.5-03 -- to ensure that earlier versions of CMS are B unable to access the database once the "conversion" to V3.5-05 andG later is made, you must issue the following two commands when upgrading B from V3.5-03 and prior.  (The only differences between CMS versionA V3.5-03 and CMS version V3.5-05 involve changes to ensure that np < earlier version of CMS can access the "converted" database.)  B To perform the "conversion", issue the following commands for each CMS library present:  ,     $ RENAME disk:[directory]00CMS.* 01CMS.**     $ COPY NLA0: disk:[directory]00CMS.CMS  B The new file 00CMS.CMS must have the same security settings as theG 01CMS.CMS file, and is created solely to ensure continued compatibility E with tools that expect to find a 00CMS.CMS file (eg: various versions . of the Language-Sensitive text editor LSEDIT).  < ------------------------------------------------------------@ SOFT9.  Where can I get new certificates for Netscape Navigator?  @ The URLs that I found for adding/updating root certificates are:  E http://www.entrust.net/customer/generalinfo/import.htm        entrust D http://www.equifaxsecure.com/servercert/rollover.html         thawteF https://www.verisign.com/server/prg/browser/root.html         verisign6                                           [Ken Chaney]  > To update certificates in Netscape Navigator V3.03 on OpenVMS, use the following:  8 Here's how to update your Root certificates in Netscape:  0 Thawte Server certificate which expired in 1998:  : 1) Under the Options Menu choose "Security Preferences..."% 2) Select the "Site Certificates" tab 8 3) Select "Thawte Server CA" in the list of certificates, 4) Select "Delete Certificate" and then "OK". 5) Go to http://www.thawte.com/serverbasic.crtL 6) Follow the instructions on the popup dialog box to accept the certificateH    This mostly involves hitting the "Next" button and clicking an acceptI    button and then naming the resulting certificate.  I named it the same     name as the original.  ; VeriSign/RSA Server certificate which expired Dec 31, 1999:   : 1) Under the Options Menu choose "Security Preferences..."% 2) Select the "Site Certificates" tab E 3) Select "Verisign/RSA Secure Server CA" in the list of certificates , 4) Select "Delete Certificate" and then "OK"> 5) Go to https://www.verisign.com/server/prg/browser/root.htmlL 6) Follow the instructions on the popup dialog box to accept the certificateH    This mostly involves hitting the "Next" button and clicking an acceptG    button and then naming the resulting certificate.  Verisign suggests      using the name "VeriSign CA".  ;                                           [Vance Haemmerle]   < ------------------------------------------------------------1 SOFT10. Why doesn't DCL symbol substitution work?   F The DCL symbol substitution processing occurs only at the DCL prompt, E not within data and not within files.  If you wish to perform symbol  C substitution in this environment, you typically write a small file  E containing the command(s) and data to be invoked -- potentially only  C the data -- and you then invoke the created procedure or reference   the specified data.   C In this case, use of a file containing nolinemode commands or other C techniques might be useful -- you will want to ensure that the text F editor you use does not attempt to use screen mode or similar, as thisD is not generally considered adventageous within a command procedure.  . Tools such as FTP have alternatives: COPY/FTP.  E DCL symbol substitution occurs in two passes, using the ampersand and E the apostrophe.  In most cases, only the apostrophe is necessary.  In G a few cases -- such as the DCL PIPE command -- you will may need to use E the ampersand to get the substitution to work.  The following example B uses ampersand substitution to transfer the contents of the header into a logical name:  F   $ PIPE CC/VERSION | (READ SYS$PIPE hdr ; DEFINE/JOB/NOLOG hdr &hdr )  G A logical name (in the job logical name table; shared by all processes  G in the current job) was used as DCL symbols cannot be returned back out , from a DCL PIPE or other spawned subprocess.   [End of Part 4/4]   N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com