gtpm2m3fMigration Guide: Program Update Tapes

XML4C Parser 3.5.1 (APAR PJ28176)

The following section discusses the migration considerations for XML4C parser 3.5.1.

Prerequisite APARs

XML4C Parser 3.5.1 (APAR PJ28176) obsoletes the version of the parser that was ported for XML parser (APAR PJ27634) on PUT 14. As a result, only the pieces of APAR PJ27634 that are TPF-specific are considered prerequisites for APAR PJ28176:

Functional Overview

XML4C parser 3.5.1 allows your applications to read (parse) and write Extensible Markup Language (XML) data on the TPF 4.1 system. XML is a markup language that combines the power of Standard Generalized Markup Language (SGML) and the simplicity of Hypertext Markup Language (HTML). XML allows you to mark up data based on what information the data contains rather than on how it is to be rendered. Data marked up in XML is easy to share across various platforms and across various companies. For more information about the XML specification, go to http://www.w3.org/.

XML4C parser 3.5.1 is the XML Parser for C++ (XML4C) Version 3.5.1 ported to the TPF 4.1 system. The parser is XML Version 1.0 compliant and allows TPF 4.1 applications written in C++ language to do the following:

In addition, the parser fully implements the ability to use namespaces in support of unique tagging structures.

Applications on the TPF 4.1 system interact with XML documents that are in the file system, coming in through standard input (stdin) or residing in memory. This interaction is made possible through application programming interfaces (APIs) specified by either the DOM or SAX specifications and can be either nonvalidating or validating against a schema (DTD or XML Schema). The API definitions are contained in a set of header files that application programmers will need to have in their #include (or search) path. See General Use C/C++ Language Header Files for more information about these header files.

TPF information for XML4C parser 3.5.1 is exclusively online. The browser-readable HTML files are available on IBM TPF Product Information Center, which is the CD-ROM included with TPF 4.1 PUT 16, or on the TPF Web site (http://www.ibm.com/tpf/pubs/tpfpubs.htm). See Publication Changes for more information about XML4C parser 3.5.1 written information.

Architecture

IBM contributed the XML4C parser to the Apache XML Project (http://xml.apache.org) as open source in November 1999. XML Parser for C++ (XML4C) Version 3.5.1 is based on Xerces-C Version 1.5.0 and is fully compliant with the Unicode 3.0 specification. While the Apache Xerces-C parser can be updated by the open source community, the XML4C parser is maintained only by IBM and may differ slightly from the Xerces-C parser.

Operating Environment Requirements and Planning Information

There are none.

Interface Changes

The following section summarizes interface changes.

C/C++ Language

The following section summarizes C/C++ language changes. This information is presented in alphabetic order by the type of C/C++ language information. See the TPF C/C++ Language Support User's Guide and TPF Application Programming for more information about the C/C++ language.

Build Scripts

There are no changes.

Dynamic Load Module (DLM) Stubs

There are no changes.

General Use C/C++ Language Header Files

General use means these header files are available for your use.

The ported XML4C parser code provides a set of header files (or #include files) that are needed for applications that use the XML4C parser to access XML data. The header files are included with XML4C parser 3.5.1 and must be copied into a directory accessible by application programmers. (Application programmers are instructed to concatenate the directory that contains these header files in their #include path.)

When copying the XML4C header files to your TPF 4.1 system, ensure that you first remove any header files you copied with the XML parser (APAR PJ27634) on PUT 14 and that you retain the directory structure in which the XML4C parser 3.5.1 (APAR PJ28176) header files reside. The following shows the directory structure for the XML4C parser 3.5.1 files (note that there are many header files in each directory):

+--------------------------------------------------------------------------------+
|include                                                                         |
|    |- dom                                                                      |
|    |- framework                                                                |
|    |- internal                                                                 |
|    |- parsers                                                                  |
|    |- sax                                                                      |
|    |- sax2                                                                     |
|    |- util                                                                     |
|        |- regx                                                                 |
|        |- Compilers                                                            |
|        |- MsgLoaders                                                           |
|            |- InMemory                                                         |
|        |- Platforms                                                            |
|            |- TPF                                                              |
|        |- Transcoders                                                          |
|            |- IconvTPF                                                         |
|    |- validators                                                               |
|        |- common                                                               |
|        |- datatype                                                             |
|        |- schema                                                               |
|        |- DTD                                                                  |
+--------------------------------------------------------------------------------+

See Publication Changes for more information about XML4C parser 3.5.1 information. (For specific information about the XML4C header files, open XML on TPF: An Online User's Guide and click XML4C Version 3.5.1 Documentation.)

Note:
The XML4C header files cannot reside in a partitioned data set (PDS) because the first eight characters of all header files that reside in a PDS must be unique, and the XML4C header file names do not follow this rule. To ensure that your application programs work, put the header files into a hierarchical file system (HFS); these header files cannot be renamed and each must reside in its native directory in the HFS.

Implementation-Specific C/C++ Language Header Files (IBM Use Only)

There are no changes.

Library Interface Scripts

There are no changes.

Link-Edited Modules

Table 1247 summarizes changes to the link-edited modules shipped by IBM, which should go into a data set with attributes DCB=(RECFM=U,LRECL=80,BLKSIZE=1200). This information is presented in alphabetic order by the name of the link-edited module.

Table 1247. Changes to Link-Edited Modules for XML4C Parser 3.5.1

Link-Edited Module New, Changed, or No Longer Supported? Description of Change
CXML Changed Updated for XML4C Parser 3.5.1.

Members

There are no changes.

Object Code Only (OCO) Stubs

There are no changes.

Configuration Constant (CONKC) Tags

There are no changes.

Control Program Interface (CINFC) Tags

There are no changes.

Copy Members

There are no changes.

Fixed File Records

There are no changes.

Macros

There are no changes.

Segments

There are no changes.

System Equates

There are no changes.

User Exits

There are no changes.

Functional and Operational Changes

There are no changes.

Performance or Tuning Changes

There are no changes.

Storage Considerations and Changes

There are no changes.

System Initialization Program (SIP) and System Generation Changes

There are no changes.

Loading Process Changes

There are no changes.

Online System Load Changes

There are no changes.

Publication Changes

Table 1248 summarizes changes to the publications in the TPF library. This information is presented in alphabetic order by the publication title. See the TPF Library Guide for more information about the TPF library.

Table 1248. Changes to TPF Publications for XML4C Parser 3.5.1

Publication Title Softcopy File Name Description of Change
TPF Migration Guide: Program Update Tapes GTPMG206 Updated with migration considerations for XML4C parser 3.5.1.
TPF C/C++ Language Support User's Guide GTPCLU0G Updated the list of classes that are supported by XML Parser for C++ (XML4C) Version 3.5.1 but not documented in the TPF C/C++ Language Support User's Guide.
XML User's Guide Not Applicable Updated for the delivery of TPF information on XML4C parser 3.5.1.

This guide was delivered previously as browser-readable HTML files only, called XML on TPF: An Online User's Guide. The contents of this guide have been changed slightly so that you can view XML information in PDF as well as in HTML format. From the IBM TPF Product Information Center, do one of the following:

  • Click Tasks -> XML4C Parser 3.5.1 to view task-oriented information such as a short tutorial that walks you through a real example of XML on TPF, step-by-step instructions for using sample programs included with the ported source code, and migration information.
  • Click Concepts -> XML4C Parser 3.5.1 to view conceptual information about XML on TPF, including a list of resources and the documentation included with the ported source code.
  • Click Full Library and select XML User's Guide to view the information in either HTML or PDF.

Host System Changes

There are no changes.

Application Programming Interface (API) Changes

XML4C parser 3.5.1 supports the DOM and SAX specifications, which are each comprised of several APIs. These APIs are supported on the TPF 4.1 system but are not documented in the library. Some of the APIs included with this version of the parser may be different than those included with the original port of the XML parser (APAR PJ27634) on PUT 14. The information for the APIs was included with the ported code for XML4C parser 3.5.1 and is available in XML on TPF: An Online User's Guide. See Publication Changes for more information.

Database Changes

There are no changes.

Feature Changes

There are no changes.

Installation Validation

There are no changes.

Migration Scenarios

Use the following procedure to install XML4C parser 3.5.1 on your TPF 4.1 system:

  1. Unpack program update tape (PUT) 16, which contains APAR PJ28176 for XML4C parser 3.5.1. See TPF Memo to Licensees for more information about unpacking the tape.
  2. Copy the XML4C C/C++ language header files into an HFS so that they are available to application programmers. The directory structure must be maintained and any header files copied for XML parser (APAR PJ27634) on PUT 14 must be removed. See General Use C/C++ Language Header Files for more information about the XML4C header files.
  3. Load the CXML link-edited module listed in Table 1247.
  4. IPL your TPF 4.1 system.

Additional Information