Restart and Reload Components and Modules

Operations › Restart and Reload Components and Modules

Restart and Reload Components and Modules

CA OPS/MVS can be restarted without restarting the entire product. Use the following component restart command:

MODIFY OPSx,RESTART(componentname)

x: Specifies the appropriate CA OPS/MVS subsystem character.
componentname: Specifies the name of the component used in the command.

The corresponding module of each component can be reloaded by issuing the following command:

MODIFY OPSx,RELOAD(module)

x: Specifies the appropriate CA OPS/MVS subsystem character.
module: Specifies the name of the component module used in the command.

The following table lists the CA OPS/MVS components that can be restarted (or recycled), the MODIFY command component name, and the name of the module associated with the component:

CA OPS/MVS Component	Component Name	Module	Notes
MSF	MSF	OPMFEX	1, 2
CAIENF Interface	ENF, CA7, or CPM	OPINEN	1
CA Network and Systems Management System Status Manager CA OPS/MVS Option Interface	SSMO or NSMX	OPTNAGCO	1, 3
CA Netman Interface	NETMAN	OPNTEX	1
Monitor Task	MONITOR	OPINMN	1
Security Interface	SECURITY	OPINSC	1
EPI	EPI	OPEPEX	1, 4
OPSLOG	OPSLOG	OPINBO	1, 5
OPSLOG Archive	ARCH	OPINAR	1
CCI	CCI	OPMFCCI	1
CA Service Desk Integration	SERVDESK	OPINSD	1
System State Manager (SSM)	STATEMAN	OPSYSTZS	1
Health Checks	HCS	OPINHC	1
System State Manager (SSM) Subtask	SSMSUB	OPZSSMMG	1
Hardware Services(HWS)	HWS	OPINHW	1

Usage Information

These modules are dynamically reloadable. However, the new module will only take effect after the corresponding subtask (component) is recycled.
In the event that MSF is unable to close its VTAM ACB, the restart will not be successful, and you may need to restart the entire product. The MSF system definitions will not be preserved after an MSF restart. You will need to redefine the MSF sessions by using the MSFRESTARTREXX parameter to call an OPS/REXX program that you have written to set up your MSF environment after the MSF has been restarted.
In the event that the CA NSM communication task of CA OPS/MVS terminates or is looping on a TCP/IP-related error, you can use the restart command to reactivate or reinitialize the task.
In the event that EPI is unable to close its VTAM ACB, the restart will not be successful, and you may need to restart the entire product.
The OPSLOG subtask is only eligible for restart in an OPSLOG Browse-only subsystem.
These restart commands are intended for manual recovery in problem situations and are not meant to be used in typical operational procedures.

Example: Restart and Reload

Assume that your CA OPS/MVS subsystem name is OPSS. If you have received a PTF for module OPMFEX and need to activate it without restarting the product, then perform the following steps:

Make sure that the new load module (OPMFEX) is in the correct load library (OPSMAIN STEPLIB or LINKLIST)
Reload the module with the following command:
```
MODIFY OPSS,RELOAD(OPMFEX)
```
Restart the MSF component using the new module with the following command:
```
MODIFY OPSS,RESTART(MSF)
```

If you only want to restart the MSF component, then issue the following command:

MODIFY OPSS,RESTART(MSF)