ADSM-L

Re: Message of activity log truncated to 250 with SELECT

2003-04-03 11:16:20
Subject: Re: Message of activity log truncated to 250 with SELECT
From: Andrew Raibeck <storman AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 3 Apr 2003 09:16:09 -0700
This problem is documented in APAR IC35194 (go to www.ibm.com and search
on the APAR number for details). I believe it will be fixed in a
forthcoming server PTF.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.eyebm DOT com (change eye to i to reply)

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




Christian Bagard <christian.bagard AT WANADOO DOT FR>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
04/03/2003 08:55
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Message of activity log truncated to 250 with SELECT



Hello,

Have somebody any idea :

Subject : Length (chars) of activity log messages

In TSM Database :
Table : Columns, Actlog, LENGTH of Message is specified to max 250.
Some messages are longer than 250.
By example : ANR8300E which is a drive error (with a long SENSE
00:01:xxxxxx, etc.)

With SELECT :
DSMADMC -id -pa SELECT MSGNO, LENGTH(MESSAGE) AS LNG, MESSAGE FROM ACTLOG
messages are 250 truncated

But not with Query which doesn't truncate the string (if the field in the
DB is really limited to 250, from where come the extra-datas used by Query
?)

It' possible to reproduce in easier way than a drive error (!) by sending
a long syntax select and search for
ANR2017I message, by example.

Thanks
Regards

Christian Bagard
SOS-Restore
Aix-en-Provence - France

<Prev in Thread] Current Thread [Next in Thread>