Other recommendations for a large number of objects

You should follow certain recommendations when you use Db2 Admin Tool in an environment that has a large number of objects.

The following recommendations will help you use Db2 Admin Tool with a large number of objects:

  • Reduce the number of objects for primary commands. Running Db2 Admin Tool primary commands on a very large number of objects can take some time and locks your ISPF session while the objects are being processed. If possible, when searching for objects in the Db2catalog (Db2 Admin Tool option 1), limit the number of objects by specifying a narrower search criteria.
  • When searching for objects in the Db2 catalog (Db2 Admin Tool option 1), use a search criteria that allows Db2 to use indexes to retrieve the information that you need. For more information, see the online help for the System Catalog panel (ADB21).
  • Add the recommended indexes to the Db2 catalog.
  • Run RUNSTATS on the Db2 catalog.
  • Ensure that there is free space on the DASD volumes that you are using. Db2 Admin Tool functions might need to expand the data sets beyond the primary allocation. Extending the data sets with secondary extents requires that the DASD volume has sufficient free space. If you are experiencing problems with space on data sets that have not reached their maximum extents, contact your storage administrator. The storage administrator might need to change the storage policy for these data sets to avoid the problems.
  • Ensure that your batch jobs can get sufficient virtual storage. Some Db2 Admin Tool functions keep information in storage while processing through the objects. If you are experiencing out-of-storage abends, specify a large region size on the job card, for example, 64 MB. If you still experience abends, contact your system administrator because the installation limits in the system that you are using might be causing the problem.
  • Ensure that your batch jobs can get sufficient CPU time. When you generate the DDL for a large number of objects, you might, depending on your installation settings and processor speed, need to add a TIME=n option on your job card. The recommended initial value for n is 180 (CPU minutes).