SLIP traps in systems in a sysplex

For a sysplex containing similar systems, certain problems might require identical SLIP traps on those similar systems. To set up these traps, do the following:

Assign similar names to identical jobs on different systems. The names should form a pattern, such as JOB1, JOB2, JOB3, and so on.
Create one IEASLPxx member containing the trap you need for the problem.
Use a REMOTE parameter in the SLIP command so that, the first time a trap matches on a system, the action will also be taken on other systems in the sysplex. For example, the SLIP command could request a dump on its system and, through REMOTE, on all the similar systems.

Use an IDGROUP parameter so that, after the match, the identical traps on the other systems will be disabled.

Use wildcards in parameters so that the command will process in all systems in the sysplex. For example, JOB? would indicate JOB1, JOB2, JOB3, and so on.
Place the member in the shared parmlib data set or in the parmlib data set for each of the similar systems.
In systems using JES2 or JES3, activate the member or members with the following command entered on one of the systems:
```
ROUTE *ALL,SET SLIP=xx
```
If only some systems in the sysplex are similar, use a ROUTE command specifying a named subset of systems; see ROUTE command for details.

When a SLIP trap results in SVC dumps from multiple systems, each dump contains the same incident token. You can use the incident token to correlate the multiple dumps to one problem.