Checking for dumps

If a dump occurs on your system, an error message is produced.

Procedure

On Windows
BIP2111 error message ( IBM® Integration Bus internal error). The error message contains the path to the MiniDump file in your errors directory.
On UNIX
BIP2060 error message (integration server terminated unexpectedly). Look in the directory where the integration node was started, or in the service user ID's home directory, to find the core dump file.
On z/OS®
- BIP2060 error message (integration server ended unexpectedly) from the main integration node address space. This message should be accompanied by one of the following messages and dump.
- IEF450I message in the syslog, or component's joblog, showing an abend code followed by a reason code, for example:
```
 IEF450I MQ83BRK DEFAULT - ABEND=S2C1 U0000 REASON=000000C4
```
  Look in the system's dump dataset hlq for the dump dataset, or search the syslog for the appropriate IEA611I message to find out the dump dataset name.
- IEA993I message in the syslog for a SYSMDUMP. Look in the started task user's directory for the coredump.pid file, as specified in the syslog:
```
 IEA993I SYSMDUMP TAKEN TO coredump.00500319
```
- An error message for an SVC dump; see Dumps on IBM Integration Bus for z/OS for further information on SVC dumps.