User`s guide

124 DC 900-1317J
ADCCP NRM Programmer’s Guide
UNIX example: freeway/client/<op-sys>/bin
VMS example: [FREEWAY.CLIENT.<vms_platform>_tcp-sys.BIN]
where <vms_platform> is VAX or AXP
for example,
[FREEWAY.CLIENT.VAX_UCX.BIN]
NT example: freeway\client\<op-sys>\bin
• Compiles and links the test programs and copies them to the same bin direc-
tory.
5. Boot the Freeway server and load the ADCCP NRM protocol software onto the
ICP (refer to the Freeway User’s Guide).
6. Connect two ICP links with loopback cables (refer to the Freeway User’s Guide
appendix).
7. Execute the test program from the directory where the binary DLI and TSI config-
uration files reside (that resulted from Step 4 above).
In Step 4 above, the make file runs the dlicfg and tsicfg preprocessor programs and com-
piles and links the test program. If you already compiled and linked the test program,
you can avoid recompiling and relinking it by running
dlicfg and tsicfg yourself instead
of running the make file. However, note the following if you do.
In a UNIX system, if you run dlicfg and tsicfg instead of running the make file, you must
manually move the resulting DLI and TSI binary configuration files to the appropriate
freeway/client/<op-sys>/bin directory where <op-sys> indicates the operating system:
bsd,
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
In a VMS system, if you run dlicfg and tsicfg instead of running the make file, you must
do the following: