Home
Customizing File Manager
Customizing File Manager to use an I/O exit
Using the I/O exit control block
The I/O exit control block is a single parameter that is passed with each call from File Manager to the I/O exit and returns data from the I/O exit to File Manager.
Termination call discussion

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
- Customizing File Manager to use the Optim™ Data Privacy Provider API
- Customizing File Manager to use an I/O exit
  - Exit protocol
  - Writing your exit
  - Exit control block data names
  - Using the I/O exit control block
    The I/O exit control block is a single parameter that is passed with each call from File Manager to the I/O exit and returns data from the I/O exit to File Manager.
  - Installing your 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.

Termination call discussion

The last call for a given data set is always one (and only one) termination call. The termination call is intended primarily to allow de-allocation of resources allocated at initialization time. File Manager makes the termination call even if exit processing was terminated by an error or a request from the exit to continue without calling the exit again.