Re: JOIN USING problem

On 04 May 2012 15:13, CRPence wrote:
On 04 May 2012 15:00, Jonathan Ball wrote:
<<SNIP>> upgrade to V6R1 <<SNIP>>

I am running into a different problem at compile time. If I have the
schema (library) containing the tables in my library list at compile
time, the SQL precompiler throws an error SQL0203 saying that one of
the common columns (col3 or col4) is "ambiguous." This is exactly
why the columns had to be qualified with the table alias at V5R4.
However, if I qualify the column as as above, to remove the
ambiguity, the precompile fails as well.

This seems like a bug to me. Has anyone else encountered it?

https://www.google.com/search?q=msgsql0203+join+using


Sorry, I had to do a "force quit" multiple times on my browser when looking at the PSP document for v7r1m0, found in the above web search, so initially I just sent the above.

If the PTF level is already c1256610 and\or latest DB Fixpack [i.e. SI42050 applied or superseded], then my SWAG is that very probably the v7r1 APAR SE50797 "OSP-DB-OTHER-MSGSQL0203 REFERENCING A FIELD IN A JOIN USING CLAUSE" which appears on the IBM i 7.1 PSP is likely going to have a corresponding APAR for IBM i 6.1; i.e. perhaps what got that fix in the 7.1 PSP listing, would be the same origin in the prior release, and similarly require a "replacement" PTF.

Seems the v6r1 APAR SE46048 "OSP-DB-OTHER-MSGSQL0203 OSP-DB-OTHER-MSGSQL0203" giving SI42050 correlates to the v7r1 PTF SI42092 [on C1116710] for APAR SE46048. The latter was the PTF that was replaced in v7r1 with PTF SI43721 for SE50797. If so, such a v6r1 PTF may exist already, available for test; unavailable on the web, as would be the case for the new APAR for different version of the OS. Regardless, probably best to call your service provider; probably ask directly if such a [test] PTF is available from a 6.1 APAR [as a SYSROUTE] from the 7.1 APAR SE50797.

Regards, Chuck
.

Relevant Pages

  • RE: [IBM-MAIN] Heads Up - LE PE - PK15432
    ... As I read the examples in the APAR it was broken and is now fixed ... would match before the PTF and still match now. ... IBM support on this one, finally got them to fess up that this behavior ...
    (bit.listserv.ibm-main)
  • Re: apar say ptf is PE
    ... Jim McAlpine wrote: ... *APAR information* APAR number PK34517 Reported component name DB2 OS/390 ... PE YesPE HIPER YesHIPER Special Attention NoSpecatt Submitted date ... PTF UK21071 fixes APAR PK34517. ...
    (bit.listserv.ibm-main)
  • Re: PTF 0A05281 information.
    ... It's an APAR not a PTF. ... Reported component name DFSMS/MVS VSAM ... Subject: PTF 0A05281 information. ... PTF 0A05281 the first character is a ZERO and should be an "O" instead. ...
    (bit.listserv.ibm-main)
  • Re: Dynamic PAV assigment has stopped
    ... UNABLE TO BIND PAV DEVICES FOLLOWING AN ACTIVATE FAILURE ... APARCLOSURE - APAR is being closed. ... PE PTF List: ... if only PAV Aliases of the unbound traditional type ...
    (bit.listserv.ibm-main)
  • Re: PTF 0A05281 information.
    ... In IBMLINK, click on "work with document" in the menu on the right, then enter the APAR or PTF number you want. ... IBMLINK in Brazil may look somewhat different from the version we use in the US, but you should be able to find either. ... For IBM-MAIN subscribe / signoff / archive access instructions, ...
    (bit.listserv.ibm-main)