|
|
|
This section contains the following topics:
This section contains the following topics:
Hardware Services (HWS) provides the ability to automate hardware (HMC) functions. Through HWS, hardware event notifications are captured as OPS Generic API events. Rule-based automation can be designed for hardware events such as hardware message events, security events, and operating system message events.
For more information on automation of HMC control functions, see Manage the Processors.
The HWS component of CA OPS/MVS provides hardware function automation through the following features:
HWS event notification feature:
For more information on available hardware events and detailed information on coding hardware event API rules, see "Hardware Event API Rules" in the CA OPS/MVS AOF Rules User Guide.
To activate HWS, set the INITHWS parameter to YES:
OPSPRM('SET','INITHWS','YES')
Setting INITHWS to YES activates the general HWS component. In order to activate hardware event notification, parameter HWSRULES must also be set to YES:
OPSPRM('SET','HWSRULES','YES')
When HWSRULES is set to YES, CA OPS/MVS will provide hardware event notification in the form of API events that can be automated through )API rules.
For more detailed information on the hardware event types and associated variables that are available through HWS event notification. see, "Hardware Event API Rules" in the CA OPS/MVS AOF Rules User Guide.
HWS can be activated and deactivated at anytime through the initialization parameters.
Note: If you are changing the value of INITHWS from NO to YES after CA OPS/MVS initialization, you must issue the z/OS command: MODIFY OPSS,RESTART(HWS) for the new value to take effect (where OPSS is the CA OPS/MVS subsystem .
For more information on the INITHWS and HWSRULES parameters see "Hardware Services" in the CA OPS/MVS Parameter Reference Guide.
Since hardware events are presented as OPS )API events, the OPS API interface must also be activated to receive the hardware events. To activate the OPS API interface, set the OPS APIACTIVE parameter to YES:
OPSPRM('SET','APIACTIVE','YES')
For more information on the APIACTIVE parameter, see "Application Programming Interface Parameters" in the CA OPS/MVS Parameter Reference Guide. For general information on coding API rules and specific information for coding hardware event API rules, see "Generic Event Application Program Interface" in the CA OPS/MVS AOF Rules User Guide.
HWS requires the Hardware Interface Service The Hardware Interface Service provides CA Technologies products with a common interface/API for accessing hardware functions. CA OPS/MVS interfaces with the Hardware Interface Service to implement HWS. Therefore, the Hardware Interface Service must be configured and started on the system where CA OPS/MVS is running in order for HWS to provide services such as hardware event notification.
See the Hardware Interface Service Component Guide for information on installation, configuration, and operation of the Hardware Interface Service.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |