RE: GLOBAL TEMPORARY TABLE issues

Yes I know, but our standards for source limit what type of source is
used to create objects (for the moment).  The only other way to get a
non-DDS based object into Aldon (for us) is to make it non-source based.


Thanks, Matt


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Wilt, Charles
Sent: Monday, March 27, 2006 5:58 AM
To: RPG programming on the AS400 / iSeries
Subject: RE: GLOBAL TEMPORARY TABLE issues

> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx 
> [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Tyler, Matt
> Sent: Friday, March 24, 2006 11:38 AM
> To: RPG programming on the AS400 / iSeries
> Subject: RE: GLOBAL TEMPORARY TABLE issues
<snip>
> 
>       The solution we need must be compatible with our CMS product
> from Aldon.  So, during promotion time the model file object 
> must exist
> because all promotions to the next environment must be done in batch.
> We do not want to build special exit program processing just for this
> one instance.  We could create the model file using SQL and add it to
> Aldon as a non-source based object, but as I said before our current
> standard is to use DDS only for files.  
> 

Matt,

Why would you need to create the object as non-source based in Aldon?

Unless you're on a really old version of Aldon, Aldon supports SQL
objects, *TABLE, *VIEW, *INDEX, *FUNCTN, *PROC, and *TRIGGER as pseudo
source objects.  You can check them out, edit, create, and promote them
just like DDS defined *FILEs.

HTH,

Charles