×
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.
Brown, Stephen GRNRC wrote:
Has this something to do with fact my trigger program is compiled with
ACTGRP *CALLER.
ACTGRP shouldn't matter at all, since your override is
OVRSCOPE(*CALLLVL) -- which means the activation group is not related to
the override scope.
ACTGRP(*CALLER) is the right value for a trigger, because if you use
commitment control, you want the trigger to run in the same commitment
definition as the program that's writing the records. But, that
shouldn't have any impact on overrides...
I don't know why this is happening... you run the OVRDBF and 4 lines
later (in the same program/same call level/same activation group), the
override is missing. That doesn't make sense.
Are you sure there's no condition where the override might not have been
executed, but the DLTOVR is being executed?
I'm curious as to why you do the ovrdbf/dltovr all the time, but only do
the OPEN if the file isn't already opened. What good does that do? The
OVRDBF only affects the OPEN statement, right? So why not have the
OVRDBF and DLTOVR conditioned by the same "if not %OPEN" group? Sorry
-- nothing to do with the problem, it just struck me as odd.
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.
midrange.com
