LISTDS for Data Set in Lost Lock State
The first part of Figure 1 summarizes
the status for the data set. In this example, the data set:
- Has lost locks
- Is a recoverable data set
- Is not in NON-RLS UPDATE PERMITTED state
The second part of Figure 1 shows a subsystem sharing the data set and gives status relative to the data set. The subsystem is a commit protocol application (ONLINE), and is not currently active (FAILED). The application owns locks that have been lost.
Figure 1. LISTDS for Data Set in Lost
Lock State
SHCDS LISTDS(SYSPLEX.KSDS.LOSTLOCK.CLUS5)
----- LISTING FROM SHCDS ----- IDCSH02
--------------------------------------------------------------------
DATA SET NAME----SYSPLEX.KSDS.LOSTLOCK.CLUS5
CACHE STRUCTURE----- NOT ASSIGNED -
RETAINED LOCKS----------NO NON-RLS UPDATE PERMITTED---------NO
LOST LOCKS-------------YES PERMIT FIRST TIME----------------NO
LOCKS NOT BOUND---------NO FORWARD RECOVERY REQUIRED--------NO
RECOVERABLE------------YES
SHARING SUBSYSTEM STATUS
SUBSYSTEM SUBSYSTEM RETAINED LOST NON-RLS UPDATE
NAME STATUS LOCKS LOCKS PERMITTED
--------- -------------- -------- ----- --------------
ONLINE01 ONLINE--FAILED NO YES NO
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0