RE: RPG ILE Problems (Activation Groups)

Luis,

I'd compile all the programs with DFTACTGRP(*NO) and ACTGRP(QILE). Compiling with DFTACTGRP(*NO) ACTGRP(*CALLER) is the same as DFTACTGRP(*YES) if the program is getting called from another program running with DFTACTGRP(*YES) or an OPM program.

Consider changing the OVRDBF OVRSCOPE parameter, the DLTOVR LVL parameter and the OPNQRY OPNSCOPE parameter defaults to *JOB. Changing the defaults lets these commands work across activation groups without changing code. Once all the programs are recompiled into the QILE activation group and you have no OPM programs still running in the default activation group you can revert back to the system defaults.

Paul Morgan

Principal Programmer Analyst
IT Supply Chain/Replenishment

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of LuisMaldonado
Sent: Thursday, March 03, 2011 5:40 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: RPG ILE Problems (Activation Groups)



Hi,
we have a lot of problems in our system about activation groups.
I wonder if you can help us !!!
I mean we are working with ILE RPG but always compile with DFTACTGRP(*yes). Now we begin to compile with DFTACTGRP(*NO) ACTGRP(QILE) and all the OVRDBF and OPNQRY don´t work.

Because we have some ILE RPG that use procedures we need to compile with DFTACTGRP(*NO) and QILE or *Caller.

Two questions :
1) is a good idea to compile all the programs (CLLE,RPGLE) of the system with DFTACTGRP(*NO) ACTGRP(*caller) ? Can cause some problems ?

2) Maybe, It´s better to compile all the programs with DFTACTGRP(*yes) and only the programs that have procedures with DFTACTGRP(*NO) ACTGRP(*caller) .

Thank you very much.





Lluis Maldonado