Note: The code accompanying this article is available for download here.

Using the IBMDASQL provider, I want to find the field/column description/label for fields in a record set. However, all my scenarios return null. I am using IBM iSeries Access for Windows V5R3M0 service level SI30707.

–Andy

Here is the Excel VBA code snippet that Andy sent in.

Sub testit()
   Dim con, com, rs
   Set con = CreateObject("ADODB.Connection")
   con.Open "provider=IBMDASQL;data source=AS400;", "", ""
   Set rs = CreateObject("ADODB.Recordset")
   Set com = CreateObject("ADODB.Command")
   Set com.ActiveConnection = con
   com.CommandText = "select * from QIWS.QCUSTCDT for read only"
   Set rs = com.Execute()
   Debug.Print 

I hate huge programs. For one thing, I’m not smart enough to wrap my mind around a big program. And it seems that modifying one part of the program invariably causes something to go amiss elsewhere. Dividing a program into subprocedures, modules, and multiple programs is a good way to manage large tasks. But what do you do when you’ve divided a program into two or more modules and/or programs, and more than one of them needs to contribute to a single report? You share.

Suppose you have a program that builds a report of accounts receivable. It’s a manageable

Similar to other hardware systems, crises can happen whenever you administer iSeries, System i, and Power i equipment in a data center. However, being a good administrator means knowing what to do and having the appropriate information available when you’re handling a crisis. This week, I’ll look at four key lists you should have handy to restore functionality after a system issue or disaster occurs.

The Big Four Lists

Generally, you’ll need the following information at your fingertips when a critical issue occurs that eliminates some or all i operating system functionality in your shop.

1. IP addresses, critical profile names,