Re: DataArea in a no cycle rpg

"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx> wrote on 03/12/2018 05:36:38
PM:

On 2018-03-12 12:02 PM, dlclark@xxxxxxxxxxxxxxxx
wrote:

I did some testing. You're probably missing the DTAARA

keyword in

column 40 of the UDS statement. Using the MAIN keyword means that the

LDA

(and other data areas) cannot be automatically handled by the RPG

program.

Therefore, you must explicitly tell RPG that your UDS is a data area

by

specifying the DTAARA keyword on your UDS statement and coding the IN,
OUT, and UNLOCK op codes in your calculations.

When you use the MAIN keyword, the UDS is still automatically handled by

the RPG program. But the automatic handling only applies to locking the
data area during module initialization.

The automatic handling I was referring to is the reading of and
writing of the *LDA. Am I not correct that this is done automatically by
a cycle program but is not done for a non-cycle program? Am I not correct
that a non-cycle program would have to use both the DTAARA keyword and the
IN and OUT keywords with the *DTAARA parameter in order to read and write
the *LDA?


Sincerely,

Dave Clark