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



Thanks Scott, I will look into this.

-----Original Message-----
From: Scott Klement [mailto:midrange-l@xxxxxxxxxxxxxxxx] 
Sent: Monday, November 20, 2006 2:42 PM
To: Midrange Systems Technical Discussion
Subject: Re: very strange issue with batch job


Simple cl containing a very simple OPNQRYF statement and an OVERDBF
SHARE(*YES).  Program was working for weeks, then for about 2 hours
when
the program would be submitted to batch it was ignoring the OPNQRYF
and
selecting all records... but if I submit on hold, then copy paste the
call on the command line it works fine, when I release... it selects
all
records in the file or skips the opnqryf or ignores the SHARE????

Both the OVRDBF command and the OPNQRYF command have a paramter called 
"OPNSCOPE".  This parameter determines which programs in the job will be

affected by the override/open and which ones won't.

The default value is *ACTGRPDFN which means that the override scope is 
defined by the activation group that the command is run from.  If it's
run 
from the default activation group, then the scope is based on the 
call-level. When run from a different activation group, the scope is
that 
activation group itself.

This means that if you call it from the command line (which is always
the 
default activation group) the override and opnqryf will affect any 
programs that you call until you use CLOF/DLTOVR, or end the current 
call-stack entry (i.e. exit the command-prompt that you're running, such

as when you sign off, or if you typed CALL QCMD, when you exit that
call, 
etc.)

If you call it from an ILE CL program that's running in a genuine ILE 
activation group, however, the ovrdbf/opnqryf will only affect programs 
that happen to be in the same activation group.

Try changing the OVRDBF command to specify OVRSCOPE(*CALLLVL) and the 
OPNQRYF command to specify OVRSCOPE(*JOB).  That seems to be the way you

expect it to work, so you might as well code it that way :)





Important Confidentiality Notice: This email message, including all attachments 
is for the exclusive use by the person(s) 
to whom it is addressed, and may contain information that is confidential or 
privileged. Any unauthorized review, use, 
disclosure or distribution is prohibited under applicable law. If you have 
received this email in error, please notify me 
immediately by reply email and delete this message and any attachments. Thank 
you.



As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.