Configuring and Installing Optional Components › Configuration Tasks for Optional Base Components › Set up the Interface with CA 7 WA › Access the CA 7 Browse Log

Access the CA 7 Browse Log

You must add a data control module (DCM) to the ENF database to access the CA 7 WA Browse log.

To access the CA 7 WA browse log

1. Install CA 7 WA Release 3.3 or higher.
2. Set the CA OPS/MVS INITCA7 parameter to YES in the OPSSPA00 member. If you want CA OPS/MVS to generate ENF-related trace messages, then you must also set the CA OPS/MVS DEBUGENF parameter to YES. Additionally, depending on the volume of browse messages that CA 7 WA produces, you may need to tailor the default values of the CAIENFMAX and CAIENFRATE parameter. For more information on these parameters, see the Parameter Reference.
3. Add the DCM to ENF. Verify with CA 7 WA Technical Support that their SAMPJCL contains an L232DCM1 job.

   This job installs the CA 7 WA browse event. An ENF EVENT command listing all of the DCMs that are installed should display:

   DCM module name: CAL2DCM1 Description: CA 7 BROWSE EVENT Installed
    date: 01.010 time: 11:25:20
   

Configure Hardware Services (HWS)

To activate CA OPS/MVS Hardware Services (HWS) initialization parameters must be appropriately set. Also, since HWS interfaces with the Hardware Interface Service , the Hardware Interface Service, must be available on the system where CA OPS/MVS is running.

HWS Parameters

To activate HWS, set the INITHWS parameter to YES:

OPSPRM('SET','INITHWS','YES')

Setting INITHWS to YES activates the general CA OPS/MVS Hardware Services 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, HWS will provide hardware event notifications in the form of API events that can be automated via )API rules.

HWS can be activated and deactivated at anytime through the initialization parameters.

For detail information on 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.

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 name).

For more information on the INITHWS and HWSRULES parameters, see "Hardware Services (HWS)" 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.

To have CA OPS/MVS generate HWS-related trace messages, set the DEBUGHWS parameter to ON:

OPSPRM('SET','DEBUGHWS','ON')

Setting up the Hardware Interface Service

HWS utilizes 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 its HWS functions. 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.

Install and Configure the Hardware Interface Service

See the Hardware Interface Service Component Guide for information on installation, configuration, and operation of the Hardware Interface Service.