IMD 1.18: 11/11/2012 20:57:08 UNISYS STANDARD SOFTWARE SYSTEM UTILITIES PACKAGE 12.00.00 B25-STU 8 of 13  |l 03433-8/13 l l%$9|M^Standard Software 12.0.02am  f "mfd.syssys*XlllrY  Execw( 0statuscodesmsg.binExec0wLlllk $ mJy%ث\hYwA8yï   = V pbҵp(_> ŷк^D" 6!,"(#($%s&,'()*+fi,-:d.w/ 2V3It45Jp6X7P8 b<k=a>kx?@A<BkT0 CDqEFG PQSRi>STEUV|WX#Y1Zh[|\]^q_)F`|oaIb94czmdCe*f_g!h!i>#j%k'l(m )n>,o -x`-yTQ.z_.{/|\/}Z/~YQ0 00 z2t224=66v7 99 t:  ':(4/)/c*6+&,=-(+./S//0"1c2T6 3X 4? 5>! 6*_   7 8> 9NP :@ ;H <C& =Ei >9 ?> @,% A3Q B2 C D( E/ F.G,DH'pI-J7K6L31M:dN:O+PQRSTUTV8-W.eX2YAZC[.I\0w]1^6_8`0Fa8vb-c.d efgG h!i!j"k#lI$m%n%o3t&p7&q&r.f's]'t 'uT'v-N(  w.{(x (y(z){K*|+}+~,-!../q00i.1>1234-55667789 :B:C%;D<E ==:==>>6>)S>-|>>>>>? :v:n';0;7;C; ?<H<< 7=,@@ A7A:B QBEZB B BBʦḑ0F,g !*]ET jfU/ 2Z%`  R ճ޳xO.϶ݷ̸¹ c\4 ao]=̾N JW<cݿ)@wi[;y JDSX YZ[=z\?]L^>B_$`oabUc_d\^ef,g'h x.UW AY% ~H*a/ZJD<l `Sd6SkjXs5s6<#r?Dd |[9Dd"E:&w`w|PoC [hepW=  M!"@#I$^%7&k'(G)KU*M+@,<--/i.R/0/1;2 c-]$s~7Hx DbWLDV%{{kGpY"{;@ 1:eokg 2N-1;>l:)9 5F2{+= -!.B"Ip#M$:%-@&m ??@ABCDEFuGoHVI6J eFJ J J =K FK 2L e;L  EL! L# L$ XM% m O& zR' S( T) U* ]V+ ,^, E`- 1bb. c/ d0 }e e 5f g h h ;8i si L|i i i kj tj j k k !k !k "k + l "5l( 7Wl) l* m+ ^n, t_n- 4n. p/ q0 1q1 ,q2 %r3 8r4 r5 kms6 s7 %Xt8 0}t9 nt: zu; +u< /u= Mu> *ov uv 5"w 9Ww  w x x x y ;z z { m.| %| } s} {<~ K~ ^ `! (" -# $ ς% ]& n' O( g) }i* N+ 4, kȆ- i3. / G0 1 {2 3 u4 \'5 6 7 8 u9 a: O; e< = P> ? n@ A B (C kD gE aF ;G KH B?I J K L ˚M N 3[O P   Q VOR S T RU V W ϣX դY ~ܥZ }Z[ ~צ\ U] ֧^ _ H` Щa gb c !d 6e íf wYg Юh _i j k .l m }n o p -q ̴r qs |t su  v w $x 1y Ӻz s{ | 4 ^Ѽ /     f9  y   g  =sH ]I Q J ^K aL ^BM NN X O FP Q onR ZS U7T j  V k U_  C  Y _8 U U ZA _ S ^M  S> =aOPbb\zt tuvwqxNyz{|gj} [ 5>n@{`?QT= _%(m)jB01/ " /<(k,!E%%"J:lG%  1<:=/>?s@D!AeB(CDE^_XYBnu%G\[^ \eu uh Xx`0u>l;~~:nMV(q$$ frm- } X ^] \ m y   ZPNIh yg1nuaAW1mHyLyP{Vo{[  b!!"##.$ $$to%f%I&8''M(zd))& y*u+h+/+--^../}N0|0G1M2 3p3031 O52}X5355}66o87G199x:: ;;;< <=<>T=? =B>E ?F'?H?Id?JuC@KM@L A8AkFAfA]BctB`BW7CcC`CXQDMDQDGGEgEE6 F|BF_FGGKvH HHVIKJ`J5K( <6KrL\&MNOAPP QRT U\UJU;HVOVIVFWHaWKWW XYY*Z Z~ZDl[/[[\]Gn^,  L(MNC\OP j}sV֩wh~9B! # yR2˴жҷr<xq6   _ ` C 0  3D7  I' Hp  k K A V 8 L   m  q  S   *! " .# t.$ i% p & b{' h( HE) * QH+ , Zl cm   '   44!1=5!n6!P7!8!9!O:!%;!!r?![@!A!B!C!D!E!F!mG!YH!^I!QJ!-K!L!cM!h4N!P9 O!l[P!Q!PTR!LS!LT!o<U!V!{W!PKX!nY! Z!/[!N\!k]!z^!]_!*`! a!b!qc!W_`oaEbc)dee4fCfE9g~gshs?iirjklkl,mnaoompqyq_rLrCsEt@t/:u* piuvw6YxxWuy[yR'zWyzSzY#{T|{T{\$|V|Y|Y/}Q}O} (~ 1~ y~ zWNew*΁pgpkqۃmL „TS:eF#uy vK U$,^%&L)*O.8ݑ/E3iZ4 Õ ̕ZՕ/*  - XҞ*ơGפ֥\ަ:&W 7a@4Jխ g(  ]Q}ճRn:<Wϸj&^n̼Xvb5"&>1[Z iv  ~y ~ Muq?3#rEDHWf/  UV q<z[ mv  &/h p {=@0}V z /AQtZM p/Cc^&M^Zt 88BB3du  a8j$Lm}B 1 c" \  & M kF* ` i U EB g`H!@#$%J8'(I*f,./^1=23U3)6 t7!A9"P;#n<$b=%R?&P@''A(B)D*D+6E,F-G.aH/J0J1XK2K3L4M5SN6VN7nTP8 QsQ,3 tRu xSwSxTyTzYU{V|X}*Z~I[a\]^^s_d`=aabcdxeXf"ggShjjtsm8mooKp>r 4t=twuBEv ww .x7x#yzz{|}q~ "E+GpdyV1.Cd[u85 465k[ 56 "7+8 9(:; @ ABC?ŗD<E@Fn G+yH?I]J|@Kl d!e!gf!cZg! h!i! ok!dxl! ! !! !h# !l ! ![ ! ! !w ! # !. ! !B!_! $!1-!3^!3!1! !!!i!!f!"!a ! l!du!w!}P!v! C![L\; !?!!!>" " `"+a"|b"lc"d",e"f"~g"Oh"i"j" k"H!l"L!m"."n""o"P#p"i#q"T$r"t$s"N%t"%u"u&v"&w"'x"y5(y"(z"V){")|"m*}"*~"z+"l+"f,"c -"n-"." /"$/"/"70"0"e1"&2" *4"-75" d6"m6" 6"6"h7"8"9"@*:"<j:":"y8;" ;";h= "r<"="="c>">"y?"9@"@" DB"eMB"C"kOD"D"kE"G"G"?H"0I"AI"^I"+{I"=I"#I"J"hJ" K"3L"q5L"|L">"M"[`M":M"gM"\N" 'O"0O"O"jP"rQ"*vQ" Q"#Q"Q"R"R"xS" 1T":V"5W"W"X"q/X"X"SY"#nY"GY"Y"Z["I\"^B]"t]"#^" 7^"=@^t? "%}^"M^" ^#(^# _#h`#,l`# `#`# a #na #a #Yb #15c#(fc#+d#d# qe#pze#e#"f#f#gOg##h#h#(j#*j#N k#/Zk#+k#(k #Tk!#0s"#pKs##Is$#t%#t&#Qt'#HOu(# u)#6u*#yu+#Ov,#v-#5mw.#Cw/#w0#1x1#y2#z3#v{4#J|5#-}6#V}7#~8#9#:# Z;#ec<#NȀ=#>#?# r@#{A A#Z*B# H#QI#ބJ#K#yL#M#pωN#?O#ΌP#\Q#R#S#a׏T#r8U# [#\#\]#^#ܓ_#Ŕ`#oa#"b#{%c#d#1e# n#Țo#jvp#rq#Rr#Us#5t#5u#bv#Mw#џx#P^y#z# .}#7~#F#1#Q*#I{#ĩ#Ju##HN#X#e#gS#8##z#m#l#kc#Oΰ###'̱##1{C ##GȲ#"#1####*# +#4#t̸#@# й#Lٹ# %#P.#K~# ɺ#Һ##R#Q#88#%p#"#&#Mݼ#*#MG#%##@9#Ay# #~þ#A#Ŀ#E#s#;#v#>## ##T:# $$w{$$xy$f${W $  $D $ $ $v$nZ$$}$z$o$E  $x$$$h@$$>$|$d$v$Bb$a$C $H!$k"$J#$$$%$u&$'$($)$Q*$M+$N`,${-$r).$/$"0$1$2$J3$ 7$(8$9$b:$;$<$v=$Z>$?$@$ZA$ B$C$ %h% %['%%%|%.% %|%L%%%"%%%"%%`% G !%l%d%%&rT& &&&l&&]&`&)= &f &% &4 &9 & '''';'''"'u',''v'6''' $'X %'he&'b''P/('q)'e*'fU+'f,' ! C'G* D'Yq E'E F'U G'Jd H'I I'g J'?^ K'9 L'e M'`;N'JO'4P'XQ'UqR'HS'PT'`^U'LV's W'K}X'uI "Y'~=Z's['P.\'M~]'H^' t'u'Q v'q  (O+HmP+9R+ \+3]+;*^+"e_+&`+-a+1b+ c+%d+G?e+Af+Ag+Ah+=Ii+2j+Ck+l+9m+.Pn+2~o+&p+q+r+fs+/t+u+v+w+Nx+y+z+P{+ |+. }+D;~++R;+ +?+9+$+ 2+*R+-|+N+Z+1Q+2+%+0+* +/3+*b++8+++u+).+W+S+KX )+`+Uf+'+'+% +K.+y++#+"+*+%+C+Q_+Q+I+IJ+#+++#+2+6+R+Gp+"+>+B+FY+G++x+k4+^+n+Ck+n+B+T^+b+d+x++U+ +i+ih+[+,++eo+k+ ?+H+++5+L+ ++z0+q+tw'4x'y'qcz' {'Y|'U:}'~','''n' !'N!'Z"'\"'"'#'5$'%'%'b&'''q'':('U(')')'*'/+'+'b,'\ -'de-'`-'z).'b.'5/':0'Q1'G-2'ut2'h2'>Q3'a3'_3'rO4'I4'E 5'O5'c5'<86'ft6'J6'p$7'7K #'M8'h8'RE9'K9'Z9'<:'t:'l`;'[;''<'{<'+='='>'?'@',A'A'|B'4C'f*D'XD'D'rE'4F'rF')G'G'mH's I'I'OaJ'J'MNK'IK'EK')L'L'WM'M'N'r>O'hO'IP'GaP'P'UsQ'hQ'z0R'wR'^!S'oS'YS'HGT'T'2U'U'OV'KV'b)W'OW'W'y\X'XM $'pY'YZ'ltZ'}[']]')^'^' _<(k_=(N&`>(]t`?(O`@(P aA(fpaB( a(a(^vb(b(c(@d(d(e(f(,g(:h( h(h(i( @j)Ij)>j)uK)uL)KpvM) vT)vU)jwV) xW)xX)DyY)yZ)z[)Q#{\)gt{])F{^) !|O %h)*|i)|j)f}k)}l) ~r)~s)>t)u)v)*w)́x) l)u),)<)u)e) )†))E)%)y>))kd)mϋ)j<))<)܍)yz)))){)9)N)%k)) )K)K)sK)_)Y)Kv)){a)ܗ)_)[) p)y)**5*Zě*J*h** 0*`1*I 2*@RQ &3*s4*+5*&06*LV7*&8*Xȟ9*_ :*;*N<*=**>*b)?*@*YA*dlB*0ТC*3D*K3E*~F*#G*H*5գI*` J*LjK*AL*AM*8N*RO* k*t*J*v٥*3O*\*M*Q+*i|*P*a5*G*@ݨ* *k&**c*M]**z}**n+-+-+++++@+#^+i+F +?0 +o + + +S '+Wy+з+H[+\+N+PM+R+U+MD+L+Tݺ+71+5h+/+U̻+R!+Ts+#Ǽ +#!+F "+S#+o$+X-%+&+'+#S(+"v)+L*+++,+M-+.+4/+0+3_1+42+m3+34+J5+N6+i7+ 38+3S9+S:+;+3<+#)=+YL>+?+@+QA+AB+CC+>D+M]E+?F+?G+5(H+#]I+K+ZL+'M+N+@-U  +S+Z *+ ,\,b,I , ,vi , ,e` ,,CZ, ,Z,,p,,n,l,Bq,,e, ,,D,,rh , ,t  , C .1L .[} . .Wg . .P.k1. |.}.~.. *.B3.u..T.n.K.Y.=D.>..|{..S..C.G".*i..%./.q.Sv.o.S8\ +.b.K.A8 .y . . .!."/r~#/[#/6K$/:$/G$/4%/$6%/9Z%/7% /5% /6% /5& /I& /R'/&g'/%'/,'/'/Kq(/(/)/**/;+/DN+/:+/+/,/Vq- //-!/ -"/4-#/F3.$/ y.4/J.5/<.6/:/7/IB/8/D/9/O/:/]0;/K{0/ Q1?/.Z1@/W1A/\1B/;2C/3>3D/Kq3E/&3F/93G/'4H/#B4I/"e4J/04(^ ,K/?4L/(4M/>5N/ \5/Je5/H5/95/O06/Y6/N6/O&7/Nu7/T7/98/8P8/98/:8/;8/;69/Gq9/e9/O:/?l:/L:/N:/NE;/M;/=;/></=[</-</.</%</4=/5L=/<=/%=/ =/W=/?B>/>/?/=?/F@/D\@/4@/@/4A/MA/2B/LB/B/6C/HC/.!D/2OD/JD/JD/\E/HqE/ E/8E/E/DF4` -/BG/AXG/;G/=G/:H/@KH/8H/?H/+I/2-I/6_I/FI/`I/C;J/W~J/AJ/ K/K/KK/rEL/=L/=L/81M/;iM0oM0ON0dbN03N0cN05\O0 ON0OO0.PP0PQ0?QR0QS0kRT0RU0ySV0TW0TX0zUY0UZ0V[0V\0.W]0(W^0BW_0*X`0xHXa0tXb0y4Yc0sYd0 Ze0Zf08[g0[h0|R\i0{\j0I]k0]l0a^m0^n0_@b .o0w(`p0B`q0L`r08-as0=eat04au02av07bw07?bx0'vby0Ebz0?b{0.!c|0Oc}0Gnc~0)c0Fc0?$d0Pcd0Bd0d0'e0!e0 e0}e0ef0f0g0h0h0|&i0|i0vj0j0k0}k0+l0wl0p%m0 m0>m06m02n0(Dn0&ln0!n0<n0#n05o0:Go03o0 o0>o0$o1?p15^p19p1@p1< q1*Hq1/rq16q1q 1=qLd / 1//r 1%^r 1%r 15r1:r1:s1Qs1 ls1us1+s1Cs11s150t1/et 1<t!1Gt"10u#1)Gu$1(pu%19u&1-u'15u(1&3v)18Yv*19v+1 v1vv1Iw1@w1:!x19[y10y1y1tz1 {1${1r{1r?|1r|1 #}1',}1&S}1y}1~1-~1~11d1 1L1P1HK1B1=Ղ1P1Rb1O1S1GV1A1ބ11NJ1(Xf 01$1.1@1QR1}1T 16t11o151 K2T2=2Q2 2Ō2 2d22 2 2\ 27 2*= 2Wg22\2A2;2:20V262M2S 2\22h2h2gw2ޗ2n22 2Z!2("2|#2Gt$2 22ğ32y42.523-62+`72827:92q:2 %d2`.e2Mf2Lۣg2;'h2Kbi2Xj2ldh 1k2ql2Sm2RPn2Go2?p2 (24127e212.ͧ2;2462:j2H2"3 3~3 33}/4_4 44M4 &4c'4 QY4ZZ4[4x\4#]4^47_4b`4a4 b4jc4d4 Ȳe4TѲf4]%g4 l4m4n4eo4 p4q4r4 p4y  F|SF}TF(}UF$G}VFk}WF}XF}YF}ZF!}[F }\F3~]F-L~^Fy~KG0~LG ~MG'~NG$OG$EH%4FH)YGH?I@I.v 8AI!8J9J-:J*FJB̀?J;@J-IAJ7vBJ1CJ;ށDJAEJ}ZFJ-ׂGJ(HJ0,IJM\JJ3KJ&܃LJ.MJ+0NJ'[OJ'PJ'QJ'ЄRJ'SJVJޅWJ҆XJPYJ%>ZJBc[Jr\Ja]J2xtJuJ}vJwwJ0xJ@OyJ2zJ JʌJ?cJ)J-ˏJJJ JXJSJS;J4JT–JSJ<iJ;JCJ9#J1\J<JQɠJAx 9JV[JUJ]J8cJ(J)çJJGJPJ1XJ@J3ɬJHJ^DJJA=JE~JîJ1߮JGJ@WJ>J?կJ J#J)@J7iJ KFK1KB K bdKkeK9TfKK#K@Kk4}4i4 i4r4 (414ܺ4K44k4 4<48W4_pj 244FĿ4 4(4O4J 4V4k4 f49o4 434 44 t4a}4 4\4 C4QL4 4T4 4/4 24;4V4;4C4Y4s4 44 %4.4>44O 4vY444N5e5555|K5H5)5C85{ 5V% 5.{55I`5 5S5o5t55,5 5 L6m|l 3M6pN6~O67uP6Q6R6S6|T69U64V6W6]X6Y6Z616ZA6D66}66}66I66 }666I6966gh6K66866c6{{666yw6 7i7 b7k7 C7 L7FY727 (7)7.*7?+7 ,7-7 K<7T=7>7 ?7F@77A7|KB7 P7MQ78R79Un 4S7 d7e7 f7B g7 x7 y7N z7 7s 7 i 7 r 7  7 7@ 7 7 7l77^7 777>767y97 : :}: A;J;;;P;5; ;!;";FL#;F#; #;N#;/%;%; &;&;C';$(; ););n);g+; F,;O,;=-;-; .;7.; /;/;0;1;2;X!3;y4p 5; 5;5;@5; :6(<C6)==@>=>=?=1@=*A= ?B=(HB= pB= yB= B>B> C=>;C>>?C@>*8DA>0bDB>6DC>BDD> E>"E>F>F>&F>#H>BH>XH>lH>I>,>I>=jI><I>I>=I>E8J>3}J>J>J>&J>5 K>5>K>sK>*K><K>K> L>3M>N>Qr 6>R>jS>)GT>pU>+nV>V>W>X>Y>2n[>'[>,\>+]>M_>k_>}_?+q`?2`?2`?#a?#a?36a?/ia?;a?a?[b?%b?$c?,c?Hc?dc?Nc?c@ad@e@|ehBseiBeqfjBfkBXglBgmB*hnB--hB=ZhBEhBVhB2iB"iBi0Ci1CCj2CUj3CSj4CX7k5CYk6C\k7CVDl8C\l9CWl:CMmnxDpxDPyDly$E|y%E2z&E3{'E_{E$6|E?Z|E|PF1|QF|R KZK+K((K PKYK&;K#aKK KK YLZL3ݹ[L<\LL]L ^L)2_L2[`L6aL*ûbL,cLdL3eL#NfLqgL(z :hL(iL߼jLkLlL#mL <rL%EsLjtL$juLvLfwL>xLyL'zLy{L L&L'L)L'L 'L'0L WLwLLL LL>sL L8LL5L=-L@jL/LIL"L(;M:cM:M$ M M M 6#M?$M2%M3&M9K'M5(M8)M7*M8(+M9`,M8-M=.MF/METEMAGMAIMASM+\TM)UM)| ;VM*WM/XM 2dM4;eM4ofM M4M2M M#M>MdMgMzM_M-NM{MOM*WMAM+M&MM2M9QM3M*MM3MI6MGM  N!N"NT#N$N%N =NFNNNNNLNNaN N?N5?N2tNAN*N LOSMOTmNOTOOUPOVjQOZROYSO^sTOVUO'VO?~ <WO[XOW\YOZOV[O\OWs]O^O}_OO`OW aOZbbOWcOdO se?s3@s/)As^XBs Fs?Gs8Hs67Is mPsKwQspRs>2Ss>pTs Zs#[s ds;esI fs)igs&hs*is nsos;psAqsxrs;ss?ts xs3 ys3?zs3r{s`|sg}s@l~s 0uv rv{vLv#v vvvvvSv  =v) v  v v  Px Qxl Rx' Sx  Zx5 [x3P \xK ]x; ^xJ  _x,S `x  x9 x. x  |y }y ~yk yv yp y y{ y y/ yq yj' y yF yH yP\ yN y y y^ y y y[ yX yR y#a y yzn y yi y{H yP y y7 y  y y! y" y0# y# y$ y% y<& y' y( y ) yR)  >y* y+ y, y- y. y/ y0 y1 yi2 y3 y3 y:4 y}4 yC5 y6 y6 y(7 y7 yd8 y8 y9 yy): y: y; y \< y9e< y= y P> y`Y> yI> y>? y @? y4I? yI}? yr? y]8@ y@ yA yxB y\B yKWC yWC ylC yGeD y D DzXD EzE FzsE Gz3F Hz2G IzH JzH KzI9I LzI MzJ Nz.J Oz8K PzO$M Qz sN Rz#}O SzP Tz|Q Uz5R Vz R  ?z*R z/S z9DS z=}S zPS z5 T z-?T zQlT zVT zBU z4UU z)U zZU z= V z3IV z^|V z/V z/ W z 8W zAW z X zj X ztX zY ztY zuZ zqZ z Z zv[ zdw[ zC[ zN\ zKl\ zJ\ z[] zP\] zR] zL] z:J^ z^ zK_ z b_ z\k_ zW_ zu` {?` {` {Sa {Ka {a/b {=b {b {zc {Q[d {Pd {d {e { f p{Df q{Uf {g {h {sj {Bk  @{l {l {m {n {o {p { q {-q {r {t {Dau {u {7v {w {Px {/ y {Oz {Dz {,{ {{ {3| {w} {zp~ {~ { { {9 {> { {r {C[ |x | |+ | | |G |c |D |1 |, | |T | | x ~ ~V ~V ~U6 ~U ~[ ~; ~ + 4  Ȓ ӓ  NA  k    yʗ $ A C c   # ' & s/ 0 $Қ   6, Qb @ # + A V ڜ 9j X !_ "{Z #՟ $I %  M M kA N X DR [ N H? H Q  k r3 \   M 3P A V !Y "Ms # $ % &M 'Tg (T )Q * ` N[j O PpO QM R  S/ T_ U*3 V ] W f Xo Y Za [h \ ] x H^ _B `` a ( vD1 w=u x; y< zB) {#k |= }4 ~1 E0! ,u! B! )!  " z" # # e0$ q$ % % % & !' ' G( =3) op* l+ eK- &. / 0 ;1 Z1 `(3 4 5 5 56 |)7 v7 8 8 9 ¬$: ì]: Ĭ(< ŬF= Ƭ= Ǭo> Ȭ? ɬ7? ʬ>@ ˬB ̬B ͬC άoD Ϭ VE ڬt_E  I۬ F ܬFG ݬ$J ެJ ߬L ଺L PM N uN \O yO O 5O O ߡ &X ' ( )W *ڤ +fk ,}ѥ -N .VΦ /l$ 0 1* 2 3D 4aǩ 5^( 6s 7 F H Q iC n  Є#   J  Q B_ T ˆ 0 B I LR p    # \  f QR   L  -  " # $x0 % , -YE . / o 6y 7 8 9 :( ; < => > J K- L M } | i ol u hP i f d ] h at gU s c/ T AO B!I C-j < CD/ E2 F? G;7 H:r I2 JA K? L2^ M; N OR P1& QBW R. SS TW U\q VZ WJ' Y6q ZI [ ( ) * +5 ,N -&l . / 0 1+ 2+ 3-4 4 a Z#j [# \" ] ^ _ `"& a(H b*p c0 d+ e f g, h; i Q jq k5 l ( )  "9 )[ $ "  $ H D# ## "F "h $ &   *, -V ! #  ' & 7  P àg Ġ Š Ơ( Ǡ( Ƞ' ɠ2 ʠN ˠ^ ̠#w ͠# Π" Ϡ Р! Ѡ Ҡ&, Ӡ>R Ԡ> ՠ# ֠ נ ؠ*) ٠S ڠ2m ۠9 ܠ$ ݠ  ! "@ b   $ 2 " #/ $J %!e & ' (& )% *% T E+&- ,%S -x . / 0 1 2 3) 4(F 5(n 6' 7$ 8$ 9# :#( ;#K <n = >! ?* @$ A$ B: D Y E1y F! G H I# J)' K"P L r T"{ U V W X Y Z% [: \U ]!n ^" _! ` a# b# c"4 d!V ew f   - ' 2) [ *x    7 71 ` Fh  2 7   * F #_       ( 1 Q !m    !  ,# O ̡X ͡#t Ρ ѡ ҡ ӡ ԡ  ` Tv & % 0 )E En [ > @L ^ b QL a I SG \ f h\ Y < hY [ G Uc 9 q l Ggb N L 0c n L [M b r  L| J N ` Rq K N K\  $P )P FP  bP p_kP q,P r5P sW+Q tWQ u2Q v R 8R 9R :\|S ;GS + ?34 @kg Aˡұ Bjs C˶ݲ D˔ E˓' F? G˵ H˜ IUJ Jp Kp LS M~Ҹ N{P O˭˹ P˒x Q R+߻ S˟ T |˸ }lj ~%ֽ ˩ ~ (" ^J e O Je       M 8 M $g % ' ( ) ,# - ] ^. a!C bd e!y f. g& h ii jt n p[ qF r;3 s@n t8 uJ vT0 w 5 6  _ Dr 1 W b> O 7 & [; 2 ] % U: R V 7 qL ^  0 49 1m 0   & 5' )\ * * -  N5 U; : Y U# Yx / F F e $  3 S IU ] ^ Y 1b ] 7 &' M V k ?t 3 3  !" KC s $ G% l + + K I" k =t V  O 6h  4- 5* 6 :+ ;Ј2 <Ю ={h >t ?W @u A B C DА E F4 G7 ̥ OHC I JИ K - + K ). +W ) ) x -L y # ) # U F -O c| ) * (2 'Z ) ( ' ؏ / / #  7 /S  6- 7 ۨ ہj K ? :H k h gU e ! p & P / Qܟ8 Rܟ Svv Te UbQ Vb WR XRg Y^ Ze ا P[F| \E ]L ^KS _H `J aL0 ba| c[ d]8 eF fS gt. h iZ j  oK pSY qL rQ sRI tW uV vKH wX x[ yWF zd {_ |K` }a ~Q O] Z $ X* H H H Fc J H D; G C L  IU F E ) |_2 }ݜ ~- I    | pi ~ rW ݡ Yj  Qi ݉,    General: OK. Successful completion.Gen, Weral: End of file (EOF). An attempt was made to read or write beyond the end of a file.General: End of medium (EOM). An attempt was made to read or write beyond the end of a file or device.General: Inconsistency. The operating system detected an error that was nonrecoverable. Run the crash dump analyzer.General: Operator intervention. The user pressed ACTION-FINISH.General: Syntax error. The user entered invalid data to the application program. Check for the following: - Entries that do not fol8 Xlow appropriate syntax. You may have entered a numeric where the application expected an alphabetic character, or vice versa. - Lines and variable names that have exceeded length restrictions. - Syntax errors, such as a misplaced While or Else, or a procedure that is too nested.General: Server not running. Interstation communication with the server (formerly called master) of the cluster has been interrupted. Notify the system administݶ ݫk ݁  ގ ސ. s 1 f: K J B5 ^w ~ nS  Y@ H ;   e% W   %f & P 'ߊY (ߊ )mm *߄ +z^ ,z - R /Y[ 0U 1o  2Wx 3= 4  5  DI Eu? F  G H  I. J  NQ Os P R So! TB" U ,# ]_5# ^# _Wa$ `ߓ$ a K% chT% d% eD& fߊ&  RgCf' h?' i:' j߮"( k ( lq( m J) nߞS) o ) pP) q.J* r=x* sd* t + @"+ <b+ .+ 4+ M, NM, ?, @, B- @\- U- >- 5/. d. Am. . M. / # / 0/ @9/ y/ U/ :/ 70 H0 ?Q0 k0 (0 A#1 Ad1 E1 ^1 EH2 V2 <2 53 T3 {]3 3 3 V4 5 ߃ 5 ߢ5 .6 G76 E~6 ߅6 H7  S߻Q7 u 8 *8 \9 >: ߟE: : D: 21; c; ?l; K; B; -8< 7e< ]< 0< ')= 8P= \= 7= x> .> 4> D> 09? "i? 4? 2? 1? 3"@ .U@ @ aA dhA cA c/B ! B 8B 98D :E ;eF < H =yI >*J ?FL @M A|eN BcO CcDQ DR EET FU GkW HX IY Jo [ K\ L]^ MW` Nsa O+b Pb Qc  TR Oe kXe !te "E7f #I|f $Sf %g &Qh 'QWh (qh )Si *li +uj ,g{j -j 3zxk 4 k >Am ?Sq @cq ASr Br bs c`wt drt eIu fu gVv hjw iqw jIw k<=x llyx m`x nKEy o^y pSy qmAz ruz sk#{ tm{ uo{ voj| ws| xL} y} zT~ {~ | }lm ~jـ NC  E{ &    3    Ui  t  FB GUB K L M# N" O  P$ Q? R!] S+~ T# UȖ Z+! [UL ] ^U _& `#8 *[ 5 ! *ۓ 1 #6 )Y - ! "Д   ( > U l u  !Е   !* -K 'x ) Ȗ ! + , %J o %  җ  % )/ $X | '  VBØ 0 :5 o # 0 . ! 2/ $a  ( "ƚ  & +' R !r $ g h iyd jvݝ kuS lȞ msY n̠ o\T p\ q r| s}3 t uD v_S wZ xW yZc zI {G |HM }U ~ ? m0 W @Ъ   B Z MN L Mz% Nd Oh rator.General: Not implemented. The procedures necessary to impleD Yment this operation were excluded at system or application build. For example, an attempt was made to use a bytestream not included in the SAMgen. This status code is also returned by the operations ReadBSRecord, WriteBSRecord, ReadByte, and WriteByte if an illegal mode is specified. Draw: No such object. Cannot build the object. Delete the ? representing the template or make a new template.General: An internal inconsistent state was discovered. This is an internal error that indicates a problem iP Zn the software you are using. Draw: This file was modified on a different type of graphics workstation. You attempted to recover a crashed file on a workstation different from the type it was modified on. You must recover the drawing file on the same type of workstation.Reserved.Kernel: Exchange out of range.Kernel: Invalid pointer.Kernel: No link block. Generated by PSend. To specify more blocks at system build, increase nMsgWait. Refer to your Procedural Interface Reference Manual.Kernel: Inv\ [alid interrupt vector. Generated by SetIntHandler. (Refer to the information on Interrupt Handlers in your CTOS Operating Concepts Manual.)Kernel: No message available.Kernel: No link block available. Generated by Send and Request. To specify more link blocks at system build, increase nMsgWait. Refer to your Procedural Interface Reference Manual.Kernel: Inconsistent request block. Information provided in request block does not agree with expected values.Kernel: Mismatched response.Kernel: No proceh \ss control block (PCB) available. Create fewer processes or specify more PCBs at system build.Kernel: Programmable interval timer (PIT) chain invalid. Possible causes of this problem are: - A PIT block that was established by SetTimerInt was erroneously modified. (Refer to Timer Management, status codes 420-429.) - An attempt to reset the timer was made after the interrupt occurred.Kernel: Invalid response exchange specified in request block.Kernel: Memory protect fault. The seventh and eighth wordt ]s are Code Segment (CS) and Instruction Pointer (IP) when the memory protection fault interrupt is detected. (Refer to the Fatal-Error Message explanation in the Troubleshooting chapter for the interpretation of operating system crash status words.) The error condition causes termination of the operating system and an automatic reload. Shared resource processor: Memory reference fault. A processor tried to write to its own memory. System crash status word 3 is the nonmaskable interrupt (NMI) status co ^de. Status word 4 is the high 2 bits of the memory address at the time of the NMI. On a shared resource processor, configuration parameters and the keyswitch position may avoid operating system termination.Kernel: Bus timeout. The fifth status word contains the lower 16 bits (NMI port 0) of the error address. The sixth status word contains NMI Register 1; the meaning depends on the processor type. The error condition causes termination of the operating system and an automatic reload on a workstation.  _ The contents of NMI Register contains the following information (bit 0 indicates the least significant bit: - bits 0-3: address bits 16-19 - bits 4-7: B26: error latches B28/B38/B39: Memory address bits 20-23 - bits 8-11: B26: unused B28/B38: error latches B39: memory address bits 24-27 - bits 12-15: B26: unused B28/B38: memory boards installed on the system B39: error latches Error latches are a 4-bit subset of the NMI register that store error information. The conte `nts are: - bit 0: if = 1, a bus timeout occurred. If=0, a parity error occurred, and bits 2 and 3 can be used to locate the chip in error - bit 1: if = 1, a DMA was in progress at the time the error was detected - bit 2: if = 1, the low byte of the word accessed had bad parity - bit 3: if = 1, the high byte of the word accessed had bad   hes B39: memory address bits 24-27 - bits 12-15: B26: unused B28/B38: memory boards installed on the system B39: error latches Error latches are a 4-bit subset of the NMI register that store error information. The cont gents are: - bit 0: if = 1, a bus timeout occurred. If=0, a parity error occurred, and bits 2 and 3 can be used to locate the chip in error - bit 1: if = 1, a DMA was in progress at the time the error was detected - bit 2: if = 1, the low byte of the word accessed had bad parity - bit 3: if = 1, the high byte of the word accessed had bad parity. Possible causes for this error are: - An I/O port fails to respond (by sending a transfer acknowledge) or a nonexistent I/O port is referenced - A non hexistent memory location is referenced. A parity error has occurred because the address specified is greater than the highest address of installed memory. This typically happens as a result of an insufficient stack size, a jump to nonexistent memory, parity. Possible causes for this error are: - An I/O port fails to respond (by sending a transfer acknowledge) or a nonexistent I/O port is referenced - A none axistent memory location is referenced. A parity error has occurred because the address specified is greater than the highest address of installed memory. This typically happens as a result of an insufficient stack size, a jump to nonexistent memory, or a bad array subscript. - Memory timing and control do not recognize a legal address, and fail to send a transfer acknowledge. - An invalid pointer is referenced. The pointer is not a valid memory address. - DMA (Direct Memory Address) is programmed inc borrectly and thus SN:RA is meaningless. (Refer to the Fatal-Error Message explanation in the Troubleshooting chapter for the interpretation of operating system crash status words.) Shared resource processor Kernel: Bus time-out. A bus time-out occurs on a bus server (formerly master) if a bus subordinate does not acknowledge a request in 15 microseconds. A processor is a bus server when it writes and reads another processor's memory, a bus subordinate when its memory is written and read by the bus ser cver. The error condition causes termination of the operating system and an automatic reload on a workstation. On a shared resource processor, configuration parameters and the keyswitch position may avoid operating system termination. A subordinate processor experiencing a crash such as an Erc 21, Erc 23, and so on, issues the bus error signal to its server. The server then crashes with an Erc 28. Possible causes to check include: - A processor board that is poorly seated with the backplane. - Hardw dare that is not distributed across the system bus properly. - The crashing processor or the processor involved in a remote reference is faulty. - An attempt was made to access a nonexistent processor. If system crash status word 4 is a 3, a remote reference was being performed when the crash occurred. Status word 5 is the contents of the remote slot number register (port 40h). Word 6 is the contents of the base register zero (port 48h). AWS/IWS: The seventh and eighth words of a crash status message  eare the CS and IP of the instruction following the one that caused the timeout (usually by doing I/O to a nonexistent port or referencing a nonexistent memory location). On an IWS, the third word contains the value of port 56h.Kernel: Memory parity failure. The fifth status word contains the lower 16 bits of the error address. The sixth status word contains NMI Register 1; the meaning depends on the processor type. The error condition causes termination of the operating system and an automatic reload.  f The contents of NMI Register contains the following information (bit 0 indicates the least significant bit: - bits 0-3: address bits 16-19 - bits 4-7: B26: error latches B28/B38/B39: Memory address bits 20-23 - bits 8-11: B26: unused B28/B38: error latc or a bad array subscript. - Memory timing and control do not recognize a legal address, and fail to send a transfer acknowledge. - An invalid pointer is referenced. The pointer is not a valid memory address. - DMA (Direct Memory Address) is programmed in icorrectly and thus SN:RA is meaningless. (Refer to the Fatal-Error Message explanation in the introduction of this section for the interpretation of operating system crash status words.) Shared resource processor: Double-bit error detected by error correction code (ECC) circuitry. System crash status word 3 is the NMI status code. Status word 4 is the high 2 bits of the memory address at the time of the NMI. Status word 6 contains the ECC syndrome register contents.Kernel: Power failure Shared reso jurce processor: Power failure. System crash status word 3 is the NMI status code. Status word 4 is the high 2 bits of the memory address at the time of the NMI.Kernel: Unknown nonmaskable interrupt. The third word of the crash status message contains the value of port 56. The seventh and eighth words are code segment (CS) and instruction pointer (IP) when the nonmaskable interrupt is detected. The error condition causes termination of the operating system and an automatic reload. (Refer to the Troub kle Shooting chapter for the interpretation of operating system crash status words.) Shared resource processor: Unknown NMI. System crash status word 3 is the NMI status code. Status word 4 is the high 2 bits of the memory address at the time of the NMI.Kernel: Stray interrupt or illegal instruction. Shared resource processor: Stray interrupt. System crash status word 3 is the interrupt type multiplied by 6. Status word 4 is the interrupt service register, word 6 is the interrupt request register, ( land word 7 is the interrupt mask register. The error condition causes termination of the operating system and an automatic reload. The stray interrupt number referred to in the log entry for this error code is not significant; it is indicating the type of interrupt that the processor has attempted to service when no actual interrupt condition has occurred. This problem is probably caused by an invalid program jump to the processor's low memory interrupt vector table. A hardware failure could cause an 4 minterrupt of an unknown type.Kernel: Divide overflow. This is usually caused by a divide by zero. On a workstation, the seventh and eighth words of the crash status message are the CS and IP of the instruction following the one that caused the overflow. The other status words contain the same information as they would for an error26. The error condition causes termination of the operating system and an automatic reload. (Refer to the Troubleshooting chapter for an explanation operating system crash s@ ntatus words.) Shared resource processor: This is usually caused by a divide by zero. System crash status words 7 and 8 indicate the address of the instruction following the instruction being executed when the crash occurred. The error condition causes termination of the operating system and an automatic reload on a workstation. On a shared resource processor, configuration parameters and the keyswitch position may avoid operating system termination.Kernel: Invalid Op Code. This error occurs followingL o an attempt to execute an illegal instruction. Shared resource processor: Bus error. This error results from a reference to a nonexistent remote processor memory address or a remote double-bit error. If system crash status word 4 is 3, a remote reference was being performed when the crash occurred. Status word 5 is the contents of the remote slot number register (port 40h). The board designated by the remote slot number is usually the cause of the crash. Word 6 is the contents of the base register zeX pro (port 48h).Kernel: Math coprocessor not present. A floating point instruction was encountered that cannot be executed due to the absence of the numeric   real mode program that will call MapXBusWindow, specify Yes for this parameter in [Sys]Config.sys.Kernel: Response buffer too small. The response buffer could not hold all of the requested information. Some operations transfer the information that does fit into the buffer before returning this status code. Other operations return this status code without transferring any data.Cluster Request Management: Not enough w cluster buffer memory. Initialization error in server (formerly master). Insufficient memory is available to allocate for cluster buffers. Specify smaller data structures at system build. The error condition causes operating system termination and an automatic reload on a workstation. On a shared resource processor, configuration parameters and the keyswitch position may avoid operating system termination.Cluster Request Management: No available request control block (RCB). No RCB is available at th xe local CWS Agent Service Process to process this request. Scoprocessor or a floating point emulator.Kernel: Request table is inconsistent. The error condition causes termination of the operating system and an automatic reload on a workstation. On a shared resource processor, configuration parameters and the keyswitch position may avoid operating system termination.Kernel: No such request code. In most cased qs, this error occurs when a workstation or shared resource processor requires rebooting after an application has been installed or updated. Try rebooting the system. If this does not correct the problem, the software package was probably not installed correctly. Try repeating the software installation procedure. In other cases, BuildAsyncRequest or BuildAsyncRequestDirect return this status code if the request code is not recognized. The stack pointer is not valid because the procedure does not know hop rw many words to remove from the stack. This error generally comes from an improper Request.sys file. The request code file(s) were probably not merged correctly. The INSTALL NEW REQUEST command or SIM had a problem merging the request file(s).Kernel: Invalid message on default response exchange.Kernel: Service not available. The request is not being served by any system service process. A system service process must call ServeRq to declare its readiness to service the specified request code. Possi| sble causes of this problem include: - a service was not installed locally or at the server (formerly master) by manual installation or through [Sys]SysInit.jcl. - duplicate entries in the Queue.index file (specific to Queue Manager). - attempting to deinstall a service at a processor on which it was not installed. For example, XBIF Service may have been installed at a server workstation and deinstallation attempted at a cluster workstation. Check for the relevant run file to be certain that the  tservice was installed into memory, and on which processor it was installed. Another option is to check partition status to see what software is running in active memory. Install the service that is needed either manually or through [Sys]SysInit.jcl.Kernel: Exit run file is not specified.Kernel: Invalid X-Bus ID. There is no workstation module that corresponds to the specified ID. Shared Resource Processor Kernel: Wrong file system overlay.Kernel: The I-Bus parameter in a GetModuleID call is ill uegal. In the workstation environment, an I-Bus parameter of 1 specifies the I-Bus and a value of 2 specifies the X-Bus. Shared Resource Processor Kernel: Invalid termination request.Kernel: Request cannot be serviced until the application is swapped into memory. Swap in and reissue the request.Kernel: X-Bus memory window size is larger than allowed by the system configuration file. This error occurs if you specify No to the parameter UsedFromVirtualRealMode in the [Sys]Config.sys file, and then  va real mode program attempts to call MapXBusWindow. Therefore, if you are running a  pecify more RCBs at system build by modifying nRcb or modify the application system to require fewer concurrent requests.Cluster Request Management: Agent request block too large. The user-defined request block is too big for the Agent to handle. Check the total size of the requests being issued.Cluster Request Management: Invalid response from server. The response from the server (formerly master) does not match the request. The error condi ytion causes operating system termination and an automatic reload on a workstation. On a shared resource processor, configuration parameters and the keyswitch position may avoid operating system termination.Cluster Request Management: Unmatched response at server Workstation Agent Service Process. Probably a message was erroneously sent to exchange 12 at the server (formerly master). The error condition causes operating system termination and an automatic reload on a workstation. On a shared resource pr zocessor, configuration parameters and the keyswitch position may avoid operating system termination.Cluster Request Management: Request block too large. The request block (with data fields expanded) is too large for the transmission buffer or line buffer. Reduce the size of the request or specify larger buffers at system build by modifying nSectorPerXBlock, or for a very large request, piecemeal the request.Cluster Request Management: Server (formerly master) going down. Polling of the cluster workstat {ion is going to stop.Reserved.General: Invalid system common subroutine index. The subroutine number is too large.General: An invalid pointer to a procedure (possibly zero) was detected.General: Service is already installed. You tried to install a system service (for example, XBIF Service) that is already installed. A system service can be installed only once.General: The bus is locked. Some other process is using the X-Bus/F-Bus.General: Bad user. A process that did not lock the X-Bus/F-Bus attem |pted to unlock it.General: Bad handle. A process attempted to remove an ISR that it did not own.Reserved.General: Invalid device specification for a communications line. The device specification does not match any of the codes for the InitCommLine request. Note that when the system service for a module (such as the Datacomm Service for the Four-Port Data Commications Expander, or XC-002 Service for the Multiline Expander) is not installed, the codes for the ports on that module are not recognized. B }MULTI: BMULTI cannot be installed on a data communications expansion (DCX) module because the DCX Service is not installed. X.25 Gateway: This indicates that the channel specified in the packet level configuration file is either incorrect or being used by another application.General: Communications line baud rates must match. A parameter error occurred in InitCommLine or ChangeCommLineBaudRate. The specified communications line does not support the baud-rate clocking option requested. If split baud r ~ates (different baud rates for receiving and transmitting) are not supported by the specified channel, the transmit and receive baud rates must match, unless one is zero (indicating external clock). If one is zero, the other must also be zero, unless the specified communications line supports independent selection of external versus internal clock for receive and transmit.General: Invalid communications line handle. The CommLineHandle argument is not a valid handle previously returned by InitCommLine. T  he caller does not currently have this channel open. (Once ResetCommLine has been issued, the CommLineHandle is no longer valid and no further operations can be performed on the channel until another InitCommLine is executed.)General: ReadCommLineStatus or WriteCommLineStatus parameter error. The specified mask bit is undefined, or an attempt was made to write a bit that can only be read, or vice versa.General: A parameter to a CommLine operation is invalid. This error code appli  lt results. Faults transfer control automatically to the operating system fault handler. Non-` system service programs will exit and load the exit run file (normally Exec.run). The system will crash if there if a fault in system services or if the fault occurred during an interrupt. Breaking any of the protection rules generates a general protection fault, exception 13. An example of an exception is a bad selector due to a programming error. Any fault causes an erc 80. You can force general protection faults to activate the Debugger by specifying :EnterDebuggerOnFault. As a result, you cannl ot load values other than selectors into the ES register. When you do, the hardware tries to fetch the associated descriptor, resulting in a fault -- even before you try to use the segment register to reference anything. The selector value 0 is special. It can be loaded into a segment register, but causes a fault if it is subsequently used in an address calculation. The 0 value allows tes to miscellaneous par  ameters such as the RxTx argument to ChangeCommLineBaudRate.General: Communications line does not support Non-Return to Zero Invert (NRZI). The hardware does not support NRZI encoding on the specified channel. This status code is also returned if the hardware does not support TDI or X.21 electrical interface on the specified channel.General: The Communications Line Configuration Block (CLCB), a parameter to InitCommLine, is not of the expected size. Since the CLCB is designed to accommodate future ex$  pansion, this error code could indicate that the program uses a feature not supported by the older operating system on which it is running. Otherwise, the code indicates a programming error.General: The InitCommLine Return Block, in which results are returned from InitCommLine to the user, is not of the expected size. This error code indicates a programming error.General: Communications line does not support Direct Memory Access (DMA). The hardware does not support DMA capabilities on the specified ch0 annel.General: Bad CommLineDmaStatus return block size. The CommLineDmaStatus Return Block, in which the current transmit and receive counts is returned, is not of the expected size. This indicates a programming error.General: Invalid combination of communication lines using Direct Memory Access (DMA) and non-DMA capabilities. The communications hardware requires that if DMA capabilities are specified for the second port of each pair of ports (such as channel B of ports A and B, or channel D of ports C<  and D), the first port must also be initialized to support DMA. This status code is also returned if the first port has been initialized for non-DMA use, and an attempt is made to initialize the second port to support DMA. Your configuration may require that one channel be used in DMA mode and the other channel in non-DMA mode. Set the port assignments so that the application that requires DMA specifies the first port of the pair, and the other application specifies the second port.Reserved.General: H General Protection fault. Your program or application tried to access an invalid memory address. Several checks are associated with loading a segment register and its descriptor cache register. There must be an entry in the descriptor table for the selector that was loaded; the system knows the size of the descriptor table (which varies from table to table) and verifies that the selector does not index beyond the end of the table. The system uses information from the descriptor to perform other checksT . In addition to the base address, the descriptor contains the size of the segment, the type of segment, and other protection-related information. You cannot access accidentally beyond the end of the segment in protected mode, execute data segments, and write to code segments. You can protect certain data segments from being written and certain code segments from being read. If the selector is invalid, a fau  he passing of, for example, pbPassord = 0 and cbPassword = 0 in an OpenFile call. Although you can use 0, do not use tx he value to calculate an address. Additional exceptions can occur later when using a valid segment register in an address calculation. Trying to address beyond the end of a segment is this type of exception, called a limit exception.General: General protection violation by a real-mode application running under a protected-mode OS. You tried to access an invalid memory address. Real mode protection faults may occur when a memory access extends beyond the end of a segment. You cannot access accidentally  beyond the end of the segment in protected mode, execute data segments, and write to code segments. You can protect certain data segments from being written and certain code segments from being read. If the selector is invalid, a fault results. Faults transfer control automatically to the operating system fault handler. Non-system service programs will exit and load the exit run file (normally Exec.run). The system will crash if there is a fault in a system service or if the fault occurred during an  interrupt. You can force general protection faults to activate the Debugger by specifying :EnterDebuggerOnFault. Additional exceptions can occur later when using a valid segment register in an address calculation. Trying to address beyond the end of a segment is this type of exception, called a limit exception.General: Stack Fault. A protected mode program encountered a protection fault during a stack operation.General: Segment not present. A descriptor points to a segment which is marked not pr  esent in memory. In general, this error represents a system failure.General: Memory page fault. A descriptor points to a page which is marked not present in memory. This error is possible only on an 80386 processor. In general, this error represents a system failure.General: Stack overflow. The program executed an INTO (interrupt on overflow) instruction and the overflow bit was set in the Flag register.General: Segment bounds check failed. The program executed a BOUND instruction that detected a" n out of bounds condition.General: Math coprocessor error. The math coprocessor is signaling an error through the 80386 ERROR# input pin. This exception is only possible on an 80386 processor.General: Math coprocessor overrun.General: Double fault. While trying to invoke a handler for an exception (fault), the processor is unable to handle a second exception. Application programs are not expected to generate double faults. Therefore, a double fault is probably caused by an operating system error or $ a system service error.General: Operating system stack overflow. The stack of an operating system process has been corrupted.General: Operating system checksum error. Operating system code has been overwritten (probably by an application program).General: Interrupt stack overflow. This error occurs when: - An interrupt service routine (ISR) uses too much stack space and overflowed the special operating system stack reserved for mediated ISR's. - A raw ISR happens to interrupt a lower-priority medi& ated ISR. - An interrupt handler encounters a protection fault during a stack operation. Modify the ISR's use of stack space or build an operating system with a larger interrupt stack.General: A real mode program attempted an operation that is restricted to protected mode programs. The real mode program cannot reference protected mode structures and procedures.General: Caller must be protected mode. A real mode program attempted an operation that is restricted to protected mode programs. The real m( ode program cannot reference protected mode structures and procedures.General: The System Common Heap is full.General: A parameter list which was passed to SystemCommonInstall, or was defined within [Sys]Config.sys, is too long.General: A System Common entry already exists for this proced   . Increase sOsData for the file system generation prefix file.Shared Resource Processor Initialization: CTOS/XE configuration file larger than 64 Kb. The configuration file must be less than 64 Kb. This error only applies to the SrpConfig.k.sys file (where k is the keyswitch positio 7 n) that was read on this boot. Use the FILES command, specifying Yes to [Details?], to verify the problem. Reduce the number of entries in the file. You may be able to increase the number of entries in the Default Processor section of the configuration file, eliminating the need to repeat entries on individual processor entries. For example, if you have two Cluster Processors and one General Processor, and want to set the cluster line speed to 1.8 MB in each, you can set the default processor entries ,9 as follows: :Processor:Default :ClusterLine1: (Speed = 1.8M) :ClusterLine2: (Speed = 1.8M) Refer to your System Administration Guide for more information.Shared Resource Processor Initiure number.General: System common parameter list unknown character.General: An attempt was made to use SystemCommonConnect without predefining the parameter string in [Sys]Config.sys.Initialization: Memory f* ailure was detected during initialization.Initialization: There is insufficient memory for operating system initialization. This can be caused by too much software on the server (formerly called master). The error condition causes operating system termination and an automatic reload on a workstation. On a shared resource processor, configuration parameters and the keyswitch position may avoid operating system termination.Initialization: No Device Control Block (DCB) was configured for the device from,  which the operating system was bootstrapped. The error condition causes operating system termination and an automatic reload on a workstation. On a shared resource processor, configuration parameters and the keyswitch position may avoid operating system termination.Initialization: Initialization error. The operating system logs this error during initialization (for example, if it finds something wrong with the keyboard or screen). Refer to the PLOG command in your Executive Reference Manual.Shared Re. source Processor Initialization: Insufficient Y blocks or Z blocks specified at system generation on the shared resource processor server. Increase the number of Y blocks or Z blocks of the failing processor by either recustomizing its operating system or modifying the Y or Z block entry in the processor's configuration file. Refer to your System Administration Guide or CTOS Operating System Concepts Manual for more information about Y and Z blocks.Shared Resource Processor Initialization: Insufficient 0 hardware configuration detected. There are no Cluster Processors or General Processors running, or there are too many File Processors, Disk Processors, or Storage Processors running. Another possible cause is too few devices in the Mount Table (nMountedDisks).Shared Resource Processor Initialization: An shared resource processor initialization file contains an error. This is usually a syntax error. Correct the parameters for the failing processor in the system initialization file. Your Installation an3 d Configuration Guide and System Administration Guide contain information about the proper format for processor initialization files. This error may also occur if TmpFilter.run is the first system service being installed in the Master Processor. Check the system initialization files.Shared Resource Processor initialization: The watchdog process on the shared resource processor Master Processor detected the failure of another processor on the bus. This error is returned only if a processor other than t5 he Master Processor crashes and the "NoWatchDog" entry has been removed from the shared resource processor master configuration file, [Sys]SrpConfig.sys.Initialization: Insufficient memory for file system initialization  alization: Memory failed initialization tests. While booting, the operating system tests the ECC capability of the memory. If the test fails, then the operating system boots, but ECC is disabled. Run diagnostics or Visinostics. Refer to the diagnostics or Visinostics documentation.Reserved.Initialization:8;  Wrong hardware. The workstation hardware is invalid for use with the software.Initialization: Invalid operating system. The operating system version is too old.Initialization: Release timeout. This software product has expired. Install a newer version.Initialization: Cannot load a request code level. Level 0 cannot be loaded with a loadable request file. It must be built into the operating system.Initialization: Inconsistent loadable request code tables. The loadable file is incorrect.InitializD= ation: Bad sysgen tables. Incorrect information was inserted into sysgen table.Initialization: The XBIF service must be installed before this run file can be executed.Reserved. Kernel: Interrupt cannot block. An interrupt handler called Wait. Because there was no message queued at the exchange passed to Wait, the system crashed. Erc 130 indicates a programming error. Only the device handler can call Wait. This error causes operating system termination and an automatic reload on a workstation. OP? n a shared resource processor, configuration parameters and the keyswitch position may avoid operating system termination.Reserved.Shared Resource Processor Initialization: A processor attempted to route a request to itself, which cannot be done.Shared Resource Processor Initialization: Remote request is too large for local buffer or the pb/cb in the request may be corrupt. Try increasing the number of Y or Z blocks for the failing processor. Refer to your System Administration Guide or CTOS Operating S\A ystem Concepts Manual for more information about Y and Z blocks. Also check the number and size of the request pb/cb and response pb/cb.Shared Resource Processor Initialization: Cannot remote boot a processor that has not been initialized. This can be caused by either of two conditions: - There is no processor. The processor named is not part of the system because it does not physically exist or because it was never booted. - The target processor is dead. The processor was valid at one time buthC  has crashed. It can no longer receive messages or requests.Shared Resource Processor Initialization: Target processor did not respond to remote boot. This error code is most likely to occur during initialization.Shared Resource Processor Initialization: An illegal option was used in GetSlotInfo or GetProcInfo, or an illegal code in the CDT was issued from RemoteBoot.Shared Resource Processor Initialization: Too many disk devices were declared in the [Sys]SrpConfig.sys file. Increase the size of tE %nMountedDisks in the system generation prefix file table for the master processor and regenerate the master processor's operating system. For more information about customizing shared resource processor operating systems, refer to your System Administration Guide.Initialization: No handle fixup available. There was no free handle fixup block at the time the request was made. Specify a larger number of fixup blocks at system build by modifying nFixup.Initialization: No handle available. There was no fG ree device handle when the open was issued. Specify more device handles at system build by modifying nDeviceHandle.Initialization: Orphan Request.Initialization: Bad routing.Initialization: Bad route table. An UpdateRouteTable or GetRouteTable request was issued for an invalid route table.Shared Resource Processor Initialization: Too many cluster lines. The maximum number of cluster lines is 32.Shared Resource Processor Initialization: Wait.Shared Resource Processor Initialization: Corrupt ICC.SharI ed Resource Processor Initialization: Odd control information.Reserved.Shared Resource Processor Initial   r example, brackets may be missing, or the specified node, volume, directory, or file name may be too long. If you enter a file name with more than one word, you must place single quotation marks (') around the file name.File Management: Invalid user number.File Management: Invalid request code. Any bad argument to a file operation, such as an invalid file protection or invalid length password, returns this code.File Management: Duplicate volume. You have attempted to W initialize a new volume with the same name as a volume that already exists.File Management: File is read only. You have attempted to modify a file to which only read access is permitted.File Management: Invalid file handle. The file handle is not associated with any open file. In a cluster configuration, this status code may mean that the server (formerly master) crashed. Restart the server, then re-enter your application and recover. This status code may also mean that you tried to perform an operY ation sucization: Bus address not mapped. The system returns this status code when a request that is supposed to be sent to a remote processor is sent to a service on the local processor. When a request code is a remote DMA request, ICC translates the first pb into a bus address. The server received a request that is expected to be a remote DMA request, but the request received is not remote DMA.Shared ResoK urce Processor Initialization: Invalid bus address. Returned by RemapBusAddress or UnmapBusAddress if the bus address supplied by the user cannot be used to reprogram or deprogram the mapper hardware because: - the format of the bus address is incorrect - the mapper slots referenced by the bus address are not in use - the mapper slots referenced by the bus address are in use but by different user. RemapBusAddress also returns this status code if the bus address is valid but does not reference enough mM ap slots to accomodate the remapped address.Initialization: No free map slot. MapBusAddress and ReserveBusAddress return this status code if there is no contiguous block of free mapper slots large enough to satisfy the request.Initialization: No mapper hardware. MapBusAddress returns this status code on processors that do not support the hardware bus address mapping, if a MapBusAddress request is made that specifies an array of pb/cbs rather than a single pb/cb.Reserved.Shared Resource Processor InitiaO lization: DMA Pending.Shared Resource Processor Initialization: Channel in use.Reserved.Shared Resource Processor Initialization: Service already installed.Reserved.Reserved.File Management: No free volume structure. You should configure the same number of Volume Home Blocks as Device Control Blocks in sysgen.File Management: Directory full. Delete unneeded files. You can also copy all the files to another directory and then remove this directory. Create a new larger directory with the name of the Q old directory. Then copy the files from the other directory to this new, expanded directory. If you receive this message while working in the directory, however, you must backup the disk using the BACKUP VOLUME command, then reinitialize the disk (FORMAT DISK command) with more files in the directory.File Management: No such file. The specified file does not exist. Check that you are using the correct volume and directory address, and that the file name is spelled correctly. The system retS urns this error at the beginning of system initialization if the run file [Sys]Batch.run is not present on the system. Use the FILES command to make sure the file is present. If necessary, copy the file from the Standard Software distribution diskettes or tape.File Management: No such directory. The specified directory does not exist. Make sure that the directory name is entered correctly, and that you specified the correct volume.File Management: Invalid file specification. Any portion of the fU ile specification is invalid. Fo  h as DELETE, SCRUB, or RENAME on a file that has been locked. Using the file handle returned from a LockFile operation as an argument for any file system call other than UnlockFile causes the system to return this status code.File Management: Invalid buffer size. This must be a multiple of 512 for disk volumes, unless you are using SetDevParams, which can set buffers to 128, 256, or 512.File Management: Invalid logical file address. This must be a multiple of 512 for disk volumes, unless you a[ re using SetDevParams, which can set buffers to 128, 256, or 512.File Management: No free File Area Blocks (FABs). Open fewer files concurrently, specify more FABs at system build, or compact the file system by backing up, reinitializing, and restoring the volume. If this does not correct the problem, increase the number of File Allocation Blocks (nFab) at Sysgen.File Management: No free file number. Open fewer files concurrently or specify more File Control Blocks (FCBs) and file user blocks (FUBs) pe^ r User Control Block (UCB) at system build (increase nFCB, nFUB). These parameters must have the same values. If they are modified, the values for the nlob and nFab should be modified accordingly.File Management: Unrecognized volume or device. The specified volume or device is not recognized. This may occur when: - The drive control cable is defective. - The workstation attempting to access a remote disk drive is either disconnected (cluster cable) or the wrong volume name is being used.File Manageme` nt: Volume is not mounted. The specified volume is not mounted. If you are using a floppy disk, make sure that the disk (volume) is properly inserted and check to see that the disk does not have the same name as another volume. This error may also occur when: - The disk is not formatted. (The disk may not have been initialized with FORMAT DISK.) - The volume home block (VHB) has been overwritten. - The area of the disk in which the VHB resides has a media defect.File Management: Invalid password. b The password supplied is longer than 12 characters.File Management: Invalid mode.File Management: Access denied. A file system request was made that was denied because: - The password is either missing or incorrect. Use the PATH command to supply the password before you restart the installation. - An illegal request was made to change the length of, modify, or access a system file (such as [Sys]SysImage.sys).File Management: File in use. This error occurs when the Executive command file for a w(d orkstation is in use. This happens if the workstation is running Context Manager, or if several workstations are sharing a command file on the server (formerly master). If the workstation is running Context Manager, log out and after you sign on again, perform the operation before you install Context Manager. For a shared command file, have all users who share the command file log out and remain logged out while you restart and perform the installation.  This error also means that a process that opens a 4f file in modify mode is guaranteed exclusive access. Only one file handle can refer to a file that is open in modify mode.File Management: File header invalid checksum. The volume control structures are invalid. Backup, reinitialize, and restore this volume.File Management: File header invalid page number. The volume control structures are invalid. Backup, reinitialize, and restore this volume.File Management: File header invalid header number. The volume control structures are invalid. Backup, rei@h nitialize, and restore this volume.File Management: File already exists.File Management: No free file headers. Backup, reinitialize, and restore this volume, specifying more File Header Blocks. For a floppy disk, initialize with more file headers.File Management: Free File Headers broken. The volume control structures are invalid. Backup, reinitialize, and restore this volume.File Management: Device is in use.File Management:   run file a second time.File Management: Unrecognized format run file. The file is probably not a run file, or else the run file version field is v not understood by the operating system loader. Use a Linker release compatible with the operating system.File Management: Wrong pRq argument. CheckReadAsync or CheckWriteAsync does not agree with the preceding ReadAsync or WriteAsync.File Management: Invalid attributes for secondary task. A task loaded with LoadTask (as opposed to Chain) cannot use virtual code segments or have a memory array. (Refer to Task Management, status codes 430-499, and your Development Utilities documentation.)File Managemenx t: Too many runs. The file cannot be expanded because it already contains the maximum number of runs. The maximum number of runs per file is a system build parameter. Compact the file system by backing up, reinitializing, and restoring the volume.File Management: You cannot write to the [Sys]Log.sys Log file.File Management: You Device is already mounted.File Management: Device is not mounted.File MaLj nagement: Disk is full. There are not enough available disk sectors to accommodate the current CreateFile or ChangeFileLength request, or to install an application.  You will have to clear some room on the disk before you restart the operation. Remove unneeded files, such as <$*>*, <*>*.ts, and <*>*.tmp. Also delete -old files that you do not need to recover the operation you were working on.File Management: This is not a device that can be mounted.File Management: No valid Volume Home Block (VHB). Xl  The volume control structures are invalid. Back up, reinitialize, and restore the volume.File Management: File Header invalid file name. The volume control structures are invalid. Back up, reinitialize, and restore the volume.File Management: Odd-byte buffer address. The buffer must be word-aligned.File Management: The wrong volume is mounted.File Management: Invalid device specification.File Management: Directory page invalid. The volume control structures are invalid. Back up, reinitialize, andn d restore the volume.File Management: Request is not valid for this device.File Management: Wrong volume chosen as destination. The RENAME utility cannot move a file to another volume.File Management: Directory already exists.File Management: Directory is not empty.File Management: MFD is full. Backup and reinitialize the volume, specifying more sectors for the Master File Directory (MFD). Then RESTORE this volume.File Management: Verify error. A Volume Control Structure (for example, VHB or FHB) pp was written and then immediately reread to verify that it was written correctly. The information reread does not compare with the information written, although the disk controller did not report an error. Error 243 indicates a serious disk controller, DMA, or memory hardware malfunction.File Management: System device is not ready. If you bootstrap a swapping operating system from a floppy disk, the operating system floppy disk cannot be removed from the drive. The error condition causes operating syste|r m termination and an automatic reload on a workstation. On a shared resource processor, configuration parameters and the keyswitch position may avoid operating system termination.File Management: Run file invalid checksum. The file is probably not a run file, or has been improperly altered in some way (for example, with the Editor instead of the DEBUG FILE command).File Management: Invalid run file. The file is probably not a run file. This also can occur if the run file header contains an inconsistent cy, or a dormant run file has become invalid because the server (formerly master) went down. The last case is a recoverable error. Dormant run files are run files that are no longer being executed by an active context, but are still in memory. Should the run file be executed in the future, it need not be loaded. To recover from this error, simply execute the    cannot open the operating system image file for the swapping cluster workstation.File Management: You cannot read the operating system overlay for the swapping cluster wz orkstation.File Management: All the user numbers on the server (formerly master) workstation have been used. Change the system build parameter for nWSUserNum. This code is also returned if you enter an invalid node or volume name, or an invalid queue name while using the PRINT command.File Management: Data verification error.File Management: A parameter passed was not a multiple of 512.File Management: Swap space full.File Management: No swap file.File Management: No free swap FABs. Swap file is | too fragmented.File Management: Swap file is inconsistent.File Management: Cannot access swap file.File Management: Virtual code is not supported. Overlays are not allowed in Global Descriptor Table-based programs or in secondary tasks.File Management: Internal error. Attempted to use a feature not present on the PC.File Management: Internal error. The operating system issued an invalid configuration request to the File System.File Management: Bad run file overlays not together.File Management: Fi~ le not locked. An attempt is being made to unlock a file that is not locked.File Management: File locked. The operation attempted to access a file that was locked by another user. If you are attempting to create a file and receive this status code, this means that the file name has been locked although the file does not exist.File Management: Invalid lock mode. An invalid lock mode was specified as an argument for a LockFile operation. Valid modes are: - 0, to pocket requests from other users for tЀ he locked file. - 1, to return an error code to other users who attempt to use the locked file. For more information on the LockFile operation, refer to your Procedural Interface Reference Manual.File Management: No free lock request list. There are no free lists available to queue a request for a file that is locked by another user. This number is a Sysgen parameter; you can increase it with the Customizer. Refer to your System Administration Guide.File Management: Attempted a directory operation on܂  a file.File Management:  The file header has a bad parent specification.File Management: The file header has a bad parent directory name.File Management: The directory file is invalid.File Management: When renaming a directory, you either attempted to change volumes, or to rename the directory under itself.File Management: The request was not valid for a directory. For example, a request to change file length would not be valid.File Management: The handle is not a file handle. These operations do no t work on volumes or directories.File Management: Bad protection code file handle.File Management: There is no free FCB (file control block).File Management: Bad link. This is an internal file system error. Either a file or a directory is not correctly linked to a parent directory.File Management: The Operating System file name table is too small. The table must be large enough to hold the names of all open files.File Management: No volume password.File Management: Request incomplete.File Managemen t: These are internal file system errors, resulting in a crash. The problem can be caused by bad structures on the disk; backup, reinitialize, and restore the disk. The error condition causes operating system termination and an automatic reload on a workstation. On a shared resource processor, configuration parameters and the keyswitch position may avoid operating system termination.Reserved.File Management: Log buffer overflow. Multiple errors occurred rapidly and the operating system was unable to l og all of them.Reserved.File Management: Invalid file protection level.Device Management: Device is not ready. Make sure the power is on and the floppy disk is properly inserted in the disk drive; if the floppy drive has a latch, make sure it   ppy Disk Controller: Floppy disk controller never ready in result.Floppy Disk Controller: Floppy disk controller not data input in result.Floppy Disk Controller: Floppy disk controller not busy after transfer request.Floppy Disk Controller: Floppy disk controller wrong unit after transfer request.Floppy Disk Controller: Floppy disk T controller busy without transfer request.Floppy Disk Controller: Received floppy disk controller interrupt from undefined unit. This error may result from a failure to include all floppy disks in the system build.Floppy Disk Controller: Floppy timeout.Floppy Disk Controller: Incomplete Direct Memory Access (DMA) transfer to or from floppy disk.Floppy Disk Controller: Floppy disk controller failure. The value read from sector register is different from the value written.Reserved.Hard Disk Controller: ` Hard disk controller busy in command.Hard Disk Controller: Hard disk controller never ready in command.Hard Disk Controller: Hard disk controller d is properly closed. Also check the hard disk. Error 300 can be caused in the same way as error 215. With an error 300, the device is recognizable, but a control line (ready) never became active.Device Management: I/O error. This may be caused by a hardware or m  edia fault. Frequent 301 errors usually indicate a hardware failure; check boards, drives, cables, head alignment, and so on. Several 301 errors at the same head/cylinder/sector numbers usually indicate flawed media, but with floppy disks, try using another drive. The problem may be due to incompatible head alignment. Check the contents of PLog. Some applications may require a more recent version of the operating system. Update to a more recent version. Shared resource processor: Disk I/O error Pos sible causes: - Previously unrecorded bad spots appear on the disk. - The disk is deteriorating, producing unwriteable or unreadable areas. - The AC and DC grounds are connected. - Input power is unstable or inadequate. - The disk drive daisy chain is not terminated properly (for example, there is no terminator or there are multiple terminators in the chain). Perform a backup, reinitialization, and restore of the disk.Device Management: Write protected. You are trying to save a file onto a write-pro$ tected disk. Remove the covering from the write-protect notch on the floppy disk.Device Management: No free I/O Blocks (IOBs). There are too many concurrent input/output operations. More IOBs should be specified at system build by modifying nIOB.Device Management: Odd DMA count. The number of bytes transferred by Direct Memory Access (DMA) must be even.Device Management: Attempted to reference unformatted disk. Any attempt to use an unformatted disk by any I/O request, except by the format request, 0 returns this error.Shared resource processor Device Management: Recalibration failed. Run the diagnostics or Visinostics.Device Management: Hard disk controller write fault detected. Run the diagnostics or Visinostics.Device Management: Incomplete DMA. MassIo drivers return this status code when a DMA fault occurs that prevented the transfer of all the data. This status code is not file system specific; it can be used by other operating system facilities.Device Management: Not local DMA. The SCSI < Manager returns this status code if a remote DMA request has been received and the File Cache Service has not been installed on the SCSI Manager's processor. The SCSI Manager received a request that requires DMA to a remote processor, but the server cannot perform DMA except to the local processor's memory. For a SCSI disk connected to a GP/SI to be accessible from another processor, the File Cache Service must be installed on the GP/SI that controls the disk.Reserved.Floppy Disk Controller: Floppy disH k controller busy in command.Floppy Disk Controller: Floppy disk controller never ready in command.Floppy Disk Controller: Floppy disk controller data input in command.Flo  ata input in command.Hard Disk Controller: Hard disk controller never ready in result.Hard Disk Controller: Hard disk controller not data input in result.Hard Disk Controller: Hard disk controller is not busy after transfer request.Hard Disk Controller: Hard disk controller wrong unit after transfer request.Hard Disk Controller: Hard disk controller busy wl ithout transfer request.Hard Disk Controller: Hard disk controller interrupt was received from undefined unit. This may result from a failure to include all hard disks in the system build.Hard Disk Controller: Hard disk timeout.Hard Disk Controller: Hard disk controller local Direct Memory Access (DMA) fault. Incomplete DMA transfer to and from hard disk.Hard Disk Controller: Bad hard disk controller.Hard Disk Controller: Hard disk controller remote DMA fault.Hard Disk Controller: Cylinder or head ix s out of range.Hard Disk Controller: ECC is not available.Hard Disk Controller: Device is not formatted spiral.Hard Disk Controller: ECC inconsistency. An ECC-formatted disk was accessed in CRC mode, or vice versa.Reserved.SCSI Manager: A SCSI device has not interrupted (reselected or completed an operation on) the host processor.Reserved.SCSI Manager: A SCSI command was aborted. ScsiWaitTargetDataAsync returns this status code if the foreign SCSI initiator has terminated a command in progress by sen ding an ABORT message.SCSI Manager: Malfunctioning SCSI host adapter. The host adapter hardware has failed to pass consistency checks during the system boot or has returned inconsistent information during subsequent operation.SCSI Manager: No free SCSI Path Blocks (UPB). A ScsiOpenPath operation has failed because too many paths are already open. To correct the problem, modify nUpb at system build to specify more SCSI Path Blocks.SCSI Manager: No free SCSI Logical Unit Control Blocks (LUCB). A ScsiOp enPath operation has failed because no LUCBs are available. An LUCB is required for each SCSI device for which a SCSI path is opened. To correct the problem, modify nLucb at system build to specify more LUCBs. No more than 56 LUCBs are ever needed for each SCSI host adapter.SCSI Manager: The SCSI bus is busy. Either the BSY or SEL signals or both are asserted on the SCSI bus. This prevents the host adapter from arbitrating for and gaining access to the bus.SCSI Manager: SCSI device selection timeout.  A SCSI device failed to respond to selection by the host adapter. Normally this means no device is connected to the SCSI bus with the specified target ID, or a connected device is not powered on.SCSI Manager: Invalid SCSI Path Handle. Possible causes of this problem are: - the path handle parameter supplied in a SCSI operation is not a valid Path Handle previously returned by a ScsiOpenPath operation - a path handle for a path in "peek" mode has been invalidated because another user has opened a pa th to the same SCSI device in exclusive mode. - a path handle was opened for target mode in a non-target mode operation, or vice versa.SCSI Manager: A SCSI bus reset condition has occurred. The RST signal has been detected on the SCSI bus. This terminates all I/O operations in progress and causes all SCSI devices to perform soft or hard reset operations.SCSI Manager: No Command Descriptor Block Available. Returned if no SCSI Command Descriptor Block has been received from another SCSI initiator.SCSI M anager: Excess SCSI data phase. During a SCSI operation, the SCSI device attempted to transfer more data to or from memory than the transfer count permits. If the transfer is to memory (DATA IN phase), the additional bytes have been discarded by the SCSI Manager. If the transfer is from memory (DATA OUT phase), additional bytes have been fabricated by the SCSI Manager and sent to the device.SCSI Manager: SCSI timeout. A SCSI operation has failed to complete within the time specified by the SCSI operat ion or within the system default timeout limit.SCSI M   n: No  free selector name. Only 8192 selectors can exist at one time on this processor.Allocation: Bad selector name.Allocation: Segment in use.Allocation: Invalid pointer. A pointer parameter is invalid.Allocation: The operation failed because memory is not addressable from real mode. This error is returned when the client is real mode and the structure is not located within the first MB of memory. This message occurs only on protected mode workstations.Allocation: Not enough memory is available for both  the Executive and the requested system service.Allocation: All exchanges are already allocated. Specify more exchanges at system build. Also caused by too many files listed in the SUBMIT command. Submit fewer files at a time.Allocation: Invalid exchange identification specified to DeallocExch.Allocation: Not aligned on 4 KByte boundary. The operation failed because an address parameter is not aligned on a 4 Kb boundary.Allocation: Run file size error. The operationanager: Unexpected disconnect. A SCSI device (target) disconnected at an inappropriate time.SCSI Manager: Invalid host adapter number. The host adapter number in a ScsiOpenPath operation is not recognized by the SCSI Manager.SCSI Manager: Invalid target ID. The target ID in a ScsiOpenPath operation is not in the range 0 to 7 inclusive, or is the same as the ID of the host adapter.SCSI Manager: Invalid Logical Unit Number (LUN). The LUN in a ScsiOp̫ enPath operation was not in the range 0 to 7 inclusive.SCSI Manager: Outstanding SCSI operations. A ScsiClosePath operation has been attempted while SCSI operations for the path have not yet been completed. Wait for all SCSI operations to finish or timeout before closing the path.SCSI Manager: SCSI sense data is unavailable. After detecting a CHECK CONDITION for a SCSI operation, the SCSI Manager was unable to obtain sense data with a REQUEST SENSE command. The I/O error is reported with no sense dataح . The SCSI Manager does not use this error code.SCSI Manager: A SCSI protocol error has occurred. Information received from a SCSI device during an operation does not conform to the SCSI standard. The operation was terminated at the earliest opportunity, but what actions (if any) have occurred at the SCSI device are not known. This might be a cabling problem, a duplicate selection ID problem or a hardware malfunction in the SCSI device or host adapter.SCSI Manager: SCSI message reject. A SCSI targe t rejected a message sent by the host processor or the SCSI Manager has rejected a message sent by the SCSI device.SCSI Manager: SCSI bus parity error. An uncorrectable SCSI bus parity error was detected by the host processor or a SCSI device.SCSI Manager: SCSI target busy. A SCSI device has returned BUSY status to an attempted I/O operation. This error is returned by the File System. The SCSI Manager returns the BUSY target status to the user.Allocation: There is not enough memory available in a spe cific partition to satisfy memory allocation request. You may get this error when you attempt to install a application such as Batch Manager after installing Window Services. Install the application before Window Services. Linker/Librarian: The Linker does not have enough memory available to link the file. To link the file: - Properly determine and use valid parameters. - If you are running the Linker under the Context Manager, reconfigure the partition size. - Link the run file on a system with  more memory.Allocation: You cannot allocate long-lived memory. The memory cannot be allocated because the Debugger is locked into memory in multiple-process or interrupt mode. Refer to your Debugger documentation.Allocation: Invalid memory segment specification to DeallocMemorySL/LL.Allocation: Parameter in a memory management request is not aligned on a paragraph boundary (that is, the offset part of the segment:offset memory address must be zero). A paragraph is defined as 16 bytes.Allocatio  failed because the local page   map size is too small.Allocation: Run file protection mode not defined. The operation failed because the user has not previously defined a local page map.Allocation: Selector not an LDT selector. The operation failed because a selector parameter was not Local Descriptor Table-based.Reserved.Allocation: Bad Swapper data. Virtual code management failed because of inconsistencies in data structures required by the operating system.Allocation: LDT slot unavailable. The operation failed because there a, re no free LDT slots.Cannot Shrink Long-Lived memory. ShrinkPartition returns this status code if any long-lived memory is present. The user must ResetMemoryLL before calling ShrinkPartition.Timer Management: Too many Real Time Clock (RTC) requests. Specify a larger RTC request table at system build by increasing the size of npTiming.Timer Management: Invalid timer block specification in CloseRTClock.Reserved.Task Management: The partition is not large enough to load the exit run file. Possibly the D8 ebugger is locked in memory, or memory specifications at system build were too small. As a last resort, increase the size of sParExitRunFile. The error condition causes operating system termination and an automatic reload on a workstation. On a shared resource processor, configuration parameters and keyswitch position may avoid operating system termination.Task Management: The printer ISR already exists. Another program is using the communications or printer port. For example, the spooler is installedD  and an application program tried to print on channel A, B, or the line printer port.Task Management: Kbd Isr already exists. There is already an interrupt handler serving the keyboard.Task Management: Not an operating system call.Reserved.Task Management: Soft vector table is full. More space can be created at system build if necessary. Increase the value of the maxMedInterruptType parameter. In the sysgen.asm file, include the macro %Set(nSoftVec, X), where X is an appropriately high number. ReferP  to your System Administration Guide.Task Management: Bad Device Type. An invalid device type was passed to ControlInterrupt.Reserved.Task Management: Memory map overflow. An attempt was made to free or access memory. This caused the map to overflow. This is an internal error that indicates a problem in the software you are using.Task Management: Large memory map inconsistent. This is an internal error that indicates a problem in the software you are using.Reserved.Task Management: No available Act\ ive Runfile Information Block (ARIB). This is an internal error that indicates a problem in the software you are using.Task Management: ARIB was not created. An attempt was made to mark an Active Runfile Information Block that was not fully created. This is an internal error that indicates a problem in the software you are using.Task Management: ARIB not marked. An attempt was made to unmark an Active Runfile Information Block that was not marked. This is an internal memory management error that indih cates a problem in the software you are using.Task Management: No available Task Information Block (TIB). This is an internal memory management error that indicates a problem in the software you are using.Task Management: Active State Information Block (ASIB) inconsistency. An attempt was made to create an ASIB that already existed or to free an ASIB that did not exist. This is an internal memory management error that indicates a problem in the software you are using.Task Management: Task Information t Block (TIB) inconsistency. A TIB was referenced that had no associated Active State Information Block. This is an internal memory management error that indicates a problem in the software you are using.Task Management: Active Runfile Information Block (ARIB) inconsistency. An attempt was made to create an ARIB that was in use or did not exist. This is an internal memory managem  no data has been received before the current receive timeout period has elapsed, this status code is returned. This error usually appears in the Modem Server Status display. Teller Extension Module /Peripheral Extension Module: A read command has been done and no character is currently available on the port specified.Keyboard Management: Invalid escape sequence in submit file.Keyboard Management: Invalid argument to a keyboard operation.Keyboard Management: Invalid mode code specified in a call to SetSysInMode.Keyboard Management: Failure of 8048 keyboard microprocessor.Keyboard Management: Reset is down.Keyboard Management: An application system is being terminated by request of another proces s or ACTION-FINISH.Keyboard Management: No action code is available. ReadActionCode returns this status code if the workstation operator has not entered an action code.Keyboard Management: Type-ahead buffer overflow. Modify sKbdBuffer at system build.Keyboard Management: Keyboard staent error that indicates a problem in the software you are using.Task Management Linker/Librarian: Kernel Data Segment (KDS)   An attempt was made to free an ASIB or ARIB when the start of the linked list was null. This is an internal memory management error that indicates a problem in the software you are using.Task Management: Memory map inconsistency An attempt was made to free nonexistent memory, or the memory map contained overlapping pieces. This is an internal memory management error that indicates a problem in the software you are using.Task Management: Code is not shareable. An attempt was made to fork from a task  whose code was not shareable. This is an internal memory management error that indicates a problem in the software you are using.Reserved.Task Management: Segment not in memory. An attempt was made to deallocate a segment that was not present. This is an internal memory management error that indicates a problem in the software you are using.Task Management: This is an internal error that indicates a problem in the software you are using.Task Management: This is an internal inconsistency.Reserved.Vide o Display Manager: Frame number/coordinates do not agree with the Video Control Block (VCB).Video Display Manager: Invalid argument(s) to Video Display Management (VDM) or Video Access Management (VAM).Video Display Manager: The video buffer is not word-aligned.Video Display Manager: The Video Control Block is not completely initialized.Video Display Manager: Video Direct Memory Access (DMA) hardware failure.Video Display Manager: Too many video attributes on a line.Video Display Manager: Screen time out interval is too large. The maximum interval is 109 minutes.Video Display Manager: Cannot load font.Video Display Manager: The UnLockVideo operation called more times than LockVideo was called by an application or VAM.Video Display Manager: An unexpected message was received at the video lock exchange (27).Video Display Manager: Current frame overlaps another frame with unlike double high/wide characteristics. More than one LockVideoForModify was made.Video Display Manager: The number of lines col lectively defined by all frames exceeds the number of lines on the screen.Reserved.Reserved for special status codes related to localized VAM. For additional information, refer to the documentation provided with your version of the operating system.Reserved.Keyboard Management: Duplicate ReadKbd or ReadKbdDirect. Only one ReadKbd or ReadKbdDirect request can be outstanding at a time.Keyboard Management: No character available. You specified ReadInputEvent not to wait for a character code. This message  merely indicates that no character code is currently available. Status code 602 (ercTimeout) is also returned when the specified timeout elasped before the Communications Byte Stream operation had finished. OFIS Mail: The ReadModemBytes service reads incoming data from the indicated communications line. If  tus change queue overflow. Issue ReadKBDStatus more often.Keyboard Management: Soft Keyboard Reset. The keyboard is being reset by request ResetKbd.Keyboard Management: I-Bus Table Full. The operating system table th at records I-Bus device handlers (Mouse or pointing device) is full. This status code is returned by the ServeIBusInt operation.Keyboard Management: No such I-Bus handler.Keyboard Management: No such I-Bus ID.Reserved.Keyboard Management: Duplicate ReadTerminal Only one ReadTerminal at a time can be outstanding for each attached port.Keyboard Management: The port is being reset.Keyboard Management: The application has already issued an OpenTerminal for that port. Reserved.Keyboard Management: Failur e of 1654 Hardware ID microprocessor.Keyboard Management: The hardware ID number must be less than 128 and greater than zero.Reserved.Keyboard Management: No device is present on the Interface bus (I-Bus).Keyboard Management: MCR buffer overflow.Keyboard Management: Too many retries while reading a message from the MCR (bad message syntax).Keyboard Management: No MCR data is available.Keyboard Management: User buffer is not large enough to receive MCR data.Keyboard Management: Wrong mode specified at  ReadMCR function call.Keyboard Management: An incorrect Sys.Keys file was loaded.Pre-GPS Spooler: A ConfigureSpooler operation attempted to free a device that was not attached.Pre-GPS Spooler: A SpoolerPassword operation attempted to enter a password when the device spooler was not waiting for a password.Pre-GPS Spooler: Invalid device name specified in a SpoolerPassword operation. Specify O, A, or B.Pre-GPS Spooler: Invalid channel number specified in a ConfigureSpooler operation.Pre-GPS Spooler: A  ConfigureSpooler operation attempted to add a new device to a channel that is not free.Pre-GPS Spooler: Invalid device spooler configuration file was specified in a ConfigureSpooler operation.Pre-GPS Spooler: A spooler was installed with a device name that was already in use. Device names must be unique.Pre-GPS Spooler: Invalid Device Configuration File Specification. The cbConfigureFile field of the ConfigureSpooler service exceeds 91 characters.Pre-GPS Spooler: Invalid Queue Name. The cbQueueName  field of the ConfigureSpooler service exceeds 50 characters.Pre-GPS Spooler: Current print request was cancelled.Pre-GPS Spooler: Device restarted.Pre-GPS Spooler: Device is freed and needs to be reconfigured.Printer Spooler:  The device handle in the request was unrecognized.Printer Spooler: An attempt was made to supply a password when the Spooler was not waiting for one.Reserved.Spooler: An attempt was made to install a device with the same name as one already in use.Printer Spooler: Device is unab le to receive print data.GPS: The Print Service is unable to manage another local device. Reinstall the Print Service with a larger value for the [Maximum number of local devices] parameter.GPS: An attempt was made to access a device that was not installed.GPS: The Print Service is unable to handle the request. This is an internal error that indicates a problem in the software you are using. Contact your Unisys representative.GPS Spooler: Delete failed. The print job for which the delete request was(  issued cannot be found.GPS Spooler: Spool job not found.GPS: The Print Service job table is full. Either wait until the current Spooled jobs are finished and resubmit this job, or reinstall the Print Service with a larger value for [Maximum number of simultaneous jobs]. Shared Resource Processor: An attempt was made to install a printer spooler manager on a processor that does not have printer hardware. It can be installed only on a Cluster Processor (CP) or a Terminal Processor (TP). Check the init4 ialization file(s) to make sure that the other processors in your system do not contain an entry for a printer spooler manager.GPS: Print Service already installed.Printer Spooler: The Printe   have been issued by the operating system. This error is usually caused by services (formerly called servers) that do not handle swapping correctly. Either wait until the context in memory is finished, or finish the context that is in memory, and then try to switch your context again.Application Partition Management: Request is not valid for the primary partition.Application Partition  Management: Cannot swap a partition in. Context Manager: A context in memory cannot be swapped out. A context in memory cannot be swapped out because it has served a request, served interrupts, or has a communication or parallel printer resource in use. Either wait until the context in memory is finished, or finish the context that is in memory, and then try to switch your context again.Application Partition Management: The ReservePartitionMemory operation was called when all available partition memo ry descriptors were used. The number of partition memory descriptors may be configured by settinr Spooler was unable to complete a request because contact with the Queue Manager was lost.Spooler: The Printer Service received an illegal command from an old-style spooler application.Spooler: An attempt was made to add a new device with the same scheduling queue name as a previously installed device.Spooler: The@  loadable request file was either missing or was the wrong version.GPS Releases prior to 2.0: The Spooler went down. The Spooler is no longer installed. You must reinstall it.GPS releases prior to 2.0: Cannot install from the current partition. Installation must be done from the primary partition. Remove Context Manager if it is running. Reserved.GPS releases prior to 2.0: Invalid reset string. An invalid reset string was received in the document.GPS releases prior to 2.0: Invalid page orientatioL n. An invalid page orientation was received in the document.GPS releases prior to 2.0: Invalid GPS version. Update to the current version of GPS.Reserved.Application Partition Management: Partition is not vacant. Vacate the partition first. Context Manager: This version of the Operating System cannot support any more contexts. The operating system has run out of user numbers. This message may be displayed when you try to start a new application from the Context Manager screen.Application Partition X Management: Cannot create any more partitions. The number of partitions is a system build parameter. Specify more partitions at system build by modifying nPartitions. Refer to your System Administration Guide.Application Partition Management: Partition name is duplicated.Application Partition Management: Invalid partition handle is specified.Application Partition Management: Invalid partition name is specified. The partition name supplied is longer than 12 characters.Application Partition Managementd : Partition is vacant.Application Partition Management: Partition is locked. A task on a locked partition cannot be terminated.Application Partition Management: Partition is not locked. The partition should be locked before using the SetPartitionExchange operation.Application Partition Management: Partition exchange has not been set.Application Partition Management: Partition exchange has already been set.Application Partition Management: Request is valid only for an application running in the primap ry partition. The operation failed because the partition is not the primary partition or does not have a user structure. A user structure contains data such as the Application System Control Block and the Extended Partition Descriptor.Application Partition Management: Partition is already swapped.Application Partition Management: Partition is not swapped.Application Partition Management: Cannot swap out this partition. Context Manager: A context in memory cannot be swapped out. A context in memory | cannot be swapped out because it cannot be quieted; that is, the program has requests outstanding after swapping requests g nUseg in the appropriate sysgen prefix file. Refer to your System Administration Guide.Application Partition Management: Bad partition swap mode.Reserved.Queue Management: A RemoveQueueEntry, UnmarkQueueEntry, or RewriteMarkedQueueEntry operation was invoked with an invalid Queue Entry Handle (QEH). The QEH specified was for an entry that is not marked.Queue Management: A RemoveKeyedQueueEntry operation s pecified an entry that was previously marked.Queue Management: A RemoveKeyedQueueEntry, ReadKeyedQueueEntry, or MarkKeyedQueueEntry operation was invoked for which no matching entry was found.Queue Management: A MarkNextQueueEntry operation was invoked when no entries were available.Queue Management: The ReadNextQueueEntry operation specified an entry that was deleted since its queue entry handle was returned.Queue Management: The pb/cbQueueName fields of an operation specifies an invalid or nonexistent  queue. Either the file name, the queue name, or the queue type specified in an AddQueue call is incorrect. To correct the problem, check: - for the file name, check the volume and directory specifications, and check the length of the file specification. File specifications cannot exceed 92 characters. - for the queue name, check to see if it is less than 50 characters long - for a queue type, make sure that it is a value between 0 and 255.Queue Management: An EstablishQueueEntry operation was invo ked when 100 server processes were already established.Queue Management: A Marking operation was invoked by a server process that had not invoked an EstablishQueueServer operation.Queue Management: An AddQueueEntry operation was attempted with the fQueueIfNoServers flag set to FALSE when no server processes were established.Queue Management: A DeleteMarkedQueueEntry, UnmarkQueueEntry, or RewriteMarkedQueueEntry operation was invoked with an invalid Queue Entry Handle.Queue Management: A DeleteMarkedQueu eEntry, UnmarkQueueEntry, or RewriteMarkedQueueEntry operation was invoked by a server process other than the server process that marked the entry.Queue Management: A syntax error was found in the Queue Index File.Queue Management: An AddQueueEntry operation specifies a queue type that does not match the queue type in the Queue Index File.Queue Management: An AddQueueEntry operation was invoked with an invalid date/time specification.Queue Management: The service (formerly called server) process specifi ed in an EstablishQueueServer operation is already established as a service.Queue Management: The queue table is full. Either reduce the number of queues or reinstall the Queue Manager with a larger maximum number of files.Queue Management: The queue handle in the request was unrecognized.Queue Management: An attempt was made to remove a queue that is no longer in service.Queue Management: An attempt was made to install a queue with a file specification matching that of a queue already in service.Queue  Management: An attempt was made to install a queue with a file specification matching that of a queue already in service.Queue Management: DeterminQueNum marked as net-routable a request that ReRouteCommand refuses to reroute across the net. This is an internal error that indicates a problem in the software you are using.Queue Management: An attempt was made to install the Queue Manager with an illegal installation parameter.Queue Management: An attempt was made to deinstall the Queue Manager running  in a single partition environment.Queue Management: The loadable request file was either missing or was the wrong version.Queue Management: An attempt was made to install from a partition other than the primary partition. (For GPS releases prior to 2.0)Queue Management: The Queue Manager is in an inoperative state and will accept only a deinstall request. (For GPS releases prior to 2.0)Queue Management: This is an internal error that indicates a problem in the software you are using. (For GPS release  s   Formatting operator overflow.OFIS Designer, OFIS Writer: <  Wrong video.OFIS Designer, OFIS Writer: Formatting operator too big.OFIS Designer, OFIS Writer: Bad formatting operator.OFIS Designer, OFIS Writer: Cannot resolve place.OFIS Designer, OFIS Writer: Too many bins.OFIS Designer Release 1.0, OFIS Writer: Virtual memory lock.OFIS Designer, OFIS Writer: Bad file format.OFIS Designer, OFIS Writer: Bad file version.OFIS Designer Release 1.0, OFIS Writer: Virtual memory read only buffer.OFIS Designer Release 1.0, OFIS Writer: Virtual memory dirty page undeH rflow.OFIS Designer, OFIS Write: Data segment allocation error.OFIS Designer, OFIS Writer: Bad file number.OFIS Designer, OFIS Writer: Bad style. Try removing some of the formatting attributes (headers, footers, indents, etc.) and then save.OFIS Designer, OFIS Writer: Back memory allocation error.OFIS Designer, OFIS Writer: No free buffer pointer.OFIS Designer, OFIS Writer: Spooler disk full.OFIS Designer, OFIS Writer: prior to 2.0)Queue Management: Duplicate Service A queue service (formerly called server) attempted to mark or unmark a queue entry in a queue that was established by another service with the fUniqueServer flag set to TRUE. (For GPS releases prior to 2.0)Queue Management: Queue File Overflow. The Queue Manager cannot expand the queue file because queue entry forward links would be too large to store in 16 bytes. This status code is returned by the operation AddQueueEntry. (For GPS releases prior to   2.0)Queue Management: Forward Request Failed. An attempt was made to forward a request to a Queue Manager residing on a remote node and the attempt failed. This usually occurs because the Queue Manager on the remote node is not installed or because network software is not installed. (For GPS releases prior to 2.0)Queue Management: Request Forwarded. This is an internal Queue Manager error and should never be seen by an application or user. If you do receive this status code, call the Unisys Customer   Support Center. (For GPS releases prior to 2.0)Reserved.Debugger: Cannot convert from simple mode to multiprocess mode To enter multiprocess mode, you must first exit the Debugger and then press ACTION-B.Debugger: Not enough memory The Debugger needs approximately 55Kb of memory to be able to enter multiple-process mode or to set CODE-I breakpoints.Debugger: Cannot deactivate Debugger You cannot deactivate the Debugger while CODE-I breakpoints are set or while a breakpoint has just executed. To dea ctivate the Debugger, first remove all CODE-I breakpoints and/or proceed (single step) from the breakpoint.Debugger: Breakpoint already set A previous CODE-B command already set a breakpoint at the specified address.Debugger: Debugger crash A fatal internal error has occurred. You will have to reboot (turn machine off and on or press the RESET button).Debugger: The Debugger is not installed. The Debugger is not installed on the system. Possible causes of this problem include: - The operating system$  was customized without the resident part of the Debugger. Therefore, configuration file options have no effect. - The configuration file for the processor specifies that the Debugger is not to be loaded. Refer to the System Administration Guide. - The appropriate [Sys]DebuggerXXX.sys file (where XXX is the designation for the specific hardware) is missing or corrupt. Check the contents of PLog. - The system does not have enough memory available to load the [Sys]DebuggerXXX.sys file. Check 0 the contents of PLog. - The operating system is not compatible with the [Sys]DebuggerXXX.sys file. Check the contents of PLog.Reserved.OFIS Designer, OFIS Writer: Bad keyboard message.OFIS Designer, OFIS Writer: No more documents. Save more often in a session.OFIS Designer, OFIS Writer: No more windows.OFIS Designer, OFIS Writer: Cannot locate place.OFIS Designer, OFIS Writer: No more display line descriptors.OFIS Designer, OFIS Writer:  Too many user parameters.OFIS Designer, OFIS Writer: Bad font.OFIS Designer, OFIT S Writer: Format set initialization error.OFIS Designer, OFIS Writer: Sort error.OFIS Designer, OFIS Writer: Cannot deallocate.OFIS Designer, OFIS Writer: No free attribute.OFIS Designer: Bad anchor header.OFIS Designer 1.0: Index not available. OFIS Designer Release 2.0, OFIS Writer: Merge too large.OFIS Designer 1.0: Internal index full. OFIS Designer Release 2.0: No more fonts.OFIS Designer 1.0: Word already in index. OFIS Designer Release 2.0: No font service.OFIS Designer, OFIS Writer: C` annot register character pointer.OFIS Designer, OFIS Writer: Character pointer not registered.OFIS Designer, OFIS Writer: Bad document.OFIS Designer, OFIS Writer: End of typescript file. Recover the session and cancel recovery before the operation that caused the error.OFIS Designer, OFIS Writer: Indexed document has bad pointer.OFIS Designer, OFIS Writer: Indexed document has bad delta character pointer.OFIS Designer, OFIS Writer: Indexed document has bad hash code.OFIS Designer, OFIS Writer: Indexl ed document has bad character pointer.OFIS Designer, OFIS Writer: Indexed document has bad index phrase.OFIS Designer, OFIS Writer: Indexed document has bad count of bytes.OFIS Designer, OFIS Writer: Character pointer too large.OFIS Designer, OFIS Writer: Typescript synchronization error.OFIS Designer, OFIS Writer: Stack overflow.OFIS Designer, OFIS Writer: No more index headers.OFIS Designer, OFIS Writer: Negative white space.Reserved.OFIS Designer, OFIS Writer: Memory low.OFIS Designer, OFIS Writex  r: Macro stack empty.OFIS Designer, OFIS Writer: Macro stack full.OFIS Designer, OFIS Writer: Bad macro file.OFIS Designer, OFIS Writer: Bad macro.OFIS Designer, OFIS Writer: Bad macro state.OFIS Designer, OFIS Writer: Typescript checksum error.OFIS Designer Release 2.0: Math: Undefined variable.OFIS Designer Release 2.0: Math: String expected.OFIS Designer Release 2.0: Math: Selected text too long.OFIS Designer Release 2.0: Math: String length exceeded.OFIS Designer Release 2.0: Bad typescri"  pt.OFIS Writer and other applications: Bad heap call. The internal heap check, which is performed when doing a heap manipulation, has determined that the heap is not consistent with itself. This message may be returned by application products that share code pertaining to the heap. Heap errors can occur when you open, close, and delete a number of files, causing an internal memory management error. Reopen the application and recover. OFIS Designer Release 2.0: Index not available.OFIS Writer and ot$  her applications: Bad heap free space count. The internal heap check, which is performed when doing a heap manipulation, has determined that the heap is not consistent with itself. This message may be returned by application products that share code pertaining to the heap. Heap errors can occur when you open, close, and delete a number of files, causing an internal memory management error. Reopen the application and recover. OFIS Designer Release 2.0: Index not available.OFIS Writer and other appli&  cations: Bad heap limits. The internal heap check, which is performed when doing a heap manipulation, has determined that the heap is not consistent with itself. This message may be returned by application products that share code pertaining to the heap. Heap errors can occur when you open, close, and delete a number of files, causing an internal memory management error. Reopen the application and recover. OFIS Designer Release 2.0: Word already in index.OFIS Writer and other applications: Bad hea(  p node sequence. The internal heap check, which is performed when doing a heap manipulation, has determined that the heap is not consistent with itself. This message may be returned by application products that share code pertaining to the heap. Heap errors can occur when you open, close, and delete a number of files, causing   stry. An internal memory management error has occurred. If you observe such an error, report it to your Unisys representative.OFIS Designer, OFIS Writer, Development Utilities: No node backpointers. An internal memory management error has occurred6 . If you observe such an error, report it to your Unisys representative.OFIS Designer, OFIS Writer, Development Utilities: No free node backpointer. An internal memory management error has occurred. If you observe such an error, report it to your Unisys representative.OFIS Designer, OFIS Writer, Development Utilities: Node not busy. An internal memory management error has occurred. If you observe such an error, report it to your Unisys representative.OFIS Designer, OFIS Writer: Node not free. An in9 ternal memory management error has occurred. If you observe such an error, report it to your Unisys representative.OFIS Designer, OFIS Writer: Node not on free list.OFIS Designer, OFIS Writer: Cannot register selection.OFIS Designer, an internal memory management error. Reopen the application and recover.OFIS Writer and other applications: Bad heap signature. The internal heap check, which is performed when*   doing a heap manipulation, has determined that the heap is not consistent with itself. This message may be returned by application products that share code pertaining to the heap. Heap errors can occur when you open, close, and delete a number of files, causing an internal memory management error. Reopen the application and recover.OFIS Writer and other applications: Heap full. Cannot complete operation (allocate or grow a heap node, or shrink the heap) because there is insufficient free space remai, ning in the heap. This message may be returned by application products that share code pertaining to the heap. Heap errors can occur when you open, close, and delete a number of files, causing an internal memory management error. Reopen the application and recover. Save your changes more often.OFIS Designer, OFIS Writer: Node backpointer not found.OFIS Designer, OFIS Writer: Bad node address.OFIS Designer, OFIS Writer: Bad node backpointer.OFIS Designer, OFIS Writer: Bad node count of register poi. nters.OFIS Designer, OFIS Writer: Bad binary-coded decimal (BCD) number.OFIS Designer, OFIS Writer: Bad BCD operator.OFIS Designer, OFIS Writer: Divide BCD by zero.OFIS Designer, OFIS Writer: BCD must be integer.OFIS Designer, OFIS Writer: A BCD number is expected.OFIS Designer, OFIS Writer: A BCD operator is expected.OFIS Designer, OFIS Writer: BCD is too complex.OFIS Designer, OFIS Writer: BCD has unmatched brackets.OFIS Designer, OFIS Writer: Document in use.OFIS Designer, OFIS Writer: No such 0 document.OFIS Designer, OFIS Writer, Development Utilities: Bad heap node pointer. An internal memory management error has occurred. If you observe such an error, report it to your Unisys representative.OFIS Designer, OFIS Writer, Development Utilities: Bad node link. An internal memory management error has occurred. If you observe such an error, report it to your Unisys representative.OFIS Designer, OFIS Writer, Development Utilities: Bad node tag. An internal memory management error has occurred. 2  If you observe such an error, report it to your Unisys representative.OFIS Designer, OFIS Writer, Development Utilities: Count of register pointers node overflow. An internal memory management error has occurred. If you observe such an error, report it to your Unisys representative.OFIS Designer, OFIS Writer, Development Utilities: Count of register pointers node underflow. An internal memory management error has occurred. If you observe such an error, report it to your Unisys representative.OFIS Des4 igner, OFIS Writer, Development Utilities: Dangling node backpointer. An internal memory management error has occurred. If you observe such an error, report it to your Unisys representative.OFIS Designer, OFIS Writer, Development Utilities: Double node regi OFIS Writer: Bad soft key piece number. Document Designer: Cannot Unregister selection; selection was not registered.OFIS Designer, OFIS Writer: Print job failed.OFIS Designer Release 1.0: Reserved. OFIS Designer Release 2.0: Bad soft key piece number.Reserved.OFIS D; esigner Release 1.0: Reserved. OFIS Designer Release 2.0: Bad help version.OFIS Designer, OFIS Writer: Merge too large.OFIS Designer, OFIS Writer: Bad help version.Reserved.Caching: Cache miss. CacheGetEntry and RemoteGetCacheEntry return this status code if the specified cache ID was not found in the cache and a new cache entry was created (for example, by replacing the LRU cache entry with the new ID).Caching: Cache entry locked. CacheGetEntry and RemoteGetCacheEntry return this status code if th = e specified cache ID was found in the cache but is currently locked (busy).Caching: No free cache entry. CacheGetEntry and RemoteGetCacheEntry return this status code if the specified cache ID was not found in the cache and no new LRU cache entry is available to be replaced.Caching: Cache hit deferred. CacheGetEntry returns this status code if the specified cache ID was found in the cache, is unlocked, and the caller has asserted the defer hit bit in the CacheGetEntry flags parameter.Caching: Remote Ca,? che request in progress. The Remote Cache service returns this status code to indicate that a request has been queued internally. This status code is for internal operating system use only; it is not returned to applications.Caching: Bad Remote Cache handle. The Remote Cache service returns this status codes if the handle supplied in a request is no a valid handle obtained through RemoteCacheOpen.Caching: Invalid Remote Cache parameter. The Remote Cache service returns this status code if a cb in a re8A quest block has an illegal value.Caching: No free Remote Cache descriptor. The Remote Cache service returns this status code if its internal descriptor supply has been exhausted. Reinstall the Remote Cache service with a larger value for nDescriptors.Caching: No such Remote Cache pool. RemoteCacheOpen returns this status code if a cache with the specified name does not exist.Caching: Bad cache handle. The cacher primitives return this status code if the handle supplied in a call is not a valid handleDC  obtained through CacheInit.Caching: No such cache entry. CacheGetStatus reutrns this status code if the specified cache ID does not exist.Caching: Bad cache descriptor. The cacher primitives return this status code if the cache entry handle supplied in a call does not specify a valid cache entry.Caching: No cache pool. LockInCache and UnlockInCache if the File Cache Service has not been installed.Caching: Cache miss. LockInCache returns this status code if the number of replaceable entries in the FPE ile Cache would fall below the Minimum Working Set established in the system configuration file. The cacher primitives return this status code if there is not sufficient space in the cache to satisfy a request.Caching: Cache pool busy. CacheClose returns this status code if the specified cache has outstanding locked entries. These entries need to be released by calling CacheReleaseEntry.Caching: Cache disabled. LockInCache returns this status code if the specified fiel handle is cache-disabled. Cac\G hing is disabled by SetFileStatus on a per-file or per-volume basis; caching is disabled in the entire system through the system configuration file.Caching: Bad cache control word. The cacher primitives return this status code if the controlValue and/or controlMask parameters in a call are illegal.Caching: Remote Cache pool busy. RemoteCacheClose returns this status code if the specified cache has outstanding locked entries. These entries must be released by calling RemoteCacheReleaseEntry.Caching: BahI d Remote Cache control word. The Remote Cache service returns this status code if the controlMask and/or controlValue parameters in a reques  n problem with the software you are using. If you observe such an error, report it to Technical Support.Editor: Node not free. Problem encountered in allocating a segment of the heap. This is an internal memory management error, indicating an problem with the software you are using. If you observe such an error, report it to Technical Support.Editor: Next tag bad. The next used heap segment indicator is invalid. This is an internalW # memory management error, indicating an problem with the software you are using. If you observe such an error, report it to Technical Support.Editor: Previous tag bad. The previous used heap segment indicator is invalid. This is an internal memory management error, indicating an problem with the software you are using. If you observe such an error, report it to Technical Support.Editor: Next node not free. The next free heap segment was incorrectly marked as being free. This is an internal memory maY $nagement error, indicating an problem with tht are illegal.Caching: Duplicate Remote Cache descriptor. RemoteCacheControl returns this status code if an attempt is made to define a duplicate cache pool or client.Caching: Bad Remote Cache descriptor. The Remote Cache service returns this status code if the cache entry handle supplied in a request does not specify a valid cache entry.Caching: Bad Remote Cache tK buffer size. RemoteCacheOpen returns this status code if the open mode is mode MassIo and the cache buffer size is not a multiple of 4096 bytes (a Mapper page). The BlockSize in a RemoteCachePool parameter in the system configuration file is incorrect.Caching: Bad cache buffer size. A SetFsConfigParams request specified a file cache whose buffer size is not a multiple of 512 (a disk sector). The BlockSize in a FileCacheService parameter in the system configuration file is incorrect.Caching: Cache pagM e unlockable. LockInCache returns this status code if a portion of disk cannot be locked into the File Cache because of a disk media defect.Reserved.Intra-Segment Heap Manager: Heap too small. Internal error. IntraSegHeapInit returns this status code if the cbHeap parameter is too small.Intra-Segment Heap Manager: Heap full. Internal error. IntraSegHeapAlloc returns this status code if the fNoWait parameter is asserted and there is insufficient space in the specified heap to satisfy the allocation.O  The Intra-Segment Heap Manager is an internal operating system facility. This status code may result from a request if the request is spec-routed, the requester is a system service or interrupt procedure, and the heap used for spec-expansion is full.Intra-Segment Heap Manager: Bogus node. Internal error. IntraSegHeapDealloc returns this status code if a corrupt heap node is detected.Reserved.Editor: Bad keyboard message.Editor: No more documents. Save more often in a session.Editor: No more windoQ  ws.Editor: Wrong video.Editor: Cannot resolve place.Editor: Virtual memory lock.Editor: Virtual memory read only buffer.Editor: Virtual memory dirty page underflow.Editor: Bad file number.Editor: Bad document.Editor: Stack overflow.Editor: The Editor nationalization file, [Sys]EditorMsg.sys, does not match the Editor run file. This usually indicates that the two files are from two different Standard Software releases. The nationalization file may be corrupt.toReserved.Editor: Heap full. ThS !ere is not enough memory for allocation. This is an internal memory management error, indicating an problem with the software you are using. If you observe such an error, report it to Technical Support.Editor: Node not busy. A problem was encountered in compacting the heap or freeing a segment of the heap. This is an internal memory management error, indicating an problem with the software you are using. If you observe such an error, report it to Technical Support.Editor: Bad signature. The heap is U "corrupted. This is an internal memory management error, indicating a e software you are using. If you observe such an error, report it to Technical Support.Editor: Next node bad link. The link to next free heap segment is invalid. This is an internal memory management error, indicating an problem with the software you are using. If you observe such an error, report it to Technical Support.Editor: Not on free list. The free heap segment is incorrectly marked as being free. This is an internal memory management error, indica[ %ting an problem with the software you are using. If you observe such an error, report it to Technical Support.Editor: Bad tag. The free/used heap segment indicator is invalid. This is an internal memory management error, indicating an problem with the software you are using. If you observe such an error, report it to Technical Support.Editor: Bad node size. The heap segment size is incorrect. This is an internal memory management error, indicating an problem with the software you are using. If you ] &observe such an error, report it to Technical Support.- 2304 Reserved.Sequential Access Method: Too many put backs. Only one PutBackByte is allowed before reading again.Reserved.Sequential Access Method: Invalid mode to OpenByteStream. Valid modes are: ModeRead, ModeWrite, ModeAppend, ModeModify, and ModeText.Reserved.Sequential Access Method: Invalid BSWA. A Byte Stream operation was made with an invalid BSWA. Either the operation is not valid for the Byte Stream, the BSWA was modified erroneously_ ' by the user, or the BSWA passed was never opened.Reserved.Sequential Access Method: Buffer too small. Buffer must be 1024 bytes to allow device independence.Sequential Access Method: Invalid video byte stream escape sequence.Reserved.Sequential Access Method: ReadStatusC or WriteStatusC parameter error. The status mask selects an undefined status bit, or an attempt was made to write a bit that can only be read, or vice versa.Sequential Access Method: Parity error detected. All bytes, except the laa (st one returned from the read operation, were received without error. The last byte is in error and has not been examined or translated in any way (by CR/LF translation or EOF checking, for example). That character is treated as if the byte stream were in image mode.Sequential Access Method: Receive overrun (detected by the serial controller hardware). All bytes, including the last one returned from the read operation, were received without error. One or more bytes were lost after the last byte. This d )error indicates that the serial controller hardware overflowed its internal three-byte buffer because the interrupt service routine did not run soon enough to unload the controller. Unless the system is very heavily loaded with high-frequency communications interrupts at the time, this is probably just an interrupt latency (patience) problem, the fault of some software component that is keeping interrupts disabled for too long a period. Otherwise, the code of the interrupt service routine needs to be opf *timized. Start by rewriting it as a raw ISR if it is not one already. (Note the difference between this error and 2346.)Sequential Access Method: Framing error detected. All bytes, except the last one returned from the read operation, were received without error. The last byte is in error and has not been examined or translated in any way (by CR/LF translation or EOF checking, for example). That character is treated as if the byte stream were in image mode. (Typically the character is garbage.)Sequenh +tial Access Method: Wrong configuration type. The specified configuration file is not of the type expected for the device specified.Sequential Access Method: Invalid configuration file. There was an error in accessing the appropriate configuration file. Either the specified configuration file (or the default if one was not specified) does not exist or an error was encountered when trying to read the file.Sequential Access Method: This status code indicates one of  ns are independent and may overlap in time. For example, the caller will not get ercWrongTimeToCall from a Flupv 2shBufferC operation while waiting for a message signaling the end of a FillBufferAsyncC operation.Sequential Access Method: All bytes, including the last one returned from the read operation, were received without error. A break signal was received after the last byte returned was received. This code can be treated in the same way as ercOk if the break signal is not significant to the application.X.25 Network Gateway: Packet level error occurred during operation. If a packet level error occurs during a|x 3 byte stream operation, the call is cleared, but the byte stream is not closed. A ReleaseByteStream or CloseByteStream operation must be implemented to close the byte stream.X.25 Network Gateway: Time out. The specified time out elapsed before the X.25 Network Gateway system service operation could finish. The operation in question is terminated, but the call is not clea the following, depending on operating (j ,conditions: - The translation file is bad. - The specified open bytestream does not exist.Sequential Access Method: Receive overrun (detected by software). All bytes, including the last one returned from the read operation, were received without error. One or more bytes were lost after the last byte. This error indicates that the interrupt service routine overflowed its receive buffer, because the application process did not call soon enough to unload the buffer. (Note the difference between this er4l -ror and 2341.) This error may mean that the client of communications byte streams, rather than communications byte streams themselves, is falling behind. Try the following possible remedies, in sequence: - Raise the priority of the receiving process. In a full-duplex situation, make sure that the receiving process runs at a higher priority than the transmitting process. - Use a line control discipline: XON/XOFF unless the data is binary (image mode), or CTS if the hardware connection supports it. Thi@n .s holds off the transmitter while the receiver catches up, then restarts the transmitter. (Refer to the CREATE CONFIGURATION FILE utility description in your Executive Reference Manual.) - Increase the size of the buffer given to OpenByteStream (or OpenByteStreamC or AcquireByteStreamC, whichever interface you are using). This will not help for long if the receiving process keeps on falling behind, but it enables the receiving process to cope with bursts of activity, provided that it can eventually catchLp / up. - Optimize the offending code. This may be the code in the receiving process. The offending code could also be inefficient interrupt service routines, which leave too little bandwidth for the process to use. First check to see that the process is not insisting on receiving a single character at a time. This method is very inefficient. Ask for a larger chunk or a variable-sized chunk, whatever is available at the time you call. - Use a lower baud rate. - Run fewer communications channels on one Xr 0processor simultaneously.Sequential Access Method: Cannot complete operation now. This code indicates that in order to complete the requested operation, the user process would have had to wait, and the caller explicitly denied this by using the asynchronous form of the call (for example, FillBufferAsyncC with nonzero idExch argument). This status code can indicate a normal condition as well as an error. Once this code is returned, the caller must expect a subsequent message notifying him when the blockidt 1ng condition has been removed, at which point he may repeat the call.Sequential Access Method: Wrong time to call. The user previously initiated an asynchronous operation and received the ercCantCompleteNow response. The user may not issue the next operation of the same type until he receives a message indicating that the blocking condition has been removed. Note: Receive and transmit operatio red.Reserved.Parameter Management: No such parameter. In a call to RqParams, the parameter specified exceeds the maximum number of poz 4ssible parameters. Context/Window Manager: This application must be invoked through the Executive; edit the configuration file.Parameter Management: A parameter contains an invalid value. The value passed was not in the range of legal values as determined by the executing application. For example, the application expected a number but was supplied a letter; or the maximum value was 20, and the application received the number 40.Parameter Management: Too many subparameters. The application has rest| 5ricted the number of subparameters that may be entered. Refer to the application's documentation for the maximum number of subparameters.Reserved.Parameter Management: No such subparameter. In a call to RqParams, the subparameter specified exceeds the maximum number of subparameters allowed in the parameter.Parameter Management: A required subparameter was missing.Reserved.Parameter Management: Parameter or subparameter was greater than 255 bytes.Reserved.Parameter Management: VLPB full. The operatio~ 6n failed because the Variable Length Parameter Block could not be extended by allocating long-lived memory.Reserved.Parameter Management: Illegal iParam. The value of iParam supplied to RgParamSetListStart or RgParamSetSimple is not less then CParams.Reserved.Parameter Management: Not in list. An RgParamSetEltNext was invoked after an RgParamSetSimple, or the number of parameters in the list was exhausted.Reserved.Executive Forms: Internal error.Executive Forms: Form too large.Executive Forms: Intern 7al errors.Executive Forms: Invalid form description.Executive Forms: Internal errors.Executive Forms: Wild card expression too complicated.Executive Forms: Buffer too small. The AtFileInit operation returns this status code if the client provides a buffer of less than 800 bytes.Executive Forms: Unexpected macro. In the process of expanding a string message, a macro could not be expanded because no string was supplied. A macro expansion charater was found, but no string was supplied to be substituted 8.Executive Forms: A number was expected after a macro expansion character, but none was found.Executive Forms: Invalid count for expansion. The count of bytes supplied is not valid for this type of expansion.Executive Forms: String too long. The operation AtFileNext returns this status code when it encounters a string in an at-file that exceeds the maximum length of 255 characters. Strings within at-files are separated by white space characters (spaces, tabs), and do not begin with the comment charactĄ 9ers %'.Executive Forms: More than one file matches this file specification. AtFileInit returns this error if it expands a file specification with a wild card character, and finds that a match has occurred for more than one file name. The AtFileInit file specification must be unique.Executive Forms: No file matches this file specification. AtFileInit is unable to successfully expand a file specification with a wild card character.Executive Forms: Uninitialized work area buffer.Executive Forms: UnrecogІ :nized display type.Executive Forms: Not a command file.Executive Forms: No command match. The specified command string does not match any command in the command file, nor is it the abbreviation of any command.Executive Forms: Not a unique command abbreviation. More than one command matches the sequence you entered. Use a more specific command abbreviation.Executive Forms: Invalid Command handle. The command handle is not in the current command file directory.Executive Forms: Resource not found. ܈ ; The specified file is either not a resource or does not contain the indicated resource.Executive Forms: Invalid field type.Executive Forms: Invalid field descriptor size.Executive Forms: Too much choice text. The choice text will not fit into the choice text area on the scree  ates a problem with the software you are using. CT-DBMS: An attempt was made by CT-DBMS to open an ISAM data set with more than 100 indices. This is an internal error that indicates a problem with the software you are using.CT-DBMS, ISAM: ISAM or CT-DBMS is already installed. ISAM: This code is g0 Benerated by the InstallISAM operation or the ISAM INSTALL command if ISAM or CT-DBMS is already installed. CT-DBMS: This code is generated by the DB INSTALL command if ISAM or CT-DBMS is already installed.ISAM: Not enough DGroup Storage. The amount of Data Group storage specified to the ISAM Install command was not sufficient. Internal error.ISAM: Not addressable from DS. The Data Group storage specified to the ISAMInstall operation was not addressable. Internal error.ISAM: No free Isam Control Blo< Ccks. The maximum number of ISAM Control Blocks has been used. Internal error.ISAM: No free ISAM handles. The ISAM data set cannot be opened because the maximum ISAM data sets that cn.Executive Forms: Invalid choice text. The choice text is empty, not alphanumeric, or the first character is not unique.Executive Forms: Form work area too small.Executive Forms: Invalid menu descriptor type.Executive Forms:  < Default form value exceeds the number of choices available.Executive Forms: Too many menu selection.Reserved.Date/Time Conversion: Year is not within the range 1952-2042.Date/Time Conversion: Day is not valid for specified month. Must be 1 to 28/29/30/31, as appropriate for the month.Date/Time Conversion: Date and day of week disagree.Date/Time Conversion: Invalid time of day specification.Date/Time Conversion: Bad date/name index. In a call to GetN1DateName, the iDateName parameter is outside the  =allowable range.Reserved.Direct Access Method: DAWA in use. OpenDaFile failed because the Direct Access Work Area (DAWA) is currently associated with another Direct Access Method file.Direct Access Method: Not readable by Direct Access Method. OpenDaFile failed because the specified file contains records that cannot be read by the Direct Access Method. For example, the file can contain variable-length records.Direct Access Method: sRecords mismatch. OpenDaFile failed because the sRecord parameter did > not match the sRecord specified when the file was created.Direct Access Method: DAM internal error. The operation failed because an internal inconsistency was detected. Consult the Unisys Customer Support Center.Direct Access Method: DAWA invalid. The operation failed because pDAWA specified an invalid DAWA. A DAWA is invalid if it is not recognized as a DAWA or if it is not associated with an open file.Direct Access Method: Invalid record fragment. ReadDaFragment or WriteDaFragment failed because   ?the record fragment exceeds the record bounds.Direct Access Method: Invalid buffer mode. SetDaBufferMode failed because an invalid buffer mode was given.Direct Access Method: Record beyond existing records. The operation failed because the specified record does not exist. This status code is equivalent to ercRecordDoesNotExist (code 3302) except that code 3007 provides this additional information: the record is beyond any existing record.Reserved.ISAM: No such index exists. An operation that include @s a key was invoked, but the specified index does not exist.ISAM: Prefix is not valid. SetUpISAMIterationPrefix was invoked for an index that is neither a byte nor character string.ISAM: Bad key length. The key length is inconsistent with the index type.ISAM: Bad ISAM or data base handle. The ISAM handle does not identify an open ISAM data set.ISAM: Bad ISAM header size. The ISAM data set cannot be opened by the OpenISAM operation due to an inconsistency in the header of one of the files of the data$ A set.ISAM: Bad ISAM header. See erc 3104.ISAM, CT-DBMS: Too many indices. ISAM: An attempt was made to perform an OpenISAM on a data set with more than 100 indices. This is an internal error that indic an be simultaneously opened by all users combined (256) has been reached.ISAM: No free ISAM handles. The maximum number of ISAM Status Blocks have been used. Internal error.ISAM: Buffers are too large. The amount of RAM required by either the data store or index cache buffers exceeds a megabyte.ISAM, CT-DBMS: The pointeH Drs to the cache buffer are corrupt. Internal error.ISAM: ISAM terminated abnormally. Following detection of an internal error, all subsequent ISAM operations and services generate this status code.ISAM: Isam not installed. An ISAM operation was attempted before ISAMInstall was called. Internal error.ISAM: Bad unique record identifier. An incorrect unique record identifier parameter was passed to ISAM.ISAM: Duplicate key. An attempt to store or modify a record would duplicate the key stored in anotT Eher record for the same index, but the index does not allow duplicates.ISAM: Index file error. This status code is returned as the status code of an ISAM operation. The detail status code refers to a problem with the index file of the ISAM data set.ISAM: Attempted privacy breach. An attempt was made to modify a data set that is open in batch read or transaction read mode.ISAM: Bad request. Either the request block is invalid, or the parameters of an operation are inconsistent or have invalid values.I` FSAM: Data store file error. This is returned as the status code of an ISAM operation. The detail status code refers to a problem with the data store file of the ISAM data set.ISAM: Index to data error. An inconsistency has arisen between the index and data store files of the ISAM data set.ISAM: Record size incorrect. The specified record size is incorrect for the ISAM data set.ISAM: Duplicates allowed. An operation specified a unique key parameter (that is, duplicates are not allowed), but the indel Gx allows duplicates.ISAM: No such record exists. A unique key was used to identify a record, but no record is stored in the ISAM data set with that key.ISAM: No more records. A ReadNextISAMRecord(Hold) or GetISAMRecords(Hold) operation has read all the records within the range specified for the current iteration. No record is read when this status code is generated.ISAM: Bad key. Either (1) a key field is longer than 64 bytes or is defined to occupy bytes past the end of the record, or (2) a suppliedx H key is invalid. For example, a DECIMAL key with a digit that is not between 0 and 9 is invalid.ISAM: Bad index. The specified key field does not exist, that is, the iIndex parameter of an ISAM operation is greater than or equal to the number of indexes in the ISAM data set.ISAM: Bad ISAM mode. The mode parameter of the OpenISAM operation is invalid.ISAM: Cannot open ISAM. This is returned as the status code of an OpenISAM operation. The detail status code gives the reason for this failure.ISAM: Ba Id ISAM password. Either the password does not give the access desired by the OpenISAM operation, or the password is larger than the 12 bytes accepted by the SetISAMProtection operation.ISAM: Wrong record size. The OpenISAM operation detects the wrong size record.ISAM: Incompatible ISAM mode. An attempt was made to open a data set when the data set is already open in an incompatible mode.ISAM: ISAM already locked. LockISAM was called on an ISAM data set that was already locked. Internal error.ISAM:  JNot administrator. An operation for which the data set must be open in administrator mode is attempted with the data set open in some other mode.ISAM: Cannot create ISAM. This is returned as the status code of the CreateISAM operation. The detail status code gives the reason for the failure.ISAM, CT-DBMS: Buffer is too small. ISAM: The data set being opened or created requires buffers larger than those installed. CT-DBMS: The relation being accessed requires buffers larger than those installed.ISAM K: Not locked. UnLockISAM was called on an ISAM data set that was not already locked. I   initialize a data base with some files on a workstation other than the one from which DB Initialize was invoked.CT-DBMS, ISAM: Invalid match kind. ISAM: A SetUpISAMIterationLimits operation contained an invalid matchKind argument. CT-DBMS: A SetUpDBIterationLimits operation contained an invalid matchKind argument.ISAM: Service not logging. Usually the result of a version incompatibility between the service and application link library. Internal error.ISAM: Transaction barrier afte Rr modification. An ISAM transaction barrier operation was called after a modification to the data set or data base in the current transaction, but the SetTransactionParams operation was previously invoked with fBarrierAfterModify set to FALSE (0).ISAM: Key is locked. This code is returned as the detail status code when the primary status code is 3143 (Record not available). It indicates that the record was not available because of key locking constraints.CT-DBMS, ISAM: Record is held or tuple is lockednternal error.CT-DBMS, ISAM: Small ISAM record. ISAM: An attempt was made to create an ISAM data set with records shorter than four bytes. CT-DBMS: An attempt was made to initialize a data base with one of the relations having records shorter than four bytes.CT-DBMS, ISAM: Not in transaction. An operation that can be invoked only when the application is in a transaction was invoked while the application was not i Ln a transaction.CT-DBMS, ISAM: Data set or relation is not available. ISAM: An attempt to read or hold a record or to hold a data set failed because the data set was held by another user. CT-DBMS: An attempt to read or lock a record or to hold a tuple or lock a relation failed because the relation was locked by another user.CT-DBMS, ISAM: Record or tuple is not available. ISAM: An attempt to read or hold a record failed because the record was held by another user. CT-DBMS: An attempt to read or lo Mck a tuple failed because the tuple was locked by another user.CT-DBMS, ISAM: Record or tuple is not locked. ISAM: An operation for which the record (or its data set) must be held was invoked when neither the record nor its data set was held. CT-DBMS: An operation for which the tuple (or its relation) must be locked was invoked when neither the record nor its relation was held.CT-DBMS, ISAM: Too many records are locked. An attempt was made to hold a record when the maximum allowable number of records N was already held.CT-DBMS, ISAM: In transaction. BeginTransaction, which can only be invoked when the application system is not in a transaction, was invoked during a transaction.ISAM: Internal error.ISAM: Transaction purged. The application finished a transaction while the request was queued. (This status code is generated only if the application has a request pending when invoking RollBackTransaction or CommitTransaction.)ISAM: Not enough buffers. ISAM Installation was attempted with a configurati̱ Oon file that did not specify at least two buffers and three index buffers. Internal error.ISAM: ISAM Service not available. Internal error.CT-DBMS, ISAM: Data set or relation is not locked. ISAM: An operation for which the data set must be held was called when the data set was not held. CT-DBMS: An operation for which the relation must be locked was called when the relation was locked.CT-DBMS, ISAM: ISAM heap is full. The ISAM or CT-DBMS operation failed because there is not enough room in the ISAس PM or CT-DBMS service's heap to store data structures required by the operation.ISAM: Journal file inconsistency. Illegal clean point after modify. Internal error.CT-DBMS, ISAM: Files are not on same workstation. ISAM: An attempt was made to either create or rename a data set so that the data store and index files would be on different workstations or to open a data set (in other than administrator mode) that is on a different workstation from the one where the ISAM service is running. CT-DBMS: An at Qtempt was made to  S. This code is returned as the detail status code when the primary status code is 3143 (Record or tuple not available). It indicates that the record or tuple was not available because another user had locked it.ISAM: Transaction has been rolled back. The applications current transaction has been rolled back. This status code is returned for every operation by an application after a lock has been broken, until the application invokes the RollbackTransaction operation.ISAM: Journal file error. An error T has occurred during access to a journal file. See the detail error for more information.ISAM: Journal open error. An error has occurred while opening the journal file. See the detail error for more information.ISAM: Journal close error. An error has occurred while closing the journal file. See the detail error for more information.ISAM: Journal write error. An error has occurred while writing to the journal file. See the detail error for more information.ISAM: Journal record illegal. An error U has occurred while reading the journal file during an attempt to roll back a transaction. A record in the journal file has an incorrect format.CT-DBMS, ISAM: Heap not on free list. A supposedly free heap node was not found on the heap's list of free blocks. This indicates an internal error with the software you are using.CT-DBMS, ISAM: Heap bad tag. A heap node contains an incorrect size.This indicates an internal error with the software you are using.CT-DBMS, ISAM: Heap bad node size. A heap n  Vode contains an incorrect node size. This indicates an internal error with the software you are using.CT-DBMS, ISAM: Bad free heap operation. A free heap operation failed due to a bad pointer. This indicates an internal error with the software you are using.CT-DBMS, ISAM: No such key. ISAM: An expected key was not found in a data set. This indicates an internal error with the software you are using. CT-DBMS: An expected key was not found in a relation. This indicates an internal error with the so, Wftware you are using.CT-DBMS, ISAM: Duplicate key. ISAM: An unexpected duplicate key was found in a data set. This indicates an internal error with the software you are using. CT-DBMS: An unexpected duplicate key was found in a relation. This indicates an internal error with the software you are using.ISAM: Bad interior node. An interior node of an ISAM B-tree is corrupt. This indicates an internal error with the software you are using.ISAM:  Heap not on free list. A frontier (leaf) node of an I8 XSAM B-tree is corrupt. This indicates an internal error with the software you are using.ISAM: No more keys. Expected keys were not found. This indicates an internal error with the software you are using.CT-DBMS, ISAM: Bad structure. Some internal structure has become corrupt. This indicates an internal error with the software you are using.CT-DBMS, ISAM: Cache too many files. Too many files are open simultaneously for the cache to handle. This indicates an internal error with the software you aD Yre using.CT-DBMS, ISAM: Cache bad open. An attempt to open a file for caching failed. This indicates an internal error with the software you are using.CT-DBMS, ISAM: Cache bad close. An attempt to close a caching open file failed. This indicates an internal error with the software you are using.CT-DBMS, ISAM: Cache realized in close. Cache object were still realized when an attempt was made to close a cache file. This indicates an internal error with the software you are using.CT-DBMS, ISAM: Bad gP Zlobals. The global variables for the cache have become corrupt. This indicates an internal error with the software you are using.CT-DBMS, ISAM: Bad cache. The cache has become corrupt. This indicates an internal error with the software you are using.CT-DBMS, ISAM: Bad cache realize. An attempt to realize a cache object failed. This indicates an internal error with the software you are using.CT-DBMS, ISAM:    header signature (the ASCII characters am).STAM, ISAM: STAM header invalid checksum. The operation failed because the checksum computed on the file header did n aot match the checksum computed when the file was created.STAM, ISAM: Record does not exist. The operation failed because the specified record does not exist.STAM, ISAM: Malformed record. The operation failed because data read from the disk contained an inconsistency in the record header and trailer. In Sequential Access Method, use the maintain file to fix the database.STAM, ISAM: Not fixed-length record. The operation failed because the access method cannot reference variable-length records.STAM: I bnvalid file type. ISAM: Bad file type. The operation failed because the file cannot be accessed with the specified access method.STAM: Invalid buffer size. ISAM: Bad buffer size. The operation failed because the buffer size was too small or not a multiple of 512.STAM, ISAM: Buffer is not word-aligned. The operation f Bad cache unrealize. An attempt to unrealize a cache object failed. This indicates an in\ [ternal error with the software you are using.CT-DBMS, ISAM: Cache not realized. A cache object that was expected to be realized is not. This indicates an internal error with the software you are using.CT-DBMS, ISAM: Cache object not deleted. A cache object that was expected to be realized is not. This indicates an internal error with the software you are using.CT-DBMS, ISAM: Cache inconsistency. The cache has become corrupt. This indicates an internal error with the software you are using.CT-DBMS, h \ISAM: Cache too small. The cache is too small. This indicates an internal error with the software you are using.CT-DBMS, ISAM: Bad cache check point. A check point operation on the cache failed. This indicates an internal error with the software you are using.CT-DBMS, ISAM: Log DS error. A file system error occurred during an input/output operation to a data store file. The error was recorded in the log file. The detail status code indicates the exact error. This indicates an internal error witt ]h the software you are using.CT-DBMS, ISAM: Log index error. A file system error occurred during an I/O operation to an index file. The error was recorded in the log file. The detail status code indicates the exact error. This indicates an internal error with the software you are using.CT-DBMS, ISAM: Log index to DS error. A file system error occurred during an I/O operation to an index file. The error was recorded in the log file. The detail status code indicates the exact error. This indicates a ^n internal error with the software you are using.CT-DBMS, ISAM: Bad queue request. An internal request used to queue waiting requests failed. This indicates an internal error with the software you are using.CT-DBMS, ISAM: Heap node not busy. A heap node that was expected to be busy is not busy. This indicates an internal error with the software you are using.CT-DBMS, ISAM: Bad heap signature. A heap node has become corrupt. This indicates an internal error with the software you are using.CT- _DBMS, ISAM: Heap node not free. A heap node that was expected to be free is not free. This indicates an internal error with the software you are using.ISAM: Internal heap structures have become corrupt.ISAM: Bad key type. The type field of a key specification for Sort/Merge or ISAM is invalid.ISAM: Incorrect key length. The cbKey field of a key specification for a Sort/Merge or ISAM operation does not correspond to the type field of the key specification. (For example, for binary keys, cbKey mus `t be 2.)ISAM: Bad key. A key contained in a record for Sort/Merge or ISAM, or a key described by a parameter of an ISAM operation is not of the correct type. (For example, each digit of a BCD key must be between 0 and 9.) ISAM: Internal errors.STAM, ISAM: Not a STAM file. The operation failed because the file did not contain the proper file ailed because the buffer was not word-aligned.Internal errors. Consult the Unisys Customer Support Center.Sort/Merge: Cannot open work file. Unable to open one of the work files during c PrepareSort.Sort/Merge: Work area invalid. Unable to allocate work area during PrepareSort.Sort/Merge: Invalid key size. A key passed to ReleaseRecordAndKey is a different length from the length specified in PrepareSort.Sort/Merge: File error during sort. A file error occurred during the sort phase of the program.Sort/Merge: No more records. ReturnRecordAndKey was called after all records were retrieved.Sort/Merge: Error returning record. An error occurred in ReturnRecordAndKey.Sort/Merge: Error d during conclude. An error occurred in ConcludeSort or TerminateSort.Sort/Merge: More records available. ConcludeSort was called before all records were retrieved. To end a sort prematurely, call TerminateSort.Sort/Merge: Record too large. The size of a record is larger than the maximum key size specified in PrepareSort, or the sort area is not large enough.Sort/Merge: Error during sort. An error occurred during DoSort. You may need to increase the Sort work area.Sort/Merge: Insufficient memory.  eNot enough memory was allocated for the sort work area.Sort/Merge: No records to sort. DoSort was called before any records were released.Reserved.Reserved.Sort/Merge: Sort pending. PrepareKeySort was called while a sort was already active.Sort/Merge: No sort pending. A sort procedure other than PrepareKeySort was called before PrepareKeySort.Sort/Merge: Invalid sort key. The key provided is inconsistent with specifications.Sort/Merge: Sort key not in record. A key could not be synthesized from th fis record, given the initial specifications of keys within records.Sort/Merge: Invalid key specification. The key specification in PrepareKeySort is incorrect. It conflicts with the maximum record size provided.Reserved.Sort/Merge: Invalid key specification. The key specification passed to Sort is invalid.Sort/Merge: Non-numeric key length. The length field of the key specification is not numeric.Sort/Merge: Record too large. A record found in the file to be sorted is too large.Sort/Merge: Malform ged record. A record found in the file to be sorted is malformed.Sort/Merge: Invalid key specification. The key specification passed to Merge is invalid.Sort/Merge: Non-numeric key length. The length field of the key specification is not numeric.Sort/Merge: Record too large. A record found in a file to be merged is too large.Sort/Merge: Insufficient memory. There is not enough memory available to perform this merge.Sort/Merge: Sequence break. A sequence break has occurred in one or more of the fil hes being merged. A sort of that file must be performed first.Sort/Merge: Malformed record. A record found in a file to be merged is malformed.Reserved.RSAM: Record Sequential Work Area (RSWA) in use. OpenRsFile failed because the Record Sequential Work Area (RSWA) is currently associated with another RSAM file.RSAM: RSWA invalid. The operation failed because pRSWA specified an invalid RSWA. An RSWA is invalid if it is not recognized as an RSWA or is not associated with an open file.RSAM: RSAM inter inal error. The operation failed because an interval inconsistency was detected.RSAM: Invalid mode. OpenRsFile failed because the mode parameter was invalid.RSAM: Not readable by RSAM. OpenRsFile failed because the specified file cannot be read by RSAM.RSAM: Wrong mode. The mode, which was specified when the file was opened, does not allow the operation to succeed. For example, mode read does not allow WriteRsRecord to succeed.RSAM: Record too large. The record is too large to fit into the buffer s jupplied by ReadRsRecord.RSAM: Good record not found. ScanToGoodRsRecord was unable to locate a well-formed record.RSAM: Bad RSAM logical file address (lfa). The lfa given is within the file header rather than in the range of   itialization buffer that was not correctly formatted.Forms Designer: Input cancelled TypeForm was terminated by a Form cancel function key. No data is returned.Forms Designer: Buffer too small TypeForm or OutForm was supplied with a buffer too small for the size of the data to be returned.Forms Designer: Invalid function key affectation One or mod qre of the function key values passed to FonctForm were invalid.Forms Designer: No input field TypeForm was called on a form containing only protected fields.Forms Designer: No such validation routine The name of the user validation routine associated with the field could not be found in the table generated by the FmValProc.asm module.Forms Designer: Invalid Buffer The value supplied to AddValues is inconsistent.Forms Designer: Value List Too Large For Form Including the user-supplied information wilp rl cause the Form descriptor to exceed its maximum size (8Kb).Forms Designer: Data Truncated In Returned Buffer The user-supplied buthe data.Reserved.Forms Designer: Name not found The form name supplied to OpenForm was not found in the file. Check that the file name and form name are correct. OFIS Imager: Bad Icon Library The OFIS Imager icon library is not found.Forms Designer: Bad object file The fil ke supplied to OpenForm is not a valid object module. The file could be empty. Check that the file name is correct for the form you want.Forms Designer: Form too big The work area supplied to OpenForm is too small to contain the named form. Use the Forms Reporter (FREPORT command) to determine the required work area, and make sure you have allocated enough space.Forms Designer: Form out of bounds The coordinates passed to DisplayForm would result in a part of the form lying outside the frame. Use th( le Forms Reporter (FREPORT command) to determine the required height and width.Forms Designer: Form not displayed A Forms Run-Time service was called for a form that was not displayed. Display the form (use DisplayForm) before attempting any of the Forms Run-Time services.Forms Designer: No such field A Forms Run-Time service was called for a field (specified by pbFieldName, cbFieldName) and index that do not exist. Use the Forms Reporter (FREPORT command) to determine the correct name and index.Form4 ms Designer: Bad type specification A ReadField or WriteField was supplied with a type code that is not defined in your configuration. Examine the source text of FmRgtd.asm for a list of defined type codes.Forms Designer: Bad data size A ReadField or WriteField was attempted in which the cbMax parameter was incorrect for the type of data being returned (for example, a cbMax of three for type Binary). Make sure that the size and type of your data agree. AddValues also returns this error message: - i@ nf the default value to be added is invalid, according to the data control type assigned to the field - if the data for a numeric field is not a valid number (for example, a numeric sign inside a number or a duplicated decimal point) - if the default value for a field defined with a list of values is not equal to the first characters of any values in the listForms Designer: Invalid data You attempted a ReadField or WriteField in which the requested data conversion could not be performed (for example, reaL oding an alphabetic string as type Binary). For ReadField, display an error message and have the user reenter the data. For WriteField, make sure the type of the data you are displaying is correct. AddValues also returns this error message if one or several default values are too large to fit in a field. As a result, AddValues truncates the user-supplied value name, processes all data in the buffer, and, as a warning, returns the last error code encountered.Reserved.Forms Designer: Protected field UserX pFillField was called on a field defined as protected.Reserved.Forms Designer: Invalid initialization buffer EditForm or RestoreForm was supplied with an in ffer is too small to contain all of the returned data. As a result, the system returns the maximum possible valid information and updates CbValuesRet.Reserved.Date/Time: Invalid character in string. The Date/Time constant contains an invalid character.Date/Time: Year is missing from string.Date/Time: Year is out of range. The year specified in the Date/Time constant is n| sot between 1952 and 2041.Date/Time: Month is missing from string.Date/Time: Month is out of range. The month specified in the Date/Time constant is not between 1 and 12.Date/Time: Day of month is missing from string.Date/Time: Day of month is out of range 0 to 31.Date/Time: Day of week is missing from string.Date/Time: Day of week is out of range 0 to 6.Date/Time: Time is missing from string.Date/Time: Minutes are missing from string.Date/Time: Time is out of range.Date/Time: Hour is out of range t. The hour must be between 0 and 23.Date/Time: Minutes are out of range.Date/Time: Day and date disagree.Date/Time: Word in string is not a day, month, am, or pm.Date/Time: Word in string matches more than one day, month, am, or pm.Date/Time: Bad date/time mode.Date/Time: Invalid date/time format.Reserved.ISAM: Cannot auto-restart. Because of a problem with the journal file, auto-restart recovery cannot be used to recover a data base (or one or more ISAM data sets). Recover ISAM data sets by anoth uer mechanism such as restoring archived copies.ISAM: Bad ISAM configuration file An attempt was made to use a file as an ISAM configuration file, but the file has been damaged or it was not generated by ISAM Configure.ISAM: Bad ISAM configuration version. An attempt was made to use an ISAM configuration file that was generated by an incompatible version of ISAM Configure. Regenerate the file by using a compatible version.ISAM: Too many services. An attempt was made to simultaneously open data sets in v more than 16 separate locations.ISAM: Bad Node Specification. An attempt was made to pass an invalid node specifier. Node specifiers consist of node names having 1 to 12 characters between left and right curly brackets: { }. In ISAM, a file specification supplied to OpenISAM, CreateISAM, Rename ISAM, or an ISAM utility contained a malformed BNET node specification. This status code can also occur if a bad node specification was supplied to VerifyMultiUserISAM. If no attempt was made to pass a node  wspecifier to the ISAM operation, this is an internal error. Call the Unisys Customer Support Center.ISAM: You tried to terminate ISAM on a real mode workstation after Context Manager was running. This status code is returned by CTOS 9.0 or older or by an operating system earlier than BTOS II.ISAM: Multiuser ISAM can only be installed on workstations having a local file system. An attempt was made to install multiuser ISAM on a workstation without a local file system.ISAM: Locked Record is read. A rec xord that has been locked by another user has been read. ISAM has a procedural interface that allows you to read locked records for report purposes. This status code is returned to the caller to allow logging of how many records were locked.ISAM: Index key buffer too small. The index key buffer information given by the user application is too small for ISAM service to write up all the information to that buffer, (in GetISAMFile.Status call). ISAM: Internal errors.ISAM: BadUnrealize Dirty occurs if th ye information that should be written to a record to indicate that it is deleted is not written.ISAM: BadUnrealizeCheckB occurs if the CheckB in the record about to be written is incorrect.ISAM: BadUnrealizeURI occurs if the URI in the record about to be written is incorrect.ISAM: BadCheckPointURI occurs if the URI in the record about to be written is incorrect.ISAM: ISAM cannot be deinstalled while running in protected mode.ISAM: CLog handles corrupt. The internal count of the number of ISAM services  z currently active has become corrupt.  CompileDBView operation . The detail status code gives the reason for the failure.CT-DBMS: Cannot access view. The user attempted to compile a view for which the user has no access rights.CT-DBMS: Cannot open view. This is the status code for a CompileDBView operation. The detail status code gives the reason for the failure, which resulted from the attempt to open the files of the viewed relation.CT-DBMS: Cannot compile index. This is the status code for the CompileDBIndex operation. The detail status codes gives the rea$ son for the failure.CT-DBMS: Data base directory error. This is the status code for the OpenDB operation. The detail status code refers to a problem with the directory of data bases.CT-DBMS: Data base directory already open. This is an internal error that indicates a problem in the software you are using.CT-DBMS: Data base directory was accessed before it was open. This is an internal error that indicates a problem in the software you are using.CT-DBMISAM: Heap is too small. The heap size specified by the configuration file is too small. The heap must be at least 6Bh bytes.ISAM: Heap is not addressable. The heap is not addressable as part of the data segment. This status code is used with protected mode operating system and the 80286/80386 processor.ISAM: Bad heap selector. A pointer to a heap node has become corrupt.ISAM: Cannot find service. An internal table of currently active ISAM has become corrupt.IS  {AM: Malformed unrealize. An unrealizable operation preformed on the cache is inconsistent.Reserved.ISAM: Not multipartitioned operating system. An attempt was made to deinstall the ISAM Service on an operating system that is not a multipartioned operating system.ISAM: Service is not on the same workstation. The ISAM Terminate procedure was attempted from a remote workstation.ISAM: Service is is use. The ISAM Terminate procedure was attempted when the ISAM Service was still in use by application syst  |ems.ISAM: Completion by auto-restart. This error is used during auto-restart to correct the journal file that has become corrupt as a result of a system failure.ISAM: Rollforward inconsistency. An error has occurred when replaying the journal file during a recover operation.ISAM: Rollback inconsistency. An internal error has occurred during a rollback operation. Consult the Unisys Customer Support Center.ISAM: Rollback not legal. An attempt was made to rollback a data base where rollback was not  }possible.CT-DBMS: Invalid CT-DBMS request. Either the request block is invalid, or the parameters of a CT-DBMS operation are inconsistent or have invalid values.CT-DBMS: Invalid CT-DBMS mode. The mode parameter of the OpenDB operation is invalid.CT-DBMS: Cannot open data base. This is the status code for an OpenDB operation. The detail status code gives the reason for the failure.CT-DBMS: Incompatible CT-DBMS mode. An attempt was made to open a data base when the data base was already open in an ~ incompatible mode.CT-DBMS: Unable to create data base. This is an internal error that indicates a problem in the software you are using.CT-DBMS: Data base off-line. An attempt was made to open a data base with a mode other than administrator mode when the data base was off-line.CT-DBMS: Data base undamaged. Because of a serious hardware or software malfunction, the data base may contain invalid data or file structures. The data base administrator must repair the data base and place it back on line b  efore it can be accessed by application systems.Internal CT-DBMS utility error. An internal error has occurred in one of the CT-DBMS utilities.CT-DBMS: Data dictionary error. This status code is returned for a CT-DBMS operation. The detail status code refers to a problem with the data dictionary of the data base.CT-DBMS: No such data base. An attempt was made to open a data base that has not been initialized by DB Initialize.Cannot compile view. This is the status code for the  S: Unable to access data base directory. This0  is an internal error that indicates a problem in the software you are using.CT-DBMS: Invalid view identifier. The view identifier does not identify a compiled view for the data base.CT-DBMS: Tuple size incorrect. The tuple size specified is incorrect for the view.CT-DBMS: View access denied. An attempt was made to use a view for a CT-DBMS operation, but the user does not have the required access rights. For example, ModifyDBTuple is called with a particular view, but the user has only read acces< s to one or more attributes in the view.CT-DBMS: View/Index mismatch. This is the status code returned by a CT-DBMS operation that has both viewId and indexId parameters. The view identifier is for a view of one relation, and the index identifier is for an index of a different relation.CT-DBMS: Invalid index identifier. The index identifier does not identify a compiled index for the data base.CT-DBMS: Key record size incorrect. The size of the key record specified is incorrect for the index.CT-DBH MS: Index access denied. To compile an index, the user must have read access to the view used as well as read access to all the attributes of the index. (The view used may contain only some of the attributes used in the index.) The DeleteDBTupleByKey operation also returns this status code if the user does not have the right to delete tuples in the relation.CT-DBMS: Partial key for unique index. An attempt was made to compile an index with "UNIQUE" specified, but not all of the attributes of the inT  dex were included in the index specification.CT-DBMS: Index not unique. This is returned by ReadDBTupleByKey, DeleteDBTupleByKey, and ModifyDBTupleByKey operations. The index used was not compiled as a "UNIQUE" index.CT-DBMS: Null not allowed. An attempt was made to modify or store a tuple so that it would contain a null value for an attribute defined in the schema as not allowing null values.CT-DBMS: Invalid data for type. An attempt was made to modify or store a tuple with an invalid value `" for an attribute, such as a variable-length string with a length not allowed by the schema, or a DECIMAL key with a digit larger than 9.CT-DBMS: Invalid prefix specification. SetUpDBIterationPrefix was called with an invalid cAttrPrefix or cbPrefix parameter.CT-DBMS: Invalid SELECT key word. Syntax error in SELECT clause of view specification.CT-DBMS: Invalid relation name. Syntax error in the relation name in a view specification.CT-DBMS: Invalid relation name. Syntax error in an attribute name il$ n a view specification.CT-DBMS: Invalid domain. Syntax error in the domain specification for an attribute in a view specification.CT-DBMS: Invalid length of domain. Invalid length in the domain specification for an attribute in a view specification.CT-DBMS: Invalid maximum length of string. Invalid maximum length in the domain specification for a variable length BYTE or CHARACTER string attribute in a view specification.CT-DBMS: Invalid DEPENDING ON attribute. The attribute on which a variable lengtx& h BYTE or CHARACTER string attribute depends is either missing from the view specification, or is not declared as a BINARY attribute in the view specification.CT-DBMS: Missing parenthesis. A parenthesis is missing in a view or index specification.CT-DBMS: Missing square bracket. A bracket is missing in a view specification.CT-DBMS: Missing comma. A comma is missing in a view or index specification.CT-DBMS: Invalid index key word. A syntax error occurred in an index specification. The specification ( does not exist in the data base.CT-DBMS: No such relation. The relation named in a view specification does not exist in the data base.CT-DBMS: No such attribute. The index or view specification refers to an attribute that does not exist in the relation.CT-DBMS: Incorrect domain for attribute. The domain specified for an attribute in a view specification diffe  ates a problem in the software you are using.CT-DBMS: An error occurred trying to open root file 03. This is an internal error that indicates a problem in the software you are using.CT-DBMS: The data file for s6 ome relation already exists.  This is an internal error that indicates a problem in the software you are using.CT-DBMS: An error occurred trying to open the data file for some relation in the data base. This is an internal error that indicates a problem in the software you are using.CT-DBMS: The index file for some relation already exists. This is an internal error that indicates a problem in the software you are using.CT-DBMS: An error occurred trying to open the index file for some relation in the da8 ta base. This is an internal error that indicates a problem in the software you are using.CT-DBMS: Root file 00 already exists. This is an internal error that indicates a problem in the software you are using.CT-DBMS: An error occurred trying to open root file 00. rs from that specified in the schema of the data base.CT-DBMS: Data dictionary for the data base is corrupt. This is an internal error that i* ndicates a problem in the software you are using.CT-DBMS: No such index. The index specified by an index specification is not defined in the schema.CT-DBMS: Index definition inconsistency. The index specification is inconsistent with the definition of the index in the schema. Either the UNIQUE/DUPLICATES clause or the NULL IS INDEXED clause is inconsistent.CT-DBMS: ASCENDING or DESCENDING incorrect. One attribute of a index is defined in the schema to be sorted in the reverse order from that specif, ied in the index specification.CT-DBMS: Too many attributes for index. An index specification includes an attribute that is not defined in the index the same way it is defined in the schema.CT-DBMS: Invalid attribute for the index. An index specification includes an attempt that is not defined in the index the same way it is defined in the schema.CT-DBMS: Attribute not in view. An index specification includes an attribute that does not appear in the view used.CT-DBMS: No free data base handles. The . maximum number of data bases and ISAM data sets that can be opened simultaneously by all users combined is 1023. This number has now been reached and the data base cannot be opened.CT-DBMS: DB Initialize's internal memory space is full. This is an internal error that indicates a problem in the software you are using.CT-DBMS: DB Initialize symbol table overflow. This is an internal error that indicates a problem in the software you are using.CT-DBMS: DB Initialize's internal memory workspace is fragmen0 ted. This is an internal error that indicates a problem in the software you are using.CT-DBMS: Cannot initialize the data base from its schema. A generic error related to a data base environment that prohibits DB Initialize from successfully completing its task. The data base is probably not on line.CT-DBMS: Error in list file parameter passed to DB Initialize. The file name passed as the list file to DB Initialize has failed to be interpreted as a valid parameter.CT-DBMS: Cannot open a root file dur2 ing DB Initialize. An attempt to create or open a root file has failed.CT-DBMS: An error occurred trying to open root file 07. This is an internal error that indicates a problem in the software you are using.CT-DBMS: Root file 01 already exists. This is an internal error that indicates a problem in the software you are using.CT-DBMS: An error occurred trying to open root file 01. This is an internal error that indicates a problem in the software you are using.CT-DBMS: Root file 05 already exists. T4 his is an internal error that indicates a problem in the software you are using.CT-DBMS: An error occurred trying to open root file 05. This is an internal error that indicates a problem in the software you are using.CT-DBMS: Root file 03 already exists. This is an internal error that indic This is an internal error that indicates a problem in the software you are using.CT-DBMS: The journal file specified to DB Initialize already exists. This is an internal error that indicates a problem in the software you are using.CT-DBM: S: An error occurred trying to open the journal. This is an internal error that indicates a problem in the software you are using.CT-DBMS: The data file for some relation already exists. This is an internal error that indicates a problem in the software you are using.CT-DBMS: The index file for some relation already exists. This is an internal error that indicates a problem in the software you are using.CT-DBMS: DB Initialize's internal memory space is corrupt. This is an internal error that indi< cates a problem in the software you are using.CT-DBMS: User file, symbol table overflow. This is an internal error that indicates a problem in the software you are using.Reserved.CT-DBMS: Data base in use. The data base is currently being used by a CT-DBMS utility. If this error is returned by a utility, the data base may be in use by an application system.CT-DBMS: Missing index name. An index specification for which no attributes are specified requires an index name.CT-DBMS: File is not a CT-DB? MS configuration file. DB Install was invoked with a configuration file.CT-DBMS: CT-DBMS configuration file wrong version. This is the status code for a CompileDBView operation. The detail status code gives the reason for the failure, which resulted from the attempt to open the files of the viewed relation.CT-DBMS: CT-DBMS configuration file error. This is an internal error that indicates a problem with the software you are using.CT-DBMS: User file error. An error has occurred in the verificationA  of this user name. See the detail error code for more specific information.CT-DBMS: Unknown User. The user name passed to an OpenDataBase call is invalid given the current user file for this data base. If the name should be a valid one and if the user file has recently been modified, it may contain syntax errors. See your Data Base Administrator.CT-DBMS: Missing user file privileges. There are no privileges list in the user file for this data base for this user.CT-DBMS: Journal file inconsisten C t. The archive copy and the journal file do not represent the current state of the data base. Further data base operations cannot be journalized.CT-DBMS: Journal file unusable. The CT-DBMS journalization subsystem cannot read from or write to the journal file.CT-DBMS: Journal file corrupt. An inconsistency in the sequence of entries in the journal file has been detected.CT-DBMS: Data base already open. An application system is allowed to open a given data base only once.CT-DBMS: Invalid vie,E w for index. The ISAM operation OpenISAM was used to open a relation of a data base as an ISAM data set. The operation failed because the view used for one of the indexes did not correspond properly to the index. Refer to the CT-DBMS reference documentation for more information.CT-DBMS: A CT-DBMS physical scanning index Id was used for key lookup. This is an internal error that indicates a problem in the software you are using.CT-DBMS: The data structures used during the scanning of the journal file a8G re corrupt. This is an internal error that indicates a problem in the software you are using.CT-DBMS: The data structures used during roll-forward are corrupt. This is an internal error that indicates a problem in the software you are using.CT-DBMS: A reference to a user or data set in the journal file has not been encountered before. This is an internal error that indicates a problem in the software you are using.CT-DBMS: The entry in the data base directory for the specified data base is bad. ThiDI s is an internal error that indicates a problem in the software you are using.CT-DBMS: View Control Block is corrupt. This is an internal error that indicates a problem in t  tion size. - Link the run file on a system with more memory.Reserved.Linker/Librarian: Bad object module, segment, or group index out of range You included an invalid object module. Usually this is the result of a Compiler error.Too many public procedures in resident/overlay The resident portion and any single overlay can have a maximum of 4,096 procedures. Divide the code into more overlays.ReseW rved.Linker/Librarian: Too many segments Too many areas The Linker does not have sufficient memory to link the run file. To link the file: - If you are running the Linker under the Context Manager, reconfigure the partition size. - Link the run file on a system with more memory.Reserved.Linker/Librarian: Bad object module, external index out of range You included an invalid object module. Usually this is the result of a Compiler error.Linker/Librarian: Bad sector.Linker/Librarian: Fatal error. Y Cannot open the file. You may have used an illegal library format.Linker/Librarihe software you are using.CT-DBMS: Index Control Block is corrupt. This is an internal error that indicates a problem in the software you are using.CT-DBMS: Journalizing data bases open at too many nodes. During a transaction, an application is allowed to have journalizing data bases open in transaction modify mode at one mode oPK nly. Close all data bases at the other node before calling BeginTransaction.CT-DBMS: No more data bases. A ReadNextDB operation has read all of the data bases at the specified node. No information on any data base is returned when this status code is generated. Reserved. CT-DBMS: Internal errors. This is an internal error that indicates a problem in the software you are using.Linker/Librarian: Attempt to access data outside of segment bounds, possibly bad object module If you did not use a segme\M nt directive in your Assembly program, or if you declare code or data outside any segment, the Assembler supplies a segment named ??SEG. The resulting object module is invalid and the Linker cannot produce a run file. In Assembly programs, make sure you include a segment directive. This error can also result from a Compiler error.Reserved.Linker/Librarian: Fatal error. An internal failure has occured. Report the failure to your Unisys Customer Support Center.Linker/Librarian: Too many segment or clashO s names Too many segments You cannot declare more than 255 segments or different segment names in one module; however, the program can contain more than 255 segments. The Linker does not produce a run file. If necessary, divide the module.Linker/Librarian: Segment size exceeds 65520 One segment cannot be larger than 65,520 bytes. This error pertains only to a single segment, not to a group or sum of segments (for example, DATA, CONST, and STACK). The link is aborted. The Linker does not produce a rutQ n file. If you are writing in Assembly language or Pascal, reduce the size of the segment to less than 65,520.Linker/Librarian:  Too many groups Each module can contain a maximum of 10 groups, and the program can contain a maximum of 256 groups. (Refer to your Development Utilities Programming Guide.)Linker/Librarian: Too many public symbols in one module Too many external symbols in one module The Linker does not have sufficient memory to link these modules. To link the file: - If you are running thS e Linker under the Context Manager, reconfigure the partition size. - Link the run file on a system with more memory.Linker/Librarian: Invalid object module A file you specified as an object module is not in object module format. This could result from: - Compiler error - Damage to the file - Specification of a text file (such as the sourcefile) instead of an object moduleReserved.Linker/Librarian: Too many common symbols in one module The Linker does not have sufficient memory to link the run fiU le. To link the file: - If you are running the Linker under the Context Manager, reconfigure the parti an: Bad Index. The index read in is out of range or does not follow OMF for indices greater than 128.Linker/Librarian: Runfile header too large. The Runfile header exceeds 64K.Reserved.GPAM: Invalid GPAMWA has been passed to a GPAM routine.GPAM: Invalid bypass. bBypass value passed to GPAMBeginOverstrike or GPAMBeginUnderscore is out of range.GPAM: Invalid underscore parameter. bUnderscore value passed to GPAMBeginUnde[ rscore is out of range.GPAM: Too many parameters. cbParams value passed to GPAMBeginPage or GPAMOpen is too large.GPAM: Invalid sides specification. bSides value in GPAMBeginPage parameter block is out of range.GPAM: Invalid form name specification. Form name in GPAMBeginPage parameter block is too long.GPAM: Invalid aspect. bAspect value in GPAMBeginPage parameter block is out of range.GPAM: Invalid page number specification Page number in GPAMBeginPage parameter block is too long.GPAM: Invalid ] montage specification Montage name in GPAMBeginPage parameter block is too long.GPAM: Invalid quality bQuality value in GPAMBeginPage parameter block is out of range.GPAM: User name too long User name in GPAMOpen parameter block is too long.GPAM: Document name too long User name in GPAMOpen parameter block is too long.GPAM: Font name too long Font name passed to GPAMSetFont is too long.GPAM: Translate table name too long Translate table name passed to GPAMSetTranslateTable is too long.GPAM: GPAM_ WA too smallGPAM: Timeout value set in GPAMOpen has been reached.GPAM: A GPAM text routine has been called while in graphics mode, or a graphics routine has been called while in text mode.GPAM: Invalid vertical offset level intLevel passed to GPAMSetVerticalOffset is out of range.GPAM: Invalid color specification pb/cbColors passed to GPAMGrColorTable either contain too many colors, or do not contain exactly one red, green, and blue value per color.GPAM: Bad specification of points cbPoints passed ta o GPAMGrPolyLine or GPAMGrPolygon is too large or does not contain exactly one x value and one y value for each point.GPS: Amount to write too large cb passed to GPAMWriteRecord is too large.Reserved.GPS: Device is not installed. Print Manager: The DevHelp file header is corrupted, or is an old version that Print Manager cannot use.GPS: Internal error. This internal error indicates a problem with the software you are using. Consult Technical Support. Print Manager: The DevHelp file cannot be c read or is corrupted.Print Manager: Print Manager request for printing or status has timed out.GPS: Cannot install a GPS service. Print Manager: The GPS.Printers file is corrupted. Delete this file from your directory and reinstall GPS Services.GPS Asynchronous Service Library: Installation errorGPS Asynchronous Service Library: Returned by BuildAsyncRequest or BuildAsyncRequestDirect if request block to be built would overflow stack. Create the context with a bigger stack. Adding 50 bytes ie n the [Increment stack size by] parameter should be enough when installing the Print Service in the Print Manager.GPS Asynchronous Service Library: Context Not Found. Returned by ResumeContext if the request block that pRq points to does not belong to a context that is waiting for a request.GPS Asynchronous Service Library: No heap memory available. Returned by HeapAlloc if there is not enough contiguous memory available in the heap to satisfy the allocation request. Allocate more space to the heap. Ag dding 1000 bytes in the [Increase heap size by] parameter should be enough when installing the Print Manager in the Print Manager.GPS Asynchronous Service Library: Invalid Heap Block. Returned by Heapfree if the pointer to the block to free is invalid. Either the address is out of range or the header of the heap block was corrupted. For example, a user might have overwritten one heap block into the next.Device Drivers: A hexadecimal string of byte values entered into the device driver installation f  e Drivers: Specified file does not exist.GPS releases prior to 2.0: InterLv nal error that indicates a problem in the software you are using. Consult your Unisys representative. GPS 2.0: The font table is full.Device Drivers: The device dependent call DdPutCharG returns this status code when the character does not fit into the current band. This is an internal error that indicates a problem in the software you are using. Consult your Unisys representative.GPS releases prior to 2.0: GPAM data being processed by the GPS device driver contains an invalid GPAM op code. This is Xx an internal error that indicates a problem in the software you are using. Consult your Unisys representative.GPS releases prior to 2.0: More fonts have been requested in the current document than can be supported by this GPS device driver. This is an internal error that indicates a problem in the software you are using. Consult your Unisys representative. GPS 2.3: The TIFF data being processed by the devor j either contains nonhexadecimal digits or an odd number of digits.Device Drivers: GPAM or "NORMAL image-mode" data was sent to the BinaryMode device driver, which requires either "IMAGE" or "BINARY image mode" data.Device Drivers: An attempt was made to acquire a GPS device that is paused (a direct print device may be paused when it is not acquired to prevent its use by GPS). The device must be restarted.Device Drivers: A SetImageModeGPS request was sent to a GPS device while also sending it GPAM data. l The image-mode of a GPS device cannot be set while it processes GPAM. If a pass-through mode is required, use GPAMBegin-Transparent and GPAMEndTransparent functions.Device Drivers: More than one SetGPSParams request was sent to a GPS device driver for a single document. Or the SetGPSParams request was made after a WriteGPSFile request had already been made. For direct printers, the SetGPSParams request must occur between the OpenGPSFile request and the first WriteGPSFile request; and, there cannot be mon re than one SetGPSParams request between them. For Spooled printers, multiple SetGpsParam requests can be made any time before CloseGpsFile is called.Device Drivers: The GPS device driver's output port is not currently acquired, and this request cannot be performed. If the device driver is installed for direct printing, some other application may be currently printing to the device driver's shared port.Reserved.Device Drivers: An Align or Restart command was attempted upon a device that is not paused.De(p vice Drivers: Incorrect graphics data was received in the input stream.Device Drivers: An invalid image-mode value was specified.Device Drivers: The supplied data buffer was too small for the requested data.Device Drivers: An invalid value was specified for Beginning-Page class.Device Drivers: An invalid value was specified for Ending-Page class.Device Drivers: An invalid value was specified for the Control command.Device Drivers: An invalid value was specified for the Control subcommand.GPS Asynchro4r nous Service Library: Can't find OS tables. AsyncServer procedures cannot access the tables in the operating system to get the tables it needs to build request blocks. The operating system may be too old to work with the AsyncServer procedures.Reserved.Device Drivers: The specified restart location could not be found in the document. Releases prior to GPS 2.0: This request to GPS is not appropriate at this time.Device Drivers: The current operation upon this GPS device must be completed before this@t  request to the Device Driver may be made.Device Drivers: A print job must start again from the beginning. (This is an internal error that indicates a problem in the software you are using. Contact your Unisys representative.)Reserved.Device Drivers: The request cannot be serviced because the device driver for the requested device is currently being removed.Device Drivers: Job has been cancelled and data will not be output.Devic ice driver is malformed.GPS: Cannot find OS tables. This occurs if the AsyncServer procedures candz not access the operating system tables needed to build request blocks. The operating system may be too old to work with AsyncServer procedures.  Device Driver: The CGM data being processed by the device driver is malformed.Device Drivers: The GPAM data being processed by the GPS device driver contains malformed GPAM records or is not a supported version of GPAM.GPS Device Drivers: Control process of the GPS device driver has received an invalid request. This is an internal error that indicates a problep| m in the software you are using. Contact your Unisys representative.GPS Device Drivers: Data process of the GPS device driver has received an invalid request. This is an internal error that indicates a problem in the software you are using. Contact your Unisys representative.GPS Device Drivers: Device driver cannot acquire access to the device's output port because: - GPS has already acquired this port. - Another application is currently using the port. The device driver being installed is incom|~ patible with your current version of GPS.GPS Device Drivers: The GPS device driver is unable to get the correct information to allow its deinstallation. This is an internal error that indicates a problem in the software you are using. Contact your Unisys representative.GPS Device Drivers: JOB CHANGE command was received by the wrong process at the GPS device driver. This is an internal error that indicates a problem in the software you are using. Contact your Unisys representative.GPS Device Drivers:   Wheel file accessed by the daisy device driver is not a valid Wheel file. This is an internal error that indicates a problem in the software you are using. Contact your Unisys representative.GPS Device Drivers: Name passed to GPS is too long.GPS: Invalid GPAM operation encountered while in Transparent mode.Device Drivers: Invalid, preGPS Spooler Escape Sequence encountered.GPS Release prior to 2.0: The number of fonts specified in the currently printing document is greater than the number allowed in  any one document by this device driver, or the requested font could not be found in the device driver's font table.GPS Device Drivers: The device driver failed while processing a job change request. This is an internal error that indicates a problem in the software you are using. Contact your Unisys representative.GPS Print Service: An attempt was made to access a device in the Print Service tables that was marked uninstalled.GPS Print Service: Bad request file. Verify that a correct version of the lo adable request file, Request.sys, is in [Sys]. Be sure to reboot the system after installing GPS. Merge Request.Q.sys with Request.sys.GPS Print Service: A workstation prefix is required if the Routing Switch is installed at a diskless workstation.GPS: The Routing Switch job table does not contain the required job handle. Print Service: Bad case value for Job Delete Request.GPS Print Service: Exceeded maximum number of simultaneously open device streams. Either reduce the number of simultaneous ly open devices or increase the Maximum number of open files (default=12) value specified at the time of Routing Switch installation. Print Service: Print Service on server (formerly master) is holding a request for an "Unlinked" printer.Print Service: The request was routed, but not marked, for the Routing Switch uplink. This is an internal error that indicates a problem in the software you are using. Contact your Unisys representative.GPS: The internal flag indicates that the Routing Switch uplink w ill process the request. This is an internal error that indicates a problem in the software you are using. Contact your Unisys representative. Print Service: The Print Service is formatting the request to another node for service.GPS: An invalid request code has been detected. Print Service: The GPS Service i  essor, Document Designer: Bad dictionary I/O.OFIS Writer, OFIS Designer, Word Processor, Document Designer: Distionary word too long.OFIS Writer, OFIS Designer, Word Processor, Document Designer: Bad dictionary path.OFIS Writer, OFIS Designer, Word Processor, Docu  ment Designer: Bad dictionary file.OFIS Writer, OFIS Designer, Word Processor, Document Designer: Dictionary temporarily full.OFIS Writer, OFIS Designer, Word Processor, Document Designer: Bad dictionary unload.OFIS Writer, OFIS Designer, Word Processor, Document Designer: Dictionary inconsistency.OFIS Writer, OFIS Designer, Word Processor, Document Designer: Dictionary not available.OFIS Writer, OFIS Designer, Word Processor, Document Designer: Need word traits.OFIS Writer, OFIS Designer, Word Proces sor, Document Designer: Word not found.Reserved.OFIS Writer, OFIS Designer, Word Processor, Document Designer: Dictionary Call Not Implemented. Older version of the dictionary does not implement this dictionary requests terminating. Requests to a GPS device that is being deinstalled are being returned.GPS Print Service: You cannot deinstall GPS when running on a single partition operating system.GPS Print SeĊ rvice: The device driver has not yet been installed. Device driver is partially installed or is not yet polling its server (formerly called master).GPS Print Service: Duplicate device specification. An attempt was made to add a device that already exists.GPS Print Service: A request for spooled printing or status was made to a device driver installed for direct print device. (On direct print devices, document information is available only for the document currently printing.)GPS Print Service: An attЌ empt was made to read beyond the end of a device scheduling queue by the GetGPSDocInfo request.GPS Print Service: Bad job handle. The printing job has been aborted. Possibly caused by termination or system crash of GPS on another workstation.GPS Print Service: A direct print device is already opened by another user.GPS Print Service: Exceeded maximum number of simultaneously open device streams. Either reduce the number of simultaneously open devices or increase the Maximum number of open files (de܎ fault=12) value specified at the time of Routing Switch installation.GPS Print Service: Network device table is full. Either reduce the number of devices known to the Print Service (Routing Switch) or increase the Maximum number of network devices.GPS Print Service: Unbalanced brackets on device specification.GPS Print Service: Invalid node specification.GPS Print Service: User has specified an invalid file handle. This is an internal error that indicates a problem in the software you are using. Cont act your Unisys representative. Bad type case. Location of device in Device table is incorrect. This is an internal error that indicates a problem in the software you are using. Contact your Unisys representative.GPS Print Service: Bad update case for Network Device Management. This is an internal error that indicates a problem in the software you are using. Contact your Unisys representative.GPS Print Service: Bad query case. This is an internal error that indicates a problem in the software you a re using. Contact your Unisys representative. Device configuration record is malformed.GPS Print Service: The device name is not recognized.GPS Print Service: The device table is full. Either reduce the number of devices known to the Routing Switch or increase the Maximum number of local devices (default=3) value specified at the time of Routing Switch installation.OFIS Writer, OFIS Designer, Word Processor, Document Designer: Bad dictionary version.OFIS Writer, OFIS Designer, Word Processor, Document  Designer: Bad dictionary environment.OFIS Writer, OFIS Designer, Word Processor, Document Designer: Not enough memory.OFIS Writer, OFIS Designer, Word Processor, Document Designer: Cannot open dictionary.OFIS Writer, OFIS Designer, Word Proc .OFIS Writer, OFIS Designer, Word Processor, Document Designer: Too few arguments specified for macro or string argument.OFIS Writer, OFIS Designer, Word Processor, Document Designer: Too many arguments specified for macro or string argument.OFIS Writer, OFIS Designer, Word Processor, Doc$ ument Designer: External macro or string function cannot be performed because ICMS is not installed.OFIS Writer, OFIS Designer, Word Processor, Document Designer: Bad predicate.OFIS Writer, OFIS Designer, Word Processor, Document Designer: External macro or string function argument is too long.OFIS Writer, OFIS Designer, Word Processor, Document Designer: Macro or string expression contains an identifier in a context in which identifiers are not allowed.OFIS Writer, OFIS Designer, Word Processor, Docume0 nt Designer: Macro or string expression contains an external function reference in a context in which external function references are not allowed.OFIS Writer, OFIS Designer, Word Processor, Document Designer: First macro or string function argument invalid.OFIS Writer, OFIS Designer, Word Processor, Document Designer: Second macro function argument invalid.OFIS Writer, OFIS Designer, Word Processor, Document Designer: Third macro or string function argument invalid.OFIS Designer, Word Processor, Docume< nt Designer: Object inconsistency. The object anchor has been corrupted.OFIS Designer, Word Processor, Document Designer: Voice inconsistency. The voice anchor has been corrupted.Reserved.Mouse Management: Invalid parameters. Check the parameters of the procedures you are calling to be sure they are in the correct range and form.Mouse Management: Coordinate parameters out of range. The coordinates specified in a PDSetCursorPosNSC or PDSetMotionRectangleNSC procedure are not within the specified raH nge. Either specify new coordinates or, for procedures that use virtual screen coordinates, define a new virtual screen coordinate space with PDSetVirtualCoordinates.Mouse Management: Cursor not in current window. You attempted to get the cursor position with PDGetCursorPosNSC when the mouse had been moved out of the application window. In most cases, the application would probably ignore this status code; for example, the last valid cursor position received would be used.Mouse Management: Mouse and keT yboard not assigned to process. You attempted to move the cursor position with PDSetCursorPosNSC, but you are not allowed to move the cursor position unless the application is the current context. This status code should normally be handled by the application. In most cases, the application would probably ignore the code.Mouse Management: Workstation not supported. All workstations except B24, IWS, and AWS are supported. This status code is generated when you attempt to install the Mouse Server.Mouse ` Management: Graphics type not supported. Graphics are supported on BTOS and CTOS workstations with a graphics module or card; B24, IWS, and AWS workstations are not supported. This status code is generated when you attempt to install the Mouse Server on a non-supported workstation.Mouse Management: Unsupported graphics cursor type. In PDLoadCursor, the valid cursor type is 3 for the XOR cursor.Mouse Management: Invalid gear value. In PDSetControls and PDSetSystemControls, the valid gear speeds are 1 l through 10.Mouse Management: Not an icon [file]. The icon [file] specified in PDLoadCursor or PDReadIconFile is not an icon [file] with the specified structure.Mouse Management: Icon too large for specified structure. The icon [file] specified in PDReadCurrentCursor or PDReadIconFile does not fit into the specified structure.Mouse Management: Work area too small. The work area specified in PDReadIconFile must be 512 bytes and word aligned.Mouse Management: Operating system not supported. Your operatx ing system is not supported. You must have BTOS II, or CTOS 9.5 or higher. This status code is generated when you attempt t  ET, BNet II: Buffer not waiting for read. B-NET, BNet II: Internal error. CT-Net: The CT-Net Server received a read event for a buffer that is not waiting for a read.CT-Net, B-NET, BNet II: Invalid request. The Net Server received an unexpected request at an exchange allocated to the Net Server. It is not a response to a request that the Net Server originated. Possible cause: the system has sent a request to the wrong exchange.CT-Net, B-NET, BN̷ et II: Buffer not waiting for response.  B-NET, BNet II: Internal error. CT-Net: The CT-Net Server received a response to a request, but its buffer was not waiting for a response. This could be due to a program error or data in memory being written at random.CT-Net, B-NET, BNet II: Buffer not in write state. B-NET, BNet II: Internal error. CT-Net: The CT-Net Server just received a response to a write, its buffer is not in StateWaitingForWrite. This could be due to a program error or data in mع emory being written at randomo install the Mouse Service.Mouse Management: Incompatible cursor type. A graphics cursor operation, such PDLoadCursor, was specified without previously using PDSetCursorType to declare the cursor type as graphics.Reserved.Windows Manager: There are no free windows.Windows Manager: Cannot deinstall. Windows is prevented from deinstalling unless there is only one window. This sta tus code is returned when attempting to deinstall Window Services within Context Manager or under other applications that have more than one window open.Windows Manager: There is an invalid window handle (window services error).Windows Manager: Window not present. Windows could not find the character map for the specified Window Services procedures that require a window handle as a parameter.Windows Manager: There is an invalid window parameter (window services error).Windows Manager: No window memory.  Windows could not allocate enough memory. This is required so that the user can distinguish between Window Servivces and applications running out of memory. This error code is returned by Window Services procedures that attempt to create or increase the size of a window.Windows Manager: Error in deallocation. Windows could not deallocate memory. This is required so that the user can distinguish between Window Servivces and applications not being able to deallocate memory. This error code is return ed by Window Services procedures that attempt to destroy or decrease the size of a window.Windows Manager: Duplicate UIMS query. Windows Services has already queued up the request for GetUIMSEvent by this usr. This status code is returned by the request GerUIMSEvent if called multiple times since the last event by the same user. This error code is returned by Window Services procedures that attempt to destroy or decrease the size of a window.Reserved.Reserved.CT-Net, B-NET, BNet II: Request data too l arge. The request received from the Net Agent is too large to fit in the Net Server's buffer. CT-NET Server: The request data in client request is larger than the size of the buffer specified by sXbData in the command line. This could be due to data incorrectly received from the Transport Service. B-NET: If you installed the Net Agent and/or Net Server via the RUN command, check to make sure you did not specify too many parameters. BNet II: Specify a larger value for the Size of Large Requests par ameter when installing BNet on the remote node.CT-Net, B-NET, BNet II: No user number available. The Net Server has run out of numbers to allocate for this request (too many remote users are trying to access a node at the same time). B-NET, BNet II: This is a Sysgen parameter; to increase the number of Net Users, customize the operating system on the remote node reporting the error. CT-Net Server: The client should try again later or allocate more remote user numbers to the CT-Net Server in the nNet Users parameter of the Sysgen Prefix file.CT-Net, B-N .CT-Net: Invalid disconnect response. The CT-Net Server received a response to a disconnect request from the Transport Service, but the session does not expect to be disconnected.CT-Net, B-NET, BNet II: Invalid user number. The Net Server received a response to a client request when the user number in the request block is not assigned to a remote user. A program may have sent a message to the Net Server's exchange by mistake, or a server may have corrupted the user number f ield in the request the Net Server issued.B-NET, BNet II: Invalid event. Internal error. CT-Net: The CT-Net Server received an event from the Transport Service, the event type of which is unknown. This could be due to a program error or data in memory being written at random.B-NET, BNet II, CT-Net: No abort requests. The Net Server expects the Request.asm to specify Abort requests. Something may be wrong with the operating system environment.B-NET, BNet II, CT-Net: Invalid connection handle. The  Net Server received a connection handle from the Transport Service that is not in the Net Server table. This could be due to a program error or data in memory being written at random.B-NET, BNet II, CT-Net: Invalid request size. The size of the message received from the Net Server does not equal the total of the header, the request block, and the request data. Possible cause: data incorrectly received from the transport service.B-NET, BNet II, CT-Net: Invalid buffer on read. The pointer returned by th e event request on a read does not point to a buffer. Internal error. Possible cause: program error or data in memory being written at random.CT-Net: Session closed. The session has been closed due to a timeout.B-NET, BNet II, CT-Net: File handle to close not found. The file handle of a file closed by a remote user is not in the Net Server's table of remote file handles. Internal error. Possible cause: program error or data in memory being written at random.B-NET, BNet II, CT-Net: File handle for c hange longevity not found. The file handle specified by ChangeFhLongevity is not in the Net Server's table of remote file handles. Internal error. Possible cause: program error or data in memory being written at random.B-NET, BNet II, CT-Net: No remote file handle available. An Open request has been processed by the Net Server, but the Net Server cannot support any more remote resources. BNetII: Increase the number of Server Remote Resources when installing BNetII on the remote node. CT-Net: Sp ecify a larger number of remote files in the command line.B-NET, BNet II, CT-Net: User resource count zero. A file is being closed, but the user's resource count is invalid (already zero). Internal error. Possible cause: program error or data in memory being written at random.B-NET, BNet II, CT-Net: No net users. The system is customized to permit no Net Users. You should rebuild it to define some Net Users if you use the Net Server. This is a Sysgen option specified by the nNetUsers parameter i  n the Prefix file.B-NET: No Transport Service. Neither the Net Transport Service nor the LAN Transport Service is present. CT-Net: No Transport Service. The Transport Service must be initialized before the Net Server. The Transport Service is not serving the exchange for AttachCtNet.CT-Net: Unexpected request. The CT-Net Server has been stopped, but it found another request in its queue. Possible cause: program error or data in memory being written at random.CT-Net: CT-Net Server stopped. ,  CT-Net Server has received a stop (deinstall) request.Reserved.CT-Net: CT-Net Server array too small. The static array allocated in the module InitAlloc must be large enough for all dynamically allocated arrays that get initialized. If the array is not large enough, InitAlloc must be reassembled. Making the array larger makes the run file larger. Leftover memory gets returned when initialization is complete.CT-Net: The CloseAllFiles buffer list i  owing a session (connection) failure, which causes any open resources to be closed. Also, the caller may not have set the file  handle correctly. Retry the command.CT-Net: Transport failure. The Transport Service returned an event request with event transport failure.B-NET, BNet II, CT-Net: Remote file handle not found. A remote file handle is not in the Net Agent's table of remote resources. Internal error. Possible cause: program error or data in memory being written at random.B-NET, CT-Net: Invalid user number. The Net Agent has received a request with a user number out of range. This request should not have been rou ted to the Net Agent. On a shared resource processor, try increasing the value of the nUsersPerCPBoard parameter when installing the Net Agent; otherwise it is probably a programming error by the caller.B-NET, BNet II, CT-Net: Invalid node name. The node name is invalid (either more than 12 characters long, or zero length (that is, "{}")).B-NET, BNet II, Cs corrupted.CT-Net: A user is terminating and an error8  occurred in Server Processing.Reserved.CT-Net: The file specification is too long for the Net Agent's buffer. Reissue with a shorter length.Reserved.Reserved.B-NET, BNet II, CT-Net: The Request Control Blocks (RCB) list is corrupted. Internal error.B-NET, BNet II, CT-Net: Net Agent no room. The Net Agent has run out of Request Control Blocks. Increase the Max # Clients Requests Queued. This parameter determines the size of the queue set aside for requests that need to be routed across CT-Net.CT-NetD : NetXBuf too small.B-NET, BNet II, CT-Net: Invalid message header. The first word is not a valid RCB pointer. The first word of a message should point to the RCB that belongs to the message. Internal error. Possible cause: invalid data received from the Transport Service.CT-Net: Message wrong session. The ConnectionHandle that came with the message does not agree with the ConnectionHandle of the RCB associated with the handle.B-NET, BNet II, CT-Net: Invalid net request. A status or query rP equest to the Net Agent or Net Server is improperly formed or unexpected. BNetII: This can also indicate an attempt to turn on compression when the Agent/Server was installed with the "Never" option for compression, or to turn it off when the "Always" option was specified. CT-Net: Possibly a request was sent to the wrong exchange.B-NET, BNet II, CT-Net: Invalid event. The CT-Net Agent received an event that it does not recognize from the Transport Service.B-NET, BNet II, CT-Net: Aborted request te\ rminating. A request in stateWaitingToAbort is being terminated. Internal error.B-NET, BNet II, CT-Net: Read overflow. The response contained more data than expected. The data does not fit in the client's buffer. Possible cause: transmission error, program error, or data in memory being written at random.B-NET, BNet II, CT-Net: No session available. The Net Agent has no more available sessions; all sessions are in use supporting access to other remote nodes. Try again later, or increase the Agenth  Max # Sessions Open parameter when installing the Net Agent (B-NET) or Net Agent/Server (BNet II), or increase the value of nSessions in the CT-Net Agent command line.B-NET, BNet II, CT-Net: Invalid RCB state. Internal error.B-NET, BNetII, CT-Net: Invalid system request. The Net Agent received a request with a zero routing code that is not a system request (a zero routing code indicates a system request). Possible cause: program error or the system may have randomly written data in memoryInvalid Nett  Agent connection handle. The Transport Service returned a ConnectionHandle that is not in the Net Agent's table. Internal error. Possible cause: program error or data in memory being written at random.B-NET, BNet II, CT-Net: Invalid file handle. The Net Agent received a request with a file or resource handle that does not match any of its existing files. This can occur foll T-Net: No remote file handles available. The Net Agent has run out of remote resource control blocks. For BNET, increase the Agent Max # Remote Reso urces Open parameter when installing the Net Agent. For CT-Net, consider increasing nRemoteFhMax in the command line.B-NET, BNet II, CT-Net: File to close not found. The file handle for a close request is not in the Net Agent's table of remote file handles. Internal error. Possible cause: program error or data in memory being written at random.B-NET, CT-Net: No Transport Service. B-NET: Neither the Net Transport Service nor the LAN Transport Service is present. Also, on the shared resource pro cessor, it may indicate that the Net Agent is waiting for the Net Transport Service to come up. CT-Net: The Transport Service must be initialized before the Net Agent. The Transport Service is not serving the exchange for AttachCtNet.B-NET, BNet II, CT-Net: Session closed. The system has closed the session (probably due to a timeout). B-NET: The session may have been closed due to a transport failure, or the caller may not have set the file handle correctly. (If the Net Agent should abort with thi s error, it is an internal error.)B-NET, BNet II, CT-Net: Session not waiting for open. The Net Agent received a response to an Open request, but the session is not waiting for an Open. Internal error. Possible cause: program error or data in memory being written at random.B-NET, BNet II, CT-Net: Invalid timeout. The Net Agnet received a request with a request code of zero, indicating a TimerRequestBlock, but the request pointer does not point to a SessionData record. Internal error. Possible c ause: program error or data in memory being written at random.B-NET, BNet II, CT-Net: Bad sequence number. The Net Agent received a request back from the Net Server, but the sequence number does not correspond to the request that the Net Agent sent. Internal error. The error could be due to invalid data received from the Transport Service.CT-Net: Net Agent array too small. The static array allocated in the module InitAlloc must be large enough for all dynamically allocated arrays that are initialize d. Reaasemble InitAlloc, making the array, and therefor the run file, larger. Leftover memory is returned when initialization is complete.B-NET, BNet II, CT-Net: Net Agent stopped. B-NET: The NCC Deinstall Table deinstalled the Net Agent. BNetII: The NCU program was used to deinstall the Net Agent. CT-Net: The Net Agent received a request from a client, but the Net Agent has been closed down. This could be due to a program error or data in memory being written at random.B-NET, BNet II, CT-Net: N et Agent SRP Buffer Failure. There was a buffer failure on the shared resource processor. This is an internal error.CT-Net: Agent has gotten into a wrong status when fanning out a system (abort, term, and so on) request.B-NET, BNet II, CT-Net: Termination error. Agent has gotten into a wrong status when terminating or aborting (abort, term) a request. Internal error.CT-Net: Agent has gotten back all the user requests from all open sessions but has already responded to the swapping request.CT-Net:  Agent has gotten back all the user requests from all open sessions but has already responded to the swapping request.CT-Net: Agent has received an internal request with an invalid request type.CT-Net: Users' requests were outstanding after all the termination requests had returned from the distant nodes.CT-Net: This user has a request in State Waiting for Transmit.CT-Net: User Number state invalid.CT-Net: There is a request for this user in Status Waiting To Abort.CT-Net: There is a request for this u ser in State Waiting To Abort.CT-Net: There is a request for this user in State Waiting for Transmit.B-NET, BNet II, CT-Net: In termination A termination request is issued for this user.Reserved.B-NET, BNet II, CT-Net: Bad heap. The internal heap check, which   ture when one was already open. Only one picture can be open at a time. Use ClosePicture to close the open picture and retry.BTOS Graphics II, Graphics Library: An attempt was made to modify (the vectors or labels in) a picture that was opened in read mode. An existing picture must be opened in modify mode to add @ new objects to the picture or to modify existing objects in the picture. Specify modify mode (mm) when you call OpenPicture.BTOS Graphics II, Graphics Library: An OpenPicture (or ReadPicFile, AddPicture, AddPicFile) procedure failed because the picture specified was not a picture file. A picture file is of a particular format. The file you opened does not contain picture information. If the file was a .pic file, the picture format was of an incompatible level. Check to be sure you have referred to thL e correct file. OFIS Graphics: File is not a picture file You have tried to load in a file that is not a chart or picture. Make sure you are referring to the right fis performed when doing a heap manipulation, has determined that the heap is not consistent with itself.Reserved.Virtual Code Segment Management: Overlay already in memory.Virtual Code Segment Management: Next overlay does not fit. The swap buf fer is not large enough to swap in the next overlay. Increase the size of the swap buffer.Virtual Code Segment Management: ROD will not fit. The Regional Overlay Descriptor (ROD) will not fit. The swap buffer is not large enough. Increase the size of the swap buffer.Virtual Code Segment Management: Swap failed. Internal system error was detected. Possibly a file system error that involves the run file occurred.Virtual Code Segment Management: Inconsistent ProcInfo table. An internal data structure  has been corrupted. This problem was possibly caused by link time errors reported in the run file load map.Reserved.Configuration Management: The configuration exceeds 32 hardware modules. This status code may indicate an X-Bus problem or a defective hardware module.Reserved.Configuration Management: Invalid module type code. A workstation hardware module or input device supplied an unrecognized self-identification code. The hardware module may be defective or the version of the operating system you  are using may not support the device.Reserved.BTOS GraphicsII, Graphics Library: Graphics is not available on this workstation. Your workstation does not have the necessary graphics hardware.GPS: Internal error within the device driver's graphics processing. Contact your Customer Support Center. BTOS Graphics II, Graphics Library: A graphics procedure was called before graphics was initialized. InitGraphics is always the first graphics procedure called when you use device-independent procedures. ( For device-dependent procedures, use InitScreenGraphics.) Make InitGraphics or InitScreenGraphics the first graphics procedure called in the program.BTOS Graphics II, Graphics Library, OFIS Graphics: An internal graphics error has occurred. Real number divide by zero operation attempted or invalid entry in display list. Consult your system administrator.BTOS Graphics II, Graphics Library: Raster Operations are not available. You attempted to call DoRasterOp or DpRasterOpText on a workstation that does(  not support raster operations.BTOS Graphics II, Graphics Library: An internal fill error has occurred. This error occurs on calls to FillRectangle or FillScreenRectangle. This is an internal error that indicates a problem with the software you are using.Reserved.BTOS Graphics II, Graphics Library: A graphics procedure that requires a picture to be open was called before a picture was opened. You attempted to use picture or object procedures without first opening a picture. Use OpenPicture to open a p4 icture before you call other picture or object procedures. Subsequent picture and object procedures use this open picture.BTOS Graphics II, Graphics Library: An attempt was made to open a pic  ile.BTOS Graphics II, Graphics Library: An OpenPicture procedure failed because the picture name was greater than 106 characters or the password was greater than 12 characters. The failure can also occur if the picture file has inconsistent data and is therefore an invalid picture file. Both picture names and passwords have a limited numbX er of characters. Shorten the picture name or password. OFIS Graphics: I/O error while reading picture file A read error occurred while OFIS Graphics was reading a .pic file. This error could indicate a bad spot on the disk or corrupted data in the file.Reserved.BTOS Graphics II, Graphics Library: A graphics procedure that requires an open object was called when there was no open object. You have used an object procedure, such as ClearLabels or DisplayCurrentObject, before you opened an object. Opend  an object using OpenTempObject, SetFirstObject, SetNextObject, AddObject, or OpenPicture before you call any other object procedures.BTOS Graphics II, Graphics Library: An attempt was made to open a picture or an object when an object was still open. Only one picture or object can be open at a time. Use ClosePicture and CloseObject to close the open object and picture and retry.BTOS Graphics II, Graphics Library: The object name specified to AddObject was more than 12 characters. Object names are limip ted to 12 characters. Shorten the object name.BTOS Graphics II, Graphics Library: A graphics operation that requires an object to be closed was invoked when the object was still open.BTOS Graphics II, Graphics Library: CloseTempObject was performed when the open object was not temporary. CloseTempObject can be used only for temporary objects. Use CloseObject for all other objects.  Use CloseObject to close objects that are not temporary.BTOS Graphics II, Graphics Library: A graphics procedure that req| uires a retained object was called when a temporary object was open. You attempted to call a procedure such as AddObject, GetObjectName, SetFirstObject, SetNextObject, ClearLabels, SetNextLabel, SetFirstLabel, GetCurrentLabel, ModifyLabel, DeleteCurrentLabel, ClearVectors, DisplayCurrentObject, RemoveCurrentObject, CloseObject, or DisplayPicture. These procedures all operate on retained objects only, not temporary objects. Open a picture and set the current object before calling other object procedures.B TOS Graphics II, Graphics Library: An attempt was made to modify the vectors or labels in the open object when the picture was opened in read mode.BTOS Graphics II, Graphics Library: An attempt was made to write (the vectors and labels in) the open object when the picture was opened in read or modify mode. An existing picture must be opened in write mode to write any objects in the pictures. Specify write mode (mw) when you call OpenPicture if you want to write in the objects.BTOS Graphics II, Graphics  Library: SetNextObject was performed when the current object was the last object in the picture. You have reached the last object in the current picture; thus, it is not possible to move to the next object. Either (1) use SetFirstObject and start through the list again, or (2) stop processing because you have reached the end of the picture.BTOS Graphics II, Graphics Library: An OpenTempObject procedure failed because either a picture or another object was open. You cannot open a temporary object when  other pictures or objects are open. Close the current picture and/or object.BTOS Graphics II, Graphics Library: Bad object bounds were encountered. GetPictureBounds failed because the current picture does not contain any objects, or contains only an empty object.Reserved.BTOS Graphics II, Graphics Library: A label procedure requiring a current label was called when there was no label. A label must be designated as the current label before any other label procedures can be used. Use AddLabel, SetFirstL  abel, or SetNextLabel to set the current label.BTOS Graphics II, Graphics   work area passed to the graphics library by the last OpenPicture is insufficient for you to continue adding to the current picture. Also, there may be insufficient memory to display the string passed to DoRasterText. Allocate a larger portion of memory for the work area or break the string into smaller parts. OFIS Graphics: Not enough memory for last graphics operation The system does not have sufficient memory to complete the last command you gave OFIS Graphics. Save your current file and exit to th e Executive. Reenter OFIS Graphics and repeat the graphics operation you previously attempted. You can simplify the chart or drawing you are working with by eliminating multiple fonts, sketched lines, circles, and so on. The long-term solution is to add more memory to your system. You can also change the memory requirements in the Context Manager configuration file.BTOS Graphics II, Graphics Library: On Key is interrupted. When the user-written procedure ReadInterruptKey returns a nonzero s Library: SetNextLabel was performed when the current label was the last label in the object. You have reached the last label in the current picture; thus, it is not possible to move to the next label. Either (1) use SetFirstLabel and start through the list again, or (2) stop processing because you have reached the end of the label list.BTOS Graphics II, Graphics Library: A font name was specified that was longer than 12 characters  . Font names are limited to 12 characters. Shorten the font name.BTOS Graphics II, Graphics Library: An invalid label origin was specified in a label procedure. Label origin values are 0 through 8. Specify a label origin in the appropriate range.BTOS Graphics II, Graphics Library: A text or label procedure was performed in which the text string extended outside the world coordinate system. Either the x,y coordinates specified are outside the world coordinate system, or the label origin or font size w  ould cause text to shift outside the world coordinate system. Adjust the x,y coordinates, size, or the label origin so that the text will fit inside the world coordinate system. OFIS Graphics: Label would extend out of bounds The text you are entering is too large or long for the work area. Make the text smaller or break it into shorter lines.BTOS Graphics II, Graphics Library: A zero-length label was specified. Zero-length labels are not valid. Specify the correct label length.GPS: Invalid CGM-gra phics formats encountered in the document being processed by the device driver, or an internal error detected within the driver's raster scaling. BTOS Graphics II, Graphics Library: A graphics procedure was called with incorrect parameters. There are many possible causes of this status code. Check the description of the procedure and its parameters. OFIS Graphics: Bad parameter given for graphics operation Bad data was passed to a graphics operation. Parts of the file may have been overwritten or wr ongly calculated.BTOS Graphics II, Graphics Library: A graphics transformation procedure (SetScale, SetTranslate) would, if called, result in invalid transformation values. Transformed objects must be inside the world coordinate area. If any part of the transformed object falls outside the world coordinate area, you must supply new transformation parameters. Default world coordinate area is (0,0) through (100,n). Refer to the graphics programming manual to obtain the value of n for your workstation. I nclude bounds checking in your mathematics so that you stay within the world coordinate space.BTOS Graphics II, Graphics Library: Bad polygon. Parameters were specified that are not contained within the given viewport boundaries.GPS: Insufficient memory allocated within the device driver to print a graphics object. Reinstall the device driver with a larger Font Data Table Size or reduce the complexity of the graphics object. BTOS Graphics II, Graphics Library: There is insufficient memory. The memory  ! tatus code,   the current display picture is interrupted. This is the recommended standard code to be returned. The graphics library makes no special check for this code; it is provided here only for user consistency.Reserved.BTOS Graphics II, Graphics Library: Bad Icon header. The passed icon is not valid. Check to see that the parameters that were passed point to a valid icon description.Graphics Library: Size of the old palette is too large.Graphics Library: Size of the new palette is too large.Graphics Librar y: Size of the old control structure is too large.Graphics Library: Size of the new control structure is too large.Graphics Library: Palette entry is out of range. This status code is returned by SetStyleRamEntry.Reserved.Graphics Library: SetAlphaColorDefault returns this status code if the parameter's value (bmode) is any value other than zero.Reserved.BTOS Graphics II: Insufficient memory for an area fill.BTOS Graphics II, Graphics Library: Invalid plane was requested. This code is returned if th$ e plane set in SetRasterSourcePlane or SetRasterDestinationPlane does not exist on your workstation. Refer to the graphics documentation to determine the hardware requirements for your workstation.BTOS Graphics II, Graphics Library: Invalid op code was supplied. BTOS Graphics II: An invalid operation code was supplied in DoRasterOp (for wSourceOperation or wDestinationOperation). Refer to the BTOS Graphics II Programming Reference Manual to be sure that you have supplied the proper operation code for D0  oRasterOp. Graphics Library: Drawing mode for a line or bitmap is invalid.OFIS Graphics, Art Designer: Format file and data inconsistent You have specified a chart format file that is inconsistent with the data file. For example, you may have specified a line chart format file with pie chart data. Change the format file or go back to Enhanced Multiplan and change the data. For instance, if you have created a bar graph, the format file must be filenamebar.fm.OFIS Graphics, Art Designer: Too many bar <" chart legends You have exceeded the maximum of legends allowed in a bar chart for this release of the application. (The number varies with the release level.) Reformat the bar chart using fewer legends. Refer to the documentation for the specific release of the application for the maximum number of legends allowed.OFIS Graphics, Art Designer: Maximum number of groups for bar chart exceeded The maximum number of data groups allowed per bar chart in this release has been exceeded. (The number varies H$ with the release level.) Reformat the bar chart using fewer data groups. Refer to the documentation for the specific release of the application for the maximum number data groups allowed.OFIS Graphics, Art Designer: Maximum number of segments for pie chart exceeded Maximum number of pie segments per pie chart is exceeded. (The number varies with the release level.) Reformat the pie chart using fewer pie segments. Refer to the documentation for the specific release of the application for the maximT& um number of pie segments allowed.OFIS Graphics, Art Designer: Max number of legends for line chart exceeded A maximum of five legends are allowed in a line chart. Reformat the line graph using five or fewer line legends.OFIS Graphics, Art Designer: Negative number incorrect with pie chart A negative number cannot be used in a pie chart. Remove the negative data in the Enhanced Multiplan worksheet or specify another graph type.OFIS Graphics, Art Designer: Bad Palette Signature This error occurs if `( a file specified as a palette file does not contain the proper signature for a palette file.OFIS Graphics, Art Designer: Need at least 2 data points for a line chart A line containing only one data point cannot be displayed. Modify your worksheet or use another type of graph.OFIS Graphics, Art Designer: Unrecognized message type passed in The graphics application has received an indecipherable mes!  cs II, OFIS Graphics, Art Designer: Standard font was not specified. The standard font, Simplex Roman, was not specified in the Graphics.Fonts file. This font specification mus6  t be part of Graphics.Fonts. Check the file [Sys]Graphics.Fonts. The first line should read as follows: Standard: SimplexRomanBTOS Graphics II, OFIS Graphics, Art Designer: Invalid output device was specified. An invalid output device was specified in SetOutputDevice or SetOutputType. Refer to the graphics programming documentation for a listing of valid output device codes and SetOutputType.GPS: Invalid CGM-graphics formats encountered in the document being processed by the device driver. BT8 OS Graphics II, Art Designer: Entry contains an odd CGM parameter count. CGM files contain entries that are word-aligned. This error occurs when an entry contains an odd number of parameter bytes. If this error occurs on a file generated by WriteVDM, it is an internal error. If the file was not generatesage from the Inter-Context Message Service (ICMS). Consult the manual for the application that is sendingl*  the graphics application the message.OFIS Graphics, Art Designer: No graphics devices were found on the system The output device you specified to print to is not configured on your system. Either ask the system administrator to configure the device or specify another output device.GPS: Internal error within the device driver's graphics processing. Contact the nearest Customer Support Center. OFIS Graphics, Art Designer: Plotter configuration file was not found A configuration file is needed to intex, rface the graphics application with a plotter. If this file is missing, contact your system administrator.GPS: Invalid CGM-graphics formats encountered in the document being processed by the device driver. OFIS Graphics: No spooler found for this device Pertinent data in the spooler file for the selected printer/plotter is missing. Contact your system administrator. Document Designer: Invalid CGI device. This is an internal Document Designer error and should not occur. Call Technical Support.OFIS .  Graphics, Art Designer, Document Designer: No picture files in this directory In OFIS Graphics and Art Designer, this message is displayed when you use the View Files function and finds no files with a .pic file name extension. In Document Designer, you may also get the message "Object out of range." This indicates an internal Document Designer error and should not occur. Please call Technical Support.OFIS Graphics: Bad input value An incorrect entry was made in a field; for example, an alphabetic c0  haracter was typed in a field requiring a number. Correct your entry.OFIS Graphics: Chart minimum value is out of range The number entered for the minimum value in an OFIS Graphics chart exceeds the acceptable limit. Correct your entry.OFIS Graphics: Chart maximum value is out of range The number entered for the maximum value in a OFIS Graphics chart exceeds the acceptable limit. Correct your entry.GPS: Internal error within the device driver's graphics processing. Contact the nearest Customer Supp2  ort Center. OFIS Graphics: Chart label spacing value is out of range The number entered for the label spacing value in an OFIS Graphics chart exceeds the acceptable limit. Correct your entry.OFIS Graphics: Chart ticks value is out of range The number entered for the chart ticks value in a chart exceeds the acceptable limit. Correct your entry.Reserved.BTOS Graphics II, Art Designer: Invalid printer was specified. A printer was specified incorrectly in SetPlotterDevice. Printer names are limited to4   50 characters. Shorten the printer name. OFIS Graphics: Bad Printer SpecificationBTOS Graphics II, Art Designer, OFIS Graphics: Invalid font was specified. A font was specified incorrectly in AddLabel, ModifyLabel, SetFont, or SetUserFont. Look in the file [Sys]Graphics.Fonts to verify the font specification.BTOS Graphi" d by WriteVDM, contact the source of the CGM file.GPS: Invalid CGM-graphics formats encountered in the document being processed by the device driver. BTOS Graphics II, Art Designer: Invalid CGM opcode:  was read. You have attempted to read a non-CGM file. Check to be sure the file is a CGM file.GPS: Invalid CGM-graphics formats encountered in the document being processed by the device driver. Bad CGM parameter count was encountered. BTOS Graphics II: The CGM interpreter found an entry containing an incorrect count. A CGM entry requires a fixed count. If errors 7696 to 7698 occur on a file generated by WriteVDM, it is an internal error. If the file was not generated by WriteVDM, contact the source < of the CGM file. Art Designer: Bad CGM count. The CGM interpreter found one of the following: - An entry containing an incorrect count. A CGM entry requires a fixed count. - A point list containing an odd number of words. Polylines and Polygons have virtual points (0 through 32767) as parameters, which are indicated as x,y pairs. This error indicates either that an odd number of coordinates is given, or a coordinate is outside the range of 0 to 32767. - A color table opcode having an invalid cou> nt. A color table consists of an index word followed by a list of three word entries, therefore the count must be (3n+1)*2, where n is the number of color entries. If this error occurs on a file generated by WriteVDM, it is an internal error. If the file was not generated by WriteVDM, contact the source of the CGM file.BTOS Graphics II: Bad VDM point list was encountered. A point list contains an odd number of words. Polylines and polygons have virtual points (0 through 32,767) as parameters, whic@ h are listed as x,y pairs. This error indicates that either an odd number of coordinates is given, or a coordinate is outside the range of 0 to 32,767. If errors 7696 to 7698 occur on a file generated by WriteVDM, it is an internal error. If the file was not generated by WriteVDM, contact the source of the CGM file.BTOS Graphics II: Bad VDM color table was encountered. A color table opcode has an invalid count. A color table consists of an index word, followed by a list of three word entries. The couB nt must be (3n+1) * 2, where n is the number of color entries. If errors 7696 to 7698 occur on a file generated by WriteVDM, it is an internal error. If the file was not generated by WriteVDM, contact the source of the CGM file.Document Designer:  Image management disk access error. This indicates that the Document Designer subsystem handling graphics images has encountered an internal error. Call Technical Support.OFIS Graphics: No graphics devices were found on the system No graphics hard copy deviE ces are recognized by the system. Make the appropriate entry for a graphics hard copy device in the Sys.printers file or install a graphics output device using GPS 2.0. Document Designer, OFIS Imager: No graphics hard copy devices are recognized by the system. Install a graphics output device using GPS 2.0.OFIS Graphics: Plotter configuration file was not found Art Designer: No printer configuration. There is no [Sys]Sys.printers file on the system. Create the [Sys]Sys.printers file using G the Editor. BTOS Draw: world is not allocated Reactivate BTOS Draw; if the abort occurs again, call your Unisys representative.OFIS Graphics, Art Designer: No spooler found for this device There is no spooler defined for the selected hard copy device. Create spooler entry in the SpoolerCnfg.sys file. BTOS Draw: An internal BTOS Draw error has occurred There is nothing to delete in the world; nothing seen. Auto error correction is attempted. If BTOS Draw exits with error 7702, reactivate BTOS Draw I  and recover; if the abort occurs again, call your Unisys representative.OFIS Graphics, Art Designer: No Picture Files in This Directory There are no picture files in the current directory. Make certain your pa"  h too many points. Draw the picture again with more than one object. BTOS Draw: Template area is full. Remove unnecessary templates The template area is full, and the template you just attempted to create was not created. To make room for additional templates, remove unnecessary templates using the Remove command.OFIS Graphics, Art Designer: No changes made, gridtW  multiple must be between 1 and 30 Make certain that the grid multiple entered is between 1 and 30, inclusive. BTOS Draw: Function key already assigned, please choose another You cannot overwrite template object function key assignments. Choose another function key or another level to assign to the template object.OFIS Graphics, Art Designer: Chart label would be out of bounds A chart label which was to be drawn would have gone outside of the chart's boundaries. Replace the label if it is to be moveY d outside of the chart's limits. BTOS Draw: Function key is not assigned You pressed a function key that does not th is correct. Enter the name of a directory that contains a .pic file. BTOS Draw: Not enough room for the last operation You cannot create additional objects or you cannot perform Pieces command to break the template object into pieces, because BTOS Draw world is full. If you still want to co,K ntinue, you must either delete unwanted objects or remove unwanted templates using the Remove command.OFIS Graphics, Art Designer: Bad Input Value An incorrect entry was made in a menu field; for example, an alphabetic character was typed in a field requiring a number. Correct your entry. BTOS Draw: An internal BTOS Draw error has occurred There is nothing to delete in the view; nothing seen. Auto error correction is attempted. Reactivate BTOS Draw and recover; if the abort occurs again, call your U8M nisys representative.OFIS Graphics, Art Designer: Chart minimum value is out of range An illegal axis minimum value was specified. Check the chart's data value range and the difference between the minimum and maximum values. The minimum axis value cannot exceed (present minimum value) + [maximum to minimum] x 100. BTOS Draw: view is full Reactivate BTOS Draw and recover; if the abort occurs again, call your Unisys representative.OFIS Graphics, Art Designer: Chart maximum value is out of range An iDO ncorrect axis maximum value was given. Check the chart's data value range and the difference between the minimum and maximum values. The maximum axis value cannot exceed (present maximum value) + [maximum to minimum] x 100. BTOS Draw: bad view number Reactivate BTOS Draw and recover; if the abort occurs again, call your Unisys representative.OFIS Graphics, Art Designer: Chart label spacing is out of Range An incorrect value was specified for axes label spacing. Labels could not be included at specPQ ified spacing. Enter a positive integer for the label space.OFIS Graphics, Art Designer: Chart ticks value is out of range An incorrect value was specified for the number of axes ticks. Be sure the value you enter can be accommodated by the limited space between labels.OFIS Graphics, Art Designer: Bad format for charting parameters An unrecognized signature was in the parameter file passed in from the spreadsheet application to OFIS Graphics or Art Designer.OFIS Graphics, Art Designer: No more charts\S  can be added to the picture The maximum number of charts allowed in a picture file was exceeded.(The number varies with the release level.) Refer to the documentation for the specific release of the application for the maximum number charts allowed in a picture. BTOS Draw: An internal BTOS Draw error has occurred BTOS Draw was unable to load correctly or encountered a problem while running, possibly caused by a corrupted object database. Refer to the BTOS Draw Operations Guide. If that does not hU work, contact your Unisys representative.OFIS Graphics, Art Designer: Too many points drawn A connected line or sketched line was drawn wit# have a template object assigned to it. Press the correct function key; you may need to search for the template level that contains the template object you want to draw.OFIS Graphics, Art Designer: Can't pick that much at one time The maximum number of picked objects allowed at one time was exceeded. Select only a few at a time. BTOS Draw: This template is used in another template and ca[ nnot be removed You have attempted to remove a template that is being used to define other templates objects.OFIS Graphics, Art Designer: No Mouse Service. The Mouse Service was not installed on the workstation. The application requires that the Mouse Service be installed. BTOS Draw: An internal BTOS Draw error has occurred There is no text to be deleted. Auto error correction is attempted. Reactivate BTOS Draw and recover; if the abort occurs again, call your Unisys representative.OFIS Graphics, A]  rt Designer: Grid is suppressed when both work areas are displayed Grid is displayed only when one work area is displayed in a single layout. This message is for information only; it is not an error condition. BTOS Draw: text area is full; label not created Reactivate BTOS Draw, recover, and save. Use less text or make two files.OFIS Graphics, Art Designer: No chart picked in this work area You attempted a chart operation when no chart was selected. Pick a chart before performing the operation. B_ !TOS Draw: text number does not exist Reactivate BTOS Draw using the -Old file.OFIS Graphics, Art Designer: Can only save one chart format file at a time A chart format file can only contain the format of one chart. Make sure only one chart is picked before saving the chart format file. BTOS Draw: This would put an object outside the world You attempted an action that would have placed an object, the cursor, or one of the edges of the screen outside the world.OFIS Graphics: No text found. (Can only a "pick text here.) Art Designer: No pick label. No text was found in the pick box. Select text again. Be sure to pull the icon across the text. When using Text Tools, only text labels can be picked. Use Drawing or Charts Tools to pick other objects.OFIS Graphics: No edge found. (Move across edge with button down.) Art Designer: No pick. No objects were found in the pick box. Pick box must include an edge or surround an object. Select object again. Be sure to pull the icon across at least one edge c #of the object.BTOS Draw: An I/O error has occurred Clean up the disk and recover; if the abort occurs again, call your Unisys representative.OFIS Graphics: Can't zoom in any more Art Designer: Cannot window more. Already zoomed in as far as possible. BTOS Draw: Invalid drawing file format BTOS Draw was unable to open the drawing file you specified because of incorrect format.OFIS Graphics, Art Designer: Bad Icon Library file Data in one of the following files is missing or bad: - OFIS Graphics: e $720x348_80LocSys.Icon or 1024x768_80LocSys.Icon - Art Designer: 720x348_ArtChartIcons.lib or 1024x768_ArtChartIcons.lib. Recopy the file from the distribution disk into [Sys].OFIS Graphics: Bad Icon Library format Art Designer: Bad icon entry Data in the file 720x348_ArtChartIcons.lib or 1024x768_ArtChartIcons.lib is bad. Recopy the file from the distribution disk of into [Sys].OFIS Graphics, Art Designer: Bad Locator Cursor File The file 720x348_80LocSys.Icon or 1024x768_80LocSys.Icon ig %s not in [Sys] or is corrupted. Recopy the file from the distribution disk into [Sys].OFIS Graphics, Art Designer: Too many charts in picture. Excess charts deleted. A maximum of six charts can be included in a single picture. The picture being read in had more than six charts so the extra charts were excluded from the picture. The number of charts varies with the release level. Refer to the documentation for the specific release of the application for the maximum number data groups allowedi &.OFIS Graphics, Art D#  dy been made and you are attempting to (v ,reinitialize the system. You must make a call to cgi_Terminate before you can make the cgi_Initialize call again. OFIS Designer: Object out of range. A graphics object would extend outside the world coordinate space if displayed.CCGI+: CCGI+ not initialized. You are attempting other CCGI+ calls before you make a call to cgi_Initialize. The system must be successfully initialized before other library calls can be used. OFIS Designer: Invalid Link or signature. The verification mechanism of an inter4x -nal data structure has been corrupted. This is an internal error and should not occur. Call the Unisys Customer Support Center.CCGI+: Internal graphics error This is an internal error that indicates a problem in the software you are using or internal inconsistencies due to memory overwrite. Confirm that you are making calls correctly, then contact Technical Support. OFIS Designer: Invalid SuperVAM device or object. A device handle or obesigner: Bad System Font file Depending on the resolution of the monitor being used, the file [Sys]720x348_80Sys.font or [Sys]1024x768_80Sys.font could not be read by the application.OFIS Graphics, Art Designer: Bad Format file The application was unable to read the format file specified in making the chart.OFIS Graphics, Art Designer: Only one page of files can be deleted at a time A user can only select files to be deleted from a single page at a time.OFIS Graphics, Ark 't Designer: Warning: copy box was reduced to fit The size of the copy box was adjusted to fit within the selected viewing area. If necessary, change views.OFIS Graphics, Art Designer: Grid display is simplified for this size and view To prevent overcrowding of the display, the grid may be simplified to show less detail (for example, after returning to Full View). This message is for information only, it does not indicate an error.OFIS Graphics, Art Designer: Warning to Only 200 names can be listed m (The directory contains more than 200 files and only the first 200 can be displayed.OFIS Graphics, Art Designer: Not enough memory to display all fills Too little memory exists for the work area to display some of the fills in the picture on the screen.OFIS Graphics, Art Designer: Replaced unknown fonts, see PICTURE INFO There are unknown fonts in the picture and so the font was displayed using the standard font. Select Show Picture Info in the Files pop-up menu to display a list of the unknown fonts p )which must be entered in the [Sys]Graphics.fonts file to be displayed properly.OFIS Graphics: Unknown fonts & can't display all fills. See PICTURE INFO Unknown fonts were displayed using the standard font in addition to too little memory to display some of the fills. Select Show Picture Info in the Files pop-up menu to display a list of the unknown fonts which must be entered in the [Sys]Graphics.fonts file to be displayed properly.Reserved.OFIS Graphics, Art Designer: No picture information r *to report Show Picture Info was selected in the Files pop-up menu for an empty .pic file. This message is for information only; it does not indicate an error.OFIS Graphics, Art Designer: No printing status to report Printer Status was selected in the Print pop-up menu when printing activity is absent. This message is for information only; it does not indicate an error.Reserved.OFIS Graphics, Art Designer: Feature not implemented Displayed when any selected feature is not coded into the current releast +e of the run file.CCGI+: No graphics available. This workstation does not have the necessary graphics hardware. OFIS Designer: Invalid CGI device. The device handle specified does not describe a valid device.CCGI+: Invalid icon or cursor. The passed pointer to an icon or cursor is invalid. Confirm that the pointer is valid. OFIS Designer: Bad CGI state. This indicates a software error.CCGI+: CCGI+ previously initialized. A call to cgi_Initialize has alrea$ ject handle given to a SuperVAM procedure does not describe a v@z .alid SuperVAM device or object.CCGI+: Insufficient memory. No more memory is avaiable to perform the requested operation. Allocate more memory on initialization or change your partition size. OFIS Designer: Resource in use. A bitmap or other resource cannot be deleted because it is currently being used by some device.CCGI+: Invalid device handle The device handle you have passed is invalid for this operation. Confirm that you are passing a device handle returned from a successful call to cgi_OpL| /enWk, and confirm that you are passing a device handle (as opposed to a cursor or bitmap handle).CCGI+: Parameter out of range The value you have given for a parameter to a CCGI+ call is out of the valid range. Refer to the CCGI+ Programmer's Guide for parameter restrictions.CCGI+: Invalid device for procedure Not all CCGI+ calls are valid to all devices. You have attempted a call with a device handle representing a device that does not support this call. Refer to the CCGI+ Programmer's Guide for parX~ 0ameter restrictions.CCGI+: Invalid bitmap handle The bitmap handle you have passed is not valid. Confirm that it is a handle returned from a successful cgi_OpenWk of a bitmap device, or a successful cgi_CreateBitMap.CCGI+: Invalid cursor handle The cursor handle you have passed is not valid. Confirm that it is a handle returned from a successful cgi_OpenCursor.CCGI+: Value out of number range The value has been calculated to fall outside the CCGI+ maximum integer range of -32767 to 32767. Choose d 1a smaller VDC extent so values outside the VDC extent do not exceed the limits of the numbers range.CCGI+: Standard font not specified. The font handling code could not locate the standard font whose format is resolution_80sys.font (for example, 1024x768_80Sys.font). It should reside in your [Sys] directory.CCGI+: Invalid CCGI+ device The device type specified as input to cgi_OpenWk was not recognized. Confirm that it is one of the valid device types specified in the CCGI+ Programming Guide.CCGp 2I+: Insufficient cursors enabled. An attempt has been made to open more cursors than the maximum allowed (defined as input to cgi_Initialize). Increase the number of cursors enabled when CCGI+ is initialized.CCGI+: Fonts not enabled Memory has not been allocated for fonts because the number of font descriptors specified as input to cgi_Initialize is insufficient. Increase the number of font descriptors enabled when CCGI+ is initialized.CCGI+: Fonts not enabled Memory has not been allocated for fonts| 3 because the number of font descriptors specified as input to cgi_Initialize is insufficient. Increase the number of font descriptors enabled when CCGI+ is initialized.CCGI+: Standard font not enabled Memory for the default font was not allocated at initialization time. Change the appropriate flag to cgi_Initialize, so that memory for the default font will be allocated.CCGI+: Bitmaps not enabled Memory for bitmaps, other than the display bitmap, was not allocated at initialization time. Change the ap 4propriate flag to cgi_Initialize so that memory for offscreen bitmaps will be allocated.CCGI+: Invalid Tiff compression scheme A compression scheme that is not supported currently has been encountered; processing cannot proceed. Try converting the file to use another compression scheme.CCGI+: One Tiff device allowed open at a time An attempt has been made to open a Tiff device when another Tiff device is currently open. You must close the first Tiff device in order to open another.CCGI+: One bitmap p 5er Tiff allowed An attempt has been made to put more than one bitmap in a single Tiff file. Try copying all the required bitmaps to a single offscreen bitmap. Then copy that bitmap to the Tiff file.CCGI+: Odd CGM parameter count CGM files contain entries that are word-aligned. This error occurs when an entry contains an odd number of parameter b$   This error is often returned when attempting to read non-PIC files. Check to be sure that the file is a picture file. This error prevents further processing of the picture file.CCGI+: Invalid logical file address. The LFA giv <en is invalid. The ending LFA must be larger than the beginning LFA.CCGI+: Picture file processing error The values within the picture file cannot be translated properly into CCGI+ calls. Picture files are generated by GRAPHICS.LIB applications such as Art Designer and OFIS Graphics. The picture file is most likely corrupt or has parameter values that CCGI+ is not designed to handle.Reserved.CCGI+: Unable to delete bitmap The bitmap specified to be deleted is currently in use. Select another bitmap  =as the drawing bitmap before making this call.Reserved.CCGI+: Memory Handling Error Check code logic for overwriting, or increase memory available for CCGI+. Document Designer: No free file number Too many Virtual Memory files open. Close some files aytes. If this error occurs on a file generated by CCGI+, it is an internal error. Contact Technical Support. If the file was not generated by CCGI+, contact 6 the source of the CGM file.CCGI+: Invalid CGM opcode The opcode for a CGM entry is invalid. This error is often returned when attempting to read non-CGM files. Check to be sure the file is a CGM file.CCGI+: Invalid CGM parameter count The CGM interpreter found one of the following: - An entry containing an incorrect count. A CGM entry requires a fixed count. - A point list containing an odd number of words. Since points are x,y pairs of integers, an odd number of coordinates was given. - A color 7 table entry having an invalid count. A color table entry is an index word followed by a list of three word entries so the byte count must be (3n+1)*2 where n is the number of color entries. If this error occurs on file generated by CCGI+, it is an internal error. Contact Technical Support. If the file was not generated by CCGI+, contact the source of the CGM file.CCGI+: Incomplete CGM file This error occurs if the CGM interpreter expects more data and encounters an EndOfFile.CCGI+: Illegal viewport  8call If the device is a CGM or GPS device, the viewport must be set as the first call to the device. This error occurs when other calls have been made to the device, and then an attempt is made to write the viewport. Ensure that a call to cgi_Viewport is the first call to the device.CCGI+: One GPS device allowed open at a time An attempt has been made to open a GPS device when another GPS device is currently open. You must close the first GPS device in order to open another.CCGI+: One CGM device alloĐ 9wed open at a time An attempt has been made to open a CGM device when another CGM device is currently open. You must close the first CGM device in order to open another.CCGI+: No physical information in CGM file In order to scale CGM files into windows based on physical dimensions, the physical information about picture size must be stored in the CGM metafile. CCGI+ provides this capability by allowing a cgi_Viewport call to a CGM device, which writes the physical information into the file through anВ : escape opcode. Physical information is necessary for some scaling options upon CGM interpretation. Either write the physical information into the CGM file, or read the CGM file into a window that is not based on the physical size of the image.CCGI+: GPAM not enabled. This error occurs when an attempt is made to use a GPMA call when the program has not been linked with GPAM.LIB. Ensure that the program has been linked with GPAM.LIB if printing services are necessary, or read the CGM file into a window ܔ ;that is not based on the physical size of the image.Reserved.CCGI+: Invalid picture file opcode An invalid picture file opcode has been encountered. Picture files are generated by GRAPHICS.LIB applications such as Art Designer and OFIS Graphics. Valid opcodes are from 0 to 13.% nd save before opening more files.CCGI+: Memory Handling Error Check code logic for overwriting, or increase memory available for CCGI+. Document Designer: Bad file number. Virtual file address specified in Virtual Memory operation contains an invali >d file number.CCGI+: Memory Handling Error Check code logic for overwriting, or increase memory available for CCGI+. Document Designer: Bad virtual file address. Virtual file address specified in Virtual Memory Operation is invalid.CCGI+: Memory Handling Error Check code logic for overwriting, or increase memory available for CCGI+. Document Designer, OFIS Designer: Read only buffer. Attempt to write to a Virtual Memory buffer which is available for reading only.CCGI+: Memory Handling Error Chec  ?k code logic for overwriting, or increase memory available for CCGI+. Document Designer, OFIS Designer: Lock error. Operation failed because Virtual Memory buffer was locked or because buffer lock count overflowed.CCGI+: Memory Handling Error Check code logic for overwriting, or increase memory available for CCGI+. Document Designer, OFIS Designer: No free buffer ID. Operation failed because all Virtual Memory buffers are locked.CCGI+: Memory Handling Error Check code logic for overwriting, or inc @rease memory available for CCGI+. Document Designer, OFIS Designer: Bad buffer ID. Invalid VM buffer block id.CCGI+: Memory Handling Error Check code logic for overwriting, or increase memory available for CCGI+. Document Designer, OFIS Designer: Inconsistency in VM data structures.Reserved.CCGI+: Bad heap selector Document Designer, OFIS Designer: Bad address. The selector for the pointer does not exist in the heap selector table. This probably indicates an invalid heap pointer or heap corrupti$ Aon. This is an internal error related to memory and heap management in the software. Call Technical Support.CCGI+: Heap selector table overflow Document Designer, OFIS Designer: Heap Address table overflow. An attempt has been made to allocate more selectors for heap pointers than there is space in the heap selector table. This is an internal error related to memory and heap management in the software. Call Technical Support.CCGI+, Document Designer, OFIS Designer: Heap inconsistency. Inconsiste0 Bncy in heap data structures. This is an internal error related to memory and heap management in the software. Call Technical Support.CCGI+, Document Designer, OFIS Designer: Bad heap finger table Inconsistency in heap node handle mapping table. This is an internal error related to memory and heap management in the software. Call Technical Support.CCGI+: Bad heap count of paragraphs Memory-ordered heap node chain broken: count of paragraphs in heap node invalid. This is an internal error related t< Co memory and heap management in the software. Call Technical Support. Document Designer, OFIS Designer: Bad node link.CCGI+, Document Designer, OFIS Designer, OFIS Graphics: Bad heap free list Inconsistency in the heap free list. This is an internal error related to memory and heap management in the software. Call Technical Support.CCGI+, Document Designer, OFIS Designer, OFIS Graphics: Bad heap node tag Invalid tag in heap node. This probably indicates a heap corruption.CCGI+, Document DesigneH Dr, OFIS Designer, OFIS Graphics: Bad heap finger The node handle in a heap node does not match the index into the node handle mapping table. This is an internal error related to memory and heap management in the software. Call Technical Support.CCGI+, Document Designer, OFIS Designer, OFIS Graphics: Bad heap handle An attempt has been made to fetch a node using an invalid node handle. This is an internal software error related to memory and heap management in the software. Call Technical Support.CCGT EI+, Document Designer, OFIS Designer, OFIS Graphics: Lock count error. Node lock count overflow or underflow. This indicates a software error, such as mismatc%  fileheaders.sysMfd.sysLog.sys SysImage.sys BadBlk.sys Crashdump.sys,System Utilities Diskette 8 of 13 (B25STU-8) fdSys.Versionhed node allocations and releases. This is an internal error related to memory and heap management in the software. Call Technical Support.CCGI+, Document Designer, OFIS Designer: Heap node locked A heap operation, such as an attempt to free or resize a heap node, failed because the heap node is locked. This is an internal error related to m` Femory and heap management in the software. Call Technical Support.CCGI+, Document Designer, OFIS Designer, OFIS Graphics: Heap resize failed An attempt to shrink or move the heap failed, most likely because nodes in the heap are locked. This is an internal error related to memory and heap management in the software. Call Technical Support.CCGI+, Document Designer, OFIS Designer: Heap node too large An attempt to allocate or grow a heap node failed because the size requested is larger than the maximul Gm node size. This is an internal error related to memory and heap management in the software. Call Technical Support. If this error occurs in Document Designer, save your edits more often.CCGI+, Document Designer, OFIS Designer: Heap full. Cannot complete operation (allocate or grow a heap node, or shrink the heap) because there is insufficient free space remaining in the heap. If this error occurs in Document Designer, save your edits more often. This is an internal error related to memory and heap x Hmanagement in the software. Call Technical Support.CCGI+: Bad font specification. A font key could not be built for this font specification. Make sure that the font names in the font file are valid. This is an internal error related to memory and heap management in the software. Call Technical Support.CCGI+: Text positioning error. This error occurs when the font in combination with the requested height and spacing cannot fit into a bounding box. Choose another font, or adjust the text parameters.  I This is an internal error related to memory and heap management in the software. Call Technical Support.CCGI+: Invalid formatted string. The formatted string input could not be interpreted. Check the opcodes and parameters being sent. This is an internal error related to memory and heap management in the software. Call Technical Support.CCGI+: Font index not defined. The font index being queried is not defined. This is an internal error related to memory and heap management in the software. Call J Technical Support.Reserved.Document Designer, OFIS Designer: No more charts can be added to the picture. If you are creating a picture composed of multiple graphs and this message displays, you cannot add more graphs. The exact number of graphs that can be displayed is currently six.Reserved.Document Designer, OFIS Designer: No chart picked in this work area. This message is displayed when you are working with charts and attempt to perform a task that requires a picked chart, but no chart is picke Kd. Pick a chart and try again.Reserved.Document Designer, OFIS Designer: No text found & /  03433-8/13 l l% Mf9|M^SysUnisys9{fileheaders.sys Sysh lh lh lJJ#Mfd.sys Sysi li li lLog.sys Sysj lj lj lz SysImage.sys Sysk lk lk l BadBlk.sys Sysm lm lm l&  -o ,n v Crashdump.sys Sysm lm lm lI,System Utilities Diskette 8 of 13 (B25STU-8) Sysu lu lu lqf fdSys.Version Sysr lt lt lA StatuscodesMsg.Bin.01 Unisys z l l2l<@  StatuscodesMsg.Bin.02 Unisys  l l l.p ' +m*l)k(j'i&h%g$f'  _^#e"d!c ba`( ]\ [ !Z!"Y"#X#$|$StatuscodesMsg.Bin.01 (   not set when expected.Communications: Illogical device status. This is an internal error that indicates a problem in the software you are using.Communications: No data. This is an internal error that indicates a problem in the software you are using.Communications: Terminate read or internal consistency check. This is an internal error that indicates a problem in the software you are using.Communications: Break or selected. A break character may have been ؿ Preceived. This is an internal error that indicates a problem in the software you are using.Communications: Parity error. This is valid only for ASCII mode.Communications: Host received NAK. When the Control Unit Emulator receives a Negative Acknowledgement in response to a text transmission, the Control Unit Emulator retransmits the last block of text.Reserved.Server/Cluster Workstation communications: Timeout A workstation no longer responds to polling. BSC 2780/3780 RJE: The host computer fa Qiled to respond t(can only pick text here). When you have the Text Tools menu displayed, only text can be picked. Select either the Chart or Drawing Tools menus to pick other objects.Document Designer, OFIS Designer: No edge found. (Move across edge with the MARK key down. When you pick an object, you must move the Box cursor across an edge of the object or surround the object. Try to pick up the object again.Reserved.Reserved L.Communications: Buffer overrun. Maximum size of receive data buffer was exceeded. This status code indicates a breakdown in protocol or possible hardware problems.Communications: Lost Clear To Send. Lost carrier during reception. This generally indicates a modem problem. BSC 2780/3780 RJE: This error causes an automatic sign off from the host computer. The Signon RJE command must then be used to re-establish communications with the host.Communications: Lost carrier during reception. This indic Mates a problem with the modem or transmission facilities, or at the host computer site. BSC 2780/3780 RJE: This error causes an automatic sign off from the host computer. The Signon RJE command must then be used to re-establish communications with the host.Communications: Invalid asynchronous communication request.Communications: Character overrun detected. Receive buffers in SIO were full and another character was received, overwriting the last character. This status code indicates a possible hardwa Nre problem.Communications: Parity error detected. There is a bad data communication line or possible hardware problems.Communications: Framing error detected. In asynchronous mode, this status code indicates loss of stop bits at the end of the received character. In synchronous mode, the comparison between received and calculated CRCs failed. There is a bad data communication line or possible hardware problems.Communications: Invalid asynchronous communication parameters.Communications: Data Set not̽ O ready The DataSetReady (DSR) signal was) o a transmission. This status code may indicate a total break in communications. Enhanced BSC 3270 Agent: If there is no activity from the host, the agent will MAKE LINE NOT READY and log the error in the MCM Error log file. Shared resource processor:  Protocol failure. Communications between a CP or GP and a cluster terminal are corrupted or nonexistent. Possible causes include improperly terminated cluster lines, a faulty RS-422 port on the processor, and faulty cable. The total le Rngth from the beginning of an RS-422 channel on the CP or GP board to the end of the cluster line can be up to 1200feet at baud rates of either 307Kbps or 1.8Mbps. This 1200-foot maximum length is a total of all cable lengths between cluster terminals and consequently between cluster line terminators. Make sure that both lines associated with a cluster port are properly terminated using an RS-422 100-ohm terminator. Check that all RS-422 cables are properly connected and not defective.Server/Cluster W Sorkstation communications: Invalid state. Run the crash dump analyzer if available. The error condition causes termination of the operating system and an automatic reload.Server/Cluster Workstation communications: Communications hardware failure. The error condition causes termination of the operating system and an automatic reload. Run the workstation hardware diagnostics.Server/Cluster Workstation communications: Protocol failure detected by the server workstation. The error condition causes ter Tmination of the operating system and an automatic reload. A cluster workstation no longer follows proper protocol procedure. The frame received does not match the expected frame type. This can be caused by a hardware failure (including cabling) or or more than one server (formerly master) on a line. Shared resource processor: Protocol failure. Possible causes include improperly terminated cluster lines, a faulty RS-422 port on the processor, and faulty cable. The total length from the beginning of U an RS-422 channel on the CP or GP board to the end of the cluster line can be up to 1200feet at baud rates of either 307Kbps or 1.8Mbps. This 1200-foot maximum length is a total of all cable lengths between cluster terminals and consequently between cluster line terminators. Make sure that both lines associated with a cluster port are properly terminated using an RS-422 100-ohm terminator. Check that all RS-422 cables are properly connected and not defective.Server/Cluster Workstation communications:  V Invalid Direct Memory Access (DMA) buffer address. An error in system initialization has caused the DMA buffer of the Cluster Workstation Agent Service Process to fall outside the low-order 128K bytes of memory or on an odd-byte boundary.Server/Cluster Workstation communications: Busy Bit I/O. An error has occurred in the Cluster Line Protocol or the shared resource processor Line Protocol Handler. The error condition causes operating system termination and an automatic reload. This is an internal er, Wror that indicates a problem in the software you are using. Consult the Unisys Customer Support Center.Server/Cluster Workstation communications: Invalid Command bit (Busy Bit) I/O. This is an internal error that indicates a problem in the software you are using. Consult the Unisys Customer Support Center.Server/Cluster Workstation communications: An unexpected interrupt was detected while attempting to transmit or receive data.Server/Cluster Workstation communications: Transmit DMA underrun.Server/8 XCluster Workstation communications: Protocol failure detected by a cluster workstation. This is an internal error that indicates a problem in the software you are using. The cluster workstation indicates that the server (formerly master) workstation is no longer following proper protocol procedures. This can be caused by a hardware failure (including cabling) or excessive Multibus DMA loading. In protected mode, this is caused by the s)   A reject (REJ) was received from the cluster workstation. The workstation detected a protocol violation and sent a reject to the server  _(formerly master).Server/Cluster Workstation communications: Abort. An RcvAbort was detected while reading from the cluster workstation.Server/Cluster Workstation communications: Read not complete. The system got an interrupt for read complete, but the read complete bit is not set in the 2652 status word.Server/Cluster Workstation communications: SetUpCommDma read back a different DMA address than was just written.Reserved.BSC 2780/3780 RJE, BSC 3270: Abort. The host received an EOT (End of Transmiss `ion) during transmission. Any further attempt to transmit the current file has been abandoned.BSC 2780/3780 RJE, BSC 3270: Busy BSC I/O. The user is trying the initiate a communication channel while data I/O is in operation.BSC 2780/3780 RJE, BSC 3270: Invalid BSC command I/O. The BSC I/O command request was invalid.BSC 2780/3780 RJE, BSC 327erver going down and coming up again, or by multiple services (formD Yerly servers) on the line.Reserved.Server/Cluster Workstation communications: An error in the hardware (SIO or cabling) on the cluster line has caused a temporary inability of the cluster workstation to communicate with the server (formerly master) workstation.Server/Cluster Workstation communications: Server workstation disconnect. An unrecoverable protocol failure has occurred at the server (formerly master) workstation and further communications with this workstation have ceased. The most likely causP Zes are: - A duplicate workstation identification somewhere within the cluster (if so, the workstation with the duplicate identification should have simultaneously crashed with this error). - A hardware failure (including cabling). - Excessive Multibus DMA loading.Server/Cluster Workstation communications: Request block error. An improperly formatted request block was sent by a workstation.Server/Cluster Workstation communications: Read not complete. The system received an interrupt for Read Complete,\ [ but the Read Complete bit is not set. Shared Resource Porcessor: Timer failure.Server/Cluster Workstation communications: Bootstrap failure. A protocol failure occurred during the bootstrap process.Server/Cluster Workstation communications: No IDs. The ID search algorithm was unable to find a free ID. In general, this indicates that the system build performed for the operating system currently running on the server (formerly master) workstation specified too few IDs for the cluster configuration.Serh \ver/Cluster Workstation communications: ID search failure. The ID search algorithm found a free ID but was unable to lock onto it for use.  In general, this indicates a serious hardware or software problem.Server/Cluster Workstation communications: Bad address. The ID field received from a workstation did not match the ID field sent to that workstation. This could be due to a hardware failure or to more than one server (formerly master) on the same cluster.Server/Cluster Workstation communications: Bat ]d length. The length of the data received did not match the length of the data sent by the cluster workstation. This could be due to a hardware failure.Server/Cluster Workstation communications: Bad sequence. The sequence number of the IFrame received from the workstation did not match the expected sequence number. The expected first number is zero, then 1, 2, ...7, and then zero again.Server/Cluster Workstation communications: Cyclical Redundancy Check error. A Cyclical Redundancy Check (CRC) error ^ is due to a line transmission error. This could be a hardware failure or a problem with the communications line.Server/Cluster Workstation communications: Overrun error. An overrun error was detected by the communications chip. The sending station wanted to transmit more bytes than the DMA was told to receive.Server/Cluster Workstation communications: Reject error.* 0: An invalid character sequence was detected. BSC 2780/3780 RJE: This occurs if an invalid character is received after a DLE in transparent mode or number of c aharacters transmitted is greater than the number in the transmit buffer. This indicates possible protocol problems. BSC 3270: An invalid character was received after a DLE (Data Link Escape) in transparency mode. The number of characters transmitted is greater than the number in the transmit buffer.BSC 2780/3780 RJE, BSC 3270: An invalid response to a line bid was received from the host computer. This is probably due to a problem in the host software or configuration. For example, in BSC 2780/3780 RJ bE, it would occur if the host were configured to support a HASP Multileaving Workstation rather than a 2780/3780 terminal. Enhanced BSC 3270 Emulator Driver: If the host sends an unexpected message, the agent will MAKE LINE NOT READY and log the error in the MCM Error log file.BSC 2780/3780 RJE, BSC 3270: Host down. The host is not polling. Enhanced BSC 3270 Emulator Driver: If the host is down and not polling, the agent will MAKE LINE NOT READY and log the error in the MCM Error log file.BSC 2780/378 c0 RJE, BSC 3270: Invalid format error.BSC 3270: Invalid 3270 command. A subsystem error in the 3270 emulator.BSC 3270: Unexpected response. A subsystem error in the 3270 emulator.BSC 2780/3780 RJE, BSC 3270: Buffer too small. The buffer must be large enough to accept the longest EBCDIC transmission from the host, which may be larger than the screen size.BSC 3270: Request from unknown workstation. Open3270Emulator must be the first request issued. The device request issued and the device address in d all subsequent requests must match the one returned from Open3270Emulator.BSC 3270: Too many workstations. No available device. The number of device addresses already assigned is equal to the maximum set at system build; no further Open3270Emulator requests can be honored.BSC 3270: Command Reject. Subsystem error in the 3270 emulator.BSC 2780/3780 RJE: Protocol failure during reception. BSC 3270: Protocol failure after selection. A valid selection was received; however, procedures were unable to s euccessfully receive a data block from the host computer.BSC 2780/3780 RJE: Excessive retries. Protocol failure during transmission. BSC 3270: Protocol failure after poll. A valid poll sequence was received; however, the normal BSC error recovery procedures were unable to sucessfully transmit a data block to the host computer.BSC 3270: Assigned different. 3270 already open. On using the Virtual Terminal Interface (VTI), the user has called the Open3270Emulator procedure without first calling Close327 f0Emulator.BSC 2780/3780 RJE, BSC 3270: Cancel. The StartEmulator request returned to the VTI was due to a timeout condition while waiting for host data or host line activity.BSC 2780/3780 RJE, BSC 3270: CRC error. A Cyclical Redundancy Check (CRC) from the receive data does not match the CRC included in the data. The possible cause is line noise or a line error that modifies one or more bits during transmission.BSC 2780/3780 RJE, BSC 3270: Interrupt. Reverse interrupt received from host. Transmissio gn was terminated.BSC 2780/3780 RJE, BSC 3270: Sequence error. An attempt was made to sign on when already signed on, or to sign off when already signed off or not idle.BSC 2780/3780 RJE: Not RJE Request. Not Remote Job Entry request. Invalid request code for RJE system service.BSC 2780/3780 RJE, BSC 3270: Disconnect. Communications line is disconnected. BSC 2780/3780 RJE: The error causes an automatic sign off from the host computer. The Signon RJE command must then be used to re-establish commu hnications with the host. Enhanced BSC 3270 Emulator Driver: If the communication line is disconnected, the agent will MAKE LINE NOT READY and log the error in the MCM Error log file.BSC 2780/3780 RJE: Disconnect. Communications line is disconnected.*  have a DCX or XC-002, refer to the Installation and Configuration Guide for the line number. Shared Resource Processor: The port number for OpenTerminal must be between 1 and 10 for a Terminal Processor, and between 1 and 3 for a Cluster Processor.Communications Interrupt Handlers: Line in use. The line specified in InitCommLL oine is being used by the operating system. The specified line number is currently in use by other communciations software, For example, if you are attempting to use Channel B, the Spooler may have opened that channel for a serial printer or another communication service, such as BSC 2780/3780 RJE, may be using it. If you are using a master IWS that does not have a CommIOP board, remember that Channel A is usually not available for an RS-232-C serial connection.Communications Interrupt Handlers: A requX pest was made to start programmable terminal emulation on a cluster workstation that is already in programmable terminal emulation mode.Communications Interru The error causes an automatic sign off from the host computer. The Signon RJE command must then be used to re-establish communications with the host. BSC 3270 Terminal Emulator: Invalid device. The device number specified is not in the valid range of 0  ithrough 31.BSC 2780/3780 RJE, BSC 3270: Device in use. The user has selected a device number that is in use by someone else. BSC 2780/3780 RJE: The error causes an automatic sign off from the host computer. The Signon RJE command must then be used to re-establish communications with the host.BSC 2780/3780 RJE, BSC 3270: Invalid screen profile. The user has selected a screen profile not supported on a workstation in use.BSC 2780/3780 RJE, BSC 3270: Invalid mode. When installing the system printer, t jhe user selected a mode that is not supported.BSC 2780/3780 RJE: This error code is returned by Deinstall RJE if an attempt is made to deinstall RJE on an Single partition operating system; from another workstation; or while Context Manager is installed. BSC 3270 Terminal Emulator: Invalid timeout.BSC 2780/3780 RJE, BSC 3270: The reset key was used, cancelling a previously outstanding program attention request.BSC 2780/3780 RJE, BSC 3270: From Ir. The "from" device specified in the COPY command is not k available.BSC 2780/3780 RJE, BSC 3270: From Locked. The "from" device specified in the COPY command has a locked buffer.BSC 2780/3780 RJE, BSC 3270: From Busy. The "from" device specified in the COPY command is busy.BSC 2780/3780 RJE, BSC 3270: Service already installed. The system service has already been installed.BSC 2780/3780 RJE, BSC 3270: Cannot deinstall. Deinstall command was invoked on a single partition operating system or from a workstation other than where the install command was execut( led. Use the deinstall command on the workstation where the install command was executed, where a multipartition operating system is running.BSC 2780/3780 RJE, BSC 3270: Node name and Service ID specified in parameter for CRT Subsystem or Printer Subsystem is longer than 64 characters (including the curly and angle brackets).BSC 3270: This error code is returned by the CRT or Printer Subsystems if the BSC 3270 driver has been deinstalled. BSC 3270 releases prior to 7.0: On a single-partition operating4 m system, the memory used by printer subsystems cannot be recovered; if the driver is subsequently reinstalled, the printer subsystem must be reinstalled.BSC 3270: This error code is returned if you attempt to deinstall the BSC Driver while there is a Printer Subsystem installed. Deinstall all Printer Subsystems before deinstalling the driver.Reserved.BSC 2780/3780 RJE, BSC 3270: A line bid was received from the host in response to your line bid when in bid state. Control of the line was relinquished to @ nthe host.Reserved.Communications Interrupt Handlers: Invalid line number. Workstation: The line number specified in InitCommLine and ResetCommLine must be either 0 or 1. If you + pt Handlers: A request was made to stop programmable terminal emulation on a cluster workstation that was not in programmable terminal emulation mode.Reserved.X.25 LAPB Link Level: Link level down. The link level of the X.25 Network Gateway system service is not operational. This situation occurs either at power up, before communication with the PDNd q is established, or during operation, if an irrecoverable link level error occurs. The X.25 Network Gateway system service link level software should reestablish communication as soon as possible. If the link level remains down for an extended period, an irrecoverable error at the physical level or the link level exists. You should contact a PDN representative.X.25: The packet level of the X.25 Network Gateway system service is down and not operational. The situation occurs at power up, during operatp rion following a link level failure and subsequent reestablishment of link level communications, or following an irrecoverable packet level error condition. The packet level system service should reestablish itself as soon as possible. If the packet level remains down for an extended period, you should contact a PDN representative.X.25: Maximum number of this request has been queued. Previously submitted requests of this type must be completed before more can be issued. The maximum number of each requ| sest type is as follows: NotifyNextIncomingCall requests: the number of virtual circuits per line. ReadX25Packet requests: two per virtual circuit. WriteX25Packet requests: five per virtual circuit. All other Packet Access Method operation requests: one per virtual circuit. Since the packet level should complete requests in a short time, the request should be resubmitted. If this condition persists, QueryX25Status should be used to examine the state of the X.25 Network Gateway system service to determi  tne the cause of the delay.X.25: The packet level system service is busy. Insufficient memory is available for the packet level system service to process any more requests at this time. In normal operation, the X.25 Network Gateway system service should complete enough requests to free the memory required to accept new requests. If this error persists, consider reinstalling the packet level with additional memory.X.25: Process termination. All requests were (or shortly will be) returned and all virtu  ual calls were (or shortly will be) cleared because your process has terminated.X.25: A NotifyNextIncomingCall operation contains a port range with one of two error conditions: - The high port number is less than the low port number. - The low and/or high port number is not in ASCII digits.X.25: No virtual circuit available. An InitiateX25Call operation was received, but all virtual circuits were either in use or out of order.X.25: A user-specified time-out has occurred. A ReadX25Packet or a NotifyNex  vtIncomingCall operation could not be fulfilled by the packet level during the specified maximum time.X.25: The virtual circuit is in use. A request was received for a virtual circuit (or permanent virtual circuit) that is already in use.X.25: There was a call collision. An incoming call was received on a virtual circuit before an InitiateX25Call operation that had been allocated to that virtual circuit could be completed. The process should resubmit the InitiateX25Call operation.X.25: The call has bee wn cleared. An AcceptX25Call operation was made on a circuit for which no call was pending.X.25: Virtual circuit not in use. A request was received for a virtual circuit (or permanent virtual circuit) that was not allocated to any user.X.25: DTE clear. Either an erroneous packet was received from the PDN, or the process requested that the call be terminated. The packet level system service cleared the call that was on this virtual circuit. Data in the process of being transferred may have been lost.X. x25: DCE clear. The PDN cleared the call that was on this vi+   ~ase. Refer to your application documentation for the packet sizes for your release.X.25: Maximum number of permanent VCs exceeds the total number of VCs assigned.X.25: Number of incoming-only VCs exceeds the total number of VCs assigned.X.25: Number of outgoing-only VCs exceeds the total number of VCs assigned.X.25: Total of all outgoing-only VCs, incoming-only VCs, and permanent VCs exceeds the assigned number of VCs.X.25: Either the window size specified in the packet level configuration file is inc  orrect or an invalid entry, or you need to check your PDN service to see if they can accept the window size you designated.X.25: Either the window size specified in the packet level configuration file is incorrect or an invalid entry, or you need to check your PDN service to see if they can accept the window size you designated.X.25: The address specified in the packet level configuration file is too long.X.25: Invalid frame modulus value entered in the link level configuration filrtual circuit. Data in the process of being transferred may have been lost.X.25: DTE reset. Either an erroneous packet was received from the PDN, or the process requested the call be reset. The packet level system service reset the call on this virtual circuit. Data in the process of being transferred may have been lost.X.25: DCE reset. The PDN reset the call on this virtual circuit. Data in the process of being transferred may have been lo yst.X.25: DTE restart. An erroneous packet was received from the PDN, and the packet level system service was restarted. All active calls were cleared. Data in the process of being transferred may have been lost.X.25: DCE restart. The PDN restarted the packet level. All active calls were cleared. Data in the process of being transferred may have been lost.X.25: Virtual circuit is not in data transfer mode. A read, write, reset, or interrupt request was received for a virtual circuit that was not in z the correct state. Either no call was present or the circuit was being cleared or reset.X.25: Interrupt data. This indicates normal completion of a read request, but with an interrupt data packet rather than a normal data packet. Interrupt data are returned to the process before any normal packets being held for the process by the packet level.X.25: Virtual circuit out of order. An irrecoverable error occurred on this virtual circuit, and the packet level system service declared it out of order. All  {calls on this circuit were cleared. The circuit can be restored only by the PDN.X.25: Internal time out. The PDN did not respond to the packet generated by the request in the required time period. The process should resubmit the request.X.25: Invalid virtual circuit number. Either one of the following conditions exists: - A request was received for a virtual circuit with a vch parameter that is either out of bounds or is 0 (circuit 0 is reserved). - A ConnectX25Permanent operation was received for a | nonpermanent virtual circuit.X.25: Data has been truncated. Data to be returned to the process exceeded the size of sPacketRet as specified by the process. The data was truncated to the size of the buffer.X.25: No buffer size allocated. A read or write operation was attempted, with sBuffer equal to 0.X.25: A ClearX25Call or AcceptX25Call was issued with the vch parameter of a permanent virtual circuit.X.25: The number of VCs requested at X.25 installation time is not enough to support the current sy }stem configuration. There must be at least one VC per workstation in a cluster environment.X.25: The number of VCs requested when the packet level was installed exceeds the maximum number of 32 VCs.X.25: You have an invalid maximum packet size value. Either the maximum user data must be changed in the link level configuration file, or the maximum packet size must be reduced. The maximum packet size values are 16, 32, 64, 128, 256, 512, 1024, 2048, or 4096. Note that the packet size varies with the rele, e. Only modulus 8 is s" upported.X.25: Invalid PDN type. PDN specified is incorrect. The PDN parameter is located in the link level configuration file. Be sure you are using the correct number to designate your PDN service. The valid values are 0 through 7.X.25: An install parameter string is too long.HDLC: The LAPB parameter, X.21 Leased or Switched, contains an invalid entry.HDLC LAPB and NRM, and X.25 LAPB: The LAPB parameter X.21 CSS service ID is either greater than 12 characters or is not surrounded by angle brackets$$ . SNA Transport: An invalid ServiceID has been entered into the X.21 CSS ServiceID field in the X.21 configuration file.HDLC LAPB and NRM, and X.25 LAPB: The LAPB parameter X.21 Call Direction contains an invalid entry. SNA Transport: A value other than I or O has been entered into the X.21 Call Direction field in the X.21 configuration file.HDLC LAPB and NRM, and X.25: The LAPB or NRM parameter X.21 CUG Index contains an invalid entry. SNA Transport: An invalid value has been specified for the X.210&  CUG Index in the X.21 configuration file.HDLC LAPB and NRM, and X.25 LAPB: The LAPB or NRM parameter X.21 Reverse Charging contains an invalid entry. SNA Transport: An invalid entry has been made into the X.21 Reverse Charging field in the X.21 configuration file.HDLC LAPB and NRM, and X.25 LAPB: The LAPB or NRM parameter X.21 Address Type contains an invalid entry. SNA Transport: A value other than F or A has been specified in the X.21 Address Type field in the X.21 configuration file.HDLC LAPB and <( NRM, SNA Transport, and X.25 LAPB: X.21 Call Verification was selected, but no valid address file was specified.HDLC LAPB and NRM, and X.25 LAPB: The LAPB or NRM parameter X.21 Call Verification contains an invalid entry. SNA Transport: An invalid file has been specified in the X.21 Call Verification field in the X.21 configuration file.HDLC LAPB and NRM, and X.25 LAPB: The X.21 CSS system service must be installed when using X.21 switched access to a PDN. SNA Transport: The X.21 Circuit Switching SeH* rvice has not been installed.HDLC LAPB and NRM, and X.25 LAPB: The LAPB parameter X.21 Network Type contains an invalid entry. SNA Transport: An invalid value has been entered into the X.21 Network Type field in the X.21 configuration file.HDLC LAPB and NRM, and X.25 LAPB: Service ID should not have been entered since MGS is not being used.HDLC LAPB and NRM, and X.25 LAPB: MGS is not installed. The service ID should not have been used.Reserved.X.25: XE service ID is invalid. The entry in the LocatioT, n parameter is incorrect (for example, the XE Board name is 12 or more characters, including the brackets [ ]).Reserved.X.25: The communications channel entered in the link level configuration file is not a valid value.Reserved.Reserved.CommIOP: CommIOP timeout. The CommIOP failed to update the status cell within a certain time period. Run the CommIOP diagnostic to determine the cause of the error.CommIOP: Line not configured. The communications line number is not currently configured in the system. `. Change the system build parameters.CommIOP: Missing System Imaage file for CommIOP. Did not find the file [Sys]CommIOP>SysImage.Sys.CommIOP: CommIOP loading error. The CommIOP could not be loaded successfully. Run the CommIOP diagnostic.CommIOP: Invalid CommIOP data structure. There is an invalid queue entry, an invalid CommIOP number, and so on. Take a crash dump and run the CommIOP diagnostic.CommIOP: CommIOP channel restart. The carrier problem on the CommIOP channel was cleared.CommIOP: l0 CommIOP channel hold. There is a carrier problem on one of the CommIOP channels. Disconnect the cluster workstations one at a time to determine which is failing.Reserved.CommIOP: CommIOP command failure. The CommIOP returned erroneous control information to the server (formerly master). Reserved.CommIOP: Invalid master workstation to CommIOP command. The CommIOP did not recognize the,  conditions exists: - the line has not been properly activated - the line has been deactivated - a line failure has been detected - no incoming or outgoing data is allowed.SNA Network Gate> way, SNA/X.25 Gateway, SNA Transport: Internal Transport Service resources unavailable. Retry the request.SNA Network Gateway, SNA/X.25 Gateway, SNA Transport: No Logical Units for the bCOS type specified in the Attach request are currently available (all LUs are in use).SNA Network Gateway, SNA/X.25 Gateway, SNA Transport: LU currently attached or suspended. The user has specified an LU number to which another user is attached, or a session is currently suspended at this LU and the proper password h@ as not been specified to resume the session.SNA Network Gateway, SNA/X.25 Gateway, SNA Transport: Read or Write buffer size insufficient. The volume of data to be received or transmitted surpasses the size of the buffer. The data has been truncated to the buffer size requested.SNA Network Gate command from the server (formerly master).CommIOP: CommIOP bootstrap checksum failure. The CommIOP checksum test faix2 led while loading its code file from the server (formerly master).CommIOP: CommIOP stacker/destacker failure. The Multibus interface hardware (stacker/destacker) on the CommIOP is not functional.CommIOP: Invalid CommIOP interrupt. The CommIOP received an interrupt from an unknown source.Reserved.CommIOP: CommIOP RAM failure in write/read test.CommIOP: CommIOP RAM "failure invalid" bit is set.CommIOP: CommIOP "failure invalid" bit is cleared.CommIOP: CommIOP RAM failure in addressing test.Reserved.Co4 mmIOP: CommIOP handler timeout. The CommIOP did not get proper status information. The most probable cause is a software problem in the server (formerly master) that caused the Server Workstation Agent Service Process to be permanently suspended.CommIOP: Invalid CommIOP check word. The CommIOP has encountered an invalid check work in its queues. There is probably a memory error in the server.CommIOP: CommIOP RAM checksum error. The CommIOP's RAM is probably faulty. Run the CommIOP diagnostic.CommIO6 P: Invalid queue entry. The CommIOP has discovered an invalid queue entry in its data queues. This is possibly a software error.CommIOP: Invalid CommIOP buffer pointer. The CommIOP received an invalid memory address of a buffer.CommIOP: CommIOP carrier problem.CommIOP: CommIOP software inconsistency. This is probably a software error. Take a crash dump.Reserved.CommIOP: CommIOP timer failure. The timer hardware on the CommIOP failed the initialization tests.CommIOP: CommIOP DMA failure. The Dir8 ect Memory Access (DMA) hardware on the CommIOP failed the initialization tests.CommIOP:  CommIOP SIO static test failure. The communications hardware on the CommIOP failed the static initialization test.CommIOP: CommIOP SIO functional test failure. The communications hardware on the CommIOP failed the functional test.Reserved.CommIOP: The cluster is too heavily loaded when the GetClusterStatus operation is invoked.CommIOP: Invalid baud rate specified in SetBaudRate operation.CommIOP: Cluster workstat: ion (CWS) timeout. The CWS did not respond in the allotted time period. This could be caused by a reset or power down on the CWS, or by a faulty CWS.CommIOP: CWS Cyclical Redundancy Check (CRC) error. An excessive number of CRC errors were encountered from the CWS. Run the communications and CommIOP diagnostics.CommIOP: CWS overrun error. The CWS sent too much data per buffer. Check the CWS/server workstation system build parameters.CommIOP: Invalid protocol errors. These errors are probably due t< o one of the following: - a case of "duelling servers" (make sure that no cluster workstations are running a server operating system) - a faulty CWS - a faulty operating system on a CWSReserved.SNA Network Gateway, SNA/X.25 Gateway, SNA Transport: Interconnecting line failure or inactive line. One of the following - way, SNA/X.25 Gateway, SNA Transport: The requested LU number was not within the range configured on the installation menu. Recheck the number supplied and try again.SNA Network Gateway, SNA/X.25 Gateway, SNA TranB sport: User-specified time out value exceeded. The request was not fulfilled.SNA Network Gateway, SNA/X.25 Gateway, SNA Transport: Invalid link address. Obtain a valid link address from local communications/operations personnel.SNA Network Gateway, SNA/X.25 Gateway, SNA Transport: Transport Service has detected a fatal error or the same host has reactivated the node. Try the request again or check with local operations personnel to determine cause.SNA Network Gateway, SNA/X.25 Gateway, SNA Transport: D  The Transport Service has detected a fatal error or the host has reactivated the LU. Retry the request or check with local operations personnel to determine cause.SNA Network Gateway, SNA/X.25 Gateway, SNA Transport: Request not executable. The SSCP-PU session is not active because the owning host has deactivated the node.SNA Network Gateway, SNA/X.25 Gateway, SNA Transport: Request not executable. The SSCP-LU session is not active because the host has deactivated the LU.SNA Network Gateway, SNA/X.25 F Gateway, SNA Transport: Session reset by PLU.SNA Network Gateway, SNA/X.25 Gateway, SNA Transport: Request received in nonfunctional state. Terminate the current session or detach the LU.SNA Network Gateway, SNA/X.25 Gateway, SNA Transport: Request is from an LU that has not previously issued an AttachLU to the Transport Service.SNA Network Gateway, SNA/X.25 Gateway, SNA Transport: No buffer resource available. You attempted a read or write-type operation with a buffer size of 0.SNA Network Gateway, H SNA/X.25 Gateway, SNA Transport: Request not executable. LU-LU session not active.SNA Network Gateway, SNA/X.25 Gateway, SNA Transport: Too many requests have been sent to the Transport Service. Retry the request.SNA Network Gateway, SNA/X.25 Gateway, SNA Transport: Unable to queue request due to insufficient memory resources.SNA Network Gateway, SNA/X.25 Gateway, SNA Transport: No inbound data can flow. The host has not yet activated the Logical Unit.SNA Network Gateway, SNA/X.25 Gateway, SNA TranspK ort: Process termination. All requests were (or shortly will be) cleared because the user's process has terminated.SNA Network Gateway, SNA/X.25 Gateway, SNA Transport: InitiateSNASession or InitiatSNASessionNet request was issued for an active LU.SNA Network Gateway, SNA/X.25 Gateway, SNA Transport: When installing the Gateway, an invalid LU value or format has been entered in the LU parameter.SNA Network Gateway, SNA/X.25 Gateway, SNA Transport: Synchronous Data Link Control (SDLC) window-size maxoutM  value is either less than one or greater than seven.SNA Network Gateway, SNA/X.25 Gateway, SNA Transport: User has specified an LU number greater than 2 as the starting LU.SNA Network Gateway, SNA/X.25 Gateway, SNA Transport: A DetachLU or DetachLUNet has been received. All subsequent requests are rejected except AttachLU or AttachLUNet.SNA Network Gateway, SNA/X.25 Gateway, SNA Transport: PLU has terminated session. All outstanding user requests are terminated.SNA Network Gateway, SNA/X.25 Gateway, SN O A Transport: A dial-up (switched) line or two-wire mode was chosen concurrently with FDX (full duplex) mode.SNA Network Gateway, SNA/X.25 Gateway, SNA Transport: SNA Transport Service detected a segmentation error. The node is to be totally reset.SNA Network Gateway, SNA/X.25 Gateway, SNA Transport: An InitiateSNASession request received a negative response from the host.SNA Network Gateway, SNA/X.25 Gateway, SNA Transport: A TerminateSNASession request received a negative response from the host.SNA Ne,Q twork Gateway, SNA Transport: Invalid channel. An invalid communications channel has been specified.SNA Network Gateway, SNA Transport: Yes or No not specified. An installation parameter requiring -  etwork Gateway must be installed before the 3270 printer subsystem can be installed. Install the gateway, then execute the Install SNA 3270 PRT command again. ClusterShare SNA 3270: The SNA Network Gateway must be installed on the server before ClusterShare SNA 3270 can be used.SNA 3270 Emulator: Invalid LU type. Execute the SNA 3270 CRT command or the Install SNA 3270 PRT co_ mmand as appropriate with a valid LU type.SNA 3270 Emulator: Invalid Open Rule. Valid values are 1 or 2.SNA 3270 Emulator: SNA 3270 Subsystem is already installed.SNA 3270 Emulator: Invalid Node Name. The size of the node name string is too large (larger than 14 bytes) or has missing or unmatched brackets.SNA 3270 Emulator: The Multibus or Multiline Network Gateway is used and the PU Number is not given in the command form.Reserved. SNA 3270 Emulator: Time Out occurred. No data was received from ta he host computer during the time period specified in procedures with a Time Out parameter. This conditioeither a Y (yes) or N (no) has not received received either value.SNA Network Gateway, SNA Transport: Invalid Switched ID. Only valid Switched ID can be specified.SNA Network Gateway, SNA Transport: Invalid PIU size. A value either too small (less than 73) or too large (greater than 1033) has been specifie8S d for the maximum PIU size. The maximum PIU size varies with the release. Refer to your application documentation for the correct PIU size.SNA Network Gateway, SNA/X.25 Gateway, SNA Transport: Invalid line speed or RTS delay. Specify only the allowed line speeds and RTS delays. Reserved.SNA/X.25 Gateway, SNA Transport: An invalid ID block has been specified. Specify a maximum of up to 3 digits hexadecimal value (000 - FFFH).SNA/X.25 Gateway, SNA Transport: A value longer than 15 digits has been entDU ered for the Switched VC Outgoing Target DTE parameter.SNA/X.25 Gateway, SNA Transport: An invalid Permanent Virtual Circuit Logical Channel Number value has been supplied. Valid entries are 0 through 4096.SNA/X.25 Gateway, SNA Transport: An invalid entry has been specified for the [Switched Virtual Circuit Incoming Port #s] parameter. This error occurs if the high port value is lowere than the low port value. Recheck the entry and retry.SNA/X.25 Gateway, SNA Transport: Non-numeric character. NumbePW r(s) must be made up of digits 0 to 9.SNA 3270 Emulator, ClusterShare SNA 3270: Invalid LU number supplied. SNA 3270 Emulator: The Logical Unit number you entered for the SNA 3270 CRT command is not in the range that was specified when the SNA Gateway was installed. Use the SNA Status Monitor to verify the range of valid numbers, and then re-execute the SNA 3270 CRT command with an appropriate LU number. ClusterShare SNA 3270: The LU Number parameter value is not in the range of 2 through 33. Execute \Y the CS3270 command with a valid LU number. SNA 3270: Invalid screen profile. The Screen Profile specified at installation is not in the range A-G, or a-g. Execute SNA 3270 CRT command with a valid screen profile. (Note that earlier releases have a more limited range. Refer to your release documentation.)SNA 3270, ClusterShare SNA 3270: Invalid numeric lock parameter. The response to the Numeric Lock parameter specified at installation is neither Y or N. Execute the appropriate command (SNA 3270 CRTh[  for SNA 3270 Emulator, CS3270 for ClusterShare SNA 3270) with a valid numeric lock parameter value.Reserved.SNA 3270 Emulator: Invalid Physical Unit (PU) Number supplied. The PU Number is either not numeric or not in the valid range (1-4).Reserved.SNA 3270 Emulator: No file name. A file name is a required parameter for installation of the 3270 printer subsystem. Execute the Install SNA 3270 PRT command with a valid file name.SNA 3270 Emulator: Invalid file name. Execute the Install SNA 3270 PRT commt] and with a valid file name. SNA 3270, ClusterShare SNA 3270: SNA Network Gateway not installed. SNA 3270 Emulator: The SNA N. n can occur when there is a heavy load on the host computer.SNA 3270 Emulator: Minus function. This is equivalent to a minus function condition when typing on the keyboard.SNA 3270 Emulator: Input inhibited. Some condition occurred that inhibits input to the screen image. Press RESET (f1) to clear the condition.SNA 3270 Emulator: Input error. An error occurred while writing to the screen image, foc r example, an attempt to write to a write-protected field. Press RESET (f1) to clear the condition.SNA 3270 Emulator: Invalid screen. An invalid screen size was specified in the OpenSNA3270Emulator or OpenSNA3270EmulatorNet procedures.SNA 3270 Emulator: Invalid keyboard input. An invalid character was found in the keyboard stream. Press RESET (f1) to clear the condition.SNA 3270 Emulator: Invalid ATTENTION key ID. An invalid ATTENTION key ID character was used in the ReturnSNA3270Screen. Use the RESEe T code in the WriteSNA3270 screen to clear the condition.SNA 3270 Emulator: Program error. The host computer has sent an error condition to the screen. Press RESET (f1) to clear the condition.SNA 3270, ClusterShare SNA 3270: Invalid Printer. SNA 3270 Emulator: The PrinterId on OpenSNA3270Emulator or OpenSNA3270EmulatorNet was invalid, or the IDENT key specified an invalid printer. Use the RESET code in the WriteSNA3270 screen to clear the condition. ClusterShare SNA 3270: An invalid printer was speg cified with the Ident function. Press Reset to clear the condition.Reserved. SNA 3270 Emulator, SNA Network Gateway: Data Set Ready (DSR) signal is not active. The SNA Gateway monitors the DSR signal periodically and if the signal is not active, data transmission will not take place. Check the modem and the modem cable, and make sure that the RS-232-C connectors are plugged in properly and connected to the correct channels.CT-Net: Link Disconnected. The link between two nodes has received an unexpei cted unrecoverable error. All operations currently in progress are terminated.CT-Net: Resources unavailable. An internal CT-Net resource has been expended. Retry the operation later.B-NET, BNet II: Maximum TSAP connects The Net Transport Service parameter Max # Users may have been set to 0 or 1. You should leave it at 2. CT-Net: Value for Transport Service installation parameter [# of Retransmissions] is out of range.B-NET, BNet II, CT-Net: TSAP in use. An attempt is being made to install the Netk  Agent, Net Server, or (with BNet II) the Naming Server when there is already a copy present. Internally, a Transport Service user has tried to use a TSAP (an address) that is currently allocated to another user. This code may appear even when the Net Transport is not installed.B-NET, BNet II, CT-Net: Data truncated. Too much data is being received or transmitted within the specified limitations of the buffer size. Whatever value can be returned is returned. Internal error.B-NET, BNet II, CT-Net: Im nvalid TSAP. A user other than a Net Agent or Net Server user has attempted to use the net. (This is currently not allowed.) Internally, a user has specified a TSAP out of the valid range. Internal error.B-NET, BNet II, CT-Net: Timeout has occurred. Internal error.CT-Net: An invalid node address has been given.CT-Net: Node has been reset.CT-Net: TSAP has been reset.CT-Net: Invalid connection index received.B-NET, BNet II, CT-Net: Invalid connection. Internal error.CT-Net: TSAP has been deactio vated.B-NET, BNet II, CT-Net: Invalid state. You received data for a connection that was waiting for a connection confirm. Internal error. An error TPDU is sent.B-NET, BNet II, CT-Net: Not attached. A request came from a user not known to the Transport Service.B-NET, BNet II, CT-Net: No buffer If aborted, this is an internal error. If this message appears in the log file without an abort, it is a warning that the Net Transport Service has temporarily run short of buffers and has to discard packetq s.CT-Net:.  e media service may have failed to install.CT-Net: 4~  No dial connection.CT-Net: No such task type.B-NET, BNet II, CT-Net: Node in use. An attempt is being made to delete a node entry which is currently in use.B-NET, BNet II, CT-Net: Media in use. An attempt is being made to delete a media entry which is currently in use (for example, referenced by entries in the Adjacent Node Table.)CT-Net: Phone not on-hook.CT-Net: This modem is answer only.CT-Net: No more RS-232-C lines. Both channels A and B have been used.B-NET, BNet II, CT-Net: Cannot delete m@ edia. If any adjacent nodes are accessing the node via the media, the media cannot be deleted. If you want to delete the media, you must first delete the adjacent nodes that are addressing the media. This is an internal error. The administrator is notified of this error on an operator level through a message of the Network Control Center.B-NET, BNet II, CT-Net: Maximum number of nodes exceeded. An attempt is being made to add No connections exist for this TSAP (user).B-NET, CT-Net: Queue contains the maximum number of requests of this type. BNet II: Internal. Maximum queues.B-NET, BNet II, CT-Net: No Rcb. No more internal queuing structures (RCBs) exist in the Transport Service. Retry later.B-NET, BNet II, CT-Net: TSAP Index mismatch. Internal error.B-NET, BNet II, CT-Net: Purge request received, operating system aborted. Internal error.B-NET, BNet II, CT-Net: TSAP in session. Internal error.B-NET, BNets  II, CT-Net: Invalid TSAP range. The Max # Users parameter is either 0 or greater than 16.B-NET, BNet II, CT-Net: Maximum connects at this node The local Net Transport Service has run out of connections. Increase the [Max # connections] parameter when installing the Net Transport Service.Reserved.B-NET, BNet II, CT-Net: TSAP detached. The Net Agent or Net Server has detached itself from the Transport Service. All outstanding operations are terminated. Internal error.B-NET, BNet II, CT-Net: Invav lid address range. The specified node is outside the [Max # Nodes] parameter specified when installing the Net Transport Service, or has a value of zero.B-NET, BNet II, CT-Net: Invalid node range. The [Max # Nodes] parameter is either 0 or greater than 255.B-NET, BNet II, CT-Net: Invalid connect range. The [Max # Connections] parameter is either 0 or greater than 16.CT-Net: Disconnect received from partner.Reserved.CT-Net: Invalid channel specified.CT-Net: Not yes or no. BNet II: "Yes" or "no" nox t entered as connection parameter in netcfg.sys. NAC.run returns an erc 8932 if it encounters a netcfg.sys connection parameter value of anything other than yes or no.CT-Net: Invalid dial in.B-NET, BNet II, CT-Net: Invalid buffer size. A status or query request to the Net Agent or Server did not provide a buffer large enough to return the requested information. This code may appear even if the Net Transport Service is not installed.B-NET, BNet II, CT-Net: Invalid maximum media. The Max # Media Configz uration parameter is either 0 or greater than 16.B-NET, BNet II, CT-Net: Node not found. The specified node is unknown, and cannot be located. (For more information, see 8992.) If encountered when trying to install the Net Transport Service, then either no node name was input, or the name input is invalid. This code may be returned even if the Net Transport Service is not installed. DCA STI: A node name was not recognized by DCA STI. This error is returned to the Naming Server Query request if the n(| ode is not recognized as a valid alias by the DCA Manager.B-NET, BNet II, CT-Net: Duplicate node. An attempt is being made to add a configuration entry for a node which already has an entry, or to add an Adjacent Node entry whose install number, configure number, and subnet address match an existing entry.B-NET, BNet II, CT-Net: No such media. A media configuration entry does not match any known media service. The Install Number may be incorrect, or th/  an Adjacent Node or User Node Table entry when that table is full. IncreaL se the [Max # Nodes] parameter when installing the Net Transport Service.B-NET, BNet II, CT-Net: Maximum number of media exceeded. An attempt is being made to add another media entry when the media table is already full. Try increasing the [Max Media Configurations] parameter when installing the Net Transport Service.CT-Net: Invalid media range. The media number exceeds the maximum number of allowable media.Duplicate media. An attempt is being made to add a media table entry for a media which has alreX ady been configured.CT-Net: Transport Service stopped.Reserved.B-NET, BNet II, CT-Net: Transport Service already installed.CT-Net: Remote Server not installed.B-NET, BNet II, CT-Net: No matching virtual circuit blocks. Internal error.Reserved.CT-Net: No reason given for disconnect.B-NET, BNet II, CT-Net: Net Server reject. The remote node's Net Server may not be able to support any more sessions. Try increasing the number of sessions when installing the Net Server (B-NET) or Net Agent/Server (BNetd II).B-NET, BNet II, CT-Net: Net Server not installed. There is no Net Server installed on the remote node.CT-Net: Disconnect because address unknown.Reserved.CT-Net: Code to handle this case is not implemented. In particular, IP segmentation is not currently implemented. This error usually occurs when there are more pb/cbs than the net can handle. Reduce the number of pb/cbs.Reserved.B-NET, BNet II, CT-Net: Normal disconnect. This can occur if the remote Net Server aborts or is deinstalled.B-NET, Bp Net II, CT-Net: No remote transport connect. The remote node's Net Transport Service may not be able to support any more connections. Try increasing the number of connections when installing the Net Transport Service.CT-Net: Disconnect because Transport Protocol negotiation for network connection failed.CT-Net: Disconnect because duplicate connection.B-NET, BNet II, CT-Net: Mismatched references. The remote station no longer considers this connection to be up. This can happen if a momentary connecti| on failure occurs. One node may attempt to recover the connection while the other decides that it cannot be recovered, and considers it shut.CT-Net: Disconnect because protocol error.B-NET, BNet II, CT-Net: Connection timeout Excessive errors at the media level may cause a connection to timeout. Decrease the KBPS parameter used during media configuration in NCC.Reserved.CT-Net: Disconnect because bad net connection. Transport connection is not allowed on this network connection.B-NET, BNet II, CT-Net : Invalid length TPDU. Your Net Agent has received a message from the Net Server which is not as long as expected. There may have been a failure during data transmission.CT-Net: Transport Protocol error.CT-Net: Transport Protocol lost network connection. You cannot route over connection oriented media or connection not allowed.B-NET, BNet II, CT-Net: Transport Protocol timeout Indicates that a switched connection, once established, terminated abnormally. For dial-up, the call may have been cut off,  or the modem reset. May also indicate excessive errors at the media level, such as caused by a very noisy line. Decrease the KBPS parameter used during media configuration in NCC.CT-Net: Transport Protocol normal.CT-Net: Transport Protocol network connection failed. This error code can be returned for many reasons, for example if any of the following occur on a dialup line: - The other node is powered off (phone does not answer). - Your modem is not connected to the phone line (no dial tone). - Som eone at another cluster workstation is using the dial-up to communicate with a different nod (line in use). This is a fairly common status code and does not indicate a software problem.CT-Net: Transport Protocol user reject.CT-Net: Transport Protocol network reset.CT-Net: Data specified in Transport Protocol connection request is too l/  ue. Tape Streamer Utilities: Timed out waiting for READY to be asserted at command completion.Tape: Timed out waiting for expected Data Busy true.Tape: A memory time out occurred during a system memory reference.Tape: Tape is blank .... i t contains no data. Blank tape was encountered where data was expected. Shared Resource Processor: On QIC hardware from Archive, this error could also indicate that the QIC Service seelcted the wrong QIC format (QIC-11 or QIC-24).Tape: An error occurred in the micro-diagnostic.Tape: End-of-tape encountered. An unexpected EOT was encountered during a forward operation or Load Point during a reverse operation. For the QIC server, this is the logical end-of-tape (in write mode, the estimate of the rema ining tape space has reached zero; in read mode, blank tape has been reached). Tape Streamer Utilities 7.1: An unexpected tape mark was found. The end of the tape cartridge was reached.Tape: A hardware or software error occurred that could arge.CT-Net: Transport Protocol provider initiated.CT-Net: Transport Protocol user initiated.CT-Net: Transport Protocol negotiation.B-NET, BNet II, CT-Net: No Send Rou te entry. The requested node, although known, cannot currently be reached because something is down. This code may be returned even if the Net Transport Service is not installed. BNet II: To troubleshoot 8936 and 8992 errors, you must determine how the connection is normally made. If both nodes are on the LAN, use NCU to check the node table. If the target node appears, then check that it is up (check the line also) and that BNetII is installed. If the target node doesn't appear, use LDM to try to e cho to it. If the echo fails, something is wrong with the LAN hardware or software. If the echo is successful, something is wrong with the BNetII software or OSI Session software. If all nodes on the LAN have trouble accessing all other nodes, then there is probably a broken or disconnected cable, or a missing terminator. If the target node is accessed over the classic BNET media without using extended routing, and you get an 8936, the node probably does not appear in the User Node Table. If the targeĖ t node is normally accessed over a series of permanent WAN connections (RS-232-C direct cables and leased lines, and X.25 PVCs) then check the Remote Status Display. If the node does not appear in that table, then either it or an intermediate node or connection is down. Trace the path through intermediate nodes by examining the Remote Status Display in each one. Also check the Media Status display to determine that the lines are up, and check that the entries appear in the Adjacent Node Tables. If the tИ arget node is accessed using extended routing, including source nodes with only LAN connections, then determine the intermediate node. Check that the initiating node can access the intermediate node, and that the intermediate node can access the target node, and proceed as above on the link that fails.CT-Net: No request blocks.B-NET, BNet II, CT-Net: Segmentation not implemented. You are trying to use a route entry that does not exist.B-NET, BNet II, CT-Net: Bad Internet Protocol Checksum. Internal erܚ ror.CT-Net: Not local node.CT-Net: Failure of Net Management Protocol. Usually this means that another node on the network is inaccessible and the Network Management Protocol could not deliver information packets, in particular, routing information.CT-Net: Net Management packet references a node exceeding bounds of local table.CT-Net: Failure occurred during Transport Service Compression routines.Reserved.Tape: Timed out waiting for expected Data Busy false.Tape: Tape operation timed out. Timed  out waiting for expected Data Busy false, Formatter Busy false, and Ready true.Tape: Timeout waiting for expected Ready false. Tape Streamer Utilities 7.1: Timed out waiting for READY to be deasserted while reading status.Tape: Timeout waiting for expected Ready tr0 not be eliminated by retry. Tape Streamer Utilities 7.1: Tape hardware failure. The tape hardware is not responding correctly.Tape: A read overflow or write underflow occurred. This error indicates that the FIFO buffer was empty when data was requested by the   tape during a write, or full when the tape presented a byte during a read.Tape: For a minimaster. There is no free preallocated data buffer. Tape Streamer Utilities 7.1: No buffer allocated to tape server. Refer to the Install QicTape Server command in your Tape Streamer Utilities documentation.Tape: A read parity error occurred on the byte interface between the drive and the Tapemaster, or for the Tape Streamer Utilities, the tape controller.Tape: An error was detected while calculating a checksum o n the tape controller PROM.Tape: A tape time-out occurred because the drive did not supply an expected read or write strobe. This normally occurs while attempting to read a larger record than was written. It may also occur during a write due to a damaged tape.Tape: Tape drive is not ready. The cartridge is not inserted, or the tape drive is either off-line or busy (for example, rewinding).Tape: A write was attempted without a write-enable ring or with a write-protected cartridge. Tape Streamer Utilit$ ies 7.1: A write or erase operation was attempted on a tape that was opened in read mode.Reserved.Tape: The diagnostic mode jumper was not installed while attempting to execute a diagnostic command.Tape: An attempt was made to link from a command that does not allow linking.Tape: A File Mark was encountered during a read operation. Tape Streamer Utilities 7.1: An unexpected tape mark was encountered during a read data operation.Tape: An error in specifying a parameter was detected by the Tapemaster, 0 or for the Tape Streamer Utility, the tape controller. The usual cause is a byte count that is zero or too large.Reserved.Tape: A hardware error occurred in the tape drive or the controller. Consult Technical support. Tape Streamer Utilities 7.1: An unidentifiable hardware error has occurred.Tape: A streaming read or write operation was terminated by the operating system or disk.Reserved.Tape: Bad tape handle. A tape service request was made with an invalid tape handle or, in the shared resource p< rocessor, an invalid user number. This is typically caused by an error in a user program. It may also occur when using the tape backup utilities, if the cluster workstation was taken off-line during the backup operation.Tape: Bad tape parameters. A tape service request was made with invalid parameters. These include: zero-length buffers, requests to read or write zero records, and so on.Tape: No free tape control blocks. This is an internal error that indicates a problem with the software you are usH ing. Consult Technical Support. Shared resource processor: The half-inch tape server ran out of device control blocks.Tape: Bad tape file name. The tape name supplied was invalid. Tape specifications have the form [Tape], [Tape]+, or [TapeMM]NN. QIC specifications have the form [QIC], [QIC]+, or [QICMM]NN. For both Tape and QIC, MM designates the tape drive number and the NN designates the tape file number. These numbers are optional. (The default for MM is 0, and the default for NN is the currentT  location. Shared resource processor: An open tape service was requested with an invalid tape name. Tape Streamer Utilities 7.1: Invalid tape name for the currently installed server. The tape name supplied was invalid for the currently installed server.Tape: An open tape service was requested on a drive currently being used by another user. Tape Streamer Utilities 7.1: Tape is currently in use. The tape drive is currently reserved by another user.Tape: Tape is write-protected. For a half-inch ` tape, the write-enable ring was not inserted. Remove the tape and insert the write-enable ring on the back of the tape. For a QIC tape, the cartrid0  must be between 1024 and 16384 bytes for backup, and between 2 and 16384 bytes for tape byte streams. Shared resource processor: Invalid tape record size specified for buffer in tape read/write request. Tape Streamer Utilities 7.1: Tape record size for backup must be a multiple of 512 bytes. Tape records must be a multiple of 512 between 2048 and 64512 bytes for tape backup. Use the Tape Streamer utility's Tape Configure Fil e command to create valid parameters.Tape: Missing tape controller. Tape controller is missing or improperly configured. For quarter-inch tape, this code indicates: - No tape module on the workstation. - Tape drive is missing or not receiving power. - You cannot install tape server on this machine. For half-inch tape, the code indicates: - Missing tape controller. - Improperly configured tape controller.Tape: XBIF not installed. The X-Bus interrupt handler, XBif.run, has not been installed. You  must install XBIF before using quarter-inch tape.Tapege is write-protected. Turn the write protect or write safe knob on the cartridge away from the word safe. The utility will continue if a write-enabled tape is mounted.Illegal tape operation. An illegal command code was supplied to the TapeOperation request. Tape Streamer Utilities 7.1: An unrecognized command was issued as a tape operation request. Thisl  code indicates one of the following: - Illegal tape operation. An illegal command code was supplied in the TapeOperation request. - Illegal Tape request. An illegal request code was sent to the Server.Tape: Tape error outstanding. A read or write request was issued while a tape error was outstanding. Issue a TapeStatus request to clear the tape error before issuing another read or write request.Tape: Unknown tape mode. Tapes may be opened only for mode read (mr) or mode write (mw).Tape: Tape opx eration is outstanding. The tape cannot be released or closed until all tape operations have completed. Tape Streamer Utilities 7.1: A CloseTape request was received before all previous requests for this drive were completed.Tape: Illegal tape buffer address. The address of the buffers are illegal for tape operations. The tape drive can access only buffers in the lower 512Kb of memory. Alternately, install the Tape Service, then run the Tape utility again.Tape: Tape record is truncated. The b uffer provided was not large enough for the tape record.Tape: The QIC tape service is in use. A user, perhaps a cluster workstation, is using the installed QIC service.Reserved.Tape: Corrupt tape. Tape is not valid or has been corrupted. The tape is not a valid backup tape or has been corrupted. QIC only: The physical end-of-tape was reached before the logical end-of-media. Therefore, information was lost.Tape: Invalid tape position. The tape is neither at load point nor at the start of a file.Tap e: Invalid tape reel. The tape reel/cartridge is not a part of the backup set currently being restored. Verify that you have mounted the correct tape. Tape Streamer Utilities 7.1: Continuation tape is not from the same backup set. The tape is not part of the backup or archive tape set currently being used for a restore operation (for example, the program expected tape 2 of 3 and tape 3 of 4 from a different set was mounted). Verify that the correct tape is mounted.Tape: Invalid tape sequence. Tape  Streamer Utilities 7.1: Tape is mounted out of sequence. The tape is mounted out of the correct seqeunce for backup (for example, the program expected tape 2 of 3 and the third tape was mounted).Tape: Invalid Tape Configuration file. The tape configuration file is invalid. Use the Tape Streamer Utility's CONFIGURE FILE command to create the configuration file.Tape: Missing Tape Configuration file. The Tape Configuration file cannot be found or is inaccesible. Use the Tape CONFIGURE FILE command to c reate the tape configuration file.Tape: Bad tape record size. Tape records 1 : Tape controller failure. The tape controller is not responding correctly. Run the Magtape or tape Diagnostic to diagnose the failure.Reserved.Tape: No internal buffers are available for remote processor copy-in/copy-out. This happens only if the read/write request is from a remote processor. Reissue the request.Tape: Bad alignment of user-supplied data buffer. Be sure data buffers are aligned on word boundaries.Tape: The user request specifie d a data buffer size larger than that specified at tape service installation time.Tape: Cartridge was removed. The QIC tape was removed from the drive after being opened by a user. Tape Streamer Utilities 7.1: Tape cartridge not in place. If this message appears when the cartridge is in place, it may mean that the cartridge is broken.Tape: An illegal command was sent to the tape controller. This is an internal error that indicates a problem with the software you are using. Consult Technical Support. Tape: Quarter-inch cartridge is not a bootable tape.Tape: Quarter-inch cartridge is a corrupted bootable tape. CTOS/XE: The system has encountered an unexpected problem loading the Boot Tape Table of Contents file. Internal error.Tape: The physical end of the QIC tape has been reached. Tape Streamer Utilities 7.1: Reserved.Tape: BootTape Table Of Contents Too Big. The BootTape Table Of Contents file is larger than 4096 bytes, the maximum size allowed.Tape: BootTape No Such File. The loaded BootT ape Table Of Contents does not contain a valid :FileType: token (keyword) for the target file.Tape: The buffer is too small. QIC: A QIC tape buffer must be at least 512 bytes. The user of tape access methods supplied a buffer that is too small. The buffer must be at least three times the record size specified in the tape configuration file used by the access method. Tape Streamer Utilities 7.1: Insufficient memory is available for the specified record size. There is insufficient RAM space to accom odate requested record size. Install more RAM or decrease the amount of RAM in use. Refer to the System Administration Guide for information on maximizing tape record size.Tape: There are too many tape services installed in the system. Tape Streamer Utilities 7.1: There are too many tape modules.Reserved.Tape Streamer Utilities 7.1: Warning: A marginal data block was detected. The tape hardware had to do eight or more retries to read a block of data. This usually indicates that the tape cartridge i s nearing the end of its useful life, but operation will be continued.Tape Streamer Utilities 7.1: An unrecoverable hardware error occurred. The tape hardware was unable to read or write a data block after 16 retries. The cartridge will be rewound to BOT if the error occurred during a write operation.Tape Streamer Utilities 7.1: Illegal command exception occurred. The error condition was caused by one of the following: - Attempt to select other than one drive. - Attempt to change drive selection afte r tape has been moved from the BOT. - Attempt to Initialize Cartridge, BOT, or Erase simultaneously. - Attempt to Write/Read Records, or Write/Read Tape Marks with Online off. - Attempt to issue a command other than Write Record or Write Tape Mark during a Write Records command. - Attempted to issue a command other than Read Record or Read Tape Mark during a Read Records command. - Attempted to issue any command not implemented. - A write data, write tape mark, or erase tape operation was attempted on  a tape that was opened in read-only mode.Tape Streamer Utilities 7.1: This error code indicates one the following time-out conditions: - Timed out waiting for command accepted interrupt. - Timed out waiting for transfer complete interrupt during a read or write data operation. - Timed out waiting for exception interrupt during a read tape mark operation or software reset.Tape Streamer Utilities 7.1: Unable to read tape status after exception.Tape Streamer Utilities 7.1: 1  be sent because of an internal software error. Call Technical Support.SNA RJE: LogOn ID is out of ranh ge. Previous releases of SNA RJE may return the message: A request to transmit all jobs in the transmit queue has already been received.SNA RJE: Line down (inactive). Previous releases of SNA RJE may return the message: Specified file cannot be sent because it was not found in transmit queue.SNA RJE: Fatal error in MLU Manager. Deinstall the MLU Manager. Use the Plog command to consult the related message in the [Sys]Log.sys file. Previous releases of SNA RJE may return the message: Multiple t Logical Unit (MLU) manager service is down.Reserved.SNA RJE: Unable to send TERM-SELF. The specified LU-LU session cannot be terminated because of an internal software error. Consult Technical Support.SNA RJE: This LU is not bound. The specified LU-LU session cannot be terminated because it is not currently bound.SNA RJE: LU name does not match. The specified LU-LU session ca This error indicates one of th  e following: - Ready not asserted during command execution. - Ready not asserted at beginning of command execution.Tape Streamer Utilities 7.1: Tape status shows unexpected power-on/reset.Tape Streamer Utilities 7.1: The tape controller board's block count register did not reach terminal count during a read or write to the tape.Tape Streamer Utilities 7.1: No free tape control block data structure.Tape Streamer Utilities 7.1: Inconsistency. Internal variables have unexpected values.Tape Streamer Util, ities 7.1: Bad user number. The user number received is 0FFFFh, which is invalid.Tape Streamer Utilities 7.1: The drive is busy. Drive is unable to accept command from the initiator.Tape Streamer Utilities 7.1: Drive aborted the command.Tape Streamer Utilities 7.1: Service could not be deinstalled because of one of the following: - Not a multipartition operating system - Tape service is not installed. - The deinstallation request was received from a workstation other than the one on which the tape 8 service resides.The tape service is already installed. An attempt was made to install a tape service on a processor that already had one.SNA RJE: No Active Logical Unit (ACTLU) received for (Logical Unit) LU. The session control request that asks the SSCP to assist in initiating a session, INIT-SELF, cannot be sent on this LU. This is because the session control command to activate the LU, ACTLU, has not been received. There may be no session with the host, check with the System Administrator.SNA RJE: D  Session is already active. INIT-SELF will not be sent because the LU-LU session is already bound.SNA RJE: Unable to send INIT-SELF. Internal software error. Contact the Unisys Customer Support Center.SNA RJE: No free LUs. INIT-SELF cannot be sent because there are no free LUs.SNA RJE: Console request outstanding. You cannot send another console message until the host has responded to the previous messages. Try again later.SNA RJE: No LUs bound.SNA RJE: Console with an unknown user.SNA RJE: CanP not send console command. No active session. Consult the System Administrator to determine why the session is not active.SNA RJE: Transmit already issued or Reader busy.SNA RJE: File not in queue.SNA RJE: Cannot terminate LU. There may be no session to be terminated. Try again later and if the LU cannot be terminated, check with the System Administrator. Previous releases of SNA RJE may return the message: Console read outstanding. Console data will not be sent because a console request is current\ ly outstanding.SNA RJE: No LU-LU session active.SNA RJE: No LU name match. User is not recognized. Console data will not be sent because the user sending this request is not recognized. An XIDRequest must be received by the MLU Manager before any SendConsole requests.SNA RJE: Invalid status type. Previous releases of SNA RJE may return this message: Console command send error. Console data cannot 2 nnot be terminated because the indicated name does not match any LU-LU session.Reserved.SNA RJE: Invalid status request. In valid status type for Status request.Reserved.SNA RJE: Logon ID out of range. The logonID must be in the range of 0 to 9.SNA RJE: Comm line not active. The communications line has gone down.Reserved.SNA RJE: Invalid data size.SNA RJE: Invalid number of chain elements. Valid range is 1-25. Check your release documentation. Some release levels support a different number of chain elements.SNA RJE: The parameter specified for the compression field is neither yes nor no.SNA RJE: The parameter s pecified for the compaction field is neither yes nor no.SNA RJE: Invalid number of LUs. Valid range is 1 to 5.SNA RJE: Invalid starting LU number.SNA RJE: Invalid Primary LU name.SNA RJE: Invalid Primary LU Password.SNA RJE: Invalid file specification for printer or punch output destination.SNA RJE: Invalid Queue name.SNA RJE: The SNA RJE Multiple Logic Unit Manager has already been installed.SNA RJE: Invalid PU Number supplied.SNA RJE: Invalid Node name. The node name string is too large (large r than 14 bytes) or it has missing or unmatched brackets.SNA RJE: Invalid Receive Transport parameter. Enter yes or no.SNA RJE: Invalid Transmit Transport parameter. Enter yes or no.Reserved.SNA LUIS, SNA DFC: Outstanding Init DFC LU has issued an InitiateDFCSession when there is an InitiateDFCSession outstanding.SNA LUIS, SNA DFC: Outstanding Terminate DFC LU has issued a TerminateDFCSession when there is a TerminateDFCSession outstanding.SNA LUIS, SNA DFC: No STSN Outstanding LU has issued a DFC STSNComplete when a STSN Request has not been issued by the IBM host.SNA LUIS, SNA DFC: DT Not Active The application issued a write or send request when data traffic was not active on this session.SNA LUIS: Not LUT0 The LU is issuing a command that is LU T0 only. SNA DFC: Not LU0 The issuing LU is not LU0.SNA LUIS: NonSupported SNA Command The LU is issuing a non-supported SNA command. SNA DFC: The LU is issuing a non-supported DFC command.SNA LUIS, SNA DFC: Invalid Signal The LU has issued a  signal when there is already a signal outstanding for this LU.SNA LUIS, SNA DFC: Bracket Error SNA LUIS or SNA DFC discovered a bracket state error on a WriteDFCRU or WriteLURU from the LU.SNA LUIS, SNA DFC: Chain Error SNA LUIS or SNA DFC discovered a chain state error on a Write or Send from the LU. This write may have been from WriteDFCRU or WriteLURU, or a command like SendDFCRTR.SNA DFC: Unable to send signal.SNA LUIS, SNA DFC: Quiesce In Progress The LU has issued a request to SNA LUIS or SNA  DFC while the session with the IBM host is being quiesced.SNA LUIS: Unsupported LU Type An invalid LU type was requested by the application.Reserved.SNA LUIS: ErcQuiesced The LU has issued a request to SNA LUIS while the session with the PLU is completely quiesced. SNA DFC: The LU has issued a request to SNA DFC while the session with the IBM host is completely quiesced.SNA LUIS, SNA DFC: Response Before LIC The LU has issued a AcceptDFCChain before the last in chain has been received.SNA LUIS, SNA  DFC: Shut Down In Progress The LU has issued a request to SNA LUIS or SNA DFC while a shutdown sequence is in progress.SNA LUIS, SNA DFC: Shut Down The LU has issued a request to SNA LUIS or SNA DFC after a shutdown sequence is complete.SNA LUIS: HDX Error A write or send request from the LU had both EndBracket and ChangeDirection set.SNA LUIS, SNA DFC: Sequence Number Error SNA LUIS or SNA DFC discovered a sequence number error on a request from the LU.Reserved.SNA LUIS: Invalid DFC Command SNA L UIS has received an invalid Command parameter in AcceptDFCCmd or RejectDFCCmd, or a DFCSTSNComplete request was issued and the TS profile in the session's BIND was not 4. SNA DFC: SNA DFC has received an invalid DFC Command parameter in AcceptDFCCmd or RejectDFCCmd Request Primitives.SN2  error.SNA LUIS: No Headers. Returned by LUIS if the sHeaders field of the WriteLURU request is not equal to 17.SNA Multiline Gateway: The SNA Multiline Gateway is already installed on this workstation. The system service cannot be installed again.SNA Network Gateway, SNA/X.25 Gateway, SNA T( ransport: The Transport Service is about to be removed from memory. This notifies all outstanding requests that no more Transport Service requests will be served. SNA Multiline Gateway: Unable to close Real-Time Clock (RTC) during deinstallation of SNA Multiline Gateway. This is an internal error that indicates a problem with the software you are using. Consult Technical Support.SNA Multiline Gateway: The PU number specified in the Notify command is invalid. The specified PU number should be less th4 an 9 and greater than 0 for the installation, or, the PU number in the configuration list is greater than the maximum number of PUs specified during installation.SNA Multiline Gateway: Too manA LUIS: Short State Block The size of the State Block in a RetrieveDFCState request or a QueryDFCConfig request was less than the minimum allowed. SNA DFC: The State Block in a RetrieveDFC State was too short.SNA LUIS,  SNA DFC: Invalid RQR A Request Recovery (RQR) request was issued before a response was received to the previous RQR.SNA LUIS: Response Outstanding The LU issued a ReadDFCRU or ReadLURU before issuing AcceptDFCChain or ReturnDFCError to a complete FMD data chain. SNA DFC:  The LU issued a ReadDFCRU before it responded to the previous chain.SNA LUIS, SNA DFC: Can Not Install SNA LUIS or SNA DFC was installed more than once on the same workstation.SNA LUIS: No Terminate Self The specified LU-LU sessio n cannot be terminated since TERM-SELF was not sent to the host. This is returned to DetachFromDFC is the LU-LU session is still active.SNA LUIS: ErcI'mGoingByeBye SNA LUIS has received a unconditional Deinstall request and is in the process of shutting down.SNA LUIS: Single Partition SNA LUIS was not deinstalled because it was installed on a single-partition operating system.SNA LUIS: User Number Too High SNA LUIS was not deinstalled, because the request came from a cluster station.SNA LUIS: Applic ations Active SNA LUIS was not deinstalled because the fAbort flag was set to false and there were applications active.SNA LUIS: Trace Already Active An attempt was made to start up a trace that was already running or to stop a trace that was not running.SNA LUIS: SNA Gateway Already Running An attempt was made to install the SNA Impersonator when either it, the SNA/SDLC gateway, or the SNA/X.25 gateway was already running.SNA LUIS: Buffer Too Small The buffer size passed by the application on a Writ eDFCRU, WriteLURU, ReadDFCRU, or ReadLURU request was too small.SNA LUIS: Request Mode Violation The application violated immediate request mode with a write request.SNA LUIS: Not Identified The LU handle given in the request does not correspond to any previously returned by a IdentifyToDFC or IdentifyLU request.SNA LUIS: Mode Inconsistency The application has issued a QuiesceComplete request when either QEC has not been received from the PLU or the session is already quiesced.SNA LUIS: Bracket State  Error The application has issued a write or send request in which there was a bracket state error.SNA LUIS: Deinstall Me. This error code is returned when SNA LUIS encounters a fatal error. SNA LUIS must be deinstalled immediately.SNA LUIS: UnSupported LU Type. Returned when the bLUtype field in the IdentifyToDFC or IdentifyLU requests is not 0.SNA LUIS: Invalid Entry. Invalid entry in the installation form.SNA LUIS: Duplicate Config. The same LU number has been entered twice in the installation  form.SNA LUIS: No Parameters. An installation field has no parameters.SNA LUIS: RH Error. The RH passed to SNA LUIS by the application with the WriteLURU or the WriteDFCRU requests (bfpassSNAHeaders = TRUE) is in 3 y LUs are allocated. The maximum number of LUs allowed is 34 times the number of PUs.SNA Multiline Gateway: The PU specified in the Notify request has already been notified. The system service has already been notified of this PU's parameters. The administrator must Remove the PU from the system service and then N@ otify the Transport Service.SNA Multiline Gateway: The specified PU is not notified. Delete and PU Detail are meaningless commands when the specified PU has not been notified.SNA Multiline Gateway: This PU cannot be removed. There are active sessions with the host. The user must first disable the PU before Remove can be executed.SNA Multiline Gateway: Cannot disable the specified PU. PU cannot be disabled while there is an active LU-LU session. All active LU-LU sessions must be terminated before a L PU can be disabled.SNA Multiline Gateway: The specified communication channel is not available.SNA Multiline Gateway: Request code not known to CTOS. Invalid installation.SNA Multiline Gateway: Cannot disable the specified PU. The specified PU is either not configured or is already disabled.SNA Multiline Gateway: The specified PU is already in an enabled state. Its status is either Active or Inactive.SNA Multiline Gateway: Cannot process this request. The specified request code is not supported by X the SNA Multiline Network Gateway. SNA Network Gateway, SNA/X.25 Gateway, SNA Transport: Unable to deinstall the Transport Service due to at least one of the following: - An attempt was made to deinstall the gateway from a single partition operating system - Transport Service is not installed at the station where attempt is made to deinstall. - Applications are currently attached or connected. SNA Multiline Gateway: Cannot process the deinstallation request. The SNA Multiline Network Gateway can bd  e deinstalled only from the workstation on which it was installed. Do not attempt to deinstall the SNA Multiline Network Gateway on a single-partition operating system.SNA Multiline Gateway: Cannot process the deinstallation request. You cannot deinstall the SNA Multiline Gateway while there are active PUs. All the PUs must be disabled and Inactive before the Transport Service can be deinstalled.SNA Multiline Gateway: Invalid status type in QueryMPUStatus Primitive. This is an internal error that indip  cates a problem in the software you are using. Consult Technical Support.SNA Multiline Gateway: An SNA Gateway primitive is issued to a PU that is disabled or not configured. This is an internal error that indicates a problem in the software you are using. Consult Technical Support.Reserved.SNA Network Gateway, SNA/X.25 Gateway, SNA Transport: An invalid bType4 value was detected in the ConnectCNMService call. Valid values for this parameter are 0, 1, or 2.SNA Network Gateway, SNA/X.25 Gateway, SNA Tr|  ansport: A Connect was received for an LUn that is already being serviced by another application.SNA Network Gateway, SNA/X.25 Gateway, SNA Transport: This status code is used to respond to any outstanding request when a Disconnect is received.SNA Network Gateway, SNA/X.25 Gateway, SNA Transport: A Connect with a CNMh that is out of range has been specified. Check the Status Monitor for the range of allowable LU numbers.SNA Network Gateway, SNA/X.25 Gateway, SNA Transport: A disconnect CNM service was  received for an LU that is not being serviced by any applications. The disconnect CNM service request has no meaning.SNA Network Gateway, SNA/X.25 Gateway, SNA Transport: There is already a ReadREQMS/ReadNmvt request outstanding for this CNMh/LUh. Only one ReadREQMS and one ReadNmvt request may be outstanding from an application at any time.SNA Network Gateway, SNA/X.25 Gateway, SNA Transport: A request for one of the CNM services was received with an CNM that did not belong to the user number associate d with the request.SNA Network Gateway, SNA/X.25 Gateway, SNA Transport: A request for CNM servi3  operator.SNA DIA: Function aborted by host. Sense data 0864 0001. The conversation is terminated because of timeout. Consult the system operator.SNA DIA: Attempted de-allocation after end of conversation. A conversation is allocated (started) and de-allocated (ended) after use by a transaction program. A de-allocation on an already de-allocated program is an error condition. Do not de-allocate.SNA DIA: Invalid parameter in Allocate request. Verify all the parameters i n Allocate request.Reserved.SNA DIA: Host resources not available. Retry; if repeated attempts fail, consult the host system operator.SNA DIA: Local resources unavailable. Retry; if repeated attempts fail, contact Technical Support.SNA DIA: Unexpected sense code received. Retry; if repeated attempts fail, consult the host system operator. If a line monitor is available, get the sense code value before contacting the host operator.SNA DIA: Function issued or parameter sent is not supported. Correct ! tce was received with a CNM that is not being serviced by any user.SNA Network Gateway, SNA/X.25 Gateway, SNA Transport: A ReadMnStatistic or ReadStatistic request was received with return buffer that is too small to accept all the maintenance data.SNA Network Gateway, SNA/X.25 Gateway, SNA Transport: A ReadREQMS or ReadNmvt request was received with return PIU buffer that is too small to accept the request fro m the host.SNA Network Gateway, SNA/X.25 Gateway, SNA Transport: No REQMS/NMVT request is available at this time. The user may issue a request with Timeout equal to 0FFFFh or issue another Read REQMS at a later time.SNA Network Gateway, SNA/X.25 Gateway, SNA Transport: A RECFMS or NMVT request is currently waiting to be sent, or the solicited state of the request is incorrect. The user may try a request at a later time.Reserved.SNA DIA: No active LU (Logical Unit) to LU session (LU-LU session). The  LU-LU session must be active for data interchange to occur during the session. The LU-LU session is established by the host sending a Bind RU (Request Unit). Verify this with a system operator on the host side. You can also use a line monitor to see if the Bind RU has been received.Reserved.SNA DIA: No LU available at this time. Configure the DIA Transport Service with more LUs.SNA DIA: Conversation type mismatch. Sense data 1008 6034. The two conversation types for LU 6.2 (Basic and Mapped) have t o match on both sides.SNA DIA: PIP not allowed. Sense data 1008 6031. Program Initialization Parameters (PIP) are not allowed in the Allocate verb. Do not use PIP parameters.SNA DIA: PIP not specified correctly. Sense data 1008 6032. Respecify Program Initialization Parameters (PIP) parameters.SNA DIA: Security invalid. Sense data 080F 6051. The remote LU rejected the user ID or password in the Allocate verb. Use the correct ID or password.Reserved.SNA DIA: Sync level not supported. Sense da ta 1008 6041. Change the sync level to match the remote program sync level.SNA DIA: TPN (Transaction Program Name) not available at host. Do not retry again. Sense data 1008 6021. Change the TPN name.SNA DIA: TPN (Transaction Program Name) not available at host. Do not retry again. Sense data 084C 0000. Do not retry the Allocate verb request. Consult the host system operator.SNA DIA: Transaction Program Name (TPN)) not available at host. Retry again. Sense data 084B 6031. Retry the Allocation  verb request after a short delay.SNA DIA: Backout initiated by host. The host program returns back to the last synchronization point. Retry again; if repeated attempts fail, consult the host system operator.SNA DIA: Function aborted by host. Sense data 0864 0001. The conversation is terminated abnormally. Retry; if repeated attempts fail, consult the host system operator.SNA DIA: Function aborted by host. Sense data 0864 0001. The conversation is terminated because of a system logic error.   Consult the host system 4 he parameters; if the parameters appear correct, consult the host system operator.SNA DIA: Illegal state. This is an internal error. Retry; if reeated attempts fail, contact Technical Support.Reserved.SNA DIA: Memory is low.SNA DIA: Bind is rejected by host. Correct the Bind parameters; if the parameters appear correct, consult the host system operator.SNA DIA: Initself rejected by host. Correct the Initself parameters; if the parameters appear correct, consult the host system operator.SNA DIA: $ Termself rejected by host. Correct the Termself parameters; if the parameters appear correct, consult the host system operator.SNA DIA: Session reset. Retry; if repeated attempts fail, consult the host system operator.SNA DIA: Unable to send Initself. Retry; if repeated attempts fail, contact Technical Support.SNA DIA: Host application not available.SNA DIA: Line has gone down. Check the modem and modem cable. Make sure that the RS-232-C connectors are plugged in properly and are connected to the c & orrect channel.SNA DIA: Invalid configuration file.SNA DIA: SNA Gateway is not installed. DIA Transport Service needs SNA Gateway services. Install the SNA Gateway before you install DIA Transport Service.SNA DIA: SNA DIA Transport Service is already installed.Reserved.Internal program/application error. A program or application encountered an internal error that caused it to discontinue normal operation and terminate. The program or application displays the description of the error.OFIS Mail, CT-Mai( l: Invalid message Work Area The Message Work Area has been erroneously modified by the user or InitMailMsgBuffer was not called.OFIS Mail, CT-Mail: Invalid message The message does not conform to the Message Facilities implementation of the National Institute of Standards and Technology (NIST) specifications.OFIS Mail, CT-Mail: No such component The call to GetMsgComponentByPosition specifies a component index that is greater than the last component in the message.OFIS Mail, CT-Mail: No such element$*  The call to GetMsgComponentByID or GetMsgComponentByPosition specifies a subcomponent index that is greater than the last element of the field.OFIS Mail, CT-Mail: No such message ID The call to GetMsgComponentByID specifies a message field identifier that is not present in the message.OFIS Mail, CT-Mail: Message nested too deep The call to InitMailMsgBuffer specifies a message file that is itself an indirection to a message file.OFIS Mail, CT-Mail: Invalid component. The call to GetMsgComponentbyID 0, specifies a component that is not supported.OFIS Mail, CT-Mail: Invalid conversion type The call to GetMsgComponentByID or GetMsgComponentByPosition specifies a type conversion that is not supported.OFIS Mail, CT-Mail: Invalid argument The PutMsgComponent procedure was called with fNewElement = false; however, the specified field does not already exist in the message.OFIS Mail, CT-Mail: Unsupported message type The message does not conform to the Message Facilities implementation of the National Insti<. tute of Standards and Technology (NIST) specification.OFIS Mail, CT-Mail: Early message end The size of the message buffer or the message file provided is not consistent with the internal structures indicating the amount of data in the message.OFIS Mail, CT-Mail: Message already enclosed The EncloseMsg procedure was called; however, the message is already contained in an envelope.OFIS Mail, CT-Mail: Message not enclosed The DetachMsg procedure was called; however, the message does not contain an envelH0 ope.Reserved.OFIS Mail, CT-Mail: Message Facilities internal error An invalid procedure was called.OFIS Mail, CT-Mail: VM allocation error A problem was encountered in creating a Virtual Memory buffer.OFIS Mail, CT-Mail: Invalid VM buffer Attempted to release an unallocated Virtual Memory buffer.OFIS Mail, CT-Mail: Major VM buffer A Virtual Memory management inconsistency.OFIS Mail, CT-Mail: Too many buffers The cal4  y The first entry of the new folder does not match the first entry of the old folder.OFIS Mail, CT-Mail: Wrong number of entries The new folder has a di>  fferent number of entries than the old folder.OFIS Mail, CT-Mail: Entry past end of file The specified entry does not exist.OFIS Mail, CT-Mail: Not initialized The call to reorganize a folder failed.OFIS Mail, CT-Mail: Invalid mode. The folder was opened incorrectly. Reserved.OFIS Mail, CT-Mail: Invalid mail handle The mail handle does not identify an open mail connection. If you installed a Communications or Remote Mail Manager in a cluster workstation, reset the master, and then reinstalled the@   Mail Server, the Mail Server no longer knows about the Communications or Remote Mail Manager's mail connection. When the Communications or Remote Mail Manager makes a mail request, the system returns the error 10100. Deinstall, then reinstall the Communications or Remote Mail Manager.OFIS Mail, CT-Mail: No more mail The systeml to InitVm specifies more than 64 short buffers or 8 long buffers.OFIS Mail, CT-MaT2 il: No free VM buffer There is not enough memory to create a Virtual Memory buffer.OFIS Mail, CT-Mail: All VM buffers are allocated A maximum of 16 Virtual Memory buffers are allowed.OFIS Mail, CT-Mail: VM bad file handle An invalid file handle was specified in a read or write call.Reserved.OFIS Mail, CT-Mail: Not a folder The file is not an OFIS Mail folder.OFIS Mail, CT-Mail: Folder not opened An operation was attempted on an unopened folder.OFIS Mail, CT-Mail: Bin out of range Bin numbers ran`4 ge from 0 to 2.OFIS Mail, CT-Mail: No index entry The entry specified by the index does not exist.OFIS Mail, CT-Mail: Entry out of range The specified entry is not valid.OFIS Mail, CT-Mail: Entry not in use The specified entry is not in use.OFIS Mail, CT-Mail: Entry already exists An attempt was made to create an entry that already exists.OFIS Mail: Index full CT-Mail: Folder is full The file folder has no more room for new messages. Move some messages into another file folder, or delete any mal6 ssages that are no longer needed. Use the Reorganize command (refer to your application's documentation). If you are adding a center, user, or communications manager, check the size of the NameRegistry in the Mailcenter.config file. If you are adding a distribution list, check the size of the DistributionLists in MailCenter.config. You may need to increase these parameters and reconfigure your mail center.OFIS Mail, CT-Mail: Map full The document is too large.OFIS Mail, CT-Mail: Unsorted folder. An ax8 ttempt was made to add a keyed entry to an unsorted folder.OFIS Mail, CT-Mail: Sorted folder An attempt was made to add a dated entry to a sorted folder.OFIS Mail, CT-Mail: Invalid index size Too large an index was specified.OFIS Mail, CT-Mail: File Access Method (FAM) error.OFIS Mail, CT-Mail: Cannot checkpoint An error was encountered in writing to the disk.OFIS Mail, CT-Mail: Invalid folder size A folder was specified which was too large.OFIS Mail, CT-Mail: Too many processes Too many drone pr:  ocesses exist.OFIS Mail, CT-Mail: Too many pages held Too much memory is already being used.OFIS Mail, CT-Mail: Page not held The specified portion of memory is not currently being used.OFIS Mail, CT-Mail: Folder Access Method (FAM) timeout. A Folder Access Method operation was not completed within one minute. The folder could not be opened, as it is in use by another Mail Server process. This sometimes occurs when the Mail Server is delivering a lot of mail at one time, such as during an organizati<  on update.OFIS Mail, CT-Mail: Cannot sort by date A problem was encountered when attempting to reorganize a folder by date.OFIS Mail, CT-Mail: Not mode exclusive The folder was opened incorrectly.OFIS Mail, CT-Mail: First entry The first entry of the new folder does not match the first entry of the old folder.OFIS Mail, CT-Mail: Mismatch first entr5  has no more mail for the Mail User.OFIS Mail, CT-Mail: Not last message received The sequence number (sN) specified in the AcknowledgeMailReceipt request does not correspond toB   the last message returned in a ReceiveMail request.OFIS Mail, CT-Mail: Mail user terminated The mail connection for the mail user was terminated, possibly through FINISH or ACTION-FINISH. The request cannot be serviced.OFIS Mail, CT-Mail: Buffer too small The buffer provided for the returned message in ReceiveMail is too small to hold the message.OFIS Mail, CT-Mail: Mailbox message too large A long message was received which was not in a mail message file.OFIS Mail, CT-Mail: Invalid originator TheD  Mail User (or Mail Center) is not registered with the Mail Center. The designated originator of the message is not the same as the user who submitted the message for delivery, or it does not contain the correct center name.OFIS Mail, CT-Mail: Invalid recipient The Mail User (or Mail Center) is not registered with the Mail Center. The intended recipient of the message is not a valid mail user or is an unrecognized mail center name. Check to see that you have correctly spelled the user's name and whetheF r the recipient is a valid mail user at the remote center.OFIS Mail, CT-Mail: Mail Server inconsistency Usually fatal, use PLOG to see error. OFIS Mail, CT-Mail: Too many recipients You must address the message to a smaller number of recipients. The maximum number is 256 different mail centers.OFIS Mail, CT-Mail: Mail Center is busy Your Mail Center cannot handle any more Mail Users. After another Mail User signs off, you can access the Mail Center.OFIS Mail, CT-Mail: Name not recognized The Mail H User name you entered does not correspond to a valid user, center, or Communications Manager at this center. Ensure that the Administrators of remote Mail Centers have the correct information and passwords for your Mail Center.OFIS Mail, CT-Mail: User is already signed on Someone is signed on to the Mail Center with that Mail User name (at another workstation).OFIS Mail, CT-Mail: Mail access denied The correct password was not supplied for a mail operation. Display the Communications Activity Status. J  If the system is sending the error 10113 to a Communications Manager that is trying to connect with another Mail Center, the passwords for the two mail centers are not identical. Check your mail center configuration and contact the other Mail Center administrator.OFIS Mail, CT-Mail: Mail Server already installed To reinstall the Mail Server, reset the system, or issue the Deinstall Mail Server and Install Mail Server commands.OFIS Mail, CT-Mail: Mail Server cannot load Executive Invalid exit run filL e.OFIS Mail, CT-Mail: Sectors are not multiple The buffer must be a multiple of 512 bytes.OFIS Mail, CT-Mail: Mail Server bad request code The Mail Server received a request for an operation that it does not perform.OFIS Mail, CT-Mail: Mail Server has malfunctioned Use the Executive PLOG at the Mail Center workstation to determine the cause of the error. Look for entries that contain three bytes of secondary status. After you solve the problem, reset the system and install mail services.OFIS Mail, CN T-Mail: To Be Delivered file overflow The To Be Delivered file has more unacknowledged messages than space. Revise your Mail Center configuration (enter a larger value for the Maximum Number of Unacknowledged Messages).OFIS Mail, CT-Mail: No more list names End of list.OFIS Mail, CT-Mail: No such distribution list The distribution list name you entered does not exist. Display the Distribution List Summary to check distribution list names.OFIS Mail, CT-Mail: Too many list nesting levels The distribQ ution list contains too many levels of distribution lists. The maximum is five levels of nesting.OFIS Mail, CT-Mail: Circular distribution list The distribution list either: - includes an entry for itself - includes a distribution l5  rd retrieved from the name registry file does not match the request.OFIS Mail, CT-Mail: Center already removed An attempt was made to remove a Center that does not exist.OFIS Mail, CT-Mail: Invalid unique ID The unique ID is null.OFIS Mail, CT-Mail: Too many requests The maximum number of pending requests has been exceeded.OFIS Mail, CT-Ma\_ il: Wrong record type A different record type was returned than was expected.OFIS Mail, CT-Mail: Invalid sector The user record was retrieved from the wrong place in the name registry file.OFIS Mail, CT-Mail: Status too large The specified buffer is too small.OFIS Mail, CT-Mail: Not an agent The record is not an agent record.OFIS Mail, CT-Mail: Too many Communications Managers You can install a maximum of eight Communications Managers in your Mail Center.OFIS Mail, CT-Mail: Center not removed Anha  error was encountered in removing the specified Center.OFIS Mail, CT-Mail: Invalid key The specified key is zero.OFIS Mail, CT-Mail: Invaist that includes an entry for itselfOFIS Mail, CT-Mail: Bad operation code An invalid operation code was specified when calling QueryMailConfiguration, QueryMailStatus, or ConfigureMail.OFIS Mail, CT-Mail: Insufficient privileges The Mail User name is not registered forS  administrative privileges.OFIS Mail, CT-Mail: Not locked The sector is not locked.OFIS Mail, CT-Mail: No such Mail Center The Mail Center name you entered is not registered with your Mail Center. Display the Center Directory to check Mail Center names.OFIS Mail, CT-Mail: No such Communications Manager The Communications Manager name you entered is not registered with your Mail Center. Display the Communications Manager Directory to check Communications Manager names.OFIS Mail, CT-Mail: Too many it U ems being changed You cannot change any more Mail Users, Mail Centers, Communications Managers, or Remote Mail Managers at this time. Try again later.OFIS Mail, CT-Mail: Mail user already exists The Mail User name you entered has already been registered at this Mail Center. Enter a different name.OFIS Mail, CT-Mail: Mail center already exists The Mail Center name you entered has already been registered at this Mail Center.OFIS Mail, CT-Mail: Communications Manager already exists The Communications ,W Manager name you entered has already been registered at this Mail Center. Enter a different name.OFIS Mail, CT-Mail: Distribution list already exists The Distribution List name you entered has already been registered at this Mail Center. Enter a different name.OFIS Mail, CT-Mail: Invalid list owner The specified user does not own the specified list.OFIS Mail, CT-Mail: User already removed An attempt was made to remove a user that does not exist.OFIS Mail, CT-Mail: User not removed A problem was en8Y countered in removing the specified user.OFIS Mail, CT-Mail: Bad information length A buffer size greater than the maximum amount of data returned was specified.OFIS Mail, CT-Mail: Invalid privileges The specified privilege is not standard or administrator.OFIS Mail, CT-Mail: User locked The user, mail center, Communications Manager, or Telex/TWX Manager is currently being modified by the system administrator. The administrator must remore the appropriate status window from the Interactive Mail ManagD[ er screen before the attempted operation can be completed.OFIS Mail, CT-Mail: Invalid name registry An internal software error has damaged your Mail Center Name Registry. Create a new Name Registry by using the CONFIGURE MAIL CENTER command. You may be able to reconstruct a valid Name Register from the NameRegistry-old file (rename the file to remove the -old suffix). If necessary, add Mail Users, other Mail Centers, Communications Managers, and Remote Mail Managers.OFIS Mail, CT-Mail: Already locked P]  An attempt was made to lock a locked sector.OFIS Mail, CT-Mail: No connection There is currently no mail to send.OFIS Mail, CT-Mail: Name not the same The reco6 lid precedence The specified precedence is greater than the maximum allowed.OFIS Mail, CT-Mail: No more info There is no more information to return.OFIS Mail, CT-Mail: Mail Server suspended Use the RESUME MAIL SERVER command to resume Mail Center operations.OFIS Mail, CT-Mail: Mail Server not suspended You cannot use the RESUME MAIL SERVER command because the Matc il Server is not suspended.OFIS Mail, CT-Mail: TBD inconsistency To Be Delivered record inconsistency.OFIS Mail, CT-Mail: Cannot verify that delivery has occurred The system could not deliver the message before the expiration time elapsed. Check your center configuration to make sure the system can make the connection.OFIS Mail, CT-Mail: Mail Server not numeric The specified number is not numeric.OFIS Mail, CT-Mail: No mailbox The User or Center mailbox does not exist.OFIS Mail, CT-Mail: Mail Serve er Stack Overflow The Mail Server process stack overflowed.OFIS Mail, CT-Mail: Invalid To Be Delivered file The To Be Delivered file is corrupt. Use the CONFIGURE MAIL CENTER command to create a new file and install the Mail Server.OFIS Mail, CT-Mail: Nonlocal distribution list You can use only distribution lists registered in your Mail Center.OFIS Mail, CT-Mail: Index too large An invalid agent or net index was specified in a QueryMailStatus call.OFIS Mail, CT-Mail: Invalid mailbox size The numbeg r of allowable mailbox entries is zero.OFIS Mail, CT-Mail: User is signed on to Mail You cannot remove this Mail User because someone is signed on with this Mail User's name.OFIS Mail, CT-Mail: Center is signed on to Mail You cannot remove this Mail Center because the center is exchanging mail.OFIS Mail, CT-Mail: Communications Manager is installed You cannot remove this Communications Manager because the Communications Manager is installed. Reset the system and remove the Communications Manager.OFISi   Mail, CT-Mail: Administrator cannot be removed You cannot remove the primary Mail Administrator. You can change the primary Mail Administrator by editing the MailCenter.config file and then configuring the center.OFIS Mail, CT-Mail: Administrator cannot be renamed You cannot rename the primary Mail Administrator. You can change the primary Mail Administrator by editing the MailCenter.config file and then configuring the center.OFIS Mail, CT-Mail: Cannot change Administrator's privileges You cannot k !change the primary Mail Administrator's privileges. You can change the primary Mail Administrator by editing the MailCenter.config file and then configuring the center.OFIS Mail, CT-Mail: Center not recognized The message originated from a Mail Center that is not registered with your Mail Center.OFIS Mail, CT-Mail: Too many hops The message traveled through too many Mail Centers before reaching its ultimate destination. Choose a more direct delivery path.OFIS Mail, CT-Mail: Circular routing path Them " message has already passed through this Mail Center in its delivery path. Check that the delivery paths specified at this Mail Center are consistent with those at other Mail Centers.OFIS Mail, CT-Mail: Not enough large buffers Not enough large buffers are specified in the Mail Center configuration file.OFIS Mail, CT-Mail: Wrong node name for center You specified a CT-Net (or BNET) node name in the Mail Center configuration that CT-Mail (or OFIS Mail) cannot accept. Make sure the Mail Center and node o #names are consistent for each Mail Center.OFIS Mail, CT-Mail: No more To Be Delivered replies All To Be Delivered replies have been processed.OFIS Mail, CT-Mail: Invalid list name An invalid Distribution List name was specified.OFIS Mail, CT-Mail: Invalid envelope The message submitted for delivery to the Mail Server contains an envelope and was submitted by a Mail User, or it does not contain an envelope and was submitted by a Mail Center.OFIS Mail, CT-Mail: Cannot administer now You cannot modify q $the Mail Center configuration now. Try again6  An attempt was ~ *made to add an Organization that already exists.OFIS Mail, CT-Mail: Signon not allowed The specified record type cannot establish a connection with another Mail Center.OFIS Mail, CT-Mail: Messages too long Only 10240 characters are allowed in the MailCenter.cnfg and MailMsg.bin files.OFIS Mail, CT-Mail: Inconsistent net routing The Mail Center is not marked as using the net.OFIS Mail, CT-Mail: No such User Directory record The specified Organization list user record does not exist.OFIS Mail, CT-Mail +: Too many duplicate names Too many duplicate Organization user namesOFIS Mail, CT-Mail: Key found Found the index key to the name registryOFIS Mail, CT-Mail: Cut off at start A bad value was specified for nEntriesBefore for operation 510 (directory of remote users) in a QueryMailConfiguration call.OFIS Mail, CT-Mail: Cut off at end A bad value was specified for nEntriesAfter for operation 510 (directory of remote users) in a QueryMailConfiguration call.OFIS Ma later.OFIS Mail, CT-Mail: Cannot reset Mail Server You cannot deinstall, suspend, or resume the Mail Server from a cluster workstation.OFIS Mail, CT-Mail: The Mail Server has been shut down The system is suspending or deinstalling the Mail Server.OFIS Mail, CT-Mail: No free Mail Server processes Currently there are no Mail Server processes free to handle the incoming CT-Net (or BNET) connection request from another mail center.OFIS Mail, CT-Mail: Synchrons %ization problem The system encountered a synchronization problem while attempting to make the connection. The system will retry the connection automatically.OFIS Mail, CT-Mail: Network failure A timeout has occurred in the transmission of data over CT-Net or BNET.OFIS Mail, CT-Mail: Recipient name too long The total length of the name of the recipient exceeds 200 characters.OFIS Mail, CT-Mail: Circular forwarding or aliasing The combination of automatic forwarding and aliasing of the specified recipu &ient refers to the original recipient name or exceeds the maximum of five such recipient changes.OFIS Mail, CT-Mail: Past end date The do not deliver after date has expired.OFIS Mail, CT-Mail: User not registered No Mail User is currently registered with the Mail System for purposes of new mail notification on this workstation.OFIS Mail, CT-Mail: Mail Server deinstalled The Mail Server is deinstalled.OFIS Mail, CT-Mail: Mail Server suspended The Mail Server is suspended.OFIS Mail, CT-Mail: Mail Sew 'rver resumed The Mail Server is resumed.OFIS Mail, CT-Mail: Invalid command case You entered an invalid command case value when you created the command (refer to your Executive Reference Manual).OFIS Mail, CT-Mail: Center is routed The routing between the Mail Centers is inconsistent. Ensure that mail is routed along the same path (distributed through the same intermediate centers).OFIS Mail, CT-Mail: Not multipartition This is not a multipartition operating system.OFIS Mail, CT-Mail: Telex/TWX mesy (sage not accepted A Mail Center attempted to send a Telex/TWX message to another mail center; however, it is not privileged to do so.OFIS Mail, CT-Mail: Circular forwarding across centers The sequence of automatic forwardings of the message from its original recipient has led to an unresolvable circular reference.OFIS Mail, CT-Mail: Too many connect tries Too many failed attempts were made to connect to another Mail Center.OFIS Mail, CT-Mail: Missing Mail Center config file The [Sys]MailCenter.c| )nfg file does not exist.OFIS Mail, CT-Mail: Mail Server installed The Mail Server is installed.OFIS Mail, CT-Mail: Bad user record Could not construct mailbox path.OFIS Mail, CT-Mail: Unsupported Operating System OFIS Mail cannot execute on an operating system older than BTOS version 4.0. CT-Mail cannot execute on an operating system older than CTOS version 9.1.OFIS Mail, CT-Mail: No such organization The specified Organization does not exist.OFIS Mail, CT-Mail: Org already exists 7 il, CT-Mail: Cut off at start and end ( , Bad values were specified for nEntriesBefore and nEntriesAfter for operation 510 (directory of remote users) in a QueryMailConfiguration call.OFIS Mail, CT-Mail: Message file missing The MailMsg.bin file does not exist.OFIS Mail, CT-Mail: No user directory The UserDirectory filename is null.OFIS Mail, CT-Mail: TWX center Used to inhibit the sending of a TBD reply to a Telex/TWX Center.OFIS Mail: No such sequence number CT-Mail: The mailbox item does not exist.OFIS Mail, CT-Mail: Message cancelled4 - The CANCEL or KILL Message feature was invoked to move an outgoing message into Dead Mail.OFIS Mail, CT-Mail: Subject field indication Used to indicate the subject field for reporting To Be Delivered failures.OFIS Mail, CT-Mail: Send/Receive request not legal Only User and Center clients may send mail messages. Send-only clients may not receive mail messages.OFIS Mail, CT-Mail: User record cannot be changed You cannot move the mailbox path of the Administrator or internal Mail Server record. The u@ .ser record was not changed.OFIS Mail, CT-Mail: User not at center The user is not located at the specified center.OFIS Mail: Mail Center needed in org. The center cannot be removed because it is a members of an organization of which the local center is not the capital. (Internal) OSI Message Handling System, OFIS Access to X.400: No Such OSI Node The OSI Node name you entered is not registered with your Mail Center. Display the Node Directory to check OSI Node names.OFIS Mail: The other centers inL / the organization have been notified that they should remove the center if possible, however the center cannot be removed from the local center, because it is a member of another organization. OSI Message Handling System, OFIS Access to X.400: OSI Node Already Exists The OSI Node name you entered has already been registered at this Mail Center.OFIS Mail, OSI Message Handling System, OFIS Access to X.400: No Such OSI Path The OSI Path name you entered is not registered with your Mail Center. Display thX 0e Path Directory to check OSI Path names.OFIS Mail, OSI Message Handling System, OFIS Access to X.400: OSI Path Already Exists The OSI Path name you entered has already been registered at this Mail Center.OFIS Mail, OSI Message Handling System, OFIS Access to X.400: Invalid X.400 Recipient Specification The message has an improperly constructed X.400 recipient specification. Use the CODE-M form to enter X.400 recipient names.Reserved.OFIS Mail, CT-Mail: Stack is full You cannot save any more memos. d 1Mail or discard the memos in progress.OFIS Mail, CT-Mail: No user directory There is no user directory to display.OFIS Mail, CT-Mail: Cannot print user directory You cannot print a user directory from PMM.OFIS Mail, CT-Mail: Not implemented The feature has not yet been implemented.OFIS Mail, CT-Mail: Invalid user name You specified an invalid Mail User name.OFIS Mail, CT-Mail: Cannot wordwrap The inserted character will cause a word to wrap off the screen.Reserved.OFIS Mail, CT-Mail: Disconnect rp 2eceived The system has dropped the communications link with the other Mail Center at the request of the other center.OFIS Mail: Disconnect received CT-Mail: No more remote mail There is no more incoming mail.OFIS Mail, CT-Mail: Wrong type received in message mode Invalid record, expecting MSG record. This is an internal error that indicates a problem with the software you are using.OFIS Mail, CT-Mail: Wrong type received in file header mode Invalid record, expecting HDR record. This is an internal| 3 error that indicates a problem with the software you are using.OFIS Mail, CT-Mail: Wrong type received in file data mode Invalid record, expecting DTA record. This is an internal error that indicates a problem with the software you are using.OFIS Mail, CT-Mail: Sequence out of order Expecting a different record number. This is an internal error that indicates a proble7  orted yet The software does not support the device you specified.OFIS Mail, CT-Mail: No phone number Enter the phone number for the remote Mail Center.OFIS Mail, CT-Mail: Not connected Contact the UnisyО :s Customer Support Center.Reserved.OFIS Mail, CT-Mail: Error in read status from Modem Bad status from modem. This is an internal error indicating a problem with the software you are using.OFIS Mail, CT-Mail: Bad modem command An illegal modem command was given. This is an internal error indicating a problem with the software you are using.OFIS Mail, CT-Mail: Modem STXV This is an internal error indicating a problem with the software you are using. Contact the Unisys Customer Support Center.OFIS ܠ ;Mail, CT-Mail: Modem STXQ This is an internal error indicating a problem with the software you are using. Contact the Unisys Customer Support Center.OFIS Mail, CT-Mail: Modem STXX This is an internal error indicating a problem with the software you are using. Contact the Unim with the software you are using.OFIS Mail, CT-Mail: Not connected yet An operation that requires a connection to another Mail Cente 4r was attempted before the connection was made. This is an internal error that indicates a problem with the software you are using.OFIS Mail, CT-Mail: Wrong record length The record is longer than 512 characters. This is an internal error that indicates a problem with the software you are using. OFIS Mail: Wrong Prg returned An invalid response was received from the Mail Server. CT-Mail: Wrong Prq returned An invalid pointer to a request was received from the Mail Server. This is an internal error 5 that indicates a problem with the software you are using.OFIS Mail, CT-Mail: Wrong mail center  The Mail Center connected to the phone number or direct line you specified has a different Mail Center name than you specified.Reserved.OFIS Mail, CT-Mail: Not valid record type Something other than one of the 12 record types was received. This is an internal error that indicates a problem in the software you are using.OFIS Mail, CT-Mail: Not status record Expecting an ACK or REJ record. This is an intern 6al error that indicates a problem in the software you are using.Reserved.OFIS Mail, CT-Mail: Link Disconnect The communications link has been disconnected. Make sure that the cables are properly connected and that the modems are functioning correctly.OFIS Mail, CT-Mail: Checksum error The record was corrupted.OFIS Mail, CT-Mail: Excessive error rate The system has encountered communications errors in excess of the range you specified when you configured the center.OFIS Mail, CT-Mail: Too many retrie 7s The system has encountered communications errors in excess of the range you specified when you configured the center and the system could not transmit a block of data despite repeated attempts.OFIS Mail, CT-Mail: Duplicate frame The same frame was received more than once.Reserved.OFIS Mail, CT-Mail: Cannot reset modem The modem did not respond properly to a reset command. Make sure that: - the modem switch settings are correct - the modem is turned on - the modem cable is wired properly - the c 8able is plugged into the modem and into the correct port of the workstation.OFIS Mail, CT-Mail: Cannot connect in receive mode The systems waited for a connection that did not occur.OFIS Mail, CT-Mail: Cannot connect while in send mode An unsuccessful attempt was made to initiate a mail connection with a remote Mail Center. There was probably no answer to the call at the other end. The remote modem may be busy, turned off, or the telephone line could be noisy or unavailable during voice busy hours, foĜ 9r example, when the call is switched through a PBX. The Mail System tries again later. However, if the problem is caused by calling during busy hours, try changing connection times.OFIS Mail, CT-Mail: Phone number too long Phone numbers cannot contain more than 30 digits.OFIS Mail, CT-Mail: Not supp8 sys Customer Support Center.Reserved.CT-Mail, OFIS Mail: Remote center is busy The Communications or Remote Mail Manager is attempting to call another Mail Center whose line is busy.CT-Mail, OFIS Mail: Dead phone at remote cente <r The Communications or Remote Mail Manager is attempting to call another Mail Center whose line is inoperable.CT-Mail, OFIS Mail: No answer Contact the Unisys Customer Support Center.Reserved.OFIS Mail, CT-Mail: Command does not exist An invalid command string was specified. This is an internal error indicating a problem with the software you are using.OFIS Mail, CT-Mail: Wrong header string An invalid header string was specified. This is an internal error indicating a problem with the software yo =u are using.OFIS Mail, CT-Mail: Quote missing A quote is missing. This is an internal error indicating a problem with the software you are using.OFIS Mail, CT-Mail: Exceeded number of entries There are a maximum of 64 entries per section. This is an internal error indicating a problem with the software you are using.OFIS Mail, CT-Mail: Exceeded buffer size There are a maximum of 1024 characters per section. This is an internal error indicating a problem with the software you are using.OFIS Mail, CT >-Mail: Bad number format An incorrect number was specified. This is an internal error indicating a problem with the software you are using.OFIS Mail, CT-Mail: Bad error code The abort command was expected. This is an internal error indicating a problem with the software you are using.OFIS Mail, CT-Mail: No such Modem name The specified modem name does not exist.OFIS Mail, CT-Mail: Modem name too long You exceeded the maximum of 12 characters for the modem name.OFIS Mail, CT-Mail: Modem name not f  ?ound A modem name was not found.Reserved.OFIS Mail, CT-Mail: File too big The MailCenter.config file is too large. This is an internal error that indicates a problem with the software you are using.OFIS Mail, CT-Mail: Delimiter missing The colon character is missing. This is an internal error that indicates a problem with the software you are using.OFIS Mail, CT-Mail: Missing entry The entry is missing. This is an internal error that indicates a problem with the software you are using.OFIS Mail, C @T-Mail: Duplicate entry The entry is a duplicate. This is an internal error that indicates a problem with the software you are using.Reserved.OFIS Mail, CT-Mail: Cnfg type out of range The specified configuration does not exist. This is an internal error that indicates a problem with the software you are using.OFIS Mail, CT-Mail: Not numeric or too big The number is not numeric or it is too big. This is an internal error that indicates a problem with the software you are using.OFIS Mail, CT-Mail: $ ADir type out of range Specified type does not exist. This is an internal error that indicates a problem with the software you are using.OFIS Mail, CT-Mail: File type out of range Specified type does not exist. This is an internal error that indicates a problem with the software you are using.OFIS Mail, CT-Mail: Folder type out of range Specified type does not exist. This is an internal error that indicates a problem with the software you are using.OFIS Mail, CT-Mail: User type out of range Specifi0 Bed type does not exist. This is an internal error that indicates a problem with the software you are using.Reserved.OFIS Mail, CT-Mail, BNET, CT-Net: Invalid line handle The line handle is not associated with any open modem line. This is an internal error. OFIS Access to X.400: Internal error.Invalid line specification OFIS Mail: Only [Comm] line type is valid for the current version of the Modem Server. OFIS Access to X.400, BNET, CT-Net, CT-Mail: Only [COMM] and [Phone] line types are valid for < Ccurrent version of Modem Server. This is an internal error.Bad pointer in wait OFIS Mail: The pointer to the request is zero. OFIS Access to X.400, BNET, CT-Net, CT-Mail: This is a8  beginning of the lines.OFIS Mail, CT-Mail, BNET, CT-Net: Invalid baud rate. The baud rate configured for the channel is not the same as specified in the request.OFIS Mail, CT-Mail, CT-Net: Buffer size too small The status buffer must be at least 14 bytes. This is an internal error. OFIS Access to X.400, BNET: Internal error. Carrier lost. OFIS Mail: The modem line carrier/receive line si Jgnal detector is not active. This can happen when the cable is disconnected or when the remote modem drops the line when it is reset. OFIS Access to X.400, BNET, CT-Net, CT-Mail: The data carrier detect signal is absent. This can happen when the cable is disconnected or when the remote modem drops the line.OFIS Mail, CT-Mail, BNET, CT-Net: The name specified in Open Modem Line is in use already BNet II, OFIS Access to X.400: Name in use. The name specified in Open Modem Line is already in use. Eit Kher your program is already installed or another program has a duplicate name.CT-Mail: Mn internal error. Consult technical support personnel.OFIS Mail, CT-Mail, BNET, CT-Net: Channel is in use. The channel is already configured for use by the modem server.OFIS Mail, CT-Mail, BNET, CT-Net: ID string is too long The ID string for the AcceptModemCall request is only one character. OFIS Access to X.400: InH Dternal error.OFIS Mail, CT-Mail, BNET, CT-Net: ID string is in use. The ID string specified in the AcceptModemCall request is used by another process. OFIS Access to X.400: Internal error.OFIS Mail, CT-Mail, CT-Net: Invalid count of bytes The specified count is zero. Internal error. Consult technical support personnel. OFIS Access to X.25, BNET: Internal error. Consult technical support personnel.OFIS Mail, CT-Mail, BNET, CT-Net: Exceeds two Read requests Only two ReadModemBytes requests can T Ebe outstanding at one time. OFIS Access to X.400: Internal error.OFIS Mail, CT-Mail, CT-Net: Bad request code The system received a request for an operation that Modem Server does not perform. OFIS Access to X.25, BNET: Internal error. Consult technical support personnel.OFIS Mail, CT-Mail, CT-Net: Modem Server Fatal error Modem Server abnormal termination. This is an internal error that indicates a problem with the software you are using. Call technical support personnel. OFIS Access to X.400` F, BNET: Internal error. Consult technical support personnel.OFIS Mail, CT-Mail, BNET, CT-Net: No more line handles. Only four line handles can be associated with a single channel.OFIS Mail, CT-Mail, BNET, CT-Net: Line handle not connected. The line handle is not actually connected (online) yet, and either read or write modem bytes are being called.OFIS Mail, CT-Mail, BNET, CT-Net: The channel is busy. Some other process is using the channel currently.OFIS Mail, CT-Mail, BNET, CT-Net: Exceeds maximul Gm channels. The modem server can handle up to six channels.OFIS Mail, CT-Mail, BNET, CT-Net: Channel is not configured. Contact the Unisys Customer Support Center.OFIS Mail, CT-Mail, BNET, CT-Net: Channel is released. The channel is released so that programs other than the modem server can use the channel now.OFIS Mail, CT-Mail, BNET, CT-Net: One accept call allowed. When no ID string is specified in AcceptModemCall, only one process can wait for a call to come in.OFIS Mail, CT-Mail, BNET, CT-Net: Rx Hequest still outstanding. The call is trying to perform CloseModemLine when a read or write request is still outstanding.OFIS Mail, CT-Mail, BNET, CT-Net: One open line allowed. For a direct connect line, only one process can open the line.OFIS Mail, BNET: No such line ID. BNet II: Lines out of order. No entry in ModemServer.Config or lines out of order. Line numbers must start at 1. CT-Mail, CT-NET: No lines configured. Check that all necessary lines in the ModemServer.config file have been u Incommented before installing the Modem Server. Uncommented means that the semicolons have been removed from the 9 odem name missing.CT-Mail: Line specification missing.CT-Mail: Baud rate missing.Reserved.OFIS Mail, CT-Mail: Need Telephone Service Install the Telephone Service.OFIS Mail, CT-Mail: Modem Server installed The Modem Server is installed.OFIS Mail, CT-Mail: Not multipartition OS The Modem Server cannot execute on a single partition operating system.OFIS Mail, CT-Mail, BNET, CT-Net: Cannot swap Modem Server. You  Lcannot swap the Modem Server.OFIS Mail, CT-Mail, BNET, CT-Net: Modem Server reset. The Modem Server is deinstalled.OFIS Mail, CT-Mail: Wrong manners Consult Unisys Customer Support Center.OFIS Mail, CT-Mail: Wrong device. This is an internal error that indicates a problem with the software you are using. Consult Unisys Customer Support Center.OFIS Mail, CT-Mail: Manager name too long The name you entered for the Communications or Remote Mail Manager is too long.OFIS Mail, CT-Mail: Manager passwor Md too long The password you entered for the Communications or Remote Mail Manager is too long.CT-Mail: Log file name too long The specified file name for the Communications Manager log file is too long to be valid. This error occurs when Communications Manager 2.0 version is used. For versions 3.0 or 4.0, this status code is no longer used.CT-Mail: Bad Opcode.Reserved.CT-Mail: String from EasyLink host not found. Internal error. This status code indicates an error with the software you are using.  NConsult Technical Support.CT-Mail: Cannot connect.  Internal error. This status code indicates an error with the software you are using. Consult Technical Support.CT-Mail: No more TWX mail. Internal error. This status code indicates an error with the software you are using. Consult Technical Support.CT-Mail: No between string. Internal error. This status code indicates an error with the software you are using. Consult Technical Support.Too many addresses A maximum of 32 addresses can be entered O for computer letter services.Your TWX ID is not valid Verify the ID with the EasyLink Network Service.Invalid TWX/Telex address format The format of the address is not valid for the TWX manager. This can happen if you manually enter the address without using CODE-T.CT-Mail: Message not accepted. Internal error. This status code indicates an error with the software you are using. Consult Technical Support.Reserved.OFIS Mail, CT-Mail: Bad keyboard message There is an unknown message at the keyboard  Pexchange.OFIS Mail, CT-Mail:  No more documents All 35 document slots are in use.OFIS Mail, CT-Mail: No more windows All 12 windows are in use.OFIS Mail: Node not free Problem encountered in allocating a segment of the heap. CT-Mail: Cannot locate place.CT-Mail: No more display line descriptors.CT-Mail: Formatting operator too big.OFIS Mail, CT-Mail: Wrong video The computer video type is not recognized.CT-Mail: Formatting operator too big.OFIS Mail, CT-Mail: Bad formatting operation code The  Qformatting code is out of range.OFIS Mail, CT-Mail: Invalid cursor location The location of the cursor is unknown or invalid.CT-Mail: Too many bins.OFIS Mail, CT-Mail: VM lock error There are too many buffer lock operations.CT-Mail: Bad file format.CT-Mail: Bad format trailer page version.OFIS Mail, CT-Mail: VM read only buffer An attempt was made to write a buffer that is read only.OFIS Mail, CT-Mail: VM dirty page underflow An attempt was made to write a portion of a document to a disk that had R not been modified.OFIS Mail, CT-Mail: Data segment alloc error There is not enough memory for allocation.OFIS Mail, CT-Mail: Bad file number The specified file number is greater than the maximum allowed.OFIS Mail, CT-Mail: Bad Style Invalid style IDOFIS Mail, CT-Mail: Back memory allocation memory.OFIS Mail, CT-Mail: No free Bp There is not enough memory for allocation.CT-Mail: Spool disk full.CT-Mail: Too many user parameters.CT-Mail: Bad Font number.OFIS Mail, CT-Mail: Initialization format 9  -FMultibus Adapter: Attempt to set interrupt handler for Multibus D YAdapter board. FSA Finesse: Record modifiedMultibus Adapter: Attempt to reset interrupt handler that was set by another user. FSA Finesse: Error (nnnnn). Refer to Status Codes manual This message is displayed when an error occurs while: - adding a teller record in Installation Utilities (failed on write process) - deleting a teller record in Installation Utilities (failed on read process) - performing cash balancing. Refer to the relevant part of this status codes documentation for a descriptionP Z of the status code displayed in parentheses.FSA Finesse: Beginning Parameter is Greater than the Ending Parameter Enter a beginning parameter with a value less than the ending parameter.FSA Finesse: Press GO to DELETE the recordFSA Finesse: Record addedFSA Finesse: Record deletedFSA Finesse: Record does NOT exist Reenter a valid record key.FSA Finesse: Record already existsFSA Finesse: File is full No more  Sset error.OFIS Mail, CT-Mail: Software error A problem was encountered in validating message recipients.OFIS Mail, CT-Mail: Invalid Typescript Invalid selection (mark and bound).OFIS Mail, CT-Mail: Invalid doc type Document type out of rangeCT-Mail: Attempted command not yet implemented. Internal error.CT-Mail: Bad message fileCT-Mail: Stack overflow.Reserved.CT-Mail: No such document.OFIS Mail, CT-Mail: Heap full There is not enough memory for allocation.OFIS Mail, CT-Mail: Node not busy A p Troblem was encountered in compacting the heap or freeing a segment of the heap.OFIS Mail, CT-Mail: Bad signature Corrupted heap.OFIS Mail, CT-Mail: Node not free Problem encountered in allocating a segment of the heap.OFIS Mail, CT-Mail: Next tag bad Invalid next used heap segment indicator.OFIS Mail, CT-Mail: Prev tag Bad Invalid previous used heap segment indicator.OFIS Mail, CT-Mail: Next node not free The next free heap segment was incorrectly marked as being free.OFIS Mail, CT-Mail: Next n Uode bad link Invalid link to next free heap segment.OFIS Mail, CT-Mail: Not on free list The free heap segment is incorrectly marked as being free.OFIS Mail, CT-Mail: Bad tag Invalid free/used heap segment indicator.OFIS Mail, CT-Mail: Bad node size Incorrect heap segment size.Reserved.Multibus Adapter: An interrupt handler for this slot has already been established by this user. Message Control System: The Data Communications Processor (DCP) is configured to run on a B25 workstation. FSA Finesse  V: Invalid Selection Refer to the help screen or the BTOS FSA Finesse Installation Utilities Operations Guide for the valid selections to enter.Multibus Adapter: Reset attempted on nonexistent interrupt. Message Control System: The Data Communications Processor (DCP) is configured to run on a shared resource processor. FSA Finesse: Processing ...Multibus Adapter: Invalid slot number specification. Slot numbers must be in the range 20h to 27h and 70h to 77h. Message Control System: MCM Module not , Wavailable. The message control module is not available. FSA Finesse: Entry must be Y or N.Multibus Adapter: Multibus Interrupt Handler table full. No more interrupt handlers can be accomodated. Message Control System: MCS terminated the DCP initialization. FSA Finesse: Value is out of range Refer to the help screen or the BTOS FSA Finesse Installation Utilities Operations Guide for the valid selections to enter.Multibus Adapter: No board exists in designated Multibus Adapter board slot. Message8 X Control System: This DCP is configured to run on a B28. FSA Finesse: Entry must be numeric Enter only 0-9 in this field.Multibus Adapter: Designated Multibus Adapter slot does not contain a Multibus Adapter board. FSA Finesse: Invalid DateMultibus Adapter: Hardware malfunction in Multibus Adapter board. FSA Finesse: Entry must be a valid Hexadecimal Code Enter a 2-character code. Values for each of the characters are: - 0-9 - A: records can be added to the file until you delete an existing record.FSA Finesse: SETTLE F\ [ile does NOT exist. Press GO to create the FileFSA Finesse: Upper Limit must NOT be less than the Lower LimitFSA Finesse: Error Reading Electronic Journal Detail File, Press CANCEL to Continue Back up all EJ and Tank files and remove them from the hard disk.FSA Finesse: Electronic Journal Detail File does NOT exist, Press CANCEL to Continue This message is displayed when an attempt to reorganize a nonexisting detail file is made. Cancel the reorganizing process and reorganize an existing detail file.h \FSA Finesse: Error (nnnnn) , Press CANCEL to Continue, Error for Teller (nnn) Reorganization is aborted. Refer to the relevant part of this status codes documentation for a description of the status code displayed in parentheses.FSA Finesse: EJ Detail File Reorganization ABORTED, Press CANCEL to Continue Press the CANCEL key to continue. The file cannot be reorganized.FSA Finesse: No EJ Detail to Reorganize for the Date entered, Press CANCEL to ContinueFSA Finesse: Error Writing the EJ Detail File, t ]Press CANCEL to Continue Back up all EJ and Tank files and remove them from the hard disk.FSA Finesse: Invalid Entry Refer to the help screen for valid entries.FSA Finesse: EJ Index File Reorganization ABORTED for that Teller, Press CANCEL to ContinueFSA Finesse: Error OPENing the Market Research File, Press CANCEL to ContinueFSA Finesse: Error Reading the Market Research Record, Press CANCEL to ContinueFSA Finesse: Error modifying the Market Research Record, Press CANCEL to ContinueFSA Finesse: Err ^or FINDING KEY in the Market Research File, Press CANCEL to ContinueFSA Finesse: Error OPENing the Sales Activity File, Press CANCEL to ContinueFSA Finesse: Error deleting Sales Activity Record, Press CANCEL to ContinueFSA Finesse: Error FINDING KEY in the Sales Activity File, Press CANCEL to ContinueFSA Finesse: Reorganizing the Electronic Journal filesFSA Finesse:  Reorganizing the Customer Service FilesFSA Finesse: Files' Reorganization is completeFSA Finesse: Current entries will be cleared. Pres _s GO to confirm, CANCEL to cancelFSA Finesse: Current changes will be lost. Press GO to confirm, CANCEL to cancelFSA Finesse: Record will be written to disk. Press GO to confirm, CANCEL to cancelFSA Finesse: Entry must be numericFSA Finesse: Value is out of rangeFSA Finesse: Field must not be blank Enter valid value in the field.FSA Finesse: Record writtenFSA Finesse: All IDs are in use The maximum number of IDs have been defined and are in use. To add an ID record: - delete a currently defined ` record - use the ID of the deleted record.FSA Finesse: Return to previous menu, no update. Press GO to confirm, CANCEL to cancelFSA Finesse: Record deletedMultibus Adapter: The server does not lock its partition on a shared resource processor. FSA Finesse: Record will be deleted from disk. Press GO to confirm, CANCEL to cancelFSA Finesse: Record does NOT existFSA Finesse: Entry must be 0 or 1FSA Finesse: Value is previously defined Enter unique values in the field.FSA Finesse: Record retriev aedFSA Finesse: Data will be cleared; press GO to confirm, CANCEL to cancel Change the data entered in the field or press the GO key to clear the field.FSA Finesse: Characters must be 0-9, a-z, or A-Z Enter a correct character.FSA Finesse: Illegal ID The ID entered is not in the acceptable range. Refer to the help screen or the BTOS FSA Finesse Installation Utilities Operations Guide for values to enter.FSA Finesse: Entry must be a valid hexadecimal codeFSA Finesse: Insertion is not possible No slo bt is available to insert a new field. Either delete an allowed, existing field, or do nothing.FSA Finesse: (This message consists of 80 spaces.)FSA Finesse: Cannot delete/insert on an empty fieldFSA Finesse: Sum of all maximum lengths is out of range Enter a sum that does not exceed the allowed limit.FSA Finesse: At l:  rator name.FSA Finesse: Invalid Window Number Enter a valid window number.FSA Finesse: Invalid Report Type Enter a valid report type.FSA Finesse: BTOS Error (nnnnn): Cannot Read DRAWER File An attempt has been made to perform a totals inquiry, but the s iystem cannot read the drawer file. Press the CANCEL key. Refer to the relevant part of this status codes documentation for a description of the status code displayed in parentheses.FSA Finesse: Teller Number Not Found Enter a valid teller number.FSA Finesse: Processing ...FSA Finesse: No TANKed Transactions Present at this TimeFSA Finesse: Press NEXT PAGE for more recordsFSA Finesse: Press PREV PAGE for previous recordsFSA Finesse: Report Request CompletedFSA Finesse: Report Request NOT Processed j: Error (nnnnn) on ACTIVITY File Refer to the relevant part of this status codes documentation for a description of the status code displayed in parentheses.FSA Finesse: Report Request NOT Processed: Error (nnnnn) on DRAWER Feast one maximum length field is required Enter data in a maximum length field. Refer to the help screen or the BTOS FSA Finesse Installation Utilities Operations Guide for values to en cter.FSA Finesse: Entry must be alphanumeric Enter an alphanumeric character.FSA Finesse: Invalid entryFSA Finesse: Beginning position plus length greater than 105 The beginning position plus the length of the field exceeds the limit of 105. Either lower the length or move the beginning position back.FSA Finesse: Entry must be zeroFSA Finesse: (This message consists of 80 spaces.)FSA Finesse: Go to next section, no update. Press GO to confirm, CANCEL to cancelFSA Finesse: Entry must be 1FSA Finess de: (This message consists of 80 spaces.)FSA Finesse: Value is out of rangeFSA Finesse: Return to DEV PARAM menu, no update. Press GO to confirm, CANCEL to cancelFSA Finesse: Station Parameters file is corrupted. Press CANCEL to return to menu Make certain that the .rec and .key files are the same version. Otherwise, you may need to re-create the .key file. Press the CANCEL key to return to the Main Menu.FSA Finesse: Station Parameters file is in use. Press CANCEL to return to menu The Station Pa erameters file is not available. Press the CANCEL key to return to the Main Menu.FSA Finesse: MCR/OCR file is corrupted. Press CANCEL to return to menu Make certain that the .rec and .key files are the same version. Otherwise, you may need to re-create the .key file. Press the CANCEL key to return to the Main Menu.FSA Finesse: MCR/OCR file is in use. Press CANCEL to return to menu The MCR/OCR File is not available. Press the CANCEL key to return to the Main Menu.FSA Finesse: At least one set of Ta fble Element/Type/ID is requiredFSA Finesse: Record does not exist. Press CANCEL to continueFSA Finesse: Next Posting Date must be greater than the current Posting DateFSA Finesse: CRT address cannot be the same as machine addressFSA Finesse: Duplicate Password in Teller File : Error (20310)FSA Finesse: Leading and embedded blanks not allowedFSA Finesse: File has been rebuiltFile is not rebuiltFSA Finesse: Error (nnnnn) Refer to your Status Codes manual; Press any key to terminateFSA Finesse: Unabl ge to Encode / DecodeFSA Finesse: FILE IN USEFSA Finesse: Whole and Decimal Delimiters can not be identical.FSA Finesse: Transactions pending on nnnnnnn to Reorganization STOPPED.FSA Finesse: Press CANCEL to clear screen after inquiry.Reserved.FSA Finesse: (This message consists of 80 spaces.)FSA Finesse: Invalid Entry Enter the time in HHMM format.FSA Finesse: Press GO to ContinueFSA Finesse: Press CANCEL to ContinueFSA Finesse: Press NEXT PAGE for more totalsFSA Finesse: Press PREV PAGE for prev hious totalsFSA Finesse: Invalid DateFSA Finesse: Invalid TimeFSA Finesse: Invalid Application Type Enter a valid application type.FSA Finesse: Invalid Teller Number Enter a valid teller number.FSA Finesse: Invalid Operator Name Enter a valid ope; ile Refer to the relevant part of this status codes documentation for a description of the status code displayed in parentheses.FSA Finesse: Report Request NOT Processed: Error (nnnnn) on EJ Index File Refer to the relevant part of this status codes documentation for a descripti kon of the status code displayed in parentheses.FSA Finesse: Report Request NOT Processed: Error (nnnnn) on SystParam File Refer to the relevant part of this status codes documentation for a description of the status code displayed in parentheses.FSA Finesse: Report Request NOT Processed: Error (nnnnn) on SETTLE File Refer to the relevant part of this status codes documentation for a description of the status code displayed in parentheses.FSA Finesse: Report Request NOT Processed: Error (nnnnn) on TE( lLLER File Refer to the relevant part of this status codes documentation for a description of the status code displayed in parentheses.FSA Finesse: Report Request NOT Processed: Error (nnnnn) on TELLNO File Refer to the relevant part of this status codes documentation for a description of the status code displayed in parentheses.FSA Finesse: Report Request NOT Processed: Error (nnnnn) on Sales Activity File Refer to the relevant part of this status codes documentation for a description of the status c4 mode displayed in parentheses.FSA Finesse: Report Request NOT Processed: Error (nnnnn) on Market Research File Refer to the relevant part of this status codes documentation for a description of the status code displayed in parentheses.FSA Finesse: Report Request NOT Processed: Error (nnnnn) on REPORT File Refer to the relevant part of this status codes documentation for a description of the status code displayed in parentheses.FSA Finesse:  Request for Supervisor Override received: press RECV MSG or CA@  nNCELReserved.FSA Finesse: Error waiting for Message An attempt was made to communicate with the branch processor and one of the following conditions occurred: - five minutes elapsed and there was no response from the branch processor - the branch processor went down. In either case, contact your supervisor.FSA Finesse: Error on Initialization to the Message Control System.FSA Finesse: Cannot send message to CONTROL An attempt was made to terminate processing from the administrative workstation, buL  ot the branch processor went down. Contact your supervisor.FSA Finesse: Report Request NOT Processed: Error (nnnnn) on Sorted ACTIVITY FileReserved.FSA Finesse: Press any key to complete the present transactionFSA Finesse: Request for Supervisor Override NOT PendingFSA Finesse: Password level too LOWFSA Finesse: Password NOT validFSA Finesse: Text Message MUST be enteredFSA Finesse: Terminate all Branch ProcessingFSA Finesse: Press NEXT PAGE for more totals or PREV PAGE for previous totalsFSA FinesX  pse: **Posting Date has changed on the Branch Processor.** Press GO to continue.FSA Finesse: Press GO to Confirm, CANCEL to DenyFSA Finesse: Terminate Administrative ApplicationFSA Finesse: Time Interval Too LargeFSA Finesse: Exiting to Customer Service/TellerFSA Finesse: Exiting to Finesse ExecutiveFSA Finesse: Invalid currency code for editingFSA Finesse: Currency type already existsFSA Finesse: Unable to open Teller File Try operation again. If failure continues, data in teller file may be cord qrupt. Contact your supervisor or Unisys representative.FSA Finesse: SYLK File Request Not Processed: Error (nnnnn) on Syst Param File Refer to the relevant part of this status codes documentation for a description of the status code displayed.FSA Finesse: SYLK File Request Not Processed: Error (nnnnn) on CSTMSales File Refer to the relevant part of this status codes documentation for a description of the status code displayed.FSA Finesse: SYLK File Request Not Processed: Error (nnnnn) on MktResearcp rh File Refer to the relevant part of this status codes documentation for a description of the status code displayed.FSA Finesse: SY;  vices: Invalid connection. The connection resulting from the specified operation is not allowed.Voice Services: Invalid parameters. The parameters to the specified operation are not valid.Voice Services: Not off hook. The voice unit or telephone line must be offhook for the specified operation.Voice Services: Bad handle. The handle you specified was invalid.Voice Services: Timeout. The operation was terminated because a specified time l yimit for completion expired.Voice Services: Invalid module. The module specified is invalid.Voice Services: Not on hook. The line must be onhook for the operation specified.Voice Services: Voice unit on hook. The voice unit must be offhook for the operation specified.Voice Services: Invalid function. The function specified to the TsDoFunction operation is illegal.Voice Services: On hold. The operation was terminated due to the line being placed on hold as the result of command being issued.Voice! z Services: On hook. The operation wLK File Request Not Processed: Error (nnnnn) on SYLK File Refer to the relevant part of this status codes documentation for a description of the status code displayed.FSA Finesse: SYLK File Request CompletedFSA Finesse: SYLK Program Failed The data being used by the SYLK file program is bad or the SLYK file program is bad. Contact your supervisor or Unisys representative| s. The system returns to the last menu displayed after this message is encountered.FSA Finesse: Report Program Failed The data being used by the report program is bad or the report program is bad. Contact your supervisor or Unisys representative. The system returns to the last menu displayed after this message is encountered.FSA Finesse: Unable to Encode / Decode The data being used by the administrative report program is bad. The system returns to the last menu displayed after this message is encoun ttered.FSA Finesse: Percent Delimiter Not Entered Error Reenter rate field using a percent delimiter.FSA Finesse: Invalid Total Set : First Free Set = (nn), Highest Allocated Set = (nn)FSA Finesse: Invalid Percent DelimiterFSA Finesse: Invalid Decimal DelimiterFSA Finesse: Invalid Whole DelimiterFSA Finesse: Report Created; Printer Not Available. An attempt to print an Administrative Report was successful, but there was no printer attached to the workstation. Change the Spooler Online ID field in th ue System Parameters File, Branch Parameters section, to "LPT," and ensure that a printer is connected to the workstation.FSA Finesse: Invalid SelectionFSA Finesse: Invalid Exit KeyFSA Finesse: Entry must be numericFSA Finesse: Not an AdministratorFSA Finesse: Invalid Administrator NumberFSA Finesse: Invalid PasswordFSA Finesse: Processing ...FSA Finesse: TellNo.Dat file not found. Press FINISH to return to the ExecutiveFSA Finesse: Teller.Dat file not found. Press FINISH to return to the Executiv veFSA Finesse: Please terminate process before executing Install UtilitiesFSA Finesse: Cannot execute Utilities on two workstations simultaneouslyFSA Finesse: Service Not AvailableFSA Finesse: Waiting for MCR; Press CancelFSA Finesse: Pass Card Through MCRFSA Finesse: MCR Read Error; Press Cancel or NextFSA Finesse: MCR Open ErrorFSA Finesse: MCR Device ErrorFSA Finesse: This is an MCR Error. Refer to the Device Server Manual.FSA Finesse: Reenter New PasswordFSA Finesse: No Currencies to Print, P wress CANCEL to continueFSA Finesse: Customer Service not available for this workstation.FSA Finesse: Report Request Parameters must be in Operator Name OrderFSA Finesse: Next Posting Date can not be before Current Posting Date.Voice Services: Invalid user. The user number of the program making the request is not an allowed user at this time for the specified operation.Voice Services: Too many connections. The connection resulting from the specified operation cannot be completed because there is no av xailable discrete path through the crosspoint switch.Voice Ser< as terminated due to the phone or line being placed onhook or to a TsOnHook or TsDoFunction (hang up) command being issued.Voice Services: Service reset. The service was reset with the TsDoFunction service.Reserved.Voice Services: Voice work area too small. The work area must be at least 13312 bytes and word aligned.Voice Services: Voice in use. The voice hardware is either in use or has been locked with TsDoFunction.Voice Services: Voice sample not found. The s# {pecified starting sample could not be found.Voice Services: Voice data lost (disk). The voice operation was terminated due to the disk and/or cluster not being able to keep up with the voice data rate.Voice Services: Voice data lost (CPU). The voice operation was terminated due to the Telephone Service process not being able to keep up with the voice data rate.Voice Services: Bad voice parameters. One or more field in the voice control structure are invalid.Voice Services: Invalid voice data file. T% |he signature byte is invalid in a record of the file specified.Reserved.Voice Services: Initialization time out. The Voice Processor module did not respond due to a failure of the Voice Processor module, X-Bus DMA or X-Bus interrupt hardware or software.Voice Services: No request file. The Telephone Service request file did not get loaded by the Operating System during system initialization (boot).Voice Services: Bad request file. The Telephone Service request file is not of the same revision level as' } the Telephone Service.Voice Services: Telephone Service already installed.Voice Services: Voice Processor module failure. The Voice Processor module did not respond due to a failure of the Voice Processor module, X-Bus DMA or X-Bus interrupt hardware or software.Voice Services: Bad request. A request not recognized by the Telephone Service was received at the Telephone Service's service exchange.Voice Services: Bad request block. Information provided in the request block does not agree with expected* ~ values. The sCntInfo, nReqPbCb, and nRespPbCb fields of every request are checked for validity. All constant values, such as 2 for the size of a return word, or 4 for the size of a returned quad are checked for validity. Pointers with non-zero cb's are checked to make sure the pointers are not zero.Voice Services: User swapped. The operation was terminated due to the swapping to disk of the program using the service.Voice Services: Invalid configuration file. The signature word in the configuration  , files specified is invalid.Voice Services: Duplicate request. The request is a duplicate of one currently being processed and is not allowed.Voice Services: Firmware invalid. The Voice Processor module firmware is invalid.Voice Services: Bad deinstallation order. Multiple invocations of the Telephone Service must be deinstalled in the reverse order in which they were installed.Reserved.Voice Services: Bad dial character. A character specified in the dial string is not valid.Voice Services: Dialing . in progress. A TsDial service is in progress using the dialing hardware.Voice Services: No dial tone: Busy. A busy signal was detected instead of dial tone when a wait for dial tone command (=) was processed.Voice Services: No dial tone: Fast busy. A fast busy signal was detected instead of dial tone when a wait for dial tone command ( = ) was processed.Voice Services: No dial tone. No dial tone was detected when a wait for dial tone command ( = or != ) was processed.Voice Services: Bad dial pulse c$0 haracter. A character that can not be dialed (such as # or *) was processed with pulse dialing.Voice Services: Too many characters to dial. No more than 64 characters can be processed at a time.Voice Services: Detector in use. The hardware required for detecting Dual Tone Multifrequency (DTMF) or a dial tone is in use by another operation.Voice Services: No answer. The party being called did not answer.Reserved.Voice Services: Line in use. The line spe<  requests. Refer to your System Administration Guide.System Requests: Illegal parity option. A mark or space parity wx> as specified with eight data bits; the hardware does not allow this combination.System Requests: The user number table used to map global user numbers to local user numbers is too small. Increase the value of the %nRemoteUser parameter in the SysGen.mdf file. Refer to your System Administration Guide.System Requests, Shared resource processor only: The board type is inconsistent with the amount of memory.Reserved.AdminAgent: The default path supplied to mfAdminAgent.run from WsAdminAgent.run is not a v@ alid shared resource processor path (for example, the path is local to a workstation volume). This status code applies to releases prior to CTOS/XE 3.0.AdminAgent: The AdminAgent is busy and cannot service the request. This status code applies to releases prior to CTOS/XE 3.0.AdminAgent: The internal request block sent from the WsAdminAgent to the MfAdminAgent hacified in a TsDataOpenLine operation is in use.02 Voice Services: Invalid line specification. The line specified in a TsDataOpenLine or TsDataUnAcceptCall operation is in use.Voice Services: Invalid line parameters. The line control structure has invalid parameters or an invalid size.Voice Services: Unaccepted issued. The TsDataOpenLine operation is being terminated due to a TsDataUnAcceptCall being issued.Voice Services: No accept call issued. The TsDataUnAcceptCall failed because no TsDataOpenLine operation for the line was waiting to accept the <4 call.Voice Services: Modem driver not installed. The Telephone Service was installed without the modem drivers.Voice Services: Lost carrier. The modem lost the carrier signal.Voice Services: Data overrun. The TsDataRead operation was returned due to a data overrun. Data was lost due to the application failing to issue TsDataRead operations fast enough to keep up with the modem, or due to multiple parity errors.Voice Services: Bad parity. The TsDataRead operation was returned due to bad parity beingH6  detected.Voice Services: TsDataRead or TsDataWrite timeout. The TsDataRead or TsDataWrite operation was returned due to the time limit specified in the operation expiring.Voice Services: End-of-Block character received. The TsDataRead operation was returned due to the specified end of block character being received.Voice Services: Modem initialization failure. The operation was terminated because the specified time limit for completion of the modem initialization expired. The error may be caused bT8 y hardware problems (modem board), poor telephone line quality, mismatched baud rates, or problems with the remote modem. This status code is also returned when the modem drivers are used with no modem present in the module.Voice Services: Line in use: accept call issued. A TsDataOpenLine to accept a call has already been issued for the specified line.Voice Services: Line in use: modem active. An open modem session is already in progress on the specified line.Voice Services: Line in use: modem er`: ror. An open modem session has been terminated with a nonrecoverable error, and the Telephone Service is waiting for a TsDataClose operation or program termination before freeing the modem for other use.Voice Services: Line in use: voice. An open voice or modem session is already in progress on the specified line.Reserved.System Requests: Internal waiting-on-Yblk error.System Requests: Time-out waiting for Data Set Ready (DSR) after an open terminal request.System Requests: The target processor dl< oes not respond. The watchdog noticed that the target processor has crashed or has a hardware failure.System Requests: Routing area too small. When adding request codes, the size of the routing area in the Master Processor's computer definition table was not increased. Increase the value of the sRouteArea parameter in the Master Processor's Prefix.asm file to accommodate the additional = s an improper format. This error can occur if the WsAdminAgent and MfAdminAgent run files are not at the same version level. This status codeB  applies to releases prior to CTOS/XE 3.0.Reserved.Context Manager: Context Manager has received an unknown message.Context Manager: No such partition handle. FSA Finesse: Electronic Journal Header FULL Run the Installation Utilities program and choose the Reorganize Files option.Context Manager: Configuration buffer too small. OFIS Graphics: Only One Graphics Context Allowed The Context Manager will only allow one graphics context on B26 and B28 graphics workstations. FSA Finesse: Detail/Tank AcD cess Error to Invalid LFA.Context Manager: No such context handle. FSA Finesse: BTOS Error (nnnnn). Transaction NOT recorded. CONTACT YOUR SUPERVISOR. A BTOS error occurred when accessing the teller EJ file (EJ..Dat). Refer to the relevant part of this status codes documentation for a description of the status code displayed in parentheses.Context Manager: No such command. FSA Finesse: DISK APPROACHING 100% USED Disk is becoming full. Discontinue processing and make more disk spF ace available.Context Manager: Size too large. FSA Finesse: BTOS Error (nnnnn). Transaction NOT recorded. CONTACT YOUR SUPERVISOR A BTOS error occurred when accessing the teller EJ file (EJ..Dat). Refer to the relevant part of this status codes documentation for a description of the status code displayed in parentheses.Context Manager: Cannot kill self. FSA Finesse: BTOS Error (nnnnn), TOTALs Error, CONTACT YOUR SUPERVISOR Refer to the relevant part of this status codes documentH ation for a description of the status code displayed in parentheses.Context Manager: Using start by block, missing command name.Context Manager: Using start by block, command name too long.Context Manager: Using start by block, missing run file. FSA Finesse: Invalid Date If already signed on to the next posting date, the teller cannot sign on to the current posting date.Context Manager: Using start by block, run file too long. FSA Finesse: Teller Already Signed On Proceed with processing.Context MJ anager: Using start by block, missing memory size. FSA Finesse: Teller NOT Signed On Perform the Local Sign-On routine, entering a unique teller number.Context Manager: No such parent context handle. FSA Finesse: BTOS Error (nnnnn), SystParam File Errors, CONTACT YOUR SUPERVISOR A BTOS error occurred while accessing the System Parameters File (SystParam.Dat). Refer to the relevant part of this status codes documentation for a description of the status code displayed in parentheses.Context Manager: L  No self parent FSA Finesse: BTOS Error (nnnnn), CANNOT Read Totals, CONTACT YOUR SUPERVISOR. Refer to the relevant part of this status codes documentation for a description of the status code displayed in parentheses.FSA Finesse: Cash Drawer has EXCEEDED the Upper Limit By: (nnnnn)FSA Finesse: Cash Drawer has Fallen Below the Lower Limit By: (nnnnn)FSA Finesse: Totals Processed and CLEAREDFSA Finesse: Totals ProcessedFSA Finesse: Branch Totals ProcessedFSA Finesse: Branch Totals Partially ProcN essedContext Manager: This application is not reading the keyboard. FSA Finesse: Batch Totals Processed and CLEAREDContext Manager: Cannot paste to a submit program. FSA Finesse: Balance CompleteContext Manager: Paste already in progress. FSA Finesse: Electronic Journal, TANK, and Teller Totals UpdatedContext Manager: Invalid data transfer parameters. FSA Finesse: Cash Drawer OVERContext Manager: The context cannot terminate the child context. FSA Finesse: Cash Drawer SHORTFSA Finesse: CannoP t Establish Communication with the Host: Error (nnnnn).FSA Finesse: Reentry Begun for Teller; Press FINISH to InterruptFSA Finesse: Reentry SUSPENDEDFSA Finesse: Reentry COMPLETEFSA Finesse: Reentry CANCELLED : Error (nnnnn) on the EJ Index File A BTOS error occurre=  sages to BACKUP BCM discontinues sending messages to the Backup workstation. If this message recurs, contact your data processing department or Unisys representative.FSA Finesse: BACKUP ERROR (nnnnn) Refer to the BTOS FSA Finesse Installation Guide.FSA Finesse: Date only valid for Branch TotalsReserved.F8_ SA Finesse: Supervisor transaction limit exceeded.FSA Finesse: Tlr already signed on at Station (nnn). Signon aborted.Reserved.Context Manager: The run file needed for this application does not exist.Context Manager: There are no more function keys available.Context Manager: There is no active context to return to.Context Manager: The swap file is full -- cannot swap any more contexts.Context Manager: The run file is too large to run in any partition.Context Manager: You cannot logout; there are coDa ntexts which must be finished.Context Manager: Warning: There are active contexts. Press GO to logout or CANCEL to deny.Context Manager: This context cannot be finished fromd while accessing the EJ Index file (EJIndex.Dat). Refer to the relevant part of this status codes manual for a description of the status code displayed in parentheses.FSA Finesse: Reentry CANCELLED : Error (nnnnn) on TANK File A BTOR S error occurred while accessing the EJ Detail/Tank File. Refer to the relevant part of this status codes documentation for a description of the status code displayed in parentheses.FSA Finesse: Reentry CANNOT be Initiated for nn/nn/nn. Try Later An attempt has been made to enter transactions for a date that the system will not accept. Try again later with a different date.FSA Finesse: Reentry CANCELLED : Teller NOT Signed On to Auto Reentry Perform a host sign-on to auto reentry.FSA Finesse: SuT pervisor NOT available Specify another destination for override request.FSA Finesse: Request for authorization is NOT pendingFSA Finesse: Detail/Tank Access Error to Invalid Next LFAFSA Finesse: Detail/Tank Access Error to Invalid maximum record lengthFSA Finesse: Detail/Tank Access Error to Table fullFSA Finesse: Cash Drawer in BALANCEFSA Finesse: Reentry CANCELLED : Host wait time elapsedFSA Finesse: Detail/Tank Access Error to Invalid IndexFSA Finesse: Supervisor has ignored Override RequestFW SA Finesse: Vault Cash Error, Vault is not signed onFSA Finesse: Not enough cash to transfer Verify that there is enough cash in the drawer to transfer and that the amount being transferred is correct.FSA Finesse: Reentry not initiated. No transactions tanked on nn/nn/nn.FSA Finesse: No more Tellers available for Auto-Reentry. Please try again later.FSA Finesse: Status Request ProcessedFSA Finesse: Tellers Still Signed OnFSA Finesse: Message Sent to Destination(s)FSA Finesse: Teller NOT AvailableY  Error occurred while attempting to send an interteller communication. Enter another valid teller short name.FSA Finesse: Invalid Teller Short Name Enter a valid teller short name.FSA Finesse: Error writing the Interview Record Confirm that the Interview.Wp file is present on disk. Also confirm that adequate disk space is available to allow for expansion when writing the Interview Record. If the message recurs, contact your Unisys representative.FSA Finesse: Error writing the New Account Reco [ rd Confirm that the NewAccount.Wp file is present on disk. Also confirm that adequate disk space is available to allow for expansion when writing the New Account Record. If the message recurs, contact your Unisys representative.FSA Finesse: No totals filed on nn/nn/nn.FSA Finesse: No totals filed for Teller (nnn) on nn/nn/nn.FSA Finesse: Drawer access table full. Access denied at this time.FSA Finesse: BCM error. Invalid index for drawer access.FSA Finesse: BACKUP DISK APPROACHING 100% USED Dis,] k is becoming full. Discontinue processing and make more disk space available. If this message recurs, contact your data processing department or Unisys representative.FSA Finesse: Error Sending Mes>  the Context Manager.Context Manager: The file specified as the swap file does not exist.Context Manager: You can run only one graphics application at a time.Reserved.Context Manager: There is no current context.Context Manager: An existing context cannot be swapped out to start a new application.Context Manager: There is not enPc ough room in the swap file to swap the highlighted context.Context Manager: Parent Application Was Terminated A parent cooperating program (for example, OFISdesigner, Document Designer, or OFIS Imager) was terminated before it transferred back the object being edited. Restart the parent application and try again.Context Manager: Context Manager is not installed.Context Manager: ICMS (Intercontext Message Service) is already installed.Context Manager: ICMS internal error.Context Manager: Cannot open \e the ICMS Disk Message file.Context Manager: No message available.Context Manager: No free messages.Context Manager: Not implemented.Context Manager: The message sent was too long.Context Manager: This context is already waiting for messages.Context Manager: ICMS is not installed.Context Manager: Incorrect version or missing Request.CM.sys.Reserved.Data Base: Invalid data base handle. FSA Finesse:  FILE ERROR to (nnnnn)Data Base: Invalid Query identifier. FSA Finesse: Invalid Date FormatFSA Fineshg se: Invalid System Date or Current Posting DateData Base: Invalid Relation identifier. FSA Finesse: Invalid Input ParameterData Base: No more free handles. The memory allocated for handles has been exhausted.Data Base: The specified operation is not implemented for CT-DBMS data bases.Data Base: The specified operation is not implemented for personal data bases.Data Base: An error occurred while the data dictionary was being initialized.Data Base: An error occurred while part of the data dictionati ry was being discarded.Data Base: There is no such data base in the dictionary.Data Base: There is no such relation in the dictionary.Data Base: There is no such attribute in the dictionary.Data Base: There are no more relations in the dictionary.Data Base: There are no more attributes in the dictionary.Data Base: There are no more data bases in the dictionary.Data Base: An error occurred while the data dictionary was being read.Data Base: The specified data base is not open. Multiplan: The specifk ied PDB relation is not open.Data Base: A name cannot be returned because the supplied buffer is too small.Data Base: The specified data type is not currently supported.Data Base: The user does not have read privileges for the specified object.Data Base: The user does not have modify privileges for the specified object.Data Base: The user does not have delete privileges for the specified object.Data Base: The user does not have store privileges for the specified object.Data Base: An error occurred inm  accessing the physical view.Data Base: An error occurred in accessing the physical index.Data Base: An error occurred in accessing the physical scan.Data Base: The physical view is too complex.Data Base: The physical index is too complex.Data Base: The symbol table is full.Data Base: An error occurred during initialization.Data Base: There is not enough memory to initialize.Data Base: Initialization must occur before this operation.Data Base: There is no symbol table.Reserved.Data Base: The pointo er for initializing the work area points to nonaddressable memory.Data Base, Multiplan: An error occurred during initialization.Data Base: The memory area for the Virtual Memory heap is not large enough. Currently, the Virtual Memory heap requires at least 10240 bytes of memory.Data Base, MultiplanCannot open the specified database. An error occurred while the specified data base was being opened. A second status code may appear, giving the reason for the failure.Data Base: The maximum number of data q bases is already open.Data Base: The maximum number of personal data bases is al>   "null allowed" status for this attribute cannot be changed.Data Base, Multiplan: Illegal type conversion. You tried to change an alpha field into a numeric, or vice versa.Data Base: The size of the specified type cannot be changed.Data Base: The Attribute Descriptor Block is the wrong size.Data Base: The mode specified for the query is invalid.Data Base: The specified record is locked by another user.Data Base: The specified value duplicates a value in another record, and this field does no t allow duplicates.Data Base: A null value may not be put into a field that does not allow nulls.Data Base: The user must store values into all fields in the relation that require non-null values.Data Base: The specified data base already exists.Data Base: The data base has too may attribute names, or the size of the data record is too large.Data Base: The specified attribute name is too long.Reserved.Data Base: A number (not a string) was expected to be converted. This is an internal error that iready open.Data Base: The mode specified for opening the data base is invalid.Data Base: The specified data base is already open.Data Base, Multiplan: Cannot create the specified database. An error occurred while the specified data base was being created. A second status code may appear, giving the reason for the failure.Data Base: The specified data base kind is invalid.Data Base: An error occurred while the specified rs elation was being created.Data Base: The specified relation already exists.Data Base, Multiplan: Cannot add field. The specified field or attribute cannot be added. A second status code may appear, giving the reason for the failure.Data Base, Multiplan: Cannot delete field. The specified field or attribute cannot be deleted from the relation. A second status code may appear, giving the reason for the failure.Data Base: The Attribute Descriptor Block is invalid. Data Base: An error occurred during au cceptance of the specified query.Data Base: The specified query is not active.Data Base: The specified query is already active.Data Base: An error occurred while the specified query was being started.Data Base: An error occurred while the specified query was being started.Data Base: The specified relation cannot be modified because an active query exists for it.Data Base: An error occurred while the specified view was being opened.Reserved.Data Base: The mode specified for this view is invalid.Data Bw ase, Multiplan: Illegal query specification. An error occurred during validation of the specified query, or the specified query is illegal. A second status code may appear, giving the reason for the failure.Data Base: The query contains an illegal or unknown attribute name.Data Base: The query contains an attribute name that is too long.Data Base: The query contains a constant value that is too long.Data Base: The query contains too many selection criteria.Data Base: The query contains an illegal sey lection criteria.Data Base: The query results with no data being returned.Data Base: The query can return data only for named attributes.Data Base: The query contains too many attribute names.Data Base: The query requests a data record that is too large.Data Base: The query structure is invalid.Data Base: Illegal data types are being compared.Data Base: The field value being compared is illegal.Data Base: An error occurred during execution of the specified query.Data Base: The memory area specified{  by the user to contain the data record is not long enough.Data Base: There are no more records to be returned for the query.Data Base: An error occurred while the specified query was being set up for execution.Data Base: The specified tuple identifier is illegal or unknown.Reserved.Data Base: An error occurred during redefinition of the specified attribute. Enhanced Multiplan: Cannot modify field. The specified field cannot be modified. The second status code gives the reason for the failure.Data B} ase: The? ndi cates a problem in the software you are using.Data Base, Multiplan: Number is too small to be converted. This is an internal error that indicates a problem in the software you are using.Data Base: Illegal data type for conversion. This is an internal error that indicates a problem in the software you are using.Data Base: A string (not a number) was expected to be converted. This is an internal error that indicates a problem in the software you are using.Data Base: An internal inconsistency was det ected during conversion. This is an internal error that indicates a problem in the software you are using.Data Base: Premature end of the compiled query. This is an internal error that indicates a problem in the software you are using.Data Base: Illegal kind of field in the compiled query. This is an internal error that indicates a problem in the software you are using.Data Base: Illegal kind of node in the compiled query. This is an internal error that indicates a problem in the software you are usi ng.Data Base: The specified view is already executable. This is an internal error that indicates a problem in the software you are using.Data Base: The specified view is not executable. This is an internal error that indicates a problem in the software you are using.Data Base: Illegal kind of structure. This is an internal error that indicates a problem in the software you are using.Data Base: No space available to allocate structure. This is an internal error that indicates a problem in the softwa( re you are using.Data Base: Attempt to de-allocate a nonexistent structure. This is an internal error that indicates a problem in the software you are using.Data Base: No such attribute exists in the specified index. This is an internal error that indicates a problem in the software you are using.Data Base: No such nodes exists in the dictionary. This is an internal error that indicates a problem in the software you are using.Data Base: The dictionary is malformed.Data Base: Attempted to open a data4  base when it is already open.Data Base: The dictionary does not exist.Data Base: Illegal dictionary level. This is an internal error that indicates a problem in the software you are using.Data Base: No such index exists. This is an internal error that indicates a problem in the software you are using.Data Base: There are no more indices. This is an internal error that indicates a problem in the software you are using.Data Base: Illegal access type. This is an internal error that indicates a proble@ m in the software you are using.Data Base: The physical view cannot be freed because it is not open. This is an internal error that indicates a problem in the software you are using.Data Base: Illegal physical view identifier. This is an internal error that indicates a problem in the software you are using.Data Base: The physical index cannot be freed because it is not open. This is an internal error that indicates a problem in the software you are using.Data Base: Illegal physical index identifier. L  This is an internal error that indicates a problem in the software you are using.Data Base: The symbol table is corrupt. This is an internal error that indicates a problem in the software you are using.Data Base: Illegal symbol identifier. This is an internal error that indicates a problem in the software you are using.Data Base: The specified symbol does not exist. This is an internal error that indicates a problem in the software you are using.Data Base: The specified object could not be mappeX d to a symbol. This is an internal error that indicates a problem in the software you are using.Data Base: The specified symbol does not denote a valid symbol identifier. This is an internal error that indicates a problem in the software you are using.Data Base: The return buffer for the symbol is too small. This is an internal error that indicates a problem in the software you are using.Data Base: Attem?  apped. This is an internal error that indicates a problem in the software you are using.Data Base: Illegal heap block identifier. This is an internal error that indicat es a problem in the software you are using.Data Base: The specified block is not accessed. This is an internal error that indicates a problem in the software you are using.Data Base: Illegal heap block size. This is an internal error that indicates a problem in the software you are using.Data Base: The heap is full. This is an internal error that indicates a problem in the software you are using.Reserved.SPA: Attempt to de-queue from empty queue with nonzero count.SPA: Head of queue has forward link  that is not zero.SPA: Element on queue has bad queue base pointer.SPA: Dword to ASCII code inconsistency.SPA: File name record pool exhausted.SPA: Table length inconsistency.SPA: File name record corruption detected by MakeHashEntry.SPA: Prime number table too short.SPA: Attempted to put element on two queuept to de-allocate the handle of a nonexistent structure. This is an internal error that indicates d a problem in the software you are using.Data Base: Illegal kind of handle. This is an internal error that indicates a problem in the software you are using.Data Base: The memory area specified for the record is too small.Data Base: The record identifier specifies a nonexistent or deleted record.Data Base: There are no more records in the scan range.Data Base: The scan ended with an illegal record identifier.Data Base: The specified field name already exists.Data Base: There are no more attributes tp o query.Data Base: The field name to be deleted was not found.Data Base: The field type and length are inconsistent.Data Base: The field name is too long.Data Base: The buffer specified for the relation query is too small.Data Base: Not enough space was given for the work space area.Data Base: Illegal relative attribute number.Data Base: Illegal match kind.Data Base: The attribute value to scan for is more than 64 bytes long.Data Base: Expected attribute not found.Data Base: The attribute is longe| r than specified in the FieldIOSpec.Data Base: The name was truncated to fit into the user buffer.Data Base: The specified field is not variable length; the length may be reset.Data Base: The data base may not be written to in read-only mode.Data Base, Multiplan: File is not a personal database (PDB) relation. You specified a name in the relation area that does not correspond to a PDB relation file.Data Base: Too many field definitions.Data Base: Too many field names.Reserved.Data Base: Too many hea p blocks accessed. This is an internal error that indicates a problem in the software you are using.Data Base: The specified block may not be freed, it is still in use. This is an internal error that indicates a problem in the software you are using.Data Base: Illegal tag in heap (node is neither free nor in use). This is an internal error that indicates a problem in the software you are using.Data Base: The specified block is not on the free list. This is an internal error that indicates a problem  in the software you are using.Data Base: The next block is not on the free list. This is an internal error that indicates a problem in the software you are using.Data Base: The next block has an invalid link. This is an internal error that indicates a problem in the software you are using.Data Base: Illegal tag in previous heap. This is an internal error that indicates a problem in the software you are using.Data Base: Illegal tag in the next heap. This is an internal error that indicates a problem  in the software you are using.Data Base: Illegal heap signature. This is an internal error that indicates a problem in the software you are using.Data Base: Too little space for heap initialization. This is an internal error that indicates a problem in the software you are using.Data Base: All heap blocks are in use, nothing may be sw@ s at once.SPA: File name record corruption detected by ReadRamFile.SPA: AllocHighMemory return value is out of range.Reserved.SPA: File name record corruption detected by UpdateHashEntry.SPA: Ģ  Hash table more than 80% full.SPA: File name record corruption detected by AllocateRemoteFh.SPA: File name record corruption detected by Bounce.SPA: File name record corruption detected by ChangeMode.SPA: File name record corruption detected by ChangeOpenModeReq.SPA: File name record corruption detected by CloseFhRemote.SPA: Attempted to close an inactive file.SPA: Multiple access to non-reentrant routine.SPA: File Name record corruption detected MassIoRead.SPA: Illegal request code.SPA: File NamФ e record corruption detected by OpenFileReqAll.SPA: File Name record has illegal state value.SPA: Inconsistent file handle value.SPA: File handle value out of range.SPA: Missing local handle value in rgoFnRecordLocal.SPA: File Name record corruption detected by PassThruReq.SPA: File Name record corruption detected by RemakeFhReq.SPA: Illegal request code.Reserved.SPA: Lost File Name record.SPA: File Name record corruption detected.SPA: File Name record pointer missing from rgoFnRecordLocal table.Sܦ PA: Active File Name record has zero use count.SPA: Dormant File Name record has nonzero use count.SPA: File Name record has illegal state value.SPA: File Name record is missing from rgoFnRecordHashTable.SPA: File Name record has multiple entries from rgoFnRecordHashTable..SPA: Zero length file name in File Name record.SPA: Missing entry in rgoFnRecordRemote.SPA: Queue with zero count has entries.SPA: Queue with illegal forward or backward link values.SPA: Queue with one element is inconsistent.SP A: Queue with one element has illegal link values.SPA: Queue has inconsistent elements.SPA: Queue element has inconsistent forward link value.SPA: Queue element has inconsistent backward link value.Reserved.CT-Net, B-NET, BNetII: Must enter install number. When installing a media service, no Install Number was specified.CT-Net, B-NET, BNetII: Invalid install number. When installing a media service, the specified Install number was out of range (0 or greater than 99).CT-Net, B-NET, BNetII: Receiv ed bad response. Internal error.CT-Net, B-NET, BNetII: No such line type. An attempt has been made to configure a media line, and the media type field is invalid for the media service. In BNet II, this code can also indicate that two media services have been installed with the same install number, or that there is a switched/lease mismatch.CT-Net, B-NET, BNetII: No free buffer. Internal error.CT-Net: CT-Net Transport Service not installed.CT-Net, B-NET, BNetII: No connection. A dial-up or switch ed connection has failed to complete within the specified connection time, or because of a failure at a lower level.CT-Net, B-NET, BNetII: Invalid buffer number. If the asynchronous service aborts with this code, it may be that a dial-up line has been configured as a leased line.Reserved.CT-Net: When installing a media system service, a media install number has already been used. All media system services when installed must had unique install numbers.CT-Net: This is an internal error that indicates a  n invalid state for disconnecting a session from the Net Agent.CT-Net: This is an internal error that indicates an invalid state for disconnecting a session from the Net Agent.CT-Net: This is an internal error that indicates an invalid state for disconnecting a session from the Net Agent.Reserved.CT-Net HDLC Media: No dial connection.CT-Net HDLC Media: Phone not on hook.B-NET, BNetII, CT-Net HDLC Media: Modem answer only. The call out is rejected because the modem has been configured for Answer Only,  and so cannot originate calls.B-NET, BNetII, CT-Net HDLC Media: Invalid number lines. More than four lines were specified for the Number of Lines parameters when installing the HDLC Media Service.CT-Net HDLC Media: H@  ISL media service is being installed, and the specified number of switched VCs plus permanent VCs is invalid (greater than 40).B-NET, BNetII, CT-Net X.25 Media: Invalid user buffer size.B-NET, BNetII, CT-Net X.25 Media: Total user buffer size too large. The X25NISL media service is being installed, and the memory requirements are too large. Reduce the numl ber of VCs.B-NET, BNetII, CT-Net X.25 Media: Total X.25 buffer size too large. The X25NISL media service is being installed, and the memory requirements are too large. Reduce the number of VCs.B-NET, BNetII, CT-Net X.25 Media: Invalid X.25 buffer size. The X25NISL media service is being installed, and the specified X.25 Buffer Size parameter is invalid. Valid values are 128, 256, 512, and 1024.Reserved.B-NET, BNetII, CT-Net X.25 Media: Transmit data from Transport Service too large. Internal errox r.B-NET, BNetII, CT-Net X.25 Media: No VCBs available. An attempt is being made to establish an X.25 VC, but the X25NISL mDLC XID exchange failed.B-NET, BNetII, CT-Net HDLC Media: Invalid baud rate. An attempt has been made to configure the HDLC media as HDLCL with a baud rate other than 300, 1200, 2400, 4800 or 9600.B-NET, BNetII, CT-Net HDLC Media: Invalid modem type.  An attempt has been made to config$ ure the HDLC media as HDLCD, but the modem type specified is not R, 1200PA, 2400PA, or (in B-NET) B.B-NET, BNetII, CT-Net HDLC Media: Invalid modem mode. An attempt has been made to configure the HDLC media as HDLCD, but the modem mode specified is not A, O, or B.B-NET, BNetII, CT-Net HDLC Media: Invalid dial type. An attempt has been made to configure the HDLC media as HDLCD, but the dialing type specified is not T or P.B-NET, BNetII, CT-Net HDLC Media: Receive buffer overrun. Internal error.B-NET0 , BNetII, CT-Net HDLC Media: Received character overrun. Internal error.B-NET, BNetII, CT-Net HDLC Media: Lost Clear To Send. Internal error.B-NET, BNetII, CT-Net HDLC Media: Lost carrier.  Internal error.B-NET, BNetII, CT-Net HDLC Media: Bad CRC. Internal error.B-NET, BNetII, CT-Net HDLC Media: Receive buffer wrap around. Internal error.B-NET, BNetII, CT-Net HDLC Media: Receive buffer not available. Internal error.B-NET, BNetII, CT-Net HDLC Media: Asynch received character. Internal err< or.B-NET, BNetII, CT-Net HDLC Media: Asynch receive spec interrupt. Internal error.B-NET, BNetII, CT-Net HDLC Media: Busy bit IO modem. Internal error.B-NET, BNetII, CT-Net HDLC Media: Busy bit IO. Internal error.B-NET, BNetII, CT-Net HDLC Media: Invalid user buffer size. An invalid value has been entered for the User Buffer Size parameter when installing the HDLC media service.B-NET, BNetII, CT-Net HDLC Media: Total buffer size too big. When installing the HDLC media service, the memory requH irements exceed the size of the data segment. Reduce the number of lines.B-NET, BNetII, CT-Net HDLC Media: Buffer too large to send. Internal error.CT-Net HDLC Media: Invalid window size.CT-Net HDLC Media: Invalid timeout.CT-Net HDLC Media: Invalid entry for retries.CT-Net HDLC Media: Invalid Receiver Not Ready (RNR) threshhold.B-NET, BNetII, CT-Net HDLC Media: Transmit data from Transport Service too big.B-NET, BNetII, CT-Net HDLC Media: Modem currently not ready. Modem in use by another conneT ction, or currently being reset.B-NET, BNetII, CT-Net HDLC Media: Receiver Not Ready (RNR) error. Internal error.CT-Net HDLC Media: Error in Setup Frame Reject state.B-NET, BNetII, CT-Net HDLC Media: Invalid dial timeout. An attempt has been made to configure the HDLC media as HDLCD, but the dialing timeout specified is invalid. The valid range is 10 to 99.B-NET, BNetII, CT-Net HDLC Media: Invalid modem clocking. An attempt has been made to configure the HDLC media as HDLCL with a clocking parame` ter other than i or e.CT-Net HDLC Media: Using a duplicate install number.Reserved.B-NET, BNetII, CT-Net X.25 Media: Invalid number VCs. The X25NA edia service cannot support any more SVCs. When installing X25NISL, try increasing the Number of Switched VCs and/or Number of Permanent VCs parameters.B-NET, BNetII, CT-Net X.25 Media: Invalid low port. The X25NISL media service is being installed, and the Low Port parameter is out of range (greater than 99).B-NET, BNetII, CT-Net X.25 Media: Invalid high port. The X25NISL medi a service is being installed, and the High Port parameter is out of range (greater than 99).B-NET, BNetII, CT-Net X.25 Media: Invalid number of retries. The X25NISL media service is being installed, and the Number of SVC or PVC Retries parameter is incorrect.CT-Net X.25 Media: X.25 Network Gateway not installed.CT-Net X.25 Media: Net connection failed.SVC already configured. An attempt is being made to configure a second X.25 SVC media.B-NET, BNetII, CT-Net X.25 Media: Invalid SVC call type. The X2 5NISL service is being installed, and the specified Switched VC Call Type is not I, O, or B.B-NET, BNetII, CT-Net X.25 Media: Invalid LCN. When configuring an X.25 PVC media, an invalid logical channel number was specified in the parameters field.CT-Net X.25 Media: No permanent virtual circuit (PVC) available.B-NET, BNetII, CT-Net X.25 Media: No SVC call outs allowed. An attempt is being made to establish an X.25 SVC, but when the X25NISL media service was installed, the Switched VC Call Type paramet er was set to Incoming only.CT-Net X.25 Media: No Switched Virtual Circuit call type.CT-Net X.25 Media: Invalid DTE calling address.CT-Net X.25 Media: Too few buffers or request blocks.B-NET, BNetII, CT-Net X.25 Media: No matching VCB in find. Internal error.B-NET, BNetII, CT-Net X.25 Media: Lost connection request block. Internal error.B-NET, BNetII, CT-Net X.25 Media: Too many X.25 Network Gateway request blocks. An internal resource has overflowed. Reduce the number of VCs.B-NET, BNetII, CT -Net X.25 Media: Too few X.25 buffers. A call has been cleared because of a temporary lack of buffers. This error is logged but does not indicate a fatal condition.B-NET, BNetII, CT-Net X.25 Media: Lost status request block. Internal error indicating a wrong state.CT-Net X.25 Media: This internal error indicates a wrong state, due to the loss of a VCB request block.CT-Net X.25 Media: This internal error indicates an inability to find a matching VCB in Check routine.B-NET, BNetII, CT-Net X.25 Media:  Invalid alive timeout. Internal error indicates an invalid value for the install parameter [PVC Alive Packet Timeout (default = 30 sec.)].B-NET, BNetII, CT-Net X.25 Media: Invalid for a PVC. Internal error. Need to check the X.25 configuration.B-NET, BNetII, CT-Net X.25 Media: Invalid Vch. Internal error. Received a Clear Call request either from the Transport Service or the X.25 Accept call response, and the VC is invalid.B-NET, BNetII, CT-Net X.25 Media: No Transport Service buffer available   If X25NISL runs out of an internal resource, it will post this error code to the log file. Normally this is a recoverable condition, but might require the Transport Service timing out the connection. If the error occurs frequently, you should allocate more VCs in the install parameters, and try to use other methods to limit the X.25 traffic.B-NET, BNetII, CT-Net X.25 Media: No X.25 buffer available Logged by X25NISL media service to indicate that a buffer is not available and that data may have been d iscarded. This is not a fatal condition. Normally this is a recoverable condition, but might require the Transport Service timing out the connection. If the error occurs frequently, you should allocate more VCs in the install parameters, and try to use other methods to limit the X.25 traffic.B-NET, B-Net II: Duplicate SVC In certain cases two SVCs may be established between two nodes. When X25NISL finds this has happened, it shuts down one SVC and routes all traffic over the other. It posts this stat us code to the log file to inA  as been corrupted. The cache i  s no longer valid, and no recovery is possible.SPA RamDisk.run: An internal consistency check has revealed that internal data is no longer valid. No recovery is possible.SPA RamDisk.run: The queuing logic has discovered an internal error. No recovery is possible.SPA RamDisk.run: The system has detected an internal error. The RamDisk.run exchange has incorrectly received a request. No recovery is possible.SPA RamDisk.run: The system has discovered an internal inconsistent state. The most likely caus, e is an SPA version with an expanded table size whose corresponding table in RamDisk.run has not been increased synchronously. No recovery is possible.SPA RamDisk.run: An internal table has overflowed. No recovery is possible.Reserved.SPA Mover.run: Mover.run has failed to install. The reason for the failure appears on the screen.Reserved.Image Designer, OFIS Imager: Bad data was sent to the scanner. Command error. The last command sent to the sdicate the reason the duplicate SVC was shut down. This is not an error condition. It frequently happens during error recovery. CT-Net X.25 Media: An invalid PDN type was entered in the install parameter [PDN type].CT-Net X.25 Media: When configuring the X.25 media, if the X.25 Network Gateway has not been installed, this error results.CT-Net X.25 Media: This internal error indicates an invalid VCB state.Reserved.B-NET, BNetII, CT-Net Asynchronous Media: Invalid number o f lines When installing the asynch media service, more than four lines were specified for the Number of Lines parameter.B-NET, BNetII, CT-Net Asynchronous Media: Invalid baud rate When configuring an asynch line, the baud rate parameter was not valid.CT-Net Asynchronous Media: Invalid stop bits.CT-Net Asynchronous Media: Invalid character bits.CT-Net Asynchronous Media: Invalid parity.B-NET, BNetII, CT-Net Asynchronous Media: Invalid user buffer size When installing the asynch media service, an in valid size was entered for the User Buffer Size parameter.CT-Net Asynchronous Media: Too large a buffer to send.B-NET, BNetII, CT-Net Asynchronous Media: Invalid timeout number When installing the asynch media service, an invalid parameter was entered for the connection timeout parameter.Reserved.CT-Net Ethernet NGEN Media: ID not found. The processor did not recognize the Ethernet module.CT-Net Ethernet NGEN Media: The EDLC reigister "received bit" was not clear.CT-Net Ethernet NGEN Media: The EDLC  register "transmit bit" was not clear.CT-Net Ethernet NGEN Media: Cannot reset the CSR register.CT-Net Ethernet NGEN Media: The General Purpose (GP) register test failed.CT-Net Ethernet NGEN Media: Sixteen consecutive collisions occurred while transmitting.CT-Net Ethernet NGEN Media: Transmit frame too big. The packet size should not be greater than 1514 bytes.CT-Net Ethernet NGEN Media: Total buffer size too big. The total size of the transmit and receive buffer should not be greater than 64 Kb.CT- Net Ethernet NGEN Media: Invalid buffer size. The number entered is not valid.CT-Net Ethernet NGEN Media: Invalid priority. The priority entered is not valid.Invalid install number. The number must be equal to or greater than 1.Must enter an install number. You must enter a numeric number.Reserved.CT-Net Ethernet NGEN Media: Transmit frame too big.CT-Net Ethernet NGEN Media: Total buffer size too big.CT-Net Ethernet NGEN Media: Invalid buffer size.CT-Net Ethernet NGEN Media: Invalid priority.CT-Ne t Ethernet NGEN Media: Invalid slot number specified.CT-Net Ethernet NGEN Media: Invalid install number.CT-Net Ethernet NGEN Media: Must enter an install number.Reserved for future use by the CT-Net Ethernet SRP Media System Service.Reserved for future use by CT-Net.Reserved.SPA RamDisk.run: The RamDisk.run program failed to install. The reason that the installation failed appears on the screen.Reserved.SPA RamDisk.run: An internal record that describes a cached file hB canner was not recognized.Image Designer, OFIS Imager: 8  The scanner did not respond. The scanner failed to respond within a preset time to the last command. Check to see that the scanner is properly connected and configured.Image Designer, OFIS Imager: Error received from the scanner. The scanner returns this error when no other error fits.Image Designer, OFIS Imager: Bad data was sent to the scanner. Format error. The last command sent to the scanner was not in the correct format.Image Designer, OFIS Imager: Bad parameter given to scanner. The last coD mmand sent to the scanner contained illegal parameters.Image Designer, OFIS Imager: Scan box is outside of the scan page. Some or all of the scanning window is outside the scannable page.Image Designer, OFIS Imager: Scanner cannot scale this amount. The scale factor is out of range.OFIS Imager: Scan page size is not within scanner capability. The size of the page you want to scan exceeds the scanner capabilities.Reserved.Image Designer, OFIS Imager: File is not an image (TIFF) file. The file does noP t follow the TIFF format.GPS Imaging: Invalid or unsupported formats encountered in TIFF Raster-Object data. Image Designer, OFIS Imager: The file is not understood by Image Designer (OFIS Imager).Reserved.OFIS Imager: No image to save. There is no image in the Final Work Area to save.OFIS Imager: No preview file to get image from. There is no image in the Preview Work Area.Reserved.Image Designer, OFIS Imager: Operation can't be done with this scanner. This feature is not supported by the scanne\ r defined in the user file.Image Designer, OFIS Imager: Unrecognized scanner type. The scanner listed in the user file is not recognized by Image Designer (OFIS Imager).Image Designer, OFIS Imager: No scanner is hooked up. There is no scanner listed in the user file.Reserved.Image Designer, OFIS Imager: Bad scanner configuration filename in user file. A bad scanner configuration file was given in the user file.Image Designer, OFIS Imager: BLP Server is not installed. A bad scanner configuration fh ile was given in the user file. The BLP Service needs to be installed to communicate with the operating system.Reserved.GPS Imaging: Invalid or unsupported formats encountered in TIFF Raster-Object data. Image Designer, OFIS Imager: Bad compaction Format. Cannot compact this image. The image parameters do not follow the internal algorithm for producing the compacted image.Image Designer, OFIS Imager: Cannot Uncompact Image. Cannot uncompact this file. The compaction algorithm of the TIFF file is not t understood by Image Designer (OFIS Imager). Save the file in uncompressed TIFF format and try again.Image Designer, OFIS Imager: Can't CCITT3 compress this image. Unable to do CCITT3 compaction on this file because it would generate a larger file than if saved uncompressed. TIFF format should be changed in the Set Up Menu to Pack Bits or Uncompressed.Reserved.Image Designer, OFIS Imager: This is not allowed in the Preview area. This operation is not allowed in the Preview Work Area. The operation  is only allowed in the Final work area.Reserved.OFIS Imager: This is not allowed in the Current Work Area. This operation is not allowed in the Preview Work Area. The operation is only allowed in the Final work area.Image Designer, OFIS Imager: Cannot do this outside of the defined box. An attempt was made to perform an illegal operation in Exterior mode. For example, you cannot mirror an image surrounding a defined box.OFIS Imager: Resolution differs: (xx, yy), preview first. You cannot scan  this image directly to the Final Work Area because the output resolution and the image resolution are different. First scan the image to the Preview Work Area then to the Final Work Area or make the output resolution the same as the image resolution.OFIS Imager: This isn't allowed outside of the Final work area. This operation must be performed in the FinaB  ata too big The request received from the Net Agent is too large to fit in the Net Server's buffer. If you installed the Net Agent and/or Net Server via the RUN command, check to make sure you did not specify too many p arameters.B-NET: service (formerly server) unknown iNA response or LAN software failure.B-NET: Invalid LAN node name The configuration file Lan.config does not contain a valid node name. Edit it to correct the node name. (It may erroneously contain embedded spaces, left square brackets, or left angle brackets or may be too long or zero lengthened.) BNet II: Invalid node name The node name entered when the Net Agent/Server was installed is invalid.B-NET: Data segment too large The parameters sp ecified when installing The Net Agent or Net Server require more memory than can be utilized. Try reducing the number of input parameters.B-NET: Too many file handles When installing the Net Agent, the number of remote resources specified exceeded 255. Reduce tl Work Area, it cannot be performed in the Preview Work Area.OFIS Imager: This applies only to Photograph mode. Select Photo mode before trying to ch ange this option. Reserved.NLS: No such Native Language Support (NLS) table signature.NLS: Bad Native Language Support (NLS) table signature.NLS: Not a message file. BNET: No response from the remote node on link level echo function.NLS: Message not found. OFIS Graphics: No Message OFIS Graphics did not find the desired message in the [Sys]ArtChartMsg.bin file. OFIS Imager: Message is not in [Sys]ScanMsg.bin. Invalid message.NLS: Message file not open. B-NET: LAN internal resources  exceeded.NLS: Message file is corrupt.NLS: Bad keycap range. B-NET: A request was made to access a session that was not in use, or a data mismatch on link level echo function occurred.NLS: Bad date table. B-NET: A session was accessed after it had been closed.NLS: Not Yes or No. The subparameter was not a valid Yes or No answer.NLS: Message file could not be opened. The required message files (refer to the release notes for the specific application) are not installed on the workstation.B-NET : The data sent with a connection request, a closed request, or a datagram exceeds the legal maximum.Reserved.B-NET: The LAN software has received an illegal request.Reserved.B-NET: The remote node has aborted the connection.Reserved.B-NET: The remote node has not responded to a connection request, even though it is up. All of the Net Server sessions may be in use.Reserved.B-NET: A duplicate request has been made to either open a connection, or to await a close on it.Reserved.B-NET: The remote node r ejected a connection request, probably due to incompatible options.Reserved.B-NET: The local node rejected a connection attempt due to incompatible options.Reserved.B-NET: An illegal address was specified for a connection attempt or for a datagram.Reserved.B-NET: An error occurred at the network layer.Reserved.B-NET: LAN session closed.B-NET: LAN transport failure. LAN session failure after it was opened successfully. The other node may have gone down, or there may be a lack of continuity in the LA N cable.B-NET: Agent unknown iNA response or LAN software failure.B-NET: Not LAN media.B-NET: No Receive buffer.B-NET: iNA invalid timeout.Reserved.B-NET: Agent no CDB available. The LAN software has exceeded an internal resource. Contact field support to have this resource expanded.Reserved.B-NET: No remote response. There is no response from the Net Server in the remote node, although the LAN software appears to be installed. The Net Server may not be installed, or there may be some other pr oblem with the software running on that node's main processor.B-NET: No LAN node name. The configuration file Lan.config does not contain a node name. Edit it to contain the node name. BNet II: No node name No node name was entered when installing the Agent/Server.B-NET: LAN dC hat parameter.B-NET: Duplicate node name Another node on the LAN has the same node name.BNET: Invalid request block The request block contains too many ReqPbCb pairs for Net to handle, or (BNetII) contains inconsistencies.BNET: Invalid par ameter An input parameter contains a non-numeric character, or exceeds the allowed range, or (B-NET only) has a value of zero. A specific message is displayed indicating the problem.BNetII: Cannot be deinstalled The caller is not able to deinstall BNet. This may be because the deinstallation program is running on a cluster workstation while BNet is running on the server (formerly master).BNetII: Agent No User Number Available The Net Agent has run out of user numbers for local clients. Increas e the Agent Number of Net Users parameter when installing the Agent/Server.BNetII: Invalid Buffer Size The buffer posted with a status request is too small to accomodate the data to be returned.BNetII: Invalid Compression Option If this occurs during installation, then an invalid character was entered for the compression option when installing the Net Agent/Server. If a program which is attempting to turn compression on or off gets this error, it indicates that the request indicated something oth er than on/off.BNetII: Internal Buffer not on list.BNetII: Internal Net Server got a response with a bad address.BNetII: Net Server Congestion The Net Server cannot handle any more requests at present. Try increasing the Number of Large Requests when installing the Net Server.BNetII: Internal The Net Agent received a compressed message of the wrong length.BNetII: Internal Memory management error.BNetII: No Server Session Available The Net Server cannot support any more session  s. When installing the Agent/Server on the remote node, increase the Server Sessions parameter.BNetII: OSI Session Abort The OSI Session has closed the connection.Reserved.BNet II: Internal These status codes indicate a problem with the Session service.BNet II: File Spec too Long The file specification (including default pathing information) exceeds 100 bytes.BNet II: Internal.BNet II: Partial Buffer Received The OSI Session sent BNet an incomplete message. The OSI Transport Service was possib(  ly installed after BNet and the OSI Session.BNet II: Remote Partial Buffer. On the remote node, the OSI Session sent BNet an incomplete message. Possibly the OSI Transport Service was installed after BNet and the OSI Session on that node.Reserved.Reserved.Font Services: Font Service Not Running. Deinstall Font Service command was issued when it was not running.Font Services: Incorrect Version Font Database. Font Service failed to installed because the version of the runtime font database is incompati4  ble with the version of the Font Service. Future releases of the font system will require that you regenerate the runtime font database, using the re-released Font Tool. Verify that you have the correct version of font system software installed, and regenerate the runtime font databse if necessary. The file provided to the Font Service may not be a valid runtime font database.Font Services: Font Database Inconsistency. The Font Service discovered an internal inconsistency in the porcess of serving a re@ quest. If regenerating the font database does not clear up the problem, contact the nearest Customer Support center.Font Services: Font Key Not Found. The Font Service returns this status code when the reduced font key is not found in the font database. Verify that the regeneration of the runtime font does not result in errors (for example, records flagged as invalid). If the problem persists, contact Technical Support.Font Services: Insufficient Font Service Buffer Space. The Font Service returns thL is status code when it does not have sufficient buffer space to service the request. Reinstall the Font Service, specifying a larger amount of buffer space. (The defauC   Context Manager and try again.PMOS: Too little RAM is installed. Add Ram memory expansion cartridges.PMOS: RAM Failure. The memory diagnostic for extended memory, which tests memory from 992 Kb to the high-order end of installed RAM, detected an error. PMOS installation failed.Reserved.PMOS: No more real mode stacks are available. This error occurs when the [Maximum number of protected mode processes] pa rameter is exceeded. Reboot and reinstall PMOS, specifying a larger value. (Note: The size of the real mode PmAgent.run partition will increase.)PMOS: PmAgent DGroup exceeded. This error occurs during installation when the [Maximum number of protected mode processes] parameter is too large. Try again with a smaller value.PMOS: Message buffer area size limit exceeded. This error occurs during installation when the [Maximum number of concurrent protected mode messages] parameter results in more than 6! 4 Kb of message buffers. Try again with a smaller value.PMOS: Mover seglt buffer size is 12K bytes.)Font Services: Insufficient Space to Return Font Information. The Font Service returns this status code when the client of the Font Service calls it with less than minimal space to return the font data.Font Services: Cannot Install. This is returned by the Font Service when it fails to install because the FonX t Service request codes are already being served by some service. Verify that the Font Service has not already been installed.Font Services: Cannot Deinstall. This is returned by the Deinstall Font Service under a single partition operating system.Font Services: Font Data Unavailable. This is returned by the Font Service when the reduced font key does not refer to the type of data requested. For example, this status code is returned if a raster font is requested for a device type for which rasters ared  inapplicable or otherwise unavailable. Examine the returned font key. If the data should be available, check for an error in the editable font database (for example, the raster font is not named in the font key, or the corresponding font file is not present in that path) and regenerate the font database.Font Services: Invalid Font Character Set Id. The Font Service returns this status code when the request parameters contain a character set id which is generally invalid, invalid for the particular requp est (for example, 0 is invalid on requests for the device alias), or invalid for the particular font key (for example, 82 hex when the font key refers to only two character sets).Font Services: No Such Font Device Type. GetFontDeviceList returns this status code when iDevice in the request is greater or equal to the total number of device types.Font Services: No Such Font Family. GetFontFamilyList returns this status code when iFamily in the request is greater or equal to the total number of font famili| es.Font Services: Invalid Font Key. The font key passed on Font Service request is invalid. For example, it may be incorrect size.Font Services: Invalid Font Handle. Handle passed on Font Service request does not match the handle for any item of the type (raster font or translation table) requested.-13999 Reserved.PMOS: This is an internal error that indicates a problem with the software you are using.PMOS: This internal error indicates an unsupported version of CTOS.PMOS: The PMOS service (formerly  server) received a request block containing an unexpected request code. Some other service or client may be malfunctioning.PMOS: This is an internal error that indicates a problem with the software you are using. Contact the Customer Support Center.PMOS: This is an internal error that indicates a problem with the software you are using. Contact the Customer Support Center.PMOS: This is an internal error that indicates a problem with the software you are using. Contact the Customer Support Center.PMO S: Like any service, PMOS cannot be installed after the Context Manager is installed. DeinstallD ment limit exceeded. This error occurs during installation when the [Maximum number of Mover Server segments] parameter exceeds 2048.PMOS: Real mode processor. This CPU supports only real mode; PMOS cannot be installed. Intel 80286 and subsequent processors support protected mode.PMOS: Down-rev CTOS. CTOS Version 9.7 or later, or CTOS II-1.0 or later, is required to install PMOS.PMOS: Single-partition (SP) CTOS. PMOS requires#  multipartition (MP) CTOS.PMOS: PMOS already installed.PMOS: SPA Mover Service (Mover.run) already installed. Install either PMOS or the Mover.run service (formerly server). Never install both.PMOS Resident Debugger inactive. PMOS: An internal error that should never occur. (The PMOS Resident Debugger is not present in released versions of PMOS.)Reserved for future use.PMOS: No mover handle available. This error occurs when the [Maximum number of Mover Server segments] parameter is exceeded. Reboo% t and reinstall PMOS, specifying a larger value.  Note that the maximum value of this parameter is 2048. (Note: The size of the real mode PmAgent.run partition will not increase, but the amount of available upper memory will decrease slightly.)PMOS: Bad Mover address. Unlike the SPA Mover.run service (formerly server) which PMOS replaces, PMOS validates requests to move to or from protected memory. The specified range of bytes must lie entirely within a single mover segment that was previously allcated'  by the client. (That is, the userNum field in the move request must match the userNum in the allocation request.) Move requests may not span mover segments, even when both were allocated to the same userNum.PMOS: Mover address buffer too small. The cbRet field of a mover allocation request is less than 4 bytes long, so PMOS cannot return the 4-byte segment identifier.PMOS: Mover version buffer too small. The cbRet field of a mover version request is less than the required 2-byte size.Reserved.PMOS: ) Out of measure buffers. This error occurs when the [Maximum number of concurrent protected mode messages] parameter is too small. This line of the command form accepts two values (maximum number of small and large messages, respectively). Reboot and reinstall PMOS, specifying a larger value. Note: The size of the real mode PMAgent.run partition will increase. This error may indicate either (a) all message buffers are full, or (b) all large message buffers are full and a large message buffer is requir+ ed. PMOS will use large message buffers for small messages if all small message buffers are full.Reserved.PMOS: Message too large. An invalid request block was encountered. The request block appeared to be larger than 64 bytes long, perhaps because the nReqPbCb and nRespPbCb fields in its header were invalid. If this error is returned from Request, Respond, or ForwardRequest, the protected mode caller provided an invalid request block. If it was returned from Wait, the invalid request block was receiv- ed from a real mode program, or an internal error occurred in PMOS.Reserved.PMOS: Intertask Send. The user is obliged to mark request blocks sent between tasks using Send or PSend with this value in the ercRet field, whenever either sender or receiver (or both) is a protected mode task. This status code does not indicate an error condition.PMOS: Not a request. Set in the ercRet field of dummy request blocks created by PMOS when Send or PSend is used. These request blocks should never be seen by the us0 er, unless Send or PSend is mis-used. See the PMOS documentation for restrictions limiting the use of Send and PSend between different tasks. The other bytes of the dummy request block header contain 0 or 0FFh, except the userNum field which identifies the sending task. This erc does not apply to the PSend done upon exit from a comm ISR, but only to Sends or PSends done explicitly by a protected mode process.PMOS: A fault occurred in an interrupt service routine. This erc is displayed by theD  dresses and back en route.Reserved.PMOS: Not enough memory. This status code occuT> rs when upper memory is full.PMOS: This internal error indicates an invalid heap ID.PMOS: This internal error indicates LSD is already free.Reserved.PMOS: No such run file. This message should not be returned to user programs. It is an internal error indicates a bad run file.PMOS: Bad run file. The run file is invalid. PMOS run files must be version 6 format (use Bind or V6Link, not the Link command.)PMOS: This internal error indicates that the buffer is too small.Reserved.PMOS: No pending task.`@  An internal error occurred while a protected mode program was loading. Specifically, PMOS received an unexpected request from an instance of PmSubAgent.run.PMOS: Invalid default user number in effect for process at ConvertToSys time.Reserved.PMOS: This internal error indicates a Bad process descriptor (the structure used as an argument to CreateProcess).Reserved.PMOS: No free CommLine control str CTOS Crash 2  handler. To prevent a possible system hang, PMOS does not attempt to diagnose the fault in the normal way (by entering the debugger with a message) under these conditions, unless you specifically tell it to.Reserved.PMOS: Global Descriptor Table (GDT) full. This internal error indicates that the Global Descriptor Table (GDT) is full. Rebuild PMOS from source with a larger GDT specified in the PMake step.PMOS: Local Descriptor Table (LDT) full. This may indicate a user programming error, such as the a4 llocation of an unusually large number of very small memory segments, or an internal error in PMOS. PMOS 1.1 and PMOS 2.1 do not support automatic expansion of a client program's LDT when it overflows.PMOS: Invalid selector. An invalid selector was used in an operating system call, such as a memory deallocation request or SetSegmentAccess. More frequently, use of an invalid selector results in a general protection fault. Since selectors become invalid when the objects they point to are deallocated, an $6 attempt may have been made to free the same memory twice, for example. Alternatively, the selector may identify a non-segment descriptor, a segment descriptor which is not accessible at the user's level of privilege, or a global (GDT) descriptor belonging to PMOS.PMOS: Invalid bAccess Operand. The "bAccess"operand to SetSegmentAccess is not one of the following: 0, 2, 8, or 10 (decimal).PMOS: Expand-down segment illegal. SetSegmentAccess may not be used to convert an expand-down data segment to a cod08 e segment. Only expand-up data segments may be converted to code segments.Reserved.PMOS: Invalid qb (size) parameter. This erc would not normally be returned to a user program that called a CTOS interface, and indicates an internal PMOS error.PMOS: Nonsegment selector. The selector specified for this operation was expected to identify a segment descriptor, but it does not. It may identify some other form of descriptor, such as a call gate. This status code is similar to 14122.Reserved.PMOS: No such <: virtual segment. This status code is similar to 14122.PMOS: Not paragraph-aligned. An attempt was made to pass a protected mode pointer or selector in a request, system common procedure, or Kernel call that is not translatable to a real mode address because it refers to a segment that is not paragraph aligned. See code 14145.PMOS: Not accessible from real mode. An attempt was made to pass a protected mode pointer or selector in a request, system common procedure, or Kernel call that is not translateabH< le to a real mode address because it refers to to segment that is not in real mode memory (address range 0 to 992 KB). The usual cause of this error is passing a pointer to data contained in a code segment. That is not permitted in protected mode because code segments reside in upper memory. Note that even when the recipient of the request is another protected mode program, pb/cb pointers must be translated to real mode adE ucture available. Internal error. This should never occur, since PMOS is built with enough of such controlB l structures for ten (10) serial ports, the maximum possible on a workstation (with two XC-002 Port Expander modules in place).Reserved.PMOS: Bad structCode operand to GetPStructure. This value of the structCode parameter is not supported. See your Procedural Interface Reference Manual for a list of supported codes.PMOS: Bad structCode operand to SetPStructure. This value of the structCode parameter is not supported. See your Procedural Interface Reference Manual for a list of supported codes.PMOS: BxD ad SetPStructure field offset. This field is not supported. See your Procedural Interface Reference Manual for a list of supported fields.Reserved.PMOS: Count of bytes operand (cb) too large for SetPStructure. The operand exceeds the maximum allowable size for this field, which is a sbString (a string preceded by a length byte). When setting such fields with SetPStructure, the pb and cb operands should not include the length byte. Instead, the length byte will be set to the value of cb automaticallyF  .PMOS: Unexpected count of bytes operand (cb) for SetPStructure. For a fixed length field, the operand's value did not exactly match the size of this field.PMOS: The task attempted to perform the GetPStructure operation for too many different data structures. PMOS 1.1 and 2.1 have a limit of 64 distinct operating system data structures that a task may know about. Note that you may call GetPStructure as many times as needed for the same operating system data structure without producing this error.ReH  served.ASCII String Manager: Invalid decimal integer. An explanatory message, rather than any of these error codes, should be issued by PmAgent if the command form is incorrectly filled in. The operator should not normally see these ercs.ASCII String Manager: Overflow. A decimal integer exceeds DWORD precision. An explanatory message, rather than any of these error codes, should be issued by PmAgent if the command form is incorrectly filled in. The operator should not normally see these ercs.ASCII StJ  ring Manager: Null string. This status code does not necessarily indicate an error. It may indicate a missing parameter. An explanatory message, rather than any of these error codes, should be issued by PmAgent if the command form is incorrectly filled in. The operator should not normally see these ercs.ASCII String Manager: Neither Yes nor No. An invalid Yes or No string. An explanatory message, rather than any of these error codes, should be issued by PmAgent if the command form is incorrectly filL  led in. The operator should not normally see these ercs.ASCII String Manager: Hex result field too small. A procedure that returns a hexadecimal ASCII string requires a larger sStringMax parameter. The result string was truncated on the right. An explanatory message, rather than any of these error codes, should be issued by PmAgent if the command form is incorrectly filled in. The operator should not normally see these ercs.Reserved.Reserved.Math Service: Numeric exception occurred. A numeric exceN  ption may be an overflow, an underflow, a zero divide, an inexact result, or an invalid operation. The specific type of exception is determined by examining certain floating-point status bits. Math service (formerly server) or math co-processor exception. A floating point operation failed due to an illegal operand.Reserved.Device Driver: Incorrect parameter information was entered in the device setup section of the Install Device form. Check for spelling errors and make sure there are no spaces beforP e or after the colon terminating a parameter identifier. Imagen driver: A document specifies more fonts than can be output by the driver. This code indicates an overflow in the actual device driver; no code is displayed when a printer overflows its memory.Device Driver: The polygon that was being printedE  t indicates a problem with the software. Contact the nearest Customer Support center.Device Driver: An invalid "font handle" was present in a call to DdFntHandles within the GPS Device Driver. This is an internal error that indicates a problem with the software. Contact _ the nearest Customer Support center.Device Driver: The recipient data structure specified in a call to DdFntKey within the GPS Device Driver was too short. This is an internal error that indicates a problem with the software. Contact the nearest Customer Support center.Reserved.Device Driver: An invalid "font handle" was present in a call to DdGetAlias within the GPS Device Driver. This is an internal error that indicates a problem with the software. Contact the nearest Customer Support center.Device  a Driver: Applies to overlaid device drivers only. The "swapping zone" with which the driver was installed is too small to support printing, vector object processing, or raster object processing. Reinstall the de was too complex for the program to process. To correct the problem, break the polygon up into several smaller polygons. Imagen driver: The Font Database encountered an erroneous second-level translatR ion value. Verify this driver has a valid "Font Device Type" string. Use the Font Tool to correct the translation data in the Font Database. APDMatrix drivers: An invalid character set specification was given on the device setup line.Device Driver: The polygon that was being printed has too many points specified. To correct the problem, break the polygon up into several smaller polygons. APDMatrix drivers: An invalid ribbon specification was given on the device setup line.Device Driver: This is an T internal error. Consult Customer Support. (GPS releases prior to 2.0.) Imagen driver: A document requires more Imagen-printer "Families" than can be used at one time. Reduce the number of fonts in the document. APDMatrix drivers: A page width greater than the capabilities of the printer was specified.Device Driver: The Pen specification supplied to the HPPlotter device driver on the Device Setup line of the Install Device form is incorrect. Verify the correctness of the information and reinstall thV e driver. Imagen driver: A document requires more Imagen-printer "Maps" than can be used at one time. Reduce the number of fonts in the document. APDMatrix drivers: A page length greater than the capabilities of the printer was specified.Device Driver (GPS releases prior to 2.0): The Characters per Line entry in the Install Device form implies a page width too large for the dot matrix printer being used. APDMatrix drivers: The Characters Per Line specified is too large for the page width given.APDMaX trix drivers: The polygon that was being printed has too many points specified. To correct the problem, break the polygon up into several smaller polygons.APDMatrix drivers: The polygon that was being printed was too complex for the program to process. To correct the problem, break the polygon up into several smaller polygons.Device Driver: Internal error. Contact Unisys Support Representative.Device Driver: Internal error. Contact Unisys Support Representative.Reserved.Device Driver: The Font DeviceZ  Type specified by the GPS device driver does not exist in the font database. All GPS device drivers have a default Font Device Type. You can specify another during installation; but, each installed device driver must have access to an installed font database containing data designed for that driver.Device Driver: Not enough heap space to store string. This is an internal error that indicates a problem with the software. Contact the nearest Customer Support center.Device Driver: The GPS Device Driver ] has detected a bad "font handle." This is an internal error that indicates a problem with the software. Contact the nearest Customer Support center.Reserved.Device Driver: Unable to find or store string. This is an internal error thaF vice driver using the default "swapping zone" size, or specify a larger one on the Device Setup field of Print Manager's driver installation form.Device Driver: An invalid "font handle" was present in a call to DdGetChSet within the GPS Device Driver. This is an internal error that indicates a pr,c oblem with the software. Contact the nearest Customer Support center.Reserved.Device Driver: The recipient data structure specified in a call to DdChXlate within the GPS Device Driver was too short.  This is an internal error that indicates a problem with the software. Contact the nearest Customer Support center.Device Driver: Out of memory for font tables. To print the document, reinstall the device driver and specify a larger amount under "Storage Allocation, font Data Table Size."Device Driver: Ins8e ufficient "Font Data Table" space was allocated when installing the driver. The default value is 4 kilobytes. The minimum allowed by most device drivers is 2 kilobytes.Reserved.Device Driver: There is not enough memory within the device driver to store the font definitions required by this document. Additional memory may be allocated within the device driver by reinstalling it with a larger number in the Font Data Table Size field of Print Manager's device driver installation form.Reserved.Device DriverDg : An invalid "font handle" was present in a call to DdChWidth within the GPS Device Driver. This is an internal error that indicates a problem with the software. Contact the nearest Customer Support center.Device Driver: An invalid "font handle" was present in a call to DdFntKey within the GPS Device Driver. This is an internal error that indicates a problem with the software. Contact the nearest Customer Support center. (GPS release 2.0.)Device Driver: Error allocating memory from the Font/GraphicsPi  Work Area. This is an internal error that indicates a problem with the software. Contact the nearest Customer Support center.Device Driver: Unable to retrieve string. This is an internal error that indicates a problem with the software. Contact the nearest Customer Support center.Device Driver: Error encountered while initializing the device driver's memory-heap manager. May be caused by entering a number greater than 64 in the Font Data Table Size field of Print Manager's driver installation form\k . Otherwise, an internal error that indicates a problem with the software. Contact the nearest Customer Support center.Device Driver: This is an internal error that indicates the device driver's memory heap has been corrupted. Contact the nearest Customer Support center.Reserved.Device Driver: An invalid "font handle" was present in a call to DdChXlate within the GPS Device Driver. This is an internal error that indicates a problem with the software. Contact the nearest Customer Support center.Devicehm  Driver: Device driver is unable to scale a raster image.Reserved.Device Driver: Cannot install system services when Context Manager is running. Deinstall Context Manager then install GPS Services.Device Driver: Error encountered while chaining to GPS Service run file by GpsInstall.Reserved.Device Driver: An invalid "Page-Portrait String" was specified in the Device Setup field of the installation form. Page-Portrait strings must contain only hexadecimal digits, are limited to 20-digit length, and mto ust contain an even number of digits.Device Driver: An invalid "Page-Landscape String" was specified in the Device Setup field of the installation form. Page-landscape strings must contain only hexadecimal digits, are limited to 20-digit length, and must contain an even number of digits.Device Driver: An invalid "Reset String" was specified in the Device Setup field of the installation form. Reset strings must contain only hexadecimal digits and must contain an even number of digits.Device Driver: Erroq r encountered determining page orientation during installation. Check Device Setup parameters in Print Manager. ThiF  &R printer FSA Finesse cannot access the V&R printer. Verify that: - the printer is connected and powered on - the cover is closed - no other device is active on the specified port.FSA Finesse: InsertFSA Finesse: Unsuccessful insert, try again A document was not inserted correctly in the AMP printer. Verify that the: - document was inserted properly - inserted document has the correct width as defined in the Form Definition File - document detector  %on the printer is working properly.FSA Finesse: Turn page, insertFSA Finesse: PrintingFSA Finesse: RemoveFSA Finesse: Press CANCEL key This message is displayed when waiting for the AMP or V&R printer. Unless the CANCEL key is pressed, the system continues to wait for the printer.FSA Finesse: Press STATION keyFSA Finesse: Invalid line number, try againFSA Finesse: Press COPY for journal, RETURN or NEXT for formFSA Finesse: Press COPY for ticket, RETURN or NEXT for formFSA Finesse: Press NEXTFSA F &inesse: STOP key pres is an internal error that indicates a problem with the software. Contact the nearest Customer Support center.Device Driver: The GPS loadable request codes have not been installed. The system must be rebooted after installing the GPS 2.0 loadable request file.Device Driver: The version of the installation parameter data and the GPS Device Driver are incompatible. Verify that the GPS 2.0s  Installer (GpsInstall.run) is being used. Consider deleting the existing .state and .config files for the affected device before repeating the installation process.Reserved.PC Emulator: An inconsistent state has been discovered in the PC Emulator software. FSA Finesse: After entering data, press GO to store dataPC Emulator: A fatal error, such as an illegal opcode, has occurred in the PC software being executed. This may be due to an error in the PC program or an error in the PC Emulator software. Fu  SA Finesse: Press the NEXT PAGE key to display the rate screen.PC Emulator: The PC service (formerly server) version does not match the PC Emulator version. FSA Finesse: Press GO to confirm or CANCEL to deny.PC Emulator: Bad color value specified in the PC Emulator configuration file. Color values must be between 0 and 63. FSA Finesse: Press CANCEL to clear, F9 to transfer, or FINISH to exit.PC Emulator: Too many colors specified in the PC Emulator configuration file. A maximum of eight different w !colors may appear on a color monitor at one time.PC Emulator: Hardware and/or system software required to run the PC Emulator is not present on this workstation. The PC Emulator requires either a PC Emulator module or an 80386-based processor module running BTOSII or CTOS/VM operating system.PC Emulator: Only one PC Emulator session is possible when using a PC Emulator module. Only one PC Emulator session is possible when using a PC Emulator module. You can have more than one session only when the Py "C Emulator is used directly on an 80386-based processor module.Reserved.FSA Finesse: Invalid value for categoryReserved.FSA Finesse: Clear screen firstReserved.PC Emulator: ClusterShare in Use. This status code is returned when an attempt is made to deinstall the ClusterShare service while it is in use. This means that either a PC or a PC Emulator has files open through ClusterShare at the time the Deinstall request is received.Reserved.FSA Finesse: Press NEXT PAGE, PREV PAGE, CANCEL, or FINISHFSA Fin{ #esse: Beginning year must not be later than ending yearFSA Finesse: Value cannot exceed 30 yearsFSA Finesse: Loading Customer Service files ...FSA Finesse: Teller level too low for access to AdminFSA Finesse: Partial word processor record written for InterviewsReserved for future use.FSA Finesse: Waiting for AMP printer FSA Finesse cannot access the AMP printer. Verify that: - the printer is connected and powered on - the printer is online - the cover is closed - no other device is active on t} $he specified port.FSA Finesse: Waiting for VG ssed on the AMP, document cancelledFSA Finesse: Module out of paper; Replace or press 'FINISH' to abortFSA Finesse: (This message consists of 80 spaces.)FSA Finesse: Transport jamFSA Finesse: Load paperFSA Finesse: End of document detectedFSA Finesse: Remove document after printing is done.FSA Finesse: Cover open; Replace or press CANCEL keyFSA Finesse: Cover closedFSA Finesse: Station manually deactivatedFSA Finesse: Cancel key pressed, Current document cancelledFSA Finesse:  ' AMP time outFSA Finesse: Invalid device config file FSA Finesse has received one of the following messages from the BTOS Device Server: - 2344: Bad Configuration - 50002: Device Not Found - 50003: Device Bad Type - 50010: Bad Device Spec - 50011: Device Already Declared - 50012: Bad Port Specification Verify that the Device Name is the same in the Device Configuration File and related files as in the Station Parameters File.FSA Finesse: An AMP module is not present or has an error condition Th (is message is displayed when attempting to access an AMP printer and the module is unavailable. The printing is rerouted to another module. The AMP modules include: - ticket dispenser - journal - keyboard/display - forms handler.FSA Finesse: Customizing error, Form ID - (nnn) This message is displayed when one of the following conditions has occurred: - host data was not referenced correctly for the form definition indicated - a passbook transaction was performed, but the form definition does not  )specify the AMP printer. FSA Finesse received one of the following messages from the printer: V&R - 3C: syntax error AMP - 50103: invalid command - 50104: command not allowed now - 50105: invalid parameters - 50106: too many parameters - 50107: syntax error - 50108: invalid font - 50109: invalid version - 50110: horizontal parameter out of range - 50111: vertical parameter out of range Verify the specifications and use of printer attributes in the Form Definition File.FSA Finesse: AMP not  *active The printer has been deactivated, either manually through the local routines or programmatically because of an error. Check the printer and repair, if necessary.FSA Finesse: V&R not active The printer has been deactivated, either manually through the local routines or programmatically because of an error. Check the printer and repair, if necessary.FSA Finesse: Fatal error, printing discontinued One of the following conditions may have occurred: V&R - 34: transport jam - 39: printer failur +e AMP - 50130 to 50143: internal and confidence test routine errorsFSA Finesse: Device server not available During system sign-on, the Device Server system service was not successfully installed. Use the FSA Finesse Executive to access the operating system Executive. Determine and correct any error conditions that occurred, then perform system sign-on again.FSA Finesse: Screen/keyboard error - (nnnnn) FSA Finesse received an error from the Screen and Keyboard Module while attempting to retrieve th( ,e optional line number. Note the number and contact your data processing department or Unisys representative.FSA Finesse: AMP keyboard error, try againFSA Finesse: Communication error, printing discontinued A communications error between your workstation and a printer was encountered. A reentry was unsuccessful, printing was terminated, and the printer was deactivated. Contact your Unisys representative.FSA Finesse: Spooler queue error - (nnnnn) An error was encountered in an attempt to send informa4 -tion to the Spooler Utility. Refer to the relevant section of this status codes manual for a description of the status code displayed in parentheses.FSA Finesse: Printing discontinued, unexpected system error - (nnnnn) An unexpected system error was encountered during an attempt to communicate with a printer. Refer to the relevant section of this status codes manual for a description of the status code displayed in parentheses.FSA Finesse: G  d 16402.)FSA Finesse: printing on same printer or GO to reroute to backup printer (Message consists of two lines, 16401 and 16402.)FS 4A Finesse: Protected file name Restart the program. Do not use the file name (sys)Menu for the screen file ID.FSA Finesse: Video specified not allowed Change the output device name to a printer or a file name.FSA Finesse: Service not available Exit Screen Designer Program, install the Spooler Utility, and execute Screen Designer again.FSA Finesse: SKM menu file not found Install the following Screen Designer menu files in the directory: - Menu.Skm.Rec - Menu.Skm.KeyFSA Finesse: Paging Allo 5wedFSA Finesse: Scrolling and Paging AllowedFSA Finesse: Error; Press CANCEL to ContinueFSA Finesse: Invalid frame index Enter a valid frame index.FSA Finesse: Invalid frame parameter Enter a valid frame parameter.FSA Finesse: Frame not defined Define the new frame or verify the existing frame ID.FSA Finesse: Invalid buffer size The entry nuDevice Sharing Error FSA Finesse has received one of the follo@ .wing messages from the Device Sharer: - 50030: No sharing of the processor - 50031: Max number of shareable devices is greater than three of the client agents - 50032: Client agent not installed - 50200: Server went down - 50201: Overflow on outstanding request table - 50202: Overflow on shareable devices table - 50203: Internal data buffer too smallFSA Finesse: Device Server/Sharer error - (nnnnn)FSA Finesse: AMP Forms Handler not available The Form module is not present or has an error coL /ndition. If the module is not present, the error condition can be ignored. If the module is present, try the print operation again. If you still receive the error message, contact your supervisor.FSA Finesse: AMP Ticket Dispenser not available The ticket module is not present or has an error condition. If the module is not present, the error condition can be ignored. If the module is present, try the print operation again. If you still receive the error message, contact your supervisor.FSA Finesse: X 0 AMP Journal Module not available The journal module is not present or has an error condition. If the module is not present, the error condition can be ignored. If the module is present, try the print operation again. If you still receive the error message, contact your supervisor.FSA Finesse: AMP time out; Press Cancel to Cancel document, Finish to Abort.FSA Finesse: AMP Printer aborted All printing for current transaction is cancelled. Perform transaction again if printing is required.FSA Finesse:d 1 Unable to access StoreBuffer.Dat file Exit to FSA Finesse Executive and reload Customer Service/Teller Module.FSA Finesse: Waiting for MCR; press CANCELFSA Finesse: Waiting for PIN keypad; press CANCELFSA Finesse: Waiting for OCR reader; press CANCELFSA Finesse: Pass card through MCREnter PIN and pressFSA Finesse: Pass MICR document through OCR readerFSA Finesse: Unable to retrieve account numberFSA Finesse: MCR read error; CANCEL to quit; NEXT to retryFSA Finesse: PIN read/device error: press CAp 2NCEL to quit; NEXT to retry A physical device problem exists or a read error has occurred.FSA Finesse: OCR read/device error; press CANCEL to quit; NEXT to retry A physical device problem exists or a read error has occurred.FSA Finesse: Valid OCR data receivedFSA Finesse: OCR field format errorFSA Finesse: MCR not activeFSA Finesse: PIN not activeFSA Finesse: OCR not activeFSA Finesse: PIN validation unsuccessful; press CANCEL to quit, NEXT to retryFSA Finesse: MCR customizing error The MCR field| 3 layout record of the MCR/OCR File was customized incorrectly. Verify the accuracy of that file.FSA Finesse: MCR device error; press CANCEL A physical device problem exists because the MCR is not connected to your workstation or is configured incorrectly.FSA Finesse: Unable to print, Press CANCEL to cancel printing, NEXT to retry (Message consists of two lines, 16401 anH mber is not in the permitted range. Enter a buffer size in the range of 1 to 64.FSA Finesse: Buffer size exceededFSA Finesse: Invalid text areaFSA Finesse:  6 Invalid screen IDFSA Finesse: Screen not found Contact your Unisys representative.FSA Finesse: Invalid WildCard specified Reenter the wild card specification. Make sure the asterisk (*) is the last character in the string.FSA Finesse: Invalid help ID Internal error. Contact your Unisys representative.FSA Finesse: Help ID not found Customizing error. Contact your Unisys representative.FSA Finesse: Invalid screen handle Internal error. Contact your Unisys representative.FSA Finesse: Screen han 7dle not active Internal error. Contact your Unisys representative.FSA Finesse: Saved screen found Internal error. Contact your Unisys representative.FSA Finesse: Multi-page screen active Only one multipage screen can be active at any time.FSA Finesse: Invalid page number Internal error. Contact your Unisys representative.FSA Finesse: Frame height inadequate Increase the frame height specification to more than one line before defining a multiple-page screen.FSA Finesse: Host display screen was n 8ot retrievedFSA Finesse: Invalid selection Extend the selected area to include the entire field, or begin again.FSA Finesse: Destination width out of frame size Press the CANCEL key and change the destination to accommodate the frame width.FSA Finesse: Destination height inadequate Press the CANCEL key and change the destination to accommodate the height of the selected area.FSA Finesse: Selection not single line When adding a field, make the selected area a single line.-17399 Reserved.FSA Finesse: Ĩ 9 Invalid data typeFSA Finesse: Data too large for fieldFSA Finesse: Field count exceeded Only 200 fields are allowed per screen. To add a field, you must delete an existing field.FSA Finesse: Field not found Select an area on the Design Screen where a field is definedFSA Finesse: Invalid field number Internal error. Contact your Unisys representative.FSA Finesse: Cannot break up field Reenter field data. Do not try to split a field when manipulating a selected area of the Design Screen.FSA FinesЪ :se: CheckField in session Used for internal flow control within SKM.FSA Finesse: Invalid exit key Used for internal flow control within SKM.FSA Finesse: Invalid time field The field selected is a time field. Read and write operations are not allowed.FSA Finesse: Invalid edit parameter Press the CANCEL key to cancel the message and reenter the data. Use the allowable data indicated on the input screen.FSA Finesse: Invalid field data Press the CANCEL key to cancel the message and reenter the data.ܬ ; Use the allowable data indicated on the input screen.FSA Finesse: CheckField not in session Internal error. Contact your Unisys representative.-17499 Reserved.FSA Finesse: Invalid key code Used for internal flow control within SKM.FSA Finesse: Not enough memory available Used for internal flow control within SKM.FSA Finesse: Null string Used for internal flow control within SKM.FSA Finesse: Blank string Used for internal flow control within SKM.FSA Finesse: Invalid string Internal error. Con <tact your Unisys representative.FSA Finesse: Invalid number of screens This error occurs in the Test Drive routine. The maximum number of screens that can be entered is five. Reenter the number of screens.-17599 Reserved.FSA Finesse: Main menu Used for internal flow control within SKM.FSA Finesse: Delete Used for internal flow control within SKM.FSA Finesse: Duplicate Used for internal flow control within SKM.FSA Finesse: Cancel Used for internal flow control within SKM.FSA Finesse: Screen desi =gn Used for internal flow control within SKM.FSA Finesse: Finish Used for internal flow control within SKM.FSA Finesse: Exit Used for internal flow control within SKM.FSA Finesse: Screen exists To duplicate an existing screen, enter a unique screen IH  quired field on Page 3.FSA Finesse: Required field on Page 4.FSA Finesse: Required field on Page 5.FSA Finesse: Division by zero is not valid The multiple for loose amounts in the Denom/Settle file is zero or the multiple for rolled/strapped amounts in the System Parameters File is zeros.FSA Finesse: Error during EJ builH Dd - EJ not built FSA Finesse was unable to create the electronic journal record for the current transaction. The electronic journal file at the branch processor will not contain a record for this transaction.FSA Finesse: Processing ...FSA Finesse: Transaction not allowed. Too many fields. The number of fields in the current transaction exceeds the maximum number of fields allowed for a transaction. The maximum number of fields is user-defined in the System Parameters File. Refer to the BTOS FSA FineT Esse Installation Utilities Operations Guide for the procedure.FSA Finesse: Unknown Erc from MFIFDIFSA Finesse: Customer Service not available for this workstatD for the duplicate screen.FSA Finesse: Field within selection Used for internal flow control within SKM.-17699 Reserved.FSA Finesse: Unable to secure LRU memory. All the memory in the pool has been allocated. This is a Fatal Error: All programs ter >minate. Increase the size of the LRU memory pool.FSA Finesse: Maximum record limit reached. No slot exists in the Record Table for the new record. The slots are already taken up for in-use and saved records. This is a Fatal Error: All programs terminate. Increase the size of the LRU memory pool.FSA Finesse: Available memory inadequate. Not enough memory is available for initial allocation of record pool. This is a Fatal Error: All programs terminate.FSA Finesse: Reserved for LRU buffer man  ?agement routines. Contact your Unisys representative.FSA Finesse: SKM Font Service ErrorFSA Finesse: Reserved for SKM Font Service Procedure routines.-17999 Reserved.FSA Finesse: Special Routines Module (SRM) ErrorFSA Finesse: Invalid monthFSA Finesse: Invalid dayFSA Finesse: Invalid yearFSA Finesse: Invalid edit codeFSA Finesse: Invalid input for editFSA Finesse: Invalid hourFSA Finesse: Invalid minuteFSA Finesse: Invalid secondFSA Finesse: Invalid AM/PMFSA Finesse: Invalid data lengthFSA Fin @esse: Invalid field sizeFSA Finesse: Invalid currency code for SRM EditingFSA Finesse: Maximum currency size exceeded.-18250 Reserved.FSA Finesse: Invalid check digit position (CDV)FSA Finesse: Invalid input dataFSA Finesse: Invalid check digit (CDV)FSA Finesse: Invalid type specified-18500 Reserved.FSA Finesse: Input data out of rangeFSA Finesse: Length of data out of range-18750 Reserved.FSA Finesse: Invalid valueFSA Finesse: Invalid multiple of denominationFSA Finesse: Invalid data lengthFSA $ AFinesse: Invalid Tran IDFSA Finesse: Transaction not allowed offlineFSA Finesse: Supervisor password requiredFSA Finesse: Screen for transaction does not existFSA Finesse: Please press GO to transmitFSA Finesse: Transaction selection not possible for this documentFSA Finesse: Teller level not valid for transaction accessFSA Finesse: Input needed for required fieldFSA Finesse: Tran not allowed in Multi Cash Check modeFSA Finesse: Tran not allowed in Tran Audit modeFSA Finesse: Multi Cash key not a0 Bllowed in Tran Audit modeFSA Finesse: Tran Audit key not allowed in Multi Cash Check modeFSA Finesse: Additional funds required Press the TRAN AUDIT (F2) key to display the collection screen and enter more funds.FSA Finesse: Press CANCEL, or GO to continueFSA Finesse: Transaction out of balanceFSA Finesse: Amount greater than maximum lengthFSA Finesse: Teller transaction limit exceeded; supervisor override requiredFSA Finesse: Supervisor transaction limit exceededFSA Finesse: Field value out of ran< CgeFSA Finesse: Field value not correct multipleFSA Finesse: Not a multi-paged transactionFSA Finesse: Required field on Page 1.FSA Finesse: Required field on Page 2.FSA Finesse: ReI ion.FSA Finesse: Press GO to confirm reentry, CANCEL for next date (Message consists of two lines, 19035 and 19036.)FSA Finesse: or CODE-GO to reenter all dates. (Message consists of two lines, 19035 and 19036.)FSA Finesse: No Dates available for Auto Reentry.FSA Finesse: Field definition does not exist An attempt was made to process the curr` Fent field but the field definition for this field does not exist on disk. Verify the Transaction and Field Definition files.FSA Finesse: Error detected during field handling An error was detected during output of the current field. Verify all custom files associated with fields. If you cannot solve the problem with the custom files, contact your Unisys representative.FSA Finesse: Access error on previous field FSA Finesse is unable to process the previous field on the screen. Verify all custom filesl G associated with screen fields.FSA Finesse: Exchange Rate record not in memoryFSA Finesse: Currency code does not exist in Exchange Rate FileFSA Finesse: Error in reading Exchange Rate file.Reserved.FSA Finesse: Unable to allocate memory The system is not able to allocate needed memory. Do not continue processing. Notify your supervisor. A memory allocation problem has occurred within the Heap Management Module while processing the response from the host. The current transaction will not terminate x Hnormally, and processing will return to the teller idle state. Contact your Unisys representative.FSA Finesse: Unable to deallocate memory The system is not able to deallocate the required portion of memory. Complete the current transaction, but do not continue processing. Notify your supervisor. A memory deallocation problem has occurred within the Heap Management Module. Contact your Unisys representative.FSA Finesse: Customer already in sessionFSA Finesse: Initialize new customer sessionFSA Fine Isse: Deallocation error. Contact your supervisor. A memory problem has occurred. Complete the current transaction, but do not continue processing. Contact your Unisys representative.FSA Finesse: Allocation error while processing host response. Contact your supervisor. The system will return to the teller idle state. Do not continue processing. Contact your Unisys representative.Reserved.FSA Finesse: Header field length greater than maximum length allowed This error message was received while bui Jlding a data communication message. While attempting to build a message to send to the host, FSA Finesse encountered the displayed error. Verify the data communication information in the Transaction and Data Comm Definition files.FSA Finesse: Index field data greater than maximum field length This error message was received while building a data communication message. While attempting to build a message to send to the host, FSA Finesse encountered the displayed error. Verify the data communication inf Kormation in the Transaction and Data Comm Definition files.FSA Finesse: Index field data greater than maximum index length This error message was received while building a data communication message. While attempting to build a message to send to the host, FSA Finesse encountered the displayed error. Verify the data communication information in the Transaction and Data Comm Definition files.FSA Finesse: Buffer length error This error message was received while building a data communication message. W Lhile attempting to build a message to send to the host, FSA Finesse encountered the displayed error. Verify the data communication information in the Transaction and Data Comm Definition files.FSA Finesse: Invalid common header item - transaction definition This error message was received while building a data communication message. While attempting to build a message to send to the host, FSA Finesse encountered the displayed error. Verify the data communication information in the Transaction and Data  MComm Definition files.FSA Finesse: Invalid common index item - tI   So build a message to send to the host, FSA Finesse encountered the displayed error. Verify the data communication information in the Transaction and Data Comm Definition files.FSA Finesse: Index field data greater than available index length This error message was received while building a data communication message. While attempting to build a message to send to the host, FSA Finesse encountered the displayed error. Verify the data communication information in the Transaction and Data Comm Definition  Tfiles.FSA Finesse: Maximum length greater than maximum index length - TCM error This error message was received while building a data communication message. While attempting to build a message to send to the host, FSA Finesse encountered the displayed error. Verify the data communication information in the Transaction and Data Comm Definition files.FSA Finesse: Data entered must equal the maximum lengthFSA Finesse: Press CANCEL to end searchFSA Finesse: Press NEXT PAGE to continueFransaction definition This error message was received while building a data communication message. While attempting to build a message to send to the host, FSA Finesse encountered the displayed error. Verify the data communication information in the Transaction and Data Comm Definition files.FSA Finesse: Invalid header field source This error message was received while building a data communication message. While attempting to build a me Nssage to send to the host, FSA Finesse encountered the displayed error. Verify the data communication information in the Transaction and Data Comm Definition files.FSA Finesse: Invalid index field source This error message was received while building a data communication message. While attempting to build a message to send to the host, FSA Finesse encountered the displayed error. Verify the data communication information in the Transaction and Data Comm Definition files.FSA Finesse: Not enough memory  Oto build indices This error message was received while building a data communication message. While attempting to build a message to send to the host, FSA Finesse encountered the displayed error. Verify the data communication information in the Transaction and Data Comm Definition files.FSA Finesse: Invalid conditional item This error message was received while building a data communication message. While attempting to build a message to send to the host, FSA Finesse encountered the displayed error.  PVerify the data communication information in the Transaction and Data Comm Definition files.FSA Finesse: Invalid TCM data This error message was received while building a data communication message. While attempting to build a message to send to the host, FSA Finesse encountered the displayed error. Verify the data communication information in the Transaction and Data Comm Definition files.FSA Finesse: Invalid header field source This error message was received while building a data communication mess Qage. While attempting to build a message to send to the host, FSA Finesse encountered the displayed error. Verify the data communication information in the Transaction and Data Comm Definition files.FSA Finesse: Location in source out of range for header field This error message was received while building a data communication message. While attempting to build a message to send to the host, FSA Finesse encountered the displayed error. Verify the data communication information in the Transaction and D Rata Comm Definition files.FSA Finesse: Invalid conditional field source This error message was received while building a data communication message. While attempting to build a message to send to the host, FSA Finesse encountered the displayed error. Verify the data communication information in the Transaction and Data Comm Definition files.FSA Finesse: Location in source out of range for conditional field This error message was received while building a data communication message. While attempting tJ SA Finesse: Invali Ud data and/or format in field Verify that data entered in the field is correct. If so, verify the length, data types, and editing defined for the current field in all associated custom files.FSA Finesse: DUP and COD-DUP not allowed on Error Correct or ReversalsFSA Finesse: Invalid parameter specified in function GetData This error message was received while building a data communication message. While attempting to build a message to send to the host, FSA Finesse encountered the displayed error. Veri  Vfy the data communication information in the Transaction and Data Comm Definition files.FSA Finesse: Source not found This error message was received while building a data communication message. While attempting to build a message to send to the host, FSA Finesse encountered the displayed error. Verify the data communication information in the Transaction and Data Comm Definition files.FSA Finesse: Location in source out of range This error message was received while building a data communication mess, Wage. While attempting to build a message to send to the host, FSA Finesse encountered the displayed error. Verify the data communication information in the Transaction and Data Comm Definition files.FSA Finesse: Criteria not met for next transactionFSA Finesse: Press CANCEL to continue, CODE-CANCEL to cancel linked setFSA Finesse: Press NEXT to begin next transaction in linked set or CODE-CANCEL to cancel linkFSA Finesse: Unsuccessful link; contact your supervisor A conditional search table needed t8 Xo initiate a conditionally linked transaction is not defined.FSA Finesse: Unable to continue processing based on current dataFSA Finesse: Clear current field and press RETURN to skip this fieldFSA Finesse: Enter new dataFSA Finesse: Field level validation unsuccessfulFSA Finesse: Press NEXT to initiate host transaction, CANCEL to ignoreFSA Finesse: Unable to process host transaction, Press NEXT keyFSA Finesse: Conditional Linking not active; file not loaded.FSA Finesse: Conditional file error. ContD Yact your supervisor.Reserved.FSA Finesse: Message sent to host:FSA Finesse: Message received from host:FSA Finesse: Check writer transaction is not required.Reserved.FSA Finesse: Press NEXT PAGE or PREV PAGE to continue, CANCEL to exitFSA Finesse: Press NEXT or PREV PAGE to continueFSA Finesse: ** Posting Date has changed on the Branch Processor.Reserved.FSA Finesse: Unable to retrieve form ID- (nnnnn) A form was specified to be printed in the Transaction Definition. The process cannot be retrievedP Z because it does not exist or is corrupt. Verify that the custom files are correct.FSA Finesse: Press NEXT to duplicate, FINISH to continueFSA Finesse: Host data discarded Data was received from the host but, the matching form definition did not access or retrieve the data, so the data was discarded. Check the message received against the forms listed in the transaction definition record.FSA Finesse: Transaction cancelledFSA Finesse: Press VALIDATE OFFLINE to continue, CANCEL to quitFSA Finesse: Hos\ [t wait time elapsed The time specified in the Station Parameters File to wait for a host response has elapsed. The transaction can be cancelled or processed offline. Press the CANCEL key to cancel the transaction or continue to process the transaction offline. Note: If no action is taken, the system continues to wait for the host response.FSA Finesse: System error A system error was received during data communications processing. Verify that the operating system software is functioning correctly.FSAh \ Finesse: Waiting for host response ...FSA Finesse: Host Format Error: (nnnnn)Reserved.FSA Finesse: Error encountered during Auto Reentry  FSA Finesse was unable to communicate properly with the current processing of Auto Reentry. Check the status of the Branch Control Module and the operating system software.FSA Finesse: Auto Reentry interruptedFSA Finesse: Auto Reentry CompleteFSA FinesJ  o idle The time specified in the Station Parameter File for waiting for a response from the Branch Control Module has elapsed. The current processing is not verified. Verify that the B cranch Control Module is running. If there are many stations configured, the Branch Control Module wait time should be increased.Reserved.FSA Finesse: Password level incorrectFSA Finesse: Day and date do not agreeFSA Finesse: Invalid date and time entryFSA Finesse: Station ID already in useReserved.FSA Finesse: Station ID already in useFSA Finesse: Invalid station IDFSA Finesse: Checks-In ListFSA Finesse: Cash-Out ListFSA Finesse: Cashed Check ListReserved.FSA Finesse: Unable to communicate with B dranch Control Module The current processing is not verified. Make sure that the Branch Control Module is running.FSA Finesse: Press NEXT PAGE to display next teller's recordsReserved.FSA Finesse: Function not allowed; transactions are conflicting transaction types An attempt was made to perform:se: Teller not signed on to Auto Reentry An error received from the host by the Branch Control Module has indicatt ]ed that the teller is not signed on either to the host or to Auto Reentry. The criteria for detecting this is defined in the System Parameters File.Reserved.FSA Finesse: Communication error , press FINISH; ERROR: (nnnnn) While in CRT mode, the workstation is unable to communicate through the Message Control System. Press the FINISH key to exit the CRT mode, then verify that the operating system software is functioning correctly.Reserved.FSA Finesse: ReEnter PasswordFSA Finesse: ReEnter New Password  ^For VerificationFSA Finesse: ReEntered Password does not match New PasswordFSA Finesse: Fatal Error: PASSWORD NOT CHANGED. Displayed during execution of the Change Teller Password local routine. There has been a problem writing to disk and the password was not changed.FSA Finesse: Security ViolationFSA Finesse: Press GO to change passwordFSA Finesse: Another supervisor password requiredFSA Finesse: Invalid multiple of roll or strap amountFSA Finesse: Printer module not availableFSA Finesse: Maxim _um total amounts exceededFSA Finesse: Invalid dateFSA Finesse: Invalid entryFSA Finesse: Invalid teller numberFSA Finesse: Invalid passwordFSA Finesse: Teller A already signed onFSA Finesse: Teller B already signed onFSA Finesse: Error in totals update This message is displayed during execution of the Vault Cash local routine. The Branch Control Module has encountered a problem in updating the totals for either the teller performing the transaction or the vault teller.FSA Finesse: Vault cash inFSA ` Finesse: Vault cash outFSA Finesse: Invalid Currency CodeReserved.FSA Finesse: Sign on to Auto ReentryFSA Finesse: Unable to go online Verify that your station address is set properly in each of the following: - FSA Finesse Station Parameters File - host Network Definition Language (NDL) configuration - host Message Control System (MCS) configuration.FSA Finesse: Auto Reentry initiatedFSA Finesse: MCR file not available The attempt to activate the MCR device is unsuccessful. Records need to be  adefined to utilize the device. Refer to the BTOS FSA Finesse Installation Utilities Operations Guide.FSA Finesse: OCR file not available The attempt to activate the OCR device is unsuccessful. Records need to be defined to utilize the device. Refer to the BTOS FSA Finesse Installation Utilities Operations Guide.FSA Finesse: Unable to continue Auto Reentry An attempt was made to use the Continue Automatic Reentry (CAR) key before initiating the mode. Refer to the BTOS FSA Finesse Operations Guide, Vo blume 2: Teller Functions.FSA Finesse: Unable to initiate Auto Reentry Verify that the date was entered correctly. Refer to the Auto Reentry directions in the BTOS FSA Finesse Operations Guide, Volume 2: Teller Functions.FSA Finesse: Press FINISH to interruptFSA Finesse: BCM wait time elapsed; press CANCEL to return tK  - an error correction on a reversal transaction - an error correction on an error correction transaction - a reversal on a reversal transaction - a reversal on an error correction transaction.FSA Finesse:  eFunction not allowed; transactions are separately defined The error correction and/or reversal transactions are separately defined. Therefore, automatic error correction, error correction, and reversal from the electronic journal are not allowed.FSA Finesse: No records matched the criteria enteredFSA Finesse: Detail search not allowed on local transactionsFSA Finesse: Sequence number beyond range of EJ summary recordsFSA Finesse: No more EJ records match criteriaFSA Finesse: Branch Control Module has f not responded For the current processing, a message was successfully sent to the Branch Control Module but there was no response. Verify that the Branch Control Module is running. If there is heavy processing on the line, the Branch Control Module time-out interval should be increased.FSA Finesse: Unexpected message received from Branch Control Module The message received from the Branch Control Module is not the message that the Customer Service/Teller Module (CTM) is waiting for. The message is ign gored and the CTM continues to wait for the correct message.FSA Finesse: Waiting for valid responseFSA Finesse: No Detail record stored for this transactionFSA Finesse: No Host Response stored for this transactionFSA Finesse: Perform next EJ SearchFSA Finesse: Host now onlineFSA Finesse: Host now offlineReserved.FSA Finesse: Unknown message type received from Branch Control Module A message was received that FSA Finesse can not interpret. Contact your Unisys representative.FSA Finesse: Unexpected S hign On response, ignoredFSA Finesse: Unexpected Sign Off response, ignoredFSA Finesse: Unexpected Cash Balancing response, ignoredFSA Finesse: Unexpected Vault Cash response, ignoredFSA Finesse: Unexpected Branch Totals response, ignoredFSA Finesse: Unexpected Batch Totals response, ignoredFSA Finesse: Unexpected Teller Totals response, ignoredFSA Finesse: Unexpected Checks In List response, ignoredFSA Finesse: Unexpected Cash Out List response, ignoredFSA Finesse: Unexpected Cashed Checks List res iponse, ignoredFSA Finesse: Unexpected Sign On to New Posting Date response, ignoredFSA Finesse: Unexpected Establish New Posting Date response, ignoredFSA Finesse: Unexpected Auto Reentry Initiated response, ignoredFSA Finesse: Unexpected Auto Reentry Suspended response, ignoredFSA Finesse: Unexpected Password Level Inquiry response, ignoredFSA Finesse: Return Customer Cash: (nnnnn)FSA Finesse: Transaction Audit initiatedFSA Finesse: Transaction Audit completedFSA Finesse: Multi Cashed Check initia jtedFSA Finesse: Total of checks cashed: ($nnnnn)Reserved.FSA Finesse: Unexpected EJ Totals response, ignoredFSA Finesse: Unexpected EJ Update response, ignoredReserved.FSA Finesse: Unexpected EJ Search response, ignoredFSA Finesse: Unexpected EJ List response, ignoredReserved.FSA Finesse: Invalid menu selectedFSA Finesse: Status Area Definition does not exist Status Area Definition 2400 must exist in the Transaction Definition File in order to continue to initialize the Customer Service/Teller Modu kle.FSA Finesse: Unable to initialize system, press any key to exit Reset the system to initialize it.FSA Finesse: !! Warning : HOST LINK NOT READY. Press Finish to continue. An attempt was made to establish communications with a host station that is either: - not defined - is configured for a line that is not ready. Refer to the BTOS FSAFinesse Installation Guide.FSA Finesse: Unable to establish communication with BCM; press FINISH An error has occurred while opening a path to the Branch Contr( lol Module (BCM) from the Teller Module. Check that the BCM is running at the branch processor.FSA Finesse: Station ID in use, press FINISH to exit An attempt was made to enter a station ID that is alreaK  s representative.FSA Finesse: Invalid order of deallocation Internal error. Contact your Unisys representative.Reserved.FSA Finesse: Unable to open file Delete the file and restart.FSA Finesse: Close failed Could not close raw file.FSA Finesse: File not found File does not exist.FSA Finesse: Invalid file specification Bad file specification.FSA Finesse: File in use| s File is in use.Reserved.FSA Finesse: Stack full Internal VDAM error. Contact your Unisys representative.FSA Finesse: Stack empty Internal VDAM error. Contact your Unisys representative.FSA Finesse: Extend node Internal VDAM error. Contact your Unisys representative.FSA Finesse: Keep looking Internal VDAM error. Contact your Unisys representative.FSA Finesse: OverWrite key Internal VDAM error. Contact your Unisys representative.FSA Finesse: Key found The specified key was found. Contact y! tour Unisys representative.FSA Finesse: Insert and shift Internal VDAM error. Contact your Unisys representdy in use. Press the FINISH key to return to the FSA Executive Menu and choose FINESSE System Sign On to enter a new station ID.FSA Finesse: Recovery completed successfullyFSA Finesse: Unable to load Device Server During system sign-on, a problem has been encountered while attempting to load the Device4 m Server.FSA Finesse: Request for Supervisor Override received; press RCV MSG or CANCELFSA Finesse: Invalid Speed Transaction IDFSA Finesse: Requested Speed Transaction ID has not been definedFSA Finesse:Press TLR-A or TLR-B keyFSA Finesse:Invalid Local Routine IDFSA Finesse:for Teller AFSA Finesse:for Teller BFSA Finesse: Unable to find Device Configuration File(s)FSA Finesse: Exiting to Administrative ApplicationFSA Finesse: Exiting to Finesse ExecutiveFSA Finesse: Exiting to @ nCTMFSA Finesse: Reloading Customer Service/Teller ...FSA Finesse: Not Enough MCM subqueues configured. Press FINISH to exit.FSA Finesse: CO Error nnnnn during queue set-up, Press FINISH to exit.Reserved.FSA Finesse: Deallocation error Internal error. Contact your Unisys representative. Of Course!: Program file is an invalid reel. The RSAM file containing the program is malformed.FSA Finesse: Invalid memory pointer specified The address of the memory to be deallocated does not match any address oL of memory that was allocated. Internal error. Contact your Unisys representative.FSA Finesse: Memory stack overFlow Too many variables have been allocated on the memory management stack. Internal error. Contact your Unisys representative.FSA Finesse: Unable to allocate memory management stack Available memory is insufficient to allocate the memory management stack. Internal error. Contact your Unisys representative.FSA Finesse: Unable to allocate memory Available memory is insufficient for alloX pcation. Internal error. Contact your Unisys representative.Reserved.FSA Finesse: Invalid bit position The bit position does not fall within the allowable range. Internal error. Contact your Unisys representative.FSA Finesse: Invalid bit string The length of the string does not equal 8 or the string contains a value other than 0 or 1. Internal error. Contact your Unisys representative.FSA Finesse: Invalid number string Non-numeric character in numeric string. Internal error. Contact your Unisysd q representative.FSA Finesse: Invalid parameter specified Either the destination string is too small or the source string is empty. Internal error. Contact your Unisys representative.FSA Finesse: Invalid string size The string length must be between 0 and 32763, inclusive. Internal error. Contact your Unisys representative.FSA Finesse: String size too small Returned by number-to-string procedures if the string is too small to hold the converted number. Internal error. Contact your Unisys represenp rtative.FSA Finesse: Invalid pointer, value is nill A nill string is being used as a parameter. Internal error. Contact your UnisyL ative.FSA Finesse: Invalid key specified Internal VDAM error. Contact your Unisys representative.FSA Finesse: Out of memory Internal VDAM error. Contact your Unisys representative.FSA Finesse: Key not found The key pointed to was not found, or this message was caused by a customizing problem. Reload the SKM menu files and restart.FSA Finesse: Duplicate key The key pointed to is a duplicate# u.FSA Finesse: Need to split node Internal VDAM error. Contact your Unisys representative.FSA Finesse: Compress failed CompressFile error. Contact your Unisys representative.FSA Finesse: Build of temporary file failed Insufficient disk space exists to hold temporary files. This code can be returned by the CompressFile or RecoverKeyFile functions. Contact your Unisys representative.FSA Finesse: CleanUp failed CompressFile error. Contact your Unisys representative.FSA Finesse: File name build fai% vled Problem creating temporary files used by CompressFile and RecoverKeyFile. Contact your Unisys representative.FSA Finesse: Read failed VDAM File read problem. Contact your Unisys representative.FSA Finesse: Unmatched check digits The record contains unmatched check digits. Reload the SKM menu files and restart. If the problem continues, delete the completed screen record from the user file and recreate the record. Contact your Unisys representative.FSA Finesse: Record not found The key exists' w, but the corresponding record does not. Contact your Unisys representative.FSA Finesse: Record size larger than maximum allowed The record size specified in the key file does not match record size specified in record file. Contact your Unisys representative.FSA Finesse: No current key Internal VDAM error. Contact your Unisys representative.FSA Finesse: Invalid insertion Internal VDAM error. Contact your Unisys representative.FSA Finesse: Node not found Internal VDAM error. Contact your Uni) xsys representative.FSA Finesse: Key length too large Unable to locate the record because the key length is greater than the key size specified for the file. Contact your Unisys representative.Reserved.Oracle: An ORACLE application failed to connect because of insufficient memory.Oracle: ORACLE could not perform the requested operation because the maximum number of processes have been exceeded.Oracle: ORACLE could not perform the requested operation because of an internal BTOS TWO_TASK error.Oracle: S+ ypecified BTOS two task driver is invalid.Oracle:  An ORACLE server could not be created.Oracle: ORACLE could not perform requested operation because of a set user interrupt failure. Reserved.Oracle: ORACLE could not create a required background process.Oracle: ORACLE could not identify a background process.Oracle: ORACLE could not delete a background process. Reserved.Oracle: ORACLE failed to initialize because of insufficent memory for SGA.Oracle: ORACLE failed to initialize because the required SGA - z(System Global Area) process could not be created.Oracle: ORACLE could not locate the SGA (System Global Area).Oracle: ORACLE could allocate the program global memory area. Reserved.Oracle: Internal OSD wait failure. Reserved.Oracle: ORACLE could not open the indicated database file.Oracle: ORACLE could not identify or locate the indicated database file. Oracle: ORACLE could not close a file.Oracle: ORACLE could not read a file.Oracle: ORACLE could not write to a file. Reserved.Oracle: ORACLE coul/ {d not parse out the device or directory portion of the indicated file specification in the list of after image journal files. AIJ file not created.Oracle: ORACLE could not open an after image journal file. Oracle: ORACLE could not identify an after image journal file.Oracle: ORACLE could not close the specified after image journal file. AIJ file and database extent files remain open.Oracle: ORACLE could not read an after image journal file.Oracle: ORACLE could not write to an after image journal fil1 |e. Reserved.OL  ed.SNA 3270 Terminal Emulator, BSC 3270 Termina0> l Emulator: Attempt to deinstall on single partition operating system. Note that erc 33 will be returned from an shared resource processor or from a workstation where the system service does not reside.Reserved.BNA: Port file exception. Examine the value of the BNA error code addressed by the pointer pwBNAercRet, which is returned by the port file function.BNA: Halt. Examine the BTOS BNA Haltcode logged in the system log. Take a dump and submit a UCF with the proper information.BNA: Power Reset Modracle: Software error. Contact Customer Support.Oracle: Software error. Contact Customer Support.Oracle: Software error. Contact Customer Support.Oracle: Required process could not be performed because an invalid reminder date was specified.Oracle:  Required process could not be performed because of insufficient interval from last occurrence.Oracle: The maximum number of reminders (200) has been reached.Reserved.OFISbridge: If OFISbridge exits and identifies an error code in the range 3 }of 30000 to 30350, the OFISbridge system file BDtext.sys is invalid. You should notify your System Administrator.Reserved.SNA PDF: Unsupported RU type. The application using the API receives this error when the RU type indicated in the SendAlert request is not supported by SNAPDF. Zero is the only valid value for SNAPDF 1.0.SNA PDF: Invalid alert type. The application using the API receives this error when the value specified in the Alert Type field (wTypeCode) of the SNAPDF SendAlert request is in6 ~valid. Valid hex values are 01-07.SNA PDF: Invalid alert major probable cause. The application using the API receives this error when the value specified in the Alert Major Probable Cause field (wMajorProbCause) of the SNAPDF SendAlert request is invalid. Valid hex values are 01-0F.SNA PDF: Invalid alert minor probable cause. The application using the API receives this error when the value specified in the Alert Minor Probable Cause field (wMinorProbCause) of the SNAPDF SendAlert request is invali 8 d. Valid hex values are 01-FF.SNA PDF: The SNAPDF system service is deinstalling. The application program receives this error when a request is sent to the SNAPDF system service while a deinstall request is being served.SNA PDF: The SNAPDF WriteLog filter is deinstalling. The application program receives this error when a request is sent to the SNAPDF WriteLog filter while a deinstall request is being served.SNA PDF: Invalid user action code. The application using the API receives this error : when the value specified in the Alert User Action Code field (wUserActionCode) of the SendAlert request is invalid. Valid hex values are 00-FF hex.SNA PDF: Unsupported resource type. The value specified in the Resource Type field (bResourceType) of the SendAlert request is not supported by the SNAPDF program. Valid values are 01-03.SNA PDF: Unable to deinstall on a single partition operating system. A deinstall request was issued in a single partition operating system, which cannot be served. Reboot$<  your system to deinstall.SNA PDF: The system service for which an installation is being attempted is already installed on the system. This error is returned when an attempt is made to install the SNAPDF system service or the WriteLog Filter system service when it has already been installed.SNA PDF: The PDF system service is malfunctioning. There is a serious problem with the SNAPDF system service. Deinstall this system service, and reinstall it.Reserv