|
|
|
CAIENF must run as an APF task because z/OS security restrictions won't allow an APF-authorized task to invoke an unauthorized task. Users have the choice of running an external MUF as APF-authorized or non-authorized, but IMUF must run APF-authorized. When the MUF is running in its own address space, it is under no CAIENF-imposed APF restrictions. It is only in CAIENF IMUF mode that a MUF requires APF authorization.
The MUF load libraries (CAAXLOAD and CUSLIB) that participate in IMUF operation must be APF-authorized because they will now be commingled through JOBLIB/STEPLIB or LNKLST with CAIENF APF-authorized libraries.
Note: The CA Datacom/AD auxiliary data sets (CXX, FXX, LXX, PXX, and RXX) do not require APF authorization.
Running the IMUF APF-authorized should not be an issue since it is strongly recommended that MUFs always be APF-authorized to maximize CA Datacom/AD's performance enhancement capabilities, and to insure that the full range of CA Datacom/AD's features are available.
If the IMUF statement is omitted from ENFPARMS, CAIENF will start up in standard mode of operation where it expects (and requires) an external MUF address space to be already started and prepared to accept CAIENF database requests.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |