That makes senses, except that archivelog is less than 10% full.  If
both active log and archivelog were full, don't you get a crashed
system?  TSM did not reflect an error.

Too many mysteries. Not enough time.

>>> "Prather, Wanda" <wPrather AT ICFI DOT COM> 1/10/2011 10:55 AM >>>
Usually it's because the archivelog filesystem is full.
In V6, the active log file size in dsmserv.opt is just a starting
point, not a limit.
It's not preformatted in V6.
If the archivelog space fills, V6 just keeps writing to the active log
space.


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
Of David E Ehresman
Sent: Monday, January 10, 2011 8:29 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] TSM v6 active log filespace

Under what conditions will tsm try to increase the size of the active
log?  I thought it was preformated and then did not change in size?

The reason I ask is that I got a file system full error in errpt (AIX
5.3) for my tsm active log file system for a TSM that has been in use
for a couple of weeks now.

---------------------------------------------------------------------------
LABEL:          J2_FS_FULL
IDENTIFIER:     F7FA22C9

Date/Time:       Sun Jan  9 22:40:36 EST 2011
Sequence Number: 299563
Machine Id:      000A3CD8D600
Node Id:         tsm
Class:           O
Type:            INFO
Resource Name:   SYSJ2

Description
UNABLE TO ALLOCATE SPACE IN FILE SYSTEM

Probable Causes
FILE SYSTEM FULL

        Recommended Actions
        INCREASE THE SIZE OF THE ASSOCIATED FILE SYSTEM
        REMOVE UNNECESSARY DATA FROM FILE SYSTEM
        USE FUSER UTILITY TO LOCATE UNLINKED FILES STILL REFERENCED

Detail Data
JFS2 MAJOR/MINOR DEVICE NUMBER
003C 0002
FILE SYSTEM DEVICE AND MOUNT POINT
/dev/fslv19, /tsm/tsmlog