NetIPC logging is automatically activated at system startup.
Network Services logging is activated when the Network Services
are initiated (i.e., when the NSCONTROL START
command is issued). Link manager logging and network transport logging
are activated when you initiate the network transport (NETCONTROL START).
When you are changing a logging configuration for a specific
subsystem, the changes will normally take effect when you perform
a SWITCHNMLOG UPDATE command. In some cases, however, such as when
no logging is currently active, the subsystem may need to be deactivated
and restarted. The steps that must be taken for each subsystem are
shown in Table 14-1 “Subsystem
Activation/Deactivation”.
Table 14-1 Subsystem
Activation/Deactivation
| Subsystem | Steps |
|---|
| Network Transport | NETCONTROL STOP (if already
active) NETCONTROL START |
| NetIPC (sockets) | Restart the system (warmstart, coolstart, update
start, or coldstart) |
| Network Services | NSCONTROL STOP (if already
active) NSCONTROL START |
| Link Manager | NETCONTROL STOP (if already
active) SNACONTROL STOP;NODE=nodename (repeat until
all SNA nodes are stopped; refer to the SNA Link/iX Node
Manager's Guide) SNACONTROL START;NODE=nodename NETCONTROL START |
How to use the log messages for troubleshooting is described
in the NS 3000/iX Error Messages Reference Manual.
How to format the log file for examination is described in Using
the Node Management Services (NMS) Utilities.
