Try tcpclientport (for Netware, OS/2 Windows, and UNIX clients) in their
respective options files (dsm.opt for Netware, OS/2, Windows, dsm.sys
for UNIX).  When the scheduler starts, it contacts the server and tells
it to call back at that port (for server-prompted schedmode).

Cheers...
Bruce

Gaverth, Timothy, J. Mr. (Tim) (GSFC-255.7) wrote:
>
> Okay, I've browsed the archives, I've looked in all documentation I have,
> and I can't find my own answer to this:
> How can I force the server to talk to a client on a specific port? I know
> about 1500, 1501, and 1580 on the server, and that's fine. But, I need to
> use one port, or a few (but pre-determined) ports, on the client. Do I give
> the client a dsmc listener, and if so, how?
> Thanks for any help.
>
> Timothy J. Gaverth
> Systems Administrator
> NASA/GSFC - BATCS
> (301)286-9282(voice);(301)286-1619(fax)
> tim.gaverth AT gsfc.nasa DOT gov