OctetView
0x00000…00100 (0, 0, 0) Sector 01554130313535 ┆ UA0155A ┆
0x00100…00200 (0, 0, 1) Sector 00000000000000 ┆ ┆
0x00200…00300 (0, 0, 2) Sector ff00f8ffffffff ┆ x @ ┆
0x00300…00306 (0, 0, 3) WangDocument {d00=0x13, d01=0x52, d02=0x41, ptr=(33,0, 0), d05=0x00}
0x00306…0030c WangDocument {d00=0x19, d01=0x81, d02=0x41, ptr=(56,0, 8), d05=0x00}
0x0030c…00312 WangDocument {d00=0x20, d01=0x22, d02=0x41, ptr=(56,0, 0), d05=0x00}
0x00312…00320 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ ┆
0x00320…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 00 00 00 00 ┆ ┆
[…0x5…]
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 12 ┆ ┆
0x00400…00500 (0, 0, 4) Sector 00000000000000 ┆ ┆
0x00500…00600 (0, 0, 5) Sector 86312020202020 ┆ 1 8 7 Q? > 7 F \ d 0 N \ N d N ~<) 0uH &4'>( 1c5 & & ┆
0x00600…00700 (0, 0, 6) Sector 421c402600415b ┆B @& A[' A X% %; PO P ; "Aa9 C g x g V Wu O 8 : H KK f 2022A g q < {C < { ; 2 hA - uP ue l 8 9 :JK t -e L 2013A2015A a< b7 N 5 ┆
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
[…0x1f7…]
0x21000…21100 (33, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(33,0, 1), len=0xff, h3=41135241}, f00=»1352A «, f01=»CPS/SDS/001 «, f02=»vhn «, f03=»BHB «, f04=»Kapitel 4 «, f05=09-10-81 06:01, f06=» «, f07=»34 «, f08=» 311 «, f09=30-08-84 10:06, f10=» «, f11=»03 «, f12=» 37 «, f13=30-08-84 10:10, f14=31-08-84 13:23, f15=»0155A «, f16=» 87 «, f17=» 10 «, f18=»50 «, f19=» 1712 «, f20=» 16823 «, f21=» «, f22=» p «, f99=770000000110062710110280aaca15050000000000000137030502df}
0x21100…21200 (33, 0, 1) WangDocumentBody
[…0x8…]
0x21a00…21b00 (33, 0, 10) Sector 210bc200135241 ┆! B RAed in the Main site at the Standard CCITT V24/V28 interface of the LTUs/LTUXs. As indicated on the figure 4.1.1-2 part of the distribution equipment is placed in the MAIN SITE racks. CAMPS is an integral part of a total system concept which als┆
0x21b00…21c00 (33, 0, 11) Sector 210c9f00135241 ┆! RA 1 Fig. 4.1.1-2 Distribution Equipment vide the optimum implementation of the CAMPS systems. The allocation of functions between syst┆
0x21c00…21d00 (33, 0, 12) Sector 210dff00135241 ┆! RA 1 4.1.1.1.2 Telecommunication Data Exchange (TDX) The TDX equipment is used for interconnection of individual data exchange channels with the Processor Units. The interfaces of th┆
0x21d00…21e00 (33, 0, 13) Sector 210eff00135241 ┆! RAe data exchange channels in the TDX-system are standard CCITT V24/V28 circuits of the LTUX modules, see fig. 4.1.1-3. Each LTUX module is able to interface 1, 2 or 4 data exchange channels dependent on channel specifications, and each TDX Crate as┆
0x21e00…21f00 (33, 0, 14) Sector 210fff00135241 ┆! RAsembly contains max. 2 LTUX modules. Each TDX Crate assembly is switched to one of the two TDX Buses. The switching is controlled by the Watchdog Processor through the Configuration Control Bus (CCB). The switching is performed by the BSM-X-modul┆
0x21f00…22000 (33, 0, 15) Sector 2100ff00135241 ┆! RAe and the interconnection to the buses are done by a TDX-outlet on each bus. A TDX Bus links together all the functional elements of the TDX System. The Multiplexing Scheme of the TDX Bus is driven and controlled by the TDX controller. All the c┆
0x22000…22100 (34, 0, 0) WangDocumentBody
[…0x15f…]
0x38000…38100 (56, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(56,0, 1), len=0xff, h3=41202241}, f00=»2022A «, f01=»CPS/SDS/028 «, f02=»rt «, f03=»HKI «, f04=»fra 4.1.4.2 I/O CTR. «, f05=15-04-82 13:46, f06=» 5 «, f07=»16 «, f08=» 19120 «, f09=21-04-82 10:59, f10=» «, f11=»12 «, f12=» 351 «, f13=30-01-85 14:16, f14=06-02-85 15:20, f15=»0155A «, f16=» 17 «, f17=» 6 «, f18=»31 «, f19=» 184 «, f20=» 21301 «, f21=» «, f22=» «, f99=020010000110052710110380aa8a37040000000000000042034000df}
0x38100…38200 (56, 0, 1) WangDocumentBody
[…0x6…]
0x38800…38900 (56, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(56,0, 9), len=0xff, h3=41198141}, f00=»1981A «, f01=»CPS/SDS/033 «, f02=»uw «, f03=»KNB «, f04=»4.2.6 «, f05=02-04-82 14:44, f06=» 19 «, f07=»25 «, f08=» 59578 «, f09=27-09-84 09:01, f10=» «, f11=»01 «, f12=» 15 «, f13=27-09-84 09:02, f14=01-10-84 09:43, f15=»0155A «, f16=» 79 «, f17=» 29 «, f18=»01 «, f19=» 900 «, f20=» 79628 «, f21=» «, f22=» 0 «, f99=830000000110052710110280aaca15050000000000000142033201df}
0x38900…38a00 (56, 0, 9) WangDocumentBody
[…0x6…]
0x39000…39100 (57, 0, 0) Sector 3901ff41198141 ┆9 A A1981A CPS/SDS/033 uw KNB 4.2.6 02 04 82 14 44 19 25 59578 31 08 84 13 41 38 960 04 09 84 12 38 04 09 84 13 27 0155A 79 29 00 932 79613 ' *J B 2 _┆
0x39100…39200 (57, 0, 1) Sector 39024f00198141 ┆9 O A 9 9 8 3 3 3 3 3 3 3 2 2 2 1 1 1 0 0 / / / / . . . - - - - , , , , , + + + * * * * * * * * ) ) ) ) ) ( ( ( ( ( ( ' ' ' & & & & % % % % % $ $ $ $ # # # # # " " " D D ┆
0x39200…39300 (57, 0, 2) Sector 3903ac00198141 ┆9 , A 1 CPS/SDS/033 831101 TRAFFIC HANDLING DETAILED DESIGN SPECIFICATION ISSUE 1 CAMPS */=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x39300…39400 (57, 0, 3) Sector 3904ff00198141 ┆9 A 1 1 4.2.6 OUTGOING TRANSPORT SUBPACKAGE ....┆
0x39400…39500 (57, 0, 4) Sector 3905ff00198141 ┆9 A......... 4.2.6.l Functional Specification .............. 4.2.6.1.1 Outgoing Traffic Control .......... 4.2.6.1.1.1 Start Transport ............... 4.2.6.1.1.2 Stop Transport ................ 4.2.6┆
0x39500…39600 (57, 0, 5) Sector 3906ff00198141 ┆9 A.1.1.3 Close Down .................... 4.2.6.l.l.4 Log Acknowledge ............... 4.2.6.l.l.5 ASM TRansmission .............. 4.2.6.l.2 Outgoing Message Handling ......... 4.2.6.l.2.l Buffer Control .....┆
0x39600…39700 (57, 0, 6) Sector 3907ff00198141 ┆9 A........... 4.2.6.l.2.2 Tramsmission Start ............ 4.2.6.l.2.3 Message Transmission .......... 4.2.6.l.2.4 Transmission End .............. 4.2.6.l.2.5 Paging of Long Messages ....... 4.2.6.┆
0x39700…39800 (57, 0, 7) Sector 3808ff00198141 ┆8 Al.l.6 Preemption ................... 4.2.6.l.2.7 Log for Outgoing Messages ..... 4.2.6.l.2.8 Statistics for Outgoing Message 4.2.6.l.3 Message Line Generation ........... 4.2.6.l.3.l ACP127 Format Line 1 ┆
0x39800…39900 (57, 0, 8) Sector 3909ff00198141 ┆9 A.......... 4.2.6.l.3.2 ACP 127 Pilot ................. 4.2.6.l.3.3 E1 - Pilot .................... 4.2.6.l.3.4 ACP127 Page Id ................ 4.2.6.l.3.5 Pre-emption ................... 4.2.6.l┆
0x39900…39a00 (57, 0, 9) Sector 390aff00198141 ┆9 A.3.6 ACP127 Format Line 14 (Fl 14) . 4.2.6.l.3.7 ACP127 Format Line 15 (Fl 15) . 4.2.6.l.3.8 ACP127 Format Line 16 (Fl 16) . 4.2.6.l.3.9 ACP127 Text Separators ........ 4.2.6.l.3.l0 E1 Format Line B ......┆
0x39a00…39b00 (57, 0, 10) Sector 390bff00198141 ┆9 A....... 4.2.6.l.3.11 PTP Dummy Formal Line 1 ...... 4.2.6.1.3.12 Start of Tape Sequence ....... 4.2.6.l.3.l3 End of Tape Sequence ......... 4.2.6.l.3.14 PTP Pre-emption Sequence ..... 4.2.6.l.3.┆
0x39b00…39c00 (57, 0, 11) Sector 390cff00198141 ┆9 A15 Start of Message Black (SOM) 4.2.6.1.3.16 End of Message Black (EOM) ... 4.2.6.l.4 Automatic Generation of ASM ....... 4.2.6.l.4.l ACP127 Format ?? ASM .......... 4.2.6.l.4.2 E1 Format for ASM .......┆
0x39c00…39d00 (57, 0, 12) Sector 390db800198141 ┆9 8 A...... 4.2.6.l.4.3 ASM for TRC/POIN TO POINT ..... 4.2.6.l.4.4 ASM FOR NICS TARE ............. 4.2.6.l.4.5 ASM FOR SCARS/CCIS ............ undet I brug nu Allerede p> systemdiskette ┆
0x39d00…39e00 (57, 0, 13) Sector 390eff00198141 ┆9 A 1 4.2.6.2 SOFTWARE STRUCTURE .................... 4.2.6.2.l Outgoing Traffic Control Module ... ┆
0x39e00…39f00 (57, 0, 14) Sector 390fff00198141 ┆9 A 4.2.6.2.2 Outgoing Start/Stop Control Module 4.2.6.2.3 Outgoing Message Handling Module .. 4.2.6.2.4 Outgoing Message Transmission ..... 4.2.6.2.5 Message Line Generation Module .... 4.2.6.4.3.3 Module┆
0x39f00…3a000 (57, 0, 15) Sector 3900ff00198141 ┆9 A Components ............. 4.2.6.4.3.4 Data Description .............. 4.2.6.4.3.5 Module Design ................ 4.2.6.4.4 PTP Outgoing Traffic Control ...... 4.2.6.4.4.1 Functional Specification ...... ┆
0x3a000…3a100 (58, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(58,0, 1), len=0xff, h3=41198141}, f00=»1981A «, f01=»CPS/SDS/033 «, f02=»uw «, f03=»KNB «, f04=»4.2.6 «, f05=02-04-82 14:44, f06=» 19 «, f07=»25 «, f08=» 59578 «, f09=28-03-84 15:09, f10=» 4 «, f11=»01 «, f12=» 10753 «, f13=29-03-84 13:12, f14=30-03-84 10:36, f15=»0155A «, f16=» 79 «, f17=» 28 «, f18=»22 «, f19=» 1000 «, f20=» 78653 «, f21=» «, f22=»" «, f99=020000000110052710110380aa8a37040000000000000142033001df}
0x3a100…3a200 (58, 0, 1) Sector 3a024f00198141 ┆: O A : : 9 8 8 8 8 4 4 4 3 3 3 2 2 2 1 1 0 0 0 0 / / / . . . . - - - - - , , , + + + + + + + + * * * * * ) ) ) ) ) ) ( ( ( ' ' ' ' ' & & & & % % % % % $ $ $ $ $ # # D D ┆
0x3a200…3a300 (58, 0, 2) Sector 3a03ac00198141 ┆: , A 1 CPS/SDS/033 831101 TRAFFIC HANDLING DETAILED DESIGN SPECIFICATION ISSUE 1 CAMPS */=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x3a300…3a400 (58, 0, 3) Sector 3a04ff00198141 ┆: A 1 1 4.2.6 OUTGOING TRANSPORT SUBPACKAGE ....┆
0x3a400…3a500 (58, 0, 4) Sector 3a05ff00198141 ┆: A......... 4.2.6.l Functional Specification .............. 4.2.6.1.1 Outgoing Traffic Control .......... 4.2.6.1.1.1 Start Transport ............... 4.2.6.1.1.2 Stop Transport ................ 4.2.6┆
0x3a500…3a600 (58, 0, 5) Sector 3a06ff00198141 ┆: A.1.1.3 Close Down .................... 4.2.6.l.l.4 Log Acknowledge ............... 4.2.6.l.l.5 ASM TRansmission .............. 4.2.6.l.2 Outgoing Message Handling ......... 4.2.6.l.2.l Buffer Control .....┆
0x3a600…3a700 (58, 0, 6) Sector 3a07ff00198141 ┆: A........... 4.2.6.l.2.2 Tramsmission Start ............ 4.2.6.l.2.3 Message Transmission .......... 4.2.6.l.2.4 Transmission End .............. 4.2.6.l.2.5 Paging of Long Messages ....... 4.2.6.┆
0x3a700…3a800 (58, 0, 7) Sector 3908ff00198141 ┆9 Al.l.6 Preemption ................... 4.2.6.l.2.7 Log for Outgoing Messages ..... 4.2.6.l.2.8 Statistics for Outgoing Message 4.2.6.l.3 Message Line Generation ........... 4.2.6.l.3.l ACP127 Format Line 1 ┆
0x3a800…3a900 (58, 0, 8) Sector 3a09ff00202241 ┆: "A5, R7): ERROR OK b2) COMON (CSYSCALL, FH FIELDS INPUT; R0, R1, R2, R3, R4, R5, R7, R6): ERROR OK Call Registers R0 Pointer to FIRST FIELD R1 INTERFACE NO R2 ┆
0x3a900…3aa00 (58, 0, 9) Sector 3a0aff00202241 ┆: "APointer to BLE R3 Pointer to FIELD LIST R4 NUMBER OF FIELDS Return Registers R0 BYTES TRANSFERRED R7 CC (OK, VDU SPLIT FAILED) Fatal Errors All but a┆
0x3aa00…3ab00 (58, 0, 10) Sector 3a0b6c00202241 ┆: l "Above fatal. The number of fields indicates the length of the field list for both output and input. the fields are taken as specified in the field list, assuming that the fields are sequenced in the Buffer as defined in the field list. The Buffer┆
0x3ab00…3ac00 (58, 0, 11) Sector 3a0cff00202241 ┆: "A 1 4.1.7.2.3.11 CHANGE FIELD ATTR The CHANGE FIELD ATTR is used to highlight a field to the operator. Attributes can be defined with numeric values as defined below. Combined a┆
0x3ac00…3ad00 (58, 0, 12) Sector 3a0dff00202241 ┆: "Attributes are obtained by summing the numeric values: Strike Through Non Display Half Intensity Reverse Video Dotted Underline Blink Input: Interface # (IFCB index) Line Number I┆
0x3ad00…3ae00 (58, 0, 13) Sector 3a0eff00202241 ┆: "Ancarnation Number Field Number. New attributes Output: Done VDU split failed Call Specification a) CHANGE FIELD ATTR (INTERFACE NO: IFCB INDEX, FIELD: FIELD DESCRIPTOR TYPE, NEW ATTR: FIELD ATTR TYPE) ┆
0x3ae00…3af00 (58, 0, 14) Sector 3a0fff00202241 ┆: "A (CC: COMPLETION CODE): ERROR OK b1) MON (SCM, SYSCALL, FH CHANGE FIELD ATTR: R6, R0, R1, R3, R5, R7): ERROR OK b2) COMON (CSYSCALL, FH CHANGE FIELD ATTR, R0, R1, R3, R5, R7 R6): ERROR OK Call Registers R0 Pointer ┆
0x3af00…3b000 (58, 0, 15) Sector 3a008e00202241 ┆: "Ato FIELD R1 INTERFACE NO R2 NEW ATTR Return Registers R7 CC (OK, VDU SPLIT FAILED) Fatal Errors All but above are fatal. LINE NUMBER: LINE NUMBER TYPE, INCARNATION NUMBER: INCARNATION NUMBER TYPE, NUMBER ┆
0x3b000…3b100 (59, 0, 0) Sector 3b01ff00202241 ┆; "A 1 Input: Interface # (IFCB index) Pointer Field List Pointer BLE list Number of fields. Byte length of buffer Output: Done VDU split failed Call Specificati┆
0x3b100…3b200 (59, 0, 1) Sector 3b02ff00202241 ┆; "Aon 1 a) FIELDS OUTPUT (INTERFACE NO: IFCB INDEX, FIELD LIST: FIELD LIST TYPE, BLE: BUFFER LIST ELEMENT, NUMBER OF FIELDS: INTEGER, ┆
0x3b200…3b300 (59, 0, 2) Sector 3b03ff00202241 ┆; "ABYTE LENGTH: BYTE LENGTH TYPE) (CC: COMPLETION CODE): ERROR OK b1) MON (SCM, SYSCALL; FH FIELDS OUTPUT: R6, R0, R1, R2, R3, R4, R5, R7): ERROR OK b2) COMON (CSYSCALL, FH FIELDS OUTPUT, R0, R1, R2, R3, R4, R5┆
0x3b300…3b400 (59, 0, 3) Sector 3b04ff00202241 ┆; "A, R7, R6): ERROR OK Call Registers R0 BYTE LENGTH Buffer length in total R1 INTERFACE NO R2 Pointer to BLE R3 Pointer to FIELD LIST R4 NUMBER OF FIELDS Return R┆
0x3b400…3b500 (59, 0, 4) Sector 3b057600202241 ┆; v "Aegisters R7 CC (OK, VDU SPLIT FAILED) Fatal Errors Other than above mentioned are fatal. ne, the number of lines should be defined to zero. If too many lines specified, the maximum will be deleted. Note that the issuing of ┆
0x3b500…3b600 (59, 0, 5) Sector 3b06ff00202241 ┆; "A 1 4.1.7.2.3.10 FIELD INPUT Input: Interface # (IFCB index) Pointer empty field list Pointer BLE list First field Number of fields. Output: Field list fille┆
0x3b600…3b700 (59, 0, 6) Sector 3b07ff00202241 ┆; "Ad, Buffer filled, Bytes transferred filled, Fields transferred = Number of fields) Call Specification a) FIELDS INPUT ( INTERFACE NO: IFCB INDEX, BLE: BUFFER LIST ELEMENT, FIRST FIELD: FIELD DESCRIPTOR TYPE, ┆
0x3b700…3b800 (59, 0, 7) Sector 3a08ff00202241 ┆: "A NUMBER OF FIELDS: INTEGER) (BYTES TRANSFERRED: BYTE LENGTH TYPE, FIELD LIST: FIELD LIST TYPE, CC: COMPLETION CODE): ERROR OK b1) MON (SCM, SYSCALL, FH FIELDS INPUT: R6, R0, R1, R2, R3, R4, R┆
0x3b800…3b900 (59, 0, 8) Sector 3b09d100202241 ┆; Q "A 1 Return Registers R7 CC (OK, DELETE NOT ALLOWED, VDU SPLIT FAILED) Fatal Errors All but the ones above are fatal , R3,R5,R7,R6): ┆
0x3b900…3ba00 (59, 0, 9) Sector 3b0aff00202241 ┆; "A 1 4.1.7.2.3.9 FIELD OUTPUT The field handling functions are performing input and output of fields. Fields are transferred from / to the application buffers. The interface is based┆
0x3ba00…3bb00 (59, 0, 10) Sector 3b0bff00202241 ┆; "A on a definition of a field buffer and a field list buffer as shown in fig. 4.1.7.2.3-1. For output, the fields are taken as specified in the field list, assuming that the fields are sequenced in the Buffer as defined in the field list. The Buffer┆
0x3bb00…3bc00 (59, 0, 11) Sector 3b0cff00202241 ┆; "A is the consecutive byte string defined by buffer 1, buffer 2 and buffer 3. For input, the field content is put into the Buffer defined as above and the field list is constructed reflecting the content of the Buffer. The layout of the field list┆
0x3bc00…3bd00 (59, 0, 12) Sector 3b0df700202241 ┆; w "A is shown in fig. 4.1.7.2.3-2 and the Buffer in fig. 4.1.7.2.3-3. The Number of bytes is the byte length of the transfer (i.e. the example the length of record 1 + record 2 + record 3 + record 4 but excluding the unused part of Buffer 2). Call R┆
0x3bd00…3be00 (59, 0, 13) Sector 3b0e7a00202241 ┆; z "A 1 Fig. 4.1.7.2.3-1 Field Transfer Interface ges a format, either before it has been output or after. Input: Interface # (IFCB index) Line number Line incarnation numb┆
0x3be00…3bf00 (59, 0, 14) Sector 3b0f7300202241 ┆; s "A 1 Fig. 4.1.7.2.3-2 Field List Layout f the last line not shifted down. In order to insert one or more lines above an already defined set, incarnation must be set to zero. Call┆
0x3bf00…3c000 (59, 0, 15) Sector 3b007200202241 ┆; r "A 1 Figure 4.1.7.2.3-3 BUFFER LAYOUT INTERFACE NO: IFCB INDEX, LINE NUMBER: LINE NUMBER TYPE, INCARNATION NUMBER: INCARNATION NUMBER TYPE, NUMBER ┆
0x3c000…3c100 (60, 0, 0) Sector 3c01ff00202241 ┆< "AOF LINES: INTEGER) (CC: COMPLETION CODE): ERROR OK b1) MON (SCM, SYSCALL FH INSERT LINES: R6, R1, R2, R3, R4, R5, R7): ERROR OK b2) COMON (CSYSCALL, FH INSERT LINES, R1,R2,R3,R4┆
0x3c100…3c200 (60, 0, 1) Sector 3c02ff00202241 ┆< "A,R5,R6,R7): ERROR OK Call Registers R1 INTERFACE NO R2 LINE NUMBER R3 INCARNATION NUMBER R4 NUMBER OF LINES Return Registers R7 CC (OK, INSERT NOT ALLOWED, VDU SPLIT FAILED) ┆
0x3c200…3c300 (60, 0, 2) Sector 3c033a00202241 ┆< : "A Fatal Errors Others than above listed are fatal 4.1.7.2.2.5 NICS-TARE Data Interface The input is obtained by use of READ BYTES. Received records will be type 0, 1, 4, 5 or 6, where 0, 1 and 4 are resulting from decoding of mes┆
0x3c300…3c400 (60, 0, 3) Sector 3c04ff00202241 ┆< "A 1 4.1.7.2.3.8 DELETE LINES The DELETE LINES changes a format, either before it has been output or after. Input: Interface # (IFCB index) Line number Line incarnation numb┆
0x3c400…3c500 (60, 0, 4) Sector 3c05ff00202241 ┆< "Aer Number of lines. Output: Done VUD split failed In order to delete all lines below a specified line, the number of lines should be defined to zero. If too many lines specified, the maximum will be deleted. Note that the issuing of ┆
0x3c500…3c600 (60, 0, 5) Sector 3c06ff00202241 ┆< "AInsert or Delete Lines on a format after the format has been output implies output to the VDU. 1 Call Specification a) DELETE LINES (INTERFACE NO: IFCB INDEX, LI┆
0x3c600…3c700 (60, 0, 6) Sector 3c07ff00202241 ┆< "ANE NUMBER: LINE NUMBER TYPE, INCARNATION NUMBER: INCARNATION NUMBER TYPE, NUMBER OF LINES: INTEGER) (CC: COMPLETION CODE) b1) MON (SCM, SYSCALL, FH DELETE LINES: R6,R1,R2,┆
0x3c700…3c800 (60, 0, 7) Sector 3b08d400202241 ┆; T "AR3,R4,R5,R7): ERROR OK b2) COMON (CSYSCALL, FH DELETE LINES, R1,R2,R3,R4,R5,R7,R6): ERROR OK Call Registers R1 INTERFACE NO R2 LINE NUMBER R3 INCARNATION NUMBER R4 NUMBER OF LINES E) (CC: COMPLETION CODE) 1 ┆
0x3c800…3c900 (60, 0, 8) Sector 3c09ff00202241 ┆< "A b1) MON (SCM, SYSCALL, FH GET FORMAT: R6,R1,R3,R5,R7): ERROR OK b2) COMON (CSYSCALL, FH GET FORMAT, R1, R3,R5,R7,R6): ┆
0x3c900…3ca00 (60, 0, 9) Sector 3c0ab600202241 ┆< 6 "A ERROR OK Call Register R1 INTERFACE NO R2 Pointer to FORMAT ID Return Registers R7 CC (OK) Fatal Errors All errors are fatal pplied for all access defined below because it eventually defines the act┆
0x3ca00…3cb00 (60, 0, 10) Sector 3c0bff00202241 ┆< "A 1 4.1.7.2.3.6 OUTPUT FORMAT The OUTPUT FORMAT transfers the format from the defined format file to the defined VDU split. Input: Interface # (IFCB index). Output: Done VDU┆
0x3cb00…3cc00 (60, 0, 11) Sector 3c0cff00202241 ┆< "A split failed Call Specification a) OUTPUT FORMAT (INTERFACE NO: IFCD INDEX) (CC: COMPLETION CODE): ERROR OK b1) MON (SCM, SYSCALL, FH OUTPUT FORMAT: R6, R1, R5, R7) ERROR OK b2) COMON (CSYSCALL, FH┆
0x3cc00…3cd00 (60, 0, 12) Sector 3c0de600202241 ┆< f "A OUTPUT FORMAT R1, R5, R7, R6): ERROR OK Call Registers R1 INTERFACE NO Return Registers R7 CC (OK, VDU SPLIT FAILED) Fatal Errors Other than above fatal : ERROR OK Call R┆
0x3cd00…3ce00 (60, 0, 13) Sector 3c0eff00202241 ┆< "A 1 4.1.7.2.3.7 INSERT LINES The INSERT LINES changes a format, either before it has been output or after. Input: Interface # (IFCB index) Line number Line incarnation numb┆
0x3ce00…3cf00 (60, 0, 14) Sector 3c0fff00202241 ┆< "Aer Number of lines. Output: Done VDU split failed The incarnation number is the identification of the last line not shifted down. In order to insert one or more lines above an already defined set, incarnation must be set to zero. Call┆
0x3cf00…3d000 (60, 0, 15) Sector 3c00ff00202241 ┆< "A Specification 1 a) INSERT LINES (INTERFACE NO: IFCB INDEX, LINE NUMBER: LINE NUMBER TYPE, INCARNATION NUMBER: INCARNATION NUMBER TYPE, NUMBER ┆
0x3d000…3d100 (61, 0, 0) Sector 3d01ff00202241 ┆= "A FILESYSTEMNAME: FILE SYSTEM NAME, CONT ID: OFFER ID, DATA ID: OFFER ID) (CC: COMPLETION CODE): ERROR OK 1 b1) MON (SCM, SYSCALL, FH┆
0x3d100…3d200 (61, 0, 1) Sector 3d02ff00202241 ┆= "A INIT TERMINAL: R6,R0,R1,R3,R4,R8,R7): ERROR OK b2) COMON (CSYSCALL, FH INIT TERMINAL: R0,R1,R3,R4,R5,R7,R6): ERROR OK Call Registers R0 Pointer to FILESYSTEMNAME R1 INTERFACE NO R3 CONT ID R4 DATA ID Return Registers ┆
0x3d200…3d300 (61, 0, 2) Sector 3d033a00202241 ┆= : "A R7 CC (OK) Fatal Errors All errors are fatal 4.1.7.2.2.5 NICS-TARE Data Interface The input is obtained by use of READ BYTES. Received records will be type 0, 1, 4, 5 or 6, where 0, 1 and 4 are resulting from decoding of mes┆
0x3d300…3d400 (61, 0, 3) Sector 3d04ff00202241 ┆= "A 1 4.1.7.2.3.4 REMOVE TERMINAL Input: Interface # (IFCB index) Output: Done Call Specification a) REMOVE TERMINAL (INTERFACE NO: IFCD INDEX) (CC: COMPLETION ┆
0x3d400…3d500 (61, 0, 4) Sector 3d05ff00202241 ┆= "ACOPE): ERROR OK b1) MON (SCM, SYSCALL, FH REMOVE TERMINAL: R6, R1, R5, R7): ERROR OK b2) COMON (CSYSCALL, FH REMOVE TERMINAL, R1, R5, R7, R6): ERROR OK Call Registers R1 INTERFACE NO Return Registers R7 CC (O┆
0x3d500…3d600 (61, 0, 5) Sector 3d062b00202241 ┆= + "AK) Fatal Errors All errors fatal N (CSYSCALL, FH INIT FORMAT, R1, R2, R4, R5, R7, R6): ERROR OK Call Registers R1 Pointer to FILENAME R2 SPLITS R4 FILEDECR DIR Return Registers R7 CC (OK) Fatal Errors All errors are fa┆
0x3d600…3d700 (61, 0, 6) Sector 3d07ff00202241 ┆= "A 1 4.1.7.2.3.5 GET FORMAT The format handling functions are used to get and change formats and output them onto the VDU split. The GET FORMAT defines a format on the already define┆
0x3d700…3d800 (61, 0, 7) Sector 3c08ff00202241 ┆< "Ad format file and reads-in the control tables. Input: Interface # (IFCB index) Format ID. Output: Done Call Specification a) GET FORMAT (INTERFACE NO: IFCB INDEX) FORMAT ID: FORMAT ID TYPE) (CC: COMPLETION CODE) 1 ┆
0x3d800…3d900 (61, 0, 8) Sector 3d09ff00202241 ┆= "A, but it is possible to handle a different VDU split via the interface. To handle a different VDU-split, the Remove Terminal function must be called, followed by a renewed Init. Terminal. Input: Maximum size of control tables ever to be handled v┆
0x3d900…3da00 (61, 0, 9) Sector 3d0aff00202241 ┆= "Aia this interface. Maximum size of buffer ever to be used via this interface. Output: Done + interface number (IFCB index). The interface number (IFCB index) must be supplied for all access defined below because it eventually defines the act┆
0x3da00…3db00 (61, 0, 10) Sector 3d0bfa00202241 ┆= z "Aual format file used and the actual split. The DEFINE FORMAT AREA establishes a control structure in the FORMAT HANDLER for handling one split and should only be called once, whereas format file and actual split identification can be changed. BYTE┆
0x3db00…3dc00 (61, 0, 11) Sector 3d0cff00202241 ┆= "A 1 Call Specification 1 a) DEFINE FORMAT AREA (AREA REC: FORMAT AREA REC SPLIT SIZE: INTEG┆
0x3dc00…3dd00 (61, 0, 12) Sector 3d0dff00202241 ┆= "AER) (INTERFACE NO: IFCB INDEX, CC: COMPLETION CODE) b1) MON (SCM, SYSCALL, FH DEFINE FORMAT AREA: R6,R1,R2,R3,R5,R7): ERROR OK b2) COMON (CSYSCALL, FH DEFINE FORMAT AREA: R1,R2,R3,R5,R7,R6): ERROR OK Call R┆
0x3dd00…3de00 (61, 0, 13) Sector 3d0e9200202241 ┆= "Aegisters R2 Pointer AREA REC R3 SPLIT SIZE Return Registers R1 INTERFACE NO R7 CC (OK) Fatal Errors All errors are fatal major groups: - Process oriented interface. - VDU split oriented interface. Format Handler Definition┆
0x3de00…3df00 (61, 0, 14) Sector 3d0fff00202241 ┆= "A 1 4.1.7.2.3.3 INIT TERMINAL The INIT TERMINAL defines to the format handler which VDU split is handled via this interface. Input: Interface # (IFCB index) File System Name fo┆
0x3df00…3e000 (61, 0, 15) Sector 3d00ff00202241 ┆= "Ar TMS of Terminal Control Offer ID Data Offer ID Output: Done The terminal (split) used may be redefined by use of REMOVE TERMINAL and a renewed INIT TERMINAL. Call Specification a) FORMAT INIT TERMINAL (INTERFACE NO: IFCB INDEX, ┆
0x3e000…3e100 (62, 0, 0) Sector 3e01ff00202241 ┆> "Amilar for Format Lines following a Linegroup. 6) A Linegroup is defined as a set of consecutive Linegroups and/or Format Lines. 7) A Linegroup may only belong to one other Linegroup. 8) A Format Line/Linegroup may be repeated or deleted as lon┆
0x3e100…3e200 (62, 0, 1) Sector 3e02ff00202241 ┆> "Ag as any repetition has not taken place in higher levels of Linegroup definitions. 9) A repetition of a Linegroup copies exactly the Format layout for the Linegroup of the moment of the repetition request with all fields in the repeated area empty┆
0x3e200…3e300 (62, 0, 2) Sector 3e030800202241 ┆> "A. 4.1.7.2.2.5 NICS-TARE Data Interface The input is obtained by use of READ BYTES. Received records will be type 0, 1, 4, 5 or 6, where 0, 1 and 4 are resulting from decoding of mes┆
0x3e300…3e400 (62, 0, 3) Sector 3e04ff00202241 ┆> "A 1 4.1.7.2.3.1 INITIALIZE Input: Maximum number of splits handled FDCB of main catalogue Format file name Output: Done Call Specification a) INIT FORMAT (SPLITS: SPLITS ┆
0x3e400…3e500 (62, 0, 4) Sector 3e05ff00202241 ┆> "ATYPE, FILEDECR DIR: FDCB INDEX, FILENAME: FILE NAME) (CC: COMPLETION CODE): ERROR OK 1 b1) MON (SCM, SYSCALL, FH INIT FORMAT: R6, R1, R7, R┆
0x3e500…3e600 (62, 0, 5) Sector 3e06ff00202241 ┆> "A4, R5, R7): ERROR OK b2) COMON (CSYSCALL, FH INIT FORMAT, R1, R2, R4, R5, R7, R6): ERROR OK Call Registers R1 Pointer to FILENAME R2 SPLITS R4 FILEDECR DIR Return Registers R7 CC (OK) Fatal Errors All errors are fa┆
0x3e600…3e700 (62, 0, 6) Sector 3e070b00202241 ┆> "Atal. Fig. 4.1.7.2.2.5 NICS-TARE Data Interface ed and there is a break of 30 seconds (configurable), the application IO is terminated. If no application IO request is present, c┆
0x3e700…3e800 (62, 0, 7) Sector 3d08ff00202241 ┆= "A 1 4.1.7.2.3.2 Define Format Area Initialization. The first call for handling a split defines the format area to be used for this interface. The reserved format area remains reserved┆
0x3e800…3e900 (62, 0, 8) Sector 3e09ff00202241 ┆> "Ag of the message text and 5 and 6 are indicating start and end of message respectively. An error is returned if the application has no open connection to the terminal or if the message control field of the protocol is in error (i.e. blocks out of ┆
0x3e900…3ea00 (62, 0, 9) Sector 3e0aff00202241 ┆> "Asequence, precedence and type changed). Message control field errors following blocks are ignored. The input conversion is shown in fig. 4.1.7.2.2.6. Output is performed by using the IOS APPEND BYTES. Allowed record type are 0, 1, 4, 5 and 6. Th┆
0x3ea00…3eb00 (62, 0, 10) Sector 3e0bbc00202241 ┆> < "Ae output conversion is the inverse of the input conversion. An error code will be returned to the requestor (e.g. THP) if the record length is not identical to the one specified. number of bytes in the buffer. The file position (i.e. FIRST BYTE┆
0x3eb00…3ec00 (62, 0, 11) Sector 3e0c7c00202241 ┆> | "A 1 Fig. 4.1.7.2.2.6 CCIS/SCARS Data Interface he TRC and P to P are interfaced by use of the IOS APPEND BYTES and READ BYTES with record types identical to the ones shown for PT┆
0x3ec00…3ed00 (62, 0, 12) Sector 3e0dff00202241 ┆> "A 1 4.1.7.2.3 Format Handler Interface The FORMAT HANDLER is a set of monitor procedures called via the System Call Monitor. For each of the below specified interface routines, the ┆
0x3ed00…3ee00 (62, 0, 13) Sector 3e0eff00202241 ┆> "Aapplication may issue all system call monitor functions: INIT, WAIT, CANCEL, WAIT NEXT. The interface routines can be grouped into two major groups: - Process oriented interface. - VDU split oriented interface. Format Handler Definition┆
0x3ee00…3ef00 (62, 0, 14) Sector 3e0fff00202241 ┆> "As, Adat. - P3 extensions 1) Any number of consecutive Format Lines may be defined as a line group. 2) A Format Line can only belong to one line group. 3) A Linegroup is consecutive to another Linegroup if the Format Line number of the first li┆
0x3ef00…3f000 (62, 0, 15) Sector 3e00ff00202241 ┆> "Ane of the Linegroup is one superior to the last Format Line of the other Linegroup. 4) A consecutive set of Format Lines are consecutive to a Linegroup if the last Format Line in the Linegroup is one below the first Format-line in the set. 5) Si┆
0x3f000…3f100 (63, 0, 0) Sector 3f014400202241 ┆? D "Aontrol characters ETB are not returned to the application. figure 4.1.7.2.2.1-1 FIRST BYTE. Files Appends the contents of the buffer to the file. The size of the file is increased with the number of bytes in the buffer. ┆
0x3f100…3f200 (63, 0, 1) Sector 3f026400202241 ┆? d "A 1 Fig. 4.1.7.2.2.4-1 nterface The PTP is interfaced by use of IOS APPEND BYTES with record types as shown in figure 4.1.6.2.2.2-1. If the key is off or the application has no┆
0x3f200…3f300 (63, 0, 2) Sector 3f03ff00202241 ┆? "A 1 4.1.7.2.2.5 NICS-TARE Data Interface The input is obtained by use of READ BYTES. Received records will be type 0, 1, 4, 5 or 6, where 0, 1 and 4 are resulting from decoding of mes┆
0x3f300…3f400 (63, 0, 3) Sector 3f04ff00202241 ┆? "Asage text and 5 and 6 are indicating start and end of message respectively. An error is returned if the application has no open connection to the terminal or if a fatal error has occured on the link. The input conversion is shown in fig. 4.1.7.2┆
0x3f400…3f500 (63, 0, 4) Sector 3f05ff00202241 ┆? "A.2.5. Output is performed by using IOS APPEND BYTES. Allowed record types are 0, 1, 4, 5 and 6. The output conversion is the inverse of the input conversion. An error code will be returned if the record length is not identical to the one specified┆
0x3f500…3f600 (63, 0, 5) Sector 3f060b00202241 ┆? "A. ate recording of already received characters into a type 0 and collection of control characters in type 4. If a control sequence is longer than 69 characters it will be collected in a type 4 record and new record will start. If normal character┆
0x3f600…3f700 (63, 0, 6) Sector 3f077b00202241 ┆? { "A 1 Fig. 4.1.7.2.2.5 NICS-TARE Data Interface ed and there is a break of 30 seconds (configurable), the application IO is terminated. If no application IO request is present, c┆
0x3f700…3f800 (63, 0, 7) Sector 3e08ff00202241 ┆> "A 1 4.1.7.2.2.6 CCIS/SCARS Data Interface The input is obtained by use of READ BYTES. Received records will be of type 0, 1, 4, 5 or 6, where 0, 1 and 4 are are resulting from decodin┆
0x3f800…3f900 (63, 0, 8) Sector 3f092000202241 ┆? "Aned as described above. as data and a new record is initiated (control type). b) The line length exceeds the predefined length. The line is defined as data and a new record is initiated. c) An unexpected V24 line status change or a key on/off┆
0x3f900…3fa00 (63, 0, 9) Sector 3f0a7100202241 ┆? q "A 1 Fig. 4.1.7.2.2.2-1 PTP Interface erminated as a data record and the IO request is terminated with an error code indicating the reason for termination. The general layout of ┆
0x3fa00…3fb00 (63, 0, 10) Sector 3f0b7200202241 ┆? r "A 1 Fig. 4.1.7.2.2.2-2 PTR Interface , the size is increased to the file position of the byte sequence plus the number of bytes in the buffer. The file position (i.e. FIRST BYTE┆
0x3fb00…3fc00 (63, 0, 11) Sector 3f0cff00202241 ┆? "A 1 4.1.7.2.2.3 TRC, Point to Point Data Interface The TRC and P to P are interfaced by use of the IOS APPEND BYTES and READ BYTES with record types identical to the ones shown for PT┆
0x3fc00…3fd00 (63, 0, 12) Sector 3f0dff00202241 ┆? "AP/PTR in section 4.1.6.2.2.2. 4.1.7.2.2.4 OCR Data Interface The OCR is interfaced by use of IOS READ BYTES. Received records will be type 0, 1, 4, 5, or 6 as shown in figure 4.1.6.2.2.4-1. If the application has no open connection an error cod┆
0x3fd00…3fe00 (63, 0, 13) Sector 3f0eff00202241 ┆? "Ae is returned. The conventions for ITA 5 input processing for OCR are as follows: Characters are normally collected in type 1 records, where either the sequence "CR, CR, LF" or "CR, LF" is used as separator. When more than 69 characters have bee┆
0x3fe00…3ff00 (63, 0, 14) Sector 3f0fff00202241 ┆? "An received without this termination of line, they are collected in a type 0 record and a new count initiated. Occurence of any other control character (-sequence) than above line termination leads to an immediate recording of already received info i┆
0x3ff00…40000 (63, 0, 15) Sector 3f00ff00202241 ┆? "An type 0 and collection of control chars in type 4. If a control charseq. is longer than 69 it is divided into several of max length 69. The first occurence of a non-control character terminates the type 4 record and starts building a type 0 or 1. C┆
0x40000…40100 (64, 0, 0) Sector 40016b00202241 ┆@ k "A 1 figure 4.1.7.2.2.1-1 FIRST BYTE. Files Appends the contents of the buffer to the file. The size of the file is increased with the number of bytes in the buffer. ┆
0x40100…40200 (64, 0, 1) Sector 4002ff00202241 ┆@ "A 1 4.1.7.2.2.2 PTP/PTR Data Interface The PTP is interfaced by use of IOS APPEND BYTES with record types as shown in figure 4.1.6.2.2.2-1. If the key is off or the application has no┆
0x40200…40300 (64, 0, 2) Sector 4003ff00202241 ┆@ "A open connection to the terminal, an error will be returned. The PTP interface accepts types 0, 1, 4. The PTR is interfaced by use of IOS READ BYTES. Received records will be type 0, 1 or 4 as shown in figure 4.1.6.2.2.2-2. If the application ha┆
0x40300…40400 (64, 0, 3) Sector 4004ff00202241 ┆@ "As no open connection to the terminal an error code is returned. The conventions for ITA 5 input processing for PTR are as follows: Characters are normally collected in type 1 records, where either the sequence "CR, CR, LF" or "CR, LF" is used as┆
0x40400…40500 (64, 0, 4) Sector 4005ff00202241 ┆@ "A separator. Where more than 69 characters have been received without this termination of line, they are collected in a type 0 record and a new count is initiated. Occurrence of any other control characters than above line termination leads to an i┆
0x40500…40600 (64, 0, 5) Sector 4006ff00202241 ┆@ "Ammediate recording of already received characters into a type 0 and collection of control characters in type 4. If a control sequence is longer than 69 characters it will be collected in a type 4 record and new record will start. If normal character┆
0x40600…40700 (64, 0, 6) Sector 4007ff00202241 ┆@ "As (1 or more) are received, record type 4 is terminated and a type 0 or 1 started. If any character has been received and there is a break of 30 seconds (configurable), the application IO is terminated. If no application IO request is present, c┆
0x40700…40800 (64, 0, 7) Sector 3f08ff00202241 ┆? "Aharacters received from the PTR are lost. For lines operating in ITA 2, the same rules apply, except that Shift In and Shift Out characters are allowed to determine the meaning of next characters. Superfluous Letter shift or Figure shift are retur┆
0x40800…40900 (64, 0, 8) Sector 4009ff00202241 ┆@ "Aters). The line is defined as data and a new record is initiated (control type). b) The line length exceeds the predefined length. The line is defined as data and a new record is initiated. c) An unexpected V24 line status change or a key on/off┆
0x40900…40a00 (64, 0, 9) Sector 400aff00202241 ┆@ "A or a timeout (more than predefined time interval between two characters) detected. The current record is terminated as a data record and the IO request is terminated with an error code indicating the reason for termination. The general layout of ┆
0x40a00…40b00 (64, 0, 10) Sector 400b3800202241 ┆@ 8 "Athe buffer is presented in figure 4.1.7.2.2-1. of) the bytes in the byte sequence is not part of the file, the size is increased to the file position of the byte sequence plus the number of bytes in the buffer. The file position (i.e. FIRST BYTE┆
0x40b00…40c00 (64, 0, 11) Sector 400c6400202241 ┆@ d "A 1 Figure 4.1.7.2.2-1 FILEDECR: FDCB INDEX, FILADD: FILE ADDRESS BLE: BUFFER LIST ELEMENT) (FILADD: FILE ADDRESS, CC: COMPLETION CODE): ┆
0x40c00…40d00 (64, 0, 12) Sector 400dff00202241 ┆@ "A 1 FLAG BYTE VALUES 0 Normal data (ASCII HEX 20 to HEX 7F) 1 Line or Field (ASCII HEX 20 to HEX 7F). For incoming (CR, CR, LF) or (CR, LF) or other separator detected. For o┆
0x40d00…40e00 (64, 0, 13) Sector 400eff00202241 ┆@ "Autgoing the sequence as specified is attached. 2 Spare 3 Spare 4 Control sequences from/to application to/from device/line. 5 Control sequence from/to Application to/from IOC start of message 6 Do - end of message 7 ACK 4.1.7.2.┆
0x40e00…40f00 (64, 0, 14) Sector 400fff00202241 ┆@ "A2.1 Medium Speed Teleprinter Data Interface The Medium Speed Teleprinter is interfaced by use of IOS APPEND BYTES with record types as shown in figure 4.1.6.2.2.1-1. If the key is off or the application has no open connection to the terminal an┆
0x40f00…41000 (64, 0, 15) Sector 40005000202241 ┆@ P "A error code will be returned. The MSTP interface accepts types 0, 1, 4. el not lower than the access level for the terminal (i.e. VDUs cannot be directly accessed). The function is used to output data to a terminal. The device handler for the ┆
0x41000…41100 (65, 0, 0) Sector 4101ff00202241 ┆A "Aterminal is called to output data. "Append bytes" is equivalent to "modify bytes" with an undefined FIRST BYTE. Files Appends the contents of the buffer to the file. The size of the file is increased with the number of bytes in the buffer. ┆
0x41100…41200 (65, 0, 1) Sector 4102ff00202241 ┆A "ACall Specification a) APPENDBYTES (CONID: USER CONNECTION TYPE FILADD: FILE ADDRESS, BLE: BUFFER LIST ELEMENT) (FILADD: FILE ADDRESS, CC: COMPLETION CODE): ERROR OK Note: BLE is the first BLE in a ch┆
0x41200…41300 (65, 0, 2) Sector 4103f800202241 ┆A x "Aain. 1 b1) MON (SCM, SYSCALL, IO APPENDBYTES: R6, R1, R2, R4, R5, R7): ERROR OK b2) COMON (CSYSCALL, IO APPENDBYTES, R1, R2, R4, R5, R7, R6): ERROR OK rights┆
0x41300…41400 (65, 0, 3) Sector 4104ba00202241 ┆A : "A 1 Call Registers R1 Pointer to FILADD R2 Pointer to BLE R4 CONID Return Registers R7 CC reads one logical block of data from a terminal. The device handle┆
0x41400…41500 (65, 0, 4) Sector 4105ff00202241 ┆A "A 1 4.1.6.2.2 Data Transport Interfaces The data transport to/from a terminal is exercised by calling the IOS procedures. APPEND BYTES READ BYTES The buffer content, which is a l┆
0x41500…41600 (65, 0, 5) Sector 4106ff00202241 ┆A "Aogical contiguous byte string either specified to the IOS or returned from the IOS is formatted as specified below. The start byte identifies the start of a record. It may also occur in data, but only when flagged as control characters. The Byte┆
0x41600…41700 (65, 0, 6) Sector 4107ff00202241 ┆A "A Count gives the length of Data (so that total length is bytecount + 3). The maximum length is dependent on the interfaced line. The flag byte give the type of the data transferred. It may be a line or a field or a string of control characters. If┆
0x41700…41800 (65, 0, 7) Sector 4008ff00202241 ┆@ "A a line of text has not been terminated in a normal way the Flag Byte indicates this. Three ways of abnormal termination may be identified. a) The line is not terminated by the normal character sequence, but by a different sequence (control charac┆
0x41800…41900 (65, 0, 8) Sector 4109b800202241 ┆A 8 "A 1 Call Registers R1 Pointer to FILADD R2 Pointer to BLE R4 CONID Return Registers R7 CC ld file name" to "new file name". Call Specification a) RENAME (FIL┆
0x41900…41a00 (65, 0, 9) Sector 410aff00202241 ┆A "A 1 4.1.7.2.1.14 MODIFYBYTES Functional Description Terminals MODIFYBYTES should not be used on terminals. Files Modifies a sequence of bytes in the specified file, with┆
0x41a00…41b00 (65, 0, 10) Sector 410bff00202241 ┆A "A the contents of the buffer specified. If (some of) the bytes in the byte sequence is not part of the file, the size is increased to the file position of the byte sequence plus the number of bytes in the buffer. The file position (i.e. FIRST BYTE┆
0x41b00…41c00 (65, 0, 11) Sector 410cff00202241 ┆A "A) may not exceed the size of the file before the call. Call Specification a) MODIFYBYTES (FILEDECR: FDCB INDEX, FILADD: FILE ADDRESS BLE: BUFFER LIST ELEMENT) (FILADD: FILE ADDRESS, CC: COMPLETION CODE): ┆
0x41c00…41d00 (65, 0, 12) Sector 410dff00202241 ┆A "AERROR OK Note: BLE is the first BLE in a chain. 1 b1) MON (SCM, SYSCALL, IO MODIFYBYTES: R6, R1, R2, R4, R5, R7): ERROR OK b2) COMON (CSYSCALL, IO MODIFYBYTES, R1┆
0x41d00…41e00 (65, 0, 13) Sector 410e9800202241 ┆A "A, R2, R4, R5, R7, R6): ERROR OK Call Registers R1 Pointer to FILADD R2 Pointer to BLE R4 FILEDECR Return Registers R7 CC Pointer to FILENAME R4 FILEDECR DIR Return Registers R7 CC NB: Subject for revision. File┆
0x41e00…41f00 (65, 0, 14) Sector 410fff00202241 ┆A "A 1 4.1.7.2.1.16 APPENDBYTES Functional Description Terminals It is checked that FD identifies a connection from the caller to a subdevice of type terminal. Caller's access righ┆
0x41f00…42000 (65, 0, 15) Sector 4100ff00202241 ┆A "Ats are checked. It is checked that the function is called from a CPU level not lower than the access level for the terminal (i.e. VDUs cannot be directly accessed). The function is used to output data to a terminal. The device handler for the ┆
0x42000…42100 (66, 0, 0) Sector 4201ff00202241 ┆B "A SYSCALL, IO GETROOT: R6, R0, R1, R4, R5, R7): ERROR OK b2) COMON (CSYSCALL, IO GETROOT, R0, R1, R4, R5, R7, R6): ERROR OK Call Registers R0 Pointer to FILESYSTEMNAME R1 Pointer to VOLUMENAME Return Registers R4 FILEDE┆
0x42100…42200 (66, 0, 1) Sector 42021700202241 ┆B "ACR ROOT R7 CC 4.1.7.2.1.8 LOOKUP Functional Description Terminals Refer description for ENTER Files Retrieves in an SFD a file given by symbolic name. The file becomes open for access ┆
0x42200…42300 (66, 0, 2) Sector 4203ff00202241 ┆B "A 1 4.1.7.2.1.13 READBYTES Functional Description Terminals It is checked that FD identifies a connection from the caller to a subdevice of type terminal. Caller's access rights┆
0x42300…42400 (66, 0, 3) Sector 4204ff00202241 ┆B "A are checked. It is checked that the function is called from a CPU level not lower than the access level for the terminal (Log. VDUs cannot be accessed directly). The function reads one logical block of data from a terminal. The device handle┆
0x42400…42500 (66, 0, 4) Sector 4205ff00202241 ┆B "Ar corresponding to the terminal is called to enable input. The data is delivered into a buffer supplied by the caller. The amount of data transferred will be one logical block of data (protocol dependent) but at most the length specified in FILADD┆
0x42500…42600 (66, 0, 5) Sector 4206ff00202241 ┆B "A. The FIRST BYTE in FILADD is ignored but should for compatibility with the FMS command be set to zero at first read (and will be updated subsequently) Files Reads a sequence of bytes from the specified file into a buffer supplied by the calle┆
0x42600…42700 (66, 0, 6) Sector 4207ff00202241 ┆B "Ar. Call Specification a) READBYTES (CONID: USER CONNECTION TYPE FILADD: FILE ADDRESS, BLE: BUFFER LIST ELEMENT) (FILADD: FILE ADDRESS, CC: COMPLETION CODE): ERROR OK Note: BLE is the first BLE in a chain. 1┆
0x42700…42800 (66, 0, 7) Sector 4108eb00202241 ┆A k "A b1) MON (SCM, SYSCALL, IO READBYTES: R6, R1, R2, R4, R5, R7): ERROR OK b2) COMON (CSYSCALL, IO READBYTES, R1, R3, R4, R5, R7, R6): ERROR OK reby get a file desc┆
0x42800…42900 (66, 0, 8) Sector 4209ff00202241 ┆B "A 1 4.1.7.2.1.10 RENAME Functional Description Changes the name of the file in the specified directory from "old file name" to "new file name". Call Specification a) RENAME (FIL┆
0x42900…42a00 (66, 0, 9) Sector 420aff00202241 ┆B "AEDECR DIR: FDCB INDEX, FILENAMES: FILE NAMES) (CC: COMPLETION CODE): ERROR OK b1) MON (SCM, SYSCALL, IO RENAME: R6, R1, R4, R5, R7): ERROR OK b2) COMON (CSYSCALL, IO RENAME, R1, R4, R5, R7, R6): ERROR OK Call Registers ┆
0x42a00…42b00 (66, 0, 10) Sector 420b5200202241 ┆B R "A R1 Pointer to FILENAMES R4 FILEDECR DIR Return Registers R7 CC ER CONNECTION TYPE ACCDECR: ACCESS DESCRIPTION) (OFID: OFFER ID, CC: COMPLETION CODE): ERROR OK 1 ┆
0x42b00…42c00 (66, 0, 11) Sector 420cff00202241 ┆B "A 1 4.1.7.2.1.11 REMOVE Functional Description Deletes the symbolic name of a file from the SFD. If the names of the file has now been removed from all SFDs in which it has been en┆
0x42c00…42d00 (66, 0, 12) Sector 420dff00202241 ┆B "Atered, the file will either be deleted (if it is not open for access by any user) or become temporary. Call Specification a) REMOVE (FILEDECR DIR: FDCB INDEX, FILENAME: FILE NAME) (CC: COMPLETION CODE): ERROR OK. b1) MON (SCM, SY┆
0x42d00…42e00 (66, 0, 13) Sector 420ede00202241 ┆B ^ "ASCALL, IO REMOVE: R6, R1, R4, R5, R7): ERROR OK b2) COMON (CSYSCALL, IO REMOVE, R1, R4, R5, R7, R6): ERROR OK Call Registers R1 Pointer to FILENAME R4 FILEDECR DIR Return Registers R7 CC NB: Subject for revision. File┆
0x42e00…42f00 (66, 0, 14) Sector 420fff00202241 ┆B "A 1 4.1.7.2.1.12 GETROOT Functional Description Returns a file descriptor for the root SFD on the specified volume. The root SFD becomes open for access by the caller. Call Speci┆
0x42f00…43000 (66, 0, 15) Sector 4200ff00202241 ┆B "Afication a) GETROOT (FILESYSTEMNAME: FILE SYSTEM NAME, VOLUMENAME: VOLUME NAME) (FILEDECR ROOT: FDCB INDEX, CC: COMPLETION CODE): ERROR OK 1 b1) MON (SCM,┆
0x43000…43100 (67, 0, 0) Sector 43019f00202241 ┆C "A, R1, R2, R4, R5, R7, R6): ERROR OK Call Registers R1 Pointer to FILENAME R2 FILEDECR FILE R4 FILEDECR DIR Return Registers R7 CC ERROR OK b2) COMON (SYSCALL, IO RESET, R4, R5, R7, R6): ERROR ┆
0x43100…43200 (67, 0, 1) Sector 4302ff00202241 ┆C "A 1 4.1.7.2.1.8 LOOKUP Functional Description Terminals Refer description for ENTER Files Retrieves in an SFD a file given by symbolic name. The file becomes open for access ┆
0x43200…43300 (67, 0, 2) Sector 4303ff00202241 ┆C "Aby the caller. Call Specification a) LOOKUP (FILEDECR DIR: FDCB INDEX, FILENAME: FILE NAME) (FILEDECR FILE: FDCB INDEX, CC: COMPLETION CODE): ERROR OK 1 ┆
0x43300…43400 (67, 0, 3) Sector 4304ff00202241 ┆C "A b1) MON SCM, SYSCALL, IO LOOKUP: R6, R1, R2, R4, R5, R7): ERROR OK b2) COMON (CSYSCALL, IO LOOKUP, R1, R2, R4, R5, R7, R6): ERROR OK Call Registers R1 Pointer to FILENAME R4 FILEDECR DIR Return Registers R2 FILE┆
0x43400…43500 (67, 0, 4) Sector 43051900202241 ┆C "ADECR FILE R7 CC EMNAME: FILE SYSTEM NAME, OFID: OFFER ID) (CONID: USER CONNECTION TYPE CC: COMPLETION CODE): ERROR OK 1 b1) MON (SCM, SYSCALL, IO┆
0x43500…43600 (67, 0, 5) Sector 4306ff00202241 ┆C "A 1 4.1.7.2.1.9 DESCENT Functional Description Works as lookup. However, an implicit "dismantle" is made on the SFD. Call Specification a) DESCENT (FILEDECR DIR: FDCB INDEX, ┆
0x43600…43700 (67, 0, 6) Sector 4307ff00202241 ┆C "A FILENAME: FILE NAME) (FILEDECR FILE: FDCB INDEX, CC: COMPLETION CODE): ERROR OK b1) MON (SCM, SYSCALL, IO DESCENT: R6, R1, R4, R5, R7): ERROR OK b2) COMON (CSYSCALL, IO DESCENT, R1, R4, R5, R7, R6): ERROR OK Cal┆
0x43700…43800 (67, 0, 7) Sector 42087000202241 ┆B p "Al Registers R1 Pointer to FILENAME R4 FILEDECR DIR Return Registers R4 FILEDECR FILE R7 CC tion The caller offers a file to another user. This means that the user specified, may issue an "accept" command and thereby get a file desc┆
0x43800…43900 (67, 0, 8) Sector 4309ff00202241 ┆C "Ariptor of the file. The user will thus be able to access the file. In this way it is possible for several users to exchange information via a file without a name. The access rights of the user who accepts the file, depends on whether or not the ┆
0x43900…43a00 (67, 0, 9) Sector 430aff00202241 ┆C "Auser who "offers" the file are allowed to protect the file: - "offerer" has protect right: "accepter" gets the access rights which are the union of: 1) the rights the "accepter" already have 2) the intersection of the "offered" and the righ┆
0x43a00…43b00 (67, 0, 10) Sector 430bff00202241 ┆C "Ats the rights the "offerer" have. Call Specification a) OFFER (CONID: USER CONNECTION TYPE ACCDECR: ACCESS DESCRIPTION) (OFID: OFFER ID, CC: COMPLETION CODE): ERROR OK 1 ┆
0x43b00…43c00 (67, 0, 11) Sector 430cff00202241 ┆C "A b1) MON (SCM, SYSCALL, IO OFFER: R6, R1, R3, R4, R5, R7): ERROR OK b2) COMON (CSYSCALL, IO OFFER, R1, R2, R3, R4, R5, R7, R6): ERROR OK Call Registers R1 Pointer to ACCDECR R4 CONID Return Registers R┆
0x43c00…43d00 (67, 0, 12) Sector 430d1700202241 ┆C "A3 OFID R7 CC will be deleted. Terminals It is checked that FD identifies a connection from the caller to a subdevice. Not completed operations on the connection are cancelled. The connection is removed and will not be accessible anymore┆
0x43d00…43e00 (67, 0, 13) Sector 430eff00202241 ┆C "A 1 4.1.7.2.1.7 ENTER Functional Specification Terminals The ENTER function for TMS only works, when TMS is in control of connection selection. NB: Subject for revision. File┆
0x43e00…43f00 (67, 0, 14) Sector 430fff00202241 ┆C "As The subject file is named in the SFD specified in the second parameter with the name given as the first parameter. The subject file becomes permanent. Call Specification a) ENTER (FILEDECR DIR: FDCB INDEX, FILEDECR FILE: FDCB INDEX, ┆
0x43f00…44000 (67, 0, 15) Sector 4300ff00202241 ┆C "A FILENAME: FILE NAME) (CC: COMPLETION CODE): ERROR OK 1 b1) MON (SCM, SYSCALL, IO ENTER: R6, R1, R2, R4, R5, R7): ERROR OK b2) COMON (CSYSCALL, IO ENTER┆
0x44000…44100 (68, 0, 0) Sector 4401ff00202241 ┆D "A Specification a) RESET (FILEDECR: FDCB INDEX) (CC: COMPLETION CODE): ERROR OK b1) MON (SCM, SYSCALL, IO RESET: R6, R4, R5, R7): ERROR OK b2) COMON (SYSCALL, IO RESET, R4, R5, R7, R6): ERROR ┆
0x44100…44200 (68, 0, 1) Sector 44024600202241 ┆D F "AOK Call Registers R4 FILEDECR Return Registers R7 CC ace descriptions are: CAMPS ICDs ICD/004 through 8. : integer; PURGE "C K purge flag : boolean; END; TYPE ENABLE STATUS PARAM = "used when calling enable status┆
0x44200…44300 (68, 0, 2) Sector 4403ff00202241 ┆D "A 1 4.1.7.2.1.5 ACCEPT Functional Description Returns a file descriptor to a file/terminal, that has previsouly been offered to the caller. The offer transaction is identified by t┆
0x44300…44400 (68, 0, 3) Sector 4404ff00202241 ┆D "Ahe offer identification given as call parameter. The file/terminal becomes open for access by the caller with the file descriptor as identification. Note: The OFID must be made known to the caller of ACCEPT by the offerer. Call Specification ┆
0x44400…44500 (68, 0, 4) Sector 4405ff00202241 ┆D "Aa) ACCEPT (FILESYSTEMNAME: FILE SYSTEM NAME, OFID: OFFER ID) (CONID: USER CONNECTION TYPE CC: COMPLETION CODE): ERROR OK 1 b1) MON (SCM, SYSCALL, IO┆
0x44500…44600 (68, 0, 5) Sector 4406ff00202241 ┆D "A ACCEPT: R6, R0, R3, R4, R5, R7): ERROR OK b2) COMON ( CSYSCALL, IO ACCEPT, R0, R3, R4, R5, R6, R7): ERROR OK Call Registers R0 Pointer to FILESYSTEMNAME R3 OFID Return Registe┆
0x44600…44700 (68, 0, 6) Sector 44071d00202241 ┆D "Ars R4 CONID R7 CC (CC: COMPLETION CODE): ERROR OK. b1) MON(SCM,SYSCASE,IO MOUNT: R6, R0, R1, R2, R5, R7): ERROR OK b2) COMON(SYSCALL, IO MOUNT, R0, R1, R2, R5, R7, R6): ┆
0x44700…44800 (68, 0, 7) Sector 4308ff00202241 ┆C "A 1 4.1.7.2.1.6 OFFER Functional Description The caller offers a file to another user. This means that the user specified, may issue an "accept" command and thereby get a file desc┆
0x44800…44900 (68, 0, 8) Sector 4409ff00202241 ┆D "A 1 4.1.7.2.1.2 DISMOUNT Functional Description The description of the volume is excluded from FMS. No files may be open for access when this command is called. Call Specificatio┆
0x44900…44a00 (68, 0, 9) Sector 440aff00202241 ┆D "An a) DISMOUNT (FILESYSTEMNAME: FILE SYSTEM NAME, VOLUMENAME: VOLUME NAME) (CC: COMPLETION CODE): ERROR OK. b1) MON (SCM, SYSCALL, IO DISMOUNT: R6, R0, R1, R5, R7): ERROR OK b2) COMON ┆
0x44a00…44b00 (68, 0, 10) Sector 440bd900202241 ┆D Y "A(SYSCALL, IO DISMOUNT, R0, R1, R5, R7, R6): ERROR OK Call Registers R0 Pointer to FILESYSTEMNAME R1 Pointer to VOLUMENAME Return Registers R7 CC high level protocols "Controller Da┆
0x44b00…44c00 (68, 0, 11) Sector 440cff00202241 ┆D "A 1 4.1.7.2.1.3 DISMANTLE Functional Description Files The file will no longer be open via the given file descriptor. If the file is not open for access by any user, and the file┆
0x44c00…44d00 (68, 0, 12) Sector 440dff00202241 ┆D "A is temporary, it will be deleted. Terminals It is checked that FD identifies a connection from the caller to a subdevice. Not completed operations on the connection are cancelled. The connection is removed and will not be accessible anymore┆
0x44d00…44e00 (68, 0, 13) Sector 440eff00202241 ┆D "A. Call Specification a) DISMANTLE (CONID: USER CONNECTION TYPE) (CC: COMPLETION CODE): ERROR OK b1) MON (SCM, SYSCALL, IO DISMANTLE: R6, R4, R5, R7): ERROR OK b2) COMON (SYSCALL, IO DISMANTLE, R4, R5, ┆
0x44e00…44f00 (68, 0, 14) Sector 440f6b00202241 ┆D k "AR7, R6): ERROR OK Call Registers R4 CONID Return Registers R7 CC 4 1 CONTROLLER 4 2, CONTROLLER 4 4, SUBDEVICE 2 7, SUBDEVICE 2 11, SUBDEVICE 8 1, PROT CONT 2 2, PROT CONT 2 3, PROT CONT 3 3 PROT CONT 5┆
0x44f00…45000 (68, 0, 15) Sector 4400ff00202241 ┆D "A 1 4.1.7.2.1.4 RESET Functional Description Removes the contents of the specified file. If the file is a random file, the sectors corresponding to the file are deallocated. Call┆
0x45000…45100 (69, 0, 0) Sector 4501ff00202241 ┆E "A 1 4.1.6 Common Data N.A. 4.1.7 Interfaces 4.1.7.1 External Interfaces The external interfaces for IOC is the electrical interface for devices and lines, where IOC in fact im┆
0x45100…45200 (69, 0, 1) Sector 45027c00202241 ┆E | "Aplements the CAMPS external interface to devices/lines. Interface descriptions are: CAMPS ICDs ICD/004 through 8. : integer; PURGE "C K purge flag : boolean; END; TYPE ENABLE STATUS PARAM = "used when calling enable status┆
0x45200…45300 (69, 0, 2) Sector 4503ff00202241 ┆E "A 1 4.1.7.2 Package Interfaces The interface for IOC can be divided into 4 main groups. a) IOS Interfaces b) Data transport interfaces (using IOS calls). c) FORMAT HANDLER i┆
0x45300…45400 (69, 0, 3) Sector 45045d00202241 ┆E ] "Anterfaces. d) Control Interfaces for defining control parameters within the IOC N, SYSTEM KEY DEVICE RESPONSE TYPE = INTEGER ,STATUS MESSAGE ); TYPE OPERATION RESULT TYPE = integer; "values: CONST OPERATION OK = OK; ┆
0x45400…45500 (69, 0, 4) Sector 4505ff00202241 ┆E "A 1 4.1.7.2.1 IOS Interfaces 4.1.7.2.1.1 MOUNT Functional Description The specified volume name is checked against the volume name actually recorded on the volume. At return the┆
0x45500…45600 (69, 0, 5) Sector 4506ff00202241 ┆E "A volume is identified by the symbolic volume name, and the functions utilizing the file structure of the volume may operate on the files. Call Specification a) MOUNT (FILESYSTEMNAME: FILE SYSTEM NAME, DEVICENAME: DEVICE NAME, VOLUMEN┆
0x45600…45700 (69, 0, 6) Sector 4507ff00202241 ┆E "AAME: VOLUME NAME) (CC: COMPLETION CODE): ERROR OK. b1) MON(SCM,SYSCASE,IO MOUNT: R6, R0, R1, R2, R5, R7): ERROR OK b2) COMON(SYSCALL, IO MOUNT, R0, R1, R2, R5, R7, R6): ┆
0x45700…45800 (69, 0, 7) Sector 4408b800202241 ┆D 8 "A ERROR OK Call Registers R0 Pointer to FILESYSTEMNAME R1 Pointer to DEVICENAME R2 Pointer to VOLUMNAME Return Registers R7 CC C ENABLE, PC OPEN PROTOCOL, PC CLOSE PROTOCOL, PC REDEFINE PARAM┆
0x45800…45900 (69, 0, 8) Sector 45093c00202241 ┆E < "AS, PC STATISTICS, PC STATUS, PC DEVICE STATUS) essage H SDID, "handler's Id for subdevice SDID: "receiver's Id for subdevice integer; STATUS: device status; INFO SIZE: "size of info field following integer; ┆
0x45900…45a00 (69, 0, 9) Sector 450aff00202241 ┆E "A 1 SDID RECORD = RECORD SDID: SDID "see DAMOS" PARENT SDID: SDID OPENER: USER ID STATUS: (DISABLED, ENABLED) STATUS SE: OBJECT DESCRIPTOR REPLY: H OP REPLY ME┆
0x45a00…45b00 (69, 0, 10) Sector 450bff00202241 ┆E "ASSAGE STATUS REPORT: H STATUS MESSAGE REPORT PRIORITY: INTEGER "Inputter data" INPUTTER: INPUTTER DATA "Outputter data" OUTPUTTER: OUTPUTTER DATA "User data" USER: USER DATA Only high level protocols "Controller Da┆
0x45b00…45c00 (69, 0, 11) Sector 450cca00202241 ┆E J "Ata" CONTROLLER: CONTROLLER DATA Only when Controller present "Subdevice data SUBDEVICE IF: SUBDEVICE INTERFACE DATA "Protocol data" PROTOCOL: Protocol dependent END END; operation status; END; TYPE SET ┆
0x45c00…45d00 (69, 0, 12) Sector 450dff00202241 ┆E "A 1 1 TYPE PROTOCOL ERR = (DUMMY, SPI ENTRY 1, SPI ENTRY 6, INPUTTER 3 4, INPUTTER 3 5, INPUTTER 3 ┆
0x45d00…45e00 (69, 0, 13) Sector 450eff00202241 ┆E "A7 INPUTTER 5 1, INPUTTER 6 1 INPUTTER 6 2, INPUTTER 7 1 INPUTTER 7 2 A,INPUTTER 7 2 B, OUTPUTTER 3 3 A, OUTPUTTER 3 3 B, OUTPUTTER 4 1, OUTPUTTER 5 2, OUTPUTTER 5 3, OUTPUTTER 6 1 OUTPUTTER 6 6, USER IF 2 4, CONTROLLER 2 4,CONTROLL┆
0x45e00…45f00 (69, 0, 14) Sector 450fff00202241 ┆E "AER 2 5 CONTROLLER 2 6,CONTROLLER 2 7 CONTROLLER 3 3,CONTROLLER 3 10, CONTROLLER 3 16,CONTROLLER 4 1 CONTROLLER 4 2, CONTROLLER 4 4, SUBDEVICE 2 7, SUBDEVICE 2 11, SUBDEVICE 8 1, PROT CONT 2 2, PROT CONT 2 3, PROT CONT 3 3 PROT CONT 5┆
0x45f00…46000 (69, 0, 15) Sector 45000a00202241 ┆E "A 3) OL STATUS DATA OFFSET = 2 SUBDEV INIT DATA = RECORD PRIORITY: PRIORITY TYPE Other data is dependent of the protocol. POSITION "C K terminal position (e.g. cursor address) ions; BYTE COUNT "C K number of bytes to output ┆
0x46000…46100 (70, 0, 0) Sector 4601ff00202241 ┆F "A 1 CONST INTERRUPT TYPE OFFSET = 2 INT ERROR CODE OFFSET = 3 REPORT PRIORITY = (PROTOCOL FAILORE PRI, EXT D FAILORE PRI, EXT D STATUS PRI, MIN┆
0x46100…46200 (70, 0, 1) Sector 46020c00202241 ┆F "A PRI) C K size of record -1 H SDID , "C K handler's Id for subdevice H OPID "C K handler's Id for operation : integer; PURGE "C K purge flag : boolean; END; TYPE ENABLE STATUS PARAM = "used when calling enable status┆
0x46200…46300 (70, 0, 2) Sector 4603ff00202241 ┆F "A 1 TYPE SD OTHER STATUS REC = RECORD ACTION TYPE: (DEVICE ACTION, USER ACTION, DEVICE RESPONSE) ACTION SUBTYPE: INTEGER END DEVICE ACTION T┆
0x46300…46400 (70, 0, 3) Sector 46049500202241 ┆F "AYPE = (PAPER OK, PAPER OUT, AUDIO ALARM USER ACTION TYPE = (KEY OFF, KEY ON, SYSTEM KEY DEVICE RESPONSE TYPE = INTEGER ,STATUS MESSAGE ); TYPE OPERATION RESULT TYPE = integer; "values: CONST OPERATION OK = OK; ┆
0x46400…46500 (70, 0, 4) Sector 4605ff00202241 ┆F "A 1 TYPE NICS-TARE FAILORE = (DF,NT LINK FAIL, NT EDC FAIL) NICS TARE OTHER STATUS = (DS, NT MAN SYNC, NT INC RESET) TYPE CCIS SCARS FAILORE (DCS, CS RX DISC, LS RX DISC)┆
0x46500…46600 (70, 0, 5) Sector 46063900202241 ┆F 9 "A CCIS SCARS OTHER STATUS = (DCSO, CS RX CONN) OUNT, "number of bytes transferred PAGE ADDR, "physical page address of buffer BYTE ADDR: "intra page byte offset to buffer integer; BUFFER TYPE "state of logical data unit ┆
0x46600…46700 (70, 0, 6) Sector 4607ff00202241 ┆F "A 1 CS COMMAND = (CSDO, CS REOPEN, CS SET UP LINK, CS DISC LINK, CS SET UP LINES, CS DISC LINES, CS SET V24, CSD7, CSD8, CSD9, CSD10, CSD11, CSD12, C┆
0x46700…46800 (70, 0, 7) Sector 4508ff00202241 ┆E "ASD13, CSD14, CSD15, CSD16, CS READ V24, CS STATISTIC) CS COMMAND ERROR = (OK, CS LEV2 NOT DISCONN, CS LEV2 NOT CONN, CS PARAM ERROR) PROT COMMAND = (PCD, PC ENABLE, PC OPEN PROTOCOL, PC CLOSE PROTOCOL, PC REDEFINE PARAM┆
0x46800…46900 (70, 0, 8) Sector 4609ff00202241 ┆F "AGE = RECORD RESPONSE: MESSAGE TYPE; " = status message H SDID, "handler's Id for subdevice SDID: "receiver's Id for subdevice integer; STATUS: device status; INFO SIZE: "size of info field following integer; ┆
0x46900…46a00 (70, 0, 9) Sector 460a5400202241 ┆F T "A INFO: "additional info (max 14 words) variable size data; END; tion : integer; POSITION :C K terminal position (e.g. cursor address) ions; BUF SIZE, "C K size in bytes of user buffer BYTE COUNT, "-R number┆
0x46a00…46b00 (70, 0, 10) Sector 460bff00202241 ┆F "A 1 4.1.4.3 IOC HANDLER DATA PRIORITY TYPE = INTEGER CONTROLLER PRIORITY = 0 USER PRIORITY = 3 SUBDEVICE PRIORITY = USER PRIORITY TYPE IO QEL = RECORD LINK: ┆
0x46b00…46c00 (70, 0, 11) Sector 460cd300202241 ┆F S "APOINTER PRIORITY: PRIORITY TYPE QUEUE: POINTER REQUESTOR: (NONE, USER, SUBDEVICE, CONTROLLER, PROTOCOL) REQ RECORD: POINTER REQ REF: INTEGER ADDI: INTEGER END; operation status; END; TYPE SET ┆
0x46c00…46d00 (70, 0, 12) Sector 460dff00202241 ┆F "A 1 CONST BUFFER TYPE OFFSET = 0 LDU OFFSET = 1 SPLIT ADDR OFFSET = 2 CONTROL REQUESTS OFFSET = 1 CANCEL INPUT LDU OFFSET = 2 CANCEL OUTPUT LDU OF┆
0x46d00…46e00 (70, 0, 13) Sector 460eff00202241 ┆F "AFSET = 2 INPUT REQ BYTE LENGTH OFFSET = 3 INPUT REQ LDU OFFSET = 2 INPUT REQ DATA OFFSET = 4 STATUS TYPE OFFSET = 1 RECEPTION STATUS LDU OFFSET = 2 TRANSMISSION STATUS LDU OFFSET = 2 TRANSMISSION STATUS COD┆
0x46e00…46f00 (70, 0, 14) Sector 460fff00202241 ┆F "AE OFFSET = 3 CONTROL PRIORITY = 0 DATA PRIORITY = 1 LDU DATA OFFSET = 1 START LDU DATA OFFSET = 2 CONTROL REQUEST = Entire LDU with control set LDU HEAD OFFSET = 1 PROTOCOL COMMAND DATA OFFSET = 2 PR┆
0x46f00…47000 (70, 0, 15) Sector 46008800202241 ┆F "AOTOCOL STATUS DATA OFFSET = 2 SUBDEV INIT DATA = RECORD PRIORITY: PRIORITY TYPE Other data is dependent of the protocol. POSITION "C K terminal position (e.g. cursor address) ions; BYTE COUNT "C K number of bytes to output ┆
0x47000…47100 (71, 0, 0) Sector 4701ff00202241 ┆G "A : integer; PURGE "C K purge flag : boolean; BUFFER TYPE "C K state of logical data unit : buffer types; END; TYPE ACK OR CANCEL PARAM = "used when calling acknowledge input and RECORD "cancel operation SIZEO┆
0x47100…47200 (71, 0, 1) Sector 4702ff00202241 ┆G "AF , "C K size of record -1 H SDID , "C K handler's Id for subdevice H OPID "C K handler's Id for operation : integer; PURGE "C K purge flag : boolean; END; TYPE ENABLE STATUS PARAM = "used when calling enable status┆
0x47200…47300 (71, 0, 2) Sector 47038200202241 ┆G "A response RECORD SIZEOF , "C K size of record -1 H SDID "C K handler's Id for subdevice : integer; END; e functions" TYPE VARIABLE SIZE DATA = ARRAY (0..0) OF INTEGER; TYPE INITIALIZE PARAM = "used when calling initialize-de┆
0x47300…47400 (71, 0, 3) Sector 4704ff00202241 ┆G "A 1 "Asynchronous response formats TYPE MESSAGE TYPE = (OP REPLY ,STATUS MESSAGE ); TYPE OPERATION RESULT TYPE = integer; "values: CONST OPERATION OK = OK; ┆
0x47400…47500 (71, 0, 4) Sector 4705ff00202241 ┆G "A OPERATION CANCELLED = REQUEST QUEUED; OPERATION ABORTED = REQUEST QUEUED; TYPE H OP REPLY MESSAGE = RECORD RESPONSE: MESSAGE TYPE; " = op reply OPID, "receiver's Id of operation H OPID "handler's Id for operation : int┆
0x47500…47600 (71, 0, 5) Sector 4706ff00202241 ┆G "Aeger; RESULT: OPERATION RESULT TYPE; BYTE COUNT, "number of bytes transferred PAGE ADDR, "physical page address of buffer BYTE ADDR: "intra page byte offset to buffer integer; BUFFER TYPE "state of logical data unit ┆
0x47600…47700 (71, 0, 6) Sector 47072100202241 ┆G ! "A :buffer types; END; "C K object descr index for subdevice status SE PROTOCOL ID "C K Id of protocol for new subdevice :integer; PARAMETERS "device dependent parameters :variable size data; END; TYPE CLOSE SUBDEVIC┆
0x47700…47800 (71, 0, 7) Sector 4608ff00202241 ┆F "A 1 TYPE DEVICE STATUS = (SUBDEVICE BREAK ,SUBDEVICE OFFLINE ,DEVICE FAILURE ,PROTOCOL EVENT ,USER RESPONSE ,SD FAILORE ,SD OTHER STATUS ); TYPE H STATUS MESSA┆
0x47800…47900 (71, 0, 8) Sector 4709ff00202241 ┆G "A 1 TYPE ENABLE PARAM = "used when calling enable input and RECORD "enable control input SIZEOF, "C K size of record -1 H SDID, "C K handler's Id for subdevice ┆
0x47900…47a00 (71, 0, 9) Sector 470aff00202241 ┆G "AH OPID, "-R handler's Id for operation OPID "C K caller's Id for operation : integer; POSITION :C K terminal position (e.g. cursor address) ions; BUF SIZE, "C K size in bytes of user buffer BYTE COUNT, "-R number┆
0x47a00…47b00 (71, 0, 10) Sector 470bff00202241 ┆G "A of bytes available PAGE ADDR, "-R physical page address of buffer BYTE ADDR "-R byte address within page of buffer integer; BUFFER TYPE "-R state of logical data unit :buffer types; END; TYPE TEST OPERATION PARAM =┆
0x47b00…47c00 (71, 0, 11) Sector 470cff00202241 ┆G "A "used when calling test operation RECORD SIZEOF , "C K size of record -1 H SDID , "C K handler's Id for subdevice H OPID : "C K handler's Id for operation integer; RESULT : "-R operation status; END; TYPE SET ┆
0x47c00…47d00 (71, 0, 12) Sector 470dff00202241 ┆G "ABUFFER PARAM = "used when calling set output buffer and RECORD "set control buffer SIZEOF , "C K size of record -1 H SDID , "C K handler's Id for subdevice H OPID , "- R handler's Id for operation OPID , "C K caller's Id f┆
0x47d00…47e00 (71, 0, 13) Sector 470ec200202241 ┆G B "Aor operation BUF SIZE , "-R size of buffer in bytes PAGE ADDR , "-R physical page address of buffer BYTE ADDR , "-R byte address of buffer within page : integer; END; page number) BUFFER ADDR, Byte address relative to page ┆
0x47e00…47f00 (71, 0, 14) Sector 470fff00202241 ┆G "A 1 TYPE INIT OUTPUT PARAM = "used when calling init output RECORD SIZEOF , "C K size of record -1 H SDID , "C K handler's Id for subdevice H OPID , "C identifies t┆
0x47f00…48000 (71, 0, 15) Sector 4700ff00202241 ┆G "Ahe buffer at call "R identifies this operation at return OPID "C K caller's Id for this operation integer; POSITION "C K terminal position (e.g. cursor address) ions; BYTE COUNT "C K number of bytes to output ┆
0x48000…48100 (72, 0, 0) Sector 4801ff00202241 ┆H "Aest record BUFFER ENTRY: INTEGER; "Pointer to buffer entry PARAM: INTEGER; "Pointer to parameter area STATUS: INTEGER; "Result of performed operation END; TYPE SPI FUNCTIONS = ( NOTIFY INPUT BUFFER, RELEASE INPUT BUFFER, RESERV┆
0x48100…48200 (72, 0, 1) Sector 4802f100202241 ┆H q "AE OUTPUT BUFFER, CANCEL RESERVE OUTPUT BUFFER, NOTIFY OUTPUT BUFFER, RELEASE OUTPUT BUFFER, TRANSMIT OUTPUT BUFFER, NOTIFY TRANSMISSION, OPEN PROTOCOL, WANT TO CLOSE, CLEAN UP ALL, CLEAN UP USER, CONTROL PROTOCOL ┆
0x48200…48300 (72, 0, 2) Sector 4803ff00202241 ┆H "A 1 "parameter records used by TMS when calling device functions" TYPE VARIABLE SIZE DATA = ARRAY (0..0) OF INTEGER; TYPE INITIALIZE PARAM = "used when calling initialize-de┆
0x48300…48400 (72, 0, 3) Sector 4804ff00202241 ┆H "Avice RECORD SIZEOF, "C K size of record -1 STATUS SE, "C K object descriptor index SDID, "C K caller's device Id H SDID, "-R handler's device Id H OPID, "-R handler's Id for operation OPID: "C K caller's Id for operat┆
0x48400…48500 (72, 0, 4) Sector 4805ff00202241 ┆H "Aion integer; PARAMETERS " device dependent parameters (may be nil) :variable-size-data; END TYPE OPEN SUBDEVICE PARAM = "used when calling open-subdevice RECORD SIZEOF, "C K size of record -1 H SDID, "C handl┆
0x48500…48600 (72, 0, 5) Sector 4806ff00202241 ┆H "Aer's Id for parent subdevice at call "R handler's Id for new subdevice at return H OPID, "-R handler's Id for operation OPID, "C K caller's Id for operation SDID, "C K caller's Id for new subdevice SDA, "C K address of n┆
0x48600…48700 (72, 0, 6) Sector 4807ff00202241 ┆H "Aew subdevice STATUS SE, "C K object descr index for subdevice status SE PROTOCOL ID "C K Id of protocol for new subdevice :integer; PARAMETERS "device dependent parameters :variable size data; END; TYPE CLOSE SUBDEVIC┆
0x48700…48800 (72, 0, 7) Sector 4708bc00202241 ┆G < "AE PARAM = "used when calling close subdevice and RECORD "shutdown SIZEOF, "C K size of record -1 H SDID "C K handler's Id for subdevice :integer; END; SDD.SISTER LINK # ref to sister SDD ┆
0x48800…48900 (72, 0, 8) Sector 4809ff00202241 ┆H "A SDD.PARENT LINK # ref to parent SDD SDD.CHILD QUEUE # QD.IP # - - - - - - # QD.EP # - - - - - - # QD.RC # SDD.SD SDID # user defined sd id # ┆
0x48900…48a00 (72, 0, 9) Sector 480aff00202241 ┆H "A SDD.SD SE # user defined SE # SDD.SDIDREF # pointer to SDID # work area for parent subdevice SDID.SDDREF # pointer to SDD # ┆
0x48a00…48b00 (72, 0, 10) Sector 480bff00202241 ┆H "A SDID.DCBREF # pointer to DCB # SDID.PROTOCOL # protocol number # SDID.STACK POINTER # stack pointer # SDID.STACK # stack of: sdid's # and ┆
0x48b00…48c00 (72, 0, 11) Sector 480c7700202241 ┆H w "A link's work area for subdevice Fig. 4.1.4.2-1 HANDLER DATA LAYOUT ter) (S]ger) (Udf]rer) Inds`t hvilket? Slette hvilket? Flytte hvilket? Kopiere hvilket? Bytte hvilket? Bytte med? S]ge hvilket? ┆
0x48c00…48d00 (72, 0, 12) Sector 480dff00202241 ┆H "A 1 TYPE BUFFER TYPES = "The buffers relation to the logical data unit (ldu) (ENTIRE LDU "whole ldu in one transfer ,START OF LDU ,PART OF-LDU ,END OF-LDU ); TYPE BUFF┆
0x48d00…48e00 (72, 0, 13) Sector 480eff00202241 ┆H "AER ENTRY = RECORD LINK, "Link field DEVICE BUFFER ID, "Device defined buffer identifier PAGE START, "Start address of page containing the buffer PAGE ADDR, "Page address (page number) BUFFER ADDR, Byte address relative to page ┆
0x48e00…48f00 (72, 0, 14) Sector 480f4600202241 ┆H F "A BUFFER SIZE "Number of bytes in buffer. : INTEGER; END; fra 4.1.4.2 I/O CTR. 15 04 82 13 46 5 16 19120 21 04 82 10 59 01 58 21 04 82 09 51 27 04 82 11 04 0155A 82 6 20 1060 21008 f *J B ] _┆
0x48f00…49000 (72, 0, 15) Sector 4800ff00202241 ┆H "A 1 TYPE SPI PARAM = RECORD PRIORITY: INTEGER; "Priority of request (O = control) BUFFER ID: INTEGER; "Caller defined buffer id. REQ RECORD: INTEGER; "Pointer to requ┆
0x49000…49100 (73, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(73,0, 1), len=0xff, h3=41202241}, f00=»2022A «, f01=»CPS/SDS/028 «, f02=»rt «, f03=»HKI «, f04=»fra 4.1.4.2 I/O CTR. «, f05=15-04-82 13:46, f06=» 5 «, f07=»16 «, f08=» 19120 «, f09=21-04-82 10:59, f10=» «, f11=»01 «, f12=» 58 «, f13=21-04-82 09:51, f14=27-04-82 11:04, f15=»0155A «, f16=» 82 «, f17=» 6 «, f18=»20 «, f19=» 1060 «, f20=» 21008 «, f21=» «, f22=» «, f99=020010000110056610110480aaca15050000000000000042032b01df}
0x49100…49200 (73, 0, 1) Sector 49025200202241 ┆I R "A I I I H H H G G G G F F F F F F E E E E E D D D D D C C C B B B B A A A A A @ @ @ @ ? ? ? ? ? ? ? > > > > = = = = < < < ; ; ; ; ; ; ; : : : 9 9 9 9 8 8 8 8 7 7 7 7 6 ntnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET ┆
0x49200…49300 (73, 0, 2) Sector 4903a000202241 ┆I "A 1 CPS/SDS/028 820421 I/O CONTROL DETAILED DESIGN SPECIFICATION CAMPS WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x49300…49400 (73, 0, 3) Sector 4904ff00202241 ┆I "A 1 1 4.1.4.2 DAMOS Definitions for handlers TYPE SDD = RECORD SISTER LINK: INTEGER; "Pointer to SDD of s┆
0x49400…49500 (73, 0, 4) Sector 4905ff00202241 ┆I "Aister subdevice PARENT LINK: INTEGER; "Pointer to SDD of parent subdevice CHILD QUEUE: QD; "Queue descriptor for child subdevices SD SDID: INTEGER; "User defined subdevice identi- fication SD SE: INTEGER; User ┆
0x49500…49600 (73, 0, 5) Sector 4906ff00202241 ┆I "Adefined synchronization element SDIDREF: INTEGER; Pointer to SDID part of SDB END; TYPE SDID = RECORD SDDREF: INTEGER; "Pointer to SDD part of SDB DCBREF: INTEGER; "Pointer to DCB PROTOCOL: INTEGER; "Pro┆
0x49600…49700 (73, 0, 6) Sector 4907aa00202241 ┆I * "Atocol table index STACK POINTER:INTEGER; "Pointer to current stack level in STACK: "Link save stack ARRAY(0..STACKSIZE-1) OF INTEGER; END; !&<6 ! "$<!#<6 ! <6 {M)(sC I! <6 ! "(= <q#p!"<6 !#<6 ! "$<!&<6$`i6 {M)(sM &M7 ┆
0x49700…49800 (73, 0, 7) Sector 4808ff00202241 ┆H "A 1 1 Subdevice Block: SDB SDD.SISTER LINK # ref to sister SDD ┆
0x49800…49900 (73, 0, 8) Sector 00000000000000 ┆ ┆
[…0x37…]
