Customizing File Manager
- Preparing to customize File Manager
- Customizing the operating environment for File Manager
- 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
  - Accessing source code in CA-Panvalet libraries
    The CA-Panvalet interface enables File Manager to work with COBOL copybooks, PL/I include books, and HLASM copybooks stored in CA-Panvalet libraries.
  - Other library management systems
  - Capabilities provided by File Manager via FMNCRAEX
  - Functions which must be provided by FMNCRAEX
  - The LMS sample exit
    Sample code for the LMS user exit is provided in FMN.SFMNSAM1. There are two sample members: FMNCRAEX and FMNCRACJ.
  - Writing your own exit
  - Performance considerations
- 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.

Validate the library

File Manager allows users to enter a copybook library name and member name on many panels. By means of FMNCRAEX File Manager will allow multiple types of copybook libraries without having to specify the type.

The exit must be able to take a library name passed to it and determine whether it is a library which the exit supports. The possible results are:

Yes: the exit supports this library.
No: the exit does not support this library. File Manager should try other access methods (for example, CA-Panvalet or PDS I/O) but should not use the exit to access this data set.
Unknown: the exit was unable to access the library for various reasons (for example, data set in use or security violation).