Required Artifacts for TDM Mainframe Support Cases

Products

• CA Test Data Manager (Data Finder / Grid Tools)

Issue/Introduction

This article lists the mandatory input and output artifacts required by Broadcom Support to investigate and resolve TDM Mainframe defects.

To expedite resolution, please provide the following artifacts when opening a support case for Test Data Manager (TDM) mainframe issues.

Environment

CA Test Data Manager, TDM Mainframe Add-on.

Resolution

Input Files:

• MAPCSV: Defines the specific tasks performed during the run.
• DEFCSV:  Required for non-DB2 file masking; maps entries to input data.
• Data Layout (one of the following): This describes the input data 
  • INCLUDE (PL/I)
  • COPYBOOK (COBOL)
  • DCLGEN (DB2) 
• Masking PROC: Provide the name used. If customized, a copy of the actual PROC is required to identify the masking logic.
• Input Data (file or DB2 according to what is in use): Required for troubleshooting. If data is sensitive, you must provide a sanitized/non-secure version that reproduces the issue.
• Run JCL and Options: Shows the control logic and parameters used for the job.
• Any other pertinent components that would have affected/caused the issue.
  
  
  NOTE: Data mapping errors often cause issues, particularly during file translation.
  For example, a file translated between CSV and fixed formats may retain commas not accounted for in the COPYBOOK or DEFCSV.
  Reviewing the actual data, in many cases, helps quickly resolve the issue. 

Output Files:

• Job Log: Includes JCL and system messages.
• SYSOUT: Essential for viewing internal processing details. 
• Report: Confirms if the run completed or terminated prematurely.
• Audit Trail: Provides "before" and "after" states for individual data elements.
• Output Data: The resulting file or DB2 table from the failed/problematic run.