122 Data Sharing in a Nutshell
7.1 CLOSE YES and CLOSE NO table spaces
The CLOSE specification you made for CREATE/ALTER TABLESPACE has
different implications in data sharing.
Any table space or index which has remained in a read-only state with no activity
for a period of time longer than the pseudo-close interval (PCLOSEN/PCLOSET
DSNZPARM) is physically closed to reduce data sharing overhead (the object
can become non-GBP-dependent if it is closed on all but one member or if it is
open on multiple members but all are read-only). Its disadvantage is that the next
access to the object must go through physical open again. There can be
significant overhead, particularly if a large number of objects are accessed at the
same time after a period ...