Automatic Editing and Error Handling › Automatic Editing Criteria › Edit and Code Tables › Code Table Values

Code Table Values

Code table values specify encoded and decoded values:

• Encoded values specify data that can be stored in program variable storage. The data type and length of encoded values must be compatible with the internal format for the field with which the code table is associated. The internal format for a field is determined by the internal picture defined for the associated record element.

  For example, the following sample encoded values are valid in terms of their corresponding internal pictures:

• Decoded values specify data that can be displayed on a terminal screen. The data type and length of decoded values must be valid in terms of the external picture for the field with which the code table is associated. Insertion characters are not included as decoded values in code tables.

  For example, the following sample decoded values are valid in terms of their corresponding external pictures:

On mapin, the edit table (if any) is invoked before the code table (if any) for a field.

DDDL Compiler Options

DDDL compiler conventions apply when specifying values for edit and code tables:

• Delimit words or clauses by using one of the following delimiter characters:
  • Blank
  • Comma
  • Period
  • Semicolon
  • Colon
  • Apostrophe
  • Parenthesis
  • Quotation mark
• Embed one or more delimiter characters by enclosing the value that contains delimiter characters in a pair of site-standard quote characters. The single quote (') is the default. For example, the value OFFICE SERVICES in the following sample code table contains an embedded blank character:

  01          SHIPPING
  02         PERSONNEL
  03        ACCOUNTING
  04         MARKETING
  05  'OFFICE SERVICES'
  

  Single quotes around the value OFFICE SERVICES indicate that the space character between the two words in the value is part of the value rather than a delimiter between two values.

• Embed the site-standard quote character in a value by coding the quote character twice. For example, the value USER'S SITE in the following sample code table includes the default quote character ('):

  50        DENVER
  60        'BOSTON RGNL OFFICE'
  70        'CHICAGO RGNL OFFICE'
  85        'USER''S SITE
  

Note: For more information about DDDL compiler conventionsand specifying values for tables, see the CA IDMS IDD DDDL Reference Guide.

Special Values

The following special values can be included in code tables to facilitate use of the tables at runtime:

• The NOT FOUND keyword can be included in a code table to define a catchall for a decoded or encoded value:
  • As an encoded value, NOT FOUND ensures that an unanticipated stored value does not cause an abend on mapout. The decoded value that corresponds to NOT FOUND is displayed for unanticipated input.
  • As a decoded value, NOT FOUND ensures that unanticipated input does not cause an input error when evaluated by the code table. The encoded value that corresponds to NOT FOUND is stored for unanticipated data.

  NOT FOUND must not be enclosed in quotation marks when used as a keyword. For example, the following sample code table for a DEPARTMENT field includes NOT FOUND as an encoded and a decoded value:

  01           SHIPPING
  02           PERSONNEL
  03           ACCOUNTING
  04           MARKETING
  05           'OFFICE SERVICES'
  00           NOT FOUND
  NOT FOUND    MISSING
  

  The value 00 is stored for the field when an operator supplies a value that is not included as a decoded value in this sample table. The word MISSING is displayed when a value other than 01, 02, 03, 04, 05, or 00 is stored for the field.

  Note: For more detailed information about the NOT FOUND keyword, see the appendix “Generating Edit and Code Tables".

• The null value, (''), two consecutive quotation marks, should be included as a decoded value in a code table in the following cases:
  • The numeric data field is to be filled with zeros when automatic editing is enabled and the operator presses the ERASE EOF key, as specified by either of the following options:
    • The Zero when null option on the Map Read/Write Options screen
    • The ZEROED WHEN NULL option of the batch compiler MFLD statement
  • The alphanumeric data field is defined without a pad character.

  The following sample code table for a DEPARTMENT field included the null value as a decoded value:

     00             ''
     01             SHIPPING
     02             PERSONNEL
     03             ACCOUNTING
     04             MARKETING
     05             'OFFICE SERVICES'
  

  The decoded value 00 is stored for this example when the operator presses ERASE EOF at the beginning of the associated alphanumeric map field and submits a null value for the field.