In general, all system libraries continue to exist in the system disk pool. However, to support better isolation and recovery of the independent disk pool group containing system libraries, the following instances of system libraries are also created in the primary disk pool:
In the above, nnnnn is the independent disk pool number right-aligned and padded with zeros.
One new library attribute, Protected, is introduced to support the extended library capability. Since the libraries QSYSnnnnn, QSYS2nnnnn, and SYSIBnnnnn are special versions that correspond to the system libraries, only operating system code can create objects into them. Applications cannot create objects into these libraries.
Library | *SYSBAS library | Protected in independent disk pool | Protected in system disk pool |
---|---|---|---|
QSYSnnnnn | QSYS | Yes | No |
QSYS2nnnnn | QSYS2 | Yes | No |
SYSIBnnnnn | SYSIBM | Yes | No |
QRCLnnnnn | QRCL | No | No |
QRCYnnnnn | QRECOVERY | No | No |
QRPLnnnnn | QRPLOBJ | No | No |
All user libs | Not applicable | No | No |
The normal search order for objects is to search the libraries based on the user-specified library value, the user's library list, and the namespace in effect for the job. The only exception to this occurs when the user job has a disk pool group in the job's namespace. In this case, aliasing support takes effect for object references to the database control objects in QSYS, QSYS2, and SYSIBM. The objects in the QSYSnnnnn, QSYS2nnnnn, and SYSIBnnnnn libraries are returned so that users are operating on the database control information associated with their extended namespace.