User`s guide

5: ADCCP NRM Link Configuration Using dlicfg
DC 900-1317J 101
UNIX example: freeway/client/op-sys/bin/tsicfg nrmaltcfg
NT example: freeway\client\op-sys\bin\tsicfg nrmaltcfg
5. From the freeway/client/test/nrm directory, execute dlicfg with the text file from
Step 2 as input. This creates the DLI binary configuration file in the same direc-
tory 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 nrmaldcfg
UNIX example: freeway/client/op-sys/bin/dlicfg nrmaldcfg
NT example: freeway\client\op-sys\bin\tsicfg nrmaldcfg
Note
Yo u m u s t r e r u n dlicfg or tsicfg whenever you modify the text con-
figuration 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.
6. If you have a UNIX system, move the TSI and DLI binary configuration files that
you created in Step 4 and Step 5 into the appropriate
freeway/client/op-sys/bin
directory where op-sys indicates the operating system: sunos, hpux, solaris, rs_aix,
osf1.
UNIX example: mv nrmaldcfg.bin /usr/local/freeway/client/hpux/bin
mv nrmaltcfg.bin /usr/local/freeway/client/hpux/bin
7. If you have a VMS system, run the move.com command file from the
[FREEWAY.CLIENT.TEST.NRM] directory. This moves the DLI and TSI binary configu-