Re: table not journaled

Thank you CR,
that WITH NC goes before the NOT NULL WITH DEFAULT)

am getting this error"

NC in *LIBL type *SQLUDT not found.


On Thu, Mar 6, 2014 at 6:28 PM, CRPence <CRPbottle@xxxxxxxxx> wrote:

On 06-Mar-2014 15:14 -0800, Hoteltravelfundotcom wrote:

I created a table to be used as a Data Warehouse table to our
reporting tool or even on the i. This is going to be refreshed
nightly. It will be used strictly in a reporting mode.
Do we need to be concerned about the Not Journal status?

Message ID : SQL7905
Message. . : Table DTAWHSO in PROJ_T1 created but was not journaled.
<<SNIP>>
Recovery . : The table was created, but until the table is
journaled, COMMIT(*CHG), COMMIT(*CS), COMMIT(*RS), COMMIT(*RR),
COMMIT(*UR), and COMMIT(*ALL) will not be allowed for table DTAWHSO.

The "Recovery" explains whether a concern is warranted; i.e. if an
isolation level other than NC [no-commit] is required, for any reason
when accessing the file [data; i.e. effectively just for DML, including
SELECT], then the data access will fail [with SQL7008]. To ensure a
SELECT does not operate with a commitment-control\isolation level other
than *NC, then use\append the WITH NC clause to the request.

--
Regards, Chuck
--
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.