MVSFORUMS.com

[ROBERTLa]

Gents:

I'm setting up small database of 12 tables that must be available 24 x 7. It uses row level locking and is used by online and batch users to record statistical data (non financial / non transaction oriented).

I need to know what special data-center procedures are required to keep this database fully bullet proof. For example I remember something about log-datasets needing special treatment, and fairly frequent image-copies - but the details I've long forgotten.

Any bullet-list you can throw my way ?

Any help appreciated.
-Rob

[Bithead]

You should use concurrent (online/fuzzy) image copies, usually at a time of low useage. Recovery will make use of the online logs so those must be available. That means that the image-copies and logs must be stored seperately (geographically) from the databases. It is useful to have copies on site as well.

The number of image copies taken depends on how fast your recovery should take, which is also a function of transaction volume. Image copies at peak periods will impact system performance.

You make also need to take some kind of sync-point at the end of the image-copy to give you a recovery point.

If there is a latge amount of data, you should consider partitioned tables.

Full 24x7 shops make use of sysplexing / clustering to allow individual machines to be IPL'd / re-booted.

You may also need to re-org the databases which can be done "online" in many cases.

Online and batch processes do not always work well together. Batch commits tend to be further apart than online ones leading to record locking. Consider using seperate tables if possible.

[ROBERTLa]

Thank You !

Always a pleasure working with the fine team at MVSForums !.

Rob.

[Mukunda]

Rob
You might want to have a look at this http://www.mainframeweek.com/journals/articles/0019/ and this http://www.mainframeweek.com/journals/articles/0020/. Might help in designing your bullet-proof