Front End Programming Interface exits XSZARQ and XSZBRQ
If you have installed the Front End Programming Interface (FEPI), you can use global user exits XSZARQ and XSZBRQ before and after FEPI commands.
- XSZBRQ
- Invoked before a FEPI command is executed (but after the syntax of the command has been validated, and therefore after EDF processing).
- XSZARQ
- Invoked immediately after a FEPI command has completed (before EDF processing).
Note that both the FEPI application programming and system programming commands cause XSZBRQ and XSZARQ to be invoked, but the latter do not provide the exit programs with any meaningful information.
Usage of the exits
You cannot use exit programming interface (XPI) calls or EXEC CICS commands in
programs invoked from these exits. The exits allow you to monitor the FEPI commands and data being
processed; you can inhibit commands, and modify specific command options. You could use them for:
- Monitoring the issue of FEPI commands
- Workload routing
- External security on application programming commands.
Using XMEOUT to control message output
You can use the XMEOUT global user exit, in the CICS® message domain, to suppress or reroute FEPI messages. Note, however, that error conditions that generate a message also generate a transient data queue record. It is more efficient to handle such events using a monitoring program, through the TD queue, than by duplicating a message and then acting on it.