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

> START PROCESS $ZZKRN.CIPMON
13. Restart the Measure subsystem.
CAUTION: You must connect to CLCI by using the OSM Low Level Link to perform this procedure.
(CLCI provides a primitive terminal emulation when TCP/IP subsystem is available, but has limited
functionality.) To connect to CLCI using OSM Low Level Link:
From the File menu, select Start Terminal Emulator > For Startup TACL. This launches a CLCI TACL
session.
Replace CIPSAM
TCP/IP socket connections are lost during this procedure. Storage paths are unaffected by this
procedure.
For CIPSAM processes configured under the Persistence Manager, use the SCF ABORT and START
PROCESS commands to the Kernel subsystem, for example: > ABORT PROCESS $ZZKRN.name
and > START PROCESS $ZZKRN.name.
1. Rename the existing CIPSAM file by using the TACL command:
> RENAME $SYSTEM.SYSnn.CIPSAM, $SYSTEM.SYSnn.CIPSAMx
2. Install the new CIPSAM as $SYSTEM.SYSnn.CIPSAM.
3. List all CIPSAM and other TCP/IP processes by using the SCF LISTDEV command.
4. If the OSM maintenance processes are configured on CLIMs, stop them by using the SCF
Abort command on the maintenance Providers. For example:
> ABORT PROCESS $ZTCP0
> ABORT PROCESS $ZTCP1
5. Check to ensure the maintenance processes are stopped by using the SCF LISTDEV command.
If the processes do not appear in the display, they are stopped. For example:
> LISTDEV TCPIP
6. Start the OSM maintenance processes by using the SCF START command to the Kernel
subsystem. For example:
> START PROCESS $ZZKRN.ZTCP0
> START PROCESS $ZZKRN.ZTCP1
7. Stop and restart the remaining CIPSAM processes by :
1. Using the SCF ABORT command to the Kernel ($ZZKRN) or to the CIP subsystem ($ZZCIP).
2. Checking that the CIPSAM processes are stopped by using the SCF LISTDEV command.
3. Restarting the CIPSAM processes by using the SCF START command to the Kernel or CIP
subsystem.
Upgrading CLIM Software and Firmware
A new OSM tool, the Down System CLIM Firmware Update Tool, now makes it possible to update
the firmware for all CLIM components, in a single action, while the NonStop system is not running.
Because this method allows the updates to be run on multiple CLIMs at the same time, resulting in
a much more efficient update process, this is now the method prescribed for use during planned
Upgrading CLIM Software and Firmware 135