Hi,
could someone explain me why Using *caller with dftactgrp causes big problems.
thank you
Lluis Maldonado
Dpto. Informática - CIFSA
Area logística
Tel: +34 93 814 09 09 - Extensión: 249
E-mail: lmaldonado@xxxxxxxx
________________________________________
De: rpg400-l-bounces@xxxxxxxxxxxx [rpg400-l-bounces@xxxxxxxxxxxx] en nombre de Bryce Martin [BMartin@xxxxxxxxxxxx]
Enviado el: jueves, 03 de marzo de 2011 17:45
Para: RPG programming on the IBM i / System i
Asunto: RE: RPG ILE Problems (Activation Groups)
I give each Program its own AG. So if I great a program called BKM001R
then I name the AG BKM001. Then I can just reclaim BKM001 and only that
program is affected. Works well so far, havnen't seen any pitfalls yes :D
Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777
BMay@xxxxxxxxx
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
03/03/2011 09:44 AM
Please respond to
RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>
To
RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>
cc
Subject
RE: RPG ILE Problems (Activation Groups)
I agree that you should compile into a named activation group, but PLEASE
do not use QILE. There are too many pieces of software out there that use
this default value. You could reclaim QILE to clean up resources in your
application and have undesirable effects on other applications that you
may be using in the job that happen to be using the QILE activation group.
I generally recommend using something simple like your company's or
software's name as the activation group when fist starting out. As you
learn more about ILE concepts, you can decide if you need more activation
groups or not. Honestly, most shops usually just need the one anyway.
Hope this helps,
Brian May
Project Lead
Management Information Systems
Garan, Incorporated
Starkville, Mississippi
"Morgan, Paul" <Paul.Morgan@xxxxxxxxxxx>
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
03/03/2011 08:25 AM
Please respond to
RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>
To
RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>
cc
Subject
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
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing
list
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.
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing
list
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.
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing
list
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.
--- This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us and destroy this message immediately. ---
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
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.
midrange.com
