Security

If the installation has a security package such as RACF or ACF2 on the MVS system on which TDMF is installed, it is necessary to make the appropriate modifications to the security package in order for TDMF to run properly: specifically, profiles and/or command tables should be checked.

Limiting access to the TDMF authorized library to prevent unauthorized use of the TDMF system can be accomplished through security packages. The user associated with the GTDSOPTN batch job must have UPDATE authority for the library pointed to by the GTDKEY DD statement. The Master migration job will also need UPDATE authority for the GTDKEY file if the authorization keys in use specify volume or terabyte limits. To update authorization keys via Option 10 of the TDMF TSO Monitor, the user must have UPDATE authority for the SGTDLLIB library, which must have been allocated as GTDKEY in the GTDSOPTN job.

Important: The GTDKEY data sets must be defined as PDS type, not LIBRARY. Failure to do this will generate an error when trying to apply the product key.

If the History option is selected, UPDATE authority is required for the data set specified in order for TDMF to update that data set. When viewing the history file (and any COMMDS) via the TDMF TSO Monitor, the user must have READ authority.