On Fri, Jul 26, 2013 at 12:59 AM, William H. Blair <wmhbl...@comcast.net>wrote:
> ...<snip>... and what things > you did (called) in your program then look like in the system trace, et al. > ...<snip>... > IMO, learning what each possible entry in the system trace table looks like, during normal system operation and during system stress or meltdown situations, goes a LONG way toward understanding what led up to and caused a problem, both for standalone, SVC and SYSUDUMP type dumps...trace table understanding is a very important dump reading skill. -- Mike Shaw MVS/QuickRef Support Group Chicago-Soft, Ltd.
