User guide

148 DC 900-1338I
Protocol Software Toolkit Programmer Guide
3. If you have a UNIX or Windows NT system, skip this step. If you have a VMS sys-
tem, run the
makefc.com command file from the [FREEWAY.CLIENT.TEST.SPS]
directory to create the foreign commands used for dlicfg and tsicfg.
@MAKEFC <tcp-sys>
where <tcp-sys> is your TCP/IP package:
MULTINET (for a Multinet system)
TCPWARE (for TCPware system)
UCX (for a UCX system)
VMS example:
@MAKEFC UCX
4. For a Freeway server, go to the freeway/client/test/sps directory and execute tsicfg
with the text file from Step 1 as input. This creates the TSI 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 TSI text configuration file plus a
.bin
extension.
tsicfg TSI-text-configuration-filename [TSI-binary-configuration-filename]
UNIX example:
freeway/client/op-sys/bin/tsicfg spsaltcfg
VMS example: tsicfg spsaltcfg
NT example: freeway\client\op-sys\bin\tsicfg spsaltcfg
5. From the freeway/client/test/sps (or the freeway/client/nt_dlite/sps) directory, exe-
cute
dlicfg with the text file from Step 2 as input. This creates the DLI binary con-
figuration 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]
UNIX example:
freeway/client/op-sys/bin/dlicfg spsaldcfg