Cluster I/O Protocols (CIP) Configuration and Management Manual (H06.16+, J06.05+)

STOP Command, CIPSAM
The only supported STOP command for CIPSAM is STOP PROCESS.
STOP PROCESS
The STOP PROCESS command stops the operation of the specified CIPSAM process if it has no
open sockets. If sockets are open, the command returns an error.
STOP PROCESS Command Syntax
STOP PROCESS $cipsam-name
cipsam-name
Is the name of the CIPSAM process to stop.
Example 103 stops the CIPSAM process named $ZTC1.
Example 103 STOP PROCESS (CIPSAM)
> STOP PROCESS $ZTC1
TRACE Command, CIPSAM
The only supported TRACE command for CIPSAM is TRACE PROCESS.
TRACE PROCESS
The TRACE PROCESS command starts or stops tracing of CIPSAM operations.
TRACE PROCESS Command Syntax
TRACE PROCESS $cipsam-name
{{,STOP |[,BACKUP]}
{,TO file-spec |
[,BACKUP count]|
[,LOCKSIZE]|
[,NOCOLL]|
[,PAGES pages]|
[,RECSIZE size]|
[,WRAP]}}
PROCESS $cipsam-name
Is the name of the CIPMAN process. If you omit the object name, SCF uses the assumed object
name. For information about the ASSUME command, see the SCF Reference Manual for J-Series
and H-Series RVUs.
STOP
Discontinues the trace currently in progress.
TO file-spec
Specifies the name of the file into which the results of the trace operation are to be placed. It
is a required option if the STOP option is not used.
BACKUP
If BACKUP is specified, the command applies to the backup CIPMAN process (that is, the trace
is stopped or started on the backup). If omitted, the primary is assumed. CIPMAN must be
running as a fault-tolerant process pair if this syntax is used. If primary CIPMAN is being traced
when a takeover by backup CIPMAN occurs, the trace of the same CIPMAN continues, but
most events that were being traced prior to the CIPMAN switch are no longer traced. This is
because CIPMAN being traced is no longer the primary. If neither PRIMARY nor BACKUP is
designated, primary CIPMAN is traced.
288 SCF Reference for CIP