IDMS masking issue

Products

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

Issue/Introduction

After resolving issues with ETL extract process, I am now trying to run the masking and get this message

00029E  

Maximum number of record definitions (50) exceeded   

I'm aware that I reported this before but don't really understand the issue or how to get round it.

The message says 
0029E0
Maximum number of record definitions (%1) exceeded
Reason:
More record types are being masked than the program can process
Action:
Reduce the number of records masked in one run, by splitting the masking into two or more runs

How do I reduce the number of records? Is that in the DataMaker and FDM or can I do this on the files that have been passed to the mainframe?

Environment

Release : 6.0.03

Resolution

Several issues were addressed:

1. The client was advised to install the latest patch, which being cumulative, included corrections made to the Seed List manipulation facility that was redesigned and rebuilt some time ago. This included new version of the embedded processing programs and replacements for the PROCs, along with multiple new utility facilities for data download (VSAM and DB2) and library/file allocation.
2. Issues were found in the masking program that processes the AFL generated by FDM (the AFL which was itself in error, was fixed with another Windows patch). GTXMSKSF was only able to accept Up to 75 RECNAME clauses (generally this is more than sufficient, however files generated by the IDMS deconstruction will require more). The client's file contained 138. 10 internal tables were increased to 200 elements in size and this appeared to solve the issue.
3. As a successor to the RECNAMEs issue a further (connected) issue appeared. This related to the linkages created by the IDMS download tool in concert with FDM. It too required expansion.

After the above changes were made, a series of basic tests showed masking to take place where expected. Additionally, the area of table definition within GHTXMSKF has been clearly marked such that future table expansion will be straightforward.