It looks like your server is running out of memory.  Some of the threads
are crashing, and message reading threads can't get started, therefore you
are seeing the Message number xxxx errors.

I had simular problems with this on AIX, when we were doing server to server
communications.  Restores from one server to another would cause my AIX
TSM server to eat memory and die.

hope this helps, your server level looks like a good candidate for upgrade.

bob

On Mon, Feb 24, 2003 at 05:50:23PM +0100, Jozef Zatko wrote:
> Hello guys,
>
> Can you help me please with following problem?
> I have TSM server v.4.1.1 on Win NT 4.0 SP6i (I know it is quite old)
> Recently (about two weeks ago) my server started to crash.
>
> Here is output from my activity log:
>
> 02/23/2003 18:32:26 ANR0987I Process 5 for EXPIRATION running in the
> BACKGROUND processed 1 items with a completion state of SUCCESS at
> 18:32:26.
> 02/23/2003 23:52:18 ANR9999D pkthread.c(962): Unable to create new Thread.
> CreateThread error.
> 02/23/2003 23:52:18 << Message number 8219 not available for language AMENG
> >>
> 02/24/2003 04:00:16 ANR2750I Starting scheduled command ADSMDB ( run
> adsmdb_backup ).
> 02/24/2003 04:00:16 ANR2102I Activity log pruning started: removing entries
> prior to 02/23/2003 00:00:00.
> 02/24/2003 04:00:16 ANR2017I Administrator RADO issued command: RUN
> adsmdb_backup
> 02/24/2003 04:00:16 ANR2017I Administrator RADO issued command: DELETE
> VOLHISTORY type=dbbackup todate=today-1 totime=now
> 02/24/2003 04:00:20 ANR2103I Activity log pruning completed: 364 records
> removed.
> 02/24/2003 04:00:22 ANR2467I DELETE VOLHISTORY: 1 sequential volume history
> entries were successfully deleted.
> 02/24/2003 04:00:22 ANR2017I Administrator RADO issued command: BACKUP DB
> type=full devclass=DLTCLASS scratch=yes volumenames=ADSMDB1,ADSMDB2 wait=no
> 02/24/2003 04:00:22 ANR2753I (ADSMDB):ANR2467I DELETE VOLHISTORY: 1
> sequential volume
> 02/24/2003 04:00:22 ANR2753I (ADSMDB):history entries were successfully
> deleted.
> 02/24/2003 04:02:07 ANR0984I Process 6 for DATABASE BACKUP started in the
> BACKGROUND at 04:02:07.
> 02/24/2003 04:02:07 ANR2280I Full database backup started as process 6.
> 02/24/2003 04:02:07 ANR1462I RUN: Command script ADSMDB_BACKUP completed
> successfully.
> 02/24/2003 04:02:07 ANR2753I (ADSMDB):ANR2280I Full database backup started
> as process
> 02/24/2003 04:02:07 ANR2753I (ADSMDB):6.
> 02/24/2003 04:02:07 ANR2753I (ADSMDB):ANR1462I RUN: Command script
> ADSMDB_BACKUP
> 02/24/2003 04:02:07 ANR2753I (ADSMDB):completed successfully.
> 02/24/2003 04:02:07 ANR2751I Scheduled command ADSMDB completed
> successfully.
> 02/24/2003 04:02:15 ANR1409W Volume ADSMDB1 already in use - skipped.
> 02/24/2003 04:03:10 << Message number 7838 not available for language AMENG
> >>
> 02/24/2003 04:03:10 << Message number 7837 not available for language AMENG
> >>
> 02/24/2003 04:03:11 << Message number 7833 not available for language AMENG
> >>
> 02/24/2003 04:03:11 << Message number 7833 not available for language AMENG
> >>
> 02/24/2003 04:03:11 << Message number 7833 not available for language AMENG
> >>
> 02/24/2003 07:43:18 ANR1412W Volume IP001 access mode is "unavailable".
> ---------------------------------------------------------------------------------------
>
> After message 02/24/2003 04:03:11 << Message number 7833 not available for
> language AMENG >> server crashed
> and restarted.
>
> No error message in dsmerror.log.
>
> After restarting the server I found this message in activity log:
>
> 02/24/2003 07:43:18 ANR0362W Database usage exceeds 96 % of its assigned
> capacity.
>
> Could this be a reason for crashing the server?
>
> Does somebody know, what means this message << Message number 7838 not
> available for language AMENG >>?
>
> Thank you for your help
>
>
>
> Ing. Jozef Zatko
> Login a.s.
> Dlha 2, Stupava
> tel.: (421) (2) 60252618