Re: SQLRPGLE attribute question

On 2013-07-03, at 9:56 AM, Gary Thompson <gthompson@xxxxxxxxxxx> wrote:

I just finished re-compiling some modules and programs for a file change.

I had not noticed this before, but when I create a *MODULE from a
SQLRPGLE member, the module attribute is RPGLE - I wonder why ?

As others have said this is because the created program is pure RPGLE. It helps if you realize that source member types in PDM are just conventions. There is nothing fixed in the system that says you can't specify MYRPG (for example) as the type for all your source members including those containing SQL. The type only has meaning within PDM (where it determines which compile command to use) and SEU where it determines which syntax checker is used.

The value the system uses as a module attribute is based on the compiler used not on the source type. Change an RPG program to be source type XYZ and then compile it with CRTRPGMOD and you'll see.

But, today, the compile failed due to a mismatch between an SQL cursor
and the receiving data structure. Apparently the compiler got "tighter"
in the last few years -

Actually if anything it has loosened up as I found to my cost recently when I specified the columns in a SELECT in the wrong order. These days (V7) SQL will (when it can) automagically cast columns to the type specified in the DS.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com