RE: GLOBAL TEMPORARY TABLE issues

SQL Tables, SQL Indexes, and logical files built over SQL Tables can have 
incorrect format level identifiers if the table contains timestamps.  This 
has been corrected for V5R3 and V5R4 with PTFs SI22347 and SI22348 
respectively.  Please see the coverletters for these PTFs for additional 
information.

Bruce Vining
 



"Tyler, Matt" <mattt@xxxxxxxxxxxxxx> 
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
03/24/2006 09:38 AM
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>


To
"RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>
cc

Subject
RE: GLOBAL TEMPORARY TABLE issues






Rob,
                 Thanks for the input and effort. Your testing has help 
prove
that there is a difference between creating a table via SQL and DDS.
Something I can't say I was consciously aware of. 

                 Our solution still needs to reside with using DDS as the 
source
language for file objects.  The programmer's final solution to creating
the temporary file was to use CRTDUPOBJ.  He thought he found a
solution, that allowed him one source and no QCMDEXC calls, in DECLARE
GLOBAL TEMPORARY TABLE.

                 I just wanted to know for fact why there existed a 
difference
between the model file and the temporary table and why the difference
only appeared when dates were used in the model file.  I wanted to be
able to tell others, here is the reason, so do it some other way. 


Thanks, Matt