Previous Topic: Event ID, Associated Entity and Description TableNext Topic: OPS/REXX Rule Variables For Linux Connector Events


Linux Connector API Rules

CA OPS/MVS Linux Connector interface (LXCON) connects with the Linux Connector component through a local IP connection. This interface delivers unsolicited message events from monitored VM and Linux systems as normalized messages that are processed as CA OPS/MVS API events. Write API rules that specify how CA OPS/MVS can respond to these Linux and VM events. Typically, the System State Manager (SSM) component of CA OPS/MVS is used to monitor and control the availability of Linux systems that run as VM guest computers. The Address LXCON host command can be used to display any connected VM and Linux systems and to issue commands to the systems. Every Linux Connector API event ID begins with a common prefix, LX. Write individual API rules for specific LXCON events or a single rule for all events with the rule specification:

)API LX*

For more information about the Linux Connector interface and component, see the Linux Connector Service in the CA OPS/MVS Administration Guide.

Note: Generally, Linux Connector unsolicited message events should only be received and automated by one CA OPS/MVS per Linux Connector component. This avoids duplicate automation of events.

The following Linux Connector unsolicited message events are available through API rules:

Z/VM Messages
Description

LXMSG001I z/VM-node message-type user ID message-text

Example
LXMSG001I ZVM002 MSG POLLGEN NMVM0001 00:34:49 Hello
Z/VM Events
Description

LXEVT001I z/VM-node user ID event-type

Example
LXEVT001I ZVM002 LINUX113 RUNNABLESTATEENABLED
Linux Syslog-ng Messages
Description

LXLOG001I Linux-name z/VM-host facility severity message-text

Example

LXLOG001I LINUX113 ZVM002 user notice logger: Test Message