IBM MQ Bridge to Salesforce messages

AMQSF000I

Usage: runmqsfb -m QMgrName -t TopicString -e EventName -p PushtopicName -d debugLevel -i interval -w WaitTime -f configFile -k killFile -r runtimeLogFile -n InstanceName -q SyncQName -sf InitialKeyFile -sp protectionMode or runmqsfb -f inputConfigFile -o outputConfigFile [-b] [-sf InitialKeyFile] \n -m Queue Manager Name -t MQ topic root -e Salesforce platform event name (can repeat) -p Salesforce pushtopic name (can repeat) -q Replay Status Queue name -n Instance name -i Monitor interval (0 to disable monitoring) -f Configuration file -o New configuration file -b Use environment variables during configuration -w Wait before fully starting -k Exit if <killFile> exists -r Runtime log file containing copy of stdout/stderr -sf File containing key used for password protection in configuration file -sp Password protection mode (0 for backwards compatibility; 1 otherwise) -d Debug level 0-2

AMQSF001E

Exception:

AMQSF002I

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

AMQSF003I

Exclusive access to queue <insert_0> obtained.

AMQSF004I

Will try to reestablish connection in <insert_0> seconds.

AMQSF005E

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

AMQSF006E

A fatal error has occurred. The program will now exit.

AMQSF007E

A maximum of <insert_0> pushtopics can be configured.

AMQSF008E

A maximum of <insert_0> platform events can be configured.

AMQSF009E

Message received on unexpected channel <insert_0>.

AMQSF010E

A JMS error occurred.

AMQSF011E

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

AMQSF012E

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

AMQSF013E

Error: Failed login to Salesforce.

AMQSF014W

Warning: Subscribing to MQ-created platform events is only possible when OAUTH attributes are configured.

AMQSF015W

Warning: Subscribing to MQ-created platform events is not enabled.

AMQSF016E

Error: Connection to Salesforce failed.

AMQSF017E

Error: Connection to Salesforce failed with timeout during handshake.

AMQSF018E

Error: Connection to Salesforce failed during <insert_0> with reason: <insert_1>.

AMQSF019E

Error: Connection to Salesforce failed during <insert_0> with an exception.

AMQSF020E

Error: Subscription to topic <insert_0> failed with reason <insert_1>.

AMQSF021E

Error: Subscription failed with reason: <insert_0>.

AMQSF022I

Connection to Salesforce may have reached an expiry time. Attempting to reconnect.

AMQSF023E

Error: Cannot read from configuration file <insert_0>.

AMQSF024E

Error: Cannot write to configuration file <insert_0>.

AMQSF025E

Error: Cannot write to file <insert_0>.

AMQSF026E

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

AMQSF027E

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

AMQSF028E

Error: Cannot parse configuration file .

AMQSF029E

Error: Cannot generate configuration file contents.

AMQSF030E

Error: Cannot parse message contents.

AMQSF031E

Error: Cannot parse synchronisation information on queue <insert_0>. You may need to empty the queue to recover ('CLEAR QLOCAL(<insert_0>)').

AMQSF032E

Error: The token at <insert_0> in the configuration file cannot be processed. It can only be updated by rerunning the configuration program. Perhaps there is an incorrect or missing protection key supplied.

AMQSF033E

Error: Bad value for option '<insert_0>'

AMQSF034E

Error: Bad option '<insert_0>'

AMQSF035E

Error: Publication on topic '<insert_0>' does not contain a text formatted message

AMQSF036E

Moving message to <insert_0> because it has reached the backout threshold.

AMQSF037E

Error: Publication to Salesforce on topic '<insert_0>' failed with status <insert_1> and reason <insert_2>

AMQSF038W

Ignoring unknown topic '<insert_0>'. Continuing anyway.

AMQSF039E

Error: Message has an incorrect format or does not have a topic. <insert_0>

AMQSF040E

Error: A unexpected Salesforce error has occurred. <insert_0>

AMQSF041E

Error: Log file <insert_0> already exists. Delete it before continuing.

AMQSF042I

Caught signal <insert_0>.

AMQSF043E

Cannot get exclusive access to <insert_0>. Another program may already have the queue open.

AMQSF044E

Queue <insert_0> is not configured for exclusive access. Redefine it with NOSHARE and DEFSOPT(EXCL) attributes.

AMQSF045E

Error: Bad value for attribute - please try again.

AMQSF046E

Error: Cannot open queue '<insert_0>'. Verify the Replay Status Queue exists.

AMQSF047E

Error: Attribute value must be at least <insert_0> - please try again.

AMQSF048E

A maximum of <insert_0> change data events can be configured.

AMQSF049W

Warning: Configuration attribute <insert_0> is protected using an old protection mode.

AMQSF050W

Warning: A password protection problem occurred. Code : <insert_0> Details : <insert_1>

AMQSF051E

Error: Cannot read key from file <insert_0>.

AMQSF052E

Error: A password protection error occurred. Code : <insert_0> Details : <insert_1>

AMQSF053W

Warning: Consider regenerating the configuration file.

AMQSF054W

Warning: Password protection is using a default key. Consider providing your own key and regenerating the configuration file.

AMQSF055W

Warning: Password protection keyfile is ignored when old protection mode is used.

AMQSF056E

Error: Initial key cannot be empty.

AMQSF057E

Error: Configuration has not been changed.