Technical data

Tuning Techniques
2.1 Subsystem Attributes
$ TCPIP
TCPIP> sysconfig -s
cm: loaded and configured
inet: loaded and configured
iptunnel: loaded and configured
ipv6: loaded and configured
net: loaded and configured
snmpinfo: loaded and configured
socket: loaded and configured
inetkvci: loaded and configured
proxy: loaded and configured
nfs: loaded and configured
vfs: loaded and configured
TCPIP>
Note
Depending on the configuration of your system, the list of subsystems
displayed may differ from this example.
2.1.1.1 Static and Dynamic Subsystems
There are two types of subsystems:
Static subsystems are loaded at startup time and can be unloaded only when
TCP/IP shuts down.
Dynamic subsystems can be loaded and unloaded at will without shutting
down and restarting TCP/IP Services.
You can use the
sysconfig -m
command to display static and dynamic
subsystems, as follows:
$ TCPIP
TCPIP> sysconfig -m
cm: static
inet: static
iptunnel: static
ipv6: static
net: static
snmpinfo: static
socket: static
inetkvci: static
proxy: static
nfs: static
vfs: static
Subsystems can be loaded but not available for use. Subsystems can have the
following states:
Loaded and configured (available for use)
Loaded and unconfigured (not available for use)
This state applies only to static subsystems, which you can unconfigure, but
you cannot unload.
Unloaded (not available for use)
This state applies only to loadable subsystems, which are automatically
unloaded when you unconfigure them.
2–2 Tuning Techniques