While I have not used Alan Campin's COMPILE tool, I understand that it
can allow you to embed these overrides into your program source so that
you don't need a special compile option for each program with special
requirements. Probably worth a look, and I suspect there may be some
useful suggestions regarding overrides in that product's
documentation...
http://www.think400.dk/downloads.htm
hth,
-Eric DeLong
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Stefano Arrighini -
Smea s.r.l.
Sent: Tuesday, October 05, 2010 12:07 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: OVRDBF, CRTBNDRPG and Activation Group
Hello everyone,
I have a quite strange problem (or better... strange for me...).
I solved it with a work-around... but I'd like to understand its cause.
Because perhaps I'm doing wrong some other...
When I compile RPGLE program, I need to "do some work" before run
CRTBNDRPG.
So I do not "compile" my RPGLE with option 14 but with my own "CO"
option.
This option (inserted in QAUOOPT) call a program that make some changes
and then call CRTBNDRPG.
One of the duty of this program is doing OVRDBF.
When the source contains EXTFILE, my pre-compiler make OVRDBF to success
the compilation (CRTBNDRPG).
Well...
When I "compile" my RPG from a job in Default Activation Group it's all
OK.
When I compile my RPG from a job in a named Activation Group... the
CTRBNDRPG fails.
So, I suppose the command CRTBNDRPG runs EVER in the Default Activation
Group or in a named Activation Group...
As if the CRTBNDRPG "program" was compiled with DFTACTGRP(*YES) or with
ACTGRP(aaaaaa).
Is this correct?
These are my tests and my considerations:
PGM1 (CLLE):
OVRDBF FILE(FILE1) TOFILE(MYLIBFILE/MYFILE)
CRTBNDRPG PGM(MYLIBPGM/PGM2) SRCFILE(MYLIBPGM/SRC) +
SRCMBR(PGM2) DBGVIEW(*SOURCE) +
REPLACE(*YES)
PGM2 contains:
FFILE1 IF E K DISK EXTFILE(FILEXY)
The parameter OVRSCOPE of OVRDBF isn't specified, so it uses default
(*ACTGRPDFN).
When PGM1 runs in Default Activation Group, the scope of OVRDBF is
"calllevel", so CRTBNDRPG is affected from OVRDBF.
When PGM1 runs in a named Activation Group, the scope is "activation
group only",
so if CRTBNDRPG runs in a specific Activation Group (or in the DAG)
isn't affected from OVRDBF.
I solved my problem specifying OVRSCOPE(*CALLLVL) on the OVRDBF
instruction.
So... are my considerations right?
And in this case... CRTTDNDRPG run in a specific AG or in the DAG?
I searched in documentation and forums but I didn't find this
information....
Furthermore...
We are modifying our programs to run them in Named Activation Group and
not in the DAG.
But this operation can produce some problem...
for example OVRDBF scoping... To avoid THIS problem I must specify
OVRSCOPE(*CALLLVL) on all the OVRDBF.
My question is.... how many other problem can I get?
I found some difference in "closing" program... The RCLRSC LVL(*CALLER)
in the DAG can't be "replaced" in a Named AG...
I have to close the Activation Group... Right?
Probably my knowledge of Activation Group is not complete..
Any help would be greatly appreciated.
Thanks in advance
Stefano
midrange.com
