|
I placed the SQLCA in a /copy member and the verify now works great. But, it causes the compile to fail because the SQLCA winds up being defined twice. Another problem I have run into is with the Put to Host option. It seems to put to host only if the date on source member is not the current date. Is this how this behaves? Phil -----Original Message----- From: owner-code400-l@midrange.com [mailto:owner-code400-l@midrange.com]On Behalf Of John Taylor Sent: Friday, May 18, 2001 2:57 PM To: CODE400-L@midrange.com Subject: Re: Verify and SQLRPGLE The verifier(?) always kicks up errors because it doesn't pull in the SQLCA. I know that I could define it myself and stick it in a /Copy member, but I haven't bothered because the precompiler on the 400 does it automatically. ----- Original Message ----- From: "Chris Nickchen" <CNickchen@aind.com> To: <CODE400-L@midrange.com> Sent: Friday, May 18, 2001 12:33 Subject: Re: Verify and SQLRPGLE > > It does for us. > +--- | This is the CODE/400 Mailing List! | To submit a new message, send your mail to CODE400-L@midrange.com. | To subscribe to this list send email to CODE400-L-SUB@midrange.com. | To unsubscribe from this list send email to CODE400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: larry@paque.net +--- _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com +--- | This is the CODE/400 Mailing List! | To submit a new message, send your mail to CODE400-L@midrange.com. | To subscribe to this list send email to CODE400-L-SUB@midrange.com. | To unsubscribe from this list send email to CODE400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: larry@paque.net +---
As an Amazon Associate we earn from qualifying purchases.
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.