The object locking rules that the server uses for save-while-active requests are less restrictive than the rules it uses for other save operations. These object locking rules allow users to perform update operations and use most object-level commands after the server performs checkpoint processing. Generally, the server keeps a shared, no update (*SHRNUP) lock on the objects through the checkpoint processing. After the establishes checkpoints, the server unlocks most of the objects. Other objects remain allocated with a shared for read (*SHRRD) lock.
| Save-While-Active | |||
|---|---|---|---|
| Object Type | SAVACT(*NO) | Establish Checkpoint | After Checkpoint |
| Most object types | *SHRNUP | *SHRNUP | None |
| Configuration object | None | 1 | 1 |
| Data area | *SHRNUP | *SHRRD | None |
| Database members | *SHRNUP | *SHRRD | None |
| Document | *SHRNUP | *SHRRD | None |
| Folder | *SHRRD | *SHRRD | None |
| Job queue | *SHRRD | *SHRRD | None |
| Journal | *SHRRD | *SHRRD | None |
| Journal receiver | *SHRRD | *SHRRD | *SHRRD |
| Library, when the library or an object in it is being saved | *SHRUPD | *SHRUPD | *SHRRD |
| Output queue | *SHRRD | *SHRRD | None |
| Product load | *SHRNUP | *SHRNUP | *SHRRD |
| System resource management object | *SHRNUP | 1 | 1 |
| User profiles, authorization lists, and authority holders | *SHRRD | 1 | 1 |
| Object, if STG(*FREE) is specified | *EXCL2 | 1 | 1 |
| Objects in directories | Share with readers | Share with readers3, 4 | Share with readers and writers3 |
|
|||
These locking rules pertain to object-level locks and not database record-level locks. The locking rules allow the opening and closing of database file members and any record-level I/O operations to database file members during any phase of the save-while-active operation.