OctetView
0x00000…00100 (0, 0, 0) Sector 03064130333036 ┆ A0306A ┆
0x00100…00200 (0, 0, 1) Sector 00000000000000 ┆ ┆
0x00200…00300 (0, 0, 2) Sector ff00f880ffc0ff ┆ x @ p | @ @ ` | ` p ┆
0x00300…00306 (0, 0, 3) WangDocument {d00=0x28, d01=0x94, d02=0x41, ptr=(53,0, 8), d05=0x00}
0x00306…0030c WangDocument {d00=0x32, d01=0x31, d02=0x41, ptr=(33,0, 8), d05=0x00}
0x0030c…00312 WangDocument {d00=0x32, d01=0x71, d02=0x41, ptr=(36,0, 0), d05=0x00}
0x00312…00318 WangDocument {d00=0x33, d01=0x48, d02=0x41, ptr=(61,0, 0), d05=0x00}
0x00318…0031e WangDocument {d00=0x33, d01=0x99, d02=0x41, ptr=(42,0, 0), d05=0x00}
0x0031e…00324 WangDocument {d00=0x34, d01=0x00, d02=0x41, ptr=(55,0, 8), d05=0x00}
0x00324…0032a WangDocument {d00=0x34, d01=0x01, d02=0x41, ptr=(56,0, 8), d05=0x00}
0x0032a…00330 WangDocument {d00=0x34, d01=0x02, d02=0x41, ptr=(31,0, 0), d05=0x00}
0x00330…00336 WangDocument {d00=0x36, d01=0x53, d02=0x41, ptr=(55,0, 0), d05=0x00}
0x00336…0033c WangDocument {d00=0x38, d01=0x54, d02=0x41, ptr=(41,0, 8), d05=0x00}
0x0033c…00342 WangDocument {d00=0x38, d01=0x56, d02=0x41, ptr=(59,0, 8), d05=0x00}
0x00342…00348 WangDocument {d00=0x38, d01=0x58, d02=0x41, ptr=(66,0, 0), d05=0x00}
0x00348…0034e WangDocument {d00=0x38, d01=0x59, d02=0x41, ptr=(69,0, 0), d05=0x00}
0x0034e…00360 38 59 41 45 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆8YAE ┆
0x00360…00380 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 ┆ ┆
[…0x3…]
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 4e ┆ N┆
0x00400…00500 (0, 0, 4) Sector 00000000000000 ┆ ┆
0x00500…00600 (0, 0, 5) Sector 03064130333036 ┆ A0306A ┆
0x00600…00700 (0, 0, 6) Sector 421c402600415b ┆B @& A[' X% % PO P ; 3HA} C g x g V Ww O 8 :} [,4 > 3348A g J < {C < { ; 8 c TuL Tux V 0 9 : 8 4 t xyyx yy ~ q-q.q/q n9q!q"q#q$X- ┆
0x00700…00800 (0, 0, 7) Sector 00000000000000 ┆ ┆
[…0x8…]
0x01000…01100 (1, 0, 0) WangDocumentBody
[…0x4…]
0x01500…01600 (1, 0, 5) Sector 00000000000000 ┆ ┆
[…0x2…]
0x01800…01900 (1, 0, 8) WangDocumentBody
0x01900…01a00 (1, 0, 9) Sector 010a9800339941 ┆ 3 A MON REGION, RPUT 7 MON REGION,RLEAVE 0 MON TERMINATE 3.9 Listing References Please refer to chapt. 5. 4 QUALITY ASSURANCE N/A a areas) TOP OF MEMORY (When the data area is laid out, the pointers to next the free memory areas on┆
0x01a00…01b00 (1, 0, 10) Sector 010bff00339941 ┆ 3 A W 5 PREPARATIONS FOR DELIVERY Generation of Object Code File: . Copy the source directory of the actual version into a work directory. . Activate the command file MTCB DATAINI┆
0x01b00…01c00 (1, 0, 11) Sector 010c8200339941 ┆ 3 AT.CR . Activate the command file MTCB DATAINIT.CP . Activate the command file MTCB DATAINIT.LO The object code reacess. In ref. I chapt. 3.4 the complete layout of the MTCB data are as shown. This chapter contains a brief description o┆
0x01c00…01d00 (1, 0, 12) Sector 0000bc00339941 ┆ < 3 Ady for installation is now available in the file MTCB DATAINIT.S. LISTINGS The compilation and linker printfiles may be obtained by activating the command file MTCB DATAINIT.PP. MTCB 1, containing the configuration parameters for the MTCB data a┆
0x01d00…01e00 (1, 0, 13) Sector 00000000000000 ┆ ┆
[…0x2…]
0x02000…02100 (2, 0, 0) WangDocumentBody
[…0x9…]
0x02a00…02b00 (2, 0, 10) Sector 020b0d00334841 ┆ 3HA N/A 3.4 Data Organization Please refer to: Source listings and FIKS File Generators PSP FIX/1200/PSP/0042 The utility procedure ITERR (ref. 3.1.9.1) is called by this procedur┆
0x02b00…02c00 (2, 0, 11) Sector 020cbc00334841 ┆ < 3HA W 5 PREPARATION FOR DELIVERY Please refer to: FIKS S/W Configuraton Control Lib. Descr. Doc. FIX/1000/EWP/0080 s The IWAIT Procedure interfaces to the following monitor procedu┆
0x02c00…02d00 (2, 0, 12) Sector 020d5800334841 ┆ X 3HA W 6 NOTES N/A e Characteristic N/A 3.2.9.3.1 Internal Interface PSM MESS Procedure is invoked by: TEP INIT REST ref. 3.1.4 INT TERM ref. 3.1.6 EVENT HANDLER┆
0x02d00…02e00 (2, 0, 13) Sector 020e5c00334841 ┆ \ 3HA W 7 APPENDICES N/AN/A S: None 3.2.9.3.2 External Interface The following monitor procedures are called: MON SENDMESSAGE g monitors are called: MON REGION MON ERROR REST┆
0x02e00…02f00 (2, 0, 14) Sector 0000c400334841 ┆ D 3HA W W The following format is used: ?-X: YYY where X will ide┆
0x02f00…03000 (2, 0, 15) Sector 00000000000000 ┆ ┆
0x03000…03100 (3, 0, 0) WangDocumentBody
[…0x12b…]
0x15c00…15d00 (21, 0, 12) Sector 150de700340041 ┆ g 4 A.CR SEND REPORT.CP SEND REPORT.LO The object code ready for installation is now available in the file SEND REPORT.C. LISTINGS By activating the command file SEND REPORT.PP, the compilation and Linkters for the MTCB data a┆
0x15d00…15e00 (21, 0, 13) Sector 00002100340041 ┆ ! 4 Aer print files are printed. 3.2 Interface Description SWELL call: MON (SEND REPORT, R4, R7) REGISTER INPUT OUTPUT R4 : Ref. work area Kept of 21 words R7 : LINK Completi┆
0x15e00…15f00 (21, 0, 14) Sector 00000000000000 ┆ ┆
[…0x1…]
0x16000…16100 (22, 0, 0) WangDocumentBody
[…0x18…]
0x17900…17a00 (23, 0, 9) Sector 170aad00340141 ┆ - 4 A W 4 QUALITY ASSURANCE 4.1 Qualification Tests N/A 4.2 Other Quality Assurance Provisions N/A til a printout request (which presets the file) is received (14.19). If the con┆
0x17a00…17b00 (23, 0, 10) Sector 170bff00340141 ┆ 4 A W 5 PREPARATIONS FOR DELIVERY Command files and source files are found on FIXLIB volume in directory: FIX SOURCE.D * JOURNAL.D * JOURNAL xxxx.D (xxxx = version number) Generati┆
0x17b00…17c00 (23, 0, 11) Sector 170cfe00340141 ┆ ~ 4 Aon of Object Code File: Copy the source directory of the actual version into a work directory. . Activate the command file JOURNAL.CR0 . Activate the command file JOURNAL.CP . Activate the command file JOURNAL.L0 The code file JOURNALe┆
0x17c00…17d00 (23, 0, 12) Sector 00008e00340141 ┆ 4 A.C is now ready for installation. Listings The computer and linker output may be obtained by activating the command file JOURNAL.PP 2 of 2) ) are inserted within the 10 secs., the incore record buffer is copied to file (7). When a queue elem┆
0x17d00…17e00 (23, 0, 13) Sector 00000000000000 ┆ ┆
[…0x2…]
0x18000…18100 (24, 0, 0) WangDocumentBody
[…0x6f…]
0x1f000…1f100 (31, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(31,0, 1), len=0xff, h3=41340241}, f00=»3402A «, f01=»FIX/1256/PSP/0102 «, f02=»ja «, f03=»OK «, f04=»TEST HDB MONITOR «, f05=07-03-83 15:41, f06=» 1 «, f07=»29 «, f08=» 4810 «, f09=06-07-83 12:50, f10=» «, f11=»12 «, f12=» 211 «, f13=06-07-83 13:19, f14=08-07-83 14:51, f15=»0306A «, f16=» 13 «, f17=» 1 «, f18=»41 «, f19=» 96 «, f20=» 5029 «, f21=» «, f22=» «, f99=020010000410052710110180aaca15050000000000000142032500df}
0x1f100…1f200 (31, 0, 1) WangDocumentBody
[…0xc…]
0x1fe00…1ff00 (31, 0, 14) Sector 00000000000000 ┆ ┆
[…0x1…]
0x20000…20100 (32, 0, 0) WangDocumentBody
[…0x17…]
0x21800…21900 (33, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(33,0, 9), len=0xff, h3=41323141}, f00=»3231A «, f01=»FIKS - tilbud til FMK «, f02=»ut «, f03=»HBA «, f04=»TDX Test Crate «, f05=07-01-83 16:22, f06=» 1 «, f07=»03 «, f08=» 3789 «, f09=18-03-83 12:17, f10=» «, f11=»02 «, f12=» 40 «, f13=11-03-83 14:39, f14=03-06-83 13:00, f15=»0306A «, f16=» 12 «, f17=» 1 «, f18=»55 «, f19=» 96 «, f20=» 6509 «, f21=» «, f22=» «, f99=600010000110052710110280aaca15050000000000000042032600df}
0x21900…21a00 (33, 0, 9) WangDocumentBody
[…0x8…]
0x22200…22300 (34, 0, 2) Sector 00000000000000 ┆ ┆
[…0x5…]
0x22800…22900 (34, 0, 8) WangDocumentBody
[…0x17…]
0x24000…24100 (36, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(36,0, 1), len=0xff, h3=41327141}, f00=»3271A «, f01=»Tilbud til FMK (FIKS) «, f02=»ut «, f03=»HBA «, f04=»FIKS Test udstyr «, f05=19-01-83 14:41, f06=» «, f07=»34 «, f08=» 3185 «, f09=18-03-83 12:19, f10=» «, f11=»00 «, f12=» 38 «, f13=09-02-83 15:14, f14=03-06-83 13:00, f15=»0306A «, f16=» 10 «, f17=» 1 «, f18=»08 «, f19=» 88 «, f20=» 3956 «, f21=» «, f22=» «, f99=020010000110052710110180aaca15050000000000000042032200df}
0x24100…24200 (36, 0, 1) WangDocumentBody
[…0x8…]
0x24a00…24b00 (36, 0, 10) Sector 240bff00344841 ┆$ 4HA W 3.1.10 GET NN ID TR Procedure The function of the GET NN ID TR Procedure is to get the identification and trunk. The trunk identification from one an┆
0x24b00…24c00 (36, 0, 11) Sector 240c6400344841 ┆$ d 4HAd of the trunk is known. The trunk identification from the other end of the trunk is wanted. ontaining: . Trunk id . Retransmission rate . No of messages on each precedure level . DTG of oldest message in trunkQUEUE of each procedures ed. ┆
0x24c00…24d00 (36, 0, 12) Sector 00004a00344841 ┆ J 4HA W 3.1.6.7 PR MEDE STA Procedure The function of the PR MEDE STA Procedure is to format and print the hour report from the MEDE. A header buffer is loade┆
0x24d00…24e00 (36, 0, 13) Sector 00000000000000 ┆ ┆
[…0x2…]
0x25000…25100 (37, 0, 0) WangDocumentBody
[…0xa…]
0x25b00…25c00 (37, 0, 11) Sector 250cf700344841 ┆% w 4HAng originator and DTG of report. The report itself will be printed line by line, each line containing: . Trunk id . Retransmission rate . No of messages on each precedure level . DTG of oldest message in trunkQUEUE of each procedures ed. ┆
0x25c00…25d00 (37, 0, 12) Sector 250dff00344841 ┆% 4HA W 3.1.6.7 PR MEDE STA Procedure The function of the PR MEDE STA Procedure is to format and print the hour report from the MEDE. A header buffer is loade┆
0x25d00…25e00 (37, 0, 13) Sector 250ed200344841 ┆% R 4HAd with originator and DTG and printed. The report itself will be printed line by line, each line containing: . Terminal id . DTG of oldest message in printqueue at each precedence level of terminal. nt has to be read from a file. .. 3.┆
0x25e00…25f00 (37, 0, 14) Sector 250fff00344841 ┆% 4HA W 3.1.6.2 PR OLD STA Procedure The function of the PR OLD STA Procedure is to format and print the result of an operator initiated on-line diagnostics. Th┆
0x25f00…26000 (37, 0, 15) Sector 2500a100344841 ┆% ! 4HAe header will be loaded with the originator and the DTG. The information to be printed are: . CPU0 status . CPU1 status . RAM status . PROM status ocedure is to read a line from a file into a buffer. ept . Node hour report . Mede hour repo┆
0x26000…26100 (38, 0, 0) WangDocumentBody
[…0x37…]
0x29800…29900 (41, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(41,0, 9), len=0xff, h3=41385441}, f00=»3854A «, f01=»FIX/0000/USM/0006 «, f02=»rt «, f03=»APE «, f04=»FIKS DISK OPERATION «, f05=05-07-83 11:31, f06=» 4 «, f07=»05 «, f08=» 12878 «, f09=28-07-83 16:32, f10=» «, f11=»03 «, f12=» 38 «, f13=28-07-83 16:40, f14=29-07-83 16:03, f15=»0306A «, f16=» 18 «, f17=» 7 «, f18=»06 «, f19=» 252 «, f20=» 15900 «, f21=» «, f22=» «, f99=310031000110462710110170aaca15050000000000000038034300df}
0x29900…29a00 (41, 0, 9) WangDocumentBody
[…0x6…]
0x2a000…2a100 (42, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(42,0, 1), len=0xff, h3=41339941}, f00=»3399A «, f01=»FIX/1200/PSP/0067 «, f02=»ja «, f03=»OK «, f04=»MTCB INIT PROCEDURE «, f05=07-03-83 09:05, f06=» 1 «, f07=»46 «, f08=» 8131 «, f09=13-07-83 12:37, f10=» «, f11=»01 «, f12=» 13 «, f13=13-07-83 12:38, f14=13-07-83 12:46, f15=»0306A «, f16=» 17 «, f17=» 1 «, f18=»58 «, f19=» 124 «, f20=» 8471 «, f21=» «, f22=» «, f99=700040000410052710110170aaca15050000000000000142033100df}
0x2a100…2a200 (42, 0, 1) WangDocumentBody
[…0x14…]
0x2b600…2b700 (43, 0, 6) Sector 00000000000000 ┆ ┆
[…0x1…]
0x2b800…2b900 (43, 0, 8) WangDocumentBody
[…0x9f…]
0x35800…35900 (53, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(53,0, 9), len=0xff, h3=41289441}, f00=»2894A «, f01=»Proposal «, f02=»ut/ «, f03=»APE «, f04=»I/F FIKS and CCIS «, f05=08-10-82 12:34, f06=» 1 «, f07=»05 «, f08=» 6580 «, f09=07-06-83 11:48, f10=» «, f11=»01 «, f12=» 6 «, f13=26-04-83 14:36, f14=07-06-83 11:49, f15=»0306A «, f16=» 41 «, f17=» 11 «, f18=»46 «, f19=» 592 «, f20=» 40864 «, f21=» «, f22=» «, f99=220041000110052710110180aaca1505000000000000004203ae00df}
0x35900…35a00 (53, 0, 9) WangDocumentBody
[…0x16…]
0x37000…37100 (55, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(55,0, 1), len=0xff, h3=41365341}, f00=»3653A «, f01=»CAMPS - FIKS INTERFACE «, f02=»rt «, f03=»CAH «, f04=»PROPOSAL «, f05=28-04-83 11:08, f06=» «, f07=»10 «, f08=» 425 «, f09=13-02-84 15:19, f10=» «, f11=»01 «, f12=» 47 «, f13=08-07-83 10:51, f14=14-02-84 08:06, f15=»0306A «, f16=» 10 «, f17=» 3 «, f18=»36 «, f19=» 120 «, f20=» 8660 «, f21=» «, f22=» «, f99=600050000220052710110170aaca15050000000000000137032a00df}
0x37100…37200 (55, 0, 1) WangDocumentBody
[…0x6…]
0x37800…37900 (55, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(55,0, 9), len=0xff, h3=41340041}, f00=»3400A «, f01=»FIX/1256/PSP/0092 «, f02=»ja «, f03=»OK «, f04=»SEND REPORT MONITOR «, f05=07-03-83 11:00, f06=» «, f07=»48 «, f08=» 4145 «, f09=17-12-86 16:07, f10=» «, f11=»01 «, f12=» 3 «, f13=17-12-86 15:24, f14=30-03-87 14:25, f15=»0306A «, f16=» 14 «, f17=» 1 «, f18=»31 «, f19=» 92 «, f20=» 5534 «, f21=» «, f22=» «, f99=100030000410052710110160aaca15050000000000000142032400df}
0x37900…37a00 (55, 0, 9) WangDocumentBody
[…0xe…]
0x38800…38900 (56, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(56,0, 9), len=0xff, h3=41340141}, f00=»3401A «, f01=»FIX/1200/PSP/0054 «, f02=»ja «, f03=»OK «, f04=»JOURNAL PROCEDURE «, f05=07-03-83 13:13, f06=» 3 «, f07=»41 «, f08=» 14904 «, f09=06-07-83 15:07, f10=» «, f11=»07 «, f12=» 14 «, f13=06-07-83 12:32, f14=08-07-83 14:51, f15=»0306A «, f16=» 42 «, f17=» 4 «, f18=»11 «, f19=» 224 «, f20=» 15497 «, f21=» «, f22=» «, f99=300000000410052710110180aaca15050000000000000142036100df}
0x38900…38a00 (56, 0, 9) WangDocumentBody
[…0x11…]
0x39b00…39c00 (57, 0, 11) Sector 00000000000000 ┆ ┆
[…0x4…]
0x3a000…3a100 (58, 0, 0) WangDocumentBody
[…0x17…]
0x3b800…3b900 (59, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(59,0, 9), len=0xff, h3=41385641}, f00=»3856A «, f01=»FIX/1256/PSP/0073 «, f02=»rt «, f03=»O.K. «, f04=»OVERLAY MONITOR PSP «, f05=06-07-83 10:58, f06=» 1 «, f07=»15 «, f08=» 5500 «, f09=13-07-83 12:31, f10=» «, f11=»01 «, f12=» 76 «, f13=13-07-83 12:32, f14=13-07-83 12:46, f15=»0306A «, f16=» 10 «, f17=» 2 «, f18=»25 «, f19=» 108 «, f20=» 7462 «, f21=» «, f22=» «, f99=900060000410462710110170aaca15050000000000000038032300df}
0x3b900…3ba00 (59, 0, 9) WangDocumentBody
[…0xa…]
0x3c400…3c500 (60, 0, 4) Sector 00000000000000 ┆ ┆
[…0x3…]
0x3c800…3c900 (60, 0, 8) WangDocumentBody
[…0x7…]
0x3d000…3d100 (61, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(61,0, 1), len=0xff, h3=41334841}, f00=»3348A «, f01=»FIX/1151/PSP/0099 «, f02=»ja «, f03=»MLA «, f04=»TEP SUBSYSTEM PSP «, f05=07-02-83 13:57, f06=» 7 «, f07=»32 «, f08=» 42650 «, f09=04-11-88 12:47, f10=» «, f11=»00 «, f12=» 30 «, f13=04-11-88 12:49, f14=19-12-88 12:53, f15=»0306A «, f16=» 98 «, f17=» 9 «, f18=»53 «, f19=» 804 «, f20=» 46894 «, f21=» «, f22=» «, f99=580037000210052710110480aaca17040000000000000142032a01df}
0x3d100…3d200 (61, 0, 1) WangDocumentBody
[…0x6…]
0x3d800…3d900 (61, 0, 8) Sector 3d09ff00385441 ┆= 8TAe exist three utility programs DISK ONE.c, DISK TWO.c and DISKS DUAL.c which overwrites the checkpointed DISK STATUS. These are manual activated by the operator (Use S-RUN 'Program') The FIKS-fileboot may be used together with TOS-boot-no disk wri┆
0x3d900…3da00 (61, 0, 9) Sector 3d0aff00385441 ┆= 8TAting will be performed. The operations that may be executed in this way can not be predicted, but at least there is no risk of damaging something. 6. SYSTEM OPERATIONAL PROCEDURES This section deals with what a system operator has to do i┆
0x3da00…3db00 (61, 0, 10) Sector 3d0ba600385441 ┆= & 8TAn certain selected cases. All keying in is performed on the console, - transparent Watchdog mode to the affected branch is assumed. Keying in is underlined. E's can use the disks at the same time. If both branches were allowed to do writing on th┆
0x3db00…3dc00 (61, 0, 11) Sector 3d0cff00385441 ┆= 8TA 1 6.1 Boot load of FIKS 1 B1 A ," normal B2 B ERROR SWITCHOVER ...... etc. if no response or the system d┆
0x3dc00…3dd00 (61, 0, 12) Sector 3d0dff00385441 ┆= 8TAoes respond as stated then key in I 33 "boot from opposite B1 A "site branch B2 B the following may appear DISK STATUS ? OE/TO/DL The system has found that no disk can be used as a result of the disk investigation performed at th┆
0x3dd00…3de00 (61, 0, 13) Sector 3d0eff00385441 ┆= 8TAe disk initializing. The operator may then close the proper DISK STATUS by keying in OE, TO or DL(ONE, TWO or DUAL). The DISK STATUS used last time the system was FIKS-ACTIVE can be found in earlier log printing - DISK STATUS CHANGES IS ALWAYS LOGGE┆
0x3de00…3df00 (61, 0, 14) Sector 3d0fff00385441 ┆= 8TAD: Note: The operator has to make a decision that may have catastrophic effect on the system in case it is wrong. Is the situation caused by hardware failure? Wrong BRANCH ID keyed in? Uncontrolled use of TOS-system. If an errorreport with erro┆
0x3df00…3e000 (61, 0, 15) Sector 3d00ff00385441 ┆= 8TArcode # 4FF (disk system stopped) appears, the just after bootload, then this may be caused by an unlucky hardware error in one of the disk unit. It is then better to exclude this unit from the system. This is done by switching off the power to the┆
0x3e000…3e100 (62, 0, 0) Sector 3e01ff00385441 ┆> 8TAon of DISK STATUS. It is noticed that in BRANCH ONE correspond DISK ONE/TWO to the IO-addresses 200/204, and in BRANCH TWO correspond DISK ONE/TWO to the IO-addresses 204/200. 4. INITIALIZING OF FIKS DISK SYSTEM When the FISK-system is bo┆
0x3e100…3e200 (62, 0, 1) Sector 3e02ff00385441 ┆> 8TAot loaded BRANCH ID, DISK STATUS is defaulted to BRANCH ONE, DISKS DUAL. The state of the disk-controllers is examined. If the cables to the controller or the interface board itself is missing, then no attempt to use the corresponding disk unit is┆
0x3e200…3e300 (62, 0, 2) Sector 3e03ff00385441 ┆> 8TA performed - the DISK STATUS is set in accordance to this. When BRANCH ID id keyed in by the operator, DISK STATUS is updated again (if BRANCH TWO is stated). The next step in the initializing procedure is to examine the earlier checkpointed DISK ST┆
0x3e300…3e400 (62, 0, 3) Sector 3e04ff00385441 ┆> 8TAATUS WORD's (one on each disk unit): By combining the obtainable DISK STATUS's- (those from the disk controllers and the checkpointed), the largest common DISK STATUS is determined. In case DISK STATUS comes out with "no disk available" the system o┆
0x3e400…3e500 (62, 0, 4) Sector 3e057c00385441 ┆> | 8TAperator is asked to key in a DISK STATUS. If the state of the branch is going to be ACTIVE the disk-write is enabled. disk hardware errors) are handled of the system software (ESP). ....................... 003 2. SUMMARY ....................┆
0x3e500…3e600 (62, 0, 5) Sector 3e06ff00385441 ┆> 8TA 1 5. USE OF TOS IN THE DUAL DISK SYSTEM Normal operations with the TOS-system will take place in BRANCH ONE and on DISK ONE-floppy drive is only connected to BRANCH ONE. It is presu┆
0x3e600…3e700 (62, 0, 6) Sector 3e07ff00385441 ┆> 8TAmed that some kind of updating is performed on the disk and last time FIKS was active the DISK STATUS was DUAL. Therefore the checkpointed DISK STATUS is automatically set to ONE when the TOS-system is used. Next time FIKS becomes active, DISK STATU┆
0x3e700…3e800 (62, 0, 7) Sector 3d08ff00385441 ┆= 8TAS will be one and a 'DUALIZING of Disks' - procedure can be performed. If the system in some manner is reduced (one BRANCH or DISK is missing) and TOS is used, then the checkpointed DISK STATUS shall be set in accordance to the case. To do this ther┆
0x3e800…3e900 (62, 0, 8) Sector 3e09ff00385441 ┆> 8TAs said to be ONE/TWO. If DISK STATUS is DUAL then the disk read operations will be performed from one of the disk units and disk write operations on both units. In case of a hardware failure in one of the disk units, this one is DISCARDED and the ┆
0x3e900…3ea00 (62, 0, 9) Sector 3e0aff00385441 ┆> 8TAone unit left is used as single (ONE/TWO). Later on when the erroneuous disk is repaired, it can be included in the disk system again - a DUALIZING of the disk is started. All write operations are now performed on both units while a copying of disk ┆
0x3ea00…3eb00 (62, 0, 10) Sector 3e0bff00385441 ┆> 8TAsectors from the disk used all the time to the disk to be included. When this copying is finished the units are identical and DISK STATUS is DUAL. Both BRANCHE's can use the disks at the same time. If both branches were allowed to do writing on th┆
0x3eb00…3ec00 (62, 0, 11) Sector 3e0cff00385441 ┆> 8TAe disk units simultaneous, then the disks would soon be corrupted. Therefore a feature for controlling the ability of being able to write on the disks is present. When the FIKS-system is booted, no disk writing can be done - every disk write operati┆
0x3ec00…3ed00 (62, 0, 12) Sector 3e0dff00385441 ┆> 8TAon is converted to a dummy 'CHECK'-operation. All diskread-operations are executed in the usual manner. This state of the disk system is meant to be used when a branch is STANDBY. When the branch is going to be ACTIVE DISK-writing is enabled. (WRTDI┆
0x3ed00…3ee00 (62, 0, 13) Sector 3e0e6200385441 ┆> b 8TASK). To keep track of the different states of the disk system a DISK STATUS WORD is used. the file- and user processor is done via the DMA-link. The CDC-diske (kind = MMD82, unit no = 0) consist of two submits: - the section accessed with mova┆
0x3ee00…3ef00 (62, 0, 14) Sector 3e0fff00385441 ┆> 8TA 1 1 15 14 3 2 1 0 bit no ┆
0x3ef00…3f000 (62, 0, 15) Sector 3e00ff00385441 ┆> 8TA Bit on means 0: DISK ONE INCLUDED 1: DISK TWO INCLUDED 2: DISK WRITE ENABLED 3: DISKS DUALIZING This word is checkpointed (i.e. written to disk) to be retrieved at next initializing of the disk system for determinati┆
0x3f000…3f100 (63, 0, 0) Sector 3f019a00385441 ┆? 8TA 1 FIG. 1 FRONT VIEW DISK OPERATION ┆
0x3f100…3f200 (63, 0, 1) Sector 3f02ff00385441 ┆? 8TA 1 2.2 Software (ref. fig. 2) When an application in the CR80-computer requests a disk read/write, this command is sent via the IO-system in the user processor and DMA-driver (DMA000┆
0x3f200…3f300 (63, 0, 2) Sector 3f03ff00385441 ┆? 8TA) for the File Management System (FMS) placed in the file processor. The FMS translates the commands to disk-sector read/write commands. These are handed over to the disks drivers (CDC000, CDC001 for the CDC-disks and FDD000 for the Floppy), which c┆
0x3f300…3f400 (63, 0, 3) Sector 3f04ff00385441 ┆? 8TAarry out the interface to the disk-controllers. Needed data transfers between file- and userprocessor is controlled by the FMS and executed by the DMA-driver. When the disk-operation is finished the disk-drivers are interrupted. They return completi┆
0x3f400…3f500 (63, 0, 4) Sector 3f05bc00385441 ┆? < 8TAon to the FMS, which forwards this information via DMA-drivers and IO-system to the application. Certain completians (disk hardware errors) are handled of the system software (ESP). ....................... 003 2. SUMMARY ....................┆
0x3f500…3f600 (63, 0, 5) Sector 3f069000385441 ┆? 8TA 1 FIG. 2 DISK OPERATION 6 3. FIKS DUAL DISK SYSTEM ..................... 008 4. INITIALIZING OF FIKS DISK SYSTEM .......... ┆
0x3f600…3f700 (63, 0, 6) Sector 3f07ff00385441 ┆? 8TA 1 3. FIKS DUAL DISK SYSTEM Seen from the system operational software point of view, the FIKS dual disksystem (ref. fig. 1, Node/MEDE-config.) consist of two logical DEVICES: - MMD┆
0x3f700…3f800 (63, 0, 7) Sector 3e08ff00385441 ┆> 8TAO, with volume MOVHED - FIXO, with volume FIXHEAD The devices may consist of submits from one or both of the disk units. If both submits are used then DISK STATUS is said to be DUAL. If only submits from BRANCH ONE/TWO are used then DISK STATUS i┆
0x3f800…3f900 (63, 0, 8) Sector 3f09ff00385441 ┆? 8TA 1 1. INTRODUCTION This document gives an overview of how the FIKS Disk System functions and how it shall be operated. It is meant to be read of technicians, system operator and othe┆
0x3f900…3fa00 (63, 0, 9) Sector 3f0aff00385441 ┆? 8TAr persons, who interface to the FIKS Disk System. For more detailed description refer to the following documents. ESP SYSTEM PSP Product Specification, FIX/1105/PSP/0046 CR80 AMOS I/O System, Product Specification, CSS/006/PSP/0006 CR80 DMA ┆
0x3fa00…3fb00 (63, 0, 10) Sector 3f0bcd00385441 ┆? M 8TALink Driver, Product Specification, CSS/006/PSP/0002 CR80 AMOS File Management System, System Product Specification, CSS/920/SPS/0001 CR80 Disk Driver, Product Specification, CSS/006/PSP/0005 ┆
0x3fb00…3fc00 (63, 0, 11) Sector 3f0cff00385441 ┆? 8TA 1 2. SUMMARY 2.1 Hardware (ref. fig. 1) The disks (CDC and FLOPPY) are controlled of the interface boards placed in the file processor. These diskcontrollers are accessed from th┆
0x3fc00…3fd00 (63, 0, 12) Sector 3f0dff00385441 ┆? 8TAe file processor via the SCM-mainbus using the IO-addresses 200,204 (=4(#32, #33)) for CDC and 8(=2*4) for floppy. In this way they are requested to perform data transfers to/from the disks from/to the disk-CACHE-CR80-memory RAM placed page 1, locat┆
0x3fd00…3fe00 (63, 0, 13) Sector 3f0eff00385441 ┆? 8TAions 0 - #4000). These transfers are executed using a SUBBUS. Transferrence of data between the file- and user processor is done via the DMA-link. The CDC-diske (kind = MMD82, unit no = 0) consist of two submits: - the section accessed with mova┆
0x3fe00…3ff00 (63, 0, 14) Sector 3f0fff00385441 ┆? 8TAble heads (submit no = 0), where the volume MOVHEAD is placed. - the section accessed with fixed heads (submit no = 1), where the volume FIXHEAD is placed. The Floppy disk (kind = FLOPPY, unit no = 0) is in the Node/MEDE configuration only place┆
0x3ff00…40000 (63, 0, 15) Sector 3f009c00385441 ┆? 8TAd in BRANCH ONE (i.e. it can not be used of BRANCH TWO). There is one submit (submit no = 0), where a volume with name FLOPPY (normally) is placed. ┆
0x40000…40100 (64, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(64,0, 1), len=0xff, h3=41385441}, f00=»3854A «, f01=»FIX/0000/USM/0006 «, f02=»rt «, f03=»APE «, f04=»FIKS DISK OPERATION «, f05=05-07-83 11:31, f06=» 4 «, f07=»05 «, f08=» 12878 «, f09=07-07-83 10:15, f10=» «, f11=»04 «, f12=» 23 «, f13=07-07-83 10:36, f14=14-07-83 13:14, f15=»0306A «, f16=» 16 «, f17=» 5 «, f18=»54 «, f19=» 196 «, f20=» 13710 «, f21=» «, f22=» «, f99=510010000110462710110170aaca15050000000000000038033f00df}
0x40100…40200 (64, 0, 1) Sector 40021000385441 ┆@ 8TA @ @ @ ? ? ? ? ? ? > > = = = < < < DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANAN┆
0x40200…40300 (64, 0, 2) Sector 40039c00385441 ┆@ 8TA 1 3854/rt FIX/0000/USM/0006 APE/830630 # FIKS DISK OPERATION FK 7809 !/=6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x40300…40400 (64, 0, 3) Sector 40047500385441 ┆@ u 8TA 1 APPENDIX A FIKS DISK OPERATION ~ B~.> IMB'IM2& 9x2"<!Z="(=^#Vk"$<:]=2#<:^=~ J6.! <6 M8) R6.> I! <6 M8)I!h=6 ! =6 M")IM"):g=~ J /:h=2>=M?.Mj': < Zn.C / E*:=k 0wM% !;=4C┆
0x40400…40500 (64, 0, 4) Sector 4005ff00385441 ┆@ 8TA 1 TABLE OF CONTENTS 1 1. INTRODUCTION .............................. 003 2. SUMMARY ....................┆
0x40500…40600 (64, 0, 5) Sector 4006ff00385441 ┆@ 8TA............... 004 2.1 HARDWARE .............................. 004 2.2 SOFTWARE .............................. 006 3. FIKS DUAL DISK SYSTEM ..................... 008 4. INITIALIZING OF FIKS DISK SYSTEM .......... ┆
0x40600…40700 (64, 0, 6) Sector 4007ff00385441 ┆@ 8TA 009 5. USE OF TOS IN FIKS DUAL DISK SYSTEM ....... 010 6. SYSTEM OPERATIONAL PROCEDURES ............. 010 6.1 BOOT LOAD OF FIKS ..................... 011 6.2 DUALIZING OF DISKS .................... 012 6.3 D┆
0x40700…40800 (64, 0, 7) Sector 3f08a900385441 ┆? ) 8TAISCARDING OF DISKS ................... 012 6.4 DISK STATUS PRINTOUT .................. 013 6.5 USE OF TOS: ........................... 014 28=I!#<:"<>R<2> I E*#<& "< DM L<M% :#<F 2#<> I:g= Ro2M/2 Rl2> IC13!?=4~~ B|2> I:A=!┆
0x40800…40900 (64, 0, 8) WangDocumentBody
[…0x17…]
0x42000…42100 (66, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(66,0, 1), len=0xff, h3=41385841}, f00=»3858A «, f01=»FIX/1256/PSP/0052 «, f02=»rt «, f03=»JK «, f04=»INTASC MONITOR PSP «, f05=06-07-83 13:33, f06=» «, f07=»38 «, f08=» 2771 «, f09=12-07-83 10:04, f10=» «, f11=»00 «, f12=» 2 «, f13=08-07-83 14:10, f14=14-07-83 13:15, f15=»0306A «, f16=» 21 «, f17=» «, f18=»38 «, f19=» 60 «, f20=» 2773 «, f21=» «, f22=» «, f99=020010000410462710110170aaca15050000000000000138032400df}
0x42100…42200 (66, 0, 1) WangDocumentBody
[…0x6…]
0x42800…42900 (66, 0, 8) Sector 00000000000000 ┆ ┆
[…0x7…]
0x43000…43100 (67, 0, 0) WangDocumentBody
[…0x1f…]
0x45000…45100 (69, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(69,0, 1), len=0xff, h3=41385941}, f00=»3859A «, f01=»FIX/1256/PSP/0048 «, f02=»rt «, f03=»OK «, f04=»FILL-MTCB MONI.PSP «, f05=08-07-83 09:54, f06=» 1 «, f07=»43 «, f08=» 5515 «, f09=14-07-83 11:55, f10=» «, f11=»09 «, f12=» 4 «, f13=14-07-83 11:53, f14=14-07-83 13:16, f15=»0306A «, f16=» 14 «, f17=» 1 «, f18=»58 «, f19=» 100 «, f20=» 5706 «, f21=» «, f22=» «, f99=100010000410462710110170aaca15050000000000000138032800df}
0x45100…45200 (69, 0, 1) WangDocumentBody
[…0x6…]
0x45800…45900 (69, 0, 8) Sector 00000000000000 ┆ ┆
[…0x77…]
