User`s guide

64 DC 900-1343D

DDCMP Programmer’s Guide

6. If you have a UNIX system, move the binary conﬁguration ﬁles 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:

dec, hpux, sgi, solaris, or sunos.

UNIX example:

mv ddcmpaldcfg.bin /usr/local/freeway/client/hpux/bin

mv ddcmpaltcfg.bin /usr/local/freeway/client/hpux/bin

7. If you have a VMS system, run the move.com command ﬁle from the

[FREEWAY.CLIENT.TEST.DDCMP] directory. This moves the binary configuration

ﬁles you created in Step 4 and Step 5 into the

bin directory for your particular

TCP/IP package.

@MOVE filename <tcp-sys>

where ﬁlename is the name of the binary conﬁguration ﬁle and

<tcp-sys> is the TCP/IP package:

MULTINET (for a Multinet system)

TCPWARE (for TCPware system)

UCX (for a UCX system)

VMS example:

@MOVE DDCMPALDCFG.BIN UCX

8. If you have a Windows NT system, move the binary conﬁguration ﬁles 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: axp_nt or int_nt (for a

Freeway server);

axp_nt_emb or int_nt_emb (for an embedded ICP).

NT example:

copy ddcmpaldcfg.bin \freeway\client\axp_nt\bin

copy ddcmpaltcfg.bin \freeway\client\axp_nt\bin

When your application calls the dlInit function, the DLI and TSI binary conﬁguration

ﬁles generated in Step 4 and Step 5 are used to conﬁgure the DLI sessions and TSI con-

nections. Figure B–1 shows the conﬁguration process.

Techpubs —

keep the op-

sys up-to-

date with

DC900-1333

Techpubs —

keep the op-

sys up-to-

date with

DC900-1333