OctetView
0x00000…00100 (0, 0, 0) Sector 01744130313734 ┆ tA0174A ┆
0x00100…00200 (0, 0, 1) Sector 00000000000000 ┆ ┆
0x00200…00300 (0, 0, 2) Sector ff00c0fffffeff ┆ @ ~ p ~ | p ┆
0x00300…00306 (0, 0, 3) WangDocument {d00=0x16, d01=0x42, d02=0x41, ptr=(73,0, 0), d05=0x00}
0x00306…0030c WangDocument {d00=0x20, d01=0x29, d02=0x41, ptr=(54,0, 0), d05=0x00}
0x0030c…00312 WangDocument {d00=0x20, d01=0x95, d02=0x41, ptr=(27,0, 0), d05=0x00}
0x00312…00318 WangDocument {d00=0x21, d01=0x21, d02=0x41, ptr=(28,0, 0), d05=0x00}
0x00318…0031e WangDocument {d00=0x21, d01=0x61, d02=0x41, ptr=(66,0, 0), d05=0x00}
0x0031e…00324 WangDocument {d00=0x21, d01=0x62, d02=0x41, ptr=(72,0, 8), d05=0x00}
0x00324…0032a WangDocument {d00=0x21, d01=0x76, d02=0x41, ptr=(70,0, 0), d05=0x00}
0x0032a…00330 WangDocument {d00=0x38, d01=0x10, d02=0x41, ptr=( 3,0, 0), d05=0x00}
0x00330…00340 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ ┆
0x00340…00360 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ ┆
[…0x4…]
0x003e0…00400 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30 ┆ 0┆
0x00400…00500 (0, 0, 4) Sector 00000000000000 ┆ ┆
0x00500…00600 (0, 0, 5) Sector 86312020202020 ┆ 1 8 7 Q? > 7 N N ~<d N ^<) 0uH &4'>( 1c5 & & ┆
0x00600…00700 (0, 0, 6) Sector 421c402600415b ┆B @& A[' d X% % PO P ; BA C g x g V W( O B :c c L ' 1642A g L < {C < { ; 4 ;s IC $jp $j- o 8 9 : L t x q ` Y ┆
0x00700…00800 (0, 0, 7) Sector 00000000000000 ┆ ┆
[…0x8…]
0x01000…01100 (1, 0, 0) WangDocumentBody
[…0x1…]
0x01200…01300 (1, 0, 2) Sector 00000000000000 ┆ ┆
[…0x5…]
0x01800…01900 (1, 0, 8) WangDocumentBody
[…0x16…]
0x02f00…03000 (2, 0, 15) Sector 00000000000000 ┆ ┆
0x03000…03100 (3, 0, 0) WangDocumentHead {hdr=WangSectHead {next=( 3,0, 1), len=0xff, h3=41381041}, f00=»3810A «, f01=»CPS/SDS/033 «, f02=»vhn «, f03=»KNB «, f04=»4.3 «, f05=13-06-83 14:35, f06=» «, f07=»38 «, f08=» 1282 «, f09=31-08-84 15:05, f10=» «, f11=»05 «, f12=» 21 «, f13=04-09-84 13:25, f14=04-09-84 13:29, f15=»0174A «, f16=» 4 «, f17=» «, f18=»43 «, f19=» 36 «, f20=» 1303 «, f21=» «, f22=» «, f99=020010000110462710110280aaca15050000000000000038030f00df}
0x03100…03200 (3, 0, 1) WangDocumentBody
[…0x6…]
0x03800…03900 (3, 0, 8) Sector 0309ff00164241 ┆ BA1) The appropriate printer device designation determined from information about the printer configuration and the actual item type. 4.2.2.1.1.2 Send Print Item (1.2) When the destination printer device is determined, the item is sent to it. ┆
0x03900…03a00 (3, 0, 9) Sector 030aff00164241 ┆ BA 4.2.2.1.2 Execution of Commands from SPICO(2.0) 4.2.2.1.2.1 Send CLOSE CMD to RESCO (2.1) When a CLOSE CMD is received it is passed on to RESCO in order to close RESCO down as well. 4.2.2.1.2.2 Cancel DELCO System Calls (2.2) All outstan┆
0x03a00…03b00 (3, 0, 10) Sector 030bff00164241 ┆ BAding sytem calls initiated by DELCO are cancelled. 4.2.2.1.2.3 Send Comments CC to SPICO (2.3) SPICO is notified when its commands have been completed. 4.2.2.1.2.4 Stop DELCO Actions (2.4) After SPICO has been notified of CLOSE completion,┆
0x03b00…03c00 (3, 0, 11) Sector 030c4300164241 ┆ C BA DELCO enters a passive state where it ignores all input. T ATTR.OBJECT,SPI) REL OP REC(SPICO CMDQ OP)(4.1.5.7) REL OP REC(SPICO DELCO OP)(4.1.5.7) INIT RECOVER FROM SPIP CMDQ END CASE END Fig. 4.2.1.4.1-6 ,1,NIL) (4.1.5.5 )┆
0x03c00…03d00 (3, 0, 12) Sector 030dff00164241 ┆ BA 1 4.2.2.1.3 Keep Account of Supervisor Printer Configuration (3.0) The current configuration is determined at two different points : of initialisation and when the configuration has┆
0x03d00…03e00 (3, 0, 13) Sector 030ebe00164241 ┆ > BA been changed. 4.2.2.1.3.1 Process Config Change Not. (3.1) When a Configuration Change Notification is received from SPICO the current configuration data will be read and the ap CASE WAIT SYSTEM CALL(SPICO CMDQ OP) (SPICO INPUT ┆
0x03e00…03f00 (3, 0, 14) Sector 0000cd00164241 ┆ M BApropriate changes in delivery strategy is performed. 4.2.2.1.3.2 Get Configuration Data (3.2) The system parameter which contains the configuration data is read by a call to Table Management. SPIP CMD SUBTYPE) (4.1.5.2) ┆
0x03f00…04000 (3, 0, 15) Sector 03004100164241 ┆ A BA END Fig. 4.2.1.6.2-1 PROC PRINTQ CANCELLED CC SPICO INPUT ATTR.FUNCTION REQ EQ FALSE? SPIP SUPV DEPLY(SPICO INPUT QEL, OK, QUEUE CANCEL NOTIFICATION ) (4.1.5.2)┆
0x04000…04100 (4, 0, 0) WangDocumentBody
[…0x3…]
0x04400…04500 (4, 0, 4) Sector 0405ff00164241 ┆ BA 1 4.2.2 Delivery Control Subpackage The Delivery Control Subpackage (DELCO) controls the delivery of print items to the appropriate printers. 4.2.2.1 Functional Specification T┆
0x04500…04600 (4, 0, 5) Sector 04069700164241 ┆ BAhe following functions are carried out by this subpackage (ref. fig. 4.2.2.1-1): Delivery of Print Items Execution of Commands from SPICO. SPICO INPUT ATTR.HEADER.INF,PRINTQ UNBLOCKED)(4.2.1.6.2 ) OTHERWISE? ERROR REP(QER,CON,SP┆
0x04600…04700 (4, 0, 6) Sector 0407b300164241 ┆ 3 BA 1 Fig. 4.2.2.1-1 DELCO Functional Breakdown - Main Functions sociate this to semaphor SPIP S1. 4.2.1.4.1.3.9 CMD TO DELCO Signal DEL┆
0x04700…04800 (4, 0, 7) Sector 0308ff00164241 ┆ BA 1 4.2.2.1.1 Delivery of Print Items (1.0) All items queued for print at SPIP, shall be delivered to the appropriate printer subqueue. 4.2.2.1.1.1 Determine Device Designation (1.┆
0x04800…04900 (4, 0, 8) WangDocumentBody
[…0xe6…]
0x12f00…13000 (18, 0, 15) Sector 1200ff00164241 ┆ BAne of the building blocks of the TEP package. For an overall description of the TEP package refer CPS/SDS/012. All Supervisor Printer Package internal data and interfaces are defined within this document in detail. For a detailed data descript┆
0x13000…13100 (19, 0, 0) WangDocumentBody
[…0x15…]
0x14600…14700 (20, 0, 6) Sector 14077d00216141 ┆ } !aAIN, FOR CONT PREP) (4.2.5.6.3) END CASE END CASE END CASE FIG. 4.2.5.4.3-5 ,1, SUBQUEUE EMPTY):(LA1) LA1? EXIT RECV NEXT LOOP END CASE OK? ┆
0x14700…14800 (20, 0, 7) Sector 1308ff00216141 ┆ !aA 1 CHANGE STATUS TO DELETED STATUS REC.STATUS = S DELETED CONVERT OUTG TO INTA(PREP REC)(4.2.5.6.7) INCLUDE IN INTA (INTA REC)(4.2.5.4.15) PREP REC STATUS = S DUMMY B┆
0x14800…14900 (20, 0, 8) WangDocumentBody
[…0x8…]
0x15100…15200 (21, 0, 1) Sector 00000000000000 ┆ ┆
[…0x6…]
0x15800…15900 (21, 0, 8) WangDocumentBody
[…0x57…]
0x1b000…1b100 (27, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(27,0, 1), len=0xff, h3=41209541}, f00=»2095A «, f01=»CPS/TCN/043 «, f02=»am] «, f03=»JJS «, f04=»Prel. user manl disk «, f05=27-04-82 17:11, f06=» «, f07=»43 «, f08=» 1877 «, f09=18-05-82 14:46, f10=» «, f11=»16 «, f12=» 114 «, f13=18-05-82 15:36, f14=25-05-82 11:14, f15=»0174A «, f16=» 60 «, f17=» 6 «, f18=»06 «, f19=» 156 «, f20=» 11308 «, f21=» «, f22=» «, f99=200034000110052710110290aaca15050000000000000142036100df}
0x1b100…1b200 (27, 0, 1) WangDocumentBody
[…0xa…]
0x1bc00…1bd00 (27, 0, 12) Sector 00000000000000 ┆ ┆
[…0x3…]
0x1c000…1c100 (28, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(28,0, 1), len=0xff, h3=41212141}, f00=»2121A «, f01=»CPS/TCN/044 «, f02=»am] «, f03=»URH «, f04=»kan slettes senere «, f05=03-05-82 10:38, f06=» «, f07=»23 «, f08=» 1442 «, f09=12-05-82 15:35, f10=» «, f11=»02 «, f12=» 18 «, f13=12-05-82 16:05, f14=25-05-82 11:14, f15=»0174A «, f16=» 2 «, f17=» 3 «, f18=»06 «, f19=» 40 «, f20=» 10652 «, f21=» «, f22=» «, f99=020030000110056610110490aaca15050000000000000042030c00df}
0x1c100…1c200 (28, 0, 1) WangDocumentBody
[…0x19e…]
0x36000…36100 (54, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(54,0, 1), len=0xff, h3=41202941}, f00=»2029A «, f01=»CPS/TCN/042, issue 2 «, f02=»vhn «, f03=»EV «, f04=» «, f05=16-04-82 12:22, f06=» «, f07=»03 «, f08=» 268 «, f09=17-10-83 14:32, f10=» «, f11=»01 «, f12=» 2 «, f13=17-10-83 11:40, f14=17-10-83 14:45, f15=»0174A «, f16=» 6 «, f17=» 6 «, f18=»21 «, f19=» 80 «, f20=» 16073 «, f21=» «, f22=» «, f99=020030000110056610110480aaca15050000000000000142031a00df}
0x36100…36200 (54, 0, 1) WangDocumentBody
[…0xbe…]
0x42000…42100 (66, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(66,0, 1), len=0xff, h3=41216141}, f00=»2161A «, f01=»CPS/SDS/039 «, f02=»rt «, f03=»JBS «, f04=»fra 4.2.5 (USER VDU) «, f05=13-05-82 10:01, f06=» 11 «, f07=»57 «, f08=» 34882 «, f09=12-02-85 13:34, f10=» «, f11=»00 «, f12=» 6 «, f13=12-02-85 13:37, f14=12-02-85 14:48, f15=»0174A «, f16=» 76 «, f17=» 39 «, f18=»38 «, f19=» 672 «, f20=» 87586 «, f21=» «, f22=» «, f99=020010000110052710110380aa8a3704000000000000014203f600df}
0x42100…42200 (66, 0, 1) WangDocumentBody
[…0x3e…]
0x46000…46100 (70, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(70,0, 1), len=0xff, h3=41217641}, f00=»2176A «, f01=»CPS/SDS/033 «, f02=»vhn «, f03=»KNB «, f04=»Table of Contents «, f05=18-05-82 13:26, f06=» 3 «, f07=»58 «, f08=» 16604 «, f09=19-10-84 14:53, f10=» «, f11=»01 «, f12=» 14 «, f13=19-10-84 14:55, f14=25-10-84 11:01, f15=»0174A «, f16=» 17 «, f17=» 16 «, f18=»29 «, f19=» 740 «, f20=» 31739 «, f21=» «, f22=» «, f99=020010000110052710110280aaca1505000000000000013003b000df}
0x46100…46200 (70, 0, 1) WangDocumentBody
[…0x26…]
0x48800…48900 (72, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(72,0, 9), len=0xff, h3=41216241}, f00=»2162A «, f01=»CPS/SDS/028 «, f02=»vhn «, f03=»HKI «, f04=»4.1.6 «, f05=13-05-82 11:00, f06=» «, f07=»39 «, f08=» 902 «, f09=11-02-85 08:48, f10=» «, f11=»07 «, f12=» 250 «, f13=11-02-85 09:00, f14=11-02-85 09:04, f15=»0174A «, f16=» 82 «, f17=» 4 «, f18=»22 «, f19=» 940 «, f20=» 10409 «, f21=» «, f22=» «, f99=180010000110052710110280aaca15050000000000000042033f01df}
0x48900…48a00 (72, 0, 9) WangDocumentBody
[…0x6…]
0x49000…49100 (73, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(73,0, 1), len=0xff, h3=41164241}, f00=»1642A «, f01=»CPS/SDS/036 «, f02=»vhn «, f03=»KS «, f04=»fra 1 «, f05=01-02-82 10:20, f06=» 3 «, f07=»44 «, f08=» 18760 «, f09=18-06-85 10:45, f10=» «, f11=»00 «, f12=» 20 «, f13=18-06-85 10:07, f14=20-06-85 09:22, f15=»0174A «, f16=» 76 «, f17=» 22 «, f18=»41 «, f19=» 652 «, f20=» 47007 «, f21=» «, f22=» «, f99=400010000110062710110280aaca1505000000000000013703ec00df}
0x49100…49200 (73, 0, 1) WangDocumentBody
[…0x6…]
0x49800…49900 (73, 0, 8) Sector 4909ff00216241 ┆I !bAescription The specified volume name is checked against the volume name actually recorded on the volume. At return the volume is identified by the symbolic volume name, and the functions utilizing the file structure of the volume may operate on t┆
0x49900…49a00 (73, 0, 9) Sector 490aff00216241 ┆I !bAhe files. Call Specification a) MOUNT (FILESYSTEMNAME: FILE SYSTEM NAME, DEVICENAME: DEVICE NAME, VOLUMENAME: VOLUME NAME) (CC: COMPLETION CODE): ERROR OK. b1) MON(SCM,SYSCASE,IO MOUNT: R6, R0, R1, R2, R5, R7): ┆
0x49a00…49b00 (73, 0, 10) Sector 490bff00216241 ┆I !bA ERROR OK b2) COMON(SYSCALL, IO MOUNT, R0, R1, R2, R5, R7, R6): ERROR OK Call Registers R0 Pointer to FILESYSTEMNAME R1 Pointer to DEVICENAME R2 ┆
0x49b00…49c00 (73, 0, 11) Sector 490c3800216241 ┆I 8 !bAPointer to VOLUMNAME Return Registers R7 CC R)() CONTROLLER PROT CONT RESULT (QEL: IO QEL,BUFFER REF:POINTER)() PROTOCOL PROT CONT RESULT (QEL:IO QEL,BUFFER REF:POINTER)() NOTIFY USER PROT CONT BUFFER (QEL:IO QEL,BUFFER REF:POINTER)() ┆
0x49c00…49d00 (73, 0, 12) Sector 490dff00216241 ┆I !bA 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┆
0x49d00…49e00 (73, 0, 13) Sector 490eff00216241 ┆I !bAn 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 ┆
0x49e00…49f00 (73, 0, 14) Sector 490fd900216241 ┆I Y !bA(SYSCALL, IO DISMOUNT, R0, R1, R5, R7, R6): ERROR OK Call Registers R0 Pointer to FILESYSTEMNAME R1 Pointer to VOLUMENAME Return Registers R7 CC 0159 ' * 7 B R _┆
0x49f00…4a000 (73, 0, 15) Sector 4900ff00216241 ┆I !bA 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┆
0x4a000…4a100 (74, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(74,0, 1), len=0xff, h3=41216241}, f00=»2162A «, f01=»CPS/SDS/028 «, f02=»vhn «, f03=»HKI «, f04=»4.1.6 «, f05=13-05-82 11:00, f06=» «, f07=»39 «, f08=» 902 «, f09=05-02-85 11:07, f10=» «, f11=»00 «, f12=» 13 «, f13=06-02-85 09:11, f14=06-02-85 15:25, f15=»0174A «, f16=» 82 «, f17=» 4 «, f18=»15 «, f19=» 1016 «, f20=» 10159 «, f21=» «, f22=» «, f99=020010000110052710110380aa8a37040000000000000042033f01df}
0x4a100…4a200 (74, 0, 1) Sector 4a025200216241 ┆J R !bA J J J J I I I I H H H G G G G G F F D D C C C C C B B B * * * * * ) ) ) ) ( ( ( ( ' ' ' & & & & & & % % % $ $ $ # # # # " " " " ! ! ! ! et / / : ANV.TID ANSLAG Oprettet / / : : / / : : : : : ┆
0x4a200…4a300 (74, 0, 2) Sector 4a03a600216241 ┆J & !bA 1 CPS/SDS/028 850301 I/O CONTROL DETAILED DESIGN SPECIFICATION ISSUE 1 CAMPS =6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x4a300…4a400 (74, 0, 3) Sector 4a04ff00216241 ┆J !bA 1 4.1.6 Common Data N.A. 4.1.7 Interfaces 4.1.7.1 External Interfaces The external interfaces for IOC are the electrical interfaces for devices and lines, where IOC in fact ┆
0x4a400…4a500 (74, 0, 4) Sector 4a057e00216241 ┆J ~ !bAimplements the CAMPS external interface to devices/lines. Interface descriptions are: CAMPS ICDs ICD/004 through 8. =2#<! <6 M)(I:g=~ J /Mj'! "(=~ R*/!/=6jM (*(=~ R;/!/=6nM (*(=~ RM/!/=6iM (*(=~ R`/!/=6WM (*(=~ Rt/!/=6lM (*(=~ R ┆
0x4a500…4a600 (74, 0, 5) Sector 4a06ff00216241 ┆J !bA 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┆
0x4a600…4a700 (74, 0, 6) Sector 4a075d00216241 ┆J ] !bAnterfaces. d) Control Interfaces for defining control parameters within the IOC :^=~ Bl1{M40sI:^=~ J 1!"<6;!#<6 !&<6 ! "$<! <6 {M;(s! 9"c=! "(= Z=q#p!"<6 !&<6 ! "$<!#<6 ! <6 {M)(sC I! <6 ! "(= <q#p!"<6 !#<6 ! "$<!&<6$`i6 {M)(sM &M7 ┆
0x4a700…4a800 (74, 0, 7) Sector 4908ff00216241 ┆I !bA 1 4.1.7.2.1 IOS Interfaces The IOS interfaces are included here as background information. For coding purposes please refer to DAMOS I/O SYSTEM. 4.1.7.2.1.1 Mount Functional D┆
0x4a800…4a900 (74, 0, 8) Sector 4a09ff00216141 ┆J !aA 1 4.2.5.1.4 Supervisory Control Functions (4.0) Commands inserted by the Supervisor are received in the Collect Queue. a) QUEUE STATE REQUEST (4.1) The number of messages under┆
0x4a900…4aa00 (74, 0, 9) Sector 4a0aff00216141 ┆J !aA preparation is calculated and sent to the Supervisor Printer. b) CANCEL ALL PREP QUEUES (4.2) All messages under preparation is deleted and a command completion report is generated. c) CANCEL TERMINAL PREP QUEUE (4.3) All messages under p┆
0x4aa00…4ab00 (74, 0, 10) Sector 4a0bff00216141 ┆J !aAreparation for the specified terminal is deleted. A command completion report is generated. d) DELETE CIF (4.4) The specified CIF is deleted from the preparation files and an acknowledge is returned.. 4.2.5.1.5 Error Reporting (5.0) a) Que┆
0x4ab00…4ac00 (74, 0, 11) Sector 4a0cf700216141 ┆J w !aAue Error Reporting (5.1). Reports to SSC that an unexpected Queue element has been received. b) Internal Error Handling (5.2). Reports to SSC that an unexpected response has been received from SFCO or from monitor procedures called. Upon re┆
0x4ac00…4ad00 (74, 0, 12) Sector 4a0dff00216141 ┆J !aA 1 4.2.5.2 Software Structure Figure 4.2.5.2-1 shows a hierarchical overview of the software structure within UMAM. UMAM consists of one process performing the functions listed in se┆
0x4ad00…4ae00 (74, 0, 13) Sector 4a0e1500216141 ┆J !aAction 4.2.5.1. he File Directory. The relevant records are then transferred from the status file to a temporary CIF and sent to the requestor. the CIF is then sent to the requestor. b) Periodic Generated Status (2.2) A summary status is gene┆
0x4ae00…4af00 (74, 0, 14) Sector 4a0fa000216141 ┆J !aA 1 FIG. 4.2.5.2-1 UMAM Software Structure s/devices, then the status files will be cleared and the file directories will be reset. B z _┆
0x4af00…4b000 (74, 0, 15) Sector 4a00ff00216141 ┆J !aA 1 4.2.5.3 Data Flow and Control Logic 4.2.5.3.1 Data Flow The HIPO diagrams overleaf show the data flow of UMAM The dataflow between the files of UMAM is shown in figure 4.2.5.3┆
0x4b000…4b100 (75, 0, 0) Sector 4b01ff00216141 ┆K !aALECT AREA and OUT AREA. d) Generate Outgoing Message Status (2.4) An outgoing message status is generated and sent to the requestor. The status will be generated by sorting the EXPAND AREA, PREP AREA, COLLECT AREA and OUT AREA. e) Generate Re┆
0x4b100…4b200 (75, 0, 1) Sector 4b02ff00216141 ┆K !aAlease Message Status (2.5) A release message status is generated and sent to the requestor. The status will be generated by sorting the COLLECT AREA and RELEASE AREA. f) Generate Delivery Status (2.6) A delivery status is generated for the r┆
0x4b200…4b300 (75, 0, 2) Sector 4b037600216141 ┆K v !aAequired terminal/device and sent to the requestor. The status will be generated by sorting the DELIVER AREA. LED DESIGN SPECIFICATION CAMPS !/=6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x4b300…4b400 (75, 0, 3) Sector 4b04ff00216141 ┆K !aA 1 4.2.5.1.3 Message Access-Control (3.0) Deletion requests, edit requests and VDU page retrieval requests inserted by a user or operator are received in the Collect Queue. a) Use┆
0x4b400…4b500 (75, 0, 4) Sector 4b05ff00216141 ┆K !aAr Deletion Request (3.1) Depending on the message status, the deletion request is either sent to the supervisor or the referenced item is deleted from the Preparation File b) Edit Request (3.2) If the reference message is in a state where it┆
0x4b500…4b600 (75, 0, 5) Sector 4b06ff00216141 ┆K !aA is available for editing, then the message is sent to the requesting terminal. If the SEND command is rejected by QMON due to profile fault, then the message is deleted and a response message is returned. If the user does not have access to the mes┆
0x4b600…4b700 (75, 0, 6) Sector 4b07ff00216141 ┆K !aAsage, then a response message is returned to the requestor. c) VDU-Page Retrieval (3.3) If the referenced Display name can be found in the Display table, then a copy of the stored VDU-page will be sent to the requestor. d) VDU-Page Storage (3┆
0x4b700…4b800 (75, 0, 7) Sector 4a08c600216141 ┆J F !aA.4). If the referenced Display name can be found in the Display table, then the received CIF will be stored in the Display Database, otherwise the received CIF will be sent to the MDCO. L will identify the type of status. They are: - deliver┆
0x4b800…4b900 (75, 0, 8) Sector 4b09ff00216141 ┆K !aAy message status - release status - outgoing message status - service message status a) Status Changes (1.1) The referenced CIF is looked up in the PREP AREA or EXPAND AREA and status is changed. The CIF currently referenced from the status ┆
0x4b900…4ba00 (75, 0, 9) Sector 4b0aff00216141 ┆K !aArecord will be dismantled and the new CIF will be inserted. b) Status Updating (1.2) The received data buffer will be inserted as a part of the delivery status. c) Offline Append Changes (1.3) The CIF which has requested the offline append┆
0x4ba00…4bb00 (75, 0, 10) Sector 4b0b7100216141 ┆K q !aA is searched and status is changed to append complete. An Append Notification is returned to the drafter. M.:^=~ B}5I:g=~ J 5IC$3I > S C_* ┆
0x4bb00…4bc00 (75, 0, 11) Sector 4b0cff00216141 ┆K !aA 1 4.2.5.1.2 Generate Status (2.0) Two types of status are generated. They are: - user requested status - periodic generated status. a) User Requested Status (2.1) Upon re┆
0x4bc00…4bd00 (75, 0, 12) Sector 4b0dff00216141 ┆K !aAquest from a user or operator, a status is generated. There are four types of status which can be requested: - outgoing message status - message release status - delivery status - service message status. Information about the terminal is┆
0x4bd00…4be00 (75, 0, 13) Sector 4b0eff00216141 ┆K !aA looked up in the File Directory. The relevant records are then transferred from the status file to a temporary CIF and sent to the requestor. the CIF is then sent to the requestor. b) Periodic Generated Status (2.2) A summary status is gene┆
0x4be00…4bf00 (75, 0, 14) Sector 4b0ffa00216141 ┆K z !aArated each day at 00.00 hours and sent to the supervisor. The status is generated per terminal/device When status has been generated for all terminals/devices, then the status files will be cleared and the file directories will be reset. B z _┆
0x4bf00…4c000 (75, 0, 15) Sector 4b00ff00216141 ┆K !aA 1 c) Generate Service Message Status (2.3) A service message status is generated and sent to the requestor. The status will be generated by sorting the EXPAND AREA, PREP AREA, COL┆
0x4c000…4c100 (76, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(76,0, 1), len=0xff, h3=41216141}, f00=»2161A «, f01=»CPS/SDS/039 «, f02=»rt «, f03=»JBS «, f04=»fra 4.2.5 (USER VDU) «, f05=13-05-82 10:01, f06=» 11 «, f07=»57 «, f08=» 34882 «, f09=27-05-82 12:03, f10=» «, f11=»03 «, f12=» 268 «, f13=27-05-82 12:07, f14=27-05-82 13:40, f15=»0174A «, f16=» 98 «, f17=» 19 «, f18=»30 «, f19=» 1112 «, f20=» 41894 «, f21=» «, f22=» «, f99=910000000110052710110290aaca15050000000000000142034901df}
0x4c100…4c200 (76, 0, 1) Sector 4c026200216141 ┆L b !aAL L L L L K K K J J J J J J J J J I I I H H H H H G G G G F F F F E E E E D D D D D D C C C C B B B B A A A A A @ @ @ @ @ @ ? ? ? ? ? ? > > > > > = = = = = < < < < < ; ; ; ; : : : : 9 9 9 9 9 8 8 8 8 vn: Operat]r: Forfatter:r: Forfatter:r:┆
0x4c200…4c300 (76, 0, 2) Sector 4c039c00216141 ┆L !aA 1 CPS/SDS/039 820505 USER VDU DETAILED DESIGN SPECIFICATION CAMPS !/=6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x4c300…4c400 (76, 0, 3) Sector 4c04ff00216141 ┆L !aA 1 4.2.5 User Message Access Monitoring Subpackage The User Message Access Monitoring (UMAM) process has the responsibility for the status collecting and status generating. Furthermo┆
0x4c400…4c500 (76, 0, 4) Sector 4c05ff00216141 ┆L !aAre, UMAM performs the access control to the preparation database. 4.2.5.1 Functional Specification The following functions are included in this subpackage (refer figure 4.2.5.1-1): - collect status - generate status - message access control┆
0x4c500…4c600 (76, 0, 5) Sector 4c063c00216141 ┆L < !aA - supervisory control functions - error handling #<!"<6 !%<6 +6L!&<6 :$<~ JY0*.;:i=>Jf0C.1:.= Rp0C%0! <6 M1' R 0C 0! <6 M1' R 0C 0! <6 M1' Z 0CR0Mc&!.=6 ! <6 M1' R40C.1! <6 M1' RC0C.1! <6 M1' RR0C.1!$<5CQ0!$<6 !&<6 Mc&! "(=6 E '<M% ! "2<┆
0x4c600…4c700 (76, 0, 6) Sector 4c07a600216141 ┆L & !aA 1 FIG. 4.2.5.1-1 UMAM Functional Description "<6 !&<6 ! "$<!#<6 ! <6 {M)(sC I! <6 ! "(= <q#p!"<6 !#<6 ! "$<!&<6$`i6 {M)(sM &M7 ┆
0x4c700…4c800 (76, 0, 7) Sector 4b08ff00216141 ┆K !aA 1 4.2.5.1.1 Collect Status (1.0) Status update requests are received from VUP, SUP, MDC and MSO in the Collect Queue. The QEL will identify the type of status. They are: - deliver┆
0x4c800…4c900 (76, 0, 8) Sector 00000000000000 ┆ ┆
[…0x7…]
