1. $ SHOW DEVICE KUDOS
      %SYSTEM-W-NOSUCHDEV, no such device available
      $ HELP/MESSAGE

      The first command creates an error. The default HELP/MESSAGE
      command (with no qualifiers) displays a description of the
      SYSTEM facility message NOSUCHDEV.

   2. $ HELP/MESSAGE ACCVIO
      $ HELP/MESSAGE/BRIEF ACCVIO
      $ HELP/MESSAGE/FACILITY=SYSTEM ACCVIO
      $ HELP/MESSAGE VIRTUAL ACCESS
      $ HELP/MESSAGE/STATUS=12
      $ HELP/MESSAGE/STATUS=%XC

      These commands demonstrate how you can use various qualifiers
      to access and display the ACCVIO message (sometimes several!)
      in different formats.

   3. $ HELP/MESSAGE/BRIEF ACC
      $ HELP/MESSAGE/BRIEF/WORD_MATCH=WHOLE_WORD ACC

      In the first command, Help Message by default matches dozens of
      words beginning with the string "ACC." The /WORD_MATCH=WHOLE_WORD
      qualifier dramatically refines the search to match the exact word
      only.

   4. $ HELP/MESSAGE/FACILITY=(BACKUP,SHARED)/SORT/OUTPUT=MESSAGES.TXT

      This command selects all messages issued by the BACKUP
      facility and those messages documented as "Shared by several
      facilities," alphabetizes them, and outputs them to a printable
      file called MESSAGES.TXT.

      By selecting the messages you want and directing them to a
      file, you can create and print your own customized messages
      documentation.

   5. $ HELP/MESSAGE/EXTRACT=BADMESSAGE.MSGHLP BADMESSAGE

      $ HELP/MESSAGE/DELETE=BADMESSAGE.MSGHLP-
      _$ /LIBRARY=SYS$LOGIN:MYMESSAGES.MSGHLP$DATA

      $ CONVERT SYS$LOGIN:MYMESSAGES.MSGHLP$DATA-
      _SYS$LOGIN:MYMESSAGES.MSGHLP$DATA

      $ PURGE SYS$LOGIN:MYMESSAGES.MSGHLP$DATA
      $ HELP/MESSAGE/INSERT=BADMESSAGE.MSGHLP

      The first command in this sequence extracts the hypothetical
      message BADMESSAGE from the default database and outputs it to
      file BADMESSAGE.MSGHLP.

      The second command uses the BADMESSAGE.MSGHLP file to delete
      the BADMESSAGE description from the MYMESSAGES.MSGHLP$DATA file
      specified by the /LIBRARY qualifier.

      The next two commands compress the MYMESSAGES.MSGHLP$DATA file
      to save disk space after the deletion.

      The last command uses the BADMESSAGE.MSGHLP file (possibly
      an edited version at a later time) to insert the BADMESSAGE
      message into the default .MSGHLP$DATA file.

   6. $ HELP/MESSAGE/EXTRACT=NOSNO.MSGHLP NOSNO
      $ EDIT/EDT NOSNO.MSGHLP

      1NOSNO, can't ski; no snow
      2XCSKI, XCSKI Program
      3Your attempt to ski failed because there is no snow.
      4Wait until there is snow and attempt the operation again.
      5If you don't want to wait, go to a location where there is
      5snow and ski there.
      5
      5Or, try ice skating instead!
      [EXIT]

      $ HELP/MESSAGE/INSERT=NOSNO.MSGHLP

      This command sequence shows how users with write access to
      OpenVMS supplied .MSGHLP$DATA files can add a comment to a
      OpenVMS supplied message.

      The first command extracts hypothetical message NOSNO to file
      NOSNO.MSGHLP. The second command edits the .MSGHLP file to add
      a comment at the end of the message. Each comment line, even
      blank lines, includes a "5" prefix. The next command updates
      the database by using NOSNO.MSGHLP to insert the updated
      message into the default .MSGHLP$DATA file.