NIO CommKit Host Interface Installation and System Administration Manual

DK(1C) DK(1C)

E-6 CommKit Host Interface, Release 4.0

Environment Variables

If the shell variable DKKEY is set in the user’s environment, then that string is used as a matching token when

authorizing. The token value is then used when mapping the originating host user ID to a user ID local to the

destination host. For example,

DKKEY=token dk destination.authorize

The DKKEY value is stored in the dkuidtab(4) file on the remote destination host. Thus, from any given

originating host and user ID, by changing the value of DKKEY, a user can remotely login as a number of

different user IDs on a given remote host.

Multiple Interfaces

If multiple interface boards are installed on the originating host the dk(1C) command will use the default

processing to select the interface for the outgoing call. See dkdial(3X) and authorize(1M) for more

information.

EXAMPLES

The following command lines show the different ways that the dk command may be used. The dk command

may be used for remote login specifying the dialstring of a remote data switch host as in:

dkwombat

where wombat is mapped into the appropriate data switch dialstring [see dkhosts(4)].

A valid data switch dialstring may be specified for remote login as in:

dkarea1/exch1/host1.rl.vx

where area1 is the area, exch1 is the exchange and host1 is the destination.

One can redirect the standard input, standard output, and standard error during remote execution using the dk

command. For example,

dkwombat cat x 2>/dev/null

will redirect the standard error messages to /dev/null.

Whenever you login from one machine to another, or remotely execute a command, your .profile is read to

set up your environment the way you wish, so the invoked command will get the right PATH, umask, etc.

You should distinguish between the different cases by the name of the invoked shell as it was stored in the

variable $0. The value of $0 will be ’–sh’ or ’–ksh’ for a login from ’DESTINATION:’, ’–Dsh’ for remote

Since the user’s .profile is executed on the remote machine during remote execution, you should never do any

prompting for terminal type (for example, if $0 == ’–Xsh’) and you might not want to set tabs, for instance,

if $0 == ’–Dsh’. Shell variables such as TERM may be exported across system boundaries by setting

DKEXPORT.

Warning: When $0 == ’–Xsh’ the profile should never exec another program (as in ’exec ksh’) or run any

program that requests standard input from the terminal or sends standard output or error to the terminal. If

you fail to abide by this rule, your attempts at remote execution may not be successful.