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

SHCDS|be made to complete forward recovery, whether using a product such asCICSVR that supports VSAM RLS or using another forward recoveryprocedure.If forward recovery does not successfully complete, locks cannot bereassociated (bound) to the new version of the data set, because these locks donot provide the protection that online backout requires.Before using this parameter, check the documentation for your onlineapplication. For CICS, the procedure is documented in the CICS Recovery andRestart Guide.Abbreviation: DUNBLPERMITNONRLSUPDATE(base-cluster)Allows a data set with pending RLS recovery to be opened for output innon-RLS mode. This command is used when it is necessary to run criticalbatch updates and RLS recovery cannot first be completed. This is reset thenext time the data set is accessed for RLS. If after usingPERMITNONRLSUPDATE, you do not run a non-RLS batch job, you must useDENYNONRLSUPDATE to prevent non-RLS updates.Abbreviation: PERMTDENYNONRLSUPDATE(base-cluster)If you inadvertently issue PERMITNONRLSUPDATE, use this parameter toreset the effect of PERMITNONRLSUPDATE.If recovery was pending, but you did not run a non-RLS batch job, you mustuse this parameter. If not reset, CICS takes action assuming the data set hasbeen opened for update in non-RLS mode.Do not use DENYNONRLSUPDATE if you do indeed run non-RLS work afterspecifying PERMITNONRLSUPDATE. The permit status is reset the next timethe data set is opened in RLS mode.Abbreviation: DENYREMOVESUBSYS(subsystem)Use this parameter to remove any knowledge of recovery owed to SMSVSAMby the named subsystem, including locks protecting uncommitted updates.Normally, a failed online application would be restarted so that it can do therequired backouts and release locks protecting uncommitted updates. However,sometimes it might be necessary to cold start the online application. For moreinformation about cold starts, see CICS Recovery and Restart Guide.Use of this parameter is equivalent to cold starting the named subsystem withrespect to the SMSVSAM server. Use REMOVESUBSYS for the rare caseswhere either there is no intention of ever running the subsystem again or theapplication’s cold start procedures cannot be used. An example of anappropriate use of REMOVESUBSYS would be removing a test system that isno longer needed.If the removed subsystem is ever run again, every effort should be made tocold start the subsystem.Attention: Use of REMOVESUBSYS can result in loss of data integrity.Abbreviation: RSSCFREPAIR({INFILE(ddname)|INDATASET(dsname)}Use this command to reconstruct the RLS indicators for all applicable data sets344 z/OS V1R6.0 DFSMS Access Method Services for Catalogs