|
>> While that seems desirable at first blush, look at the default value for OPNQRYF: OPNSCOPE(*ACTGRPDFN). This is exactly the same default as OVRDBF, and has virtually the same help text wording. But it isn't the _same_ default. Any more than a default of *LIBL always means the exact same library list. The option *ACTGRPDFN has no meaning in and of itself. It means - in all cases - "the default depends on where the command is issued". If you look at the options for OPNQRYF there is no Call level option as such. Only Job and AG scope. The only way to get call level is when the command is issued in the default. When this stuff was being designed, the objective was to make it transparent to existing programs. That was the whole rationale behind the *ACTGRPDFN option. I think (but can't remember for certain) that one of the reasons why call level wasn't supported for OPNQRYF was that scoping had always been a major problem with the command (i.e. a major cause of support calls) and making an expensive change to OPNQRYF to further support a problem area wasn't considered a good idea. There were other technical reasons as well but I can't recall them. Jon Paris Partner400
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.