[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference csc32::consolemanager

Title:POLYCENTER Console Manager
Notice:Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS:
Moderator:CSC32::BUTTERWORTH
Created:Thu Aug 06 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1541
Total number of notes:6564

957.0. "Wrong data (old data) while monitoring node" by 54625::WILLEMS (Johan Willems @BRO DTN 856-8739) Wed Aug 30 1995 10:46

A customer logged a call with following information

	Hardware		MicroVAX 3100-80
	OpenVMS			VMS V6.1
	Consolemanager		PCM V1.6-100



problem PCM V1.6-100 (old information in console monitor)                       

Hello,


We have encountered a problem with PCM V1.6-100:

Yesterday evening I was following a reboot of one of our ELN-machines
with console monitor. At one moment some information of yesterday morning
was displayed on the screen overwritting the current information.
After some time the console continued with the real information.

In the monitor screen there's a piece of yesterday's evening information
missing when I execute the 'PREV SCREEN' and 'NEXT SCREEN' commands.

Even when I do an extract of that system I can find this old information 
between the lines of the actual information. In the extract I could cut
the old information with the editor to have the correct and complete
information of yesterday evening.

I have included the original extract so you can see at the time indications
that somethings is wrong: after 21:00 it continues at 17:30, from line
0024 it goes straight to line 0375.


23-Aug-1995 20:57:37  ?02 EXT HLT
23-Aug-1995 20:57:37          PC = 8000658E
23-Aug-1995 20:57:37   [c>>>B
23-Aug-1995 20:57:39  (BOOT/R5:0 EZA0,ESA0)
23-Aug-1995 20:57:42  
23-Aug-1995 20:57:42    2..
23-Aug-1995 20:57:42  -EZA0
23-Aug-1995 20:58:23    1..0..
23-Aug-1995 20:58:23  
23-Aug-1995 20:58:23  
23-Aug-1995 20:58:23  
23-Aug-1995 20:58:23  %VAXELN system initializing
23-Aug-1995 20:58:23  
23-Aug-1995 20:58:23  
23-Aug-1995 20:58:23   VAXELN V4.4  QBUS
23-Aug-1995 20:58:23  
23-Aug-1995 20:58:23  
23-Aug-1995 20:59:20  
23-Aug-1995 20:59:20  0001 00:00:00 %ATS2-S-SYSTART: ATS/2 VERSION 7.0F: Mar 23 
1995 12:37:06
23-Aug-1995 20:59:20  
23-Aug-1995 20:59:20  0002 00:00:00 %ATS2-S-SYSTART: Console Started.
23-Aug-1995 20:59:21  
23-Aug-1995 20:59:21  0003 00:00:00 %ATS2-S-SYSTART: Logger Started.
23-Aug-1995 20:59:25  
23-Aug-1995 20:59:25  0004 20:59:27 %ATS2-I-SYSTART: ATS/2 Time set to 23-AUG-19
95 20:59:27.67  
23-Aug-1995 20:59:26  
23-Aug-1995 20:59:26  0005 20:59:27 %ATS2-S-SYSTART: Initialisation Controller S
tarted.
23-Aug-1995 20:59:28  
23-Aug-1995 20:59:28  
23-Aug-1995 20:59:28  VAXELN V4.4  QBUS on node ELN01
23-Aug-1995 20:59:28  Press <RETURN> to continue
23-Aug-1995 20:59:28  
23-Aug-1995 20:59:29  
23-Aug-1995 20:59:29  0006 20:59:31 %ATS2-I-SYSTART: Initialisation Controller C
onnected To Database PDB_ELN01.
23-Aug-1995 20:59:33  
23-Aug-1995 20:59:33  0007 20:59:35 %ATS2-S-SYSTART: Configuration Manager Start
ed.
23-Aug-1995 20:59:37  
23-Aug-1995 20:59:37  0008 20:59:38 %ATS2-S-SYSTART: Session Controller Started.
23-Aug-1995 20:59:45  INIT SVM CODES-I: There must follow 10 DIFFERENT underlyin
g codes
23-Aug-1995 20:59:45  INIT SVM CODES-I: [0000364354]
23-Aug-1995 20:59:45  INIT SVM CODES-I: [0001504207]
23-Aug-1995 20:59:45  INIT SVM CODES-I: [0000000099]
23-Aug-1995 20:59:45  INIT SVM CODES-I: [0000356270]
23-Aug-1995 20:59:45  INIT SVM CODES-I: [0000365263]
23-Aug-1995 20:59:45  INIT SVM CODES-I: [0000000098]
23-Aug-1995 20:59:45  INIT SVM CODES-I: [0000357684]
23-Aug-1995 20:59:45  INIT SVM CODES-I: [0000356472]
23-Aug-1995 20:59:45  INIT SVM CODES-I: [0000347075]
23-Aug-1995 20:59:45  INIT SVM CODES-I: [0000362637]
23-Aug-1995 20:59:47  
23-Aug-1995 20:59:47  0009 20:59:49 %ATS2-S-SYSTART: Outbound Logger ( LOBN ) St
arted.
23-Aug-1995 20:59:57  
23-Aug-1995 20:59:57  0010 20:59:59 %ATS2-S-SYSTART: Registration ( RG01 ) Start
ed.
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  0011 21:00:00 %ATS2-S-SYSTART: Logger Concentrator ( LOGC 
) Started.
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  0012 21:00:00 %ATS2-S-SYSTART: Outbound Router ( OR01 ) St
arted.
23-Aug-1995 20:59:59  ATS2-I-LOGGER: Make connection to Logger Client
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  0013 21:00:00 ATS2-S-SYSTART: Broadcast Manager ( BC01 ) S
tarted [AN/BL/RT].
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  0014 21:00:00 %ATS2-S-SYSTART: Outbound Concentrator ( OB0
1 ) Started.
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  0015 21:00:00 %ATS2-S-SYSTART: Outbound Concentrator ( OB0
2 ) Started.
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  0016 21:00:00 %ATS2-S-SYSTART: Registration ( RG02 ) Start
ed.
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  0017 21:00:00 %ATS2-S-SYSTART: Inbound Logger ( LIBN ) Sta
rted.
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  0018 21:00:00 %ATS2-S-SYSTART: Inbound Switch ( IB01 ) [X2
5] Started.
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  0019 21:00:00 %ATS2-S-SYSTART: Inbound Switch ( IB02 ) [X2
5] Started.
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  0020 21:00:01 %ATS2-S-SYSTART: Registration ( RG03 ) Start
ed.
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  0021 21:00:01 %ATS2-S-SYSTART: Registration ( RG04 ) Start
ed.
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  0022 21:00:01 %ATS2-S-SYSTART: Registration ( RG05 ) Start
ed.
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  0023 21:00:01 %ATS2-S-SYSTART: Registration ( RG06 ) Start
ed.
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  0024 21:00:01 %ATS2-S-SYSTART: Registration ( :30:33 %ATS2
-I-USRLOGOF: User 242,1 logoff due to OB_CONNECTION_FAIL
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  0374 17:30:33 %ATS2-I-USRLOGOFF: Sending OB_LOGOFF to 121,
5 OB02 channel 7
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  0375 17:30:33 %ATS2-E-LOSTCONN: Inbound Switch ( IB01 ) Lo
st X25 connection with member 121, 5.
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  0376 17:30:33 %ATS2-I-USRLOGOF: User 220,5 logoff due to I
B_CONNECTION_FAIL
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  0377 17:30:33 %ATS2-I-USRLOGOF: User 121,5 logoff due to I
B_CONNECTION_FAIL
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  0378 17:30:48 %ATS2-S-SYSHUT: Logger Shutdown.
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  0379 17:30:48 %ATS2-S-SYSHUT: Console Shutdown.
23-Aug-1995 20:59:59  ?02 EXT HLT
23-Aug-1995 20:59:59          PC = 8000658A
23-Aug-1995 20:59:59   [c>>>B
23-Aug-1995 20:59:59  (BOOT/R5:0 EZA0,ESA0)
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59    2..
23-Aug-1995 20:59:59  -EZA0
23-Aug-1995 20:59:59    1..0..
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  %VAXELN system initializing
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59   VAXELN V4.4  QBUS
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  Time set to Wed Aug 23 17:38:45 1995
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  VAXELN V4.4  QBUS on node ELN01
23-Aug-1995 20:59:59  Press <RETURN> to continue
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  ?02 EXT HLT
23-Aug-1995 20:59:59          PC = 8000658E
23-Aug-1995 20:59:59   [c>>>B
23-Aug-1995 20:59:59  (BOOT/R5:0 EZA0,ESA0)
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59    2..
23-Aug-1995 20:59:59  -EZA0
23-Aug-1995 20:59:59    1..0..
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  %VAXELN system initializing
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59   VAXELN V4.4  QBUS
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  0001 00:00:00 %ATS2-S-SYSTART: ATS/2 VERSION 7.0F: Mar 23 
1995 12:37:06
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  0002 00:00:00 %ATS2-S-SYSTART: Console Started.
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  0003 00:00:00 %ATS2-S-SYSTART: Logger Started.
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  0004 20:59:27 %ATS2-I-SYSTART: ATS/2 Time set to 23-AUG-19
95 20:59:27.67  
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  0005 20:59:27 %ATS2-S-SYSTART: Initialisation Controller S
tarted.
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  VAXELN V4.4  QBUS on node ELN01
23-Aug-1995 20:59:59  Press <RETURN> to continue
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  0006 20:59:31 %ATS2-I-SYSTART: Initialisation Controller C
onnected To Database PDB_ELN01.
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  0007 20:59:35 %ATS2-S-SYSTART: Configuration Manager Start
ed.
23-Aug-1995 20:59:59  
23-Aug-1995 20:59:59  0008 20:59:38 %ATS2-S-SYSTART: Session ControlRG07 ) Start
ed.
23-Aug-1995 21:00:07  
23-Aug-1995 21:00:07  0025 21:00:01 %ATS2-S-SYSTART: Registration ( RG08 ) Start
ed.
23-Aug-1995 21:00:07  
23-Aug-1995 21:00:07  0026 21:00:01 %ATS2-S-SYSTART: Registration ( RG09 ) Start
ed.
23-Aug-1995 21:00:07  
23-Aug-1995 21:00:07  0027 21:00:01 %ATS2-S-SYSTART: Registration ( RG10 ) Start
ed.
23-Aug-1995 21:00:07  
23-Aug-1995 21:00:07  0028 21:00:01 %ATS2-S-SYSTART: Registration ( RG11 ) Start
ed.
23-Aug-1995 21:00:31  
23-Aug-1995 21:00:31  0029 21:00:29 %ATS2-S-SYSTART: Clearing Link [ARCH] Starte
d.
23-Aug-1995 21:00:31  
23-Aug-1995 21:00:31  0030 21:00:29 %ATS2-S-SYSTART: Message Server Started.
23-Aug-1995 21:00:31  
23-Aug-1995 21:00:31  0031 21:00:29 %ATS2-S-SYSTART: Broadcast Logger ( LOBC ) S
tarted.
23-Aug-1995 21:03:19  
23-Aug-1995 21:03:19  0032 21:03:21 %ATS2-S-SYSTART: Validation ( VN01 ) [BE]  S
tarted.
23-Aug-1995 21:06:21  
23-Aug-1995 21:06:21  0033 21:06:23 %ATS2-S-SYSTART: Validation ( VN02 ) [BE]  S
tarted.
23-Aug-1995 21:09:15  
23-Aug-1995 21:09:15  0034 21:09:17 %ATS2-S-SYSTART: Validation ( VN03 ) [BE]  S
tarted.
23-Aug-1995 21:11:34  
23-Aug-1995 21:11:34  0035 21:11:36 %ATS2-S-SYSTART: Validation ( VN04 ) [BE]  S
tarted.
23-Aug-1995 21:15:10  
23-Aug-1995 21:15:10  0036 21:15:12 %ATS2-S-SYSTART: Validation ( VN05 ) [BE]  S
tarted.
23-Aug-1995 21:18:10  
23-Aug-1995 21:18:10  0037 21:18:12 %ATS2-S-SYSTART: Validation ( VN06 ) [BE]  S
tarted.
23-Aug-1995 21:20:31  
23-Aug-1995 21:20:31  0038 21:20:33 %ATS2-S-SYSTART: Validation ( VN07 ) [BE]  S
tarted.
23-Aug-1995 21:21:16  
23-Aug-1995 21:21:16  0039 21:21:18 %ATS2-S-SYSTART: Validation ( VN08 ) [BE]  S
tarted.
23-Aug-1995 21:23:15  
23-Aug-1995 21:23:15  0040 21:23:17 %ATS2-S-SYSTART: Validation ( VN09 ) [BE]  S
tarted.
23-Aug-1995 21:25:54  
23-Aug-1995 21:25:55  0041 21:25:56 %ATS2-S-SYSTART: Validation ( VN10 ) [BE]  S
tarted.
23-Aug-1995 21:28:37  
23-Aug-1995 21:28:37  0042 21:28:39 %ATS2-S-SYSTART: Validation ( VN11 ) [BE]  S
tarted.
23-Aug-1995 21:28:37  
23-Aug-1995 21:28:37  0043 21:28:40 %ATS2-S-SYSTART: Order Manager ( OM01 ) [BL]
 Started.
23-Aug-1995 21:28:38  
23-Aug-1995 21:28:38  0044 21:28:40 %ATS2-S-SYSTART: Order Manager ( OM02 ) [BL]
 Started.
23-Aug-1995 21:28:39  
23-Aug-1995 21:28:39  0045 21:28:41 %ATS2-S-SYSTART: Order Manager ( OM03 ) [BL]
 Started.
23-Aug-1995 21:28:39  
23-Aug-1995 21:28:39  0046 21:28:42 %ATS2-S-SYSTART: Order Manager ( OM04 ) [BL]
 Started.
23-Aug-1995 21:28:40  
23-Aug-1995 21:28:40  0047 21:28:42 %ATS2-S-SYSTART: Order Manager ( OM05 ) [BL]
 Started.
23-Aug-1995 21:28:41  
23-Aug-1995 21:28:41  0048 21:28:43 %ATS2-S-SYSTART: Order Manager ( OM06 ) [BL]
 Started.
23-Aug-1995 21:28:42  
23-Aug-1995 21:28:42  0049 21:28:44 %ATS2-S-SYSTART: Order Manager ( OM07 ) [BL]
 Started.
23-Aug-1995 21:28:42  
23-Aug-1995 21:28:42  0050 21:28:44 %ATS2-S-SYSTART: Order Manager ( OM08 ) [BL]
 Started.
23-Aug-1995 21:28:43  
23-Aug-1995 21:28:43  0051 21:28:45 %ATS2-S-SYSTART: Order Manager ( OM09 ) [BL]
 Started.
23-Aug-1995 21:28:44  
23-Aug-1995 21:28:44  0052 21:28:46 %ATS2-S-SYSTART: Order Manager ( OM10 ) [BL]
 Started.
23-Aug-1995 21:28:44  
23-Aug-1995 21:28:44  0053 21:28:46 %ATS2-S-SYSTART: Order Manager ( OM11 ) [BL]
 Started.
23-Aug-1995 21:28:46  
23-Aug-1995 21:28:46  0054 21:28:48 %ATS2-I-INDEXED: Market ( 01 ) Has Created C
ontract Index.
23-Aug-1995 21:28:47  
23-Aug-1995 21:28:47  0055 21:28:49 %ATS2-I-PRICES: Market ( 01 ) Has Dumped Pri
ces.
23-Aug-1995 21:28:47  
23-Aug-1995 21:28:47  0056 21:28:49 %ATS2-I-OPENORD: Market ( 01 ) Has Received 
Open Orders.
23-Aug-1995 21:28:47  
23-Aug-1995 21:28:47  0057 21:28:49 %ATS2-S-SYSTART: Matcher [BL] ( MR01 ) Start
ed.
23-Aug-1995 21:28:49  
23-Aug-1995 21:28:49  0058 21:28:51 %ATS2-I-INDEXED: Market ( 02 ) Has Created C
ontract Index.
23-Aug-1995 21:28:49  
23-Aug-1995 21:28:49  0059 21:28:51 %ATS2-I-PRICES: Market ( 02 ) Has Dumped Pri
ces.
23-Aug-1995 21:28:49  
23-Aug-1995 21:28:49  0060 21:28:51 %ATS2-I-OPENORD: Market ( 02 ) Has Received 
Open Orders.
23-Aug-1995 21:28:49  
23-Aug-1995 21:28:49  0061 21:28:52 %ATS2-S-SYSTART: Matcher [BL] ( MR02 ) Start
ed.
23-Aug-1995 21:28:51  
23-Aug-1995 21:28:51  0062 21:28:53 %ATS2-I-INDEXED: Market ( 03 ) Has Created C
ontract Index.
23-Aug-1995 21:28:52  
23-Aug-1995 21:28:52  0063 21:28:54 %ATS2-I-PRICES: Market ( 03 ) Has Dumped Pri
ces.
23-Aug-1995 21:28:52  
23-Aug-1995 21:28:52  0064 21:28:54 %ATS2-I-OPENORD: Market ( 03 ) Has Received 
Open Orders.
23-Aug-1995 21:28:52  
23-Aug-1995 21:28:52  0065 21:28:54 %ATS2-S-SYSTART: Matcher [BL] ( MR03 ) Start
ed.
23-Aug-1995 21:28:53  
23-Aug-1995 21:28:53  0066 21:28:56 %ATS2-I-INDEXED: Market ( 04 ) Has Created C
ontract Index.
23-Aug-1995 21:28:54  
23-Aug-1995 21:28:54  0067 21:28:56 %ATS2-I-PRICES: Market ( 04 ) Has Dumped Pri
ces.
23-Aug-1995 21:28:54  
23-Aug-1995 21:28:54  0068 21:28:56 %ATS2-I-OPENORD: Market ( 04 ) Has Received 
Open Orders.
23-Aug-1995 21:28:54  
23-Aug-1995 21:28:54  0069 21:28:56 %ATS2-S-SYSTART: Matcher [BL] ( MR04 ) Start
ed.
23-Aug-1995 21:28:56  
23-Aug-1995 21:28:56  0070 21:28:58 %ATS2-I-INDEXED: Market ( 05 ) Has Created C
ontract Index.
23-Aug-1995 21:28:56  
23-Aug-1995 21:28:56  0071 21:28:59 %ATS2-I-PRICES: Market ( 05 ) Has Dumped Pri
ces.
23-Aug-1995 21:28:57  
23-Aug-1995 21:28:57  0072 21:28:59 %ATS2-I-OPENORD: Market ( 05 ) Has Received 
Open Orders.
23-Aug-1995 21:28:57  
23-Aug-1995 21:28:57  0073 21:28:59 %ATS2-S-SYSTART: Matcher [BL] ( MR05 ) Start
ed.
23-Aug-1995 21:28:58  
23-Aug-1995 21:28:58  0074 21:29:00 %ATS2-I-INDEXED: Market ( 06 ) Has Created C
ontract Index.
23-Aug-1995 21:28:59  
23-Aug-1995 21:28:59  0075 21:29:01 %ATS2-I-PRICES: Market ( 06 ) Has Dumped Pri
ces.
23-Aug-1995 21:28:59  
23-Aug-1995 21:28:59  0076 21:29:01 %ATS2-I-OPENORD: Market ( 06 ) Has Received 
Open Orders.
23-Aug-1995 21:28:59  
23-Aug-1995 21:28:59  0077 21:29:01 %ATS2-S-SYSTART: Matcher [BL] ( MR06 ) Start
ed.
23-Aug-1995 21:29:04  
23-Aug-1995 21:29:04  0078 21:29:06 %ATS2-I-INDEXED: Market ( 07 ) Has Created C
ontract Index.
23-Aug-1995 21:29:04  
23-Aug-1995 21:29:04  0079 21:29:06 %ATS2-I-PRICES: Market ( 07 ) Has Dumped Pri
ces.
23-Aug-1995 21:29:05  
23-Aug-1995 21:29:05  0080 21:29:07 %ATS2-I-OPENORD: Market ( 07 ) Has Received 
Open Orders.
23-Aug-1995 21:29:05  
23-Aug-1995 21:29:05  0081 21:29:07 %ATS2-S-SYSTART: Matcher [BL] ( MR07 ) Start
ed.
23-Aug-1995 21:29:11  
23-Aug-1995 21:29:11  0082 21:29:13 %ATS2-I-INDEXED: Market ( 08 ) Has Created C
ontract Index.
23-Aug-1995 21:29:11  
23-Aug-1995 21:29:11  0083 21:29:13 %ATS2-I-PRICES: Market ( 08 ) Has Dumped Pri
ces.
23-Aug-1995 21:29:11  
23-Aug-1995 21:29:11  0084 21:29:13 %ATS2-I-OPENORD: Market ( 08 ) Has Received 
Open Orders.
23-Aug-1995 21:29:11  
23-Aug-1995 21:29:12  0085 21:29:13 %ATS2-S-SYSTART: Matcher [BL] ( MR08 ) Start
ed.
23-Aug-1995 21:29:17  
23-Aug-1995 21:29:17  0086 21:29:20 %ATS2-I-INDEXED: Market ( 09 ) Has Created C
ontract Index.
23-Aug-1995 21:29:18  
23-Aug-1995 21:29:18  0087 21:29:20 %ATS2-I-PRICES: Market ( 09 ) Has Dumped Pri
ces.
23-Aug-1995 21:29:18  
23-Aug-1995 21:29:18  0088 21:29:20 %ATS2-I-OPENORD: Market ( 09 ) Has Received 
Open Orders.
23-Aug-1995 21:29:18  
23-Aug-1995 21:29:18  0089 21:29:20 %ATS2-S-SYSTART: Matcher [BL] ( MR09 ) Start
ed.
23-Aug-1995 21:29:20  
23-Aug-1995 21:29:20  0090 21:29:22 %ATS2-I-INDEXED: Market ( 10 ) Has Created C
ontract Index.
23-Aug-1995 21:29:20  
23-Aug-1995 21:29:20  0091 21:29:22 %ATS2-I-PRICES: Market ( 10 ) Has Dumped Pri
ces.
23-Aug-1995 21:29:21  
23-Aug-1995 21:29:21  0092 21:29:22 %ATS2-I-OPENORD: Market ( 10 ) Has Received 
Open Orders.
23-Aug-1995 21:29:21  
23-Aug-1995 21:29:21  0093 21:29:23 %ATS2-S-SYSTART: Matcher [BL] ( MR10 ) Start
ed.
23-Aug-1995 21:29:22  
23-Aug-1995 21:29:22  0094 21:29:24 %ATS2-I-INDEXED: Market ( 11 ) Has Created C
ontract Index.
23-Aug-1995 21:29:23  
23-Aug-1995 21:29:23  0095 21:29:25 %ATS2-I-PRICES: Market ( 11 ) Has Dumped Pri
ces.
23-Aug-1995 21:29:23  
23-Aug-1995 21:29:23  0096 21:29:25 %ATS2-I-OPENORD: Market ( 11 ) Has Received 
Open Orders.
23-Aug-1995 21:29:23  
23-Aug-1995 21:29:23  0097 21:29:25 %ATS2-S-SYSTART: Matcher [BL] ( MR11 ) Start
ed.
23-Aug-1995 21:29:26  
23-Aug-1995 21:29:26  0098 21:29:28 %ATS2-S-SYSTART: BDB Feed ( BD01 ) Started.
23-Aug-1995 21:37:28  
23-Aug-1995 21:37:28  0099 21:37:30 %ATS2-I-LOGON: User 80,4 connected on OB01 X
25 channel 0
23-Aug-1995 21:39:59  
23-Aug-1995 21:39:59  0100 21:40:01 ATS2-I-USRLOGOFF: User 80,4 Logoff request i
n ibswit
23-Aug-1995 21:39:59  
23-Aug-1995 21:39:59  0101 21:40:01 %ATS2-I-USRLOGOF: SESCON, IBSWIT 80,4 reques
ted logoff
23-Aug-1995 21:39:59  
23-Aug-1995 21:39:59  0102 21:40:01 %ATS2-I-USRLOGOFF: Sending OB_LOGOFF to 80,4
 OB01 channel 0



What went wrong with this, and what info do you need more to trace down the problem.


Kind regards,

Johan Willems
T.RTitleUserPersonal
Name		DateLines
957.1ZENDIA::DBIGELOWInnovate, Integrate, EvaporateThu Aug 31 1995 11:1013
    Johan,
    
    If I understand you correctly, it would appear that the monitor interface 
    is not clearing part of the screen. I'll put this on our bug list.
    
    Can you have the customer try refreshing the screen using the Ctrl-w key
    combination and see if that doesn't help. Perhaps part of the scrolling
    area of the monitor window is set incorrectly.
    
    Also I presume that the customer has the latest ECO patch kit
    installed? It's on pcmsvr::cm$kits
    
    Dave
957.254625::WILLEMSJohan Willems @BRO DTN 856-8739Thu Aug 31 1995 12:036
	Dave,

	When the customer looks at the data now, some data is missing. 
	Ctrl-W did not help during the monitored period.

	Johan
957.3ZENDIA::DBIGELOWInnovate, Integrate, EvaporateThu Aug 31 1995 14:1711
    Johan,
    
       Can you ask the customer to actually verify that the data is missing
    or that we are just reporting the old data incorrectly. They can verify
    this by looking in the CONSOLE$LOGFILES:system_name.LOG.
    Be very careful not to destroy the consistancy of this file. It might
    be wise to just copy to file before reviewing it. Anyway, if data 
    is missing from the middle of this file, then it's definately gone
    and we have a logging problem.
    
    Dave
957.4No data lost, but double entry.54625::WILLEMSJohan Willems @BRO DTN 856-8739Fri Sep 01 1995 05:1047
     Dave,

	From what I can see in the logfile (looked at it with edit/read),
	No data is lost in the file, but a part has been wriiten twice.

	The monitored system (running VAX ELN) seems to number it's output
	The sequence goes like this, (only the line numbers)	

	0378
	0379
	0001
	0002
	0003
	0004
	0005
	0006
	0007
	0008
	0009
	...	(all number to 0019 are there!)
	0020
	0021
	0022
	0023
	0024
	0374	\
	0375	|
	0376	|
	0377	|
	0378	|
	0379	|
	0001	\	This part is twice in the log-file
	0002	/
	0003	|
	0004	|
	0005	|
	0006	|
	0007	|
	0008	/	\
	0025		/ This looks like the missing data
	0026


	Is it IPMT time???


Johan
957.554625::WILLEMSJohan Willems @BRO DTN 856-8739Fri Sep 01 1995 05:141
	Forgot to say that this customer is running PCM V1.6-100
957.6ZENDIA::DBIGELOWInnovate, Integrate, EvaporateTue Sep 05 1995 11:109
    Johan,
    
       Yes, it looks like it's IPMT time. There is also a command which 
    will fix bad log files and is called 'console Verify/repair'. It's 
    the only thing I can think of to help you out at this point. You will 
    have to shutdown PCM to use this. Before using the /repair option,
    try using the /full option to get a report.
    
    Dave
957.7CSC32::BUTTERWORTHGun Control is a steady hand.Wed Sep 06 1995 16:329
    Before we jump the gun with an IPMT I want to know if the output inthe
    base note has been editied in anyway/ If you look at the
    CONSOLEMANAGER* timestamps things are in order as they should be. The
    other timestamp appearss to be output from the ELN system hence my
    question, was the output modified *in any* way? At this point I'm not
    sure we have a PCM problem here!
    
    Regs,
      Dan
957.854625::WILLEMSJohan Willems @BRO DTN 856-8739Thu Sep 07 1995 08:379
Dan,

	To my knowledge, this output has not been edited. I even looked in the
	logfile of that system, and the info is bad there too.

	Regards,


	Johan
957.9CSC32::BUTTERWORTHGun Control is a steady hand.Thu Sep 07 1995 16:238
    Johan,
      Then I have to wonder if maybe someone didn't change the time on the
    ELN system or some such becuase the PCM timestamps appear to be
    correctly sequenced.
    
    REgs,
       Dan
957.1054625::WILLEMSJohan Willems @BRO DTN 856-8739Fri Sep 15 1995 11:149
	Dan,

	My understanding of this problem is that the ELN system started booting 
	shortly before 21:00. Then a part of the old output from the console (from
	around 17:00 got inserted (but we don't know how) in the input stream, and 
	then the normal input stream from the console continued. If this is correct,
	The reference date of PCM is correct (all this happened around 21:00)

	Johan.
957.11CSC32::BUTTERWORTHGun Control is a steady hand.Fri Sep 15 1995 12:3518
	Dan,

>	shortly before 21:00. Then a part of the old output from the console
    > (from around 17:00 got inserted (but we don't know how) in the input 
    >stream, and then the normal input stream from the console continued.
    > If this is correct, The reference date of PCM is correct 
    >(all this happened around  21:00)
    
    PCM uses a ring buffer to hold input from each terminal line for
    scanning and logging so this buffer is constantly being overwritten
    thus we don't store old data in memory. It's kept only in the logfile.
    Since the timestamps are in order, they would have had to have come from
    the source. The only other possibility is if the time got changed
    somehow on the PCM engine but we would have had other data out of
    order.

Regs,
      Dan
957.12It happened again54625::WILLEMSGGeert Willems MCS-BelgiumTue Oct 17 1995 07:5110
    
    
    	Hi Dan,...
    
    	It happened again (PCM V1.6 + ECO kit) ?
    	What should I do ? Open an IPMT ?
    
    	Rgds,
    
    	Geert
957.1354625::WILLEMSGGeert Willems MCS-BelgiumTue Oct 17 1995 12:05198
    
    
    

    	Hi,
    
    	This is the extract made by the customer :
    
    
    
 ?02 EXT HLT
         PC = 8000658E
  [c>>>B
 (BOOT/R5:0 EZA0,ESA0)
 
   2..
 -EZA0
   1..0..
 
 
 
 %VAXELN system initializing
 
 
  VAXELN V4.4  QBUS
 
 
 
 0001 00:00:00 %ATS2-S-SYSTART: ATS/2 VERSION 7.0F: Mar 23 1995 12:37:06
 
 0002 00:00:00 %ATS2-S-SYSTART: Console Started.
 
 0003 00:00:00 %ATS2-S-SYSTART: Logger Started.
 
 0004 20:35:04 %ATS2-I-SYSTART: ATS/2 Time set to 12-OCT-1995 20:35:04.34  
 
 0005 20:35:04 %ATS2-S-SYSTART: Initialisation Controller Started.
 
 
 VAXELN V4.4  QBUS on node ELN01
 Press <RETURN> to continue
 
 
 0006 20:35:13 %ATS2-I-SYSTART: Initialisation Controller Connected To Database 
PDB_ELN01.
 
 0007 20:35:20 %ATS2-S-SYSTART: Configuration Manager Started.
 
 0008 20:35:24 %ATS2-S-SYSTART: Session Controller Started.
 INIT SVM CODES-I: There must follow 10 DIFFERENT underlying codes
 INIT SVM CODES-I: [0000364354]
 INIT SVM CODES-I: [0001504207]
 INIT SVM CODES-I: [0000000099]
 INIT SVM CODES-I: [0000356270]
 INIT SVM CODES-I: [0000365263]
 INIT SVM CODES-I: [0000000098]
 INIT SVM CODES-I: [0000357684]
 INIT SVM CODES-I: [0000356472]
 INIT SVM CODES-I: [0000347075]
 INIT SVM CODES-I: [0000362637]
 
 0009 20:35:39 %ATS2-S-SYSTART: Outbound Logger ( LOBN ) Started.
 
 0010 20:35:43 %ATS2-S-SYSTART: Outbound Router ( OR01 ) Started.
 
 0011 20:35:45 ATS2-S-SYSTART: Broadcast Manager ( BC01 ) Started [AN/BL/RT].
 
 0012 20:35:46 %ATS2-S-SYSTART: Outbound Concentrator ( OB01 ) Started.
 
 0013 20:35:46 %ATS2-S-SYSTART: Outbound Concentrator ( OB02 ) Started.
 
 0014 20:35:47 %ATS2-S-SYSTART: Registration ( RG01 ) Started.
 
 0015 20:35:47 %ATS2-S-SYSTART: Logger Concentrator ( LOGC ) Started.
 ATS2-I-LOGGER: Make connection to Logger Client
 
 0016 20:35:47 %ATS2-S-SYSTART: Inbound Logger ( LIBN ) Started.
 
 0017 20:35:48 %ATS2-S-SYSTART: Inbound Switch ( IB01 ) [X25] Started.
 
 0018 20:35:48 %ATS2-S-SYSTART: Inbound Switch ( IB02 ) [X25] Started.
 
 0019 20:35:48 %ATS2-S-SYSTART: Registration ( RG02 ) Started.
 
 0020 20:35:48 %ATS2-S-SYSTART: Registration ( RG03 ) Started.
 
 0021 20:35:48 %ATS2-S-SYSTART: Registration ( RG04 ) Started.
 
 0022 20:35:48 %ATS2-S-SYSTART: Registration ( RG05 ) Started.
 
 0023 20:35:48 %ATS2-S-SYSTART: Registration ( RG06 ) Started.
 
 0024 20:35:48 %ATS2-S-SYSTART: Registration ( RG07 ) Started.
 
 0025 20:35:48 %ATS2-S-SYSTART: Registration ( RG08 ) Started.
 
 0026 20:35:48 %ATS2-S-SYSTART: Registration ( RG09 ) Started.
 
 0027 20:35:48 %ATS2-S-SYSTART: Registration ( RG10 ) Started.
 
 0028 20:35:48 %ATS2-S-SYSTART: Registt
 
 0361 17:44:07 %ATS2-I-USRLOGOF: SESCON, IBSWIT 220,5 requested logoff
 
 0362 17:44:07 %ATS2-I-USRLOGOFF: Sending OB_LOGOFF to 220,5 OB01 channel 0
 
 0363 17:44:29 %ATS2-S-SYSHUT: Logger Shutdown.
 
 0364 17:44:29 %ATS2-S-SYSHUT: Console Shutdown.
 ?02 EXT HLT
         PC = 8000658E
  [c>>>B
 (BOOT/R5:0 EZA0,ESA0)
 
   2..
 -EZA0
   1..0..
 
 
 
 %VAXELN system initializing
 
 
  VAXELN V4.4  QBUS
 
 
 Time set to Thu Oct 12 17:51:27 1995
 
 
 
 VAXELN V4.4  QBUS on node ELN01
 Press <RETURN> to continue
 
 ?02 EXT HLT
         PC = 8000658E
  [c>>>B
 (BOOT/R5:0 EZA0,ESA0)
 
   2..
 -EZA0
   1..0..
 
 
 
 %VAXELN system initializing
 
 
  VAXELN V4.4  QBUS
 
 
 
 0001 00:00:00 %ATS2-S-SYSTART: ATS/2 VERSION 7.0F: Mar 23 1995 12:37:06
 
 0002 00:00:00 %ATS2-S-SYSTART: Console Started.
 
 0003 00:00:00 %ATS2-S-SYSTART: Logger Started.
 
 0004 20:35:04 %ATS2-I-SYSTART: ATS/2 Time set to 12-OCT-1995 20:35:04.34  
 
 0005 20:35:04 %ATS2-S-SYSTART: Initialisation Controller Started.
 
 
 VAXELN V4.4  QBUS on node ELN01
 Press <RETURN> to continue
 
 
 0006 20:35:13 %ATS2-I-SYSTART: Initialisation Controller Connected To Database 
PDB_ELN01.
 
 0007 20:35:20 %ATS2-S-SYSTART: Configuration Manager Started.
 
 0008 20:35:24 %ATS2-S-SYSTART: Session Controller Started.
 INIT SVM CODES-I: There must follow 10 DIFFERENT underlying codes
 INIT SVM CODES-I: [0000364354]
 INIT SVM CODES-I: [0001504207]
 INIT SVM CODES-I: [0000000099]
 INIT SVM CODES-I: [0000356270]
 INIT SVM CODES-ration ( RG11 ) Started.
 
 0029 20:35:55 %ATS2-S-SYSTART: Clearing Link [ARCH] Started.
 
 0030 20:35:56 %ATS2-S-SYSTART: Message Server Started.
 
 0031 20:35:56 %ATS2-S-SYSTART: Broadcast Logger ( LOBC ) Started.
 
 0032 20:38:52 %ATS2-S-SYSTART: Validation ( VN01 ) [BE]  Started.
 
 0033 20:42:21 %ATS2-S-SYSTART: Validation ( VN02 ) [BE]  Started.
 
 0034 20:44:57 %ATS2-S-SYSTART: Validation ( VN03 ) [BE]  Started.
 
 0035 20:47:17 %ATS2-S-SYSTART: Validation ( VN04 ) [BE]  Started.
 
 0036 20:50:43 %ATS2-S-SYSTART: Validation ( VN05 ) [BE]  Started.
 
 0037 20:53:24 %ATS2-S-SYSTART: Validation ( VN06 ) [BE]  Started.
957.1429067::BUTTERWORTHGun Control is a steady hand.Tue Oct 17 1995 18:416
    Geert,
      I really don't think we have a PCM problem here. Have you run the
    logfile verification against the logfiles yet?
    
    Regs,
      Dan
957.15console verify output54625::WILLEMSGGeert Willems MCS-BelgiumWed Oct 18 1995 09:11154
    
    
	Hi Dan,
    
    	This is the output that I have received from the customer.
    	Seems to be OK !
    
    	Rgds,
    
    	Geert
    
-----------------------------------------------------------------------------------------------------
I have included in this reply the output of 'console verify eln01/full'
file named CONSOLE$VERIFY__ELN01.REPORT:


 Starting Host ELN01

Loading : CONSOLE$LOGFILES:ELN01. fileset 
          LOG file
Test 1, Check to ensure that there are the same number of timestamp
        records in the .TIMES file as there are <NL> characters in
        the .LOG file, there should be a one-one match.
Test 1 : Passed.
 <985> Timestamps in the TIMES file
Test 2, Check to ensure that the first timestamp record points to
        offset 0 in the .LOG file
Test 2 : Passed.
Test 3, Check to ensure that all our timestamp records point
        somewhere within the logfile and that they point to
        newline characters
Test 3 : Passed.
Test 4, Check to ensure that we dont have log records on the end of
        the file for which there are no timestamp records
Test 4 : Passed.
Test 5, Check that the .TIME and .LOG file pointers for each event
        record fall within the bounds of the relevant file.
        Also check the length values match in the record.
Test 5 : Passed.
Loading : CONSOLE$ROOT:[ARCHIVE]ELN01.9510100530_TO_9510110002_ fileset 
          LOG file
Test 1, Check to ensure that there are the same number of timestamp
        records in the .TIMES file as there are <NL> characters in
        the .LOG file, there should be a one-one match.
Test 1 : Passed.
 <762> Timestamps in the TIMES file
Test 2, Check to ensure that the first timestamp record points to
        offset 0 in the .LOG file
Test 2 : Passed.
Test 3, Check to ensure that all our timestamp records point
        somewhere within the logfile and that they point to
        newline characters
Test 3 : Passed.
Test 4, Check to ensure that we dont have log records on the end of
        the file for which there are no timestamp records
Test 4 : Passed.
Test 5, Check that the .TIME and .LOG file pointers for each event
        record fall within the bounds of the relevant file.
        Also check the length values match in the record.
Test 5 : Passed.
Loading : CONSOLE$ROOT:[ARCHIVE]ELN01.9510110530_TO_9510120001_ fileset 
          LOG file
Test 1, Check to ensure that there are the same number of timestamp
        records in the .TIMES file as there are <NL> characters in
        the .LOG file, there should be a one-one match.
Test 1 : Passed.
 <768> Timestamps in the TIMES file
Test 2, Check to ensure that the first timestamp record points to
        offset 0 in the .LOG file
Test 2 : Passed.
Test 3, Check to ensure that all our timestamp records point
        somewhere within the logfile and that they point to
        newline characters
Test 3 : Passed.
Test 4, Check to ensure that we dont have log records on the end of
        the file for which there are no timestamp records
Test 4 : Passed.
Test 5, Check that the .TIME and .LOG file pointers for each event
        record fall within the bounds of the relevant file.
        Also check the length values match in the record.
Test 5 : Passed.
Loading : CONSOLE$ROOT:[ARCHIVE]ELN01.9510120530_TO_9510130001_ fileset 
          LOG file
Test 1, Check to ensure that there are the same number of timestamp
        records in the .TIMES file as there are <NL> characters in
        the .LOG file, there should be a one-one match.
Test 1 : Passed.
 <881> Timestamps in the TIMES file
Test 2, Check to ensure that the first timestamp record points to
        offset 0 in the .LOG file
Test 2 : Passed.
Test 3, Check to ensure that all our timestamp records point
        somewhere within the logfile and that they point to
        newline characters
Test 3 : Passed.
Test 4, Check to ensure that we dont have log records on the end of
        the file for which there are no timestamp records
Test 4 : Passed.
Test 5, Check that the .TIME and .LOG file pointers for each event
        record fall within the bounds of the relevant file.
        Also check the length values match in the record.
Test 5 : Passed.
Loading : CONSOLE$ROOT:[ARCHIVE]ELN01.9510130005_TO_9510140001_ fileset 
          LOG file
Test 1, Check to ensure that there are the same number of timestamp
        records in the .TIMES file as there are <NL> characters in
        the .LOG file, there should be a one-one match.
Test 1 : Passed.
 <759> Timestamps in the TIMES file
Test 2, Check to ensure that the first timestamp record points to
        offset 0 in the .LOG file
Test 2 : Passed.
Test 3, Check to ensure that all our timestamp records point
        somewhere within the logfile and that they point to
        newline characters
Test 3 : Passed.
Test 4, Check to ensure that we dont have log records on the end of
        the file for which there are no timestamp records
Test 4 : Passed.
Test 5, Check that the .TIME and .LOG file pointers for each event
        record fall within the bounds of the relevant file.
        Also check the length values match in the record.
Test 5 : Passed.
Loading : CONSOLE$ROOT:[ARCHIVE]ELN01.9510160530_TO_9510170001_ fileset 
          LOG file
Test 1, Check to ensure that there are the same number of timestamp
        records in the .TIMES file as there are <NL> characters in
        the .LOG file, there should be a one-one match.
Test 1 : Passed.
 <810> Timestamps in the TIMES file
Test 2, Check to ensure that the first timestamp record points to
        offset 0 in the .LOG file
Test 2 : Passed.
Test 3, Check to ensure that all our timestamp records point
        somewhere within the logfile and that they point to
        newline characters
Test 3 : Passed.
Test 4, Check to ensure that we dont have log records on the end of
        the file for which there are no timestamp records
Test 4 : Passed.
Test 5, Check that the .TIME and .LOG file pointers for each event
        record fall within the bounds of the relevant file.
        Also check the length values match in the record.
Test 5 : Passed.

 Ended Host ELN01


I think you will find no errors,

Can you give better arguments if you still think these
problems are due to ELN01 hardware errors 
    ---------------------------------------------------------------------------------------------
957.1629067::BUTTERWORTHGun Control is a steady hand.Wed Oct 18 1995 13:2923
    >Can you give better arguments if you still think these
    >problems are due to ELN01 hardware errors
    
    At this point we have no evidence to say it is a PCM problem. SO far
    you have proven that the logfiles are not corrupted *and* that the
    PCM timestamps are in order. The only timestamps that aren't in order
    are those provided by the ELN system. Note also that the ring buffer
    that PCM uses to log console data is not very large and in no way could
    it retain data for that long of a period of time. With the data flow
    during a bootstrap it's already been written over several times  before
    you see the wierd timestamps from the ELN system. So if PCM cannot
    buffer it then we would have to consider logfile corruption and again
    the logfile verification has already shown that the files are
    healthy.
    
    If this only happens during a bootstrap, I would suggest finding a
    "Y" cable so that console output could be sent to both a hardcopy
    device and PCM silmulatenously and turn it one whenever the system
    is rebooted. If you see the same output on the printer then you have
    definitive proof that it isn't the fault of PCM. 
    
    REgards,
      Dan