Every “old timer” IBM i developer knows about the compiler option to include or exclude source statements within an OPM or ILE program. The CL compilers even have an option to allow CL source to be retrieved from the Retrieve CL Source (RTVCLSRC) command.

While high-level language programmers can decide whether or not to include source statements with their objects, DB2 SQL developers had no such option because anyone could use a tool like iNavigator to retrieve the SQL source. Thanks to the IBM i 7.1 technology refresh 4 update, SQL developers now have the option to obfuscate their

I am writing in response to your recent article, Add Powerful Generic Processing to Your Applications, regarding generic processing. I have another, simpler technique that you should share with my fellow readers of Four Hundred Guru.

–D

D’s technique is to use the Remove Link (RMVLNK) command. Here’s the example he (she?) gave me:

RMVLNK OBJLNK('/qsys.lib/dug*.devd')

This command deletes device descriptions with names that begin with DUG. Notice that RMVLNK requires objects to be specified in the IFS naming convention.

You may use RMVLNK or its two aliases, DEL and ERASE, for objects other than libraries. For libraries,

For this week’s column, here’s some interesting information I found about discovering the history of your TCP/IP interfaces and how to retrieve the QUSRTOOL library for installing the IBM i NetServer GO NETS menu discussed in last week’s column.

Displaying The History Of Your IBM i TCP/IP Interfaces

If you’re on i 6.1 or above, here’s an easy way to determine when and how your TCP/IP interfaces were last started or stopped. You can do this by looking at the job log history of the TCP/IP control job, QTCPWRK (formerly named QTCPIP in V5R4Mx and below).

Whenever TCP/IP