Is APF Authorization required for the CA IPC Loadlib?


Article ID: 102416


Updated On:


CA Datacom CA DATACOM - AD CA CIS CA Common Services for z/OS CA 90s Services CA Database Management Solutions for DB2 for z/OS CA Common Product Services Component CA Common Services CA Datacom/AD CA ecoMeter Server Component FOC CA Easytrieve Report Generator for Common Services CA Infocai Maintenance CA IPC Unicenter CA-JCLCheck Common Component CA Mainframe VM Product Manager CA Chorus Software Manager CA On Demand Portal CA Service Desk Manager - Unified Self Service CA PAM Client for Linux for zSeries CA Mainframe Connector for Linux on System z CA Graphical Management Interface CA Web Administrator for Top Secret CA 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


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. 

Additional Information

As always, please contact CA Technologies support for CA Datacom if you have further questions.