What are the minimum recommend diagnostics for Server/studio Enterprise Edition?

Here is what we would suggest as the minimum diagnostics set to be requested when customers report Enterprise Server incidents.

Customers need to be made aware of these guidelines as early as possible.

N.B. All the following must be from the same run.

• A problem summary which describes the manifestation of the issue.
• Console.log
• An offline dump taken as close to the point of failure as possible (this should be generated even if the failure itself resulted in a dump – e.g. RTS error).
• Log.html
• Auxiliary trace if created (Running with aux trace active obviously has a performance impact and we would not expect it to have been generated at initial contact)

They should always be running with “Application” (API) and “Task Control” (KCP) trace flags set. With these flags set, the trace tables (SEP local and System) which will be included in the dump will show the most recent events. Turning on much more trace would swamp the tables and make them (probably) unusable.

What this will give us is either enough information to guide us to the issue or pointers to what the next level of trace should be.

In a batch environment the following information will be required:

• Console.log
• Joblog
• CTF Traces - "Minimum" traces would depend on the issue we're being asked to track.  

Depending on the problem area we would need different "minimums".  The following attempts to identify the following classifications by color:

Red - Mandatory  (all types)
Green - Issues with catalog and/or dataset allocation
Yellow - S806 Abends
Purple - Issues with Job Restart
Dark Blue - GDG Issues ( Green mvscatio) - need to also turn on "level" for mvsrgdg - currently in purple

################################################

# CASSPOOL Tracing

################################################

 

mftrace.level.mf.mvs.casspool           = debug

mftrace.comp.mf.mvs.casspool#restart    = true

 

 

################################################

# MVSRGDG Tracing

################################################

 

mftrace.level.mf.mvs.mvsrgdg            = debug

 

mftrace.comp.mf.mvs.mvsrgdg#entry      = true

mftrace.comp.mf.mvs.mvsrgdg#restart    = true

 

################################################

# JCL Tracing

################################################

 

mftrace.level.mf.mvs.mfjcl              = debug

 

mftrace.comp.mf.mvs.mfjcl#msgs          = true

mftrace.comp.mf.mvs.mfjcl#pgm           = true

 

################################################

# MJRM Tracing

################################################

 

mftrace.level.mf.mvs.mjrm               = debug

 

mftrace.comp.mf.mvs.mjrm#entry          = true

mftrace.comp.mf.mvs.mjrm#enq            = true

 

 

################################################

# MVSCATIO Tracing

################################################

 

mftrace.level.mf.mvs.mvscatio           = debug

mftrace.comp.mf.mvs.mvscatio#entry      = true

 

 

################################################

# RTS Tracing

################################################

 

mftrace.level.mf.rts                    = debug

 

mftrace.comp.mf.rts#pgmsearch         = true

mftrace.comp.mf.rts#pgmload           = true