Why does the Telnet profile display reflect some PARMSGROUP based timer values but not others?
The IP Configuration Guide section for the INACTIVE family of timers makes the following statement:
"The timer with the smallest value defined in TELNETGLOBALS, TELNETPARMS or PARMSGROUP for that port profile is used to define how often connections are checked."
A detailed profile display for that port does not, however, always reflect the smallest timer value coded.
The following example will be used as an illustration. Telnet timer values are specified in three statement blocks:
TELNETPARMS PORT 23
Output from a profile display command:
indicates the following values:
Note that the SCANINTERVAL value reflects the PARMSGROUP specification yet the INACTIVE and TIMEMARK values are from TELNETPARMS.
The D TCPIP,procname,T,OBJECT,PORT=ALL,PROFILE=CURRENT,TYPE=
command should be used to obtain the information you need. The PROFILE DETAIL display is not designed to reflect changes at the PARMSGROUP level. However, a change will be seen in the SCANINTERVAL value when PROFILE DETAIL is used because only one SCANINTERVAL for a port is used. The value used will be the smallest value coded in TELNETGLOBALS, TELNETPARMS, or PARMSGROUP. So, if a smaller value for SCANINTERVAL is coded in a PARMSGROUP, that value will be used.