Let me extend my answer. Under normal DB2 operations, the DB2 tabelspace and indexspace datasets open and close as activity against those datasets comes and goes. Normal numbers would be 10's to 100's datasets open and close per hour. Any catalog setting can handle that level of activity. DB2 runs the processes the open and close on specific TCB's just for that task. It doesn't affect any other workload unless the work is waiting on a specific dataset open. You don't tune for that level of activity.
The problem is during DB2 startup and shutdown when DB2 is opening and closing thousands of datasets in a period of minutes. That can hammer your catalog response time and make a high cpu usage situation worse. This is when you would need STRNO>2. If a subsystem has less than 500 datasets open during normal running, STRNO=3 or 4 should be sufficient. If there are 2 subsystems using the same catalog, sum the activity. . If the subsytem has multiple thousands of datasets open, you need to measure your catalog response time during DB2 startup and increase STRNO until it doesn't affect the open processes. I don't remeber the exact number of TCB;s used for open/close but I am certain it is in the range of 10 to 20. . The only DB2 activity against the catalog besides OPEN calls is the check for MIGRAT so that the open/close tasks don't hang during the recall and block other open or close requests. Usually this only occurs for test subsystems so it woud not be an issue for production. -- Mike ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
