QSH provides a wonderful utility called db2 which allows you to run SQL queries from within the QSH shell, but what if you're in a QP2TERM shell or using SSH - what then?

Today I got asked if you can index in to rows returned by ibm_db_dbi by column name. While this doesn't come out of the box, it can be done pretty easily.

In my last blog I showed how the LIBPATH gets used and also how the runtime search path in the binary gets used. LIBPATH is obviously set as an environment variable, but how does that runtime search path get generated? Let's explore!

So in the last entry, I described the differences between PATH and LIBPATH, but I didn't really explain how LIBPATH is actually used. I'm going to rectify that in this entry. First, though, we need to take a detour and learn how programs get loaded.

I see this kind of tip suggested a lot when dealing with PASE issues:

export PATH=/my/path/bin:/other/path/bin:$PATH
export LIBPATH=/my/path/bin:/other/path/bin:$LIBPATH

This misguided suggestion bugs me to no end, so today I'm here to educate and clear up confusion over LIBPATH.