IBM MQ Bridge to blockchain messages

AMQBC001

Exception:

AMQBC002

The queue <insert_0> appears to be in use. Will retry in <insert_1> seconds.

AMQBC003

Exclusive access to queue <insert_0> obtained.

AMQBC004

Will try to restablish connection in <insert_0> seconds.

AMQBC005

Maximum reconnection attempts have been reached. The program will now exit.

AMQBC006

A maximum of <insert_0> locations can be configured.

AMQBC007

A JMS error occurred.

AMQBC008

Error: Disconnected from queue manager.

AMQBC009

Error: Cannot delete file <insert_0>. Reason: <insert_1>

AMQBC010

Found control file <insert_0>. Delete file before restarting bridge.

AMQBC011

Error: Failed login to Blockchain.

AMQBC012

Error: Cannot read from configuration file <insert_0>.

AMQBC013

Error: Cannot write to configuration file <insert_0>.

AMQBC014

Error: A configuration file name must be specified.

AMQBC015

Error: Cannot write to file <insert_0>.

AMQBC016

Error: Must provide a value for the runtime log file.

AMQBC017

Error: Unexpected data type <insert_0> in configuration file.

AMQBC018

Error: Cannot parse configuration file <insert_0>.

AMQBC019

Error: Cannot generate configuration file contents.

AMQBC020

Error: Cannot parse input message or there are missing fields in the message. Message must contain channel, chaincodeName, and a function name.

AMQBC021

Error: Cannot parse input message or there are missing fields in the message. Missing fields appear to be: <insert_0>

AMQBC022

Error: The password token at <insert_0> in the configuration file cannot be processed. It can only be updated by rerunning the configuration program.

AMQBC023

Error: Cannot open queue <insert_0>

AMQBC024

Error: Bad syntax for location <insert_0>. Must be of form "servicename address:port". For example, "peer0 127.0.0.1:7051" or "peer4 localhost:7056".

AMQBC025

Error: Bad syntax for the CA location <insert_0>. Must be of form "address:port".

AMQBC026

Error: Bad syntax for location <insert_0>. Must be of form "servicename address:port". For example, "peer0 127.0.0.1:7051" or "peer4 localhost:7056".

AMQBC027

Error: Cannot read file <insert_0>

AMQBC028

Error: There is no reply queue in the input message

AMQBC029

Error: Input message does not appear to be TEXT format

AMQBC030

Error: Unexpected response from REST server: <insert_0>

AMQBC031

Error: Blockchain operation failure

AMQBC032

Error: Bad value for option '<insert_0>'

AMQBC033

Error: Bad option '<insert_0>'

AMQBC034

Error: Bad value for attribute - please try again.

AMQBC035

Error: Unsupported queue manager command level <insert_0> - should be <insert_1>.

AMQBC036

Error: The MQ to BlockChain bridge requires an enablement APAR to run. Consult the Knowledge Center for further details.

AMQBC037

Error: Operation timed out after <insert_0> seconds

AMQBC038

Error: The queue manager must have the "advanced" license capability.

AMQBC039

Error: The organisation name and MSP Id must be provided.

AMQBC040

Error: Failed to initialise channel <insert_0> with error: <insert_1>

AMQBC041

Error: Check the configuration for bad hostnames. Bridge will now end.

AMQBC042

Error: No peer event locations are configured.

AMQBC043

Error: Not authorized. <insert_0>

AMQBC044

Error: Resource not found or not authorized. <insert_0>

AMQBC045

Error: Cannot configure TLS keystores

AMQBC046

Expected only one set of consistent proposal responses but got <insert_0>

AMQBC047

Update transaction with txid <insert_0> failed with error: <insert_1>

AMQBC048

Update failed with <insert_0>. Exception <insert_1>

AMQBC049

Update was not confirmed because of a timeout. It may have succeeded.

AMQBC050

No responses returned from peers.

AMQBC051

Cannot verify signature on response from peer.