Managed File Transfer REST calls are not permitted because the service is not enabled.
Response
Enable the MFT REST API and resubmit the request.
MQWB0401E
MQWB0401E: Transfer details cannot be found for transfer ID <insert_0>.
Explanation
The transfer for which the details were queried is not present. This might be because the transfer ID is invalid, or the transfer was initiated before the mqweb server was started, or the transfer contained too many files to be stored by the mqweb server.
Response
Resubmit the request with a valid transfer ID.
MQWB0402E
MQWB0402E: The coordination queue manager name is not set.
Explanation
The coordination queue manager name must be set before using the MFT REST API.
Response
Set the coordination queue manager name and restart the mqweb server.
MQWB0403E
MQWB0403E: An attempt to connect to the coordination queue manager <insert_0> failed. The root MQ reason code was <insert_1> : <insert_2>.
Explanation
The coordination queue manager must be running before using the MFT REST API.
Response
Start the coordination queue manager and resubmit the request.
MQWB0404E
MQWB0404E: The transfer with transfer ID <insert_0> has <insert_1> files. Transfers that have more than <insert_2> files cannot be stored by the mqweb server. Therefore this transfer cannot be retrieved by the MFT REST API.
MQWB0406E
MQWB0406E: The subscription thread for topic <insert_0> failed to connect to the coordination queue manager <insert_1>. The root MQ reason code was <insert_2> : <insert_3>.
MQWB0407E
MQWB0407E: The connection to the coordination queue manager <insert_0> is broken. The root MQ reason code was <insert_1> : <insert_2>. Ensure that the coordination queue manager is running before using the MFT REST API. A reconnection attempt will be made every 5 minutes until reconnection times out.
MQWB0408E
MQWB0408E: Agent details cannot be found for <insert_0>.
Explanation
The agent for which the details were queried is not present.
Response
Resubmit the request with a valid agent name.
MQWB0415E
MQWB0415E: The reconnect attempt to the coordination queue manager <insert_0> timed out after <insert_1> minutes for the subscription thread of topic <insert_2>. Failed to reconnect within the reconnection timeout period. No further attempts to connect to coordination queue manager will be made. The next reconnection attempt will be made only when the next MFT REST API call is received.
MQWB0416E
MQWB0416E: Subscription thread for topic <insert_0> failed to connect to the coordination queue manager <insert_1>. The root MQ reason code was <insert_2> : <insert_3>. Ensure that the coordination queue manager is running before using the MFT REST API. A reconnection attempt will be made every 5 minutes until reconnection times out.
MQWB0417I
MQWB0417I: Subscription thread for topic <insert_0> successfully established a connection to the coordination queue manager.
MQWB0418E
MQWB0418E: An attempt to create a subscription to topic SYSTEM.FTE failed. The root MQ reason code was <insert_0> : <insert_1>. Ensure that the topic is created on the coordination queue manager and has appropriate authorities. A reconnection attempt will be made every 5 minutes until reconnection times out.
MQWB0419E
MQWB0419E: An attempt to create a subscription to topic SYSTEM.FTE failed. The root MQ reason code was <insert_0> : <insert_1>.
Explanation
The SYSTEM.FTE topic must be created and have appropriate authorities before using the MFT REST API.
Response
Create the SYSTEM.FTE topic, set appropriate authorities, and resubmit the request.
MQWB0420E
MQWB0420E: The subscription thread for topic <insert_0> failed to create a subscription to SYSTEM.FTE topic. The root MQ reason code was <insert_1> : <insert_2>.
MQWB0421E
MQWB0421E: The connection to the coordination queue manager <insert_0> is broken for the subscription thread of topic <insert_1>.
MQWB0422E
MQWB0422E: The value <insert_0> is not valid for a resource monitor name.
Explanation
The resource monitor name supplied does not conform to the Managed File Transfer naming conventions. Resource monitor names must not contain asterisk (*), percent (%), or question mark (?) characters.
Response
Resubmit the request with a valid resource monitor name.
MQWB0423E
MQWB0423E: Cannot find the resource monitor <insert_0>.
Explanation
The REST API was invoked specifying a resource monitor name which cannot be located.
Response
Resubmit the request with the name of an existing resource monitor, or with no resource monitor name to retrieve a list of resource monitors.
MQWB0424E
MQWB0424E: User not authorized to connect to queue manager <insert_0>.
Explanation
The REST API was invoked for user which does not have authority to connect to queue manager.
Response
Provide required authority to user and resubmit the request.
MQWB0425E
MQWB0425E: User not authorized to subscribe to topic <insert_0>.
Explanation
The REST API was invoked for user which does not have authority to subscribe to specified topic.
Response
Provide required authority to user and resubmit the request.
MQWB0426E
MQWB0426E: The value <insert_0> is not valid for an agent name.
Explanation
The agent name supplied does not conform to the Managed File Transfer naming conventions. Agent names must not question mark (?) character.
Response
Resubmit the request with a valid agent name.
MQWB0427E
MQWB0427E: The value <insert_0> exceeds the maximum allowed nested levels for the query parameter <insert_1>.
Explanation
The value specified for the query parameter can have a maximum of three levels of nesting.
Response
Resubmit the request by removing either key name or subsection(s) and key name in the specified value for the query parameter. For example if the value specified is 'transferDefinition.transferSet.item.source.name', then limit the value to 'transferDefinition.transferSet.item' and retry the request.
MQWB0428E
MQWB0428E: The command queue manager name is not specified.
Explanation
The command queue manager name must be specified in mqwebuser.xml file before using the MFT REST API.
Response
Specify the command queue manager name using 'mqRestMftCommandQmgr=<queue manager name>' property in mqwebuser.xml file and restart the mqweb server.
MQWB0429E
MQWB0429E: Mutually exclusive attributes <insert_0> and <insert_1> specified in Managed File Transfer request.
Explanation
The named nested attributes are mutually exclusive for this type of transfer request.
Response
Resubmit the request with valid set of attributes.
MQWB0430E
MQWB0430E: An attempt to connect to the command queue manager <insert_0> failed. The root MQ reason code was <insert_1> : <insert_2>.
Explanation
The command queue manager must be running and have required authorities.
Response
Check the user authorities and queue manager status before resubmitting the request.
MQWB0431E
MQWB0431E: An attempt to submit transfer request on <insert_0> failed. The root MQ reason code was <insert_1> : <insert_2>.
Explanation
The command queue must be created and have appropriate authorities before using the MFT REST API.
Response
Check the authorities and other required attributes to submit the transfer request.
MQWB0432E
MQWB0432E: The attribute <insert_0> can only be specified with attribute <insert_1>.
Explanation
The specified attribute has a dependency on another attribute.
Response
Resubmit the request with a dependent attributes.
MQWB0433E
MQWB0433E: The transfer request contains more than one message splitting attributes.
Explanation
The transfer request contains multiple message splitting attributes specified which is not valid. Transfer request can contain only one of the valid message splitting attribute.
Response
Resubmit the request with valid attributes.
MQWB0434E
MQWB0434E: Invalid source and destination specification types.
Explanation
Either the source or destination specification of a transfer request can be queue but not both.
Response
Resubmit the request with valid attributes.
MQWB0435E
MQWB0435E: Invalid source and destination specifications.
Explanation
It is not valid to specify the same file name for both source and destination of a transfer request.
Response
Resubmit the request with valid attributes.
MQWB0436E
MQWB0436E: The value <insert_0> for <insert_1> must be between <insert_2> and <insert_3> characters long.
Explanation
A name was supplied for an MFT entity which does not conform to the naming conventions.
Response
Resubmit the request with a valid name.
MQWB0437E
MQWB0437E: The attribute <insert_0> is required.
Explanation
Mandatory attribute is missing.
Response
Resubmit the request with the required attribute.
MQWB0438E
MQWB0438E: The delimiter <insert_0> is not valid for <insert_1> mode of transfer.
Explanation
Attempt to specify an invalid delimiter for the transfer mode.
Response
Resubmit the request with an valid delimiter attribute.
MQWB0439E
MQWB0439E: The attribute <insert_0> cannot be specified along with <insert_1> for a Transfer request.
Explanation
The attribute is not appropriate for this type of transfer request.
Response
Resubmit the request with an appropriate value for the attribute.
MQWB0440E
MQWB0440E: The attribute <insert_0> is not valid for <insert_1> mode of transfer.
Explanation
Attempt to specify an invalid attribute for the transfer mode.
Response
Resubmit the request with an valid attribute.#
MQWB0441E
MQWB0441E: Error has occurred while parsing or validating start schedule or end schedule parameters.
Explanation
Verify the format of schedule parameters date and ensure end date will occur before the start date of the schedule transfer.
Response
Check the start schedule or end schedule parameters of schedule transfer and resubmit the command.
MQWB0442E
MQWB0442E: The attribute <insert_0> is not valid for <insert_1>.
Explanation
The REST API was invoked with invalid attribute.
Response
Resubmit the request with a valid list of attributes or attribute sections.
MQWB0443E
MQWB0443E: The values for attribute <insert_0> and <insert_1> are different.
Explanation
The REST API was invoked with different values for attributes. Same value must be specified for both attributes.
Response
Resubmit the request with same value specified for both attributes.
MQWB0444E
MQWB0444E: An attempt to create resource monitor with name <insert_0> in agent <insert_1> failed.
Explanation
The REST API was invoked to create a resource monitor with the name of an existing resource monitor.
Response
Resubmit the request with unique monitor name or delete the existing monitor before resubmitting.
MQWB0445E
MQWB0445E: An attempt to create resource monitor with name <insert_0> in agent <insert_1> failed.
Explanation
The REST API was invoked to create a resource monitor with the name of an existing resource monitor.
Response
Resubmit the request with unique monitor name or delete the existing monitor before resubmitting.