RE: SQL create view statement too long or complex

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-
bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Wednesday, October 23, 2013 5:35 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: SQL create view statement too long or complex

On 10/23/13 1:48 PM, Koester, Michael wrote:

CREATE VIEW DEVLIB/V_InternetProfiles FOR SYSTEM NAME V_INETPRFS

I rather like the "FOR SYSTEM NAME" clause as the alternative to the
V_INT00001 name that we get without it. Except that I can't get the
Great View Creator to play along. Keyword FOR not expected... Was

that

capability provided through a recent PTF that our SysAdmin might have
missed? (InfoCenter document has that reference surrounded by
chevrons). If that's the case, does anyone know of what PTF group I
should suggest he acquire?

The following web search identifies APAR SE54542 as the add-function
PTF:
https://www.google.com/search?q="for+system+name"+"syntax"+"PTF";

The following link to that APAR shows the latest PTF in the chain,
as of 2013-06-19 apparently, is R710 SI50058; a PTF that is not on a
cumulative:
www.ibm.com/support/docview.wss?uid=nas2e0985d0ce41ffd8a86257af50041fa0
0

TWiMC, that superseding PTF is also an add-function, providing
REFFLD support for retrieved\generated SQL [QSQGNDDL API] via APAR
SE55612.
And another superseded change corrected [I infer, that new] support for
GTT names. There also may be a fix to a defect for creating an MQT
that was introduced by the support for the FOR SYSTEM NAME clause....
so, as is generally the case, and why the latest PTF is listed, best to
get the latest rather than ordering the original\minimal code-level
that provided the initial change\ADDF. That is, best not to order the
old\original PTF[s] SI49110 [SI49111 and SI49112].

--
Regards, Chuck
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-
L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.