Manual Installation Process

"X:" is the drive letter assigned to the location of the IBMCOM (MPTS) installation. This is usually the boot drive, but this is not necessarily the case.

Open this file in an editor. 

If you are implementing PROTOCOL mode then continue with step 6A.
If you are implementing SERVICE mode then continue with step 6B.

Add the following section (these are the safest default configuration values):

[NTRACE_nif]

DriverName = NTRACE$
ModuleType = "Protocol"
Bindings = list of module name(s) for MAC(s) the Network Trace driver is to be bound to
MaxBufSegments = 32
RejectFrames = 21

For each LAN adapter on which tracing must be active, a separate instance of NTRACE.OS2 MUST BE loaded in CONFIG.SYS (see step 7) and configured in PROTOCOL.INI.  Each instance MUST BE uniquely named and the names MUST MATCH between CONFIG.SYS and PROTOCOL.INI.  This matching of names is how each specific driver instance knows which section in PROTOCOL.INI is to be used for its configuration.

Add the following section (these are the safest default configuration values) for each instance of NTRACE:

[NTRACE_nif]

DriverName = NTRACE$
ModuleType = "Service"
Bindings = module name of MAC which the Network Trace driver is to be bound to
MaxBufSegments = 32
RejectFrames = 21

The NTRACE "Bindings" statement MUST NOT contain more than 1 MAC module name.  There MUST ONLY be a one-to-one correspondence of NTRACE instances and MAC drivers.

On a machine with 2 LAN adapters on which tracing will be enabled, the NTRACE sections might look like:

[NTRACE_nif]

DriverName = NTRACE$
ModuleType = "Service"
Bindings = IBMFEEO2_nif
MaxBufSegments = 32
RejectFrames = 21

DriverName = NTRACE2$
ModuleType = "Service"
Bindings = IBMTRP_nif
MaxBufSegments = 32
RejectFrames = 21

1. the module name (the bracketed section name) must be unique and this is what the protocol drivers will use in their "Bindings" statement
2. the "DriverName" statement, which must match a unique instance name in CONFIG.SYS
3. the "Bindings" statement which must specify a single UNIQUE MAC module name

Edit each PROTOCOL.INI section which pertains to a protocol which should be included in tracing.  For each MAC module name which is being enabled for tracing, replace this module name which the protocol had been previously bound to, with the corresponding module name of NTRACE.

For example, if the TCP/IP section previously looked like:

[tcpip_nif]

   DriverName = TCPIP$
   Bindings = IBMFEEO2_nif,IBMTRP_nif

The Bindings would be changed as in:

[tcpip_nif]

   DriverName = TCPIP$
   Bindings = NTRACE_nif,NTRACE2_nif
 

If service mode is in use, then for each LAN adapter on which tracing must be active, a separate instance of NTRACE.OS2 MUST BE loaded in CONFIG.SYS and configured in PROTOCOL.INI (see step 6B) .  Each instance MUST BE uniquely named and the names MUST MATCH between CONFIG.SYS and PROTOCOL.INI.  If protocol mode is in use, then loading multiple instances is optional but would be needed if there is a requirement for simultaneous tracing on more than 1 LAN adapter.

Add the following statement to your CONFIG.SYS (for each instance of NTRACE): 

DEVICE=X:\IBMCOM\PROTOCOL\NTRACE.OS2 NTRACE$

On a machine with 2 LAN adapters on which tracing will be enabled, the NTRACE entries might look like:

DEVICE=X:\IBMCOM\PROTOCOL\NTRACE.OS2 NTRACE$
DEVICE=X:\IBMCOM\PROTOCOL\NTRACE.OS2 NTRACE2$

IMPORTANT!  If the protocol mode of operation is in use or ever planned to be in use, then make sure the above device statement(s) go AFTER all protocol drivers loaded in CONFIG.SYS!  The easiest way to ensure this, is to place this line at the end of CONFIG.SYS.  Another way of checking this, is to ensure that all statements in the CONFIG.SYS file that start with "DEVICE=X:\XXXX\PROTOCOL\" are above the NTRACE.OS2 statement.

In protocol mode, failure to load NTRACE.OS2 as a last protocol driver will lead to a frame filtering effect: some frames will be intercepted by protocols loaded after NTRACE.OS2.  The Protocol Manager honors protocol priorities in the reverse order to their loading.  When NTRACE.OS2 is the last driver loaded then it is the first driver in the PROTMAN.OS2 priority list.  This means it will see all frames before any other protocol.