WebSphere Message Brokers
File: au13580_
Writer: Jane Brockbank Task topic This build: July 31, 2007 21:39:07
Have you made any changes since the last successful run?
When you are considering changes that might have been made recently,
think not only about WebSphere Message Broker, but also
about the other programs with which it interfaces, the hardware, device drivers,
and any new applications.
Have you changed your initialization procedure?
On z/OS, have you changed any data sets or library
definitions? Has the operating system been initialized with different parameters?
Check for error messages generated during initialization.
Has the profile of the user who is running the commands on Linux or UNIX systems
been changed?
If so, this might mean that the user no longer
has access to the required objects and commands.
Has any of the software on your system been upgraded to a later
release?
Check that the upgrade completed successfully,
and whether the new software is compatible with WebSphere Message Broker (check
the product readme.html file).
Do your message flows deal with the errors and return codes
that they might get as a result of any changes that you have made?
Check that your message flow can handle all possible error situations.