Before continuing, do the following on your OS/390 UNIX system:
Note: You may need to modify the following steps to match your development environment.
- To compile applications domxml.cpp and saxxml.cpp, do the following:
- Enter the following export commands:
- export _C89_CCMODE=1
- export _CXX_INCDIRS="tinclude xinclude"
where tinclude is the full directory path of the TPF system header files and xinclude is the
full directory path of the XML4C header files*.
- export _C89_INCDIRS="$_CXX_INCDIRS"
- export _CXX_INCLIBS=""
- export _C89_INCLIBS=""
- export _CXX_CSYSLIB=""
- export _C89_CSYSLIB=""
- export _CXX_CXXSUFFIX="cpp"
- export _CXX_OPTIONS="-W 0,langlvl(extended)
-W0,NOSTART -D_POSIX_SOURCE -Uerrno -DTPF"
(Enter the entire command as a single line.)
- Enter export to verify that the environment variables defined in step 1 were set correctly.
- Enter c++ -c domxml.cpp to start the compiling process. This step creates a .o file for the DOM
application.
- Enter c++ -c saxxml.cpp to start the compiling process. This step creates a .o file for the SAX
application.
- Link each application and its associated .o file with CSTRTD(40) and CGETOP40.pds. You must include the following definition side-decks:
- Create a loadset for each application (domxml.cpp and saxxml.cpp).
Once you have completed these steps, you are ready to continue.
* Note: The XML4C header files needed for applications accessing XML data should have been copied to
an accessible directory when APAR PJ28176 was installed on your TPF 4.1 system. These header files
must retain their names and the directory structure in which they reside. For more information
about the header files, see the migration information in either TPF Migration Guide: Program Update Tapes or the TPF XML User's Guide. See your system
installer to find out where the header files are on your TPF 4.1 system and use that path name
for the xinclude variable.
