|
Hello everyone,CRTBNDRPG.
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
and then call 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
the compilation (CRTBNDRPG).
One of the duty of this program is doing OVRDBF.
When the source contains EXTFILE, my pre-compiler make OVRDBF to success
allOK.
Well...
When I "compile" my RPG from a job in Default Activation Group it's
When I compile my RPG from a job in a named Activation Group... theCTRBNDRPG fails.
Group or in a named Activation Group...
So, I suppose the command CRTBNDRPG runs EVER in the Default Activation
As if the CRTBNDRPG "program" was compiled with DFTACTGRP(*YES) or withACTGRP(aaaaaa).
"calllevel", so CRTBNDRPG is affected from OVRDBF.
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
When PGM1 runs in a named Activation Group, the scope is "activation grouponly",
so if CRTBNDRPG runs in a specific Activation Group (or in the DAG) isn'taffected from OVRDBF.
instruction.
I solved my problem specifying OVRSCOPE(*CALLLVL) on the OVRDBF
information....
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
not in the DAG.
Furthermore...
We are modifying our programs to run them in Named Activation Group and
But this operation can produce some problem...OVRSCOPE(*CALLLVL) on all the OVRDBF.
for example OVRDBF scoping... To avoid THIS problem I must specify
the DAG can't be "replaced" in a Named AG...
My question is.... how many other problem can I get?
I found some difference in "closing" program... The RCLRSC LVL(*CALLER) in
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
As an Amazon Associate we earn from qualifying purchases.
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.