Retrieving Data With SQL › Interpreting Common Error Messages in SQL Retrieval

Interpreting Common Error Messages in SQL Retrieval

For retrieval processing, SQL Prepare and Describe commands are issued during the pre-compile phase of CA Culprit. If any errors are detected, you will receive the following messages on your Sequential Parameter Listing.

mm/dd/yy              SEQUENTIAL PARAMETER LISTING            Vnn.n   PAGE 1

00 ** SYSIN **        PRO  USER=MZC  PW=MZC
  C200138 INSTALLATION SECURITY OPTION IS NO
                      IN  DB(Q)  SCHEMA=INV  DICTIONARY=TSTDICT
                      SQL SELECT * FROM  XYZ;
E C700054 ERROR FROM PREPARE SQL SELECT
  C700055   SQLCODE:  -0004          SQLCERC: 5138
  C700056   SQLCESER:  0000          SQLCNRP: 0000
  C700057    Table INV.XYZ not found in catalog
E C700052 SQL ERROR ENCOUNTERED

Messages 55, 56, and 57 print the error codes and text contained in the SQL Communications Area (SQLCA).

see the CA IDMS SQL Reference Guide, for more information about the SQLCA error code fields.

Any E or F level errors associated with the SQL statement will prevent CA Culprit from generating REC parameters to describe the SQL columns and null indicators. That means you will probably receive messages like "Field Not Defined" on the Input Parameter Listing. Ignore these extraneous errors for now. They will probably go away as soon as you correct the SQL statement.

During the extract phase of CA Culprit, you issue SQL commands to perform the bulk fetch operation. Any errors at this time appear under Run Time Messages. The SQL error codes and text are be formatted exactly as shown above.