Plarch 30, 1979
324.2 lBPl VPl/370 CPlS User's Guide

Pg. of GC20-1819-2 Rev March 30, 1919 by Supp. SD23-9024-1 for 5148-118 Section 18. HELP File Naming Conventions
and Creation
The HELP facility enables the user to: I • Extend the command and .essage description files IBft provides with I additional description files of the user's choice I • Produce a formatted terminal display by using the HELP format words I when creating the HELP description file
Naming Conventions When you extend the HELP text files IBft provides, you must use the
following naming conventions for the HELP files: I • The filename for components, commands, subcommands, or EXECs must be I the exact full name of the component, command, subcommand, or EXEC. I • The filename for messages has the form xxxnnnt where:
xxx is the component code
messages). See component code prefixes.
nnn is the .essage number.
prefix (for example, for a DftS for list of ces the
t 1.5 the lIessage eMS). (for example. E for error messages in
For example, the filename for the eMS message "NO FILENAME SPECIFIED" would be DMS001E. I • The filetype for components, commands, or EXECs is 'HELPxxxx' where I xxxx identifies the system associated with this component, command, I or EXEC. For example, the filetype for a CMS command would be I 'HELPCMS'. I • The filetype for subcommands is 'HELPxxxx' where X%XX identifies the I command name associated with this subcommand; for example, DEBU for I the DEBUG com.and. I • The filetype for messages is 'HELPMSG'. I • The filetype for a list of all supported commands for a given I function is 'HELPMENU'. The following examples illustrate the naming conventions required to
interface with the HELP command. ACCESS E:CIT CHANGE DMS186i CMS HELPCMS HELPCMS HELPEDIT HELPMSG HELPMENU A CMS command description
A CMS command description
An EDIT subcommand description
A message description
A list of the CMS command and/or EXEC names
supported by the HELP facility Section 18. HELP File Naming Conventions and creation 324.3