The support is based on two components:

• IOADDI - A short-running job (the procedure found in the IOA PROCLIB library) you execute prior to any CONNECT DIRECT‑IOADDC interface request. This job 'registers' the IOA installation by saving installation information in a persistent system-wide control block. Among other fields, this control block contains relevant fields from the IOACPRM and CMMPLEX IOA PARM members referenced by the DAPARM DD statement.

  This job must be run:

  • with different JCL statements (in the DAPARM DD statement) for every IOA installation on every system that runs CONNECT DIRECT and IOADDC.
  • only once.
  • prior to the first CONNECT DIRECT‑IOADDC request.

whenever there is any change to the IOACPRM and CMMPLEX IOA PARM members.

• IOADDC - A routine linking a CONNECT DIRECT address space to an IOA installation. The routine receives an input trigger and the IOA installation QNAME. The QNAME is set by the user and taken from the QNAME parameter in the IOAPARM IOA PARM member. Depending on the settings in the IOACPRM and CMMPLEX IOA PARM members referenced by the DAPARM DD statement of the relevant run of the IOADDI job, IOADDC determines whether the input trigger is passed to the IOA installation (the IOADDR module) directly or via the MVS system logger interface.

  This routine accesses the control block built by IOADDI. If the user-specified QNAME is not found in the system-wide control block or the control block is not found, the request is aborted with a clear error message. If no QNAME is present in the request, module IOADDC will function as it did previously, that is, IOADDC sends the input trigger to the IOA installation (IOADDR module) based on the relevant fields from the IOACPRM and CMMPLEX IOA PARM members referenced by the DAPARM DD statement allocated to the IOADDC caller.