How does TDM use AES Key across Dev, PLE, Prod mainframe systems
Article ID: 417727
Updated On:
Products
Issue/Introduction
We would like clarification of how TDM uses AES Keys across multiple Mainframe environments and systems.
Environment
TDM Mainframe Add-on
Resolution
1. How does TDM Use AES Key across Development, PLE (Pre-production), and Production mainframe systems, and each system would have its independent AES Key generated through ICSF process?
Answer - TDM will use the keys or labels that are defined in each development. The process will read the key that is directly stated in the MAPCSV files or read the content of the LABEL stated in the MAPCSV which was created at the ICSF panels. Remember that, for each environment, the content of the label (which is hidden) differs, so a way to keep the LABEL + its key value consistent throughout all environments is to export them from the first environment created to the other environments.
2. Could TDM software bundle the ICSF process to generate the AES Key for masking with inclusion of encryption in its job execution?
Answer - No. The management of AES Keys is done by a TSO tool (CKDS). TDM uses the keys that are created by that tool, but TDM has no ability to
Additional Information
For more information regarding the Mainframe Masking Functions, see Masking Functions for Mainframe
Feedback
