I have an RPG program (defined as an SQL external stored procedure) that returns a data structure array as a result set. When this procedure is called from iNavigator, I can see the result set. But in our .NET client/server environment, the result set is not returned to the .NET program. Further, the .NET program first calls a “setup” stored procedure that establishes the library list and general environment settings. Thereafter this “setup” procedure calls the RPG program that returns the result set. The RPG program runs upon request from the .NET world but no result set is returned.

–B.C.

I find it ironic that the most commonly used CL command suffers from an annoying (if not aggravating) limitation that does not afflict many less-used commands. Fortunately, the commands you and I write do not have to have this limitation.

The command to which I refer is CALL. The limitation is that the parameters must be literals or variables, never expressions. To see what I mean, look at this CALL command.

call   somepgm   parm(%sst(&Data 5 4))

Doesn’t that make sense to you? The first parameter consists of bytes 5 through 8 of a variable named &DATA. The compiler complains, expressing

We have a persistent problem with application jobs waiting on record locks with an RNQ1218 (unable to allocate a record in file &7) message. The record is only temporarily locked because by the time my help desk looks at it, the lock is gone and the program resumes after answering the message with an ‘R’ (Retry). Any ideas what we can do so we’re not constantly answering record lock messages?

–Bob

In your case, the first thing is to determine why a constantly needed record is always being locked and to devise a fix. This could be a case where