The ISPF interface delivered with the product consists of REXX procedures and ISPF skeletons.
The following describes the procedures and ISPF skeletons that represent Exits and that can or should be adapted to the respective environment.
| Exit | Type | Description |
|---|---|---|
| TAUTOXA1 | REXX | Exit for the dynamic allocation of the ISPF environment.
This exit procedure is always called directly before a modeled ISPF tool is called. It receives one parameter, which is assigned to the modeled application (see Variable references). The exit is typically used to carry out dynamic allocations depending on the modeled input parameter, e.g. in order to be able to test modified applications. |
| TAUTOXA2 | REXX | Exit for the allocation of (temporary) files.
The allocation of temporary MVS files takes place in this exit. |
| TAUTOXA3 | REXX | Exit which runs before ISPF is shut down. The exit is meant to do finally processing as long as ISPF is active. |
| TAUTOXA4 | REXX | Exit which is called when a user connects to the remote server from the REXX TAULAPPL when the server is IBM RSED, or from the REXX TAUZCAPP when the server is the Micro Focus MFA Server. The exit is intended to gather login information, for example for floating licence checking. |
| TAUTOXCC | REXX | Exit for the integration of the COBOL compiler e.g. for remote syntax check.
This exit is used only in context with add-ons for the support of SCM products, in order to support remote syntax check with Error Feedback. For these purposes, the exit can also be integrated into home-grown tool attachments as a REXX subroutine. |
| TAUTOXCP | REXX | Exit for the integration of the PL/I compiler for remote syntax check.
This exit is used only in connection with add-ons for the support of SCM products, in order to support remote syntax check with Error Feedback. For these purposes, the exit can also be integrated into home-grown tool attachments as a REXX subroutine. |
| TAUTOXCA | REXX | Exit for the integration of ASSEMBLER for remote syntax check.
This exit is used only in connection with add-ons for the support of SCM products, in order to support remote syntax check with Error Feedback. For these purposes, the exit can also be integrated into home-grown tool attachments as a REXX subroutine. |
| TAUTOXC3 | REXX | Exit for the integration of C compile for remote syntax check.
This exit is used only in connection with add-ons for the support of SCM products, in order to support remote syntax check with Error Feedback. For these purposes, the exit can also be integrated into home-grown tool attachments as a REXX subroutine. |
| TAUTOXIS | Skeleton | This skeleton must be adapted for the use of the batch interface in order to build up a valid ISPF environment in batch, under which a modeled ISPF batch tool can be started (only relevant for ISPF command tool modeled using the attribute Model Job. |
| TAUTOXJC | Skeleton | This skeleton must be adapted for the use of the batch interface, in order to support a default job card. |
The remote syntax check exits TAUTOXCA, TAUTOXCC, TAUTOXCP and TAUTOXC3 use the data set allocation exit TAUTOXA2 to allocate the XML error feedback data set. The XML error feedback data set is an MVS partitioned organized data set where the remote syntax check exit writes the XML error feedback of the syntax check to a member named the same as the source member of the syntax check.
The client will always display the errors listed in all XML members which are found in this data set.
Therefore this data set should be cleared at the beginning of each syntax check action.