Coding Each AOF Rule Type › Generic Event Application Program Interface › OPS/REXX Rule Variables For Linux Connector Events

OPS/REXX Rule Variables For Linux Connector Events

These variables are available for all unsolicited VM and Linux message events.

Note: When a variable representing event data is not applicable for that event, the variable-length is zero.

API.APPLICATION

Description

The name of the application providing the event.

Data Type

Character, read-only, up to eight characters.

Fixed Value

LXC

API.HOSTNAME

Description

The name of the VM or Linux system that issued the unsolicited message.

Data Type

Character, read-only, 1-16 characters.

Example

LINUX113

API.ID

Description

The first word of the unsolicited message text.

Data Type

Character, read-only, 1-10 characters.

Example

LXLOG0001

API.LEVEL

Description

This value is set to the CA OPS/MVS subsystem name that created the API event.

Data Type

Character, read-only, four characters.

Example

OPSS

API.SYSTYPE

Description

The system type that generated the message.

Data Type

Character, read-only, character

Values

VM

VM or Linux guest computers

LPAR

A Linux guest system that does not support the VMCP command.

INTEL

A Linux system running on an Intel platform

OTHER

A Linux system running on a non-Intel platform

API.TEXT

Description

The complete normalized message text that was passed from the Linux Connector component. The first 128 characters appear in OPSLOG when the BROWSELXC parameter is set to YES.

Data Type

Character, read-only, 1-4096 characters.

Example

LXLOG001I LINUX113 ZVM002 user notice logger: Test Message

API.VERSION

Description

This value is set to the CA OPS/MVS product version code.

Data Type

Character, read-only, eight characters.

Example

12.00.00

API.VMNODE

Description

The name of the VM system that issued a VM message or the Linux guest VM system name.

Data Type

Character, read-only, 1-8 characters.

Example

ZVM002