TN3270:Trace Files Show Wrong Time DelayLast reviewed: April 17, 1997Article ID: Q159277 |
The information in this article applies to:
SYMPTOMSThe init status delay time should be traced in milliseconds, not seconds.
MORE INFORMATIONSample Traces:
>08/31 14:42:35.978 (+ smidgen ) Event=TEV_SNAInitTimerStarted Thread = 0x00000085 Session = 0x002664E0 Socket = 0x00000134 Delay = 1000 secondsTN3270 admin init status delay set to 1 second.
>08/31 14:59:50.165 (+ smidgen ) Event=TEV_SNAInitTimerStarted Thread = 0x00000050 Session = 0x00266500 Socket = 0x00000014 Delay = 15000 secondsTN3270 admin init status delay is set to 15 seconds.
>08/31 15:00:35.931 (+ smidgen ) Event=TEV_SNAInitTimerStarted Thread = 0x00000141 Session = 0x002664F0 Socket = 0x00000130 Delay = 45000 secondsTN3270 admin init status delay is set to 45 seconds.
STATUSMicrosoft has confirmed this to be a problem in Microsoft SNA Server 2.11 and 2.11 Service Pack 1 (SP1). This problem was corrected in the latest Microsoft SNA Server 2.11 U.S. Service Pack. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K |
Additional query words: prodsna tn3270
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |