RPG II

June 21, 2002 Timothy Prickett Morgan

Hey, Ted:

I have several clients that still run RPG II
code in the S/36EE and the code runs fine.

I don’t believe in conversion for conversion

sake. [See the article, “One Way to Ease Conversion of RPG II Programs,” Midrange Guru, OS/400 Edition, April 5, 2002.] When an old program needs more than minor modification, I’ll convert it to RPG IV (first to RPG III, then to RPG IV). Sometimes the code is ugly, but I clean it up and add new and improved logic. I’ve read a lot of your stuff, so I know you’re

Determining Whether a User Is Already Signed On, Take Two

June 21, 2002 Timothy Prickett Morgan

Hey, Ted:

I am writing in reference to the first question and answer that was published in the May 31 “Odds and Ends” column. A reader asked the following: “Is it possible for an initial program to determine if the user who is running it is already signed on with another session?”

The technique that you described for setting an object lock is common, and it was probably adequate for the situation portrayed in the original question. However, the object-lock technique doesn’t tell you anything except ‘This object is/is not locked right now.’ Conceivably, locks can be established by users

Parameterized RUNSQLSTM

June 21, 2002 Timothy Prickett Morgan

Hey, Ted:

Can I pass parameters to an SQL statement in a source member before executing the Run SQL Statement (RUNSQLSTM) command? I’m sure there must be a simple way, but I’ve never seen any examples of this.

For example, today I might like to have the SQL statement select company 005. Tomorrow I might want it to select company 007.

— Darrell

What you want is the ability to put placeholders in the SQL source and specify replacement arguments on the RUNSQLSTM command, as you can do with the Start Query Management Query (STRQMQRY) command.

It may be worth