InfoSphere Optim

I'm working on a new Access Definition using Optim Data Growth 11.3 z/OS against DB2. There are about 10 tables in the AD and we noticed during testing that Optim is issuing commits during the Delete phase after each table is completed...which is far below the commit threshold. We expected Optim to just crank along and issue a commit when the overall delete count is hit. 

The behavior of committing after each table is processed is usually tied to when you are using Table Locks, but we are not using that option and have it turned off at the site level options anyway. 

Can anyone confirm if Optim will always issue a commit after processing a table, regardless of the Delete_Commit_Count explicitly listed in the job parameters? 

-Keith


------------------------------
Keith Tidball
Progressive Insurance
------------------------------

#InfoSphereOptim
#Optim

Hi,

I am confirming: Optim will always issue a commit after processing a table, regardless of the Delete_Commit_Count explicitly listed in the job parameters.

------------------------------
Greg Czaja
Optim for z/OS Development
Unicom Systems Inc.
------------------------------

Original Message:
Sent: Mon June 29, 2020 12:18 PM
From: Keith Tidball
Subject: Delete Commit Timing

I'm working on a new Access Definition using Optim Data Growth 11.3 z/OS against DB2. There are about 10 tables in the AD and we noticed during testing that Optim is issuing commits during the Delete phase after each table is completed...which is far below the commit threshold. We expected Optim to just crank along and issue a commit when the overall delete count is hit. 

The behavior of committing after each table is processed is usually tied to when you are using Table Locks, but we are not using that option and have it turned off at the site level options anyway. 

Can anyone confirm if Optim will always issue a commit after processing a table, regardless of the Delete_Commit_Count explicitly listed in the job parameters? 

-Keith


------------------------------
Keith Tidball
Progressive Insurance
------------------------------

#InfoSphereOptim
#Optim

I suspected as much, thank you for confirming this. 

-Keith

------------------------------
Keith Tidball
Progressive Insurance
------------------------------

Original Message:
Sent: Mon June 29, 2020 01:46 PM
From: Gregory Czaja
Subject: Delete Commit Timing

Hi,

I am confirming: Optim will always issue a commit after processing a table, regardless of the Delete_Commit_Count explicitly listed in the job parameters.

------------------------------
Greg Czaja
Optim for z/OS Development
Unicom Systems Inc.

Original Message:
Sent: Mon June 29, 2020 12:18 PM
From: Keith Tidball
Subject: Delete Commit Timing

I'm working on a new Access Definition using Optim Data Growth 11.3 z/OS against DB2. There are about 10 tables in the AD and we noticed during testing that Optim is issuing commits during the Delete phase after each table is completed...which is far below the commit threshold. We expected Optim to just crank along and issue a commit when the overall delete count is hit. 

The behavior of committing after each table is processed is usually tied to when you are using Table Locks, but we are not using that option and have it turned off at the site level options anyway. 

Can anyone confirm if Optim will always issue a commit after processing a table, regardless of the Delete_Commit_Count explicitly listed in the job parameters? 

-Keith


------------------------------
Keith Tidball
Progressive Insurance
------------------------------

#InfoSphereOptim
#Optim