LISTDS for Data Set in Non-RLS Permitted State

The first part of Figure 1 summarizes the status for the data set. In this example, the data set:
  • Has retained locks
  • Is a recoverable data set
  • Is not in NON-RLS UPDATE PERMITTED state
  • Has been processed by an RLS application that reset the PERMIT FIRST TIME status

The second part of Figure 1 lists the subsystems sharing the data set and their status relative to the data set. The subsystems are commit protocol applications (ONLINE), and are not currently active (FAILED). Both of the applications own retained locks for this data set.

Subsystem RETLK05A has not completed recovery for the NON-RLS PERMITTED state of the data set.

Subsystem KMKLK05D has either cleared the NON-RLS PERMITTED state or began sharing the data set after setting the NON-RLS PERMITTED state.

Figure 1. LISTDS for Data Set in NON-RLS PERMITTED State
   SHCDS LISTDS(SYSPLEX.KSDS.PERMIT.CLUS2)
 ----- LISTING FROM SHCDS ----- IDCSH02
 ------------------------------------------------------------------
 DATA SET NAME----SYSPLEX.KSDS.PERMIT.CLUS2
   CACHE STRUCTURE----CACHE01
   RETAINED LOCKS---------YES   NON-RLS UPDATE PERMITTED--------YES
   LOST LOCKS--------------NO   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
   ---------    --------------    --------    -----    --------------
   KMKLK05D     ONLINE--FAILED    YES         NO       NO
   RETLK05A     ONLINE--FAILED    YES         NO       YES
 IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0
Parent topic: LISTDS