Collecting documentation to submit to the IBM Support Center
If your storage problem is caused by TCP/IP common or private storage usage, ensure that you have a dump of TCP/IP; IBM® service will need to review it. If you did not get a system dump for the abend, or if you want to obtain a dump of TCP/IP to perform a storage analysis, use the following table for commands you can issue.
Commands | Type of dump |
---|---|
where xxx equals the abend code you are receiving (for example,
878). |
SLIP DUMP of the abend |
where xxx equals the abend code you are receiving (for
example, 878). |
SLIP dump of the abend if your storage problem is related to TCP/IP's CSM storage usage (includes the CSM data spaces in your dump). |
|
Console dump of TCP/IP |
where zzzzz causes a dump when the message identified in the slip is issued
(that is, CSM message IVT5562I). |
MSGID slip can be used to take a dump when a particular message is issued. |
|
Console dump when the storage problem is related to CSM storage usage (includes CSM data spaces). |
|
Dump of TCP/IP and any TCP/IP related applications that may be having storage problems (for example Omproute, FTP) |
Note: Wildcards (*) allow you to use a single specification
to indicate a number of address spaces whose names match the wildcard
pattern. This can be useful if you need to dump multiple TCP/IP stacks.
You can specify a wildcard on the JOBLIST and DSPNAME parameters
of a SLIP. And, the JOBNAME and DSPNAME parameters of the console
dump command. For information about how to use wildcards in a SLIP
and DUMP command, see z/OS MVS System Commands.
Submit the console log, and all dumps to the IBM Support Center for review.