PPRC command overview

Peer-to-peer remote copy TSO commands have the same restrictions as other TSO commands. The TSO abbreviation convention requires that you specify as much of the command parameter as is necessary to distinguish it from other parameters. Do not abbreviate PPRC command names.

PPRC TSO commands, like most TSO commands, are deferred requests. You receive an initial message that reports whether the command syntax is valid, and whether TSO has accepted the command for processing. Command function processing is a separate operation that can take minutes or hours to complete. The TSO terminal, meanwhile, is free to do other processing.

When TSO is operational, you can issue the PPRC commands to automatically initiate PPRC subsystem activity. Table 1 shows which PPRC TSO commands you can issue to primary and secondary devices. TSO processes commands in the order that you issue them.

Table 1. Peer-to-peer remote copy TSO commands

TSO command	Can command be issued to a:
	Primary device?	Secondary device?
CDELPAIR	Yes	Yes
CDELPATH	Yes	No
CESTPAIR	Yes	No
CESTPATH	Yes	No
CGROUP	Yes	No
CQUERY	Yes	Yes
CRECOVER	No	Yes
CSUSPEND	Yes	Yes
PSETCHAR	Yes	No

You can put all PPRC TSO commands in a SYS1.PROCLIB member, in CLISTs, and include them within standard job JCL.

PPRC uses the Write-to-Operator (WTO) route code to route all messages to the console.

For additional information about TSO commands, refer to z/OS TSO/E Command Reference.

For additional information about the CESTPAIR NOCOPY option, refer to CESTPAIR command syntax.