Customizing Z Data Tools
- Preparing to customize Z Data Tools
- Customizing the operating environment for Z Data Tools
  - License and enable Z Data Tools
  - Modifying the ISPF environment
    To make it easy to start Z Data Tools under ISPF, configure your ISPF environment as described in the following sections.
  - Enabling Z Data Tools to work with certain products
  - Disabling Websphere MQ feature by system name
  - Running Z Data Tools with APF-authorization
  - Language Environment® considerations
- Customizing Z Data Tools
- Customizing the Z Data Tools security environment
  Z Data Tools provides security for system-oriented functions through ®either RACF (or an equivalent security product) or the HFMSECUR exit.
- Customizing Z Data Tools to write audit records to SMF
- Customizing the Z Data Tools audit facility for the Z Data Tools Base component
- Customizing Z Data Tools for national languages
  You can customize Z Data Tools for national languages other than English.
- Customizing Z Data Tools Service Provider for z/OS® Connect
  Z Data Tools Service Provider for IBM® z/OS® Connect Enterprise Edition enables client applications to access IBM Z data sources using z/OS Connect.
- Customizing Z Data Tools to use library management system libraries
- Customizing Z Data Tools to use the Optim™ Data Privacy Provider API
- Customizing Z Data Tools to use an I/O exit
- Customizing Z Data Tools to use a scrambling exit
- Verifying the customization of Z Data Tools
  After you have completed the initial installation and customization of Z Data Tools Base function, you can perform the following steps to verify your customization.

Language Environment® considerations

During the Z Data Tools Initialization process, Language Environment® (LE) preinitialization facilities (CEEPIPI) are used to create and initialize a common run-time environment.

This means that if LE is active when Z Data Tools is invoked, there are restrictions on Z Data Tools functionality because the CEEPIPI functions are not available.

Note that these restrictions only apply if LE is active when Z Data Tools is invoked. (LE active means that Z Data Tools has been invoked directly via an LE application (for example, from Enterprise COBOL).)

The restrictions are:

TRAP(ON,NOSPIE) should be set to allow Z Data Tools abend handler to function correctly.
An LE-enabled I/O exit cannot be used.
MOD_DATE REXX Built-in function cannot be used.
Scramble Exit (if used) must be in Assembler (non-LE).
Library Management exit (LMS=USERLMS) cannot be used.