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).
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.
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.
Console
DFHPIDM, DFHPIWT
XMEOUT Parameters:
applid,
aaa/bbbb,
X'
offset',
modname
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.
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.
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.
Console
DFHPIDM, DFHPIST, DFHPIWT
XMEOUT Parameters:
applid,
X'
code',
modname
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.
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.
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.
Console
DFHPIRM
XMEOUT Parameters: applid, X'offset', modname
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.
The CPIH transaction has not been started.
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.
CPIO
DFHPIDSH
XMEOUT Parameters:
date,
time,
applid
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.
The transaction is abended with abend code APIJ.
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.
CPIO
DFHPILSQ
XMEOUT Parameters:
date,
time,
applid,
tranid,
function,
reason_code
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.
The inbound message is placed on the Dead Letter Queue and a report message is sent to the ReplyTo queue.
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.
CPIO
DFHPILSQ
XMEOUT Parameters:
date,
time,
applid,
tranid,
hostname,
pathname
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.
The inbound message is placed on the Dead Letter Queue and a report message is sent to the ReplyTo queue.
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.
CPIO
DFHPILSQ
XMEOUT Parameters:
date,
time,
applid,
tranid,
urimapname,
hostname,
pathname
A Websphere MQ function call issued by the pipeline MQ transport mechanism was unsuccessful and has set a non-zero reason code.
The pipeline MQ transport mechanism returns an exception response to the pipeline manager which performs further error processing.
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.
CPIO
DFHPITQ1
XMEOUT Parameters:
date,
time,
applid,
tranid,
function,
reason_code
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.
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.
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.
CPIO
DFHPITQ1
XMEOUT Parameters:date, time,applid, tranid .
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.
CICS has kept the information necessary to retry the failing provider pipeline in the named process. CICS takes no further action for the process.
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.
CPIO
DFHPIDSQ
XMEOUT Parameters:date, time,applid
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.
CICS cancels the process that completed with status ABENDED. All the data associated with the process is removed.
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.
CPIO
DFHPIDSQ
XMEOUT Parameters:date, time,applid
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.
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.
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.
Console
DFHPILSQ
XMEOUT Parameters:applid
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.
An exception response will be returned to the exec interface module which requested the INVOKE WEBSERVICE.
None.
CPIO
DFHPIIW
XMEOUT Parameters:
date,
time,
applid,
WebService,
container_name
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.
The link is abandoned and the INVOKE WEBSERVICE command returns appropriate EIBRESP and EIBRESP2 codes to the application program. Error processing will continue.
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.
CPIO
DFHPIIW
XMEOUT Parameters:
date,
time,
applid,
program_name,
WebService,
{1=The
program abended.,
2=The program was not defined.,
3=The program was not enabled.,
4=The program
was not loadable.,
5=No further details are available.}
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.
The request is not sent. Error processing will continue.
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.
CPIO
DFHPITH
XMEOUT Parameters:
date,
time,
applid,
tranid,
{1=the request was using an
invalid host codepage,
2=there was a socket error,
3=the URL was invalid,
4=the connection
was closed,
5=a socket request timed out}
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.
The response is not sent. Error processing will continue.
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.
CPIO
DFHPITH
XMEOUT Parameters:
date,
time,
applid,
tranid,
{1=the codepage was not found,
2=there was a socket error,
3=the connection
was closed,
4=the client codepage was invalid}
The CICS pipeline HTTP transport mechanism was unable to successfully handle the outbound request because the host hostname from the URI is unknown.
The request is not sent. Error processing will continue.
Ensure that the URI specifies a host which is known and available.
CPIO
DFHPITH
XMEOUT Parameters:
date,
time,
applid,
tranid,
hostname
The CICS pipeline HTTP transport mechanism did not successfully receive a response to the outbound request because the socket receive was timed out.
The request is abandoned. Error processing will continue.
Investigate why the remote server failed to respond in a timely manner. Consider changing the DTIMOUT value for the transaction that encountered this error.
CPIO
DFHPITH
XMEOUT Parameters: date, time,applid, tranid, {1=the socket receive was timed out}
The CICS Pipeline Manager, DFHPIPM, was unable to link to the given program, or the linked program abended.
The link is abandoned. Error processing will continue.
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.
CPIO
DFHPIPM
XMEOUT Parameters:
date,
time,
applid,
tranid,
program_name,
{1=The
program abended.,
2=The program was not defined.,
3=The program was not enabled.,
4=The program
was not loadable.,
5=No further details are available.},
pipeline
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.
In the requester case the transaction is abended with abend code APIB. In the provider case the transaction is abended with abend code API1.
Correct the problem identified in the message.
CPIO
DFHPIPM
XMEOUT Parameters:
date,
time,
applid,
tranid,
{1=The pipeline was not found.,
2=The pipeline is disabled.,
3=The pipeline
was of the wrong type.},
pipeline
The CICS Pipeline Manager DFHPIPM was unable to receive a request from the underlying transport. This is due to a error in that transport.
The transaction is abended with abend code API2.
Check the previous messages issued by the transport to identify the cause of the problem.
CPIO
DFHPIPM
XMEOUT Parameters:
date,
time,
applid,
tranid,
transport,
pipeline
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.
The request is abandoned. Error processing continues.
Check the previous messages issued by the transport to identify the cause of the problem.
CPIO
DFHPIPM
XMEOUT Parameters:
date,
time,
applid,
tranid,
transport,
pipeline
The CICS Pipeline Manager DFHPIPM failed to communicate with a remote server due to an error in the underlying transport.
The request is abandoned. Error processing continues.
Check the previous messages issued by the transport to identify the cause of the problem.
CPIO
DFHPIPM
XMEOUT Parameters:
date,
time,
applid,
tranid,
transport,
pipeline
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.
An exception trace entry is written. Error processing continues.
Correct either the application logic or the configuration file so that the URI is provided.
CPIO
DFHPIPM
XMEOUT Parameters:
date,
time,
applid,
tranid,
pipeline
The CICS Pipeline Manager DFHPIPM failed to communicate with a remote server as a URI with an invalid scheme was provided. Before CICS can make and a request to a remote server it must be provided with a URI identifying that server.
An exception trace entry is written. Error processing continues.
Correct either the application logic or the configuration file so that a URI with a supported scheme is provided.
CPIO
DFHPIPM
XMEOUT Parameters:
date,
time,
applid,
tranid,
uri,
pipeline
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.
The request will be treated as failed and error processing will continue.
Check the message logs for the region in which the application task was running to determine the detailed cause of the problem.
CPIO
DFHPIPM
XMEOUT Parameters:
date,
time,
applid,
tranid,
{1=The request timed out.,
2=The application task abended.,
3=The connection
to the application task was closed.},
pipeline
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.
The SOAP Handler attempting to create this request stream will create a SOAP server fault to return to the client. Error processing continues.
Determine the remote system name from the tranid definition. Ensure that IRC is open and the IRC connection named is in service.
CPIO
DFHPIPM
XMEOUT Parameters:
date,
time,
applid,
tranid,
userid
The CICS pipeline manager attempted to create or join a request stream for transaction tranid which is not installed.
The SOAP Handler that attempted to create the request stream will create a SOAP server fault to return to the client. Error processing continues.
Add an RDO definition for tranid with a program name of DFHPIAP.
CPIO
DFHPIPM
XMEOUT Parameters:
date,
time,
applid,
tranid
The CICS pipeline manager attempted to create or join a request stream for transaction tranid. CICS encountered a severe error.
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.
None
CPIO
DFHPIPM
XMEOUT Parameters:
date,
time,
applid,
tranid,
userid
The CICS soap handler DFHPISN was unable to convert the container to UTF-8 as the container does not have a datatype of CHAR.
The soap handler is unable to process the input and returns a SOAP fault to the client/sender.
Ensure that the DFHREQUEST and DFHWS-BODY containers use the DATATYPE(CHAR) option on the EXEC CICS PUT CONTAINER call.
CPIO
DFHPISN
XMEOUT Parameters:
date,
time,
applid
The CICS soap handler DFHPISN has detected that the data in container DFHWS-BODY passed to it does not begin with a '<' character.
The soap handler attempts to continue processing using the contents of the DFHWS-BODY container.
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.
CPIO
DFHPISN
XMEOUT Parameters:
date,
time,
applid
The CICS SOAP handler DFHPISN has failed to parse a message.
The SOAP handler stops processing the SOAP message and creates a SOAP fault to return to the requester.
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,
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.
No pipeline is installed, but CICS continues normally.
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.
CPIO
DFHPIPL
XMEOUT Parameters:
date,
time,
applid,
userid,
pipeline
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.
CICS continues normally.
None.
CPIO
DFHPIPL
XMEOUT Parameters:
date,
time,
applid,
userid,
pipeline
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.
The pipeline is set to a DISABLED state and normal processing continues.
Correct the configuration file. Ensure that the corrected file has been validated before discarding the pipeline (pipeline) and then re-installing it.
CPIO
DFHPIPL
XMEOUT Parameters:
date,
time,
applid,
userid,
pipeline,
filename,
X'
offset',
elementname
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.
The system continues normally.
None.
CPIO
DFHPIPL
XMEOUT Parameters:
date,
time,
applid,
userid,
pipeline
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.
CICS continues normally.
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).
CPIO
DFHPIPL
XMEOUT Parameters:
date,
time,
applid,
userid,
pipeline,
num_files,
num_ok,
num_failed
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.
The pipeline is disabled and CICS continues normally.
See the z/OS UNIX System Services Messages and Codes manual for the specified response and reason codes.
CPIO
DFHPIPL
XMEOUT Parameters:
date,
time,
applid,
userid,
pipeline,
derived-shelf,
X'
uss-response',
X'
uss-reason'
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.
The pipeline is set to a DISABLED state and CICS continues normally.
Correct the configuration file. Pipeline pipeline_name must be discarded and then re-installed.
CPIO
DFHPIPL
XMEOUT Parameters:
date,
time,
applid,
userid,
pipeline
An XML element was discovered that had a namespace prefix specified. This is not supported.
The pipeline is set to a DISABLED state and CICS continues normally.
Correct the configuration file. Pipeline pipeline_name must be discarded and then re-installed.
CPIO
DFHPIPL
XMEOUT Parameters:
date,
time,
applid,
userid,
pipeline
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.
The pipeline is set to a DISABLED state.
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.
CPIO
DFHPIPL
XMEOUT Parameters:
date,
time,
applid,
userid,
pipeline
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.
The pipeline is set to a DISABLED state.
Determine the reason for this failure and correct it, before discarding and then re-installing the pipeline.
CPIO
DFHPIPL
XMEOUT Parameters:
date,
time,
applid,
userid,
pipeline
The PIPELINE was successfully discarded and is no longer available for use.
Processing continues.
None.
CPIO
DFHPIPL
XMEOUT Parameters:
date,
time,
applid,
userid,
pipeline
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.
The pipeline is set to a DISABLED state and CICS continues normally.
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.
CPIO
DFHPIPL
XMEOUT Parameters:
date,
time,
applid,
userid,
pipeline,
X'errcode',
X'
offset',
hexdata
A NOTAUTH condition was raised when an attempt to read the configuration file (CONFIGFILE) for this pipeline was made.
The pipeline is disabled and CICS continues normally.
Correct the access for the userid or ensure the correct userid is used for the installation of this pipeline.
CPIO
DFHPIPL
XMEOUT Parameters:
date,
time,
applid,
userid,
pipeline
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.
Processing continues.
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.
CPIO
DFHPIPL
XMEOUT Parameters:
date,
time,
applid,
userid,
pipelinename
The HFS directory specified in the WSDIR parameter is invalid.
The pipeline is NOT installed. CICS continues normally.
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.
CPIO
DFHPIPL
XMEOUT Parameters:
date,
time,
applid,
userid,
pipeline
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.
CICS continues normally.
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).
CPIO
DFHPIPL
XMEOUT Parameters:
date,
time,
applid,
userid,
pipeline,
num_files,
num_ok,
num_nun,
num_failed
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.
The webservice is NOT created. CICS continues normally.
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.
CPIO
DFHPIPL
XMEOUT Parameters:
date,
time,
applid,
userid,
pipeline
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.
The pipeline is set to a DISABLED state and normal processing continues.
Correct the configuration file. Ensure that the corrected file has been validated before discarding the pipeline (pipeline) and then re-installing it.
CPIO
DFHPIPL
XMEOUT Parameters:
date,
time,
applid,
userid,
pipeline,
filename,
X'
offset',
element_found,
element_expected
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.
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.
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.
Console and Transient Data Queue CPIO
DFHPIRS
XMEOUT Parameters: date, time,applid, X'uowid'
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.
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.
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.
Console and Transient Data Queue CPIO
XMEOUT Parameters: date, time,applid, X'uowid
'
During processing of an atomic transaction the remote WS-AT coordinating task has requested that CICS rolls back the specified unit of work.
The specified unit of work will be rolled back.
None.
CPIO
DFHPIRS
XMEOUT Parameters: date, time,applid, X'uowid
'
A CICS transaction waiting for a Prepare message from a remote WS-AT coordinator has timed out.
The specified unit of work will be rolled back.
None.
CPIO
DFHPIPM
XMEOUT Parameters: date, time,applid, X'uowid
'
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.
The transaction abends.
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.
CPIO
DFHPIAT
XMEOUT Parameters:
date,
time,
applid,
userid,
X'
errcode',
X'offset
'
A CICS transaction waiting for a Prepare message from a remote WS-AT coordinator has timed out.
The specified unit of work will be rolled back.
None.
CPIO
DFHPIPM
XMEOUT Parameters: date, time,applid, X'uowid
'
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.
The transaction abends.
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.
CPIO
DFHPIAT
XMEOUT Parameters:
date,
time,
applid,
userid,
X'
errcode',
X'offset
'
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.
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.
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.
CPIO
DFHWSATH
XMEOUT Parameters: date, time,applid, TRAN
A new WSBIND file has been discovered on HFS during a scan. A corresponding CICS WEBSERVICE resource is being automatically created to represent it.
None.
None.
CPIO
DFHPISC
XMEOUT Parameters:
date,
time,
applid,
userid,
WebService,
Pipeline
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.
If there is 'inflight' activity outstanding for this WEBSERVICE then the update will complete after that workload has ended.
None.
CPIO
DFHPISC
XMEOUT Parameters:
date,
time,
applid,
userid,
WebService,
Pipeline
A new URIMAP resource is being installed during a scan of a PIPELINE.
None.
None.
CPIO
DFHPISC
XMEOUT Parameters:
date,
time,
applid,
userid,
UriMap,
Pipeline,
WebService
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.
None.
None.
CPIO
DFHPISC
XMEOUT Parameters:
date,
time,
applid,
userid,
UriMap,
WebService,
Pipeline,
Uri
A WEBSERVICE has been created and is now in the INITING state. It is not available for use until it has reached INSERVICE state.
Processing continues. The WEBSERVICE will complete installation shortly.
None.
CPIO
DFHPIWR
XMEOUT Parameters:
date,
time,
applid,
userid,
WebService,
Pipeline
WEBSERVICE WebService was not created. This error may be caused if the specified PIPELINE is not installed.
The WEBSERVICE is not created.
Ensure that the specified PIPELINE resource is installed and try again.
CPIO
DFHPIWR
XMEOUT Parameters:
date,
time,
applid,
userid,
WebService,
Pipeline,
{1=there is insuffient storage,
2=there
is a directory domain error,
3=the specified PIPELINE
is not installed,
4=a lock cannot be obtained,
5=there is a duplicate resource error}
The WEBSERVICE was successfully discarded and is no longer available for use.
Processing continues.
None.
CPIO
DFHPIWR
XMEOUT Parameters:
date,
time,
applid,
userid,
WebService
A discard of a WEBSERVICE has been started but cannot complete at this time as 'inflight' work is outstanding.
The WEBSERVICE discard will complete when the 'inflight' activity has ended.
None.
CPIO
DFHPIWR
XMEOUT Parameters:
date,
time,
applid,
userid,
WebService
The WEBSERVICE failed to complete initialization.
The WEBSERVICE has been put into the UNUSABLE state.
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.
CPIO
DFHPIWR
XMEOUT Parameters:
date,
time,
applid,
userid,
WebService,
{1=the
WSBind file was not found,
2=CICS is not authorized
to read the WSBind file,
3=there is insufficient
storage to load the WSBind file,
4=the HFS read for
the WSBind file failed,
5=writing the WSBind file
to the shelf failed,
6=the PIPELINE is incompatible
with this WEBSERVICE,
7=the CPIR resolution transaction
could not be attached,
8=the direction of the PIPELINE
can't be determined,
9=the WSBind file is corrupt,
10=the WSBind file has an invalid version number,
11=the WSBind file has an out of date version number,
12=the WSBind file product number was not recognised}
The WEBSERVICE has completed initialization and is ready for use.
Processing continues.
None.
CPIO
DFHPIWR
XMEOUT Parameters:
date,
time,
applid,
userid,
WebService
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.
The WEBSERVICE is not CREATED, the PIPELINE SCAN processing continues.
Rename the wsbind file and retry the operation.
CPIO
DFHPISC
XMEOUT Parameters:
date,
time,
applid,
userid,
WebService,
Pipeline,
Pipeline
The pipeline manager encountered a problem attempting to open file DFHPIDIR. This might be due to one of the following:
Processing is aborted. A SOAP fault is returned to the client.
Examine the trace to determine why the pipeline manager failed.
CPIO
XMEOUT Parameters:
date,
time,
applid,
tranid,
{1=the file was not found,
2=the file
key length was too small,
3=the file record size
was too small,
4=the file is full,
5=the
file control record is full,
6=file recovery mode
was not backout,
7=there was an internal error,
8=file failed to open or connect}
The Pipeline Manager encountered a problem whilst attempting to process a message. This can be due to one of the following;
None.
Examine the trace to determine why the Pipeline Manager failed.
CPIO
DFHPIPM
XMEOUT Parameters:
date,
time,
applid,
tranid,
pipeline,
{1=PIPELINE not found,
2=PIPELINE not active,
3=PIPELINE mode mismatch,
4=unhandled node failure,
5=context switch
failed,
6=request stream creation failure,
7=request stream transport error,
8=target
program unavailable,
9=channel error,
10=channel
not found,
11=URI not found,
12=invalid
URI,
13=authorization failure,
14=program
abend,
15=unidentified problem,
16=timeout
occured,
17=no request message,
18=there
was a problem with file PIDIR,
19=attempt to register
a WS-AT context twice}
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.
The program abends with an APIC abend.
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.
CPIO
DFHPIRT
XMEOUT Parameters:
date,
time,
applid,
X'
code
'
The Outbound Router program, DFHPIRT, was unable to successfully start the Pipeline Manager.
The program abends with an APIB abend.
Examine the trace to determine why the Pipeline Manager failed.
CPIO
DFHPIRT
XMEOUT Parameters:
date,
time,
applid
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.
None.
None.
CPIO
DFHPITL, DFHPIIW
XMEOUT Parameters:
date,
time,
applid,
{1=request,
2=response},
webservicename,
operationname,
message
Validation was requested for a particular operation, operationname, for webservice webservicename. The validation has been performed successfully.
None.
None.
CPIO
DFHPITL, DFHPIIW
XMEOUT Parameters:
date,
time,
applid,
{1=request,
2=response},
webservicename,
operationname
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.
Validation is not attempted. The application program is invoked as though validation had not been requested.
None.
CPIO
DFHPITL
XMEOUT Parameters:
date,
time,
applid
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.
Validation is not attempted. Processing continues. The application program is invoked as though validation had not been requested.
Ensure that the CSD in use has the definition for DFHPIVAL included.
CPIO
DFHPITL, DFHPIIW
XMEOUT Parameters:
date,
time,
applid
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.
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.
Ensure that the WEBSERVICE definition refers to the correct WSBIND file and that the vendor program progname required is available to CICS.
CPIO
DFHPITL, DFHPIIW
XMEOUT Parameters:
date,
time,
applid,
progname,
modname
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.
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.
Ensure that the WEBSERVICE definition for WebService refers to the correct WSBIND file and that the file has been properly produced.
CPIO
DFHPITL, DFHPIIW
XMEOUT Parameters:
date,
time,
applid,
WebService,
modname
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:
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.
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.
CPIO
DFHPICC
XMEOUT Parameters:
date,
time,
applid,
1=XML_FOMAT_ERROR,
2=UNEXPECTED_CONTENT,
3=HEADER_FORMAT_ERROR,
4=UNDEFINED_ELEMENT,
5=UNDEFINED_NAME_SPACE,
6=ARRAY_OVERFLOW,
7=NAME_TOO_LONG,
8=PREFIX_TOO_LONG,
9=NAME_SPACE_TOO_LONG,
error_qualifier
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:
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.
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.
CPIO
DFHPIII
XMEOUT Parameters:
date,
time,
applid,
1=ARRAY_CONTAINER_TOO_SMALL,
2=INPUT_STRUCTURE_TOO_SMALL,
3=INPUT_ARRAY_TOO_LARGE,
4=INPUT_ARRAY_TOO_SMALL,
5=CONTAINER_NOT_FOUND,
6=CONTAINER_NOT_BIT,
error_qualifier
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:
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.
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.
CPIO
DFHPICC
XMEOUT Parameters:
date,
time,
applid,
99=UNKNOWN_CONVERSION,
1=INPUT_TOO_LONG,
2=OUTPUT_OVERFLOW,
3=NEGATIVE_UNSIGNED,
4=NO_FRACTION_DIGITS,
5=FRACTION_TOO_LONG,
6=INVALID_CHARACTER,
7=ODD_HEX_DIGITS,
11=INVALID_BASE64,
12=NOT_PURE_DBCS,
14=INVALID_FIELD_SIZE,
15=EXPONENT_OVERFLOW,
16=EXPONENT_UNDERFLOW,
fieldname
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:
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.
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.
CPIO
DFHPIII
XMEOUT Parameters:
date,
time,
applid,
99=UNKNOWN_CONVERSION,
3=NEGATIVE_UNSIGNED,
6=INVALID_CHARACTER,
8=INVALID_PACKED_DEC,
9=INVALID_ZONED_DEC,
10=INCOMPLETE_DBCS,
13=ODD_BYTES_DBCS,
14=INVALID_FIELD_SIZE,
15=EXPONENT_OVERFLOW,
16=EXPONENT_UNDERFLOW,
fieldname
The messages for the Web services assistants cannot be located.
The Web services assistant continues processing but no other messages will be issued.
Contact your IBM support representative for further assistance.
SYSPRINT
DFHWS2LS, DFHLS2WS
A message number value is missing and cannot be issued.
The Web services assistant continues processing.
Contact your IBM support representative for further assistance.
SYSPRINT
DFHWS2LS, DFHLS2WS
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.
The Web services assistant continues processing.
Edit the WSDL document and reduce the length of the operation name. Resubmit the DFHWS2LS job to reprocess the WSDL.
SYSPRINT
DFHWS2LS
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.
The Web services assistant continues processing.
Edit the WSDL document and reduce the length of the part name. Resubmit the DFHWS2LS job to reprocess the WSDL.
SYSPRINT
DFHWS2LS
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.
The Web services assistant continues processing.
Correct the WSDL document and then resubmit the DFHWS2LS job to reprocess the WSDL.
SYSPRINT
DFHWS2LS
DFHWS2LS only supports simple primitive XML data types. Type type is either a list or a union data type.
The Web services assistant continues processing.
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:
SYSPRINT
DFHWS2LS
XML data type base_type is derived from XML data type super_type The super type is not supported by DFHWS2LS.
The Web services assistant continues processing.
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:
SYSPRINT
DFHWS2LS
A XML schema referenced within WSDL document contains an 'any' tag. The 'any' tag is not supported by DFHWS2LS.
The Web services assistant continues processing.
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:
SYSPRINT
DFHWS2LS
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
The Web services assistant continues processing.
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:
SYSPRINT
DFHWS2LS
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
The Web services assistant continues processing.
Correct the XML schema and then resubmit the DFHWS2LS job to reprocess the WSDL.
SYSPRINT
DFHWS2LS
There is an error in an XML schema referenced from the WSDL document. An XML particle value has been found with unrecognized content.
The Web services assistant continues processing.
Correct the XML schema and then resubmit the DFHWS2LS job to reprocess the WSDL.
SYSPRINT
DFHWS2LS
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
The Web services assistant continues processing.
Correct the XML schema or the WSDL and then resubmit the DFHWS2LS job to reprocess the WSDL.
SYSPRINT
DFHWS2LS
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
The Web services assistant continues processing.
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:
SYSPRINT
DFHWS2LS
There is an error in an XML schema referenced from the WSDL document. XML schema element element does not reference an XML type.
The Web services assistant continues processing.
Correct the XML schema and then resubmit the DFHWS2LS job to reprocess the WSDL.
SYSPRINT
DFHWS2LS
An XML schema referenced within the WSDL document contains an XML type that is not supported by DFHWS2LS. The unsupported XML type is type
The Web services assistant continues processing.
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:
SYSPRINT
DFHWS2LS, DFHLS2WS
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.
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.
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:
SYSPRINT
DFHWS2LS
There is an error in an XML schema referenced from the WSDL document. An XML type value has been found with unrecognized content.
The Web services assistant continues processing.
Correct the XML schema and then resubmit the DFHWS2LS job to re-process the WSDL.
SYSPRINT
DFHWS2LS
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
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.
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:
SYSPRINT
DFHWS2LS
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
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.
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:
SYSPRINT
DFHWS2LS
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
The Web services assistant continues processing.
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:
SYSPRINT
DFHWS2LS
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.
The Web services assistant continues processing.
Correct the XML schema or the WSDL and then resubmit the DFHWS2LS job to re-process the WSDL.
SYSPRINT
DFHWS2LS
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
The Web services assistant continues processing.
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.
SYSPRINT
DFHWS2LS
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
The Web services assistant continues processing.
Correct the XML schema or the WSDL and then resubmit the DFHWS2LS job to re-process the WSDL.
SYSPRINT
DFHWS2LS
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.
The Web services assistant continues processing.
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:
SYSPRINT
DFHWS2LS
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.
The Web services assistant continues processing.
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.
SYSPRINT
DFHLS2WS
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.
The Web services assistant continues processing.
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.
SYSPRINT
DFHLS2WS
An internal processing error has occurred. DFHLS2WS has not been able to correctly parse a language structure.
The Web services assistant continues processing.
Contact your IBM support representative for further assistance.
SYSPRINT
DFHLS2WS
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.
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.
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:
SYSPRINT
DFHWS2LS
The Web services assistant has caught an unexpected exception.
The Web services assistant continues processing.
Contact your IBM support representative for further assistance.
SYSPRINT
DFHWS2LS, DFHLS2WS
The value of the HTTPPROXY parameter is invalid.
The Web services assistant continues processing.
Correct or remove the HTTPPROXY parameter.
SYSPRINT
DFHWS2LS
The Web services assistant cannot continue as one or more errors have been detected in the input parameters.
The Web services assistant fails with a return code of 8.
Correct the errors in the input parameters details of which can be found in the previous messages issued.
SYSPRINT
DFHWS2LS, DFHLS2WS
A required parameter is missing from the input parameters. The missing parameter is parameter
The Web services assistant continues processing.
Provide a value for the missing parameter.
SYSPRINT
DFHWS2LS, DFHLS2WS
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
The Web services assistant continues processing.
Remove the unexpected parameter.
SYSPRINT
DFHWS2LS, DFHLS2WS
An invalid value has been specified for the LANG parameter.
The Web services assistant continues processing.
Correct the value of the LANG parameter.
SYSPRINT
DFHWS2LS, DFHLS2WS
The value of parameter parameter is too long.
The Web services assistant continues processing.
Change the value to be no longer than value characters long.
SYSPRINT
DFHWS2LS, DFHLS2WS
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.
The Web services assistant continues processing.
Consider removing the unexpected parameter.
SYSPRINT
DFHWS2LS, DFHLS2WS
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' .
The Web services assistant continues processing.
Correct the value of the URI parameter.
SYSPRINT
DFHWS2LS, DFHLS2WS
One or more invalid characters have been found in parameter parameter
The Web services assistant continues processing.
Correct the value of the parameter.
SYSPRINT
DFHWS2LS, DFHLS2WS
An invalid value has been specified for the PGMINT parameter.
The Web services assistant continues processing.
Correct the value of the PGMINT parameter.
SYSPRINT
DFHWS2LS, DFHLS2WS
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.
The Web services assistant continues processing.
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.
SYSPRINT
DFHWS2LS, DFHLS2WS
The CONTID input parameter has been specified but is ignored as the program interface has been defined to be a COMMAREA.
The Web services assistant continues processing.
Consider either removing the CONTID parameter or changing the PGMINT to CHANNEL.
SYSPRINT
DFHWS2LS, DFHLS2WS
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.
The Web services assistant continues processing.
Consider adding '.wsbind' to the end of your WSBIND parameter value.
SYSPRINT
DFHWS2LS, DFHLS2WS
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'.
The Web services assistant continues processing.
Consider changing the extension of the WSBIND parameter to '.wsbind'.
SYSPRINT
DFHWS2LS, DFHLS2WS
The PDS library specified in the PDSLIB input parameter cannot be found.
The Web services assistant continues processing.
Correct the PDSLIB input parameter.
SYSPRINT
DFHWS2LS, DFHLS2WS
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.
The Web services assistant continues processing.
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.
SYSPRINT
DFHWS2LS, DFHLS2WS
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.
The Web services assistant continues processing.
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.
SYSPRINT
DFHWS2LS, DFHLS2WS
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.
The Web services assistant continues processing.
Consider changing the PDSLIB to a fixed record data set with a logical record length of 80 characters.
SYSPRINT
DFHWS2LS, DFHLS2WS
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.
The Web services assistant continues processing.
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.
SYSPRINT
DFHWS2LS, DFHLS2WS
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.
The Web services assistant continues processing.
Change one of the REQMEM and RESPMEM input parameters in order to make them unique.
SYSPRINT
DFHWS2LS
The location at which the language structures are to be written to or read from is not a fixed block PDS member.
The Web services assistant continues processing.
Change the location of the PDSLIB input parameter to indicate a FB data set.
SYSPRINT
DFHWS2LS, DFHLS2WS
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.
The Web services assistant continues processing.
Correct the problem.
SYSPRINT
DFHLS2WS
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.
The Web services assistant continues processing.
Correct the identified problem.
SYSPRINT
DFHWS2LS, DFHLS2WS
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.
The Web services assistant continues processing.
Correct the problem.
SYSPRINT
DFHWS2LS
Directory directory does not exist. Therefore the Web services assistant is unable to create an output file that should be written to that directory.
The Web services assistant continues processing.
Either create the directory or change the input parameters to indicate a different output location.
SYSPRINT
DFHWS2LS, DFHLS2WS
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.
The Web services assistant continues processing.
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.
SYSPRINT
DFHWS2LS, DFHLS2WS
File file exists but the userid under which the Web services assistant is executing does not have write permission to change it.
The Web services assistant continues processing.
Either change the permissions for the file or change the input parameters to indicate a different output location.
SYSPRINT
DFHWS2LS, DFHLS2WS
File file either does not exist the userid under which the Web services assistant is executing does not have permission to read it.
The Web services assistant continues processing.
Either change the permissions for the file or correct the input parameters to indicate a different input file.
SYSPRINT
DFHWS2LS, DFHLS2WS
The input parameters extend beyond character 72. The problematic line identified is line
The Web services assistant continues processing.
Change the indicated line to use less than 72 characters of data.
SYSPRINT
DFHWS2LS, DFHLS2WS
An unrecognized parameter has been found amongst the input parameters.
The Web services assistant continues processing.
Consider removing the named parameter.
SYSPRINT
DFHWS2LS, DFHLS2WS
The STRUCTURE input parameter is not well formed. It may only contain bracket characters at the start and end of the value.
The Web services assistant continues processing.
Correct the value of the STRUCTURE input parameter.
SYSPRINT
DFHWS2LS, DFHLS2WS
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).
The Web services assistant continues processing.
Correct the value of the STRUCTURE input parameter.
SYSPRINT
DFHWS2LS, DFHLS2WS
An invalid character has been found in parameter character
The Web services assistant continues processing.
Correct the value of the named input parameter.
SYSPRINT
DFHWS2LS, DFHLS2WS
No explanation is available for this message.
The Web services assistant continues processing.
Note: This message cannot be changed with the message editing utility.
SYSPRINT
DFHWS2LS, DFHLS2WS
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.
The Web services assistant continues processing.
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:
SYSPRINT
DFHWS2LS
DFHLS2WS is unable to locate a required user defined type with the C or C++ header file.
The Web services assistant continues processing.
Change the C header file to include the required user defined type.
SYSPRINT
DFHLS2WS
DFHLS2WS has found a compiler directive within the C or C++ header file. Compiler directives are not supported.
The Web services assistant continues processing.
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.
SYSPRINT
DFHLS2WS
DFHLS2WS is unable to locate a required structure which is referenced in the C or C++ header file.
The Web services assistant continues processing.
Change the C header file to include the required structure.
SYSPRINT
DFHLS2WS
An invalid character has been found in the C or C++ header file.
The Web services assistant continues processing.
Correct the header file.
SYSPRINT
DFHLS2WS
DFHLS2WS has detected a keyword keyword that is not currently supported.
The Web services assistant continues processing.
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.
SYSPRINT
DFHLS2WS
DFHLS2WS has detected an unsupported data type in a C or C++ header file.
The Web services assistant continues processing.
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.
SYSPRINT
DFHLS2WS
DFHLS2WS has found a macro within the C or C++ header file. Macros are not supported.
The Web services assistant continues processing.
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.
SYSPRINT
DFHLS2WS
DFHLS2WS has found a constant within an array declaration. This is not supported.
The Web services assistant continues processing.
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.
SYSPRINT
DFHLS2WS
DFHLS2WS has detected a keyword keyword that is not currently supported, it has been ignored.
The Web services assistant continues processing.
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.
SYSPRINT
DFHLS2WS
DFHLS2WS has detected and ignored an assignment operator within a C or C++ header file.
The Web services assistant continues processing.
Consider removing the assignment operator from the header file.
SYSPRINT
DFHLS2WS
DFHLS2WS has detected and ignored an initialization operator within a C or C++ header file.
The Web services assistant continues processing.
Consider removing the initialization operator from the header file.
SYSPRINT
DFHLS2WS
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.
The Web services assistant continues processing.
Consider removing the named variable from the header file.
SYSPRINT
DFHLS2WS
DFHLS2WS has been unable to locate a requested structure within the C or C++ header file.
The Web services assistant continues processing.
Correct or supply a value for the STRUCTURE input parameter.
SYSPRINT
DFHLS2WS
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.
The Web services assistant continues processing.
Correct the header file.
SYSPRINT
DFHLS2WS
DFHLS2WS has detected a duplicate type definition in the C or C++ header file.
The Web services assistant continues processing.
Correct the header file.
SYSPRINT
DFHLS2WS
DFHLS2WS has been unable to locate the main structure within the C or C++ header file.
The Web services assistant continues processing.
Correct or supply a value for the STRUCTURE input parameter.
SYSPRINT
DFHLS2WS
DFHLS2WS has encountered a value that should be numeric but does not appear to be a valid number. The problematic value is value
The Web services assistant continues processing.
Correct the language structure.
.
SYSPRINT
DFHLS2WS
DFHLS2WS has detected a PICTURE clause that it does not currently support for BINARY or DISPLAY data types.
The Web services assistant continues processing.
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.
SYSPRINT
DFHLS2WS
DFHLS2WS has detected a PICTURE clause that it does not currently support.
The Web services assistant continues processing.
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.
SYSPRINT
DFHLS2WS
DFHLS2WS has detected an error in one of the language structures. 01 level identifiers should not be present within the main language structure.
The Web services assistant continues processing.
Remove the 01 level identifier from within the language structure.
SYSPRINT
DFHLS2WS
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
The Web services assistant continues processing.
Correct the identified problem.
SYSPRINT
DFHWS2LS, DFHLS2WS
One or more error messages and one or more warning messages have been issued by the Web services assistant.
The web services assistant fails with return code 12.
Resolve the previously issued error messages and consider addressing the warning messages.
SYSPRINT
DFHWS2LS, DFHLS2WS
One or more error messages have been issued by the Web services assistant.
The web services assistant fails with return code 12.
Resolve the previously issued error messages.
SYSPRINT
DFHWS2LS, DFHLS2WS
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.
The Web services assistant continues processing.
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.
SYSPRINT
DFHLS2WS
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.
The Web services assistant continues processing.
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
SYSPRINT
DFHLS2WS
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.
The Web services assistant continues processing.
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
SYSPRINT
DFHLS2WS
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.
The Web services assistant continues processing.
Consider changing the PGMINT input parameter to CHANNEL rather than COMMAREA.
SYSPRINT
DFHLS2WS
DFHLS2WS has spotted a line of PL/I based code that it does not support at line line
The Web services assistant continues processing.
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.
SYSPRINT
DFHLS2WS
The termination character for a language structure is missing. It is assumed that the end of file indicates the end of the language structure.
The Web services assistant continues processing.
Correct the language structure.
SYSPRINT
DFHLS2WS
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.
The Web services assistant continues processing.
Change each entry within the language structure to specify ALIGNED or UNALIGNED individually.
SYSPRINT
DFHLS2WS
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.
The Web services assistant continues processing.
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.
SYSPRINT
DFHLS2WS
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.
The Web services assistant continues processing.
Correct the language structure.
SYSPRINT
DFHLS2WS
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.
The Web services assistant continues processing.
Either correct the language structure or change the LANG input parameter to specify PLI-ENTERPRISE.
SYSPRINT
DFHLS2WS
DFHLS2WS has spotted a line of PL/I based code that it does not support after line line
The Web services assistant continues processing.
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.
DFHLS2WS
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.
The Web services assistant continues processing.
Either correct the language structure or change the LANG input parameter to specify PLI-ENTERPRISE.
SYSPRINT
DFHLS2WS
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.
The Web services assistant continues processing.
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.
SYSPRINT
DFHLS2WS
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.
The Web services assistant continues processing.
Either correct the language structure or change the LANG input parameter to specify PLI-ENTERPRISE.
SYSPRINT
DFHLS2WS
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.
The Web services assistant continues processing.
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.
SYSPRINT
DFHLS2WS
DFHLS2WS has detected a problem in a PL/I language structure. A data type specifies a length of 0.
The Web services assistant continues processing.
Correct the problem.
SYSPRINT
DFHLS2WS
DFHLS2WS has detected a problem in a PL/I language structure. The length of a PICTURE clause can not be determined.
The Web services assistant continues processing.
Correct the problem.
SYSPRINT
DFHLS2WS
DFHLS2WS has detected an unsupported data type in a PL/I language structure. FIXED BINARY scaling factors are not supported.
The Web services assistant continues processing.
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.
SYSPRINT
DFHLS2WS
DFHLS2WS has detected an error in a PL/I language structure. A precision factor which is too large for PL/I has been specified.
The Web services assistant continues processing.
Correct the problem.
SYSPRINT
DFHLS2WS
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.
The Web services assistant continues processing.
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.
SYSPRINT
DFHLS2WS
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.
The Web services assistant continues processing.
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.
SYSPRINT
DFHLS2WS
The Web services assistant as replaced existing PDS member member.
The Web services assistant continues processing.
No user action is required. You may safely ignore this message.
SYSPRINT
DFHWS2LS, DFHLS2WS
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.
The Web services assistant continues processing.
Ensure that all other processes which have locks on the PDS release those locks.
SYSPRINT
DFHWS2LS, DFHLS2WS
The Web services assistant as replaced existing file file
The Web services assistant continues processing.
No user action is required. You may safely ignore this message.
SYSPRINT
DFHWS2LS, DFHLS2WS
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.
The Web services assistant continues processing.
Change the value of the PGMINT input parameter to CHANNEL.
SYSPRINT
DFHWS2LS
DFHWS2LS needs to generate one or more language structures for request messages but the REQMEM input parameter has not been set.
The Web services assistant continues processing.
Specify a value for the REQMEM input parameter.
SYSPRINT
DFHWS2LS
DFHWS2LS needs to generate one or more language structures for response messages but the RESPMEM input parameter has not been set.
The Web services assistant continues processing.
Specify a value for the RESPMEM input parameter.
SYSPRINT
DFHWS2LS
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.
The Web services assistant continues processing.
You may safely ignore this message.
SYSPRINT
DFHWS2LS
The Web services assistant has completed processing. No error or warning messages have been issued.
The Web services assistant ends with return code 0.
You may safely ignore this message.
SYSPRINT
DFHWS2LS, DFHLS2WS
DFHWS2LS has not found any WSDL operations associated with WSDL binding binding
The Web services assistant continues processing.
Either correct the WSDL document or supply a different value for the BINDING input parameter.
SYSPRINT
DFHWS2LS
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.
The Web services assistant continues processing.
Consider changing the PGMINT input parameter to CHANNEL rather than COMMAREA.
SYSPRINT
DFHWS2LS
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'.
The Web services assistant continues processing.
Correct the WSDL.
SYSPRINT
DFHWS2LS
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.
The Web services assistant continues processing.
Either correct the WSDL document or specify a different BINDING input parameter.
SYSPRINT
DFHWS2LS
DFHWS2LS has detected an error in the WSDL document. The WSDL binding is missing a soapAction attribute for operation operation
The Web services assistant continues processing.
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.
SYSPRINT
DFHWS2LS
DFHWS2LS has detected an error in the WSDL document. The WSDL binding specifies a soapAction attribute for use with SOAP 1.2.
The Web services assistant continues processing.
Consider removing the soapAction attribute or changing the WSDL to indicate the use of SOAP 1.1.
SYSPRINT
DFHWS2LS
DFHWS2LS has detected an error in the WSDL document. The WSDL binding specifies a soapAction attribute for a non-HTTP transport protocol.
The Web services assistant continues processing.
Remove the soapAction attribute.
SYSPRINT
DFHWS2LS
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.
The Web services assistant continues processing.
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:
SYSPRINT
DFHWS2LS
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.
The Web services assistant continues processing.
Either correct the WSDL document or specify a different BINDING input parameter.
SYSPRINT
DFHWS2LS
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'.
The Web services assistant continues processing.
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:
SYSPRINT
DFHWS2LS
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.
The Web services assistant continues processing.
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:
SYSPRINT
DFHWS2LS
DFHWS2LS has encountered a problem with the WSDL document. The WSDL binding specifies no transport protocols. DFHWS2LS requires one transport protocol per binding.
The Web services assistant continues processing.
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:
SYSPRINT
DFHWS2LS
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.
The Web services assistant continues processing.
Specify a value for the BINDING input parameter.
SYSPRINT
DFHWS2LS
The value of the BINDING input parameter does not identify a binding element in the WSDL document.
The Web services assistant continues processing.
Correct the value of the BINDING input parameter.
SYSPRINT
DFHWS2LS
DFHWS2LS has detected that the WSDL binding does not indicate the use of SOAP. DFHWS2LS only supports Web services that use SOAP.
The Web services assistant continues processing.
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:
SYSPRINT
DFHWS2LS
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.
The Web services assistant continues processing.
Remove all but one of the service elements for the binding.
SYSPRINT
DFHWS2LS
The WSDL document does not appear to contain WSDL. It may have been corrupted in transit or it may not contain XML.
The Web services assistant continues processing.
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.
SYSPRINT
DFHWS2LS
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.
The Web services assistant continues processing.
Either correct or remove the encoding attribute. It is likely that the correct value should be UTF-8.
SYSPRINT
DFHWS2LS
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.
The Web services assistant continues processing.
Either correct or remove the encoding attribute. It is likely that the correct value should be EBCDIC-CP-US.
SYSPRINT
DFHWS2LS
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
The Web services assistant continues processing.
Correct the identified problem.
SYSPRINT
DFHWS2LS
The Web services assistant has completed and has issued one or more warning messages.
The Web services assistant ends with return code 4.
Read the previously issued warning messages and decide on what if any actions must be taken.
SYSPRINT
DFHWS2LS, DFHLS2WS
The value of parameter parameter is value
The Web services assistant continues processing.
You may safely ignore this message.
SYSPRINT
DFHWS2LS, DFHLS2WS
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.
The Web services assistant continues processing.
Consider hosting the Web services assistant on a platform that is supported such as z/OS.
SYSPRINT
DFHWS2LS, DFHLS2WS
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.
The Web services assistant continues processing.
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.
SYSPRINT
DFHLS2WS
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.
The Web services assistant continues processing.
Consider changing the PGMINT input parameter to CHANNEL rather than COMMAREA.
SYSPRINT
DFHWS2LS
An invalid value has been specified for the MAPPING-LEVEL parameter.
The Web services assistant continues processing.
Correct the value of the MAPPING-LEVEL parameter.
SYSPRINT
DFHWS2LS, DFHLS2WS
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.
The Web services assistant continues processing.
Consider switching to the most current mapping level.
SYSPRINT
DFHWS2LS, DFHLS2WS
The Web services assistants require a more recent version of Java in order to execute.
The Web services assistant continues processing.
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.
SYSPRINT
DFHWS2LS, DFHLS2WS
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.
The Web services assistant continues processing.
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'.
SYSPRINT
DFHLS2WS
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.
The Web services assistant continues processing.
Alter the WSDL document so that it does include a WSDL binding.
DFHWS2LS
A value has been specified for one of the parameters in DFHLS2WS or DFHWS2LS that is invalid.
The Web services assistant continues processing.
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.
SYSPRINT
DFHLS2WS, DFHWS2LS