|
Maybe I'm over cautious, but I have been stung several times by OVRDBF that didn't have the OVRSCOPE set to *JOB and the program running away because the override was effective at that level.
When the OVRDBF was run from within the SAME PROGRAM?!I can understand that when you're new to ILE you don't understand that OVRDBF doesn't across activation group boundaries. But if it's the SAME PROGRAM, how could it possibly be in a different activation group? How can a program be in a different activation group than itself?
Or, for that matter, how could it possibly be at a different call stack entry than itself?
It's true that subprocedures do add new call stack entry levels, but if you're using a subprocedure you're not using DFTACTGRP(*YES). Consequently, the overrides are scoped to the activation group, and therefore will still work.
How on earth do you write your code that OVRDBF when run from within the SAME PROGRAM won't succeed without using OVRSCOPE(*JOB)
It's like using a sledgehammer to crack open a walnut.
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.
midrange.com
