$A PAGE=60;UND='#'
$A JUST=1;PGAP=5;TAB=5,10,20,30
$A NLS=2;INDENT=1;LINE=70
$A PAGENO=1;START=1
$L1CUM
E.R.T.E.  USER MANUAL
$B8 $L1CUM
CONTENTS
$A INDENT=3
$B2 $L9CI
1) INTRODUCTION
2) SCRIPT FORMATS
3) PARAMETER FILES
4) RUNNING E.R.T.E.
5) ERROR MESSAGES
6) CONFIGURING E.R.T.E.
7) DATA ANALYSIS
8) SCRIPT FILE UTILITIES
9) OTHER RELEVANT DOCUMENTATION
$B8 $I1 $L1CUI
ISSUE NO. 6.0 (FOR ERTE MK.3 & ERTE MK.4)  16TH MARCH 1979
$N $I2 $L1CUI
SECTION 1 : INTRODUCTION
$A INDENT=1
$P2
@THE .EDINBURGH .REMOTE .TERMINAL .EMULATOR IS A SYSTEM DESIGNED
TO SIMULATE TERMINAL USERS ON A @MULTI @ACCESS @SYSTEM. @IT OPERATES
BY PASSING COMMANDS (HELD IN .SCRIPT .FILES) TO THE RECEIVING SYSTEM
(REFERRED TO AS THE .TARGET IN THE REST OF THIS DOCUMENT) AS IF
FROM ORDINARY TERMINALS. @THESE SCRIPT FILES AND THE CORRESPONDING
PARAMETER FILES MAY BE GENERATED USING THE .MAVIS [@BREBNER 1977]
SUITE OR MERELY BY EDITING APPROPRIATE TEXT FILES USING THE
STANDARD SYSTEM EDITOR. @THE VERSIONS OF .ERTE DESCRIBED HAVE BEEN USED
EXTENSIVELY ON .EMAS 4/75, VARIOUS .EMAS 2900's AND .DEC .VAX .VMS.
@THIS DOCUMENT DESCRIBES PARTICULAR IMPLEMENTATIONS OF .ERTE SPECIFIC
TO THE NEEDS OF THE ORIGINAL .SRC FUNDED RESEARCH PROJECT
( .SRC GRANTS .BRG 93968 AND .BRG 96084 ), A MORE
GENERAL DISCUSSION OF .ERTE MAY BE FOUND IN .ADAMS ET AL 1977.
$B
$P
@THE CURRENT SUPPORTED VERSIONS OF .ERTE ARE AS FOLLOWS:
$A INDENT=3
$b
$I2
.%ERTE MK.3.0 $T4 @SIMULATES A .TCP ON THE .RCO NET, TALKING
.NSI AND .ITP PROTOCOLS DOWN 1 CONCENTRATED SYNCHRONOUS LINE. @UPTO
48 SIMULTANEOUS USERS ON A 32K WORD .PDP 11/40.
$b
$I2
.%ERTE MK.3.1 $T4 @SIMULATES A .TCP CONNECTED DIRECTLY TO THE
TARGET .FRONT .END, TALKING .NSI AND .ITP PROTOCOLS DOWN 1
CONCENTRATED ASYNCHRONOUS LINE ( USUALLY A @C.@S. DEPT .LINK ).
@UPTO 48 USERS ON A 32K WORD .PDP 11/40.
$b
$I2
.%ERTE MK.3.2 $T4 @SIMULATES A .TCP ON THE .RCO NET, TALKING
.NSI AND .ITP PROTOCOLS DOWN 1 CONCENTRATED SYNCHRONOUS LINE. @UPTO
128 USERS HAVE BEEN HANDLED ON A 48K WORD .PDP 11/40, AND MORE MAY
BE POSSIBLE.
$b
$I2
.%ERTE MK.4.0 $T4 @OUTPUTS CHARACTERS ONTO A NUMBER OF
INDIVIDUAL ASYNCHRONOUS LINES, NO PROTOCOL IS USUALLY PLACED ON
THESE AND .ERTE IS CONNECTED TO THE
TARGET AS THOUGH IT WERE A
NUMBER OF LOCAL TERMINALS. @CURRENTLY UP TO ONLY 7
USERS HAVE BEEN SIMULATED BY THIS METHOD DUE TO 
THE NON EXISTENCE OF ANY MORE MULTIPLEXOR LINES.
@CAPACITY OF THE .PDP 11/40 UNDER THIS REGIME IS NOT KNOWN, BUT WILL
NOT BE AS HIGH AS UNDER .ERTE MK.3 AS EXTRA PROCESSING IS REQUIRED
TO IDENTIFY SYSTEM PROMPT MESSAGES ETC.
$a indent=1
$B
$P
@THE ENTIRE PACKAGE IS WRITTEN IN THE HIGH LEVEL LANGUAGE
.IMP-77 [@ROBERTSON 1977] AND THE LISTINGS ARE INTENDED TO BE SELF
DOCUMENTING. @THIS DOCUMENT IS INTENDED TO SUPLEMENT SAID LISTINGS
AND GIVE A QUICK GUIDE TO RUNNING THE PACKAGE. .ERTE CONSISTS OF
SEVERAL CO-OPERATING TASKS RUNNING UNDER THE .DEIMOS @OPERATING
@SYSTEM ON A .PDP 11 WITH MEMORY MANAGEMENT AND
 AT LEAST .32K @CORE @MEMORY. @THE TASKS
ARE AS FOLLOWS:-
$A INDENT=3
$I2
.INIT $T3 @INITIALISE AND @CONTROL @TASK ( GIVEN THE .DEIMOS NAME OF .ERTE )
$I2
.TIME $T3 @STIMULATOR @CLOCK @TASK
$I2
.DQS1 $T3 .DQS/11E SYNCHRONOUS LINE @COMMUNICATIONS @HANDLER ( MK.3 )
$I2
@D@Z@AN $T3 .DZ/11 @MULTIPLEXOR @HANDLERS ( MK.4 )
$I2
.PROT $T3 @LINE @PROTOCOL @HANDLER ( .HDLC ) ( MK.3 )
$I2
.CSLK $T3 @C.@S. @LINK @HANDLER AND .HDLC @PROTOCOL @HANDLER ( MK.3.1 )
$I2
.NSI $T3 @NETWORK @PROTOCOL @HANDLER ( TO .RCO .NSI ) (  MK.3 )
$I2
.TCP $T3 @TERMINAL @PROTOCOL @HANDLER ( TO .RCO .ITP ) ( MK.3 )
$I2
.TSIM $T3 @TERMINAL @SIMULATOR  ( MK.4 )
$I2
.CPUT $T3 @OPTIONAL .CPU @UTILISATION @MODULE
$I2
@T@S@KN $T3 N .SCRIPT @TASKS, EACH OF WHICH CAN HANDLE UP TO A
FIXED NUMBER OF SCRIPTS FOR THE "VIRTUAL TERMINALS"
(CURRENTLY 16 SCRIPTS). ( MK.3 )
$I2
@T@S@CN $T3 N .SCRIPT @TASKS ( MK.4 VERSION OF .TSK )
$A INDENT=1
$P
@ALL THE DETAILS OF THE NUMBER OF SCRIPTS, ETC. ARE PASSED TO
.ERTE IN .PARAMETER .FILES, ONE PER @SCRIPT @TASK. @THE LIMIT TO THE
NUMBER OF SCRIPT TASKS AND VIRTUAL CONSOLES IS DETERMINED BY THE
AVAILABLE CORE.
$P1
@ALL MONITORING DATA FROM .ERTE IS OUTPUT TO A FIXED FILE ,
.XOT, ON A SPECIFIED DISC UNIT, AND THERE IS A SET OF UTILITIES FOR
PROCESSING THIS DATA. (@SEE .SECTION 7)
$N $I2 $L1CUI
SECTION 2 : SCRIPT FORMATS
$P2
@A SCRIPT FILE CONTAINS THE SIMULATED INPUT FROM A TERMINAL.
@IT MAY BE OF ANY LENGTH AND CAN INCLUDE ANY NUMBER OF USER
SESSIONS I$.E. LOGING ON AND OFF.
$P
@ITS FORMAT IS AS FOLLOWS
$A INDENT=3
$L3CI
COMMAND LINE
CHECK LINE
DELAY TIME
$A INDENT=1
$P
.COMMAND .LINE:- @THIS IS PASSED ON VERBATIM TO THE SYSTEM
(CURRENT MAX. 70 CHARACTERS). @NOTE THAT THE SCRIPT MUST START
WITH THE USUAL SYSTEM STARTUP REQUIREMENTS (&, .EMAS, .USERNAME, .PASSWORD)
$P
.CHECK .LINE:- @MAY BE USED TO VERIFY THE SCRIPT.
@IN .ERTE MK.3
THIS IS CURRENTLY NOT USED ( LINE USUALLY HOLDS A "0") EXCEPT THAT
THE LAST CHECK DIGIT IN A USER SESSION .%MUST BE NEGATIVE. @IN .ERTE
MK.4 THIS LINE IS USED TO HOLD THE EXPECTED SYSTEM PROMPT
MESSAGE, OR A "0" IF THE PROMPT IS THE SAME AS THAT OF THE PREVIOUS
INTERACTION. @ALL TEXT OUTPUT FROM THE TARGET WILL BE CHECKED AGAINST
THIS MESSAGE FOR A MATCH. @ON A MATCH BEING FOUND, THE .TSIM TASK
WILL INFORM THE .TSC TASK AND THE NEXT USER THINK TIME AND COMMAND
WILL START. @THE FORMAT OF THIS LINE IS "<PROMPT TEXT>0". @THE
"PROMPT TEXT" SHOULD NOT CONTAIN A "0" AND SHOULD BE AS SHORT AS
POSSIBLE TO IDENTIFY THE PROMPT. 
@N.@B. THE FIRST OCCURENCE OF THE "PROMPT TEXT" APPEARING IN THE
OUTPUT FROM THE TARGET IS TAKEN TO BE THE PROMPT.
@IF THE PROMPT IS UNCHANGED THEN
THE .CHECK .LINE SHOULD CONTAIN A "0" ( SPACES BEFORE THE "0" ARE
SIGNIFICANT ). @N.@B. ATTEMPTING TO CHANGE THE "PROMPT TEXT" TO THE SAME VALUE
WILL USUALLY CAUSE THE .TSIM TASK (WHICH ACTUALLY DOES THE CHECKING FOR THE
PROMPTS) TO SEND AN IMMEDIATE REPLY TO THE .TSC TASK INDICATING A PROMPT HAS 
BEEN
FOUND. @THE .CHECK .LINE SHOULD ONLY CONTAIN A CHANGE OF "PROMPT TEXT" WHEN
NECESSARY.
$P
.DELAY .TIME:- @THE TIME IN SECONDS BETWEEN THE SYSTEM RESPONSE
TO THE COMMAND AND THE INPUT OF THE NEXT COMMAND IN THE SCRIPT
(I$.E. THE USER THINK TIME). @USER THINK TIMES ARE NORMALLY
CALCULATED FROM THE END OF TYPING OF THE TARGET'S PROMPT. @HOWEVER
FOR .ERTE MK.3.3 AND .ERTE MK.4 A "TYPE AHEAD" OPTION IS INCLUDED.
@IF A MINUS SIGN PRECEDES THE USER THINK TIME THEN THE USER THINK
TIME IS CALCULATED FROM THE LAST CHARACTER BEING INPUT FROM THE
CURRENT COMMAND AND .ERTE DOES NOT WAIT FOR THE SYSTEM'S PROMPT TO
APPEAR.
$P
@THERE SHOULD BE NO REDUNDANT BLANK LINES IN THE SCRIPT FILE
AND NO TERMINATOR IS REQUIRED. @THE UTILITY .ANALY CAN BE USED TO
TIDY UP SCRIPT FILES, VERIFY THEM AND PROVIDE A SUMMARY OF DELAY
TIMES ETC. .SCRIPT FILES MAY EXIST ON ANY LOGICAL DISC UNIT UNDER ANY
USER FILE SYSTEM
NUMBER, BUT THE NAME .%MUST BE .%EXACTLY 6 CHARACTERS IN LENGTH.
$N $I2 $L1CUI
SECTION 3 : PARAMETER FILES
$P2
@THE PARAMETER FILES INFORM THE SCRIPT TASKS WITHIN .ERTE WHICH
SCRIPT FILES ETC. TO USE. THE PARAMETER FILES .%MUST BE ON THE SAME
UNIT AND FILE SYSTEM NUMBER AS .ERTE WHEN IT IS RUN AND THERE IS
ONE SUCH FILE PER SCRIPT TASK.
$P
@PARAMETER FILE NAMES MUST BE OF THE FORM @T@K@P@A@RN WHERE N =
@SCRIPT @TASK @NUMBER (1-9) AND HAVE THE FOLLOWING FORMAT
$I2 $L1CI
LINE 1 : <NUMBER OF SCRIPTS> <TYPING RATE> <START UP DELAY>
$P
@THE .TYPING .RATE IS THE PERCENTAGE OF LINE SPEED TO BE USED AS A TYPING
SPEED FOR INPUTING THE COMMAND LINES OF THE SCRIPT.
$P
@THE .START .UP .DELAY IS THE TIME IN SECONDS BETWEEN SENDING THE
FIRST LOGON ATTEMPT FOR EACH SUCESSIVE SCRIPT.
$P2
@FOR EACH SCRIPT THE TASK HAS TO HANDLE THERE ARE FOUR LINES
OF DATA:-
$A INDENT=2
$L4CI
1 : SCRIPT FILE NAME (EXACTLY 6 CHARACTERS)
2 : FILE SYSTEM NUMBER FOR FILE (0-63 DECIMAL)
3 : DISC UNIT FOR FILE 
4 : LINE SPEED IN CHARACTERS PER SECOND.
$A INDENT=1
$P2 
@NO TERMINATOR IS REQUIRED.
$N $I2 $L1CUI
SECTION 4 : RUNNING E.R.T.E.
$P2
@TO SET UP ANY .TARGET TO RECEIVE .ERTE INPUT THE APPROPRIATE
EXPERIMENTORS GUIDE SHOULD FIRST BE CONSULTED [SEE @SECTION 9].
@THE FOLLOWING PROCEDURE SHOULD THEN BE FOLLOWED:-
$A INDENT=2
$L2CI
1)IPL DEIMOS 
2)LOGON TO THE APPROPRIATE DEIMOS FILE SYSTEM
@THE FOLLOWING TASKS ARE LOADED FOR .ERTE MK.3.0 AND MK.3.2 :
$b
$A TAB=3,20,40
$I1
.%STIMULATOR $T2 .%USER $T3 .%COMMENTS
$B1
$A INDENT=3
$T2 @E@R@T@ENN $T3 @LOADS THE CURRENT VERSION NN OF
.ERTE ( NN USUALLY FOUND IN THE CURRENT EDITION OF THE .INSTANT .ERTE .GUIDE).
$I1
.ERTE .VNN .DD/MM/YY $T3 @REPORTS THE VERSION NUMBER AND
DATE OF ISSUE. @IF WRONG HALT
MACHINE & START AGAIN.
$I1
.TCP .UNIT: $T2 N $T3 @REQUESTS THE LOGICAL OUTPUT DEVICE FOR
THE FILE ( .XOT ) PRODUCED BY THE
.TCP TASK. @ON THE ORIGINAL CONFIGURATION N=2 OR 3 OR 0 (IF
ONLY ONE DISC).
$I1
.TIME .LOADED $T3 @TIMER @MODULE @LOADED.
$I1
.DQSY .LOADED $T3 .DQS/11E @HANDLER.
$I1
.PROT .LOADED $T3 @LINE @PROTOCOL @HANDLER.
$I1
@T@C@PN .LOADED $T3 @TERMINAL @PROTOCOL @HANDLER.
N='@X' - @THE NON .NSI VERSION.
N='@Z' - @THE .NSI VERSION.
$I1
.NSIZ .LOADED $T3 @NETWORK @PROTOCOL @HANDLER (IF
USING .TCPZ).
$I1
.CPUT .LOADED $T3 .CPU @UTILISATION @MONITORING TASK (SEE
BELOW)
$I1
.NSIZ: .PROT .UP $T3 @PHYSICAL LINE UP
$I1
.NSIZ: .ATTACHED AS NN $T3 @SUCESSFULLY ATTACHED TO .RCO NETWORK
$I1
.NSIZ: .CONNECTED TO NN $T3 @SUCESSFULLY CONNECTED TO TARGET
$I1
.TCPZ: .BUFF .REM NN $T3 @SOMETIMES OUTPUT BY .ERTE MK.3.2. @MEANS THAT ONE
OF THE .ITP MESSAGE BUFFER POOL SPANS A .PDP 11 SEGMENT BOUNDARY AND HAS BEEN
REMOVED FROM THE FREE POOL. @THIS USUALLY ONLY HAPPENS IN VERSIONS WITH LARGE
BUFFER POOLS @E.@G. MK.3.2.
$I1
.TCPZ: .ITP .READY $T3 @ALL INITIALISATION COMPLETE AND NOW READY TO START.
@IT IS NOW SAFE TO REPLY TO THE " .NUMBER .OF .TASKS" MESSAGE (@N.@B. THE
.NSIZ, .TCPZ AND " .NUMBER .OF .TASKS" MESSAGES ARE OUTPUT BY 3 DIFFERENT 
TASKS AND SO MAY COME OUT IN ANY INTERLEAVED ORDER, .DO .NOT .REPLY TO THE
" .NUMBER .OF .TASKS" MESSAGE UNTIL THE .ITP .READY MESSAGE HAS APPEARED) .
$I1
.NUMBER .OF .TASKS $T2 @N $T3 @ASKS FOR THE NUMBER OF SCRIPT
TASKS TO BE LOADED. @THIS
NUMBER IS CURRENTLY 1,2, OR 3
(FOR 1-16, 1-32 OR 1-48
SCRIPTS) BUT WILL VARY ON CORE
SIZE.
$I1 $L1CI
SCRIPT TASK 1 STARTED WITH X SCRIPTS
@EACH SCRIPT TASK IS LOADED AND
THE CORRESPONDING PARAMETER
FILE IS READ. @THE FIRST
COMMANDS IN THE SCRIPTS ARE
FOUND AND THE SCRIPTS ARE
STARTED AFTER THE APPROPRIATE
DELAY. @IT IS AT THIS POINT
THAT MANY OF THE OBVIOUS ERRORS
WILL OCCUR ( .SECTION 5).
$b $L
@THE LOADING SEQUENCE OF .%ERTE MK.3.1 DIFFERS IN THE FOLLOWING TASKS :
$i1
.CSLK .LOADED $T3 @C.@S. DEPARTMENTAL LINK HANDLER, REPLACES .PROT AND .DQSY.
$b $L
@THE LOADING SEQUENCE OF .%ERTE MK.4.0 DIFFERS IN THE FOLLOWING TASKS :
$I1
@D@Z@AN .LOADED $T3 N .MULTIPLEXOR TASKS, REPLACES .PROT AND .DQSY OF MK.3.0.

$I1
.TSIM .LOADED $T3 @TERMINAL SIMULATOR AND PROMPT CHECKING TASK REPLACES @T@C@P
AND .NSI OF .ERTE MK.3.0.
$I1
@THE .SCRIPT .TASKS LOADED IN MK.4.0 ARE ALSO DIFFERENT AND ARE CALLED 
@T@S@CN
RATHER THAN @T@S@KN. @ALL THE QUERY MECHANISMS AND STATE NUMBERINGS WITHIN
.TSC REMAINS THE SAME AS THAT IN .TSK HOWEVER.
$A INDENT=1
$A TAB=5,10,20,30,40
$P
@FROM THIS POINT ON .ERTE RUNS AUTOMATICALLY BUT THE FOLLOWING
CONTROLS ARE AVAILABLE BY USING THE .DEIMOS .INT MECHANISM.
$I3 $L1CI
INT Z TSKN or int z tscn      WHERE Z MAY BE
$P
$A INDENT=3
$I2
? : $T3 @PRINTS A STATUS REPORT FOR EACH
SCRIPT UNDER THAT TASK. @IT IS
A TABLE WITH SCRIPT NUMBER,
STATE, NUMBER OF COMMAND LINES
SENT AND THE NUMBER OF TIMES
THAT THE SCRIPT HAS BEEN HELD
UP DUE TO THE NEXT COMMAND NOT
BEING BROUGHT OFF THE DISC IN
TIME. @THIS NORMALLY ONLY
HAPPENS WITH A ZERO THINK
TIME, AS ON START UP AND THIS
NUMBER SHOULD BE RELATIVELY
SMALL COMPARED TO THE NUMBER OF
COMMANDS. @STATE MAY BE ONE
OF:-
$L10CI
 0    ABOUT TO SEND A COMMAND(TYPING ONE IN)
 1    WAITING FOR TCP BUFFER(1ST TRY)
 2    WAITING FOR TCP BUFFER(SUBSEQUENT TRY)
 3    WAITING FOR EMAS TO RESPOND
 4    IN THINK DELAY
 5    WAITING FOR DISC TRANSFER TO COMPLETE
 6    START UP STATE
 7    END OF SCRIPT FILE REACHED
 8    requesting prompt buffer from tsim ( MK.4 only )
 9    typing ahead (MK.3.3 and MK.4 only )
$P
$I2
@Q : $T3 .FULL .STATUS - AS FOR ? PLUS
INTERNAL SCRIPT BUFFER
INFORMATION (SEE PROGRAM
LISTING FOR DETAILS).
$P
$I2
@L : $T3 .ENTER .LOOP .MODE. @IF A SCRIPT
REACHES STATE 7 IT IS RESTARTED
FROM THE BEGINNING.
$P
$I2
@A : $T3 .ABORT THE TASK IMMEDIATELY
$P
$A INDENT=1
$P
.N.B. @THE .INT FLAG IS ONLY INSPECTED EVERY 5 SECONDS SO THERE
MAY BE SOME DELAY. @A NEW .INT COMMAND WILL OVERWRITE THE OLD ONE
(E$.G. @A WILL OVERWRITE @L BUT ? OVERWRITES ITSELF TO 0 AFTER TYPING
THE REPORT).
$P
@THE .INT MECHANISM MAY BE USED WITH TASK .CPUT TO MEASURE THE .CPU
@IDLE @TIME IN THE 11/40 WHILE .ERTE IS RUNNING.
$I2
.INT @X .CPUT WHERE @X MAY BE:-
$A INDENT=2
$L4CI
     T : MEASURE OVER 10 SECOND INTERVAL
     H : MEASURE OVER 30 SECOND INTERVAL
     M : MEASURE OVER 60 SECOND INTERVAL
     A : STOP
$A INDENT=1
$B3 
$L1CUI
CLOSING DOWN ERTE
$P
@THE .INT MECHANISM MAY BE USED WITH THE .INIT TASK (KNOWN IN .DEIMOS AS
 THE TASK
.ERTE ) TO CLOSE DOWN .ERTE. @THIS IS QUICKER THAN DOING AN .INT @A TO EACH OF 



 
THE .SCRIPT TASKS. @THE SHUTDOWN COMMAND IS :
$L
             .INT @A .ERTE
$A INDENT=1
$P
@ALTERNATIVELY .SCRIPTS TASKS WILL TERMINATE NATURALLY WHEN ALL THE SCRIPTS
IN A TASK HAVE REACHED STATE 7 AND LOOP MODE IS NOT SET. .SCRIPT TASKS CAN
OF COURSE ALSO BE HALTED BY AN .INT @A.
@WHEN ALL THE SCRIPTS IN A TASK HAVE FINISHED OR .INT
@A IS SENT, THE TASK WILL PRODUCE A SCRIPT STATUS REPORT 
AND THE MESSAGE .TASK NN .TERMINATED WILL APPEAR (TWICE).
$P
@WHEN ALL THE .SCRIPT TASKS HAVE TERMINATED THE .TCP OR .TSIM TASK IS
STOPPED AND WILL PRODUCE DATA ON THE UTILISATION OF ITS INTERNAL
QUEUES, THEN THE .TIME TASK IS STOPPED GIVING THE RUN TIME IN .MINS,
AND .SECS, .1/10TH SECS. @FINALLY AFTER A PAUSE THE MESSAGE .ERTE .STOPPED WILL
APPEAR.
$P
.N.B. @THIS STILL LEAVES THREE TASKS IN CORE, .DQS1 AND .PROT
WHICH SHOULD BE KILLED IMMEDIATELY, AND .CPUT WHICH SHOULD BE SENT AN
.INT .A. (@IT MAY BE REMOVED AT ANY TIME USING THIS METHOD). @HOWEVER
.ERTE OFTEN CRASHES AT THIS POINT (BUT THIS SHOULD NOT BE A CAUSE FOR
ALARM) SO RE .IPL ING THE SYSTEM MAY BE THE BEST COURSE OF ACTION.
$N $I2 $L1CUI
SECTION 5 : ERROR MESAGES
$P2
@MOST .ERTE ERROR MESSAGES ARE FATAL IN THAT THEY CAUSE AT LEAST
PART OF .ERTE TO STOP. @THE MESSAGES BELOW ARE DIVIDED INTO THE TASKS
FROM WHICH THEY ORIGINATE.
$B1 $I2 $L1CUI
5.1)INIT
$P
.INIT REPORTS ALL ERROR MESSAGES COMING FROM THE SCRIPT TASKS
(5.2) AND ITS ONLY OTHER ERROR CONDITION IS
$I2 $L1CI
UNEXPECTED MESSAGE   A   B   C
WHERE @A = .TASK .ID SENDING THE MESSAGE , .B= .P_A1, .C= .P_A3. @THIS
USUALLY INDICATES A FAULTY START UP : RELOAD & TRY AGAIN.
@N.@B. THE .INIT TASK USUALLY TAKES THE .DEIMOS NAME OF .ERTE.
$B1 $I2 $L1CUI
5.2)SCRIPT TASKS
$P
@ALL THE .SCRIPT .TASK ERRORS ARE REPORTED BY .INIT WITH THE
FOLLOWING FORMAT:-
$I2 $L1CI
 FATAL ERROR NUMBER   X   TASK NUMBER   N
WHERE @N=@SCRIPT @TASK @NUMBER, @X=@ERROR @NUMBER AS FOLLOWS ( .N.B. ALL
THESE ERRORS CAUSE THE SCRIPT TASK TO STOP)
$A INDENT=3
$I2
-1 $T3 @INTERNAL SCRIPT BUFFERS
EXHAUSTED
$I2
-2 $T3 @BAD DISC READ (SCRIPT FILE)
$I2
-3 $T3 @BAD DISC READ AT START OF
SCRIPT FILE (FILE MAY NOT
EXIST)
$I2
-4 $T3 @SCRIPT FILE CORRUPT-VERIFY THE
FILE SYSTEM BEFORE RESTARTING
$I2
-5 $T3 @RUN OUT OF PROMPT BUFFERS - INCREASE THE NUMBER HELD, .PROMPTBMAX AND
.PROMPTBTOTAL ( MK.4.0 ). @NOT USED IN MK.3.
$I2
-6 $T3 @NOT @USED
$I2
-7 $T3 @DISC QUEUE FULL
$I2
-8 $T3 @PARAMETER FILE TOO SHORT (END
OF FILE REACHED BEFORE ALL
SCRIPTS FOUND OR FILE CORRUPT)
$I2
-9 $T3 @PARAMETER FILE DISC READ ERROR
$I2
-10 $T3 @SYMBOL IN PARAMETER DATA
$I2
-11 $T3 @PARAMETER FILE DOES NOT EXIST
$I2
-12 $T3 @DISC READ ERROR ON FIRST BLOCK
OF PARAMETER FILE
$A INDENT=1
$B $I2 $L1CUI
5.3)TCP
$P
@ALL ERROR MESSAGES CAUSE THE .TCP TASK TO STOP AND ARE IN THE
FORMAT
$I3 $L1CI
TCP <MESSAGE> <TIME> <VIRTUAL CONSOLE NUMBER>,
WHERE THE MESSAGE MAY BE:-
$A INDENT=4
$I1
.BREAK .INT .TO .USER $T4 @BAD CONTROL MESSAGE FROM .FEP
$I1
.TARGET .DOWN
$I1
.TARGET .JUST .BACK .UP
$I1
.BUFF .NOT .SENT $T4 @BAD REPLIES FROM A TRANSMIT TO .TARGET
REQUEST
$I1
.ABORTED .CONSL $T4 @MESSAGE RECEIVED FROM SCRIPT TASK FOR A
VIRTUAL CONSOLE WHICH HAS BEEN ABORTED
$I1
.MQ .DN .FULL $T4 @QUEUE OF MESSAGES TO .TARGET FULL
$I2
.GAH .Q .FULL $T4 @QUEUE OF .GO-AHEAD MESSAGES TO .TARGET NODE IS FULL.
$A INDENT=1
$B $I2 $L1CUI
5.4)NSI
$P
@ALL ERROR MESSAGES CAUSE THE .NSI TASK TO STOP AND ARE IN THE
FORMAT :
$I3 $L1CI
NSIZ: < MESSAGE > < NSI STATE >
WHERE THE MESSAGES MAY BE:
$A INDENT=4
$I1
.ITP @Q .FULL $T4 - @TOO MANY MESSAGES FROM .TCP -> TARGET. (
@CUT DOWN THE NUMBER OF OUTSTANDING WRITES
 .TCP MAY SEND ).
$I1
.ITP .READY @Q .FULL $T4 - @TOO MANY READ FROM TARGET MESSAGES SENT
BY .TCP.
( @CUT DOWN ON THE NUMBER OF
OUTSTANDING READS .TCP CAN SEND. )
$I1
.TOO .MANY .FREE .SB'S $T4 - .NSI .SEND .BLOCK BUFFERING GONE HAYWIRE.
$I1
.NO .FREE .SB'S $T4 - @HAVE RUN OUT OF .NSI .SEND .BLOCKS. (
@INCREASE THE NUMBER OF .SB'S AVAILABLE TO
.NSI. )
$I1
.STATE .NOT .ATTACH $T4 - .NSI .ATTACH TO NETWORK REPLY RECEIVED AT
ODD TIME. ( @SEE @B.@G. OR @S.@C. )
$I1
.STATE .NOT .REMOVE $T4 - .NSI .REMOVE FROM NETWORK MESSAGE
RECEIVED AT ODD TIME. ( @TARGET .FRONT .END
MAY HAVE GONE DOWN. )
$I1
.PROT .NOT .UP $T4 - .PROT TASK DOES NOT WISH TO START. (
@CHECK PHYSICAL LINE EXISTS. )
$I1
.UGH .FROM .PROT $T4 - @LOUSY MESSAGE FROM .PROT. ( ?? )
$I1
.LOUSY .POFF $T4 - @A .DEIMOS TAsKS UNKNOWN TO .NSI SENT IT A
MESAGE. ( @CHECK OTHER TASKS. )
$B $L
@THE .NSI STATES ARE :
$A INDENT=2
$I2
1 $T3 - INITIALISING
$I2
2 $T3 - ATTACHING TO NETWORK
$I2
3 $T3 - CONNECTING TO TARGET
$I2
4 $T3 - RUNNING
$I2
5 $T3 - DISCONNECTING FROM TARGET
$I2
6 $T3 - REMOVING FROM NETWORK

$A INDENT=1

$B $I2 $L1CUI
5.5)PROT
$P
@THE .PROTOCOL .HANDLER MAY PRODUCE MESAGES OF THE FORM
$L
         .PROT:MESSAGE 
WHERE .MESSAGE CAN BE:-
$I1
.DM $T3 @DATA MISS - CAN BE IGNORED
$I1
.BAD .ACK $T3 @BAD ACK FROM FRONT END (FATAL
IF MANY OF THEM)
$I1
.NOISE $T3 @IGNORE THIS
$B $I2 $L1CUI
5.6)cslk
$P
@ALL ERROR MESSAGES ARE IN THE FORMAT 
$P
" .CSLK:"<MESSAGE>, 
$P
WHERE MESSAGE MAY
BE:
$I2
.BUFFER .NOT .IN .SEG 6
$I2
.OUT .STATE .ERROR
$I2
.IN .STATE .FAULT
$b $I2 $l1cui
5.7)dza
$P
@ALL ERROR MESSAGES ARE IN THE FORMAT 
$P
" .DZ11:*" <FAULT NUMBER><LINE NUMBER>
$b $i2 $l1cui
5.8)tsim
$P
@ALL ERROR MESSAGES CAUSE .TSIM TO STOP WITH A FAULT DUMP. @THE MESSAGES ARE IN





THE FORMAT 
$P
" .TSIM"<FAULT MESSAGE><TIME OF DAY><CNSL NUMBER>. 
$P
@THE FAULT MESSAGES ARE :
$A INDENT=3
$I1
0 .LENGTH $T3 @ATTEMPTING TO SEND AN INPUT LINE OF LENGTH 0 TO THE TARGET.
$I1
.MQDN .FULL $T3 @THE ARRAY HOLDING INPUT TO TARGET MESSAGES IS FULL.
$I1
.FT, .MULTOUT $T3@THE MULTIPLEXOR NUMBER IS OUT OF RANGE ON INPUT TO TARGET.
$I1
.MULT @W .REPLY $T3 @THE MULTIPLEXOR TASK REJECTED AN INPUT TO TARGET 
MESSAGE FOR SOME REASON.

$b $i2 $l1cui
5.9)SYSTEM MESSAGES
$P
.DEIMOS MAY ITSELF PRODUCE ERROR MESAGES ESPECIALLY DURING
SHUTDOWN WHEN .BAD .SER WILL APPEAR AND CAN BE IGNORED. @SEE .DEIMOS
MANUAL FOR OTHER MESSAGES.[@GILMORE 1978]
$N $I2 $L1CUI
SECTION 6 : CONFIGURING E.R.T.E.
$P
@THE PRINCIPLE TASKS COMPRISING .ERTE (SEE .SECTION 1) EACH HAVE
SEVERAL CONFIGURATION PARAMETERS TO ENABLE THE USER TO BUILD A
SYSTEM FOR HIS REQUIREMENTS. @THESE PARAMETERS ARE NOW DESCRIBED ON A
TASK BY TASK BASIS( .NB @IN ALL CASES RECOMPILATION OF THE TASK SOURCE
IS REQUIRED). @FOR FURTHER DETAILS SEE THE SELF DOCUMENTING LISTINGS.
$P $I2 $L1UI
@THE @INITIALISE @TASK
$P
@THIS TASK AUTOMATICALLY LOADS ANY NUMBER OF SCRIPT TASKS (SEE
BELOW) BUT MUST BE ALTERED IF THE LOG FILE NAME IS TO BE MODIFIED.
@IN THIS CASE CHANGE THE ARRAY .TCPZ. @THE .INIT TASK ALSO PASSES SOME
NETWORK INFORMATION TO .TCP (MK.3 ). @THIS DATA INCLUDES THE NETWORK ADDRESS
OF .TCP AND THE TARGET AS WELL AS THE TARGET'S NAME. @THIS IS ALL
HELD IN ARRAY .NETWORK.
@FOR .ERTE MK.4.0 THE .INIT TASK PASSES THE INITIAL TARGET PROMPT, THE 
CHARACTER
TO BE PASSED TO THE TARGET AT LOGON, THE LOGON CHARACTER HELD IN THE SCRIPTS
( WILL BE TRANSLATED TO THE TARGET LOGON CHARACTER BY .TSIM ), THE NUMBER OF
MULTIPLEXORS AVAILABLE AND THEIR .DEIMOS SERVICE NUMBERS. @AGAIN THIS IS HELD
IN THE ARRAY .NETWORK.
$P $I2 $L1UI
@THE @TIME @TASK
$P
@THE CONSTANT .ARSIZE IS THE SIZE OF THE REQUEST BUFFER AND THUS
MUST BE LARGE ENOUGH TO COPE WITH A REQUEST FROM EACH SCRIPT PLUS
SEVERAL OTHER REQUESTS.@THE FORMULA
$L1CM
ARSIZE = NUMBER OF SCRIPTS * 1.5
IS RECOMMENDED AS A MINIMUM BUFFER ALLOCATION.
$P $I2 $L1UI
@THE @SCRIPT @TASKS
$P
@THE NUMBER OF .SCRIPT TASKS REQUIRED FOR A PARTICULAR
CONFIGURATION IS A FUNCTION OF THE NUMBER OF SCRIPTS. @IT IS NOT
RECOMMENDED TO HAVE MORE THAN 16 SCRIPTS PER TASK AS THIS MAY CAUSE
EXCESSIVE INTERNAL QUEUING.
$P
@TO SET UP A SCRIPT TASK EDIT THE FOLLOWING
$A INDENT=3
$A TAB=5,10,20,30,40
$I2
.NUMSCR $T3 @THE NUMBER OF SCRIPTS THIS TASK
IS TO HANDLE.
$I2
.SYSLOT $T3 @THE SYSTEM SLOT THE TASK IS TO
RUN IN.@THESE START AT 26 FOR
.TSK1 AND DESCEND,25 FOR
.TSK2,ETC.
$I2
.PARMF $T3 @THIS ARRAY HOLDS THE NAME OF
THE PARAMETER FILE TO BE USED
BY THIS TASK,NORMALLY .TKPARN.
$I2
.SCBUFFS $T3 @THIS IS THE NUMBER OF INTERNAL
SCRIPT BUFFERS, WHICH SHOULD BE
AT LEAST .2*NUMSCR AND %MUST BE
.>NUMSCR. @THIS IS DEPENDANT ON
THE NUMBER OF CHARACTERS SENT
IN ON COMMAND LINES BY THE
SCRIPTS. @THE BUFFERS ARE EACH
20 CHARACTERS LONG AND THERE
MUST BE SUFFICIENT TO COPE WITH
THE PEAK LOAD.
$i2
.PRMPTL $T3 @THIS DETERMINES THE MAXIMUM SIZE OF ANY PIECE OF
"PROMPT TEXT" ( MK.4.0 ONLY ).
$i2
.PRMPTBMAX $T3 @THIS (ALONG WITH .PRMPTBTOTAL) DETERMINES THE NUMBER OF
PROMPT BUFFERS HELD, CURRENT RECOMMENDED VALUE OF 8 ( MK.4.0 ONLY ).
$i2
.PRMPTEND $T3 @THIS IS THE CHARACTER WHICH DEFINES THE END OF
"PROMPT TEXT" INA .CHECK .LINE OR AN EMPTY .CHECK .LINE, CURRENTLY
IS SET TO "0" ( MK.4.0 ONLY ).
$i2
.TEXTEND $T3 @THIS IS THE CHARACTER WHICH DEFINES THE END OF A COMMAND
LINE TO BE PASSED ON TO THE TARGET, CURRENTLY SET TO BE THE NEWLINE SYMBOL,
HOWEVER THERE IS NO LOGICAL REASON  STOPPING ANY CHARACTER BEING USED -
THOUGH THE FORMAT OF THE SCRIPT FILES WILL OF COURSE THEN CHANGE.
$A INDENT=1
$P
@COMPILE THE REQUIRED SCRIPT TASKS WITH A STACK OF 200,NO
STREAMS AND .ALL .WITH .THE .SAME .NAME, .TSK1 ( OR .TSC IN MK.4.0 ).
 @THE SYSTEM WILL CODE
SHARE THE TASKS.
$P $I2 $L1UI
@THE @TCP @TASK
$P
@THE SETS OF CONSTANTS AT THE BEGINNING OF THE .TCP TASK DEFINE
(AMONG OTHER THINGS) THE NUMBER OF VIRTUAL CONSOLES THIS .TCP MAY
MULTIPLEX, THE NUMBER OF .SCRIPT TASKS IT MAY COMMUNICATE WITH AND
THE AMOUNT OF INTERNAL BUFFERING IT HOLDS. @THE MAIN INTERNAL
BUFFERING HAS TO DO WITH TEXT MESSAGES PASSING BETWEEN THE .SCRIPT
TASKS AND THE .PROTOCOL TASKS NEARER THE .TARGET. @THERE IS A SEPARATE
QUEUES FOR .ITP PROTOCOL LEVEL .GO-AHEAD MESSAGES. @THE MAJOR
CONSTANTS ARE:-
$A INDENT=3
$I1
.TOTSCRIPTS $T3 @THE HIGHEST VIRTUAL CONSOLE
NUMBER EXPECTED(I. E. THE TOTAL
NUMBER OF VIRTUAL CONSOLES
-1,NUMBERING STARTS AT 0).
$I1
.PERTASK $T3 @THE NUMBER OF VIRTUAL CONSOLES
PER .SCRIPT TASK.
$I1
.MAXTASK $T3 @THE MAXIMUM NUMBER OF .SCRIPT
TASKS.
$I1
.MAXREAD $T3 @THE MAXIMUM NUMBER OF READS ( FROM TARGET )
WHICH MAY BE OUTSTANDING WITH
THE NEXT .PROTOCOL TASK TOWARDS
THE .TARGET.
$I1
.MAXWRITE $T3 @THE MAXIMUM NUMBER OF WRITES(TO
.TARGET) WHICH MAY BE
OUTSTANDING WITH THE .PROTOCOL
TASK TOWARDS .TARGET.
$I1
.MDQL $T3 @THE MAXIMUM NUMBER OF MESSAGES
TO TARGET WHICH MAY BE HELD IN
THE .TCP AT A TIME
$I1
.BUFFARL $T3 @THE NUMBER OF MESSAGE BUFFERS
WHICH EXIST ( .MAXREAD +
.MAXWRITE + .MDQL+1).
$I1
.GAHQL $T3 @THE SIZE OF THE .GO-AHEAD QUEUE
-1 (ALWAYS A POWER OF 2 -1).
$I1
.CHECKOUT $T3 .='Y' IF CONTENTS OF ALL
MESSAGES ARE TO BE RECORDED IN
THE .XOT FILE. .='N' IF NOT (THE
RECOMMENDED MODE FOR 'LONG
DISTANCE' @E@R@T@ES).
$I1
.TIMESTAMP $T3 .='Y' IF A TIME STAMP (IN 1/10
SECOND TICKS) IS TO BE APPENDED
TO ALL MESSAGES IN THE .XOT
FILE. .='N' IF NOT.
$I1
.TOXOT $T3 .='Y' IF AN .XOT FILE EXISTS,
RATHER THAN LOGGING DIRECTLY TO
THE OPERATOR'S CONSOLE. .='N'
WILL LOG TO OPERATOR'S CONSOLE.
$I1
.TRACEGAH $T3 .='N' IF .GO-AHEADS ARE TO BE
LOGGED. .='N' IF THEY ARE NOT.
$A INDENT=1
$P $I2 $L1UI
@THE @NSI @TASK
$P
@AS WITH .TCP THERE ARE A NUMBER OF CONSTANTS IN THE .NSI TASK DEFINING
HOW MANY MESAGES IT WILL BUFFER ETC. @THE MOST IMPORTANT ARE :
$A INDENT=3
$I1
.MAX .RD .SB $T3 @THE MAXIMUM NUMBER OF .SEND .BLOCK READS (FROM TARGET)
SENT TO THE .PROT TASK AT ANY TIME (CURRENTLY 3).
$I1
.SBMAX $T3 @THE MAXIMM NUMBER OF @S@B'S IN EXISTENCE -1 (CURRENTLY 7).
$I1
.SBLMAX $T3 @THE MAXIMUM LENGTH OF A .SB IN BYTES (CURRENTLY 256).
$I1
.TO .TARG .MAX $T3 @THE MAXIMUM NUMBER OF .ITP MESSAGES QUEUED TOWARDS THE
TARGET -1 (CURRENTLY 7).
$I1
.ITP .READY .MAX $T3 @THE MAXIMUM NUMBER OF .ITP READ FROM TARGET BUFFERS HELD
AT A TIME -1 (CURRENTLY 7).
$A INDENT=1
$P
@IF THE .NSI TASK IS TO INCREASE ITS .SB THROUGHPUT ( FOR LARGER NUMBERS OF
USERS) THEN THE .SB BUFFERING WILL HAVE TO BE INCREASED, THE NUMBER OF
.SB'S ALLOWED OUTSTANDING EACH WAY OVER THE NETWORK (NEGOTIATED AT ATTACH TIME)




WILL HAVE TO BE INCREASED AND PROBABLY A CHECK WILL HAVE TO BE MADE THAT NONE
OF THE .SB'S IN THE BUFFER POOL SPAN A .PDP 11 SEGMENT BOUNDARY (AS IN
.ERTE MK.3.2).
$P $I2 $L1UI
@THE @TSIM @TASK
$P
@MOST OF THE CONSTANTS INVOLVED IN .TSIM ARE THE SAME AS THOSE OF .TCP.
@THE TASK ASSUMES 1 PHYSICAL MULTIPLEXOR PER .SCRIPT TASK ( .TSC VERSION
OF THE .SCRIPT TASK ).

$N $I2 $L1CUI
SECTION 7 : DATA ANALYSIS
$P
@THIS SECTION DESCRIBES SOME DATA ANALYSIS PROGRAMS WHICH OPERATE ON
THE .XOT FILE PRODUCED BY THE .TCP (OR .TSIM) TASK. 
@.XOT FILES ARE STANDARD .DEIMOS TEXT FILES
AND CAN BE INSPECTED USING THE STANDARD SYSTEM
EDITOR.
@THE .XOT
FILE RECORDS, APPART FROM A HEADER, *< .TCP .VERSION> ,AND THE
TERMINATOR '+',HAVE THE FORMAT:-
$I2 $L1CI
 <TIME STAMP><RECORD TYPE><VIRT CONSL><LENGTH><MESSAGE>NL
WHERE RECORD TYPE MAY BE ONE OF:-
$A INDENT=2
$L3CI
1 = MESSAGE FROM SCRIPT TO EMAS
2 = FROM EMAS TO SCRIPT
3 = PROMPT MESSAGE SENT TO SCRIPT
$A INDENT=1
$P
@THE LENGTH IS IN CHARACTERS AND THERE IS NO MESSAGE TEXT FOR A
TYPE 3 RECORD.
@THE TIME STAMP IS IN 1/10TH SECOND TICKS (THIS WILL WRAP ROUND APPROXIMATELY
EVERY 55 MINUTES ).
$P
@FOR .ERTE MK.3, TYPE 1 RECORDS ARE PRODUCED WHENEVER A USER WOULD HAVE
COMPLETED TYPING AN INPUT LINE AND THE PACKET CORRESPONDING TO THAT LINE
IS FIRED OFF INTO THE NETWORK. @FOR .ERTE MK.4 TYPE 1 RECORDS ARE PRODUCED
WHEN THE INPUT LINE IS PASSED TO THE MULTIPLEXOR TASK FOR TRANSMISSION
TO THE TARGET, THERE WILL STILL BE SOME "TYPING DELAY" TO COME IN THIS CASE
CORRESPONDING TO @L CHARACTER TRANSMISSION TIMES ON THAT LINE (WHERE @L IS
THE LENGTH OF THE INPUT MESSAGE). @TYPE 2 AND 3 MESSAGES ARE PRODUCED AT 
SIMILAR POINTS IN BOTH MK.3
AND MK.4. ( HOWEVER IN MK.3 TYPE 2 MESSAGES CORRESPOND TO A PACKET BEING
RECEIVED AT A .TCP ON THE NETWORK WITH SEVERAL CHARACTERS PER PACKET, IN
MK.4 TYPE 2 MESSAGES ARE FOR INDIVIDUAL CHARACATERS BEING PRINTED ON A 
PARTICULAR LINE, HENCE .XOT FILES IN MK.4 TEND TO BE LARGER). @THE ANALYSIS
PROGRAMS ARE SET UP TO ALLOW FOR THE DIFFERENCE IN THE TIMING POINTS OF
TYPE 1 MESSAGES SO THAT THE FINAL RESULTS ARE EQUIVALENT.
$P
@ALL THE ANALYSIS PROGRAMS DESCRIBED HAVE EVOLVED TO MEET SOME OF
THE NEEDS OF THE ORIGINAL .SRC PROJECT. @THUS THEY HAVE BEEN SET UP
TO OBTAIN MEASUREMENTS FROM EXPERIMENTS USING THE .F1 AND .CS1BM WORKLOADS,
RUN UNDER THE STANDARD EXPERIMENT FORMAT (ONCE THE FIRST USER HAS STARTED
TO LOG ON, AN 8 MINUTE SETTLING PERIOD IS ALLOWED SO THAT ALL USERS CAN LOG ON
AND THE SYSTEM REACH SOME KIND OF STEADY STATE, THE TARGET'S PERFORMANCE IS
THEN MONITORED FOR A 30 MINUTES WINDOW, THE END OF THIS WINDOW MARKS THE END
OF THE EXPERIMENT ). @MONITORING UTILITIES INTERNAL TO THE TARGETS USED DURING
THE PROJECT HAVE ALSO BEEN PRODUCED WHICH WILL FOLLOW THIS FORMAT, THEY
ARE NOT DESCRIBED IN THIS DOCUMENT.
$P
@THE COMMON PERFORMANCE METRICS QUOTED ARE :
$A INDENT=4
$I1
.REACTION .TIME $T4 @THE TIME FROM THE USER TYPING THE LAST CHARACTER OF
HIS INPUT LINE UNTIL THE TIME THE TARGET OUTPUTS THE FIRST CHARACTER OF ITS 
REPLY (NOT COUNTING ANY ECHOED CHARACTERS). @THUS THIS REPRESENTS THE TIME THE
USER WAITS WITH NOTHING HAPPENING ON HIS CONSOLE.
$I1
.RESPONSE .TIME $T4 @THE TIME FROM THE USER TYPING THE LAST CHARACTER OF HIS 
INPUT LINE UNTIL ALL OF THE TARGET'S REPLY HAS BEEN TYPED AND THE TARGET'S
PROMPT MESSAGE REQUESTING FURTHER INPUT HAS ALSO BEEN TYPED. @THUS THIS 
REPRESENTS THE TIME (INCLUDING TYPING DELAY) IT TAKES THE TARGET TO
DEAL WITH A COMMAND AND MAKE ITSELF READY FOR THE NEXT.
$I1
.THROUGHPUT $T4 @THE MEAN NUMBER OF .REACTIONS COMPLETED PER MINUTE
$I1
.SATISFACTION .LEVEL $T4 @THE PERCENTAGE OF .REACTIONS COMPLETING WITHIN
2 SECONDS. @THE CUT OFF POINT OF 2 SECONDS IS CHOSEN AS .REACTION
TIME OF GREATER THAN THIS LEVEL CEASE TO BE INTERACTIVE. @THE DISTRIBUTIONS
OF .REACTION AND .RESPONSE TIME ARE OFTEN HEAVILY SKEWED AND MAY BE HEAVILY
INFLUENCED BY A SMALL NUMBER OF VERY LONG TIMES, THIS FIGURE GIVES SOME 
INDICATION OF THIS SKEWING.
$A INDENT=1
$P
@AS WITH .ERTE PROPER THESE PROGRAMS ARE WRITTEN IN .IMP-77 AND SHOULD BE
EASILY MODIFIED. @HOWEVER THE .IMP-77 COMPILER ON THE ORIGINAL CONFIGURATION
DID NOT HAVE %REAL ARITHMETIC AND A DOUBLE WORD ARITHMETIC PACKAGE WAS PRODUCED




TO GET ROUND THE EXTREME LIMITATIONS IMPOSED BY 16 BIT %INTEGERS. 
@THESE PROGRAMS
TEND TO USE THIS DOUBLE WORD ARITHMETIC PACKAGE HEAVILY [ @CURRIE 1976 ].
$B
$P $L1CUI
ALOG
$P
.ALOG IS AN ANALYSIS PROGRAM DEVISED TO OBTAIN MEANS FOR RESPONSE
AND REACTION TIMES. @TO RUN .ALOG, TYPE :
$L2
          ALOG <XOTFILE>/<DATA FILE>,<EXPANDED LOG>
.ALOG WILL PRINT:-
$I2 $L1CI
ERTE VRSN :
$P
@REPLY WITH 3 OR 4 CORRESPONDING TO .ERTE MK.3 OR MK.4.
@FOR REPLIES OF 4 (CORRESPONDING TO .ERTE MK.4 .XOT FILES) ,
TO ENABLE A CORRECTION TO BE MADE FOR CHARACTER TRANSMISSION TIMES TOWARDS
THE TARGET IN .ERTE MK.4.0 ,
.ALOG WILL THEN
GIVE TWO EXTRA PROMPTS :
$I2 $L1CI
CHARS PER UNIT :
$P
@THE REPLY TO THIS (AND THE NEXT REQUEST) IS TO GIVE AN INDICATION OF
 THE LINE SPEED TO WHICH ALL THE LINES WERE SET (MUST CURRENTLY
ALL BE THE SAME). .ALOG WILL THEN PROMPT (AGAIN MK.4 ONLY)
$I2 $L1CI
UNITS PER 1/10 SEC :
@REPLY WITH THE NUMBER OF 
UNITS (AS GIVEN AS REPLY TO THE PREVIOUS PROMPT)
PER 1/10 SECOND TICK.
@E.@G. 10 CHARACTER PER SECOND TERMINALS WOULD HAVE 1 CHARACTER PER UNIT 
AND 1 UNIT
PER 1/10 SECOND TICK.
 .ALOG WILL
THEN PROMPT (IN ALL VERSIONS)
$I2 $L1CI
GIVE MODE : ALL DATA=1,EXPAND LOG=2,SUMMARY ONLY=3,FIXED=4
$P
@RETURN THE MODE (MEANING AS FOLLOWS)
$A INDENT=3
$I2
1 $T3 @SUMMARY OF ACTIVITY OF EACH
VIRTUAL CONSOLE; THE THE NUMBER
OF RECORDS PROCESED ; THE TIME
INTERVAL MONITORED AND A
SUMMARY OF ALL CONSOLE
ACTIVITY.
$I2
2 $T3 @AS FOR 1 TO @STREAM 1 PLUS
EXPANDED .XOT FILE TO @STREAM 2
$I2
3 $T3 @AS FOR 1 TO @STREAM 1 MISSING
OUT INDIVIDUAL CONSOLE DATA
$I2
4 $T3 @AS FOR 1 BUT OVER FIXED TIME
PERIOD (SKIP FIRST 8 MINS THEN
ANALYSE FOR 30 MINS)
$A INDENT=1
$P
@FOR ALL MODES EXCEPT 4 , THE FOLLOWING PARAMETERS ARE REQUESTED
BY THE PROGRAM:-
$A INDENT=3
$I1
.MAX .RECORDS: $T3 @THE MAXIMUM NUMBER OF RECORDS
TO BE ANALYSED. (-1 MEANS ALL
POSSIBLE RECORDS).
$I1
.MAX .TIME: $T3 @THE MAXIMUM TIME (IN SECONDS )
TO BE ANALYSED (-1 MEANS THE
MAXIMUM POSSIBLE TIME).
$I1
.GRAPHS: $T3 @REPLY 1 MEANS PRINT GRAPHS OF
.REACTION TIMES, .RESPONSE TIMES,
.USER .DELAY TIMES (BOTH FOR RAW
DATA AND NORMALISED). @A REPLY
NOT EQUAL TO 1 MEANS DO NOT.
$I1
.SKIP .FIRST 8: $T3 @REPLY 1 MEANS SKIP FIRST 8
MINUTES IN FILE. @A REPLY NOT
EQUAL TO 1 MEANS DO NOT.
$P
@ALL MODES (INCLUDING MODE=4) WILL REQUEST A 
$I1
.TITLE: $T3 .ALOG WILL
READ IN THE NEXT LINE (UNTIL A 'NEWLINE' SYMBOL) TO BE OUTPUT ON ALL
ANALYSIS FILES.
$A INDENT=1
$P
@THE VIRTUAL CONSOLE DATA IS OF THE FORM:-
$A INDENT=2
$L10CI
1     NUMBER OF INTERACTIONS.
2     CHARACTERS INTO AND OUT OF THE TARGET.
3     CHARACTERS PER LINE INTO AND OUT OF THE TARGET.
4     RESPONSE TIME FROM A STIMULUS BEING GIVEN TO THE TARGET AND 
      THE TARGET BEING READY TO TAKE THE NEXT COMMAND.
5     REACTION TIME FROM A STIMULUS BEING GIVEN TO THE TARGET UNTIL 
      THE FIRST CHARACTER BEING RECEIVED FROM THE TARGET
6     THINK TIME.
7     TCP DELAY (TIME FROM FIRST REPLY TO PROMPT).
8     INTERACTION RATE PER MIN.
$P
@INFORMATION IS ALSO PRODUCED ON THE NUMBER OF
.REACTIONS COMPLETING WITHIN CERTAIN TIME RANGES (SATISFACTION LEVELS).
@N.@B. INTERACTION RATES WILL BE INCORRECT IF THE TIME INTERVAL MONITORED IS 
NOT AN INTEGERAL NUMBER OF 10 MINUTE PERIODS.
$P
@THE CURRENT VERSION IS 6.0 (14/3/79) AND IS SET UP FOR UPTO 128 TERMINALS.
$A INDENT=1
$B5
$P $L1CUI
BLOG
$P
.BLOG IS AN ANALYSIS PROGRAM TO OBTAIN .REACTION AND .RESPONSE TIMES,
.SATISFACTION .LEVELS AND A .COUNT OF .OCCURRENCES  FOR
SPECIFIC .TARGET COMMANDS. @TO RUN THE VARIOUS VERSIONS OF .BLOG, TYPE :-
$I2 $LCI
F1BLOG <XOTFILE>/<DATAFILE>,<LOGFILE>  (F1 STANDARD COMMANDS MK.3)
$I2 $LCI
CSBLOG <XOTFILE>/<DATAFILE>,<LOGFILE>  (CS1BM STANDARD COMMANDS MK.3)
$I2 $LCI
CVBLOG <XOTFILE>/<DATAFILE>,<LOGFILE>  (CS1BM STANDARD COMMANDS MK.4)






.BLOG WILL PROMPT:-
$I2 $LCI
ERTE VRSN :
$P
@REPLY WITH A 3 (FOR .ERTE MK.3) OR A 4 (FOR .ERTE MK.4). @FOR REPLIES
OF 4 .BLOG PROMPTS FOR 2 ADDITIONAL PIECES OF INFORMATION :
$I2 $LCI
CHARS PER UNIT :
$I2 $LCI
UNITS PER 1/10 SEC :
$P
@REPLY TO THESE AS FOR .ALOG TO INDICATE LINE SPEED SETTINGS. .BLOG THEN 
PROMPTS :
$I1 $LCI
MODE:
$P
@RETURN THE MODE AS FOLLOWS :-
$A INDENT=3
$I2
1 $T3 @MEASURE RESPONSE TIMES FOR
STANDARD SET OF COMMANDS .F1 - .(IMP,
.FORTE, .EDIT, .RUN, .LIST ), .CS1BM - .(IMP, .COPY, .E, .RUN, .FILES).
$I2
2 $T3 @AS FOR 1, BUT FOR A
USER-DEFINED COMMAND SET
$I2
3 $T3 @AS FOR 1, BUT OVER A FIXED TIME
PERIOD (SKIP 8 MINUTES, MEASURE FOR 30)
$I2
4 $T3 @AS FOR 2, BUT OVER A FIXED TIME
PERIOD (SKIP 8 MINUTES, MEASURE FOR 30)
$A INDENT=1
$B
.BLOG NEXT PROMPTS :-
$I2 $LCI
GRAPHS:
$P
@REPLY '1' IF GRAPHS OF RESPONSE TIMES (BOTH RAW DATA AND
NORMALISED) FOR EACH COMMAND ARE REQUIRED. @OTHERWISE, REPLY '0'.
$P
@FOR MODES 1 AND 2, THE NUMBER OF RECORDS TO BE SUMMARISED IS
ASKED FOR .(MAX .RECORDS), -1 MEANS ALL; DITTO THE MAX TIME IN
SECONDS. .BLOG WILL ANALYSE THE MAX RECORDS OR THE MAX TIME
POSSIBLE.
$P
@FOR MODES 2 AND 4, IN RESPONSE TO THE PROMPT:-
$I2 $LCI
COMMANDS FOR ANALYSIS:
A MAXIMUM OF 5 .TARGET COMMAND NAMES SHOULD BE INPUT, SEPARATED BY
SPACES ON ONE LINE. @IF GRAPHS ARE TO BE PRODUCED, THE MESSAGE:-
$I2 $LCI
SCALE FOR TIME TO PROMPT:
IS OUTPUT. @FOR EACH COMMAND TO BE MEASURED, THE GRAPH SCALE SIZE
SHOULD BE INPUT, BEARING IN MIND THAT THE MAXIMUM RESPONSE TIME
SHOWN ON THE GRAPH WILL BE 50*(SCALE SIZE) TICKS. @SIMILARLY, THE
MESSAGE:-
$I2 $LCI
SCALE FOR TIME TO REPLY:
IS OUTPUT, AND ANSWERED.
$P
@N.@B. FOR VERSIONS BEFORE VERSION 2.0 A 38 MINUTE WINDOW WAS USED
FOR MODES 3 AND 4. @IN THIS THE FIRST 8 MINUTES WERE NOT SKIPPED BUT
INCLUDED IN THE MAJORITY OF THE RESULTS, THE SATISFACTION LEVELS QUOTED
WERE ALSO WRONG AS THE COUNT OF GOOD REACTIONS WAS RESET AT THE END OF THE 
FIRST 8 MINUTES BUT THE TOTAL COUNT OF ALL .REACTIONS WAS NOT.
$P
@THE .LOG FILE PRODUCED ON STREAM 2 CONTAINS RECORDS OF THE FOLLOWING 
FORMAT
$L
         <RESPONSE TYPE><COMMAND TYPE><TIME>
WHERE:
$A INDENT=4
$I2
.RESPONSE .TYPE $T4 =0 FOR .RESPONSE TIMES, =1 FOR .REACTION TIMES.
$I2
.COMMAND .TYPE $T4 @LIES BETWEEN 0 AND 5 (INCLUSIVE) FOR THE TYPE
OF COMMAND FOUND
$I2
.TIME $T4 @IS THE ACTUAL .RESPONSE OR .REACTION TIME IN 1/10 SECOND TICKS.
$A INDENT=1
$P
@THIS FILE ALWAYS STARTS WITH THE TITLE LINE OF THE .BLOG RESULTS FILE
AND ENDS WITH A "-1". @THIS FILE IS NORMALLY SHIPPED UP TO A LARGER MAINFRAME
(VIA .T44)
FOR FURTHER STATISTICAL ANALYSIS WHICH IS IMPRACTICAL ON THE ORIGINAL .PDP 11.
$P
@CURRENT VERSIONS 2.0 (F1BLOG), 2.1 (CVBLOG), 2.2 (CSBLOG) (14/3/79)
ARE SET UP FOR UPTO 128 USERS.
$B5
$P $L1CUI
CLOG
$P
.CLOG IS AN ANALYSIS PROGRAM TO OBTAIN THE FREQUENCY OF USE OF
SPECIFIC .TARGET COMMANDS BY EACH VIRTUAL CONSOLE.
$P
@TO RUN .CLOG, TYPE :-
$I2 $LCI
CLOG <XOTFILE>/<DATA FILE>
$P
@THE PROMPTS AND RESPONSES FOR .CLOG ARE SIMILAR TO THOSE FOR
.BLOG. @HOWEVER ONLY TWO ARE USED (REPLY AS FOR .BLOG)
$L2
   .MODE :
   .COMMANDS .FOR .ANALYSIS :
$P
@OUTPUT
FROM .CLOG CONSISTS OF A SINGLE TABLE OF COMMANDS AGAINST VIRTUAL
CONSOLES, TOGETHER WITH ROW AND COLUMN SUB-TOTALS.
$P
@THERE IS NO TIMING INVOLVED WITH THIS PROGRAM AND IT WILL RUN ON .XOT
FILES FOR BOTH MK.3 AND MK.4. .CLOG IS ONLY SET UP FOR THE .F1
GROUP OF STANDARD COMMANDS.
$P
@CURRENT VERSION 2.2 (15/3/79) IS SET UP FOR UPTO 128 TERMNALS.
$A INDENT=1
$B5
$P $L1CUI
DLOG
$P
.DLOG IS AN ANALYSIS PROGRAM TO CHECK WHETHER OR NOT THERE HAVE
BEEN ANY UNTOWARD HAPPENINGS DURING THE RUN. @IT CURRENTLY SEARCHS
THE .XOT FILE FOR REPLIES FROM THE .EMAS NETWORK WHICH WOULD INDICATE
SOME TROUBLE. @THESE MESSAGES CURRENTLY ARE:
$I2
.EMAS?
$I2
** 2970 .DOWN
$I2
.SYSTEM .DOWN
$I2
.NO .USER .SERVICE
$I2
.SYSTEM .FULL
$I2
.INVALID .USER
$I2
.INVALID .PASSWORD
$I2
.INVALID .NAME
$I2
.NOT .AVAILABLE
$P
@TO RUN .DLOG, TYPE:-
$I2 $LCI
DLOG <XOTFILE>/<DATA FILE>
.DLOG WILL PROMPT:-
$I2
.TITLE:
$P
@IT WILL THEN READ IN THE NEXT LINE AS A TITLE LINE TO BE OUT
PUT AT THE HEAD OF THE DATAFILE.
$P
@THE OUTPUT WILL TELL THE NUMBER OF OCCURRENCES OF THE .EVIL
MESSAGES OVER THE FIRST 8 MINUTES, THE MONITORED WINDOW (THE NEXT 30
MINUTES) AND THE WHOLE FILE. @IT WILL ALSO CHECK THAT ALL THE
VIRTUAL CONSOLES MANAGED TO LOG-ON SUCCESSFULLY.
.DLOG IS CURRENTLY ONLY SET UP FOR USE WITH .ERTE MK.3 AND THE .EMAS TARGETS.
$P
@CURRENT VERSION 7 (15/11/78) IS CURRENTLY SET UP FOR UPTO 128 TERMINALS.
$A INDENT=1
$B5
$P $L1CUI
PLOG
$P
.PLOG IS AN ANALYSIS PROGRAM TO REPRODUCE THE 'CONSOLE LOG' OF
ANY VIRTUAL CONSOLE IN THE .XOT FILE.
$P
@TO RUN .PLOG, TYPE:-
$I2 $LCI
PLOG <XOTFILE>/<DATAFILE>
.PLOG WILL PROMPT:-
$I2
.MODE:
$P
.MODE=1 MEANS PRINT LOG OVER WHOLE FILE. .MODE=4 MEANS PRINT LOG
OVER MONITORED WINDOW ONLY.
$I2
.VIRT .CNSL:
$P
@REPLY WITH THE NUMBER OF THE VIRTUAL CONSOLE WHOSE LOG IS
REQUIRED. @IF LOGS ARE WISHED FOR A RANGE OF VIRTUAL CONSOLES THEN REPLY
-1. @IN THE CASE OF A -1 REPLY .PLOG WILL THEN PROMPT
$I2
.FIRST .CNSL :
$I2
.LAST .CNSL :
$P
@THE NUMBER OF THE LOWEST AND HIGHEST VIRTUAL CONSOLES 
OF THE GROUP OF CONSOLES WHOSE LOGS ARE REQUIRED
SHOULD BE THE REPLIES.
$I2
.MAX .RECORDS:
$P
@THE MAXIMUM RECORDS IN THE .XOT FILE WHICH SHOULD BE ANALYSED IN
PRINTING THE LOGS SHOULD BE THE REPLY (-1 MEANS ALL RECORDS).
$I2
.MAX .TIME:
$P
@THE MAXIMUM AMOUNT OF TIME IN THE .XOT FILE TO BE CONSIDERED
WHILE PRINTING OUT THE LOGS SHOULD BE THE REPLY (-1 MEANS THE WHOLE
FILE). @ALL TIMES ARE IN SECONDS.
$I2
.TITLE:
$P
@THE PROGRAM WILL READ IN THE NEXT LINE AND WILL OUTPUT IT AT
THE HEAD OF ALL THE LOGS IT PRINTS.
$P
.PLOG WILL THEN OUTPUT ALL MESSAGES GOING TO AND FROM THE
VIRTUAL CONSOLES IN QUESTION.@IT WILL APPEND THE TIMES AT WHICH THERE
IS ANY CHANGE IN THE DIRECTION OF THE MESSAGE FLOW AND WILL INDICATE
IN WHICH DIRECTION THE MESSAGES ARE FLOWING (I. E. TO OR FROM THE
.TARGET).
$P
.PLOG WILL RUN ON EITHER MK.3 OR MK.4 .XOT FILES BUT
HAS NOT BEEN ADJUSTED TO TAKE INTO ACCOUNT THE TIMING DIFFERENCES ON
INPUT BETWEEN THE MK.3 AND MK.4 AS IT WAS  NOT ENVISAGED  
THAT THIS UTILITY WOULD BE
USED TO GUAGE THOSE TIMES TO ANY GREAT ACCURACY.
$P
@CURRENT VERSION 1.2 (24/1/79) IS SET UP FOR UPTO 128 TERMINALS.
$B5
$P $L1CUI
OVERLORD
$P
.OVERLORD IS  UTILITY TO ANALYSE SEVERAL .XOT  FILES IN ONE RUN.
@THIS PROGRAM WILL SEARCH ALL THE FILE SYSTEMS ON A LOGICAL DISC UNIT
FOR .XOT FILES; ONCE IT FINDS ONE IT WILL CALL A VERSION OF .DLOG (NAMED
.DLIG ) TO CHECK IF THE RUN WAS SUCCESSFULL. @IF THE RUN WAS A SUCCESS
THE A VERSION OF .ALOG ( .ALIG ) WILL BE CALLED TO ANALYSE THE FILE AS
FOR MODE 4 OF .ALOG, IT WILL ALSO PRINT OUT CORRECTED VALUES FOR THE
MAJOR PERFORMANCE METRICS TAKING INTO ACCOUNT ANY MESSAGES RESULTING
FROM UNSUCCESSFULL LOG ONS. @THEN A VERSION OF .BLOG ( .BLIG ) IS CALLED
AS THOUGH FOR MODE 3 OF .BLOG. @ONCE THE ENTIRE LOGICAL UNIT HAS BEEN SCANNED
THE PROGRAM WILL ASK IF THE FILES CREATED SHOULD BE PRINTED (VIA THE @C.@S.
.FILESTORE PRINTER) AND THEN DESTROYED. @ALL REPLIES TO .OVERLORD PROMPTS
ARE ON A SINGLE LINE. @TO RUN .OVERLORD, TYPE :
$A INDENT=3
$I3
.OVER
$P
.OVER WILL REQUEST
$I1
.XOT .UNIT :
$P
REPLY WITH THE NUMBER OF THE LOGICAL DISC UNIT TO BE SCANNED. .OVER
WILL THEN REQUEST
$I1
.TITLE :
$P
@THE LINE, TYPED IN WILL BE COPIED ONTO THE TOP OF ALL FILES PRODUCED
DURING THE RUN. .OVERLORD WILL THEN, TYPE OUT SOME INFORMATION ON THE
RESULTS IT IS ABOUT TO PRODUCE AND THEN START TO ANALYSE .XOT FILES. @WHEN
ALL THE FILE SYSTEMS HAVE BEEN CHECKED IT WILL THEN REQUEST
$I1
.PRINT :
$P
@REPLY WITH "Y" TO HAVE ALL FILES PRODUCED PRINTED ON THE .FILESTORE PRINTER,
 "N" IF NOT. .OVER WILL THEN PROMPT
$I1
.DELETE :
$P
@REPLY WITH "Y" IF ALL FILES GENERATED DURING THE RUN ARE TO BE DESTROYED,
"N" IF NOT.
$A INDENT=1
$P
@DURING THE RUNNING OF .OVER, .DLIG WILL PRODUCE FILES CALLED .CERT IN THE
SAME FILE SYSTEM AS ANY .XOT FILE IT FINDS, .ALIG ( IF CALLED ) WILL
PRODUCE FILES CALLED .RESL AND .BLIG WILL PRODUCE FILES CALLED .BLOG. @ALL
THSES FILES ARE CREATED ON LOGICAL DISC UNIT 0.
@EACH FILE PRODUCED WILL HAVE A COPY OF THE TITLE LINE PRINTED AT ITS HEAD
AND WILL HAVE THE NUMBER OF THE FILESYSTEM IN WHICH THE CORRESPONDING .XOT
FILE WAS FOUND APPENDED TO THIS TITLE LINE.
$P
@THIS PROGRAM WILL REQUIRE THE @C.@S. DEPARTMENT .FILESTORE TO SPOOL ALL
PRINTING OF THE RESULTS FILES. @NO VERSION OF .OVERLORD HAS BEEN PRODUCED YET
FOR .ERTE MK.4.0 ( OWING TO THE LACK OF .DLOG FOR THESE .XOT FILES ).
@WHEN THE CHANGE IS MADE TO RUN THIS ON MK.4 .XOT FILES BOTH .BLIG AND
.ALIG WILL REQUIRE MINOR CHANGES, THE CHANGES IN .BLIG ARE ESSENTIALLY THE SAME
AS THOSE INDICATED IN THE .BLOG LISTINGS.
$P
@CURRENT VERSION 1.3 (15/11/78) USES " .LIG " VERSIONS SET UP FOR 
UPTO 128 TERMINALS.
@THE CURRENT VERSIONS ARE:
$I2
.ALIG  - AUTO 1.3 (18/12/78).
$I2
.BLIG  - AUTO 2.0 (16/3/79), .CS1BM STANDARD COMMANDS.
$I2
.BLIG  - AUTO 2.1 (16/3/79), .F1 STANDARD COMMANDS.
$I2
.DLIG  - AUTO 1.4 (16/3/79).
$B5
$N $I2 $L1CUI
SECTION 8 : SCRIPT FILE UTILITIES
$P $L1CUI
ANAL
$P
.ANAL IS A UTILITY FOR CHECKING OUT INDIVIDUAL .SCRIPT FILES MADE UP
TO .ERTE MK.3 STANDARD. @IT WILL CHECK THAT THE FILE IS IN THE CORRECT
FORMAT AND GIVE A COMPACTED LISTING OF THE FILE, SOME INFORMATION ON
THE INPUT CHARACTER RATE AND THINK TIMES CONTAINED IN THE FILE AND IF
REQUIRED A CLEANED UP VERSION OF THE FILE. @TO RUN IT, TYPE :
$L
         .ANAL <SCRIPTFILE>/<LISTING FILE>,<NEW SCRIPT FILE>
$P
.ANAL WILL PROMPT
$L
   .GIVE .SCRIPT .FILE NAME :
$P
@REPLY WITH THE NAME OF THE .SCRIPT FILE INVOLVED (THE WHOLE LINE IS READ AND
REPRODUCED ON TOP OF ALL LISTING FILES AS WITH THE .TITLE LINE IN THE .XOT
ANALYSIS PROGRAMS). .ANAL WILL THEN PROMPT
$L
         .MODE :
$P
@WHERE
$A INDENT=3
$I2
.MODE=1 $T3 @PRINT COMPACTED LISTING FILE AND PRODUCE SUMMARY OF THINK TIME
AND CHARACTER INPUT PRODUCED BY THIS SCRIPT.
$I2
.MODE=2 $T3 @ONLY PRINT THINK TIME AND CHARACTER INPUT SUMMARY.
$I2
.MODE=3 $T3 @CREATE NEW .SCRIPT FILE ON STREAM 2, REMOVING ALL REDUNDANT SPACES
IN CHECK LINES AND THINK TIME LINES. @THIS MODE WAS ALSO USED TO TRANSLATE
THE ORIGINAL .F1 SCRIPTS WHICH HAD THE PRE-NETWORK LOGON SEQUENCES.
$A INDENT=1
$P
@CURRENT VERSION 1.4 (15/3/79).
$B5
$P $L1CUI
SCRIPT ANALYSER
$P
@THE .SCRIPT .ANALYSER IS A SPECIALLY MODIFIED VERSION OF .ERTE WHICH WILL
RUN THROUGH A SET OF SCRIPTS (DEFINED BY A SINGLE .TKPAR FILE) AND WILL CHECK
THAT THEY ARE VALID AND PRODUCE SOME STATISTICS ON THE EXPECTED TYPING AND
THINK TIME DELAYS AS WELL AS INFORMATION ON THE DISTRIBUTION OF DISTINCT
INPUT LINES. @TO RUN IT THE .TKPAR FILE, THE .SCRIPT .ANALYSER AND THE
SPECIALLY MODIFIED .SCRIPT TASK (WHICH CURRENTLY TAKES UPTO 48 CONSOLES) MUST
ALL BE IN THE SAME FILE SYSTEM ON UNIT 0. @IT IS NOT RECOMMENDED THAT THIS
UTILITY BE RUN IN FILE SYSTEMS USED FOR NORMAL .ERTE WORK. @THIS IS CURRENTLY
ONLY SET UP FOR MK.3. @WHILE RUNNING THE MODIFIED .SCRIPT TASK REMOVES LINES
OF INPUT FROM THE .SCRIPT FILES, LOGS THE THINK TIMES AND INPUT LINE, AND THEN
PAUSES FOR A FIXED RESPONSE TIME ( 3 SECONDS) BEFORE GOING ONTO THE NEXT INPUT
LINE FOR THAT SCRIPT. @CURRENTLY UPTO 48 SCRIPTS CAN BE HANDLED AT ONCE IN THIS
SINGLE MODIFIED .SCRIPT TASK, BUT THERE CAN ONLY BE 1 .TKPAR FILE. @TO USE 
THIS, TYPE:
$L
         .SCRIPY
$P
@THE .TIMER TASK WILL THEN BE LOADED AND AN APPROPRIATE MESSAGE PUT OUT.
@IT WILL PROMPT  :
$L
         @NUMBER OF TASKS :
$P
@REPLY WITH A 1.
@THERE IS NO REASON WHY FURTHER SPECIAL .SCRIPT TASKS SHOULD NOT BE MADE UP
AND RUN IN PARALLEL. @HOWEVER THEY WOULD EFFECTIVELY EACH PRODUCE INFORMATION
ON THE PARTICULAR BENCHMARK DEFINED IN THEIR OWN .TKPAR FILE AND THIS
DATA WOULD NOT BE MERGED IN ANY WAY. @THERE MAY ALSO BE SOME CONFUSION AS
TO WHAT INFORMATION IS COMING FROM WHICH SPECIAL .SCRIPT TASK AS ALL OUTPUT
IS CURRENTLY TO THE CONSOLE AND NOT TO A FILE ( IT IS A TRIVIAL
OPERATION TO PUT THE OUTPUT TO A FILE FOR EACH SPECIAL SCRIPT TASK).
$P
.SCRIPY WILL NEXT OUTPUT A MESSAGE SAYING HOW MANY SCRIPTS IT IS ANALYSING
(SIMILAR TO THAT PUT OUT BY A NORMAL .ERTE .SCRIPT TASK ON START UP) AND
WILL PROCEED. @THE ANALYSIS CAN TAKE SOME TIME. @ALL THE .INT MECHANISMS
FOR THE NORMAL .SCRIPT TASK APPLY TO THIS SPECIAL .SCRIPT TASK (WHICH
IS ALSO USUALLY CALLED .TSK). @WHEN THE .SPECIAL .SCRIPT TASK HAS
FINISHED (EITHER ALL SCRIPTS REACH STATE 7 OR AN .INT @A IS GIVEN) THEN
THE FOLLOWING DATA IS PUT OUT ON THE CONSOLE (THE PRINTING CAN TAKE
SOME TIME).
$A INDENT=4
$I2
@BUFFER @USAGE $T4 @DATA ON THE USAGE OF THE INTERNAL SCRIPT BUFFERS HELD
BY THE .SCRIPT TASK. @THIS CAN BE VERY USEFUL IN TUNING THE BUFFER SIZE
HELD BY THESE TASKS FOR ANY PARTICULAR BENCHMARK.
$I2
@INPUT @TEXT $T4 @DATA ON THE NUMBER OF OCCURENCES OF VARIOUS LINES OF 
INPUT TEXT IN THE BENCHMARK. 
@THESE DISTINCT INPUT LINES ARE CURRENTLY DEFINED AS
DISTINCT SETS OF LETTERS
OCCURING BEFORE A "(" OR ANY NUMBER. @THIS CAN BE USEFUL IN OBTAINING COUNTS
OF VARIOUS TARGET COMMANDS ETC IN A BENCHMARK FOR VALIDATION.
$I2
@DISTRIBUTIONS $T4 @GRAPHS OF THE DISTRIBUTIONS 
OF .INPUT .LINE .LENGTH, .THINK .TIME AND .TOTAL
.DELAY FROM THE .USER ( .THINK .TIME + .TYPING .DELAY ).
$I2
@COMMAND @COUNT $T4 @A COUNT OF THE TOTAL NUMBER OF COMMANDS IN EACH
SCRIPT IN THE BENCHMARK.
$A INDENT=1
$P
@WHEN THE TEST RUN IS COMPLETE THE .TIME TASK WILL STILL
BE RUNNING, THIS CAN BE .PURGED OR THE SYSTEM MAY BE
RE.IPL'D.
@THE SOURCE FILE FOR THE SPECIAL .SCRIPT FILE IS USUALLY CALLED .SCAN.
@AS THIS IS USING A VERY NON STANDARD .SCRIPT FILE IT IS ADVISED THAT
THIS BE RUN IN A COMPLETELY SEPARATE FILE SYSTEM FROM NORMAL .ERTE WORK.
$P
@CURRENT VERSION 2 (22/2/78).
$B5
$P $L1CUI
SCRIPT TRANSLATOR
$P
@THIS UTILITY IS SET UP FOR .ERTE MK.3 SCRIPTS. @IT TAKES A SET OF .SCRIPT 
FILES ALL RESIDING AN THE SAME UNIT AND FILE SYSTEM
WHOSE FILE NAMES ALL SHARE THE SAME FIRST 4 CHARACTERS (KNOWN AS A FAMILY)
AND CREATES A NEW FAMILY ON A NOMINATED UNIT AND FILE SYSTEM. @THIS NEW
FAMILY IS A DUPLICATE OF THE ORIGINAL (PERHAPS IT SHOULD BE CALLED CLONING).
 @IT ALSO CHANGES THEIR 
TARGET USER NUMBER FAMILY NAMES TO A NEW FAMILY ( @E.@G.
 IT CAN TRANSLATE ALL .ECSB TO .XXYY IF REQUIRED TO MAKE UP A FURTHER SET
OF SCRIPTS FOR A PARTICULAR BENCHMARK). @IT IS CURRENTLY BASED HEAVILY ON
REQUIREMENTS TO INCREASE  WORKLOAD SIZE ON THE
.EMAS TARGETS AND HAS BEEN USED TO SET UP NEW .F1 AND .CS1BM BENCHMARK
UNITS BY REPLICATING CURRENT ONES. @TO RUN THIS, TYPE :
$L
      .SCTR
$P 
@IT WILL PROMPT
$L
   .OLD .FILE .GROUP :
$A INDENT=4
$T2 @REPLY WITH SOMETHING OF THE FORM
$L
               <LOGICAL UNIT>.<FAMILY NAME>(<FILE SYSTEM>)
$I2
.LOGICAL .UNIT $T4 @IS THE LOGICAL DISC UNIT HOLDING THE ORIGINAL .SCRIPT
FILE FAMILY
$I2
.FAMILY .NAME $T4 @IS THE FIRST 4 CHARACTERS OF THE .SCRIPT FILE NAME,
COMMON TO ALL FAMILY MEMBERS.
$I2
.FILE .SYSTEM $T4 @IS THE FILE SYSTEM HOLDING THE ORIGINAL .SCRIPT FILES
(IN OCTAL).
$A INDENT=1
$P
@E.@G. 3$.SCRP(21)
$L
   .NEW .FILE .GROUP :
$P
@REPLY IN THE SAME FORMAT AS ABOVE TO DEFINE THE NEW .SCRIPT FILE FAMILY
NAME. .SCTR WILL NEXT PROMPT
$L
   .OLD .JOB .NO :
$P
@REPLY WITH THE 4 CHARACTER FAMILY NAME OF THE TARGET USER NUMBER USED BY ALL
THE SCRIPTS IN THE ORIGINAL .SCRIPT FILES.
$L
   .NEW .JOB .NO. :
$P
@REPLY WITH THE 4 CHARACTER FAMILY NAME OF THE TARGET USER NAME TO BE USED BY
ALL THE SCRIPTS IN THE NEW .SCRIPT FILES. .SCTR WILL CALL A PROGRAM NAMED .TRIN
FOR EACH FILE OF THE FAMILY IT COMES ACROSS. .TRIN WILL COPY THE ORIGINAL FILE
INTO A NEW ONE AND AT THE SAME TIME WILL TRANSLATE ALL OCCURENCES OF TEXT IN
THE FORMAT < .OLD .JOB .NO >< 2 DIGITS > INTO < .NEW .JOB .NO >< 2 DIGITS >
@E.@G IT COULD CHANGE THE JOB NUMBERS FROM .ECSB TO .GUWS.
$P
@CURRENT VERSION 1.1 (22/11/78).
$N $I2 $L1CUI
SECTION 9 : OTHER RELEVANT DOCUMENTATION
$P
.ADAMS @J.@C. "@THE @EXPERIMENTOR'S @GUIDE FOR .EMAS 4/75"
$I2
.ESP @REPORT 1978
$P
.ADAMS @J.@C. "@THE @EXPERIMENTOR'S @GUIDE FOR .EMAS 2900"
$I2
.ESP @REPORT 1978
$P
.ADAMS @J.@C. "@THE @INSTANT .ERTE @GUIDE"
$I2
.ESP @REPORT 1978
$P
.ADAMS @J.@C. .CURRIE @W.@S. AND .GILMORE @B.@A.@C. "@THE
@STRUCTURE AND @USES OF @THE @EDINBURGH @REMOTE @TERMINAL @EMULATOR"
$I2
.CS .DEPT @REPORT .CSR-12-77 1977 AND @SOFTWARE @PRACTICE
AND @EXPERIENCE VOL. 8 NO. 4 1978
$P
.BREBNER @G.@J. "@THE .MAVIS @USER'S @GUIDE"
$I2
.ESP @REPORT 1977
$P
.BREBNER @G.@J. " .MAVIS - @A @SCRIPT @GENERATOR FOR .ERTE"
$I2
.ESP @REPORT 1977
$P
.BREBNER @G.@R. "@NODDY @EXPLORES @THE @NETWORK - .T44, @THE @SINGLE @USER
.NSI @WORK @STATION"
$I2
.ESP @REPORT .NOV 1978
$P
.CURRIE @W.@S. "@THE @UTILITY @ROUTINES"
$I2
.ESP @REPORT .MARCH 1977
$P
.GILMORE @B.@A.@C. "@USER @MANUAL FOR .DEIMOS - @AN @OPERATING @SYSTEM
 FOR THE .PDP 11"
$I2
.ERCC .MAY 1978
$P
.ROBERTSON @P.@S.@R. "@THE .IMP-77 @LANGUAGE"
$I2
.CS .DEPT @REPORT .CSR-19-77 1977
$P
.SHAW @S. "@BENCHMARK @UTILITIES ON THE 2970"
$I2
.EMAS 2900 @DOCUMENTATION .ERCC .NOV 1978
$P
.SHAW @S. "@SETTING @UP @PROCESSES FOR THE .F1 @BENCHMARK"
$I2
.EMAS 2900 @DOCUMENTATION .ERCC .NOV 1978
$E