Removing the catalog entry lock (CE lock)
To guarantee the consistency of catalog entries (e.g. for system communication), system components can temporarily lock the catalog entry of a file or JV against modification. If it is not possible to remove a CE lock, for example because of an error during system communication, the catalog entry remains locked even though the lock is no longer required.
This type of “leftover” CE lock hinders the operation of tasks which require this file or JV for processing.
Systems support can use the REMOVE-CE-LOCK command to remove a lock for the catalog entry of a file or JV. The command is executed only when the lock holder’s task no longer exists or is in the PENDING INDEFINITELY status.
If the lock holder task possesses a different status, then the CE lock cannot be released and the command is rejected. In this case, it is necessary to check whether the lock holder task can be terminated (e.g. CANCEL-JOB command). The SHOW-CE-LOCK command can be used to ascertain the TID of this task and the SYSID of the system in which the task is running.
In the case of shared pubsets, the REMOVE- and SHOW-CE-LOCK commands can be entered at any system in the network.
Removing a file lock
The owner of the file or systems support (TSOS user ID) can use the REPAIR-FILE-LOCKS command to remove “illegal” file locks for a file. These are file locks which are no longer required but which could not be automatically reset by the system for one of the following reasons:
temporary loss of a connection in a network
system error preventing the file lock reset
The locks present for a file can be set by a job, by a system component or for data transfer.
The SHOW-FILE-LOCKS command informs the file owner and all users with access authorization about the locks which currently apply to a file. File locks which are effective because of the catalog entry are not displayed. These locks can be displayed by means of the SHOW-CE-LOCK command.