Symptoms of SQL problems
Table 1 and Table 2 show some symptoms and possible causes
of SQL problems. Table 1 shows problems
that generate a reply beginning with 55x.
Reply | Output file | Possible causes |
---|---|---|
Reply 551: Transfer aborted: SQL PREPARE/DESCRIBE failure | The output file contains the SQL code and error message returned by the DB2® subsystem. |
|
Reply 551: Transfer aborted: unsupported SQL statement | No output is sent from the host. |
|
Reply 551: Transfer aborted: attempt to connect to db2name failed (code) | No output is sent from the host. |
|
Reply 551: Transfer aborted: SQL not available. Attempt to open plan <planname> failed (DB2_reason_code). | No output is sent from the host. |
|
Reply 550: SQL query not available. Cannot load CAF routines. | No output is sent from the host. |
|
Note: For more information about the messages, see z/OS Communications Server: IP and SNA Codes.
|
Table 2 shows other SQL
problems.
Problem | Possible causes |
---|---|
Output file contains only the SQL SELECT statement. |
|
Client closes the connection because server is not responding. |
|