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.

Performance considerations

The major performance considerations for the exit are related to GetMemberInfo and wildcard processing:

If there are no wildcards: When a member name is provided to GetMemberInfo without any wildcard characters (* or %), attention should be given to ensuring the fastest possible response time. This function is used as an existence check on the member. The member attributes (RHS field) are not displayed on an ISPF panel, so, if you want to, you can leave this field blank.
If a wildcard is present: Some user libraries contain large numbers of members. Ten to thirty thousand members are not unusual. Attention should be given to finding ways to give good performance when GetMemberInfo is called with wildcards. How to do this depends on the functions offered by the LMS. Be aware that File Manager gets all members matching the given pattern from the exit before presenting any information to the user via a member selection list.