Listing and controlling SMSVSAM recovery

Use the SHCDS command to list SMSVSAM recovery associated with subsystems and spheres and to control that recovery. This command works both in batch and in the TSO/E foreground. The functions include the following subcommands:

List subcommands
Subcommands that enable you to take action on work that was shunted
Subcommands to control a manual forward recovery in the absence of a forward recovery utility that supports SMSVSAM protocols
Subcommands that enable you to run critical non-RLS batch window work when it is not possible to first close out all outstanding SMSVSAM recovery
A subcommand that allows for a subsystem cold start
Recommendation: After a cold start, if recovery was not completed for any data sets, they are most likely left in a damaged state and must be recovered manually. If the data sets are forward recoverable, their forward recovery logs might also be damaged. Manually recover the data sets (without using forward recovery), take backups of them and of any other data sets that use the forward recovery log, and then delete and redefine the forward recovery log.

Use this command cautiously. The CICS Transaction Server for z/OS Information Center at http://publib.boulder.ibm.com/infocenter/cicsts/v3r1/index.jsp. describes many of the situations that require the use of the SHCDS command. For details about administering VSAM RLS, see z/OS DFSMSdfp Storage Administration.

The syntax of the access method services SHCDS command follows.

This table shows the syntax of the access method services SHCDS command.

Command	Parameters
SHCDS	{[LISTDS(`base-cluster`)[JOBS]]\|
	[LISTSHUNTED{SPHERE(`base-cluster`)\|URID({`urid`\|ALL})}]\|
	[LISTSUBSYS(`subsystem`\|ALL)]\|
	[LISTSUBSYSDS(`subsystem`\|ALL)]\|
	[LISTRECOVERY(`base-cluster`)\|
	[LISTALL]\|
	[FRSETRR(`base-cluster`)]\|
	[FRUNBIND(`base-cluster`)]\|
	[FRBIND(`base-cluster`)]\|
	[FRRESETRR(`base-cluster`)]\|
	[FRDELETEUNBOUNDLOCKS(`base-cluster`)]\|
	[PERMITNONRLSUPDATE(`base-cluster`)]\|
	[DENYNONRLSUPDATE(`base-cluster`)]\|
	[REMOVESUBSYS(`subsystem`)]\|
	[CFREPAIR({INFILE(`ddname`)\|INDATASET(`dsname`)}
	[({LIST\|NOLIST})]]\|
	[CFRESET({INFILE(`ddname`)\|INDATASET(`dsname`)}]
	[({LIST\|NOLIST})]]\|
	[CFRESETDS(`base-cluster`)]}
	[PURGE{SPHERE(`base-cluster`)\|URID(`urid`)}]\|
	[RETRY{SPHERE(`base-cluster`)\|URID(`urid`)}]\|
	[OUTFILE(`ddname`)]

Base-cluster is a fully or partially qualified VSAM data set name. The high-level qualifier must be specified. You can use an asterisk (*) for a subsequent qualifier, but then no lower-level qualifiers are allowed. For example, this is allowed:

A.*

This is not allowed:

A.*.B

Subsystem is the name of an online system, such as CICS®, as registered to the SMSVSAM server.

Requirements:

Various levels of authority are required to use the SHCDS parameters. For more information, see z/OS DFSMS Access Method Services Commands.
A program that calls the SHCDS command must be APF-authorized. For more information, see z/OS DFSMS Access Method Services Commands.
To use the SHCDS command in the TSO foreground, you must add SHCDS to the authorized command list (AUTHCMD) in the IKJTSOxx member of SYS1.PARMLIB or to the CSECT IKJEGSCU. For more information, see z/OS DFSMS Access Method Services Commands and z/OS TSO/E Customization.
For examples and explanations of the output from the list parameters, see z/OS DFSMS Access Method Services Commands.