Some XML Extender sample programs might have the same name as other installed 2programs. Accidentally invoking another program with the same name as an 2XML Extender sample program can damage your XML files. The following list 2shows the old XML Extender sample program names as well as new replacement 2program names that are less likely to cause conflicts. Make sure you use 2the new sample program names instead of the old ones to prevent damaging your 2XML files.
2 2Old Program (Do not use) | 2New Program (Use) | 2
---|---|
insertx.exe | 2dxxisrt.exe | 2
retrieve.exe | 2dxxretr.exe | 2
retrieve2.exe | 2dxxretr2.exe | 2
retrievec.exe | 2dxxretrc.exe | 2
shred.exe | 2dxxshrd.exe | 2
tests2x.exe | 2dxxgenx.exe | 2
tests2xb.exe | 2dxxgenxb.exe | 2
tests2xc.exe | 2dxxgenxc.exe | 2
Old Program (Do not use) | 2New Program (Use) | 2
---|---|
insertx | 2dxxisrt | 2
retrieve | 2dxxretr | 2
retrieve2 | 2dxxretr2 | 2
retrievec | 2dxxretrc | 2
shred | 2dxxshrd | 2
tests2x | 2dxxgenx | 2
tests2xb | 2dxxgenxb | 2
tests2xc | 2dxxgenxc | 2
The source code (.sqx files) for the executables listed previously are 2located in the samples\db2xml\c directory of your installation. 2The source files are still labeled with their old names. If you make changes 2to the source code, copy your newly compiled executables (with the old names) 2to the sqllib\bin directory.
2On Windows platforms, you must make an additional copy, 2rename it with its new name above, and copy it to the bin directory. Both 2copies replace the existing files in the bin directory. For example, after 2compiling your new version of shred.exe, you need to make two copies and replace 2the files in the bin directory: one labeled shred.exe and the other renamed 2dxxshrd.exe.
2On Linux and UNIX platforms, you need only to replace the file with the old 2name with your newly compiled version. If you create new executable files 2from these samples, you must copy the new files from the \SQLLIB\samples\db2xml\c\ directory into the \SQLLIB\bin\ directory, and then make 2an additional copy, renaming them according to the previous table.
[ Top of Page |Previous Page | Next Page | Contents ]