• Subject: RE: AS/400 Tips & Techniques - December 1997 News/400
  • From: "Leland, David" <dleland@xxxxxxxxxx>
  • Date: Fri, 12 Dec 1997 14:23:30 -0500

Nope.

>----------
>From:  Jon Erickson[SMTP:jonerickson@vikingindustries.com]
>Sent:  Friday, December 12, 1997 10:53 AM
>To:    'MIDRANGE-L@midrange.com'
>Subject:       RE: AS/400 Tips & Techniques - December 1997 News/400
>
>Are you using SHARE(*YES) in the OVRDBF?  Just a thought.
>
>Regards,
>-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>Jon A. Erickson - Viking Industries
>jonerickson@vikingindustries.com
>-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>
>
>-----Original Message-----
>From:  John Carr [SMTP:74711.77@compuserve.com]
>Sent:  Thursday, December 11, 1997 7:32 PM
>To:    Midrange-L
>Subject:       AS/400 Tips & Techniques - December 1997 News/400
>
>
>Date:  12/11/97  7:43 PM
>
>RE:    AS/400 Tips & Techniques - December 1997 News/400
>
>>I was implementing a tip in the December 1997 News/400 magazine on
>>creating a service program wrapper over QCMDEXC (pg. 65) when I came
>>across a strange situation.  The procedure works fine for every command
>>I've tried except for an override data base file (OVRDBF).  Everything
>>runs and the procedure completes fine, however, the override is never in
>>effect after executing the procedure.  I suspect it's related to the
>>program call level.
>>
>>Any thoughts, or am I just missing something?
>>
>>Thanks,
>>Dave
>
>I believe what you found out is why a QCMDEXEC with an OVRDBF called
>from an RPG program will effect the the RPG program that subsequently 
>does an OPEN.  
>
>By this I mean that the QCMDEXEC runs at the same invocation as the 
>of the program it is called from.  If you call a CL program from an
>RPG that does an OVRDBF and then returns to the RPG program, the 
>OVRDBF is gone.  Thus the reason to do the override using QCMDEXEC
>from RPG.  Thus your problem. 
>
>I probably made this as clear as mud.
>
>But there it is.
>
>John Carr      
>EdgeTech
>
>+---
>| This is the Midrange System Mailing List!
>| To submit a new message, send your mail to "MIDRANGE-L@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
>+---
>
>+---
>| This is the Midrange System Mailing List!
>| To submit a new message, send your mail to "MIDRANGE-L@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
>+---
>umidr
>
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@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
+---


This thread ...


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

This mailing list archive is Copyright 1997-2019 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 here. If you have questions about this, please contact [javascript protected email address].