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
  - 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.

Language Environment® considerations

During the File Manager Initialization process, Language Environment® (LE) preinitialization facilities (CEEPIPI) are used to create and initialize a common run-time environment.

This means that if LE is active when File Manager is invoked, there are restrictions on File Manager functionality because the CEEPIPI functions are not available.

Note that these restrictions only apply if LE is active when File Manager is invoked. (LE active means that File Manager has been invoked directly via an LE application (for example, from Enterprise COBOL).)

The restrictions are:

TRAP(ON,NOSPIE) should be set to allow File Manager abend handler to function correctly.
An LE-enabled I/O exit cannot be used.
MOD_DATE REXX Built-in function cannot be used.
Scramble Exit (if used) must be in Assembler (non-LE).
Library Management exit (LMS=USERLMS) cannot be used.