-    1,   22
-  675
2 /MENU

	Invokes the MENU program which creates an interface 
between DCL and a form created under FMS.

    Format:

	FMS/MENU[/qualifier] library form

3 Parameters

	"library" is the FMS forms library which will be used
	"form" is the form within the library.

	Note that if the /VERSION qualifier is used, that the
	library and form names are not required and if present
	will be ignored.

3 Qualifiers

</VERSION
	Displays the current version of MENU

</LOCAL
Normally, MENU will search both the LOCAL and GLOBAL DCL symbol tables
for the default values of the fields.  If /LOCAL is specified, only
the local symbol table will be searched. By default both the local and
global symbol tables will be searched with the local symbol table
being searched first. 

</VALID
MENU can validate the contents of a form at run time based on the
contents of the forms Named Data area.  The /NOVALID option disables
this validation process.  Note that /NOVALID is the same as specifying
 /NOLEGAL/NORANGE on the same command line. 

See the help on Validation for more details

</LEGAL
MENU can validate both ranges of number and legal character strings.
If the /NOLEGAL option is selected only numerical range checking is
enabled. 

See the help on Validation for more details

</RANGE
MENU can validate both ranges of number and legal character strings.
If the /NORANGE option is selected only character string checking is
enabled. 

See the help on Validation for more details

3 Description_and_Use
MENU is a utility for interfacing FMS forms with DCL. It displays a
form out of the selected library and creates local DCL symbols
corresponding to the field names in the forms. MENU also will display
default values for form fields if those fields are defined prior to
starting the program. 
3 Validation
MENU can validate the contents of fields in three ways:

	o  Legal character strings
	o  Range testing
	o  Numerical radix checking

Validation is requested by creating a named data item within the FMS
form of the same name as the field being validated. The contents of
the named data string form the validation string. 
4 Character_string_validation

If one wished to validate character strings the named
data portion of the FMS screen would look like this:

	1	Name FIELD_NAME
	/LEGAL=(STRING1,STRING2,STRING3)[/MESSAGE="Error message text"]

Where FIELD_NAME must correspond to the name of the FMS field being
validated and "STRING1", "STRING2" and "STRING3" are the valid
character strings.  If a legal character string must contain a space,
the string must be enclosed in quotes ("). 

An optional error message may be included with the /MESSAGE = text
qualifier. If this text is not present MENU constructs a 
default error message. 
4 Range_Validation

If one wished to validate the range of a numerical field, the
named data portion of the FMS screen would look like this: 

	1	Name FIELD_NAME
	/LOWER=XXXX/UPPER=YYYY [/MESSAGE="Error message text"]

Where FIELD_NAME must correspond to the name of the FMS field being
validated.  The above example tests for both upper and lower ranges
but if only low limit or high limit testing is desired, only one may
be used.  The values for the range limits may begin with radix
indicators (e.g. %X to store a hexicecimal number, %O for an octal
number, %D for a decimal number, and %B for a binary number). The
default radix is decimal.

If desired, an optional error message may also be included.
4 Radix_Validation

If the named data string for validation contains a /RADIX qualifier,
MENU will test the input string for valid radix before testing the
legal range.  Legal values for /RADIX are: 

	/RADIX=OCTAL
	/RADIX=DECIMAL
	/RADIX=HEXIDECIMAL
	/RADIX=BINARY
All of which may be abbreviated to their first letter

If one wished to validate the radix of a numerical field, the
named data portion of the FMS screen would look like this: 

	1	Name FIELD_NAME
	/RAD=HEX/LOWER=XXXX/UPPER=YYYY [/MESSAGE="Error message text"]

/