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

Binding Db2® to use File Manager object access method (OAM) functions

If you intend to use File Manager OAM functions, you must bind the File Manager plan, FMNODIRS, into the Db2® system where the OAM objects are defined, to allow the proper working of OAM functions. The following sample jobs are provided in FMN.SFMNSAM1 and can be used to bind the FMNBDIRS plan/collection into a Db2® subsystem.

FMNBDI2K: Db2® V12 JOB to bind the collection associated with plan FMNBDIRS.
FMNBDI2P: Db2® V12 JOB to bind the plan FMNBDIRS.
FMNBDI3K: Db2® V13 JOB to bind the collection associated with plan FMNBDIRS.
FMNBDI3P: Db2® V13 JOB to bind the plan FMNBDIRS.

Customize the sample jobs according to your Db2® installation requirements. See the instructions in the sample jobs for more information about changes you need to make.

The DBRM associated with the plan FMNBDIRS is distributed in FMN.SFMNDBRM.

The following Db2® authorities must also be granted to each user of OAM functions:

Directory processing requires READ authority for the following tables:
- GROUPnn.OSM_OBJ_DIR (all group directories) nn = 00 … 99 inclusive
- SYSIBM.SYSTABLES
- owner.VOLUME
- OAMADMIN.CBR_COLLECTION_TBL
- OAMADMIN.CBR_MGT_CLASS_TBL
- OAMADMIN.CBR_STO_CLASS_TBL
Restoring objects requires UPDATE authority for the following tables:
- GROUPnn.OSM_OBJ_DIR (all group directories) nn = 00 … 99 inclusive
- OAMADMIN.CBR_COLLECTION_TBL