2.131 LAGCRITICAL

Valid for

Manager

Description

Use LAGCRITICALCSECS, LAGCRITICALSECONDS, LAGCRITICALMINUTES, or LAGCRITICALHOURS to specify the time interval at which Extract or Replicat processing lag is reported to the event log as a critical message. For example, LAGCRITICALMINUTES 5 specifies a reporting interval of five minutes. Likewise, LAGCRITICALSECONDS 20 specifies a reporting interval of 20 seconds; LAGCRITICALHOURS 2 specifes two hours.

When using a LAGCRITICAL parameter, specify LAGREPORT to determine how often the lag times are evaluated and reported.

Syntax

LAGCRITICALCSECS csecs [,process_type group_name] [,IGNORETASKS|REPORTTASKS] [,IGNORESTOPPED|REPORTSTOPPED]|
LAGCRITICALSECONDS seconds [,process_type group_name] [,IGNORETASKS|REPORTTASKS] [,IGNORESTOPPED|REPORTSTOPPED]|
LAGCRITICALMINUTES minutes [,process_type group_name] [,IGNORETASKS|REPORTTASKS] [,IGNORESTOPPED|REPORTSTOPPED]|
LAGCRITICALHOURS hours [,process_type group_name] [,IGNORETASKS|REPORTTASKS] [,IGNORESTOPPED|REPORTSTOPPED]

csecs

The reporting interval in centiseconds, as in LAGCRITICALCSECS 50.

seconds

The reporting interval, in seconds, as in LAGCRITICALSECONDS 10.

minutes

The reporting interval, in minutes, as in LAGCRITICALMINUTES 5.

hours

The reporting interval, in hours, as in LAGCRITICALHOURS 1.

process_type group_name

Specifies the process for which the lag will be reported.

process_type

Must be EXTRACT or REPLICAT or ER.

group_name

The name of the Extract group or Replicat group or wildcard group.

IGNORETASKS|REPORTTASKS

By default the task groups are not reported.

By adding the REPORTTASKS option, the lag information will be reported for SOURCEISFILE and SPECIALRUN groups, toggle off with IGNORETASKS.

IGNORESTOPPED|REPORTSTOPPED

By default no information is printed for a group in a STOPPED state. By adding the REPORTSTOPPED option, lag information will be reported, to toggle off with IGNORESTOPPED.