Alert Management

Using the Central Component › Alert Management

Alert Management

Alert processing automatically identifies critical situations within a job step that require measurement by CA Mainframe Application Tuner. The alert is issued automatically by Performance Management Assistant when it recognizes these situations:

Current execution consumption values exceed either the statistical limits or the defined thresholds for a particular job step. For details about how to define Alert Thresholds, see "Define Alert Thresholds" in the Administration Guide.
A scheduled job step is calling a changed module.

Additionally, the user can manually issue alerts explicitly for job steps by using the online Alert Management option.

The Alert Management option provides all the necessary information for the APM Team to handle the alert. Information is provided in the form of state and reason codes that identify the situation. The following table provides a description of these codes:

State Code	Reason Code	Long Description
PEND		Performance Management Assistant provides a CA MAT measurement. A measurement is available if the alert state is changed to OPEN.
	ELPS SRVU SUIO ELIO CPIO	The state was created by job APCXJSMF as a result of statistical calculations based on absolute values. The state was created by job APCXJSMF as a result of statistical calculations based on performance indexes.
	ALTH	The state was created by job APCXJSMF by comparing SMF consumption values of a job to the defined alert thresholds.
	MODC	The state was created by job APCXJLIB as a result of a changed module.
	SRVR	The state was created by the server.
	USER	The state was created by an online user.
OPEN		Performance Management Assistant has information about an alert, either a CA MAT measurement or the user text.
	ELPS SRVU MODC USER	The state was changed from PEND to OPEN by job APCYJLNA for one of the following reasons: A CA MAT measurement existed for a job step that was in the TOP Scope and had exceeded its statistical limits. A measurement was stored in any case by user definition. No further alerts are created except those of changed modules.
	TEXT	The state was created by an online user to indicate that no measurement was requested; however, user text information was provided.
	CHCK	A user has initiated an alert for checkpoint writing.
REV		An online user selected an alert for review/inspection.
REV	all	The state was changed by an online user by using command R(eview) in the Alert List Panel. No further alerts are provided by Performance Management Assistant.
CUSE		An online user closed the alert.
CUSE	all	The state was changed by an online user by using command C(lose) in the Alert List Panel.
CTHR		PMA closed the alert automatically. No measurement is provided.
CTHR	ELPS SRVU MODC USER	The state was changed by job APCYJLNA because the measured job step abended or a CA MAT Scope change has affected a PEND alert.
CIMP		PMA closed the alert automatically. No measurement is provided.
CIMP	ELPS SRVU MODC	The state was changed by job APCYJLNA because the consumption values of the measurement did not exceed the statistical-based alert values or a TOP Scope change affected a PEND alert.
CMUL		PMA closed the alert and temporarily stopped further alerts automatically.
CMUL	ELPS SRVU MODC	The state was changed by job APCYJLNA because more than three contiguous alerts with CTHR or CIMP were detected. No further CA MAT measurements are provided until a module change is detected or an online user uses the D(elete) command in the Alert List Panel.
COVT		An online user closed the alert and took over the statistical data.
COVT	ELPS SRVU	The state was changed by an online user by using the overtake command O in the Alert List panel. In this case, the runaway values are the new statistical base for future tests.

Tell Technical Publications how we can improve this information