Journal receivers

[d***@yahoo.com]

Hello,

An application we are using accesses an iSeries (V5R2) via Odbc and
manipulates files through the SQL interface. Even though the
consultant has indicated that the application is not using journaling,
we are seeing the journal receivers getting huge, so we need to delete
them quite frequently.

My questions: How can we make sure that sql statements are running with
journaling off? Is it possible to turn off journaling for some
collections? (Sorry if the questions are naive; I am new to iSeries.)

[Saml]

Journaling is optional on DB2 for iSeries.

If a collection was created through SQL, then journaling has probably been
turned on by default.

If the application is using commit or rollback then journaling is required.

Otherwise the only use for journaling is roll forward or roll backward
recovery, or "who did what to whom and when" analysis. If you have no need
for either of these you can stop journaling.

Journaling is one on a per table (file in native iSeries parlance) basis.
Using the ENDJRNPF command will allow you to stop journaling a table.

If you really do need journaling only for commit or rollback, you can set
the journal to system managed and when it reaches a specified size, a new
journal will be attached and, if you so specify, the old journal will be
deleted. See the CHGJRN command.

Sam

Post by d***@yahoo.com
Hello,
An application we are using accesses an iSeries (V5R2) via Odbc and
manipulates files through the SQL interface. Even though the
consultant has indicated that the application is not using journaling,
we are seeing the journal receivers getting huge, so we need to delete
them quite frequently.
My questions: How can we make sure that sql statements are running with
journaling off? Is it possible to turn off journaling for some
collections? (Sorry if the questions are naive; I am new to iSeries.)

[d***@yahoo.com]

Post by Saml
Journaling is optional on DB2 for iSeries.

Thanks! That was a very clear explanation. Right after I posted, I
went to IBM docs, and found a whole chapter on the topic too.

[Tim M]

In order to use "transaction isolation" aka "commitment control" you
must have journaling enabled on your tables, you can, however, modify
the journals so that the OS will automatically manage your journal
receivers. Including changing them when they become too large and
deleting old journal receivers if you don't intend to use them for
recovery purposes.

Post by d***@yahoo.com
Hello,
An application we are using accesses an iSeries (V5R2) via Odbc and
manipulates files through the SQL interface. Even though the
consultant has indicated that the application is not using journaling,
we are seeing the journal receivers getting huge, so we need to delete
them quite frequently.
My questions: How can we make sure that sql statements are running with
journaling off? Is it possible to turn off journaling for some
collections? (Sorry if the questions are naive; I am new to
iSeries.)