Re: OVRDBF et activation groups

Birgitta answered the question about the OVR (*JOB would also be a valid option for the scope).

As to the reclaim. The whole point of *NEW for the AG is to provide a self-destructing AG. If you replaced *NEW with (say) MYAGNAME then when the initial program with that designation returned to its caller AG MYAGNAME would remain active and a specific RCLACTGRP MYAGNAME would be required to clean it up. In the case of *NEW the AG self-destructs on the exit of the program that created it. This was initially instituted to make it easy to mirror the behaviour of C programs but a lot of RPGers like to use it from the main menu level to automatically clean up overrides, close files, etc. without any explicit actions being needed.


Jon P.

On Dec 30, 2022, at 12:05 PM, Dave <dfx1@xxxxxxxxxxxxxx> wrote:

Hello,



I modified a CLP by adding DCLPRCOPT DFTACTGRP(*NO) ACTGRP(*NEW). The
subsequent programs are compiled with ACTGRP(*CALLER). Why aren’t my OVRDBF
functioning any longer ? They aren't even visible when working with the job
at the same level as the program that issued them.

Also, I put RCLACTGRP ACTGRP(*ELIGIBLE) at the end of the program and
noticed while debugging that no activation groups were eligible for
reclamation. Would that be because I used ACTGRP(*NEW) ?



Thanks
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com