Re: DataArea in a no cycle rpg

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

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?

To write the *LDA (or any other data area) in a non-cycle program, yes, it would need the DTAARA keyword.

But the *LDA is automatically read in any type of module. And a non-UDS data area is automatically locked in any type of module.

I was reading too literally when you said you have use the DTAARA keyword to explicitly tell RPG that a UDS in a non-cycle module is a data area. You meant that you have to explicitly tell RPG that you want to use the data-area opcodes, so you can use OUT to write and unlock the data area.