OctetView
0x00000…00100 (0, 0, 0) Sector 01134130313133 ┆ A0113A ┆
0x00100…00200 (0, 0, 1) Sector 00000000000000 ┆ ┆
0x00200…00300 (0, 0, 2) Sector ff00c0fffcffff ┆ @ | ` ┆
0x00300…00306 (0, 0, 3) WangDocument {d00=0x15, d01=0x58, d02=0x41, ptr=(20,0, 8), d05=0x00}
0x00306…0030c WangDocument {d00=0x15, d01=0x61, d02=0x41, ptr=(29,0, 0), d05=0x00}
0x0030c…00312 WangDocument {d00=0x15, d01=0x64, d02=0x41, ptr=(38,0, 0), d05=0x00}
0x00312…00318 WangDocument {d00=0x15, d01=0x69, d02=0x41, ptr=(72,0, 0), d05=0x00}
0x00318…0031e WangDocument {d00=0x15, d01=0x75, d02=0x41, ptr=(67,0, 0), d05=0x00}
0x0031e…00320 00 00 ┆ ┆
0x00320…00340 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ ┆
[…0x5…]
0x003e0…00400 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1e ┆ ┆
0x00400…00500 (0, 0, 4) Sector 00000000000000 ┆ ┆
0x00500…00600 (0, 0, 5) Sector 86312020202020 ┆ 1 8 7 Q? > 7 d N ~<) 0uH &4'>( 1c5 & & ┆
0x00600…00700 (0, 0, 6) Sector 421c402600415b ┆B @& A[' X% % PO P ; uA 2 C g x g V W O 7 :/@ /CH a 1575A g I < {C < { ; 5 ?v x ?vT ?vq 8 : 9 xyyg /C/D/F ┆
0x00700…00800 (0, 0, 7) Sector 00000000000000 ┆ ┆
[…0x8…]
0x01000…01100 (1, 0, 0) WangDocumentBody
[…0x1…]
0x01200…01300 (1, 0, 2) Sector 00000000000000 ┆ ┆
[…0x5…]
0x01800…01900 (1, 0, 8) WangDocumentBody
[…0xd…]
0x02600…02700 (2, 0, 6) Sector 00000000000000 ┆ ┆
[…0x1…]
0x02800…02900 (2, 0, 8) WangDocumentBody
[…0x11f…]
0x14800…14900 (20, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(20,0, 9), len=0xff, h3=41155841}, f00=»1558A «, f01=»CPS/SDS/039 «, f02=»pn/rt/sdv «, f03=»BBC «, f04=»Fra kap. 4.2.2.4 «, f05=29-12-81 09:23, f06=» 14 «, f07=»28 «, f08=» 51750 «, f09=19-03-82 09:27, f10=» «, f11=»08 «, f12=» 230 «, f13=07-01-82 11:56, f14=19-05-82 14:44, f15=»0113A «, f16=»101 «, f17=» 18 «, f18=»07 «, f19=» 812 «, f20=» 54835 «, f21=» «, f22=» «, f99=100010000110062710110480aaca15050000000000000037033201df}
0x14900…14a00 (20, 0, 9) WangDocumentBody
[…0x7…]
0x15100…15200 (21, 0, 1) Sector 1502ff00155841 ┆ XAStart-Up (1.2) Executes the function to be performed after sign-on. The command validation table reflecting the user capability is defined. c) Close-Down (1.3) This function provides the UFCO with the capability of performing the following f┆
0x15200…15300 (21, 0, 2) Sector 1503ff00155841 ┆ XAunctions: - Sign-off - Block terminal - Order close-down. d) Security Interrogation (1.4) Requests a security interrogation to be performed in case of release. Executes the functions to be performed after a security interrogation (e.g┆
0x15300…15400 (21, 0, 3) Sector 15042100155841 ┆ ! XA. receive function keys). Hvilken funktion? Til hvor? Fra hvor? Dokument: Hvilken kommando? Hvilken side: (Sletter) (S]ger) (Udf]rer) Inds`t hvilket? Slette hvilket? Flytte hvilket? Kopiere hvilket? Bytte hvilket? Bytte med? S]ge hvilket? ┆
0x15400…15500 (21, 0, 4) Sector 1505ff00155841 ┆ XA 1 4.2.2.1.2 Transaction Accounting (2.0) The transaction accounting functions are those concerning log and statistics. a) Collect Data (2.1) The data which are used for log, st┆
0x15500…15600 (21, 0, 5) Sector 1506ff00155841 ┆ XAatistics and other purposes are collected in sequence table. There exists no special collecting procedures but all data which are pertinent for UFCO will be placed in this area. b) Log Reporting (2.2) The log reporting functions are those requi┆
0x15600…15700 (21, 0, 6) Sector 1507ff00155841 ┆ XAred to report final log records. The data which are required in a log record are extracted from the sequence table. c) Statistics Reporting (2.3) The statistics reporting functions are those required to report statistics. The data which are ┆
0x15700…15800 (21, 0, 7) Sector 1408ff00155841 ┆ XArequired in the statistics are extracted from the sequence table. 4.2.2.1.3 Transaction Creation (3.0) The transaction creation group includes all the functions to be performed before a transaction may be started. a) Receive and Validate (3.1┆
0x15800…15900 (21, 0, 8) WangDocumentBody
[…0x77…]
0x1d000…1d100 (29, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(29,0, 1), len=0xff, h3=41156141}, f00=»1561A «, f01=»CPS/SDS/039 «, f02=»rt «, f03=»JBS «, f04=»Fra 4.2.3 USER VDU «, f05=29-12-81 11:28, f06=» 5 «, f07=»54 «, f08=» 23891 «, f09=07-01-82 10:32, f10=» «, f11=»22 «, f12=» 449 «, f13=07-01-82 11:58, f14=07-01-82 15:51, f15=»0113A «, f16=» 43 «, f17=» 8 «, f18=»22 «, f19=» 392 «, f20=» 25648 «, f21=» «, f22=» 0 «, f99=530010000110066610110480aaca15050000000000000037037e00df}
0x1d100…1d200 (29, 0, 1) WangDocumentBody
[…0x7…]
0x1d900…1da00 (29, 0, 9) Sector 00000000000000 ┆ ┆
[…0x6…]
0x1e000…1e100 (30, 0, 0) WangDocumentBody
[…0x7f…]
0x26000…26100 (38, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(38,0, 1), len=0xff, h3=41156441}, f00=»1564A «, f01=»USER VDU, CPS/SDS/039 «, f02=»bbh/sdv «, f03=»BBC «, f04=»FRA 4.2.3.4.5.3 «, f05=29-12-81 13:25, f06=» 7 «, f07=»55 «, f08=» 20969 «, f09=07-01-82 10:54, f10=» «, f11=»12 «, f12=» 366 «, f13=07-01-82 12:07, f14=07-01-82 15:52, f15=»0113A «, f16=» 40 «, f17=» 11 «, f18=»12 «, f19=» 468 «, f20=» 31642 «, f21=» «, f22=» 0 «, f99=930010000110066610110480aaca15050000000000000037038900df}
0x26100…26200 (38, 0, 1) WangDocumentBody
[…0x39…]
0x29b00…29c00 (41, 0, 11) Sector 290cff00156941 ┆) iA 1 PUT LOG CIF CASE WRITE VIEW (CIF WRITE SIZE, LOG CIF FIELD LIST 2, LOG CIF VIEW REF, COLLECT BUFFER.RECS) (CC): ERROR? ANALYSE ERROR (CC, O) ┆
0x29c00…29d00 (41, 0, 12) Sector 290dff00156941 ┆) iAOK? END CASE CASE SAVE VIEW (FALSE, LOG CIF VIEW REF) (CC): ERROR? ANALYSE ERROR (CC, O) OK? END CASE COLLECT BUFFER.HEADER.COLL BUF INDEX = 1 Same new index value. PUT LOG DATA 10 RETURN Fi┆
0x29d00…29e00 (41, 0, 13) Sector 290e2600156941 ┆) & iAgure 4.2.1.4.1.4-9 PUT LOG CIF INITIALIZE COLL BUF INDEX = 1 CLOSE DOWN = FALSE IN Q. MAINQUEUE = SYSTEM Q IN Q. SUBQUEUE = 0 CMD Q.MAINQUEUE = SYSTEM Q CMD Q.SUBQUEUE = IN COMM Q O┆
0x29e00…29f00 (41, 0, 14) Sector 290fff00156941 ┆) iA 1 PUT LOG DATA Store COLLECT BUFFER on fast disk log file CASE MODIFYBYTES (LOG SAVE FD, LOG SAVE FILEADDRESS, COLLECT BUFFER BLE) (LOG SAVE FILEADDRESS, CC):┆
0x29f00…2a000 (41, 0, 15) Sector 29008100156941 ┆) iA ERROR? ANALYSE ERROR (CC, O) OK? END CASE Figure 4.2.1.4.1.5-10 PUT LOG DATA LN) (LOG ROOT FD, CC): ERROR? ANALYSE ERROR (CC, O) OK? END CASE CASE LOOKUP (LOG ROOT FD, LOG SAVE FIL┆
0x2a000…2a100 (42, 0, 0) WangDocumentBody
[…0x18f…]
0x43000…43100 (67, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(67,0, 1), len=0xff, h3=41157541}, f00=»1575A «, f01=»CPS/SDS/032 «, f02=»bbh «, f03=»HUH «, f04=»Fra 4.2.2 «, f05=11-01-81 09:13, f06=» 10 «, f07=»01 «, f08=» 28308 «, f09=21-11-84 14:43, f10=» «, f11=»01 «, f12=» 8 «, f13=06-05-82 15:46, f14=21-11-84 14:44, f15=»0113A «, f16=» 72 «, f17=» 26 «, f18=»25 «, f19=» 604 «, f20=» 51926 «, f21=» «, f22=» @ «, f99=240010000110066610110480aaca1505000000000000003703e100df}
0x43100…43200 (67, 0, 1) WangDocumentBody
[…0x4e…]
0x48000…48100 (72, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(72,0, 1), len=0xff, h3=41156941}, f00=»1569A «, f01=»CPS/SDS/032 «, f02=»pc «, f03=»HUH «, f04=»fra 1 «, f05=05-01-82 13:20, f06=» 5 «, f07=»35 «, f08=» 24655 «, f09=10-05-82 08:42, f10=» «, f11=»03 «, f12=» 48 «, f13=10-05-82 08:46, f14=10-05-82 10:55, f15=»0113A «, f16=» 87 «, f17=» 25 «, f18=»52 «, f19=» 1120 «, f20=» 53978 «, f21=» «, f22=» «, f99=400010000110066610110480aaca15050000000000000137034301df}
0x48100…48200 (72, 0, 1) WangDocumentBody
[…0x6…]
0x48800…48900 (72, 0, 8) Sector 4809a000157541 ┆H uA 1 Figure 4.2.2.1-2 FUNCTIONAL BREAKDOWN ┆
0x48900…48a00 (72, 0, 9) Sector 480aff00157541 ┆H uA 1 4.2.2.2 Software Structure The trace sub-package consists of one coroutine performing the function listed in section 4.2.2.1. The coroutine in the Trace sub-package consist of o┆
0x48a00…48b00 (72, 0, 10) Sector 480bff00157541 ┆H uAne software module. 4.2.2.3 Data Flow and Control Logic Data flow and control logic are related to interaction between modules. Data flow and control logic within the Trace module and the Trace Log CIF module is described in figure 4.2.2.3-1 ┆
0x48b00…48c00 (72, 0, 11) Sector 480c0a00157541 ┆H uA og Trace Sub-Package 4.2.2.1 Functional Specification The main functions for the log trace sub-package are: 1) Receive trace keys. 2) Retrieve pertinent log CIFs. 3)┆
0x48c00…48d00 (72, 0, 12) Sector 480d7800157541 ┆H x uA 1 FIG. 4.2.2.3-1 Data Flow In Trace Subpackage 2.1-1. 4.2.2.1.1 Receive Trace Keys When a trace command is received the trace key buffer is read into the trace data area. The tr┆
0x48d00…48e00 (72, 0, 13) Sector 480eff00157541 ┆H uA 1 4.2.2.4 Module Specification 4.2.2.4.1 Trace Module 4.2.2.4.1.1 Functional Specification The Trace Module is the main module in the Trace subpackage. The incoming trace comm┆
0x48e00…48f00 (72, 0, 14) Sector 480fff00157541 ┆H uAands are received and validated. If errors are found the queue element is sent to the SSC garble queue via CSF and a negative acknowledge returned to TEP. The required log CIFs are retrieved via SAR and each log CIF traced by a call to the Trace L┆
0x48f00…49000 (72, 0, 15) Sector 4300ff00157541 ┆C uAog CIF Module. 4.2.2.4.1.2 Module Interface The Trace module interface via queues to TEP and SAR and via system calls to CSF. Refer to section 4.1.7.1. The module/module interface to the Trace Log CIF Module is described in section 4.2.2.4.2.┆
0x49000…49100 (73, 0, 0) Sector 4901ff00157541 ┆I uA 1 b) a specific terminal. The trace key is a log time interval and a parameter defining: 1) terminal procedures 2) message distribution control 3) message service 4) super┆
0x49100…49200 (73, 0, 1) Sector 4902ff00157541 ┆I uAvisor transactions 5) security procedures c) a specific device. The trace key is a log time interval and a parameter defining: 1) incoming messages 2) PTP d) a log time interval only. Log Trace Command Definition TYPE LOG TRACE CO┆
0x49200…49300 (73, 0, 2) Sector 4903ff00157541 ┆I uAMMAND TYPE = RECORD TRACE TYPE : LOG TRACE RECORD TYPE; EARLY LOG TIME : TIME TYPE; LATE LOG TIME : TIME TYPE; CHAN TERM DESIGNATOR : DESIGNATOR TYPE END; 1 ┆
0x49300…49400 (73, 0, 3) Sector 4904ff00157541 ┆I uA TYPE LOG TRACE RECORD TYPE = (LOG TRACE ALL, LOG TRACE INCOMING MSG, LOG TRACE OUTGOING MSG, LOG TRACE CH DISCONTINUITY, LOG TRACE TERMINAL PROC, LOG TRACE MESSAGE DIST, LOG TRACE MESSAGE SERVICE, LOG ┆
0x49400…49500 (73, 0, 4) Sector 49055900157541 ┆I Y uATRACE SUPV TRANS, LOG TRACE SECURITY PROC, LOG TRACE SPECIFIC DEVICE) DISMANTLE VIEW OG RECORDS) OF INTERNAL LOG REC TYPE END TYPE COLL BUF INDEX TYPE = (0..COLLECT BUFFER NO OF LOG RECORDS) TYPE COLLECT CONTROL HEADER TYPE = ┆
0x49500…49600 (73, 0, 5) Sector 4906ff00157541 ┆I uA 1 4.2.2.1.2 Retrieve Pertinent Log CIFs The pertinent log CIF-refs are retrieved from SAR. Inputs are log time intervals and SAR log type indicator. The log records are read from th┆
0x49600…49700 (73, 0, 6) Sector 4907ff00157541 ┆I uAe trace CIF and stored in the log trace data area. 4.2.2.1.3 Trace Log Records The log records in the log trace data area are traced one by one. The log record parameters are compared with the trace keys. The wanted log records are stored in th┆
0x49700…49800 (73, 0, 7) Sector 4808c100157541 ┆H A uAe trace CIF for later print-out. 4.2.2.1.4 Return Traced Log Records When log trace is completed, the log trace CIF-ref and a completion code are returned to the TEP reply queue. ┆
0x49800…49900 (73, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(73,0, 9), len=0xff, h3=41157541}, f00=»1575A «, f01=»CPS/SDS/032 «, f02=»bbh «, f03=»HUH «, f04=»Fra 4.2.2 «, f05=11-01-81 09:13, f06=» 10 «, f07=»01 «, f08=» 28308 «, f09=06-05-82 15:36, f10=» «, f11=»06 «, f12=» 92 «, f13=06-05-82 15:46, f14=10-05-82 10:56, f15=»0113A «, f16=» 72 «, f17=» 26 «, f18=»24 «, f19=» 704 «, f20=» 51918 «, f21=» «, f22=» @ «, f99=240010000110066610110480aaca1505000000000000003703e100df}
0x49900…49a00 (73, 0, 9) Sector 490a4800157541 ┆I H uA I I I I H H H H C C B B B A A A A A @ @ @ @ @ @ ? ? ? ? ? ? ? > > > > > = = = = = < < < < < ; ; ; ; ; ; ; : : : : : 9 9 9 ) ) ( ( ( ( ( ( ' ' ' ' : FoFoFoFoFoFoFoFoFoFoFoFoFoFoFoFoFoFoFoFo: FoFoFoFoFoFoFoFoFoFoFo: FoFoFoFoFoFoFoFoFoFoFo┆
0x49a00…49b00 (73, 0, 10) Sector 490ba200157541 ┆I " uA 1 CPS/SDS/032 HUH/820503 LOGGING DETAILED DESIGN SPECIFICATION CAMPS *-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x49b00…49c00 (73, 0, 11) Sector 490cff00157541 ┆I uA 1 og Trace Sub-Package 4.2.2.1 Functional Specification The main functions for the log trace sub-package are: 1) Receive trace keys. 2) Retrieve pertinent log CIFs. 3)┆
0x49c00…49d00 (73, 0, 12) Sector 490dff00157541 ┆I uA Trace log records. 4) Return traced log records in a trace CIF. The functional breakdown is shown in fig. 4.2.2.1-1. 4.2.2.1.1 Receive Trace Keys When a trace command is received the trace key buffer is read into the trace data area. The tr┆
0x49d00…49e00 (73, 0, 13) Sector 490eff00157541 ┆I uAace command type consists of a trace record type, an early log time, a late log time, and a channel or terminal designator. If any errors are found, the trace action is terminated and the trace command queue element is sent to the SSC garble queue. ┆
0x49e00…49f00 (73, 0, 14) Sector 490fff00157541 ┆I uA 4.2.2.1.1.1 Trace Key Definition The stored log information may be traced by TEP with respect to: a) a specific channel. The trace key is a log time interval and a parameter defining: 1) incoming messages 2) outgoing messages 3) cha┆
0x49f00…4a000 (73, 0, 15) Sector 49001a00157541 ┆I uAnnel discontinuity "(=~~ J*2M2/C<2:^=~ B<2:b= R<2M/,:g=~ BG2M")M2&! "(=~~ BW2I! <6 M /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=!┆
0x4a000…4a100 (74, 0, 0) Sector 00000000000000 ┆ ┆
[…0x2f…]
