Question & Answer
Question
Why does the Telnet profile display reflect some PARMSGROUP based timer values but not others?
Cause
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.
Answer
The following example will be used as an illustration. Telnet timer values are specified in three statement blocks:
TELNETGLOBALS
SCANINTERVAL 1900
TIMEMARK 10900
INACTIVE 3800
TELNETPARMS PORT 23
SCANINTERVAL 1800
TIMEMARK 10800
INACTIVE 3600
PARMSGROUP
SCANINTERVAL 120
TIMEMARK 180
INACTIVE 1140
Output from a profile display command:
D TCPIP,,T,PROF,PORT=23,DET
indicates the following values:
TIMERS
INACTIVE 3600
SCANINTERVAL 120
TIMEMARK 10800
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=
PARMSGRP,ID=parmsgroupname
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.
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21292919