|
Short Description
|
requested trace enhancements
|
|
Entered
|
By:
PeteL
When: 1999-06-03 08:03:06 Build: 1.03.29M
|
|
Categories
|
Type:
Suggestion
Department: Product
Category:
Troubleshooting
|
Description
|
debugging in the operational environment is always a bit different than doing it in test. A couple of enhancements to the trace facility would greatly aid this endeavor.
1. selective template tracing by individual session (like the protocol trace does)
2. selective tracing by TESECTION name - this would allow broadscale (or selective, when used in combination with #1) tracing with minimal overhead when a problem is known to occur in a particular TESECTION, but is not reproduceable at will
3. in-core trace - provide for an in-core memory-only trace that could be dumped to disk in the event of an error (like CICS trace table) - this will eliminate the I/O overhead and related performance penalty of writing huge amounts of trace to disk. User would specify amount of memory to allocate to it, SS would just wrap when it got to the end. This whole idea may be impractical, but it's at least a thought.
|
|
|
|
Append
|
By: PeteL When: 1999-07-22 10:18:06 New Status:
Pending IE
|
|
Comment
|
4. allow tracing to be turned on via a TETRACE tag with access to all possible settings, e.g. turn on tracing for just "my" session, just a particular TESECTION, globally, datastream vs. template, etc.
|
|
|
|
Append
|
By: WindSurfer When: 1999-09-27 17:51:19 New Status:
Accepted
|
|
Comment
|
Sorry for the delay in responding--the trace options request has been accepted for enhancements-- many others have the same requirement...
|