Interface exit components

The security system interface exit consists of the following components. The component groupings are for the two high-level language exit points and the low-level language (assembler) exit point. All of the components are provided in source form.

Components of the high-level language interfaces

There are two high level language interfaces. Both, either, or neither of them can be activated based on the settings in the ars.ini file. The following sample files are provided for each interface:
User Authentication
The executable file is the arsusec DLL, which is used for checking user security.
  • ARSUSEC (c sample)
  • ARSUSECH (c header file)
or
  • ARSUSECC (sample COBOL program equivalent to the ARSUSEC C sample)
  • ARSUSECB (COBOL copybook equivalent to the C ARSUSECH header file)
  • ARSUSEJJ (sample JCL to compile and link the ARSUSECC sample)
Resource Authorization
The executable file is the arsuperm DLL, which is used for checking user permissions.
  • ARSUPERM (c sample)
  • ARSUSECH (c header file)
or
  • ARSUPERC (sample COBOL program equivalent to the ARSUPERM C sample)
  • ARSUPERJ (sample JCL to compile and link the ARSUPERC sample)
The sample modules ARSUSEC and ARSUPERM provide the high level interface from the Content Manager OnDemand system to the external exit routine driver, ARSUSECX.

Components of the low-level language interface

There is a single low level assembler language interface. It is activated based on the settings in the ars.ini file.
  • Assembler Interface 1.ARSUSECX (Assembler external exit routine driver)
  • ARSUSECZ (Assembler associated exit routine)
  • ARSUSECA (Assembler header file)
  • ARSUSECJ (JCL stream used to assemble and bind ARSUSECX and ARSUSECZ)

Module ARSUSECX interfaces with the MVS™ Dynamic Exit Facility to route control to a set of exit routines. Module ARSUSECZ is an example of such an exit routine.

ARSUSECA (assembler), ARSUSECH (C), and ARSUSECB (COBOL) provide mappings of the data structures presented to exit routines associated with the exit point defined by ARSUSECX. (That is, the data structure presented as an input parameter to ARSUSECZ.)