DSNL025I A DISTRIBUTED AGENT FOR luw-id=token EXISTS AT THIS LOCATION BUT NOT AT SITE WITH LOCATION location AND LU luname

Explanation

The DDF error monitor has detected that a distributed agent exists at this location but not at the named partner location.

Where
luw-id=token
The logical unit of work ID of the thread followed by an '=' sign and a token which may be used in place of 'luw-id' in any Db2 command that accepts 'luw-id' as input.
location
The location name of the partner site where a thread with the same 'luw-id' does not exist.
luname
The 8-character LUNAME of the partner location.

Operator response

Determine if the inconsistency is due to network conditions or a Db2 error. If a Db2 error is suspected, acquire documentation to diagnose the problem.
  1. Console dump of Db2 address spaces (ssnmDBM1, ssnmMSTR, and ssnmDIST), VTAM®, and user's address space at the requesting site.
  2. Console dump of Db2 address spaces (ssnmDBM1, ssnmMSTR, and ssnmDIST), and VTAM at the server site.
  3. SYSLOG from requesting and server sites.
  4. LOGREC from requesting and server sites.

If an indefinite inconsistency is suspected, use the CANCEL DDF THREAD command to terminate the thread. If CANCEL DDF THREAD fails to terminate the agent, use VTAM commands to terminate the thread conversations.

Problem determination

Use the Db2 DISPLAY THREAD command with DETAIL option at each Db2 subsystem to display information about the agent and its conversations. Use VTAM commands to display additional information about the conversations being used by the thread and also about network conditions.

Collect the following diagnostic items:
  • Console output from the system on which the job was run, and a listing of the SYSLOG data set for the period of time that spans the failure.
  • SVC dump (or system dump), taken to SYS1.DUMPxx data set, as result of an operator-initiated dump command or SLIP trap exit.
  • A listing of the SYS1.LOGREC data set, obtained by executing IFCEREP1.
.