|
How would I know if I've got all the "right" things applied?
When trying the "Run SQL Scripts" option from iNav, I did this: as a simple test:
select * from edportal.edclient order by cllib limit 5
Which returned this error:
SQL State: 42601
Vendor Code: -104
Message: [SQL0104] Token LIMIT was not valid. Valid tokens: FOR USE SKIP WAIT WITH FETCH OPTIMIZE. Cause . . . . . : A syntax error was detected at token LIMIT. Token LIMIT is not a valid token. A partial list of valid tokens is FOR USE SKIP WAIT WITH FETCH OPTIMIZE. 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. Recovery . . . : Do one or more of the following and try the request again: -- Verify the SQL statement in the area of the token LIMIT. Correct the statement. The error could be a missing comma or quotation mark, it could be a misspelled word, or it could be related to the order of clauses. -- If the error token is <END-OF-STATEMENT>, correct the SQL statement because it does not end with a valid clause.
On 3/7/2016 10:50 AM, Rob Berendt wrote:
In the Catholic world you have baptism, confession, communion,
confirmation and so on...
In IBM TR world MF99011 is like baptism and getting all the right groups
is more like confirmation.
So, MF99011 is like you're ready for the enhancements coming in group
ptf's like:
- TR Group
- DB2 Group
and so on.
In this case the DB2 Group is what's pretty important.
Rob Berendt
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.