|
Colin, I ended up going a different route based on a comment from Scott Klement. We just had some training with Jon Paris and Susan Gantner and based on that you should be able to specify OVRSCOPE(*JOB) with OPNSCOPE(*JOB) and get the desired results no matter what is going on in AG's further down the line. Please correct me if I am wrong. Aaron Bartell -----Original Message----- From: Colin Williams [mailto:colin.williams@bertrams.com] Sent: Thursday, February 06, 2003 3:42 AM To: 'rpg400-l@midrange.com' Subject: RE: Activation Groups, external sub procedures, and OVRDBF -----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 _______________________________________________ This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@midrange.com 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-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.