Customizing File Manager
- Preparing to customize File Manager
- Customizing the operating environment for File Manager
  - Enable/Register File Manager
  - Modifying the ISPF environment
    To make it easy to start File Manager under ISPF, configure your ISPF environment as described in the following sections.
  - Enabling File Manager to work with certain products
  - Disabling Websphere MQ feature by system name
  - Running File Manager with APF-authorization
    - Troubleshooting problems with APF-authorization
  - Language Environment® considerations
- Customizing File Manager
- Customizing the File Manager security environment
  File Manager provides security for system-oriented functions through ®either RACF (or an equivalent security product) or the FMNSECUR exit.
- Customizing File Manager to write audit records to SMF
- Customizing the File Manager audit facility for the File Manager Base component
- Customizing File Manager for national languages
  You can customize File Manager for national languages other than English.
- Customizing File Manager Service Provider for z/OS® Connect
  File Manager Service Provider for IBM® z/OS® Connect Enterprise Edition enables client applications to access IBM Z data sources using z/OS Connect.
- Customizing File Manager to use library management system libraries
- Customizing File Manager to use the Optim™ Data Privacy Provider API
- Customizing File Manager to use an I/O exit
- Customizing File Manager to use a scrambling exit
- Verifying the customization of File Manager
  After you have completed the initial installation and customization of File Manager Base function, you can perform the following steps to verify your customization.

Running File Manager with APF-authorization

In batch mode, File Manager can run APF-authorized or non APF-authorized. File Manager cannot run APF-authorized under ISPF. You make File Manager authorized by adding FMN.SFMNMOD1 to your site-specific IEAAPFxx or PROGxx member in SYS1.PARMLIB.

Note:

If you are running File Manager APF-authorized in batch mode, and you want to run File Manager batch jobs using COBOL copybook templates, then you MUST also authorize the COBOL compiler library. If you do not do this, you will receive an ABENDS306 from the batch job.
If you plan to access source code in a library management system that does not provide a SUBSYS interface, then you cannot run File Manager APF-authorized. For information about accessing source code in an LMS without a SUBSYS interface, see Accessing source code in an LMS without SUBSYS interface.

To activate any changes you have made to SYS1.PARMLIB members, either restart your system, or use the appropriate commands for your site to dynamically activate the changes.