Google
 

Trailing-Edge - PDP-10 Archives - BB-M856A-BB - sprins.exe
There are 22 other files named sprins.exe in the archive. Click here to see a list.
?p @ @  ?xgCYKb)b<Kb`INXQF:z3~'B?{rE@@'J
'r+*>	` 2EsB@)9B?xH0JANFEBMARAPRMAYJUNJULAUGSEPOCTNOVDECPM21 pHEINXgB,@Kb(\INX),0GJ!##`phNow type: SAVE SPRINS<cr>F4 p4%G-G3,&(''(0  )%FG-G[ pHSPEAR.MSG`p4B		@p~A'2G- p	T p	V	]	g pD pE paik`pXB p
 p
 p`p
Hf
`p
sB p
r p
rp p0@p ph pk pm pq p
s pu pw pw JKPLLQ!DJXhM[hlk p p p8 p: p< p> p@ pA p
D pG pJ p
L pU pX`p]BA??C FCDG  p	 p p p p pKQ p% p& p& p] p] p^@p@p@p p p p p p p p p p p	 p
p p" p" p" p" p" p" p"c p"c p"d p"d p"e p"e$ $"$$$$&$(apTE@$TEp0 ap$1TG$60 $b '	$T``$bp'
$T`` $c@!'$T``%$d&'$T``$*$d`+'$T``)/$e00'$T``.4$f5'$T``3 p' p'@p@pU 5E*@pE* /@p p' p') p'2 p'3 p'4'6 p': p': p'; p';(H(W@)?R$'/'/'22@'Q2@E@rBKf/.G-rBQE2@Q rBr,T2@ac,b,Hg$2@.	$
$2@Pu!S<cr>
2@X5@
2@WhC2@r,G^G-Yd2@CadG-G-Yd2@IoG-
./2@G=E[g2@F 2@J[N82@PAf^2@r,2@P+YG0G0GHGG2@_(f\Cz2@r7G_G_P2@^l,G_G_ p p p p p p p pDSK:SPEAR.MSGBE*PfPzP{@2@MP`pBE*PCn"Pu"Pv"@"G02@MV"G-GHGGG0G.@pG^#"G02@[G1G0G^G0"G02@Q2G02@_((mCz2@r7P2@^l,EMi)^&*xpG)`de)^T_M$aDKSi)^&*xpM)bde)^T_M$aJQii)^&*yPS)ede)^T_M$aPXiiM)^&*&!z0ZTbU)gfU)^T`%V@c-GMWi
o'?{u)^&*&,&-&/&0)i)j)l)m)o{ iTb)pbu)^T_-$M]@mii)^&*}o)rde)^T_M$alsii)^&*}u)tde)^T_M$aryi<&*)^}{)wde)^T_M$axi7<`8>*W>AY7*<2>fn7o:j7A=|}:J<I:%=+8Ka@=eW>o!n@8b<wJ
:<3>X3)7X<:S8Ba8=%O)=N84&*)y)z)|)})*******	**
************* *!*#*$*&*'*)***,*-*/*0*2*3*5*6*8*9*;*<*>*?*A*B*D*E*G*H*J*K*M*N*P*Q0<U*hdTa~siWm/E[q3I_uHW   ] s!	!!5!K"!"S##0#M#q$$*$@$V$l%%;%Q%g%}&&0&>&['r(((4(C(Y(v)')6)E)T)x*A*W+++-+<+`,,2,A,W,m---/-L.5.K.a.w///M/\/k/z00`0v1.1=1L1[12D2S2b2x33%3;3Q3g3v4
3&**X*Z*\*^*`*b*d*f*h*j*l*n*p*r*t*v*x*z*|*~++++++
+
++++++++++ +"+$+&+(+*+,+.+0+2+4+6+8+:+<+>+@+B+D+F+H+J+L+N+P+R+T+V+X+Z+\+^+`+b+d+f+h+j+l+n+p+r+t+v+x+z+|+~,,,,,,
,
,,,,,,,,,,,"}'UDPc@UE?,i3&*,F}-,Gde,FTM$a*2i9&*,FX3,Ide,FTM$a08i?&*,F89,Kde,FTM$a6>iE&*,F?,Mde,FTM$a<DiW&*,FxE,Ode,FTM$aBJWi-,F&*&!XL,QfU,FT`%HSi]-]pK,&*,F&,&-&/&0&2HWTb,Sbu,FT-$MO@\Wc&*,Fx],Tde,FTM$aZbWp&*,FXc,Vde,FTM$a`hpW],F&*&!8j,YfU,FT`%foWv&*,F(p,Zde,FT*M$amuW|&*,Fv,\de,FT+M$as{W&*,Fh|,^de,FT,M$ayW&*,FH,`de,FT-M$aW&*,F(,bde,FT-M$aaqyW&*,F.Hz-de,FTM$awW&*,F,9,;/(-
de,FT_M$a}W&*,F0(-
de,FTM$aF0(-de,FTM$aW&*,F1h-de,FTM$aW &*,F2H-de,FTM$aW&&*,F3( -de,FTM$a%W,&*,F4&-de,FTM$a#+W2&*,F4h,-de,FTM$a)1W8&*,F5H2-de,FTM$a/7W>&*,F6(8-de,FTM$a5=KW,F&*7>-e5,FTu$u;CKWp,F&*&!7E-!fU,FT`%AJWQ&*,F8XK-"de,FTM$aHPWW&*,F98Q-$de,FTM$aNVW]&*,F:W-&de,FTM$aT\Wc&*,F:x]-(de,FTM$aZbWi&*,F;Xc-*de,FTM$a`hWo&*,F<8i-,de,FTM$afnWu&*,F=o-.de,FTM$altW{&*,F=xu-0de,FTM$arzW&*,F>X{-2de,FTM$axW&*,F?8-4de,FTM$a~W
W&*,F@x
W&*,FAX-:de,FTM$aW&*,FB8-<de,FTM$a,W,F&*C->e5,FTu$u$,WK,F&*&!B8&-AfU,FT`%"+W2&*,FDh,-Bde,FTM$a)1W8&*,FEH2-Dde,FTM$a/7W>&*,FF(8-Fde,FTM$a5=WD&*,FG>-Hde,FTM$a;CWJ&*,FGhD-Jde,FTM$aAIWW,F&*HHJ-Lde,FTM$aGOWi-j&*}Q-lde-jTM$aNUii-j&*JW-nde-jTM$aT\iiW-j&*&!Jp^TbU-pfU-jT`%Z@eiQ{sq-j&*&,&-&/&0-rK`iTb-sbu-jT-$Ma@nwiw}-j&*-u-wMqU`-z-jTHl@uii-j&*Nw.de-jTM$at{ii-j&*M}.de-jTM$az	i-j&*M.de-jTM$ai-j&*M	.de-jTM$a  i)-a-c-j&*-eMTcE.
@)<)&&&)-jR .f-jTaU%x)<&&&)-jS .f-jTaU%x&077i@-a-c-j&*-eM)TcE.-jTa5%3#@.@<@&&&)-jU0.f-jTaU%x,5@<&&&)-jV7.f-jTaU%x3=GNGiW-a-c-j&*-eM@TcE.-jTa5%3:@EW<&&&)-jXG.!f-jTaU%xCLW<W&&&)-jXpN.$f-jTaU%xJT^e^in-a-c-j&*-eMWTcE.'-jTa5%3Q@\n<&&&)-jZp^.*f-jTaU%xZcn<n&&&)-j[`e.-f-jTaU%xaku||i-a-c-j&*-eMnTcE./-jTa5%3h@s<&&&)-j]`u.2f-jTaU%xqz<&&&)-j^P|.5f-jTaU%xx

i-a-c-j&*-eMTcE.8-jTa5%3@
<&&&)-j`P
.;f-jTaU%x<&&&)-ja@.>f-jTaU%x#**i3-a-c-j&*-eMTcE.@-jTa5%3@!3<3&&&)-jc@#.Cf-jTaU%x(3<&&&)-jd0*.Ff-jTaU%x&0:AAiJ-a-c-j&*-eM3TcE.I-jTa5%3-@8J<J&&&)-jf0:.Lf-jTaU%x6?J<&&&)-jg A.Of-jTaU%x=GQXQia-a-c-j&*-eMJTcE.Q-jTa5%3D@Oa<&&&)-ji Q.Tf-jTaU%xMVa<a&&&)-jjX.Wf-jTaU%xT^hohiu-a-c-j&*-eMaTcE.Z-jTa5%3[@fu<&&&)-jlh.]f-jTaU%xdmu<u&&&)-jmo.`f-jTaU%xksii-j&*mpu.bde-jT_M$aryi-j&*M{.ede-jT_M$ax
i-j&*M.gde-jT_M$a~i!-a-c-j&*-eM
TcE.j-jTa5%3@!<!&&&)-jq.mf-jTaU%x//i8-a-c-j&*-eM!TcE.r-jTa5%3@&8<8&&&)-jt(.uf-jTaU%x$-8<&&&)-ju/.xf-jTaU%x+5?F?iO-a-c-j&*-eM8TcE.{-jTa5%32@=O<&&&)-jw?.~f-jTaU%x;DO<O&&&)-jwpF/f-jTaU%xBLV]Vif-a-c-j&*-eMOTcE/-jTa5%3I@Tf<&&&)-jypV/f-jTaU%xR[f<f&&&)-jz`]/	f-jTaU%xYcmtti}-a-c-j&*-eMfTcE/
-jTa5%3`@k}<}&&&)-j|`m/f-jTaU%xir}<&&&)-j}Pt/f-jTaU%xpzi-a-c-j&*-eM}TcE/-jTa5%3w@<&&&)-jP/f-jTaU%x	<&&&)-j@/f-jTaU%x""i+-a-c-j&*-eMTcE/-jTa5%3@+<+&&&)-j@/ f-jTaU%x +<&&&)-j0"/#f-jTaU%x(299iB-a-c-j&*-eM+TcE/%-jTa5%3%@0B<B&&&)-j02/(f-jTaU%x.7B<&&&)-j 9/+f-jTaU%x5?IPIiY-a-c-j&*-eMBTcE/.-jTa5%3<@GY<&&&)-j I/1f-jTaU%xENY<Y&&&)-j	P/4f-jTaU%xLV`g`im-a-c-j&*-eMYTcE/6-jTa5%3S@^m<&&&)-j`/9f-jTaU%x\em<m&&&)-j
g/<f-jTaU%xckii-j&*
pm/?de-jT_M$ajqii-j&*Ms/Ade-jT_M$apx
i/_&*}y/ade/_T_M$av~
iy/_&*&!/cfU/_T`%|iy04)9;N;/_&*&,&-&/&0&2&3
Tb/dbu/_T_-$M@
0&*H0de0T_M$a
0&*00de0T_M$a0
0&*0de0T_M$a$0
0&*&!p&TbU0fU0T`%"@,6
60&*&,&-&/&0`0Tb0TM$a3;0DLD&*/v/w0`>0de0TM$a9BL00&*`D0de0TM$aAI0RZR&*/v/w0`L0de0TM$aGPZ00&*@R0de0TM$aOW0`h`&*/v/w0@Z0de0TM$aU^h00&* `0de0TM$a]e0nvn&*/v/w0 h0de0TM$aclv00&*n0"de0TM$aks0||&*/v/w0v0$de0TM$aqz00&*`|0'de0TM$ay0&*0`0)de0TM$a060&*&!  	TbU0+fU0T`%@ 0)/y/{0&*/}!TcE0.0Ta5%3
@)<&&&)0" 00f0TaU%x)<)&&&)0# 03f0TaU%x&0700@/y/{0&*/}" )TcE050Ta5%3#@.@<&&&)0%008f0TaU%x,5@<@&&&)0&70:f0TaU%x3=GNN0W/y/{0&*/}%@TcE0=0Ta5%3:@EW<W&&&)0(G0?f0TaU%xCLW<&&&)0(pN0Bf0TaU%xJT^ee0n/y/{0&*/}(WTcE0D0Ta5%3Q@\n<n&&&)0*p^0Gf0TaU%xZcn<&&&)0+`e0If0TaU%xaku||0/y/{0&*/}*pnTcE0L0Ta5%3h@s<&&&)0-`u0Nf0TaU%xqz<&&&)0.P|0Qf0TaU%xx

0&-&/0&*0R-`Tc
<&&&)00P
0Wf0TaU%x<&&&)01@0Zf0TaU%x#**03/y/{0&*/}0PTcE0\0Ta5%3@!3<3&&&)03@#0_f0TaU%x(3<&&&)040*0af0TaU%x&0:AA0J/y/{0&*/}3@3TcE0d0Ta5%3-@8J<J&&&)060:0ff0TaU%x6?J<&&&)07 A0if0TaU%x=GQXQ0a/y/{0&*/}60JTcE0k0Ta5%3D@Oa<&&&)09 Q0nf0TaU%xMVa<a&&&)0:X0pf0TaU%xT^hoo0u/y/{0&*/}9 aTcE0s0Ta5%3[@fu<u&&&)0<h0uf0TaU%xdmu<&&&)0=o0xf0TaU%xks000&*u0zde0T_M$ary00&*{0|de0T_M$ax0{0&*&!?0TbU0~fU0T`%~@0{+'
0&*&,&-&/@ Tb1bu0T_-$M@+'1&#&*A01!de1T_M$a+'1&#&*&!B(1#fU1T`%$2'PA V"%4&0&[1&#&*&,&-&/&0&2&3&5&6&8&9C(+1&bu1T_-$M0P'+1&#&*E821(de1T_M$a.8P'+21&#&*&!F(:1+fU1T`%5GW'+2Wm/E[q3I_u	1&#&*&,&-&/&0&2&3&5&6&8&9&;&<&>&?&AG(P1.bu1T_-$M=U^'P1&#&*JW10de1T_M$aS\m'P1&#&*Jx^13de1T_M$aZdm'PW1&#&*&!Khf16fU1T`%akt'P1&#&*Lhm18de1T_M$air'P1&#&*MXt1;de1T_M$apz'Pm1&#&*&!NH|1>fU1T`%w
'P1&#&*OH1Ade1T_M$a'P1&#&*P8
1Dde1TM$a'P1&#&*&!Q(1GfU1T`%1&#&*S 1Lde1TM$a&/'P1&#&*&!T(1OfU1T`%#-6'P1&#&*U/1Rde1TM$a+4E'P1&#&*Ux61Tde1TM$a2<E'P/1&#&*&!Vh>1WfU1T`%9CL'P1&#&*WhE1Zde1TM$aAJ['P1&#&*XXL1\de1TM$aHR['PE1&#&*&!YHT1fU1T`%OYb'P1&#&*ZH[1bde1TM$aW`q'P1&#&*[8b1dde1TM$a^hq'+[1&#&*&!\(j1gfU1T`%eox'P1&#&*](q1jde1TM$amv'P1&#&*^x1mde1TM$at~'Pq1&#&*&!1pfU1T`%{'P1&#&*`1rde1TM$a
'P1&#&*`x1ude1T_M$a
'P1&#&*&!ah1xfU1T`%$'P1&#&*bh1zde1TkM$a"3'P1&#&*cX$1}de1TkM$a*3'P1&#&*&!dH,2fU1T`%'1:'P1&#&*eH32de1TmM$a/8I'P1&#&*f8:2de1TnM$a6@I'P31&#&*&!g(B2fU1T`%=GP'P1&#&*h(I2de1ToM$aEN'P1&#&*iP2#&*q82&de1TM$a*'+1&#&*r(2(de1TbM$a/'+1&#&*s*2+e51Tu$u&/'+1&#&*&!s(2.fU1T`%#-A'+1&#&*u/21de1TM$a+5A'+/1&#&*&!ux724fU1T`%2>H'+/HW1&#&*&,&-&/vxA26bu1T-$M:FW'A1&#&*xH29de1TM$aDNW'AH1&#&*&!yP2<fU1T`%KU^'A1&#&*zW2>de1TM$aS\m'+1&#&*zx^2Ae51Tu$uZdm'+W1&#&*&!zxf2DfU1T`%ak'+1&#&*|hm2Gde1TM$ais'+m1&#&*&!}Xu2JfU1T`%p| '+m  1&#&*&,&-&/~X2Lbu1T-$Mx  
h ]2lde1T_M$a Y b s' V1&#&*X d2ode1T_M$a ` j s' V ]1&#&*&!
H l2rfU1T`% g q!z' V1&#&*8 z2wde1TM$a v!!	' V s1&#&*&!(!2zfU1T`% }!!' V1&#&*(!	2|de1TM$a!!!' V1&#&*!2de1TM$a!
!!' V!	1&#&*&!!3fU1T`%!!!&' V1&#&*!3de1T_M$a!!$!5' V1&#&*x!&3de1T_M$a!"!,!5' V!1&#&*&!h!.3
fU1T`%!)!3!<' V1&#&*h!53
de1T_M$a!1!:!K' V1&#&*X!<3de1T_M$a!8!B!K' V!51&#&*&!H!D3fU1T`%!?!I!R' V1&#&*H!K3de1T_M$a!G!P!Y' V1&#&*8!R3de1T_M$a!N!W"'+1&#&*(!Y3e51T_u$u!U!_!i'!K38&#&*&!(!b3;fU38T`%!]!g!p'+38&#&* !i3=de38T_M$a!e!n!w'+38&#&*!p3@de38T_M$a!l!u!~'+38&#&*!w3Bde38T_M$a!s!|"'+38&#&*p!~3Ede38T_M$a!z""'+!i38&#&*&!`"3HfU38V9-%"""!'+!i"!"S##0#M#q$$*$@$V$l%38&#&*&,&-&/&0&2&3&5&6&8&9&;&<&> `"3M38T_-$M"	""('"38&#&*# "!3Ode38T_M$a""&"/'"38&#&*$"(3Rde38T_M$a"$"-"6'"38&#&*%"/3Tde38T_M$a"+"4"='"38&#&*%p"63Wde38T_M$a"2";"D'"38&#&*&`"=3Yde38T_M$a"9"B"S'"38&#&*'P"D3\de38T_M$a"@"I"S'""!38&#&*&!(@"L3_fU38T`%"G"Q"Z'"38&#&*)@"S3ade38T_M$a"O"X"a'"38&#&**0"Z3dde38T_M$a"V"_"h'"38&#&*+ "a3fde38T_M$a"]"f"o'"38&#&*,"h3ide38T_M$a"d"m"v'"38&#&*-"o3kde38T_M$a"k"t#'"38&#&*-p"v3nde38T_M$a"r"{#'""S38&#&*&!.`"~3qfU38T`%"y##
'"38&#&*/`#3sde38T_M$a##
#'"38&#&*0P#
3vde38TM$a###'"38&#&*1@#3xde38TM$a###!'"38&#&*20#3{de38TM$a###0'"38&#&*3#!3}de38TM$a##&#0'"#38&#&*&!4#)4fU38T`%#$#.#7'"38&#&*5#04de38TM$a#,#5#>'"38&#&*6#74de38TM$a#3#<#M'"38&#&*6p#>4de38TM$a#:#C#M'"#038&#&*&!7`#F4fU38T`%#A#K#T'"38&#&*8`#M48T`%$	$$'"38&#&*A`$4'de38TM$a$$$*'"38&#&*BP$4*de38TM$a$$!$*'"$38&#&*&!C@$$4-fU38T`%$$($1"38&*D@$*4/de38TM$a$'$/$@'"38&#&*E $142de38TM$a$-$6$@'"$*38&#&*&!F$945fU38T`%$4$>$G'"38&#&*G$@47de38TM$a$<$E$V'"38&#&*H$G4:de38TM$a$C$L$V'"$@38&#&*&!Hp$O4=fU38T`%$J$T$]'"38&#&*Ip$V4?de38TM$a$R$[$l'"38&#&*J`$]4Bde38TM$a$Y$b$l'"$V38&#&*&!KP$e4EfU38T`%$`$j$s'"38&#&*LP$l4Hde38TM$a$h$q%'"38&#&*M@$s4Kde38TM$a$o$x%'"$l38&#&*&!N0${4NfU38T`%$v%%	'"38&#&*O0%4Pde38TM$a$~%%'"38&#&*P %	4Sde38TM$a%%%'+38&#&*Q%4Ve538Tu$u%
%%'%38&#&*&!Q%4YfU38T`%%%%4'+38&#&*S%4\de38T_M$a%%$%4'+%38&#&*&!Sp%'4_fU38T`%%"%/%;'+%%;%Q%g%}&38&#&*&,&-&/&0&2&3Tp%44abu38T_-$M%*%9%B'%438&#&*V@%;4dde38T_M$a%7%@%Q'%438&#&*W0%B4fde38T_M$a%>%G%Q'%4%;38&#&*&!X %J4ifU38T`%%E%O%X'%438&#&*Y %Q4lde38T_M$a%M%V%g'%438&#&*Z%X4nde38T_M$a%T%]%g'%4%Q38&#&*&![%`4qfU38T`%%[%e%n'%438&#&*\%g4tde38T_M$a%c%l%}'%438&#&*\p%n4vde38T_M$a%j%s%}'%4%g38&#&*&!]`%v4yfU38T`%%q%{&'%438&#&*^`%}4|de38T_M$a%y&&'%438&#&*_P&4~de38T_M$a&&	&'%4%Q38&#&*&!`@&
5fU38T`%&&&'%438&#&*a@&5de38T_M$a&&&!'%438&#&*b0&5de38T_M$a&&&0'+38&#&*c &!5	e538T_u$u&&&&0'+&38&#&*&!c &)5
fU38T`%&$&.&7'+38&#&*e&05de38T_M$a&,&5&>'+38&#&*f&75de38T_M$a&3&<&E'+38&#&*fp&>5de38T_M$a&:&C&L'+38&#&*g`&E5de38T_M$a&A&J&['+38&#&*hP&L5e538T_u$u&H&Q&['+&038&#&*&!hP&T5fU38T`%&O&Y&b'+38&#&*j@&[5de38T_M$a&W&`&i'+38&#&*k0&b5!de38T_M$a&^&g&x'38&#&*l &i5$38T`%&e&o&x'5B&#&*&!A0&q5DfU5BT`%&l&v'
'5B&#&*n&x5Gde5BT_M$a&t&~'
''
&x5B&#&*&!o'5IfU5BT`%&{'''&x'%-w5B&#&*&,&-&/p'
5Lbu5BT_-$M'''%''
5B&#&*q('5Nde5BTM$a'#&*&!r'5QfU5BT`%''!',''
''?*!,-L5B&#&*&,&-&/&0&2s'%5Tbu5BT-$M''*'?''%5B&#&*tX',5Vde5BTM$a'('2'?''%',5B&#&*&!uH'45YfU5BT`%'/';'F''%','k))x5B&#&*&,&-&/&0vH'?5\bu5BTf-$M'7'D'M''?5B&#&*wx'F54de5BTdM$a'B'K'T''?5B&#&*xh'M5bde5BTM$a'I'R'k''?5B&#&*yX'T5ede5BTM$a'P'Z'k''?'F5B&#&*&!zH'\5hfU5BT`%'W'e'r'?''F'r(((4(C(Y(v5B&*&#&,&-&/&0&2&3&5&6{H'k5kbu5BT-$M''p'y''k5B&#&*}8'r5nde5BTM$a'n'w(''k5B&#&*~('y5qde5BTM$a'u'(''k'r5B&#&*&!(5ufU5BT`%'|((''k5B&#&*(5xde5BTM$a((
((Y6de5BT_M$a(U(^(g''k5B&#&*(`6de5BT_M$a(\(e(v''k5B&#&*
(g6!de5BT_M$a(c(m(v''k(Y5B&#&*&!
x(o6$fU5BT`%(j(t(}''k5B&#&*
''?5B&#&*h(}6+e55BT_u$u(y))
') (v5B&#&*&!h)6.fU5BT`%))
) ''?5B&#&*X)
61de5BT_M$a))) ''?)
5B&#&*&!H)65fU5BT`%)))'''?)
)')6)E)T5B&#&*&,&-&/&0&2H) 68bu5BT_-$M))%)6') 5B&#&*)'6;de5BT_M$a)#)-)6') )'5B&#&*&!x)/6>fU5BT`%)*)4)E') 5B&#&*x)66Ade5BT_M$a)2)<)E') )65B&#&*&!h)>6EfU5BT`%)9)C)T') 5B&#&*h)E6Hde5BT_M$a)A)K)T') )E5B&#&*&!X)M6KfU5BT`%)H)R)[') 5B&#&*X)T6Nde5BT_M$a)P)Y)b') 5B&#&*H)[6Qde5BT_M$a)W)`)i') 5B&#&*8)b6Tde5BT_M$a)^)g)x''%5B&#&*()i6Xe55BT_u$u)e)o)x') )T5B&#&*&!8)q6[fU5BT`%)l)v)''?5B&#&*)x6^de5BT_M$a)t)}*''%5B&#&*)6ae55BT_u$u){**''?)x5B&#&*&!*6efU5BT`%**
*!''?5B&#&* x*6gde5BT_M$a*
**!''?*5B&#&*&!!h*6jfU5BT`%***(''%**:++`5B&#&*&,&-&/&0"h*!6mbu5BT-$M**&*:'*!5B&#&*$*(6pde5BTM$a*$*.*:'*!*(5B&#&*&!%*06sfU5BT`%*+*7*A'*!*(*A*W5B&#&*&,&-&/&*:6vbu5BT`-$M*3*?*H'*:5B&#&*'(*A6yde5BTM$a*=*F*W'*:5B&#&*(*H6|de5BTM$a*D*N*W'*:*A5B&#&*&!)*P7fU5BT`%*K*U*^'*:5B&#&***W7de5BTM$a*S*\*e'*:5B&#&**x*^7de5BT`M$a*Z*c*t'*!5B&#&*+h*e7	e55BTu$u*a*k*t'*:*W5B&#&*&!+h*m7u+c+m+v'*!+`5B&#&*&!<+o7CfU5BT`%+j+t+}''%5B&#&*=x+v7Fde5BTM$a+r+{,''%5B&#&*>h+}7Ide5BTM$a+y,,''%+v5B&#&*&!?X,7LfU5BT`%,,,''%+v,,2,A,W,m---/5B&#&*&,&-&/&0&2&3&5&6&8@X,7Obu5BT-$M,,,#',5B&#&*BX,7Qde5BTM$a,,!,2',5B&#&*CH,#7Tde5BTM$a,,),2',,5B&#&*&!D8,+7XfU5BT`%,&,0,A',5B&#&*E8,27Zde5BTM$a,.,8,A',,25B&#&*&!F(,:7]fU5BT`%,5,?,H',5B&#&*G(,A7`de5BTM$a,=,F,W',5B&#&*H,H7cde5BTM$a,D,N,W',,A5B&#&*&!I,P7ffU5BT`%,K,U,^',5B&#&*J,W7ide5BTM$a,S,\,m',5B&#&*Jx,^7lde5BTM$a,Z,d,m',,W5B&#&*&!Kh,f7ofU5BT`%,a,k,t',5B&#&*Lh,m7rde5BTM$a,i,r-',5B&#&*MX,t7ude5BTM$a,p,z-',,m5B&#&*&!NH,|7xfU5BT`%,w--
',5B&#&*OH-7{de5BT_M$a,--',5B&#&*P8-
7~de5BTM$a---',-5B&#&*&!Q(-8fU5BT`%-5B&#&*S- 8de5BTM$a--&-/',-5B&#&*&!T-(8
fU5BT`%-#---6',5B&#&*U-/8de5BTM$a-2-;-L''%5B&#&*Vh-=8e55BTu$u-9-C-L''%-/5B&#&*&!Ux-E8fU5BT`%-@-J-S''%5B&#&*XX-L8de5BTM$a-H-Q-c''
5B&#&*YH-S8e55BT_u$u-O-Y-c''
-L8:&#&*&!YH-\8=fU8:T`%-W-a-w''
8:&#&*[@-c8?de8:T_M$a-_-h-w''
-c8:&#&*&!\0-k8BfU8:T`%-f-r-~''
-c.0@2=4
8:&#&*&,&-&/&0&2]0-w8Ebu8:T-$M-n-|.'-w8:&#&*^p-~8Gde8:TM$a-z..'-w-~8:&#&*&!`.8JfU8:T`%..:8SfU8:T`%..(.5'...5.K.a.w//8:&#&*&,&-&/&0&2&3&5d..8Vbu8:T-$M.#.3.<'..8:&#&*e`.58Yde8:TM$a.1.:.K'..8:&#&*fP.<8\de8:TM$a.8.A.K'...58:&#&*&![email protected]8`fU8:T`%.?.I.R'..8:&#&*[email protected]8cde8:TM$a.G.P.a'..8:&#&*i0.R8fde8:TM$a.N.W.a'...K8:&#&*&!j.Z8ifU8:T`%.U.:.h'..8:&#&*k.a8lde8:TM$a.].f.w'..8:&#&*l.h8ode8:TM$a.d.m/'...a8:&#&*&!m.p8sfU8:T`%.k.u/'..8:&#&*n.w8vde8:TM$a.s.|/'...w8:&#&*&!np.8yfU8:T`%.z//
0g9Xde8:T_M$a0c0l0v'0Y0`8:&#&*&!
p0o9[fU8:T`%0j0t0}'0Y8:&#&*`0}9ade8:TM$a0y11'0@8:&#&*P19ee58:Tu$u11	1'0Y0v8:&#&*&!P1
9hfU8:T`%111''-w8:&#&*@19kde8:T_M$a111''-w18:&#&*&!019ofU8:T`%11"1.'0@11.1=1L1[8:&#&*&,&-&/&0&201'9rbu8:T_-$M11,1='1'8:&#&*p1.9ude8:T_M$a1*131='1'1.8:&#&*&!`169xfU8:T`%111;1L'1'8:&#&*`1=9{de8:T_M$a191B1L'1'1=8:&#&*&!P1E9fU8:T`%1@1J1['1'8:&#&*P1L:de8:T_M$a1H1Q1['1'1L8:&#&*&!@1T:fU8:T`%1O1Y1b'1'8:&#&*@1[:de8:T_M$a1W1`1i'1'8:&#&*01b:de8:T_M$a1^1g1p'1'8:&#&* 1i:de8:T_M$a1e1n1'0@8:&#&*1p:e58:T_u$u1l1u1'1'1[8:&#&*&!1x:fU8:T`%1s1}2'0@8:&#&*1:de8:T_M$a1{22'-w8:&#&*p2:e58:T_u$u222'0@18:&#&*&!p2:fU8:T`%2	22'-w8:&#&*!`2:!de8:T_M$a222#'-w8:&#&*"P2:$de8:T_M$a22!2='-w8:&#&*#@2#:'de8:T_M$a22(2='-w28:&#&*&!$02+:+fU8:T`%2&252D'-w22D2S2b2x33%3;3Q3g3v8:&#&*&,&-&/&0&2&3&5&6&8&9&;%02=:-bu8:T_-$M2.2B2S'2=8:&#&*'P2D:0de8:T_M$a2@2I2S'2=2D8:&#&*&!(@2L:3fU8:T`%2G2Q2b'2=8:&#&*)@2S:5de8:T_M$a2O2X2b'2=2S8:&#&*&!*02[:8fU8:T`%2V2`2i'2=8:&#&*+02b:;de8:T_M$a2^2g2x'2=8:&#&*, 2i:>de8:T_M$a2e2n2x'2=2b8:&#&*&!-2q:AfU8:T`%2l2v2'2=8:&#&*.2x:Dde8:T_M$a2t2}3'2=8:&#&*/2:Gde8:T_M$a2{33'2=2x8:&#&*&!/p3:JfU8:T`%33
3'2=8:&#&*0p3:Mde8:T_M$a3
33%''2=8:&#&#&*1`3:Pde8:T_M$a333%'2=38:&#&*&!2`3:SfU8:T`%33#3,'2=8:&#&*3`3%:Vde8:T_M$a3!3*3;'2=8:&#&*4P3,:Yde8:T_M$a3(313;'2=3%8:&#&*&!5@34:\fU8:T`%3/393B'2=8:&#&*6@3;:_de8:T_M$a373@3Q'2=8:&#&*703B:bde8:T_M$a3>3G3Q'2=3;8:&#&*&!8 3J:efU8:T`%3E3O3X'2=8:&#&*9 3Q:hde8:T_M$a3M3V3g'2=8:&#&*:3X:kde8:T_M$a3T3]3g'0@3Q8:&#&*&!;3`:nfU8:T`%3[3e3v'2=8:&#&*<3g:qde8:T_M$a3c3l3v'0@3g8:&#&*&!<p3o:tfU8:T`%3j3t3}'0@8:&#&*=p3v:wde8:T_M$a3r3{4
'-w8:&#&*>`3}:ze58:T_u$u3y44
'-w3v8:&#&*&!>`4:}fU8:T`%44
4'-w8:&#&*@P4
:de8:T_M$a44'
''
8:&#&*A@4;e58:T_u$u444)
;!&*H4;#de;!T_M$a444)
4;!&*&!C4 TbU;%fU;!T`%4@4&4/
44/7;!&*&,&-&/D4)Tb;'bu;!T_-$M4#@4.4)47&*;!E4/;)de;!T_M$a4,454)4=4E4=&*;;;!Ex47;+de;!T_M$a424<4)4E&*;!Fx4=;.de;!T_M$a4:4C4)4K4Q4K&*;;;!Fx4E;0de;!T_M$a4@4J4)4Q&*;!HX4K;3de;!T_M$a4H4P4)4Y&*;!HX4Q;5de;!T_M$a4N4W4)4_4e4_&*;;;!J4Y;7de;!T_M$a4T4^4)4e&*;!K4_;9de;!T_M$a4\4d4)4m&*;!K4e;;de;!T_M$a4b4k4)4s4{4s&*;;;!LX4m;=de;!T_M$a4h4r4)4{&*;!LX4s;@de;!T_M$a4p4y4)55	5&*;;;!LX4{;Bde;!T_M$a4v54)5	&*;!O85;Ede;!T_M$a4~54)555&*;;;!O85	;Gde;!T_M$a554)5&*;!Q5;Jde;!T_M$a5
54)5&*;!Q5;Lde;!T_M$a554)5#5+5#&*;;;!RX5;Nde;!T_M$a55"4)5+&*;!RX5#;Pde;!T_M$a5 5)4)515951&*;;;!RX5+;Rde;!T_M$a5&504)59&*;!U851;Ude;!T_M$a5.574)5?5G5?&*;;;!U859;Wde;!T_M$a545>4)5G&*;!W5?;Zde;!T_M$a5<5E4)5M5U5M&*;;;!W5G;\de;!T_M$a5B5L4)5U&*;!Xx5M;^de;!T_M$a5J5S4)5[5a5[&*;;;!Xx5U;`de;!T_M$a5P5Z4)5a&*;!ZX5[;cde;!T_M$a5X5`4)5g&*;!ZX5a;ede;!T_M$a5^5f4)5o&*;!\5g;gde;!T_M$a5d5m4)5u5}5u&*;;;!\x5o;ide;!T_M$a5j5t4)5}&*;!\x5u;lde;!T_M$a5r5{4)666&*;;;!\x5};nde;!T_M$a5x64)6&*;!_X6;qde;!T_M$a66	4)666&*;;;!_X6;sde;!T_M$a664)6&*;!a86;ude;!T_M$a664)6&*;!a86;wde;!T_M$a664)6%&*;!bx6;yde;!T_M$a66#4)6+636+&*;;;!cX6%;{de;!T_M$a6 6*4)63&*;!dX6+;~de;!T_M$a6(614)696A69&*;;;!dX63<de;!T_M$a6.684)6A&*;!f869<de;!T_M$a666?4)6G6O6G&*;;;!f86A<de;!T_M$a6<6F4)6O&*;!h6G<de;!T_M$a6D6M4)6U6[6U&*;;;!h6O<
de;!TM$a6J6T4)6[&*;!ix6U<de;!TM$a6X6a4)6i6q6i&*;;;!k86c<de;!TM$a6^6h4)6q&*;!k86i<de;!TM$a6f6o4)6w6}6w&*;;;!k86q<de;!TM$a6l6v4)6}&*;!n6w<de;!TM$a6t6|4)7&*;!n6}<de;!TM$a6z774);!&*oX7<de;!TM$a7774)4/;!&*&!p87
TbU<fU;!T`%7@777!7!4)7*;;;!&*;q(7TcE<!;!Ta5%37);!s(7!<&f;!TaU%x77'7178784)7A;;;!&*;r87*TcE<);!Ta5%37$@7/7A<7A&&&);!u(71<+f;!TaU%x7-767A<&&&);!v78<.f;!TaU%x747>7H7O7H4)7X;;;!&*;u(7ATcE<0;!Ta5%37;@7F7X<&&&);!x7H<3f;!TaU%x7D7M7X<7X&&&);!y7O<5f;!TaU%x7K7U77f7f4)7o;;;!&*;x7XTcE<8;!Ta5%37R@7]7o<7o&&&);!{7<:f;!TaU%x7[7d7o<&&&);!{x7f<=f;!TaU%x7b7l7v7}7v4)8;;;!&*;{7oTcE<?;!Ta5%37i@7t8<&&&);!}x7v<Bf;!TaU%x7r7{8<8&&&);!~h7}<Df;!TaU%x7y88
(8Y<bf;!TaU%x8U8_8i8p8p4)8v;;;!&*;	88bTcE<e;!Ta5%38\@8g8v<8v&&&);!
(8i<gf;!TaU%x8e8n8v<&&&);!de;!TM$a8s8{9
=
&*H8}=
de=
T_M$a8z99	
=
&*P9=de=
T_M$a999
=
&*09	=de=
TM$a99
=
&*9=de=
T_M$a9
99
8}=
&*&!H9TbU=fU=
T`%9@99%
8}9%:=
&*&,&-&/`9Tb=bu=
T_-$M9@9#9-9=
&*p9%=de=
T_M$a9"9*9939;93&*<}<=
P9-=de=
T_M$a9(9199;&*=
P93=de=
T_M$a909899A9I9A&*<}<=
09;=de=
T_M$a969?99I&*=
09A=!de=
T_M$a9>9F99O9]9O&*<}<=
9I=#de=
T_M$a9D9M99U&*=
9O=&de=
T_M$a9L9S99]&*=
p9U=)de=
T_M$a9R9Z99c9k9c&*<}<=
P9]=+de=
T_M$a9X9a99k&*=
P9c=.de=
T_M$a9`9h99q9y9q&*<}<=
09k=0de=
T_M$a9f9o99y&*=
09q=2de=
T_M$a9n9v99:9&*<}<=
9y=4de=
T_M$a9t9}9:&*=
9=7de=
T_M$a9|:9:&*=
p:=9de=
T_M$a:::::9:%===
&*=p:TcE=;=
Ta5%3:@::%<:%&&&)=
!`:=>f=
TaU%x:::%<&&&)=
"P:=@f=
TaU%x::":,:3:,9:<===
&*=p:%TcE=C=
Ta5%3:@:*:<<&&&)=
$P:,=Ef=
TaU%x:(:1:<<:<&&&)=
%@:3=Hf=
TaU%x:/:9:C:J:J9:S===
&*=p:<TcE=J=
Ta5%3:6@:A:S<:S&&&)=
'@:C=Mf=
TaU%x:?:H:S<&&&)=
(0:J=Of=
TaU%x:F:P:Z:a:Z9:j===
&*=p:STcE=R=
Ta5%3:M@:X:j<&&&)=
*0:Z=Tf=
TaU%x:V:_:j<:j&&&)=
+ :a=Wf=
TaU%x:]:g:q:x:x9:~===
&*=p:jTcE=Y=
Ta5%3:d@:o:~<&&&)=
- :q=\f=
TaU%x:m:v:~<:~&&&)=
.:x=^f=
TaU%x:t:|99=
&*/:~=`de=
T_M$a:{;;
=~&*H;>de=~T_M$a;;	

;=~&*&!0H;>fU=~T`%;;;
=~&*H;>de=~T_M$a;;;
=~&*2;>de=~T_M$a;;;#
=~&*2x;>	de=~T_M$a;;";)
=~&*3X;#>de=~T_M$a; ;(;/
=~&*48;)>.;5
=~&*5;/>de=~T_M$a;,;4

=~&*5x;5>de=~T_M$a;2;:;N
>/&*H;<>1de>/T_M$a;9;A;N
;<>/&*&!7@;CTbU>3fU>/T`%;?@;J;T
;<;T<=?=N>/&*&,&-&/&0&280;NTb>5bu>/T_-$M;F@;R;\;N>/&*9`;T>7de>/T_M$a;Q;Y;N;b;j;b&*>">$>/:@;\>9de>/T_M$a;W;`;j;N>/&*;@;b><de>/T_M$a;_;g;N;p;x;p&*>">$>/;@;j>>de>/T_M$a;e;n;x;N>/&*= ;p>Ade>/T_M$a;m;u;N;~<;~&*>">$>/= ;x>Cde>/T_M$a;s;|<;N>/&*?;~>Fde>/T_M$a;{<;N<
<<
&*>">$>/?<>Hde>/T_M$a<<
<;N>/&*@`<
>Kde>/T_M$a<	<<;N>/&*@`<>Mde>/T_M$a<<<"<)<);N<2>%>'>/&*>*9`<TcE>P>/Ta5%3<@< <2<<2&&&)>/C0<">Rf>/TaU%x<<'<2<&&&)>/D <)>Uf>/TaU%x<%</<9<@<@;N<I>%>'>/&*>*9`<2TcE>W>/Ta5%3<,@<7<I<<I&&&)>/F <9>Zf>/TaU%x<5<><I<&&&)>/G<@>\f>/TaU%x<<<F<P<W<W;N<`>%>'>/&*>*9`<ITcE>_>/Ta5%3<C@<N<`<<`&&&)>/I<P>af>/TaU%x<L<U<`<&&&)>/J<W>df>/TaU%x<S<]<g<n<g;N<w>%>'>/&*>*9`<`TcE>f>/Ta5%3<Z@<e<w<&&&)>/L<g>if>/TaU%x<c<l<w<<w&&&)>/Lp<n>kf>/TaU%x<j<t<~=<~;N=>%>'>/&*>*9`<wTcE>n>/Ta5%3<q@<|=<&&&)>/Np<~>pf>/TaU%x<z==<=&&&)>/O`=>sf>/TaU%x=====;N=%>%>'>/&*>*9`=TcE>u>/Ta5%3=@==%<=%&&&)>/Q`=>xf>/TaU%x===%<&&&)>/RP=>zf>/TaU%x=="=,=3=3;N=9>%>'>/&*>*9`=%TcE>}>/Ta5%3=@=*=9<=9&&&)>/TP=,>f>/TaU%x=(=1=9<&&&)>/U@=3?f>/TaU%x=/=7;N;N>/&*V0=9?de>/T_M$a=6===E;N>/&*9`=??de>/T_M$a=<=C=N;N>/&*Wp=E?de>/T_M$a=B=K=U=\=\;N=e>%>'>/&*>*9`=NTcE?
>/Ta5%3=H@=S=e<=e&&&)>/Y`=U?f>/TaU%x=X=b=l=s=l;N=|>%>'>/&*>*9`=eTcE?>/Ta5%3=@=j=|<&&&)>/\P=l?f>/TaU%x=h=q=|<=|&&&)>/]@=s?f>/TaU%x=o=y>>
>;N>>%>'>/&*>*9`=|TcE?>/Ta5%3=v@>><&&&)>/_@>?f>/TaU%x=>><>&&&)>/`0>
?f>/TaU%x>>>>!>!;N>*>%>'>/&*>*9`>TcE?!>/Ta5%3>)>/c >!?&f>/TaU%x>>'>1>8>1;N>A>%>'>/&*>*9`>*TcE?(>/Ta5%3>$@>/>A<&&&)>/e >1?+f>/TaU%x>->6>A<>A&&&)>/f>8?-f>/TaU%x>4>>>H>O>H;N>X>%>'>/&*>*9`>AWvE?0>/Ta5%3>;@>F>X<>X&&&)>/h>H?6f>/TaU%x>D>M>X<>X&&&)>/i>O?9f>/TaU%x>K>U>>f>f;N>o>%>'>/&*>*9`>XTcE?;>/Ta5%3>R@>]>o<>o&&&)>/k>?>f>/TaU%x>[>d>o<&&&)>/kp>f?@f>/TaU%x>b>l>v>}>};N?>%>'>/&*>*9`>oTcE?C>/Ta5%3>i@>t?<&&&)>/mp>v?Ef>/TaU%x>r>{?<?&&&)>/n`>}?Hf>/TaU%x>y?;N;N>/&*oP??Jde>/TM$a???i?h&*}?	?jde?hTM$a?????	?h&*&!q?TbU?lfU?hT`%?
@??i?	??7?h&*&,&-&/r?Tb?nbu?hT_-$M?@??%??h&*s??qde?hT_M$a??$?+??h&*sx?%?tde?hT_M$a?"?*?1??h&*tX?+?wde?hT_M$a?(?0???h&*u8?1?zde?hT_M$a?.?6?=??h&*s?7?}de?hT_M$a?4?<?C??h&*vx?=@de?hT_M$a?:?B?I??h&*wX?C@de?hT_M$a?@?H?O??h&*x8?I@de?hT_M$a?F?N???h&*y?O@	de?hT_M$a?L}( H@&AH@&H@H@&, CE B?e B?g CE B?f,A	6 ,CH@@?i+A "?d,~,@@?h@@?g@@?h6@?i+@|,Ad"d,A CE @?f "?c,AfO@?h ?d0@B ?dY
?caJ+@O@?hO@?i N?j ?e N?g N?d ?d3N?j@@?iO@?h N?d P?g  ?d @1,~, ~Z  
?f
""6@B=hA7@,~@B,~@@?[@@?\CI,A6@?`+CD7@?a+A""	b&+CC B?] B?b " B?a CJ	b'+CC@3BCJ $3BCK $3BCK $ D?i D?R
CL+CC?RO@?S+A-6@?`+A?X+CD,>;"%/C,^+CD6@?`+A!?X+CD,>a"C%,^+CD6@?`+A%B?[@@?\ ?\1B+A*0B1B7+CD"pPCNCOXCPxCP@CD@CD@CD@CD@CD CD@CDCDAEAE CM . ?]@	b'+ +CD6@?`+AK
"+CD+CD6@?`+AN
&+CD+CD7@?_+AQ@@?_ ?^+CD6@?`+AU7@?a+AV
7?^[?^+CDOB?^+CD+AV1@\@+AU6@?A+CC6@?^O@?B+CD6@?`+Ab7@?a+Ae,C.O@	d&+CCr"Q.X.	n'+CC\+CD~"$4CCZ+CD[?`+CD7@?`+Ah*4CC+CD7@?S+CCDB?Z,C?,C8D^?0"=$?T,C)Q?Z?ZD."*$Q"BB?T,B(@@?Z@@?[@7b?V+B	!"cB?T+CQ[?U6@?\+B,AOW1\B4 B?W!"bB?T+CD7B?U+CC,B4 B?U+CDh"ibQ"A`$CU1$+CV+CD,C?,C.,B4 4\CD,BB+B: ",BZ?Y #,B+CD &"	 ?X()""CW+CD "bB?T+CD0<+BH,B?+CX "/,B "p ,B+CD +B0\
5DCC+CDxC(BdBq8C,B{@@?Z 
?] 
?U,C+Bh,B+BeZ?Y5BBk "C\,B+Bk,B< 
?] 
?^,C+Bn+Ar6F?W,C%$C]!"5DB	+Ar@@?ZZ?Y4BBs,B<+Bt "C\,B,>,B{ 
?] 
?^,C+C] ?U $D ?],B8,^+Ar 
?^ 
?U,C+C 
?U"1B+C,C 
?^,C+C+B} J?]+CD(C_.(hC_1h,~/* (+C,>,>``2J:,^,^,~ ?U3B?^+C",B ?UZ?Y5BC ".6 ?Z,BO@?Z,BB+Ar1<+C "C_,B+Ar,B?4BAr0B+Bq "C`,B+Ar,B{@@?Z 
?U 
?^,C+C",B 
?U 
?],C+C"/" $=dC Ca4DC2D+C +Bq"C]5BCa ",B+Ar[1B "A`0BA`+B ,B+CD,>,>."@@Q`:*$,^,^+CD*x,>C0Q.-n81C0:+C7*x,>,>,>,>C5Q.~-n81C5:~,^,^,^,^,~*x,>,>,>,>C<Q&~-f1C<:~,^,^,^,^,~*x,>CAQ<-|p1CA:,^,~gO,~H@&H@TERMINAL UUO FAILED "CF+%
UM*/*?amQ
mQ* mQ*`iSHCNCOJCP?T5\A~!"+B	 ",B+Ar>?T2?T< $dCU9CDCDBFBHBI


0?T
<?T6F?W,C%+Bw<   HBX!"+B	 p@
`pBpBpBpBpGN pIr pL pL" pL" pL# pL# pL$
 pO pO pP pR8 pR9 pR: pR; pR< pR= pR? pR@ pRB pRC p
RE pRG pRH pRJ pRK pS! pSX pSY pSY pSZT;@T=pTAp
TD8TI`TM0!TPH!TR(!	TW8!%Th(!)Tj!-Tmp!1To!5Tp!9Tr`!=TtH!ATvp!ETxp!ITzx!MT{!QT}!UUP!YU!]U !aU	`!eU0!iU!mU!qU!uUp!yU!}Ux!U@!U!!	U#H!
h"-V`"1VH"5V("9V`"=V"AVx"EVX"IV!X"MV$@"QV'"UV*@"YV-`"]V0h"aV3h"eV6h"iV9"mV<p"qV?X@VAP@VBH@
VE(VJhVL0VN(VQ@(VSH(	VU`()Vj@(-Vm((1Vo((5Vr(9Vv(=Vx(AVzp(EV}H(IWP(MW(QWHW(W`pE pW !=uP pYQ pYR pYR p	\ p\& p\5 p\7 p\F p\H p\I p\J p\a p\c p^ p^ p` p`8 p`b pa paN&(U G\E*@pG^E*/@pHf(,YG`z0GM)f
`@pG[Z$/ pG]SPEAR.MSGDSK:SPEAR.MSGH&,H@?GdH%@H&:1 by B Smith - Added stub Overview and Menu messages for INSTS,
		       INSEF, INSRET, INSCOM, and INSAPP files.
 05/19/81 by B Smith - Corrected TX01/02 Massbus Theory descriptions.
 06/09/81 by B Smith - Corrected TX01/02 Overview.
 06/11/81 by B Smith - Added dialog questions and answers.
 07/07/81 by B Smith - Corrected Disk report formats (xxx Total Retries)
 07/08/81 by B Smith - Added text for Tape Theories [2.1.1.4] & [2.2.1.4]
 08/07/81 by L Emlich- Removed answers to questions within questions
 08/18/81 by B Smith - Corrected spelling errors and typos.
@Gd@ll 31 retries are unsuccessful, then the read error is defined as
non-recoverable (Hard) and an entry is made in the structures BAT block.
@@

!!INSREC.END - Text that goes with Disk Error Recovery Algorithms
@@END_FILE
Now type: SAVE SPRINS<cr>
@@

END----END----END----END----END----END----END----END----END

!!Edit History

 04/10/81 by B Smith - Corrected some spelling errors.
 04/24/81 by B Smith - Added TM02/03 tape subsystem messages.
 04/30/81 by B Smith - Added TX01/02 tape subsystem messages.
 05/03/81 by B Smith - Added some missing report format examples.
 05/07/81 by B Smith - Added Course menu.
o05/08/8@@EsSPRINS<cr>coveryAlgorithmsP0I
query_res_error_msg	HwG-	XHx	pHz
`I@p#H{This is the Theory Query response error message. The theory number that	 I
@p$Iyoutenteredddoesrnotsexist.ePleasetcheckmthesnumberandtryagain.Also,	0I@pI RETURN key to repeat the Query prompt.zI9@p	I6A{@}pzHo@pI 	Pranquestreserrormsg	
`I/@p#I'This is the Random Question response error message. The number that you	`@pI0entered is not within the range of 1 to 60.	/8KG-ask:text_res_error_msg	8I:G-	I<	(I=
`IF@p#I>This is the text response error message. Instruct displays one page of	XIM@pIGtext at a time. After you have read the text you can:	`IN@p	PIU@pIO 1. Press the RETURN key to go on to the next page.	hIW@p	XI`@p#IX 2. Press the BACKSPACE key or type /R to go back to the previous page.	pIa@p	Ii@p Ib 3. Type MENU to go back to the menu and select another subject.	Ik@p	Is@p"Il 4. Type /B to return to the Spear prompt. If you are using a student	0I|@p!It    ID, and if you specify that ID at the Instruct prompt, you will	8J@pI}    return to the page that you were at when you typed /B.	@J@p	 8J
@pJ 5. Type anything else and you will get this message.	 P@pzJ@p	J	/8|#$menu_res_error_msg	!XJG-	" J	"8J
`J@p"JThissisrthe menuresponseerrormessage.Instruct uses a hierarchy of	"hJ'@p"J menus. The menus allow you to use Instruct as a quick reference tool.	#pJ+@p	J(At a menu you can:	$xJ,@p	%0J5@p$J- 1. Type the number on the menu that corresponds to the subject that you	%HJ9@pJ6    are interested in.	&XJ;@p	'JC@pJ< 2. Type MENU to go back to the previous (higher level) menu.	'0JD@p	(0JM@p"JE 3. Type /B to return to the Spear prompt. If you are using a student	(HJU@p!JN    ID, and if you specify that ID at the Instruct prompt, you will	)PJ]@pJV    return to the page that you were at when you typed /B.	*XJ^@p	+PJg@p#J 4. Press the BACKSPACE key or type /R. You will get a message stating	+hJo@p Jh    that you are about to back into the Introduction to the menu.	,pJp@p	-pJw@pJq 5. Type anything else and you will get this message.	.@pzLS@pLQ;`zI5@pJ}	t(J
`K
@p"KThiseisithetforwardRresponseferrordmessage.uYoulcanesequence	through	08K@p"Kn Introduction, followed by a menu, followed by the first	2HK&@p#Ksubject, followed by the second subject, etc. You will be notified each	3PK/@p#K'time you transition from one subject to another. At that point you can:	4`K0@p	5pK8@p K1 1. Press the RETURN key to continue sequencing through Instruct.	6K:@p	7KC@p#K; 2. Press the BACKSPACE key or type /R to repeat the last page of text.	7 KD@p	80KL@p KE 3. Type MENU to go back to the menu and select another subject.	8HKN@p	9HKV@p"KO 4. Type /B to return to the Spear prompt. If you are using a student	9`K@p!KW    ID, and if you specify that ID at the Instruct prompt, you will	:hKf@pK`    return to the point that you were at when you typed /B.	;pKh@p	<hKo@pKi 5. Type anything else and you will get this message.	=@pzKu@pKr9]P^"revtransreserrormsg	>KwG-	>XKx	>pKz
`L@p"K{This is the reverse-transition prompt/response error message.You are	? L@p"Lsequencing through Instruct in a reverse direction. You were notified	@(L@p!L
that you are about to transition (in a reverse direction) from one	A0L@pLsubject to another. You can:	B8L@p	CL"@p"L 1. Press the RETURN key to begin sequencing in a forward direction.	CL#@p	D L,@p"L$ 2. Press the BACKSPACE key to continue going in a reverse direction.	D8L-@p	E@L4@pL. 3. Type BEGIN to go to the beginning of the subject.	EXL6@p	FHL>@p L7 4. Type MENU to go back to the menu and select another subject.	F`L?@p	G`LE@pL@ 5. Type /B to return to the Spear prompt.	GxLG@p	HXLN@pLH 6. Type anything else and you will get this message.	Hp@pfarewellerM.X1.0.ans_res_error_msg	/LUG-	J8LV	JPLX
`La@p#LYThis is a response error message. Your response does not match the list	KLi@p#Lbof acceptable responses. For further information press the RETURN key,	L@p
Ljthen type: ? or HELP.1.M.1.1.zLq@pLO2K O"	MhLrG-	NLt	N(Lu
`Lz@pstruct bids you farewell.	NX@pL{Type /Break to return to Spear.	lHNgG-zM@pM;9Mb$courseadmin	PMG-	PHM	P`M	
`M@pM
        Spear Course Administrator and Student Guide	QM@p	RM@p#MThroughout this course there are a number of questions and answers. If	RM"@p"Myou are interested in formally completing this course, you may do so	S M+@p"M#by filling out a copy of the following answer sheet and returning it	T(M,@pHp	U0M.@p	UHM2@pM/	Digital Equipment Corporation	U`M7@pM3	Course Administrator MR1-2 / E17	V(M;@p	M8	200 Forest Street	VxM?@pM<	Marlboro, Mass   01752	W0M@@p	WpMB@p	XMK@p$MCYour answer sheet will be graded and returned. Please include your name,	X MT@p$MLmailing address, and phone number with your answer sheet. To obtain your	Y0M]@p$MUcopy of the answer sheet, direct the system to TYPE or PRINT: ANSWER.TXT	Z@M^@p	[P@p
M_						Thank you;  c.t.s.zMf@pMd	P{\,course_admin_a	\(MhG-	\hMi	]Mk
`Mr@pMl TOPS-10 T  F   TOPS-20  F	 2Analyze	Retrieve	Summarize	]0My@pMsEvent File    3EventFFile T  Dialog	 Dialog		NDialog		^ N@pMz----------. T  ----------	 4.--------	--------	---------	5N@pN.1. TF	F	1.TT FF 5. T 1.T	F	N1.@TF	1. T. F	`NT  F      6. T  F	 6. T  F	 6. T  F	dN.@pN( 7. T  F	7. T  F      7. T  F	 7. T  F	 7. T  F	dxN3@pN/ 8. T  F	8. T  F      8. T  F	 8. T  F			e`N:@pN4 9. T  F	9. T  F      9. T  F	 9. T  F	Summarize	f8NA@pN;10. T  F       10. T  F     10. T  F    10. T  F	 Report	g NE@pNB							---------	hNI@pNFCompute							1. T  F		hPNL@p
NJDialog							2. T  F	iNP@p
NM-------							3. T  F	iHNT@p
NQ1. T  F							4. T  F	jNX@p
NU2. T  F							5. T  F	jHN\@p
NY3. T  F							6. T  F	kN`@p
N]4. T  F							7. T  F	kH@p
Na5. T  F							8. T  FzL@pLP29HU&	OpNh	lpNj
`No@pNkg The Spear LibrSpearCourse@Menu	m	Np@p	mpNr@p	nNw@pNs 0. Course Administrator/Student Guide	n Ny@p	nxN|@p	Nz 1. Troubleshooting	oN~@p	oHO@pN 2. System Event Files	o`O@p	p O@p
 Appendices	q0O@p	q`O@pO A. FEEDBACK	qxO@pO B. Theory Query	r(O@pO C. Disk Recovery Algorithms	r`O@p
O D. RandomTQuestions	s(@pzO&@pO$	MhJ{&feedback	t(O'G-	t`O)	txO*
`O2@p O+Feedback is an important part of any system design. Technically,	u(O:@p O3feedback is defined as: a representive sample of the output used	v(O?@pO;to control or correct the process.	w(OA@p	wxOI@p!OBThe process, in this case, is The Spear Library. The output is; the	xOR@p"OJability of the Spear Library to help you evaluate system performance	yOZ@p!OSand solve service related system problems. If you have any ideas or	z Oc@p"O[suggestions for improving the usefulness of The Spear Library, please	{(Oe@pOdcontact:	|0Og@p	|XOh@p	|pOm@pOi	Digital Equipment Corporation	}Oq@pOn	The SPEAR Team  MR1-1 / S35	}POu@p	Or	200 Forest Street	~Oy@pOv	Marlboro, Mass.  01752	~POz@p	O|@p	(O@pO}			Thank you;	@@pP			The Spear Teamspear_mane1.2.zP@pP	dJrandom_question
@P	G-
P
P

`P@p#Puestion feature allows you to enter a random number in the
HP@p#Prange of 1 to 60. Instruct will respond by presenting you with a random
PP#@pPquestion based on the course content.
`P%@p
8P.@p#P&This feature can be used by anyone who has a few minutes, and who would
PP6@p"P/like to pickup a few tidbits about the use of The Spear Library. The
`P?@p#P7feature can also be used by The Course Administrator as a tool to spot
hPC@pP@check student progress.
pPD@p
0PM@p"PEAfter being informed that you have correctly answered a question, you
HPT@pPNmay select another random question by typing "RANDOM".  
	PPV@p

H@pPWType <return> if you wish to enter the random question mode.  zP`@pP	>n$
`PbG-
Pc
 Pe
`Pi@p
Pf		Using The Spear Manual
PPj@p
Ps@p"PkYou can use The Spear Manual as a learning aid, a user's guide, or a
(Pv@pPtreference tool. 
0Px@p
hQ@p!PyAs a Learning Aid: Chapters 1, 2, and 3 provide an overview of the
Q	@p!QSpear Library. They also provide background information required to
Q@pQ
understand and use the Spear library.
Q@p
hQ@p#QAs a User's Guide: Chapters 4 and 5 provide step-by-step procedures for
Q!@p"Qusing the Spear functions; Analyze, Retrieve, Summarize, and Compute.
Q*@p"Q"The chapters explain, in detail, the command syntax and the response
Q0@pQ+parameters associated with each function.
 Q1@p
Q:@p!Q2As a Reference Tool: Chapter 6 and the appendixes provide reference
QB@p#Q;material such as system event file formats, event record descriptions,
 QK@p#QCand examples of the report formats. This chapter and the appendixes are
(@p$QLfor reference only. They are not meant to be read from beginning to end.
hQqG-zQZ@pQX=dnR.T.cou_ovr_a
`Q[G-
 Q]
8Q^
`Qg@p#Q_STOP - You are moving in a reverse direction through the menu. You are
h@pQhabout to back into the Course Administrator/Student Guide.zQT@pLPR+
HQr
Qt
`Q|@p#QuAbout two hours ago the CTY sent it's last message. Now you are gazing
@R@pQ}at a million dollars worth of useless wires and ceramic chips.
HR@p
 HR
@p
R  "coffee would be nice"
 `R@p
!@R
!8R@p$RThe operator patiently recounts the experience.  Still half asleep, your
!PR@p#Rmind wanders from one minor detail to another. You notice the clock on
"`R'@p$Rthe wall. The little hand points to three ... the big hand is lost some-
#h@pR(where in the fog ......zR/@pR-
hS1.0.A.
%8R0G-
%pR2
&R3
`R<@p#R4First, pull yourself together. Now try to understand the operators, the
&8RE@p"R=programmers, and all the other midnight workers who found themselves
'HRN@p#RFidled by your system. The sinking feeling... the irritation... the fear
(PRV@p"ROand anxiety... they won't help. Relax. Listen. Try to pay attention.
)`RX@p
*hR`@pRY  "I was an hour into the nightly batch job when the thing just
+Rf@pRa   quit. I tried a restart, but it just hung."
,Rh@p
,hRp@p!RiFinally, concentration sets in. You feel the gears begin to mesh. 
-Rr@p
.Ry@pRs   "So I turned off and on a couple of times and then...."
. R{@p
/@pR|Oh well, you've been at ground zero before.zS@pS
%8SQ1.0.B.
0SG-
0HS
0`S	
`S@p!S
Somehow you weren't really paying attention, but the monologue was
1S@p"Seffective. It got you out of sleep mode and through the panic stage.
2S"@p"SNow, you realize that it's time to take over. You consciously ignore
3 S+@p#S#the chaff. Your mind begins to recall the troubleshooting memory pegs.
4(S1@pS,You get the feeling that you're ready to function.
50S3@p
6S;@p"S4So far, you have resisted many impulses. You didn't run for the scope
60SD@p"S<or spend half an hour checking every circuit breaker in the building.
78SM@p$SEYou managed to keep your hands off the diagnostic pack, no one was hurt,
8@@pSNand you didn't quit your job.zSU@pSS
0T;1.0.C.
:SVG-
:PSX
:hSY
`Sb@p#SZInstead, you listened and you waited. Now the feeling that you've been
;Sj@p"Scwaiting for has arrived. The clock is forgotten. The people fade into
< Sr@pSkthe background. The symptoms have become very interesting.
=(Ss@p
> S{@p St "Doesn't sound too bad," you say calmly, "but I think I'd better
>8T@p S|  get a cup of coffee to clear my head a bit. This kind of thing
?8T@pT  ever happen before ?"
@8T	@p
@xT
@p
AT@p"TYou're in charge now. Your confidence seems contagious. The operators
A(T@p"Tand programmers begin to relax. They stop talking. Somehow they sense
B0T$@p!Tthat you know what you're doing. No longer hindrances, they become
C8T,@p#T%tools. You can talk with them now. And, from your experience, you know
D@T5@p#T-that if your current state of mind holds up, you will solve the problem
EH@pT6and, at the same time enjoy the challenge.zT?@pT=
:UQ1.0.D.
G8T@G-
GpTB
HTC
`TL@p#TDThere's no other feeling quite like it. You're driving home. It's still
H8TU@p#TMdark. There's no reason why you can't sleep in. The problem hadn't been
IHT^@p#TVall that simple. But, as you mull it over in your mind you realize that
JXTg@p#T_"scope-chasing" and "random checking" would have kept you there longer.
KhTp@p"ThAt the same time you recall a couple of places where you went wrong.
LxTv@pTq"Make a mental note, so that won't happen again."
NTx@p
NhTy@p
OU@p TzAfter all, you're a professional troubleshooter; and professional
O@pUtroubleshooters enjoy doing a professional job.zU@pU
	lHV_R.T.1.0.
QUG-
Q8U
QPU
`U@p#USTOP - You are moving in a reverse direction through the menu. You are
RU@pUabout to back into the Troubleshooting Introduction.
SU!@p
Sx@p
U"Your response please:zU'@pLmhy(
TPU)G-
TxU*
UU,
`U-@p
U@U2@pU.              Troubleshooting
UXU3@p
V U6@pU4Topic menu:
V8U8@p
VhU;@pU90. Introduction
WU<@p
W0U@@p
U=1. Attitude vs. Approach
WHUB@p
XUF@pUC2. The Formal Approach
X UG@p
X`UL@pThe Systematic Approach
XxUM@p
Y@@p
UN4. The Variable ApproachzUT@pLm
G8V$
ZUUG-
Z@UW
ZXUX
`U]@p    Attitude vs. Approach
[U^@p
[PU`@p
[hUh@p"UaFirst and foremost; your success as a problem solver depends more on
\Up@p Uiyour attitude than it does on your approach. Quite simply, if you
]Uy@p"Uqbelieve that you can (solve a particular problem), then you probably
^V@pUzwill; if you believe that you can't, then you probably won't.
_V@p
`V@p
`(V
@p#VRemember; In New England, Can't rhymes with won't. The only thing that
`@V@p#V going for it is your attitude. Therefore, with the right
aHV@p#Vattitude, you can solve almost any problem. It's just a matter of time.
bP@pVNever give up and you'll never lose.  !1.3.zV(@pV&
ZV~1.1.A.
dHV)G-
eV+
eV,
`V2@pV-                            Approach
eHV3@p
f V<@p"V4The way you approach the solution to a problem will also, to a large
f8VD@p"V=extent, determine your success as a problem solver. The more logical
g@VM@p#VEand systematic your approach, the more successful you're likely to be.
hHVN@p
iPVW@p#VONext on the menu are a couple of systematic problem solving approaches
ih@p#VXthat I think you will find to be both interesting and quite effective.zVc@pVa
QlHR.T.1.1.A.
kxVdG-
l0Vf
lHVg
`Vp@p#VhSTOP - You are moving in a reverse direction through the menu. You are
lxVx@p!Vqabout to back into the Attitude vs. Approach section of the course.
nVz@p
o@p
V{Your response please:zW@pP
dHWY&
o`WG-
pW
p W
`W
@pW                    The Formal Approach
pPW
@p
q(W
q@W@pWThe Formal Approach consists of seven steps:
qXW@p
r8W@p
rPW@p!W 1. RESEARCH and DEFINE the problem (what is, or is not, happening)
rhW @p
spW)@p#W! 2. VENTURE a testable educated guess (as to the cause of the problem)
tW*@p
uW2@pW+ 3. SETUP a practical experiment (to test the educated guess)
u(W4@p
v(W;@pW5 4. PREDICT the result (before you conduct the experiment)
v@W=@p
w8WD@pW> 5. CONDUCT the experiment (keep an accurate set of notes)
wPWF@p
xHWN@p!WG 6. EVALUATE the result (compare the actual and predicted results)
x`WP@p
yh@p#WQ 7. REFINE the definition and REPEAT the process (begining with step 2)zW\@pW[
o`gb(1.2.A.
{W^G-
{HW_
{`Wa
`Wi@p#WbStep 1 - RESEARCH and DEFINE the problem - If you're not familiar with
|Wr@p!Wjthe system, begin your research at the Branch office. Look over the
}Wz@p"Wsrecords for the last couple of weeks. Try and get an idea of the size
~ X@p"W{and the application of the system. Also, find out when the system was
(X@pXlast serviced, by whom, and why.0X	@pX@p#X
When you first arrive on site take five or ten minutes to talk with theX@p#Xcustomer, the operator, or anyone else that may be able to explain the(X$@p#Xproblem. Here's a partial list of the type of questions that you should0X%@pI6@X'@pXX+@pX(How serious is the problem ?pX-@p8X2@pX.How long has it been going on ?PX3@p X:@pX4Has the system ever had a problem like this before ?8X<@p(XB@pX=How has the system been performing lately ?@XC@p @p XDHave there been any recent hardware or software changes lately ?zXO@pXM
|(h1.2.B.	8XPG-	pXR
XS
`X\@p!XTYou can define the problem at the same time that you are doing the
8Xa@pX]research. Ask yourself three questions:@Xc@p
Xd@p
0Xj@pXe 1. What is happening that shouldn't ? 
HXk@p2.XWhatisnot happeningrthateshouldu?ding coons ?8X{@pY@p#X|The first two questions will help you identify the main error symptom.0Y
@p#YTheCthirdyquestionhwillhelpryoutidentifyethe'contextiorlcircumstances8Y@p"Ye to solve a problem out of context.zY@pY
`Y+@p#Y#Onceagain,the-questionstoaskyourselfwhendefining a problem are:(Y,@p0Y.@pHY4@pY/       What is happening that shouldn't ?`Y:@pY5                                          @YA@pY;       What is not happening that should ?            YG@pYB                                          YM@pYH       What are the surrounding conditions ?pYN@pPYP@phYY@p#YQThe definition should be as complete as possible. It should also state,Ya@p!YZin clear and concise terms, the major symptom and the conditions orYj@p"Ybcircumstances that surround that symptom. One more thing, and this isYs@p#Ykimportant, you should write the definition down, at least in note form. Yt@p0Yw@pYuFor example:HYy@px@p YzDef -  4 days/2020/256K/cache/TOPS-20(4.1)/UBANXM/freq:12-14 hrs.zZ@pZ
`Z
@pZ
Or more formally:!Z@p!HZ@p"Z   During the last four days, the system, a 2020 with 256K and cache,!`Z@p"Z   running TOPS-20 (4.1) has crashed about every 12 or 14 hours with"hZ#@p
Za1UBANXMBug'Halt.#pZ$@p$0Z&@p$HZ/@p#Z'Note that the definition states only one main error symptom, UBANXM Bug$`Z8@p$Z0Halt. The rest of the information describes the conditions that surround%p@pZ9the error symptom (i.e., the context of the problem).zZB@pZA
`ZO@p"ZHSometimes, however, a system will exhibit multiple error symptoms. In(pZX@p#ZPsuch a case, each error symptom (including the surrounding conditions))xZ`@p#ZYshould be stated separately. This is important because, when you first+Zi@p#Zastart working, you have no way of knowing, for sure, whether or not the,Zo@pZjsystem actually has multiple problems.-Zp@p-pZr@p.Zz@p"ZsTherefore, assume the worst case. If a system exhibits multiple error. [@p#Z{symptoms treat each symptom separately. That way you will eliminate the/([
@p#[possibilityhoflmultiplererrorspcompoundingythecproblemssolvingprocess.08[@p#[obvious symptom first, which is sound troubleshooting practice.z["@p[ 
`[,@p['Review- ThekeypointsXdiscussedsofarare:4h[.@p5H[5@p[/ 1. Talk to anyone who may know something about the problem.5`[7@p6X[=@p[8 2. DEFINE the problem. Find out exactly:6p[>@p7P[D@p[?      What is happening that shouldn't ?7h[J@p[E      What is not happening that should ?8@[P@p[K      What are the surrounding conditions ?9 [Q@p:[Z@p#[R 3. Remember to get all the conditions and circumstances. It's next to:[`@p[[    impossible to solve a problem out of context.; [b@p<[k@p$[c 4. Write down the definition, at least in note form. Be clear, concise,< [p@p[l    and as complete as possible.=0[q@p>[y@p[r 4. Treat each error symptom as if it were a separate problem. >[{@p?@p[| 5. Attempt to solve the most obvious problem first.z\@p\

`\@p#\Step 2 - VENTURE a testable educated guess (TEG) as to the cause of theA \@p#\problem. The truth of the matter is, when you first start out to solveB0\$@p#\a problem, you can't know (for sure) what the cause is. Therefore, youC8\,@p!\%really don't have much of a choice; you have to begin with a guess.D@\.@pEH\7@p#\/Fortunately, if the guess is testable, it does not have to be accurate.E`\@@p#\8In fact, your first few guesses probably won't be accurate. But, if youFp\I@p#\Ause this approach and your guesses are testable, then they will quicklyH\P@p\Jbecome accurate.  In other words, they will either:I\Q@pJ\X@p\R  a) lead you directly to the cause of the problem, orJ\Z@pK\c@p$\[  b) they will lead you to the realization that you could use some help.K \d@pL0@p
\eEither2way,youMwin.z\k@p\jMP\p
`\y@p#\qHere's a couple of testable educated guesses (tegs)to go along with theN\@p\zproblem that was identified and defined earlier:O]@pOx]@pP]
@p ]Def -  4 days/2020/256K/cache/TOPS-20(4.1)/UBANXM/freq:12-14 hrs.P(]
@pQ(]@p]Teg #1. A low voltage condition exists at one of the UBAs.QX]@p]         RP@p]Teg #2. One of the Unibus cables is improperly seated.z]"@p] M]<
1.2.I.Sh]#G-T ]%T8]&
`](@pTh]-@p])                        REMEMBERU].@pUP]5@p]/          Tegs don't have to be earth shattering.Uh]6@pVP@p]7             But they do have to be testable.z]@@p]>Sh^
1.2.J.WH]AG-X]CX]D
`]M@p"]EStep 3 - SETUP an experiment that will prove, or disprove, your teg.XH]U@p"]NThe experiment should be carefully thought out. You should make everyYP]^@p"]Veffort to ensure that it is a true, and accurate test of your guess.ZX]f@p!]_Take your time. Make sure that your experiment is not inadvertently[`]l@p]gtesting something other than your teg.\h]m@p]@]v@p"]nHere's why. If your experiment turns out to test something other than]X]@p#]wyour teg, and you don't realize it, then you are liable to misinterpret^`^@p"^the result. Consequently, you may find yourself tripping down the Old_p@p^Garden Path.z^@p^
WH^M1.2.K.a(^G-a`^ax^
`^@p$^The Old Garden path, by the way, is a New England expression that refersb(^$@p$^to a troubleshooting tangent; a lessons in pure frustration. The path orc8^-@p#^%tangent leads you away from the real cause of the problem, contributesdH^5@p"^.very little useful information, and it consumes lots of valuable timeeP^8@p^6and effort.fX^:@pg^;@pg ^D@p$^<So, give yourself a break. Don't take a chance on a trip down the gardeng8@p!^Epath. Instead, use the time to carefully think out your experiment.z^P@p^Oa(_1.2.L.iP^RG-j^Sj ^U
`^^@p$^VThe.experimentDdoesn'tehavehtovbetcomplexeorhelaborate. Let'sgopbacktojP^g@p#^gthe.problem definition andltegssthatrweeusedsearlier,qandseeifweEcank`^p@p#^hdevise aacouple ofesimplesexperimentsthatwillprove,2or.disprove,thelp^r@p^qtegs.n^s@pn ^u@pn8^}@p ^vDef -  4 days/2020/256K/cache/TOPS-20(4.1)/UBANXM/freq:12-14 hrs.nP^~@poP@p^Teg #1. A low voltage condition exists at one of the UBAs.oh
`_*@p_%Review - The key points discussed so far are:tH_,@pu(_4@p!_- 1. Research and Define the problem (in writing). Find out exactly:u@_:@p_5     a) What is happening that shouldn't ?vH_@@p_;     b) What is not happening that should ?w(_F@p_A     c) What are the surrounding conditions ?x_H@pxh_P@p!_I 2. Treat each error symptom as if it was a separate problem. Then,y_W@p_Q    select the most obvious problem and work on it.z_Y@pzx_b@p#_Z 3. Venture a testable educated guess (teg) as to what might be causing{_e@p_c    the problem.| _g@p|X_p@p#_h 4. Setup an experiment that will either prove, or disprove your guess.|p_x@p"_q    Take your time. Make sure the experiment is a valid test. If it's~_@p_y    not, you may waste a lot of time chasing a tangent.`@px`	@p"`If you've been following this course, right around now you should be
`@p"`
getting some idea of how effective a problem solving approach such as
`@p"`this can be. Essentially, it is a systematic process of elimination.
 `#@p"`Properly used it will isolate and ultimately eliminate virtually any
(@p`$problem a system can develop. It's just a matter of time.z`.@p`,sH`f1.2.N.
(`/G-
``1
x`2
``;@p"`3Step 4 - PREDICT the result of the experiment before you conduct it.
(`C@p `<The purpose of this step is to double check the validity of your
0`K@p!`Dexperiment. The prediction should be based on the assumption that:
0`M@p
	8`S@p`N 1. Your teg or guess is absolutely correct.
	P`T@p
0`\@p`U 2. Your experiment is a true and valid test of your teg.
H`]@p
@`_@p
X@p``Both of these assumptions will be verified later in Step 6.z`j@p`h
(aA1.2.O.
h`kG-
 `m
8`n
``w@p$`oAs trivial as this step may seem, it should never be skipped. Nor should
h`~@p`xyou ever leave it up to "maybe" type thinking:
x`@p
`a@pa    Maybe...this will happen   (or)   Maybe...that will happen
xa	@p
xa
@p
a@p#aWhen it comes to your experiment and the predicted result, "maybe" type
(a@p$athinking leads to: "Gee.. that's interesting; wonder what it means" type
8a%@p$acuriosity. And that my friend, will lead you right down Old Garden Path.
Ha'@p
Xa(@p
pa1@p#a)Therefore, if you decide to use this problem solving approach, keep in
a9@p#a2mind that your prediction should be explicitly stated and well thought
@pa:out. Don't get tricked into going off on a wild turkey chase.zaE@paC
hb
1.2.P.
aFG-
PaH
haI
`aQ@paJGetting back to our example, let's add a couple of predictions:
aS@p
aT@p
0a\@p aUDef -  4 days/2020/256K/cache/TOPS-20(4.1)/UBANXM/freq:12-14 hrs.
Ha^@p
Hae@pa_Teg #1. A low voltage condition exists at one of the UBAs.
`am@pafExp #1. Use up a DVM to test the voltage at each UBA.       
Xau@p anPre #1. The voltage at one of the UBAs will be out of tolerance.
Pav@p
Pa}@pawTeg #2. One of the Unibus cables is improperly seated.
hb@pa~Exp #2. Clean and reseat each cable in the Unibus.
X@pbPre #2. One of the cables will be loose or dirty.zb@pb
c,1.2.Q.
!(bG-
!`b
!xb
`b@p#bWell, that's it for the hard part. The last three steps are relatively
"(b#@p#bsimple and straight forward. But before we go on, let's quickly review
#0b'@pb$the main points:
$8b(@p
$pb/@pb) 1. Research and Define the problem. Find out:
%b0@p
%pb6@pb1     a) What is happening that shouldn't ?
&b<@pb7     b) What is not happening that should ?
&hbB@pb=     c) What are the surrounding conditions ?
'HbD@p
((bL@pbE 2. Treat each error symptom as if it were a separate problem.
(@bM@p
)@bV@p!bN 3. Venture a testable educated guess (teg) as to the cause of the
)XbY@pbW    problem.
*`bZ@p
+bc@p"b[ 4. Setup an experiment that will either prove, or disprove your teg.
+(bd@p
,0bm@p"be 5. Predict the result of the experiment in advance. Assume that your
,Hbv@p#bn    teg is correct and your experiment is valid. Be explicit. State (in
-Pb|@pbw    writing) exactly what you expect to happen.
.`b~@p
/H@p"b 6. Avoid "maybe" type thinking. It's liable to get you into trouble.zc
@pc
!(cN1.2.R.
0hcG-
1c
18c
`c@p#cStep 5 - CONDUCT the experiment - This is the most exciting step in the
1hc @p!cformal problem solving process. Here's all you have to do. Either:
2xc!@p
4c&@pc" 1. Check the voltage at each UBA.
4c(@p
4hc-@pc) 2. Clean and reseat each UBA cable.
5c/@p
5Xc0@p
5pc9@p"c1Unfortunately, this is where a lot of people fall down. They're over
6cA@p!c:whelmed by the task. So they tend to put it off. After all checking
7cJ@p"cBthe voltage at each UBA, or cleaning and reseating each UBA cable is
8@pcKnot a five minute job.zcQ@pcP
0hd
1.2.S.
9`cSG-
:cT
:0cV
`c^@p"cWBut, if you properly setup the experiment, then half the job is done.
:`cg@p#c_Now if it's going to take awhile to conduct the experiment, set a time
;hcp@p#chlimit. Don't rush, but try to estimate how long it will take. You might
<pcy@p#cqbe surprised to find that, once your setup, it only takes a few minutes
>d@p#czto check the voltage at each UBA. So if you've five UBAs to check, you
?@pdcould easly be done in ten minutes. That's not so bad.zd
@pd
9`db1.2.T.
AdG-
A@d
AXd
`d@p#dWhen it comes to cleaning and reseating cables, however, that can be a
Bd!@p"dlarge undertaking. At two or three minutes per connector, that could
Cd*@p"d"require forty five minutes or an hour to complete. At this point you
Dd2@p!d+might want to revise your experiment: you might decide to clean and
E d;@p#d3reseat a third of the UBA cables, and see if that corrects the problem.
F(d=@p
G8dE@p#d>There is a trade-off involved here. You must consider; the seriousness
GPdN@p!dFof the problem, the frequency of recurrence, and the amount of time
HXdV@p#dOand effort necessary to prove (or disprove) your TEG. The decision is 
I`d_@p#dWsubjective, and entirely up to you. The rule of thumb here is: Do what
Jh@p	d`you think is right.zdf@pdd
Ae@1.2.U.
L(dgG-
L`di
Lxdj
`ds@p#dkStep 6 - EVALUATE the result - After conducting the experiment compare
M(d{@p#dtpredicted result, with the actual result. If they match, then you have
N0e@pd|accomplished one of two things.
O8e@p
Pe	@pe 1. You have either identified the cause of the problem, or
P e@p
Qe@p e
 2. You have gathered some new, fairly reliable, information that
Q0e@pe    you can use to refine the problem definition.
R0e@p
Se@p
S0e@p
SHe&@p"eIf the predicted result and the actual result do not match, however,
S`e/@p#e'then there is a conflict.  Either the experiment tested something other
The8@p#e0than your teg, or your understanding of the experiment (the prediction)
Ux@pe9was incorrect. In either case you should STOP IMMEDIATELY.zeC@peB
L(f1.2.V.
XeEG-
X8eF
XPeH
`eQ@p$eIYou must figure out which was in error; the experiment, or the predicted
YeZ@p$eRresult. If, after some thought, you decide that the predicted result was
Zec@p#e[in error, that's ok. It means that the experiment was, in fact, a valid
[ el@p$edtest of your teg. And, therefore, the result can be used with confidence
\0eq@pemto refine the definition of the problem.
]@es@p
^e|@p$etIf, however, you discover that the experiment was in error; that is, the
^0f@p#e}experiment was not a valid test of your teg, then be very careful. You
@f$fshould reconsider the entire situation and either; revise the experiment
`Hf@p#fin such a way that it is a valid test of your hypothesis, or scrap the
aX@pfwhole thing and start over again. zf@pf
Xfb1.2.W.
c0f G-
chf!
df#
`f,@p$f$Now you can see the importance of predicting the result of an experiment
d0f5@p$f-before you conduct it. If you are unable to determine whether or not the
e@f>@p$f6experiment was, in fact, a valid test of your teg then, you're liable to
fPfG@p#f?"assume" that it was. And that kind of an assumption may lead you right
g`fK@p
fHdown the Old Garden Path.
hpfL@p
i0fU@p#fMThe point here is: if you know what you expect to happen, then you are
iHf^@p#fVmuch more likely to recognize cases where the experiment is not testing
jP@p
f_what you think it is.zfe@pfd
c0gJ1.2.X.
l fgG-
lXfh
lpfj
`fr@p#fkCHANGES - If an experiment requires that you change  the system in any
m f{@p"fsway (swap a cable, perform an adjustment, exchange a module, etc.) be
n(g@p"f|sure that you can restore the system to its original state should you
o0g
@p#gneed to. One fool proof way of doing that is to keep notes. Notes don't
p8g@pg
qHg@p
qpg@p"gSurely, in the past at least, some very successful technicians didn't
rg!@p#gkeep any notes at all. But that doesn't mean that they shouldn't have;
sg*@p#g"it only means that they didn't. And that's too bad, because that means
tg3@p#g+that they were using part of their brain muscle to recall facts, there-
u g;@p"g4fore, less of their brain muscle was available to think about solving
v0gD@p$g<the problem.  Besides, once you get used to it, thinking is much more fun
w8@pgEthan recalling facts. Don't you think ?zgM@pgL
l gX1.2.Y.
y gOG-
yXgP
ypgR
`@pgSEither you disagree, or you're not thinking.zg[@pgZ
y le1.2.Z.
{g]G-
{8g^
{Pg`
`@pgaSo do I.zgf@pgd
{XK
1.2.A1.
|(ggG-
|`gi
|xgj
`gs@p$gkBack to CHANGES. If you change the system and the change doesn't correct
}(g|@p#gtthe problem, then you should restore the system to it's original state
~8h@p#g}as soon as possible. If you don't, then you should realize that you are
@h#hrunningtthesrisktofnintroducing@newproblemsintothe.system and thus,
`h#@p#hNEWdSYMPTOMSa-tFinally,tifsyouvrestoreetheSsystemototitsnoriginalstate1.
`hS@p"hLStepp72--REFINErthe definitioniandhREPEAT thepprocessdbeginning with
8he@p#h]experiment,eandpthemresultsofothe experimentptonthehproblemmdefinition.
Phv@p!hnthebdefinition.iAtpleastoyoueknowonenthingthatisnotcausingthe1.2.D1.
`i&@p#iTakelyourhtimemappendingitheenewtinformationetowthecproblemsdefinition.
@p#jjsupport.wButtevenwaucallforsupporteiseategnof.fashions,dbecauset from
`j'@p#jOneolasttworddbeforeAwergoconwtorthevfinalisummary.sEarlier,ewentalked
j9meanneverucalltsupport.l.vIt'sitherettophelpeyoutdoeyourdjobwmorerefficiently.1.2.F1.
`jp@p#jhNeverGgivecupsreallybmeans,wnevercleteawproblemlgoawithoutdfindingioutou
thecausewasandthowyheioryshesarrivedoatrthatmconclusion.olved.sAndlthat'slwherezk1@pk/@ \h,1.2.G1.
`k8@pk6FinalRSummary:ndaDEFINEgtheaproblem.nFindoutsexactly:ause.e,wyouryteg.7bhuRF.T.1.3.
`l@@p#l9ThattconcludesetheiexplanationmofithepFormal.Troubleshooting Approach.
kxuiR.T.1.2.G1.
`lY@p#lQSTOPu- Youbare movinghinFarreverseudirectionnthroughathe menu. You are
lbYour response please:zlF@pV#
{m"
`lo@pllSystematicsSubstitutionetpuristatechniciansnmayfnotaagree,tbutiunder
Forexample,mlet'soassumelthatFyouhareoat,home,sinsNeweEngland,uworkingapcircular
`m2@p#m+Suddenly,wtheesawgbinds,ethetlightstdimcandithenstheylgoeout.eFromftheure
@pn	.3.B.
G-n
`n@pnAt1thisupointsyoulhave,troughly,nsixhoptions:roblemuwillpdisappear.nThis,
`@p!nRD2.You can call an electrician, but that could be very expensive.zn]@pn[
`nj@p$nbk3.You canigongetyatflashlightu(ifyouncanpfindone that works) and use
`o@p"nx4. Youtcantlightiaucoupleemorehmatches,gstudy.thetwiringtdiagramtandris@po
1.3.F.
`o*@p!o#+5. YougcancuseethevsparescanderandomlylsubstituteTfusessuntilrtheezoQ@poO
1.3.G.
`o^@p$oVh6.Youecanguseatheesparesoandisystematicallybsubstituteteachpfuseluntil
`p@p#pNowlet'spsaythat,afterRcarefulconsideration of all six options, youPp@p"preject wishful thinking and random substitution because they are both`p@p#prisky and impractical. Next, you dismiss the possibility of calling anhp(@p$p electrician because it seems unnecessary and it could be very expensive.pp)@pp2@p"p*Finally, you eliminate using the wiring diagram to figure out exactlyp:@p#p3which fuse is blown. The idea is feasible and even tempting, but under pC@p"p;the circumstances it's just too time consuming. Remember, you want to(@p#pDget the saw back on line so you can finish cutting that piece of wood.zpO@ppM
pS
`p\@p"pTThat leaves you with two options; either go get a working flashlight,
8pd@p#p]or try the systematic substitution approach. If you opt for the flash-@pm@p$pelight, that's a trip upstairs, a few minutes locate a flashlight, a trip
Hpv@p"pnbackndownacellarmandl30fsecondsutosreplace thesblownifuse.eTotalttime`q@p#prequired to return the flashlight so that you can find it the next timehq
@pqyou need it.)xq
@p(q@p$qNof optingforqthepflashlight,%youoptedJforthe@q@p#qsystematicsubstitutionqapproach and, on the fourth try you locate thePq&@p$qblown fuse. Total time expended (at 30 seconds per fuse): 2 minutes withX@p
`q;@p#q4One last supposition; suppose that instead of working in your cellar, 0qD@p#q<you had just arrived on site. Instead of a dead power line you're faced8qM@p#qEwith a failing subsystem. Instead of six fuses in a box, the subsystemHqU@p#qNconsists of four modules, a cable and a power supply. Finally, insteadPq^@p"qVof a box of spare fuses and a wiring diagram you have a spares kit, aXqf@p"q_scope, and a set of prints. But the diagnostics that you need are not`ql@pqgon site. The same six options apply:hqm@p@qu@pqn1. You can stall for time wishing the problem will go away.Xqy@pqv2. You can call for support.Pr@p#qz3. You can go back to the office and get the diagnostics that you need.r@p!r4. You can study the print set and try to figure out what's wrong. (r@p$r
5. You can randomly substitute the spares and hope to solve the problem.!0r@p$r6. You can systematically substitute the spares and quickly identify the"@@p#r   cause. There are, however, some things that you should be aware of:zr)@pr'0s0&1.3.K.$Xr*G-%r,%(r-
`r6@p"r.A.sYouomustrapproachthepsubstitutionprocesssystematically.rIfayou%Xr>@p!r7odudon't,vyou'll becomeoconfused andendrup@resorting toothelrandom&`rG@p#r? yomethodooflsubstitution.hTherrandomhmethodXissoprone to error that'hrK@p
r_   their weight in gold.+hrd@p,(rl@p#reC. If you substitute a module and the problem doesn't go away, replace,@ru@p"rm   the original module immediately. If you don't, you'll run the risk-Hr}@p"rv   of introducing new problems into the system. Spares tend to have a.Ps@p"r~   higher failure rate than modules that have been in use for awhile./Xs@p0`s@p$sD. If you substitute a module and the symptoms change, STOP. Replace the0xs@p"s   original module. If the original symptoms return, then chances are2s"@p#s   you have come upon a bad spare. Try it one more time. If the results3s*@p#s#   are the same; Tag the spare right away. If you don't, you're likely4 @ps+   to forget and reliable spares are a must. zs4@ps2$XtX*1.3.L.6s5G-6@s76Xs8
`sA@p#s9E. If you substitute a module and the symptoms change, and they remain7sI@p"sB   changed even after you replace the original, STOP. Chances are you8sR@p#sJ   inadvertently changed something and didn't realize it. Retrace every9s[@p"sS   step. Symptoms change for a reason. Find the reason. Don't run the:(s`@ps\   risk of compounding the problem.;0sa@p<sj@p"sbF. If you substitute a module and it seems to solve the problem don't<sr@p!sk   stop. Confirm the fix. Return the original module. The symptoms= s{@p#ss   should appear. If they don't, then you can't be sure that you found>(t@p$s|   the problem. If they do, then you can be pretty sure that you got it.?0t
@p"t neBut,odon't stop yet.tRuntthehdiagnosticsionelmoreatime.oMakesure@@t@p$t few minutes, make sure that the equipment comes back on line ok.BXt@pC`t(@p#t G. Back to the case where the spare seemed to correct the problem, butCxt1@p#t)   when you replaced the original module to confirm the fix, everythingEt:@p$t2   seemed to work fine. In this case you may, or may not have identifiedFtC@p#t;   the cause of the problem. You don't know. So, leave the spare in theG tL@p#tD   system, tag the suspect module as potentially intermittent, and saveH0tU@p$tM   your notes. Such situations call for a different type of confirmationI@@ptV   technique. zt[@ptZ6v1.3.M.Kt]G-K8t^KPt`
`ti@p#taThe technique is called the subjective time window. To use it, you mustLtr@p$tjto establish a period of time during which you will monitor the problem.Mt{@p$tsUsually a week is adequate, if the problem was solid. If the problem wasN u@p$t|intermittent, however, then you must determine the rate, or frequency ofO0u
@p"utheyfailure,mtripleite(atoleast),anduusepthatastheperiodoftimeP@u@pu not recur during the time window that you set up,R@u$@p uthen you can assume that you solved it. Tag the suspect module asSHu-@p!u%intermittent, return it for repair, file your notes, and close outTHu5@p"u.the paper work. If, however, the problem does recur, then you're allUPu=@p u6set, replace the original module, update your notes, and pick upVXuE@p u>where you left off. That's all there is to it. As some of the oldWXuN@p!uFschool hard-liners would say; Hey, at least you know what it's not,XX@puOand that's worth something. zuV@puT
`uc@p#u[ThatMconcludesGtheexplanationofthe]SystematicSubstitution Approach.[(@pudNext on the menu is the Variable Approach.zum@puk
`uz@p#urSTOP - You are moving in a reverse direction through the menu. You are^v@pu{about to back into the Systematic Substitution Approach._ v@p`@p
vYour response please:zv	@pm Kv;`pvG-av
a0v
`v@pv                   The Variable Approacha`v@pb8v@p"vThis short story was once told by a senior field service engineer tobPv&@p!villustrate a VERY important point about using the variable approachcXv.@p"v'to isolate the cause of an intermittent failure. The story is about ad`v7@p"v/telephone conversation he had while working for another company (noteh@pv8to be mentioned).2.M.lost.zv?@pv=`pw#1.4.A.g8v@G-gpvBhvC
`vL@p#vD"At first, the diagnostic only failed every hour or two. So I performedh8vU@p$vMall the standard checks and adjustments. The problem got a little worse,iHv^@p"vVbut it still wasn't solid. So then, I decided to vary the voltage andjXvf@p#v_clock margins awhile. That helped some. I pulled out a marginal modulek`vn@pvgand the symptoms changed so I knew I was getting closer.lhvo@pm`vx@p#vpThen I thought, maybe the problem had something to do with temperature,mxw@p$vyso I blocked the fans for a few minutes. I just wanted to see if varyingow
@p$wthe temperature would have any effect. Finally, I tapped around with thepw@p#wback of my screw driver awhile. That really helped. I found a couple ofq(w@p$wvibrational modules. But now I seem to have a new problem - I can't evenr8@pwload the diagnostics. What do you think is wrong ?"zw'@pw%g8wZ1.4.B.t8w(G-tpw*uw+
`w4@p$w,At that point, the senior engineer would bellow; "Now that's what I callu8w=@p!w5a dumb question -  Obviously the guy beat the poor thing to death."vHw>@pwPw@@pwhwI@p#wAThe story served it's purpose. Clearly, it illustrates the problem withxwQ@p"wJindiscriminately using the variable approach. That is, if you're noty@p!wRreal careful, you're likely to cause more problems than you solve.zw]@pw\t8x&1.4.C.{ w_G-{Xw`{pwb
`wj@p"wcThe reason is: systems frequently operate in a controlled environment| ws@p#wkfor long periods of time. As a result the environmental operating range}(w|@p#wtof the system narrows. Normally, this is not a problem. As long as the~8x@p#w}environment remains relatively stable the system will run indefinitely.@x@pPx@p#xKeep in mind that; if an intermittent problem is, in fact, being causedhx@p#xby an environmentally sensitive component then, just a slight variationxx!@p$xin voltage, temperature or clock speed should be enough to aggravate it.@px"The rule of thumb is; BE CAREFUL.zx*@px({ U%1.4.D.hx+G- x-8x.
`x7@p#x/After all, if you had an intermittent problem, would you want a doctorhx?@p#x8to double your heart rate in an effort to determine whether or not thepxH@p#x@problem had something to do with your circulatory system ? Probably notxxP@p xIbecause a lot of working parts could get damaged in the process.	xR@p
x[@p#xSKeep that in mind next time you use the variable approach to isolate an
 xd@p#x\elusive intermittent system problem. It will, in the long run, save you0xm@p$xea lot of unnecessary grief and aggravation. And don't forget the rule of
@xo@pxnthumb:               BE CAREFULzxz@pxxMa8
ts_endhx{G- x}8x~
`y@p#xWell, that conclude the Troubleshooting section of the course. We hopehy@p#ythat you found it useful. Also, if you have any comments or know of anypy@p#yother troubleshooting approaches that you think should be added to thisy"@p#ysection please get in touch with us. We're listed under FEEDBACK on they%@py#main course menu. @py&			Thank Youzy+@pm!
TPz(y,G-0y.Hy/
`y5@py0                   System Event Filesxy:@py6                       (Overview)Py;@p yD@p#y<Most operating systems maintain a system event file. The event file is8yL@p#yEused to record information about certain events that happen within the@yU@p!yMsystem (e.g., system reloads, configuration changes, hardware and HyZ@pyVsoftware detected errors, etc.).Py[@p yd@p#y\The classification and type of information that is recorded in a system8ym@p$yeevent file is unique to the operating system maintaining the event file.Hyp@pynFor example:Xyr@pyy@pys  TOPS-10 supports approximately 55 event categories. yz@pz@py{  TOPS-20 supports approximately 25 event categories.(z@p z
@pz!VAX/VMS$supports approximatelyi20 eventicategories.c0z@p!Rzference card.zz@pz{+"2.0.A."`zG-#z#0z
`z&@p!zFile Structures - There is nothing special about the file structure#`z,@pz'associated with a system event file.$hz-@p%@z6@p"z.   a. If the event file is maintained by a TOPS-10 operating system,%Xz>@p!z7      then it conforms to the standard TOPS-10 file structure. For&`zG@p!z?      further information about the TOPS-10 file structure refer to'hzO@p"zH      The TOPS-10 Software NoteBook 17 (Monitor Table Descriptions).(pzQ@p)xzY@p"zR   b. If the event file is maintained by a TOPS-20 operating system,*zb@p!zZ      then it conforms to the standard TOPS-20 file structure. For+zj@p!zc      further information about the TOPS-20 file structure refer to, zs@p"zk      The TOPS-20 Software NoteBook 16 (Monitor Table Descriptions).-(zt@p.0z}@p"zu   c. If the event file is maintained by a VAX/VMS operating system,.H{@p!z~      then it conforms to the standard VAX/VMS file structure. For/P{@p!{      further information about the VAX/VMS file structure refer to0X@p{      The VAX/VMS Software Support Notebook.z{@p{]R.T.2.0.A.2@{G-2x{3{
`{$@p#{STOP - You are moving in a reverse direction through the menu. You are3@@p{%about to back into the System Event File Overview.z{-@pv:"aq 50{/G-5X{05p{2
`{6@p{3		   System Event Files6 {7@p6`{:@p{8Topic Menu:6x{<@p7({?@p{= 0. Overview7@{@@p7p{E@p{A 1. TOPS-10 System Event Files8{F@p8P{K@p{G 2. TOPS-20 System Event Files8h{L@p90{Q@p{M 3. VAX/VMS System Event Files9H{R@p:{T@p:({V@p{UAppendix:@{X@p:h@p{Y A. DEFINE.LST  "DONE"stz{_@p{^	\+Zdefine_lst;@{aG-;x{b<{d
`{l@p"{eDEFINE.LST is a text file that describes the hardware and/or software<@{u@p"{mstatus that is saved for each entry type in both the TOPS-10 and the=H{}@p#{vTOPS-20 system event file. DEFINE.LST is normally stored in the system>P|@p{~documentation area. To obtain a copy of the file type:?X|@p@H|
@p
|PRINT<DOC>DEFINE.LST<cr>@`|@pA |@p!|
If DEFINE.LST is not in the system documentation area you can get aA8|@p"|copy from the Spear distribution tape. There are two procedures; oneB@@p|for TOPS-10, the other for TOPS-20.tops_10_efsystem.0z|(@p	|%	!X},pri_define_tops_10D8|)G-E|+E|,
`|5@p#|-TOPS-10 procedure to copy DEFINE.LST from the Spear tape to your area.EH|6@pFP|?@p!|7Assign a magtape (xxx), mount the Spear tape, run BACKUP, and type:Fh|B@p	|@  /TAPE MTxxx:<cr>Gp|E@p|C  /REWIND<cr>H(|I@p	|F  /INTERCHANGE<cr>HX|L@p|J  /FILES<cr>I|P@p|M  /SUPERSEDE ALWAYS<cr>I@|S@p|Q  /SKIP 1<cr>J|Y@p|TNote: BACKUP will print "DONE" and reprompt. Type:J0|[@pK|`@p|\  /RESTORE DEFINE.LST = DEFINE.LST<cr>K0|h@p |aNote: BACKUP will print the following message and reprompt. Type:L|j@pV#M|m@p|k  "DEFINE LST"M |n@p{ZMP|p@pMh|s@p|q  /UNLOAD<cr>N|v@p|t  /EXIT<cr>N0|~@p|wNote: Remove and return the Spear distribution tape. Then type:N`|@pO`@p
}PRINT DEFINE.LST<cr>z}@p	}D8Hq,pri_define_tops_20P0}	G-Px}
Q}

`}@p#}edure to copy DEFINE.LST from the Spear tape to your area.Q@}@pRH}@p!}Assign a magtape (xxx), mount the Spear tape, run DUMPER, and type:R`}"@p
}  DUMPER> TAPE MTxxx:<cr>Sh}&@p
}#  DUMPER> REWIND<cr>T(}*@p
}'  DUMPER> INTERCHANGE<cr>T`}-@p	}+  DUMPER> FILES<cr>U }2@p}.  DUMPER> SUPERSEDE ALWAYS<cr>UX}5@p
}3  DUMPER> SKIP 1<cr>V }>@p"}6Note: DUMPER will print two information messages and reprompt. Type:VX}?@pW`}G@p}@  DUMPER> RESTORE PS:<*>DEFINE.LST PS:<your directory><cr>Wx}O@p }HNote: DUMPER will print the following message and reprompt. Type:Xp}P@pYp}V@p}Q  % RESTORING FILES TO PS:<your directory>Z}\@p}W  PS:<*>DEFINE.LST => DEFINE.LST [OK]Zh}]@p[@}a@p
}^  DUMPER> UNLOAD<cr>[X}b@p\}j@p}cNote: Remove and return the Spear distribution tape. Then type:\(}l@p](@p
}mPRINT DEFINE.LST<cr>entry.0_efz}s@p|!	8~"^}tG-^0}v^H}w
`}|@p}x		TOPS-10 System Event Files^x}}@p_@~@p#}~The section of Instruct consists of a series of questions that pertain_X~@p!~to the TOPS-10 System Event File (ERROR.SYS). Before you attempt to``~@p"~answer the questions you should review Chapter 2 of the Spear Manual.ah~@pbp@p"~Don't forget, you can use the /BREAK feature and return via your ID.j(~WG-z~&@p~$^	
9tops_10_ef_ad(~(G-dh~)e~+
`@p~,Press the RETURN key when you are ready.z~4@p~2'Btops_10_ef_q1f~6G-fH~7f`~9
`~>@p~:TOPS-10 System Event Files - Q1 of 10g~@@pgh~H@p!~ATrue or False -  Many of the questions that pertain to the TOPS-10h@p ~Isystem event file also pertain to the TOPS-20 system event file.tops_10_ef_q2_alost.z~!@p~Tqh9tops_10_ef_q1_atd~Xjp~Z
`~]@p~[That's correct.k ~^@pkP~g@p#~_In fact, the questions are practically identical. In many cases so arekh~o@p"~hthe answers. Therefore, if you have already answered the questions aslp~x@p"~pthey pertain to the TOPS-20 system event file, then you can probablymx@p#~yafford to skip this section of Instruct. Of course, on the other hand,o	@p"you may want to answer the questions anyway. If that's the case, thenp@p
don't be confused by the redundancy.z@pH~Rtops_10_ef_q1_afqhG-r0rH
` @p$The statement is TRUE. The TOPS-10 system event file (ERROR.SYS) and therx)@p"!TOPS-20 system event file (ERROR.SYS) are very similar. Therefore, itt1@p"*stands to reason that many of the questions that pertain to one eventu@p2file will also pertain to the other event file.z VG-z<@p~Pj(nw=G-w@?wX@
`F@pATOPS-10 System Event Files - Q2 of 10xG@px`@p!HTrue or False - The TOPS-10 System Event File is called ERROR.SYS. tops_10_ef_q3_aTRUEz8@pT}aAtops_10_ef_q2_atwXzhY
`\@pZThat's correct.{^@p{Hg@p$_Both the TOPS-10 and the TOPS-20 system event file are called ERROR.SYS.{`@phThe VAX/VMS system event file is called ERRLOG.SYS.zr@ppwRtops_10_ef_q2_af}`tG-~(u~@w
`@p#xThe statement is TRUE. The idea of a system event file (ERROR.SYS) was~q@p#first implemented in the early 1970's for TOPS-10. Initially, the filey@p#	was used only to record main memory, channel, and disk errors. The idea@p$proved to be a good one and new entries were added to the file until now"@p"ERROR.SYS is the main source of information for solving intermittent!&@p#system failures.)'@pa0@p"(In the mid 1970's the idea of a system event file along with the filey8@p#1name ERROR.SYS was carried over to TOPS-20. Thus, both the TOPS-10 and@p9the TOPS-20 system event file are called ERROR.SYS.
eG-z	C@pOz!BEG-9FPH
aM@pITOPS-10 System Event Files - Q3 of 10	O@p	YW@p!PTrue or False - Prior to the Spear library, TOPS-10 used a program	p@pXcalled SYSERR to record entries in the system event files.tops_10_ef_q4_aFALSEz	?@pc)mtops_10_ef_q3_atyg
Xh
aq@p#iThenstatementiis FALSE.cNeitheroSYSERRinorithehSpeartlibrarythaveeany-t@p{is strictly a function of the operating system.!@p	
@p#Both SYSERR and the Spear library are designed to process the contents!@p#of the system event file. SYSERR was a report generator. Basically, it)@p#allowed the user to select and translate specific entries in the event1$@p$file. The SPEAR library (SYSERR's replacement) is more sophisticated. In9-@p#%addition to translating event file entries it also attempts to localizeI6@p$.the cause of intermittent disk and tape subsystem failures. Note howeverY?@p"7that neither SYSERR nor Spear have anything to do with recording theh@p	@system event file.z	G@pDa
tops_10_ef_q3_af)HG-qJK
aO@pLThat is correct.9P@pqY@p"QBoth SYSERR and its' replacement, the SPEAR library, are designed to 	a@p#Zprocess the contents of the system event file. They have nothing to doj@p$bwith recording the entries. That is a strictly function of the operating@p|"!G-z	p@p^
HYqG-st
az@puTOPS-10 System Event Files - Q4 of 10I{@p!@p!|True or False - All hardware detected failures are recorded in the8@p	system event file.tops_10_ef_q5_aTRUEz	l@p)ctops_10_ef_q4_atA!`
a@p!The statement is FALSE. Only failures that require operating system""@p"intervention are recorded in the system event file. Failures that do#+@p##not require operating system intervention are not recorded in the event$!3@p",file. For example, some subsystems attempt error recovery locally. In%1<@p!4most cases, if the recovery is successful then the operating is not&9D@p#=notified. Thus, those kinds of errors are normally not recorded in the'@@p	Esystem event file.z	L@pJY	tops_10_ef_q4_af)NG-)IO)`Q
aT@pRThat's correct.*U@p*A^@p#VOnly errors that require operating system intervention are recorded in*X@p_the system event file.0!G-z	f@p!$,9gG-,ai,xj
ap@pkTOPS-10 System Event Files - Q5 of 10-)q@p.z@p#rTrue or False - Every record in a TOPS-10 system event file consists of.@p{a header section and a body section.tops_10_ef_q6_aTRUEz	b@p4Ie
tops_10_ef_q5_at,!0h	
a
@p
That's correct.1@p1I@p$Furthermore, the header and body section of each entry type is described1a@p"in a file called DEFINE.LST. To obtain a copy of DEFINE.LST, refer to2p@p Appendix A on the Event File Menu.z	)@p&,9tops_10_ef_q5_af4I*G-5,5(-
a6@p!.The statement is TRUE. Each entry in the TOPS-10 system event file5Y>@p#7consists of a header section and a body section. The header identifies6aG@p#?the entry type (i.e., event code), the date and time that the entry was7iP@p#Hrecorded, the processor serial number, the length of the header section8yY@p$Qand the length of the body section. Currently, the header section is set:	b@p#Zat four words, the body section varies in size depending on the type of;@p}o@)G-z	h@p0!T<YiG-=k=l
ar@pmTOPS-10sSystemeEventFiles -0Q6fof710=Is@p>!|@p"tTrue or False-EachrecordinaTOPS-10system event file represents>8@p

a@p$The statement is true with one exception, KLERR. KLERR entries are builtA!@p#by the console front-end whenever the KL10 crashes. When the system isB1$@p$restarted the entry is transfered via the DTE to KL main memory and thenC9)@p%recorded in the system event file.DI+@pE4@p$,Because the buffer area set aside for communications between the consoleE1=@p#5and KL main memory is significantly smaller than a typical KLERR entry,FAF@p$>the entry divided into segments. Each segment is given a unique sequenceGQO@p$Gnumber and recorded as a separate record in the event file. Technically,H`@pPtherefore, the statement is FALSE.z	X@pV<Y
tops_10_ef_q6_afJAZG-K	[K ]
a`@p^That's correct.KQa@pLj@p$bThe KLERR entry consists of multiple records. Each record has a separateLs@p"ksequence number. When a KLERR entry is translated, however, only theM)|@p#tfirst sequence number is used to identify the entry. The other sequenceN0@p}numbers are masked-out to avoid confusion.T9(G-z	@p@)@P9G-Pa	Px

a@pTOPS-10 System Event Files - Q7 of 10Q)@pR@p"True or False - The synchronization word is used to recover from hardR@pread errors that occur while reading the system event file.tops_10_ef_q8_aFALSEz	@p%X	!tops_10_ef_q7_atP!)U+
a.@p,That's correct.U1/@pUa8@p!0Whenever Spear uses the synchronization word to recover from a hardUx@p"9read error it will print the message "Bad header found - RESYNCing".z	E@pBP9#tops_10_ef_q7_afX	FG-XQHXhI
aR@p"JTheestatement islTRUE.ThezfirstwordineachsystemTeventefile dataYZ@p#Sblockois aosynchronizationkpointer.sThepointer points to the startingZ!c@p![location of the next record in the file. Thus, if a hard read error[)l@p#doccurs while reading a record Spear skips to the next data block, reads\1t@p!mthe sync word, finds the starting location of the next record, and]Ay@p
@p#event filerwas incorporatedginhthevmid 1970's.aPrior tocthattime,@if%a`9@p#re lost. Now only the records affected by the read error arebP@pv:t)'G-z	#@p!T9\*d%G-d9&dP(
a-@p)TOPS-10 System Event Files - Q8 of 10e/@peY8@p$0True or False - When the TOPS-10 operating system detects a device erroreq<@p
9the following occurs:g=@pgAF@p$>1. Normal operation is suspended and applicable hardware and/or softwaregYO@p$G   status is captured (at error) and saved in the Unit Data Block (UDB).hiQ@piyX@pR2. If applicable, an error recovery algorithm is applied.jZ@pk	b@p"[3. Regardless of whether the recovery algorithm is successful or not,k!k@p!c   the applicable hardware and/or software status is captured againl)p@pl   (at end) and appended to the UDB.m1r@pn	{@p#s4. The error status stored in the UDB is formatted, assigned a sequencen!@p|   number, and appended to to the system event file.o1@pp!
@p"5..Ifftheosystem was ableetowrecoverlfrom theoerrorrnormaloperationp9@prthen the job affected by the error is notified and itr@@p
   handles the error.tops_10_ef_q9_aTRUEz	@p${Iptops_10_ef_q8_atcy(tp*
a-@p+That's correct.u!.@puQ6@p /The action outlined in the question is typical of the way TOPS-10ui?@p"7handles most device errors. Non-device errors (e.g., CPU errors) andviG@p"@errors that affect the operating system itself are also handled in awqP@p"Hsimilar manner. If, however, there is no recovery algorithm or if thexyX@p"Qrecovery algorithm is unsuccessful, then those errors may result in az@p
Yuser job or system crash.z	a@p^d"tops_10_ef_q8_af{IbG-|d|(e
`@p#fThe statement is TRUE. Most TOPS-10 device errors are handled this way.aG-z	r@p t),~tG-~)u~@w
a|@pxTOPS-10 System Event Files - Q9 of 10~q~@pI@p!True or False - The exact content and format of each TOPS-10 event`@precord is described in the Spear Manual.tops_10_ef_q10aFALSEz	n@pA
Rtops_10_ef_q9_at}i(
a@p!The statement is FALSE. The Spear Manual does describes the reportY&@p!formats generated by Retrieve, but it does not describe the content`@p'and format of the actual event records.z	0@p.~tops_10_ef_q9_afA2G-	3 5
a8@p6That's correct.Q9@p@p:The event records are described in a file called DEFINE.LST.IyG-z	E@pf		K)FG-QHhI
aO@pJTOPS-10 System Event Files - Q10 of 10	P@p	qY@p#QTrue or False - The fifth word in a 011 type record is used to save the
	a@pZresults of the DATAI performed at the time of the failure.b@p
k@p%cNote: Refer to DEFINE.LST. If you do not have a copy of DEFINE.LST and you
(@plwant one, refer to Appendix A on the Event File Menu.tops_10_ef_lq0_TRUEz	A@pv8tops_10_ef_q10_atz|
a	@p#}ThelstatementdisiFALSE.bOpen0the.DEFINE.LSTntobthea011lentry.aIttstartsA		left of the page.Y	@p	@p!	Now skipping over the word, byte, and bit definitions, go down the)	#@p"	center, or word number column, until you get to word number 5. To the1	,@p#	$left you will see that word number 5 is defined as CONIINITIAL. To the9	5@p#	-right you will see that CONIINITIAL is described as "controller statusI	8@p	6at error".Y	9@p	B@p#	:Now find word 16. You will see that it is defined as "RHDATABARERR",@p#	Cand described as: DATAI from RH10 block address register at error time.z		P@p	M)ttops10efq10af9	QG-	S	T
a	W@p	UThat's correct.I	Y@py	a@p#	ZWord 5 is used to save the CONI status word. The DATAI status is saved	j@p"	bword 16. Anytime you want to know exactly what hardware and software	q@p	kstatus is saved in an entry type you can consult DEFINE.LST!	s@p	|@p$	tNow, if you haven't already done so, take a few minutes to look over the1
@p$	}contents of the file. The introduction explains the overall organizationA
@p#
and format of an event file record. Following the introduction, each of Q
@p
the event types are described in detail.!a
@p"9
@p#
When you are finished, take a few more minutes and compare the reports"Q
&@p"
listed in the Spear Manual with the corresponding record descriptions#Y
/@p#
'listed in DEFINE.LST. As a result, you will have a better understanding$`@p"
0of the system event file and the reports that are generated from it.tops_20_efTRUEz	
;@prd(~0'
=G-'9
>'P
@
a
I@p$
AThat's it. There are only 10 questions about TOPS-10 System Event Files.(@p
JPress the RETURN key to return to the System Event File Menu.system._efz	
T@p
7a*!
VG-*I
W*`
Y
a
]@p
Z		TOPS-20 System Event Files+
_@p+Y
g@p#
`The section of Instruct consists of a series of questions that pertain+q
p@p!
hto the TOPS-20 System Event File (ERROR.SYS). Before you attempt to,y
x@p"
qanswer the questions you should review Chapter 2 of the Spear Manual..
z@p/@p"
{Don't forget, you can use the /BREAK feature and return via your ID.6A8G-z	@p*!/tops_20_ef_a0A	G-11

`@pTURN key when you are ready.z	@puy6tops20efq12!G-2a2x
a @pTOPS-20 System Event Files - Q1 of 103)!@p4*@p!"True or False -  Many of the questions that pertain to the TOPS-104@p +system event file also pertain to the TOPS-20 system event file.tops_20_ef_q2_a		(z	@p6>
tops_20_ef_q1_at0):7;
a>@p<That's correct.79@@p7iH@p#AIn fact, the questions are practically identical. In many cases so are8Q@p"Ithe answers. Therefore, if you have already answered the questions as9	Y@p"Rthey pertain to the TOPS-10 system event file, then you can probably:b@p#Zafford to skip this section of Instruct. Of course, on the other hand,;j@p"cyou may want to answer the questions anyway. If that's the case, then< @pkdon't be confused by the redundancy.z	t@pr\Y4tops_20_ef_q1_af>vG->Iw>`y
a
@p$zThe statement is TRUE. The TOPS-10 system event file (ERROR.SYS) and the?
@p"
TOPS-20 system event file (ERROR.SYS) are very similar. Therefore, it@!
@p"
stands to reason that many of the questions that pertain to one eventA(@p
file will also pertain to the other event file.F9
8G-z	
@p16A
OC1
G-CY
 Cp
"
a
'@p
#TOPS-20 System Event Files - Q2 of 10D!
)@pDx@p!
*True or False - The TOPS-20 System Event File is called ERROR.SYS. tops_20_ef_q3_a3.0.z	
@p
5Iytops20efq2atC
9G
;
a
>@p
<That's correct.G1
?@pGa
H@p$
@Both the TOPS-10 and the TOPS-20 system event file are called ERROR.SYS.Gx@p
IThe VAX/VMS system event file is called ERRLOG.SYS.z	
T@p
QC1
3tops_20_ef_q2_afIy
UG-JA
WJX
X
a
a@p#
YThe statement is TRUE. The idea of a system event file (ERROR.SYS) wasK	
i@p#
bfirst implemented in the early 1970's for TOPS-10. Initially, the fileL
r@p#
jwas used only to record main memory, channel, and disk errors. The ideaM
{@p$
sprovedto be a good one and new entries were added to the file until nowN)
|ERROR.SYSiisrthemainPsource of information for solving intermittentO9
In@themidR1970'satheaideadofvarsystemPeventRfile,alongwithTthe-fileQ@p
1F9$T)
a@pSystem-EventrFilesh-iQ3eof 10UeTOPS-20 usedsaprogramV@p
a@p#ementiisnFALSE.cNeitheroSYSERRinorithehSpeartlibrarythaveeany-Y!Z)$#addition to translating event file entries it also attempts to localize`a@p$the cause of intermittent disk and tape subsystem failures. Note howeveraq @p"that neither SYSERR nor Spear have anything to do with recording thec@p	!system event file.z	(@p&T)
tops_20_ef_q3_afdA*G-e	+e -
a0@p.That is correct.eQ2@pf	:@p"3Both SYSERR and its' replacement, the SPEAR library, are designed to f!C@p#;process the contents of the system event file. They have nothing to dog)L@p$Dwith recording the entries. That is a strictly function of the operatingh0@p
Pm1oG-z	Q@pTj0V
a[@pWTOPS-20 System Event Files - Q4 of 10ja]@pk9e@p!^True or False - All hardware detected failures are recorded in thekP@p	fsystem event file.tops_20_ef_q5_a @@z	M@pmuEtops_20_ef_q4_atiYqmxr
a{@p!sThe statement is FALSE. Only failures that require operating systemn)@p"|intervention are recorded in the system event file. Failures that doo1
@p#notmrequiremoperatingesystemeinterventioncarernotorecordedninqtheeventp9@p" the recovery is successful then the operating is notrQ&@p#notified. Thus, those kinds of errors are normally not recorded in thesX@p	'system event file.z	.@p+iqktops20efq4afu/G-ua1ux2
a5@p3That's correct.v)7@pvY?@p#8Only errors that require operating system intervention are recorded invp@p@the system event file.|9hG-z	G@phm1xQIG-xyJyL
aQ@pMTOPS-20 System Event Files - Q5 of 10yAS@pz\@p#TTrue or False - Every record in a TOPS-20 system event file consists ofz0@p]a header section and a body section.tops_20_ef_q6_ais 2.z	C@peaH
tops_20_ef_q5_atx9i}k
an@plThat's correct.}1o@p}ax@p$pFurthermore, the header and body section of each entry type is described}y@p"yin a file called DEFINE.LST. To obtain a copy of DEFINE.LST, refer to@pAppendix A on the Event File Menu.z	
@pxQctops_20_ef_q5_afa
G-)
a@p!The statement is TRUE. Each entry in the TOPS-20 system event fileq @p#consists of a header section and a body section. The header identifiesy)@p#!the entry type (i.e., event code), the date and time that the entry was2@p#*recorded, the processor serial number, the length of the header section;@p$3and the length of the body section. Currently, the header section is set!D@p#<at four words, the body section varies in size depending on the type of0@pEentry.
QiG-z	J@pa|96	LG-	)M	@O
aT@pPTOPS-20 System Event Files - Q6 of 10	qV@p
I^@p"WTrue or False - Each record in a TOPS-20 system event file represents
`@pecomplete system event.tops20efq7an Xz	F@pgiftops20efq6atik
au@p$mThetstatementeisrtrueewithhonevexception,0KLERR.eKLERReentriesyarembuilt@p$restarted the entry is transfered via the DTE to KL main memory and thena
@precordedintheBsystem eventufile.qset aside for communications between the consoleY@p#and KL main memory is significantly smaller than a typical KLERR entry,i(@p$ the entry divided into segments. Each segment is given a unique sequencey1@p$)number and recorded as a separate record in the event file. Technically,@p2therefore, the statement is FALSE.z	;@p8	e
tops_20_ef_q6_afi<G-1>H?
aB@p@That's correct.yD@p)M@p$EThe KLERR entry consists of multiple records. Each record has a separateAU@p"Nsequence number. When a KLERR entry is translated, however, only theQ^@p#Vfirst sequence number is used to identify the entry. The other sequenceX@p_numbers are masked-out to avoid confusion. a
G-z	h@pb
Q#ajG-	k m
ar@pnTOPS-20 System Event Files - Q7 of 10Qt@p)|@p"uTrue or False - The synchronization word is used to recover from hard@@p}read errors that occur while reading the system event file.tops_20_ef_q8_aSpot.z	d@p$1tops_20_ef_q7_atI
!(
a@pThat's correct.!Y@p"	@p!Whenever Spear uses the synchronization word to recover from a hard" @p"read error it will print the message "Bad header found - RESYNCing".z	'@p%atops_20_ef_q7_af$1)G-$y*%,
a4@p"-Theestatement islTRUE.The]firstwordineachsystemTeventefile data%A=@p#5blockois aosynchronizationkpointer.sThepointerpointstoethetstarting&IE@p!>locationiof1the'nextrrecord inatheifile.fThus,ifaawhard#readperror'QN@p#Foccursewhileireadingeaerecord Spearnskipsetorthe-next@datablock,treads(YW@p!Othe syncrword, findstthebstartingalocationiofthexnextprecord,and)i[@p	@p a<*09G-0a	0x

a@pTOPS-20 System Event Files - Q8 of 101)@p2@p$True or False - When the TOPS-20 operating system detects a device error2@p
the following occurs:3) @p3i)@p$!1. Normal operation is suspended and applicable hardware and/or software40@p*   status is captured (at error) and saved in a buffer.51@p69@p22. If applicable, an error recovery algorithm is applied.6:@p7C@p";3. Regardless of whether the recovery algorithm is successful or not,7)K@p!D   the applicable hardware and/or software status is captured again81Q@pL   (at end) and appended to the buffer.99R@p:[@p$S4. The contents of the buffer are formatted, assigned a sequence number,:)a@p\   and appended to to the system event file.;9c@p<k@p"d5. If the system was able to recover from the error normal operation<1t@p"l   continues. If, however, the the system was unable to recover from=9|@p!u   the error, then the job effected by the error is notified and it>@@p
}   handles the error.tops_20_ef_q9_aSpot.z	@pGIPtops_20_ef_q8_at0!@p

apThat's correct.A!@pAQ@p The action outlined in the question is typical of the way TOPS-20Ai@p"handles most device errors. Non-device errors (e.g., CPU errors) andBi'@p" errors that affect the operating system itself are also handled in aCq0@p"(similar manner. If, however, there is no recovery algorithm or if theDy8@p"1recovery algorithm is unsuccessful, then those errors may result in aF@p
9user job or system crash.z	A@p>09tops_20_ef_q8_afGIBG-HDH(E
`@p#FThe statement is TRUE. Most TOPS-20 device errors are handled this way.MarG-z	R@p@)
JTG-J)UJ@W
a\@pXTOPS-20 System Event Files - Q9 of 10Jq^@pKIf@p!_True or False - The exact content and format of each TOPS-20 eventK`@pgrecord is described in the Spear Manual.tops_20_ef_q10aSpot.z	N@ppQ@xvtops_20_ef_q9_atIitN(u
a~@p!vThe statement is FALSE. The Spear Manual does describes the reportNY@p!formats generated by Retrieve. But it does not describe the contentO`@pand format of the actual event records.z	@pJn
tops_20_ef_q9_afQAG-R	R 
a@pThat's correct.RQ@pS"@p$The event records are described in a file called DEFINE.LST. To obtain aS*@p#copy of DEFINE.LST refer to Appendix A on the Event File Menu.T),@pU(@p"-P.S. You will need a copy of DEFINE.LST to answer the next question. \YjG-z	8@pk2!?Va:G-W	;W =
aB@p>TOPS-20 System Event Files - Q10 of 10WQD@pX)L@p#ETrue or False - The thirty second word in a 111 type record is used toXAR@pMsave the first channel control word.YIS@pZ!\@p%TNote: Refer to DEFINE.LST. If you do not have a copy of DEFINE.LST and youZ8@p]want one, refer to Appendix A on the Event File Menu.tops_20_ef_lq0_ upz	4@pggyptops_20_ef_q10_atVIk] m
av@p#nThe statement is FALSE. Open the DEFINE.LST to the 111 entry. It starts]Q~@p#wsome place around line number 01320. The line number are listed at the^a@pleft of the page._i@p`!
@p!Nowrskipping overmtheuword,ybyte,tand bitddefinitions,TgotdownAthe`9@p#will see that word number 32 is defined as RETRYCNT. To thebI&@p#right you will see that the RETRYCNT is saved in bit 18 thru 35 of thecQ-@p'word and it is described as "final retry error count".da.@peQ7@p"/Now find word number 28. You will see that it is defined as CCW1, iteh@p#8consists of 36 bits, and it is described as "first chan control word".z	D@pAVaetops20efq10afgyEG-hAGhXH
aK@pIThat's correct.i	M@pi9V@p$NWord 32 is used to save the error retry count. The first channel controliQ_@p$Wword is saved in word 28. Anytime you want to know exactly what hardwarejah@p$`and software status is saved in an entry type you can consult DEFINE.LSTkqi@pmr@p$jNow, if you haven't already done so, take a few minutes to look over them{@p$scontents of the file. The introduction explains the overall organizationn)@p#|and format of an event file record. Following the introduction, each ofo9
@pthe event types are described in detail.pI@pq!@p#
When you are finished, take a few more minutes and compare the reportsq9@p"listed in the Spear Manual with the corresponding record descriptionsrA%@p#listed in DEFINE.LST. As a result, you will have a better understandingsH@p"&of the system event file and the reports that are generated from it.vax_vms_ef Hz	2@pc0Auy3G-v!5v86
a?@p$7That's it. There are only 10 questions about TOPS-20 System Event Files.vh@p@Press the RETURN key to return to the System Event File Menu.z	K@pIPfvax_vms_efxxyMG-y9NyPP
aY@p#QThe VAX/VMS Event file section of Instruct was not complete in time forzb@p$Zthis Field Test version of Spear. When it is complete it will consist of{k@p#ca series of questions about the VAX/VMS system event file (ERRLOG.SYS).|!t@p$lThe questions will be based on the information contained  in the VAX/VMS}1x@p
uversion Spear Manual.~Ay@p@p#zSince the purpose of the questions is to ensure that you understand the@p#format and content of the VAX/VMS system event file, you can review the)@p#
information in the VAX/VMS Spear Manual. Then later, when this section9@pis complete, you can come back and try to answer the questions.A@pA&@p"P.S. If you're not running Spear on a VAX/VMS system then chances areY-@p'     the VAX/VMS version of Spear has not been released yet.a/@pX@p 0Press the BACKSPACE key to return to the System Event File Menu.VAX/VMS Q1z	:@p-i<G-)=@?
aH@p#@You do not need to understand file structures to use System Event FilesqQ@p$Ito isolate system failures. However, in order to be effective you should	Z@p#Runderstand something about their format and content. Chapter (?) of the
c@p#[VAX/VMS Spear Manual describes the overall format and content of system!l@p$devent files. Appendix (?) of the Manual describes in detail, the content
1t@p#mofIeachptyperecordsthatoyoufwilltfind innaiVAX/VMSaSystemsEventeFile.and specifica@p#questions about the VAX/VMS System Event File (ERRLOG.SYS). Before youi@p%attempt to answer the questions you should review Chapter (?) and Appendixq@p%(?) in the Spear Manual. (Don't forget, you can use the /BREAK feature and@preturn via your student ID.)QIG-z	#@p!Yvaxvmsefaq$G-1&H'
`@p(Press the RETURN key when you are ready.z	1@p/[!
vax_vms_ef_q1Q2G-4(5
a;@p6Q1 of 10 (VAX/VMS System Event Files)Y<@p1@@p=True or False - IA@p@pQvax_vms_ef_q2_aare:z	@pG)evax_vms_ef_q1_atYKL
aN@p6IO@p`@pPThat's correct.z	W@pTVyEvax_vms_ef_q1_af)XG-qZ[
a^@p\VAX/VMS Q19_@p`@p
`The statement is TRUE9G-z	g@pBQ
QiG-yjl
aq@pmQ2 of 10 (VAX/VMS System Event Files)As@pv@ptTrue or False - 1x@ph@p`vax_vms_ef_q3_afile.z	c@p}!1vax_vms_ef_q2_at9 
a@pVAX/VMS Q2a1@p-X@pThestatementisFALSEz	@p
a@pVAX/VMS Q2"A@p"h@pThat's correct.&17G-z	@py9A
#I G-#q"$#
a)@p$Q3 of 10 (VAX/VMS System Event Files)$9*@p%.@p+True or False - %)/@p%`@pvax_vms_ef_q4_a- z	@p5(Tvax_vms_ef_q3_at#19&x:
a=@p;VAX/VMS Q3')>@p'P@p?That's correct.z	F@pC#I3vax_vms_ef_q3_af(GG-(aI(xJ
aM@pKVAX/VMS Q3))N@p)P@p
OThe statement is TRUE-)oG-z	V@p0&1y
*AXG-*iY+[
a`@p\Q4 of 10 (VAX/VMS System Event Files)+1b@p,	e@pcTrue or False - ,!g@p,X@pvax_vms_ef_q5_a4z	R@pl/vax_vms_ef_q4_at*)p-pr
at@psVAX/VMS Q4.!v@p.H@pwThat's correct.z	}@p{*Ajvax_vms_ef_q4_af/G-/Y/p
a@pVAX/VMS Q40!@p0H@p
The statement is TRUE4!&G-z	@ph-)0
19G-1a1x
a@pQ5 of 10 (VAX/VMS System Event Files)2)@p3@pTrue or False - 3@p3P@pvax_vms_ef_q6_a;z	
@p$6	Cvax_vms_ef_q5_at1!(4h)
a,@p*VAX/VMS Q55-@p5@@p.That's correct.z	5@p219"vax_vms_ef_q5_af6	6G-6Q86h9
a<@p:VAX/VMS Q57=@p7@@p
>The statement is TRUE;^G-z	E@p4!i
81GG-8YH8pJ
aO@pKQ6 of 10 (VAX/VMS System Event Files)9!Q@p9yT@pRTrue or False - :V@p:H@p"vax_vms_ef_q7_aBz	A@p[=zvax_vms_ef_q6_at8_;`a
ac@pbVAX/VMS Q6<e@p<8@pfThe statement is FALSEz	m@pk81Yvax_vms_ef_q6_af=oG-=Yp=pr
at@psVAX/VMS Q6>!v@p>H@pwThat's correct.BG-z	}@pW;
?)~G-?Q?h
a@pQ7 of 10 (VAX/VMS System Event Files)@@p@q
@p	TrueorpFalse-vA	fq8aIz	y@pCy2vaxvmsefq7at?BX
a@pVAX/VMS Q7C	@pC0@pThat's correct.z	$@p!?)vax_vms_ef_q7_afCy%G-DA'DX(
a+@p)VAX/VMS Q7E	,@pE0@p
-The statement is TRUEI	MG-z	4@pBX
F!6G-FI7F`9
a>@p:Q8of10z(VAX/VMSSystemEventFiles)G@@pGiC@pATrueorFalse - HE@pH8@p
aR@pQVAX/VMS Q8JT@pJ(@pUThe statement is FALSEz	\@pZF!Hvax_vms_ef_q8_afK^G-KI_K`a
ac@pbVAX/VMS Q8Le@pL8@pfThat's correct.PG-z	l@pFI	
MmG-MAoMXp
av@pqQ9 of 10 (VAX/VMS System Event Files)N	w@pNa{@pxTrue or False - Ny|@pO0@psvax_vms_ef_q10aVpz	h@pQiGvax_vms_ef_q9_atMPH
a
@pVAX/VMS Q9Py@pQ @p
That's correct.z	@pMvax_vms_ef_q9_afQiG-R1RH
a@pVAX/VMS Q9Ry@pS @p
The statement is TRUEVy<G-z	#@p}QF
T%G-T9&TP(
a-@p)Q10 of 10 (VAX/VMS System Event Files)U/@pUY2@p0True or False - Uq4@pV(@p
8vax_vms_ef_lq0_r0z	@p9XiRvax_vms_ef_q10_atSy=W@?
aB@p@VAX/VMS Q10WqC@pX @pDThat's correct.z	K@pHT7vax_vms_ef_q10_afXiLG-Y1NYHO
aR@pPVAX/VMS Q10YyT@pZ(@p
UThe statement is TRUE^tG-z	\@p5q-[]G-[A_[X`
ai@p$aThat's it. There are only 10 questions about VAX/VMS System Event Files.\@pjPress the RETURN key to get back to the System Event File Menu.z	X@p
251i$[u^@w
a|@px                       Spear Library^q~@p_I@pIntroduction_a@p`@p#Spear is an on-line maintenance software library that runs under three`)@p$
operating systems: TOPS-10, TOPS-20, and VAX/VMS. Currently, the librarya1@p!contains four functions: Summarize, Analyze, Retrieve, and Compute.bA@pcI'@p$The first three functions; Summarize, Analyze and Retrieve, are designedca/@p"(to help you sort and evaluate  32- and 36-bit system event files. Thedq8@p#0third function, Compute, calculates system availability. Its purpose iseyA@p!9to help you prepare crash and up time reports and determine overallg	D@p	Bsystem performance.hF@phIO@p#GIn the future we plan to expand the library to include a Watch functionhaX@p#Pand a Purge function. The Watch function will enable you to monitor on-iq`@p#Yline system event recording as it takes place. The Purge function willk@pahelp you maintain the size and content of system event files.failures.2z	m@pk^^
3.0.A.mnG-mQpmhq
az@p$rEach Spear Library functions supports a dialog style user interface. Then@p#{dialog prompts for information and waits for a response. If the prompto)@p"excepts a default, the default will be (parenthetically) included asp1@p	
part3oftheprompt.q8@pz	2@p
R.T.3.0.rev_trans_sl_intror9G-ss(
a&@p#STOP - You are moving in a reverse direction through the menu. You aresY,@p'about to back into the Spear Library Introduction.ta.@puH@p
/Your response please:r	3G-v!5v86
a<@p7                        Spear Libraryvi=@pwA@@p>Topic Menu:wYB@px	E@pC  0. Introductionx!G@pxYJ@pH  1. AnalyzexqK@py!N@pL  2. Retrievey9P@pyiS@pQ  3. ComputezT@pz1W@pU  4. SummarizezIY@pzy\@pZ  5. Applications{@pz	a@p`m =3.1.0.{acG-|d|0f
ak@pg                Spear Library - Analyze|am@p}9p@pnIntroduction}Qq@p~z@p$rAnalyze is designed to help you isolate the cause of intermittent system~ @p#{failures. It reads and sorts the records contained in the local system) @p# event file: ERROR.SYS (for TOPS-10/20) or ERRLOG.SYS (for VAX/VMS). As1 @p# 
each record is read it is sorted according to subsystem and error type.9 @pI @p$ Then, by applying a set of fixed theories, Analyze attempt to relate thea (@p$  error symptoms to the failing component within the subsystem. The resultq 1@p# )is a set of numbered reports. The reports identify failing subsystems,  9@p# 2state a possible cause, and list the major error symptoms that seem to@p :support the statement.z	 A@p ?{a d3.1.0.A.Y BG- D( E
a N@p# FAnalyze also produces a packet file. The packet file contains a set ofY V@p" Onumbered packets that correspond to the numbered reports. The packets	a _@p" Wcontain the sequence numbers of the event file records that were used
h@p `as evidence to support the report. z	 g@p fY!H3.1.0.B.
A iG-
yj
a t@p" mRetrievessupportsepacketttranslation. Thus,Sifryourquestionranreport,H@p$ ~manually evaluate the evidence (records), and draw your own conclusions.z	!$@p!(S3.1.M.ntrofPz	!@p!
r9&5R.T.3.1.0.B.rev_trans_analyze_intro_b!!G-	! !
a!@p#!STOP - You are moving in a reverse direction through the menu. You areP@p!about to back into the the Introduction to Analyze.a!&G-I!'`!)
a!.@p!*                 Spear Library - Analyze!0@pi!3@p!1Topic Menu:!4@p1!8@p!5 0. IntroductionI!9@p!=@p	!: 1. Analyze Dialog!>@pQ!B@p
!? 2. Theories Descriptionsi!D@p(@p!E 3. Questions & Answersz	!K@p!J
A3c$3.1.1.!MG-9!NP!P
a!X@p"!QAnalyze Dialog - The Analyze dialog is straight forward. It consists!a@p!!Yof six prompts: five selection prompts and one confirmation prompt.	!b@p!d@p)!g@p!eAnalyze modeA!j@p!h------------q!k@p!!p@p!l    Event file (SYSTEM:ERROR.SYS):9!r@p	!u@p	!s    Time from (-1):!!w@pY!{@p
!x    Time to (LATEST):q!|@p1"@p!}    Report to (DSK:Ammdd.RPT):I"@p "@p"    Packets to (DSK:Ammdd.PAK): )"	@p x@p
Type <cr> to confirm (/GO):z	"@p"<1"}*3.1.1.A.!Y"G-"""("
a"@p"Y"@pon prompt:"q"@p#9""@p"     Event file (SYSTEM:ERROR.SYS):#Q"#@p$!",@p""$allows you to specify the name of the system event file that you want$9"4@p "-analyzed. The default response (SYSTEM:ERROR.SYS) is enclosed in%A"<@p!"5parentheses and can be selected by pressing the RETURN key. You can&A"E@p#"=override the entire default response by specifying a new file name. You'I"N@p""Fcan also override any field in the default response by specifying the(Y"S@p"Oonly field that you want to override.)a"U@p*9"Z@p"VFor example, if you were to type:*Q"[@p+!"b@p"\        Event file (SYSTEM:ERROR.SYS): .LWK<cr>+9"c@p,!"k@p"dthe input file specification would become SYSTEM:ERROR.LWK,9"l@p-1"n@p-I"w@p#"oThe prompt also supports standard Help and question mark (?) responses.-`@p"xWould you like to review the Help message ?z	#@p"!Y#W3.1.1.B./Q#G-0	#0 #
a#	@p#The second selection prompt:0Q#@p1#@p
#
     Time from (-1):11#@p1i#@p"#allows you to specify the time at which to begin analyzing the system2#!@p"#event file. The default response (-1) is inclosed in parentheses and3	#)@p"#"refers to yesterday at 00:00:01 hours. It can be selected by pressing4#2@p##*the RETURN key. In addition to relative time (-dd), the prompt accepts5#;@p##3real time(dd-mmm-yy hh:mm:ss), and the expression EARLIEST. If you type6!#D@p##<Earliest, the analysis will begin with the earliest (or first) entry in71#G@p#Ethe event file.8A#H@p8q#Q@p##IThe prompt also supports standard Help and question mark (?) responses.9@p#RWould you like to review the Help message ?z	#[@p#Y/Q$3.1.1.C.:y#\G-;1#^;H#_
a#d@pe third selection prompt:;y#e@p<A#i@p#f     Time to (LATEST):<Y#k@p=#s@p"#lallows you to specify the time at which you want the analysis to end.=1#|@p!#tThe default response (LATEST) is enclosed in parentheses and can be>9$@p"#}selected by pressing the RETURN key. Again, you can also specify real?A$@p	$and relative time.@I$	@pA$@p#$
The prompt also supports standard Help and question mark (?) responses.A@p$Would you like to review the Help message ?z	$@p$:y%
(3.1.1.D.C	$G-CA$CX$ 
a$%@p$!The fourth selection prompt:D	$&@pDQ$+@p$'    Report to (DSK:Ammdd.RPT):Di$,@pE1$5@p"$-allows you to specify the name of the output Report file. The defaultEI$>@p#$6response (DSK:Ammdd.RPT) is enclosed in parentheses and can be selectedFQ$F@p#$?by the pressing RETURN key. (The expression mmdd refers to the currentGa$O@p$$Gmonth and day respectively.) You can replace the entire default responseHi$X@p"$Pby specifying a new file name. You can also replace any field in theIy$a@p$$Ydefault response by specifying only the field that you want to override.K$b@pL$k@p!$cFor example, if todays date was December 25th and you were to type:L)$l@pM1$r@p$m    Report to (DSK:Ammdd.RPT): FS:<cr>MI$s@pN!$z@p$tthe output file specification would become FS:A1225.RPTN9$|@pO)$}@pOA%@p#$~The prompt also supports standard Help and question mark (?) responses.OX@p%Would you like to review the Help message ?z	%@p%C	%p$3.1.1.E.QI%G-R%R%
a%@p%The fifth and final selection prompt:RI%@pS!% @p%     Report to (DSK:Ammdd.PAK):S9%"@pT	%*@p %#allows you to specify the name of the output Packet file. Again:T!%+@pU!%4@p#%,1. The default response (DSK:Ammdd.PAK) is enclosed in parentheses andU9%:@p%5    can be selected by pressing the RETURN key.VA%<@pW)%E@p$%=2. The expression mmdd refers to the current month and day respectively.WA%F@pXQ%O@p#%G3. You can replace the entire default response by specifying a new fileXi%W@p %P   name, or you can replace any field in the default response byYy%^@p%X   specifying only the field that you want to override.Zy%`@p[i%a@p\%j@p#%bThe prompt also supports standard Help and question mark (?) responses.\@p%kWould you like to review the Help message ?z	%t@p%rQI9)3.1.1.F.^	%uG-^A%w^X%x
a%|@p
%yThe&confirmation prompt:t	%~@peI&@p%ge anTypes<cr>etoconfirm(/GO):na&@p`1&point. If you want to review the response listaQ&@p &type /SHOW. If you are satisfied with the response list press thebQ&!@p&RETURN key or type /GO.cQ&"@pd&+@p!&#If you want to change a response, press the BACKSPACE key until youd(@p#&,arrive at the corresponding prompt, make the change, and then type /GO.anadiaq1mpz	&9@p&7!;OR.T.3.1.1.F.fY&;G-g&<g0&>
a&F@p#&?STOP - You are moving in a reverse direction through the menu. You areg`@p&Gabout to back into the Analyze Dialog explanation.z	&O@p&3@3
iQ&QG-iy&Rj&T
a&X@p
&UAnalyze Dialog - Q1 of 10jA&Y@pk&b@p!&ZTrue or False - Analyze attempts to isolate (or localize) the causek&j@p"&cof intermittent Mainframe, Disk, Tape, Unit-record, and Communicationl @p	&ksubsystem failures.ana_dia_q2Pz	&s@p&qy'ana_dia_q1_atmy&uG-n9&vnP&x
a'@p"&yThe statement if FALSE. This version Analyze only attempts to isolateo'@p'(or localize) the cause of intermittent Disk and Tape subsystemp	'
@p'	failures. Specifically:q	'@pqI'@p'   RH10, RH11, and RH20 Massbus controllers connected toqa'@p'   RP04, RP05, RP06, or RM03 Disk drives.rY'@p3s9'$@p'   RH10, RH11, and RH20 Massbus controllers connected tosQ'*@p'%   TU45 or TU77 Tape drives thru a TM02/03.tI',@pu)'2@p'-   RH11 and RH20 Massbus controllers connected touA':@p'3   TU70, TU71, TU72, or TU73 Tape drives thru a DX20 - TX01/02.v)'<@pw)'A@p'=   DX10 Channel Bus Adapter connected tow@@p'B   TU70, TU71, TU72, or TU73 Tape drives thru a TX01/02.z	'M@p'K31&oana_dia_q1_afy'NG-yQ'Pyh'Q
a'T@p'RThat's correct.z'V@pzI'^@p!'WThe main thrust behind Analyze is to attempt to isolate or at leastza'g@p"'_localize the cause of intermittent Disk and Tape subsystem failures. {i'o@p"'hIn the future, however, we do plan to add Mainframe, Unit-record, and|q'x@p"'pCommunication subsystem failure analysis. But for now, those types of}x@p'yfailures are only summarized in the Analyze report.z	(@p&mmy({q(G-(0(
a(
@p
(Analyze Dialog - Q2 of 10a(@p!(@p!(
True or False - Analyze is capable of isolating the exact cause of8@p(intermittent Disk and Tape subsystem failures 100% of the time.ana_dia_q3Xz	(!@p(1)1ana_dia_q2_atY(#G-($0(&
a(.@p"('The statement is FALSE. Analyze is NOT capable of isolating the exacta(7@p$(/cause of intermittent Disk and Tape subsystem failures 100% of the time.i(@@p"(8In many cases the ability of Analyze to isolate the exact cause of any(I@p#(Aintermittent failure is limited because of hardware partitioning, event(Q@p"(Jfile content-restrictions, and the complex nature of certain types of	(S@ph
(T@p
1(]@p"(UIn such cases, the capability of Analyze is limited to localizing the
I(e@p"(^cause of an intermittent failure to a general area of logic. Once theQ(n@p"(fcause of an intermittent failure has been localized, however, you can
Y(w@p#(ouse a module (or component) substitution technique to isolate the exact
(xcause of the failure.z	(@p(}q(ana_dia_q2_af1)G-q))
a)@p)That's correct.9)@pi)@p")	The statement is FALSE. Analyze is NOT capable of isolating the exact)@p$)cause of intermittent Disk and Tape subsystem failures 100% of the time.	)"@p#)It is, however, pretty good at localizing the cause failures to general)+@p#)#areas of logic. Thus, in many cases, you can use substitution technique(@p),to complete the isolation process.follow:_q9z	)4@p(Y*
)5G-A)7X)8
a)<@p
)9Analyze Dialog - Q3 of 10	)>@pI)G@p$)?True or False - The packet numbers listed in the Analyze report refer toa)O@p#)Ha set pointers that identify the records that were used as evidence top@p)Psupport the corresponding theories.ana_dia_q45pz	)Z@p)X 9+
ana_dia_q3_ata)[G-!)]8)^
a)a@p)_That's correct.i)c@p)k@p#)dThe packets are saved in a Packet file. You can submit the Packet file1)t@p")lto Retrieve and select one or more packets for translation. Thus, you9)|@p")ucan examine individual packets and decide whether or not the evidence@@p)}(i.e., the records) does in fact, support the theory.z	*@p*)V,ana_dia_q3_af 9*	G- y*
!*

a*@p#*toissTRUE. Next time youeruneAnalyzestakera minuteeandetype!A*@p#*orhprintmthesPacketoFiles(Ammdd.PAK). It willPlooktsomethinglikethis:"Q*@p#a*'@p*PAKWRTV1.0		!Versionnumber of packet file writer (PAKWRT)#y*,@p*(SYSTEM:ERROR.SYS	! Name of file analyzed$q*4@p*-11734493336		! Packet file creation date in universal format%I*;@p*5****1			! Packet number corresponding to first theory &A*@@p*<3			! Number of records used by theory'1*F@p*A978			! Sequence number of first record(	*L@p*G1171			! Sequence number of second record(a*R@p*M1184			! Sequence number of third and last record)A*Y@p*S****2			! Packet number corresponding to second theory*)*@p*Z11			! Number of records used by the theory+*e@p*`1023			! Sequence number of first record+y*k@p*f1054			! Sequence number of second record,Q*p@p*l1165			! Sequence number of next record-1*s@p*q1226			! etc..	*u@p.9*}@p!*vThe packet numbers correspond to individual theories listed in the.Q+@p!*~Analyze report and the sequence numbers identify (or point to) the/Y+
a+ @p
+Analyze Dialog - Q4 of 103I+"@p4	++@p#+#True or False - Retrieve can Translate packets contained in the Analyze4 @p+,packet file.ana_dia_q5Lhz	+3@p+1=i,Lana_dia_q4_at5y+5G-69+66P+8
a+;@p+9That's Correct.7+<@p71+E@p!+=However, if you specify multiple packet numbers, you should realize7I+M@p!+Fthat Retrieve will NOT translate the records in the order that they8Q+V@p"+Nappear in the packets. Instead, the records will be translated in the9Y+^@p"+Worder that they appear in the event file. In other words, the record:a+f@p +_with the lowest sequence number will be translated first and the;h@p +grecord with the highest sequence number will be translated last.z	+r@p+p2Y+/ana_dia_q4_af=i+tG->)+u>@+w
a+@p!+xThe statement is TRUE. Retrieve can Translate packets. Thus, if you>q,@p#,decide that you want to examine the records that were used as evidence?y,@p,	to support a specific theory you can do so using Retrieve.A,@pAy,@p$,The following prompt/response illustrates how to translate a packet. TheB,#@p$,dialog directs Retrieve to translate the records in packet 4 and displayC!,(@p,$the result (in Full format) on the TTY.D1,*@pE	,2@p,+       Event of packet file (SYSTEM:ERROR.SYS): Ammdd.PAK<cr>E!,6@p,3       Packet numbers: 4<cr>F!,;@p,7       Output mode (ASCII): <cr>Fi,A@p,<         Report format (SHORT): FULL<cr>G9,G@p,B       Output to (DSK:RETRIE.TXT): TTY:<cr>H@p,H       Type <cr> to confirm (/GO): <cr>z	,O@p+-5y-/II,PG-Iq,RJ,S
a,W@p
,TAnalyze Dialog - Q5 of 10J9,Y@pJy,a@p",ZTrue or False - Analyze will accept and process a binary history fileK@p,bgenerated by Retrieve.ana_dia_q6^xz	,k@p,iUy-Oana_dia_q5_atLq,lG-M1,nMH,o
a,s@p,pThatrislcorrect.wMy,t@pN1,}@p#,uAnalyzelwilllacceptandPprocessaany standard2binaryosystem eventzfile.NI-@p,~There-is,Vhowever,oonefgeneralrestriction:OQ-@pP1-q5afUy-5G-V9-6VP-8
a-@@p!-9The statement is TRUE. In fact, Analyze will accept and process anyW-I@p"-Astandard binary event file. That includes special purpose event filesX@p-J(or history files) generated by Retrieve.z	-Q@p,eLq-xYq-SG-Z-TZ0-V
a-Z@p
-WAnalyzeeDialogy-aQ60of010Za-[@p[!-d@p#-\Multiple.Choice - If, in response to the "Time from (-1):" prompt, you[9-k@p-epress the RETURN key: which time will Analyze use ?\A-l@p]1-p@p-m   1. Today at 00:00:01]I-r@p^@p
ana_dia_q6_a1_-}G-_A-_X.
a.	@p#.That may seem reasonable, however, when dealing with relative time the`	.@p$.
number following the minus sign is subtracted from the current date (thea.@p".time defaults to 00:00:01) and the result becomes the time parameter.b!.#@p$.Therefore, if you press the RETURN key in response to the Time from (-1)c).,@p#.$the time will default to yesterday at 00:00:01. If you were to specifyd8@p!.-minus zero (-0), then the time would default to today at 00:00:01.z	.8@p.6_.Qana_dia_q6_a2fI.:G-g	.;g .=
a.@@p.>That's correct.gQ.A@ph.J@p$.BRelative time is measures in whole days. Since today won't be over untilh@p.Ktomorrow, the correct answer is yesterday at 00:00:01.z	.T@p-vfI/qj.UG-jA.WjX.X
a.\@p
.YAnalyze Dialog - Q7 of 10k	.^@pkI.f@p"._True or False - Analyze can be run automatically every midnight via ak`@p	.gBatch control file.ana_dia_q8@z	.o@p.m~0&ana_dia_q7_atm9.qG-my.rn.t
a.w@p.uThat's correct.nA.x@pnq/@p#.yIn fact, during load test, most of the Account Reps used the followingo	/
@p#/(resubmitting) Batch Control File to ensure that Analyze was run daily.p/@pq!/@p"/
@SUBMITPSPEAR	/TIME:30u/AFTER:TODAY!9ResubmitSPEARNagainOtomorrow.q9/@p/@RENAMEr*.RPT*.RPO		@p:!@Rename/yesterdays.reportOfile.rA/F@p  ! Print two copies of the report:v!/C@p$/;@PRINT A*.RPT /NOTE:"SPEAR - OPER"  ! one for FS and one for Operations.w)/E@px9/M@p#/FThe daily report was used monitor the overall performance of a system.xQ/V@p#/NThen, just before the scheduled maintenance period, a weekly report wasyY/@p#/Wgenerated. The weekly report was used to help determine the maintenancezi/h@p#/`strategy for the period. (i.e., what, if any, modules should be swapped{x@p$/ior substituted in an effort to isolate the cause of intermittent faults)z	/u@p/sj.kanadiaq7af~/wG-~Y/x~p/z
a0@p$/{The statement is TRUE. In fact, any one of the Spear Library maintenance!0@p"0functions (Analyze, Retrieve, Summarize, or Compute) can be run daily0@p
via a Batch control file. z	0@p.im90J0G-)0@0
a0@p
0Analyze Dialog - Q8 of 10q0@p10%@p!0True or False - Both the "Time from" and the "Time to" prompt willH@p0&accept either real time or relative time.ana_dia_q90z	00@p0.	)1ana_dia_q8_atI02G-	03 05
a08@p06That's correct. Q0:@p	0B@p"0;All Spear Library "time" prompts accept real time and relative time. @p 0CThey also accept "EARLIEST" and "LATEST" as time specifications.z	0N@p0L0,ana_dia_q8_af	)0PG-	i0Q
0S
a0[@p"0TThe statement is TRUE. Both the "Time from" and the "Time to" prompt
10b@p0\will accept either real time or relative time.90c@p
!0l@p!0dThe format for specifying real time is: dd-mmm-yy hh:mm:ss. Where:
90m@p
0npddrepresentsethesday,he first three letter of the month,0@p0y  yy represents the last two digits of the year, and	1@p1  hh:mm:ss represent the hour, minute and second respectively.y1	@py1
@p1@p1The format for specifying relative time is: -dd. Where:)1@p1@p$1  dd is a numerical value that refers to some number of whole past days.0@pjz	1 @p0*I2 Y1!G-1#1$
a1(@p
1%Analyze Dialog - Q9 of 10I1*@p@p 1+True or False - Analyze does NOT accept indirect response files.3.1.1.1.q1QXz	17@p15$Jy ana_dia_q9_at919G-y1:1<
a1E@p#1=The statement is FALSE. All Spear Library Functions (including Analyze)A1J@p1Faccept indirect response files.Q1K@p!1T@p#1LAn indirect response file is simply an ASCII text file that contains a91]@p#1Ulist of Spear Library responses. Almost any text editing program can beA1e@p#1^used to build an indirect file. There are only two rules that you mustQ1g@p)0Y1h@pq1q@p#1i 1. The responses in the file must pertain to one Spear function only.	1r@p1{@p#1s 2. The responses must be in the correct order and conclude with a /GO.)1}@p92@p#1~If you omit any responses (or the /GO switch), you will be prompted forQ2@p$2all missing responses. This feature can be used to build special purpose a2@p$2response files that only prompt for specific items. For example, you can!p@p 2build a response file that will only prompt for time parameters.z	2$@p2"Y13&ana_dia_q9_af$2%G-$A2'$X2(
a2+@p2)That's correct.%	2-@p%925@p 2.The following indirect response file (SPRLWK.CMD) can be used to%Q2=@p!26automatically analyze the last 7 days of information in the system&Q2F@p!2>event file ERROR.SYS. Comments can be included in indirect response'Y2N@p2Gfiles but they must be preceded with an exclamation point (!).(a2O@p)a2S@p
2PANALYZE				!KFunction)y2X@p2TSYSTEM:ERROR.SYS		!	Eventcfile*92[@p2Y-7				!OTime!from+2c@p	2\LATEST				!-Time@to+92c@pw@p!2pThe indirect response file can only be submitted at the main Spear-q2}@p2xprompt and must be preceded with a @ sign..y2@p/X@p3  Example:   SPEAR> @SPRLWK.CMD<cr>z	3@p3iQ35anadiaq100A3	G-1313

a3@p Dialog - Q10 of 101I3@p2@p"3True or False - The entire Analyze dialog can be entered on one line.z	3@p36Y'Ianadiaq10at313 G-3q3"43#
a3&@p3$That's correct.493(@p4i30@p!3)Using the ESCAPE key and Control W (^W) you can complete the entire5@p31Analyze dialog without prompting. z	39@p370A3
ana_dia_q10_af6Y3;G-73<703>
a3G@p#3?ThestatementisTRUE.Onceyoubecome familiar with the Analyze dialog7a3P@p$3Hyou will be able to use the ESCAPE key and the Control W (^W) feature to8q3Y@p#3Qenter your responses. The ESCAPE key will display each default response:3`@p3Zin order. The ^W allows you to alter the default response. ;@pPACKET 3..z	3e@p11"
a3s@p$3kThat's it. If you have gotten this far, then chances are you have a good= @p3thandle on the Analyze dialog.Qa5G-z	3}@p3{r	8*ANALYZE INPUT?3~G-?Q4?h4
a4@p4Analyze Help Message: Event File Prompt@4@p@q4@p4	     System Event File ___.   .----------.   .___ Report FileA	4@p4                          !   !  Event   !   !B	4@p4            Retrieve      !---!  File    !---!Bq4%@p4         (binary) File ___!   ! Analysis !   !___ Packet FileCY4+@p4&                              !__________!DY4-@pE944@p4.          INPUT                 PROCESS             OUTPUTEQ46@pFI4>@p#47Analyze reads the specified event file, sorts the records according toFa4G@p#4?a set of (best guess) theories, and then, produces a report file and aGi4O@p#4Hpacket file.  The report file summarizes the theories and presents theHq4X@p#4Pmajor supporting evidence.  The packet file contains a set of pointersIy4_@p4Yto the individual records that support each theory.K4`@pKq4i@p"4aAt this prompt Analyze is waiting for you to specify the name of theL	4q@p!4jinput file. You can specify any binary system event file you want,M4z@p"4rincluding a binary file produced by Retrieve.  The file specificationN5@p$4{format is: dev:<user>file.extension.version. Press the RETURN key if youO @p$5want to default to the local system event file (ERROR.SYS or ERRLOG.SYS)ANALYZE TIME TOc@z	3w@p	5s	6*ANALYZE TIME FROM >y5R(5
a5@p5Analyze Help Message: Time From PromptRY5@pS15#@p5                        Time From:           Time To:SI5+@p5$                 ***********!oooooooooooooooooooo!************T952@p5,                        02-Mar-81            09-Mar-81U959@p53                        18:30:45             23:30:01V)5;@pW5C@p#5<You can use the "Time From:" and the "Time To:" prompts to specify theW15L@p"5Dperiod during which you want the event file analyzed. At this promptX95T@p"5MAnalyze is waiting for you to specify the time at which you want theYA5Y@p5Ufile analysis to begin. You can:ZI5[@p[5d@p$5\ 1. Press the RETURN key to default to -1 (yesterday at 00:00:01 hours).[15e@p\A5n@p#5f 2. Enter real time. The format is: dd-mmm-yy hh:mm:ss  where dd is the\Y5w@p"5o    numerical day, mmm is the first three letters of the month, yy is]i6@p#5x    the year, hh is the hour, mm the minute, and ss the second. If only^q6	@p#6    the date is specified, the default time is 1 second after midnight.`6
@pa6@p#6 3. Enter relative time. The format is: -dd  where -dd is the number ofa(@p6    past days. To indicate today at 00:00:01 hours, type: -03.1.2.0.PA9hz	6@p5Q`GS&cI6 G-cq6"d6#
a6)@p6$Analyze Help Message: Time To Promptd96*@pe61@p6+                      Time From:           Time To:e)69@p62               ***********!oooooooooooooooooooo!***********f6@@p6:                      02-Mar-81            09-Mar-81g6G@p6A                      18:30:45             23:30:01h6H@phq6Q@p#6IAt this prompt Analyze is waiting for you to specify the time at whichi	6W@p6Ryou want the file analysis to end. You can:j6X@pjq6a@p"6Y  1. Press the RETURN key to default to the LATEST time in the file.k	6b@pl6k@p#6c  2. Enter real time. The format is: dd-mmm-yy hh:mm:ss where dd is thel)6t@p#6l     numerical day, mmm is the first three letters of the month, yy ism96}@p$6u     the year, hh is the hour, mm the minute, and ss the second. If onlynA7@p$6~     the date is specified, the default time is 1 second after midnight.oQ7@ppa7@p$7  3. Enter relative time. The format is: -dd  where -dd is the number ofpx@p7     past days. To indicate today at 00:00:01 hours, type: -0z	7@p715&ANALYZE REPORTs	7G-sI7s`7!
a7&@p7"Analyze Help Message: Report To Promptt7(@pti71@p#7)The Big Picture is still: Input - Process - Output.   Remember, Analyzeu7:@p#72is designed to sort and classify the information contained in the localv7B@p#7;system event file.  The result is a report file and a packet file.  Atw!7K@p#7Cthis prompt Analyze is waiting for you to specify a destination for thex)7O@p
7Lreport file. You can:y97Q@pyy7Y@p!7R 1. Press the RETURN key to select the default file specification:z7b@p#7Z    DSK:Ammdd.RPT. Where mmdd corresponds to the current month and day.{7d@p|)7l@p"7e 2. Enter your own unique file specification (e.g., DSK:WEEKLY.RPT).|A7u@p#7m    The file specification format is: dev:<user>file.extension.version.}I7w@p~Y8@p$7x 3. Type TTY: in which case the report will be printed on your terminal.~q8@p!8    Understand that if you specify TTY: the file will not be saved.8
@p	8@p"8NOTE: If you save the file, you can use any text editor to review the @p"8report. Of course, you can also print or type the report as you wish.z	8@p8?7*ANALYZE PACKETS18 G-q8"8#
a8)@p8$Analyze Help Message: Packets To Prompt98*@p83@p$8+There is a packet associated with each theory listed in the report file.)8<@p$84The packets are numbered and contain pointers to those records that were98E@p#8=used as evidence to support the theories.  After the file is analyzed,I8M@p#8Fthe packets are put in a common packet file along with the name of theQ8V@p"8Nfile that was analyzed.  At this prompt Analyze is waiting for you to	Y8]@p8Wspecify a destination for the packet file. You can: 
a8^@pQ8g@p!8_ 1. Press the RETURN key to select the default file specification:i8p@p#8h    DSK:Ammdd.PAK. Where mmdd corresponds to the current month and day.
q8q@p8z@p"8rn2.cEnterhyouroownouniquenfileespecifications(e.g.,DSK:WEEKLY.PAK).9@p#8{9@ThefileNspecificationhformatois:vdev:<user>file.extension.version.!9@p199to translate the records listed in the packets. This should be done any@p9"time you question a theory or the evidence that supports it.z	9+@p6^	;,9-G-99.P90
a95@p91           Analyze - Theory Descriptions97@pY9:@p98Introductionq9;@p!9D@p"9<Analyze attempts to localize the cause of intermittent disk and tape99L@p"9Esubsystem failures. It does this by reading the system event file andA9U@p"9Mapplying two sets of (best guess) theories; one for disk subsystems, I9Z@p9Vthe other for tape subsystems. Q9[@p!9d@p#9\They are called "best guess" theories because, the best that we can do99m@p$9eat this time is venture a guess as to the cause of a particular failure.A9v@p$9nEach theory is based on what we know about error checking built into theQ9@p$9whardware and software, the information recorded in the system event filea:@p$:being analyzed, and common sense. But, because the theories are based onq:@p$:	limited knowledge, information, and common sense they are susceptible to!:@p":inaccuracy. You must keep that fact in mind when reading the report. ":@p#:#@p#:In other words, if you have reason to doubt the Analyze report, do so.#1:,@p#:$Don't go changing parts or making adjustments just because the Analyze$9:4@p":-report indicated that the part or adjustment may be causing failures.%A:=@p":5If you don't agree, don't do it. Remember, Analyze is an information &H@p:>sorter designed to replace SYSERR and SYE, not human judgment.z	:c@p:G3!!3.1.2.M.oz	:N@p:J9q=YR.T.3.1.2.0.rev_trans_theory_intro)	:PG-)i:Q*:S
a:[@p#:TSTOP - You are moving in a reverse direction through the menu. You are*0@p:\about to back into the Introduction to the Theory descriptions.(Q:eG-,9:f,P:h
a:n@p:i Subsystem TAnalyze-Theory@Descriptions-:o@p-a:r@p:pTopic Menu:-y:t@p.):w@p:u 0. Introduction.A:y@p.y:}@p
1;
a;@p;
              Analyze - Disk Theories19;@p2;@p;Introduction2);@p2Y;@p ;There are 45 disk theories. The theories evaluate and attempt to2q;'@p!; identify the cause of disk errors recorded in a system event file.3q;0@p";(Currently, the disk theories only evaluate error events that involve:4y;1@p6;8@p;2 RH10, RH11, and RH20 disk controllers that use6;9@p7;?@p;: RP04, RP05, RP06, or RM03 disk drives.7;@@p7q;B@p8	;C@p8 @p;DThe following menu lists the major Disk Theory categories.z	;p@p;M#9b["3.1.2.1.M.z	;U@p;QfY:HR.T.3.1.2.0.rev_trans_disk_theory_intro9q;WG-:Y;X:p;Z
a;b@p#;[STOP - You are moving in a reverse direction through the menu. You are;!;k@p!;cabout to back into the Introduction to the Disk Subsystem Theories.<);l@p=0@p
;mYour response please:91;rG->	;s> ;u
a;{@p;v             Analyze - Disk Subsystem Theories>Q;}@p?9<@p;~Topic Menu:?Q<@p@<@p< 0. Introduction@<@p@Q<@p< 1. Unsafe Theories .................. [1.1.1] thru [1.1.9]@i<@p< 2. Servo System Theory .............. [1.2.1]Aa<@p< 3. Operation Incomplete Theories .... [1.3.1] thru [1.3.2]BI<#@p< 4. Massbus (control bus) Theories ... [1.4.1] thru [1.4.2]CA<+@p<$ 5. Massbus (data bus) Theories ...... [1.5.1] thru [1.5.6]D9<2@p<, 6. Read Data Error Theories ......... [1.6.1] thru [1.6.12]E1<:@p<3 7. Channel Error Theories ........... [1.7.1] thru [1.7.5]F)<A@p<; 8. Header Compare Error Theory ...... [1.8.1] thru [1.8.2]G!<H@p<B 9. Index Error Theory ............... [1.9.1]H<I@pI@p<JYour selection please (topic #):[=_G-z	<T@p<R09>w*3.1.2.1.1.0.J<UG-JA<WJX<X
a<_@p<Y            Analyze - Disk Subsystem Unsafe TheoriesK	<a@pKy<d@p<bIntroductionL<e@pLA<n@p!<fThe TOPS-10, TOPS-20 and VAX/VMS  operating systems consider UnsafeLY<v@p!<oErrors to be non-recoverable device errors. When a drive reports anMa<@p"<wunsafe condition, the operating system places the drive off-line and Ni=@p=notifies the operator that manual intervention is required.Oq=@pPi=@p"=	There are fourteen Unsafe Theories. The theories attempt to localize Q=@p"=the cause of an unsafe error to one of several areas in the drive orR	=!@p#=that are important to maintaining the integrity of the drive while it S=$@p="is spinning.T=&@pTI=.@p"='Normally, in order to avoid reporting transient causes, the thresholdTa=7@p#=/for reporting unsafe errors would be set at two or more. However, sinceUi=@@p#=8unsafe errors are fairly rare, the threshold has been set to one. Thus,Vy=I@p$=Athere will be a report produced for each drives that detects any kind ofX	=L@p=Junsafe error.Y=N@pYH@p=OThe following menu lists the fourteen Unsafe Theories.z	=y@p=W!Qs*3.1.2.1.1.M.oz	<N@p=[)	@$R.T.3.1.2.1.1.0.rev_trans_unsafe_introIi=a[x=b
a=k@p#=cSTOP - You are moving in a reverse direction through the menu. You are\)=r@p=labout to back into the Introduction to the Unsafe Theories.]1=t@p^(@p
=uYour response please:I@,G-ZQ={G-_=|_0=~
a>@p=           Analyze - Disk Subsystem Unsafe Theories_a>@p`Q>	@p>Topic Menu:`i>@pa>@p>
 0.  Introductiona1>@p> 1.  Disk Unit Power Supply Theory ........ [1.1.1]ai>@p> 2.  RP04 AC Power Theory...................[1.1.1A]  bY>#@p> 3.  RP04 DC Power Theory...................[1.1.1B]cI>*@p>$ 4.  RP06 DC Power Theory...................[1.1.1C]d9>1@p>+ 5.  R/W Head Select Logic Fault Theory ... [1.1.2]e)>8@p>2 6.  Clock Timing Fault Theory ............ [1.1.3]f>?@p>9 7.  R/W Current Control Logic Theory ......[1.1.4]g	>F@p>@ 8.  Head to Cylinder Position Theory.......[1.1.4A]gy>M@p>G 9.  R/W  Phase Locked Oscillator Drive Theory..[1.1.5]hi>U@p>N 10. R/W  Phase Locked Oscillator Media Theory..[1.1.5A]iY>\@p>V 11. RP06 Write and Offset Theory...........[1.1.6]jQ>c@p>] 12. Head Load Speed Theory.................[1.1.7]kA>j@p>d 13. RP04 Pack Speed Theory.................[1.1.8]l1>q@p>k 14. Drive Timing Logic Theory..............[1.1.9]m!>r@pn@p>sYour selection please (topic #):z	>{@p>yJ?h(3.1.2.1.1.1.ny>}G-o9>~oP?
a?	@p$?Theory - If a drive detects either an AC Low or DC Low error condition, p?@p$?
then there is a good chance that the fault lies in the drive and that itq?@p"?has something to do with either the power distribution system or ther!?@p?power supply.s)?@psY?'@p?   AC Low/DC Low Error - Drive Power Supply Theory ... [1.1.1]sq?(@ptq?-@p?)     DP030(RP04/SN: 23) reports:u	?/@puY?3@p
?0      4.  AC-Low errors.uq?7@p
?4      no  DC-Low errors.v1?8@pvq?>@p?9  122. Total Retries (HARD and SOFT)w	??@pwa?G@p?@  Time:  2-Mar 10:31:28  TO 9-Mar 03:50:41  Span: 161:19:13wy?H@pxq?Q@p#?IThresholds - There are no thresholds associated with this theory. The y	?Y@p#?Rtheory produces a report for every drive that detects either an AC Lowz?b@p$?Zor a DC Low error symptom. The report identifies the drive and lists the{@p?cnumber of times each symptom occurred.z	?l@p?jnyCe3.1.2.1.1.1.A.}?mG-}A?o}X?p
a?x@p ?qBackground - Two detectors monitor electrical power in the drive:~	?z@p	@@p"?{  AC LOW - The AC Power Low Detector sets if the ac power exceeds the!@@p@  acceptable range. Typically: + or - 10%)@
@p	@@p"@  DC LOW - The DC Power Detector sets if any of the dc power supplies!@@p#@  exceed there acceptable range. The range, of course, depends upon the(@p
@  dc supply and its use.z	@D@p@!#ciA&3.1.2.A.1.1.1lydrive.y_az	=x@p@&[ER.T.3.1.2.1.1.1.A.rev_trans_power_supply_theory_a_@-@@/
a@7@p#@0STOP - You are moving in a reverse direction through the menu. You areq@=@p@8about to back into the Power Supply Theory.y@?@pX@p
@@Your response please:A5G-y@FG-I@G`@I
a@Q@p"@JTheory-If an RP04 drive detects an AC unsafe condition, the cause is	@Y@p @Rusually associated with a power brownout or a power failure.  It
@b@p$@Zindicates the AC voltage of the drive power transformer secondary is low.@d@p
)@e@p
A@g@p3a
Y@h@p
q@o@p@ishAC4UsafePError:-5RP04pACtPower@Theory...[1.1.1A]@xy. 1.tACUnsafeerrors.q@|@p1@~@pIA@p@deTimeeofiError:P23-Nov22:03:03aA@p1AyHk3.1.2.A.1.1.1.AqAG-1AHA
aA(@p#A Background - This theory is associated with an AC low condition.  Whenx@pA)it occurs, there is usually an AC low condition also.3.1.2.B.1.1.1.1(z	@C@p	A32/	J
R.T.3.1.2.A.1.1.1.A1A7XA8
aAA@p#A9STOP - You are moving in a reverse direction through the menu. You are	AF@pABabout to back into the AC Unsafe Theory.AH@ph@p
AIYour response please:(BEG-z	AP@pA.E!B"YAQG-ASAT
aA]@p$AUTheory - If an RP04 drive detects a 30 Volts Unsafe condition, it pointsIAf@p!A^to a bad DC power supply in the Vendor Logic portion of the drive.YAg@paAj@pAhPACKET 1.yAk@p!As@pAl30 Volts Unsafe Error - RP04 DC Power Theory ... [1.1.1B]9At@p1Ay@pAu   DP400 (RP04/SN: 5) reports:IAz@pA@pA{   1. 30 Volts Unsafe errors.)B@pqB@p 	B@pB  Time of Error: 23-Nov 22:03:03 !B@p qB@p"B	Thresholds - There are no thresholds associated with this theory.  It!	B@p"Bproduces a report for every 30 volts unsafe condition detected in an"@pBRP04 drive.z	B @pBYB^3.1.2.B.1.1.1.A#IB"G-$	B#$ B%
aB-@p"B&Background - There is a 28 volt DC power supply located in the Vendor$QB6@p$B.Specific portion of the equipment.  Whenever it drops more than 10%, the%X@p!B730 volts unsafe bit is set.  This error is specific to RP04 drives.3.1.2.C.1.1.1.18pz	AL@p	BCIICGR.T.3.1.2.B.1.1.1.AABG(XBH
aBQ@p#BISTOP - You are moving in a reverse direction through the menu. You are)	BW@pBRabout to back into the 30 Volts Unsafe Theory.*BY@p*x@p
BZYour response please:8yCLG-z	Ba@pB>#IC+iBbG-,Bd,(Be
aBn@p!BfTheory - If an RP06 drive detects a DC Voltage Unsafe condition, it,YBv@p!Bopoints to a bad DC power supply in the Vendor Logic portion of the-aBy@pBwequipment..iBz@p/B}@pB{PACKET 4./)B~@p/QC@pBDC Unsafe Error - RP06 DC Power Theory ... [1.1.1C]/iC@p0YC
@pC1ADP250(RP06/SN:110000)oreports:0qCerrors1YC@p2!C@p28@pC  Time of Error: 30-Nov 04:07:31z	C@pC+i:E
3.1.2.C.1.1.1.A3!CG-3aC!3xC"
aC+@p"C#Thresholds - There are no thresholds associated with this theory.  A4)C2@pC,report is produced for each DC Unsafe condition detected.51C4@p6)C<@p#C5Background - This condition is associated with a DC low condition.  It6@@p$C=occurs when the power supply is either above or below its rated voltage.3.1.2.1.1.2.1.1Qpz	B]@p	CI(@R.T.3.1.2.C.1.1.1.A+QCM9@CO
aCW@p#CPSTOP - You are moving in a reverse direction through the menu. You are9qC^@pCXabout to back into the DC Voltage Unsafe Theory.:yC_@p;`@p
C`Your response please:QyEG-z	Cg@pCE}DP&<QCiG-<yCj=Cl
aCt@p!CmTheory - If a drive reports either a No Head Select or a Multi Head=AC}@p#CuSelect error condition, then there is a good chance that the fault lies>ID@p$C~in the drive and that it has something to do with the head select logic.?YD@p@iD@pD	  Head Select Error - R/W Head Select Logic Theory ... [1.1.2]AD@pBD@pD     DP010(RP06/SN: 55) reports:BD@pBiD@pD      6.    NHS errors.CD @pD      no    MHS errors.CAD!@pDD&@pD"  12. Total Retries (HARD and SOFT)DD(@pDiD/@pD)  Time:  2-Mar 10:31:28  TO 9-Mar 03:50:41  Span: 161:19:13ED1@pEyD9@p#D2Thresholds - There are no thresholds associated with this theory. The FDB@p#D:theory produces a report for every drive that detects either a NHS or aGDK@p#DCMHS error symptom. The report identifies the drive and lists the numberH(@pDLof times each symptom occurred.z	DT@pDR<QE3.1.2.1.1.2.A.J	DVG-JIDWJ`DY
aD`@pDZBackgroundo-TwodetectorsmonitorIheadselection:2KDa@pLDj@p"DbNHSE-NoHeadSelectmonitorsthree signals: read, write, and headLDr@p Dk  select. NHS sets if either read or write is active without headM!Dz@p Ds  select. (i.e., head select has been disabled for some reason.)N!D{@pO!E@p"D|  MHS - Multiple Head Select monitor head select current and sets ifO8@pE  two or more heads are center tapped at the same time.z	E/@pE
aE"@p#ESTOP - You are moving in a reverse direction through the menu. You areSE(@pE#about to back into the Head Select Theory.T!E)@pU@p
E*Your response please:o	GG-Q1E0G-UqE2VE3
aE<@p$E4Theory- If a drive reports a Transitions Unsafe or a Transition DetectorV9EE@p$E=Failure, then chances are the fault lies in the drive and has to do withWIEJ@pEFthe write clock timing logic.XYEK@pY!ES@pEL  R/W Transition Error - Clock Timing Logic Theory ... [1.1.3]Y9EU@pZ9EZ@pEV     DP020(RP06/SN: 33) reports:ZQE[@p[!E_@pE\        4.  TDF errors.[9Ec@pE`        no  TUF errors.[yEe@p\9Ej@pEf  21. Total Retries (HARD and SOFT)\QEk@p]!Es@pEl  Time:  2-Mar 10:31:28  TO 9-Mar 03:50:41  Span: 161:19:13]9Et@p^1E}@p#EuThresholds - There are no thresholds associated with this theory. The ^IF@p#E~theory produces a report for every drive that detects either a TDF or a_QF@p#FTUF error symptom. The report identifies the drive and lists the number``@pFof times each symptom occurred.z	F@pFQ1Fs3.1.2.1.1.3.A.bAFG-cFcF
aF$@pFBackground - Two detectors monitor write clock transitions:cIF%@pdAF.@p"F& TUF - Transitions Unsafe monitors two signals: write and write clockdYF6@pF/ transitions. TUF sets if write is active without write clockeaF9@pF7 transition. faF:@pgFC@p"F; TDF - Transition Detector Failure monitors for the case where writeg)FL@p#FD clock transitions are true, but write is not. Among other things, thish1FT@p#FM is a clever way to assure that the write clock transition detector isiAFX@p	FU working properly.jIFY@pkFb@p"FZNote: Write clock transitions are monitored by a timing detector. ThekFk@p#Fctiming detector monitors the write clock to insure that it is occurringl @p#Flat the correct time intervals. The intervals are drive type dependent.z	G@pFubAGu$3.1.2.1.1.4.g_tPACKET 5.z	E-@pFzQyHpR.T.3.1.2.1.1.3.A.rev_trans_clk_timing_theory_aUYGpG
aG@p#GSTOP - You are moving in a reverse direction through the menu. You arep1G@pG
about to back into the Clock Timing Theory.q9G@pr@p
GYour response please:HwG-n9GG-s	Gs G
aG%@p"GTheory - If a drive reports either a Current Sink Failure, a CurrentsQG.@p#G&Switch Unsafe, a Write  Select Unsafe, or a Write  Current Unsafe errortYG6@p G/condition, then there is a good chance that the fault lies in theuiG?@p!G7drive and that it has to do with either the write control logic orviGC@pG@the write current generators.wqGE@px9GM@p!GF  R/W Control Error - R/W Current Control Logic Theory ... [1.1.4]xQGO@pyYGT@pGP     DP120(RP06/SN: 43) reports:yqGU@pzAGY@p
GV     10.  CSF errors.zYG]@p
GZ      no  CSU errors.{Ga@p
G^      no  WSU errors.{YGe@p
Gb      no  WCU errors.|Gg@p|YGl@pGh  10. Total Retries (HARD and SOFT)|qGm@p}@@pGn  Time:  2-Mar 10:31:28  TO 9-Mar 03:50:41  Span: 161:19:13z	Gy@pGwn9J)$3.1.2.1.1.4.A.~QGzG-G|(G}
aH@p#G~Thresholds - There are no thresholds associated with this theory. The YH@p$Htheory produces a report for every drive that detects either a CSF, CSU,aH@p#HWSU, or a WCU error symptom. The report identifies the drive and listsqH@pHthe number of times each symptom occurred.yH@pYH%@pH Background - Four detectors monitor write current:qH'@pYH/@p#H( CSF - Current Sink Failure monitors the write current and sets if theqH7@pH0 current does not shut off at the end of the write operation.yH9@pyHA@p H: CSU - Current Switch Unsafe monitors the write current for eachHI@p#HB recording zone. CSU sets if the write current exceeds zone tolerance.HK@p	HT@p$HL WSU - Write Select Unsafe monitors head write current. WSU sets if both	1HZ@pHU detectors sense write current at the same time.
AH\@p)Hd@p!H] WCU - Write Current Unsafe monitor write current and sets if write@@pHe current is sensed during a non-write operation.z	I@pHmqIk$3.1.2.A.1.1.4t_PACKET 8.z	G@pHro	K=R.T.3.1.2.1.1.4.A.rev_trans_r_w_current_theory_arqHyxHz
aI@p#H{STOP - You are moving in a reverse direction through the menu. You are)I
@pIabout to back into the R/W Current Control Logic Theory.1I
@p(@p
Iresponseplease:9IpG-I
aI@p"ITheory.-.IfadriveqdetectsaWriteReadyUnsafe condition, it couldaI'@p$Ipoint to a bad servo amplifier, a bad cylinder detector and/or bad writeiI0@p#I(counter circuits in the SS board of the DCL, or bad write control logicyI6@pI1in the Vendor Logic portion of the drive.	I8@piI9@pFwI;@pIB@pI<   WRU Error - Head to Cylinder Position Theory ... [1.1.4A]1ID@p)II@pIE   DP250 (RP06/SN: 10000) reports:AIJ@pIO@pIK   1. Write Ready Unsafe errors.)IQ@pyIR@pIW@pIS  Time of Error: 30-Nov 04:07:31)IY@pyIb@p$IZThreshold - There are no thresholds associated with theory.  It produces@pIca report for every write ready unsafe condition detected.3.1.2.1.1.5.1.17Hz	I@pIm
aI{@p#ItBackground - Whenever a write command is being executed, the heads are1J@pI|to be within a certain range relative to the cylinder.  If this8@pJspecified range is exceeded, the error occurs.z	J@p	J
LLR.T.3.1.2.A.1.1.4.A!!JG-!iJ"J
aJ@p#JSTOP - You are moving in a reverse direction through the menu. You are"1J"@pJabout to back into the Write Ready Unsafe Theory.#9J#@p$ @p
J$Your response please:7QKAG-z	J+@pIi~QJz %J-G-%9J.%PJ0
aJ8@p#J1Theory - If a drive detects PLO unsafe error(s), and they are detected&JA@p#J9on different media or different cylinders on the same media, it points'	JI@p!JBto problems on the servo head head read path and could be either a(JN@pJJbad servo head or bad servo track.)JP@p)iJQ@pHn*JS@p*J[@p!JT   PLO Error - R/W Phase Locked Oscillator Drive Theory ... [1.1.5]*1J]@p+9Jb@pJ^   DP000 (RP06/SN: 492) reports:+QJc@p,!Jk@pJd   2. PLO errors on different media or different cylinders of,9Jo@p
Jl      the same media.-9Jq@p-yJr@p.@pJs  Time: 17-Mar 01:00:00  TO  17-Mar 03:00:00   Span:   1:59:60z	J~@pJ|%Li3.1.2.1.1.5.A/)KG-/iK0K
aK@p!KThreshold - There are no overt thresholds associated with this this01K@p$K
theory.  However, because of the very nature of it (i.e. there have to be19K@p$Kat least 2 errors occurring at different places), its inherent threshold2IK@pb3YK @p3qK)@p$K!Background - The PLO is the controller that sets the timing sequence for4	K2@p!K*passing of data (on either a read or write operation).  This error5@p%K3occurs when the drive detects the loss of synchronization within the PLO. 3.1.2.A.1.1.5.5I@z	J'@pK?M^R.T.3.1.2.1.1.5.A$yKC8KD
aKM@p#KESTOP - You are moving in a reverse direction through the menu. You are8IKR@pKNabout to back into the PLO Drive Theory.9QKT@p:(@p
KUYour response please:IILQG-z	K\@pK:9L*$;K]G-;AK_;XK`
aKi@p$KaTheory - If a drive reports PLO unsafe errors and they occur on the same<	Kr@p"Kjmedia and on the same cylinder of that media, it is most likely a bad=Kt@pKsmedia. >!Kv@p>IKx@pKwPACKET 9.>aKz@p?	L@p"K{   PLO Error - R/W Phase Locked Oscillator Media Theory ... [1.1.5A]?!L@p@)L	@pL   DP250 (RP06/SN: 735) reports@AL
@pAL@p$L   2. PLO errors occurring on the same media with all errors on the sameA)L@pL      cylinder.B9L@pBiL@p	L      Media ID: PS1CL@p	L      Cylinder: 768C9L @pCqL"@pD@pL#  Time: 23-Nov 08:58:00  TO  28-Oct 08:58:00   Span: ***:00:00z	L.@pL,;AM3.1.2.A.1.1.5.AE!L/G-EaL1ExL2
aL;@p#L3Threshold - There have to be at least 2 errors occurring in this mannerF)LA@pL<in order for the theory to be called out.G9LC@pH@pLDBackground - Refer to background for the PLO Drive Theory.3.1.2.1.1.6.1.1[Xz	KX@p	LN!!BAR.T.3.1.2.A.1.1.5.A;LRJLT
aL\@p#LUSTOP - You are moving in a reverse direction through the menu. You areJALb@pL]about to back into the PLO Media Theory.KILc@pL @p
LdYour response please:[aMbG-z	Lk@pLJ/)M(MLmG-M9LnMPLp
aLx@p"Lq If an RP06 drive detects a Write and Offset error, it could point toNM@p$Ly a bad DCL register board, or bad drive command logic in the Vendor LogicO	M@pM portion of the drive.PM@pPYM	@pMPACKET 6.PqM@pQM@p"M
   Write and Offset Error - RP06 Write and Offset Theory ... [1.1.6]Q1M@pR9M@pM   DP110 (RP06/SN: 520) reports:RQM@pS!M @pM   1. Write and Offset errors.S9M!@pTM#@pT@pM$  Time of Error:  4-Sep 01:30:49z	M,@pM*MM{
3.1.2.1.1.6.AUM-G-UAM/UXM0
aM9@p!M1Threshold - There are no thresholds associated with this theory.  AV	MA@p"M:report is produced for every Write and Offset error that is detected.WMC@pXMK@pMDBackground - A programmed offset is only allowed during a readX1MS@p MLoperation.  This error will occur if, during a write operation, aY0@p%MTprogrammed offset is active.  This error will only be detected on an RP06.3.1.2.1.1.7.1.6r0z	Lg@pM`7QOR.T.3.1.2.1.1.6.ALyMd\(Me
aMn@p#MfSTOP - You are moving in a reverse direction through the menu. You are\YMt@pMoabout to back into the Write and Offset Theory.]aMv@p^H@p
MwYour response please:r9OG-z	M~@pM[UN? _9MG-_aN_xN
aN@p$NTheory - If an RP04 drive reports a Velocity Unsafe condition, it points`)N@p$N
to a bad servo mechanism.  It warrants immediate Field Service attention.a9N@pbIN@pNPACKET 1.baN@pc	N"@pN   Velocity Unsafe Error - Head Load Speed Theory ... [1.1.7]c!N#@pd!N(@pN$   DP400 (RP04/SN: 5) reports:d9N)@peN.@pN*   1. Velocity Unsafe errorseN/@peaN5@pN0   Take drive offline and call Field Service.eyN7@pfYN8@pfqN=@pN9  Time of Error: 23-Nov 22:03:03g@pz	NC@pNA_9O13.1.2.1.1.7.AgqNDG-h1NFhHNG
aNP@p$NHThresholds -yTherearenoNthresholdsassociatedwithBthisrtheory.WhSincehyNX@pNQitoisesuchhaiserious condition,dtheNdrive#becomes immediatelyj	N]@py are supposed to.  If the detected speed oflqNy@p#Nqthe heads at any particular point is too fast for the maximum speed setnO@p"Nzfor that point, a Velocity Unsafe condition occurs.  The unsafe lightoO
@p#Oin the console will then go on and the drive is no longer available forp@pOuse by the system.  This condition is unique to RP04's.3.1.2.1.1.8.1.7	Pz	Mz@pO[aPMR.T.3.1.2.1.1.7.A_!OsO
aO#@p#OSTOP - You are moving in a reverse direction through the menu. You ares1O*@pO$about to back into the Velocity Unsafe Theory.t9O+@pu @p
O,Your response please:	YPRG-z	O3@pOgqO~"vO5G-v9O6vPO8
aO@@p"O9Theory -  If an RP04 drive detects a Pack Speed Unsafe condition, itwOI@p"OApoints to a variety of causes:  loss of phase to the primary power, ax	OQ@p#OJbad drive motor, a broken drive belt, or a bad servo mechanism.  FieldyOW@pORService should be notified immediately.zOX@pzqO[@pOYPACKET 1.{	O\@p{1Oc@pO]   PSU Error - RP04 Pack Speed Theory ... [1.1.8]{IOd@p|1Oi@pOe   DP400 (RP04/SN: 5) reports:|IOj@p}Oo@pOk   1. Pack Speed Unsafe errors})Op@p}qOv@pOq   Take drive offline and call Field Service.~	Ox@p~iO}@pOy  Time of Error: 23-Nov 22:03:03@pz	P@pPvPk3.1.2.1.1.8.AiPG-)P@P
aP@p"PThresholds - There are no thresholds associated with this theory.  ItqP@p$Ppoints to an extremely serious condition and makes the drive unavailableyP@p
Pto the Operating System.	P@pIP&@p!PBackground - There are two conditions that have to be maintained inaP,@pP'order to keep this error from occurring:iP-@pAP6@p#P.The pack speed has to be AT LEAST 70% of the normal operating speed andYP?@p#P7Hold Reverse must be present if the Pack at Speed signal is clear.  IfiPH@p$P@either of these conditions are not met, the error occurs.  This error isp@p	PIconfined to RP04's3.1.2.1.1.9.1.8hz	O/@pPOr9QRR.T.3.1.2.1.1.8.AuyPS
 PU
aP]@p#PVSTOP - You are moving in a reverse direction through the menu. You are
QPd@pP^about to back into the Pack Speed Unsafe Theory.YPe@p
@@p
PfYourresponse please:qQ^G-z	Pm@pPKiQ"
aPz@pPsTheoryT-mIfgaEdrive-detectsTamDriveoTimingeError,.it1indicatesa!Q@pP{hardwarefailurePin0thePdrive:timingelogic.!Q@pQ@pQPACKET 7.Q@pAQ
3.1.2.1.1.9.A!Q'G-aQ)xQ*
aQ3@p"Q+Thresholds-There are no thresholds associated with this theory.  A)Q9@pQ4report is produced for each error that occurs.1Q;@pQD@p#Q<Background - When a write or read is enabled, the heads need to receive1QL@p"QEan index and a sector pulse in order to execute the command properly.@@pQMIf these are not available, the error occurs.z	QU@pQx	YSG)Q}G-=z	Pi@pQYZ)SJF.T.3.1.2.1.2.1.fwdtransservosystheory
aQj@p#QbThat's it. There are only fourteen unsafe theories. Next on the menu isQn@p
Qkthe servo system theory.!Qo@p`@p
QpYour response please:z	R@pQuZQR|&3.1.2.1.2.1.nt_system:aR.T.3.1.2.1.1.9.A.rev_trans_r_w_current_theory_aQQXR
aR	@p#RSTOP - You are moving in a reverse direction through the menu. You are 	R@pR
about to back into the unsafe theories.!R@p!h@p
RYour response please:9)SPG-9RG-"YR"pR
aR#@p#RTheory - If a drive reports either a Seek Incomplete or an Off Cylinder#!R+@p#R$error condition, then chances are the fault is in the drive and has to$1R3@pR,do with either the servo mechanism or the servo control logic.%9R5@p&9R;@pR6  Servo Error - Servo System Theory ... [1.2.1]&QR=@p'9RB@pR>     DP020(RP04/SN: 22) reports:'QRC@p(!RG@pRD      no  SKI  errors.(9RK@pRH      3.  OCYL errors.(yRM@p)9RR@pRN  12. Total Retries (HARD and SOFT))QRS@p*!R[@pRT  Time:  2-Mar 10:31:28  TO 9-Mar 03:50:41  Span: 161:19:13*9R\@p+1Re@p#R]Thresholds - There are no thresholds associated with this theory. The +IRn@p#Rftheory produces a report for every drive that detects either a SKI or a,QRw@p$RoOCYL error symptom. The report identifies the drive and lists the number-`@pRxof times each symptom occurred.z	S@pR~9Se3.1.2.1.2.1.A./ASG-0S0S
aSp"SBackground - Two error detectors monitor the performance of the servo0IS@pQw1QS@p1iS@p#S OCYL - Off Cylinder monitors the output of the servo head and sets if2S!@p#S the servo moves off cylinder during a non-positioning operation. This3	S'@pS" detector is not incorporated in RM03 drives.4S(@p4qS1@p"S) SKI - Seek Incomplete monitors the amount of time that it takes the5	S9@p!S2 servo to complete a positioning operation. SKI is set if the servo6SB@p"S: is unable to complete the positioning operation within a prescribed7@pSC amount of time. Typically 100 m/s.z	Sn@pSi)TxTopic Menuz	R@pSLqWrF.T.3.1.2.1.3.0.fwdtransopiintro"ASR:SS
aS\@p#STThat's it. There is only one servo system theory. Next on the menu are:9S_@pS]the OPI theories.;ASa@p;x@p
SbYour response please:z	T
@pSg/AUD$3.1.2.1.3.0.heoiXR.T.3.1.2.1.2.A.rev_trans_servo_sys_theory_a8qSoG-=aSq=xSr
aS{@p#SsSTOP - You are moving in a reverse direction through the menu. You are>)T@p#S|about to leave the OPI theories and back into the servo system theory.?1T@p@8@p
TYour response please:OT~G-<QT
G-A)TT
aT@pTng (theoryAnalyze.-DiskaSubsystemOPIHTheoriesAqT@pBYT@pTIntroductionBqT@pC!T$@p"TThe@timingTforaboth aosearchrandla dataotransfer operationucomesmfromC9T,@p"T%themediumT(servotrack).andRisdusedWthroughoutntheidriveito controlDAT5@p"T-thegoperation.pAnOPI error,atherefore,(couldsbeccausedsbyweitherttheEIT>@p$T6mediumh(theory1.3.1),orbythe controlnlogicethat distributesaandcusesFQTB@pdid not occurM@pTq    within three Index pulses.z	U@pUiWnoccurred.oz	T	@pTz8qVNR.T.3.1.2.1.3.0.revtransopiintroATO`U
aU	@p#USTOP - You are moving in a reverse direction through the menu. You arePU@pU
about to back into the Introduction to the OPI theories.QU@pR@p
UYour response please:iaVUG-3.1.2.1.3.M.NIUG-SUS0U
aU%@pU     Analyze - Disk Subsystem Operation Incomplete TheoriesSaU'@pTYU*@pU(Topic Menu:TqU+@pU!U/@pU, 0. IntroductionU9U0@pUqU5@pU1 1. Media OPI Theory ...[1.3.1]V	U7@pVYU<@pU8 2. Drive OPI Theory ...[1.3.2]VqU=@pWAU?@pWX@pU@Your selection please (topic #):z	UH@pUF<QVI,3.1.2.1.3.1.XAUIG-YUKYUL
aUU@p$UMTheoryo-hIftardisk.subsystem@reportsOperationIncompleteerrors,iand ifYIU^@p#UVtheaerrors0involveatwo1or:more3drives,@andiftheyVarepassociatedewithZYUf@paU thedsame5medium,Pcylinder,atrackqandesector,tthenthereVis@agood[aUl@pUgchancerthatmthe mediumeiswcausingrthererrors.\aUm@p]AUs@pUne OPIuErroro- MediaaTheoryi...a[1.3.1]]YUt@p^1U}@p#UuV:@MediaID:eOPER1a-dCyl:.33., Trk:r4.,dSect:i12.twasmidentifiednwith^IV@pU~VB@noHard;andt6. SofteOPI errorseon QV@prst detected the error.g)VC@ph @pVDBackground - Refer to the OPI Introduction.z	Vm@pVKXATt.3.1.2.1.3.2.heo(z	U@pVPOXR.T.3.1.2.1.3.1.revtransmediaopitheoryRiVVjPVX
aV`@p#VYSTOP - You are moving in a reverse direction through the menu. You arekVf@pVaabout to back into the Media OPI Theory.l	Vg@pl`@p
VhYour response please:~!WxG-iVnG-mQVpmhVq
aVz@p$VrTheory - If a drive reports multiple Operation Incomplete errors, and ifnW@p#V{those errors are not associated with a particular medium, then chanceso)W
@p#WarenthelfaultrliesninHtheedrivedandehasisomethingtopdowiththetimingp1W@pWDrive Timing Logic Theory ... [1.3.2]rIW@ps9W"@pW     DP210(RP04/SN: 21) reports:sQW'@pW#     2. Hard and no Soft OPI errors.t!W)@ptyW.@pW*  24. Total Retries (HARD and SOFT)uW/@puaW7@pW0  Time:  2-Mar 10:31:28  TO 9-Mar 03:50:41  Span: 161:19:13uyW8@pvqWA@p$W9Threshold - At least 1 Hard or 5 Soft OPI errors are required to satisfyw	WJ@p%WBthis theory. The errors must pertain to the same drive. If multiple drivesxWS@p"WKare reported, check to see if theory 1.3.1 has also seen the errors.y)WX@pWTThe problem may be a faulty media.z1WY@p{Wb@p"WZThe report identifies the drive and lists the number of hard and soft{Wf@pWcOPI errors the drive detected.|!Wh@p|h@pWiBackground - Refer to the OPI Introduction.z	X/@pWpNIYc 3.1.2.1.4.0.ryz	Vk@pWt9)\9F.T.3.1.2.1.4.0.fwdtransmbcbintrom9WzW{
aX@p"W|That's it. There are only two OPI theories. Next on the menu are the9X
@pXMassbus (control bus) parity error theories.AX@p @p
X
Your response please:z	X@pXiaYR.T.3.1.2.1.3.2.rev_trans_dr_opi_theoryyXG-aXxX
aX#@p#XSTOP - You are moving in a reverse direction through the menu. You are)X(@pX$about to back into the OPI theories.1X*@p@p
X+Your response please:QYG-}aX1G-yX2X4
aX;@pX5    Analyze - Disk Subsystem Massbus Control Bus TheoriesAX=@p9X@@pX>IntroductionQXA@pXJ@p!XBRH10 and RH20 controllers have a single bit: Register Access ErrorXS@p#XK(RAE), which indicates that either a Massbus (control bus) parity error	!X\@p#XTor a Massbus (control bus) timeout occurred during an external register
1X_@pX]read or write.AX`@pqXi@p#XaRH11 controllers have two bits: RH Control Bus Parity Error (RHCPE) and
	Xr@p#XjNon-ExistenteDrived(NON-X-DRIVE).oThesesbitsmindicate Massbusi(control!X|@p)Y@p#X}This setzof7theoriesYattempttolocalize4thecauseXof@Massbus(controlAYT.3.1.2.1.4.0.revtransmbcbintroaY8Y
aY'@p#YSTOP - You are moving in a reverse direction through the menu. You areiY0@p$Y(about to back into the Introduction to the Massbus Control Bus Theories.qY1@p@p
Y2YourresponseGplease:0Y[Y;
aYC@pY<   Analyze - Disk Subsystem Massbus Control Bus Theories9YD@p1YF@pSIIYG@paYK@pYH 0. IntroductionyYL@p1YS@pYM 1. Massbus (control bus) RH Theory ...... [1.4.1]IYT@p1Y[@pYU 2. Massbus (control bus) Drive Theory ... [1.4.2] IY]@pd9Y^@pP@pY_Your selection please (topic #):z	Yg@pYe}aZB 3.1.2.1.4.1.9YiG-yYjYl
aYu@p$YmTheory - If a disk subsystem reports Massbus (control bus) parity errorsAY~@p$Yvor Massbus timeout errors, and if the errors involve two or more drives,QZ@p"Ythen chances are the fault lies in the controller or the Massbus. If,aZ@p"Zhowever, the errors are local to a single drive, then chances are the iZ@p"Zfault is in the drive and has to do with the Massbus interface logic.!qZ@p"yZ!@pZ  RH CBUS Error - Massbus (control bus) RH Theory ... [1.4.1]#Z"@p$Z&@pZ#     RH No: 3. reports:$)Z(@p$iZ-@pZ)     5. Massbus Control Bus Errors.%Z2@pZ.     2. different drives were involved.%QZ4@p&)Z9@pZ5  24. Total Retries (HARD and SOFT)&AZ:@p'@pZ;  Time:  2-Mar 10:31:28  TO 9-Mar 03:50:41  Span: 161:19:13z	ZF@pZD9[3.1.2.1.4.1.A.(!ZGG-(aZI(xZJ
aZS@p"ZKThreshold - At least two (controller detected) Massbus (control bus)))Z\@p#ZTparity errors or Massbus (control bus) timeouts are required to satisfy*1Zd@p#Z]this theory. In addition, the errors must involved two or more drives.+AZm@p"ZeThe report identifies the controller, the number of drives that were,IZu@p!Zninvolved, and the total number of Massbus (control bus) errors that-QZw@pTv.YZx@p.p@pZyBackground - Refer to the Massbus (control bus) Introduction.z	[&@p[(![|3.1.2.1.4.2.raeinvolved.z	Y5@p[Q\5R.T.3.1.2.1.4.1.A.rev_trans_mb_cb_rh_rae_theory_aY[1P[
a[@p#[STOP - You are moving in a reverse direction through the menu. You are2[@p[about to back into the Massbus (control bus) RH Theory.3	[!@p3x@p
["Your response please:G\@G-0	[(G-4i[)5[+
a[4@p$[,Theory - If a disk subsystem reports Massbus (control bus) parity errors51[=@p$[5or Massbus timeout errors, and if the errors involve two or more drives,6A[E@p"[>then chances are the fault lies in the controller or the Massbus. If,7Q[N@p"[Fhowever, the errors are local to a single drive, then chances are the8Y[V@p"[Ofault is in the drive and has to do with the Massbus interface logic.9a[X@p:i[`@p [Y  RH CBUS Error - Massbus (control bus) Drive Theory ... [1.4.2];[a@p<[g@p[b     DP020(RP04/SN: 451) was identified with<[l@p[h     6. Massbus Control Bus Errors<y[n@p=I[s@p[o    24. Total Retries (HARD and SOFT)=a[u@p>8@p[v  Time:  2-Mar 10:31:28  TO 9-Mar 03:50:41  Span: 161:19:13z	\@p[~0	Y3.1.2.1.4.2.A.?I\G-@	\@ \
a\p!\Threshold - One or more (controller detected) Massbus (control bus)@Q\@p#\parity errors or Massbus (control bus) timeouts are required to satisfyAY\@p"\this theory. In addition, all the errors must involve the same drive.Bi\(@p#\ The report identifies the drive and the number of Massbus (control bus)Cq\,@p
\)errors that occurred.E\-@pE@@p\.Background - Refer to the Massbus (control bus) Introduction.z	\8@p\]0Y^FY\bG-z	[%@p\;~!i{F.T.3.1.2.1.5.0.fwd_trans_mb_db_intro4Q\AH\C
a\K@p"\DThat's it. There are only two Massbus (control bus) theories. Next onH1\S@p\Lthe menu are the Massbus (data bus) parity error theories.I9\T@pJ0@p
\UYour response please:z	\}@p\Z]q,3.1.2.1.5.0.raewrite>---!R.T.3.1.2.1.4.2.A.rev_trans_mb_cb_dr_rae_theory_aG\dL(\e
a\n@p#\fSTOP - You are moving in a reverse direction through the menu. You areLY\v@p!\oabout to back into the Massbus (control bus) parity error theories.Ma\x@pNh@p
\yYour response please:c9^"G-K	\G-OY]Op]
a]	@p]     Analyze - Disk Subsystem Massbus (data bus) TheoriesP!]@pQ]@p$]
Introduction - Both Massbus controllers and Massbus devices check parityQ1]@p#]on the Massbus (data bus). The parity is checked during read and writeRA]!@p]operations as illustrated below.SI]#@pT](@p]$ DF10C     RH10    Massbus   DeviceT1].@p]) <read --- DPE   <---------  no ck <--- diskU]4@p]/ write>--- no ck ----------> PAR   ---> diskUa]5@pVA]:@p]6  UBA      RH11    Massbus   DeviceVY]@@p]; <read --- DPE   <---------  no ck <--- diskW)]F@p]A write>--- no ck ----------> PAR   ---> diskX	]H@pXi]M@p]I MBox      RH20    Massbus   DeviceY]S@p]N <read --- DPE   <---------  no ck <--- diskYQ]Y@p]T write>--- DPE   ----------> PAR   ---> diskZ1]Z@p[]\@p[)]d@p!]]This set of six Massbus (data bus) theories attempt to localize the]m@p#]ecause of Massbus (data bus) parity errors to either the MBox/UBA/DF10C,\H@p
]na controller, or a drive.z	]u@p]sK	_3.1.2.1.5.0.A.^]wG-^Y]x^p]z
a^@p"]{The first two theories apply to Massbus (data bus) parity errors that_!^@p#^were reported during read data operations. The last four theories apply`)^@p$^
to Massbus (data bus) parity errors that were reported during write dataa8@p^operations. z	^=@p^j6(3.1.2.1.5.M.z	\|@p^FY`XR.T.3.1.2.1.5.0.rev_trans_mb_db_introOA^#d ^%
a^-@p#^&STOP - You are moving in a reverse direction through the menu. You aredQ^6@p"^.about to back into the Introduction to the Massbus Data Bus Theories.eY^7@pf`@p
^8Your response please:`_G-by^>G-gQ^@gh^A
a^I@p^B @pAnalyzeq-DiskSubsystemrMassbusi(dataebus)(Theoriesh^J@pi^M@p^KTopic5Menu:i)^O@piY^R@p^P0.Introductioniq^T@pj)^\@p^U 1. Data Read/Massbus (data bus) RH Theory ............[1.5.1]jA^]@pkA^e@p^^ 2. Data Read/Massbus (data bus) Drive Theory .........[1.5.2]kY^g@plY^o@p^h 3. Data Write/Massbus (data bus) MBox (UBA) Theory ...[1.5.3]lq^p@pmq^x@p^q 4. Data Write/Massbus (data bus) RH Theory ...........[1.5.4]n	^z@po	@p^{ 5. Data Write/Massbus (data bus) RH Theory ...........[1.5.5]o!@pp!@p 6. Data Write/Massbus (data bus) Lone Drive Theory ...[1.5.6]p9
a_$@p"_Theory - If a disk subsystem reports Massbus (data bus) parity errorssA_-@p!_%during data reads, and if the errors involve multiple  drives, thentI_5@p"_.chances are the fault lies in the controller. If, however, the errorsuQ_>@p"_6involve a single drive then, chances are the fault lies in the drivevY_E@p_?and has something to do with the Massbus interface logic.wa_G@pxY_O@p!_H  RH DPE Error - Data Read/Massbus (data bus) RH Theory ... [1.5.1]xq_Q@pyy_X@p_R     RH No: 2. reports: (during Data Read operations)z_^@p_Y         4. Massbus (data bus) Parity Errors.{_d@p__         2. different drives were involved.{a_e@p|A_j@p_f  24. Total Retries (HARD and SOFT)|Y_l@p}(@p_m  Time:  2-Mar 10:31:28  TO 9-Mar 03:50:41  Span: 161:19:13z	_w@p_ur9`S 3.1.2.1.5.1.A.~9_yG-~y_z_|
a`@p$_}Threshold - At least two (controller detected) Massbus (data bus) parityA`@p#`errors are required to satisfy this theory. The errors must involve twoQ`@p#`or more drives and they must have occurred during data read operations.a`@p"`The report identifies the common controller and the number of drivesq`(@p"` that were involved. The report also lists the number of Massbus (datay`-@p`)bus) parity errors that occurred.`.@pQ`0@pi`5@p`1MBox/UBA    RHxx    Massbus   Device`7@pY`=@p`8 <read  --- DPE   <---------.- no ck <--- diskq`B@p`>                            !Y`H@p`C                            !_ no ck <--- disk!`J@p		`K@p	 @p`LBackground - Refer to the Massbus (data bus) Introduction.z	`y@p`U~9aP3.1.2.1.5.2.rd_Bad Spots.z	^;@p`Zc9bR.T.3.1.2.1.5.1.A.rev_trans_mb_db_rh_rd_theory_ag9`ax`b
a`k@p#`cSTOP - You are moving in a reverse direction through the menu. You are
)`r@p`labouttoback into the Massbus (data bus) RH Theory.
`tYour response please:#qb&G-
1`zG-`|(`}
aa@p"`~Theory - If a disk subsystem reports Massbus (data bus) parity errorsYa@p!aduring data reads, and if the errors involve multiple  drives, thenaa@p"achances are the fault lies in the controller. If, however, the errorsia@p"ainvolve a single drive then, chances are the fault lies in the driveqa'@pa and has something to do with the Massbus interface logic.ya(@pqa1@p!a)  RH DPE Error - Data Read/Massbus (data bus) Drive Theory  [1.5.2]	a2@pa8@pa3     DP020(RP04/SN: 33) was identified with)aA@p!a9    3. (RH detected - Data Read) Massbus (data bus) Parity Errors.	aB@paG@paC  24. Total Retries (HARD and SOFT))aI@px@paJ  Time:  2-Mar 10:31:28  TO 9-Mar 03:50:41  Span: 161:19:13z	aT@paR
1b3.1.2.1.5.2.A.	aVG-IaW`aY
aab@p#aZThreshold - One or more (controller detected) Massbus (data bus) parityak@p#acerrors are required to satisfy this theory. The errors must involve the!at@p#alsame drive and they must have occurred during data read operations. The1a|@p#aureport identifies the drive and lists the number of Massbus (data bus)Ab@pa}parity errors that occurred.Ib@p b@pbMBox/UBA    RHxx    Massbus   Device )b	@p!b@pb
 <read  --- DPE   <---------  no ck <--- disk!b@p!yb@p"@pbBackground - Refer to the Massbus (data bus) Introduction.z	b@@pb	c-"3.1.2.1.5.3.rd_medium.az	`w@pb!dR.T.3.1.2.1.5.2.A.rev_trans_mb_db_dr_rd_theory_ayb($hb)
ab2@p#b*STOP - You are moving in a reverse direction through the menu. You are%b9@pb3about to back into the Massbus (data bus) Drive Theory.&!b:@p'@p
b;Your response please:C9d#G-#!bAG-(bC(bD
abM@p"bETheoryE-rIf a systemrreportssMassbust(data)bus)xparity errors during](IbU@p!bNdataYwrites,andif those errorseinvolveomultiplescontrollers,rthen)Qb]@ppbVchancesarethefaulthas to6doMwithuthedmemoryscontrollerrorrthe*Ybe@ppb^channel.@If,however,.theterrorsrinvolveRa singleFcontrollerand+Ybn@p"bfmultiple:drives, then1chances areathe3fault1liesain the:controller1or,Ybv@p"bothe.Massbus.3Finally,3iftheerrorscinvolveasingledrive,then the-ab@p#bwfault is probably in the drive and has something to do with the Massbus.ic@pcinterface logic./yc@p01c
ac?@p$c7Threshold - At least two (controller detected) Massbus (data bus) parity6acH@p#c@errors are required to satisfy this theory. The errors must involve two7qcP@p cIor more controllers and they must have occurred during data write9cX@p"cQoperations. The report lists the number of Massbus (data bus) parity:ca@p#cYerrors that occurred and the number of different controllers that were;	cb@p[<cd@p<)ce@p<Ack@pcf MBox         RH20  Massbus   Device<Ycl@p=1cr@pcm         .--> DPE ---------->  PAR  ---> disk=Ict@p\\>)cz@pcu         `--> DPE ---------->  PAR  ---> disk>Ac{@p?!d@p$c|Since RH10s and RH11s do not check parity during a data write operation,?9d
@pdthistheoryonlyAappliestoRH20ccontrolledRdiskdsubsystems.@Id(databus)&Introduction.z	d=@pd5Ye)"3.1.2.1.5.4.xwbad spots.z	b>@pd#qf
ad.@p#d'STOP - You are moving in a reverse direction through the menu. You areDad6@pd/about to back into the Massbus (data bus) MBox (UBA) Theory.Eid7@pF`@p
d8Your response please:aQfG-Bid>G-GQd@GhdA
adJ@p"dBTheory - If a system reports Massbus (data bus) parity errors during HdR@p!dKdata writes, and if those errors involve multiple controllers, thenI!dZ@p dSchances are the fault has to do with the memory controller or theJ)db@p d[channel. If, however, the errors involve a single controller andK)dk@p"dcmultiple drives, then chances are the fault lies in the controller orL)ds@p"dlthe Massbus. Finally, if the errors involve a single drive, then theM1d|@p#dtfault is probably in the drive and has something to do with the MassbusN9e@pd}interface logic.OIe@pPe
@p"e  RH DPE Error - Data Write/Massbus (data bus) RH Theory ... [1.5.4]Pe@pQ!e@pe
     RH No: 4. reports: (during Data Write operations)Q9e@pe         3. (RH detected) Massbus (data bus) Parity Errors.R)e@pS!e @pe  24. Total Retries (HARD and SOFT)S9e"@pT@pe#  Time:  2-Mar 10:31:28  TO 9-Mar 03:50:41  Span: 161:19:13z	e-@pe+Bif"3.1.2.1.5.4.A.Ue/G-UYe0Upe2
ae;@p$e3Threshold - At leasttwo(controllerfdetected) Massbus (data bus) parityV!eD@p#e<errorsareerequiredtoSsatisfy1thisntheory. ThenerrorscmustrinvolveitheW1eL@poeEsamecontrollerandtwohor morerdrives.aAlsoetheoerrorscmustohaveXAeQ@peMoccurred@duringdatafwriteoperations.YAeS@pZeT@pZ1eY@peUMBoxs) IntrRH20tiMassbus	f.DeviceZIe[@p[ea@pe\write> ---  DPE --------->-- PAR ---> disk[1ee@p
Ug"&3.1.2.1.5.5.wr_					/ \z	d;@pfC9hR.T.3.1.2.1.5.4.A.rev_trans_mb_db_rh_wr_theory_aG9fbHf
af @p#fSTOP - You are moving in a reverse direction through the menu. You arebyf'@pf!about to back into the Massbus (data bus) RH Theory.df(@pdp@p
f)Your response please:	h G-af/G-eaf1exf2
af;@p"f3Theory8- IfravsystemcreportssMassbusa(datasbus)rparityrerrorsduring@f)fC@p!f<datadwrites,tandiifsthose errorseinvolvegmultiplecontrollers,theng1fK@pRfDchances are theTfaulthastodowiththememory controllerMor theh9fS@p fLchannel.1If,phowever,1the3errorsinvolvegasinglecontroller5andi9f\@p"fTmultipledrives,thenchancesare the fault lies in the controller orj9fd@p"f]the Massbus. Finally, if the errors involve a single drive, then thekAfm@p#fefault is probably in the drive and has something to do with the MassbuslIfq@pfninterface logic.mYfr@pnft@pn)f|@p"fu  RP PAR Error - Data Write/Massbus (data bus) RH Theory ... [1.5.5]nAf~@poIg@pf     RH No: 4 reports: (during Data Write operations)oag
ag4@p$g,Threshold - At leasttwo1drivedetected Massbus (data bus) parity errorsu1g<@p"g5(PAR)areYrequiredtoxsatisfylthisstheory.vTheserrors must havetbeenvAgE@p$g=detectedsbytwohor@moredrivessandetheyamustebetcommon,toHthe sameRdiskcwIgN@p#gFcontroller.Thehreport identifies the controller, the number of drivesxYgW@p#gOthat were involved, and the number of drive detected Massbus (data bus)yag[@pgXparity errors that occurred.zqg]@p{9g^@p{Qgc@pgMBox/UBA    RHxx  Massbus   Device{ige@p|9gk@pgf write> --- DPE --------->-- PAR ---> disk|Qgo@p
@ph
@p(@phe Massbus (data bus) Introduction.z	h9@pht)i)$3.1.2.1.5.6.wrrecovery.z	f,@phaQjR.T.3.1.2.1.5.5.A.revtransmbdbrhwrtheory2aeIh!h#
ah+@p#h$STOP - You are moving in a reverse direction through the menu. You are1h2@ph,about to back into the Massbus (data bus) RH Theory.9h4@p(@p
h5Your response please:1iG-9h;G-h<0h>
ahF@p"h?Theory - If a system reports Massbus (data bus) parity errors during ahO@p!hGdata writes, and if those errors involve multiple controllers, thenihW@p hPchances are the fault has to do with the memory controller or the	qh_@p hXchannel. If, however, the errors involve a single controller and
qhg@p"h`multiple drives, then chances are the fault lies in the controller orqhp@p"hhthe Massbus. Finally, if the errors involve a single drive, then the
yhy@p#hqfault is probably in the drive and has something to do with the Massbush|@phzinterface logic.h~@pIh@pai@p$i  RP PAR Error - Data Write/Massbus (data bus) Lone Drive Theory [1.5.6]yi
@p	i@pi     DP020(RP06/SN: 32) reports: (during Data Write operations)!i@pi      8. (drive detected) Massbus (data bus) Parity Errors.!i@pi @pi  24. Total Retries (HARD and SOFT)1i!@p@pi"  Time:  2-Mar 10:31:28  TO 9-Mar 03:50:41  Span: 161:19:13z	i-@pi+9^3.1.2.1.5.6.A.i.G-Qi0hi1
ai:@p!i2Threshold - One or more (drive detected) Massbus (data bus) parityiC@p#i;errors are required to satisfy this theory. The errors must involve the!iK@p"iDsame drive and they must have occurred during data write operations.1iM@p9iR@piNMBox/UBA    RHxx  Massbus   DeviceQiS@p!iY@piT write> --- DPE ----------->PAR ---> disk9i[@pi\@p1ie@p$i]Since all Massbus devices check data parity during data write operationsIin@p#ifthis theory applies to RH10, RH11, and RH20 controlled disk subsystems.Yip@piiq@p@pirBackground - Refer to the Massbus (data bus) Introduction.3.1.2.1.6.0.5.6cz	h8@pi}G
yF.T.3.1.2.1.6.0.jxj
aj@p#jThat's it. There are only six Massbus (data bus) parity error theories. )j@pj
Next on the menu are the Read Data Theories.!9j@p"@p
jYour response please:z	j@pj	nR.T.3.1.2.1.5.6.A"qjG-#9j#Pj 
aj(@p#j!STOP - You are moving in a reverse direction through the menu. You are$j/@pj)about to back into the Massbus (data bus) Theories.%	j1@p%x@p
j2Your response please:c!nG-z	j9@pixbyk &ij:G-'j<'(j=
ajE@pj>        Analyze - Disk Subsystem Read Data Error Theories'YjF@p(QjO@p#jGThis set of twelve theories attempt to localize the cause of read data(ijT@pjPerrors. A read data error is defined as:)qjV@p*IjZ@p
jW1.(DCK1-2data.check*aj[@p+!j@pj\2.FER-format error+9ja@p+yjg@pjb 3. HCRC - header cyclic redundancy check,jh@p,qjj@p-	jr@p jkAll read data errors are processed by two independent sets of six-!jz@p"jstheories. The first set of six theories attempt to identify the media.!k@p#j{as the cause of read errors. The second set of six theories attempt to/(@p klocalize the cause of read errors to the circuitry in the drives.z	k@pk
ak@p$kThe Media theories attempt to localize the read data errors to media bad29k%@p"kspots. The theories look for single sector bad spots; circumferential3Ik-@p"k&bad spots (three or more single bad spots in a circumferential line);4Qk6@p#k.and radial bad spots (three or more single bad spots in a radial line).5Yk?@p#k7That is, they are on the same surface and have the same sector address,6ikH@p#k@but they extend across three or more cylinders. The following examples7ykM@pkIillustrate each type of bad spot.9kN@p9QkW@p!kO      sector           	cly 000 <--------49---50---51--------< Hub 9ikZ@p	kX                  :qka@pk[   -----X-----       Radial Bad Spot     4    2    3;)kg@pkb       / \        			Soft Hard Soft <kl@pkh      3  12                        <qkr@pkm     Hard Soft                            =Akx@pks                                      sector>!k{@pky  Single Sector?l@p"k|    Bad Spot             cyl 263-------5----6-----------------cyl 263?1l@p@9l@pl                  Circumferential      7    5@P@pl
                     Bad Spot         Soft Hardz	l@pl11m(3.1.2.1.6.0.B.BlG-BYlBpl
al"@p#lThe following diagram illustrates that errors considered by the SingleC!l+@p#l#Bad Spot Theories are also considered by the Radial Bad Spot Theories,D)l3@p l,but not the Circumferential Bad Spot Theories. Conversely, errorsE1l<@p#l4considered by the Circumferential Bad Spot Theories are also consideredF1lD@p l=by the Radial Bad Spot Theories, but not the Single Bad Theories.GAlE@pHAlI@p
lF          All Read ErrorsHYlM@p	lJlj            !IlQ@plN@p    .!.IQlV@plR        !                  !Jl[@plW    Single Bad      CircumferentialJal`@pl\  Spot Theories    Bad Spot TheoriesK1le@pla        !!L	li@p
ln           Spot TheoriesMYls@pNl{@p#ltNote: Errors that are reported as Single Bad Spots and errors that areN1m@p"l|reported as Circumferential Bad Spots may also be reported as RadialO8@p`Vz	m	@pmBo.,3.1.2.1.6.0.C.PYmG-Qm
Q0m
am@p#mThe following diagram illustrates how the read errors are processed byQam@p#mthe Drive Theories. The errors are processed on a drive by drive basis.Rim!@pSym&@pm"                 All Read ErrorsTm+@pm'             .__________!_________.Tam0@pm,             !                    !U1m5@pm1        Single Head           Multi HeadVm;@pm6        .____!_____.       .______!______.VYmA@pm<        !          !       !      !      !W9mG@pmB      Offset      Not     Odd    Even  CommonXmM@pmH     Corrected   Offset   Head   Head  LogicXymS@pmN               Corrected   !______!______!YYmX@pmT                                  !Z9m^@pmY                            Offset Corrected[	m`@p[imi@p#maNote: If all errors pertain to a single head, and if offset was used to\mq@p#mjcorrect any one of the errors, then the errors will be reported by the]mz@p#mrSingle Head Alignment (offset) Theory. Otherwise, they will be reported^n@p"m{by the Single R/W Head Theory. In addition, errors reported by either_)n
@p#ntheHOdd Head,mEven(Head,torTCommoniLogicsTheoriesswilltalsobe@reported`1n@p!nror.3.1.2.1.6.M.6.05xz	j5@p	n"qs0R.T.3.1.2.1.6.0.C.&Qn chn!
an*@p#n"STOP - You are moving in a reverse direction through the menu. You aredn2@pn+about to back into the Introduction to the Data Error Theories.e!n3@pf @p
n4Yournresponseplease:6s4G-z	n;@pn!
anG@pnA    Analyze - Disk Subsystem Read Data Error Theories MenuhnI@phynL@pnJ 0. IntroductioninN@piInU@pnO 1. Single Drive Radial Bad Spot Theory ............[1.6.1]ian]@pnV 2. Multi  Drive Radial Bad Spot Theory ............[1.6.2]jYnd@pn^ 3. Multi  Drive Single Sector Bad Spot Theory .....[1.6.3]kQnl@pne 4. Single Drive Single Sector Bad Spot Theory .....[1.6.4]lIns@pnm 5. Multi  Drive Circumferential Bad Spot Theory ...[1.6.5]mAn{@pnt 6. Single Drive Circumferential Bad Spot Theory ...[1.6.6]n9o@pn| 7. Single R/W Head Theory .........................[1.6.7]o1o
@po 8. Single Head Alignment Theory ...................[1.6.8]p)o@po 9. Common Read Logic Theory .......................[1.6.9]q!o@po10. Odd  Matrix Module Theory ......................[1.6.10]ro @po11. Even Matrix Module Theory ......................[1.6.11]so(@po!12. Multi  R/W Head Alignment Theory ...............[1.6.12]t	o)@pu@po*Your selection please (topic #):z	o2@po0PYp&3.1.2.1.6.1.uio4G-v)o5v@o7
ao?@p!o8Theory - If a drive reports multiple read data errors, and if thosevqoH@p#o@errors involve the same medium, and if they occur along the same radialwyoQ@p!oIline, then there is a possibility that a radial bad spot (scratch)y	oU@poRis causing the errors.zoV@pzQoX@pzio`@p!oY  Read Data Error - Single Drive Radial Bad Spot Theory ... [1.6.1]{ob@p|	oh@poc    Media ID: PS  may have a radial bad spot at:|!oj@p}	oq@pok     Track    Sector           Cylinder        Hard    Soft}!os@p~oz@pot       12.        2.         5.   to   8.        0.     35.~1o|@p)p@po}    DP020(RP06) was the only drive to detect these errors.Ap@p9p
@pp  365. Total Retries (HARD and SOFT)Qp
@p(@pp TO 9-Mar 03:50:41  Span: 161:19:13z	p@ppuipy3.1.2.1.6.1.A.9pG-ypp
ap$@p#pThreshold - Several combinations of at least 4 Hard and/or at least 11Ap-@p#p%Soft read data errors will satisfy this theory. All error combinations,Ip6@p!p.however, must involve the same drive and medium, and they must haveYp?@p$p7occurred in a radial line.  That is, they must have the same surface andapH@p$p@sector address and extend across multiple (three or more) cylinders. TheqpQ@p#pIreport identifies the medium, the first and last bad spot in the radial	pY@p"pRline, and the total number of hard and soft read errors that occurred
p]@ppZalong the radial line.p_@pYpd@pp`Background - Refer to the Introduction.qpf@p
Ipo@p#pgThe following examples illustrate some of Hard and Soft read data error
apx@p#ppcombinationsthat9thistheory2will.tentativelyidentifyasqaRadialBadq
aq
@p!qExample 1-4. Four or more Hard read errors along a radial line will!q@p qsatisfy this theory. i.e., same drive, medium, surface and sector)q@pqaddress, but multiple (4 or more) cylinder addresses.)q@pq@p1q$@p q       cyl 000 <--------45---46---47---48-------------------< HubIq&@pIq,@pq'                         n    n    n    naq2@pq-                        Hard Hard Hard HardAq3@p!q9@pq4Where n is equal to or greater than one.9q:@pq<@p)q=@pAqE@pq>	cyl 000 <-------15------21-----51---73-------------< HubYqF@pQqJ@p
qG			H3rd    H7rd   H1rd H4h@pS@pqQr3.1.2.1.6.1.C.qqTG-1qVHqW
aq`@p#qXExample12-4.Anycombination!offourormoreHardand/oreleven or moreyqi@p$qaSoft read errors along a radial line will satisfy this theory. i,e,. same	qr@p%qjdrive, medium, surface and sector address, but multiple cylinder addresses.qt@p)qu@pAq}@pqv	cyl 000 <--------49---50---51----------------------< Hub Yq~@pQr@pq			 5    3    7ir@pr			Soft Hard Soft r@p Qr@p ir	@p!@pz	r@pr
ar@p#rExample 3-4. Eleven or more Soft read errors along the same radial line"9r%@p"rsatisfy this theory. (same drive, medium, surface and sector address,#Ir*@pr&but multiple cylinder addresses).$Qr+@p%!r3@pr,	cyl 000 <--------21---22--23----------------------< Hub%9r4@p&1r7@pr5			 1    9    1&Ir;@pr8			Soft Soft Soft&yr<@p'1r>@p'Ir?@p'arG@pr@	cyl 000 <-------134-----178----------301-----------< Hub'yrH@p(qrL@prI			 8	 1	      5)@p
rM			Soft    Soft	     Softz	rT@prR!2w$3.1.2.1.6.1.E.*rUG-*ArW*XrX
ara@p!rYExample4-4. This example illustrates some typical radial bad spot+	rf@prbpatterns thatfthisStheory willSidentify.,rh@p,iri@p-rq@prjcyl@000<--8--------------45--------------------314----->rHub-rs@p.ry@prts'sector, b4t at three or 1ore different cylinder1.1s@prz.2.1.6.2.6Hardz	n7@pSofts2c"             Soft/s@p0	s@p0!s@pscyl 000 <------12-----13----------32--------------207---> Hub09s
R.T.3.1.2.1.6.1.E.fys66Hs7
as@@p#s8STOP - You are moving in a reverse direction through the menu. You are6ysG@psAabout to back into the Single Drive Radial Bad Spot Theory.8sI@p8x@p
sJYour response please:xG-z	sQ@ps-!Jat0&9isRG-:sT:(sU
as^@p#sVTheory - If two or more drives detect read errors, and if those errors:Ysf@p#s_involve the same medium, and if they occur along the same radial line,;aso@p"sgthen there is a good possibility that a radial bad spot (scratch) is<isr@p	spcausing the errors.=qst@p>)su@p>As~@p!sv  Read Data Error - Multi Drive Radial Bad Spot Theory ... [1.6.2]>Ys@p?at@pt    Media ID: PS  may have a radial bad spot at:?yt@p@at@pt     Track    Sector           Cylinder        Hard    Soft@yt@pAqt@pt       12.        2.         5.   to   8.        0.     35.B	t@pCt @pt    DP010(RP04) and other drives detected these errors.Ct"@pD	t'@pt#  200. Total Retries (HARD and SOFT)D!t)@pDx@pt*  Time:  2-Mar 10:31:28  TO 9-Mar 03:50:41  Span: 161:19:13z	t4@pt29iu-$3.1.2.1.6.2.A.F	t6G-FIt7F`t9
atA@p"t:Threshold - Several combinations of at least four Hard and/or elevenGtJ@p#tBSoft read data errors will satisfy this theory. All error combinations,HtS@p$tKhowever, must involve two or more drives, the same medium, and they mustI)t\@p$tThave occurred in a radial line. That is, they must have the same surfaceJ9te@p$t]and sector address and extend across multiple (three or more) cylinders.KItg@pLYto@p#thNote - Errors reported by this theory will also be reported by either:Lqtx@p!tpthe Single Bad Spot Theory, or a  Circumferential Bad Spot Theory.Myty@pOu@p tzThis theory is similar to the Single Drive Radial Bad Spot TheoryOu
@p#u[1.6.1]. The only difference is; this theory looks at all the read dataPu@puerrors, not just those common to a single drive.Q)u@pRu@puBackground - Refer to the Introduction.R)u@pSu"@p#uThe following examples illustrate some of Hard and Soft read data errorSu+@p#u#combinations that this theory will tentatively identify as a Radial BadT(@pz	u1@pu/F	v&3.1.2.1.6.2.B.UQu2G-Vu4V(u5
au>@p!u6ExampleD1-4. Four0ormoreuhardreaderrorsalongauradial0line-willVYuF@p"u?satisfy-this-theory.-i.e., multidrives,thesameYmedium, surface andWauN@puGsector address, but multiple (4 or more) cylinder addresses.XiuO@pYauT@p
u`			  n     n     n     n[qui@pudWhere n is equal to    	 Hard  Hard  Hard  Hard\1um@p
ujor greater than one.]un@p]Qup@p]iuu@puq			DP240 DP140   DP220     DP110^uv@p^Qu~@puw	cyl 000 <---------312--313-----416-------642----------< Hub^iu@p_av@p
v			   3    1       5	  2_x@pv			  Hard Hard    Hard	 Hardz	v
@pv
UQv-&3.1.2.1.6.2.C.avv
av@p$vExample 2-4.  Any combination of four or more hard and/or eleven or moreb	v"@p$vsoft read errors along a radial line will satisfy this theory. i,e,. twocv+@p$v#or more drives, the same medium, surface and sector address, but multipled)v/@p	v,cylinder addresses.e9v0@peqv4@p
v1			DP110 DP140 DP220f	v5@pfAv=@pv6	cyl 000 <--------49----50----51----------------------< HubfYv>@pgQvB@pv?			 1     5     1givE@p	vC			Soft  Hard  Softh!vG@phYvH@phqvM@pvI		      DP240  DP240	   DP060i	vN@piQvV@pvO	cyl 000 <-------21-----25------------128------------< HubiivW@pjav[@p
vX			 4      7	      4jx@p
v\			Soft   Soft	     Hardz	vc@pvaaw3&3.1.2.1.6.2.D.kqvdG-l1vflHvg
avp@p#vhExampleD3-4. ElevenormoreSoftreaderrorspalongwthe same radial linelyvy@p"vqwill satisfy this theory. i.e., two or more drives, the same medium,n	w@pvzsurface and sector address, but multiple cylinder addresses.ow@pp	w@pp!w@p
	cyl 000 <--------21----22----23----------------------< Hubqw@prw@pw			 1     9     1r)w@p	w			Soft  Soft  Softraw@psw@ps1w!@pw		       DP050   DP110	    DP260sIw#@ptw*@pw$	cyl 000 <-------134-----178----------301-----------< Hubt1w,@pu)w/@pw-			 8	 1	      5u@@p
w0			Soft    Soft	     Softz	w7@pw5kqx7&3.1.2.1.6.2.E.v9w9G-vyw:ww<
awD@p!w=Example 4-4. This example illustrates some typical radial bad spotwAwJ@pwEpatterns that this theory will identify.xIwK@py!wM@py9wU@pwNcyl 000 <--8--------------45--------------------314-----> HubyQwV@pzQw]@pwW           4              1                      1ziwd@pw^          Hard           Soft                   Soft{Qwe@p|Awg@p|Ywo@pwhcyl 000 <------12-----13----------32--------------207---> Hub|qwp@p}qww@pwq               4      2           7               5 ~	w~@pwx              Soft   Hard        Soft            Soft~yx@pix@px
@p#xRemember: The errors must have occurred on two or more drives, and at x@p!xthe same medium, surface, and sector address, but at three or more  @pxdifferent cylinder addresses.3.1.2.1.6.3.6.2Az	sM@p	x!R9|	R.T.3.1.2.1.6.2.E.9QxXx 
ax)@p#x!STOP - You are moving in a reverse direction through the menu. You are	x0@px*about to back into the Multi Drive Radial Bad Spot Theory.x2@p@p
x3Your response please:A|G-z	x:@pxv9y&yx;G-!x=8x>
axG@p#x?Theory - If two or more drives detect read errors, and if those errorsixO@p!xHinvolve the same medium, cylinder, surface and sector address, thenqxX@p#xPthere is a good chance that the errors were caused by a bad spot on the	yxZ@pb	x[@p!x]@p9xe@p!x^  Read Data Error - Multi Drive Single Bad Spot Theory ... [1.6.3]Qxg@p
Yxn@pxh    Media ID: SUPT  may have a single bad spot at LBN 701620
qxp@p    Track     Cylinder    Sector    Hard    Softxx@pix~@pxy        0.         606.        8.      5.      6.y@piy@py    DP030(RP06) and other drives detected these errors.y@pqy@py	  170. Total Retries (HARD and SOFT)	y@p`@py  Time:  2-Mar 10:31:28  TO 9-Mar 03:50:41  Span: 161:19:13z	y@pyyyy3.1.2.1.6.3.A.qyG-1yHy
ay(@p!y Threshold - Any combinations of at least four Hard and/or at leastyy0@p y)eleven Soft read data errors will satisfy this theory. The errory8@p"y1combinations, however, must involve two or more drives, and they mustyA@p$y9pertain to the same medium, cylinder, surface, and sector. The following	yG@pyBexamples illustrate the combinations.yH@pqyQ@p"yINote: Errors that are reported by this theory will not be reported by	yY@p#yRthe Single Drive Single Bad Spot Theory, but they may be reported by ay]@pyZRadial Bad Spot Theory.y_@pYyd@py`Background - Refer to the Introduction.qyf@pIyo@p#ygThe following examples illustrate some of Hard and Soft read data errorayx@p#ypcombinations that this theory will tentatively identify as a Radial Badp@pmz	y}@py{qz@3.1.2.1.6.3.B.yG-Yzpz
az
@p"zExample 1-3.mFourdormmoreHardreaderrors-willXsatisfycthisutheory.-!z@p"zTheerrors must involve two or more drives, and theymustQpertainto!)z@pzthe same medium, cylinder,asurface,andsector'address."1z@p#!z@p#9z#@pzz	zD@pDP120{&&3.1.2.1.6.3.C.DP270#Qz'@p(AzG(XzH
azQ@p!zIExamples2-3.mAnyumixtureaoffourorzmore-Hard-and/orcelevenforemore)	zY@p#zRSoftread errors will4satisfy this theory. The errors/must@involvetwo*zb@p"zZor more drives, and theyfmustapertaintotheAsamepmedium,cylinder,+zf@pzcsurface,andsectoraddress.,!zh@p,izn@pzi            DP220                      DP140-zr@p
a{7@p#{/Examples3-3.mElevenormoreSoftread	errorsXwill-satisfyuthisetheory.5i{?@p"{8Theerrors{mustinvolve two or more drives, and they must pertainto6q{F@p{@the same medium, cylinder, surface, andfsectorhaddress.7y{H@p8i{I@p9{O@p{JP110.a|DP120A`DP230=!{t@DP2709{T@p
a|@p#|STOP - You are moving in a reverse direction through the menu. You areB|!@p|about to back into the Multi Drive Single Bad Spot Theory.C|"@pD@p
|#Your response please:g~=G-z	|*@p|4a}
&E|,G-E)|-E@|/
a|7@p!|0Theory - If a drive detects multiple read data errors, and if thoseEq|@@p!|8involve the same medium and the same cylinder, surface, and sectorFy|H@p"|Aaddress, then there is a good chance that the errors were caused by aH|L@p|Ibad spot on the medium.I	|N@pII|O@pIa|X@p!|P  Read Data Error - Single Drive Single Bad Spot Theory ... [1.6.4]Iy|Y@pK|a@p|Z    Media ID: SUPT  may have a single bad spot at LBN 701620K|b@pL|i@p|c     Track     Cylinder    Sector    Hard    SoftL)|j@pM|q@p|k        0.         606.        8.      5.      6.M)|r@pN|z@p|s    DP020(RP04) was the only drive to detect these errors.N)|{@pO!}@p||  170. Total Retries (HARD and SOFT)O9}@pP@p}  Time:  2-Mar 10:31:28  TO 9-Mar 03:50:41  Span: 161:19:13z	}@p}
E}f3.1.2.1.6.4.A.Q!}G-Qa}Qx}
a}@p"}Threshold - At least 4 Hard or 11 Soft read data errors are requiredR)}$@p#}to satisfy this theory. All of the errors must involve the same medium,S1}-@p#}%cylinder, surface, and sector address. In addition the errors must haveTA}4@p}.occurred while the medium was mounted on the same drive.UQ}6@pVI}>@p#}7Note: Errors reported by this theory will not be reported by either ofVa}G@p#}?the Circumferential Bad Spot Theories, but they may be reported by oneWi}K@p}Hof the Radial Bad Spot Theory.Xq}M@pY9}R@p}NBackground - Refer to the Introduction.YQ}T@pZ)}\@p!}UThe following example illustrates some of Hard and Soft read errorZA}d@p }]combinations that this theory will tentatively identify as single[H@pdz	}j@p}hQ!~W$3.1.2.1.6.4.B.\a}kG-]!}m]8}n
a}v@p}oExample 1-1. At least four Hard, or at least eleven Soft errors]i}~@p }wwill satisfy this theory. The errors must involve the same drive^i~@p$}and they must pertain to the same medium, cylinder, surface, and sector._i~	@p`y~
@p~
            DP120a~@paI~@p~	 -----X-----  aa~@pb~@p~              4  b)~@p~             Hardba~@pc~@pc1~"@p~            DP110                      DP230cI~$@pd)~)@p~%	 -----X-----  		    -----X-----dA~*@pfe~0@p~+             11                        3  12e(@p~1            Soft                     Hard Soft3.1.2.1.6.5.6.4 0z	|&@p	~;A;R.T.3.1.2.1.6.4.B.Di~?gX~@
a~I@p#~ASTOP - You are moving in a reverse direction through the menu. You areh	~P@p~Jabout to back into the Single Drive Single Bad Spot Theory.i~R@pj@p
~SYour response please: :@G-z	~Z@p~6\aA&jy~[G-k!~]k8~^
a~g@p"~RTheoryt- Ifrtwo-orumoreDdrivesidetectrreadadataderrors,handyif[thoseki~o@p"~herrorsinvolvethe samedmedium,Scylinder,hand surfacemaddress,landdiflq~x@p$~ptheyiinvolveadjacent sectoraddresses,athen thereiisea good chancetthatmy@p!~ytheserrorsarecaused)bypacircumferential bad spot6on.the medium.o	@pp@pp)u1@p+    DP020(RP06) and other drives detected these errors.u)3@pv8@p4  80. Total Retries (HARD and SOFT)v19@pw@p:  Time:  2-Mar 10:31:28  TO 9-Mar 03:50:41  Span: 161:19:13z	E@pCjz3.1.2.1.6.5.A.xFG-xQHxhI
aR@p#JThreshold - Several combinations of Hard and Soft read data errors willy[@p"Ssatisfy this theory. All combinations, however, must involve the samez)b@p\medium, adjacent sector addresses, and two or more drives.{1d@p|)l@p#eNote: Errors reported by this theory will not be reported by either of|Au@p"mthe Single Bad Spot Theories, but they may be reported by one of the}Iy@p
vRadial Bad Spot Theories.~Qz@p@p{Background - Refer to the Introduction.*@p @p @p The following examples illustrate some of Hard and Soft read data 2@p!
error combinations that this theory will tentatively identify as a  0@p
Circumferential Bad Spot.z
@pxr&3.1.2.1.6.5.B. zG- : P 
b(@p"!Example 1-3. Two or more Hard errors (multi drives, adjacent sectors) ,@p
)will satisfy this theory. 
.@p J1@p	/			 DP120    DP040 b6@p2	                    \ sect / <@p7	cyl 175--------------4----5--------------cyl 175 b?@p=			     n    n JC@p@			    Hard Hard zD@p 2M@p!EExample 2-3. Any combination of Hard and Soft errors (multi drives, JS@pNadjacent sectors) will satisfy this theory. 	RT@p 
2X@pU			DP220    DP140 
J\@pY	                    \ sect / c@p]	cyl 112--------------1----2--------------cyl 112 Jf@pd			     n    n 
2i@pg			    Hard Soft 
bk@pWhere in both examples, n is equal to or greater than one.z
v@pt z["3.1.2.1.6.5.C. *xG- jy {
b@p$|Example 3-3. Eleven or more Soft errors (multi drives, adjacent sectors) 2@p
will satisfy this theory. B	@p 
			DP220    DP140 @p	                    \ sect / R@p	cyl 345--------------8----9--------------cyl 345 @p @p			     10   1  @p			    Soft Soft J!@p #@p &@p	$			 DP110    DP130 2+@p'	                    \ sect / j1@p,	cyl 263--------------5----6--------------cyl 263 23@p 6@p4			     7    5 0@p7			    Soft Hard3.1.2.1.6.6.6.5 Gz	~V@p	=g:R.T.3.1.2.1.6.5.C.jbA C
bK@p#DSTOP - You are moving in a reverse direction through the menu. You are 2T@p!Labout to back into the Multi Drive Circumferential Bad Spot Theory. :U@p @@p
VYour response please: G">G-z
]@p9 *E& 2_G- Z` pb
bj@p!cTheory - If a drive detects multiple read data errors, and if those "s@p"kerrors involve the same medium, cylinder, and surface address, and if *|@p$tthey involve adjacent sector addresses, then there is a good chance that 2@p!}the errors are caused by a circumferential bad spot on the medium. B@p  J@p  b@p$  Read Data Error - Single Drive Circumferential Bad Spot Theory [1.6.6]  z@p "
@p"    Media ID: SUPT  may have a circumferential bad spot at LBN 701620 ""@p #*#@p     Track     Cylinder         Sector         Hard    Soft #B%@p $:,@p&        0.         606.      8.   to     9.      0.     22. $R.@p %J5@p/    DP010(RP06) was the only drive to detect these errors. %b7@p &Z<@p8  120. Total Retries (HARD and SOFT) &r>@p 'H@p?  Time:  2-Mar 10:31:28  TO 9-Mar 03:50:41  Span: 161:19:13z
I@pG 23.1.2.1.6.6.A. (ZKG- )L )0N
bW@p#OThreshold - Several combinations of hard and soft read data errors will )b_@p"Xsatisfy this theory. All combinations, however, must involve the same *rf@p`medium, adjacent sector addresses, and the same drive. +zh@p ,jp@p#iNote: Errors reported by this theory will not be reported by either of -y@p#qSingle Bad Spot Theories but they may be reported by one of the Radial .
|@p	zBad Spot Theories. /~@p /J@p The following examples illustrate some of Hard and Soft read data /b@p!error combinations that this theory will tentatively identify as a  0`@p
Circumferential Bad Spot.z
@p (Zo&3.1.2.1.6.6.B. 2*G- 2j 3
b#@p!Example 1-3. Two or more Hard errors (same drive, adjacent sectors) 32'@p
$will satisfy this theory. 4:)@p 4z,@p	*			 DP120    DP120 51@p-	                    \ sect / 5J7@p2	cyl 175--------------4----5--------------cyl 175 69@p 6z>@p:Where n is equal to          n    n 7C@p?or greater than one.   	    Hard Hard 7bE@p 8:M@p!FExample 2-3. Any combination of Hard and Soft errors (same drives, 8RS@pNadjacent sectors) will satisfy this theory. 9ZU@p ::X@pV			DP220    DP220 :R]@pY	                    \ sect / ;
c@p^	cyl 112--------------1----2--------------cyl 112 ;Re@p <:j@pfWhere n is equal to 	     n    n <P@pkor greater than one.        Hard Softz
s@pq 2*Y$3.1.2.1.6.6.C. =zuG- >:v >Px
b@p$yExample 3-3. Eleven or more Soft errors (multi drives, adjacent sectors) ?@p
will satisfy this theory. @@p @R@p @j@p				DP140    DP140 A@p
	                    \ sect / A:@p	cyl 345--------------8----9--------------cyl 345 B@p Bj@p			     10   1 C@p			    Soft Soft C2 @p Cj!@p D%@p	"			 DP110    DP110 D)@p&	                    \ sect / DR0@p*	cyl 263--------------5----6--------------cyl 263 E1@p F4@p2			     7    5 F@p5			    Soft Hard3.1.2.1.6.7.6.6 \xz
Y@p	< :hR.T.3.1.2.1.6.6.C. @ GhA
bJ@p#BSTOP - You are moving in a reverse direction through the menu. You are HR@p"Kabout to back into the Single Drive Circumferential Bad Spot Theory. I"T@p J(@p
UYour response please: ]lG-z
\@p7 =z>" K]G- KB_ KX`
bi@p"aTheory - If a drive reports multiple read data errors, and if all the L
q@p"jerrors involve the same head, then chances are the head is at fault. Mz@p#rIf, however, offset was used to recover from one or more of the errors, N@p{then it may be that the head is slightly out of alignment. O*@p P"
@p  Read Data Error - Single R/W Head Theory ... [1.6.7] P:
@pRQ*@preports: QB@p    head 10. is common to all R@p    1. Hard and 7. Soft Read Data errors. RZ@p S:"@p  90. Total Retries (HARD and SOFT) SR#@p T"+@p$  Time:  2-Mar 10:31:28  TO 9-Mar 03:50:41  Span: 161:19:13 T:,@p U25@p#-The report identifies the drive, the head, the number of Hard and Soft UH@p#6read errors associated with that head, and the total number of retries.z
B@p@ K3.1.2.1.6.7.A. WbCG- X"E X8F
bO@p!GThreshold - At least 1 Hard or 3 Soft read data errors are required XjW@p"Pto satisfy this theory. If, however, offset was used successfully to  Yr`@p#Xrecover from any of the errors, then the errors will be reported under Zx@pathe single head alignment theory [1.6.8]. 3.1.2.1.6.8.6.7 sz
X@p	j G"R.T.3.1.2.1.6.7.A. Kn ]Ho
bx@p#pSTOP - You are moving in a reverse direction through the menu. You are ]z~@pyabout to back into the Single Head Theory. _@p _`@p
Your response please: s"G-z
@pe Wbp$ `R	G- `z
 a

b@p"a drive reports multiple read data errors, and if all the aB@p"errors involve the same head, then chances are the head is at fault. bJ&@p#If, however, offset was used to recover from one or more of the errors, cR-@p'then it may be that the head is slightly out of alignment. db/@p eZ6@p0  Read Data Error - Single Head Alignment Theory ... [1.6.8] er8@p fj=@p9    DP020 (RP04/SN: 33) reports: gD@p>    head 6. used offset (at least once) to recover from gRJ@pE    no Hard and 6. Soft Read Data errors. hBK@p i"P@pL  90. Total Retries (HARD and SOFT) i:R@p j
Y@pS  Time:  2-Mar 10:31:28  TO 9-Mar 03:50:41  Span: 161:19:13 j"[@p kd@p#\The report identifies the drive, the head that may be out of alignment, k2l@p"ethe number of Hard and Soft errors associated with that head, and the l@@p
mtotal number of retries.z
t@pr `R8
3.1.2.1.6.8.A. n
vG- nJw n`y
b@p#zThreshold - At least 3 Soft errors are required to satisfy this theory. o@p#The errors must pertain to the same head and offset must have been used p"@p
to recover from at least one of the errors.  q2@p r@pBackground - Refer to the Introduction.3.1.2.1.6.9.6.8!z
@p	 ]ZR.T.3.1.2.1.6.8.A. `:  sh!
b*@p#"STOP - You are moving in a reverse direction through the menu. You are t1@p+about to back into the Single Head Alignment Theory. u"2@p v@p
3Your response please:!"^G-z
:@p n
@, w<G- w*= w@?
bH@p$@Theory - If a drive reports multiple read data errors, and if the errors wrP@p#Iare not local to a single head or one of the head matrix modules, then yX@pQchances are the fault lies in the common read circuitry. z
Y@p {a@pZ  Read Data0Error - Common Read Logic Theory....![1.6.9]{b@p|j@pc.    DP000 (RP06/SN: 21) reports2random Read Data.errorson:p|*k@p }"t@p!l      0.Head No.     Hard Errors     SoftErrors@pTotal Retries.}:u@p ~B}@pv  3.       4.     6.!r(0.p!r01.)  Time:2.a~Z@p~ 9-Mar 03:56.41  Span: 161:10.13!         1.              2. Z
1@p!:@p#2The report identifies drive and the number of Hard errors, Soft errors,!@p;and retries associated with each head.z
D@pB wn93.1.2.1.6.9.A.!EG-!BG!XH
bQ@p#IThreshold - At least 2 read errors are required to satisfy this theory.!	@pRThe errors must involve both odd and even heads.3.1.2.1.6.10..9!  z
6@p	\ s"R.T.3.1.2.1.6.9.A. vj`!ha
bj@p#bSTOP - You are moving in a reverse direction through the menu. You are!
p@pkabouttoback into the Common Read Logic Theory.!
sYour response please:! *
G-z
z@pW*	h&!z{G-!"}!8~
b	@p"Theory - If a drive reports multiple read data errors, and if all the!j	@p$	errors involve either odd or even heads, then chances are the respective!r	@p	head matrix module has something to do with the errors.!	@p!r	@p!
	"@p	  Read Data Error - Odd Head Matrix Module Theory ... [1.6.10]!"	#@p!"	+@p 	$     DP140 (RP06/SN: 451) reports read errors on odd heads only.!:	-@p!:	5@p!	.        Head No.     Hard Errors     Soft Errors     Total Retries!R	7@p!Z	?@p	8           9.               0.             20.            100.!r	G@p	@          13.               0.              4.             17.!r	O@p	H          17.               0.             18.             68.!r	P@p!r	X@p	Q  Time:  2-Mar 10:31:28  TO 9-Mar 03:50:41  Span: 161:19:13!
	Y@p!	b@p!	ZThe report identifies the drive and the number of Hard errors, Soft!@p	cerrors, and retries associated with each head.z
	l@p	j!z
 3.1.2.1.6.10.A.!
	nG-!J	o!`	q
b	y@p#	rThreshold - At least two read data errors are required to satisfy this!@p	ztheory. The errors must involve two or more odd heads.3.1.2.1.6.11..1!5(z
v@p	
6+R.T.3.1.2.1.6.10.A.!b
! p


b
@p#
STOP - You are moving in a reverse direction through the menu. You are!!"
@p
about to back into the Odd Matrix Module Theory.!"*
@p!#@p

Your response please:!52/G-z

"@p
!
&!$
$G-!$*
%!$@
'
b
/@p"
(Theory - If a drive reports multiple read data errors, and if all the!$r
8@p$
0errors involve either odd or even heads, then chances are the respective!%z
?@p
9head matrix module has something to do with the errors.!'

A@p!'z
B@p!(
J@p
C  Read Data Error - Even Head Matrix Module Theory ... [1.6.11]!(*
L@p!)*
T@p 
M     DP140 (RP06/SN: 451) reports read errors on even heads only.!)B
U@p!*B
^@p!
V        Head No.     Hard Errors     Soft Errors     Total Retries!*Z
_@p!+b
g@p
`           8.               0.             20.            100.!+z
o@p
h          12.               0.              4.             17.!,z
w@p
p          16.               0.             18.             68.!-z
y@p!.z@p
z  Time:  2-Mar 10:31:28  TO 9-Mar 03:50:41  Span: 161:19:13!/@p!0

@p!The report identifies the drive and the number of Hard errors, Soft!0 @perrors, and retries associated with each head.z
@p!$H3.1.2.1.6.11.A.!2G-!2R!2h
b"@p#Threshold - At least two read data errors are required to satisfy this!3@p#theory. The errors must involve two or more even heads.3.1.2.1.6.12..1!Oz

@p	-!1*2.1.6.11.A.!#j1!5x2
b;@p#3STOP - You are moving in a reverse direction through the menu. You are!6*A@p<about to back into the Even Matrix Module Theory.!72C@p!8@p
DYour response please:!O
}G-z
K@p(!2
V.!9
LG-!92N!9HO
bX@p#PTheory - If a drive reports multiple read data errors involving two or!9za@p#Ymore heads, and if offset was used in the recovery process, then there !;i@p bis a possibility that those heads are slightly out of alignment.!<j@p!=r@pk  Read Data Error - Multiple Head Alignment Theory ... [1.6.12]!=*t@p!>*|@p u     DP000 (RP06/SN: 21) reports offset was used (at least once)!>B
@p }     to recover from errors associated with the following heads:!?B
@p!@B
@p!
        Head No.     Hard Errors     Soft Errors     Total Retries!@Z
@p!Ab
@p
           8.               0.              2.              7.!Az
@p
          10.               0.              3.              6.!Bz
'@p
           16.               0.              4.              8.!Cz
)@p!Dz
1@p
*           3.               0.              3.              6.!E
9@p
2           5.               0.              2.              4.!F
:@p!G
B@p
;  Time:  2-Mar 10:31:28  TO 9-Mar 03:50:41  Span: 161:19:13!G*
C@p!H"
L@p!
DThe report identifies the drive and the number of Hard errors, Soft!H:
T@p!
Merrors, and retries associated with each head that used offset for!I@@phz
Z@p
X!9	sN3.1.2.1.6.12.A.!Jb
[G-!K"
]!K8
^
b
g@p"
_Threshold - At least 2 Soft read data errors are required to satisfy!Kj
p@p#
hthis theory. The errors must involve at least two heads and offset must!Lp@p
qhave been used successfully in the recovery process.3.1.2.1.7.0.6.1!c@z
G@p
{2<F.T.3.1.2.1.7.0.!8r
!OX
b@p"t. There are only twelve Read Data Theories. Next on the menu!P
@p
areptheChannelError Theories.!Q
ur response please:z
@p	R.T.3.1.2.1.6.12.A.!R:
b@p#ouaareimovingeineadreversehdirectionthrough the menu. You are!SJ
ur response please:!cJ!G-z
4@p
vg"!V"
b@pAnalyze!-DisksSubsystemeChanneleErrors!Wouritheories!XZl!ZZ@p@p errors that occur with the Overrun bit being the only other error!aZ@p
bit set in the CONI.!bX@p3.1.2.1.7.M.7.0"(z
0@p!"+R.T.3.1.2.1.7.0.!V
"!d$
b,@p#%STOP - You are moving in a reverse direction through the menu. You are!dB4@p-about to back into the Introduction to the Channel Theories.!eJ5@p!f@@p
6Your response please:"2/G-z
=@p"^jv"!g2?G-!gZ@!gpB
bI@pC      Analyze - Disk Subsystem Channel Error Theories!h"J@p!iM@pKTopic Menu:!i*O@p!iZR@pP 0. Introduction!irT@p!j*[@pU 1. Read Operation/RH Controller Theory ......... [1.7.1]!jB]@p!k:d@p^ 2. Read Operation/MBox (UBA) Channel Theory .... [1.7.2]!kRf@p!lJm@pg 3. Write Operation/RH Controller Theory ........ [1.7.3]!lbo@p!mZv@pp 4. Write Operation/MBox (UBA) Channel Theory ... [1.7.4]!mrx@p!nj@py 5. Overrun Only Channel Theory...................[1.7.5]!o@p!ox@pYour selection please (topic #):z

@p!V"|&3.1.2.1.7.1.!pbG-!q"
b@p"Theory - If two or more disk subsystems report channel errors during !qj@p"data read operations, and if there are no error bits set in the drive!rr(@p# error register (DRER1), then chances are the fault lies in the MBox (or!sz1@p$)UBA), the channel, or the Channel Bus. If, however, the errors are local!u
:@p#2to one subsystem, then chances are the fault lies in the controller or!v?@p;the Channel Bus interface logic.!w"@@p!wrH@p A  Channel Error - Read Operation/RH Controller Theory ... [1.7.1]!x
J@p!y
Q@pK 54. RHtNo:r3.rreports:!(duringDataReadoperations)!y"R@p!zY@pSr 03:50:12. (Hard)1and1no1(Soft)hchannelerrors.!z*]@phe report identifies the RH controller on the channel and the number of!}y@p"rHard channel errors, Soft channel errors, and retries associated with!~@pzthe channel.z
@p~!pbH
3.1.2.1.7.1.A.!JG-"
" 
bp Threshold - At least 1 Hard or 6 Soft channel errors are required"R@p to satisfy this theory. The errors must have occurred during data"R@p"read operations and the drive error register must be clear (no error"R @pbits set). "Z"@p"@p#Background - Refer to the Channel Error Introduction.3.1.2.1.7.2.7.1"z
9@p	-!cJqR.T.3.1.2.1.7.1.A.!g1"x2
b;@p#3STOP - You are moving in a reverse direction through the menu. You are"*A@p<about to back into the Channel Read RH Theory."2C@p"@p
DYour response please:"vG-z
K@p(!J=$"	
LG-"	2N"	HO
bX@p"PTheory - If two or more disk subsystems report channel errors during "	z`@p"Ydata read operations, and if there are no error bits set in the drive"i@p#aerror register (DRER1), then chances are the fault lies in the MBox (or"
r@p$jUBA),ntheuchannel, orethehChannelrBus.eIf,uhowever,itheherrorsrareelocal"@p|the Channel Bus interface logic."2@p"
@p#  Channel Error - Read Operation/MBox (UBA) Channel Theory ... [1.7.2]"@p""@p!
       2. different channels report: (during Data Read operations)":@p       no (Hard) and 7. (Soft) channel errors."B@p
       40. total retries."* @p"j'@p!  Time:  2-Mar 10:31:28  TO 9-Mar 03:50:41  Span: 161:19:13")@p"z1@p"*The report identifies the number of channels, the number of Hard and":@p"2Soft channel errors, and the number of retries associated with either"@p;the MBox or UBA.z
A@p?"	

3.1.2.1.7.2.A."ZCG-"D"0F
bN@p"GThreshold - At least 1 Hard or 6 Soft channel errors are required to"bW@p"Osatisfy this theory. The errors must involve two or more controllers"j_@p"Xand they must have occurred during data read operations. In addition,"rg@p`the drive error register must be clear (no error bits set)."zh@p"p@piBackground - Refer to the Channel Error Introduction.3.1.2.1.7.3.7.2"6`z
G@p	s"26R.T.3.1.2.1.7.2.A."rw"`y
b@p#zSTOP - You are moving in a reverse direction through the menu. You are"@pabout to back into the Channel Read MBox (UBA) Theory." 
@p"!@p
Your response please:"6j;G-z
@po"Z&"!zG-"""""8
b@p"Theory - If two or more disk subsystems report channel errors during""j'@p# data write operations, and if there are no error bits set in the drive"#r0@p#(error register (DRER1), then chances are the fault lies in the MBox (or"$z9@p$1UBA), the channel, or the Channel Bus. If, however, the errors are local"&
B@p#:toeoneusubsystem,ethenchancesparethe"fault@liesinIthehcontrollerror"'F@peration/RH Controller Theory ... [1.7.3]")R@p"*
Y@pS    RH No: 3. reports: (during Data Write operations)"*"_@pZ       21. (Hard) and 0. (Soft) channel errors."+c@p
`      120. total retries."+ze@p",:l@pf  Time:  2-Mar 10:31:28  TO 9-Mar 03:50:41  Span: 161:19:13",Rn@p"-Jw@p$oThe report identifies the RH controller on the channel and the number of"-b@p"xHard channel errors, Soft channel errors, and retries associated with".r@pthe channel."/x@pz
@p"!zT
3.1.2.1.7.3.A."0B	G-"1"1

b@p"At least 1 Hard or 6 Soft channel errors are required to"1J@p#satisfy this theory. The errors must pertain to the same channel, they"2R&@p"must have occurred during data write operations, and the drive error"3Z,@p'register must be clear (no error bits set)."4b-@p"5@@p.Background - Refer to the Channel Error Introduction.3.1.2.1.7.4.7.3"OHz
@p	8"}R.T.3.1.2.1.7.3.A."!b<"70>
bF@p#?STOP - You are moving in a reverse direction through the menu. You are"7bM@pGabout to back into the Channel Write RH Theory."8jN@p"9P@p
OYour response please:"ORG-z
V@p4"0BI$":BXG-":jY";[
bc@p"\Theorys-iIfetwocormore@disk subsystems report channel errors during";2l@p#ddata write operations, and if there are no error bits set in the drive"<:u@p#merror register (DRER1), then chances are the fault lies in the MBox (or"=B~@p$vUBA), the channel, or the Channel Bus. If, however, the errors are local">R@p#to one subsystem, then chances are the fault lies in the controller or"?b@p
@p"A2@p#Operation/MBox (UBA) Channel Theory ... [1.7.4]"AJ@p"BZ@p!       2. different channels report: (during Data Write operations)"Br&@p        9. (Hard) and 0. (Soft) channel errors."Cz*@p
'      40. total retries."Db+@p"E"3@p,  Time:  2-Mar 10:31:28  TO 9-Mar 03:50:41  Span: 161:19:13"E:4@p"F2=@p"5The report identifies the number of channels, the number of Hard and"FJE@p">Soft channel errors, and the number of retries associated with either"GP@pFthe MBox or UBA.z
M@pK":B
3.1.2.1.7.4.A."ING-"IRP"IhQ
bZ@p"RThreshold - At least 1 Hard or 6 Soft channel errors are required to"Jb@p"[satisfy this theory. The errors must involve two or more controllers"K"k@p#cand they must have occurred during data write operations. In addition,"L*r@plthe drive error register must be clear (no error bits set)."M2t@p"N(@puBackground - Refer to the Channel Error Introduction.3.1.2.1.7.5.7.4"g8z
R@p	"6jXR.T.3.1.2.1.7.4.A.":*"P
bp#STOP - You are moving in a reverse direction through the menu. You are"PH@pabout to back into the Channel Write/MBOX Theory."gB@G-z
@pz"Iv$"RRG-"Rz"S
b$@p# Theory-If disk subsystem(s) report channel errors and the Overrun Bit"SB-@p"% is the only other error bit set in the CONI register, with no error"TJ6@p#. bits set in the drive error register (DRER1), it could be the hardware"UR;@p7 configuration or a heavy system load."Vb=@p"W:?@p>PACKET 13."WRA@p"WzG@pB  Channel Error - Overrun Only Theory ... [1.7.5]"XI@p"XzQ@pJ       3. channel errors occurred with only the overrun bit set"YV@pR       3. hard and 0. soft errors."ZZ@p
W     236. total retries."Zb[@p"["]@p"[:e@p^  Time: 04-FEB 15:57:56  TO  04-FEB 23:24:04   Span:   7:26:08"[Rf@p"\Ro@p$g The report gives the total number of channel errors, the amount of each"\h@pp type (hard or soft) and how many retries there were.z
z@px"RR;3.1.2.1.7.5.A"^j|G-"_*}"_@
b@p$ Threshold - At least one hard or five soft channel errors must occur to"_r@p$	 fulfill this theory.  It will only be called out when the overrun bit is"a@p$ the only other error bit set in the CONI register and there are no error"b @p bits set in the Drive Error register (DRER1)."c""@p"d
+@p$# Background - When a system has a bad hardware configuration or the load"d"4@p&, gets extremely heavy, an overrun condition may result.  This condition will"e0@p5 set the channel error bit in the CONI.3.1.2.1.8.1.7.5#'xz
@p>!O@F.T.3.1.2.1.8.1."R:B"hC
bL@p#DThat's it. there are only five Channel Error Theories. Next on the menu"h:R@pMis the Head Select/Header Compare Theory."iJT@p"j(@p
UYour response Please:z
\@p	Z"ORSR.T.3.1.2.1.7.5.A."k^G-"kJ_"k`a
bi@p#bSTOP - You are moving in a reverse direction through the menu. You are"lo@pjabout to back into the Channel Theories."mp@p"mp@p
qYour response please:#(DG-z
x@p9!g2^""nbzG-"o
{"o }
b@p$~Theory - If a drive reports Header Compare Errors, and if the drive does"oR@p!not report Header CRC errors at the same time, then chances are the"pb@p#fault lies in the drive and to do with the head select circuitry or the"qj@p
header compare logic."rz@p"s:$@p  HCE Error - Head Select/Header Compare Theory ... [1.8.1]"sR&@p"tJ+@p'     DP030(RP06/SN: 21) reports:"tb2@p,     30. Header Compare Errors without Header CRC errors."u24@p"v*<@p 5        Media    Cylinder    Track    Sector    Errors    Retries"vB=@p"wBE@p >        ADCO1        0.        14.      15.        5.        20."wZM@p F        OPER2      230.        11.      13.       10.       160."xZU@p N        XRAY3       20.        12.       1.       15.        50."yZW@p"zX@pX  Time:  2-Mar 10:31:28  TO 9-Mar 03:50:41  Span: 161:19:13z
b@p`"nb~*3.1.2.1.8.1.A."{jdG-"|*e"|@g
bo@p"hThreshold - There are no thresholds associated with this theory. The"|rx@p#ptheory produces a report for every drive that detects an HCE error with"}z@p#yout an HCRC error. The report identifies the drive, the media addresses"
	@pthat were involved, and the number of HCE errors that occurred.#@p#@p$
Background - Before a data read or a data write operation can begin, the#2@p#header read by the drive must match the header address specified by the#B$@pread or write command. Thus, there are three possibilities.#R&@p#J/@p#'   1. A sector compare occurs, the header is read, a match takes place,#b4@p0      and the operation begins.#r5@p#B>@p#6   2. A sector compare occurs, the header is read but information (bits#ZG@p#?      in the header) are picked up or dropped. This will cause a Header#jP@p$H      CRC error (HCRC). Note: Under these circumstances (if the drive is#zY@p$Q      at the correct FCO level) Header Compare Error (HCE) will not set.#

[@p#c@p#\   3. A sector compare occurs, the header is read without error, but a#2l@p#d      match between the header read by the drive and the header address#
:u@p#m      specified byHtheereadmorrwriteocommand failsutoaoccur.rThis will#.z
@p"{j
,3.1.2.1.8.2.#bG-#"#8
b@p"Theory - If a drive detects Header Compare Errors without HCRC errors#j@p!and there are several errors on the same track, but scattered over #r @p#several cylinders, it could be a bad head or bad media.  Check for Read#z&@p!Data Errors for further media analysis.#
'@p#b)@p#z/@p*  HCE Error - Head or Media Theory ... [1.8.2]#1@p#z6@p2     DP210 (RP06/SN: 770) reports:#=@p7     7. Header Compare Errors without Header CRC errors.#b?@p#ZG@p @        Media    Cylinder    Track    Sector    Errors    Retries#rH@p#rP@p I        ADCO        694.       6.       14.         1.         3.#
X@p Q        ADCO        698.       6.       12.         1.         2.#
`@p Y        ADCO        718.       6.        3.         1.         2.#
h@p a        ADCO        767.       6.        8.         1.         2.#
p@p i        ADCO        771.       6.       15.         1.         3.#
x@p q        ADCO        781.       6.       11.         1.         3.#
@p y        ADCO        794.       6.       10.         1.         2.#
@p# @p  Time: 30-Nov 13:36:37  TO   1-Dec 17:32:32   Span:  27:55:55z
@p
#bs
3.1.2.1.8.2.A.#!"G-#!b#!x
b@p Threshold - If 7 or more errors are found on the same track, this#"*#@p%theory is activated.  The report identifies the drive, the media addresses##*+@p$that were involved, and the number of HCE errors that occurred.#$:-@p#%:5@p".Background - For background on the occurrence of HCE errors refer to#%P@p#6the background descriptions for the Head Select/Header Compare Theory.3.1.2.1.9.1.8.1#Tz
t@pB"gB,F.T.3.1.2.1.9.1."nJF#(HG
bO@pHThat's it. There are only two Header Compare Theories. Next on#(x@p
Pthe menu is Index Theory.z
X@p	U"k!R.T.3.1.2.1.8.1.A.#*:YG-#+[#+\
be@p#]STOP - You are moving in a reverse direction through the menu. You are#+Jl@pfabout to back into the Head Select/Header Compare Theory.#,Rn@p#-H@p
oYour response please:#T%G-z
v@p=#!"N #.:wG-#.by#.xz
b@p"{Theory - If a drive reports IXE (Index Errors), then chances are the #/*@p!fault lies in the drive and is local to the Index Pulse timing and#02@p
control logic.#1:@p#1j@p  IXE Error - Index Pulse Timing Logic Theory ... [1.9.1]#2@p#2z@p     DP030(RP06/SN: 451) reports:#3"@p
     6. Index errors.#3b#@p#4"+@p $        Media    Cylinder    Track    Sector    Errors    Retries#4:-@p#5:5@p .        CRUSH       100.      10.       10.         1.         5.#5R=@p 6        BADP0        20.      12.        3.         2.         6.#6RE@p >        BADP0        25.       8.        2.         3.         9.#7RF@p#8P@pG  Time:  2-Mar 10:31:28  TO 9-Mar 03:50:41  Span: 161:19:13z
R@pP#.9;K3.1.2.1.9.1.A.#9bSG-#:"U#:8V
b_@p"WThreshold - There are no thresholds associated with this theory. The#:jh@p#`theory produces a report for every drive that detects an IXE error. The#;rp@p#ireport identifies the drive and the media addresses that were involved#=w@pqand lists the number of IXE errors that occurred.#>
x@p#>r@pyBackground - Index Error (IXE) means that either:#?
@p#?r@p 1. an index pulse failed to occur at the proper time.#@
@p    (i.e., once per revolution, just before sector 0).#@z@p#Aj@p 2. an index pulse occurred at the wrong time.#B@p    (i.e., during a revolution)#Bj@p#C:&@p$Note: Since index pulses are developed from the media servo track, index#CP@p'errors could also be caused by the media.z
0@p.#(2. F.T.3.1.2.2.0.#EB1G-#F3#F4
b=@p$5Well,tthat'sftheulastlofstheydiskstheories.sTherelareu45kofwthemtinoall.#FJC@p>Nexton#themenu are the tape theories.#GZD@p#H2F@p#HJN@p#GBut, before going on, we would like to remind you that this is a first#HbW@p#Oattempt at writing a program that is designed to help sort and evaluate#Ij`@p#Xthe information in the system event file. In order to succeed, we need#Jzi@p$aall the technical expertise we can get. That's were you come in. You are#Lr@p$jthe people that actually make a living solving computer problems of this#M{@p$stype. Consequently, only you can tell us if these theories make sense or#N"@p#|not. So if you are willing and have the time, we, the Spear team, would#O2
							The Spear Team#R@@pPress the RETURN key to proceed to the Tape Theories.R.T.3.1.2.M.9.1#Wxz
r@p	##*:R.T.3.1.2.1.9.1.A.#."'#TX(
b1@p#)STOP - You are moving in a reverse direction through the menu. You are#U
9@p 2about to leave the tape theories and back into the disk theories.#V:@p#W@p
;Your response please:3.1.2.2.0.#`z
B@p8{#XDG-#X*E#X@G
bO@p!HSTOP - You are moving in a reverse direction thru the menu. You are#XrT@pPabout to back into the Theory Menu.#YzV@p#ZH@p
WYour response please:Control)..z
]@p>92Q
#[2_G-#[Z`#[pb
bi@pced tape subsysteAnalyze.-.Mag.TapexSubsystem Theories#\"j@p#]s@p"kOverview - There are two sets of mag tape subsystem theories. One set#]*{@p"tapplies to TM controlled tape subsystems. The other set applies to TX#^0@p
@p#TR.T.3.1.2.2.0.#`G-#`Z#`p

b@p!STOP - You are moving in a reverse direction thru the menu. You are#a"@pabout to back into the  Mag Tape Theory Overview.#b*@p#c@p
Your response please:z
!@p+K1@#cj"G-#d$#d(%
b+@p&                Analyze - Tape Theory Menu#dZ-@p#e:0@p.Selection Menu#eR1@p#f7@p2 0. Overview - Tape Subsystem Theories#f8@p#fr?@p9 1. TM02/TM03 Theories ... [2.1.1.1] thru [2.1.8.1]#g
A@p#gzH@pB 2. TX01/TX02 Theories ... [2.2.1.1] thru [2.2.8.1]#hI@p#iK@p#i@pLYour selection please (topic #):#sG-z
U@pS#[23.1.2.2.1.0.#jWG-#jZX#jpZ
ba@p[11, RH20,Analyze8-.TM02/TM03@TapeSubsystem@Theories#k"b@p#lk@p#cOverview -pThetTMntape theoriessapply#onlytoTM02/03 tape controllers#l*t@p#lthat drive TU45 and TU77 tape transports. In addition, the TM02/03 tape#m2}@p#utheories are restricted to TMs that are directly connected to either an#nB@p
was performing at the time the error was reported (i.e., Read, Write, or#q8@pY3.1.2.2.1.M.1.0$pz
P@p#` 'R.T.3.1.2.2.1.0.#j#sH
b(@p! STOP - You are moving in a reverse direction thru the menu. You are#sz/@p)about to back into the TM02/03  Tape Theory Overview.#u0@p#up@p
1Your response please:$z ,G-z
8@p+'j[v #vb:G-#w
;#w =
bD@p>                    TM02/TM03 Tape Subsystem Theories#wRE@p#xBH@pFSelection Menu#xZJ@p#y
P@pK 0. Overview - TM02/TM03 Tape Subsystem Theories#y"R@p#z
Z@p!S 1. TM02/03 Read Operation Theories ......[2.1.1.1] thru [2.1.3.1]#z"\@p#{*d@p!] 2. TM02/03 Write Operation Theories .....[2.1.4.1] thru [2.1.6.1]#{Bf@p#|Jn@p!g 3. TM02/03 Massbus Theories .............[2.1.7.1] thru [2.1.7.8]#|bp@p#}jw@pq 4. TM02/03 Control Operation Theories ...[2.1.8.1]#~x@p#~rz@p#@p{Your selection please (topic #):z
 @p #j!
3.1.2.2.1.1.0.#r G-$2 $H 
b @p              TM02/TM03 Read Operation Theories$z @p$b @p" Overview - The TM02/03 Read Operation Theories are based on the type$z  @p" of errors that occur during tape read operations (i.e., Data errors,$@p !Device errors, or Software errors.3.1.2.2.1.1.M.1$hz
4@p	 )#s#R.T.3.1.2.2.1.1.0.#vJ -$@ /
b 7@p! 0STOP - You are moving in a reverse direction thru the menu. You are$r ?@p 8about to back into the TM02/03 Read Operation Theory Overview.$z A@p$x@p
 BYour response please:$r!G-z
 I@p %'B;$j JG-$	 L$	( M
b T@p N             TM02/TM03 Read Operation Theories$	Z U@p$
B X@p VSelection Menu$
Z Z@p$
 `@p [ 0. Overview - TM02/TM03 Read Operation Theories$" b@p$
 k@p# c 1. TM02/03 Read Operation Data Theories ......[2.1.1.1] thru [2.1.1.7]$
" l@p$2. TM02/03Read3Operation DevicepTheoriesS....[2.1.2.1]rthru.[2.1.2.4]$r!@p$h@p!Your selection please (topic #):$3B#!G-$70z
E@p!	#r!b3.1.2.2.1.1.1.0.$R!
b!@p!ead error oTM02/TM03Read!OperationData!Theories$j!@p$R!@p#!OverviewM-aThisPsetrofctheoriesdapplyvonlyctoerrorsthat are directly$j!(@p$! related to reading tape (space forward, space reverse, read forward, and$r!+@p!)read reverse).$!,@p$2!5@p"!-The transport must report the occurrence of a read error without the$J!=@p"!6occurrence of a device error (i.e., the following status bits must be$R!D@p!>zero: DTE, NEF, FCE, NSG, FMT, RMR, ILR, ILF, and OPI).$Z!F@p$J!N@p"!GIn PE recording mode: COR, CS, INC and PEF are considered as evidence$b!S@p
!f@p	!d$r"G"3.1.2.2.1.1.1.0.A.$"!hG-$j!i$!k
b!o@p
!lIn PE recording mode:$2!p@p$r!y@p$!qCOR - Correctable Data Error means that a single dead track was detected$
!@p!zand corrected by the tape subsystem.$"@p$r"	@p!"CS - Correctable Skew means that excessive but correctable skew was$ 
"@p$"
detected. The condition is only a warning and doesn't indicate bad data.$!"@p$"""@p"INC - Incorrectable Data Error means that either:$":"@p$#""!@p" 1. Multiple dead tracks were detected.$#:"(@p"" 2. A dead track was detected without a parity error.$$"/@p") 3. A parity error was detected without a dead track.$%"4@p"0 4. A skew overflow condition occurred.$%r"6@p$&J">@p""7PEF - Format Error means that an incorrect preamble or postamble was$&`@p$"?detected. The condition is only a warning and doesn't indicate bad data.z
"L@p	"I$"$"3.1.2.2.1.1.1.0.B.$(z"MG-$)B"O$)X"P
b"T@p"QIn NRZI recording mode:$*
"V@p$*J"^@p#"W CRC - Cyclic Redundancy Check Error means that the CRC character read$*b"g@p""_ from the tape did not match the CRC character computed from the data$+j"j@p
"hread from thedtape.$,r"l@p$-*"u@p$"m$LRC-@LongitudinalRedundancy Check meanscthatatheyreadoafternwritetLRC$-B"}@pi"vrcharacter$didnotmatchLRCtcharacter computed during the write.$.R"~@p$/R#@p#" ITM - Illegal Tape Mark means that characters not legally a tape mark$/j#
#=@p#;&R2l(z
!@p#$z'R.T.3.1.2.2.1.1.1.0.B.$R#"$4#$
b#,@p!#%STOP - You are moving in a reverse direction thru the menu. You are$4B#4@p#-about to back into the Read Operation Data Theory Overview.$5J#5@p$6@@p
#6Your response please:$s'G-$vx3.1.2.2.1.1.1.M.$3#?G-$7Z#@$7p#B
b#H@p#C          TM02/03 Read Operation Data Theories$8"#J@p$9
#Q@p#K 0. Overview - TM02/TM03 Read Operation Data Theories$9"#R@p$:#[@p$#S 1. Read Data Head/Amplifier Theory .......................... [2.1.1.1]$:*#]@p$;:#f@p$#^ 2. Read Data Error Rate Greater Than 1 per Million Transfers  [2.1.1.2]$;R#g@p$<b#p@p$#h 3. Read Data Error Rate Less Than 1 per Million Transfers ....[2.1.1.3]$<z#r@p$>
#{@p$#s 4. Read Data Error Summary by Data Track .....................[2.1.1.4]$>"#|@p$?2$@p$#} 5. Read Data Media Bad Spot Theory ...........................[2.1.1.5]$?J$@p$@Z$@p$$ 6. Read Data Error Summary ...................................[2.1.1.6]$@r$@p$B$@p$$ 7. Read Data Media Bad Spot Summary ..........................[2.1.1.7]$B$@p$C*$@p$C@@p$Your selection please (topic #):z
$'@p$$$(z%&(3.1.2.2.1.1.1.1.$D*$(G-$Dr$*$E$+
b$4@p#$,TheoryD-tIfEtherreaderrorjratefora$given data track is greater than$E:$=@p$$5twice the average for all tracks, then chances are the read amplifier or$FB$F@p$$>the read head for that track is at fault. The theory produces a two part$GR$N@p#$Greport. The first part of the report identifies the tape drive and the$Hb$U@p$Onumber of read errors associated with each data track.$Ij$W@p$JZ$]@p$X  Read Data Head/Amplifier Theory ... [2.1.1.1]$Jr$@p$KZ$d@p$`    MT100 (TU77, SN:6742) reports:$Kr$h@p
$r@p"$k                Physical Track / Data Track               NRZI or PE$M"$w@p$s					                  Multi Track$N*%@p!$x    1/5   2/7   3/3   4/P   5/2   6/1   7/0   8/6   9/4    Failures$Nz%	@p$%    ---   ---   ---   ---   ---   ---   ---   ---   ---   --------------$P%@p %
     1.    0.    0.   138.    1.   0.    0.    0.    0.        0.$Q%@p$R%@p$R*%@p#%Note: This theory only applies to TOPS-20 because TOPS-10 does not keep$R@@p$%track of the number of frames read per Tape drive. See Theory [2.1.1.4].z
%*@p	%($D*&,"3.1.2.2.1.1.1.1.A.$Tb%,G-$U*%-$U@%/
b%8@p$%0The second part of the report lists the time between consecutive errors,$Ur%A@p$%9the number of frames that were read between errors, the track associated$W%J@p$%Bwith the error (when possible), the media that was mounted, the user ID,$X%M@p	%Kand the program ID.$Y"%Q@p%NTime Between    $YZ%Y@p"%RConsecutive     Number of     Track    Media        User      Program$Z%b@p!%ZRead Errors     Frames Read  in Error   ID           ID         ID$[%j@p#%c------------    ----------  --------  ------    -----------   --------$\"%s@p"%k   0:00:25        2562240.      4.    IT7406    500000,,661    TAPE20$]*%{@p"%t   0:02:47       12201760.      4.    IT7406    500000,,661    TAPE20$^2&@p"%|   0:00:00          32640.      1.    IT7406    500000,,661    TAPE20$_:&
@p"&   0:00:0011520.    27200.  IT745.    IT7406,,66500000,,661$aJTAPE20$`B&@p"&1        8978490.      4.    FOO       500000,,605    TAPE20$bR& @p&- - - - - - -$cZ&)@p#&!The report continues to list all read errors associated with the drive.$d@p&*- - - - - - -z
&1@p	&.$Tb'3.1.2.2.1.1.1.1.B.$eJ&2G-$f&4$f(&5
b&>@p#&6Threshold - At least 100 data read errors are required to satisfy this$fZ&F@p"&?theory. The errors must involve the same drive and two or more media.$gb&O@p"&GIn addition, the overall error rate for the drive must be equal to or$hj&X@p#&Pgreater than one error per million frames read. Finally, the error rate$ir&`@p"&Yof at least one data track must be twice the average for all tracks.$k&b@p$l
&k@p$&cNote@-SincethecontentsofBthegCRCnregisterrcannotebeeusedato identify$l"&t@p#&lthefailing track in NRZI mode, this theory applies only to read errors$m2&x@p&uthat occur in PE mode. $nB&y@p$o'@p$&zNote - This theory only applies to TOPS-20 because TOPS-10 does not keep$o'@p$'track of the number of frames read per Tape drive. See Theory [2.1.1.4].$p*'
':@p'7$eJ(8(z
#9@p'$3B)DR.T.3.1.2.2.1.1.1.1.B.$7'$s`'!
b')@p!'"STOP - You are moving in a reverse direction thru the menu. You are$t'0@p'*about to back into the Read Data Head/Amplifier Theory.$u'2@p$v@p
'3Your response please:%B)IG-%@3.1.2.2.1.1.1.2.$rj';G-$w"'=$w8'>
b'G@p$'?This is a two part summary report. The report identifies all tape drives$wj'P@p"'Hthat have a read data error rate that is equal to or greater than one$xz'X@p#'Qerror per million frames read. The first part of the report identifies$z'a@p#'Ythe tape drive and, when possible, the number of errors associated with${
'e@p'beachadatattrack.$|'f@p$|R'o@p$'g'Read Data - ErrorPRatecGreaterkThana1aperaMillion TransfersNR[2.1.1.2]$|j'q@p$}z'v@p'r    MT100t(TU77,kSN:6609)preports:$~'z@p
    1/5   2/7   3/3   4/P   5/2   6/1   7/0   8/6   9/4    Failures%(@p$(    ---   ---   ---   ---   ---   ---   ---   ---   ---   --------------%"(#@p"(    12.   17.   13.    9.    1.    3.    6.    3.   13.          34.%2(%@p%:(&@p%R(/@p#('Note: This theory only applies to TOPS-20 because TOPS-10 does not keep%h@p$(0track of the number of frames read per Tape drive. See Theory [2.1.1.4].z
(=@p	(:$rj)A&3.1.2.2.1.1.1.2.A.%
(>G-%R(@%h(A
b(J@p$(BThe second part of the report lists the time between consecutive errors,%(S@p$(Kthe number of frames that were read between errors, the track associated%	*(\@p$(Twith the error (when possible), the media that was mounted, the user ID,%
:(`@p	(]and the program ID.%J(a@p%
(e@p(bTime Between    %
(m@p"(fConsecutive     Number of     Track    Media        User      Program%
R(v@p!(nRead-Errors-    Frames-Read -in-Error --ID--    -----ID----   --ID%b)@p"(   0:00:25        2562240.      1.    IT7406    500000,,661    TAPE20%j)@p")   0:02:47       12201760.      8.    IT7406    500000,,661    TAPE20%r)@p")   0:00:00          32640.   MULTI    IT7406    500000,,661    TAPE20%z) @p")   0:00:01         111520.      4.    IT7406    500000,,661    TAPE20%))@p")!  41:40:21        8978490.   MULTI    FOO       500000,,605    DUMPER%
),@p)*- - - - - - -%)5@p#)-The report continues to list all read errors associated with the drive.%B)8@p)6- - - - - - -%R)9@p%@p):Background - Refer to the Read Data Theory Overview (topic # 0)z
)f@p)d%
*`$z
'6@p)F$s+cR.T.3.1.2.2.1.1.1.2.A.$vb)J%)L
b)T@p!)MSTOP - You are moving in a reverse direction thru the menu. You are%B)]@p")Uabout to back into the Error Rate Greater Than 1 Per Million Theory.%J)^@p%P@p
)_Your response please:%<2+hG-%Nh3.1.2.2.1.1.1.3.%)hG-%j)i%)k
b)t@p$)lThis is a two part summary report. The report identifies all tape drives%2)}@p$)uthat have a read data error rate that is less than one error per million%B*@p$)~frames read. The first part of the report identifies the tape drive and,%R*@p"*when possible, the number of errors associated with each data track.% b*@p%!j*@p$*  Read Data - Error Rate Less Than 1 per Million Transfers ... [2.1.1.3]%"*@p%#*@p*    MT100 (TU77, SN:6609) reports:%#**#@p
*     10. Read Data Errors.%#z*%@p%$:*-@p"*&                Physical Track / Data Track               NRZI or PE%$R*2@p*.					                  Multi Track%%Z*;@p!*3    1/5   2/7   3/3   4/P   5/2   6/1   7/0   8/6   9/4    Failures%&**D@p$*<    ---   ---   ---   ---   ---   ---   ---   ---   ---   --------------%'2*L@p"*E     0.    0.    0.    0.    0.    0.    0.    7.    0.           3.%(B*N@p%)J*W@p#*ONote: This theory only applies to TOPS-20 because TOPS-10 does not keep%)`@p$*Xtrack of the number of frames read per Tape drive. See Theory [2.1.1.4].z
*d@p	*b%+`$3.1.2.2.1.1.1.3.A.%,*fG-%,J*g%,`*i
b*r@p$*jThe second part of the report lists the time between consecutive errors,%-*{@p$*sthe number of frames that were read between errors, the track associated%."+@p$*|with the error (when possible), the media that was mounted, the user ID,%/2+@p	+and the program ID.%0B+	@p%0z+
@p+
TimeeBetween    %1+@p"+k    Media        User      Program%1J+@p!+Read Errors     Frames Read  in Error   ID           ID         ID%2R+&@p#+------------    ----------  --------  ------    -----------   --------%3Z+.@p"+'   0:00:25        2562240.      8.    IT7406    500000,,661    TAPE20%4b+7@p"+/   0:02:47       12201760.      8.    IT7406    500000,,661    TAPE20%5j+?@p"+8   0:00:00          32640.   MULTI    IT7406    500000,,661    TAPE20%6r+H@p"+@   0:00:01          62560.   MULTI    IT7406    500000,,661    TAPE20%7z+K@p+I- - - - - - -%9+T@p#+LThe report continues to list all read errors associated with the drive.%92+W@p+U- - - - - - -%:B+X@p%:p@p+YBackground - Refer to the Read Data Theory Overview (topic # 0)z
,@p,%,-&z
)b@p+e%B,wR.T.3.1.2.2.1.1.1.3.A.%*+i%=+k
b+s@p!+lSTOP - You are moving in a reverse direction thru the menu. You are%=2+{@p +tabout to back into the Error Rate Less Than 1 Per Million Theory.%>:+}@p%?8@p
+~Your response please:%Nr,{G-3.1.2.2.1.1.1.4%<
,G-%@B,%@X,
b,@p",	This is a summary report. It lists each drive that detected read data%A
,@p",errors and, when possible, identifies the number of errors associated%B,@p
,with each data track.%C,@p%CZ,&@p,   Read Data Error Summary by Data Track ... [2.1.1.4]%Cr,'@p%Db,,@p,(    MT100 (TU77, SN:6742) reports:%Dz,0@p
,-    14. Read Data Errors.%EJ,2@p%F
,:@p",3                Physical Track / Data Track               NRZI or PE%F",?@p,;					                  Multi Track%G*,H@p!,@    1/5   2/7   3/3   4/P   5/2   6/1   7/0   8/6   9/4    Failures%Gz,P@p",I    ---   ---   ---   ---   ---   ---   ---   ---   ---   -----------%I,X@p ,Q     1.    0.    0.   12.    1.   0.    0.    0.    0.        0.%J
,Z@p%K
,b@p,[  Time:  5-Jan 15:56:53  To  5-Jan 16:15:53   Span:   0:19:00 %K",c@p%L",l@p",dNote: This summary applies to TOPS-10 (only) because, unlike TOPS-20,%L8@p$,mTOPS-10 does not keep track of the number of frames read per Tape drive.%ej.3G-%i8z
,@p
,y%<2..
R.T.3.1.2.2.1.1.1.4.%@,}%O8,~
b-@p!,STOP - You are moving in a reverse direction thru the menu. You are%Oj-@p-about to back into the Data Track Summary Description.%Pr-@p%Qb-@p
-Your response please:%Qz-@p%R8@p
-tm_rd_op_media_bs_theoryz
-@p-%<
.(3.1.2.2.1.1.1.5.%S-G-%SZ- %Sp-"
b-*@p!-#If a reel of tape is associated with four or more read errors in PE%T"-3@p"-+mode, or eight or more read errors in NRZI mode, then chances are the%U*-;@p"-4tape has become worn or dirty and should be copied and (if possible)%V2-?@p
-<cleaned and verified.%W:-A@p%Wz-G@p-B  Read Data - Media Bad Spot Theory ... [2.1.1.5]%X-I@p%Xz-P@p-J    Media ID: FICHE   Recording Mode: PE was identified with%Y-W@p-Q    read errors as noted against the following drives:%Z
-Y@p%Zz-_@p-Z    MT100  (TU45, SN: 627)  with 20. errors.%[-c@p
-`      Additional Data%[r-h@p-d        Operation    : READ FWD%\2-m@p-i        User ID      : 500000,,5%]-q@p-n        Program ID   : TAPE20%]R-s@p%^-|@p$-t** If the tape was mounted on multiple drives, then the report will list%^2.@p#-}   each drive that detected read errors associated with that Media ID.%_B.@p%`H@p.  Time:  5-Jan 15:56:53  To  5-Jan 16:15:53   Span:   0:19:00 z
.@p.%S.,3.1.2.2.1.1.1.5.A%ab.G-%b*.%b@.
b.@p .Threshold - In PE mode, at least four read errors are required to%br.'@p . satisfy this theory. In NRZI mode, at least eight read errors are%cp@p.(required to satisfy this theory.z
.N@p.K%ab/F(z
,u@p.0%Nr1R.T.3.1.2.2.1.1.1.5.A.%NR.5%f8.6
b.?@p!.7STOP - You are moving in a reverse direction thru the menu. You are%fj.D@p.@about to back into the Bad Media Theory.%gr.F@p%hH@p
.GYour response please:&z1G-&X3.1.2.2.1.1.1.6.%eB.OG-%ib.Q%ix.R
b.[@p$.SThis report summarizes all read data errors by; drive, medium, recording%j*.d@p$.\mode, error status bit combinations, and the number of times the various%k:.j@p.eerror status bit combinations occurred.%lJ.k@p%m".r@p.l  Read Data - Read Data Error Summary ... [2.1.1.6]%m:.t@p%n*.x@p.uMT100 (TU77, SN:6609) reports:%nB.z@p%o
.~@p.{Media	  Mode	  					 Number of%o"/@p". ID      PE/NRZI  CS/ITM   COR/CRC   PEF/LRC   INC/VPE   Occurrences%oj/@p"/-----    -------  ------   -------   -------   -------   -----------%pr/@p /   unk.      PE       0       0         1         0          11.%qz/@p /   BACK      NRZI     0       0         0         1           8.%rz/'@p /    FICHE     PE       1       0         0         1           3.%sz//@p /(   LOCKE     PE       0       0         1         1           2.%tz/1@p%uz/:@p#/2** The report will continue to list each drive and the associated read %v/<@p/;   errors.%w"/>@p%wH@p/?  Time: 29-Dec 17:40:37  To 29-Dec 19:05:41   Span:   1:25:04 z
/J@p/H%eB03"3.1.2.2.1.1.1.6.A%xb/LG-%y*/M%y@/O
b/W@p"/PBackground -  Four error detectors monitor read data transfers in PE %yr/\@p/Xmode (COR, CS, INC, and PEF):%zz/]@p%{B/f@p$/^COR - Correctable Data Error means that a single dead track was detected%{Z/l@p/gand corrected by the tape subsystem.%|j/m@p%}B/v@p!/nCS - Correctable Skew means that excessive but correctable skew was%}Z/@p$/wdetected. The condition is only a warning and doesn't indicate bad data.%~b0@p%r0@p0INC - Incorrectable Data Error means that either:&
0
@p0 1.aMultipleedeadetracksowere detected.&r0@p00 3. A parity error was detected without a dead track.&:0 @p0 4. A skew overflow condition occurred.&*0!@p&0*@p"0"PEF - Format Error means that an incorrect preamble or postamble was&@p$0+detected. The condition is only a warning and doesn't indicate bad data.z
07@p05%xb1.1.6.B&209G-&z0:&0<
b0E@p$0=Four error detectors monitor read data transfers in NRZI mode (CRC, LRC,&B0H@p0FITM, and VPE):&R0I@p&	0R@p#0J CRC - Cyclic Redundancy Check Error means that the CRC character read&	0Z@p"0S from the tape did not match the CRC character computed from the data&
"0^@p
0[ read from the tape.&*0_@p&b0h@p$0` LRC - Longitudinal Redundancy Check means that the read after write LRC&z0p@p 0i character did not match LRC character computed during the write.&
0r@p&
0z@p#0s ITM - Illegal Tape Mark means that characters not legally a tape mark&"1@p0{ were read and recognized as a tape mark.&*1@p&
1
@p!1 VPE - Vertical Parity Error means that a vertical parity error was& @p1 detected.z
10@p1-&2#,z
.J@p1%ej2NR.T.3.1.2.2.1.1.1.6.B.%i"1&H1
b1 @p!1STOP - You are moving in a reverse direction thru the menu. You are&z1&@p1!about to back into the Read Data Error Summary.&1(@p&h@p
1)Your response please:3.1.2.2.1.1.2.M&@03.1.2.2.1.1.1.7.&R11G-&13&14
b1=@p"15This report summarizes of all media bad spots that do not exceed the &J1E@p!1>threshold established for the Bad Spot Theory [2.1.1.5]. The report&R1N@p#1Fidentifies the medium, the recording mode, the drive, and the number of&Z1W@p"1Oread errors associated with the medium. In addition, the report lists&j1_@p#1Xthe type of read operation, the user ID, and the program ID associated&r1c@p1`with the errors.&z1d@p&21k@p1e  Read Data - Media Bad Spot Summary ... [2.1.1.7]&J1l@p&21t@p1m    Media ID: 7601 Recording Mode: NRZI was identified with&J1{@p1u    read errors as noted against the following drives:&B1|@p&22@p1}    MT404  (TU72, SN: 28411.)  with 1. errors.&J2@p
2      Additional Data& 22@p2        Operation    :READ FWD& r2@p2
        User ID      :500000,,5&!:2@p2        Program ID   :DUMPER&"
2@p&"R2@p$2** If the tape was mounted on multiple drives, then the report will list&"j2(@p#2    each drive that detected read errors associated with that Media ID.&#z2)@pd&%@p2*  Time of Error: 26-Jun 06:29:54 z
23@p
20#EB9F.T.3.1.2.2.1.1.2.0.&%j24G-&&226&&H27
b2@@p#28That's it. There are only 7 Read Operation Data Theories and Summaries.&&z2H@p2ANext on the menu are the Read Operation Device Error Theories.&(
2J@p&)@p
2KYour response please:z
2R@p
2P&z3"R.T.3.1.2.2.1.1.1.7.&)b2TG-&**2U&*@2W
b2_@p!2XSTOP - You are moving in a reverse direction thru the menu. You are&*r2f@p2`about to back into the Read Operation Data Theories.&+z2h@p&,h@p
2iYour response please:z
2p@p2n$343.1.2.2.1.1.2.0.&-B2rG-&.
2s&. 2u
b2|@p2v              TM02/03 Read Operation Device Error Theories&.R2~@p&/J3@p#2Overview - The TM02/03 Read Operation Device Error Theories attempt to&/b3@p!3localize the cause of device errors that occurred during tape read &0j3@p 3operations (space forward, space reverse, read forward, and read&1r3@p 3reverse). Device errors that can not be localized are listed in a&2p@p3 summary report.z
3&@p
3$&)b4cR.T.3.1.2.2.1.1.2.0.&4"3(G-&4j3)&53+
b33@p!3,STOP - You are moving in a reverse direction thru the menu. You are&523;@p34about to back into the Read Operation Device Theory Overview.&6:3=@p&78@p
3>Your response please:&@:4G-z
3E@p1+'	9$ &8*3FG-&8R3H&8h3I
b3P@p3J               TM02/TM03 Read Operation Device Theories&93R@p&:
3U@p3SSelection Menu&:"3V@p&:R3]@p3W 0. Overview - TM02/TM03 Read Operation Device Theories&:j3_@p&;Z3d@p3` 1. Power Supply Theory	.....[2.1.2.1]&;r3f@p&<J3k@p3g 2. Drive Offline Theory ....[2.1.2.2]&<b3m@p&=:3r@p3n 3. OPI Blank Tape Theory ...[2.1.2.3]&=R3t@p&>*3y@p3u 4. Device Error Summary ....[2.1.2.4]&>B3{@p&?3|@p&?0@p3}Your selection please (topic #):&ir6TG-&mXz
3A@p4&-B53.1.2.2.1.1.2.1.&84	&A4
b4@p#4
Theory - If a drive reports an unsafe error condition, and if the frame&A24@p"4counter is nonzero, indicating that a data transfer operation was in&BB4%@p"4progress, then chances are the unsafe condition was caused by a power&CJ4.@p$4&supply failure. If, however, the frame counter is clear, indicating that&DR46@p!4/a data transfer operation was not in progress, then chances are the&Eb4?@p"47Unsafe condition was caused by the software attempting to access the&Fj4C@p4@drive while it was off-line.&Gr4E@p&H:4K@p4F  Read Data - Power Supply Theory ... [2.1.2.1]&HR4M@p&I:4R@p4N    MT100 (TU77, SN:6609) reports:&IR4Z@p 4S    3. Unsafe Errors that are most likely Power Supply failures.&J"4[@p&K @p4\  Time: 29-Dec 18:32:50  To 29-Dec 19:06:07   Span:   0:33:17 z
4h@p
4e&4"5bR.T.3.1.2.2.1.1.2.1.&L:4iG-&M4k&M4l
b4u@p!4mSTOP - You are moving in a reverse direction thru the menu. You are&MJ4|@p4vabout to back into the Read Data Power Supply Theory.&NR4}@p&O@@p
4~Your response please:z
5@p5&@:63.1.2.2.1.1.2.2.&P5G-&Pb5	&Px5

b5@p#5Theory - If a drive reports an unsafe error condition, and if the frame&Q*5@p"5counter is nonzero, indicating that a data transfer operation was in&R:5$@p"5progress, then chances are the unsafe condition was caused by a power&SB5-@p$5%supply failure. If, however, the frame counter is clear, indicating that&TJ56@p!5.a data transfer operation was not in progress, then chances are the&UZ5>@p"57Unsafe condition was caused by the software attempting to access the&Vb5C@p5?drive while it was off-line.&Wj5D@p&X25K@p5E  Read Data - Drive Off-line Theory ... [2.1.2.2]&XJ5L@p&Y25Q@p5M    MT100 (TU77, SN:6609) reports:&YJ5Y@p5R    4. Unsafe Errors that are most likely off-line errors.&Z5Z@p&[@p5[  Time: 29-Dec 18:19:51  To 29-Dec 18:37:03   Span:   0:17:12 z
5g@p
5d&L:6OR.T.3.1.2.2.1.1.2.2.&\*5hG-&\r5j&]5k
b5t@p!5lSTOP - You are moving in a reverse direction thru the menu. You are&]:5{@p5uabout to back into the Read Data Drive Off-line Theory.&^B5|@p&_0@p
5}Your response please:z
6@p6&P6L3.1.2.2.1.1.2.3.&`
6G-&`R6&`h6	
b6@p!6
Theory - If ardrive reportsrOPIerrors6duringread&operations,then&a6@p 6chances(are7theNtape5waseither@blankor was in the.wrong format.&b"6@p&c"6"@p6ReadhData@-OPIBlankiTape Theory1...3[2.1.2.3]&c:6#@p&d"6)@p6$7Media I D: AUG6   was associated with&d:6/@p6*    4. OPI errors on the following drives:&e61@p&ez65@p
6p@p6m&`
7Q&z
4@p6Q&\*9&R.T.3.1.2.2.1.1.2.3.A.&@6U&j@6W
b6_@p!6XSTOP - You are moving in a reverse direction thru the menu. You are&jr6f@p6`about to back into the Read Data OPI Blank Tape Theory.&kz6h@p&lh@p
6iYour response please:'j9+G-'X3.1.2.2.1.1.2.4.&iJ6qG-&n6s&n6t
b6}@p!6uThis report summarizes device errors that occurred during read data&nJ7@p#6~operations. The errors are summarized by drive and  device error status&oR7	@p7bit combinations.&pb7@p&q7@p7
  Read Data - Device Error Summary ...[2.1.2.4]&q27@p&r7@p7  MT100  (TU77, SN: 6609) reports:&r27@p&s7@p7      Error bit		Number  of				  Span&s7&@p7      Combinations	Occurrences        Window	        HH:MM:SS&sr7(@p&tj7,@p7) D  N  F  N  F  R  I  I&u70@p7- T  E  C  S  M  M  L  L&uB74@p71 E  F  E  G  T  R  R  F&v75@p&vB7>@p$76 0  0  0  0  1  0  0  0	   2.  29-Dec 19:05:25_29-Dec 19:06:07   0:00:42&vZ7G@p$7? 0  0  1  0  0  0  0  0	   3.  29-Dec 18:31:57_29-Dec 19:20:19   0:48:21&wj7I@p&xx@p7J  Time: 29-Dec 18:31:57  To 29-Dec 19:20:19   Span:   0:48:21 z
7U@p	7S&iJ8I"3.1.2.2.1.1.2.4.A.&z7WG-&zZ7X&zp7Z
b7b@p7[Background - Eight detectors monitor for TM02/03 device errors:&{"7c@p&|"7l@p"7d DTE - Drive Timing Error means that a data transfer (read or write)&|:7t@p 7m was attempted when the Massbus (data bus) was already occupied.&}B7u@p&~B7~@p!7v NEF - Non Executable Function means that either; a read or a space&~Z8@p#7 reverse operation was issued while at Beginning of Tape (BOT), a space&b8@p!8 operation was issued and the frame count was equal to zero, or the'r8@p$8 phase-lock-loop modules (M8901-YB, YC, YD) do not match the drive type.'z8@p'
8#@p$8 FCE - Frame Count Error means that either; a space operation terminated'"8,@p$8$ with a non-zero frame count, or the drive failed to negate Run when the'280@p8- controller asserted Enable.'B82@p'
8;@p#83 NSG - Non Standard Gap means that a tape character was detected during'"8C@p"8< the first half of the end of record gap. This error condition should'0@p8D only occur during a write operation.z
8M@p	8K&z3B3.1.2.2.1.1.2.4.B.'	8OG-'	Z8P'	p8R
b8Z@p!8S FMT - Format Error means that the format code is not implemented.'
"8\@p'*8d@p!8] RMR - Register Modification Refuse means that a register write was'B8i@p8e attempted when the GO bit was set.'
J8k@p'ILF~-@IllegalvFunctionlmeans thatsanrillegaltfunctiontcodetwassissued.'d or write'X@p8       a non-existent register.z
9@p
9&%j:DF.T.3.1.2.2.1.1.3.1.':9	G-'9'9

b9@p#9here are only  three Read Operation Device Theories and one'J9@p$9Summary Report. Next on the menu is the Read Operation Software Summary.'Z9 @p'h@p
9!Your response please:z
9H@p9E&8* F,z
6l@p9(&ir:cR.T.3.1.2.2.1.1.2.4.B.&mB9-'89.
b97@p!9/STOP - You are moving in a reverse direction thru the menu. You are'j9>@p98about to back into the Read Operation Device Error Theories.'r9@@p'h@p
9AYour response please:3.1.2.2.1.2.0.1'5H3.1.2.2.1.1.3.1.'B9IG-'9K'9L
b9U@p#9MThis report summarizes magtape errors thought to be caused by software.'J9^@p#9VFor example: A Read Reverse operation issued while the tape was at BOT'Z9c@p9_would be considered a software error.'b9e@p':9k@p9fRead Data - Software Error Summary ... [2.1.3.1]'R9m@p':9s@p9n  Note: Error register contents are in octal.'R9t@p'29y@p9uMT100  (TU45, SN: 627) reports:'J9{@p':@p9| Error	    Media   No. of					  SPAN  '2:@p:Register     ID     Errors		Window			HH:MM:SS' 
:@p:--------    -----   ------              ------			--------' j:@p'!b:@p$:     0       unk.     2.  24-Jun 12:37:53 - 24-Jun 12:37:54      0:00:01 '!z:!@p$:     0     6258       2.  25-Jun 00:56:07 - 25-Jun 00:56:08      0:00:01 '#
:*@p$:"     0     9494       2.  25-Jun 01:16:35 - 25-Jun 01:16:36      0:00:01 '$:.@p	:+-------------------'%*:7@p$:/The report continues to list each drive associated with software errors.'%b::@p	:8-------------------'&r:<@p''(@p:=  Time: 24-Jun 12:37:53  To 30-Jun 02:41:49   Span: 134:03:56 z
:H@p	:F':?lF.T.3.1.2.2.1.2.0.'(B:JG-')
:K') :M
b:U@p!:NThat's it. There is only one Read Operation Software Error Summary')R:^@p!:VReport. Next on the menu are the TM02/03 Write Operation Theories.'*Z:_@p'+`@p
:`Your response please:z
:h@p
:e'j;-R.T.3.1.2.2.1.1.3.1.',::iG-'-:k'-:l
b:u@p!:mSTOP - You are moving in a reverse direction thru the menu. You are'-J:}@p":vabout to back into the Read Operation Software Error Summary Report.'.R:@p'/X@p
;Your response please:'5R;1G-z
;@p9C$j<
'0J;G-'0r;
'1;
b;@p;
               TM02/03 Write Operation Theories'1:;@p'2";@p";Overview - The TM02/03 Write Operation Theories are based on the type'2:;$@p";of errors that occur during tape write operations (i.e., Data errors,'3B;)@p;%Device errors, or Software errors.'4H@p3.1.2.2.1.2.M.2'Az
;@p	;/',:<xR.T.3.1.2.2.1.2.0.'02;3'6;4
b;=@p!;5STOP - You are moving in a reverse direction thru the menu. You are'6J;D@p;>about to back into the Write Operation Theory Overview.'7R;E@p'8@@p
;FYour response please:'A
<G-z
;M@p;*(nHK'92;OG-'9Z;P'9p;R
b;X@p;S               TM02/TM03 Write Operation Theories':";Z@p';
;`@p;[ 0. Overview - TM02/03 Write Operation Theories';";b@p'<
;k@p$;c 1. TM02/03 Write Operation Data Theories ......[2.1.4.1] thru [2.1.4.2]'<";l@p'=2;u@p$;m 2. TM02/03 Write Operation Device Theories ....[2.1.5.1] thru [2.1.5.4]'=J;w@p'>Z;~@p;x 3. TM02/03 Write Operation Software Summary ...[2.1.6.1]'>r<@p'?j<@p'@@p<Your selection please (topic #):'f2>8G-'j z
;I@p<
'0J=C$3.1.2.2.1.2.1.0.'9<'AP<
b<@p<           TM02/TM03 Write Operation Data Theories'B<@p'Bj< @p#<Overview - This set of theories apply only to errors that are directly'C<)@p"<!related to writing (write file mark, write check forward, write check'D
<-@p<*reverse, and write forward).'E</@p'EZ<7@p"<0The transport must report the occurrence of a read after write error'Er<@@p"<8without the occurrence of a device error (i.e., the following status'Fz<H@p"<Abits must be zero: DTE, NEF, FCE, NSG, FMT, RMR, ILR, ILF, and OPI).'H<J@p'I
<R@p"<KIn PE recording mode: COR, CS, INC and PEF are considered as evidence'I"<X@p<Sthat a read after write error occurred.'J*<Y@p'K<b@p$<ZIn NRZI recording mode: CRC, LRC, ITM and VPE are considered as evidence'K<h@p<cthat a read after write error occurred.'L*<i@p'M<r@p#<jNote: The meaning of each read (after write) error bit is described in'M@p<sthe TM02/03 Read Operation Data Theory Overview.z
<}@p
<z'5R>3R.T.3.1.2.2.1.2.1.0.'O
<~G-'OR='Oh=
b=
@p!=STOP - You are moving in a reverse direction thru the menu. You are'P=@p=about to back into the Write Operation Theory Overview.'Q"=@p'R@p
=Your response please:z
=@p='y@	3.1.2.2.1.2.1.M.'Rj=G-'S2='SH=
b=%@p= TM02/02 Write Operation Data Theories'Sz=&@p'TR=-@p=' 0. Overview - TM02/02 Write Operation Data Theories'Tj=/@p'UZ=4@p=0 1. Bad Media Theory .........[2.1.4.1]'Ur=6@p'VJ=;@p=7 2. Media Bad Spot Summary ...[2.1.4.2]'Vb==@p'W:=>@p'WP@p=?Your selection please (topic #):z
=H@p=E'A
>"3.1.2.2.1.2.1.1.'X:=IG-'Y=K'Y=L
b=U@p#=MIf a medium is involved in more than 50 (read after write) errors, then'YJ=^@p#=Vchances are the medium is either dirty or worn and should be cleaned or'ZZ=a@p=_replaced.'[j=b@p'\=h@p=c  Write Data - Bad Media Theory ... [2.1.4.1]'\*=j@p']
=o@p=k    Media ID: FICHE was associated with']"=x@p#=p    174. read after write errors while mounted on the following drives:']z=z@p'_
=~@p
={	MT300  (TU45, SN: 431.)'_"=@p'_b>@p
>>Additional Data:'0z>@p'`2>	@p
    Program ID  :DUMPER'a>@p'aP@p>  Time: 14-Jan 15:48:16  To 18-Jan 20:33:03   Span: 100:44:47 z
>@p	>'X:>03.1.2.2.1.2.1.1.A.'bj>G-'c2>'cH>
b>(@p#> Threshold - At least 50 read after write errors are required to satisfy'cx@p >)this theory. All 50 errors must pertain to the same reel of tape.z
>T@p>R'bj?I*z
<@p>5'O
@
R.T.3.1.2.2.1.2.1.1.A.'@j>9'g>;
b>C@p!><STOP - You are moving in a reverse direction thru the menu. You are'g2>K@p>Dabout to back into the Write Operation Bad Media Theory.'h:>L@p'i0@p
>MYour response please:(B@G-((3.1.2.2.1.2.1.2.'f
>VG-'jJ>W'j`>Y
b>a@p#>ZThisNreport summarizes allP(read afterawrite)?dataerrors that didrnot'k>j@p#>bmeet:theSthresholdqestablished?for-the Bad-Media Theory [2.1.4.1]. The'l>r@p">kreport lists-thedrive,@themedium,8and number of-(read0after0write)'m">w@p>serrors#associated3with1theamedium.'n*>y@p'nz?@p>z9 WriteEData't-?MediaBad?Spot1Summary....1[2.1.4.2]'o?@p'p?@p?MT301  (TU70, SN: 0.) reports:'p?@p'pb?
?6@p?3MT302  (TU70, SN: 0.) reports:'v"?8@p'vj??@p?9The report will continue to list all write errors by drive.'w?A@p'wx@p ?B    Time: 11-Mar 00:33:50  To 12-Mar 12:19:06   Span:  35:45:16 z
?M@p	?K'f
=3.1.2.2.1.2.1.2.A.'y?OG-'yZ?P'yp?R
b?Z@p#?SNote: Since rewind operations are not currently recorded in the system'z"?c@p!?[event file some bad spots may have been counted more than once. You'{(@p#?dshould take this into consideration before discarding the reel of tape.z
?p@p
?n'(BFMF.T.3.1.2.2.1.2.2.0.'}B?rG-'~
?s'~ ?u
b?~@p$?vThat's it. There are only two Write Operation Data Theories. Next on the'~R@@p?menu are the Write Operation Device Theories.'b@@p(@@p
@Your response please:z
@-@p@*'RjA:z
>P@p@'f2@aR.T.3.1.2.2.1.2.1.2.A.'j
@(@
b@@p!@STOP - You are moving in a reverse direction thru the menu. You are(B@#@p@about to back into the Write Operation Data Theories.(J@%@p(8@p
@&Your response please:(n*FwG-(r 3.1.2.2.1.2.2.0.(@.G-(R@0(h@1
b@9@p@2              TM02/03 Write Operation Device Error Theories(@:@p(@C@p#@;Overview - The TM02/03 Write Operation Device Error Theories attempt to(*@L@p"@Dlocalize the cause of device errors that occurred during tape write (:@U@p#@Moperations  (write file mark, write check forward, write check reverse,(	B@]@p#@Vand write forward). Device errors that can not be localized are listed(
P@p
@^in a summary report.z
@e@p
@c(BB#R.T.3.1.2.2.1.2.2.0.(
@gG-(
Z@h(
p@j
b@r@p!@kSTOPt-tYouaareimovingeinratreversetdirectionethruothehmenu.OYouvare(*@|@p(0@p
@}Your response please:z
A@pA(bRFp3.1.2.2.1.2.2.M.(
AG-(RA(hA	
bA@pA
            TM02/TM03 Write Operation Device Theories(A@p(
A@pA 0. Overview - Write Device Theories("A@p(zA@pA 1. Power Supply Theory .......[2.1.5.1](A @p(jA&@pA! 2. Drive Offline Theory ......[2.1.5.2] (A'@p(bA-@pA( 3. OPI Write Timing Theory ...[2.1.5.3](zA.@p(RA4@pA/ 4.Device Error Summary .......[2.1.5.4](jA5@p(@@pA6Your selection please (topic #):z
A?@pA<(BB3.1.2.2.1.2.2.1.(*A@G-(rAB(AC
bAL@p#ADTheory-Ifa drive0reports,anNUnsafe errortcondition,pandifboth3the(:AT@p#AMfilerandorecordecounters arepgreateruthanzero,indicating#that@adata(BA]@p"AUtransfer5operationDwas1in0progress,athen chances arethe Unsafe error(JAe@p"A^condition was caused by a power supply failure. If, however, the file(RAn@p"Afand record counters are less than or equal to zero, indicating that a(ZAw@p$Aodata transfer operation was not in progress, then chances are the Unsafe(bA@p!Axcondition was caused by the software attempting to access the drive(rB@pBwhile it was off-line.(zB@p( :B@pB  Write Data - Power Supply Theory ... [2.1.5.1]( RB
B(@p
B%(
C*R.T.3.1.2.2.1.2.2.1.($:B)G-(%B+(%B,
bB5@p!B-STOP - You are moving in a reverse direction thru the menu. You are(%JB<@pB6about to back into the Write Operation Power Supply Theory.(&RB>@p('H@p
B?Your response please:z
BF@pBD(*CI3.1.2.2.1.2.2.2.(("BHG-((jBI()BK
bBS@p#BLTheory - If a drive reports an Unsafe error condition, and if both the()2B\@p#BTfile and record counters are greater than zero, indicating that a data(*:Bd@p"B]transfer operation was in progress, then chances are the Unsafe error(+BBm@p"Becondition was caused by a power supply failure. If, however, the file(,JBu@p"Bnand record counters are less than or equal to zero, indicating that a(-RB~@p$Bvdata transfer operation was not in progress, then chances are the Unsafe(.ZC@p!Bcondition was caused by the software attempting to access the drive(/jC@pCwhile it was off-line.(0rC
@p(12C@pC-line Theory ... [2.1.5.2](1JC@p(22C@pC    MT100 (TU77, SN:6609) reports:(2JC!@pC    4. Unsafe Errors that are most likely off-line errors.(3C"@p(4@pC#  Time: 29-Dec 18:19:51  To 29-Dec 18:37:03   Span:   0:17:12 z
C/@p
C,($:DR.T.3.1.2.2.1.2.2.2.(5*C0G-(5rC2(6C3
bC<@p!C4STOP - You are moving in a reverse direction thru the menu. You are(6:CC@pC=about to back into the Write Data Drive Off-line Theory.(7BCE@p(88@p
CFYour response please:z
CM@pCK(("D=$3.1.2.2.1.2.2.3.(9COG-(9ZCP(9pCR
bC[@p#CSTheory - If a drive reports OPI Errors while writing data, then chances(:"Cc@p#C\are the fault has something to do with the Write Clock timing logic in(;2Cf@pCdthe drive.(<:Cg@p(<bCi@p(<zCp@pCj  Write Data - OPI Write Timing Theory ... [2.1.5.3](=Cq@p(>Cv@pCr    MT100 (TU45, SN:FF8) reports:(>C}@pCw    6. OPI errors while performing write operations.(>jC@p(?ZD@pD  Time: 23-Mar 00:00:00  To 23-Mar 00:01:50   Span:   0:01:50 (?rD@p(@rD
@p(A
D@p(A"D@pD
Background - (A:D@p(AjD@p"D OPI - Operation Incomplete indicates that the data transfer did not(B@pD begin within seven seconds after command initiation.z
D$@p
D!(5*FrR.T.3.1.2.2.1.2.2.3.(CzD%G-(DBD'(DXD(
bD1@p!D)STOP - You are moving in a reverse direction thru the menu. You are(E
D7@pD2about to back into the Write Operation OPI Theory.(FD9@p(Fx@p
D:Your response please:z
DA@pD?(9E%(3.1.2.2.1.2.2.4.(GRDCG-(HDD(H0DF
bDN@p"DGThis report summarizes device errors that occurred during write data(HbDW@p!DOoperations. The errors are summarized by drive and error status bit(IjDZ@pDXcombinations.(JrD[@p(K"D]@p(K:Dc@pD^  Write Data - Device Error Summary ...[2.1.5.4](KRDe@p(L:Di@pDf  MT100 (TU45, SN:200) reports(LRDk@p(MDp@pDl      Error bit		Number  of				  Span(M2Dx@pDq     Combinations	Occurrences        Window	        HH:MM:SS(N
E@p$Dy     ------------       -----------        ------               --------(OE@pE D  N  F  N  F  R  I  I(PE	@pE T  E  C  S  M  M  L  L(PRE
 E  F  E  G  T  R  R  F(QE@p(QRE@pE 0  0  0  0  0  0  0  1   10.  23-Mar 00:03:00 (QjE@pE 0  0  0  0  0  0  1  0   10.  23-Mar 00:02:00 (RRE@p(S8@pE  Time: 23-Mar 00:00:00  To 23-Mar 00:05:00   Span:   0:05:00 z
E)@p	E'(GRF"3.1.2.2.1.2.2.4.A.(TRE+G-(UE,(U0E.
bE6@pE/Background - Eight detectors monitor for TM02/03 device errors:(UbE7@p(VbE@@p!E8 DTE - Drive Timing Error means that either; the Write Clock signal(VzEH@p#EA was not received in time to provide a valid tape character, or a data(XEQ@p#EI transfer (read or write) was attempted when the Massbus (data bus) was(Y
EU@p	ER already occupied.(ZEV@p(ZRE_@p#EW NEF - Non Executable Function means that either; a write operation was(ZjEh@p"E` issued to a write protected drive, or the tape density code does not([zEm@pEi match the drives PE status line.(]En@p(]REw@p$Eo FCE - Frame Count Error means that either; a space operation terminated(]jF@p$Ex with a non-zero frame count, or the drive failed to negate run when the(^zF@p
F controller asserted EBL.(`
F@p(`JF@p#F NSG - Non Standard Gap means that a tape character was detected during(``@pF the first half of the end of record gap.z
F@p	F(TRA3.1.2.2.1.2.2.4.B.(bRFG-(cF(c0F
bF&@p!F FMT - Format Error means that the format code is not implemented.(cbF(@p(djF0@p"F) RMR - Register Modification Refused means that a register write was(eF5@pF1 attempted when the GO bit was set.(f
F7@p(fZF@@p#F8 ILF - Illegal Function means that an illegal function code was issued.(frFA@p(hFI@pFB ILR - Illegal Register means an attempt was made to access a(h@pFJ non-existent register.z
FR@p
FO'}BH
F.T.3.1.2.2.1.2.3.1.(iZFSG-(j"FU(j8FV
bF_@p$FWThat's it. There are only  three Write Operation Device Theories and one(jjFh@p#F`Summary Report. Next on the menu is the Write Operation Software Error(kzFj@pFiSummary.(mFl@p(m(@p
FmYour response please:z
G@pG(
;K*z
@)@pFt(CzH*R.T.3.1.2.2.1.2.2.4.B.(Fy(nxFz
bG@p!F{STOP - You are moving in a reverse direction thru the menu. You are(o*G@pGabout to back into the Write Operation Device Error Theories.(p2G
@p(q0@p
G response please:3.1.2.2.1.3.0.2)p3.1.2.2.1.2.3.1.(nGG-(rJG(r`G
bG"@p#GThis report summarizes magtape errors thought to be caused by software.(sG*@p"G#For example: a Write operation issued while the tape was at EOT would(t"G/@pG+be considered a software error.(u*G1@p(uzG8@pG2Write data - Write Software Error Summary ... [2.1.6.1](vG9@p(wG?@pG:  Note: Error register contents are in octal.(wGA@p(wzGF@pGBMT300  (TU45, SN: 621.) reports:(xGG@p(xbGM@pGH Error      Media   No. of					  SPAN  (xzGS@pGN Register    ID     Errors		Window			HH:MM:SS(yRGY@pGT----------  -----   ------		------			--------(z2Gb@p$GZ     0      unk.      2.  24-Jun 12:37:53 - 24-Jun 12:37:54      0:00:01 ({Gk@p$Gc     0     6258       2.  25-Jun 00:56:07 - 25-Jun 00:56:08      0:00:01 (|"Gt@p$Gl     0     9494       2.  25-Jun 01:16:35 - 25-Jun 01:16:36      0:00:01 (}2Gw@p	Gu-------------------(~BH@p$GxThe report continues to list each drive associated with software errors.(~zH@p	H-------------------)
H@p)@@pH  Time: 24-Jun 12:37:53  To 30-Jun 02:41:49   Span: 134:03:56 z
H@p	H(iZZF.T.3.1.2.2.1.3.0.)ZHG-)"H)8H
bH@p"HThat's it. There is only one Write Operation Software Summary Report.)jH%@pH Next on the menu are the Massbus Theories.)rH&@p)P@p
H'Your response please:z
H/@p
H,(n*J+R.T.3.1.2.2.1.2.3.1.)*H0G-)rH2)H3
bH<@p!H4STOP - You are moving in a reverse direction thru the menu. You are):HD@p"H=about to back into the Write Operation Software Error Summary Report.)BHF@p)H@p
HGYour response please:)zI<G-z
HN@pG'92I7)	:HOG-)	bHQ)	xHR
bHZ@pHS       TM02/TM03 Massbus (control bus/data bus) Theories)
*H[@p)"Hd@p!H\Overview - There are eight Massbus theories. The first two theories):Hl@p"Heattempt to localize the cause of Massbus (control bus) parity errors)
BHu@p!Hmand1Massbus)(controltbus)ctimeoutsrtoTeither)theMassbus@controller)@p"H~  RH10 and RH20 controllers have a single bit: Register Access Error)RI@p!I  (RAE), which indicates that either a Massbus (control bus) parity)ZI@p#I  error or a Massbus (control bus) timeout occurred during an external)bI@p
I  register read or write.)jI@p)*I$@p"I  RH11 controllers have two bits: RH Control Bus Parity Error (RHCPE))BI-@p$I%  and Non-Existent Drive (NED). These bits indicate Massbus (control bus))H@p I.  parity errors and Massbus (control bus) timeouts respectively.3.1.2.2.1.3.M.3)Exz
HJ@pI9)	:K5&3.1.2.2.1.3.0.A.)	"I=)@I?
bIG@p!I@The remaining six Massbus theories attempt to localize the cause of)rIP@p$IHMassbus (data bus) to either; the MBox/DF10C/UBA, the Massbus Controller)zIW@pIQ(RH10/11/20), or the tape controller (TM02/03).)
IX@p)rIa@p#IY  Both Massbus controllers (RHs) and Massbus devices (TMs) check parity)
Ij@p$Ib  on the Massbus (data bus). The parity is checked during read and write)Io@pIk  operations as illustrated below.)*Iq@p)zIv@pIr    DF10C     RH10    Massbus   TM02/03)I}@pIw    <read --- DPE   <---------  no ck  <--- tape)jJ@pI~    write>--- no ck ----------> PAR    ---> tape)RJ@p) :J
@pJ    UBA      RH11    Massbus   TM02/03) RJ@pJ    <read --- DPE   <---------  no ck  <--- tape)!*J@pJ    write>--- no ck ----------> PAR    ---> tape)"J@p)"zJ@pJ    MBox      RH20    Massbus   TM02/03)#J%@pJ    <read --- DPE   <---------  no ck  <--- tape)#h@pJ&    write>--- DPE   ----------> PAR    ---> tapez
J0@p
J-)*LpR.T.3.1.2.2.1.3.0.A.)%:J1G-)&J3)&J4
bJ=@p!J5STOP - You are moving in a reverse direction thru the menu. You are)&JJC@pJ>about to back into the Massbus Theory Overview.)'RJE@p)(8@p
JFYour response please:)FL4G-z
JM@pI5+RZ>$))*JNG-))RJP))hJQ
bJY@pJR       TM02/TM03 Massbus (control bus/data bus) Theories)*JZ@p)+J]@pJ[Selection menu)+*J_@p)+ZJf@pJ` 0. Overview - Massbus (control bus/data bus) Theories)+rJg@p),bJp@p"Jh 1. Massbus (control bus) RH Theory .......................[2.1.7.1]),zJx@p"Jq 2. Massbus (control bus) TM Theory .......................[2.1.7.2]).Jz@p)/
K@p"J{ 3. Data Read/Massbus  (data bus) RH Theory (RH20 only) ...[2.1.7.3])/"K@p"K 4. Data Read/Massbus  (data bus) TM Theory (RH20 only) ...[2.1.7.4])0*K
@p)12K@p"Kdata bus) MBox Theory .............[2.1.7.5])1JK@p"K 6. Data Write/Massbus (data bus) RH Theory ...............[2.1.7.6])2RK&@p"K 7. Data Write/Massbus (data bus) RH Theory ...............[2.1.7.7])3ZK.@p"K' 8. Data Write/Massbus (data bus) TM Theory ...............[2.1.7.8])4bK0@p)5h@pK1Your selection please (topic #):z
K9@pK7)zL0$3.1.2.2.1.3.1.)6RK:G-)7K<)7(K=
bKF@p$K>Theory - If a tape subsystem reports Massbus (control bus) parity errors)7ZKO@p#KGor Massbus timeout errors and if the errors involve two or more TM02/03)8jKX@p!KPtape controllers, then chances are the fault lies in the RH Massbus)9zK`@p"KYcontroller or the Massbus cable. If, however, the errors are local to);Ki@p#Kaa single TM02/03, then chances are the fault is in the TM02/03 and has)<
Ko@pKjsomething to do with the Massbus interface logic.)=Kq@p)=zKx@pKrRH CBUS Error - Massbus(control bus) RH theory [2.1.7.1])>Kz@p)?
L@pK{  MT315 (TU45, SN: 627) was identified with)?"L@pL  4.  Massbus (control bus) Parity Errors detected by)@L@pL  Controller no: 1 (TM02) connected to channel 3 (RH11).)@rL@p)AjL@pL  MT324 (TU45, SN: 452) was identified with)BL@pL  2.  Massbus (control bus) Parity Errors detected by)BbL$@pL  Controller no: 2 (TM02) connected to channel 3 (RH11).)CRL&@p)DH@pL'  Time: 23-Mar 00:01:00  To 23-Mar 06:01:15   Span:   6:00:15 3.1.2.2.1.3.2.3)dHz
JI@pL2)6RM3.1.2.2.1.3.1.A.))L6)FHL7
bL@@p!L8Threshold - At least two (RH detected) Massbus (control bus) parity)FzLH@p"LAerrors or Massbus (control bus) timeouts are required to satisfy this)HLP@pLItheory. In addition, the errors must involved two or more tape)I
LY@p#LQcontrollers (TM02/03). The report identifies the controller, the number)J
Lb@p#LZofrdrives thatrwereinvolved,@andthetotalnumberof)Massbus(control)KLf@p- Refer to the Massbus Theory Overview. z
Lu@p
Lr)%:N%R.T.3.1.2.2.1.3.1.A.)N
LvG-)NRLx)NhLy
bM@p!LzSTOP - You are moving in a reverse direction thru the menu. You are)OM	@pMabout to back into the Massbus (control bus) RH Theory.)P"M
@p)Q@p
MYour response please:)dRN)G-z
M@pL-)FNC,)RMG-)R*M)R@M
bM @p$MTheory - If a tape subsystem reports Massbus (control bus) parity errors)RrM)@p#M!or Massbus timeout errors and if the errors involve two or more TM02/03)TM1@p!M*tape controllers, then chances are the fault lies in the RH Massbus)UM:@p"M2controller or the Massbus cable. If, however, the errors are local to)VMB@p#M;a single TM02/03, then chances are the fault is in the TM02/03 and has)W"MI@pMCsomething to with the Massbus interface logic.)X*MJ@p)YMR@pMKRH CBUS Error - Massbus (control bus) TM theory [2.1.7.2])Y*MS@p)Z"MY@pMT  MT315 (TU45, SN: 627) was identified with)Z:M`@pMZ  4.  Massbus (control bus) Parity Errors detected by)[Mh@pMa  Controller no: 1 (TM02) connected to channel 3 (RH11).)\
Mi@p)]Mq@pMj  Time: 23-Mar 00:01:00  To 23-Mar 06:01:15   Span:   6:00:15 )]Ms@p)^M{@p!MtThreshold - One or more (RH detected) Massbus (control bus) parity)^2N@p"M|errors or Massbus (control bus) timeouts are required to satisfy this)_:N
@pNtheory.0In.addition,ralldtheierrorshmustiinvolvetthensamertape)`BN@p#NMassbus (control bus) errors that occurred.)bRN@p)c0@pNBackground - Refer to the Massbus Theory Overview.3.1.2.2.1.3.3.3)v`z
M@p	N')N
PR.T.3.1.2.2.1.3.2.)QjN+)eN,
bN5@p!N-STOP - You are moving in a reverse direction thru the menu. You are)eJN<@pN6about to back into the Massbus (control bus) TM theory.)fRN=@p)g@@p
N>Your response please:)vjO;G-z
NE@pN")RO6&)h2NGG-)hZNH)hpNJ
bNR@p"NKTheory - If a tape subsystem reports Massbus (data bus) parity errors)i"N[@p!NSduring data reads, and if the errors involve multiple TM02/03 tape)j*Nc@p#N\controllers, then chances are the fault lies in the Massbus controller)k2Nl@p!Nd(RH10/11/20) or the Massbus cable If, however, the errors involve a)l:Nt@p#Nmsingle TM02/03 then, chances are the fault lies in the TM02/03 and has)mBN{@pNusomething to do with the Massbus interface logic.)nJN|@p)o2N~@p)oJO@p"N  RH DPE Error - Data Read/Massbus (data bus) RH theory ... [2.1.7.3])obO@p)pjO
@pO	sbusRHdNo: 2.s(RH20)treports:)qO@p"Oh the following)qJO@pO    controllers and their drives:)rRO@p)s"O"@pO       1. Errors in MT210  (TM02: 1., TU45, SN: 200))s:O$@p)t*O+@pO%       1. Errors in MT220  (TM02: 2., TU45, SN: 600))tBO,@p)u0@pO-  Time: 23-Mar 00:01:00  To 23-Mar 00:01:15   Span:   0:00:15 3.1.2.2.1.3.4.3*8z
NA@pO8)h2P5 3.1.2.2.1.3.3.A.)hO<)w0O>
bOG@p#O?Threshold - At least two (RH detected) Massbus (data bus) parity errors)wbOP@p$OHare required to satisfy this theory. The errors must involve two or more)xrOY@p#OQtape controllers (TM02/03) and they must have occurred during data read)zOa@p"OZoperations. The report identifies the RH controller and the number of){Oj@p$Obtape controllers that were involved. The report also lists the number of)|Oq@pOkMassbus (data bus) parity errors that occurred.)}*Or@p)~Ot@p)~*Oy@pOuMBox/UBA    RHxx    Massbus   TM02/03)~BO{@p)P@pO| <read  --- DPE   <---------.- no ck <--- tape)2P@pP                            !*P
@pP                            !_ no ck <--- tape*bP@p*JP@p*`@pPBackground - Refer to the Massbus Theory Overview.z
P@p
P)dRQeR.T.3.1.2.2.1.3.3.A.*bPG-**P*@P
bP'@p!P STOP - You are moving in a reverse direction thru the menu. You are*rP.@pP(about to back into the Massbus (data bus) RH Theory.*zP0@p*h@p
P1Your response please:*BQ G-z
P8@pO4)vjQ *ZP9G-*P;*P<
bPE@p"P=Theory - If a tape subsystem reports Massbus (data bus) parity errors*JPM@p!PFduring data reads, and if the errors involve multiple TM02/03 tape*RPV@p#PNcontrollers, then chances are the fault lies in the Massbus controller*	ZP^@p"PW(RH10/11/20) or the Massbus cable. If, however, the errors involve a*
bPg@p#P_single TM02/03 then, chances are the fault lies in the TM02/03 and has*jPm@pPhsomething to do with the Massbus interface logic.*
rPo@p* RH DPE Error - Data Read/Massbus(data bus) controller theory [2.1.7.4]*
P{@p*Q@pP|  MT210  (TU45, SN: 200) was identified with*2Q@pQ  3. Massbus (data bus) Parity Errors detected by*Q@pQ  Controller no: 1. (TM02) connected to channel 2. (RH20).*zQ@p*rQ@p*@pQ  Time: 23-Mar 00:00:00  To 23-Mar 00:01:45   Span:   0:01:45 3.1.2.2.1.3.5.3*3 z
P4@pQ*ZR3.1.2.2.1.3.4.A.*BQ"*Q#
bQ,@p#Q$Threshold - One or more (RH detected) Massbus (data bus) parity errors*:Q4@p"Q-are required to satisfy this theory. The errors must involve the same*BQ=@p#Q5tape controller (TM02/03) and they must have occurred during data read*JQE@p!Q>operations. The report identifies the drive and lists the number of*RQL@pQFMassbus (data bus) parity errors that occurred.*ZQM@p*BQS@pQNMBox/UBA    RHxx    Massbus   TM02/03*ZQT@p*2QZ@pQU <read  --- DPE   <---------  no ck <--- tape*JQ\@p**Q]@p*@@pQ^Background - Refer to the Massbus (data bus) Introduction.z
Qi@p
Qg*bTR.T.3.1.2.2.1.3.4.A.*RQkG-*Ql*0Qn
bQv@p!QoSTOP - You are moving in a reverse direction thru the menu. You are*bQ}@pQwabout to back into the Massbus (data bus) TM Theory.*jQ@p*X@p
RYour response please:*3*SG-z
R@pQ*BS,* JRG-* rR
*!R
bR@p"R
Theory - If a system reports Massbus (data bus) parity errors during *!:R@p"Rdata writes, and if those errors involve multiple Massbus controllers*"BR%@p!R(RH10/11/20), then chances are the fault has to do with the memory*#JR-@p!R&controller or the channel. If, however, the errors involve a single*$RR6@p$R.Massbus controller and multiple tape controllers (TM02/03), then chances*%ZR?@p$R7are the fault lies in the Massbus controller or the Massbus. Finally, if*&jRH@p#R@the errors involve a single tape controller, then the fault is probably*'zRQ@p$RIin the TM02/03 and has something to do with the Massbus interface logic.*)
RS@p**R\@p$RTRH DPE Error - Data Write/Massbus (data bus) MBox (UBA) Theory [2.1.7.5]**2Rd@p"R]  2. different RH controllers report: (during data write operations)*+BRj@pRe  5. Massbus (data bus) Parity Errors.*,JRk@p*-"Ro@pRlAdditional Data:*-:Rp@p*-rRx@pRq   RH no: 1 (RH20) reports (during data write operations)*.
R@pRy   3. (RH detected) Massbus (data bus) Parity Errors*/S@p*/rS@pS   RH no: 2 (RH20) reports (during data write operations)*0
S@pS	   2. (RH detected) Massbus (data bus) Parity Errors*1S@p*1p@pS  Time: 29-Mar 00:30:00  To 29-Mar 02:15:00   Span:   1:44:603.1.2.2.1.3.6.3*U z
R@pS* JT!$3.1.2.2.1.3.5.A.* 2S *3pS"
bS+@p#S#Threshold - At least two (RH detected) Massbus (data bus) parity errors*4"S4@p$S,are required to satisfy this theory. The errors must involve two or more*52S=@p$S5RH controllers and they must have occurred during data write operations.*6BSE@p"S>The report lists the number of Massbus (data bus) parity errors that*7RSN@p"SFoccurred and the number of different controllers that were involved.*8ZSO@p*9bSQ@p*9zSV@pSR MBox         RH20  Massbus   TM02/03*:SX@p*:jS^@pSY         .--> DPE ---------->  PAR  ---> tape*;S`@pS_write>---!*;bSf@pSa         `--> DPE ---------->  PAR  ---> tape*<
Sh@p*<jSq@p$SiSince RH10s and RH11s do not check parity during a data write operation,*=Sx@pSrthis theory only applies to RH20 controlled tape subsystems.*>Sz@p*?
S{@p*? @pS|Background - Refer to the Massbus Theory Overview.z
T@p
T*RVR.T.3.1.2.2.1.3.5.A.*@"TG-*@jT	*AT
bT@p!T
STOP - You are moving in a reverse direction thru the menu. You are*A2T@pTabout to back into the Massbus (data bus) MBox Theory.*B:T@p*C(@p
TYour response please:*U*U/G-z
T$@pS*3*U*(*DT%G-*DBT'*DXT(
bT1@p"T)Theory - If a system reports Massbus (data bus) parity errors during *E
T9@p"T2data writes, and if those errors involve multiple Massbus controllers*FTB@p!T:(RH10/11/20), then chances are the fault has to do with the memory*GTJ@p!TCcontroller or the channel. If, however, the errors involve a single*H"TS@p$TKMassbus controller and multiple tape controllers (TM02/03), then chances*I*T\@p$TTare the fault lies in the Massbus controller or the Massbus. Finally, if*J:Te@p#T]the errors involve a single tape controller, then the fault is probably*KJTn@p$Tfin the TM02/03 and has something to do with the Massbus interface logic.*LZTp@p*MjTx@p#Tq  RH DPE Error - Data Write/Massbus(data bus) RH Theory ...  [2.1.7.6]*NTz@p*O
U@pT{    RH No: 1. (RH20) reports (during Data Write operations)*O"U@pU    4. (RH detected) Massbus (data bus) Parity Errors.*PU
@p*Q
U@p	U  Additional Data:*Q"U@p*QZU@p$U  MT100  (TM02: 0, TU45, SN:654) reports: (during Data Write operations)*QrU@pU  4. (TM02 detected) Massbus (data bus) Parity Errors.*SU @p*Sp@pU!  Time: 29-Mar 00:30:00  To 29-Mar 02:15:00   Span:   1:44:603.1.2.2.1.3.7.3*uxz
T @pU,*DV% 3.1.2.2.1.3.6.A.*DU0*UpU2
bU;@p#U3Threshold - At leasttwo(RH@detected) Massbus (data bus) parity errors*V"UC@p"U<arerequiredtosatisfyithisRtheory.dThe1errorsnmusthinvolveithedsame*W2UL@p"UDRHrcontroller]andtwoormoreitapeecontrollers.lAlso,othe2errorsrmust*X:UR@pUMhavejoccurredduringdatawriteoperations.*YBUS@p*Z"UU@p*Z:UZ@pUVMBox       RH20  Massbus   TM02/03*ZRU[@p*["Ua@pU\write> ---  DPE --------->-- PAR ---> tape*[:Uf@p
V
@p
V*@"XR.T.3.1.2.2.1.3.6.A.*`bV
G-*a*VV
bV@p!VSTOP - You are moving in a reverse direction thru the menu. You are*arV@pVabout to back into the Massbus (data bus) RH20 Theory.*bzV @p*ch@p
V!Your response please:*vW4G-z
V(@pU(*U*W0(*dZV)G-*eV+*eV,
bV5@p"V-Theory - If a system reports Massbus (data bus) parity errors during *eJV=@p"V6data writes, and if those errors involve multiple Massbus controllers*fRVF@p!V>(RH10/11/20), then chances are the fault has to do with the memory*gZVN@p!VGcontroller or the channel. If, however, the errors involve a single*hbVW@p$VOMassbus controller and multiple tape controllers (TM02/03), then chances*ijV`@p$VXare the fault lies in the Massbus controller or the Massbus. Finally, if*jzVi@p#Vathe errors involve a single tape controller, then the fault is probably*l
Vr@p$Vjin the.TM02/03sandahasbsomethingytordorwith theeMassbus interfaceZlogic.*mVt@p*n*V|@p"VuerRHDPE*Error@-DataWrite/Massbus(data bus)ERHotheorye...d[2.1.7.7]*nBV~@p*oJW@pVBWRHNo:1.*(RH20)preports (duringrData Writetoperations)*obW03: 1,TU45, SN: 764.)*sRW&@p*tH@pW'  Time: 29-Mar 00:00:00  To 29-Mar 02:15:00   Span:   2:15:00 3.1.2.2.1.3.8.3+Hz
V$@pW2*dZX>&3.1.2.2.1.3.7.A.*dBW6*vHW7
bW@@p!W8Threshold - At least two TM02/03 detected Massbus (data bus) parity*vzWH@p#WAerrors (PAR) are required to satisfy this theory. The errors must have*xWQ@p"WIbeen detected by two or more TM02/03s and they must be common to the*y
WZ@p#WRsame RH controller.!The*reportpidentifies the controller, the numberAof*zWb@p!W[drivesthatXwere involved, and the number of drive detected Massbus*{"Wh@pWc(data bus) parity errors that occurred.*|*Wi@p*}Wk@p*}Wp@pWlMBox/UBA    RHxx  Massbus   TM02/03*}2Wq@p*~Ww@pWr write> --- DPE --------->-- PAR ---> tape*~W|@p
@p$XSincelall Massbus,devicesacheck2datanparitydduringsdataswriteoperations+:X@p#X+p@pXBackground - Refer to the Massbus Theory Overview.z
X#@p
X!*`bZR.T.3.1.2.2.1.3.7.A.+rX%G-+:X&+PX(
bX0@p!X)STOP - You are moving in a reverse direction thru the menu. You are+X7@pX1about to back into the Massbus (data bus) RH Theory.+
X9@p+x@p
X:Your response please:+RY9G-z
XA@pW-*vY5"+jXBG-+XD+(XE
bXN@p"XFTheory - If a system reports Massbus (data bus) parity errors during +ZXV@p"XOdata writes, and if those errors involve multiple Massbus controllers+	bX_@p!XW(RH10/11/20), then chances are the fault has to do with the memory+
jXg@p!X`controller or the channel. If, however, the errors involve a single+rXp@p$XhMassbus controller and multiple tape controllers (TM02/03), then chances+
zXy@p$Xqare the fault lies in the Massbus controller or the Massbus. Finally, if+
Y@p#Xztheerrorsinvolveapsingletape controller, then thetfaultsissprobably+Y@p$Yin]theYTM02/03and+has somethingto doMwith theUMassbus interfacerlogic.+*Yata Write operations)+Y(@pY!     3. (TM02 detected) Massbus (data bus) Parity Errors.+
Y)@p+Y+@p+@pY,  Time: 23-Mar 00:00:00  To 23-Mar 00:01:45   Span:   0:01:45 3.1.2.2.1.4.1.3+2z
X=@pY7+jJJ3.1.2.2.1.3.8.A.+RY;+Y<
bYE@p"Y=Threshold - One or more (TM02/03 detected) Massbus (data bus) parity+JYN@p#YFerrors are required to satisfy this theory. The errors must involve the+RYV@p#YOsame TM02/03 and they must have occurred during data write operations.+bYX@p+jY]@pYYMBox/UBA    RHxx  Massbus   TM02/03+Y^@p+RYd@pY_ write> --- DPE ----------->PAR ---> tape+jYf@p+JYg@p+bYp@p$YhSince all Massbus devices check data parity during data write operations+zYy@p#Yqthis theory applies to RH10, RH11, and RH20 controlled tape subsystems.+
Y{@p+Y|@p+0@pY}Background - Refer to the Massbus Theory Overview.z
Z@p	Z)Z[F.T.3.1.2.2.1.4.1.+ 2Z	G-+ zZ
+!Z

bZ@p"Zhere are only eight Massbus Theories. Next on the menu is+!BZ@pZTM02/03 Control Operation Summary.+"JZ@p+#@p
ZYour response please:z
Z#@p
Z!+r[RR.T.3.1.2.2.1.3.8.A.+#rZ%G-+$:Z&+$PZ(
bZ0@p!Z)STOP - You are moving in a reverse direction thru the menu. You are+%Z7@pZ1about to back into the Massbus (data bus) TM Theory.+&
Z9@p+&x@p
Z:Your response please:+2"[G-z
ZA@pY2))*6&+'jZBG-+(ZD+((ZE
bZM@p ZFThis report summarizes all non read/write errors. The report !!!+(ZZO@p+)ZZP@p+)rZY@p"ZQ  Control Operation - Control Operation error summary ... [2.1.8.1] +*
ZZ@p++Zb@pZ[  Note: Function code is in octal and without the GO bit.++*Zc@p+,"Zh@pZdMT210  (TU45, SN: 200) reports:+,:Zj@p+-
Zn@p
Zk Media ID    : TEST  +-"Zo@p+-bZt@pZp  Function    No. of						  SPAN  +-zZz@pZu    code      Errors		Window				HH:MM:SS+.JZ@pZ{  --------    ------		------				--------+/"[@p[     3           1.  23-Mar 00:00:00 			+/z[@p+0R[	@p[		     OPI, +0j[@p+1@p[
  Time of Error: 23-Mar 00:00:00 3.1.2.2.2.0.1.4+GHz
Z=@p[+ 2jF.T.3.1.2.2.2.0.+'R[+2h[
b["@p#[That'seit.sThere.areonly[27@TM02/039tapeTtheories.and summary reports.+3[+@p"[#Again, if you have any comments or suggestions that will make either+4*[4@p#[,Instruct or any other Spear Library function a better field maintenance+52[8@p
[?@p
[<						The Spear Team+7:[B@p[@						MR1-2 S/35+7r[D@p+8*[E@p+8B[M@p[FNext on the menu are the TX01/02 tape theories and reports.+8Z[N@p+9P@p
[OYour response please:z
[W@p	[T+#r\=
R.T.3.1.2.2.1.4.1.+:*[XG-+:r[Z+;[[
b[d@p![\STOP - You are moving in a reverse direction thru the menu. You are+;:[l@p[eabout to back into the TM02/03 tape theory and summary reports+<B[o@p[mdescriptions.+=B[p@p+=p@p
[qYour response please:+GR\AG-z
[x@p[#vb]$+>b[zG-+?
[{+? [}
b\@p[~         Analyze - TX01/TX02 Tape Subsystem Theories+?R\@p+@B\@p#\Overview - The TX tape theories apply only to TX01/02 tape controllers+@Z\@p#\that drive TU70, TU71, TU72 and TU73 tape transports. In addition, the+Ab\@p#\TX01/02 tape theories are restricted to TXs that are directly connected+Bj\%@p\ to either a DX10 (DF10C) or a DX20 (RH20).+Cz\'@p+DZ\/@p"\(The TX theories are based on the type of operation the tape subsystem+Dr\8@p$\0was performing at the time the error was reported (i.e., Read, Write, or+Ex@p\9Control).3.1.2.2.2.M.2.0+Y@z
[t@p\?+:*]LR.T.3.1.2.2.2.0.+>J\C+H\D
b\M@p!\ESTOP - You are moving in a reverse direction thru the menu. You are+HJ\T@p\Nabout to back into the TX01/02  Tape Theory Overview.+IR\U@p+J@@p
\VYour response please:+YJ]QG-z
\]@p\:2A" +K2\_G-+KZ\`+Kp\b
b\i@p\c                    TX01/TX02 Tape Subsystem Theories+L"\j@p+M\m@p\kSelection Menu+M*\o@p+MZ\u@p\p 0. Overview - TX01/TX02 Tape Subsystem Theories+Mr\w@p+NZ\@p!\x 1. TX01/02 Read Operation Theories ......[2.2.1.1] thru [2.2.3.1]+Nr]@p+Oz]	@p!] 2. TX01/02 Write Operation Theories .....[2.2.4.1] thru [2.2.6.1]+P]@p+Q]@p!]
 3. TX01/02 Massbus Theories .............[2.2.7.1] thru [2.2.7.10]+Q2]@p+R:]@p] 4. TX01/02 Control Operation Theories ...[2.2.8.1]+RR]@p+SB]@p+SX@p] Your selection please (topic #):z
](@p]&+>b^-
3.1.2.2.2.1.0.+TB])G-+U]++U],
b]3@p]-             TX01/TX02 Read Operation Theories+UJ]4@p+V2]=@p"]5Overview - The TX01/02 Read Operation Theories are based on the type+VJ]E@p"]>of errors that occur during tape read operations (i.e., Data errors,+WP@p]FDevice errors, or Software errors.3.1.2.2.2.1.M.1+ePz
\Y@p	]N+GR_R.T.3.1.2.2.2.1.0.+K]R+Z]T
b]\@p!]USTOP - You are moving in a reverse direction thru the menu. You are+ZB]d@p]]about to back into the TX01/02 Read Operation Theory Overview.+[J]f@p+\H@p
]gYour response please:+eZ^2G-z
]n@p]J.Rr+]b]q+]x]r
b]y@p]s             TX01/TX02 Read Operation Theories+^*]z@p+_]}@p]{Selection Menu+_*]@p+_Z^@p^ 0. Overview - TX01/TX02 Read Operation Theories+_r^@p+`Z^@p#^ 1. TX01/02 Read Operation Data Theories ......[2.2.1.1] thru [2.2.1.6]+`r^@p+b^@p#^ 2. TX01/02 Read Operation Device Theories ....[2.2.2.1] thru [2.2.2.4]+b^@p+c*^#@p^ 3. TX01/02 Read Operation Software Summary ...[2.2.3.1]+cB^%@p+d:^&@p+dP@p^'Your selection please (topic #):,"aGG-,z
]j@p^/+TB`3.1.2.2.2.1.1.0.+]"^3+f ^5
b^;@p^6           TX01/TX02 Read Operation Data Theories+fR^=@p+g:^E@p#^>Overview - This set of theories apply only to errors that are directly+gR^N@p#^Frelated to reading tape. The transport must report the occurrence of a+hZ^W@p#^Oread error (Data Check) without the occurrence of a device error (i.e.,+ib^^@p^Xall other error bits in Sense Byte Zero (0) must be zero).+jr^`@p+kj^a@p+l^j@p$^bThe DX10 read operations are: Read Forward, Read Backward, Forward Space+l^r@p^kBlock, Backspace Block, Forward Space File, and Backspace File.+m*^t@p+n*^}@p$^uThe DX20 read operations are: Read Forward, Read Reverse, Space Forward,+n@@p^~Space Reverse, Forward Space File, and Reverse Space File.z
_	@p
_+YJaB
R.T.3.1.2.2.2.1.1.0.+pJ_
G-+q_
+q(
b_@p!_STOP - You are moving in a reverse direction thru the menu. You are+qZ_@p_about to back into the Read Operation Data Theory Overview.+rb_@p+sZ_ @p+sp@p
_!Your response please:z
_)@p_&-
2jA$3.1.2.2.2.1.1.M.+tJ_*G-+u_,+u(_-
b_4@p_.          TX01/02 Read Operation Data Theories+uZ_5@p+vB_<@p_6 0. Overview - TX01/TX02 Read Operation Data Theories+vZ_>@p+wJ_G@p$_? 1. Read Data Head/Amplifier Theory .......................... [2.2.1.1]+wb_H@p+xr_Q@p$_I 2. Read Data Error Rate Greater Than 1 per Million Transfers  [2.2.1.2]+y
_S@p+z_\@p$_T 3. Read Data Error Rate Less Than 1 per Million Transfers ....[2.2.1.3]+z2_]@p+{B_f@p$_^ 4. Read Data Error Summary by Data Track .....................[2.2.1.4]+{Z_h@p+|j_q@p$_i 5. Read Data Media Bad Spot Theory ...........................[2.2.1.5]+}_r@p+~_{@p$_s 6. Read Data Media Bad Spot Summary ..........................[2.2.1.6]+~*_}@p+:_~@p+P@p_Your selection please (topic #):z
`@p`+eZ`t$3.1.2.2.2.1.1.1.,:`	G-,`,`

b`@p#`errordrateaforrargivendata8trackisgreater@thantwice the,J`@p#`average foraallatracks, then chancesIare thereadEamplifierAor	the read,Z`#@p`headfor that track is at fault.,j`%@p,:`+@p`&  Read Data Head/Amplifier Theory ... [2.2.1.1],R`-@p,:`2@p`.    MT100 (TU70, SN:0) reports:,R`6@p
`N@p!`F    1/5   2/7   3/3   4/P   5/2   6/1   7/0   8/6   9/4    Failures,Z`W@p$`O    ---   ---   ---   ---   ---   ---   ---   ---   ---   --------------,	b`_@p `X     1.    0.    0.   138.    1.   0.    0.    0.    0.        0.,
r``@p,r`b@p,
`k@p#`cNote: This theory only applies to TOPS-20 because TOPS-10 does not keep,
 @p$`ltrack of the number of frames read per Tape drive. See Theory [2.2.1.4].z
`x@p	`v,:a?3.1.2.2.2.1.1.1.A.,B`zG-,
`{, `}
ba@p#`~Threshold - At least 100 data read errors are required to satisfy this,Ra@p"atheory. The errors must involve the same drive and two or more media.,Za@p"aIn addition, the overall error rate for the drive must be equal to or,ba@p#agreater than one error per million frames read. Finally, the error rate,ja(@p"a of at least one data track must be twice the average for all tracks.,za)@p,a2@p$a*Note - Since the contents of the CRC register cannot be used to identify,a;@p#a3the failing track in NRZI mode, this theory applies only to read errors,(@pa<that occur in PE mode. z
ac@pa`,Bb`&z
^+@paD+pJcrR.T.3.1.2.2.2.1.1.1.A.+e:aH,paJ
baR@p!aKSTOP - You are moving in a reverse direction thru the menu. You are,"aY@paSabout to back into the Read Data Head/Amplifier Theory.,*a[@p,@p
a\Your response please:,>*cwG-,B(3.1.2.2.2.1.1.2.,zadG-,2af,Hag
bap@p$ahThis is a two part summary report. The report identifies all tape drives,zay@p"aqthat have a read data error rate that is equal to or greater than one,
b@p#azerror per million frames read. The first part of the report identifies,b
@p#bthe tape drive and, when possible, the number of errors associated with, b@pbeach data track.,!*b@p,!bb@p$b  Read Data - Error Rate Greater Than 1 per Million Transfers  [2.2.1.2],!zb@p,#
b@pb. ReMT100t(TU70,rSN:0)reports:,#"b#@p@p"b&                Physical Track / Data Track               NRZI or PE,$Rb2@pb.					                  Multi Track,%Zb;@p!b3    1/5   2/7   3/3   4/P   5/2   6/1   7/0   8/6   9/4    Failures,&*bD@p$b<    ---   ---   ---   ---   ---   ---   ---   ---   ---   --------------,'2bL@p"bE    12.   17.   13.    9.    1.    3.    6.    3.   13.          34.,(BbN@p,)JbW@p#bONote: This theory only applies to TOPS-20 because TOPS-10 does not keep,)`@p$bXtrack of the number of frames read per Tape drive. See Theory [2.2.1.4].z
bd@p	bb,zcp&3.1.2.2.2.1.1.2.A.,,bfG-,,Jbg,,`bi
bbr@p$bjThe second part of the report lists the time between consecutive errors,,-b{@p$bsthe number of frames that were read between errors, the track associated,."c@p$b|with the error (when possible), the media that was mounted, the user ID,,/2c@p	cand the program ID.,0Bc	@p,0zc
@pc
TimeeBetween    ,1c@p"ck    Media        User      Program,1Jc@p!cRead Errors     Frames Read  in Error   ID           ID         ID,2Rc&@p#c------------    ----------  --------  ------    -----------   --------,3Zc.@p"c'   0:00:25        2562240.      1.    IT7406    500000,,661    TAPE20,4bc7@p"c/   0:02:47       12201760.      8.    IT7406    500000,,661    TAPE20,5jc?@p"c8   0:00:00          32640.   MULTI    IT7406    500000,,661    TAPE20,6rcH@p"c@   0:00:00          27200.      8.    IT7406    500000,,661    TAPE20,7zcP@p"cI   0:00:01         111520.      4.    IT7406    500000,,661    TAPE20,9cY@p"cQ  41:40:21        8978490.   MULTI    FOO       500000,,605    DUMPER,:
c\@pcZ- - - - - - -,;ce@p#c]The report continues to list all read errors associated with the drive.,;Bch@pcf- - - - - - -,<P@pciBackground - Refer to the Read Data Theory Overview (topic # 0)z
d@pd,,e$z
a_@pct,"fR.T.3.1.2.2.2.1.1.2.A.,rcy,>xcz
bd@p!c{STOPp- You are moving in a reverse direction thru the menu. You are,?*d@p"dabout to back into the Error Rate Greater Than 1 Per Million Theory.,@2d
dYour response please:,bfG-,f3.1.2.2.2.1.1.3.,>dG-,BRd,Bhd
bd"@p$dThis is a two part summary report. The report identifies all tape drives,Cd+@p$d#that have a read data error rate that is less than one error per million,D*d4@p$d,frames read. The first part of the report identifies the tape drive and,,E:d=@p"d5when possible, the number of errors associated with each data track.,FJd>@p,GRdG@p$d?  Read Data - Error Rate Less Than 1 per Million Transfers ... [2.2.1.3],GjdI@p,HzdN@pdJ    MT100 (TU70, SN:0) reports:,IdR@p
dO    10. Read Data Errors.,IbdS@p,J"d\@p"dT                Physical Track / Data Track               NRZI or PE,J:da@pd]					                  Multi Track,KBdi@p!db    1/5   2/7   3/3   4/P   5/2   6/1   7/0   8/6   9/4    Failures,Ldr@p$dj    ---   ---   ---   ---   ---   ---   ---   ---   ---   --------------,Md{@p"ds     0.    0.    0.    0.    0.    0.    0.    7.    0.           3.,N*d|@p,O2e@p#d}Note: This theory only applies to TOPS-20 because TOPS-10 does not keep,OH@p$etrack of the number of frames read per Tape drive. See Theory [2.2.1.4].z
e@p	e,>f$3.1.2.2.2.1.1.3.A.,QjeG-,R2e,RHe
be @p$eThe second part of the report lists the time between consecutive errors,,Rze)@p$e!the number of frames that were read between errors, the track associated,T
e2@p$e*with the error (when possible), the media that was mounted, the user ID,,Ue6@p	e3and the program ID.,V*e7@p,Vbe;@pe8Time Between    ,VzeC@p"e<Consecutive     Number of     Track    Media        User      Program,W2eL@p!eDRead Errors     Frames Read  in Error   ID           ID         ID,X:eT@p#eM------------    ----------  --------  ------    -----------   --------,YBe]@p"eU   0:00:25        2562240.      8.    IT7406    500000,,661    TAPE20,ZJee@p"e^   0:02:47       12201760.      8.    IT7406    500000,,661    TAPE20,[Ren@p"ef   0:00:00          32640.   MULTI    IT7406    500000,,661    TAPE20,\Zev@p"eo   0:00:01          62560.   MULTI    IT7406    500000,,661    TAPE20,]bey@pew- - - - - - -,^jf@p#ezThe report continues to list all read errors associated with the drive.,_f@pf- - - - - - -,`*f@p,`X@pfBackground - Refer to the Read Data Theory Overview (topic # 0)z
f3@pf1,QjgB&z
d@pf,>*g$R.T.3.1.2.2.2.1.1.3.A.,Bf,bhf
bf"@p!fSTOP - You are moving in a reverse direction thru the menu. You are,cf*@p f#about to back into the Error Rate Less Than 1 Per Million Theory.,d"f+@p,e @p
f,Your response please:-
ZhjG--(3.1.2.2.2.1.1.4.,arf5G-,f:f6,fPf8
bf@@p"f9This is a summary report. It lists each drive that detected read data,gfI@p"fAerrors and, when possible, identifies the number of errors associated,h
fM@p
fJwith each data track.,ifN@p,iRfU@pfO  Read Data Error Summary by Data Track ... [2.2.1.4],ijfW@p,jZf\@pfX    MT100 (TU77, SN:6742) reports:,jrf`@p
f]    14. Read Data Errors.,kBfa@p,lfj@p"fb                Physical Track / Data Track               NRZI or PE,lfo@pfk					                  Multi Track,m"fw@p!fp    1/5   2/7   3/3   4/P   5/2   6/1   7/0   8/6   9/4    Failures,mrg@p"fx    ---   ---   ---   ---   ---   ---   ---   ---   ---   -----------,nzg@p g     1.    0.    0.   12.    1.   0.    0.    0.    0.        0.,pg	@p,qg@pg
  Time:  5-Jan 15:56:53  To  5-Jan 16:15:53   Span:   0:19:00 ,qg@p,rg@p"gNote: This summary applies to TOPS-10 (only) because, unlike TOPS-20,,r0@p$gTOPS-10 does not keep track of the number of frames read per Tape drive.z
g)@p
g&,bheR.T.3.1.2.2.2.1.1.4.,tJg*G-,ug,,u(g-
bg6@p!g.STOP - You are moving in a reverse direction thru the menu. You are,uZg=@pg7about to back into the Data Track Summary Description.,vbg>@p,wP@p
g?Your response please:z
gG@pgD,arh;(3.1.2.2.2.1.1.5.,x*gHG-,xrgJ,ygK
bgT@p!gLIf a reel of tape is associated with two or more read errors in GCR,y:g\@p#gUmode, four or more read errors in PE mode or eight or more read errors,zBge@p"g]in NRZI mode, then chances are the tape has become worn or dirty and,{Jgl@pgfshould be copied and (if possible) cleaned and verified.,|Rgn@p,}Jgt@pgo  Read Data - Media Bad Spot Theory ... [2.2.1.5],}bgv@p,~Jg}@pgw    Media ID: FICHE   Recording Mode: PE was identified with,~bh@pg~    read errors as noted against the following drives:,Zh@p-Jh
@ph    MT100  (TU71, SN: 0)  with 20. errors.-bh@p
h  Additional Data-Bh@ph        Operation    : READ FWD-h@ph        User ID      : 500000,,5-Rh@ph        Program ID   : TAPE20-"h @p-jh)@p$h!** If the tape was mounted on multiple drives, then the report will list-h1@p#h*   each drive that detected read errors associated with that Media ID.-h3@p-@ph4  Time:  5-Jan 15:56:53  To  5-Jan 16:15:53   Span:   0:19:00 z
h?@p	h=,x*hc3.1.2.2.2.1.1.5.A.-2hAG--zhB-hD
bhM@p#hEThreshold - In GCR mode, at least 2 read errors are required to satisfy-BhU@p!hNthis theory. In PE mode, at least four read errors are required to-	Rh^@p"hVsatisfy this theory. And in NRZI mode, at least eight read errors are-
X@ph_required to satisfy this theory.z
i@pi-2_$,z
f/@phg,tJj#R.T.3.1.2.2.2.1.1.5.A.,ezhl-
bhv@p!hnSTOPt-tYouaareimovingeinaa reversehdirection}thruthemenu.Youare-
h~Your response please:3.1.2.2.2.1.2.M-; 3.1.2.2.2.1.1.6.-
2iG--Ri-hi	
bi@p!i
This report summarizes all media bad spots that do not exceed the -i@p!ithreshold established for the Bad Spot Theory [2.2.1.5]. The report-"i#@p#iidentifies the medium, the recording mode, the drive, and the number of-*i,@p"i$read errors associated with the medium. In addition, the report lists-:i4@p#i-the type of read operation, the user ID, and the program ID associated-Bi8@pi5with the errors.-Ji9@p-i@@pi:  Read Data - Media Bad Spot Summary ... [2.2.1.6]-iA@p-iI@piB    Media ID: 7601 Recording Mode: NRZI was identified with-iP@piJ    read errors as noted against the following drives:-iQ@p-iX@piR    MT404  (TU72, SN: 28411.)  with 1. errors.-i\@p
iY      Additional Data-i`@pi]        Operation    :READ FWD-Bie@pia        User ID      :500000,,5-
ij@pif        Program ID   :DUMPER-Zik@p-"it@p$il** If the tape was mounted on multiple drives, then the report will list-:i}@p#iu   each drive that detected read errors associated with that Media ID.-Ji~@p.-P@pi  Time of Error: 26-Jun 06:29:54 z
j@p
j+2"pF.T.3.1.2.2.2.1.2.0.- :j	G--!j-!j

bj@p#jhere are only 6 Read Operation Data Theories and Summaries.-!Jj@pjNext on the menu are the Read Operation Device Error Theories.-"Zj@p-#X@p
j Your response please:z
j'@p
j%-
ZjwR.T.3.1.2.2.2.1.1.6.-$2j)G--$zj*-%j,
bj4@p!j-STOP - You are moving in a reverse direction thru the menu. You are-%Bj;@pj5about to back into the Read Operation Data Theories.-&Jj=@p-'8@p
j>Your response please:z
jE@pjC+tJkZ3.1.2.2.2.1.2.0.-(jGG--(ZjH-(pjJ
bjQ@pjK              TX01/02 Read Operation Device Error Theories-)"jS@p-*j[@p#jTOverview - The TX01/02 Read Operation Device Error Theories attempt to-*2jd@p!j\localize the cause of device errors that occurred during tape read -+:jl@p jeoperations (space forward, space reverse, read forward, and read-,Bjt@p jmreverse). Device errors that can not be localized are listed in a--@@pjusummary report.z
j{@p
jy-$2l7R.T.3.1.2.2.2.1.2.0.-.rj}G--/:j~-/Pk
bk@p!kSTOP - You are moving in a reverse direction thru the menu. You are-0k@pk	about to back into the Read Operation Device Theory Overview.-1
k@p-2@p
kYour response please:-;*k_G-z
k@pi-t
p5 -2zkG--3"k-38k
bk%@pk               TX01/TX02 Read Operation Device Theories-3jk'@p-4Zk*@pk(Selection Menu-4rk+@p-5"k2@pk, 0. Overview - TX01/TX02 Read Operation Device Theories-5:k4@p-6*k:@pk5 1. Tape Slippage Theory ...........[2.2.2.1]-6Bk;@p-7"kA@pk< 2. Tape Slippage Summary ..........[2.2.2.2]-7:kC@p-8kI@pkD 3. Vacuum Column Sensor Summary ...[2.2.2.3]-82kJ@p-9kP@pkK 4. Device Error Summary ...........[2.2.2.4]-9*kR@p-:
kS@p-: @pkTYour selection please (topic #):.zp<G-.
hz
k@pk\-(lU(3.1.2.2.2.1.2.1.-2bk`-;pkb
bkk@p$kcTheory - If a drive reports multiple velocity check errors, then chances-<"ks@p"klare the tape is slipping on the capstan due to a misadjusted capstan,-=2kz@pktlow tape column vacuum, or improper bearing pressure.->:k|@p-?*k}@p-?Bl@pk~  Read Data - Tape Slippage Theory ... [2.2.2.1]-?Zl@p-@Bl@pl    MT100 (TU72, SN:32896.) reports:-@Zl
@p-A2l@p#lhich indicate a possible Capstan misadjustment-AJl@p-BRl@p	l  Additional Data:-Bjl@p-C"l@p
l    Media id    : TEST  -C:l!@p-Czl)@pl"  Time: 29-Mar 00:00:00  To 29-Mar 02:45:00   Span:   2:45:00 -Dl*@p-El,@p-E*l4@p#l-Threshold - At least six velocity check errors are required to satisfy-E@@pl5this theory.z
l<@p
l9-.rmAR.T.3.1.2.2.2.1.2.1.-Fzl=G--GBl?-GXl@
blI@p!lASTOP - You are moving in a reverse direction thru the menu. You are-H
lP@plJabout to back into the Read Data Tape Slippage Theory.-IlQ@p-J@p
lRYour response please:z
lZ@plW-;*m_*3.1.2.2.2.1.2.2.-JZl[G--K"l]-K8l^
blg@p$l_Theory - If a drive reports multiple velocity check errors, then chances-Kjlp@p"lhare the tape is slipping on the capstan due to a misadjusted capstan,-Lzlw@plqlow tape column vacuum, or improper bearing pressure.-Nlx@p-Nrlz@p-O
m@pl{  Read Data - Tape Slippage Summary ... [2.2.2.2]-O"m@p-P
m@pm    MT100 (TU72, SN:32896.) reports:-P"m	@p-Pzm@pm
    5. Velocity Checks which indicate a possible dirty Capstan.-Qm@p-Rm@p	m  Additional Data:-R*m@p-Rbm@p
m    Media id    : TEST  -Rzm@p-S:m%@pm  Time: 29-Mar 00:00:00  To 29-Mar 02:15:00   Span:   2:15:00 -SRm&@p-TRm(@p-Tjm0@p"m)Threshold - Only drives with less than six velocity check errors are-Um9@p$m1identified by this report. Drives with six or more velocity check errors-V@pm:will be identified under the Tape Slippage Theory [2.2.2.1].z
mE@p
mC-Fzn)R.T.3.1.2.2.2.1.2.2.-XmGG--XZmH-XpmJ
bmR@p!mKSTOP - You are moving in a reverse direction thru the menu. You are-Y"mY@pmSabout to back into the Read Data Tape Slippage Summary.-Z*m[@p-[@p
m\Your response please:z
mc@pma-JZnH3.1.2.2.2.1.2.3.-[rmeG--\:mf-\Pmh
bmp@p#miThis report summarizes vacuum column error checks that occurred during-]mt@p
mqdata read operations.-^
mv@p-^Jm}@pmw  Read Data - Vacuum Column Sensor Summary ...[2.2.2.3]-^bm~@p-_Rn@pm    MT100  (TU72, SN: 32896.) reports:-_jn@p-`Bn
@p                Left	Right	-`Zn@pn    Top/Bottom  col.	 col.   No. of Times Occurred-a"n@pn    ----------  ----    ----    ----------------------b
n@p-bzn@pn	 0       0        1          5.-cn@p-cbn!@p-cx@pn"  Time: 29-Mar 00:00:00  To 29-Mar 02:15:00   Span:   2:15:00 z
n-@p
n+-Xp7R.T.3.1.2.2.2.1.2.3.-en/G--eZn0-epn2
bn:@p!n3STOP - You are moving in a reverse direction thru the menu. You are-f"nB@pn;about to back into the Read Data Vacuum Column Sensor Summary.-g*nD@p-h(@p
nEYour response please:z
nL@pnJ-[ro (3.1.2.2.2.1.2.4.-inNG--iJnO-i`nQ
bnY@p!nRThis report summarizes device errors that occurred during read data-jnb@p#nZoperations. The errors are summarized by drive and  device error status-knf@pncbit combinations.-l*ng@p-lbnn@pnh  Read Data - Device Error Summary ...[2.2.2.4]-lzno@p-mbnt@pnp    MT300 (TU70, SN:0.) reports:-mznv@p-nJnz@pnw      0  Buss Out Check-nbn}@pn{      0  Overruns-o"o@pn~      1  C/P Comp-oZo@p	o      0  Reject TU-po@p	o      0  Reset Key-pJo
@p
o	      0  Cmnd Stat Reject-qo@p
o  0  Tach Start Fail-qBo@p-ro@powith  1. occurrence at Time: 17-Jan 22:42:49 -ro@p-rzo@p-s@poThe definition of these status bits follow:z
o%@p	o"-ik&3.1.2.2.2.1.2.4.A.-t
o&G--tRo(-tho)
bo2@p#o*Bus Out Check (sense byte 0, bit 2) - means that a Bus-out parity error-uo7@po3was detected by the controller.-v*o9@p-vzoB@p$o:Overrun (sense byte 0, bit 5)  - means that the tape controller transfer-woG@poCrate exceeded the channel transfer rate.-x"oI@p-xzoQ@p"oJReject TU (sense byte 4 bit 1) - Refer to the STC Maintenance Manual.-yoS@p-zo\@p#oTCommand Status Reject (sense byte 0, bit 0) - means that the tape drive-z2od@p"o]failed to return the proper command status (causes Reject TU to set).-{Bof@p-|Jon@p"ogTach Start Fail (sense byte 10, bit 5) - means that the drive did not-|bos@poodetect a Tach Status change.-}jot@p-~2o}@p#ouReset Key (sense byte 7, bit 3) - means that the Reset push button was-~Jp@po~pressed after start of operation. -Rp@p."p
@p#pC/PbCompareo(senseebyte3,zbit 7) - means that a data path parity error.8@pp
p@p
p- :qM
F.T.3.1.2.2.2.1.3.1..pG-.bp.xp
bp#@p$pThat's it. There are only two Read Operation Device Theories and two Data.*p+@p p$Operation Summary Reports. Next on the menu is the Read Operation.:p/@p
p,Software Summary Report..:p1@p.x@p
p2Your response please:z
pY@ppV-2z]k(z
kX@pp9-eqlR.T.3.1.2.2.2.1.2.4.A.-;
p>.Hp?
bpH@p!p@STOP - You are moving in a reverse direction thru the menu. You are.zpO@ppIabout to back into the Read Operation Device Error Theories..	pQ@p.	x@p
pRYour response please:3.1.2.2.2.2.0.1.&@3.1.2.2.2.1.3.1..RpZG-.p\.(p]
bpf@p#p^This report summarizes magtape errors thought to be caused by software..Zpo@p#pgFor example: A Read Reverse operation issued while the tape was at BOT.
jpt@pppwouldbeconsideredaa softwareoerror..re error summary ... [2.2.3.1].bp@p.Zq@pqMT404  (TU72, SN: 28411.) reports:.rq@p.Bq@pqSense Byte  Media   No. of					  SPAN  .Zq@pq
0 (octal)    ID     Errors		Window			HH:MM:SS.2q@pq----------  -----   ------		------			--------.q@p.rq!@p$q     0       unk.     2.  24-Jun 12:37:53 - 24-Jun 12:37:54      0:00:01 .
q*@p$q"     0     6258       2.  25-Jun 00:56:07 - 25-Jun 00:56:08      0:00:01 .q3@p$q+     0     9494       2.  25-Jun 01:16:35 - 25-Jun 01:16:36      0:00:01 .*q7@p	q4-------------------.:q@@p$q8The report continues to list each drive associated with software errors..rqC@p	qA-------------------.qE@p.8@pqF  Time: 24-Jun 12:37:53  To 30-Jun 02:41:49   Span: 134:03:56 z
qQ@p	qO.vDF.T.3.1.2.2.2.2.0..RqSG-.qT.0qV
bq^@p!qWThat's it. There is only one Read Operation Software Error Summary.bqg@p!q_Report. Next on the menu are the TX01/02 Write Operation Theories..jqh@p.p@p
qiYour response please:z
qq@p
qn.zr4R.T.3.1.2.2.2.1.3.1..JqrG-.qt.(qu
bq~@p!qvSTOP - You are moving in a reverse direction thru the menu. You are.Zr@p"qabout to back into the Read Operation Software Error Summary Report..br@p. h@p
r	Your response please:.&Jr9G-z
r@ppT+]:s
.!ZrG-."r."r
br@pr               TX01/02 Write Operation Theories."Jr@p.#2r%@p"rOverview - The TX01/02 Write Operation Theories are based on the type.#Jr-@p"r&of errors that occur during tape write operations (i.e., Data errors,.$P@pr.Device errors, or Software errors.3.1.2.2.2.2.M.2.1xz
r
@p	r6.JsRR.T.3.1.2.2.2.2.0..!Br:.'r<
brD@p!r=STOP - You are moving in a reverse direction thru the menu. You are.'BrK@prEabout to back into the Write Operation Theory Overview..(JrM@p.)8@p
rNYour response please:.2sG-z
rU@pr2/W.*RrX.*hrY
br`@prZ               TX01/TX02 Write Operation Theories.+ra@p.,rh@prb 0. Overview - TX01/02 Write Operation Theories.,ri@p.-rr@p$rj 1. TX01/02 Write Operation Data Theories ......[2.2.4.1] thru [2.2.4.2].-rt@p..*r}@p$ru 2. TX01/02 Write Operation Device Theories ....[2.2.5.1] thru [2.2.5.4]..Br~@p./Rs@pr 3. TX01/02 Write Operation Software Summary ...[2.2.6.1]./js@p.0bs	@p.0x@ps
Your selection please (topic #):.QRuG-.U@z
rQ@ps.!Zt3.1.2.2.2.2.1.0..*s.2Hs
bs@ps           TX01/TX02 Write Operation Data Theories.2zs@p.3bs(@p#s Overview - This set of theories apply only to errors that are directly.3zs0@p#s)related to writing. The transport must report the occurrence of a read.5s9@p#s1after write (Data Check) error without the occurrence of a device error.6
sA@p s:(i.e., all other error bits in Sense Byte Zero (0) must be zero)..7sC@p.8sL@p$sDThe DX10 and the DX20 read after write operations are: Write, Write Tape.80@psMMark, Erase Gap, and Data Security Erase.z
sV@p
sT.&Ju3.1.2.2.2.2.1.0..:"sXG-.:jsY.;s[
bsc@p!s\STOP - You are moving in a reverse direction thru the menu. You are.;2sj@psdabout to back into the Write Operation Theory Overview..<:sl@p.=(@p
smYour response please:z
st@psr.dvb3.1.2.2.2.2.1.M..>svG-.>Jsw.>`sy
bs@psz        TX02/02 Write Operation Data Theories.?t@p.?rt@pt 0. Overview - TX02/02 Write Operation Data Theories.@
t	@p.@zt@pt
 1. Bad Media Theory .........[2.2.4.1].At@p.Ajt@pt 2. Media Bad Spot Summary ...[2.2.4.2].Bt@p.BZt@p.Bp@ptYour selection please (topic #):z
t"@pt.2tp"3.1.2.2.2.2.1.1..CZt#G-.D"t%.D8t&
bt/@p#t'If a medium is involved in more than 50 (read after write) errors, then.Djt8@p#t0chances are the medium is either dirty or worn and should be cleaned or.Ezt;@pt9replaced..G
t<@p.G2tB@pt=  Write Data - Bad Media Theory ... [2.2.4.1].GJtD@p.H*tI@ptE    Media ID: FICHE was associated with.HBtR@p#tJ    174. read after write errors while mounted on the following drives:.ItT@p.J*tX@ptU	MT300  (TU70, SN: 0.).JBtY@p.Kt]@p
tZ    Additional Data:.Kt^@p.KRtc@pd    Program ID  :DUMPER.L2th@p.Lp@pti  Time: 14-Jan 15:48:16  To 18-Jan 20:33:03   Span: 100:44:47 z
tu@p	tr.CZu
3.1.2.2.2.2.1.1.A..N
tvG-.NRtx.Nhty
bu@p#tzThreshold - At least 50 read after write errors are required to satisfy.O@p uthis theory. All 50 errors must pertain to the same reel of tape.z
u.@pu,.N
v!(z
s@pu.:"vdR.T.3.1.2.2.2.2.1.1.A..1bu.R u
bu@p!uSTOP - You are moving in a reverse direction thru the menu. You are.RRu%@puabout to back into the Write Operation Bad Media Theory..SZu&@p.TP@p
u'Your response please:.lJviG-.p03.1.2.2.2.2.1.2..Q*u0G-.Uju1.Vu3
bu;@p#u4This report summarizes all (read after write) data errors that did not.V2uD@p#u<meet the threshold established for the Bad Media Theory [2.2.4.1]. The.W:uL@p"uEreport lists the drive, the medium, and number of (read after write).XBuQ@puMerrors associated with the medium..YJuS@p.ZuZ@puT  Write Data  - Media Bad Spot Summary ... [2.2.4.2].Z2u[@p.["u`@pu\MT301  (TU70, SN: 0.) reports:.[:ua@p.\ug@pubMedia  No. of      				     SPAN    Program.\um@puh ID    Errors		Window		   	   HH:MM:SS     ID.\zuv@p"un-----  ------           ------                     --------  ------- .]Zu|@puw6638      1.   11-Mar 00:33:50				     DUMPER.^bv@p"u}7099      3.   11-Mar 02:01:11 TO 11-Mar 02:05:00   0:03:49  DUMPER	._Bv
@pv7921      1.   12-Mar 04:53:23				     TAPE20.`Jv
@p.a*v@pvvThe report will continue to list all write errors by drive..arv@pv---------------.bh@pv    Time: 11-Mar 00:33:50  To 12-Mar 12:19:06   Span:  35:45:16z
v&@p	v#.Q*sp3.1.2.2.2.2.1.2.A..dv'G-.dbv).dxv*
bv3@p#v+Note: Since rewind operations are not currently recorded in the system.e*v;@p!v4event file some bad spots may have been counted more than once. You.f0@p#v<should take this into consideration before disgarding the reel of tape.z
vI@p
vF.R}F.T.3.1.2.2.2.2.2.0..hJvJG-.ivL.i(vM
bvV@p$vNThat's it. There are only two Write Operation Data Theories. Next on the.iZv\@pvWmenu are the Write Operation Device Theories..jjv^@p.kH@p
v_Your response please:z
w@pw.>xz
u*@pvf.QRw:R.T.3.1.2.2.2.2.1.2.A..U*vk.mvl
bvu@p!vmSTOP - You are moving in a reverse direction thru the menu. You are.mJv|@pvvabout to back into the Write Operation Data Theories..nRv}@p.o@@p
v~Your response please:/W*}?G-/[ 3.1.2.2.2.2.2.0..l"wG-.pZw.ppw

bw@pwn a summary reTX01/02Write Operation Device Error Theories.q"w@p.rw@p#wOverview - The TX01/02 Write Operation Device Error Theories attempt to.r2w$@p"wlocalize the cause of device errors that occurred during tape write .sBw-@p"w%operations  (i.e., write file mark, write check forward, write check.tJw6@p$w.reverse, and write forward). Device errors that can not be localized are.uP@p
w?@p
w<.lJxuR.T.3.1.2.2.2.2.2.0..w*w@G-.wrwB.xwC
bwL@p!wDSTOP - You are moving in a reverse direction thru the menu. You are.x:wT@p"wMabout to back into the Write Operation Device Error Theory Overview..yBwV@p.zH@p
wWYour response please:z
w^@pw\/Kr}83.1.2.2.2.2.2.M..{"w`G-.{jwa.|wc
bwj@pwd            TX01/TX02 Write Operation Device Theories.|2wk@p.}"wq@pwl 0. Overview - Write Device Theories.}:wr@p.~wx@pws 1. Tape Slippage Theory ...........[2.2.5.1].~*wz@p.
x@pw{ 2. Tape Slippage Summary ..........[2.2.5.2]."x@p/x@px 3. Vacuum Column Sensor Summary ...[2.2.5.3]/x	@p/zx@px
 4. Device Error Summary ...........[2.2.5.4]/x@p/rx@p/@pxYour selection please (topic #):z
x@px.l"y(3.1.2.2.2.2.2.1./rxG-/:x/Px 
bx)@p$x!Theory - If a drive reports multiple velocity check errors, then chances/x1@p"x*are the tape is slipping on the capstan due to a misadjusted capstan,/x8@px2low tape column vacuum, or improper bearing pressure./x:@p/
x;@p/"xB@px<  Write Data - Tape Slippage Theory ... [2.2.5.1]/:xC@p/"xI@pxD    MT100 (TU72, SN:32896.) reports:/:xJ@p/	xS@p#xK    7. Velocity Checks which indicate a possible Capstan misadjustment/	*xT@p/
2xX@p	xU  Additional Data:/
JxY@p/x]@p
xZ    Media ID    : TEST  /x_@p/Zxg@px`  Time: 29-Mar 00:00:00  To 29-Mar 02:45:00   Span:   2:45:00 /rxh@p/
rxj@p/
xr@p#xkThresholdo-yAtleast six velocity check errors are required to satisfy/
xz@p
xw.w*yxR.T.3.1.2.2.2.2.2.1./Zx{G-/"x}/8x~
by@p!xSTOP - You are moving in a reverse direction thru the menu. You are/jy@pyabout to back into the Write Operation Tape Slippage Theory./ry@p/h@p
yYour response please:z
y@py/rz(3.1.2.2.2.2.2.2./ByG-/
y/ y
by&@p$yTheory - If a drive reports multiple velocity check errors, then chances/Ry.@p"y'are the tape is slipping on the capstan due to a misadjusted capstan,/by5@py/low tape column vacuum, or improper bearing pressure./jy7@p/Zy8@p/ry?@py9  Write Data - Tape Slippage Summary ... [2.2.5.2]/
y@@p/ryF@pyA    MT100 (TU72, SN:32896.) reports:/
yG@p/byO@pyH    5. Velocity Checks which indicate a possible dirty Capstan./zyQ@p/zyT@p	yR  Additional Data:/yV@p/JyZ@p
yW    Media ID    : TEST  /by[@p/"yc@py\  Time: 29-Mar 00:00:00  To 29-Mar 02:15:00   Span:   2:15:00 /:ye@p/:yf@p/Ryo@p"ygThreshold - There are no thresholds associated with this theory. The/h@p#ypreport identifies each drive that reported less than 6 velocity checks.z
y|@p
yz/ZzcR.T.3.1.2.2.2.2.2.2./y~G-/Jy/`z
bz	@p!zSTOP - You are moving in a reverse direction thru the menu. You are/ z@pz
about to back into the Write Operation Tape Slippage Summary./!z@p/"@p
zYour response please:z
z@pz/B{ 3.1.2.2.2.2.2.3./"rzG-/#:z/#Pz 
bz(@p#z!This report summarizes vacuum column error checks that occurred during/$z,@p
z)data read operations./%
z.@p/%Jz/@p/%bz7@pz0  Write Data - Vacuum Column Sensor Summary ... [2.2.5.3]/%zz8@p/&rz>@pz9    MT100 (TU72, SN:32896.) reports:/'
z?@p/'bzD@pLeft	Right	/'zzJ@pzE    Top/Bottom  col.	 col.   No. of Times Occurred/(BzQ@pzK    ----------  ----    ----    ---------------------/)*zS@p/*zX@pzT	 1       0        0          5./*2zY@p/+z[@p/+@pz\  Time: 29-Mar 00:00:00  To 29-Mar 02:15:00   Span:   2:15:00 z
zg@p
ze/}:R.T.3.1.2.2.2.2.2.3./,2ziG-/,zzj/-zl
bzt@p!zmSTOP - You are moving in a reverse direction thru the menu. You are/-Bz}@p"zuabout to back into the Write Operation Vacuum Column Sensor Summary./.Jz~@p//P@p
zYour response please:z
{@p{/"r{f,3.1.2.2.2.2.2.4./0*{G-/0r{
/1{
b{@p"{
This report summarizes device errors that occurred during write data/1:{@p!{operations. The errors are summarized by drive and error status bit/2B{@p{combinations./3J{!@p/3z{'@p{"  Write Data - Device Error Summary ... [2.2.5.4]/4{)@p/4z{.@p{*    MT302 (TU70, SN:0.) reports:/5{/@p/5b{3@p{0      0  Overruns/5z{6@p	{4      0  Reject TU/62{:@p
{7      0  C/PtCompare/6j{>@p{;@p  0  Write Trg VRC/7"{B@p
{C      0  DSEsFailure/8*{J@p/8b{N@p
{K      0  Cmnd Stat Reject/9*{S@p{O      1  Record Not Detected/9j{W@p
{T      0  Tach Start Fail/:2{X@p/:r{\@p{Ywith  9. occurrences in/;
{^@p/;H@p{_     Time : 11-Mar 00:47:04 - 12-Mar 10:14:10  span  33:27:06z
{j@p	{h/0*|_*3.1.2.2.2.2.2.4.A./<b{lG-/=*{m/=@{o
b{w@p{pBackground - Ten detectors monitor for TX01/02 device errors:/=r{x@p/>r|@p"{yOverrun (sense byte 0, bit 5) - means that the channel transfer rate/?
|@p|exceeded tape controller transfer rate./@|@p/@j|@p"|	Reject TU (sense byte 4, bit 1) Refer to the STC Maintenance Manual./A|@p/B
|@p#|Command Status Reject (sense byte 0, bit 0) - means that the tape drive/B"|#@p"|failed to return the proper command status. (causes Reject TU to set)/C2|%@p/D:|.@p#|&Record Not Detected (sense byte 10, bit 3) Refer to the STC Maintenance/DR|0@p|/Manual./Eb|2@p/F
|:@p"|3Tach Start Fail (sense byte 10, bit 5) - means that the drive did not/F"|?@p|;detect a Tach Status change./G*|@@p/Gr|I@p!|ADSE Fail (sense byte 7, bit 4) - means that the data security erase/H
|O@p|Jcommand failed to reach a normal termination. /I|Q@p/Iz|Z@p#|RC/P Compare (sense byte 3, bit 7) - means that a data path parity error/J@p|[was detected by the controller.			z
|c@p	|a/<bwZ3.1.2.2.2.2.2.4.B./Kr|eG-/L:|f/LP|h
b|q@p$|iErase Head Fail - means that the drive did not detect erase head current/M|v@p|rduring a write or erase operation./N|w@p/Nb}@p$|xWrite Current Fail (sense byte 6, bit 1) - means that the drive detected/Nz}@p}erase current during a read operation./P
}@p/Pb}@pe}WriteTrigger VRC (sense byte 4, bit 3) means that bad parity was/Px@p
}@p
}.hJ~M
F.T.3.1.2.2.2.2.3.1./RB}G-/S
}/S }
b}%@p"}That's it. There are only two Write Operation Device Theories and two/SR}.@p$}&Write Operation Summary Reports. Next on the menu is the Write Operation/TZ}2@p}/Software Error Summary./Uj}4@p/V(@p
}5Your response please:z
}\@p}Z.{"rR&z
w@p}</,2~lR.T.3.1.2.2.2.2.2.4.B..p}A/Wx}B
b}K@p!}CSTOP - You are moving in a reverse direction thru the menu. You are/X*}S@p}Labout to back into the Write Operation Device Error Theories./Y2}T@p/Z0@p
}UYour response please:3.1.2.2.2.3.0.20p3.1.2.2.2.2.3.1./W}^G-/[J}_/[`}a
b}j@p#}bThisyreportdsummarizesfmagtapeSerrors/thoughttobecausedaby software./\}r@p"}kForMexample:apWrite~operation-issued-while-the-tape-was	at-EOT-would/]"}w@p}sbe0considered.a software4error./^*}y@p/^z~@p}z0:Write/Data-pSoftware Error Summary ... [2.2.6.1]/0~@p/`~@p~MT3000:(TU70,dSN:0.)$reports:/`~@p/`b~2.  25-Jun 01:16:35 - 25-Jun 01:16:36      0:00:01 /e2~7@p	~5-------------------/fB~@@p$~8The report continues to list each drive associated with software errors./fz~D@p	~A-------------------/h
~E@p/h@@p~F  Time: 24-Jun 12:37:53  To 30-Jun 02:41:49   Span: 134:03:56 z
~R@p	~O/RCLF.T.3.1.2.2.2.3.0./iZ~SG-/j"~U/j8~V
b~_@p"~WThat's it. There is only one Write Operation Software Summary Report./jj~f@p~`Next on the menu are the DX20 - TX01/02 Massbus Theories./kr~h@p/lh@p
~iYour response please:z
~p@p
~n/W+SR.T.3.1.2.2.2.2.3.1./mB~rG-/n
~s/n ~u
b~}@p!~vSTOP - You are moving in a reverse direction thru the menu. You are/nR@p"~~about to back into the Write Operation Software Error Summary Report./oZ@p/p`@p
Your response please:0{,G-z
@p}X.*+',/qRG-/qz/r
b@p       DX20 - TX01/TX02 Massbus (control bus/data bus) Theories/rB@p/sB%@p Overview - There are ten Massbus theories. The first two theories/sZ.@p"&attempt to localize the cause of Massbus (control bus) parity errors/tZ6@p!/and Massbus (control bus) timeouts to either the Massbus controller/ub<@p7(RH11 or RH20) or the Adapter (DX20)./vj=@p/wBF@p#>  RH20 controllers have a single bit: Register Access Error(RAE), which/wZO@p#G  indicates that either a Massbus (control bus) parity error or timeout/xjV@pP  occurred during an external register read or write./yzX@p/zj`@p"Y  RH11 controllers have two bits: RH Control Bus Parity Error (RHCPE)/{i@p"a  and Non-Existent Drive (NED). These bits indicate Massbus (control/|
q@p"j;bus)parity errors and Massbus (control bus)0timeoutsBrespectively./}s@p/~{@p"teUBA <--- RARH11<--Massbus  CEDX20<--Chan-Bus C/TXxx <-TU-Bus-0Drive/~3@pw|-readRA<----PE/TO-<--------- -CERR--<---------  C/P----<--------2/;@p: write ---> no ck ----------> CERR  --------->  BO CK  --------> 0;
@p)/qS 3.1.2.2.2.3.0.A./q;-0@/
c7@p#0The next six Massbus theories attempt to localize the cause of Massbus0s?@p 8(data bus) parity errors to either; the MBox or UBA, the Massbus0{F@p@Controller (RH11, or RH20), or the Adapter (DX20).0{G@p0cP@p$H Both Massbus controllers (RHs) and Massbus devices (DX20s) check parity0{Y@p#Q on the Massbus (data bus). The parity is checked during read and write0
^@pZ operations as illustrated below.0`@p0ka@p0
j@p"b UBA        RH11   Massbus    DX20   Chan Bus   TXxx   TU Bus   Drive0
r@p k reade <--- DPEck <---------> CERR  <---------  C/PCK <-------- 0#{@p0#@p"| MBox       RH20    Massbus   DX20   Chan Bus   TXxx   TU Bus   Drive0;
@p>read  <----DPE---<-----------CERR-><-----------C/P-><--------0@@p3.1.2.2.2.3.0.B.0CG-00 
c%@pThe last two reports summarize DX10/20 Data Channel Bus Errors.0S&@p0S-@p' Mem       DX10  Chan Bus  TXxx   TU Bus    Drive0k3@p. read <--- CERR <--------- C/P   <--------0S9@p4 write---> no ck---------> BO CK -------->03:@p0C@p#;  MBox      RH20    Massbus   DX20   Chan Bus   TXxx    TU Bus   Drive0+K@pD read  <--- DPE   <---------  CERR  <---------  C/P   <--------00@p L write ---> DPE   ----------> CERR  --------->  BO CK  -------->zW@p
U/mC7R.T.3.1.2.2.2.3.0.B.03YG-0{Z0\
cd@p!]STOP - You are moving in a reverse direction thru the menu. You are0Ck@peabout to back into the Massbus Theory Overview.0Kl@p00@p
mYour response please:0:{\G-zt@p%2(
,0#vG-0Kw0`y
c@p!z       DX10/20 Massbus (control bus/data bus) and Channel Theories0@p0 @pSelection menu0 3@p0 c@p 0. Overview - Massbus (control bus/data bus) Theories0 {@p0!k@p" 1. Massbus (control bus) RH Theory .......................[2.2.7.1]0"!@p" 2. Massbus (control bus) DX Theory .......................[2.2.7.2]0#"@p0$+@p"# 3. Data Read/Massbus  (data bus) RH Theory (RH20 only) ...[2.2.7.3] 0$+3@p", 4. Data Read/Massbus  (data bus) DX Theory (RH20 only) ...[2.2.7.4]0%35@p0&;=@p"6 5. Data Write/Massbus (data bus) MBox Theory .............[2.2.7.5]0&SF@p"> 6. Data Write/Massbus (data bus) RH Theory ...............[2.2.7.6]0'[N@p"G 7. Data Write/Massbus (data bus) RH Theory ...............[2.2.7.7]0(cW@p"O 8. Data Write/Massbus (data bus) Lone Drive Theory .......[2.2.7.8]0)kX@p0*sa@p"Y 9. Channel Error Summary .................................[2.2.7.9]0+i@p"b10. Channel Buffer Theory .................................[2.2.7.10]0,k@p0-l@p0-0@pmYour selection please (topic #):zu@ps0CW3.1.2.2.2.3.1.0.wG-0.[x0.pz
c@p${Theory - If a tape subsystem reports Massbus (control bus) parity errors0/#@p"or Massbus timeout errors, and if the errors involve two or more DX20003@p#
Adapters, then3chances)arepthesfault6lies@intheRH Massbusbcontroller01;@p$orotheaMassbusecable. If,0however,theerrorslarenlocalttolaesingle2DX2002C%@p#thenechancesare@thefault9isOinptheDX20 andEhasrsomething5toDwith do03S*@p&theMassbusinterfacerlogic.04[+@p05#3@p,RH1CBUS.Error.-0Massbus(controlbus).RHtheory.[2.2.7.1]05;4@p0639@p
cg@p!`Threshold - At least two (RH detected) Massbus (control bus) parity0;sp@p"herrors or Massbus (control bus) timeouts are required to satisfy this0<{y@p#qtheory. In addition, the errors must involve two or more DX20 Adapters.0>@p!zThe report identifies the controller, the number of DX20s that were0?
@p!involved, and the total number of Massbus (control bus) errors that0@
@poccurred.0A#@p0AK@p!MBox/UBA    RHxx  Massbus    DX20   Chan Bus  TXxx   TU Bus   Drive0Ac@p0Bk@p<rd/wr> --- CPE  <------->.- CBPE <----------       <------0C%@p                           !                  0C{-@p&                          !_ CBPE <----------       <------0D[.@p0ES0@p0Eh@p1Background - Refer to the Massbus Theory Overview. z;@p	903jR.T.3.1.2.2.2.3.1.0Fs=G-0G;>0GP@
cH@p!ASTOP - You are moving in a reverse direction thru the menu. You are0HO@pIabout to back into the Massbus (control bus) RH Theory.0IQ@p0Ix@p
RYour response please:0_[G-zY@pU22c20JkZG-0K\0K(]
cf@p$^Theory - If a tape subsystem reports Massbus (control bus) parity errors0K[o@p"gor Massbus timeout errors and if the errors involve two or more DX200Lkw@p#pAdapters, then chances are the fault lies in the RH Massbus controller0Ms@p$xor the Massbus cable. If, however, the errors are local to a single DX200N{	@p#then chances are the fault is in the DX20 and has something to do with0P
the Massbus interface logic.0Q@p0Q[@p#RH CBUS Error - Massbus (control bus) DX20 Controller Theory [2.2.7.2]0Qs@p0R{@p  MT315 (TU70, SN: 0) was identified with0S&@p   4.  Massbus (control bus) Parity Errors detected by0Ss.@p!'  Controller (Adapter) no: 1 (DX20) connected to channel 3 (RH20).0Tc0@p0Uk8@p1  Time: 29-Mar 00:30:00  To 29-Mar 02:15:00   Span:   1:44:60 0V9@p0WB@p#:Note: If the system only has one DX20 tape subsystem then the fault may0WK@p!Clie in either the RH20 or the Massbus interface logic in the DX20.0X+S@p!LThreshold - One or more (RH detected) Massbus (control bus) parity0Y3\@p"Terrors or Massbus (control bus) timeouts are required to satisfy this0Z;e@p#]theory. In addition, all the errors must involve the same DX20 Adapter.0[Cm@p fThe report identifies the data channel and the number of Massbus0\Sr@pn(control bus) errors that occurred.0]Ss@p0^#u@p0^8@pvBackground - Refer to the Massbus Theory Overview.3.1.2.2.2.3.3.30q8zU@p	2=+pR.T.3.1.2.2.2.3.2.0JS0` 
cp!STOP - You are moving in a reverse direction thru the menu. You are0`S@pabout to back into the Massbus (control bus) DX theory.0a[@p0bH@p
Your response please:0qCG-z@p{0Jk
$0c;G-0cc!0cx"
c+@p"#TheoryH-0Ifraptape:subsystem@reportscMassbusM(datasbus)tparity errors0d+3@p",duringhdatareads,@andifthe errorslinvolvecmultiplerDX20dAdapters,0e3<@p#4thenchancesarethefault lies inreither the1(RH20)2MassbusTcontroller0f;E@p!=ortheMassbus cable. If,ohowever,2the errors involve0a single0DX200gKM@p"Fthen,chances:are-the fault:liesTin2theaDX20:and1has something:to:do0hSR@pNwithPthezMassbusinterfacelogic.0i[T@p0j+\@p"URHDPEError-Data Read/Massbus (data bus) RH theory ... [2.2.7.3]0jC^@p0kKb@p
c@p#Threshold - At least two (RH detected) Massbus (data bus) parity errors0r;%@p$are required to satisfy this theory. The errors must involve two or more0sK.@p$&(DX20) Adapters and they must have occurred during data read operations.0t[7@p"/The report identifies the RH controller and the number of DX20s that0uk?@p"8were involved. The report also lists the number of Massbus (data bus)0vsD@p@parity errors that occurred.0w{E@p0xCN@p#FMBox/UBA    RHxx    Massbus    DX20   Chan Bus    TXxx   TU Bus   Drive0x[P@p0ykX@pQ <read  --- DPE   <---------.- DBPE <------------ D CK  <------0z^@pY                            !                  0{f@p_                            !_ DBPE <------------ D CK <------0{kh@p0|ki@p0}@pjBackground - Refer to the Massbus Theory Overview.zt@p
r0_[	bR.T.3.1.2.2.2.3.3.A.0~vG-0~Kw0~`y
c@p!zSTOP - You are moving in a reverse direction thru the menu. You are0@pabout to back into the Massbus (data bus) RH Theory.1
@p1@p
Your response please:1[	
G-z@p	0qC	"1{G-1#18
c@p"Theory - If a tape subsystem reports Massbus (data bus) parity errors1k'@p" during data reads, and if the errors involve multiple DX20 Adapters,1s0@p#(then chances are the fault lies in either the (RH20) Massbus controller1{9@p!1or the Massbus cable. If, however, the errors involve a single DX201A@p":then, chances are the fault lies in the DX20 and has something to do1F@pBwith the Massbus interface logic.1H@p1kP@p#I  RH DPE Error - Data Read/Massbus(data bus) DX20 Theory ... [2.2.7.4]1	R@p1
X@pS  MT100  (TU70, SN: 0.) was identified with1
#^@pY  4. Massbus (data bus) Parity Errors detected by1g@p"_  Controller (Adapter) no: 0. (DX20) connected to channel 1. (RH20).1kh@p1
sp@pi1Time:p29-Mars00:45:00 tTo 29-Mar 02:15:00 onSpan:0 t1:30:00s1m then the fault may1 @p!|lie in either the RH20 or the Massbus interface logic in the DX20.3.1.2.2.2.3.5.312Pz@p	1{
3.1.2.2.2.3.4.A.1c	1 	
c	@p#	Threshold - One or more (RH detected) Massbus (data bus) parity errors1S	@p"	are required to satisfy this theory. The errors must involve the same1[	'@p#	(DX20) Adapter and they must have occurred during data read operations.1c	/@p#	(The report identifies the data channel and lists the number of Massbus1s	5@p	0(data bus) parity errors that occurred.1{	6@p1S	?@p#	7MBox/UBA    RHxx    Massbus    DX20   Chan Bus    TXxx   TU Bus   Drive1k	A@p1{	I@p	B <read  --- DPE   <---------.- DBPE <------------ D CK  <------1	O@p	J                            !                  1	X@p"	P                            !_ other error free DX20 tape subsystems 1{	Y@p1	[@p1@p	\Background - Refer to the Massbus (data bus) Introduction.z	g@p
	d0~
R.T.3.1.2.2.2.3.4.A.1+	hG-1s	j1	k
c	t@p!	lSTOP - You are moving in a reverse direction thru the menu. You are1;	{@p	uabout to back into the Massbus (data bus) DX20 Theory.1C	|@p10@p
	}Your response please:12[G-z
@p	1[,1 #
G-1 K
1 `
	
c
@p"

Theory - If a system reports Massbus (data bus) parity errors during 1!
@p"
data writes, and if those errors involve multiple Massbus controllers1"
"@p
(RH11/20), then chances are the fault has to do with the memory1##
*@p!
#controller or the channel. If, however, the errors involve a single1$#
3@p#
+Massbus controller and multiple (DX20s) Adapters, then chances are the1%+
;@p"
4fault lies in the Massbus controller or the Massbus. Finally, if the1&3
D@p"
<errors involve a single DX20, then the fault is probably in the DX201';
K@p
Eand has something to do with the Massbus interface logic.1(C
M@p1);
V@p$
N  RH DPE Error - Data Write/Massbus(data bus) MBOX (UBA) theory [2.2.7.5]1)S
W@p1*c
`@p#
X     2. different RH controllers report: (during data Write operations)1*{
f@p
a     5. Massbus (data bus) Parity Errors.1,
h@p1,k
k@p	
i  Additional Data:1-
m@p1-;
t@p
n  RH NO: 1. (RH20) reports (during Data Write operations)1-S
{@p
u     3. (RH detected) Massbus (Data Bus) Parity Errors.1.K@p
|  RH NO: 2. (RH20) reports (during Data Write operations)1/;
@p     2. (RH detected) Massbus (Data Bus) Parity Errors.103@p11 @p
  Time: 29-Mar 00:00:00  To 29-Mar 02:15:00   Span:   2:15:00 3.1.2.2.2.3.6.31R@z
@p1 #
"$3.1.2.2.2.3.5.A.1 13 
c&@p#Threshold - At least two (RH detected) Massbus (data bus) parity errors13S/@p$'are required to satisfy this theory. The errors must involve two or more14c8@p$0RH controllers and they must have occurred during data write operations.15s@@p"9The report lists the number of Massbus (data bus) parity errors that17I@p"Aoccurred and the number of different controllers that were involved.18J@p19L@p19+T@p!M MBox         RH20  Massbus   DX20  Chan Bus  TXxx  TU Bus   Drive19CV@p1:K]@pW         .--> DPE ----------> DBPE  ------>  D CK   ------>1:c`@p^write>---!1;[g@pa         `--> DPE ----------> DBPE  ------>  D CK   ------>1<i@p1<{q@p!jSince RH11s do not check parity during a data write operation, this1=y@prtheory only applies to RH20/DX20 controlled tape subsystems.1>z@p1?|@p1?(@p}Background - Refer to the Massbus Theory Overview.z
@p

1+R.T.3.1.2.2.2.3.5.A.1@+
G-1@s
1A

c
@p!
STOP - You are moving in a reverse direction thru the menu. You are1A;
@p
about to back into the Massbus (data bus) MBox Theory.1BC
@p1C0@p

Your-response please:1RK
$@p12[
&G-1DK
'1D`
)
c
1@p"
*Theory - If a system reports Massbus (data bus) parity errors during 1E
:@p"
2data writes, and if those errors involve multiple Massbus controllers1F
B@p
;(RH11/20), then chances are the fault has to do with the memory1G#
J@p!
Ccontroller or the channel. If, however, the errors involve a single1H#
S@p#
KMassbus controller and multiple (DX20s) Adapters, then chances are the1I+
[@p"
Tfault lies in the Massbus controller or the Massbus. Finally, if the1J3
d@p"
\errors involve a single DX20, then the fault is probably in the DX201K;
k@p
eand has something to do with the Massbus interface logic.1LC
m@p1M;
n@p1MS
w@p#
o  RH DPE Error - Data Write/Massbus(data bus) RH theory ...  [2.2.7.6]1Mk
x@p1Ns
y@pRHNo:(1. (RH20)ereportsb(duringaData)Writetoperations)1O
@p1Q@p0  To 29-Mar 02:15:00   Span:   2:15:00 3.1.2.2.2.3.7.31t8z
@p"3.1.2.2.2.3.6.A.1D
c@p#dr-dAtoleaststwot(RHXdetected)hMassbuss(dataebus)lparityherrors1SC
1@+ R.T.3.1.2.2.2.3.6.A.1_kG-1`31`H
c@p!STOP - You are moving in a reverse direction thru the menu. You are1`{@pabout to back into the Massbus (data bus) RH20 Theory.1b@p1bp@p
Your(responseplease:1tC(G-z@p
c-@p"&Theory - If a system reports Massbus (data bus) parity errors during 1dS6@p".data writes, and if those errors involve multiple Massbus controllers1e[>@p7(RH11/20), then chances are the fault has to do with the memory1fcF@p!?controller or the channel. If, however, the errors involve a single1gcO@p#GMassbus controller and multiple (DX20s) Adapters, then chances are the1hkW@p"Pfault lies in the Massbus controller or the Massbus. Finally, if the1is`@p"Xerrors involve a single DX20, then the fault is probably in the DX201j{g@paand has something to do with the Massbus interface logic.1li@p1l{q@p"j  RH DPE Error - Data Write/Massbus(data bus) RH theory ... [2.2.7.7]1ms@p1nz@pt    RH No: 1. (RH20) reports (during Data Write operations)1n3@p{       5. Massbus (data bus) Parity Errors as detected by the1o+@p	  following drive controllers:1p+	@p1p{@p
    3. Errors detected by MT100  (DX20: 0,TU70, SN: 0.)1q@p1r@p    2. Errors detected by MT110  (DX20: 1,TU70, SN: 0.)1r@p1s@p  Time: 29-Mar 00:00:00  To 29-Mar 02:15:00   Span:   2:15:00 3.1.2.2.2.3.8.32z@p&1cc@&3.1.2.2.2.3.7.A.1cK*1u+
c4@p!,Threshold - At leasttwo{(DX20detected) Massbus (data bus) parity1u;<@p#5errors-(PAR)1are~requiredto satisfy thistheory.pTheerrors must have1vCD@pr=beenHdetectedsbystwoeormoreDX20spandtheymust@be$commonitoethe1wKM@p#EsamehRHkcontroller.yTherreporttidentifiesetheiRHscontroller,thenumber1xKV@p"NoftDX201Adapters2thatnwerelinvolved,uandsthesnumberofpDX20detected1y[\@pWMassbusf(data bus)Mparity errors thatvoccurred.1zc^@p1{Kf@p!MBox         RH20  Massbus   DX20  Chan Bus  TXxx   TU Bus   Drive1{ch@p1|ko@piwrite> ---.- DPE --------->- DBPE  ------->  D CK   ------>1}t@p
"1_k!R.T.3.1.2.2.2.3.7.A.2&G-2S(2h)
c2@p!*STOP - You are moving in a reverse direction thru the menu. You are29@p3about to back into the Massbus (data bus) RH Theory.2#:@p2@p
;Your response please:2#6G-zB@p!1tC2 2DG-2+E2@G
cO@p"HTheory - If a system reports Massbus (data bus) parity errors during 2sX@p"Pdata writes, and if those errors involve multiple Massbus controllers2	{`@pY(RH11/20), then chances are the fault has to do with the memory2h@p!acontroller or the channel. If, however, the errors involve a single2
q@p#iMassbusicontrollerMandbmultipleo(DX20s) Adapters,uthenichancesiarehthe2@p"zerrors involve a single DX20, then the fault is probably in the DX202	@pand has something to do with the Massbus interface logic.2#@p2@p!
  RH DPE Error - Data Write/Massbus(data bus) DX20 theory [2.2.7.8]23@p2;@p!     MT100  (TU70, SN: 0.) reports: (during Data Write operations)2S%@p     4. (DX20 detected) Massbus (data bus) Parity Errors.2[&@p2S(@p2h@p)  Time: 29-Mar 00:30:00  To 29-Mar 02:15:00   Span:   1:44:60 3.1.2.2.2.3.9.32/z>@p42A$3.1.2.2.2.3.8.A.2k82h9
cA@p :Threshold - One ormore(DX20pdetected) Massbus (data bus) parity2J@p#Berrors areerequiredeto2satisfythistheory.@Theerrors;mustpinvolveSthe2S@p!KsamehDX20dand theytmustrhavedoccurrededuringtdatawriteoperations.2+T@p23\@p UMBox/UBA conRHxxleMassbussubDX20emChanBus@TXxxTU Bus@pDrive2K^@p2Ke@ps write>2---aDPEsu--------.-eDBPEe -------->DCK!------->2cj@peither the RH20 or the Massbus interface logic in the DX20.2"@p2#@pBackground - Refer to the Massbus Theory Overview.z&@p
#2xR.T.3.1.2.2.2.3.8.A.2$'G-2$c)2$x*
c3@p!+STOP - You are moving in a reverse direction thru the menu. You are2%+:@p4about to back into the Massbus (data bus) DX20 Theory.2&3;@p2' @p
<Your response please:2/}G-zC@p/2#r2(EG-2(;F2(PH
cI@p2)Q@pJDX10 Data Channel Error Summary (DX10 only)... [2.2.7.9]2)R@p2*X@pS  MT260 (TX02, TU70, SN: 0) reports:2*+[@p
Y  4. Channel Errors.2+]@p2+;`@p	^-------------------2+Si@p#aThe report continues to list each drive associated with Channel errors.2,m@p	j-------------------2-n@p2-P@po  Time: 29-Mar 00:30:00  To 29-Mar 02:15:00   Span:   1:44:60 3.1.2.2.2.3.10.29@z?@p	z2$A1R.T.3.1.2.2.2.3.9.2'{~2/P
c@p!STOP - You are moving in a reverse direction thru the menu. You are20@p	about to back into the Channel Summary Report.21@p21p@p
Your response please:29KQG-z@pv0:{V22cG-2323 
c%@pWrite Device Error - DX20 Channel Error Summary ... [2.2.7.10]23S&@p24S+@p'    MT300 (TU70, SN: 0.) reports:24k/@p
,    3. Channel Errors25;1@p25{4@p	2-------------------26=@p#5The report continues to list each drive associated with Channel errors.26KA@p	>-------------------27[B@p28@pC  Time: 29-Mar 00:30:00  To 29-Mar 02:15:00   Span:   1:44:60 3.1.2.2.2.4.1.35h`z@p	N/iXNdF.T.3.1.2.2.2.4.1.22KR2:T
c]@p$UThat's it. There are only eight Massbus Theories and two Channel Summary2:Ce@p^Reports. Next on the menu is TX01/02 Control Operation Summary.2;Sf@p2<P@p
gYour response please:zo@p	l0Fs}R.T.3.1.2.2.2.3.10.2=+pG-2=sr2>s
c|@p!tSTOP - You are moving in a reverse direction thru the menu. You are2>;@p}about to back into the Massbus Channel Buffer Theory.2?C@p2@0@p
Your response please:2K#^G-z
@pJ0"\[$2A#G-2AK2A`
c@pThis report summarizes all non read/write errors.2B@p2B{@p  Control Operation Error Summary ...[2.2.8.1]2C!@p2C{(@p"  Note: Function code is in octal and without the GO bit.2D*@p2E/@p+ MT300  (TU70, SN: 0.) reports:2E#2@p	0 Media id    : unk.2Es4@p2F+9@p5  Function    No. of						  SPAN  2FC>@p:    code      Errors		Window				HH:MM:SS2GD@p?  --------    ------		------				--------2GkE@p2HCK@pF     1           1.  14-Jan 19:55:35 			2H[L@p2I3R@pM		     Error bits set in the sense bytes:2IKT@p2J(@p
U		     INTERVENTION REQD3.2.0._tapR.T.3.2.0.z@p
\;@Lnend_of_tape_theories2A`2Kha
cj@p$bThat's it. There are only 28 TX01/02 tape theories and summaries. If you2Ls@p$khave any comments or suggestions for improving the TX01/02 Tape Theories2M+w@p	tplease let us know.2N;x@p2Ns|@p
y		      				Thank you2O~@p2OK@p
						The Spear Team2Oc@p						MR1-2 S/352P@p2PS@p2Ph@p"	Press the RETURN key or type MENU to return to the Tape Theory menu.You can:..z@pWcP*2RG-2RC2RX
c@p    The BigpPicture			2]sxInputFile2S"@p				:.....2^;@p:2Sc)@p#Retrieveeaccepts event		   :    ..........:.........2T#0@p*filesrand packet files.		ASCII   : Binary2 s      :2U5@p1				   Event File         Packet File2V<@p6The Selected information	   .....:.....             :2V[C@p=in an event file can be:	   :         :             :2WKK@pDIncluded in, or Excluded	Include   Exclude        Packet2X;R@pLfrom, the output file.		   :.........:           Numbers2Y3W@pS				        :                  :2Z+^@pXOne or more Packets can		   Selection and           :2Z{e@pbe selected from a Packet	   Time Criteria           :2[kk@pffile.				        :..................:2\[o@pl				                  :2]3s@p
@psavestheyselected entries	        :2aH:.........:2`c@p   Output Filez@pX#XB!2bsG-2c2c0
c&@p!STOP - You are moving in a reverse direction thru the menu. You are2c`@p'about to back into the Retrieve Overview.z0@p.5$;PT3.2.M.2eK1G-2f32f4
c:@p5                  Spear Library - Retrieve2fK<@p2g+?@p=Topic menu:2gC@@p2gsB@p2hE@pC0. Overview2h#F@p2hSJ@p	G1. Retrieve Dialog2hkK@p2i @pL2. Retrieve Questions & AnswerszT@pR2RP,,3.2.1.2jUG-2jCW2jXX
ca@p!YThetbasicyRetrieve:dialogconsistsof2nineprompts: eight selection2kf@pbprompts and one confirmation prompt.2lh@p2lkk@piRETRIEVE mode2mn@pl-------------2m3t@po    Event or packet file (SYSTEM:ERROR.SYS): 2mcu@p2nCz@pv    Selection to be (INCLUDED):2n[|@p2o+@p
@p	2qCTimeto (LATEST): 2q
TypeOutputtmoden(ASCII):O2q[@p2r@p3.2.1.A.Report)format(SHORT):2r3@p2r{@p    Output to (DSK:RETRIE.RPT): 2s@p2s`@p
c0@pe first selection prompt:2uC2@p2v8@p3    Event or packet file (SYSTEM:ERROR.SYS): 2v#9@p2wB@p":allow you to specify the name of the input file. Retrieve accepts two2wK@p#Ctypes of files: standard system event files (such as those generated by2x#S@p"LTOPS-10, TOPS-20, or VAX/VMS systems), and Packet files generated by2y3V@pTAnalyze.2z;W@p2zc`@p$XIf you specify a system event file Retrieve will continue with the basic2z{i@p#adialog. If you specify a Packet file, however, Retrieve will switch to2|r@p$jthe Packet selection dialog. Since the Packet dialog is short (1 prompt)2}{@p#sit will be explained next. Then we will continue with the basic dialog.2~#|@p23@p$}This prompt also supports standard Help and question mark (?) responses.2H@pBefore we go on, would you like to review the Help message ?z@p54c+=*3.2.1.B.3SG-33 
c@p"If you specify a Packet file at the input file prompt, Retrieve will3S%@pprompt you for the packet numbers that you want to select.3[&@p3S.@p'    Event or packet file (SYSTEM:ERROR.SYS): DSK:A1225.PAK<CR>3k0@p3k4@p
1      Packet numbers:35@p3C>@p#6Each numbered packet contains a list of sequence numbers. The sequence3[F@p"?numbers identify the individual records that were used by Analyze as3cO@p"Gevidence to support the theories listed in the corresponding Analyze3kW@p#PReport file. There is one packet for each theory listed in the report.3	sY@p3
{a@p"ZYou can use Retrieve to translate (or save in a separate binary file)3j@p#bthe records listed in the packet files. Typically, you would translate3
s@p$kaopacketrifayourwantedrtohexamineotheorecordsethat wererusedfasoevidence3@p!|building or maintaining a history file for a particular device or a3;@pspecific type of error.3C	@p3@p$
This prompt also supports standard Help and Question mark (?) responses.3@pWould you like to review the Help message ?z@p57[,/,3.2.1.C.3G-3C3X 
c)@p#!If you specify multiple packet numbers, each number should be separated32@p#*by a comma. You should realize, however, that if you specify more than3;@p$3one packet number; the records listed in the packets will be grouped and3#D@p$<translated (or saved) according to sequence numbers. In other words, the33K@pErecords will not be grouped according to packet number.3CL@p33U@p#MAfter prompting for packet numbers, Retrieve will skip the "Time from"3K]@p#Vand "Time to" prompts and pickup the basic dialog at the "Output mode"3Sf@p"^prompt. From that point on, there is no difference between the Event3[k@pgFile dialog and the Packet File dialog.3cm@p3;u@pn    Event or packet file (SYSTEM:ERROR.SYS): DSK:A1225.PAK<cr>3Sv@p3S{@pw      Packet numbers: 3,7,14<cr>3k}@p3;@p
~Outputumoden(ASCII):R3S@p3!@p3!X@pReportformat(SHORT):3+@p3s
c#@pBackato therbasic Retrieveidialog.rTheosecondeselectioneprompt:3#;%@p3$;+@p&ginaEvent orppacketlfilel(SYSTEM:ERROR.SYS): 3$S0@p,@Selection2to bep(INCLUDED): ?3%33@p1ts staINCLUDED3&6@p4mark (EXCLUDED3&37@p3&c@@p#8allows yourtoispecifyHwhethersthe selectedentrieswillbeincluded.in,3&{I@p#Aorexcludedfrom,theoutput file. Included is the normal response. If,3(R@p"Jhowever, you specify Excluded, then ALL the entries in the input file3)[@p$S(except those that you select later in the dialog) will be extracted and3*#`@p\translated or saved in the output file.3+3b@p3,j@p"cThe Exclude feature is used to purge entries from a system event file3,#s@p#kbefore the file is translated, saved or analyzed. For example, suppose3-+|@p#ta communications node developed a problem that caused the event file to3.3@p$}fill up with Network entries; since you know what caused the problem you3/C
c7@p#/TheithirdpselectionpromptBallowsyou3specifyoneof the fiveLselection35k:@p8categories.l36{<@p37+@@pp#K       file. You can further qualify the selection at the Time prompts.39+U@p3:;]@p#V       NONERROR - indicates that you want to select only the non-error3:Sf@p!^       type entries. (i.e., statistical information, configuration3;[o@p#g       changes, etc.) Refer to the Spear Reference Card. Again, you can3<cv@pp       further qualify the selection at the Time prompts.3=sx@p3>k@p$y       SEQUENCE - indicates that you want to select entries according to3?	@p       sequence numbers. This response will be explained next.3@
@p3A@p"       CODE - indicates that you want to select entries based on the3A+@p#       event codes assigned each type of entry by the operating system.3B3%@p%       This response will be explained later, after the Sequence response.3CC&@p3DS/@p#'       ERROR - indicates that you want to select error related entries.3Dh@p0       This response will be explained in detail later.z:@p834kO3.2.1.F.3Fk;G-3G#=3G8>
cG@p#?Before we go on to the explanation of the Sequence response, Would you3Gh@p#Hlike to review the Help message associated with the Selection prompt ?zS@pQ3Fk7 3.2.1.G.3I{TG-3J3V3JHW
c`@p"XWhen youtspecifyaSEQUENCE inmresponseuto thes"Selectionmtype"mprompt,3J{h@p!aRetrieveiwillypromptiyoutforfthetsequencetnumberscthatmyou wanthto3Lk@piselect.3Ml@p3M3r@pm by aSelection.type (ALL):eSEQUENCE<cr>3MKs@p3N#y@pt want tSequence numbers: 22,24,35-67,12<cr>3N;{@p3O@p$|YouhcanpselectaasomanypsequencennumberslasayouQwant.oIndividual sequence3O3@p2Would you like to review the Help message ?z:@p93I{3.2.1.H.3Vs<G-3W+=3W@?
cH@p$@If you specify CODE in response to the "Selection type" prompt, Retrieve3WsO@pIwill prompt you for the event codes that you want to select.3YQ@p3Y{V@pR     Selection type (ALL): CODE<cr>3ZW@p3Zc\@pX       Event codes: 133,161-163<cr>3Z{^@p3[Kg@p#_You can select as many event codes as you want. Each event code must be3[co@p"hseparated by a comma. You can also select groups of event codes.  The3\sx@p#pfirst and last event code in the group must be separated by a dash (-).3]{@p#yFor example, 161-163 indicates that you want to select event codes; 1613_@pthru 163.3`@p3`C@p$This prompt also supports standard Help and Question mark (?) responses.3`X@pWould you like to review the Help message ?z@p3Vs,3.2.1.I.3bKG-3c3c
c%@p"Finally, if you specify ERROR in response to the "Selection" prompt,3cK.@p$&Retrieve will enter the "Error class" dialog. Retrieve will loop in this3dS7@p#/dialog until you indicate that you are finished making your selections.3ec@@p#8There are eleven error classes. Excluding ALL, which indicates that you3fsI@p#Awant to select all the error entries, each of the error classes will be3hO@pJexplained in the order that they appear below.3iQ@p3i{U@pR	Selection type (ALL): ERROR3jW@p3j[[@p
X	    Error class (ALL): ?3js]@p\	      ALL3k3`@p^	      FINISHED3k[d@pa	      MAINFRAME3lg@pe	      DISK3lCj@ph	      TAPE3lsm@pk	      UNITRECORD3m#p@pn	      COMM3m[s@pq	      NETWORK3nv@pt	      SOFTWARE3n;y@pw	      CRASH3nk|@pz	      PACKID3o@p}	      REELIDz@p3bK3.2.1.J.3o{G-3p33pH
c@p#Before we continue, however, would you like to review the Help message3px@passociated with the "Error class" prompt ?z@p3o{ (3.2.1.K.3rcG-3s3s0
c'@p$If you specify MAINFRAME in response to the Error class prompt, Retrieve3sc-@p(will prompt for specific Mainframe devices.3ts.@p3uS3@p/	Selection type (ALL): ERROR3uk4@p3v39@p5	   Error class (ALL): MAINFRAME3vK;@p3w?@p<		Mainframe devices (ALL): ?3w3A@p3w{H@pB		  ALL - indicates that you want all central processor,3xQ@p!I                        memory and front-end related error records.3yY@p#R                  CPU - indicates that you want all central processor,3z`@pZ                        related error records.3{h@pa    		  MEM - indicates that you want all memory related error3|k@pi			records.3}r@pl		   FE - indicates that you want all front-end related3}3u@ps			error records.3~#w@p3~[ @p$xThis prompt also supports standard Help and Question mark (?) responses.3~p@p Would you like to review the Help message ?z 	@p 3rc ~,3.2.1.L.4c G-4 
40 
c @p$ If you specify DISK in response to the Error class prompt, Retrieve will4c @p prompt for specific disk drives.4s @p4C "@p      Selection type (ALL): ERROR4[ $@p4+ (@p %       Error class (ALL): DISK4C *@p4 .@p +	 Disk drives (ALL): ?4# 6@p  /	   Logical name or physical device type: (recognized types are)4c =@p 7	   ALL, RM03, RM05, RP04, RP05, RP06, RP07, RP20, RS044c >@p4S F@p  ?You can select ALL disk entries, specific disk subsystems, or any4k O@p" Gcombination of logical and physical device names. You can also enter4k V@p Pyour selections directly at the error class prompt.4	s W@p4
c [@p
 X	 Disk drives (ALL): <cr>4
{ `@p \	 Disk drives (ALL): DP0,DP2<cr>4; g@p a	 Disk drives (ALL): DP220,RM03,RM05,DP010<cr>4
 n@p h       Error class (ALL): DISK:DP220,DP130,RM03<cr>4
so@p4hisdpromptialsoosupportststandardmHelpgandQuestionpmark(?)responses.4M.4k!G-4#!48!
c!@p$!If you specify TAPE in response to the Error class prompt, Retrieve will4k!@p!prompt for specific tape drives.4{!@p4K!@p!     Selection type (ALL): ERROR<cr>4c!@p4;!"@p!       Error class (ALL): TAPE<cr>4S!#@p4#!'@p!$	 Tape drives (ALL): ?4;!/@p !(	   Logical name or physical device type: (recognized types are)4{!6@p!0	   ALL, TU16, TU45, TU70, TU71, TU72, TU73, TU77, TU784{!8@p4k!@@p !9You can select ALL tape entries, specific tape subsystems, or any4!H@p"!Acombination of logical and physical device names. You can also enter4!O@p!Iyour selections directly at the error class prompt.4!Q@p4{!U@p
!R	 Tape drives (ALL): <cr>4!Z@p!V	 Tape drives (ALL): TM1,TM2<cr>4S!`@p![	 Tape drives (ALL): TM304,TM300,TU45<cr>4#!f@p!a       Error class (ALL): TAPE:MT300,TU77<cr>4!g@p4c!p@p$!hThis prompt also supports standard Help and Question mark (?) responses.4x@p!qWould you like to review the Help message ?z!z@p!x4k"b&3.2.1.N.4k!{G-4#!}48!~
c"@p!IfeyouwspecifymUNITRECORDciniresponseetortheeError.classprompt,4k"["@p"     Selection type (ALL): ERROR<cr>4!s"@p4"K"@p"       Error class (ALL): UNITRECORD<cr>4"c"@p4#;"!@p"	 Unit record devices (ALL): ?4#S"#@p4$"+@p"$	   ALL - indicates that you want to select all error records4$3"3@p#",                 that pertain to either line printers or card readers.4%3"<@p""4           LPT - indicates that you want to select all error records4&;"B@p"=                 that pertain to line printers.4'C"K@p""C           CDR - indicates that you want to select all error records4(+"P@p"L		 that pertain to card readers.4)3"Q@p4*"S@p4*"\@p$"TThis prompt also supports standard Help and Question mark (?) responses.4*0@p"]Would you like to review the Help message ?z"e@p"d4k#B&3.2.1.O.4,#"gG-4,["h4,p"j
c"r@p#"kIf you specify COMMUNICATIONS, NETWORK, or SOFTWARE in response to the4-#"{@p$"sError class prompt, all records that pertain to Communications, Network,4.+#@p"|or Software errors will be automatically selected.4/;#@p40##@p
#COMMUNICATIONS - selects:40;#
@pDL4Hardware	ErrorsE(050)40{#cts:41[#@p#   Network Hardware Errors (210) 42#@p#   Network Software Errors (211)42c# @p#   Network Operator Log Entry (220)433#%@p#!   Network Check11 Report (220)44#&@p44S#*@p	#'SOFTWARE - selects:44k#.@p
#+   Software Events (014)45##3@p#/   System Error Log (016) or (116)45c#8@p#4   Software Requested Data (017)463#9@p47@p##:There are no Help messages associated with these error classifications.z#F@p#D4,#$9,3.2.1.P.48+#GG-48c#I48x#J
c#S@p"#KIf you specify CRASH in response to the Error class prompt, Retrieve49+#X@p#Twill prompt for specific Crash Codes4:3#Z@p4;#_@p#[     Selection type (ALL): ERROR<cr>4;##a@p4;{#f@p#b       Error class (ALL): CRASH<cr>4<#g@p4<c#k@p
#h	 Crash codes (ALL):4<{#l@p4=3#u@p##mCrash Codes refer to STOPCODE names (TOPS-10), BUGxxx names (TOPS-20),4=K#}@p"#vand BUGCHECK names (VAX/VMS). Normally, you would get the Crash Code4>S$@p#~name from either the Analyze Report or the Summarize Report.4?[$@p4@S$@p4@k$@p!$	The TOPS-10 STOPCODES are described in the Stopcodes Specification4A$@p$section of The TOPS-10 Software Notebook set (Volume 16).4B$@p4C$"@p"$The TOPS-20 BUGHLTs, BUGCHKs, and BUGINFs are described in the BUGHLT4C$*@p!$#Document section of the TOPS-20 Software Notebook set (Volume 16).4D#$,@p4E+$4@p#$-The VAX/VMS BUGCHECKS are described in the VAV/VMS Software Specialist4E@@p$5Notebook (a one volume set).z$<@p$;48+$Q3.2.1.Q.4G$>G-4GK$?4G`$A
c$J@p$$BThis Crash Code prompt also supports standard Help and Question mark (?)4H@p$Kresponses. Would you like to review the Help message ?z$T@p$S4G%8&3.2.1.R.4J$VG-4JK$W4J`$Y
c$a@p"$ZIf you specify PACKID in response to the Error class prompt, Retrieve4K$h@p$bwill prompt for specific pack or structure names.4L$i@p4M$o@p$j     Selection type (ALL): ERROR<cr>4M$p@p4Ms$v@p$q       Error class (ALL): PACKID<cr>4N$w@p4Nc$}@p$x	 Disk (structure) IDs: PS,JUICE<cr>4N{$~@p4OS%@p#$You can enter as many pack or structures as you want. Each ID should be4Ok%@p
%separatedbypacomma.4P{%#%IMPORTANT NOTE: Normally, when you specify a pack or structure name you4Qk% @p#%delimit it with a colon (i.e., PS:). When specifying pack or structure4R{%(@p%!IDs at the DISK IDs prompt, however, do NOT include the colon.4T%)@p4U%2@p$%*This prompt also supports standard Help and Question mark (?) responses.4U@p%3Would you like to review the Help message ?z%<@p%:4J&&3.2.1.S.4W%=G-4WC%?4WX%@
c%I@p"%AIfyou$specifyiREELIDpinaresponseotostheaError classaprompt,tRetrieve4X%O@p%JwillPpromptfor&specificoreelkIDsooretape labels.4Y%Q@p4Y{%V@p%R&~Selection.typeC(ALL):-ERROR<cr>4Z%X@p4Zk%]@p%Y       Error class (ALL): REELID<cr>4[%@p4[[%d@p%`	 Tape (reel) IDs: ACCT,BAR,6751<cr>4[s%f@p4\K%o@p#%gYou can enter as many reel IDs as you want. Each ID should be separated4\c%r@p%pby a comma.4]s%s@p4^#%u@p4^;%~@p#%vIMPORTANT NOTE: Again, when you specify a reel ID, normally you delimit4^S&@p#%it with a colon (i.e., BAR:). When specifying reel IDs at this prompt,4c&@p&however, do NOT include the colon.4`k&
c&,@p"&%Finished.sAfter)thefirst&passthroughgtheErrorclass dialogrloop,a4dC&4@p&-Retrieve@changesthe&defaultresponsefrom(ALL)htoF(FINISHED).4eK&6@p4fK&:@pe that you have completed the4hC&V@p$&Nselection process, and that you are ready to specify the time parameters.4iS&W@p4jc&`@p#&XYou can, if you like, verify your selections before you go on by typing4j{&i@p$&a/SHOW. Retrieve will list the selections made up to that point, and then4l&r@p"&jrepeat the "Error class (FINISHED)" prompt. If you are satisfied with4m&z@p#&sthe selections you can press the RETURN key and Retrieve will go on to4n @p&{the Time dialog. z'@p'4cC'V3.2.1.U.4oc'G-4p'4p0'
c'@p#'If you are not satisfied, however, you can specify the error class that4pc'@p"'you want to add or change. Then, you can add to the selection list by4qs' @p$'entering the item that you wish to add. For example, suppose you entered4r{')@p#'!a list of five sequence numbers (1,7,12,22,45) and then you decide that4t'2@p"'*you want to add one more sequence number to the list (67); you do not4u':@p#'3have to retype the entire list. You only need to enter the new number.4v#'<@p4w+'E@p#'=If, however, you want to change the list, then you must type /CLEAR and4wC'N@p#'Fenter the new list. The /CLEAR switch clears all selected responses and4xP@p'Orestores the default response (which is, in most cases, ALL).z'Y@p'X4oc(3.2.1.V.4zc'[G-4{'\4{0'^
c'@p4{c'f@p'`Backto4thenbasicdialog.'Thepfourthoselectionuprompt:4{{'h@p4|k'l@puewantthehselectionprocess4}c'@p"'wtoebegin.HThe default response(EARLIEST)zisainclosed.inWparentheses4~k(@p"(andcan(beselected%by pressing the RETURN key. You can also specify4s(@p(real and relative time.5{(
c(*@pe fifth selection prompt:5[(+@p5#(/@p(,     Time to (LATEST):5;(1@p5{(9@p#(2allows you to specify the time at which you want the selection process5(A@p (:to end. The default response (LATEST) is inclosed in parentheses5(J@p!(Band can be selected by pressing the RETURN key. Again, you can also5(O@p(Kspecify real and relative time.5	#(P@p5	s(R@p5
([@p#(SThe prompt also supports standard Help and question mark (?) responses.5
 @p(\Would you like to review the Help message ?z(d@p(c5[)43.2.1.X.5
(fG-5
K(g5
`(i
c(q@p#(jThemsixthRselectionprompttallows(youptospecify(theptype ofCfile that5cates that you want the selected entries extracted5[)
@p)5C)@p")and translated indacreport.5c)want the selected entries extracted5[)@p)               and saved in a binary file.5c)@p5C)&@p$)We will discuss the ASCII response first. But, before we do, this prompt5[)/@p#)'also supports standard Help and question mark (?) responses. Would you5h@p)0like to review the Help message ?z)7@p)65
*#(3.2.1.Y.5C)9G-5{):5)<
c)D@p#)=If you specify ASCII in response to the "Output mode" prompt, Retrieve5C)K@p)Ewill prompt you for the type format that you want.5K)L@p53)P@p
)M*Outputomodeu(ASCII):5K)R@p5)V@p)Snes thReportcformat(SHORT): ?5#)X@p5k)`@p)Y	.SHORT*-indicates5thatyou#wantahbriefmtranslationpofteach5)e@p)aestion mark (?) reselectedentry.5)f@p5S)n@p )g	ieFULLe -eindicatesethatyou'wantadetailedtranslation.of5each5k)s@p)o5%selected entry.5k)u@p5;)}@p)v	  OCTAL - indicates that you want an octal translation of each5S*@p#)~                  selected entry. Normally, octal translations are used5S*
c*4@p#*,If5you+specifyBINARY,inresponse5tothe"Output mode" prompt, Retrieve5%;*=@p#*5will ask you if you want to merge the selected entries with an existing5&K*@@p*>binary file.5'[*B@p5(*G@p*C    Output mode (ASCII): BINARY<cr>5(#*H@p5(s*L@p	*I	Merge with (NONE):5)*M@p5)C*V@p#*NNormally, merging is done only if you are maintaining a device history5)[*^@p!*Wfile. For example, suppose the processor was experiencing a highly5*c*g@p$*intermittent failure. Let's say that on the average, the failure occurred5+k*p@p!*honce a week. Given that situation, you might need several weeks or5,{*x@p"*qeven a months worth of error information to isolate the cause of the5.*{@p*yproblem.5/*|@p5/3+@p#*}Since an event file can get quite large over a period of several weeks5/K+@p$+or a month, you might consider establishing a history file to keep track50S+@p"+of the failure. The merge feature is designed to help you do this. It51c+@p"+allows you to combine the currently selected entries with previously52h@p+ selected entries and merge them in the output file.z+)@p+(2tC
c+6@p!+/The Merge prompt also supports standard Help and question mark (?)55`@p+7responses. Would you like to review the Help message ?z+A@p+?3S,3.2.1.B1.57[+BG-58+D58(+E
c+K@p+FThe eighth and last selection prompt:58[+L@p593+Q@p+M    Output to (DSK:RETRIE.RPT):59K+S@p5:+[@p#+Tallows you to specify the name of the output or file. The default file5:3+d@p"+\name is DSK:RETRIE.RPT (if you are generating a report). The default5;;+l@p!+ebecomes DSK:RETRIE.SYS (if you are building or maintaining a binary5<C+o@p+mhistory file).5=K+q@p5={+y@p#+rYou can override the entire default by specifying a new file name. You5>,@p#+zcan also override any field in the default response by specifying only5?,@p,the field that you want to override.5@#,	@p5@{,@p,
For example, if you were to type:5A,@p5Ac,@p,    Report to (DSK:SUMMAR.SYS): CPU<cr>5A{,@p5BS,@p,the output file specification would become DSK:CPU.SYS5Bk,@p5C[, @p5Cs,)@p#,!The prompt also supports standard Help and question mark (?) responses.5D@p,*Would you like to review the Help message ?z,3@p,133.2.1.C1.5E{,4G-5F3,65FH,7
c,<@p,8Finally, the confirmation prompt:5F{,>@p5GK,C@p,?     Type <cr> to confirm (/GO):5Gc,D@p5H3,M@p!,Eprovides an opportunity for you to review and change any responses5HK,U@p ,Nentered up to that point. If you want to review the response list5IS,]@p ,Vtype /SHOW. If you are satisfied with the response list press the5JS,a@p,^RETURN key or type /GO.5KS,b@p5L,k@p!,cIf you want to change a response, press the BACKSPACE key until you5L(@p#,larrive at the corresponding prompt, make the change, and then type /GO.z,w@p,v3";&3.2.1.D1.5NC,yG-5N{,z5O,|
c-@p#,}ThattconcludesutheiexplanationhofRtheiRetrieveodialog.eNext'on thedmenu5OC--the explanation, and you've had a chance to review the help messages,5QX@p-you should have no difficulty answering the questions.5hk.KG-z-"@p- 6nC7s,RETRIEVE INPUT 5Sk-$G-5T+-%5T@-'
c-,@p-(Retrieve Help Message: Input File Prompt5Ts-.@p5UK-6@p -/    Selection Criteria ___________.             .___ Short Report5Uc->@p -7                         .________!_________.   !___ Full  Report5Vc-F@p -?       Event File ___.   !  Event Retrieval !   !___ Octal Report5Wc-L@p-G                     !___!    Translation   !___!5Xc-S@p-M      Packet File ___!   !   and/or Storage !   !5YK-[@p!-T                         !__________________!   !___ Device History5Z3-d@p!-\   Merge File (binary) ___________!                  Files (binary)5[;-e@p5\C-n@p$-fRetrieve can be used to generate reports, or it can be used to establish5\[-w@p#-oand maintain device history files.  If you choose to generate a report,5]k.@p#-xyou can select one of three formats: Short, Full, or Octal (Hexadecimal5^{.	@p$.on VAX/VMS systems). If you choose to generate a device history file you5`.@p#.
will be asked if you want to merge it with an existing (history) file.5a.@p5b#.@p#.At this prompt Retrieve is waiting for you to specify the name of the 5b;.$@p#.input file. You can specify a packet file or any binary event file you5cC.-@p#.%want, including one generated by Retrieve. If you specify a packet file5dK.6@p#..you will be prompted for packet numbers. Press the RETURN key to select5e[.?@p$.7the default (ERROR.SYS or ERRLOG.SYS). The file specification format is:5fh@p.@dev:<user>file.extension.version.RETRIEVE TYPEET6
z-@p.H7CKETS5SS.L5i0.N
c.T@p.ORetrievemHelpeMessage:sPacketnNumberyPrompt5ic.U@p5jC.^@p!.VAlltheoriesiandhmanyisummariestlistedoinstheaAnalyzeareportshaveta5j[.f@p#.pmatchingrpacket. Thespackethisnnumberedoandncontains aesetnofnpointers5kc.o@p".gthatidentify thetrecordsmthatYwereasummarized$orpusedas5evidenceto5lk.w@p".psupportptheetheory.rThetpacketfile/that.wastgenerated in conjunction5ms/@p#.xwithmtheAnalyze2reportcontainsthe!packetsTandInameuofptheffilelthat5n{/@p/wasranalyzed.5p/@p5p3/p /<arranged in the order that they appear in the event file. That is5w0@p/Dto say, the records will not be grouped by packet number.6
0UG-z/N@p.D6M+5z/S
c/Y@p/TRetrieveGHelpMessage:Selection Mode Prompt5z3/Z@p5{/c@p#/[Selected events can be either included in, or excluded from, the output5{+/l@p#/dfile. The following example illustrates the difference between the two.5|;/n@p5}K/v@p!/o                Include(event type C)         Exclude(event type C)5}c/x@p5~k0@p/yTime:               From        To               From        To50@p0                     :           :                :           :60@p"0	Input  file:   CABBACBCCAABCABBCAACCBCA     CABBACBCCAABCABBCAACCBCA60@p"0Output file:          CC   C   C            CABBACB  AAB ABB AACCBCA60@p60#@p#0At this prompt Retrieve is waiting for you to indicate whether you want6+0,@p!0$the events included in, or excluded from, the output file. You can:6;0-@p6C06@p!0.  1. Type INCLUDED or press the RETURN key to include the selected6[0;@p07     events in the output file.6c0<@p630E@p#0=  2. Type EXCLUDED to exclude the selected event from the output file.6K0F@p6P@p"0GNOTE: You will be prompted for event types and time parameters later.RETRIEVE CODESN6;`z/J@p0SA
X0X
c0^@p0YRetrieve Help Message: Selection Type Prompt60`@p6k0h@p"0aAt this prompt Retrieve is waiting for you to specify the first level6
0m@p0iof1entrysselection.RYouecan:6petALLlif6you~wanttoselectallthe6 2. Type ERROR if you are interested in either a general class, or a6c1@p"1     specific type of error. Retrieve will then prompt you for more 6k1@p!1     information about the type errors that you are interested in.6s1@p6{1!@p"1  3. Type SEQUENCE if you want to select entries by sequence number.61#@p61,@p#1$  4. Type NONERROR if you want to select ALL non-error related entries.631-@p6C15@p1.  5. Type CODE if you want to select entries by event code.6[16@p6S18@p6h@p19NOTE: You will be prompted for time parameters later.z1C@p1A5hk5k(RETRIEVE SEQUENCE6s1EG-6;1F6P1H
c1N@p1IRetrieveeHelpcMessage:sSequence NumberpPrompt61O@p6c1X@p"1PSpearassignsoatsequenceynumber toeeach record in theeeventafile.iThe6{1a@p#1Ynumberrefers@to$the2recordsspositionRinrtheefile.a(ie,gsequence number61i@p#1b1erefers"to'thefirst recordoinethenfile,tsequencednumber 2orefers the61r@p#1jsecond)record,etc.)2.Retrieve2prints theesequencelnumbereinethemheader61{@p$1sof eachrreporttthatsitugenerates.rAsslongaasdthe ordersof6the=recordsin6+2@p!1|theffileuareenotmchangedp(partiallyadeleted&or?mergedwith'anGother6;2TE: The numbers you enter will remain until you type /CLEAR at this 6'p@p2H      prompt.6;k3cG-z2N@p0N6
6t*6)C2PG-6)k2Q6*2S
c2Y@p2TRetrievetHelp)Message:yEvent CodesrPrompt6*32Z@p6+2c@p#2[Generallysspeaking,othe TOPS-10,nTOPS-20tandsVAX/VMSvoperating6systems6++2k@p"2dhandleerrorseintansimilarmmanner.rThatwis,rwhen aneerrortoccursethey6,32t@p"2lsnapshothpertinent hardwaretandesoftwarelstatusm(ataerror).gThen,eif6-;2|@p"2uapplicable,ranrerrortretryralgorithmtistapplied. Next,lregardlesscof6.C3@p"2}whethereorhnotPthe0retrySalgorithmVwasVsuccessful,carsecond snapshot6/K3ed65{3=@p39on the back of the Spear Reference Card.673?@p67[3H@p$3@At this prompt Retrieve is waiting for you to enter the event codes that67s3O@p3Icorrespond to the records that you want to select. You can:693Q@p69{3V@p3R  1. Enter a single event code.6:@p3W  2. Enter a list of codes separated by commas.RETRIEVE STYLET8
(z2J@p	3`6]34j*RETRIEVE TIME FROM6)+3d6<03f
c3k@p3gRetrieve Help Message: Time From Prompt6<c3m@p6=;3s@p3n                Time From:           Time To:6=S3z@p3t         ***********!oooooooooooooooooooo!***********6>34@p3{                02-Mar-81            09-Mar-816?#4@p4                18:30:45             23:30:016@4@p6@k4@p 4	You can use the "Time From:" and "Time To:" prompt to specify the6A4@p#4part of the event file that you want the selected entries extracted or6B4!@p#4excluded from. At this prompt Retrieve is waiting for you to enter the6C4)@p4"time at which you want the selection process to begin. You can:6D4*@p6E43@p#4+  1. Press the RETURN key to default to the EARLIEST time in the file.6E+44@p6F34=@p#45  2. Enter real time. The format is: dd-mmm-yy hh:mm:ss where dd is the6FK4F@p#4>     numerical day, mmm is the first three letters of the month, yy is6G[4O@p$4G     the year, hh is the hour, mm the minute, and ss the second. If only6Hc4X@p$4P     the date is specified, the default time is 1 second after midnight.6Is4Y@p6K4b@p$4Z  3. Enter relative time. The format is: -dd  where -dd is the number of6K@p4c     past days. To indicate today at 00:00:01 hours, type: -0z4o@p4l6;k/L&RETRIEVE TIME TO6M+4pG-6Ms4r6N4s
c4y@p4tRetrieve Help Message: Time To Prompt6N;4z@p6O5@p4{                   Time From:           Time To:6O+5@p5            ***********!oooooooooooooooooooo!***********6P5@p5	                   02-Mar-81            09-Mar-816Q5@p5                   18:30:45             23:30:016Qs5@p6R[5 @p#5At this prompt Retrieve is waiting for you to specify the time at which6Rs5(@p5!you want the extraction (or exclusion) process to end. You can:6T5)@p6U52@p"5*  1. Press the RETURN key to default to the LATEST time in the file.6U53@p6V#5<@p#54  2. Enter real time. The format is: dd-mmm-yy hh:mm:ss where dd is the6V;5E@p#5=     numerical day, mmm is the first three letters of the month, yy is6WK5N@p$5F     the year, hh is the hour, mm the minute, and ss the second. If only6XS5W@p$5O     the date is specified, the default time is 1 second after midnight.6Yc5X@p6Zs5a@p$5Y  3. Enter relative time. The format is: -dd  where -dd is the number of6[@p5b     past days. To indicate today at 00:00:01 hours, type: -07bk>G-z5m@p3\6s3^&6]35oG-6][5p6]p5r
c5x@p5sRetrieve Help Message: Output Mode Prompt6^#5y@p6_6@p#5zRemember, Retrieve is used to translate and/or save selected entries in6_6@p$6the system event file. The result will be either an ASCII report file or6`+6@p"6
a special purpose binary file. At this prompt Retrieve is waiting for6a;6@p$6you to specify the type of output file that you want generated. You can:6bC6@p6cS6'@p"6  1. Type ASCII or press the RETURN key. The result will be a report6ck6/@p"6(     file. The next prompt will ask you to specify the report format.6ds61@p6e{69@p#62  2. Type BINARY. The result will be a binary event file that contains6f6B@p"6:     only the events that you have specified. If you type binary, the6g6J@p"6C     the next prompt will ask you if you want to merge these entries6h#6S@p"6K     with an existing binary file. The merge feature is useful if you6i+6Y@p6T     are maintaining a device history file.6j36Z@p6k6c@p"6[NOTE: If you are using the Exclude capability, you will translate or6k+6k@p"6dsave all of the entries that are in the input file except for those 6l0@p"6lthat you selected for exclusion during the time period you specified.z6x@p6v6)C-(RETRIEVE FORMAT6nC6yG-6o6{6o6|
c7@p6}Retrieve Help Message: Report format Prompt6oK7@p6p+7
@p!7Retrievefis aboutotoetranslatertherentriestthattyouuspecified.KThis6pC7@p"76rk7!@p#7 1. Type SHORT. The result will be a set of brief (3 or 4 line) reports6s7*@p#7"    that list the major symptoms or conditions contained in each entry.6t7+@p6u#74@p"7, 2. Type FULL. The result will be a set of detailed reports that list6u;7;@p75    all of the information contained in each entry.6vC7<@p6w37E@p#7= 3. Type OCTAL. The result will be a set of octal reports that reflect6wK7M@p#7F    the binary contents of each entry. This format is used for program6xS7T@p7N    debugging and event file verification purposes.6y[7V@p6zK7@p$7WNOTE: Typically, the default format, Short, is used to translate packets6zc7h@p$7`and lengthly system event files. Then, the sequence number listed in the6{s7p@p"7iheader of each report, is used to select specific entries for a Full6}@p7qtranslation.z7w@p7u5Sk8m$RETRIEVE MERGE6~;7yG-6~{7z67|
c8@p7}Retrieve Help Message: Merge Prompt6C8@p78@p"8You can merge the entries that you have selected with the entries in7+8@p#8
an existing binary event file. The entries will be arranged in chrono-738@p!8logical order according to the date and time stamps. At this prompt7;8%@p#8Retrieve is waiting for you to enter the name of the file that contains7C8,@p8&the entries that want these entries merged with. You can:7S8.@p7K87@p$8/  1. Press the RETURN key or type NUL: if you do not want to merge these7c8=@p88     entries with an existing (binary) file.7s8>@p7S8G@p"8?  2. Enter the name of the merge file that contains the entries. The7k8O@p"8H     standard file specification is: dev<user>file.extension.version.7s8Q@p7	{8R@p7
8[@p"8SNOTE: The contents of the merge file will not be affected. If you are7
+8d@p#8\updatingahistoryfileandyou do not want to keep a backup copy, then70@p$8eyou should specify the name of the merge file at the "Output to" prompt.z8q@p8o6~;.F(RETRIEVE OUTPUT7
c8{@p8vRetrieve Help Message: Output File Prompt7[8}@p7;9@p#8~At this prompt Retrieve is waiting for you to specify a destination for7S9
@p
9the output file. You can:7c9@p7#9@p#9
  1. Press the RETURN key to select the default file specification. If7;9@p"9     you requested an ASCII report (Brief, Full or Octal format) the7C9%@p$9     default file name will be DSK:RETRIE.TXT. If you requested a Binary7K9-@p 9&     (history file) the default file name will be DSK:RETRIE.SYS.7[9/@p7[98@p$90  2. Enter your own unique file name. (e.g., DSK:SHORT.TAP. The standard7s9@@p"99     file specification format is: dev:<user>file.extension.version.79B@p79K@p#9C  3. Type TTY: in which case the file will be printed on your terminal.7#9S@p"9L     Understand that if you specify TTY: the file will not be saved.739U@p7;9V@p7S9_@p#9WNOTE: If you request and save a report file, then you can use any text7k9g@p#9`editor to review the report. Of course, you can also type or print the7p@p9hfile as you wish.z9o@p9mz3?G,ERROR CATEGORY739pG-7s9r79s
c9x@p9tRetrieve Help Message: Error Prompt7;9z@p7:@p#9{Retrieve is waiting for you to specify the type of errors that you want7#:@p:to select. Press the RETURN key to select all errors, or type:7 3:@p!:
  MAINFRAME ....to select Console Front-end, CPU, or Memory errors.7!3:@p":  DISK......... to select Disk subsystem or individual Drive errors.7";:%@p#:  TAPE..........to select Magtape subsystem or individual Drive errors.7#C:-@p:&  UNITRECORD... to select Card Reader or Line Printer errors.7$S:5@p:.  COMM ........ to select ALL Communications subsystem errors.7%S:;@p:6  NETWORK...... to select ALL Network errors.7&S:A@p:<  SOFTWARE..... to select ALL Software errors.7'3:J@p":B  CRASH.........to select BUGINF, BUGCHK, BUGHLT, or STOPCODE errors.7(:R@p":K  PACKID........to select Disk errors based on Pack or structure IDs.7)#:[@p":S  REEL-ID.......to select Magtape errors based on Reel or label IDs.7*+:\@p7+3:e@p":]This prompt loops, so you can select as many error types as you want.7+K:m@p":fType /CLEAR at the beginning of this prompt clear all previous ERROR7,S:v@p#:nselections. Press the RETURN key at this prompt when you are FINISHED.7-[:~@p#:wType /SHOW to check your selection. You can enter your selections on a7.c;@p#:single line. Use a + sign to separate each error class. Use a colon to7/k;@p";separate error class from device types. Use commas to separate device70p@p;types. Example:  DISK:DP220,DP030+TAPE:MT170,MT166 etcz;@p;8
3>L(ERROR_MAINFRAME72k;G-73+;73@;
c;$@p; Retrieve Help Message: Mainframe Prompt73s;&@p74K;/@p#;'Retrieve defines the mainframe as: the console front-end processor, all74c;8@p#;0central processing units, and the main memory subsystem. At this prompt75s;:@p;9you can:77;<@p77+;D@p ;= 1. Press the RETURN key to select ALL mainframe related errors.77C;E@p78C;N@p!;F 2. Type FE to select errors that pertain to the console processor.78[;O@p79c;X@p";P 3. Type CPU to select errors that pertain to the master and (if any)79{;]@p;Y    all slave central processing units.7;;_@p7;[;h@p$;` 4. Type MEM to select processor detected errors that seem to be related7;s;k@p	;i    to main memory.7=;m@p7=;;u@p";nNOTE: Error classification at this level is very difficult because of7=S;~@p";vthe complex "cause and effect" relationship between the components. 7>[<@p#;Therefore if you're working on an intermittent system problem, you may7?`@p<be better off translating ALL mainframe errors.z<@p<7x{@S(ERROR_DISKS7AS<G-7B<7B(<
c<@p<Retrieve Help Message: Disk Prompt7B[<@p7C+<$@p#<You can select disk entries by logical or physical name. Logical names7CC<-@p#<%are system dependent. Many systems, however, define the disk subsystem7DK<5@p <.as DPnx0, where DPn identifies the channel and controller, and x07ES<<@p<6identifies a specific drive. At this prompt you can:7FS<=@p7GC<D@p<>  1. Press the RETURN key to select ALL disk entries.7G[<M@p"<E  2. Type DPn   to select all entries that pertain to disk channel n.7HK<V@p#<N  3. Type DPnx0 to select all entries that pertain to a specific drive.7IS<]@p<W  4. Type physical names to select entries by option type.7Jc<e@p<^     (RM03, RM05, RP04, RP05, RP06, RP07, RP08, RP20, RS04)7K[<f@p7LS<h@p7Lk<q@p$<iNOTE: Type /CLEAR to clear all disk selections and start over again. You7M<z@p#<rcan enter multiple selections on a single line, and you can mix logical7N=@p<{and physical names. Separate each selection with a comma.7O#=@p7P=@p=Example:  DP040,DP220,DP150 7P0@p=Example:  DP030,RP07,DP020,RP20z=@p=8[>*ERROR_TAPES7QK=G-7R=7R =
c=@p=Retrieve Help Message: Tape Prompt7RS=@p7S#=$@p!=You can select magtape entries by logical or physical name. Logical7S;=,@p"=%names are system dependent. Most systems, however, define the magtape7TC=5@p#=-subsystem as MTxyz, where x is the channel, y is the master controller,7UK==@p=6and z is the drive or slave number. At this prompt you can:7V[=>@p7WS=F@p=?  1. Press the RETURN key to select ALL magtape entries.7Wk=N@p!=G  2. Type MTx to select all entries that pertain to a channel (x).7Xc=W@p"=O  3. Type MTxy to select all entries that pertain to controller (y).7Yk=_@p =X  4. Type MTxyz to select all entries that pertain to drive (z).7Zs=f@p=`  5. Type physical names to select entries by option type.7[s=m@p=g     (TE16, TU45, TU70, TU71, TU72, TU73, TU77, TU78)7\k=o@p7][=p@p7]s=y@p$=qNOTE: Type /CLEAR to clear all tape selections and start over again. You7^>@p#=zcan enter multiple selections on a single line, and you can mix logical7_>
@p>and physical names. Separate each selection with a comma.7`+>@p7a#>@p
>
Example:   MTA3,MTA7,MTC57a8@p>Example:   MT140,TU45,TU78,MT403ERROR_NETTYou can:z5i@p>7QHl0ERROR_UNIT_RECORD6]>7c0>
c>%@p>Retrieve Help Message: Unit Record Equipment Prompt7cc>&@p7dS>/@p#>'Unit record equipment refers to line printers and card readers. At this7dk>2@p>0prompt you can:7e{>4@p7f+>;@p>5   1. Press the RETURN key to select ALL unit record errors.7fC>=@p7g;>C@p>>   2. Type LPT to select ALL line printer errors.7gS>E@p7h8@p>F   3. Type CDR to select ALL card reader errors.Analyze.q1z>O@p>72kA=,7iK>PG-7is>R7j>S
c>Y@p>TRetrievemHelplMessage:7NetworkPrompt7j;>Z@p7k>c@p">[At7thispromptRetrieve is waiting forvyoustoaenterthe?number of the7k+>l@p$>dDECNET Phase III Event Message Class that you want to select.The Classes7l3>m@pD7mC>o@p7m[>s@p>p Class     Description7ms>w@p
@p?    4	  Transport layer7pc?@p
?    5     Data Link layer7q#?@p?    6     Physical Link layer7qc?@p? 007-031  Reserved for Other common event classes7r+?@p? 032-063  Reserved for RSTS specific event classes7s?&@p?  064-095  Reserved for RSX specific event classes7s{?-@p?' 096-127  Reserved for TOPS-20 specific event classes7tc?3@p?. 128-159  Reserved for VMS specific event classes7uS?:@p?4 160-191  Reserved for RT specific event classes7v;??@p?; 192-479  Reserved for Future use7w @p?@ 480-511  Reserved for Customer specific event classes8
3@WG-z?K@p?I73<7y;?N7yP?P
c?U@p?QRetrieve Help Message: Crash Code Prompt7z?W@p7z[?_@p"?XThe TOPS-10, TOPS-20 and VAX/VMS operating systems report software as7zs?h@p#?`well as hardware detected errors. If the system detects an error, or an7{{?q@p"?iunusual software condition, an appropriate message is printed and, in7}?z@p#?rmost cases an entry is recorded in the system event file. Under TOPS-107~@@p ?{these entries are called STOPCODES; under TOPS-20 they are called7#@
@p"@BUGINFS, BUGCHKS, and BUGHLTS; under VAX/VMS they are called BUGCHKS,8#@@p"@and BUGHLTS. At this prompt Retrieve is waiting for you to enter the8+@@p!@name of the BUG type or STOPCODE that you want to select. You can:83@@p8;@$@p@ 1. Press the RETURN key to select ALL entries of this type.8S@&@p8K@-@p@' 2. Enter the name of a specific STOPCODE or BUG type.8c@.@p8S@5@p@/ 3. Enter a list of names separated by commas.8k@6@p8S@8@p8k@@@p"@9NOTE: TOPS-10 STOPCODES are listed in the TOPS-10 Software Notebooks,8@H@p @ATOPS-20 BUG types are listed in the TOPS-20 Operators Guide and,8@p#@IVAX/VMS BUG types are listed in the VAX/VMS Software Support Notebook.ERROR_REEL_IDSK8Pz?F@p@U7AS; ERROR_DISK_PACKS7xc@Y8
x@Z
c@`@p@[Retrieve Help Message: Pack ID Prompt8+@a@p8
@j@p#@bYou can extract or exclude disk entries based on Pack or structure IDs.8
@s@p$@kTherextractiono(oraexclusion)ewill.beodoneainladditionutoaanysotheredisk8;A@p"@}diskachannelhoriacspecificophysicalior)logicalidiskrdrive,.thenthose8KA8cA @p#AAt this prompt Retrieve is waiting for you to enter the structure name8{A)@p#A!or Pack ID that correspond to the disk entries that you wish to select.8A*@p>8A,@p8+A2@pA-   1. Enter a single structure or Pack ID.8CA3@p8 @p#A4   2. Enter a list of structure names or Pack IDs separated by commas.retdiaq18*xzA@@p@P7iK=
8[AAG-8AC8AD
cAJ@pAERetrieve Help Message: Reel ID Prompt8KAK@p8#AT@p#ALYou can extract or exclude tape entries based on label or Reel IDs. The8;A]@p#AUextraction (or exclusion) will be done in addition to any other magtape8KAf@p$A^entries that you have selected. For example, if you have selected a tape8o@p$Agchannel or a specific physical or logical tape drive, then those entries8kAx@p$Apas well as any entries that you select at this prompt will be considered8{B@pAypart of the inclusion (or exclusion) selection criteria.8B@p8 B
@p$BAt this prompt Retrieve is waiting for you to enter the label or Reel ID8 B@p"Bthat correspond to the tape entries that you wish to select. You can:8!+B@p8"3B@pB   1. Enter a single Reel ID.8"KB@p8#@pB   2. Enter a list of Reel IDs separated by commas.zB%@pB#2bsSR.T.3.2.1.D1.8$B'G-8$[B(8$pB*
cB2@p!B+STOP - You are moving in a reverse direction thru the menu. You are8% @pB3about to back into the Retrieve Dialog explanation.zB<@pA;ANj8'B=G-8'CB?8'XB@
cBE@ptrieve Dialog - Q1 of 108(BF@p8(SBN@p BGTrue or False - Retrieve can be used to translate and/or save the8(h@pBOrecords listed in the packets that are generated by Analyze ?retdiaq28=zB\@pBZ8.[CNretdiaq1at8+B]G-8+CB8+XB`
cBc@pBaThat's Correct.8,Be@p8,;Bn@p#BfThis feature allows you to translate and/or save the individual records8,P@pBothat were used as evidence to support specific theories.zBy@pBw9pcBXret_dia_q1_af8.[B{G-8/B|8/0B~
cC@p#BThe statement is TRUE. Retrieve can translate the Packets generated by8/cC@p>K80kC	@p81C@p"C
Remember, there is a packet associated with each theory listed in the81C@p#CAnalyze report. The Packet contains pointers that identify the records82#C!@pCthat were used as evidence to support the theory.83+C"@p84C+@p#C#Thus, anytime you question the validity of a theory and want to examine84+C4@p"C,the evidence yourself, you can do so by specifying the Packet file as85;C<@p"C5input to Retrieve. When Retrieve prompts for the packet number, enter86CCE@p$C=the number that corresponds to the theory that you are investigating and87H@pCFthen, specify the desired output mode (Short, Full, or Octal).   prompt.zCQ@pBV8+D 89kCRG-8:CT8:(CU
cCZ@ptrieve Dialog - Q2 of 108:[C[@p8;#Cd@p"C\True or False - Retrieve can be used to generate and maintain device8;8@pCehistory files ?retdiaq38YzCl@pCj8DE'retdiaq2at8=CnG-8=KCo8=`Cq
cCt@pCrThat's correct.8>Cu@p8>CC}@pCvYou can use Retrieve to build and maintain history files for:8>[C@p8?[D@pD  a) entire subsystems (disks, tapes, networks, etc.),8?sD@p8@cD@pD  b) logical devices (DP220, MT300, CPU0, etc.),8@{D@p8AcD@pD  c) physical option types (RP06s, TU45s etc.) or,8A{D@p8BcD@pD  d) disk and tape storage media (Pack or Reel IDs).8Bx@pzD$@pD"89kCh"ret_dia_q2_af8DD%G-8DCD'8DXD(
cD1@p$D)TheistatementeishTRUE.yRetrievehcansbecusedatonbuildfand maintain,device8ED:@p"D2historyefiles.iTheaprocedure issrelatively simple.eHere'shwhat8toEdo:8FD;@p8G#DD@p$D<First,aselectathegdeviceoviacthes"Erroruclass"prompt.pNext,Especifymthe8G;DM@p$DEtime frame.pThen,twheneRetrievewpromptsofor.OutputEmode,specifyBINARY.8HKDO@p8I[DX@p#DPRetrieve will ask you if you want to merge the selected entries with an8IsD`@p"DYexisting binary history file. If you are building a new history file 8KDi@p$Dapress the RETURN key or type: NONE. If, however,a history already exists8LDr@p#Djfor the selected device and you just want to combine the entries, then8MD{@p#Dsspecify the name of the history file in response to the "Merge" prompt.8N#D|@p8O3E@p"D}Finally, Retrieve will prompt for the output file name. Again, if you8OKE
8T{E+G-8U#E-8U8E.
cE3@ptrieve Dialog - Q3 of 108UkE4@p8V3E=@p!E5True or False - If, in response to the "Type <cr> to confirm (GO):"8VKEE@p"E>prompt, you type "/DISPLAY" - Retrieve will display the current list8WP@pEFof responses ?retdiaq48rzEN@pEL8fsFt,retdiaq3at8Y#EOG-8YcEQ8YxER
cE[@p"ESThe:statementIisTFALSE.`Theswitchis called "/SHOW".NIfaftermaking8Z+Ec@p"E\yourIselections, you type "/SHOW",Retrievewill display:eachEprompt8[3El@p#Edandthe8corresponding response as illustrated in the following example.8\;En@p8]KEs@pEo  Type [cr] to confirm (/GO): /SHOW8]cEt@p8^3Ew@pEu  RETRIEVE mode8^KEz@pEx  -------------8^{F@pE{  Event or packet file: SYSTEM:ERROR.SYS8+F@p
F  Outputcmode: ASCII8cFE@pF@ReportFformat: SHORT8cCF$@pF!8eSelectiontype:TERROR8dF(@p0, 8eSF2@p8f@pF3  Type [cr] to confirm (/GO):zF;@pF98T{EJretdiaq3af8fsF<G-8g3F>8gHF?
cFB@pF@That's correct.8g{FD@p8h+FL@p"FEIt's the "/SHOW" switch that will cause the current list or responses8hCFP@pFMto be displayed.8iKFQ@p8jFZ@p!FRIf, after reviewing the list, you decide that you want to change a8jFb@p#F[response, you can press the BACKSPACE key (or type /REVERSE) until you8k#Fk@p#Fcget back to the response that you want to change. At that point you can8l(@p"Fladd to the response, or you can type /CLEAR and enter a new response.zFv@pEH8Y#GE8nCFxG-8nkFy8oF{
cF@ptrieve Dialog - Q4 of 108o3G@p8o{G	@p!GTrue or False - Retrieve can be used to select entries that pertain8p@pG
to specific Disk Packs or Magtape Reel ID's ?ret_dia_q59@zG@pG8xSGaret_dia_q4_at8rGG-8rSG8rhG
cG@pGThat's correct.8sG@p8sKG'@p$GPack and Reel ID's were added to the selection criteria so that you could8scG0@p#G(use the EXCLUDE mode to remove entries from the event file that pertain8tsG8@p#G1to known bad media. Thus, you can clean up the file a bit, resubmit it8vGA@p$G9to Analyze, and see if media problems were covering up other more subtle8w@p	GBhardware problems.zGI@pGG8nCGret_dia_q4_af8xSGJG-8yGL8y(GM
cGV@p#GNThe statement is TRUE. If you type "?" at the "Error class" prompt you8y[G^@p GWwill see that PACKID and REELID are among the selection criteria8z`@pG_available. zGc@pG8rHu
8|GeG-8|;Gf8|PGh
cGl@ptrieve Dialog - Q5 of 108}Gn@p8}KGv@pGoTrue or False - If you specify a file name  in response to the8}cG~@pGw"Merge with (NONE):" prompt, Retrieve will automatically append8~`@pGthe selected entries to that file ?retdiaq69zH@pH9[I$retdiaq5at9KH
G-9H9 H
cH@p!HThe statement is FALSE. Retrieve will NOT automatically append the9SH@p Hselected entries to the file that you specify in response to the9[H!@p
H"Merge with" prompt.9[H"@p9H+@p"H#Instead what happens is: the selected[entriesandLthe entries inthe9+H3@p#H,"merge file" aretcombinedeandmwrittencout@tothefile that you specify93H9@pH4in response to the "Output to" prompt.9;H:@p9HA@pH;        Selected Entries    Merge with "file name"9+HE@p
;H]@p"HVIf at the "Output to" prompt, however, you specify the same file name9
SHf@p#H^that you specified at the "Merge with" prompt, then the entries will be9[Ho@p#Hgcombined and written in that file. Incidentlly, that is the recommended9
h@pHpmethod for maintaining device history files.zHy@pHw8|Hret_dia_q5_af9[H{G-9H|90H~
cI@pHThat's correct.9cI@p9I@p#IRetrieve will NOT change the "merge" file in any way unless you direct9(@p#I
it to do so by specifying the same file name at the "Output to" prompt.zI@pH9KI9CIG-9kI9I
cI@ptrieve Dialog - Q6 of 1093I!@p9{I)@p!I"True or False - Sequence numbers are used to identify the relative9@pI*position of the records in a system event file ?retdiaq79+`zI5@pI39{J?retdiaq6at9I7G-9[I89pI:
cI=@pI;That is correct.9#I?@p9[IG@p"I@Record sequence numbers are included as part the header in all Short9sIP@p#IHFull, and Octal reports translated by Retrieve. The sequence number is9{IV@pIQthe simplest way to refer to a specific record.9IX@p9kI`@p#IYAs long as the order of the records in the file are not disturbed, the9Ii@p#Iasequence numbers will remain valid. Thus, if you request a Short ASCII9Iq@p!Ijtranslation of several records and then decide that you want a Full9Iz@p#Irtranslation of one or two of those records, you can do so by specifying9@pI{the sequence numbers to Retrieve.zJ@pJ9CI1ret_dia_q6_af9{JG-9 ;J9 PJ
cJ@p"J	The statement is TRUE. Sequence numbers reflect each records relative9!J@p	Jposition in a file.9"J@p9"CJ@p#JRemember, sequence numbers are dynamically assigned to each record as a9"[J'@p!Jfile is read. For example, if a file contains 623 records then, the9#kJ0@p#J(first record in the file will be assigned sequence number 1, the second9$sJ9@p$J1record will be assigned sequence number 2, etc. Finally, the last record9&@pJ:in the file will be assigned sequence number 623.zJB@pI/9K9'{JCG-9(#JE9(8JF
cJK@ptrieve Dialog - Q7 of 109(kJL@p9)3JU@p!JMTrue or False - Retrieve can be used to select entries based on the9)H@pJVevent codes assigned to the entries by the operating system ?retdiaq89>8zJb@pJ`92;KUretdiaq7at9+kJdG-9,+Je9,@Jg
cJj@pJhThat's correct.9,sJk@p9-#Jt@p$JlIf, for example, you wanted to select all KS10 Halt Status Block entries9-;J}@p#Juyou could: reference the Spear Manual or look on the back of the Spear9.KK@p#J~Reference Card to get the code number, specify "CODE" at the "Selection9/SK@p"Ktype" prompt, and, when Retrieve prompted for "Event code:" enter 03390`@pKfor TOPS-10 or 133 for TOPS-20.zK@pK9'{J^ret_dia_q7_af92;KG-92{K93K
cK @pKThe statement is TRUE.93CK!@p94K*@p$K"If you type "?" in response to the "Selection type" prompt, you will see94K3@p#K+"CODE" listed as one of the acceptable responses. If you select "Code"95+K9@pK4Retrieve will prompt you for the "Event codes".963K;@p97KD@p$K<The event types and the corresponding event codes are listed on the back973KM@p$KEpanel of the Spear Reference Card. In addition, the detailed information98@@p!KNcontained in of each entry types is described in the Spear Manual.zKX@pJ\9+kLU9:[KYG-9;K[9;K\
cKa@ptrieve Dialog - Q8 of 109;KKb@p9<Kk@p#KcTrue or False - Typing /C in response to the "Error class (FINISHED):"9<(@pKlprompt will clear all entries selected up to that point ?retdiaq99]zKx@pKv9JSMLretdiaq8at9>CKyG-9?K{9?K|
cK@pK}That's correct.9?KL@p9?{L	@p"LKeep in mind, however, that in addition to clearing selected entries,9@L@p"L
the /Clear switch will also reset the prompt response to the default.9AL@p9B#L@p#LIn other words, suppose you type /SHOW before starting Retrieve. Then,9B;L$@p!Llet's say that you decide that you don't want the selected magtape9CCL-@p#L%entries after all, so you press the BACKSPACE key until you get back to9DKL6@p"L.the "Error class" prompt. At that point you specify "Tape", Retrieve9E[L<@pL7prompts for tape drives and you type /CLEAR. 9FcL=@p9GCLF@p"L>You might think that you are no longer selecting any Magtape entries.9G[LO@p$LGBut that is not the case. Instead, what you did was cleared the selected9H`@pLPlist and thus, reinstated the default (ALL).zLY@pLW9:[Kt(ret_dia_q8_af9JSLZG-9KL\9K(L]
cLe@p L^The statement is TRUE. The /CLEAR switch provides a mechanism for9K[Lj@pLfchanging selected entry types.9L[Lk@p9M#Ls@pLlFor example, suppose you had just selected some event codes for9M;L|@p#Lttranslation and you're about to press the RETURN key to start Retrieve9N;M@p#L}but, before doing so, you typed "/SHOW" just to double check yourself.9OCM@p9PKM@p#MNow, suppose you discover that, for some reason, you entered the wrong9PcM@pMlist of event codes. Here's what to do: 9QkM@p9RCM@p"M1. Press the BACKSPACE key until you get back to the "Selection type"9R[M@pCM9ScM!@p9S{M)@p!M"2. Then, in response to the "Selection type" prompt specify "CODE".9TM+@p9UM4@p$M,3. When Retrieve prompts for the Event codes, type "/CLEAR" to clear the9U3M<@p M5   existing list of event codes and then enter the correct list.9VCM=@p9WCMF@p#M>4. Finally, type "/SHOW" as a last check and then, if everything is OK9WX@pMG   type "/GO" to start Retrieve.period._q1zMN@pKr9>CN39YCMPG-9YkMQ9ZMS
cMW@ptrieve Dialog - Q9 of 109Z3MY@p9Z{Ma@p"MZTrue or False - Entries can be retrieved by logical names (i.e. CPU0)9[@pMbas well as by physical names (i.e. RP06) ?3.2.1.1.q1:S@zMm@pMk9f8Kpretdiaq9at9]MnG-9]SMp9]hMq
cMz@p"MrTechnically, the statement is FALSE. Retrieve can recognize some, but9^N@p#M{not all, logical and physical names. Currently, Retrieve can recognize9_#N@p#Nlogical names associated with Disks or Tapes. In addition Retrieve can9`+N@pN
recognize the following physical and logical names:9a3N@p9b#N@pN     Mainframe devices: CPU, MEM, and FE.9b;N@p9cN#@pN     Disks: RM03, RM05, RP04, RP05, RP06, RP07, RP20, and RS04.9c3N$@p9d3N,@pN%     Tapes: TU16, TU45, TU70, TU71, TU72, TU73, TU77, and TU78.9dKN.@p9eH@pN/     Unit record devices: LPT and CDR.zN7@pN59YCMiret_dia_q9_af9f;N9G-9f{N:9gN<
cN?@pN=That is correct.9gCNA@p9g{NJ@p#NBRetrieve recognizes some, but not all, physical and logical names. Just9hNS@p#NKas a double check before running, Retrieve will list all selected names9i#N[@p"NTthat it considers to be logical. Thus, if you made a typing error or9j3Nd@p#N\entered a physical name that it does NOT recognize, you'll know because9k8@pNeRetrieve will list it as a logical name. zNn@pNl8'OKret_dia_q109m+NpG-9mkNq9nNs
cNw@ptrieve Dialog - Q10 of 109n3Ny@p9n{O@p NzTrue or False - Retrieve can be used to extract entries based on9o@pOSTOPCODES or BUGxxx code names ?zO
@pO9y3BuretOdiaq10at9pcOG-9q#O
cO@pOThat's correct.9qkO@p9rO@p"OThe "Mainframe Error and Crash Summary" section of the Analyze report9r3O$@p$Obreaks down STOPCODES (for TOPS-10) and BUGxxx (for TOPS-20 and VAX/VMS)9s;O*@pO%by: type, name, and number of occurances.9tKO,@p9u+O4@p#O-Thus, given the Analyze report, you can then use Retrieve to translate9uCO=@p#O5or save the STOPCODE or BUGxxx entries for further investigation. This9vKOF@p$O>feature is particularlly helpful when it come to saving and investigating9wP@pOGvery intermittent system crashes.zOO@pOM9m+O"ret_dia_q10_af9y3OPG-9ysOR9zOS
cO\@p"OTThe statement is TRUE. Retrieve can be used to extract entries based9z;Oa@pO]on STOPCODES and BUGxxx code names.9{COb@p9|Ok@p!OcIf you type "?" at the Retrieve "Error class" prompt, you will see9|+Os@p"Ol"Crash" listed among the acceptable responses. If you specify "Crash"9}3O|@p#OtRetrieve will prompt for "Crash codes". At that point you can enter the9~;P@p O}names of one or more STOPCODES or BUGxxx that you want retrieved.9KP@p:KP
@pFor example, if you typed::cP
@p:+P@pPERROR<cr>:CP@pP    Error class (All): CRASH<cr>:P@pP      Crash codes: DX2FUS,P2RAE<cr>:cP@p:3P@p:KP&@p PRetrieve will translate (or save) all entries that are related to:`@pP'either of the Crash codes (DX2FUS and P2RAE).zP.@pMg2j$:CP0G-:kP1:P3
cP;@p"P4That's it. There are only ten questions about the Retrieve dialog. If:3PD@p#P<you have gotten this far, then chances are you have a pretty good idea:;PM@p$PEof how to use Retrieve. Therefore, it is with great honor, that Instruct:@@pPNpronounces you a "Retrieve-Dialog Subject Matter Expert".zPX@pPV2eKQ9 3.3.0.:
KPYG-:P[:P\
cPd@pP]Compute calculates the following system performance factors::KPe@p:
CPn@p$PfSystem Availability (AS) - System Availability is the percentage of time:
[Pw@p#PothatthesystemUwas availablelfor use.)(ItUincludeslStandalone time.)r:entage of time:Q	@pQthat the system was available for use by the user community. :Q
@p:Q@p#QSystem Effectiveness (SE) - System Effectiveness (SE) is the percentage:+Q@p#Qof probability that the system remained available for a given period of:;Q@pQtime (t). :KQ @p:sQ"@p:Q*@p"Q#The remainder of this introduction briefly explains the formulas used:#Q3@p#Q+by Compute to calculate these factors. For a more detailed explanation:(@pQ4of the formulas refer to the Spear Manual.zQ<@pQ;:
KQv3.3.0.A.:Q>G-:KQ?:`QA
cQI@p"QBThe following formula is used to calculate System Availability (SA)::QK@p:QO@pQL  SA = (1.0) - CDT/(TDT + TRT):3QQ@p:{QR@p:QU@pQSwhere::+QV@p:SQ[@pQW  CDT = Chargeable Down Time:kQ_@pQ\  TDT = Total Down Time:3Qc@pQ`  TRT = Total Run Time:sQd@p:3Qf@p:KQo@p$QgRemember - System Availability is the percentage of time that the system:`@pQpwas available for use. (It includes Standalone time.) zQy@pQx:R-3.3.0.B.:cQ{G-:Q|:0Q~
cR@p!QThe following formula is used to calculate User Availability (UA)::cR@p: kR
@pR	= UAa=g(1.0) -oCDT/(CDT+:TRT):!R@p:!KR@p:!cR@pRwhere::!{R@p:"#R@p
R TRT = Total Run Time:#R@p:#CR@p:#[R'@p#R Remember - User Availability is the percentage of time that the system:#p@pR(was available for use by the user community. zR1@pR/:cSM$3.3.0.C.:%[R2G-:&R4:&(R5
cR>@p"R6The following formula is used to calculate System Effectiveness (SE)::&[R?@p:'cRD@pR@  SE = (SA) * (e** (-t/MTBF)):'{RE@p:(CRG@p:([RI@pRHwhere::(sRK@p:)RO@p
RL SA = System Availability:)3RV@pRP e  = the Napierian or natural base of logarithms (2.71828+):)sR_@p$RW t  = an arbitrary period of time for which the SE factor is calculated.:*kRh@p$R`      Typically, Compute calculates the SE factor for four time periods::+{Ro@pRi      6 minutes, 30 minutes, 1 hour, and 4 hours.:-Rx@p$RpMTBF= The mean, or average time between failures (chargeable Downtimes).:-sR~@pRy e**  means "e" raised to the power of (-t/MTBF).:/S@p:/kS@p:0S
@p"SRemember - System Effectiveness (SE) is the percentage of probability:0@p!Sthat the system remained available for a given period of time (t). zS@pS8$ifR.T.3.3.0.:2+SG-:2cS:2xS
cS#@p#SSTOP - You are moving in a reverse direction through the menu. You are:3(@pS$about to back into the Introduction to Compute.zS-@pS+={h_3.3.M.:5S.G-:5SS0:5hS1
cS8@pS2                        Spear Library - Compute:6S9@p:7S<@pS:Topic menu::7S>@p:7KS?@p:7cSB@pS@0. Overview:7{SD@p:8+SG@pSE1. Compute Dialog:8CSI@p:8x@pSJ2. Questions & AnswerszSP@pSO:%[f/(3.3.1.:9SSRG-::SS:: SU
cS^@p$SVComputeEDialogT-:TheCompute@dialogfairlystraightforward. It consists::SSe@pSof:seven@selection promptstandponeSconfirmation)prompt.:;cSf@p:<SSi@pSgCOMPUTE mode:<kSl@pSj------------:=Sq@pSm  Event file (SYSTEM:ERROR.SYS): :=KSs@p:>Sw@pSt  Report period (LAST-WEEK)::>3Sy@p:>{S}@p
Availability Reportftom(DSK:COMPUT.RPT):p:A3T@p:BT@pTReloadreportto(DSK:RELOAD.RPT)::B+T@p:C@p
cT*@pe first selection prompt::DcT,@p:E+T1@pT-  Event file (SYSTEM:ERROR.SYS): :ECT2@p:FT;@p!T3allows you to specify the name of the file that contains the system:F+TC@p"T<performance entries that you want Compute to use in its calculations.:G3TE@p:H;TM@p"TFThe default response (SYS:AVAIL.SYS for TOPS-10, SYSTEM:ERROR.SYS for:HSTV@p#TNTOPS-20, and SYSTEM:ERRLOG.SYS for VAX/VMS) is enclosed in parentheses,:I[T@p"TWand can be selected by pressing the RETURN key. You can override the:JkTh@p#T`entire default response by specifying a new file name, or you can over-:KsTq@p$Tiride any field in the default response by specifying the only field that:MTx@pTryou want to override. For example, if you were to type::NTy@p:OU@pTz        Event file (SYSTEM:ERROR.SYS): .LWK<cr>:OU@p:PU	@pUthe input file specification would become SYSTEM:ERROR.LWK:PU
@p:QU
@p:Q+U@p#U standard Help and question mark (?) responses.:Q@@pUWould you like to review the Help message ?3.3.1.B.in:t0zU @pU=K],compute input:SKU"G-:TU#:T U%
cU*@pU&Compute Help Message: Input File Prompt:TSU,@p:U+U4@pU-                       .--------------.   .___ Summary Report:UCU:@pU5                       |  Calculate   |   |:VCUB@p!U;  System Event File ___|    System    |___|___ Availability Report:W#UH@pUC   (or AVAIL.Ann)      | Availability |   |:X+UP@pUI                       |______________|   |___ Reload Report:YUQ@p:ZUS@p:ZU[@p"UTTOPS-10, TOPS-20, and VAX/VMS record entries that are used by Compute:Z3Ud@p#U\to calculate overall system performance. Under TOPS-10 the entries are:[;Ul@p!Uerecorded in a file called AVAIL.SYS. Under TOPS-20 and VAX/VMS the:\CUt@pUmentries are recorded in ERROR.SYS and ERRLOG.SYS respectively.:]KUv@p:^KU~@p"UwAt this prompt Compute is waiting for you to specify the name of the:^cV@p"Ufile that contains the entries that correspond to the period, during:_kV@pVwhich you want system performance calculated. You can::`sV@p:acV@p#V1. Specify a file name. The format is: dev:<user>file.extension.version:a{V@p:cV#@p#V2. Press the RETURN key, in which case Compute will determine the input:c @p V$   file based on the system type (TOPS-10, TOPS-20, or VAX/VMS).zV-@pU:CcX&:e3V/G-:e[V0:epV2
cV6@pe second selection prompt:f#V8@p:fkV<@pV9    Report period (LAST-WEEK)::gV>@p:gKVF@p V?allows you to specify the time period for which you want system :gcVN@p VGperformance calculated. Compute is designed to calculate system :hcVV@p"VOperformance for the previous week. That is, from a week ago Sunday at:icV@p"VW00:00:01 to last Sunday at 00:00:01. Thus, by running Compute weekly:jkVg@p V`you can monitor overall system performance and note any trends in:ksVk@pVhavailability or effectiveness.:lsVm@p:m;Vu@p"VnYou can also direct Compute to calculate system performance for this:mSV}@p Vvweek or any other period of time. If you specify THIS-WEEK, then:n[W@p"V~Compute calculate system performance from last Sunday at 00:00:01 to:o[W@p#Wthe present. If you specify OTHER Compute will prompt for the specific:pcW@pWtime period.:qkW@p:rW@p#WThe prompt also supports standard Help and question mark (?) responses.:r0@pWWould you like to review the Help message ?3.3.1.C.pe;
0zW'@pW%;Qs^`compute period:t;W)G-:t{W*:uW,
cW2@pW-Compute Help Message: Time Period Prompt :uCW3@p:v#W<@p#W4At this prompt Compute is waiting for you to specify the period of time:v;WD@pW=for which you want system performance calculated. You can::wKWE@p:xCWN@p#WF 1. Type THIS-WEEK if you want the report to cover this week; beginning:x[WW@p"WO    with last Sunday at 00:00:01 and continuing thru to the present.:ykWX@p:zsWa@p"WY 2. Press the RETURN key or type LAST-WEEK if you want the report to:{Wi@p!Wb    cover the 7 days (168 hours) prior to last Sunday at 00:00:01.:|Wk@p:}Ws@p"Wl 3. Type OTHER if you want the report to cover a period of time other:}3W|@p#Wt    than THIS-WEEK or LAST-WEEK. You will be prompted for the date and:~8@p
W}    time parameters next.zX@pW!:e3Z`;XG-;+X;@X
cX
@pXThe third and fourth selection prompts;sX@p;KX@pX  Time from (EARLIEST):;cX@p;#X@p	X  Time to (LATEST):;;X@p;sX!@p$Xare displayed only if you specify OTHER in response to the Report Period;X*@p#X"Prompt. The time prompts allow you to specify the specific time period ;X3@p"X+for which you want system performance calculated. You can specify the;+X;@p"X4default times (Earliest and Latest respectively), or you can specify;3X@@pX<either real or relative time.;;XA@p;XJ@p#XBBoth of these prompts also supports standard Help and question mark (?);@pXKresponses. Would you like to review the Help messages ?compute time to;8zXX@pXU;lYd*compute time from;
;XYG-;X[;X\
cXb@pX]Compute Help Massage: Time From Prompt;KXc@p;
#Xj@pXd                       Time From:            Time To:;
;Xr@pXk                ***********|ooooooooooooooooooooo|***********;Xz                       18:30:45             23:30:01;Y@p;Y
@p"YUsing the "Time From:" and the "Time To:" prompt, you can specify the;#Y@p!Ytime period during which you want system performance calculated. At;+Y@p"Ythis prompt Compute is waiting for you to enter the time at which you;3Y!@pYwant the calculation to begin. You can:;;Y"@p;Y+@p#Y#  1. Press the RETURN key to default to the earliest time in the file.;+Y,@p;3Y5@p#Y-  2. Enter real time. The format is: dd-mmm-yy hh:mm:ss where dd is the;KY>@p#Y6     numerical day, mmm is the first three letters of the month, yy is;[YG@p$Y?     the year, hh is the hour, mm the minute, and ss the second. If only;cYP@p$YH     the date is specified, the default time is 1 second after midnight.;sYQ@p;YZ@p$YR  3. Enter relative time. The format is: -dd  where -dd is the number of;@pY[     past days. Enter -0 to refer to today at 00:00:01 hours.3.3.1.D.ti;8xzYf@pXQ;
;[H&;CYhG-;kYi;Yk
cYp@pYlCompute Help Message: Time To Prompt;3Yr@p;Yy@pYs                       Time From:            Time To:;#Z@pYz                ***********|ooooooooooooooooooooo|***********;Z@pZ                       02-Mar-81            09-Mar-81; Z@pZ	                       18:30:45             23:30:01;!Z@p;!sZ@p#ZAt this prompt Compute is waiting for you to specify the time at which;"Z@pZyou want the calculation to end. You can:;#Z @p;#sZ)@p"Z!  1. Press the RETURN key to default to the latest time in the file.;$Z*@p;%Z3@p#Z+  2. Enter real time. The format is: dd-mmm-yy hh:mm:ss where dd is the;%+Z<@p#Z4     numerical day, mmm is the first three letters of the month, yy is;&;ZE@p$Z=     the year, hh is the hour, mm the minute, and ss the second. If only;'CZN@p$ZF     the date is specified, the default time is 1 second after midnight.;(SZO@p;)cZX@p$ZP  3. Enter relative time. The format is: -dd  where -dd is the number of;)x@pZY     past days. Enter -0 to refer to today at 00:00:01 hours.zZc@pYb;\# ;,ZdG-;,3Zf;,HZg
cZl@pe[fifthrselectionuprompt;,{Zm@p;-CZr@pZnLEReportTtype(SINGLE-REPORT):;-[Zs@p;.#Z|@p"Ztis alsondisplayedtonlytifeyoucspecifyeOTHER[in@responseptoftheaReport;.;[@p#Z}PeriodrPrompt.The[ReportType;promptpallowsyou tonspecifyptheftypeLof;/C[RTS, in which case Compute will;3[[.@p$[&generate (in addition to the single report) a set of weekly reports that;4[[6@p[/reflect system performance for the selected time period.;5k[7@p;6c[@@p#[8The prompt also supports standard Help and question mark (?) responses.;6x@p[AWould you like to review the Help messages ?3.3.1.E.ty;Qhz[L@p[J;@Mcompute type;9[MG-;9C[O;9X[P
c[V@p[QCompute Help Message: Report Type Prompt;:[W@p;:c[`@p#[XCompute can generate a single report, or a set of weekly reports, that;:{[h@p"[areflect system performance. At this prompt Compute is waiting for you;<[o@p[ito specify the type of report that you want. You can:;=[q@p;={[z@p$[r 1. Press the RETURN key or type SINGLE if you want a single report that;>\@p[{    reflects the system performance for the specified period.;?#\@p;@#\
@p#\ 2.eTyperMULTIPLEEifhyoupwantwthe systemtperformancefbrokenedowninto"a;@;\@p#\y period beginning on Sunday at 00:00:01 and ending on;BP@p\    the following Sunday at 00:00:00.z\%@p[F;,]|&;D3\'G-;D[\(;Dp\*
c\.@pe sixth selection prompt;E#\0@p;Ek\6@p\1  Availability Report to (DSK:COMPUT.RPT):;F\7@p;Fc\@@p"\8allows you to specify the destination of the Availability Report. The;F{\I@p#\Adefault destination (DSK:COMPUT.RPT) is enclosed in parentheses and can;H\N@p\Jbe selected by the pressing RETURN key.;I\P@p;Ik\Y@p#\QYou can replace the entire default destination by specifying a new file;J\b@p$\Zname, or you can replace any field in the default by specifying only the;K\j@p!\cfield that you want to override. For example, if you were to type:;L#\l@p;M+\r@p\m  Availability Report to (DSK:COMPUT.RPT): FS:;MC\t@p;N+\{@p\uthe output file specification would become FS:COMPUT.RPT;NC\}@p;O;\~@p;OS]@p#\The prompt also supports standard Help and question mark (?) responses.;Oh@p]Would you like to review the Help message ?3.3.1.F.ou;lz]@p]:SKW#"compute output;Qs]G-;R3];RH]
c]@p]ComputeHelp;Message:AvailabilityReportPrompt;R{]@p;Sc](@p"] Compute generates two reports; a 72 column Summary Report, and a 132;S{]0@p#])column Availability Report. The Summary Report is automatically output;U]9@p#]1to your terminal. At this prompt Compute is waiting for you to specify;V]@@p]:a destination for the Availability Report. You can:;W]A@p;X]J@p!]B 1. Press the RETURN key to select the default file specification:;X]M@p	]K    DSK:COMPUT.RPT.;Y#]O@p;Y[]W@p"]P 2. Enter a unique file specification (e.g., DSK:WK21.RPT). The file;Ys]@p ]X    specification format is: dev:<user>filename.filetype.version.;Z{]a@p;[{]b@p;\]k@p#]cIf you specified multiple reports, then Compute will generate a set of;\+]s@p!]lweekly reports in addition to COMPUT.RPT. The reports will be named;]0@p"]tCmmdd.RPT. Where mmdd corresponds to the month and day of each week.z]~@p]
c^@pe last selection Prompt ;`3^	@p;`{^@p^
  Reload report to (DSK:RELOAD.RPT):;a^@p;ak^@p#^allows you to specify the destination of the Reload Log Report. You can;b^"@p$^select the default response (DSK:RELOAD.RPT) by pressing the RETURN key. ;c^#@p;d#^,@p#^$You can replace the entire default destination by specifying a new file;d;^5@p$^-name, or you can replace any field in the default response by specifying;eK^>@p!^6only the field that you want to replace. For example, if you typed:;f[^?@p;gc^E@p^@  Reload report to (DSK:RELOAD.RPT): .LWK<cr>;g{^G@p;h[^N@p^Hthe output file specification would become DSK:RELOAD.LWK;hs^P@p;ik^Y@p#^QThe prompt also supports standard Help and question mark (?) responses.;j@p^ZWould you like to review the Help message ?3.3.1.G.re<z^d@p^b:t;XS&compute reload;l^fG-;lK^g;l`^i
c^o@p^jCompute Help Message: Reload Report Prompt;m^p@p;ms^y@p"^qIn addition to the Summary and Availability Reports, Compute can also;n_@p#^zgenerate a Reload Report. The Reload Report uses 132 columns and lists;o_
@p#_the system name, the operating system version, the number of times the;p_@p"_system was reloaded, and the operators response to the question: "Why;q#_@p_Reload ?". At this prompt you can:;r+_@p;r{_!@p!_ 1. Press the RETURN key to select the default file specification:;s_%@p	_"    DSK:RELOAD.RPT.;t_&@p;tS_/@p"_' 2. Enter a unique file specification (e.g., DSK:WK21.RPT). The file;tk_7@p _0    specification format is: dev:<user>filename.filetype.version.;us_8@p;vs_:@p;w_B@p#_;If you specified multiple reports, then Compute will generate a set of;w#_K@p$_Cweekly Reload Reports in addition to RELOAD.RPT. The weekly reports will;x+_T@p#_Lbe named RLmmdd.RPT. Where mmdd corresponds to the month and first day;y8@p_Uof each week (i.e., Sunday at 00:00:01).z_\@p^^;_CfC;{_]G-;{C__;{X_`
c_d@p
_aThe confirmation prompt:;|_f@p;|K_k@p_g     Type <cr> to confirm (/GO):;|c_l@p;}3_u@p!_mprovides an opportunity for you to review and change any responses;}K_}@p _ventered up to that point. If you want to review the response list;~S`@p _~type /SHOW. If you are satisfied with the response list press the;S`	@p`RETURN key or type /GO.<S`
@p<`@p!`If you want to change a response, press the BACKSPACE key until you<(@p#`arrive at the corresponding prompt, make the change, and then type /GO.z`@p`	/`m
com_dia_q1<C`!G-<{`"<`$
c`(@p`%ComputetDialogFQ1Gof5<C`)@p<`1@p`*True or False - The formulas used by Compute to calculate: System<`:@p$`2Availability (SA), User Availability (UA), and System Effectiveness (SE)<@p`;are described in the Spear Manual ?comdiaq2<z`E@p`C<
c`L@p`JThat's correct.<	`N@p<	K`Q@p`OThe formulas:<	c`R@p<
`W@p`S  SA = (1.0) - CDT/(TDT + TRT)<
+`X@p<
s`]@p`Y  UA = (1.0) - CDT/(CDT + TRT)<`^@p<S`c@p`_  SE = (SA) * (e** (-t/MTBF))<k`d@p<
0@p#`eare`alsobrieflyexplainedinuthe Introduction section of this module.z`q@p`o<C`Acomdiaq1af<
c`}@p `vThe statement is TRUE. The formulas used by Compute to calculate<[a@p!`~system availability, user availability and system effectiveness are<[a@padescribed in the Spear Manual. <ca
@p<3a@p<Ka@p"aYou should become familiar with those formulas before you attempt to <`@painterpret the reports generated by Compute.za@p`?<a`
<Ka G-<sa"<a#
ca'@pa$Compute Dialog  Q2 of 5<;a)@p<{a1@pa*True or False - The entries used by Compute to calculate system<a9@p a2performance are recorded in the system event file: ERROR.SYS for<@pa:TOPS-10 and TOPS20, and ERRLOG.SYS for VAX/VMS ?com_dia_q3<)HzaE@paC<b'com_dia_q2_at<aFG-<SaH<haI
caQ@p aJThe statement is FALSE. Under TOPS-20 and VAX/VMS the entries are<aZ@p#aRrecorded in the system event files. However, under TOPS-10 the entries<@pa[are recorded in a file called AVAIL.SYS. zad@pab<KaAcom_dia_q2_af<aeG-<Cag<Xah
cak@paiThat's correct.<am@p<;au@p"anTOPS-10 records the entries in a file called AVAIL.SYS. As a general<Sa~@p#avrule, most TOPS-10 sites rename the AVAIL.SYS file to AVAIL.Ann weekly.<[b@p"a(Where nn is a number in the range of 01 to 99.) Typically, the first<kb@pbAVAIL.SYS file becomes AVAIL.A01, the second AVAIL.A02, etc.< sb@p<!kb@p$bThus, if the latest AVAIL.Ann file was AVAIL.A25, and you wanted Compute<"b"@p#bto calculate system performance for the last four weeks, then you would<#@pb#specify AVAIL.A22 as the input file.zb*@pa?<b
<${b+G-<%#b-<%8b.
cb2@pb/Compute Dialog  Q3 of 5<%kb4@p<&+b<@p!b5True or False - Compute generates two types of reports; a 72 column<&CbE@p"b=Summary Report that highlights overall system performance, and a 132<'H@pbFcolumn Full Report that provides more detail ?com_dia_q4<CzbQ@pbO</{czcom_dia_q3_at<)SbRG-<*bT<*(bU
cbX@pbVThat's correct.<*[bZ@p<+bc@p#b[The Summary report is automatically displayed on your terminal. It will<+#bk@p#bdprovide a picture of overall performance. The Full report backs up the<,3bq@pblSummary report with specific details. <-;br@p<.b{@p#bsNote: The Full report requires 132 columns and is generally not suited<.(@pb|for display on most terminals.zc@pc<${bM,com_dia_q3_af</{cG-<0;c<0Pc
cc@p$c	The statement is TRUE. Compute generates two types of reports; a Summary<1c@p"cReport that highlights overall system performance, and a Full Report<2c @pcthat details system availability and effectiveness.<3c"@p<4c+@p$c#The Summary report is automatically output to your terminal when you run<4#c3@p"c,Compute. The following example illustrates a typical Summary report:<53c5@p<6;c6@p<6Sc?@p!c7Compute Summary Report From:     7-Jun-81 01:00 To: 14-Jun-81 01:00<6kcC@pc@	period length (HRS):	 168.000<7scE@p<8;cJ@pcF     SYSTEM Availability % :	 100.000<8ScP@pcK     USER Availability %   :	 100.000<9+cQ@p<:cS@p<:c[@pcTEffectiveness	Six minutes	Thirty minutes	One Hour    Four Hours<:3ca@pc\  factor	  99.584	  97.938	  95.918      94.648<;3cc@p<<ch@pcdReport file name: DSK:COMPUT.RPT<<3ci@p<=cr@p#cjNote: The Effectiveness Factor is the probability that a six minute, a<=@p"csthirty minute, a one hour and a four hour job will run to completion.zc}@pbK<)Sd7
<?+c~G-<?Sd<?hd
cd@pdCompute Dialog  Q4 of 5<@d@p<@[d@p"dTrue or False - Compute uses the operators response to the question:<@sd@pd"Why Reload" to determine User Availability ?<Ax@pdDowntime ?com_dia_q5<Szd@pd<F{d{com_dia_q4_at<CdG-<C[d <Cpd"
cd*@p"d#The statement is FALSE. The operators response to the question: "Why<D#d3@p"d+Reload" is used by Compute to distinguish between Chargeable Downtime<E(@pd4and Non-chargeable Downtime. zd;@pd9<?+dcom_dia_q4_af<F{d=G-<G;d><GPd@
cdC@pdAThat's correct.<HdD@p<H3dM@p#dEThe operators response to the question: "Why Reload" is to distinguish<HKdU@p#dNbetween Chargeable Downtime and Non-chargeable Downtime. The following<ISdZ@pdVoperator responses constitute:<J[d[@p<K#dd@p$d\Chargeable Downtime - STOPCD, BUGHLT, HALT, PARITY, HARDWARE, NXM, HUNG,<K;dj@pdeLOOP, AND CM (Corrective Maintenance).<LKdk@p<M#dt@p#dlNon-chargeable Downtime - PM (Preventive Maintenance), OPERATOR, POWER,<M8@pduSTATIC, NEW, SCHEDULED, STANDALONE, and OTHER.zd}@pd<Ce1<O3dG-<O[e<Ope
ce@peCompute Dialog  Q5 of 5<P#e@p<Pce@p#eTrue or False - In addition to the Summary Report and the Full Report,<Px@peCompute also generates a Reload Report called COMPUT.RLD ?3.3.1.1.q5<n@ze@pe<Vf`com_dia_q5_at<SeG-<SSe <She!
ce*@p#e"The statement is true, only in that Compute generates a Reload Report.<T@pe+The report is actually called RELOAD.RPT not COMPUT.RLD.ze5@pe3<O3e*com_dia_q5_af<Ve7G-<V[e8<Vpe:
ce=@pe;That's correct.<W#e>@p<WSeG@p$e?The name of the report is: RELOAD.RPT. The following example illustrates<WkeM@peHthe type of information it contains.<X{eN@p<YSeP@p<YkeW@peQSYSTEM 2116 THE BIG ORANGE, TOPS-20 MONITOR 4(3530)<Ze_@peX   Built on:     28-May-81 11:41:11     Version:    400,,3530<Zseg@p#e`   Loaded on:    10-Jun-81 20:20:45     Crashed on: 14-Jun-81 07:00:16<[seo@peh   Reloaded on:  14-Jun-81 07:25:08     Why reload: OTHER<\{ev@pep   Run time:     6.004                  Down time:  0.414<]sex@p<^ke@peySYSTEM 2116 THE BIG ORANGE, TOPS-20 MONITOR 4(3530)<_f@pf   Built on:    28-May-81 11:41:11       Version:    400,,3530<_sf@p#f   Loaded on:   14-Jun-81 07:25:10       Crashed on: 15-Jun-81 08:38:20<`sf@pf   Reloaded on: 15-Jun-81 08:38:20	 Why reload: OTHER<bf@pf   Run time:    25.219                   Down time:  0.000<bsf @p<ckf!@p<df*@p$f"The Reload Report and the Full Report, are intended to help you complete<d@pf+system Crash and Uptime reports.zf2@pe:9ST<e{f3G-<f#f5<f8f6
cf?@p#f7That's the last question about the Compute dialog. Press the RETURN key<fh@pf@to return to the menu.zfG@pfE;{hG3.3.2.<h;fHG-<hsfJ<ifK
cfT@p#fLThe Compute Report questions were not ready in time for this Field Test<i;f]@p#fUVersion of Spear. Press the BACKSPACE key or type MENU to return to the<jH@pf^Compute menu.zfd@pfb<Sgcom_rpt_q1<lfeG-<lCfg<lXfh
cfl@p
fiCompute Report - Q1 of 5<mfn@p<mKfq@pfoTrue or False - <m`@pcom_rpt_q2<t zfx@pfv<pgcom_rpt_q1_at<nKfzG-<of{<o f}
cg@pf~That's correct.<oP@pzg@pg<lftcom_rpt_q1_af<pgG-<p[g<ppg

cg@pgThe statement is TRUE.<q @pzg@pfr<nKg0<q{gG-<r#g<r8g
cg@p
gCompute Report - Q2 of 5<rkg@p<s+g@pgTrue or False - <s@@pcom_rpt_q3<zzg&@pg$<vg=com_rpt_q2_at<t+g(G-<tkg)<ug+
cg/@pg,The statement is FALSE.<u0@pzg4@pg2<q{g"com_rpt_q2_af<vg6G-<vKg7<v`g9
cg<@pg:That's correct.<w@pzg@@pg <t+g^<w[gAG-<xgC<xgD
cgH@p
gECompute Report - Q3 of 5<xKgJ@p<ygM@pgKTrue or False - <y @pcom_rpt_q4<`zgT@pgR<{kgkcom_rpt_q3_at<zgVG-<zKgW<z`gY
cg]@pgZThe statement is FALSE.<{@pzgb@pg`<w[gPcom_rpt_q3_af<{kgdG-<|+ge<|@gg
cgj@pghThat's correct.<|p@pzgn@pgN<zh<};goG-<}cgq<}xgr
cgv@p
gsCompute Report - Q4 of 5<~+gx@p<~kg{@pgyTrue or False - <@pcom_rpt_q5=@zh@ph=;hcom_rpt_q4_at<khG-=+h=@h
ch
@phThat'stcorrect.=p@pzh@ph=h
ch@phThe statement is TRUE.=@@pzh@pg|<kh:=hG-=Ch=Xh 
ch$@p
h!Compute Report - Q5 of 5=h&@p=Kh)@ph'True or False - =`@p3.3.2.1.q5=fzh0@ph.=+Ucom_rpt_q5_at=Kh2G-=h3= h5
ch9@ph6The statement is FALSE.=P@pzh>@ph<=h,com_rpt_q5_af=+h@G-=khA=hC
chF@phDThat's correct.=0@pzhJ@ph*<h;S)={hKG-=	#hM=	8hN
chW@p!hOThat's it. There are only five questions about the Compute Report.=	khX@p=
p@phYPress the RETURN key to return to the Compute menu.zhc@pha:5j-&3.4.0.={hdG-=
3hf=
Hhg
chp@p"hhSummarize Overview - Summarize is designed to read and summarize the=
{hu@phqcontents of system event files.=hv@p=Sh@p"hwThe purpose of this Instruct module is to ensure that you understand=ki@p"ithe dialog and the report associated with the Summarize function. The=si@p"imodule consists of two parts. Part one briefly explains the Summarize={i@p"idialog and then asks some questions to ensure that there are no mis-=i@piunderstandings.=i@p=;i&@p#iPart two of this module briefly explains the format and organization of=Si/@p$i'the Summarize Report. (You will be asked to generate or obtain a typical=ci7@p#i0Summarize Report.) The remainder of the module consists of a series of=si@@p"i8questions about the report. Again, the purpose of the questions is to={iI@p#iAensure that there are no misunderstandings about the general format and=iM@piJcontent of the report.=iN@p=SiW@p$iOObjective - Upon completion of this module you should have no difficulty=ki`@p$iXusing the Summarize dialog or understanding the format, organization and=x@piacontent of a typical Summarize report.zii@pih:2(QVR.T.3.4.0.=cikG-=il=0in
civ@p#ioSTOP - You are moving in a reverse direction through the menu. You are=`@piwabout to back into the Summarize Overview.zj@pi~>X4
3.4.M.=KjG-= j= j
cj@pj                        Spear Library - Summarize= Kj
@p=!3j@pj=!{j@p="j@pj0. Overview="+j@p="[j@p	j1. Summarize Dialog="sj@p=#+j!@pj2. Summarize Dialog Questions & Answers=#Cj#@p=$j&@p	j$3. Summarize Report=$3j(@p=$h@pj)4. Summarize Report Questions & Answerszj1@pj/={tY3.4.1.=%[j2G-=&j4=&(j5
cj>@p$j6SummarizeiDialogO-:TheSummarizedialogisstraight1forward.jItconsists=&[jG@p"j?offiveprompts: four selection prompts and one confirmation prompt.='kjH@p=(sjK@pjISUMMARIZE mode=)jN@pjL--------------=);jP@p=)kjU@pjQ  Event file (SYSTEM:ERROR.SYS):=*jV@p=*SjZ@pjW  Time from (EARLIEST):=*kj\@p=++j@p	j]  Time to (LATEST):=+Cja@p=+{je@pjb  Report to (DSK:SUMMAR.RPT):=,jg@p=,X@p
cjx@pe first selection prompt:=.;jy@p=/j~@pjz     Event file (SYSTEM:ERROR.SYS):=/k@p=/kk@p"kallows you to specify the name of the system event file that you want=0k@p!k	summarized. The default response (SYSTEM:ERROR.SYS) is inclosed in=1k@p!kparentheses and can be selected by pressing the RETURN key. You can=2k"@p#koverride the entire default response by specifying a new file name. You=3k+@p"k#can also override any field in the default response by specifying the=4+k0@pk,only field that you want to override.=53k2@p=6k7@pk3For example, if you were to type:=6#k8@p=6sk?@pk9         Event file (SYSTEM:ERROR.SYS): .LWK<cr>=7k@@p=7skH@pkAthe input file specification would become SYSTEM:ERROR.LWK=8kI@p=9kK@p=9kL@p=93kU@p#kMThe prompt also supports standard Help and question mark (?) responses.=9H@pkVWould you like to review the Help message ?zk@pk]=-;l3.4.1.B.=;;k`G-=;skb=<kc
ckh@pkdThersecondRselectionprompt:=<;ki@p==kn@plows you to specify the time at which to begin summarizing the system=={l@p#kyevent file. The default response (EARLIEST) is inclosed in parentheses=?l	@p"land can be selected by pressing the RETURN key. You can also specify=@l
real and relative time.=Al@p=A[l@p=Asl@p#lThe prompt also supports standard Help and question mark (?) responses.=B@plWould you like to review the Help message ?zl#@pl!=;;lc3.4.1.C.=C{l$G-=D3l&=DHl'
cl,@pe third selection prompt:=D{l-@p=ECl1@pl.     Time to (LATEST):=E[l3@p=Fl;@p"l4allows you to specify the time at which to end summarizing the system=F3lD@p"l<event file. The default response (LATEST) is inclosed in parentheses=G;lL@p!lEand can be selected by pressing the RETURN key. Again, you can also=HClQ@plMspecify real and relative time.=IKlS@p=JlT@p=J3l]@p#lUThe prompt also supports standard Help and question mark (?) responses.=JH@pl^Would you like to review the Help message ?zlg@ple=C{mN&3.4.1.D.=L;lhG-=Lslj=Mlk
clq@pllThe fourth and last selection prompt:=M;lr@p=Nlw@pls    Report to (DSK:SUMMAR.RPT):=N+ly@p=N{m@p$lzallows you to specify the name of the output or Report file. The default=Om@p$mresponse (DSK:SUMMAR.RPT) is inclosed in parentheses and can be selected=P#m@p$m
by pressing the RETURN key. You can override the entire default response=Q3m@p"mby specifying a new file name. You can also override any field in the=RCm%@p$mdefault response by specifying the only field that you want to override.=SKm'@p=T[m,@pm(For example, if you were to type:=Tsm-@p=UCm3@pm.    Report to (DSK:SUMMAR.RPT): FS:<cr>=U[m4@p=V3m<@pm5the output file specification would become FS:SUMMAR.RPT=VKm=@p=WCm?@p=W[mH@p#m@The prompt also supports standard Help and question mark (?) responses.=Wp@pmIWould you like to review the Help message ?zmQ@pmP=L;tw3.4.1.E.=YcmSG-=ZmT=Z0mV
cmZ@p
mWThe confirmation prompt:=Zcm[@p=[#m`@pm\     Type <cr> to confirm (/GO):=[;mb@p=\mj@p!mcprovides an opportunity for you to review and change any responses=\#mr@p mkentered up to that point. If you want to review the response list=]+mz@p mstype /SHOW. If you are satisfied with the response list press the=^+m~@pm{RETURN key or type /GO.=_+n@p=_kn@p!nIf you want to change a response, press the BACKSPACE key until you=`@p#n	arrive at the corresponding prompt, make the change, and then type /GO.zn@pn
cndsum_dia_q1=bnG-=bSn=bhn
cn@pmmarize Dialog - Q1 of 7=cn@p=ccn'@p n True or False - If you do NOT want to change any of the Summarize=cx@pn(default responses, you can type /GO at the Event file prompt ?sumdiaq2=v`zn5@pn3=lKosumdiaq1at=fn6G-=fSn8=fhn9
cn=@pn:That is correct.=gn>@p=gSnG@p"n?All Spear Library functions begin by setting the response list to the=gknO@p"nHdefault values. You can change the responses or type /GO at any time.=hsnX@p"nPThe function will use the the responses that you have specified up to=i{n`@p!nYthat point and default the rest. If you make no changes the default=k@pnaresponse list is used.znh@pnf=bn1
sum_dia_q1_af=lKnjG-=mnk=m nm
cnv@p#nnThe statement is TRUE. When you first enter a Spear library dialog, the=mSn@p$nwresponse list is set to the default values. Thus, if you type /GO at the=nco@p$oEvent file prompt Summarize will begin execution using the defaults. The=oso@p#o	result will be report that summarizes the contents of the entire event=q@pzzo@pn/=fob
=r#oG-=rKo=r`o
co@pmmarize Dialog - Q2 of 7=so@p=s[o'@p"o True or False - If you type HELP in response to any Summarize prompt,=sso0@p"o(a ONE page message explaining the prompt and the acceptable response=tx@po1to that prompt will be displayed ?sumdiaq3>zo:@po8=|+p
sum_dia_q2_at=vko<G-=w+o==w@o?
coB@po@That is correct.=wsoD@p=x+oL@p"oEAll Spear Library prompts support the HELP and (?) command.  The Help=xCoU@p$oMmessages are limited to one page, and the prompt is repeated immediately=yKo^@p"oVfollowing the message. Typing (?) will result in a list of acceptable=zX@po_responses without explanation.zof@pod=r#o6sum_dia_q2_af=|+ohG-=|koi=}ok
cos@p#olThe statement is TRUE. You can type HELP<cr> any time you are not sure=}3o|@p"othow you should respond to a particular prompt. You will receive a one=~;p@p#o}page HELP message that explains the prompt and the acceptable responses=@@ppto that prompt.zp
@po4=vkpo>p
G->+pp
cp@pmmarizeaDialog->Q3pof7>sp@p>;p@p#pTrue or False - Summarize will accept and summarize the contents of any>P@p$pbinary event file, including a binary event file generated by Retrieve ?sumdiaq4>Xzp,@pp*>
cp4@pp2That is correct.>p6@p>Kp?@p#p7Summarize will accept (as input) any file that conforms to the standard>cpH@p$p@binary event file format. Currently, that includes event files generated>spN@ppIby: TOPS-10, TOPS-20, VAX/VMS, or Retrieve.>	pO@p>	cpW@p pPThere is one restriction, however, the event file must have been>	{p`@p"pXgenerated by the same type of system that you are using to summarize>
{ph@p#pathe file. In other words, the TOPS-10 version of Spear can NOT be used>
@ppito3processeventfilesgenerated by TOPS-20 etc.zps@ppq>p(sumdiaq3af>
cq@p#pxThe statement is TRUE. Retrieve does not change the file format when it>{q	@p!qgenerates a binary (or History) file. Therefore, since Summarize is>q@p"q
designed to handle standard binary event files, it will accept binary>@pqevent files generated by Retrieve.zq@pp&>qr>kqG->q>(q
cq"@pmmarize Dialog - Q4 of 7>[q#@p>#q,@p"q$True or False - In order to take the default response at a Summarize>8@p"q-prompt you must press the ESCAPE key before pressing the RETURN key ?sumdiaq5>$hzq:@pq8>#r
sum_dia_q4_at>cq;G->#q=>8q>
cqG@p"q?The statement is FALSE. You don't have to press ESCAPE/RETURN to take>kqN@pqHthe default response. You need only press the RETURN key. >sqP@p>kqX@p"qQOriginally, the purpose of the ESCAPE key was to display the default>qa@p"qYresponse. However, as a result of feedback during product Field Test,>qi@p!qbthe prompts were changed. They now display the default responses in>@p"qjparentheses. Thus, the original purpose of the ESCAPE was nullified.zqv@pqt>kq6sum_dia_q4_af>#qwG->cqy>xqz
cq~@pq{That is correct.>+q@p>cr@p#rSince the default response is inclosed in parentheses, there is no need>x@pr	to use the ESCAPE key.zr@pq4>crP>!KrG->!sr>"r
cr@pmmarize Dialog - Q5 of 7>";r@p>#r!@p rTrue or False - Summarize will accept and summarize Packet Files>#@pr"generated by Analyze ?sumdiaq6>2zr+@pr)>*rosumdiaq5at>$sr,G->%3r.>%Hr/
cr8@p"r0The statement is FALSE. A Packet file is not a standard binary event>%{r@@p"r9file. It is a special file produced by Analyze that contains pointers>'rI@p!rAthat identify the records that were used as evidence to support the>(@prJtheories listed in the corresponding Analyze Report file.zrT@prR>!Kr'sum_dia_q5_af>*rVG->*KrW>*`rY
cr\@prZThat is correct.>+r^@p>+Krg@p#r_Summarize only accepts standard binary event files. Since a Packet file>+`@p!rhis not a standard binary event file, Summarize will not accept it.zrr@pr%>$ss<
>-{rsG->.#ru>.8rv
cr{@pmmarizeSDialogR-TQ6oofS7>.kr|@p>/3s@p#r}Truetor Falset->Ifyoupwanttopchange?theunameaof7thereportfilefrom>/Ks\sumdiaq6at>2sG->2[s>2ps
cs@psThat is correct.>3#s@p>3[s'@p"s You can substitute fields at any Spear file specification prompt. For>3ss0@p"s(example, if you wanted the report to go to FS: and you wanted to call>4{s4@ps1it SUMMAR.LWK, you could type:>6s6@p>6H@ps7    Report to(DSK:SUMMAR.RPT): FS:.LWK<cr>zs@@ps>>-{ssum_dia_q6_af>7CsAG->8sC>8sD
csM@p#sEThe statement is TRUE. All Spear Library file-name prompts accept field>8KsV@p#sNsubstitution. You can substitute the output device, the file name, the>9X@psWfile extension, or any combination thereof.zs^@ps>2t>;Cs`G->;ksa><sc
csg@pmmarize Dialog - Q7 of 7><3si@p><{sq@p"sjTrue or False - Both the "Time from" and the "Time to" prompt accept>=@p
srreal and relative time ?3.4.1.1.q7>bhzs{@psy>B 
sum_dia_q7_at>>ss|G->?3s~>?Hs
ct@p>?{t@ptThat is correct.>@t@p>@Kt@p!tAll Spear Library "Time" prompts accept both real and relative time>@`@ptspecifications.zt@pt>;Cswsum_dia_q7_af>BtG->B[t>Bpt
ct#@p$tThe statement is TRUE. All Spear Library "Time" prompts accept both real>C#t+@pt$and relative time specifications. The format for real time is:>D3t,@p>E3t5@p"t-   dd-mmm-yy hh:mm:ss where dd is the numerical day, mmm is the first>EKt=@p"t6   three letters of the month, yy is the last two digits of the year,>FStF@p"t>   and hh:mm:ss represent the hour, minute, and second respectively.>G[tG@p>HctL@ptHThe format for relative time is:>H{tN@p>IKtV@p#tO   -dd where dd represents some number of past days. The time defaults>I`@ptW   to 00:00:01.zt\@psu=%[jk>Kt]G->KCt_>KXt`
cti@p$taThat's it. If you have gotten this far, then chances are you have a good>Ltr@p#tjhandle on the Summarize dialog. Next on the menu is a brief explanation>M@ptsof the Summarize Report format.zt{@pty=Yc~C3.4.2.>N{t|G->O3t~>OHt
cu@p$uSummarize Report - The Summarize Report consists of four major sections:>O{u
@p>Qu@puRep1.tAFileEnvironmentEandiEntry Occurrence Count section.>Q#u@p>Ru@pu   2. A Monitor Detected Error and Reload section.>R3u@p>Su"@pu   3. A Front-end, Channel and Device Summary section.>S3u#@p>T#u)@pu$   4. A Channel and Device Breakdown section.>T;u+@p>Uu,@p>U3u5@p#u-This part of Instruct involves a series of questions. The questions are>UKu>@p$u6designed to ensure that you understand the format and general content of>VX@p
3.4.2.A.>X3uHG->XkuI>YuK
cuT@p$uLBefore proceeding further, you should have a copy of a Summarize Report.>Y3u]@p$uUYou can type /BREAK and generate one using the Spear Library or, you can>ZCub@pu^use the one in the Spear Manual.>[Suc@p>\ @pudWhen you are ready to proceed press the RETURN key.zun@pul@6Cv1
sum_rpt_q1>]+uoG->]cuq>]xur
cuw@pmmarize Report - Q1 of 8>^+ux@p>^sv@p"uyTrue or False - If you are running on a TOPS-20 System, the "Monitor>v
@p#vDetected Errors and Reloads" section of the Summarize Report identifies>`v@p$vthe number of BUGHLT, BUGCHK, and BUGINF that occurred during the summary>a @pvperiod ?sum_rpt_q2>p8zv@pv>fv^sum_rpt_q1_at>bsvG->c3v>cHv
cv#@pv That is correct.>c{v$@p>d3v-@p!v%The BUGHLTs, BUGCHKs, and BUGINFs described in the TOPS-20 Software>dH@pv.Notebooks (Volume 16).zv5@pv3>]+v
sum_rpt_q1_af>fv6G->fSv8>fhv9
cvB@p#v:The statement is TRUE. You would have no way of knowing this, however,>gvK@p#vCif, during the summary period that you selected, there were no BUGHLTs,>h#vS@p#vLBUGCHKs, or BUGINFs recorded. Summarize does not print this section of>i3v\@p#vTthe report unless there were BUGxxx events recorded during the summary>j8@pMJexceed 99.zva@pv>bsw'
>kkvbG->lvd>l(ve
cvj@pmmarize Report - Q2 of 8>l[vk@p>m#vt@p#vlTrue or False - The "File Environment" section of the Summarize Report>m;v}@p$vualways lists the total number and type of entries recorded in the system>n@@pv~event file that was submitted as input ?sumrptq3>}`zw@pw>t{wFsumrptq2at>pCw	G->qw>qw

cw@p$wt is FALSE. The Summarize Report only lists the entries that>qKw@p#wwere recorded during the period of time being summarized. Although that>rX@p#wperiod of time could, it does not always reflect the entire event file.zw+@pw)>kkwsumrptq2af>t{w-G->u;w.>uPw0
cw3@pw1That is correct.>vw5@p>v;w>@p$w6Only the events that occurred on or between the time the user specified,>vP@pw?at the "Time from" and the "Time to" prompts, are summarized.zwH@pw>pCx$
>xcwJG->ywK>y wM
cwQ@pmmarizeReportx-Q3ofu8>ySwS@p>zw[@p"wTTrueorFalse-Underwthe "File Environment" section of the Summarize>z3wd@p$w\Report, the term "inconsistencies" refers to the number of unknown event>{8@p!wetypes that were found in the summarized period of the event file ?sumrptq4?
cw{@p
wxTheestatementSisaFALSE.a>~sw|@p>3x@p$w}The term "inconsistencies" means that Spear encountered a nonrecoverable>Kx@p$xread error while reading the event file. In such cases it loses sync and?[x@p#xmust use the resynchronization word in the next data block to recover.?kx @p$xFor further information about the resync process refer to the DEFINE.LST?p@p
sum_rpt_q3_af?Kx*G-?x+? x-
cx0@px.That is correct.?Sx2@p?x;@p#x3The term "inconsistencies" refers to the number of times Summarize lost?#xC@p"x<sync reading the event file and had to use the resynchronization word?0@pxDin the next data block to recover.zxK@pwl>}ky
?	xLG-?	3xN?	HxO
cxT@pmmarize Report - Q4 of 8?	{xU@p?
Cx^@p#xVTrue or False - The "Entry Occurrence Counts" section of the Summarize?
[xf@p!x_Report lists the event code and the number of times each event type?`@pxgappeared in the summarized period of the system event file ?sum_rpt_q5?hzxs@pxq?[yW
sumrptq4at?v?Pxx
cx{@pxyThat is correct.?x}@p?;y@p$x~The entry types are catalogued by entry code and described in Appendix B?Sy@p#yof the Spear Manual. Sometime, when you get a chance, you should take a?cy@p"ylook at Appendix B. It lists, in detail, the information recorded for?p@pyeach entry type in the system event file.zy!@py?	xosum_rpt_q4_af?[y#G-?y$?0y&
cy.@p"y'ThewstatementoisrTRUE.Ifyyouptakeamlook at the report you'll see a?cy7@p#y/decimal number, followed by name, followed by a number in parentheses.?ky8@p?syA@p$y9The decimal number indicates the number of times a particular entry type?yJ@p#yBappeared in the file; the name refers to the entry type; and the number?yS@p!yKin parentheses refers to the code assigned to the entry type by the?(@p
cyc@pmmarize Report - Q5 of 8?kyd@p?3ym@p!yeTrue or False - Under the "RP04/RP05/RP06 Breakdown" section of the?H@p!ynSummarize Report only the contents of Error Register 1 are listed ?sumrptq6?/Xzy{@pyy?$kzc
sum_rpt_q5_at?sy|G-?3y~?Hy
cz@pszTheystatementristFALSE.$Ifthereareanyzerrorbits(setyinError?{z@pfzRegister2theyzwillbelistedalso.However, if none of the disk? {z@p!zerror summarized had a bit set in Error Register 2 then, of course,?!{z @p!zthe contents of Error Register 2 would not be listed. If that's the?#z%@p
cz2@pz0That is correct.?%sz4@p?&+z=@p#z5Summarize does not try to hide information. However, because the report?&CzE@p!z>was designed so that it could be displayed on a terminal (i.e., 72?'SzN@p$zFcolumns), the contents of Error Register 2 are listed below the contents?([zW@p#zOof Error Register 1. The purpose of the question was to point that out?)kz`@p#zXbecause, at a glance, you might think that Error Register 2 was part of?*p@p
zaa different summary.zzf@pyu?s{?,;zgG-?,czi?,xzj
czo@pmmarize Report - Q6 of 8?-+zp@p?-szy@p#zqTrue or False - For the most part the Summarize Report is easy to read?.@pzzand understand ?sumrptq7?<`z{@p{?3{{Hsumrptq6at?/c{G-?0#{?08{
c{@p"{We're glad that you're satisfied. However, if have any suggestion or?0k{@p#{ideas that will improve the format or content of the report please use?1p@p{the FEEDBACK feature on the Main Course Menu to let us know. z{#@p{!?,;z~sum_rpt_q6_af?3{{%G-?4;{&?4P{(
c{0@p#{)OK. Changing the report format is a relatively easy task. If you would?5{9@p#{1take the time to let us know how the report could be improved we'll do?6{A@p!{:our best to make the changes in the next release. You will find our?7@p{Baddress listed under FEEDBACK on the Main Course Menu.z{K@pz|?/c|?9{LG-?93{N?9H{O
c{T@pmmarize Report - Q7 of 8?9{{U@p?:C{^@p#{VTrue or False - In a Summarize Report, asterisks (***) will be printed?:X@p{if a number exceeds the maximum digits for a field ?sumrptq8?S8z{j@p{h?C|Nsumrptq7at?<k{lG-?=+{m?=@{o
c{p@p?=s{t@p{qThat is correct.?>{u@p?>C{~@p"{vEach asterisk represents one digit of the total spaces set aside for?>[|@p!{a numeric value (that includes the decimal point, if the number is ??c|@p"|decimal). In other words, if three spaces were set aside for a value?@k|@p#|(say 99.), then three asterisks (***) will be printed should the value?Ap@pv]z|@p|?9{fsum_rpt_q7_af?C|G-?CS| ?Ch|!
c|#@p?D|+@p!|$The statement is TRUE. The number of digits that can be printed is?D3|4@p#|,limited to the space available in the report (i.e., 72 columns). Thus,?E;|<@p"|5there is always a possibility that the number of digits necessary to?FC|E@p#|=report a count will exceed the available space. When such a case occurs?GK|K@p|Fa string of asterisks (***) will be printed.?HX@pBreakdown.z|P@p{d?<k~ ?Ic|RG-?J|S?J |U
c|Y@pmmarize Report - Q8 of 8?JS|[@p?K|c@p!|\True or False - The following Summarize report indicates that DP160?K3|j@p|dexperienced 5 errors: 2 Hard Errors and 3 Soft Errors ??L;|l@p?M+|p@p
|mRP04/RP05/RP06 Breakdown:?MC|q@p?N|u@p
|r			     Error Register 1?N|w@p?N[|~@p|x	       D  U  O  D  W  I  A  H  H  E  W  F  P  R  I  I?Ns}@p|	       C  N  P  T  L  A  O  C  C  C  C  E  A  M  L  L?Oc}
@p}	QC}@pKS}I  E/NE19E7?Ek}R@EHF R  RDPR60R HF?PS}@p}             1.?R@p}            S  3.3.4.2.1.q8@=z} @p}?cDW*sumrptq8at?SC}!G-?T}#?T}$
c}-@p!}%The statement isfFALSE.^YoucannotdetermineShow1many^Hard@andSoft?TK}6@p#}.error1a device.experiencedbylookingattheBreakdownpsectionTbecause;?US}?@p#}7(andnthishiskimportanttto remember)dtherBreakdownpsection indicates the?Vc}H@p$}@number of times the error bit was set when Hard errors occurred, and the?Ws}P@p }Inumber of times the error bit was set when Soft errors occurred.?Y}Q@p?Z}Z@p!}RThe following RP04/RP05/RP06 Summary taken from the same Summarize?Z}b@p"}[report that the Breakdown was taken from bears this out. It indicates?[#}j@p}cthat DP160 experienced a total of 4 errors; 1 Hard and 3 Soft.?\+}l@p?]+}p@p}m     RP04/5/6 Summary:?]C}q@p?^}v@p
errors than it actually had. When you want to know the total number of?a~@p"~errors experienced by a Channel or a Device go by the Summary NOT the?b @p|Lz~ @p~?Ic}
sum_rpt_q8_af?cC~!G-?d~#?d~$
c~(@p~%That is correct.?dK~)@p?e~2@p#~*The Breakdown reflects the number of times each bit was set during Hard?e~;@p#~3and Soft errors. If you want to know the total number of Hard and Soft?f(@p~<for a given Channel or Device refer to the Summaries.END_FILEqxz~E@p}>N{uC?h3~GG-?h[~H?hp~J
c~R@p"~KWell, that's it. You have just completed the Summarize Report section?i#~[@p#~Sof Instruct. Assuming that you have also completed the Dialog section,?j+~b@p~\you should feel that you are a qualified Summarize user. ?k3~d@p?l+~m@p#~eIf for some reason you do not agree, or again, if you have any ideas or?lC~v@p$~nsuggestions that will make either Instruct or Summarize a better product?mS~~@p!~wplease let us know. You will find our mailing address listed under?nc@p~FEEDBACK on the Course Menu.?ok@p?p0@pPress the RETURN key to return to the Spear Library Menu.@TG-z@p5yD (SUMMARIZE INPUT?q[G-?r?r0
c@pSummarizeeHelpoMessage:|InputpFilePrompt?rc@p?sC#@pe is SystemgEventyFileo sp.cif.----------.?s[)@p$qinput file. You can spec!fy !nyEventry !?t;1@p*ou want,?~@p"!inc!udFilea bi!ary fSummarydReport?u7@p2le specificRetrieve       !   ! Summary  !?v=@p8         (binary) File !   !!?v{?@p?w[F@p@          INPUT                 PROCESS             OUTPUT?wsH@p?xkP@p"ISummarize reads the specified event file, summarizes its contents and?yY@p!Qproduces a report file. The contents are summarized by: event code,?za@p#ZSTOPCODE or BUGxxx code types, front-end reloads, channel errors, disk?{f@p

@p$format is: dev:<user>file.extension.version. Press the RETURN key if you@@p$want to default to the local system event file (ERROR.SYS or ERRLOG.SYS)sum_dia_qxsum_rpt_qxz
@p
@$!*SUMMARIZE TIME FROM ?qD@
d"@pSummarize Help Message: Time From Prompt@L#@p@$*@p$                        Time From:           Time To:@<2@p+                 ***********!oooooooooooooooooooo!***********@,9@p3                        02-Mar-81            09-Mar-81@,@@p:                        18:30:45             23:30:01@B@p@
J@p#CYou can use the "Time From:" and the "Time To:" prompts to specify the@$S@p#Kperiod during which you want the event file summarized. At this prompt@	,[@p#TSummarize is waiting for you to specify the time at which you want the@
4`@p\file summary to begin. You can:@<b@p@
j@p!c 1. Press the RETURN key to default to the first event in the file.@
$l@p@2. Enterirealdtime.mThesformatiis: dd-mmm-yythh:mm:sshewherehddyisithe@@p#~    the year, hh is the hour, mm the minute, and ss the second. If only@\@p#    the date is specified, the default time is 1 second after midnight.@l@p@|@p# 3. Enter relative time. The format is: -dd  where -dd is the number of@@p    past days. To indicate today at 00:00:01 hours, type: -0z
&@p#@Q&M&SUMMARIZE TIME TO@'G-@d)@x*
d0@p+Summarize Help Message: Time To Prompt@,1@p@8@p2                      Time From:            Time To:@@@p9               ***********!ooooooooooooooooooooo!***********@
G@pA                      02-Mar-81            09-Mar-81@N@pH                      18:30:45             23:30:01@tO@p@dX@p$PAt this prompt Summarize is waiting for you to specify the time at which@|^@pYyou want the file summary to end. You can:@
`@p@lh@p"a  1. Press the RETURN key to default to the LATEST time in the file.@j@p@
s@p#k  2.hEntererealstime.iThe formatfis:tdd-mmm-yy1hh:mm:ssawheremddnishthe@${@p#t\@numerical day,nmmm islthevfirstethree lettersiof the month, yydis@4@p$|@!theyear,hhis theahour,ymm theiminute, andassathe0second.hIfronly@<z
$@p"?q\&SUMMARIZE REPORT@$&G-@$L'@$`)
d.@p*Summarize Help Message: Report To Prompt@%0@p@%l9@p#1The Big Picture is still: Input - Process - Output. Remember, Summarize@&A@p#:is designed to summarize the information contained in the local system@'J@p"Bevent file.  The result is a report file. At this prompt Summarize is@(R@p#Kwaiting for you to specify a destination for the report file. You can:@)$T@p@*,\@p U1. Press the RETURN key to select the default file specification:@*D_@p	]   DSK:SUMMAR.RPT.@+Da@p@+|i@p!b2. Enter your own unique file specification (e.g., DSK:WEEKLY.SUM).@,r@p#j   The file specification format is: dev:<user>file.extension.version.@-s@p@.$|@p#t3. Type TTY: in which case the report will be printed on your terminal.@.<@p#}   The report is 132 columns which may make it difficult to read. Also,@/L@p!   understand that if you specify TTY: the file will not be saved.@0\@p@1d@p"NOTE: If you save the file, you can use any text editor to review the@1x@p"report. Of course, you can also print or type the report as you wish.z
#@p>>tE@4
$G-@44&@4H'
d,@pmmarize Dialog - Qx of x@4|-@p@5D1@p.True or False - @5X@p@:tYG-z
8@p6@8[ujsum_dia_qx_at@6D9G-@7;@7<
d@@p=That is correct.@7LD@pAThe statement is FALSE@8@pz
I@pG@4
4sum_dia_qx_af@8\KG-@9L@90N
dQ@pOThat is correct.@9dU@p
RThe statement is TRUE@:@pz
2@p?SDz@6,[@;\
da@pmmarize Report - Qx of x@;Lb@p@<f@pcTrue or False - @<(@p3.5.1.tqxA
m@pk@?,	.sum_rpt_qx_at@=nG-@=Tp@=hq
du@prThat is correct.@>y@pvThe statement is FALSE@>P@pz
~@p|@:tisum_rpt_qx_af@?,G-@?l@@
d@pThat is correct.@@4
@p
The statement is TRUE@@h@pz
@pg=L2
@ADG-@Al@B
d@p	          Spear Library Applications@B4@p@C
"@p#The Spear Library can be used inconjunction with either the Systematic@C$+@p"#Substitution Troubleshooting Approach, or the Formal Troubleshooting@D(@p,Approach to isolate the cause of intermittent failures.z
5@p4@AD3.5.1.A.@F$7G-@F\8@Fp:
dC@p#;The firstuthingAyouwantDtodoisensureAthat Analyze is!runaonza daily@G$K@p"Dbasis. The best way to do this is to run it via a daily Batch job. If@H4T@p#Lyou not sure how to do that you can ask an experienced operator to give@I<]@p#Uyou a hand, or, if your on a TOPS-20 system, you can try the using this@JLa@p	^Batch Control File@K\b@p@Ld@p@L,l@p"e@SUBMIT SPEAR /TIME:30 /AFTER:TODAY ! Resubmit SPEAR again tomorrow.@LDt@pm@RENAME *.RPT *.RPO		    ! Rename yesterdays report file.@MLx@p
@pEXIT				    ! Then leave.@Ot
@p@IF (ERROR)			    ! Continue even if there's an error.@P<@p"@PRINT A*.RPT /NOTE:"SPEAR - F-S"   ! Print two copies of the report:@Q(@p$@PRINT A*.RPT /NOTE:"SPEAR - OPER"  ! one for FS and one for Operations.z
@p@F$n3.5.1.B.@SD!G-@S|"@T$
d,@p"%Or, if yournonpaaTOPS-10systemyoucanNtryZusing	this ControlyFile.@TD.@p@UL/@p@Ud8@p"0.SUBMITNSPEARS/TIME:30I/AFTER:23:59 !wResubmit Speareagainrtomorrow.@U|<@pRINT A*.RPT /NOTE:"SPEAR - F-S"   ! one for FS and one for the Site. @Zth@pa.RENAME A*.RPD = A*.RPT		    ! Rename today's report so that it@\@pi				    ! won't be printed again tomorrow.z
q@pp@SD 
3.5.1.C.@]dsG-@^t@^0v
d~@p"wOnce you have the Batch File running you can use the daily reports to@^d@p"monitor the over all performance of the system. If the error rate for@_l@p a particular device or subsystem starts to go up, you will see it@`t@p!reflected in the various summaries and histograms. Furthermore, the@ap@p!theory reports should give you some idea of what the cause may be.z
#@p"@]d$3.5.1.D.@d%G-@d<&@dP(
d0@p!)Next, a few hours before you get the system for routine maintenance@e9@p#1submit the last seven days or so of the event file for Analysis. Allow@f
A@p":yourself about an hour to look over the report and decide on a fault@gJ@p"Bisolation strategy. For example; suppose the Analyze report indicates@hN@p
Kthat, among other things:@i$O@p@idX@p!P  DP140 reported 5 recoverable Index Errors while PS1: was mounted.@i|Y@p@k[@p@kd@p#\Since intermittent Index Errors are generally caused by either a faulty@k4m@p#eServo Track or a faulty Index Module; during the maintenance period you@lDu@p"ncould swap the Index module in DP140 with the Index module in another@mTy@p
vdrive (let's say DP220).@n\{@p@o@p#|Then, when you return the system to operations you could ask that they@o4
@p#movehPS1:otoda differentndrive (perhapsADP110).(Thearestlisoamatterof@p<@p#sis) to do the watching.z
@p@dm3.5.1.E.@s,G-@sd!@sx"
d+@p## 1. If the problem moves to DP220, then you know that the Index module@t,0@p,    was the cause of the failure.@u41@p@v:@p#2 2. If the problem moves to DP110, then you know that the medium (PS1:)@v?@p;    was the cause of the failure.@w,A@p@w|I@p#B 3. If the problem does not move, then you know that cause was not the@xR@p$J    Index module nor was it the medium. So, the next chance you get, put@y[@p"S    everything back the way it was and try something else. Sooner or@z,d@p#\    later the Analyze report is bound to reflect the fact that you have@{0@p#e    identified and either moved or eliminated the cause of the problem.z
p@po@s)3.5.1.F.@}TrG-@~
s@~ u
d~@p$vWhen used in this manner Analyze becomes a very powerful troubleshooting@~T@p#tool. The principal is simple. If you move a faulty component from one@d@p#piece of equipment to another the error symptoms will move with it. IfAl@pthey don't, then at least you know what the problem is not.At@pAl @p#This particular isolation technique was developed, during product loadA)@p#!test, by the South massachusetts Field Service Office. If you can comeA
1@p!*up with any neat ways of using the Spear Library to simplify systemA:@p"2maintenance please let us know. We'd be glad to try and include it inAC@p#;this Application Section. You'll find our address listed under FeedbackA$G@p
Don the main course menu.A0@p	H				Thanks  c.t.s.z
N@pL
D	rec_algA	,OG-A	dQA	xR
d[@p$SRecovery Algorithms - Most operating systems have some sort of algorithmA
,d@p#\or procedure for error recovery. This section of Instruct explains theA8@p$ealgorithms used by TOPS-10 and TOPS-20 to recover from disk read errors.rec_menualA"z
r@pp
c0QR.T.recalgAA@w
d	@p$xSTOP - You are moving in a reverse direction through the course. You areAp@p	about to back into the Introduction to the Recovery Algorithms.z
	
@plA	+B9A	
G-A,		
d	@p	                Disk Read Error Recovery AlgorithmsAt	@pAd	@p	Topic MenuA|	@pA$	@p	0. IntroductionA<	 @pAl	%@p	!1. TOPS-10 Disk Recovery AlgorithmA	&@pAT	+@p	'2. TOPS-20 Disk Recovery AlgorithmAh@pA"
G-z
	2@p	0@=
"t10_dsk_rec_algAl	4G-A,	5A@	7
d	>@p	8     TOPS-10 RP04/05/06 Disk Read Error Recovery AlgorithmAt	@@pAl	H@p"	ATOPS-10 and TOPS-20 use a similar algorithm to recover from disk readA	Q@p"	Idata errors. The algorithm involves 31 retry attempts. Under TOPS-10,A
	Y@p"	Rif an ECC correctable error is detected during a read header or dataA	^@p	Zoperation the following occurs:A	`@pAl	e@p	a 1. The transfer is terminated.A	f@pAT	o@p#	g 2. The software reconstructs the data using the calculated ECC value.Al	p@pAt	y@p"	q 3. The transfer is restarted beginning at the next sector (i.e., theA
	@p	z    sector following the sector in error).A
@pAt
@pA 

@p"
If the read data error is not ECC correctable, however, the followingA  @p
recovery algorithm is evoked.t20_dsk_rec_algASxz
	-@p
Al&t10_dsk_rec_alg_aAT
A"X

d
@p
 1. Non (ECC) recoverable read error A#
$@p
 2. Repeat read operation (attempt ECC correction)A#d
+@p
% 3. Repeat read operation (attempt ECC correction)A$L
1@p
, 4. Repeat read operation (attempt ECC correction)A%4
8@p
2 5. Repeat read operation (attempt ECC correction)A&
>@p
9 6. Repeat read operation (attempt ECC correction)A'
E@p
? 7. Repeat read operation (attempt ECC correction)A'l
K@p
F 8. Repeat read operation (attempt ECC correction)A(T
R@p
L 9. Repeat read operation (attempt ECC correction)A)<
X@p
S10. Repeat read operation (attempt ECC correction)A*$
_@p
Y11. Repeat read operation (attempt ECC correction)A+
e@p
`12. Repeat read operation (attempt ECC correction)A+t
l@p
f13. Repeat read operation (attempt ECC correction)A,\
r@p
m14. Repeat read operation (attempt ECC correction)A-D
y@p
s15. Repeat read operation (attempt ECC correction)A.,
@p
z16. Repeat read operation (attempt ECC correction)A/@p17. Repeat read operation (attempt ECC correction)A/|@pA0`@p
Next Offset is tried.z
@p10dskrecalgbA1<G-A2A2
d@pOffset heads (+400 microinches if RP04/05, +200 if RP06).A2L#@p18. Repeat read operation (attempt ECC correction).A3D*@p$19. Repeat read operation (attempt ECC correction).A44+@pA5$3@p,Offset heads (-400 microinches if RP04/05, -200 if RP06).A5<:@p420. Repeat read operation (attempt ECC correction).A64A@p;21. Repeat read operation (attempt ECC correction).A7$B@pA8J@pCOffset heads (+800 microinches if RP04/05, +400 if RP06).A8,Q@pK22. Repeat read operation (attempt ECC correction).A9$X@pR23. Repeat read operation (attempt ECC correction).A:Y@pA;a@pZOffset heads (-800 microinches if RP04/05, -400 if RP06).A;h@pb24. Repeat read operation (attempt ECC correction).A<@pi25. Repeat read operation (attempt ECC correction).z
s@pqA1<
Z$t10_dsk_rec_alg_cA=tuG-A><vA>Px
d@pyOffset heads (+1200 microinches if RP04/05, +600 if RP06).A?
@p
26. Repeat read operation (attempt ECC correction).A?|
@p
27. Repeat read operation (attempt ECC correction).A@l
@pAA\
@p
Offset heads (-1200 microinches if RP04/05, -600 if RP06).AAt
@p
28. Repeat read operation (attempt ECC correction).ABl
$@p
29. Repeat read operation (attempt ECC correction).AC\
&@pADL
*@p
'Return to center line.ADd
0@p
+Set Error Correction Inhibit (ECC INHIBIT = 1)AE$
5@p
130. Repeat read operation.AF
6@pAFT
=@p
7Reset Error Correction Inhibit (ECC INIBIT = 0)AFl
D@p
>31. Repeat read operation (attempt ECC correction).AGT
E@pAHD
G@pAH\
O@p"
HIf all 31 retries are unsuccessful, then the read error is defined asAHp@p$
Pnon-recoverable (Hard) and an entry is made in the structures BAT block.AT
%G-z
\@p
A=tAK$
^G-AKL
_AK`
a
d
h@p
b        TOPS-20 RP04/5/6 Disk Read Error Retry AlgorithmAL
j@pAM
k@pAM$
t@p"
lTOPS-10 and TOPS-20 use a similar algorithm to recover from disk readAM<
{@p
udata errors. The algorithm involves 31 retry attempts.AND
|@pAO4
}Ifanyofrthevretryeattemptsearessuccessful,ethenetheoerrormisndefinedAOL@p!dz
X@pdskrecalgaAK
&ATP
d@pfowinghdetailsmeachaofathea31ostepsiinothecdiskiread errorAU
I@pAX|ad operation. Do not attempt ECC correction.AY@p
d@p
Gt20dskrecalgbA[|
d@p$t 13 retries will attempt ECC correction if ECC Hard = zero (0).A]
s@pA^adpoperation.pAttempt.ECCtcorrection.A^4@p@6.Repeat8readpoperation.pAttempt.ECCtcorrection.A`tion.AaT@p 9. Repeat read operation. Attempt ECC correction.Ab< @p10. Repeat read operation. Attempt ECC correction.Ac$'@p!11. Repeat read operation. Attempt ECC correction.Ad
-@p(12. Repeat read operation. Attempt ECC correction.Adt4@p.13. Repeat read operation. Attempt ECC correction.Ae\:@p514. Repeat read operation. Attempt ECC correction.AfDA@p;15. Repeat read operation. Attempt ECC correction.Ag(@pB16. Repeat read operation. Attempt ECC correction.z
L@pIA[|\,t20_dsk_rec_alg_cAh|MG-AiDOAiXP
dW@pQThe next 12 retries attempt offset and ECC correction.Aj
_@pXThe first offset value listed is used for RP04s and RP05s.Aj|e@p`The second offset value listed is used for RP06s.Aktg@pAl\h@pAltq@p#i17. Offset (+400/+200). Repeat read operation.  Attempt ECC correction.Am
z@p#r18. Repeat read operation at this offset.       Attempt ECC correction.An|@pAo,@p#}19. Offset (-400/-200). Repeat read operation.  Attempt ECC correction.AoD@p#20. Repeat read operation at this offset.       Attempt ECC correction.ApT@pAqd@p#21. Offset (+800/+400). Repeat read operation.  Attempt ECC correction.Aq|!@p#22. Repeat read operation at this offset.       Attempt ECC correction.As
#@pAt,@p#$23. Offset (-800/-400). Repeat read operation.  Attempt ECC correction.At45@p#-24. Repeat read operation at this offset.       Attempt ECC correction.AuD6@pAvT?@p#725. Offset (+1200/+600). Repeat read operation. Attempt ECC correction.AvlH@p#@26. Repeat read operation at this offset.       Attempt ECC correction.Aw|J@pAy
S@p#K27. Offset (-1200/-600). Repeat read operation. Attempt ECC correction.Ay @p#T28. Repeat read operation at this offset.       Attempt ECC correction.z
`@p^AhxIt20_dsk_rec_alg_dA{DbG-A|
cA| e
dm@pfThefinalthreelretriesarealastditcheffort to get the data.A|Tn@pA}Tw@p$o29. Return to centerline. Repeat read operation. Attempt ECC correction.A}l@px30. Set Error Correction Inhibit. Repeat read operation.A~|@p31. Set Error Correction Inhibit. Repeat read operation.At@pBl@p"	If all 31 retries are unsuccessful, then the read error is defined asB@p$non-recoverable (Hard) and an entry is made in the structures BAT block.yTGPB@p
`@p
$Now type: SAVE SPRINS<cr>YB@)9+B?x2@gCY,~ @0 '* 4,^x,x (*  0,~, ~ ~ P(@1F+ 
[4B, ",,Z, "1F,@B P1,~5" 
",&#`QDx6@,[x."0b."B:,~, ~ P( ) &.(H=f @H,~, Z H@  BA@@@1PO@@ ) ^?,axA,h( N1,~A? @ 0
",~, ~+7,,q# ,S *,Q+Q,,q#[.S .E,A "D B1,~,q#,~, ~ ,SP( 8 *,O 8dx$0dx. @9 ( (P=hIJ 7,Q *J * *,O+Q,O,QJ,~,Q.0P,~,>,U,^,~,d[/(&(Z ,6@&*6$(.* "@5L\ & (=
b:`HhA( ( 0F+a (aJ:/
5l\.
,jZ
+iZ
$*Q@[`&*&,*
,>,j,^,j 
,j)B}&,ln+,~,&$H0 H B1,~,@@1 (XB* +	b+u B\ BY ,	b,/ B] $X"2Q"	b@4B| B]1$9x 0 0 &4H.(H=f} 0P7@]+
 0P ) &4H
.(H=f	9
 0.P@P,~ &@,,~,!"X"Y	b,4,~,  @@Y 51P+/0P+Z"Y	b,9,~ ,~ ,~ ,~ ,~@,~B,~b,~
&:
&
&>@@1,~1HH0A0H<x.x/Can't get PPN of program ",+%HIH\Unable to return to SPEAR.EXE "1+%HYCan't find the selected program "5+%?SPEAR  Monitor call failed
-       
FOREST p>INIT_TABLES p@BUILD_TABLE pBADD_LINK pEINSERT_LINK pGREMOVE_TABLE pIRETRIEVE_TABLE pLMATCH_KEYS pNCOUNT_OF_SONS pQRESTART_RETRIEVE pSREAD_LIST pVINIT_AND_GET_TABLE p	XSEARCH_BROTHER p[LOWEST_SON p^ADD_LONG p`ADD_SHORT pbSAVE_STRING pdVALUES_NOT_MATCH pgSWEEP_CHAIN pjUNLINK_LONG plUNLINK_SHORT poREMOVE_BLOCK pqFIND_UNKEYED ptBDFIKNPSVX[]`bdfilnqsv " Ba d1bf+	 "2Ba+	,>d,>
,/+@@dpa,~Failed to pass enough keys for this table pCount item was not skipped p
,>,>,>,>,>   @a,>|,>|,\/ BaaB+ ,z Ba e6b d b2 +^  2@a+^ eZ5@(,>,y /c eZ @e:b c b.4b0T+0,>c,>x,>d,>d+\0T+4 e c.  .F+!0T+F e .& c.0V+@ @(}aP+>  ,>,>,+Y   @+!Z,>  ,>,3/`B:H Re:b+!0T+J1V+!,>c,>x,>d,>e+\0T
+O e c.  G@+!0T+S e c.  A@+!0T1T+V0T	+Z,>e c.  ,>,f/+!,>c,>x,>d,>e,y/f "+_ a,^,^,^,^,^,~<@?  @@@f."1b+g 5Bl $f De+l BeO c b . (~`D+s (~aB+xaD+v e0Bf (+ eZ4B Be+v e.",>,>,3 /5( eZ4D eZ De+x`H+ e0Bf,~0H+ eXBf[ De,>,>,/,~,>e,y Be e.$ c b. (}aB+,>,>,/+  B e[0Bf+ ~ D/c,~Linkage error found by SWEEP_CHAIN routine p@@a,>,>,\/ BaaB+.,z BaaB+.,>/,v "cBa+% e0"f+),>c,>y,>d,>0,y/0 ",~ e1bf+-$/5D- Bx, Be+)/c a,~$(TABLE_BUILD improperly indicated bottom of tree p0,>,>@@a,>~,>~,\/ BaaB+A e !  b@+?,z Ba e!  b@@@a aaB+u e e$w4D`Z De:b e!$ bD3B+OZ1df+LZ De+F[ De>b e!$ GD+F e!$ cD+R@+u c b. $bD+Y,>c,>z,>d,>w,y/f "+u d b. e.$ c. (}aB  D+C e d b2 +sZ :b.b c 
b . (aF+o   @e e.& (}aD  F eZ @  eQ@@+` .& (}aD  F+` e!  G@ a,^,^,~26@@a,>,>,\/aB+~,zaB+~ e"b,~@,~@@a,>,>,\/aB+,zaB+ e"/,~@,~Linkage error found by SWEEP_CHAIN routine pLinkage error found by RESTART_RETRIEVE p
@@a,>,>,\/ BaaB+),z BaaB+),>
,v "cBa+ e0"f+,>c,>{,>d,>*+% e!$cD1Bf+)[ De e0bf+',>c,>{,>d,>+,y/0 ",~ e!$ BD+/c a,~Caller did not retrieve table before reading list p+Item to be read is not designated as LIST item p1@@a,>,>
,\/ BaaB+Z e[ De6@e+@,>c,>|,>d,>[+L,X / Db9D eZ Fe=$C /d Bb c b. (`B+N,>c,>|,>d,>[,y/f ",~ e  De e1bf+Y d b. e.$ c. (}aB  D e eZ F+Z@@a a,~06@@b " Ba  Bb  Bc  Dc c  Dd@@@f."1b+b!"GBh d0bf+j "cBa+i,>n+k@@a+m,>d,>~, Be/ a,~fOut of items before end of key search pnFound item other than key before end of key search ps,>7@b+ "2Ba+>b eZ5B $cDa+@@@f."1b+ eQBf "f+,>c,>},>d,>+ Be:b "cBa+
 c. +c. $cD+,>e,>, Be/+z,>c,>},>d,>,y/f "+ a,^,~ry,>,> ~ . ,>,>~,3/5"!Z@1`f+!Z@+`B+#0Pf+9  c@a+93BG1Pf+,@@@f."1b+&[@Q@f E`EQPg,>n+,,>,M  ." c b. (}aD+54F5,>~,>,/+6 ~ @@6`b "bF/c+9@@a  c@a+C  c@a+C F0@+?! G@@! b@@+B F. `F!  B@@ ,^,^,~4@4h2@<@XPORT returned bad address for free-core pG,>,>.R`  `p  `p@@x,>q  ,>,>
,>
,>
,>r,PJ`B }0pf+[,>c,>~,>d,>r,y/s "+n zXB@[Q@@[Q@@ q`EQP[@4BbXP+e! c@@+d Pd+e[@XP[@! b@@+m /0@+j! G@! b@+m /. `//s /,^,^,~$$6$4R$LP0XPORT returned bad free-core address. ps,>,>.R`  `p  `p@@x,>  ,>,>
,>
,>
,>,PJ`BX}0pf+,>c,>~,>d,>,y/s "+
 QP/s /,^,^,~R$x,>,> ~  `0 ~@@ ~ ~"11B+  `1 ~Z,>,>~,>/+b1 ~Z,>,>~,>
,>
,>
,>2,PJ { 4H. { .$ 10@++  
ZO+) . . 
 L.&3&+&+.Z,>,>,>,rf/2/s,^,^,~6$$$$$R$,>,>,>,> } @ } c b. (}aB+_4D_@
Z@5@= *+> }Z5@D }@Z5@A $A1D+g0J+l+c p0@+Y@Z@Z3  "1B+c }@Z@Z2` $1D+l @ } 
@Z@O+W . . 3P+W  
h0h,30+c+l.&3&+P+mZ@,>,>@Z,>,>,>
,r}0/0+m@+ hh$35"0B+dO+m@3H},"0B+h@+m@,}h>h$2`!"0B+m (+,^,^,^,^,~$$@Called>SWEEPCHAINwithinvalid long blockpp./e0"f+{,>c,>,>d,>,y/f+ e!$@cD+ZBZ DeZeZ1Df+Z+~/e[,Dx,>~,v/c,x,Be6@e+/ Be4e$q0D+("f++e@[5F,>,E /+< ~@@,>~,>,E B}. /+7,^,^,~,>. } .$Z7@+M,>,>W,>
,>
,>W,Q
/0 ~XB "bp "bp } Bx ",>,>W,>
,>
,>W,Q
/0 /,^,~R$,>,>   d 
@+GIc.,cL+.7.&3f+[.,^,^,~SPRMSG.TXT@@MSGWRTpeCRE>TEXT"FILEpgREL>TEXT>FILEJpiWRTINIT'plWRT"HEADERpnWRITEMESSAGEppFINDMESSAGE7psQUICKFINDMESSAGEp	uTYPEPAKNUMBERpxFILLTEXT7p{DISPLAY ERRORp}MOVEFILLLINEpCONVERTVARpPAKBWRT~pERRORMESSAGES:pPAKBLD p	OUTTIMEPAK pINTER pSTKERROR p	ikmprux{}	
,>8,>8,/O/7,~$$$~6$~P.7 k B4,>k,>4,>:,rL,>,>4,r4XB3@@x,>l,>l,>:,>m,Ze yXB% "bi "bi,>BZB,>,r( B& xXBz "bj "bj y Bz@@x "z,>,>l,>:,>m,WZB B B B/m/7,~$$%6$%$$z6$zH3B[}x  B@@ "% B& "% B0,>8,>8,x/74bu,	k+u,	 ",~   D." B  D   D "% B& "% B0,>8,>8,x/74b	,	k+	,	 ,~Message Writer can not find ID in text file p	ID:  p	EOFFLAG:   p		Additional info: p	,>.7@@   @ X@  `6  `7  @x,>:  ,>,>:,\sXB	! G@
  2@"+	,   @,>	K,>,>	K,>	L,y  @D  @E,>	L,>	M,>	M,>	N,>	N,>:,
@@+	9,>	L,>,>	L,>	O,rQ B@7@ "5B	;,>,>	L,r( B Z,>,>Z,>,>,rQ B@7@ "5B	:/	O+	</	P/	P+	6@+	D  b@l,F "b	I,>	J,>:,>	J,@
,>	Q,o/	Q`@+	>`	I,>	J,>:,>	J,E/	R/7,^,~$BEGIN p	R@@BEGIN p	TBEGINRequested message has no text in the file p	WID:  p	\Additional info: p	^Message Writer can not find ID in text file p	aID:  p	fAdditional info: p	h,>,>,>,>,>.7   @@  @1  3@1+	s   @1,>8,>;, B@@ "bB+	z,>8,>	L, /7,>8,>	L,7 B 2 B' "cB+
  1Z@ZH2b+
  @XD} $d6 $d6 H D~@@ Bx "},>,>;,>:,>;,aP/	QaB+
,>8,>	L,7 B/7+	}`@+
 "bB+
aT+
/7+
/7. 1`+	v`T@`V+
  b@+
  2@1+
  +
   @1.61v+	v a@+
)  "bBla@+
",FaT+
)  c@+
),>3,o ,>8,><,7 B/<+
"aT1T+2  3@+2   @ ' @H  @G  	S @   @(   @1 H! b@+
N  .2@@x,>9   Q 	,>,rj  X@@  `7! ~B@@  `7  `8 H X@}  `6  `6  @~@@x  },>,>:,\sXB@! G@@  `8 P@@x,>=,B H  `M B@@x,>=,@
/	P@ 0~.0`R+ H! b@+  c@+  X@~  `9  `9 H  @@@@x,>=  ~,>,>;,>:,>;,`:/>aB+
y HZ1`+
w/ X@~  `9  `9,>,>	L,r( B@@@x  },>,>>,>:,>;,Ze  F @ G ZZ2`+
v  XF{ "b: "b:  B@@@ @x  {,>,>;,>:,>;,`:/	Q`B 2/	P+  	V @+@@x,>?,>,>;,>:,>;,aP/>aB+ H.  @(,>8,>;, B/7 H  `M B@@x,>=,@
/9+
O   @(  @1  b@l,F H! c@+ aR+,>	K,>,>	K,>?,y G @K,>8,>@,>@,>A,>A+,>	K,>,>	K,>B,y G @L,>8,>B,>C,>C,>D,>:,
   @ H! G@  `M B@@@@x,E/OaR+"   @1aR+2  c@+2 H! b@+2 H.  @( @x,o B  c@+",>8,>;, B H  `M B@@x,>=,@
/<+"/7/7,^,^,^,^,^,~$$}6$}$$@$$H6$H$@$$~6$~$${6${[}3R$H(FI	\	`JKK	f	jLLMPACKET .:qR`o "b\ "b\ ] Bp "
XBpZ`p,>:,>^,>^,>:,>_,W,>_,>q,>:,XB@@ Bx,>^,>:,>_,W@@x,>`,>^,>:,>_,W "oXB "b],>`,>:,>a,E\@@l/a,~$$o6$o$lMo[}	NR$	@@MSGWRT can not output all variables pbMessage ID:  pgSTATUS:      piAdditional info: pl,>,>.7 }   @Z@5@xXP  `],>`,>:,>
,E\/<+
  X@  `6  `7 @ @x,>:,>
  ~,>,>;,>:,>
,aP/	P BaB+
,>},
s B/9+
7@+
,>	K,>,>	K,>
,y  @Q  @R,>	L,>
,>
,>
,>
,>:,
   @/O /7,^,^,~R$O[}fnPQRTTY:     ,>,>,>.7R`  `
f  `
g 
j @  BX@Z`! c@+
    @S+
-,>:,>9,>
k,rj  X@f  `
g! ~B@f  `
h  `
h  X@g  `
i,>
k,>:,>
l,B  f @S/	P  c@}+
2,>:,>z,>
l,>:,>
m,Ze/7+
7 S {X@  `M,>,>:,>
l,E\ y4r
] "~ .0O+
[ "bB{+
?@@x,>
m,>
l,>:,>
m,Ze/	Q z.  D@@x,>,>
l,>:,>
m,W x.,> x.,>,>
n,z "b
i "b
j 
n B@@@x "z,>,>
l,>:,>
m,W "bBv+
[ S $XD $dM B@@x,>
l,E\R` "b
f "b
g 
j B "BXBZ`/9/
o. 3 +
:  c@{+
c S  X@  `M B@@x,>
l,E\/9/</7,^,^,^,~$$6$$$f$$i6$i$k$$z6$zXffR$[}TSX#%! p
o\#%! p
p\\,>,>,>,>.<R`@` " G,>
@@x,>4b,r(1@+,r(/7+$$6$s
q[}
pR$p/-/--/0123456789 0123456789: unk..no MSGWRT: Unsupported variable type p
+e+f++++
+
+
++^+Y,>	K,>,>	K,>#,y z @-,>8,>$,>$,>%,>%,>:,
@@/O+,>|,>&,@R`.,>`[` &@#,>X@!Z`!R`!,>`,>`|0@Q`@@",>X@"Z`"@,>W/	Q+X00`+X@@x,>,,>+,>:,>(,W0@+R<<",]B@@@@x,>+,>:,>(,W+WZ%/X@%@@x,>+,>+,>:,>(,W/9/	PZ!+,>,,>{,>|,	   3@{/0+,>-+1@6@|+b 0 } 
/0+,>	L+,>0,>{+|5@|0}.Zp,>,>p|Q`,>,rfZp/< /7,^,^,^,~$$ 6$ $$!6$!$$#6$#$$$6$$$$%6$%$$&6$&p%&
XBpZ`p,>:,>d,>^,>:,>d,W,>_,>q,>:,XB@@ Bx,>^,>:,>d,W "oXB "ba,>e,>:,>e,E\R`1 "bb "bb f B1 "
XB2Z`2,>_,>w,>:,XB@@ Bx,>f,>:,>d,W "1XB "ba,>e,>:,>e,E\/gR`: "bc "bc g B; "(XB;Z`;,>_,>,>:,XB@@ Bx,>h,>:,>d,W ":XB "ba,>e,>:,>e,E\/	R ",~$$$16$1$$:6$:@[}R$.182:?SPEAR  Program error in module   -- Routine %SPEAR  Event file error detected in module  -- Routine %WARNING from module  --Routine -       ,>,>,> }0@+~,>!,>",>{,>"+0@+,>!,>#,>{,>#+5@	,>!,>$,>{,>$,>{ <~,]B@@ @x,>%,>:,>%,Ze/; 0! b@+,>:,>%,>:,>:,>:,>:,
/	P! c@+  b@+  AX@  `],>`,>:,>&,E\/<,>.,>&,>',>| <,]B@@ @x,>%,>:,>%,Ze/	P.01p+
 ",^,^,^,~`BCDEFGA[}R$HI  BL   DM M  DM M .$ DN  DJ N  DJ " B "cB+>,>?,>8,,>~,>~,7 B }  DM M  DM M .$ DN  DJ N  DJ/	Q+1 ,~NPKET_TAB found empty p
?Status:  pCAdditional Info:  pETIME_STAMP_MSG2 pHTIME_STAMP_MSG1 pK "cB+x,>{,>:,7 B "3B+[,>	K,>,>	K,>{,y  BU,>8,>|,>|,>},>},>:,
/O R BS  DS S." BT  Dh  Dl,>{,>8,x BT,>T S,>,1 B,>{,>~,7 B/77@+p R BS  DS ." BT  Fl@@x,>,1 B/9+e h2Bl+s,>~,v+w,>h,>l, B "j Bk,>,v/7/	P,>{,>:,/7 ,~NBGUUVRVY::,>,> ~/~ @a,>a,$,>,>5,$ Bx, B`   @dS`d,>d,$ Bd,>`,>d,  Bb,>b,# B_ _ @],>b,>_,$ Bx, Bc,>c,>5,$ Bx, Bc,>c,# B^ ^ @`,>c,>`,$ Bx, Bc,>c,>5,$ Bx, Bc,>8,$,>,>	L,$ Bx,  B_,>c,>_, Bc,>c,# B^,>_,>],>;,XB ,>.,>^,>	L,XB ,>.,>^,>	L,XB,>6,>,>6,>,>7,> <~,]B@@ @x,>7,>:,>8,Ze/8 ,^,^,~
Xefj[}@STK_ERROR calledPCword on stack: STACK address: , STACK length: , STACK depth: $STK_REMOVE operation failed$STK_TOP operation failed$STK_INSERT operation failedInvalid STACK operationRE-initializing stack,>,>,>.7,>6,>:,>:,>,>	L,> <~,S[,>6,>:,>:,>,>	L,>,>w,>:,XB,>,>,> <,]B/> @x <~,S[,>6,>:,>:,>,>	L,>,>s,>:,XB ,>_,>r,>:,XB ,>_ p ,>,>:,XB,>,>,>,>,>,>,> <},]B/m @x <~,S[O2@t+u,>6,>:,>:,>,>	L,> <~,S[/	P6@t+{,>6,>:,>:,>,>	L,> <~,S[/	P  2@t+,>6,>:,>:,>,>	L,> <~,S[/	P t3 O+1`+,>6,>	K,>:,>,>	L,> <~,S[/	P,>6,>:,>:,>,>	L,> <~,S[ pO2@q+@@+   @ p@@ p. / /7,^,^,^,~R$gph
Pijklmnop@
UNSPEC pNONE pALL p FINISHED p"EARLIEST p$LATEST p&CHECK p(ON p*OFF p+YES p-NO p.TRUE p0FALSE p1Next-question p3Repeat-frame p6next-frame p8USER p;INIT_USER p<GET_VALID_PARAMETER p	>GET_COMPLETE_PARAMETER pASEND_USER_REQUEST pEGET_LINE pHREAD_INDIRECT pJGET_FIELD pLCONCAT_FIELDS pNSET_RESPONSE_FLAGS p	QHANDLE_ESCAPES pTFILE_SPEC_FILL pVADD_TO_INPUT pYNEXT_FIELD p[FULL_QUERY p^PARTIAL_QUERY p`VALIDATE_PARAMETER p	cCHECK_LIST pfVERIFY_TYPE phDO_COMMAND pkSHOW_PARAMETER pmSAVE_PARAMETER ppSAVE_MODE prSAVE_LIST ptOUTPUT_PARAMETER_LIST p
vWRITE_VARIABLES pzRETYPE_LAST_LINE p}TEST_ETERNAL_TIMES p	FILL_ALL_DEFAULTS pSAVE_STRINGS pSEND_ERROR pCOMPARE_STRINGS pWRITE_INDENTED pCHANGE_DIALOG pFILL_DEFAULT p>ADGILNPSVX[]`behjmortvy|

 p' p(HELP p*+k
For more info on this field, type HELP p-One of the following: p
3-- Recognizedftypesiare<-- p:0123456789- p>ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789 pA%'?SPEAR  Validation failed p
G?May not havec"?",l"@",t<esc>,oort<backsp>in%file pK?ThatdfunctionispnotavailableapR%PleaseeselectfunctionfirstepV?Notoaevaliddnumberep	Z?Endwtimebmustobeolaterethansbeginotime p]?Valuefislouteoforangehpb?Nota validnamelordnumber p first prompt pSS$NOTSQDEV p
 "b+,>,,>-,>-,E "b+,>-,>-,>-,E "b,,>.,>-,>-,E@@o@@I@@J@@J@@M@@}@@| y Bq z B=5B ,>.,>,>/,>/,y/0,~ z B> { B>,>0,#! B3,@g5B(,>.,>,>/,>1,y/1,~,@m BK "GBI/2,~$v$$0r,<
h
pP,>&@,>,E /EaF+4,Y aF+B 33B>+< 32B>+B 32B>+>  +@ z {. ,>,> /EaF+3 I,^,~,>  @J  l @1  b@I,  b@I+N  b@I+N  c@I+P ,>,L/E,>J,} BI,>I, BI@@J K@  3@ $0D+\,>,>-,A  G@I,>,#! B3/+& G 1@Z5@` $A0D+c@@x,#! B3+ z3`q+h,>z,>-,"@ /	+h@"0B+k,;b+} 1@Z5Fn $&A0D+q,h+}"0B+s,+}@4@u " A0B+x,>	,"+{ 0@+|,>0,>/E+}   @J  b@I+  b@J+  b@I+, v/	 J,^,~IIII$III(|-------------------------------HJ p
 mode
,>,> 3Z4@# K  2@+,>C,>-,A/	 K  2@+,>D,>-,A/	Z2,>,>2,P 3 Z,>,n/ 3[4@:R`N  `A  `B D @N  X@OZ`O,>E,>E,>F[,>,>F,>G,>G <},]B@@ @x,>H,>-,>H,Ze,>H,>-,AZN/ X@T  `B  `C I @U,>I,>-,A/1 3[4@>,>,>,"f B{+?,>J,>,A/	,^,^,~$$N6$N$$T6$TOPKLMNON[}
TJ

?,>,>,>.	 K  c@}+T 3 @y @ @@,> ,>-,+W,>mZl".,>,r( B@ K,>@,>@,r4  K/ @@ K .$  b@I+_! c@I+` +a  @  }.  "cBJ+e,' BK "bBJ+g,@n BK "bB{+n "bBI+n!"bBI+n K $cD+sR`l "b "b K  Dm "KXBmZ`m K $bD+x "bBI+x!"cBI+,>/,#! B3,> ,>-,7/	aB+ H BC H BD,>!,>!,/	+z/E K $2D+ $GDI $cDI+
 $XDP $d $d "+ $XDP $d $d " DQ $XD} $d $d ,>,>#,r( 
 B0,>0 "|,>,>#,>-,>-,>-,>$,^. /$0P+b/%/	,^,^,^,~$$l6$l$$P6$P$$}6$}D@JJP[}H ?/@!
!,>,>,>. K  @a  @d  c@Q+/  3@b@@_6@_+c  `+,>,,>-,>o,@
 BQ  c@Q+F ` @b ` @_,>0,>p,>p,>-  |,>,>-,>q,^.`B { BQ  2@Q+B@1P "@1P  G @Q  b@Q+E,>q,"/E/r  c@Q+X,>p,>-,A,>,>-,AR`l  `  ` ` @m `X@mZ`m,>r,>p,>-,\s,>s,>,>s <,]B@@ @x,>t,>-,>q,ZeR`l/0/  c@Q+c  X@  `n  `o m @,>-,>t  ~,>,>#,>-,>q,aP/uaB+0 Q @J  c@J+g_ @b+k  `+,>,,>-,>-,E@@_/ "_/,^,^,^,~$$6$RLwd[}Q8pelf0 	@ 	 	,+:
?!
?/@! 	,+:
?/@! 	
?/@!,+:
?/@!.E"cBR`l@33D>"0B+("XBh"bU"bV@W+"1B+@33D>"0B+"XBh"bU"bVX+"XBh"bU"bVXBh,>Y,>t,>Y,>t,>-,>-,>Z,^.3[@1F"G&VG&WFi@3D>&@3D>"G0B+$"XBh"bU"bVZ+<@=3Dy"Ai0B+,"XBh"bU"bV [+<@ =3Dy "0B+3 "XBh "bU "bV [+< "2Bi+8 "XBh "bU "bV \+< "XBh "bU "bV \ Bh,>],>t,>Y,>t "z,>,>-,>Z,^.aB+C y DjZl4bP,>m/",>,r( Bg g1B+I0B+OZl/"XBl,>mZl/",>,r( Bg/	+G/	 =2By+S,>j,` Bj/E/1 j/E,~$$h6$huuvh[}vwyz| 	01234567890123456789:. } B~R`j "b "b,>mZl,>,r( Bk "KZl/XBkZ`k,>Y,>,>,> "|,>,>-,>,^.aB+p z DzZj Bl 3[0B1B+t+	,>Y,>,>,>- "y,>,>-,>,^.aB+z w Dv Bl "2Bl+	 "2Bv+	,>Y,>,>,> "v,>,>-,>,^.aB+ t DsZl.lZj.XBl,>s,` Br//r z1B+1"+
 a@+Z 4q+_,!  1 $l D1a@+_ Bx, 1@+b " Bn+b@/E+k 3[0D+g "r Bn+k "w BnR`l+k,>,>-,A/	5@o,>,>-,A,>n," "BBI/0@+~,>-,>,>,>-,>,Ze  b@I+x y2@=+x,>,- /E,>,>-,AZp5`~,>,>-,A  B@I/	/r ,^,^,^,^,~-kq)p[}>:..>]::>].:>].  ,>,>,>.E }R`@[k`  ` k @@ kX@@Z`@,>mZl/ ,>,r( Br r 3[@5F "@1F $G@1F "GJ1B+A@1@ "0B+&,>r,>#,r(/	1B+%,>],>,>+=O+A@1@ "0B+4,>],>,>,>,>-,>-,>,^. 0R+@,>],>,>,>-,>-,>-,>,^./r1B@+@@1@ "0B+9,>],>,>+=@1@. "0B+A,>],>,>,>,>-,>-,>,^. /r+A@1@+C0@.+N1R+NR`@[kb "b k B@ kXB@Z`@,>],>,>,>,>-,>-,>,^. /r1R+P2R#+~,>Y,>,>,>,>-,>-,>,^. "cBI+_,>],>,>,> "y,>,>-,>,^./r`B {0B+cZ@. X@@+c,>],>,>,>,>-,>-,>,^./r@@ Px,>1,>-,>,W@@ Px,>,>-,>,Ze  c@I+o,>	,>,>	,>
,>-,>-,>,^./r@@x,>1,>,>-,>,Ze 1 X@k  c@I+y@@x,>
,>,>-,>,W/% sX@@[s`  ` s @@/
+~@/	"/E,^,^,^,~$$@6$@
uv[}wxyz{|}s~t:>.] "BXB
 "b)Z"b)/+ B4f!XF &f* &f*,>Z,>,r( B "cBI+ ,>0,>+,>,,>,,>-,>-,>-,^./r0B+ Z
."XB/	+$R` "b* "b*@@,>-,>+,>1,>-,>-,W/ ",~$$
6$
$$6$~
[},>,>.	 }@ 33@> $@ 33@> "G1B+:,>-,>f,>1,>#,>-,>f,`:/u$W0D+;@+S 3$d0D+D,>-,>g,>1,>#,>-,>f,`:/uaB+C  +S  +S 3@[1F $0D+S,>-,>g,>1,>#,>-,>f,`:/u`B+S,>-,>g,>1,>#,>-,>f,`:/u`B+S  +S  4@a 1,>Z,>,r(@ "XB~ "be "be 1,>Z,>,r( B~@@x "},>,>,>-,>f,W/@4@b "/	,^,^,~$$~6$~+[}!#,>,> 3Z4@x,>,>-,A 3 Z,>,>-,"f,>,>-,A,>,>-,A 3[0@+w z3`q+w,>,>-,"f/	/%+{,>,>-,A,>,>-,"f 3Z4@~[0@+
 z3`q+
 z @+ z.,>,>-,"f/	. 3`+ 33@>+
,>f,>-,"f/	,>,>-,A/	/%,^,^,~2:6,-`p,>,>Rz3`q+,>z,>-,"@,["./	+"@B`@+"+3@Z4F,$,aD+",>W,>-,A@3Z,>,>-,A/%@5@$`"0B+,,>,>-,A+3[0D+*,>W,"++,>X,"R`l/@0`"0B+2,>,>-,A,>,>-,"f/%@1@+&@3@Z5@6$BGA0D+E[0@+<z,$@. +=!n,>-,>1,>,>#,>-,>X,`:/uaB+E+B@I@,>,>-,A/	[b.@1B,$0D+K,>,>-,A/	@`pX"0B+P,>z,>,"@/	>0@+S,>n,>-,"f/	,>,>-,A/	,^,^,~rw[},>,"X1@Z5F\$0D+c,3Z4D` $k,D1+c[5Dc,>u,"/E@/1@Z4FfX$G0D+lGz3bq+k,u,,"cB|+l,a`@+sR`l,"GBI,3[5Dq,v+s,>!,#!,B3/Eb,^,~,>@,>z,>-,"@[ZB{5HzB"w+0H+zb{.,QD1!"+@"|Bn,3@[1B &@0H+"A,B|,"bB|,>`@+[5Bn1BwR`l,>n,"/E/	,,^,~SPRCMD.COM:LP-9999-@Unidentifiedresponse"type."pb,,>.,>-,>/,B /aR+.@@x,>1,>1,>-,>.,Ze "b,,>.,>-,>2,E " B1/r0@+C@,>!,>1,>2,>-,>-,>-,>.,^. 0R+:,>,>1,>3,>-,>-,>-,>.,^./raB+;,>3+A@@x,>1,>4,>#,>-,>.,`d/aB+B,>4,"@/E/r0@+E@ "@ B0@+H@ "E B0@1@+J+@px,>g,>1,>#,>-,>.,aP/aB+[,>!,>1,>,>-,>-,>-,>.,^. 0R+X 1Z1d+Z 3[0D+Z@,>5,"/E/r+ 3[0D+@,>5,"/E0@1@+a+t@ "XB} "b "b  1  D~@@x,>6 "},>,>#,>-,>.,`:/aB+t@@x,>1 "~,>,>-,>-,>-,>-,YS/u`B ~aB+t Dx,: B10@1@+v+@,! 5R,>,>1,>6,>-,>-,>-,>.,^./raB+,>1,$+,>1,$ 4R,>7,>,>-,XB@@ Bx,>1,>-,>.,Ze " B1 3[0D+ R Rx,>7+
,  p
,>,>,>,>,> 3@r3,>,>-,AZN4`,>H,>-,A,>I,>-,A,>,>-,A/u } O+F PC,>!,>-, }.  @3 34BE[4@E7@@}+/,>,>-,A 3 [,>,>-,A,>M,>-,A 3[0B++,>9+-1B+-,>@}+-,>9,>-,A/u+E,>!,>,7 BI I`@3R3+:,>,>-,A 3 [,>,>-,A,>M,>-,A 3+Da@+=,>N,>-,A/	  c@I+E,>D,>-,A,>N,>-,A,>!,>,7 BI/u+=/	/	.030+,>,>-,A V3/%,^,^,^,^,^,~
,>O,}4DX,O+W[.+32H+W,+X.3+S42`Q| .,>@},!y B@}&3!"c@+`.|,>,/E/E "},^,^,^,~Programnamedefined7twicep3 @) M B1+ ,> ,"O/E/	 ,^,~fV  B? } D? BC } DD,>-,>?,>g,>#,>-,> ,aP/uaB+ ,>-,>?,>g,>#,>-,> ,aP/uaB+ ,> ,>!,,>!,>!,/% @@},~[}SPRCMD.TMP1(36),>,>,>  `+,>-,>-,>-,E@@x,>,,> C,rj  X@  ` A! ~B@  ` B  ` B  *X@! G@  G@  `+,>-,>-,> C,B  +X@  `+,>-,>-,> C,E\O } O+ : @}4B 7XB "b+,>-,>-,> C,E\. /E+ : /,>,>, E/	.030+ 1  `+,>-,>-,> C,E/1,^,^,^,~$$$$6$R$TVEV,>,>,>@` ~ @C,>!,>-,,>!,>,7 BI  c@I+ Q.0,>!,>,7 BI/	+ L4p r,>7,>{,>-,XB,>s,> t,> <,]BX@  `+,>-,>-,> u,E\,>7,>,>-,XB,>s,> u,> <,]BX@  `+,>-,>-,> u,E\,>!,>-,,>!,>,7 BI  c@I+ m DX@  `+,>-,>-,> u,E\,>!,>,7 BI/+ e  .X@  `+,>-,>-,> u,E\/ v/%,^,^,^,~,R$-H
.	"GBI,>,>-,A"cBJ+!!"GBI@@J"b+,>,,>-,>!,E`K@@,@m!BK+!!"BBI!{XB~"be"beKDy[4D!"~,>,>-,A/	,>mZl,>,r(,>K,>,r4XB|"b!"b!K!D}Z|4b!!"|,>,>-,A/	/E//	,~$$|6$|R$,>,>!1,>-,"@[0B+!,Z,6/[H1B+!K0B+!e  X@|  `!  `! 1  @}@@x,>!y  |,>,>#,>-,>!x,`:/aB+!e@@x,>1  },>,>-,>-,>-,>-,YS/u`B }aB+!^ Xx,: B1,>1,$ ,>7,>,>-,XB@@ Bx,>,>-,>!x,Ze/r[H0@+!j@@x,>1,>9,>-,>!x,Ze/%[H0@+!o@@x,>1,>9,>-,>!x,Ze/%  k @1,>@},!y B@}/u.030+!9 V1/,^,^,^,^,^,^,~[}/.	7@~7@1+"R` "b" "b"@@x,>! ",>,>#,>-,>-,>",PJaB+" } D{ {R` $d" $d"@@/u 14B"
-       
,>,>.	 }R`8  `"9  `": ": @8  (X@9Z`9  X@  `"  `" p @x,>-,>";  ~,>,>#,>-,>";,`:/uaB+"(,>"<,>-,A/	Zp/ X@  `"  `" p` Bx,>E,>"<,>"=,>"=  },>,>">,>"> <},]B@@ @x,>"?,>-,>";,Ze,>"?,>-,A/"?/	,^,^,~$$86$8/9[}K:;<=>8`,>,>,>,>.	@   " .0 |2`+"^ 1Z4f"^.  1 XD $d" $d" H D@,>-,> "~,>,>#,>-,>"a,`:/uaB+"W."bX "cB|+"W,>,>-,"f/	,>-,>1,>,>#,>-,>"a,`:/uaB+"]Q4+"^9"E /	,^,^,^,^,~[}						      >  (): ,>,>.	R`  `#  `# # @  @X@Z`,>,>-,A 3"#&" X@~  `e  `e # @@@x  ~,>,>#,>-,>#,Ze 3  c@+"}@@x,>#,>#,>-,>#,W/%  b@z+#@@x,>#,>#,>-,>#,W/%@@x,>z,>#,>-,>#,W  c@x+# 32\=+#	@@x,>#+#Zp4@# "@bBp+#,>#,># ,>,>#  <,]B@@ @x,>#,>-,>#,W/r@@x,>#!,>#,>-,>#,W/%,>#,>x,A/"?Z/	,^,^,~$$6$$?"b[}h,>,>,> ~@1D "  #pG@1D "0B+#* y+#P@1D "0B+#. 3[+#P 0@+#0 >+#P 0@+#3 >+#P@1D "0B+#6 =+#P #p0@+#9 3+#P0R+#; 3[+#P  b@|+#B z3bq+#B {. 3`q+#B "+#B@0B+#F z {. +#P 3 #q0@+#O o4b#K0b
+#K>o.#r+#N,>#s,>#s,>#,O/  @3 3Z  @c@I+#R   @J@@|  b@@aR+#U[@ 32P`R+#h4B#h3B>+#h  b@3P>+#\2P>+#h #q0@+#d o4"#a0"
+#a:o."o+#c,>#s,>#s,>,O/ 3 @ #q"#rG0@+#h 3Q@@4P#k,>Z@,>,#t/	Z@ @z z  @z ,^,^,^,~II@
@oo
 4B#,>-,>,>,>-,>#,Ze } XDk | $cD+#~,>k,>!x,r(,>,6//,~[}UNSPEC p#NONE p$ALL p$FINISHED p$EARLIEST p$LATEST p$CHECK p$
ON p$
OFF p$YES p$NO p$TRUE p$FALSE p$Next-question p$Repeat-frame p$next-frame p$/GO p$/BREAK p$/CLEAR p$!/HELP p$#/REVERSE p$%/SHOW p$'Type <cr> to confirm p
$)MODE COMPLETION p$,DSK:SPRCMD.CMD p$/Indirect command file specification p$2INDIRECT FILES p$7
1. Press the RETURN key to sequence through the menu.
2. Enter the menu number (#) of the topic that you want to investigate.
3. Type MENU to return to the previous (higher level) menu.
 p_$9
1. Press the RETURN key to procede to the next frame of information.
2. Press the BACKSPACE key to review the previous frame of information.
3. Type MENU to return to the topic menu.
 p^$N
That's it.  There is no more information available on the topic.

1. Press the RETURN key to proceed to the next topic on the menu.
2. Type MENU to return to the topic menu.
 pZ$b
The topic you are backing into may consist of several frames.

1. Type BEGIN to go to the beginning of the topic
2. Press the BACKSPACE key to continue in a reverse direction.
3. Press the RETURN key to go in a forward direction.
4. Type MENU to return to the topic menu.
 p
$u
Read the statement, then:

1. Type TRUE  if you believe that the statement is true
2. Type FALSE if you believe that the statement is false
3. Press the RETURN key if you are unsure of the answer.
4. Press the BACKSPACE key to return to the Topic Menu 
5. Type NEXT to pass, and go on to the next statement.
 p%
Read the question, then:

1. Enter the number that corresponds to the most correct answer.
2. Press the RETURN key if you are unsure of the correct answer.
3. Press the BACKSPACE key to return to the Topic Menu 
4. Type NEXT to pass, and go on to the next statement.
 p	%4
You have just answered a question. You can:

1. Press the RETURN key. If the answer was correct you will go on to the
   next question. If it was incorrect then the question will repeat.
2. Type NEXT to go to the next question regardless of the answer.
3. Press the BACKSPACE key to re-display the question.
4. Type RANDOM QUESTION if you want to select another random question.
rpB%Qmenuehelpp%ytexthelp p%{fwdtranshelp p%}revtranshelp p%queryhelp p&nohelp p&ranquesthelp p&questhelp p&	anshelp p&Your selection please (Topic #) p&
&Your answer please (#) p&Your answer please (T/F) p
&Your answer please (Y/N) p
&BEGIN p& QUERY p&"NEXT QUESTION p&$RANDOM QUESTION p&&MENU p&)0 p&+1 p&,2 p&.3 p&/4 p&15 p&26 p&47 p&58 p&79 p&810 p&:11 p&;12 p&=13 p&>14 p&@15 p&A16 p&C17 p&D18 p&F19 p&G20 p&I21 p&J22 p&L23 p&M24 p&O25 p&P26 p&R27 p&S28 p&U29 p&V30 p&X31 p&Y32 p&[33 p&\34 p&^35 p&_36 p&a37 p&b38 p&d39 p&e40 p&g41 p&h42 p&j43 p&k44 p&m45 p&n46 p&p47 p&q48 p&s49 p&t50 p&v51 p&w52 p&y53 p&z54 p&|55 p&}56 p&57 p'58 p'59 p'60 p'menu_res_error_msg p	'query_res_error_msg p	'	ran_quest_res_error_msg p'
text_res_error_msg p	'fwd_trans_res_error_msg p'ans_res_error_msg p'rev_trans_res_error_msg p'SPRID.LOGSPRID.LOGSPEAR.MSGTOP p' CONTROL_LOOP p'!'#
 p'%EXIT p'&''TTY:SPEAR.MSG p')INFO -- Pre-loading text file p'+SPEAR.MSGEND_FILE p'0SPRCMD.TMPNOUNSTUDENT ID :	 p'4INVALID STUDENT ID p	'7OTTY:UN.(4 "bB3+'R "5XB "b(1,>(4,>(5,>(5,B,>(6,@@x,>(6,>(5,>(5,>(5,>(5,
,>(7,>(7,P,>(8,n " B3 (QB( (/"QB-[-QB- "b(1,>(4,>(5,>(5,E/(8+(0 "3B4, " B4@@5,q "6XBu "b(2,>(9,>(5,>(5,B "b(2,>(9,>(5,>(5,@
 "b(2,>(9,>(5,>(5,@
@@x,>(9,>(:,>(5,>(:,Ze,>(;,>(:,>(;,>(<,>(5,>(5,>(:,^.@@x,>(<,>(<,>(=,>(5,>(:,a/(=aB+'q " B:,>(>,>(>,>(?,>(?,>(@,>(5,
,/(@@@x,>(A,>(<,>(=,>(5,>(:,`8B4."+>(9,>(5,>(5,E"<XB"b(1,>(4,>(5,>(5,B,>(A,>8,>(B,>(B,>(5,>(:,`:/(=aB+( $' D "9XB:!"GB> "b(3,>(D,>(5,>(5,B "XBA "b(3,>(D,>(5,>(5,E\,>(D,>3,>(5,XBXBA "b(3,>(D,>(5,>(5,E\ "b(3,>(D,>(5,>(5,E/(E/(E+(,@@x,#! B3 " cB8+( "b(1,>(4,>(5,>(5,E,/(F/(4,~$$y$$n6$n$>R$'+'/'/'2xuz[}78('99::0;=>:	`0STUDENT ID :	 p(FMay need to create a Student Log File p(HCorrect response to SPEAR> for a "NEW USER" is Instruct or I p(MSTUDENT ID :	 p(UTHIS IDENTIFIER NOT IN THE STUDENT LOG FILE p(WType Instruct or I to following prompt p(].)0 "WXBX!"GB\ "GB] "b)0,>)1,>(5,>)1,B/(E1B+(s " BA,>(>,>)2,>)2,>)3,>)3,>(5,
@@x,>)4,>(5,>(5,>(5,>(5,
,/)4 "9XB:!"GB> "b(3,>(D,>(5,>)5,B "b)0,>)1,>(5,>)5,@
/(EaB+)@@x,>)5,>(:,>(=,>(5,>)6,aP/(=aB+) )5XBA "b(3,>(D,>(5,>)5,E\ " B?+) " B? "b)0,>)1,>(5,>)5,@
@@x,>)5 "|,>,>(5,>(5,>(5,>)6,YSaB+) z D8/(@/(E+(x!"GB\ "b)0,>)1,>(5,>)5,E "b)0,>)1,>(5,>)5,GO!"GB> "b(3,>(D,>(5,>)5,E6@?+)# "b(3,>(D,>(5,>)5,GO/(E "3B?+)- " BB,>(>,>)6,>)7,>)7,>)8,>(5,
@@x,>)8,>(5,>(5,>(5,>(5,
,/)4@@?@@?/(E/)0,~$\XRL(M@AA(TXR$][}(\BBC(ag "	` )@,$,$,$,$,$ @zG,,'</(=	b+)?CUNSPEC p)@NONE p)BALL p)DFINISHED p)EEARLIEST p)GLATEST p)ICHECK p)KON p)MOFF p)OYES p)PNO p)RTRUE p)SFALSE p)UNext-question p)WRepeat-frame p)Ynext-frame p)\farewell p)^course_admin p)`course_admin_a p)cR.T.cou_ovr_a p)eA. p)hB. p)iC. p)kD. p)lE. p)nM. p)ofeedback p)qspear_man p)srandom_question p)u1 p)x2 p)y3 p){4 p)|5 p)~6 p)7 p*8 p*9 p*10 p*11 p*12 p*13 p*
14p*15.p*18p*19 p*20p*21.p*22p*23 p*24p*25.p*26p*27p*28p*29.p*"30p*#31 p*%32p*&33.p*(34p*)35Lp*+36p*,37.p*.38p*/39p*1402p*241.p*442p*543p*7445p*845.p*:46p*;47 p*=481p*>49.p*@50p*A51ep*C524p*D53.p*F54p*G55.p*I562p*J57.p*L58p*M59.p*O603p*PEnter2a1randomnumberbetween611and60p*R1.1.1p*W1.1.1Ap*Y1.1.1Bp*[1.1.1Cp*]1.1.2p*71.1.3p*a1.1.4p*c1.1.4Ap*e1.1.5p*g1.1.5Ap*i1.1.6p*k1.1.7p*m1.1.8p*o1.1.9p*q1.2.1p*s1.3.1p*u1.3.2p*w1.4.1p*y1.4.2p*{1.5.1p*}1.5.2p*1.5.3p+1.5.4p+1.5.5p+1.5.6p+1.6.1p+	1.6.2p+1.6.3p+at p.tops10efq1af p.tops10efq2 p.tops10efq2at p.tops10efq2af p.tops10efq3 p.tops10efq3at p.tops10efq3af p."tops10efq4 p.%tops10efq4at p.'tops10efq4af p.*tops10efq5 p.-tops10efq5at p.0tops10efq5af p.3tops10efq6 p.6tops10efq6at p.8tops10efq6af p.;tops10efq7 p.>tops10efq7at p.Atops10efq7af p.Dtops10efq8 p.Gtops10efq8at p.Itops10efq8af p.Ltops10efq9 p.Otops10efq9at p.Rtops10efq9af p.Utops10efq10 p.Xtops10efq10at p.Ztops10efq10af p.]tops10eflq p.`tops20ef p.ctops20efa p.etops20efq1 p.htops20efq1at p.jtops20efq1af p.mtops20efq2 p.ptops20efq2at p.stops20efq2af p.vtops20efq3 p.ytops20efq3at p.{tops20efq3af p.~tops20efq4 p/tops20efq4at p/tops20efq4af p/tops20efq5 p/
tops_20_ef_q5_at p/
tops120.efq5afNp/tops20pefq6.p/tops20efAq6LatEp/tops20ef3q6.af p/topsY20 efMq7p/tops201ef.q7atp/topsE20Refq7af.p/tops20efAq8Ep/#tops20pefq80atFp/&tops'20Tef.q81af p/)topsd20efq9 p/,topsd20efq9atp/.tops120fefq9afnp/1tops20pefq10np/4tops20pefq106atap/7tops20efaq10dafp/:tops;20aefilqap/=vax0vmsaefxap/?UNSPECap/BNONEp/DALLap/EFINISHEDap/GEARLIESTnp/ILATESTp/KCHECK p/MONap/OOFFp/PYESp/RNOp/STRUEnp/UFALSEp/VNext-questionp/XRepeat-framep/[next-framep/]3.0.ap/`R.T.3.0.ap/a3.M.p/cUNSPEC p/eNONEap/gALLp/hFINISHED p/jEARLIESTap/lLATESTap/nCHECKnp/pON p/rOFFap/sYESp/uNO p/vTRUE.p/xFALSE.p/yNext-question1p/{Repeat-frameMp/~next-frame p03.1.0.p03.1.0.A.Ip03.1.0.B.Ap0R.T.3.1.0.B.p0	3.1.M. p03.1.1. p0
CHECK p1
ON p1OFF p1YES p1NO p1TRUE p1FALSE p1Next-question p1Repeat-frame p1next-frame p13.1.2.1.0. p1R.T.3.1.2.0. p1!3.1.2.1.M. p1$3.1.2.1.1.0. p1&R.T.3.1.2.1.1.0. p1)3.1.2.1.1.M. p1,3.1.2.1.1.1. p1.3.1.2.1.1.1.A. p11R.T.3.1.2.1.1.1.A. p	133.1.2.A.1.1.1 p163.1.2.A.1.1.1.A p19R.T.3.1.2.A.1.1.1.A p	1<3.1.2.B.1.1.1 p1?3.1.2.B.1.1.1.A p1AR.T.3.1.2.B.1.1.1.A p	1D3.1.2.C.1.1.1 p1G3.1.2.C.1.1.1.A p1JR.T.3.1.2.C.1.1.1.A p	1M3.1.2.1.1.2. p1P3.1.2.1.1.2.A. p1RR.T.3.1.2.1.1.2.A. p	1U3.1.2.1.1.3. p1X3.1.2.1.1.3.A. p1ZR.T.3.1.2.1.1.3.A. p	1]3.1.2.1.1.4. p1`3.1.2.1.1.4.A. p1bR.T.3.1.2.1.1.4.A. p	1e3.1.2.A.1.1.4 p1h3.1.2.A.1.1.4.A p1jR.T.3.1.2.1.1.5.A p1m3.1.2.1.1.5 p1p3.1.2.1.1.5.A p1sR.T.3.1.2.1.1.5.A p1u3.1.2.A.1.1.5 p1x3.1.2.A.1.1.5.A p1{R.T.3.1.2.A.1.1.5.A p	1~3.1.2.1.1.6 p23.1.2.1.1.6.A p2R.T.3.1.2.1.1.6.A p23.1.2.1.1.7 p2	3.1.2.1.1.7.A p2R.T.3.1.2.1.1.7.A p23.1.2.1.1.8 p23.1.2.1.1.8.A p2R.T.3.1.2.1.1.8.A p23.1.2.1.1.9 p23.1.2.1.1.9.A p2F.T.3.1.2.1.2.1. p2R.T.3.1.2.1.1.9.A p2!3.1.2.1.2.1. p2$3.1.2.1.2.1.A. p2&F.T.3.1.2.1.3.0. p2)R.T.3.1.2.1.2.A. p2,3.1.2.1.3.0. p2/R.T.3.1.2.1.3.0. p213.1.2.1.3.M. p243.1.2.1.3.1. p27R.T.3.1.2.1.3.1. p293.1.2.1.3.2. p2<F.T.3.1.2.1.4.0. p2?R.T.3.1.2.1.3.2. p2B3.1.2.1.4.0. p2ER.T.3.1.2.1.4.0. p2G3.1.2.1.4.M. p2J3.1.2.1.4.1. p2M3.1.2.1.4.1.A. p2OR.T.3.1.2.1.4.1.A. p	2R3.1.2.1.4.2. p2U3.1.2.1.4.2.A. p2WF.T.3.1.2.1.5.0. p2ZR.T.3.1.2.1.4.2.A. p	2]3.1.2.1.5.0. p2`3.1.2.1.5.0.A. p2bR.T.3.1.2.1.5.0. p2e3.1.2.1.5.M. p2h3.1.2.1.5.1. p2j3.1.2.1.5.1.A. p2mR.T.3.1.2.1.5.1.A. p	2o3.1.2.1.5.2. p2r3.1.2.1.5.2.A. p2uR.T.3.1.2.1.5.2.A. p	2w3.1.2.1.5.3. p2z3.1.2.1.5.3.A. p2}R.T.3.1.2.1.5.3.A p23.1.2.1.5.4. p33.1.2.1.5.4.A. p3R.T.3.1.2.1.5.4.A. p	33.1.2.1.5.5. p3
3.1.2.1.5.5.A.Ap3	33.1.2.1.5.6. p33.1.2.1.5.6.A. p3F.T.3.1.2.1.6.0. p3UNSPEC p3NONE p3ALL p3FINISHED p3EARLIEST p3!LATEST p3#CHECK p3%ON p3'OFF p3)YES p3*NO p3,TRUE p3-FALSE p3/Next-question p31Repeat-frame p33next-frame p36R.T.3.1.2.1.5.6.A p383.1.2.1.6.0. p3;3.1.2.1.6.0.A. p3>3.1.2.1.6.0.B. p[email protected]. p3CR.T.3.1.2.1.6.0.C p3Erevtranshelp p3H3.1.2.1.6.M. p3K3.1.2.1.6.1. p3M3.1.2.1.6.1.A. p3P3.1.2.1.6.1.B. p3R3.1.2.1.6.1.C. p3U3.1.2.1.6.1.D. p3W3.1.2.1.6.1.E. p3ZR.T.3.1.2.1.6.1.E. p	3\3.1.2.1.6.2. p33.1.2.1.6.2.A. p3b3.1.2.1.6.2.B. p3d3.1.2.1.6.2.C. p3g3.1.2.1.6.2.D. p3i3.1.2.1.6.2.E. p3lR.T.3.1.2.1.6.2.E p3n3.1.2.1.6.3. p3q3.1.2.1.6.3.A. p3t3.1.2.1.6.3.B. p3v3.1.2.1.6.3.C. p3y3.1.2.1.6.3.D. p3{R.T.3.1.2.1.6.3.D. p	3~3.1.2.1.6.4. p43.1.2.1.6.4.A. p43.1.2.1.6.4.B. p4R.T.3.1.2.1.6.4.B. p	43.1.2.1.6.5. p43.1.2.1.6.5.A. p43.1.2.1.6.5.B. p43.1.2.1.6.5.C. p4R.T.3.1.2.1.6.5.C. p	43.1.2.1.6.6. p43.1.2.1.6.6.A. p43.1.2.1.6.6.B. p43.1.2.1.6.6.C. p4 R.T.3.1.2.1.6.6.C. p	4"3.1.2.1.6.7. p4%3.1.2.1.6.7.A. p4(R.T.3.1.2.1.6.7.A. p	4*3.1.2.1.6.8. p4-3.1.2.1.6.8.A. p40R.T.3.1.2.1.6.8.A. p	423.1.2.1.6.9. p453.1.2.1.6.9.A. p48R.T.3.1.2.1.6.9.A p4:3.1.2.1.6.10. p4=3.1.2.1.6.10.A. p[email protected]. p	4C3.1.2.1.6.11. p4F3.1.2.1.6.11.A. p4HR.T.3.1.2.1.6.11.A. p	4K3.1.2.1.6.12. p4N3.1.2.1.6.12.A. p4QF.T.3.1.2.1.7.0. p4TR.T.3.1.2.1.6.12.A p	4W3.1.2.1.7.0. p4ZR.T.3.1.2.1.7.0. p4\3.1.2.1.7.M. p43.1.2.1.7.1. p4b3.1.2.1.7.1.A. p4dR.T.3.1.2.1.7.1.A. p	4g3.1.2.1.7.2. p4j3.1.2.1.7.2.A. p4lR.T.3.1.2.1.7.2.A. p	4o3.1.2.1.7.3. p4r3.1.2.1.7.3.A. p4tR.T.3.1.2.1.7.3.A. p	4w3.1.2.1.7.4. p4z3.1.2.1.7.4.A p4|R.T.3.1.2.1.7.4.A p43.1.2.1.7.5 p53.1.2.1.7.5.A p5F.T.3.1.2.1.8.1. p5R.T.3.1.2.1.7.5.A p5
3.1.2.1.8.1. p53.1.2.1.8.2. p53.1.2.1.8.2.A. p5F.T.3.1.2.1.9.1. p5R.T.3.1.2.1.8.1.A. p	53.1.2.1.9.1. p53.1.2.1.9.1.A. p5F.T.3.1.2.2.0. p5"UNSPEC p5$NONE p5&ALL p5(FINISHED p5)EARLIEST p5+LATEST p5-CHECK p5/ON p51OFF p53YES p54NO p56TRUE p57FALSE p59Next-question p5;Repeat-frame p5=next-frame p[email protected]. p5B3.1.2.2.0. p5ER.T.3.1.2.2.0. p5G3.1.2.2.M. p5J3.1.2.2.1.0. p5LR.T.3.1.2.2.1.0. p5O3.1.2.2.1.M. p5R3.1.2.2.1.1.0. p5TR.T.3.1.2.2.1.1.0. p	5W3.1.2.2.1.1.M. p5Z3.1.2.2.1.1.1.0. p5\3.1.2.2.1.1.1.0.A. p	53.1.2.2.1.1.1.0.B. p	5bR.T.3.1.2.2.1.1.1.0.B. p5e3.1.2.2.1.1.1.M. p5i3.1.2.2.1.1.1.1. p5l3.1.2.2.1.1.1.1.A. p	5oR.T.3.1.2.2.1.1.1.1.A. p5r3.1.2.2.1.1.1.2. p5u3.1.2.2.1.1.1.2.A. p	5xR.T.3.1.2.2.1.1.1.2.A. p5{3.1.2.2.1.1.1.3. p53.1.2.2.1.1.1.3.A. p	6R.T.3.1.2.2.1.1.1.3.A. p63.1.2.2.1.1.1.4 p6R.T.3.1.2.2.1.1.1.4. p
63.1.2.2.1.1.1.5 p63.1.2.2.1.1.1.5.A p6R.T.3.1.2.2.1.1.1.5.A p
63.1.2.2.1.1.1.6 p63.1.2.2.1.1.1.6.A p63.1.2.2.1.1.1.6.B p6R.T.3.1.2.2.1.1.1.6.B p
6!3.1.2.2.1.1.1.7. p6%F.T.3.1.2.2.1.1.2.0. p
6(R.T.3.1.2.2.1.1.1.6. p
6+3.1.2.2.1.1.2.0. p6/R.T.3.1.2.2.1.1.2.0. p
623.1.2.2.1.1.2.M p653.1.2.2.1.1.2.1. p68R.T.3.1.2.2.1.1.2.1. p
6;3.1.2.2.1.1.2.2. p6?R.T.3.1.2.2.1.1.2.2. p
6B3.1.2.2.1.1.2.3. p6ER.T.3.1.2.2.1.1.2.3. p
6H3.1.2.2.1.1.2.4. p6L3.1.2.2.1.1.2.4.A. p	6O3.1.2.2.1.1.2.4.B. p	6RF.T.3.1.2.2.1.1.3.1. p
6UR.T.3.1.2.2.1.1.2.4.B. p6X3.1.2.2.1.1.3.1. p6\F.T.3.1.2.2.1.2.0. p	6_R.T.3.1.2.2.1.1.3.1. p
6b3.1.2.2.1.2.0. p6eR.T.3.1.2.2.1.2.0. p	6h3.1.2.2.1.2.M. p6k3.1.2.2.1.2.1.0. p6mR.T.3.1.2.2.1.2.1.0. p
6p3.1.2.2.1.2.1.M. p6t3.1.2.2.1.2.1.1. p6w3.1.2.2.1.2.1.1.A. p	6zR.T.3.1.2.2.1.2.1.1.A. p6}3.1.2.2.1.2.1.2. p73.1.2.2.1.2.1.2.A. p	7F.T.3.1.2.2.1.2.2.0. p
7R.T.3.1.2.2.1.2.1.2.A. p7
3.1.2.2.1.2.2.0.p7
73.1.2.2.1.2.2.M. p73.1.2.2.1.2.2.1. p7R.T.3.1.2.2.1.2.2.1. p
73.1.2.2.1.2.2.2. p7R.T.3.1.2.2.1.2.2.2. p
7 3.1.2.2.1.2.2.3. p7$R.T.3.1.2.2.1.2.2.3. p
7'3.1.2.2.1.2.2.4. p7*3.1.2.2.1.2.2.4.A. p	7-3.1.2.2.1.2.2.4.B. p	70F.T.3.1.2.2.1.2.3.1. p
73R.T.3.1.2.2.1.2.2.4.B. p773.1.2.2.1.2.3.1. p7:F.T.3.1.2.2.1.3.0. p	7=R.T.3.1.2.2.1.2.3.1. p
[email protected]. p7D3.1.2.2.1.3.0.A. p7FR.T.3.1.2.2.1.3.0.A. p
7I3.1.2.2.1.3.M. p7M3.1.2.2.1.3.1. p7O3.1.2.2.1.3.1.A. p7RR.T.3.1.2.2.1.3.1.A. p
7U3.1.2.2.1.3.2. p7XR.T.3.1.2.2.1.3.2. p	7[3.1.2.2.1.3.3. p7^3.1.2.2.1.3.3.A. p7`R.T.3.1.2.2.1.3.3.A. p
7c3.1.2.2.1.3.4. p7g3.1.2.2.1.3.4.A. p7iR.T.3.1.2.2.1.3.4.A. p
7l3.1.2.2.1.3.5. p7p3.1.2.2.1.3.5.A. p7rR.T.3.1.2.2.1.3.5.A. p
7u3.1.2.2.1.3.6. p7y3.1.2.2.1.3.6.A. p7{R.T.3.1.2.2.1.3.6.A. p
7~3.1.2.2.1.3.7. p83.1.2.2.1.3.7.A. p8R.T.3.1.2.2.1.3.7.A. p
83.1.2.2.1.3.8. p83.1.2.2.1.3.8.A.p8
83.1.2.2.1.4.1 p8F.T.3.1.2.2.2.0. p8UNSPEC p8NONE p8ALL p8 FINISHED p8!EARLIEST p8#LATEST p8%CHECK p8'ON p8)OFF p8+YES p8,NO p8.TRUE p8/FALSE p81Next-question p83Repeat-frame p85next-frame p88R.T.3.1.2.2.1.4.1 p8:3.1.2.2.2.0. p8=R.T.3.1.2.2.2.0. p[email protected]. p8C3.1.2.2.2.1.0. p8ER.T.3.1.2.2.2.1.0. p	8H3.1.2.2.2.1.M. p8K3.1.2.2.2.1.1.0. p8MR.T.3.1.2.2.2.1.1.0. p
8P3.1.2.2.2.1.1.M. p8T3.1.2.2.2.1.1.1. p8W3.1.2.2.2.1.1.1.A. p	8ZR.T.3.1.2.2.2.1.1.1.A. p8]3.1.2.2.2.1.1.2. p8`3.1.2.2.2.1.1.2.A. p	8cR.T.3.1.2.2.2.1.1.2.A. p8f3.1.2.2.2.1.1.3. p8j3.1.2.2.2.1.1.3.A. p	8mR.T.3.1.2.2.2.1.1.3.A. p8p3.1.2.2.2.1.1.4. p8sR.T.3.1.2.2.2.1.1.4. p
8v3.1.2.2.2.1.1.5. p8z3.1.2.2.2.1.1.5.A. p	8}R.T.3.1.2.2.2.1.1.5.A. p93.1.2.2.2.1.1.6. p9F.T.3.1.2.2.2.1.2.0. p
9R.T.3.1.2.2.2.1.1.6. p
9
3.1.2.2.2.1.2.0.p9
93.1.2.2.2.1.2.M p93.1.2.2.2.1.2.1. p9R.T.3.1.2.2.2.1.2.1. p
93.1.2.2.2.1.2.2. p9R.T.3.1.2.2.2.1.2.2. p
9 3.1.2.2.2.1.2.3. p9$R.T.3.1.2.2.2.1.2.3. p
9'3.1.2.2.2.1.2.4. p9*3.1.2.2.2.1.2.4.A. p	9-F.T.3.1.2.2.2.1.3.1. p
90R.T.3.1.2.2.2.1.2.4.A. p943.1.2.2.2.1.3.1. p97F.T.3.1.2.2.2.2.0. p	9:R.T.3.1.2.2.2.1.3.1. p
9=3.1.2.2.2.2.0. p9AR.T.3.1.2.2.2.2.0. p	9C3.1.2.2.2.2.M. p9F3.1.2.2.2.2.1.0. p9IR.T.3.1.2.2.2.2.1.0. p
9L3.1.2.2.2.2.1.M. p9O3.1.2.2.2.2.1.1. p9R3.1.2.2.2.2.1.1.A. p	9UR.T.3.1.2.2.2.2.1.1.A. p9X3.1.2.2.2.2.1.2. p9\3.1.2.2.2.2.1.2.A. p	9_F.T.3.1.2.2.2.2.2.0. p
9bR.T.3.1.2.2.2.2.1.2.A. p9e3.1.2.2.2.2.2.0. p9iR.T.3.1.2.2.2.2.2.0. p
9l3.1.2.2.2.2.2.M. p9o3.1.2.2.2.2.2.1. p9rR.T.3.1.2.2.2.2.2.1. p
9u3.1.2.2.2.2.2.2. p9yR.T.3.1.2.2.2.2.2.2. p
9|3.1.2.2.2.2.2.3. p9R.T.3.1.2.2.2.2.2.3. p
:3.1.2.2.2.2.2.4. p:3.1.2.2.2.2.2.4.A. p	:	3.1.2.2.2.2.2.4.B. p	:
F.T.3.1.2.2.2.2.3.1. p
:R.T.3.1.2.2.2.2.2.4.B. p:3.1.2.2.2.2.3.1. p:F.T.3.1.2.2.2.3.0. p	:R.T.3.1.2.2.2.2.3.1. p
:3.1.2.2.2.3.0. p:3.1.2.2.2.3.0.A. p:"3.1.2.2.2.3.0.B. p:%R.T.3.1.2.2.2.3.0.B. p
:(3.1.2.2.2.3.M. p:+3.1.2.2.2.3.1. p:.R.T.3.1.2.2.2.3.1. p	:03.1.2.2.2.3.2. p:3R.T.3.1.2.2.2.3.2. p	:63.1.2.2.2.3.3. p:93.1.2.2.2.3.3.A. p:;R.T.3.1.2.2.2.3.3.A. p
:>3.1.2.2.2.3.4. p:B3.1.2.2.2.3.4.A. p:DR.T.3.1.2.2.2.3.4.A. p
:G3.1.2.2.2.3.5. p:K3.1.2.2.2.3.5.A. p:MR.T.3.1.2.2.2.3.5.A. p
:P3.1.2.2.2.3.6. p:T3.1.2.2.2.3.6.A. p:VR.T.3.1.2.2.2.3.6.A. p
:Y3.1.2.2.2.3.7. p:]3.1.2.2.2.3.7.A. p:_R.T.3.1.2.2.2.3.7.A. p
:b3.1.2.2.2.3.8. p:f3.1.2.2.2.3.8.A. p:hR.T.3.1.2.2.2.3.8.A. p
:k3.1.2.2.2.3.9. p:oR.T.3.1.2.2.2.3.9. p	:q3.1.2.2.2.3.10. p:tF.T.3.1.2.2.2.4.1 p:wR.T.3.1.2.2.2.3.10. p	:z3.1.2.2.2.4.1 p:}end_of_tape_theories p
;UNSPEC p;NONE p;ALL p;FINISHED p;EARLIEST p;
LATEST p;
CHECK p;ON p;OFF p;YES p;NO p;TRUE p;FALSE p;Next-question p;Repeat-frame p;next-frame p;3.2.0. p;!R.T.3.2.0. p;#3.2.M. p;&3.2.1. p;(3.2.1.A. p;*RETRIEVE INPUT p;,3.2.1.B. p;.RETRIEVE PACKETS p;03.2.1.C. p;33.2.1.D. p;5RETRIEVE TYPE p;73.2.1.E. p;:3.2.1.F. p;<RETRIEVE CATEGORY p;>3.2.1.G. p;ARETRIEVE SEQUENCE p;C3.2.1.H. p;FRETRIEVE CODES p;H3.2.1.I. p;J3.2.1.J. p;LERROR CATEGORY p;N3.2.1.K. p;QERROR_MAINFRAME p;S3.2.1.L. p;VERROR_DISKS p;X3.2.1.M. p;ZERROR_TAPES p;\3.2.1.N. p;_ERROR_UNIT_RECORD p;a3.2.1.O. p;d3.2.1.P. p;f3.2.1.Q. p;hERROR_CRASHES p;j3.2.1.R. p;lERROR_DISK_PACKS p;n3.2.1.S. p;qERROR_REEL_IDS p;s3.2.1.T. p;v3.2.1.U. p;x3.2.1.V. p;zRETRIEVE TIME FROM p	;|3.2.1.W. p;RETRIEVE TIME TO p<3.2.1.X. p<RETRIEVE STYLE p<3.2.1.Y. p<RETRIEVE FORMAT p<
3.2.1.Z. p<RETRIEVE MERGE p<3.2.1.B1. p<RETRIEVE OUTPUT p<3.2.1.C1. p<3.2.1.D1. p<R.T.3.2.1.D1. p<retdiaq1 p<retdiaq1at p<"retdiaq1af p<$retdiaq2 p<'retdiaq2at p<)retdiaq2af p<,retdiaq3 p<.retdiaq3at p<1retdiaq3af p<3retdiaq4 p<6retdiaq4at p<8retdiaq4af p<;retdiaq5 p<=retdiaq5at p<@retdiaq5af p<Bretdiaq6 p<Eretdiaq6at p<Gretdiaq6af p<Jretdiaq7 p<Lretdiaq7at p<Oretdiaq7af p<Qretdiaq8 p<Tretdiaq8at p<Vretdiaq8af p<Yretdiaq9 p<[retdiaq9at p<^retdiaq9af p<`retdiaq10 p<cretdiaq10at p<eretdiaq10af p<h3.2.1.1. p<jUNSPEC p<lNONE p<nALL p<pFINISHED p<qEARLIEST p<sLATEST p<uCHECK p<wON p<yOFF p<{YES p<|NO p<~TRUE p<FALSE p=Next-question p=Repeat-frame p=next-frame p=3.3.0. p=
3.3.0.A. p=
3.3.0.B.p=3.3.0.C.tp=R.T.3.3.0.Lp=3.3.M.Ep=3.3.1.Sp=3.3.1.A.p=computeEinput p=3.3.1.B.p=computeperiodap=3.3.1.C.p="computetimeLfromp=$computeetimentop='3.3.1.D.ap=*computeatypep=,3.3.1.E.pp=.compute.output p=03.3.1.F. p=3computereloadp=53.3.1.G.p=7comEdiaPq1 p=9com.dia.q1atp=<comEdiaMq1Faf p=>com.dia.q2p=AcomEdiaMq2Tat p=Ccom.dia.q2afp=FcomEdiaPq3 p=Hcom.dia.q3atp=Kcomqdiaq3afp=Mcomqdiatq4p=Pcomqdiafq4atp=Rcomqdiaq4afp=Ucomqdiatq5p=Wcomqdiafq5atp=Zcomqdiaq5afp=\3.3.1.1. p=UNSPECap=aNONEup=cALL p=dFINISHEDap=fEARLIESTap=hLATESTup=jCHECKp=lONap=nOFFup=oYES p=qNOap=rTRUEp=tFALSE p=uNext-question p=wRepeat-frame p=znext-frame p=|3.5.0.ap=R.T.3.5.0. p>3.5.1. p>3.5.1.A. p>3.5.1.B.p>3.5.1.C.tp>	3.5.1.D.up>3.5.1.E.p>
?0sum_rpt_q6_at p?4sum_rpt_q6_af p?7sum_rpt_q7 p?9sum_rpt_q7_at p?<sum_rpt_q7_af p?>sum_rpt_q8 p?Asum_rpt_q8_at p?Csum_rpt_q8_af p?F3.4.2.1. p?HUNSPEC p?JNONE p?LALL p?NFINISHED p?OEARLIEST p?QLATEST p?SCHECK p?UON p?WOFF p?YYES p?ZNO p?\TRUE p?]FALSE p?_Next-question p?aRepeat-frame p?cnext-frame p?frec_alg p?hR.T.rec_alg p?jrec_menu p?mt10_dsk_rec_alg p?ot10_dsk_rec_alg_a p?rt10_dsk_rec_alg_b p?ut10_dsk_rec_alg_c p?xt20_dsk_rec_alg p?{t20_dsk_rec_alg_a p?~t20_dsk_rec_alg_b p@t20_dsk_rec_alg_c p@t20_dsk_rec_alg_d p@

,>,>,>,>,>,>,>.B
+wZ@,@`B@+@,@+@x^@1@+@ "@+@+x@@/+@@!"b@@+@+!m+@!b@@+@+!e +@..<b@@+@"Z@5`@"1@M+ @ 1+@-  c@@+@%@B	0@+@++c@@+@(`B	0@+@+,>c@@+@/ B	1@+@/   M  @   % x @.B

&/B v  c@@+A#R`@  c@@+@] Px,Hs1B+Ad0B+Ay+@^:@ @ v! c@+@f
(}}+@f
&@vZ4@Ad! G@+Av!5b@@+@oPx+},>,I10B+@nZ@4@AU! G@@/B
  `B@@|Z@. (,>  {,>,>B,>B,>B,>B,PJ/BaB+A | @~ aB+A=Z@,>,>@,>},rf  @X@z  `B  `B
 @ @{  z,>,>B,>B,>B,>B,Q
/B`B+A   } } @ ~ B/B+Ay | @@Z@. (X@@/BR vZ. X@+@^ v,>@Z@,>,r( Z@4`A" VO@x,r(   @|  2@|+A"Z@/ X@@+A/B+Ay vR`@ }Z@3t+AA  @,>,>B,>B,>B,>B,Q
/B`B+A.   }  @  B+AyR`|  b@@+A2  c@@+A3  +A3  `B
  `B@@| Tx  |,>,>B,>B,>B,>B,PJ/BaB+A< | @~ `B+A@ "!  B +Am ~ @@XT@ ."  b@@+AE  c@@+AF +AHZ "Q"	  v@+A]! c@@+AQ
2}}+AZ
&@dvZ4@Ad!.G@+APx+},>,I10B+AXZ@5@AV/B2 }+Ay  +Am v .<! G@p ."!  c@p+AlZ[.Z3 +An    @+Ay! G@p Xx,>B,>B,E/BaB+Ay Xx,>B,>B,B/BaB+Ay! B@p  
 @`+@=  `@7w w4BB,>B,> ~,>,>u, } B@/B v  b@+B! B@/B
,^,^,^,^,^,^,^,~$$@6$`L`$$|6$|$$z6$z@@Cb(0 TTY:+++,>,>,>,>,>,>,>.E h .< .8^P5@B$ D{h/ 5@B$ D|h/ 5@B$6@p+B$  X@P  `D{! ~B@P  `D|  `D}^P1@+B*  @ @p   1+C&@@`@@x,>,K>/EaB+C'! b@P+B0! c@P+B1! G@P! b@P+B<! b@P+B<,>EZP,>,>E,>E,>E,>E,`:/EaB+B<! G@P! G@P! b@P+B>! G@P  b@P+BC  b@P+BD  b@P+BD  G@P! B@P^P5@BG  X@P! c@P+BI  !u+C
  c@P+BL  b@P+C  c@P+BO  b@P+C  c@P+BR  b@P+C7@P
+BU  c@P+C! b@P+C	 .0 ."! c@P+Ba  B@P  b@P+B^  c@P+B_  +B_  `D}  _`D~! b@P+B{! b@P+C,>EZP,>,>E,>E,>E,>E,>E,^./EaB+C!  G@PR`@  `D~  `D@@@,>EZP,>,>,>E,>E,Ze/E	aB+CXPP  _`D @X@@R`@Z`@,>E	,>,>E
,>,>E,>E,>E,^./E+CZ@. X@@,>E	,>,>E
,>,>E,>E,>E,^./E`B+C   Y+C,>,L%/EaB+C'! c@P+C  c@P+C
   -+C
   @p+C'! c@P+C! c@P+C  @ @p   m+C&  P,>  m,>,>E,>E,>E,Mw/E	`B+C   U @p B`+C',>,IC/EaB+C'R`  `D  `E@@,>E  ~,>,>E,>E,>E,>E,PJ/EaB+C$ X@P `B+C( "! Bp @`.E
+DaZP .6@ "v.@@. 1`+C*  c@P+C0  X@v+C0R`vZo/ ,>,>o,IS Bv! c@P+C6XRv+C9QRv! c@P+C9  b@PXVv^P  uQ PbE+@+C>   @+C?   +DaR`~  `E  `E@@~,>E
  },>,>E,>E,>E,>E,PJ/EaB+CH ~ @H aB+CUR`~  `E  `E@@~,>E
aB},>,>E,>E,>E,>E,PJ/EaB+CS!~,@H+`B+CW,"!,Bp/@`+DaDHDHD/EDg!c@+CpZw4@DZw4"D1"c@@+D	 Px  l,>  v,>,Ib/E
aB+Da!c@@+D)^@D#wQ(~bE+@+D+D)ZwD4"D1"D`+D(+D(+D(+D&+D'+D(+D(+D(+D(+D%+D(+D(D@+Da!9+DaE!5+DaD"+Dap!+Dabu+DaD!M+Da!Y+Da!1+Dap!Q+Da!-+Dag!c@+D<c@+D<^pQ\bE+@+D0+D6g.$Hc@+D5G@+D<B@+D<xg^$Q$dbE+@a@ +DN g! G@ g! c@+DO  c@+DO  2@+DO^  Q \bE+@+DD+DJ g.$ X  c@+DI  G@+DO  B@+DO g^ $Q$dbE+@`@ +DO  !
 @/E,^,^,^,^,^,^,^,~$$P6$P$$P6$P$$6$$$@6$@$$6$.$$~6$~$D$D.$@0@Cc0@Cd8(ACeCfA? ,>,>,>,> | .4 .2^1@+E  @ @P   1+E!@@H! c@+E   i+EI! b@+E  !m+EI! c@+E"!  c@+E"   m @P  !) @H+EJ! c@+E$! G@! b@+E+^  Q pbEX+@ |^  Q rbEX+@ |,>,K/EXaB+EB! B@@! B@@! c@@+E9 . ,>,>EY,>EY,>EY,>EY,Q
/EZaB+EB,>,L/EX+ED! c@@+E?,>,Kj/EXaB+EB . X@@+ED,>,K`/EX`B+ED   } @P BH+EJ! G@@! B@@! B@@! B@@! B@@   @P P`@7} }4BEP,>EZ,>,>H,>{, BP/E[ |  b@@+EU! b@@+EU,>,K`/EX @,^,^,^,^,~.( 
,>,>,>,>,>,>,>.GH jZ@  @ @  @ @x^@1@+Eg  @  @   1+F x@@! b@@+Ej  !m+G-! b@@+Em  !q+G-  b@@+Ep  c@@+EwZ@,>,_c`B+Ev   M  @  B/GH+G./GH+Ex5XEx   M+G- @
4`E~Z`2b+E~Z` B~Z`/ @+EZ` @~@@ ~ .Z@! c@@+F60rB+F 0oQ0`+FR`}  `GD  `GD@@~ . ,>  },>,>GI,>GI,>GI,>GI,PJ/GJ`B ~ `B+F "!  B x+G. ` @+F5@F $?D+F@."3b+F,>GJ,>~,>,rj  i  c@+F!,>GK,>GK,>,rf/GL+F"@ @"GE
&  nQ `3P+F1.2XR|  `GE  `GF P|  |,>,>GL,>GI,>GI,>GI,Q
/GM`B+F1   } ~ @ ~ B+F5Z`3`}+F3  "+F4   ~ @/GL+G. j  c@+G GF0`+F;  3`p+FA@@p>`p+F8 j^  Q ^bGG+@+F8+G) j7@6@~+Fb `0@+Fb $  @p>`p+FK j^  Q ^bGG+@+FK+G).$1d+FE p:  @p>`p+FT j^  Q ^bGG+@+FT+G)  @p>`p+FZ j^  Q ^bGG+@+FZ+G) $@@p>`p+F` j^  Q ^bGG+@+F`+G).$1d+FZ+G-  3`p+Fj@@p>`p+Fb j^  Q ^bGG+@+Fb+G) j 
@ &p/ &" .  @ &" 
.(1h+Fk@"p.Bp>`p+F{j^$Q$^bGG+@+F{"!G+G) j  b@+G  c@+G `+G
+`Z"Q"	+H~@+G@p>`p+G`j^HQB^bGG+@+G+G).$3d+GH@+GZ@p>`p+Gj^+Q@^bGG+@+G+G).$3d+G`jR`c@+G*,^@p>`p+G$,j^,^Q~^bGG+@+G$+G)6$@p>`p+G*j^Q^bGG+@+G*![( +,>,>,>,>,>.Hmj.4H.2^@5@G]Hjh/l5@G]Hkh/j5@G]6@P+G]X@@h`Hj!~B@@i`Hk`Hl^@1@+Gc@H@P^1+Gp@vH,>,K>/HmaB+H!c@@+Gh!u+Gx,>HnZ@,>,>Hn,>Ho,>Ho,>Ho,>Ho,^./HoaB+GqYI@P}!)@H+H!c@@+Gs>-+Gx,>,L%/HmaB+H!1c@@+Gy>@P+H@,>I1n,>,>Hp,>Ho,>Ho,Mw/Hp`B+HI,@]@PIBH+H,>,IC/Hm`B+H.Hq+HV@I"x.@@. 1`+HZp/ ,>,>p,IS Bw^@  wQ PbHl+@+H 6+H   +HU i,>  m,>  w,>,Ib/HqaB+HV^@  xQ |bHl+@+H+H(Zy 4"H>1"
,$I DH+I/I1."1`+I,>@,>,I1aB+I& D3@+I I&@H/I1+I,^H."X@HbB+@H/I1+I-6@x+I,>XH,>,I1aB+I&/I1+IaP+I+@@H<0.x0$0d+I+ H$ ./  @H,>  ,>,I1`B+I'/I1+I-/I1.01p+I  3@x+I-   I @H " I+I- "/I0,^,^,^,~<@ Z> +I?^ &Q&\bIB+@+I7+I8>+I? ^ (Q(dbIB+@aF +I= ",~  &!
 "Q"@ &3f~+IX@+I^0(00h=+IZ/(1(+I\1h/+I]\"+Ia /$D.&1f+IV x/Ib,~,>,> ~@ .@@. 1`+Id ~  c@+IlO@  XQ"	b$+  },>,>},>},Is/IraB7@ ",^,^,~,],>,>,>,>,>.J4 z ." .  .4 { .6Z,>,>,IS B@ Z/",>  `,>,IS(wQB@  c@H+J. . X@@[H4@JX@@ZH4@J	Q@@  b@H+J
@@X+J.R`|[P`J3,~`J3.P,@},PX@}Z`}\,>J4c"|,>,>J5&"{,>^"|,>,>J5,>J5,^./J6`B!~aB5RJ*4PJ#Z|4bJ . Bx,>},ISB@/Ib+J#,.6@+J#,x,$Q! D+J-0R+J&Z|."XB|+J( . @@+J*. 1`+J1R.+J.4RJ. x   ! @/J4 " !+J//J4 "/J4,^,^,^,^,^,~$$|6$| ACi8,>,>,>.Ib }Z@ K1`+J@,>  ,>,KaB+Jw6@+JS/K+J9,>}  ,>,KaB+Jw/K x4@J@ H &cF+J|0@+Jg  ,>} $,>,KaB+Jw $2D+JS/K. 1`+JH,>}  ,>,KaB+Jw  3@+JT/K+J|,>|  ~,>,K`B+JX/J4+J}  3@~+JZ/J4+J|  ,>{ $},>,K`B+J/K+J}7@}+Ja/K+J|/K. 1`+J[ {^. X@ {   @/J4+J@ }6@x+Jm,>  ,>,KaB+Jw/K+Jh H  c@+J|@@@ 2 x0$0d+J| @$ ./  @@,>  ,>,K`B+Jx/K+J}/K.21r+Jp  3@x+J} " I+J} "/Ib,^,^,^,~<H0 Z> +K^ &Q&\bK+@+K+K>+K ^ (Q(dbK+@aF +K
/K=aB+K9 @4BK/  AX@  `K<  `K< Bx  ,>,>K=,>J5,>J5,>J5,Q
/K=aB+K9  X@  `K<  `K< Px  ,>,>K=,>J5,>J5,>J5,Q
/K=aB+K9R`H "/K,^,^,^,~<$$6$(,>,> ~Z@5BKB  E*X@@+KG,>,_c/K_`B+KG B@   Y @@ " Y+K^[@5BKI  E*Q@@+KN,>,_c/K_`B+KN B@    @@ " +K^Z@5BKQ  E*X@@+KV,>,_c/K_`B+KV B@   Q @@ " Q+K^Z@5BKX  E*X@@+K],>,_c/K_`B+K] B@   E @@ " E+K^ ",^,^,~,>,Kj/KhaB,~ .",>,>Ki,>Ki,>Ki,>Ki,Q
/Kj`B ",~(,>,> ~,>,K/KhaB+LZ@4BKs,>,_KaB+L0BR`@/Kh[@4BKw,>,_KaB+L0BZ`@/KhZ@4BK|,>,_KaB+L0BR`@/KhZ@4BL,>,_KaB+L0BR`@/KhZ@4BL,>,_K`B+L/Kh+L0BR`@/Kh L4@L
  @,>,>Ki,>Ki,>Ki,>Ki,Q
/KjaB+L L0@_+L  @,>,>Ki,>Ki,>Ki,>Ki,Q
/KjaB+L+LR`@@@@! B@@! B@@,>,L/Kh ",^,^,~6$@6$@ R`@@@@
@@
!$cD,~ $BD,~[XPORT Temporary File]DSK:X.TMPDSK:TTY:,>,>,>,>,>,>,>.Mf H .0[@ @x .8 .6 .4 .2^1@+L3  @ @P   1+M@@HZX4@L6   @P+MR`~  `Ma  `Ma  pQ ` @  BX@Z`,>Mg,>@,>Mg,>Mh,>Mh,>Mh,`:/MiaB+LS,>Mi	b
,>,>Mj,XB ,>Mi,>E,,>Mj,XB,>Mk,>Mk,>,>Ml,>,>Ml <~,]B,>Mg,>,>,>Mh,>Mh,Ze:E,aB+LQ @! G@   @P+LR   U @P BH/Mm+M[,>@  L,>,>Mm,>Mh,>Mh,Mw/Mn`B+LY   Y+Lm H! b@@+L^  c@M+L^   Y+Lr,>x  U,>,>Mm,>Mh,>Mh,Mw/Mn`B+Ld   +Lm! b@@+Lh  c@V+Lh   +Lr,>`  ^,>,>Mm,>Mh,>Mh,Mw/Mn`B+Lo   Q @P BH+M! b@@+Lt  c@_+Lt   Q @P  "+MZN5@Lx Mb`Mb WX@N X @OZ`4@M! b@@+L{ZN4@L~! c@@+M  c@M+M,>Mn  `+M  c@M+M   Q @P    @H.Mo+M[ZN5@M,>Mn,>Mo+M,>Mn  N,>  },>,>Mh,>Mh,WZM5@M Mc`Mc VX@M V @M<Md`\+MZM4@Ma\+M   c@J+MZ_4@MZM0@+M,>Mn  ^+M   b@J+M,>Mn  L,>  {,>,>Mh,>Mh,W/MnZN5@M" Md`Me WX@N X @OZN4@M'a\+M) "@cBJ+M)Z`4BM)0@+M),>Mn  `+M*,>Mn  N,>  {,>,>Mh,>Mh,WZM5@M1 Me`Mf VX@M V @MZM4@M6a\+M8 "cBH+M8Z_4BM80@+M8,>Mn  ^+M9,>Mn  L,>  x,>,>Mh,>Mh,W  w,>  `,>,>Mm,>Mh,>Mh,Mw/MnaB+MX! b@@+MG  c@`+MG   U @P  " @H+M[,>Mg,>Mp  a,>,>Mh,>Mh,>Mp,`:/MiaB+MS,>Mg  a,>,>,>Mh,>Mh,Ze/MnaB+MX! G@@+MZ,>Mg  v,>,>,>Mh,>Mh,Ze/Mn`B+MZ   U @P BH+M[   @P A/Mo /Mf,^,^,^,^,^,^,^,~$$~6$~
V
M
S
J&@SJQH83@Cj0EXCkClCm(PxCnCo[}ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz*0123456789,>,>,>,>,>.N5@@x z,>,c`B+M 2(	 B.N6+N% Vx z,>,N:7@Cr+N,>N6,>N7,>N7,>N7  |,>,>N8,>N8,^.aB+N	 { @Cr Cr0@+N
 /N5+N0@+N Px "{,>,O{+N5@N Px  {,>,P /N6+N 2"q  ( @{+N`T+N /N9+N%/N9+N N2"N2G"N3G"N3G"N4G"N4G`N5 2`R7z {4BN+,>N9,>,>~,>, /N:  c@z+N- Vx,_K/N5 /N5,^,^,^,^,^,~@
@
@@@@@ACpCs.8 @ &"  &" NkdNl@
j.(1h+N; R`Cp[dNl $dNm  DCq XDCqZ`Cq "? BCr " BCr  "BB " &R` &fNm &fNn@@ " &R` &fNm &fNn@@ " &R` &fNm &fNn@@R`Z` " &R` &fNm &fNn@@ " &R` &fNm &fNn@@ " &R` &fNm &fNn@@ " &R` &fNm &fNn@@ " $R` $dNm $dNn@@,~Cp<$$Cp6$Cp$$6$* "cBCp+Nr  $"m+N}ZCp4BNt1b+Nu  $ 1+N},>O,>O,>O,>N8,>N8,>N8,>N8,^./N9aB+OZCp1B+N  $" D " ,~  $GDZCp."XBCp  CpXD Cq D "GBCp "GBCp ",~@CpCt01234567890123456789]>)*,>,>,>.Ov y,> y,>,P/N5aB+Os  c@Cp+O  "m+OO Cq`1"+O1b+O0B+OMR`|  `Ou  `Ov@@}R`}Z`}  X@| Cq @} CqX@}[CqQ@},>N6  |,>,>Ow  {,>  |,>,>N8,>N8,^.aB+O( z @Cr  2@Cr+O[Zy4@O3,>Ow  x,>  z,>,>N8,>N8,>N8,>N8,YS/N9aB+O2 {X@HaB+O[Zy. X@y,>N6  x,>,>Ox  w,>  y,>,>N8,>N8,^.aB+O< x @Cr Cr3Br+O@0B+OI  G@HZu4@OK,>Ow  u,>  w,>,>N8,>N8,>N8,>N8,YS/N9aB+OH xQ@H`B+OK  "q @@/Ox+Of  G@H/Ox+OP0B3By+OP  "q @@+Of,>Oy,>Oy,>Oz,>Oy  ~,>,>N8,>N8,^.aB+OW | @Cr Cr2Bv+OZZCp. X@Cp+O\4BO\  "q+Oe,>O,>Oy,>Oz,>N8,>N8,>N8,>N8,^./N9aB+OgZCp0@+Od   G@H+Og  " @@/N9 " !+Os CpX@H Cq @H  G@Cp  G@Cp  G@Cp  b@Cp+Oo  c@Cp+Or  G@Cp  G@Cp   @Cr/N9 "/Ov,^,^,^,~$$|6$|@Cu@CvpACpCwCx,>,>,P/N5aB,~ "XBCp ",~**,>,>ZCp@5DP "  3@Cr+P  3@Cr+P  3@Cr+PF Cr /&+P
+P:+P
+P!  c@Cp+P ~  "m+P1d+P ~   1+P,>O,>PH,>PI,>N8,>N8,>N8,>N8,^./N9aB+PZCp1@+P ~  " @ " 5+PG ~  @G@ ~ CpX@ Cq @  G@Cp   @Cr+P?  c@Cp+P$ ~  "m+P/1d+P' ~   1+P/,>O,>PH,>PI,>N8,>N8,>N8,>N8,^./N9aB+P2ZCp1@+P0 ~  " @ " ]+PG ~  G@ ~ZCp. X@@,>Cq,>PJ,r( B@  G@Cp  G@Cp   @Cr/N5+P?aB+P<  +P> ~  "m @  "q +PG,>CqZCp,>,r( BCq[CqZCp.Q@CqR`Cp  G@Cp  G@Cp/N5 ",^,^,~CpCyCz,>,>,>,>@ {"Q@1B+PR $1B+PR 2  4 %+P["Q0B1B_+PW1B^+PW 2  4"Y+P[7@@+PY 2  4 +P[ {5@P\ 2.Q+P{aD+Pc ."&",> "@,>,QZ  @ "Q"` B@+Pf,> "@,>,QZ `D+Ph +P{"Q0B_+PkR`@X@@+PkX@@ {3BQ+P{$Q1D+Pp,>{,>,>@+Pt0B+Pv,>{,> @ "Q"	,>,rj/Q+P{ @O+Py . { H.$3$+Pw 2`R+P}   @@`R7| |4BQ,>Q	,>,>,>, /Q	/Q ,^,^,^,^,~$$@6$@ ,>,>,>,>,>,>@ z QW1@+Q,>,_c`B+Q 0  /QX+QM/QX"QW0B1B^+Q+QZH H+Q'0B_+Q"ZH ."$QW0D+Q [H/+Q',>[H",>,r( /Q+Q'0B1B+Q&5BQ&ZH5BQ&@+Q' 0  8"Y+QM@4TQ4 65@Q+ 0  8 +QM@"QW1B+Q0 $ DQX3BQY+Q0 0"5+QMaD+Q4 d3BQY+Q4 0 +QM "cB{+Q="QW1B+Q9,>{,>,>+Q<,>{,>  "Q"	,>,rj/QaV+QH"QW1B+QD ."&",>Z.",>+QE,>,>,R`B+QH /Q+QM/QR`H@@H"QW1B+QL0B_+QMR`HZ`H 0`P7| |4BQS,>QZ,>,>,>, /Q	 ,^,^,^,^,^,^,~$$H6$H~,>,>,>,>,> } *E, (  .2 |[(4FQs Z
(.3f+QeZ5DQf ""-+RZ 
h$h,2$+Qj  
+Q` F Z2D+Qn[QD(+Qr.  Z
/
XL[
QLQF( "+R /2$+Qy."&"$".	b+Qx+Qy "!=+R (  .2 R( ( Z
(.2D+RZ(./XD( 
+Q` /XDZ`QB(+Q`,^,^,^,^,^,~ (E, [ 4BR Z
Z.3b+R
5JR ""-,~2"+R +R	3d+R " ,~ .3d+R " 1,~ .2D+R Z
.XD[QD+R"XDQBZS.2B+R"ZSZ.XB[QB+R#QF",~,>}/"+SN/R8@/R8,^,~
|!yRerroropeningRclosingSdeletinghrenaminghbackingRup>writingStoreadingRfromSauto-openingauto!closinginvalidSoperationSon>for,inputand4outputfor+output>to,>,>,>,>`}<@ |`R+SS4@SS0`+RU,>S,^/R8 <"R[1"+
,>S,^/R8+S
,>S,^+S
0@+S
[@ .<,>S,^Zp4BR| \x,^+R Z,>,^/R8 " 93B@6@@+S
,>S,>S,>S,>S,>S,>S,>S,>S,>S ,>,>S ,> <{,S[/S +S/R8,>S ,>S,>S,>S,>S,>S,>S,>@,>S,>@ <|,S[/S! ,^,^,^,^,~
|$@C{DC|C}C~CDDDDDDDDD	(E( 9p8Xerror parsing ,>,>,>S.,^,>~,^,>S ,>S,>S,>S,>S,>S/,>S,>y,>S,>x <|,S[/S/ },^,^,~D
E(`,>,>,>S,>S,>S,>S,>S,>S9,>S,>z,>S,>y <|,S[/S:(},^,^,~!P,>,>,>Sp,>S,>S,>S,>S,>SD,>S,>z,>S,>y<|,S[/S:W},^,^,~},>,>,>S,>S,>S,>S,>S,>SN,>S,>z,>S,>y<|,S[/S:T},^,^,~",>,>,>SV,>SW,>SW,>SW,>SX,>|T<~,S[	`	b/SX,^,^,~X0TTY:?%-~,>,>,>,>,>,>,>,>,>,>.T3@@xHBO2`T4+S|O"`@0b+S|R`~~`T1  `T2  oQ ` @~  BX@Z`! b@E2+Su  DX@E-! G@E1  `T2,>T4,>T5,>T5,B/T5`B+Su EG+T"O" 0+T  . w <"S|1"+
}E-@D
D`h @
normal completionfile was successfully created and openedincomplete amount of data readfirst read on concatenated file was successfulfirst read on a new page was successfulend-of-file has been reachedinvalid memory addressmemory element not on a fullword boundaryinvalid argument listinvalid concatenated file specificationinvalid punctuationinvalid descriptorinvalid deviceinvalid default file specificationinvalid directoryinvalid data typeinvalid record formatinvalid I/O optioninvalid lengthinvalid file nameinvalid new fileinvalid nodeinvalid file organizationinvalid promptinvalid recordinvalid requestinvalid related file specificationinvalid resultant file specificationinvalid file specificationinvalid file typeinvalid file versionI/O channel assignment errorfile is already closedconflicting options or attributesfile is corruptedfile already existsfile is lockeddynamic memory deallocation errordynamic memory allocation errorfile is currently in useI/O buffering errorI/O errorrequired parameter, option or attribute missingnetwork errorfile cannot be accessedfile cannot be backed upall I/O channels are in usefile cannot be closedconcatenated file specification not allowedfile cannot be createdfile cannot be deleteddirectory does not existfile does not existinsufficient dynamic memoryfile cannot be openedfile cannot be readfile cannot be renamedinsufficient spacesub-directory does not existrequested function not supportedfile cannot be writtenfile has not been closedexpiration date has not been reachedfile is not open for inputdevice is not onlinefile has not been openedfile is not open for outputfile is currently openprogram terminated due to previous errorprivileged operationfile protection denies accessmessage output errorrecord is lockednew file cannot be renamedold file cannot be renamedrecord was truncatedwildcard errorinvalid account attributeinvalid attributeinvalid datadisk/tape cannot be read/writtenfree storage chain is invalidinvalid protection attributeinvalid character pointerinvalid record numberinvalid sizeinvalid temporary file attributeI/O channel is currently in usehost operating system errornetwork node does not existinsufficient stack spaceunexpected operating system errorinvalid descriptor classtemporary file not permittedforeground jobs not permittedappend function not permittedsequenced files not permittedfield is misplaced or duplicatedinvalid syntaxinvalid IOBXPORT logic error detectedprogram terminated due to program requestend of string reachedstring was truncatednot a temporary stringinvalid characterinvalid descriptor classinvalid string descriptorinvalid descriptor data typeinvalid string lengthinvalid maximum string lengthinvalid pattern stringinvalid string pointerinvalid string requestinvalid source stringinvalid primary stringinvalid secondary stringinvalid target stringconflicting string function argumentsinsufficient spaceno string specifiedrequested function not supportedtemporary string not permittednull string not permittedinteger value out of rangestring is too longXPORT string logic error detected*** invalid XPORT completion code ***@ $"."DZ2D5DW [XH (hW (hW  H+W.&3fW+W ",~$$6$?,>,>,>,>,>,>,>.X<@@x w,>,_c`B+W% 2(% B.X=+X, w,>,_c`B+W) 2(1 B+X,ZX P}"X;0B+W- 2(!  (+Wc0B+WXZP . @~ .< .  @} ."&"$" ~ h h$2`+W= Px },>,>p,>,r(/X= Bx,rf }+WjR`|  `X;  `X<@@| ~ @x  |,>,>X=,>X>,>X>,>X>,PJ/X>aB+WG | @~ `B+WJ 2!+Wc Xx,>p,> |,>,>X>,>|,>{,>X?,rn Tx,>X?,>X>,>X>,>X>,Q
/X@`B+WU 2 } B{/X<+X, {X@P z @p/X>+X0B+WkZP[P/ZP/  h h"2`+W` P}+Wd   c@u+Wb \}+Wd 2(1  (9 @+X, } @x,>X,>PZP,>,r(/X= Bx,rfZP.|X@P+X0B_+X ZP. .< .  @}[PZP/  h$h&2d+W{ Px },>,>pZP,>,r(/X= Bx,rfXXP+XZP B~ .3b~+W "(.B~+W|R`| "bX; "bX<@@| ~ Bx "|,>,>X=,>X>,>X>,>X>,PJ/X>aB+X	 | D~ `B+X
 2! D+X, ZP.,>,>p",>,r(/X= Bx,> {,>,>X>,>|,>{,>X?,rn Tx,>X?,>X>,>X>,>X>,Q
/X@`B+XX2}XB{/X@+X,XXPz@pzX@P/XA/XAX]c@u+X,,>PZP/}/<,>,r(@+X*`X0(00h=+X*Y/&YF.3`|+X%/XAY2`R7wYw4BX3,>XB,>,>~,>t,>,>t,/XA@b@u+X5Vx,K/XA0/X<,^,^,^,^,^,^,^,~6$P$$|6$|8(|@0,>,>,>,>,>.Y!R`|5P`Y+`Y@@},>Y! |,>,>Y",>Y",>Y",>Y",PJ/Y#`B/}`B+XP,"E++YR`X`Y^`Y@@XY}(/"+~1@+YJ,>,>Y!,>Y",YB  & /YQ ~4FYO &"$(B }/ @ ,^,^,~
,>,>,>,>,>.Z*@>w,>,{c`B+Y[>4(%>+ZR`}[@`Z(`Z)@B@}2@X@~Z`~Z)+y."XBy,>Z+ "y,>,>Z- "x,>,>Z,,>Z,,>Z,,^./Z- +
7@u+Z2b{+Z% 6(M+Z,>Z+  y,>,>Z.  x,>,>Z,,>Z,,>Z,,^./Z-1B+Z 4(% 6(+Z t4BZ { @ 4/Z-+Z 4(A`T7y y4BZ!,>Z/,>,> Z*,>,>,>u, /Z*  @b@v+Z$ Px,K/Z/ /Z*,^,^,^,^,^,~$$}6$} v u0AEJ[}EK8EL0123456789abcdefABCDEF,>,>,>,>,>,>.Z. z { y0V+Z9  +Z:  zX@  `Zc  `Zc Zd @,>Z+,>  ~,>,>  ~,>,>Z,,>Ze,^.aB+ZE | @@ ZH5PZJ0@+ZH  (I+ZI  (/Z- +Z H@@P &" @
+Z\0f+ZP/&+ZR A ' /&O/("Zd&  P 
h6h,3v+ZZ/Z- "(M+Z_ P$(@. @P.*3j+ZN/Z- "/Z.,^,^,^,^,^,^,~$$6$
Z/[},>,>,>,>,>,>,>.[w@@x w,>,_c`B+Zn 6(% B.[w+[g w,>,_c`B+Zr 6(1 B+[gZ` \}"[u0B+Z~   b@u+Zy ZHh h"2`+[% \x,>`,>[xZH,>,>H,>[x,rn/[y+[Y0B+[ .0 .  @} .  &" $ ZH."&"$"3@+[3R`|  `[v  `[v@@| \x  |,>,>[y,>[z,>[z,>[z,PJ/[y`B | aB+[F \x },>,>,rf Rx,>[z,>[z,>[z,>[z,Q
/[{`B+[ 6 } B~/[{+[gX\H T@+[Y0B+[+ZH[H/  h h"2`+[# \}+['   c@u+[% P}+[' 6(1  (9+[G } @x,>`,>H,rf |X@H+[Y0B_+[Y .0 .  @}[HZH/  h"h$2b+[6 \x },>,>@,rfX\H+[YZH @~ .3`~+[;  (.@~+[7R`|  `[v  `[v@@| ~ @x  |,>,>[y,>[z,>[z,>[z,PJ/[yaB+[E | @~ `B+[H 6! @+[g Tx,>@",>,r(/[w Bx,> |,>,>[z,>|,>{,>[|,rn Rx,>[z,>[z,>[z,>[z,Q
/[{`B+[V\6}\B{/[w+[gX\H\z\@@\{X@H/[y/[{\ec@u+[f,>HZH/}/2,>,r(@+[d` 0 00`=+[d /& F.$3d|+[/[{ 6`V7w w4B[m,>[|,>,>~,>t,>,>t, /[}  @b@u+[p Xx,K/[{ /[w,^,^,^,^,^,^,^,~6$H$$|6$|8}( |0,> | /"+
z!y0comparison>error:\U,>,>,>\#,^,>},^,>|,^,>},^,>\#,>\$,>\$,>\$,>\%,>\%,>\&,>w,>\&,>v~<|,S[/\&|,^,^,~EM8E(perror>copying,>,>,>\4,^,>},^,>\#,>\$,>\$,>\$,>\%,>\4,>\&,>x,>\&,>w^<|,S[/\5|,^,^,~ENE(`error>appending`to,>,>,>\E,^,>},^,>\F,^,>},^,>\#,>\$,>\$,>\$,>\%,>\F,>\&,>w,>\&,>v`<|,S[/\& |,^,^,~EOEPE(error4scanning to{find , spanning , stopping at ,>,>,>\,^,>},^ | /"+
 +]
Z@Z@2v+] @x,>,>]?,>]?,>]>,>]>,PJ/]@`B+]+] @x,>,>]?,>]@,>]>,>]>,PJ/]@`B+]7 4.]<+]0  c@z+]Z`/+]   c@z+]Z`/ &"7@ Vx,>@,>`,>,r(/]A Bx,rf  c@y+]0,>`/2,>,r( @+].` 0 00`=+]. /& F.$3d+])/]< 4  @b@y+]3 Px,_K`T+]5! B@` T`/]A /]<,^,^,^,^,^,^,~$$6$$$`6$`0(,>,>,>,>,>,>,>,>,>.^ _W @xO2@x+]K P+]{R`~  `^	  `^
@@,>^
  ~,>,>^
,>^J/^`B+]U  E++^R`H  `^
  ^`^@@H6@x+]Z 8 	+]{@"x@+]h . w,>,_c`B+]a 8(%+]e /"Zp h$h&3d+]f 8(Q/^+]{Zp./^. 3`+]\,>,>,>^
,>^J/^o^+]{H@"x@+]yr.wZX,>,>X,>~,rf~ BxZX,>,r(^B}/^.3`+]r 8"x@+] .,>w, K/^.3`+]}`X+^!B@HXH/^,^,^,^,^,^,^,^,^,^,~$$~6$~$$H6$H 0,>^,>,>^,>^,>^,Ze/^,~`E((,>^,>,>^,>^,>^,W/^,~E('[invalid string],>,@c/^,aB+^(,>^,>^,,>^-,>^,>^,W,>^,>|,>^-,>^,>^,W,>^,>^,,>^-,>^,>^,W/^-+^+,>^,>^.,>^-,>^,>^,W/^,~EWE(PEX,>,>,>,>,>,>,>.F@u,>,c`B+^7~(%@+^< 3c@t+^=vC0@1@+^=~(%@ 6(.>F+>0u,>,c`B+^As(+TZ@ @}6@}+^E F( @~6(I+^0u4R^XRx,^caB+^2T+^Nc@s+^L{c@s+^N(1@~6(5+0b@s+^XC0@^+^S(%@~ 6(E+ 0`@C1@+^V1@3R+^X b(1 @~ 6(+0Q."  c@s+^bZP[P/ZP D /  @},>},>~,r( /G+^eZP @   @} }.0 P| D /"+
/_caB+_^ _`0@^+_]  X@  `_`  `_a Px  ,>,>_b,>_b,>_b,>_b,Q
/c+`^4"/a,^,^,~6$@$$6$(05DeZ"(=,~"`0B+l"`4b(i1b+q1"^+k1b+(q,"(,~5Bp"`0B1B^+do+p,,~,"(,>@ {,>,c`B+`
,>(),.`5+`',{,>,c`B+` "(-b+`'O2B{+`ZHZ@2B+`ZH,>,>HZ@,>,>@,>y,r}/`6+`'.$ ."ZHZ@2&+`ZH,>,>ZH,>,>,>`6,r}/`65b`&+`%Z@,>,>Z@,>,>,>`6,r}/`65"`&O+`'Za@5@`(7|,|4B`.,>`7,>,>,>`7,>,>x, /`8Z"@bBz+`2+Rx,K,>{,K/`5/`8,,^,^,^,^,~(EY0,equalto,>,>,>,>,>@ {,>,ac`B+`A,4(),.`v+`P {,>,@c`B+`E 4(-,+`PO2@{+`IZHZ@2@+`PZH,>,>HZ@,>,>@,>y,r}@5B`Neq /``+`P@aT5T`R7{ |4B`W,>``,>,>,>`a,>,>x, /`a,@b@y+`[ Rx,K,>z,K/`{/`bZ,^,^,^,^,^,~(EZ04greaterthan,>,>,>,>@7{,>,ac`B+`k,>(),.a+a,{,>,ac`B+`o+(- .a+aO2B{+`sZHZ@2B+`wZH,>,>HZ@,>,>@,>y+`~.$ ."ZHZ@2&+aZH,>,>ZH,>,>,>a,r}@4ba+aZ@,>,>Z@,>,>,>a,r}@4"a $ a@5@a7y z4Ba
,qM[FEjZ`,>,qM7@ & FEh4FbSX(E~[0f	 &	*(E~,qM[FEkZFEk,qM FEl^0O@G
	b
+  BE^0J+b:G#O@G#O@EyO@Ex "7@E~1J BFU,^,o9O@Em	b
,b%QBEh Q( BEg\",	b7+b!@b!$Lu
+b! E^!$YR (	h m@+b!"m$"j0(D~A$pA&G,q& BEj6@E~,d-7@G#+b)!"K8 BE~,d-+b@ (&".$)D}=hb&[,~7@E^+b@
0
6+b@O@,jL4pb-4Nb,4Nb@1P8Jb, m7 ,im+b74pb@1P+b4
6m0,jh+b1O@G(ZE^^0 PEm+b: E^,im+b@O@G%0P,k+!$cDElO@G#7`@@EnZE^Z"/,~
6m0,jh5pb>OmPEm,~,l`JxdDGEe,qM[FEeZFEf,qM[FEcZFEf,qMZFEgZ^G*:@Em+bS6@G#6@G*+bS+b`2^G`O@G'@@G)@@G+6@Ec,Ec6@G*+be,d<5BbS,d,d
6@Ef,Ef4pcO@G)"m5Bc!$}[bpd0F@*dbm 
bp+0ebt@mbv@}bvA%bvA=bvA-bvd "bBEf6 G'+c+bw:@G'+c "bBEf+b Fe`b!+d7`Fm6`Fm+d7`Fn6`Fn+d7`Fl6`Fl+d,Ee+c
4Jc
 EfaBaB+c7 G'+dO@G):G' "bBEf+c	 FebBm+dLFo7@6 Fo+d,Ed,e%4,c5pbg6`Fq+h
6@G),~6@E~+bS6@G*+bS6@G#,~+bS,d&@@En 0+be m*"G
O@G(,~,m*"Fp@@G(+bv,l` ^G
,qMd&/&(dFEbZJEa[.&(GFEa,qMkFEiEl,l`2^GEm5pd,d<:@G
?@G
+c@Ei,c.+c1P+c&1P ,d&4pc+d,qd,>G*@@G*,>En,>En@@En@@En,>EmZ^Em,>G
G
 
Eo@@Eo,cq+ca JG
 LEo,qM5Fc?\&	f+cbafp+cb6@E~+cb FEi7 G*,eO m*"Ff@@Fg m*"FpO@Fl m*"Fo,d',ds7@G
+c[:@G
>G
 *80c[OpEm@@En,jL Ei`bp+m	h"*bcN2N*bcN5"cT7@G
1P+cQ+cV6@G
0P+cT,jL3NG
+cV4pcI,j|+cTO@4pcI0P1P 00P+d,eX+cV Em+cV5Jca G
6 x4Nca m
,luaB+c`,,p4,p-,hg^NHtS:O@@G+@@G*6x DG.Dx7`@@El^En6@El7`7+cz6` DEl2PmOpEm4Bd[,qM FE^.&Q& FE,qM[7@7m
Q( HE`Z7@7m
Q( HE`,qMZ7@7m
Q(\HE,qM2Fm FEb7`Em@@En@@FqO@G
,qk6 G*,eO7 G*,eS@@Fp@@G,qn,~^0 PEm7@Eh7@E~+ln,l-,~
&m
2	b+d-"l>KNmm-"l>M6}m-"l>M6Mm7m m ,>d,lu ,^aD+lS,pC ,o{6@G7@G+d% "m!,pC G7$G "G, ",pL+lS,dX5"d8 "7@E~ BFU7@E~ PFU7 \06@FR,l- "E~ $	,e%7BFU"8v BF7@EO@E7BESEh BE7BE~+d8	b`b O@FT? FU+d:\"4pd77 G*+d81P+k. .E~OdG%-"lKUMm# .E~OdG%-"lKi6Mm&,l`7BEo,~1B+m(,qU4"ln
8+ ,"Eou$Ey&E{,l=+dV,l-;E{KBE}oEz!"bBEq!$>9 DE{7"Ex "1b(B BE~SEyX"E{6 Ey+dMd"6@G#l"	b G
2(+d.EoO@-"lKe^Mm-,q[-Fp,ds+dZO@Fp,jc,iH1P+d4Nd`6@Fc+gk,h
1P+e1P+e6`Fq0P7+e
6@Fp7FG*7+dk1P+dz1P+dZ7@Fc,h,&fm0Fp,~@@Fc+m1*$FpO@Fl+m*$Fo6@Ed6@7,Ed!"GBFeGBFe,~,eX+g},j^7+d5"e$`b+e%7@Fp:Fp+e%LG4Ngm5Bgl6@Fc+gn,NFc!"BBFe+dZ,iH,j6@Fd+goYG5NFd+e$6@Fq+h:Fq,h<6@Fp7 G* &e,,0d
}m7,>7	Fq,eO,^,~FFed&DGFEFed&GFF(w0hF("`S`F	3FmFX!"BBFXBBFX,~,q],jL4Nqj:Fp:x,f#7+ec5bg|h.k``n`+m;h.k`,>(N,f#+m<,^!"0cC0+g{Q,@@G& Fp1b+eiZ00"Fc0bFo7+ei2"Ea2bEa+g{ 0Z`daN7 8`d Q. NG@@G m>*"G 0`d+m>4,f`dQ"6@G&+f1P+e|6 G*+ey4pey Fp0F+ey0P,k++e|`d@+hab5Bf5"fw4Nh+f4Bh7 G*+f ,jh,k+*0H+f@@ElO@G&5bf,jL4Nf 0,im+f/0 .+f5"h " )B!( cI0+f3Nm@+m@3NmA+mB0BW+f,>  0,im+f,^/0\.+f4Nf1P+f7 G*0P+f,jL mC,im+g~ ./.f A.+f,^2NmC5Ng .!$ bE0!. 0h"`ib`5Bf+fw,+fw+g# "]<s08 * E^,im+mD ,E 
4"f* mE,im+mF6 5Jf, 
 ,l~ * %0 */*+qi ",~O@,~,j"+fq,j0+fq,j+fq mH*"F~,dX 06@Eg1Ll~7+mIZ[06 G*7@+f96@Ei+f:+h,e% mL*"Fp+qi,j6 Fn3NFn+f>6 G*+mL NFn Fp7 G*0H+fA NFa0P+qi,j3.Fn+h
,~	07@O@,.,~,jLd4Nf[0P+f[,>,jD,^+&!$qbFG*dfL6>"$S`X$G,p-+fp,qr+fp , "mX1L "mZ,pC 
E^1L 
mE4Jfo .+fm,pI=nfm "m[,pC .,pK (,p4*jfk,p-=lff,lf+lV[06D 0`d `d +fw4Bfw4.h2n+h,~ 0 0P
`j(+m\d,6@Eg1Ll~+f|+mbad`l$	(mdg1(:0hd&`af`l&	"3N+g6G*3Bmg#nO@1(b+Fp7PG*0H+g#d$0$Fc0dFo+g/$ 0 PEmR0>Fp,~C
,kyCNMhrE5|RIv::KJu{RKK+zKK\KO%0KbN@"-LYt}[83]>~i7j6m:7FmFmFl
Fe>Fe2Fe0FeFoEo}f\FnG+G
>Fe2Fe0FeG
Fe@Fe$FeEoExEyFl4FeFoh"h"h"Eg`jfDugdf;EgfAIaAI$A*U00A"Y,I*
S;H6g^NHtiF@KZ-`_ aJ,j<M'=G>vJ7

C&)9-"lAIuml-"lAo5mo-"l>]5mq-"lAI5ms-"lAIEmv[`-"lEGmx,iC-"lEIm{[`-"lEem~aN[`-"lESBUnaN[`-"lESB=n .Fc $-"lKg%n-"l>]N5n
-"lAk/n
-"lACn5"h-"lAkO5n-"lACO5nn0-"lAkn6@Ei+g#F0-"lAINMnF0-"lA]6,~6BFcBFV6BFcBFVFd6@DFW6BFdBFWn1!"bBFe*$FPFeFeBDFXGBFXGDFX!$|Fl2BmBG$+BG$O@G4n1*"G,q#*BG000p+h3+hR,jL4Ni3+iB,im+i1../.i40.+hA7BG$+i,=BG$[G&$/7..RG6 G$m/.S.,>,iZx,^P+i
,i G$+@%n?+i
7`G$?8G:8G,i  "of BG2.n@+j@-"l>I?nA G$".G$".G$"t G$$.G$$.G$$.G$$.G/n9+q&0P,~,j"4.i+0.
+i- NG0P+i#,j"0.+i-4.i+ NG0P+i#,j"0.+i-4.i+ NG7"G "$"6 G.G$"6 G.G $)w'"Q@ +qi-"l>]%nC-"l>]CnG-"l>]:%nJ-"l>]B5nM-"l>IenR-"l>IUnU-"l>kmnW-"l>S3n[-"l>kun^-"l>[%nb-"l>IRmndo%i9i#.,rMJLH<g&\RgVtH<[>tH<iV.9UvX9M-0[:CC[HUVtPUVgCV>\zgI6_%xR]?4[1I[1sI9i>$ i>m|YY>=@]>}`[&%j3YVt:I&ui9%i7~-i4,jc@nG'0P+iFl+iJO@00 +iL+iO,jc@nG'0P+iLS.  $,jcO@G'+ikO@0P+iYO@G',jc0P+iR(D(Nl+iN000p+iV($l(N..Gh+iN@@G&,j96@O@G'O@)D+ik "p4 BG " ng nh,jf,jd6@Eo+ib0P+i``fpB+ib,j^+if`fp`/0`hpP.0,jcO@G'+i]0P+ik/0`hpP,jcO@G'afp+ikB+ii7@G' $ DG+j@ +q>,jc,jf@n000p+it`np+j
(Npnh,jc+ip,j^+i|000p1+j
,jd0$G`4Bni$"
bni,jc0P+j@,jc,j^+nk000p+j
 $Gh(B.`b+j
X+i}0P+j,jc,jd000p+j
pnm,jc,"p6BG+j@-"l>mnn@G`n,~7@G'O@SU@BG,~,jc,j7@(N6"p$+BG+j@,jc2"1P,"1P,jc .0000+j$...Gh,jc+j"p&,BG1P((N1P%(N1P!(N0P!1P++j0P(1P%7jug,jc+j@,jc1P+j0,jA1P+j6000p+j)$...Gh,jc+j%1P,jc0"p;,BG0"1P%:"t1P&,ns1P#,ns$0b,jc+j?,jc,jA,>7*000p+j7(N..Gh$*.*Gh,jc+j21P1,^1P+j)0"p;+BG/"1P%"1P&0"	1P#!"{X"p,q>+jx/"p 0,qn,~ 5"jz-"lAk=nv-"lAC=nx -"lAS=nz,>6@El+n~6@En^En@@En6BEn+6`^0-"k+k+k+k
-"k-"k+k+k+k
+k-"k+k+k+k	+kQ0-"k-"k+k+k
Q0+k-"k+k+k1P+k
+k!",k.7@E~^0+k\PEn_`+k-"k6@El+k+k BEn PEm,^,~6@El+o,k67`Eo+k"4pk!2PEo+,k63PEo+4pk!,k+ 0@@Eo4p1P+1P+0P1P+k*6 G(+7 G*0P7+o0P+,k65pk*+ PEl5Pqj 0*El,~6@G*+k27 +k16@G#,~6@E~+o6@Ek+Ek
8+ 7  "
",~,k91P6`Eo7@0,~,kE40qj4Pk90P1P?+k91Pm,~6@Ej+Ej
(1P00P1P07@G(6@G#6`G%,~0Pap+kW\`FT,qk "E~ $F &F	,l=+l; " BF	 "FR BF F	QX$F
4Bk`ab*$F $F
ab DF	,qn,ky+kx60FRap`6@G)+kk,kk80kx,> FS1"+kh FRaB+o ",kk80kx=bki,^>`FS+ku7@FR+kx:FT 0G4Pkq,ky+kx70FT+kx0p@@+ks
` +kx FS PFS FR000p+o@@G),~,^^0,~,qk7`G#+l o
SF
 o
	b+l$" BFS o BFR+l
F+l!0F	+BF	,$	dadig $@F	+l F(BrQ" E^7DF	 ad  (	h  ( $5Hl,>( "F B(
6`FT+l!(bHFed+l5Dl[F
0D8vg $;2SDF
+ld$6@Ei,l*7+l 6`G#,l*+l@@G#@@G#>(+l  .E~O@G%-"lKSeo^0,qn,~[F0BK8+l(QBF
 "LuQBF[F
7@ZEhPEh BF
@@F	Z`FT+k{ .E~OdG%-"lKS}o0D	1D
+qi<dqi9qj7@E~,~6@FR7`G#+l7O@G#7@FR+l4,ky+l7@b@f + +l7 oSF
 o
	b+@@E~@@G% FU@@FU@@FR+o*"FT,~7.E~OdG%-"lKS^Mo (G+p`7Z,> ,lu+lS7Z (p4+lG7Z (p;+lG7Z (p;,> ,luaB+lS,pK , +lS7Z,> Q,luaB+lS,pK4.lR[,p;,pKZ,oB6@G%,l7^"7`G*7@E~7 BEm,p-,p- Em7@Ei@@Eo G
27@G#7 G(^0+li,>
66@FR5po2Pm^0@@El@@En@@En@@Eo2Pm^0 PEm,^,~,l`,l-@@G#@@G#@@G(6@Ek+Ek,qU+lt	`	b,~7`
&o	`,qkZ[`6@Q"8wQ$6@EiQ$ ~Z&,o B~,>6@Ei,l-,^,qn,~-g+-g8-gF-gS[`E^,eVpgR-um,d5pb`+bS6
Fel0FopFc\<hFclpFgm@Fl2B+cT+cONo option ]>um
m?
?SCNPDL PDL phase error
EqualasignamissingFileswitchesiillegal inoutputffileOutputoswitchillegalniniinputcfileExcess@argumentsustartingewithl"Kbe25m*Wildcard illegal in /RUN specificationl0Fc NFf BFf+ekFf/BEFORE and /SINCE don't overlap/ABEFORE and /ASINCE don't overlapkpFj`FVh.k`+g{,^5bg|+g{qhG[ .8+f]>tP!.+fC2` .+fUf 4"f&O@+f&~-g*5bqj4*f,4Jf- +f*l0Fq 0`f+f5,Eg+f:+f5nFc6@Ei+fA+hCan't write tmpfileIncorrect tmpfile argument format% I can't help you, please read the manualSwitches are:Standard ones:
	Zanen1B+fz4Bfz0"	+h "(B?X+fz`j+f|,Eg+g#+f|0[0BaB8+gZ`nh`B8+g+g,jh0P,k++eiDouble file name illegalDevice wildcard illegalNull device illegalDouble device illegalDouble extension illegalComma required in directoryDouble directory illegalRight bracket required in directoryImproper project numberImproper programmer numberSFD depth greater thanNull SFD illegalUnknown switchAmbiguous switchNo switch specifiedUnknown switch valueAmbiguous switch valueUnknown default for switchDouble switch illegalNo modifier allowed on switchSwitch value too largeSwitch value negativeSwitch value required onLength values inconsistent; specify min:maxParenthesis nesting too deepUnmatched open parenthesisl`FYq`GRGX.+h>RG+hOMnemonic date/time switch not implemented%x:D(afQ+i3"G+ 2bG_XDate/time out of rangeDate/time must be in the futureDate/time must be in the pastNegative number in date/timeNot known whether past or future in date/timeField too large in date/timeField zero in date/timeUnrecognized month in date/timeIllegal year format in date/timeUnrecognized name in date/timeMissing day in date/timeValue missing in date/timeHH0
$ "dni,jc+it0P+j
,jc+jB
Illegal character or field too large in /VERSIONB n5JHGGHGGUnknown guide wordAmbiguous guide wordIncorrectly formatted guide word El@@El1P 0+k El@@El1P^0+k^0+7@FT,~Z"+k2@@En+kA,^>,~6@O@G),~xFHFIndirect file LOOKUP errorCan't OPEN indirect devicej FRWildcard illegal in indirect specification,j|+lg

.KJOB
. &,>,>,>[A"?1B6@G++o#
8+5O@G+,p-,pL,o1,^abS``H,p4,^`FaH@+o-g",pLZ,p;",pL,pKZx`H,pC,^A(X,~\"	b "ab`l"`fo9(B}DG+[`GG+d"`Bl7@l,~c*G,,~  ,p4,pH  [ 1DYR5bpO,p4 ",pLR ,p4 " +oK 7B +oD,p4,pH  ,p4R !$bD bD 4FoJ ",pL ,p4 " l" 7B +pP`h+oO`b+p0 ([/",>Q(} "-,pL  2BpR4"pS6 x+pT,p8*HoY6 x:7@ +oY,pI  ,p4+oU,^x+p3!`)"w,>!`,o^,pI,^iB+pG  & ")B5Boc=fo` ")B."`d ",pL=fob,~,q,> ,oj,pH,^+oq	b,q[&"  " $,ow&( "-pU,pC "  &"2"+p;	b	&p[  $,ow,pH &"j0 ,ow,pH &"t $4"p;0b+p;*,pL "+pL0"+p!${Pp
TXzp"p\6@,p;"p\4Bp>&"pLZ,p; ",pL$p]4DpN ",pL +p;`B?+p+ p]+p*4Bp+ p^U$*Dp) p^bB+p+&" 7!(+,p;[+pL,> ",pL ",pL,^,~,> "-,pL,^4"p,p8 ".+pL 4DpN ")B.",pL+p5,>[,p;,pI,^Z7p` &5"p>  ",pL &#`QDx6@,p>[x."0b."+pLQ"A`aB,~,>x4Bp/,pL+pE "+pL "+pL "+pL "+pL "aB?,~6@G,+G,
",~,p0+o?[1D7@ ,~+oO,p4+oU  ,oZ+oU-Jan-Feb-Mar-Apr-May-Jun-Jul-Aug-Sep-Oct-Nov-Decmn@0$$B
?X,p4+p3,q`7N!.Lu N 
!,>9	laLd*@ 
q
`j@l
+@ ,`j@!,an+pk`Jl
.q
nq6NL5Nqj+LN6Nh`N,~aN.q^ N7@+q@@ S* X* **  N  *!,}X, 7N(+q N0L(5Nqj.**lp} .  N[
 ,!. bNGL[
0j
7.
 .(N|0l N0j
7
 .0l3Nq7 N+qi	n
$,>4"q [."~L&":X(D&$:XG&&&Z(H(B.$"2."n `D+q&$27@aDg &/"V$":5Fq1(+q>!$z3(q7+q."*dq/q6.*xd"%q=),^,~ q=	b "5Bq6	b		d,q[,>&$:0d~+q3&&.q6 *0& * .$&$0F *.(} $$6.^$m4dq2&$2/0F1.0hO@,^ $)w'q=Q,~-<KZjy'6L\X5"qY,q],> ,qQ  
,^O@: `f+qG(FFdA4Fqi+qJF4FqiA5FqJ :*bqCZ4Lqi ,~<$qN7 &:,~>  F:,~ "!$pbFG(D}5DqR,~	b
"`	b+qZ`b;xO@,~O@,~ ",~*
xQ*x,qj>+qi*
xQ*x,>,qj>+qh*
xQ*x,>,>,qj>~+qh*
xQ*x,>,>,>,qj>~,^,^,^,^:x,~-j(,>,>,>*~,> ~,~,^,^,^,^*x,~ p,>,>,>,>( QDx@,>,>,>,>7r!&>9Z(
+q!$@f@e$+r0D	1D
+q0d+rl$+r@+r
`@+r	
` +r?$x+r` `B+r!"
"+r-"rIOE I/O error reading help file-"rNHF No .HLP file on SYS:
&r#\$	d $ad`l$``dl$@`d 
&r#`d 
&ad@+r
&
&r$
&r'"/r',^ZB([	b+ ,^,^,^,~Q3qwqxqxr
 ,>,r9/r-.$r-,>,>,rC/r.,~0,>~,>,r@/r3.,>,>,rC/r3,~,>,r9/r9,>,>~,r9/r9/x/r9,~(r? $&Z$$r?/$&/<,~0<Z $&$<,~@ hrK $&,> &xX8$ &/frK/rL,~0<7d~+rP  3H+rQ=drN@,~,>,>.re7@}+ra 
|/
}7 +rb } B | Bx x2B+r^,>},>,>|,>|,>re,r}/rf4Br`<,rb  Bx+rX x+rc |+rc@/re,^,^,~( ~  +riH=$rh,~  ~ +rmF=$rl,~,> .$Q.r| &,>~  4hrz 
2j 
/ 
+rwF=*rv.r|*drr4hrz xF=hry/r|,^,~ ,>.s |2D}+s4ds | B } Bx
x2H+s=ds@+s } 
3, 
4ls | B } Bx ~ 
> > 
x2H+s=ls
@+sOh(h*2( "/s,^,~