DFHPInnnn messages

DFHPI0001
applid An abend (code aaa/bbbb) has occurred at offset X'offset' in module modname.
DFHPI0002
applid A severe error (code X'code') has occurred in module modname.
DFHPI0004
applid A possible loop has been detected at offset X'offset' in module modname.
DFHPI0110
date time applid An attempt to start program DFHPIDSH by something other than an attach request from web domain has been made. This is not allowed.
DFHPI0111
date time applid tranid Call to WebSphere MQ function function returned with reason code reason_code. Transaction abended.
DFHPI0112
date time applid tranid Unable to locate URIMAP to match HOST hostname and PATH pathname. Unable to process inbound MQ message.
DFHPI0113
date time applid tranid URIMAP urimapname has been located for HOST hostname and PATH pathname, but does not have USAGE(PIPELINE). Unable to process inbound MQ message.
DFHPI0114
date time applid tranid The pipeline MQ transport mechanism failed because a call to WebSphere MQ function function returned with reason code reason_code.
DFHPI0115
date time applid tranid The service provider pipeline has returned a response message to the MQ transport, but the inbound request did not expect a response. The response message is ignored.
DFHPI0116
date time applid A one-way request has been received as a WebSphere MQ persistent message, but the provider pipeline has abended or backed out changes to recoverable resources. The BTS process processname of processtype processtype has completed with status ABENDED and this process can be re-tried or used to provide information for reporting the failure.
DFHPI0117
date time applid BTS Process processname of processtype processtype, which has completed with status ABENDED, has been cancelled. A provider pipeline started with a persistent WebSphere MQ message has abended or backed out, but a response has been sent to the requester.
DFHPI0118
applid CICS has attempted to use BTS processes to support pipelines started with WebSphere MQ persistent messages. This attempt failed. CICS will continue, using channel based containers for the pipeline, but there is a risk of data loss in the event of a system failure. Ensure that BTS processtype, repository and local request queue are correctly defined and installed.
DFHPI0119
date time applid The XML Toolkit could not be loaded. Some configurations of the CICS Supplied WS-Security handler are not usable.
DFHPI0200
date time applid BUNDLE bundlename has successfully installed PIPELINE pipeline in the {Disabled state. Enabling process initiated | Disabled state}.
DFHPI0201
date time applid BUNDLE bundlename has failed to install PIPELINE pipeline because {the definition is invalid | of an installation failure | an internal error occurred}.
DFHPI0202
date time applid PIPELINE name was not specified or is too long in BUNDLE bundlename.
DFHPI0203
date time applid CONFIGFILE path in PIPELINE pipeline is too long in BUNDLE bundlename.
DFHPI0204 I
date time applid userid PIPELINE Pipeline is now ENABLED and is ready for use.
DFHPI0220
date time applid BUNDLE bundlename has successfully installed WEBSERVICE webservice in the {Disabled state. Enabling process initiated | Disabled state}.
DFHPI0221
date time applid BUNDLE bundlename has failed to install WEBSERVICE webservice because {the definition is invalid | of an installation failure | an internal error occurred}.
DFHPI0222
date time applid WEBSERVICE name was not specified or is too long in BUNDLE bundlename.
DFHPI0223 E
date time applid attribute path in WEBSERVICE webservice is too long in BUNDLE bundlename.
DFHPI0300
date time applid CICS could not invoke WEBSERVICE WebService because it was unable to find container container_name.
DFHPI0301
date time applid CICS was unable to link to PROGRAM program_name while attempting to invoke WEBSERVICE WebService. {The program abended. | The program was not defined. | The program was not enabled. | The program was not loadable. | No further details are available.}
DFHPI0400
date time applid tranid The CICS pipeline HTTP transport mechanism failed to send a request because {the request was using an invalid host codepage | there was a socket error (IO_ERROR) | the URL was invalid | the connection was closed | a socket request timed out | a proxy error was detected | there was an HTTP error | an invalid media type was used | there was an authorization problem | there was a problem with the client certificate | there was a URIMAP problem | SSL is not supported in CICS | there was a error with exit XWBAUTH | the URIMAP is disabled | there was a socket error (ADDRESS_IN_USE) | there was a socket error (ADDRESS_NOT_AVAILABLE) | there was a socket error (ALREADY_ASSOCIATED) | the connection was refused | there was a socket error (INVALID_OPTION) | there was a socket error (MAX_PORTS_REACHED) | there was a socket error (MISSING_OPTION) | there was a socket error (NEVER_ASSOCIATED) | there was a socket error (NO_CONNECTION) | there was a socket error (NO_SOCKET_AVAILABLE) | there was a socket error (NOT_PENDING) | there was a socket error (NOTIFIED) | there was a socket error (SCHEDULED) | there was a socket error (SOCKET_IN_USE) | there was a socket error (STATE_ERROR) | there was a socket error (TASK_CANCELLED) | there was a socket error (TCP_NOT_ACTIVE)}. Problem occurred for URI URI .
DFHPI0401
date time applid tranid The CICS pipeline HTTP transport mechanism failed to send a response or receive a request because {the codepage was not found | there was a socket error | the connection was closed | the client codepage was invalid | an HTTP chunking error occurred}.
DFHPI0402
date time applid tranid The CICS pipeline HTTP transport mechanism failed to send a request because the URI specified an unknown host: hostname.
DFHPI0403
date time applid tranid The CICS pipeline HTTP transport mechanism failed to receive a response because {the socket receive was timed out | the task was purged}. Problem occurred for URI URI.
DFHPI0404
date time applid tranid A failure occurred in the CICS pipeline HTTP transport mechanism for PIPELINE pipeline_name WEBSERVICE webservice_name.
DFHPI0450
date time applid tranid The CICS transport mechanism in the pipeline was unable to successfully handle the request because of an invalid URI.
DFHPI0451
date time applid tranid The CICS transport manager encountered an error while trying to link to program program_name.
DFHPI0452
date time applid tranid The CICS transport manager encountered an error while trying to locate URIMAP with HOST=localhost and PATH=urimap_path.
DFHPI0453
date time applid tranid The CICS transport manager encountered an error while trying to use URIMAP urimap_name.
DFHPI0454
date time applid tranid The CICS transport manager encountered an error while trying to use provider pipeline pipeline_name.
DFHPI0455
date time applid tranid The CICS transport manager encountered an error while trying to use requester pipeline pipeline_name.
DFHPI0456
date time applid tranid The CICS transport manager encountered an error with the input data being greater then the maximum COMMAREA length.
DFHPI0457
date time applid tranid The CICS transport manager was unable to successfully handle the request because of the missing targetServiceUri parameter in the URI.
DFHPI0500
date time applid tranid The CICS Pipeline Manager DFHPIPM encountered an error while trying to link to program program_name. {The program abended. | The program was not defined. | The program was not enabled. | The program was not loadable. | No further details are available.} PIPELINE: pipeline.
DFHPI0501
date time applid tranid The CICS Pipeline Manager cannot proceed as the pipeline is unusable. {The pipeline was not found. | The pipeline is disabled. | The pipeline was of the wrong type. | The pipeline is configured for z/OS Connect.} PIPELINE: pipeline.
DFHPI0502
date time applid tranid The CICS Pipeline Manager has failed to receive a request from the underlying transport. TRANSPORT: transport, PIPELINE: pipeline.
DFHPI0503
date time applid tranid The CICS Pipeline Manager has failed to send a response on the underlying transport. TRANSPORT: transport, PIPELINE: pipeline.
DFHPI0504
date time applid tranid The CICS Pipeline Manager has failed to communicate with a service provider due to an error in the underlying transport. TRANSPORT: transport, PIPELINE: pipeline.
DFHPI0505
date time applid tranid The CICS Pipeline Manager has failed to communicate with a remote server as no URI was provided. PIPELINE: pipeline.
DFHPI0506
date time applid tranid The CICS Pipeline Manager has failed to communicate with a remote server due to an invalid URI scheme being specified. URI: uri, PIPELINE: pipeline.
DFHPI0507
date time applid tranid The CICS Pipeline Manager has failed to receive a response from an application handling task.{The request timed out. | The application task abended. | The connection to the application task was closed.} PIPELINE: pipeline.
DFHPI0508 E
date time applid The pipeline manager is unable to create or join a request stream because it is unable to reach the target for transaction tranid with userid userid.
DFHPI0509 E
date time applid The pipeline manager is unable to create or join a request stream because transaction tranid is not installed.
DFHPI0510 E
date time applid The pipeline manager is unable to create or join a request stream because it has encountered a severe error for transaction tranid with userid userid.
DFHPI0511
date time applid tranid The CICS Pipeline Manager has failed to receive a response from the target Secure Token Service: sts_uri. The response message failed to parse.
DFHPI0512
date time applid tranid The CICS Pipeline Manager has received a fault from the target Secure Token Service: sts_uri. The fault had a fault code of fault_code.
DFHPI0513
date time applid tranid The CICS Pipeline Manager has failed to find the required credentials in a response from the Secure Token Service: sts_uri.
DFHPI0514
date time applid tranid The CICS Pipeline Manager has failed to find the required credentials in a request. An element : local_name , in namespace: namespace, was expected.
DFHPI0515
date time applid tranid The CICS Pipeline Manager cannot run a CICS supplied WS-Security handler in pipeline: pipeline. The XML Toolkit was not available.
DFHPI0516
date time applid tranid SAML request saml_function to endpoint saml_endpoint on JVM server jvmserver has failed because {of an invalid token. | of a container error. | a required input container is missing. | the JVM server is not enabled. | the JVM server cannot be found. | the DFHSAML-FUNCTION container is not DATATYPE(CHAR). | the DFHSAML-TOKEN container is not found. | the DFHSAML-TOKEN container is not DATATYPE(CHAR). | the DFHSAML-JVM container is not DATATYPE(CHAR). | the DFHSAML-FILTER container is not DATATYPE(CHAR). | the DFHSAML-SIGNED container is not DATATYPE(CHAR). | of an error in parsing the token. | the DFHSAML-FILTER container has invalid data. | the DFHSAML-FUNCTION container has invalid data. | the DFHSAML-SIGNED container has invalid data. | the DFHSAML-OUTTOKEN container is not found. | the certificate has expired. | the token is no longer valid. | the certificate in the token is not trusted. | the input container is not readonly. | a signature element is not specified in the Security Token Service configuration file. | an error has occurred while adding an attribute to the token. | at least one of the attribute input containers is not DATATYPE(CHAR). | the value of an attribute is missing. | the name of an attribute is missing. | the KEYRING SIT parameter is not set. | the certificate was not found in the keyring. | the transaction channel DFHTRANSACTION cannot be found. | the JVM server is not configured for SAML. | the DFHSAML-RESPONSE container cannot be found. | of an internal error.}
DFHPI0517
date time applid tranid The CICS Pipeline Manager DFHPIPM encountered an error while trying to link to program program_name. Abend, abend_code, has been issued.
DFHPI0600
date time applid The CICS SOAP handler has been passed a container that is not DATATYPE(CHAR).
DFHPI0601
date time applid The CICS SOAP handler has been passed data that does not begin with a '<' character.
DFHPI0602
date time applid tranid trannum The CICS SOAP handler failed to parse a message. The parser error code is errcode. The error was found at offset offset into the message. Further information: {a GETMAIN failure has occurred | an unspecified error has been detected in DFHPIEP | a non-SOAP tag has been found in the SOAP envelope | an in-line DTD has been found in the SOAP envelope | an unspecified error has occurred | the namespace of the SOAP envelope is not recognized | an XML processing instruction has been found | the SOAP envelope is not well formed | an unqualified attribute has been found on a SOAP tag | the PL/I XML parser returned a fatal error code | an unspecified error has occurred | a problem occurred processing a tag in DFHPIEP | a problem occurred processing an attribute in DFHPIEP}.
DFHPI0603 I
date time applid The CICS SOAP handler has received an unexpected HTTP GET for URI Uri.
DFHPI0604
date time applid tranid The CICS SOAP handler encountered an error while trying to link to program program_name. {The program abended. | The program was not defined. | The program was not enabled. | The program was not loadable. | No further details are available.} PIPELINE: pipeline.
DFHPI0700 S
date time applid userid PIPELINE pipeline failed to install completely because PL/I support is not available and is required for pipeline usage.
DFHPI0701 I
date time applid userid PIPELINE pipeline has been created.
DFHPI0702 E
date time applid userid PIPELINE pipeline encountered an error in the configuration file filename for pipeline at offset X'offset'. The element name is elementname.
DFHPI0703 I
date time applid userid PIPELINE pipeline is about to scan the WSDIR directory.
DFHPI0704 I
date time applid userid PIPELINE pipeline Implicit scan has completed. Number of wsbind files found in the WSDIR directory: num_files. Number of successful WEBSERVICE creates: num_ok. Number of failed WEBSERVICE creates: num_failed.
DFHPI0705 E
date time applid userid PIPELINE pipeline cannot copy the configuration file to the derived shelf directory derived_shelf.
DFHPI0706 E
date time applid userid PIPELINE pipeline resolution failed because it cannot be determined if this is a requester or provider pipeline.
DFHPI0707 E
date time applid userid PIPELINE pipeline resolution failed because namespace prefixes are not supported in the XML configuration file.
DFHPI0708 E
date time applid userid PIPELINE pipeline resolution failed because the XML configuration file cannot be found.
DFHPI0710 I
date time applid userid PIPELINE pipeline was successfully discarded.
DFHPI0711 E
date time applid userid PIPELINE pipeline resolution failed because the SAX parser returned error code X'errcode'. The error was at offset X'offset' in the CONFIGFILE. The first eight bytes of data at this offset are: 'hexdata'.
DFHPI0712 E
date time applid userid PIPELINE pipeline failed to install due to insufficient access rights to a zFS file.
DFHPI0713 E
date time applid userid PIPELINE pipelinename The pipeline resolution transaction CPIR did not attach.
DFHPI0714 E
date time applid userid PIPELINE pipeline failed to install. The directory specified in the WSDIR parameter is invalid.
DFHPI0715 I
date time applid userid PIPELINE pipeline explicit scan has completed. Number of wsbind files found in the WSDIR directory: num_files. Number of WEBSERVICEs created or updated: num_ok. Number of WEBSERVICEs not requiring an update: num_nun. Number of failed WEBSERVICE creates or updates: num_failed.
DFHPI0716 E
date time applid userid Unable to dynamically create a WEBSERVICE for PIPELINE pipeline. The complete WSBIND file name is too long.
DFHPI0717 E
date time applid userid PIPELINE pipeline resolution failed because the XML configuration file is empty.
DFHPI0720 E
date time applid userid PIPELINE pipeline encountered an error in the configuration file filename at offset X'offset'. Found : element_found yet expected : {<service> | <transport> or <service> | a transport handler list | <service_handler_list> or <terminal_handler> | <handler> | <program> | <handler_parameter_list> | <name> | <cics_soap_1.1_handler> | <cics_soap_1.2_handler> | <header_program> | <service> | <service_handler_list> | <default_target> or a default handler list | <program_name> | <namespace> | <localname> | <mandatory> | true, false, 1 or 0 | <terminal_handler> | <service_parameter_list> | <service>, <transport> or <service_parameter_list> | / | <localname>value</localname> | <namespace>valid value for namespace</namespace> | a tag that is valid within <service_handler_list> | <jvmserver> tag within <cics_soap_1.n_handler_java> | <jvmserver>value</jvmserver> | <repository>value</repository> | <apphandler> | </provider_pipeline_json>}.
DFHPI0721 E
date time applid userid PIPELINE pipeline encountered an error in the configuration file filename for pipeline at offset X'offset'. The value attribvalue for attribute attribname is not valid.
DFHPI0722 E
date time applid userid PIPELINE pipeline encountered an error in the configuration file filename for the pipeline. The WSSE_Handler configuration has values specified for mode and trust that are not valid in this pipeline.
DFHPI0723 E
date time applid userid PIPELINE pipeline encountered an error in the configuration file filename for the pipeline. The value for the algorithm specified for the element is not supported.
DFHPI0724 E
date time applid userid PIPELINE pipeline encountered an error in the configuration file filename for the pipeline. The WSSE_Handler configuration has both <authentication> and <sts_authentication> elements specified. You must only specify one of these elements.
DFHPI0725 E
date time applid userid PIPELINE pipeline encountered an error in the configuration file filename for the pipeline. The element element must be specified.
DFHPI0726 E
date time applid userid PIPELINE pipeline encountered an error in the configuration file filename for the pipeline. The element element is a duplicate or unrecognized element.
DFHPI0727 E
date time applid userid PIPELINE pipeline cannot be installed as it requires support for ICRX based identity tokens and these are not supported by the platform.
DFHPI0728 E
date time applid userid PIPELINE pipeline encountered an error in the configuration file filename for the pipeline. The repository Axis2 configuration file element cannot be accessed by CICS.
DFHPI0729 E
date time applid userid PIPELINE pipeline encountered an error in the pipeline configuration file filename at offset X'offset'. The CICS Java SOAP handler cannot be an intermediate message handler.
DFHPI0730
date time applid An attempt to register a remote Web service as a participant in unit of work - X'uowid' has failed.
DFHPI0731
date time applid An attempt to register unit of work - X'uowid' with a remote WSAT coordinating transaction has failed.
DFHPI0732
date time applid A request to rollback unit of work - X'uowid' has been received from a remote WS-AT coordinating transaction.
DFHPI0733
date time applid A transaction timed out while waiting for a Prepare message from a remote WS-AT coordinator. The unit of work - X'uowid' will be rolled back.
DFHPI0734 E
date time applid Error 'exception' occurred whilst configuring PIPELINE pipeline within a JVMSERVER.
DFHPI0735 E
date time applid Error 'exception' occurred whilst configuring WEBSERVICE webservice within a JVMSERVER.
DFHPI0736 E
date time applid PIPELINE pipeline' encountered an error in the configuration file filename for the pipeline. The file has both <apphandler> and <apphandler_class> elements specified. You may only specify one of these elements.
DFHPI0737
date time applid PIPELINE pipeline encountered an error in the configuration file filename for the pipeline. Configuration for {endpoint cics://PROGRAM/DFHSAML | sts_authentication attribute extract | sts_authentication attribute token_signature | jvmserver element | auth_token_type namespace for SAML 1.1 or SAML 2.0 assertions | sts_authentication attribute tran_channel} implies configuration for the SAML security token service. This requires {a provider mode pipeline. | sts_authentication element attribute action=validate. | auth_token_type namespace for SAML 1.1 or SAML 2.0 assertions.}
DFHPI0800 E
date time applid userid Atomic Transaction processing failed because the SAX parser returned error code X'errcode'. The error was at offset X'offset' in the SOAP message.
DFHPI0801I E
date time applid A one way message has been found in an atomic transaction message exchange for transaction TRAN.
DFHPI0901 I
date time applid userid New WEBSERVICE WebService is being created during a scan against PIPELINE Pipeline.
DFHPI0902 I
date time applid userid WEBSERVICE WebService is being updated during a scan against PIPELINE Pipeline.
DFHPI0903 I
date time applid userid New URIMAP UriMap is being created during a scan against PIPELINE Pipeline for WEBSERVICE WebService.
DFHPI0904 I
date time applid userid URIMAP UriMap could not be created for WEBSERVICE WebService in PIPELINE Pipeline. The URI that could not be allocated is: 'Uri'.
DFHPI0905 E
date time applid userid WEBSERVICE WebService within PIPELINE Pipeline cannot check for archive file because the WSDL name Name is too long.
DFHPI0906 E
date time applid userid WEBSERVICE WebService within PIPELINE Pipeline cannot generate URIMAP for WSDL discovery because URI Uri is too long.
DFHPI0910 I
date time applid userid WEBSERVICE WebService within PIPELINE Pipeline has been created.
DFHPI0911 E
date time applid userid WEBSERVICE WebService within PIPELINE Pipeline was not created because: {there is insufficient storage | there is a directory domain error | the specified PIPELINE is not installed | a lock cannot be obtained | there is a duplicate resource error}.
DFHPI0912 I
date time applid userid WEBSERVICE WebService was successfully discarded.
DFHPI0913 I
date time applid userid WEBSERVICE WebService is being discarded.
DFHPI0914 E
date time applid userid WEBSERVICE WebService is UNUSABLE because: {the WSBind file was not found | CICS is not authorized to read the WSBind file | there is insufficient storage to load the WSBind file | the zFS read for the WSBind file failed | writing the WSBind file to the shelf failed | the PIPELINE is incompatible with this WEBSERVICE | the CPIR resolution transaction could not be attached | the direction of the PIPELINE can't be determined | the WSBind file is corrupt | the WSBind file has an invalid version number | the WSBind file has an out of date version number | the WSBind file product number was not recognized | the PIPELINE is not a SOAP PIPELINE | the PIPELINE does not support SOAP version 1.2 | the PIPELINE is not configured for SOAP version 1.1 | the WSBind file is incompatible with the LOCALCCSID | it is incompatible with a Bundle defined PIPELINE | the associated JVMSERVER does not support CICS z/OS Connect | the WSBind file defines too many operations for JSON | the WSBind file could not be configured for JSON | the WSBind file specifies an unsupported CCSID | the WSBind file specifies RESTful. This is not supported in non-Java JSON processing}.
DFHPI0915 I
date time applid userid WEBSERVICE WebService is now INSERVICE and is ready for use.
DFHPI0916 E
date time applid userid WEBSERVICE WebService within PIPELINE Pipeline was not created because it clashes with another WEBSERVICE of the same name in PIPELINE Pipeline.
DFHPI0917 W
date time applid userid WEBSERVICE WebService might perform unpredictably as the PIPELINE Pipeline is non-SOAP.
DFHPI0918 E
date time applid userid WEBSERVICE WebService within PIPELINE Pipeline can not be set as INSERVICE because the specified PIPELINE is not installed.
DFHPI0919 E
date time applid userid The WSDL file filename for WEBSERVICE WebService cannot be read because: {CICS is not authorized to read the file | the zFS read for the file failed}.
DFHPI0996
date time applid The Outbound Router program, DFHPIRT, has received a non-NORMAL response while attempting to read a container. The resulting error code is X'code' and the container name is container_name.
DFHPI0997
date time applid tranid PIPELINE pipeline WEBSERVICE webservice The CICS pipeline manager has encountered an error: {PIPELINE not found | PIPELINE not active | PIPELINE mode mismatch | unhandled node failure | context switch failed | request stream creation failure | request stream transport error | target program unavailable or abended | channel error | channel not found | URI not found | invalid URI | authorization failure | program abend | unidentified problem | timeout occurred | no request message | there was a problem with file PIDIR | attempt to register a WS-AT context twice | empty DFHREQUEST container returned from a handler | req and resp containers both returned from a handler | empty DFHRESPONSE container returned from a handler | chunking request from non-terminal node | chunking request is incompatible with MTOM/XOP | chunking request not supported for this transport | transport function failed | bad mime type | failure to receive request | failure to send response to WS-Addressing endpoint}.
DFHPI0998
date time applid The Outbound Router program, DFHPIRT, has received a non-NORMAL response while attempting to get the pipeline name from the DFHWS-PIPELINE container. The resulting error code is X'code'.
DFHPI0999
date time applid tranid The CICS pipeline manager has encountered a problem with file DFHPIDIR: {the file was not found | the file key length was too small | the file record size was too small | the file is full | the file control record is full | file recovery mode was not backout | there was an internal error | file failed to open or connect}.
DFHPI1000
date time applid The Outbound Router program, DFHPIRT, has detected an invalid URI in the DFHWS-STSACTION container. The URI was: 'uri'.
DFHPI1001
date time applid Validation of a {request | response} message for WEBSERVICE webservicename and operation operationname failed. The failure response contains the following message: 'message'.
DFHPI1002
date time applid Validation of a {request | response} message for WEBSERVICE webservicename and operation operationname was successful.
DFHPI1003
date time applid No current channel located. Validation cannot occur.
DFHPI1004
date time applid The attempt to link to DFHPIVAL to perform validation failed.
DFHPI1005
date time applid Attempt to link to program progname failed. SOAP conversions cannot be performed. Module: modname.
DFHPI1006
date time applid The WSBIND file used for WEBSERVICE WebService is not a type which CICS can use. Module: modname.
DFHPI1007
DATE TIME APPLID TRANID TRANNUM {XML | JSON} to data transformation failed because of incorrect input ({XML_FORMAT_ERROR | UNEXPECTED_CONTENT | HEADER_FORMAT_ERROR | UNDEFINED_ELEMENT | UNDEFINED_NAME_SPACE | ARRAY_OVERFLOW | NAME_TOO_LONG | PREFIX_TOO_LONG | NAME_SPACE_TOO_LONG | UNEXPECTED_XOP_INCLUDE | XOP_INCLUDE_ERROR | DUPLICATE_CHOICE | MISSING_XSI_TYPE | UNKNOWN_XSI_TYPE | MISSING_ATTRIBUTE | MIXED_CONTENT | MISSING_EQUALS_ATTR | MISSING_CLOSE_TAG_CHAR | MISSING_QUOTE_OR_APOSTROPHE | MISSING_END_QUOTE | DUPLICATE_ATTRIBUTE | MISMATCHED_TAGS | UNSUPPORTED_ENTITY | INVALID_UNICODE_DATA} error_qualifier) for {WEBSERVICE | XMLTRANSFORM | BUNDLE | EVENTBINDING | SCACOMPOSITE | JVMSERVER pipeline handler program | EPADAPTER | OSGIBUNDLE | PROGRAM | POLICY | EPADAPTERSET | APPLDEF | TRANSACTION | URIMAP | PLATDEF | LIBRARY | WARBUNDLE | EBABUNDLE | TCPIPSERVICE | JVMSERVER | FILE | PIPELINE | JSONTRANSFRM | EARBUNDLE | PACKAGESET | TYPE UNKNOWN} resource_name.
DFHPI1008
DATE TIME APPLID TRANID TRANNUM {XML | JSON} generation failed because of incorrect input ({ARRAY_CONTAINER_TOO_SMALL | DATA_STRUCTURE_TOO_SMALL | ARRAY_TOO_LARGE | ARRAY_TOO_SMALL | CONTAINER_NOT_FOUND | CONTAINER_NOT_BIT | CONTAINER_NOT_CHAR | BAD_CHOICE_ENUM | LENGTH_TOO_LONG | LITTLE_ENDIAN_BOM | INVALID_UNICODE_DATA} error_qualifier) for {WEBSERVICE | XMLTRANSFORM | BUNDLE | EVENTBINDING | SCACOMPOSITE | JVMSERVER pipeline handler program | EPADAPTER | OSGIBUNDLE | PROGRAM | POLICY | EPADAPTERSET | APPLDEF | TRANSACTION | URIMAP | PLATDEF | LIBRARY | WARBUNDLE | EBABUNDLE | TCPIPSERVICE | JVMSERVER | FILE | PIPELINE | JSONTRANSFRM | EARBUNDLE | TYPE UNKNOWN} resource_name.
DFHPI1009
DATE TIME APPLID TRANID TRANNUM {XML | JSON} to data transformation failed. A conversion error ({UNKNOWN_CONVERSION | INPUT_TOO_LONG | OUTPUT_OVERFLOW | NEGATIVE_UNSIGNED | NO_FRACTION_DIGITS | FRACTION_TOO_LONG | INVALID_CHARACTER | ODD_HEX_DIGITS | INVALID_BASE64 | NOT_PURE_DBCS | INVALID_FIELD_SIZE | EXPONENT_OVERFLOW | EXPONENT_UNDERFLOW | ABSTIME_INVALID}) occurred when converting field fieldname for {WEBSERVICE | XMLTRANSFORM | BUNDLE | EVENTBINDING | SCACOMPOSITE | JVMSERVER pipeline handler program | EPADAPTER | OSGIBUNDLE | PROGRAM | POLICY | EPADAPTERSET | APPLDEF | TRANSACTION | URIMAP | PLATDEF | LIBRARY | WARBUNDLE | EBABUNDLE | TCPIPSERVICE | JVMSERVER | FILE | PIPELINE | JSONTRANSFRM | EARBUNDLE | TYPE UNKNOWN} resource_name.
DFHPI1010
DATE TIME APPLID TRANID TRANNUM {XML | JSON} generation failed. A conversion error ({UNKNOWN_CONVERSION | NEGATIVE_UNSIGNED | INVALID_CHARACTER | INVALID_PACKED_DEC | INVALID_ZONED_DEC | INCOMPLETE_DBCS | ODD_DBCS_BYTES | INVALID_FIELD_SIZE | EXPONENT_OVERFLOW | EXPONENT_UNDERFLOW | ABSTIME_INVALID}) occurred when converting field fieldname for {WEBSERVICE | XMLTRANSFORM | BUNDLE | EVENTBINDING | SCACOMPOSITE | JVMSERVER pipeline handler program | EPADAPTER | OSGIBUNDLE | PROGRAM | POLICY | EPADAPTERSET | APPLDEF | TRANSACTION | URIMAP | PLATDEF | LIBRARY | WARBUNDLE | EBABUNDLE | TCPIPSERVICE | JVMSERVER | FILE | PIPELINE | JSONTRANSFRM | EARBUNDLE | TYPE UNKNOWN} resource_name.
DFHPI1020 E
date time applid tranid The CICS handling program for the SCACOMPOSITE type failed to create resource resource_name in the BUNDLE resource bundle_name because CICS failed to parse the SCDL resource definition scdl_path_name specified in bundle root directory bundle_root. {The SCDL is not valid. | Failed to convert the SCDL.}
DFHPI1100 E
date time applid userid PIPELINE pipeline encountered an error while processing an inbound MIME message. The problem with the MIME message is: {it contained an invalid character | it had an invalid header | it had an invalid MIME header | it had a boundary error | it did not contain a root part | it used an unsupported encoding | it caused an unexpected response}.
DFHPI1101 E
date time applid userid PIPELINE pipeline encountered an error while processing an inbound MIME message in compatibility mode. The problem with the MIME message was it contained: {a body that could not be parsed | an include for which there was no attachment}.
DFHPI1102 E
date time applid userid PIPELINE pipeline encountered an error while processing an outbound MIME message in compatibility mode. Generation of the MIME message failed because: {it contained a body that could not be parsed | a container had an invalid ccsid | a container had the wrong type}.
DFHPI1103 E
date time applid userid PIPELINE pipeline encountered an error while processing an outbound message in MIME compatibility mode. The problem with the MIME message was: {it contained a body that could not be parsed | it had an include for which there was no attachment | it caused an unexpected exception}.
DFHPI1201
date time applid Container DFHHTTPMETHOD does not contain POST.
DFHPI1202
date time applid Container DFHMEDIATYPE does not contain application/json.
DFHPI1203
date time applid Container containername could not be found.
DFHPI2000 E
date time applid tranid The installation of SCACOMPOSITE resource_name in the BUNDLE resource bundle_name did not complete successfully. {A WEBSERVICE wsbind file was not found. | A WEBSERVICE name was a duplicate. | A URIMAP has an invalid path. | A URIMAP has a duplicate path. | A binding combination was invalid. | A binding did not provide required values. | A Service required for wiring was not found. | A Reference required for wiring was not found. | A wire target was already wired. | A service or reference name was a duplicate. | A service or reference has multiple bindings. | A reference target was not found. | A reference target was invalid. | An implementation was not found.}
DFHPI2001 E
date time applid tranid The installation of SCACOMPOSITE resource_name in the BUNDLE resource bundle_name did not complete successfully. The bindfile could not be read. Bindfile: bindfile_name ,Binding:binding_name .
DFHPI2002 E
date time applid tranid The installation of SCACOMPOSITE resource_name in the BUNDLE resource bundle_name did not complete successfully. A duplicate WEBSERVICE name was used in a binding. WEBSERVICE: webservice_name ,Binding:binding_name .
DFHPI2003 E
date time applid tranid The installation of SCACOMPOSITE resource_name in the BUNDLE resource bundle_name did not complete successfully. A duplicate URIMAP path was used in a binding. Path: path_name ,Binding:binding_name .
DFHPI2004 E
date time applid tranid The installation of SCACOMPOSITE resource_name in the BUNDLE resource bundle_name did not complete successfully. A invalid URIMAP path was used in a binding. Path: path_name ,Binding:binding_name . {Reference: | Service:} element_name.
DFHPI2005 E
date time applid tranid The installation of SCACOMPOSITE resource_name in the BUNDLE resource bundle_name did not complete successfully. A binding attempted to wire to a target with an incompatible binding type. Target: target ,Binding:binding_name .
DFHPI2006 W
date time applid tranid The installation of SCACOMPOSITE resource_name in the BUNDLE resource bundle_name contained a wired binding that did not provide required value. The binding cannot be used unless a later composite provides the value. Value Type:{pipeline | uri | bindfile} ,Binding: binding_name .
DFHPI2007 E
date time applid tranid The installation of SCACOMPOSITE resource_name in the BUNDLE resource bundle_name did not complete successfully. A wired binding targeted a service which could not be found. Target: target_name ,Binding: binding_name .
DFHPI2008 E
date time applid tranid The installation of SCACOMPOSITE resource_name in the BUNDLE resource bundle_name did not complete successfully. A wired binding targeted a reference which could not be found. Target: target_name ,Binding: binding_name .
DFHPI2009 E
date time applid tranid The installation of SCACOMPOSITE resource_name in the BUNDLE resource bundle_name did not complete successfully. A wired binding targeted a service or reference which had already been wired. Target: target_name ,Binding: binding_name.
DFHPI2011 E
date time applid tranid The installation of SCACOMPOSITE resource_name in the BUNDLE resource bundle_name did not complete successfully. No services or references could be found in the composite implementation impl_comp.
DFHPI2012 E
date time applid tranid The installation of SCACOMPOSITE resource_name in the BUNDLE resource bundle_name did not complete successfully. The prerequisite composite implementation impl_comp could not be found.
DFHPI2015 E
date time applid tranid A attempt to directly invoke a service service_name failed. {The service is internal. | The service cannot be invoked directly. | The composite that defines the service is disabled. | The service uses the web services binding.}
DFHPI2016 E
date time applid tranid The installation of SCACOMPOSITE resource_name in the BUNDLE resource bundle_name did not complete successfully. A Web service binding was used to wire an internal reference to a service. Binding:binding_name.
DFHPI2018 E
date time applid tranid The installation of SCACOMPOSITE resource_name in the BUNDLE resource bundle_name did not complete successfully. The resource name must be the same as the composite name. Composite name:composite_name.
DFHPI2019 E
date time applid tranid The installation of SCACOMPOSITE resource_name in the BUNDLE resource bundle_name did not complete successfully. The SCDL encoding is invalid.
DFHPI2020 E
date time applid tranid The installation of SCACOMPOSITE resource_name in the BUNDLE resource bundle_name did not complete successfully. The SCDL is invalid.
DFHPI2021 W
date time applid tranid The installation of SCACOMPOSITE resource_name in the BUNDLE resource bundle_name might not complete successfully. {A composite name was not provided. | An internal reference name was not provided. | An internal reference target was not provided. | An internal service name was not provided. | An external reference name was was not provided. | An external reference promote was not provided. | An external reference target was not provided. | An external service name was not provided. | An external service promote was not provided.}
DFHPI2022 W
date time applid tranid The SCACOMPOSITE resource_name in the BUNDLE resource bundle_name defined an unsupported attribute in the SCDL. Attribute:{policySets. | requires. } {Composite | Service | Reference | Component | Implementation | Binding}:element_name.
DFHPI2023 E
date time applid tranid The installation of SCACOMPOSITE resource_name in the BUNDLE resource bundle_name did not complete successfully. The mapping modes of {reference | service } element_name and {reference | service } element_name must be identical.
DFHPI2024
date time applid tranid BUNDLE resource bundle_name cannot be enabled because one or more resources in the BUNDLE were not created successfully.
DFHPI2025 W
date time applid tranid An INVOKE SERVICE call failed because it used an unwired reference. Reference: reference_name , Scope: scope_name .
DFHPI2026 E
date time applid tranid The installation of SCACOMPOSITE resource_name in the BUNDLE resource bundle_name did not complete successfully. The prerequisite composite implementation impl_comp does not have any components defined.
DFHPI2027 E
date time applid tranid The installation of SCACOMPOSITE resource_name in the BUNDLE resource bundle_name did not complete successfully. The composite name is a duplicate of an existing composite.
DFHPI9000 E
ResourceBundle not found issuing message: value.
DFHPI9001 E
Message not found issuing message: value.
DFHPI9002 E
A WSDL operation name is too long to be supported by CICS: value.
DFHPI9003 E
A WSDL part name is too long to be supported by CICS: value.
DFHPI9004 E
The WSDL specifies a style value of document and contains a part name that refers to an XML type. Document style WSDL must only refer to XML elements.
DFHPI9010 E
Simple data type type is not atomic. List and union data types are not supported.
DFHPI9011 E
Unsupported super type super_type found for type base_type.
DFHPI9012 E
Schema wild cards (<any> tags) are only supported at mapping level 2.1 and later.
DFHPI9013 E
Schema model groups with maxOccurs or minOccurs not equal to 1 are not supported. Problem found for type: value.
DFHPI9014 E
No model group found for model group definition definition.
DFHPI9015 E
A schema particle with unrecognized content has been found: value.
DFHPI9016 E
Required schema element element cannot be found.
DFHPI9017 E
Unsupported attribute attribute found for schema element element.
DFHPI9018 E
Schema element element is missing a type definition.
DFHPI9019 E
Schema type type is not supported.
DFHPI9020 W
Schema attribute attribute has been found and ignored for type type.
DFHPI9021 E
A schema type with unrecognized content has been found: value.
DFHPI9022 W
Schema type type is being restricted to a total of value digits in the response message of operation operation.
DFHPI9023 W
Schema type type is being restricted to a total of value digits for operation operation.
DFHPI9024 E
Recursion within type type is not supported.
DFHPI9025 E
Required schema type type cannot be found.
DFHPI9026 E
URI uri cannot be resolved. Consider checking that the HTTP Proxy is correct.
DFHPI9027 E
The XML parser has found an error: value at line line and column column in document document.
DFHPI9028 E
The length of schema element element is set to value characters. CICS only supports up to value2 characters.
DFHPI9029 E
Implicit padding (slack bytes) are not supported for PL/I. Please change the language structure to ensure that all slack bytes are explicitly referenced and that top level structures start on a double-word boundary. Slack bytes are needed near or around field field.
DFHPI9030 E
Implicit padding (slack bytes) are not supported for PL/I. Please change the language structure to ensure that all slack bytes are explicitly referenced and that top level structures start on a double-word boundary. Slack bytes are needed near or around structure structure.
DFHPI9031 E
A structure or array is unexpectedly empty.
DFHPI9032 W
Schema attribute wild cards (<anyAttribute> tags) are not supported.
DFHPI9033 E
Duplicate elements with the same name in the same scope are not supported. The duplicated name is name.
DFHPI9034 W
Schema type type is being restricted to a total of value digits.
DFHPI9035 E
XML Schema element cannot be found in document document.
DFHPI9036 W
Abstract Data Types are not supported. Problems may be experienced with type type in element element.
DFHPI9037 E
XML Schema model groups are not supported within <choice> structures. Problem found in type type.
DFHPI9038 E
The number of options for an enumerated set of options exceeds the maximum supported value of 255.
DFHPI9039 E
Substitution groups within xsd:choice constructs are not supported. The substitution group name is name.
DFHPI9040 E
Array name occurs occurs times. The largest supported value is max.
DFHPI9500 E
An internal error has occurred. Please contact IBM Support.
DFHPI9501 E
The HTTPPROXY parameter is invalid. The correct format is proxy.hostname.com:8080 or similar.
DFHPI9502 E
One or more incorrect parameters have been specified.
DFHPI9503 E
Required parameter parameter is missing.
DFHPI9504 E
Parameter parameter has been specified but is not valid for program program.
DFHPI9505 E
Invalid value specified for the LANG parameter. Valid values are: COBOL, PLI-ENTERPRISE, PLI-OTHER, C or CPP.
DFHPI9506 E
Parameter parameter exceeds the maximum valid length of max characters. The supplied value is value.
DFHPI9507 W
Parameter parameter is not set therefore parameter parameter2 is ignored.
DFHPI9509 E
Parameter parameter contains invalid characters.
DFHPI9510 W
Invalid value specified for the PGMINT parameter. Valid values are: CHANNEL or COMMAREA. The default value of CHANNEL is assumed.
DFHPI9511 W
Parameter PGMINT is set to CHANNEL but parameter CONTID is not set. The default value of value is assumed.
DFHPI9512 W
Parameter CONTID is set but not needed for PGMINT=COMMAREA. Parameter CONTID is ignored.
DFHPI9513 W
The value of parameter parameter is missing a file extension, extension is assumed.
DFHPI9514 W
The value of parameter parameter specified a file extension other than extension.
DFHPI9515 E
PDS library library cannot be found.
DFHPI9516 E
PDS library library exists but cannot be read.
DFHPI9517 E
PDS library library exists but cannot be written to.
DFHPI9518 W
PDS library library specifies a record length less than 80 characters, output may be truncated.
DFHPI9519 E
Codepage codepage is not recognized.
DFHPI9520 E
Parameter RESPMEM and parameter REQMEM must supply different values.
DFHPI9521 E
The record format of PDS member member must be FB and have a record length of 80.
DFHPI9522 E
File file cannot be read.
DFHPI9523 E
An unexpected error occurred whilst processing file file. The problem is: value.
DFHPI9524 E
File file cannot be written to.
DFHPI9525 E
Cannot write a file because directory directory does not exist.
DFHPI9526 E
Cannot write a file because directory directory is not writable.
DFHPI9527 E
Cannot write to the log file, file, is not writable.
DFHPI9528 E
Cannot find or read file file.
DFHPI9529 W
Characters beyond column column have been truncated for line line.
DFHPI9530 I
Parameter parameter is not recognized and has been ignored.
DFHPI9531 E
Parameter STRUCTURE must only contain ( or ) characters in the first or last position.
DFHPI9532 E
Parameter STRUCTURE must be of the form STRUCTURE=(request_structure_name, response_structure_name).
DFHPI9533 E
Parameter parameter contains an invalid character character at position position in value value.
DFHPI9534 E
Non-unique operation signature found: value.
DFHPI9535 E
WSDL operation operation has an operation signature greater than value characters long and therefore is not supported by CICS.
DFHPI9536 E
User Defined Type type cannot be found.
DFHPI9537 W
Compiler directive directive has been ignored.
DFHPI9538 E
The required struct entry cannot be found.
DFHPI9539 E
An invalid character character has been found.
DFHPI9540 E
Unsupported keyword keyword has been found.
DFHPI9541 E
Fixed point decimal types are not supported.
DFHPI9542 E
Unsupported macro macro has been found.
DFHPI9543 E
Constant constant is not supported in array dimension.
DFHPI9544 W
Unsupported keyword keyword has been found and ignored.
DFHPI9545 W
Assignment operator detected and ignored.
DFHPI9546 W
Initialization operator detected and ignored.
DFHPI9547 E
Top level variables are not supported: value.
DFHPI9548 E
Top-level structure structure for C and C++ must be named value or must be specified using the 'STRUCTURE' parameter.
DFHPI9549 E
A type definition has been found with no instance and no label.
DFHPI9550 E
Duplicate type name name found.
DFHPI9551 E
Structure structure cannot be found.
DFHPI9552 E
Value value is not a valid integer in file 'fileName'.
DFHPI9553 E
PICTURE picture is not supported for BINARY fields, or DISPLAY fields before mapping level 1.2.
DFHPI9554 E
PICTURE picture is not supported.
DFHPI9555 E
Top level structure found within the main structure.
DFHPI9556 E
An unexpected error occurred whilst writing to file file. The problem is: value.
DFHPI9557 E
ERRORS and WARNINGS have been generated processing file file.
DFHPI9558 E
ERRORS have been generated processing file file.
DFHPI9559 W
Illegal character character has been found at the start of a name and replaced with X.
DFHPI9560 W
Illegal character character has been found in a name and replaced with X.
DFHPI9561 I
Identifier identifier has generated a name-clash for operation operation. Subsequent declarations have been renamed to ensure their uniqueness.
DFHPI9562 E
Parameter PGMINT is specified with value COMMAREA but there is too much data required for a COMMAREA.
DFHPI9563 E
Unsupported PL/I source code detected in line line.
DFHPI9564 W
A terminating ; is missing, it is assumed to be at the end of the file.
DFHPI9565 E
ALIGNED and UNALIGNED keywords are not supported for an entire structure.
DFHPI9566 E
The FIXED and FLOAT attributes are both missing: value.
DFHPI9567 E
Too many digits have been specified for a packed decimal field: value.
DFHPI9568 E
The UNSIGNED attribute is not supported unless PLI-ENTERPRISE is specified: value.
DFHPI9569 E
Unsupported PL/I source code detected after line line.
DFHPI9570 E
FIXED BINARY types with length greater than 31 are not supported unless PLI-ENTERPRISE is specified: value.
DFHPI9571 W
ORDINAL references are always treated as SIGNED FIXED BINARY (7) data types. If this is incorrect then please replace the ordinal reference with an equivalent FIXED BINARY variable: value.
DFHPI9572 E
ORDINAL types are only supported if PLI-ENTERPRISE is specified: value.
DFHPI9573 E
BIT fields are only supported if they are in multiples of 8: value.
DFHPI9574 E
Lengths less that one are not supported for array data types: dataType.
DFHPI9575 E
The length of a PICTURE cannot be found: value.
DFHPI9576 E
FIXED BINARY data types with a scaling factor of the form (p,q) with q not equal to 0 are not supported: value.
DFHPI9577 E
Precision factor factor is out of supported range: value.
DFHPI9578 E
FIXED DECIMAL data types with a scaling factor of the form (p,q) with q greater than p are not supported: value.
DFHPI9579 E
FIXED DECIMAL data types with a scaling factor of the form (p,q) with q less than 0 are not supported: value.
DFHPI9580 I
PDS member member has been replaced.
DFHPI9581 E
An unexpected exception occurred when writing to the PDS.
DFHPI9582 I
File file has been replaced.
DFHPI9583 E
The supplied WSDL contains an element with different minOccurs and maxOccurs values. This is only supported when PGMINT is set to CHANNEL or when 'INLINE-MAXOCCURS-LIMIT' is set to a higher value than maxOccurs.
DFHPI9584 E
The WSDL file contains at least one request message but the REQMEM parameter has not been set.
DFHPI9585 E
The WSDL file contains at least one response message but the RESPMEM parameter has not been set.
DFHPI9586 W
A reserved word word has been detected in the input document, it has been changed to value.
DFHPI9587 I
Program program has completed SUCCESSFULLY.
DFHPI9588 E
WSDL binding binding has no operation elements in the WSDL.
DFHPI9589 E
The supplied WSDL requires too much data for a CICS Commarea. The PGMINT parameter must be set to CHANNEL.
DFHPI9590 E
A style attribute has not been specified for WSDL operation operation.
DFHPI9591 E
No input message has been found for WSDL operation operation.
DFHPI9592 W
An expected soapAction attribute is missing for WSDL operation operation.
DFHPI9593 W
An unexpected soapAction attribute has been found for WSDL operation operation. This can only be used with SOAP version 1.1.
DFHPI9594 E
An unexpected soapAction attribute has been found for WSDL operation operation. This can only be used with SOAP version 1.1.
DFHPI9595 E
The WSDL binding contains a mixture of rpc and document style attributes. This is not supported.
DFHPI9596 E
The WSDL Binding for operation operation is missing an input message.
DFHPI9597 E
The WSDL file specifies a 'use' attribute value of value. Only literal WSDL is supported.
DFHPI9598 E
WSDL binding binding references more than one transport protocol. Only one protocol is supported.
DFHPI9599 E
WSDL binding binding is not associated with a transport protocol.
DFHPI9600 E
The WSDL file contains multiple binding elements. The BINDING parameter must be set to specify which one to use.
DFHPI9601 E
Binding element element cannot be found in the WSDL file. Only one of the following values may be specified: value.
DFHPI9602 E
WSDL binding binding is not a SOAP binding.
DFHPI9603 E
Multiple WSDL service elements exist for a single binding element. Only one is supported unless the 'WSDL-SERVICE' parameter is set.
DFHPI9604 E
File file does not contain valid XML.
DFHPI9605 E
The value of the XML encoding attribute must match that of the underlying file system. For example, the value UTF-8 may be appropriate.
DFHPI9606 E
The value of the XML encoding attribute must match that of the underlying file system. For example, the value EBCDIC-CP-US may be appropriate.
DFHPI9607 E
An unexpected error occurred whilst processing WSDL operation operation. The problem is: value.
DFHPI9608 W
WARNINGS have been generated processing file file.
DFHPI9609 I
Parameter parameter has value value.
DFHPI9610 W
Platform platform is not a supported platform for this API.
DFHPI9611 W
All content after the first ';' for line line is ignored.
DFHPI9612 E
Provider mode Web services with more than one operation must specify 'PGMINT=CHANNEL'.
DFHPI9613 E
Mapping level level is not recognized.
DFHPI9614 I
Mapping level old has been requested. The most current mapping level available is new.
DFHPI9615 E
The version of Java in use is current. The minimum version of Java required is required.
DFHPI9616 W
National characters in COBOL are assumed to be DBCS characters: line.
DFHPI9617 E
The input data contains an element with unknown length content which should be stored in a separate CONTAINER. This is only supported when PGMINT is set to CHANNEL.
DFHPI9618 E
The keyword keyword has been specified. This requires the use of LANG=PLI-ENTERPRISE.
DFHPI9619 E
Parameter parameter has been specified. It is not supported at mapping level level.
DFHPI9620 E
CCSID CCSID is not recognized.
DFHPI9621 W
CCSID CCSID is not recognized as an EBCDIC CCSID. Use of this CCSID may cause problems when the Web service is executed.
DFHPI9622 E
Invalid value specified for the parameter parameter. The length specified must be a positive integer between min and max.
DFHPI9623 E
Invalid value specified for the CHAR-VARYING parameter. Valid values are: NULL, NO or YES.
DFHPI9624 E
Invalid value specified for the FLOAT parameter. Valid values are: IEEE, HEX or HEXADEC.
DFHPI9625 E
Invalid value specified for the CHAR-VARYING parameter. Valid values are: NULL, NO, COLLAPSE or BINARY.
DFHPI9626 W
Parameter parameter has been specified but is not valid when parameter parameter2 is set. The parameter is ignored.
DFHPI9627 E
Minimum runtime level level is not recognized.
DFHPI9628 E
Parameter parameter has been specified but it is not compatible with the specified minimum runtime level.
DFHPI9629 I
The minimum runtime level required for this Web service is level.
DFHPI9630 W
The minimum runtime level required for this Web service is greater than the mapping level due to the use of the parameter parameter.
DFHPI9631 E
Field field requires a character array length of length but the largest length that can be used in language is maxlength.
DFHPI9632 E
URI uri is invalid. The reported problem is: problem.
DFHPI9633 E
Invalid value specified for the SOAPVER parameter. Valid values are: 1.1, 1.2 or ALL.
DFHPI9634 E
WSDL service element service cannot be found in the WSDL document.
DFHPI9635 E
WSDL reusable binding binding may only be used if the WSDL-SERVICE parameter is specified.
DFHPI9636 E
WSDL operation operation cannot be found.
DFHPI9637 W
One or more WSDL operations have not been processed for a provider mode Web service.
DFHPI9638 W
The minimum runtime level required for this Web service is greater than the mapping level due to the use of WSDL 2.0
DFHPI9639 E
WSDL 2.0 has been used but it is not compatible with the specified minimum runtime level.
DFHPI9640 I
This Web service should be installed into a PIPELINE that uses SOAP version soapver.
DFHPI9641 E
Unsupported message content model contentModel found whilst processing operation operation.
DFHPI9642 E
WSDL Message Exchange Pattern mep is unsupported. This pattern is specified for operation operation.
DFHPI9643 I
This Web service requires a capability implied by URI uri. It must be installed into an appropriate PIPELINE.
DFHPI9644 I
This Web service supports a capability implied by URI uri.
DFHPI9645 I
Operation operation requires a capability implied by URI uri. It must be installed into an appropriate PIPELINE.
DFHPI9646 I
Operation operation supports a capability implied by URI uri.
DFHPI9647 I
The request message for operation operation requires a capability implied by URI uri. It must be installed into an appropriate PIPELINE.
DFHPI9648 I
The request message for operation operation supports a capability implied by URI uri.
DFHPI9649 I
The response message for operation operation requires a capability implied by URI uri. It must be installed into an appropriate PIPELINE.
DFHPI9650 I
The response message for operation operation supports a capability implied by URI uri.
DFHPI9651 E
The value of parameter parameter1 is incompatible with the value of parameter parameter2.
DFHPI9652 W
A required but unsupported WSDL extensibility element has been detected. The element is of type type.
DFHPI9653 W
An unresolved PolicyReference element has been found and ignored. The URI associated with this PolicyReference is uri.
DFHPI9654 W
An unsupported Policy element has been found. The element is of type type in namespace namespace.
DFHPI9655 E
The supplied WSDL file contains a message exchange pattern of in-opt-out. This is only supported when PGMINT is set to CHANNEL.
DFHPI9656 E
The WSDL file does not contain any binding elements. There must be at least one WSDL binding.
DFHPI9657 W
The WSDL file contains elementType elements but the parameter parameter has not been specified. These elements are ignored.
DFHPI9658 E
Directory directory cannot be read.
DFHPI9659 E
Directory directory is not a valid directory.
DFHPI9660 I
WS-Policy file file has been processed.
DFHPI9661 E
File file is not a CICS WS-Policy file.
DFHPI9662 E
An exception was thrown whilst processing WS-Policy file file. The exception message is: exception.
DFHPI9663 E
Operation Operation specified a SOAP MEP of specified_MEP. The only SOAP MEP supported is supported_MEP.
DFHPI9664 E
The value specified for parameter parameter is invalid. Valid values are: values.
DFHPI9665 E
The WSDL Binding for operation Operation specifies an invalid message. MessageFound was found, but MessageExpected was expected.
DFHPI9666 E
A complexType can not contain more than one 'any' type. Problem found in type: '"typeName"'.
DFHPI9667 E
The supplied WSDL contains an 'any' or 'anyType' element. This is only supported when 'PGMINT' is set to 'CHANNEL'.
DFHPI9668 E
Invalid value specified for the XML-ONLY parameter. Valid values are: TRUE or FALSE.
DFHPI9669 E
Global XML Element element not found.
DFHPI9670 E
No Global XML Elements or Types have been processed.
DFHPI9671 E
Mismatch between WS-Addressing Action and SOAP Action for operation operation.
DFHPI9672 E
Mismatch between WS-Addressing Endpoint Reference address and port address.
DFHPI9673 E
Mismatch between WS-Addressing Endpoint Reference address and endpoint address.
DFHPI9674 E
Non-Abstract global XML Type type not found.
DFHPI9675 E
Multiple WS-Addressing Endpoint References exist.
DFHPI9676 E
The input data contains constructs that are only supported when 'PGMINT' is set to 'CHANNEL'.
DFHPI9677 E
Invalid WS-Addressing Endpoint Reference element element.
DFHPI9679 E
Invalid WS-Addressing Endpoint Reference element, 'address' element not found.
DFHPI9680 W
The MINIMUM-RUNTIME-LEVEL is less than 3.0, the WS-Addressing content in the WSDL is ignored.
DFHPI9681 E
Invalid value specified for the 'WSADDR-EPR-ANY' parameter. Valid values are: 'TRUE' or 'FALSE'.
DFHPI9682 W
Container names beginning 'DFH' should not be used in channel description documents. The problem is for container 'containerName'.
DFHPI9683 W
Bundle directory dirName already exists and may contain files that are inconsistent with the new Bundle manifest file.
DFHPI9684 W
The value of the XSDBIND parameter indicates a directory name of dirName. This is ignored as the XSDBind file is being generated into a Bundle.
DFHPI9685 E
A language structure cannot be parsed. Please ensure that the statement terminator characters are correct and that any brackets are matched.
DFHPI9686 W
Structure structureName is ignored for container containerName as the container is defined as type 'char'.
DFHPI9687 W
Unexpected text text found in columns start_column to end_column. Text is ignored.
DFHPI9688 E
Unexpected End of Line condition encountered for line 'line' of file filename.
DFHPI9689 E
Bundle directorydirName already exists and will not be replaced because OVERWRITE-OUTPUT=NO is specified.
DFHPI9690 E
File 'filename' does not contain valid JSON. The problem is: 'exception'.
DFHPI9691 E
Unsupported JSON schema. The JSON schema must describe a JSON object or JSON Array.
DFHPI9692 E
Unsupported JSON schema. A JSON schema requires a "type" keyword with single string value.
DFHPI9693 E
Invalid JSON schema. It contains an undefined JSON schema "type" of 'typevalue'.
DFHPI9694 E
Unsupported JSON schema. JSON schema "type" of 'typevalue' is not supported.
DFHPI9695 E
Unsupported JSON schema. A JSON schema "type" of "object" without a "properties" keyword is not supported.
DFHPI9696 E
Invalid JSON schema. The value of "properties" keyword must be an object.
DFHPI9697 E
Invalid JSON schema. The value of "required" keyword must be an array.
DFHPI9698 E
Unsupported JSON schema. A JSON schema "type" of "array" without an "items" keyword is not supported.
DFHPI9699 E
PICTURE strings are not supported for COMP-1 and COMP-2 fields. Problem found for field "fieldName".
DFHPI9700 E
Unsupported JSON schema. A JSON schema "type" of "object" with an "additionalProperties" keyword is only supported with value false.
DFHPI9701 E
Unsupported JSON schema. The JSON schema keyword 'keyword' is not supported.
DFHPI9702 E
Unsupported JSON schema. A JSON schema "type" of "array" with an "additionalItems" keyword is only supported with value false.
DFHPI9703 E
Invalid JSON schema. The JSON schema keyword 'keyword' requires the keyword 'required' to be present.
DFHPI9704 W
The JSON schema keyword 'keyword' is not recognized and will be ignored.
DFHPI9705 E
Invalid JSON schema. The JSON schema keyword "required" includes elements 'missing' that are not in the "properties" keyword.
DFHPI9706 E
Invalid JSON schema. The JSON schema keyword 'keyword' for an array has a bad value.
DFHPI9707 E
Invalid JSON schema. The JSON schema keywords "maximum" or "minimum" for an integer have a bad value.
DFHPI9708 W
The JSON schema format 'format' for "type" of 'type' is not recognized and will be ignored.
DFHPI9709 E
Invalid JSON schema. The JSON schema keywords "maxLength" or "minLength" for a string have a bad value.
DFHPI9710 E
Invalid JSON schema. The JSON schema keywords 'keywords' are not compatible with JSON schema "format" 'format'.
DFHPI9711 W
Possible bad integer read. The numeric value 'number' is rounded to integer 'integer'.
DFHPI9712 W
For JSON schema "type" of "number" with "decimal" format, display is limited to 18 digits.
DFHPI9713 E
For JSON schema "type" of "number" with "decimal" format, absolute values are limited to 1.0E19.
DFHPI9714 E
Unsupported JSON schema. In element 'element', the JSON schema 'type' of 'array' is not supported for 'items' keyword.'
DFHPI9715 E
Expected keyword 'keyword' missing in line 'line'.
DFHPI9716 E
Field 'name' not found for array 'array'.
DFHPI9717 E
Unsupported content found after OCCURS DEPENDING ON field 'name'.
DFHPI9718 E
Use of OCCURS DEPENDING ON requires use of DATA-TRUNCATION=ENABLED.
DFHPI9719 E
Unsupported content found after group item 'name' with OCCURS DEPENDING ON clause.
DFHPI9720 E
Unsupported keyword "UNBOUNDED" found in an OCCURS clause.
DFHPI9721 W
The parameter CCSID=1200 is not supported when assistant is used.
DFHPI9722 E
The parameter CHAR-MULTIPLIER=value is not supported in combination with CCSID=1200.
DFHPI9723 E
UTF-16 is not supported when parameter LANG=PLI-OTHER is used.
DFHPI9724 E
Type \"type\" requires a minimum mapping level of \"required-mapping-level\", but mapping level \"actual-mapping-level\" was specified.
DFHPI9725 W
A CICS abstime data type has been used. This data type can experience time-zone related data conversion errors.
DFHPI9726 E
Minimum bound "minimum" is greater than maximum bound "maximum".
DFHPI9727 E
Minimum bound "minimum" is less than zero.
DFHPI9728 E
JSON Pointers are only supported if they resolve to a local reference: \"pointer\".
DFHPI9729 E
JSON Pointer could not be resolved: \"pointer\".
DFHPI9730 E
Use of CICS Containers has been prohibited, therefore the input Schema cannot be processed using the selected input parameters.
DFHPI9800 E
The Service Registry Client has not been initialized.
DFHPI9801 E
A document with a matching name, namespace and version already exists within the registry. The publish step was not run.
DFHPI9802 E
The setting of the registry endpoint was not successful.
DFHPI9803 W
Greater than 250 custom properties have been defined; the first 250 are used.
DFHPI9804 E
When retrieving a document from a registry a fault was returned with message faultMessage.
DFHPI9805 E
An attempt to retrieve a document from a registry failed with reason failReason.
DFHPI9806 E
The WSDL file was not found at the specified location.
DFHPI9807 E
The WSDL file can not be read in the ccsid specified.
DFHPI9808 E
The WSDL file could not be used due to an IOException.
DFHPI9809 E
When querying a registry a fault was returned with message faultMessage.
DFHPI9810 E
An attempt to query a registry failed with reason failReason.
DFHPI9811 I
The document docName has been found in the registry with unique identifier docURI.
DFHPI9812 W
Multiple documents matching the query have been found. The first will be used.
DFHPI9813 E
When publishing to a registry a fault was returned with message faultMessage.
DFHPI9814 E
An attempt to publish to a registry failed with reason failReason.
DFHPI9815 I
Starting requesttype Web service request.
DFHPI9816 I
Response received for requesttype Web service request.
DFHPI9817 I
The WSRR-SERVER location is wsrrserver.
DFHPI9818 I
Custom property set with name propertyname and value propertyvalue.
DFHPI9819 I
Starting write of file filename.
DFHPI9820 E
An IOException occurred when attempting to write file filename.
DFHPI9821 E
No document matched name filename, namespace xmlns, and version version.
DFHPI9822 E
The parameter parameterName has an invalid value of value.
DFHPI9823 W
Publishing of WSDL 2.0 documents to WSRR is not supported. The document documentName has not been published.

Parent topic: CICS messages