OctetView
0x00000…00100 (0, 0, 0) Sector 00664130303636 ┆ fA0066A ┆
0x00100…00200 (0, 0, 1) Sector 00000000000000 ┆ ┆
0x00200…00300 (0, 0, 2) Sector ff00fcff00e0ff ┆ | ` ~ x ┆
0x00300…00306 (0, 0, 3) WangDocument {d00=0x10, d01=0x76, d02=0x41, ptr=(65,0, 0), d05=0x00}
0x00306…0030c WangDocument {d00=0x10, d01=0x94, d02=0x41, ptr=(34,0, 0), d05=0x00}
0x0030c…00312 WangDocument {d00=0x11, d01=0x00, d02=0x41, ptr=(66,0, 0), d05=0x00}
0x00312…00318 WangDocument {d00=0x11, d01=0x03, d02=0x41, ptr=(66,0, 8), d05=0x00}
0x00318…0031e WangDocument {d00=0x11, d01=0x12, d02=0x41, ptr=(58,0, 8), d05=0x00}
0x0031e…00324 WangDocument {d00=0x11, d01=0x13, d02=0x41, ptr=(64,0, 0), d05=0x00}
0x00324…00340 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ ┆
0x00340…00360 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ ┆
[…0x4…]
0x003e0…00400 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 24 ┆ $┆
0x00400…00500 (0, 0, 4) Sector 00000000000000 ┆ ┆
0x00500…00600 (0, 0, 5) Sector 00664130303636 ┆ fA0066A ┆
0x00600…00700 (0, 0, 6) Sector 421c402600415b ┆B @& A[' X% % PO P ; A' C f x f V W O 7 :d? e8 1113A f L < {C < { ; 1 ` l! bP b ^ 9 : 8 x $ 1076A1094A1100A1103A1112A1113A ┆
0x00700…00800 (0, 0, 7) Sector 00000000000000 ┆ ┆
[…0x8…]
0x01000…01100 (1, 0, 0) WangDocumentBody
[…0x5…]
0x01600…01700 (1, 0, 6) Sector 00000000000000 ┆ ┆
[…0x1…]
0x01800…01900 (1, 0, 8) WangDocumentBody
[…0x7…]
0x02000…02100 (2, 0, 0) Sector 0201ff00111341 ┆ A LENGTH User Area LENGTH message format between WDP and PUs (ONLINE) KIND = ACK, NACK, MESSAGE, RESET LINE # = 1..5; type of message SERIAL NUMBER = 0..255; con┆
0x02100…02200 (2, 0, 1) Sector 0202ec00111341 ┆ l Anected to the LINE LENGTH = Number of bytes in the used area The header of the message is set by the PU driver, when the message is sent to the PU. In the same way, the IOC sets the header of the message sent to the WDP. -TRANS PROCEDURE ┆
0x02200…02300 (2, 0, 2) Sector 0203ff00111341 ┆ A 1 4.2.8.4.6 Message Format Used Internally in the WDP CHAIN POINTER LINE # SERIAL NU┆
0x02300…02400 (2, 0, 3) Sector 0204ff00111341 ┆ AMBER USER STATUS SENDER STATUS LENGTH User Area CHAIN POINTER; used by KERNEL. LINE # = 1...N; type of message SERIAL NUMBER = 0...255, con┆
0x02400…02500 (2, 0, 4) Sector 0205f300111341 ┆ s Anected to the LINE # USER STATUS = ACK, NACK, QUEUE SENDER STATUS = QUEUE, ACK LENGTH = Number of bytes in the user area. The header of the message format used, internally in the WDP, is set by the originator of the message. le. 4.2.8┆
0x02500…02600 (2, 0, 5) Sector 0206ff00111341 ┆ A 1 4.2.8.4.7 Control Message to CCB CHAIN POINTER POINTER TO CONTROL TABLE ┆
0x02600…02700 (2, 0, 6) Sector 0207e400111341 ┆ d A STATUS CHAIN POINTER : User by the Kernel POINTER TO CONTROL-TABLE : the crate to be controlled : status to be set, via the control configuration bus, in the crate definedNCTION KEY TO PU VDU┆
0x02700…02800 (2, 0, 7) Sector 00004900111341 ┆ I A in the control table. 4.2.8.5 Interfaces Ref. sec. 4.1.6. 4.2.8.4.2 Digital Output Control Table CRATE ADDRESS PORT POINTER STATUS CRATE ADDRESS ┆
0x02800…02900 (2, 0, 8) WangDocumentBody
[…0x2…]
0x02b00…02c00 (2, 0, 11) Sector 020cff00107641 ┆ vA 1 Reconfiguration due to operator commands or an error includes: - updating the HW and SW configuration tables - updating the WDP-VDU system configuration (via a system connectio┆
0x02c00…02d00 (2, 0, 12) Sector 020dff00107641 ┆ vAn) - issuing of WDP-LP error reports (via a system connection) - sending of commands directly to the WDP (via a system connection) - starting/stopping subprocesses The CFH sends replies to the CMI, when having executed an operator command. ┆
0x02d00…02e00 (2, 0, 13) Sector 020eff00107641 ┆ vA The CFH sends replies to the TEP, when having executed a circuit command. Reconfigurations related to the offline disk are sent to TEP (in a supervisor subprocess). 4.1.3.2 CMI Data Flow and Control Logic Figure 4.1.3.2-1 overleaf defines th┆
0x02e00…02f00 (2, 0, 14) Sector 020fff00107641 ┆ vAe environment for the CMI process. The CMI process receives operational commands (e.g. start-up) from COPSY in its input queue CMIQ and sends replies to the CMIRQ at COPSY. The CMI receives operator commands via the WDP-VDU command split (refer s┆
0x02f00…03000 (2, 0, 15) Sector 0200ff00107641 ┆ vAection 4.1.4.3.2) and operator command formats via the format split. CMI validates operator commands against the HW configuration table. Having validated a command COPSY is requested via the SYQ to execute the command. COPSY sends a command execu┆
0x03000…03100 (3, 0, 0) WangDocumentBody
[…0x86…]
0x0b700…0b800 (11, 0, 7) Sector 0000b700110341 ┆ 7 A 1 The associated operation on 18 words contains a copy of the input data as described in section 4.2.4.5.1. XEC-CHECKSUMMING, SEND-REPLY CLOSE DOWN? CLOSE-DOWN-OLD ┆
0x0b800…0b900 (11, 0, 8) WangDocumentBody
[…0xc…]
0x0c500…0c600 (12, 0, 5) Sector 0c06ff00110041 ┆ A 1 4.1.6.3.2.7 Number of Last Error Report TYPE CMD NUMBER TYPE = WDP-CMD CMD = REPORT-NUMBER NUMBER = Number┆
0x0c600…0c700 (12, 0, 6) Sector 0c07f900110041 ┆ y A of last error report printed. Description When the LP or WDP are back in service, the number of the last error report printed is sent to the WDP. Error reports are printed on the supervisor LP if the operator LP is "out of service". ┆
0x0c700…0c800 (12, 0, 7) Sector 0b08ff00110041 ┆ A 1 4.1.6.3.3 CMI to COPSY Interface 4.1.6.3.3.1 CMI commands to COPSY Q INFO Q BUFFER TYPE CMD PARAMET┆
0x0c800…0c900 (12, 0, 8) WangDocumentBody
[…0x157…]
0x22000…22100 (34, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(34,0, 1), len=0xff, h3=41109441}, f00=»1094A «, f01=»CPS/SDS/004 «, f02=»vhn «, f03=»FH «, f04=»fra table of content «, f05=29-06-81 14:47, f06=» 8 «, f07=»17 «, f08=» 31364 «, f09=12-10-81 10:44, f10=» «, f11=»00 «, f12=» 26 «, f13=29-07-81 11:14, f14=02-03-82 09:40, f15=»0066A «, f16=» 75 «, f17=» 13 «, f18=»49 «, f19=» 1092 «, f20=» 41131 «, f21=» «, f22=» «, f99=210010000110068610110480aaca15050000000000000137035e01df}
0x22100…22200 (34, 0, 1) WangDocumentBody
[…0x186…]
0x3a800…3a900 (58, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(58,0, 9), len=0xff, h3=41111241}, f00=»1112A «, f01=»CPS/SDS/004 «, f02=»sdv «, f03=»BHJ «, f04=»4.2.7 «, f05=02-07-81 10:16, f06=» 5 «, f07=»29 «, f08=» 24685 «, f09=24-02-82 10:47, f10=» «, f11=»01 «, f12=» 74 «, f13=24-07-81 12:17, f14=02-03-82 09:41, f15=»0066A «, f16=» 38 «, f17=» 8 «, f18=»32 «, f19=» 348 «, f20=» 26317 «, f21=» «, f22=» 0 «, f99=730010000110066610110480aaca15050000000000000037037f00df}
0x3a900…3aa00 (58, 0, 9) WangDocumentBody
[…0x56…]
0x40000…40100 (64, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(64,0, 1), len=0xff, h3=41111341}, f00=»1113A «, f01=»CPS/SDS/004 «, f02=»tdh «, f03=»BHJ «, f04=»fra fig 4.2.8.15-1 «, f05=02-07-81 10:39, f06=» 5 «, f07=»36 «, f08=» 14583 «, f09=24-07-81 14:04, f10=» «, f11=»00 «, f12=» 14 «, f13=24-07-81 14:05, f14=02-03-82 09:42, f15=»0066A «, f16=» 45 «, f17=» 7 «, f18=»52 «, f19=» 172 «, f20=» 19725 «, f21=» «, f22=» «, f99=020010000110066610110480aaca15050000000000000037035800df}
0x40100…40200 (64, 0, 1) WangDocumentBody
[…0xe…]
0x41000…41100 (65, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(65,0, 1), len=0xff, h3=41107641}, f00=»1076A «, f01=»CPS/SDS/004 «, f02=»sdv «, f03=»FH «, f04=»4-4.1.3.3 Sys. Statu «, f05=23-06-81 10:30, f06=» 5 «, f07=»41 «, f08=» 27623 «, f09=18-02-82 10:10, f10=» «, f11=»00 «, f12=» 5 «, f13=24-07-81 14:47, f14=02-03-82 09:39, f15=»0066A «, f16=» 50 «, f17=» 9 «, f18=»46 «, f19=» 412 «, f20=» 33190 «, f21=» «, f22=» @ «, f99=990010000110066610110480aaca15050000000000000037039b00df}
0x41100…41200 (65, 0, 1) WangDocumentBody
[…0xe…]
0x42000…42100 (66, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(66,0, 1), len=0xff, h3=41110041}, f00=»1100A «, f01=»CPS/SDS/004 «, f02=»tdh «, f03=»fh «, f04=»fra 4.1.3.4 «, f05=30-06-81 12:26, f06=» 1 «, f07=»11 «, f08=» 6578 «, f09=23-07-81 09:37, f10=» «, f11=»12 «, f12=» 126 «, f13=23-07-81 10:39, f14=02-03-82 09:41, f15=»0066A «, f16=» 59 «, f17=» 11 «, f18=»46 «, f19=» 504 «, f20=» 34872 «, f21=» «, f22=» P «, f99=050010000110066610110480aaca1505000000000000003703a500df}
0x42100…42200 (66, 0, 1) WangDocumentBody
[…0x6…]
0x42800…42900 (66, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(66,0, 9), len=0xff, h3=41110341}, f00=»1103A «, f01=»CPS/SDS/004 «, f02=»vhn «, f03=»FH «, f04=»fra 4.2.1 «, f05=01-07-81 10:34, f06=» 6 «, f07=»53 «, f08=» 27089 «, f09=24-07-81 10:33, f10=» «, f11=»01 «, f12=» 17 «, f13=24-07-81 11:20, f14=02-03-82 09:41, f15=»0066A «, f16=» 54 «, f17=» 7 «, f18=»51 «, f19=» 400 «, f20=» 28163 «, f21=» «, f22=» «, f99=400010000110066610110480aaca15050000000000000037039800df}
0x42900…42a00 (66, 0, 9) WangDocumentBody
[…0x6…]
0x43000…43100 (67, 0, 0) Sector 43016700107641 ┆C g vAg to the checkpoint record type and an acknowledgement is sent to the active PU via the TDX bus. ~ B 3: = R 3*$<MMY *%<MMY !\<6 C 3M, !\<6 : =~ B 5: = R$3C/4!e=6 !f=6 !g=6 !h=6 Ml+M;) RE3C#4: 2i=:g=~ JV3C/4!"<6 #6 MB&! =6 !,<6 :]=2'< AMD MB&!,<6 ! ┆
0x43100…43200 (67, 0, 1) Sector 4302ff00107641 ┆C vA 1 1 FCT NO. TITLE ┆
0x43200…43300 (67, 0, 2) Sector 4303ff00107641 ┆C vA DESCRIBED IN SECTION 1 Overview 2.2.1 2 Check point transm. 2.2.1.1 4.1.1.1 3 Checkpoint reception 2.2.1.2 4.1.1.2 4 Online diagnostics 2.2.1.3 4.1.1.3 5 Li┆
0x43300…43400 (67, 0, 3) Sector 4304ff00107641 ┆C vAne M&C 2.2.1.4 4.1.1.4 6 Technical error processing 2.2.1.5 4.1.1.5 7 Operator commands 2.2.1.6 4.1.1.6 8 Offline PU operation 2.2.1.7 4.1.1.7 9 WDP FW 2.2.1.8 4.1.1.8 10 Bootload 2.2.2.1.1.1 11 Start active 2.2.2.1.1.2 4.1.┆
0x43400…43500 (67, 0, 4) Sector 4305ff00107641 ┆C vA1.6.3.1 12 Common start active 4.1.1.6.3.1 13 Start standby 2.2.2.1.1.2 4.1.1.6.3.3 14 Common start standby 4.1.1.6.3.3 15 Recovery 2.2.2.2 16 Close active 2.2.2.1.2.1 4.1.1.6.3.2 17 Close standby 2.2.2.1.2.2 18 Validity checks┆
0x43500…43600 (67, 0, 5) Sector 4306ff00107641 ┆C vA 2.2.2.4 19 Data collection 2.2.2.5 20 Own error handling 2.2.2.3 21 Peripheral recon- figuration 4.1.1.5 22 Common peripheral reconfiguration 4.1.1.5 23 Common line M&C 4.1.1.4.2 24 Common SSC functions 4.1.1.9.1 ┆
0x43600…43700 (67, 0, 6) Sector 43077700107641 ┆C w vA Figure 4.1.1-1 SSC Function to Section Table 5 41 27623 24 07 81 14 45 00 2 24 07 81 14 47 24 07 81 15 00 0066A 50 9 46 456 33185 @ f *J 7 & _┆
0x43700…43800 (67, 0, 7) Sector 2a08ff00107641 ┆* vA 1 4.1.1.3 On-Line Diagnostics The functions covered by on-line diagnostic are defined in section 2.2.1.3. 4.1.1.4 Line Monitoring and Control The line M&C functions are depicte┆
0x43800…43900 (67, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(67,0, 9), len=0xff, h3=41107641}, f00=»1076A «, f01=»System Status and Control «, f02=»sdv «, f03=»FH «, f04=»SDS/004 4-4.1.3.3 «, f05=23-06-81 10:30, f06=» 5 «, f07=»41 «, f08=» 27623 «, f09=24-07-81 14:45, f10=» «, f11=»00 «, f12=» 2 «, f13=24-07-81 14:47, f14=24-07-81 15:00, f15=»0066A «, f16=» 50 «, f17=» 9 «, f18=»46 «, f19=» 456 «, f20=» 33185 «, f21=» «, f22=» @ «, f99=990010000110066610110480aaca15050000000000000037039b00df}
0x43900…43a00 (67, 0, 9) Sector 430a3200107641 ┆C 2 vA C C C C * * * * DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatte┆
0x43a00…43b00 (67, 0, 10) Sector 430b9200107641 ┆C vA 1 CPS/SDS/004 FH/810801 SYSTEM STATUS AND CONTROL CAMPS *-:!<~ B%-!/=6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x43b00…43c00 (67, 0, 11) Sector 430cff00107641 ┆C vA 1 4 PACKAGE DESIGN 4.1 Package Overview 4.1.1 Functional Specification Sections 4.1.1.1 to 4.1.1.9 describes the functions derived in section 2.2.1 and 2.2.2 to a level of d┆
0x43c00…43d00 (67, 0, 12) Sector 430dff00107641 ┆C vAetail, which enables an allocation of the functions to process or coroutine software structures. Section 4.1.1.9 describes requirements derived from the functional responsibilities defined in section 2.2.2. The sections, in which SSC functions (┆
0x43d00…43e00 (67, 0, 13) Sector 430eff00107641 ┆C vAidentified by a number) are described, are defined in figure 4.1.1-1. 4.1.1.1 Checkpoint Transmission SSC receives checkpoint records from MMS, LOG and TIMER - MON and transfers the checkpoints records to the standby PU via the TDX-bus. Havi┆
0x43e00…43f00 (67, 0, 14) Sector 430fff00107641 ┆C vAng transmitted a record, an acknowledgement from the SB PU is awaited and a reply is sent to the caller. The SSC does not await acknowledgement before transmitting a new checkpoint (CP) record. However, only a limited number of outstanding acknow┆
0x43f00…44000 (67, 0, 15) Sector 4300ff00107641 ┆C vAledgements are allowed. 4.1.1.2 Checkpoint Reception SSC receives checkpoint records from the active PU. The checkpoint records are received via the TDX bus from the active PU. Having received a checkpoint record, a table is updated accordin┆
0x44000…44100 (68, 0, 0) Sector 44018400110041 ┆D A 1 Fig. 4.1.3.5-1 Watchdog Software Structure Overview 6 C 3M, !\<6 : =~ B 5: = R$3C/4!e=6 !f=6 !g=6 !h=6 Ml+M;) RE3C#4: 2i=:g=~ JV3C/4!"<6 #6 MB&! =6 !,<6 :]=2'< AMD MB&!,<6 ! ┆
0x44100…44200 (68, 0, 1) Sector 4402ff00110041 ┆D A 1 4.1.3.5.1 Input to the WDP from a PU The PU-IN driver recognizes three types of PU input: - VDU data - LP data - WDP data and sends the data to three associated queues: - ┆
0x44200…44300 (68, 0, 2) Sector 4403ff00110041 ┆D AVDU queue - LP queue - PU queue VDU data are analyzed in the VDU-HANDLER and LP-HANDLER process respectively and printed by the corresponding VDU and LP drivers. The LP-HANDLER synchronizes LP output. The WDP data in the PUQ contain keep alive┆
0x44300…44400 (68, 0, 3) Sector 4404ff00110041 ┆D A messages and direct WDP commands. The keep alive messages are handled in the PU-HANDLER, whereas WDP commands are executed in the SYS M&C process. The non-arrival of a keep alive message is signalled to the SYS M&C process by the PU-HANDLER. 4.1┆
0x44400…44500 (68, 0, 4) Sector 4405ff00110041 ┆D A.3.5.2 Input to the WDP from a VDU VDU input is directed to the VDU queue at the VDU-HANDLER by a VDU-IN driver. Three types of VDU input are handled: - offline PU commands - direct WDP commands - online PU commands. The VDU-HANDLER sends on┆
0x44500…44600 (68, 0, 5) Sector 4406a100110041 ┆D ! Aline and offline PU data to a PU-OUT driver. Direct WDP commands are executed in the SYS M&C process. Offline commands are copied at the record WDP-LP. - non-line processes are started/closed via separate request queues and a single reply queue. ┆
0x44600…44700 (68, 0, 6) Sector 4407ff00110041 ┆D A 1 4.1.3.5.3 CCB Scanning The CCB driver periodically scans the CAMPS crates. Exceptions are reported to the SYS M&C process, which determines further actions, e.g. an active PU erro┆
0x44700…44800 (68, 0, 7) Sector 2a00ff00110041 ┆* Ar is handled by disabling the AC PU and by commanding the SB PU to become active. Peripheral device exceptions are reported to the active PU. 4.1.3.5.4 Buffer Handling The application processes communicate via queue semaphores containing buff┆
0x44800…44900 (68, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(68,0, 9), len=0xff, h3=41110041}, f00=»1100A «, f01=»CPS/SDS/004 «, f02=»tdh «, f03=»fh «, f04=»fra 4.1.3.4 «, f05=30-06-81 12:26, f06=» 1 «, f07=»11 «, f08=» 6578 «, f09=23-07-81 09:37, f10=» «, f11=»12 «, f12=» 126 «, f13=23-07-81 10:39, f14=24-07-81 15:01, f15=»0066A «, f16=» 59 «, f17=» 11 «, f18=»46 «, f19=» 504 «, f20=» 34872 «, f21=» «, f22=» P «, f99=050010000110066610110480aaca1505000000000000003703a500df}
0x44900…44a00 (68, 0, 9) Sector 440a3b00110041 ┆D ; A D D D D D D D * * * ) ) ) ) ) ) ) ) ) ) ( ( ( ( ( ' ' ' ' ' & & & & & % % % % % $ $ $ $ # # # # # # " " " DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: ┆
0x44a00…44b00 (68, 0, 10) Sector 440b9200110041 ┆D A 1 CPS/SDS/004 FH/810801 SYSTEM STATUS AND CONTROL CAMPS *-:!<~ B%-!/=6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x44b00…44c00 (68, 0, 11) Sector 440cff00110041 ┆D A 1 4.1.3.4 OLD Data Flow and Control Logic Figure 4.1.3.4-1 overleaf defines online diagnostics data flow and control logic. OLD receives operational commands from COPSY in the OLDQ.┆
0x44c00…44d00 (68, 0, 12) Sector 440d7f00110041 ┆D A Also, supervisor and periodic request are entered in the OLDQ. OLD replies to operational and supervisor requests. 2#<! <6 M)(I:g=~ J /Mj'! "(=~ R*/!/=6jM (*(=~ R;/!/=6nM (*(=~ RM/!/=6iM (*(=~ R`/!/=6WM (*(=~ Rt/!/=6lM (*(=~ R ┆
0x44d00…44e00 (68, 0, 13) Sector 440e7100110041 ┆D q A 1 Fig. 4.1.3.4-1 OLD Block Diagram <6 M1' R 0C 0! <6 M1' R 0C 0! <6 M1' Z 0CR0Mc&!.=6 ! <6 M1' R40C.1! <6 M1' RC0C.1! <6 M1' RR0C.1!$<5CQ0!$<6 !&<6 Mc&! "(=6 E '<M% ! "2<┆
0x44e00…44f00 (68, 0, 14) Sector 440fff00110041 ┆D A 1 4.1.3.5 WDP Data Flow and Control Logic Figure 4.1.3.5-1 overleaf illustrates the WDP data flow and control logic. The WDP standard software drivers are shown outside the box, w┆
0x44f00…45000 (68, 0, 15) Sector 4400b600110041 ┆D 6 Ahereas the four application software processes are shown within the box. The following sections handle input to the WDP from: - a PU - a VDU - the CCB scanning driver. <2> I E*#<& "< DM L<M% :#<F 2#<> I:g= Ro2M/2 Rl2> IC13!?=4~~ B|2> I:A=!┆
0x45000…45100 (69, 0, 0) Sector 00000000000000 ┆ ┆
[…0x7f…]
