• Subject: Re: SQLRPG Question (as Survey for AS/400 Developers (ISERIES) DB2/400)
  • From: DAsmussen@xxxxxxx
  • Date: Wed, 1 Nov 2000 00:03:16 EST


In a message dated 10/30/00 9:15:47 PM Eastern Standard Time, Kaynor@aol.com 

> I'm not very knowledgeable about SQLRPG and I'm curious--my cohorts who use 
>  it say that SQLRPG programs must be recompiled over the exact datafiles 
>  will be run against.  

Well, as always, it depends.  What do you mean by recompiled?  Had you said 
compiled, I would have said that this statement was pure balderdash.  
Recompiled is a different animal entirely.

>  Can someone explain to me why, and whether there is a way to compile an 
>  SQLRPG program so that it can safely use unqualified file names?  I'd like 
>  be able to change the library list to run these programs over a different 
>  (e.g. Test) data library!

As far as "qualification", there are no more options in CRTSQLRPG than there 
are in CRTRPGPGM.  The only file option is to switch to COMMIT(*NONE) if 
you're not running journaling on the desired database.

>  We have not used SQLRPGLE.

Same difference.



Dean Asmussen
Enterprise Systems Consulting, Inc.
Fuquay-Varina, NC  USA
E-mail:  DAsmussen@aol.com

"There is something fascinating about science. One gets such wholesale 
returns of conjecture out of such a trifling investment of fact." -- Mark 
| 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

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 on our policy page. If you have questions about this, please contact [javascript protected email address].