Sorry, code levels as below:
Server: TSM 4.2.0.0 on AIX 4.3.3
Client: TSM 4.2.0.0 on NT4
DB2:v7 fixpack 5
Qlogic FC catd is at firmware 1.61 and driver 8.00.08
On the client side there is nothing in the dsmerror.log other than
20-05-2002 22:33:11 sessRecvVerb: Error -72 from call to 'readRtn'.
20-05-2002 22:33:11 cuConfirm: Received rc: -72 trying to receive
ConfirmResp verb
20-05-2002 22:33:12 sessSendVerb: Error sending Verb, rc: -1
20-05-2002 22:33:12 sessRecvVerb: Error -72 from call to 'readRtn'.
20-05-2002 22:33:12 cuConfirm: Received rc: -72 trying to receive
ConfirmResp verb
20-05-2002 22:33:12 sessSendVerb: Error sending Verb, rc: -1
From dsmrc.h:
/*--
-*/
/* Return codes (-71)-(-90) are reserved for CommTSM error codes
*/
/*--
-*/
#define DSM_RC_TSM_ABORT -72 /* Session aborted abnormally
*/
In the dsmaccnt.log
4,0,ADSM,05/20/2002,22:34:30,DB2RSLTSBDC1001_DB2,,DB2/NT,1,Named
Pipe,0,0,0,0,0,0,0,0,0,12696744,2008,2,1731,52,4,0,0,0,0,2,0
4,0,ADSM,05/20/2002,22:35:15,DB2RSLTSBDC1001_DB2,,DB2/NT,1,Named
Pipe,0,0,0,0,0,0,0,0,0,11574426,1924,2,1655,51,4,0,0,0,0,2,0
Nothing in the dsmsched.log since the DB2 backups aren't under the
scheduler's control.
On the Server side of things:
Sessions aborted abnormally, however there are no related errors in the
server log, only the following warnings:
ate/Time Message
--
05/20/02 22:01:07 ANR0406I Session 25934 started for node
DB2RSLTSBDC1001_-
DB2 (DB2/NT) (Tcp/Ip 10.255.128.226(4315)).
05/20/02 22:34:01 ANR0480W Session 25934 for node DB2RSLTSBDC1001_DB2
(DB2/NT) terminated - connection with client
severed.
Sessions start then terminate some time later.
The only other error/warning in the acct log is:
05/20/02 22:35:46 ANR8264W (Session: 25948, Origin:
DB2RSLTSBDC1001_STA)
Error reading data on Named Pipes, session 242.
ReadFile
return code is 233.
05/20/02 22:35:46 ANR8264W (Session: 25948, Origin:
DB2RSLTSBDC1001_STA)
Error reading data on Named Pipes, session 242.
ReadFile
return code is 233.
05/20/02 22:35:46 ANR8264W (Session: 25948, Origin:
DB2RSLTSBDC1001_STA)
Error reading data on Named Pipes, session 246.
ReadFile
return code is 233.
ANR8264W (Windows NT) Error reading data on Named Pipes, session session
number. ReadFile return code is return code.
Explanation: The server experiences an error return code from the ReadFile
Windows NT API while reading data from Named Pipes in the indicated
session. This may be a normal event if either side of the connection is
ended abruptly.
System Action: The session is ended. Server operation continues.
User Response: If the session is ended as a result of intentionally
stopping either the client or server, no response is required.
This is apparently an extraneous error fixed as of clinet v4.2.1.0 (we are
at 4.2.0.0)
IC30272 ANR8264W ...ERROR READING DATA ON NAMED PIPES, SESSION 22153844
SYSROUTES:
An extraneous Named Pipe Read error may be reported
when a session is cancelled for exceeding the idle time
out period or is cancelled by administrative command.
The P3A server IdleTimeOut is currently set at 60 minutes. CommTimeOut is
also one hour.
No session lasted more than about 30 minutes.
-Original Message-
From: Dave Canan [mailto:[EMAIL PROTECTED]]
Sent: 15 May 2002 17:00
To: [EMAIL PROTECTED]
Subject: Re: DB2 backup RC=157
Check to see if the activity log contains any error messages. I
have seen these errors before when TSM is trying to mount a volume for the
DB2 backup that has been marked read-only. Also, what is your DB2 fixpack
level? Your TSM level?
At 04:43 PM 5/15/2002 +0100, you wrote:
*SMers,
Our DBAs are having a few problems backing up a DB2 database to a TSM 3590
tape pool via LANfree. There are no errors in the dsmerror.log on the
client, nor any indicated errors in the server actlog, nor any errors in
the
NT Event Viewer that could be related.
The storage agent is running fine and not prodg any errors.
When our DBAs run
db2= backup db dbtest use TSM open 2 sessions
they get an error message in the DB2 logs:
SQL2025N An I/O error '157' occurred on media 'TSM'
In the API messages it merely states that the transaction will be aborted:
In dsmrc.h
#define DSM_RC_WILL_ABORT 157 /* Transaction will be
aborted */
Which doesn't really indicate what cause the abort. Any ideas/suggestions
appreciated?
Ta,
Matt
LTSB Storage Support
* internal.7-430-3213
* external. 020-7922-3213
* fax020-7922-3302
* e-mail
