Micro Focus Visual COBOL 2.3 Update 2 for Eclipse (Windows)
>
Deployment
>
Deploying to Enterprise Server
>
Enterprise Server Reference
>
Error Messages
>
Enterprise Server Error Messages
>
CASPI Error Messages
>
CASPI0100 - CASPI0600
CASPI0100 - CASPI0600
CASPI0110E Date Time Applid An attempt to start transaction CPIH by something other than an attach request from web domain has been made. This is not allowed.
An attempt has been made to start transaction CPIH by some method other than a transaction attachment from a web domain. Transaction CPIH is a system task and cannot be entered from a terminal.
CASPI0111E Date Time Applid Tranid Call to WebSphere MQ function MQ function returned with reason code MQ reason code. Transaction abended.
A WebSphere MQ function call issued by transaction CPIL was unsuccessful and has set a non-zero reason code. The transaction CPIL is used to start a PIPELINE for a message received from WebSphere MQ.
CASPI0112E Date Time Applid Tranid Unable to locate URIMAP to match HOST Hostname and PATH Pathname. Unable to process inbound MQ message.
A WebSphere MQ message has been received on queue hostname and with target service pathname, but no match was found when attempting to locate a URIMAP with this host and path. No pipeline processing can be done for this WebSphere MQ message.
CASPI0113E Date Time Applid Tranid URIMAP urimap_name has been located for HOST hostname and PATH pathname, but does not have USAGE(PIPELINE). Unable to process inbound MQ message.
A WebSphere MQ message has been received on queue hostname and with target service pathname, and a matching URIMAP urimap_name was found. This URIMAP was not defined with USAGE(PIPELINE). As a result, no pipeline processing can be done for this WebSphere MQ message.
CASPI0114E Date Time Applid Tranid The pipeline MQ transport mechanism failed because a call to WebSphere MQ function MQ function returned with reason code MQ reason_code.
A WebSphere MQ function call issued by the pipeline MQ transport mechanism was unsuccessful and has set a non-zero reason code.
CASPI0115I Date Time Applid Tranid The service provider pipeline has returned a response message to the MQ transport, but the inbound request did not expect a response. The response message is ignored.
The WebSphere MQ transport module has been called by a provider pipeline to return a response. The inbound request did not expect a response, and was sent as a one-way request. There is no reply-to queue on which to place the response. There is a mismatch between the service requester and the service provider definitions of the service, as the service requester specified that the request was a one-way request.
CASPI0300E Date Time Applid CICS could not invoke WEBSERVICE WebService because it was unable to find container container_name.
The WEBSERVICE WebService could not be invoked because the container container_name was not found. An exception response from the program which gets the container was received.
CASPI0400E Date Time Applid Tranid The CICS pipeline HTTP transport mechanism failed to send a request because Reason Error. Problem occurred for URI URI.
The CICS pipeline HTTP transport mechanism was unable to successfully handle the outbound request because of described reason.
CASPI0403E Date Time Applid Tranid The CICS pipeline HTTP transport mechanism failed to receive a response because Reason Error. Problem occurred for URI URI.
The CICS pipeline HTTP transport mechanism did not successfully receive a response to the outbound request due to the reason indicated in the message.
CASPI0404E Date Time Applid Tranid A failure occurred in the CICS pipeline HTTP transport mechanism for PIPELINE Pipeline WEBSERVICE Web Service Name.
A failure occurred in the CICS pipeline HTTP transport mechanism for the named PIPELINE and WEBSERVICE.
CASPI0453E Date Time Applid Tranid The CICS transport manager encountered an error while trying to use URIMAP urimap_name.
The CICS transport manager was unable to use the URIMAP named in the message.
CASPI0454E Date Time Applid Tranid The CICS transport manager encountered an error while trying to use provider pipeline pipeline_name.
The CICS transport manager was unable to use the provider pipeline named in the message.
CASPI0500E Date Time Applid Tranid The CICS Pipeline Manager DFHPIPM encountered an error while trying to link to program Program. reason. PIPELINE: Pipeline.
The CICS Pipeline Manager, DFHPIPM, was unable to link to the given program, or the linked program abended.
CASPI0501E Date Time Applid Tranid The CICS Pipeline Manager cannot proceed as the pipeline is unusable. reason. PIPELINE: Pipeline.
The CICS Pipeline Manager DFHPIPM was unable to begin processing as the pipeline it has been invoked for is unusable.
CASPI0504E Date Time Applid Tranid The CICS Pipeline Manager has failed to communicate with a service provider due to an error in the underlying transport. TRANSPORT: Transport, PIPELINE: Pipeline.
The CICS Pipeline Manager DFHPIPM failed to communicate with a service provider due to an error in the underlying transport.
CASPI0506E Date Time Applid Tranid The CICS Pipeline Manager has failed to communicate with a remote server due to an invalid URI scheme being specified. URI: Uri, PIPELINE: Pipeline.
The CICS Pipeline Manager DFHPIPM failed to communicate with a remote server as a URI with an invalid scheme was provided. Before CICS can make a request to a remote server it must be provided with a URI identifying that server.
Parent topic:
CASPI Error Messages
