Message BIP8081 is issued when creating an
integration node
Procedure
Scenario: Message BIP8081E is
displayed when you are creating an integration node, the inserted
message does not format correctly, and the integration node is not
created.
Explanation: This problem occurs because you are
not a member of the correct group.
Solution: Read the explanation of message BIP8081,
and ask your IBM® Integration Bus administrator
to give your user ID access to the mqbrkrs group.
Message BIP8246 is issued when creating an integration node that is
configured to start as a WebSphere MQ service
Procedure
Scenario: Message BIP8246E is displayed when you are creating an
integration node that is configured to start and stop with the queue manager that is associated with
the integration node.
Explanation: You must be a member of the mqm group to
run the mqsicreatebroker command with the
-d parameter.
Solution: Ask your IBM Integration Bus administrator to give your
user ID access to the mqm group.
You cannot create files when creating an integration node on AIX
Procedure
Scenario: When you run the mqsicreatebroker command on IBM Integration Bus for AIX®, the following message is
displayed:
BIP8135E Unable to create files. Operating System return code 1
Explanation: The user ID that you create for IBM Integration Bus testing must have a primary
group of mqbrkrs. The following example
shows an AIX SMIT panel listing
the Change / Show Characteristics of a User:
Change / Show Characteristics of a User
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
[TOP] [Entry Fields]
* User NAME peterc
User ID [202] #
ADMINISTRATIVE USER? false +
Primary GROUP [mqbrkrs] +
Group SET [mqbrkrs,mqm,system,sys> +
The JCL BIPGEN fails when you create a component on z/OS®
Procedure
Scenario: The BIPGEN job fails when you are copying
the integration node profile BIPBPROF from the PDSE to the file system.
Explanation: The file system might lack the required
space, the component profile might not exist, or you might not have
the appropriate authority.
Solution: Make the following checks:
The file system has sufficient space. You can check how much space
is used and how much is free in a file system using the OMVS command df
-P /pathname. 100 MB is 3 276 800 512 byte sectors.
The profile file exists in the PDSE.
Your user ID has the appropriate authority to write to the file
system.
Your DataFlowEngine ends with an abend when you create an integration
node on HP-UX using Oracle
Procedure
Scenario: Your message flow (DataFlowEngine or DFE)
ends with an abend when you create an integration node on HP-UX using Oracle.
Explanation: This problem occurs when you have installed DB2®and Oracle on the same computer.
Solution: Remove the DB2 LIL files that are used by IBM Integration Bus. For example,
issue the following commands:
Error message BIP2624 is issued when creating
an integration server
Procedure
Scenario: When you create an integration server,
you get several BIP2624 messages (MQRC=2012 (MQRC_ENVIRONMENT_ERROR)),
and no WebSphere® MQ messages are processed.
Explanation: You have created the integration node
to run as a WebSphere MQ trusted application
(that is, the integration node runs in the same process as the WebSphere MQ queue manager), but the user
ID that you specified does not have the required authority.
Solution: If you request the trusted application
option on the mqsicreatebroker command
by specifying the -t parameter, perform the appropriate
steps for your operating system:
Windows
Using the -i parameter on the mqsicreatebroker command, specify
a service user ID that is a member of WebSphere MQ group mqm.
Linux and UNIX systems
Specify the user ID mqm on the -i parameter
on the mqsicreatebroker command.