Using the Product in a DB2 Environment › Background DB2 Catalog Extraction › Synchronous Data Gatherer › Harvester Error Processing Control

Harvester Error Processing Control

In the remote possibility that the Synchronous Data Gatherer encounters an unrecoverable problem when harvesting data, diagnostic information is written to the operating system logrec and a message will be displayed on the server JES log.

As some problems are repetitive in nature, the Harvester data collector has built-in-limit the number of messages displayed. It also shuts itself down after a built-in number of errors are exceeded.

The messages displayed are as follows:

• When the message count exceeds the built-in value of 100 messages, the following message displays:

  TN3441W

  Max Harvester internal ABEND message count exceeded for pppppppp jjjjjjjj

  where

  pppppppp

  Specifies the profile name.

  jjjjjjjj

  Specifies the job name being monitored.

• When an error occurs, the Harvester writes diagnostic information to LOGREC and displays the following message on the server JES log:

  TN3438W

  Harvester Abend cccccccc aaaaaaaa dddddddd tttttttt ssssssss pppppppp jjjjjjjj

  TN3439I

  Harvester processing continues. pppppppp jjjjjjj

  where

  cccccccc

  Specifies the abend code.

  aaaaaaaa

  Specifies the next instruction address.

  dddddddd

  Specifies displacement of instruction.

  tttttttt

  Specifies the count of abends.

  ssssssss

  Specifies the intercept sequence number.

  pppppppp

  Specifies the profile name.

  jjjjjjjj

  Specifies the job name being monitored.

• Harvesting processing continues until the built-in maximum count of 100 abends is exceeded. At this time, the following message displays:

  TN3440W

  Max Harvester internal ABEND count has been exceeded. Harvester processing ended for pppppppp jjjjjjjj

  where

  pppppppp

  Specifies the profile name.

  jjjjjjjj

  Specifies the job name being monitored.

  Then, the Harvester stops collecting data.