IBM Support

PH27483: AN MTOM MULTI-PART MESSAGE SENT BY CICS TO FILENET RESULTS IN FNRCT0057E OR HTTP 500 INTERNAL SERVER ERROR IN FILENET.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • CICS sent MTOM / XOP message to Filenet P8. This resulted in
    one of two errors:
    FNRCT0057E: TRANSPORT_WSI_MULTIPART_PROBLEM: A multipart SOAP
        request or response could not be deserialized. The multipart
        body was missing a body part with this Content-ID:
                                  (note the blank Content-ID above).
    or
    HTTP/1.1 500 Internal Server Error..
    ..
    Error 500: com.filenet.api.exception.EngineRuntimeException:
    FNRCE0066E: E_UNEXPECTED_EXCEPTION: An unexpected exception
    occurred. Message was: null..
                                                                   .
    From the CICS aux trace for example the SO 0201 SOCK ENTRY
    - FUNCTION(SEND)
    This showed no 'Start' parameter in the MTOM/XOP message from
    CICS. The 'Start' parameter itself is optional. As it is not
    present the 'root' is the first body part in the
    multipart/related entity.
                                                                   .
    If Start is given, then it is the content-ID of the compound
    object's root.
    Filenet was expecting the 'Start' to be given, and so gave an
    error for content-ID when it wasn't; although content-ID is
    shown in the first body part, as illustrated below.
    Trace entry example:
    SO 0201 SOCK  ENTRY - FUNCTION(SEND)
    ..
    POST /wsi/FNCEWS40MTOM HTTP/1.1..Host: xx.xx.xxx.xx:xxxx..
    User-Agent: IBM_CICS_Transaction_Server/5.4.0(zOS)..
    ..
    Content-Type: multipart/related;
    type="application/xop+xml";
    boundary=MimeBoundary-etc
    start-info="application/soap+xml;
    action=\"http://www.filenet.com/ns/fnce/2006/11/ws/
           MTOM#ExecuteChanges\""..
    Accept-Encoding:  ....
    --MimeBoundary-etc
    Content-Type: application/xop+xml;
    charset=UTF-8;
    type="application/soap+xml;
    action=\"http://www.filenet.com/ns/fnce/2006/11/ws/
           MTOM#ExecuteChanges\""..
    Content-Transfer-Encoding: 8bit..
    Content-ID: <mime-root@cicsts>....
    etc
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: SOAP request sent by CICS using         *
    *                      MTOM/XOP fails to be processed by       *
    *                      Filenet P8 server.                      *
    ****************************************************************
    CICS is acting as a web service requester.  An INVOKE SERVICE
    command is issued to send a request to a remote Filenet P8
    server.  Due to the request containing a large binary element
    the CICS PIPELINE has been configured to use MTOM/XOP when
    sending the request.
    
    The multipart message that CICS creates does not specify the
    start parameter.  That parameter would be used to indicate the
    root message part.  The start parameter is optional and the
    server should use the first message part as the root in this
    case.
    
    When the Filenet P8 server receives the request from CICS it
    ends up trying to locate a message part with a blank Content-ID.
    It does not find a matching part so returns a SOAP Fault back to
    CICS containing FNRCT0057E: TRANSPORT_WSI_MULTIPART_PROBLEM.
    

Problem conclusion

  • DFHPIMM has been changed to always specify the start parameter
    in multipart messages.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH27483

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    100

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-07-15

  • Closed date

    2020-08-12

  • Last modified date

    2020-09-01

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UI71026 UI71027 UI71028

Modules/Macros

  • DFHPIMM
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R100 PSY UI71028

       UP20/08/13 P F008

  • R200 PSY UI71027

       UP20/08/13 P F008

  • R300 PSY UI71026

       UP20/08/13 P F008

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"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.4","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
02 September 2020