Re: Alt index to SQL keyed view

[Carlos <carlosir@xxxxxxxxxxxxx>]

Thanks Birgitta
It helps m we too
Best regards
Carlos


Sent from my iPhone

> On Nov 6, 2019, at 12:40 PM, Birgitta Hauser <Hauser@xxxxxxxxxxxxxxx> wrote:
>
> You cannot access an SQL Index with SQL. You only can access views. It it
> the query optimizer which decides if or whether and which indexes are used.
> If you created an index with enhanced indexing technologies (such as
> additionally generated key fields or where conditions) and you want to
> access these data, you either have to build the additional fields you need
> in the SELECT statement and/or add the where conditions to the SELECT
> statement.
> Much better however is to create a view with the appropriate information
> (additional key fields and where conditions) and access the view.
>
> Mit freundlichen Grüßen / Best regards
>
> Birgitta Hauser
>
> "Shoot for the moon, even if you miss, you'll land among the stars." (Les
> Brown)
> "If you think education is expensive, try ignorance." (Derek Bok)
> "What is worse than training your staff and losing them? Not training them
> and keeping them!"
> „Train people well enough so they can leave, treat them well enough so they
> don't want to.“ (Richard Branson)
>
>
> -----Original Message-----
> From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Justin
> Taylor
> Sent: Mittwoch, 6. November 2019 18:07
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
> Subject: Alt index to SQL keyed view
>
> I'm doing some legacy work and I need to replace an alternate index file.
> I'm trying to use a SQL keyed view
> (https://developer.ibm.com/articles/i-sql-indexs-and-native-io/).  It works
> fine in RPG record-level access, but SQL gives SQLSTATE 42851 (A referenced
> file is not a table, view, or physical file) and QRY/400 gives CPD4360
> (Queried file &1 in &2 not data base file or is an SQL derived key index).
>
> Is there a way around this, or do I have to create a DDS LF?
>
> TIA
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
> unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives at
> https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate link:
> https://amazon.midrange.com
>
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com