(1) .-MAXLOCAT--=--5000-----------------------------. >>-+-----------------------------------------------+----------->< '-MAXLOCAT--=--max_locate_congestion_threshhold-'
- MAXLOCAT is meaningful only if NODETYPE is specified.
| range: | 100–65535 |
(queued requests plus queued replies for the adjacent CP)x
(number of seconds since last response from adjacent CP)
VTAM resumes sending APPN search requests to an adjacent CP when a minimum congestion threshold is reached. The minimum threshold is based on the number of queued searches waiting to be sent to the adjacent CP. When the queued searches are reduced to 10% of the number on the queue when the maximum locate congestion threshold was reached, new APPN search requests are again sent to the adjacent CP.
Even after VTAM suspends sending APPN search requests to an adjacent CP, VTAM continues to queue APPN search replies to the adjacent CP. If the number of queued requests plus the number of queued replies reaches 200% of the MAXLOCAT value and a minimum time interval has been exceeded, VTAM stops the CP-CP session to the adjacent CP. VTAM stops the CP-CP session with a sense code that can be tried again and retries the CP-CP session. The minimum time interval is based on the time since VTAM issued message IST1601I, which indicates that routing to this node has been suspended. If the IOPURGE value is less than the default of 180 seconds, then the minimum time interval is 180 seconds. Otherwise, the minimum time interval is the current IOPURGE value.
If you specify a value less than 100, VTAM uses MAXLOCAT=100 as the MAXLOCAT value.