DFHPIxxxx messages

Start of changeDFHPI0001End of change
Start of changeapplid An abend (code aaa/bbbb) has occurred at offset X'offset' in module modname.End of change
Start of change
Explanation:

An abnormal end (abend) or program check has occurred in module modname. This implies that there may be an error in the CICS code. Alternatively, unexpected data has been input, or storage has been overwritten.

The code aaa/bbbb is a 3-digit hexadecimal MVS code (if applicable), followed by a 4-digit alphanumeric CICS code. The MVS code is a system completion code (for example, 0C1 or D37). If an MVS code is not applicable, this field is filled with three hyphens. The CICS code is an abend code or a number referring to a CICS message (for example, AKEA is a CICS abend code; 1310 refers to message DFHTS1310).

End of change
Start of change
System action:

An exception entry is made in the trace table. A system dump is taken, unless you have specifically suppressed dumps in the dump table.

CICS continues unless you have specified in the dump table that CICS should terminate. If appropriate, an error return code is sent to the caller of this domain. In this case CICS could be terminated by the caller ( for example, the domain manager, DFHDMDM). A message is issued to this effect.

Message DFHME0116 is normally produced containing the symptom string for this problem.

End of change
Start of change
User response:

Notify the system programmer. If CICS is still running, it is necessary to decide whether to terminate CICS.

Look up the MVS code, if there is one, in the relevant MVS codes manual.

Next, look up the CICS alphanumeric code. This tells you, for example, whether the error was a program check, an abend, or a runaway, and may give you some guidance concerning user response.

If module modname is not crucial to the running of your CICS system, you may decide to continue and bring CICS down at a convenient time to resolve the problem.

If you cannot continue without the full use of module modname you should bring CICS down in a controlled shutdown.

You need further assistance from IBM to resolve this problem. See CICS® Problem Determination Guide for guidance on how to proceed.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHPIDM, DFHPIWTEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changeaaa/bbbb,End of changeStart of changeX'End of changeStart of changeoffset', End of changeStart of changemodnameEnd of change

Start of changeDFHPI0002End of change
Start of changeapplid A severe error (code X'code') has occurred in module modname.End of change
Start of change
Explanation:

An error has been detected in module modname. The code X'code' is the exception trace point ID which uniquely identifies what the error is and where the error was detected. For further information about CICS exception trace entries, refer to the CICS Problem Determination Guide.

End of change
Start of change
System action:

An exception entry (code code in the message) is made in the trace table. A system dump is taken, unless you have specifically suppressed dumps in the dump table.

CICS will continue unless you have specified in the dump table that CICS should terminate.
If appropriate, an error return code is sent to the caller of this domain. In this case, CICS could be terminated by the caller (for example, the domain manager, DFHDMDM). A message will be issued to this effect.

Message DFHME0116 is normally produced containing the symptom string for this problem.

End of change
Start of change
User response:

Inform the system programmer. This indicates a possible error in CICS code. The severity of its impact will depend on the importance of the function being executed at the time of the error.

CICS may not have been terminated.

If the message occurs once and module modname is not crucial to the running of your CICS system, you may decide to continue to run and bring CICS down at a convenient time to resolve the problem.

If the message recurs or if you cannot run without the full use of module modname, you should bring CICS down in a controlled shutdown.

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHPIDM, DFHPIST, DFHPIWTEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changeX'End of changeStart of changecode',End of changeStart of changemodnameEnd of change

Start of change
DFHPI0004
applid A possible loop has been detected at offset X'offset' in module modname.
Explanation:

A CICS function is taking more time to process than CICS expects. A possible loop has been detected in module modname at offset X'offset'. This is the offset of the instruction which was executing at the time the error was detected.

System action:

An exception entry is made in the trace table. A system dump is taken, unless you have specifically suppressed dumps in the dump table.

Either this is a critical error and CICS is terminated, even if you have specified in the dump table that CICS should not terminate.

Or CICS will continue unless you have specified in the dump table that CICS should terminate. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

Notify the system programmer. If CICS has not been terminated, it will be necessary to decide whether the problem is serious enough to bring CICS down.

This may not be an error as some CICS functions can use a lot of processor time, and this message may have been caused by a long-running function.

Usually, CICS will purge a CICS function which exceeds the runaway task time interval which you have specified in the SIT (this is the ICVR parameter, which is measured in milliseconds). This means that the module modname will be terminated and CICS will continue.

If you have declared ICVR=0 in the SIT and you consider that module modname has gone into a loop, you will have to terminate CICS in order to terminate the runaway function.

If CICS has terminated module modname, and you consider that it was not a runaway function, you should increase the ICVR time interval in the SIT. You will have to bring CICS down at a suitable time to do this permanently. You can change the ICVR time interval temporarily online, using the CEMT transaction.

If raising the ICVR time does not solve the problem, you need further assistance from IBM to resolve this problem.

Destination:

Console

Modules:

DFHPIRM

XMEOUT Parameters: applid, X'offset', modname

Start of changeDFHPI0110End of change
Start of changedate 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.End of change
Start of change
Explanation:

An attempt has been made to start transaction CPIH by some method other than a transaction attach from web domain. Transaction CPIH is a system task and cannot be entered from a terminal.

End of change
Start of change
System action:

The CPIH transaction has not been started.

End of change
Start of change
User response:

Do not attempt to enter CPIH from a terminal or from any other device. CICS will start the transaction if a PIPELINE request is made via a TCP/IP attached client. No user action is required.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIDSHEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplidEnd of change

Start of changeDFHPI0111End of change
Start of changedate time applid tranid Call to Websphere MQ function function returned with reason code reason_code. Transaction abended.End of change
Start of change
Explanation:

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.

End of change
Start of change
System action:

The transaction is abended with abend code APIJ.

End of change
Start of change
User response:

Check the Websphere MQ reason code in the MQ Messages and Codes manual, and examine the trace to determine why the MQ function call failed. You may need help from IBM to resolve this problem.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPILSQEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranid, End of changeStart of changefunction, End of changeStart of changereason_codeEnd of change

Start of changeDFHPI0112End of change
Start of changedate time applid tranid Unable to locate URIMAP to match HOST hostname and PATH pathname. Unable to process inbound MQ message.End of change
Start of change
Explanation:

A Websphere MQ message has been received on queue hostname and with targetService 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.

End of change
Start of change
System action:

The inbound message is placed on the Dead Letter Queue and a report message is sent to the ReplyTo queue.

End of change
Start of change
User response:

Define and install a suitable URIMAP to match this combination of host and path which will identify the PIPELINE (and optionally WEBSERVICE) to process requests using this combination of queue name and targetService.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPILSQEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranid, End of changeStart of changehostname, End of changeStart of changepathnameEnd of change

Start of changeDFHPI0113End of change
Start of changedate time applid tranid URIMAP urimapname has been located for HOST hostname and PATH pathname, but does not have USAGE(PIPELINE). Unable to process inbound MQ message.End of change
Start of change
Explanation:

A Websphere MQ message has been received on queue hostname and with targetService pathname, and a matching URIMAP urimapname was found. However, this URIMAP was not defined with USAGE(PIPELINE). Therefore, no pipeline processing can be done for this Websphere MQ message.

End of change
Start of change
System action:

The inbound message is placed on the Dead Letter Queue and a report message is sent to the ReplyTo queue.

End of change
Start of change
User response:

Define and install a suitable URIMAP to match this combination of host and path with USAGE(PIPELINE) which will identify the PIPELINE (and optionally WEBSERVICE) to process requests using this combination of queue name and targetService.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPILSQEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranid, End of changeStart of changeurimapname, End of changeStart of changehostname, End of changeStart of changepathnameEnd of change

Start of changeDFHPI0114End of change
Start of changedate time applid tranid The pipeline MQ transport mechanism failed because a call to Websphere MQ function function returned with reason code reason_code.End of change
Start of change
Explanation:

A Websphere MQ function call issued by the pipeline MQ transport mechanism was unsuccessful and has set a non-zero reason code.

End of change
Start of change
System action:

The pipeline MQ transport mechanism returns an exception response to the pipeline manager which performs further error processing.

End of change
Start of change
User response:

Check the Websphere MQ reason code in the MQ Messages and Codes manual, and examine the trace to determine why the MQ function call failed. You may need help from IBM to resolve this problem.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPITQ1End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranid, End of changeStart of changefunction, End of changeStart of changereason_codeEnd of change

Start of change
DFHPI0115
date time applid tranid The service provider pipeline has returned a response message to the WebSphere MQ transport, but the inbound request did not expect a response. The response message is ignored.
Explanation:

The Websphere MQ transport module has been called by a provider pipeline to return a response. However, the inbound request was one-way only and did not expect a response. Therefore, there is no reply-to queue on which to place the response. There is probably 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.

System action:

The response is ignored by the Websphere MQ transport module. The transport module returns control to the pipeline manager with no error indication, and pipeline processing completes normally.

User response:

Check the definitions of the web service in the service requester and service provider and ensure that both indicate one-way request, or both indicate a reply is expected.

Destination:

CPIO

Modules:

DFHPITQ1

XMEOUT Parameters:date, time,applid, tranid .

End of change
Start of change
DFHPI0116
date time applid A one-way request has been received as a WebSphere MQ persistent message, but the provider pipeline has abended or backed out changes to recoverable resources. The BTS process "processname" of processtype "processtype" has completed with status ABENDED and this process can be retried or used to provide information for reporting the "failure"
Explanation:

A one-way SOAP message has been received as a persistent WebSphere MQ message, but the provider pipeline has abended or forced a backout of changes to recoverable resources. As there is no reply to queue, there is no way of informing the requester of the failure. A BTS process "processname" in completion state ABENDED contains information about the original WebSphere MQ message, and this process and its containers can be used to retry the failing provider pipeline, or to report the failure appropriately.

System action:

CICS has kept the information necessary to retry the failing provider pipeline in the named process. CICS takes no further action for the process.

User response:

A user-written transaction can ACQUIRE the PROCESS named in the message and take appropriate installation defined action. This could include one or more of the following:

After recovering any necessary information for reporting or logging the failure, the PROCESS can be cancelled with a CANCEL ACQPROCESS.

Destination:

CPIO

Modules:

DFHPIDSQ

XMEOUT Parameters:date, time,applid

End of change
Start of change
DFHPI0117
date time applid BTS process "processname" of processtype "processtype", which has completed with status ABENDED, has been cancelled. A provider pipeline started with a persistent WebSphere MQ message has abended or backed out, but a response has been sent to the requester.
Explanation:

A provider pipeline was started by a persistent WebSphere MQ message, and a BTS process was created to ensure that the information was not lost on a system failure. The provider pipeline abended or backed out changes to recoverable resources, and the BTS process completed with status ABENDED. A response message has been returned to the requester (in the form of a WebSphere MQ message on the reply-to queue), so the requester is aware of the failure and can take appropriate action. The BTS process in the provider system has been cancelled, as there is no longer any need to retain it. Earlier message DFHBA0104 reported the ABENDED state of the process.

System action:

CICS cancels the process that completed with status ABENDED. All the data associated with the process is removed.

User response:

None. This is an informational message, indicating that the process that completed with status ABENDED has been cancelled. CICS has sent a response to the requester indicating the failure.

Destination:

CPIO

Modules:

DFHPIDSQ

XMEOUT Parameters:date, time,applid

End of change
Start of change
DFHPI0118
applid CICS has attempted to use BTS processes to support pipelines started with WebSphere MQ persistent messages. This attempt failed. CICS will continue, using channel-based containers for the pipeline, but there is a risk of data loss in the even of a system failure. Ensure that BTS PROCESSTYPE, repository, and local request queue are correctly defined and installed.
Explanation:

A persistent WebSphere MQ message has been received to start a CICS provider pipeline, and CICS has attempted to create a BTS process to reliably hold the message data until the provider pipeline completes. However, an error occurred when attempting to create the BTS process. CICS will continue processing persistent WebSphere MQ messages to start provider pipelines, using channel based containers, but there is a risk that data from the persistent message may be lost in the event of a system failure.

System action:

CICS continues to process inbound WebSphere MQ persistent messages to drive provider pipelines, but in the event of a system failure, data originating in the persistent messages may be lost. This message is issued once on the first occurrence of a failure to create a BTS process. It is not issued for every occurrence of such a failure.

User response:

The Local Request Queue (LRQ) and Repository File must be defined to MVS using IDCAMS. The LRQ and Repository File must be defined to CICS using RDO. Note that a suitable value for STRINGS must be specified for both these file definitions. The default value of 1 is unlikely to be sufficient. 10 is recommended. A PROCESSTYPE with name DFHMQSOA must be defined to CICS using RDO, and the Repository File name must be specified as the FILE parameter.

Destination:

Console

Modules:

DFHPILSQ

XMEOUT Parameters:applid

End of change
Start of changeDFHPI0300End of change
Start of changedate time applid CICS could not invoke WEBSERVICE WebService because it was unable to find container container_name.End of change
Start of change
Explanation:

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.

End of change
Start of change
System action:

An exception response will be returned to the exec interface module which requested the INVOKE WEBSERVICE.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIIWEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeWebService, End of changeStart of changecontainer_nameEnd of change

Start of changeDFHPI0301End of change
Start of changedate time applid CICS was unable to link to program program_name while attempting to invoke webservice WebService. {The program abended. | The program was not defined. | The program was not enabled. | The program was not loadable. | No further details are available.}End of change
Start of change
Explanation:

CICS was attempting to perform an INVOKE WEBSERVICE command for webservice WebService but was unable to link to the given program program_name, or the linked program program_name abended.

End of change
Start of change
System action:

The link is abandoned and the INVOKE WEBSERVICE command returns appropriate EIBRESP and EIBRESP2 codes to the application program. Error processing will continue.

End of change
Start of change
User response:

Ensure that the program definition for program_name is correct. Correct the problem identified in the message. If the message reports no further information is available then trace can be referred to.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIIWEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeprogram_name, End of changeStart of changeWebService,End of changeStart of change{1=The program abended., End of changeStart of change2=The program was not defined., End of changeStart of change3=The program was not enabled., End of changeStart of change4=The program was not loadable., End of change Start of change5=No further details are available.}End of change

Start of changeDFHPI0400End of change
Start of changedate time applid tranid The CICS pipeline HTTP transport mechanism failed to send a request because {the request was using an invalid host codepage | there was a socket error | the URL was invalid | the connection was closed | a socket request timed out}.End of change
Start of change
Explanation:

The CICS pipeline HTTP transport mechanism was unable to successfully handle the outbound request due to one of two reasons as indicated in the message.

End of change
Start of change
System action:

The request is not sent. Error processing will continue.

End of change
Start of change
User response:

Depending on the error indicated in the message, ensure the host codepage you are using is correct or check for any socket errors indicated by examining any exception trace entries issued from sockets (SO) domain, or check that the URI specified as input does not contain any invalid characters or null delimiters.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPITHEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranid, End of changeStart of change{1=the request was using an invalid host codepage, End of changeStart of change2=there was a socket error, End of changeStart of change3=the URL was invalid, End of changeStart of change4=the connection was closed, End of changeStart of change5=a socket request timed out}End of change

Start of changeDFHPI0401End of change
Start of changedate time applid tranid The CICS pipeline HTTP transport mechanism failed to send a response or receive a request because {the codepage was not found | there was a socket error | the connection was closed | the client codepage was invalid} .End of change
Start of change
Explanation:

The CICS pipeline HTTP transport mechanism was unable to successfully handle the inbound request due to one of four reasons as indicated in the message. For instance, the transport may be unable to send a response due to the connection being closed or a sockets error. Also, the error could be caused by the request specifying a codepage which was either invalid or not found.

End of change
Start of change
System action:

The response is not sent. Error processing will continue.

End of change
Start of change
User response:

Depending on the error indicated in the message, ensure that the codepage you are using is correct, the connection being used is open, or check for any socket errors indicated by examining any exception trace entries issued from sockets (SO) domain.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPITHEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranid, End of changeStart of change{1=the codepage was not found, End of changeStart of change2=there was a socket error, End of change Start of change3=the connection was closed, End of changeStart of change4=the client codepage was invalid}End of change

Start of changeDFHPI0402End of change
Start of changedate time applid tranid The CICS pipeline HTTP transport mechanism failed to send a request because the URI specified an unknown host: hostname.End of change
Start of change
Explanation:

The CICS pipeline HTTP transport mechanism was unable to successfully handle the outbound request because the host hostname from the URI is unknown.

End of change
Start of change
System action:

The request is not sent. Error processing will continue.

End of change
Start of change
User response:

Ensure that the URI specifies a host which is known and available.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPITHEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranid, End of changeStart of changehostnameEnd of change

Start of change
DFHPI0403
date time applid tranid The CICS pipeline HTTP transport mechanism failed to receive a response because {the socket receive was timed out}.
Explanation:

The CICS pipeline HTTP transport mechanism did not successfully receive a response to the outbound request because the socket receive was timed out.

System action:

The request is abandoned. Error processing will continue.

User response:

Investigate why the remote server failed to respond in a timely manner. Consider changing the DTIMOUT value for the transaction that encountered this error.

Destination:

CPIO

Modules:

DFHPITH

XMEOUT Parameters: date, time,applid, tranid, {1=the socket receive was timed out}

End of change
Start of changeDFHPI0500End of change
Start of changedate time applid tranid The CICS Pipeline Manager DFHPIPM encountered an error while trying to link to program program_name. {The program abended. | The program was not defined. | The program was not enabled. | The program was not loadable. | No further details are available.} PIPELINE: pipeline.End of change
Start of change
Explanation:

The CICS Pipeline Manager, DFHPIPM, was unable to link to the given program, or the linked program abended.

End of change
Start of change
System action:

The link is abandoned. Error processing will continue.

End of change
Start of change
User response:

Ensure that the program definition is correct. Correct the problem identified in the message. If the message reports no further information is available then trace can be referred to.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIPMEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranid, End of changeStart of changeprogram_name,End of changeStart of change{1=The program abended., End of changeStart of change2=The program was not defined., End of changeStart of change3=The program was not enabled., End of changeStart of change4=The program was not loadable., End of change Start of change5=No further details are available.}, End of changeStart of changepipelineEnd of change

Start of changeDFHPI0501End of change
Start of changedate time applid tranid The CICS Pipeline Manager cannot proceed as the pipeline is unusable. {The pipeline was not found. | The pipeline is disabled. | The pipeline was of the wrong type.} PIPELINE: pipeline.End of change
Start of change
Explanation:

The CICS Pipeline Manager DFHPIPM was unable to begin processing as the pipeline it has been invoked for is unusable. If the message indicates that the pipeline is of the wrong type then this means that a Requester pipeline was used where a Provider pipeline was expected or a Provider pipeline was used in place of a Requester one.

End of change
Start of change
System action:

In the requester case the transaction is abended with abend code APIB. In the provider case the transaction is abended with abend code API1.

End of change
Start of change
User response:

Correct the problem identified in the message.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIPMEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranid, End of changeStart of change{1=The pipeline was not found., End of changeStart of change2=The pipeline is disabled., End of changeStart of change3=The pipeline was of the wrong type.}, End of changeStart of changepipelineEnd of change

Start of changeDFHPI0502End of change
Start of changedate time applid tranid The CICS Pipeline Manager has failed to receive a request from the underlying transport. TRANSPORT: transport, PIPELINE: pipeline.End of change
Start of change
Explanation:

The CICS Pipeline Manager DFHPIPM was unable to receive a request from the underlying transport. This is due to a error in that transport.

End of change
Start of change
System action:

The transaction is abended with abend code API2.

End of change
Start of change
User response:

Check the previous messages issued by the transport to identify the cause of the problem.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIPMEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranid, End of changeStart of changetransport, End of changeStart of changepipelineEnd of change

Start of changeDFHPI0503End of change
Start of changedate time applid tranid The CICS Pipeline Manager has failed to send a response on the underlying transport. TRANSPORT: transport, PIPELINE: pipeline.End of change
Start of change
Explanation:

The CICS Pipeline Manager DFHPIPM was unable to send a response on the underlying transport. This is due to a previous error in that transport.

End of change
Start of change
System action:

The request is abandoned. Error processing continues.

End of change
Start of change
User response:

Check the previous messages issued by the transport to identify the cause of the problem.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIPMEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranid, End of changeStart of changetransport, End of changeStart of changepipelineEnd of change

Start of changeDFHPI0504End of change
Start of changedate time applid tranid The CICS Pipeline Manager has failed to communicate with a remote server due to an error in the underlying transport. TRANSPORT: transport, PIPELINE: pipeline.End of change
Start of change
Explanation:

The CICS Pipeline Manager DFHPIPM failed to communicate with a remote server due to an error in the underlying transport.

End of change
Start of change
System action:

The request is abandoned. Error processing continues.

End of change
Start of change
User response:

Check the previous messages issued by the transport to identify the cause of the problem.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIPMEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranid, End of changeStart of changetransport, End of changeStart of changepipelineEnd of change

Start of changeDFHPI0505End of change
Start of changedate time applid tranid The CICS Pipeline Manager has failed to communicate with a remote server as no URI was provided. PIPELINE: pipeline.End of change
Start of change
Explanation:

The CICS Pipeline Manager DFHPIPM failed to communicate with a remote server as no URI was provided. Before CICS can make and a request to a remote server it must be provided with a URI identifying that server. This URI must either be provided in the container 'DFHWS-URI' or in the Pipeline configuration file.

End of change
Start of change
System action:

An exception trace entry is written. Error processing continues.

End of change
Start of change
User response:

Correct either the application logic or the configuration file so that the URI is provided.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIPMEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranid, End of changeStart of changepipelineEnd of change

Start of changeDFHPI0506End of change
Start of changedate 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.End of change
Start of change
Explanation:

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 and a request to a remote server it must be provided with a URI identifying that server.

End of change
Start of change
System action:

An exception trace entry is written. Error processing continues.

End of change
Start of change
User response:

Correct either the application logic or the configuration file so that a URI with a supported scheme is provided.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIPMEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranid, End of changeStart of changeuri, End of changeStart of changepipelineEnd of change

Start of changeDFHPI0507End of change
Start of changedate time applid tranid The CICS Pipeline Manager has failed to receive a response from an application handling task.{The request timed out. | The application task abended. | The connection to the application task was closed.} PIPELINE: pipeline.End of change
Start of change
Explanation:

The CICS Pipeline Manager DFHPIPM was unable to receive a response from an application task. A separate task was used for the application handler as a context switch was required. The message indicates the reason the response was not received.

End of change
Start of change
System action:

The request will be treated as failed and error processing will continue.

End of change
Start of change
User response:

Check the message logs for the region in which the application task was running to determine the detailed cause of the problem.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIPMEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranid, End of changeStart of change{1=The request timed out., End of changeStart of change2=The application task abended.,End of change Start of change3=The connection to the application task was closed.},End of change Start of changepipelineEnd of change

Start of changeDFHPI0508 EEnd of change
Start of changedate time applid The pipeline manager is unable to create or join a request stream because it is unable to reach the target for transaction tranid with userid userid.End of change
Start of change
Explanation:

The CICS pipeline manager attempted to create or join a request stream for transaction tranid. The transaction specifies a REMOTESYSTEM which cannot be contacted. This might be because IRC is not open or the target system is unavailable.

End of change
Start of change
System action:

The SOAP Handler attempting to create this request stream will create a SOAP server fault to return to the client. Error processing continues.

End of change
Start of change
User response:

Determine the remote system name from the tranid definition. Ensure that IRC is open and the IRC connection named is in service.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIPMEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranid, End of changeStart of changeuseridEnd of change

Start of changeDFHPI0509 EEnd of change
Start of changedate time applid The pipeline manager is unable to create or join a request stream because transaction tranid is not installed.End of change
Start of change
Explanation:

The CICS pipeline manager attempted to create or join a request stream for transaction tranid which is not installed.

End of change
Start of change
System action:

The SOAP Handler that attempted to create the request stream will create a SOAP server fault to return to the client. Error processing continues.

End of change
Start of change
User response:

Add an RDO definition for tranid with a program name of DFHPIAP.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIPMEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranidEnd of change

Start of changeDFHPI0510 EEnd of change
Start of changedate time applid The pipeline manager is unable to create or join a request stream because it has encountered a severe error for transaction tranid with userid userid.End of change
Start of change
Explanation:

The CICS pipeline manager attempted to create or join a request stream for transaction tranid. CICS encountered a severe error.

End of change
Start of change
System action:

A system dump is taken. The SOAP Handler attempting to create this request stream will create a SOAP server fault to return to the client. Error processing continues.

End of change
Start of change
User response:

None

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIPMEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranid, End of changeStart of changeuseridEnd of change

Start of changeDFHPI0600End of change
Start of changedate time applid The CICS SOAP handler has been passed a container that is not DATATYPE(CHAR).End of change
Start of change
Explanation:

The CICS soap handler DFHPISN was unable to convert the container to UTF-8 as the container does not have a datatype of CHAR.

End of change
Start of change
System action:

The soap handler is unable to process the input and returns a SOAP fault to the client/sender.

End of change
Start of change
User response:

Ensure that the DFHREQUEST and DFHWS-BODY containers use the DATATYPE(CHAR) option on the EXEC CICS PUT CONTAINER call.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPISNEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplidEnd of change

Start of changeDFHPI0601End of change
Start of changedate time applid The CICS SOAP handler has been passed data that does not begin with a '<' character.End of change
Start of change
Explanation:

The CICS soap handler DFHPISN has detected that the data in container DFHWS-BODY passed to it does not begin with a '<' character.

End of change
Start of change
System action:

The soap handler attempts to continue processing using the contents of the DFHWS-BODY container.

End of change
Start of change
User response:

If the contents of the DFHWS-BODY container is not expected to begin with a '<' character no further action is required. If the contents of the DFHWS-BODY container is expected to begin with a '<' character then check the data being put into it is correct and that the fromccsid parameter is set correctly.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPISNEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplidEnd of change

Start of change
DFHPI0602
date time applid The CICS SOAP handler failed to parse a message. The parser error code is . The DFHPIEP return code is . The error was found at offset into the message.
Explanation:

The CICS SOAP handler DFHPISN has failed to parse a message.

System action:

The SOAP handler stops processing the SOAP message and creates a SOAP fault to return to the requester.

User response:

Look up the parser error code in the Enterprise PL/I Programming Guide to determine the type of parsing failure. If the parser error code is 0 the XML is valid but the SOAP is not. Use the offset into the SOAP message to determine the precise location of the failure.

XMEOUT Parameters: date, time,applid,

End of change
Start of changeDFHPI0700 SEnd of change
Start of changedate time applid userid PIPELINE pipeline PL/I support is required in order to use pipelines.End of change
Start of change
Explanation:

The Pipeline pipeline installation has failed because PL/I support is not available in this region. PL/I language support is a pre-requisite for using pipelines.

End of change
Start of change
System action:

No pipeline is installed, but CICS continues normally.

End of change
Start of change
User response:

Add PL/I language support to your region and restart CICS. For instructions on how to do this, see z/OS V1R4.0 Language Environment Customization.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIPLEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeuserid, End of changeStart of changepipelineEnd of change

Start of changeDFHPI0701 IEnd of change
Start of changedate time applid userid PIPELINE pipeline has been created.End of change
Start of change
Explanation:

The Pipeline pipeline has been created. It now needs to undergo resolution processing. The CPIR transaction is attached automatically to do this. Once resolution is complete, the pipeline will become available for use.

End of change
Start of change
System action:

CICS continues normally.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIPLEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeuserid, End of changeStart of changepipelineEnd of change

Start of changeDFHPI0702 EEnd of change
Start of changedate time applid userid PIPELINE pipeline encountered an error in the configuration file filename for pipeline at offset X'offset'. The element name is elementname.End of change
Start of change
Explanation:

During the pipeline resolution process, the configuration file is parsed and control blocks are built. During this process, an error was encountered. The error is at the offset indicated and starts with the element name shown.

End of change
Start of change
System action:

The pipeline is set to a DISABLED state and normal processing continues.

End of change
Start of change
User response:

Correct the configuration file. Ensure that the corrected file has been validated before discarding the pipeline (pipeline) and then re-installing it.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIPLEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeuserid, End of changeStart of changepipeline, End of changeStart of changefilename, End of changeStart of changeX'End of changeStart of changeoffset', End of changeStart of changeelementnameEnd of change

Start of changeDFHPI0703 IEnd of change
Start of changedate time applid userid PIPELINE pipeline is about to scan the WSDIR directory.End of change
Start of change
Explanation:

A scan is about to begin for pipeline pipeline. This will cause a WebService to be created for each of any wsbind files found in the directory specified in the WSDIR parameter of the pipeline.

End of change
Start of change
System action:

The system continues normally.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIPLEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeuserid, End of changeStart of changepipelineEnd of change

Start of changeDFHPI0704 IEnd of change
Start of changedate time applid userid PIPELINE pipeline Implicit scan has completed. Number of wsbind files found in the WSDIR directory: num_files. Number of successful webservice creates: num_ok. Number of failed webservice creates: num_failed.End of change
Start of change
Explanation:

The scan for pipeline pipeline has completed. The number of wsbind files found in the directory specified for this pipeline by the WSDIR parameter is reported by num_files. The number that successfully created WebService resources is reported by num_ok and the number that failed WebService creation is reported by num_failed.

The number that successfully created URIMAP resources is reported by num_uri_ok and the number that failed URIMAP creation is reported by num_uri_failed.

End of change
Start of change
System action:

CICS continues normally.

End of change
Start of change
User response:

If num_failed or num_uri_failed is non-zero, look for previous messages that may describe the errors. PI domain trace entries will also have been written to aid in diagnosing the problem(s).

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIPLEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeuserid, End of changeStart of changepipeline, End of changeStart of changenum_files, End of changeStart of changenum_ok, End of changeStart of changenum_failedEnd of change

Start of changeDFHPI0705 EEnd of change
Start of changedate time applid userid PIPELINE pipeline encountered an error writing the configuration to the der ived shelf derived-shelf. The response code from the HFS write was X'uss-response' and the reason code was 'X'uss-reason'.End of change
Start of change
Explanation:

While doing an HFS write for pipeline pipeline, a bad response code was received. The HFS filename is hfs_file. The response code was hfs_rs and the reason code was hfs_rc.

End of change
Start of change
System action:

The pipeline is disabled and CICS continues normally.

End of change
Start of change
User response:

See the z/OS UNIX System Services Messages and Codes manual for the specified response and reason codes.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIPLEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeuserid, End of changeStart of changepipeline, End of changeStart of changederived-shelf, End of changeStart of changeX'End of changeStart of changeuss-response', End of changeStart of changeX'End of changeStart of changeuss-reason'End of change

Start of changeDFHPI0706 EEnd of change
Start of changedate time applid userid PIPELINE pipeline resolution failed because it cannot be determined if this is a requester or provider pipeline.End of change
Start of change
Explanation:

After the pipeline has been created, it undergoes the resolution process in a separate transaction. CICS has been unable to determine if the pipeline is a requester or a provider. The first element name must be requester_pipeline or provider_pipeline.

End of change
Start of change
System action:

The pipeline is set to a DISABLED state and CICS continues normally.

End of change
Start of change
User response:

Correct the configuration file. Pipeline pipeline_name must be discarded and then re-installed.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIPLEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeuserid, End of changeStart of changepipelineEnd of change

Start of changeDFHPI0707 EEnd of change
Start of changedate time applid userid PIPELINE pipeline resolution failed because namespace prefixes are not supp orted in the XML configuration file.End of change
Start of change
Explanation:

An XML element was discovered that had a namespace prefix specified. This is not supported.

End of change
Start of change
System action:

The pipeline is set to a DISABLED state and CICS continues normally.

End of change
Start of change
User response:

Correct the configuration file. Pipeline pipeline_name must be discarded and then re-installed.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIPLEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeuserid, End of changeStart of changepipelineEnd of change

Start of changeDFHPI0708 EEnd of change
Start of changedate time applid userid PIPELINE pipeline resolution failed because the XML configuration file cann ot be found.End of change
Start of change
Explanation:

After the pipeline has been created, it undergoes the resolution process in a separate transaction. This transaction has been unable to find the file specified in the cfgfile parameter of the resource definition, or in the EXEC CICS CREATE PIPELINE command.

End of change
Start of change
System action:

The pipeline is set to a DISABLED state.

End of change
Start of change
User response:

Ensure that the HFS filename is being specified correctly. A fully-qualified name must be used. Usual HFS restrictions, such as case-sensitivity and access rights, apply to the filename.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIPLEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeuserid, End of changeStart of changepipelineEnd of change

Start of changeDFHPI0709 EEnd of change
Start of changedate time applid userid PIPELINE pipeline resolution failed because the XML configuration file cann ot be copied to the derived shelf.End of change
Start of change
Explanation:

After the pipeline has been created, it undergoes the resolution process in a separate transaction. Part of this transaction is to copy the XML configuration file to the derived shelf. The derived shelf is the shelf name with /<applid>/PIPELINE/<pipeline>/ appended to it.

End of change
Start of change
System action:

The pipeline is set to a DISABLED state.

End of change
Start of change
User response:

Determine the reason for this failure and correct it, before discarding and then re-installing the pipeline.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIPLEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeuserid, End of changeStart of changepipelineEnd of change

Start of changeDFHPI0710 IEnd of change
Start of changedate time applid userid PIPELINE pipeline was successfully discarded.End of change
Start of change
Explanation:

The PIPELINE was successfully discarded and is no longer available for use.

End of change
Start of change
System action:

Processing continues.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIPLEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeuserid, End of changeStart of changepipelineEnd of change

Start of changeDFHPI0711 EEnd of change
Start of changedate time applid userid PIPELINE pipeline resolution failed because the SAX parser returned error c ode X'errcode'. The error was at offset X'offset' in the CONFIGFILE. The first eight bytes of data at this offset are: 'hexdata'.End of change
Start of change
Explanation:

After the pipeline has been created, it undergoes the resolution process in a separate transaction. This transaction invokes a SAX parser. The parser has detected an error (errcode) at offset offset into the CONFIGFILE, as specified in RDO or in the EXEC CICS CREATE PIPELINE command. The first eight bytes of data (hexdata) are printed in hexadecimal to aid problem resolution.

End of change
Start of change
System action:

The pipeline is set to a DISABLED state and CICS continues normally.

End of change
Start of change
User response:

Refer to Enterprise PL/I for z/OS Programming Guide for the terminating exception code errcode. Correct the configuration file. Pipeline pipeline_name must be discarded and then re-installed.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIPLEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeuserid, End of changeStart of changepipeline, End of changeStart of changeX'errcode', End of changeStart of changeX'End of changeStart of changeoffset', End of changeStart of changehexdataEnd of change

Start of changeDFHPI0712 EEnd of change
Start of changedate time applid userid PIPELINE pipeline failed to install due to insufficient access rights to a HFS file.End of change
Start of change
Explanation:

A NOTAUTH condition was raised when an attempt to read the configuration file (CONFIGFILE) for this pipeline was made.

End of change
Start of change
System action:

The pipeline is disabled and CICS continues normally.

End of change
Start of change
User response:

Correct the access for the userid or ensure the correct userid is used for the installation of this pipeline.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIPLEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeuserid, End of changeStart of changepipelineEnd of change

Start of changeDFHPI0713 EEnd of change
Start of changedate time applid userid PIPELINE pipelinename The pipeline resolution transaction CPIR did not attach.End of change
Start of change
Explanation:

After the pipeline has been created, it undergoes the resolution process in a separate transaction. However, this transaction was not successfully attached. The pipeline is not installed.

End of change
Start of change
System action:

Processing continues.

End of change
Start of change
User response:

Examine the exception trace entry that shows the cause of the attachment error. Ensure that the CPIR transaction is defined and installed on your CICS system and that the program DFHPIITL is also defined and available.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIPLEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeuserid, End of changeStart of changepipelinenameEnd of change

Start of changeDFHPI0714 EEnd of change
Start of changedate time applid userid PIPELINE pipeline failed to install. The directory specified in the WSDIR p arameter is invalid.End of change
Start of change
Explanation:

The HFS directory specified in the WSDIR parameter is invalid.

End of change
Start of change
System action:

The pipeline is NOT installed. CICS continues normally.

End of change
Start of change
User response:

Inspect the data specified and ensure that it is correct. Remember that case is important in specifying any HFS filename. Once correct, re-install the pipeline.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIPLEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeuserid, End of changeStart of changepipelineEnd of change

Start of changeDFHPI0715 IEnd of change
Start of changedate time applid userid PIPELINE pipeline Explicit scan has completed. Number of wsbind files found in the WSDIR directory: num_files. Webservices successful create/update: num_ok. Webservices not requiring update: num_nun. Webservices failed create/update: num_failed.End of change
Start of change
Explanation:

The explicit scan for pipeline pipeline has completed. The number of wsbind files found in the directory specified for this pipeline by the WSDIR parameter is reported by num_files. The number that successfully created or updated WebService resources is reported by num_ok, the number that did not require any update is reported by num_nun and the number that failed WebService creation is reported by num_failed.

The number that successfully created URIMAP resources is reported by num_uri_ok and the number that failed URIMAP creation is reported by num_uri_failed.

End of change
Start of change
System action:

CICS continues normally.

End of change
Start of change
User response:

If num_failed or num_uri_failed is non-zero, look for previous messages that may describe the errors. PI domain trace entries will also have been written to aid in diagnosing the problem(s).

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIPLEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeuserid, End of changeStart of changepipeline, End of changeStart of changenum_files, End of changeStart of changenum_ok, End of changeStart of changenum_nun, End of changeStart of changenum_failedEnd of change

Start of changeDFHPI0716 EEnd of change
Start of changedate time applid userid Unable to dynamically create a webservice for PIPELINE pipeline. The complete WSBIND file name is too long.End of change
Start of change
Explanation:

An attempt was made to dynamically create a webservice using the name of a wsbind file found in the WSDIR directory. The fully-qualified filename is longer than the maximum 255 characters.

End of change
Start of change
System action:

The webservice is NOT created. CICS continues normally.

End of change
Start of change
User response:

Use a shorter value for the WSDIR directory. The pipeline will need to be discarded and re-installed once the WSDIR parameter has been altered and any wsbind files either copied or re-generated to this new directory.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIPLEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeuserid, End of changeStart of changepipelineEnd of change

Start of changeDFHPI0720 EEnd of change
Start of changedate time applid userid PIPELINE pipeline encountered an error in the configuration file filename at offset X'offset'. Found : element_found yet expected : element_expected.End of change
Start of change
Explanation:

During the pipeline resolution process, the configuration file is parsed and control blocks are built. During this process, an error was encountered. The error was at offset offset. element_found was found when element_expected was expected.

End of change
Start of change
System action:

The pipeline is set to a DISABLED state and normal processing continues.

End of change
Start of change
User response:

Correct the configuration file. Ensure that the corrected file has been validated before discarding the pipeline (pipeline) and then re-installing it.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIPLEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeuserid, End of changeStart of changepipeline, End of changeStart of changefilename, End of changeStart of changeX'End of changeStart of changeoffset', End of changeStart of changeelement_found, End of changeStart of changeelement_expectedEnd of change

Start of change
DFHPI0730
date time applid An attempt to register a remote webservice as a participant in unit of work - X'uowid' has failed.
Explanation:

An error has been encountered while attempting to register a remote webservice as a participant in an atomic transaction, under the coordination of a local unit of work.

System action:

The local unit of work, is not updated with a link for the remote webservice and a registration response is not sent to the remote webservice's registration end point. The remote webservice then times out and backs out any recoverable updates it has made.

User response:

The problem may be the result of the coordinating unit of work timing out before the registration message is delivered to the region where it ran. If this is the case then consider extending the coordinating transaction's DTIMOUT value if set, or the coordinating region's FTIMOUT setting if DTIMOUT is set to NO. If the problem persists then you need further assistance from IBM to resolve this problem.

Destination:

Console and Transient Data Queue CPIO

Modules:

DFHPIRS

XMEOUT Parameters: date, time,applid, X'uowid'

End of change
Start of change
DFHPI0731
date time applid An attempt to register unit of work - X'uowid' with a remote WSAT coordinating transaction has failed.
Explanation:

An error has been encountered while attempting to register a local webservice as a participant in an atomic transaction, under the coordination of a remote unit of recovery.

System action:

The local unit of work is not updated with a link for the remote coordinating transaction, and the local webservice is not invoked. Instead a SOAP fault is returned to the coordinating transaction.

User response:

The problem may be the result of a configuration error for one of the pipeline resources that the local region uses. The DFHWSATR pipeline is used to send the registration request and the DFHWSATP pipeline is used to receive a registration response. If either of these are not installed, disabled or incorrectly configured then the message processing that they are intended for may not take place. Alternatively, the error may be caused by the participant transaction timing out before a registration response is received. This interval is controlled by the value of the wscoorcontext that resulted in the registration attempt. Consider extending this time to allow registration to complete successfully. If the problem persists then you need further assistance from IBM to resolve this problem.

Destination:

Console and Transient Data Queue CPIO

Modules:

XMEOUT Parameters: date, time,applid, X'Start of changeuowidEnd of change'

End of change
Start of change
DFHPI0732
date time applid A request to rollback unit of work - X'uowid' has been received from a remote WS-AT coordinating transaction.
Explanation:

During processing of an atomic transaction the remote WS-AT coordinating task has requested that CICS rolls back the specified unit of work.

System action:

The specified unit of work will be rolled back.

User response:

None.

Destination:

CPIO

Modules:

DFHPIRS

XMEOUT Parameters: date, time,applid, X'Start of changeuowidEnd of change'

End of change
Start of change
DFHPI0733
date time applid A transaction timed out while waiting for a Prepare message from a remote WS-AT coordinator. The unit of work - X'uowid' will be rolled back.
Explanation:

A CICS transaction waiting for a Prepare message from a remote WS-AT coordinator has timed out.

System action:

The specified unit of work will be rolled back.

User response:

None.

Destination:

CPIO

Modules:

DFHPIPM

XMEOUT Parameters: date, time,applid, X'Start of changeuowidEnd of change'

End of change
Start of changeDFHPI0800 EEnd of change
Start of changedate time applid userid Atomic Transaction processing failed because the SAX parser returned error code X'errcode'. The error was at offset X'offset' in the SOAP message.End of change
Start of change
Explanation:

During processing for an Atomic Transaction, the SOAP message is parsed by a SAX parser. The parser has detected an error (errcode) at offset offset into the message. The first eight bytes of data (hexdata) are printed to aid problem resolution.

End of change
Start of change
System action:

The transaction abends.

End of change
Start of change
User response:

Obtain trace entries (level 2 for the PI domain is required) and pass these onto your IBM service representative. You will need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to proceed.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIATEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeuserid, End of changeStart of changeX'End of changeStart of changeerrcode', End of changeStart of changeX'offsetEnd of changeStart of change'End of change

Start of change
DFHPI0733
date time applid A transaction timed out while waiting for a Prepare message from a remote WS-AT coordinator. The unit of work - X'uowid' will be rolled back.
Explanation:

A CICS transaction waiting for a Prepare message from a remote WS-AT coordinator has timed out.

System action:

The specified unit of work will be rolled back.

User response:

None.

Destination:

CPIO

Modules:

DFHPIPM

XMEOUT Parameters: date, time,applid, X'Start of changeuowidEnd of change'

End of change
Start of changeDFHPI0800 EEnd of change
Start of changedate time applid userid Atomic Transaction processing failed because the SAX parser returned error code X'errcode'. The error was at offset X'offset' in the SOAP message.End of change
Start of change
Explanation:

During processing for an Atomic Transaction, the SOAP message is parsed by a SAX parser. The parser has detected an error (errcode) at offset offset into the message. The first eight bytes of data (hexdata) are printed to aid problem resolution.

End of change
Start of change
System action:

The transaction abends.

End of change
Start of change
User response:

Obtain trace entries (level 2 for the PI domain is required) and pass these onto your IBM service representative. You will need further assistance from IBM to resolve this problem. See Part 4 of the CICS Problem Determination Guide for guidance on how to proceed.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIATEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeuserid, End of changeStart of changeX'End of changeStart of changeerrcode', End of changeStart of changeX'offsetEnd of changeStart of change'End of change

Start of change
DFHPI0801I E
date time applid A one way message has been found in an atomic transaction message exchange for transaction TRAN.
Explanation:

The Web service atomic transactions header handler in the pipeline has detected that a one way message flow has been sent as part of the atomic transaction message PSFSDATA A1 Worldwide VM/ESA Conversational Monitor System flows. This is not permitted.

System action:

The Web service atomic transactions handler has issued a trace and abended with an APIR abend. A SOAP fault message has also been sent to the client to indicate that CICS has detected an error.

User response:

The error is in the client that sent an invalid atomic transactions message to CICS. If you have control over the client system, investigate why it is attempting to use one way messages as part of the atomic transaction.

Destination:

CPIO

Modules:

DFHWSATH

XMEOUT Parameters: date, time,applid, TRAN

End of change
Start of changeDFHPI0901 IEnd of change
Start of changedate time applid userid New WEBSERVICE WebService is being created during a scan against PIPELINE Pipeline.End of change
Start of change
Explanation:

A new WSBIND file has been discovered on HFS during a scan. A corresponding CICS WEBSERVICE resource is being automatically created to represent it.

End of change
Start of change
System action:

None.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPISCEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeuserid, End of changeStart of changeWebService, End of changeStart of changePipelineEnd of change

Start of changeDFHPI0902 IEnd of change
Start of changedate time applid userid WEBSERVICE WebService is being updated during a scan against PIPELINE Pipeline.End of change
Start of change
Explanation:

An update has been detected for a WEBSERVICE resource. CICS compares the last modification time of the WSBIND file on HFS with the last modification time stored in the WEBSERVICE resource definition. If the WSBIND file on HFS is newer than the currently installed resource, the WEBSERVICE resource is updated. This process involves discarding the existing definition and installing a new one.

End of change
Start of change
System action:

If there is 'inflight' activity outstanding for this WEBSERVICE then the update will complete after that workload has ended.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPISCEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeuserid, End of changeStart of changeWebService, End of changeStart of changePipelineEnd of change

Start of changeDFHPI0903 IEnd of change
Start of changedate time applid userid New URIMAP UriMap is being created during a scan against PIPELINE Pipeline for WEBSERVICE WebService.End of change
Start of change
Explanation:

A new URIMAP resource is being installed during a scan of a PIPELINE.

End of change
Start of change
System action:

None.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPISCEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeuserid, End of changeStart of changeUriMap, End of changeStart of changePipeline, End of changeStart of changeWebServiceEnd of change

Start of changeDFHPI0904 IEnd of change
Start of changedate time applid userid URIMAP UriMap could not be created for WEBSERVICE WebService in PIPELINE Pipeline. The URI that could not be allocated is: ' Uri'.End of change
Start of change
Explanation:

An attempt to automatically create a URIMAP for a scanned WEBSERVICE failed. This is probably because the URI specified in the wsbind file is already in use by another URIMAP.

End of change
Start of change
System action:

None.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPISCEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeuserid, End of changeStart of changeUriMap, End of changeStart of changeWebService, End of changeStart of changePipeline, End of changeStart of changeUriEnd of change

Start of changeDFHPI0910 IEnd of change
Start of changedate time applid userid WEBSERVICE WebService within PIPELINE Pipeline has been created.End of change
Start of change
Explanation:

A WEBSERVICE has been created and is now in the INITING state. It is not available for use until it has reached INSERVICE state.

End of change
Start of change
System action:

Processing continues. The WEBSERVICE will complete installation shortly.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIWREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeuserid, End of changeStart of changeWebService, End of changeStart of changePipelineEnd of change

Start of changeDFHPI0911 EEnd of change
Start of changedate time applid userid WEBSERVICE WebService within PIPELINE Pipeline was not created because: {there is insuffient storage | there is a directory domain error | the specified PIPELINE is not installed | a lock cannot be obtained | there is a duplicate resource error}.End of change
Start of change
Explanation:

WEBSERVICE WebService was not created. This error may be caused if the specified PIPELINE is not installed.

End of change
Start of change
System action:

The WEBSERVICE is not created.

End of change
Start of change
User response:

Ensure that the specified PIPELINE resource is installed and try again.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIWREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeuserid, End of changeStart of changeWebService, End of changeStart of changePipeline, End of changeStart of change{1=there is insuffient storage, End of changeStart of change2=there is a directory domain error, End of change Start of change3=the specified PIPELINE is not installed, End of changeStart of change4=a lock cannot be obtained, End of changeStart of change5=there is a duplicate resource error}End of change

Start of changeDFHPI0912 IEnd of change
Start of changedate time applid userid WEBSERVICE WebService was successfully discarded.End of change
Start of change
Explanation:

The WEBSERVICE was successfully discarded and is no longer available for use.

End of change
Start of change
System action:

Processing continues.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIWREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeuserid, End of changeStart of changeWebServiceEnd of change

Start of changeDFHPI0913 IEnd of change
Start of changedate time applid userid WEBSERVICE WebService is being discarded.End of change
Start of change
Explanation:

A discard of a WEBSERVICE has been started but cannot complete at this time as 'inflight' work is outstanding.

End of change
Start of change
System action:

The WEBSERVICE discard will complete when the 'inflight' activity has ended.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIWREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeuserid, End of changeStart of changeWebServiceEnd of change

Start of changeDFHPI0914 EEnd of change
Start of changedate time applid userid WEBSERVICE WebService is UNUSABLE because: {the WSBind file was not found | CICS is not authorized to read the WSBind file | there is insufficient storage to load the WSBind file | the HFS read for the WSBind file failed | writing the WSBind file to the shelf failed | the PIPELINE is incompatible with this WEBSERVICE | the CPIR resolution transaction could not be attached | the direction of the PIPELINE can't be determined | the WSBind file is corrupt | the WSBind file has an invalid version number | the WSBind file has an out of date version number | the WSBind file product number was not recognised}.End of change
Start of change
Explanation:

The WEBSERVICE failed to complete initialization.

End of change
Start of change
System action:

The WEBSERVICE has been put into the UNUSABLE state.

End of change
Start of change
User response:

Check that the CICS region id has permission to write to the HFS shelf directory structure. Check that the WSBind file exists and that CICS has read permission for it. Check that the WSDL file, if specified, exists and that CICS has read permission for it. Check how the WSBind file has been produced. It was not produced using either the CICS Web Services Assistant or a recognised vendor product. If there is a version error reported then regenerate the WSBind file using the correct version of the tools. Check that if the WEBSERVICE represents an application in CICS that is going to implement a WebService then the PIPELINE is also configured in provider mode. Conversely, if the WEBSERVICE represents a WebService running on a remote server then the PIPELINE is configured in requester mode. Check that the PIPELINE has been installed without errors.

A provider mode WEBSERVICE is one for which a PROGRAM has been specified. A requester mode WEBSERVICE is one for which no PROGRAM has been specified. The PROGRAM name (if needed) must be specified at the time that the WSBind file is generated.

Discard and reinstall the WEBSERVICE.

If the problem persists you may need to use the trace facility to determine the cause of the problem.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIWREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeuserid, End of changeStart of changeWebService, End of changeStart of change{1=the WSBind file was not found, End of changeStart of change2=CICS is not authorized to read the WSBind file, End of change Start of change3=there is insufficient storage to load the WSBind file, End of changeStart of change4=the HFS read for the WSBind file failed, End of changeStart of change5=writing the WSBind file to the shelf failed, End of change Start of change6=the PIPELINE is incompatible with this WEBSERVICE, End of changeStart of change7=the CPIR resolution transaction could not be attached, End of changeStart of change8=the direction of the PIPELINE can't be determined, End of change Start of change9=the WSBind file is corrupt, End of changeStart of change10=the WSBind file has an invalid version number, End of changeStart of change11=the WSBind file has an out of date version number, End of change Start of change12=the WSBind file product number was not recognised}End of change

Start of changeDFHPI0915 IEnd of change
Start of changedate time applid userid WEBSERVICE WebService is now INSERVICE and is ready for use.End of change
Start of change
Explanation:

The WEBSERVICE has completed initialization and is ready for use.

End of change
Start of change
System action:

Processing continues.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIWREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeuserid, End of changeStart of changeWebServiceEnd of change

Start of changeDFHPI0916 EEnd of change
Start of changedate time applid userid WEBSERVICE WebService within PIPELINE Pipeline was not created because it clashes with another WEBSERVICE of the same name in PIPELINE Pipeline.End of change
Start of change
Explanation:

WEBSERVICE WebService was not created. This error was caused by a name clash with an existing WEBSERVICE that is already installed. The clash can occur if the same wsbind file is installed in two different PIPELINEs or if a wsbind file matches another wsbind file with a sufficiently similar name from any PIPELINE.

End of change
Start of change
System action:

The WEBSERVICE is not CREATED, the PIPELINE SCAN processing continues.

End of change
Start of change
User response:

Rename the wsbind file and retry the operation.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPISCEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeuserid, End of changeStart of changeWebService, End of changeStart of changePipeline, End of changeStart of changePipelineEnd of change

Start of change
DFHPI0995
date time applid tranidThe CICS pipeline manager has encountered a problem with PFSDATA A1 Worldwide VM/ESA Conversational Monitor System file DFHPIDIR {the file was not found|the file key length was too small|the file record size was too small|the file is full|the file control record is full|file recovery mode was not backout|there was an internal error|file failed to open or connect}
Explanation:

The pipeline manager encountered a problem attempting to open file DFHPIDIR. This might be due to one of the following:

System action:

Processing is aborted. A SOAP fault is returned to the client.

User response:

Examine the trace to determine why the pipeline manager failed.

Destination:

CPIO

Modules:

XMEOUT Parameters:Start of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranid, End of changeStart of change{1=the file was not found, End of changeStart of change2=the file key length was too small, End of change Start of change3=the file record size was too small, End of changeStart of change4=the file is full, End of changeStart of change5=the file control record is full, End of changeStart of change6=file recovery mode was not backout, End of changeStart of change7=there was an internal error, End of changeStart of change8=file failed to open or connect}End of change

End of change
Start of change
DFHPI0997
date time applid tranid pipeline The CICS pipeline manager has encountered an error: {pipeline not found|pipeline not active|pipeline mode mismatch|unhandled node failure|context switch failed|request stream creation failure|request stream transport error|target program unavailable|channel error|channel not found|URI not found|invalid URI|authorization failure|program abend|unidentified problem|timeout occured|no request message|there was a problem with file PIDIR|attempt to register a WS-AT context twice}
Explanation:

The Pipeline Manager encountered a problem whilst attempting to process a message. This can be due to one of the following;

System action:

None.

User response:

Examine the trace to determine why the Pipeline Manager failed.

Destination:

CPIO

Modules:

DFHPIPM

XMEOUT Parameters:Start of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranid, End of changeStart of changepipeline, End of changeStart of change{1=PIPELINE not found, End of changeStart of change2=PIPELINE not active, End of change Start of change3=PIPELINE mode mismatch, End of changeStart of change4=unhandled node failure, End of changeStart of change5=context switch failed, End of changeStart of change6=request stream creation failure, End of changeStart of change7=request stream transport error, End of changeStart of change8=target program unavailable, End of changeStart of change9=channel error, End of changeStart of change10=channel not found, End of changeStart of change11=URI not found, End of changeStart of change12=invalid URI, End of changeStart of change13=authorization failure, End of changeStart of change14=program abend, End of changeStart of change15=unidentified problem, End of changeStart of change16=timeout occured, End of changeStart of change17=no request message, End of changeStart of change18=there was a problem with file PIDIR, End of changeStart of change19=attempt to register a WS-AT context twice}End of change

End of change
Start of changeDFHPI0998End of change
Start of changedate time applid The Outbound Router program, DFHPIRT, has received a non-NORMAL response while attempting to get the pipeline name from the DFHWS-PIPELINE container. The resulting error code is X'code'.End of change
Start of change
Explanation:

The Outbound Router program, DFHPIRT, was unable to successfully start the pipeline as it was unable to obtain the pipeline name from the DFHWS-PIPELINE container. A non-NORMAL response was returned from the EXEC CICS GET CONTAINER call. If the code was '099D'X then a CONTAINERERR was returned. The code '099E'X indicates that a LENGERR was returned.

End of change
Start of change
System action:

The program abends with an APIC abend.

End of change
Start of change
User response:

Examine the trace to determine why the Outbound Router failed. Ensure that the DFHWS-PIPELINE container has been created correctly before linking to the Outbound Router program, DFHPIRT, and that the pipeline name placed in this container is not larger than eight characters.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIRTEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeX'End of changeStart of changecodeEnd of changeStart of change'End of change

Start of changeDFHPI0999End of change
Start of changedate time applid The Outbound Router program, DFHPIRT, has received an error from the Pipeline Manager.End of change
Start of change
Explanation:

The Outbound Router program, DFHPIRT, was unable to successfully start the Pipeline Manager.

End of change
Start of change
System action:

The program abends with an APIB abend.

End of change
Start of change
User response:

Examine the trace to determine why the Pipeline Manager failed.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIRTEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplidEnd of change

End of change
Start of changeDFHPI1001End of change
Start of changedate time applid Validation of a {request | response} message for webservice webservicename and operation operationname failed. The failure response contains the following message: 'message'.End of change
Start of change
Explanation:

Validation was requested for a particular operation, operationname, for webservice webservicename. The validation has been attempted and failed. The incoming message does not match the schema specified for this message. The contents of the error container are output as part of this message.

End of change
Start of change
System action:

None.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPITL, DFHPIIWEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of change{1=request, End of changeStart of change2=response}, End of changeStart of changewebservicename, End of changeStart of changeoperationname,End of changeStart of changemessageEnd of change

Start of changeDFHPI1002End of change
Start of changedate time applid Validation of a {request | response} message for webservice webservicename and operation operationname was successful.End of change
Start of change
Explanation:

Validation was requested for a particular operation, operationname, for webservice webservicename. The validation has been performed successfully.

End of change
Start of change
System action:

None.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPITL, DFHPIIWEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of change{1=request, End of changeStart of change2=response}, End of changeStart of changewebservicename, End of changeStart of changeoperationnameEnd of change

Start of changeDFHPI1003End of change
Start of changedate time applid No current channel located. Validation cannot occur.End of change
Start of change
Explanation:

Validation was requested for a particular operation. This requires that a channel exists with containers present. No current channel could be found. Validation cannot occur in this situation.

End of change
Start of change
System action:

Validation is not attempted. The application program is invoked as though validation had not been requested.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPITLEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplidEnd of change

Start of changeDFHPI1004End of change
Start of changedate time applid The attempt to link to DFHPIVAL to perform validation failed.End of change
Start of change
Explanation:

Validation was requested for a particular operation. This requires linking to program DFHPIVAL. The link to the program failed. Validation cannot occur without this program.

End of change
Start of change
System action:

Validation is not attempted. Processing continues. The application program is invoked as though validation had not been requested.

End of change
Start of change
User response:

Ensure that the CSD in use has the definition for DFHPIVAL included.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPITL, DFHPIIWEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplidEnd of change

Start of changeDFHPI1005End of change
Start of changedate time applid Attempt to link to program progname failed. SOAP conversions cannot be performed. Module: modnameEnd of change
Start of change
Explanation:

SOAP conversion to a format suitable for a CICS application failed. The link to a vendor supplied program progname failed. The webservice cannot be used without this program.

End of change
Start of change
System action:

The attempt to use the webservice is aborted. A soap fault is returned to the client. If the failure occurs during an INVOKE WEBSERVICE API command, i.e. the issuing module for this message is DFHPIIW, appropriate EIBRESP and EIBRESP2 codes are returned to the application program.

End of change
Start of change
User response:

Ensure that the WEBSERVICE definition refers to the correct WSBIND file and that the vendor program progname required is available to CICS.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPITL, DFHPIIWEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeprogname, End of changeStart of changemodnameEnd of change

Start of changeDFHPI1006End of change
Start of changedate time applid The WSBIND file used for WEBSERVICE WebService is not a type which CICS can use. Module: modnameEnd of change
Start of change
Explanation:

The product which produced the WSBIND file is not one which CICS knows how to handle. As such, it is not possible to invoke the webservice WebService.

End of change
Start of change
System action:

The attempt to use the webservice is aborted. A soap fault is returned to the client. If the failure occurs during an INVOKE WEBSERVICE API command, i.e. the issuing module for this message is DFHPIIW, appropriate EIBRESP and EIBRESP2 codes are returned to the application program.

End of change
Start of change
User response:

Ensure that the WEBSERVICE definition for WebService refers to the correct WSBIND file and that the file has been properly produced.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPITL, DFHPIIWEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeWebService, End of changeStart of changemodnameEnd of change

Start of change
Start of changeDFHPI1007End of change
Start of changedate time applid SOAP message processing failed because of incorrect input: ({XML_FORMAT_ERROR | UNEXPECTED_CONTENT | HEADER_FORMAT_ERROR | UNDEFINED_ELEMENT | UNDEFINED_NAME_SPACE | ARRAY_OVERFLOW | NAME_TOO_LONG | PREFIX_TOO_LONG | NAME_SPACE_TOO_LONG}error_qualifier).End of change
Start of change
Explanation:

CICS has failed to convert the body of a SOAP message received from a partner process. The reason for the failure is due to a problem with the content of the SOAP message. The message is either not well formed, invalid with respect to the XML schema or does not conform to one of the internal constraints of the CICS SOAP transformation service. An error_qualifier may be provided to help identify the source of the problem. In some cases the error_qualifier will be empty.

The possible error codes and qualifiers associated with this message are:

XML_FORMAT_ERROR
The SOAP message is not well formed. See the trace for further details.
UNEXPECTED_CONTENT
Character data has been found between two XML tags at a place where such text was not expected.
HEADER_FORMAT_ERROR
There is a problem reading the namespace attributes from the SOAP Envelope.
UNDEFINED_ELEMENT element_name
The SOAP message includes an unexpected XML tag.
UNDEFINED_NAME_SPACE name_space
The SOAP message includes an XML namespace prefix that has not been defined.
ARRAY_OVERFLOW array_name
Too many instances of an array or list of tags has been found in the SOAP message.
NAME_TOO_LONG
An XML tag name longer than 255 characters has been found.
PREFIX_TOO_LONG
An XML namespace prefix longer than 255 characters has been found.
NAME_SPACE_TOO_LONG
An XML namespace name longer than 255 characters has been found.
End of change
Start of change
System action:

The XML conversion process halts. If CICS is acting as the Web service provider then the task is terminated with an APIG abend. If CICS is the Web service requester then a response code of INVREQ is returned to the caller of the INVOKE WEBSERVICE API with a resp2 code of 14. An exception entry is written to the trace table.

End of change
Start of change
User response:

Examine the exception trace entry for further information. Consider using the WEBSERVICE validation option to test the SOAP message for validity with respect to the XML schema.

Correct or change the partner process to ensure that the SOAP message sent to CICS is appropriate to be consumed by CICS.

If the SOAP message is changed by a handler program as part of the CICS PIPELINE processing then ensure that the handler has not introduced this problem.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPICCEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of change1=XML_FOMAT_ERROR, End of change Start of change2=UNEXPECTED_CONTENT, End of changeStart of change3=HEADER_FORMAT_ERROR, End of changeStart of change4=UNDEFINED_ELEMENT, End of changeStart of change5=UNDEFINED_NAME_SPACE, End of changeStart of change6=ARRAY_OVERFLOW, End of changeStart of change7=NAME_TOO_LONG, End of changeStart of change8=PREFIX_TOO_LONG, End of change9=NAME_SPACE_TOO_LONG,Start of changeerror_qualifierEnd of change

End of change
Start of change
Start of changeDFHPI1008End of change
Start of changedate time applid SOAP message generation failed because of incorrect input: ( {ARRAY_CONTAINER_TOO_SMALL | INPUT_STRUCTURE_TOO_SMALL | INPUT_ARRAY_TOO_LARGE | INPUT_ARRAY_TOO_SMALL | CONTAINER_NOT_FOUND | CONTAINER_NOT_BIT | }error_qualifier).End of change
Start of change
Explanation:

CICS has failed to generate a SOAP message due to a problem with the data received from the CICS application. An error_qualifier may be provided to help identify the source of the problem. In some cases the error_qualifier will be empty.

The possible error codes and qualifiers associated with this message are:

ARRAY_CONTAINER_TOO_SMALL array_name
A CICS container does not hold sufficient data given the number of instances of the data expected and the length of one instance of the data.
INPUT_STRUCTURE_TOO_SMALL
The container passed to CICS does not hold sufficent data given the length of the language structure.
INPUT_ARRAY_TOO_LARGE array_name
Too many instances of a structure have been supplied in a container given the maximum value specified in the WSDL.
INPUT_ARRAY_TOO_SMALL array_name
Too few instances of a structure have been supplied in a container given the minimum value specified in the WSDL.
CONTAINER_NOT_FOUND container_name
A container named in the input structure cannot be found.
CONTAINER_NOT_BIT container_name
A container named in the input structure exists but is of the wrong type. The container must be created in BIT mode rather than CHAR mode.
End of change
Start of change
System action:

The XML conversion process halts. If CICS is acting as the Web service provider then the task is terminated with an APIG abend. If CICS is the Web service requester then a response code of INVREQ is returned to the caller of the INVOKE WEBSERVICE API with a resp2 code of 14. An exception entry is written to the trace table.

End of change
Start of change
User response:

Examine the exception trace entry for further information.

Correct the CICS application to ensure that the data presented to CICS is appropriate to be converted into a SOAP message.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIIIEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of change1=ARRAY_CONTAINER_TOO_SMALL, End of change Start of change2=INPUT_STRUCTURE_TOO_SMALL, End of changeStart of change3=INPUT_ARRAY_TOO_LARGE, End of changeStart of change4=INPUT_ARRAY_TOO_SMALL, End of changeStart of change5=CONTAINER_NOT_FOUND, End of changeStart of change6=CONTAINER_NOT_BIT, End of changeStart of changeerror_qualifierEnd of change

End of change
Start of change
Start of changeDFHPI1009End of change
Start of changedate time applid SOAP message processing failed. A conversion error { UNKNOWN_CONVERSION | INPUT_TOO_LONG | OUTPUT_OVERFLOW | NEGATIVE_UNSIGNED | NO_FRACTION_DIGITS | FRACTION_TOO_LONG | INVALID_CHARACTER | ODD_HEX_DIGITS | INVALID_BASE64 | NOT_PURE_DBCS | INVALID_FIELD_SIZE | EXPONENT_OVERFLOW |EXPONENT_UNDERFLOW } occurred when converting field fieldnameEnd of change
Start of change
Explanation:

CICS has failed to convert the body of a SOAP message received from a partner process. The reason for the failure is due to a problem converting a value from the SOAP message.

The possible error codes and qualifiers associated with this message are:

INPUT_TOO_LONG
The value of an XML tag that was declared as numeric contains more than 31 digits.
OUTPUT_OVERFLOW
An XML tag contains a value that is too long to fit in the associated field of the commarea, or an XML tag contains a numeric value which is outside the permitted range for the associated field in the COMMAREA.
NEGATIVE_UNSIGNED
A negative number has been found in an XML tag that was declared as unsigned.
NO_FRACTION_DIGITS
An XML tag contains a number which contains a decimal point but is not followed by any valid fractional digits.
FRACTION_TOO_LONG
An XML tag contains a number with more non-zero fractional digits than the WSDL allows.
INVALID_CHARACTER
An XML tag contains a character that is inconsistent with the declared type of that tag. For example, a tag declared as hexBinary contains a value that is not in the range 0-9, a-f, A-F.
ODD_HEX_DIGITS
An XML tag that was declared as hexBinary contains an odd number of hexadecimal characters.
INVALID_BASE64
An XML tag that was declared as base64Binary contains a value that is not consistent with the base64 encoding.
NOT_PURE_DBCS
An XML tag that maps to a pure DBCS language structure field contains a value that cannot be represented in pure DBCS.
INVALID_FIELD_SIZE
A floating point type with an unsupported precision level has been discovered.
EXPONENT_OVERFLOW
An overflow condition has been encountered whilst transforming a floating point value
EXPONENT_UNDERFLOW
An underflow condition has been encountered whilst transforming a floating point value.
UNKNOWN_CONVERSION
An unrecognized conversion type has been requested.
End of change
Start of change
System action:

The XML conversion process halts. If CICS is acting as the Web service provider then the task is terminated with an APIG abend. If CICS is the Web service requester then a response code of INVREQ is returned to the caller of the INVOKE WEBSERVICE API with a resp2 code of 14. An exception entry is written to the trace table.

End of change
Start of change
User response:

Examine the exception trace entry for further information.

Consider using the WEBSERVICE validation option to test the SOAP message for validity with respect to the XML schema.

Correct or change the partner process to ensure that the SOAP message sent to CICS is appropriate to be consumed by CICS.

If the SOAP message is changed by a handler program as part of the CICS PIPELINE processing then ensure that the handler has not introduced this problem.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPICCEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of change99=UNKNOWN_CONVERSION, End of changeStart of change1=INPUT_TOO_LONG, End of change Start of change2=OUTPUT_OVERFLOW, End of changeStart of change3=NEGATIVE_UNSIGNED, End of changeStart of change4=NO_FRACTION_DIGITS, End of changeStart of change5=FRACTION_TOO_LONG, End of changeStart of change6=INVALID_CHARACTER, End of changeStart of change7=ODD_HEX_DIGITS, End of changeStart of change11=INVALID_BASE64, End of changeStart of change12=NOT_PURE_DBCS, End of changeStart of change14=INVALID_FIELD_SIZE, End of changeStart of change15=EXPONENT_OVERFLOW, End of changeStart of change16=EXPONENT_UNDERFLOW, End of changeStart of changefieldnameEnd of change

End of change
Start of change
Start of changeDFHPI1010End of change
Start of changedate time applid SOAP message generation failed. A conversion error { UNKNOWN_CONVERSION | NEGATIVE_UNSIGNED | NO_FRACTION_DIGITS | INVALID_CHARACTER | INVALID_PACKED_DEC | INVALID_ZONED_DEC | INCOMPLETE_DBCS | ODD_DBCS_BYTES | INVALID_FIELD_SIZE |EXPONENT_OVERFLOW |EXPONENT_UNDERFLOW} occurred when converting field fieldnameEnd of change
Start of change
Explanation:

CICS has failed to generate the body of a SOAP message using application supplied data. The reason for the failure is due to a problem converting a value from the application data.

The possible error codes and qualifiers associated with this message are:

NEGATIVE_UNSIGNED
A negative number has been found in the application data that was declared as unsigned.
INVALID_CHARACTER
An XML tag contains a character that is inconsistent with the declared type of that tag. For example, a tag declared as hexBinary contains a value that is not in the range 0-9, a-f, A-F.
INVALID_PACKED_DEC
A packed decimal field in the application data contains an illegal value that can't be converted to XML.
INVALID_ZONED DEC
A zoned decimal field in the application data contains an illegal value that can't be converted to XML.
INCOMPLETE_DBCS
A DBCS sequence in the application data is missing a shift in (SI) character.
ODD_DBCS_BYTES
A DBCS sequence in the application data is an odd number of bytes in length.
INVALID_FIELD_SIZE
A floating point type with an unsupported precision level has been discovered.
EXPONENT_OVERFLOW
An overflow condition has been encountered whilst transforming a floating point value
EXPONENT_UNDERFLOW
An underflow condition has been encountered whilst transforming a floating point value.
UNKNOWN_CONVERSION
An unrecognized conversion type has been requested.
End of change
Start of change
System action:

The XML conversion process halts. If CICS is acting as the Web service provider then the task is terminated with an APIG abend. If CICS is the Web service requester then a response code of INVREQ is returned to the caller of the INVOKE WEBSERVICE API with a resp2 code of 14. An exception entry is written to the trace table.

End of change
Start of change
User response:

Examine the exception trace entry for further information.

Correct the CICS application to ensure that the data presented to CICS is appropriate to be converted into a SOAP message.

End of change
Start of change
Destination:

CPIO

End of change
Modules:

Start of changeDFHPIIIEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of change99=UNKNOWN_CONVERSION, End of changeStart of change3=NEGATIVE_UNSIGNED, End of changeStart of change6=INVALID_CHARACTER, End of changeStart of change8=INVALID_PACKED_DEC, End of changeStart of change9=INVALID_ZONED_DEC, End of changeStart of change10=INCOMPLETE_DBCS, End of change Start of change13=ODD_BYTES_DBCS, End of changeStart of change14=INVALID_FIELD_SIZE, End of changeStart of change15=EXPONENT_OVERFLOW, End of changeStart of change16=EXPONENT_UNDERFLOW, End of changeStart of changefieldnameEnd of change

End of change
Start of change
DFHPI9000
ResourceBundle not found issuing message: value
Explanation:

The messages for the Web services assistants cannot be located.

System action:

The Web services assistant continues processing but no other messages will be issued.

User response:

Contact your IBM support representative for further assistance.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9001
Message not found issuing message: value
Explanation:

A message number value is missing and cannot be issued.

System action:

The Web services assistant continues processing.

User response:

Contact your IBM support representative for further assistance.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9002
A WSDL operation name is too long to be supported by CICS: value
Explanation:

CICS imposes a limit on the maximum length of each operation name in a WSDL document. This limit is 255 characters. Operation name value is too long.

System action:

The Web services assistant continues processing.

User response:

Edit the WSDL document and reduce the length of the operation name. Resubmit the DFHWS2LS job to reprocess the WSDL.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9003
A WSDL part name is too long to be supported by CICS: value
Explanation:

CICS imposes a limit on the maximum length of each part name in a WSDL document. This limit is 255 characters. Part name value is too long.

System action:

The Web services assistant continues processing.

User response:

Edit the WSDL document and reduce the length of the part name. Resubmit the DFHWS2LS job to reprocess the WSDL.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9004
The WSDL specifies a style value of document and contains a part name that refers to an XML type. Document style WSDL must only refer to XML elements.
Explanation:

There is an error in the WSDL document. The WSDL binding element specifies the use of 'document' style encoding but the associated message element points to an XML type. If document style bindings are used then the message elements may only point to XML elements.

System action:

The Web services assistant continues processing.

User response:

Correct the WSDL document and then resubmit the DFHWS2LS job to reprocess the WSDL.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9010
Simple data type type:emv. is not atomic. List and union data types are not supported.
Explanation:

DFHWS2LS only supports simple primitive XML data types. Type type is either a list or a union data type.

System action:

The Web services assistant continues processing.

User response:

Either redesign your WSDL to remove the content that is not supported by DFHWS2LS or consider implementing this Web service without the use of the Web services assistants. If the Web services assistant cannot be used then the following options are available:

  1. If you are implementing a Web service provider application then you should consider writing your own XML capable SOAP 'apphandler'.
  2. If you are implementing a Web service requester application then you should consider writing an XML capable application that uses the DFHPIRT channel linkable SOAP interface.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9011
Unsupported super type super_type found for type base_type
Explanation:

XML data type base_type is derived from XML data type super_type The super type is not supported by DFHWS2LS.

System action:

The Web services assistant continues processing.

User response:

Either redesign your WSDL to remove the content that is not supported by DFHWS2LS or consider implementing this Web service without the use of the Web services assistants. If the Web services assistant cannot be used then the following options are available:

  1. If you are implementing a Web service provider application then you should consider writing your own XML capable SOAP 'apphandler'.
  2. If you are implementing a Web service requester application then you should consider writing an XML capable application that uses the DFHPIRT channel linkable SOAP interface.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9012
Schema wild cards (<any> tags) are not supported.
Explanation:

A XML schema referenced within WSDL document contains an 'any' tag. The 'any' tag is not supported by DFHWS2LS.

System action:

The Web services assistant continues processing.

User response:

Either redesign your WSDL to remove the content that is not supported by DFHWS2LS or consider implementing this Web service without the use of the Web services assistants. If the Web services assistant cannot be used then the following options are available:

  1. If you are implementing a Web service provider application then you should consider writing your own XML capable SOAP 'apphandler'.
  2. If you are implementing a Web service requester application then you should consider writing an XML capable application that uses the DFHPIRT channel linkable SOAP interface.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9013
Schema model groups with maxOccurs different from minOccurs are not supported. Problem found for type: value
Explanation:

An XML model group has been found within the XML schema referenced from the WSDL document which specifies an unknown number of occurrences. The term 'model group' refers to one of the following XML tags: 'all', 'sequence' or 'choice'. DFHWS2LS only supports these tags where they repeat a fixed number of times. This problem has been identified for type value

System action:

The Web services assistant continues processing.

User response:

Either redesign your WSDL to remove the content that is not supported by DFHWS2LS or consider implementing this Web service without the use of the Web services assistants. If the Web services assistant cannot be used then the following options are available:

  1. If you are implementing a Web service provider application then you should consider writing your own XML capable SOAP 'apphandler'.
  2. If you are implementing a Web service requester application then you should consider writing an XML capable application that uses the DFHPIRT channel linkable SOAP interface.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9014
No model group found for model group definition definition
Explanation:

There is an error in an XML schema referenced from the WSDL document. A required model group cannot be found for model group definition definition

System action:

The Web services assistant continues processing.

User response:

Correct the XML schema and then resubmit the DFHWS2LS job to reprocess the WSDL.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9015
A schema particle with unrecognized content has been found: value
Explanation:

There is an error in an XML schema referenced from the WSDL document. An XML particle value has been found with unrecognized content.

System action:

The Web services assistant continues processing.

User response:

Correct the XML schema and then resubmit the DFHWS2LS job to reprocess the WSDL.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9016
Required schema element element cannot be found.
Explanation:

There is an error in an XML schema referenced from the WSDL document. A schema element referenced either from the WSDL or from within the XML schema cannot be found. The missing element is element

System action:

The Web services assistant continues processing.

User response:

Correct the XML schema or the WSDL and then resubmit the DFHWS2LS job to reprocess the WSDL.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9017
Unsupported attribute attribute found for schema element element
Explanation:

An attribute that is not supported by DFHWS2LS has been found in an XML schema referenced from within the WSDL document. DFHWS2LS does not support the following schema attributes: 'substitutionGroup', 'abstract' and 'fixed'. The unsupported attribute has been found in schema element element

System action:

The Web services assistant continues processing.

User response:

Either redesign your WSDL to remove the content that is not supported by DFHWS2LS or consider implementing this Web service without the use of the Web services assistants. If the Web services assistant cannot be used then the following options are available:

  1. If you are implementing a Web service provider application then you should consider writing your own XML capable SOAP 'apphandler'.
  2. If you are implementing a Web service requester application then you should consider writing an XML capable application that uses the DFHPIRT channel linkable SOAP interface.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9018
Schema element element is missing a type definition.
Explanation:

There is an error in an XML schema referenced from the WSDL document. XML schema element element does not reference an XML type.

System action:

The Web services assistant continues processing.

User response:

Correct the XML schema and then resubmit the DFHWS2LS job to reprocess the WSDL.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9019
Schema type type is not supported.
Explanation:

An XML schema referenced within the WSDL document contains an XML type that is not supported by DFHWS2LS. The unsupported XML type is type

System action:

The Web services assistant continues processing.

User response:

Either redesign your WSDL to remove the content that is not supported by DFHWS2LS or consider implementing this Web service without the use of the Web services assistants. If the Web services assistant cannot be used then the following options are available:

  1. If you are implementing a Web service provider application then you should consider writing your own XML capable SOAP 'apphandler'.
  2. If you are implementing a Web service requester application then you should consider writing an XML capable application that uses the DFHPIRT channel linkable SOAP interface.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9020
Schema attribute attribute has been found and ignored for type type
Explanation:

An XML schema referenced within the WSDL document contains an XML type definition with an attribute. DFHWS2LS does not support XML attributes though it does tolerate their presence.

System action:

The Web services assistant continues processing. If the attribute is present in a SOAP message sent to CICS at runtime then it will be ignored.

User response:

Consider whether or not this attribute is important to your application. If it is acceptable that CICS ignores the attribute at runtime then you can safely ignore this message. If it is important that your application has access to the value of this attribute or that your application is able to set the value of this attribute then you will not be able to use the Web services assistants in the implementation of this Web service. The following options are available:

  1. If you are implementing a Web service provider application then you should consider writing your own XML capable SOAP 'apphandler'.
  2. If you are implementing a Web service requester application then you should consider writing an XML capable application that uses the DFHPIRT channel linkable SOAP interface.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9021
A schema type with unrecognized content has been found: value
Explanation:

There is an error in an XML schema referenced from the WSDL document. An XML type value has been found with unrecognized content.

System action:

The Web services assistant continues processing.

User response:

Correct the XML schema and then resubmit the DFHWS2LS job to re-process the WSDL.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9022
Schema type type is being restricted to a total of value digits in the response message of operation operation
Explanation:

An XML schema referenced from the WSDL document contains type definition type This type specifies a total number of digits which is too large for the target programming language to support. DFHWS2LS is restricting the type definition to a total of value digits. This type appears in the response message for operation operation

System action:

The Web services assistant continues processing. If at runtime a SOAP message is received with a value which is too large for the target field in the language structure then a conversion error will be indicated.

User response:

Consider whether you need to be able to support numbers which require more digits than are allowed in the DFHWS2LS mappings. If it is acceptable for CICS to impose this maximum length then you may safely ignore this message. Otherwise you will not be able to use the Web services assistants in the implementation of this Web service. The following options are available:

  1. If you are implementing a Web service provider application then you should consider writing your own XML capable SOAP 'apphandler'.
  2. If you are implementing a Web service requester application then you should consider writing an XML capable application that uses the DFHPIRT channel linkable SOAP interface.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9023
Schema type type is being restricted to a total of value digits for operation operation
Explanation:

An XML schema referenced from the WSDL document contains type definition type This type specifies a total number of digits which is too large for the target programming language to support. DFHWS2LS is restricting the type definition to a total of value digits. This type appears in the request message for operation operation

System action:

The Web services assistant continues processing. If at runtime a SOAP message is received with a value which is too large for the target field in the language structure then a conversion error will be indicated.

User response:

Consider whether you need to be able to support numbers which require more digits than are allowed in the DFHWS2LS mappings. If it is acceptable for CICS to impose this maximum length then you may safely ignore this message. Otherwise will not be able to use the Web services assistants in the implementation of this Web service. The following options are available:

  1. If you are implementing a Web service provider application then you should consider writing your own XML capable SOAP 'apphandler'.
  2. If you are implementing a Web service requester application then you should consider writing an XML capable application that uses the DFHPIRT channel linkable SOAP interface.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9024
Recursion within type type is not supported.
Explanation:

An XML schema referenced from the WSDL document contains a type definition which is defined recursively. DFHWS2LS does not support recursive definitions. The recursively defined type is type

System action:

The Web services assistant continues processing.

User response:

Either redesign your WSDL to remove the content that is not supported by DFHWS2LS or consider implementing this Web service without the use of the Web services assistants. If the Web services assistant cannot be used then the following options are available:

  1. If you are implementing a Web service provider application then you should consider writing your own XML capable SOAP 'apphandler'.
  2. If you are implementing a Web service requester application then you should consider writing an XML capable application that uses the DFHPIRT channel linkable SOAP interface.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9025
Required schema type type cannot be found.
Explanation:

There is an error in an XML schema referenced from the WSDL document. A schema type definition referenced either from the WSDL or from within the XML schema cannot be found. The missing type is type.

System action:

The Web services assistant continues processing.

User response:

Correct the XML schema or the WSDL and then resubmit the DFHWS2LS job to re-process the WSDL.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9026
URI uri cannot be resolved. Consider checking that the HTTP Proxy is correct.
Explanation:

A namespace reference within either the WSDL document or an XML schema referenced from the WSDL document cannot be resolved. DFHWS2LS has attempted to use the URI from the namespace to resolve the reference but has not been able to do so. This may be because a HTTP proxy service has not been specified or because there is no content available at the location implied by the URI. The URI is uri

System action:

The Web services assistant continues processing.

User response:

Specify the location of the HTTP proxy to use via the HTTPPROXY parameter. If the correct proxy has already been specified or if there is genuinely no content available at the location implied by the URI then add a schemaLocation XML attribute to the WSDL or schema in order to allow DFHWS2LS to locate the included content.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9027
The XML parser error has found an error: value at line line and column column in document document
Explanation:

The XML parser that is used to read the WSDL document and the XML schemas referenced from the WSDL document has encountered a problem. The problem has been found in document document at line line and column column The message issued by the XML parser is: value

System action:

The Web services assistant continues processing.

User response:

Correct the XML schema or the WSDL and then resubmit the DFHWS2LS job to re-process the WSDL.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9028
The length of schema element element is set to value characters. CICS only supports up to value2 characters.
Explanation:

An XML schema referenced from the WSDL document contains element element This element specifies a maximum size which is too large for DFHWS2LS to support. The XML schema has requested a length of up to value characters but the largest number supported by DFHWS2LS is value2 characters.

System action:

The Web services assistant continues processing.

User response:

Either redesign your WSDL to remove the content that is not supported by DFHWS2LS or consider implementing this Web service without the use of the Web services assistants. If the Web services assistant cannot be used then the following options are available:

  1. If you are implementing a Web service provider application then you should consider writing your own XML capable SOAP 'apphandler'.
  2. If you are implementing a Web service requester application then you should consider writing an XML capable application that uses the DFHPIRT channel linkable SOAP interface.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9029
Implicit padding (slack bytes) are not supported for PL/I. Please change the language structure to ensure that all slack bytes are explicitly referenced and that top level structures start on a double-word boundary. Slack bytes are needed near or around field field
Explanation:

DFHLS2WS is unable to correct determine the location of where slack bytes (also known as filler bytes) should be placed when PL/I is used to define a language structure. DFHLS2WS has determined that one or more slack bytes are needed somewhere near to field fieldbut is unsure of precisely where.

System action:

The Web services assistant continues processing.

User response:

Change the language structure to ensure that every byte is explicitly referenced and so that the first entry in the language structure starts on a double word boundary. If you are unable to predict precisely where filler fields must be placed to meet these requirements you could consider marking the fields as UNALIGNED and recompiling the application.

An alternative solution is to create a wrapper program. A wrapper program is a program which accepts input in a format that is suitable for use with DFHLS2WS and maps that input to the format needed by the target program. It then issues a LINK to the target program before converting the response back to an output format which is also suitable for use with DFHLS2WS.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9030
Implicit padding (slack bytes) are not supported for PL/I. Please change the language structure to ensure that all slack bytes are explicitly referenced and that top level structures start on a double-word boundary. Slack bytes are needed near or around structure structure
Explanation:

DFHLS2WS is unable to correct determine the location of where slack bytes (also known as filler bytes) should be placed when PL/I is used to define a language structure. DFHLS2WS has determined that one or more slack bytes are needed somewhere near to structure structure but is unsure of precisely where.

System action:

The Web services assistant continues processing.

User response:

Change the language structure to ensure that every byte is explicitly referenced and so that the first entry in the language structure starts on a double word boundary. If you are unable to predict precisely where filler fields must be placed to meet these requirements you could consider marking the fields as UNALIGNED and recompiling the application.

An alternative solution is to create a wrapper program. A wrapper program is a program which accepts input in a format that is suitable for use with DFHLS2WS and maps that input to the format needed by the target program. It then issues a LINK to the target program before converting the response back to an output format which is also suitable for use with DFHLS2WS.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9031
A structure or array is unexpectedly empty.
Explanation:

An internal processing error has occurred. DFHLS2WS has not been able to correctly parse a language structure.

System action:

The Web services assistant continues processing.

User response:

Contact your IBM support representative for further assistance.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9032
Schema attribute wild cards <anyAttribute> tags) are not supported.
Explanation:

An XML schema referenced from the WSDL document contains a schema attribute wild card (the <anyAttribute> XML schema tag). DFHWS2LS does not support attributes that are referenced in this way.

System action:

The Web services assistant continues processing and the schema attribute wild card is ignored. If at run time a message containing unrecognized attributes is received these attributes are ignored.

User response:

Consider whether the value of these attributes is important to your application. If it is acceptable for CICS to ignore these attributes then you may safely ignore this message. Otherwise you will not be able to use the Web services assistants in the implementation of this Web service. The following options are available:

  1. If you are implementing a Web service provider application then you should consider writing your own XML capable SOAP 'apphandler'.
  2. If you are implementing a Web service requester application then you should consider writing an XML capable application that uses the DFHPIRT channel linkable SOAP interface.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9500
An internal error has occurred. Please contact IBM Support.
Explanation:

The Web services assistant has caught an unexpected exception.

System action:

The Web services assistant continues processing.

User response:

Contact your IBM support representative for further assistance.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9501
The HTTPPROXY parameter is invalid. The correct format is proxy.hostname.com:8080 or similar.
Explanation:

The value of the HTTPPROXY parameter is invalid.

System action:

The Web services assistant continues processing.

User response:

Correct or remove the HTTPPROXY parameter.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9502
One or more incorrect parameters have been specified.
Explanation:

The Web services assistant cannot continue as one or more errors have been detected in the input parameters.

System action:

The Web services assistant fails with a return code of 8.

User response:

Correct the errors in the input parameters details of which can be found in the previous messages issued.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9503
Required parameter parameter is missing.
Explanation:

A required parameter is missing from the input parameters. The missing parameter is parameter

System action:

The Web services assistant continues processing.

User response:

Provide a value for the missing parameter.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9504
Parameter parameter has been specified but is not valid for program program
Explanation:

A parameter has been specified that was not expected. For example, a value may have been provided for the BINDING parameter in DFHLS2WS. A BINDING is only valid as input to DFHWS2LS. The unexpected parameter is parameter

System action:

The Web services assistant continues processing.

User response:

Remove the unexpected parameter.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9505 E
Invalid value specified for the LANG parameter. Valid values are: COBOL, PLI-ENTERPRISE, PLI-OTHER, C or CPP.
Explanation:

An invalid value has been specified for the LANG parameter.

System action:

The Web services assistant continues processing.

User response:

Correct the value of the LANG parameter.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9506 E
Parameter parameter exceeds the maximum valid length of value characters.
Explanation:

The value of parameter parameter is too long.

System action:

The Web services assistant continues processing.

User response:

Change the value to be no longer than value characters long.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9507
Parameter parameter is not set therefore parameter parameter2 is ignored.
Explanation:

Parameter parameter2 has been ignored because parameter parameter is not set. For example, a PGMINT value only makes sense if a PROGRAM value has also been supplied.

System action:

The Web services assistant continues processing.

User response:

Consider removing the unexpected parameter.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9508
Invalid value specified for the URI parameter. The URI specified must be relative.
Explanation:

The value of the URI parameter is invalid. The value specified must be relative rather than absolute. For example, the following example URI is acceptable: '/ibm/cics/testURI' .

System action:

The Web services assistant continues processing.

User response:

Correct the value of the URI parameter.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9509
Parameter parameter contains invalid characters.
Explanation:

One or more invalid characters have been found in parameter parameter

System action:

The Web services assistant continues processing.

User response:

Correct the value of the parameter.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9510
Invalid value specified for the PGMINT parameter. Valid values are: CHANNEL or COMMAREA. The default value of CHANNEL is assumed.
Explanation:

An invalid value has been specified for the PGMINT parameter.

System action:

The Web services assistant continues processing.

User response:

Correct the value of the PGMINT parameter.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9511
Parameter PGMINT is set to CHANNEL but parameter CONTID is not set. The default value of value is assumed.
Explanation:

The program interface has been defined as 'Channel' but a container name has not been provided to indicate the name of the container that CICS should populate at runtime. A default value of valuehas been assumed.

System action:

The Web services assistant continues processing.

User response:

Consider whether the default container name is acceptable. If you are enabling an existing channel based application as a Web service then it is likely that the default container name is incorrect. If the default container name is acceptable then you can safely ignore this message.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9512
Parameter CONTID is set but not needed for PGMINT=COMMAREA. Parameter CONTID is ignored.
Explanation:

The CONTID input parameter has been specified but is ignored as the program interface has been defined to be a COMMAREA.

System action:

The Web services assistant continues processing.

User response:

Consider either removing the CONTID parameter or changing the PGMINT to CHANNEL.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9513
The value of parameter WSBIND is missing a file extension, .wsbind is assumed.
Explanation:

A file extension has not been provided for the WSBind file. If you wish to use the PIPELINE scan mechanism for automatically creating WEBSERVICE resources from WSBind files then you must use an extension of '.wsbind'. This file extension has therefore been assumed.

System action:

The Web services assistant continues processing.

User response:

Consider adding '.wsbind' to the end of your WSBIND parameter value.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9514
The value of parameter WSBIND specified a file extension other than .wsbind.
Explanation:

A file extension other than '.wsbind' has been used for the WSBind file. If you wish to use the PIPELINE scan mechanism for automatically creating WEBSERVICE resources from WSBind files then you must use an extension of '.wsbind'.

System action:

The Web services assistant continues processing.

User response:

Consider changing the extension of the WSBIND parameter to '.wsbind'.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9515
PDS library library cannot be found.
Explanation:

The PDS library specified in the PDSLIB input parameter cannot be found.

System action:

The Web services assistant continues processing.

User response:

Correct the PDSLIB input parameter.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9516
PDS library library exists but cannot be read.
Explanation:

The PDS library specified in the PDSLIB input parameter exists but cannot be read. This may be because the userid under which the Web services assistant is executing does not have permission to view the PDS or because an exclusive lock is being held by another process.

System action:

The Web services assistant continues processing.

User response:

Ensure that permission is assigned to allow the Web services assistant to read from the PDSLIB. Ensure that no other process has a lock on the PDSLIB.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9517
PDS library library exists but cannot be written to.
Explanation:

The PDS library specified in the PDSLIB input parameter exists but cannot be written to. This may be because the userid under which the Web services assistant is executing does not have permission to alter the PDS or because an exclusive lock is being held by another process.

System action:

The Web services assistant continues processing.

User response:

Ensure that permission is assigned to allow the Web services assistant to alter the PDSLIB. Ensure that no other process has a lock on the PDSLIB.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9518
PDS library library specifies a record length less than 80 characters, output may be truncated.
Explanation:

The PDS library specified in the PDSLIB input parameter specifies a record length less than 80 characters. DFHWS2LS requires 80 characters for the creation of language structures, it is therefore likely that truncation will occur.

System action:

The Web services assistant continues processing.

User response:

Consider changing the PDSLIB to a fixed record data set with a logical record length of 80 characters.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9519
Code page codepage is not recognized.
Explanation:

The code page indicated in the PDSCP input parameter is not recognized. The Web services assistants use the code page support built in to Java, Java does not recognize the named code page.

System action:

The Web services assistant continues processing.

User response:

Remove or correct the PDSCP parameter. If the PDSCP parameter is not set then the same code page is used when reading from and writing to the PDS library as is used when reading from and writing to HFS. This code page is determined according to the default code page configured for UNIX System Services.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9520
Parameter RESPMEM and parameter REQMEM must supply different values.
Explanation:

The same language structure name has been used for both the request and the response messages. DFHWS2LS requires that these names be unique even if it is likely that the generated language structures will be identical.

System action:

The Web services assistant continues processing.

User response:

Change one of the REQMEM and RESPMEM input parameters in order to make them unique.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9521
The record format of PDS member member must be FB and have a record length of 80.
Explanation:

The location at which the language structures are to be written to or read from is not a fixed block PDS member.

System action:

The Web services assistant continues processing.

User response:

Change the location of the PDSLIB input parameter to indicate a FB data set.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9522
File file cannot be read.
Explanation:

File file exists but cannot be read. This may be because the userid under which DFHLS2WS is executing does not have access permission to the specified resource.

System action:

The Web services assistant continues processing.

User response:

Correct the problem.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9523
An unexpected error occurred whilst processing file file The problem is: value
Explanation:

An exception was caught whilst attempting to process file file The exception included a message to identify the problem which is indicated in value

DFHWS2LS requires an exclusive lock on the partitioned data set to which it is writing language structures. This message may be issued if an exclusive lock is not currently available.

System action:

The Web services assistant continues processing.

User response:

Correct the identified problem.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9524
File file cannot be written to.
Explanation:

File file exists but cannot be written to. This may be because the userid under which DFHWS2LS is executing does not have alter permission to the specified resource.

System action:

The Web services assistant continues processing.

User response:

Correct the problem.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9525
Cannot write a file because directory directory does not exist.
Explanation:

Directory directory does not exist. Therefore the Web services assistant is unable to create an output file that should be written to that directory.

System action:

The Web services assistant continues processing.

User response:

Either create the directory or change the input parameters to indicate a different output location.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9526
Cannot write a file because directory directory is not writable.
Explanation:

Directory directory exists but the userid under which the Web services assistant is executing does not have write permission to create a new file within it.

System action:

The Web services assistant continues processing.

User response:

Either change the permissions for the directory or change the input parameters to indicate a different output location. Note: This message cannot be changed with the message editing utility.

Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9527
Cannot write to the log file, file, is not writable.
Explanation:

File file exists but the userid under which the Web services assistant is executing does not have write permission to change it.

System action:

The Web services assistant continues processing.

User response:

Either change the permissions for the file or change the input parameters to indicate a different output location.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9528
Cannot find or read file file
Explanation:

File file either does not exist the userid under which the Web services assistant is executing does not have permission to read it.

System action:

The Web services assistant continues processing.

User response:

Either change the permissions for the file or correct the input parameters to indicate a different input file.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9529
Characters beyond column column have been truncated for line line
Explanation:

The input parameters extend beyond character 72. The problematic line identified is line

System action:

The Web services assistant continues processing.

User response:

Change the indicated line to use less than 72 characters of data.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9530
Parameter parameter is not recognized and has been ignored.
Explanation:

An unrecognized parameter has been found amongst the input parameters.

System action:

The Web services assistant continues processing.

User response:

Consider removing the named parameter.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9531
Parameter STRUCTURE must only contain ( or ) characters in the first or last position.
Explanation:

The STRUCTURE input parameter is not well formed. It may only contain bracket characters at the start and end of the value.

System action:

The Web services assistant continues processing.

User response:

Correct the value of the STRUCTURE input parameter.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9532
Parameter STRUCTURE must be of the form STRUCTURE=(request_structure_name, response_structure_name).
Explanation:

The STRUCTURE input parameter is not well formed. It should contain two structure names separated by a comma and entirely enclosed within rounded brackets as in the following example: STRUCTURE=(request_structure_name,response_structure_name).

System action:

The Web services assistant continues processing.

User response:

Correct the value of the STRUCTURE input parameter.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9533
Parameter parameter contains an invalid character character at position position in value value
Explanation:

An invalid character has been found in parameter character

System action:

The Web services assistant continues processing.

User response:

Correct the value of the named input parameter.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9534
None unique operation signature found: value
Explanation:

No explanation is available for this message.

System action:

The Web services assistant continues processing.

User response:

Note: This message cannot be changed with the message editing utility.

Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9535
WSDL operation operation has an operation signature greater than value characters long and therefore is not supported by CICS.
Explanation:

Operation operation in the WSDL document has a wire signature that is longer than value characters. DFHWS2LS can not process this operation. The wire signature is used to determine the operation that is being invoked based on the sequence of XML child elements found within the SOAP:body element at run time. If there are a large number of such child elements or the child elements have unusually long names then the generated signature may be too large.

System action:

The Web services assistant continues processing.

User response:

Either redesign your WSDL to remove the content that is not supported by DFHWS2LS or consider implementing this Web service without the use of the Web services assistants. If the Web services assistant cannot be used then the following options are available:

  1. If you are implementing a Web service provider application then you should consider writing your own XML capable SOAP 'apphandler'.
  2. If you are implementing a Web service requester application then you should consider writing an XML capable application that uses the DFHPIRT channel linkable SOAP interface.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9536
User Defined Type type cannot be found.
Explanation:

DFHLS2WS is unable to locate a required user defined type with the C or C++ header file.

System action:

The Web services assistant continues processing.

User response:

Change the C header file to include the required user defined type.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9537
Compiler directive directive has been ignored.
Explanation:

DFHLS2WS has found a compiler directive within the C or C++ header file. Compiler directives are not supported.

System action:

The Web services assistant continues processing.

User response:

Consider removing the compiler directive from the header file. If the compiler directive is important to how the compiler processes the structures within the header file then it may be necessary to change those structures in order to ensure that DFHLS2WS interprets them correctly.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9538
The required struct entry cannot be found.
Explanation:

DFHLS2WS is unable to locate a required structure which is referenced in the C or C++ header file.

System action:

The Web services assistant continues processing.

User response:

Change the C header file to include the required structure.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9539
An invalid character character has been found.
Explanation:

An invalid character has been found in the C or C++ header file.

System action:

The Web services assistant continues processing.

User response:

Correct the header file.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9540
Unsupported keyword keyword has been found.
Explanation:

DFHLS2WS has detected a keyword keyword that is not currently supported.

System action:

The Web services assistant continues processing.

User response:

Consider removing the unsupported keyword from the input file. If the keyword is important to the shape of the language structure in memory then it may be necessary to create a wrapper program. A wrapper program is a program which accepts input in a format that is suitable for use with DFHLS2WS and maps that input to the format needed by the target program. It then issues a LINK to the target program before converting the response back to an output format which is also suitable for use with DFHLS2WS.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9541
Fixed point decimal types are not supported.
Explanation:

DFHLS2WS has detected an unsupported data type in a C or C++ header file.

System action:

The Web services assistant continues processing.

User response:

Consider removing the unsupported data type from the input file. If the data type is important to the shape of the language structure in memory then it may be necessary to create a wrapper program. A wrapper program is a program which accepts input in a format that is suitable for use with DFHLS2WS and maps that input to the format needed by the target program. It then issues a LINK to the target program before converting the response back to an output format which is also suitable for use with DFHLS2WS.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9542
Unsupported macro macro has been found.
Explanation:

DFHLS2WS has found a macro within the C or C++ header file. Macros are not supported.

System action:

The Web services assistant continues processing.

User response:

Consider removing the unsupported macro from the input file. If the macro is important to the shape of the language structure in memory then it may be necessary to create a wrapper program. A wrapper program is a program which accepts input in a format that is suitable for use with DFHLS2WS and maps that input to the format needed by the target program. It then issues a LINK to the target program before converting the response back to an output format which is also suitable for use with DFHLS2WS.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9543
Constant constant is not supported in array dimension.
Explanation:

DFHLS2WS has found a constant within an array declaration. This is not supported.

System action:

The Web services assistant continues processing.

User response:

Consider removing the unsupported constant from the input file. If the constant is important to the shape of the language structure in memory then it may be necessary to create a wrapper program. A wrapper program is a program which accepts input in a format that is suitable for use with DFHLS2WS and maps that input to the format needed by the target program. It then issues a LINK to the target program before converting the response back to an output format which is also suitable for use with DFHLS2WS.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9544
Unsupported keyword keyword has been found and ignored.
Explanation:

DFHLS2WS has detected a keyword keyword that is not currently supported, it has been ignored.

System action:

The Web services assistant continues processing.

User response:

Consider whether it is acceptable that this keyword has been ignored. If it is acceptable then you can safely ignore this message. If it is not acceptable then it may be necessary to create a wrapper program. A wrapper program is a program which accepts input in a format that is suitable for use with DFHLS2WS and maps that input to the format needed by the target program. It then issues a LINK to the target program before converting the response back to an output format which is also suitable for use with DFHLS2WS.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9545
Assignment operator detected and ignored.
Explanation:

DFHLS2WS has detected and ignored an assignment operator within a C or C++ header file.

System action:

The Web services assistant continues processing.

User response:

Consider removing the assignment operator from the header file.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9546
Initialization operator detected and ignored.
Explanation:

DFHLS2WS has detected and ignored an initialization operator within a C or C++ header file.

System action:

The Web services assistant continues processing.

User response:

Consider removing the initialization operator from the header file.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9547
Top level variables are not supported: value
Explanation:

DFHLS2WS has encountered a variable value within a C or C++ header file that is not part of a structure or part of a type definition. This is not supported.

System action:

The Web services assistant continues processing.

User response:

Consider removing the named variable from the header file.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9548
Top-level structure structure must be named value
Explanation:

DFHLS2WS has been unable to locate a requested structure within the C or C++ header file.

System action:

The Web services assistant continues processing.

User response:

Correct or supply a value for the STRUCTURE input parameter.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9549
A type definition has been found with no instance and no label.
Explanation:

DFHLS2WS has detected a type definition in the C or C++ header file that is either missing a label or is missing an instance name.

System action:

The Web services assistant continues processing.

User response:

Correct the header file.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9550
Duplicate type name name found.
Explanation:

DFHLS2WS has detected a duplicate type definition in the C or C++ header file.

System action:

The Web services assistant continues processing.

User response:

Correct the header file.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9551
Structure structure cannot be found.
Explanation:

DFHLS2WS has been unable to locate the main structure within the C or C++ header file.

System action:

The Web services assistant continues processing.

User response:

Correct or supply a value for the STRUCTURE input parameter.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9552
Value value is not a valid number.
Explanation:

DFHLS2WS has encountered a value that should be numeric but does not appear to be a valid number. The problematic value is value

System action:

The Web services assistant continues processing.

User response:

Correct the language structure.

Note:
This message cannot be changed with the message editing utility.

.

Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9553
PICTURE picture is not supported for BINARY or DISPLAY types.
Explanation:

DFHLS2WS has detected a PICTURE clause that it does not currently support for BINARY or DISPLAY data types.

System action:

The Web services assistant continues processing.

User response:

Consider removing the unsupported PICTURE from the input file. If the PICTURE is important to the shape of the language structure in memory then it may be necessary to create a wrapper program. A wrapper program is a program which accepts input in a format that is suitable for use with DFHLS2WS and maps that input to the format needed by the target program. It then issues a LINK to the target program before converting the response back to an output format which is also suitable for use with DFHLS2WS.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9554
PICTURE picture is not supported.
Explanation:

DFHLS2WS has detected a PICTURE clause that it does not currently support.

System action:

The Web services assistant continues processing.

User response:

Consider removing the unsupported PICTURE from the input file. If the PICTURE is important to the shape of the language structure in memory then it may be necessary to create a wrapper program. A wrapper program is a program which accepts input in a format that is suitable for use with DFHLS2WS and maps that input to the format needed by the target program. It then issues a LINK to the target program before converting the response back to an output format which is also suitable for use with DFHLS2WS.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9555
Top level structure found within the main structure.
Explanation:

DFHLS2WS has detected an error in one of the language structures. 01 level identifiers should not be present within the main language structure.

System action:

The Web services assistant continues processing.

User response:

Remove the 01 level identifier from within the language structure.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9556
An unexpected error occurred whilst writing to file file The problem is: value
Explanation:

An exception was caught whilst attempting to write to file file The exception included a message to identify the problem which is indicated in value

System action:

The Web services assistant continues processing.

User response:

Correct the identified problem.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9557
ERRORS and WARNINGS have been generated processing file file
Explanation:

One or more error messages and one or more warning messages have been issued by the Web services assistant.

System action:

The web services assistant fails with return code 12.

User response:

Resolve the previously issued error messages and consider addressing the warning messages.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9558
ERRORS have been generated processing file file
Explanation:

One or more error messages have been issued by the Web services assistant.

System action:

The web services assistant fails with return code 12.

User response:

Resolve the previously issued error messages.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9559
Illegal character character has been found at the start of a name and replaced with X.
Explanation:

DFHLS2WS has found a character at the start of a field name in the language structure that is not valid in XML. It has been replaced with a substitute character.

System action:

The Web services assistant continues processing.

User response:

Consider whether the new name is appropriate to expose in the WSDL. If you are unhappy with the name chosen you can either change the language structure and rerun DFHLS2WS or change the WSDL and run DFHWS2LS.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9560
Illegal character character has been found in a name and replaced with X.
Explanation:

DFHLS2WS has found a character in a field name in the language structure that is not valid in XML. It has been replaced with a substitute character.

System action:

The Web services assistant continues processing.

User response:

Consider whether the new name is appropriate to expose in the WSDL. If you are unhappy with the name chosen you can either change the language structure and rerun DFHLS2WS or change the WSDL and run

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9561
Identifier identifier has generated a name-clash for operation operation Subsequent declarations have been renamed to ensure their uniqueness.
Explanation:

DFHLS2WS has detected a field name in the language structure which will clash with another name when converted to XML. The name has been changed to ensure that this does not happen.

System action:

The Web services assistant continues processing.

User response:

Consider whether the new name is appropriate to expose in the WSDL. If you are unhappy with the name chosen you can either change the language structure and rerun DFHLS2WS or change the WSDL and run

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9562
Parameter PGMINT is specified with value COMMAREA but there is too much data required for a COMMAREA.
Explanation:

DFHLS2WS has been asked to process language structures for a COMMAREA based PROGRAM. The language structures processed require more than 32K of data and therefore are too large for use with a COMMAREA.

System action:

The Web services assistant continues processing.

User response:

Consider changing the PGMINT input parameter to CHANNEL rather than COMMAREA.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9563
Unsupported PL/I source code detected in line line
Explanation:

DFHLS2WS has spotted a line of PL/I based code that it does not support at line line

System action:

The Web services assistant continues processing.

User response:

Consider removing the unsupported line from the input file. If the line is important to the shape of the language structure in memory then it may be necessary to create a wrapper program. A wrapper program is a program which accepts input in a format that is suitable for use with DFHLS2WS and maps that input to the format needed by the target program. It then issues a LINK to the target program before converting the response back to an output format which is also suitable for use with DFHLS2WS.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9564
A terminating ; is missing, it is assumed to be at the end of the file.
Explanation:

The termination character for a language structure is missing. It is assumed that the end of file indicates the end of the language structure.

System action:

The Web services assistant continues processing.

User response:

Correct the language structure.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9565
ALIGNED and UNALIGNED keywords are not supported for an entire structure.
Explanation:

An ALIGNED keyword or an UNALIGNED keyword has been applied to a structure in a PL/I language structure. This is not supported in DFHLS2WS.

System action:

The Web services assistant continues processing.

User response:

Change each entry within the language structure to specify ALIGNED or UNALIGNED individually.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9566
The default FLOAT attribute is not supported: value
Explanation:

DFHLS2WS has determined that a DECIMAL or BINARY field in a PL/I language structure is of type FLOAT due to the absence of the FIXED keyword. The FLOAT data type is not supported.

System action:

The Web services assistant continues processing.

User response:

Consider changing the field to explicitly specify FIXED. If this is not possible then consider writing a wrapper program. A wrapper program is a program which accepts input in a format that is suitable for use with DFHLS2WS and maps that input to the format needed by the target program. It then issues a LINK to the target program before converting the response back to an output format which is also suitable for use with DFHLS2WS.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9567
Too many digits have been specified for a packed decimal field: value
Explanation:

DFHLS2WS has spotted an error in a PL/I language structure. A packed decimal field has specified a greater number of digits than can be supported for that language.

System action:

The Web services assistant continues processing.

User response:

Correct the language structure.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9568
The UNSIGNED attribute is not supported unless PLI-ENTERPRISE is specified: value
Explanation:

DFHLS2WS has spotted an error in a PL/I language structure. The UNSIGNED keyword has been used even though it is not available before Enterprise level PL/I.

System action:

The Web services assistant continues processing.

User response:

Either correct the language structure or change the LANG input parameter to specify PLI-ENTERPRISE.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9569
Unsupported PL/I source code detected after line line
Explanation:

DFHLS2WS has spotted a line of PL/I based code that it does not support after line line

System action:

The Web services assistant continues processing.

User response:

Consider removing the unsupported line from the input file. If the line is important to the shape of the language structure in memory then it may be necessary to create a wrapper program. A wrapper program is a program which accepts input in a format that is suitable for use with DFHLS2WS and maps that input to the format needed by the target program. It then issues a LINK to the target program before converting the response back to an output format which is also suitable for use with DFHLS2WS.

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9570
FIXED BINARY types with length greater than 31 are not supported unless PLI-ENTERPRISE is specified: value
Explanation:

DFHLS2WS has detected an error in a PL/I language structure. A FIXED BINARY length greater than 31 has been specified. This is not allowed for versions of PL/I prior to Enterprise PL/I.

System action:

The Web services assistant continues processing.

User response:

Either correct the language structure or change the LANG input parameter to specify PLI-ENTERPRISE.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9571
ORDINAL references are always treated as SIGNED FIXED BINARY (7) data types. If this is incorrect then please replace the ordinal reference with an equivalent FIXED BINARY variable: value
Explanation:

DFHLS2WS has detected an Ordinal data type in a PL/I language structure. These are always treated as though they are SIGNED FIXED BINARY (7) data types.

System action:

The Web services assistant continues processing.

User response:

Consider whether or not this assumption is appropriate. If it is not then you should either change the language structure to replace the ordinal data type with an equivalent data type or you should write a wrapper program. A wrapper program is a program which accepts input in a format that is suitable for use with DFHLS2WS and maps that input to the format needed by the target program. It then issues a LINK to the target program before converting the response back to an output format which is also suitable for use with DFHLS2WS.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9572
ORDINAL types are only supported if PLI-ENTERPRISE is specified: value
Explanation:

DFHLS2WS has detected an error in a PL/I language structure. An ordinal data type has been specified. This is not allowed for versions of PL/I prior to Enterprise PL/I.

System action:

The Web services assistant continues processing.

User response:

Either correct the language structure or change the LANG input parameter to specify PLI-ENTERPRISE.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9573
BIT fields are only supported if they are in multiples of 8: value
Explanation:

DFHLS2WS has detected a BIT field in a PL/I language structure which specifies a number of bits that are not exactly divisible by 8. This is not supported by DFHLS2WS.

System action:

The Web services assistant continues processing.

User response:

Consider changing the language structure to remove this field or to change its length to a multiple of 8. If this change is not appropriate then consider writing a wrapper program. A wrapper program is a program which accepts input in a format that is suitable for use with DFHLS2WS and maps that input to the format needed by the target program. It then issues a LINK to the target program before converting the response back to an output format which is also suitable for use with DFHLS2WS.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9574
Lengths of zero are not supported for CHAR data types.
Explanation:

DFHLS2WS has detected a problem in a PL/I language structure. A data type specifies a length of 0.

System action:

The Web services assistant continues processing.

User response:

Correct the problem.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9575
The length of a PICTURE cannot be found: value
Explanation:

DFHLS2WS has detected a problem in a PL/I language structure. The length of a PICTURE clause can not be determined.

System action:

The Web services assistant continues processing.

User response:

Correct the problem.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9576
FIXED BINARY data types with a scaling factor of the form (p,q) with q not equal to 0 are not supported: value
Explanation:

DFHLS2WS has detected an unsupported data type in a PL/I language structure. FIXED BINARY scaling factors are not supported.

System action:

The Web services assistant continues processing.

User response:

Consider removing the unsupported data type from the input file. If the data type is important to the shape of the language structure in memory then it may be necessary to create a wrapper program. A wrapper program is a program which accepts input in a format that is suitable for use with DFHLS2WS and maps that input to the format needed by the target program. It then issues a LINK to the target program before converting the response back to an output format which is also suitable for use with DFHLS2WS.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9577
Precision factor factor is too large: value
Explanation:

DFHLS2WS has detected an error in a PL/I language structure. A precision factor which is too large for PL/I has been specified.

System action:

The Web services assistant continues processing.

User response:

Correct the problem.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9578
FIXED DECIMAL data types with a scaling factor of the form (p,q) with q greater than p are not supported: value
Explanation:

DFHLS2WS has detected an unsupported data type in a PL/I language structure. DFHLS2WS is unable to support scaling factors in the form (p,q) where q is greater than p.

System action:

The Web services assistant continues processing.

User response:

Consider removing the unsupported data type from the input file. If the data type is important to the shape of the language structure in memory then it may be necessary to create a wrapper program. A wrapper program is a program which accepts input in a format that is suitable for use with DFHLS2WS and maps that input to the format needed by the target program. It then issues a LINK to the target program before converting the response back to an output format which is also suitable for use with DFHLS2WS.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9579
FIXED DECIMAL data types with a scaling factor of the form (p,q) with q less than 0 are not supported: value
Explanation:

DFHLS2WS has detected an unsupported data type in a PL/I language structure. DFHLS2WS is unable to support scaling factors in the form (p,q) where q is less than 0.

System action:

The Web services assistant continues processing.

User response:

Consider removing the unsupported data type from the input file. If the data type is important to the shape of the language structure in memory then it may be necessary to create a wrapper program. A wrapper program is a program which accepts input in a format that is suitable for use with DFHLS2WS and maps that input to the format needed by the target program. It then issues a LINK to the target program before converting the response back to an output format which is also suitable for use with DFHLS2WS.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9580
PDS member member has been replaced.
Explanation:

The Web services assistant as replaced existing PDS member member.

System action:

The Web services assistant continues processing.

User response:

No user action is required. You may safely ignore this message.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9581
An unexpected exception occurred when writing to the PDS.
Explanation:

The Web services assistant has been unable to write to the PDS library. This may be because another process has a lock on the PDS.

System action:

The Web services assistant continues processing.

User response:

Ensure that all other processes which have locks on the PDS release those locks.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9582
File file has been replaced.
Explanation:

The Web services assistant as replaced existing file file

System action:

The Web services assistant continues processing.

User response:

No user action is required. You may safely ignore this message.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9583
The supplied WSDL contains an element with different minOccurs and maxOccurs values. This is only supported when PGMINT is set to CHANNEL.
Explanation:

DFHWS2LS has detected an XML element which will occur in a SOAP message an unknown number of times. This is only supported if the PGMINT input parameter is set to CHANNEL.

System action:

The Web services assistant continues processing.

User response:

Change the value of the PGMINT input parameter to CHANNEL.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9584
The WSDL file contains at least one request message but the REQMEM parameter has not been set.
Explanation:

DFHWS2LS needs to generate one or more language structures for request messages but the REQMEM input parameter has not been set.

System action:

The Web services assistant continues processing.

User response:

Specify a value for the REQMEM input parameter.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9585
The WSDL file contains at least one response message but the RESPMEM parameter has not been set.
Explanation:

DFHWS2LS needs to generate one or more language structures for response messages but the RESPMEM input parameter has not been set.

System action:

The Web services assistant continues processing.

User response:

Specify a value for the RESPMEM input parameter.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9586
A reserved word word has been detected in the WSDL, it has been changed to value
Explanation:

DFHWS2LS has detected an element name in the WSDL document that is not valid as a keyword in the target programming language. It has been renamed as indicated.

System action:

The Web services assistant continues processing.

User response:

You may safely ignore this message.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9587
Program program has completed SUCCESSFULLY.
Explanation:

The Web services assistant has completed processing. No error or warning messages have been issued.

System action:

The Web services assistant ends with return code 0.

User response:

You may safely ignore this message.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9588
WSDL binding binding has no operation elements in the WSDL.
Explanation:

DFHWS2LS has not found any WSDL operations associated with WSDL binding binding

System action:

The Web services assistant continues processing.

User response:

Either correct the WSDL document or supply a different value for the BINDING input parameter.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9589
The supplied WSDL requires too much data for a CICS Commarea. The PGMINT parameter must be set to CHANNEL.
Explanation:

DFHWS2LS has been asked to generate language structures for a COMMAREA based PROGRAM. The language structures generated require more than 32K of data and therefore are too large for use with a COMMAREA.

System action:

The Web services assistant continues processing.

User response:

Consider changing the PGMINT input parameter to CHANNEL rather than COMMAREA.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9590
A style attribute has not been specified for WSDL operation operation
Explanation:

DFHWS2LS has detected an error in the WSDL document. The binding for WSDL operation operation must have a 'style' specified. The style may be either 'rpc' or 'document'.

System action:

The Web services assistant continues processing.

User response:

Correct the WSDL.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9591
No input message has been found for WSDL operation operation
Explanation:

DFHWS2LS has encountered a problem with the WSDL document. Operation operation is missing a WSDL input message. DFHWS2LS does not support response only Web services.

System action:

The Web services assistant continues processing.

User response:

Either correct the WSDL document or specify a different BINDING input parameter.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9592
An expected soapAction attribute is missing for WSDL operation operation
Explanation:

DFHWS2LS has detected an error in the WSDL document. The WSDL binding is missing a soapAction attribute for operation operation

System action:

The Web services assistant continues processing.

User response:

Consider whether the absence of the soapAction is a problem. If your application does not require the soapAction attribute then you can safely ignore this message.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9593 W
An unexpected soapAction attribute has been found for WSDL operation operation This can only be used with SOAP version 1.1.
Explanation:

DFHWS2LS has detected an error in the WSDL document. The WSDL binding specifies a soapAction attribute for use with SOAP 1.2.

System action:

The Web services assistant continues processing.

User response:

Consider removing the soapAction attribute or changing the WSDL to indicate the use of SOAP 1.1.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9594 E
An unexpected soapAction attribute has been found for WSDL operation operation This can only be used with a HTTP transport mechanism.
Explanation:

DFHWS2LS has detected an error in the WSDL document. The WSDL binding specifies a soapAction attribute for a non-HTTP transport protocol.

System action:

The Web services assistant continues processing.

User response:

Remove the soapAction attribute.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9595 E
A WSDL binding contains a mixture of rpc and document style attributes. This is not supported.
Explanation:

DFHWS2LS has encountered a problem processing the WSDL document. The WSDL binding specifies a mixture of 'rpc' style messages and 'document' style messages. DFHWS2LS does not support mixed styles within a binding.

System action:

The Web services assistant continues processing.

User response:

Either redesign your WSDL to remove the content that is not supported by DFHWS2LS or consider implementing this Web service without the use of the Web services assistants. If the Web services assistant cannot be used then the following options are available:

  1. If you are implementing a Web service provider application then you should consider writing your own XML capable SOAP 'apphandler'.
  2. If you are implementing a Web service requester application then you should consider writing an XML capable application that uses the DFHPIRT channel linkable SOAP interface.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9596
The WSDL Binding for operation operation is missing an input message.
Explanation:

DFHWS2LS has encountered a problem with the WSDL document. Binding binding for operation operation is missing a WSDL input binding. DFHWS2LS does not support response only Web services.

System action:

The Web services assistant continues processing.

User response:

Either correct the WSDL document or specify a different BINDING input parameter.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9597
The WSDL file contains a soap:body tag with a use attribute value of value Only literal WSDL is supported.
Explanation:

DFHWS2LS has encountered a problem with the WSDL document. The WSDL binding specifies a 'use' attribute value of value DFHWS2LS only supports a value of 'literal'.

System action:

The Web services assistant continues processing.

User response:

Either redesign your WSDL to remove the content that is not supported by DFHWS2LS or consider implementing this Web service without the use of the Web services assistants. If the Web services assistant cannot be used then the following options are available:

  1. If you are implementing a Web service provider application then you should consider writing your own XML capable SOAP 'apphandler'.
  2. If you are implementing a Web service requester application then you should consider writing an XML capable application that uses the DFHPIRT channel linkable SOAP interface.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9598
WSDL binding binding references more than one transport protocol. Only one protocol is supported.
Explanation:

DFHWS2LS has encountered a problem with the WSDL document. The WSDL binding specifies more than one transport protocol. DFHWS2LS only supports one transport protocol per binding.

System action:

The Web services assistant continues processing.

User response:

Either redesign your WSDL to remove the content that is not supported by DFHWS2LS or consider implementing this Web service without the use of the Web services assistants. If the Web services assistant cannot be used then the following options are available:

  1. If you are implementing a Web service provider application then you should consider writing your own XML capable SOAP 'apphandler'.
  2. If you are implementing a Web service requester application then you should consider writing an XML capable application that uses the DFHPIRT channel linkable SOAP interface.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9599
WSDL binding binding is not associated with a transport protocol.
Explanation:

DFHWS2LS has encountered a problem with the WSDL document. The WSDL binding specifies no transport protocols. DFHWS2LS requires one transport protocol per binding.

System action:

The Web services assistant continues processing.

User response:

Either redesign your WSDL to remove the content that is not supported by DFHWS2LS or consider implementing this Web service without the use of the Web services assistants. If the Web services assistant cannot be used then the following options are available:

  1. If you are implementing a Web service provider application then you should consider writing your own XML capable SOAP 'apphandler'.
  2. If you are implementing a Web service requester application then you should consider writing an XML capable application that uses the DFHPIRT channel linkable SOAP interface.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9600
The WSDL file contains multiple binding elements. The BINDING parameter must be set to specify which one to use.
Explanation:

The WSDL document contains more than one binding element. The BINDING input parameter was not set therefore DFHWS2LS cannot determine which WSDL binding to process.

System action:

The Web services assistant continues processing.

User response:

Specify a value for the BINDING input parameter.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9601
Binding element element cannot be found in the WSDL file. Only one of the following values may be specified: value
Explanation:

The value of the BINDING input parameter does not identify a binding element in the WSDL document.

System action:

The Web services assistant continues processing.

User response:

Correct the value of the BINDING input parameter.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9602
WSDL binding binding is not a SOAP binding.
Explanation:

DFHWS2LS has detected that the WSDL binding does not indicate the use of SOAP. DFHWS2LS only supports Web services that use SOAP.

System action:

The Web services assistant continues processing.

User response:

Either redesign your WSDL to remove the content that is not supported by DFHWS2LS or consider implementing this Web service without the use of the Web services assistants. If the Web services assistant cannot be used then the following options are available:

  1. If you are implementing a Web service provider application then you should consider writing your own XML capable terminal node in place of the SOAP node used with most PIPELINEs.
  2. If you are implementing a Web service requester application then you should consider writing an XML capable application that uses the DFHPIRT channel linkable PIPELINE interface.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9603
Multiple WSDL service elements exist for a single binding element. Only one is supported.
Explanation:

DFHWS2LS has encountered a problem processing the WSDL document. The WSDL specifies more than one WSDL service element for use with the specified binding element. DFHWS2LS only supports at most one service element per binding.

System action:

The Web services assistant continues processing.

User response:

Remove all but one of the service elements for the binding.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9604
File file does not contain valid WSDL.
Explanation:

The WSDL document does not appear to contain WSDL. It may have been corrupted in transit or it may not contain XML.

System action:

The Web services assistant continues processing.

User response:

Ensure that the value of the WSDL input parameter identifies the correct file. Ensure that the WSDL document has been stored in the correct code page.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9605
The value of the XML encoding tag must match that of the underlying file system. For example, the value UTF-8 may be appropriate.
Explanation:

The XML encoding pseudo-attribute in the prolog of the WSDL document appears to be incorrect. The value of this attribute must match the encoding in which the WSDL document is stored in the file system.

System action:

The Web services assistant continues processing.

User response:

Either correct or remove the encoding attribute. It is likely that the correct value should be UTF-8.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9606
The value of the XML encoding tag must match that of the underlying file system. For example, the value EBCDIC-CP-US may be appropriate.
Explanation:

The XML encoding pseudo-attribute in the prolog of the WSDL document appears to be incorrect. The value of this attribute must match the encoding in which the WSDL document is stored in the file system.

System action:

The Web services assistant continues processing.

User response:

Either correct or remove the encoding attribute. It is likely that the correct value should be EBCDIC-CP-US.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9607
An unexpected error occurred whilst processing WSDL operation operation The problem is: value
Explanation:

DFHWS2LS has encountered a problem whilst processing the WSDL document. An exception has been caught which includes a message the details of which are available in value

System action:

The Web services assistant continues processing.

User response:

Correct the identified problem.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9608
WARNINGS have been generated processing file file
Explanation:

The Web services assistant has completed and has issued one or more warning messages.

System action:

The Web services assistant ends with return code 4.

User response:

Read the previously issued warning messages and decide on what if any actions must be taken.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9609
Parameter parameter has value value
Explanation:

The value of parameter parameter is value

System action:

The Web services assistant continues processing.

User response:

You may safely ignore this message.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9610
Platform platform is not a supported platform for this API.
Explanation:

The Web services assistant has detected that it is executing on a platform that is not currently supported. If you experience any problems whilst executing the Web services assistant on this platform you may receive a reduced level of support from IBM.

System action:

The Web services assistant continues processing.

User response:

Consider hosting the Web services assistant on a platform that is supported such as z/OS.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9611
All content after the first ';' for line line is ignored.
Explanation:

DFHLS2WS has spotted a line termination character part way through what appears to be a line of PL/I code. DFHLS2WS does not process the remainder of the line.

System action:

The Web services assistant continues processing.

User response:

Consider whether DFHLS2WS is correct in ignoring the end of the line. If there is significant data still to be processed then edit the input file in order to supply the data in a format that DFHLS2WS can understand.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9612
Provider mode Web services with more than one operation must specify 'PGMINT=CHANNEL'.
Explanation:

DFHWS2LS has determined that there is more than one operation associated with the binding in the WSDL document. If there is more than one operation supported by a provider mode WEBSERVICE then the CICS application which implements the Web service will have to determine the operation invoked using the contents of the DFHWS-OPERATION container. This container is only available if the CICS application is linked to with a channel rather than a COMMAREA.

System action:

The Web services assistant continues processing.

User response:

Consider changing the PGMINT input parameter to CHANNEL rather than COMMAREA.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9613
Mapping level level is not recognized.
Explanation:

An invalid value has been specified for the MAPPING-LEVEL parameter.

System action:

The Web services assistant continues processing.

User response:

Correct the value of the MAPPING-LEVEL parameter.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9614
Mapping level old has been requested. The most current mapping level available is new
Explanation:

An old mapping level has been requested. More recent mapping levels have enhanced support for WSDL and language structures that may not be available at the mapping level requested.

System action:

The Web services assistant continues processing.

User response:

Consider switching to the most current mapping level.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9615
The version of Java in use is current The minimum version of Java required is required
Explanation:

The Web services assistants require a more recent version of Java in order to execute.

System action:

The Web services assistant continues processing.

User response:

Ensure you have the correct minimum version of Java installed. The 'JAVADIR' option of the JCL procedure used to launch the Web services assistant may be used to specify a version of Java other than the default.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHWS2LS, DFHLS2WS

End of change
Start of change
DFHPI9616
National characters in COBOL are assumed to be DBCS characters: line
Explanation:

A language structure processed by DFHLS2WS contains fields which are declared to contain National characters. National characters are only partially supported. DFHLS2WS assumes that all fields defined to contain National values do so using DBCS.

System action:

The Web services assistant continues processing.

User response:

Consider whether you intend these fields to contain pure DBCS data. If this is expected then you can safely ignore this message. If you intend the field to contain UTF-16 data then you cannot make use of the Web services assistants to expose your application as a Web service. You should instead consider writing your own XML capable SOAP 'apphandler'.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS

End of change
Start of change
DFHPI9656E
The WSDL file does not contain any binding elements. There must be at least one WSDL binding.
Explanation:

DFHWS2LS has processed a WSDL document that does not include any binding elements. DFHWS2LS requires that there is at least one SOAP binding in the WSDL document.

System action:

The Web services assistant continues processing.

User response:

Alter the WSDL document so that it does include a WSDL binding.

Modules:

DFHWS2LS

End of change
Start of change
DFHPI9664 E
The value specified by parameter parameter is invalid. Consult the log file generated by the CICS Web services assistant for more information.
Explanation:

A value has been specified for one of the parameters in DFHLS2WS or DFHWS2LS that is invalid.

System action:

The Web services assistant continues processing.

User response:

Correct the parameter value passed to the CICS Web services assistant before retrying. More information on the permissible values for this parameter can be found in the log file of the CICS Web services assistant and the CICS Web services manual.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHLS2WS, DFHWS2LS

End of change [[ Contents Previous Page | Next Page Index ]]