RE: Activation Groups, external sub procedures, and OVRDBF -- RPG400-L

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

Subject: RE: Activation Groups, external sub procedures, and OVRDBF
From: Colin Williams <colin.williams@xxxxxxxxxxxx>
Date: Thu, 6 Feb 2003 09:42:14 -0000
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the AS400 / iSeries <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>,<mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>,<mailto:rpg400-l-request@midrange.com?subject=unsubscribe>


-----Original Message-----
Aaron

Are you just trying to get OVRDBF to work the way it used to before the
influence of Activation Groups. I had loads of trouble with OVRDBF working
and fiddle with ACTGRP(*CALLER), (*NEW) etc OVRSCOPE(*JOB)  (*ACTGRP) etc,
etc,, blah, blah blah.

The only sure fire way that I have found to get OVRDBF to work consistently
in the old way is to specify OVRDBF with the keyword OVRSCOPE(*CALLLVL).
This seems to have solved my problems with OVRDBF.

Cheers
Colin.W

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.