|
Oh.... I'd open a PMR on that baby. Found a v4r5 PTF that mentions a problem with NOT LIKE. But nothing else. Sounds like a bug to me, not a syntax problem. What version of OS/400 are you on and do you have the latest cume and DB group PTFs loaded? Can you try it in STRSQL? What about "Run SQL Scripts" in iSeries Navigator? Charles Wilt -- iSeries Systems Administrator / Developer Mitsubishi Electric Automotive America ph: 513-573-4343 fax: 513-398-1121 > -----Original Message----- > From: midrange-l-bounces@xxxxxxxxxxxx > [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Jeff Crosby > Sent: Wednesday, June 22, 2005 3:10 PM > To: 'Midrange Systems Technical Discussion' > Subject: RE: SQL update make fields match > > > > "Frogger Array Template..." > > > > Huh? > > > > Where are you running these statements? > > RUNSQLSTM from command line. > > >From joblog: > > MCH1869 Escape 40 06/22/05 > 11:04:48.283272 ExSndPm > 000000 QQQQUERY QSYS *STMT > > To module . . . . . . . . . : QQQQUERY > > To procedure . . . . . . . : QQQQUERY > > Statement . . . . . . . . . : 16186 > > Message . . . . : Frogger Array Template had an error, The > error type is > > 24. > > Cause . . . . . : An error was found in Frogger Array > Template with an > > identifier X'0002'. The error type is 24, the current > frogger range number > > is 1, and the current bound number is 1. The low/high bound > indicator is 0, > > (0=low 1=high). The selection template identifier is located > in the header > > of each selection template and is used to distinguish > between the multiple > > selection templates that are allowed for any particular data > space. The > > error type definitions follow: Error Definition ----- > > -------------------------------------- 01 -- number of bytes > is too small > 02 > -- number of frogger ranges is zero 03 -- Invalid reserved area 04 -- > number > of key fields is zero 05 -- number of key fields exceeds the > number of > index > key fields 06 -- Invalid reserved area in frogger range 07 -- > key field > cannot be severed 08 -- low bound end truncation position is > larger than key > field 09 -- high bound end truncation position is larger than > key field 10 > -- one bound specifies is not null and the other specifies is > null. 12 -- > bound is null indicator contains an invalid value 13 -- bound > infinity > indicator contains an invalid value 14 -- bound exclusion > indicator contains > an invalid value 15 -- bound location value is invalid 16 -- > bound position > value is invalid 18 -- bound reserved area not all zeros 19 > -- bound > datatype does not match key field datatype 20 -- global > literal list > template not provided 21 -- invalid datatype for dynamic > substring selection > > And that's the end of that particular message. > > -- > Jeff Crosby > Dilgard Frozen Foods, Inc. > P.O. Box 13369 > Ft. Wayne, IN 46868-3369 > 260-422-7531 > > The opinions expressed are my own and not necessarily the > opinion of my > company. Unless I say so. > > > > -- > 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-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.