Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+TSM\s+5\.4\s+traceflagss\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+TSM\s+5\.4\s+traceflagss\s*$/: 2 ]

Total 2 documents matching your query.

1. [ADSM-L] TSM 5.4 traceflagss (score: 1): Author: David E Ehresman <deehre01 AT LOUISVILLE DOT EDU>; Date: Thu, 22 Jan 2009 13:30:21 -0500; In older versions of TSM "insturment:detail" used to give you diagnostic information like this: Detailed Instrumentation statistics for Thread: 6328 Elapsed time 20937,580 sec Section Actual (sec) Av; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-01/msg00286.html (11,737 bytes)
2. Re: [ADSM-L] TSM 5.4 traceflagss (score: 1): Author: Erwann Simon <erwann.simon AT FREE DOT FR>; Date: Thu, 22 Jan 2009 20:47:21 +0100; Hi, Just put the "testflag instrument:detail" in your dsm.sys or dsm.opt (or use it as an option (whith a preceding dash) for dsmc. Note there is now one tsminstr.report file created by operation, wi; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2009-01/msg00288.html (12,481 bytes)

Current List: 1 - 2
Page: [1]