NET/MASTER Network Control Language (NCL) Programmer's Guide

Defining Field Characters in a Panel Description File
Working With Panels
14–46 106160 Tandem Computers Incorporated
Finally, observe the post-panel values of the unchanged input variables:
(07:19) --------------------- OPERATOR CONTROL SERVICES ----------------------
Post-panel values are
John
Janet
Jack
Jill
James
Joyce
1A1
1A1
1A1
A1
A1
A1
1A1
1A1
1A1
NNM1005 START ZEX1408N PROCESSING COMPLETE. NCLID 001084
_____________________________________________________________________________
---------- ------------------ NonStop NET/MASTER D30 ---------------- --------
M=>
Defining Edit Rules for
Input Fields
There are many options you can use to specify the type of data that an input field can
accept. These are called internal validation rules and, when specified, are used by
Panel Services to analyze data before it is passed to an NCL process. You can specify
the following:
Whether an input field is mandatory, using the REQ operand of the #FLD
statement:
#FLD ^ REQ=YES
The characters that an input field can contain, using the EDIT operand of the #FLD
statement:
#FLD ~ EDIT=ALPHA
Whether a field can contain embedded blanks, using the BLANKS operand of the
#FLD statement:
#FLD ~ BLANKS=TRAIL
Defining Hexadecimal Field
Characters
There are two ways of defining field characters: using character mode and using
hexadecimal mode. As the preceding examples show, using character mode you can
define any character other than an alphanumeric character, an ampersand (&), a blank,
or a null character as a field character.
You can use hexadecimal mode to define a field character when you are defining a
large number of field characters within one panel description file and have exhausted
the set of available nonalphanumeric characters.