Technical Considerations › CA Auditor as a Standard ISPF/PDF Application › LIBDEF Considerations

LIBDEF Considerations

Some sites use the ISPF LIBDEF facility when integrating products into their panel structures. This can minimize file allocations to those required by the executing applications.

You can use the LIBDEF facility to allocate these data sets to the ISPPLIB and ISPMLIB library types respectively.

CA Auditor provides a sample REXX EXEC called EXAMLIBD that demonstrates how LIBDEF services can be used with CA Auditor.

There are two flavors of the LIBDEF service: the DATASET format, and the LIBRARY format.

Additionally, the CA Auditor load library, CAI.EXAMINE.CAILOAD, cannot be specified using the LIBDEF service. This restriction exists because CA Auditor calls its modules through low-level SVCs below the ISPF layer. You must make this data set available for use using one of the following:

• Inclusion in the TSO session’s ISPLLIB concatenation.

  Note: You cannot use the LIBDEF service to allocate the CAI.PRODHLQ.CAJ0LOAD data set to the ISPLLIB library type. Attempts to do so will result in S806 abends upon invoking CA Auditor.

• Inclusion in the TSO LOGON procedure’s STEPLIB concatenation.
• Inclusion in the system LPA.
• Inclusion in the system linklist.

If you use the batch CA Auditor facilities, please review the restrictions and notes found in the Technical Reference Guide.