PDF documentation
Summary of changes
About this document
These topics provide information needed to plan for, customize, maintain, and diagnose problems with IBM® File Manager for z/OS®.
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
    - File Manager supported software environments
    - 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
      - Using a licensed site PL/I compiler
        Adding the PL/I compiler library to the LINKLIST
        Adding the PL/I compiler library to the batch JCL skeletons
        Authorizing the PL/I compiler library for batch processing
        Suppressing PL/I compiler warning messages
    - 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 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
- 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.
Customizing File Manager Db2® Component
Customizing File Manager IMS™ Component
Customizing File Manager CICS® Component
File Manager on VS Code
IBM File Manager for z/OS is a host component that supports various interfaces such as Eclipse and Microsoft Visual Studio Code IDEs.
File Manager on Eclipse
File Manager plug-in for Eclipse, when used with an Eclipse-based platform such as IBM® Explorer for z/OS® or IBM Developer for z/OS, provides easy access through a graphical user interface (GUI) on the workstation to IBM File Manager for z/OS.
Preparing for File Manager Remote Services
Customizing ADFz Common Components server
File Manager options
FM/Db2 options
FM/IMS options
File Manager options specified in PARMLIB members
The library management system exit
File Manager audit records
Support resources
Notices

Using a licensed site PL/I compiler

By default, File Manager uses the internal PL/I compiler.

To use the licensed site compiler, use one of the following methods:

Before you invoke File Manager, allocate the FMNPLI DD to the required compiler library, usually hlq.SIBMZCMP.
Create a FACILITY class profile named FILEM.PLI.EXTERNAL with CONTROL access or higher. For more information, see Controlling the use of the PL/I compiler.

Note:

The PL/I compiler requires a region size of at least 50 MB. Complex copybooks might require a larger region size.