ACSUUEX2 is a user-written routine that normally passes the data on to the target system; it can, however, also bypass the target system and invoke ACSUUEX1, the write-intercept exit, in order to produce a response to the user's input. The routine ACSUUEX2 can also be used to initiate commands to the host operating system, for example, CMS/CP commands.
This document covers the following topics:
To create a ACSUUEX2 routine, the following steps are required:
- Step 1
Code the ACSUUEX2 routine entry of ACSEXITS (A.ACSEXITS for z/VSE, or ACSEXITS ASSEMBLE for CMS).
- Step 2
Assemble and link ACSEXITS (A.ACSEXITS for z/VSE) into the ACCESS load library (relo library for z/VSE). For z/OS and z/VSE, have the ACCESS source library referred to during assemblies. Or for CMS only, assemble ACSEXITS with the ACCESS macro library referenced.
- Step 3
Link edit ACSEXITS (A.ACSEXITS for z/VSE) to the ACCESS driver for the host Adabas TPF, CICS, or TSO system. Member JCLLINKA (A.JCLLINKA for z/VSE) in the ACCESS source library contains the link edit JCL for all TP monitors supported. Or for CMS only, execute the EXEC GENACS.
Members CCACSWK and CCACSPFX in the distributed source library are DSECTS referred to in the main ACCESS routine. These areas are addressable in the ACSUUEX2 exit. A skeleton entry is provided in member ACSEXITS (A.ACSEXITS for z/VSE) of the ACCESS source library.
The following table summarizes the ACSUUEX2 linkage conventions.
Feature | Convention | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Attributes | None required. | ||||||||||||||
Size | Restricted to the ACS driver region. | ||||||||||||||
Registers at Entry |
|
||||||||||||||
Registers at return | All registers must be restored. | ||||||||||||||
Return Codes |
|
||||||||||||||
Considerations | Must be assembled and link edited with the ACS driver. |