Expand Configuration and Management Manual (G06.24+)

Subsystem Control Facility (SCF) Commands
Expand Configuration and Management Manual—523347-008
15-27
INFO PATH Command
L4Timeout
reports the time interval for the Layer 4 timer.
L4SendWindow
is the maximum number of outstanding packet send requests in any single
transport connection.
TimeFactor
reports the current time factor for this path. The time factor is used by NCP when
calculating the best route between systems and represents the cost of using the
path. The lower the time factor, the more desirable the path.
The time factor is calculated based upon the parameters you have set. Previously,
path time-factor calculations made within a node were made using the device/line
settings (RSIZE, SPEED, and SPEEDK) and from looking at the aggregate values
of time factors for the line if the path was a multi-line path. As of G06.20, the two
direct time-factor settings (LINETF and PATHTF) can be applied to override the
RSIZE, SPEED, and SPEEDK calculations within a node.
If PATHTF is set to a nonzero value, the time factor and PATHTF will be the same.
If PATHTF is not set (zero), the TimeFactor field will display the time factor being
used by the path.
If a line in the path fails and PATHTF is not set (zero), $NCP updates its NETMAP
table to reflect the decrease in path bandwidth. Reactivation of the line updates the
NETMAP table to reflect the increase in bandwidth. If a communications hardware
device fails, $NCP updates its NETMAP table to reflect the decrease in bandwidth
for all lines connected to the failed device.
L4ExtPackets
shows whether the extended packet format is enabled (ON) or disabled (OFF).
Extended packet format uses a larger packet header, which can reduce throughput
on lower-speed lines. It can provide higher throughput and less OOS processing in
paths with multiple high-speed lines. This feature is negotiated between end
systems and should be enabled at both end systems.
L4CongCtrl
shows whether congestion control is enabled (ON) or disabled (OFF). Congestion
control is used to avoid bottlenecks and deadlocks. If the congestion control
feature is enabled on both ends of a connection, it is executed for traffic in both
directions. Traffic in a given direction is subject to congestion control if the sender
has congestion control enabled and the receiver supports it. The receiver does not
have to have the congestion control feature enabled in order to support it.