|
Hi Marco, SQLCODE -104: A syntax error was detected at token &1. Token &1 is not a valid token. A partial list of valid tokens is &2. This list assumes that the statement is correct up to the token. The error may be earlier in the statement, but the syntax of the statement appears to be valid up to this point. Please check your statement in :PSQL or post it. It seems to be not correct. Mit freundlichen Gru?en / Best regards Birgitta "Shoot for the moon, even if you miss, you'll land among the stars." (Les Brown) -----Ursprungliche Nachricht----- Von: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]Im Auftrag von Marco Velazquez Gesendet: Dienstag, 7. Marz 2006 23:36 An: rpg400-l@xxxxxxxxxxxx Betreff: SQL ERROR in Batch I have a Report program that when run interactive it generates the report normally, but when run in batch it generates the following SQL error: [SQL0104] SQLCODE = -104 003 FOR WITH FETCH ORDER UNION OPTIMIZE SQLSTATE = 42601 C/EXEC SQL C+ CONNECT RESET C/END-EXEC * Prepare the SQL statement C/EXEC SQL PREPARE SEL FROM :PSQL C/END-EXEC c Exsr ErrorSr * Declare the SQL cursor to hold the data retrieved from the C/EXEC SQL DECLARE MYCSR CURSOR FOR SEL C/END-EXEC c Exsr ErrorSr * Open the SQL cursor. C/EXEC SQL OPEN MYCSR C/END-EXEC c Exsr ErrorSr * Make selection case-insensitive C/EXEC SQL C+ SET OPTION SRTSEQ = *LANGIDSHR C/END-EXEC c/EXEC SQL FETCH MYCSR INTO :DSFIELDS c/END-EXEC Any ideas? Thanks for you help, Marco. -- 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.