Problems when starting resources

This section outlines some common problems that can arise when starting resources. It contains advice for dealing with the problems:

Resources terminate during startup

Resources hang at startup on Windows

You get BIP2228 messages when trying to start a second broker

Broker and execution group are not running after using the Getting Started wizard

The Getting Started wizard does not appear to have worked

You get BIP2322 Database error when starting or stopping a broker

You get error code BIP832 on startup

Broker fails to start on z/OS

There are a number of potential problems that might arise when trying to start a broker on z/OS and these are described in the following sections.

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

Your execution groups repeatedly restart

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 either 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 cannot start the Configuration Manager

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

Your components should now start.

MQIsdp client connection is refused by broker

You get abend code 047 and a diagnostic message

You get abend code 047 in bin/bipimain

You get message BIP2048

You get message BIP2604 or BIP2624 when starting a broker or a new message flow

You get a device allocation error

You get diagnostic ICH408I

When starting the broker through the Dataflowengine, it continually cycles

Broker abends on startup on AIX