Stored procedures are great tools for easily delivering the results of one or more queries (aka result sets) to a client/server or Web application. (For a brief outline of this technique from the client side, see "Retrieve Multiple Result Sets from a Stored Procedure.") However, testing DB2 stored procedures that return multiple result sets can be challenging. For instance, I wrote a stored procedure that returns an immense amount of related data in six result sets and is subsequently processed in a SQL Server database. Every once in a while, however, there is a problem that requires examination of all the result sets for troubleshooting. How does one go about easily capturing these result sets?
Santa, SkyView Partners, and i5/OS all have gifts for you!
At this time of year, children of all ages are snooping for those treasures that have been hidden and will eventually appear as beautifully wrapped presents. But until then, the hunt is on! So I thought it might be fun to "unveil" a few of the hidden treasures of i5/OS security.
One of the latest i5/OS gifts that I discovered is the ability to see who is connected to the NetServer server and which file share they used to make the connection. I've found this very helpful in determining the feasibility of removing file shares, especially those to root. Simply open iSeries Navigator -> Network -> Servers and click on TCP/IP. When the list of servers appears on the right, right-click on iSeries NetServer and choose Open.