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 |
---|---|---|
EZA2570E: Transfer aborted: SQL PREPARE/DESCRIBE failure | The output file contains the SQL code and error message returned by the DB2® subsystem. |
|
EZA2573E: Transfer aborted: unsupported SQL statement | No output is sent from the host. | The file type is SQL, but the host file being retrieved does not contain an SQL SELECT statement. |
EZA2568E: Transfer aborted: attempt to connect to db2name failed (code) | No output is sent from the host. |
|
EZA2569E: Transfer aborted: SQL not available. Attempt to open plan <planname> failed (DB2_reason_code). | No output is sent from the host |
|
EZA2740E: SQL query not available. Cannot load CAF routines. | No output is sent from the host. | The DSNLOAD library is not in the link list or the FTP server STEPLIB. |
Note: For more information about these 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. |
|
Connection terminated. | The processing time needed by DB2 or FTP or both for the SQL query has exceeded the server time limit for send or receive. If you are using the MVS™ FTP server and the server trace shows a select error due to a bad file descriptor, check the inactive time set for the server and, if necessary, increase the time. An FTP client trace indicates the amount of SQL activity through FTP and the approximate time when each query is processed. |