|
If you say OVRSCOPE(*ACTGRPDFN) then an OVRDBF run in Activation Group "A" will not be applied to program calls in Activation Group "B". Since you said the CL and RPG IV are in different activation groups, the override from the CL will not work. Use *JOB for the ovrscope parm, and then make sure you delete the override when you're finished with it, perhaps in the same CL after you return from the call to the RPG IV program. -Bob Cozzi www.RPGxTools.com If everything is under control, you are going too slow. - Mario Andretti -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Lorraine Ford Sent: Friday, March 18, 2005 2:28 PM To: rpg400-l@xxxxxxxxxxxx Subject: OVRDBF problems when using debug in called bound program I have a strange error occurring. I have a bound program that when called by the originating RPGLE runs fine. However, if I try to debug the bound program, I start getting CPF4101 errors. Both programs are running out of a named activation group, but the CLLE is in a different activation group, the debug activation group (with a lower number, which is 55, while the other programs are in 57). I'm thinking the problem is somewhere in the midst of here but I'm not sure. The OVRDBF commands on all the files referenced in the bound program use the default value of *ACTDFNGRP for the override scope command. Any thoughts? Thanks, Lorraine -- This is the RPG programming on the AS400 / iSeries (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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.