• SGI
• SUN
• WIN
• Linux

Description

The conv_stf_2.5.x_To_3.0.3 application will convert a 2.5, 2.5.2, and 2.5.2a STF transmittals to 3.0.3 transmittals. The application has the following usage format:

Usage

conv_stf_2.5.x_to_3.0.3 [options] -t <2.5.x_stf_file> -f <3.0.3_stf_file>

Where:

-t <2.5.x_stf_file>
Specifies the path and the root file name of the input 2.5.x STF transmittal to be converted.
.
-f <3.0.3_stf_file>
Specifies the path and the root file name of the resulting 3.0.3 STF transmittal.

Options

-r : Remove 2.5.x files as they are converted.

-u <URN name> : The URN name for the new 3.0.3 transmittal.

-<number> : Convert only this number of 2.5.x STF files.

-c : Continue converting from a previous run with the -<number> option.

-v : Version. Prints the version number of this executable.

-fix <3.0.3_stf_file> : Repair endian problem with data tables in transmittals converted with version 1.0 of this converter.

Only the -t and -f arguments are required. (The exeption is the -fix option which is described above.) The arguments may appear in any order on the command line. The -t and -f filenames may be the same only if -r is also given. In this case the 3.0.3 transmittal is written to a temporary directory and until all files are converted. The converter will not overwrite existing 3.0.3 files. If -<number> option only creates a partial transmittal which is not valid until the converter is run again with the -c option. The -c and -<number> options may be used together to convert a range of STF files from a previous -<number> run to the new -<number>. The converter uses a statefile to track the current file being converted. If this statefile exists without the -c option then you must either include the -c option or remove the statefile and any existing STF files. The -c option will also not work without a statefile created from a previous run. The -c option will also work if a previous run was killed or crashed for some reason. The 3.0.3 STF implementation automatically compresses Data Tables but the converter does not support this. Uncompressed 2.5.x Data Tables are not automatically compressed during the conversion process to 3.0.3. Invalid Data in the 2.5.x transmittals is passed thru. A few field values in 2.5.x which were not previously caught by the 2.5.x checker program will be flagged by the 3.0.3 syntax checker. The resulting 3.0.3 transmittal will have one more file than the original 2.5.x transmittal.

Examples

Here are some examples of how to execute this program and the expected results:

conv_stf_2.5.x_to_3.0.3 -t /transmittals/2.5_stf/stf_belle.stf -f /transmittals/3.0_stf/stf_belle.stf -u "urn:sedris:example_belle" 

This will create a new stf_belle.stf in /transmittals/3.0_stf with a URN name of "urn:sedris:example_belle".

conv_stf_2.5.x_to_3.0.3 -3 -t /transmittals/2.5_stf/stf_moba.stf -f /transmittals/3.0_stf/stf_moba.stf -r 

This will convert the first 3 files of the transmittal stf_moba.stf in /transmittals/2.5_stf and delete them after they are converted. A partial transmittal is created in /transmittals/3.0_stf

conv_stf_2.5.x_to_3.0.3 -c -t /transmittals/2.5_stf/stf_moba.stf -f /transmittals/3.0_stf/stf_moba.stf -r 

This will finish converting the transmittal stf_moba.stf in /transmittals/2.5_stf and delete the rest of the transmittal. The completed 3.0.3 stf_moba.stf transmittal is created in /transmittals/3.0_stf.

conv_stf_2.5.x_to_3.0.3 -fix /transmittals/3.0_stf/stf_moba.stf 

This will change the endian-ness of the data table data in the 3.0.1 stf.

If you have any questions or comments regarding the STF Converter, please contact: help@sedris.org.