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
    - Enabling WebSphere® MQ support
      To access WebSphere® MQ queue managers and queue contents on the local z/OS® system where File Manager is running, the WebSphere MQ libraries must be made available to File Manager and users must be granted read and update access.
    - Customizing for processing COBOL copybooks
      To use the view, edit, copy, print, or data create functions with a COBOL copybook, you need to make a COBOL compiler available to File Manager.
      - Using a supported COBOL compiler
        If a supported COBOL compiler is available and will be used by File Manager, review the following sections for customization tasks you might need to perform.
      - Using the File Manager COBOL compiler
        Forcing the use of the File Manager COBOL compiler
        Adding the COBOL compiler library to the batch JCL skeletons
        Authorizing the COBOL compiler library for batch processing
        Suppressing COBOL compiler warning messages
        Using COBOL compiler options with File Manager
    - Customizing for processing PL/I include books
    - Customizing for processing HLASM copybooks
    - Customizing to use DFSORT to improve File Manager performance
      File Manager can use DFSORT to improve the performance of the Data Set Copy and Data Set Print functions under ISPF and in batch.
    - Binding Db2® to use File Manager object access method (OAM) functions
  - 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 RACF® (or an equivalent security product).
- Customizing File Manager to write audit records to SMF
- Customizing the File Manager audit facility for 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.

Using the File Manager COBOL compiler

File Manager uses its internal COBOL compiler if one of these conditions applies:

A licensed, supported COBOL compiler is not available.
An //FMNCOB DD DUMMY has been defined (as described below).
A user has a minimum of Read access to the SAF FACILITY class profile FILEM.COBOL.INTERNAL, as described in Controlling the use of the COBOL compiler.

Note: The File Manager compiler requires a region size of at least 40 MB, and possibly more depending on the complexity of the copybook being compiled.

If File Manager is to use its internal COBOL compiler, review the following sections for customization tasks you might need to perform. Not all the functions available using a supported COBOL compiler are available using the File Manager compiler, and for functions that are available, the customization might differ.