Previous Topic: Combining the Interface With the CMDEXIT ModuleNext Topic: Interfacing With the DSAEXIT Module


Combining the Interface With the SUBEXIT Module

The CA Top Secret submit interface, SUBEXIT, is called to perform job submit validation to determine whether the ACID of the signed on user is authorized to submit the ACID associated with a particular job. The user‑written code is a front‑end to the CA Top Secret‑supplied code. The name of the CSECT is your choice, and the code must be reentrant.

To incorporate the interface, place the following instructions in your SUBEXIT module at the required locations:

In CA‑Roscoe UXDSECT, there are four fullwords (UXWKAREA) reserved for installation use. The CA Top Secret CSECT, TSSRXSUB, uses the first fullword. Therefore, sites linking in their own SUBEXIT with the CA Top Secret CSECT must not use the first fullword. The second through fourth fullwords are available for site use.

The CA Top Secret SUBEXIT supports checking records that replace the record passed to the user‑written SUBEXIT (entry code 4, exit code 8). If UXSUBRCO is not a zero on entry to the CA Top Secret SUBEXIT, all replacement records are checked since CA Top Secret assumes you are trying to replace records. It is, therefore, advisable to clear this field after use.

Sample source code that can be used with your SUBEXIT can also be found on the distribution tape in the file named TSSROSCO of the member SAMPSUB.

The JCL to link‑edit user‑written code with CA Top Secret‑supplied code into a load module can be found on the distribution tape in the file named TSSROSCO of the member INSTALL2.