NonStop XML Parser User Guide

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.
Valid valuesVariable
ieee, tandem. Default is ieee.FLOAT
2, 3. Default is 3.VERSION
yes, no. Default is no.ICU_SUPPORT
oss, guardian. Default is oss. For guardian, ICU_SUPPORT variable must be set
to no.
PLATFORM
NOTE:
• The value of each variable in the defs.mk file is case sensitive.
• There is no support for ICU on guardian platform.
After setting the required values, execute the following command to build all samples from the
<xercesc_user_location>/samples directory:
OSS> make
To build a particular sample, use the following command:
OSS> make <sample_name>
NOTE: When building an executable on Guardian, you must not return a non-zero value from
the main() function as it results in abend. For more information, see the Guardian Procedure Calls
Reference manual and the CRE Programmer's Guide.
Running the Xerces-C++ samples
When you build the samples, the executable files are created in the
<xercesc_user_location>/samples directory. If you have built OSS executable samples,
you can execute them from the OSS command line directly as follows:
OSS> ./<sample exe file>
If you have built Guardian executable samples, then perform the following steps:
1. Copy the executable to the Guardian location in binary mode.
OSS> cp <sample exe file> /G/<volname>/<subvolname>/<filename>
NOTE: Guardian does not accept more than 8 characters as file name.
If there are other data files such as xml and dtd, you must copy them as well.
2. Go to the Guardian prompt, change the file code to TNS/E executable.
TACL> fup alter <filename>, code 800
3. Execute the sample.
TACL> run <filename>
16 Sample applications