Requesting data sharing environment DB2 SLIP traps
In a DB2® data sharing environment, a hang or problem on one DB2 member might originate in a separate member. To find the problem, you need to create a serviceability level indication processing (SLIP) trap to catch error events and to create supervisor call (SVC) dumps.
Before you begin
Be sure to set up the IEASLPxx member
in the SYS1.PARMLIB partitioned data set. Before activating the SLIP
trap, disable all existing program event recordings (PER) SLIP traps
for each system image in the data sharing group. For example, use
the following command, where trap-id identifies
the SLIP trap:
ROUTE *ALL,SLIP MOD,DISABLE,ID=trap-id
Procedure
Results
When the conditions that you defined in the SLIP trap occur, matching dumps are produced based on the wildcard specification in the IEASLPxx member.