Question & Answer
Question
If there is a problem with the Guardium STAP on ZOS , what information must be gathered before contacting IBM Software Support?
Answer
When you encounter Guardium STAP issue on ZOS, please collect and attach the following with the requested parameters enabled and provide the output:
A) The output from the following procedure:
1) Add the following parameters to the parm file:
- ZIIP_TCP(N) -
TRACECOMPILE( Y ) -
STAP_LOG_EVENTS(Y) -
STAP_TRACE_POLICY(Y) -
2) Shut down S-TAP
3) Restart S-TAP
4) Run the command /F <stapstc>,STAP (where <stapstc> is the jobname of the STAP started task.
5) Execute problematic Db2 activity
6) Run the command /F <stapstc>,STAP again
7) Run the command /F <stapstc>,DDX
8) Shutdown S-TAP, capture the resulting job log, terse it and provide to tech support
9) Remove from the STAP parm file:
TRACECOMPILE( Y ) -
STAP_TRACE_POLICY(Y) -
STAP_LOG_EVENTS(Y) -
10) Change parm ZIIP_TCP(N) - to ZIIP_TCP(Y) - in parm file
11) Restart S-TAP
12) Provide screen shots of the activity executed in #5 from the appliance if shown in the appliance
Also provide full screen shots of the error, such as access violation on DB2 plans for a list of users, if error is seen in the Guardium appliance reports.
B. Upload maintenance listing for the customer's S-TAP implementation:
Provide the current product maintenance level via the TERSED output from an SMP/E LIST PTFS job run against the target zone.
Related Information
[{"Product":{"code":"SSMPHH","label":"IBM Security Guardium"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Guardium S-TAP for DB2 on z\/OS","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"10.1;9.1","Edition":"","Line of Business":{"code":"LOB24","label":"Security Software"}}]
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg22014577