Designing the Procedure Interaction › Exit States › Components of an Exit State

Components of an Exit State

Each exit state definition includes the components shown next:

• Name—The name appears as the subject of the EXIT STATE IS action.
  For example, an Exit State customer not found may be set if a particular customer does not exist on the database. In that case, the exit state is action in the action diagram would read:

  EXIT STATE IS CUSTOMER_NOT_FOUND
  

• Message—A message appears in the system message field if its associated exit state value is set when the procedure concludes and the exit state value does not trigger a flow or an abnormal termination.
  Messages are displayed according to the message type (informational, warning or error). In a client procedure that contains a display, messages are displayed in an appropriate dialog box.

  For example, the CUSTOMER_NOT_FOUND Exit State may have an associated message: Requested customer not on the database. If CUSTOMER_NOT_ FOUND is set in the WHEN NOT FOUND condition of a READ statement, the message Requested customer not on the database appears in the system message field of a screen.

• Termination Action—A termination action indicates the type of processing that is performed at run time when the associated exit state value is detected.

  These are the possible termination actions:

  • Normal-the exit state message will be displayed or a flow will take place.
  • Rollback-all database updates (the results of CREATE, UPDATE, and DELETE actions) performed by the procedure since the previous checkpoint will be backed out.
  • Abort-the procedure will abnormally terminate and will roll back all database updates.