DRDA application problems

The best time to handle a problem with an application is before it goes into production. However, it is impossible to anticipate all the conditions that will exist for an application when it gets into general use.

A problem you encounter when running a distributed relational database application can exhibit two general symptoms: incorrect output or the application does not complete in the expected time. The figures in these topics show generally how you can classify problems as application program problems, performance-related problems, and system-related problems so that you can use standard IBM® i problem analysis methods to resolve the problem.

The job log of either the application requester (AR) or the application server (AS) can tell you that a package failed; the listings of the program or the package can tell you why it failed. The SQL compilers provide diagnostic tests that show the SQLCODEs and SQLSTATEs generated by the precompile process on the diagnostic listing.

For Integrated Language Environment® (ILE) precompiles, you can optionally specify OPTION(*XREF) and OUTPUT(*PRINT) to print a precompile source and cross-reference listing. For non-ILE precompiles, you can optionally specify *SOURCE and *XREF on the OPTIONS parameter of the Create SQL program (CRTSQLxxx) commands to print a precompile source and cross-reference listings.