Special event handling

In addition to signon and signoff, you must consider what special event handling is required and whether it should be handled by central functions or by applications individually.

The special event handling you must consider are as follows:
  • The receipt of unsolicited data
  • Unexpected events
  • Beginning a session
  • Ending a conversation or session
  • Shutdown of the front-end CICS system.

If some sort of enforcement is required, or you want central provision for convenience, commonality, or the upholding of conventions and standards, you must supply a set of standard handlers. Otherwise, the application programs must handle each event. If you need special back-end processing when CICS shuts down, you need an end-session handler.

Unexpected events (including errors in setup) are reported to a transient data (TD) queue, so that a monitoring transaction can be triggered to handle them; they also send a message to the FEPI message log CSZL. You must decide how to handle these events, and which queues to use.

For more detailed information about the design and structure of applications, including information about using the various event handlers, see FEPI application design.

If you want central control over the range of FEPI commands that applications are permitted to issue, you can use the XSZBRQ global user exit, which is described in Front End Programming Interface exits.



dfhp7c0022.html | Timestamp icon Last updated: Sunday, 4 June 2017