RE: SQLCODE -104

Thanks for the suggestion.

After removing both commas I am getting a new error:
Token + was not valid.  Valid tokens: ,  FROM  INTO.

After removing all  the +'s it worked great.

Thanks a bunch.  That did the trick.

Gary Kuznitz

On 21 Apr 2003 at 17:12, Kevin (Kevin Mohondro <midrange-l@xxxxxxxxxxxx>) 
commented about RE: SQLCODE -104:

> I'd say it's the comma after the GROUP BY or the comma after "DIRECTORY".
> Both of them need to go for that statement to be a valid SQL statement.
> 
> Kevin R Mohondro
> Programmer/Analyst
> Ashworth, Inc.
> 
> > -----Original Message-----
> > From: Gary Kuznitz [mailto:docfxit@xxxxxxxxxxxx] 
> > Sent: Monday, April 21, 2003 4:46 PM
> > To: Midrange Systems Technical Discussion
> > Subject: SQLCODE -104
> > 
> > 
> > Hi,
> > 
> > I'm trying to run SQL.  I'm getting an error saying:
> > Message . . . . :   RUN QUERY command failed with SQLCODE -
> > 104.              
> > Cause . . . . . :   The SQLCODE is -104. The SQLSTATE is 42601. 
> > The DB2 SQL  
> >   OS/400 message text for this error is: Token <END-OF-
> > STATEMENT> was not valid. Valid tokens: + - AS <IDENTIFIER>.  
> >                                 
> > 
> > The source statements in a source member are:
> > SELECT                                        +  
> >         COUNT(*) AS "NUMBER OF OBJECTS",                        +  
> >         SUM(CAST(ST_SIZE AS DEC(31))) AS "FILE SIZE",           +  
> >         SUM(CAST(ST_ALLOCSZ AS DEC(31))) AS "ALLOCATED 
> > SIZE",   +  
> >         SUBSTR(DIRNAME,1,200) AS "DIRECTORY",                   +  
> > FROM                                        +  
> >         QRYIFSLIB                                        +  
> > GROUP BY,                                        +  
> >               SUBSTR(DIRNAME,1,200)                                
> > 
> > I created the above source object with:
> > CRTQMQRY QMQRY(GARY1/IFSLISTRUN)  + 
> > SRCFILE(GARY1/QCLSRC) SRCMBR(IFSLISTQRY) 
> > 
> > I am runing it in a cl pgm with:
> > STRQMQRY   QMQRY(GARY1/IFSLISTRUN) 
> > 
> > Does anyone have any idea what might be causing this error?
> > 
> > TIA,
> > 
> > Gary Kuznitz
> 
> #############################################################################
> Attention:
> The information contained in this message and or attachments is intended
> only for the person or entity to which it is addressed and may contain
> confidential and/or privileged material.  Any review, retransmission,
> dissemination or other use of, or taking of any action in reliance upon,
> this information by persons or entities other than the intended recipient
> is prohibited. If you received this in error, please contact the sender and
> delete the material from any system and destroy any copies.
> 
> Thank You.
> #############################################################################
> _______________________________________________
> 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.cgi/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.
> 
>