See the memo to users. There is a note there about this SQL error message.
It's been a year, but that customer had to rework a boatload of SQL
statements due to taking shortcuts in the JOIN clauses.

Paul Nelson
Cell 708-670-6978
Office 512-392-2577
nelsonp@xxxxxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Oberholtzer
Sent: Monday, May 14, 2012 10:43 AM
To: Midrange Systems Technical Discussion
Subject: SQL error after upgrade to V7

A Client just upgraded to V7 over the weekend. (Test partition)

We recreated the Host server SQL Package QGPL/QZDAPKG but that did not
clear the problem and this SQL is beyond my ability to debug. Any clue
as to what might be wrong? It works well at V5R4.

SELECT
DMNAME,DMSOURCE,SRDESC,DMREV,DMDESC,DMSTATUS,STSDESC,DMORDER,DMOWNER,WGDESC,
DMASGN,DMCHECK,
(SELECT COUNT(*) FROM COWOC WHERE OCNAME = DMNAME) NOTE
FROM COWDOC,COWSR,COWSTS,COWWG,HDMCATS A
LEFT OUTER JOIN HDMCATS B ON (B.CAT = 'FILEICONS' AND B.IDX = 'FILEEXT' AND
B.IDXVAL = A.FILEEXT AND B.STS IN('A','K'))
LEFT OUTER JOIN COWOA ALERT1 ON (DMOA1 = ALERT1.OACODE)
LEFT OUTER JOIN COWOA ALERT2 ON (DMOA2 = ALERT2.OACODE)
LEFT OUTER JOIN COWOA ALERT3 ON (DMOA3 = ALERT3.OACODE)
LEFT OUTER JOIN COWOA ALERT4 ON (DMOA4 = ALERT4.OACODE)
LEFT OUTER JOIN COWOA ALERT5 ON (DMOA5 = ALERT5.OACODE)
WHERE DMSOURCE = SRSOURCE
AND DMSTATUS = STSCODE
AND DMOWNER = WGUSER
AND DMNAME = A.DOCID
AND DMSTATUS = 'N'
AND A.CAT = 'CUSTPO';


Error is:
SQL State: 42972
Vendor Code: -338
Message: [SQL0338] JOIN predicate or MERGE ON clause not valid.

It is highlighting the "ON (DMOA1 = ALERT1.OACODE)" portion of the
statement.


This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].