OctetView
0x00000…00100 (0, 0, 0) Sector 00354130303335 ┆ 5A0035A ┆
0x00100…00200 (0, 0, 1) Sector 00000000000000 ┆ ┆
0x00200…00300 (0, 0, 2) Sector ff00feff80ffff ┆ ~ @ x |` | pp~ @ ┆
0x00300…00306 (0, 0, 3) WangDocument {d00=0x04, d01=0x74, d02=0x41, ptr=(19,0, 8), d05=0x00}
0x00306…0030c WangDocument {d00=0x04, d01=0x76, d02=0x41, ptr=( 5,0, 0), d05=0x00}
0x0030c…00312 WangDocument {d00=0x04, d01=0x78, d02=0x41, ptr=(38,0, 0), d05=0x00}
0x00312…00318 WangDocument {d00=0x04, d01=0x79, d02=0x41, ptr=(22,0, 0), d05=0x00}
0x00318…0031e WangDocument {d00=0x04, d01=0x84, d02=0x41, ptr=(38,0, 8), d05=0x00}
0x0031e…00324 WangDocument {d00=0x04, d01=0x86, d02=0x41, ptr=(39,0, 8), d05=0x00}
0x00324…0032a WangDocument {d00=0x04, d01=0x87, d02=0x41, ptr=(21,0, 0), d05=0x00}
0x0032a…00330 WangDocument {d00=0x04, d01=0x89, d02=0x41, ptr=(35,0, 8), d05=0x00}
0x00330…00336 WangDocument {d00=0x04, d01=0x90, d02=0x41, ptr=(36,0, 0), d05=0x00}
0x00336…0033c WangDocument {d00=0x04, d01=0x96, d02=0x41, ptr=(36,0, 8), d05=0x00}
0x0033c…00342 WangDocument {d00=0x05, d01=0x33, d02=0x41, ptr=(57,0, 0), d05=0x00}
0x00342…00348 WangDocument {d00=0x05, d01=0x60, d02=0x41, ptr=(52,0, 8), d05=0x00}
0x00348…00360 04 96 41 24 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ A$ ┆
0x00360…00380 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ ┆
[…0x3…]
0x003e0…00400 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 48 ┆ H┆
0x00400…00500 (0, 0, 4) Sector 00000000000000 ┆ ┆
0x00500…00600 (0, 0, 5) Sector 86312020202020 ┆ 1 8 7 Q? > 7 H | | d N ~<) 0uH &4'>( 1c5 & & ┆
0x00600…00700 (0, 0, 6) Sector 421c402600415b ┆B @& A[' X% % PO P ; 3A1? C g x g V WJ O 8 :<0 <3 g 0533A g d < {C < { ; 3 b - b bK ? R 8 : 9& t x <2<3<55181} ┆
0x00700…00800 (0, 0, 7) Sector 00000000000000 ┆ ┆
0x00800…00900 (0, 0, 8) Sector c3000000090014 ┆C ?C @ s!a " * 6 ~7B! #>J 2 C. 2t 2 2* e!> >aX2> Ioy gx ZX 4H -CO 4H}& -k k G~ + Bc Ig/9 Bu O 7Jn %Bm I! k/=+B .O>J y=B x<B k Ii`/;H=+B+ .O>J$ B$ Ik _/=+B? .Osy=B7 x<B7 I~ H~ I! 4Ise! ~6 a{Iue[ o& ~MK LQ a<Bx qC%@=2 q{I ┆
0x00900…00a00 (0, 0, 9) Sector c3000003090014 ┆C /C!@ !)@" {* 6 ~7B! #>B7 1 MO M? CW > 2 C< !2 6 [ 26 !5 6 !9 6 !: 6 & !} q y2 ! " !{ 6 M4 ! 6 I ┆
0x00a00…00b00 (0, 0, 10) Sector c3000003090014 ┆C /C!@ !)@" {* 6 ~7B! #>B7 1 MO M? CW > 2 C< !5 6 !n 6 !2 6 ! "n "l }2[ 26 2C >~S >wS M /> S > S ! 6 I ┆
0x00b00…00c00 (0, 0, 11) Sector c3000000090014 ┆C C s!a " * 6 ~7B! #>J 2 C. 2t 2 2* e!> >aX2> Ioy gx ZX 4H -CO 4H}& -k k G~ + Bc Ig/9 Bu O 7Jn %Bm I! k/=+B .O>J y=B x<B k Ii`/;H=+B+ .O>J$ B$ Ik _/=+B? .Osy=B7 x<B7 I~ H~ I! 4Ise! ~6 a{Iue[ o& ~MK LQ a<Bx qC% =2 q{I ┆
0x00c00…00d00 (0, 0, 12) Sector c300000f090000 ┆C C!@ !)@" {[ ~ B( >32 * 6 ~7B- #>J > 2 C< oy gx ZU 4H -BL I4H}& -k k G~ + B` I[ x Ck I: ~QJ ~HJ ~WJ f I> I> I> Iy7r > MJ yf ~ X~ HMJ yv O f H~ J@ CJ > MJ > CJ _ [ f BM o{v _ S Re }v o}S >}S I ┆
0x00d00…00e00 (0, 0, 13) Sector 00000000000000 ┆ ┆
0x00e00…00f00 (0, 0, 14) Sector c3000003090013 ┆C C!@ C " {* 6 ~7B! #>J3 > 2 C0 6 C oy gx ZU 4H -BL I4H}& -k k G~ + B` I DOC ID?1~/! @/w#<B > s gMA g[ 7J fpJz > #B !r wM^ M^ !i " 6 ~7B< #~7Bz +6 ~7BJ :m 2 :n 2 C f O fp1+wI ┆
0x00f00…01000 (0, 0, 15) Sector 2f000000000000 ┆/ Z.0 aeiouaeiouaeiAOU '& S=W8,24 < : ( ]$ "`!7 -#% + 9'1 36 ) ; 5_ *Y[ LRBEI?@UHFSMGPJ>TXODKVNACQ\ e^c \\\ . ] k_WUwU]uwU _~f `h```X`h X``(``hhXX``h(`h`X @"n┆
0x01000…01100 (1, 0, 0) WangDocumentBody
[…0x6…]
0x01700…01800 (1, 0, 7) Sector ec3021e6303600 ┆l0!f06 #61> !p0 ,O> R5 -~,FV Ox^ -q#w.fN,F! "f0C *p0+k*f0 k!h0N,F.0q#py x ./~V B^ MU Ca M !&06@*@0~#F!h0w#p *@0 ~V B+ *@0 ~O> R+ !E0~F O *d0 k!|0N,Fy x .E4!|0N,F.(q#p/I!+06 > IM V Bg *@0 ~V Bg *@0 ~O> Rg > I/I!l06 #6 .+6 .G6 .f6 #61┆
0x01800…01900 (1, 0, 8) WangDocumentBody
[…0x8…]
0x02100…02200 (2, 0, 1) Sector 00002400047641 ┆ $ vAIGN command was issued last. phanumeric, and whether the parameter is mandatory or optional. In fig. 4.4.2-1 the symbols used in VDU layout formats are shown and in fig. 4.4.2-3 an example of a screen lay-out is depicted. ┆
0x02200…02300 (2, 0, 2) Sector 5f554e52454144 ┆_UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD_┆
0x02300…02400 (2, 0, 3) Sector 0204ff00000220 ┆ 1 ^ Y^ @^ J^ ┆
0x02400…02500 (2, 0, 4) Sector 0205ff00000220 ┆ a 1980-00-00 000/000 to: shnmo division att.: mr. paul f. shey, contracting officer cc.: lt. col. manfred stoltz, camps program manager fm: christian rovsing a/s, denmark gert jensen our ref: cps/000/tlx/0000┆
0x02500…02600 (2, 0, 5) Sector 0206ff00000220 ┆ subject: 1 ----------------------------------------------------------------- b SHAPE Purchasing and Contracting Office Communications Implementation Branch B-7010 SHAPE Belgium Att.: Mr. Paul F. Shey, SHAPE Contracting Office┆
0x02600…02700 (2, 0, 6) Sector 0207ff00000220 ┆ r GJ/000/LET/0000 1980-00-00 cc.: Lt. Col. Manfred Stoltz, CAMPS Program Manager Gentlemen, Subject: 1 c H ┆
0x02700…02800 (2, 0, 7) Sector 01088100000220 ┆ 000/000/000 000/000000 # 1 1 CAMPS 1 d Kind regards, CHRISTIAN ROVSING A/S Gert Jensen : #wI>K!8=>R 2!8=6 #4 E*8=k L<M% :8=F 28=I!#<:"<>R<2> I E*#<& "< DM L<M% :#<F 2#<> I:g= Ro2M/2 Rl2> IC13!?=4~~ B|2> I:A=!┆
0x02800…02900 (2, 0, 8) WangDocumentBody
[…0x27…]
0x05000…05100 (5, 0, 0) WangDocumentHead {hdr=WangSectHead {next=( 5,0, 1), len=0xff, h3=41047641}, f00=»0476A «, f01=»CPS/SDS/001 «, f02=»vhn «, f03=»MSN «, f04=»Kap. 4.4 «, f05=07-01-81 12:17, f06=» 2 «, f07=»50 «, f08=» 9542 «, f09=08-01-81 14:42, f10=» «, f11=»14 «, f12=» 253 «, f13=08-01-81 15:35, f14=20-02-81 12:13, f15=»0035A «, f16=» 13 «, f17=» 3 «, f18=»04 «, f19=» 164 «, f20=» 9795 «, f21=» «, f22=» «, f99=020010000110056610a10a80aaca15050000000000000038033100df}
0x05100…05200 (5, 0, 1) WangDocumentBody
[…0x8…]
0x05a00…05b00 (5, 0, 10) Sector 050bff00036441 ┆ dA 26 is returned. If the entry in the Final/Draft field is invalid, error code 1 is returned. If the SIC is invalid then message 8 is returned. If the Item reference Identity is valid then error 1 is returned. If the Item reference identity l┆
0x05b00…05c00 (5, 0, 11) Sector 050cff00036441 ┆ dAeads to a search in the currently stored data base, then response message 28 is returned to assume the user that retrieval is in progress. On retrieval completion the catalogue display or the retrieved item will be delivered to the terminals at FL┆
0x05c00…05d00 (5, 0, 12) Sector 050d1700036441 ┆ dAASH precendence. ansmitted or a comment received at this terminal. e) A release notification sent from or to this terminal. On entering the appropriate command and pressing the RETURN key the user is presented with a request for entry of data re┆
0x05d00…05e00 (5, 0, 13) Sector 050e8c00036441 ┆ dA 1 SCREEN LAYOUT H-2 s consisting of an item type, time stamp and an item reference identity - uses a command. - General references co┆
0x05e00…05f00 (5, 0, 14) Sector 050fff00036441 ┆ dA 1 3.11.3 Incoming Message Except where stated the description are as for outgoing messages (3.11.2). 3.11.3.1 DTG (Mandatory) This is the DTG contained in format line 5 of the ┆
0x05f00…06000 (5, 0, 15) Sector 0500ff00036441 ┆ dAincoming message. 3.11.3.2 DTG Window (Optional) 3.11.3.3 Subject Indicator Code (Mandatory) 3.11.3.4 Validation Validation results are as for the same fields in the outgoing message format (3.11.2). 3.11.3.5 Security Only incoming m┆
0x06000…06100 (6, 0, 0) WangDocumentBody
[…0xc…]
0x06d00…06e00 (6, 0, 13) Sector 060eff00047941 ┆ yAciated AG is not existing. c) PLA table - A PLA must only be deleted if it is not referenced from AIG table or from PLA # table. - Only RIs existing in RI table must be referenced in PLA table. d) SIC table - Referenced SCDs must exist ┆
0x06e00…06f00 (6, 0, 14) Sector 060fbf00047941 ┆ ? yAin SCD table. e) SCD table - Referenced TDs must be defined. - Changing an TD must require changes in SIC table. f) Terminal profiles - Referenced operators must exist. k unlock procedures, reorganization and consistency checks. Upda┆
0x06f00…07000 (6, 0, 15) Sector 0600ff00047941 ┆ yA 1 5.14.1.3.2 Hardware Control of Subsystem N/A. 5.14.1.3.3 Error Control Mechanisms TMP checks parameters for syntax and consistancy. 5.14.1.4 Characteristics 5.14.1.4.1 ┆
0x07000…07100 (7, 0, 0) WangDocumentBody
[…0xd…]
0x07e00…07f00 (7, 0, 14) Sector 070f6600047841 ┆ f xAertain changes may require the distribution list associated with the message to be adjusted. elivered to the appropriate device and terminal queues. Messages received from the analysis process are dealt with according to type: depend on both the┆
0x07f00…08000 (7, 0, 15) Sector 0700ff00047841 ┆ xA 1 4.2.4.13 Final Situation As a result of the procesisng described in this section the following effects will also have been achieved: a) Storage An incoming message stored in ┆
0x08000…08100 (8, 0, 0) WangDocumentBody
[…0x2…]
0x08300…08400 (8, 0, 3) Sector 0804ff00047841 ┆ xAd for the MDCO (and presented without text). Possible distribution destinations for such a message could be SCARS/CCIS/Paper-Tape punch. c) The queue for the MDCO will contain, in addition, elements for each message/queue combination rejected beca┆
0x08400…08500 (8, 0, 4) Sector 0805ff00047841 ┆ xAuse of classification mis-match or terminal/user status not suitable. This rejection may occur upon queuing for a device or subsequently if the status changes before the message is output or for a FLASH time-out. In these cases the information that ┆
0x08500…08600 (8, 0, 5) Sector 08066400047841 ┆ d xAindicates which terminal SCD is involved is stored in the queue element rather that the MCB. SCARS X X 1 ┆
0x08600…08700 (8, 0, 6) Sector 08078900047841 ┆ xA 1 Figure 4.2.4-5 alyzed to obtain the required outgoing circuits. The precedence and classification also need to be deduced. Internal d┆
0x08700…08800 (8, 0, 7) Sector 0708ff00047841 ┆ xA 1 4.2.4.12 MDCO Actions The TEP process (or processes) handling the queue of elements for MDCO positions, present the corresponding messages and expect responses according to the re┆
0x08800…08900 (8, 0, 8) WangDocumentBody
[…0xaf…]
0x13800…13900 (19, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(19,0, 9), len=0xff, h3=41047441}, f00=»0474A «, f01=»OPTO MODEMS AT CR-CARD «, f02=»vhn «, f03=»BHB «, f04=»M< IKKE SLETTES «, f05=06-01-81 16:24, f06=» «, f07=»26 «, f08=» 2844 «, f09=03-07-85 10:52, f10=» «, f11=»00 «, f12=» 4 «, f13=07-01-81 09:12, f14=03-07-85 10:52, f15=»0035A «, f16=» 2 «, f17=» «, f18=»33 «, f19=» 48 «, f20=» 2936 «, f21=» «, f22=» «, f99=020010000110056610a10a80aaca15050000000000000038031000df}
0x13900…13a00 (19, 0, 9) WangDocumentBody
[…0x16…]
0x15000…15100 (21, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(21,0, 1), len=0xff, h3=41048741}, f00=»0487A «, f01=»Minutes of Meeting No. 4 «, f02=»vhn «, f03=»FE «, f04=»M> ikke slettes «, f05=09-01-81 13:45, f06=» «, f07=»48 «, f08=» 3321 «, f09=29-01-81 10:59, f10=» «, f11=»00 «, f12=» 6 «, f13=29-01-81 10:59, f14=20-02-81 12:13, f15=»0035A «, f16=» 5 «, f17=» 1 «, f18=»07 «, f19=» 116 «, f20=» 3904 «, f21=» «, f22=» «, f99=100020000210056610a10a01aaca15050000000000000038032200df}
0x15100…15200 (21, 0, 1) WangDocumentBody
[…0xe…]
0x16000…16100 (22, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(22,0, 1), len=0xff, h3=41047941}, f00=»0479A «, f01=»CPS/SDS/001 system design «, f02=»am] «, f03=»BMN «, f04=»kap. 5.14 «, f05=08-01-81 10:59, f06=» 3 «, f07=»30 «, f08=» 11869 «, f09=23-01-81 15:03, f10=» «, f11=»04 «, f12=» 187 «, f13=23-01-81 15:51, f14=20-02-81 14:22, f15=»0035A «, f16=» 15 «, f17=» 4 «, f18=»15 «, f19=» 184 «, f20=» 12572 «, f21=» «, f22=» «, f99=110010000110056610a10a80aaca15050000000000000038033d00df}
0x16100…16200 (22, 0, 1) WangDocumentBody
[…0x14…]
0x17600…17700 (23, 0, 6) Sector 1707ff00048441 ┆ A2,6 mm ( 10 V crate) Width: 17,1 mm ( 1 Module) Depth: 305 mm The Floppy Disk Controller is a front crate mounted module. Power Consumption for the Floppy Disk Controller + 5V: TBD +12V: TBD -12V: TBD Mechanical Specifi┆
0x17700…17800 (23, 0, 7) Sector 1608ff00048441 ┆ Acation for the Adapter Height: 412,6 mm ( 10 V crate) Width: 17,1 mm ( 1 Module) Depth: 160 mm Power Consumption for the Adapter Not applicable. Electrical Specifications for the Floppy Disk Controller/Adapter Flatcable Bus ┆
0x17800…17900 (23, 0, 8) WangDocumentBody
[…0xbf…]
0x23800…23900 (35, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(35,0, 9), len=0xff, h3=41048941}, f00=»0489A «, f01=»CAMPS SYS DES SPEC «, f02=»sdv «, f03=»KNN «, f04=»CPS/SDS/001, 2.2 «, f05=09-01-81 14:34, f06=» «, f07=»16 «, f08=» 1078 «, f09=12-01-81 09:00, f10=» «, f11=»01 «, f12=» 5 «, f13=12-01-81 09:02, f14=13-01-81 16:50, f15=»0035A «, f16=» 1 «, f17=» «, f18=»18 «, f19=» 16 «, f20=» 1108 «, f21=» «, f22=» «, f99=020010000110056610a10a80aaca15050000000000000038030400df}
0x23900…23a00 (35, 0, 9) WangDocumentBody
[…0x2…]
0x23c00…23d00 (35, 0, 12) Sector 230d4a00048041 ┆# J A the MIA issues the IA signal and terminates the interrupt procedureed into its RAR during the set up, onto the Channel Unit I/O Bus. The data phase is similar to that of a single transfer with the exception that the data path now goes through the┆
0x23d00…23e00 (35, 0, 13) Sector 0000f200048041 ┆ r A. MIA Controlled Interrupt Requests The polling controller transmits automatically the interrupt request word. The response from the CU may either be a Module Address (MA) or Status Word (SW) depending on the MSB of the response. the last data┆
0x23e00…23f00 (35, 0, 14) Sector 0d2d2c3b0d1a21 ┆ -,; ! $ 0 . $ $-+- $;'- $; - $' - $ -- 2 2 2 2 2! 2+ 2 2 2; 0 . 1 2' 0 . 1 2 0 . 1 2 0 . 1 2! 0 . 1 2+ 0 . 1 2 0 . 1 2 ┆
0x23f00…24000 (35, 0, 15) Sector 09b0092e1409b1 ┆ 0 . 1 6 $ 2; ;--- 8'--- 2' ;--- 8'--- $ --; --- 6 $ 2; ;;-- 8;!-- 2' ;;-- 8;!-- $ --; --- 6 $ 2; ;;-- 8;!-- 2' ;;-- 8;!-- $ --; --- ! + @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ ┆
0x24000…24100 (36, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(36,0, 1), len=0xff, h3=41049041}, f00=»0490A «, f01=»CAMPS SYS DES SPEC «, f02=»sdv «, f03=»KNN «, f04=»CPS/SDS/001, 2.6 «, f05=09-01-81 14:51, f06=» «, f07=»04 «, f08=» 428 «, f09=12-01-81 08:56, f10=» «, f11=»04 «, f12=» 6 «, f13=12-01-81 09:01, f14=13-01-81 16:50, f15=»0035A «, f16=» 1 «, f17=» «, f18=»08 «, f19=» 8 «, f20=» 434 «, f21=» «, f22=» «, f99=020010000110056610a10a80aaca15050000000000000038030400df}
0x24100…24200 (36, 0, 1) WangDocumentBody
[…0x2…]
0x24400…24500 (36, 0, 4) Sector 2405ff00048041 ┆$ Aflag simultaneously with loading the Block Transfer Error (BTE) register. The data received from the CU may contain an error message. In this case, the MIA stops the block transfer, loads the BTE register with the error message plus an error stat┆
0x24500…24600 (36, 0, 5) Sector 2406ff00048041 ┆$ Aus and sets the BTH signal high. If the CU does not response at all, the MIA issues the DA signal, sets the BTH signal and loads the BTE with an error status. During a Reduced transfer, the MAP can issue a single transfer. The MAP issues only t┆
0x24600…24700 (36, 0, 6) Sector 2407ff00048041 ┆$ Ahe first address cycle to the MIA and then waits for the BTO flag to be reset. After that, the rest of the single transfer may be issued as used. When the single transfer has ended, the reduced transfer continues setting the BTO flag. In case of┆
0x24700…24800 (36, 0, 7) Sector 2308ff00048041 ┆# A an erroneous transfer on the Data Channel, the MIA stops the block transfer by setting the BTH signal high and clearing the BTO signal. To ensure that the FIFO is empty before a retransmission of the block the MAP must issue a Reset FIFO (RFI) si┆
0x24800…24900 (36, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(36,0, 9), len=0xff, h3=41049641}, f00=»0496A «, f01=»CPS/SDS/001 «, f02=»vhn «, f03=»KNN «, f04=»KAP. 1 + 1.1 «, f05=13-01-81 09:21, f06=» «, f07=»07 «, f08=» 988 «, f09=28-01-81 16:23, f10=» «, f11=»01 «, f12=» 7 «, f13=22-01-81 10:42, f14=20-02-81 11:17, f15=»0035A «, f16=» 1 «, f17=» «, f18=»12 «, f19=» 16 «, f20=» 1028 «, f21=» «, f22=» «, f99=020010000110056610a10a80aaca15050000000000000038030700df}
0x24900…24a00 (36, 0, 9) WangDocumentBody
[…0x5…]
0x24f00…25000 (36, 0, 15) Sector 2400ff00048041 ┆$ Aore the Terminal Count reaches zero, the block transfer becomes pending and does not continue before the FIFO contains at least 2 bytes. This situation is signalled to the MAP by resetting the BTO flag and setting the FMY signal. The FIFO may be l┆
0x25000…25100 (37, 0, 0) WangDocumentBody
[…0xf…]
0x26000…26100 (38, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(38,0, 1), len=0xff, h3=41047841}, f00=»0478A «, f01=»CPS/SDS/001 «, f02=»vhn «, f03=»RG «, f04=»Kap. 4.2 «, f05=07-01-81 15:32, f06=» 7 «, f07=»01 «, f08=» 30756 «, f09=28-01-81 13:24, f10=» «, f11=»00 «, f12=» 5 «, f13=16-01-81 12:41, f14=20-02-81 12:13, f15=»0035A «, f16=» 29 «, f17=» 7 «, f18=»55 «, f19=» 464 «, f20=» 33319 «, f21=» «, f22=» «, f99=100010000110056610a10a80aaca15050000000000000038039300df}
0x26100…26200 (38, 0, 1) WangDocumentBody
[…0x6…]
0x26800…26900 (38, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(38,0, 9), len=0xff, h3=41048441}, f00=»0484A «, f01=»CAMPS SYS DES SPEC «, f02=»sdv «, f03=»SRA «, f04=»CPS/SDS/001, 5.1.5 «, f05=09-01-81 11:20, f06=» 6 «, f07=»48 «, f08=» 39604 «, f09=15-01-81 09:40, f10=» «, f11=»20 «, f12=» 213 «, f13=15-01-81 10:13, f14=20-02-81 14:22, f15=»0035A «, f16=» 39 «, f17=» 8 «, f18=»55 «, f19=» 652 «, f20=» 41084 «, f21=» «, f22=» 0 «, f99=330010000110056610a10a80aaca1505000000000000003803b600df}
0x26900…26a00 (38, 0, 9) WangDocumentBody
[…0xe…]
0x27800…27900 (39, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(39,0, 9), len=0xff, h3=41048641}, f00=»0486A «, f01=»CPS/SDS/001 system design «, f02=»am] «, f03=»BHJ «, f04=»kap. 5.4 «, f05=09-01-81 13:00, f06=» 2 «, f07=»35 «, f08=» 11422 «, f09=14-01-81 18:29, f10=» «, f11=»02 «, f12=» 13 «, f13=15-01-81 08:14, f14=20-02-81 14:22, f15=»0035A «, f16=» 14 «, f17=» 3 «, f18=»54 «, f19=» 184 «, f20=» 12841 «, f21=» «, f22=» «, f99=310010000110056610a10a80aaca15050000000000000038033600df}
0x27900…27a00 (39, 0, 9) WangDocumentBody
[…0x6…]
0x28000…28100 (40, 0, 0) Sector 2801ff00056041 ┆( `A During validation of user entries tables are accessed by TEP. 5.13.2.2.7.2 Printers - Terminal Manager Increments document control no. 5.13.2.2.7.3 PTR - Terminal Manager Increments release serial no. 5.13.2.2.7.4 PTP - Terminal Manag┆
0x28100…28200 (40, 0, 1) Sector 00007300056041 ┆ s `Aer Increments document control no. 5.13.2.2.7.5 OCR - Terminal Manager Increments release serial no. her covers the following special areas: a) Error Reporting. Errors that cannot be handled by the Terminal Package are reported to SS&C ┆
0x28200…28300 (40, 0, 2) Sector 2803ff00047241 ┆( rA 1 5.13.2.2.3.4 User Functions When a user issues a retrieval or message merge request, the Terminal package inserts the request in the SAR package retrieval request queue. When th┆
0x28300…28400 (40, 0, 3) Sector 2804ff00047241 ┆( rAe SAR Package has processed the request, it inserts the result of it in the Terminal Package delivery queue. 5.13.2.2.4 Log and Accountability Package The Log and Accountability Package collects log records reported from various package and sto┆
0x28400…28500 (40, 0, 4) Sector 2805ff00047241 ┆( rAres them on disk. Upon request from the Supervisor trace of log is performed by the Log and Accountability Package. The Log and Accountability delivers periodically a report to the terminal position containing log records for each transaction wh┆
0x28500…28600 (40, 0, 5) Sector 2806ff00047241 ┆( rAich have been executed at that terminal in the given period. 5.13.2.2.4.1 Supervisor Function Log records of Supervisor activities (command utilization records) are communicated to the Log and Accountability package through CAMPS System Functio┆
0x28600…28700 (40, 0, 6) Sector 2807ff00047241 ┆( rAns. The Log and Accountability Package queues log records to the Terminal Package (Q1) for print-out at the supervisor's terminal as they arrive, if this has been requested by the supervisor. The supervisor may request various traces of log reco┆
0x28700…28800 (40, 0, 7) Sector 2708ff00047241 ┆' rArds. The Terminal Package queues such requests in the command function queue of the Log and Accountability Package. When the Log and Accountability Package has traced the requested log records, they are placed in the Terminal Package queue for tr┆
0x28800…28900 (40, 0, 8) Sector 2809b200056041 ┆( 2 `Ao special interface. f) User Function No special interface. 5.13.2.2.6.2 Stand Alone Devices - Terminal Managers No special interfaces to the SS&C Package exist. . Refer fig. 5.13.2.2.5-2. og and Accountability Package through CAMPS Sys┆
0x28900…28a00 (40, 0, 9) Sector 280a8a00056041 ┆( `A 1 Fig. 5.13.2.2.6-1 5-1 The supervisor may request various traces of log records. The Terminal Package queues such requests in the ┆
0x28a00…28b00 (40, 0, 10) Sector 280bff00056041 ┆( `A 1 5.13.2.2.7 Table Management Package (TMP) TMP provides access to tables, global number series and system parameters and validates update-requests to these as well as ensuring cont┆
0x28b00…28c00 (40, 0, 11) Sector 280cff00056041 ┆( `Ainuity and integrity in case of system failures. Back-up/reload facilities are also supplied. The tables accessed by TEP include: AIG PLA RI CH SDL SCD SIC Command Control Tables ROUT MDCO Tables Term. prof. (read via TMP, update via SS&C┆
0x28c00…28d00 (40, 0, 12) Sector 280dff00056041 ┆( `A) User. prof. (read via TMP, update via SS&C) Global no. series: Document control no. Transaction serial no. Release serial no. System Parameters: TBD. 5.13.2.2.7.1 VDU - Terminal Manager a) Supervisor Function In addition to the┆
0x28d00…28e00 (40, 0, 13) Sector 280ee100056041 ┆( a `A supervisor facilities for read and update implemented as commands, the Terminal Package reads the relevant tables, numbers, and system parameters required for its functions. b) MDCO Function No interface to TMP. itializes an instance of the T┆
0x28e00…28f00 (40, 0, 14) Sector 280f8f00056041 ┆( `A 1 Figure 5.13.2.2.7-1 f Terminal Manager, activated is device dependent. 5.13.2.2.6.1 VDU - Terminal Manager For VDUs, the initia┆
0x28f00…29000 (40, 0, 15) Sector 2800ff00056041 ┆( `A 1 c) MSO Function No interface to TMP. d) User Functions Following the read TMP increments the transaction serial no. After release TMP increments the release serial no. ┆
0x29000…29100 (41, 0, 0) Sector 2901ff00056041 ┆) `A 1 The Terminal Package is initiated with information about the access rights determined by the SS&C Package and include: - CAMPS functions which may be accessed by the user from th┆
0x29100…29200 (41, 0, 1) Sector 2902ff00056041 ┆) `Ae given terminal position. - System tables which may be accessed. The interface to the SS&C software further covers the following special areas: a) Error Reporting. Errors that cannot be handled by the Terminal Package are reported to SS&C ┆
0x29200…29300 (41, 0, 2) Sector 2903ff00056041 ┆) `Aand appropriate action taken here. Control will be returned from SS&C in the cases where continued operation is possible, otherwise switchover or restart will be performed. b) Ordered close-down. When a close-down command is received from SS&C ┆
0x29300…29400 (41, 0, 3) Sector 2904ff00056041 ┆) `Athe following actions are taken: 1) Warning sent to all manned terminals specifying when close-down will take place. 2) Commands are ignored when current activities are completed and all flash messages have been displayed. 3) Suspension of┆
0x29400…29500 (41, 0, 4) Sector 2905ff00056041 ┆) `A transactions still active at terminals when warning time has elapsed. 4) Notify SS&C that close-down actions are complete. c) Supervisor Function The supervisor may issue some commands to the SS&C Package, such as integrity check, change pr┆
0x29500…29600 (41, 0, 5) Sector 29067d00056041 ┆) } `Aofile (external channel, terminal, user). Such commands are by TEP inserted in the command queue of the SS&C Package. d to the Statistics Package. When the Statistics Package has retrieved the commanded statistics, it queues it in the TEP statis┆
0x29600…29700 (41, 0, 6) Sector 2907ff00056041 ┆) `A 1 When the SS&C Package has executed a command, it places a command completion code in TEP queue assigned to this purpose, so TEP can generate a command completion report. Report┆
0x29700…29800 (41, 0, 7) Sector 2808ff00056041 ┆( `As for the supervisor generated by the SS&C Package (e.g. system integrity check unsuccessfull) are placed in TEP queue for supervisor reports. Refer fig. 5.13.2.2.6-1. d) MDCO Function No special interface. e) Message Service Function N┆
0x29800…29900 (41, 0, 8) Sector 2909d000056041 ┆) P `APackage collects statistics information on user formats and communicates such statistics records to the Statistics Package by invoking the appropriate CAMPS system function. Refer fig. 5.13.2.2.5-2. og and Accountability Package through CAMPS Sys┆
0x29900…29a00 (41, 0, 9) Sector 290a8f00056041 ┆) `A 1 Figure 5.13.2.2.5-1 The supervisor may request various traces of log records. The Terminal Package queues such requests in the ┆
0x29a00…29b00 (41, 0, 10) Sector 290b9000056041 ┆) `A 1 Figure 5.13.2.2.5-2 are placed in the Supervisor's queue for traced log. Then the Log and Accountability package places a command┆
0x29b00…29c00 (41, 0, 11) Sector 290cff00056041 ┆) `A 1 5.13.2.2.5.2 Printer - Terminal Manager The Terminal Manager collects statistics information on formats distributed on SCDs to the printer and communicates such statistics records┆
0x29c00…29d00 (41, 0, 12) Sector 290dff00056041 ┆) `A to the Statistics Package by invoking the appropriate CAMPS System Function. 5.13.2.2.5.3 PTR - Terminal Manager No interface to Statistics. 5.13.2.2.5.4 PTP - Terminal Manager No interface to Statistics. 5.13.2.2.5.5 OCR - Terminal Ma┆
0x29d00…29e00 (41, 0, 13) Sector 290eff00056041 ┆) `Anager No interface to Statistics. 5.13.2.2.6 SS&C System The SS&C software monitors and controls the CAMPS system, hardware as well as software. The SS&C software acts as operating system. The SS&C software initializes an instance of the T┆
0x29e00…29f00 (41, 0, 14) Sector 290fff00056041 ┆) `Aerminal Package (Terminal Manager) each time the state of a terminal changes from Unmanned to Manned/Attended. The instance, i.e. type of Terminal Manager, activated is device dependent. 5.13.2.2.6.1 VDU - Terminal Manager For VDUs, the initia┆
0x29f00…2a000 (41, 0, 15) Sector 2900a000056041 ┆) `Alization procedure is similar for all CAMPS functions, except that the supervisor function is not handed over before the ASSIGN command has been issued. r - Terminal Manager Log records of information distributed by SCD to a printer are communica┆
0x2a000…2a100 (42, 0, 0) Sector 2a01ff00056041 ┆* `Ated by the Terminal Package to the Log and Accountability Package through CAMPS System Functions. 5.13.2.2.4.3 PTR - Terminal Manager No interface to log and accountability. 5.13.2.2.4.4 PTP - Terminal Manager No interface to log and accou┆
0x2a100…2a200 (42, 0, 1) Sector 2a026200056041 ┆* b `Antability. 5.13.2.2.4.5 OCR - Terminal Manager No interface to log and accountability. result of it in the Terminal Package delivery queue. When a user Terminal Manager detects a transaction (An initial version of a message, a message relea┆
0x2a200…2a300 (42, 0, 2) Sector 2a039000056041 ┆* `A 1 Figure 5.13.2.2.4-2 SAR. Refer fig. 5.13.2.2.3-3. 5.13.2.2.3.2 Printer - Terminal Manager No interface to SAR. 5.13.2.2┆
0x2a300…2a400 (42, 0, 3) Sector 2a04ff00056041 ┆* `A 1 5.13.2.2.5 Statistics (STP) The Statistics Package collects statistical information from many packages and makes statistics based on the collected information. The Statistics Pac┆
0x2a400…2a500 (42, 0, 4) Sector 2a05ff00056041 ┆* `Akage extracts on request from the supervisor specified statistics and queues them in the supervisor's statistics print queue. 5.13.2.2.5.1 VDU - Terminal Manager a) Supervisor Function No statistics information flows from the Terminal Packag┆
0x2a500…2a600 (42, 0, 5) Sector 2a06ff00056041 ┆* `Ae to the Statistics Package. The Terminal Package requests statistics from the Statistics Package by giving a command to the Statistics Package. When the Statistics Package has retrieved the commanded statistics, it queues it in the TEP statis┆
0x2a600…2a700 (42, 0, 6) Sector 2a07ff00056041 ┆* `Atics print queue. Then the Statistics queues a command completion code in the supervisor queue dedicated to this purpose so TEP can generate a command completion report. Statistics information generated periodically by the Statistics Package is ┆
0x2a700…2a800 (42, 0, 7) Sector 2908ff00056041 ┆) `Aqueued in the queue for statistics print as well. Refer fig. 5.13.2.2.5-1. b) Message Distribution Control Function No interface to Statistics. c) Message Service Function No interface to Statistics. d) User Functions The Terminal ┆
0x2a800…2a900 (42, 0, 8) Sector 2a09ff00056041 ┆* `Aervisor trace of log is performed by the Log and Accountability Package. 5.13.2.2.4.1 VDU - Terminal Manager a) Supervisor Function Log records of Supervisor activities are communicated to the Log and Accountability Package through CAMPS Sys┆
0x2a900…2aa00 (42, 0, 9) Sector 2a0aff00056041 ┆* `Atem Functions. The Log and Accountability Package queues log records to TEP for print-out at the supervisor's terminal as they arrive. The supervisor may request various traces of log records. The Terminal Package queues such requests in the ┆
0x2aa00…2ab00 (42, 0, 10) Sector 2a0bff00056041 ┆* `Arequest queue of the Log and Accountability Package. When the Log and Accountability Package has traced the requested log records, they are placed in the Supervisor's queue for traced log. Then the Log and Accountability package places a command┆
0x2ab00…2ac00 (42, 0, 11) Sector 2a0cf400056041 ┆* t `A completion code in the Terminal Package queue assigned to this purpose, so that TEP can generate a command completion report. Warning reports are placed in the warning queue by Log and Accountability Package. Refer fig. 5.13.2.2.4-1. n acknowled┆
0x2ac00…2ad00 (42, 0, 12) Sector 2a0d8e00056041 ┆* `A 1 Fig. 15.13.2.2.4-1 ctivities commanded or acknowledged by the supervisor are communicated to the SAR by the Terminal Manager. Rep┆
0x2ad00…2ae00 (42, 0, 13) Sector 2a0eff00056041 ┆* `A 1 b) Message Distribution Control Function Log records of MDCO activities are communicated to the Log and Accountability Package through CAMPS System Functions. Refer fig. 5.13┆
0x2ae00…2af00 (42, 0, 14) Sector 2a0fff00056041 ┆* `A.2.2.4-2. c) Message Service Function Log records of MSO activities are communicated to the Log and Accountability Package through CAMPS System Functions. Refer fig. 5.13.2.2.4-2. d) User Functions Log records of user activities are com┆
0x2af00…2b000 (42, 0, 15) Sector 2a00ff00056041 ┆* `Amunicated by the Terminal Package to the Log and Accountability Package through CAMPS System Functions. Refer fig. 5.13.2.2.4-2. 5.13.2.2.4.2 Printer - Terminal Manager Log records of information distributed by SCD to a printer are communica┆
0x2b000…2b100 (43, 0, 0) Sector 2b01ff00056041 ┆+ `A result of the processing of the request in the MDCO delivery queue. Refer fig. 5.13.2.2.3-2. c) Message Service Function No interface to SAR. d) User Functions When a user issues a retrieval or message append request, TEP inserts the r┆
0x2b100…2b200 (43, 0, 1) Sector 2b02ff00056041 ┆+ `Aequest in SAR retrieval request queue. When SAR has processed the request, it inserts the result of it in the Terminal Package delivery queue. When a user Terminal Manager detects a transaction (An initial version of a message, a message relea┆
0x2b200…2b300 (43, 0, 2) Sector 2b03ff00056041 ┆+ `Ased, a comment transmitted) which results in information being stored, the Terminal Manager reports the retrieval keys and information to SAR. Refer fig. 5.13.2.2.3-3. 5.13.2.2.3.2 Printer - Terminal Manager No interface to SAR. 5.13.2.2┆
0x2b300…2b400 (43, 0, 3) Sector 2b04da00056041 ┆+ Z `A.3.3 PTR - Terminal Manager Messages received from the PTR are automatically released by the Terminal Manager. The Terminal Manager reports the retrieval key of the message automatically released to SAR. ackage Control TEP is as a whole co┆
0x2b400…2b500 (43, 0, 4) Sector 2b059000056041 ┆+ `A 1 Figure 5.13.2.2.3-2 ling. 5.13.2.2.1.3 PTR - Terminal Manager ACP127 messages received by the Terminal Manager from a PTR are ┆
0x2b500…2b600 (43, 0, 5) Sector 2b069000056041 ┆+ `A 1 Figure 5.13.2.2.3-3 ues information addressed, either by SCD or device designator, to the printer position in the FLASH, IMMEDIATE,┆
0x2b600…2b700 (43, 0, 6) Sector 2b07ff00056041 ┆+ `A 1 5.13.2.2.3.4 PTP - Terminal Manager No interface to SAR. 5.13.2.2.3.5 OCR - Terminal Manager Messages received from the OCR are released automatically by the Terminal Manager┆
0x2b700…2b800 (43, 0, 7) Sector 2a08ff00056041 ┆* `A. The retrieval keys of the message are reported to SAR. 5.13.2.2.4 Log and Accountability Package (LOG) The Log and Accountability Package collects log records reported from various package and stores them on disk. Upon request from the Sup┆
0x2b800…2b900 (43, 0, 8) Sector 2b09ff00056041 ┆+ `Aue. 5.13.2.2.2.5 OCR - Terminal Manager Messages received by the OCR Terminal Manager, which did not successfully pass the format A validation are queued to the MSO via the Distribution Package. 5.13.2.2.3 Storage and Retrieval (SAR) The S┆
0x2b900…2ba00 (43, 0, 9) Sector 2b0aff00056041 ┆+ `Atorage and Retrieval Package handles the storage/retrieval of all items of information, which are stored on long term storage. 5.13.2.2.3.1 VDU - Terminal Manager a) Supervisor Function Supervisor retrieve requests are by TEP inserted in the┆
0x2ba00…2bb00 (43, 0, 10) Sector 2b0ba000056041 ┆+ `A SAR retrieve request queue. When the SAR Package has processed the request, the result is placed in the Terminal Package supervisor queue for delivery. the Distribution Package are queued to TEP in the MDCO queue. Distribution instructions to t┆
0x2bb00…2bc00 (43, 0, 11) Sector 2b0cff00056041 ┆+ `A 1 When the Supervisor Terminal Manager has requested a disk dismount, this is reported to SAR via the SAR request queue. This request is acknowledged by SAR by queuing an acknowled┆
0x2bc00…2bd00 (43, 0, 12) Sector 2b0dff00056041 ┆+ `Age in the proper queue. When the Supervisor has performed a disk mount this is communicated to SAR by the Terminal Manager. Dump activities commanded or acknowledged by the supervisor are communicated to the SAR by the Terminal Manager. Rep┆
0x2bd00…2be00 (43, 0, 13) Sector 2b0ed000056041 ┆+ P `Aorts, mount request reports, dump request reports for print-out at the printer(s) associated the supervisor VDU are placed in the Terminal Package queue for reports by SAR. Refer fig. 5.13.2.2.3-1. Service Function Messages detected to be in ┆
0x2be00…2bf00 (43, 0, 14) Sector 2b0f9000056041 ┆+ `A 1 Figure 5.13.2.2.3-1 for which the MSO request a print-out at his own printer are queued to the Distribution Package for queuing to ┆
0x2bf00…2c000 (43, 0, 15) Sector 2b00ff00056041 ┆+ `A 1 b) Message Distribution Control Function When the MDCO wants to retrieve a message, TEP inserts the retrieve request in the SAR Packages retrieve request queue. SAR inserts the┆
0x2c000…2c100 (44, 0, 0) Sector 2c018d00056041 ┆, `A 1 Fig. 5.13.2.2.2-2 age Service Function Incoming and outgoing Messages, which are not automatically accepted by Traffic Handling a┆
0x2c100…2c200 (44, 0, 1) Sector 2c02ff00056041 ┆, `A 1 d) User Functions TEP queues messages for coordination, messages for release, comments, and release notifications to be distributed to the Distribution Package. Information f┆
0x2c200…2c300 (44, 0, 2) Sector 2c03ff00056041 ┆, `Aor which the user requests a print-out is queued to the Distribution Package for queuing to the shared printer associated with the user VDU. The Distribution package queues information addressed to a user position in the FLASH, IMMEDIATE, PRIORIT┆
0x2c300…2c400 (44, 0, 3) Sector 2c047c00056041 ┆, | `AY or ROUTINE queue of TEP in accordance with the precedence of the delivered information. Refer fig. 5.13.2.2.2-3. s. 5.13.2.2.1-1/2/3 system state. For detailed recovery levels ref. sec. 4.7. 5.13.1.3 Package Control TEP is as a whole co┆
0x2c400…2c500 (44, 0, 4) Sector 2c059000056041 ┆, `A 1 Figure 5.13.2.2.2-3 ling. 5.13.2.2.1.3 PTR - Terminal Manager ACP127 messages received by the Terminal Manager from a PTR are ┆
0x2c500…2c600 (44, 0, 5) Sector 2c06ff00056041 ┆, `A 1 5.13.2.2.2.2 Printer - Terminal Manager The Distribution Package queues information addressed, either by SCD or device designator, to the printer position in the FLASH, IMMEDIATE,┆
0x2c600…2c700 (44, 0, 6) Sector 2c07ff00056041 ┆, `A PRIORITY or ROUTINE queue of the Printer Terminal Manager in accordance with the precedence of the delivered information. 5.13.2.2.2.3 PTR - Terminal Manager ACP127 messages received by the PTR - Terminal Manager which did not successfully pas┆
0x2c700…2c800 (44, 0, 7) Sector 2b08ff00056041 ┆+ `As the ACP127 validation are queued to the MSO via the Distribution Package. 5.13.2.2.2.4 PTP - Terminal Manager Messages for which the supervisor has specified output on PTP are queued by the Distribution Package in the PTP Terminal Manager que┆
0x2c800…2c900 (44, 0, 8) Sector 2c09b100056041 ┆, 1 `Ag or released message for internal re-distribution, the message is placed by TEP in the Distribution Packages queue assigned to this purpose. Refer fig. 5.13.2.2.2-1. for each terminal type (VDU, Printer, PTR, PTP, OCR) the interface between th┆
0x2c900…2ca00 (44, 0, 9) Sector 2c0a8f00056041 ┆, `A 1 Figure 5.13.2.2.2-1 Function, Message Distribution Control Function, Message Service Function, User Functions. It should however, b┆
0x2ca00…2cb00 (44, 0, 10) Sector 2c0bff00056041 ┆, `A 1 b) MDCO Function Incoming messages for which distribution cannot be determined by the Distribution Package are queued to TEP in the MDCO queue. Distribution instructions to t┆
0x2cb00…2cc00 (44, 0, 11) Sector 2c0cff00056041 ┆, `Ahe Distribution Package leading to delivery of information to a terminal position not active are delivered in this queue as well. The decision for distribution made by the MDCO is communicated to the Distribution Package, which if the ordered dis┆
0x2cc00…2cd00 (44, 0, 12) Sector 2c0dff00056041 ┆, `Atribution can be executed, i.e. listed terminal positions active, returns a confirmation signal to the terminal position. The MDCO may retrieve messages for distribution. Such messages are by TEP queued for the Distribution Package in the approp┆
0x2cd00…2ce00 (44, 0, 13) Sector 2c0eff00056041 ┆, `Ariate queue. The information which the MDCO requests to be printed is queued to the Distribution Package for queuing to the printer associated the MDCO VDU. Refer fig. 5.13.2.2.2-2. b) Message Service Function Messages detected to be in ┆
0x2ce00…2cf00 (44, 0, 14) Sector 2c0fff00056041 ┆, `Aerror by the Terminal Manager of an OCR or PTR are by the Distribution Package queued to the Message Service Operator. The information for which the MSO request a print-out at his own printer are queued to the Distribution Package for queuing to ┆
0x2cf00…2d000 (44, 0, 15) Sector 2c00ce00056041 ┆, N `Athe printer associated with the MSO VDU. Incoming messages for which the MSO requests print-out at terminal positions allocated to specified Staff Cells are queued to the Distribution Package. he supervisor's queue for reports by the Traffic ┆
0x2d000…2d100 (45, 0, 0) Sector 2d01ff00056041 ┆- `AHandling Package. Refer fig. 5.13.2.2.1-1. b) Message Distribution Control Function No interface to Traffic Handling. c) Message Service Function Incoming and outgoing Messages, which are not automatically accepted by Traffic Handling a┆
0x2d100…2d200 (45, 0, 1) Sector 2d02ff00056041 ┆- `Are queued for Message Service, in the incoming respective outgoing message service queues. TEP places the message in the Traffic Handling Package queue for messages having been to Message Service. Refer fig. 5.13.2.2.1-2. d) User Functions ┆
0x2d200…2d300 (45, 0, 2) Sector 2d03ab00056041 ┆- + `AWhen the Release Officer releases a message, TEP places the message in the Message Routing Queue (MRQ) of the Traffic Handling Package. Refer fig. 5.13.2.2.1-3. wn, switch-over or total system failure "recovery required" is specified (by SS&C). ┆
0x2d300…2d400 (45, 0, 3) Sector 2d049100056041 ┆- `A 1 Figs. 5.13.2.2.1-1/2/3 system state. For detailed recovery levels ref. sec. 4.7. 5.13.1.3 Package Control TEP is as a whole co┆
0x2d400…2d500 (45, 0, 4) Sector 2d05ff00056041 ┆- `A 1 5.13.2.2.1.2 Printer - Terminal Manager No interface to Traffic Handling. 5.13.2.2.1.3 PTR - Terminal Manager ACP127 messages received by the Terminal Manager from a PTR are ┆
0x2d500…2d600 (45, 0, 5) Sector 2d06ff00056041 ┆- `Aplaced in the Message Routing Queue (MRQ) of the Traffic Handling Package for routing assignment. 5.13.2.2.1.4 PTP - Terminal Manager When the Traffic Handling Package detects an outgoing message, which shall be output on the PTP, the Traffic H┆
0x2d600…2d700 (45, 0, 6) Sector 2d07ff00056041 ┆- `Aandling Package queues the message to the PTP. 5.13.2.2.1.5 OCR - Terminal Manager Messages received in format A from the OCR - Terminal Manager are placed in the Message Routing Queue (MRQ) of the Traffic Handling Package for Routing assignmen┆
0x2d700…2d800 (45, 0, 7) Sector 2c08ff00056041 ┆, `At and ACP127 conversion. 5.13.2.2.2 Distribution (MDP) The Distribution Package is responsible for internal distribution of information. 5.13.2.2.2.1 VDU - Terminal Manager a) Supervisor Function When the Supervisor retrieves an incomin┆
0x2d800…2d900 (45, 0, 8) Sector 2d09ff00056041 ┆- `Aces In the following sections, the interfaces of the Terminal Package to other packages are described. Each section describes the interface to one package and contains for each terminal type (VDU, Printer, PTR, PTP, OCR) the interface between th┆
0x2d900…2da00 (45, 0, 9) Sector 5f554e52454144 ┆_UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD_┆
0x2da00…2db00 (45, 0, 10) Sector 2d0bff00056041 ┆- `Ae understood that for each active VDU terminal, an interface of the described type exists, i.e. if two MDCOs are signed-in, two instances of MDCO interfaces exist, one for each MDCO terminal position. Further, if a terminal position has access to t┆
0x2db00…2dc00 (45, 0, 11) Sector 2d0cff00056041 ┆- `Awo or more CAMPS functions, that terminal position or instance of the Terminal Package will have all the interfaces described for the CAMPS functions to which access is granted. 5.13.2.2.1 Traffic Handling (THP) The Traffic Handling Package per┆
0x2dc00…2dd00 (45, 0, 12) Sector 2d0d6400056041 ┆- d `Aforms analysis of incoming and outgoing messages, as well as routing of outgoing messages. VDU. ) Log. This function generates the information to be delivered to the Log & Accountability Package. 2) Statistics. This function generate┆
0x2dd00…2de00 (45, 0, 13) Sector 2d0eff00056041 ┆- `A 1 5.13.2.2.1.1 VDU - Terminal Manager a) Supervisor Function Service Message prepared by the Supervisor are queued by TEP in the Traffic Handling Package queue for outgoing servi┆
0x2de00…2df00 (45, 0, 14) Sector 2d0fff00056041 ┆- `Ace messages. Outgoing Messages retrieved for rerun by the Supervisor are queued by TEP in the Traffic Handling Package queue for outgoing messages. Incoming Service Messages which shall be presented to the Supervisor are queued by the Traffic ┆
0x2df00…2e000 (45, 0, 15) Sector 2d00ff00056041 ┆- `AHandling Package in the supervisor's queue for service messages. Security reports, warning reports, and channel reports for print-out at the printer(s) associated the supervisor VDU are placed in the supervisor's queue for reports by the Traffic ┆
0x2e000…2e100 (46, 0, 0) Sector 2e016b00056041 ┆. k `Asic Functions onto the Top Level Functions for this Terminal Manager is shown on fig. 5.13.1.2.8-1. inated. 3) Send Q-Element. This function enters (via Queue Monitor) an element into a specified queue. 4) Dismantle Q-Element. This fu┆
0x2e100…2e200 (46, 0, 1) Sector 2e02ae00056041 ┆. . `A 1 TERMINAL MANAGER FIGS. 5.13.1.2.4-1/5-1/6-1/7-1/8-1 tions (defined in Queue Monitor) applicable to TEP. 6) Send Request. This ┆
0x2e200…2e300 (46, 0, 2) Sector 2e03ff00056041 ┆. `A 1 5.13.1.2.9 Recovery Functions When the Terminal Package is restarted by SS&C following close down, switch-over or total system failure "recovery required" is specified (by SS&C). ┆
0x2e300…2e400 (46, 0, 3) Sector 2e04ff00056041 ┆. `A Relevant queues will then contain contents according to last checkpoint and Terminal package will inspect the queues to re-establish the system state. For detailed recovery levels ref. sec. 4.7. 5.13.1.3 Package Control TEP is as a whole co┆
0x2e400…2e500 (46, 0, 4) Sector 2e05ff00056041 ┆. `Antrolled by the SS&C Software, refer subsection 5.13.1.2.1. The only parameters shared between TEP and other packages are the System Parameters to which access is controlled by the Table Management package. Errors detected by TEP are reported to┆
0x2e500…2e600 (46, 0, 5) Sector 2e06f600056041 ┆. v `A SS&C by means of a queue mechanism. Errors of this kind will be defined during detailed design. 5.13.1.4 Characteristics TBD. 5.13.1.5 Design and Construction Refer section 2.5. 5.13.1.6 Documentation Refer section 2.6. lose down┆
0x2e600…2e700 (46, 0, 6) Sector 2e07ff00056041 ┆. `A 1 5.13.2 Environment 5.13.2.1 External Interfaces User Procedures ref. doc. no. CPS/ICD/001 MDCO Procedures ref. doc. no. CPS/ICD/002 Message Service Procedures ref. doc. no. ┆
0x2e700…2e800 (46, 0, 7) Sector 2d08ff00056041 ┆- `A CPS/ICD/002 Supervisor Commands and Procedures ref. doc. no. CPS/ICD/002 Optical Character Reader ref. doc no. CPS/ICD/008 PTR/PTP 5.13.2.2 Package Interfa┆
0x2e800…2e900 (46, 0, 8) Sector 2e09ff00056041 ┆. `A 1 2) Format Completion. This function hands over to the Terminal IF Software data to be filled into the format to be output. 3) Format Output. This function calls upon th┆
0x2e900…2ea00 (46, 0, 9) Sector 5f554e52454144 ┆_UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD_┆
0x2ea00…2eb00 (46, 0, 10) Sector 2e0bff00056041 ┆. `Anction compares the contents of a format sent to a terminal with the contents received from the same terminal to identify changes performed by the user. 6) Format Validation. This function performs the syntax and semantic validation of the co┆
0x2eb00…2ec00 (46, 0, 11) Sector 2e0cff00056041 ┆. `Antents of the format received. 7) Format Conversion. This function performs the conversion of the specified format to Internal Message Format. 8) Predefined Message Handling. This function handles all operations on predefined messages.┆
0x2ec00…2ed00 (46, 0, 12) Sector 2e0d6b00056041 ┆. k `A 9) Status Display. This function displays the current status in the status area on the VDU. ) Log. This function generates the information to be delivered to the Log & Accountability Package. 2) Statistics. This function generate┆
0x2ed00…2ee00 (46, 0, 13) Sector 2e0eff00056041 ┆. `A 1 5.13.1.2.4 VDU - Terminal Manager The mapping of Basic Functions onto the Top Level Functions for this Terminal Manager is shown on fig. 5.13.1.2.4-1. 5.13.1.2.5 PRINT - Termin┆
0x2ee00…2ef00 (46, 0, 14) Sector 2e0fff00056041 ┆. `Aal Manager The mapping of Basic functions onto the Top Level Functions for this Terminal Manager is shown on fig. 5.13.1.2.5-1. 5.13.1.2.6 PTR - Terminal Manager The mapping of Basic Functions onto the Top Level Functions for this Terminal Ma┆
0x2ef00…2f000 (46, 0, 15) Sector 2e00ff00056041 ┆. `Anager is shown on fig. 5.13.1.2.6-1. 5.13.1.2.7 PTP - Terminal Manager The mapping of Basic Functions onto the Top Level Functions for this Terminal Manager is shown on fig. 5.13.1.2.7-1. 5.13.1.2.8 OCR - Terminal Manager The mapping of Ba┆
0x2f000…2f100 (47, 0, 0) Sector 2f01ff00056041 ┆/ `AThis function returns (via Queue Monitor) the specified queue element to the queue from where it originated. 3) Send Q-Element. This function enters (via Queue Monitor) an element into a specified queue. 4) Dismantle Q-Element. This fu┆
0x2f100…2f200 (47, 0, 1) Sector 2f02ff00056041 ┆/ `Anction removes (via Queue Monitor) an element from a queue. 5) Auxiliary Queue Functions. These functions deal with the remaining part of the queue handling functions (defined in Queue Monitor) applicable to TEP. 6) Send Request. This ┆
0x2f200…2f300 (47, 0, 2) Sector 2f03e400056041 ┆/ d `Afunction sends (via Queue Monitor) a request to another package within CAMPS. 7) Send Reply. This function delivers a reply (via Queue Monitor) corresponding to a request received from another package within CAMPS. level functions onto Termin┆
0x2f300…2f400 (47, 0, 3) Sector 2f04ff00056041 ┆/ `A 1 8) Receive Request. This function waits for and receives (via Queue Monitor) requests from other packages within CAMPS. 9) Receive Reply. This function waits for and re┆
0x2f400…2f500 (47, 0, 4) Sector 2f05ff00056041 ┆/ `Aceives (via Queue Monitor) replies to requests sent to other packages within CAMPS. f) Start, Stop, and Error Handling. 1) Start-up. This function is activated (by SSC) when an instance of the Terminal Manager is created and performs requir┆
0x2f500…2f600 (47, 0, 5) Sector 2f06ff00056041 ┆/ `Aed initialisation. 2) Restart. This function is activated (by SSC) when an instance of the Terminal manager is created following a system failure or switch-over to standby PU. 3) Close Down. This function is performed when a close down┆
0x2f600…2f700 (47, 0, 6) Sector 2f07ff00056041 ┆/ `A operation is requested (by SSC). 4) Local Error Handling. This function performs error actions for all errors specified as local to TEP. g) Format Handling. 1) Format Selection. This function calls upon the Terminal IF Software for ┆
0x2f700…2f800 (47, 0, 7) Sector 2e087100056041 ┆. q `Aaccess to the required format corresponding to the type of terminal and the output operation in question. in Short Term Storage. 4) Close Item. This function terminates (via Message Monitor) access to an item. 5) Update Item. This fu┆
0x2f800…2f900 (47, 0, 8) Sector 2f099a00056041 ┆/ `Anction stores data (via Message Monitor) in an item. 6) Send Item. This function sends (via Message Monitor) an item to one or more queues. Figure 5.13.1-7 Message Flow for Terminal Types Printer OCR, PTR ┆
0x2f900…2fa00 (47, 0, 9) Sector 5f554e52454144 ┆_UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD_┆
0x2fa00…2fb00 (47, 0, 10) Sector 2f0bff00056041 ┆/ `Ad Control Block (associated with an item). 9) Update Control Block. This function updates (via Message Monitor), the contents of the specified Control Block. c) Table Handling. 1) Table Access. This function operates on all tables co┆
0x2fb00…2fc00 (47, 0, 11) Sector 2f0cff00056041 ┆/ `Antrolled by the Table Management Package. 2) System Parameter Access. This function operates on all system parameters controlled by the Table Management Package. 3) Global Number Series Access. This function operates on all global numb┆
0x2fc00…2fd00 (47, 0, 12) Sector 2f0dff00056041 ┆/ `Aer series controlled by the Table Management Package. d) Status, Log, and Statistics Handling. 1) Log. This function generates the information to be delivered to the Log & Accountability Package. 2) Statistics. This function generate┆
0x2fd00…2fe00 (47, 0, 13) Sector 2f0e4400056041 ┆/ D `As the information to be delivered to the Statistics Package. 1) Function Control. The tasks of Function Control are: - Transaction Handling - Item Handling - Table Handling - Queue and Request Handling - Start, Stop, and┆
0x2fe00…2ff00 (47, 0, 14) Sector 2f0fff00056041 ┆/ `A 1 3) Status. This function generates and maintains the status information required by the TEP for response to status requests. 4) VDU Status Update. This function generat┆
0x2ff00…30000 (47, 0, 15) Sector 2f00ff00056041 ┆/ `Aes and maintains the status information to be displayed in the VDU status area. e) Queue and Request Handling. 1) Look-up Q-Element. This function obtains (via Queue Monitor) next element in the specified queue. 2) Return Q-Element. ┆
0x30000…30100 (48, 0, 0) Sector 3001ff00056041 ┆0 `As as shown on fig. 5.13.1.2.3-1. This figure shows a grouping of the Basic Functions based upon their relation. The selection of the functions required for construction of the individual Terminal Managers is described later in this section. The ┆
0x30100…30200 (48, 0, 1) Sector 3002f100056041 ┆0 q `ABasic Functions are: a) Transaction Handling. 1) Interpret Command. This function inputs and interprets the commands from terminals and validates them against the list of commands allowed for the particular Terminal Manager. The Termin┆
0x30200…30300 (48, 0, 2) Sector 30034a00056041 ┆0 J `A 1 will be different with respect to commands and detailed functions and thus inherently prevented from unauthorized activities. The precise mapping of low level functions onto Termin┆
0x30300…30400 (48, 0, 3) Sector 3004ba00056041 ┆0 : `A 1 Fig. 5.13.1.2.3-1 Terminal Package Basic Functional Breakdown inal Manager dedicated especially to that terminal. The Terminal M┆
0x30400…30500 (48, 0, 4) Sector 3005ff00056041 ┆0 `A 1 2) Create Transaction. This function creates local work space and data specific to the current transaction 3) Terminate Transaction. This function frees local workspace┆
0x30500…30600 (48, 0, 5) Sector 3006ff00056041 ┆0 `A and performs "clean-up" when the current transaction is finished. 4) Display Error Message. This function converts the error codes to plain text and displays this on the response line on the VDU when requested. b) Item Handling. 1) Crea┆
0x30600…30700 (48, 0, 6) Sector 3007ff00056041 ┆0 `Ate New Item. This function creates (via the Message Monitor) a new item (message, comment etc.), in Short Term Storage ready for storing data in. 2) Create Next Version. This function creates (via Message Monitor) a new version of an alre┆
0x30700…30800 (48, 0, 7) Sector 2f08ff00056041 ┆/ `Aady existing item. 3) Open Item. This function gets (via Message Monitor) access to an existing item in Short Term Storage. 4) Close Item. This function terminates (via Message Monitor) access to an item. 5) Update Item. This fu┆
0x30800…30900 (48, 0, 8) Sector 30092600056041 ┆0 & `Aleprinters used as PTR device. . Figure 5.13.1-6 Information Flow for Terminal Type VDU Figure 5.13.1-7 Message Flow for Terminal Types Printer OCR, PTR ┆
0x30900…30a00 (48, 0, 9) Sector 5f554e52454144 ┆_UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD_┆
0x30a00…30b00 (48, 0, 10) Sector 300bff00056041 ┆0 `A and Error Handling. 2) Dialogue Control. The tasks of Dialogue Control are: - Format Reception. 3) Validation. The tasks of Validation are: - Format Validation. f) PTP - Terminal Manager. The Terminal Manager for paper ta┆
0x30b00…30c00 (48, 0, 11) Sector 300cff00056041 ┆0 `Ape output controls stand alone PTP and teleprinters used as PTP device. 1) Function Control. The tasks of Function Control are: - Table Handling - Queue and Request Handling - Start, Stop, and Error Handling 2) Dialogue Control. ┆
0x30c00…30d00 (48, 0, 12) Sector 300dc400056041 ┆0 D `A The tasks of Dialogue Control are: - Format Output. 3) Validation. N/A. g) OCR - Terminal Manager. The Terminal Manager for document input controls the stand alone OCR. ed at this level are: 1) Transaction Handling: Comma┆
0x30d00…30e00 (48, 0, 13) Sector 300eff00056041 ┆0 `A 1 1) Function Control. The tasks of Function Control are: - Transaction Handling - Item Handling - Table Handling - Queue and Request Handling - Start, Stop, and┆
0x30e00…30f00 (48, 0, 14) Sector 300fff00056041 ┆0 `A Error Handling 2) Dialogue Control. The tasks of Dialogue Control are: - Format Reception. 3) Validation. The tasks of Validation are: - Format Validation and Conversion. h) Terminal IF Software. The Tasks of Terminal IF ┆
0x30f00…31000 (48, 0, 15) Sector 3000ff00056041 ┆0 `Asoftware are to implement high level features for device access. 5.13.1.2.3 Terminal Package Basic Functions The TEP is broken down, as mentioned in the previous section, into Main Functions and these are further broken down into Basic Function┆
0x31000…31100 (49, 0, 0) Sector 3101ff00056041 ┆1 `AStatistics Handling: Collection and maintenance of status log and statistics information. 5) Queue and Request Handling: Operations on queues and inter system communication via requests/replies. 6) Start, Stop, and Error Handling: ┆
0x31100…31200 (49, 0, 1) Sector 3102ff00056041 ┆1 `AStart up, restart, close down, and local error handling. 7) Format Handling: Input, output, and validation of data for terminals. These functions are mapped onto the Top Level Functions as follows: c) VDU - Terminal Manager The Termin┆
0x31200…31300 (49, 0, 2) Sector 3103ff00056041 ┆1 `Aal Managers for the various functions (Supervisor, MDCO, MSO, User) will be different with respect to commands and detailed functions and thus inherently prevented from unauthorized activities. The precise mapping of low level functions onto Termin┆
0x31300…31400 (49, 0, 3) Sector 31049300056041 ┆1 `Aal Managers and their Top Level Functions are beyond the scope of this document and will be defined at a later stage in the design process. h active terminal is serviced by a Terminal Manager dedicated especially to that terminal. The Terminal M┆
0x31400…31500 (49, 0, 4) Sector 3105ff00056041 ┆1 `A 1 1) Function Control. The tasks of Function Control are: - Transaction Handling - Item Handling - Table Handling - Status, Log, and Statistics Handling - Queue ┆
0x31500…31600 (49, 0, 5) Sector 3106ff00056041 ┆1 `Aand Request Handling - Start, Stop, and Error Handling 2) Dialogue Control. The tasks of Dialogue Control are: - Format Input/Output and Status display. 3) Validation. The tasks of validation are: - Format Validation and Co┆
0x31600…31700 (49, 0, 6) Sector 3107ff00056041 ┆1 `Anversion. d) PRINT - Terminal Manager. The Terminal Manager for print-out controls slow - and medium-speed printers. 1) Function Control. The tasks of Function Control are: - Table Handling - Queue and Request Handling - Sta┆
0x31700…31800 (49, 0, 7) Sector 3008ff00056041 ┆0 `Art, Stop, and Error Handling 2) Dialogue Control. The tasks of Dialogue Control are: - Format output. 3) Validation. - N/A. e) PTR - Terminal Manager. The Terminal Manager for paper tape input controls stand alone PTR and te┆
0x31800…31900 (49, 0, 8) WangDocumentBody
0x31900…31a00 (49, 0, 9) Sector 5f554e52454144 ┆_UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD__UNREAD_┆
0x31a00…31b00 (49, 0, 10) Sector 310bff00056041 ┆1 `Aped with locking mechanism, this will be in the ON position too. The Terminal Manager is activated with access rights as determined by the SS&C Package. Access rights include: 1) Formats and tables. For printers addressable by SCDs, thes┆
0x31b00…31c00 (49, 0, 11) Sector 310cff00056041 ┆1 `Ae are handed over as well. 5.13.1.2.2 General Mapping of Functions onto Units a) This section describes the principal tasks of each of the Top Level Functions: - Function Control - Dialogue Control - Validation for each of the types o┆
0x31c00…31d00 (49, 0, 12) Sector 310dff00056041 ┆1 `Af Terminal Manager: - VDU - Terminal Manager - PRINT - Terminal Manager - PTR - Terminal Manager - PTP - Terminal Manager - OCR - Terminal Manager b) The main functions recognized at this level are: 1) Transaction Handling: Comma┆
0x31d00…31e00 (49, 0, 13) Sector 310e4500056041 ┆1 E `And interpretation, transaction accounting and error response. O control software making a high level interface against terminals for the rest of the Terminal package. d) The packages to which the Terminal System interfaces are 1) Kernel 2) ┆
0x31e00…31f00 (49, 0, 14) Sector 310fb300056041 ┆1 3 `A 1 Fig. 5.13.1.2.2-1 Terminal Package Top Level Breakdown ckage Control .................. 5.13.1.4 Characteristics ..........┆
0x31f00…32000 (49, 0, 15) Sector 3100ff00056041 ┆1 `A 1 2) Item Handling: Operations on items and their control blocks. 3) Table Handling: Access to tables, system parameters and global number series. 4) Status, Log, and ┆
0x32000…32100 (50, 0, 0) WangDocumentBody
[…0x27…]
0x34800…34900 (52, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(52,0, 9), len=0xff, h3=41056041}, f00=»0560A «, f01=»System Design Specific. «, f02=»sdv «, f03=»MSN «, f04=»CPS/SDS/001, 5.13 «, f05=27-01-81 10:14, f06=» 7 «, f07=»25 «, f08=» 31364 «, f09=28-01-81 11:50, f10=» «, f11=»36 «, f12=» 732 «, f13=28-01-81 12:28, f14=20-02-81 14:22, f15=»0035A «, f16=» 61 «, f17=» 8 «, f18=»01 «, f19=» 648 «, f20=» 32096 «, f21=» «, f22=»$ «, f99=020010000110056610a10a80aaca1505000000000000003803ca00df}
0x34900…34a00 (52, 0, 9) WangDocumentBody
[…0x46…]
0x39000…39100 (57, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(57,0, 1), len=0xff, h3=41053341}, f00=»0533A «, f01=»R & M PROGRAM PLNA «, f02=»VHN «, f03=»LPO «, f04=»S@TTES P< 0532A «, f05=19-01-81 15:12, f06=» 5 «, f07=»49 «, f08=» 19967 «, f09=27-01-81 15:10, f10=» «, f11=»00 «, f12=» 11 «, f13=26-01-81 11:59, f14=03-07-85 10:54, f15=»0035A «, f16=» 28 «, f17=» 7 «, f18=»09 «, f19=» 292 «, f20=» 20806 «, f21=» «, f22=» «, f99=020010000110056610a10a80aaca15050000000000000038036700df}
0x39100…39200 (57, 0, 1) WangDocumentBody
[…0x6…]
0x39800…39900 (57, 0, 8) Sector 3909bd00053341 ┆9 = 3A.......................... 5.2.9 Reliability Test Report (For Specified Modules Only) .......................... 5.2.10 Final Report ......................... RE3C#4: 2i=:g=~ JV3C/4!"<6 #6 MB&! =6 !,<6 :]=2'< AMD MB&!,<6 ! ┆
0x39900…39a00 (57, 0, 9) Sector 390aff00053341 ┆9 3A 1 5.2.1 Introduction These reports are conducted to verify and improve the reliability on module level and system level as well. The predicted values are compared with experience ┆
0x39a00…39b00 (57, 0, 10) Sector 390b6700053341 ┆9 g 3Aby test data and carefully calculated values using stress parameter techniques and FMECA tools. = Rp5Cr4IMM.:^=~ B}5I:g=~ J 5IC$3I > S C_* ┆
0x39b00…39c00 (57, 0, 11) Sector 390cff00053341 ┆9 3A 1 TABLE OF CONTENTS 6 FAILURE REPORTING AND CONTROL .................. 6.1 INTRODUCTION ............................... 6 6.2 DESCRIPTION OF FAILURE REPORTING SYSTEM ..┆
0x39c00…39d00 (57, 0, 12) Sector 390d7b00053341 ┆9 { 3A.. 6 6.3 COLLECTION OF FAILURE DATA ................. 6 6.4 HANDLING OF FAILURE DATA ................... n mellemrum eller retur Under redigering nu Ukendt dokument Fundet I brug nu Allerede p> systemdiskette ┆
0x39d00…39e00 (57, 0, 13) Sector 390eff00053341 ┆9 3A 1 6.1 INTRODUCTION A deliberate failure reporting and control system is of great importance during implementation of the project and in the operational phase as well. This section ┆
0x39e00…39f00 (57, 0, 14) Sector 390fff00053341 ┆9 3Adescribes all action items to be taken to establish and run such a system. 6.2 DESCRIPTION OF FAILURE REPORTING SYSTEM For each CR80 module in CAMPS, a log book shall be established. Together with a complete technical manual, including reliabi┆
0x39f00…3a000 (57, 0, 15) Sector 3900ff00053341 ┆9 3Ality analysis report, possibly FMECA analyse report, and design analysis report, it shall contain all facts considering the specific module. All failures shall be registrated in time and the operating or test conditions under which the module fail┆
0x3a000…3a100 (58, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(58,0, 1), len=0xff, h3=41053341}, f00=»0533A «, f01=»R & M PROGRAM PLNA «, f02=»VHN «, f03=»LPO «, f04=»S@TTES P< 0532A «, f05=19-01-81 15:12, f06=» 5 «, f07=»49 «, f08=» 19967 «, f09=27-01-81 15:10, f10=» «, f11=»00 «, f12=» 7 «, f13=26-01-81 11:59, f14=27-01-81 15:11, f15=»0035A «, f16=» 28 «, f17=» 7 «, f18=»09 «, f19=» 292 «, f20=» 20802 «, f21=» «, f22=» «, f99=020010000110056610a10a80aaca15050000000000000038036700df}
0x3a100…3a200 (58, 0, 1) Sector 3a021c00053341 ┆: 3A : : : : 9 9 9 9 9 9 8 8 8 7 7 7 7 7 7 6 6 6 " " DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO┆
0x3a200…3a300 (58, 0, 2) Sector 3a038f00053341 ┆: 3A 1 CPS/PLN/004 LP/810123 # R & M PROGRAM PLAN CAMPS 6'C*-:!<~ B%-!/=6WC*-!/=6)M2&*/=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 3a04ff00053341 ┆: 3A 1 1 TABLE OF CONTENTS 5 R & M ANALYSIS ............................... 2 5.1 INTRODUCTION ................┆
0x3a400…3a500 (58, 0, 4) Sector 3a051c00053341 ┆: 3A............... 2 <6 M1' R+/M )M2&MP'I:^=~ B;/IMC'!e=6 *(=~ RN/C}/:]=2#<:b= Rc/! <6 Ch/! <6 M)(:^=~ Bt/I:\=2#<C /:]=2#<! <6 M)(I:g=~ J /Mj'! "(=~ R*/!/=6jM (*(=~ R;/!/=6nM (*(=~ RM/!/=6iM (*(=~ R`/!/=6WM (*(=~ Rt/!/=6lM (*(=~ R ┆
0x3a500…3a600 (58, 0, 5) Sector 3a06f600053341 ┆: v 3A 1 5 R & M ANALYSIS 5.1 INTRODUCTION This section summarizes all activities which have to be performed to realise the specific requirements mentioned in sec. 3.1.2. M% ! "2<┆
0x3a600…3a700 (58, 0, 6) Sector 3a07ff00053341 ┆: 3A 1 5.2 RELIABILITY REPORTS ........................ 5.2.1 Introduction ........................... 4 5.2.2 Reliability Model (Parts Count) ........ 5.2.3 Tabular ┆
0x3a700…3a800 (58, 0, 7) Sector 3908ff00053341 ┆9 3APresentation of Component Failure Rates Under Required Conditions 5.2.5 MTBF Calculation Method ................ 5.2.6 Mathematical Model ..................... 5.2.7 Failure Analysis Reports (System Level Only) ..┆
0x3a800…3a900 (58, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(58,0, 9), len=0xff, h3=41056041}, f00=»0560A «, f01=»System Design Specific. «, f02=»sdv «, f03=»MSN «, f04=»CPS/SDS/001, 5.13 «, f05=27-01-81 10:14, f06=» 7 «, f07=»25 «, f08=» 31364 «, f09=28-01-81 11:50, f10=» «, f11=»36 «, f12=» 732 «, f13=28-01-81 12:28, f14=29-01-81 10:26, f15=»0035A «, f16=» 61 «, f17=» 8 «, f18=»01 «, f19=» 648 «, f20=» 32096 «, f21=» «, f22=»$ «, f99=020010000110056610a10a80aaca1505000000000000003803ca00df}
0x3a900…3aa00 (58, 0, 9) Sector 3a0a3d00056041 ┆: = `A : : 4 4 3 3 3 3 3 3 3 3 2 2 2 2 2 1 1 1 1 0 0 0 0 0 / / / . . . . . - - - , , , , , , + + + + + + * * * * ) ) ) ) ) ( ( ( ( DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Komm┆
0x3aa00…3ab00 (58, 0, 10) Sector 3a0b9e00056041 ┆: `A 1 CPS/SDS/001 BBC/810115 CAMPS SYSTEM 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┆
0x3ab00…3ac00 (58, 0, 11) Sector 3a0cff00056041 ┆: `A 1 1 TABLE OF CONTENTS 5.13 TERMINAL PACKAGE ......................... 5.13.1 Summary of Requirements ..┆
0x3ac00…3ad00 (58, 0, 12) Sector 3a0dff00056041 ┆: `A............ 5.13.1.1 Package Description .............. 5.13.1.2 Package Function ................. 5.13.1.2.1 Activation/Deactivation ...... 5.13.1.2.2 General Mapping of Function onto Units ..........┆
0x3ad00…3ae00 (58, 0, 13) Sector 3a0eff00056041 ┆: `A......... 5.13.1.2.3 Terminal Package Basic Functions .................... 5.13.1.2.4 VDU - Terminal Manager ....... 5.13.1.2.5 Printer - Terminal Manager ... 5.13.1.2.6 PTR - Terminal Manager ....... ┆
0x3ae00…3af00 (58, 0, 14) Sector 3a0fff00056041 ┆: `A 5.13.1.2.7 PTP - Terminal Manager ....... 5.13.1.2.8 OCR - Terminal Manager ....... 5.13.1.2.9 Recovery Functions ........... 5.13.1.3 Package Control .................. 5.13.1.4 Characteristics ..........┆
0x3af00…3b000 (58, 0, 15) Sector 3400ff00056041 ┆4 `A........ 5.13.1.5 Design and Construction .......... 5.13.1.6 Documentation .................... 5.13.2 Environment .......................... 5.13.2.1 External Interfaces .............. 5.13.2.2 Package Inter┆
0x3b000…3b100 (59, 0, 0) Sector 3b01ff00047241 ┆; rAaced log. Then the Log and Accountability package places a command completion code in the terminal package queue assigned to this purpose, so that TEP can generate a command completion report. Warning reports are placed in the warning queue by Log┆
0x3b100…3b200 (59, 0, 1) Sector 3b022300047241 ┆; # rA and Accountability Package. Fig. 5.13.2.2.2-3 rted by SS&C following close down, switch-over or total system failure "recovery required" is specified (by SS&C).┆
0x3b200…3b300 (59, 0, 2) Sector 3b038e00047241 ┆; rA 1 Fig. 15.13.2.2.4-1 SAR) Package handles the storage/retrieval of all items of information, which are stored on long term storage. ┆
0x3b300…3b400 (59, 0, 3) Sector 3b04ff00047241 ┆; rA 1 5.13.2.2.4.2 Message Distribution Control Function Log records of MDCO activities are communicated to the Log and Accountability Package through CAMPS Systeme Functions. 5.13.2┆
0x3b400…3b500 (59, 0, 4) Sector 3b05ff00047241 ┆; rA.2.4.3 Message Service Function Log records of MSO activities are communicated to the Log and Accountability Package through CAMPS System Functions. 5.13.2.2.4.4 User Functions Log records of user activities are communicated by the Terminal P┆
0x3b500…3b600 (59, 0, 5) Sector 3b06ff00047241 ┆; rAackage to the Log and Accountability Package through CAMPS System Functions. TEP will periodically with a periodicity specified by the supervisor or as a result of a user request ask the Log and Accountability Package to extract the log records co┆
0x3b600…3b700 (59, 0, 6) Sector 3b07ff00047241 ┆; rAnstituting a specified Status Report. The Log and Accountability Package will place the requested information in the Terminal Package queue for requested information assigned to the requesting user. The request may be for one of the following sta┆
0x3b700…3b800 (59, 0, 7) Sector 3a08ff00047241 ┆: rAtus types: - Transaction Status Report - Message Status - Release Status 5.13.2.2.5 Statistics The Statistics package collects statistical information from many packages and makes statistics based on the collected information. The statisti┆
0x3b800…3b900 (59, 0, 8) Sector 3b098d00047241 ┆; rA 1 Fig. 5.13.2.2.3-2 e Distribution Control Function, Message Service Function or User Functions. It should however be understood that┆
0x3b900…3ba00 (59, 0, 9) Sector 3b0a8d00047241 ┆; rA 1 Fig. 5.13.2.2.3-3 tances of MDCO interfaces exist, one for each MDCO terminal position. Further, if a terminal position has access ┆
0x3ba00…3bb00 (59, 0, 10) Sector 3b0bff00047241 ┆; rA 1 5.13.2.2.3.4 User Functions When a user issues a retrieval or message merge request, the Terminal package inserts the request in the SAR package retrieval request queue. When th┆
0x3bb00…3bc00 (59, 0, 11) Sector 3b0cff00047241 ┆; rAe SAR Package has processed the request, it inserts the result of it in the Terminal Package delivery queue. 5.13.2.2.4 Log and Accountability Package The Log and Accountability Package collects log records reported from various package and sto┆
0x3bc00…3bd00 (59, 0, 12) Sector 3b0dff00047241 ┆; rAres them on disk. Upon request from the Supervisor trace of log is performed by the Log and Accountability Package. The Log and Accountability delivers periodically a report to the terminal position containing log records for each transaction wh┆
0x3bd00…3be00 (59, 0, 13) Sector 3b0eff00047241 ┆; rAich have been executed at that terminal in the given period. 5.13.2.2.4.1 Supervisor Function Log records of Supervisor activities (command utilization records) are communicated to the Log and Accountability package through CAMPS System Functio┆
0x3be00…3bf00 (59, 0, 14) Sector 3b0fff00047241 ┆; rAns. The Log and Accountability Package queues log records to the Terminal Package (Q1) for print-out at the supervisor's terminal as they arrive, if this has been requested by the supervisor. The supervisor may request various traces of log reco┆
0x3bf00…3c000 (59, 0, 15) Sector 3b00ff00047241 ┆; rArds. The Terminal Package queues such requests in the command function queue of the Log and Accountability Package. When the Log and Accountability Package has traced the requested log records, they are placed in the Terminal Package queue for tr┆
0x3c000…3c100 (60, 0, 0) Sector 3c018d00047241 ┆< rA 1 Fig. 5.13.2.2.2-2 rvice messages Q2: Queue for Rerun of Outgoing messages Q3: Queue for Supervisor reports Q4: Queue for Service ┆
0x3c100…3c200 (60, 0, 1) Sector 3c028d00047241 ┆< rA 1 Fig. 5.13.2.2.2-3 rted by SS&C following close down, switch-over or total system failure "recovery required" is specified (by SS&C).┆
0x3c200…3c300 (60, 0, 2) Sector 3c03ff00047241 ┆< rA 1 5.13.2.2.3 Storage and Retrieval (SAR) The Storage and Retrieval (SAR) Package handles the storage/retrieval of all items of information, which are stored on long term storage. ┆
0x3c300…3c400 (60, 0, 3) Sector 3c04ff00047241 ┆< rA 5.13.2.2.3.1 Supervisor Function When the SAR Package detects the need for getting an offline disc mounted or for dumping to offline discs, a request for the required activity is inserted by the SAR Package in the Terminal Package Supervisor repo┆
0x3c400…3c500 (60, 0, 4) Sector 3c05ff00047241 ┆< rArt queue. When the Supervisor has mounted the wanted disc or acknowledged the dump activity to take place, the Terminal Package communicates this to SAR. Supervisor retrieve requests are by the Terminal Package inserted in the SAR package retrie┆
0x3c500…3c600 (60, 0, 5) Sector 3c06ff00047241 ┆< rAve request queue. When the SAR Package has processed the request, the result is placed in the Terminal Package supervisor queue for delivery. Reports generated by SAR are inserted in the Terminal Package supervisor report queue. 5.13.2.2.3.2 M┆
0x3c600…3c700 (60, 0, 6) Sector 3c07ff00047241 ┆< rAessage Distribution Control Function When the MDCO wants to retrieve a message, the Terminal Package inserts the retrieve request in the SAR Packages retrieve request queue. The SAR Package inserts the result of the processing of the request in t┆
0x3c700…3c800 (60, 0, 7) Sector 3b087300047241 ┆; s rAhe Terminal Packages MDCO delivery queue. 5.13.2.2.3.3 Message Service Function No interface to SAR. Fig. 5.13.2.2.1-2 5.13.2.2 Package Interfaces In the following subsections, all the interfaces of the Terminal package to other ┆
0x3c800…3c900 (60, 0, 8) Sector 3c098d00047241 ┆< rA 1 Fig. 5.13.2.2.1-3 e Distribution Control Function, Message Service Function or User Functions. It should however be understood that┆
0x3c900…3ca00 (60, 0, 9) Sector 3c0a8c00047241 ┆< rA 1 Fig. 5.13.2.2.2-1 stances of MDCO interfaces exist, one for each MDCO terminal position. Further, if a terminal position has access ┆
0x3ca00…3cb00 (60, 0, 10) Sector 3c0bff00047241 ┆< rA 1 5.13.2.2.2.2 MDCO Function Incoming messages for which distribution cannot be determined by the Distribution Package are queued for the Terminal Package in the queue assigned to t┆
0x3cb00…3cc00 (60, 0, 11) Sector 3c0cff00047241 ┆< rAhis purpose. Distribution instructions to the Distribution Package leading to delivery of information to a terminal position not active are delivered in this queue as well. The decision for distribution made by the MDCO is communicated to the Di┆
0x3cc00…3cd00 (60, 0, 12) Sector 3c0dff00047241 ┆< rAstribution system, which if the ordered distribution can be executed, i.e. listed terminal positions active, returns a confirmation signal to the terminal position. The MDCO may retrieve messages for distribution. Such messages are by the Termina┆
0x3cd00…3ce00 (60, 0, 13) Sector 3c0eff00047241 ┆< rAl Package queued for the Distribution Package in the appropriate queue. 5.13.2.2.2.3 Message Service Function TBD. 5.13.2.2.2.3 User Functions The Terminal package queues messages for coordination, messages for release, comments, and relea┆
0x3ce00…3cf00 (60, 0, 14) Sector 3c0fff00047241 ┆< rAse notifications to be distributed to the Distribution Package. The Distribution package queues information addressed to a user position in the FLASH, IMMEDIATE, PRIORITY or ROUTINE queue of the Terminal Package in accordance with the precedence o┆
0x3cf00…3d000 (60, 0, 15) Sector 3c002400047241 ┆< $ rAf the delivered information. red. 5.13.1.2.14 Print Manager - User Functions The Print/Display Manager controls print on printer and display on VDU of messages, comments and various control information. Print/Display is performed under direc┆
0x3d000…3d100 (61, 0, 0) Sector 3d01ff00047241 ┆= rA 1 Q1: Queue for Outgoing Service messages Q2: Queue for Rerun of Outgoing messages Q3: Queue for Supervisor reports Q4: Queue for Service ┆
0x3d100…3d200 (61, 0, 1) Sector 3d023700047241 ┆= 7 rAMessages Q5: Request queue Fig. 5.13.2.2.1-1 5.13.1.2.15 Recovery Functions When the Terminal Package is restarted by SS&C following close down, switch-over or total system failure "recovery required" is specified (by SS&C).┆
0x3d200…3d300 (61, 0, 2) Sector 3d03ff00047241 ┆= rA 1 5.13.2.2.1.2 Message Distribution Control Function No interface to Traffic Handling. 5.13.2.2.1.3 Message Service Function Messages that are not automatically accepted by Tra┆
0x3d300…3d400 (61, 0, 3) Sector 3d04ff00047241 ┆= rAffic Handling are queued for Message Service. The Terminal Package places the message in the Traffic Handling packages queue for messages having been to Message Service after completion of message service. 5.13.2.2.1.4 User Functions When the┆
0x3d400…3d500 (61, 0, 4) Sector 3d05ff00047241 ┆= rA Release Officer releases a message, the Terminal Package places the message in the Released message queue of the Traffic Handling Package. The Traffic Handling Package returns a Station Serial Number, SSN to the Terminal Package. 5.13.2.3.2 Di┆
0x3d500…3d600 (61, 0, 5) Sector 3d06ff00047241 ┆= rAstribution The Distribution Package is responsible for internal distribution of information. 5.13.2.3.2.1 Supervisor Function When the Supervisor retrieves an incoming or released message for internal re-distribution, the message is placed by┆
0x3d600…3d700 (61, 0, 6) Sector 3d075a00047241 ┆= Z rA the Terminal Package in the Distribution Packages queue assigned to this purpose. nt 5.13.2.1 External Interfaces User Procedures ref. doc. no. CPS/ICD/001 MDCO Procedures ref. doc. no. CPS/ICD/002 Message Service Procedures ref. doc. no. ┆
0x3d700…3d800 (61, 0, 7) Sector 3c088d00047241 ┆< rA 1 Fig. 5.13.2.2.1-2 5.13.2.2 Package Interfaces In the following subsections, all the interfaces of the Terminal package to other ┆
0x3d800…3d900 (61, 0, 8) Sector 3d09ff00047241 ┆= rApackages are described. Each interface is described for one terminal position having either access to the Supervisor Function, Message Distribution Control Function, Message Service Function or User Functions. It should however be understood that┆
0x3d900…3da00 (61, 0, 9) Sector 3d0aff00047241 ┆= rA for each active terminal position accessing CAMPS, an interface of the described type exists, i.e. if two MDCOs are signed-in, two instances of MDCO interfaces exist, one for each MDCO terminal position. Further, if a terminal position has access ┆
0x3da00…3db00 (61, 0, 10) Sector 3d0bff00047241 ┆= rAto two or more CAMPS functions, that terminal position or instance of the Terminal package will have all the interfaces described for the CAMPS functions to which access is granted. 5.13.2.2.1 Traffic Handling The Traffic Handling Package perfo┆
0x3db00…3dc00 (61, 0, 11) Sector 3d0cff00047241 ┆= rArms analysis of incoming and outgoing messages, as well as routing of outgoing messages. 5.13.2.2.1.1 Supervisor Function Service Messages prepared by the Supervisor are queued by the Terminal Package in the Traffic Handling package queue for o┆
0x3dc00…3dd00 (61, 0, 12) Sector 3d0d2100047241 ┆= ! rAutgoing service messages. ption will take place as described above in 3), the pre-emption of the Dialogue Manager having the same effect as the suspend function. If the terminal is in receive mode, the printing action will be stopped (analogue to ┆
0x3dd00…3de00 (61, 0, 13) Sector 3d0eff00047241 ┆= rA 1 Outgoing Messages retrieved for rerun by the Supervisor are queued by the Terminal Package in the Traffic Handling Package queue for outgoing messages. Incoming Service Messages ┆
0x3de00…3df00 (61, 0, 14) Sector 3d0fff00047241 ┆= rAwhich shall be presented to the Supervisor are queued by the Traffic Handling package in the Terminal Package queue for service messages. Security reports, warning reports and channel reports are placed in the Terminal Package queue for reports by┆
0x3df00…3e000 (61, 0, 15) Sector 3d002500047241 ┆= % rA the Traffic Handling Package. red. 5.13.1.2.14 Print Manager - User Functions The Print/Display Manager controls print on printer and display on VDU of messages, comments and various control information. Print/Display is performed under direc┆
0x3e000…3e100 (62, 0, 0) Sector 3e01e000047241 ┆> ` rAtion of a Format Descriptor for the presentation format under execution. The format description describes the fields to be output, the sequence of output and the text strings to be output together with the fields. e a record for statistics colle┆
0x3e100…3e200 (62, 0, 1) Sector 3e02ff00047241 ┆> rA 1 5.13.1.2.15 Recovery Functions When the Terminal Package is restarted by SS&C following close down, switch-over or total system failure "recovery required" is specified (by SS&C).┆
0x3e200…3e300 (62, 0, 2) Sector 3e03ff00047241 ┆> rA Relevant queues will then contain contents according to last checkpoint and Terminal package will inspect the queues to re-establish the system state. For detailed recovery levels ref. sec. 4.7. 5.13.1.2.16 Special Devices TBD. 5.13.1.3┆
0x3e300…3e400 (62, 0, 3) Sector 3e04ff00047241 ┆> rA Package Control TEP is as a whole controlled by the SS&C Software, refer subsection 5.13.1.2.1. The only parameters shared between TEP and other packages are the System Parameters to which access is controlled by the Table Management package. ┆
0x3e400…3e500 (62, 0, 4) Sector 3e05ff00047241 ┆> rA Errors detected by TEP are reported to SS&C by means of a queue mechanism. Errors of this kind will be defined during detailed design. 5.13.1.4 Characteristics TBD. 5.13.1.5 Design and Construction Refer section 2.5. 5.13.1.6 Document┆
0x3e500…3e600 (62, 0, 5) Sector 3e062400047241 ┆> $ rAation Refer section 2.6. tion of a transaction. Log information is communicated to the Log and Accountability package via the CAMPS System Functions by the Function Manager upon initiation and/or completion of a transaction as required for ┆
0x3e600…3e700 (62, 0, 6) Sector 3e07ff00047241 ┆> rA 1 5.13.2 Environment 5.13.2.1 External Interfaces User Procedures ref. doc. no. CPS/ICD/001 MDCO Procedures ref. doc. no. CPS/ICD/002 Message Service Procedures ref. doc. no. ┆
0x3e700…3e800 (62, 0, 7) Sector 3d08ff00047241 ┆= rA CPS/ICD/002 Supervisor Commands and Procedures ref. doc. no. CPS/ICD/002 5.13.2.2 Package Interfaces In the following subsections, all the interfaces of the Terminal package to other ┆
0x3e800…3e900 (62, 0, 8) Sector 3e09ff00047241 ┆> rAre a printing action is in progress is as described above in 3). The effect of a cancel request when an interactive action is in progress will cause the action to be terminated. Other effects will depend on the type of the cancelled transaction┆
0x3e900…3ea00 (62, 0, 9) Sector 3e0a8d00047241 ┆> rA. A suspend function may be issued by the operator. The interpretation of the suspend command depends on the action in progress. Delivery queue management and scheduling. The Function Manager monitors the queues associated with the termin┆
0x3ea00…3eb00 (62, 0, 10) Sector 3e0bff00047241 ┆> rA 1 If an interactive function is in progress, the suspend function will either have the same effect as the cancel function or cause information entered so far to be kept by the syst┆
0x3eb00…3ec00 (62, 0, 11) Sector 3e0cff00047241 ┆> rAem for later manipulation. The actual effects depend on the transaction type in progress. Pre-emption is carried out by the Function Manager upon detection of the presence of an element in the Flash precedence queue. If the terminal is in i┆
0x3ec00…3ed00 (62, 0, 12) Sector 3e0dff00047241 ┆> rAnteractive mode, the pre-emption will take place as described above in 3), the pre-emption of the Dialogue Manager having the same effect as the suspend function. If the terminal is in receive mode, the printing action will be stopped (analogue to ┆
0x3ed00…3ee00 (62, 0, 13) Sector 3e0eff00047241 ┆> rAcancel), and the Print/Display Manager ordered to Print/Display the information of Flash precedence. 5.13.1.2.13 Dialogue Manager - User Functions The Dialogue Manager monitors the dialogue with the user, i.e. guides the user in entering parame┆
0x3ee00…3ef00 (62, 0, 14) Sector 3e0fff00047241 ┆> rAters etc. in the correct sequence. The Dialogue Manager makes syntactic and semantic checks on entered information. These checks may require look-up in system tables by the Table Managemment Package. The Dialogue Manager collects parts of stati┆
0x3ef00…3f000 (62, 0, 15) Sector 3e00ff00047241 ┆> rAstics and log information required. 5.13.1.2.14 Print Manager - User Functions The Print/Display Manager controls print on printer and display on VDU of messages, comments and various control information. Print/Display is performed under direc┆
0x3f000…3f100 (63, 0, 0) Sector 3f01ff00047241 ┆? rA Transaction-ids and document control numbers are fetched and assigned by the Function Manager. 5) Statistics and log submission to collecting packages. When the Function Manager initiates a command/procedure a record for statistics colle┆
0x3f100…3f200 (63, 0, 1) Sector 3f02ff00047241 ┆? rAction and for log collection are created. For the created statistics record the contents may be supplied by the Function Manager alone or by the Function Manager and the Dialogue Manager depending on the characteristics of the transaction in pro┆
0x3f200…3f300 (63, 0, 2) Sector 3f030d00047241 ┆? rAgress. following main tasks: - Command/procedure initiation and termination - Submission of prepared information to the CAMPS system. e main difference is that upon entry of the retrieve key a retrieve command is issued to the Storage and Retr┆
0x3f300…3f400 (63, 0, 3) Sector 3f04ff00047241 ┆? rA 1 For the created log record the contents may be supplied by the Function Manager alone, by the Function Manager and the Dialogue Manager, or by the Function Manager, the Dialogue ┆
0x3f400…3f500 (63, 0, 4) Sector 3f05ff00047241 ┆? rAManager, and the Terminal Monitoring and Control Software (SS&C subsystem) depending on the characteristics of the transaction in progress. The Statistics information is communicated to the Statistics package via the CAMPS System Functions by th┆
0x3f500…3f600 (63, 0, 5) Sector 3f06ff00047241 ┆? rAe Function Manager upon completion of a transaction. Log information is communicated to the Log and Accountability package via the CAMPS System Functions by the Function Manager upon initiation and/or completion of a transaction as required for ┆
0x3f600…3f700 (63, 0, 6) Sector 3f07ff00047241 ┆? rAthe transaction type. 6) Terminal Status Function The Function Manager is responsible for monitoring the terminal control information and the display of it at the top of the VDU. 7) Cancel, Suspend, Preemption Cancel, suspend and preem┆
0x3f700…3f800 (63, 0, 7) Sector 3e08ff00047241 ┆> rAption commands are executed under the control of the Function Manager. A Cancel request may be issued by the operator. The interpretation of the Cancel command depends on the activity in progress. The effect of depressing the Cancel key whe┆
0x3f800…3f900 (63, 0, 8) Sector 3f09ff00047241 ┆? rAte CAMPS system in the latter case a command is queued. The Function Manager now await entry of the next user command. If the Dialogue Manager during performance of its task needs access to a message, command or alike this access is requeste┆
0x3f900…3fa00 (63, 0, 9) Sector 3f0aff00047241 ┆? rAd through the Function Manager with an indication, that control is wanted again after access to the information has been granted. 2) Delivery queue management and scheduling. The Function Manager monitors the queues associated with the termin┆
0x3fa00…3fb00 (63, 0, 10) Sector 3f0b7800047241 ┆? x rAal position. There is one queue for each precedence level and one queue for reception of requested information. Function. The Print/Display Manager controls print-out. It is activated by the Function Manager, directing it from which queue the o┆
0x3fb00…3fc00 (63, 0, 11) Sector 3f0cff00047241 ┆? rA 1 The Function Manager scans the queues in order of precedence and associates a transaction id with the fetched information. Then control is transferred to the Print/Display Manag┆
0x3fc00…3fd00 (63, 0, 12) Sector 3f0dff00047241 ┆? rAer for print or display of the information. 3) Terminal mode control The Function Manager monitors the terminal mode, and performs its task in accordance with the current mode. When operating in interactive mode the only delivery queue sc┆
0x3fd00…3fe00 (63, 0, 13) Sector 3f0eff00047241 ┆? rAanned is the Flash queue. If a queue element arrives in this queue the Function Manager checks if preemption of the Dialogue Manager is required, this will be the case if the task of the Dialogue Manager is of lower precedence than Flash. If preem┆
0x3fe00…3ff00 (63, 0, 14) Sector 3f0fff00047241 ┆? rAption is required the Dialogue Manager is preempted and the terminal forced into receive mode. When operating in receive mode the only events from the operator the Function Manager serves are the depressing of either of the two function keys Can┆
0x3ff00…40000 (63, 0, 15) Sector 3f00ff00047241 ┆? rAcel or Suspend. The printing action in cause will be stopped (if not of Flash precedence), the information under print staying in its delivery queue and the terminal forced into interactive mode. 4) Transaction-id and document control number.┆
0x40000…40100 (64, 0, 0) Sector 4001ff00047241 ┆@ rAhe information. 5.13.1.2.12 Function Manager - User Functions a) The term User Functions covers the three types of user functions: Preparation, Reception, and Release. Any subset of this set may be assigned to a terminal position and an opera┆
0x40100…40200 (64, 0, 1) Sector 4002ff00047241 ┆@ rAtor by the supervisor (refer fig. 5.12.1.2.12-3). The three types of user functions do not diverge too much from each other with respect to the general requirement and thus they are treated in common in this description. b) The Function Manager h┆
0x40200…40300 (64, 0, 2) Sector 40039200047241 ┆@ rAas the following main tasks: - Command/procedure initiation and termination - Submission of prepared information to the CAMPS system. e main difference is that upon entry of the retrieve key a retrieve command is issued to the Storage and Retr┆
0x40300…40400 (64, 0, 3) Sector 40049d00047241 ┆@ rA 1 Fig. 5.13.1.2.12-1 User Functions ing the command parameters in the correct sequence. The Dialogue Manager performs the required sy┆
0x40400…40500 (64, 0, 4) Sector 4005ff00047241 ┆@ rA 1 - Delivery queue management and scheduling - Terminal mode control - Transaction id and document control number - Statistics and log to collecting packages - Terminal ┆
0x40500…40600 (64, 0, 5) Sector 4006ff00047241 ┆@ rAstatus function - Cancel, suspend, preemption. 1) Command/procedure initiation and termination. Upon entry of a command code the Function Manager checks the entered command code against an internally held command table. If the command cod┆
0x40600…40700 (64, 0, 6) Sector 4007ff00047241 ┆@ rAe is found a transaction id is assigned and control is transferred to the Dialogue Manager. When the Dialogue Manager has finished a command/procedure control is transferred back to the Function Manager together with an instruction list informin┆
0x40700…40800 (64, 0, 7) Sector 3f08ff00047241 ┆? rAg the Function Manager either what to do with generated information (e.g. a prepared message) or to request some information from the CAMPS system (e.g. a retrieve request). In the first case the generated information is queued for the appropria┆
0x40800…40900 (64, 0, 8) Sector 4009ff00047241 ┆@ rAand is MSQ the Function Manager fetches the next message queued for message service, and transfers control to the Print/Display Manager, which displays the message and returns control. Control is now transferred to the Dialogue Manager. When contr┆
0x40900…40a00 (64, 0, 9) Sector 400aff00047241 ┆@ rAol is returned to the Function Manager the MSO has entered his corrections, and these have been validated (and transferred into an internal form). The Function Manager now executes the entered command which may be: print-out of message at associate┆
0x40a00…40b00 (64, 0, 10) Sector 400b5e00047241 ┆@ ^ rAd printer, queue for local distribution, queue for renewed incoming message processing. play Manager - Supervisor Function. The Print/Display Manager controls print-out. It is activated by the Function Manager, directing it from which queue the o┆
0x40b00…40c00 (64, 0, 11) Sector 400ca600047241 ┆@ & rA 1 Fig. 5.13.1.2.9-1 Message Service Function print-format. If the print action shall be preceded by a "bell" the Print/Display Manag┆
0x40c00…40d00 (64, 0, 12) Sector 400dff00047241 ┆@ rA 1 5.13.1.2.10 Dialogue Manager - MSO Function The Dialogue Manager monitors the dialogue with the MSO, i.e. guides the MSO in entering the command parameters in the correct sequence┆
0x40d00…40e00 (64, 0, 13) Sector 400eff00047241 ┆@ rA. The Dialogue Manager performs the required syntax check on the entered parameters and builds up an internal representation of entered corrections and/or commands. After entry of all parameters control is transferred to the Function Manager. 5.┆
0x40e00…40f00 (64, 0, 14) Sector 400fff00047241 ┆@ rA13.1.2.11 Print/Display Manager - MSO Function The Print/Display Manager controls printout on the printer at the MSO terminal position. Upon request after a printout from the MSO the Function Manager transfers control to the Print/Display Manage┆
0x40f00…41000 (64, 0, 15) Sector 4000ff00047241 ┆@ rAr for printout. Depending on the type of message/output the Print/Display Manager fetches a system Print control number and a special handling control number and prints out the information under direction of the format descriptor associated with t┆
0x41000…41100 (65, 0, 0) Sector 4101ee00047241 ┆A n rAFunction Manager in validated form. If output on own printer is specified the Print/Display Manager is activated. If output on PTP or distribution are commanded the message is queued to the PTP and/or distribution, respectively. e. In any case a┆
0x41100…41200 (65, 0, 1) Sector 41029b00047241 ┆A rA 1 Fig. 5.13.1.2.6-1 MDCO Function e command completion code received from the executing package. or internally will by the Function Ma┆
0x41200…41300 (65, 0, 2) Sector 4103ff00047241 ┆A rA 1 The RDI command (Retrieve for local distribution) is treated alike. The main difference is that upon entry of the retrieve key a retrieve command is issued to the Storage and Retr┆
0x41300…41400 (65, 0, 3) Sector 4104ff00047241 ┆A rAieval package. 5.13.1.2.7 Dialogue Manager - MDCO Function The Dialogue Manager monitors the dialogue with the MDCO, i.e. guides the MDCO in entering the command parameters in the correct sequence. The Dialogue Manager performs the required sy┆
0x41400…41500 (65, 0, 4) Sector 4105ff00047241 ┆A rAntax check on the entered parameter and builds up an internal representation of entered corrections and/or commands. After entry of all parameters control is transferred to the Function Manager. 5.13.1.2.8 Print/Display Manager - MDCO Function ┆
0x41500…41600 (65, 0, 5) Sector 4106ff00047241 ┆A rA The Print/Display Manager controls print-out on the printer at the MDCO terminal position. Upon request after a print-out from the MDCO the Function Manager transfers control to the Print/Display Manager for printout. Depending on the type of mes┆
0x41600…41700 (65, 0, 6) Sector 4107e400047241 ┆A d rAsage/output the Print/Display Manager fetches a system Print control number and a special handling control number and prints out the information under direction of the format descriptor associated with the information. nt queues in order of prece┆
0x41700…41800 (65, 0, 7) Sector 4008ff00047241 ┆@ rA 1 5.13.1.2.9 Function Manager - MSO Function The Function Manager checks the entered command code against an internally held command table. (Refer fig. 5.13.1.2.9-1). If the comm┆
0x41800…41900 (65, 0, 8) Sector 4109ff00047241 ┆A rAogue Manager monitors the dialogue with the supervisor, i.e. guide the supervisor in entering the command/procedure parameters in the right sequence. The Dialogue Manager performs the required syntax and semantic checks on entered parameters and in┆
0x41900…41a00 (65, 0, 9) Sector 410add00047241 ┆A ] rAforms the supervisor accordingly. Upon entry of a complete and valid command/procedure control is transferered to the Function Manager together with the internal representation of the entered command/procedure. ation of the terminal position as ┆
0x41a00…41b00 (65, 0, 10) Sector 410bff00047241 ┆A rA 1 5.13.1.2.5 Print/Display Manager - Supervisor Function. The Print/Display Manager controls print-out. It is activated by the Function Manager, directing it from which queue the o┆
0x41b00…41c00 (65, 0, 11) Sector 410cff00047241 ┆A rAutput to be printed shall be taken. The Print/Display Manager checks up the type of the print-out and prints the information under direction of the associated print-format. If the print action shall be preceded by a "bell" the Print/Display Manag┆
0x41c00…41d00 (65, 0, 12) Sector 410dff00047241 ┆A rAer is responsible for this. Upon completion of the print-action which may involve print-out of one or more queue elements the Print/Display Manager returns to the idle state and reports this state to the Function Manager. 5.13.1.2.6 Function Man┆
0x41d00…41e00 (65, 0, 13) Sector 410eff00047241 ┆A rAager - MDCO Function The Function Manager upon entry of a command code checks the command code against an internally held table of commands (refer fig. 5.13.1.2.6-1). If the command is MDQ (Correction of Message for Distribution) the Function Ma┆
0x41e00…41f00 (65, 0, 14) Sector 410fff00047241 ┆A rAnager fetches the next message to be handled from the MDCO queue, displays the transaction id, and transfers control to the Dialogue Manager, after the Print/Display Manager has displayed the message. The Function Manager gets control again when t┆
0x41f00…42000 (65, 0, 15) Sector 4100ff00047241 ┆A rAhe MDCO has finished his corrections and these have been syntax validated. From the Dialogue Manager the applied corrections together with commands for further treatment, i.e. output on PTP, output on own printer, distribution, are handed to the ┆
0x42000…42100 (66, 0, 0) Sector 4201ff00047241 ┆B rA 1 7) If the command is of the type "Command Control" or "Print Control" it is executed by the Function Manager, otherwise the command is queued to the proper package. In any case a┆
0x42100…42200 (66, 0, 1) Sector 4202da00047241 ┆B Z rA command completion report is created, after command execution and queued for printout at the report printer. The completion report is based upon the command completion code received from the executing package. or internally will by the Function Ma┆
0x42200…42300 (66, 0, 2) Sector 4203a800047241 ┆B ( rA 1 Fig. 5.13.1.2.3-1 CAMPS Supervisor Functions ordination or released). oring. 4) Terminal IF Software constitutes the interface t┆
0x42300…42400 (66, 0, 3) Sector 4204a500047241 ┆B % rA 1 Fig. 5.13.1.2.3-2 Supervisor Print Queues e performance of tasks initiated by the operator and system by scheduling the activities o┆
0x42400…42500 (66, 0, 4) Sector 4205ff00047241 ┆B rA 1 c) Scanning of Print Queues The supervisor position may be equipped with one or more (max. four) printers. Activities on a printer are controlled by a Print/Display Manager. ┆
0x42500…42600 (66, 0, 5) Sector 4206ff00047241 ┆B rAThe Function Manager has a table connecting to each printer the information type to the printed at that printer. Four types of information to be printed at the supervisor position has been defined: 1) Supervisor Print 2) Report Print 3) St┆
0x42600…42700 (66, 0, 6) Sector 4207ff00047241 ┆B rAatistics print 4) Log Print. The print types above are listed in the order of precedence. One or more print types may be assigned to one printer by the supervisor. The Function Manager scans the appropriate print queues in order of prece┆
0x42700…42800 (66, 0, 7) Sector 4108ff00047241 ┆A rAdence, when a Print/Display Manager report itself to be idle. If any non empty queue is found the Function Manager activates the Print/Display Manager for printout of the information. 5.13.1.2.4 Dialogue Manager - Supervisor Functions The Dial┆
0x42800…42900 (66, 0, 8) Sector 4209ff00047241 ┆B rAon VDU's. Print/display is performed under direction of a format descriptor for the information to be printed, and under direction of a destination descriptor indicating the device where the information shall be printed/displayed. e) Terminal IF ┆
0x42900…42a00 (66, 0, 9) Sector 420a9a00047241 ┆B rASoftware The Terminal IF Software has the tasks of implementing high level features for access to devices not covered by IO control Software. e activated with access rights and information of hardware configuration of the terminal position as ┆
0x42a00…42b00 (66, 0, 10) Sector 420bff00047241 ┆B rA 1 5.13.1.2.3 Function Manager - Supervisor Functions a) The Function Manager performs in principle two tasks in parallel. 1) Treatment of commands 2) Scanning of print queues ┆
0x42b00…42c00 (66, 0, 11) Sector 420cff00047241 ┆B rArefer fig. 5.13.1.2.3-1 and fig. 5.13.1.2.3-2 b) Treatment of commands 1) Upon entry of a command code from the supervisor, the Function Manager checks if the command code entered is valid by looking up the entered command in its command table.┆
0x42c00…42d00 (66, 0, 12) Sector 420dff00047241 ┆B rA If the command code entered is a mnemonic the full command code is displayed. Detection of a valid command code will cause control to be transferred to the Dialogue Manager. 2) When the Function Manager gets control again a syntactic and seman┆
0x42d00…42e00 (66, 0, 13) Sector 420eff00047241 ┆B rAtic correct command has been entered. The Function Manager checks if the command is protected in which case it awaits the input of the Permissive Entry Code (PEC). 3) The Function Manager checks if the command is one of those with restrictive ef┆
0x42e00…42f00 (66, 0, 14) Sector 420fff00047241 ┆B rAfect in which case the appropriate text is displayed. 4) The Function Manager now awaits either the confirmation code or a cancel. 5) In case a cancel request is received the entered command is deleted and the Function Manager awaits input of ┆
0x42f00…43000 (66, 0, 15) Sector 4200c900047241 ┆B I rAthe next supervisor command. 6) If the confirmation code is received the transaction id is displayed and a command utilization record created and issued to the log and accountability system. to be performed, or information accessible are wanted┆
0x43000…43100 (67, 0, 0) Sector 4301ff00047241 ┆C rA to be displayed/printed. In the first case control is transferred to the Dialogue Manager which will report back upon termination of the dialogue. In the latter case the Function Manager requests the information demanded from the appropriat┆
0x43100…43200 (67, 0, 1) Sector 4302ff00047241 ┆C rAe package and transfers control to the Print/Display Manager for output of the demanded information. 2) Delivery queuing and scheduling. Any message which shall be distributed/redistributed externally and/or internally will by the Function Ma┆
0x43200…43300 (67, 0, 2) Sector 4303c200047241 ┆C B rAnager be queued in the appropriate Traffic Handling or Message Distribution queue. (E.g. messages reentered by the MDCO or MSO, Messages prepared and sent for coordination or released). oring. 4) Terminal IF Software constitutes the interface t┆
0x43300…43400 (67, 0, 3) Sector 4304ff00047241 ┆C rA 1 The Function Manager controls the activities at the terminal positions, i.e. controls the performance of tasks initiated by the operator and system by scheduling the activities o┆
0x43400…43500 (67, 0, 4) Sector 4305ff00047241 ┆C rAf the Dialogue Manager and Print/Display Manager. 3) Log/Statistics information is collected by the Function Manager and reported to the accountability system, as well as all administrative information such as transaction id's is maintained by th┆
0x43500…43600 (67, 0, 5) Sector 4306ff00047241 ┆C rAe Function Manager. 4) Terminal Control information is maintained and collected by the Function Manager as well as the constant display of part of this information. c) Dialogue Manager. The dialogue Manager performs the dialogue with the ter┆
0x43600…43700 (67, 0, 6) Sector 4307ff00047241 ┆C rAminal operator under direction of a format descriptor for the dialogue. The format descriptor describes the flowgram for the format, the validity checks to be performed on the entered fields and the position within the message/table/command where t┆
0x43700…43800 (67, 0, 7) Sector 4208ff00047241 ┆B rAhe validated fields shall be stored. Validity checks include field type check, field width check, table look-up (if necessary) and some semantic checks. d) Print/Display Manager The Print/Display Manager controls print on printers and display ┆
0x43800…43900 (67, 0, 8) Sector 4309ff00047241 ┆C rA 1 5.13.1.2 Package Functions 5.13.1.2.1 Activation/Deactivation a) Each manned terminal position is serviced by a Function Manager, Dialogue Manager, and a Print/Display Manager ┆
0x43900…43a00 (67, 0, 9) Sector 430aff00047241 ┆C rAdedicated exclusively to that terminal position. b) The three Managers are activated by the SS&C software, Terminal monitoring and control, and are activated with access rights and information of hardware configuration of the terminal position as ┆
0x43a00…43b00 (67, 0, 10) Sector 430bff00047241 ┆C rAdetermined by Terminal monitoring and control. c) Access rights include which CAMPS functions may be performed by the operator at that terminal position, and which may be one or more of the following 1) Supervisor Functions 2) MDCO Functions┆
0x43b00…43c00 (67, 0, 11) Sector 430cff00047241 ┆C rA 3) MSO Functions 4) Release Functions 5) Reception Functions 6) Preparation Functions d) Each of the above groups of functions further implies the access right to certain queues and/or system tables. e) The three Managers may be dea┆
0x43c00…43d00 (67, 0, 12) Sector 430d8c00047241 ┆C rActivated by the Terminal Monitoring and Control software then withdrawing all access rights handed over at the time of activation. tus report and Message status 18 Transaction status report .......... 5.13.2.2.6 SS&C ....................┆
0x43d00…43e00 (67, 0, 13) Sector 430eff00047241 ┆C rA 1 5.13.1.2.2 General Mapping of Functions On Units a) This section describes the tasks of each unit in the Terminal System in general, i.e. independent of supplied access rights to ┆
0x43e00…43f00 (67, 0, 14) Sector 430fff00047241 ┆C rACAMPS functions. b) Functions Manager. The tasks of the Function Manager are the following: - Command interpretion, initiation and termination. - Delivery queuing and scheduling. - Log/statistics functions. - Terminal Status function┆
0x43f00…44000 (67, 0, 15) Sector 4300ff00047241 ┆C rAs. 1) Command interpretation, initiation and termination. Commands received by the Function Manager are analysed to an extent necessary to determine whether a function requiring a dialogue is to be performed, or information accessible are wanted┆
0x44000…44100 (68, 0, 0) Sector 4401ff00047241 ┆D rAwithin CAMPS. Presents to the user information sent by CAMPS to a terminal position. 2) Man/Machine IF Support and monitoring. b) TEP consists of the following units - Function Manager - Dialogue Manager - Print/Display Manager - T┆
0x44100…44200 (68, 0, 1) Sector 4402ff00047241 ┆D rAerminal IF Software 1) The Function Manager performs/initiates all interaction with the various packages of CAMPS and schedules the tasks of the Print/Display Manager and the Dialogue Manager. 2) The Dialogue Manager is responsible for the int┆
0x44200…44300 (68, 0, 2) Sector 4403ff00047241 ┆D rAeractive part of the Man/Machine interface support and monitoring 3) The Print/Display Manager is responsible for the man interactive part of the Man/Machine interface support and monitoring. 4) Terminal IF Software constitutes the interface t┆
0x44300…44400 (68, 0, 3) Sector 4404de00047241 ┆D ^ rAo the I/O control software making a high level interface against terminals for the rest of the Terminal package. c) The packages to which the Terminal System interfaces are 1) Kernel 2) I/O control software ages for coordination Recepti┆
0x44400…44500 (68, 0, 4) Sector 4405ff00047241 ┆D rA 1 3) CAMPS Systems Functions 4) Storage and File Management package 5) SS&C software 6) Traffic Handling 7) Distribution 8) Table Management 9) Storage and Retriev┆
0x44500…44600 (68, 0, 5) Sector 4406ff00047241 ┆D rAal 10) Log and Accountability 11) Statistics d) The Terminal package interfaces with CAMPS users and thus the following external interfaces apply. 1) Supervisor (ref. CPS/ICD/002) 2) Message Distribution Control Operator (MDCO) rer.┆
0x44600…44700 (68, 0, 6) Sector 4407b900047241 ┆D 9 rA CPS/ICD/002)- 3) Message Service Operator (MSO) ref. CPS/ICD/002) 4) Users (ref. CPS/ICD/001) e) In fig. 5.13.1.1-1 an overview of the interfaces of TEP are depicted. ............. 5.13.1.2.8 Print/Display Manager - MDCO ┆
0x44700…44800 (68, 0, 7) Sector 4308b400047241 ┆C 4 rA 1 Fig. 5.13.1.1-1 Operators: Supervisor, MDCO, MSO, Users Function ..................... 5.13.1.2.11 Print/Display ┆
0x44800…44900 (68, 0, 8) Sector 4409ff00048641 ┆D Aed. This ensures that in case of a failure or a repair the WD CPU can be removed without offlining the system. 5.4.1.2.5 VDU & LP The VDU, which includes a keyboard, and the LP are connected to thee WD via one V24 interface. By means of these d┆
0x44900…44a00 (68, 0, 9) Sector 440aff00048641 ┆D Aevices the system engineer is able to decide and execute control of the system. 5.4.1.3 Subsystem Control 5.4.1.3.1 Synchronization N.A. 5.4.1.3.2 Hardware Control Configuration control can be operated in the following ways. - Automat┆
0x44a00…44b00 (68, 0, 10) Sector 440bff00048641 ┆D Aically by the WD program - Manually by the VDU + keyboard through the WD - Manually via switches on each crate assembly indepent of the WD Built in tests in the various modules may be activated in the following way by the WD. - Manually by t┆
0x44b00…44c00 (68, 0, 11) Sector 440c4e00048641 ┆D N Ahe VDU and keyboard through the WD - Automatically by the WD program. ration or maintenance phase, see fig. 5.4.1.2.2.-1. The use of the 2 extra monitor lines is - One indicating to the WD if one or more of the seitches being out of auto. - ┆
0x44c00…44d00 (68, 0, 12) Sector 440da000048641 ┆D A 1 Fig. 5.4.1.2.5-1 Crate Configuration bus Referring to fig. 5.4.1.2.2-1. Analog Digital Digital Inputs inputs output A. M┆
0x44d00…44e00 (68, 0, 13) Sector 440eff00048641 ┆D A 1 5.4.1.3.3 Error Reporting Status of built in tests TBD. Status from the TDW controller via V24 TBD. To check the WD itself for failures, a special circuit which is completely i┆
0x44e00…44f00 (68, 0, 14) Sector 440fff00048641 ┆D Andependent of the other electronics has been developed. It is built up around a timer acting as a one shot OS in case of the retriggerable monitoring OS not receiving signal ofter enough, the WD CPU will switch over to the WPC. Upon detection of a┆
0x44f00…45000 (68, 0, 15) Sector 2300ff00048641 ┆# A failure the WD program starts an audible signal, generate a headline report on the VDU and a detailed report on the LP. 5.4.1.4 Characteristics 5.4.1.4.1 Performance The watchdog has a selctable rate from 50 to 19200 baud. - WD to PU ┆
0x45000…45100 (69, 0, 0) Sector 4501ff00048641 ┆E A 1 5.4.1.2.3 TDX Crate Assembly The control 8 monitoring of this crate is done via a BTM-Y module, which is a CCA integrated with the BTM-module. The BTM-Y assigns either the TDX B┆
0x45100…45200 (69, 0, 1) Sector 4502ff00048641 ┆E Aus # 1, TDX Bus # 2 or none to the internal crate TDX Bus. The assignment is controlled by the WD or manuel by two switched on the front panel of the BTM-Y. One of the switches is an auto/manuel switch controlling the assignment source. In auto th┆
0x45200…45300 (69, 0, 2) Sector 4503ff00048641 ┆E Ae WD is in control else the other switch gives TDX Bus # 1, TDW Bus # 2 or none connected. The WD monitors the auto/manuel switch for an auto/non auto indication. In addition to the above mentioned functions the WD also minotors the power supply┆
0x45300…45400 (69, 0, 3) Sector 4504ff00048641 ┆E A voltages in the different assemblies. CCA Functions (TDX) Summary Referring to fig. 5.4.1.2.3-1. 1 Analog Digital Digital Inputs Inputs Outputs A. Monitor supply ┆
0x45400…45500 (69, 0, 4) Sector 4505ff00048641 ┆E Avoltages (+5, +/- 12V) 3 - - B. Monitor results (wired- or) of individual self- test routines - 1 - C. 1. Controlling bus assignment - - 2 2. Monitor state of auto/ manual switch - 1 - D.* Monitor TD┆
0x45500…45600 (69, 0, 5) Sector 4506d400048641 ┆E T AX-controller status (RS, TS, FS, Col1/2 - - - E. Result of individual self- test if any - - - * In the two crates with the TDX-controllers a V 24 monitoring point is implemented. Analog Digital Digital inputs input ou┆
0x45600…45700 (69, 0, 6) Sector 45079e00048641 ┆E A 1 Fig. 5.4.1.2.3-1 A,B,C,D,E's functions - 1 2. Issue "Maintenance Mode" to the MAP - - 1 3. Monitoring the state of ┆
0x45700…45800 (69, 0, 7) Sector 4408ff00048641 ┆D A 1 5.4.1.2.4 Watchdog Self-control A fail safe circuit is implemented between the WD CPU and the WD panel controller, in case of a failure an automatic switching to manual is preform┆
0x45800…45900 (69, 0, 8) Sector 4509ff00048641 ┆E A The CCA control and monitoring path to the CU is, to improve the WD control, given on extra set of lines, e.i. 2 control and 2 monitor lines. Via the 2 control lines the WD controls the "take ownership" command as follows for all units together ┆
0x45900…45a00 (69, 0, 9) Sector 450ac200048641 ┆E B Ai.e. a) Enable via I/O Bus A, enable via I/O Bus B b) Disable via I/O Bus A, enable via I/O Bus B c) Enable via I/O Bus A, disable via I/O Bus B d) Disable via I/O Bus A, and - B Status is read back and displayed on the frontpanel of the WP┆
0x45a00…45b00 (69, 0, 10) Sector 450bff00048641 ┆E A 1 In manual mode it is possible to establish an individual connection of each of the units (i.e. diskcontroller, floppy-disk controller and LTU) by a three-state switch placed on the┆
0x45b00…45c00 (69, 0, 11) Sector 450cff00048641 ┆E A front panel of each unit. This possibility can be used during an integration or maintenance phase, see fig. 5.4.1.2.2.-1. The use of the 2 extra monitor lines is - One indicating to the WD if one or more of the seitches being out of auto. - ┆
0x45c00…45d00 (69, 0, 12) Sector 450dff00048641 ┆E AThe other monitor the results of the built in tests. CCA Functions (CU) Summary 1 Referring to fig. 5.4.1.2.2-1. Analog Digital Digital Inputs inputs output A. M┆
0x45d00…45e00 (69, 0, 13) Sector 450eff00048641 ┆E Aonitor dualized supply voltages (+5, +/- 12V) 6 - - B. Monitor (wired-or) state of front panel switches (Auto/non auto) - 1 - C. Controlling "Take owner- ship" - enable/disable - - 2 D. Monitors card self-test ┆
0x45e00…45f00 (69, 0, 14) Sector 450f5a00048641 ┆E Z A results (wired-or) - 1 - E. Individual self-test results - - - TDX RACK 5.4.1.1.3 External Interfaces None. 0 02 14 09 01 81 20 22 12 01 81 15 49 0035A 15 2 37 164 11453 Q f ! *J 8 : _┆
0x45f00…46000 (69, 0, 15) Sector 45009c00048641 ┆E A 1 Fig. 5.4.1.2.2-1 A,B,C,D's functions depiced on fig. 5.4.1.1.4 -1. 5.4.1.2 Subsystem Functions This section describes how the WD vi┆
0x46000…46100 (70, 0, 0) Sector 4601ff00048641 ┆F Aa V24 CCA's and BTM-Y's controls and monitors the different types of assemblies within the CAMPS system. a) Processor Unit Assembly b) Channel Unit Assembly c) TDX Crate Assembly 5.4.1.2.1 Processor Unit Assembly The monitoring and contro┆
0x46100…46200 (70, 0, 1) Sector 4602ff00048641 ┆F Al of the two PU's is done through. - 2 x V24 interface - Crate Configuration Bus The PU's send status and "alive" messages to the watchdog via the 2 x V24 lines. The monitoring and control of switches and voltages is done via the serial Conf┆
0x46200…46300 (70, 0, 2) Sector 4603d100048641 ┆F Q Aiguration bus and the CCA. ref. fig. 5.4.1.2.1. The frontpanel of the MAP includes an auto/manual switch which controls the connect/disconnets state of the MIA and the 2 TIA's. (Ref. fig. 5.4.1.2.1-1).! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x46300…46400 (70, 0, 3) Sector 46048900048641 ┆F A 1 Fig. 5.4.1.1.4-1 system Description 5.4.1.1.1 General Description Themain feature of the watchdog HW packages is to enable monitor┆
0x46400…46500 (70, 0, 4) Sector 4605b600048641 ┆F 6 A 1 Fig. 5.4.1.2.1-1 A,B,E, F's functions are described overleaf. of hardware - Control physical device allocation e.g. isolate a HW devi┆
0x46500…46600 (70, 0, 5) Sector 4606ff00048641 ┆F A 1 CCA Functions (PU) Summary Referring to fig. 5.4.1.2.1-1. 1 Analog Digital Digital inputs input ou┆
0x46600…46700 (70, 0, 6) Sector 4607ff00048641 ┆F Atput A. Supervision of analog voltages (+5, +/- 12V) 3 - - B. 1. Controllong the connect/ disconnect state of the MIA + TIA's - - 1 2. Issue "Maintenance Mode" to the MAP - - 1 3. Monitoring the state of ┆
0x46700…46800 (70, 0, 7) Sector 4508ff00048641 ┆E A the auto/manuel switch - 1 - E. Individual selftest results - - - F. Issue "Master Clear" command to the MAP - - 1 1 5.4.1.2.2 Channel Unit Assembly ┆
0x46800…46900 (70, 0, 8) Sector 4609ff00048641 ┆F A 1 The WCA also contains a failsafe circuit, which in case of a failure in the WD CPU, will switch over to the WPC, the system is hereby in manual mode. The WPC contains of a single┆
0x46900…46a00 (70, 0, 9) Sector 460aff00048641 ┆F A chip processor, which major task is to scan the switches set on its frontpanel and convey the settings to the CCA's and BTM-Y's via the configuration bus, using PAM serial communication. Status is read back and displayed on the frontpanel of the WP┆
0x46a00…46b00 (70, 0, 10) Sector 460bff00048641 ┆F AC. In CAMPS the WPC is not used so, in manual mode no monitoring or control is performed, and isolation of a physical device has to be done in the crates via manual switches. The reason for not using the WPC facility is to avoid, that in the case ┆
0x46b00…46c00 (70, 0, 11) Sector 460cff00048641 ┆F Athe engineer has forgotten to update the switches on the frontpanel, we will have a wrong configuration if the WD CPU fails. The CCA contains 1 PAM circuit, 1 A10 converter and a number of multiplexed latches. The PAM circuit is an addressable asy┆
0x46c00…46d00 (70, 0, 12) Sector 460dff00048641 ┆F Anchronous receiver and transmitter. Via the configuration bus it receives two eleven-bit word in a serial data stream. The first of the incoming words contains the PAM address and if the address matches, the PAM will receive the next eleven-bit data┆
0x46d00…46e00 (70, 0, 13) Sector 460eff00048641 ┆F A word. This word is used as a pointer to the latch you want to control or monitor. The PAM will after receipt of the second word, transmit back status of the latch in two eleven-bit words. Each of the transmitted words contains eight data bits, even┆
0x46e00…46f00 (70, 0, 14) Sector 460f9000048641 ┆F A parity bit, start and stop bit. 5.4.1.1.2 Reference to other Subsystem CR80D TDX RACK 5.4.1.1.3 External Interfaces None. 0 02 14 09 01 81 20 22 12 01 81 15 49 0035A 15 2 37 164 11453 Q f ! *J 8 : _┆
0x46f00…47000 (70, 0, 15) Sector 4600ff00048641 ┆F A 1 5.4.1.1.4 Blockdiagram A blockdiagram showing the interfaces of this package is depiced on fig. 5.4.1.1.4 -1. 5.4.1.2 Subsystem Functions This section describes how the WD vi┆
0x47000…47100 (71, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(71,0, 1), len=0xff, h3=41048641}, f00=»0486A «, f01=»CPS/SDS/001 system design «, f02=»am] «, f03=»BHJ «, f04=»kap. 5.4 «, f05=09-01-81 13:00, f06=» 2 «, f07=»35 «, f08=» 11422 «, f09=09-01-81 20:20, f10=» «, f11=»02 «, f12=» 14 «, f13=09-01-81 20:22, f14=12-01-81 15:49, f15=»0035A «, f16=» 15 «, f17=» 2 «, f18=»37 «, f19=» 164 «, f20=» 11453 «, f21=» «, f22=» «, f99=510010000110056610a10a80aaca15050000000000000038033900df}
0x47100…47200 (71, 0, 1) Sector 47020f00048641 ┆G A G G F F F F F E E E E E D D # " DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG┆
0x47200…47300 (71, 0, 2) Sector 47039f00048641 ┆G A 1 CPS/SDS/001 BHJ/800115 CAMPS SYSTEM 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┆
0x47300…47400 (71, 0, 3) Sector 4704ff00048641 ┆G A 1 5.4 WATCHDOG HW 5.4.1 Summary of Requirements 5.4.1.1 Subsystem Description 5.4.1.1.1 General Description Themain feature of the watchdog HW packages is to enable monitor┆
0x47400…47500 (71, 0, 4) Sector 4705ff00048641 ┆G Aing and controlling of correct configuration in the CAMPS system: - Receive error reports from the PU's - Receive "keep alive" messages from the PU's - Monitoring status of hardware - Control physical device allocation e.g. isolate a HW devi┆
0x47500…47600 (71, 0, 5) Sector 4706ff00048641 ┆G Ace - Determine a switchover in case of a PU failure The WD consists of 4 major components: - Watchdog CPU (WPU) - Watchdog CPU adaptor (WCA) - watchdog panel controller (WPC) - Crate configuration adaptor (CCA) ┆
0x47600…47700 (71, 0, 6) Sector 4707ff00048641 ┆G AThe WPU is a standard LTU which boots its program from an EPROM located on the WCA. 4 x V24 parts ensure the WD capability of interfacing e.g. 2 PU, 1 VDU and 1 LP. The WPU communicates with the CCA's, BTM-Y's and WPC through a 16 p flotcable conf┆
0x47700…47800 (71, 0, 7) Sector 46085d00048641 ┆F ] Aiguration bus, which uses a serial communication based on the single chip PAM system. /M?.I*:="8=IM2&MP'Mc2! m"2< [MI !?=6 : #wI>K!8=>R 2!8=6 #4 E*8=k L<M% :8=F 28=I!#<:"<>R<2> I E*#<& "< DM L<M% :#<F 2#<> I:g= Ro2M/2 Rl2> IC13!?=4~~ B|2> I:A=!┆
0x47800…47900 (71, 0, 8) Sector 4709ff00047241 ┆G rA 1 Legend for fig. 5.13.1-1 on previous page 1 Messages rejected during ACP127 analysis, i.e. messages for Message service. 2 Service messages prepared by supervisor and messages ┆
0x47900…47a00 (71, 0, 9) Sector 470aff00047241 ┆G rAfor rerun 3 Service messages presented to supervisor 4 Message retrieval for rerun, Message retrieval for redistribution 5 Messages to be redistributed 6 Message retrieval for redistribution 7 Message Distribution control, i.e. messages wh┆
0x47a00…47b00 (71, 0, 10) Sector 470bff00047241 ┆G rAich for some reason cannot be distributed automatically by CAMPS 8 Messages released by the release officer 9 Notification of Release and comments 10 Messages for release decision, Messages for coordination and comments 11 Message Retrieval,┆
0x47b00…47c00 (71, 0, 11) Sector 470cff00047241 ┆G rA Message Merge, Message Deletion 12 Messages sent for Release decision, Messages for coordination and comments 13 Notification of Release, Messages for coordination and comments. 14 Incoming messages and copies of outgoing messages 15 Transa┆
0x47c00…47d00 (71, 0, 12) Sector 470dca00047241 ┆G J rAction status report and Release Status 16 Log of transactions for respective Release, Preparation and Reception 17 Transaction status report and Message status 18 Transaction status report .......... 5.13.2.2.6 SS&C ....................┆
0x47d00…47e00 (71, 0, 13) Sector 470eff00047241 ┆G rA 1 19 Statistics information delivery for respectively Release, Preparation and Reception. 20 Log of transactions for respectively Message Service, Supervisor and MDCO 21 Trace of┆
0x47e00…47f00 (71, 0, 14) Sector 470f2400047241 ┆G $ rA Log 22 Statistics delivery 5.13 TERMINAL SYSTEM 5.13.1 Summary of Requirements a) The Terminal System constitutes the only means by which users may get access to the services of the CAMPS system. The se┆
0x47f00…48000 (71, 0, 15) Sector 4400ff00047241 ┆D rA 1 5.13.1.1 Package Description a) The Terminal Package performs the following tasks: 1) Interfaces the user to the CAMPS System, i.e. direct user input to the relevant subsystem ┆
0x48000…48100 (72, 0, 0) Sector 4801ff00047241 ┆H rA Device Control User Profile Update Security Control Access Control at Restart Table Update Abbreviated Service Message Queue Access Retrieval ACP 127 parameter control Message distribution control Engineering┆
0x48100…48200 (72, 0, 1) Sector 48021200047241 ┆H rA function. ┆
0x48200…48300 (72, 0, 2) Sector 4803ff00047241 ┆H rA 1 2) Message Distribution Control Function Local Distribution assignment Alternative Distribution assignment Redistribution Message Service Function Garble Corre┆
0x48300…48400 (72, 0, 3) Sector 4804ff00047241 ┆H rAction RI Assignment Relay Determination Operating Signals Assignment Group Count Verification 3) Preparation Function Message/Comment preparation Retrieval Deletion Reception of Mesages for coordination Recepti┆
0x48400…48500 (72, 0, 4) Sector 4805bf00047241 ┆H ? rAon of Comments Reception of notifications of release Status 4) Reception function Reception of incoming messages Reception of copies of outgoing messages Status of Function into Units .................. 5.13.┆
0x48500…48600 (72, 0, 5) Sector 4806ff00047241 ┆H rA 1 5) Release function Comment preparation and reception Reception of messages for coordination Release of messages sent for release decision Status. b) In fig. 5.1┆
0x48600…48700 (72, 0, 6) Sector 48078e00047241 ┆H rA3.1-1 the information flow between the CAMPS functions implemented by the Terminal package and the other packages of CAMPS is depicted. er - MDCO Function .................... 5.13.1.2.8 Print/Display Manager - MDCO ┆
0x48700…48800 (72, 0, 7) Sector 47089800047241 ┆G rA 1 Fig. 5.13.1-1 Terminal System Dialogue Manager - MSO Function ..................... 5.13.1.2.11 Print/Display ┆
0x48800…48900 (72, 0, 8) Sector 4809ff00047241 ┆H rAManager MSO Function ................. 5.13.1.2.12 Function Manager - User Functions .................... 5.13.1.2.13 Dialogue Manager - User Functions .................... 5.13.1.2.1┆
0x48900…48a00 (72, 0, 9) Sector 480aff00047241 ┆H rA4 Print/Display Manager - User Functions 5.13.1.2.15 Recovery Functions ........... 5.13.1.2.16 Special Devices .............. 5.13.1.3 Subsystem Control ................ 5.13.1.4 Characteristics ...............┆
0x48a00…48b00 (72, 0, 10) Sector 480b6d00047241 ┆H m rA... 5.13.1.5 Design and Construction .......... 5.13.1.6 Documentation .................... r4IMM.:^=~ B}5I:g=~ J 5IC$3I > S C_* ┆
0x48b00…48c00 (72, 0, 11) Sector 480cff00047241 ┆H rA 1 5.13.2 Environment .......................... 5.13.2.1 External Interfaces .............. 5.13.2.2 Subsystem Interfaces ............. 5.13.2.2.1 Traffic Handling┆
0x48c00…48d00 (72, 0, 12) Sector 480dff00047241 ┆H rA ............. 5.13.2.2.2 Distribution ................. 5.13.2.2.3 Storage and Retrieval ........ 5.13.2.2.4 Logging ...................... 5.13.2.2.5 Statistic .................... 5.13.2.2.6 SS&C ....................┆
0x48d00…48e00 (72, 0, 13) Sector 480e3d00047241 ┆H = rA..... 5.13.2.2.7 Table Management ............. ┆
0x48e00…48f00 (72, 0, 14) Sector 480fff00047241 ┆H rA 1 5.13 TERMINAL SYSTEM 5.13.1 Summary of Requirements a) The Terminal System constitutes the only means by which users may get access to the services of the CAMPS system. The se┆
0x48f00…49000 (72, 0, 15) Sector 4800ff00047241 ┆H rArvices in question are listed below: - Supervisor Functions - Message Distribution Control Functions - Message Service Functions - User Functions, i.e. Preparation, Reception and Release. 1) Supervisor Function Command Control ┆
0x49000…49100 (73, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(73,0, 1), len=0xff, h3=41047241}, f00=»0472A «, f01=»CPS Sys Design Spec. «, f02=»kk/sdv «, f03=»MSN «, f04=»CPS/SDS/001 5.13 «, f05=06-01-81 11:00, f06=» 9 «, f07=»10 «, f08=» 45598 «, f09=13-01-81 15:22, f10=» «, f11=»12 «, f12=» 180 «, f13=13-01-81 13:22, f14=13-01-81 16:44, f15=»0035A «, f16=» 61 «, f17=» 14 «, f18=»05 «, f19=» 760 «, f20=» 48914 «, f21=» «, f22=» «, f99=020010000110056610a10a80aaca1505000000000000003803d900df}
0x49100…49200 (73, 0, 1) Sector 49023d00047241 ┆I = rA I I H H H H H G G G D D C C C B B B B B A A A A @ @ @ @ ? ? > > > = = = = < < < < < < ; ; ; ; ; : : : : : : : 9 9 9 9 9 9 8 DOKUMENTOVERSIGT Dokument nr: Dokumentnavnvn┆
0x49200…49300 (73, 0, 2) Sector 49039f00047241 ┆I rA 1 CPS/SDS/001 MSN/810115 CAMPS SYSTEM 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┆
0x49300…49400 (73, 0, 3) Sector 4904ff00047241 ┆I rA 1 1 TABLE OF CONTENTS 5.13 TERMINAL SYSTEM ......................... 5.13.1 Summary of Requirements .....┆
0x49400…49500 (73, 0, 4) Sector 4905ff00047241 ┆I rA........ 5.13.1.1 Subsystem Description ........... 5.13.1.2 Subsystem Function .............. 5.13.1.2.1 Activation/Deactivation ..... 5.13.1.2.2 General Mapping of Function into Units .................. 5.13.┆
0x49500…49600 (73, 0, 5) Sector 4906ff00047241 ┆I rA1.2.3 Function Manager - Supervisor Functions ................... 5.13.1.2.4 Dialogue Manager - Supervisor Function .................... 5.13.1.2.5 Print/Display Manager - Supervisor Fu┆
0x49600…49700 (73, 0, 6) Sector 4907ff00047241 ┆I rAnction ......... 5.13.1.2.6 Function Manager - MDCO Function .................... 5.13.1.2.7 Dialogue Manager - MDCO Function .................... 5.13.1.2.8 Print/Display Manager - MDCO ┆
0x49700…49800 (73, 0, 7) Sector 4808ff00047241 ┆H rA Function .................... 5.13.1.2.9 Function Manager - MSO Function ..................... 5.13.1.2.10 Dialogue Manager - MSO Function ..................... 5.13.1.2.11 Print/Display ┆
0x49800…49900 (73, 0, 8) Sector 00000000000000 ┆ ┆
[…0x17…]
0x4b000…4b100 (75, 0, 0) Sector ffffffffffffff ┆ ┆
0x4b100…4b200 (75, 0, 1) Sector 00000000000000 ┆ ┆
[…0x1e…]
