MVSFORUMS.com

db2rules

Hello All,

We have a customer going into production with a relatively empty database and about 150 users to start with.

This is a large OLTP application with a browser front-end and DB2/CICS on z/OS as the host. There are obvious concerns about locking/contention until there is enough data so support all the accesses.

I see two methods of getting around this temporarily:

1) Row level locking.

PRO - easily implemented/un-implemented

CON - DB2 overhead

2) Seeding the database. The seeding would consist of loading fake data keyed by state or other method (not thought out completely yet), which could be deleted when no longer required.

PRO - Data is hidden from users (hopefully). Lock and Freespace parms would need little changes going forward.

CON - Application RI would make load program difficult. How would reporting or data warehouse programs react to the fake data? What DBA would actually want to delete production (albeit fake) data when not needed anymore?

Has anyone gone through this in real life or have any opinions they'd like to share?

Thanks!

kolusu · Posted: Mon May 10, 2004 12:03 pm Post subject:

Db2rules,

db2rules · Posted: Mon May 10, 2004 1:25 pm Post subject:

Howdy Kolusu,

The brower is very thin... most all work and data happens on the host and remains on the host, if that's what you mean.

The application is very update / delete / insert / select intensive.

LOCKMAX zero is definitely under consideration.

Thanks for all your help (on this and other posts).

Is there anyone out there with real world experience with this type of "opportunity"?

Remember,

DB2 Rules!

kolusu · Posted: Mon May 10, 2004 4:37 pm Post subject:

Db2rules,

How can I forget you ? I always remember all my contacts via helpboards. Unfortunately I do not have any real experience with your situation. sorry about that.

Kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu