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


  • Subject: RE: OvErRiDeS -- question
  • From: Buck Calabro <mcalabro@xxxxxxxxxxxx>
  • Date: Wed, 21 Oct 1998 13:20:49 -0400
  • Organization: commsoft

On Wednesday, October 21, 1998 11:17 AM, Tim Truax 
[SMTP:ttruax@shiprps.com] wrote:
> If I put a file override in place at my interactive session and specify
> for
> the (OVRSCOPE) override scope -- *JOB, why can't I SBMJOB the specific
> program and it will refer to that override?  -- Better yet -- is there a
> way to do this without coding a CL ?

Basically, because the newly submitted job is, well, a new job!  Think of 
it as starting a new workstation session (not entirely accurate, but close 
enough...)  You wouldn't want workstation A's overrides, *LIBL, etc. to be 
propagated into workstation B's job, would you?  Same idea for submitting 
a batch job.

You *can* do the overrides in your RPG program via CALL QCMDEXC but I 
don't recommend it--poor error trapping/recovery.  A CL program is a small 
price to pay for a reliable app., IMHO.


Buck Calabro
Commsoft, Albany, NY
mailto:mcalabro@commsoft.net

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


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.