Customizing File Manager to use the Optim™ Data Privacy Provider API
To enable File Manager to specify and run ODPP commands, you must first allocate or define a DD name FMNODPP. This name points to a data set that contains the environment variables that are required by the ODPP to run as a TSO or batch application.
Example
//FMNODPP DD DISP=SHR,DSN=OPTIM.ODPP.SAMPLIB(ENVVARS)
Where the data set member ENVVARS contains the following lines:
LIBPATH=/usr/local/odpp/odppbin
ODPPLL=/usr/local/odpp/licensefiles
ODPPERRL=/usr//local/odpp/odppbin
ODPPTRCL=/usr/local/odpp/tracefiles
ODPPTRC=N
Customize the names to match the path names that are specified in the installation of the ODDP API. Refer to the relevant ODPP User's Guide and ODPP Installation Guide for more details on the environment variables required for your installation.
If the FMNODPP DD is allocated by JCL or TSO allocation statement, File Manager attempts to initialize the framework that is required for running ODPP commands. If the framework initialization is successful then you are able to define the ODPP commands as a scrambling attribute for any given field in a File Manager template. The commands are run when you run a copy operation with an input and output template and the receiving field has the scrambling option of ODPP with the associated ODPP command. For more information, see the File Manager for z/OS® User's Guide and Reference.
- For TSO/ISPF users. Only one instance of File Manager can have the framework initialized. Therefore, when running split sessions under ISPF, only one session can have an active File Manager session that can support specifying and running ODPP commands.
- You might need to increase your region sizes when running
File Manager to accommodate the ODPP API. You receive
a Language Environment®
message that indicates
not enough storage
when you start File Manager if your region size is insufficient. Run with a minimum of 100 MB. - The IBM® Optim™ Data Privacy Solution on z/OS® needs to be Version 11 or above.