DSNT408I SQLCODE = -104 ERROR: ILLEGAL SYMBOL when masking DB2 tables on the Mainframe
search cancel

DSNT408I SQLCODE = -104 ERROR: ILLEGAL SYMBOL when masking DB2 tables on the Mainframe

book

Article ID: 241260

calendar_today

Updated On:

Products

CA Test Data Manager (Data Finder / Grid Tools)

Issue/Introduction

While executing the masking job for one of the DB2 Mainframes tables, we are getting job abended error with RC=12.
The strange part is the masking job is working fine for a few other DB2 tables/DBs in the same environment but throwing errors for this table.

Table to mask must have a primary key, unique index or unique columns defined <TABLE>

DSNT408I SQLCODE = -104, Error: Illegal Sybol "End-ofStatment>"
Some symbols that might be legal are: not exists xmlexists
array_exists + - Case current

We have also verified from our DBA team if the table has any missing privileges, but that’s not the case here.
The table shares the same privileges as that of other tables for which we are able to perform the successful masking using the same job.

Need your help/guidance in resolving this issue.

Environment

TDM Mainframe 4.10.x and up

GTXMSK Process

Cause

For masking to work on the Mainframe, we require a definition that TDM can sort and identify the row's uniqueness. Therefor we require a Primary Key, Unique Index, or unique columns defined.

Resolution

The DBA for the client must add a primary Key, or unique index, to the Table being masked:

MF TDM does now allow masking in a table without primary keys, unique index, or some way for the application to identify the row's uniqueness.

Additional Information

Normally, an error -104 is related to some kind of syntax error in the SQL Statement.
But it can also be caused due to the missing primary key.