How to Call DB2 Stored Procedures in Visual Basic 6.0 Applications
This article uses samples to teach IBM® DB2® for OS/390® database administrators and stored procedure authors how to create and run their own Visual Basic, client-side tests for their server-side stored procedures.
If you are a database administrator or stored procedure author for IBM DB2 for OS/390 and z/OS™, you probably use server-side tests (in COBOL) to test your server-side stored procedures. However, there are also benefits to taking the extra step in running some simple, client-side tests. By doing this, you can be aware of complications arising from communication or system problems related to stored procedures before client-side application developers try to use those stored procedures.
For example, if the database server is DB2 for OS/390 or z/OS, the complications that might arise include TCP/IP services being down or problems with the SQL stored procedure builder/processor DSNTPSMP. Creating these client-side tests can give you a better understanding of the way in which your database and stored procedures are being used (which might affect system and stored procedure design and implementation choices).
Finally, the experience of creating and running client-side tests help you bridge the communication gap that sometimes develops between you and the client-side application developers.
- Sample 1: Calling a stored procedure
- Sample 2: Navigating a result set
- Sample 3. Navigating multiple result sets
- Sample 4: Calling a stored procedure that takes one parameter
- Sample 5: Calling a stored procedure with multiple parameters
- Appendix A. Unattended batch processing
- Appendix B. Adding a graphical user interface
- Appendix C. Sample stored procedures in COBOL
- Build your next development project with IBM trial software, available for download directly from developerWorks.