× 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.



Thanks all

I'm a bit embarrassed I didn't know about the prototype to qcmdexc. Great
idea.

Yes the program was compiled with Dftactgrp(*no) actgrp(*caller). It
is running in the default activation group. We will probably be in
"compatibility mode" for a long time. I am trying to setup a set of
rules/techniques that will work in as many situations as possible. Even
when something that has been converted may be called from an old S36 Proc.

Am putting a /copy spec into everything with the following directives.
h bnddir('QC2LE':'MIS_LIB/BNDDIR1') actgrp(*caller) dftactgrp(*no)

At some time in the future will work on the *caller technique and maybe
change it to qile and recompile everything in one big bang. will be
interresting. probably won't happen till v6 so should be able to put
compiler directives in the clle also.

Do I need to paste programs differently in my emails so they don't wrap so
poorly?

Jim Horn

------------------------------

message: 4
date: Fri, 10 Oct 2008 11:16:27 -0400
from: "Mark S. Waterbury" <mark.s.waterbury@xxxxxxx>
subject: Re: override scope in a procedure

Hi, Jim:

I suspect you are seeing this behavior because your program is running
in the default activation group (in "OPM compatibility mode").

Did you compile this RPG IV program with the CRTBNDRPG command, or
option 14 in PDM? If so, DFTACTGRP(*YES) is the default. Or, perhaps you
compiled this program and bound it with ACTGRP(*CALLER) and then it was
called from another program that was already running in the default
activation group?

This is important because you did not specify OVRSCOPE on the OVRDBF
command, so it defaults to OVRSCOPE(*ACTGRPDFN) -- see the help text for
this parameter value:

*ACTGRPDFN
The scope of the override is determined by the activation group of
the program that calls this command. When the activation group is
the default activation group, the scope equals the call level of the
calling program. When the activation group is not the default
activation group, the scope equals the activation group of the
calling program.

Notice that overrides with OVRSCOPE(*ACTGRPDFN) behave differently when
running in the default activation group than when running in an ILE
activation group.

Hope that helps.

Mark S. Waterbury

This email is intended only for the person or entity
to which it is addressed and may contain information
that is privileged, confidential or otherwise protected
from disclosure. If you are not the named addressee
or an employee or agent responsible for delivering
this message to the named addressee, you are not
authorized to read, print, retain copy, and disseminate
this message or any part of it. If you have received this
message in error please notify us immediately by email,
discard any paper copies and delete all electronic files
of this message.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.