Control Statements › EXCEPTION Statement › Considerations

Considerations

• EXCEPTION, OUTPUT, LIST(BOTH), PLOT, and RANK statements are mutually exclusive in a run. Also, if the input file is unusually long, you may want to suppress the regular report by checking that there is no LIST statement before the EXCEPTION statement. Summary report facilities are not available in an exception report run.
• If there is a LIST statement before the last EXCEPTION statement(s), a detail report is generated in the first pass.

  If there is a LIST statement after the last EXCEPTION statement(s), it is used for the exception reports; otherwise, the LIST statement preceding the EXCEPTION statements is used.

• If you request a detail report prior to the exception report and want it sequenced, you must supply a SORT statement prior to the EXCEPTION statement.

  If you want the exception report to be sequenced, you must supply a SORT statement after the EXCEPTION statement.

  Should you require both a detail and an exception report and want both reports sequenced, you must include a SORT statement both before and after the EXCEPTION statement (that is, you need two SORT statements).

• Exception reports are created using a two-pass process. The fields available for use in the second pass are:
  • CA JARS Wizard keywords
  • All input glossary fields
  • SORTKEY
  • Fields computed in the SECOND pass

  When applying the exception feature, you must recompute the items on the LIST statement for exception reports that are not derived directly from the input record. You must recompute these items as part of the second pass. All statements following an EXCEPTION statement are applied to the second pass.