Troubleshooting problems with APF-authorization

If you expect File Manager to be running APF-authorized in batch mode, and it does not appear to be doing so, you can check this by submitting a File Manager batch job with the control statement: 
$$FILEM VER

If the VER function indicates that File Manager is not APF-authorized, it means that FMN.SFMNMOD1 is not APF-authorized. Check that IEAAPFxx is set up correctly and selected in IEASYSxx. You will need to re-IPL to activate IEAAPFxx. Alternatively, you can use PROGxx (if it is available on your system).

If a JOBLIB or STEPLIB statement is used to specify the File Manager load library, ensure that the File Manager load library is not concatenated with a non APF-authorized library. If a library concatenation includes a non-authorized library, (for example, you have not authorized your COBOL compiler library), then no library in that concatenation will be authorized.

If you start File Manager from an ISPF selection panel, the VER command will always show that File Manager is not APF-authorized, as File Manager cannot run APF-authorized under ISPF. File Manager functions that require APF-authorization are not supported under ISPF.

If you plan to use SMF for audit logging you must ensure that the module FMNSMF is APF-authorized. You also need to provide an SMF number, either in the appropriate option's module or parmlib member. See Customizing File Manager to write audit records to SMF.

The current File Manager function is terminated when auditing to SMF fails.

Message Unable to link to FMNSMF. TSOLNK RC=20 (Dec) REASON CODE=56 (Dec) is diagnostic of an APF authorization failure. The most common causes are:

  • The library containing FMNSMF is not APF authorized.
  • The DDNAME to which the library containing FMNSMF is allocated includes other libraries and at least one of those libraries is not APF-authorized.