Event ID, Associated Entity and Description Table

Coding Each AOF Rule Type › Generic Event Application Program Interface › Hardware Event API Rules › Event ID, Associated Entity and Description Table

Event ID, Associated Entity and Description Table

Event Name	Event ID (API.ID value)	Associated Entity Type	Event Description (API.EVDESC value)
Activation Profile Change	HWSACTPCHG	CPC/LPAR	ACTIVE PROFILE CHANGED
Application Ended	HWSAPPEND	CPC	APPLICATION ENDED
Application Started	HWSAPPSTRT	CPC	APPLICATION STARTED
Attribute Added/Updated	HWSATRUPDT	Any	ATTRIBUTES ADDED OR UPDATED
Capacity Change	HWSCAPCHG	CPC	CAPACITY CHANGED
Capacity Record	HWSCAPREC	CPC	CAPACITY RECORD CHANGE
Command Response	HWSCMDRESP	CPC/LPAR	ENTITY COMMAND RESPONSE
Disabled Wait	HWSDBLWAIT	LPAR	DISABLED WAIT
Entity Exception	HWSENTEXC	CPC/LPAR	ENTITY EXCEPTION
Hardware Communication Error	HWSHWCOMER	CPC	HARDWARE COMMUNICATIONS ERROR
Hardware Interface Down	HWSINTFDWN	N/A	SERVER HARDWARE INTERFACE DOWN
Hardware Interface Up	HWSINTFUP	N/A	SERVER HARDWARE INTERFACE UP
Hardware Message	HWSHWMSG	CPC	HARDWARE MESSAGE ISSUED BY ENTITY
Hardware Message Delete	HWSHWMSGD	CPC	HARDWARE MESSAGE DELETED
New Child	HWSNEWCHLD	Any	NEW CHILD UNDER ENTITY
New Entity	HWSNEWENT	Any	NEW ENTITY CREATED
Operating System Message	HWSOSMSG	LPAR	OPERATING SYSTEM MESSAGE
Power Change	HWSPOWCHG	CPC	POWER CHANGE
Security Event	HWSSECUR	LPAR	SECURITY EVENT
Status Change	HWSSTATCHG	CPC/LPAR	ENTITY STATUS CHANGE
Topology Complete	HWSTOPCOMP	N/A	INITIAL H/W TOPOLOGY COLLECTION COMPLETE
Topology Error	HWSTOPERR	N/A	INITIAL H/W TOPOLOGY COLLECTION HAD ERRORS
Other (See Note)	HWSOTHER	varies	varies

Note: The Other event is generated when CA OPS/MVS receives an unknown event type. The Other event type is designed to handle new Hardware Interface Service events that have not yet been defined as their own HWS event type. For example, if the Hardware Interface Service adds support for a new event and delivers the event notification to CA OPS/MVS, CA OPS/MVS will see the event and generate it as an HWSOTHER event with associated event data. Once CA OPS/MVS adds support for the new event type, it will have its own HWS event type and will no longer fall under the Other event. Implementing the Other event type in this way allows CA OPS/MVS to receive and process new events as they become available.