Datamaker with Mainframe: [IBM][CLI Driver][DB2] SQL0471N Invocation of routine "SYSIBM.SQLTABLES" failed due to reason "00F30091". SQLSTATE=55023

Products

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

Issue/Introduction

When trying to access to DB2 Mainframe tables from GT Datamaker, we see the following error: 

[IBM][CLI Driver][DB2] SQL0471N Invocation of routine "SYSIBM.SQLTABLES" failed due to reason "00F30091". SQLSTATE=55023 

-DISPLAY DDF 
DSNL080I !C10V DSNLTDDF DISPLAY DDF REPORT FOLLOWS: 
DSNL081I STATUS=STARTD 
DSNL082I LOCATION LUNAME GENERICLU 
DSNL083I C10VPTIB USILDA01.C10VDB2 -NONE 
DSNL084I TCPPORT=7400 SECPORT=7402 RESPORT=7401 IPNAME=-NONE 
DSNL085I IPADDR=
DSNL086I SQL DOMAIN=
DSNL105I CURRENT DDF OPTIONS ARE: 
DSNL106I PKGREL = COMMIT 
DSNL099I DSNLTDDF DISPLAY DDF REPORT COMPLETE

Environment

CA Test Data Manager (TDM)- Mainframe & DB2

Resolution

Here are some common solutions for this error message: 

1. 
- This error seems to be an issue with DB2 database.
- Please contact your DBA and ask them to verify the required stored procedures are enabled on the DB2 database.
- The required stored procedures are: JAVA Database Connectivity (JDBC) Open Database Connectivity (ODBC).
- Please go through below forums for more information about this error: 
http://www-01.ibm.com/support/docview.wss?uid=swg21351101 
http://www-01.ibm.com/support/docview.wss?uid=swg21452742 

2. 
- Make sure your DB2 drivers are up-to-date and correct 
- Cause and Resolution: 
http://www-01.ibm.com/support/docview.wss?uid=swg21452742 
- SQLSTATE values and common error codes: 
(55023: An error occurred calling a procedure.) 
https://www.ibm.com/support/knowledgecenter/en/SSEPEK_10.0.0/codes/src/tpc/db2z_sqlstatevalues.html 

3. 
- The error could be related to a problem that was introduced when upgrading. 
- It is very likely that your stored procedure SYSIBM.SQLTABLES is not in synch. 
- This problem would also occur when running the query from outside Datamaker. 
- The next approach is to get your DBA involved to analyze further. 

4. 
- If your RRS is down, the DBA will need to start this service. Then you will be able to connect to the tables successfully. 
- More about RRS is at this link below. 
https://www.ibm.com/support/knowledgecenter/en/SSEPEK_10.0.0/inst/src/tpc/db2z_implementrrs.html 
- It could have been an improper DB2 shutdown process that caused the RRS service to be down.

Additional Information

If you experience any further issues, please open a support case by going to https://support.broadcom.com