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 @ @ ?x gCYKb)b <Kb` INX Q F: z3~ 'B?{r E@@ 'J
'r + *> ` 2Es B@)9 B?x H 0 JAN FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DEC PM 2 1 p H E INX gB, @Kb( \ INX ) , 0 GJ ! # # `p h Now type: SAVE SPRINS<cr> F 4 p 4 % G- G3 , & ( ' ' ( 0 ) % F G- G[ p HSPEAR.MSG `p 4 B @p ~A '2 G- p T p V ] g p D p E p a i k `p X B p
p
p `p
Hf
`p
s B p
r p
r p p 0 @p p h p k p m p q p
s p u p w p w J K P L L Q ! D J X h M [ h l k p p p 8 p : p < p > p @ p A p
D p G p J p
L p U p X `p ] B A ? ? C F C D G p p p p p p K Q 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@ $ TEp 0 ap $1TG$6 0 $ b ' $ T`` $ bp '
$ T`` $ c@! ' $ T`` % $ d& ' $ T`` $ * $ d`+ ' $ T`` ) / $ e00 ' $ T`` . 4 $ f 5 ' $ T`` 3 p ' p ' @p @p U 5 E* @p E* /@p p ' p ') p '2 p '3 p '4 '6 p ': p ': p '; p '; (H (W @)? R$ '/ '/ '2 2@'Q 2@E@ rBKf / . G-rBQE 2@Q rBr, T2@ac , b, Hg $2@. $
$2@Pu ! S<cr>
2@X5 @
2@Wh C2@r, G^ G- Y d2@Ca d G- G- Y d2@Io G-
. / 2@G= E[ g2@F 2@J[N8 2@PA f^2@r, 2@P+ Y G0 G0 GH GG2@_( f\ Cz2@r7 G_ G_ P 2@^l , G_ G_ p p p p p p p p DSK:SPEAR.MSG B E* P f P z P { @ 2@MP `p B E* P Cn " P u " P v " @ " G0 2@MV " G- GH GG G0 G. @p G^ # " G0 2@[ G1 G0 G^ G0 " G02@Q 2 G0 2@_( (m Cz2@r7 P 2@^l , E M i )^ &*xpG )` de)^T_M$a D K S i )^ &*xpM )b de)^T_M$a J Q i i )^ &*yPS )e de)^T_M$a P X i i M )^ &* &!z0ZTbU)g fU)^T` % V @ c - G M W i
o ' ? { u )^ &* &, &- &/ &0 )i )j )l )m )o{ iTb )p bu)^T_-$M ] @ m i i )^ &*}o )r de)^T_M$a l s i i )^ &*}u )t de)^T_M$a r y i < &* )^}{ )w de)^T_M$a x i 7 <` 8 >* W >A Y 7* <2 > f n 7o :j 7A =| } : J <I :% = + 8K a @ =e W >o ! n @ 8b <w J
:< 3 >X 3 ) 7X < :S 8 B a 8 =% O ) =N 84 &* )y )z )| )} ) * * * * * * * * *
* * * * * * * * * * * * * *! *# *$ *& *' *) ** *, *- */ *0 *2 *3 *5 *6 *8 *9 *; *< *> *? *A *B *D *E *G *H *J *K *M *N *P *Q0<U*h d Ta ~ s i W m / E [ q 3 I _ u H W ] 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 /z 0 0` 0v 1. 1= 1L 1[ 1 2D 2S 2b 2x 3 3% 3; 3Q 3g 3v 4
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 +| +~ , , , , , ,
,
, , , , , , , , , , ,"}'UDP c@ UE ? , i 3 &* ,F}- ,G de,FT M$a * 2 i 9 &* ,FX3 ,I de,FT M$a 0 8 i ? &* ,F89 ,K de,FT M$a 6 > i E &* ,F? ,M de,FT M$a < D i W &* ,FxE ,O de,FT M$a B J W i - ,F &* &!XL ,Q fU,FT` % H S i ] - ] p K , &* ,F &, &- &/ &0 &2HWTb ,S bu,FT -$M O @ \ W c &* ,Fx] ,T de,FT M$a Z b W p &* ,FXc ,V de,FT M$a ` h p W ] ,F &* &! 8j ,Y fU,FT` % f o W v &* ,F (p ,Z de,FT*M$a m u W | &* ,F v ,\ de,FT+M$a s { W &* ,F h| ,^ de,FT,M$a y W &* ,F H ,` de,FT-M$a W &* ,F ( ,b de,FT-M$a a q y W &* ,F.Hz - de,FTM$a w W &* ,F ,9 ,;/( -
de,FT_M$a } W &* ,F0( -
de,FT M$a F0( - de,FT M$a W &* ,F1h - de,FTM$a W &* ,F2H - de,FTM$a W & &* ,F3( - de,FTM$a % W , &* ,F4& - de,FTM$a # + W 2 &* ,F4h, - de,FTM$a ) 1 W 8 &* ,F5H2 - de,FTM$a / 7 W > &* ,F6(8 - de,FTM$a 5 = K W ,F &*7> - e5,FTu$u ; C K W p ,F &* &!7E -! fU,FT` % A J W Q &* ,F8XK -" de,FTM$a H P W W &* ,F98Q -$ de,FTM$a N V W ] &* ,F:W -& de,FTM$a T \ W c &* ,F:x] -( de,FTM$a Z b W i &* ,F;Xc -* de,FTM$a ` h W o &* ,F<8i -, de,FTM$a f n W u &* ,F=o -. de,FTM$a l t W { &* ,F=xu -0 de,FTM$a r z W &* ,F>X{ -2 de,FTM$a x W &* ,F?8 -4 de,FTM$a ~ W
W &* ,F@x
W &* ,FAX -: de,FTM$a W &* ,FB8 -< de,FTM$a , W ,F &*C -> e5,FTu$u $ , W K ,F &* &!B8& -A fU,FT` % " + W 2 &* ,FDh, -B de,FTM$a ) 1 W 8 &* ,FEH2 -D de,FTM$a / 7 W > &* ,FF(8 -F de,FTM$a 5 = W D &* ,FG> -H de,FTM$a ; C W J &* ,FGhD -J de,FTM$a A I W W ,F &*HHJ -L de,FTM$a G O W i -j &*}Q -l de-jTM$a N U i i -j &*JW -n de-jTM$a T \ i i W -j &* &!Jp^TbU-p fU-jT` % Z @ e i Q { s q -j &* &, &- &/ &0 -rK`iTb -s bu-jT-$M a @ n w i w } -j &* -u -wMqU`-z -jTH l @ u i i -j &*Nw . de-jTM$a t { i i -j &*M} . de-jTM$a z i -j &*M . de-jTM$a i -j &*M . de-jTM$a i ) -a -c -j &* -eMTcE.
@ ) < ) && &) -jR . f-jTaU%x ) < && &) -jS . f-jTaU%x & 0 7 7 i @ -a -c -j &* -eM)TcE. -jTa5%3 # @ . @ < @ && &) -jU0 . f-jTaU%x , 5 @ < && &) -jV 7 . f-jTaU%x 3 = G N G i W -a -c -j &* -eM@TcE. -jTa5%3 : @ E W < && &) -jX G .! f-jTaU%x C L W < W && &) -jXpN .$ f-jTaU%x J T ^ e ^ i n -a -c -j &* -eMWTcE.' -jTa5%3 Q @ \ n < && &) -jZp^ .* f-jTaU%x Z c n < n && &) -j[`e .- f-jTaU%x a k u | | i -a -c -j &* -eMnTcE./ -jTa5%3 h @ s < && &) -j]`u .2 f-jTaU%x q z < && &) -j^P| .5 f-jTaU%x x
i -a -c -j &* -eMTcE.8 -jTa5%3 @
< && &) -j`P
.; f-jTaU%x < && &) -ja@ .> f-jTaU%x # * * i 3 -a -c -j &* -eM TcE.@ -jTa5%3 @ ! 3 < 3 && &) -jc@# .C f-jTaU%x ( 3 < && &) -jd0* .F f-jTaU%x & 0 : A A i J -a -c -j &* -eM3TcE.I -jTa5%3 - @ 8 J < J && &) -jf0: .L f-jTaU%x 6 ? J < && &) -jg A .O f-jTaU%x = G Q X Q i a -a -c -j &* -eMJTcE.Q -jTa5%3 D @ O a < && &) -ji Q .T f-jTaU%x M V a < a && &) -jjX .W f-jTaU%x T ^ h o h i u -a -c -j &* -eMaTcE.Z -jTa5%3 [ @ f u < && &) -jlh .] f-jTaU%x d m u < u && &) -jm o .` f-jTaU%x k s i i -j &*mpu .b de-jT_M$a r y i -j &*M{ .e de-jT_M$a x
i -j &*M .g de-jT_M$a ~ i ! -a -c -j &* -eM
TcE.j -jTa5%3 @ ! < ! && &) -jq .m f-jTaU%x / / i 8 -a -c -j &* -eM!TcE.r -jTa5%3 @ & 8 < 8 && &) -jt( .u f-jTaU%x $ - 8 < && &) -ju / .x f-jTaU%x + 5 ? F ? i O -a -c -j &* -eM8TcE.{ -jTa5%3 2 @ = O < && &) -jw ? .~ f-jTaU%x ; D O < O && &) -jwpF / f-jTaU%x B L V ] V i f -a -c -j &* -eMOTcE/ -jTa5%3 I @ T f < && &) -jypV / f-jTaU%x R [ f < f && &) -jz`] / f-jTaU%x Y c m t t i } -a -c -j &* -eMfTcE/
-jTa5%3 ` @ k } < } && &) -j|`m / f-jTaU%x i r } < && &) -j}Pt / f-jTaU%x p z i -a -c -j &* -eM}TcE/ -jTa5%3 w @ < && &) -jP / f-jTaU%x < && &) -j @ / f-jTaU%x " " i + -a -c -j &* -eMTcE/ -jTa5%3 @ + < + && &) -j@ / f-jTaU%x + < && &) -j0" /# f-jTaU%x ( 2 9 9 i B -a -c -j &* -eM+TcE/% -jTa5%3 % @ 0 B < B && &) -j02 /( f-jTaU%x . 7 B < && &) -j 9 /+ f-jTaU%x 5 ? I P I i Y -a -c -j &* -eMBTcE/. -jTa5%3 < @ G Y < && &) -j I /1 f-jTaU%x E N Y < Y && &) -j P /4 f-jTaU%x L V ` g ` i m -a -c -j &* -eMYTcE/6 -jTa5%3 S @ ^ m < && &) -j ` /9 f-jTaU%x \ e m < m && &) -j
g /< f-jTaU%x c k i i -j &*
pm /? de-jT_M$a j q i i -j &*Ms /A de-jT_M$a p x
i /_ &*}y /a de/_T_M$a v ~
i y /_ &* &! /c fU/_T` % | i y 0 4) 9 ;N ; /_ &* &, &- &/ &0 &2 &3
Tb /d bu/_T_-$M @
0 &*H 0 de0T_M$a
0 &*0 0 de0T_M$a 0
0 &* 0 de0T_M$a $ 0
0 &* &!p&TbU0 fU0T` % " @ , 6
6 0 &* &, &- &/ &0`0Tb 0TM$a 3 ; 0 D L D &* /v /w 0`> 0 de0TM$a 9 B L 0 0 &*`D 0 de0TM$a A I 0 R Z R &* /v /w 0`L 0 de0TM$a G P Z 0 0 &*@R 0 de0TM$a O W 0 ` h ` &* /v /w 0@Z 0 de0TM$a U ^ h 0 0 &* ` 0 de0TM$a ] e 0 n v n &* /v /w 0 h 0 de0TM$a c l v 0 0 &* n 0" de0TM$a k s 0 | | &* /v /w 0 v 0$ de0TM$a q z 0 0 &* `| 0' de0TM$a y 0 &* 0 ` 0) de0TM$a 0 6 0 &* &! TbU0+ fU0T` % @ 0 ) /y /{ 0 &* /}!TcE0. 0Ta5%3
@ ) < && &) 0" 00 f0TaU%x ) < ) && &) 0# 03 f0TaU%x & 0 7 0 0 @ /y /{ 0 &* /}" )TcE05 0Ta5%3 # @ . @ < && &) 0%0 08 f0TaU%x , 5 @ < @ && &) 0& 7 0: f0TaU%x 3 = G N N 0 W /y /{ 0 &* /}%@TcE0= 0Ta5%3 : @ E W < W && &) 0( G 0? f0TaU%x C L W < && &) 0(pN 0B f0TaU%x J T ^ e e 0 n /y /{ 0 &* /}( WTcE0D 0Ta5%3 Q @ \ n < n && &) 0*p^ 0G f0TaU%x Z c n < && &) 0+`e 0I f0TaU%x a k u | | 0 /y /{ 0 &* /}*pnTcE0L 0Ta5%3 h @ s < && &) 0-`u 0N f0TaU%x q z < && &) 0.P| 0Q f0TaU%x x
0 &- &/ 0 &* 0R-`Tc
< && &) 00P
0W f0TaU%x < && &) 01@ 0Z f0TaU%x # * * 0 3 /y /{ 0 &* /}0P TcE0\ 0Ta5%3 @ ! 3 < 3 && &) 03@# 0_ f0TaU%x ( 3 < && &) 040* 0a f0TaU%x & 0 : A A 0 J /y /{ 0 &* /}3@3TcE0d 0Ta5%3 - @ 8 J < J && &) 060: 0f f0TaU%x 6 ? J < && &) 07 A 0i f0TaU%x = G Q X Q 0 a /y /{ 0 &* /}60JTcE0k 0Ta5%3 D @ O a < && &) 09 Q 0n f0TaU%x M V a < a && &) 0:X 0p f0TaU%x T ^ h o o 0 u /y /{ 0 &* /}9 aTcE0s 0Ta5%3 [ @ f u < u && &) 0<h 0u f0TaU%x d m u < && &) 0= o 0x f0TaU%x k s 0 0 0 &* u 0z de0T_M$a r y 0 0 &* { 0| de0T_M$a x 0 { 0 &* &!?0 TbU0~ fU0T` % ~ @ 0 { + '
0 &* &, &- &/@ Tb 1 bu0T_-$M @ + ' 1 &# &*A0 1! de1 T_M$a + ' 1 &# &* &!B( 1# fU1 T` % $ 2 ' P A V " %4 &0 &[ 1 &# &* &, &- &/ &0 &2 &3 &5 &6 &8 &9C( + 1& bu1 T_-$M 0 P ' + 1 &# &*E8 2 1( de1 T_M$a . 8 P ' + 2 1 &# &* &!F( : 1+ fU1 T` % 5 G W ' + 2 W m / E [ q 3 I _ u 1 &# &* &, &- &/ &0 &2 &3 &5 &6 &8 &9 &; &< &> &? &AG( P 1. bu1 T_-$M = U ^ ' P 1 &# &*J W 10 de1 T_M$a S \ m ' P 1 &# &*Jx ^ 13 de1 T_M$a Z d m ' P W 1 &# &* &!Kh f 16 fU1 T` % a k t ' P 1 &# &*Lh m 18 de1 T_M$a i r ' P 1 &# &*MX t 1; de1 T_M$a p z ' P m 1 &# &* &!NH | 1> fU1 T` % w
' P 1 &# &*OH 1A de1 T_M$a ' P 1 &# &*P8
1D de1 T M$a ' P 1 &# &* &!Q( 1G fU1 T` % 1 &# &*S 1L de1 TM$a & / ' P 1 &# &* &!T ( 1O fU1 T` % # - 6 ' P 1 &# &*U / 1R de1 TM$a + 4 E ' P 1 &# &*Ux 6 1T de1 TM$a 2 < E ' P / 1 &# &* &!Vh > 1W fU1 T` % 9 C L ' P 1 &# &*Wh E 1Z de1 TM$a A J [ ' P 1 &# &*XX L 1\ de1 TM$a H R [ ' P E 1 &# &* &!YH T 1 fU1 T` % O Y b ' P 1 &# &*ZH [ 1b de1 TM$a W ` q ' P 1 &# &*[8 b 1d de1 TM$a ^ h q ' + [ 1 &# &* &!\( j 1g fU1 T` % e o x ' P 1 &# &*]( q 1j de1 TM$a m v ' P 1 &# &*^ x 1m de1 TM$a t ~ ' P q 1 &# &* &! 1p fU1 T` % { ' P 1 &# &*` 1r de1 TM$a
' P 1 &# &*`x 1u de1 T_M$a
' P 1 &# &* &!ah 1x fU1 T` % $ ' P 1 &# &*bh 1z de1 TkM$a " 3 ' P 1 &# &*cX $ 1} de1 TkM$a * 3 ' P 1 &# &* &!dH , 2 fU1 T` % ' 1 : ' P 1 &# &*eH 3 2 de1 TmM$a / 8 I ' P 1 &# &*f8 : 2 de1 TnM$a 6 @ I ' P 3 1 &# &* &!g( B 2 fU1 T` % = G P ' P 1 &# &*h( I 2 de1 ToM$a E N ' P 1 &# &*i P 2# &*q8 2& de1 T M$a * ' + 1 &# &*r( 2( de1 TbM$a / ' + 1 &# &*s * 2+ e51 Tu$u & / ' + 1 &# &* &!s ( 2. fU1 T` % # - A ' + 1 &# &*u / 21 de1 TM$a + 5 A ' + / 1 &# &* &!ux 7 24 fU1 T` % 2 > H ' + / H W 1 &# &* &, &- &/vx A 26 bu1 T-$M : F W ' A 1 &# &*x H 29 de1 TM$a D N W ' A H 1 &# &* &!y P 2< fU1 T` % K U ^ ' A 1 &# &*z W 2> de1 TM$a S \ m ' + 1 &# &*zx ^ 2A e51 Tu$u Z d m ' + W 1 &# &* &!zx f 2D fU1 T` % a k ' + 1 &# &*|h m 2G de1 TM$a i s ' + m 1 &# &* &!}X u 2J fU1 T` % p | ' + m 1 &# &* &, &- &/~X 2L bu1 T-$M x
h ] 2l de1 T_M$a Y b s ' V 1 &# &* X d 2o de1 T_M$a ` j s ' V ] 1 &# &* &!
H l 2r fU1 T` % g q !z ' V 1 &# &*8 z 2w de1 TM$a v ! ! ' V s 1 &# &* &!(! 2z fU1 T` % } ! ! ' V 1 &# &*(! 2| de1 TM$a ! ! ! ' V 1 &# &*! 2 de1 TM$a !
! ! ' V ! 1 &# &* &!! 3 fU1 T` % ! ! !& ' V 1 &# &*! 3 de1 T_M$a ! !$ !5 ' V 1 &# &*x!& 3 de1 T_M$a !" !, !5 ' V ! 1 &# &* &!h!. 3
fU1 T` % !) !3 !< ' V 1 &# &*h!5 3
de1 T_M$a !1 !: !K ' V 1 &# &*X!< 3 de1 T_M$a !8 !B !K ' V !5 1 &# &* &!H!D 3 fU1 T` % !? !I !R ' V 1 &# &*H!K 3 de1 T_M$a !G !P !Y ' V 1 &# &*8!R 3 de1 T_M$a !N !W " ' + 1 &# &*(!Y 3 e51 T_u$u !U !_ !i ' !K 38 &# &* &!(!b 3; fU38T` % !] !g !p ' + 38 &# &* !i 3= de38T_M$a !e !n !w ' + 38 &# &* !p 3@ de38T_M$a !l !u !~ ' + 38 &# &* !w 3B de38T_M$a !s !| " ' + 38 &# &* p!~ 3E de38T_M$a !z " " ' + !i 38 &# &* &! `" 3H fU38V9-% " " "! ' + !i "! "S # #0 #M #q $ $* $@ $V $l % 38 &# &* &, &- &/ &0 &2 &3 &5 &6 &8 &9 &; &< &> `" 3M 38T_-$M " " "( ' " 38 &# &*# "! 3O de38T_M$a " "& "/ ' " 38 &# &*$"( 3R de38T_M$a "$ "- "6 ' " 38 &# &*% "/ 3T de38T_M$a "+ "4 "= ' " 38 &# &*%p"6 3W de38T_M$a "2 "; "D ' " 38 &# &*&`"= 3Y de38T_M$a "9 "B "S ' " 38 &# &*'P"D 3\ de38T_M$a "@ "I "S ' " "! 38 &# &* &!(@"L 3_ fU38T` % "G "Q "Z ' " 38 &# &*)@"S 3a de38T_M$a "O "X "a ' " 38 &# &**0"Z 3d de38T_M$a "V "_ "h ' " 38 &# &*+ "a 3f de38T_M$a "] "f "o ' " 38 &# &*,"h 3i de38T_M$a "d "m "v ' " 38 &# &*- "o 3k de38T_M$a "k "t # ' " 38 &# &*-p"v 3n de38T_M$a "r "{ # ' " "S 38 &# &* &!.`"~ 3q fU38T` % "y # #
' " 38 &# &*/`# 3s de38T_M$a # #
# ' " 38 &# &*0P#
3v de38T M$a # # # ' " 38 &# &*1@# 3x de38T M$a # # #! ' " 38 &# &*20# 3{ de38T M$a # # #0 ' " 38 &# &*3#! 3} de38T M$a # #& #0 ' " # 38 &# &* &!4#) 4 fU38T` % #$ #. #7 ' " 38 &# &*5#0 4 de38T M$a #, #5 #> ' " 38 &# &*6 #7 4 de38T M$a #3 #< #M ' " 38 &# &*6p#> 4 de38T M$a #: #C #M ' " #0 38 &# &* &!7`#F 4 fU38T` % #A #K #T ' " 38 &# &*8`#M 48T` % $ $ $ ' " 38 &# &*A`$ 4' de38TM$a $ $ $* ' " 38 &# &*BP$ 4* de38TM$a $ $! $* ' " $ 38 &# &* &!C@$$ 4- fU38T` % $ $( $1 " 38 &*D@$* 4/ de38TM$a $' $/ $@ ' " 38 &# &*E $1 42 de38TM$a $- $6 $@ ' " $* 38 &# &* &!F$9 45 fU38T` % $4 $> $G ' " 38 &# &*G$@ 47 de38TM$a $< $E $V ' " 38 &# &*H $G 4: de38TM$a $C $L $V ' " $@ 38 &# &* &!Hp$O 4= fU38T` % $J $T $] ' " 38 &# &*Ip$V 4? de38TM$a $R $[ $l ' " 38 &# &*J`$] 4B de38TM$a $Y $b $l ' " $V 38 &# &* &!KP$e 4E fU38T` % $` $j $s ' " 38 &# &*LP$l 4H de38TM$a $h $q % ' " 38 &# &*M@$s 4K de38TM$a $o $x % ' " $l 38 &# &* &!N0${ 4N fU38T` % $v % % ' " 38 &# &*O0% 4P de38TM$a $~ % % ' " 38 &# &*P % 4S de38TM$a % % % ' + 38 &# &*Q% 4V e538Tu$u %
% % ' % 38 &# &* &!Q% 4Y fU38T` % % % %4 ' + 38 &# &*S % 4\ de38T_M$a % %$ %4 ' + % 38 &# &* &!Sp%' 4_ fU38T` % %" %/ %; ' + % %; %Q %g %} & 38 &# &* &, &- &/ &0 &2 &3Tp%4 4a bu38T_-$M %* %9 %B ' %4 38 &# &*V@%; 4d de38T_M$a %7 %@ %Q ' %4 38 &# &*W0%B 4f de38T_M$a %> %G %Q ' %4 %; 38 &# &* &!X %J 4i fU38T` % %E %O %X ' %4 38 &# &*Y %Q 4l de38T_M$a %M %V %g ' %4 38 &# &*Z%X 4n de38T_M$a %T %] %g ' %4 %Q 38 &# &* &![ %` 4q fU38T` % %[ %e %n ' %4 38 &# &*\ %g 4t de38T_M$a %c %l %} ' %4 38 &# &*\p%n 4v de38T_M$a %j %s %} ' %4 %g 38 &# &* &!]`%v 4y fU38T` % %q %{ & ' %4 38 &# &*^`%} 4| de38T_M$a %y & & ' %4 38 &# &*_P& 4~ de38T_M$a & & & ' %4 %Q 38 &# &* &!`@&
5 fU38T` % & & & ' %4 38 &# &*a@& 5 de38T_M$a & & &! ' %4 38 &# &*b0& 5 de38T_M$a & & &0 ' + 38 &# &*c &! 5 e538T_u$u & && &0 ' + & 38 &# &* &!c &) 5
fU38T` % &$ &. &7 ' + 38 &# &*e&0 5 de38T_M$a &, &5 &> ' + 38 &# &*f &7 5 de38T_M$a &3 &< &E ' + 38 &# &*fp&> 5 de38T_M$a &: &C &L ' + 38 &# &*g`&E 5 de38T_M$a &A &J &[ ' + 38 &# &*hP&L 5 e538T_u$u &H &Q &[ ' + &0 38 &# &* &!hP&T 5 fU38T` % &O &Y &b ' + 38 &# &*j@&[ 5 de38T_M$a &W &` &i ' + 38 &# &*k0&b 5! de38T_M$a &^ &g &x ' 38 &# &*l &i 5$ 38T` % &e &o &x ' 5B &# &* &!A0&q 5D fU5BT` % &l &v '
' 5B &# &*n&x 5G de5BT_M$a &t &~ '
' '
&x 5B &# &* &!o' 5I fU5BT` % &{ ' ' ' &x '% -w 5B &# &* &, &- &/p'
5L bu5BT_-$M ' ' '% ' '
5B &# &*q(' 5N de5BT M$a '# &* &!r' 5Q fU5BT` % ' '! ', ' '
' '? *! , -L 5B &# &* &, &- &/ &0 &2s'% 5T bu5BT -$M ' '* '? ' '% 5B &# &*tX', 5V de5BT M$a '( '2 '? ' '% ', 5B &# &* &!uH'4 5Y fU5BT` % '/ '; 'F ' '% ', 'k ) )x 5B &# &* &, &- &/ &0vH'? 5\ bu5BTf-$M '7 'D 'M ' '? 5B &# &*wx'F 54 de5BTdM$a 'B 'K 'T ' '? 5B &# &*xh'M 5b de5BTM$a 'I 'R 'k ' '? 5B &# &*yX'T 5e de5BTM$a 'P 'Z 'k ' '? 'F 5B &# &* &!zH'\ 5h fU5BT` % 'W 'e 'r '? ' 'F 'r ( ( (4 (C (Y (v 5B &* &# &, &- &/ &0 &2 &3 &5 &6{H'k 5k bu5BT-$M ' 'p 'y ' 'k 5B &# &*}8'r 5n de5BTM$a 'n 'w ( ' 'k 5B &# &*~('y 5q de5BTM$a 'u ' ( ' 'k 'r 5B &# &* &!( 5u fU5BT` % '| ( ( ' 'k 5B &# &* ( 5x de5BTM$a ( (
((Y 6 de5BT_M$a (U (^ (g ' 'k 5B &# &* (` 6 de5BT_M$a (\ (e (v ' 'k 5B &# &*
(g 6! de5BT_M$a (c (m (v ' 'k (Y 5B &# &* &!
x(o 6$ fU5BT` % (j (t (} ' 'k 5B &# &*
' '? 5B &# &*h(} 6+ e55BT_u$u (y ) )
' ) (v 5B &# &* &!h) 6. fU5BT` % ) )
) ' '? 5B &# &*X)
61 de5BT_M$a ) ) ) ' '? )
5B &# &* &!H) 65 fU5BT` % ) ) )' ' '? )
)' )6 )E )T 5B &# &* &, &- &/ &0 &2H) 68 bu5BT_-$M ) )% )6 ' ) 5B &# &*)' 6; de5BT_M$a )# )- )6 ' ) )' 5B &# &* &!x)/ 6> fU5BT` % )* )4 )E ' ) 5B &# &*x)6 6A de5BT_M$a )2 )< )E ' ) )6 5B &# &* &!h)> 6E fU5BT` % )9 )C )T ' ) 5B &# &*h)E 6H de5BT_M$a )A )K )T ' ) )E 5B &# &* &!X)M 6K fU5BT` % )H )R )[ ' ) 5B &# &*X)T 6N de5BT_M$a )P )Y )b ' ) 5B &# &*H)[ 6Q de5BT_M$a )W )` )i ' ) 5B &# &*8)b 6T de5BT_M$a )^ )g )x ' '% 5B &# &* ()i 6X e55BT_u$u )e )o )x ' ) )T 5B &# &* &!8)q 6[ fU5BT` % )l )v ) ' '? 5B &# &* )x 6^ de5BT_M$a )t )} * ' '% 5B &# &* ) 6a e55BT_u$u ){ * * ' '? )x 5B &# &* &! * 6e fU5BT` % * *
*! ' '? 5B &# &* x* 6g de5BT_M$a *
* *! ' '? * 5B &# &* &!!h* 6j fU5BT` % * * *( ' '% * *: + +` 5B &# &* &, &- &/ &0"h*! 6m bu5BT -$M * *& *: ' *! 5B &# &*$*( 6p de5BT M$a *$ *. *: ' *! *( 5B &# &* &!%*0 6s fU5BT` % *+ *7 *A ' *! *( *A *W 5B &# &* &, &- &/&*: 6v bu5BT`-$M *3 *? *H ' *: 5B &# &*'(*A 6y de5BTM$a *= *F *W ' *: 5B &# &*(*H 6| de5BTM$a *D *N *W ' *: *A 5B &# &* &!)*P 7 fU5BT` % *K *U *^ ' *: 5B &# &***W 7 de5BT M$a *S *\ *e ' *: 5B &# &**x*^ 7 de5BT`M$a *Z *c *t ' *! 5B &# &*+h*e 7 e55BTu$u *a *k *t ' *: *W 5B &# &* &!+h*m 7u +c +m +v ' *! +` 5B &# &* &!<+o 7C fU5BT` % +j +t +} ' '% 5B &# &*=x+v 7F de5BTM$a +r +{ , ' '% 5B &# &*>h+} 7I de5BTM$a +y , , ' '% +v 5B &# &* &!?X, 7L fU5BT` % , , , ' '% +v , ,2 ,A ,W ,m - - -/ 5B &# &* &, &- &/ &0 &2 &3 &5 &6 &8@X, 7O bu5BT-$M , , ,# ' , 5B &# &*BX, 7Q de5BTM$a , ,! ,2 ' , 5B &# &*CH,# 7T de5BTM$a , ,) ,2 ' , , 5B &# &* &!D8,+ 7X fU5BT` % ,& ,0 ,A ' , 5B &# &*E8,2 7Z de5BTM$a ,. ,8 ,A ' , ,2 5B &# &* &!F(,: 7] fU5BT` % ,5 ,? ,H ' , 5B &# &*G(,A 7` de5BTM$a ,= ,F ,W ' , 5B &# &*H,H 7c de5BTM$a ,D ,N ,W ' , ,A 5B &# &* &!I,P 7f fU5BT` % ,K ,U ,^ ' , 5B &# &*J,W 7i de5BTM$a ,S ,\ ,m ' , 5B &# &*Jx,^ 7l de5BTM$a ,Z ,d ,m ' , ,W 5B &# &* &!Kh,f 7o fU5BT` % ,a ,k ,t ' , 5B &# &*Lh,m 7r de5BTM$a ,i ,r - ' , 5B &# &*MX,t 7u de5BTM$a ,p ,z - ' , ,m 5B &# &* &!NH,| 7x fU5BT` % ,w - -
' , 5B &# &*OH- 7{ de5BT_M$a , - - ' , 5B &# &*P8-
7~ de5BT M$a - - - ' , - 5B &# &* &!Q(- 8 fU5BT` % - 5B &# &*S- 8 de5BTM$a - -& -/ ' , - 5B &# &* &!T-( 8
fU5BT` % -# -- -6 ' , 5B &# &*U-/ 8 de5BTM$a -2 -; -L ' '% 5B &# &*Vh-= 8 e55BTu$u -9 -C -L ' '% -/ 5B &# &* &!Ux-E 8 fU5BT` % -@ -J -S ' '% 5B &# &*XX-L 8 de5BTM$a -H -Q -c ' '
5B &# &*YH-S 8 e55BT_u$u -O -Y -c ' '
-L 8: &# &* &!YH-\ 8= fU8:T` % -W -a -w ' '
8: &# &*[@-c 8? de8:T_M$a -_ -h -w ' '
-c 8: &# &* &!\0-k 8B fU8:T` % -f -r -~ ' '
-c . 0@ 2= 4
8: &# &* &, &- &/ &0 &2]0-w 8E bu8:T -$M -n -| . ' -w 8: &# &*^p-~ 8G de8:T M$a -z . . ' -w -~ 8: &# &* &! `. 8J fU8:T` % . .: 8S fU8:T` % . .( .5 ' . . .5 .K .a .w / / 8: &# &* &, &- &/ &0 &2 &3 &5d .. 8V bu8:T -$M .# .3 .< ' .. 8: &# &*e`.5 8Y de8:T M$a .1 .: .K ' .. 8: &# &*fP.< 8\ de8:T M$a .8 .A .K ' .. .5 8: &# &* &![email protected] 8` fU8:T` % .? .I .R ' .. 8: &# &*[email protected] 8c de8:T M$a .G .P .a ' .. 8: &# &*i0.R 8f de8:T M$a .N .W .a ' .. .K 8: &# &* &!j .Z 8i fU8:T` % .U .: .h ' .. 8: &# &*k .a 8l de8:T M$a .] .f .w ' .. 8: &# &*l.h 8o de8:TM$a .d .m / ' .. .a 8: &# &* &!m .p 8s fU8:T` % .k .u / ' .. 8: &# &*n .w 8v de8:TM$a .s .| / ' .. .w 8: &# &* &!np. 8y fU8:T` % .z / /
0g 9X de8:T_M$a 0c 0l 0v ' 0Y 0` 8: &# &* &!
p0o 9[ fU8:T` % 0j 0t 0} ' 0Y 8: &# &*`0} 9a de8:TM$a 0y 1 1 ' 0@ 8: &# &*P1 9e e58:Tu$u 1 1 1 ' 0Y 0v 8: &# &* &!P1
9h fU8:T` % 1 1 1' ' -w 8: &# &*@1 9k de8:T_M$a 1 1 1' ' -w 1 8: &# &* &!01 9o fU8:T` % 1 1" 1. ' 0@ 1 1. 1= 1L 1[ 8: &# &* &, &- &/ &0 &201' 9r bu8:T_-$M 1 1, 1= ' 1' 8: &# &*p1. 9u de8:T_M$a 1* 13 1= ' 1' 1. 8: &# &* &!`16 9x fU8:T` % 11 1; 1L ' 1' 8: &# &*`1= 9{ de8:T_M$a 19 1B 1L ' 1' 1= 8: &# &* &!P1E 9 fU8:T` % 1@ 1J 1[ ' 1' 8: &# &*P1L : de8:T_M$a 1H 1Q 1[ ' 1' 1L 8: &# &* &!@1T : fU8:T` % 1O 1Y 1b ' 1' 8: &# &*@1[ : de8:T_M$a 1W 1` 1i ' 1' 8: &# &*01b : de8:T_M$a 1^ 1g 1p ' 1' 8: &# &* 1i : de8:T_M$a 1e 1n 1 ' 0@ 8: &# &* 1p : e58:T_u$u 1l 1u 1 ' 1' 1[ 8: &# &* &! 1x : fU8:T` % 1s 1} 2 ' 0@ 8: &# &* 1 : de8:T_M$a 1{ 2 2 ' -w 8: &# &* p2 : e58:T_u$u 2 2 2 ' 0@ 1 8: &# &* &! p2 : fU8:T` % 2 2 2 ' -w 8: &# &*!`2 :! de8:T_M$a 2 2 2# ' -w 8: &# &*"P2 :$ de8:T_M$a 2 2! 2= ' -w 8: &# &*#@2# :' de8:T_M$a 2 2( 2= ' -w 2 8: &# &* &!$02+ :+ fU8:T` % 2& 25 2D ' -w 2 2D 2S 2b 2x 3 3% 3; 3Q 3g 3v 8: &# &* &, &- &/ &0 &2 &3 &5 &6 &8 &9 &;%02= :- bu8:T_-$M 2. 2B 2S ' 2= 8: &# &*'P2D :0 de8:T_M$a 2@ 2I 2S ' 2= 2D 8: &# &* &!(@2L :3 fU8:T` % 2G 2Q 2b ' 2= 8: &# &*)@2S :5 de8:T_M$a 2O 2X 2b ' 2= 2S 8: &# &* &!*02[ :8 fU8:T` % 2V 2` 2i ' 2= 8: &# &*+02b :; de8:T_M$a 2^ 2g 2x ' 2= 8: &# &*, 2i :> de8:T_M$a 2e 2n 2x ' 2= 2b 8: &# &* &!-2q :A fU8:T` % 2l 2v 2 ' 2= 8: &# &*.2x :D de8:T_M$a 2t 2} 3 ' 2= 8: &# &*/ 2 :G de8:T_M$a 2{ 3 3 ' 2= 2x 8: &# &* &!/p3 :J fU8:T` % 3 3
3 ' 2= 8: &# &*0p3 :M de8:T_M$a 3
3 3% ' ' 2= 8: &# &# &*1`3 :P de8:T_M$a 3 3 3% ' 2= 3 8: &# &* &!2`3 :S fU8:T` % 3 3# 3, ' 2= 8: &# &*3`3% :V de8:T_M$a 3! 3* 3; ' 2= 8: &# &*4P3, :Y de8:T_M$a 3( 31 3; ' 2= 3% 8: &# &* &!5@34 :\ fU8:T` % 3/ 39 3B ' 2= 8: &# &*6@3; :_ de8:T_M$a 37 3@ 3Q ' 2= 8: &# &*703B :b de8:T_M$a 3> 3G 3Q ' 2= 3; 8: &# &* &!8 3J :e fU8:T` % 3E 3O 3X ' 2= 8: &# &*9 3Q :h de8:T_M$a 3M 3V 3g ' 2= 8: &# &*:3X :k de8:T_M$a 3T 3] 3g ' 0@ 3Q 8: &# &* &!; 3` :n fU8:T` % 3[ 3e 3v ' 2= 8: &# &*< 3g :q de8:T_M$a 3c 3l 3v ' 0@ 3g 8: &# &* &!<p3o :t fU8:T` % 3j 3t 3} ' 0@ 8: &# &*=p3v :w de8:T_M$a 3r 3{ 4
' -w 8: &# &*>`3} :z e58:T_u$u 3y 4 4
' -w 3v 8: &# &* &!>`4 :} fU8:T` % 4 4
4 ' -w 8: &# &*@P4
: de8:T_M$a 4 4 '
' '
8: &# &*A@4 ; e58:T_u$u 4 4 4)
;! &*H4 ;# de;!T_M$a 4 4 4)
4 ;! &* &!C4 TbU;% fU;!T` % 4 @ 4& 4/
4 4/ 7 ;! &* &, &- &/D4)Tb ;' bu;!T_-$M 4# @ 4. 4) 47 &* ;!E4/ ;) de;!T_M$a 4, 45 4) 4= 4E 4= &* ; ; ;!Ex47 ;+ de;!T_M$a 42 4< 4) 4E &* ;!Fx4= ;. de;!T_M$a 4: 4C 4) 4K 4Q 4K &* ; ; ;!Fx4E ;0 de;!T_M$a 4@ 4J 4) 4Q &* ;!HX4K ;3 de;!T_M$a 4H 4P 4) 4Y &* ;!HX4Q ;5 de;!T_M$a 4N 4W 4) 4_ 4e 4_ &* ; ; ;!J4Y ;7 de;!T_M$a 4T 4^ 4) 4e &* ;!K4_ ;9 de;!T_M$a 4\ 4d 4) 4m &* ;!K4e ;; de;!T_M$a 4b 4k 4) 4s 4{ 4s &* ; ; ;!LX4m ;= de;!T_M$a 4h 4r 4) 4{ &* ;!LX4s ;@ de;!T_M$a 4p 4y 4) 5 5 5 &* ; ; ;!LX4{ ;B de;!T_M$a 4v 5 4) 5 &* ;!O85 ;E de;!T_M$a 4~ 5 4) 5 5 5 &* ; ; ;!O85 ;G de;!T_M$a 5 5 4) 5 &* ;!Q5 ;J de;!T_M$a 5
5 4) 5 &* ;!Q5 ;L de;!T_M$a 5 5 4) 5# 5+ 5# &* ; ; ;!RX5 ;N de;!T_M$a 5 5" 4) 5+ &* ;!RX5# ;P de;!T_M$a 5 5) 4) 51 59 51 &* ; ; ;!RX5+ ;R de;!T_M$a 5& 50 4) 59 &* ;!U851 ;U de;!T_M$a 5. 57 4) 5? 5G 5? &* ; ; ;!U859 ;W de;!T_M$a 54 5> 4) 5G &* ;!W5? ;Z de;!T_M$a 5< 5E 4) 5M 5U 5M &* ; ; ;!W5G ;\ de;!T_M$a 5B 5L 4) 5U &* ;!Xx5M ;^ de;!T_M$a 5J 5S 4) 5[ 5a 5[ &* ; ; ;!Xx5U ;` de;!T_M$a 5P 5Z 4) 5a &* ;!ZX5[ ;c de;!T_M$a 5X 5` 4) 5g &* ;!ZX5a ;e de;!T_M$a 5^ 5f 4) 5o &* ;!\5g ;g de;!T_M$a 5d 5m 4) 5u 5} 5u &* ; ; ;!\x5o ;i de;!T_M$a 5j 5t 4) 5} &* ;!\x5u ;l de;!T_M$a 5r 5{ 4) 6 6 6 &* ; ; ;!\x5} ;n de;!T_M$a 5x 6 4) 6 &* ;!_X6 ;q de;!T_M$a 6 6 4) 6 6 6 &* ; ; ;!_X6 ;s de;!T_M$a 6 6 4) 6 &* ;!a86 ;u de;!T_M$a 6 6 4) 6 &* ;!a86 ;w de;!T_M$a 6 6 4) 6% &* ;!bx6 ;y de;!T_M$a 6 6# 4) 6+ 63 6+ &* ; ; ;!cX6% ;{ de;!T_M$a 6 6* 4) 63 &* ;!dX6+ ;~ de;!T_M$a 6( 61 4) 69 6A 69 &* ; ; ;!dX63 < de;!T_M$a 6. 68 4) 6A &* ;!f869 < de;!T_M$a 66 6? 4) 6G 6O 6G &* ; ; ;!f86A < de;!T_M$a 6< 6F 4) 6O &* ;!h6G < de;!T_M$a 6D 6M 4) 6U 6[ 6U &* ; ; ;!h6O <
de;!TM$a 6J 6T 4) 6[ &* ;!ix6U < de;!TM$a 6X 6a 4) 6i 6q 6i &* ; ; ;!k86c < de;!TM$a 6^ 6h 4) 6q &* ;!k86i < de;!TM$a 6f 6o 4) 6w 6} 6w &* ; ; ;!k86q < de;!TM$a 6l 6v 4) 6} &* ;!n6w < de;!TM$a 6t 6| 4) 7 &* ;!n6} < de;!TM$a 6z 7 7 4) ;! &*oX7 < de;!TM$a 7 7 7 4) 4/ ;! &* &!p87
TbU< fU;!T` % 7 @ 7 7 7! 7! 4) 7* ; ; ;! &* ; q(7TcE<! ;!Ta5%3 7) ;!s(7! <& f;!TaU%x 7 7' 71 78 78 4) 7A ; ; ;! &* ; r87*TcE<) ;!Ta5%3 7$ @ 7/ 7A < 7A && &) ;!u(71 <+ f;!TaU%x 7- 76 7A < && &) ;!v78 <. f;!TaU%x 74 7> 7H 7O 7H 4) 7X ; ; ;! &* ; u(7ATcE<0 ;!Ta5%3 7; @ 7F 7X < && &) ;!x7H <3 f;!TaU%x 7D 7M 7X < 7X && &) ;!y7O <5 f;!TaU%x 7K 7U 7 7f 7f 4) 7o ; ; ;! &* ; x7XTcE<8 ;!Ta5%3 7R @ 7] 7o < 7o && &) ;!{7 <: f;!TaU%x 7[ 7d 7o < && &) ;!{x7f <= f;!TaU%x 7b 7l 7v 7} 7v 4) 8 ; ; ;! &* ; {7oTcE<? ;!Ta5%3 7i @ 7t 8 < && &) ;!}x7v <B f;!TaU%x 7r 7{ 8 < 8 && &) ;!~h7} <D f;!TaU%x 7y 8 8
(8Y <b f;!TaU%x 8U 8_ 8i 8p 8p 4) 8v ; ; ;! &* ; 88bTcE<e ;!Ta5%3 8\ @ 8g 8v < 8v && &) ;!
(8i <g f;!TaU%x 8e 8n 8v < && &) ;!de;!TM$a 8s 8{ 9
=
&*H8} =
de=
T_M$a 8z 9 9
=
&*P9 = de=
T_M$a 9 9 9
=
&*09 = de=
T M$a 9 9
=
&*9 = de=
T_M$a 9
9 9
8} =
&* &!H9TbU= fU=
T` % 9 @ 9 9%
8} 9% : =
&* &, &- &/`9 Tb = bu=
T_-$M 9 @ 9# 9- 9 =
&*p9% = de=
T_M$a 9" 9* 9 93 9; 93 &* <} < =
P9- = de=
T_M$a 9( 91 9 9; &* =
P93 = de=
T_M$a 90 98 9 9A 9I 9A &* <} < =
09; = de=
T_M$a 96 9? 9 9I &* =
09A =! de=
T_M$a 9> 9F 9 9O 9] 9O &* <} < =
9I =# de=
T_M$a 9D 9M 9 9U &* =
9O =& de=
T_M$a 9L 9S 9 9] &* =
p9U =) de=
T_M$a 9R 9Z 9 9c 9k 9c &* <} < =
P9] =+ de=
T_M$a 9X 9a 9 9k &* =
P9c =. de=
T_M$a 9` 9h 9 9q 9y 9q &* <} < =
09k =0 de=
T_M$a 9f 9o 9 9y &* =
09q =2 de=
T_M$a 9n 9v 9 9 : 9 &* <} < =
9y =4 de=
T_M$a 9t 9} 9 : &* =
9 =7 de=
T_M$a 9| : 9 : &* =
p: =9 de=
T_M$a : : : : : 9 :% = = =
&* =p:TcE=; =
Ta5%3 : @ : :% < :% && &) =
!`: => f=
TaU%x : : :% < && &) =
"P: =@ f=
TaU%x : :" :, :3 :, 9 :< = = =
&* =p:%TcE=C =
Ta5%3 : @ :* :< < && &) =
$P:, =E f=
TaU%x :( :1 :< < :< && &) =
%@:3 =H f=
TaU%x :/ :9 :C :J :J 9 :S = = =
&* =p:<TcE=J =
Ta5%3 :6 @ :A :S < :S && &) =
'@:C =M f=
TaU%x :? :H :S < && &) =
(0:J =O f=
TaU%x :F :P :Z :a :Z 9 :j = = =
&* =p:STcE=R =
Ta5%3 :M @ :X :j < && &) =
*0:Z =T f=
TaU%x :V :_ :j < :j && &) =
+ :a =W f=
TaU%x :] :g :q :x :x 9 :~ = = =
&* =p:jTcE=Y =
Ta5%3 :d @ :o :~ < && &) =
- :q =\ f=
TaU%x :m :v :~ < :~ && &) =
.:x =^ f=
TaU%x :t :| 9 9 =
&*/ :~ =` 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;< >1 de>/T_M$a ;9 ;A ;N
;< >/ &* &!7@;CTbU>3 fU>/T` % ;? @ ;J ;T
;< ;T < =? =N >/ &* &, &- &/ &0 &280;NTb >5 bu>/T_-$M ;F @ ;R ;\ ;N >/ &*9`;T >7 de>/T_M$a ;Q ;Y ;N ;b ;j ;b &* >" >$ >/:@;\ >9 de>/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 >A de>/T_M$a ;m ;u ;N ;~ < ;~ &* >" >$ >/= ;x >C de>/T_M$a ;s ;| < ;N >/ &*? ;~ >F de>/T_M$a ;{ < ;N <
< <
&* >" >$ >/? < >H de>/T_M$a < <
< ;N >/ &*@`<
>K de>/T_M$a < < < ;N >/ &*@`< >M de>/T_M$a < < <" <) <) ;N <2 >% >' >/ &* >*9`<TcE>P >/Ta5%3 < @ < <2 < <2 && &) >/C0<" >R f>/TaU%x < <' <2 < && &) >/D <) >U f>/TaU%x <% </ <9 <@ <@ ;N <I >% >' >/ &* >*9`<2TcE>W >/Ta5%3 <, @ <7 <I < <I && &) >/F <9 >Z f>/TaU%x <5 <> <I < && &) >/G<@ >\ f>/TaU%x << <F <P <W <W ;N <` >% >' >/ &* >*9`<ITcE>_ >/Ta5%3 <C @ <N <` < <` && &) >/I<P >a f>/TaU%x <L <U <` < && &) >/J <W >d f>/TaU%x <S <] <g <n <g ;N <w >% >' >/ &* >*9`<`TcE>f >/Ta5%3 <Z @ <e <w < && &) >/L <g >i f>/TaU%x <c <l <w < <w && &) >/Lp<n >k f>/TaU%x <j <t <~ = <~ ;N = >% >' >/ &* >*9`<wTcE>n >/Ta5%3 <q @ <| = < && &) >/Np<~ >p f>/TaU%x <z = = < = && &) >/O`= >s f>/TaU%x = = = = = ;N =% >% >' >/ &* >*9`=TcE>u >/Ta5%3 = @ = =% < =% && &) >/Q`= >x f>/TaU%x = = =% < && &) >/RP= >z f>/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 ?6 f>/TaU%x >D >M >X < >X && &) >/i >O ?9 f>/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 ?E f>/TaU%x >r >{ ? < ? && &) >/n`>} ?H f>/TaU%x >y ? ;N ;N >/ &*oP? ?J de>/TM$a ? ? ? i ?h &*}? ?j de?hTM$a ? ? ? ? ? ?h &* &!q?TbU?l fU?hT` % ?
@ ? ? i ? ? ?7 ?h &* &, &- &/r?Tb ?n bu?hT_-$M ? @ ? ?% ? ?h &*s? ?q de?hT_M$a ? ?$ ?+ ? ?h &*sx?% ?t de?hT_M$a ?" ?* ?1 ? ?h &*tX?+ ?w de?hT_M$a ?( ?0 ? ? ?h &*u8?1 ?z de?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 ?d 3N ?j@@ ?iO@ ?h N ?d P ?g ?d @ 1,~ , ~Z
?f
" " 6@B =h A7@,~ @ B ,~ @@ ?[@@ ?\ CI, A 6@ ?`+ CD7@ ?a+ A"" b &+ CC B ?] B ?b " B ?a CJ b '+ CC@ 3B CJ $ 3B CK $ 3B CK $ 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*0B 1B 7 + CD " p PCN CO XCP xCP @CD @CD @CD @CD @CD CD @CD CD AE AE CM . ?]@ b '+ + CD6@ ?`+ AK
" + CD + CD6@ ?`+ AN
& + CD + CD7@ ?_+ AQ@@ ?_ ?^+ CD6@ ?`+ AU7@ ?a+ AV
7 ?^[ ?^+ CD OB ?^+ CD+ AV1@ \@ + AU6@ ?A+ CC6@ ?^O@ ?B+ CD6@ ?`+ Ab7@ ?a+ Ae, C.O@ d &+ CCr" Q. X. n '+ CC\ + CD~" $4 CCZ + CD[ ?`+ CD7@ ?`+ Ah *4 CC+ 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, AOW 1\ 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\
5D CC+ CD xC (Bd Bq 8C, B{@@ ?Z
?]
?U, C+ Bh, B+ BeZ ?Y5B Bk " C\, B+ Bk, B<
?]
?^, C+ Bn+ Ar6F ?W, C%$ C]!" 5D B + Ar@@ ?ZZ ?Y4B Bs, B<+ Bt " C\, B,> , B{
?]
?^, C+ C] ?U $ D ?], B8,^ + Ar
?^
?U, C+ C
?U" 1B + C, C
?^, C+ C+ B} J ?]+ CD( C_.( h C_1h ,~ /* ( + C,> ,> ` ` 2J : ,^ ,^ ,~ ?U3B ?^+ C", B ?U Z ?Y5B C " .6 ?Z, BO@ ?Z, BB+ Ar1< + C " C_, B+ Ar, B?4B Ar0B + Bq " C`, B+ Ar, B{@@ ?Z
?U
?^, C+ C", B
?U
?], C+ C"/" $ =d C Ca 4D C2D + C + Bq" C]5B Ca " , B+ Ar[ 1B "A`0BA`+ B , B+ CD,> ,> ." @@ Q` : *$,^ ,^ + CD*x ,> C0Q.-n8 1 C0: + C7*x ,> ,> ,> ,> C5Q.~-n8 1 C5: ~,^ ,^ ,^ ,^ ,~ *x ,> ,> ,> ,> C<Q&~-f 1 C<: ~,^ ,^ ,^ ,^ ,~ * x ,> CAQ<-|p 1 CA: ,^ ,~ g O ,~ H @&H @TERMINAL UUO FAILED " CF+ %
UM* /* ?amQ
mQ* mQ* `iSH CN[K COJ CP ?T5\ A~!" + B " , B+ Ar> ?T2 ?T< $ d CU9 CD CD BF BH BI
0 ?T
< ?T6F ?W, C%+ Bw< H BX!" + B p @
`p B p B p B p B p GN p Ir p L p L" p L" p L# p L# p L$
p O p O p P p R8 p R9 p R: p R; p R< p R= p R? p R@ p RB p RC p
RE p RG p RH p RJ p RK p S! p SX p SY p SY p SZ T; @ T= p TA p
TD 8 TI ` TM 0! TP H! TR (! TW 8!% Th (!) Tj !- Tm p!1 To !5 Tp !9 Tr `!= Tt H!A Tv p!E Tx p!I Tz x!M T{ !Q T} !U U P!Y U !] U !a U `!e U 0!i U !m U !q U !u U p!y U !} U x! U @! U! ! U# H!
h"- V `"1 V H"5 V ("9 V `"= V "A V x"E V X"I V! X"M V$ @"Q V' "U V* @"Y V- `"] V0 h"a V3 h"e V6 h"i V9 "m V< p"q V? X@ VA P@ VB H@
VE ( VJ h VL 0 VN ( VQ @( VS H( VU `() Vj @(- Vm ((1 Vo ((5 Vr (9 Vv (= Vx (A Vz p(E V} H(I W P(M W (Q W H W ( W `p E p W != uP p YQ p YR p YR 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 p a p aN &( U G\ E* @p G^ E* /@p Hf ( ,Y G` z0GM ) f
` @p G[Z $/ p G]SPEAR.MSG DSK:SPEAR.MSG H&, H@ ? Gd H% @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>covery AlgorithmsP0I
query_res_error_msg Hw G- XHx p Hz
`I @p # H{This is the Theory Query response error message. The theory number that I
@p $ Iyoutenteredddoesrnotsexist.ePleasetcheckmthesnumberand try again.Also, 0I @p I RETURN key to repeat the Query prompt. zI9 @p I6A{@}p zHo @p I P ranquestreserrormsg
`I/ @p # I'This is the Random Question response error message. The number that you ` @p I0entered is not within the range of 1 to 60. /8K G- 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 @p IGtext at a time. After you have read the text you can: `IN @p PIU @p IO 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 @p I} return to the page that you were at when you typed /B. @J @p 8J
@p J 5. Type anything else and you will get this message. P @p zJ @p J /8|# $ menu_res_error_msg !XJ G- " J "8 J
`J @p " JThissisrthe menu response error message. 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 @p J6 are interested in. &XJ; @p 'JC @p J< 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] @p JV 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 @p Jq 5. Type anything else and you will get this message. . @p zLS @p LQ;` zI5 @p J} t(J
`K
@p " KThiseisithetforwardRresponseferrordmessage.uYoulcanesequence through 08K @p " Kn Introduction, followed by a menu, followed by the first 2HK& @p # K subject, 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 @p K` return to the point that you were at when you typed /B. ;pKh @p <hKo @p Ki 5. Type anything else and you will get this message. = @p zKu @p Kr9]P^ " revtransreserrormsg >Kw G- >XKx >p Kz
`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 @p Lsubject to another. You can: B8L @p C L" @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 @p L. 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 @p L@ 5. Type /B to return to the Spear prompt. GxLG @p HXLN @p LH 6. Type anything else and you will get this message. Hp @p farewellerM.X 1.0. ans_res_error_msg /LU G- J8LV JP LX
`La @p # LYThis is a response error message. Your response does not match the list K Li @p # Lbof acceptable responses. For further information press the RETURN key, L @p
Ljthen type: ? or HELP. 1.M.1.1. zLq @p LO2K O" MhLr G- NLt N( Lu
`Lz @p struct bids you farewell. NX @p L{Type /Break to return to Spear. lHNg G- zM @p M;9 Mb $ courseadmin PM G- PHM P` M
`M @p M
Spear Course Administrator and Student Guide QM @p R M @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, @p Hp U0M. @p UHM2 @p M/ Digital Equipment Corporation U`M7 @p M3 Course Administrator MR1-2 / E17 V(M; @p M8 200 Forest Street VxM? @p M< 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 @p Md P{\ , course_admin_a \(Mh G- \hMi ] Mk
`Mr @p Ml TOPS-10 T F TOPS-20 F 2Analyze Retrieve Summarize ]0My @p MsEvent File 3EventFFile T Dialog Dialog NDialog ^ N @p Mz----------. T ---------- 4.-------- -------- --------- 5N @p N.1. TF F 1.TT FF 5. T 1. T F N1.@T F 1. T. F `NT F 6. T F 6. T F 6. T F dN. @p N( 7. T F 7. T F 7. T F 7. T F 7. T F dxN3 @p N/ 8. T F 8. T F 8. T F 8. T F e`N: @p N4 9. T F 9. T F 9. T F 9. T F Summarize f8NA @p N;10. T F 10. T F 10. T F 10. T F Report g NE @p NB --------- hNI @p NFCompute 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 F zL @p LP29HU & OpNh lp Nj
`No @p Nkg The Spear LibrSpear Course@Menu m Np @p mpNr @p nNw @p Ns 0. Course Administrator/Student Guide n Ny @p nxN| @p Nz 1. Troubleshooting oN~ @p oHO @p N 2. System Event Files o`O @p p O @p
Appendices q0O @p q`O @p O A. FEEDBACK qxO @p O B. Theory Query r(O @p O C. Disk Recovery Algorithms r`O @p
O D. RandomTQuestions s( @p zO& @p O$ MhJ{ & feedback t(O' G- t`O) tx O*
`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? @p O;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 @p Odcontact: |0Og @p |XOh @p |pOm @p Oi Digital Equipment Corporation }Oq @p On The SPEAR Team MR1-1 / S35 }POu @p Or 200 Forest Street ~Oy @p Ov Marlboro, Mass. 01752 ~POz @p O| @p (O @p O} Thank you; @ @p P The Spear Team spear_mane1.2. zP @p P dJ random_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# @p P question 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 @p P@check student progress.
pPD @p
0PM @p " PEAfter being informed that you have correctly answered a question, you
HPT @p PNmay select another random question by typing "RANDOM".
PPV @p
H @p PWType <return> if you wish to enter the random question mode. zP` @p P > n $
`Pb G-
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 @p Ptreference 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 @p Q
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 @p Q+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.
hQq G- zQZ @p QX= dn R.T.cou_ovr_a
`Q[ G-
Q]
8 Q^
`Qg @p # Q_STOP - You are moving in a reverse direction through the menu. You are
h @p Qhabout to back into the Course Administrator/Student Guide. zQT @p LP R+
HQr
Qt
`Q| @p # QuAbout two hours ago the CTY sent it's last message. Now you are gazing
@R @p Q}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 $ R the wall. The little hand points to three ... the big hand is lost some-
#h @p R(where in the fog ...... zR/ @p R-
hS 1.0.A.
%8R0 G-
%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` @p RY "I was an hour into the nightly batch job when the thing just
+ Rf @p Ra 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 @p Rs "So I turned off and on a couple of times and then...."
. R{ @p
/ @p R|Oh well, you've been at ground zero before. zS @p S
%8SQ 1.0.B.
0S G-
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 @p S,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@ @p SNand you didn't quit your job. zSU @p SS
0T; 1.0.C.
:SV G-
:PSX
:h SY
`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 @p Skthe 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 @p T ever happen before ?"
@8T @p
@xT
@p
AT @p " T You'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 ! T that 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 @p T6and, at the same time enjoy the challenge. zT? @p T=
:UQ 1.0.D.
G8T@ G-
GpTB
H TC
`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 @p Tq"Make a mental note, so that won't happen again."
N Tx @p
NhTy @p
O U @p TzAfter all, you're a professional troubleshooter; and professional
O @p Utroubleshooters enjoy doing a professional job. zU @p U
lHV_ R.T.1.0.
Q UG-
Q8U
QP U
`U @p # USTOP - You are moving in a reverse direction through the menu. You are
R U @p Uabout to back into the Troubleshooting Introduction.
SU! @p
Sx @p
U"Your response please: zU' @p Lmhy(
TPU) G-
TxU*
U U,
`U- @p
U@U2 @p U. Troubleshooting
UXU3 @p
V U6 @p U4Topic menu:
V8U8 @p
VhU; @p U90. Introduction
W U< @p
W0U@ @p
U=1. Attitude vs. Approach
WHUB @p
XUF @p UC2. The Formal Approach
X UG @p
X`UL @p The Systematic Approach
XxUM @p
Y@ @p
UN4. The Variable Approach zUT @p Lm
G8V$
ZUU G-
Z@UW
ZX UX
`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 @p Uzwill; 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 @p V Never give up and you'll never lose. ! 1.3. zV( @p V&
ZV~ 1.1.A.
dHV) G-
e V+
e V,
`V2 @p V- 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 @p Va
Q lH R.T.1.1.A.
kxVd G-
l0Vf
lH Vg
`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.
n Vz @p
o @p
V{Your response please: zW @p P
dHWY &
o`W G-
pW
p W
`W
@p W The Formal Approach
pPW
@p
q(W
q@W @p WThe 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 @p W+ 3. SETUP a practical experiment (to test the educated guess)
u(W4 @p
v(W; @p W5 4. PREDICT the result (before you conduct the experiment)
v@W= @p
w8WD @p W> 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\ @p W[
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 @p Xlast serviced, by whom, and why. 0X @p X @p # X
When you first arrive on site take five or ten minutes to talk with the X @p # Xcustomer, the operator, or anyone else that may be able to explain the (X$ @p # X problem. Here's a partial list of the type of questions that you should 0X% @p I6 @X' @p XX+ @p X(How serious is the problem ? pX- @p 8X2 @p X.How long has it been going on ? PX3 @p X: @p X4Has the system ever had a problem like this before ? 8X< @p (XB @p X=How has the system been performing lately ? @XC @p @p XDHave there been any recent hardware or software changes lately ? zXO @p XM
|(h 1.2.B. 8XP G- pXR
XS
`X\ @p ! XTYou can define the problem at the same time that you are doing the
8Xa @p X]research. Ask yourself three questions: @Xc @p
Xd @p
0Xj @p Xe 1. What is happening that shouldn't ?
HXk @p 2.XWhat is not happeningrthateshouldu?ding co ons ? 8X{ @p Y @p # X|The first two questions will help you identify the main error symptom. 0Y
@p # YTheCthirdyquestionhwill helpryoutidentifyethe'contextiorlcircumstances 8Y @p " Ye to solve a problem out of context.zY @p Y
`Y+ @p # Y#Once again, the-questionsto ask yourself when defining a problem are: (Y, @p 0Y. @p HY4 @p Y/ What is happening that shouldn't ? `Y: @p Y5 @YA @p Y; What is not happening that should ? YG @p YB YM @p YH What are the surrounding conditions ? pYN @p PYP @p hYY @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 or Yj @p " Ybcircumstances that surround that symptom. One more thing, and this is Ys @p # Ykimportant, you should write the definition down, at least in note form. Yt @p 0Yw @p YuFor example: HYy @p x @p YzDef - 4 days/2020/256K/cache/TOPS-20(4.1)/UBANXM/freq:12-14 hrs.zZ @p Z
`Z
@p Z
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
Z a1UBANXM Bug'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 @p Z9the error symptom (i.e., the context of the problem). zZB @p ZA
`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 @p Zjsystem 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 # [possibilityhoflmultiplererrorspcompoundingythecproblemssolving process. 08[ @p # [obvious symptom first, which is sound troubleshooting practice. z[" @p [
`[, @p ['Review - The key pointsXdiscussed so far are: 4h[. @p 5H[5 @p [/ 1. Talk to anyone who may know something about the problem. 5`[7 @p 6X[= @p [8 2. DEFINE the problem. Find out exactly: 6p[> @p 7P[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 the A \ @p # \problem. The truth of the matter is, when you first start out to solve B0\$ @p # \ a problem, you can't know (for sure) what the cause is. Therefore, you C8\, @p ! \%really don't have much of a choice; you have to begin with a guess. D@\. @p EH\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 you Fp\I @p # \Ause this approach and your guesses are testable, then they will quickly H \P @p \Jbecome accurate. In other words, they will either: I\Q @p J \X @p \R a) lead you directly to the cause of the problem, or J\Z @p K\c @p $ \[ b) they will lead you to the realization that you could use some help. K \d @p L0 @p
\eEither2way, youMwin.z\k @p \j MP \p
`\y @p # \qHere's a couple of testable educated guesses (tegs)to go along with the N \ @p \zproblem that was identified and defined earlier: O] @p Ox] @p P]
@p ]Def - 4 days/2020/256K/cache/TOPS-20(4.1)/UBANXM/freq:12-14 hrs. P(]
@p Q(] @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 ]&
`]( @p Th]- @p ]) REMEMBER U ]. @p UP]5 @p ]/ Tegs don't have to be earth shattering. Uh]6 @p VP @p ]7 But they do have to be testable.z]@ @p ]> Sh^
1.2.J. WH]A G- X ]C X ]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 every YP]^ @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^M 1.2.K. a(^ G- a`^ ax ^
`^ @p $ ^The Old Garden path, by the way, is a New England expression that refers b(^$ @p $ ^ to a troubleshooting tangent; a lessons in pure frustration. The path or c8^- @p # ^%tangent leads you away from the real cause of the problem, contributes dH^5 @p " ^.very little useful information, and it consumes lots of valuable time eP^8 @p ^6and effort. fX^: @p g^; @p g ^D @p $ ^<So, give yourself a break. Don't take a chance on a trip down the garden g8 @p ! ^Epath. Instead, use the time to carefully think out your experiment. z^P @p ^O a(_ 1.2.L. iP^R G- j^S j ^U
`^^ @p $ ^VThe.experimentDdoesn'tehavehtovbetcomplexeorhelaborate. Let'sgopback to jP^g @p # ^gthe.problem definition andltegssthatrweeusedsearlier,qand seeif weEcan k`^p @p # ^hdevise aacouple ofesimplesexperimentsthat will prove,2or.disprove, the lp^r @p ^qtegs. n ^s @p n ^u @p n8^} @p ^vDef - 4 days/2020/256K/cache/TOPS-20(4.1)/UBANXM/freq:12-14 hrs. nP^~ @p oP @p ^Teg #1. A low voltage condition exists at one of the UBAs. oh
`_* @p _%Review - The key points discussed so far are: tH_, @p u(_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 @p xh_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 @p zx_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. ` @p x` @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`f 1.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
(aA 1.2.O.
h`k G-
`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 @p a Maybe...this will happen (or) Maybe...that will happen
xa @p
xa
@p
a @p # a When 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 $ a curiosity. 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
@p a:out. Don't get tricked into going off on a wild turkey chase. zaE @p aC
hb
1.2.P.
aF G-
PaH
h aI
`aQ @p aJGetting 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 @p a_Teg #1. A low voltage condition exists at one of the UBAs.
`am @p afExp #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} @p awTeg #2. One of the Unibus cables is improperly seated.
hb @p a~Exp #2. Clean and reseat each cable in the Unibus.
X @p bPre #2. One of the cables will be loose or dirty. zb @p b
c , 1.2.Q.
!(b G-
!`b
!x b
`b @p # bWell, that's it for the hard part. The last three steps are relatively
"(b# @p # b simple and straight forward. But before we go on, let's quickly review
#0b' @p b$the main points:
$8b( @p
$pb/ @p b) 1. Research and Define the problem. Find out:
%b0 @p
%pb6 @p b1 a) What is happening that shouldn't ?
&b< @p b7 b) What is not happening that should ?
&hbB @p b= c) What are the surrounding conditions ?
'HbD @p
((bL @p bE 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 @p bW 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| @p bw 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
@p c
!(cN 1.2.R.
0hc G-
1 c
18 c
`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
4 c& @p c" 1. Check the voltage at each UBA.
4c( @p
4hc- @p c) 2. Clean and reseat each UBA cable.
5 c/ @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 @p cKnot a five minute job. zcQ @p cP
0hd
1.2.S.
9`cS G-
:cT
:0 cV
`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
? @p dcould easly be done in ten minutes. That's not so bad. zd
@p d
9`db 1.2.T.
AdG-
A@d
AX d
`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 @p dd
Ae@ 1.2.U.
L(dg G-
L`di
Lx dj
`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 @p d|accomplished one of two things.
O8e @p
Pe @p e 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 @p e you can use to refine the problem definition.
R0e @p
Se @p
S0e @p
SHe& @p " e If 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 @p e9was incorrect. In either case you should STOP IMMEDIATELY. zeC @p eB
L(f 1.2.V.
X eE G-
X8eF
XP eH
`eQ @p $ eIYou must figure out which was in error; the experiment, or the predicted
Y eZ @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 @p emto 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 @p fwhole thing and start over again. zf @p f
X fb 1.2.W.
c0f G-
chf!
d f#
`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 @p fd
c0gJ 1.2.X.
l fg G-
lXfh
lp fj
`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 @p g
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 @p gEthan recalling facts. Don't you think ? zgM @p gL
l gX 1.2.Y.
y gO G-
yXgP
yp gR
` @p gSEither you disagree, or you're not thinking. zg[ @p gZ
y le 1.2.Z.
{ g] G-
{8g^
{P g`
` @p gaSo do I. zgf @p gd
{XK
1.2.A1.
|(gg G-
|`gi
|x gj
`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@newproblemsinto the.system and thus,
`h# @p # hNEWdSYMPTOMSa-tFinally,tifsyouvrestoreetheSsystemototitsnoriginalstate 1.
`hS @p " hLStepp72--REFINErthe definitioniandhREPEAT thepprocessdbeginning with
8he @p # h]experiment,eandpthemresultsofothe experimentptonthehproblemmdefinition.
Phv @p ! hnthebdefinition.iAtpleastoyoueknow onenthing thatis notcausingthe 1.2.D1.
`i& @p # i Takelyourhtimemappendingitheenewtinformationetowthecproblemsdefinition.
@p # j j support.wButtevenwaucallfor supporteisea tegnof.fashions,dbecauset from
`j' @p # j OneolasttworddbeforeAwergoconwtorthevfinalisummary.sEarlier,ewentalked
j9mean neverucalltsupport. l.vIt'sitherettophelpeyoutdoeyourdjobwmorerefficiently. 1.2.F1.
`jp @p # jhNeverGgivecupsreallybmeans,wnevercleteawproblemlgoawithoutdfindingioutou
thecause was andthowyheioryshesarrivedoatrthatmconclusion. olved.sAndlthat'slwhere zk1 @p k/ @ \h , 1.2.G1.
`k8 @p k6FinalRSummary: ndaDEFINEgtheaproblem.nFind outsexactly: ause.e,wyouryteg. 7bhuR F.T.1.3.
`l@ @p # l9ThattconcludesetheiexplanationmofithepFormal.Troubleshooting Approach.
kxui R.T.1.2.G1.
`lY @p # lQSTOPu- Youbare movinghinFarreverseudirectionnthroughathe menu. You are
lbYour response please: zlF @p V#
{ m"
`lo @p llSystematicsSubstitution etpuristatechniciansnmayfnotaagree,tbutiunder
Forexample,mlet'soassumelthatFyouhareoat,home,sinsNeweEngland,uworking apcircular
`m2 @p # m+Suddenly,wtheesawgbinds,ethetlightstdimcandithenstheylgoeout.eFromftheure
@p n .3.B.
G- n
`n @p nAt1thisupointsyoulhave,troughly,nsixhoptions:roblemuwillpdisappear.nThis,
` @p ! nRD2. You can call an electrician, but that could be very expensive. zn] @p n[
`nj @p $ nbk3. You canigongetyatflashlightu(if youncanpfind one that works) and use
`o @p " nx4. Youtcantlightiaucoupleemorehmatches,gstudy.thetwiringtdiagramtand ris @p o
1.3.F.
`o* @p ! o#+5. YougcancuseethevsparescanderandomlylsubstituteTfusessuntilrthe e zoQ @p oO
1.3.G.
`o^ @p $ oVh6. Youecanguseatheesparesoandisystematicallybsubstituteteachpfuseluntil
`p @p # pNow let'spsay that, afterRcareful consideration of all six options, you Pp @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) @p p2 @p " p*Finally, you eliminate using the wiring diagram to figure out exactly p: @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 @p pM
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 time hq
@p qyou need it.) xq
@p (q @p $ qNof opting forqthepflashlight,%you optedJfor the @q @p # qsystematicsubstitutionqapproach and, on the fourth try you locate thePq& @p $ q blown fuse. Total time expended (at 30 seconds per fuse): 2 minutes with X @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 faced 8qM @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, a Xqf @p " q_scope, and a set of prints. But the diagnostics that you need are not `ql @p qgon site. The same six options apply: hqm @p @qu @p qn1. You can stall for time wishing the problem will go away. Xqy @p qv2. 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) @p r'0s0 & 1.3.K. $Xr* G- %r, %( r-
`r6 @p " r.A.sYouomustrapproach thepsubstitutionprocess systematically.rIfayou %Xr> @p ! r7odudon't,vyou'll becomeoconfused and endrup@resorting toothelrandom &`rG @p # r? yomethodooflsubstitution.hTherrandomhmethodXis so prone 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 @p 0`s @p $ sD. If you substitute a module and the symptoms change, STOP. Replace the 0xs @p " s original module. If the original symptoms return, then chances are 2s" @p # s you have come upon a bad spare. Try it one more time. If the results 3s* @p # s# are the same; Tag the spare right away. If you don't, you're likely4 @p s+ to forget and reliable spares are a must. zs4 @p s2$XtX * 1.3.L. 6s5 G- 6@s7 6X s8
`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 you 8sR @p # sJ inadvertently changed something and didn't realize it. Retrace every 9s[ @p " sS step. Symptoms change for a reason. Find the reason. Don't run the :(s` @p s\ 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.oMake sure @@t @p $ t few minutes, make sure that the equipment comes back on line ok. BXt @p C`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, everything E t: @p $ t2 seemed to work fine. In this case you may, or may not have identified FtC @p # t; the cause of the problem. You don't know. So, leave the spare in the G tL @p # tD system, tag the suspect module as potentially intermittent, and save H0tU @p $ tM your notes. Such situations call for a different type of confirmation I@ @p tV technique. zt[ @p tZ6v 1.3.M. K t] G- K8t^ KP t`
`ti @p # taThe technique is called the subjective time window. To use it, you must L tr @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 was N u @p $ t|intermittent, however, then you must determine the rate, or frequency of O0u
@p " utheyfailure,mtriple ite(atoleast), anduusepthat asthe period oftime P@u @p u not recur during the time window that you set up, R@u$ @p u then you can assume that you solved it. Tag the suspect module asSHu- @p ! u%intermittent, return it for repair, file your notes, and close out THu5 @p " u.the paper work. If, however, the problem does recur, then you're all UPu= @p u6set, replace the original module, update your notes, and pick up VXuE @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 @p uOand that's worth something. zuV @p uT
`uc @p # u[ThatMconcludesGthe explanation of the]Systematic Substitution Approach. [( @p udNext on the menu is the Variable Approach. zum @p uk
`uz @p # urSTOP - You are moving in a reverse direction through the menu. You are^v @p u{about to back into the Systematic Substitution Approach. _ v @p ` @p
vYour response please: zv @p m K v; `pv G- av
a0 v
`v @p v The Variable Approacha`v @p b8v @p " vThis short story was once told by a senior field service engineer to bPv& @p ! v illustrate a VERY important point about using the variable approach cXv. @p " v'to isolate the cause of an intermittent failure. The story is about a d`v7 @p " v/telephone conversation he had while working for another company (not eh @p v8to be mentioned). 2.M.lost.zv? @p v=`pw# 1.4.A. g8v@ G- gpvB h vC
`vL @p # vD"At first, the diagnostic only failed every hour or two. So I performed h8vU @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 and jXvf @p # v_clock margins awhile. That helped some. I pulled out a marginal modulek`vn @p vgand the symptoms changed so I knew I was getting closer. lhvo @p m`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 varying ow
@p $ wthe temperature would have any effect. Finally, I tapped around with the pw @p # w back of my screw driver awhile. That really helped. I found a couple of q(w @p $ wvibrational modules. But now I seem to have a new problem - I can't even r8 @p w load the diagnostics. What do you think is wrong ?" zw' @p w%g8wZ 1.4.B. t8w( G- tpw* u w+
`w4 @p $ w,At that point, the senior engineer would bellow; "Now that's what I call u8w= @p ! w5a dumb question - Obviously the guy beat the poor thing to death." vHw> @p wPw@ @p whwI @p # wAThe story served it's purpose. Clearly, it illustrates the problem with x wQ @p " wJindiscriminately using the variable approach. That is, if you're not y @p ! wRreal careful, you're likely to cause more problems than you solve. zw] @p w\t8x& 1.4.C. { w_ G- {Xw` {p wb
`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 @p Px @p # xKeep in mind that; if an intermittent problem is, in fact, being caused hx @p # xby an environmentally sensitive component then, just a slight variation xx! @p $ xin voltage, temperature or clock speed should be enough to aggravate it. @p x"The rule of thumb is; BE CAREFUL. zx* @p x({ U% 1.4.D. hx+ G- x- 8 x.
`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 not xxP @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 you 0xm @p $ xea lot of unnecessary grief and aggravation. And don't forget the rule of
@xo @p xnthumb: BE CAREFUL zxz @p xxMa8
ts_end hx{ G- x} 8 x~
`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 any py @p # yother troubleshooting approaches that you think should be added to this y" @p # ysection please get in touch with us. We're listed under FEEDBACK on the y% @p y#main course menu. @p y& Thank You zy+ @p m!
TPz ( y, G- 0y. H y/
`y5 @p y0 System Event Files xy: @p y6 (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 @p yVsoftware detected errors, etc.). Py[ @p yd @p # y\The classification and type of information that is recorded in a system 8ym @p $ yeevent file is unique to the operating system maintaining the event file. Hyp @p ynFor example: Xyr @p yy @p ys TOPS-10 supports approximately 55 event categories. yz @p z @p y{ TOPS-20 supports approximately 25 event categories. (z @p z
@p z!VAX/VMS$supports approximatelyi20 eventicategories. c0z @p !Rzference card. zz @p z{+ " 2.0.A. "`z G- #z #0 z
`z& @p ! z File Structures - There is nothing special about the file structure #`z, @p z'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 to 0X @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{- @p v:"a q 50{/ G- 5X{0 5p {2
`{6 @p {3 System Event Files 6 {7 @p 6`{: @p {8Topic Menu: 6x{< @p 7({? @p {= 0. Overview 7@{@ @p 7p{E @p {A 1. TOPS-10 System Event Files8{F @p 8P{K @p {G 2. TOPS-20 System Event Files8h{L @p 90{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 {^ \+Z define_lst;@{a G- ;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> @`| @p A | @p ! |
If DEFINE.LST is not in the system documentation area you can get a A8| @p " |copy from the Spear distribution tape. There are two procedures; one B@ @p | for TOPS-10, the other for TOPS-20.tops_10_efsystem.0 z|( @p |% !X} , pri_define_tops_10 D8|) G- E |+ E |,
`|5 @p # |-TOPS-10 procedure to copy DEFINE.LST from the Spear tape to your area.EH|6 @p FP|? @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|[ @p K|` @p |\ /RESTORE DEFINE.LST = DEFINE.LST<cr> K0|h @p |aNote: BACKUP will print the following message and reprompt. Type:L|j @p V#M|m @p |k "DEFINE LST" M |n @p {ZMP|p @p Mh|s @p |q /UNLOAD<cr> N |v @p |t /EXIT<cr> N0|~ @p |wNote: Remove and return the Spear distribution tape. Then type: N`| @p O` @p
} PRINT DEFINE.LST<cr>z} @p }D8Hq , pri_define_tops_20 P0} G- Px}
Q }
`} @p # }edure to copy DEFINE.LST from the Spear tape to your area.Q@} @p RH} @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}? @p W`}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 @p Yp}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~" ^}t G- ^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~ @p bp @p " ~Don't forget, you can use the /BREAK feature and return via your ID. j(~W G- z~& @p ~$^
9 tops_10_ef_a d(~( G- dh~) e ~+
` @p ~,Press the RETURN key when you are ready.z~4 @p ~2'B tops_10_ef_q1 f~6 G- fH~7 f` ~9
`~> @p ~:TOPS-10 System Event Files - Q1 of 10 g~@ @p gh~H @p ! ~ATrue or False - Many of the questions that pertain to the TOPS-10 h @p ~Isystem event file also pertain to the TOPS-20 system event file. tops_10_ef_q2_alost.z~! @p ~Tqh9 tops_10_ef_q1_at d~X jp ~Z
`~] @p ~[That's correct.k ~^ @p kP~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 as lp~x @p " ~pthey pertain to the TOPS-20 system event file, then you can probably mx @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, then p @p
don't be confused by the redundancy. z @p H~R tops_10_ef_q1_af qh G- r0 rH
` @p $ The statement is TRUE. The TOPS-10 system event file (ERROR.SYS) and the rx) @p " !TOPS-20 system event file (ERROR.SYS) are very similar. Therefore, it t1 @p " *stands to reason that many of the questions that pertain to one event u @p 2file will also pertain to the other event file. z V G- z< @p ~Pj(n w= G- w@? wX @
`F @p ATOPS-10 System Event Files - Q2 of 10 xG @p x` @p ! HTrue or False - The TOPS-10 System Event File is called ERROR.SYS. tops_10_ef_q3_aTRUE z8 @p T}a A tops_10_ef_q2_at w X zh Y
`\ @p ZThat's correct.{^ @p {Hg @p $ _Both the TOPS-10 and the TOPS-20 system event file are called ERROR.SYS. {` @p hThe VAX/VMS system event file is called ERRLOG.SYS. zr @p pwR tops_10_ef_q2_af }`t G- ~(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. ) ' @p a 0 @p " (In the mid 1970's the idea of a system event file along with the file y 8 @p # 1name ERROR.SYS was carried over to TOPS-20. Thus, both the TOPS-10 and @p 9the TOPS-20 system event file are called ERROR.SYS.
e G- z C @p Oz!B E G- 9 F P H
a M @p ITOPS-10 System Event Files - Q3 of 10 O @p Y W @p ! PTrue or False - Prior to the Spear library, TOPS-10 used a program p @p Xcalled SYSERR to record entries in the system event files. tops_10_ef_q4_aFALSEz ? @p c)m tops_10_ef_q3_at y g
X h
a q @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. In 9- @p # %addition to translating event file entries it also attempts to localize I6 @p $ .the cause of intermittent disk and tape subsystem failures. Note however Y? @p " 7that neither SYSERR nor Spear have anything to do with recording the h @p @system event file. z G @p D a
tops_10_ef_q3_af )H G- qJ K
aO @p LThat is correct. 9P @p qY @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 ^
H Yq G- s t
az @p uTOPS-10 System Event Files - Q4 of 10 I{ @p ! @p ! |True or False - All hardware detected failures are recorded in the 8 @p system event file. tops_10_ef_q5_aTRUE z l @p )c tops_10_ef_q4_at A !`
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 @p J Y tops_10_ef_q4_af )N G- )IO )` Q
aT @p RThat'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 !$ ,9g G- ,ai ,x j
ap @p kTOPS-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_aTRUE z b @p 4Ie
tops_10_ef_q5_at ,! 0h
a
@p
That's correct.1 @p 1I @p $ Furthermore, the header and body section of each entry type is described 1a @p " in a file called DEFINE.LST. To obtain a copy of DEFINE.LST, refer to 2p @p Appendix A on the Event File Menu. z ) @p &,9 tops_10_ef_q5_af 4I* G- 5, 5( -
a6 @p ! .The statement is TRUE. Each entry in the TOPS-10 system event file 5Y> @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 was 7iP @p # Hrecorded, the processor serial number, the length of the header section 8yY @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 @p 0!T <Yi G- =k = l
ar @p mTOPS-10sSystemeEvent Files -0Q6fof710 =Is @p >!| @p " tTrue or False - Eachrecord in aTOPS-10 system event file represents >8 @p
a @p $ The statement is true with one exception, KLERR. KLERR entries are built A! @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 then C9) @p %recorded in the system event file. DI+ @p E4 @p $ ,Because the buffer area set aside for communications between the console E1= @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 sequence GQO @p $ Gnumber and recorded as a separate record in the event file. Technically, H` @p Ptherefore, the statement is FALSE. z X @p V<Y
tops_10_ef_q6_af JAZ G- K [ K ]
a` @p ^That's correct.KQa @p Lj @p $ bThe KLERR entry consists of multiple records. Each record has a separate Ls @p " ksequence number. When a KLERR entry is translated, however, only the M)| @p # tfirst sequence number is used to identify the entry. The other sequence N0 @p }numbers are masked-out to avoid confusion. T9( G- z @p @)@ P9 G- Pa Px
a @p TOPS-10 System Event Files - Q7 of 10 Q) @p R @p " True or False - The synchronization word is used to recover from hard R @p read errors that occur while reading the system event file. tops_10_ef_q8_aFALSEz @p %X ! tops_10_ef_q7_at P!) U +
a. @p ,That's correct.U1/ @p Ua8 @p ! 0Whenever Spear uses the synchronization word to recover from a hard Ux @p " 9read error it will print the message "Bad header found - RESYNCing". z E @p BP9# tops_10_ef_q7_af X F G- XQH Xh I
aR @p " JTheestatement islTRUE.Thezfirst wordineach systemTeventefile data YZ @p # Sblockois aosynchronizationkpointer.sThe pointer 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 are bP @p v:t)' G- z # @p !T9\ * d% G- d9& dP (
a- @p )TOPS-10 System Event Files - Q8 of 10 e/ @p eY8 @p $ 0True or False - When the TOPS-10 operating system detects a device error eq< @p
9the following occurs: g= @p gAF @p $ >1. Normal operation is suspended and applicable hardware and/or software gYO @p $ G status is captured (at error) and saved in the Unit Data Block (UDB). hiQ @p iyX @p R2. If applicable, an error recovery algorithm is applied. jZ @p k 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 again l)p @p l (at end) and appended to the UDB. m1r @p n { @p # s4. The error status stored in the UDB is formatted, assigned a sequence n! @p | number, and appended to to the system event file. o1 @p p!
@p " 5..Ifftheosystem was ableetowrecoverlfrom theoerrorrnormaloperation p9 @p r then the job affected by the error is notified and it r@ @p
handles the error. tops_10_ef_q9_aTRUE z @p ${Ip tops_10_ef_q8_at cy( tp *
a- @p +That's correct.u!. @p uQ6 @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) and viG @p " @errors that affect the operating system itself are also handled in a wqP @p " Hsimilar manner. If, however, there is no recovery algorithm or if the xyX @p " Qrecovery algorithm is unsuccessful, then those errors may result in a z @p
Yuser job or system crash.z a @p ^d" tops_10_ef_q8_af {Ib G- |d |( e
` @p # fThe statement is TRUE. Most TOPS-10 device errors are handled this way. a G- z r @p t), ~t G- ~)u ~@ w
a| @p xTOPS-10 System Event Files - Q9 of 10 ~q~ @p I @p ! True or False - The exact content and format of each TOPS-10 event ` @p record is described in the Spear Manual.tops_10_ef_q10aFALSEz n @p A
R tops_10_ef_q9_at }i (
a @p ! The statement is FALSE. The Spear Manual does describes the report Y& @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_af A2 G- 3 5
a8 @p 6That's correct.Q9 @p @p :The event records are described in a file called DEFINE.LST.Iy G- z E @p f K )F G- QH h I
aO @p JTOPS-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 @p Zresults 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
( @p lwant one, refer to Appendix A on the Event File Menu. tops_10_ef_lq0_TRUE z A @p v8 tops_10_ef_q10_at z |
a @p # }ThelstatementdisiFALSE.bOpen0the.DEFINE.LSTntobthea011lentry.aIttstarts A 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 the 1 , @p # $left you will see that word number 5 is defined as CONIINITIAL. To the 9 5 @p # -right you will see that CONIINITIAL is described as "controller status I 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)t tops10efq10af 9 Q G- S T
a W @p UThat's correct.I Y @p y 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 the 1
@p $ }contents of the file. The introduction explains the overall organization A
@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_efTRUE z
; @p rd(~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 *!
V G- *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. 6A 8 G- z @p *!/ tops_20_ef_a 0A G- 1 1
` @p TURN key when you are ready.z @p uy6 tops20efq1 2! G- 2a 2x
a @p TOPS-20 System Event Files - Q1 of 10 3) ! @p 4 * @p ! "True or False - Many of the questions that pertain to the TOPS-10 4 @p +system event file also pertain to the TOPS-20 system event file. tops_20_ef_q2_a ( z @p 6>
tops_20_ef_q1_at 0) : 7 ;
a > @p <That's correct.79 @ @p 7i H @p # AIn fact, the questions are practically identical. In many cases so are8 Q @p " Ithe answers. Therefore, if you have already answered the questions as 9 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 < @p kdon't be confused by the redundancy. z t @p r\Y 4 tops_20_ef_q1_af > v G- >I w >` 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 event A( @p
file will also pertain to the other event file. F9
8 G- z
@p 16A
O C1
G- CY
Cp
"
a
' @p
#TOPS-20 System Event Files - Q2 of 10 D!
) @p Dx @p !
*True or False - The TOPS-20 System Event File is called ERROR.SYS. tops_20_ef_q3_a3.0. z
@p
5Iy tops20efq2at C
9 G
;
a
> @p
<That's correct.G1
? @p Ga
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
3 tops_20_ef_q2_af Iy
U G- JA
W JX
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 idea M
{ @p $
sproved to be a good one and new entries were added to the file until now N)
|ERROR.SYSiisrthe mainPsource of information for solving intermittent O9
In@themidR1970'satheaideadofvarsystemPeventRfile,along withTthe-file Q @p
1F9$ T)
a @p System-EventrFilesh-iQ3eof 10 UeTOPS-20 usedsa program V @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 however aq @p " that neither SYSERR nor Spear have anything to do with recording the c @p !system event file. z ( @p &T)
tops_20_ef_q3_af dA* G- e + e -
a0 @p .That is correct. eQ2 @p f : @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 operating h0 @p
Pm1o G- z Q @p T j0 V
a[ @p WTOPS-20 System Event Files - Q4 of 10 ja] @p k9e @p ! ^True or False - All hardware detected failures are recorded in the kP @p fsystem event file. tops_20_ef_q5_a @@ z M @p muE tops_20_ef_q4_at iYq mx r
a{ @p ! sThe statement is FALSE. Only failures that require operating system n) @p " |intervention are recorded in the system event file. Failures that do o1
@p # notmrequiremoperatingesystemeinterventioncarernotorecordedninqthe event p9 @p " the recovery is successful then the operating is not rQ& @p # notified. Thus, those kinds of errors are normally not recorded in thesX @p 'system event file. z . @p +iqk tops20efq4af u/ G- ua1 ux 2
a5 @p 3That's correct.v)7 @p vY? @p # 8Only errors that require operating system intervention are recorded invp @p @the system event file. |9h G- z G @p hm1 xQI G- xyJ y L
aQ @p MTOPS-20 System Event Files - Q5 of 10 yAS @p z\ @p # TTrue or False - Every record in a TOPS-20 system event file consists of z0 @p ]a header section and a body section. tops_20_ef_q6_ais 2.z C @p e aH
tops_20_ef_q5_at x9i } k
an @p lThat'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 @p Appendix A on the Event File Menu. z
@p xQc tops_20_ef_q5_af a
G- )
a @p ! The statement is TRUE. Each entry in the TOPS-20 system event file q @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 was 2 @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 of 0 @p Eentry.
Qi G- z J @p a|96 L G- )M @ O
aT @p PTOPS-20 System Event Files - Q6 of 10 qV @p
I^ @p " WTrue or False - Each record in a TOPS-20 system event file represents
` @p e complete system event. tops20efq7an X z F @p gif tops20efq6at ik
au @p $ mThetstatementeisrtrueewithhonevexception,0KLERR.eKLERReentriesyarembuilt @p $ restarted the entry is transfered via the DTE to KL main memory and then a
@p recorded in theBsystem eventufile. qset aside for communications between the console Y @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 sequence y1 @p $ )number and recorded as a separate record in the event file. Technically, @p 2therefore, the statement is FALSE. z ; @p 8 e
tops_20_ef_q6_af i< G- 1> H ?
aB @p @That's correct.yD @p )M @p $ EThe KLERR entry consists of multiple records. Each record has a separate AU @p " Nsequence number. When a KLERR entry is translated, however, only the Q^ @p # Vfirst sequence number is used to identify the entry. The other sequence X @p _numbers are masked-out to avoid confusion. a
G- z h @p b
Q# aj G- k m
ar @p nTOPS-20 System Event Files - Q7 of 10 Qt @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 $1 tops_20_ef_q7_at I
!(
a @p That'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 % a tops_20_ef_q7_af $1) G- $y* % ,
a4 @p " -Theestatement islTRUE.The]first wordineach systemTeventefile data %A= @p # 5blockois aosynchronizationkpointer.sThe pointer pointstoethetstarting&IE @p ! >locationiof1the'nextrrecord inatheifile.fThus, ifaawhard#readperror 'QN @p # Foccursewhileireadingeaerecord Spearnskipsetorthe-next@data block,treads (YW @p ! Othe syncrword, findstthebstartingalocationiof thexnextprecord,and )i[ @p @p a< * 09 G- 0a 0x
a @p TOPS-20 System Event Files - Q8 of 10 1) @p 2 @p $ True or False - When the TOPS-20 operating system detects a device error 2 @p
the following occurs: 3) @p 3i) @p $ !1. Normal operation is suspended and applicable hardware and/or software 40 @p * status is captured (at error) and saved in a buffer.51 @p 69 @p 22. If applicable, an error recovery algorithm is applied. 6: @p 7C @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 again 81Q @p L (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 @p GIP tops_20_ef_q8_at 0! @p
ap That's correct.A! @p AQ @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) and Bi' @p " errors that affect the operating system itself are also handled in a Cq0 @p " (similar manner. If, however, there is no recovery algorithm or if the Dy8 @p " 1recovery algorithm is unsuccessful, then those errors may result in a F @p
9user job or system crash.z A @p >09 tops_20_ef_q8_af GIB G- HD H( E
` @p # FThe statement is TRUE. Most TOPS-20 device errors are handled this way. Mar G- z R @p @)
JT G- J)U J@ W
a\ @p XTOPS-20 System Event Files - Q9 of 10 Jq^ @p KIf @p ! _True or False - The exact content and format of each TOPS-20 event K` @p grecord is described in the Spear Manual.tops_20_ef_q10aSpot.z N @p pQ@xv tops_20_ef_q9_at Iit N( u
a~ @p ! vThe statement is FALSE. The Spear Manual does describes the report NY @p ! formats generated by Retrieve. But it does not describe the content O` @p and format of the actual event records. z @p Jn
tops_20_ef_q9_af QA G- R R
a @p That's correct.RQ @p S" @p $ The event records are described in a file called DEFINE.LST. To obtain a S* @p #copy of DEFINE.LST refer to Appendix A on the Event File Menu. T), @p U( @p " -P.S. You will need a copy of DEFINE.LST to answer the next question. \Yj G- z 8 @p k2!? Va: G- W ; W =
aB @p >TOPS-20 System Event Files - Q10 of 10 WQD @p X)L @p # ETrue or False - The thirty second word in a 111 type record is used toXAR @p Msave the first channel control word. YIS @p Z!\ @p % TNote: Refer to DEFINE.LST. If you do not have a copy of DEFINE.LST and you Z8 @p ]want one, refer to Appendix A on the Event File Menu. tops_20_ef_lq0_ up z 4 @p ggy p tops_20_ef_q10_at VIk ] 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 @p left 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 the bI& @p # right you will see that the RETRYCNT is saved in bit 18 thru 35 of the cQ- @p 'word and it is described as "final retry error count". da. @p eQ7 @p " /Now find word number 28. You will see that it is defined as CCW1, it eh @p # 8consists of 36 bits, and it is described as "first chan control word".z D @p AVae tops20efq10af gyE G- hAG hX H
aK @p IThat's correct.i M @p i9V @p $ NWord 32 is used to save the error retry count. The first channel control iQ_ @p $ Wword is saved in word 28. Anytime you want to know exactly what hardware jah @p $ `and software status is saved in an entry type you can consult DEFINE.LST kqi @p mr @p $ jNow, if you haven't already done so, take a few minutes to look over the m{ @p $ scontents of the file. The introduction explains the overall organization n) @p # |and format of an event file record. Following the introduction, each of o9
@p the event types are described in detail.pI @p q! @p #
When you are finished, take a few more minutes and compare the reportsq9 @p " listed in the Spear Manual with the corresponding record descriptions rA% @p # listed in DEFINE.LST. As a result, you will have a better understanding sH @p " &of the system event file and the reports that are generated from it. vax_vms_ef H z 2 @p c0A uy3 G- v!5 v8 6
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 @p IP f vax_vms_efx xyM G- y9N yP P
aY @p # QThe VAX/VMS Event file section of Instruct was not complete in time for zb @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 @p is complete, you can come back and try to answer the questions. A @p A& @p " P.S. If you're not running Spear on a VAX/VMS system then chances are Y- @p ' the VAX/VMS version of Spear has not been released yet.a/ @p X @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 Files qQ @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 specific a @p # questions about the VAX/VMS System Event File (ERRLOG.SYS). Before youi @p % attempt to answer the questions you should review Chapter (?) and Appendix q @p % (?) in the Spear Manual. (Don't forget, you can use the /BREAK feature and @p return via your student ID.) QI G- z # @p ! Y vaxvmsefa q$ G- 1& H '
` @p (Press the RETURN key when you are ready.z 1 @p /[ !
vax_vms_ef_q1 Q2 G- 4 ( 5
a; @p 6Q1 of 10 (VAX/VMS System Event Files) Y< @p 1@ @p =True or False - IA @p @p Qvax_vms_ef_q2_aare: z @p G)e vax_vms_ef_q1_at YK L
aN @p 6IO @p ` @p PThat's correct.z W @p TVyE vax_vms_ef_q1_af )X G- qZ [
a^ @p \VAX/VMS Q19_ @p ` @p
`The statement is TRUE 9 G- z g @p BQ
Qi G- yj l
aq @p mQ2 of 10 (VAX/VMS System Event Files) As @p v @p tTrue or False - 1x @p h @p `vax_vms_ef_q3_afile.z c @p }!1 vax_vms_ef_q2_at 9
a @p VAX/VMS Q2a1 @p -X @p The statement is FALSE z @p
a @p VAX/VMS Q2"A @p "h @p That's correct.&17 G- z @p y 9A
#I G- #q" $ #
a) @p $Q3 of 10 (VAX/VMS System Event Files) $9* @p %. @p +True or False - %)/ @p %` @p vax_vms_ef_q4_a- z @p 5(T vax_vms_ef_q3_at #19 &x :
a= @p ;VAX/VMS Q3')> @p 'P @p ?That's correct.z F @p C#I3 vax_vms_ef_q3_af (G G- (aI (x J
aM @p KVAX/VMS Q3))N @p )P @p
OThe statement is TRUE -)o G- z V @p 0&1y
*AX G- *iY + [
a` @p \Q4 of 10 (VAX/VMS System Event Files) +1b @p , e @p cTrue or False - ,!g @p ,X @p vax_vms_ef_q5_a4 z R @p l/ vax_vms_ef_q4_at *)p -p r
at @p sVAX/VMS Q4.!v @p .H @p wThat's correct.z } @p {*Aj vax_vms_ef_q4_af / G- /Y /p
a @p VAX/VMS Q40! @p 0H @p
The statement is TRUE 4!& G- z @p h-)0
19 G- 1a 1x
a @p Q5 of 10 (VAX/VMS System Event Files) 2) @p 3 @p True or False - 3 @p 3P @p vax_vms_ef_q6_a; z
@p $6 C vax_vms_ef_q5_at 1!( 4h )
a, @p *VAX/VMS Q55- @p 5@ @p .That's correct.z 5 @p 219" vax_vms_ef_q5_af 6 6 G- 6Q8 6h 9
a< @p :VAX/VMS Q57= @p 7@ @p
>The statement is TRUE ;^ G- z E @p 4!i
81G G- 8YH 8p J
aO @p KQ6 of 10 (VAX/VMS System Event Files) 9!Q @p 9yT @p RTrue or False - :V @p :H @p "vax_vms_ef_q7_aB z A @p [=z vax_vms_ef_q6_at 8_ ;` a
ac @p bVAX/VMS Q6<e @p <8 @p fThe statement is FALSE z m @p k81Y vax_vms_ef_q6_af =o G- =Yp =p r
at @p sVAX/VMS Q6>!v @p >H @p wThat's correct.B G- z } @p W;
?)~ G- ?Q ?h
a @p Q7 of 10 (VAX/VMS System Event Files) @ @p @q
@p True orpFalse-v A fq8aI z y @p Cy 2 vaxvmsefq7at ? BX
a @p VAX/VMS Q7C @p C0 @p That's correct.z $ @p !?) vax_vms_ef_q7_af Cy % G- DA ' DX (
a + @p )VAX/VMS Q7E , @p E0 @p
-The statement is TRUE I M G- z 4 @p B X
F! 6 G- FI 7 F` 9
a > @p :Q8of 10z(VAX/VMSSystemEventFiles) G @ @p Gi C @p ATrue or False - H E @p H8 @p
a R @p QVAX/VMS Q8J T @p J( @p UThe statement is FALSE z \ @p ZF! H vax_vms_ef_q8_af K ^ G- KI _ K` a
a c @p bVAX/VMS Q8L e @p L8 @p fThat's correct.P G- z l @p FI
M m G- MA o MX p
a v @p qQ9 of 10 (VAX/VMS System Event Files) N w @p Na { @p xTrue or False - Ny | @p O0 @p svax_vms_ef_q10aVp z h @p QiG vax_vms_ef_q9_at M PH
a
@p VAX/VMS Q9Py @p Q @p
That's correct.z @p M vax_vms_ef_q9_af Qi G- R1 RH
a @p VAX/VMS Q9Ry @p S @p
The statement is TRUE Vy < G- z # @p }Q F
T % G- T9 & TP (
a - @p )Q10 of 10 (VAX/VMS System Event Files) U / @p UY 2 @p 0True or False - Uq 4 @p V( @p
8vax_vms_ef_lq0_r0 z @p 9XiR vax_vms_ef_q10_at Sy = W@ ?
a B @p @VAX/VMS Q10 Wq C @p X @p DThat's correct.z K @p HT 7 vax_vms_ef_q10_af Xi L G- Y1 N YH O
a R @p PVAX/VMS Q10 Yy T @p Z( @p
UThe statement is TRUE ^ t G- z \ @p 5q- [ ] G- [A _ [X `
a i @p $ aThat's it. There are only 10 questions about VAX/VMS System Event Files. \ @p jPress the RETURN key to get back to the System Event File Menu. z X @p
251 i $ [ u ^@ w
a | @p x Spear Library ^q ~ @p _I @p Introduction _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 library a1 @p ! contains four functions: Summarize, Analyze, Retrieve, and Compute. bA @p cI ' @p $ The first three functions; Summarize, Analyze and Retrieve, are designed ca / @p " (to help you sort and evaluate 32- and 36-bit system event files. The dq 8 @p # 0third function, Compute, calculates system availability. Its purpose is ey A @p ! 9to help you prepare crash and up time reports and determine overall g D @p Bsystem performance. h F @p hI O @p # GIn the future we plan to expand the library to include a Watch function ha X @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 @p ahelp you maintain the size and content of system event files. failures.2z m @p k^ ^
3.0.A. m n G- mQ p mh q
a z @p $ rEach Spear Library functions supports a dialog style user interface. The n @p # {dialog prompts for information and waits for a response. If the prompto) @p " excepts a default, the default will be (parenthetically) included as p1 @p
part3of theprompt. q8 @p z 2 @p
R.T.3.0.rev_trans_sl_intro r9 G- s s(
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 . @p uH @p
/Your response please: r 3 G- v! 5 v8 6
a < @p 7 Spear Library vi = @p wA @ @p >Topic Menu: wY B @p x E @p C 0. Introduction x! G @p xY J @p H 1. Analyze xq K @p y! N @p L 2. Retrieve y9 P @p yi S @p Q 3. Compute z T @p z1 W @p U 4. Summarize zI Y @p zy \ @p Z 5. Applications { @p z a @p `m = 3.1.0. {a c G- | d |0 f
a k @p g Spear Library - Analyze |a m @p }9 p @p nIntroduction }Q q @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). As 1 @p #
each record is read it is sorted according to subsystem and error type. 9 @p I @p $ Then, by applying a set of fixed theories, Analyze attempt to relate the a ( @p $ error symptoms to the failing component within the subsystem. The result q 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 d 3.1.0.A. Y B G- 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!H 3.1.0.B.
A i G-
y j
a t @p " mRetrievessupportsepacketttranslation. Thus,Sifryourquestionranreport, H @p $ ~manually evaluate the evidence (records), and draw your own conclusions. z !$ @p !(S 3.1.M.ntrofP z ! @p !
r9&5 R.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 @p i!3 @p !1Topic Menu: !4 @p 1!8 @p !5 0. Introduction I!9 @p != @p !: 1. Analyze Dialog !> @p Q!B @p
!? 2. Theories Descriptionsi!D @p ( @p !E 3. Questions & Answers z !K @p !J
A3c $ 3.1.1. !M G- 9!N P !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 mode A!j @p !h------------ q!k @p !!p @p !l Event file (SYSTEM:ERROR.SYS): 9!r @p !u @p !s Time from (-1): !!w @p Y!{ @p
!x Time to (LATEST): q!| @p 1" @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" @p on 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#W 3.1.1.B. /Q# G- 0 # 0 #
a# @p #The second selection prompt: 0Q# @p 1# @p
#
Time from (-1):11# @p 1i# @p " #allows you to specify the time at which to begin analyzing the system 2#! @p " #event file. The default response (-1) is inclosed in parentheses and 3 #) @p " #"refers to yesterday at 00:00:01 hours. It can be selected by pressing 4#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 type 6!#D @p # #<Earliest, the analysis will begin with the earliest (or first) entry in 71#G @p #Ethe event file.8A#H @p 8q#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 @p e 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$ @p A$ @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 $& @p DQ$+ @p $' Report to (DSK:Ammdd.RPT):Di$, @p E1$5 @p " $-allows you to specify the name of the output Report file. The default EI$> @p # $6response (DSK:Ammdd.RPT) is enclosed in parentheses and can be selected FQ$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 response Hi$X @p " $Pby specifying a new file name. You can also replace any field in the Iy$a @p $ $Ydefault response by specifying only the field that you want to override. K$b @p L$k @p ! $cFor example, if todays date was December 25th and you were to type: L)$l @p M1$r @p $m Report to (DSK:Ammdd.RPT): FS:<cr> MI$s @p N!$z @p $tthe output file specification would become FS:A1225.RPTN9$| @p O)$} @p OA% @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% @p S!% @p % Report to (DSK:Ammdd.PAK): S9%" @p T %* @p %#allows you to specify the name of the output Packet file. Again: T!%+ @p U!%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%< @p W)%E @p $ %=2. The expression mmdd refers to the current month and day respectively. WA%F @p XQ%O @p # %G3. You can replace the entire default response by specifying a new file Xi%W @p %P name, or you can replace any field in the default response by Yy%^ @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. ^ %u G- ^A%w ^X %x
a%| @p
%yThe&confirmation prompt: t %~ @p eI& @p %ge anTypes<cr>eto confirm (/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&" @p d&+ @p ! &#If you want to change a response, press the BACKSPACE key until you d( @p # &,arrive at the corresponding prompt, make the change, and then type /GO. anadiaq1mp z &9 @p &7!;O R.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&Q G- iy&R j &T
a&X @p
&UAnalyze Dialog - Q1 of 10jA&Y @p k&b @p ! &ZTrue or False - Analyze attempts to isolate (or localize) the cause k&j @p " &cof intermittent Mainframe, Disk, Tape, Unit-record, and Communication l @p &ksubsystem failures. ana_dia_q2P z &s @p &qy' ana_dia_q1_at my&u G- n9&v nP &x
a' @p " &yThe statement if FALSE. This version Analyze only attempts to isolate o' @p '(or localize) the cause of intermittent Disk and Tape subsystem p '
@p ' failures. Specifically: q ' @p qI' @p ' RH10, RH11, and RH20 Massbus controllers connected to qa' @p ' RP04, RP05, RP06, or RM03 Disk drives. rY' @p 3s9'$ @p ' RH10, RH11, and RH20 Massbus controllers connected to sQ'* @p '% TU45 or TU77 Tape drives thru a TM02/03. tI', @p u)'2 @p '- RH11 and RH20 Massbus controllers connected to uA': @p '3 TU70, TU71, TU72, or TU73 Tape drives thru a DX20 - TX01/02. v)'< @p w)'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&o ana_dia_q1_af y'N G- yQ'P yh 'Q
a'T @p 'RThat's correct.z'V @p zI'^ @p ! 'WThe main thrust behind Analyze is to attempt to isolate or at least za'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 10 a( @p !( @p ! (
True or False - Analyze is capable of isolating the exact cause of 8 @p (intermittent Disk and Tape subsystem failures 100% of the time. ana_dia_q3X z (! @p ( 1)1 ana_dia_q2_at Y(# G- ($ 0 (&
a(. @p " ('The statement is FALSE. Analyze is NOT capable of isolating the exact a(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 an y(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 @p h
(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 the Q(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_af 1) G- q) )
a) @p )That's correct.9) @p i) @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*
)5 G- A)7 X )8
a)< @p
)9Analyze Dialog - Q3 of 10 )> @p I)G @p $ )?True or False - The packet numbers listed in the Analyze report refer to a)O @p # )Ha set pointers that identify the records that were used as evidence top @p )Psupport the corresponding theories.ana_dia_q45p z )Z @p )X 9+
ana_dia_q3_at a)[ 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 file 1)t @p " )lto Retrieve and select one or more packets for translation. Thus, you 9)| @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 willPlooktsomethinglike this: "Q* @p #a*' @p *PAKWRT V1.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+" @p 4 ++ @p # +#True or False - Retrieve can Translate packets contained in the Analyze 4 @p +,packet file. ana_dia_q5Lh z +3 @p +1=i,L ana_dia_q4_at 5y+5 G- 69+6 6P +8
a+; @p +9That's Correct.7+< @p 71+E @p ! +=However, if you specify multiple packet numbers, you should realize 7I+M @p ! +Fthat Retrieve will NOT translate the records in the order that they 8Q+V @p " +Nappear in the packets. Instead, the records will be translated in the 9Y+^ @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+t G- >)+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, @p Ay, @p $ ,The following prompt/response illustrates how to translate a packet. The B,# @p $ ,dialog directs Retrieve to translate the records in packet 4 and display C!,( @p ,$the result (in Full format) on the TTY. D1,* @p E ,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,P G- Iq,R J ,S
a,W @p
,TAnalyze Dialog - Q5 of 10J9,Y @p Jy,a @p " ,ZTrue or False - Analyze will accept and process a binary history file K @p ,bgenerated by Retrieve. ana_dia_q6^x z ,k @p ,iUy-O ana_dia_q5_at Lq,l G- M1,n MH ,o
a,s @p ,pThatrislcorrect.w My,t @p N1,} @p # ,uAnalyzelwilllaccept andPprocessaany standard2binaryosystem eventzfile.NI- @p ,~There-is,Vhowever,oonefgeneral restriction: OQ- @p P1-q5af Uy-5 G- V9-6 VP -8
a-@ @p ! -9The statement is TRUE. In fact, Analyze will accept and process any W-I @p " -Astandard binary event file. That includes special purpose event files X @p -J(or history files) generated by Retrieve. z -Q @p ,eLq-x Yq-S G- Z-T Z0 -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 (the a. @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_.Q ana_dia_q6_a2 fI.: G- g .; g .=
a.@ @p .>That's correct.gQ.A @p h.J @p $ .BRelative time is measures in whole days. Since today won't be over until h @p .Ktomorrow, the correct answer is yesterday at 00:00:01. z .T @p -vfI/q j.U G- jA.W jX .X
a.\ @p
.YAnalyze Dialog - Q7 of 10k .^ @p kI.f @p " ._True or False - Analyze can be run automatically every midnight via a k` @p .gBatch control file. ana_dia_q8@ z .o @p .m~0 & ana_dia_q7_at m9.q G- my.r n .t
a.w @p .uThat's correct.nA.x @p nq/ @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/ @p q!/ @p " /
@SUBMITPSPEAR /TIME:30u/AFTER:TODAY!9Resubmit SPEARNagainOtomorrow. 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 @p x9/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 was yY/ @p # /Wgenerated. The weekly report was used to help determine the maintenance zi/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.k anadiaq7af ~/w G- ~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 daily 0 @p
via a Batch control file. z 0 @p .im90J 0 G- )0 @ 0
a0 @p
0Analyze Dialog - Q8 of 10q0 @p 10% @p ! 0 True or False - Both the "Time from" and the "Time to" prompt will H @p 0&accept either real time or relative time. ana_dia_q90 z 00 @p 0. )1 ana_dia_q8_at I02 G- 03 05
a08 @p 06That'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 @p 0L0, ana_dia_q8_af )0P G- i0Q
0S
a0[ @p " 0TThe statement is TRUE. Both the "Time from" and the "Time to" prompt
10b @p 0\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
0np dd representsethesday, he first three letter of the month, 0 @p 0y yy represents the last two digits of the year, and 1 @p 1 hh:mm:ss represent the hour, minute and second respectively. y1 @p y1
@p 1 @p 1 The format for specifying relative time is: -dd. Where:)1 @p 1 @p $ 1 dd is a numerical value that refers to some number of whole past days. 0 @p jz 1 @p 0*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.q1QX z 17 @p 15$ Jy ana_dia_q9_at 919 G- y1: 1<
a1E @p # 1=The statement is FALSE. All Spear Library Functions (including Analyze) A1J @p 1Faccept 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 be A1e @p # 1^used to build an indirect file. There are only two rules that you mustQ1g @p )0 Y1h @p q1q @p # 1i 1. The responses in the file must pertain to one Spear function only. 1r @p 1{ @p # 1s 2. The responses must be in the correct order and conclude with a /GO. )1} @p 92 @p # 1~If you omit any responses (or the /GO switch), you will be prompted for Q2 @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$ @p 2"Y13 & ana_dia_q9_af $2% G- $A2' $X 2(
a2+ @p 2)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 @p 2Gfiles but they must be preceded with an exclamation point (!). (a2O @p )a2S @p
2PANALYZE !KFunction )y2X @p 2TSYSTEM:ERROR.SYS ! Eventcfile*92[ @p 2Y-7 !OTime!from +2c @p 2\LATEST !-Time@to +92c @p w @p ! 2pThe indirect response file can only be submitted at the main Spear -q2} @p 2xprompt and must be preceded with a @ sign. .y2 @p /X @p 3 Example: SPEAR> @SPRLWK.CMD<cr>z 3 @p 3iQ35 anadiaq10 0A3 G- 13 1 3
a3 @p Dialog - Q10 of 10 1I3 @p 2 @p " 3True or False - The entire Analyze dialog can be entered on one line. z 3 @p 3 6Y'I anadiaq10at 313 G- 3q3" 4 3#
a3& @p 3$That's correct.493( @p 4i30 @p ! 3)Using the ESCAPE key and Control W (^W) you can complete the entire 5 @p 31Analyze dialog without prompting. z 39 @p 370A3
ana_dia_q10_af 6Y3; G- 73< 70 3>
a3G @p # 3?The statement is TRUE.Once you become familiar with the Analyze dialog 7a3P @p $ 3Hyou will be able to use the ESCAPE key and the Control W (^W) feature to 8q3Y @p # 3Qenter your responses. The ESCAPE key will display each default response :3` @p 3Zin order. The ^W allows you to alter the default response. ; @p PACKET 3..z 3e @p 11"
a3s @p $ 3kThat's it. If you have gotten this far, then chances are you have a good = @p 3thandle on the Analyze dialog. Qa5 G- z 3} @p 3{r 8 * ANALYZE INPUT ?3~ G- ?Q4 ?h 4
a4 @p 4Analyze Help Message: Event File Prompt @4 @p @q4 @p 4 System Event File ___. .----------. .___ Report File A 4 @p 4 ! ! Event ! ! B 4 @p 4 Retrieve !---! File !---! Bq4% @p 4 (binary) File ___! ! Analysis ! !___ Packet File CY4+ @p 4& !__________! DY4- @p E944 @p 4. INPUT PROCESS OUTPUT EQ46 @p FI4> @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_ @p 4Yto the individual records that support each theory. K4` @p Kq4i @p " 4aAt this prompt Analyze is waiting for you to specify the name of the L 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 specification N5 @p $ 4{format is: dev:<user>file.extension.version. Press the RETURN key if you O @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 >y5 R( 5
a5 @p 5Analyze Help Message: Time From Prompt RY5 @p S15# @p 5 Time From: Time To: SI5+ @p 5$ ***********!oooooooooooooooooooo!************ T952 @p 5, 02-Mar-81 09-Mar-81 U959 @p 53 18:30:45 23:30:01 V)5; @p W5C @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 prompt X95T @p " 5MAnalyze is waiting for you to specify the time at which you want the YA5Y @p 5Ufile 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
@p a6 @p # 6 3. Enter relative time. The format is: -dd where -dd is the number of a( @p 6 past days. To indicate today at 00:00:01 hours, type: -03.1.2.0.PA9h z 6 @p 5 Q`GS & cI6 G- cq6" d 6#
a6) @p 6$Analyze Help Message: Time To Prompt d96* @p e61 @p 6+ Time From: Time To: e)69 @p 62 ***********!oooooooooooooooooooo!*********** f6@ @p 6: 02-Mar-81 09-Mar-81 g6G @p 6A 18:30:45 23:30:01 h6H @p hq6Q @p # 6IAt this prompt Analyze is waiting for you to specify the time at whichi 6W @p 6Ryou want the file analysis to end. You can: j6X @p jq6a @p " 6Y 1. Press the RETURN key to default to the LATEST time in the file. k 6b @p l6k @p # 6c 2. Enter real time. The format is: dd-mmm-yy hh:mm:ss where dd is the l)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 only nA7 @p $ 6~ the date is specified, the default time is 1 second after midnight. oQ7 @p pa7 @p $ 7 3. Enter relative time. The format is: -dd where -dd is the number of px @p 7 past days. To indicate today at 00:00:01 hours, type: -0 z 7 @p 715 & ANALYZE REPORT s 7 G- sI7 s` 7!
a7& @p 7"Analyze Help Message: Report To Prompt t7( @p ti71 @p # 7)The Big Picture is still: Input - Process - Output. Remember, Analyze u7: @p # 72is designed to sort and classify the information contained in the local v7B @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 the x)7O @p
7Lreport file. You can: y97Q @p yy7Y @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 " 8 NOTE: 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 @p 8 ?7 * ANALYZE PACKETS18 G- q8" 8#
a8) @p 8$Analyze Help Message: Packets To Prompt 98* @p 83 @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 were 98E @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] @p 8Wspecify a destination for the packet file. You can:
a8^ @p Q8g @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 @p 8z @p " 8rn2.cEnterhyouroownouniquenfileespecifications(e.g., DSK:WEEKLY.PAK). 9 @p # 8{9 @ThefileNspecificationhformatois:vdev:<user>file.extension.version. !9 @p 199to translate the records listed in the packets. This should be done any @p 9"time you question a theory or the evidence that supports it.z 9+ @p 6^ ; , 9- G- 99. P 90
a95 @p 91 Analyze - Theory Descriptions97 @p Y9: @p 98Introduction q9; @p !9D @p " 9<Analyze attempts to localize the cause of intermittent disk and tape 99L @p " 9Esubsystem failures. It does this by reading the system event file and A9U @p " 9Mapplying two sets of (best guess) theories; one for disk subsystems, I9Z @p 9Vthe 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 the Q9 @p $ 9whardware and software, the information recorded in the system event file a: @p $ : being analyzed, and common sense. But, because the theories are based on q: @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.o z :N @p :J9q=Y R.T.3.1.2.0.rev_trans_theory_intro ) :P G- )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:e G- ,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 Theories 19; @p 2; @p ;Introduction 2); @p 2Y; @p ;There are 45 disk theories. The theories evaluate and attempt to 2q;' @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 @p 6;8 @p ;2 RH10, RH11, and RH20 disk controllers that use 6;9 @p 7;? @p ;: RP04, RP05, RP06, or RM03 disk drives. 7;@ @p 7q;B @p 8 ;C @p 8 @p ;DThe following menu lists the major Disk Theory categories. z ;p @p ;M#9b [ " 3.1.2.1.M. z ;U @p ;QfY:H R.T.3.1.2.0.rev_trans_disk_theory_intro 9q;W G- :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;r G- > ;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 @p I @p <JYour selection please (topic #): [=_ G- z <T @p <R09>w * 3.1.2.1.1.0. J<U G- JA<W JX <X
a<_ @p <Y Analyze - Disk Subsystem Unsafe Theories K <a @p Ky<d @p <bIntroduction L<e @p LA<n @p ! <fThe TOPS-10, TOPS-20 and VAX/VMS operating systems consider Unsafe LY<v @p ! <oErrors to be non-recoverable device errors. When a drive reports an Ma< @p " <wunsafe condition, the operating system places the drive off-line and Ni= @p = notifies the operator that manual intervention is required. Oq= @p Pi= @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 or R =! @p # =that are important to maintaining the integrity of the drive while it S=$ @p ="is spinning. T=& @p TI=. @p " ='Normally, in order to avoid reporting transient causes, the threshold Ta=7 @p # =/for reporting unsafe errors would be set at two or more. However, since Ui=@ @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 of X =L @p =Junsafe error. Y=N @p YH @p =OThe following menu lists the fourteen Unsafe Theories. z =y @p =W!Qs * 3.1.2.1.1.M.o z <N @p =[) @$ R.T.3.1.2.1.1.0.rev_trans_unsafe_intro Ii=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> @p a> @p >
0. Introduction a1> @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 @p n @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 it q? @p " ?has something to do with either the power distribution system or the r!? @p ?power supply. s)? @p sY?' @p ? AC Low/DC Low Error - Drive Power Supply Theory ... [1.1.1] sq?( @p tq?- @p ?) DP030(RP04/SN: 23) reports: u ?/ @p uY?3 @p
?0 4. AC-Low errors. uq?7 @p
?4 no DC-Low errors. v1?8 @p vq?> @p ?9 122. Total Retries (HARD and SOFT) w ?? @p wa?G @p ?@ Time: 2-Mar 10:31:28 TO 9-Mar 03:50:41 Span: 161:19:13 wy?H @p xq?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 ?jnyCe 3.1.2.1.1.1.A. }?m G- }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_a z =x @p @&[E R.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@? @p X @p
@@Your response please: A5 G- y@F G- 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 @p 3a
Y@h @p
q@o @p @ishAC4UsafePError:-5RP04pACtPower@Theory ... [1.1.1A] @xy. 1.tACUnsafe errors. q@| @p 1@~ @p IA @p @deTimeeofiError:P23-Nov22:03:03 aA @p 1AyHk 3.1.2.A.1.1.1.AqA G- 1A H A
aA( @p # A Background - This theory is associated with an AC low condition. Whenx @p A)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.A 1A7 X A8
aAA @p # A9STOP - You are moving in a reverse direction through the menu. You are AF @p ABabout to back into the AC Unsafe Theory.AH @p h @p
AIYour response please: (BE G- z AP @p A.E!B " YAQ G- AS AT
aA] @p $ AUTheory - If an RP04 drive detects a 30 Volts Unsafe condition, it points IAf @p ! A^to a bad DC power supply in the Vendor Logic portion of the drive. YAg @p aAj @p AhPACKET 1. yAk @p !As @p Al30 Volts Unsafe Error - RP04 DC Power Theory ... [1.1.1B] 9At @p 1Ay @p Au DP400 (RP04/SN: 5) reports: IAz @p A @p A{ 1. 30 Volts Unsafe errors. )B @p qB @p B @p B 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 " @p BRP04 drive. z B @p B YB^ 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.18p z AL @p BCIICG R.T.3.1.2.B.1.1.1.A ABG (X BH
aBQ @p # BISTOP - You are moving in a reverse direction through the menu. You are) BW @p BRabout to back into the 30 Volts Unsafe Theory. *BY @p *x @p
BZYour response please: 8yCL G- z Ba @p B>#IC +iBb G- ,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 @p Bwequipment..iBz @p /B} @p B{PACKET 4. /)B~ @p /QC @p BDC Unsafe Error - RP06 DC Power Theory ... [1.1.1C] /iC @p 0YC
@p C1ADP250 (RP06/SN:110000)oreports: 0qCerrors1YC @p 2!C @p 28 @p C Time of Error: 30-Nov 04:07:31 z C @p C +i:E
3.1.2.C.1.1.1.A3!C G- 3aC! 3x C"
aC+ @p " C#Thresholds - There are no thresholds associated with this theory. A 4)C2 @p C,report is produced for each DC Unsafe condition detected. 51C4 @p 6)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.1Qp z B] @p CI( @ R.T.3.1.2.C.1.1.1.A +QCM 9@ CO
aCW @p # CPSTOP - You are moving in a reverse direction through the menu. You are9qC^ @p CXabout to back into the DC Voltage Unsafe Theory. :yC_ @p ;` @p
C`Your response please: QyE G- z Cg @p CE}DP & <QCi G- <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 @p D Head Select Error - R/W Head Select Logic Theory ... [1.1.2] AD @p BD @p D DP010(RP06/SN: 55) reports: BD @p BiD @p D 6. NHS errors. CD @p D no MHS errors. CAD! @p DD& @p D" 12. Total Retries (HARD and SOFT)DD( @p DiD/ @p D) Time: 2-Mar 10:31:28 TO 9-Mar 03:50:41 Span: 161:19:13 ED1 @p EyD9 @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 a GDK @p # DCMHS error symptom. The report identifies the drive and lists the number H( @p DLof times each symptom occurred. z DT @p DR<QE 3.1.2.1.1.2.A. J DV G- JIDW J` DY
aD` @p DZBackgroundo-Two detectorsmonitorIhead selection:2 KDa @p LDj @p " Db NHSE- No Head Select monitorsthree signals: read, write, and head LDr @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{ @p O!E @p " D| MHS - Multiple Head Select monitor head select current and sets if O8 @p E two or more heads are center tapped at the same time.z E/ @p E
aE" @p # ESTOP - You are moving in a reverse direction through the menu. You areSE( @p E#about to back into the Head Select Theory. T!E) @p U @p
E*Your response please: o G G- Q1E0 G- UqE2 V E3
aE< @p $ E4Theory- If a drive reports a Transitions Unsafe or a Transition Detector V9EE @p $ E=Failure, then chances are the fault lies in the drive and has to do with WIEJ @p EFthe write clock timing logic. XYEK @p Y!ES @p EL R/W Transition Error - Clock Timing Logic Theory ... [1.1.3] Y9EU @p Z9EZ @p EV DP020(RP06/SN: 33) reports: ZQE[ @p [!E_ @p E\ 4. TDF errors. [9Ec @p E` no TUF errors. [yEe @p \9Ej @p Ef 21. Total Retries (HARD and SOFT)\QEk @p ]!Es @p El 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 `` @p Fof times each symptom occurred. z F @p FQ1Fs 3.1.2.1.1.3.A. bAF G- cF c F
aF$ @p F Background - Two detectors monitor write clock transitions: cIF% @p dAF. @p " F& TUF - Transitions Unsafe monitors two signals: write and write clock dYF6 @p F/ transitions. TUF sets if write is active without write clock eaF9 @p F7 transition. faF: @p gFC @p " F; TDF - Transition Detector Failure monitors for the case where write g)FL @p # FD clock transitions are true, but write is not. Among other things, this h1FT @p # FM is a clever way to assure that the write clock transition detector isiAFX @p FU working properly. jIFY @p kFb @p " FZNote: Write clock transitions are monitored by a timing detector. The kFk @p # Fctiming detector monitors the write clock to insure that it is occurring l @p # Flat the correct time intervals. The intervals are drive type dependent.z G @p FubAGu $ 3.1.2.1.1.4.g_tPACKET 5. z E- @p FzQyHp R.T.3.1.2.1.1.3.A.rev_trans_clk_timing_theory_a UYG p G
aG @p # GSTOP - You are moving in a reverse direction through the menu. You arep1G @p G
about to back into the Clock Timing Theory. q9G @p r @p
GYour response please: Hw G- n9G G- s G s G
aG% @p " G Theory - If a drive reports either a Current Sink Failure, a Current sQG. @p # G&Switch Unsafe, a Write Select Unsafe, or a Write Current Unsafe error tYG6 @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 or viGC @p G@the write current generators. wqGE @p x9GM @p ! GF R/W Control Error - R/W Current Control Logic Theory ... [1.1.4] xQGO @p yYGT @p GP DP120(RP06/SN: 43) reports: yqGU @p zAGY @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 @p Gh 10. Total Retries (HARD and SOFT)|qGm @p }@ @p Gn Time: 2-Mar 10:31:28 TO 9-Mar 03:50:41 Span: 161:19:13 z Gy @p Gwn9J) $ 3.1.2.1.1.4.A. ~QGz G- 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 @p Hthe number of times each symptom occurred. yH @p YH% @p H Background - Four detectors monitor write current:qH' @p YH/ @p # H( CSF - Current Sink Failure monitors the write current and sets if theqH7 @p H0 current does not shut off at the end of the write operation. yH9 @p yHA @p H: CSU - Current Switch Unsafe monitors the write current for each HI @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 @p HU detectors sense write current at the same time.
AH\ @p )Hd @p ! H] WCU - Write Current Unsafe monitor write current and sets if write @ @p He current is sensed during a non-write operation. z I @p HmqIk $ 3.1.2.A.1.1.4t_PACKET 8. z G @p Hro K= R.T.3.1.2.1.1.4.A.rev_trans_r_w_current_theory_a rqHy x Hz
aI @p # H{STOP - You are moving in a reverse direction through the menu. You are)I
@p Iabout to back into the R/W Current Control Logic Theory. 1I
@p ( @p
I responseplease: 9Ip G- I
aI @p " ITheory.-.If a driveqdetects a Write Ready Unsafe condition, it could aI' @p $ I point to a bad servo amplifier, a bad cylinder detector and/or bad write iI0 @p # I(counter circuits in the SS board of the DCL, or bad write control logic yI6 @p I1in the Vendor Logic portion of the drive. I8 @p iI9 @p FwI; @p IB @p I< WRU Error - Head to Cylinder Position Theory ... [1.1.4A]1ID @p )II @p IE DP250 (RP06/SN: 10000) reports: AIJ @p IO @p IK 1. Write Ready Unsafe errors. )IQ @p yIR @p IW @p IS Time of Error: 30-Nov 04:07:31 )IY @p yIb @p $ IZThreshold - There are no thresholds associated with theory. It produces @p Ica report for every write ready unsafe condition detected. 3.1.2.1.1.5.1.17H z I @p Im
aI{ @p # ItBackground - Whenever a write command is being executed, the heads are 1J @p I|to be within a certain range relative to the cylinder. If this 8 @p Jspecified range is exceeded, the error occurs. z J @p J
LL R.T.3.1.2.A.1.1.4.A !!J G- !iJ " J
aJ @p # JSTOP - You are moving in a reverse direction through the menu. You are"1J" @p J about to back into the Write Ready Unsafe Theory. #9J# @p $ @p
J$Your response please: 7QKA G- z J+ @p Ii~QJz %J- G- %9J. %P J0
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 @p JJbad servo head or bad servo track. )JP @p )iJQ @p Hn*JS @p *J[ @p ! JT PLO Error - R/W Phase Locked Oscillator Drive Theory ... [1.1.5] *1J] @p +9Jb @p J^ DP000 (RP06/SN: 492) reports: +QJc @p ,!Jk @p Jd 2. PLO errors on different media or different cylinders of ,9Jo @p
Jl the same media. -9Jq @p -yJr @p . @p Js Time: 17-Mar 01:00:00 TO 17-Mar 03:00:00 Span: 1:59:60 z J~ @p J|%Li 3.1.2.1.1.5.A /)K G- /iK 0 K
aK @p ! KThreshold - There are no overt thresholds associated with this this 01K @p $ K
theory. However, because of the very nature of it (i.e. there have to be 19K @p $ Kat least 2 errors occurring at different places), its inherent threshold 2IK @p b3YK @p 3qK) @p $ K!Background - The PLO is the controller that sets the timing sequence for 4 K2 @p ! K*passing of data (on either a read or write operation). This error 5 @p % K3occurs when the drive detects the loss of synchronization within the PLO. 3.1.2.A.1.1.5.5I@ z J' @p K?M^ R.T.3.1.2.1.1.5.A $yKC 8 KD
aKM @p # KESTOP - You are moving in a reverse direction through the menu. You are8IKR @p KNabout to back into the PLO Drive Theory.9QKT @p :( @p
KUYour response please: IILQ G- z K\ @p K: 9L* $ ;K] G- ;AK_ ;X K`
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 @p Ksmedia. >!Kv @p >IKx @p KwPACKET 9. >aKz @p ? L @p " K{ PLO Error - R/W Phase Locked Oscillator Media Theory ... [1.1.5A] ?!L @p @)L @p L DP250 (RP06/SN: 735) reports @AL
@p AL @p $ L 2. PLO errors occurring on the same media with all errors on the same A)L @p L cylinder.B9L @p BiL @p L Media ID: PS1 CL @p L Cylinder: 768 C9L @p CqL" @p D @p L# Time: 23-Nov 08:58:00 TO 28-Oct 08:58:00 Span: ***:00:00 z L. @p L,;AM 3.1.2.A.1.1.5.AE!L/ G- EaL1 Ex L2
aL; @p # L3Threshold - There have to be at least 2 errors occurring in this manner F)LA @p L<in order for the theory to be called out. G9LC @p H @p LDBackground - Refer to background for the PLO Drive Theory. 3.1.2.1.1.6.1.1[X z KX @p LN!!BA R.T.3.1.2.A.1.1.5.A ;LR J LT
aL\ @p # LUSTOP - You are moving in a reverse direction through the menu. You areJALb @p L]about to back into the PLO Media Theory.KILc @p L @p
LdYour response please: [aMb G- z Lk @p LJ/)M( MLm G- M9Ln MP Lp
aLx @p " Lq If an RP06 drive detects a Write and Offset error, it could point to NM @p $ Ly a bad DCL register board, or bad drive command logic in the Vendor Logic O M @p M portion of the drive. PM @p PYM @p MPACKET 6. PqM @p QM @p " M
Write and Offset Error - RP06 Write and Offset Theory ... [1.1.6] Q1M @p R9M @p M DP110 (RP06/SN: 520) reports: RQM @p S!M @p M 1. Write and Offset errors.S9M! @p TM# @p T @p M$ Time of Error: 4-Sep 01:30:49 z M, @p M*MM{
3.1.2.1.1.6.A UM- G- UAM/ UX M0
aM9 @p ! M1Threshold - There are no thresholds associated with this theory. A V MA @p " M:report is produced for every Write and Offset error that is detected. WMC @p XMK @p MDBackground - A programmed offset is only allowed during a read X1MS @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.6r0 z Lg @p M`7QO R.T.3.1.2.1.1.6.A LyMd \( Me
aMn @p # MfSTOP - You are moving in a reverse direction through the menu. You are\YMt @p Moabout to back into the Write and Offset Theory. ]aMv @p ^H @p
MwYour response please: r9O G- z M~ @p M[UN? _9M G- _aN _x N
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 @p bIN @p NPACKET 1. baN @p c N" @p N Velocity Unsafe Error - Head Load Speed Theory ... [1.1.7] c!N# @p d!N( @p N$ DP400 (RP04/SN: 5) reports:d9N) @p eN. @p N* 1. Velocity Unsafe errors eN/ @p eaN5 @p N0 Take drive offline and call Field Service.eyN7 @p fYN8 @p fqN= @p N9 Time of Error: 23-Nov 22:03:03 g @p z NC @p NA_9O1 3.1.2.1.1.7.A gqND G- h1NF hH NG
aNP @p $ NHThresholds -yThere arenoNthresholds associatedwithBthisrtheory.WhSince hyNX @p NQitoisesuchhaiserious condition,dtheNdrive#becomes immediately j N] @p y are supposed to. If the detected speed of lqNy @p # Nqthe heads at any particular point is too fast for the maximum speed set nO @p " Nzfor that point, a Velocity Unsafe condition occurs. The unsafe light oO
@p # Oin the console will then go on and the drive is no longer available for p @p O use by the system. This condition is unique to RP04's.3.1.2.1.1.8.1.7 P z Mz @p O[aPM R.T.3.1.2.1.1.7.A _!O s O
aO# @p # O STOP - You are moving in a reverse direction through the menu. You ares1O* @p O$about to back into the Velocity Unsafe Theory. t9O+ @p u @p
O,Your response please: YPR G- z O3 @p OgqO~ " vO5 G- v9O6 vP O8
aO@ @p " O9Theory - If an RP04 drive detects a Pack Speed Unsafe condition, it wOI @p " OApoints to a variety of causes: loss of phase to the primary power, a x OQ @p # OJbad drive motor, a broken drive belt, or a bad servo mechanism. FieldyOW @p ORService should be notified immediately. zOX @p zqO[ @p OYPACKET 1. { O\ @p {1Oc @p O] PSU Error - RP04 Pack Speed Theory ... [1.1.8] {IOd @p |1Oi @p Oe DP400 (RP04/SN: 5) reports:|IOj @p }Oo @p Ok 1. Pack Speed Unsafe errors})Op @p }qOv @p Oq Take drive offline and call Field Service.~ Ox @p ~iO} @p Oy Time of Error: 23-Nov 22:03:03 @p z P @p P vPk 3.1.2.1.1.8.A iP G- )P @ P
aP @p " PThresholds - There are no thresholds associated with this theory. It qP @p $ Ppoints to an extremely serious condition and makes the drive unavailable yP @p
Pto the Operating System. P @p IP& @p ! P Background - There are two conditions that have to be maintained in aP, @p P'order to keep this error from occurring:iP- @p AP6 @p # P.The pack speed has to be AT LEAST 70% of the normal operating speed and YP? @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 is p @p PIconfined to RP04's 3.1.2.1.1.9.1.8h z O/ @p POr9QR R.T.3.1.2.1.1.8.A uyPS
PU
aP] @p # PVSTOP - You are moving in a reverse direction through the menu. You are
QPd @p P^about to back into the Pack Speed Unsafe Theory. YPe @p
@ @p
PfYour response please: qQ^ G- z Pm @p PKiQ"
aPz @p PsTheoryT-mIfgaEdrive-detectsTamDriveoTimingeError,.it1indicatesa !Q @p P{hardware failurePin0thePdrive:timingelogic. !Q @p Q @p QPACKET 7. Q @p AQ
3.1.2.1.1.9.A !Q' G- aQ) x Q*
aQ3 @p " Q+Thresholds -There are no thresholds associated with this theory. A )Q9 @p Q4report is produced for each error that occurs. 1Q; @p QD @p # Q<Background - When a write or read is enabled, the heads need to receive 1QL @p " QEan index and a sector pulse in order to execute the command properly. @ @p QMIf these are not available, the error occurs.z QU @p Qx YSG )Q} G- = z Pi @p QYZ)SJ F.T.3.1.2.1.2.1.fwdtransservosystheory
aQj @p # QbThat's it. There are only fourteen unsafe theories. Next on the menu is Qn @p
Qkthe servo system theory. !Qo @p ` @p
QpYour response please: z R @p QuZQR| & 3.1.2.1.2.1.nt_system:a R.T.3.1.2.1.1.9.A.rev_trans_r_w_current_theory_a QQ X R
aR @p # RSTOP - You are moving in a reverse direction through the menu. You are R @p R
about to back into the unsafe theories. !R @p !h @p
RYour response please: 9)SP G- 9R G- "YR "p R
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 @p R,do with either the servo mechanism or the servo control logic. %9R5 @p &9R; @p R6 Servo Error - Servo System Theory ... [1.2.1] &QR= @p '9RB @p R> DP020(RP04/SN: 22) reports: 'QRC @p (!RG @p RD no SKI errors. (9RK @p RH 3. OCYL errors. (yRM @p )9RR @p RN 12. Total Retries (HARD and SOFT))QRS @p *!R[ @p RT 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 -` @p Rxof times each symptom occurred. z S @p R~ 9Se 3.1.2.1.2.1.A. /AS G- 0S 0 S
aSp " SBackground - Two error detectors monitor the performance of the servo 0IS @p Qw1QS @p 1iS @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' @p S" detector is not incorporated in RM03 drives.4S( @p 4qS1 @p " S) SKI - Seek Incomplete monitors the amount of time that it takes the 5 S9 @p ! S2 servo to complete a positioning operation. SKI is set if the servo 6SB @p " S: is unable to complete the positioning operation within a prescribed 7 @p SC amount of time. Typically 100 m/s.z Sn @p Si)Tx Topic Menuz R @p SLqWr F.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_ @p S]the OPI theories. ;ASa @p ;x @p
SbYour response please: z T
@p Sg/AUD $ 3.1.2.1.3.0.heoiX R.T.3.1.2.1.2.A.rev_trans_servo_sys_theory_a 8qSo G- =aSq =x Sr
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)T T
aT @p Tng (theoryAnalyze.- DiskaSubsystem OPIHTheories AqT @p BYT @p TIntroduction BqT @p C!T$ @p " T The@timingTforaboth aosearchrandla dataotransfer operationucomesmfrom C9T, @p " T%the mediumT(servotrack).andRisdusedWthroughoutntheidriveito control DAT5 @p " T-thegoperation.pAnOPI error,atherefore,(couldsbeccausedsbyweithertthe EIT> @p $ T6mediumh(theory 1.3.1), or by the controlnlogicethat distributesaandcuses FQTB @p did not occurM @p Tq within three Index pulses.z U @p UiWn occurred.oz T @p Tz8qVN R.T.3.1.2.1.3.0.revtransopiintroAT O` U
aU @p # USTOP - You are moving in a reverse direction through the menu. You arePU @p U
about to back into the Introduction to the OPI theories. QU @p R @p
UYour response please: iaVU G- 3.1.2.1.3.M. NIU G- SU S0 U
aU% @p U Analyze - Disk Subsystem Operation Incomplete Theories SaU' @p TYU* @p U(Topic Menu: TqU+ @p U!U/ @p U, 0. Introduction U9U0 @p UqU5 @p U1 1. Media OPI Theory ...[1.3.1] V U7 @p VYU< @p U8 2. Drive OPI Theory ...[1.3.2] VqU= @p WAU? @p WX @p U@Your selection please (topic #): z UH @p UF<QVI , 3.1.2.1.3.1. XAUI G- YUK Y UL
aUU @p $ UMTheoryo-hIftardisk.subsystem@reports Operation Incompleteerrors,iand if YIU^ @p # UVtheaerrors0involveatwo1or:more3drives,@and if theyVarepassociatedewithZYUf @p a U thedsame5medium,Pcylinder,atrackqandesector,tthen thereVis@a good[aUl @p Ugchancerthatmthe mediumeiswcausingrthererrors.\aUm @p ]AUs @p Une OPIuErroro- MediaaTheoryi...a[1.3.1] ]YUt @p ^1U} @p # UuV: @MediaID:eOPER1a-dCyl:.33., Trk:r4.,dSect:i12.twasmidentifiednwith^IV @p U~VB @no Hard;andt6. SofteOPI errorseon QV @p rst detected the error.g)VC @p h @p VDBackground - Refer to the OPI Introduction. z Vm @p VKXATt . 3.1.2.1.3.2.heo ( z U @p VPOX R.T.3.1.2.1.3.1.revtransmediaopitheory RiVV jP VX
aV` @p # VYSTOP - You are moving in a reverse direction through the menu. You arekVf @p Vaabout to back into the Media OPI Theory.l Vg @p l` @p
VhYour response please: ~!Wx G- iVn G- mQVp mh Vq
aVz @p $ VrTheory - If a drive reports multiple Operation Incomplete errors, and if nW @p # V{those errors are not associated with a particular medium, then chanceso)W
@p # WarenthelfaultrliesninHtheedrivedandehasisomethingtopdo withthetiming p1W @p WDrive Timing Logic Theory ... [1.3.2] rIW @p s9W" @p W DP210(RP04/SN: 21) reports: sQW' @p W# 2. Hard and no Soft OPI errors. t!W) @p tyW. @p W* 24. Total Retries (HARD and SOFT)uW/ @p uaW7 @p W0 Time: 2-Mar 10:31:28 TO 9-Mar 03:50:41 Span: 161:19:13 uyW8 @p vqWA @p $ W9Threshold - At least 1 Hard or 5 Soft OPI errors are required to satisfy w WJ @p % WBthis theory. The errors must pertain to the same drive. If multiple drives xWS @p " WKare reported, check to see if theory 1.3.1 has also seen the errors. y)WX @p WTThe problem may be a faulty media. z1WY @p {Wb @p " WZThe report identifies the drive and lists the number of hard and soft {Wf @p WcOPI errors the drive detected.|!Wh @p |h @p WiBackground - Refer to the OPI Introduction. z X/ @p WpNIYc 3.1.2.1.4.0.ry z Vk @p Wt9)\9 F.T.3.1.2.1.4.0.fwdtransmbcbintro m9Wz W{
aX @p " W|That's it. There are only two OPI theories. Next on the menu are the 9X
@p XMassbus (control bus) parity error theories. AX @p @p
X
Your response please: z X @p XiaY R.T.3.1.2.1.3.2.rev_trans_dr_opi_theory yX G- aX x X
aX# @p # XSTOP - You are moving in a reverse direction through the menu. You are)X( @p X$about to back into the OPI theories. 1X* @p @p
X+Your response please: QY G- }aX1 G- yX2 X4
aX; @p X5 Analyze - Disk Subsystem Massbus Control Bus Theories AX= @p 9X@ @p X>Introduction QXA @p XJ @p ! XBRH10 and RH20 controllers have a single bit: Register Access Error XS @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_ @p X]read or write. AX` @p qXi @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 setzof7theoriesYattempt to localize4the causeXof@Massbus(controlAYT.3.1.2.1.4.0.revtransmbcbintro aY 8 Y
aY' @p # Y STOP - 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
Y2Your responseGplease: 0Y[ Y;
aYC @p Y< Analyze - Disk Subsystem Massbus Control Bus Theories 9YD @p 1YF @p SIIYG @p aYK @p YH 0. Introduction yYL @p 1YS @p YM 1. Massbus (control bus) RH Theory ...... [1.4.1]IYT @p 1Y[ @p YU 2. Massbus (control bus) Drive Theory ... [1.4.2] IY] @p d9Y^ @p P @p Y_Your selection please (topic #): z Yg @p Ye}aZB 3.1.2.1.4.1. 9Yi G- yYj Yl
aYu @p $ YmTheory - If a disk subsystem reports Massbus (control bus) parity errors AY~ @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! @p Z RH CBUS Error - Massbus (control bus) RH Theory ... [1.4.1] #Z" @p $Z& @p Z# RH No: 3. reports: $)Z( @p $iZ- @p Z) 5. Massbus Control Bus Errors.%Z2 @p Z. 2. different drives were involved. %QZ4 @p &)Z9 @p Z5 24. Total Retries (HARD and SOFT)&AZ: @p ' @p Z; Time: 2-Mar 10:31:28 TO 9-Mar 03:50:41 Span: 161:19:13 z ZF @p ZD 9[ 3.1.2.1.4.1.A. (!ZG G- (aZI (x ZJ
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 @p Tv.YZx @p .p @p ZyBackground - Refer to the Massbus (control bus) Introduction. z [& @p [(![| 3.1.2.1.4.2.raeinvolved. z Y5 @p [Q\5 R.T.3.1.2.1.4.1.A.rev_trans_mb_cb_rh_rae_theory_a Y[ 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 [! @p 3x @p
["Your response please: G\@ G- 0 [( G- 4i[) 5 [+
a[4 @p $ [,Theory - If a disk subsystem reports Massbus (control bus) parity errors 51[= @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 the 8Y[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:13 z \ @p [~0 Y 3.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 satisfy AY\ @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\- @p E@ @p \.Background - Refer to the Massbus (control bus) Introduction. z \8 @p \]0Y^ FY\b G- z [% @p \;~!i{ F.T.3.1.2.1.5.0.fwd_trans_mb_db_intro 4Q\A H \C
a\K @p " \DThat's it. There are only two Massbus (control bus) theories. Next on H1\S @p \Lthe menu are the Massbus (data bus) parity error theories. I9\T @p J0 @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_a G\d L( \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 @p Nh @p
\yYour response please: c9^" G- K \ G- OY] Op ]
a] @p ] Analyze - Disk Subsystem Massbus (data bus) Theories P!] @p Q] @p $ ]
Introduction - Both Massbus controllers and Massbus devices check parity Q1] @p # ]on the Massbus (data bus). The parity is checked during read and writeRA]! @p ] operations as illustrated below. SI]# @p T]( @p ]$ DF10C RH10 Massbus DeviceT1]. @p ]) <read --- DPE <--------- no ck <--- disk U]4 @p ]/ write>--- no ck ----------> PAR ---> disk Ua]5 @p VA]: @p ]6 UBA RH11 Massbus DeviceVY]@ @p ]; <read --- DPE <--------- no ck <--- disk W)]F @p ]A write>--- no ck ----------> PAR ---> disk X ]H @p Xi]M @p ]I MBox RH20 Massbus DeviceY]S @p ]N <read --- DPE <--------- no ck <--- disk YQ]Y @p ]T write>--- DPE ----------> PAR ---> disk Z1]Z @p []\ @p [)]d @p ! ]]This set of six Massbus (data bus) theories attempt to localize the [A]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. ^]w G- ^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 data a8 @p ^operations. z ^= @p ^ j6 ( 3.1.2.1.5.M. z \| @p ^ FY`X R.T.3.1.2.1.5.0.rev_trans_mb_db_intro OA^# 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 @p f` @p
^8Your response please: `_ G- by^> G- gQ^@ gh ^A
a^I @p ^B @p Analyzeq- Disk SubsystemrMassbusi(dataebus)(Theories h^J @p i^M @p ^KTopic5Menu: i)^O @p iY^R @p ^P 0. Introduction iq^T @p j)^\ @p ^U 1. Data Read/Massbus (data bus) RH Theory ............[1.5.1] jA^] @p kA^e @p ^^ 2. Data Read/Massbus (data bus) Drive Theory .........[1.5.2] kY^g @p lY^o @p ^h 3. Data Write/Massbus (data bus) MBox (UBA) Theory ...[1.5.3] lq^p @p mq^x @p ^q 4. Data Write/Massbus (data bus) RH Theory ...........[1.5.4] n ^z @p o @p ^{ 5. Data Write/Massbus (data bus) RH Theory ...........[1.5.5] o! @p p! @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 errors sA_- @p ! _%during data reads, and if the errors involve multiple drives, then tI_5 @p " _.chances are the fault lies in the controller. If, however, the errors uQ_> @p " _6involve a single drive then, chances are the fault lies in the drive vY_E @p _?and has something to do with the Massbus interface logic. wa_G @p xY_O @p ! _H RH DPE Error - Data Read/Massbus (data bus) RH Theory ... [1.5.1] xq_Q @p yy_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:13 z _w @p _ur9`S 3.1.2.1.5.1.A. ~9_y G- ~y_z _|
a` @p $ _}Threshold - At least two (controller detected) Massbus (data bus) parity A` @p # `errors are required to satisfy this theory. The errors must involve two Q` @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 drives q`( @p " ` that were involved. The report also lists the number of Massbus (data y`- @p `)bus) parity errors that occurred. `. @p Q`0 @p i`5 @p `1MBox/UBA RHxx Massbus Device `7 @p Y`= @p `8 <read --- DPE <---------.- no ck <--- disk q`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~9aP 3.1.2.1.5.2.rd_Bad Spots.z ^; @p `Zc9b R.T.3.1.2.1.5.1.A.rev_trans_mb_db_rh_rd_theory_a g9`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 Massbus (data bus) RH Theory.
`tYour response please: #qb& G-
1`z G- `| ( `}
aa @p " `~Theory - If a disk subsystem reports Massbus (data bus) parity errors Ya @p ! aduring data reads, and if the errors involve multiple drives, then aa @p " achances are the fault lies in the controller. If, however, the errors ia @p " ainvolve a single drive then, chances are the fault lies in the drive qa' @p a and has something to do with the Massbus interface logic. ya( @p qa1 @p ! a) RH DPE Error - Data Read/Massbus (data bus) Drive Theory [1.5.2] a2 @p a8 @p a3 DP020(RP04/SN: 33) was identified with )aA @p ! a9 3. (RH detected - Data Read) Massbus (data bus) Parity Errors. aB @p aG @p aC 24. Total Retries (HARD and SOFT) )aI @p x @p aJ Time: 2-Mar 10:31:28 TO 9-Mar 03:50:41 Span: 161:19:13 z aT @p aR
1b 3.1.2.1.5.2.A. aV G- IaW ` aY
aab @p # aZThreshold - One or more (controller detected) Massbus (data bus) parity ak @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. The 1a| @p # aureport identifies the drive and lists the number of Massbus (data bus) Ab @p a}parity errors that occurred. Ib @p b @p bMBox/UBA RHxx Massbus Device )b @p !b @p b
<read --- DPE <--------- no ck <--- disk !b @p !yb @p " @p bBackground - Refer to the Massbus (data bus) Introduction. z b@ @p b c- " 3.1.2.1.5.3.rd_medium.a z `w @p b! d R.T.3.1.2.1.5.2.A.rev_trans_mb_db_dr_rd_theory_a yb( $h b)
ab2 @p # b*STOP - You are moving in a reverse direction through the menu. You are %b9 @p b3about to back into the Massbus (data bus) Drive Theory. &!b: @p ' @p
b;Your response please: C9d# G- #!bA G- (bC ( bD
abM @p " bETheoryE-rIf a systemrreportssMassbust(data)bus)xparity errors during] (IbU @p ! bNdataYwrites,andif those errorseinvolveomultiplescontrollers,rthen )Qb] @p p bVchances are the faulthas to6doMwithuthedmemoryscontrollerrorrthe *Ybe @p p b^channel.@If,however,.theterrorsrinvolveRa singleFcontroller and +Ybn @p " bfmultiple:drives, then1chances areathe3fault1liesain the:controller1or ,Ybv @p " bothe.Massbus.3Finally,3if the errorscinvolve a single drive,then the -ab @p # bwfault is probably in the drive and has something to do with the Massbus .ic @p c interface logic. /yc @p 01c
ac? @p $ c7Threshold - At least two (controller detected) Massbus (data bus) parity 6acH @p # c@errors are required to satisfy this theory. The errors must involve two 7qcP @p cIor more controllers and they must have occurred during data write 9cX @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 @p cf MBox RH20 Massbus Device <Ycl @p =1cr @p cm .--> DPE ----------> PAR ---> disk =Ict @p \\ >)cz @p cu `--> DPE ----------> PAR ---> disk >Ac{ @p ?!d @p $ c|Since RH10s and RH11s do not check parity during a data write operation, ?9d
@p dthistheory onlyAapplies toRH20ccontrolledRdiskdsubsystems. @Id(data bus)&Introduction. z d= @p d 5Ye) " 3.1.2.1.5.4.xwbad spots.z b> @p d #qf
ad. @p # d'STOP - You are moving in a reverse direction through the menu. You are Dad6 @p d/about to back into the Massbus (data bus) MBox (UBA) Theory. Eid7 @p F` @p
d8Your response please: aQf G- Bid> G- GQd@ Gh dA
adJ @p " dBTheory - If a system reports Massbus (data bus) parity errors during HdR @p ! dKdata writes, and if those errors involve multiple controllers, then I!dZ @p dSchances are the fault has to do with the memory controller or the J)db @p d[channel. If, however, the errors involve a single controller and K)dk @p " dcmultiple drives, then chances are the fault lies in the controller or L)ds @p " dlthe Massbus. Finally, if the errors involve a single drive, then the M1d| @p # dtfault is probably in the drive and has something to do with the Massbus N9e @p d}interface logic. OIe @p Pe
@p " e RH DPE Error - Data Write/Massbus (data bus) RH Theory ... [1.5.4] Pe @p Q!e @p e
RH No: 4. reports: (during Data Write operations) Q9e @p e 3. (RH detected) Massbus (data bus) Parity Errors. R)e @p S!e @p e 24. Total Retries (HARD and SOFT) S9e" @p T @p e# Time: 2-Mar 10:31:28 TO 9-Mar 03:50:41 Span: 161:19:13 z e- @p e+ Bif " 3.1.2.1.5.4.A. Ue/ G- UYe0 Up e2
ae; @p $ e3Threshold - At least two(controllerfdetected) Massbus (data bus) parity V!eD @p # e<errors areerequiredtoSsatisfy1thisntheory. Thenerrorscmustrinvolveithe W1eL @p o eEsame controller andtwohor morerdrives.aAlsoetheoerrorscmustohave XAeQ @p eMoccurred@during datafwrite operations. YAeS @p ZeT @p Z1eY @p eUMBoxs) IntrRH20tiMassbus f.Device ZIe[ @p [ea @p e\write> --- DPE --------->-- PAR ---> disk [1ee @p
Ug" & 3.1.2.1.5.5.wr_ / \ z d; @p f C9h R.T.3.1.2.1.5.4.A.rev_trans_mb_db_rh_wr_theory_a G9f bH f
af @p # fSTOP - You are moving in a reverse direction through the menu. You are byf' @p f!about to back into the Massbus (data bus) RH Theory. df( @p dp @p
f)Your response please: h G- af/ G- eaf1 ex f2
af; @p " f3Theory8- IfravsystemcreportssMassbusa(datasbus)rparityrerrors during@ f)fC @p ! f<datadwrites,tandiifsthose errorseinvolvegmultiple controllers,then g1fK @p R fDchances are theTfaulthas to do with the memory controllerMor the h9fS @p fLchannel.1If,phowever,1the3errors involvega single controller5and i9f\ @p " fTmultiple drives, then chancesare the fault lies in the controller or j9fd @p " f]the Massbus. Finally, if the errors involve a single drive, then the kAfm @p # fefault is probably in the drive and has something to do with the Massbus lIfq @p fninterface logic. mYfr @p nft @p n)f| @p " fu RP PAR Error - Data Write/Massbus (data bus) RH Theory ... [1.5.5] nAf~ @p oIg @p f RH No: 4 reports: (during Data Write operations) oag
ag4 @p $ g,Threshold - At least two1drive detected Massbus (data bus) parity errors u1g< @p " g5(PAR) areYrequired toxsatisfylthisstheory.vTheserrors must havetbeen vAgE @p $ g=detectedsby twohor@more drivessandetheyamustebetcommon,toHthe sameRdiskc wIgN @p # gFcontroller. Thehreport identifies the controller, the number of drives xYgW @p # gOthat were involved, and the number of drive detected Massbus (data bus) yag[ @p gXparity errors that occurred. zqg] @p {9g^ @p {Qgc @p gMBox/UBA RHxx Massbus Device {ige @p |9gk @p gf write> --- DPE --------->-- PAR ---> disk |Qgo @p
@p h
@p ( @p he Massbus (data bus) Introduction. z h9 @p h t)i) $ 3.1.2.1.5.6.wrrecovery. z f, @p h aQj R.T.3.1.2.1.5.5.A.revtransmbdbrhwrtheory2a eIh! h#
ah+ @p # h$STOP - You are moving in a reverse direction through the menu. You are 1h2 @p h,about to back into the Massbus (data bus) RH Theory. 9h4 @p ( @p
h5Your response please: 1i G- 9h; G- h< 0 h>
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, then ihW @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 or qhp @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 Massbus h| @p hzinterface logic. h~ @p Ih @p ai @p $ i RP PAR Error - Data Write/Massbus (data bus) Lone Drive Theory [1.5.6] yi
@p i @p i DP020(RP06/SN: 32) reports: (during Data Write operations) !i @p i 8. (drive detected) Massbus (data bus) Parity Errors. !i @p i @p i 24. Total Retries (HARD and SOFT) 1i! @p @p i" Time: 2-Mar 10:31:28 TO 9-Mar 03:50:41 Span: 161:19:13 z i- @p i+ 9^ 3.1.2.1.5.6.A. i. G- Qi0 h i1
ai: @p ! i2Threshold - One or more (drive detected) Massbus (data bus) parity iC @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 @p 9iR @p iNMBox/UBA RHxx Massbus Device QiS @p !iY @p iT write> --- DPE ----------->PAR ---> disk 9i[ @p i\ @p 1ie @p $ i]Since all Massbus devices check data parity during data write operations Iin @p # ifthis theory applies to RH10, RH11, and RH20 controlled disk subsystems. Yip @p iiq @p @p irBackground - Refer to the Massbus (data bus) Introduction. 3.1.2.1.6.0.5.6 c z h8 @p i}G
y F.T.3.1.2.1.6.0. j x j
aj @p # jThat's it. There are only six Massbus (data bus) parity error theories. )j @p j
Next on the menu are the Read Data Theories. !9j @p " @p
jYour response please: z j @p j n R.T.3.1.2.1.5.6.A "qj G- #9j #P j
aj( @p # j!STOP - You are moving in a reverse direction through the menu. You are $j/ @p j)about to back into the Massbus (data bus) Theories. % j1 @p %x @p
j2Your response please: c!n G- z j9 @p ixbyk &ij: G- 'j< '( j=
ajE @p j> 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 @p jPerrors. A read data error is defined as: )qjV @p *IjZ @p
jW 1.(DCK1-2data.check *aj[ @p +!j @p j\ 2. FER- format error +9ja @p +yjg @p jb 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 @p k
ak @p $ kThe Media theories attempt to localize the read data errors to media bad 29k% @p " k spots. The theories look for single sector bad spots; circumferential 3Ik- @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 examples 7ykM @p kIillustrate each type of bad spot. 9kN @p 9QkW @p ! kO sector cly 000 <--------49---50---51--------< Hub 9ikZ @p kX :qka @p k[ -----X----- Radial Bad Spot 4 2 3 ;)kg @p kb / \ Soft Hard Soft <kl @p kh 3 12 <qkr @p km Hard Soft =Akx @p ks sector >!k{ @p ky Single Sector ?l @p " k| Bad Spot cyl 263-------5----6-----------------cyl 263 ?1l @p @9l @p l Circumferential 7 5 @P @p l
Bad Spot Soft Hard z l @p l 11m ( 3.1.2.1.6.0.B. Bl G- BYl Bp l
al" @p # lThe following diagram illustrates that errors considered by the Single C!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, errors E1l< @p # l4considered by the Circumferential Bad Spot Theories are also considered F1lD @p l=by the Radial Bad Spot Theories, but not the Single Bad Theories. GAlE @p HAlI @p
lF All Read Errors HYlM @p lJ lj ! IlQ @p lN @p .!. IQlV @p lR ! ! Jl[ @p lW Single Bad Circumferential Jal` @p l\ Spot Theories Bad Spot Theories K1le @p la !! L li @p
ln Spot Theories MYls @p Nl{ @p # ltNote: Errors that are reported as Single Bad Spots and errors that are N1m @p " l|reported as Circumferential Bad Spots may also be reported as Radial O8 @p `Vz m @p m Bo. , 3.1.2.1.6.0.C. PYm G- Qm
Q0 m
am @p # mThe following diagram illustrates how the read errors are processed by Qam @p # mthe Drive Theories. The errors are processed on a drive by drive basis. Rim! @p Sym& @p m" All Read Errors Tm+ @p m' .__________!_________. Tam0 @p m, ! ! U1m5 @p m1 Single Head Multi Head Vm; @p m6 .____!_____. .______!______. VYmA @p m< ! ! ! ! ! W9mG @p mB Offset Not Odd Even Common XmM @p mH Corrected Offset Head Head Logic XymS @p mN Corrected !______!______! YYmX @p mT ! Z9m^ @p mY 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,torTCommoniLogicsTheoriesswilltalso be@reported `1n @p ! nror. 3.1.2.1.6.M.6.0 5x z j5 @p n "qs0 R.T.3.1.2.1.6.0.C. &Qn ch n!
an* @p # n"STOP - You are moving in a reverse direction through the menu. You are dn2 @p n+about to back into the Introduction to the Data Error Theories. e!n3 @p f @p
n4Yournresponse please: 6s4 G- z n; @p n!
anG @p nA Analyze - Disk Subsystem Read Data Error Theories Menu hnI @p hynL @p nJ 0. Introduction inN @p iInU @p nO 1. Single Drive Radial Bad Spot Theory ............[1.6.1] ian] @p nV 2. Multi Drive Radial Bad Spot Theory ............[1.6.2] jYnd @p n^ 3. Multi Drive Single Sector Bad Spot Theory .....[1.6.3] kQnl @p ne 4. Single Drive Single Sector Bad Spot Theory .....[1.6.4] lIns @p nm 5. Multi Drive Circumferential Bad Spot Theory ...[1.6.5] mAn{ @p nt 6. Single Drive Circumferential Bad Spot Theory ...[1.6.6] n9o @p n| 7. Single R/W Head Theory .........................[1.6.7] o1o
@p o 8. Single Head Alignment Theory ...................[1.6.8] p)o @p o 9. Common Read Logic Theory .......................[1.6.9] q!o @p o10. Odd Matrix Module Theory ......................[1.6.10] ro @p o11. Even Matrix Module Theory ......................[1.6.11] so( @p o!12. Multi R/W Head Alignment Theory ...............[1.6.12] t o) @p u @p o*Your selection please (topic #): z o2 @p o0 PYp & 3.1.2.1.6.1. uio4 G- v)o5 v@ o7
ao? @p ! o8Theory - If a drive reports multiple read data errors, and if those vqoH @p # o@errors involve the same medium, and if they occur along the same radial wyoQ @p ! oIline, then there is a possibility that a radial bad spot (scratch) y oU @p oRis causing the errors. zoV @p zQoX @p zio` @p ! oY Read Data Error - Single Drive Radial Bad Spot Theory ... [1.6.1] {ob @p | oh @p oc Media ID: PS may have a radial bad spot at: |!oj @p } oq @p ok Track Sector Cylinder Hard Soft }!os @p ~oz @p ot 12. 2. 5. to 8. 0. 35. ~1o| @p )p @p o} DP020(RP06) was the only drive to detect these errors. Ap @p 9p
@p p 365. Total Retries (HARD and SOFT) Qp
@p ( @p p TO 9-Mar 03:50:41 Span: 161:19:13 z p @p p uipy 3.1.2.1.6.1.A. 9p G- yp p
ap$ @p # p Threshold - Several combinations of at least 4 Hard and/or at least 11 Ap- @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 have Yp? @p $ p7occurred in a radial line. That is, they must have the same surface and apH @p $ p@sector address and extend across multiple (three or more) cylinders. The qpQ @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] @p pZalong the radial line. p_ @p Ypd @p p`Background - Refer to the Introduction. qpf @p
Ipo @p # pgThe following examples illustrate some of Hard and Soft read data error
apx @p # ppcombinationsthat9this theory2will.tentatively identify asqa Radial Bad q
aq
@p ! qExample 1-4. Four or more Hard read errors along a radial line will !q @p q satisfy this theory. i.e., same drive, medium, surface and sector )q @p qaddress, but multiple (4 or more) cylinder addresses. )q @p q @p 1q$ @p q cyl 000 <--------45---46---47---48-------------------< Hub Iq& @p Iq, @p q' n n n n aq2 @p q- Hard Hard Hard Hard Aq3 @p !q9 @p q4Where n is equal to or greater than one. 9q: @p q< @p )q= @p AqE @p q> cyl 000 <-------15------21-----51---73-------------< Hub YqF @p QqJ @p
qG H3rd H7rd H1rd H4 h @p S @p qQ r 3.1.2.1.6.1.C. qqT G- 1qV H qW
aq` @p # qXExample12-4. Anycombination!offour or moreHard and/oreleven or more yqi @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 @p Aq} @p qv cyl 000 <--------49---50---51----------------------< Hub Yq~ @p Qr @p q 5 3 7 ir @p r Soft Hard Soft r @p Qr @p ir @p ! @p z r @p r
ar @p # rExample 3-4. Eleven or more Soft read errors along the same radial line "9r% @p " r satisfy this theory. (same drive, medium, surface and sector address, #Ir* @p r&but multiple cylinder addresses). $Qr+ @p %!r3 @p r, cyl 000 <--------21---22--23----------------------< Hub %9r4 @p &1r7 @p r5 1 9 1 &Ir; @p r8 Soft Soft Soft &yr< @p '1r> @p 'Ir? @p 'arG @p r@ cyl 000 <-------134-----178----------301-----------< Hub 'yrH @p (qrL @p rI 8 1 5 ) @p
rM Soft Soft Softz rT @p rR !2w $ 3.1.2.1.6.1.E. *rU G- *ArW *X rX
ara @p ! rYExample4-4. This example illustrates some typical radial bad spot + rf @p rbpatterns thatfthisStheory willSidentify. ,rh @p ,iri @p -rq @p rjcyl@000<--8--------------45--------------------314----->rHub -rs @p .ry @p rts'sector, b4t at three or 1ore different cylinder1 .1s @p rz.2.1.6.2.6Hard z n7 @pSofts2 c" Soft /s @p 0 s @p 0!s @p scyl 000 <------12-----13----------32--------------207---> Hub 09s
R.T.3.1.2.1.6.1.E. fys6 6H s7
as@ @p # s8STOP - You are moving in a reverse direction through the menu. You are 6ysG @p sAabout to back into the Single Drive Radial Bad Spot Theory. 8sI @p 8x @p
sJYour response please: x G- z sQ @p s-!Jat0 & 9isR G- :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 @p t Media ID: PS may have a radial bad spot at: ?yt @p @at @p t Track Sector Cylinder Hard Soft @yt @p Aqt @p t 12. 2. 5. to 8. 0. 35. B t @p Ct @p t DP010(RP04) and other drives detected these errors. Ct" @p D t' @p t# 200. Total Retries (HARD and SOFT) D!t) @p Dx @p t* Time: 2-Mar 10:31:28 TO 9-Mar 03:50:41 Span: 161:19:13 z t4 @p t2 9iu- $ 3.1.2.1.6.2.A. F t6 G- FIt7 F` t9
atA @p " t:Threshold - Several combinations of at least four Hard and/or eleven GtJ @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 must I)t\ @p $ tThave occurred in a radial line. That is, they must have the same surface J9te @p $ t]and sector address and extend across multiple (three or more) cylinders. KItg @p LYto @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 @p Ou @p tzThis theory is similar to the Single Drive Radial Bad Spot Theory Ou
@p # u[1.6.1]. The only difference is; this theory looks at all the read data Pu @p u errors, not just those common to a single drive. Q)u @p Ru @p uBackground - Refer to the Introduction. R)u @p Su" @p # uThe following examples illustrate some of Hard and Soft read data error Su+ @p # u#combinations that this theory will tentatively identify as a Radial Bad T( @p z u1 @p u/ F v & 3.1.2.1.6.2.B. UQu2 G- Vu4 V( u5
au> @p ! u6ExampleD1-4. Four0or moreuhard read errors along auradial0line-will VYuF @p " u?satisfy-this-theory.-i.e., multi drives, the sameYmedium, surface and WauN @p uGsector address, but multiple (4 or more) cylinder addresses. XiuO @p YauT @p
u` n n n n [qui @p udWhere n is equal to Hard Hard Hard Hard \1um @p
ujor greater than one. ]un @p ]Qup @p ]iuu @p uq DP240 DP140 DP220 DP110 ^uv @p ^Qu~ @p uw cyl 000 <---------312--313-----416-------642----------< Hub ^iu @p _av @p
v 3 1 5 2 _x @p v Hard Hard Hard Hard z v
@p v
UQv- & 3.1.2.1.6.2.C. av v
av @p $ vExample 2-4. Any combination of four or more hard and/or eleven or more b v" @p $ vsoft read errors along a radial line will satisfy this theory. i,e,. two cv+ @p $ v#or more drives, the same medium, surface and sector address, but multiple d)v/ @p v,cylinder addresses. e9v0 @p eqv4 @p
v1 DP110 DP140 DP220 f v5 @p fAv= @p v6 cyl 000 <--------49----50----51----------------------< Hub fYv> @p gQvB @p v? 1 5 1 givE @p vC Soft Hard Soft h!vG @p hYvH @p hqvM @p vI DP240 DP240 DP060 i vN @p iQvV @p vO cyl 000 <-------21-----25------------128------------< Hub iivW @p jav[ @p
vX 4 7 4 jx @p
v\ Soft Soft Hard z vc @p va aw3 & 3.1.2.1.6.2.D. kqvd G- l1vf lH vg
avp @p # vhExampleD3-4. Eleven or more Soft read errorspalongwthe same radial line lyvy @p " vqwill satisfy this theory. i.e., two or more drives, the same medium, n w @p vzsurface and sector address, but multiple cylinder addresses. ow @p p w @p p!w @p
cyl 000 <--------21----22----23----------------------< Hub qw @p rw @p w 1 9 1 r)w @p w Soft Soft Soft raw @p sw @p s1w! @p w DP050 DP110 DP260 sIw# @p tw* @p w$ cyl 000 <-------134-----178----------301-----------< Hub t1w, @p u)w/ @p w- 8 1 5 u@ @p
w0 Soft Soft Softz w7 @p w5 kqx7 & 3.1.2.1.6.2.E. v9w9 G- vyw: w w<
awD @p ! w=Example 4-4. This example illustrates some typical radial bad spot wAwJ @p wEpatterns that this theory will identify. xIwK @p y!wM @p y9wU @p wNcyl 000 <--8--------------45--------------------314-----> Hub yQwV @p zQw] @p wW 4 1 1 ziwd @p w^ Hard Soft Soft {Qwe @p |Awg @p |Ywo @p whcyl 000 <------12-----13----------32--------------207---> Hub |qwp @p }qww @p wq 4 2 7 5 ~ w~ @p wx Soft Hard Soft Soft ~yx @p ix @p x
@p # xRemember: The errors must have occurred on two or more drives, and at x @p ! x the same medium, surface, and sector address, but at three or more @p xdifferent cylinder addresses. 3.1.2.1.6.3.6.2 A z sM @p x!R9| R.T.3.1.2.1.6.2.E. 9Qx X x
ax) @p # x!STOP - You are moving in a reverse direction through the menu. You are x0 @p x*about to back into the Multi Drive Radial Bad Spot Theory. x2 @p @p
x3Your response please: A| G- z x: @p x v9y & yx; G- !x= 8 x>
axG @p # x?Theory - If two or more drives detect read errors, and if those errors ixO @p ! xHinvolve the same medium, cylinder, surface and sector address, then qxX @p # xPthere is a good chance that the errors were caused by a bad spot on the yxZ @p b x[ @p !x] @p 9xe @p ! x^ Read Data Error - Multi Drive Single Bad Spot Theory ... [1.6.3] Qxg @p
Yxn @p xh Media ID: SUPT may have a single bad spot at LBN 701620
qxp @p Track Cylinder Sector Hard Soft xx @p ix~ @p xy 0. 606. 8. 5. 6. y @p iy @p y DP030(RP06) and other drives detected these errors. y @p qy @p y 170. Total Retries (HARD and SOFT) y @p ` @p y Time: 2-Mar 10:31:28 TO 9-Mar 03:50:41 Span: 161:19:13 z y @p y yyy 3.1.2.1.6.3.A. qy G- 1y H y
ay( @p ! y Threshold - Any combinations of at least four Hard and/or at least yy0 @p y)eleven Soft read data errors will satisfy this theory. The error y8 @p " y1combinations, however, must involve two or more drives, and they must yA @p $ y9pertain to the same medium, cylinder, surface, and sector. The following yG @p yBexamples illustrate the combinations. yH @p qyQ @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 a y] @p yZRadial Bad Spot Theory. y_ @p Yyd @p y`Background - Refer to the Introduction. qyf @p Iyo @p # ygThe following examples illustrate some of Hard and Soft read data error ayx @p # ypcombinations that this theory will tentatively identify as a Radial Bad p @p mz y} @p y{ qz@ 3.1.2.1.6.3.B. y G- Yz p z
az
@p " zExample 1-3.mFourdormmore Hard readerrors-willXsatisfycthisutheory. -!z @p " z The errors must involve two or more drives, and they mustQpertainto !)z @p zthe same medium, cylinder,asurface, and sector'address. "1z @p #!z @p #9z# @p z z zD @p DP120{& & 3.1.2.1.6.3.C.DP270 #Qz' @p (AzG (X zH
azQ @p ! zIExamples2-3.mAnyumixtureaof fourorzmore-Hard-and/orcelevenforemore ) zY @p # zRSoftread errors will4satisfy this theory. The errors/must@involvetwo *zb @p " zZor more drives, and theyfmustapertain to theAsamepmedium, cylinder, +zf @p zcsurface, and sector address. ,!zh @p ,izn @p zi DP220 DP140 -zr @p
a{7 @p # {/Examples3-3.mEleven or more Softread errorsXwill-satisfyuthisetheory. 5i{? @p " {8The errors{must involve two or more drives, and they must pertain to 6q{F @p {@the same medium, cylinder, surface, andfsectorhaddress. 7y{H @p 8i{I @p 9{O @p {JP110. a|DP120 A` DP230 =!{t @DP270 9{T @p
a| @p # |STOP - You are moving in a reverse direction through the menu. You are B|! @p |about to back into the Multi Drive Single Bad Spot Theory. C|" @p D @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 those Eq|@ @p ! |8involve the same medium and the same cylinder, surface, and sector Fy|H @p " |Aaddress, then there is a good chance that the errors were caused by a H|L @p |Ibad spot on the medium. I |N @p II|O @p Ia|X @p ! |P Read Data Error - Single Drive Single Bad Spot Theory ... [1.6.4] Iy|Y @p K|a @p |Z Media ID: SUPT may have a single bad spot at LBN 701620 K|b @p L|i @p |c Track Cylinder Sector Hard Soft L)|j @p M|q @p |k 0. 606. 8. 5. 6. M)|r @p N|z @p |s DP020(RP04) was the only drive to detect these errors. N)|{ @p O!} @p || 170. Total Retries (HARD and SOFT) O9} @p P @p } Time: 2-Mar 10:31:28 TO 9-Mar 03:50:41 Span: 161:19:13 z } @p }
E}f 3.1.2.1.6.4.A. Q!} G- Qa} Qx }
a} @p " }Threshold - At least 4 Hard or 11 Soft read data errors are required R)}$ @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 have TA}4 @p }.occurred while the medium was mounted on the same drive. UQ}6 @p VI}> @p # }7Note: Errors reported by this theory will not be reported by either of Va}G @p # }?the Circumferential Bad Spot Theories, but they may be reported by one Wi}K @p }Hof the Radial Bad Spot Theory. Xq}M @p Y9}R @p }NBackground - Refer to the Introduction. YQ}T @p Z)}\ @p ! }UThe following example illustrates some of Hard and Soft read error ZA}d @p }]combinations that this theory will tentatively identify as single [H @p dz }j @p }h Q!~W $ 3.1.2.1.6.4.B. \a}k G- ]!}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 ~
DP120 a~ @p aI~ @p ~ -----X----- aa~ @p b~ @p ~ 4 b)~ @p ~ Hard ba~ @p c~ @p c1~" @p ~ DP110 DP230 cI~$ @p d)~) @p ~% -----X----- -----X----- dA~* @p f e~0 @p ~+ 11 3 12 e( @p ~1 Soft Hard Soft 3.1.2.1.6.5.6.4 0 z |& @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 are h ~P @p ~Jabout to back into the Single Drive Single Bad Spot Theory. i~R @p j @p
~SYour response please: :@ G- z ~Z @p ~6 \aA & jy~[ G- k!~] k8 ~^
a~g @p " ~RTheoryt- Ifrtwo-orumoreDdrivesidetectrreadadataderrors,handyif[those ki~o @p " ~herrorsinvolvethe samedmedium,Scylinder,hand surfacemaddress,landdif lq~x @p $ ~ptheyiinvolve adjacent sector addresses,athen thereiisea good chancetthat my @p ! ~ytheserrors are caused)bypa circumferential bad spot6on.the medium. o @p p @p p) u1 @p + DP020(RP06) and other drives detected these errors. u)3 @p v8 @p 4 80. Total Retries (HARD and SOFT) v19 @p w @p : Time: 2-Mar 10:31:28 TO 9-Mar 03:50:41 Span: 161:19:13 z E @p C jz 3.1.2.1.6.5.A. xF G- xQH xh I
aR @p # JThreshold - Several combinations of Hard and Soft read data errors will y[ @p " Ssatisfy this theory. All combinations, however, must involve the same z)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
@p x r & 3.1.2.1.6.5.B. z G- : P
b ( @p " !Example 1-3. Two or more Hard errors (multi drives, adjacent sectors) , @p
)will satisfy this theory.
. @p J 1 @p / DP120 DP040 b 6 @p 2 \ sect / < @p 7 cyl 175--------------4----5--------------cyl 175 b ? @p = n n J C @p @ Hard Hard z D @p 2 M @p ! EExample 2-3. Any combination of Hard and Soft errors (multi drives, J S @p Nadjacent sectors) will satisfy this theory. R T @p
2 X @p U DP220 DP140
J \ @p Y \ sect / c @p ] cyl 112--------------1----2--------------cyl 112 J f @p d n n
2 i @p g Hard Soft
b k @p Where in both examples, n is equal to or greater than one. z
v @p t z[ " 3.1.2.1.6.5.C. * x G- j y {
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 @p 4 7 5 0 @p 7 Soft Hard 3.1.2.1.6.6.6.5 G z ~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
] @p 9 *E & 2_ G- Z` p b
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< @p 8 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:13 z
I @p G 2 3.1.2.1.6.6.A. (ZK G- )L )0 N
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 @p 2 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 @p Nadjacent sectors) will satisfy this theory. 9ZU @p ::X @p V DP220 DP220 :R] @p Y \ sect / ;
c @p ^ cyl 112--------------1----2--------------cyl 112 ;Re @p <:j @p fWhere n is equal to n n <P @p kor greater than one. Hard Soft z
s @p q 2*Y $ 3.1.2.1.6.6.C. =zu G- >:v >P x
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 @p 2 7 5 F @p 5 Soft Hard 3.1.2.1.6.7.6.6 \x z
Y @p < :h R.T.3.1.2.1.6.6.C. @ Gh A
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: ]l G- z
\ @p 7 =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:
@p RQ* @p reports: 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 @ K 3.1.2.1.6.7.A. WbC G- X"E X8 F
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 @p athe single head alignment theory [1.6.8]. 3.1.2.1.6.8.6.7 s z
X @p j G" R.T.3.1.2.1.6.7.A. Kn ]H o
bx @p # pSTOP - You are moving in a reverse direction through the menu. You are ]z~ @p yabout to back into the Single Head Theory. _ @p _` @p
Your response please: s" G- z
@p e 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 @p 0 Read Data Error - Single Head Alignment Theory ... [1.6.8] er8 @p fj= @p 9 DP020 (RP04/SN: 33) reports: gD @p > head 6. used offset (at least once) to recover from gRJ @p E no Hard and 6. Soft Read Data errors. hBK @p i"P @p L 90. Total Retries (HARD and SOFT) i:R @p j
Y @p S 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 @p r `R8
3.1.2.1.6.8.A. n
v G- 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 @p Background - Refer to the Introduction. 3.1.2.1.6.9.6.8! z
@p ]Z R.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 @p Qchances are the fault lies in the common read circuitry. z
Y @p {a @p Z Read Data0Error - Common Read Logic Theory....![1.6.9] {b @p |j @p c. DP000 (RP06/SN: 21) reports2random Read Data.errorson:p|*k @p }"t @p ! l 0.Head No. Hard Errors Soft Errors @p Total Retries .}:u @p ~B} @p v 3. 4. 6. !r(0.p !r0 1. ) 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 @p B wn9 3.1.2.1.6.9.A. !E G- !BG !X H
bQ @p # IThreshold - At least 2 read errors are required to satisfy this theory. ! @p RThe 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` ! h a
bj @p # bSTOP - You are moving in a reverse direction through the menu. You are!
p @p kabout to back into the Common Read Logic Theory. !
sYour response please: ! *
G- z
z @p W * 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.!
n G- ! 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 @p errors, and retries associated with each head. z
@p !$ H 3.1.2.1.6.11.A.!2 G- !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!O z
@p -!1*2.1.6.11.A. !#j 1 !5x 2
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. !72 C @p !8 @p
DYour response please: !O
} G- z
K @p (!2
V . !9
L G- !92 N !9H O
b X @p # PTheory - If a drive reports multiple read data errors involving two or!9z a @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 @p k 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@ @p hz
Z @p
X!9 sN 3.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
arepthe Channel Error Theories. !Q
ur response please: z
@p R.T.3.1.2.1.6.12.A. !R:
b @p # ouaareimovingeineadreversehdirection through the menu. You are!SJ
ur response please: !cJ! G- z
4 @p
v g " !V"
b @p Analyze!-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 @p 3.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@ !gp B
bI @p C Analyze - Disk Subsystem Channel Error Theories !h"J @p !iM @p KTopic Menu: !i*O @p !iZR @p P 0. Introduction !irT @p !j*[ @p U 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 @p g 3. Write Operation/RH Controller Theory ........ [1.7.3] !lbo @p !mZv @p p 4. Write Operation/MBox (UBA) Channel Theory ... [1.7.4] !mrx @p !nj @p y 5. Overrun Only Channel Theory...................[1.7.5] !o @p !ox @p Your selection please (topic #): z
@p !V"| & 3.1.2.1.7.1. !pb G- !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 @p K 54. RHtNo:r3.rreports:!(during Data Readoperations) !y"R @p !zY @p Sr 03:50:12. (Hard)1and1no1(Soft)hchannel errors. !z*] @p he report identifies the RH controller on the channel and the number of !}y @p " rHard channel errors, Soft channel errors, and retries associated with !~ @p zthe channel. z
@p ~!pbH
3.1.2.1.7.1.A. !J G- "
"
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 @p bits set). "Z" @p " @p #Background - Refer to the Channel Error Introduction. 3.1.2.1.7.2.7.1" z
9 @p -!cJq R.T.3.1.2.1.7.1.A. !g1 "x 2
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: " v G- z
K @p (!J= $ "
L G- " 2N " H O
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. "ZC G- "D "0 F
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 @p iBackground - Refer to the Channel Error Introduction. 3.1.2.1.7.3.7.2"6` z
G @p s"26 R.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" @p about to back into the Channel Read MBox (UBA) Theory. "
@p "! @p
Your response please: "6j; G- z
@p o"Z & "!z G- """ ""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,ethen chancespare the"fault@lies inIthehcontrollerror"'F @p eration/RH Controller Theory ... [1.7.3] ")R @p "*
Y @p S RH No: 3. reports: (during Data Write operations) "*"_ @p Z 21. (Hard) and 0. (Soft) channel errors. "+c @p
` 120. total retries."+ze @p ",:l @p f 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 @p the channel. "/x @p z
@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"OH z
@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 @p Gabout to back into the Channel Write RH Theory. "8jN @p "9P @p
OYour response please: "OR G- z
V @p 4"0BI $ ":BX G- ":jY "; [
bc @p " \Theorys-iIfetwocor more@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 @p Fthe MBox or UBA. z
M @p K":B
3.1.2.1.7.4.A. "IN G- "IRP "Ih Q
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 @p lthe drive error register must be clear (no error bits set). "M2t @p "N( @p uBackground - Refer to the Channel Error Introduction. 3.1.2.1.7.5.7.4"g8 z
R @p "6jX R.T.3.1.2.1.7.4.A. ":* "P
bp # STOP - You are moving in a reverse direction through the menu. You are"PH @p about to back into the Channel Write/MBOX Theory. "gB@ G- z
@p z"Iv $ "RR G- "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; @p 7 configuration or a heavy system load. "Vb= @p "W:? @p >PACKET 13."WRA @p "WzG @p B Channel Error - Overrun Only Theory ... [1.7.5] "XI @p "XzQ @p J 3. channel errors occurred with only the overrun bit set "YV @p R 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 @p p type (hard or soft) and how many retries there were. z
z @p x"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 @p 5 set the channel error bit in the CONI. 3.1.2.1.8.1.7.5#'x z
@p >!O@ F.T.3.1.2.1.8.1. "R:B "h C
bL @p # DThat's it. there are only five Channel Error Theories. Next on the menu "h:R @p Mis the Head Select/Header Compare Theory. "iJT @p "j( @p
UYour response Please: z
\ @p Z"ORS R.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 @p jabout to back into the Channel Theories."mp @p "mp @p
qYour response please: #(D G- z
x @p 9!g2^ " "nbz G- "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 @p X Time: 2-Mar 10:31:28 TO 9-Mar 03:50:41 Span: 161:19:13 z
b @p `"nb~ * 3.1.2.1.8.1.A. "{jd G- "|*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 "
@p that 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$ @p read 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 @p 0 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. #b G- #" #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 @p 2 DP210 (RP06/SN: 770) reports: #= @p 7 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:55 z
@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#T z
t @p B"gB , F.T.3.1.2.1.9.1. "nJF #(H G
bO @p HThat'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. #*:Y G- #+[ #+ \
be @p # ]STOP - You are moving in a reverse direction through the menu. You are#+Jl @p fabout to back into the Head Select/Header Compare Theory. #,Rn @p #-H @p
oYour response please: #T % G- z
v @p =#!"N #.:w G- #.by #.x z
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 @p G Time: 2-Mar 10:31:28 TO 9-Mar 03:50:41 Span: 161:19:13 z
R @p P#.9;K 3.1.2.1.9.1.A. #9bS G- #:"U #:8 V
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 @p qand lists the number of IXE errors that occurred. #>
x @p #>r @p yBackground - 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. #EB 1 G- #F 3 #F 4
b = @p $ 5Well,tthat'sftheulastlofstheydiskstheories.sTherelareu45kofwthemtinoall. #FJ C @p >Next on#themenu are the tape theories. #GZ D @p #H2 F @p #HJ N @p # GBut, before going on, we would like to remind you that this is a first#Hb W @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#Jz i @p $ aall the technical expertise we can get. That's were you come in. You are #L r @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@ @p Press the RETURN key to proceed to the Tape Theories. R.T.3.1.2.M.9.1#Wx z
r @p ##*: R.T.3.1.2.1.9.1.A. #." ' #TX (
b 1 @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 @p 8{ #X D G- #X* E #X@ G
b O @p ! HSTOP - You are moving in a reverse direction thru the menu. You are #Xr T @p Pabout to back into the Theory Menu.#Yz V @p #ZH @p
WYour response please: Control)..z
] @p >92 Q
#[2 _ G- #[Z ` #[p b
b i @p ced 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 #T R.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" @p about 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 #eR 1 @p #f 7 @p 2 0. Overview - Tape Subsystem Theories #f 8 @p #fr ? @p 9 1. TM02/TM03 Theories ... [2.1.1.1] thru [2.1.8.1] #g
A @p #gz H @p B 2. TX01/TX02 Theories ... [2.2.1.1] thru [2.2.8.1] #h I @p #i K @p #i @p LYour selection please (topic #): #s G- z
U @p S#[2 3.1.2.2.1.0. #j W G- #jZ X #jp Z
b a @p [11, RH20,Analyze8-.TM02/TM03@Tape Subsystem@Theories #k" b @p #l k @p # cOverview -pThetTMntape theoriessapply#only to TM02/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 @p Y3.1.2.2.1.M.1.0$p z
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. #u 0 @p #up @p
1Your response please: $z , G- z
8 @p +'j[v #vb : G- #w
; #w =
b D @p > TM02/TM03 Tape Subsystem Theories #wR E @p #xB H @p FSelection Menu #xZ J @p #y
P @p K 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] #{B f @p #|J n @p ! g 3. TM02/03 Massbus Theories .............[2.1.7.1] thru [2.1.7.8] #|b p @p #}j w @p q 4. TM02/03 Control Operation Theories ...[2.1.8.1] #~ x @p #~r z @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$h z
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 J G- $ 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/03 Read3Operation DevicepTheoriesS....[2.1.2.1]rthru.[2.1.2.4] $r! @p $h @p !Your selection please (topic #): $3B#! G- $70 z
E @p ! #r!b 3.1.2.2.1.1.1.0. $R!
b! @p !ead error oTM02/TM03 Read!Operation Data!Theories $j! @p $R! @p # !OverviewM-aThisPsetrofctheoriesdapplyvonlycto errors that 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. $ "!h G- $ 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"M G- $)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"} @p i "vrcharacter$did not matchLRCtcharacter 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- $vx 3.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-tIfEtherread errorjrate for a$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&2 G- $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@- Since the contentsofBthegCRCnregisterrcannotebeeusedato identify $l"&t @p # <hefailing 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)D R.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)I G- % @ 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+c R.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+h G- %Nh 3.1.2.2.1.1.1.3. %)h G- % 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. %,*f G- %,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,w R.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.3 G- %i8 z
, @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_theory z
- @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%Nr1 R.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: &z1 G- &X 3.1.2.2.1.1.1.6. %eB.O G- %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/L G- %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 @p 0INC - Incorrectable Data Error means that either: &
0
@p 0 1.aMultipleedeadetracksowere detected. & r0 @p 0 0 3. A parity error was detected without a dead track. &:0 @p 0 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 @p 05%xb1.1.6.B &209 G- &z0: & 0<
b0E @p $ 0=Four error detectors monitor read data transfers in NRZI mode (CRC, LRC, &B0H @p 0FITM, 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 @p 0{ were read and recognized as a tape mark. &*1 @p &
1
@p ! 1 VPE - Vertical Parity Error means that a vertical parity error was & @p 1 detected.z
10 @p 1-&2# , z
.J @p 1%ej2N R.T.3.1.2.2.1.1.1.6.B. %i"1 &H 1
b1 @p ! 1STOP - You are moving in a reverse direction thru the menu. You are &z1& @p 1!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&@0 3.1.2.2.1.1.1.7. &R11 G- &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 @p 1`with the errors. &z1d @p & 21k @p 1e Read Data - Media Bad Spot Summary ... [2.1.1.7]& J1l @p & 21t @p 1m Media ID: 7601 Recording Mode: NRZI was identified with & J1{ @p 1u read errors as noted against the following drives: & B1| @p & 22 @p 1} MT404 (TU72, SN: 28411.) with 1. errors. & J2 @p
2 Additional Data & 22 @p 2 Operation :READ FWD& r2 @p 2
User ID :500000,,5 &!:2 @p 2 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) @p d&% @p 2* Time of Error: 26-Jun 06:29:54 z
23 @p
20#EB9 F.T.3.1.2.2.1.1.2.0.&%j24 G- &&226 &&H 27
b2@ @p # 28That's it. There are only 7 Read Operation Data Theories and Summaries. &&z2H @p 2ANext 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.&)b2T G- &**2U &*@ 2W
b2_ @p ! 2XSTOP - You are moving in a reverse direction thru the menu. You are &*r2f @p 2`about to back into the Read Operation Data Theories. &+z2h @p &,h @p
2iYour response please: z
2p @p 2n$34 3.1.2.2.1.1.2.0. &-B2r G- &.
2s &. 2u
b2| @p 2v 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 @p 3 summary report.z
3& @p
3$&)b4c R.T.3.1.2.2.1.1.2.0.&4"3( G- &4j3) &5 3+
b33 @p ! 3,STOP - You are moving in a reverse direction thru the menu. You are &523; @p 34about to back into the Read Operation Device Theory Overview. &6:3= @p &78 @p
3>Your response please: &@:4 G- z
3E @p 1+' 9$ &8*3F G- &8R3H &8h 3I
b3P @p 3J TM02/TM03 Read Operation Device Theories&93R @p &:
3U @p 3SSelection Menu &:"3V @p &:R3] @p 3W 0. Overview - TM02/TM03 Read Operation Device Theories&:j3_ @p &;Z3d @p 3` 1. Power Supply Theory .....[2.1.2.1] &;r3f @p &<J3k @p 3g 2. Drive Offline Theory ....[2.1.2.2] &<b3m @p &=:3r @p 3n 3. OPI Blank Tape Theory ...[2.1.2.3] &=R3t @p &>*3y @p 3u 4. Device Error Summary ....[2.1.2.4] &>B3{ @p &?3| @p &?0 @p 3}Your selection please (topic #): &ir6T G- &mX z
3A @p 4&-B5 3.1.2.2.1.1.2.1. &84 &A 4
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 " 4 progress, 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 @p 4@drive while it was off-line. &Gr4E @p &H:4K @p 4F Read Data - Power Supply Theory ... [2.1.2.1] &HR4M @p &I:4R @p 4N MT100 (TU77, SN:6609) reports: &IR4Z @p 4S 3. Unsafe Errors that are most likely Power Supply failures. &J"4[ @p &K @p 4\ Time: 29-Dec 18:32:50 To 29-Dec 19:06:07 Span: 0:33:17 z
4h @p
4e&4"5b R.T.3.1.2.2.1.1.2.1.&L:4i G- &M4k &M 4l
b4u @p ! 4mSTOP - You are moving in a reverse direction thru the menu. You are &MJ4| @p 4vabout to back into the Read Data Power Supply Theory. &NR4} @p &O@ @p
4~Your response please: z
5 @p 5&@:6 3.1.2.2.1.1.2.2. &P5 G- &Pb5 &Px 5
b5 @p # 5 Theory - 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 " 5 progress, 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 @p 5?drive while it was off-line. &Wj5D @p &X25K @p 5E Read Data - Drive Off-line Theory ... [2.1.2.2] &XJ5L @p &Y25Q @p 5M MT100 (TU77, SN:6609) reports: &YJ5Y @p 5R 4. Unsafe Errors that are most likely off-line errors. &Z5Z @p &[ @p 5[ Time: 29-Dec 18:19:51 To 29-Dec 18:37:03 Span: 0:17:12 z
5g @p
5d&L:6O R.T.3.1.2.2.1.1.2.2.&\*5h G- &\r5j &] 5k
b5t @p ! 5lSTOP - You are moving in a reverse direction thru the menu. You are &]:5{ @p 5uabout to back into the Read Data Drive Off-line Theory.&^B5| @p &_0 @p
5}Your response please: z
6 @p 6&P6L 3.1.2.2.1.1.2.3. &`
6 G- &`R6 &`h 6
b6 @p ! 6
Theory - If ardrive reportsrOPI errors6during read&operations,then &a6 @p 6chances(are7theNtape5was either@blankor was in the.wrong format.&b"6 @p &c"6" @p 6 ReadhData@- OPIBlankiTape Theory1...3[2.1.2.3] &c:6# @p &d"6) @p 6$7 Media I D: AUG6 was associated with &d:6/ @p 6* 4. OPI errors on the following drives: &e61 @p &ez65 @p
6p @p 6m&`
7Q & z
4 @p 6Q&\*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 @p 6`about to back into the Read Data OPI Blank Tape Theory.&kz6h @p &lh @p
6iYour response please: 'j9+ G- 'X 3.1.2.2.1.1.2.4. &iJ6q G- &n6s &n 6t
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 @p 7bit combinations. &pb7 @p &q7 @p 7
Read Data - Device Error Summary ...[2.1.2.4] &q27 @p &r7 @p 7 MT100 (TU77, SN: 6609) reports: &r27 @p &s7 @p 7 Error bit Number of Span &s7& @p 7 Combinations Occurrences Window HH:MM:SS&sr7( @p &tj7, @p 7) D N F N F R I I &u70 @p 7- T E C S M M L L &uB74 @p 71 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 @p 7J 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. &z7W G- &zZ7X &zp 7Z
b7b @p 7[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 @p 8- 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 @p 8D only occur during a write operation. z
8M @p 8K&z3B 3.1.2.2.1.1.2.4.B. ' 8O G- ' Z8P ' p 8R
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 @p 8e attempted when the GO bit was set.'
J8k @p 'ILF~-@IllegalvFunctionlmeans thatsanrillegaltfunctiontcodetwassissued. 'd or write 'X @p 8 a non-existent register. z
9 @p
9&%j:D F.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 @p 9E&8* F , z
6l @p 9(&ir:c R.T.3.1.2.2.1.1.2.4.B. &mB9- '8 9.
b97 @p ! 9/STOP - You are moving in a reverse direction thru the menu. You are 'j9> @p 98about to back into the Read Operation Device Error Theories.'r9@ @p 'h @p
9AYour response please: 3.1.2.2.1.2.0.1'5H 3.1.2.2.1.1.3.1. 'B9I G- '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 @p 9_would be considered a software error. 'b9e @p ' :9k @p 9fRead Data - Software Error Summary ... [2.1.3.1] ' R9m @p ' :9s @p 9n Note: Error register contents are in octal.' R9t @p ' 29y @p 9uMT100 (TU45, SN: 627) reports: ' J9{ @p ' : @p 9| 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':?l F.T.3.1.2.2.1.2.0. '(B:J G- ')
: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.',::i G- '-: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;1 G- z
; @p 9C$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 @p 3.1.2.2.1.2.M.2'A z
; @p ;/',:<x R.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;O G- '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>8 G- '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>3 R.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:=I G- '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:>0 3.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
>V G- 'jJ>W 'j` >Y
b>a @p # >ZThisNreport summarizes allP(read afterawrite)?data errors that didrnot'k>j @p # >bmeet:theSthresholdqestablished?for-the Bad-Media Theory [2.1.4.1]. The'l>r @p " >kreport lists-the drive,@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?O G- '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'(BFM F.T.3.1.2.2.1.2.2.0.'}B?r G- '~
?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@a R.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*Fw G- (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.(
@g G- (
Z@h (
p @j
b@r @p ! @kSTOPt-tYouaareimovingeinratreversetdirectionethruothehmenu.OYouvare (*@| @p (0 @p
@}Your response please: z
A @p A(bRFp 3.1.2.2.1.2.2.M. (
A G- (RA (h A
bA @p A
TM02/TM03 Write Operation Device Theories (A @p (
A @p A 0. Overview - Write Device Theories ("A @p (zA @p A 1. Power Supply Theory .......[2.1.5.1](A @p (jA& @p A! 2. Drive Offline Theory ......[2.1.5.2] (A' @p (bA- @p A( 3. OPI Write Timing Theory ...[2.1.5.3](zA. @p (RA4 @p A/ 4.Device Error Summary .......[2.1.5.4](jA5 @p (@ @p A6Your selection please (topic #): z
A? @p A<(BB 3.1.2.2.1.2.2.1. (*A@ G- (rAB ( AC
bAL @p # ADTheory- Ifa drive0reports,anNUnsafe errortcondition,pand ifboth3the(:AT @p # AMfilerandorecordecounters arepgreateruthan zero, indicating#that@a data(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 @p B while it was off-line. ( zB @p ( :B @p B 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< @p B6about to back into the Write Operation Power Supply Theory. (&RB> @p ('H @p
B?Your response please: z
BF @p BD(*CI 3.1.2.2.1.2.2.2. (("BH G- ((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 @p Cwhile it was off-line. (0rC
@p (12C @p C-line Theory ... [2.1.5.2](1JC @p (22C @p C MT100 (TU77, SN:6609) reports: (2JC! @p C 4. Unsafe Errors that are most likely off-line errors. (3C" @p (4 @p C# Time: 29-Dec 18:19:51 To 29-Dec 18:37:03 Span: 0:17:12 z
C/ @p
C,($:D R.T.3.1.2.2.1.2.2.2.(5*C0 G- (5rC2 (6 C3
bC< @p ! C4STOP - You are moving in a reverse direction thru the menu. You are (6:CC @p C=about to back into the Write Data Drive Off-line Theory. (7BCE @p (88 @p
CFYour response please: z
CM @p CK(("D= $ 3.1.2.2.1.2.2.3. (9CO G- (9ZCP (9p CR
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 @p Cdthe drive.(<:Cg @p (<bCi @p (<zCp @p Cj Write Data - OPI Write Timing Theory ... [2.1.5.3] (=Cq @p (>Cv @p Cr MT100 (TU45, SN:FF8) reports: (>C} @p Cw 6. OPI errors while performing write operations. (>jC @p (?ZD @p D 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 @p D
Background - (A:D @p (AjD @p " D OPI - Operation Incomplete indicates that the data transfer did not (B @p D begin within seven seconds after command initiation. z
D$ @p
D!(5*Fr R.T.3.1.2.2.1.2.2.3.(CzD% G- (DBD' (DX D(
bD1 @p ! D)STOP - You are moving in a reverse direction thru the menu. You are (E
D7 @p D2about to back into the Write Operation OPI Theory.(FD9 @p (Fx @p
D:Your response please: z
DA @p D?(9E% ( 3.1.2.2.1.2.2.4. (GRDC G- (HDD (H0 DF
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 @p DXcombinations. (JrD[ @p (K"D] @p (K:Dc @p D^ Write Data - Device Error Summary ...[2.1.5.4] (KRDe @p (L:Di @p Df MT100 (TU45, SN:200) reports(LRDk @p (MDp @p Dl Error bit Number of Span (M2Dx @p Dq Combinations Occurrences Window HH:MM:SS(N
E @p $ Dy ------------ ----------- ------ -------- (OE @p E D N F N F R I I (PE @p E T E C S M M L L (PRE
E F E G T R R F (QE @p (QRE @p E 0 0 0 0 0 0 0 1 10. 23-Mar 00:03:00 (QjE @p E 0 0 0 0 0 0 1 0 10. 23-Mar 00:02:00 (RRE @p (S8 @p E 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, (U0 E.
bE6 @p E/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 @p Ei 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 (`` @p F the first half of the end of record gap. z
F @p F(TRA 3.1.2.2.1.2.2.4.B. (bRF G- (cF (c0 F
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 @p F1 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 @p FB ILR - Illegal Register means an attempt was made to access a (h @p FJ non-existent register. z
FR @p
FO'}BH
F.T.3.1.2.2.1.2.3.1.(iZFS G- (j"FU (j8 FV
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 @p FiSummary. (mFl @p (m( @p
FmYour response please: z
G @p G(
;K * z
@) @p Ft(CzH* R.T.3.1.2.2.1.2.2.4.B. (Fy (nx Fz
bG @p ! F{STOP - You are moving in a reverse direction thru the menu. You are (o*G @p Gabout to back into the Write Operation Device Error Theories. (p2G
@p (q0 @p
G response please: 3.1.2.2.1.3.0.2)p 3.1.2.2.1.2.3.1. (nG G- (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/ @p G+be considered a software error. (u*G1 @p (uzG8 @p G2Write data - Write Software Error Summary ... [2.1.6.1](vG9 @p (wG? @p G: Note: Error register contents are in octal.(wGA @p (wzGF @p GBMT300 (TU45, SN: 621.) reports: (xGG @p (xbGM @p GH Error Media No. of SPAN (xzGS @p GN Register ID Errors Window HH:MM:SS(yRGY @p GT---------- ----- ------ ------ --------(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 ) @ @p H Time: 24-Jun 12:37:53 To 30-Jun 02:41:49 Span: 134:03:56 z
H @p H(iZZ F.T.3.1.2.2.1.3.0. )ZH G- )"H )8 H
bH @p " HThat's it. There is only one Write Operation Software Summary Report. )jH% @p H 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.)*H0 G- )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 @p G'92I7 ) :HO G- ) bHQ ) x HR
bHZ @p HS 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)the Massbus@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)Ex z
HJ @p I9) :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 @p IQ(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 @p Ik operations as illustrated below. ) *Iq @p ) zIv @p Ir DF10C RH10 Massbus TM02/03 ) I} @p Iw <read --- DPE <--------- no ck <--- tape ) jJ @p I~ write>--- no ck ----------> PAR ---> tape ) RJ @p ) :J
@p J UBA RH11 Massbus TM02/03 ) RJ @p J <read --- DPE <--------- no ck <--- tape )!*J @p J write>--- no ck ----------> PAR ---> tape )"J @p )"zJ @p J MBox RH20 Massbus TM02/03 )#J% @p J <read --- DPE <--------- no ck <--- tape )#h @p J& write>--- DPE ----------> PAR ---> tape z
J0 @p
J-)*Lp R.T.3.1.2.2.1.3.0.A.)%:J1 G- )&J3 )& J4
bJ= @p ! J5STOP - You are moving in a reverse direction thru the menu. You are )&JJC @p J>about to back into the Massbus Theory Overview. )'RJE @p )(8 @p
JFYour response please: )FL4 G- z
JM @p I5+RZ> $ ))*JN G- ))RJP ))h JQ
bJY @p JR TM02/TM03 Massbus (control bus/data bus) Theories )*JZ @p )+J] @p J[Selection menu )+*J_ @p )+ZJf @p J` 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 @p K1Your selection please (topic #): z
K9 @p K7)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 @p Kjsomething to do with the Massbus interface logic. )=Kq @p )=zKx @p KrRH CBUS Error - Massbus(control bus) RH theory [2.1.7.1] )>Kz @p )?
L @p K{ MT315 (TU45, SN: 627) was identified with )?"L @p L 4. Massbus (control bus) Parity Errors detected by )@L @p L Controller no: 1 (TM02) connected to channel 3 (RH11). )@rL @p )AjL @p L MT324 (TU45, SN: 452) was identified with )BL @p L 2. Massbus (control bus) Parity Errors detected by )BbL$ @p L Controller no: 2 (TM02) connected to channel 3 (RH11). )CRL& @p )DH @p L' Time: 23-Mar 00:01:00 To 23-Mar 06:01:15 Span: 6:00:15 3.1.2.2.1.3.2.3)dH z
JI @p L2)6RM 3.1.2.2.1.3.1.A. ))L6 )FH L7
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 @p LItheory. 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 thatrwere involved,@and the total number of)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
Lv G- )NRLx )Nh Ly
bM @p ! LzSTOP - You are moving in a reverse direction thru the menu. You are )OM @p Mabout to back into the Massbus (control bus) RH Theory.)P"M
@p )Q @p
M Your response please: )dRN) G- z
M @p L-)FNC , )RM G- )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 @p MCsomething to with the Massbus interface logic. )X*MJ @p )YMR @p MKRH CBUS Error - Massbus (control bus) TM theory [2.1.7.2] )Y*MS @p )Z"MY @p MT MT315 (TU45, SN: 627) was identified with )Z:M` @p MZ 4. Massbus (control bus) Parity Errors detected by )[Mh @p Ma Controller no: 1 (TM02) connected to channel 3 (RH11). )\
Mi @p )]Mq @p Mj 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
@p Ntheory.0In.addition,ralldtheierrorshmustiinvolvetthensamertape )`BN @p # NMassbus (control bus) errors that occurred. )bRN @p )c0 @p N Background - Refer to the Massbus Theory Overview.3.1.2.2.1.3.3.3)v` z
M @p N')N
P R.T.3.1.2.2.1.3.2. )QjN+ )e N,
bN5 @p ! N-STOP - You are moving in a reverse direction thru the menu. You are )eJN< @p N6about to back into the Massbus (control bus) TM theory.)fRN= @p )g@ @p
N>Your response please: )vjO; G- z
NE @p N")RO6 & )h2NG G- )hZNH )hp NJ
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{ @p Nusomething 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
@p O sbusRHdNo: 2.s(RH20)treports: )qO @p " Oh the following )qJO @p O controllers and their drives: )rRO @p )s"O" @p O 1. Errors in MT210 (TM02: 1., TU45, SN: 200) )s:O$ @p )t*O+ @p O% 1. Errors in MT220 (TM02: 2., TU45, SN: 600) )tBO, @p )u0 @p O- Time: 23-Mar 00:01:00 To 23-Mar 00:01:15 Span: 0:00:15 3.1.2.2.1.3.4.3*8 z
NA @p O8)h2P5 3.1.2.2.1.3.3.A. )hO< )w0 O>
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 @p OkMassbus (data bus) parity errors that occurred. )}*Or @p )~Ot @p )~*Oy @p OuMBox/UBA RHxx Massbus TM02/03 )~BO{ @p )P @p O| <read --- DPE <---------.- no ck <--- tape )2P @p P ! * P
@p P !_ no ck <--- tape * bP @p *JP @p *` @p PBackground - Refer to the Massbus Theory Overview.z
P @p
P)dRQe R.T.3.1.2.2.1.3.3.A.*bP G- **P *@ P
bP' @p ! P STOP - You are moving in a reverse direction thru the menu. You are *rP. @p P(about to back into the Massbus (data bus) RH Theory. *zP0 @p *h @p
P1Your response please: *BQ G- z
P8 @p O4)vjQ *ZP9 G- *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 @p Phsomething 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 @p P| MT210 (TU45, SN: 200) was identified with *2Q @p Q 3. Massbus (data bus) Parity Errors detected by *Q @p Q Controller no: 1. (TM02) connected to channel 2. (RH20). *zQ @p *rQ @p * @p Q 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 @p Q *ZR 3.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 @p QFMassbus (data bus) parity errors that occurred. *ZQM @p *BQS @p QNMBox/UBA RHxx Massbus TM02/03 *ZQT @p *2QZ @p QU <read --- DPE <--------- no ck <--- tape*JQ\ @p **Q] @p *@ @p Q^Background - Refer to the Massbus (data bus) Introduction. z
Qi @p
Qg*bT R.T.3.1.2.2.1.3.4.A.* RQk G- * Ql * 0 Qn
bQv @p ! QoSTOP - You are moving in a reverse direction thru the menu. You are * bQ} @p Qwabout to back into the Massbus (data bus) TM Theory. * jQ @p * X @p
R Your response please: *3*S G- z
R @p Q*BS , * JR G- * 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 @p Re 5. Massbus (data bus) Parity Errors. *,JRk @p *-"Ro @p RlAdditional Data: *-:Rp @p *-rRx @p Rq RH no: 1 (RH20) reports (during data write operations) *.
R @p Ry 3. (RH detected) Massbus (data bus) Parity Errors */S @p */rS @p S RH no: 2 (RH20) reports (during data write operations) *0
S @p S 2. (RH detected) Massbus (data bus) Parity Errors *1S @p *1p @p S Time: 29-Mar 00:30:00 To 29-Mar 02:15:00 Span: 1:44:60 3.1.2.2.1.3.6.3*U z
R @p S * JT! $ 3.1.2.2.1.3.5.A. * 2S *3p S"
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 @p SR MBox RH20 Massbus TM02/03 *:SX @p *:jS^ @p SY .--> DPE ----------> PAR ---> tape*;S` @p S_write>---!*;bSf @p Sa `--> DPE ----------> PAR ---> tape*<
Sh @p *<jSq @p $ SiSince RH10s and RH11s do not check parity during a data write operation, *=Sx @p Srthis theory only applies to RH20 controlled tape subsystems.*>Sz @p *?
S{ @p *? @p S|Background - Refer to the Massbus Theory Overview.z
T @p
T* RV R.T.3.1.2.2.1.3.5.A.*@"T G- *@jT *A T
bT @p ! T
STOP - You are moving in a reverse direction thru the menu. You are *A2T @p Tabout to back into the Massbus (data bus) MBox Theory. *B:T @p *C( @p
T Your response please: *U*U/ G- z
T$ @p S*3*U* ( *DT% G- *DBT' *DX T(
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 @p T{ RH No: 1. (RH20) reports (during Data Write operations) *O"U @p U 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 @p U 4. (TM02 detected) Massbus (data bus) Parity Errors. *SU @p *Sp @p U! Time: 29-Mar 00:30:00 To 29-Mar 02:15:00 Span: 1:44:60 3.1.2.2.1.3.7.3*ux z
T @p U,*DV% 3.1.2.2.1.3.6.A. *DU0 *Up U2
bU; @p # U3Threshold - At least two(RH@detected) Massbus (data bus) parity errors *V"UC @p " U<are required to satisfyithisRtheory.dThe1errorsnmusthinvolveithedsame *W2UL @p " UDRHrcontroller]and two ormoreitapeecontrollers.lAlso,othe2errorsrmust *X:UR @p UMhavejoccurred during data write operations. *YBUS @p *Z"UU @p *Z:UZ @p UVMBox RH20 Massbus TM02/03 *ZRU[ @p *["Ua @p U\write> --- DPE --------->-- PAR ---> tape *[:Uf @p
V
@p
V*@"X R.T.3.1.2.2.1.3.6.A.*`bV
G- *a*V V
bV @p ! VSTOP - You are moving in a reverse direction thru the menu. You are *arV @p Vabout to back into the Massbus (data bus) RH20 Theory. *bzV @p *ch @p
V!Your response please: *vW4 G- z
V( @p U(*U*W0 ( *dZV) G- *eV+ *e V,
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 " VuerRH DPE*Error@- Data Write/Massbus(data bus)ERHotheorye...d[2.1.7.7] *nBV~ @p *oJW @p VBW RH No: 1.*(RH20)preports (duringrData Writetoperations) *obW03: 1,TU45, SN: 764.) *sRW& @p *tH @p W' Time: 29-Mar 00:00:00 To 29-Mar 02:15:00 Span: 2:15:00 3.1.2.2.1.3.8.3+H z
V$ @p W2*dZX> & 3.1.2.2.1.3.7.A. *dBW6 *vH W7
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[drives thatXwere involved, and the number of drive detected Massbus *{"Wh @p Wc(data bus) parity errors that occurred. *|*Wi @p *}Wk @p *}Wp @p WlMBox/UBA RHxx Massbus TM02/03*}2Wq @p *~Ww @p Wr write> --- DPE --------->-- PAR ---> tape *~W| @p
@p $ XSincelall Massbus,devicesacheck2datanparitydduringsdataswrite operations + :X @p # X +p @p XBackground - Refer to the Massbus Theory Overview.z
X# @p
X!*`bZ R.T.3.1.2.2.1.3.7.A.+rX% G- +:X& +P X(
bX0 @p ! X)STOP - You are moving in a reverse direction thru the menu. You are +X7 @p X1about to back into the Massbus (data bus) RH Theory. +
X9 @p +x @p
X:Your response please: +RY9 G- z
XA @p W-*vY5 " +jXB G- +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 # Xzthe errors involve apsingletape controller, then thetfaultsissprobably +Y @p $ Yin]theYTM02/03 and+has somethingto doMwith theUMassbus interfacerlogic. +*Yata Write operations) +Y( @p Y! 3. (TM02 detected) Massbus (data bus) Parity Errors. +
Y) @p +Y+ @p + @p Y, Time: 23-Mar 00:00:00 To 23-Mar 00:01:45 Span: 0:01:45 3.1.2.2.1.4.1.3+2 z
X= @p Y7+jJJ 3.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] @p YYMBox/UBA RHxx Massbus TM02/03+Y^ @p +RYd @p Y_ 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 @p Y}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 @p ZTM02/03 Control Operation Summary. +"JZ @p +# @p
Z Your response please: z
Z# @p
Z!+r[R R.T.3.1.2.2.1.3.8.A.+#rZ% G- +$:Z& +$P Z(
bZ0 @p ! Z)STOP - You are moving in a reverse direction thru the menu. You are +%Z7 @p Z1about to back into the Massbus (data bus) TM Theory. +&
Z9 @p +&x @p
Z:Your response please: +2"[ G- z
ZA @p Y2))* 6 & +'jZB G- +(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 @p Z[ Note: Function code is in octal and without the GO bit. ++*Zc @p +,"Zh @p ZdMT210 (TU45, SN: 200) reports: +,:Zj @p +-
Zn @p
Zk Media ID : TEST +-"Zo @p +-bZt @p Zp Function No. of SPAN +-zZz @p Zu code Errors Window HH:MM:SS+.JZ @p Z{ -------- ------ ------ --------+/"[ @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+GH z
Z= @p [+ 2j F.T.3.1.2.2.2.0. +'R[ +2h [
b[" @p # [That'seit.sThere.are only[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. +:*[X G- +: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\A G- z
[x @p [#vb]$ +>b[z G- +?
[{ +? [}
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 \?+:*]L R.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]Q G- 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+eP z
\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^2 G- 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 #): ,"aG G- , 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 # `errordrateaforrargiven data8track is greater@than twice the ,J` @p # `average foraallatracks, then chancesIare the readEamplifierAor the read ,Z`# @p ` head for 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`z G- ,
`{ , `}
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 ,( @p a<that occur in PE mode. z
ac @p a`,Bb` & z
^+ @p aD+pJcr R.T.3.1.2.2.2.1.1.1.A. +e:aH ,p aJ
baR @p ! aKSTOP - You are moving in a reverse direction thru the menu. You are ,"aY @p aSabout to back into the Read Data Head/Amplifier Theory.,*a[ @p , @p
a\Your response please: ,>*cw G- ,B( 3.1.2.2.2.1.1.2. ,zad G- , 2af , H ag
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 @p b each data track. ,!*b @p ,!bb @p $ b Read Data - Error Rate Greater Than 1 per Million Transfers [2.2.1.2] ,!zb @p ,#
b @p b. ReMT100t(TU70,rSN:0) reports: ,#"b# @p @p " b& Physical Track / Data Track NRZI or PE ,$Rb2 @p b. 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. ,,bf G- ,,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
@p c
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\ @p cZ- - - - - - - ,;ce @p # c]The report continues to list all read errors associated with the drive. ,;Bch @p cf- - - - - - - ,<P @p ciBackground - Refer to the Read Data Theory Overview (topic # 0) z
d @p d,,e $ z
a_ @p ct,"f R.T.3.1.2.2.2.1.1.2.A. ,rcy ,>x cz
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: ,bf G- ,f 3.1.2.2.2.1.1.3. ,>d G- ,BRd ,Bh d
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 @p dJ 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 @p d] 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. ,Qje G- ,R2e ,RH e
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; @p e8Time 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 @p ew- - - - - - - ,^jf @p # ezThe report continues to list all read errors associated with the drive. ,_f @p f- - - - - - - ,`*f @p ,`X @p fBackground - Refer to the Read Data Theory Overview (topic # 0) z
f3 @p f1,QjgB & z
d @p f,>*g$ R.T.3.1.2.2.2.1.1.3.A. ,Bf ,bh f
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: -
Zhj G- -( 3.1.2.2.2.1.1.4. ,arf5 G- ,f:f6 ,fP f8
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 @p fO Read Data Error Summary by Data Track ... [2.2.1.4] ,ijfW @p ,jZf\ @p fX 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 @p fk 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 @p g
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 $ g TOPS-10 does not keep track of the number of frames read per Tape drive. z
g) @p
g&,bhe R.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= @p g7about to back into the Data Track Summary Description. ,vbg> @p ,wP @p
g?Your response please: z
gG @p gD,arh; ( 3.1.2.2.2.1.1.5. ,x*gH G- ,xrgJ ,y gK
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 @p gfshould be copied and (if possible) cleaned and verified. ,|Rgn @p ,}Jgt @p go Read Data - Media Bad Spot Theory ... [2.2.1.5] ,}bgv @p ,~Jg} @p gw Media ID: FICHE Recording Mode: PE was identified with,~bh @p g~ read errors as noted against the following drives: ,Zh @p - Jh
@p h MT100 (TU71, SN: 0) with 20. errors. - bh @p
h Additional Data -Bh @p h Operation : READ FWD -h @p h User ID : 500000,,5 -Rh @p h 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 - @p h4 Time: 5-Jan 15:56:53 To 5-Jan 16:15:53 Span: 0:19:00 z
h? @p h=,x*hc 3.1.2.2.2.1.1.5.A. -2hA G- -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 @p h_required to satisfy this theory. z
i @p i-2_$ , z
f/ @p hg,tJj# R.T.3.1.2.2.2.1.1.5.A. ,ezhl -
bhv @p ! hnSTOPt-tYouaareimovingeinaa reversehdirection}thru the menu. You are -
h~Your response please: 3.1.2.2.2.1.2.M-; 3.1.2.2.2.1.1.6. -
2i G- -Ri -h i
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 @p i5with the errors. -Ji9 @p -i@ @p i: Read Data - Media Bad Spot Summary ... [2.2.1.6]-iA @p -iI @p iB Media ID: 7601 Recording Mode: NRZI was identified with -iP @p iJ read errors as noted against the following drives: -iQ @p -iX @p iR MT404 (TU72, SN: 28411.) with 1. errors. -i\ @p
iY Additional Data -i` @p i] Operation :READ FWD-Bie @p ia User ID :500000,,5 -
ij @p if 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 @p i Time of Error: 26-Jun 06:29:54 z
j @p
j+2"p F.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 @p jNext on the menu are the Read Operation Device Error Theories. -"Zj @p -#X @p
j Your response please: z
j' @p
j%-
Zjw R.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; @p j5about to back into the Read Operation Data Theories. -&Jj= @p -'8 @p
j>Your response please: z
jE @p jC+tJkZ 3.1.2.2.2.1.2.0. -(jG G- -(ZjH -(p jJ
bjQ @p jK 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--@ @p jusummary report.z
j{ @p
jy-$2l7 R.T.3.1.2.2.2.1.2.0.-.rj} G- -/:j~ -/P k
bk @p ! kSTOP - You are moving in a reverse direction thru the menu. You are -0k @p k about to back into the Read Operation Device Theory Overview. -1
k @p -2 @p
kYour response please: -;*k_ G- z
k @p i -t
p5 -2zk G- -3"k -38 k
bk% @p k TX01/TX02 Read Operation Device Theories-3jk' @p -4Zk* @p k(Selection Menu -4rk+ @p -5"k2 @p k, 0. Overview - TX01/TX02 Read Operation Device Theories-5:k4 @p -6*k: @p k5 1. Tape Slippage Theory ...........[2.2.2.1]-6Bk; @p -7"kA @p k< 2. Tape Slippage Summary ..........[2.2.2.2]-7:kC @p -8kI @p kD 3. Vacuum Column Sensor Summary ...[2.2.2.3]-82kJ @p -9kP @p kK 4. Device Error Summary ...........[2.2.2.4]-9*kR @p -:
kS @p -: @p kTYour selection please (topic #): .zp< G- .
h z
k @p k\-(lU ( 3.1.2.2.2.1.2.1. -2bk` -;p kb
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 @p ktlow tape column vacuum, or improper bearing pressure. ->:k| @p -?*k} @p -?Bl @p k~ Read Data - Tape Slippage Theory ... [2.2.2.1] -?Zl @p -@Bl @p l 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) @p l" 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@ @p l5this theory. z
l< @p
l9-.rmA R.T.3.1.2.2.2.1.2.1.-Fzl= G- -GBl? -GX l@
blI @p ! lASTOP - You are moving in a reverse direction thru the menu. You are -H
lP @p lJabout to back into the Read Data Tape Slippage Theory. -IlQ @p -J @p
lRYour response please: z
lZ @p lW-;*m_ * 3.1.2.2.2.1.2.2. -JZl[ G- -K"l] -K8 l^
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 @p lqlow tape column vacuum, or improper bearing pressure. -Nlx @p -Nrlz @p -O
m @p l{ Read Data - Tape Slippage Summary ... [2.2.2.2] -O"m @p -P
m @p m MT100 (TU72, SN:32896.) reports: -P"m @p -Pzm @p m
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% @p m 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 @p m: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.-XmG G- -XZmH -Xp mJ
bmR @p ! mKSTOP - You are moving in a reverse direction thru the menu. You are -Y"mY @p mSabout to back into the Read Data Tape Slippage Summary.-Z*m[ @p -[ @p
m\Your response please: z
mc @p ma-JZnH 3.1.2.2.2.1.2.3. -[rme G- -\:mf -\P mh
bmp @p # miThis report summarizes vacuum column error checks that occurred during-]mt @p
mqdata read operations. -^
mv @p -^Jm} @p mw Read Data - Vacuum Column Sensor Summary ...[2.2.2.3]-^bm~ @p -_Rn @p m MT100 (TU72, SN: 32896.) reports: -_jn @p -`Bn
@p Left Right -`Zn @p n Top/Bottom col. col. No. of Times Occurred-a"n @p n ---------- ---- ---- --------------------- -b
n @p -bzn @p n 0 0 1 5. -cn @p -cbn! @p -cx @p n" Time: 29-Mar 00:00:00 To 29-Mar 02:15:00 Span: 2:15:00 z
n- @p
n+-Xp7 R.T.3.1.2.2.2.1.2.3.-en/ G- -eZn0 -ep n2
bn: @p ! n3STOP - You are moving in a reverse direction thru the menu. You are -f"nB @p n;about to back into the Read Data Vacuum Column Sensor Summary. -g*nD @p -h( @p
nEYour response please: z
nL @p nJ-[ro ( 3.1.2.2.2.1.2.4. -inN G- -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 @p ncbit combinations. -l*ng @p -lbnn @p nh Read Data - Device Error Summary ...[2.2.2.4] -lzno @p -mbnt @p np MT300 (TU70, SN:0.) reports: -mznv @p -nJnz @p nw 0 Buss Out Check -nbn} @p n{ 0 Overruns -o"o @p n~ 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 @p owith 1. occurrence at Time: 17-Jan 22:42:49 -ro @p -rzo @p -s @p oThe definition of these status bits follow: z
o% @p o"-ik & 3.1.2.2.2.1.2.4.A. -t
o& G- -tRo( -th o)
bo2 @p # o*Bus Out Check (sense byte 0, bit 2) - means that a Bus-out parity error -uo7 @p o3was detected by the controller. -v*o9 @p -vzoB @p $ o:Overrun (sense byte 0, bit 5) - means that the tape controller transfer -woG @p oCrate 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 @p oodetect a Tach Status change. -}jot @p -~2o} @p # ouReset Key (sense byte 7, bit 3) - means that the Reset push button was-~Jp @p o~pressed after start of operation. -Rp @p . "p
@p # pC/PbCompareo(senseebyte 3,zbit 7) - means that a data path parity error . 8 @p p
p @p
p- :qM
F.T.3.1.2.2.2.1.3.1..p G- .bp .x p
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 @p pV-2z]k ( z
kX @p p9-eql R.T.3.1.2.2.2.1.2.4.A. -;
p> .H p?
bpH @p ! p@STOP - You are moving in a reverse direction thru the menu. You are .zpO @p pIabout 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. .RpZ G- . 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 @p ppwould be consideredaa softwareoerror. .re error summary ... [2.2.3.1] .bp @p .Zq @p q MT404 (TU72, SN: 28411.) reports: .rq @p .Bq @p qSense Byte Media No. of SPAN .Zq @p q
0 (octal) ID Errors Window HH:MM:SS.2q @p q---------- ----- ------ ------ --------.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 @p qF Time: 24-Jun 12:37:53 To 30-Jun 02:41:49 Span: 134:03:56 z
qQ @p qO.vD F.T.3.1.2.2.2.2.0. .RqS G- .qT .0 qV
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.zr4 R.T.3.1.2.2.2.1.3.1.. Jqr G- . 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: .&Jr9 G- z
r @p pT+]:s
.!Zr G- ."r ." r
br @p r TX01/02 Write Operation Theories ."Jr @p .#2r% @p " r Overview - 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 @p r.Device errors, or Software errors. 3.1.2.2.2.2.M.2.1x z
r
@p r6. JsR R.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 @p rEabout to back into the Write Operation Theory Overview..(JrM @p .)8 @p
rNYour response please: .2s G- z
rU @p r2/W .*RrX .*h rY
br` @p rZ TX01/TX02 Write Operation Theories .+ra @p .,rh @p rb 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 @p r 3. TX01/02 Write Operation Software Summary ...[2.2.6.1] ./js @p .0bs @p .0x @p s
Your selection please (topic #): .QRu G- .U@ z
rQ @p s.!Zt 3.1.2.2.2.2.1.0. .*s .2H s
bs @p s 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 @p sMMark, Erase Gap, and Data Security Erase. z
sV @p
sT.&Ju3.1.2.2.2.2.1.0..:"sX G- .:jsY .; s[
bsc @p ! s\STOP - You are moving in a reverse direction thru the menu. You are .;2sj @p sdabout to back into the Write Operation Theory Overview..<:sl @p .=( @p
smYour response please: z
st @p sr.dvb 3.1.2.2.2.2.1.M. .>sv G- .>Jsw .>` sy
bs @p sz TX02/02 Write Operation Data Theories.?t @p .?rt @p t 0. Overview - TX02/02 Write Operation Data Theories .@
t @p .@zt @p t
1. Bad Media Theory .........[2.2.4.1] .At @p .Ajt @p t 2. Media Bad Spot Summary ...[2.2.4.2] .Bt @p .BZt @p .Bp @p tYour selection please (topic #): z
t" @p t .2tp " 3.1.2.2.2.2.1.1. .CZt# G- .D"t% .D8 t&
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; @p t9replaced. .G
t< @p .G2tB @p t= Write Data - Bad Media Theory ... [2.2.4.1].GJtD @p .H*tI @p tE Media ID: FICHE was associated with .HBtR @p # tJ 174. read after write errors while mounted on the following drives: .ItT @p .J*tX @p tU MT300 (TU70, SN: 0.) .JBtY @p .Kt] @p
tZ Additional Data:.Kt^ @p .KRtc @p d Program ID :DUMPER .L2th @p .Lp @p ti 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
tv G- .NRtx .Nh ty
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. @p u,.N
v! ( z
s @p u.:"vd R.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% @p u about to back into the Write Operation Bad Media Theory. .SZu& @p .TP @p
u'Your response please: .lJvi G- .p0 3.1.2.2.2.2.1.2. .Q*u0 G- .Uju1 .V u3
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 @p uMerrors associated with the medium. .YJuS @p .ZuZ @p uT Write Data - Media Bad Spot Summary ... [2.2.4.2] .Z2u[ @p .["u` @p u\MT301 (TU70, SN: 0.) reports:.[:ua @p .\ug @p ubMedia No. of SPAN Program .\um @p uh ID Errors Window HH:MM:SS ID.\zuv @p " un----- ------ ------ -------- ------- .]Zu| @p uw6638 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
@p v7921 1. 12-Mar 04:53:23 TAPE20.`Jv
@p .a*v @p v vThe report will continue to list all write errors by drive. .arv @p v---------------.bh @p v Time: 11-Mar 00:33:50 To 12-Mar 12:19:06 Span: 35:45:16 z
v& @p v#.Q*sp 3.1.2.2.2.2.1.2.A. .dv' G- .dbv) .dx v*
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..hJvJ G- .ivL .i( vM
bvV @p $ vNThat's it. There are only two Write Operation Data Theories. Next on the .iZv\ @p vWmenu are the Write Operation Device Theories..jjv^ @p .kH @p
v_Your response please: z
w @p w.>x z
u* @p vf.QRw: R.T.3.1.2.2.2.2.1.2.A. .U*vk .m vl
bvu @p ! vmSTOP - You are moving in a reverse direction thru the menu. You are .mJv| @p vvabout 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"w G- .pZw .pp w
bw @p w n a summary reTX01/02 Write Operation Device Error Theories .q"w @p .rw @p # wOverview - The TX01/02 Write Operation Device Error Theories attempt to .r2w$ @p " w localize 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<.lJxu R.T.3.1.2.2.2.2.2.0..w*w@ G- .wrwB .x wC
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^ @p w\/Kr}8 3.1.2.2.2.2.2.M. .{"w` G- .{jwa .| wc
bwj @p wd TX01/TX02 Write Operation Device Theories .|2wk @p .}"wq @p wl 0. Overview - Write Device Theories .}:wr @p .~wx @p ws 1. Tape Slippage Theory ...........[2.2.5.1].~*wz @p .
x @p w{ 2. Tape Slippage Summary ..........[2.2.5.2]."x @p / x @p x 3. Vacuum Column Sensor Summary ...[2.2.5.3]/ x @p / zx @p x
4. Device Error Summary ...........[2.2.5.4]/x @p /rx @p / @p xYour selection please (topic #): z
x @p x.l"y ( 3.1.2.2.2.2.2.1. /rx G- /:x /P x
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 @p x2low tape column vacuum, or improper bearing pressure. /x: @p /
x; @p /"xB @p x< Write Data - Tape Slippage Theory ... [2.2.5.1] /:xC @p /"xI @p xD 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 @p x` Time: 29-Mar 00:00:00 To 29-Mar 02:45:00 Span: 2:45:00 / rxh @p /
rxj @p /
xr @p # xkThresholdo-yAt least six velocity check errors are required to satisfy/
xz @p
xw.w*yx R.T.3.1.2.2.2.2.2.1./Zx{ G- /"x} /8 x~
by @p ! xSTOP - You are moving in a reverse direction thru the menu. You are /jy @p yabout to back into the Write Operation Tape Slippage Theory./ry @p /h @p
yYour response please: z
y @p y/rz ( 3.1.2.2.2.2.2.2. /By G- /
y / y
by& @p $ y Theory - 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 @p y/low tape column vacuum, or improper bearing pressure. /jy7 @p /Zy8 @p /ry? @p y9 Write Data - Tape Slippage Summary ... [2.2.5.2]/
y@ @p /ryF @p yA MT100 (TU72, SN:32896.) reports: /
yG @p /byO @p yH 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 @p y\ 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/Zzc R.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 @p z
about to back into the Write Operation Tape Slippage Summary. /!z @p /" @p
zYour response please: z
z @p z/B{ 3.1.2.2.2.2.2.3. /"rz G- /#:z /#P z
bz( @p # z!This report summarizes vacuum column error checks that occurred during/$z, @p
z)data read operations. /%
z. @p /%Jz/ @p /%bz7 @p z0 Write Data - Vacuum Column Sensor Summary ... [2.2.5.3] /%zz8 @p /&rz> @p z9 MT100 (TU72, SN:32896.) reports: /'
z? @p /'bzD @p Left Right /'zzJ @p zE Top/Bottom col. col. No. of Times Occurred/(BzQ @p zK ---------- ---- ---- --------------------- /)*zS @p /*zX @p zT 1 0 0 5. /*2zY @p /+z[ @p /+ @p z\ 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./,2zi G- /,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:06 z
{j @p {h/0*|_ * 3.1.2.2.2.2.2.4.A. /<b{l G- /=*{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/<bwZ 3.1.2.2.2.2.2.4.B. /Kr|e G- /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} @p e }Write Trigger 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~l R.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.20p 3.1.2.2.2.2.3.1. /W}^ G- /[J}_ /[` }a
b}j @p # }bThisyreportdsummarizesfmagtapeSerrors/thought to becausedaby 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/RCL F.T.3.1.2.2.2.3.0. /iZ~S G- /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+S R.T.3.1.2.2.2.2.3.1./mB~r G- /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.*+ ' , /qR G- /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< @p 7(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 @p P 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 @p w |-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@ /
c 7 @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 Massbus 0{ F @p @Controller (RH11, or RH20), or the Adapter (DX20).0{ G @p 0c P @p $ H Both Massbus controllers (RHs) and Massbus devices (DX20s) check parity 0{ Y @p # Q on the Massbus (data bus). The parity is checked during read and write 0
^ @p Z operations as illustrated below. 0 ` @p 0 k a @p 0
j @p " b UBA RH11 Massbus DX20 Chan Bus TXxx TU Bus Drive 0
r @p k reade <--- DPEck <---------> CERR <--------- C/PCK <-------- 0# { @p 0# @p " | MBox RH20 Massbus DX20 Chan Bus TXxx TU Bus Drive 0;
@p >read <----DPE---<-----------CERR-><-----------C/P-> <-------- 0@ @p 3.1.2.2.2.3.0.B. 0C G- 0 0
c% @p The last two reports summarize DX10/20 Data Channel Bus Errors. 0S& @p 0S- @p ' Mem DX10 Chan Bus TXxx TU Bus Drive 0k3 @p . read <--- CERR <--------- C/P <-------- 0S9 @p 4 write---> no ck---------> BO CK --------> 03: @p 0C @p # ; MBox RH20 Massbus DX20 Chan Bus TXxx TU Bus Drive0+K @p D read <--- DPE <--------- CERR <--------- C/P <-------- 00 @p L write ---> DPE ----------> CERR ---------> BO CK --------> z W @p
U/mC7 R.T.3.1.2.2.2.3.0.B.03Y G- 0{Z 0 \
cd @p ! ]STOP - You are moving in a reverse direction thru the menu. You are 0Ck @p eabout to back into the Massbus Theory Overview. 0 Kl @p 0 0 @p
mYour response please: 0:{\ G- z t @p %2(
, 0 #v G- 0 Kw 0 ` y
c @p ! z DX10/20 Massbus (control bus/data bus) and Channel Theories 0 @p 0 @p Selection menu 0 3 @p 0 c @p 0. Overview - Massbus (control bus/data bus) Theories 0 { @p 0!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# " @p 0$+ @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 @p 0&;= @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 @p 0*sa @p " Y 9. Channel Error Summary .................................[2.2.7.9] 0+ i @p " b10. Channel Buffer Theory .................................[2.2.7.10] 0,k @p 0-l @p 0-0 @p mYour selection please (topic #): z u @p s0CW 3.1.2.2.2.3.1. 0.w G- 0.[x 0.p z
c @p $ {Theory - If a tape subsystem reports Massbus (control bus) parity errors 0/# @p " or Massbus timeout errors, and if the errors involve two or more DX20 003 @p #
Adapters, then3chances)arepthesfault6lies@in theRH Massbusbcontroller01; @p $ orotheaMassbusecable. If,0however, theerrorslarenlocalttolaesingle2DX20 02C% @p # thenechances are@the fault9isOinpthe DX20 andEhasrsomething5toDwith do03S* @p &the Massbus interfacerlogic. 04[+ @p 05#3 @p ,RH1CBUS.Error.-0Massbus(control bus).RHtheory.[2.2.7.1] 05;4 @p 0639 @p
cg @p ! `Threshold - At least two (RH detected) Massbus (control bus) parity 0;sp @p " herrors or Massbus (control bus) timeouts are required to satisfy this 0<{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 were 0?
@p ! involved, and the total number of Massbus (control bus) errors that 0@
@p occurred. 0A# @p 0AK @p ! MBox/UBA RHxx Massbus DX20 Chan Bus TXxx TU Bus Drive 0Ac @p 0Bk @p <rd/wr> --- CPE <------->.- CBPE <---------- <------ 0C% @p ! 0C{- @p & !_ CBPE <---------- <------ 0D[. @p 0ES0 @p 0Eh @p 1Background - Refer to the Massbus Theory Overview. z ; @p 903j R.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 are 0HO @p Iabout to back into the Massbus (control bus) RH Theory.0I Q @p 0Ix @p
RYour response please: 0_[ G- z Y @p U22c 2 0JkZ G- 0K\ 0K( ]
cf @p $ ^Theory - If a tape subsystem reports Massbus (control bus) parity errors 0K[o @p " gor Massbus timeout errors and if the errors involve two or more DX20 0Lkw @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 DX20 0N{ @p # then chances are the fault is in the DX20 and has something to do with0P
the Massbus interface logic. 0Q @p 0Q[ @p # RH CBUS Error - Massbus (control bus) DX20 Controller Theory [2.2.7.2]0Qs @p 0R{ @p MT315 (TU70, SN: 0) was identified with 0S& @p 4. Massbus (control bus) Parity Errors detected by 0Ss. @p ! ' Controller (Adapter) no: 1 (DX20) connected to channel 3 (RH20). 0Tc0 @p 0Uk8 @p 1 Time: 29-Mar 00:30:00 To 29-Mar 02:15:00 Span: 1:44:60 0V9 @p 0WB @p # :Note: If the system only has one DX20 tape subsystem then the fault may 0WK @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) parity 0Y3\ @p " Terrors or Massbus (control bus) timeouts are required to satisfy this 0Z;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 Massbus 0\Sr @p n(control bus) errors that occurred.0]Ss @p 0^#u @p 0^8 @p vBackground - Refer to the Massbus Theory Overview.3.1.2.2.2.3.3.30q8 z U @p 2=+p R.T.3.1.2.2.2.3.2. 0JS 0`
cp ! STOP - You are moving in a reverse direction thru the menu. You are 0`S @p about to back into the Massbus (control bus) DX theory.0a[ @p 0bH @p
Your response please: 0qC G- z @p {0Jk
$ 0c; G- 0cc! 0cx "
c+ @p " #TheoryH-0Ifraptape:subsystem@reportscMassbusM(datasbus)tparity errors 0d+3 @p " ,duringhdata reads,@andifthe errorslinvolvecmultiplerDX20dAdapters, 0e3< @p # 4then chances arethefault lies inreither the1(RH20)2MassbusTcontroller 0f;E @p ! =or theMassbus cable. If,ohowever,2the errors involve0a single0DX20 0gKM @p " Fthen,chances:are-the fault:liesTin2theaDX20:and1has something:to:do 0hSR @p NwithPthezMassbusinterfacelogic. 0i[T @p 0j+\ @p " U RHDPE Error-Data Read/Massbus (data bus) RH theory ... [2.2.7.3] 0jC^ @p 0kKb @p
c @p # Threshold - At least two (RH detected) Massbus (data bus) parity errors 0r;% @p $ are required to satisfy this theory. The errors must involve two or more 0sK. @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 that 0uk? @p " 8were involved. The report also lists the number of Massbus (data bus) 0vsD @p @parity errors that occurred. 0w{E @p 0xCN @p # FMBox/UBA RHxx Massbus DX20 Chan Bus TXxx TU Bus Drive 0x[P @p 0ykX @p Q <read --- DPE <---------.- DBPE <------------ D CK <------ 0z^ @p Y ! 0{f @p _ !_ DBPE <------------ D CK <------ 0{kh @p 0|ki @p 0} @p jBackground - Refer to the Massbus Theory Overview.z t @p
r0_[ b R.T.3.1.2.2.2.3.3.A.0~v G- 0~Kw 0~` y
c @p ! zSTOP - You are moving in a reverse direction thru the menu. You are 0 @p about to back into the Massbus (data bus) RH Theory. 1
@p 1 @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 errors 1k' @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 controller 1{9 @p ! 1or the Massbus cable. If, however, the errors involve a single DX20 1 A @p " :then, chances are the fault lies in the DX20 and has something to do 1F @p Bwith the Massbus interface logic. 1H @p 1kP @p # I RH DPE Error - Data Read/Massbus(data bus) DX20 Theory ... [2.2.7.4]1 R @p 1
X @p S MT100 (TU70, SN: 0.) was identified with 1
#^ @p Y 4. Massbus (data bus) Parity Errors detected by 1 g @p " _ Controller (Adapter) no: 0. (DX20) connected to channel 1. (RH20). 1 kh @p 1
sp @p i1Time:p29-Mars00:45:00 tTo 29-Mar 02:15:00 onSpan:0 t1:30:00s 1m then the fault may 1 @p ! |lie in either the RH20 or the Massbus interface logic in the DX20. 3.1.2.2.2.3.5.312P z @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 same 1[ ' @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 @p 1S ? @p # 7MBox/UBA RHxx Massbus DX20 Chan Bus TXxx TU Bus Drive 1k A @p 1{ I @p B <read --- DPE <---------.- DBPE <------------ D CK <------ 1 O @p J ! 1 X @p " P !_ other error free DX20 tape subsystems 1{ Y @p 1 [ @p 1 @p \Background - Refer to the Massbus (data bus) Introduction. z g @p
d0~
R.T.3.1.2.2.2.3.4.A.1 + h G- 1 s j 1 k
c t @p ! lSTOP - You are moving in a reverse direction thru the menu. You are 1 ; { @p uabout to back into the Massbus (data bus) DX20 Theory. 1 C | @p 1 0 @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 controllers 1"
" @p
(RH11/20), then chances are the fault has to do with the memory 1##
* @p !
#controller or the channel. If, however, the errors involve a single 1$#
3 @p #
+Massbus controller and multiple (DX20s) Adapters, then chances are the1%+
; @p "
4fault lies in the Massbus controller or the Massbus. Finally, if the 1&3
D @p "
<errors involve a single DX20, then the fault is probably in the DX20 1';
K @p
Eand has something to do with the Massbus interface logic. 1(C
M @p 1);
V @p $
N RH DPE Error - Data Write/Massbus(data bus) MBOX (UBA) theory [2.2.7.5] 1)S
W @p 1*c
` @p #
X 2. different RH controllers report: (during data Write operations) 1*{
f @p
a 5. Massbus (data bus) Parity Errors. 1,
h @p 1,k
k @p
i Additional Data: 1-
m @p 1-;
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 @p 11 @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
@p 1 #
" $ 3.1.2.2.2.3.5.A. 1 13
c & @p # Threshold - At least two (RH detected) Massbus (data bus) parity errors 13S / @p $ 'are required to satisfy this theory. The errors must involve two or more 14c 8 @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 that 17 I @p " Aoccurred and the number of different controllers that were involved. 18 J @p 19 L @p 19+ T @p ! M MBox RH20 Massbus DX20 Chan Bus TXxx TU Bus Drive 19C V @p 1:K ] @p W .--> DPE ----------> DBPE ------> D CK ------> 1:c ` @p ^write>---!1;[ g @p a `--> DPE ----------> DBPE ------> D CK ------> 1< i @p 1<{ q @p ! jSince RH11s do not check parity during a data write operation, this 1= y @p rtheory only applies to RH20/DX20 controlled tape subsystems.1> z @p 1? | @p 1?( @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 are 1A;
@p
about to back into the Massbus (data bus) MBox Theory. 1BC
@p 1C0 @p
Your-response please: 1RK
$ @p 12[
& 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 controllers 1F
B @p
;(RH11/20), then chances are the fault has to do with the memory 1G#
J @p !
Ccontroller or the channel. If, however, the errors involve a single 1H#
S @p #
KMassbus controller and multiple (DX20s) Adapters, then chances are the1I+
[ @p "
Tfault lies in the Massbus controller or the Massbus. Finally, if the 1J3
d @p "
\errors involve a single DX20, then the fault is probably in the DX20 1K;
k @p
eand has something to do with the Massbus interface logic. 1LC
m @p 1M;
n @p 1MS
w @p #
o RH DPE Error - Data Write/Massbus(data bus) RH theory ... [2.2.7.6]1Mk
x @p 1Ns
y @p RH No:(1. (RH20)ereportsb(duringaData)Writetoperations) 1O
@p 1Q @p 0 To 29-Mar 02:15:00 Span: 2:15:00 3.1.2.2.2.3.7.31t8 z
@p " 3.1.2.2.2.3.6.A. 1D
c @p # dr-dAtoleaststwot(RHXdetected)hMassbuss(dataebus)lparityherrors 1SC
1@+ R.T.3.1.2.2.2.3.6.A.1_k G- 1`3 1`H
c @p ! STOP - You are moving in a reverse direction thru the menu. You are 1`{ @p about to back into the Massbus (data bus) RH20 Theory. 1b @p 1bp @p
Your(response please: 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 controllers 1e[> @p 7(RH11/20), then chances are the fault has to do with the memory 1fcF @p ! ?controller or the channel. If, however, the errors involve a single 1gcO @p # GMassbus controller and multiple (DX20s) Adapters, then chances are the1hkW @p " Pfault lies in the Massbus controller or the Massbus. Finally, if the 1is` @p " Xerrors involve a single DX20, then the fault is probably in the DX20 1j{g @p aand has something to do with the Massbus interface logic. 1li @p 1l{q @p " j RH DPE Error - Data Write/Massbus(data bus) RH theory ... [2.2.7.7] 1ms @p 1nz @p t RH No: 1. (RH20) reports (during Data Write operations) 1n3 @p { 5. Massbus (data bus) Parity Errors as detected by the 1o+ @p following drive controllers: 1p+ @p 1p{ @p
3. Errors detected by MT100 (DX20: 0,TU70, SN: 0.)1q @p 1r @p 2. Errors detected by MT110 (DX20: 1,TU70, SN: 0.)1r @p 1s @p Time: 29-Mar 00:00:00 To 29-Mar 02:15:00 Span: 2:15:00 3.1.2.2.2.3.8.32 z @p &1cc@ & 3.1.2.2.2.3.7.A. 1cK* 1u +
c4 @p ! ,Threshold - At least two{(DX20 detected) Massbus (data bus) parity 1u;< @p # 5errors-(PAR)1are~requiredto satisfy this theory.pThe errors must have1vCD @p r =beenHdetectedsbystwoeor moreDX20spand they must@be$commonitoethe1wKM @p # EsamehRHkcontroller.yTherreporttidentifiesetheiRHscontroller, thenumber 1xKV @p " NoftDX201Adapters2thatnwerelinvolved,uandsthesnumberofpDX20 detected 1y[\ @p WMassbusf(data bus)Mparity errors thatvoccurred. 1zc^ @p 1{Kf @p ! MBox RH20 Massbus DX20 Chan Bus TXxx TU Bus Drive 1{ch @p 1|ko @p iwrite> ---.- 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 are 29 @p 3about to back into the Massbus (data bus) RH Theory. 2#: @p 2 @p
;Your response please: 2#6 G- z B @p !1tC2 2D G- 2+E 2@ 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 controllers 2 {` @p Y(RH11/20), then chances are the fault has to do with the memory 2 h @p ! acontroller or the channel. If, however, the errors involve a single 2
q @p # iMassbusicontrollerMandbmultipleo(DX20s) Adapters,uthenichancesiarehthe2 @p " zerrors involve a single DX20, then the fault is probably in the DX20 2 @p and has something to do with the Massbus interface logic. 2# @p 2 @p !
RH DPE Error - Data Write/Massbus(data bus) DX20 theory [2.2.7.8] 23 @p 2; @p ! MT100 (TU70, SN: 0.) reports: (during Data Write operations) 2S% @p 4. (DX20 detected) Massbus (data bus) Parity Errors. 2[& @p 2S( @p 2h @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 > @p 42A $ 3.1.2.2.2.3.8.A. 2k8 2h 9
cA @p :Threshold - One or more (DX20pdetected) Massbus (data bus) parity2J @p # Berrors areerequiredeto2satisfy this theory.@The errors;mustpinvolveSthe 2S @p ! KsamehDX20dand theytmustrhavedoccurrededuringtdata writeoperations. 2+T @p 23\ @p UMBox/UBA conRHxxleMassbussubDX20emChan Bus @TXxx TU Bus @pDrive2K^ @p 2Ke @p s write>2---aDPEsu--------.-eDBPEe --------> D CK!-------> 2cj @p either the RH20 or the Massbus interface logic in the DX20. 2" @p 2# @p Background - Refer to the Massbus Theory Overview.z & @p
#2 x R.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 are 2%+: @p 4about to back into the Massbus (data bus) DX20 Theory. 2&3; @p 2' @p
<Your response please: 2/ } G- z C @p /2#r 2(E G- 2(;F 2(P H
cI @p 2)Q @p JDX10 Data Channel Error Summary (DX10 only)... [2.2.7.9] 2)R @p 2*X @p S MT260 (TX02, TU70, SN: 0) reports: 2*+[ @p
Y 4. Channel Errors.2+] @p 2+;` @p ^------------------- 2+Si @p # aThe report continues to list each drive associated with Channel errors. 2, m @p j------------------- 2-n @p 2-P @p o 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$A1 R.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 are 20 @p about to back into the Channel Summary Report. 21 @p 21p @p
Your response please: 29KQ G- z @p v0:{V 22c G- 23 23
c% @p Write Device Error - DX20 Channel Error Summary ... [2.2.7.10] 23S& @p 24S+ @p ' MT300 (TU70, SN: 0.) reports: 24k/ @p
, 3. Channel Errors 25;1 @p 25{4 @p 2------------------- 26= @p # 5The report continues to list each drive associated with Channel errors. 26KA @p >------------------- 27[B @p 28 @p C 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/iXNd F.T.3.1.2.2.2.4.1. 22KR 2: T
c] @p $ UThat's it. There are only eight Massbus Theories and two Channel Summary 2:Ce @p ^Reports. Next on the menu is TX01/02 Control Operation Summary. 2;Sf @p 2<P @p
gYour response please: z o @p l0Fs} R.T.3.1.2.2.2.3.10. 2=+p G- 2=sr 2> s
c| @p ! tSTOP - You are moving in a reverse direction thru the menu. You are 2>; @p }about to back into the Massbus Channel Buffer Theory. 2?C @p 2@0 @p
Your response please: 2K#^ G- z
@p J0 "\[ $ 2A# G- 2AK 2A`
c @p This report summarizes all non read/write errors. 2B @p 2B{ @p Control Operation Error Summary ...[2.2.8.1] 2C! @p 2C{( @p " Note: Function code is in octal and without the GO bit. 2D* @p 2E / @p + MT300 (TU70, SN: 0.) reports: 2E#2 @p 0 Media id : unk. 2Es4 @p 2F+9 @p 5 Function No. of SPAN 2FC> @p : code Errors Window HH:MM:SS2GD @p ? -------- ------ ------ --------2GkE @p 2HCK @p F 1 1. 14-Jan 19:55:35 2H[L @p 2I3R @p M Error bits set in the sense bytes: 2IKT @p 2J( @p
U INTERVENTION REQD 3.2.0._tapR.T.3.2.0.z @p
\;@Ln end_of_tape_theories2A ` 2Kh a
cj @p $ bThat's it. There are only 28 TX01/02 tape theories and summaries. If you 2Ls @p $ khave any comments or suggestions for improving the TX01/02 Tape Theories 2M+w @p tplease let us know. 2N;x @p 2Ns| @p
y Thank you 2O ~ @p 2OK @p
The Spear Team2Oc @p MR1-2 S/35 2P @p 2PS @p 2Ph @p " Press the RETURN key or type MENU to return to the Tape Theory menu. You can:..z @p WcP * 2R G- 2RC 2RX
c @p The BigpPicture 2]sxInputFile 2S " @p :..... 2^; @p : 2Sc) @p #Retrieveeaccepts event : ..........:......... 2T#0 @p *filesrand packet files. ASCII : Binary 2 s : 2U5 @p 1 Event File Packet File 2V< @p 6The Selected information .....:..... : 2V[C @p =in an event file can be: : : : 2WKK @p DIncluded in, or Excluded Include Exclude Packet 2X;R @p Lfrom, the output file. :.........: Numbers 2Y3W @p S : : 2Z+^ @p XOne or more Packets can Selection and : 2Z{e @p be selected from a Packet Time Criteria : 2[kk @p ffile. :..................: 2\[o @p l : 2]3s @p
@p savestheyselected entries :2aH :.........:2`c @p Output File z @p X#XB! 2bs G- 2c 2c0
c& @p ! STOP - You are moving in a reverse direction thru the menu. You are 2c` @p 'about to back into the Retrieve Overview. z 0 @p .5$;PT 3.2.M. 2eK1 G- 2f3 2f 4
c: @p 5 Spear Library - Retrieve 2fK< @p 2g+? @p =Topic menu: 2gC@ @p 2gsB @p 2h E @p C0. Overview 2h#F @p 2hSJ @p G1. Retrieve Dialog 2hkK @p 2i @p L2. Retrieve Questions & Answers z T @p R2RP, , 3.2.1. 2j U G- 2jCW 2jX X
ca @p ! YThetbasicyRetrieve:dialogconsists of2nine prompts: eight selection 2k f @p bprompts and one confirmation prompt. 2lh @p 2lkk @p iRETRIEVE mode 2mn @p l------------- 2m3t @p o Event or packet file (SYSTEM:ERROR.SYS): 2mcu @p 2nCz @p v Selection to be (INCLUDED): 2n[| @p 2o+ @p
@p 2qCTime to (LATEST): 2q
TypeOutputtmoden(ASCII):O2q[ @p 2r @p 3.2.1.A.Report)format (SHORT):2r3 @p 2r{ @p Output to (DSK:RETRIE.RPT): 2s @p 2s` @p
c0 @p e first selection prompt: 2uC2 @p 2v 8 @p 3 Event or packet file (SYSTEM:ERROR.SYS): 2v#9 @p 2wB @p " :allow you to specify the name of the input file. Retrieve accepts two 2wK @p # Ctypes of files: standard system event files (such as those generated by 2x#S @p " LTOPS-10, TOPS-20, or VAX/VMS systems), and Packet files generated by 2y3V @p TAnalyze. 2z;W @p 2zc` @p $ XIf you specify a system event file Retrieve will continue with the basic 2z{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~#| @p 23 @p $ }This prompt also supports standard Help and question mark (?) responses. 2H @p Before we go on, would you like to review the Help message ?z @p 54c+= * 3.2.1.B. 3S G- 3 3
c @p " If you specify a Packet file at the input file prompt, Retrieve will 3S% @p prompt you for the packet numbers that you want to select. 3[& @p 3S. @p ' Event or packet file (SYSTEM:ERROR.SYS): DSK:A1225.PAK<CR> 3k0 @p 3k4 @p
1 Packet numbers: 35 @p 3C> @p # 6Each numbered packet contains a list of sequence numbers. The sequence3[F @p " ?numbers identify the individual records that were used by Analyze as 3cO @p " Gevidence to support the theories listed in the corresponding Analyze 3kW @p # PReport file. There is one packet for each theory listed in the report.3 sY @p 3
{a @p " ZYou can use Retrieve to translate (or save in a separate binary file) 3 j @p # bthe records listed in the packet files. Typically, you would translate3
s @p $ kaopacketrifayourwantedrtohexamineotheorecordsethat wererusedfasoevidence 3@p ! |building or maintaining a history file for a particular device or a 3; @p specific type of error. 3C @p 3 @p $
This prompt also supports standard Help and Question mark (?) responses. 3 @p Would you like to review the Help message ? z @p 57[,/ , 3.2.1.C. 3 G- 3C 3X
c) @p # !If you specify multiple packet numbers, each number should be separated 3 2 @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 and 3#D @p $ <translated (or saved) according to sequence numbers. In other words, the 33K @p Erecords will not be grouped according to packet number.3CL @p 33U @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 Event 3[k @p gFile dialog and the Packet File dialog. 3 cm @p 3 ;u @p n Event or packet file (SYSTEM:ERROR.SYS): DSK:A1225.PAK<cr> 3 Sv @p 3 S{ @p w Packet numbers: 3,7,14<cr> 3 k} @p 3 ; @p
~ Outputumoden(ASCII):R3 S @p 3! @p 3!X @pReportformat (SHORT):3 + @p 3 s
c# @p Backato therbasic Retrieveidialog.rTheosecondeselectioneprompt: 3#;% @p 3$;+ @p &ginaEvent orppacketlfilel(SYSTEM:ERROR.SYS): 3$S0 @p , @Selection2to bep(INCLUDED): ? 3%33 @p 1ts staINCLUDED 3&6 @p 4mark (EXCLUDED 3&37 @p 3&c@ @p # 8allows yourtoispecifyHwhethersthe selected entrieswill be included.in, 3&{I @p # Aor excluded from, the output file. Included is the normal response. If, 3( R @p " Jhowever, you specify Excluded, then ALL the entries in the input file 3)[ @p $ S(except those that you select later in the dialog) will be extracted and 3*#` @p \translated or saved in the output file. 3+3b @p 3, j @p " cThe Exclude feature is used to purge entries from a system event file 3,#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 to 3.3 @p $ }fill up with Network entries; since you know what caused the problem you 3/C
c7 @p # /Theithirdpselection promptBallows you3specify oneof the fiveLselection 35k: @p 8categories.l 36{< @p 37+@ @p p # K file. You can further qualify the selection at the Time prompts. 39+U @p 3:;] @p # V NONERROR - indicates that you want to select only the non-error3:Sf @p ! ^ type entries. (i.e., statistical information, configuration 3;[o @p # g changes, etc.) Refer to the Spear Reference Card. Again, you can 3<cv @p p further qualify the selection at the Time prompts. 3=sx @p 3>k @p $ y SEQUENCE - indicates that you want to select entries according to 3? @p sequence numbers. This response will be explained next. 3@
@p 3A @p " CODE - indicates that you want to select entries based on the 3A+ @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 & @p 3DS / @p # ' ERROR - indicates that you want to select error related entries. 3Dh @p 0 This response will be explained in detail later.z : @p 834k O 3.2.1.F. 3Fk ; G- 3G# = 3G8 >
c G @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 ?z S @p Q3Fk 7 3.2.1.G. 3I{ T G- 3J3 V 3JH W
c ` @p " XWhen youtspecifyaSEQUENCE inmresponseuto thes"Selectionmtype"mprompt, 3J{ h @p ! aRetrieveiwillypromptiyoutforfthetsequencetnumberscthatmyou wanthto 3L k @p iselect. 3M l @p 3M3 r @p m by aSelection.type (ALL):eSEQUENCE<cr> 3MK s @p 3N# y @p t want tSequence numbers: 22,24,35-67,12<cr> 3N; { @p 3O @p $ |YouhcanpselectaasomanypsequencennumberslasayouQwant.oIndividual sequence 3O3 @p 2Would you like to review the Help message ? z : @p 93I{ 3.2.1.H. 3Vs < G- 3W+ = 3W@ ?
c H @p $ @If you specify CODE in response to the "Selection type" prompt, Retrieve 3Ws O @p Iwill prompt you for the event codes that you want to select.3Y Q @p 3Y{ V @p R Selection type (ALL): CODE<cr>3Z W @p 3Zc \ @p X Event codes: 133,161-163<cr>3Z{ ^ @p 3[K g @p # _You can select as many event codes as you want. Each event code must be 3[c o @p " hseparated by a comma. You can also select groups of event codes. The 3\s x @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; 161 3_ @p thru 163. 3` @p 3`C @p $ This prompt also supports standard Help and Question mark (?) responses. 3`X @p Would you like to review the Help message ? z @p 3Vs , 3.2.1.I. 3bK G- 3c 3c
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 this 3dS 7 @p # /dialog until you indicate that you are finished making your selections. 3ec @ @p # 8There are eleven error classes. Excluding ALL, which indicates that you 3fs I @p # Awant to select all the error entries, each of the error classes will be 3h O @p Jexplained in the order that they appear below. 3i Q @p 3i{ U @p R Selection type (ALL): ERROR 3j W @p 3j[ [ @p
X Error class (ALL): ?3js ] @p \ ALL3k3 ` @p ^ FINISHED3k[ d @p a MAINFRAME 3l g @p e DISK 3lC j @p h TAPE 3ls m @p k UNITRECORD 3m# p @p n COMM 3m[ s @p q NETWORK 3n v @p t SOFTWARE3n; y @p w CRASH 3nk | @p z PACKID 3o @p } REELID z @p 3bK 3.2.1.J. 3o{ G- 3p3 3pH
c @p # Before we continue, however, would you like to review the Help message3px @p associated with the "Error class" prompt ? z @p 3o{ ( 3.2.1.K. 3rc G- 3s 3s0
c ' @p $ If you specify MAINFRAME in response to the Error class prompt, Retrieve 3sc - @p (will prompt for specific Mainframe devices. 3ts . @p 3uS 3 @p / Selection type (ALL): ERROR 3uk 4 @p 3v3 9 @p 5 Error class (ALL): MAINFRAME 3vK ; @p 3w ? @p < Mainframe devices (ALL): ? 3w3 A @p 3w{ H @p B ALL - indicates that you want all central processor, 3x Q @p ! I memory and front-end related error records. 3y Y @p # R CPU - indicates that you want all central processor,3z ` @p Z related error records. 3{ h @p a MEM - indicates that you want all memory related error 3| k @p i records. 3} r @p l FE - indicates that you want all front-end related3}3 u @p s error records. 3~# w @p 3~[ @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. 4 c G- 4
40
c @p $ If you specify DISK in response to the Error class prompt, Retrieve will 4c @p prompt for specific disk drives. 4s @p 4C " @p Selection type (ALL): ERROR 4[ $ @p 4+ ( @p % Error class (ALL): DISK4C * @p 4 . @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 > @p 4S 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 enter 4k V @p Pyour selections directly at the error class prompt. 4 s W @p 4
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
s o @p 4hisdpromptialsoosupportststandardmHelpgand Questionpmark(?) responses. 4M. 4k! G- 4#! 48 !
c! @p $ !If you specify TAPE in response to the Error class prompt, Retrieve will 4k! @p !prompt for specific tape drives. 4{! @p 4K! @p ! Selection type (ALL): ERROR<cr> 4c! @p 4;!" @p ! Error class (ALL): TAPE<cr> 4S!# @p 4#!' @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 @p 4k!@ @p !9You can select ALL tape entries, specific tape subsystems, or any4!H @p " !Acombination of logical and physical device names. You can also enter 4!O @p !Iyour selections directly at the error class prompt. 4 !Q @p 4{!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 @p 4 c!p @p $ !hThis prompt also supports standard Help and Question mark (?) responses. 4 x @p !qWould you like to review the Help message ? z !z @p !x4k"b & 3.2.1.N. 4 k!{ G- 4 #!} 4 8 !~
c" @p !IfeyouwspecifymUNITRECORDciniresponseetortheeError.classprompt, 4 k"[" @p " Selection type (ALL): ERROR<cr> 4!s" @p 4"K" @p " Error class (ALL): UNITRECORD<cr>4"c" @p 4#;"! @p " Unit record devices (ALL): ?4#S"# @p 4$"+ @p "$ ALL - indicates that you want to select all error records 4$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 records 4&;"B @p "= that pertain to line printers. 4'C"K @p " "C CDR - indicates that you want to select all error records 4(+"P @p "L that pertain to card readers. 4)3"Q @p 4*"S @p 4*"\ @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 "d4 k#B & 3.2.1.O. 4,#"g G- 4,["h 4,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/;# @p 40## @p
#COMMUNICATIONS - selects:40;#
@p DL4Hardware 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#& @p 44S#* @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 @p 47 @p # #:There are no Help messages associated with these error classifications. z #F @p #D4,#$9 , 3.2.1.P. 48+#G G- 48c#I 48x #J
c#S @p " #KIf you specify CRASH in response to the Error class prompt, Retrieve 49+#X @p #Twill prompt for specific Crash Codes 4:3#Z @p 4; #_ @p #[ Selection type (ALL): ERROR<cr> 4;##a @p 4;{#f @p #b Error class (ALL): CRASH<cr>4<#g @p 4<c#k @p
#h Crash codes (ALL):4<{#l @p 4=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 Code 4>S$ @p #~name from either the Analyze Report or the Summarize Report.4?[$ @p 4@S$ @p 4@k$ @p ! $ The TOPS-10 STOPCODES are described in the Stopcodes Specification 4A$ @p $section of The TOPS-10 Software Notebook set (Volume 16). 4B $ @p 4C$" @p " $The TOPS-20 BUGHLTs, BUGCHKs, and BUGINFs are described in the BUGHLT 4C$* @p ! $#Document section of the TOPS-20 Software Notebook set (Volume 16). 4D#$, @p 4E+$4 @p # $-The VAX/VMS BUGCHECKS are described in the VAV/VMS Software Specialist4E@ @p $5Notebook (a one volume set). z $< @p $;48+$Q 3.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$V G- 4JK$W 4J` $Y
c$a @p " $ZIf you specify PACKID in response to the Error class prompt, Retrieve 4K$h @p $bwill prompt for specific pack or structure names. 4L$i @p 4M$o @p $j Selection type (ALL): ERROR<cr> 4M$p @p 4Ms$v @p $q Error class (ALL): PACKID<cr> 4N $w @p 4Nc$} @p $x Disk (structure) IDs: PS,JUICE<cr> 4N{$~ @p 4OS% @p # $You can enter as many pack or structures as you want. Each ID should be 4Ok% @p
%separatedbypa comma. 4P{%# %IMPORTANT NOTE: Normally, when you specify a pack or structure name you 4Qk% @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%) @p 4U%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 " %AIf you$specifyiREELIDpinaresponseotostheaError classaprompt,tRetrieve 4X %O @p %JwillPpromptfor&specificoreelkIDsooretape labels. 4Y%Q @p 4Y{%V @p %R&~ Selection.typeC(ALL):-ERROR<cr> 4Z%X @p 4Zk%] @p %Y Error class (ALL): REELID<cr> 4[% @p 4[[%d @p %` Tape (reel) IDs: ACCT,BAR,6751<cr> 4[s%f @p 4\K%o @p # %gYou can enter as many reel IDs as you want. Each ID should be separated 4\c%r @p %pby a comma. 4]s%s @p 4^#%u @p 4^;%~ @p # %vIMPORTANT NOTE: Again, when you specify a reel ID, normally you delimit 4^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)the first&pass throughgthe Error class dialogrloop,a 4dC&4 @p &-Retrieve@changes the&default response from(ALL)htoF(FINISHED). 4eK&6 @p 4fK&: @p e that you have completed the 4hC&V @p $ &Nselection process, and that you are ready to specify the time parameters. 4iS&W @p 4jc&` @p # &XYou can, if you like, verify your selections before you go on by typing 4j{&i @p $ &a/SHOW. Retrieve will list the selections made up to that point, and then 4l &r @p " &jrepeat the "Error class (FINISHED)" prompt. If you are satisfied with 4m&z @p # &sthe selections you can press the RETURN key and Retrieve will go on to4n @p &{the Time dialog. z ' @p ' 4cC'V 3.2.1.U. 4oc' G- 4p' 4p0 '
c' @p # 'If you are not satisfied, however, you can specify the error class that 4pc' @p " 'you want to add or change. Then, you can add to the selection list by 4qs' @p $ 'entering the item that you wish to add. For example, suppose you entered 4r{') @p # '!a list of five sequence numbers (1,7,12,22,45) and then you decide that 4t '2 @p " '*you want to add one more sequence number to the list (67); you do not 4u': @p # '3have to retype the entire list. You only need to enter the new number.4v#'< @p 4w+'E @p # '=If, however, you want to change the list, then you must type /CLEAR and 4wC'N @p # 'Fenter the new list. The /CLEAR switch clears all selected responses and 4xP @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' @p 4{c'f @p '`Back to4thenbasic dialog.'Thepfourthoselectionuprompt: 4{{'h @p 4|k'l @p uewant thehselectionprocess4}c' @p " 'wtoebegin.HThe default response (EARLIEST)zisainclosed.inWparentheses 4~k( @p " ( and can(be selected%by pressing the RETURN key. You can also specify 4s( @p (real and relative time. 5 {(
c(* @p e fifth selection prompt: 5[(+ @p 5#(/ @p (, Time to (LATEST): 5;(1 @p 5{(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 parentheses 5(J @p ! (Band can be selected by pressing the RETURN key. Again, you can also 5(O @p (Kspecify real and relative time. 5 #(P @p 5 s(R @p 5
([ @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[)4 3.2.1.X. 5
(f G- 5
K(g 5
` (i
c(q @p # (jThemsixthRselection prompttallows(youpto specify(theptype ofCfile that5cates that you want the selected entries extracted 5[)
@p )5C) @p " )and translated indacreport. 5c)want the selected entries extracted 5[) @p ) and saved in a binary file. 5c) @p 5C)& @p $ ) We will discuss the ASCII response first. But, before we do, this prompt 5[)/ @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)9 G- 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 @p 53)P @p
)M *Outputomodeu(ASCII): 5K)R @p 5 )V @p )Snes thReportcformat(SHORT): ?5#)X @p 5k)` @p )Y . SHORT*- indicates5that you#wantahbriefmtranslationpofteach 5)e @p )aestion mark (?) reselected entry. 5 )f @p 5 S)n @p )g ieFULLe -eindicatesethatyou'wanta detailed translation.of5each5 k)s @p )o 5% selected entry. 5 k)u @p 5 ;)} @p )v OCTAL - indicates that you want an octal translation of each 5 S* @p # )~ selected entry. Normally, octal translations are used 5 S*
c*4 @p # *,If5you+specify BINARY,in response5to the "Output mode" prompt, Retrieve 5%;*= @p # *5will ask you if you want to merge the selected entries with an existing 5&K*@ @p *>binary file. 5'[*B @p 5( *G @p *C Output mode (ASCII): BINARY<cr>5(#*H @p 5(s*L @p *I Merge with (NONE): 5) *M @p 5)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 highly 5*c*g @p $ *intermittent failure. Let's say that on the average, the failure occurred 5+k*p @p ! *honce a week. Given that situation, you might need several weeks or 5,{*x @p " *qeven a months worth of error information to isolate the cause of the 5.*{ @p *yproblem. 5/ *| @p 5/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 track 50S+ @p " +of the failure. The merge feature is designed to help you do this. It 51c+ @p " +allows you to combine the currently selected entries with previously 52h @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[+B G- 58+D 58( +E
c+K @p +FThe eighth and last selection prompt: 58[+L @p 593+Q @p +M Output to (DSK:RETRIE.RPT): 59K+S @p 5:+[ @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 default 5;;+l @p ! +ebecomes DSK:RETRIE.SYS (if you are building or maintaining a binary 5<C+o @p +mhistory file). 5=K+q @p 5={+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@#, @p 5@{, @p ,
For example, if you were to type: 5A, @p 5Ac, @p , Report to (DSK:SUMMAR.SYS): CPU<cr> 5A{, @p 5BS, @p ,the output file specification would become DSK:CPU.SYS 5Bk, @p 5C[, @p 5Cs,) @p # ,!The prompt also supports standard Help and question mark (?) responses. 5D @p ,*Would you like to review the Help message ? z ,3 @p ,13 3.2.1.C1. 5E{,4 G- 5F3,6 5FH ,7
c,< @p ,8Finally, the confirmation prompt: 5F{,> @p 5GK,C @p ,? Type <cr> to confirm (/GO): 5Gc,D @p 5H3,M @p ! ,Eprovides an opportunity for you to review and change any responses 5HK,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 @p 5L,k @p ! ,cIf you want to change a response, press the BACKSPACE key until you 5L( @p # ,larrive at the corresponding prompt, make the change, and then type /GO. z ,w @p ,v3";& 3.2.1.D1. 5NC,y G- 5N{,z 5O ,|
c- @p # ,}ThattconcludesutheiexplanationhofRtheiRetrieveodialog.eNext'on thedmenu 5OC--the explanation, and you've had a chance to review the help messages, 5QX @p -you should have no difficulty answering the questions. 5hk.K G- z -" @p - 6nC7s , RETRIEVE INPUT 5Sk-$ G- 5T+-% 5T@ -'
c-, @p -(Retrieve Help Message: Input File Prompt5Ts-. @p 5UK-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 History 5Z3-d @p ! -\ Merge File (binary) ___________! Files (binary) 5[;-e @p 5\C-n @p $ -fRetrieve can be used to generate reports, or it can be used to establish 5\[-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 (Hexadecimal 5^{. @p $ .on VAX/VMS systems). If you choose to generate a device history file you 5` . @p # .
will be asked if you want to merge it with an existing (history) file.5a. @p 5b#. @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 file 5dK.6 @p # ..you will be prompted for packet numbers. Press the RETURN key to select 5e[.? @p $ .7the default (ERROR.SYS or ERRLOG.SYS). The file specification format is: 5fh @p .@dev:<user>file.extension.version. RETRIEVE TYPEET6
z - @p .H7CKETS 5SS.L 5i0 .N
c.T @p .ORetrievemHelpeMessage:sPacketnNumberyPrompt 5ic.U @p 5jC.^ @p ! .VAll theoriesiandhmanyisummariestlistedoinstheaAnalyzeareportshaveta 5j[.f @p # .pmatchingrpacket. Thespackethisnnumberedoandncontains aesetnofnpointers5kc.o @p " .gthatidentify thetrecordsmthatYwereasummarized$orpused as5evidenceto 5lk.w @p " .psupportptheetheory.rThetpacket file/that.wastgenerated in conjunction 5ms/ @p # .xwithmthe Analyze2report contains the!packetsTandInameuofptheffilelthat5n{/ @p /wasranalyzed. 5p/ @p 5p3/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
0U G- z /N @p .D6M+ 5z /S
c/Y @p /TRetrieveGHelp Message: Selection Mode Prompt 5z3/Z @p 5{/c @p # /[Selected events can be either included in, or excluded from, the output 5{+/l @p # /dfile. The following example illustrates the difference between the two. 5|;/n @p 5}K/v @p ! /o Include(event type C) Exclude(event type C) 5}c/x @p 5~k0 @p /yTime: From To From To 50 @p 0 : : : : 6 0 @p " 0 Input file: CABBACBCCAABCABBCAACCBCA CABBACBCCAABCABBCAACCBCA 60 @p " 0Output file: CC C C CABBACB AAB ABB AACCBCA 6 0 @p 60# @p # 0At this prompt Retrieve is waiting for you to indicate whether you want 6+0, @p ! 0$the events included in, or excluded from, the output file. You can: 6;0- @p 6C06 @p ! 0. 1. Type INCLUDED or press the RETURN key to include the selected 6[0; @p 07 events in the output file. 6c0< @p 630E @p # 0= 2. Type EXCLUDED to exclude the selected event from the output file.6K0F @p 6P @p " 0GNOTE: You will be prompted for event types and time parameters later. RETRIEVE CODESN6;` z /J @p 0SA
X 0X
c0^ @p 0YRetrieve Help Message: Selection Type Prompt 6 0` @p 6 k0h @p " 0aAt this prompt Retrieve is waiting for you to specify the first level 6
0m @p 0iof1entrysselection.RYouecan: 6petALLlif6you~want to selectall the 6 2. Type ERROR if you are interested in either a general class, or a 6c1 @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 @p 6{1! @p " 1 3. Type SEQUENCE if you want to select entries by sequence number. 61# @p 61, @p # 1$ 4. Type NONERROR if you want to select ALL non-error related entries. 631- @p 6C15 @p 1. 5. Type CODE if you want to select entries by event code. 6[16 @p 6S18 @p 6h @p 19NOTE: You will be prompted for time parameters later. z 1C @p 1A5hk5k ( RETRIEVE SEQUENCE 6s1E G- 6;1F 6P 1H
c1N @p 1IRetrieveeHelpcMessage:sSequence NumberpPrompt61O @p 6c1X @p " 1PSpear assignsoatsequenceynumber toeeach record in theeeventafile.iThe 6{1a @p # 1Ynumber refers@to$the2recordsspositionRinrtheefile.a(ie,gsequence number 61i @p # 1b1erefers"to'the first recordoinethenfile,tsequencednumber 2orefers the6 1r @p # 1jsecond)record, etc.)2.Retrieve2prints theesequencelnumbereinethemheader 6 1{ @p $ 1sof eachrreporttthatsitugenerates.rAsslongaasdthe ordersof6the=recordsin 6 +2 @p ! 1|theffileuareenotmchangedp(partiallyadeleted&or?merged with'anGother 6 ;2TE: The numbers you enter will remain until you type /CLEAR at this 6'p @p 2H prompt. 6;k3c G- z 2N @p 0N6
6t * 6)C2P G- 6)k2Q 6* 2S
c2Y @p 2TRetrievetHelp)Message:yEvent CodesrPrompt 6*32Z @p 6+2c @p # 2[Generallysspeaking,othe TOPS-10,nTOPS-20tandsVAX/VMSvoperating6systems6++2k @p " 2dhandleerrorseintansimilarmmanner.rThatwis,rwhen aneerrortoccursethey 6,32t @p " 2lsnapshothpertinent hardwaretandesoftwarelstatusm(ataerror).gThen,eif 6-;2| @p " 2uapplicable,ranrerrortretryralgorithmtistapplied. Next,lregardlesscof 6.C3 @p " 2}whethereorhnotPthe0retrySalgorithmVwasVsuccessful,carsecond snapshot 6/K3ed 65{3= @p 39on the back of the Spear Reference Card.673? @p 67[3H @p $ 3@At this prompt Retrieve is waiting for you to enter the event codes that 67s3O @p 3Icorrespond to the records that you want to select. You can: 693Q @p 69{3V @p 3R 1. Enter a single event code. 6: @p 3W 2. Enter a list of codes separated by commas. RETRIEVE STYLET8
( z 2J @p 3`6]34j * RETRIEVE TIME FROM 6)+3d 6<0 3f
c3k @p 3gRetrieve Help Message: Time From Prompt 6<c3m @p 6=;3s @p 3n Time From: Time To:6=S3z @p 3t ***********!oooooooooooooooooooo!*********** 6>34 @p 3{ 02-Mar-81 09-Mar-81 6?#4 @p 4 18:30:45 23:30:016@ 4 @p 6@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 the6C 4) @p 4"time at which you want the selection process to begin. You can: 6D4* @p 6E43 @p # 4+ 1. Press the RETURN key to default to the EARLIEST time in the file.6E+44 @p 6F34= @p # 45 2. Enter real time. The format is: dd-mmm-yy hh:mm:ss where dd is the 6FK4F @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 only 6Hc4X @p $ 4P the date is specified, the default time is 1 second after midnight. 6Is4Y @p 6K4b @p $ 4Z 3. Enter relative time. The format is: -dd where -dd is the number of 6K @p 4c past days. To indicate today at 00:00:01 hours, type: -0 z 4o @p 4l6;k/L & RETRIEVE TIME TO 6M+4p G- 6Ms4r 6N 4s
c4y @p 4tRetrieve Help Message: Time To Prompt 6N;4z @p 6O5 @p 4{ Time From: Time To: 6O+5 @p 5 ***********!oooooooooooooooooooo!*********** 6P5 @p 5 02-Mar-81 09-Mar-81 6Q 5 @p 5 18:30:45 23:30:01 6Qs5 @p 6R[5 @p # 5At this prompt Retrieve is waiting for you to specify the time at which 6Rs5( @p 5!you want the extraction (or exclusion) process to end. You can: 6T5) @p 6U52 @p " 5* 1. Press the RETURN key to default to the LATEST time in the file. 6U53 @p 6V#5< @p # 54 2. Enter real time. The format is: dd-mmm-yy hh:mm:ss where dd is the 6V;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 only 6XS5W @p $ 5O the date is specified, the default time is 1 second after midnight. 6Yc5X @p 6Zs5a @p $ 5Y 3. Enter relative time. The format is: -dd where -dd is the number of 6[ @p 5b past days. To indicate today at 00:00:01 hours, type: -0 7bk> G- z 5m @p 3\6s3^ & 6]35o G- 6][5p 6]p 5r
c5x @p 5sRetrieve Help Message: Output Mode Prompt 6^#5y @p 6_6 @p # 5zRemember, Retrieve is used to translate and/or save selected entries in 6_6 @p $ 6the system event file. The result will be either an ASCII report file or 6`+6 @p " 6
a special purpose binary file. At this prompt Retrieve is waiting for 6a;6 @p $ 6you to specify the type of output file that you want generated. You can: 6bC6 @p 6cS6' @p " 6 1. Type ASCII or press the RETURN key. The result will be a report 6ck6/ @p " 6( file. The next prompt will ask you to specify the report format. 6ds61 @p 6e{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, the 6g6J @p " 6C the next prompt will ask you if you want to merge these entries 6h#6S @p " 6K with an existing binary file. The merge feature is useful if you 6i+6Y @p 6T are maintaining a device history file. 6j36Z @p 6k6c @p " 6[NOTE: If you are using the Exclude capability, you will translate or 6k+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. z 6x @p 6v6)C- ( RETRIEVE FORMAT6nC6y G- 6o6{ 6o 6|
c7 @p 6}Retrieve Help Message: Report format Prompt 6oK7 @p 6p+7
@p ! 7Retrievefis aboutotoetranslatertherentriestthattyouuspecified.KThis 6pC7 @p " 7 6rk7! @p # 7 1. Type SHORT. The result will be a set of brief (3 or 4 line) reports 6s7* @p # 7" that list the major symptoms or conditions contained in each entry. 6t7+ @p 6u#74 @p " 7, 2. Type FULL. The result will be a set of detailed reports that list 6u;7; @p 75 all of the information contained in each entry. 6vC7< @p 6w37E @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 @p 7N debugging and event file verification purposes. 6y[7V @p 6zK7 @p $ 7WNOTE: Typically, the default format, Short, is used to translate packets 6zc7h @p $ 7`and lengthly system event files. Then, the sequence number listed in the 6{s7p @p " 7iheader of each report, is used to select specific entries for a Full 6} @p 7qtranslation. z 7w @p 7u5Sk8m $ RETRIEVE MERGE 6~;7y G- 6~{7z 6 7|
c8 @p 7}Retrieve Help Message: Merge Prompt6C8 @p 7 8 @p " 8You can merge the entries that you have selected with the entries in 7 +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 prompt 7;8% @p # 8 Retrieve is waiting for you to enter the name of the file that contains 7C8, @p 8&the entries that want these entries merged with. You can: 7S8. @p 7K87 @p $ 8/ 1. Press the RETURN key or type NUL: if you do not want to merge these 7c8= @p 88 entries with an existing (binary) file. 7s8> @p 7S8G @p " 8? 2. Enter the name of the merge file that contains the entries. The 7k8O @p " 8H standard file specification is: dev<user>file.extension.version. 7s8Q @p 7 {8R @p 7
8[ @p " 8SNOTE: The contents of the merge file will not be affected. If you are 7
+8d @p # 8\updating a history file andyou do not want to keep a backup copy, then 7 0 @p $ 8eyou should specify the name of the merge file at the "Output to" prompt. z 8q @p 8o6~;.F ( RETRIEVE OUTPUT7
c8{ @p 8vRetrieve Help Message: Output File Prompt 7[8} @p 7;9 @p # 8~At this prompt Retrieve is waiting for you to specify a destination for 7S9
@p
9the output file. You can:7c9 @p 7#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) the 7C9% @p $ 9 default file name will be DSK:RETRIE.TXT. If you requested a Binary 7K9- @p 9& (history file) the default file name will be DSK:RETRIE.SYS.7[9/ @p 7[98 @p $ 90 2. Enter your own unique file name. (e.g., DSK:SHORT.TAP. The standard 7s9@ @p " 99 file specification format is: dev:<user>file.extension.version. 79B @p 7 9K @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 @p 7;9V @p 7S9_ @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 @p 9hfile as you wish. z 9o @p 9mz3?G , ERROR CATEGORY 7 39p G- 7 s9r 7 9s
c9x @p 9tRetrieve Help Message: Error Prompt7 ;9z @p 7 : @p # 9{Retrieve is waiting for you to specify the type of errors that you want 7 #: @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*+:\ @p 7+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 ERROR 7,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 device 70p @p ;types. Example: DISK:DP220,DP030+TAPE:MT170,MT166 etc z ; @p ;8
3>L ( ERROR_MAINFRAME72k; G- 73+; 73@ ;
c;$ @p ; Retrieve Help Message: Mainframe Prompt 73s;& @p 74K;/ @p # ;'Retrieve defines the mainframe as: the console front-end processor, all 74c;8 @p # ;0central processing units, and the main memory subsystem. At this prompt 75s;: @p ;9you can: 77;< @p 77+;D @p ;= 1. Press the RETURN key to select ALL mainframe related errors. 77C;E @p 78C;N @p ! ;F 2. Type FE to select errors that pertain to the console processor. 78[;O @p 79c;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;;_ @p 7;[;h @p $ ;` 4. Type MEM to select processor detected errors that seem to be related 7;s;k @p ;i to main memory. 7=;m @p 7=;;u @p " ;nNOTE: Error classification at this level is very difficult because of 7=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_DISKS 7AS< G- 7B< 7B( <
c< @p <Retrieve Help Message: Disk Prompt 7B[< @p 7C+<$ @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<= @p 7GC<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 @p 7LS<h @p 7Lk<q @p $ <iNOTE: Type /CLEAR to clear all disk selections and start over again. You 7M<z @p # <rcan enter multiple selections on a single line, and you can mix logical 7N= @p <{and physical names. Separate each selection with a comma. 7O#= @p 7P= @p =Example: DP040,DP220,DP150 7P0 @p =Example: DP030,RP07,DP020,RP20 z = @p =8[> * ERROR_TAPES 7QK= G- 7R = 7R =
c= @p =Retrieve Help Message: Tape Prompt 7RS= @p 7S#=$ @p ! = You can select magtape entries by logical or physical name. Logical 7S;=, @p " =%names are system dependent. Most systems, however, define the magtape 7TC=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[=> @p 7WS=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 @p 7][=p @p 7]s=y @p $ =qNOTE: Type /CLEAR to clear all tape selections and start over again. You 7^ > @p # =zcan enter multiple selections on a single line, and you can mix logical 7_>
@p >and physical names. Separate each selection with a comma. 7`+> @p 7a#> @p
>
Example: MTA3,MTA7,MTC57a8 @p >Example: MT140,TU45,TU78,MT403 ERROR_NETTYou can: z 5i @p >7QHl0 ERROR_UNIT_RECORD 6]> 7c0 >
c>% @p > Retrieve Help Message: Unit Record Equipment Prompt 7cc>& @p 7dS>/ @p # >'Unit record equipment refers to line printers and card readers. At this 7dk>2 @p >0prompt you can:7e{>4 @p 7f+>; @p >5 1. Press the RETURN key to select ALL unit record errors.7fC>= @p 7g;>C @p >> 2. Type LPT to select ALL line printer errors. 7gS>E @p 7h8 @p >F 3. Type CDR to select ALL card reader errors. Analyze.q1z >O @p >72kA= , 7iK>P G- 7is>R 7j >S
c>Y @p >TRetrievemHelplMessage:7Network Prompt 7j;>Z @p 7k>c @p " >[At7this promptRetrieve is waiting forvyoustoaenter the?number of the 7k+>l @p $ >dDECNET Phase III Event Message Class that you want to select.The Classes 7l3>m @p D7mC>o @p 7m[>s @p >p Class Description 7ms>w @p
@p ? 4 Transport layer 7pc? @p
? 5 Data Link layer7q#? @p ? 6 Physical Link layer 7qc? @p ? 007-031 Reserved for Other common event classes 7r+? @p ? 032-063 Reserved for RSTS specific event classes7s?& @p ? 064-095 Reserved for RSX specific event classes 7s{?- @p ?' 096-127 Reserved for TOPS-20 specific event classes 7tc?3 @p ?. 128-159 Reserved for VMS specific event classes 7uS?: @p ?4 160-191 Reserved for RT specific event classes 7v;?? @p ?; 192-479 Reserved for Future use 7w @p ?@ 480-511 Reserved for Customer specific event classes 8
3@W G- z ?K @p ?I7 3< 7y;?N 7yP ?P
c?U @p ?QRetrieve Help Message: Crash Code Prompt7z?W @p 7z[?_ @p " ?XThe TOPS-10, TOPS-20 and VAX/VMS operating systems report software as 7zs?h @p # ?`well as hardware detected errors. If the system detects an error, or an 7{{?q @p " ?iunusual software condition, an appropriate message is printed and, in 7} ?z @p # ?rmost cases an entry is recorded in the system event file. Under TOPS-10 7~@ @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 the 8+@ @p ! @name of the BUG type or STOPCODE that you want to select. You can: 83@ @p 8;@$ @p @ 1. Press the RETURN key to select ALL entries of this type.8S@& @p 8K@- @p @' 2. Enter the name of a specific STOPCODE or BUG type. 8c@. @p 8S@5 @p @/ 3. Enter a list of names separated by commas. 8k@6 @p 8S@8 @p 8k@@ @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_IDSK8P z ?F @p @U7AS; ERROR_DISK_PACKS 7xc@Y 8
x @Z
c@` @p @[Retrieve Help Message: Pack ID Prompt 8 +@a @p 8
@j @p # @bYou can extract or exclude disk entries based on Pack or structure IDs. 8
@s @p $ @kTherextractiono(oraexclusion)ewill.beodoneainladditionutoaanysotheredisk 8;A @p " @}diskachannelhoriacspecificophysicalior)logicalidiskrdrive,.thenthose 8KA 8cA @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, @p 8+A2 @p A- 1. Enter a single structure or Pack ID. 8CA3 @p 8 @p # A4 2. Enter a list of structure names or Pack IDs separated by commas.retdiaq18*x z A@ @p @P7iK=
8[AA G- 8AC 8 AD
cAJ @p AERetrieve Help Message: Reel ID Prompt 8KAK @p 8#AT @p # ALYou can extract or exclude tape entries based on label or Reel IDs. The 8;A] @p # AUextraction (or exclusion) will be done in addition to any other magtape 8KAf @p $ A^entries that you have selected. For example, if you have selected a tape 8[Ao @p $ Agchannel or a specific physical or logical tape drive, then those entries 8 kAx @p $ Apas well as any entries that you select at this prompt will be considered 8 {B @p Aypart of the inclusion (or exclusion) selection criteria. 8 B @p 8 B
@p $ BAt this prompt Retrieve is waiting for you to enter the label or Reel ID 8 B @p " B that correspond to the tape entries that you wish to select. You can: 8!+B @p 8"3B @p B 1. Enter a single Reel ID. 8"KB @p 8# @p B 2. Enter a list of Reel IDs separated by commas. z B% @p B#2bsS R.T.3.2.1.D1. 8$B' G- 8$[B( 8$p B*
cB2 @p ! B+STOP - You are moving in a reverse direction thru the menu. You are 8% @p B3about to back into the Retrieve Dialog explanation. z B< @p A;ANj 8'B= G- 8'CB? 8'X B@
cBE @p trieve Dialog - Q1 of 10 8( BF @p 8(SBN @p BGTrue or False - Retrieve can be used to translate and/or save the8(h @p BOrecords listed in the packets that are generated by Analyze ? retdiaq28= z B\ @p BZ8.[CN retdiaq1at 8+B] G- 8+CB 8+X B`
cBc @p BaThat's Correct.8, Be @p 8,;Bn @p # BfThis feature allows you to translate and/or save the individual records 8,P @p Bothat were used as evidence to support specific theories. z By @p Bw9pcBX ret_dia_q1_af 8.[B{ G- 8/B| 8/0 B~
cC @p # BThe statement is TRUE. Retrieve can translate the Packets generated by8/cC @p >K80kC @p 81C @p " C
Remember, there is a packet associated with each theory listed in the 81C @p # CAnalyze report. The Packet contains pointers that identify the records82#C! @p Cthat were used as evidence to support the theory. 83+C" @p 84C+ @p # C#Thus, anytime you question the validity of a theory and want to examine 84+C4 @p " C,the evidence yourself, you can do so by specifying the Packet file as 85;C< @p " C5input to Retrieve. When Retrieve prompts for the packet number, enter 86CCE @p $ C=the number that corresponds to the theory that you are investigating and 87H @p CFthen, specify the desired output mode (Short, Full, or Octal). prompt.z CQ @p BV8+D 89kCR G- 8:CT 8:( CU
cCZ @p trieve Dialog - Q2 of 10 8:[C[ @p 8;#Cd @p " C\True or False - Retrieve can be used to generate and maintain device 8;8 @p Cehistory files ?retdiaq38Y z Cl @p Cj8DE' retdiaq2at 8= Cn G- 8=KCo 8=` Cq
cCt @p CrThat's correct.8>Cu @p 8>CC} @p CvYou can use Retrieve to build and maintain history files for: 8>[C @p 8?[D @p D a) entire subsystems (disks, tapes, networks, etc.), 8?sD @p 8@cD @p D b) logical devices (DP220, MT300, CPU0, etc.), 8@{D @p 8AcD @p D c) physical option types (RP06s, TU45s etc.) or,8A{D @p 8BcD @p D d) disk and tape storage media (Pack or Reel IDs). 8Bx @p z D$ @p D"89kCh " ret_dia_q2_af 8DD% G- 8DCD' 8DX D(
cD1 @p $ D)TheistatementeishTRUE.yRetrievehcansbecusedatonbuildfand maintain,device 8E D: @p " D2historyefiles.iTheaprocedure issrelatively simple.eHere'shwhat8toEdo: 8FD; @p 8G#DD @p $ D<First,aselectathegdeviceoviacthes"Erroruclass" prompt.pNext,Especifymthe 8G;DM @p $ DEtime frame.pThen,twheneRetrievewpromptsofor.OutputEmode,specify BINARY. 8HKDO @p 8I[DX @p # DPRetrieve will ask you if you want to merge the selected entries with an 8IsD` @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 exists 8L Dr @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| @p 8O3E @p " D}Finally, Retrieve will prompt for the output file name. Again, if you 8OKE
8T{E+ G- 8U#E- 8U8 E.
cE3 @p trieve Dialog - Q3 of 10 8UkE4 @p 8V3E= @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 list 8WP @p EFof responses ? retdiaq48r z EN @p EL8fsFt , retdiaq3at 8Y#EO G- 8YcEQ 8Yx ER
cE[ @p " ESThe:statementIisTFALSE.`The switchis called "/SHOW".NIf after making 8Z+Ec @p " E\yourIselections, you type "/SHOW",Retrieve will display:eachEprompt 8[3El @p # Edand the8corresponding response as illustrated in the following example. 8\;En @p 8]KEs @p Eo Type [cr] to confirm (/GO): /SHOW8]cEt @p 8^3Ew @p Eu RETRIEVE mode8^KEz @p Ex -------------8^{F @p E{ Event or packet file: SYSTEM:ERROR.SYS8+F @p
F Outputcmode: ASCII8c FE @p F @ReportFformat: SHORT 8cCF$ @p F!8eSelection type:TERROR 8dF( @p 0, 8eSF2 @p 8f @p F3 Type [cr] to confirm (/GO): z F; @p F98T{EJ retdiaq3af 8fsF< G- 8g3F> 8gH F?
cFB @p F@That's correct.8g{FD @p 8h+FL @p " FEIt's the "/SHOW" switch that will cause the current list or responses 8hCFP @p FMto be displayed. 8iKFQ @p 8jFZ @p ! FRIf, after reviewing the list, you decide that you want to change a 8jFb @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 can 8l( @p " Fladd to the response, or you can type /CLEAR and enter a new response. z Fv @p EH8Y#GE 8nCFx G- 8nkFy 8o F{
cF @p trieve Dialog - Q4 of 10 8o3G @p 8o{G @p ! GTrue or False - Retrieve can be used to select entries that pertain 8p @p G
to specific Disk Packs or Magtape Reel ID's ?ret_dia_q59 @ z G @p G8xSGa ret_dia_q4_at 8rG G- 8rSG 8rh G
cG @p GThat's correct.8sG @p 8sKG' @p $ G Pack and Reel ID's were added to the selection criteria so that you could 8scG0 @p # G(use the EXCLUDE mode to remove entries from the event file that pertain 8tsG8 @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 subtle 8w @p GBhardware problems. z GI @p GG8nCG ret_dia_q4_af 8xSGJ G- 8yGL 8y( 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 criteria 8z` @p G_available. z Gc @p G8rHu
8|Ge G- 8|;Gf 8|P Gh
cGl @p trieve Dialog - Q5 of 10 8}Gn @p 8}KGv @p GoTrue or False - If you specify a file name in response to the 8}cG~ @p Gw"Merge with (NONE):" prompt, Retrieve will automatically append 8~` @p Gthe selected entries to that file ?retdiaq69 z H @p H9[I $ retdiaq5at 9 KH
G- 9 H 9 H
cH @p ! HThe statement is FALSE. Retrieve will NOT automatically append the 9SH @p Hselected entries to the file that you specify in response to the 9[H! @p
H "Merge with" prompt.9[H" @p 9H+ @p " H#Instead what happens is: the selected[entriesandLthe entries in the 9+H3 @p # H,"merge file" aretcombinedeandmwrittencout@to the file that you specify93H9 @p H4in response to the "Output to" prompt. 9;H: @p 9HA @p H; Selected Entries Merge with "file name"9+HE @p
;H] @p " HVIf at the "Output to" prompt, however, you specify the same file name 9
SHf @p # H^that you specified at the "Merge with" prompt, then the entries will be 9 [Ho @p # Hgcombined and written in that file. Incidentlly, that is the recommended 9
h @p Hpmethod for maintaining device history files. z Hy @p Hw8|H ret_dia_q5_af 9[H{ G- 9H| 90 H~
cI @p HThat's correct.9cI @p 9I @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. z I @p H9 KI 9CI G- 9kI 9 I
cI @p trieve Dialog - Q6 of 10 93I! @p 9{I) @p ! I"True or False - Sequence numbers are used to identify the relative 9 @p I*position of the records in a system event file ? retdiaq79+` z I5 @p I39 {J? retdiaq6at 9I7 G- 9[I8 9p I:
cI= @p I;That is correct. 9#I? @p 9[IG @p " I@Record sequence numbers are included as part the header in all Short 9sIP @p # IHFull, and Octal reports translated by Retrieve. The sequence number is9{IV @p IQthe simplest way to refer to a specific record. 9IX @p 9kI` @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 ASCII9 Iq @p ! Ijtranslation of several records and then decide that you want a Full 9 Iz @p # Irtranslation of one or two of those records, you can do so by specifying 9 @p I{the sequence numbers to Retrieve. z J @p J9CI1 ret_dia_q6_af 9 {J G- 9 ;J 9 P J
cJ @p " J The statement is TRUE. Sequence numbers reflect each records relative 9!J @p Jposition in a file. 9" J @p 9"CJ @p # JRemember, sequence numbers are dynamically assigned to each record as a 9"[J' @p ! J file is read. For example, if a file contains 623 records then, the 9#kJ0 @p # J(first record in the file will be assigned sequence number 1, the second 9$sJ9 @p $ J1record will be assigned sequence number 2, etc. Finally, the last record 9& @p J:in the file will be assigned sequence number 623. z JB @p I/9K 9'{JC G- 9(#JE 9(8 JF
cJK @p trieve Dialog - Q7 of 10 9(kJL @p 9)3JU @p ! JMTrue or False - Retrieve can be used to select entries based on the 9)H @p JVevent codes assigned to the entries by the operating system ? retdiaq89>8 z Jb @p J`92;KU retdiaq7at 9+kJd G- 9,+Je 9,@ Jg
cJj @p JhThat's correct.9,sJk @p 9-#Jt @p $ JlIf, for example, you wanted to select all KS10 Halt Status Block entries 9-;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 "Selection 9/SK @p " Ktype" prompt, and, when Retrieve prompted for "Event code:" enter 033 90` @p Kfor TOPS-10 or 133 for TOPS-20. z K @p K9'{J^ ret_dia_q7_af 92;K G- 92{K 93 K
cK @p K The statement is TRUE. 93CK! @p 94K* @p $ K"If you type "?" in response to the "Selection type" prompt, you will see 94K3 @p # K+"CODE" listed as one of the acceptable responses. If you select "Code"95+K9 @p K4Retrieve will prompt you for the "Event codes". 963K; @p 97KD @p $ K<The event types and the corresponding event codes are listed on the back 973KM @p $ KEpanel of the Spear Reference Card. In addition, the detailed information 98@ @p ! KNcontained in of each entry types is described in the Spear Manual. z KX @p J\9+kLU 9:[KY G- 9;K[ 9; K\
cKa @p trieve Dialog - Q8 of 10 9;KKb @p 9<Kk @p # KcTrue or False - Typing /C in response to the "Error class (FINISHED):"9<( @p Klprompt will clear all entries selected up to that point ? retdiaq99] z Kx @p Kv9JSML retdiaq8at 9>CKy G- 9?K{ 9? K|
cK @p K}That's correct.9?KL @p 9?{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 @p 9B#L @p # LIn other words, suppose you type /SHOW before starting Retrieve. Then,9B;L$ @p ! L let's say that you decide that you don't want the selected magtape 9CCL- @p # L%entries after all, so you press the BACKSPACE key until you get back to 9DKL6 @p " L.the "Error class" prompt. At that point you specify "Tape", Retrieve 9E[L< @p L7prompts for tape drives and you type /CLEAR. 9FcL= @p 9GCLF @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 selected 9H` @p LPlist and thus, reinstated the default (ALL). z LY @p LW9:[Kt ( ret_dia_q8_af 9JSLZ G- 9KL\ 9K( L]
cLe @p L^The statement is TRUE. The /CLEAR switch provides a mechanism for9K[Lj @p Lfchanging selected entry types.9L[Lk @p 9M#Ls @p LlFor example, suppose you had just selected some event codes for 9M;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 @p 9PKM @p # MNow, suppose you discover that, for some reason, you entered the wrong9PcM @p Mlist of event codes. Here's what to do: 9QkM @p 9RCM @p " M1. Press the BACKSPACE key until you get back to the "Selection type" 9R[M @p CM9ScM! @p 9S{M) @p ! M"2. Then, in response to the "Selection type" prompt specify "CODE". 9TM+ @p 9UM4 @p $ M,3. When Retrieve prompts for the Event codes, type "/CLEAR" to clear the 9U3M< @p M5 existing list of event codes and then enter the correct list. 9VCM= @p 9WCMF @p # M>4. Finally, type "/SHOW" as a last check and then, if everything is OK9WX @p MG type "/GO" to start Retrieve. period._q1z MN @p Kr9>CN3 9YCMP G- 9YkMQ 9Z MS
cMW @p trieve Dialog - Q9 of 10 9Z3MY @p 9Z{Ma @p " MZTrue or False - Entries can be retrieved by logical names (i.e. CPU0) 9[ @p Mbas well as by physical names (i.e. RP06) ? 3.2.1.1.q1:S@ z Mm @p Mk9f8Kp retdiaq9at 9]Mn G- 9]SMp 9]h Mq
cMz @p " MrTechnically, the statement is FALSE. Retrieve can recognize some, but 9^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 @p N
recognize the following physical and logical names: 9a3N @p 9b#N @p N Mainframe devices: CPU, MEM, and FE. 9b;N @p 9cN# @p N Disks: RM03, RM05, RP04, RP05, RP06, RP07, RP20, and RS04. 9c3N$ @p 9d3N, @p N% Tapes: TU16, TU45, TU70, TU71, TU72, TU73, TU77, and TU78. 9dKN. @p 9eH @p N/ Unit record devices: LPT and CDR. z N7 @p N59YCMi ret_dia_q9_af 9f;N9 G- 9f{N: 9g N<
cN? @p N=That is correct. 9gCNA @p 9g{NJ @p # NBRetrieve recognizes some, but not all, physical and logical names. Just 9hNS @p # NKas a double check before running, Retrieve will list all selected names 9i#N[ @p " NTthat it considers to be logical. Thus, if you made a typing error or 9j3Nd @p # N\entered a physical name that it does NOT recognize, you'll know because 9k8 @p NeRetrieve will list it as a logical name. z Nn @p Nl8'OK ret_dia_q10 9m+Np G- 9mkNq 9n Ns
cNw @p trieve Dialog - Q10 of 10 9n3Ny @p 9n{O @p NzTrue or False - Retrieve can be used to extract entries based on 9o @p OSTOPCODES or BUGxxx code names ? z O
@p O9y3Bu retOdiaq10at 9pcO G- 9q#O
cO @p OThat's correct.9qkO @p 9rO @p " OThe "Mainframe Error and Crash Summary" section of the Analyze report 9r3O$ @p $ O breaks down STOPCODES (for TOPS-10) and BUGxxx (for TOPS-20 and VAX/VMS) 9s;O* @p O%by: type, name, and number of occurances. 9tKO, @p 9u+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 investigating 9wP @p OGvery intermittent system crashes. z OO @p OM9m+O " ret_dia_q10_af 9y3OP G- 9ysOR 9z OS
cO\ @p " OTThe statement is TRUE. Retrieve can be used to extract entries based 9z;Oa @p O]on STOPCODES and BUGxxx code names.9{COb @p 9|Ok @p ! OcIf you type "?" at the Retrieve "Error class" prompt, you will see 9|+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 the 9~;P @p O}names of one or more STOPCODES or BUGxxx that you want retrieved.9KP @p : KP
@p For example, if you typed: : cP
@p :+P @p PERROR<cr> :CP @p P Error class (All): CRASH<cr> :P @p P Crash codes: DX2FUS,P2RAE<cr>:cP @p :3P @p :KP& @p P Retrieve will translate (or save) all entries that are related to:` @p P'either of the Crash codes (DX2FUS and P2RAE).z P. @p Mg2j $ :CP0 G- :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 :@ @p PNpronounces you a "Retrieve-Dialog Subject Matter Expert". z PX @p PV2eKQ9 3.3.0. :
KPY G- : P[ : P\
cPd @p P]Compute calculates the following system performance factors:: KPe @p :
CPn @p $ PfSystem Availability (AS) - System Availability is the percentage of time :
[Pw @p # Pothatthe systemUwas availablelfor use.)(ItUincludeslStandalone time.)r:entage of time: Q @p Qthat the system was available for use by the user community. :Q
@p :Q @p # Q System Effectiveness (SE) - System Effectiveness (SE) is the percentage :+Q @p # Qof probability that the system remained available for a given period of :;Q @p Q time (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:( @p Q4of the formulas refer to the Spear Manual. z Q< @p Q;:
KQv 3.3.0.A. :Q> G- :KQ? :` QA
cQI @p " QBThe following formula is used to calculate System Availability (SA): :QK @p :QO @p QL SA = (1.0) - CDT/(TDT + TRT):3QQ @p :{QR @p :QU @p QSwhere: :+QV @p :SQ[ @p QW CDT = Chargeable Down Time :kQ_ @p Q\ TDT = Total Down Time :3Qc @p Q` TRT = Total Run Time :sQd @p : 3Qf @p : KQo @p $ QgRemember - System Availability is the percentage of time that the system : ` @p Qpwas available for use. (It includes Standalone time.) z Qy @p Qx:R- 3.3.0.B. : cQ{ G- : Q| : 0 Q~
cR @p ! QThe following formula is used to calculate User Availability (UA): : cR @p : kR
@p R = UAa=g(1.0) -oCDT/(CDT +:TRT):!R @p :!KR @p :!cR @p Rwhere: :!{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 @p R(was available for use by the user community. z R1 @p R/: cSM $ 3.3.0.C. :%[R2 G- :&R4 :&( R5
cR> @p " R6The following formula is used to calculate System Effectiveness (SE): :&[R? @p :'cRD @p R@ SE = (SA) * (e** (-t/MTBF)) :'{RE @p :(CRG @p :([RI @p RHwhere: :(sRK @p :)RO @p
RL SA = System Availability:)3RV @p RP 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 @p Ri 6 minutes, 30 minutes, 1 hour, and 4 hours. :- Rx @p $ RpMTBF= The mean, or average time between failures (chargeable Downtimes). :-sR~ @p Ry 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 ! S that the system remained available for a given period of time (t). z S @p S8$if R.T.3.3.0.:2+S G- :2cS :2x S
cS# @p # SSTOP - You are moving in a reverse direction through the menu. You are:3( @p S$about to back into the Introduction to Compute. z S- @p S+={h_ 3.3.M. :5S. G- :5SS0 :5h S1
cS8 @p S2 Spear Library - Compute :6S9 @p :7S< @p S:Topic menu: :7S> @p :7KS? @p :7cSB @p S@0. Overview :7{SD @p :8+SG @p SE1. Compute Dialog :8CSI @p :8x @p SJ2. Questions & Answers z SP @p SO:%[f/ ( 3.3.1. :9SSR G- :: SS :: SU
cS^ @p $ SVComputeEDialogT-:The Compute@dialog fairly straight forward. It consists ::SSe @p S of:seven@selection promptstandponeSconfirmation)prompt.:;cSf @p :<SSi @p SgCOMPUTE mode :<kSl @p Sj------------ :=Sq @p Sm Event file (SYSTEM:ERROR.SYS): :=KSs @p :>Sw @p St Report period (LAST-WEEK): :>3Sy @p :>{S} @p
Availability Reportftom(DSK:COMPUT.RPT):p :A3T @p :BT @p T Reload report to (DSK:RELOAD.RPT): :B+T @p :C @p
cT* @p e first selection prompt: :DcT, @p :E+T1 @p T- 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 @p Tryou want to override. For example, if you were to type::NTy @p :OU @p Tz Event file (SYSTEM:ERROR.SYS): .LWK<cr> :OU @p :PU @p Uthe input file specification would become SYSTEM:ERROR.LWK :PU
@p :QU
@p :Q+U @p # U standard Help and question mark (?) responses. :Q@ @p UWould you like to review the Help message ? 3.3.1.B.in:t0 z U @p U =K] , compute input :SKU" G- :T U# :T U%
cU* @p U&Compute Help Message: Input File Prompt :TSU, @p :U+U4 @p U- .--------------. .___ Summary Report :UCU: @p U5 | Calculate | | :VCUB @p ! U; System Event File ___| System |___|___ Availability Report :W#UH @p UC (or AVAIL.Ann) | Availability | | :X+UP @p UI |______________| |___ Reload Report:Y UQ @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 @p Umentries 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 @p Vwhich 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 :c V# @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). z V- @p U:CcX & :e3V/ G- :e[V0 :ep V2
cV6 @p e second selection prompt :f#V8 @p :fkV< @p V9 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 @p Vhavailability 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 @p Wtime period. :qkW @p :rW @p # WThe prompt also supports standard Help and question mark (?) responses. :r0 @p W Would you like to review the Help message ? 3.3.1.C.pe;
0 z W' @p W%;Qs^` compute period :t;W) G- :t{W* :u W,
cW2 @p W-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 @p W=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.z X @p W!:e3Z` ; X G- ; +X ; @ X
cX
@p XThe third and fourth selection prompts ; sX @p ;KX @p X 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@ @p X<either real or relative time. ;;XA @p ;XJ @p # XBBoth of these prompts also supports standard Help and question mark (?) ; @p XKresponses. Would you like to review the Help messages ?compute time to; 8 z XX @p XU;l Yd * compute time from ;
;XY G- ; X[ ; X\
cXb @p X]Compute Help Massage: Time From Prompt ; KXc @p ;
#Xj @p Xd Time From: Time To: ;
;Xr @p Xk ***********|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 ! Y time 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! @p Y want 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 ; @p Y[ past days. Enter -0 to refer to today at 00:00:01 hours. 3.3.1.D.ti;8x z Yf @p XQ;
;[H & ; CYh G- ; kYi ; Yk
cYp @p YlCompute Help Message: Time To Prompt ; 3Yr @p ; Yy @p Ys Time From: Time To: ; #Z @p Yz ***********|ooooooooooooooooooooo|*********** ; Z @p Z 02-Mar-81 09-Mar-81 ; Z @p Z 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 @p Zyou 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 @p ZY past days. Enter -0 to refer to today at 00:00:01 hours. z Zc @p Yb; \# ;, Zd G- ;,3Zf ;,H Zg
cZl @p e[fifthrselectionuprompt ;,{Zm @p ;-CZr @p ZnLEReportTtype (SINGLE-REPORT):;-[Zs @p ;.#Z| @p " Ztis alsondisplayedtonlytifeyoucspecifyeOTHER[in@responseptoftheaReport ;.;[ @p # Z}PeriodrPrompt. The[Report Type;promptpallows you 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;Qh z [L @p [J; @M compute type ;9[M G- ;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 systemtperformancefbrokenedown into"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\. @p e 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;l z ] @p ]:SKW# " compute output ;Qs] G- ;R3] ;RH ]
c] @p ]Compute Help;Message: Availability ReportPrompt ;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^ @p e 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 ^f G- ;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 `%ComputetDialogF Q1Gof 5 <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`also brieflyexplained inuthe Introduction section of this module.z `q @p `o<C`A comdiaq1af <
c`} @p `vThe statement is TRUE. The formulas used by Compute to calculate <[a @p ! `~system availability, user availability and system effectiveness are <[a @p adescribed in the Spear Manual. <ca
@p <3a @p <Ka @p " aYou should become familiar with those formulas before you attempt to <` @p ainterpret the reports generated by Compute. z a @p `?<a`
<Ka G- <sa" < a#
ca' @p a$Compute Dialog Q2 of 5 <;a) @p <{a1 @p a*True or False - The entries used by Compute to calculate system <a9 @p a2performance are recorded in the system event file: ERROR.SYS for < @p a:TOPS-10 and TOPS20, and ERRLOG.SYS for VAX/VMS ? com_dia_q3<)H z aE @p aC< b' com_dia_q2_at <aF G- <SaH <h aI
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< @p a[are recorded in a file called AVAIL.SYS. z ad @p ab<KaA com_dia_q2_af < ae G- < Cag < X ah
cak @p aiThat'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 @p bAVAIL.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 <# @p b#specify AVAIL.A22 as the input file. z b* @p a?<b
<${b+ G- <%#b- <%8 b.
cb2 @p b/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 @p bFcolumn Full Report that provides more detail ? com_dia_q4<C z bQ @p bO</{cz com_dia_q3_at <)SbR G- <*bT <*( bU
cbX @p bVThat'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 @p blSummary report with specific details. <-;br @p <.b{ @p # bsNote: The Full report requires 132 columns and is generally not suited<.( @p b|for display on most terminals.z c @p c<${bM , com_dia_q3_af </{c G- <0;c <0P c
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 @p cthat details system availability and effectiveness. <3c" @p <4 c+ @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 @p c@ period length (HRS): 168.000<7scE @p <8;cJ @p cF SYSTEM Availability % : 100.000 <8ScP @p cK USER Availability % : 100.000 <9+cQ @p <:cS @p <:c[ @p cTEffectiveness Six minutes Thirty minutes One Hour Four Hours <:3ca @p c\ factor 99.584 97.938 95.918 94.648 <;3cc @p <<ch @p cdReport 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. z c} @p bK<)Sd7
<?+c~ G- <?Sd <?h d
cd @p dCompute Dialog Q4 of 5 <@d @p <@[d @p " dTrue or False - Compute uses the operators response to the question: <@sd @p d"Why Reload" to determine User Availability ?<Ax @p dDowntime ?com_dia_q5<S z d @p d<F{d{ com_dia_q4_at <Cd G- <C[d <Cp d"
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( @p d4and Non-chargeable Downtime. z d; @p d9<?+d com_dia_q4_af <F{d= G- <G;d> <GP d@
cdC @p dAThat'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 @p dVoperator responses constitute:<J[d[ @p <K#dd @p $ d\Chargeable Downtime - STOPCD, BUGHLT, HALT, PARITY, HARDWARE, NXM, HUNG, <K;dj @p deLOOP, AND CM (Corrective Maintenance). <LKdk @p <M#dt @p # dlNon-chargeable Downtime - PM (Preventive Maintenance), OPERATOR, POWER, <M8 @p duSTATIC, NEW, SCHEDULED, STANDALONE, and OTHER. z d} @p d<Ce1 <O3d G- <O[e <Op e
ce @p eCompute Dialog Q5 of 5 <P#e @p <Pce @p # eTrue or False - In addition to the Summary Report and the Full Report,<Px @p eCompute also generates a Reload Report called COMPUT.RLD ? 3.3.1.1.q5<n@ z e @p e<Vf` com_dia_q5_at <Se G- <SSe <Sh e!
ce* @p # e"The statement is true, only in that Compute generates a Reload Report.<T @p e+The report is actually called RELOAD.RPT not COMPUT.RLD. z e5 @p e3<O3e * com_dia_q5_af <Ve7 G- <V[e8 <Vp e:
ce= @p e;That's correct.<W#e> @p <WSeG @p $ e?The name of the report is: RELOAD.RPT. The following example illustrates <WkeM @p eHthe type of information it contains. <X{eN @p <YSeP @p <YkeW @p eQSYSTEM 2116 THE BIG ORANGE, TOPS-20 MONITOR 4(3530) <Ze_ @p eX 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 @p eh Reloaded on: 14-Jun-81 07:25:08 Why reload: OTHER <\{ev @p ep Run time: 6.004 Down time: 0.414 <]sex @p <^ke @p eySYSTEM 2116 THE BIG ORANGE, TOPS-20 MONITOR 4(3530) <_f @p f 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 @p f Reloaded on: 15-Jun-81 08:38:20 Why reload: OTHER <bf @p f 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 @p f+system Crash and Uptime reports. z f2 @p e:9ST <e{f3 G- <f#f5 <f8 f6
cf? @p # f7That's the last question about the Compute dialog. Press the RETURN key <fh @p f@to return to the menu. z fG @p fE;{hG 3.3.2. <h;fH G- <hsfJ <i fK
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 @p f^Compute menu. z fd @p fb<Sg com_rpt_q1<l fe G- <lCfg <lX fh
cfl @p
fiCompute Report - Q1 of 5 <m fn @p <mKfq @p foTrue or False - <m` @p com_rpt_q2<t z fx @p fv<pg com_rpt_q1_at <nKfz G- <o f{ <o f}
cg @p f~That's correct.<oP @p z g @p g<l ft com_rpt_q1_af <pg G- <p[g <pp g
cg @p g The statement is TRUE. <q @p z g @p fr<nKg0 <q{g G- <r#g <r8 g
cg @p
gCompute Report - Q2 of 5 <rkg @p <s+g @p g True or False - <s@ @p com_rpt_q3<z z g& @p g$<v g= com_rpt_q2_at <t+g( G- <tkg) <u g+
cg/ @p g,The statement is FALSE. <u0 @p z g4 @p g2<q{g" com_rpt_q2_af <v g6 G- <vKg7 <v` g9
cg< @p g:That's correct.<w @p z g@ @p g <t+g^ <w[gA G- <xgC <x gD
cgH @p
gECompute Report - Q3 of 5 <xKgJ @p <y gM @p gKTrue or False - <y @p com_rpt_q4<` z gT @p gR<{kgk com_rpt_q3_at <z gV G- <zKgW <z` gY
cg] @p gZThe statement is FALSE. <{ @p z gb @p g`<w[gP com_rpt_q3_af <{kgd G- <|+ge <|@ gg
cgj @p ghThat's correct.<|p @p z gn @p gN<z h <};go G- <}cgq <}x gr
cgv @p
gsCompute Report - Q4 of 5 <~+gx @p <~kg{ @p gyTrue or False - < @p com_rpt_q5=@ z h @p h =;h com_rpt_q4_at <kh G- = +h = @ h
ch
@p hThat'stcorrect.= p @p z h @p h = h
ch @p hThe statement is TRUE. =@ @p z h @p g|<kh: =h G- =Ch =X h
ch$ @p
h!Compute Report - Q5 of 5 = h& @p =Kh) @p h'True or False - =` @p 3.3.2.1.q5=f z h0 @p h.=+U com_rpt_q5_at =Kh2 G- = h3 = h5
ch9 @p h6The statement is FALSE. =P @p z h> @p h<=h, com_rpt_q5_af =+h@ G- =khA = hC
chF @p hDThat's correct.=0 @p z hJ @p h*<h;S) ={hK G- = #hM = 8 hN
chW @p ! hOThat's it. There are only five questions about the Compute Report. = khX @p =
p @p hYPress the RETURN key to return to the Compute menu. z hc @p ha:5j- & 3.4.0. = {hd G- =
3hf =
H hg
chp @p " hhSummarize Overview - Summarize is designed to read and summarize the =
{hu @p hqcontents of system event files. =hv @p =Sh @p " hwThe purpose of this Instruct module is to ensure that you understand =ki @p " i the 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 @p iunderstandings.= i @p =;i& @p # i Part 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 @p iJcontent 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 @p iacontent of a typical Summarize report. z ii @p ih:2(QV R.T.3.4.0.= cik G- = il = 0 in
civ @p # ioSTOP - You are moving in a reverse direction through the menu. You are= ` @p iwabout to back into the Summarize Overview. z j @p i~>X4
3.4.M. = Kj G- = j = j
cj @p j Spear Library - Summarize = Kj
@p =!3j @p j =!{j @p ="j @p j0. Overview ="+j @p ="[j @p j1. Summarize Dialog ="sj @p =#+j! @p j 2. Summarize Dialog Questions & Answers =#Cj# @p =$j& @p j$3. Summarize Report =$3j( @p =$h @p j)4. Summarize Report Questions & Answers z j1 @p j/= {tY 3.4.1. =%[j2 G- =&j4 =&( j5
cj> @p $ j6SummarizeiDialogO-:TheSummarizedialogis straight1forward.jIt consists =&[jG @p " j?of five prompts: four selection prompts and one confirmation prompt. ='kjH @p =(sjK @p jISUMMARIZE mode =) jN @p jL-------------- =);jP @p =)kjU @p jQ Event file (SYSTEM:ERROR.SYS): =*jV @p =*SjZ @p jW Time from (EARLIEST): =*kj\ @p =++j @p j] Time to (LATEST): =+Cja @p =+{je @p jb Report to (DSK:SUMMAR.RPT): =,jg @p =,X @p
cjx @p e first selection prompt: =.;jy @p =/j~ @p jz 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 =1 k @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 @p k,only field that you want to override. =53k2 @p =6 k7 @p k3For example, if you were to type: =6#k8 @p =6sk? @p k9 Event file (SYSTEM:ERROR.SYS): .LWK<cr> =7 k@ @p =7skH @p kAthe input file specification would become SYSTEM:ERROR.LWK =8 kI @p =9kK @p =9kL @p =93kU @p # kMThe prompt also supports standard Help and question mark (?) responses. =9H @p kVWould you like to review the Help message ? z k @p k]=-;l 3.4.1.B. =;;k` G- =;skb =< kc
ckh @p kdThersecondRselection prompt: =<;ki @p ==kn @p lows 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 @p lWould you like to review the Help message ? z l# @p l!=;;lc 3.4.1.C. =C{l$ G- =D3l& =DH l'
cl, @p e third selection prompt: =D{l- @p =ECl1 @p l. 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 @p lMspecify real and relative time. =IKlS @p =JlT @p =J3l] @p # lUThe prompt also supports standard Help and question mark (?) responses. =JH @p l^Would you like to review the Help message ? z lg @p le=C{mN & 3.4.1.D. =L;lh G- =Lslj =M lk
clq @p llThe fourth and last selection prompt: =M;lr @p =Nlw @p ls 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 $ m default response by specifying the only field that you want to override. =SKm' @p =T[m, @p m(For example, if you were to type: =Tsm- @p =UCm3 @p m. Report to (DSK:SUMMAR.RPT): FS:<cr> =U[m4 @p =V3m< @p m5the 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 @p mIWould you like to review the Help message ? z mQ @p mP=L;tw 3.4.1.E. =YcmS G- =ZmT =Z0 mV
cmZ @p
mWThe confirmation prompt: =Zcm[ @p =[#m` @p m\ 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~ @p m{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. z n @p n
cnd sum_dia_q1=bn G- =bSn =bh n
cn @p mmarize Dialog - Q1 of 7 =cn @p =ccn' @p n True or False - If you do NOT want to change any of the Summarize=cx @p n(default responses, you can type /GO at the Event file prompt ? sumdiaq2=v` z n5 @p n3=lKo sumdiaq1at =fn6 G- =fSn8 =fh n9
cn= @p n: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 @p naresponse list is used. z nh @p nf=bn1
sum_dia_q1_af =lKnj G- =m nk =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 $ o Event 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 @p zz o @p n/=fob
=r#o G- =rKo =r` o
co @p mmarize 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 @p o1to that prompt will be displayed ? sumdiaq3> z o: @p o8=|+p
sum_dia_q2_at =vko< G- =w+o= =w@ o?
coB @p o@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 @p o_responses without explanation.z of @p od=r#o6 sum_dia_q2_af =|+oh G- =|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 =@ @p pto that prompt.z p
@p o4=vkpo >p
G- >+p p
cp @p mmarizeaDialog ->Q3pof 7 >sp @p >;p @p # pTrue or False - Summarize will accept and summarize the contents of any >P @p $ p binary event file, including a binary event file generated by Retrieve ? sumdiaq4>X z p, @p p*>
cp4 @p p2That 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 @p pIby: 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>
@p pito3process eventfiles generated by TOPS-20 etc. z ps @p pq>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 > @p qevent files generated by Retrieve. z q @p p&> qr >kq G- >q >( q
cq" @p mmarize 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>$h z q: @p q8> #r
sum_dia_q4_at >cq; G- >#q= >8 q>
cqG @p " q?The statement is FALSE. You don't have to press ESCAPE/RETURN to take >kqN @p qHthe 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. z qv @p qt>kq6 sum_dia_q4_af > #qw G- > cqy > x qz
cq~ @p q{That is correct. > +q @p > cr @p # r Since the default response is inclosed in parentheses, there is no need > x @p r to use the ESCAPE key. z r @p q4>crP >!Kr G- >!sr >" r
cr @p mmarize Dialog - Q5 of 7 >";r @p >#r! @p rTrue or False - Summarize will accept and summarize Packet Files ># @p r"generated by Analyze ? sumdiaq6>2 z r+ @p r)>* ro sumdiaq5at >$sr, G- >%3r. >%H r/
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 >( @p rJtheories listed in the corresponding Analyze Report file. z rT @p rR>!Kr' sum_dia_q5_af >* rV G- >*KrW >*` rY
cr\ @p rZThat 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. z rr @p r%>$ss<
>-{rs G- >.#ru >.8 rv
cr{ @p mmarizeSDialogR-TQ6oofS7 >.kr| @p >/3s @p # r}Truetor Falset->If youpwanttopchange?theunameaof7the report filefrom>/Ks\ sumdiaq6at >2s G- >2[s >2p s
cs @p sThat 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 @p s1it SUMMAR.LWK, you could type:>6s6 @p >6H @p s7 Report to(DSK:SUMMAR.RPT): FS:.LWK<cr> z s@ @p s>>-{s sum_dia_q6_af >7CsA G- >8sC >8 sD
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 @p sWfile extension, or any combination thereof. z s^ @p s>2t >;Cs` G- >;ksa >< sc
csg @p mmarize 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>bh z s{ @p sy>B
sum_dia_q7_at >>ss| G- >?3s~ >?H s
ct @p >?{t @p tThat is correct. >@t @p >@Kt @p ! tAll Spear Library "Time" prompts accept both real and relative time >@` @p tspecifications.z t @p t>;Csw sum_dia_q7_af >Bt G- >B[t >Bp t
ct# @p $ tThe statement is TRUE. All Spear Library "Time" prompts accept both real >C#t+ @p t$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 @p tHThe format for relative time is: >H{tN @p >IKtV @p # tO -dd where dd represents some number of past days. The time defaults>I` @p tW to 00:00:01.z t\ @p su=%[jk >Kt] G- >KCt_ >KX t`
cti @p $ taThat's it. If you have gotten this far, then chances are you have a good >L tr @p # tjhandle on the Summarize dialog. Next on the menu is a brief explanation >M @p tsof the Summarize Report format. z t{ @p ty=Yc~C 3.4.2. >N{t| G- >O3t~ >OH t
cu @p $ u Summarize Report - The Summarize Report consists of four major sections: >O{u
@p >Q u @p u Rep1.tA File EnvironmentEandiEntry Occurrence Count section.>Q#u @p >Ru @p u 2. A Monitor Detected Error and Reload section.>R3u @p >Su" @p u 3. A Front-end, Channel and Device Summary section. >S3u# @p >T#u) @p u$ 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. >X3uH G- >XkuI >Y uK
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 @p u^use the one in the Spear Manual. >[Suc @p >\ @p udWhen you are ready to proceed press the RETURN key. z un @p ul@6Cv1
sum_rpt_q1>]+uo G- >]cuq >]x ur
cuw @p mmarize 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 $ v the number of BUGHLT, BUGCHK, and BUGINF that occurred during the summary >a @p vperiod ? sum_rpt_q2>p8 z v @p v>fv^ sum_rpt_q1_at >bsv G- >c3v >cH v
cv# @p v That is correct. >c{v$ @p >d3v- @p ! v%The BUGHLTs, BUGCHKs, and BUGINFs described in the TOPS-20 Software >dH @p v.Notebooks (Volume 16). z v5 @p v3>]+v
sum_rpt_q1_af >fv6 G- >fSv8 >fh v9
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 @p MJexceed 99.z va @p v>bsw'
>kkvb G- >lvd >l( ve
cvj @p mmarize 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@ @p v~event file that was submitted as input ?sumrptq3>}` z w @p w>t{wF sumrptq2at >pCw G- >qw >q w
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 # w period of time could, it does not always reflect the entire event file. z w+ @p w)>kkw sumrptq2af >t{w- G- >u;w. >uP w0
cw3 @p w1That is correct. >vw5 @p >v;w> @p $ w6Only the events that occurred on or between the time the user specified, >vP @p w?at the "Time from" and the "Time to" prompts, are summarized. z wH @p w>pCx$
>xcwJ G- >y wK >y wM
cwQ @p mmarize Reportx- Q3ofu8 >ySwS @p >zw[ @p " wTTrue or False - 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 @p x.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 @p xDin the next data block to recover. z xK @p wl>}ky
? xL G- ? 3xN ? H xO
cxT @p mmarize 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 ? ` @p xgappeared in the summarized period of the system event file ?sum_rpt_q5? h z xs @p xq?[yW
sum rpt q4 at ?v ?P xx
cx{ @p xyThat 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 @p yeach entry type in the system event file. z y! @p y ? xo sum_rpt_q4_af ?[y# G- ?y$ ?0 y&
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 @p mmarize 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?/X z y{ @p yy?$kzc
sum_rpt_q5_at ? sy| G- ? 3y~ ? H y
cz @p s z TheystatementristFALSE.$If there are anyzerrorbits(setyin Error ? {z @p f zRegister 2 theyzwill be listed also. 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 @p z0That 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.z zf @p yu? s{ ?,;zg G- ?,czi ?,x zj
czo @p mmarize Report - Q6 of 8 ?-+zp @p ?-szy @p # zqTrue or False - For the most part the Summarize Report is easy to read?. @p zzand understand ? sumrptq7?<` z { @p { ?3{{H sumrptq6at ?/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 @p z|?/c| ?9 {L G- ?93{N ?9H {O
c{T @p mmarize 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?S8 z {j @p {h?C|N sumrptq7at ?<k{l G- ?=+{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 @p v]z | @p |?9 {f sum_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 @p Breakdown.z |P @p {d?<k~ ?Ic|R G- ?J |S ?J |U
c|Y @p mmarize 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 @E H F 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.^You cannotdetermineShow1many^Hard@andSoft ?TK}6 @p # }.error1a device.experienced by looking at the BreakdownpsectionTbecause; ?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~G G- ?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 @p Press the RETURN key to return to the Spear Library Menu. @T G- z @p 5yD ( SUMMARIZE INPUT?q[ G- ?r ?r0
c @p SummarizeeHelpoMessage:|InputpFile Prompt ?rc @p ?sC# @p e 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 @p 2le specificRetrieve ! ! Summary ! ?v= @p 8 (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, ?z a @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 " @p Summarize Help Message: Time From Prompt@L # @p @$ * @p $ Time From: Time To: @< 2 @p + ***********!oooooooooooooooooooo!*********** @, 9 @p 3 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 @p 2 Time From: Time To: @ @ @p 9 ***********!ooooooooooooooooooooo!***********@
G @p A 02-Mar-81 09-Mar-81 @N @p H 18:30:45 23:30:01 @tO @p @dX @p $ PAt this prompt Summarize is waiting for you to specify the time at which @|^ @p Yyou 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 $ | @!the year, 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, @p mmarize Dialog - Qx of x @4|- @p @5D1 @p .True or False - @5X @p @:tY G- z
8 @p 6@8[uj sum_dia_qx_at @6D9 G- @7; @7 <
d@ @p =That is correct. @7LD @p AThe statement is FALSE @8 @p z
I @p G@4
4 sum_dia_qx_af @8\K G- @9 L @90 N
dQ @p OThat is correct. @9dU @p
RThe statement is TRUE @: @p z
2 @p ?SDz @6,[ @; \
da @p mmarize Report - Qx of x @;Lb @p @<f @p cTrue or False - @<( @p 3.5.1.tqxA
m @p k@?, . sum_rpt_qx_at @=n G- @=Tp @=h q
du @p rThat is correct. @> y @p vThe statement is FALSE @>P @p z
~ @p |@:ti sum_rpt_qx_af @?, G- @?l @@
d @p That is correct. @@4
@p
The statement is TRUE @@h @p z
@p g= L2
@AD G- @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 @p 4@AD 3.5.1.A. @F$7 G- @F\8 @Fp :
dC @p # ;The firstuthingAyou wantDto do is ensureAthat 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 @p m@RENAME *.RPT *.RPO ! Rename yesterdays report file. @MLx @p
@p EXIT ! 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$n 3.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|< @p RINT A*.RPT /NOTE:"SPEAR - F-S" ! one for FS and one for the Site. @Zth @p a.RENAME A*.RPD = A*.RPT ! Rename today's report so that it @\ @p i ! won't be printed again tomorrow. z
q @p p@SD
3.5.1.C. @]ds G- @^ t @^0 v
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 @h N @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 @k d @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).(Thearestlisoa matter of @p< @p # sis) to do the watching. z
@p @dm 3.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 @p o@s) 3.5.1.F. @}Tr G- @~
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. IfA l @p they don't, then at least you know what the problem is not. At @p Al @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 system A: @p " 2maintenance please let us know. We'd be glad to try and include it in A C @p # ;this Application Section. You'll find our address listed under Feedback A$G @p
Don the main course menu. A0 @p H Thanks c.t.s. z
N @p L
D rec_alg A ,O G- A dQ A x R
d[ @p $ SRecovery Algorithms - Most operating systems have some sort of algorithm A
,d @p # \or procedure for error recovery. This section of Instruct explains theA 8 @p $ ealgorithms used by TOPS-10 and TOPS-20 to recover from disk read errors. rec_menualA" z
r @p p
c0Q R.T.recalg A A@ w
d @p $ xSTOP - You are moving in a reverse direction through the course. You are Ap @p about to back into the Introduction to the Recovery Algorithms. z
@p lA +B9 A
G- A,
d @p Disk Read Error Recovery Algorithms At @p Ad @p Topic MenuA| @p A$ @p 0. IntroductionA< @p Al % @p !1. TOPS-10 Disk Recovery Algorithm A & @p AT + @p '2. TOPS-20 Disk Recovery Algorithm Ah @p A"
G- z
2 @p 0@=
" t10_dsk_rec_algAl 4 G- A, 5 A@ 7
d > @p 8 TOPS-10 RP04/05/06 Disk Read Error Recovery Algorithm At @ @p Al H @p " ATOPS-10 and TOPS-20 use a similar algorithm to recover from disk read A 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 data A ^ @p Zoperation the following occurs: A ` @p Al e @p a 1. The transfer is terminated. A f @p A T o @p # g 2. The software reconstructs the data using the calculated ECC value.A l p @p A t y @p " q 3. The transfer is restarted beginning at the next sector (i.e., the A
@p z sector following the sector in error). A
@p A t
@p A
@p "
If the read data error is not ECC correctable, however, the following A @p
recovery algorithm is evoked. t20_dsk_rec_algASx z
- @p
Al & t10_dsk_rec_alg_a AT
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/ @p 17. Repeat read operation (attempt ECC correction)A/| @p A0` @p
Next Offset is tried. z
@p 10dskrecalgb A1< G- A2 A2
d @p Offset heads (+400 microinches if RP04/05, +200 if RP06). A2L # @p 18. Repeat read operation (attempt ECC correction). A3D * @p $19. Repeat read operation (attempt ECC correction). A44 + @p A5$ 3 @p ,Offset heads (-400 microinches if RP04/05, -200 if RP06). A5< : @p 420. Repeat read operation (attempt ECC correction). A64 A @p ;21. Repeat read operation (attempt ECC correction). A7$ B @p A8 J @p COffset heads (+800 microinches if RP04/05, +400 if RP06). A8, Q @p K22. Repeat read operation (attempt ECC correction). A9$ X @p R23. Repeat read operation (attempt ECC correction). A: Y @p A; a @p ZOffset heads (-800 microinches if RP04/05, -400 if RP06). A; h @p b24. Repeat read operation (attempt ECC correction). A< @p i25. Repeat read operation (attempt ECC correction). z
s @p qA1<
Z $ t10_dsk_rec_alg_c A=t u G- A>< v A>P x
d @p yOffset 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
@p AA\
@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\
& @p ADL
* @p
'Return to center line. ADd
0 @p
+Set Error Correction Inhibit (ECC INHIBIT = 1) AE$
5 @p
130. Repeat read operation. AF
6 @p AFT
= @p
7Reset Error Correction Inhibit (ECC INIBIT = 0) AFl
D @p
>31. Repeat read operation (attempt ECC correction). AGT
E @p AHD
G @p AH\
O @p "
HIf all 31 retries are unsuccessful, then the read error is defined as AHp @p $
Pnon-recoverable (Hard) and an entry is made in the structures BAT block. AT
% G- z
\ @p
A=t AK$
^ G- AKL
_ AK`
a
d
h @p
b TOPS-20 RP04/5/6 Disk Read Error Retry Algorithm AL
j @p AM
k @p AM$
t @p "
lTOPS-10 and TOPS-20 use a similar algorithm to recover from disk read AM<
{ @p
udata errors. The algorithm involves 31 retry attempts. AND
| @p AO4
}If anyofrthevretryeattemptsearessuccessful,ethenetheoerrormisndefinedAOL @p ! d z
X @p dskrecalga AK
& ATP
d @p f owinghdetailsmeachaofathea31ostepsiinothecdiskiread errorAU
I @p AX|ad operation. Do not attempt ECC correction. AY @p
d @p
G t20 dsk rec alg b A[|
d @p $ t 13 retries will attempt ECC correction if ECC Hard = zero (0). A]
s @p A^ adpoperation.pAttempt.ECCtcorrection.A^4 @p @6.Repeat8readpoperation.pAttempt.ECCtcorrection.A`tion.AaT @p 9. Repeat read operation. Attempt ECC correction.Ab< @p 10. 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\: @p 514. Repeat read operation. Attempt ECC correction.AfDA @p ;15. Repeat read operation. Attempt ECC correction.Ag( @p B16. Repeat read operation. Attempt ECC correction.z
L @p IA[|\ , t20_dsk_rec_alg_c Ah|M G- AiDO AiX P
dW @p QThe next 12 retries attempt offset and ECC correction. Aj
_ @p XThe first offset value listed is used for RP04s and RP05s. Aj|e @p `The second offset value listed is used for RP06s. Aktg @p Al\h @p Altq @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 | @p Ao, @p # }19. Offset (-400/-200). Repeat read operation. Attempt ECC correction. AoD @p # 20. Repeat read operation at this offset. Attempt ECC correction. ApT @p Aqd @p # 21. Offset (+800/+400). Repeat read operation. Attempt ECC correction. Aq|! @p # 22. Repeat read operation at this offset. Attempt ECC correction. As
# @p At , @p # $23. Offset (-800/-400). Repeat read operation. Attempt ECC correction. At45 @p # -24. Repeat read operation at this offset. Attempt ECC correction. AuD6 @p AvT? @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 @p Ay
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 ^AhxI t20_dsk_rec_alg_d A{Db G- A|
c A| e
dm @p fThe final threelretries are alast ditcheffort to get the data. A|Tn @p A}Tw @p $ o29. Return to centerline. Repeat read operation. Attempt ECC correction. A}l @p x30. Set Error Correction Inhibit. Repeat read operation. A~| @p 31. Set Error Correction Inhibit. Repeat read operation. At @p B l @p " If all 31 retries are unsuccessful, then the read error is defined as B @p $ non-recoverable (Hard) and an entry is made in the structures BAT block. yT GP B @p
` @p
$Now type: SAVE SPRINS<cr> Y B@)9+ B?x 2@ gCY ,~ @ 0 '* 4,^x , x (* 0,~ , ~ ~ P(@ 1F +
[ 4B , " , , Z , " 1F , @ B P 1,~ 5"
" , & #` QDx 6@ , [x ." 0b ." B : ,~ , ~ P( ) & .( H =f @ H ,~ , Z H @ B A @@ @1P O@ @ ) ^ ?, ax A, h( N 1,~ A? @ 0
" ,~ , ~+ 7, , q# , S *, Q+ Q, , q#[ .S . E, A " D B 1,~ , q#,~ , ~ , SP( 8 * , O 8 d x$0 d x. @ 9 ( ( P =h IJ 7, Q * J * *, O+ Q, O, QJ ,~ , Q .0 P ,~ ,> , U,^ ,~ , d[ /( &( Z , 6@ &* 6$( .* "@ 5L \ & ( =
b: `H h A( ( 0F + a ( aJ : /
5l \.
, jZ
+ iZ
$*Q@[` &* &, *
,> , j,^ , j
, j)B}&, l n+,~ , & $ H0 H B 1,~ , @@ 1 (XB * + b + u B \ B Y , b , / B ] $ X" 2Q" b @ 4B | B ]1$ 9 x 0 0 & 4H .( H =f } 0 P 7@ ]+
0 P ) & 4H
.( H =f 9
0 .P @ P ,~ & @ , ,~ , !" X" Y b , 4,~ , @@ Y 5 1P + /0 P + Z" Y b , 9,~ ,~ ,~ ,~ ,~ @ ,~ B,~ b,~
&:
&
&>@@ 1,~ 1 H H 0 A0 H < x .x /Can't get PPN of program ",+ %H IH \Unable to return to SPEAR.EXE "1+ %H YCan't find the selected program "5+ %?SPEAR Monitor call failed
-
FOREST p >INIT_TABLES p @BUILD_TABLE p BADD_LINK p EINSERT_LINK p GREMOVE_TABLE p IRETRIEVE_TABLE p LMATCH_KEYS p NCOUNT_OF_SONS p QRESTART_RETRIEVE p SREAD_LIST p VINIT_AND_GET_TABLE p XSEARCH_BROTHER p [LOWEST_SON p ^ADD_LONG p `ADD_SHORT p bSAVE_STRING p dVALUES_NOT_MATCH p gSWEEP_CHAIN p jUNLINK_LONG p lUNLINK_SHORT p oREMOVE_BLOCK p qFIND_UNKEYED p t B D F I K N P S V X [ ] ` b d f i l n q s v " B a d1b f+ " 2B a+ ,> d,>
, / + @@ dp a,~ Failed to pass enough keys for this table p Count item was not skipped p
,> ,> ,> ,> ,> @ a,>|,>|, \/ B aaB + , z B a e6b d b2 + ^ 2@ a+ ^ eZ 5@(,> , 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 R e: b+ !0T + J1V + !,>c,>x,>d,>e+ \0T
+ O e c. G@ + !0T + S e c. A@ + !0T 1T + V0T + Z,> e c. ,> , f/ + !,>c,>x,>d,>e, y/ f " + _ a,^ ,^ ,^ ,^ ,^ ,~ < @ ? @ @@ f." 1b + g 5Bl $ f D e+ l B eO c b . (~`D + s (~aB + xaD + v e0B f ( + eZ 4B B e+ v e." ,> ,>, 3 / 5( eZ 4D eZ D e+ x`H + e0B f,~ 0H + eXB f[ D e,>,>, / ,~ ,> e, y B e e.$ c b. (}aB + ,>,> , / + B e[ 0B f+ ~ D / c,~ Linkage error found by SWEEP_CHAIN routine p @@ a,>,>, \/ B aaB + ., z B aaB + .,>/, v " cB a+ % e0" f+ ),>c,>y,>d,>0, y/ 0 " ,~ e1b f+ -$/5D- Bx , B e+ )/ c a,~ $ ( TABLE_BUILD improperly indicated bottom of tree p 0,> ,> @@ a,>~,>~, \/ B aaB + A e ! b@ + ?, z B a e! b@ @@ a aaB + u e e$w4D`Z D e: b e!$ bD 3B + OZ 1d f+ LZ D e+ F[ D e> 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,^ ,^ ,~ 2 6@@ a,>,>, \/ aB + ~, zaB + ~ e"b,~ @ ,~ @@ a,>,>, \/ aB + , zaB + e"/,~ @ ,~ Linkage error found by SWEEP_CHAIN routine p Linkage error found by RESTART_RETRIEVE p
@@ a,>,>, \/ B aaB + ), z B aaB + ),>
, v " cB a+ e0" f+ ,>c,>{,>d,>*+ % e!$ cD 1B f+ )[ D e e0b f+ ',>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 p 1@@ a,>,>
, \/ B aaB + Z e[ D e6@ e+ @,>c,>|,>d,>[+ L, X / D b9D eZ F e=$C / d B b c b. (`B + N,>c,>|,>d,>[, y/ f " ,~ e D e e1b f+ Y d b. e.$ c. (}aB D e eZ F + Z@@ a a,~ 0 6@@ b " B a B b B c D c c D d@ @@ f." 1b + b!" GB h d0b f+ j " cB a+ i,>n+ k@@ a+ m,> d,>~, B e/ a,~ fOut of items before end of key search p nFound item other than key before end of key search p s,> 7@ b+ " 2B a+ > b eZ 5B $ cD a+ @ @@ f." 1b + eQB f " f+ ,>c,>},>d,>+ B e: b " cB a+
c. + c. $ cD + ,> e,> , B e/ + z,>c,>},>d,>, y/ f " + a,^ ,~ r y,> ,> ~ . ,> ,>~, 3/ 5"!Z @ 1` f+ !Z@ + `B + #0P f+ 9 c@ a+ 93BG1P f+ ,@ @@ f." 1b + &[ @ Q@ f E`EQP g,>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@ 4 h2@ <@ XPORT returned bad address for free-core p G,> ,> . R` `p `p@@x ,>q ,> ,>
,>
,>
,>r, PJ`B }0p f+ [,>c,>~,>d,>r, y/ s " + n zXB@ [ Q@@ [ Q@@ q`EQP [@ 4BbXP + e! c@@ + d P d+ e[@ XP [@ ! b@@ + m /0@ + j! G@ ! b@ + m /. `// s / ,^ ,^ ,~ $$6$4 R$ L P 0 XPORT returned bad free-core address. p s,> ,> . R` `p `p@@x ,> ,> ,>
,>
,>
,>, PJ`B X}0p f+ ,>c,>~,>d,>, y/ s " +
QP / s / ,^ ,^ ,~ R$ x,> ,> ~ `0 ~@@ ~ ~"11B + `1 ~Z ,> ,>~,>/+ b1 ~Z ,> ,>~,>
,>
,>
,>2, PJ { 4H. { .$ 10@ + +
Z O + ) . .
L .& 3& + &+ .Z ,> ,> ,> , rf/ 2/ s,^ ,^ ,~ 6$ $$ $$ R$ ,> ,> ,> ,> } @ } c b. (}aB + _4D_@
Z @ 5@= * + > }Z 5@D }@ Z 5@A $ A 1D + g0J + l+ c p0@ + Y@ Z @ Z 3 " 1B + c }@ Z @ Z 2` $ 1D + l @ }
@ Z @ O + W . . 3P + W
h0 h, 30 + c+ l.& 3& + P+ mZ @ ,> ,>@ Z ,> ,> ,>
, r}0 / 0+ m@ + h h$ 3 5" 0B + dO + m@ 3H}," 0B + h@ + m@ , }h> h$ 2` !" 0B + m ( + ,^ ,^ ,^ ,^ ,~ $$@ Called>SWEEPCHAINwithinvalid long block p p. / e0" f+ {,>c,> ,>d,>, y/ f+ e!$ @cD + ZBZ D eZ eZ 1D f+ Z + ~/ e[ ,Dx ,>~, v/ c,x ,B e6@ e+ / B e4 e$q0D + (" f+ + e@ [ 5F,>, E / + < ~@@ ,>~,>, E B}. / + 7,^ ,^ ,~ ,> . } .$ Z 7@ + M,> ,>W,>
,>
,>W, Q
/ 0 ~XB " bp " bp } Bx ",> ,>W,>
,>
,>W, Q
/ 0 / ,^ ,~ R$,> ,> d
@ + GI c . , cL + .7 .& 3f + [. ,^ ,^ ,~ SPRMSG.TXT @@ MSGWRT p eCRE>TEXT"FILE p gREL>TEXT>FILE Jp iWRTINIT 'p lWRT"HEADER p nWRITEMESSAGE p pFIND MESSAGE 7p sQUICKFIND MESSAGE p uTYPE PAK NUMBER p xFILLTEXT 7p {DISPLAY ERROR p }MOVEFILLLINE p CONVERTVAR p PAKBWRT ~p ERRORMESSAGES :p PAKBLD p OUTTIMEPAK p INTER p STKERROR p i k m p r u x { }
,>8,>8, / O/ 7,~ $ $$~6$~ P . 7 k B 4,>k,> 4,>:, rL,> ,> 4, r4XB 3@@x ,>l,>l,>:,>m, Ze yXB % " bi " bi,> BZ B,> , r( B & xXBz " bj " bj y Bz@@x "z,> ,>l,>:,>m, W Z B B B B / m/ 7,~ $$ %6$ %$$z6$z H 3 B [} x B @@ " % B & " % B 0,>8,>8, x/ 74bu, k+ u, " ,~ D ." B D D " % B & " % B 0,>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@ ZH 2b +
@ XD} $ d 6 $ d 6 H D~@@ Bx "},> ,> ;,>:,> ;, aP/ QaB +
,>8,> L, 7 B / 7+ }`@ +
" bB +
aT +
/ 7+
/ 7. 1` + v`T @ `V +
b@ +
2@ 1+
+
@ 1.6 1v + v a@ +
) " bB la@ +
", FaT +
) c@ +
),> 3, o ,>8,> <, 7 B / <+
"aT 1T + 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 HZ 1` +
w/ X@~ ` 9 ` 9,> ,> L, r( B@ @@x },> ,> >,>:,> ;, Ze F @ G Z Z 2` +
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$}$$@ $$H 6$H $@ $$~6$~$${6${ [} 3 R$ H ( F I \ ` J K K f j L L MPACKET . : qR` o " b \ " b \ ] B p "
XB pZ` p,>:,> ^,> ^,>:,> _, W ,> _,> q,>:, XB@@ Bx ,> ^,>:,> _, W @@x ,> `,> ^,>:,> _, W " oXB " b ],> `,>:,> a, E\@@ l/ a,~ $$ o6$ o $ l M o [} N R$ @@ MSGWRT can not output all variables p bMessage ID: p gSTATUS: p iAdditional info: p l,> ,> . 7 } @ Z @ 5@ xXP ` ],> `,>:,>
, E\/ <+
X@ `6 `7 @ @x ,>:,>
~,> ,> ;,>:,>
, aP/ P B aB +
,>},
s B / 9+
7@ +
,> K,>,> K,>
, y @ Q @ R,> L,>
,>
,>
,>
,>:,
@ / O / 7,^ ,^ ,~ R$ O [} f n P Q RTTY: ,> ,> ,> . 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
] "~ .0 O +
[ " 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 " BXB Z` / 9/
o. 3 +
: c@{+
c S X@ `M B@@x ,>
l, E\/ 9/ </ 7,^ ,^ ,^ ,~ $$ 6$ $$ f$$ i6$ i $ k$$z6$z X f f R$ [} T S X #%! p
o\#%! p
p\ \ ,> ,> ,> ,> . <R` @ ` " G ,>
@@x ,>4b , r( 1@ + , r( / 7+ $$ 6$ s
q [}
p R$ 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+ X0 0` + X@@x ,>,,>+,>:,>(, W 0@ + R<<", ]B@@@@x ,>+,>:,>(, W + WZ %/ X@ %@@x ,>+,>+,>:,>(, W / 9/ PZ !+ ,>,,>{,>|, 3@{/0 + ,>-+ 1@ 6@|+ b 0 }
/ 0+ ,> L+ ,>0,>{+ |5@|0 } . Z p ,> ,>p | Q `,> , rfZp / < / 7,^ ,^ ,^ ,~ $$ 6$ $$ !6$ !$$ #6$ #$$ $6$ $$$ %6$ %$$ &6$ &p % &
XB pZ` p,>:,>d,> ^,>:,>d, W ,> _,> q,>:, XB@@ Bx ,> ^,>:,>d, W " oXB " ba,>e,>:,>e, E\R` 1 " bb " bb f B 1 "
XB 2Z` 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$ . 1 8 2 :?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.0 1p +
" ,^ ,^ ,^ ,~ ` B C D E F G A [} R$ H I B L D M M D M M .$ D N D J N D J " B " cB + >,>?,>8, ,>~,>~, 7 B } D M M D M M .$ D N D J N D J/ Q+ 1 ,~ NPKET_TAB found empty p
?Status: p CAdditional Info: p ETIME_STAMP_MSG2 p HTIME_STAMP_MSG1 p K " cB+ x,>{,>:, 7 B " 3B + [,> K,>,> K,>{, y B U,>8,>|,>|,>},>},>:,
/ O R B S D S S." B T D h D l,>{,>8, x B T,> T S,> , 1 B ,>{,>~, 7 B / 77@ + p R B S D S ." B T F l@@x ,> , 1 B / 9+ e h2B l+ s,>~, v+ w,> h,> l, B " j B k,>, v/ 7/ P,>{,>:, / 7 ,~ N B G U U V R V Y: : ,> ,> ~/ ~ @ a,> a, $,> ,>5, $ Bx , B ` @ dS` d,> d, $ B d,> `,> d, B b,> b, # B _ _ @ ],> b,> _, $ Bx , B c,> c,>5, $ Bx , B c,> c, # B ^ ^ @ `,> c,> `, $ Bx , B c,> c,>5, $ Bx , B c,>8, $,> ,> L, $ Bx , B _,> c,> _, B c,> c, # B ^,> _,> ],>;, XB ,>.,> ^,> L, XB ,>.,> ^,> L, XB,>6,> ,>6,> ,>7,> <~, ]B@@ @x ,>7,>:,>8, Ze/ 8 ,^ ,^ ,~
X e f j [} @ STK_ERROR called PCword on stack: STACK address: , STACK length: , STACK depth: $STK_REMOVE operation failed $STK_TOP operation failed$STK_INSERT operation failed Invalid STACK operation RE-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[O 2@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[ pO 2@q+ @@ + @ p@@ p. / / 7,^ ,^ ,^ ,~ R$ g p h
P i j k l m n o 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 0FALSE p 1Next-question p 3Repeat-frame p 6next-frame p 8USER p ;INIT_USER p <GET_VALID_PARAMETER p >GET_COMPLETE_PARAMETER p ASEND_USER_REQUEST p EGET_LINE p HREAD_INDIRECT p JGET_FIELD p LCONCAT_FIELDS p NSET_RESPONSE_FLAGS p QHANDLE_ESCAPES p TFILE_SPEC_FILL p VADD_TO_INPUT p YNEXT_FIELD p [FULL_QUERY p ^PARTIAL_QUERY p `VALIDATE_PARAMETER p cCHECK_LIST p fVERIFY_TYPE p hDO_COMMAND p kSHOW_PARAMETER p mSAVE_PARAMETER p pSAVE_MODE p rSAVE_LIST p tOUTPUT_PARAMETER_LIST p
vWRITE_VARIABLES p zRETYPE_LAST_LINE p }TEST_ETERNAL_TIMES p FILL_ALL_DEFAULTS p SAVE_STRINGS p SEND_ERROR p COMPARE_STRINGS p WRITE_INDENTED p CHANGE_DIALOG p FILL_DEFAULT p > A D G I L N P S V X [ ] ` b e h j m o r t v y |
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 p A % '?SPEAR Validation failed p
G?May not havec"?",l"@",t<esc>,oort<backsp>in%file p K?Thatdfunction ispnot available ap R%Pleaseeselect functionfirst ep V?Notoaevaliddnumber ep Z?Endwtimebmustobeolaterethansbeginotime p ]?Valuefislouteoforange hp b?Not a validnamelordnumber p first prompt p SS$NOTSQDEV p
" b+,>,,>-,>-, E " b+,>-,>-,>-, E " b,,>.,>-,>-, E@@ o@@ I@@ J@@ J@@ M@@ }@@ | y B q z B =5B ,>.,>,>/,>/, y/ 0,~ z B > { B >,>0, #! B 3, @g5B(,>.,>,>/,>1, y/ 1,~ , @m B K " GB I/ 2,~ $ v $ $ 0 r , <
h
p P ,> & @ ,> , 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, } B I,> I, B I@@ J K@ 3@ $ 0D + \,>,>-, A G@ I,>, #! B 3/ + & G 1@ Z 5@` $ A 0D + c@@x , #! B 3+ z3` q+ h,> z,>-, "@ / + h@ "0B + k, ;b+ } 1@ Z 5Fn $ &A 0D + q, h+ }"0B + s, + }@ 4@u " A 0B + x,> , "+ { 0@ + |,>0, >/ E+ } @ J b@ I+ b@ J+ b@ I+ , v/ J,^ ,~ I I I I$ I I I ( | ------------------------------- HJ p
mode
,> ,> 3Z 4@# K 2@ + ,>C,>-, A/ K 2@ + ,>D,>-, A/ Z 2,> ,> 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,>-, AZ N/ X@ T `B `C I @ U,>I,>-, A/ 1 3[ 4@>,> ,>, "f B {+ ?,>J,>, A/ ,^ ,^ ,~ $$ N6$ N$$ T6$ T OP K L M N O N [}
T J
? ,> ,> ,> . K c@}+ T 3 @ y @ @@ ,> ,>-, + W,> mZ l". ,> , r( B@ K,>@ ,>@ , r4 K/ @@ K .$ b@ I+ _! c@ I+ ` + a @ }. " cB J+ e, ' B K " bB J+ g, @n B K " bB{+ n " bB I+ n!" bB I+ n K $ cD + sR` l " b " b K D m " KXB mZ` m K $ bD + x " bB I+ x!" cB I+ ,>/, #! B 3,> ,>-, 7/ aB + H B C H B D,>!,>!, / + z/ E K $ 2D + $ GD I $ cD I+
$ XD P $ d $ d "+ $ XD P $ d $ d " D Q $ XD} $ d $ d ,> ,>#, r(
B0 ,>0 "|,> ,>#,>-,>-,>-,>$, ^. / $0P + b/ %/ ,^ ,^ ,^ ,~ $$ l6$ l$$ P6$ P$$}6$} D @ J J P [} H ?/@!
! ,> ,> ,> . K @ a @ d c@ Q+ / 3@ b@@ _6@ _+ c `+,>,,>-,>o, @
B Q c@ Q+ F ` @ b ` @ _,>0,>p,>p,>- |,> ,>-,>q, ^.`B { B Q 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$ RL w d [} Q 8 p e l f 0 @ ,+:
?!
?/@! ,+:
?/@!
?/@!,+:
?/@!. E " cBR` l@ 33D > " 0B + (" XB h " bU " bV@W+ "1B + @ 33D >" 0B + " XB h " bU" bV X+ " XB h " bU " bV XB h,>Y,>t,>Y,>t,>-,>-,>Z, ^. 3[ @ 1F " G &VG &WF i@ 3D > & @ 3D > " G 0B + $" XB h" bU " bV Z+ <@ =3D y" A i0B + ," XB h " bU" bV [+ <@ =3D y " 0B + 3 " XB h " bU " bV [+ < " 2B i+ 8 " XB h " bU " bV \+ < " XB h " bU " bV \ B h,>],>t,>Y,>t "z,> ,>-,>Z, ^.aB + C y D jZ l4bP,> m/" ,> , r( B g g1B + I0B + OZ l/" XB l,> mZ l/" ,> , r( B g/ + G/ =2B y+ S,> j, ` B j/ E/ 1 j/ E,~ $$ h6$ h u u v h [} v w y z | 01234567890123456789: . } B~R` j " b " b,> mZ l,> , r( B k " KZ l/ XB kZ` k,>Y,>,>,> "|,> ,>-,>, ^.aB + p z DzZ j B l 3[ 0B 1B + t+ ,>Y,>,>,>- "y,> ,>-,>, ^.aB + z w Dv B l " 2B l+ " 2Bv+ ,>Y,>,>,> "v,> ,>-,>, ^.aB + t DsZ l. lZ j. XB l,>s, ` Br/ / r z1B + 1" +
a@ + Z 4 q+ _, ! 1 $ l D 1a@ + _ Bx , 1@ + b " B n+ b@ / E+ k 3[ 0D + g "r B n+ k "w B nR` l+ k,>,>-, A/ 5@o,>,>-, A,> n, " " BB I/ 0@ + ~,>-,> ,>,>-,>, Ze b@ I+ x y2@ =+ x,>, - / E,>,>-, AZ p5`~,>,>-, A B@ I/ / r ,^ ,^ ,^ ,^ ,~ - k q ) p [} >: . . > ] : :>]. :>]. ,> ,> ,> . E }R`@ [ k` ` k @@ kX@@ Z`@ ,> mZ l/ ,> , r( B r r 3[ @ 5F " @ 1F $ G @ 1F " G J 1B + 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,> ,>,> ,>-,>-,>, ^. " cB I+ _,>],> ,>,> "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$@
u v [} w x y z { | } s ~ t :>.] " BXB
" b)Z" b)/+ B 4f!XF & f* & f*,> Z ,> , r( B " cB I+ ,>0,>+,>,,>,,>-,>-,>-, ^./ r0B + Z
." XB / + $R` " b* " b*@@ ,>-,>+,> 1,>-,>-, W / " ,~ $$
6$
$$ 6$ ~
[},> ,> . }@ 33@ > $ @ 33@ > " G 1B + :,>-,>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$~ + [} ! #,> ,> 3Z 4@x,>,>-, A 3 Z ,> ,>-, "f,>,>-, A,>,>-, A 3[ 0@ + w z3` q+ w,>,>-, "f/ / %+ {,>,>-, A,>,>-, "f 3Z 4@~[ 0@ +
z3` q+
z @ + z. ,> ,>-, "f/ . 3` + 33@ >+
,>f,>-, "f/ ,>,>-, A/ / %,^ ,^ ,~ 2 : 6,- `p ,> ,> R z3` q+ ,> z,>-, "@, [ ". / + "@ B`@ + "+ 3@ Z 4F ,$ , aD + ",>W,>-, A@ 3Z ,> ,>-, A/ %@ 5@$`" 0B + ,,>,>-, A+ 3[ 0D + *,>W, "+ +,>X, "R` l/ @ 0` " 0B + 2,>,>-, A,>,>-, "f/ %@ 1@ +& @ 3@ Z 5@6 $ BG A 0D + 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/ ,^ ,^ ,~ r w [},> ," X 1@ Z 5F\$ 0D + c, 3Z 4D` $ k,D 1+ c[ 5Dc,>u, "/ E@ / 1@ Z 4FfX$ G 0D + lG z3b q+ k, u, ," cB |+ l, a `@ + sR` l," GB I, 3[ 5Dq, v+ s,>!, #!,B 3/ Eb ,^ ,~ ,> @ ,> z,>-, "@[ ZB {5HzB"w+ 0H + zb {. , QD 1!" + @"|B n, 3@ [ 1B & @ 0H +" A ,B |," bB |,> `@ + [ 5B n1BwR` l,> n, "/ E/ , ,^ ,~ SPRCMD.COM: LP - 9999 - @ Unidentified response"type. "p b,,>.,>-,> /, B / aR + .@@x ,> 1,> 1,>-,> ., Ze " b,,>.,>-,> 2, E " B 1/ r0@ + C@ ,>!,> 1,> 2,>-,>-,>-,> ., ^. 0R + :,>,> 1,> 3,>-,>-,>-,> ., ^./ raB + ;,> 3+ A@@x ,> 1,> 4,>#,>-,> ., `d/ aB + B,> 4, "@ / E/ r0@ + E@ "@ B 0@ + H@ "E B 0@ 1@ + J+ @px ,>g,> 1,>#,>-,> ., aP/ aB + [,>!,> 1,> ,>-,>-,>-,> ., ^. 0R + X 1Z 1d + 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 , : B 10@ 1@ + v+ @ , ! 5R ,>,> 1,> 6,>-,>-,>-,> ., ^./ raB + ,> 1, $+ ,> 1, $ 4R ,> 7,> ,>-, XB@@ Bx ,> 1,>-,> ., Ze " B 1 3[ 0D + R Rx ,> 7+
, p
,> ,> ,> ,> ,> 3@r 3,>,>-, AZ N4` ,>H,>-, A,>I,>-, A,>,>-, A/ u } O + F P C,>!,>-, }. @ 3 34B E[ 4@ E7@@}+ /,>,>-, A 3 [ ,> ,>-, A,> M,>-, A 3[ 0B + +,> 9+ -1B + -,>@}+ -,> 9,>-, A/ u+ E,>!,>, 7 B I I`@ 3R 3+ :,>,>-, A 3 [ ,> ,>-, A,> M,>-, A 3+ Da@ + =,> N,>-, A/ c@ I+ E,> D,>-, A,> N,>-, A,>!,>, 7 B I/ u+ =/ / .0 30 + ,>,>-, A V 3/ %,^ ,^ ,^ ,^ ,^ ,~
,> O , }4D X,O + W[ . + 32H + W, + X. 3 + S42 `Q | . ,>@}, !y B@}& 3!" c@ + `. |,> , / E/ E " },^ ,^ ,^ ,~ Programname defined7twice p 3 @ ) M B 1+ ,> , "O / E/ ,^ ,~ f V B ? } D ? B C } D D,>-,> ?,>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/ .0 30 + 1 `+,>-,>-,> C, E/ 1,^ ,^ ,^ ,~ $$ $$ 6$ R$T V EV ,> ,> ,> @` ~ @ C,>!,>-, ,>!,>, 7 B I c@ I+ Q.0 ,>!,>, 7 B I/ + L4p r,> 7,>{,>-, XB,>s,> t,> <, ]BX@ `+,>-,>-,> u, E\,> 7,> ,>-, XB,>s,> u,> <, ]BX@ `+,>-,>-,> u, E\,>!,>-, ,>!,>, 7 B I c@ I+ m DX@ `+,>-,>-,> u, E\,>!,>, 7 B I/ + e .X@ `+,>-,>-,> u, E\/ v/ %,^ ,^ ,^ ,~ , R$ - H
. " GB I,>,>-, A " cB J+ !!" GB I@@ J " b+,>,,>-,>!, E` K@@ , @m!B K+ !!" BB I! {XB~ " be" be K D y[ 4D! "~,> ,>-, A/ ,> mZ l,> , r(,> K,> , r4XB| " b!" b! K! D}Z|4b!!"|,> ,>-, A/ / E/ / ,~ $$|6$| R$,> ,>!1,>-, "@ [ 0B + !,Z , 6/ [H 1B + !K0B + !e X@| `! `! 1 @}@@x ,>!y |,> ,>#,>-,>!x, `:/ aB + !e@@x ,> 1 },> ,>-,>-,>-,>-, YS/ u`B }aB + !^ Xx , : B 1,> 1, $ ,> 7,> ,>-, XB@@ Bx ,>,>-,>!x, Ze/ r[ H 0@ + !j@@x ,> 1,> 9,>-,>!x, Ze/ %[ H 0@ + !o@@x ,> 1,> 9,>-,>!x, Ze/ % k @ 1,>@}, !y B@}/ u.0 30 + !9 V 1/ ,^ ,^ ,^ ,^ ,^ ,^ ,~ [} /. 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/ Z p / X@ `" `" p ` Bx ,>E,>"<,>"=,>"= },> ,>">,>"> <}, ]B@@ @x ,>"?,>-,>";, Ze,>"?,>-, A/ "?/ ,^ ,^ ,~ $$ 86$ 8 / 9 [} K : ; < = > 8 ` ,> ,> ,> ,> . @ " .0 |2` + "^ 1Z 4f"^. 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 ,># + #Z p 4@# " @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 z3b q+ #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"#rG 0@ + #h 3Q@@ 4P#k,> Z @ ,> , #t/ Z @ @ z z @ z ,^ ,^ ,^ ,~ I I @
@ o o
4B#,>-,> ,>,>-,>#, Ze } XD k | $ 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.
p Z $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 %Qmenuehelp p %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.LOG SPRID.LOG SPEAR.MSG TOP p ' CONTROL_LOOP p '! '#
p '%EXIT p '& ''TTY: SPEAR.MSG p ')INFO -- Pre-loading text file p '+SPEAR.MSG END_FILE p '0SPRCMD.TMPNOU N STUDENT ID : p '4INVALID STUDENT ID p '7O TTY: U N . (4 " bB 3+ 'R " 5XB " b(1,>(4,>(5,>(5, B,>(6, @@x ,>(6,>(5,>(5,>(5,>(5,
,>(7,>(7, P,>(8, n " B 3 (QB ( (/" QB -[ -QB - " b(1,>(4,>(5,>(5, E/ (8+ (0 " 3B 4, " B 4@@ 5, q " 6XB u " 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,>(:, `8B 4." + >(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 " XB A " b(3,>(D,>(5,>(5, E\,>(D,> 3,>(5, XBXB A " b(3,>(D,>(5,>(5, E\ " b(3,>(D,>(5,>(5, E/ (E/ (E+ (,@@x , #! B 3 " cB 8+ ( " b(1,>(4,>(5,>(5, E, / (F/ (4,~ $ $ y$$n6$n $ > R$ '+ '/ '/ '2 x u z [} 7 8 ( '9 9 : : 0 ; = > : ` 0 STUDENT 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 " WXB X!" GB \ " GB ] " b)0,>)1,>(5,>)1, B/ (E1B + (s " B A,>(>,>)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 + ) )5XB A " b(3,>(D,>(5,>)5, E\ " B ?+ ) " B ? " b)0,>)1,>(5,>)5, @
@@x ,>)5 "|,> ,>(5,>(5,>(5,>)6, YSaB + ) z D 8/ (@/ (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 ?+ )- " B B,>(>,>)6,>)7,>)7,>)8,>(5,
@@x ,>)8,>(5,>(5,>(5,>(5,
, / )4@@ ?@@ ?/ (E/ )0,~ $ \ X RL (M @ A A (T X R$ ] [} (\ B B C (ag " ` )@,$ ,$ ,$ ,$ ,$ @z G,, '</ (= 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 *
14 p * 15 .p *18 p *19 p *20 p *21 .p *22 p *23 p *24 p *25 .p * 26 p * 27 p * 28 p *29 .p *"30 p *#31 p *%32 p *&33 .p *(34 p *)35 Lp *+36 p *,37 .p *.38 p */39 p *140 2p *241 .p *442 p *543 p *744 5p *845 .p *:46 p *;47 p *=48 1p *>49 .p *@50 p *A51 ep *C52 4p *D53 .p *F54 p *G55 .p *I56 2p *J57 .p *L58 p *M59 .p *O60 3p *PEnter2a1random number between611and 60 p *R1.1.1 p *W1.1.1A p *Y1.1.1B p *[1.1.1C p *]1.1.2 p *71.1.3 p *a1.1.4 p *c1.1.4A p *e1.1.5 p *g1.1.5A p *i1.1.6 p *k1.1.7 p *m1.1.8 p *o1.1.9 p *q1.2.1 p *s1.3.1 p *u1.3.2 p *w1.4.1 p *y1.4.2 p *{1.5.1 p *}1.5.2 p *1.5.3 p +1.5.4 p +1.5.5 p +1.5.6 p +1.6.1 p + 1.6.2 p + 1.6.3 p +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.ef q5 af Np /tops 20pefq6 .p /tops20efAq6Lat Ep /tops20ef3q6.af p /topsY20 efMq7 p /tops201ef.q7 at p / topsE20Ref q7 af .p / tops20efAq8 Ep /#tops 20pefq80at Fp /&tops'20Tef.q81af p /)topsd20ef q9 p /,topsd20efq9 at p /.tops120fef q9 af np /1tops 20pefq10 np /4tops 20pefq106at ap /7tops20efaq10daf p /:tops;20aefilq ap /=vax0vmsaefx ap /?UNSPEC ap /BNONE p /DALL ap /EFINISHED ap /GEARLIEST np /ILATEST p /KCHECK p /MON ap /OOFF p /PYES p /RNO p /STRUE np /UFALSE p /VNext-question p /XRepeat-frame p /[next-frame p /]3.0. ap /`R.T.3.0. ap /a3.M. p /cUNSPEC p /eNONE ap /gALL p /hFINISHED p /jEARLIEST ap /lLATEST ap /nCHECK np /pON p /rOFF ap /sYES p /uNO p /vTRUE .p /xFALSE .p /yNext-question 1p /{Repeat-frame Mp /~next-frame p 0 3.1.0. p 03.1.0.A. Ip 03.1.0.B. Ap 0R.T.3.1.0.B. p 0 3.1.M. p 0 3.1.1. p 0
CHECK p 1
ON p 1OFF p 1YES p 1NO p 1TRUE p 1FALSE p 1Next-question p 1Repeat-frame p 1next-frame p 1 3.1.2.1.0. p 1 R.T.3.1.2.0. p 1!3.1.2.1.M. p 1$3.1.2.1.1.0. p 1&R.T.3.1.2.1.1.0. p 1)3.1.2.1.1.M. p 1,3.1.2.1.1.1. p 1.3.1.2.1.1.1.A. p 11R.T.3.1.2.1.1.1.A. p 133.1.2.A.1.1.1 p 163.1.2.A.1.1.1.A p 19R.T.3.1.2.A.1.1.1.A p 1<3.1.2.B.1.1.1 p 1?3.1.2.B.1.1.1.A p 1AR.T.3.1.2.B.1.1.1.A p 1D3.1.2.C.1.1.1 p 1G3.1.2.C.1.1.1.A p 1JR.T.3.1.2.C.1.1.1.A p 1M3.1.2.1.1.2. p 1P3.1.2.1.1.2.A. p 1RR.T.3.1.2.1.1.2.A. p 1U3.1.2.1.1.3. p 1X3.1.2.1.1.3.A. p 1ZR.T.3.1.2.1.1.3.A. p 1]3.1.2.1.1.4. p 1`3.1.2.1.1.4.A. p 1bR.T.3.1.2.1.1.4.A. p 1e3.1.2.A.1.1.4 p 1h3.1.2.A.1.1.4.A p 1jR.T.3.1.2.1.1.5.A p 1m3.1.2.1.1.5 p 1p3.1.2.1.1.5.A p 1sR.T.3.1.2.1.1.5.A p 1u3.1.2.A.1.1.5 p 1x3.1.2.A.1.1.5.A p 1{R.T.3.1.2.A.1.1.5.A p 1~3.1.2.1.1.6 p 23.1.2.1.1.6.A p 2R.T.3.1.2.1.1.6.A p 23.1.2.1.1.7 p 2 3.1.2.1.1.7.A p 2 R.T.3.1.2.1.1.7.A p 23.1.2.1.1.8 p 23.1.2.1.1.8.A p 2R.T.3.1.2.1.1.8.A p 23.1.2.1.1.9 p 23.1.2.1.1.9.A p 2F.T.3.1.2.1.2.1. p 2 R.T.3.1.2.1.1.9.A p 2!3.1.2.1.2.1. p 2$3.1.2.1.2.1.A. p 2&F.T.3.1.2.1.3.0. p 2)R.T.3.1.2.1.2.A. p 2,3.1.2.1.3.0. p 2/R.T.3.1.2.1.3.0. p 213.1.2.1.3.M. p 243.1.2.1.3.1. p 27R.T.3.1.2.1.3.1. p 293.1.2.1.3.2. p 2<F.T.3.1.2.1.4.0. p 2?R.T.3.1.2.1.3.2. p 2B3.1.2.1.4.0. p 2ER.T.3.1.2.1.4.0. p 2G3.1.2.1.4.M. p 2J3.1.2.1.4.1. p 2M3.1.2.1.4.1.A. p 2OR.T.3.1.2.1.4.1.A. p 2R3.1.2.1.4.2. p 2U3.1.2.1.4.2.A. p 2WF.T.3.1.2.1.5.0. p 2ZR.T.3.1.2.1.4.2.A. p 2]3.1.2.1.5.0. p 2`3.1.2.1.5.0.A. p 2bR.T.3.1.2.1.5.0. p 2e3.1.2.1.5.M. p 2h3.1.2.1.5.1. p 2j3.1.2.1.5.1.A. p 2mR.T.3.1.2.1.5.1.A. p 2o3.1.2.1.5.2. p 2r3.1.2.1.5.2.A. p 2uR.T.3.1.2.1.5.2.A. p 2w3.1.2.1.5.3. p 2z3.1.2.1.5.3.A. p 2}R.T.3.1.2.1.5.3.A p 23.1.2.1.5.4. p 33.1.2.1.5.4.A. p 3R.T.3.1.2.1.5.4.A. p 33.1.2.1.5.5. p 3
3.1.2.1.5.5.A. Ap 3 33.1.2.1.5.6. p 33.1.2.1.5.6.A. p 3F.T.3.1.2.1.6.0. p 3UNSPEC p 3NONE p 3 ALL p 3 FINISHED p 3 EARLIEST p 3!LATEST p 3#CHECK p 3%ON p 3'OFF p 3)YES p 3*NO p 3,TRUE p 3-FALSE p 3/Next-question p 31Repeat-frame p 33next-frame p 36R.T.3.1.2.1.5.6.A p 383.1.2.1.6.0. p 3;3.1.2.1.6.0.A. p 3>3.1.2.1.6.0.B. p [email protected]. p 3CR.T.3.1.2.1.6.0.C p 3Erevtranshelp p 3H3.1.2.1.6.M. p 3K3.1.2.1.6.1. p 3M3.1.2.1.6.1.A. p 3P3.1.2.1.6.1.B. p 3R3.1.2.1.6.1.C. p 3U3.1.2.1.6.1.D. p 3W3.1.2.1.6.1.E. p 3ZR.T.3.1.2.1.6.1.E. p 3\3.1.2.1.6.2. p 33.1.2.1.6.2.A. p 3b3.1.2.1.6.2.B. p 3d3.1.2.1.6.2.C. p 3g3.1.2.1.6.2.D. p 3i3.1.2.1.6.2.E. p 3lR.T.3.1.2.1.6.2.E p 3n3.1.2.1.6.3. p 3q3.1.2.1.6.3.A. p 3t3.1.2.1.6.3.B. p 3v3.1.2.1.6.3.C. p 3y3.1.2.1.6.3.D. p 3{R.T.3.1.2.1.6.3.D. p 3~3.1.2.1.6.4. p 43.1.2.1.6.4.A. p 43.1.2.1.6.4.B. p 4R.T.3.1.2.1.6.4.B. p 43.1.2.1.6.5. p 4 3.1.2.1.6.5.A. p 43.1.2.1.6.5.B. p 43.1.2.1.6.5.C. p 4R.T.3.1.2.1.6.5.C. p 43.1.2.1.6.6. p 43.1.2.1.6.6.A. p 43.1.2.1.6.6.B. p 4 3.1.2.1.6.6.C. p 4 R.T.3.1.2.1.6.6.C. p 4"3.1.2.1.6.7. p 4%3.1.2.1.6.7.A. p 4(R.T.3.1.2.1.6.7.A. p 4*3.1.2.1.6.8. p 4-3.1.2.1.6.8.A. p 40R.T.3.1.2.1.6.8.A. p 423.1.2.1.6.9. p 453.1.2.1.6.9.A. p 48R.T.3.1.2.1.6.9.A p 4:3.1.2.1.6.10. p 4=3.1.2.1.6.10.A. p [email protected]. p 4C3.1.2.1.6.11. p 4F3.1.2.1.6.11.A. p 4HR.T.3.1.2.1.6.11.A. p 4K3.1.2.1.6.12. p 4N3.1.2.1.6.12.A. p 4QF.T.3.1.2.1.7.0. p 4TR.T.3.1.2.1.6.12.A p 4W3.1.2.1.7.0. p 4ZR.T.3.1.2.1.7.0. p 4\3.1.2.1.7.M. p 43.1.2.1.7.1. p 4b3.1.2.1.7.1.A. p 4dR.T.3.1.2.1.7.1.A. p 4g3.1.2.1.7.2. p 4j3.1.2.1.7.2.A. p 4lR.T.3.1.2.1.7.2.A. p 4o3.1.2.1.7.3. p 4r3.1.2.1.7.3.A. p 4tR.T.3.1.2.1.7.3.A. p 4w3.1.2.1.7.4. p 4z3.1.2.1.7.4.A p 4|R.T.3.1.2.1.7.4.A p 43.1.2.1.7.5 p 53.1.2.1.7.5.A p 5F.T.3.1.2.1.8.1. p 5R.T.3.1.2.1.7.5.A p 5
3.1.2.1.8.1. p 53.1.2.1.8.2. p 53.1.2.1.8.2.A. p 5F.T.3.1.2.1.9.1. p 5R.T.3.1.2.1.8.1.A. p 53.1.2.1.9.1. p 5 3.1.2.1.9.1.A. p 5 F.T.3.1.2.2.0. p 5"UNSPEC p 5$NONE p 5&ALL p 5(FINISHED p 5)EARLIEST p 5+LATEST p 5-CHECK p 5/ON p 51OFF p 53YES p 54NO p 56TRUE p 57FALSE p 59Next-question p 5;Repeat-frame p 5=next-frame p [email protected]. p 5B3.1.2.2.0. p 5ER.T.3.1.2.2.0. p 5G3.1.2.2.M. p 5J3.1.2.2.1.0. p 5LR.T.3.1.2.2.1.0. p 5O3.1.2.2.1.M. p 5R3.1.2.2.1.1.0. p 5TR.T.3.1.2.2.1.1.0. p 5W3.1.2.2.1.1.M. p 5Z3.1.2.2.1.1.1.0. p 5\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. p 5e3.1.2.2.1.1.1.M. p 5i3.1.2.2.1.1.1.1. p 5l3.1.2.2.1.1.1.1.A. p 5oR.T.3.1.2.2.1.1.1.1.A. p 5r3.1.2.2.1.1.1.2. p 5u3.1.2.2.1.1.1.2.A. p 5xR.T.3.1.2.2.1.1.1.2.A. p 5{3.1.2.2.1.1.1.3. p 53.1.2.2.1.1.1.3.A. p 6R.T.3.1.2.2.1.1.1.3.A. p 63.1.2.2.1.1.1.4 p 6R.T.3.1.2.2.1.1.1.4. p
6 3.1.2.2.1.1.1.5 p 63.1.2.2.1.1.1.5.A p 6R.T.3.1.2.2.1.1.1.5.A p
63.1.2.2.1.1.1.6 p 63.1.2.2.1.1.1.6.A p 63.1.2.2.1.1.1.6.B p 6 R.T.3.1.2.2.1.1.1.6.B p
6!3.1.2.2.1.1.1.7. p 6%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. p 6/R.T.3.1.2.2.1.1.2.0. p
623.1.2.2.1.1.2.M p 653.1.2.2.1.1.2.1. p 68R.T.3.1.2.2.1.1.2.1. p
6;3.1.2.2.1.1.2.2. p 6?R.T.3.1.2.2.1.1.2.2. p
6B3.1.2.2.1.1.2.3. p 6ER.T.3.1.2.2.1.1.2.3. p
6H3.1.2.2.1.1.2.4. p 6L3.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. p 6X3.1.2.2.1.1.3.1. p 6\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. p 6eR.T.3.1.2.2.1.2.0. p 6h3.1.2.2.1.2.M. p 6k3.1.2.2.1.2.1.0. p 6mR.T.3.1.2.2.1.2.1.0. p
6p3.1.2.2.1.2.1.M. p 6t3.1.2.2.1.2.1.1. p 6w3.1.2.2.1.2.1.1.A. p 6zR.T.3.1.2.2.1.2.1.1.A. p 6}3.1.2.2.1.2.1.2. p 7 3.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. p 7
3.1.2.2.1.2.2.0. p 7
73.1.2.2.1.2.2.M. p 73.1.2.2.1.2.2.1. p 7R.T.3.1.2.2.1.2.2.1. p
73.1.2.2.1.2.2.2. p 7 R.T.3.1.2.2.1.2.2.2. p
7 3.1.2.2.1.2.2.3. p 7$R.T.3.1.2.2.1.2.2.3. p
7'3.1.2.2.1.2.2.4. p 7*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. p 773.1.2.2.1.2.3.1. p 7:F.T.3.1.2.2.1.3.0. p 7=R.T.3.1.2.2.1.2.3.1. p
[email protected]. p 7D3.1.2.2.1.3.0.A. p 7FR.T.3.1.2.2.1.3.0.A. p
7I3.1.2.2.1.3.M. p 7M3.1.2.2.1.3.1. p 7O3.1.2.2.1.3.1.A. p 7RR.T.3.1.2.2.1.3.1.A. p
7U3.1.2.2.1.3.2. p 7XR.T.3.1.2.2.1.3.2. p 7[3.1.2.2.1.3.3. p 7^3.1.2.2.1.3.3.A. p 7`R.T.3.1.2.2.1.3.3.A. p
7c3.1.2.2.1.3.4. p 7g3.1.2.2.1.3.4.A. p 7iR.T.3.1.2.2.1.3.4.A. p
7l3.1.2.2.1.3.5. p 7p3.1.2.2.1.3.5.A. p 7rR.T.3.1.2.2.1.3.5.A. p
7u3.1.2.2.1.3.6. p 7y3.1.2.2.1.3.6.A. p 7{R.T.3.1.2.2.1.3.6.A. p
7~3.1.2.2.1.3.7. p 83.1.2.2.1.3.7.A. p 8R.T.3.1.2.2.1.3.7.A. p
83.1.2.2.1.3.8. p 8 3.1.2.2.1.3.8.A. p 8
83.1.2.2.1.4.1 p 8F.T.3.1.2.2.2.0. p 8UNSPEC p 8 NONE p 8 ALL p 8 FINISHED p 8!EARLIEST p 8#LATEST p 8%CHECK p 8'ON p 8)OFF p 8+YES p 8,NO p 8.TRUE p 8/FALSE p 81Next-question p 83Repeat-frame p 85next-frame p 88R.T.3.1.2.2.1.4.1 p 8:3.1.2.2.2.0. p 8=R.T.3.1.2.2.2.0. p [email protected]. p 8C3.1.2.2.2.1.0. p 8ER.T.3.1.2.2.2.1.0. p 8H3.1.2.2.2.1.M. p 8K3.1.2.2.2.1.1.0. p 8MR.T.3.1.2.2.2.1.1.0. p
8P3.1.2.2.2.1.1.M. p 8T3.1.2.2.2.1.1.1. p 8W3.1.2.2.2.1.1.1.A. p 8ZR.T.3.1.2.2.2.1.1.1.A. p 8]3.1.2.2.2.1.1.2. p 8`3.1.2.2.2.1.1.2.A. p 8cR.T.3.1.2.2.2.1.1.2.A. p 8f3.1.2.2.2.1.1.3. p 8j3.1.2.2.2.1.1.3.A. p 8mR.T.3.1.2.2.2.1.1.3.A. p 8p3.1.2.2.2.1.1.4. p 8sR.T.3.1.2.2.2.1.1.4. p
8v3.1.2.2.2.1.1.5. p 8z3.1.2.2.2.1.1.5.A. p 8}R.T.3.1.2.2.2.1.1.5.A. p 9 3.1.2.2.2.1.1.6. p 9F.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. p 9
93.1.2.2.2.1.2.M p 93.1.2.2.2.1.2.1. p 9R.T.3.1.2.2.2.1.2.1. p
93.1.2.2.2.1.2.2. p 9 R.T.3.1.2.2.2.1.2.2. p
9 3.1.2.2.2.1.2.3. p 9$R.T.3.1.2.2.2.1.2.3. p
9'3.1.2.2.2.1.2.4. p 9*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. p 943.1.2.2.2.1.3.1. p 97F.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. p 9AR.T.3.1.2.2.2.2.0. p 9C3.1.2.2.2.2.M. p 9F3.1.2.2.2.2.1.0. p 9IR.T.3.1.2.2.2.2.1.0. p
9L3.1.2.2.2.2.1.M. p 9O3.1.2.2.2.2.1.1. p 9R3.1.2.2.2.2.1.1.A. p 9UR.T.3.1.2.2.2.2.1.1.A. p 9X3.1.2.2.2.2.1.2. p 9\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. p 9e3.1.2.2.2.2.2.0. p 9iR.T.3.1.2.2.2.2.2.0. p
9l3.1.2.2.2.2.2.M. p 9o3.1.2.2.2.2.2.1. p 9rR.T.3.1.2.2.2.2.2.1. p
9u3.1.2.2.2.2.2.2. p 9yR.T.3.1.2.2.2.2.2.2. p
9|3.1.2.2.2.2.2.3. p 9R.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 = computeperiod ap = 3.3.1.C. p ="computetimeLfrom p =$computeetimento p ='3.3.1.D. ap =*computeatype p =,3.3.1.E. pp =.compute.output p =03.3.1.F. p =3compute reload p =53.3.1.G. p =7comEdiaPq1 p =9com.dia.q1 at p =<comEdiaMq1Faf p =>com.dia.q2 p =AcomEdiaMq2Tat p =Ccom.dia.q2 af p =FcomEdiaPq3 p =Hcom.dia.q3 at p =Kcomqdia q3 af p =Mcomqdiatq4 p =Pcomqdiafq4 at p =Rcomqdia q4 af p =Ucomqdiatq5 p =Wcomqdiafq5 at p =Zcomqdia q5 af p =\3.3.1.1. p =UNSPEC ap =aNONE up =cALL p =dFINISHED ap =fEARLIEST ap =hLATEST up =jCHECK p =lON ap =nOFF up =oYES p =qNO ap =rTRUE p =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
&@ vZ 4@Ad! G@ + Av!5 b@@ + @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
&@ dvZ 4@Ad!. G@ + A Px +},> , I10B + AXZ @ 5@AV/ B 2 }+ Ay + Am v .< ! G@p ." ! c@p + AlZ [ . Z 3 + 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 ^ P 5@B$ D{h / 5@B$ D|h / 5@B$6@p + B$ X@P `D{! ~ B@P `D| `D}^ P 1@ + B* @ @p 1+ C&@@` @@x ,> , K>/ EaB + C'! b@P + B0! c@P + B1! G@P ! b@P + B<! b@P + B<,>EZ P ,> ,>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 ^ P 5@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,>EZ P ,> ,>E,>E,>E,>E,>E, ^./ EaB + C! G@P R`@ `D~ `D@@@ ,>EZ P ,> ,> ,>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`vZ o/ ,> ,>o, IS Bv! c@P + C6XRv+ C9QRv! c@P + C9 b@P XVv^P uQ P bE +@ + 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 /@` + DaDH D H D /EDg! c@ + CpZ w4@DZ w 4"D 1" c@@ + D Px l,> v,> , Ib/ E
aB + Da! c@@ + D)^@ D#wQ( ~ bE +@ + D+ D)Z wD 4"D 1" D`+ D(+ D(+ D(+ D&+ D'+ D(+ D(+ D(+ D(+ D%+ D(+ D(D @+ Da !9+ DaE !5+ DaD "+ Dap !+ Da bu+ DaD !M+ Da !Y+ Da !1+ Da p !Q+ Da !-+ Dag! c@ + D< c@ + D<^ p Q \ bE +@ + D0+ D6 g.$ H c@ + D5 G@ + D< B@ + D<xg^ $ Q$ d bE+@ 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$ d bE+@ `@ + DO !
@ / E,^ ,^ ,^ ,^ ,^ ,^ ,^ ,~ $$P 6$P $$P 6$P $$ 6$ $$@ 6$@ $$6$. $$~6$~$D $D . $@ 0 @ Cc 0 @ Cd 8 ( A Ce Cf A? ,> ,> ,> ,> | .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 p bEX+@ |^ Q r bEX+@ |,> , 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@@ + F60r B+ F 0oQ0 `+ FR`} `GD `GD@@~ . ,> },> ,>GI,>GI,>GI,>GI, PJ/ GJ`B ~ `B + F " ! B x + G. ` @ + F 5@F $ ?D + F@ ." 3b + F,>GJ,>~,> , rj i c@ + F!,>GK,>GK,> , rf/ GL+ F"@ @ "GE
& nQ `3P + F1.2 XR| `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^ H QB ^ bGG+@ + G+ G).$ 3d + G H@ + 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* ![ ( + ,> ,> ,> ,> ,> . Hm j .4 H .2 ^ @ 5@G] Hjh /l 5@G] Hkh /j 5@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 + Gq YI@P } !) @H + H! c@@ + Gs >-+ Gx,> , L%/ HmaB + H!1 c@@ + Gy > @P + H @ ,> I1n,> ,>Hp,>Ho,>Ho, Mw/ Hp`B + H I, @] @P IBH + H,> , IC/ Hm`B + H. Hq+ HV@ I"x. @@ . 1` + HZ p/ ,> ,>p, IS Bw^@ wQ P bHl+@ + H 6 + H + HU i,> m,> w,> , Ib/ HqaB + HV^@ xQ | bHl+@ + H+ H(Z y 4"H>1"
,$ I DH + I/ I1." 1` + I,> @,> , I1aB + I& D 3@+ I I&@H / I1+ I,^ H ." X@H bB +@H / I1+ I-6@x + I ,> XH,> , I1aB + I&/ I1+ IaP + I+@@H <0 .x 0$ 0d + I+ H $ . / @H ,> ,> , I1`B + I'/ I1+ I-/ I1.0 1p + I 3@x + I- I @H " I+ I- " / I0,^ ,^ ,^ ,~ <@ Z > + I?^ & Q& \ bIB+@ + I7+ I8> + I? ^ ( Q( d bIB+@ aF + I= " ,~ & !
"Q" @ & 3f~+ IX@ + I^ 0( 00h =+ IZ/( 1( + I\1h /+ I]\"+ Ia /$ D .& 1f + IV x / Ib,~ ,> ,> ~@ . @@ . 1` + Id ~ c@ + IlO@ X Q" b $+ },> ,>},>}, Is/ IraB 7@ " ,^ ,^ ,~ ,] ,> ,> ,> ,> ,> . J4 z ." . .4 { .6 Z ,> ,> , IS B@ Z /" ,> ` ,> , IS(wQB@ c@H + J. . X@@ [ H 4@JX@@ Z H 4@J Q@@ b@H + J
@@X + J.R`|[ P `J3,~ `J3. P ,@}, P X@}Z`}\,>J4c"|,> ,>J5&"{,> ^"|,> ,>J5,>J5, ^./ J6`B !~aB 5RJ*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$| A Ci 8 ,> ,> ,> . Ib }Z@ K 1` + J@,> ,> , KaB + Jw6@+ JS/ K + J9,>} ,> , KaB + Jw/ K x 4@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 x 0$ 0d + J| @ $ . / @@ ,> ,> , K`B + Jx/ K + J}/ K .2 1r + Jp 3@x + J} " I+ J} " / Ib,^ ,^ ,^ ,~ <H 0 Z > + K^ & Q& \ bK+@ + K+ K> + K ^ ( Q( d bK+@ 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 + L0B R`@ / Kh[@ 4BKw,> , _KaB + L0B Z`@ / KhZ@ 4BK|,> , _KaB + L0B R`@ / KhZ@ 4BL ,> , _KaB + L0B R`@ / KhZ@ 4BL,> , _K`B + L/ Kh+ L0B R`@ / 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 .TMP DSK: TTY: ,> ,> ,> ,> ,> ,> ,> . Mf H .0 [ @ @x .8 .6 .4 .2 ^ 1@ + L3 @ @P 1+ M@@H Z X 4@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 "+ MZ N5@Lx Mb`Mb WX@N X @OZ `4@M ! b@@ + L{Z N4@L~! c@@ + M c@M+ M ,>Mn `+ M c@M+ M Q @P @H . Mo+ M[Z N5@M,>Mn,>Mo+ M,>Mn N,> },> ,>Mh,>Mh, W Z M5@M Mc`Mc VX@M V @M<Md`\ + MZ M4@Ma\ + M c@J+ MZ _4@MZ M0@ + M,>Mn ^+ M b@J+ M ,>Mn L,> {,> ,>Mh,>Mh, W / MnZ N5@M" Md`Me WX@N X @OZ N4@M'a\ + M) " @cBJ+ M)Z`4BM)0@ + M),>Mn `+ M*,>Mn N,> {,> ,>Mh,>Mh, W Z M5@M1 Me`Mf VX@M V @MZ M4@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&@ SJQH 8 3 @ Cj 0 E X Ck Cl Cm ( P x Cn Co [}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 `R 7z {4BN+,>N9,> ,>~,> , / N: c@z+ N- Vx , _K/ N5 / N5,^ ,^ ,^ ,^ ,^ ,~ @
@
@ @ @ @ @ A Cp Cs . 8 @ &" &" NkdNl@
j .( 1h + N; R` Cp[ dNl $ dNm D Cq XD CqZ` Cq " ? B Cr " B Cr "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$ * " cB Cp+ Nr $ "m+ N}Z Cp4BNt1b + Nu $ 1+ N},>O,>O,>O,>N8,>N8,>N8,>N8, ^./ N9aB + O Z Cp1B + N $ " D " ,~ $ GD Z Cp." XB Cp CpXD Cq D " GB Cp " GB Cp " ,~ @ Cp Ct01234567890123456789]>) * ,> ,> ,> . 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[Z y4@O3,>Ow x,> z,> ,>N8,>N8,>N8,>N8, YS/ N9aB + O2 {X@H aB + O[Z y. X@y,>N6 x,> ,>Ox w,> y,> ,>N8,>N8, ^.aB + O< x @ Cr Cr3Br+ O@0B + OI G@H Z u4@OK,>Ow u,> w,> ,>N8,>N8,>N8,>N8, YS/ N9aB + OH xQ@H `B + OK "q @@ / Ox+ Of G@H / Ox+ OP0B 3By+ OP "q @@ + Of,>Oy,>Oy,>Oz,>Oy ~,> ,>N8,>N8, ^.aB + OW | @ Cr Cr2Bv+ OZZ Cp. X@ Cp+ O\4BO\ "q+ Oe,>O,>Oy,>Oz,>N8,>N8,>N8,>N8, ^./ N9aB + OgZ Cp0@ + 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 @ Cv p A Cp Cw Cx,>,>, P/ N5aB ,~ " XB Cp " ,~ * * ,> ,> Z Cp@ 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 + P Z Cp1@ + 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 + P2Z Cp1@ + P0 ~ " @ " ]+ PG ~ G@ ~Z Cp. X@@ ,> Cq,>PJ, r( B@ G@ Cp G@ Cp @ Cr/ N5+ P?aB + P< + P> ~ "m @ "q + PG,> CqZ Cp,> , r( B Cq[ CqZ Cp. Q@ CqR` Cp G@ Cp G@ Cp/ N5 " ,^ ,^ ,~ Cp Cy Cz,> ,> ,> ,> @ {"Q@ 1B + PR $ 1B + PR 2 4 %+ P["Q0B 1B _+ 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} @@ `R 7| |4BQ,>Q ,> ,> ,> , / Q / Q ,^ ,^ ,^ ,^ ,~ $$@ 6$@ ,> ,> ,> ,> ,> ,> @ z QW1@ + Q,> , _c`B + Q 0 / QX+ QM/ QX"QW0B 1B ^+ Q+ QZH H + Q'0B _+ Q"ZH ." $QW0D + Q [H / + Q',> [H " ,> , r( / Q+ Q'0B 1B + Q&5BQ&ZH 5BQ&@ + Q' 0 8 "Y+ QM@ 4TQ4 6 5@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`H Z`H 0 `P 7| |4BQS,>QZ,> ,> ,> , / Q ,^ ,^ ,^ ,^ ,^ ,^ ,~ $$H 6$H ~ ,> ,> ,> ,> ,> } * E, ( .2 |[( 4FQs Z
( . 3f + QeZ 5DQf " "-+ RZ
h$ h, 2$ + Qj
+ Q` F Z 2D + Qn[ QD( + Qr. Z
/
XL [
QL QF( " + R / 2$ + Qy." &" $" . b + Qx+ Qy " !=+ R ( .2 R ( ( Z
( . 2D + RZ( . / XD(
+ Q` / XD Z` QB( + Q`,^ ,^ ,^ ,^ ,^ ,~ ( E, [ 4BR Z
Z . 3b + R
5JR " "-,~ 2" + R + R 3d + R " ,~ .3d + R " 1,~ .2D + R Z
. XD [ QD + R "XD QB ZS . 2B + R"ZS Z . XB [ QB + R#QF " ,~ ,> } /" + SN/ R8@ / R8,^ ,~
| !y R error openingR closingS deletingh renamingh backingRup> writingSto readingRfromS auto-opening auto!closing invalidSoperationSon >for,input and4output for+output >to ,> ,> ,> ,> `} <@ |`R + SS4@S S0` + RU,>S, ^/ R8 <"R[1" +
,>S, ^/ R8+ S
,>S, ^+ S
0@ + S
[ @ .< ,>S , ^Zp 4BR| \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{ D C| C} C~ C D D D D D D D D D ( E( 9 p 8 X error 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,^ ,^ ,~ X 0 TTY: ? % -~,> ,> ,> ,> ,> ,> ,> ,> ,> ,> . T3 @@x H B O2`T4+ S| O" `@ 0b + S|R`~~ `T1 `T2 oQ ` @~ BX@Z`! b@ E2+ Su D X@ E-! G@ E1 `T2,>T4,>T5,>T5, B/ T5`B + Su EG+ T" O" 0 + T . w <"S|1" +
} E- @ D
D ` h @
normal completion file was successfully created and openedincomplete amount of data readfirst read on concatenated file was successful first read on a new page was successful end-of-file has been reached invalid memory address memory element not on a fullword boundary invalid argument list invalid concatenated file specification invalid punctuation invalid descriptor invalid device invalid default file specification invalid directory invalid data type invalid record format invalid I/O option invalid length invalid file name invalid new file invalid node invalid file organizationinvalid prompt invalid record invalid requestinvalid related file specification invalid resultant file specification invalid file specification invalid file type invalid file versionI/O channel assignment error file is already closed conflicting options or attributes file is corrupted file already exists file is locked dynamic memory deallocation error dynamic memory allocation error file is currently in use I/O buffering error I/O error required parameter, option or attribute missing network error file cannot be accessed file cannot be backed up all I/O channels are in use file cannot be closed concatenated file specification not allowed file cannot be created file cannot be deleted directory does not exist file does not exist insufficient dynamic memory file cannot be opened file cannot be read file cannot be renamed insufficient space sub-directory does not exist requested function not supported file cannot be written file has not been closed expiration date has not been reached file is not open for input device is not onlinefile has not been opened file is not open for output file is currently open program terminated due to previous errorprivileged operationfile protection denies access message output errorrecord is locked new file cannot be renamed old file cannot be renamed record was truncatedwildcard error invalid account attributeinvalid attribute invalid data disk/tape cannot be read/written free storage chain is invalid invalid protection attribute invalid character pointerinvalid record number invalid size invalid temporary file attribute I/O channel is currently in use host operating system error network node does not exist insufficient stack space unexpected operating system error invalid descriptor class temporary file not permitted foreground jobs not permitted append function not permitted sequenced files not permitted field is misplaced or duplicated invalid syntax invalid IOB XPORT logic error detected program terminated due to program request end of string reached string was truncatednot a temporary string invalid character invalid descriptor class invalid string descriptorinvalid descriptor data type invalid string length invalid maximum string length invalid pattern string invalid string pointer invalid string request invalid source string invalid primary string invalid secondary string invalid target string conflicting string function arguments insufficient space no string specified requested function not supported temporary string not permittednull string not permittedinteger value out of range string is too long XPORT string logic error detected *** invalid XPORT completion code *** @ $" ." DZ 2D5DW [ 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>+ X 0B + WkZ P [ P / Z P / h h" 2` + W` P}+ Wd c@u+ Wb \}+ Wd 2 (1 (9 @+ X, } @x ,>X ,>P Z P ,> , r(/ X= Bx , rfZ P . |X@P + X 0B _+ X Z P . .< . @}[ P ZP / h$ h& 2d + W{ Px },> ,>p ZP ,> , r(/ X= Bx , rfXXP + X ZP 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 + X X2 }XB{/ X@+ X,XXP z@p zX@P / XA/ XAX] c@u+ X,,>P Z P / }/< ,> , r(@ + X*` X 0( 00h =+ X*Y /& Y F . 3`|+ X%/ XAY2 `R 7wYw4BX3,>XB,> ,>~,>t,> ,>t, / XA @ b@u+ X5 Vx , 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 @@X Y}( /" + ~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`T 7y y4BZ!,>Z/,> ,> Z*,> ,> ,>u, / Z* @ b@v+ Z$ Px , K/ Z/ / Z*,^ ,^ ,^ ,^ ,^ ,~ $$}6$} v u 0 A EJ [} EK 8 EL 0123456789abcdefABCDEF ,> ,> ,> ,> ,> ,> . Z. z { y0V + Z9 + Z: zX@ `Zc `Zc Zd @,>Z+,> ~,> ,> ~,> ,>Z,,>Ze, ^.aB + ZE | @@ ZH 5PZJ0@ + ZH (I+ ZI (/ Z- + Z H @@P &" @
+ Z\ 0f + ZP/& + ZR A ' /& O / ( "Zd& P
h6 h, 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 ZH h h" 2` + [% \x ,>` ,>[xZ H ,> ,>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 . @}[H Z H / h" h$ 2b + [6 \x },> ,>@ , rfX\H + [YZ H @~ . 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/ [{\e c@u+ [f,>H ZH /}/2 ,> , r( @ + [d` 0 00` =+ [d /& F .$ 3d|+ [/ [{ 6 `V 7w w4B[m,>[|,> ,>~,>t,> ,>t, / [} @ b@u+ [p Xx , K/ [{ / [w,^ ,^ ,^ ,^ ,^ ,^ ,^ ,~ 6$H $$|6$| 8 } ( | 0 ,> | /" +
z !y 0 comparison>error:\U ,> ,> ,>\#, ^,>}, ^,>|, ^,>}, ^,>\#,>\$,>\$,>\$,>\%,>\%,>\&,>w,>\&,>v~<|, S[/ \& |,^ ,^ ,~ EM8 E( p error>copying ,> ,> ,>\4, ^,>}, ^,>\#,>\$,>\$,>\$,>\%,>\4,>\&,>x,>\&,>w^<|, S[/ \5 |,^ ,^ ,~ EN E( ` error>appending `to ,> ,> ,>\E, ^,>}, ^,>\F, ^,>}, ^,>\#,>\$,>\$,>\$,>\%,>\F,>\&,>w,>\&,>v`<|, S[/ \& |,^ ,^ ,~ EO EP E(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 @x O 2@x + ]K P + ]{R`~ `^ `^
@@,>^
~,> ,>^
,>^J/ ^`B + ]U E++ ^R`H `^
^`^ @@H 6@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~ Bx ZX ,> , r(^B}/ ^ . 3` + ]r 8 "x @ + ] . ,>w, K/ ^. 3` + ]}`X + ^! B@H XH / ^ ,^ ,^ ,^ ,^ ,^ ,^ ,^ ,^ ,^ ,~ $$~6$~$$H 6$H 0 ,>^,>,>^,>^,>^, Ze/ ^,~ ` E( ( ,>^,>,>^,>^,>^, W / ^,~ E(' [invalid string] ,>, @c/ ^,aB + ^(,>^,>^,,>^-,>^,>^, W ,>^,>|,>^-,>^,>^, W ,>^,>^,,>^-,>^,>^, W / ^-+ ^+,>^,>^.,>^-,>^,>^, W / ^,~ EW E( P EX,> ,> ,> ,> ,> ,> ,> . F@ u,> , c`B + ^7~ (% @ + ^< 3 c@t+ ^=vC0@ 1@ + ^=~ (% @ 6 (. >F+ >0u,> , c`B + ^As (+ T Z @ @}6@}+ ^E F ( @~6 (I+ ^0 u4R^X Rx , ^caB + ^ 2T + ^N c@s+ ^L{ c@s+ ^N (1 @~ 6 (5+ 0 b@s+ ^X C0@ ^+ ^S (% @~ 6 (E+ 0`@C1@ + ^V1@ 3R + ^X b (1 @~ 6 (+ 0Q ." c@s+ ^bZ P [P / ZP D / @},>},>~, r( / G+ ^eZ P @ @} }.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," (,~ 5B p"`0B 1B ^+ do+ p, ,~ ," (,> @ {,> , c`B + `
,> (), . `5+ `',{,> , c`B + ` " (-b + `'O 2B{+ `ZH Z@ 2B + `ZH ,> ,>H Z@ ,> ,>@ ,>y, r} / `6+ `' .$ ." ZH Z@ 2& + `ZH ,> ,> ZH ,> ,> ,>`6, r}/ `65b`&+ `%Z@ ,> ,> Z@ ,> ,> ,>`6, r}/ `65"`&O + `'Z a@ 5@`(7|,|4B`.,>`7,> ,> ,>`7,> ,>x, / `8Z" @ bBz+ `2+Rx , K,>{, K/ `5/ `8, ,^ ,^ ,^ ,^ ,~ ( EY 0 ,equalto ,> ,> ,> ,> ,> @ {,> , ac`B + `A,4 (), . `v+ `P {,> , @c`B + `E 4 (-, + `PO 2@{+ `IZ H Z@ 2@ + `PZ H ,> ,>H Z @ ,> ,>@ ,>y, r}@ 5B`Neq / ``+ `P@ aT 5T`R7{ |4B`W,>``,> ,> ,>`a,> ,>x, / `a, @ b@y+ `[ Rx , K,>z, K/ `{/ `bZ ,^ ,^ ,^ ,^ ,^ ,~ ( EZ 0 4greater than ,> ,> ,> ,> @ 7{,> , ac`B + `k,> (), . a+ a,{,> , ac`B + `o+ (- . a+ aO 2B{+ `sZH Z@ 2B + `wZH ,> ,>H Z@ ,> ,>@ ,>y+ `~ .$ ." ZH Z@ 2& + a ZH ,> ,> ZH ,> ,> ,>a, r}@ 4ba+ aZ@ ,> ,> Z@ ,> ,> ,>a, r}@ 4"a $ a@ 5@a7y z4Ba
, qM[F EjZ` ,> , qM7@ & F Eh4FbS X( E~[ 0f & *(E~, qM[F EkZF Ek, qM F El^0O@ G
b
+ B E^0J + b: G#O@ G#O@ EyO@ Ex " 7@ E~1J B FU,^ , o9O@ Em b
, b%QB Eh Q ( B Eg\" , b 7 + b!@b !$Lu
+ b! E^!$YR ( h m@ + b!"m$"j0(D~A$ p A& G , q& B Ej6@ E~, d-7@ G#+ b)!"K8 B E~, d-+ b@ ( &" .$ )D}=hb&[ ,~ 7@ E^+ b@
0
6 + b@O@ , jL4pb-4Nb,4Nb@1P 8Jb, m7 , im+ b74pb@1P + b4
6 m0, jh+ b1O@ G(Z E^^0 P Em+ b: E^, im+ b@O@ G%0P , k+!$ cD ElO@ G#7` @@ EnZ E^Z"/ ,~
6 m0, jh5pb>O mP Em,~ , l`Jx dD GEe, qM[F EeZF Ef, qM[F EcZF Ef, qMZF EgZ^ 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, Ef4pc O@ G)"m5Bc!$}[bpd 0F@ *dbm
bp+ 0 ebt@mbv@}bvA %bvA =bvA -bv d " bB Ef6 G'+ c+ bw:@ G'+ c " bB Ef+ b Fe`b ! + d7` Fm6` Fm+ d7` Fn6` Fn+ d7` Fl6` Fl+ d, Ee+ c
4Jc
EfaB aB + c7 G'+ dO@ G): G' " bB Ef+ c FebBm+ dL Fo7@ 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&/&( dF EbZJ Ea[ .&( GF Ea, qMkF Ei El, l`2^ G Em5pd, d<:@ G
?@ G
+ c @ Ei, c.+ c 1P + c&1P , d&4pc + d, qd,> G*@@ G*,> En,> En@@ En@@ En,> EmZ^ Em,> G
G
Eo@@ Eo, cq+ ca J G
L Eo, qM5Fc?\& f + cbafp + cb6@ E~+ cb F Ei7 G*, eO m*" Ff@@ Fg m*" FpO@ Fl m*" Fo, d', ds7@ G
+ c[:@ G
> G
* 80c[Op Em@@ En, jL Ei`bp + m h"*bcN2N*bcN5"cT7@ G
1P + cQ+ cV6@ G
0P + cT, jL3N G
+ cV4pcI, j|+ cTO@ 4pcI0P 1P 0 0P + d, eX+ cV Em+ cV5Jca G
6 x 4Nca m
, luaB + c`, , p4, p-, h g^NHtS:O @@ G+@@ G*6x D G .Dx 7` @@ El^ En6@ El7` 7 +cz6` D El2PmOp Em4Bd [ , qM F E^.& Q& F E, qM[ 7@ 7m
Q( H E`Z 7@ 7m
Q( H E`, qMZ 7@ 7m
Q( \H E, qM2Fm F Eb7` Em@@ En@@ FqO@ G
, qk6 G*, eO7 G*, eS@@ Fp@@ G , qn,~ ^0 P Em7@ Eh7@ E~+ ln, l-,~
&m
2 b + d-"l>KNmm-"l>M6}m-"l>M6Mm7m m ,> d, lu ,^ aD + lS, pC , o{6@ G 7@ G+ d% "m!, pC G7$ G " G, " , pL+ lS, dX5"d8 " 7@ E~ B FU7@ E~ P FU7 \06@ FR, l- " E~ $ , e%7B F U"8v B F 7@ EO@ E7B ES Eh B E7B E~+ d8 b `b O@ FT? FU+ d:\" 4pd77 G*+ d81P + k. . E~Od G%-"lKUMm# . E~Od G%-"lKi6Mm&, l`7B Eo,~ 1B + m(, qU4"ln
8 + ," Eou$ Ey & E{, l=+ dV, l-; E{KB E}o Ez!" bB Eq!$>9 D E{7" Ex " 1b (B B E~S EyX" 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 + e 1P + e6` Fq0P 7 + e
6@ Fp7F G*7 + dk1P + dz1P + dZ7@ Fc, h,& fm0 Fp,~ @@ Fc+m1*$ FpO@ Fl+m*$ Fo6@ Ed6@ 7 , Ed!" GB FeGB Fe,~ , eX+ g}, j^7 + d5"e$`b + e%7@ Fp: Fp+ e%L G 4Ngm5Bgl6@ Fc+ gn,N Fc!" BB Fe+ dZ, iH, j 6@ Fd+ goY G 5N Fd+ e$6@ Fq+ h : Fq, h<6@ Fp7 G* &e,, 0d
}m7,> 7 Fq, eO,^ ,~ F Fed& D GF E Fed& GF F(w0h F( "` S` F 3Fm FX!" BB FXBB FX,~ , q], jL4Nqj: Fp: x , f#7 + ec5bg|h.k``n`+ m;h.k`,> (N , f#+ m<,^ !" 0 cC0 + g{Q,@@ G& Fp1b + eiZ0 0" Fc0b Fo7 + ei2" Ea2b Ea+ g{ 0 Z `d aN7 8 `d Q. N G@@ G m>*" G 0 `d + m>4,f`d Q" 6@ G&+ f1P + e|6 G*+ ey4pey Fp0F + ey0P , k++ e|`d @ + hab5Bf 5"fw4Nh+ f 4Bh7 G*+ f , jh, k+* 0H + f@@ ElO@ G&5bf , jL4Nf 0 , im+ f/0 . + f 5"h " )B !( cI0 + f3Nm@+ m@3NmA+ mB0B W+ f,> 0 , im+ f,^ /0 \. + f 4Nf 1P + f7 G*0P + f , jL mC, im+ g~ . /.f A. + f ,^ 2NmC5Ng . !$ bE0 !. 0 h"`ib`5Bf + fw, + fw+ g# " ]< s 0 8 * E^, im+ mD , E
4"f* mE, im+ mF6 5Jf,
,l~ * %0 * /* + qi " ,~ O@ ,~ , j"+ fq, j0+ fq, j+ fq mH*" F~, dX 0 6@ Eg1Ll~7 + mIZ [0 6 G*7@ + f96@ Ei+ f:+ h, e% mL*" Fp+ qi, j6 Fn3N Fn+ f>6 G*+ mL N Fn Fp7 G*0H + fA N Fa0P + qi, j3. Fn+ h
,~ 0 7@ 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[0 6D 0 `d `d + fw4Bfw4.h2n + h,~ 0 0 P
`j ( + m\d,6@ Eg1Ll~+ f|+ mbad`l$ (mdg 1( : 0h d&`af `l& " 3N + g6 G*3Bmg#n O@ 1( b + Fp7P G*0H + g#d$0$ Fc0d Fo+ g/$ 0 P EmR0 > Fp,~ C
,kyCNMhrE5|RIv::KJu{RKK+zKK \KO%0KbN@ "-L Yt}[ 83]>~i7j6m:7 Fm Fm Fl
Fe> Fe2 Fe0 Fe Fo Eo}f\ Fn G+ G
> Fe2 Fe0 Fe G
Fe@ Fe $ Fe Eo Ex Ey Fl4 Fe Fo h" h" h"Eg` j fDugd f;Egf A I a A I $A *U0 0A "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
-"lAC n5"h -"lAkO5n-"lACO5nn0 -"lAk n6@ Ei+ g#F0 -"lAINMnF0 -"lA]6,~ 6B Fc B FV6B FcB FV Fd6@ D FW6B FdB FW n1!" bB Fe*$ FP Fe FeBD FXGB FXGD FX!$| Fl2BmB G$+B G$O@ G4n1*" G, q#*B G 00 0p + h3+ hR, jL4Ni3+iB, im+ i1.. /.i40. + hA7B G$+ i,=B G$[ G &$ / 7 .. R G 6 G$m/. S . ,> , iZx ,^ P + i
, i G$+@%n?+ i
7` G$? 8G: 8G, i "of B G 2.n@+ j@-"l>I?nA G$" . G$" . G$" t G$$ . G$$ . G$$ . G$$ . G/n9+ q&0P ,~ , j"4.i+0.
+ i- N G0P + i#, j"0. + i-4.i+ N G0P + i#, j"0. + i-4.i+ N G7" G " $" 6 G. G$" 6 G. G $ )w'"Q@ + qi-"l>]%nC-"l>]C nG-"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 [H UVtP UVg CV>\zgI6_%xR]?4[1I [1s I9i>$ i>m|YY>=@]>}` [&%j3YVt: I&ui9%i7~-i4, jc@n G'0P + iFl+ iJO@ 00 + iL+ iO, jc@n G'0P + iLS. $ , jcO@ G'+ ikO@ 0P + iYO@ G', jc0P + iR(D (N l + iN00 0p + iV($ l (N ..Gh+ iN@@ G&, j96@ O@ G'O@ )D + ik "p4 B G " ng nh, jf, jd6@ Eo+ ib0P + i``fp B + ib, j^+ if`fp ` /0 `hp P .0 , jcO@ G'+ i]0P + ik/0 `hp P , jcO@ G'afp + ikB + ii7@ G' $ D G + j@ + q>, jc, jf@n 00 0p + it`n p + j
(N pnh, jc+ ip, j^+ i|00 0p 1 + j
, jd0$G`4Bni$"
bni, jc0P + j@ , jc, j^+ nk00 0p + j
$Gh(B . `b+ j
X + i}0P + j, jc, jd00 0p + j
pnm, jc,"p6B G + j@-"l>mnn@ G `n,~ 7@ G'O@ S U @B G ,~ , jc, j7@ (N 6"p$+B G + j@, jc2" 1P ," 1P , jc . 00 00 + j$. ..Gh, jc+ j"p&,B G 1P ((N 1P %(N 1P !(N 0P !1P ++ j 0P (1P %7jug , jc+ j@, jc1P + j0, jA1P + j600 0p + j)$. ..Gh, jc+ j%1P , jc0"p;,B G 0" 1P %:" t1P &,ns1P #,ns$ 0b , jc+ j?, jc, jA,> 7* 00 0p + j7(N ..Gh$* .*Gh, jc+ j21P 1 ,^ 1P + j)0"p;+B G /" 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@@ En6B En+ 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\P En_` + k-"k6@ El+ k+k B En P Em,^ ,~ 6@ El+ o , k67` Eo+ k"4pk!2P Eo+ , k63P Eo+ 4pk!, k+ 0 @@ Eo4p 1P + 1P + 0P 1P + k*6 G(+ 7 G*0P 7 + o0P + , k65pk*+ P El5Pqj 0 * El,~ 6@ G*+ k27 + k16@ G#,~ 6@ E~+ o6@ Ek+ Ek
8 + 7 "
" ,~ , k91P 6` Eo7 @0 ,~ , kE40qj4Pk90P 1P ?+ k91P m,~ 6@ Ej+ Ej
( 1P 0 0P 1P 0 7@ G(6@ G#6` G%,~ 0P ap + kW\` FT, qk " E~ $ F & F , l=+ l; " B F " FR B F F Q X$ F
4Bk`ab*$ F $ F
ab D F , qn, ky+ kx60 FRap` 6@ G)+ kk, kk80kx,> FS1" + kh FRaB + o " , kk80kx=bki,^ >` FS+ ku7@ FR+ kx: FT 0G4Pkq, ky+ kx70 FT+ kx0p @ @ + ks
` + kx FS P FS FR00 0p + o@@ G),~ ,^ ^0,~ , qk7` G#+ l o
S F
o
b + l $" B FS o B FR+ l
F+ l!0 F +B F ,$ d ad ig $ @F + l F (BrQ" E^7D F ad ( h ( $ 5Hl,> ( " F B (
6` FT+ l!( bH F ed+ l5Dl[ F
0D8vg $;2SD F
+ ld$6@ Ei, l*7 + l 6` G#, l*+ l @@ G#@@ G#> (+ l . E~O@ G%-"lKSeo ^0, qn,~ [ F0BK8+ l(QB F
"LuQB F[ F
7@ Z EhP Eh B F
@@ F Z` FT+ k{ . E~Od G%-"lKS}o0D 1D
+ qi<dqi9qj7@ E~,~ 6@ FR7` G#+ l7O@ G#7@ FR+ l4, ky+ l7@b @f + + l7 oS F
o
b + @@ E~@@ G% FU@@ FU@@ FR+o*" FT,~ 7. E~Od G%-"lKS^Mo ( G + p`7 Z ,> , lu+ lS7 Z (p4+ lG7 Z (p;+ lG7 Z (p;,> , luaB + lS, pK , + lS7 Z ,> Q , luaB + lS, pK4.lR[ , p;, pKZ , oB6@ G%, l7^"7` G*7@ E~7 B Em, p-, p- Em7@ Ei@@ Eo G
2 7@ G#7 G(^0+ li,>
6 6@ FR5po2Pm^0@@ El@@ En@@ En@@ Eo2Pm^0 P Em,^ ,~ , 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^ , eVp gR- um, d5pb`+ bS6
Fe l0FopFc\<hFclpFgm@Fl2B + cT+ cONo option ]>um
m ?
?SCNPDL PDL phase error
Equalasignamissing File switchesiillegal in outputffile Outputoswitch illegalniniinputcfile Excess@argumentsustartingewithl" Kb e25m*Wildcard illegal in /RUN specification l0Fc N Ff B Ff+ e kFf/BEFORE and /SINCE don't overlap /ABEFORE and /ASINCE don't overlap kpFj`FVh.k`+ g{,^ 5bg|+ g{qhG[ .8 + f]>tP !.+ f C2` .+ f Uf 4"f&O@ + f&~-g*5bqj4*f,4Jf- + f*l0Fq 0 `f + f5, Eg+ f:+ f5nFc6@ Ei+ fA+ h Can't write tmpfile Incorrect tmpfile argument format % I can't help you, please read the manual Switches are: Standard ones:
Z anen 1B+ fz4Bfz0" + h " (B?X + fz`j + f|, Eg+ g#+ f|0 [ 0BaB8 + gZ `nh`B8 + g+ g, jh0P , k++ ei Double file name illegal Device wildcard illegal Null device illegal Double device illegal Double extension illegal Comma required in directory Double directory illegal Right bracket required in directory Improper project number Improper programmer number SFD depth greater than Null SFD illegal Unknown switch Ambiguous switch No switch specified Unknown switch value Ambiguous switch value Unknown default for switch Double switch illegal No modifier allowed on switch Switch value too large Switch value negative Switch value required on Length values inconsistent; specify min:max Parenthesis nesting too deep Unmatched open parenthesis l`FYq`GR G X. + h>R G + hOMnemonic date/time switch not implemented %x : D (afQ + i3" G + 2b G _X Date/time out of range Date/time must be in the future Date/time must be in the past Negative number in date/time Not known whether past or future in date/time Field too large in date/time Field zero in date/time Unrecognized month in date/time Illegal year format in date/time Unrecognized name in date/time Missing day in date/time Value missing in date/time H H 0
$ " dni, jc+ it0P + j
, jc+ jB
Illegal character or field too large in /VERSION B n5J H G G H G G Unknown guide word Ambiguous guide word Incorrectly formatted guide word El@@ El1P 0 + k El@@ El1P ^0+ k ^0+ 7@ FT,~ Z" + k2@@ En+ kA,^ > ,~ 6@ O@ G),~ x FH FIndirect file LOOKUP error Can't OPEN indirect device j FRWildcard illegal in indirect specification , j|+ lg
.KJOB
. & ,> ,> ,> [ A" ?1B 6@ G++ o#
8 +5 O@ G+, p-, pL, o1 ,^ abS` `H , p4,^ `FaH @+ o-g" , pLZ , p; " , pL, pKZx `H , pC,^ A( X ,~ \" b " ab `l" `fo9(B}D G+[` G G+d"`B l 7@ 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 & " )B 5Boc=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,^ Z 7p` & 5"p> " , pL & #` QDx 6@ , p>[x ." 0b ." + pLQ"A`aB,~ ,> x 4Bp/, pL+ pE " + pL " + pL " + pL " + pL " aB ?,~ 6@ G,+ G,
" ,~ , p0+ o?[ 1D 7@ ,~ + oO, p4+ oU , oZ+ oU-Jan -Feb -Mar -Apr -May -Jun -Jul -Aug -Sep -Oct -Nov -Dec mn@0$ $ B
? X , p4+ p3 , q`7N !.Lu N
!,>9 l aLd* @
q
`j @ l
+@ , `j @ !, an + pk`J l
.q
nq 6N L 5Nqj+ LN 6N h`N,~ aN .q^ N 7@ + q@@ S* X* ** N * !,}X, 7N( + q N0 L( 5Nqj.* *lp} . N [
, !. bN GL [
0j
7.
. (N|0l N 0j
7
. 0l 3Nq7 N + qi n
$ ,> 4"q [ ."~L&":X(D &$:XG& && Z(H(B . $" 2."n `D + q&$ 27@ aD g & /" V$" :5Fq 1( + q > !$z3(q7+ q ." *dq /q6. *x d"%q=) ,^ ,~ q= b " 5Bq6 b d , q[,> &$ :0d ~+ q3&& . q6 * 0& * .$ &$ 0F * .(} $$ 6. ^$m4dq2&$ 2/ 0F 1. 0hO@ ,^ $ )w'q=Q ,~ - < K Z j y ' 6 L\ X 5"qY, q],> , qQ
,^ O@ : `f + qG(F F d A 4Fqi+ qJF 4FqiA 5FqJ : *bqCZ 4Lqi ,~ <$qN7 & : ,~ > F : ,~ " !$p bF G (D}5DqR,~ b
"` b + qZ`b ; x O@ ,~ O@ ,~ " ,~ *
x Q*x , qj> + qi*
x Q*x ,> , qj> + qh*
x Q*x ,> ,> , qj> ~+ qh*
x Q*x ,> ,> ,> , qj> ~,^ ,^ ,^ ,^ : x ,~ -j( ,> ,> ,> *~,> ~,~ ,^ ,^ ,^ ,^ *x ,~ p ,> ,> ,> ,> ( QDx @ ,> ,> ,> ,> 7r !&>9Z(
+ q!$ @f @ e$+ r0D 1D
+ q0d + r l$ + 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$ ``d l$ @`d
&r#`d
& ad @+ r
&
&r$
&r'" / r',^ ZB ([ b + ,^ ,^ ,^ ,~ Q3 qw qx qx r
,>, r9/ r-.$r-,> ,> , rC/ r.,~ 0 ,>~,>, r@/ r3.,>,> , rC/ r3,~ ,>, r9/ r9,> ,>~, r9/ r9/x / r9,~ (r? $ & Z$ $r?/$ & / < ,~ 0<Z $ &$ < ,~ @ hrK $ & ,> &x X 8 $ & / frK/ rL,~ 0 < 7d~+ rP 3H+ rQ=drN@ ,~ ,> ,> . re7@}+ ra
|/
}7 + rb } B | Bx x 2B+ r^,>},>,>|,>|,>re, r}/ rf4Br`<,rb Bx + rX x + rc |+ rc@ / re,^ ,^ ,~ ( ~ + ri H =$rh,~ ~ + rmF =$rl,~ ,> .$Q.r| &,> ~ 4hrz
2j
/
+ rw F =*rv.r|*drr4hrz x F =hry/ r|,^ ,~ ,> . s |2D}+ s4ds | B } Bx
x 2H + s=ds@ + s }
3,
4ls | B } Bx ~
> >
x 2H + s=ls
@ + sO h( h* 2( " / s,^ ,~