Re: UDS & Allocations

Just to add more useless information to the story, when I got a hold of this
program, it had both an I-spec UDS & a C-spec *NAMVAR coded. Glad my name
wasn't on it (VBG)!

Buzz Fenner
Systems Analyst/Network Administrator
870.930.3374
mailto:bfenner@xxxxxxxxxxxxxxxx

message: 5
date: Wed, 28 Nov 2007 18:08:21 -0600
from: Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>
subject: Re: UDS & Allocations

Whether it's ILE or OPM is irrelevant. The real question is whether
it's RPG III or RPG IV.

RPG III has two options:
- Use UDS
- use *NAMVAR DEFN and the IN/OUT op-codes.

RPG IV (regardless of whether it's in OPM compatibility mode or true ILE
mode) has three options:
- Use UDS
- use *NAMVAR DEFINE and the IN/OUT op-codes.
- use the DTAARA D-spec keyword and the IN/OUT op-codes.

In either case, it's possible to use both UDS and the IN/OUT op-codes on
the same data area in the same program, but I strongly discourage you
from doing that, because it's confusing. IMHO, you should either use
UDS, or you should make sure you do NOT code UDS (but just code DS
instead) if you plan to use the IN/OUT op-codes.



Francis Lapeyre wrote:

Not to split hairs, but RPG IV can be made to *act like* an OPM program,

for

all intents and purposes. And as far as I know, *NAMVAR DEFN (or *NAMVAR
DEFINE) work the same way in III and IV.

--
PRIVACY WARNING: For auditing purposes, a copy of this message has been
saved in a permanent database.





--
PRIVACY WARNING: For auditing purposes, a copy of this message has been
saved in a permanent database.