Solved

SQL0338 Error received on query

Posted on 2014-09-19
3
310 Views
Last Modified: 2014-09-19
I have an application executing this query that used to work in iSeries O/S V5R4, but no longer works in V7R1.  I understand IBM made a change to the way they handle joins in versions 6.1 and above, but can't figure out a way to get around the error.  Here is the query:

Select H.PONumber, H.CreationDate, H.BuyerID, H.VendorID,
            H.LDC, V.DBVen_Vendor_VName, Coalesce(DBVLo_Addr1,
            DBVen_Addr1) as DBVen_Addr1, Coalesce(DBVLo_Addr2,
            DBVen_Addr2) as DBVen_Addr2, Coalesce(DBVLo_Addr3,
            DBVen_Addr3) as DBVen_Addr3, Coalesce(DBVLo_Addr4,
            DBVen_Addr4) as DBVen_Addr4, Coalesce(DBVLo_City_Addr5,
            DBVen_City_Addr5) as DBVen_City_Addr5,
            Coalesce(DBVLo_State_Prov, DBVen_State_Prov) as
            DBVen_State_Prov, Coalesce(DBVLo_Postal_Code,
            DBVen_Postal_Code) as DBVen_Postal_Code, S.StatusDescription
            From PMFPOHeader H, PMFPODetails D, PMFPORevision R,
            PMFPOStatus S, DBAPVEN V Left Outer Join DBAPVLo VL On
            VL.DBVLo_Vendor = V.DBVEN_VENDOR and VL.DBVLo_Location_Code
            = H.VendorLocationCode Where H.PONumber = 1000 and D.PONumber
            = 1000 and H.VendorID = V.DBVEN_VENDOR and S.StatusID =
            H.Status Group By H.PONumber, H.CreationDate, H.BuyerID,
            H.VendorID, H.LDC, V.DBVEN_VENDOR_VNAME, VL.DBVLo_ADDR1,
            VL.DBVLo_ADDR2, VL.DBVLo_ADDR3, VL.DBVLo_Addr4,
            VL.DBVLo_City_Addr5, VL.DBVLo_State_Prov,
            VL.DBVLo_Postal_Code, DBVen_ADDR1, DBVen_ADDR2, DBVen_ADDR3,
            DBVen_Addr4, DBVen_City_Addr5, DBVen_State_Prov,
            DBVen_Postal_Code, S.StatusDescription

Ideas?
0
Comment
Question by:JJSystems
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 18

Expert Comment

by:Dave Ford
ID: 40332999
Ahh yes. I see it. You mixed "old-style" joins with "new style" joins.

old-style = joins using commas
new-style = explicitly using JOIN keyword

convert all your old-style joins to new-style joins and you should be ok.

HTH,
DaveSlash
0
 
LVL 18

Accepted Solution

by:
Dave Ford earned 500 total points
ID: 40333045
Something like this should work:

Select H.PONumber, 
       H.CreationDate, 
       H.BuyerID, 
       H.VendorID,
       H.LDC, 
       V.DBVen_Vendor_VName, 
       Coalesce(DBVLo_Addr1, DBVen_Addr1) as DBVen_Addr1, 
       Coalesce(DBVLo_Addr2, DBVen_Addr2) as DBVen_Addr2, 
       Coalesce(DBVLo_Addr3, DBVen_Addr3) as DBVen_Addr3, 
       Coalesce(DBVLo_Addr4,
       DBVen_Addr4) as DBVen_Addr4, 
       Coalesce(DBVLo_City_Addr5,
       DBVen_City_Addr5) as DBVen_City_Addr5,
       Coalesce(DBVLo_State_Prov, DBVen_State_Prov) as DBVen_State_Prov, 
       Coalesce(DBVLo_Postal_Code, DBVen_Postal_Code) as DBVen_Postal_Code, 
       S.StatusDescription
  From PMFPOHeader H
  join PMFPODetails D
    on D.PONumber = H.PONumber
  cross join PMFPORevision R
  join PMFPOStatus S
    on S.StatusID = H.Status
  join DBAPVEN V 
    on H.VendorID = V.DBVEN_VENDOR
  Left Outer Join DBAPVLo VL
    On VL.DBVLo_Vendor = V.DBVEN_VENDOR
   and VL.DBVLo_Location_Code = H.VendorLocationCode
 Where H.PONumber = 1000
 Group By H.PONumber,
       H.CreationDate,
       H.BuyerID,
       H.VendorID,
       H.LDC,
       V.DBVEN_VENDOR_VNAME,
       VL.DBVLo_ADDR1,
       VL.DBVLo_ADDR2,
       VL.DBVLo_ADDR3,
       VL.DBVLo_Addr4,
       VL.DBVLo_City_Addr5,
       VL.DBVLo_State_Prov,
       VL.DBVLo_Postal_Code,
       DBVen_ADDR1,
       DBVen_ADDR2,
       DBVen_ADDR3,
       DBVen_Addr4,
       DBVen_City_Addr5,
       DBVen_State_Prov,
       DBVen_Postal_Code,
       S.StatusDescription

Open in new window


I noticed that you didn't specify any join-criteria for table PMFPORevision, I assume you meant for it to be a cross-join.

I find it best to fully enter this century and abandon all old-style joins. They're much "clearer" and easier to code.

HTH,
DaveSlash
0
 

Author Closing Comment

by:JJSystems
ID: 40333454
Thank you!
0

Featured Post

Webinar: Aligning, Automating, Winning

Join Dan Russo, Senior Manager of Operations Intelligence, for an in-depth discussion on how Dealertrack, leading provider of integrated digital solutions for the automotive industry, transformed their DevOps processes to increase collaboration and move with greater velocity.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

November 2009 Recently, a question came up in the DB2 forum regarding the date format in DB2 UDB for AS/400.  Apparently in UDB LUW (Linux/Unix/Windows), the date format is a system-wide setting, and is not controlled at the session level.  I'm n…
Recursive SQL in UDB/LUW (you can use 'recursive' and 'SQL' in the same sentence) A growing number of database queries lend themselves to recursive solutions.  It's not always easy to spot when recursion is called for, especially for people una…
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit https://www.mail-signatures.com/articles/signature-templates/?sts=6651 If you want to manage em…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…
Suggested Courses

738 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question