User`s guide

B: DLI and TSI Configuration Process
DC 900-1343D 63
uration file in the same directory as the location of the text file (unless a different
path is supplied with the optional filename). If the optional filename is not sup-
plied, the binary file is given the same name as your TSI text configuration file
plus a
.bin extension.
tsicfg TSI-text-configuration-filename [TSI-binary-configuration-filename]
VMS example:
tsicfg ddcmpaltcfg
UNIX example: freeway/client/op-sys/bin/tsicfg ddcmpaltcfg
NT example: freeway\client\op-sys\bin\tsicfg ddcmpaltcfg
5. From the freeway/client/test/ddcmp (or the freeway/client/nt_dlite/ddcmp)
directory, execute
dlicfg with the text file from Step 2 as input. This creates the
DLI binary configuration file in the same directory as the location of the text file
(unless a different path is supplied with the optional filename). If the optional
filename is not supplied, the binary file is given the same name as your DLI text
configuration file plus a
.bin extension.
dlicfg DLI-text-configuration-filename [DLI-binary-configuration-filename]
VMS example:
dlicfg ddcmpaldcfg
UNIX example: freeway/client/op-sys/bin/dlicfg ddcmpaldcfg
NT example: freeway\client\op-sys\bin\dlicfg ddcmpaldcfg
Note
You must rerun dlicfg or tsicfg whenever you modify the text
configuration file so that the DLI or TSI functions can apply the
changes. On all but VMS systems, if a binary file already exists with
the same name in the directory, the existing file is renamed by
appending the
.BAK extension. If the renamed file duplicates an
existing file in the directory, the existing file is removed by the con-
figuration preprocessor program.