>>From:         "Byron D. Graham" <uskimwvm AT IBMMAIL DOT COM>
>>Subject:      trace act file

>>Our DSMSERV machine went inactive over the weekend. Apparently his dis
>>filled up because of a cancerous file named 'TRACE ACT'. The disturbin
>>thing is we can't figure out when this file got created, how or why it
>>got started, who enabled the trace, what kind of trace it is, etc. etc

>>Has anyone else encountered this file ? A sample of the output looks lke
>>this (naturally, timestamps would be TOO helpful):

>> <1778>BUF(379): Latch database page 31, mode = S
>> <1778>BUF(379): Latch database page 26751, mode = S
>> <1778>BUF(1730): Getting buffer for database page=26751.
>> <1778>BUF(562): Unlatching database page 31 (Clean).

------------------------ reply separator -------------------------------
Byron,
Byron,

From your description, it looks like the trace flag DBBUF was set.  ADSM
does not automatically turn on traces unless you specifically set them.

AS far as finding out what might have happened, check your activity log
and your console log to see if there are indications of the trace being
activated.

Check to see if your server was recycled before or during the weekend.
If that is the case, please see if tracing has been activiated via the
server option file.  You would want to look for "trace begin ..." &
"trace enable .." statements in your option file.

The TRACE ACT file is defined by the "tracefile " statement in your
server option file, if one is specified.  This is the output file for
the trace.  If one is not specified, the trace output goes to the
console by default.

The long and short of this is that the trace was turned on at your
installation for some reason by someone.  ADSM does not do this auto-
matically.  Hope this helps.

Bill Chang
ADSM Technical Support