IBM Support

PM74124: PL/I XML2LS conversion fails with message IRZ0966S while parsing base64Binary content.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Headline/Abstract
    ***************************************************************
    Rational Developer for System z (RDz) PL/I XML2LS conversion
    fails with message IRZ0966S while parsing base64Binary content.
    
    APAR Error Description
    ***************************************************************
    Rational Developer for System z - RDz - v8.5.0
    
    The generated size of the converter content buffer does not
    accomodate the fact that data is much longer when encoded in
    base64. For instance, the length of the character content of an
    XML element or attribute of type xsd:base64Binary with
    maxLength='256' could be up to 344
    [(ceil(256/3) * 4) = (86 * 4) = 344]
    The expanison factor is l = (ceil(n/3) * 4)
    where n is the length of the data to be encoded, and l is its
    encoded length.
    
    ***************************************************************
    Local fix:
    None
    

Local fix

Problem summary

  • L/I Compiled XML Conversion establishes limits
    (CONTENT_TXT_MAXLEN, CONTENT_TXT_MAXLEN) on the length of the
    XML element and XML attribute content that can be processed.
    These limits are based on the maximum length of each mapped
    language structure member.  For example, if the largest, mapped,
    member of a PL/I structure is declared as "field-1 char (256)",
    the respective converter will issue message IRZ0966S if the
    content of any mapped XML element or XML attribute exceeds 256
    characters (the 5 predefined entities count as one character).
    However, in the case of a base64Binary mapping, PL/I Compiled
    XML Conversion may compute an insufficient limit on the length
    of XML element and XML attribute content causing condition
    IRZ0966S to be incorrectly raised during XML2LS conversion.
    

Problem conclusion

  • L/I Compiled XML Conversion has been corrected to establish
    limits that take into account the 4:3 expansion of data when it
    is encoded in base64.
    
    The problem listed in this APAR has been resolved with
    IBM Rational Developer for System z V8.5.1 Refresh Pack which
    is available from the Recommended Fixes support download page:
    http://www-1.ibm.com/support/docview.wss?rs=2294&uid=swg27006335
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM74124

  • Reported component name

    RATL DEV FOR SY

  • Reported component ID

    5724T0700

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-10-02

  • Closed date

    2012-12-04

  • Last modified date

    2012-12-04

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

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

Fix information

  • Fixed component name

    RATL DEV FOR SY

  • Fixed component ID

    5724T0700

Applicable component levels

  • R850 PSY

       UP



Document information

More support for: Rational Developer for System z

Software version: 7.5

Reference #: PM74124

Modified date: 04 December 2012