Hardware Services (HWS) › HWS Features › HWS Configuration and Start-up

HWS Configuration and Start-up

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.