Hi Steve,
The force kills all attachements and connections... including the guy who 
did the force.

You could rerun the attach after the force aplications. You may also need 
another command to soak up the error as the session has been terminated (or 
just run the attach twice).

Regards,

Bruce Allen
GrapeVine I.T, Sydney
DB2 Certified Technical Expert DB2 for Clusters, DB2 - Data Replication, 
DB2 - DRDA



-----Original Message-----
From:   [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
Sent:   Thursday, 2 May 2002 2:31 PM
To:     [EMAIL PROTECTED]
Subject:        [DB2EUG] Force Applications problem

NT UDB 7.2

I am trying to write a small command file that 'cleans up' some problems we
have here.  So I have a file containing an attach, a Force, a drop db and
several other bits.

The attach works fine but the FORCE APPLiCATIONS ALL gives me a SQL30081N
and talks about a TCP/IP error.  The subsequent drop db fails saying I
supplied the wrong password.

If I comment out the force all is well so it looks as if the failed force 
is
'unattaching' from the server.  I don't really need to worry too much about
this as there are only one or two of us likely to be attached to this
particular machine but I wondered if there is a way to do this and why I 
get
the TCP/IP error in the first place. I can successfully attach to the node
and do all the usual bits.

Regards,

Steve T

-
:::  When replying to the list, please use 'Reply-All' and make sure
:::  a copy goes to the list ([EMAIL PROTECTED]).
***  To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
***  For more information, check http://www.db2eug.uni.cc
-
:::  When replying to the list, please use 'Reply-All' and make sure
:::  a copy goes to the list ([EMAIL PROTECTED]).
***  To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
***  For more information, check http://www.db2eug.uni.cc

Reply via email to