User guide

114 DC 900-1333P
Freeway User Guide
Changing the AsyncIO parameter to “no” or omitting it prevents the server TSI software
from operating as designed.
Caution
Before modifying the muxcfg file for the server TSI software, you
should be familiar with the parameter descriptions in the Freeway
Transport Subsystem Interface Reference Guide. Of particular
importance are those parameters that control server resources,
such as the TSI buffer pool size (
MaxBuffers parameter) or message
size (
MaxBufSize parameter). Improper values could adversely
affect server operation.
Keep the following points in mind if you must modify the
muxcfg file:
• The Transport parameter for each connection name has no default and must be
defined.
• Unlike the client TSI configuration file you modified (described in Section 2.2.8
on page53 for UNIX, Section 2.3.7 on page 71 for VMS, or Section 2.4.8 on
page 90 for Windows NT), the
server parameter is not required for muxcfg
because the server TSI software automatically uses the address of the machine on
which it is running.
//
Server2
{
transport = "tcp-socket";
logLev = 0;
traceLev = 3;
timeout = 63999;
MaxInQ = 10;
MaxOutQ = 10;
asyncio = "yes";
wellknownport = 0x'2011'; // protocol specifics
}
Figure 3–2: TSI Configuration File (muxcfg) for Server-Resident Software (Cont’d)