HP NonStop XML Parser User Guide HP Part Number: 731047-001 Published: August 2013 Edition: J06.16 and subsequent J-series RVUs and H06.27 and subsequent H-series RVUs.
© Copyright 2013 Hewlett-Packard Development Company, L.P. Legal Notice Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents About this document......................................................................................4 Supported Release Version Updates (RVUs)..................................................................................4 Intended audience....................................................................................................................4 Document organization.............................................................................................................
About this document This guide contains NonStop specific installation instructions for NonStop XML Parser (T0970). It contains a brief overview of the open source products, International Components for Unicode (ICU) and Xerces-C++ libraries, used for building the NonStop XML parser. It also provides instructions on how to build and execute the samples provided with the product. Supported Release Version Updates (RVUs) This manual supports J06.16 and all subsequent J-series RVUs, and H06.
where [threadID|all] { } Braces A group of items enclosed in braces is a list from which you must choose one item. For example: -c identity {true|false} | Vertical Line A vertical line separates alternatives in a list that is enclosed in brackets or braces. For example: where [threadID|all] ... Ellipsis An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times. For example: print {objectID|objectName} ...
Publishing history Part Number Product Version Publication Date 731047-001 1.0 August 2013 HP encourages your comments HP encourages your comments concerning this document. We are committed to providing documentation that meets your needs. Send any errors found, suggestions for improvement, or compliments to docsfeedback@hp.com. Include the document title, part number, and any comment, error found, or suggestion for improvement you have concerning this document.
1 Introduction The NonStop XML parser (T0970H01) is based on the Apache Xerces-C++ open source parser, version 3.1.1, and IBM's open source International Components for Unicode (ICU), version 50.1.2. This product is available along with the existing two XML parsers listed below, which are available as two different T-numbers, each supporting a particular floating-point type.
2 Installation This chapter describes the procedure to install and verify the NonStop XML Parser on NonStop systems. Pre-requisites Before getting started, ensure that you have the following software installed on the NonStop system: • Open System Services (OSS) environment running a H06.27 or J06.
NOTE: If you do not select the Manage OSS Files option in the DSM/SCM planner interface, DSM/SCM places the PAX files in the Guardian subvolume $ISV.ZOSSUTL (where, ISV is the installation volume). You must then use the COPYOSS command to extract and place the contents of the PAX files to the OSS file system. 3. 4. 5. Copy the files to the NonStop system. Run the Build request and the Apply request on the configuration revision. Run ZPHIRNM to rename the product files.
3. Extract the PAX files using the TACL macro COPYOSS. TACL> RUN COPYOSS where, : all PAX files specified one by one, separated by space. The COPYOSS command extracts the product files from the PAX files and places them in the /usr/ tandem/xml/t0970h01 OSS directory. For more information about using the COPYOSS command, see the Open System Services Management and Operations Guide.
Figure 1 Directory structure /usr/tandem/xml/t0970h01<_XXX> icu ieee ver2 bin ICU tools used to build ICU application built with C++ library version2 and IEEE float lib ICU libraries with C++ library version2 and IEEE float sbin ICU tools used to build ICU data built with C++ library version2 and IEEE float ver3 bin ICU tools used to build ICU application built with C++ library version3 and IEEE float lib ICU libraries with C++ library version3 and IEEE float sbin ICU tools used to build ICU data
xercesc LICENSE doc License information of XERCESC Xerces-C++ open source documentation include Header files to build applications using Xerces-C++ libraries samples Xerces-C++ sample application code and their build files ieee ver2 lib Xerces-C++ libraries with C++ library version2 and IEEE float ver3 lib Xerces-C++ libraries with C++ library version3 and IEEE float bin Xerces C++ samples built with C++ library version3 and IEEE float tandem ver2 lib Xerces-C++ libraries with C++ librar
3 Sample applications The NonStop XML Parser is packaged with sample applications. You can use the sample applications to get started with the NonStop XML Parser. These sample applications demonstrate the important features of the parser. You can build all the samples simultaneously or build each sample individually. However, you must set some key environment variables before building the samples.
Perform the following steps before building the samples: • Copy the samples directory and sub-directories to an OSS location where you have read, write, and execute permissions. This location is referred to as /samples. • Set the ICUROOT and ICU_DATA environment variables by entering the following commands: OSS> export ICUROOT=/usr/tandem/xml/T0970H01/icu OSS> export ICU_DATA=$ICUROOT/share/icu/50.1.
You can execute the samples from OSS command line directly as follows: OSS> cd /samples/ OSS> ./ Building the Xerces-C++ samples The NonStop XML Parser is packaged with the following Xerces-C++ samples. These samples are available in the /samples directory, where XERCESCROOT is the /xercesc directory. Sample Function CreateDOMDocument Creates a DOM tree in memory from scratch.
The following table lists the valid values for these variables. You can define a combination of these values for building the samples. Default values are set in the defs.mk file. If you do not change these values, the default values are used. Variable Valid values FLOAT ieee, tandem. Default is ieee. VERSION 2, 3. Default is 3. ICU_SUPPORT yes, no. Default is no. PLATFORM oss, guardian. Default is oss. For guardian, ICU_SUPPORT variable must be set to no.
A Sample defs.mk file This appendix provides an example of the definition files used for building the samples. For ICU: A sample defs.
endif ifeq ($(ICU_SUPPORT),no) XLIB=xerces-c else XLIB=icuxerces-c -L$(ICUROOT)/$(FLOAT)/ver$(VERSION)/lib -licui18n -licuuc -licudata -licuio -licui18n -licuuc -lm -lput -lZRLDDLL endif ifeq ($(PLATFORM),guardian) PUTILS=GuardianTandemPlatformUtils.o PGUARD=-D_GUARDIAN_SYSTYPE=1 else PUTILS=OssTandemPlatformUtils.
Index B building ICU samples, 13 building Xerces samples, 15 D defs.
