An OS/2 program uses dynamic link libraries during run time, where some of the functions are called like subroutines, allowing more function with fewer memory requirements. Although DOS does not use dynamic link libraries, Microsoft Windows 3.1 does.

LAN Server provides dynamic link libraries, NETAPI.DLL and PMSPL.DLL, for use with Windows 3.1. In order to call LAN Server APIs, a Windows application must link to the NETAPI.LIB and PMSPL.LIB (for DosPrint API support) libraries.

Link a DOS application to the DOSNET.LIB library. This library file provides the network functions for applications on DLS workstations to access LAN Server.

Link your application to these .LIB files during compile with a compiler such as Microsoft C Version 6.0 or later, Microsoft C/C++ Version 7.0 or later, or Microsoft Visual C++ Professional Edition Version 1.5 or later (which supports the LAN Server DOSNET.LIB library for DLS applications), Borland C/C++ Version 4.0 or later.

Depending on the compiler and your options, the command to link a DOS application to the API libraries might resemble this:

• For non-Windows, DLS (DOS) applications:

  LINK MYDOSAPP.OBJ, MYDOSAPP.EXE, MYDOSAPP.MAP,
  d:DOSNET.LIB
  

• For Windows applications:

  LINK MYWINAPP.OBJ, MYWINAPP.EXE, MYWINAPP.MAP,
  d:NETAPI.LIB
  d:PMSPL.LIB
  

where d: includes the drive and directory path for the .LIB file. The DOSNET.LIB, NETAPI.LIB, and PMSPL.LIB. libraries are located by default in the \NET directory on the workstation. If you have remote IPL support on a server, the library files are stored by default in the \IBMLAN\DOSLAN\NET subdirectory of that server. (Refer to the documentation accompanying your compiler for instructions and options.)