RE: Issue with ovrprtf/dltovr (is this an activation group issue)

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx

On Behalf Of Scott Klement
Sent: Friday, September 14, 2007 2:50 PM
To: RPG programming on the AS400 / iSeries
Subject: Re: Issue with ovrprtf/dltovr (is this an activation group

Hi Kevin,

Just a quick note on top of Scott's notes. The batch routing process
starts out in OPM compatibility mode. So if the first program you
submit is *CALLER, then your job stream is in OPM compatibility

No, that's not true. Not if you're using the same terminology that

using!

When I say "OPM Compatibility Mode", I mean programs compiled with
DFTACTGRP(*YES). If you've specified DFTACTGRP(*NO) and
ACTGRP(*CALLER), it will not inherit OPM compatibility mode from the
caller.

It's true that it'll run in the default activation group -- but the
other aspects of OPM compatibility will not be inherited. It will run
like an ILE program -- the only difference being that the activation
group can't be reclaimed.

That means that default scope of the ovr and dltovr commands

In OPM mode the default acts like *CALLLVL.

That's true. Because it's running in the default activation group,

value *ACTGRPDFN (which is the default value for the OVRSCOPE

of the OVRxxx CL commands) will act like *CALLLVL.

However, that's an aspect of being in the default activation group,

an aspect of being in OPM-compatibility mode.
--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing

To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.