Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
HP.com home

HP OpenVMS Systems

XML Technology for OpenVMS
Content starts here

XML C Technology for HP OpenVMS

Installation Guide and Release Notes

November 2007

 

Version 3.0, based on
Apache Xerces C Version 2.7.0 and
Apache Xalan C Version 1.10

Contents

 Before Installing XML C Technology

  Hardware Prerequisites

  Software Prerequisites

Installing XML C Technology

  Downloading the Kit

  Expanding the Kit

  Installing the Kit

 After Installing XML C Technology
Creating Applications using XML-C Version 3.0 on OpenVMS Alpha and Integrity servers

Creating Xerces C Applications

                Compiling and Linking Xerces C Applications

Creating Xalan C Applications
                Compiling and Linking Xalan C Applications

 Building the XML C Sources

 Release Notes

 Support


Before Installing XML C Technology

Hardware Prerequisites

 

XML C Technology Version 3.0 for OpenVMS is available on the OpenVMS Alpha and Integrity server platforms.

The XML C Technology for OpenVMS self-extracting file requires approximately 116,408 blocks (57 MB) of disk space for OpenVMS Alpha and 390,000 blocks (191 MB) of disk space for OpenVMS Integrity servers . Expanding the file requires an additional 173,103 (85 MB) blocks for OpenVMS Alpha and 590,000 (287 MB) blocks for OpenVMS Integrity servers .

 

To install the product, a minimum of 295,018 blocks of disk space is required for OpenVMS Alpha and 1,124,191 blocks for OpenVMS Integrity servers . Documentation and Sources require an additional of 96,881 blocks of disk space for OpenVMS Alpha and 177,454 blocks of disk space for OpenVMS Integrity servers .

 

Software Prerequisites

                For OpenVMS Alpha: 

  • HP OpenVMS Alpha Version 7.3-2 or higher

  • HP C++ Version 7.1 or higher for OpenVMS Alpha  

 

                 For OpenVMS Integrity servers:

  • HP OpenVMS Integrity servers Version 8.2 or higher

  • HP C++ Version 7.1 or higher for OpenVMS Integrity servers

 

Installing on an ODS-5 enabled disk is required. Because of long file names and directory depth issues, the installed code  base and the accompanying documentation cannot be guaranteed to function properly in a non-ODS5 environment.


Installing XML C Technology

Removing the Previous Version

 

To remove the previous installation, perform the following steps:

  • Run $ @XML-C$ROOT:[XML-C-2_0]UNINSTALL_XML-C-2_0.COM

         

             Or

  • The PCSI product installation will provide an option to delete the previous JAR based installation. It checks for XML-C$ROOT:[XML-C-2_0]UNINSTALL_XML-C-2_0.COM and prompts for removal.

Note: The XML C Technology Version 3.0 for OpenVMS kit provides you an option to retain the previous version (XML C V2.0-1) of the kit. If you want to use the previous version (i.e., XML C V2.0-1) of the kit, the XML-C$ROOT, XERCES-C$ROOT and XALAN-C$ROOT logicals must be defined to point to that kit. 

     

Downloading the Kit

The XML C Technology Version 3.0 for OpenVMS can be obtained in the following ways:

  • Software Products Library (SPL) for OpenVMS Alpha (from Q2 2008)

  • I64 Delta CDs for OpenVMS Integrity servers

  • OpenVMS website for both OpenVMS Alpha and Integrity. To download the kit, please submit the registration form.

Expanding the Kit

To expand the XML C Technology Version 3.0 for OpenVMS file, perform the following steps:

1.       Set default to a directory on the ODS-5 disk where the installation files can be extracted. You can download and extract the files to an ODS-2 disk. However, you must install the kit on an ODS-5 disk.

For example:

$ SET DEFAULT DISK:[DOWNLOADS]


2.       Enter the following command to extract relevant files from the XML C kit:

$ RUN DISK:[DOWNLOADS]XMLC-V0300-AXP.EXE (for OpenVMS Alpha)

$ RUN DISK:[DOWNLOADS]XMLC-V0300-I64.EXE (for OpenVMS Integrity servers)

 

Following is an example of expanding the self-extractable kit on OpenVMS Alpha:

On OpenVMS Alpha:

 

$ RUN XMLC-V0300-AXP.EXE

UnZipSFX 5.41 of 16 April 2000, by Info-ZIP (Zip-Bugs@lists.wku.edu)

inflating: hp-axpvms-xml_c-v0300--1.pcsi$compressed

inflating: hp-axpvms-xml_c-v0300--1.pcsi$compressed_esw

 

On OpenVMS Integrity servers:

 

$ RUN XMLC-V0300-I64.EXE

UnZipSFX 5.42 of 14 January 2001, by Info-ZIP (Zip-Bugs@lists.wku.edu)

inflating: hp-I64vms-xml_c-v0300--1.pcsi$compressed

inflating: hp-I64vms-xml_c-v0300--1.pcsi$compressed_esw

 

Installing the Kit

Note: This kit creates logicals in the system name table. Therefore, the SYSNAM privilege is required.

To install the XML C Technology for OpenVMS kit, enter the following command:

 

Installation on an OpenVMS Alpha V7.3-2 and V8.2 systems:

$ PRODUCT INSTALL XML_C /DEST=DISK:[DOWNLOADS]

The following product has been selected:
HP AXPVMS XML_C V3.0 Layered Product

Do you want to continue? [YES]

Configuration phase starting ...

You will be asked to choose options, if any, for each selected product and for any products that may be installed to satisfy software dependency requirements.

HP AXPVMS XML_C V3.0: XML Technology for OpenVMS is based on Apache Xerces C

Version 2.7.0 and Apache Xalan C Version 1.10

© Copyright 2007 Hewlett-Packard Development Company, L.P.

Hewlett-Packard Company

* This product does not have any configuration options.

Execution phase starting ...

The following product will be installed to destination:
HP AXPVMS XML_C V3.0 DISK:[DOWNLOADS.]

Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%

The supported version of CXX compiler is V7.1 or higher

XML-C$ROOT, XERCES-C$ROOT and XALAN-C$ROOT have been defined.
The following lines must be added to SYS$MANAGER:SYLOGICALS.COM so that it will be defined each time the system is rebooted.

$ define/system/nolog/trans=concealed XML-C$ROOT DISK:[DOWNLOADS.XML.]
$ define/system/nolog/trans=concealed XERCES-C$ROOT DISK:[DOWNLOADS.XML.Xerces-C-3_0.]
$ define/system/nolog/trans=concealed XALAN-C$ROOT DISK:[DOWNLOADS.XML.Xalan-C-3_0.]

Verification of the installation can be performed using the XML-C Test Procedure. To run the XML-C Test Procedure, enter the following command:

$ @XML-C$ROOT:[XML-C-3_0]XML-C-3_0-TP
...100%

The following product has been installed:
HP AXPVMS XML_C V3.0 Layered Product

$

Installation on an OpenVMS Alpha V8.3 system:  

 

$ PRODUCT INSTALL XML_C /DEST=DISK:[DOWNLOADS]
Performing product kit validation ...
%PCSI-I-VALPASSED, validation of DISK:[DOWNLOADS]HP-AXPV
MS-XML_C-V0300--1.PCSI$COMPRESSED;1 succeeded

The following product has been selected:
HP AXPVMS XML_C V3.0 Layered Product

Do you want to continue? [YES]

Configuration phase starting ...

You will be asked to choose options, if any, for each selected product and 
for any products that may be installed to satisfy software dependency 
requirements.

HP AXPVMS XML_C V3.0: XML Technology for OpenVMS is based on Apache Xerces C 
Version 2.7.0 and Apache Xalan C Version 1.10

© Copyright 2007 Hewlett-Packard Development Company, L.P.

Hewlett-Packard Company

* This product does not have any configuration options.

Execution phase starting ...

The following product will be installed to destination:
HP AXPVMS XML_C V3.0 DISK:[DOWNLOADS.]

Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%

The supported version of CXX compiler is V7.1 or higher

XML-C$ROOT, XERCES-C$ROOT and XALAN-C$ROOT have been defined.
The following lines must be added to SYS$MANAGER:SYLOGICALS.COM so that it 
will be defined each time the system is rebooted.

$ define/system/nolog/trans=concealed XML-C$ROOT DISK:[DOWNLOADS.XML.] 
$ define/system/nolog/trans=concealed XERCES-C$ROOT DISK:[DOWNLOADS.XML.Xerces-C-3_0.]
$ define/system/nolog/trans=concealed XALAN-C$ROOT DISK:[DOWNLOADS.XML.Xalan-C-3_0.]

Verification of the installation can be performed using the XML-C Test Procedure. 
To run the XML-C Test Procedure, enter the following command:

$ @XML-C$ROOT:[XML-C-3_0]XML-C-3_0-TP
...100%

The following product has been installed:
HP AXPVMS XML_C V3.0 			Layered Product

$
 

Installation on an OpenVMS Integrity servers Versions 8.2 and 8.2-1 system:

 

$ PRODUCT INSTALL XML_C /DEST=DISK:[DOWNLOADS]

 

The following product has been selected:

HP I64VMS XML_C V3.0 Layered Product

 

Do you want to continue? [YES]

 

Configuration phase starting ...

 

You will be asked to choose options, if any, for each selected product and

for any products that may be installed to satisfy software dependency requirements.

 

HP I64VMS XML_C V3.0: XML Technology for OpenVMS is based on Apache Xerces

C Version 2.7.0 and Apache Xalan C Version 1.10

 

© Copyright 2007 Hewlett-Packard Development Company, L.P.

 

Hewlett-Packard Company

 

* This product does not have any configuration options.

 

Execution phase starting ...

 

The following product will be installed to destination:

HP I64VMS XML_C V3.0 DISK:[DOWNLOADS.]

 

Portion done: 0%...10%...20%...40%...50%...60%...70%...80%...90%

 

The supported version of CXX compiler is V7.1 or higher

 

XML-C$ROOT, XERCES-C$ROOT and XALAN-C$ROOT have been defined.

 

The following lines must be added to SYS$MANAGER:SYLOGICALS.COM so

that it will be defined each time the system is rebooted.

 

$ define/system/nolog/trans=concealed XML-C$ROOT DISK:[DOWNLOADS.XML.]

$ define/system/nolog/trans=concealed XERCES-C$ROOT DISK:[DOWNLOADS.XML.Xerces-C-3_0.]

$ define/system/nolog/trans=concealed XALAN-C$ROOT DISK:[DOWNLOADS.XML.Xalan-C-3_0.]

 

Verification of the installation can be performed using the XML-C Test Procedure.
To run the XML-C Test Procedure, enter the following command:

 

$ @XML-C$ROOT:[XML-C-3_0]XML-C-3_0-TP

...100%

 

The following product has been installed:

HP I64VMS XML_C V3.0                    Layered Product

 

$

 

Installation on an OpenVMS Integrity servers V8.3 system:

 

$ PRODUCT INSTALL XML_C /DEST=DISK:[DOWNLOADS]

 

Performing product kit validation ...

%PCSI-I-VALPASSED, validation of DISK:[DOWNLOADS]HP-I64VMS-XML_C-V0300--

1.PCSI$COMPRESSED;1 succeeded

 

The following product has been selected:

HP I64VMS XML_C V3.0 Layered Product

 

Do you want to continue? [YES]

 

Configuration phase starting ...

 

You will be asked to choose options, if any, for each selected product and

for any products that may be installed to satisfy software dependency

requirements.

 

HP I64VMS XML_C V3.0: XML Technology for OpenVMS is based on Apache Xerces C Version 2.7.0 and Apache Xalan C Version 1.10

 

© Copyright 2007 Hewlett-Packard Development Company, L.P.

 

Hewlett-Packard Company

 

* This product does not have any configuration options.

 

Execution phase starting ...

 

The following product will be installed to destination:

HP I64VMS XML_C V3.0 DISK:[DOWNLOADS.]

 

Portion done: 0%...10%...20%...40%...50%...60%...70%...80%...90%

 

The supported version of CXX compiler is V7.1 or higher

XML-C$ROOT, XERCES-C$ROOT and XALAN-C$ROOT have been defined.

 

The following lines must be added to SYS$MANAGER:SYLOGICALS.COM so

that it will be defined each time the system is rebooted.

 

$ define/system/nolog/trans=concealed XML-C$ROOT DISK:[DOWNLOADS.XML.]

$ define/system/nolog/trans=concealed XERCES-C$ROOT DISK:[DOWNLOADS.XML.Xerces-C-3_0.]

$ define/system/nolog/trans=concealed XALAN-C$ROOT DISK:[DOWNLOADS.XML.Xalan-C-3_0.]

 

Verification of the installation can be performed using the XML-C Test Procedure.
To run the XML-C Test Procedure, enter the following command:

 

$ @XML-C$ROOT:[XML-C-3_0]XML-C-3_0-TP

...100%

 

The following product has been installed:

HP I64VMS XML_C V3.0                    Layered Product

 

$

   

After Installing XML C Technology

After the installation is complete, perform the following steps.

Add the following lines to SYS$MANAGER:SYLOGICALS.COM so that XML C Technology is defined each time the system is rebooted.

 

$ define/system/nolog/trans=concealed XML-C$ROOT DISK:[DOWNLOADS.XML.]

$ define/system/nolog/trans=concealed XERCES-C$ROOT DISK:[DOWNLOADS.XML.Xerces-C-3_0.]

$ define/system/nolog/trans=concealed XALAN-C$ROOT DISK:[DOWNLOADS.XML.Xalan-C-3_0.]

Optionally run the XML C Test Procedure. To run the test procedure, enter the following command:


$@XML-C$ROOT:[XML-C-3_0]XML-C-3_0-TP  

Interpreting the results of the XML C Test Procedure

The XML Test Procedure compares the output from the tests with a set of benchmarks. Because of the nature of the tests, some differences between the results and the benchmarks are to be expected. The following describes the common differences which are expected to occur.

Many of the tests display the amount of time it takes to parse the document. For example, SAXCount will output:

personal.xml: 736 ms (37 elems, 12 attrs, 134 spaces, 134 chars)

The values are the parse time, and the count of elements, attributes, ignorable whitespaces, and characters appearing in the document. The parse time will vary based on a number of factors and is not likely to match the time in the benchmark, however, the element counts should match.

Note: The results produced by this and other similar programs should never be accepted as true performance measurements.

Following is a session log containing a run of the XML C Test Procedure followed by a section showing the differences between the run log and supplied benchmark. Your log should look very similar depending on the platform.

  $ @XML-C$ROOT:[XML-C-3_0]XML-C-3_0-TP

 No test specified. All applicable tests will be run.
 Starting Xerces-C tests...
 %DCL-S-SPAWNED, process SYSTEM_11010 spawned
 %DCL-S-ATTACHED, terminal now attached to process SYSTEM_11010
 %DCL-S-RETURNED, control returned to process _TNA27:
 Starting Xalan-C tests...
 %DCL-S-SPAWNED, process SYSTEM_56454 spawned
 %DCL-S-ATTACHED, terminal now attached to process SYSTEM_56454
 %DCL-S-RETURNED, control returned to process _TNA27:
 Tests complete. Check XML-C$ROOT:[XML-C-3_0]XML-C-TP.LOG for errors.

  $ ty XML-C$ROOT:[XML-C-3_0]XML-C-TP.LOG

************

File XML-C$ROOT:[Xerces-C-3_0.samples.RESULTS]XML-XERCES-TP.OUT;1

6  21
7  ms (

******

File XML-C$ROOT:[Xerces-C-3_0.samples.BENCHMARKS]XML-XERCES-TP.BMK;1

6   12
7   ms
(

************

************

File XML-C$ROOT:[Xerces-C-3_0.samples.RESULTS]XML-XERCES-TP.OUT;1

20    9
21    ms
(

******

File XML-C$ROOT:[Xerces-C-3_0.samples.BENCHMARKS]XML-XERCES-TP.BMK;1

20    11
21    ms (

************

************

File XML-C$ROOT:[Xerces-C-3_0.samples.RESULTS]XML-XERCES-TP.OUT;1

 34            8
35           ms (

******

File XML-C$ROOT:[Xerces-C-3_0.samples.BENCHMARKS]XML-XERCES-TP.BMK;1

34   7
35   ms (

************

File XML-C$ROOT:[Xerces-C-3_0.samples.RESULTS]XML-XERCES-TP.OUT;1

48   11
49   ms (

******

File XML-C$ROOT:[Xerces-C-3_0.samples.BENCHMARKS]XML-XERCES-TP.BMK;1

48   10
49   ms(

************

************

File XML-C$ROOT:[Xerces-C-3_0.samples.RESULTS]XML-XERCES-TP.OUT;1

93    13
94    ms (

******

File XML-C$ROOT:[Xerces-C-3_0.samples.BENCHMARKS]XML-XERCES-TP.BMK;1

93    14
94    ms (

************

************

File XML-C$ROOT:[Xerces-C-3_0.samples.RESULTS]XML-XERCES-TP.OUT;1

101   14
102  ms(

******

File XML-C$ROOT:[Xerces-C-3_0.samples.BENCHMARKS]XML-XERCES-TP.BMK;1

101   13
102   ms (

************

************

File XML-C$ROOT:[Xerces-C-3_0.samples.RESULTS]XML-XERCES-TP.OUT;1

117   13
118   ms (

******

File XML-C$ROOT:[Xerces-C-3_0.samples.BENCHMARKS]XML-XERCES-TP.BMK;1

117   12
118   ms (

************

************

File XML-C$ROOT:[Xerces-C-3_0.samples.RESULTS]XML-XERCES-TP.OUT;1

125 14
126 ms (

******

File XML-C$ROOT:[Xerces-C-3_0.samples.BENCHMARKS]XML-XERCES-TP.BMK;1

125  13
126  ms (

************

Number of difference sections found: 8
Number of difference records found: 8

DIFFERENCES /IGNORE=()/MERGED=1-

    XML-C$ROOT:[Xerces-C-3_0.samples.RESULTS]XML-XERCES-TP.OUT;1-
    XML-C$ROOT:[Xerces-C-3_0.samples.BENCHMARKS]XML-XERCES-TP.BMK;1

Number of difference sections found: 0
Number of difference records found: 0

DIFFERENCES /IGNORE=()/MERGED=1-

    XML-C$ROOT:[Xalan-C-3_0.c.samples.RESULTS]XML-XALAN-TP.OUT;1-
    XML-C$ROOT:[Xalan-C-3_0.c.samples.BENCHMARKS]XML-XALAN-TP.BMK;1

$

In order to build and run all the samples provided, refer to
XML-C$ROOT:[XML-C-3_0] BuildAllSamples_Readme.txt

For documentation on XML-C, please access the Apache website at the following URLs: 

Installing the Sources and Documentation

The sources and documentation are provided in the form of a backup savesets. The "sources" restore operation requires approximately 43,617 blocks of disk space for OpenVMS Alpha and 124,190 blocks of disk space for OpenVMS Integrity servers, and the "documentation" restore operation requires approximately 53,264 blocks of disk space. Execute the following commands to restore the documentation and source files.

$ SET DEF XML-C$ROOT:[000000]
$ @XMLC_RESTORE_BACKUPS.COM

*** THIS PROCEDURE WILL LET YOU RESTORE DOCUMENTATION OR SOURCE OR BOTH ON 
TO XML-C$ROOT:[000000…] ***

1. RESTORE DOCUMENTATION ONLY
2. RESTORE SOURCES ONLY
3. RESTORE DOCUMENTATION AND SOURCES
4. EXIT

TYPE 1 OR 2 OR 3 OR 4 : 1

BACKUP RESTORE OPERATION STARTS.....

DOCUMENTATION IS RESTORED.
$ @XMLC_RESTORE_BACKUPS.COM
*** THIS PROCEDURE WILL LET YOU RESTORE DOCUMENTATION OR SOURCE OR BOTH ON 
TO XML-C$ROOT:[000000…] ***

1. RESTORE DOCUMENTATION ONLY
2. RESTORE SOURCES ONLY
3. RESTORE DOCUMENTATION AND SOURCES
4. EXIT

TYPE 1 OR 2 OR 3 OR 4 : 2

BACKUP RESTORE OPERATION STARTS.....

SOURCE IS RESTORED
$ @XMLC_RESTORE_BACKUPS.COM
*** THIS PROCEDURE WILL LET YOU RESTORE DOCUMENTATION OR SOURCE OR BOTH ON 
TO XML-C$ROOT:[000000…] ***

1. RESTORE DOCUMENTATION ONLY
2. RESTORE SOURCES ONLY
3. RESTORE DOCUMENTATION AND SOURCES
4. EXIT

TYPE 1 OR 2 OR 3 OR 4 : 3
BACKUP RESTORE OPERATION STARTS.....

DOCUMENTATION AND SOURCES ARE RESTORED
$ @XMLC_RESTORE_BACKUPS.COM
*** THIS PROCEDURE WILL LET YOU RESTORE DOCUMENTATION OR SOURCE OR BOTH ON 
TO XML-C$ROOT:[000000…] ***

1. RESTORE DOCUMENTATION ONLY
2. RESTORE SOURCES ONLY
3. RESTORE DOCUMENTATION AND SOURCES
4. EXIT

TYPE 1 OR 2 OR 3 OR 4 : 4

$

Removing XML C Technology for OpenVMS

        

            To remove XML C Technology, execute the following command:

 

            On OpenVMS Alpha:

         
 $ PRODUCT REMOVE XML_C

 

            The following output is then displayed:

 

           The following product has been selected:

        HP AXPVMS XML_C V3.0                 Layered Product

 

          Do you want to continue? [YES]

 

          The following product will be removed from destination:

          HP AXPVMS XML_C V3.0                 DISK:[DOWNLOADS.]

 

       Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
 

          The following product has been removed:
          HP AXPVMS XML_C V3.0                  Layered Product
       $

 

            On OpenVMS Integrity servers:


         
 $ PRODUCT REMOVE XML_C

 

            The following output is then displayed:

 

           The following product has been selected:

        HP I64VMS XML_C V3.0                 Layered Product

 

          Do you want to continue? [YES]

 

          The following product will be removed from destination:

          HP I64VMS XML_C V3.0                 DISK:[DOWNLOADS.]

 

       Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
 

          The following product has been removed:
          HP I64VMS XML_C V3.0                   Layered Product

       $

 

Creating Applications using XML-C Version 3.0 on OpenVMS Alpha and Integrity servers

Setting up the Environment

 

To set up the environment for creating Xerces C and Xalan C applications, perform the following steps:

 

1.  To extract the sources, refer to the Installing the Sources and Documentation section.


2. Define XERCESC as a rooted logical name to point to the top level Xerces directory as follows:
   

    $ DEFINE/JOB XERCESC XERCES-C$ROOT:[SRC.XERCESC]
   

    This is required for including the XERCES C header files.


3. Define XALANC as a rooted logical name to point to the top level Xalan directory as follows:


   
$ DEFINE/JOB XALANC XALAN-C$ROOT:[C.SRC.XALANC]


    This is required for including the XALAN C header files.


4. Define the DECC feature logical DECC$FILENAME_UNIX_REPORT as follows:
   

    $ DEFINE/JOB DECC$FILENAME_UNIX_REPORT ENABLE


5. If you are using shareable images, the logical names for XERCES_SHR and XALAN_SHR must
be defined as follows:


For OpenVMS Alpha:

 

$ DEFINE/JOB XERCES_SHR XERCES-C$ROOT:[BIN]XERCES_SHR.EXE_ALPHA

$ DEFINE/JOB XML_SHR XALAN-C$ROOT:[C.BIN]XML_SHR.EXE_ALPHA

 

For OpenVMS Integrity servers:

 

$ DEFINE/JOB XERCES_SHR XERCES-C$ROOT:[BIN]XERCES_SHR.EXE_I64

$ DEFINE/JOB XML_SHR XALAN-C$ROOT:[C.BIN]XML_SHR.EXE_I64

 

Creating Xerces C Applications

 

Independent of the API you want to use, DOM, SAX, or SAX2; your application must initialize the Xerces system before using the API, and terminate it after you are done. This is achieved by the following code:

 

#include <xercesc/util/PlatformUtils.hpp>
// Other include files, declarations, and non-Xerces-C++ initializations.
XERCES_CPP_NAMESPACE_USE
int main(int argc, char* argv[])
{
try {
XMLPlatformUtils::Initialize();
}
catch (const XMLException& toCatch) {
// Do your failure processing here
return 1;
}
// Do your actual work with Xerces-C++ here.


XMLPlatformUtils::Terminate();
// Other terminations and cleanup.
return 0;
}
XMLPlatformUtils::Initialize() and XMLPlatformUtils::Terminate must be called at
least once in each process. You are allowed to call XMLPlatformUtils::Initialize() and
XMLPlatformUtils::Terminate multiple times, but each call to
XMLPlatformUtils::Initialize() must be matched with a call to
XMLPlatformUtils::Terminate.


For details on the DOM API, refer to the DOM Programming Guide:
http://xml.apache.org/xerces-c/program-dom.html


For details on the SAX API, refer to the SAX Programming Guide:
http://xml.apache.org/xerces-c/program-sax.html


For details on the SAX2 API, refer to the SAX2 Programming Guide:
http://xml.apache.org/xerces-c/program-sax2.html

 

Compiling and Linking Xerces C Applications

 

Compile Xerces C applications on OpenVMS using the following CXX compiler qualifiers:
     - /NOMEMBER_ALIGNMENT
   - /ASSUME=NOALIGNED_OBJECTS
   - /DEFINE=__USE_STD_IOSTREAM

Statically link Xerces C applications with XERCES-C$ROOT:[LIB]XERCES.OLB
Dynamically link Xerces C applications with the Xerces C shareable image, refer to XMLC$ROOT:[XML-C-3_0]   create_shareable_readme.txt


Creating Xalan C Applicati