OVRDBF, OPNQRYF, OVRSCOPE and OPNSCOPE mystery...

[DShea]

I was at a JDE client recently and ran across a situation that I hope
someone here can shed some light on.

The standard, textbook procedure for doing an OPNQRYF before calling an RPG
program is as follows:

OVRDBF FILE(FILE1) SHARE(*YES)
OPNQRYF FILE((FILE1)) QRYSLT(.....)

However, at this particular site the OVRDBF command needed OVRSCOPE(*JOB)
and OPNSCOPE(*JOB) parameters specified and the OPNQRYF command needed
OPNSCOPE(*JOB) specified in order for the OPNQRYF to work properly.

I'm curious how common this might be. It's unclear to me whether this
situation exists on this particular machine due to OneWorld, or some other
product the client has installed.

Does anyone have any insight on this situation? I had to do a fair amount
of tinkering to get some standard OPNQRYFs to run properly.

++++++++++++++++++++++++++++++++++++++++++++
Go... FASTER! Without an upgrade! With ARCTOOLS/400(tm)
http://www.arctools.com
[email protected]
DCSoftware, Inc.
Ph: (508) 435-8243
Fax: (508) 435-4498
++++++++++++++++++++++++++++++++++++++++++++

 

[Tom_Davidson]

DShea,


This is a common occurance when using both ILE and non-ILE programs. For
the most part I use the OVRSCOPE(*JOB), but I also DLTOVR as soon as
possible.

The bottom line is that if you don't use *JOB, it is up to you to ensure
both the program issuing the OVRDBF/OPNQRYF and the program actually using
the file are in the same activation group.

HTH

Tom Davidson
Xe Update 1, SP 16.1, ES: AS/400, CO: SQL, TSE, Multiple instance
(english/western european, japanese)





OW 7332 SP 11.3VER, NT 4.0 SP 5, TSE 4.0 SP 4, Metrframe 1.8, CO SQL 7.0