Re: [Bulk] Re: SQL - Limit and Offset Not Working

Thanks!

This is what it shows:

PTF_GROUP_CURRENCY PTF_GROUP_ID PTF_GROUP_TITLE

UPDATE AVAILABLE SF99709 710 Group Hiper
UPDATE AVAILABLE SF99708 710 Group Security
UPDATE AVAILABLE SF99368 710 IBM HTTP Server for i
UPDATE AVAILABLE SF99705 710 Hardware and Related PTFs
UPDATE AVAILABLE SF99572 710 Java
UPDATE AVAILABLE SF99706 710 High Availability for IBM i
INSTALLED LEVEL IS CURRENT SF99145 710 Performance Tools
INSTALLED LEVEL IS CURRENT SF99367 710 TCP/IP PTF
INSTALLED LEVEL IS CURRENT SF99369 710 IBM i integration with BladeCenter and System x
INSTALLED LEVEL IS CURRENT SF99617 710 DB2 Web Query for IBM i V1.1.1
INSTALLED LEVEL IS CURRENT SF99627 710 7.1 Electronic Services Group PTF
INSTALLED LEVEL IS CURRENT SF99637 710 DB2 Web Query for IBM i V1.1.2
INSTALLED LEVEL IS CURRENT SF99707 710 Technology Refresh

On 3/7/2016 11:57 AM, Mark S Waterbury wrote:

Brian:

In STRSQL or your iNav "Run SQL Scripts" window, run the following query:

SELECT * FROM SYSTOOLS.GROUP_PTF_CURRENCY
ORDER BY PTF_GROUP_LEVEL_AVAILABLE - PTF_GROUP_LEVEL_INSTALLED DESC

This will tell you what PTF groups you have and which ones are "current" ...

If it does not run at all, you are "way behind" on your DB2 Group PTFs.

HTH,

Mark S. Waterbury

> On 3/7/2016 11:49 AM, Brian wrote:

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