Resolving problems when starting resources

This topic contains advice for dealing with some common problems that can arise when starting resources:

The broker and execution group are not running after using the Default Configuration wizard

The broker or Configuration Manager fails to start because there is not enough space in the Java TMPDIR directory

Start of change

The broker fails to start when installed on HP-UX with Oracle and DB2

End of change

Error message BIP2048 is issued on z/OS when your broker fails to start

Diagnostic message ICH408I is issued on z/OS when your broker fails to start

Abend code 047 is issued with a diagnostic message

Abend code 047 is issued in bin/bipimain

Database error message BIP2322 is issued when you start or stop a broker on Linux or UNIX

Error message BIP2228 is issued when you try to start a second broker on Linux or UNIX

MQIsdp client connection is refused by the broker

Error messages BIP2604 or BIP2624 are issued when you start a broker or a new message flow

When you start the broker through the Dataflowengine, it cycles continually

The broker terminates with an abend on startup on AIX

You have changed your logon password and cannot start your Configuration Manager or broker

Your components should now start.

Error message BIP0889 is issued when you connect to the Configuration Manager

Connection to the Configuration Manager is slow

Resources terminate during startup

Resources hang at startup on Windows

Error message BIP8048 is issued when you start a component

You get a "Not Found" error when you click a link to the Samples Gallery, or a specific sample

Start of change

The Quick Tour displays as a blank window

End of change

Error message BIP0832 is issued on startup

Your execution groups restart repeatedly

You cannot tell whether startup is complete on z/OS

The infrastructure main program bipimain is the first process in every address space. It starts bipservice, bipbroker, DataFlowEngine, or bipuns as the second process in the same address space. For each execution group, an additional address space is started. In this example, only one execution group is available.

You get abend code 0C1 when trying to start the data flow engine on z/OS

Error message BIP2604 with return code MQRC_CONNTAG_IN_USE is issued during the start of a message flow on z/OS

You cannot start the User Name Server

A device allocation error is issued

The create command fails and error message BIP8022 is issued

Related concepts
Brokers
Broker domains