Re: Level check using CREATE TABLE AS (SELECT

[Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>]

Yep, Chuck - if I were able, I'd do that immediately. It's not that much 
to replace a READE loop with a FETCH loop.

But I'm just offering ideas at this time.

Thanks
Vern

On 3/1/2013 1:51 PM, CRPence wrote:
>     Perhaps [also] consider replacing with SQL, whatever processing
> currently is requiring that the matching record format level
> identifier.?  That would certainly avoid a level check :-)
>
> Regards, Chuck
>
> On 01 Mar 2013 11:34, Vernon Hamberg wrote:
> > Actually the combination of RCDFMT with original format name
> > and all 4 INCLUDINGs did the trick - very neat!
> >
> > > <<SNIP>>
> > > On 3/1/2013 11:43 AM, Charles Wilt wrote:
> > > > CREATE TABLE <..> AS (SELECT <...>)
> > > >   <<SNIP>>
> > > > Certainly, you'd want the copy options
> > > > INCLUDING IDENTITY COLUMN ATTRIBUTES
> > > > INCLUDING COLUMN DEFAULTS
> > > > INCLUDING IMPLICITLY HIDDEN COLUMN ATTRIBUTES
> > > > INCLUDING ROW CHANGE TIMESTAMP COLUMN ATTRIBUTES
> > > >
> > > > <<SNIP>>
> > > >
> > > > On Fri, Mar 1, 2013 at 12:23 PM, Vernon Hamberg wrote:
> > > >
> > > > > I have looked around some, to find a solution. We have a
> > > > > process that is creating a duplicate of a table with selected
> > > > > columns <ed: ¿rows?> into QTEMP.
> > > > > <<SNIP>>