Re: Level check using CREATE TABLE AS (SELECT

[Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>]

Hi Joel

I've not wanted to go that far, if there is an alternative. Although SQL 
knows nothing about level checks, it'd be hard to convince a seasoned 
developer that it's OK to do that.

:)

Vern

On 3/1/2013 2:53 PM, Stone, Joel wrote:
> Have you considered the obvious - OVRDBF FILE() LVLCHK(*NO) ?
>
> If it's a QTEMP file it should be pretty safe.
>
>
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vernon Hamberg
> Sent: Friday, March 01, 2013 11:24 AM
> To: Midrange Systems Technical Discussion
> Subject: Level check using CREATE TABLE AS (SELECT
>
> I have looked around some, to find a solution. We have a process that is
> creating a duplicate of a table with selected columns into QTEMP. The
> table has a couple timestamps, otherwise it is all ZONED and ALPHA.
>
> One of the timestamps is a ROW CHANGE TIMESTAMP.
>
> The format level ID is not the same as the table used in the SELECT.
> Both objects are SQL tables, so it's not a matter of one is an SQL
> object and the other is not.
>
> Now to have a simple example, I tried it with QIWS/QCUSTCDT, and the
> result is the same.
>
>        create table qtemp/mytest as (SELECT * FROM qiws/qcustcdt) with no
> data
>
> Fmt lvl ID for QCUSTCDT is 3B84438D4C428
>
> Fmt lvl ID for MYTEST is 449C8BB02A248
>
> At this time we are doing a single-record CPYF, then some overrides,
> then an INSERT with OVERRIDING SYSTEM VALUE clause.
>
> Is this just the way it is, or is there a PTF to take care of this? I do
> not yet have access to PTF info here. We ARE at 7.1 of the OS.
>
> Thx
> Vern