ELIPS User Exits

ELIPS exits are site-defined and written routines that get control at certain points in ELIPS processing. The exit can validate and modify certain information and tells ELIPS to discontinue processing. The exit routines to use are defined during installation using the EXIT parameter when assembling the ELIPSGEN installation macro.
cl
ELIPS exits are site-defined and written routines that get control at certain points in ELIPS processing. The exit can validate and modify certain information and tells ELIPS to discontinue processing. The exit routines to use are defined during installation using the EXIT parameter when assembling the ELIPSGEN installation macro.
ELIPS exits are ISPF applications that use ISPF variable services to obtain and, when appropriate, update information. These exits can be CLISTs or programs. Programs can be TSO command processors, load modules, or linked to ELIPS for security purposes.
When ELIPS transfers control to an exit, all information is passed in ISPF variables in the shared variable pool. Since all exits operate in a different function pool from that of ELIPS, the exit must VGET the variables to its own function pool before they are available. For program type exits, VCOPY services must VDEFINE the variables or move them to useable storage.
Program exits must use standard IBM linkage conventions. No parameters are passed to exits in linkage. Program exits that are command processors or CLIST exits are executed using the ISPF SELECT CMD service. Program exits that are load modules are invoked using the SELECT PGM service. Linked exits are invoked using standard call linkage.
In some cases, information can be passed back to ELIPS. The variables for this are documented below. Any modified variables must be VPUT back into the shared variable pool to make the new value available to ELIPS.
Exits that are linked with ELIPS must be reentrant and coded in Assembler Language.