MFLD Statement Syntax

Batch Compiler Statements › Statements for Automatic Panel Definition › MFLD Statement Syntax

MFLD Statement Syntax

Functions Performed

An MFLD statement for MAP AUTOPANEL is used to add a map field to a map by performing the following functions:

Creating and maintaining a single map field occurrence and associated panel field occurrence for the specified map and panel occurrences in the most recent MAP AUTOPANEL statement.
Identifying the map field occurrence in the data dictionary with a name that is unique within the owner map occurrence.
Identifying the panel field occurrence with a name composed of a 5-digit identifier with the prefix AUTOPF. The name AUTOPF00001 is assigned to the first panel field occurrence generated for the map, AUTOPF00002 is assigned to the second panel field occurrence generated for the map, and so forth.
Specifying characteristics for the field, such as the following:
- Field occurrences for multiply-occurring fields
- Screen locations of the field by row and column
- Physical attributes of the field, such as display color
- Field values for literal fields
- Delimit characteristics
- Variable field type, as follows:
  - The DFLD specification establishes the field as a data field and relates it to a single existing record element in the data dictionary. Additional specifications, such as automatic editing criteria, can be made for data fields.
  - The MESSAGE LENGTH specification establishes the field as a message field and defines the length of the field. establishes the field as a page field and defines the length of the field.
  - The RESPONSE LENGTH specification establishes the field as a response field and defines the length of the field. A response field is meaningful only when the map is used by a CA ADS dialog.

►►──┬──────────┬─ MFld ───────────────────────────────────────────────────────►
    ├─ ADD ────┤
    └─ MODify ─┘

 ►──┬───────────────────────────────────────┬─────────────────────────────────►
    └─ OCCURS ─┬─ 1 ◄ ────────────────────┬─┘
               └─ occurrence-count times ─┘

 ►──┬─────────────────────────────────────────────────────────────────────────►
    ├─ FOR ALL ◄ ────────────────────┬────────────────────────────────────────
    │         ┌────── , ──────┐      │
    └─ FOR ( ─▼─ device-code ─┴─ ) ──┘

 ►────────────────────────────────────────────────────────────────────────────►
  ─┬───────────────────────────────────────┬──────────────────────────────────
   └─ AT ─┬─ ANYwhere ───────────────────┬─┘
          │ ┌──────────────────────────┐ │
          └─▼─ ( row ─┬─ 1 ◄ ────┬─ ) ─┴─┘
                      └─ column ─┘
 ►────────────────────────────────────────────────────────────────────────────►
  ─┬──────────────────────────────────────────┬───────────────────────────────
   └─ ATTRibutes = ─┬─ NONE ────────────────┬─┘
                    └─ ( attributes-list ) ─┘

 ►────────────────────────────────────────────────────────────────────────────►
  ─┬───────────────────────────────────┬──────────────────────────────────────
   ├─ DELIMit ─┬──────┬──┬─ SKIP ◄ ─┬──┤
   │           ├─ IS ─┤  └─ NOSKIP ─┘  │
   │           └─ = ──┘                │
   └─ NODELIMit ───────────────────────┘

 ►────────────────────────────────────────────────────────────────────────────►
  ─┬───────────────────────────────────────────┬──────────────────────────────
   └─ PAGing type ─┬──────┬─┬─ DETail STart ─┬─┘
                   ├─ IS ─┤ ├─ DETail ONLY ──┤
                   └─ = ──┘ ├─ DETail ENd ───┤
                            ├─ FOOTer STart ─┤
                            └─ NULl ◄────────┘
 ►──────────────────────────────────────────────────────────────────────────┬─►
  ─┬──────────────────────────────────────────────────────────────────────┬─┘
   └─ VALue ─┬────┬─┬─ 'data-value' ────────────────────────────────────┬─┘
             ├ IS ┤ │    ┌─────────────────────────────────────────┐    │
             └ = ─┘ └─( ─▼─┬──────────────────────┬─ 'data-value' ─┴─ )─┘
                           └─ (occurrence count) ─┘

 ►─┬─ CURSOR ─────┬───────────────────────────────────────────────────────────►
   └─ NOCURSOR ◄ ─┘

 ►─┬─ LITeral ◄ ─────────────────────┬────────────────────────────────────────►◄
   ├─ MESSage LENgth ─┬─ length ─┬───┤
   │                  └─ 80 ◄ ───┘   │
   ├─ PAGE LENgth 4 ─────────────────┤
   ├─ RESPonse LENgth ─┬─ length ─┬──┤
   │                   └─ 80 ◄ ───┘  │
   └─ DFld dfld-specifications ──────┘

Expansion of dfld-specifications

►►─── data-field-name ─┬────────────────────────┬─────────────────────────────►
                       └─ ( subscript-number ) ─┘

 ►─┬──────────────────────────────────────────────────────┬───────────────────►
   └─ OF ─┬─ record-name ─┬──────────────────────────┬──┬─┘
          │               └─ VERsion version-number ─┘  │
          └─ role-name ─────────────────────────────────┘

 ►──┬─────────────────────────────────────────────────────────────────────────►
    └─ HELP ──────────────────────────────────────────────────────────────────

 ►────────────────────────────────────────────────────────────────────────────►
  ──── SOUrce ─┬─ NONE ───────────────────────────────────────────────────────
               └─ MODule module-name ─┬─────────────────────────────────────┬─
                                      └─ VERsion ─┬──────┬─ version-number ─┘
                                                  ├─ IS ─┤
                                                  └─ =  ─┘

 ►──────────────────────────────────────────────────────────────────────────┬─►
  ────────────────────────────────────────────────────────────────────┬─────┘
  ──┬────────────────┬────────────────────────────────────────────────┘
    ├─ HALF screen ◄─┤
    └─ FULL screen ──┘
 ►─┬─ REQuired ───┬───────────────────────────────────────────────────────────►
   └─ OPTional ◄ ─┘

 ►─┬───────────────────────────────────────┬──────────────────────────────────►
   └─ REVerse NUMeric ─┬──────┬──┬─ Yes ─┬─┘
                       ├─ IS ─┤  └─ No ──┘
                       └─ = ──┘

 ►─┬──────────────────────────────────────────────────────────┬───────────────►
   └─ UNDERSCORE when blank ──┬─ No ◄─┬───────────────────────┘
                              └─ Yes ─┘

 ►─┬─ NOEDIT ◄ ───────────────────────────────────────────────────────────────►
   └─ EXTernal PICture ─┬───────┬─┬─ 'picture'──┬─────────────────────────────
                        ├─ IS ──┤ └─ INTernal ──┘
                        └─ = ───┘
 ►────────────────────────────────────────────────────────────┬───────────────►
  ─┬──────────────────────────┬─┬───────────────────────────┬─┘
   ├─ ZEROed ◄ ─┬─ when null ─┘ ├─ DISPlay ◄ ─┬─ when zero ─┘
   └─ RETAINed ─┘               └─ BLANK ─────┘

 ►─── EDIT TABle ─┬──────┬─┬─ NULL ◄ ─────────────────────────────────────────►
                  ├─ IS ─┤ └─ table-name ─┬──────────────────────────┬────────
                  └─ = ──┘                └─ VERsion version-number ─┘

 ►──────────────────────────────────────────────┬─────────────────────────────►
  ─┬─ LINK ◄ ─┬─┬─────────────────────────────┬─┘
   └─ NOLINK ─┘ └─ USAGE is ─┬─ VALIDate ───┬─┘
                             ├─ INVALIDate ─┤
                             └─ DEFault ◄ ──┘

 ►─┬────────────────────────────────────────────────────────────────────────┬─►
   └ CODE TABle ─┬────┬─┬ NULL ◄ ──────────────────────────────────────────┬┘
                 ├ IS ┤ └ table-name ─┬────────────────────────┬─┬ LINK ◄ ┬┘
                 └ = ─┘               └ VERSION version-number ┘ └ NOLINK ┘

 ►─┬───────────────────────────────────┬──────────────────────────────────────►
   └─ ERROR MESSage ──┬─ 'message'───┬─┘
                      ├─ message-id ─┤
                      └─ NULL ◄ ─────┘
 ►──┬─────────────────────────────────────────────┬───────────────────────────►
    └─ MSG PREFIX ─┬──────┬───┬──── DC ◄ ─────────┤
                   ├─ IS ─┤   └─ message-prefix ──┘
                   └─ =  ─┘

 ►─┬──────────────────────────────────────────────────────────────────────────►
   └─ FOR INput ─┬───────────────────────┬─┬──────────────────────────┬───────
                 └─ JUSTify ─┬─ Left ──┬─┘ └─ PAD ─┬─ No ◄ ─────────┬─┘
                             └─ Right ─┘           └─ with literal ─┘
 ►────────────────────────────────────────────────────────────────────────────►
  ─┬────────────────────┬─────────────────────────────────────────────────────
   └─ DATA ─┬─ YES ◄ ─┬─┘
            └─ NO ────┘
 ►────────────────────────────────────────────────────────────────────────────►
  ─┬───────────────────────────────────────────────────────────┬──────────────
   └─ UPPERCASE ──┬─ NO ◄─┬────────────────────────────────────┘
                  └─ YES ─┘

 ►────────────────────────────────────────────────────────────────────────┬───►
   ─┬─────────────────────────────────────┬── WITH AUTOedit ─┬─ NO ◄ ───┬─┘
    └─ EDIT ─┬───────┬─ edit-module-name ─┘                  ├─ BEFore ─┤
             ├─ IS ──┤                                       └─ AFTer ──┘
             └─ = ───┘

 ►─┬──────────────────────────────────────────────────────────────────────────►
   └─ FOR OUTPUT ─┬───────────────────────┬─┬────────────────────────┬────────
                  └─ BACKscan ─┬─ YES ──┬─┘ └─ DATA ─┬─ YES ◄ ─────┬─┘
                               └─ NO ◄ ─┘            ├─ NO ────────┤
                                                     ├─ ERASE ─────┤
                                                     └─ ATTRibute ─┘

 ►────────────────────────────────────────────────────────────────────┬─ . ───►◄
  ─┬──────────────────────────────────┬── WITH AUTOedit ─┬─ NO ◄ ───┬─┘
   └─ EDIT ─┬────┬─ edit-module-name ─┘                  ├─ BEFore──┤
            ├ IS ┤                                       └─ AFTer ──┘
            └ = ─┘

Parameters

ADD/MODIFY

Specifies the action taken with regard to the MFLD statement. The DELETE verb cannot be specified for MFLD statements for MAP AUTOPANEL.

Note: For information about how to remove a field occurrencefrom a map occurrence that was defined by a MAP AUTOPANEL statement, see "Compiler Action Verbs."

MFLD

Introduces the clauses that define a map field and associated panel field occurrence.

OCCURS 1/occurrence-count TIMES

Specifies the number of times the field is to appear on the map; the default is 1.

FOR ALL /(device-code-a)

Associates the specified screen sizes with field specifications established by subsequent AT, ATTRIBUTES, DELIMIT, and VALUE clauses. If the map is used with more than one screen size, multiple FOR specifications can be included in the MFLD statement to establish different information for each screen size.

For a more detailed description of this latter use of the FOR specification, see "Defining Versions of Maps for Different Devices."

A field is associated with specific devices as follows:

ALL

Specifies that subsequent clauses of the MFLD statement apply to all screen sizes specified in the related DEVICES clause.

(Device-code-a)

Specifies one or more devices. Subsequent clauses of the MFLD statement apply only to the designated screen sizes. More than one device-code-a specification can be included in a FOR clause. The number of valid device-code-a specifications depends on the number of screen types declared in the related DEVICES specification.

Valid screen sizes are 12X40, 12X80, 24X80, 32X80, 43X80, and 27X132. Device specifications must be enclosed in parentheses and separated by commas; for example, FOR (12X40,12X80).

AT ANYWHERE/ (row,1/column)

Specifies the screen coordinate of the attribute byte for a field by row and column. The coordinate establishes the location of a runtime field on a given screen. An attribute byte is a nondisplayable character that precedes the displayed field and defines the field's attributes.

The field itself is displayed starting at the coordinate that immediately follows the nondisplayable attribute byte. For example, a field displays starting in coordinate (5,11) for an AT (5,10) specification.

The following considerations apply to the placement of attribute bytes and fields:

Specifying the coordinates for the final column of a row places the first displayable character for a field in the first column of the next row.
Specifying the coordinates for the final column of the final row on a screen places the first displayable character for a field in the first column of the first row (1,1).
Specifying coordinates that cause a field to exceed the remaining length on a given row results in a field that is split at the end of the screen and wrapped around to either the next row or the top of the screen, depending on the row in which the coordinates were placed.

Screen coordinates are designated as follows:

ANYWHERE

Specifies that the field can appear anywhere on the screen. ANYWHERE is meaningful only with mapin operations for which the requesting program reads extraneous data. Extraneous data is data that is not associated with a field at a specific row/column location.

(Row-n,column-n)

Specifies the row and column coordinates for the attribute byte for the field:

Row-n identifies a horizontal position on the screen.
Column-n identifies a vertical position on the screen; the default column is 1.

The following considerations apply when positioning multiply-occurring fields:

Each occurrence of the field requires its own row-n,column-n specification; multiple row-n,column-n specifications can be made in one AT clause, if necessary.
If there are more row-n,column-n specifications than multiply-occurring fields specified in the OCCURS clause, the compiler input statement listing returns an error message.
AT specifications can occur in any order; they are assigned to corresponding OCCURS values in order of iteration.

ATTRIBUTES=NONE/(attributes-list)

Specifies the attributes for the field. Only one ATTRIBUTES clause can occur in a given MFLD statement. ATTRIBUTES specifications apply to all occurrences of the field. Valid specifications are as follows:

NONE removes all attribute specifications from the map and panel field occurrences being defined by the MFLD statement. The following runtime considerations apply when NONE is specified for a field:
- The field is displayed with the attributes defined for the preceding field if the preceding field is not delimited.
- The field is displayed with the default display attributes provided by the device if the preceding field is delimited or if there is no preceding field.
- The field is displayed beginning in the column position specified in the AT clause, since there is no attribute character for the field.
(Attributes-list) specifies a list of attribute that apply to the field.
Note: For more information about available attributes, see "Attributes List."

DELIMIT/NODELIMIT

Specifies whether a delimit character is placed after the final position of a data field:

DELIMIT IS SKIP/NOSKIP specifies that an internal delimit character is placed after the final position of the field, as determined by the external picture of the associated record element. The action of the cursor when it reaches the delimit character and the disposition of excess characters are determined by one of the following specifications:
- SKIP (default) specifies that the cursor is advanced automatically to the start of the next UNPROTECTED field when operator input reaches the delimit character. If there are no more UNPROTECTED fields on the map, the cursor is placed at the start of the current field. Characters typed after the internal delimit character is reached are placed in the field to which the cursor advances. SKIP is the default if DELIMIT is specified.
- NOSKIP specifies that the cursor remains at the delimit character when operator input reaches the end of the field. Subsequently typed input locks the keyboard until the operator presses the RESET key. The TAB key advances the cursor to the next UNPROTECTED field.
NODELIMIT specifies that no internal delimit character is assigned to the field. The operator is not informed when input reaches the end of the field, and can continue typing until the attribute byte of the next field is reached. On mapin, the external picture of the record element associated with the field determines the amount of operator input that is stored. Input that exceeds the length of the external picture is ignored; a CA ADS dialog or application program can include commands to inquire whether extraneous data has been input for a NODELIMIT field.

PAGING TYPE IS DETAIL ONLY/START/DETAIL END/FOOTER START/NULL

(pageable maps only). Specifies whether the field begins and/or ends the detail occurrence or an area on the pageable map:

DETAIL ONLY performs the following functions:
- Begins the detail area on the line that contains the attribute byte of the field being defined.
- Begins the detail occurrence on the line that contains the attribute byte of the field being defined.
- Ends the header area (if any) on the line immediately above the line that contains the attribute byte for the field assigned the DETAIL ONLY specification.
- Ends the detail occurrence for the map at the final character of the field assigned the DETAIL ONLY specification.
The field assigned the DETAIL ONLY specification must begin on a new line (that is, it cannot begin on a line that contains characters for a field in the header area).
DETAIL START performs the following functions:
- Begins the detail area on the line that contains the attribute byte of the field being defined.
- Begins the detail occurrence on the line that contains the attribute byte of the field being defined.
- Ends the header area (if any) on the line immediately above the line that contains the attribute byte for the field assigned the DETAIL START specification.
The field assigned the DETAIL START specification must begin on a new line (that is, it cannot begin on a line that contains characters for a field in the header area).
DETAIL END specifies that the detail occurrence for the map is to end at the final character position of the current field. The detail area for the map is not terminated by DETAIL END; FOOTER START (below) can be used to terminate the detail area.
FOOTER START performs the following functions:
- Begins the footer area on the line that contains the attribute for the field. The footer area ends at the end of the screen.
- Ends the detail area on the line immediately above the line that contains the attribute byte of the field assigned the FOOTER START specification.
The field assigned the FOOTER START specification must begin on a new line (that is, it cannot begin on a line that contains characters for a field in the DETAIL END field). If assigned, the FOOTER START specification must be made for a field following the field assigned the DETAIL END specification.
NULL (default) specifies that the field does not begin or end a detail or an area on the map. The NULL setting can be used to override a previous DETAIL START, DETAIL END, or FOOTER START specification for a field.

Note: For more information about the areas of pageable maps, see "Pageable Maps."

VALUE IS data-value/((occurrence-count) data-value)

Supplies string values to literal fields:

Data-value assigns a value to a singly-occurring literal field. The specified value must be enclosed in quotation marks.
((Occurrence-count) data-value) assigns a value to a literal field or assigns discrete values to multiple occurrences of a literal field:
- (Occurrence-count) identifies one or more field occurrences by order of iteration. Values are assigned to the literal fields specified in the AT clause by order of iteration of the row/column specifications rather than by their order of display on the mapped screen. For example, with a literal field that occurs four times, the specification VALUE IS ((2) 'ABC' (1) 'DEF' (1) 'GHI') assigns the value ABC to the first and second field occurrences, DEF to the third field occurrence, and GHI to the fourth field occurrence.
- Data-value specifies the value assigned to each occurrence or group of literal field occurrences. The supplied value must be enclosed in quotation marks.

A maximum of 256 characters can be specified for a literal field in data-value

CURSOR/NOCURSOR

Specifies the mapout location of the cursor at runtime:

CURSOR specifies that the cursor is located at the start of the indicated field when the map is mapped out.
NOCURSOR (default) specifies that the cursor is not located at the start of the indicated field when the map is mapped out.

If CURSOR is specified in more than one MFLD statement for a given map, the runtime cursor is positioned at the field for which CURSOR was last specified at compile time. If CURSOR is not specified for any field on the map, the default runtime cursor location is the first UNPROTECTED field on the screen, or at coordinate 1,1 if there are no UNPROTECTED fields.

LITERAL

Specifies that the field is a literal field. A literal field is given a string value in the VALUE IS clause. If LITERAL, MESSAGE LENGTH, PAGE LENGTH, RESPONSE LENGTH, or DFLD is not specified in the MFLD statement, LITERAL is the default.

MESSAGE LENGTH length

Specifies that the field is a message field. If included, length must be an integer greater than or equal to 1 and less than or equal to the total number of character positions on the smallest screen for which the map is intended. The default for length-n is 80.

PAGE LENGTH 4

Specifies that the field is a page field.

RESPONSE LENGTH length

CA ADS only. Specifies that the field is a response field. If included, length must be an integer in the range 1 through 32. The default is 8.

DFLD data-field-name (subscript) OF record-name/role-name

Specifies that the field is a data field and associates the field with the record element named by data-field-name:

Data-field-name specifies an element that is already defined to the data dictionary by means of the CA IDMS/DB schema compiler or the IDD DDDL compiler.
Subscript-n specifies the subscript of the record element if the element is multiply-occurring.
OF record-name/role-name names the record or role to which the associated element belongs:
- Record-name VERSION version-n specifies the name of a schema or work record that is already defined in the data dictionary and is specified in the USING RECORDS clause for the map. A record name for an element must be specified when the same data-field-name occurs in more than one record used by the map.
  VERSION version-n must be used to specify the version number of the record if record-name is not unique in the map.
- Role-name specifies the role name of a record. The role name can be previously defined for a record in the subschema used in the program or dialog, or the role name can be a unique name that is established at map definition in the ROLENAME clause of the MAP statement.

The length of a data field is not specified in the DFLD clause; the length is determined in one of the following ways:

The EXTERNAL PICTURE clause of the MFLD statement (described as follows) can determine the length of a data field, as follows:
- If EXTERNAL PICTURE explicitly specifies an external picture for the field, that external picture determines the length of the field.
- If EXTERNAL PICTURE specifies INTERNAL, an external picture is constructed from the internal picture specified for the element named by data-field-name, and that external picture determines the length of the field.
The external picture associated with the record element (if any) determines the length of the field if the MFLD statement does not specify an external picture.
The external picture derived from the internal picture specified for the field (if automatic editing is enabled for the map and field) determines the length of the field if the record element definition does not specify an external picture.
A data field can contain as many character positions as are available on the smallest screen for which the map is intended, minus one character position for the attribute byte for the field.

Remaining MFLD clauses supply automatic editing and error-handling information for the field being defined. For more information about the features enabled by the clauses listed, see the chapter "Automatic Editing and Error Handling." The following MFLD clauses apply only when DFLD is specified for the field:

Note: For more information about the features enabled by the clauses listed, see the chapter "Automatic Editing and Error Handling."

HELP

Specifies whether help will be implemented for the field.

SOUrce NONE/MODule module-name

The name of the IDD module that contains the help text for the field.

If module name is specified, you can optionally specify:

The version number
Whether the help is displayed on a full or half screen

REQUIRED/OPTIONAL

Indicates whether operator input is required in the field:

REQUIRED specifies that input is required. An input error occurs if the terminal operator does not enter data for the field.
OPTIONAL (default) specifies that input is optional.

REVERSE NUMERIC IS YES/NO

Specifies whether the contents of a numeric field are reversed on mapin and again on mapout:

YES specifies that data for the field is reversed on mapin, and again on mapout. REVERSE NUMERIC is used for numeric fields when hardware modifications cause input to be entered from right to left. YES is the default for new fields when REVERSE NUMERIC is specified in the SIGNON statement for the batch run.
NO specifies that data for the field is not reversed on mapin or on mapout. The NO specification is overridden when the developer specifies REVERSE NUMERIC in the SIGNON statement for the batch run.

UNDERSCORE when blank NO/YES

Indicates if the field should be underscored if it is blank. On mapin, trailing underscores are removed.

EXTERNAL PICTURE IS/NOEDIT

Indicates whether the field is processed by automatic editing and error-handling, and establishes an external picture for use in editing. The following options are available:

NOEDIT (default) disables automatic editing and error-handling for the field.
EXTERNAL PICTURE IS enables automatic editing for the field and specifies the external picture for the field during automatic editing, the action to be taken by automatic editing should the terminal operator erase the field, and/or the display format for NUMERIC fields that contain only zeros, as follows:
- Picture/INTERNAL specifies the external picture for the field.

Note: For information about external pictures, see External Pictures.

Picture specifies an actual external picture, such as XX/XX/XX or XXX-XX-XXXX.

INTERNAL (default) requests that the map use the external picture defined for the associated record element (or the picture constructed for the field).
ZEROED/RETAINED WHEN NULL specifies the action taken when automatic editing is enabled for a numeric field and the terminal operator erases the contents of the field (for example, by pressing the ERASE EOF key).
ZEROED (default) requests the field be filled with zeros of the appropriate data type when automatic editing is enabled for the given map and field and the operator erases the contents of the field.

RETAINED indicates that the data contained in the buffer should be retained when the operator erases the contents of the field.
DISPLAY/BLANK WHEN ZERO indicates the action taken when automatic editing is enabled for a numeric field that contains only zeros.
DISPLAY (default) requests that the zeros be displayed.

BLANK requests that blanks be displayed instead of zeros.

Note: For a group data field, the only valid external picture is an alphanumeric one. Note also that edit and code tables are not supported for group data fields.

EDIT TABLE IS table-name/NULL

Specifies the edit table used for the field if automatic editing is enabled for the field and map:

Table-name specifies the name of an existing stand-alone table used as the edit table for the field.
Note: For more information about the use of edit tables, see "Edit and Code Tables".

If editing is enabled elsewhere for the field and no edit table is named by using the EDIT TABLE IS clause, the default edit table is the built-in table (if any) defined in the associated record element. If no edit table is named by the EDIT TABLE IS clause or defined in the element definition, no edit table is used. The following clauses can be included in an EDIT TABLE IS specification when the edit table is named:
- VERSION version-n specifies the version of the edit table used. The default is 1.
- LINK/NOLINK specifies whether the edit table is linked as part of the map load module or is loaded dynamically at runtime:
  LINK (default) indicates that the named edit table is to be linked as part of the map load module. The LINK specification is particularly useful for tables that contain items that cannot be used readily by another record element.
  
  NOLINK indicates that the table is loaded dynamically at runtime. NOLINK is useful when the contents of a table change frequently.
- USAGE IS VALIDATE/INVALIDATE/
  DEFAULT indicates whether the edit table is a table of valid values or invalid values:
  VALIDATE specifies that the table contains valid values. An error occurs when the terminal operator enters a value that does not appear in the table.
  
  INVALIDATE specifies that the table contains invalid values. An error occurs when the terminal operator enters a value that appears in the table.
  
  DEFAULT (default) specifies that the VALID or INVALID specification given in the table definition should be used for the table.
NULL (default) specifies that no stand-alone edit table is used for the field at runtime. NULL does not suppress use of the built-in edit table for the field.

CODE TABLE IS table-name/NULL

Specifies the code table used for the field if automatic editing is enabled for the field and map:

Table-name specifies the name of an existing stand-alone code table used for the field if automatic editing is enabled for the field.
Note: For more information about the use of code tables, see "Edit and Code Tables".

If editing is enabled elsewhere for the field, and no code table is named by using the CODE TABLE IS clause, the default code table is the built-in code table (if any) defined in the associated record element. If no code table is named by the CODE TABLE IS clause or defined in the element definition, no edit table is used. The following clauses can be included in a CODE TABLE IS specification when a code table is named:
- VERSION version-n specifies the version of the code table used. The default is one.
- LINK/NOLINK specifies whether the code table is linked as part of the map load module or is loaded dynamically at run time:
  LINK (default) indicates that the named code table is to be linked as part of the map load module. LINK is useful for tables that contain items that cannot be used readily by another record element.
  
  NOLINK indicates that the table is loaded dynamically at runtime. NOLINK is useful when the contents of a table change frequently.
NULL (default) specifies that no stand-alone code table is used for the field at runtime. NULL does not suppress use of the built-in code table for the field.

ERROR MESSAGE message/message-id/NULL

Defines the error message returned on mapout if the field is in error. The message is displayed in the message field defined for the map. If the map has no message field, the message is not displayed and processing continues normally (with CA ADS, the message is displayed on the CA ADS default message screen). The developer can specify any one of the following options:

Message specifies the text of the message displayed if the field is in error. Message must be enclosed in quotation marks.
Message-id specifies the 6-digit message identifier of the data dictionary message displayed if the field is in error. The map compiler adds the prefix DC to this 6-digit identifier to construct the actual identifier of the data dictionary message.
NULL (default) specifies that the default error message is used if the field contains incorrect input. The default message has the following format:
```
ERROR AT row,column
```

MSG PREFIX IS message-prefix

Defines the two-character prefix to be used to locate the message in the dictionary of the message defined in the previous ERROR MESSAGE parameter when the field is found to be in error at runtime. The value defaults to the value specified in the MSG PREFIX parameter in the MAP statement.

FOR INPUT

Specifies functions performed for data on a mapin operation:

JUSTIFY LEFT/RIGHT

Specifies how operator input is to be aligned for transmission to program variable storage:

LEFT (default) specifies that input is left-justified.
RIGHT specifies that input is right-justified.

PAD NO/WITH literal

Specifies a pad character for an alphanumeric field in character or hexadecimal format:

NO (default) specifies that data is not padded.
WITH literal specifies the pad character for a field in character or hexadecimal format. Character literals are specified as C'c', where c denotes a character literal. Pad characters in hexadecimal format are specified as X'nn', where nn denotes a two-digit hexadecimal value. Hexadecimal format is recommended when specifying the blank character as the pad character for a field.

Pad characters are used to avoid unwanted data being stored for a field on mapin. For example, a data field containing the name JOHNSON is mapped out. The operator presses the ERASE EOF key to erase the field, types in SMITH, and presses Enter. The value mapped to variable storage depends on whether a pad character is defined for the field:

If no pad character is defined for the field, SMITHON is stored for the field. The operator would have to key blanks over ON to eliminate these characters from the data.
If a blank pad character is defined for the field, SMITH is stored for the field.

DATA YES/NO

Indicates whether the transmitted contents (if any) of the field are to be moved automatically into program variable storage on a mapin operation:

YES (default) specifies that the contents of the field are automatically moved into program variable storage if transmitted from the terminal. Data is transmitted from the terminal when the MDT is set on for the field before a mapin operation.
NO specifies that data contained in the field is not moved automatically into program variable storage, even if the MDT is set on.

UPPERcase YES/NO

Indicates if field should be displayed in uppercase.

EDIT IS edit-module-name WITH AUTOEDIT

Optionally specifies the name of an existing user-written edit module to process input after transmission on a mapin operation. The relationship between the user edit module and automatic editing is determined by the WITH AUTOEDIT clause as follows:

NO (default) specifies that automatic editing is not performed for the field; only the user-written edit module is used.
BEFORE specifies that automatic editing is performed immediately before the user edit module edits the input.
AFTER specifies that automatic editing is performed immediately after the user edit module edits the input.

User edit modules are discussed in "Automatic Editing and Error Handling".

FOR OUTPUT

Specifies functions to be performed for data prior to a mapout operation:

BACKSCAN YES/NO

Indicates whether trailing blanks are to be eliminated from the field prior to display:

YES specifies that the contents of the field are displayed without trailing blanks (if any). Old data may remain in the field after operator alterations if NEWPAGE is set to NO in either the CA ADS sysgen statement or the DML statement that issues the mapout.
NO (default) specifies that the contents of the field are displayed with trailing blanks (if any).

DATA YES/NO/ERASE/ATTRIBUTE

Indicates whether data in program variable storage is to be transmitted to the screen on a mapout operation:

YES (default) specifies that data is transmitted.
NO specifies that neither data nor the attribute byte are transmitted. Any data previously in the field continues to display.
ERASE specifies that data is not transmitted; the field on the screen is initialized to null or low values, depending on whether the field is numeric or alphanumeric.
ATTRIBUTE specifies that only the attribute byte for the field is transmitted; data in the record buffer is not sent to the terminal.

EDIT IS edit-module-name WITH AUTOEDIT

Optionally specifies the name of an existing user-written edit module to process data before display on a mapout operation. The relationship between the user edit module and automatic editing is determined by the WITH AUTOEDIT clause as described as follows:

NO (default) specifies that automatic editing is not performed; only the user-written edit module is used.
BEFORE specifies that automatic editing is performed immediately before the user edit module edits the field.
AFTER specifies that automatic editing is performed immediately after the user edit module edits the field.

User-written edit modules are discussed in the chapter "Automatic Editing and Error Handling."