PM12080: DOC NEW XML GENERATE EXCEPTION CODES ARE MISSING FROM ENTERPRISE COBOL 4.X MIGRATION GUIDE DOCUMENTATION.

APAR status

• Closed as documentation error.

Error description

• The user received XML GENERATE ... ON EXCEPTION code 417
  after moving to Enterprise COBOL 4.x.
  Even though new XML GENERATE exception codes 414, 416, 417
  and 418 are listed in Appendix D of the Enterprise COBOL for
  zOS V4R1 Programming Guide (SC23-8529-00) and exception code
  415 is added to the Enterprise COBOL for zOS V4R2 Programming
  Guide (SC23-8529-01), there is no mention of these changes in
  the related Enterprise COBOL Runtime and Migration Guides
  (GC23-8527-00 and GC23-8527-01).
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of Enterprise COBOL V4 programs with   *
  *                 XML GENERATE statements.  There are 4 new    *
  *                 exception codes for XML GENERATE in V4R1     *
  *                 and 1 new XML GENERATE exception code in     *
  *                 Enterprise COBOL V4R2.                       *
  *                                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: New exception codes for Enterprise      *
  *                      COBOL Version 4 are missing from the    *
  *                      COBOL Migration Guide.                  *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION: Use the updated Migration Guide text below   *
  *                                                              *
  ****************************************************************
  The user received XML GENERATE ... ON EXCEPTION code 417
  after moving to Enterprise COBOL Version 4.
  Even though new XML GENERATE exception codes 414, 416, 417
  and 418 are listed in Appendix D of the Enterprise COBOL for
  zOS V4R1 Programming Guide (SC23-8529-00) and exception code
  415 is added to the Enterprise COBOL for zOS V4R2 Programming
  Guide (SC23-8529-01), there is no mention of these changes in
  the related Enterprise COBOL Compiler and Runtime Migration
  Guides (GC23-8527-00 and GC23-8527-01).
  

Problem conclusion

• The Enterprise COBOL for zOS V4R2 Compiler and Runtime Migration
  Guide (GC23-8527-01) will be changed as follows.
  
  Add a bullet to the lead-in paragraph of Chapter 20,
  "Upgrading to Enterprise COBOL Version 4 Release 2".
  
  The bullet should say:
  - Upgrading Enterprise COBOL programs that have XML GENERATE
    statements.
  
  Then add a new section in this chapter, with this heading:
  
  Upgrading Enterprise COBOL programs that have XML GENERATE
  statements.
  
  Enterprise COBOL V4R1 introduced four new XML GENERATE exception
  codes when compared to Enterprise COBOL Version 3, and
  Enterprise COBOL V4R2 introduced one new XML GENERATE exception
  code compared to V4R1.  Programs that use these exception codes
  might have to be changed to migrate to Enterprise COBOL V4R2.
  
  
  The XML GENERATE exception codes that were added in Enterprise
  COBOL Version 4 Release 1 are:
  416 The XML namespace identifier contained invalid XML
      characters.
  417 Element character content or an attribute value contained
      characters that are illegal in XML content. XML generation
      has continued, with the element tag name or the attribute
      name prefixed with "hex." and the original data value
      represented in the document in hexadecimal.
  418 Substitution characters were generated by encoding
      conversion.
  419 The XML namespace prefix was invalid.
  
  
  The XML GENERATE exception code that was added in Enterprise
  COBOL Version 4 Release 2 is:
  415 The receiver was national, but the encoding specified for
      the document was not UTF-16.
  

Temporary fix

Comments

APAR Information

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

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

Fix information

Applicable component levels