Re: Aldon & Index Advisor Indexes

I apologize I didn't read what you were looking for. If you allow Index
Advisor to create the index in your library. You can then create the
object in ALDON as a non-source object. When you promote, it will take the
object with you. However, the names must match.


Personally, I prefer to use the PSEUDO source as you will be able to track
the changes made to it. Hence the reason for having a change management
system.




On Wed, Dec 5, 2012 at 8:19 AM, Michael Schutte <mschutte369@xxxxxxxxx>wrote:

Sam,

I haven't read the entire conversation I apologize if you already have
your answer. But the answer you are looking for is to create the ALDON
object like so.

CCHGOBJ Change Checked Out Object



Object . . . . . . . . . : CNSOLGRPI1





Release . . . . . . . . : ODW/WDLSBASE/ODWPROD

Developer . . . . . . . : MSCHUTTE



Type choices, press Enter.



Object type . . . . . . *INDEX + Type

Object attribute . . . . SQL + Attribute

Extended attribute . . . + Extension

Data option . . . . . : 2 1=Keep destination data,

2=Promote data, *=Default

Source option . . . . . 2 1=Source, 2=Pseudo source,
9=None
Source file . . . . : QDDSSRC

Source member . . . : CNSOLGRPI1

Source library group : 3

For task . . . . . . . . IT718 + Task name




Your source option is 2 (pseudo source). Like the others side you can
type your index in there.



The other option is to go ahead and allow Index Advisor create the index
then in aldon and press F22 from any menu. This is your more functions
screen. Option 14 is generate SQL DDL. You put in the database object,
library and object type. Then the source that you want it to be stored at.


On Tue, Dec 4, 2012 at 5:49 PM, Sam_L <lennon_s_j@xxxxxxxxxxx> wrote:

Jim,

Yes, I know about generating the SQL--sorry I didn't make that clear.
In fact, I had just gone through the exercise of tweaking one into what
Aldon LMi expects as pseudo code, which caused me to post the question.

I'm trying to talk myself into no source...

If I forget about source, and let Index Advisor create the index, I can
then just use the Aldon LMi load facility to enroll them in Aldon as
non-source objects. Aldon will them always keep track of them as
dependent objects as needed and promote them through the environments
for me.

If I need to change one, I check it out, which means I have an empty
index in my checkout library. Then I use the iNav GUI to alter the
index (hmmm - I haven't tried that on a index) and then let Aldon take
care of the promotion and distribution.

This seems like less work to me. Only downside I see is that I have to
educate my co-workers on how this works.

Maybe someone else can pick holes in this approach.

Sam

On 12/4/2012 6:49 AM, Jim Oberholtzer wrote:

Sam,

Instead of having index adviser create the index for you, use the "Show
SQL" option in the drop down(At V7 it's the third item)

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.