APPL
The APPLID of the CICS region on which the user is signing on. Which APPLID
is passed depends on what is specified as system initialization parameters.
INSTLN
A pointer to a vector of CICS-related information, which you can map using the
DFHXSUXP mapping macro. This pointer is valid only if ESMEXITS=INSTLN is
specified as a system initialization parameter for the CICS region.
The installation data referenced by the INSTLN parameter includes a pointer,
UXPCOMM, to a two-word communications area that can be used to pass
information between the two phases of the signon verification process—between
the early verification routine initiated by ENVIR=VERIFY, and the normal verification
routine initiated by ENVIR=CREATE.
CICS maintains a separate communications area for each task, in CICS-key
storage.
Writing an early verification routine
An early verification routine, written for the ENVIR=VERIFY option, receives control
from SAF in the usual way from the external security manager whose entry point is
addressed by field SAFVRACR in the SAF vector table. It receives control in the
same state as its caller, as follows:
v Problem-program state
v Task mode (usually the CICS quasi-reentrant TCB)
v PSW storage key 8
v 31-bit addressing mode
v Primary address translation mode.
Register 13 points to a standard 18-word save area. Register 1 points to a 2-word
parameter list, where:
v The first word is the address of the SAF parameter list for the VERIFY function.
v The second word is the address of a 152-byte work area.
Using CICS API commands in an early verification routine
An early verification routine can use CICS application programming interface (API)
commands, provided it obeys the following interface rules:
v The routine must be written in assembler.
v Entry to the routine must be via the DFHEIENT macro, which saves the caller’s
registers and establishes a CICS early verification API environment.
v Exit from the routine must be via the DFHEIRET macro, which releases the CICS
early verification API environment and restores the caller’s registers.
v The routine
must
be link-edited with the special security domain API stub,
DFHXSEAI,
instead of
the normal CICS API stub, DFHEAI0. The CICS early
verification stub causes linkage to a special interface routine that is aware of the
SAF interface linkage requirements, and saves the current CICS command
environment. In addition, the standard EXEC interface stub DFHEAI should also
be included, immediately before the early verification routine, with an ORDER
statement:
early verification processing
730
CICS TS for OS/390: CICS Customization Guide