Caching authorization IDs for better performance

You can specify that Db2 is to cache authorization IDs for plans, packages, or routines (user-defined functions and stored procedures). Caching IDs can help improve performance, especially when IDs are frequently reused.

One cache exists for each plan, one global cache exists for packages, and a global cache exists for routines. The global cache for packages and routines is allocated at Db2 startup. For a data sharing group, each member does its own authorization caching.