|
Vern,
No STRSQL command for this release - but there it is in the libraries for two
prior releases. I am SO tempted to just copy it to current - but, who know what
kind of problems I'd create. I'll leave that to our operations staff - oh, wait
a minute, we don't have one for the 400! No kidding. They do backups and tell us
about messages - that's about it. The only one who knew some stuff is on
extended sick leave.
And, what a surprise - no iSeries Navigator. I think I had it installed once
when the person who is out sick installed it for me, but got it removed. Forgot
why.
Thanks for taking the time.
Fran Denoncourt
Sr. Programmer/Analyst
Pinal County Treasurer's Office
Florence, AZ 85232
(520) 866-6404
Receipt of this message does not grant you permission to send me
Unsolicited Commercial Email
Frances08/27/2008 3:19 PM >>>
Glad to see you moving this way - too bad you don't have a current license of
SQL. Are you able to use STRSQL on this box? If so, you should see about getting
the installation checked, cuz STRQM is part of the same thing.
As to you statement, you have one GROUP BY field - that one should be in the
field list - but all other items in the field list need to be aggregate kinds of
things - AVG(somefield), COUNT(otherfield) - like that. So you can't use *
because there'd be a bunch of just plain fields - can't do that.
By the way, you should be able to use the SQL statement processor in Navigator -
to test the statements. Then paste them into QMQRYSRC - just remember to take
off the trailing semi-colon.
HTH
Vern
-------------- Original message --------------
From: "Frances Denoncourt"
As many of you suggested earlier, I am trying to switch from query/400 (or--
whatever it is these days) to Query Management queries.
I cannot use STRQM because the command is only in two prior release libraries.
But, that's not the issue at the moment.
I'm following examples in the SQL Reference manual for small tests.
SELECT WORKDEPT, AVG(SALARY)
FROM EMPLOYEE
GROUP BY WORKDEPT
ORDER BY 2
and this example:
SELECT PROJNAME, PRSTDATE, PRENDATE
FROM PROJECT
ORDER BY PRENDATE DESC
My source is (I tried using Select * which didn't work either):
SELECT RPPRCL, RPYEAR, RPBTCH, RPNAME, RPREFA, RPCHCK, RPAPYR
FROM TXOVRPP
WHERE RPNAME = &NAME OR RPREFA > &NEGAMT AND RPREFA < &POSAMT
OR RPPRCL = 'B018034101'
GROUP BY RPPRCL
ORDER BY RPPRCL
I am calling it via a CL which worked for other examples.
This is the error I am getting - it's not consistent with the example from the
manual.
Any ideas which is the problem? thanks
Message ID . . . . . . : SQL0122 Severity . . . . . . . : 30
Message type . . . . . : Diagnostic
Date sent . . . . . . : 08/27/08 Time sent . . . . . . : 11:27:30
Message . . . . : Column RPYEAR or expression in SELECT list not valid.
Cause . . . . . : One of the following has occurred:
-- The statement contains column name RPYEAR and a column function in the
SELECT clause and no GROUP BY clause is specified,
-- Column name RPYEAR is specified in the SELECT clause but not in the
GROUP BY clause.
-- An expression is specified in the SELECT clause but not in the GROUP BY
clause.
-- The RRN, PARTITION, NODENAME, or NODENUMBER function is specified in
the SELECT clause with a column function or a GROUP BY clause.
-- A column or expression that is specified in the ORDER BY clause, but
not in the SELECT clause, does not conform to the grouping rules listed
above.
Recovery . . . : Do one of the following and try the request again:
-- If a GROUP BY clause is required, make certain that all columns or
expressions in the SELECT list and ORDER BY clause are also in the GROUP BY
clause. Do not specify the RRN, PARTITION, NODENAME, or NODENUMBER function.
-- If a GROUP BY clause is not needed, the SELECT list and ORDER BY clause
should not contain column functions with column names or the RRN, PARTITION,
NODENAME, or NODENUMBER function.
Fran Denoncourt
Sr. Programmer/Analyst
Pinal County Treasurer's Office
Florence, AZ 85232
(520) 866-6404
Receipt of this message does not grant you permission to send me
Unsolicited Commercial Email
--
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.
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.
--
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.
midrange.com
