Note: The code accompanying this article can be downloaded here

As the only developer in a small company, I try to find ways to make the computer work so I don’t have to. We don’t have an operator and no one is dedicated to monitoring the QSYSOPR message queue, so when problems happen, I need a way to be notified, wherever I am. I’ve tried a couple of programming solutions that captured information from the WRKACTJOB screen, but there were always conditions that I didn’t anticipate and weren’t captured by those methods.

Then I learned about Monitors in iSeries Navigator

I just read your article about the SET OPTION statement. Here are some minor comments about the OPTION CLOSQLCSR. There is a difference between closing a SQL cursor with the SQL statements CLOSE or COMMIT and closing a cursor at either *ENDMOD or *ENDACTGRP (or the other options for non-ILE programs).

When closing a cursor with the SQL commands, only a soft (or pseudo) close will be performed, that is the ODP (if reusable) stays cached and will only be reactivated the next time the SQL statement will be executed.

Closing a cursor at the end of a module (*ENDMOD)

I have a new user starting, and I need to change the default user ID sign-on information that ODBC uses to connect her machine to our i5 partition. This computer was previously assigned to another user, and that user ID keeps appearing in the Signon to iSeries box whenever the computer starts an ODBC connection. How do I change the default user ID that ODBC uses for an i5 connection?

–Bruce

ODBC connection values are defined in the Connection Options screen inside their ODBC driver. It’s fairly simple to view and change these values for an i5, iSeries, or AS/400