DDF errors

[Tracy Johnson]

Good day! I am looking for a little help with a couple of problems with
DB2 v5.1. We are new with DB2 and just implemented our first PRODuction
DB2 system, accessing DB2 v5.1 (10/97 maint level) via DB2 Connect PE &
TCP/IP 3.2.
Problem 1:
We had an instance today where we were attempting to cancel a DDF
thread. DB2 told us the thread was canceled, but subsequent displays
showed it was still there. I'm wondering if anyone else has experienced
this problem and what suggestions you may have. Below are the log
messages for this problem....
-DIS THD(*)
DSNV401I - DISPLAY THREAD REPORT FOLLOWS -
DSNV402I - ACTIVE THREADS - 827
NAME ST A REQ ID AUTHID PLAN ASID TOKEN
SERVER RA * 12 OS2PIPE2.EXE I08141 DISTSERV 00B0 1799
V437-WORKSTATION=COAQ039, USERID=I08141,
APPLICATION NAME=OS2PIPE2.EXE
V445-0A18E0FA.BF01.002B21155341=1799 ACCESSING DATA FOR 10.24.226.182
DISPLAY ACTIVE REPORT COMPLETE

-CANCEL DDF THD(1799)
DSNL010I - DDF THREAD '1799' HAS BEEN CANCELLED
DSNL027I - SERVER DISTRIBUTED AGENT WITH 882
LUWID=0A18E0FA.BF01.002B21155341=1799
THREAD-INFO=I08141:COAQ039:I08141:OS2PIPE2.EXE
RECEIVED ABEND=04E
FOR REASON=00D3001A
DSNL028I - 0A18E0FA.BF01.002B21155341=1799 883
ACCESSING DATA FOR
LOCATION 10.24.226.182
IPADDR 10.24.226.182

-DIS THD(*)
DSNV401I - DISPLAY THREAD REPORT FOLLOWS -
DSNV402I - ACTIVE THREADS - 901
NAME ST A REQ ID AUTHID PLAN ASID TOKEN
SERVER RA * 12 OS2PIPE2.EXE I08141 DISTSERV 00B0 1799
V437-WORKSTATION=COAQ039, USERID=I08141,
APPLICATION NAME=OS2PIPE2.EXE
DISPLAY ACTIVE REPORT COMPLETE
DSN9022I - DSNVDT '-DIS THD' NORMAL COMPLETION

-CANCEL THD(1799)
DSNL022I - DDF THREAD '1799' WAS PREVIOUSLY CANCELLED

------------------------------------------------------------------------

Problem 2:
We finally decided to stop DDF in order to remove the thread, and move
on. Though DB2 appeared to confirm that DDF was stopped, MVS still
showed the started task as active, and we eventually canceled the
started task, resulting in a loss of the entire DB2 subsystem (which
didn't really hurt, as no tasks were active, but still not something we
wanted to do).
My question is the same as before: Has anyone experienced this and what
would you recommend to resolve.
The log of the commands follow....
-STO DDF
DSNL021I - STOP DDF COMMAND ACCEPTED
DSNL005I - DDF IS STOPPING
five minutes later, we tried....
-STO DDF MODE(FORCE)
DSNL021I - STOP DDF MODE(FORCE) COMMAND ACCEPTED
DSNL005I - DDF IS STOPPING
three minutes later, we finally rec'd....
DSNL006I - DDF STOP COMPLETE

However, the started task (DBP1DIST) was still active, as noted by this
display....
DSNV401I - DISPLAY THREAD REPORT FOLLOWS -
DSNV402I - ACTIVE THREADS - 058
NAME ST A REQ ID AUTHID PLAN ASID TOKEN
SERVER RA * 9006 OS2PIPE2.EXE I01738 DISTSERV 00B0 1460
V437-WORKSTATION=COAQ032U, USERID=I01738,
APPLICATION NAME=OS2PIPE2.EXE
DISPLAY ACTIVE REPORT COMPLETE

Why did DB2 indicate that DDF was stopped, but there was still an active
thread, and the started task was still active???

Your help would be appreciated. I am, of course, looking at IBMLink
also. Thank you.

--
Tracy Johnson
Guidant Insurance Group
515-267-5487