× 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: dynamic embedded SQL
  • From: "R. Bruce Hoffman, Jr." <rbruceh@xxxxxxxxxxxxx>
  • Date: Wed, 28 Jun 2000 20:21:04 -0400

-----Original Message-----
From: Erick Garske <erick@formationmg.com>
To: midrange-l@midrange.com <midrange-l@midrange.com>
Date: Wednesday, June 28, 2000 6:57 PM
Subject: dynamic embedded SQL


>I have an issue with a dynamic embedded SQL statement within an RPG
program.
>When I compile and test the program on a development machine, the code
works
>correctly. When I send the program out to another machine, the code does
not
>work correctly. The program was generated using V4R4 but compiled to a
>target release of V4R3. The other machine is at V4R3.
>
>The compile options used for V4R4 are:
>
>COMMIT(*CHG) and RDB(*NONE)
>
>Does anyone have any idea what could be wrong?
>


What is the value of the dynamic user profile parameter during the compile?
It can be *OWNER or *USER.  In either event, then, what is the authority of
the target systems, user or owner profile to the file?


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