Unprotected functions and profile names for protected functions

File Manager unprotected functions, File Manager functions protected by FILEM.OTHER.ALL, and File Manager function to profile name cross-reference, show File Manager functions with their descriptions and (where applicable) the equivalent File Manager panel you can use under ISPF.

File Manager unprotected functions lists the functions that cannot be protected by RACF® or an equivalent security product or by the FMNSECUR exit.

However, there are exceptions to this. Some functions listed in File Manager unprotected functions can be protected in File Manager base function by the facility class FILEM.BASE.UPDATE when the option SEC=YES is specified in FMN0POPT. These functions are indicated in File Manager unprotected functions by ✓ in the fourth column.

Similarly these functions (and others) can be protected in FM/CICS by the facility class FILEM.CICS.UPDATE, when SEC=YES is specified in FMN3POPT. For more information about protecting the CICS® functions, see Customizing to protect update functions in FM/CICS.

The normal security checking of FILEM.FUNCTION.function_code applies to these functions when SEC=YES has been specified in FMN0POPT, FMN2POPT, or FMN3POPT.

Functions not listed in File Manager unprotected functions are protected, and File Manager function to profile name cross-reference shows the profile name used in the FACILITY class to protect a specific function.

All protected functions not listed in File Manager function to profile name cross-reference are protected by the FILEM.OTHER.ALL profile.

In particular, the File Manager functions listed in File Manager functions protected by FILEM.OTHER.ALL are protected by default when you receive File Manager. They are protected by the profile "FILEM.OTHER.ALL", and if you want to use these functions, you must first give the users access to these functions, by defining the profile "FILEM.OTHER.ALL" to RACF® or your equivalent security product.

For information on File Manager profiles, and defining them to your security product, see Setting up the security environment by using RACF or an equivalent security product. In particular, if you use a non-IBM security product, see the warning in Controlling access to File Manager functions with SAF.