  A The GNM tools allow you to have a common source file for both an  < OpenVMS message file and for DECdocument SDML documentation.  B GEN_MSG converts a .GNM file into a standard OpenVMS message file,D which can then be processed by the MESSAGE compiler and (optionally)= with MESSAGE/SDL and the SDL tool to create language-specific  include files.  @ GEN_SDML converts the same .GNM file into a standard DECdocument* .SDML file for inclusion in documentation.  : The .GNM file can be thought of as a series of directives:  3    .NAME	    - The message symbol without the VDE$_ 5    .MESSAGE	    - The message text, it may be wrapped A    .EXPLANATION    - The description that appears in the document G    .USER_ACTION    - The recovery section that appears in the document. ;    .BREAK	    - May be used to start a new paragraph in the $ 		      .explanation or .user_actionH    .DESTINATION    - Which file the following appears in, parameters are 		      both, message E    .SEVERITY       - informational, success, warning, error, or fatal   D The first 4 directives: .name, .message, .explanation, .user_action,B occur as a group in that order for each message.  .explanation andA .user_action are optional.  The FAO arguments within the .message B are contained within <>.  Within the <> there are 2 arguments, the@ first is a word which will be emphasized in that position in theA document, the second is the FAO argument which will appear in the   message file in that position.    D The .destination directive must appear between message groups and isB in effect until another .destination directive occurs.  Thus, whenC one message is to goto the message file only a .destination message B will precede the message group and a .destination both will follow the group.    E .FACILITY and .END frame the contents of the GNM file.  The arguments F on the .FACILITY directive indicate the facility name and the facilityE number, and the directive also accepts qualifiers to pass through to  % the MESSAGE file .FACILITY directive.   D Use spaces for the indentation of the message text and explanations.  * The following is an example of a GNM file:    ( .facility	facnam,facnum /PREFIX=prefix$_ ! , ! Success messages go here.  DO NOT REORDER. !  .severity success  .destination message   .name	    SUCCESS1 .message	successful + .explanation	This message indicates success  .user_action	None required ! 2 ! Informational messages go here.  DO NOT REORDER. ! 	 .base 500  .severity informational  .destination both    .name	    INFO1 - .message	information <text, !AC> is displayed A .explanation	This message informs you of something, and shows how 6 		to include some text in the message using a standard                 FAO directive. .user_action	None required   ! , ! Warning messages go here.  DO NOT REORDER. ! 
 .base 1000 .severity warning  .destination both    .name	    WARNING1 .message	ambiguous '<text,!AC>' D .explanation	Cannot complete the command because '<EMPHASIS>(text)' . 		is ambiguous in the context of this command. .user_action	None required   ! * ! Error messages go here.  DO NOT REORDER. ! 
 .base 1500 .severity error  .destination both    .name	    ERROR1 .message	whoops " .explanation	unknown mystery error7 .user_action	Wave a rubber chicken over the application    ! D ! Fatal messages go here.  DO NOT REORDER.  Very few messages should ! be of fatal severity.  ! 
 .base 2000 .severity fatal  .destination both    .name	    FATAL1 .message	crash( .explanation	unknown fatal mystery error4 .user_action	Wave a rubber chicken over the computer   .end