1 - AT_END

  The AT END phrase specifies the action your program takes when the AT
  END condition occurs.

  Format -

   AT END stment

2 - AT_END-OF-PAGE

  The AT END-OF-PAGE phrase specifies the action your program takes
  when the AT END-OF-PAGE condition occurs.

  Format -

   AT END-OF-PAGE stment

3 - CORRESPONDING

  The CORRESPONDING option allows you to specify group items as
  operands in order to use their corresponding subordinate items in an
  operation.

4 - FROM

  Format 1 -

   record-name FROM identifier

  Format 2 -

   FROM { keeplist-name } ...

  Keeplist-name refers to a user-defined keeplist in the Sub-Schema
  Section.

  Record-name and identifier must not refer to the same storage area.

  After statement execution ends, the data in the area referenced by
  identifier is available to the program.  The data is not available in
  the area referenced by record-name, unless there is an applicable
  SAME clause.

5 - INTO

  The INTO phrase implicitly moves a current record from the record
  storage area into an identifier.

  Format -

   file-name INTO identifier

6 - INVALID_KEY

  The INVALID KEY phrase specifies the action your program takes when
  an invalid key condition is detected for the file being processed.

  Format -

   INVALID KEY stment

7 - NOT_AT_END

  The NOT AT END phrase specifies the action your program takes when
  the AT END condition does not occur.

  Format -

   NOT AT END stment

8 - NOT_AT_END-OF-PAGE

  The NOT AT END-OF-PAGE phrase specifies the action your program takes
  when the AT END-OF-PAGE condition does not occur.

  Format -

   NOT AT END-OF-PAGE stment

9 - NOT_INVALID_KEY

  The NOT INVALID KEY phrase specifies the action your program takes
  when an invalid key condition is not detected for the file being
  processed.

  Format -

   NOT INVALID KEY stment

10 - NOT ON ERROR database

  The database on error exception condition occurs when the Database
  Control System (DBCS) encounters any database exception condition for
  any Data Manipulation Language (DML) statement.

  The NOT ON ERROR phrase in a DML statement allows the selection of an
  imperative statement sequence when any database exception condition
  does not occur.

  Format -

   NOT ON ERROR stment

11 - NOT_ON_EXCEPTION

  The NOT ON EXCEPTION phrase allows execution of an imperative
  statement when an exception (or error) condition does not occur.

  Format -

   NOT ON EXCEPTION stment

12 - NOT_ON_OVERFLOW

  The NOT ON OVERFLOW phrase allows you to specify an action for your
  program to take when an overflow condition does not exist.

  Format -

   NOT ON OVERFLOW stment

13 - NOT_ON_SIZE_ERROR

  The NOT ON SIZE ERROR phrase allows you to specify an action for your
  program to take when a size error condition does not exist.

  Format -

   NOT ON SIZE ERROR stment

14 - ON ERROR database

  The database on error exception condition occurs when the Database
  Control System (DBCS) encounters any database exception condition for
  any Data Manipulation Language (DML) statement.

  The ON ERROR phrase in a DML statement allows the selection of an
  imperative statement sequence when any database exception condition
  occurs.

  Format -

   ON ERROR stment

15 - ON_EXCEPTION

  The ON EXCEPTION phrase allows execution of an imperative statement
  when an exception (or error) condition occurs.

  The ON EXCEPTION option of the CALL statement prevents control
  transfer of the CALL and triggers the execution of the imperative
  statement related to the CALL.

  The ON EXCEPTION option of the ACCEPT statement allows you to handle
  data entry errors when ACCEPTing into a numeric data field WITH
  CONVERSION.

  Format -

   ON EXCEPTION stment

16 - ON_OVERFLOW

  The ON OVERFLOW phrase allows you to specify an action for your
  program to take when an overflow condition exists.

  Format -

   ON OVERFLOW stment

17 - ON_SIZE_ERROR

  The ON SIZE ERROR phrase allows you to specify an action for your
  program to take when a size error condition exists.

  Format -

   ON SIZE ERROR stment

18 - RETAINING

  The RETAINING clause specifies which currency indicators are not
  updated during the execution of the CONNECT, FETCH, FIND, MODIFY,
  RECONNECT, and STORE statements.

  Format -

   [           [ {|   REALM                  |} ]          ]
   [ RETAINING [ {|   RECORD                 |} ] CURRENCY ]
   [           [ {| { SET [ set-name ] ... } |} ]          ]
   [           [ {| { { set-name } ...     } |} ]          ]

  set-name is a subschema set name.

19 - ROUNDED

  The rounding operation adds 1 to the absolute value of the low-order
  digit of the resultant identifier if the absolute value of the next
  least significant (lower-valued) digit of the intermediate data item
  is greater than or equal to 5.

  If you do not use the ROUNDED phrase, any excess low-order digits in
  the arithmetic result are truncated when the result is moved to the
  resultant identifier(s).