The INITHWS parameter determines whether the product activates the optional HWS interface. If hardware services are not desired, leave this parameter set to NO to reduce overhead. The INITHWS parameter must be set to YES for the other hardware service parameters to have an effect. This includes HWSRULES and the Address HWS host command environment. The INITHWS parameter should only be set to YES if you intend to use the CA OPS/MVS hardware services.
NO
YES
Anytime
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 name).
Example: INITHWS
This function activates support for HWS:
OPSPRM('SET','INITHWS','YES')
The HWSRULES parameter determines whether the product activates the optional hardware event notification and associated rule interfaces. If hardware event notification support is not desired, leave this parameter set to NO to reduce overhead. The INITHWS parameter must also be set to YES if HWSRULES is set to YES in order for HWSRULES to take effect. The HWSRULES parameter should only be set to YES if you intend to use the hardware event notification function of HWS.
NO
YES
Anytime
Example: HWSRULES
This function activates support for hardware event notification and associated rules:
OPSPRM('SET','HWSRULES','YES')
Note: Setting HWSRULES to YES activates the OPS hardware event notification function. When this function is activated, OPS receives hardware events as API events that can be automated through OPS )API rules.
For detailed information on the hardware event types and associated variables see, "Hardware Event API Rules" in the CA OPS/MVS AOF Rules User 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 and for 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.
The DEBUGHWS parameter determines whether CA OPS/MVS generates HWS-related trace messages.
OFF
This value prevents CA OPS/MVS from generating HWS-related trace messages.
ON
This value causes CA OPS/MVS to generate HWS-related trace messages.
Anytime
Example: DEBUGHWS
This function causes CA OPS/MVS to generate HWS-related trace messages:
OPSPRM('SET','DEBUGHWS','ON')
The Hardware Interface Service provides CA Technologies products with a common interface/API for accessing hardware services. CA OPS/MVS uses 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 its hardware functions.
For more information see, "Configure Hardware Services (HWS)" in the CA OPS/MVS Installation Guide.
|
Copyright © 2014 CA.
All rights reserved.
|
|