|
Nope...developing it right now. Thanks for the SQLPKG parameter...I'm having an issue now specifying the 'library' for the package on the Windows system. > -------- Original Message -------- > Subject: Re: SQLSTT = 51002 > From: rob@xxxxxxxxx > Date: Mon, February 06, 2006 11:30 am > To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> > > ...unless you moved the program from a development machine to a production > machine, which "may" be a problem. > > Rob Berendt > -- > Group Dekko Services, LLC > Dept 01.073 > PO Box 2000 > Dock 108 > 6928N 400E > Kendallville, IN 46755 > http://www.dekko.com > > > > > > rob@xxxxxxxxx > Sent by: midrange-l-bounces@xxxxxxxxxxxx > 02/06/2006 11:03 AM > Please respond to > Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> > > > To > Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> > cc > > Fax to > > Subject > Re: SQLSTT = 51002 > > > > > > > See CRTSQLPKG, which I thought should have been handled by the SQLPKG > parameter of the CRTSQLRPGI command. > > Rob Berendt > -- > Group Dekko Services, LLC > Dept 01.073 > PO Box 2000 > Dock 108 > 6928N 400E > Kendallville, IN 46755 > http://www.dekko.com > > > > > > michael@xxxxxxxxxxxxxxxxxx > Sent by: midrange-l-bounces@xxxxxxxxxxxx > 02/06/2006 10:48 AM > Please respond to > Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> > > > To > midrange-l <midrange-l@xxxxxxxxxxxx> > cc > > Fax to > > Subject > SQLSTT = 51002 > > > > > > > I'm trying to access a remote database (DB2 on Windows) using embedded > SQL and am receiving a SQLCOD = -000000805 and a SQLSTT = '51002'. > Looking that up in the handy SQL message document in Info Center, it > tells me that 'The package corresponding to an SQL statement execution > request was not found.' > > In my RPG program I'm doing a DECLARE CURSOR C1 FOR SELECT <blah>. I > then do an OPEN C1, and that's where I get the error. I'm doing a > CONNECT TO prior to the OPEN, and I connect with no errors. > > I can do this from Interactive SQL with no problems. > > Any ideas? Thanks... > > > -- > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > > > -- > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > > > -- > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.