Is APF Authorization required for the CA IPC Loadlib?
Article ID: 102416
CA Datacom - DBCA DatacomCA Datacom - ADCA Datacom - ServerCA CISCA Common Services for z/OSCA 90s ServicesCA Database Management Solutions for DB2 for z/OSCA Common Product Services ComponentCA Common ServicesCA Datacom/ADCA ecoMeter Server Component FOCCA Easytrieve Report Generator for Common ServicesCA Infocai MaintenanceCA IPCUnicenter CA-JCLCheck Common ComponentCA Mainframe VM Product ManagerCA Chorus Software ManagerCA On Demand PortalCA Service Desk Manager - Unified Self ServiceCA PAM Client for Linux for zSeriesCA Mainframe Connector for Linux on System zCA Graphical Management InterfaceCA Web Administrator for Top SecretCA CA- Xpertware
There is a reference in the CA Datacom documentation that says "The CA IPC load library should already be APF authorized." This authorization is not found in any of the CA IPC documentation, and there are no jobs in the CA IPC installation like in the CA Datacom/DB installation to perform this authorization. Should the CA IPC load library be APF authorized or not?
Release: DATABB00200-14.0-Datacom/AD Component:
The primary concern for having APF authorization of the CA IPC loadlib is with the MUF execution JCL (PGM=DBMUFPR). Since the CA Datacom/DB and CA Datacom/AD loadlibs need to be APF authorized, any other loadlibs used with them for authorized functions also need APF authorization.
Consequently, the CA IPC loadlib does not need to be APF authorized, and because it is not authorized, the CA IPC loadlib should be removed from the DBMUFPR STEPLIB in the MUF startup proc or JCL.
Note, too, that this CA IPC loadlib does not need to be part of any DBUTLTY jobs, but it is needed for Datadictionary batch jobs (DDUPDATE, DDUTILTY and others), but these batch jobs do not require authorized libraries.
As always, please contact CA Technologies support for CA Datacom if you have further questions.