A fix is available
APAR status
Closed as program error.
Error description
Customer is receiving an SVCDUMP on the message, DFHPI0002 A severe error (code X'0F09') has occurred in module DFHPIII. The trace shows the following, PIII *EXC* INTERNAL_ERROR GET_CONTAINER_SET,EXCEPTION, CCSID_IGNORED,BIT, MEME ENTRY SEND_MESSAGE 2,PI0002 . The problem here is that the application has issued the PUT CONTAINER without specifying DATATYPE(CHAR) or CCSID(nnn). This causes the container to default to DATATYPE(BIT). DFHPIII requires that containers used to hold raw XML data have DATATYPE(CHAR). . This error situation should actually just issue an exception trace, message and either send a SOAP fault back to the client or return an appropriate RESP value to the application. The code to do this is in place in DFHPIII but an earlier check for an exception response on the GET_CONTAINER_SET call has decided to take a system dump. Additional Symptom(s) Search Keyword(s): KIXREVJXD
Local fix
Specify DATATYPE(CHAR) or CCSID(nnn) in PUT CONTAINER
Problem summary
**************************************************************** * USERS AFFECTED: ALL CICS USERS * **************************************************************** * PROBLEM DESCRIPTION: DFHPIII issues an internal error with a * * system dump, when raw xml data is * * received in BIT mode. * **************************************************************** * RECOMMENDATION: * **************************************************************** The xsd:any and xsd:anyType support added by PK59794 is being used. The data for elements of these types is passed to and from the application as raw XML in a container. This container is required to be in CHAR mode. The application has issued a PUT CONTAINER without specifying DATATYPE(CHAR) or CCSID(nnn). The container therefore defaults to DATATYPE(BIT). When DFHPIII attempts to get the contents of the container it gets an exception response of PGCR_EXCEPTION and a reason of PGCR_CCSID_IGNORED. There isn't any specific code to handle this exception so it is treated as a disaster and message DFHPI0002 code x'0F09' gets issued along with a system dump. This is too severe an action for a simple application error.
Problem conclusion
DFHPIII has been changed to detect when a raw XML container has DATATYPE(BIT) instead of DATATYPE(CHAR) and issue message DFHPI1008 along with an exception trace entry.
Temporary fix
FIX AVAILABLE BY PTF ONLY
Comments
APAR Information
APAR number
PK66672
Reported component name
CICSTS V3 Z/OS
Reported component ID
5655M1500
Reported release
500
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-05-27
Closed date
2008-08-13
Last modified date
2008-09-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK38972
Modules/Macros
DESPIII DFHPIII
Fix information
Fixed component name
CICSTS V3 Z/OS
Fixed component ID
5655M1500
Applicable component levels
R500 PSY UK38972
UP08/08/21 P F808
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.2","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.2","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 September 2008