09.07.2015 Views

z/OS V1R6.0 DFSMS Access Method Services for Catalogs

z/OS V1R6.0 DFSMS Access Method Services for Catalogs

z/OS V1R6.0 DFSMS Access Method Services for Catalogs

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Appendix C. Interpreting SHCDS Output ListingsLISTDSThe following is listed <strong>for</strong> each data set:vvvvvvvCache structure nameIf the subsystem sharing the data set owns:– Retained locks– Lost locksIf locks are not bound to the data setIf the data set is recoverableIf non-RLS updates are permitted (PERMITNONRLSUPDATE was used)Status of RLS usage since permitting non-RLS updateIf <strong>for</strong>ward recovery is requiredThe report also gives a list of subsystems sharing the data set. For each subsystem,LISTDS returns:v Subsystem namevvvvIf sharing protocol is used by the subsystem (online) and if it is currently activeRetained lock statusLost lock statusIf the subsystem requires recovery <strong>for</strong> data sets in a non-RLS update permittedstateLISTDS with Data Set in Retained Lock StateThe first part of Figure 20 on page 412 gives the status of the data set. The data set:v Has retained locksv Is a recoverable data setv Is not in NON-RLS UPDATE PERMITTED stateThe second part of Figure 20 on page 412 shows a subsystem sharing the data setand its status relative to the data set. In this example, the only subsystem sharingthe data set is RETLK05A. The RETLK05A subsystem:v Is a commit protocol application (ONLINE)v Is currently active (ACTIVE)v Owns retained locks <strong>for</strong> this data setIf there are no subsystems sharing the data set, the following is displayed:IDC3189I SUBSYSTEM NOT LISTED RC=8, RS=4.The retained lock state example follows:© Copyright IBM Corp. 1973, 2004 411

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!