NIO CommKit Host Interface Installation and System Administration Manual

6-10
Porting CommKit Applications To Release 4.x
Programmer-Level Compatibility
Supported Library Routines
This section describes the library routines that are currently supported by the
CommKit software. These routines comprise the only supported interface
available to you. None of the ioctl calls supported in previous releases are
still supported.
These library functions should satisfy all of your requirements for develop-
ing CommKit applications. Many of the new functions have been designed
to isolate application code from the underlying driver and make it more
dtnamer
This function converted an NIO CommKit Host Interface
minor number into the /dev name for the TTY interface.
dtnamer has been replaced by dk_tnamer, which accepts
both the NIO CommKit Host Interface number and the data
switch channel number as arguments. Refer to the
dk_tnamer example later in this chapter.
This function was often used with the dkminor function
when switching an outgoing call from the raw interface to
the TTY interface. Converting the HP-UX 9.x old code to
use the HP-UX 10.x equivalents will not make an outgoing
call over the TTY interface. A process obtains a TTY
interface directly by using the new dkitdial library function.
Refer to the dkitdial example later in this chapter.
dxnamer
This function converted an NIO CommKit Host Interface
minor number into the /dev name for the remote execution
interface. This function has been replaced by the dk_xnamer
library function that accepts both the NIO CommKit Host
Interface number and the data switch channel number as
arguments. Refer to the dk_xnamer example later in this
chapter.
dkxwrite
This function transmitted data to the remote system and was
used by the remote execution interface. This function is no
longer supported for user-level application programs.
dkxenviron
This function has been obsoleted.
Table 6-3 Obsolete CommKit Software Library Routines
Function Description