|
It don't look good Kemosabe. Do a WRKPTFGRP and paste the results According to http://publib.boulder.ibm.com/iseries/v5r3/ic2924/index.htm?info/rzala/rzalafinder.htm a sqlcod of -901 matches SQL0901 which is the same message as the last message in your joblog. SQL system error. Gotta boogie out for the night. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com fkany@xxxxxxxxxxxxxxxxxx Sent by: rpg400-l-bounces@xxxxxxxxxxxx 04/06/2005 04:07 PM Please respond to RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx> To CN=RPG programming on the AS400/O=iSeries <rpg400-l@xxxxxxxxxxxx> cc Subject RE: SQLRPGLE help/advice/direction SQLCOD = 0 after OPENing cursor SQLCOD = -901 after FETCH Field Values: XFHOT OF SQLDATA = 404. XFHPRO OF SQLDATA = 4040404. XFHDDAT OF SQLDATA = 04040404. XFHDTIM OF SQLDATA = 0404. XFHDT OF SQLDATA = 404. XFHDADT OF SQLDATA = 04040404. XFHPUDT OF SQLDATA = 04040404. XFHSCD OF SQLDATA = ' ' XFHCCD OF SQLDATA = ' ' XFHCCT OF SQLDATA = ' XFHCZIP OF SQLDATA = ' ' Job Log: 8600 - CALL PGM(FR47R457) /* The CALL command contains parameters */ Unable to retrieve query options file. Unable to retrieve query options file. CONNECT to relational database AEPROD completed. Current connection is to relational database AEPROD. Unable to retrieve query options file. **** Starting optimizer debug message for query . All access paths were considered for file FRL00144. Additional access path reason codes were used. Unable to retrieve query options file. **** Ending debug message for query . ODP created. Blocking used for query. Cursor SQLDATAINPUT opened. File QAP0ZDMP created in library QTEMP. Member QP0Z452473 added to file QAP0ZDMP in QTEMP. User Trace data for job 452473/FRANK/QPADEV00HL dumped to member QP0Z452473 in file QAP0ZDMP in library QTEMP. 27 records copied from member QP0Z452473. 1 User Trace buffer(s) deleted. SQL system error. rob@xxxxxxxxx@midrange.com on 04/06/2005 03:34:48 PM Please respond to RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx> Sent by: rpg400-l-bounces+fkany=averittexpress.com@xxxxxxxxxxxx To: RPG programming on the AS400/iSeries <rpg400-l@xxxxxxxxxxxx> cc: Subject: RE: SQLRPGLE help/advice/direction Good idea. Also check your SQLCOD after opening the cursor and after the fetch. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com "Haas, Matt" <Matt.Haas@xxxxxxxxxxx> Sent by: rpg400-l-bounces@xxxxxxxxxxxx 04/06/2005 03:15 PM Please respond to RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx> To "RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx> cc Subject RE: SQLRPGLE help/advice/direction Frank, What's in the job log? If you were in debug mode (you don't have to debug the program, keying in STRDBG UPDPROD(*YES) works) when you ran the program, you'll see SQL debugging messages in your job log that may point you in the right direction. Matt -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of fkany@xxxxxxxxxxxxxxxxxx Sent: Wednesday, April 06, 2005 4:14 PM To: CN=RPG programming on the AS400/O=iSeries Subject: SQLRPGLE help/advice/direction My SQLRPGLE program compiles, but there is not data in the multiple occurence data structure after the RTV_CSR_IN routine. Is there a problem with my SQL code? Thanks, Frank <snip> -- This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.
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.