× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



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

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.