• The VALUE clause is required in a condition-name entry, and must be the only clause in the entry. Each condition-name entry is associated with a preceding conditional variable. Thus, every level-88 entry must always be preceded either by the entry for the conditional variable, or by another level-88 entry when several condition-names apply to one conditional variable. Each such level-88 entry implicitly has the PICTURE characteristics of the conditional variable.

• The key words THROUGH and THRU are equivalent.
  The condition-name entries associated with a particular conditional variable must immediately follow the conditional variable entry. The conditional variable can be any elementary data description entry except another condition-name, a RENAMES clause (level-66 item), or an item with USAGE IS INDEX.
  
  X The conditional variable cannot be an item with USAGE IS POINTER,
  X USAGE IS PROCEDURE-POINTER, or USAGE IS OBJECT REFERENCE.
  A condition-name can be associated with a group item data description entry. In this case:
  • The condition-name value must be specified as a nonnumeric literal or figurative constant.

  • The size of the condition-name value must not exceed the sum of the sizes of all the elementary items within the group.

  • No element within the group can contain a JUSTIFIED or SYNCHRONIZED clause.

  • No USAGE other than DISPLAY can be specified within the group.
    
    X USAGE other than USAGE IS DISPLAY can be specified within the
    X group.

  Condition-names can be specified both at the group level and at subordinate levels within the group.
  The relation test implied by the definition of a condition-name at the group level is performed in accordance with the rules for comparison of nonnumeric operands, regardless of the nature of elementary items within the group.
  
  X The VALUE clause is allowed for internal floating-point data items.
  
  X The VALUE clause is allowed for DBCS data items. Relation tests for
  X DBCS data items are performed according to the rules for comparison of
  X DBCS items. These rules can be found in "Comparison of DBCS Operands"
  X in topic 6.1.6.5.5.
  A space, a separator comma, or a separator semicolon, must separate successive operands.
  Each entry must end with a separator period.

• The type of literal in a condition-name entry must be consistent with the data type of its conditional variable. In the following example:
  • CITY-COUNTY-INFO, COUNTY-NO, and CITY are conditional variables.
    The PICTURE associated with COUNTY-NO limits the condition-name value to a 2-digit numeric literal.
    The PICTURE associated with CITY limits the condition-name value to a 3-character nonnumeric literal.

  • The associated condition-names are level-88 entries.
    Any values for the condition-names associated with CITY-COUNTY-INFO cannot exceed 5 characters.
    Because this is a group item, the literal must be nonnumeric.

  
           05  CITY-COUNTY-INFO.
               88  BRONX                    VALUE "03NYC".
               88  BROOKLYN                 VALUE "24NYC".
               88  MANHATTAN                VALUE "31NYC".
               88  QUEENS                   VALUE "41NYC".
               88  STATEN-ISLAND            VALUE "43NYC".
             10  COUNTY-NO                  PICTURE 99.
                 88  DUTCHESS               VALUE 14.
                 88  KINGS                  VALUE 24.
                 88  NEW-YORK               VALUE 31.
                 88  RICHMOND               VALUE 43.
             10  CITY                       PICTURE X(3).
                 88  BUFFALO                VALUE "BUF".
                 88  NEW-YORK-CITY          VALUE "NYC".
                 88  POUGHKEEPSIE           VALUE "POK".
           05  POPULATION...
  
  
  

• X If the item is a windowed date field, the following restrictions
  X apply:
  • X For alphanumeric conditional variables:
    • X Both literal-1 and literal-2 (if specified) must be
      X alphanumeric literals of the same length as the conditional
      X variable.

    • X The literals must not be specified as figurative constants.

    • X If literal-2 is specified, then both literals must contain
      X only decimal digits.

  • X If the YEARWINDOW compiler option is specified as a negative
    X integer, then literal-2 must not be specified.

  • X If literal-2 is specified, then literal-1 must be less than
    X literal-2 after applying the century window specified by the
    X YEARWINDOW compiler option. That is, the expanded date value of
    X literal-1 must be less than the expanded date value of literal-2.

  
  X For more information on using condition-names with windowed date
  X fields, see "Condition-Name Conditions and Windowed Date Field
  X Comparisons" in topic 6.1.6.3.1.

IBM Library Server Copyright 1989, 2005 IBM Corporation. All rights reserved.

Adobe, the Adobe logo, Acrobat, the Acrobat logo, and Acrobat Reader are registered trademarks of Adobe Systems incorporated.