Guardium STAP for DB2 running on z/OS must-gather

Answer

Whenever opening a PMR for an issue related to the Guardium STAP for DB2 running on z/OS, please provide the following information:
• Guardium STAP Version/Release Level
• Guardium STAP Maintenance Level
• z/OS version/release
• DB2 version
• Brief description of the problem
• Basic description of the circumstances during which the defect occurs
• Exported of the policy if the problem is missing/unexpected events or performance
• Output from the DDX command (F stcname,DDX) where stcname is the collector agent started task
• Output from the STAP command (F stcname,STAP) where stcname is the collector agent started task
• Output from the STAP command (F stcname,STAP) where stcname is the collector agent started task about 15 seconds after issuing it the first time
• v81 only - Complete Started Task Log (all JES datasets associated with the agent agent started task)
• Complete Started Task Log (all JES datasets associated with the collector agent started task)
• Dump of the collector agent started task along with the DBM1 address space (DUMP (stcname,dbm1)) when the problem is occurring if the problem is CPU usage
• Console error messages (if any)
• Failing job listing (if applicable), or screen-shots of UI error messages
• Agent or Server log files (if applicable)
• Dump from the abend (if available)
• Configuration of collector agent (ADHCFGP member contents)