IMD 1.17: 25/12/2009 18:38:45 45858255-041 4of8 standard software system utilities style: b25-stp level: r12.3.08 03/02/94 label: b25stp-4/8    9|P^GWoep4 bBP7w4Copyright 1993 Unisys Corporation. All rights reserved.Ver R12.3.0 Linker R12.3.1 ?O@p`#?4?@CDpEFKLPQ@R S_YO^P`bo`d/dOg/Pgi?jPj kknppp@q@r?r0t vvwx/x zO{_OО0P @__ ?op'(1"E )* 0 /5,x%97J(APe  y 9Gtepo{)\{x_}666666n66$6T666656f666I66Q6T660 6 6 6 6< 6s 6 6 6* 6f 6 6 6 6K 6a 6 666{6@@@l@@@@v@@@@@@@+@B @{ @ @! @T @ @ @k @ @ @1 @g @ @ @ @@n4HWW7+GR \    -h$A$2C25222 222G2G.R'  /FX%G>DiyA v _ y /0$C$c$$/j///.CCx?i+Ff*@8|4|A|]|v||| | |S | |||R|;t=3 P3 ,/ 2 `     9 J ( > `   / 6@4HWi $2-FMpu  $/Cbox*@|3 E T / < N \ r ;[ -Ao&,?0IXm /5?qz  / D b | %+Obh|(.<Bm2 : R l  " : X |   v v v v v v v v  v  v v  v  v  v  v v $ v ( v , v 1 v 5 v 9 v = v A v F v J v N v R v V v [ v _ v c v g v k v p v t v x v ~ v '*6Y66666[6666-6666L6c6B666 6g6n66y6666a66;@@@A @ @ @W#iQii i~ii}iiisiii<fs$%2=2222(228Trl?%NI FFOMM"pu`ugv v v 4 8 ao*9Z !3 $0Cb5brbbbno_x3 3z9kF<KRj{[t3PdsR*******"*H*N*@@@!@ ||p||`||I|`|||Q|||Q||||\ | | | | | |% | | | |9 | | |||||B||||,|y|||||+|y,b  5[(N~wE YT T T T T T eT T T T T T qT T T & T T  T { T  T t T T Q T T < < N #    rx P PPh> s P P,Ph SPP Ph   $ P P Ph8  < P P Ph&?[t@6N&8]tA"r%w>^Y&?tA"r%w>^YS6S6RPPPhVS6ZRPPPPPPhN r &?u x- P P,Ph SPP PhP} Ph0P Ph8P PhP P PhS6S6PPPPh UF ^F_F `FaF bFcF dFe ^򤸤 P@PHPh rƆhƆiƆjƆkƆlƆmdžnpƆ]]vG]pPv]BP]^]]t> t@> "r8pP`PhPPRPPRPPdPh5pPPhPPRPPRPPdPh^PPhv Ph]UQF0M^&F M^&GFM^&G]U~uv <]U PPhPP P/lPh   PP P/lPh    & t@FPr & t@P~ P*PhP P*PhS6RPP~ SP SPC F]U P@PHPh6FPP>t@~uA"r,PP6 PP| PPPPPq>uPP6 PP| PJPh PdPhPPMPhFvF~u@> tA"r> w  .PFFTFZPFFTFFjFFnF2FFFFFF P^SvRPPrmPPh"Px P,Ph6x S"PPh6 Phx S"P-Ph &G PPMPh "rk &#t@ &tA"r &Ƈ  &Ƈ &ƇP & & &#tPPh6| PP PPhP9F^FPFPPPPFP >t@~wA"r PPvFPZPh2> u( P9P9>)u )P9P9 &G &GrRPP &G@]U &uv &w  &GPP &_ S &w| PZP PPFP,>uzS6~RPPPP>u@>uA"rFPzS6~RPPmmP>u{^&EM &G^&G &O &w ^^Yv^SPPP| P$>tv  v^SP-PS6RPPtmPx PP>tJP PP| P>v P P6| | PZP,]UFPrPPFPFPPFPFP6rmPr   ]˃~t  F  &G]UPP P/lPh &?uV6~F~t+Ju&FFFwB1FFuF;Ft~vFFF^ v&8#tFF 10^ v&PF1F10&PF1F10&~t2FP^ SvRPPvF uv F]Y[^扌lX0DXX^X拌lX0DSQU].^U].bU].fU0~ w ] FPFP uF~ t@~sA"r F ~ r9PFPPF~u F] ~t !] ~ t@~tA"rPF~u F] FFPF~t~Ѿ ~ྵ FFF^^&^&^& 1FЊFЀ0FފFб ^&+ȁ0NߍFPFPvRPPrmPF~t v Fv~ NF^&F] UF^&~ vPPFP/lF tFFF& t@FrFPF t~ F 10v &TF1F1v &T F1F1^ &W ^  FP^ SPRPPrmPF u~ ^&G F 10v &TF1F1v &T F1F1^ &W ^  FP^ SPRPPrmPF~u ^&@~ FP^ SPRPPrmPF t"^&TsFPFF~t~ F 10v &TF1F1v &T F1F1^ &W ^  FP^ SPRPPrmPF u^&v FF~tL&~ FP^ SPRPPrmPF u^&v FF^ Sv ^SF~tFF] UF^&؊>,~ FP^ SPRPPrmPF u ^&=;~ FP^ SPRPPrmPF u^&v FF^ Sv ^SF~tFF] UFD]F%P2FF%P"FF%PFFVU~u~uF]FPF urFFFFNNNNFFMFFFF6DFP TF u*vFPLF u^& Mt^&GFP F u v^S$ v~Fv FPjRPQRPQRPQFF@vWv FPPNQPNQNAQNQPFFvBv FPFVNQQPQFPQFFP F uvvvb FP F u vvFFFFFsFFvRPQ^SjRPQRPQFFP F u(v^Sv^Sv^Sv ^Sv,>u =F uFFPF tF= r= rF= t = t= tTs*v^Sv^Sv^Sv ^SvvZETs'^Sv^Sv^Sv ^Svv*jvv^Sv^Sv^Sv ^Sv\F hFPjF up~tjETs-hv^Sv^Sv^Sv ^Sv\(v^Sv^Sv^Sv ^SvF~uCF!>PtF tt !tF*~ v~v~v ~vv~ڋNFv~ՋNF~ r'vRPQRPQPjPjF~tFF9FvJtFF t Ⱦ~F t ȍvڿ~u~tI~ r)vPvPvRPQRPQFvPP4F u,FPF umFڈF۰F܈F݋FFދF؉FF FFFFFFFFFFFFFFF FFFFFFFPF u,v؍FPLF u^&G ;F t^&GF~ uN~uNP~uN F LPj@F t˸PPF t˃> u>s> v>Luf>Pt_FFJ~uy>JurjvFP,F u)F=8t =9t=9uFHP@JX`HF믂>Lu'>PtUW&>u =F ucFPF u^&G^&uvjP/>Lu :Fu vQhFFvjhF ue>Pt[>Luv^ S^S>Luv^ S^SF u#>Luv^ S^S F u &s6^&uFFFPPNQjRQPRQP5t^&u44 "^&7&w&w&w&wtF^&tFF<wH FFߠsRPQ^SjRPQRPQ5tF^ F&@FuFF<wF FFߠsRPQ^SjRPQRPQ5tF^ F&@FuFF<w< FFߠsRPQ^SjRPQRPQ5tFİ FuF FߠsRPQ^SjRPQRPQ5tFİFF<w: FFߠsRPQ^SjRPQRPQ5tFİ FuFFߠsRPQ^SjRPQRPQ5tFİ̊F FߠsRPQ^SjRPQRPQ5tF^ &GȊF FߠsRPQ^SjRPQRPQ5tF^ &GȊF FߠsRPQ^SjRPQRPQ5tF^ &GȊF Fߠs RPSvVQRPSRPS5tF^ &GȊF FߠsRPQ^SjRPQRPQ5tF^ &GȊF FߠsRPQ^SjRPQRPQ5tF^ &GȊF FߠsRPQ^SjRPQRPQ5tF^ &GȊFFߠsRPQ^SjRPQRPQ5tF^ &ȠsRPQ^SjRPQRPQ5tFhjP/lF uF& &s#FRPQ^SjRPQRPQ5tJ^&8GtB>F9t&u"F݊F<wHаFu^&^ 0~޵FFF<wB޴PNݵBFuFF<wNHЋBFu4^&u,FF<wHаFuHj^&^ 0~޵FFF<wB޴P@NݵBFuFF<w:HЋBFu FF<wHаFu>F9u,FF<wHаFuH>F8ud^&u\~v FFF<wB޴P{NݵBFuFF<w>HЋBFu'FF<wHаFuH FP F u vv~tvFFFNNF NFF F?F*F r> u>rxrsv RPQRPQFPjFPjF uH~u~~vNFv FPjRPQRPQRPQF uFP F uv^SvȆ^&^&G :t W^&G<t':t!&OFPsFr^&G^&u2F ^&~ t^ &?utPPP^ Sv _>u!FPF u ~ r ujjP/lF t^&GF&8G wFX ^Fv&DF&GF&GF&GF^&GF&GF&GF&GF&G F&8G uANsNQPPF t FF^&#tF ;Fv F&O#F ;Fw FrF9F w~^ &FF^&O&@^&G^&w6 FA:r smVnjޱ;u$:uH^S,F9^SFP#F u'^S^ Sv ^SFz^&G F ^&^&O :]v ^&Vnjޱ;u$:u7r0>r)PPjRPQhwmRPQF u(^&G :Hu ,FF^Su FFN F;w~t^&W&;WrS^ R+QFP,FT^&G&+GFV N+;sV^&FF^ v0~&}^9N^Y^F&GFFcF^&FU^&G :]v ]U^&G :]v ^&G ]U^&]U^&]U]U^& t^&G :u &G& u] ^&G :zt5SvF<F>sFތ;u;u P,FF0^SFP#F u^SvF<Fz^&O ^&FF~tiFs_h^&7P,F^&~t3^& u+JV rF^&^&F PF uFF PF uV  "$&@PF u6  PLF u 9Fr>t7>t \ Љ>u>t @~ ruut \>t `c8t!>t8t>r? ut;s;t>r>sC>u9>u/>u%FPFPF tFFr >t @>t>u>u rF ;s;t~r>r@9FwF~NFP F u6^SvUQF =rmt =tmt"63rmP'(*3^&G ]UQF =wmt =amt!6Hv ',.H^&G ]U^&G :Ht ^&,SP(]UQ^&^ &&W^&G :3t (S)$]U^&G :Hu,Sv*4 ]j&jFP/lF u ^&G-hjFP/lF u^&G < sA<v@"FFF FtFPjF t@^&FUFPFP"V^&?{t@&?[uT6:jt. FPQSVSVQ^[Y=Xt ],N~] t&<6u>4u4PP(\~u<4&G& GujF P,F u|F4&_^ F &FF #t+ȉNF V F V )NF 4&GZ&WF^ &F FN;s^ S+P F uHF^ &GF^ &GFF9Fr$^ X^F&^&GFuԸ8>6u>4u4PP(\4&_^F&G;F s FP^Sv ؎F@P>6u>4u4PP(\4&_^F&G;Fs 28v^@02^&O&0&GU8r 4&_S^S0S]^&v ^ &Gv&L@^ &;vS&O+P0F ud^&O&7^ &y^Y^&G^ &w&^ &G^&^&G@^&G^ &Gv&D@^ &G ^&v ^&&G^ &;Gthj \^ &G@v&L^ &;vS&wF+PiF u^^&O&7^ &y^Y^&G^ &w&^&G@v&D^&G^ &G@v&D^ &G 9FsF^&&+GFSv+FF9Fw^SF+FPF%FPvFPF=t5v(\^&%FN;tFPQvP(\ FF^&F^&OANFF;Fs"^&@&PFVFFFFFFF;FwFFF;Fs;^&@&PFVF9Fv9Fw~t FFFFF뽋v^&@&PFVFN;s7N0^~9^YFFvFV^&@&PFFFF@F^&GFF;Fs@^&@&PFV~uFFvFV^&@&PF^&+FFN@;vjvFPF=tCv(\vF#^;Vu&#+ЉVFNPQjFLNFȃ#ʉN^QN+#QF uFP+F%Y+ȉNFF^&F^ &G :uSvvL^ &G :ztWSvvn^ &G ^ SvvFNs=u8^ SFP~u#z^ &G ^ &t@Fs률z^ &G F0^ &G :t9&G 9Fu9Fu^ &G&WFV^ &G&W;Vu;Fw3&G^ &G^ &G^ &O&W;Vu;Ns^ &Gs &G&;GwH^ &G &W"N~;u;w/&wщFVN;u;s&+O &"N։~؋FjFVFVF%Ff^ &G^ &GNV^ &O &W"^ &G^ SPFPFPF t2F^ &G"^ &G :t :t^ &G&G &W"FV&9Wu&9Gw&G&W9Fu9Fu^ &G&WFV^ &tSj$F t^ &G&GF%^ &G^ &GF҉VԋN~+&O &"^ &ta&w8&Sh^ &w"&w FP#Fu^ &?(~t"^ &G&GF^ &G :}t ^ &G :uS^SzLO^ &G :zt S^S<6^ &u^ &G ^ S^SFz^ &G FU^&G :t:u^&G&G &W"^&&Wd^&G :uY&Gs&G&;Gv &G&W^&G&G &W"^&&W^&G s7&G s/^&/&_!^&G :}u^&&G ]$^ SvRPPNQNQPF uM^ SvRPjFPFPjF u$^FF;Fs4z0r vz9vq^ vJ܀0Fġ< :uhDj:P/lF uK:&G ^;v ^:X ^F&u^& u@^ Vnjޱ;u$:uu^&GjjFP/lF t^&$>t~t}?rv^&GQQjRQPham^SvF?@~&F =amt =wmtFPsFr^&G _^SvFPFPF uE^&G F^&GFsF^F^S^SvFPZU^&^SP$]^&G :t :t UƆ^&GF1F&VF9FtfF+^&G &W"FV&w8SQRPFP#F tuvN+N^~9^&w8^Sv^&w"&w FP$F t%u^Sv$F uƆ뵋FsF1F^&G &W"F+F^&GN+N^v0Y^&G&GFss^Sh$^&G :t :t ^&G&WFV&O&O &"N~;u;wN~Fs FF%~&] ~&] Y]UP3P%4]UPP%4]U졒#t4&F#t N#N&3&]U^ &G 33&:t :.]t$C^Y tt &^&] ]U^&G :]w):3u(&G t&G uF&G &G 3   ]U^&G Pt=t P < ]U~u]UhjRP/lV tR&?s^& R&?s^&#jR&? s^&&QR&?s^&)8R&<vjF~uv&<tF~to~tEv&<u<^&?t'~tv &* v &*&4v &^&~tv &F^ &^SPvFPF uFt^ &FFF~NuV~u ^&P ~u^&7P^ S ~u8^&w&7P^ S F^~Hu2Ft tuS^SvP^ S F^~Du_~uFPF~u^&&WFV, PRPvvvPj ^ S<FF^^S^ &7^Svv^S FU츔Pjbu bPF>c r!vvv^Sv ^SvEOjjFP/lF u^&G N;wukF=s5^_ ^F&HN&HN&HN&^&G F&G FܸFމFF;FsF;Fr@Fv9F u"F uFFfFPFfY;v ^&?tqjjFP/lF uhjFP/lF uҸFF^&GFԌF֚0D~svvv^&/^&?uFFPFڹY FFN^ԋFFFFHN;sFFF^&?u_F^غ#ډ^v^&^&~v^&0^&7|PFNX^&@CvF~^&^& ~vS^&^[&Av^&^&@FH;Fu 1FtF)FFFFFtFFFtNFtNFtNF>bubPFF>c r&F=sPvvv v vv,FF~FF ;FveFF~uQN F;vG;sV F +FFvFFPFFPFPvFPj|FFFF듋Fq PNVFXC XC pfSysInit Batch*SI6[Sys]Sys.Font>[Sys]T1Sys.FontV[Sys]BAWSSys.Fontp[Sys]V1Sys.Font[Sys]SysInit.Txt[Sys]Batch.Run[Sys]EF###>SysInit.Jclys]ExecMsg.binNLS[Sys]Nls.Sys&[Sys]NlsService.run>[Sys]<$000>SysInitCrashMsg.txt\[Sys]II020A01HWID[Sys]DAI>SysInit.JclMRN[sys]HW>SysInit.Jcl[Sys]WS>SysInit.Jcl[Sys]WS>Sysinit.jcl[sys]HW>SysInit.Jcl[Sys]SysInit.jcl[sys]SysInit.Jcl        [KBD][VID]89>< DVTWPYX[scr]<$>BsFilter.tmpVNVFB22B21B25XE B27VE1WMASTERSERVERLOCAL{}[]0123456789ABCDEFII120A00 Error 2624: msg= %0N maxlen= %1N^Press NEXT PAGE or SCROLL UP to continue(Press NEXT PAGE to continue!a?!*a**2Q=\zCKACTION BACK SPACEBOUNDCANCELCODECOPYDELETEFINISHGOHELPLOCKMARKMOVENEXT NEXT PAGE OVER TYPE PREV PAGERETURN SCROLL DOWN SCROLL UPSHIFTTAB#+17?GKQW]citTD aAdDhHmMnNoOsStTwWyYgG!oo!/!0d!/!0y! !hh!:!0m!!2AA!!*o!/!0d!/!0y! !*h!:!0m!!2*A!"!Nnn! !dd!, !yyyy! !hh!:!0m! !2AA!"!Nnn! !*d!, !yyyy! !*h!:!0m! !2*A!(!Www! !Nnn! !dd!, !yyyy! !hh!:!0m! !2AA!(!Www! !Nnn! !*d!, !yyyy! !*h!:!0m! !2*A! !0t!:!0m! !*t!:!0m!!hh!:!0m! !2AA!!*h!:!0m! !2*A!!0o!/!0d!/!0y!!*o!/!*d!/!0y!!0h!:!0m!:!0s!!0t!:!0m!:!0s!.tmp!W*w! !N*n! !*d!, !*y!!N*n! !*d!, !*y!"!0o!/!0d!/!0y!-!0h!:!0m!:!0s!!2*A!!Nnn! !*d!, !yyyy!Invalid Template Index$Cb %6FVfzTN00sundaymondaytuesday wednesdaythursdayfridaysaturdayjanuaryfebruarymarchaprilmayjunejulyaugust septemberoctobernovemberdecemberampmnoonmidnight05 invalid namesunmontuewedthufrisatjanfebmaraprmayjunjulaugsepoctnovdecampmnm05 %0:BLU_fmrx~ #(-27;?BEI{R12.3.0[Kbd][Vid] [SysIn][SysOut]>$a]y]y ]y {y2$t  [Sys]SysInit.?.jcl  [KBD][VID]>j>   0123456789ABCDEF      LIBRARY: ctos.lib VERSION: R12.3.1 (friday november 12, 1993, 17:19) LIBRARY: ctostoolkit.lib VERSION: R12.3.1 (friday november 12, 1993, 17:21) LIBRARY: enls.lib VERSION: R12.3.1 (friday november 12, 1993, 17:22) LIBRARY: init.lib VERSION: R12.3.0 (monday november 15, 1993, 15:51) COPYRIGHT (C) 1980, 1993 CONVERGENT TECHNOLOGIES, INC. ALL RIGHTS RESERVED. COPYRIGHT (C) 1980, 1993 UNISYS CORPORATION. ALL RIGHTS RESERVED. THIS SOFTWARE IS PROPRIETARY TO CONVERGENT TECHNOLOGIES, INC. AND UNISYS CORPORATION AND IS NOT TO BE REPRODUCED, USED OR DISCLOSED EXCEPT IN ACCORDANCE WITH PROGRAM LICENSE OR UPON WRITTEN AUTHORIZATION OF THE PATENT DIVISION OF UNISYS CORPORATION. THIS PROGRAM IS FURNISHED UNDER A LICENSE RESTRICTING ITS USE SOLELY FOR THE OPERATION OF A DESIGNATED COMPUTER FOR A PARTICULAR PURPOSE. TITLE TO AND OWNERSHIP OF THE PROGRAM, INCLUDING ITS SOURCE CODE, SHALL AT ALL TIMES REMAIN IN THE NAMES OF UNISYS CORPORATION AND CONVERGENT TECHNOLOGIES, INCORPORATED. VERSION: R12.3.0 (monday november 15, 1993, 15:51)V ;u~uA+uA+ًAv~~F󤒙RPFP+~uA+Ѿ~uA+Av~U+FVFVFF;F}v &DFVFF FRPvvFVFVvFމvFvv+R,RFFVRP,RP"FVFVĊ*U+FFF;F}v&TVFFFUPFF=} tFU~3tn n UvGWl@tE~t @6"ttڎwCopyright 1993 Unisys Corporation. All rights reserved.Ver s12.3.5 Linker R12.3.1 4>>)`Col/POP/_   p'0H?M/U0dd`ii_ppq`r`st?@o?o 0?P_ P` O/O@p_``pO p @@P  !p/0 p1?0;p;_<`=p>_@??@@ABOENOT?\]_` `?0apdOPhj@kolpm?`o~@0?Є?O0/0P@!*'(}1"E )#+7* 8F0 % -/5N,! )/D5PhW 0ji}?v . 4v!O<mt-5Ec(B  Ju(e,W* t ["u##A$$$%%&&''((  sJBh/c O   !7E@GuUulu]uzuuuuu+uNu{uuuuuu{uuu=uuu unuzuuuuzuuu5 uL um u u0 uL ux u u u u| u u u uuuuuuuuuxxxx(x>xxxxx;xpxxx"xxxBxqqq7qqqqqqqyqq%>v  j  # ;  !\T! S z  f  @       y       ?  `             2    ; <; ]; z; ; ; ; ; 6; W; ; ; ; ; ; ; ; ; T; ; '; > {> W> > m> > L> > > \> > > > )> @> f> > >  u ?    # Q x  * P  * v - 9 W g ~  i   V f  b   C m w  R O [ x   _ 5_ _ _ _ \ _ h _ _ _ _ _  _ ( _ u_ jjjj j j j jp77U77F 7R 7o 7 7sCC^CyCCCC CC+CCCaCCC7Bm7w(cv        Tg7+GRV-VhV_C_5___ ___G_7'/M  <    d     *Pdh-S0OCOcOO}ZZZZZZnZZ$ZTZZZZ5ZfZZZIZZQZTZZ0 Z Z Z Z< Zs Z Z Z* Zf Z Z Z ZK Za Z ZZZ{ZojoooivL} V+?+i+++999J9(9>9`999/9yy( 5F/Em??$??7?? ?u??a?s? i=w+Ff$6$O$o$$$$$,$H$$>$Q$$$$*$<$,84A]v  S  R.WW^W&WbWWWVWW WM W W W WQ Wg W$dtu=P|u)sQ  9  M Y j L'L'L'L'L'L'L'L'L' _    !!F!!!0!! !{!!! " ) ""\""""N'""" "F###E#GE#_j#yj#3t#rt#7#H#2#`##########l####v#######+#B #{ # #! #T # # #k # # #1 #g # # # ##$&$a$$$$$ $$%A%<% k%k%/k%Fk%Xk%Ds%is%s%ys%.%%%U%%%%%%%;%%%%uxxq ; > _ j7CV_OZdho+9uy?%0[k$YgMW$dus w !!! """""""#E#j#t####$$$% %%%C%H%k%s%%%%%&.7Lr=X 28=t .4DJ[{#17GMR^(8HNr!'-Gtz # < A F a q   O h { J^0^}-KQ~5=~WMk0o   0 J g m  ^ < e  3  / 4 R+X}b0MSm4_y/;CHH5<+~ 2 ^ | !k!!,"c""-#}###$I$a$$$$3%[%%%%,&T&&&&%'M''''(F(((()"'&'*'.'2'6':'>'B'F'J'N'R'V'Z'^'b'f'j'n'r'v'z'~'''''''''''''''''''''''''(Six~kHq<e1^pk + 1 {    o  r z   ; A _ e A"(-5==E>Dbh?^ $8>W]{e+nQ[#LwDn 'uuu=uuuuu!uhuuuu7uuguuuuuuuHuZuuu uuuuxpxxxx!xwxxxxx xgxx[xxx!xxXxxxTxx x0 x x x x xH x x x xF xd x x, xB x x x xX x^ x x x xx(xgxxxx x%x+x q'#q':q'Mq'aq'xq'q'q'q'q'v %&z %&~ %& %& %& %& %& %& %& %& %& %& %& %& %& %&qSq]qqqq`qqqq&qqq9q[qqqqq-qKqUqeqqqqq q %&V\ SY,2rx W   r \  + C     09 A k   K  X  V   #        $ W         < K     * 0    ; P; ; Z; s; ; ; l; ; ; /; 5; x; ; ; ; !; G; ; ; ; ; $; ; ; ; ; ; '; >; c; z; ; ; ; ; &; @; I; ; ; ; ; ;  ; ; ; ; ; y ; ; ; ;  ; N ; ; _ ; | ; ; ; ; ;  ; ; \; ; ; ; ; ; ; 6; )> C> > > $> D> > > % W d  - N      2 `      9 _    9 V c     o |    `       @ b z A )  ( z          _ "_ 8_ _ <_ d_ k_ _ =_ T_ Z_ r_ x_ _ _ _ 6_ S_ _ >_ _ _ _ !_ 8_ V_ m_ _ _ _ _ _ _ 6_ <_ l_ _ _ _ _ _  _ %_ ;_ _ _ D_ _ _ + _ I _ _ _ _ _ 0 _ = _ }_ _ _ _ _ _ _ _ 9_ D_ O_ n_ _ _ _ _ _ 3_ H_ o_ _ _ _ _ jj?jkjjjBjJjjjjj jjj1j>jnjjjjjqjjjjj j(j5jSj`j~jjjjjjcj j j6 j jB jz j j j:7l7y77$7K7w77777<7n7{7777-7F7_7777777G7777>7K777 7707s77[77777777'7;7X7e7y77777 7 7 7 7 7 7" 78 7p 7} 7 7 7 7 7 7 7+ 7H 7U 7i 7 7 7 7 7 7" 78 7v 7 7 7 7 7 7? 7L 7 7 7 7 767707h7777777D7Q7e7p7777777'727j7w7777f7w777777777E7V7n7777 7U77777,7977777C7d7w77777c7p777787S7777737@7v77777#7s77777>7K7777 7777 7X77777J7[777M77777 7 75 7 7 74'#C)CcCCCC CfCCCCCCCC#C3CPCVCCCiCoCCCiCCC!?io.JYu#NTc/<ci"BOou<Ian<FT<dvr";|7f,4  J s  3 f  ?s%_=____(__<gbct,  9TOZYZZZZZ[ZZZZ-ZZZZLZcZBZZZ ZgZnZZyZZZZaZZ hhD4^,tz5=wR#)+99u09g  W  . h   7 6   RvF33>|,S.b)}8O{9?Y??P?p???????[?????g???}??]?????J?ih1=`LQ@0030n000 0:00[k[kkkFkokk4uZm<F3 YY3gzgg9gkg3zE<'3zc! p`I`QQ\      %    9   B,y+MWW.WW W W& WT W W? W WY Wo W$$$$d5u[uuuu(uNu~uuuuwuuYeq&   {  t  Q  Rh!zX;v(p w  # XL'bL'lL'vL'L'L'L'L' L'= L'k L' L' L' L'# L'Q L' L'L'L'L'L'L'M'M' M'M'M'M'M' M'$M')M'-M'1M'5M'9M'>M'BM'FM'JM'NM'SM'WM'[M'_M'cM'hM'lM'pM'tM'xM'}M'M'M'M'M'M'M'M'M'M'M'M'M'M'M'M'M'M'M'M'M'M'M'M'M'M'M'M'M'M'M'M'N'N' N'N'N'N' A  m  I l!!*!P!t! !o!s!!!6!!!!!!#!Q!! !~!!}!!!s!!! "8 "T "r " " "3 "i "n " " "! " " " "v"""C"\"""""#Q#`###b#%E#NE#E#E#IE#j#at#t##;###A # # #0%&4%&$$$$$$%%5%%%"C%H%`H%O'O'9s%Zs%0%%R%%y%%%%,%b%%&%&sj j{1>:PPhj|@P/P|@&G"1& 1& s:1r<>+ s5hRPjPhFPPjPv4>+ s{hrRPjPhFPPCFFFHN;r* t F Fv+vN,0fCFujjP/P{rBj&jFP/P^&G}&G"1>+ r>+r&G&"G & G"1qFPjdRPjFPPF:JtAQVRRPt@Y"zyr|@&!u3^&Gr&G" r|RPQFPjFP+ uZFsyLF>+t?yr8F2s00~PjFPjFP+ uFyF>:&G; u@PNQQQu@Y"wr+ tw1r|@&!u>:s>tt0+ t!tt tP>+t@:::s:sP ws`:rYjjFP,$+1rO~`u 1qF=,uPaF=-t=.u v:JC:s<1s5Pws#Pws :wr=h'RPjPhFPPPvlPaP`PlP1"1J<+>:&G;;P:r-+ t@:˚xr >:&t)h<PFPjPFx>:&uh'RPjPhFPPPvlPaP`PlP:s+ t@:=t<uG+&P4P+&Ph6+v˚ibFPj@H<PF@N@QPhjFPJF=u$P@@PQhjFPJPPPMPv6@6@PPQP6@@+RQQQQQKP>:&u FP9FPDsQRPQRPQ^SjRPQdF u-~FPjRPQRPQRPQdFjPPh'FPPjF@PjaP`PP&G :&G ,:r~FNQNQPRPjhrm+ uShFP*Pv^ShPv P^Sh+P>:&GRhRPjFPjPFPP+&RVRjhPR&@#PPPPjFPvPU젬:rvs+&P4P+&PjJ<ТJ<+s =Q*1s=j; =66 ]ˠzs j]ˠystvs+&P4P+&PjW,+ u6+`P_P~ ++ tP]˚4+]U젒Ds DT:s>=u j]ˠvs+&P4PJu<PjPvFP+ udP6Pjv+ tGHPQPvFP+ u'P6PjFP+ u U욋PjP^Sv+ uPjPjv]<PQPQ&G P+ tP~ĹPjPFPj2+ tPFF=uPFPj2FP?~ċ򤡐FB:B FvJQ2+QFP+>+t=FF^FhFPjvBP2+PFP+ tPFFFQjQNQP+ tPPjPjv+ tPFp8t8h8P+ u6+FP+2~ι2PjPFPj2+ tPPQPQj2+ tP^GPjvj hF*ȵ^p*F^~ uFsM~ tGN F N10V::rA*ЈVF F^F N1F F릊F U젼s F tP]UF tP]U젼sv]U 4]trFFh'FPjdFPF uFF{0FFF^FhFPjvBPd+PFPF uFFFF tNQP}Fv ^ &;sjPPP6PF~ ~uZF^ &GȴN;rCjPQv@P^ &PDPjP^ &FFuaF^ &GȴN;rJjPv&DP^ v@P^ &PEPjP^ &FFuFs0^ &;sjv PP6PFF^ &GȴN;r+ r'FP+ uF<tA<t@ -.^&>+ r kPjFP2P{}hjFP/P^&FVFF^FhFPj^ Sv FP+ uOF^&^&;F sO-.sJFFhRPjv&<^ PF +PFP+ ux^F&^&;F sdhjFP/P^& tEG FFFhFPjv&<^ PF +PFP+ u ^F& (FFF+&(++FjPhRPj-PjPPPjjj-P6PjjjjPjjPFs+-PjPPjjj -P6PhRPjPjPPPFFF;r= ؋RPFPFğ^F<sf&&_ :vNQRPGPQPNQjPJPQP>t$^&&O :v +FwvFFFH;FsF=t= u{Fu+JV¹F؀uF F&P^S66vvhvvvP66FBF&P^S66vvhjvvP66FFFts^SRP>`tF@FRFPFćFFF&P^SQPvvhPPjP6h[^SF&PF^㋇T=XtANrPFPFFr^ćFFN tF&@&P^S6PQvhvjjRPjhXFsgF:v F/FFF޴z߾F޴FjNQQNQPPFFF^SF&@&P.)FvFFsFFF;FvA^RFPFFr^ćFFNtFV»&P^S6vQvhvvjRPjhYFsgF:v F/FFF޴z߾F޴FjNQQNQPPFFFqFFN&P^S6vhvhjQjMPj hZFsjPj P6P^SFF&PnFc-t ,t.tF@FRFPFćFFF&P^SQPvvhPPjP6h[^SF&PFݚ.)FFFF;Fv^RFPFFr^ćFFN u@FV»&P^S6vQvhvvjRPjhXIF=tFN&P^S6vvvhvQjRPjhYFsgF:v F/FFFشzپFشFjNݵQQNQPPFFFqFFN&P^S6vhvhjQjVPj hZFsjPj P6P^SFF&PFFNFAN FvFFFH;FsF=t= u{Fu+JV¹F؀uF F&P^S66vvhvvvP66FBF&P^S66vvhjvvP66FFFt^&F<F1s&Ȱ> ++jPhRPj-PjPPPjjj-P6PFF;vFF;vNFF؊d.;FsF;rFڋFF֋FN+FӉNF;FshFPFćFFPFӴPjjPNQPP6PF0FϸPNӵAQPFPjPFFҀnFFFw<+N0ʈNˆFjvjFPjPFvBFuFF؊d.;Vtc.& $ u+JV FPFćFFF؊b.1VƋȱNҵF䀿c.uʶzuF,FB^Svj hF؀c.~tDFֺ&P^Svj hPFh.FPRR^.PjW\hRPj-PjPPPFֹ&P^Svj hPhvQQ-Q6PFƴBsFH&^&&(HFƴBF؀c.re.rg.s8hFPF FFFt zu(F<sjNҵFFƴBFֹ&7F,NҵFNɵBFֹ&F&F^&&H^Svj hF؊c.svbF؃e. wNFhFPFćFFFֹ&&F܉FފFȴF؃~teFع1 tWv؊BrMHNҵFFֹ&&8uF&^Svj hvBNN땋Fֹ&&8uF&FF؃~tJFع1s;v؊Br1HNҵF^SPj hvBNF밋F t)F܋Fظ e.~ue.F؊c.@tAtF؀c.@u+e.FF~~ F܃n9Fv)F$F؋e.+1Fܹ;vNhFPFćFFFֹ&&F܉FފFȴF؃~teFع1 tWv؊BrMHNҵFFֹ&&8uF&^Svj hvBNN땋Fֹ&&8uF&FF؃~tJFع1s;v؊Br1HNҵF^SPj hvBNF밋F tB)F܋F؀c.@ue.Nރ~t F؃e.F؃e. ^&fPFֹ&X&@FF1s|~uvhFPFćFFPFȴPjjFֹ&P^SFPjhPhQQQQ6PFփ>uFHN;s&<+&P7;Vt&P6r&X5.hFPFFhFPFF ȴFF6hFPFF hFPFFȴFF^ćFFPvvjFֹ&P^SvvhPhFPQQ<+PR+&PWFFtnFt9hFPFćFFFFFFHN;r4<+&P6r&@7;Fr~uFFFFu1sF1sF~vFFFCFFFHN;s1<+&P6r &P7F;s;vFFFF<V+&@7;vjFĴPFŴP@P+&PP^SFĴPFPjFֹ&P^SvĊFPhPhFPQQ<+PR+&PWFփ~wF^&GF^&,:FvF^&*,FFFtF1rhFPFćFFjFĴPFŴPP6P^SFĴPFPjFֹ&P^SvĊFPhPhjQQQ6PFփ~wF^&GF!^&,:FwF^&*,FF1shFPFćFFjFĴPFŴPP6P^SFĴPFPjFֹ&P^SvĊFPhPhPQQQ6PF֋F;sPjj _QPPFT1s&Ȱ>jPhRPj-PjPPPjPP-P6Pjjj jPjjPFs+-PjPPjjj -P6PFNNF;rA؀d.t*c.& $ u+JV FPFćFFPPPjF؍^.-Ƈ-:CƇ- C-F&P^S66hvFh.vPP-P6jFF؊b.0FjFPj FPjPFF++FHN;s<+&@9shuF<+&@:shF<+&@;sAhFPFF<+xF<+&hFPF^ğ^F<s`&&_ :vHQRPbPQPQjPePQP^SPPjF&P^S66vPhFPQQ<+PR+&PWF^&FtYr.r FPj@PFshjYFPF^ğ^F<s`&&_ :vHQRPhPQPQjPkPQP^SPPjF&P^S66vvhPPjQ6PF^&s.rhFPFğ^F<s`&&_ :vHQRPnPQPQjPqPQP^SPPjF&P^S66vvhPPjQ6PF^&t.rhFPFğ^F<s`&&_ :vHQRPtPQPQjPwPQP^SPPjF&P^S66vvhPPjQ6PF^&u.rhFPFğ^F<s`&&_ :vHQRPzPQPQjP}PQP^SPPjF&P^S66vvhPPjQ6PF^&v.rhFPFğ^F<s`&&_ :vHQRPPQPQjPPQP^SPPjF&P^S66vvhPPjQ6PF^&FFF;s؋RXr ZwFFۋFUF=Xr =[w]h,P*Ph,P*P0P/PRPj,Sh,ShCF tPP64+P+PP+ tA>+sB"ʃ s@ ,.RFPF~u+ ~u1Fu+JVu¹FFF;v^؊t:t8みRu'^^u_^&<Ƈ'(FFP^ &7^&<Nv؍((F^P&<X&(^ &m^&<Ƈ'(DFP^&7^&<Nv؍((F^P&<X&(1s%^&?u+&^&;+s ^&^&^&<؊&(&(3(+^&,みRu ^^t ^^u+Ftr+ +FFFF~tYFj6FP,$F t4F= u)#= r ='wFFr<~uLJRF㉇RFPFPFP,.rIQPP..Pj0PaF t>uFH;Fs>uF=t= u~tbFs-^..u#0.u~uLJRF ^0.㉇RFPFPFPFroFF~uQj6FP,$F uF㉇RPFPF~uF+멊Fr0hFPjF u~tLJR++&PP*P+&Ȱ>\+FFFFFVV؉RFPFPFP@+LJR[FPFPFP1s Pjj1PhFPZF tPFF1V;wWP؍1P PjFPF u*~u$LJRXFPFPFPRPF؍1P PjFPF u*~u$LJRXFPFPFPF7,.s FFrPPP..Pj0PaF u}>tvFF;shs+0.u LJRY.^0.uLJRZ^0.㉇RFPFPFPFFTF~tj6FP,$FVV uYPrT_wOFPj@PFsLJR FRFPFPFPVwFF~uQj6FP,$F uF㉇RPFPF~uF+멊Fr0hFPjF u~tLJR++&PP*P+&Ȱ>28^^ u^.^&G "F"Fб Nшb.c.d.i.& $ u+JVR^.PjvњN+ u h.B:l.vѸ,Ph,6h.Ph.s, ,$,e.g.>$,uYh.s!jhvPFPPvvhjvjFPjPF$+tF;l.rPPP..Pj0Pa+ t>uFH^;s0.u<Ƈ z^ڀ0.u<Ƈ!_<ذ! ƇDFPFϴP<Nܵv݋؍FP<XFFrSFj v6d.6l.FF~^&8u@H؍^.^v&"F"FЋވ^ѡHև΋b.FЈc.ƅd.Hƅi.& FЋ$ u+JVRH؍^.PjvњN+ uHƇh.B:l.vѸ,Ph,Hh.PH؊h.s,> ,He.H$,؉e.Hذg.>$,uiHh.s"jhvjFPPvvhjvjFPjPF$+u;jvڍFP,$+VV uPr_w r.+F뾸FFs.t.u.v.+>+ukjvڍFP,$+ uFFPFPF؁~u u.F!~ut.~us.v.F뎊Fr%hFPj+ u~t u.:s1&PP*P&Ȱ>򪠬:s":r-:sh<P'11 18F^Fp~ }fFF~OF^&8t|@H؍^.vF^&"ʈN"ʈNދވ^ߡHև΋b.ވc.p+F@d.s@vA"i.~u~AuF@& Fދ$ u+JVRH؍^.PjvߚN+ uHƇh.B:l.v߸,Ph,Hh.P~@u$,< wu$, ~Au$,<@wu$,@F<r3<w/H؀h.u,> ,He.H$,؉e.Hذg.>$,ui Hh.s"jhvjFPPvvhjvjFPjPF$򪠬:s6RP^.P PjFPP~t@6F[^.~F]h+P*PFPj+Sh+PTP16++F+Sh+PF~u~vbjh|v j-PP6-6-v j-PjP6-6-v j-PPP--FVFFH^;sX㋇--6-6-v j-Pj(P>-t8FvZ6sFFF9Fv>RQ؍1P-P-PFP+ u ~uF뺡<؊F V1r51su>-uF Ƈi<-؈U<-؈-<t<u<Ƈ'-s<Ƈ <Ƈ~ t>-s<Ƈ<Ὰ-؍ 򤡾<-؍ 򤠴-rF>- s F!F--~ʍ{򤠺-FʉFʍNQPFPj.+ uC<v؍ 򤡾<v؍  򤡾<Ƈ >+u<ذ Ft+FFFFFFF,.sIPPP..Pj0PaF t>u+P+HFF^;s`0.u +ÃwFG^0.u+ÃwF.^0.㉇RFPFPFPF떸`F㉇RFPFPFP@+LJR[FPFPFP Pj -Pj|F t=u$LJRXFPFPFP;v+FFF;sk؀0.u/~tVLJRZFPFPFPN-~t'LJRYFPFPFPNFF~uNj6FP,$F~~ u+u%㉿RFPFPFPF~tFj6FP,$F uxF= tw#= r ='wFFr(F㉇RFPFPFP,.rIQPP..Pj0PaF ua>tZFH^;rJ..u0.uF ^0.㉇RFPFPFPFsFF~uQj6FP,$F uF㉇RPFPF~uF+멊Fr0hFPjF u~tLJR++&PP*P+&Ȱ>V+FFFFFVV؉RFPFPFP@+LJR[FPFPFP1s Pjj1PhFPZF tPFF1V;wWP؍1P PjFPF u*~u$LJRXFPFPFPRPF؍1P PjFPF u*~u$LJRXFPFPFPF7FF1V;wWP؍1P PjFPF u*~u$LJRYFPFPFPRPF؍1P PjFPF u>~u8s LJRY LJRFPFPFPF#F~tj6FP,$FVV uYPrT_wOFPj@PFsLJR FRFPFPFPVwFF~uQj6FP,$F uF㉇RPFPF~uF+멊Fr0hFPjF u~tLJR++&PP*P+&Ȱ>4..~̋F^&FH^;r0v+V.._{n^0.u^&Fsōv̿..(hBFPj+ t˸FFF+Nl8NFFF؉F^Fj FP + t6+FP+ tˋF tˊFٴ:Fش:6̿7 7^^R ^V >:&GFFf7PhjL+ tj}L+ t˸F^FFPL+ t˸F^FFPL+ tF>:&GZ&WhC+ t˸6Phhf8Pjx+ tjCP+˸F+>+tvjjPPFP+ tA!tjCP+˃~rjCP:!j |FFvvPP8Ph+jC+ t˸:P:PFPPjP-+ t::r˸+P(P:P(P+n8f:::l8PPl8d:::P:PFPPjP-+ t::m:~ r! ^&?^&O^&O^&Gi^ < < u+JVڊ< ^&^㋇:F:^&GPF 10^&GF10^&W1sv1ro:r!aFt8Fv8Fx8F y8Fz8|8F~8F88p8h8P+ uE6+FP+ up8+Ft::u FNNF~NkvFF[؍^.~F]FPjvvF P^SvFPp+ tvvv^Sv1sv1ro:r!aFt8Fv8F x8F y8Fz8|8~8F88p8h8P+ uX6+FP+ up8>F t::u3vF P^S/+ uF Fu FNNF_v FF[؍^.~F]FPjvF P^Sq+ tvvv ^Sj 1s 1r\s~>:u):PMP6:hjjh}PFVFV:FNHF@F Hv~QN^YHF@:YFVFFvFNHFF @FHv~QN^YFH:@ 1r>+ rFr1sjjvjFP+ t5KjhvjFP+ u0FFFFFFFFvvvj^ Sv Fl:1s1rj `:P  `:P++ u6+FP+ uh:1ss1rl:r!t8v8x8y88z8|8~8N88p8h8P+ t6+FP+ tˡp8˸1sq1rj:rt8v8x8y8Nz8|8~8N88p8h8P+ t6+FP+ tˊF˻8^^GwF:uSvv:P+ u9Ff꣺:6::P*+ u6::P*+ t :xjFjPP:S:P:SP+ uhFvr:F:;Fw :;Fwa:;Fv:N, :F:F:;Fv:N, :F:Fvvvv:P/ + uv^&G:&O:V+VV+VV+ЉVF+F&F&GFF;FuF;Ftl^&_ Svv F~wF;FsF F;FvNFu݋F;FsF F;FvN^&_ Svvj^&_ Svv F+FFF+FFsvvvvHvvvv++ ukF:N:V:^:F rvQRSh+ uXjF@Pvl Pj+jF@Pvjj+ ubjFPv^Svm Pj+ u;jFFPvn Pj+jFFPvjj+ uWPVR^S^+SV+RIF;FrF;Fsvvvvjj++ u>PvNQvvPPPPPK+ u_ ^F&G vjFPFP+ t>FFFF:;FvF :N+ȉN:;FvF :N+ȉN~u ~uF;Fv#~uFFHF1vFF!~uFFHF1vFF:1V+ЉV:1N+ȉNF ;FrF ;Fs_NF ;NvFF)FNF ;NvFF)FFPNQ+F V+R+N F+Ph+ tjFPFP+ ueFFFFF 1FFFFN F;rV;vNF)Fjv vvPP+ tmjv vjv+ uF+FFFV N;wJVjv vj v+ ujv  vjv+ ufNF;Fvjv Pj v+ ut?F+FFFV N;wJVjv vvPP+ uP8F vF FrV; PFFȴN;r3jFPF Q;PF Po Pj+ u4FujFPN QF ȴPNɵQPPd+ uY{s[; PFF*V;rmjFPF R;PF *Pp Pj+ u>Fu4jFPF PF *PF*Pj jd+ u "vrjFPFP+ u徾:~:^P&*GF:P&*GFYX1F uFFH:ȉN1v:FF^&O+FF&O+Fr:PjFP+ u&:;Ft6:6:P6:j+ tF1щVF9Fw:ȉN1v:FFF:;v+ȉNFF1vF:;v+ȉNFvvvvFP/ + uFuPPPPFP/ + uf^&w$e)sY^&_ S^&P&GPj^&GFHF&O FPjFP+ u^&;Fu &G;Ft^&_ Svv  F~w'^&;FvF^&;FsNFu^&G;FvF^&G;FsN^&_ Svvjejvv:vP^&GP:QP+ uvT^&PjFPF u&G PjFPF t^&GfFFFt &+FF^&GȴN;s~t&GV;v V J;sF ^&GFj^&P&GFP:vPFP:QP+^&G;Fvuv jFPF udvjFPF ulj^&F NP&GFPvFV:SQ~:PQ++ u&G PjFPF ucFFFt~t.j^&NPVRF HPV JRPPd+ u!F^&F&GF &GF &G F^ &GȴN;r^N&G FPjFPPjvFFP:vP^ &P:QPPFu jFPFP+ uTFFN+INNFF;(ο:(PPv;PjPq Pj+ u3PPv;PjPr Pj+ u~F;F~~$N}FPPvjPPP+ uҋNF;~%@F;}NPPvjPPP+ uj+A:s::hjFP/P^&!u"RPQRPQFP u@::PjH<F t:ˍFPTP~u3FjjFP,$F u.F=t&=`s!>:u@9Fs 8:t@ :F::n^ Sv ^F uy=F:rys6>=u/hA^GPjFPF uĺK^&Gi&Wk:s>=tzs6>=u/h@^GPjFPF uK^&Gi&WkjFPFPF;sp ujjFHP^GPjPF ujjFHPjjF ujjFHPjjF ujj8FHPjjF th;rFPFPd$F=uDF^ShFPFFF=ujPFHPjjF tNIF uBvvFPns FF===tjPFHPjjF tvvFPn"Fs?^ShFPFFFFsn^&;u+JVtv^&@k& @iuF2L<Sv^@iP$s#v^&@iFF~t}F tHtC~PjjFHPFPjPF ujPNIQPjPF uR<Sv^@iP$sVv^&@iFFP,F uZ6+^GGP^&GFP~ F=u zsFF&;~ u;v^@iP; FL=u1PPRP8>DuRPL<S}>=uPPRP8>=uPPRP8:rj=<t<u_JP uP;FFF t=4@GP^GP^&GPu4^ &S^&7^S81^ &&_0^& ^& LL<}^YFrF Ft^&GFFFF we^&Hi tM^&xk& xiu@^&HiL<&HiZ&PkF s#^pL+&;&G;&wGPP;&O&6FY;&G&;&G ;&w GPP;&O &6FY;&G";&G(;&w(G$PP;&O(&$^.򤡾;&G*<;&G0;&w0G,PP;&O0&,;&G6<;&G<;&w;tE;&7;GPP6;& ;&^Y;&;&G;&G&W;&G;>:&G'Z&W)>:&G+,0>:&+,umjj;P/+ tˡ; ;tM\s;>:&O';;>:&G';;;Sh, r ;&; t;&GJ<&G +&G &G 1&=&O;&WR;&G>+&wP*+ tˡ;;&OQ&O^>>+t/F+HN;r&X ^ڌF&WFu;&G&w P*+ tˡ;;&OQ&O ^>>t/FHN;r&X ^ڌF&WFu;&G";&O$Q&O(^^.;&G*;&O,Q&O0^;&G6;&O8Q&O<^&(;&G2&G41&G51&'1&(&*&&1&G@:&w@j:P+ t6::P*P;;&OB>::6::P*P;;&OF>::;wJ;]F;=< F;&;&x& F;&$\X<\<L;&ąFҌFԋF+ V+ ‰F^&HiNҌF)FԋvF^&@iZ&PkFt^^&FFFtR;N^Y У;;;>:&GZ&W ;Pj]=<Pj ;PPjFPFP+ um=t<u,F &PvvPRQP?㋇@P ++ uTGPPFP/+ u9^GP^&P>: P>:& P&P+ t >:&G>:&G^Sv>: P>:& P&PjK<P+;P;P><P=<P6;F+ t!Pj2|+h<++>:&Gr>:&G>:&G$F u$;P;P><P=<P6;F1PP>: P>:& P&PF>:&9GuP>:&G tP~tj2|F>:&GFˠJd< w&i<~ dCtG=PP=6:==C===P1F t =tPU츞=P2+]U젒DsPjj=P/= t]ˡ==&9tu(C=j 6=j=Pj=P= t]˸=]PP&G ȴP&G ȴP$+ tj+ th+ t_\^F&G1&W‰F&G1&FvP$+ tvvPP$+ t=:=RPPhDP PQPFP+ t˃~uˍF^RPFP=P+ t=^&+N::P+ uTFFrn6:FP+ u4^& 6u,h=Pj+ uÃ>=tf+ t^&G u^& u=F닃>= uc}rs{s==P^ So++ u^ &F=t^>=tI=FFPFPd$P=F=s<uF ~uF=s ~uFvvFP1rFsF;+u ^ &+9Ft<&PjF+&Ph6+^&=P2+6:FP,+====P1P=6~u ^ &'vvFPns^:^ &=|=Z>=`uFPFPd$PvvPP$+ uʊF svvFPns%&G ,FF;=tF=^&J==t.jP&G ,Pjj+ u =QvvFP1s r=t<tn ^&H^&;s&&xu/&@ ؊d.F;sB;Ȱs@"ˆFFFs\^&&PFPFPFPFPNF ;w"N;vNF ;w N;v ^&t9Us >=u~ s)F ^&^&;?v@み@"]UsC=s<&G ȴ;F w+&G ȴ;F sF F 1u>=u= F 1^&]rˍFPFPd$PvvPP$PU^ Sv ^S+ t=Zt=btP] FFFPv ^S+ t=Zt=btPՍFP^ So+ t Fvr":r+&Ph==<tA$FNvs_t<uW=PjFPFF+&P4P+&Ph6+Fs9??Kみ@r?9?s >?u?j6?jP6+FPFP_=^Sv=P+= t:=t<u+&Ph6+s==t<uFs-6=@ "=<t<t<uFs 6=v? ~ tJ wv;v>uv;vw@66++&&@ ؊d.;sy+;t)+̀~u{Ju>w 4+66++&&@ ؊d.;s+;t+͡+~ujN~u6j F+ t>+;u I;vBV++H;+u!F8FuP~ uNj F+9Ft<&PjF+&Ph6+FFFFF+F&PFPFPFPFPFFȈFFFȈFFHN;s&PFPFPFPFPNFȲ*ʈNNN*ʈNN;+tuX^. - { F:FsJF8Fw8FsF8Fw8FsF:FvF:Fs F;F~F;F~JF:FrF8Fw8FsF8Fw8FsF:FvF:Fs F;FKF;FKF:FvNF8Fw8FsF8Fw8FsF:FvF:FsF;FsFNF;Fs_FTF:FvRF8Fw8FsF8Fw8FsF:FvF:FsF;Fs FFFF;Fs FFFFt>~uFFU8FuNs$Fs hP<~ uFs$Fs jj<~u??;?s+?;?u?>s JP 4P~u1>?t?>s JP 4P~u$Fs>?t??O~u$Fs?@?Ov?~ u}=<t<uf?;?u 4P\? ;?w?? ?;v:?+??>s>=u JP >=u$~uQ>?u 4P=? +|?? }&?>s>=u  JP~Du=Т=jP8+ tP]Fsi>?tFFN?;t?み@r????み@r ????㊏@J=?@?9?r?み@r???み@r?U}rr= :6=:::]˸=:::]jjFP/F ukFFFHN;r^^&^F&ON&wX6F9FsFvvFFPXPvF uqFuF@FN^&W +;Vs&O +ȉNFFFFHN;rr^&^F&^&?u&G0vFFPFFP^Sv]F t7 FuFvvFFPjvF uՋv^&FFvFFPFFPjvF u~u^&G +FFFF;Fs^&G8:^&GF@BDFQV&:r*^&PPu ƆPvFFPFFP8PF<^&GvFFPFFPjvF ugvvFFPjvFF t=d;u؋F uэLP^ SoF t^ &?uv^SvF ttx^ &< t< t< uF@F9FuT=^ &?u~u FHF9N4^ &<t":t< t< t<t<t <t<t:u 4FȲPN^&?uA&O&w ~&}LY^&G&G^&O&wPL^&?u&Gvvv PPv ^O&w @FFO&GFv PPFjjjjOjPPdF uzjjjNPjVPjF uqjj j^SvF uW ȍ~PjPFPj F u/PjPWPjF uPjPjjF urFFs~FPhFPFF~uY ~PFjjjFPjPqPjFF< sjjPFPjPF uqFF녚4F ȍ~PjPFPj F u4PjPrPjF uPjPjjF uPPPPPF tPDshwhRPj-PjPFPF tPPPP-PvF tPF -PF<sFQQP-PjPF tPPPNQPjPF tPFDshsDsh{hRPj-PjPPF tPPPP-P6F tPF -P?@N;rDPPQ-PjPF tPPPNQPjPF tPFEh$RPj-PjPPF tPPPP-P6F tPPAQP^GP^&PF tPjvFP^ SvF tPjvFPFPvF tP v RPj>PhFPF tPv v>Pvv8?>QP6>F tP?Fみ@s%jv PjvF tPF%jv F@PjvF tPFH>F >F>??;?s?;?v ???+?;r9?u ;?r?;?wա?;?ujFPFPF tPjjFPPjPF tPjPNQPjPF tPh:RPj-PjPPF tPPjP-P6F tPF> D<t@<t<RPPNQNQPF tPFPDPoF빀>DuDDFFF ^&^&;FweFFNF;s1PF^ ^&P&x&@&H;u;vFrF&I&;@u&;Ht@ЈFsF^&F^P&+Ff^ ^Vp_^ 9^Y^&^ &&P^&'^ &x&x딋F9FssNsl^ 0~NFFPF+Ff^ ^V0_^ y^NNOOYF^ 8vNFsFF^&;FwFF^ &P&x&&xFNRᖇF&;xu&;@ _uF@FF&&P&&Q맋F u^&)FNQ^P&+FHf^ _^p^ y^YFF9Fr<^&^ &&PF^&^ &x&xFuF ȤFF=w2B@&@&PFB@&8&xFuƠDr+FFF\FFFFF F1sD8:tP FP  FPF~tj\PhFPL6+FPPF tP`bp@>r@+B@&O& B@&G &GFF=w2<@&@&PF<@&8&xFuƸFt@v@<@&&PF<@&@&PFF@HN;rb@&@ uHF&P&x<@&&xFPF@^&&P<@&H&PFFuFx@z@<@&@&Pp@r@+x@z@PFR_X<@&&x<@GPvFPFt@v@B@&&PFB@&@&PFF@HN;s @&@ u+&P u;t&pj8@Sj F tF8@&W&B@&&xF8@&W&@&+P&x&&H+PFXB@&@&HSFPF@^&P&xB@&&xFPF@^&&PB@&H&PFFtFx@z@B@&@&Pp@r@+x@z@PFR_XB@&&xB@GPvFP^=??@@>DuhhP|@P/F t˸+P+PF tˡ~@|@&O*NF+ s u>+r^&F @@x1s1r :+:+jh6DjFPF tvv6DjCPjDF t˻C|@~@GFȸУ @@F?|@&G?DDD& Ƀ>+ s@"Q\Y"sa\sD6D/|@& r6D؊i.D |@&G$D|@&$t@D&$t@>+ sA"DD DuhDP*F t˂>Duj j,@P/F uˡC;CvPCP*F tˡCC>CCC,@.@|@& r>+ r9jj 6DjFPF uvv6DjCS6CFDrDs|@&G@@Fȋ.D;v> t*DSQ+Fvȸ*DP*F tˋFȣ.Dȸ>*D*D<@>@B@D@DrDsFFCCFFĉFƋFƃ0vPF tCFƉ@C4@&G;CsC4@&G;CvC4@&G&9G vNF&W*D&P&x4@&G &+GPFR_X*D&&xF~tFtNCt@v@Cx@z@|@&G F&G @1 tF‹Fºp@r@>Dujj(@P/F tvˡC;CvPCP*F tˡCC>CCC(@*@jj6DjFPF uvv6DjCS6CF6DFPjFP F tˋFtDt?t:h<RPj-PjPPF tPj-P64~t@Ds6DFPj*FP F tˡN@ L@ta\s H@SjFDrH@SL@N@ )H@SL@N@ @@׋F@P+FDrgF@N @V@@^F@F@F?F?F~p@>r@F~t@>v@F~x@>z@@@HLF@@@@F@NڋV܉p@r@NދVt@v@NVx@z@N"DDfFL@N@>N@u>L@vj DrL@N@ #L@N@ @@׋F@PH@P*F t6DH@S6L@FP F tˠDrJ@H@&O(P@@У@@B@D@<@>@@@@@F&@FYQ8@:@8@ YQ<@>@<@@YB@D@DskУvJxJzJ|JVH@G@@6@H@@@@6 @H@@<@>@6@@H@@B@D@6F@H@@@@F;?vCFNF NMFF NF>DtvP4@QPF uDsvj8@Sj F u>Cu-4@GPDP4@&GPu F+CCУ0@2@jv0@P/Fj TF0@ tH~uB&wNFF0@&MF&OOwPFF0@&GOFjd TF#1rv6DjDPj* F u~D4@6@Dsv6Dj8@Sj F uP>CuX4@GPDP4@&GPu5F+CC)v6DjDPj* F tD4@6@v6DjDPh F uGD0@2@wNF0@&MF&OOwPFF0@&GOF У0@2@Dr+FFFF0DFFFXFF F1sD8:tP FP  FPF~tv0DPjXFPL6+FPPF tP0DP@R@Dr6DH@S6L@FP F uދF%FsH@&?uFFFf@@@@H@&?u؎&uУ @"@+@&G+?@@ @"@؎&uУ$@&@ @&G+?@@$@&@@G=`@b@@G~\H@&?uYУ @"@@&u $@&@@&GA@$@&@@G?`@b@@d@f@&@ $@uУl@n@h@j@$@Gh@j@$@G+l@n@~+t DsO8@&u:F@HN;r\@&x u&P;Vu&FFu28@&G %@&G!sjjT@&G@&G#FFvvvDShFPFP/F ufDFF&FF0@2@&wNFF0@&MF&OOwPFF0@&GOF~tУ0@2@FF~u7&@ $@uУT@V@\@^@$@GT@V@$@G+~t`@G FF&O&W&&WEE&&WFV`@_'^F6@&L &| +^&+&E>EET@V@d@&G+EE\@^@.F `@T@V@F d@\@^@^ NF'^F N1F u ^?uuF0^7^ ^^;Ft!~tF N1V 1F^ NFF;^F VN~dFV u^?u ~u~u%FV0^7^ ^^;Ft>~u~t1F VN~d~ vFV dFVm FFw$F1F؊^vfFuFFFwZFV dF؊^v~uFs ^v FFV FV Fu>=tjE tP)=@C}DsRFF@HN;r>?CQ@&P_;s;VtVCLJ@BCFuCLJ@C@CLJ@C?F?HN;rPQQQP8FuٸУEEEEEEEE???FDC=F;uS$F;u7?@E t?み@v?@6?j}F$FDrDsFFCCFFF=w^PF uCCF@CDr4Dr-4@&G;CsC4@&G;CvC ~uFuh~tf>DuhTjFP/PBjhT6DjFPPvv6Dj%FPj(P%FF^DrDsp@r@+x@z@t@v@|@&G +CCףEEEERPFPjFPvBKh#jvjF+QvNQ@Pj8%F+QvNQ@Pj8j0v^GP^&Pj8DsEEEEEEEE ~uPvQQP~tNEE?BjFPj"FPF u9FvFj0vFPvj8?BjFPj FPF u9FvFjvFPvj8F@HN;r2?዗B@&;Pu&@&PEEFuáEERPFPjFPvBK+PvFPFVj8%F+QvNQ@Pj8EEEEEEEE~tXDrhePvP6E6EFPjFPvBK+PvFPFVj86E6EFPjFPvBK%+PvFPFVj8hzj0vj6E6EFPjFPvBKjDuhjFP/F^&F޹@&@&PEEF޹@&@&PEEFEEEE8@&G&WEEEE+FFFFP@FFFXFF F1sD::tP FP  FPF~tvP@SjXFPL6+FPPF tPP@&G&WEE&G &WEEDr&@ $@th@&&WEEEE@&G &W EE`@&O&&&ףEE&G &W&G'&W)EE&@ $@tuh@&&WEE`4@&G&+GEE&G &+GEE&Or&O &;O u&;Ot4@&G &+G&O &+O+EEEEEEE>EE>EDrRPFPj6E6EFPjFPvBK+PvFPFVj8DrEERPFPj6E6EFPjFPvBK%+PvFPFVj8Ds Fs2!Ds (@v&@ ,@v&th?j&vjDrHDrA2@ 0@t84@&t4MFNF>Qu+JVX+HF#;w?@2@ 0@tOE EtFMFNF>Qu+JVX+HF#;vNj0v^OFPvj8DrDr+FFFFFFFF F1sD::tP FP  FPE>EtjPhFPL6+PPF tPFVFVFVFp@r@FVF<@&&x t&&P)FVFՠDrFFFF<@&&x t&&PFVF@$@&@$@<@^;u$:t8$@Gh@j@$@&u&G uh@&&WFV$@A롋FVt>Du+hjFP/Pv~D9jh6DjFPPvv6DjFPj0PF+FFVFVU6DCP=DE tP]ˠDrDsJJ6DJP]:s1t tpSPDP E tVˠ1s 1s1s1r D*>Dt >Du:D6D؋j.CjFPFPPvr7:r0+&PvvPRQPPF?DE tˠDrDrDsJJUHE t:sP6DJP]6E]DC=HF tPˡp@r@FF=F?HN;rPQQQP8Fu@CDr @CCLJ@C}DsCLJ@CCLJ@C@CLJ@C????F؁@v?F;uJ;u7?@F t?み@v?@6?U h}F0~tJdF h7RPj=PjOFPF tPF=Dsv=PB@p@r@FVFFB@&x& 8tIp@r@&+@&PFFN~+FFFF&+&PFVF렋FؿFFFVFF~tJdF h"RPj=PjOFPF tPF=Dsv=P<@SFFFF<@&x& 8tr@+FF~tJdF 򪠏Ds)p@r@+x@z@t@v@FFFGEt@v@FFУFGp@>r@x@6z@+G>GG6G G Gh#RPj=PjOFPF t#&~t,JdF +FFFP@FFFXFF F"F1sD;:t P FP  FPF~tjP@SjXFPLF!6+FPPF tP~u3P@&G&W t#&G&WFFFGhpRPj=PjOFPF tPF=v=a~uPvQQP8b~u^FFwNp@r@NYdRPFPjFP^PvFPjj8FuDrDs@&?SAuv F JdFF4@&G&;G u&+GFۉV&GL4@&G&+GFۉV&GF߉VjFPFP 4@&G&+G FۉV&G F߉VjFPFP v4@GPFP ȘPv^ OQ^ &QP8hRPjFPjPFPF tPhRPjYPjPFPF tPhRPj PjPFPF tPhRPjPjPFPF tPhRPjiPjPFPF tPFF?vF>FYdRP^SFPq s^Ft*sF PvviPF Pvv=FsF Pvv #F PvvYF PvvBPjj8FtP FF^&&x tGF>FV N&H&P;u;r!&&P;Vu;N r^J^F롰 ȪF JdFDrDrF;Cv-džd@Hd;r:@&P;VuF&H&PFFduF;Ct+FFFlFFFdF F"F1sD;:t P FP  FPfftjlPhdPL6+hPPF tPxz|~N~YdPFR_XFF-P@&G&WPFR_XFFFظЉFFFJhdžd@Hd;r@&P;VuS&x& 8tJ&@ s{s;d@&x ujjd@PRP du$@ tj؍OQ$@G+P džddw/j `@Pd d@P du`@w'W T] [u3d@&G+t(@&G &W +WY`@&G&W[]jWPd@G!P j`@G4Pd@G,P U젎DsFF^ &O&WFF&&WFF&G u FƇJFr]d^ &&W tZ&G& GtPF&&WFF&O&WFF^&G t FƇJFs FJF] U J@~JP@&G&W RPhJj@hJ~JJ~JƇJK~JhGRPj-PjPPJ tP~JJ-~J~JP@&W&WR؍JQ@+QhJ~JJ~JƇJK@~JJ-~J~JP@&W$&&WR؍JQ@+QhJ~JJ~JƇJK@~JjvJQPj8 J@~JP@&wF&wDhJj@hJJ~JhGRPj-PjPPJ tP~JJ-~J~JP@&wJ&wH؍JQ@+QhJ~JJ~JjHvJQPj8 J@~JP@&G &W"RPhJj@hJ~JJ~JƇJK~JhGRPj-PjPPJ tP~JJ-~J~JP@&W&WR؍JQ@+QhJ~JJ~JƇJK@~JjNAQJQPj8 J@P@&w>&wCtGvJxJ t<P@&G(&W*+vJxJRPhJj@hJjBFPJP6Jj8P@&G(&W*vJxJ&G0&W2 dRPhJj@hJhuRPj-PjPPJ tPJJ-J@JjNQJQPj8>Ct zJ|J uP@&G0&W2;|Ju;zJszJ|JP@&G0&W2+zJ|J dRPhJj@hJJJ-J@JjBNQJQPj8P@&G0&W2zJ|J]??み@u >=t???㋇@FjFPFPF tPFFЃN;rIjjQPPF tPjPvPPF tPFu=УvJxJzJ|JDC=Dr~tFFwJ:RPj-PjPPF tPPv-Q6P8Fu??Bj*Pj2FPF ujP*QvP8??Bj\PjFPF ujj\Pvj8F@HN;s??዗B@&;PuwT@V@@&x ujjjUF@&x ujjj8F@&x ujjjF@&x u jjjFtRhvRPj-PjPPF tPPj-Q6P8FFwN2RPj-PjPPF tPPN Q-Q6P8FuhxRPj-PjPPF tPj*j -P6j8hyRPj-PjPPF tPj*j -P6j8C t~ 1F uFFԉFʌ^FhtFPj-PjPPF tPj*FP-P6j8j*F P-P6j8+FFFP@FFFXFF F1sD;:t P FP  FPF~tjP@SjXFPL6+FPPF tPj ˃~sDrDsFv䚢F t4@GPRDr DrFFwJRPj-PjPPF tPPv-Q6P8FuDrF;CwhlRPj-PjPPF tPj*j-P6j8 FFwO2RPj-PjPPF tPPNAQ-Q6P8FuhxRPj-PjPPF tPj*j-P6j8hyRPj-PjPPF tPj*j-P6j8C tt 1F uFFԉFʌ^FhtFPj-PjPPF tPj*j-P6j8j*j-P6j8WFFwJHRPj-PjPPF tPPv-Q6P8Fu2@ 0@t]MFtVFҋ@+;rVjPNFQvP8FFҋ@+;rVjjFPvj8hIjPPhIjjjFCP|PjFPkjj|Pvj8} ?4@&G!shM4@&!tDrhLhKRPj-PjPPF tP}-|DrDs4@&GsIh_RPj-PjPPF tP|}-|4@&GsIh`RPj-PjPPF tP|}-|jj}P|Pj8DrDrЉFF։V؉FމV8@&G&WFVF;@r @&P;Vt&P tt&@&PFVF@T@V@@&x u&@&PFމVjjjF@&x u0&H&PNV&&PNV&@ FjjjcF@&x u#&@ t &&PF։Vjjj+F@&x ujjj F@&x ujjj F@&x uLhkRPj-PjPPF tPj(j-P6j8jj9jF@&x uLhgRPj-PjPPF tPj(j-P6j8jj9j#F@&x uLhhRPj-PjPPF tPj(j-P6j8jj9jF@&x uLhjRPj-PjPPF tPj(j -P6j8jj9j aF@&x tIhiRPj-PjPPF tPj(j -P6j8jj9j FFVFV8@&G&W+FVFV‹~ ~t)FVF FttFT@V@jjj ]DsV@&G &W FV&@ $@th@&&WFVFV`@&G&W&&WFVFV YddFVRP|Pj@FPvN|~҈|Ƃ|.ƃ}Kjj|PWj8DrMjjjjjj&@ $@t hjjhjj jjj jjj 4@&G&+GFVFV YddFVRP|Pj@FPvN|~҈|Ƃ|.ƃ}Kjj|PWj84@&Gs &w&wO4@&G&9G u &wPjj:4@&w&wjj4@&w &w jj4@&w&w jj} ?ƆzDrDs3(@v&@t.h?RPj-PjPPF u;?,@ tQ؋v&tFh?RPj-PjPPF tP}-|ƆzzsAh>RPj-PjPPF tP}-|,@v&tIh@RPj-PjPPF tP|}-|,@v&tIhARPj-PjPPF tP|}-|DrDs[(@v&utIhBRPj-PjPPF tP|}-|DrDsjj jj}P|Pj8Dr{Drt4@&wjjj 4@&wjjj 4@&wjjj 4@&w jjj 4@&w jjj4@&wjjjˠDsGFԉF@HN;r@@&x uF֋V&9Pu&9u tFFu $@&GF$@ t &?RAt Dr~whTRPj-PjPPF tPjj-P6j8FhNRPj-PjPPF tP-#u+JVFFwD.FԹ 10{FԹ 10{{^與-FFuFPj-P6j8~uhThUjjj |@F,@v&uhCRQP-PjPPF tPv荺}-FhGRPj-PjPPF tPvv⍺}-FFF,@v&uhDRPj-PjPPF tPv荺}-FhGRPj-PjPPF tPvv⍺}-FFF,@v& uhERPj-PjPPF tPv荺}-FhGRPj-PjPPF tPvv⍺}-FFF,@v&@uhFRPj-PjPPF tPv荺}-FhGRPj-PjPPF tPvv⍺}-FFFF;v+F舆|jj}P|Pj8>+ rI>+rBhIRPj-PjPPF tP|-F),@6?^Fv&P|PjFPkjj|Pvj8@  @t"F @F@FNV؎&ЉFVF t*&w|PjFPkjj|Pvj8Ds#8@&t=8@&tu8@&u}m@ tc&G1thPW@&G1@thSF@&G1 u2@&G1thQ)+ ;w;u>+r@&G1thRhOjjjDskR@ P@tbF;CvY |@P@&G &WRP|Pj@FPvƂ|Kj9j|PFVj8jУzJ|JvJxJ??;?r??ˡ?@??㋇@FFF=t׊NrPF=t=#u3??@;?r?????㋇@FFȌDrNv jT@&&W YddFVT@&G&WDT@&G&W YddFVT@&&WFVF Fu4 tvvtPjFPFuttƆt0FvNt~tƂt.ƃuK|lvvP~oFDsJuJ@1J6JFPPJ:>JuJJFVJJFPF t .ttFs [OrJ& wJ_4^F&t^&u OJF~u.FRPjvvOPjJP PJo~.ukh,#RPjFPjFPPFFFJ;vNƊNƵvǿOFƴFFOQP6JvjFmOnOOmOFNJ;w+F FJF^&G;FsF&GF^&GJ;rj+P&GȴPjvPF tkNV;Ju;JtYj^&O+Q&OɵQOQPPjNF^&W+R&WʶRVRQP F'FFFwCF1v0vB~u :t+ƉFFN1V 1FFuF;FvFNF ȋV;v+ЉV#~F+r^ ~ 9F F PF>+v*FF;+s&&xuFFۊFs4~@FFPFFFF F FFFPj@H<+ tPhRPj-PjPP+ tP+&Pj,jh-P6PFFwRtRPj-PjPP+ tPPPF@P-P6PFuFs jjjh jjjhFPP~w/^·.FFF FFjjjvFPPFPFPjjjFPFPPFPFPjjjFPFPPFPFδPjjjFPFPPFPFʹPjjjFPFPPF:FujjjhTFPPFPFPjjj FPFPPFPvjjj FPFPPFPFϴPjjj FPFPPFPvjjj FPFPjjjhUFPPFPFPjjjFPFPPFPvjjjFPFPPFs jjjhT jjjhUFPPFP&G PjjjFPFPP$DFhRQP-PjPP+ tP+&Pj+t+&P4F+f^&FFFM^&xF t?OSfP++OSFP++OSF&P++ FFsF tH^ &8 uFFFFs#~t^ &? uGF F NFփ~tv}L+ u>F u^ '&8u-WV F HFu+JVt(Z ~ Nu+JVuFF^ &?@u`GPFHPOPh F+ u+>+tOPFP-+w>+u؍FPL+ t Fr~ *Nu+J;u~ ?Nu+JtZ^ SvRPh ;+ u+>+uQRPFPn +w>+uۍFPL+ tuF FFFFFPL+ uUF9Fv^ HN F @)FFFFrN~t^ &? uGF F NFӸ jdFP,+ t^SjdjL+ tj}L+ th'-PjPP+ t˸-F^FFPL+ t˸F^FFPL+ t˸F^FPL+ t>:GAFF>:&G@FjFPL+ t>:G`FF>:&G_FjFPL+ t˸F^FjFPL+ t˸F^FjFPL+"^ &O^&uRPj+ uN^GP^&wGGPFPRPRP^P^POP+-F+ tjF^&GF^&ćFFFF Ftt^&;FvgF^&G"+V;|;vOu1#P@PQu^ &FsƇOF^&FFF^ & u&POP*+ u^ &POP*+ t^ &&Ȱ>OO&GFFFFOF&9Gs8vHNF+~u+JV^KOr^SPRFP+ tFH;FuF&O&FF&O&F&FO&HFFO&@Z&PvN^*&8uBFRXO&@vN^&8*tFsNF&FO&@F9FsFFF+~u+JVBVFtI+F^&^ &^&'PFP*+ tF^ &HN;r]^&Q&^^O&P_&xFO&@NOO&Z&PFu^&ćFFFFF Ft~^Oub^&7F&O@ P*+ t)^GP^&wF&O&X S^&7O@P ,FF^&FFz^ &F+&PjPvh^GP^&GP+ uiPPj^ &7OS^&7vFP^G P^&GP+ u F<t<u-+&P4F+ u.F u'"~ߛt@KFFHN;s+^&8~tPv&4^ PFP ,s^F&d^vPv&4^ PFP ,s^F&^vPv&4^ PFP ,s^F&U^vPv&4^ PFP ,s^F&"#P^vP"Pu "F^v&^&7^ &^&^&;F sFtP^SPt+&&H N&xu8 u1s~ ^&~ ^&:s,JVt#V%V&V'V7>Vt#V%V &V'V#V\%V &V'VЉ(V*V,V.V0V1V2V>Vu>Vt 1V2V@4V6V8V~ rHV:VVuut Vt V@V8Vt?V>V@V!>Vt>V8Vt>V>HVr?BVCVVDV%VFV0V utCVHV;s;t>JVr>VsC>Vu9>0Vu/>Vu%FPFPF tF0VF1VLV?Vr PV>0Vt PV@PV>Vt>0VuRVRVSV>Vu BVrMVNVOVMVNVOVF ;s;t~rBV>HVrUV@9FwFV~NFZVPF u6ZV^Sv<j&jFP/F u ^&G-hjFP/F u^&G < sA<v@"FFF FtFPjF t@^&F V>Vu>~Vu~VPP~u<~V&G& GujF P,F u|F~V&_^ F &FF #t+ȉNF V F V )NF ~V&GZ&WF^ &F FN;s^ S+P F uHF^ &GF^ &GFF9Fr$^ X^F&^&GFuԸV>Vu>~Vu~VPP~V&_^F&G;F s FP^Sv ؎F@P>Vu>~Vu~VPP~V&_^F&G;Fs 2Vv^@zV|V^&O&zV&GU젂Vr ~V&_S^SzVS]^&v ^ &Gv&L@^ &;vS&O+P0F ud^&O&7^ &y^Y^&G^ &w&^ &G^&^&G@^&G^ &Gv&D@^ &G ^&v ^&&G^ &;Gthj ^ &G@v&L^ &;vS&wF+PiF u^^&O&7^ &y^Y^&G^ &w&^&G@v&D^&G^ &G@v&D^ &G 9FsF^&&+GFSv+FF9Fw^SF+FPF%FPvFPF=t5v^&%FN;tFPQvP FF^&F^&OANFF;Fs"^&@&PFVFFFFFFF;FwFFF;Fs;^&@&PFVF9Fv9Fw~t FFFFF뽋v^&@&PFVFN;s7N0^~9^YFFvFV^&@&PFFFF@F^&GFF;Fs@^&@&PFV~uFFvFV^&@&PF^&+FFN@;vjvFPF=tCv蚟vF#^;Vu&#+ЉVFNPQjFLNFȃ#ʉN^QN+#QF uFP+F%Y+ȉNFF^&FU^&&GFPF tF&PPFP/F uV~ rO^&Gs ^&8^&Gs^&Gs ^&^&s^&mPPFP/F u%^&G F<uHPPFP,$F u{Fu+JVt4ڋ^&$~r ^&~ s~u^&^&?vGP^&G ^&G ]U+Zr tH]j&j^S/ u ^& +ZrHU3 &L&;Wt]U\#tH3&GtH]U u. t!;v 33@33.P 3 ҃+@sH]U؋]UN~F V u. t!;v 33@33.P 3 ҃+@sH]UN~F V ؋] 6r"^&&W&GV&G;F s Wv VX^F&F&GFFF;FsN ;NvV&@FFڋF;Fr ,Vv@^&Z&WSV&_[&GU|s]V&G@] ar V&G;FsGvVX^F&F&GFFF;FsV&@FFFU>VuVP u>VtV&GVV>Vu]ð]UVVZУVVVV] >VtF1 u~uDRPjFPF u ^&GZУVVv^ SvRPVP#F>VtvXPVPFVvPVPjF uiFH;VsBFFVVVVVv^ SvRPVP#F>Vt{VVVV;Vu;VrV^ 6V&^&>Vu'^SVP8F>VuZ ZVV^&? u& VZ>VtV&F;Vu;Vs)VVHV v^Sv^ Sv F PhjtF uU^&FV~u~wov^SvFPFw|~t~ uFV^&_F:Zu!Zsv^SvFPF u5F< t0*< w#FFV YdNY v N^& VtF+FFF+FVF;FtFFHN;r"v^Sv^&0F ugFuӊFsv^Svj F ucNV>V;Vu;Vv)vRQ F u5vjVPj F uv^Sv6V6VFP$FFF;vPV;vH VV>VV>Vv^SPWRVP#F>VtF )V)FFVV6VVV+lj^FNvvVPhVQFP#F~tFFVFVvXQhRPFP#FFFHN;r"v^Sh^&0nF u6FuӋF FtF9Fv~~ ~tvv^ShV6F udFFVFV uv^ShF u6FV䣐VVNVv^SvRPFP# ~uXVFFVFVvXQhRPFP#FF# F'F9Fs 1F~uF FF t-ȋF10vBF1VF 1Fv^Sv^ SvFPvy tFHV;ruNV>V;Vu;Vvv RQ F urFFVZs&v ^SPV>V+WQVP$F.v ^Sv6V6VVP$FFVVV>VuFVF^6V&V NV>V;Vu;Vvv RQ F ufVV>V;Vu;Vt+NVv jFPj F u*FVVVv ^Sv6V6VFP$ZFF>ZuZFZP(F t0Z~t!\r:j jjPjNF1j jZP/F uZ&G&;Gw&G^ &Z&G ^ &^&Z&G&W;Zu;ZvFZ&G& GuFFPF tZr"6ZFPF u ~ZtFk'ZZ&G&W;Zu;Zv;Vu;Fw >ZuZF t\sMj jjZPjNF uj jjZPjNF uj jjZPjNF u)ZZ&GZZ&GZZZ&G&WZ&G&;Gw&G^ &Z&G ^ &^&ZZZZZ&u&uj'dZ&G< wFF~uNZFZwZNFFZFvvZ&w&w;Vu;Fw@ZNV&9Wu&9OwA rZ{vƄZ}ZZZ6Z&G&Z>ZZZZZZZZZFZZ\sj jjZPjNF u$ZZZ&G&WZPF tZFsFqFZZ&G&GFFV ;Vu;FsKF;FrFFFF+FFV +V+VV׋YdNU^ S^S]FFFFFPDFFFFPFFFF^FFPFuFF u)vFPFF^&F^ &UFZ]F%P2FF%P"FF%PFFVU~u~uF]FPDF urFFFFNNNNFFMFFFF6ZFP F u*vFPF u^& Mt^&GFPF u v^S$ v~Fv FPjRPQRPQRPQFF@vWv FPPNQPNQNAQNQPFFvBv FPFVNQQPQFPQFFPF uvvvb FPF u vvFFFFFsFFvRPQ^SjRPQRPQFFPF u(v^Sv^Sv^Sv ^Sv,>^[u =F uFFPF tF= r= rF= t = t= t\s*v^Sv^Sv^Sv ^SvvZE\s'^Sv^Sv^Sv ^Svv*jvv^Sv^Sv^Sv ^Sv\F hFPjF up~tjE\s-hv^Sv^Sv^Sv ^Sv\(v^Sv^Sv^Sv ^SvF~uCF!>ZtF tt !tF*~ v~v~v ~vv~ڋNFv~ՋNF~ r'vRPQRPQE[Pj@[PjF~tFF9FvJt@[FF t ȾE[~F t ȍvڿE[~u~tI~ r)vE[Pv@[PvRPQRPQFvE[P@[P4F u,FPDF umFڈF۰F܈F݋FFދF؉FF FFFFFFFFFFFFFFF FFFFFFFPF u,v؍FPF u^&G ;F t^&GF~ uN~uNP~uN F ZPj@F t˸<[P>[PF t˃><[ u>>[s><[ v][][>Zuf>Zt_FFZ~uy>ZurjvZP,$F u)Z=8t =9t=9uFHP@ZX`ZF믂>Zu'>ZtZ4[Z8[:[6[6[^[&>^[u =F ucFPF u^&G^&uvjP/>Zu :Fu vQhFFvjhF ue>Zt[>Zuv^ S^S>Zuv^ S^SF u#>Zuv^ S^S F u &][s6^&uFFFPPNQjRQPRQP5^&u8[:[ "^&7&w&w&w&wtF^&tFF<wH FFߠ][sRPQ^SjRPQRPQ5F^ F&@FuFF<wF FFߠ][sRPQ^SjRPQRPQ5F^ F&@FuFF<w< FFߠ][sRPQ^SjRPQRPQ5Fİ FuF Fߠ][sRPQ^SjRPQRPQ5FİFF<w: FFߠ][sRPQ^SjRPQRPQ5Fİ FuFFߠ][sRPQ^SjRPQRPQ5Fİ̊F Fߠ][sRPQ^SjRPQRPQ5F^ &GȊF Fߠ][sRPQ^SjRPQRPQ5F^ &GȊF Fߠ][sRPQ^SjRPQRPQ5F^ &GȊF Fߠ][s RPSvVQRPSRPS5F^ &GȊF Fߠ][sRPQ^SjRPQRPQ5F^ &GȊF Fߠ][sRPQ^SjRPQRPQ5F^ &GȊF Fߠ][sRPQ^SjRPQRPQ5F^ &GȊFFߠ][sRPQ^SjRPQRPQ5F^ &Ƞ][sRPQ^SjRPQRPQ5Fhj0[P/F uF0[& &][s#FRPQ^SjRPQRPQ5Z^&8GtB>Z9t&u"F݊F<wZаFu^&^ 0~޵FFF<wB޴PNݵBFuFF<wNZЋBFu4^&u,FF<wZаFuZj^&^ 0~޵FFF<wB޴P@NݵBFuFF<w:ZЋBFu FF<wZаFu>Z9u,FF<wZаFuZ>Z8ud^&u\~v FFF<wB޴P{NݵBFuFF<w>ZЋBFu'FF<wZаFuZ FPF u vv~tvFFFNNF NFF F?F*F[PF uՃ><[ r><[ u>>[r[rsv RPQRPQFPjFPjF uH~u~~vNFv FPjRPQRPQRPQF uFPF uv^SvU쐐>`[PXPX`[ t 3 3 F^&]UP3P%]UPP%]U6[#t48[:[4[&F#t N#N&:[3&] vjFPjF uxFV^&&W~u~tYFuRFVFV)F^v^ SPvvFP#F u^ &?Gu&G &W^&&W ^Sv^ SjFPF u_^ &G &W ^&&W~u~t\FuUFVFV)F^vvvv^ SPFPF u^ &?Gu&G &W^&&W,^(&9Gw^&GF^&7~ՋNFvB^ SFP$]P]P6]RPjvF=u.F un]P]P6]RPjvF]s<>]u5F=rmu-]QQjRQjPF t ]]]F]tP F]]tP F]]Fv[ t2P6~[F u~[Уv[x[ ~uFp[ t8~u2P6|[F u|[Уp[r[ ~uFFUFut[   F%Fz[]^&FFp[FFFFFFFF;6r[u;p[ut[z[FF~u\^v@P)PF+PFPF ui~u2 ^^v@P^Ssj^F&9Gu/N^&Nv& ^ &F;6x[u;v[u>CFr4 9FF^&F^&F^ &FsFsRP^v@P^&S^&wFPF u^v&^$^F~^&Y^$^NV;v :vFF^&F^&^ &FFF@FFFs"FsF^&F^&F^ &Fs$F;6r[u;p[u]sv[ 3 F;6x[u;v[u^&Fu p[&9wx[ v[tF%v[&;r5 TF;]tH]u]]Fv[PhvPdRPFP#F u F]U^Svj]U츎]P] tNF t&v ]FF]FsC]<]]&Glt]wmȿ]F]]hrmJ] t~uX>]u(]&lt]]hrmJ]>]t9|[sPp[P] ua|[6]p[Shjj]P#] u9p[&u1t[]s9~[rPv[P] u p[&ut[p[&ut[p[&u&G1@t[;st[t[vᣒ]|[;s[+P6r[]P] t=ud>]u6]p[P] uG]|[]+|[|[r[]p[r[6]p[S6]jj]P#] u#~[6]v[Shjj]P#] uv[&uz[$v[&uz[v[&u z[v[&u&G1@z[;sz[z[v͹ᣒ]~[;s[+P6x[]P] t=ud>]u6]v[P] uG]~[]+~[~[x[]v[x[6]v[S6]jj]P#] u]]UF$]]F"]p[]]]P]P^P]P] tF t&F FuF FuF F uF Ft"6]] u/F t [&F FtP]tv[6]@]=5 t]6]@]]^^&6]~^YF t [F t[[[F t [&F t ظ[&&_]]"&^s6jjFPS/Fa\PD~tA"X ^^ 9FvFFPSDF uz^؉F^sFFN FNFF^F^FFFPNSdF u%vFP6SF u F;FtF FU^&wS]VNF؎FhQQvPQQQQQKF uPQPvhQQQQQKF uPPQvV+RPPPPPKF uRPv LF uhhMF uhPPvvhF u0>"^u "^PF>#^ r!vvv^Sv ^SvEOjjFP/F u^&G N;wukF=s5^_ ^F&HN&HN&HN&^&G F&G FܸFމFF;FsF;Fr@Fv9F u"F uFFfFPFfY;v ^&?tqjjFP/F uhjFP/F uҸFF^&GFԌF֚0~svvv^&/^&?uFFPFڹY FFN^ԋFFFFHN;sFFF^&?u_F^غ#ډ^v^&^&~v^&0^&7PFNX^&@CvF~^&^& ~vS^&^[&Av^&^&@FH;Fu 1FtF)FFFFFtFFFtNFtNFtNF>"^u"^PFF>#^ r&F=sPvvv v vvdFF~FF ;FveFF~uQN F;vG;sV F +FFvFFPFFPFPvFPjFFFF듋FRPjFPF t^w$^F jjFP/F u~F#;u ^&G v &^&G ^&O^G FF^&G ;Fv0F^&H~ & ^&@^& t u jjFP/F uJ^G FF^&G ;Fw+F^&H ~ & ^&@ ^& VNF؎hFPSjF t@~uA"F^GFF^&&FV~uW^&8=sJF<+ȉNvvWRj^@PQF u^v&@@^&8^&LJ8~t%^&&F^&&F^_^F&8^^SC^GFF~}F^Sv^Sv RQj^OQPFP}SF uB^&ƇFV^&&^&G^&G^&8^SC^ GFF&8F=r ^ &tSF^&8F^v&8u@^v&^&G^v@^&Z&WF^&G@F^&8U>V_u *_&G%*_&GV_F_&GF_ bV_]U>N_u *_&G%*_&GN_F_&GRF_SaN_]U>P_u *_&G%*_&GP_F_&GF_aP_]U>R_u*_&G*_&G*_&GR_F_&GF_aR_F_GP*PF_&GPZ_P4_F_GP+PF_&GP\_P4_9Z_u9\_t *_&G *_&G]UaP,P6T_Z_P4_aP-P6T_\_P4_9Z_u9\_t *_&G *_&GF_&O)t+w**_Z^YF_&G)*_&G *_&G*_&wZaT_*_T_&G]UF(_\v^Sv44]U^ &GF^ &Z&W^ S^Sj\4](_^a$_&_F_&ORN_wSaFF_&OP_waF*_&Gs:_R_66_F_&OR_waF*_&Gs@_T_6<_*_&OT_ZaF*_&GrN_*_&GrP_*_&GrR_P^aQX_Q(_Qj\PaQ6N_aQ6P_aQ6R_aQ6T_P bQ6V_PP,4_ t Fr>4_uFs}^N_ ta^aN_FP_ ta^^aP_FR_ ta^^aR_Fa^^aT_FT_F(_F_&_)^aJ_&&_*_&Gs(_F_&O)+&O(_F_&O)+J_&G F*_,_&Ƈ~s) ~N*_&Ƈ*_&*_F_H_F._0_N 2_*_&GZ&WF *_&G*_&Ƈ._SF PPFP0SFP'S4_ t~uFFFA9F rD._'&8u98Nu4O._0_)2_*_&OZ&W2_*_&O*_&i*_&_S.P*_&wZ_P4_ u[*_&_S/P*_&w\_P4_ u39Z_u9\_u*_&Ƈ*_&F_Sj_4_ tP._S62_PaQN_QaQP_QaQR_QaQT_Q bQV_QPP<4_ tA>P_t>N_u F_&GR>P_tq>R_uj>T_uc4_FsH^Sv F_GPF_&GP^Sv6F=c=t=V=t=W=t !tt4_~t>N_u>P_u>R_tFF_&G)P,bQX_Q2_QjiPaQ6N_aQ6P_aQ6R_aQ6T_P=P,bQX_Q2_QjiPaQ6N_aQ6P_aQ6R_aQ6T_h bQ6V_PP,4_>4_t4_ u44_ ui4_ u*_&Gr&Gs&Gr >T_ux4_ u&4_ u*_&GrF_GPF_&wsF_GSPF_&GRPGPF_&GPGPF_&GP^_Ph&\4_ tGr^Sv F_GPF_&GP^Sv6F=c=u~t*_&G*_ZP*_&ws( F_GSPF_&GRPGPF_&GPGPF_&GPGPF_&GP*_GPh<4_ tC s7^Sv F_GPF_&GP^Sv6F=c=t&~t4_*_&G*_&u&Ƈ B^&GF *_,_؍F_H_FJ_L_F_GS*_&GZ&WF_&GR*_&GF_G*_&G Z&W F_&G*_&G *_&8u**_&u&Ƈ*_&Gs&u6_P:_P(\F tI*_&uSF_&G:_;t@Fs]RPGP6_SQFP|SF t~u,F&F_GPF_&GP6_S6:_2FFscF_GSPF_&GRPGPF_&GP6_S6:_F_GPF_&GP*_GPh<F uf*_&G*_&Gs]&u^ S^S*_GP<_P@_P*_GPEF t*_&Gr*_&Gr*_&uH@_&9GtANsYRQ&_S<_SPFP)SF uB~u*F$*_ZP*_&w<_S6@_2FFrjFB^&GF *_,_؍F_H_FJ_L_F_GS*_&GZ&WF_&GR*_&GF_G*_&G Z&W F_&G*_&G *_&8u+*_&u&Ƈ*_&Gs&u6_P:_P(\F tI*_&uSF_&G:_;t@Fs]RPGP6_SQFPSF t~u,F&F_GPF_&GP6_S6:_2FFscF_GSPF_&GRPGPF_&GP6_S6:_F_GPF_&GP*_GPh<F uf*_&G*_&Gs]&u^ S^S*_GP<_P@_P*_GPEF t*_&Gr*_&Gr*_&uH@_&9GtANsYRQ&_S<_SPFPlSF uC~u*F$*_ZP*_&w<_S6@_2FFrvF U^&u && t&&4_]0FPF u'~ r!vvv^Sv ^SvF[jjFP/F u^&G N;w tukF=s5^_ ^F&HN&HN&HN&^&G F&G FڸF܉FދF;FsF;FrEF t N t;u"F uFFFfFPFfY;v ^&?trjjFP/F uhjFP/F uҋFFܸFF^&GFԌF֚0~svvv^&/^&?uFFPFعY FFN^ԋFFFFHN;s^&?ueFPFZV~ tFv^&^&~tnFN^&pvv^&C~ tv܋F~^&^&~tv܋F~^&@^&FH;Fu 1Ft$F)FFFFtFFFtNFtNFtNF9Fu^&?*u N^ &9^&~u ~t@~uF^&  F<*tF9Fv^&8*u N^ &FFFHN;sr^vPF+P^PF+P^ PFPs^vPFP8FFF뜀~?u}~u ^ &^SFP8FFF^vQN+Q^ QN+Q^ PFPrvNF^ &FF^&F^PFP8FFFFFF9Fv6^vPFP8FFFu^v&F<*tbmJuhbP*F thbP*F ubSPbSPF~t"bSh+FbSh+FF>bmJu@Fs fF u/bPjbmJu@Fs F u0bPjbmJt˸bPj<F tb>bmJtøbPj<FbSh+FbSh+FbFF;F r) ^SYPvFPF uߋFtFv~ N^Y^ v&:^ v&@ >bmJu@Fs F uNbPjbmJu@Fs JF u׸RPP^ Sv ^SPFPhTF u\RPP[Qj^SPFPhTF u0bPjbu ~'t@FFsFF<'u^>btWPF u_FPaF uNF<'t2FPF u6F< vA<uB"<u@"FFr vF?F ;bw^&!^ ^- b^&F Fbb~ s) m~N^SaPv FPF^SbPv FPF9Fu9Ft$^Sv ^SvFP"F tFFFF Fb&Gb&G &W b&GcbS^SvWQPhrmF t:shhsm^SvRPjbGPF u?b&Gb&Gb&Gb&u&7GPbGP1Fb&w&w^SvbGPbGPFF ub&u#&7GPhb&w &w FP#&b&w&w&w &w GPhFPFF;uB]=;ðu@"6b&DF;t;u ^Sv ^Sv-F t0b&u &7 b&u&w&wFF b^&&_^&GN bbbFFFrS?F uJFPwF u9FsF t$^&Sh^GP'FF릋Fcs_^ S^SF t'^ &u &7 ^ &w&wF~t@cs^&tFFFFt'N^QPFP!FFFF(FҀ~v^~tI^S^S8F^?u5^&F<*u$^N;v^&8*u^G~?uO=v4^PFP8FFF<u^v4&F<*t~?u^FF^;wU3~ u~u`~uZV\ u 3NFrD@3n u9^N V u^uK;ruA;w ^tr]UFPF t^G_FF>c t^&O@wAcF^&G@ c^SPFPF u@^&?LCu1&OwccF^&GcFF~tcchc^ScP6c^GP^&PvF t~mmt>cuU~u3^v&HpccF^v&@cccdcc^&7cP6c^GP^&P^ SvP|F u]U^SFP^SvrmPF u>tFv^Sv^Sv^ Sv ^StFv FF]U^SFP^SvmmPF u9tFv^Sv^Sv ^Svy tFv FF]6d7dPPNQPF u ^&G!r5hDj.dP/F t.d_ 2d4d&G*d6dF~u*7dr xF uR6dr2d&GFFFFFNF;w+ȃv;^PFP8F up^vPFPoF tF^v&FFFNFȉNF~u ~ wN^vPvFPF tPF;Fv@FЊV :ѳuC"Ë^^;*dsC"ÈFrFr:tFsF&Fs"F;Fu~vF;Fu F+FFFNF+ȉNhR^PQFPZF u\~ t$FrhPnPjFPZF u2d&GF u0~ t*hPoPjFPZF uN2d&GFFs ~ wFFFFFN+ȉN'hP^SvFPZFFUv< t~t. t:t\^t< tRt< tX tҀu92Ht, t:t&7t tt< u< t:u몰]^ &F$^<^&!G$^׆ĀȈFN6 tV, uF*rFsv:yPj_LF tSF*sfF( F&uF˴F$F̉F&^(F" F u{F|F ^"F FuFFFF^F F uFF FF ^FsFFFF^FЉFVFr^&Sv$F&PF$Pj{j}4F u~$ vN^ SvF PFPj[j]4F u~ vN^&Sv$^ SvFPFPFPFPlF t F&F t NN&^(F$F t N؉N ^"F^6S^2Sv,^&Sv$vF t F^6S^2Sv,^ SvvF t F^6S^2Sv,^SvvdF t F^6S^2Sv,^Sv^SvvF t FF. t ^2&&Fv2&<^6PFPF,+P^ Sv vgDF t F^2F&F6UF FtF~t@^&;Fu3vN&;Fu ^G^&Z&WF^ &u]^&FF^&FFFFsR؊p;NtE^v&:u/Q؍qPvFPF uBF9Fv @F)FF뫸(F^ &^^&Z&WF^&ȂFF2sv:Pj_LF t{_^6Sv4FPFѴP^.S^*SvLF F^6Sv4FPFP^&S^"SvtF FFsVF$ F"tNF* t &FF^.Sv^&S^"&7FPFPFPFPlF t F6F tȍv~.F^*&F tȍv~&F^"&^6Sv4FPFP^S^SvF F^6Sv4RPj^S^SvF F^6Sv4FPFP^S^ SvF FF6^&?^u GFF NF@;F vd<~ v1v~^vNFYF@^&F F t~u5^&~u^S^Sv^ SvDFFUPFF F uvvvvv v vj j{j}jlF#ue~u;v&<u2^&?{t)vvvvv v vj jj^jlF#u$v&<uvvvj vv VlF~uFFUePj@dtTdVdPdRd~txPj^SvyPjzPj^Sv{Pjx|Pj n@dPPdS6Td^Sv hrmF ul6@dj^ShF tFJFBdDd6@d^ShPdRPFP#F^LdNdOFdHdNJd.Nd LduNLdFF>Dds Fd&?uJBd@Bd6@dLdShPdRPFP#F t^FUDd^GFdHdFdG^ &Z&WFd&^&Dd@Dd#@^FdHd6@d F@d ^SvFPFPj4F u5FPF PFPjX4F uF;F vdS~ vH~^vNFY^vxFF^&F F t~u5^&~u^S^Sv^ SvdFFFF t^&8uiF Fta~t[~ tF^SFPvFPF uTF;Fw ~ uCFFs F@;Fs^v&@:FuFFF tBN+N&;N v0F t$^ tv& v^0~^YfF~ ~ t ^ t&F FtF t&F tN uPPQt@P^SQvt@Y F^SPvtFsah @FPjF t@"FN ɲuB"ƒ uA"FNQj PF ujlF~uv&<tF~to~tEv&<u<^&?jlF#ukF#t)Fv^@‰FVvvvvv v vj2jj^jlF#u$v&<uvvvj2vv VlF~uFF^SvFPFPj[j]4F u5FPF PFPj[j]X4F uF;F vdS~ vH~^vNFY^vxFF^&F F t~u5^&~u^S^Sv^ SvFF F FuFFPFPFPjj^X4F uF F;FvdbF F2vRF t$N t~^Y^vFFv~N ^YFFF ^&F Ft~uF F t~u=^&~u'^S^Sv^Sv^ SvFFUFF F uRvvvjjFPj j{j}jlF#t)F#t)Fv^@‰FVvvvjjFPj j[j]jlF#tF#t)Fv^@‰FVvvvjjFPj jjlF#tF#t)Fv^@‰FVvvvjjFPj2jj^jlF#uWF;Fs v&8^uFF#t)FF~tv~vvvj vv v vlF~uFF^&&WF F udt'~tv &*d v &*d&4v &^&~tv &F^ &^SPvFPF uFt^ &FFF~NuV~u ^&P ~u^&7fP^ S~u8^&w&7fP^ SfF^~Hu2Ft tuS^SvfP^ SfF^~Du_~uFPF~u^&&WFV, PRPvvvfPj ^ S FfF^^S^ &7^Svv^SFUePjf@f^Sj FPF=4t=4uFF~u0^&G:fO6f8f^&H@f@fFVFfHf FV;^fu;\ft^SF tdfsq`fGFFFFF9F v=Ns6^S^&Z[& S^ &[&:uFF뻊Fs ^&F^S^ Sv ^&df^Sj`fPF=4t=4uF~t@dfFV\f^fU~u~u~u؈F*PFPFPa;"vvv v jF*PF*PF UjjFP/vvjFPF#tf~uFFFFFF~uFFFFFF~tFFFFFF~u3v&F&F&F&F&F&k~u2v&F&F&F&F&F&;O~u2v&F&F&F&F&OF&c~u FFFFFFa;PvvvFPjFPjF#t*vv vFPjFPjF#tvvv FPjFPjF#tvv v FPjFPjF#tvF@PvF +FHPjF*PF*PF#tvF@Pv F +FHPjF*PF*PF#u[F@FF;F sIvvPFPjFPjF#u+vv vFPjFPjF#uF믋FUXF Fun;F F up;u+FFF;F sFv&`jt F u{jPP~v~vF uYjjjjjjjj@jjjjP^&7jP/Fj&G *j&G jF^_]UWVZj>\ju$Zj tZjq>_jtvvv v vvZj֐6j6jF+ҊԊ*RPj^ &6j6jF+ҊԊ*RPj^&>]juj^ &9s&9&)j+j@&'ȡj&j+RPVQj^ &j&9v&j^&9s&&)j+j@&'ȡj&j+RPVQj^&j&9w&j^ &9v&j^^_] U WVZj>\ju$Zj tZj>_jtvvv v vvZj֐>]jtSF+j&j&jj+jA+FjFF+j&j&j+ҋj+jA+SQRPFjFF+jFF6j6jF+j+RP,@^ &6j6jvv,@^&j^ &9v&j^&9w&^_] UWV>\ju $Zj u[>_jtv v vvZj>v v vv~v~vZj u^ &7v&4v SV$^_]UWVZj>\ju$Zj t>_jtvvZj>]jt'j9FrF9jrj9Fr F9js%Xj9Frj9Fw롶j9Fr㡺j9FwvvFPFP:$Zj uvv~v~vu^_]UWV>\ju$Zj t>_jtv v vvZj>]juF 9jw9jrF 9jw9jsjfFjfFv v F PN Q:$Zjv v 6j6jF+RP,@҉VR6j6jF+RP,@҉VR~v~vCj9F sej9F vZj9F sOj9F w\A^_]UWVZj]j$Zj tZj>_jtv v vvZjܐF jNjVj^ j+A+SQj@+ҊԊ*ڃSQjjF+F @+RPȡj@ڊԊ*ڃSQjj%^_]UWV$Zj t>_jtv v vv>ju>ju >juj8djrdj*jjjrjj8ejrej*jjjsj*jj8cjrcj*jqjj9jr jjjjF jF jFjFj+PPijHPgjHP$Zj]jv v vv$Zj^_]UWVZj>\ju$Zj tZj>^jtk>_jtv v vvZjv v vv~v~vZj u^&?t&?`u&w&wGPGP$v FP~v6~vZj tcF^&G& Q^_]UFN ȋN u F]S؋Ff ؋F[]UF |f~fFF&Z&W|f&GFfY] |f&FF|f&GNȋf;v+ЉV^6|f&t8vNFY|fF&G v ~FF=s=r~sF-F-F~to~ vFt ^84s~u~uF1 t ZFPF%mY^NHF=v ĊFf sh>f u~syjjFP/F t^&G0F&W4ffvj6fjy6fhofU>fuD]˃>f sf6fh8f]FPFP uF F= r˰fs;ffPfPF u7f ;w;u+fv# tffs*v ^SvaffP(F tIffF fFffFffPF u6fFPF u^&G&FFF=F\FzFFFFFF2FQF 1F1FF1Vu FFmFm1FF1VF1F ;vNvB;FvNFF^&F 1^&W^&8Os&vF+B@^&GF1^&WF <1^&WF 1F1^&WF 1º PF1Y^&GU]X[YZSPft ftcRQRQS\f[YZfUFЋF ]U^SP u].g;is]. g]U^SP u].g;is].g]U^S!P u].!g;is].g]U^S#P u].)g;is].%g]U^S%P u].1g;is].-g]U^ S)P u].9g;is].5g] U^ S*P u].Ag;is].=g]U^S7P u].Ig;is].Eg]U^ S8P u].Qg;is].Mg] U].ihU].mhU].qhU].uhU].yhU].}h^&G :gt SvWt6^&duWglg^&G ^SvWtFg^&G F^&G :lgt:ht :gt^&G&G &W"FV&9Wu&9Gw&G&W^&G&9G*s&G*FP&t@"FP$F u^&uSlF t^&w8&S^&w&w"&w G<P^&w: F t@^&G-^&G &W"&G4&W6^&G&G.^&F&G0Z&W2^Sv$F Yu,^&w8jGPj ^&G :Wgu ^&G :lgt@&& tA"F&G :guC&duWg ^&dulg&G ^&G-sS&G :Wgu0G<PFP1^&G :lgt:Wgt:ht ^G<PFPFF^&w:FP, u ~u~uߊFs^&w8jGPj FF^&w8 F^&w:)F^&G F u F uFF :r10^&Fr^&0FFF 10^v&F@ vvFPTF^SvhF^&:F@F^Pvj]FF^&:F@F^Pvj6FF(FFF^SvRQPNQNQPLF u$F t^ SNQvNQPjF~uVFF^S@PvFPF u2~t,^SAPvFPF u~tF;Fv4N+NA^v0^ ~9^YFF+F@^&^&<{t<[tF FF^&^&?{uFSBPvFPF uoF sdt_NAv~^YF@^&^v&48C ^& ^SNPvFPF u ~uFHN;v9@N+^vp^~&=9^YF@N+^&CFPF u^&O@wA^~&=9^Y^&G@^&^v&48O^&v&4^P^&wg&we^&^v&48Q^&"^vFF^&F^&G^vNFY^&Gw^ &Gj^&GyF^&^vNFYFPF uQ^&G@^&^&O@wA^^Y^&Ƈ^&Ƈ^PF uN^ GkP^ &PFPFPj|F u#FPvhjj^ShUPj Ⱦ^&G F =wmt =amt^SvFPFPjF|F uݍFPvjjFPQ؍GPQF!t=u~^&Gi^GePF9FvF^kvN@YF^&^S^Sv^SFP|F tF~u;^SvRPPRPF=u^v&xF^&Gi뾃~t<džCFEGv@CPEP}FF7^SFPvRQjv Pv,F u h^&G 6s ^&G8^&G8Fvj^ Sj7F t^&F^GkPYP^&PFPF uFt @^&F^& ^ &Ow~&=^ 9^NOY^ &G^&F t$@^wk~ ^Y^ vxZe~ B^&G :ht lg^&G ^SFPFPP|F u^SrF u}^&FFvN^S^Svm|F tJ^G8P^SvRPjhmmF u"^&w8F t^&w8 FFU^&G :ht ~v F^&Gj]Uv&D ~&] ~&] Y]^&G :gtSv^ S^Sg<^SFP7iF u'^Sv^ S^SgFg^&G F^ &&W^&^&O :hhv^&z"iVnjޱ;u$:u02ir)"iPpPjRPQhrmRPQ,F u(^&G :>hu @iFF^Su ^&G s<&G s4~u ^&"^&G ^G ^ &Z&W^&}^&G&;Gr$Sv^ S^S9F uX^&?uL^&G&O+;FsFF^&^&FFv&t^^ &Z&W^F&G FFN F;vP~uJ^S+QFPFPF t tu.^ v8vNFYFF릋F^&F^  &G :gtRS^ Sv ^SFXismhVnjޱ;u$:uH^SF9^SFP3iF u'^S^ Sv ^SFg^&G F ^&^&O :hhv ^&hVnjޱ;u$:u7hr0Xir)hPuPjRPQhwmRPQ,F u(^&G :Shu DiFF^Su FFN F;w~t^&W&;WrS^ R+QFPFT^&G&+GFV N+;sV^&FF^ v0~&}^9N^Y^F&GFFcF^&FU^&G :hhv ]U^&G :hhv ^&G ]U^&]U^&]U]U^& t^&G :Wgu &G& u]^ &G :huSvvD^ &G :gtWSvvnlg^ &G ^ SvvFNs=u8^ SFP~u#g^ &G ^ &dt@FsWg률g^ &G F,^ &G :hhr^ &G :Wgtw&G 9Fu9Fu^ &G&WFV^ &G&W;Vu;Fw3&G^ &O^ &O^ &O&W;Vu;Ns+^ &r &G&;Gwe^ &G &W"N~;u;wL&wщFVN;u;s&+O &"N։~؋F^ &G-sS4F u^ &G-sG<PFPF^ &G-FVFVF%Ff^ &G^ &G^ &GNV^ &O &W"^ SPFPFP4F u4F^ &G^ &G :lgt :ht^ SjtF t^ &G&G &W"FV&9Wu&9Gw&G&W9Fu9Fu^ &G&WFV^ &G&9G*s&G*^ &FF^ &G@1&@FތFF^ FV&9W"u&9G v&G*H1Fܺ&G &W"N~;u;r_F&+O &"N։~؋F։F&O,r&9G*sSlF tF^ &G^ &G*&;G(uF&G(F^ &G* ^ F&9G*s&G*^ F&9G(v&G(Fr^ Sj$F u^ SlF uy^ &G ts&w8&SP^ &w"&w G<P^ &w: F t@^ &G-^ &G &W"&G4&W6^ &G&G.^ &F&G0Z&W2~Yt^ &G@1&W^ &w&@F&Z&W^ &GN^ &O^ &OF~+&G &"^ &G&G(^ &G&G*^ &G,^ &Yti&w8&Sh^ &w"&w FP#Fu^ &?^ &G,(~t^ &G&GF^ &G :gt ^&FF^&G &W"&O*&;Wu&;GrI1&G^&G*1 uSj$F u`^&G@1&@FF^&G*1&G &W"FV&w8^SQRPFP#FtK uX^&G*1V+^0^~&}*9^Y^&G*H13^SjF u/v&|*&L+^9 ^&G*&G^&G,^ &G :huS^SzDO^ &G :gt S^S<6^ &duWglg^ &G ^ S^SFg^ &G FU^&G :hhr^&G :lgt:hu^&G&G &W"^&&Wc^&G :WguX&r&G&;Gv &G&W^&G&G &W"^&&W^&G s7&G s/^&/&_!^&G :gu^&&G ]USVF uN F3؋F9ȋ^ VF uf F r ;Vwr;FvN3Җ^[]US^v v w7W[]USF uN F3F3Fȋ^ VF uf f r ;Vwr ;Fv+F V +FV؃[]US^v v w7W[]US^WN 2W[]UQF =rmt =tmt"6>hrmP'@iBi>h^&G ]UQF =wmt =amt!6Shv 'DiFiSh^&G ]U^&G :Sht ^&DiSP(]UQ^&^ &&W^&G :>ht @iS)<]U^&G :ShuDiSv*t ]^ &dtZSFPl^& uV^ &du&G-sG<P^S^&^ Shwmvv^& ulg^ &G ^&^ &Gd<tN<uSht^& uH^ SFPl^& u/^ Shrmvv^& uWg^ &G ^&U].Pi]U#U$VWQ^SY_^F^OGG w 3GGG؉GGGFG F GFGFGFGFGPS]UU^ SG PPFPD[#uMG~&w\r/^ F%;u^ ^ FF;tX F ;FuX]~<s 9Fw 9Fw9F v~t9^&Ƈ[^vNFY^v&ƀ]FFF^v&ƀFF@^&*^+vN FYF ^&7^&:^&8^S~<s 9Fw9Fw 9Fw9F vF~t:^&Ƈ{^v NFY^v&ƀ}FFF~tC^v&ƀ[^vvNFYvv^&ƀ]FFF^v&ƀFF@^&*^+vN FYF ^&7^&:^&8^S^&8&8uSoF tb^&8F&^ &^v@^&Z&WF^ &@F^0~^YF^&8^&8rM^P^&*P+P^&7P&:SF u^&LJ8^&:F ^&^SP$F t^&G t~&w8&SP^&w"&w G<P^&w: F t@^&G-^&G &W"&G4&W6^&G&G.^&F&G0Z&W2~Yt^&GFu^&G@1V&G&G &W"F^&Gv^&@F&Z&Wv^&@&G^&G*^&G(^&G^&G, ^&G :lgt :ht F^&G-rG<PFPF^&G-^&G0FF^F&G4&W6Ft.H^&O.+N^v0^9^Y^&O.N^F&)G.^v^&G0Z&W2F^&.uF tuSvF tF^&G0FF^&w8^S^&w.&w6&w4FP$FFt.H^&O.+N^v0^9^Y^&O.N^F&G4&W6^F&)G.^v^&G0Z&W2F t ^&.u%FsFr^ShF u^&G :lgt :ht ^&G&WFV&O&O &"N~;u;wN~Fs FF%tiu!tiFPF u ~ rtiri piujjpiP/F t^&GFpi&8G wFpiX ^Fv&DF&GF&GF&GF^&GF&GF&GF&GF&G F&8G uANsNQPPF t FF^&#tF ;Fv F&O#F ;Fw FrF9F w~^ &FF^&O&@^&G^&w6 FA:r t1Sys.font[Sys]MfAdminAgent.run: nsdvmkeptxcrlfo......SCSI TapeSCSI Tape.......................................$*        #$&'*+./                         |        :    :                O__O oo     O_O   S C S I  S C S I   :  oLocalf0f1{Local}[f0]{Local}[f1]GP00{Local}[f0]Localf0f1d0d1  !"#$%&'@A~EFTCSDRGGGGEEEEEEEEAAMsyssys[Qic][DDS][Tape]0  .t:tEtMtVt_tktwttttttttttbSetNameFunctionKeyCommandOrSetLabelGoFinishCancelHelpCommandNameExecCommandParameterRunFilePauseOnExitPartitionMappingGeneral: LeftHandedHelp MsgHit Cancel to Continue ...Command Cancelled ...P ~DeviceName ~DevicePswd ~VolumeName ~ClusterLine~ProcessorName~ ~PromptUser NgenProcSet SrpProcSetDiskSetVideoSetMouseSet KeyboardSet EthernetSetPhoneSetTapeSetXC002Set PcEmulatorSet TokenRingSetEthernetLanMgrSetNullSet FloppySetPartitionStatusPartitionDetails PartitionMapRMPS[Sys]SystemMgr.run[Sys]Exec.run[Sys]SystemMgrMsg.bin[Sys]RumNul.run[Sys]ClusterView.run[Sys]SystemMgrConfig.sys ClusterStatusThe message file, [Sys]SystemMgrMsg.bin cannot be accessed.@0123456789ABCDEF +;J%&'()*+,-./0H123456kghjiabcdqm*nogj%&'()*+,.HYZ[\]^H1 @ @ HH0123456789ABCDEF01TB600^QicTape89>< DVTWPYX ,-.`aLocal[Sys]Sys.cmds[!Sys]Cluster.cmds*?*?*?[Sys]ErcMsg.bin[!Sys]ErcMsg.bin^^: ...*?-Old.user {}[]<>^{}[]mfd.sys<>MASTERSERVERLOCAL{}[]{}[]Error 2624: msg= %0N maxlen= %1N^YesNo`abcdefghijklmnopqrstuvwxyz{|}~`abcdefghijklmnopqrstuvwxy!a?!*a**2Q=\z[]}[!Scr]]$$.Tmp}[!Scr][!Scr][KBD][VID][scr]<$>BsFilter.tmpVNVFp        ~[sys]LptConfig.Sys&Press NEXT PAGE or SCROLL UP to continuept(Press NEXT PAGE to continuet ~NoStatus~~PartitionStatus~i~PartitionDetails~~PartitionMap~ ~NextPartition~$~SystemMgrDisplay~ ~VideoInformation~$ ~SystemFont~ $~NextProcessor~~Exit~ CKACTION BACK SPACEBOUNDCANCELCODECOPYDELETEFINISHGOHELPLOCKMARKMOVENEXT NEXT PAGE OVER TYPE PREV PAGERETURN SCROLL DOWN SCROLL UPSHIFTTAB#+17?GKQW]citTD aAdDhHmMnNoOsStTwWyYgG!oo!/!0d!/!0y! !hh!:!0m!!2AA!!*o!/!0d!/!0y! !*h!:!0m!!2*A!"!Nnn! !dd!, !yyyy! !hh!:!0m! !2AA!"!Nnn! !*d!, !yyyy! !*h!:!0m! !2*A!(!Www! !Nnn! !dd!, !yyyy! !hh!:!0m! !2AA!(!Www! !Nnn! !*d!, !yyyy! !*h!:!0m! !2*A! !0t!:!0m! !*t!:!0m!!hh!:!0m! !2AA!!*h!:!0m! !2*A!!0o!/!0d!/!0y!!*o!/!*d!/!0y!!0h!:!0m!:!0s!!0t!:!0m!:!0s!.tmp!W*w! !N*n! !*d!, !*y!!N*n! !*d!, !*y!"!0o!/!0d!/!0y!-!0h!:!0m!:!0s!!2*A!!Nnn! !*d!, !yyyy!Invalid Template Index$Cb %6FVfzTN00sundaymondaytuesday wednesdaythursdayfridaysaturdayjanuaryfebruarymarchaprilmayjunejulyaugust septemberoctobernovemberdecemberampmnoonmidnight05 invalid namesunmontuewedthufrisatjanfebmaraprmayjunjulaugsepoctnovdecampmnm05 %0:BLU_fmrx~ #(-27;?BEI{s12.3.5[GP00] t.t}tttttxtt$tsttIttttttt,tQttttt!tAtattt t t t tJ tv t t" t t t t t t t tB tq t t0  B0B:tPS_Vdd"  j ^*  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`ABCDEFGHIJKLMNOPQRSTUVWXYZ{|}~ [Sys]     [Kbd] [Vid] [Lpt]l[Nul][Debug][SysIn][SysOut]>ddd!<d#L>d%d)\d*]d7lud84tttt4tta ]y]yBl.l\lllBl\llBl.l\lllZ]y tO||y]y ]y {y2l;$4| >jt>jt  LIBRARY: ctos.lib VERSION: R12.3.1 (friday november 12, 1993, 17:19) LIBRARY: CtosToolKit.lib VERSION: s12.3.4 (saturday february 19, 1994, 15:33) LIBRARY: enls.lib VERSION: s12.3.5 (thursday march 3, 1994, 11:40) LIBRARY: mouse.lib VERSION: R12.3.1 (monday november 15, 1993, 17:20) LIBRARY: systemmgr.lib VERSION: R12.3.0 (monday november 15, 1993, 16:05) COPYRIGHT (C) 1980, 1993 CONVERGENT TECHNOLOGIES, INC. ALL RIGHTS RESERVED. COPYRIGHT (C) 1980, 1993 UNISYS CORPORATION. ALL RIGHTS RESERVED. THIS SOFTWARE IS PROPRIETARY TO CONVERGENT TECHNOLOGIES, INC. AND UNISYS CORPORATION AND IS NOT TO BE REPRODUCED, USED OR DISCLOSED EXCEPT IN ACCORDANCE WITH PROGRAM LICENSE OR UPON WRITTEN AUTHORIZATION OF THE PATENT DIVISION OF UNISYS CORPORATION. THIS PROGRAM IS FURNISHED UNDER A LICENSE RESTRICTING ITS USE SOLELY FOR THE OPERATION OF A DESIGNATED COMPUTER FOR A PARTICULAR PURPOSE. TITLE TO AND OWNERSHIP OF THE PROGRAM, INCLUDING ITS SOURCE CODE, SHALL AT ALL TIMES REMAIN IN THE NAMES OF UNISYS CORPORATION AND CONVERGENT TECHNOLOGIES, INCORPORATED. GW tr5t $.ttP!wCopyright 1993 Unisys Corporation. All rights reserved.Ver R12.3.0 Linker R12.3.1"/$,./ /9?`TTPV@[?\ ]?jyЀ_ `OД`?PЛП`Op0OO`p  `_/P@O /?  @@?P _ _ ?!$% '0'+?++o, ..2/P3O3/3/607PI0M_S V0WWXO Zp] ` abde`g hhj_k@mPnoOs``/ P` POp_P?r,*h67-8'0(&/."  )#+7*3 8% +,"$d1/m2,N!45)/[l2FZmq(((((i((((N(o(Q(l(((( j} '"  % B}}}Q}^}}}}<}Q}[}}}}}}(}@}H}Z}r}z}}}} }E}k}x}}z } } } } } }} }9}}}d}q}}}}}}}}}}q y                     ! ) 1 9 )=Vr q { lv+B {  ! T   k   1 g    . & a       FiFFF;FWF~FFF!FOFyF/FOFoFFFFF6FF FQw0|  6T6g66_\-hF0 {|A|P i   |  X }   1<s [s os s s s s s Ms is  0 R a n S q     ! G  = n     w    K Z ~   7 w  b v   ; H m z            ? ] q ; ; !; h; {       * 6 '" . j. . . /B B MT l l /l Fl Xl t )t < D i  y 2 % _     A h          )  <    d     *P$FSSS_y3r7H0CcH (SSSSSSuuuuuum+Ff=nnnwnnU84A]v  S  RP;;Tj*:_&EE=<P<,Yj (2\`\\\\\\\(}&*E~ F -6A|s    ; f    " + . B R T l t  2 8!1RS@SuBS[i+;VbnPEVa<N\k(\{ 7c1t:Nbu+((D(m(s((((5(l(((( (D(e((2(G(((((((((;((((( (%( 28o!=(RXr 3E}1XnIOdzP\q}r~vN".X^lx"(6B~  g s  ,}b}h}r}x}}}}}}}}}}}}}}6};}y}}}}}.}~}}} }5}g}}}=}}}" }V }s } } } } }: }@ } } } } }$ }E }s }y } } } } } } }' }G }l } } } };}Z}n}}}}}B}h}}}}}}}G}R}}}}<}W}}}}}}}}}0}|}}}5}P}}}}}}}}$}M}r}x}}}},}6}>}V}z}}}}}}}} }!})}.}3}8}D}R}^}j}{}}} }}}{{{{{{{ {:{V{p{{{{{{{{{{ {{${,{6{P{j{|{{{{X{{{{{{0{R{{{{ {'{Y{{{{{t{*[*u*~*************,*E*Y*d*t****   & 0 ; F R ^ k o Ew =E kE E E E #E QE E E E  E 7E eE E E E E KE yE E E E' 1E/ _E7 EB F J N R W [ _ c g l p t x |                                        $ ) - 1 5 9 > B F J N S W [ _ c h l p t x }                                        % ) - 1 5 9 ? D I  [5F$k$_         & t     ;A   ~~0{{      FFFFmFFFJFFFS F|(-V--?66#AQAA A~AA}AAAsAAA<fAmIl*Pt os6| {z4^D=/ = a o   4 B g    % 4 B  J     s 7s ^ A W h   > % N   I T ;  l    d G u  {      X >     1 u   B; Q; ; ; ; '; O  % H    A m 7 F  g" Pjt 8t Tt rt t t 3t it nt t t !t t t t 5  9 Z &2 K2 _2 w2 2 2 L2 g2 2 2 2 "2 2 F2 2 2 2 ?2 q2 2 2    7  9      ~ a   % 8 188y88888888888,8888p88 8(8D8`888;888 8+bct,  !C!\!!!!11SQS`SSSbS#a6N "`3@@@ @0SSSSSSSSS9SSgSS S SW S S. Sh S S S7 S6 S S SSRSvSSSSFSSSS3SSS.ubuu)u}uuu8uuuOu{uuu KtiiK +>|,SiBBS[[3izii9ikiFLQ<Z@3n :+;[;;;F;o;;V4bubbnmn<3zE'3zcR p`I`QQ\      %    9   B,y+PPP!Py,bEJ {l {Yaaaaaaeaaaaaaqaaa& a a a{ a at a aQ a aN\ kkkk'kkk\UnPjP*P(!]UjS6n+P(tz£nPjP*P(jpr6t؍vx6z|~]jS6n+P(FP0P(F=s nn6njP*P(n-1Pt1t+ډtX+ãz1z+ʉz١n+ã;ntj(jpr6t؍vx6z|~jS6n+P(hFP,P(FP0P(Fa1Pt 1t+ډtX+ãz1z+ʉzˋF+rt tt>zrz zz>r ᣀ6tpP*P(6zvP*P(6|P*P(^Sh-P(9^&FFPP^&wFPF~u ^&GFF^&?[u+vN&8]u^&S^&wRQPF ub9P^&S^&wRPjv F=t =t=uF~uFr6 FFtFQ^&S^&wRQjv pSPtF=) u1P^&S^&wRPjv pSvF~Cu]RP^&SPjFPP(~t, RP^&SPjFPP(~uFF t ظ&&_v^SH :9s?pFF6Ph66FP#FuFPjFPFP4FF t@t tP^F t^S^SPFPZ4FFF thNF F= t=u2:^S^SvFPZ4F^vFF)vF uttP^ SHF9s 6 PFF t)ttP^SHF~u :FF~u.^SF t:ttP^ SHF~u:F ȖzFP^&S^&wPNQNQNQNQNQNQlQNQRQRQPPF t,^&NFv&tN^&8]t;tNv9^ S^&S^&wRPjvvSvtF!uh^SF~) u1^ S^&S^&wRPjvvSvF~Cu]RP^&SPjFPP(~t,RP^&SPjFPP(~uFv^SH ^ SP^SHFȔFr!^ShrmRPvF tnP^ &S^ &wRPjhrmF=tAl u n FzP^ Shwm|F t\:uF:tvxv%pt+Ⱥvxvxv F=u2vjrPjF uvx;tu;rwFF ui6jmPhF tP^AvjmPhF us sF~u &sFF t򤍶򤍶G򤊆&s&򪍶--@򤍶򤍶%%򤍶򤍶vj mPh F=uvjmPh F~ulsvjPj FF t%P^ SHFvFPr?zP^ S^SF t9N:uu8r~t vFzPrFFzP^ S v ,FF tHFFHN;r8v QFP,P(FHFNQNQvP^F uFuv,FF uFFHN;svQFP,F t P%F]N^Sv|S6;F tNrPFPHFy|&r2FPFPvv^ F tT]FtPFPHF~t6|SFPv+F uʍFPFPvv^ F t Ft v^ S^Sh%RPPNQNQPF uJFPFPoF=g;t7~un!~uF ~uFF u ~u 4Fh<P*P(h@P*P(S6RPj<Sh@ShCPLsChDP*P(hHP*P(DShHShP(S6RPj<Sh@ShCPv ,Fth0v ; F !v j^S,F t h0v ; FF FuFF F ^&&Wv ,F u^&GF=F;Fsh0v ; F !v j^S,F t h0v ; F vFPNF u(RPFP^SF t h0v; F^&v,F u^ &GFS~vh0v; F ;vj^ S,F u^ &t@^&F= t= uFF vFPNF u7F t0^SPFPsh0v; F"F^F~tN~uj F=* t =+ t=, uv ~4u!PS6FPZ4P(lVG-Pjv$Ffs=FPP t@gs2PjRPjhP(vVS6Z,~tT~uj Ftu \~4u%FF^FhqFPjPlPvF=sPvRPjjPhNPFPv~4tjP6Nl\FPv F FuFFhsv ^SFPjPhNPFPv jP6Nl\F tP F^ t&JB^ &OJFF t#F^&JB^&OJFvFPFPjPhNPFPvjP6Nl\FPv U^&GZ&VXRTN uVSFP6Z\P`>\u6VNj\FN\N^ & t#^ Q&Oj^^ &GNR6\VXRTZ+ΉZPGPQ^P`>^t<R6^VXRTZ+ΉZPHPQ\P`>\u6VNj\FN\ȉNRVXRT)Z^& t%^&O>Nj^&GNVSIP6Z^P`>^t=R6^VXRT)6ZZ6VNjFZN] F=)t=tPvFPlFPv~4t0NvjFFNjQPl\FPvЉFVFv FPlFPv ~4tC^Sj^SvjPhNPjlP(jP6Nl\FPv F^ t&JB^ &OJFF t#F^&JB^&OJFvFPlFPv~4tJFPFP^SvjPhNPjlP(jP6Nl\FPv ~ u^&FF^&GF^SJQPFPF~uFFhAFPv jPhNPF t!v RPjjPhNPFvv ~ujP6Nl\FPv Pj DFd bu bPFF b&GF FF^FvFPjjPhNPFPvjP6Nl\FPvFF^FNN^Fv FPj jPhNPFPv jP6Nl\FPv FsF Pv;F=]uF Pv; \ jjFP,F u^SPPjt@jPNP(jhP(jPNP(jPFP P(jhP(jhP(>u&? u F>uFrv*iS64sh( &?u"wFNO6F>u>$u *>uIPS6RPjhwmvS6ztF tPPHF \F PhrRPjPjFFPPFN^Gss T /Pj_F tP SRP6FPF~uKL%F@F+ȉH uF&?{tSSQPFPF~uhPHF \6N&8]tjNA6FF@FƇ[@FV+INpFFF]&?[u*6N&8]uvFF6^Ƈ[C^6FFFƇ]F}^t.Ƈ{C^򤠁FFƇ}F^Ƈ[C^121FFƇ]@F^6FFJFHQTQPPF@s2QSPS6hrmPPH t \FOFt؀F uNFFƇF FQFQPFPZ4F t(6R FFtu \v s>PFPFPFPZ4PPHF tPrFF P&? vh jFP*\ tP 6TFX&Z&P6& ~^Y&G^&G &G ^&G&G&W^&G&W&G^&GTUFr95t]FRPFS6JS6hrmPPH t \6Rj|ShPFPH t6R F \6Rj rPjPPFPH t6R F \P<P(FPP(Fn+PF uvFPF uF~ujFt!u P\v >u"|&GBPXP*F tP FF~t6RpShv$RPFP#F uFpG~sp&teQ6OQP2,s4$&8GtANrs Ns8u FF@F#@pF@FtPFPHFFr9FuPh(6R F^&&G> sxFFS6JRQPQNQPFF t!{ȍ^Ƈ}^FS6JRPPQNQP FF t(^Ƈ[^^Ƈ]^^6LNNPVRPQS6hrmF=t{~t6R Fv(vj PhF t6R Fv Fv(`s bsce^&&W2hsRPjPhFPPFNFF|&OwFF|&GFFh}RPjPhFPF u/^FNFFFxyFss |G6FFFhvFPjPhFPPFNss|G:FFFhwFPjPhFPPFNsshxRPjPjPFPPFNsshyRPjPjFPPFNFPj |&wn&wl$F+؍FȍvFP FދV FމVNQj RP$F'+؍Fȍv|&r&& *|&&Y|&Y+FVࣤNQj RP$F6+؍Fȍv|&Ol&WnNV>+LNךYFV> t5>FVNQj RP$FF+KFȍv U򤿋=sshzRPjPjFPPFNFPj |&GXRP$F+؍FȍvlW|&GRFV&TtFVFVFVNQj RP$F6+؍Fȍv|&OXNVF~+LNךYFV t9FVN~FVNQj RP$FF+KFȍv X򤿋=ss >Tt X&FFX&_^FRPvDP^&P^GP^&PFPFPv,F~u4X&GFFX&F&GZ&WFX&Z&WYFTN;sANTHN;svX&FFX&^FRPvDP^&P^GP^&PFPFPv,F~uGvX&FF~X&F&Z&PvFX&Z&PYFt;FtFFF u |&GN&WPFV6QhRPFP#\ tP F9|FF=w؋)FFu~th >t4FHN;r$񋄁 FVFuCFV<FFVFNNN ~ N܉~މFԉV֋F u@;vNFF6SFPvv܍FP#F tP FFHN;r}@FFFr^v&8t5F&FFX^،F&7FV֋FFFFF@+FFVFtxF)FFV~uF'FN1FF~ךFFFFPj FRP$F'+؍FȍvFPj FRP$F6+؍FȍvFPj vvԚ$FH+؍FȍvFhjFԋVln,htRPjPhFPPFFȾsr F PrhuRPjPhFPPFNVFTHN;r%X&^F&G;VvVFuи@9VvVVPP*\ tP ss hjFP/LP(^& FjjFP/LP(^G FFFTHN;sxX&^F&wFFss0FPj ^&GRP$F+؍Fȍv^&G FrPGP^&PFPZ4\ t)6R F\tu \ 6\ PZPjFPZ4\ t)6R F\tu \ 6\ ^&G^&w&w&wv=ss*FPj FRP$F'+؍FȍvFtzrh|RPjPj2FPPFNFPj 6j6h$F6+؍GȍvFPj 6n6l$FH+؍GȍvvRPjPjFFPPFPjv$F+؍v荿FONvRPjPjFFPPFNRP\F>t@Frt |&[uPFs$hPhPhhS|&[thhS>u%FshP~hhS>uG> r@>u>u h#h>u hhSFs"|&r<t< uhh >u hSU츄PPpE sg>Tv#>TtyssPPPH\]U> Flu+Jt㋇ ]U ]U^&w FF^& ]U CS6 FPjv$Y ]UP6@}P6@g$P6@Q-P6@;KPsVZP>u[4PP@:PP@]P>uP>u(CPP@P>u*}PpPcPV]U^SP u].!s].]U^SP u].)s].%]U^S!P u].1s].-]U^S#P u].9s].5]U^S%P u].As].=]U^ S)P u].Is].E] U^ S*P u].Qs].M]U^S7P u].Ys].U]U^ S8P u].as].]] U^SP u].is].e]U^"S3P u].qs].m] U^S P u].ys].u]U^S"P u].s].}]U^S$P u].s].]U^S&P u].s].]U^S+P u].s].]U^ S,P u].s].] U^ S-P u].s].]U^ S.P u].s].]U^S/P u].s].]U^S0P u].s].]U^ S1P u].s].]U^ S2P u].s].] U^ S4P u].s].]U^S5P u].s].]U^S6P u].s].]U].U].U].U].U].U]. ~i^GP^Sv^SvHF t&FPF uW^w@F%d^&wPhMF^GP(F t^&G&G;G5P1F uT9FvFF1^&G;Fu&G^&G@&G^&G&G;FvSrFFGF^&GZ&W&Ov~ &w&&&W&Oi&G ^&w;FFU^&wvO]UF>pt=t P  \]U~u]^&GFĴ.GFF'F{ FF{ F&5^ćxFFğ^Fv &F^&NFFu-#ȋ^H^&Z&Wv#^& F^&Z&W ^&G^&t x y $^&tx x y z ^Sy Px PhFPv ^SvPF u^&G :uShhv ^Svh,aF uF^&G8 @F^&srF F~u'~thFN^SF~t,UFPvQPQe]U^&G :u:*u :?t^S]^&G :u:u:u ]^&G$&G ^&G,^&G(^&G2^&G3^&G0]^&G :*u:u :?t^Sht^&G :uF:u=:u4:u+:u":u:*u:?u ^Sh F u^&v#&wxh ^&wx&GpP K^&u t1^&FFv&|^^F&7^&Gn@P hF^&v&wxh ^&wx&wp ,^&u t^&7^&wn FU^ &G :u:*u:u :?t^ S^S]^ &G :uF:u=:u4:u+:u":u:*u:?u ]^ &G|^&^ &G|]Ȇ^&^&G :Ct W^&G<t':t!&OFP\sFr^&G^&u2F ^&~ t^ &?utPPP^ Sv _> u! FPF u ~ r ~ | ujj| P/LF t^&GF| &8G wF| X ^Fv&DF&GF&GF&GF^&GF&GF&GF&GF&G F&8G uANsNQPPF t FF^&#tF ;Fv F&O#F ;Fw FrF9F w~^ &FF^&O&@^&G^&w6 FA:r > >%]?U.>><Ŀ&UB>"u$&U>tt u Ƈ3LJ@@H ; w3ǁFıV&t&u#&t&DŽ&DŽBřN tƇ23Uw(>Ƈ0Urx> uË ;$t6ķ&&,&FA +;$r3,z>ULJ@Hu H~U ;$t2uLJ@LJ@U"!#!!!!!.!?!!!!!*!+!!!!!.!?!!!!!U&.>>>ȋz>рp "t 2.9twx0>t ."t,<t<u$t\UƇ2@uLJ@td+w"+fw u, t>Ft;wtt x>u3Ut2 2t'Ƈ2;$t@uLJ@0uS-Ƈ|UUpu51u.<t&<t".t5u < u Ƈ5 Ƈ5< t[苗d;r";wlpt@t9t0,ht :iuĿ&E&&&d;w;vLJ>:Ŀ&C;drXdrQჿ`u`+^"Ŀ&S&C+t&E3퉯^&FtLJF4LJ>:U`u`+^^&Ŀ&S&cFtLJFUd;t&r";v ;drdrLJ>1ttĿV&&UƇ4tBRP.x>p$p>Ŀ&U >XZtLJ@40uS-U>ȋ=w>=wZ=wTĿ&U>t6t t3t'Ƈ3Ƈ0LJ@Ƈ3Ƈ0LJ@3tJz>Ƈ|"t5&d;w&";w;^s^ZFu33˥'^&vvvvv&<^ Pv ^SF-u~FN ;sNFF~u\FsUvvvvv&4^ PvFPF^F&~uFFV^&;F rF랋F^&^ &&W^&G :~t ^&Gs^&G&G&WFV&w&wRP&S^&wFPFV~NV~=]=u# t^&GF^&G^&GFF up^&GFV^&G&WF^&G^&G&W;Vu;Fw4&G^&G&W&+G&WFVF&G^&uFF^&G &w8 F^&G:t P)FF!~eF =wmtAN=smt=pmu'^S^Sv^Svv ^SvL0F =rmt=tmuFrmF =wmt =mmt=amuFmm iFP^Sv^SvvF=t=uB^S^Sv^Svv ^SvLFt !t= uFFa~uv~mmuo^Sv^Sv^&w&&w$F=u^Sv^SvjhF~u FP^Sv^SvvFFF t^G:P(F uM^&w:FPT uF FuF^&G8#;u8! !uhj!P/LF tf!& r 9FvFF1F1F1F;s ^Sh %F^&GZ&WvF&MX&E&uF+ƹ1&EFF&Z&U&E$<&E&FYs߸&G&G<~ tmuv^S^GPvj^GPjFF usF =rmt=tmu^&G &G 5^&G&G~ mmu&O FV^&G FF^SvvF t ^SPmU~t^&GAF]^&G&;Gs&G^&GN1F&G^&G^&G#&W%^&O^&O^&rmu&O ^&G ^&G'^&G ^&G^&G^&GFF^&w&_S^&wFPF=S#uFF^&Z&W^&G+FV&G^&GF+^ &ONF^ GP^SvRP^ &wQRPQF-t =t= 5u"^ &GF&G1PF1YcFt!uF8#F=P#t =I#t=uL^ &wF^ &GN+Ⱥ;v'F&G1PF1YH%&G5 |~$~sx#>F^&GZ&WF^&G^&G~ wmuF mmF =rmt =mmtOF ^&GF^S^SvFPFPF u~ rmt~ ~ rmu ~}K#^S^SFP"F u^SFPF uhCF^SFPj>+^GP^SFPRPj^&wFPj<F u^&wjjFPF t~ mmt^&wFPj<F tFu+Jt ^&G!~tH^&9G!u@&G!^&wjPFPF u^&wjjFPFF tuaF=1#tk=/#tf^&wjjFPF t=1#t=/#t,~~8^&wjjFPF t=/#t=1#t ^SP)NjCFFP&w(F u^&G :t ]^&^&O's&G'^&2#t &G^M^SF==#t=2#u<^&G'2#9Fu ^&G9~=#u ^&G^&u&G~1#uF^Sv^&GFF^&GF&G :t V^&G%& G#uW&G&+GFVN ;u;vF F ^&^v&t8v N FY^F &G!^&^SPF uQ#^&G&;Gs &G%& G#u^&w^SvFPF=1#u ^&wFPjG=PF=#taFV t1^&G=&W?N~;u;sF+&G=+&G ^&GFV^&G#&W%F t=1#t ^SPFFF^&GFF^&G%& G#t&GArQ#^&G :t&G tT1&wV t'&O+^v&t8^&G+F&G^&w^S^&wFPF^&wj&w!FPF=1#uF^&G7s&wjjFPF=r#uF^&G8s&wjjFPF^&wF^&OArF u F uFF^&G%& G#u&wFPF t ^SP^&GFFF^&G#&W%&;W?u&;G=w~tFs^v&|FF^&G&+GF&w^SPFPF=1#uFFV tH^&G=&W?N~;u;sF+&G=+&G$^&wFP u ^&GFH^&G#&W%^&G=&W?^SvF^&G"s&G :itF ^&u&uF{FNs^&G$FP&O&xWF&wFPF u6^&Gt<uF ^&uSF u^&G~uFs ^&G#^&G#FF^&G :itF 1^&G$r&G&F uF FF^F ^G'FF^SvP^OQP=F^&t&G"s^&wFPF u*^&G"s2&w;^&G#sF^&G"rN^GEP<F u-^&G&GG&G&GM&G5&G9GAPF t1^&G"^&G5&G9&G t&G5^&wFPF uJ^& G9&G5G5;vu;FuF^&G"&GIF^&wFPTF u;^G5N^;u;t&^GA;u;u^&G"&GIFF~uiFFs-^&wFPT t@F~u؃~uF^G5P2F^&w)F~u u^&G ~uFF^&G$FU츂Vnjޱ;u$:u ^&G(~F =rmt =tmt .^&G ]^&^ &&W^&G :.t WFP5F uCn!~uF1~uF$^G^ &Z&W^&F^&GFU~F =amt=wmt=rmt=tmt =mmt&^&G F^&Z&WF^&G]U^&^&G :t ^&GN ^&]U^&^ &&W^&G :t ]U^S^Sv^Svv ^Svj]U^S^Sv^Svv ^Svj]UFPjv^ S^SQFPQ] vFP,F uqv~N^Y~u ЉFVsjjj ^SvNF,jjFP/LF uF^&G Z&W F&GF^Sv,Fv ^&G :tSv^ S^Sg4<^SFPF u'^Sv^ S^Sg4F^&G F^ &&W^&^&O :v^&zVnjޱ;u$:u0r)PPjRPQhrmRPQtF u(^&G :u p!FF^S4u ^&G s<&G s4~u ^&"^&G ^G ^ &Z&W^&}^&G&;Gr$Sv^ S^S9F uX^&?uL^&G&O+;FsFF^&^&FFv&t^^ &Z&W^F&G FFN F;vP~uJ^S+QFPFP4F t tu.^ v8vNFYFF릋F^&F^&G :tRS^ Sv ^S4F"smVnjޱ;u$:uH^SF9^SFPF u'^S^ Sv ^S4F^&G F ^&^&O :v ^&Vnjޱ;u$:u7r0"r)PPjRPQhwmRPQtF u(^&G :u t!FF^S4u FFN F;w~t^&W&;WrS^ R+QFPFT^&G&+GFV N+;sV^&FF^ v0~&}^9N^Y^F&GFFcF^&FU^&G :v ]U^&G :v ^&G ]U^&]U^&]U]U^& t^&G :u &G& u]Uv&D FFv^"&@Fv^"&x"ti&Gwub@JP(F u,vZ^F&^&G ^S1F tvF^"&@VZ&PX^&GFth~%^"&Gwt^F FF FF FF FFFFFF^"&OsN&OqN^&OcNNNNN&tFFFFFPFP tFF s u~r ЈFQ~ u?~uЈFF>ЈFF$~r)FFsF~ u~ r F$F~^SvFPvFPvF tlFƒwu{F^"&GF^"&GxF^"&GzF^"&^"&tu|FV^;u$:uF^"&Z&WF^"&G+!؍~!^"&&_^"&G!@%!^"&G^"&G^"&tuB^"&FFv"&t^^FF&F^&GF^&GF^&GFsZFƒtu^"S^SPRQP^"S^Sv^Sv͚\F t^"S |FF^"&G}^"&s &_ ^"&_" F^"&w) F&_v˷& F^"&vF&wxj ^"&wxj F@F^"&Go^"&wx&wo ^"&wxj ^"&G :t:u^"&G tu ^"&wxj ^"&wxj ^"&wxj ^"&G :t@^"&G :u&G tu1Fֹ@@2^"&u&Gn(^"&u Fֹ@@Fֹ@@ ^"&Gn^"&wx&wn ^"&wxj Fֹ  ^"&Gp^"&wx&wp ^"&tu^"&G# F&s&G&Ov ^"&G+&Wv"Ѷ &Gn^"&u&On^"&u&On^"&wxj` ^&7^"&wn ^&wj ^&wj ^&wv ^"&GpsjFPhFFsvv $jF$PPF uc^"&GFF^"&G& GtvjFPPF u3^"&GFF^"&G& GtvjFPPF u F^&u2&9w&wxP ^&wxj6^&tu)^&FFv&t^^F&wj ^&Ltb&GZ tXFF&G^&wLFPT t^&^&GL^&G^&G^&wLFPF^&w &gp}^&wxj ^&wx&wp^&tu^&wj ^&Gwu&wF tF^&G FF;w|^&x"tf&Owu?&HJ tQ)F tFv^&@V t4P2F t&F!v^&XV^F&^&GFtzs}jFPhFFsgvjQF uY^&GFF^&G& GtvjQF u.^&GFF^&G& GtvjQF uFU^&G :t/:t):t#:t:t:t:*t :?t ^S |]F F uF ^ &FFs^Sv^ Svv ^Sz^Sv^ Svv ^SyFF uFP|F uFv{F uFP|F uFFPFPF~ rWhFPjF u~t^ S^SF*PRQPF u^ &&C/FPFPF~ r0hFPjF u~t^ S^SFL/hjFP/LF^&G F㾠!~TF< t< u F =wmt =amty^S^SvFPcdF ug~ u^&r^& w>~ u=^&s$S^Sv^Svv ^Sv.$^&t< ~s F^&GZ&WF^&G$~u^&G@ "FP"PjFP^v@PFF+PRPjhrmF~u"FPF uvFPF u FF tv)"^&_LJ>"F>F&w扜""^S^ڌFv&\Fډ""FFFFP<F u{^&w拄>"FFF0F$NN&ONF&GHFFPF uNv^&w=SjvFPF^Ƈ$F utFFFFP<F uFFF0F$NN^&ONFFPF tv)"^&_LJ>"F4vFPFv)"^&_LJ>"F uF0FFFFP<F uq^ &w拄>"FډFF0F$NN&ONFF&O?NFN NF^^F&^ &GHF֍FPF t^ &;u vڸPSPv^ &w;SjvڍFPF܋^Ƈ$^&GF^&F=Ct=cuFZ^ &G?FҌF^&?t.F^&HN;r^ &_$^& Fu׋F^ &GEF ^ &G^ &G^&G^ &G^&G^ &G^&8Gt/^&u ^ &G"^&u ^ &G^&G^ &G^&G<t<u^ &G^ &G^&Gf^ &G FF w"؋ ^&;Gu F@^ & Fu^ & &FFFFP<F uo^ &w拄>"F܉FF0F$NN&ONFFF<uF FFF~uF FFFFPF uv܍FPF uFF FF w8؋" "t#ć"FF t& t PFFu|$P(F tPNFN|$F^FFFz$N^NNv$NFF|$NFFPF tP~$$$|$$~$P1F tP6|$$PF "$njޱ;u$:u>*"0t.F tP$^&GHF~ t9F ^㉇R"F>"^Ff"h"F^$Ƈ$ FF w+؊$s㋏R"IR" u Ƈ$PnFu^ćf""" """#"$"P<F tP|$&"*"0("$,"-""&O."/"^$u0"0" "PF tP^&F^&&W^&G :t:*u^Sv^S^S^&G :t :t g^&FtSjF u^&Gb;FsFF^&O*&Od^&`tN&9Os-SP^&+Qv ^SvhZaF uF^^&G^&Z&W^&G*^&^F&9Gw^&G^&^&^&)G^&^&G*^&G*&G^j^&G^&Z&W^&G*^&^&GFF^&G`F^&FN;s#&)^F&)G^F&G*F^&^F&)GF^&^&_㋇ F u^&G*~uF ^&^&G*^&G^F&G`^&GFF^F&9G*tC u&G"FvN^&8uvv^FF^&w`^&)FFs^&G4sSFP<F u8s,jFPhFFs^&wvGPd<FU^ &G :t :t Q^ &G^&^ &G^ &G&^ &G*^ &Gd^ &G^^ &G`^ &G4sS]^&G"&;Gw&4t^&Gte&w &wxj ^&Op^&wx&wp8^&tu+^&&G&OFN؎&WRR  P ^&Gt j^&G@^&G0rS-^&G4U*$PFP t$>$ u ~r$ >$ s#^Sv^Sv ^SvPe>$ s$vN F$F^FFFFFFFFFFFF FFFFFFFPd]U(>$ sF uv vvP'FڈFFF FFFFFFP ]U(>$ sFuvP FڈFFFFFP]U>$ sF uv v ^S$8>$ rv v ^S7$FFv v ^S^S]UQQ>$ sF uv vv01>$ rv vv8$FFv vvP]U^&&GFPF uFF^&G&GSF u(vFPF uF;Ft ^&G]^&^&G :t:*tSv^ S^S\$V^&G?^ &Z&W^&G?FFF9FvF^Sv^SF^&?t=ZuZ>F u^&.t&G9s!^&? u^&^G^ &Z&W^&G9FF^&HF~u^vP PF+PFPFFt͉F^& F;Fu ^&G9^v&x u^&F@N;sF+A^vp^~y^Y^&GE uE^&GGs7v &S^GHP^&7FPFFt @^&^ &G :t:*t :t:?u^ &G :t-:t':t!:t:t:t:*t :?t~ wc^ .p+A\e}^ &G~^ &Gu^ &G :u$&Gs&;Gqt'^ &su$^ &qu^ &G :uFFv^ &@q3^ &Gv@^ &G :tB^ &G8^ &G :t,^ &G6v^ &G :t^ &G.^^ &G :u ]^ &G/C^ &G<^ &Gh&Oi$^ &Gq^ &Gs^ &Gl^ &GjFF^& F ^&G :iudFv&^&_.2:I|^SF1^SF u^&ud&G܁~t^&G}^&G1VS&xWvF&pF uB^SF u^SF t ^&G~u^&GFFFP&O&xWF&wF uI^&G1&WR&@F&Z&W_^&@&G&G&GF~t_^ GSP<F uP^ &G&GU&G&G[FF&G]Z&W_F&GaG3F&GcZ&WeGOPFYFF ^&G5&G9&G t&G5^&wFPF u}^&G9&G5G5;vu;FuF ^&GWF^&wFPTF u6^G5N^;u;t!^GO;u;u ^&GWFFFUv&D ~&] ~&] Y]&FFF =F\FzFFFFFF2FQF 1F1FF1Vu FFmFm1FF1VF1F ;vNvB;FvNFF^&F 1^&W^&8Os&vF+B@^&GF1^&WF <1^&WF 1F1^&WF 1º PF1Y^&GU^ &G 33&:t :.t$C^Y tt &^&] ]U^&G :w):up!&G t&G uF&G &G 3  ]U^&G ]UV>] vjFPjF uxFV^&&W~u~tYFuRFVFV)F^v^ SPvvFP#F u^ &?Gu&G &W^&&W ^Sv^ SjFPF u_^ &G &W ^&&W~u~t\FuUFVFV)F^vvvv^ SPFPF u^ &?Gu&G &W^&&WU u. t!;v 33@33.P 3 ҃+@sH]U؋]UN~F V u. t!;v 33@33.P 3 ҃+@sH]UN~F V ؋]UFЋF ] 6r"^&&W&G$&G;F s Wv $X^F&F&GFFF;FsN ;Nv$&@FFڋF;Fr ,$v@^&Z&WS$&_[&GU|s]$&G@] ar $&G;FsGv$X^F&F&GFFF;Fs$&@FFFU>$u$P u>$t$&G$$>$u]ð]UQQ$P$ %%P uJF6$P u8%=u0$P u!F6$P u$=t=!t3]^ &G :~uSvv^ &G :tWSvv<n^ &G ^ Svv<FNs=u8^ SFP~u#^ &G ^ &dt@Fs률^ &G F,^ &G :r^ &G :tw&G 9Fu9Fu^ &G&WFV^ &G&W;Vu;Fw3&G^ &O^ &O^ &O&W;Vu;Ns+^ &r &G&;Gwe^ &G &W"N~;u;wL&wщFVN;u;s&+O &"N։~؋F^ &G-sSDF u^ &G-sG<PFPdF^ &G-FVFVF%Ff^ &G^ &G^ &GNV^ &O &W"^ SPFPFPDF u4F^ &G^ &G :t :Tt^ SjLF t^ &G&G &W"FV&9Wu&9Gw&G&W9Fu9Fu^ &G&WFV^ &G&9G*s&G*^ &FF^ &G@1&@FތFF^ FV&9W"u&9G v&G*H1Fܺ&G &W"N~;u;r_F&+O &"N։~؋F։F&O,r&9G*sSl<F tF^ &G^ &G*&;G(uF&G(F^ &G* ^ F&9G*s&G*^ F&9G(v&G(Fr^ Sj$F u^ Sl<F uy^ &G ts&w8&SP^ &w"&w G<P^ &w: dF t@^ &G-^ &G &W"&G4&W6^ &G&G.^ &F&G0Z&W2~Yt^ &G@1&W^ &w&@F&Z&W^ &GN^ &O^ &OF~+&G &"^ &G&G(^ &G&G*^ &G,^ &Yti&w8&Sh^ &w"&w FP#Fu^ &?^ &G,(~t^ &G&GF^ &G :t ^&FF^&G &W"&O*&;Wu&;GrI1&G^&G*1 uSj$F u`^&G@1&@FF^&G*1&G &W"FV&w8^SQRPFP#FtK uX^&G*1V+^0^~&}*9^Y^&G*H13^SjF u/v&|*&L+^9 ^&G*&G^&G,^ &G :~uS^SzO^ &G :t S^S<6^ &du^ &G ^ S^SF^ &G FU^&G :r^&G :t:Tu^&G&G &W"^&&Wc^&G :uX&r&G&;Gv &G&W^&G&G &W"^&&W^&G s7&G s/^&/&_!^&G :u^&&G ]^&^ &&W^&G :t ^SDF uk^&G;s]@1V&G&G &"F~&w8&XSv^&pWPG<P^&w:dF t@^&G-F^&GFrF@1V^&G&G &W"FV&G-sG<PFPdF^&G-3^&w8v&XSv^&pvvFP#FNVF׉NV~u t%^&9Wu&9Or&O&WFF t ^&Gv^&@F&Z&W^&GFV^&G &W"^&G&W;Vu;FYvF&GF^&G8^&G^&G&W&+G &W"FVF&G^&uFF %~6F =wmt =mmt=amu dF =rmt=tmuF smhFPjFt;v ^Sv^SvFPF t=c=u ~W=t %~6FV^&G&WFF&Z&WF1&G&G;YsF^Sv^GPjFPF ui^&G(&W*&G&W~ tmu)&w&w^Sv^S^GPF uA~^&G &G SjjF u^&G &w&wFFU^&G(F&G F&1t SvL^&/ut~ u@&G:r8S PLF u^S PLF th^SvPTU^SvLF uD~ u ^&G:1^&G:'^&/u ~ uS P^SvLFF]UQQ^&OBN&GE1+ʉN&GE&OD;sF]UF^ &G(^ F&)G ]UQ^&/tS PLF u&^&/tS PLF u ^&GE]U ^&G(F&GEF&GBF uP&GEY1+ʉN&GE&OD;s S6TlFF;Fr\^&GE&:GDuS6TF uD^S PLF t!^SvFHPTF^&GEF^&GEFu]U^ &wĄ FF^ &_ćL FF~ ~t u PF ^&NFFt(#^H^&Z&Wv#^&^&:F t v&Z&T] U^&G(F&G F&1t SvL^&GQrFF^SvFPHTFw^&:FuFFHN;s[^&F^&OE&:ODu< t< tS6TF u{^SvLF u~^&/u~ t^&/t ~ u&GEF< t< t < t^&GEFtk~ uS^&/t)S PLF u\^&GE^&/u^S PLF u^&/uz`^&GE&:GDuF< t< tS6TF uUF< t:^SPLF uF{ F{ ;FsF~ t ~r^Fxz~v@PFN ^㉇CV%xzV+V'|~V-V1sV)V/FP^GP^&GPRPjhrmF t?^&Ow! F^&G!!v QP,v^ĿxWhjjFP#F u3FFv^ĿWPvvFP#F tv F) v F u ^&G}hjFP/LF^&G F A:r1 u ~rF^&G]Un^ S Pv ^SF^&tF P^ Sv PNQNQNQNQNQNQNQNQNQNQPPF u~u^SvКdF t]U PPX1P/LF uAX1&G 1\1~I1< t< tY^S^SvFPcdF u^>1 u ^&r>1 u.^&s$S^Sv^Svv ^Sv$~ wmu~~s ~ mmuIF^&G?Z&WA^^&GZ&W^&G$^,^&GZ&WF-,`F =wmt=amuF^&GZ&WF^&G$>F =rmt=tmuTF^&G?Z&WA^^&GZ&WF-^&G"~u"^&GAH1FP1PuFP^v@PFF+PRPPrmPF~u>v^SPPPFP#F t v Fv F t( ^&?t' ^&G^&G^&G^&G^&G^&G^&G^&G;^&G ^&G=^&G ^&G.^&G ^&G/^&G^&GG^&G^&GHF =wmt=amu~ mmu*F =rmt=tmu ^&G ^&G ^&G(^&G,^SCF u/1F^P^SP^S^SF t^&G F]^ &G :t:*t :t:?u^ Svv^ &G :t-:t':t!:t:t:t:*t :?t~ wg^ Sj 1 u^ &FFv &t^FF^.5\8X0YnFse;v[;u ^ &rJF^ &G^ &v&s5&On?&w+ @ &Gn^ &Op៵&w6^ &On?&w+ @ &Gn^ &Op៵&w &Gp^ &t38Fvr ^ &u~F^ &G^ &v&Go$&w &Go^ &s5&On?&w+ @ &Gn^ &Op៵&w6^ &On?&w+ @ &Gn^ &Op៵&w &Gp^ &wxj ^ &wx&wo ^ &wxj ^ &wx&wn ^ &wxj ^ &wx&wpd^ &tt^&7 F%F^ &s+&O F&uN^ &uN ^ &G F~Kw-F^ &GqF^ &Gs^ &wj%F uvF^ &Gv^ &w>&Go$&_v˷ ^ &Go^ &wxj ^ &wx&woA^ &tub^&7 F^ &vufN^&7v#^ &G :tRF^ &G86^ &G :t9F^ &G6^ &G :t ~w8F^ &G.Z^ &G :u K~wF^ &G/)~vF^ &G^ &G :u&Gt tFF^ &G :t&Gtt ^ &gn^ &On ^ &9we&wxP ^ &wxF$P ^ &wxj ^ &wx&wn 'Ft 1tF1 u~uDRPjFPF u ^&G5У11v^ SvRP1P#F>1tv3P1PF1vP1PjF uiFH;1sBFFV1111v^ SvRP1P#F>1t{1111;1u;1rV^ 61&^&>1u'^S1P8F>1u5 511^&? u& 15>1t1&F;1u;1s)11H1 v^Sv^ Sv F PhjF uU^&FV~u~wov^SvFPFw|~t~ uFV^&_F:5u!5sv^SvFPF u5F< t0*< w#FFV YNY v N^& 1tF+FFF+F1F;FtFFHN;r"v^Sv^&0F ugFuӊFsv^Svj F ucN1>1;1u;1v)vRQ F u5vj1Pj F uv^Sv6161FP$FFF;vP1;vH V1>11>1v^SPWR1P#F>1tF )1)FFV16111+lj^FNvv1PhVQFP#F~tFFVFVv3QhRPFP#FFFHN;r"v^Sh^&0nF u6FuӋF FtF9Fv~~ ~tvv^Sh16F udFFVFV uv^ShF u6FV11N1v^SvRPFP# ~u31FFVFVv3QhRPFP#FF# F'F9Fs 1F~uF FF t-ȋF10vBF1VF 1Fv^Sv^ SvFPvy FH1;ruN1>1;1u;1vv RQ F urFFV5s&v ^SP1>1+WQ1P$F.v ^Sv61611P$FFV11>1uF1F^61&1 N1>1;1u;1vv RQ F uf11>1;1u;1t+NVv jFPj F u*FV11v ^Sv6161FP$v^& XV^F&t4^&u ^&?u!v^&@F^&^&GFF, Fv^F&9@su7~u~t^&G &;G$s&G0r&G2r &G3r^v^&x6u FFKv^&@VFF u/~uv^&@J vF^&@Bv^&x6u ^&GTv^&@6 F^&GF^&v^&@B^&G^&GF^&GF^&G vF^&@FvF ^&@NZ&PP~uav^&pBFPP(F V ;Vu;Ft<svFPm\F^&GF^SvF F+ FF^ &dtZSFP^& uV^ &du&G-sG<P^Sd^&^ Shwmvv^& u^ &G ^&^ &Gd<tN<uShL^& uH^ SFP^& u/^ Shrmvv^& u^ &G ^&^&GFFF ;F r^& u&G,&;G(r &O$+ȉN ^&G FN F +;NsN^v&t,0^~ 9N^Y^F&^F&)G ^F&G,^&G,&;G$u&G,^& tFF Q^& u) ^&_ğ"^F&GF^&GF^&GF^&F^&GF^&GF^&GF^&GFFHN;tFH;uF;Fu* FNF;rE;Fu^S^SQF@^S^SvvFPF u.^S^Sv ^S^SvFHPFPFNFȋV;r +V+FFFFF^&GF^&GU].6] ^&^SP$F t^&G t~&w8&SP^&w"&w G<P^&w: dF t@^&G-^&G &W"&G4&W6^&G&G.^&F&G0Z&W2~Yt^&GFu^&G@1V&G&G &W"F^&Gv^&@F&Z&Wv^&@&G^&G*^&G(^&G^&G, ^&G :t :Tt F^&G-rG<PFPdF^&G-^&G0FF^F&G4&W6Ft.H^&O.+N^v0^9^Y^&O.N^F&)G.^v^&G0Z&W2F^&.uF tuSvF tF^&G0FF^&w8^S^&w.&w6&w4FP$FFt.H^&O.+N^v0^9^Y^&O.N^F&G4&W6^F&)G.^v^&G0Z&W2F t ^&.u%FsFr^ShF u^&G :t :Tt ^&G&WFV&O&O &"N~;u;wN~Fs FF%R6u &6&G%&6&GR6B6&GB69R6]U>J6u &6&G%&6&GJ6B6&GRB6S8J6]U>L6u &6&G%&6&GL6B6&GB68L6]U>N6u&6&G&6&G&6&GN6B6&GB68N6B6GP4 PB6&GPV6P06B6GP5 PB6&GPX6P069V6u9X6t &6&G &6&G]U8P6 P6P6V6P068P7 P6P6X6P069V6u9X6t &6&G &6&GB6&O)t+w*&6Z^YB6&G)&6&G &6&G&6&wZ8P6&6P6&G]UF$6\v^Sv4L]U^ &GF^ &Z&W^ S^Sj\L]$6Z8 6"6B6&ORJ6wS8FB6&OL6w8F&6&Gs66N6626B6&ON6w8F&6&Gs<6P6686&6&OP6Z8F&6&GrJ6&6&GrL6&6&GrN6PZ8QT6Q$6Qj\P8Q6J68Q6L68Q6N68Q6P6P9Q6R6PPt06 t Fr>06uFs}^J6 t8Z8J6FL6 t8^Z8L6FN6 t8^Z8N6F8^Z8P6FP6F$6B6&_)Z8F6&&_&6&Gs$6B6&O)+&O$6B6&O)+F6&G F&6(6&Ƈ~s) ~N&6&Ƈ&6&&6B6D6F*6,6N .6&6&GZ&WF &6&G&6&Ƈ*6SF PPFP0SFP'S06 t~uFFFA9F rD*6'&8u98Nu4O*6,6).6&6&OZ&W.6&6&O&6&i&6&_S8 P&6&wV6P06 u[&6&_S9 P&6&wX6P06 u39V6u9X6u&6&Ƈ&6&B6Sj_06 tP*6S6.6P8QJ6Q8QL6Q8QN6Q8QP6Q9QR6QPP06 tA>L6t>J6u B6&GR>L6tq>N6uj>P6uc06FsH^Sv B6GPB6&GP^Sv6F=c=t=V=t=W=t !tt06~t>J6u>L6u>N6tFB6&G)P(9QT6Q.6QjiP8Q6J68Q6L68Q6N68Q6P6P=P(9QT6Q.6QjiP8Q6J68Q6L68Q6N68Q6P6h9Q6R6PPt06>06t06 u406 ui06 u&6&Gr&Gs&Gr >P6ux06 u&06 u&6&GrB6GPB6&w4sB6GSPB6&GRPGPB6&GPGPB6&GPZ6Ph&06 tGr^Sv B6GPB6&GP^Sv6F=c=u~t&6&G&6ZP&6&w4s( B6GSPB6&GRPGPB6&GPGPB6&GPGPB6&GP&6GPh<d06 tC s7^Sv B6GPB6&GP^Sv6F=c=t&~t06&6&G&6&u&Ƈ B^&GF &6(6؍B6D6FF6H6B6GS&6&GZ&WB6&GR&6&GB6G&6&G Z&W B6&G&6&G &6&8u*&6&u&Ƈ&6&Gs&u26P66P(F tI&6&uSB6&G66;t@Fs]RPGP26SQFP|SF t~u,F&B6GPB6&GP26S6662,FFscB6GSPB6&GRPGPB6&GP26S666B6GPB6&GP&6GPh<dF uf&6&G&6&Gs]&u^ S^S&6GP86P<6P&6GPEdF t&6&Gr&6&Gr&6&uH<6&9GtANsYRQ&_S86SP FP)SF uB~u*F$&6ZP&6&w86S6<62,FFrjFB^&GF &6(6؍B6D6FF6H6B6GS&6&GZ&WB6&GR&6&GB6G&6&G Z&W B6&G&6&G &6&8u+&6&u&Ƈ&6&Gs&u26P66P(F tI&6&uSB6&G66;t@Fs]RPGP26SQFPSF t~u,F&B6GPB6&GP26S6662,FFscB6GSPB6&GRPGPB6&GP26S666B6GPB6&GP&6GPh<dF uf&6&G&6&Gs]&u^ S^S&6GP86P<6P&6GPEdF t&6&Gr&6&Gr&6&uH<6&9GtANsYRQ&_S86SPFPlSF uC~u*F$&6ZP&6&w86S6<62,FFrvF U^&u && t&&06]9Pj<: PjRPj^Sv ^SvvF=4u/9Pj9mJuh9P*F th9P*F u9SP9SPF~t"9Sh+F9Sh+FF>9mJu@Fs fF u/9Pj9mJu@Fs F u09Pj9mJt˸9Pj<F t9>9mJtø9Pj<F9Sh+F9Sh+F9FF;F r) ^Sc PvFPF uߋFtFv~ N^Y^ v&:^ v&@ >9mJu@Fs F uN9Pj9mJu@Fs JF u׸RPP^ Sv ^SPFPhlF u\RPPe Qj^SPFPhlF u09PjF w0 F A^v&FFVFV눋F *~t)vvFPFFPFP0 F t^ Sv FPFִP$ *~t)vvFPFFPFP F t^ Sv FPFִP$ F FF t9F t~u ~uNF 1Vº1VF1VF1VF1FFPF1ZЋFR1ZЋFFR1YFF0^ v&aF tN +^ 0FY~u~t *~ N F +F UF ;FsFv~N^YF] *^&FFFFF^&G;FwFF9F vNu*^vPFP8F~v#^v&8%t^&;wrh^v@PFP8F~vh^v&@F0r9vhF0F^v@PFP8F~vh^v&@FF;Fw^v&?F]~Sucv^&^F&Sh P^&wFPF~u ^&GF^vPF +P^&Sv$s~Nu0v^&^F^vPF +P^&7$ȃ~Hu9v^&^ތF^vPF +P^&S^&w{$r~Du4v^&^ڌF^vPF +P^&w&7\$8~Tu7v^&^֌F^vPF +P^&w&7$FhF^v&^v&FFFFF^S^ Sv FPj$F FFFFF^S^SvFPj$ FFPFPF u*Fs ~ v~sFr~ v ~ rFjFPjF t@~uA"9Fu^&?*u N^ &9^&~u ~t@~uF^&F<*tF9Fv^&8*u N^ &FFFHN;sr^vPF+P^PF+P^ PFP,s^vPFP8FFF뜀~?u}~u ^ &^SFP8FFF^vQN+Q^ QN+Q^ PFP,rvNF^ &FF^&F^PFP8FFFFFF9Fv6^vPFP8FFFu^v&F<*tjTF~uv&<tF~to~tEv&<u<^&?9t9999~t Pj^Sv Pj Pj^Sv Pjx Pj n9P9S69^Sv hrmF ul69j^ShF tFJF9969^ShP$RPFP#F^99O99N 9.9 9uN9FF>9s 9&?uJ9@9699ShP$RPFP#F t^FU9^G999G^ &Z&W9&^&9@9#@^9969 F9 ^SvFPFPj|F u5FPF PFPjX|F uF;F vdS~ vH ~^vNFY^vx FF^&F F t~u5^&~u^S^Sv^ SvFFUFF F u4vvvjjFPj j{j}jTF#t F#t)Fv^@‰FVvvvjjFPj j[j]jTF#tF#t)Fv^@‰FV~t~u v&<jTF#ukF#t)Fv^@‰FVvvvvv v vj2jj^jTF#u$v&<uvvvj2vv VTF~uFF F FuFFPFPFPjj^X|F uF F;FvdbF F2vRF t$N t~^Y^vFFv~N ^YFFF ^&F Ft~uF F t~u=^&~u'^S^Sv^Sv^ SvFFUFF F uRvvvjjFPj j{j}jTF#t)F#t)Fv^@‰FVvvvjjFPj j[j]jTF#tF#t)Fv^@‰FVvvvjjFPj jjTF#tF#t)Fv^@‰FVvvvjjFPj2jj^jTF#uWF;Fs v&8^uFF#t)FF~tv~vvvj vv v vTF~uFF^S PvFPF uJ~u ^Sv^SvRPjFPFPj F~t ~s ~u ^&GM&_O^&GL&^v@^&GMZ&WOF@N+^&OL^S^Sv^Svv ^SvDF uF^ &^S PvFPF uFt^ &FFF~NuV~u ^&P ~u^&7b:P^ S~u8^&w&7b:P^ Sb:F^~Hu2Ft tuS^Svb:P^ Sb:F^~Du_~uFPF~u^&&WFV, PRPvvvb:Pj ^ S Fb:F^^S^ &7^Svv^SFU&:Pj:t'~tv &*: v &*:&4v &^&~tv &<&M&U&;Pu&;Hs4DF^&p4v&Z&TF^&A&DF끸4F=FF&Z&W<=&GF@=Y] <=& FF<=&GNȋ@=;v+ЉV^6<=&t8vNFY<=F&G v ~FF=s=r~sF-F-F~to~ vFt ^8 s~u~uF1 t ZFPF%mY^ NHF=v ĊFFF@^&*^+vN FYF ^&7^&:^&8^S~<s 9Fw9Fw 9Fw9F vF~t:^&Ƈ{^v NFY^v&ƀ}FFF~tC^v&ƀ[^vvNFYvv^&ƀ]FFF^v&ƀFF@^&*^+vN FYF ^&7^&:^&8^S^&8&8uSoF tb^&8F&^ &^v@^&Z&WF^ &@F^0~^YF^&8^&8rM^P^&*P+P^&7P&:SF u^&LJ8^&:FU^SvPl]ULFs+PPFP/LF u,^&!t@FF^ &FPF usFFFFFNNFF @FF^F FsFs PFP  FPF~u[vFPF tF;FtFF u$ 8FvFF^ &ȍvF!uFFFΈFψFбNѴFҋVVԉFF.F FڌF܋FFލFF^NFsFs PFP  FPF~uGvFPF u6F;Ft )F։F u F^ &~!t FtFF]^[Comm]C[Comm]D[Comm]C[Comm]D[sys]CmNull.run[sys]SignOn.run% % ^dCT^}]??0?? ...%0S: %0S [Sys]Exec.runnt]fileHeaders.syst (t) Copyright 1989 Unisys Corporation, All rights reserved. t>/tSystSyst[Sys]Sys.Font t[Sys]T1Sys.Font$t[Sys]BAWSSys.Font>t[Sys]V1Sys.FontZt[Sys]Signon.runttVFtVFCtmfd.syst DiskPartitions.systEXt (OS t) tVFPF t[VID]t[VID]1t[SPL]tC(tC0t[Scr]<$>submit0.tmp:t[Scr]<$>submit1.tmpTtsubmit0.tmpnt submit1.tmpt [sys]ExecMsg.bintMessage not foundt Log file: Disk is formatted in ECC mode.Disk is formatted in CRC mode. CYLINDERS=TRACKS=SECTORS=BYTES=STEP=PRECOMP=SPIRAL= REMOVABLE=YESNO)This is an ST-506 device (FP-controlled).&This is an SMD device (DP-controlled).+When performing MIVolume on an ST-506 Disk,CDO NOT enter bad spots with sector #16 when using 16 sectors/track.5(Reference -- 16 sectors are labeled #0 through #15).\t2Unable to access or use message file: Error 剖tReading text file ...扳tWriting binary file ...t done. t cannot be accessed.4t/ An error number does not follow a colon near: 44t Invalid error code near: 4Vt2 Message too long or message number invalid near: 4t. The text file does not contain any messages. 4t' Invalid delimiter for message number: tText File Name : tBinary File Name : +t* : ** WARNING ** Multiply defined message ]tJ **** Available memory not enough to perform the requested operation **** t+ The text file contains too many messages. tCreating text file ...tReading old text files ..."tCreating new text file ...%%(){}[]<>?#^- '"0Uu9dD#erc = , .   ... Clt  LH8$xd?*j<(|h OJ KF;&{f2!ra.nY+kV3"sb:%ze0 p`DeviceNameDe;9         ~[KBD][VID][]}[!Scr]]$$.Tmp}[!Scr][!Scr]. t[PTR]0123456789abcdef[scr]<$>BsFilter.tmpVNVF2Knn,X` %K& $ % * - II021B02 MinRecordSize MaxRecordSize BlockSize DensityCode SpeedCode UnbufferedMode ServiceBufferSize TotalServiceBuffersEraseOnClose RewindOnClose   config.sys[sys][!sys]II120A00SYSSYS8251Config.sysCommPtr&&II120A00p*?*?*?[Sys]ErcMsg.bin[!Sys]ErcMsg.bin^^: ^{}MASTERSERVERLOCAL{}[] []{}[]<>^{}[]mfd.sys<>[sys]LptConfig.Sys&Error 2624: msg= %0N maxlen= %1N^YesNo`abcdefghijklmnopqrstuvwxyz{|}~`abcdefghijklmnopqrstuvwxyPress NEXT PAGE or SCROLL UP to continue t(Press NEXT PAGE to continueN t!a?!*a**2Q=\z`gTD aAdDhHmMnNoOsStTwWyYgG!oo!/!0d!/!0y! !hh!:!0m!!2AA!!*o!/!0d!/!0y! !*h!:!0m!!2*A!"!Nnn! !dd!, !yyyy! !hh!:!0m! !2AA!"!Nnn! !*d!, !yyyy! !*h!:!0m! !2*A!(!Www! !Nnn! !dd!, !yyyy! !hh!:!0m! !2AA!(!Www! !Nnn! !*d!, !yyyy! !*h!:!0m! !2*A! !0t!:!0m! !*t!:!0m!!hh!:!0m! !2AA!!*h!:!0m! !2*A!!0o!/!0d!/!0y!!*o!/!*d!/!0y!!0h!:!0m!:!0s!!0t!:!0m!:!0s!.tmp!W*w! !N*n! !*d!, !*y!!N*n! !*d!, !*y!"!0o!/!0d!/!0y!-!0h!:!0m!:!0s!!2*A!!Nnn! !*d!, !yyyy!Invalid Template Index$Cb %6FVfzCKACTION BACK SPACEBOUNDCANCELCODECOPYDELETEFINISHGOHELPLOCKMARKMOVENEXT NEXT PAGE OVER TYPE PREV PAGERETURN SCROLL DOWN SCROLL UPSHIFTTAB#+17?GKQW]citTN00sundaymondaytuesday wednesdaythursdayfridaysaturdayjanuaryfebruarymarchaprilmayjunejulyaugust septemberoctobernovemberdecemberampmnoonmidnight05 invalid namesunmontuewedthufrisatjanfebmaraprmayjunjulaugsepoctnovdecampmnm05 %0:BLU_fmrx~ #(-27;?BEI{R12.3.0[Kbd][Vid] [Lpt][Ptr].$[Nul][Comm]$[8251]d[Debug][SysIn]T[SysOut]>T,$!#t>%)*]7u8\|3; Le"C|$4|&P+, l- ., /$01Dl2t{l4P 5 6D4LL44LL4DLL4a4]4y444]4 y444.\B4\4B.\4~VZ]4y44\$4~V 4~V \$~V4t[t4t[tt[t4t[t 4LOll4  d4]4|44y]4y44 T4]4y44 4{TTy442<<;< 4l zz Error opening translation file: ![Sys]PtrAConfig.sys @?[KBD][VID]>%t>%t[sys]CommXconfig.sys ? @? @       !"#{%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`ABCDEFGHIJKLMNOPQRSTUVWXYZ{|}~   LIBRARY: ctos.lib VERSION: R12.3.1 (friday november 12, 1993, 17:19) LIBRARY: ctostoolkit.lib VERSION: R12.3.1 (friday november 12, 1993, 17:21) LIBRARY: enls.lib VERSION: R12.3.1 (friday november 12, 1993, 17:22) LIBRARY: exec.lib VERSION: R12.3.0 (monday november 15, 1993, 14:14) COPYRIGHT (C) 1980, 1993 CONVERGENT TECHNOLOGIES, INC. ALL RIGHTS RESERVED. COPYRIGHT (C) 1980, 1993 UNISYS CORPORATION. ALL RIGHTS RESERVED. THIS SOFTWARE IS PROPRIETARY TO CONVERGENT TECHNOLOGIES, INC. AND UNISYS CORPORATION AND IS NOT TO BE REPRODUCED, USED OR DISCLOSED EXCEPT IN ACCORDANCE WITH PROGRAM LICENSE OR UPON WRITTEN AUTHORIZATION OF THE PATENT DIVISION OF UNISYS CORPORATION. THIS PROGRAM IS FURNISHED UNDER A LICENSE RESTRICTING ITS USE SOLELY FOR THE OPERATION OF A DESIGNATED COMPUTER FOR A PARTICULAR PURPOSE. TITLE TO AND OWNERSHIP OF THE PROGRAM, INCLUDING ITS SOURCE CODE, SHALL AT ALL TIMES REMAIN IN THE NAMES OF UNISYS CORPORATION AND CONVERGENT TECHNOLOGIES, INCORPORATED. VERSION: R12.3.0 (monday november 15, 1993, 14:12) request when .* "New" is highlighted on the "File" pull-down menu. .************************************************************************ :h1 res=CREATENEW_HP name=CREATENEW_HP.Help for New :i1 id=new.New :i2 refid=open.Opening a new file :p.Select :hp2.New:ehp2. on the :hp2.File:ehp2. pull-down to create a new file. :eh1. .************************************************************************ .* FIND, EDIT FIELD HELP PANEL - This panel appears for a help request .* whenescribed (``0'' to ``2'').X.25: Subaddress not numeric or out of range. The value assigned to this variable is not numeric, or is not in the range of values prescribed (``0'' to ``9999'').X.25: Access Point Handles is not owned. The calling application does not own the access point handle specified in the call.X.25: X.25 Gateway out of VC buffers. Internal error. Call your Unisys representative.X.25 LAPB: The location field must contain information in the following order: BNet node name, shared resource processor board name, and service ID.X.25 LAPB: There must be two complementary delimiters.X.25 Packet Layer: Deinstallation is not permitted while a call to NotifyNextIncomingCallNet or WaitForX25IncomingCall is outstanding.LAPB: There has been a fatal error in the link level system service. To recover, you must deinstall and reinstall the system services in the following order: deinstall network layer, deinstall link layer, install link layer, install network layer. HDLC LAPB: There has been a fatal error in the link level system service. To recover, you must deinstall and reinstall the system services in the following order: deinstall client server, deinstall link level, install link level, install client server. HDLC NRM: There has been a fatal error in the link level system service. You will need to deinstall the NRM link level and then reinstall it. You will need to deinstall any network level application before you can deinstall the link level.X.25 Packet Access Method: There has been a fatal error in the packet level system service. To recover, you must deinstall the packet level and then reinstall it.X.25 Packet Access Method and LAPB: There is a duplicated address in the valid address configuration file. Check the ValidAddress.Config file and delete the duplicate entry.X.25 Packet Access Method: An address in the valid address configuration file is out of sequence. Address entries must be sorted in sequential order on the first digit.X.25 Packet Access Method: An address in the valid address configuration file has a non-numeric value. You can only use numeric values for address identification. Check the address entries in the ValidAddress.Config file.X.25 Packet Access Method: An invalid priority has been specified in the priority array table or in the CALL REQUEST facility negotiated. The valid priority values are 0 through 3, with 3 as the highest priority.X.25 Packet Access Method: Priority array table queue malfunction. An unrecoverable error has occurred in your priority table. Reinstall the packet level system service.X.25 Packet Access Method: One of the parameter fields in the packet level configuration file has been altered. No changes are permitted to the parameter fields. You may have deleted or added a character to one of the fields by mistake when you set the parameter values. Refer to a copy of the original packet level configuration file (X25PktParam.Cfg) and enter your parameter values again.X.25 Packet Access Method: The value of the maximum packet size in the packet level configuration file is invalid. The valid maximum packet size values are 16, 32, 64, 128, 256, 512, 1024, 2048, or 4096.X.25 Packet Access Method: The packet retransmission parameter in the packet level configuration file has an entry other than Y (Yes) or N (No). If you have selected Y (Yes), check with your PDN service to see if your subscription permits packet retransmission.X.25 Packet Access Method: The link description parameter in the packet level configuration file  has an invalid link name. The only valid link description entries are LAPB and NRM. If you are using NRM, you must also enter a station address. The link description and station address must be separated by a space. For example, NRM 17.X.25 Packet Access Method: The packet level configuration file specified either could not be found or an incorrect file name was used. Check the file name of the configuration file you want to use and try to reinstall the system service.X.25 Packet Access Method: The check address parameter in the packet level configuration file has an invalid entry. The only valid entries are Y (Yes) or N (No).X.25 Packet Access Method: The Retry counter parameter in the packet level configuration file has an invalid entry. The default is 20 retries and corresponds with the CCITT standards. Do not enter a higher retry count value without first checking with your PDN service.X.25 Packet Access Method: The T23 Clear timer parameter in the packet level configuration file has an invalid entry. The default is 180 seconds and corresponds with the CCITT standards. Do not enter a higher clear timer value without first checking with your PDN service.X.25 Packet Access Method: The T22 Reset timer parameter in the packet level configuration file has an invalid entry. The default is 180 seconds and corresponds with the CCITT standards. Do not enter a higher reset timer value without first checking with your PDN service.X.25 Packet Access Method: The T21 Call timer parameter in the packet level configuration file has an invalid entry. The default is 200 seconds and corresponds with the CCITT standards. Do not enter a higher call timer value without first checking with your PDN service.X.25 Packet Access Method: The T20 Restart timer parameter in the packet level configuration file has an invalid entry. The default is 180 seconds and corresponds with the CCITT standards. Do not enter a higher restart timer value without first checking with your PDN service.X.25 Packet Access Method: There has been some internal error within the packet level. Deinstall the packet, then reinstall it.X.25 Packet Access Method: The maximum user data size in the link level has not been calculated large enough to accommodate the specified maximum packet size.X.25 Packet Access Method: Conflicting packet size. Maximum packet size and default packet size specified in the packet level configuration file are incompatible.X.25 Packet Access Method: The entry made in the packet level configuration file for the number of permanent virtual circuits is not numeric.X.25 Packet Access Method: The entry made in the link level configuration file for the Wait for DCE ACK parameter is not Y (Yes) or N (No).X.25 Packet Access Method: The entry made in the packet level configuration file parameter for number of VCs is not numeric.X.25 Packet Access Method: Incorrect packet size. The packet size value used in the packet level configuration file is not valid. Valid values are 16, 32, 64, 128, 256, 512, 1024, 2048, or 4096.X.25 Packet Access Method: Invalid incoming-only LCGN. Value specified as the LC group number for first incoming-only VC is not a numeric entry.X.25 Packet Access Method: Invalid incoming-only LC. Value specified as the LC number for the first incoming-only VC is not a numeric entry.X.25 Packet Access Method: Invalid incoming-only VC. Value specified for the number of incoming-only VCs is not a numeric entry.X.25 Packet Access Method: Invalid two-way LCGN. The value specified in the packet level configuration file as the starting LC group number for first two-way VC in not a numeric entry.X.25 Packet Access Method: Invalid two-way LC. The value specified as the starting LC number for the first two-way VC is not a numeric entry.X.25 Packet Access Method: Invalid outgoing-only LCGN. The value specified as the starting LC group number for the first outgoing-only VC is not a numeric entry.X.25 Packet Access Method: Invalid outgoing-only LC. Value specified as the starting LC number for first outgoing-only VC is not a numeric entry.X.25 Packet Access Method: Invalid outgoing-only VC. The value specified for the number of outgoing VCs is not numeric.X.25 Packet Access Method: User data is too large. The following requests can return this error if the user data specified is too large: PAM procedures: InitiateX25CallNet, AcceptX25CallNet, ClearX25CallNet, WriteX25PacketNet, WriteX25InterruptNet, and WriteX25LongInterruptNet. APM procedures: StartX25Call, AcceptX25CallNet, ClearX25VC, and X25GroupWrite. If the error was returned from the AcceptX25CallNet procedure the gateway clears the call.X.25 Packet Access Method: Bad Incoming Accept call. The Accept Packet received by the gateway contained an invalid facility request. The call was cleared.X.25 Packet Access Method: Bad Request Facility. Bad Request Facility. Improper window or packet size values are specified in optional facilities. The accept packet has an improper value or the original incoming request had improper data and was not overridden by the accept. (Specific to InitiateX25CallNet or Start X25Call.)X.25 Packet Access Method: Bad Accept Facility. Improper value in the incoming accept packet per-call facility data. The gateway clears the call (specific to AcceptX25CallNet).SNA Transport: The parameters specified for the Call conflict or no VC type has been chosen.SNA Transport: The specified X.25 optional facility is not available.SNA Transport: The Closed User Group (CUG) index is too long.SNA Transport: SNA request unsupported by the host.SNA Transport: Incorrect NmvtType(s) specified in ReadNmvt or WriteNmvt.SNA Transport: Incorrect or no password specified in Attach request while attempting to attach to a suspended LU.SNA Transport: Transport Service deinstallation unsuccessful due to active LU-LU session(s).SNA Transport: Multiple Gateway Server service not available. A Service ID was given at gateway installation or a location parameter was specified in the status monitor, deinstall, SNA X.25 call, or SNA X.25 clear utility when the MGS was not installed.SNA Transport: Multiple Gateway Server ID missing. The status monitor, deinstall, SNA X.25 call, or SNA X.25 clear utility must have a location parameter specified if the gateway is running under the Multiple Gateway Server.SNA Transport: Invalid Multiple Gateway Server. Service ID was entered without leading and trailing angle brackets as delimiters.SNA Transport: Invalid timer value entered for SDLC Primary Idle Detect Time Out Parameter.SNA Transport:  The Data Link Manager has not been installed on the system.SNA Transport: An invalid function has been specified for the Station Control request.SNA Transport: An attempt was made to use an SD string containing information that is invalid for this DLL.SNA Transport: Invalid PU type. Node type can be "2.0" or "2.1" only.SNA Transport: Fatal error in the Transport Service. If this error occurs, perform the following steps:  Use the PLog command to determine the error  Deinstall the Transport Service and the data link using the appropriate data link deinstall command  Reinstall all the SNA Transport softwareSNA Transport: Fatal error in the Transport Service. Deinstall the Transport Service and the data link. Then reinstall all the SNA Transport software.SNA Transport: An unacceptable value was entered in the Auto Start parameter of the X.21 CSS configuration file for the SDLC DLL.SNA Transport: A value other than Y (yes) or N (no) was entered in the Short-Hold Mode parameter of the X.21 CSS configuration file.SNA Transport: No Short-Hold Mode address was specified in the X.21 CSS configuration file.SNA Transport: An invalid Short-Hold Mode inactivity time was specified in the X.21 CSS configuration file.SNA Transport: Reserved for X.21 Circuit Switching Service (CSS).SNA Transport: A communications line for the X.21 CSS is not active.SNA Transport: The X.21 Facility Registration/Cancellation utility failed.SNA Transport: An X.21 utility request is being processed.SNA Transport: Invalid Set Type on the CNMStatus Call.SNA Transport: Invalid Function Type on the CNMStatus Call.SNA Transport: The link is in an invalid state.SNA Transport: The maximum number of independent sessions is in use.SNA Transport: The session has gone inactive.SNA Transport: The chip type was not recognized as supported.SNA Transport: An invalid trace buffer size has been entered.SNA Transport: Tracing is not allowed. Buffer space was not allocated during installation.SNA Transport: An attempt has been made to stop a trace that was either already stopped or never started.SNA Transport: An APPC application has sent a PIU with a length greater than 265 bytes.SNA Transport: An APPC LU range has been configured and has sent a PIU size of less than 265 has been specified. To configure APPC applications the PIU size must be 265 bytes.SNA Transport: Too many LUs have been configured for the PIU size specified. Reduce the number of LUs configured.SNA Transport: The LU number specified by an application does not corres pond with the Transport Service LU range configuration. Install the application with an LU number that is in the range configured for that application type on the Transport Service.SNA Transport: Either a 3270 (CRT or printer) has specified an LU number of 1, or an invalid range has been entered. Check the Gateway configuration values. Note that LU number 1 is invalid for 3270 devices.SNA Transport: An LU range has been specified that is not within the minimum or maximum LU number range. The range is greater than or equal to 1 and less than 254.SNA Transport: The same LU number has been specified for two different devices. A particular LU number may only be used by one device type.SNA Transport: A non-numeric character has been entered for an LU range.SNA Transport: An invalid LU range has been specified. Specifically, the range goes from a high number to a low number (for example, 12-3).Multiple Gateway Service: Invalid name supplied in MGSRegister Request. This code is returned in response to MGSRegister Request. BMULTI: Invalid or duplicate Service ID.Multiple Gateway Service: Not enough gateway types configured. Deinstall MGS and reinstall with a lrger value for the [Number of Different Gateways] parameter. This code is returned in response to MGSRegister Request. BMULTI: Too many gateway types installed under the Multiple Gateways Service (MGS).Multiple Gateway Service: Not enough gateways per gateway type configured. Deinstall MGS and reinstall with a larger value in the [Number of Gateways] parameter. This code is returned in response to MGSRegister Request. BMULTI: Too many copies of BMULTI installed under the Multiple Gateways Service (MGS).Multiple Gateway Service: Attempted to filter more requests than were defined at MGS installation. Deinstall MGS and reinstall with a larger value for the [Number of Requests] parameter. This code is returned in response to MGSRegister Request. BMULTI: Too many requests issued in using BMULTI under the Multiple Gateways Service (MGS).Multiple Gateway Service: Request can not be forwarded to destination due to insufficient filter link blocks. The number of outstanding requests has exceeded the [Number of Outstanding Requests] value. This code is returned in response to Application Requests.Multiple Gateway Service: No file handle aliases available. The number of file handles open are at the [Number of File Handles] value. Either reconfigure the MGS with more file handles or maintain less file handles open. This code is returned in response to Application OPEN Requests.Multiple Gateway Service: Non-existent gateway. Application specified file handle or service ID not corresponding to a registered gateway. This code is returned in response to a MGSDeregister or Application Requests.Multiple Gateway Service: Deinstallation aborted due to registered gateways. Deinstall gateways before deinstalling MGS. This code is returned in response to a MGSDeinstall Request.Multiple Gateway Service: Wrong version number. The gateway requires a subsequent release of MGS for operation. This code is returned in response to MGSRegister Request.SNA LU 6.2 Emulator: Application aborted.SNA LU 6.2 Emulator: Deinstall request denied.SNA LU 6.2 Emulator: Operator exceeded maximum LU count.SNA LU 6.2 Emulator: Invalid LU assigned by the SNA gateway.SNA LU 6.2 Emulator: APPC service already installed.SNA LU 6.2 Emulator: Deinstall APPC service.SNA LU 6.2 Emulator: APPCMsg.bin, APPCConfigMsg.bin, APPCtable.sys, APPCforms.lib or APPCCovMsg.bin could not be found. Releases prior to 5.0: Configuration file not found by APPC Configuration Program.SNA LU 6.2 Emulator: The maximum number of sessions defined in the APPC configuration file exceeds the maximum number of independent sessions defined during installation of the SNA Transport Service.SNA LU 6.2 Emulator: APPC Configuration Program is out of memory.SNA LU 6.2 Emulator: APPC service is out of memory.SNA LU 6.2 Emulator: Internal API Error.SNA LU 6.2 Emulator: The configuration file was not found or a Read error occurred during installation of APPC service.SNA LU 6.2 Emulator: Error during SNA gateway LU attachment.SNA LU 6.2 Emulator: File APPCtext.sys is missing.SNA LU 6.2 Emulator: An error occurred while reading one of the following files: APPCMsg.bin, APPCCovMsg.bin, APPCConfigMsg.bin, APPCtable.sys, or APPCForms.lib.SNA LU 6.2 Emulator: APPC service deinstalled.SNA LU 6.2 Emulator: Invalid APPC debug level.SNA LU 6.2 Emulator: All conversations are active and additional control structures are not available. The ReserveStructures verb should have been called indicating additional conversations.SNA LU 6.2 Emulator: The version number entered in the configuration file is incompatible with the current version of the APPC Service.SNA LU 6.2 Emulator: Number of conversations requested on ReserveStructures is out of the range 1 to 254. SNA LU 6.2 Emulator: ConnectAPPC has already been issued by the transaction program. Only one ConnectAPPC verb may be issued by the TP at a time.SNA LU 6.2 Emulator: A ConnectAPPC verb has not yet been issued. This verb must be issued before any other verb is issued (except ReserveStructures).SNA LU 6.2 Emulator: Attribute buffer information was truncated to the user-specified value, which is less than 66.SNA LU 6.2 Emulator: Invalid size of attribute buffer specified in (MC)GetAttributes. Size must range from 0 to 66.SNA LU 6.2 Emulator: The size of the BNET node name specified on AttachAPPC must be between 0 and 12 characters.SNA LU 6.2 Emulator: iFill specified in ReceiveAndWait, ReceiveImmediate, or PostOnReceipt is not LL(1) or Buffer(2).SNA LU 6.2 Emulator: wLocks parameter specified in (MC)PrepareToReceive is not Short(1) or Long(2).SNA LU 6.2 Emulator: The length of the data buffer is less than 0.SNA LU 6.2 Emulator: The length of the data buffer is out of range 0 to 2044.SNA LU 6.2 Emulator: The size of LU name specified is invalid.SNA LU 6.2 Emulator: Size of Map Name specified on MCSendData is invalid.SNA LU 6.2 Emulator: Size of Mode Name specified in (MC)Allocate or GetSession is invalid.SNA LU 6.2 Emulator: The size of Network Name specified is invalid.SNA LU 6.2 Emulator: The iNotify parameter specified on GetSession is not 0 or 2.SNA LU 6.2 Emulator: Size of password specified on (MC)Allocate is invalid.SNA LU 6.2 Emulator: Number of PIP parameters is invalid.SNA LU 6.2 Emulator: Size of array specified on WaitForPosting is invalid, or exceeds the number of conversations reserved with ReserveStructures.SNA LU 6.2 Emulator: Size of profile specified on (MC)Allocate is invalid.SNA LU 6.2 Emulator: The LU has an active session. You cannot change the local LU name.SNA LU 6.2 Emulator: The pResource specified is not associated with an active conversation.SNA LU 6.2 Emulator: The Return Control specified on (MC)Allocate is not SESSALLOC(1).SNA LU 6.2 Emulator: The session handle parameter specified on (MC)Allocate or (MC)Deallocate is not greater than 0.SNA LU 6.2 Emulator: The specified iType parameter is invalid.SNA LU 6.2 Emulator: An unrecoverable memory allocation error occurred. The TP should immediately prepare to exit and then exit. This will return use of the memory to the operating system.SNA LU 6.2 Emulator: iTest specified for (MC)Test is not NoSync(1) or ConfSync(2).SNA LU 6.2 Emulator: Size of TP Name specified in (MC)Allocate is invalid.SNA LU 6.2 Emulator: The mode parameter specified on TraceAPI is not ON(1), OFF(0), or RESET(2).Size of user identifier specified on (MC)Allocate is invalid.SNA LU 6.2 Emulator: A file error was encountered while accessing the BTOS API verb trace file. Check these possibilities:  The file name specification is incorrect  The file was abnormally closed by the operating system and is no longer available  The disk is fullSNA LU 6.2 Emulator: PIP information exceeds the size of the PIP data buffer and was truncated to the size of the buffer.SNA LU 6.2 Emulator: Trace mode specifies Trace On, but trace is already active.SNA LU 6.2 Emulator: Trace mode specifies Trace Reset, but trace is not active.SNA LU 6.2 Emulator: A ReserveStructures verb has already been issued. Only one ReserveStructures verb may be issued per TP invocation.SNA LU 6.2 Emulator: A ReserveStructures verb has not yet been issued. This verb must be issued before allocating a conversation.B-LAN, IDMSS: Internal Error. Contact your Unisys representative. BMULTI: DMA I/O is not supported on the specified channel.B-LAN, IDMSS, BTOS OSI Transport-LAN: Intelligent Module hardware fault. A hardware fault has occurred on the IDS or LAN. IMSP will reboot the module automatically. If the error occurs twice in a row, IMSP will abort and not boot this module. In this case the workstation should be rebooted, and the IMSP reinstalled. If the error still occurs, run Diagnostics, and then consult a customer service engineer.IDMSS Hardware: Software NMI fault. The intelligent module received a stray software nonmaskable interrupt. A user program may be sending the module interrupts. IMSP will  reboot the module automatically. IDMSS Hardware: Parity and bus timeout NMI fault. A hardware fault has occurred on the intelligent module. IMSP will reboot the module automatically. If the error occurs twice in a row, IMSP will terminate and not reboot the module. In that case, the workstation should be rebooted and the IMSP reinstalled. If the error still occurs, run diagnostics and consult a customer service engineer. IDMSS Hardware: Memory parity error. A hardware fault has occurred on the intelligent module. IMSP will reboot the module automatically. If the error occurs twice in a row, IMSP will terminate and not reboot the module. In that case, the workstation should be rebooted and the IMSP reinstalled. If the error still occurs, run diagnostics and consult a customer service engineer. IDMSS Hardware: Bus timeout NMI fault. A hardware fault has occurred on the intelligent module. IMSP will reboot the module automatically. If the error occurs twice in a row, IMSP will terminate and not reboot the module. In that case, the workstation should be rebooted and the IMSP reinstalled. If the error still occurs, run diagnostics and consult a customer service engineer. IDMSS Hardware: Invalid interrupt. A hardware fault has occurred on the intelligent module. IMSP will reboot the module automatically. If the error occurs twice in a row, IMSP will terminate and not reboot the module. In that case, the workstation should be rebooted and the IMSP reinstalled. If the error still occurs, run diagnostics and consult a customer service engineer. IDMSS Hardware: IMSP structure not found. IMSP software structures are being corrupted. A user program may be overwriting these locations. IMSP will reboot the module automatically. IDMSS Hardware: Invalid command in IMSP structure. IMSP software structures are being corrupted. A user program may be overwriting these locations. IMSP will reboot the module automatically. IDMSS Hardware: Invalid destination address in IMSP structure.  IMSP software structures are being corrupted. A user program may be overwriting these locations. IMSP will reboot the module automatically. IDMSS Hardware: Invalid source address in IMSP structure. IMSP software structures are being corrupted. A user program may be overwriting these locations. IMSP will reboot the module automatically. IDMSS Hardware: Invalid start address in IMSP structure. IMSP software structures are being corrupted. A user program may be overwriting these locations. IMSP will reboot the module automatically. IDMSS Hardware: Bad checksum. The intelligent module System Image has an invalid checksum. The copy of this file on the hard disk is probably corrupted. Reinstall the file from the installation media; then reinstall IMSP. IDMSS Hardware: Bad LAN address PROM checksum. The address PROM on the intelligent module has a bad checksum. This may indicate a hardware failure. Hardware diagnostics should be performed by a customer service engineer. IDMSS Hardware: Bad LAN address PROM contents. The address PROM on the intelligent module contains invalid data. This may indicate a hardware failure. Hardware diagnostics should be performed by a customer service engineer. IDMSS Hardware: Bus timer error. Internal hardware error. Contact your technical support representative. IDMSS Hardware: Channel A fault. Internal hardware error. Contact your technical support representative. IDMSS Hardware: Channel B fault. Internal hardware error. Contact your technical support representative. IDMSS Hardware: Dual channel fault. Internal hardware error. Contact your technical support representative. IDMSS Hardware: DMA fault. Internal hardware error. Contact your technical support representative. IDMSS Hardware: Controller register fault. Internal hardware error. Contact your technical support representative. IDMSS Hardware: Controller data fault. Internal hardware error. Contact your technical support representative. IDMSS Hardware:  DIO to interrupt register failure. Internal hardware error. Contact your technical support representative. IDMSS Hardware: Bus timeout failure. Internal hardware error. Contact your technical support representative.IDMSS Hardware: DIO to data register failure. Internal hardware error. Contact your technical support representative. IDMSS Hardware: DIO to data register / auto increment failure. Internal hardware error. Contact your technical support representative. IDMSS Hardware: Initialize failure. Internal hardware error. Contact your technical support representative. IDMSS Hardware: Open failure. Internal hardware error. Contact your technical support representative. IDMSS Hardware: No soft interrupt from adapter to processor. Internal hardware error. Contact your technical support representative. IDMSS Hardware: Wrong node address stored in CP internal buffer. Internal hardware error. Contact your technical support representative. IDMSS Hardware: Ring status error interrupt from adapter. Internal hardware error. Contact your technical support representative. IDMSS Hardware: Adapter check error interrupt from adapter. Internal hardware error. Contact your technical support representative. IDMSS Hardware: Stray unexpected interrupt from adapter. Internal hardware error. Contact your technical support representative. IDMSS Hardware: BUS timeout. Internal hardware error. Contact your technical support representative. IDMSS Hardware: Initialize timeout. Internal hardware error. Contact your technical support representative. IDMSS Hardware: Address register error. Address register did not increment following a read or write to the data register with auto increment. Internal hardware error. Contact your technical support representative. IDMSS Hardware: Parameter passing error. Internal hardware error. Contact your technical support representative. IDMSS Hardware: Command status error. Internal hardware error. Contact your technical support representative. IDMSS Hardware: Unable to put adapter in download state. Internal hardware error. Contact your technical support representative. IDMSS Hardware: ENM load error. Internal hardware error. Contact your technical support representative. IDMSS Hardware: LLC load error Internal hardware error. Contact your technical support representative. IDMSS Hardware: No hard interrupt from adapter. Internal hardware error. Contact your technical support representative. IDMSS Hardware: Bad interrupt from adapter. Internal hardware error. Contact your technical support representative. IDMSS Hardware: Processor to SIF control bus error. Internal hardware error. Contact your technical support representative. IDMSS Hardware: Lobe media fault. The adapter detected a fault in the cable from the adapter to the HUB. Check cable connections between the adapter module and the HUB. IDMSS: Bad run file signature. The intelligent module System Image file has a bad signature in the run file header. The copy of this file on the hard disk is probably corrupt. Reinstall the file from the installation media; then reinstall IMSP. IDMSS: No intelligent module on the current configuration. IMSP can only be installed on a system that has an intelligent module. If a module is on the configuration and this error occurs, it may be due to a faulty connection. Turn off the workstation and reconnect the intelligent module. If the error still occurs, it may be a module hardware problem. Run diagnostics and consult a customer service engineer. IDMSS: Software timed out. This error occurs when IMSP attempts to reboot an intelligent module but does not receive a response. The "software timed out" message refers to IMSP abandoning its attempts to reboot the intelligent module. In many cases, this error is the result of a hardware problem on the intelligent module. In such a case, the intelligent module must be replaced or repaired to correct the error. In other cases, this error occurs when the application running on the intelligent module crashes and leaves memory in a state that cannot be dumped. In such a case, the 31702 error indicates that the module cannot be rebooted by IMSP. Such errors can sometimes be corrected by rebooting the workstation. IDMSS: Intelligent module is in an unknown state. The IDMSS software is not communicating properly. A user program may be sending the module spurious interrupts. IMSP will reboot the module automatically. IDMSS: Invalid values found in run file header. The System Image file has invalid values in the run file header. The copy of this file on the hard disk is probably corrupt. Reinstall the file from the installation media; then reinstall IMSP. IDMSS: Invalid processor number. An internal software error has occurred. IMSP will reboot the module automatically. IDMSS: Invalid workstation type. IMSP cannot be installed on an unsupported workstation. See the Software Release Announcement. IDMSS: Could not access XB IS. IMSP was not granted access to the XBIS, a CTOS structure that controls initialization of modules. A user program may not be following the proper protocol when using the XBIS. IMSP cannot be installed while such a program is running. IDMSS: Invalid operation on module. An internal software error has occurred. IMSP will reboot the module automatically. IMExecutive: No run file specification. This is used for communication among the IMExecutive system service, the IMExecutive, and the IMRun utility. It does not indicate an error. IMExecutive: No termination status. This is used for communication among the IMExecutive system service, the IMExecutive, and the IMRun utility. It does not indicate an error. IMExecutive: A software error has occurred causing the IMExecutive system service to receive both an IMRun request, asking for status without presenting a run file specification, and an IMStatus request, asking for a run file specification, without presenting a termination status. IMExecutive: A software error has occurred, causing a duplicate IMRun request to be received. IMExecutive: A software error has occurred, causing a duplicate IMStatus request to be received. IMExecutive: A software error has occurred, causing an unexpected request to be received by the IMExecutive system service. IMExecutive: A program has exited with a termination status message that is too large for the IMExecutive system service to handle. IMExecutive: An attempt has been made to pass a run file specification that is too large for the IMExecutive system service to handle. This indicates a software error because the IMExecutive will handle the largest legal file specification. IMExecutive: An attempt has been made to pass a password that is too large for the IMExecutive system service to handle. This indicates a software error because the IMExecutive will handle the largest legal password. IMExecutive: An attempt has been made to pass a Variable Length Parameter Block (VLPB) that is too large for the IMExecutive to handle. IMExecutive: IMRun has been supplied with a Variable Length Parameter Block (VLPB) containing too many parameters. IMExecutive: A software error has occurred, causing an internal consistency check to fail. The IMExecutive system service has received a swapping request for a partition that appears to be already swapped. IMExecutive: Internal error. to Contact your Unisys representative. - Interprocess Communications (IPC) (31750 to 32499)IPC: A request has been received by IPC with an invalid processor ID. Examine the system log file to ensure that each intelligent module has been recognized and has bootstrapped. If so, a nonexistent processor has been specified by a software error. IPC: A request destined for a currently inactive processor has been received by IPC. The processor may have failed to boot initially or may have failed during operation. Examine the system log file to determine the cause of the failure. IPC: When IPC issues requests for abnormal termination, this error code is placed in the erc field of each request block. This error code is received only by system services and is not for operator display. IPC: A software or hardware error has occurred, causing an interrupt to be received from an inactive processor. IPC: A software or hardware error has occurred, causing an illegal value to be encountered in the type code field of a processor's mailbox. IPC: An attempt has been made to send via IPC a request that is too large for Interprocessor Request Blocks (IPRBs) of the destination processor. IPC: A processor has received requests from too many users, that is, different nodes, workstations, or partitions. IPC: Sufficient currently outstanding requests have been issued from a processor to consume all of the Request Control Blocks (RCBs). IPC: Sufficient currently outstanding requests have been issued to a processor to consume all of the Interprocessor Request Blocks (IPRBs). IPC: An attempt has been made to reboot a processor that is currently inactive and is in the process of rebooting. IPC: A software or hardware error has occurred, causing the IPC to receive a duplicate reboot notification request. IPC: A software or hardware error has occurred, causing IPC to receive an interrupt during initialization. IPC: A software or hardware error has occurred, causing an unexpected request to be received by the request manager. OFIS Organizer: Bad operation code. Software error. Contact Unisys customer support.OFIS Organizer: Reminder suspended. Software error. Contact Unisys customer support.OFIS Organizer: Bad reminder type. Software error. Contact Unisys customer support.OFIS Organizer: Bad reminder date. Software error. Contact Unisys customer support.OFIS Organizer: Bad recurrence interval. Software error. Contact Unisys customer support.OFIS Organizer: Reminder table full. Only 200 reminders for the current day can be created. If this error occurs, you can wait for the reminders to expire, delete the appointments or tasks with reminders, or turn the Reminder feature off.System Support: Invalid Command. An MpCommand request contained a command code greater than 11. BMULTI: An invalid command was issued to BMULTI.System Support: Task Overflow. The maximum number of addresses has been reached. No more can be configured until an address currently on line does an End Session. BMULTI: Task overflow. The multitasking interface cannot handle more than three device addresses.System Support, BMULTI: Command Pending. There is already a command pending for this address. In BMULTI, only one BMULTI command can be outstanding at any time per address.System Support, BMULTI: Report Pending. There is already a report request pending for this address. In BMULTI, only one BMULTI report request can be outstanding at any time for an address.System Support: Invalid Address. The device address has not been configured. BMULTI: Invalid BMULTI address.System Support: Command Denied. An MpCommand request contained a command code which cannot be honored at present because an event occurred which renders the request meaningless. BMULTI: Command denied (Mp interface).System Support: Buffer Overflow. A Transfer Receive Buffer command contained a value in sBufferMax smaller than the actual size of the data received.System Support: Report Error. BMULTI: Invalid report request. A BMULTI Internal Error has occurred. Consult the Unisys Customer Support Center.BMULTI: Read in progress.BMULTI: Write in progress.BMULTI: A request for a large buffer transfer cannot be honored at this time for want of buffer space. Try again later.BMULTI: Invalid buffer length for this command.BMULTI: Offline command denied.BMULTI: Online command denied.BMULTI: Idle command denied.BMULTI: Fast Ready command denied.BMULTI: Transmit Ready command denied.BMULTI: Receive Ready command denied.BMULTI: Transfer Xmt Buffer command denied. This error usually occurs because the application has not checked the report queue often enough, causing it to overflow. To avoid this problem, have the application empty the queue before issuing the SetTransmitReady command. Put as little code as possible between checking for a report of the Ready for Transmit buffer and issuing the command Transfer Transmit Buffer. Also, put as little code as possible between CTOS calls. To recover from this problem, issue an Idle command and reinitiate the transmit sequence.BMULTI: Transfer Receive Buffer command denied.BMULTI: End session command denied.BMULTI: Station not online.BMULTI: Station overflow.BMULTI: Device address is identical to group address.BMULTI: The buffer received by the application is only part of the full message.BMULTI: Internal error. Report it to the system administrator.BMULTI: Duplicate virtual address or duplicate X.21 poll/select addresses are configured when attempting to configure BMULTI for X.21 circuit switched mode.BMULTI: BMULTI locked for reconfiguration.BMULTI: Entry error or no poll/select addresses are configured when attempting to configure BMULTI for X.21 circuit switched mode.BMULTI: Station active. Context Manager cannot swap tasks at this time. BMULTI: BMULTI was not deinstalled because the operating system is single-partition.BMULTI: BMULTI was not deinstalled, either because the Deinstall utility was not executed in the primary application partition (Context Manager installed) or because the Deinstall utility was not executed on the workstation on which BMULTI is installed.BMULTI: Line monitor in use.BMULTI: Data lost while monitoring.BMULTI: BMULTI was not deinstalled because stations are active.BMULTI: An attempt to call BmOpenII, requesting an unused virtual address, failed because there are no more unused virtual addresses.BMULTI: Inconsistency between BMULTI and BmZip, BmConfig,or BmStatus. If you have configuration files created with a previous release of BMULTI, you must open them, make any new parameter selections and close them using the current BMULTI confi gurator.BMULTI: A change of extended character translation mode attempted by BmSetXlatMode or SetXlatModeBMULTI when station not idle, or station online but not Fast Ready. BMULTI: Invalid iRcvMode or iXmitMode was specified for BmSetXlatMode or SetXlatModeBMULTI.BMULTI: Character translation file is incomplete or in unexpected format.BMULTI: Data contents of character translation file not valid ASCII: 0-9, A-F, a-f, or space (30h-39h, 41h-46h, 61h-66h, or 20h).BMULTI: BmGetStatus (iRecordLen * nStation) exceeds specified buffer size.BMULTI: The number of stations or I/O buffer size cannot be reconfigured dynamically.BMULTI: BMULTI has already been installed. BMULTI: An invalid node specification was passed to SelectBMULTI. See the BMULTI documentation for information on the procedural interface.BMULTI: The report queue of the station requesting the report has overflowed and the contents of the queue are now meaningless.OSI TransNet: Installed. The OSI Transport system service has already been installed. OSI TransNet: No Buffers. The number of outstanding requests has exceeded the number of buffers allocated. OSI TransNet: No Connections. The Open request exceeds the maximum number of connections allowed by the service. No connection can be made at this time. OSI TransNet: Local Stack Overflow. A local stack used to save bus window values has overflowed. This internal error should never occur.OSI TransNet: Local Stack Underflowed. A local stack used to save bus window values has underflowed. This internal error should never occur. OSI TransNet: Fatal OSI Internal Error. An unrecoverable internal error has occurred in an OSI layer below the request interface. OSI TransNet: Invalid Hardware. The user attempted to install the service on an invalid module. OSI TransNet: Connection Error. A request to open or close a transport connection has failed. OSI TransNet: No NMF Link. A user already has an NMF link established. An attachment cannot be made at this time. Message Control System: The OI Manager software is already installed.Message Control System: The OI Manager software cannot connect subqueues to the MCM Module because the MCM Module is not running or does not have enough free subqueues.Message Control System: The number of OIC workstations specified through the Install Operator Interface Manager command is invalid. It must be a number from 1 to 9.Message Control System: The number of records specified through the Install Operator Interface Manager command is invalid. It must be a number from 200 to 32767.Message Control System: The node name is longer than 20 characters including the curly brackets ( {} ).Message Control System: Invalid node name. { was used instead of [ or there was no name inside the brackets.Message Control System: Workstation must be a B25 type. The workstation must be a real mode or protected mode workstation. B24 workstations are not supported.Message Control System: Invalid number entered, press CANCEL to continue.Message Control System: The NCD data file is corrupted. Please delete the file. Message Control System: Data file checksum error. Fatal error.Message Control System: The data entered is out of range, press CANCEL to continue.Message Control System: Incorrect NCD file level. Fatal error. Consult your system administrator. The data file and NCD system versions do not correspond and conversion is not possible. CTOS Ethernet Data Link Ethernet Data Link: Fatal error. Fatal error in chip initialization.CTOS Ethernet Data Link Ethernet Data Link: Fatal error. Invalid chip response.CTOS Ethernet Data Link Ethernet Data Link: Fatal error. Fatal error in system control block location.Installation Manager: No installed software. The Installation Manager has detected that the installation database does not contain any software packages.Installation Manager: Installation failed. The installation of one or more packages has failed. See the installation log file for further information.Installation Manager: Incorrect version of Installation Manager. The Installation Manager has detected that the installation database has been updated by a later version of Installation Manager. Use a later version of installation Manager. Installation Manager: Invalid database signature. The Installation Manager has detected that the installation database has an invalid signature.Of Course!: The program source file is too large. The program is too large to be compiled within Of Course! Use the Of Course! compiler.Of Course!: You may not nest comments. A comment start (/*) was found within a comment.Of Course!: A comment was started but not terminated. The compiler detected a comment start (/*) but no comment terminator (*/).Of Course!: A comment terminator (*/) was found outside a comment. The compiler detected a comment terminator (*/) but not a comment start (/*).Of Course!: Statement too complex (check for misspellings, missing semicolon, and so on.) A statement may be too long, but more likely the statement is in the wrong format, for example, it is missing a semicolon, or keywords are misspelled.Of Course!: Out of space...program too complex. The program is too long. Try using the global variables to communicate between two or more programs that are logically one, but have been broken down because of this error. Also, you may want to try the precompile option if it is not already being used. The precompile option allows larger size programs than the Of Course! run time compile option.Of Course!: Unbalanced parentheses. A left parenthesis is not balanced in a VARIABLE format definition, a CONDITION ISANUMBER or ISADATE, or an IF clause.Of Course!: Invalid variable name. A variable name in a VARIABLE statement or an assignment statement is either too long (more than 50 characters), does not begin with a letter, or uses characters other than the alphanumerics and the underscore character. This error may occur with other types of statements in which the keywords are misspelled.Of Course!: Invalid constant or variable name. A string of characters in a CONDITION statement or an assignment statement cannot be interpreted as either a variable name or a legitimate constant.Of Course!: Statements out of order. In a program, VARIABLE statements must be given first, followed by CONDITION statements; all executable statements follow CONDITION statements.Of Course!: Missing statement. The compiler detected a semicolon without a statement preceding it. A semicolon must terminate a statement. Check for statements with a repeated semicolon, as in x=x+1;;Of Course!: Variable name is not a user-defined variable--cannot create. The variable name in a VARIABLE statement either begins with a per cent character (%), clashes with a special purpose variable, or contains an illegal character.Of Course!: Invalid variable formatting information. In a VARIABLE statement, the formatting information in parentheses after the variable name is incorrect. Make sure that the format list uses spaces to separate the format codes that specify formatting information. Make sure that the format codes used are valid and not duplicated.Of Course!: Variable formatting information not reasonable for variable type. In a variable statement, the formatting information in parentheses is not reasonable for the type of variable. For example, it is not reasonable to apply the monetary attribute to a STRING variable.Of Course!: Variable formatting information repeated in format specification. The formatting information in parentheses is repeated in a VARIABLE statement. Each format keyword can appear only once in a format specification.Of Course!: Invalid constant. A specified constant is not well-formed:  For STRING variables, the maximum length is 80. Make sure that double quotes are used and balanced.  For DATE-TIME constants, make sure that the correct format is used (white space separating individual components and no white space around the equals signs). Make sure that one set of single quotes are used and balanced.  For NUMERIC constants, make sure that the number is between -9999999.99 and +9999999.99, inclusive, that no commas or monetary symbols are used, and that the period is used for a radix point.Of Course!: INITIALLY constant type does not agree with specified variable type. The constant type as denoted by double quote, single quote, or the absence of both, is inconsistent with the specified variable type (NUMERIC, STRING, or DATE-TIME).Of Course!: Variable type (STRING, NUMERIC, or DATE-TIME) is missing or out of order. Variable type keyword (STRING, NUMERIC, or DATE-TIME) could not be located in a variable statement or does not appear to the left of format of INITIALLY specifiers. The error could be the result of a misspelling.Of Course!: Variable name is missing. In a VARIABLE statement, the name of the variable is missing. This error could be the result of using a reserved word (such as STRING or LOCAL) for the variable name.Of Course!: Missing colon after condition number. In a CONDITION statement, the condi tion number must appear immediately after the keyword CONDITION and a colon (:) must appear immediately after the condition number.Of Course!: Invalid condition number. The condition number specified in a CONDITION statement is not a reasonable number. Of Course!: Invalid relational operator. The relational operator specified in a CONDITION statement is not reasonable.Of Course!: Missing = in assignment statement. In an assignment statement, the equals sign (=) must appear immediately after the target variable.Of Course!: Invalid operator in assignment. The only four valid operators are: + - * / Of Course!: An AUTOMATIC or T Variable may not be the target in an assignment statement. Only user-defined, UFA, or message variables may appear on the left side of the equal sign in an assignment statement.Of Course!: Missing ( after IF keyword. The condition specification in an IF statement must be surrounded by parentheses and immediately follow the IF keyword.Of Course!: Invalid condition or T variable reference. In an IF condition specification, only condition numbers and T variable numbers of the form T.i,i=1,2, ... are acceptable.Of Course!: Invalid IF clause. The IF condition specification either uses invalid relational operators (a character other than &, |, and !), does not balance operands with operators, or has unbalanced parentheses.Of Course!: IF clause too complex. The IF condition specification is either too long or is too deeply nested parenthetically. Of Course!: No matching IF for ELSE statement. An ELSE cannot appear without an earlier IF. Check for missing right curly brace } in the IF block immediately prior to the ELSE.Of Course!: Braces { } unbalanced. An IF block or ELSE block must be enclosed in curly braces. Left and right { } braces are not balanced. The problem might actually exist well above the indicated point of error.Of Course!: IF statements nested too deeply. A nested IF statement defines new IF statements within an IF or ELSE block of statements.Of Course!: Missing left brace { after IF or ELSE. The IF and ELSE statements must be followed immediately by a left brace before the first statement in the block. Of Course!: Missing path name after LINK verb. In a LINK statement, the keyword LINK must be followed immediately by the path name. Do not surround the path name in parentheses.Of Course!: Invalid path name after LINK verb. The path name specified in a LINK statement is not reasonable. Path names must not contain volume or directory references, copyright symbols, or metacharacters. Path names must end in the .path suffix. Do not surround the path name in parentheses.Of Course!: Missing or invalid count of actors after BACKUP verb. The BACKUP verb requires the number of actors to back up. This number must be a simple positive integer.Of Course!: An invalid data type was specified in an operation. Type conversion is not possible. Rewrite the statement.Of Course!: No more variables may be created in that class. The global or local variable table is full.Of Course!: The space containing variables in that class is full. The global or local variable table is full.Of Course!: A variable name specified is invalid. Illegal characters were used when naming or specifying variables.Of Course!: A specified variable does not exist. Unable to resolve variable name. Check the spelling.Of Course!: The format specification for a variable definition is invalid. An invalid format specification for that variable type was used, or a format specifier was repeated.Of Course!: The compiler generated an invalid variable type. If you are using the precompile option, the pseudo-code may be corrupted. Recompile the program and try again. Otherwise this is an internal Of Course! error indicating a problem with the software; report it to Technical Support.Of Course!: The compiler generated an invalid variable class. If you are using the precompile option, the pseudo-code may be corrupted. Recompile the program and try again. Otherwise this is an internal Of Course! error indicating a problem with the software; report it to Technical Support.Of Course!: The operator specified is invalid (may depend on the variable type). Interpretation of operators depends on target variable type. Rewrite the statement.Of Course!: The operation will result in a string that is too large. Rewrite the statement.Of Course!: The LONG-LIVED modifier may only be used with GLOBAL variables. If you are using the precompile option, the pseudo-code may be corrupted. Recompile the program and try again. Otherwise this is an internal Of Course! error indicating a problem with the software; report it to Technical Support.Of Course!: A value specified cannot be converted to a NUMERIC value. Rewrite the statement.Of Course!: The specified condition number is invalid. If you are using the precompile option, the pseudo-code may be corrupted. Recompile the program and try again. Otherwise this is an internal Of Course! error indicating a problem with the software; report it to Technical Support.Of Course!: A specified condition number does not exist. Condition numbers used in an IF statement must be defined within the current program.Of Course!: Invalid condition statement - The condition number already exists. Rewrite the statement.Of Course!: The IF statement contains too many condition items. Rewrite the statement using nested IF statements.Of Course!: The exists with the condition specification. Check the logic of the CONDITION statement.Of Course!: The Variable Manager is not initialized. An attempt was made to run a program in Rehearsal without the Student Tracking option. Contact your Unisys representative for an upgrade.Of Course!: Initial value type is incompatible with the variable type. Type conversion could not be performed. Rewrite using a constant of the same type.Of Course!: Invalid backup count. The backup count specified with the BACKUP verb is invalid. For example, it may be greater than the number of actors preceding the program actor in the path.Of Course!: This error can be caused by one of the following:  Using an earlier version of Of Course! to take or rehearse a course developed with CTOS Of Course! 1.0. Check that you have the latest software and if not, consult your Unisys representative for an upgrade.  A corrupted reel; to use the reel, you must recapture it and overwrite the existing one  Program file is an invalid reel  The RSAM file containing the program is malformedOf Course!: Internal error. This indicates a problem with the software you are using. If you observe such an error, report it to Technical Support.Of Course!: Wrong screen resolution. The minimum screen resolution has to be 80 X 29. Check your screen set up.Of Course!: Too many frames in reel. You cannot use Reel Builder Adjustor on reels of more than 1000 frames. You should recreate the reel with fewer frames.Of Course!: Glossary not prepared properly. Refer to the CTOS Of Course! Reference Manual for instructions on preparing a glossary.Of Course!: Missing glossary term. The glossary does not contain the specified term.Of Course!: Too many terms in glossary. Maximum 75 terms allowed in a glossary.Of Course!: Function key label too long. The function key label cannot be more than six characters long.Of Course!: Message too long. A message associated with a function key will not display if more than 80 characters long.Of Course!: Corrupted pedal file. The training wheel pedal file has been corrupted. Delete the pedal file for that reel. It is listed in the course directory as reelname.pedal. Create a new pedal file with the usual Reel Builder Adjustor procedure.Of Course!: Windows not supported. Windows are not supported on the B26/B27.Of Course!: Invalid course name. Check that you entered the name correctly and that it resides on the current volume. You can use the Directory function on the Of Course! main menu to display a list of courses on the current volume.Of Course!: Invalid lesson name. Check that you entered the name correctly. You can use the Directory function on the Of Course! main menu to display a list of lessons in the current course.Of Course!: Invalid course and lesson name. Check that you entered the names correctly. You can use the Directory function on the Of Course! main menu to display course and lesson names.Of Course!: Internal error. This indicates a problem with the software you are using. If you observe such an error, report it to Technical Support.Of Course!: Internal error. There was an internal software problem while compressing the character map. Report this to Technical Support.Of Course!: Internal error. This indicates a problem with the software you are using. If you observe such an error, report it to Technical Support.Of Course!: Incorrect software version or corrupted frame in reel. This code can be caused by one of the following:  Using an earlier version of Of Course! to take or rehearse a course developed with CTOS Of Course! 1.0. Check that you have the latest software and if no t, consult your Unisys representative for an upgrade.  A corrupted frame in a reel; to use the reel, you must recapture it and overwrite the existing one.Context Manager: Context Manager inconsistency, suggest you save all contexts.Context Manager: Internal error. Wrong exchange.Context Manager: Internal error. Region status inconsistency.Context Manager: Internal error. Swap file inconsistency.Context Manager: Internal error. Too many swaps.Context Manager: Internal error. Invalid line indices specified for a map switch.Context Manager: Internal error. Swap count invalid.Context Manager: Internal error. Unknown context status.Context Manager: Internal error. Too many swaps.Context Manager: The run file is too large to run in any region.Context Manager: You cannot logout, there are active contexts.Context Manager: Swapping is not yet implemented.Context Manager: The Context Manager is already installed.Context Manager: In order to start another application you must have a swap file.Context Manager: Not applicable to this release.Context Manager: This hardware is unknown to the Context Manager.Context Manager: There is no current context.Context Manager: Internal error. Invalid line indices specified for a map switch.Context Manager: An existing context cannot be swapped out to start a new application. Context Manager: You must finish the highlighted context to return to the one you selected.Context Manager: To deinstall Context Manager you must finish all contexts, then log out.Context Manager: The run file needed for this application does not exist.Context Manager: Internal error. Swap count invalid.Context Manager: Unable to access the swap file -- cannot swap contexts.Uninterrupted Power Supply Service: String not recognized. A string of characters in the file string in [sys]upssconfig.sys is not recognized by the UPSS. See your UPSS Software Release Announcement for more information on UPSS configuration.Uninterrupted Power Supply Service: Wrong uptime interval. The value of the UPSS configuration parameter, InitMsgWait, is more than the value of the configuration parameter, UpTime. Check the values of InitMsgWait and UpTime in the file [Sys]UPSSConfig.sys. See your UPSS Software Release Announcement for more information.Uninterrupted Power Supply Service: Incorrect Action configuration. The Action components of UPSS are not configured correctly. The Action components supported are SSM and Batch. See your UPSS Software Release Announcement for more information on UPSS configuration.Uninterrupted Power Supply Service: UPS dead. The Uninterrupted Power Supply is dead or malfunctioning. Check the serial interface cable connecting the UPS hardware to the CTOS workstation. Check the UPS hardware for correct operations using the UPS hardware documentation.Uninterrupted Power Supply Service: Missing parameter. A required parameter is missing or has no value in the UPSS configuration file [Sys]UPSSConfig.sys. Check the contents of the file [Sys]UPSSConfig.sys. See your UPSS documentation for more details on required parameters.Configuration Error. Check the text displayed with this error and correct the corresponding parameter.Invalid or unknown Mail User Name. The Mail User Name or Center Name is more than 8 characters, or the name is not known to SNADS.Too many recipients. The message is addressed to too many recipients. Address the message to a smaller number of users (maximum users is 24).SNADS reported an error. SNADS is not installed or reported an error. This may be a configuration error or some other error condition. Examine the OFIS Access SNADS log file for the actual error reported by SNADS. Unable to create/write/close a temporary file. Check if the attachment directory specified in the Mail is full. If so, deinstall OFIS Access SNADS and delete all the files in the attachment directory.Temporary file not found. A temporary file in the attachment directory was not found. Check to see if files were manually deleted from this directory.Translation Error. The DCA Translation of an attachment failed. Check the memory available on your system; otherwise, there may be inconsistencies between the versions of the software on your system. Check the log file. Consult Technical Support.Translated file not found. Either DCA Translation failed (40057) or the translated file was deleted (40056). Check if the volume and directory name for the attachment directory, including all brackets, exceeds 31 characters.Too many attachments specified. You cannot specify more than one attachment when sending to a non CTOS System.Message too large to send with an attachment. The message should not be more than 205 characters when sending an attachment.Fatal Error. An unexpected software error was encountered. Internal error. Consult Technical Support.Invalid Document Name. The specified attachment document name does not conform to the naming convention. Document types other than RFT and FFT can be a maximum of four hexadecimal digits specified as follows: Name.xxxx.DCA, where xxxx is the document type.Invalid Document Format. The attachment is not in the format specified by the name.DDM: DDMInvalidKey Key length specified in a DDM request is zero (DDMDeleteRec, DDMReadRec, DDMWriteRec). DDM: RecNotFound Record identifed by the key does not exist (DDMDeleteRec, DDMReadRec, DDMWriteRec). DDM: RecAlreadyExists Record identifed by the key already exists (DDMWriteRec with gen num == 0). DDM: GenNumMismatch The gen num specified does not match the current record gen num (DDMDeleteRec, DDMWriteRec with gen num != 0). DDM: TooManyHashBits Internal error searching for a key; should be considered the same as DDMRecNotFound (DDMDeleteRec, DDMReadRec, DDMWriteRec, DDMUpdateCList, DDMQueryCList). DDM: Truncation Internal error when reading DDM data, indicates that the file is not as large as we expect (and presumably created!), bad error, indicates possible data loss, only way to recover would be using DDM Merge or DDM Convert utility (DDMDeleteRec, DDMReadRec, DDMWriteRec, DDMUpdateCList, DDMQueryCList, DDMReadKeys). 40166 Reserved. DDM: DDMDbCorrupt DDM database is corrupt, either the header or the trie table (something like a directory of all the keys stored) is corrupt. The only way to recover would be using DDM Merge or DDM Convert utility (returned only when loading ddm into memory). DDM: DDMDatabaseTooBig Unable to store data into the ddm database because it's too large. We're either out of trie slots or pages, the user can determine which by using the DDM Query Status utility. If the DDM was not loaded with the maximum trie size then the user can recover from this error by unloading and reloading DDM (DDM will automatically increase the trie size by 20% over what is needed or they can force a greater or a smaller overhead). If this error is returned when DDM is loaded with the maximum trie size (63K) then there is no way to recover from this error, the user has hit the limits of the DDM database. (DDMWriteRec, DDMUpdateCList) DDM: DDMRecordTooLarge Key and record data specified exceed 8184 bytes which is the max limit for the sum of the two (DDMWriteRec). DDM: DDMInvalidCList A node name specified is invalid, i.e, is more than 12 characters (14 with curly braces) or has unbalanced curly braces, e.g. "{badnode". (DDMUpdateCList) DDM: DDMCListTooLarge Unable to add a node to the client list because it's too large. The first release of DDM will only support a maximum of 628 node names in the client list. (DDMUpdateCList, with mode = add node to list) ISAM III: General utility failure. General error returned by utilities when a special one is not assigned.ISAM III: An invalid parameter was specified.ISAM III: An invalid [Local/Server] parameter was specified.ISAM III: Database not normal Refer to Table B-5 for database status information in Accessing and Using ISAM III Utilities.ISAM III: No data file was specified.ISAM III: No index file was specified.ISAM III: Database is empty.ISAM III: Error was encountered in the compression utility.ISAM III: Audit file number is missing or invalid.ISAM III: Control file error. An error or problem was encountered with the control file.ISAM III: Maintenance required for control file. An error or problem was encountered with the control file. Control file maintenance is required.ISAM III: An error or problem was encountered with the configuration file.ISAM III: An error or problem was encountered when updating password.ISAM III: An attempt was made to copy a file to itself.ISAM III: An attempt was made to copy a file from a server to a cluster.ISAM III: An invalid yes or no parameter was specified.ISAM III: File accessed is not an ISAM file.ISAM III: No source file was specified.ISAM III: No destination file was specified.ISAM III: More than one source file was specified.ISAM III: More than one destination file was specified.ISAM III: More than one data file was specified.ISAM III: More than one index  file was specified.ISAM III: The source and destination files are the same.ISAM III: An invalid modify password was specified.ISAM III: An invalid read password was specified.ISAM III: Cannot audit.ISAM III: An invalid data file name was specified.ISAM III: An invalid index file name was specified.ISAM III: An error was encountered while writing to a data file.ISAM III: An error was encountered while writing to an index file.ISAM III: An error was encountered while reading a data file.ISAM III: An error was encountered while reading an index file.ISAM III: Operation denied by user. Confirmation of an overwrite of a file was canceled by the user. Applies to ISAM Copy, ISAM Create, and ISAM Rename Executive command line utilities.ISAM III: The data file name is not in the control file.ISAM III: An error was encountered accessing a data file.ISAM III: An error was encountered accessing an index file.ISAM III: An error was encountered deleting a data set from the control file.ISAM III: A matching file was found in the control file.ISAM III: An error was encountered updating the control file.ISAM III: An invalid administrator password was entered.ISAM III: An invalid password was entered.ISAM III: The data file is associated with another index file.ISAM III: The index file is associated with another data file.ISAM III: The data file and index file have different data set numbers.ISAM III: The number of indexes has been exceeded.ISAM III: Nodes are not supported.ISAM III: The index file is associated with another data file.ISAM III: An earlier ISAM III service is running. ISAM returns this error code if you are using the ISAM Reassociate utility or the ISAM List Files utility with an earlier version of the ISAM III service. You must use the version of the ISAM III service that was shipped with the version of ISAM Reassociate and ISAM List Files you are attempting to use.ISAM III: Invalid ISAM configuration file. An attempt was made to use a file as an ISAM configuration file (ISAM.Config), but the file has been damaged or it was not generated by ISAM Control Center.ISAM III: Invalid ISAM configuration version. An attempt was made to use an ISAM configuration file (ISAM.Config) that was generated by an incompatible version of ISAM Control Center. Regenerate the file by using a compatible version.ISAM III: Context Manager is installed. An attempt was made to install either the ISAM III service or the Audit Compressor service with Context Manager running. Refer to the section on loading the ISAM service when Context Manager is running in Installing ISAM III and the Computer-Based Training. FTAM: No specific reason.FTAM: Responder error.FTAM: System shutdown.FTAM: Management problem.FTAM: Management problem, bad account.FTAM: Management problem, security not passed.FTAM: Delay may be encountered.FTAM: Initiator error.FTAM: Subsequent error.FTAM: Not enough resources available. Temporary condition.FTAM: Access request violates VFS security.FTAM: Access request violates local security.FTAM: Conflicting parameter values.FTAM: Unsupported parameter values.FTAM: Mandatory parameter not set.FTAM: Unsupported parameter.FTAM: Duplicated parameter.FTAM: Illegal parameter type.FTAM: Unsupported parameter types.FTAM: FTAM protocol error (unspecified).FTAM: FTAM protocol error procedure error.FTAM: FTAM protocol error functional unit error.FTAM: FTAM protocol error corruption error.FTAM: Lower layer failure.FTAM: Lower layer addressing.FTAM: Time-out.FTAM: System shutdown.FTAM: Illegal grouping sequence.FTAM: Grouping threshold.FTAM: PDU inconsistent with current requested access.FTAM: Association with user not allowed.FTAM: Association with user not assigned.FTAM: Unsupported service class.FTAM: Unsupported functional unit.FTAM: Attribute group error (unspecific).FTAM: Attribute group not supported.FTAM: Attribute group not allowed.FTAM: Bad account.FTAM: Association management (unspecific).FTAM: Association management bad address.FTAM: Association management bad account.FTAM: Checkpoint window too large.FTAM: Checkpoint window too smallFTAM: Checkpoint window unsupported.FTAM: Communication QoS not supported.FTAM: Initiator ID unacceptable.FTAM: Context management refused.FTAM: Rollback not available.FTAM: Contents type list cut by responder.FTAM: Contents type list cut by Presentation.FTAM: Invalid filestore password.FTAM: Incompatible service classes.FTAM: File name not found.FTAM: Selection attributes not matched.FTAM: Initial attributes not possible.FTAM: Bad attribute name.FTAM: File does not exist.FTAM: File already exists.FTAM: File cannot be created.FTAM: File cannot be deleted.FTAM: Concurrency control not available.FTAM: Concurrency control not supported.FTAM: Concurrency control not possible.FTAM: More restrictive lock.FTAM: File busy.FTAM: File not available.FTAM: Access control not available.FTAM: Access control not supported.FTAM: Access control inconsistent.FTAM: File name truncated.FTAM: Initial attributes altered.FTAM:  Bad account.FTAM: Override selected existing file.FTAM: Override deleted and recreated file with old attributes.FTAM: Override deleted and recreated file with new attributes.FTAM: Create override not possible.FTAM: Ambiguous file spec.FTAM: Invalid create password.FTAM: Invalid delete password on override.FTAM: Bad attribute value.FTAM: Requested access violates permitted actions.FTAM: Functional unit not available for requested access.FTAM: File created but not selected.FTAM: Attribute does not exist.FTAM: Attribute cannot be read.FTAM: Attribute cannot be changed.FTAM: Attribute not supported.FTAM: Bad attribute name.FTAM: Bad attribute value.FTAM: Attribute partially supported.FTAM: Additional set attribute value not distinct.FTAM: Bad FADU, (unspecific).FTAM: Bad FADU, size error.FTAM: Bad FADU, type error.FTAM: Bad FADU, poorly specified.FTAM: Bad FADU, bad location.FTAM: FADU does not exist.FTAM: FADU not available (unspecific).FTAM: FADU not available for reading.FTAM: FADU not available for writing.FTAM: FADU not available for location.FTAM: FADU not available for erasure.FTAM: FADU cannot be inserted.FTAM: FADU cannot be replaced.FTAM: FADU cannot be located.FTAM: Bad data element type.FTAM: Operation not available.FTAM: Operation not supported.FTAM: Operation inconsistent.FTAM: Concurrency control not available.FTAM: Concurrency control not supported.FTAM: Concurrency control inconsistent.FTAM: Processing mode not available.FTAM: Processing mode not supported.FTAM: Processing mode inconsistent.FTAM: Access context not available.FTAM: Access context not supported.FTAM: Bad write (unspecific).FTAM: Bad read (unspecific).FTAM: Local failure (unspecific).FTAM: Local failure, file space exhausted.FTAM: Local failure, data corrupted.FTAM: Local failure, device failure.FTAM: Future filesize exceeded.FTAM: Future filesize increased.FTAM: Functional unit invalid in processing mode.FTAM: Document type inconsistent.FTAM: Contents type simplified.FTAM: Duplicate FADU name.FTAM: Damage to select/open regime.FTAM: FADU locking not available on file.FTAM: FADU locked by another user.FTAM: Bad checkpoint (unspecific).FTAM: Activity not unique.FTAM: Checkpoint outside window.FTAM: Activity no longer exists.FTAM: Activity not recognized.FTAM: No docket.FTAM: Corrupt docket.FTAM: File waiting restart.FTAM: Bad recovery point.FTAM: Recovery point does not exist.FTAM: Recovery mode not available.FTAM: Recovery mode inconsistent.FTAM: Recovery mode reduced.FTAM: Access control not available.FTAM: Access control not supported.FTAM: Access control inconsistent.FTAM: Contents type inconsistent.FTAM: Contents type simplified.FTAM: No specific reason.FTAM: Invalid OSIAM address.FTAM: Connection denied by lack of resources.FTAM: Lack of resources on remote site.FTAM: Connection refused by remote with no reason.FTAM: Selected class invalid.FTAM: Selected class is unknown by remote.FTAM: System state is closed.FTAM: SAP state is not correct.FTAM: Action is not allowed.FTAM: Error occurred when reading the system database.FTAM: No compatible service class with those supported.FTAM: Incorrect open mode.FTAM: Invalid document type.FTAM: System name does not exist in the database.FTAM: Invalid request for the actual state of automata.FTAM: File creation error.FTAM: File allocation error.FTAM: File opening error.FTAM: Error in restarting transfer.FTAM: Missing file name.FTAM: Bad file organization.FTAM: Write in reader state.FTAM: Read in writer state.FTAM: Invalid DE length.FTAM: Invalid mark number.FTAM: Invalid transfer end code.FTAM: Error on closing file.FTAM: Error on deallocating file.FTAM: Error on deleting file.FTAM: Local user error.FTAM: Protocol error occurred.FTAM: Provider abort ID received.FTAM: Abort from Session.FTAM: Remote user abort indication received.FTAM: Invalid document type.FTAM: RSAM record too large to be written.FTAM: No shadow file.FTAM: Inconsistent shadow file.FTAM: No document type.FTAM: Wrong r emote system destination.FTAM: Unknown FTAM error.Compresssion APIs: Invalid workarea. This error can be returned from all three compression APIs. This error can occur when the pointer to the workarea is NIL, the workarea size is too small, or the workarea header information becomes corrupt during a CompressData or DecompressData call.Compresssion APIs: Data not compressed. This error is returned from a DecompressData call when the data being sent has not been compressed.Compresssion APIs: Exceeds max bits. This error is returned from a DecompressData call when the data being decompressed has been compressed using a compatible compression algorithm (UNIX Compress) and more than twelve bits were specified (UNIX defaults to 16 bits) as the codeword size. Compresssion APIs: Invalid buffer. This error is returned from either the CompressData or DecompressData call when the source or destination buffers are invalid.Compresssion APIs: Compression/Decompression Incomplete. This error is returned when the source buffer sent to the compress or decompress API has not been entirely processed.Message Control System II: Array too small. The ECOConnect call failed because the length of pSubQsRet is too small to hold the number of subqueues specified in nSubQs.Message Control System II: No such program ID. The program specified by pYrId does not exist, making one of the following calls fail: ECOConnet, ECODisconnect, ECOProgStatus, ECOQueryConnections, ECOQueryTraces, ECOSendString, ECOStartTrace, or ECOStopTrace.Message Control System II: Connection. This is a status message indicating that another application connected one of its subqueues to a subqueue of the application that returned this status code.Message Control System II: Invalid message length. The ECOSendString call failed because the message length in cbMsg was set to 0.Message Control System II: Invalid subqueue. An invalid subqueue was specified in one of the following calls: ECONameSubQ, ECOSendString, or ECOStartTrace.Message Control System II: Subqueue number and subqueue name. The ECOSendString call failed because both a subqueue number (wSubQ) and a subqueue name (pSubQName) were specified.Message Control System II: No public subqueue. The program specified by pProgId or wECOId does not have a subqueue named Public, making one of the following calls fail: ECOProgStatus, ECOQueryProgIds, ECOQueryTraces, ECOSendString, or ECOQueryConnections.Message Control System II: Invalid number of subqueues. The ECOConnect call failed because there is an invalid number of subqueues in nSubQs (the number must be greater than zero).Message Control System II: No YrID. The ECODisconnect call failed because a nonzero value was specified for both wSubQ and pYrId.Message Control System II: No Subqueue name. The ECODisconnect call failed because a nonzero value was specified for pSubQName and either wSubQ is nonzero or pYrId is null.Message Control System II: No ECO. An ECO call failed because the ECO is unavailable. Message Control System II:  Connection not traced. The ECOStopTrace call failed because this program is not tracing one of the connections specified in the pbConnections array. Any specified connections that are being traced are turned off.Message Control System II: Invalid parameter. One of the parameters in a CO or ECO call is invalid and would cause a general protection (GP) fault if allowed to pass through.Message Control System II: Invalid message index. The ECORead or ECOReadGet call failed because wMsgIndex is zero.Message Control System II: Disconnect. This is a status message indicating that an application disconnected one of its subqueue from a subqueue in the application that returned this status code.Message Control System II: Census time out. The ECOSubQCensus call timed out. The current census data is returned. Message Control System II: Invalid subqueue name. The ECONameSubQ call failed because the subqueue name is invalid (name cannot contain internal spaces).Message Control System II: Subqueue frozen. An ECO call failed because the limit for the connected subqueue is zero.Message Control System II: Trace already. The ECOStartTrace call failed because one or more of the specified connections is already being traced. Message Control System II: Quit trace. This is a status message indicating that one of the Program Ids being traced either terminated or was disabled, and is no longer in the MCSII network.Message Control System II: Log file. An internal error occurred in handling the ECO log file.Message Control System II: Invalid log class. The ECOLog call failed because the Log Class was specified as 1 (ECO), which is reserved for internal MCSII use only. Message Control System: All COIDs are unavailable. Communication with the CO Module is denied. Message Control System II (MCSII): The ECOEnable call failed because there is not enough memory to allocate a new ECOId.Message Control System, MCS II: An attempt was made to disable queues without closing them. Message Control System, MCS II: Invalid COID.Message Control System, MCS II: Invalid QID.Message Control System, MCS II: Invalid COID/QID match.Message Control System: Invalid command.Message Control System, MCS II: Two queues are already opened for this COID; an attempt was made to open a third queue.Message Control System. MCS II: An attempt was made to allocate more than 254 subqueues per queue.Message Control System. MCS II: At least one subqueue must be opened. Message Control System: No subqueues available to be allocated. MCS II:  Not enough memory available to allocate subqueues.Message Control System: No parameter is specified in the MyID field for the COOpenQ function. MCS II: The ECOEnable call failed because the pMyId field is either invalid or empty.Message Control System: A queue reading with the fWait flag set or a queue census is outstanding. Message Control System: No TiID parameter was specified in the COOpenQ function.Message Control System: The queue specified for opening does not have enough subqueues attached. Message Control System: No queues are available for the opening request. MCS II: This is a CO error. There is not enough memory to allocate data structures of the COOpenQ call.Message Control System, MCS II: The MyID and YrID parameters do not match the first queue.Message Control System, MCS II: An attempt was made to close a queue without clearing the messages.Message Control System: Invalid MsgRef parameter specified in the COPutString or COPutWrite function (valid entries are 1-5).Message Control System, MCS II: Message length was specified as zero in the COPutString or COPutWrite function.Message Control System: The message specified to be updated is not stored in the buffer. MCS II: Either the ECOPutString or ECOPutWrite call failed because while fOld is true, but there is no message in the msgref to be updated.Message Control System: No buffers are currently available. MCS II: An ECO call failed because the internal heap is full (not enough memory to store the message). If you get this error consistently, reinstall the ECO with a bigger heap size.Message Control System: An attempt was made to open a queue with a previously allocated MyID parameter.Message Control System: The new message length exceeds the length of the existing message. MCS II: Either the ECOPutString or ECOPutWrite call failed because the total size of the resulting message would exceed the maximum message size (wMsgLength).Message Control System, MCS II: The queue limit specified is greater than 127.Message Control System, MCS II: An invalid subqueue was specified in the SetQLimit function.Message Control System, MCS II: Invalid MsgRef buffer specified.Message Control System: An attempt was made to retrieve a message portion starting past the size of the message. MCS II: Either the ECOGetString or ECOReadGet call failed because oMsg exceeds the message length.Message Control System, MCS II: Message length was specified as zero in the COGetString or COReadGet function.Message Control System: No message currently resides in the MsgRef specified. MCS II: The ECOGetString call failed because there are no message in the work area specified by wMsgRef.Message Control System, MCS II: Invalid subqueue specified in the COClear function.Message Control System, MCS II: Invalid message buffer.Message Control System: No message currently resides in the message buffer specified in the writing function. MCS II: The ECOWrite call failed because there are no messages in the work area specified by wMsgRef.Message Control System: Invalid subqueue specified in the writing function. MCS II: Either the ECOWrite or ECOPutWrite call failed because the specified subqueue is invalid.Message Control System, MCS II: An attempt was made to write a message to a disconnected subqueue.Message Control System. MCS II: The attached subqueue has reached its limit. No messages can be written.Message Control System, MCS II: Internal error. Reboot the system and report the error to a Unisys field representative.Message Control System: I nvalid subqueue specified in the COReadQ function. MCS II: Either the ECORead or ECOReadGet call failed because the subqueue is invalid.Message Control System: No message is available for the COReadQ function. MCS II: Either the ECORead or ECOReadGet call failed because there is no message available waiting to be read or the read timed out before a message was available.Message Control System: Invalid message buffer specified in reading function. MCS II: This is a CO error. The message buffer specified in either the COReadQueue or COReadGet call is invalid.Message Control System: Participating subqueues were specified for reading, but the value in the SubQ field of the reading function is not 255. Or a specific subqueue was designated for reading, but the value in the SubQ field of the reading function is greater than 254. MCS II: This is a CO error. The value for SubQ in the COReadGet or COReadQueue call is invalid. It must be 0 to read the first available message (FIFO), 1-254 to read a specific subqueue, or 255 to read participating subqueues.Message Control System, MCS II: An invalid subqueue was detected by the COReadQueue function.Message Control System, MCS II: A wait option is already specified for this queue.Message Control System, MCS II: Invalid subqueue specified in the COQCensus function.Message Control System, MCS II: A wait option is already specified for this queue. MCS II: The ECOSubQCensus call failed because another ECOSubQCensus call, with a wait option, is already active for this ECOId.Message Control System, MCS II: Invalid subqueue specified in the COQLimit function.Message Control System: Invalid subqueue specified in the CORecall function. MCS II: The ECORecall call failed because the value specified for wSubQ is invalid.Message Control System: The number of subqueues available is not enough to perform the COConnect function. MCS II: The ECOConnect call failed because there are not enough subqueues available in the connecting application.Message Control System: The TiID was not specified in the COConnect function. MCS II: This is a CO error. The QID was not specified in the COConnect function.Message Control System: The YrID parameter was not specified in the COConnect function. MCS II: The ECOConnect call failed because the pYrId parameter was not specified.Message Control System, MCS II: More than 253 messages reside in the queue.Message Control System: The buffer space available is not enough to duplicate the message. MCS II: There is an error in the ECO Library configuration file.Message Control System: An attempt was made to install an existing CO Module. MCS II: A copy of the ECO already exists, but the message file is either missing or invalid so an error message could not be displayed.Message Control System, MCS II: Invalid COID specified in the CORecallfunction.Message Control System, MCS II: Invalid QID specified in the CORecall function.Message Control System, MCS II: Invalid subqueue specified for in the CORecall function.Message Control System, MCS II: Message from the CO Module informing the receiving program that this subqueue is no longer communicating with the previously connected program.Message Control System, MCS II: The number of subqueues available is not enough to perform the COConnect function.Message Control System: The TiID and YrID parameters are not connected with the queue specified in this function. MCS II: The ECODisconnect call failed because the specified ECOId is not connected to any specified subqueue.Message Control System, MCS II: Messages still reside in the subqueues specified for disconnection.Message Control System: The pointer specified for the COGetString function has not been initialized or has a segment below 1200.Message Control System: The pointer specified for the COPutString function has not been initialized or has a segment below 1200.Message Control System, MCS II: Invalid subqueue specified in the COUpdate function.Message Control System: Offer status out of range. MCS II: The ECOUpdate call failed because either wOfferStatus is invalid or recovery was specified with an invalid entry for wSubQ (wSubQ must be 0 for recovery).Message Control System: No room left in the Subqueue Name table.Message Control System: The subqueue name specified for this function does not exist. MCS II: Either the ECOConnect or ECODisconnect or ECOSendString call failed because the specified subqueue name specified does not exist.Message Control System: The subqueue name specified in the COConnect function is in use. MCS II: The ECOConnect call failed because there are not enough subqueues with the specified name in the application.Message Control System: Invalid number of users specified for the CO Module.Message Control System: The destination subqueue to which this message is written is temporarily terminated. The recovery option was specified for that program so that when it is reinitialized the previous connection will be reestablished. MCS II: Either the ECOPutWrite or ECOWrite call failed because the message is written to a destination subqueue that is temporarily terminated. The recovery option was specified for that program so that when it is reinitialized, the previous connection will be reestablished.Message Control System, MCS II: The program to which this program is attached is temporarily terminated with the recovery option in effect. When this program is reinitialized, the previous connection will be reestablished.Message Control System: The program queue being opened had temporarily terminated, but is being reopened with the previous connection in effect. MCS II: This is a status message indicating that an application that terminated re-enabled using the same Program ID as before termination. This message occurs when an application specifies recovery (through the ECOUpdate call) prior to termination. Note that E_RECOVERY is also sent to the subqueues of any application that is connected to the re-enabled application.Message Control System, MCS II: The subqueue specified for disconnection is invalid.Message Control System, MCS II: Indicates that 80% of the CO memory capacity has been used.Message Control System, MCS II: Indicates that 98% of the CO memory capacity has been used.Message Control System, MCS II: The MsgRef specified in the COMaint function is invalid.Message Control System, MCS II: The second MsgRef specified in the COMaint function is invalid. Message references have a valid range of 1 to 5. The parameter for the second message is not in the correct range.SNA LUIS AGENT: Data must be entered. Enter a value in the field indicated by the cursor.SNA LUIS AGENT: Data must be entered in the required field. Enter values in all the required fields of the screen, then save the screen.SNA LUIS AGENT: DCP Number must be from 3 - 6. Enter a data communications processor (DCP) number from 3 to 6.SNA LUIS AGENT: Line Number must be from 1 - 8. Enter a number from 1 to 8.SNA LUIS AGENT: LSN Number must be from 1 - 140. Enter numbers from 1 to 140 in the logged station number (LSN) Lower Limit and LSN Upper Limit fields.SNA LUIS AGENT: Upper LSN must not be less than LOWER LSN. Either enter a number in the LSN Upper Limit field that is greater than or equal to the number in the LSN Lower Limit field, or enter a number in the LSN Lower Limit field that is less than or equal to the number in the LSN Upper Limit field.SNA LUIS AGENT: LU Number must be from 1 - 32. Enter a logical unit (LU) number from 1 to 32.SNA LUIS AGENT: Upper LU must not be less than Lower LU. Either enter a number in the LU Upper Limit field that is greater than or equal to the number in the LU Lower Limit field, or enter a number in the LU Lower Limit field that is less than or equal to the number in the LU Upper Limit field.SNA LUIS AGENT: LU Range must equal LSN range. Modify the numbers in either the LSN upper or lower limits or in the LU upper or lower limits so that the difference between the LSN upper and lower limits equals the difference between the LU upper and lower limits.SNA LUIS AGENT:  All stations already defined. The number of stations already defined equals the range of LSNs and LUs. To add another station, you must first increase the range of the LSNs and LUs -- that is, increase the difference between the lower limits and upper limits.SNA LUIS AGENT: Station name already exists. A station with this name has already been defined. Enter a different station name.SNA LUIS AGENT: LU Type must be 0 or 2 or 3. Enter an 0, 2 or 3 in the Logical Unit (LU) field.SNA LUIS AGENT: WARNING: This option is not valid for LU 2 or 3. This option is not used with the LU type entered. Change the option to NO.SNA LUIS AGENT: WARNING: This option is not valid for LU 0. This option is not used with the LU type entered. Change the option to NO.SNA LUIS AGENT: First character must be alpha or special. The first character in the name must be alphabetic, [, ], <, >, or !.SNA LUIS AGENT: Character must be alphanumeric or special. The first character in the name must be alphanumeric, [, ], <, > , or !.SNA LUIS AGENT: Input must be Yes (Y) or No (N). Enter a Y or N.SNA LUIS AGENT: Invalid buffer size. Valid range is 0-4096. Enter buffer size in valid range.SNA LUIS AGENT: Received SNA Gateway Error (Error/code)/(Module No).SNA LUIS AGENT: Received LUIS Error (Error/code)/(Module No).SNA LUIS AGENT: Received CO Error (Error/code)/(Module No).SNA LUIS AGENT: Received MCM Error (Error/code)/(Module No).SNA LUIS AGENT: Received Undefined Error (Error/code)/(Module No).SNA LUIS AGENT: LU in Receive Mode.SNA LUIS AGENT: Received CO message > Host input buffer size.SNA LUIS AGENT: Received Not-Supported MCM Commands.SNA LUIS AGENT: SNA LUIS has not been installed.SNA LUIS AGENT: Communication Organizer (CO) has not been installed. SNA LUIS AGENT: MCM has not been installed.SNA LUIS AGENT: No station was defined in the configuration file.SNA LUIS AGENT: Received chaining error.SNA LUIS AGENT: MCM Initialization was not successful. Refer to the BTOS Message Control System Programming Reference Manual.SNA LUIS AGENT: Received BTOS Error (Error Code). Refer to the BTOS Message Control System Programming Reference Manual.SNA LUIS AGENT: The input is not SNA LUIS 2.0 Agent Configuration File. Refer to BTOS SNA Logical Unit Interface System (LUIS) Operations and Programming Guide.SNA LUIS AGENT: Received TEM Error (Error Code)/(Module No.). Refer to BTOS Teller Extension Module (TEM) Programming Reference Manual.SNA LUIS AGENT: Too many Errors Received in one Message Handling Sequence. Ready the station again.SNA LUIS AGENT: WARNING: Cryptography was specified but TEM Server has not been installed. Install TEM Server.X.25 Agent Configurator: MCS DTE address is required. Press CANCEL to continue. Enter an address in the MCS DTE Address field. (This message applies to releases prior to 9.0.)X.25 Agent Configurator: First character must be alphabetic. Press CANCEL to continue. The first character of a remote DTE name or a station name must be a letter. Enter a new name with an alphabetic first character.X.25 Agent Configurator: Must enter Y or N. Press CANCEL to continue. Type Y or N in the field in which the cursor is displayed.X.25 Agent Configurator: Remote DTE address is required. Press CANCEL to continue. Enter an address in the Remote DTE Address field.X.25 Agent Configurator: Characters must be alphanumeric. Press CANCEL to continue. Enter an alphanumeric value in the field in which the cursor is displayed. X.25 Agent Configurator: Station does not exist. Press CANCEL to continue. A station with this name has not been defined. Display the Remote DTE and Station Names screen to determine the names of the stations that have been defined.X.25 Agent Configurator: Must enter T or P or O. Press CANCEL to continue. Type one of these values in the Type of Virtual Circuit field:  P - permanent  T - temporary, with the call originated by an MCS station and terminated at this remote DTE  O - Switched, with the call originated by the remote DTEX.25 Agent Configurator: When type of VC is O, initial status must be N. Press CANCEL to continue. When O is typed in the Type of Virtual Circuit field, you must type N in the Initial Station Status field. The value N indicates that the virtual circuit is not established when the X.25 Agent is initially executed. (This message applies to releases prior to 9.0.)X.25 Agent Configurator: When type of VC is P, initial status must be E. Press CANCEL to continue. When P is typed in the Type of Virtual Circuit field, you must type E in the Initial Station Status field. The value E indicates that the virtual circuit is established when the X.25 Agent is initially executed. (This message applies to releases prior to 9.0.)X.25 Agent Configurator: Must enter E or N. Press CANCEL to continue. Type one of these values in the Initial Station Status field:  E - the virtual circuit is established when the X.25 Agent is initially executed  N - the virtual circuit is not established when the X.25 Agent is initially executed (This message applies to releases prior to 9.0)X.25 Agent Configurator: Must enter F or R. Press CANCEL to continue. Type one of these values in the X.25 Call Charges for Temporary VC field:  F - the MCS DTE is charged for the X.25 call  R - the remote DTE is charged for the X.25 call (This message applies to releases prior to 9.0)X.25 Agent Configurator: Logical channel number is required for VC type P. Press CANCEL to continue. When P is typed in the Type of Virtual Circuit field, you must type a number from 1 to 32 in the Logical Channel Number field.X.25 Agent Configurator: DCP number is required. Press CANCEL to continue. Type a number from 3 to 6 in the DCP Number field.X.25 Agent Configurator: Lower limit of LSN is required. Press CANCEL to continue. Type a number from 1 to 999 in the Lower Limit of LSNs field.X.25 Agent Configurator: Upper limit of LSN is required. Press CANCEL to continue. Type a number from 1 to 999 in the Upper Limit of LSNs field. The upper limit of LSNs must be equal to or greater than the lower limit of LSNs. Also, the LSN range must be equal to or greater than the number of stations defined in the X.25 Configuration file.X.25 Agent Configurator: Upper LSN limit cannot be less than lower LSN limit. Press CANCEL to continue. Type a number in the Upper Limit of LSNs field that is equal to or greater than the number in the Lower Limit of LSNs field. Also make sure the LSN range is equal to or greater than the number of stations defined in the X.25 configuration file.X.25 Agent Configurator: Maximum packet size is required. Press CANCEL to continue. Type a number from 1 to 1024 in the Maximum Packet Size field.X.25 Agent Configurator: Enter a numeric value. Press CANCEL to continue. Type a numeric value in the field in which the cursor is displayed.X.25 Agent Configurator: Must enter number from 1 to 8. Press CANCEL to continue. Type a number from 1 to 8 in the Line Number field.X.25 Agent Configurator: Remote DTE does not exist. Press CANCEL to continue. A remote DTE with this name has not been defined. Display the Remote DTE and Station Names screen to determine the names of the remote DTEs that have been defined.X.25 Agent Configurator: Remote DTE name is required. Press CANCEL to continue. Type a name in the Remote DTE Name field.X.25 Agent Configurator: Station name is required. Press CANCEL to continue. Type a name in the Station Name field.X.25 Agent Configurator: Remote DTE already exists. Press CANCEL to continue. A remote DTE with this name has already been defined. If you want to add another remote DTE, type a different name.X.25 Agent Configurator: Station already exists. Press CANCEL to continue. A station with this name has already been defined. If you want to add another station, type a different name.X.25 Agent Configurator: DCP number must be from 3 to 6. Press CANCEL to continue. Type a number from 3 to 6 in the DCP Number field.X.25 Agent Configurator: Must enter number from 1 to 32. Press CANCEL to continue. Type a number from 1 to 32 in the Logical Channel Number for PVC field.X.25 Agent Configurator: File contains no data, select another option. Press CANCEL to continue. The X.25 configuration file named contains no defined remote DTEs, stations, or general information. There is no data to modify or delete. You can either:  Add remote DTEs and stations to this file  Create a new file  Exit the configuratorX.25 Agent Configurator: Cannot add - 31 stations already defined. Press CANCEL to continue. Thirty-one stations have already been defined for this file. That is the maximum number of stations for one file. To add more stations or remote DTEs, you must create another X.25 configuration file.X.25 Agent Configurator: Line number is required. Press CANCEL to continue. Enter a number from 1 to 8 in the Line Number field.X.25 Agent Configurator: Must enter number greater than 0. Press CANCEL to continue. Type a number greater than zero in the field in which the cursor is displayed.X.25 Agent Configurator: Must enter number from 1 to 999. Press CANCEL to continue. Type a number from 1 to 999 in the field in which the cursor is displayed.X.25 Agent Configurator: Must enter number from 1 to 1024. Press CANCEL to continue. Type a number from 1 to 1024 in the Maximum Packet Size field.X.25 Agent Configurator: Must increase LSN range to add station/remote DTE. Press CANCEL to continue. The LSN range equals the number of stations currently defined in this X.25 configuration file. To add another station or remote DTE, you must first increase the LSN range on the General Information screen.X.25 Agent Configurator: Must increase LSN range. xx stations already exist. Press CANCEL to continue. The LSN range is less than the number of stations currently defined in the X.25 configuration file. You must increase the LSN range so that it is equal to or greater than the number of stations already defined.X.25 Agent Configurator: Configuration file is corrupted. Recreate file. Press CANCEL to continue. An error condition  has corrupted the configuration file. You must recreate the file using the X.25 Agent Configurator.X.25 Agent Configurator: Remote DTE Address already exists. Press CANCEL to continue. A remote DTE with this address has already been defined. Type an address that has not been assigned to an existing remote DTE.X.25 Agent Configurator: Must enter number from 0 to 99. Press CANCEL to continue. Type a number from 0 to 99 in the field in which the cursor is displayed.X.25 Agent Configurator: Upper port number cannot be less than lower port number. Press CANCEL to continue. Type a number in the upper port number field that is equal to or greater than the number in the lower port number field.X.25 Agent Configurator: Incoming message delivered in parts to LSN = ZZZZZ. Here zzzzz is the five-digit logical station number for which the condition occurred. A message from a remote DTE is longer than the maximum message sizes. This message will be delivered in parts to the X.25 station. This error code could optionally be sent to the attached FSA Application.X.25 Agent Configurator: No free virtual circuits. Check the installation parameters for the X.25 Network Gateway. The number of stations may be greater than the number of virtual circuits. This error code could optionally be sent to the attached FSA Application.X.25 Agent Configurator: MCM is not installed or no more free subqueues in MCM. Subsystem error. Either of two conditions has occurred:  The Message Control Module was not installed before you tried to install the X.25 agent. In this case, install the Message Control Module.  There are no more free subqueues in the Message Control Module. In this case, more stations are being used concurrently than the Message Control System can handle. Either reduce the number of stations concurrently active or increase the number of stations the Message Control System can handle.X.25 Agent Configurator: X.25 Gateway is not installed. Subsystem error. The X.25 Network Gateway was not installed before you tried to install the X.25 Agent. Install the X.25 Network Gateway. X.25 Agent Configurator: MCM-DCP initialization error. Subsystem error. Check the DCP number, line number, and range of logical station numbers. One of these parameters may conflict with a similar parameter defined for another data communications processor running concurrently.X.25 Agent Configurator: CO is not installed. Subsystem error. The Communications Organizer module was not installed before you tried to install the X.25 agent. Install the Communications Organizer module.X.25 Agent Configurator: No stations defined in the configuration file. Subsystem error. Define the required X.25 stations in the configuration file using the X.25 Agent Configurator.X.25 Agent Configurator: DCP number, Line number, and LSN range are not defined. Subsystem error. You have not defined values for the parameters on the general information screen of the X.25 Agent Configurator. Define the data communications processor (DCP), line number and logical station number (LSN) fields before you continue.SNA LUIS AGENT: More than one of fPageAdvance, fMsgadvance, fMsgAdvanceProtected, FnextPage, or FmIDPresent is true.SNA LUIS AGENT: Range error. Check BuildFMH and InterpretFMH parameters in application program. Verify the validity of the host message.SNA LUIS AGENT: Range error. Check BuildFMH parameters in application program.SNA LUIS AGENT: Range error. Check BuildFMH and InterpretFMH parameters in application program. Verify the validity of the host message.SNA LUIS AGENT: SNAToggle indicates there is no FMH. SNAToggle indicates there is no FMH. Check InterpretFMH parameters in application program. Verify the validity of the host message.SNA LUIS AGENT: Range error. Range error. Check InterpretFMH parameters in application program. Verify the validity of the host message.SNA LUIS AGENT: HeaderType < > #42. Check InterpretFMH parameters in application program. Verify the validity of the host message.SNA LUIS AGENT: Range error. Check InterpretFMH parameters in application program. Verify the validity of the host message.SNA LUIS AGENT: Range error. Check InterpretFMH parameters in application program. Verify the validity of the host message.SNA LUIS AGENT: NO CLUAttach was performed or a CUUDetach was performed and then no CLUAttach. CLUAttach must be performed before any other function. Check application program.SNA LUIS AGENT: There is no LU 0 available. Repeat request.SNA LUIS AGENT: hCLU does not match a reserved hCLU. Check CLUSend or CLUCancel parameters in application program.SNA LUIS AGENT: The SNA Agent could not deliver the message to the LU defined by hCLU. Message length less than the required 28 bytes. Check application program.SNA LUIS AGENT: The SNA Agent could not deliver the message to the LU defined by hCLU. Check network status. Review network configuration.SNA LUIS AGENT: The user still has CLUs reserved. Application program did not perform CLUCancel on all reserved LUs. Check application program.SNA LUIS AGENT: SNA configuration file/CLU Manager version mismatch. Check the installation diskettes. Version numbers must be identical. Recreate configuration file using matching versions. This message is displayed on the screen.SNA LUIS AGENT: No CLU was defined in the configuration file. SNA LUIS AGENT: Line Not Ready or SNA LUIS Agent not installed.SNA LUIS AGENT: LU does not have same option and buffer size. SNA LUIS AGENT: Cannot attach LU. Check station status. Station is probably in a Not Ready state. This message can be displayed using the operator interface module.SNA LUIS AGENT: No CLU could be attached. Check station status. Station is probably in a Not Ready state. This message is displayed on the screen.SNA LUIS AGENT: Message received from unreserved CLU. Host replied to an unsent message. A system inconsistency has occurred. Notify the host's system administrator. This message can be displayed using the operator interface module.BMULTI Agent: Incorrect Configuration file name specification. The name you assigned to the configuration file does not match the file name in the processor's job control language (JCL) file.BMULTI Agent: Configuration file name cannot exceed 50 characters. Rename the configuration file. Verify that the new name matches that in the processor's JCL file.BMULTI Agent: Configuration file is corrupted. Delete and recreate the configuration file.BMULTI Agent: INTERNAL INCONSISTENCY. Report to System Administrator.BMULTI Agent: INTERNAL INCONSISTENCY. Report to System Administrator.BMULTI Agent: Form library file does not exist.BMULTI Agent: DCP number is required. Press CANCEL to continue. Enter a number between three and six in the data communications processor (DCP) Number field.BMULTI Agent: DCP number must be from 3 to 6. Press CANCEL to continue. Enter a number between three and six in the DCP Number field.BMULTI Agent: Line number is required. Press CANCEL to continue. Enter a number between one and eight in the Line Number field.BMULTI Agent: Line number should be from 1 to 8. Press CANCEL to continue. Enter a number between one and eight in the Line Number field.BMULTI Agent: Lower LSN limit is required. Press CANCEL to continue. Enter a number between 1 and 140 in the Logical Station Number (LSN) Lower Limit field.BMULTI Agent: Upper LSN limit is required. Press CANCEL to continue. Enter a number between 1 and 255 in the LSN Upper Limit field.BMULTI Agent: Upper limit cannot be less than lower. Press CANCEL to continue. Either enter a number in the LSN Upper Limit field that is greater than or equal to the number in the LSN Lower Limit field, or enter a number in the LSN Lower Limit field that is less than or equal to the number in the LSN Upper Limit field.BMULTI Agent: Must enter number from 1 to 140. Press CANCEL to continue. Enter a number between 1 and 140 in both LSN Lower Limit and LSN Upper Limit fields.BMULTI Agent: Must enter numeric value. Press any key to continue. Enter a number between 1 and 140 in both LSN Lower Limit and LSN Upper Limit fields.BMULTI Agent: Station name should be alphanumeric. Press CANCEL to continue. The first character of the station name must be alphabetic. The remaining characters must be alphanumeric.BMULTI Agent: Must increase LSN range to add stations. Press CANCEL to continue. All logical station numbers have been assigned. Expand the range between the lower and upper limits on the General Information screen if you wish to add stations.BMULTI Agent: Station name is required. Press CANCEL to continue. You must define the station name to which you will assign the device address.BMULTI Agent: First character must be alphabetic. Press CANCEL to continue. The first character of a station name must be alphabetic. The remaining characters must be alphanumeric.BMULTI Agent: Station already exists. Press CANCEL to continue. A station with this name has already been defined. Enter a different station name.BMULTI Agent: Device address a lready defined. Press CANCEL to continue. A device with this address has already been defined. Enter a different two-character value.BMULTI Agent: Control character must be hexadecimal. Press CANCEL to continue. Enter a hexadecimal value in the Network Control Character field that has not been previously assigned as a protocol control character, CRT message formatting character, or printer message formatting character.BMULTI Agent: Illegal character in device address. The value entered in the field is assigned to another BMULTI Agent function or allotted another meaning in the system. Enter another value for the device address.BMULTI Agent: Incorrect station name. Press CANCEL to continue. The station name must not contain a blank character. The first character must by alphabetic. The remaining characters must be alphanumeric.BMULTI Agent: Range not appropriate. Press CANCEL to continue. The number entered for the upper LSN range is lower than the range required for the number of stations defined.BMULTI Agent: Configuration file is corrupted. It has to be recreated. The system beeps and displays this message at the bottom of the screen if the agent cannot be successfully installed.BMULTI Agent: CO is not installed. The system beeps and displays this message at the bottom of the screen if the agent cannot be successfully installed. See the BTOS Message Control System Programming Reference Manual.BMULTI Agent: MCM is not installed or no free subqueue is available. The system beeps and displays this message at the bottom of the screen if the agent cannot be successfully installed.BMULTI Agent: BMULTI Gateway is not installed. The system beeps and displays this message at the bottom of the screen if the agent cannot be successfully installed.BMULTI Agent: No stations defined in the configuration file. The system beeps and displays this message at the bottom of the screen if the agent cannot be successfully installed.BMULTI Agent: DCP number, Line number and LSN range are not defined. The system beeps and displays this message at the bottom of the screen if the agent cannot be successfully installed.BMULTI Agent: MCM-DCP initialization error. The system beeps and displays this message at the bottom of the screen if the agent cannot be successfully installed. See the BTOS Message Control System Programming Reference Manual.BMULTI Agent: Retryable NAK response from the BMULTI Agent. The system returns this message to indicate a negative response to a selection or transmission if the Operator Interface Module of the Message Control System is installed. Retry the action. If unsuccessful, contact the host's system administrator. If the agent encounters errors while attempting to communicate with the BMULTI Gateway, the agent lists this error in the MCM error log file. Because this error is generated by actions from the host, contact the host's system administrator.BMULTI Agent: UnRetryable NAK response from the BMULTI Agent. The system returns this message to indicate a negative response to a selection or transmission if the Operator Interface Module of the Message Control System is installed. Contact host's system administrator. If the agent encounters errors while attempting to communicate with the BMULTI Gateway, the agent lists this error in the MCM error log file. BMULTI Agent: Host Not Ready. Contact host's system administrator. The system returns this message if the Operator Interface Module of the Message Control System is installed. If the agent encounters errors while attempting to communicate with the BMULTI Gateway, the agent lists this error in the MCM error log file. BMULTI Agent: Transmit Error. Contact host's system administrator. The system returns this message if the Operator Interface Module of the Message Control System is installed. If the agent encounters errors while attempting to communicate with the BMULTI Gateway, the agent lists this error in the MCM error log file. BMULTI Agent: Receive Error. Contact host's system administrator. The system returns this message if the Operator Interface Module of the Message Control System is installed. If the agent encounters errors while attempting to communicate with the BMULTI Gateway, the agent lists this error in the MCM error log file. BMULTI Agent: Receive Ready Error. Contact host's system administrator. The system returns this message if the Operator Interface Module of the Message Control System is installed. The application program executing in the poll/select environment and interfacing with the message control system (MCS) checks the DCPToggle field only when receiving messages from the host. If the value returned in this field is 1, it indicates a duplicate message sent from the host. If the value returned in this field is 2, it indicates a sequence number error detected by the agent. If the agent encounters errors while attempting to communicate with the BMULTI Gateway, the agent lists this error in the MCM error log file. BSC 3270 Agent: Incorrect Configuration file name specification. The name you assigned to the configuration file does not match the file name in the processor's JCL file.BSC 3270 Agent: Configuration file name cannot exceed 50 characters. Rename the configuration file. Verify that the new name matches that in the processor's JCL file.BSC 3270 Agent: Configuration file is corrupted. Delete and recreate the configuration file.BSC 3270 Agent: Internal inconsistency. Contact Unisys field engineering. A serious hardware and/or software incompatibility has occurred. Contact your Unisys field representative.BSC 3270 Agent: Form library file does not exist. Recopy product disk.BSC 3270 Agent: DCP number is required. Press CANCEL to continue. Enter a number between three and six in the DCP Number field.BSC 3270 Agent: DCP number must be from 3 to 6. Press CANCEL to continue. Enter a number between three and six in the DCP Number field.BSC 3270 Agent: Line number is required. Press CANCEL to continue. Enter a number between one and eight in the Line Number field.BSC 3270 Agent: Line number should be from 1 to 8. Press CANCEL to continue. Enter a number between one and eight in the Line Number field.BSC 3270 Agent: Lower LSN limit is required. Press CANCEL to continue. Enter a number between 1 and 140 in the LSN Lower Limit field.BSC 3270 Agent: Upper LSN limit is required. Press CANCEL to continue. Enter a number between 1 and 140 in the LSN Upper Limit field.BSC 3270 Agent: Upper limit cannot be less than lower. Press CANCEL to continue. Either enter a number in the LSN Upper Limit field that is greater than or equal to the number in the LSN Lower Limit field, or enter a number in the LSN Lower Limit field that is less than or equal to the number in the LSN Upper Limit field.BSC 3270 Agent: Must enter number from 1 to 140. Press CANCEL to continue. Enter a number between 1 and 140 in both LSN Lower Limit and LSN Upper Limit fields.BSC 3270 Agent: Must enter numeric value. Press CANCEL to continue. Enter a number between 1 and 140 in both LSN Lower Limit and LSN Upper Limit fields.BSC 3270 Agent: Station name should be alphanumeric. Press CANCEL to continue. The first character of a station name must be alphabetic. The remaining characters must be alphanumeric.BSC 3270 Agent: Must increase LSN range to add stations. Press CANCEL to continue. All logical station numbers have been assigned. Expand the range between the lower and upper limits on the General Information screen if you wish to add stations.BSC 3270 Agent: Station name is required. Press CANCEL to continue. You must define the station name to which you will assign the device address.BSC 3270 Agent: First character must be alphabetic. Press CANCEL to continue. The first character of a station name must be alphabetic. The remaining characters must be alphanumeric.BSC 3270 Agent: Station already exists. Press CANCEL to continue. A station with this name has already been defined. Enter a different station name.BSC 3270 Agent: Device address already defined. Press CANCEL to continue. A device with this address has already been defined. Enter a unique number between 0 and 31.BSC 3270 Agent: Control character must be hexadecimal. Press CANCEL to continue. Enter a hexadecimal value in the network control character field that has not been previously assigned as an Enhanced BSC 3270 protocol control character, CRT message formatting character, or printer message formatting character.BSC 3270 Agent: Device address should be from 0 to 31. Press CANCEL to continue. Enter a unique number between 0 and 31.BSC 3270 Agent: Incorrect station name. Press CANCEL to continue. A station name cannot contain any blanks. All characters in the name must be contiguous.BSC 3270 Agent: Range not appropriate. Press CANCEL to continue. You cannot decrease the LSN values to a range that is less than the number of stations currently defined. Recalculate the LSN range.BSC 3270 Agent: Configuration file is corrupted. It has to be recreated.BSC 3270 Agent: CO is not installed.BS C 3270 Agent: MCM is not installed or no more free subqueues in MCM.BSC 3270 Agent: BSC 3270 Driver is not installed.BSC 3270 Agent: No stations defined in the configuration file.BSC 3270 Agent: DCP number, Line number and LSN range are not defined.BSC 3270 Agent: MCM-DCP initialization error. The values in the configuration file are not compatible with the NCD parameters. For example, the DCP number in the configuration file is not unique or the number of stations defined in the NCD is too small. Review your MCS environment configuration.BSC 3270 Agent: Discarded a message from host to a Not Ready station. If you encounter this error message using the operator interface module, a message from the host has been lost. Contact the host's system administrator.BSC 3270 Agent: No response for keyboard attention request. No user response is required.Device Service: Device is in use. An attempt is being made to open a device that is currently in use by another application. Only one application can open a device at any time.Device Service: Device is not in use.Device Service: Device is not found. An invalid device name is specified in a DSOpenDevice call. Make sure the device is turned on, or check the connection to the device.Device Service: Device is a bad type.Device Service: Device is not ready.Device Service: Bad character received from the AP1330 printer.Device Service: Bad device status.Device Service: User buffer overflow. Application buffer is not large enough to receive all the data. For the MCR, the returned message has been truncated to the size of the receiving buffer.Device Service: No device freed.Device Service: Device rank overflow.Device Service: Bad device specification.Device Service: Device already present. An attempt is being made to dynamically load a device driver that is already in memory.Device Service: Bad port specification.Device Service: Transmission error for the OCR, TAU, or AMP. Data received has an invalid format.Device Service: Receive error on EF4550. Bad Block Check Character received after several attempts. Try the operation again with a different magnetic card. MCR or PIN: BCC calculated from data received from the device does not match BCC sent by the device.Device Service: EF455X module not present. The MCR reader or PIN keypad or both, are not present on the converter box.Device Service: EF455X system error. System error for the MCR device, PIN keypad, or both. Check the MCR device and PIN keypad connection.Device Service: A CancelPINMCR function occurred while no operation was pending.Device Service: Invalid line number specified in an EF455X command.Device Service: Bad device handle. An invalid device handle is specified in an API call to access an open device. Verify that the handle used was returned in a successful DSOpenDevice call.Device Service: Bad count for the list of notes (TAU). Count must be a multiple of three. Buffer length for a DSReadDevice is smaller than length of data received from a Dispense, MoveForward, or ReXmitLastDispense command.Device Service: Invalid parameter for a function of the TAU device. Make sure the sHopperSerialNumberMax parameter is a multiple of seven. Buffer length for a DSReadDevice is smaller than length of data received from a Reset or from a SendCassette commandDevice Service: Bad S-BUS initialization.Device Service: Bad character has been received from the AMP.Device Service: The AMP module selected is not present.Device Service: Invalid translate table size. The translate table size must be 0 if the table is unspecified or 16 if the table is specified.Device Service: AMP timeout. The device has begun to send a response consisting of several characters, but the last character of that sequence has not been received within two seconds. Try the operation again. If the operation is unsuccessful, turn the printer off and back on.Device Service: Internal AMP keys buffer overflow. The AMP has sent at least 32 key codes and the application program has not read them. All keys are lost.Device Service: Device not declared at the workstation trying to free this device.Device Service: The Device Service cannot be reinstalled on a single-partition operating system. Device Service: There is no Sharing Processor on the network. This error occurs when you are trying to access the Device Sharing Processor by issuing a ConfigureDevServer request with a shareable device.Device Service: The maximum number of shareable devices is greater that the maximum number of Client Agents.Device Service: Client Agent not installed. Device Service was not installed with at least one shareable device. Reinstall the Device Service to add a new shareable device.Device Service: Device Service not installed.Device Service: Key-to-key mode required for this operation.Device Service: Device Service is not yet installed. This code returns when you install the Device Service from an application with the NoWait option. Check later to see that it has been successfully installed before attempting to use it.Device Service: The position where to display a character to a PIN Pad device is invalid.Device Service: Character to be displayed is not in the range of the characters which can be displayed to a PIN Pad device.Device Service: Character to be echoed by a PIN Pad device when a key is hit is invalid.Device Service: The value for the validation key is invalid.Device Service: Device Service was not installed. It cannot be installed from the application program on a workstation running in a single-partition operating system.Device Service: With Device Service Type II, the Device Service Module that handles the device has not been installed on a remote workstation. The remote device specified does not exist or is not shareable. This code is not used with Type I Device Services. Device Service Type I: Reserved.Device Service: The Device Service has not been loaded in the specified partition.Device Service: With Device Service Type II, a remote device must be shareable when you issue a ConfigureDevServer request to add a new remote device. Device Service Type I: Reserved.Device Service: With Device Service Type II, there is a Mismatch between bLocation and ServerWSID fields of the new device descriptor. ServerWSID field must not be blank to declare a remote device. Device Service Type I: Reserved.Device Service: With Device Service Type II, the data buffer is too large. The maximum size of the internal buffer to transfer data from one workstation to another is limited to 3 Kb to send and 1 Kb to receive. Device Service Type I: Reserved.Device Service: Access to the MCR on I-Bus is denied because it is not physically attached on the workstation on which the application program is running. Remote MCRs are not shareable.Device Service: With Device Service Type II, the problem occurs while communicating with the Communications Organizer (CO) module with a single-partition operating system. Either the server workstation went down or the CO itself disabled access to it. Device Service Type I: Reserved.Device Service: A command is in process. The command is not allowed now because another command is already being processed for the device. Cancel it or complete it before issuing another command.Device Service: EF455X internal error.Device Service: A command has not been acknowleged by the device.Device Service: EF4554 power failure. MCR or PIN: Encrypting PIN Pad memory problem has occurred: power failure, key alteration, or key not initialized.Device Service: Invalid PIN length for an EPPGetPIN. Either the minimum or maximum PIN length is not in the range (hex) 30 through 3C, or the minimum is greater than the maximum.Device Service: Invalid PAN length. The Primary Account Number to be sent to the device exceeds the maximum length of 16 characters.Device Service: Invalid parameter for EPPGetPIN. One of the passed structure's bytes, 2, 3, or 4, not equal to (hex) 30 or 31.Device Service: Invalid application buffer length. Either the message to send is too large, or the receive buffer is not large enough.Device Service: Invalid command. The Command parameter sent to the SendEPPCmd function is not in the range 1 through 11.Device Service: A key alteration occurred. Keys have been altered. The buffer returned to the application contains information about the keys involved.Device Service: Module not available.Device Service: OCR not available.Device Service: Invalid command.Device Service: Command not allowed now.Device Service: Invalid parameter.Device Service: Too many parameters.Device Service: Syntax error.Device Service: Invalid font.Device Service: Invalid version.Device Service: Horizontal parameter out of range. Use a form that is wide enough for the AMP printer.Device Service: Vertical parameter out of range. Use a form that is long enough for the AMP printer.Device Service: APR function not available.Device Service: With APR, this indicates corrupted data.Device Service: With APR, this indicates no data or blank magnetic strip.Device Service: Input buffer overflow. Device Service: Parity error.Device Service: Framing error.Device Service: Overrun error.Device Service: Cover closed.Device Service: Stop key pressed.Device Service: Cover opened.Device Service: Module out of paper.Device Service: Unsuccessful insert.Device Service: Paper removed.Device Service: Station 1 (left) key pressed.Device Service: Station 2 (right) key pressed.Device Service: ROM error. Call Unisys service personnel.Device Service: RAM error. Call Unisys service personnel.Device Service: NVM alteration. Call Unisys service personnel.Device Service: Display or configuration board error. Call Unisys service personnel.Device Service: RS-232-C controller error. Call Unisys service personnel.Device Service: Motor controller error. Call Unisys service personnel.Device Service: Manual deselection.Device Service: Status mask error. The status mask selected is inconsistent. Internal use.Device Service: Receive queue overflow. There is not enough room in the receive queue, or the receive queue has not been read by the application.Device Service: Receive overrun. A character is not read from the hardware before the next character arrives.Device Service: Line in use. Communication port is already used by another software application.Device Service: Parity error detected. A parity error has been detected while receiving a character.Device Service: Communication parameters unavailable. Parameters such as baud rate or byte size are not supported, or memory allocation for input/output queues failed.Device Service: Buffer too small. It must be 1024 bytes to allow device independence Internal use.Device Service: 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 (typically, the character is worthless).Device Service: A break signal has been received after the last byte returned has been received.Device Service: Transmit queue full while trying to queue a character. The device cannot accept any other character because its buffer is full.Device Service: Bad channel specification. Channel specified to communicate with the device is invalid.Device Service: Function not implemented. The function requested is not supported by a device driver.Device Service: An attempt is made to use PEM/TEM port while PEM/TEM software is not installed or while no PEM/TEM module is connected to the workstation.Device Service: Message code invalid Internal use.Device Service: Message length invalid Internal use.Device Service: Message type invalid: RequestOrResponse field Internal use.Device Service: Invalid null pointer received.Device Service: Field size invalid; null size specified.Device Service: Unexpected message type. Function not supported by a specific device driver.Device Service: Invalid module code. Module selected does not match one of the modules supported by the device.Device Service: Type of status specified for DSGetDeviceStatus is incorrect or not supported by the device driver.Device Service: Invalid control code for a DSSetDeviceControl or within a DSWriteDevice. This control code is not supported by the device driver.Device Service: Parameter table associated with a control code contains wrong information.Device Service: Command not allowed; status is pending. Read the pending status and reissue the command.Device Service: Command not allowed. Initport command failed Internal use.Device Service: Command not allowed. A Deinstall message has been received. Internal use.Device Service: An invalid sequence has been found in data from a DSWriteDevice.Device Service: Device is not initialized. Internal use.Device Service: Command not allowed (DSReadDevice, DSWriteDevice, DSGetGetDeviceStatus or DSSetDeviceControl is not allowed now).Device Service: DSReadDevice is not allowed with the selected module.Device Service: Device is already initialized. An attempt to perform an InitDevice fails because of a pervious successful InitDevice Internal use.Device Service: Reset procedure is not completed. A new reset has to be performed.Device Service: The control code used in a DSSetDeviceControl or in a DsWriteDevice is not compatible with the module selected.Device Service: No valid user number. Internal use.Device Service: Command not allowed; data is pending. A DSReadDevice must be performed to read data received by the device driver before sending any other command.Device Service: Flag to update the user number is invalid, not 0/1 Internal use.Device Service: Device is not connected or not ready. An attempt to talk to the device has failed because the device is not ready, offline, or disconnected.Device Service: Maximum number of notes to be delivered can not be more than 100.Device Service: Invalid Teller identifier; value must be 0 or 1.Device Service: Buffer length for a DSReadDevice is smaller than length of data to be read.Device Service: Total number of notes requested for MoveForwardNotes or DispenseNotes control codes should not be 0.Device Service: ETX character not found because the driver has not received this character or because application buffer length is smaller than the data received.Device Service: Bad BCC. BCC calculated from data received from the device connected through an I-Bus does not match BCC sent by the MCR.Device Service: Some data has been lost for the MCR connected through an I-Bus.Device Service: No more device handles. The maximum number of devices that can be opened simultaneously from a workstation has been exceeded. Currently, this limit is set to 20.Device Service: Driver time out. A device driver has not responded in time to a message from the Driver Manager. Try unloading the driver and reloading it again.Device Service: Driver Manager deinstallation error. Device Service has encountered a fatal error. Try deinstalling it and reinstalling it again. If Device Service does not deinstall successfully, reboot the workstation.Device Service: Cannot access configuration file. The configuration file specified during Device Service installation is not accessible. Check if it is in use by another application or if the communication link between the local workstation and the workstation having this configuration file is broken.Device Service: Invalid parameter A DSGetDeviceList call has been made with the location parameter invalid. Check that the value passed for this parameter is valid.Device Service: No Station name. Device Service cannot get the Station name for the local workstation during installation. Verify that there is a valid station configuration and that the Station ID Service is installed in memory prior to installing Device Service in memory.Device Service: Invalid configuration block size. A DSDeviceConfigure call has specified an invalid configuration block size.Device Service: Cannot configure remote workstation. An attempt has been made to dynamically load a device driver on a remote workstation. Applications can dynamically load device drivers only on the local workstation. Verify that the Station name specified is the local Station name.Device Service: Invalid error code return size. The size of the ErcDetails structure specified in an API call is less than the minimum required by Device Service. Verify that the size is big enough to hold all of the mandatory fields of the ErcDetails structure.Device Service: Invalid request size. The request is too large to be routed to a remote station. Verify that the buffer size specified is less that 2K bytes.Device Service: Cannot open MCS queue. Device Service encountered an error while trying to open communication with MCS. It may be due to a duplicate Station name in the network. Note that the first 8 characters of the Station name must be unique in the network.Device Service: No more shareable devices. There is a limit on the number of shareable devices that can be attached to a workstation before sharing them using MCS. The maximum number is currently set to a high value (approximately 12 per workstation), and as such, an application should not receive this error code. Contact Unisys support service if you get this error code.Device Service: Cannot route by BNET. If you are running applications that were written based on Device Service 6.x, you will not be able to share devices within your workgroup using BNet. You can only access devices connected to your local workstation. Device Service 7.0 returns this error code if your application attempts to access a remote shareable device. If you need to access a remote device you have two options: either relink your program using DSPlm.Lib or use MCS for device sharing. See the Device Service documentation for more details.TEM, PEM: Invalid buffer size. The buffer cannot exceed 64Kb word boundary.TEM Release 5.0: DES (Data Encryption Standard) is already in use, or a DES operation is in progress following a termination. Only the CANCEL function is allowed while a DES operation is in progress.TEM Release 5 .0: The TEM unit interrupt handler is already set. This status code occurs when more than one call to the InitTEMInterruptHandler command is done. PEM Release 6.0: Bad Hardware Configuration A TEM has been installed on a B28 workstation or a PEM and SHW have been installed together.TEM, PEM: The TEM unit is not present or (TEM Release 5.0) the InitTEMInterruptHandler command has not been sent prior to using the TEM unit.TEM Release 5.0: DES function has been cancelled. PEM Release 6.0: Command has been cancelled. This status is returned for a function that is aborted by a CANCEL command.TEM Release 5.0: TEM is reserved. PEM Release 6.0: Feature is already reserved. A Reserve function has failed because a Release function has not been executed or the feature has been reserved by someone else.TEM, PEM: Invalid type for Release or Reserve function. TEM Release 5.0: Values for the type are: 0-CMOS 1-DES 2-Port 3-Port D 4-S-bus PEM Release 6.0: Valid values for the type are: 0-CMOS 1-DES 2-Port TEA 3-Port TEB 4-Port TES 5-Not available 6-Port FSA A The ports referenced by PortTEA, PortTEB and PortTES vary according to the hardware you use (B24, PEM, TEM or B28-EXP); refer to the PEM Server manual for a list of hardware and specific ports.PEM Server, TEM Server: PEM/TEM server already installed.PEM Release 6.0: An attempt to release a feature that has not been previously reserved has been made.PEM Release 6.0: X-Bus timeout. There is no further response from the PEM because the PEMServer has unlocked the X-Bus structure without the authorization of the PEM firmware.PEM Release 6.0: NVM(Non Volatile Memory) not available.TEM Server, PEM Server: Invalid offset. An odd or oversize offset has been sent with a nonvolatile memory (NVM) command.TEM Server, PEM Server: A BCC error has been detected in the nonvolatile memory (NVM).PEM Release 6.0: No such command. The command sent to the PEM/TEM is not available in this version of the module.PEM Release 6.0: DMA transfer problem between the CPU and the B24-SM.TEM Server, PEM Server: Receive error. This message usually means a configuration problem in the Universal Asynchronous Receiver/Transmitter (UARTs).TEM Server, PEM Server: Specified timeout has elapsed during a read, write, or checkpoint operation.TEM Server, PEM Server: Bad configuration. An SBusRead or SBusWrite function has been sent but the S-Bus port (port E for Release 5.0, and port TES for Release 6.0) has been configured using the RS232Configure function.TEM Server, PEM Server: No DTR on the S-Bus. The S-Bus does not have a Data Terminal Ready (DTR) signal. Therefore, Set and Reset DTR functions cannot be used.TEM Server, PEM Server: No such port. An RS-232-C command has been attempted on a nonexistent port.TEM Server, PEM Server: DES feature not available.TEM Server, PEM Server: Master Key not loaded. A Master Key must be present in order to use DES commands.TEM Release 5.0: An error has occurred in loading a master or session key. PEM Release 6.0: Key Error. An error occurred when loading a Master or a Data Key.TEM Server, PEM Server: Encrypt/Decrypt Error. An error has occurred in encrypting or decrypting a text.TEM Server, PEM Server: DES count must be modulo 8. The Decrypt command (ECBorCBCmodes) has been attempted on a text that has a number of characters that is not a multiple of 8.TEM Server, PEM Server: DES count must be even. The Encrypt function has been attempted on a text that does not have an even number of characters.TEM Server, PEM Server: DES count out of range. The PEM/TEM cannot encrypt or decrypt text that has more than 512characters in a single command. TEM Release 5.0: DES index not available. A maximum of 100 session keys are available. They are accessed through an index that ranges between 0 and 99. They must be initialized before use. PEM Release 6.0: Vector not loaded. A maximum of 100memory locations are available. They must be initialized prior to use.TEM Release 5.0: Master or session key out of range. The maximum is 8 characters per key. PEM Release 6.0: Vector out of range. A Vector can have a maximum of eight characters.PEM Release 6.0: DES index out of range. A maximum of 100memory locations are available. They are accessed through an index with values between 0and99.PEM Release 6.0: DES index must be unloaded before any attempt is made to modify it.PEM Release 6.0: Undefined Mode. This mode is not allowed for this function. ModeValue must be either 1 or 2.PEM Release 6.0: Undefined Mode. This mode cannot be used to generate a MAC. ModeValue must be either 1or2.PEM Release 6.0: The module connected on the S-Bus must be an EF4557 or an EF4554.PEM Release 6.0: S-Bus Timeout. A timeout occurs while waiting for a key to be entered from either the EF4557 or the EF4554.PEM Release 6.0: S-Bus Communication Error. The PEM/TEM is unable to correctly communicate with the EF4557 or the EF4554.PEM Release 6.0: Incorrect parameter specification. The parameter string is not correctly specified for:  DESPIN validation  IBM3624PIN validation  PIN translationPEM Release 6.0: Data count out of range. The data count is out of range for:  DESPIN validation  IBM3624PIN validation  PINtranslationPEM Release 6.0: Encrypted PIN does not conform to ANSI standards. The encryptedPIN is not formatted as defined by the ANSIX9.8standards for:  DESPIN validation  IBM3624PIN validation  PINtranslationPEM Release 6.0: Count value must equal 8.PEM Release 6.0: PIN translation format unknown. This format is unknown, or the PIN format does not match the format specified in the input format parameter.TEM Release 5.0: Unknown DES command. An undefined command value has been received. Hex values are: 71=LoadMasterKeyThurXBus 75=StoreSessionKey 77=Encrypt 79=DecryptTEM Release 5.0: Not reserved. Either the TEM Server Module or the DES Server must be reserved before use.TEM Release 5.0: Hardware failure. During installation of either the TEM Server Module or the DES Server, this error indicates that the DES board revision level is unsupported. During normal operations, this error indicates an unrecoverable error was encountered in the key and text memory.TEM Release 5.0: Diagnostic was interrupted before the TEM Server Module or the DES Server was installed. Repeat the DES diagnostic and allow it to terminate normally.TEM Release 5.0: Incorrect priority. During installation, the DES priority parameter was not a number in the range 10 - 253.TEM Release 5.0: Incorrect slot number.TEM Release 5.0: Incorrect parameter list. During installation, two parameters are required.TEM Release 5.0: An attempt was made to install the DES Server on hardware other than the DES board.Resource Access API: Bad pointer passed into procedure.Resource Access API: Unknown handle types specified. In "RsrcInitSetAccess", the user must specify a handle type. Legal values are 4000h for standard file system files and 8000h for CD-ROM files. All other handle types cause this error code to be returned.Resource Access API: Not a run file. In "RsrcInitSetAccess", if the user specifies that file whose handle was passed into the procedure was a run file and the first word in the file is not "GW", then this error is returned.Resource Access API: Not a known run file version. In "RsrcInitSetAccess", if the user specifies that the file whose handle was passed into the procedure was a run file and the version word is not 0004h, 0006h or 0008h this error is returned.Resource Access API: Reserved.Resource Access API: No resources in file. The error means that the file has no resources. If a run file contains no resources and an attempt is made to retrieve or get a count of resources, this error may be returned.Resource Access API: Resource(s) specified not found. The error means that the file does not have the resource or resources specified by the resource type or resource ID passed into the procedure. If a run file contains no resources and an attempt is made to retrieve or get a count of resources, this error may be returned.Resource Access API: Fewer entries in TOC than specified in TOC header. Fewer entries in the run file resource TOC than are specified in the TOC header. The run file may be corrupt.Resource Access API: Resource already exists in the resource set. A resource with an identical resource ID already exists in the resource set. Resource Access API: Size Resource Work Area (RWA) specified too small for whole TOC. The size of the Resource Work Area (RWA) whose pointer was passed into the "RsrcInitSetAccess" procedure was too small to hold the whole TOC. Look in TyFile for the required size.Resource Access API: The Resource TOC was found to have errors. The run file may be corrupt.Resource Access API: An attempt was made to modify a file opened mode read.Resource Access API: An attempt was made to modify a resource set initialized as mode read.Resource Access API: An internal error.Resource Access API: Buffer specified is too sm all to for all data to be returned. If the client application calls "RsrcGetSetTypeInfo" and the amount of data available exceeds the size of the buffer specified, this error is returned.Resource Access API: No file type data was specified. No file type data was specified in the call to "RsrcInitSetAccess"procedure. Valid types are 0002h for a Resource Binary file and 0004h for a run fileResource Access API: One of the two non resource sections is missing. This error occurs when the API is trying to build a run file and one of the two non-resource sections is missing, either the portion of the run file before the resources start or the portion after they end. Probably the client omitted a call to RsrcCopyRestRunfile.Resource Access API: Too many resources, the TOC in memory would exceed 64K.Resource Access API: File not specified as a single resource file.Resource Access API: Not a supported CTOS run file resources format. See the CTOS Programming Utilities Reference Manual: Building Applications for details.ADT: The ADT Installation Utility attempted to delete a nonexistent object.ADT: An invalid procedure name was specified in the Installation Utility.ADT: Internal Error.ADT: Too many windows.ADT: Too many windows.ADT: Too many windows.ADT: Message buffer full. The ADT message buffer is full.ADT: Message buffer full.ADT: Message buffer full.ADT: Protection code out of range.ADT: Too many windows.ADT: Incorrect AdtInt file name.ADT: Incorrect AdtInt file name.ADT: Incorrect NLS message file (AdtMsg.Bin)..ADT: This is not a scroll bar window.ADT: Invalid help file name.ADT: The called procedure is not found in ADT Runtime. You may be using a different version of Adt.Lib.ADT: You attempted to define help for a nonselectable control (such as a static control).ADT: You tried to define a validation routine for a nonedit control.ADT: You tried to define data type for a nonedit control.ADT: You tried to define an edit string for a nonedit control.ADT: You tried to define limits for a nonedit control.ADT: You tried to define limits for a nonnumeric data type edit control.ADT: There is an error in the definition of the maximum length for an edit control.ADT: You tried to Set State of a non-button control.ADT: You tried to Get State for a non-button control.ADT: Adtstoreform received an error while attempting to create the ADT Interface Library file.ADT: There is an error when opening the ADT Interface Library file.ADT: There is an error when storing the control.ADT: There is an error when reading a control from ADT Interface Objects Library file.ADT: You tried to create a control with a Length/Height that exceeds the dimension of its parent.ADT: There is an error in the Length/Height parameter specified for a control.ADT: The Length or Height of a Control cannot be Zero.ADT: Insufficient memory to read the specified object from the ADT Interface Library file.ADT: There is an error when storing a dialog box.ADT: There is an error when reading a dialog box from the ADT Interface Object Library file.ADT: You tried to create a box with a Length/Height exceeding the screen dimensions.ADT: There is an error in the Length/Height parameter specified for a dialog box.ADT: You tried to create a Menu with a Length/Height exceeding the screen dimensions.ADT: You tried to define a Control with a relative Column and Row exceeding the size of its parent (dialog box).ADT: You tried to define a Control with the dimension that out grows its parent (dialog box).ADT: Internal Error.ADT: You tried to store the message more than once.ADT: The message to be recalled cannot be found.ADT: The message to be deleted cannot be found.ADT: Internal Error.ADT: Cannot set Focus to this window.ADT: There is no tabstop control in this dialog box.ADT: This menu bar location is reserved.ADT: Internal Error (cannot create menu).ADT: The "Ib" specified is out of bounds. An ib parameter was out of bounds. ib parameters are indexes into window reserved memory.ADT: You cannot define help for this window.ADT: There is an error in the Picture String syntax.ADT: There is an error when converting a string to a value through a Picture String.ADT: There is an error in the Date Picture String syntax.ADT: There is an error when converting a string to a date through a Date Picture String.ADT: There is an error when converting a value to a string through a Picture String.ADT: There is an error when converting a date to a string through a Date Picture String.ADT: The edit string syntax contains an error.ADT: An error occured while formatting a string using an edit string.ADT: Invalid encode data type.ADT: Invalid decode data type.ADT: There is no such window class.ADT: There is no such window. A reference was made to a nonexistent window.ADT: Invalid SFK location, must be between 0 to 9.ADT: This is not a SFK control. This operation may be performed on SFK controls only.ADT: This is not a menu. This operation may be performed only on menus.ADT: This is not a header control. This operation may be performed on header controls only.ADT: This is not a footer control. This operation may be performed on footer controlS only.ADT: A bad data type specified in the operation.ADT: The Data size specified in the operation is not sufficient for the data type specified.ADT: There is invalid Data specified in the operation.ADT: Incorrect data in an edit field.ADT: Internal Error.ADT: Error File Not Defined. An error file is required for this operation. It is not yet defined. You must define one with ADTDefineErrorFile.ADT: You called an ADT procedure before calling WinInitialize.ADT: A parameter in ADTConfig.Sys is out of range.ADT: There is invalid Data found in ADTConfig.Sys.ADT: An event not available yet.ADT: An error file is required for this operation. It is not defined yet.ADT: There is an invalid menu bar location specified in the operation. Menu bar location must be between 0 and 9.ADT: Invalid button type specified.ADT: ADT structures are full. Increase MaxADTWindows in ADTConfig.Sys.ADT: Internal error.ADT: Internal Error (too many menu items).ADT: This item does not exist in the menu.ADT: This is not a control. This operation may be performed on controls.ADT: This is not a menu. This operation may be performed only on menus.ADT: ADT cannot be deinstalled before it has been installed.ADT: This is not a dialog box. This operation may be performed only on dialog boxes.ADT: Invalid HPS. A procedure attempted to use an invalid presentation space handle (HPS).ADT: This is not a client. Only client windows may be used in this operation.ADT: Cannot create message box (insufficient memory).Cluster File Access: Bad configuration file.Cluster File Access: Volume list is full.Cluster File Access: The User Number table of the Cluster File Access Server Service is full. The CFA Server Service maintains a table of Workstation IDs, and the maximum is 32. This error is returned if 32 Workstations are concurrently doing CFA operations and an operation is issued from a new workstation in the cluster network.Cluster File Access: The User Number table of the Cluster File Access Workstation Agent is full. The CFA Workstation Agent maintains a table of user numbers. (Each user number is an application in the cluster network that can access the local disks). The size of this table is configurable, and the maximum is 256. This error code is returned if the table is full which means a CFA operation from a new user number ( a partition from a workstation ) was tried, but the local table is full.Cluster File Access: The configurable maximum number of applications in the cluster that can access the local disks simultaneously via the CFA Workstation Agent can not exceed 256.Cluster File Access: The AllocUserNumber call failed to allocate the requested user numbers. Even though the maximum number of applications in the cluster that can access the local disks simultaneously via the CFA Workstation Agent (maximum user numbers) is configurable, the CTOS call AllocUserNumber may fail if the operating system is not customized to also support this number of user numbers. Customize the operating system to include more user numbers.Protocol Manager, Data Link Manager: The DLM or Protocol Manager has been installed.Protocol Manager, Data Link Manager: Service is already installed. An attempt was made to install the DLM or Protocol Manager on a workstation where it was already installed.Protocol Manager, Data Link Manager: A parameter is invalid. A specified parameter for the DLM or Protocol Manager installation is invalid (does not have a numeric value as required). Retry with a correct value.Protocol Manager, Data Link Manager: Invalid Max Data-Link Layers value. The value must be in the range 1 to 10. Retry with a correct value.Protocol Manager, Data Link Manager: Invalid Max DLL Users value. The value must be in the range 1 to 15. Retry with a correct value.Protocol Manager, Data Link Manager: DLM or Protocol Manager partition exists. An attempt was made to install the DLM or  Protocol Manager on a system where the partition in which the DLM or Protocol Manager will execute already exists. Remove the DLM or Protocol Manager partition and retry.Protocol Manager, Data Link Manager, BTOS OSI Transport-LAN: Internal error. An application specified the wrong size in a Request pbcb.Protocol Manager, Data Link Manager: An attempt was made by an application to register with the DLM or Protocol Manager when the DLM or Protocol Manager could accept no more DLL users. BTOS OSI Transport-LAN: No more applications can be registered. The maximum number of applications specified in the installation has been reached.Protocol Manager, Data Link Manager: Internal error. An application tried to deinstall the DLM or Protocol Manager with DLLs or DLL Users still registered. BTOS OSI Transport-LAN: The Data Link Manager is still active. Some DLLs or DLLUs are still registered with the DLM or Protocol Manager. DLM or Protocol Manager deinstallation is not allowed.Protocol Manager, Data Link Manager: Internal error. An application tried to use an invalid BNet II node name. BTOS OSI Transport-LAN: The name specified in the request is longer than 12 characters or the braces are mismatched.Protocol Manager, Data Link Manager, BTOS OSI Transport-LAN: Internal error. An application tried to register with the DLM or Protocol Manager using a name already in use (registered).Protocol Manager, Data Link Manager: Internal error. An application tried to use a size for pbcb that is too small. BTOS OSI Transport-LAN: The size of the returned information does not match the value in response pbcb.Protocol Manager, Data Link Manager: An attempt was made by an application to register with the DLM or Protocol Manager and request a DLL using an invalid SD File format. Specifically, the name of the DLL specified in the request is invalid. BTOS OSI Transport-LAN: Wrong Station Descriptor file format. The DLL name must be the first parameter.Protocol Manager, Data Link Manager: Internal error. An attempt was made by an application to update or deregister with the DLM or Protocol Manager using a user number that does not match the one used in the original register request. BTOS OSI Transport-LAN: Invalid user name. The deregister request was not received from the user that registered.Protocol Manager, Data Link Manager, BTOS OSI Transport-LAN: The DLL specified in the SD file(s) has not been installed. The DLL name in the SD file(s) should match the name used in the DLL Name parameter when the DLL was installed.Protocol Manager, Data Link Manager, BTOS OSI Transport-LAN: An attempt was made to deinstall the DLM or Protocol Manager from a different workstation than the one on which it was installed, or the deinstallation was executed under the Context Manager.Protocol Manager, Data Link Manager, BTOS OSI Transport-LAN: An attempt was made to use the deinstallation utility on a workstation with a single partition operating system.Application Automator: Pipe name already set.Application Automator: Duplicate pipe name.Application Automator: Too many pipes. You can have a maximum of 25 pipes.Application Automator: No such pipe name.Application Automator: No such pipe handle.Application Automator: Pipe name not set.Application Automator: No data available.Application Automator: Name is too long. Names for scripts, semaphores, and pipes can have a maximum of 12 characters.Application Automator: Cannot switch context.Application Automator: No open log.Application Automator: No open data file.Application Automator: End of data.Application Automator: Truncated input. The file exceeded the available file space.Application Automator: Semaphore already set.Application Automator: No more semaphores. A maximum of 10 semaphores is allowed at any one time.Application Automator: No such semaphore.Application Automator: Semaphore released.Application Automator: Semaphore in use.Application Automator: No need to wait.Application Automator: Invalid parameter.Application Automator: No such function.Application Automator: Recorded script.Application Automator: Cannot submit script. The script is probably a source script; only object scripts can be submitted for interpretation.Application Automator: Invalid parameter count.Application Automator: Stopwatch is not active.Application Automator: Fatal error.Application Automator: Script already being processed.Application Automator: Function not available.Application Automator: Invalid window handle.Multiple Gateways Service, BMULTI: Multiple Gateways Service (MGS) is not available. You attempted to install BMULTI using a Service ID without first installing the MGS Service.Multiple Gateways Service, BMULTI: Installation failed because a copy of BMULTI was already installed outside of Multiple Gateway Service.BMULTI: Active poll/select address not specified during dynamic reconfiguration.Multiple Gateways Service: The BMULTI Service ID is in an incorrect format. BMULTI: DMA initialization attempted after BMULTI was already successfully installed without DMA.BMULTI: Host connection cannot be established.OSI Session, OSI Transport-WAN, OSI DCA STI: The application refused the connection because of lack of resources. DCA STI: The situation could be due to the following problems:  Maximum number of connections configured at DCA STI installation is too low  Number of send buffers associated with a connection is too low OSI Session: OSI Session is running short of its resources (data buffers, buffer control blocks, request blocks, etc). This is a temporary problem. Try to re-establish connection again. However, if the problem persists, install OSI Session with more resources.OSI Session, OSI Transport-WAN: The primitive contains an invalid parameter. DCA STI: Invalid Parameter. Invalid OSI Primitive code.BTOS OSI Session, OSI Transport-WAN, DCA STI: Invalid BNet File Handle. The B-NET File Handle provided in an OSI request is invalid. The client application should correct the BNet file handle and try the request again.BTOS OSI Session, OSI Transport-WAN, DCA STI: Invalid Connection Handle. The Connection Handle provided in an OSI request is invalid. The client application should correct the session connection handle and try the request again.BTOS OSI Session, OSI Transport-WAN: The structure of user data is invalid. DCA STI: Invalid User Data. Invalid SAP number.BTOS OSI Session, OSI Transport-WAN, DCA STI: Register Cancelled. The application cancelled the register. This code is returned with outstanding requests when the upper layer cancels an access point or when DCA Transport terminates.BTOS OSI Session, OSI Transport-WAN, DCA STI: Connection Cancelled. The connection is cancelled. This code is returned with outstanding requests when the upper layer cancels a connection or when DCA Transport terminates.BTOS OSI Session, OSI Transport-WAN, DCA STI: Invalid Request Block. The request block received has invalid format or content.Document Translator: OFIS Access error. The translation table specified for translation into SITC was the translation table used for translation from SITC.Document Translator: OFIS Access error. The translation table specified for translation into SITC was the translation table used for translation from SITC.Document Translator: OFIS Access error. Could not open the word processor document exchange format (DEF) document.Document Translator: OFIS Access error. Could not open the created SITC document for translation.Document Translator: Installation error. Could not open a required document translation table.Document Translator: System error. Error reading or writing the word processor (DEF) document.Document Translator: System error. Error reading or writing the SITC document.Document Translator: System error. Error reading a required translation table.Document Translator: OFIS Access error. Specified a non-SITC document for a SITC document.Document Translator: OFIS Access error. Specified a file other than a document translation table.Document Translator: Translation table error. Invalid graphic set.Document Translator: Translation table error. Invalid table mode.Document Translator: Document Translator error. Action buffer too small.Document Translator: Document Translator error. State buffer too small.Document Translator: Document Translator error. Backspacing pointer.Document Translator: Document Translator error. File buffer too small.Document Translator: Document Translator error. Referred outside buffer.Document Translator: Document Translator error. Error reading or writing internal trace file.Document Translator: OFIS Access error. Parameters do not match DTR startup parameters.Document Translator: Installation error. The Document Translator run file does not exist.Document Translator: System error. Could not allocate an exchange.Document Translator: System error. Could not load the Document Translator task.Document Translator: OFIS Access error. The output document name must be different from the input doc ument name.Document Translator: OFIS Access error. Buffer length is greater than 1040 characters.Document Translator: Translation table error. Unknown SITC format code.Document Translator: Translation table error. Unknown translation table action.Document Translator: Translation table error. Delay queue size exceeded.Document Translator: Translation table error. DTL buffer arithmetic overflow.Document Translator: Translation table error. Invalid reference to DTL buffer.Document Translator: Translation table error. DTL buffer arithmetic divide by zero.Document Translator: Translation table error. Read passed the end of the document.Document Translator: Translation table error. Unexpected input character.Document Translator: Translation table error. Exceeded the maximum group queue size.Document Translator: Translation table error. Exceeded the maximum of 255 subdocuments.Document Translator: Translation table error. Error reading the subdocument number.Document Translator: Translation table error. A subdocument inside a subdocument is not allowed.Document Translator: Translation table error. The end of the subdocument was not specified.Document Translator: Translation table error. Invalid subdocument mode.Document Translator: Translation table error. The start of the subdocument was not specified.Document Translator: Translation table error. Referred outside of the buffer.Document Translator: Translation table error. Did not specify a text block.Document Translator: Translation table error. Duplicate or invalid subdocument number.Document Translator: Unknown error.Document Translator: Not enough memory. Current memory is too small for DTR session.Uniscope Terminal System: Error calling the UTS AscAddrToRel procedure.Uniscope Terminal System: Error calling the UTS GetBitStatus procedure.Uniscope Terminal System: Error calling the UTS GetExtStatus procedure.Uniscope Terminal System: Error calling the UTS GetRcvdBuf procedure.Uniscope Terminal System: Error calling the UTS GetRelTermAddr procedure.Uniscope Terminal System: Error calling the UTS InitDataComm procedure.Uniscope Terminal System: Error calling the UTS LockAddr procedure.Uniscope Terminal System: Error calling the UTS PgmAttenKey procedure.Uniscope Terminal System: Error calling the UTS PowerUp procedure.Uniscope Terminal System: Error calling the UTS ResetMessageWait procedure.Uniscope Terminal System: Error calling the UTS ResetXmtTrans procedure.Uniscope Terminal System: Error calling the UTS UnLockAddr procedure.Uniscope Terminal System: Error calling the UTS XmtBuffer procedure.Performance Statistics: Session already open. The user tried to open a session that had already been opened.Performance Statistics: Session not open. The user tried to access the Statistics Service with a session that was not Opened.Performance Statistics: Invalid Block information The BlockID supplied by the user while opening the session was invalid. Either:  The size was not a multiple of 8  The index for the block was too large  The size of the data requested (offset + number of bytes) was invalidPerformance Statistics: Too many users. The number of users trying to open a session exceeds the maximum number of users specified when Performance Statistics Service was installed.Performance Statistics: Invalid Log request. A PSReadLog (formerly ReadPSLog) request came to the Statistics Service after the logging information is read fully and returned to the user.Performance Statistics: Too many sessions per user. The number of sessions opened by the user exceeds the maximum number of sessions per user specified when the Performance Statistics Service was installed.Performance Statistics: Too many blocks per session. The number of blocks for which information is requested in a session exceeds the maximum number of blocks per session specified when the Performance Statistics Service was installed.Performance Statistics: Invalid Performance Statistics Work Area. The Performance Statistics Work Area has been corrupted.Performance Statistics: Invalid Session Handle. The Session Handle passed as a parameter is no longer valid.Performance Statistics: No memory available PSWA. There is not enough memory available for Performance Statistics Work Area.Performance Statistics: Wrong BlockID request The session was opened to collect some particular counters but the information to be collected/reset is not for the same counters. BlockID during PSGetCounters/PSResetCounters (formerly GetPSCounter/ResetPSCounters) is invalid. The size of the BlockID during a PSGetCounters and PSResetCounters should be divisible by 4.Performance Statistics: Performance Statistics not implemented on Real Mode OS. Performance Statistics is implemented only on protected mode operating systems.Performance Statistics: Invalid BlockSize. BlockSize given in the request is invalid.Performance Statistics: Invalid Buffersize. The buffer size entered in the request is invalid or wrong.Performance Statistics: No memory available for Open Log. There is not enough memory available in the log heap to open the log session.Performance Statistics: Log request is already pending. There is already a PSReadLog (formerly ReadPSLog) request pending with the Statistics Service.Performance Statistics: No more link available in the PS for log request. No more link block available for linking the piecemeal PSReadLog (formerly ReadPSLog) request.Performance Statistics: Iteration Incomplete. There is not enough buffer to complete all the iterations the user has asked for.Cluster Line Security: Style Id Not Defined. A style Id entry into ClstrIdList.txt is not defined in the translation table IdTransTable.txt.Cluster Line Security: Invalid Entry into Id Registration File. A non-numeric entry was made for hardware Id or memory size in ClstrIdList.txt.Cluster Line Security: Module Id Invalid. A Module Id specified in IdTransTable.txt is invalid in length or value.OSI MHS: Mailbox message too large. A long message was received which was not in a mail message file.OSI MHS: Invalid originator. The Mail User is not registered with the MTA.OSI MHS: Invalid recipient. The Mail User is not registered with the MTA.OSI MHS: LMS Inconsistency. Usually fatal, use PLog to see error.OSI MHS: Too many recipients. You must address the message to a smaller number of recipients.OSI MHS: LMS is busy. Your LMS cannot handle any more Mail Users. After another Mail User signs off, you can access the LMS.OSI MHS: Name not recognized. The Mail User name you entered does not correspond to a valid user at this MTA.OSI MHS: User is already signed on. Someone is signed on to the Mail Center with that Mail User name (at another workstation).OSI MHS: Mail access denied. The correct password was not supplied for a mail operation.OSI MHS: LMS already installed. To reinstall the LMS, reset the system.OSI MHS: LMS cannot load Executive. Invalid exit run file.OSI MHS: LMS bad request code. The LMS received a request for an operation that it does not perform.OSI MHS: The LMS is malfunctioning. Please invoke the PLog command to determine the cause of the error. Use the Executive PLog command 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.OSI MHS: Insufficient privileges. The Mail User name is not registered for administrative privileges.OSI MHS: No such node record. The node name you entered is not registered with your MTA. Display the Node Directory to check Node names.OSI MHS: No such path record. The path name you entered is not registered with your MTA. Display the Path Directory to check Node names.OSI MHS: Too many items being changed. You cannot change any more Mail Users at this time. Try again later.OSI MHS: Mail user already exists. The Mail User name you entered has already been registered at this MTA. Enter a different name.OSI MHS: Node already exists. The node name you entered has already been registered at this MTA. Enter a different name.OSI MHS: Path already exists. The path name you entered has already been registered at this MTA. Enter a different name.OSI MHS: User already removed. An attempt was made to remove a user that does not exist.OSI MHS: User not removed. A problem was encountered in removing the specified user.OSI MHS: Bad information length. A buffer size greater than the maximum amount of data returned was specified.OSI MHS: Invalid privileges. The specified privilege is not standard or administrator.OSI MHS: User locked. The user record is already being used.OSI MHS: Invalid name registry. An internal software error has damaged your LMS Name Registry. Create a new Name Registry by using the Configure LMS command. If necessary, rerun IHI and reregister any corrupted user names.OSI MHS: LMS suspended. Use the Resume LMS command to resume operations.OSI MHS: The LMS is not currently suspended. You cannot use the Re  sume LMS command because the LMS is not suspended.OSI MHS: 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.OSI MHS: No mailbox. The user does not exist.OSI MHS: Invalid mailbox size. The number of allowable mail box entries is zero.OSI MHS: User is signed on to LMS. You cannot remove this user because someone is signed on with this user's name.OSI MHS: Administrator cannot be removed. You cannot remove the primary Mail Administrator. You can change the primary Mail Administrator by editing the LMS.config file and then using the Configure LMS command.OSI MHS: Administrator cannot be renamed. You cannot rename the primary Mail Administrator. You can change the primary Mail Administrator by editing the LMS.config file and then using the Configure LMS command.OSI MHS: Cannot change Administrator's privileges. You cannot change the primary Mail Administrator's privileges. You can change the primary Mail Administrator by editing the LMS.config file and then using the Configure LMS command.OSI MHS: Cannot administer now. You cannot modify the LMS configuration now. Try again later.OSI MHS: Command must be invoked from the server station. You must invoke the command from a server station. You cannot deinstall, suspend, or resume the LMS from a client workstation.OSI MHS: The LMS has been shut down. The system is suspending or deinstalling the LMS.OSI MHS: No free LMS processes. Currently, there are no LMS processes free to handle the incoming BNET connection request from another MHS system.OSI MHS: Recipient name too long. The total length of the name of the recipient exceeds 200 characters.OSI MHS: Circular forwarding or aliasing. The combination of automatic forwarding and aliasing of the specified recipient refers to the original recipient name or exceeds the maximum of five such recipient name changes.OSI MHS: Past end date. The do not deliver after date has expired.OSI MHS: User not registered.OSI MHS: LMS deinstalled. The Local Message Server is deinstalled.OSI MHS: LMS suspended. The Local Message Server is suspended.OSI MHS: LMS resumed. The Local Message Server has been resumed.OSI MHS: Invalid command case. You entered an invalid command case value when you created the command (see your Standard Software or Executive Reference documentation).OSI MHS: Cannot deinstall on a single partition operating system. This is not a multipartition operating system.OSI MHS: Circular forwarding. The sequence of automatic forwardings of the message from its original recipient has led to an unresolvable circular reference.OSI MHS: Missing LMS config file. The [Sys]LMS.config file does not exist.OSI MHS: LMS installed. The LMS is installed.OSI MHS: Bad user record. Could not construct mail box path.OSI MHS: Pre II 1.0 BTOS MHS cannot execute on an operating system older than BTOS version II 1.0.OSI MHS: File too big. The MailCenter.config file is too large.OSI MHS: Delimiter missing. The colon character is missing.OSI MHS: Missing entry. The entry is missing.OSI MHS: Duplicate entry. The entry is a duplicate.OSI MHS: Cnfg type out of range. The specified configuration does not exist.OSI MHS: Not numeric or too big. The number is not numeric or it is too long.OSI MHS: Dir type out of range. Specified type does not exist.OSI MHS: File type out of range. Specified type does not exist.OSI MHS: Folder type out of range. Specified type does not exist.OSI MHS: User type out of range. Specified type does not exist.OSI MHS: Bad keyboard message. There is an unknown message at the keyboard exchange.OSI MHS: No more documents. All 35 document slots are in use.OSI MHS: No more windows. All 12 windows are in use.OSI MHS: Wrong video. The computer video type is not recognized.OSI MHS: Bad formatting operation code. The formatting code is out of range.OSI MHS: Bad Sy. Invalid style ID.OSI MHS: No free Bp. There is not enough memory for allocation.OSI MHS: Software error. A problem was encountered in validating message recipients.OSI MHS: Invalid Tys. Invalid selection (mark and bound).OSI MHS: Invalid doc type. Document type out of range.OSI MHS: Heap full. There is not enough memory for allocation.OSI MHS: Node not busy. A problem was encountered in compacting the heap or freeing a segment of the heap.OSI MHS: Bad signature. Corrupted heap.OSI MHS: Node not free. Heap segment incorrectly marked as free.OSI MHS: Bad tag next. Invalid next used heap segment indicator.OSI MHS: Bad tag prev. Invalid previous used heap segment indicator.OSI MHS: Next node not free. The next free heap segment was incorrectly marked as being free.OSI MHS: Next node bad link. Invalid link to next free heap segment.OSI MHS: Not on free list. The free heap segment is incorrectly marked as being free.OSI MHS: Bad tag. Invalid free/used heap segment indicator.OSI MHS: Bad node size. Incorrect heap segment size.OSI MHS: The message is retained and will be submitted when allowed by conditions or changes in system control parameters.OSI MHS: There is not sufficient memory available to perform the operation. Changing the value of the heap size parameter in the UAE configuration file and restarting OSI Mail may fix this situation.OSI MHS: Relax the MTA control parameters so that deferred messages can be submitted.OSI MHS: The recipient's O/R name is unknown or invalid or there is a registration error of the named ADMD, PRMD, or Organization.OSI MHS: A distribution list contains other distribution lists and the total number of nesting levels are greater than allowed. Four levels are usually allowed.OSI MHS: The message or attachment you are trying to send is too long.OSI MHS: An attachment file title is too long or incorrectly formed.OSI MHS: The OSI Node name you entered is not registered with your Mail Center. Display the Node Directory to check OSI Node names.OSI MHS: There is an OSI MHS system file error. Errors of this type represent OSI MHS logic errors and are not, in general, user correctable. The actual error code is in the log entry.OSI MHS: There is an internal logic error. Retain the error log and submit it with a UCF (User Communication Form).OSI MHS: The MTA rejected the submitted message. There are several possible causes, the most likely of which is that an SSAP is not properly registered. Other possibilities are that the number of message transmission connections available has been exceeded, or that it is an OSI MHS logic error.OSI MHS: There is an error in a call to the naming directory server module of BTOS OSI MHS.OSI MHS: The UAE is unable to encode a submitted IPM message.OSI MHS: There is no ID in the ID Map File. This is probably due to restarting BTOS OSI MHS with a new global prefix, or to deleting the mhs400.id-map file.OSI MHS: There is a bad disk address in the mhs400.deferred file.OSI MHS: Internal error in name directory server.OSI MHS: An invalid encoded type is requested in a P1 message.OSI MHS: The priority value of a message is not one of the allowed values.OSI MHS: A message is too long to send, or the value is negative.OSI MHS: There is an invalid protocol value.OSI MHS: There is no body part in a submitted message.OSI MHS: The content offset of the P1structure used in a UAE ProbeMessage call is not zero.OSI MHS: There is an error in an IPM body part.OSI MHS: A string is too long or null.OSI MHS: There is an invalid PerMsg Flag (for submits).OSI MHS: You attempted to use an X.400 feature not supported in this release of the system.OSI MHS: You addressed too many or too few recipients.OSI MHS: There is no space in the variable part of the message into which the OSI MHS can place a generated identifier.OSI MHS: There is an unexpected null pointer.OSI MHS: This function requires a full P1NameInfo.OSI MHS: There is a malformed DDAL part of a P1NameInfo structure.OSI MHS: There is an error in an IPM body part.OSI MHS: There is a bad IPM name.OSI MHS: The UA Content ID content ID must be null.OSI MHS: There is an invalid IPM ID on submittal.OSI MHS: There is an invalid P1 ID on submittal.OSI MHS: There is an invalid subject on submittal.OSI MHS: Size of attachment file is too long.OSI MHS: The offset value specified is out of bounds of the variable part of the structure. The value exceeds the value in cTotal.OSI MHS: The system has received an error while attempting to delete one of its temporary files.OSI MHS: The system received an internal error from its virtual memory module on a WRITE operation.OSI MHS: The system received an internal error from its virtual memory module on a READ operation.OSI MHS: The system received an internal error from its virtual memory module on a SEEK operation.OSI MHS: Max Timers exceeded. An internal error, indicating that the number of timers provided to the Mail Server have been exhausted. This status code probably represents a failure in the operating system rather than a Mail Server error. It will be printed on   the screen if it occurs during installation of the MHS Mail Server; otherwise, it is available via the Detail display of the Partition Status command.OSI MHS: Timer Not In Use. An internal error, indicating that an internal timer has been referenced which is not in use. This status code probably represents a failure in the operating system rather than a Mail Server error. It will be printed on the screen if it occurs during installation of the MHS Mail Server; otherwise, it is available via the Detail display of the Partition Status command.OSI MHS: Bad Process Id. An internal error, indicating that an error has been made by the Mail Server while trying to set up its internal process structure.OSI MHS: Deallocate Exchange failed. An error was returned to the Mail Server when it made a call to the operating system DeallocExch procedure. This status code probably represents a failure in the operating system rather than a Mail Server error. It will be printed on the screen if it occurs during installation of the MHS Mail Server; otherwise, it is available via the Detail display of the Partition Status command.OSI MHS: GetpStructure failed. An error was returned to the Mail Server when it made a call to the operating system GetpStructure procedure. This status code probably represents a failure in the operating system rather than a Mail Server error. It will be printed on the screen if it occurs during installation of the MHS Mail Server; otherwise, it is available via the Detail display of the Partition Status command.OSI MHS: PCB Process Id Error. An internal error, indicating that the process structure of the Mail Server is corrupted.OSI MHS: Initialization Failed. The initialization procedure found a problem with the supplied configuration files or one of the individual module initialization calls failed. This error is usually accompanied by text on the screen further defining the error. This status code probably represents a failure in the operating system rather than a Mail Server error. It will be printed on the screen if it occurs during installation of the MHS Mail Server; otherwise, it is available via the Detail display of the Partition Status command.OSI MHS: Unable to fork a process. The Mail Server was unable to fork a process due to an operating system problem. This status code probably represents a failure in the operating system rather than a Mail Server error. It will be printed on the screen if it occurs during installation of the MHS Mail Server; otherwise, it is available via the Detail display of the Partition Status command.OSI MHS: Create Process failure. An internal error, indicating that the Mail Server was unable to create one of its internal processes sucessfully.OSI MHS: GetDateTime failed. A call to the operating system procedure GetDateTime returned an error. This status code probably represents a failure in the operating system rather than a Mail Server error. It will be printed on the screen if it occurs during installation of the MHS Mail Server; otherwise, it is available via the Detail display of the Partition Status command.OSI MHS: Wait failed. A call to the operating system Wait procedure failed. This status code probably represents a failure in the operating system rather than a Mail Server error. It will be printed on the screen if it occurs during installation of the MHS Mail Server; otherwise, it is available via the Detail display of the Partition Status command.OSI MHS: Send failed. A call to the operating system Send procedure failed. This status code probably represents a failure in the operating system rather than a Mail Server error. It will be printed on the screen if it occurs during installation of the MHS Mail Server; otherwise, it is available via the Detail display of the Partition Status command.OSI MHS: semget failure. An internal error, indicating that a call to the semaphore allocation procedure returned an unexpected error. This status code probably represents a failure in the operating system rather than a Mail Server error. It will be printed on the screen if it occurs during installation of the MHS Mail Server; otherwise, it is available via the Detail display of the Partition Status command.OSI MHS: semop failure. An internal error, indicating that a call to the semaphore operation procedure returned an unexpected error. This status code probably represents a failure in the operating system rather than a Mail Server error. It will be printed on the screen if it occurs during installation of the MHS Mail Server; otherwise, it is available via the Detail display of the Partition Status command.OSI MHS: semctl failure. An internal error, indicating that a call to the semaphore initialization procedure returned an unexpected error. This status code probably represents a failure in the operating system rather than a Mail Server error. It will be printed on the screen if it occurs during installation of the MHS Mail Server; otherwise, it is available via the Detail display of the Partition Status command.OSI MHS: AllocExch failure. A call to the OS procedure AllocExch returned an error. This status code probably represents a failure in the operating system rather than a Mail Server error. It will be printed on the screen if it occurs during installation of the MHS Mail Server; otherwise, it is available via the Detail display of the Partition Status command.OSI MHS: malloc or calloc failure. The Mail Server was unable to obtain memory. The heap size in the UAE configuration file is probably too small.OSI MHS: RTS failure. An internal logic error has occurred in the RTS (Reliable Transfer Server) or in one of its supporting routines. This status code probably represents a failure in the operating system rather than a Mail Server error. It will be printed on the screen if it occurs during installation of the MHS Mail Server; otherwise, it is available via the Detail display of the Partition Status command.OSI MHS: Lost a file handle. The Mail Server closed a file and was unable to reopen it. This status code probably represents a failure in the operating system rather than a Mail Server error. It will be printed on the screen if it occurs during installation of the MHS Mail Server; otherwise, it is available via the Detail display of the Partition Status command.OSI MHS: Assertion failure. The Mail Server makes consistency checks throughout its code. If one of these fails, a message is logged and the system terminates with this status code. This status code probably represents a failure in the operating system rather than a Mail Server error. It will be printed on the screen if it occurs during installation of the MHS Mail Server; otherwise, it is available via the Detail display of the Partition Status command.OSI MHS: Unable to initialize for Native Language Support. The MHS Mail Server encountered a problem opening the message binary file for NLS. The associated status code is printed along with an explanatory message in English. This status code probably represents a failure in the operating system rather than a Mail Server error. It will be printed on the screen if it occurs during installation of the MHS Mail Server; otherwise, it is available via the Detail display of the Partition Status command.OSI MHS: Invalid argument count to main initialization routine. The installation routine has passed in invalid number of arguments to the Initialization and Configuration Entity ICE. The number of arguments should be three. The actual number is displayed in an associated message.OSI MHS: Unable to open UAE configuration file. The Mail Server Initialization routine was unable to open the configuration file. Its title is printed in an operator display message.OSI MHS: Invalid/Missing :Global Prefix: The UAE configuration file must contain this field. It is either missing or the directory specified is unavailable to the MHS Mail Server.OSI MHS: Confirmation level is not -c1 or -c0. The confirmation level parameter of the Mail Server is optional and defaults to -c1. If you have specified a value for this parameter, it must be given as -c0 or -c1.OSI MHS: :Cache size: incorrect. The :cache size: specified in the configuration file is too large relative to the :Heap size: This status code probably represents a failure in the operating system rather than a Mail Server error. It will be printed on the screen if it occurs during installation of the MHS Mail Server; otherwise, it is available via the Detail display of the Partition Status command.Event Manager: Exceeds limit of clusters configured. The number of client workstations exceeds the configured maximum. Event Manager: Duplicate HwId. Duplicate Hardware Id in the network. Some other workstation in the cluster network is already using this HwId. Event Manager: The Event Manager is already installed. EM has already been installed. Event Manager: Invalid 'Kind' parameter value in the subscription. This status code is for internal Unisys development use only.Event Manager: Invalid Subscription size. This status code is for internal Unisys deve! lopment use only.Event Manager: No message in the Queue. This status code is for internal Unisys development use only.Event Manager: Number of sessions exceeds the configured maximum. Event Manager: Invalid NodeName in the subscription. This status code is for internal Unisys development use only.Event Manager: This NodeName is reserved and cannot be used. This status code is for internal Unisys development use only.Event Manager: Invalid Destination UserName in the SendEventDirectByUserName call. This status code is for internal Unisys development use only.Event Manager: User has been Swapped out of memory. This status code is for internal Unisys development use only.Event Manager: A User with the same PenId has already logged on. This status code is for internal Unisys development use only.Event Manager: No such User exists. This status code is for internal Unisys development use only.Event Manager: Invalid Event Session Handle. One such session is open. This status code is for internal Unisys development use only.Event Manager: Invalid number of subscriptions. The number of subscriptions specified in the configuration file is invalid. Event Manager: Invalid Workstation Id. This status code is for internal Unisys development use only.Event Manager: This Request is already pending. This status code is for internal Unisys development use only.Event Manager: The size of the message field provided is smaller than the size of the message returned. The message returned has been truncated.  This status code is for internal Unisys development use only.Event Manager: A similar Subscription already exists. This status code is for internal Unisys development use only.Event Manager: No such subscription exists. No session in the cluster network has subscribed for this event. Event Manager: This subscription is invalid. This status code is for internal Unisys development use only.Event Manager: The Server EM is not running. Server EM has either terminated abnormally or is no longer in communication with this workstation. Event Manager: The Server EM is not installed. The Event Manager on the server workstation has not been installed. Event Manager: No such Destination. This status code is for internal Unisys development use only.Event Manager: Invalid BoxId. The BoxId parameter provided in this command line parameter is not valid. Event Manager: This Lasting User does not exist. This status code is for internal Unisys development use only.Event Manager: Cannot deinstall EM. The Event Manager cannot be deinstalled at this time. Event Manager: Invalid Return Point value set in the SendEvent request. Event Manager: Invalid pointer. Event Manager: Invalid message size. Event Manager: Invalid destination BoxId. This status code is for internal Unisys development use only.Event Manager: This session has been terminated. Event Manager: User Number and Event handle do not match. This status code is for internal Unisys development use only.Event Manager: Cluster EM has been installed. Event Manager: There are still some active sessions open. Event Manager: Cannot install Server EM on Client workstation. Event Manager: Cannot install Cluster EM on Server workstation. Event Manager: GenNum file required. The Generation Number File ([!sys]GenNum.sys) is absent. Event Manager: Cannot Allocate HyperSegment. Memory problems. This status code is for internal Unisys development use only.Event Manager: Invalid 'Case' parameter value in the Init/Set Gen Number command. This status code is for internal Unisys development use only.Event Manager: Invalid Generation Number. Event Manager: Zero Result in Gen Num Math. This status code is for internal Unisys development use only.Event Manager: Negative Result in Gen Num Math. This status code is for internal Unisys development use only.Event Manager: Invalid maximum Superfile size. The maximum SuperFile size specified in the configuration file is invalid. Event Manager: Invalid initial Superfile size. The initial SuperFile size specified in the configuration file is invalid. Event Manager: Invalid number of Client workstations. The number of Client workstations specified in the configuration file is invalid. Event Manager: Invalid Superfile ExtensionSize. The Superfile extension size specified in the configuration file is invalid. Event Manager: Invalid Queue Limit Per User. The Queue Limit Per User specified in the configuration file is invalid. Event Manager: Invalid number of users. The number of users specified in the configuration file is invalid. Event Manager: The number of pending Query requests has exceeded 64. This status code is for internal Unisys development use only.Event Manager: There are no subscriptions made for this PenId. This status code is for internal Unisys development use only.Event Manager: Event Manager configuration file required. The configuration file ([!sys]EMConfig.sys) is absent. Event Manager: The Start record number specified in the Query request is invalid. This status code is for internal Unisys development use only.Event Manager: Invalid parameter range in the Subscription. This status code is for internal Unisys development use only.Event Manager: There are no users signed on to the Event Management System presently. This status code is for internal Unisys development use only.Event Manager: The size of the buffer provided for the Query response is insufficient. This status code is for internal Unisys development use only.Event Manager: The AcceptEvent Descriptor size specified is smaller than the size of the description. The data returned has been truncated. This status code is for internal Unisys development use only.Event Manager: Invalid origin BoxId. Event Manager: Event Manager: Invalid Node Name specified. The Node Name specified in the event message is invalid. Event Manager: The user has exceeded the maximum number of messages to be queued for him (as specified in the configuration file or set by the SetEvQueueLimit call). This status code is for internal Unisys development use only.Event Manager: The Superfile is full and has exceeded the maximum configured size.Event Manager: There are no more messages queued for this user. This status code is for internal Unisys development use only.Event Manager: There are too many Query Requests.Event Manager: The destination ID is not valid. This status code is for internal Unisys development use only.Event Manager: Invalid Origin Id. This status code is for internal Unisys development use only.Event Manager: Too Many Accept Requests pending. This status code is for internal Unisys development use only.Event Manager: Too Many Credit Requests pending. This status code is for internal Unisys development use only.Event Manager: Invalid Request Code. Event Manager: Too Many Requests. EM can only handle 64 simultaneous requests. Please retry. Event Manager: Cannot call SendEvent from a Remote workstation without installing Cluster EM. Event Manager: No more Subscription Entries. This status code is for internal Unisys development use only.Event Manager: The event session has disk I/O problems. For example, the disk is full or the session's Event Queue Limit has been exceeded. Event Manager: Events for this recipient have been discarded due to problems described in erc 57824. The accept descriptor structure of the event message returned has further information about the discarded events. This status code is for internal Unisys development use only.Event Manager: EM is in the process of deinstalling and no further requests can be processed now. Event Manager: The Mode parameter value in the AcceptEvent call is invalid. This status code is for internal Unisys development use only.Event Manager: This session has been taken over and this user is no longer recognized. This status code is for internal Unisys development use only.Network Software Link Layer: Duplicate invalid DLL name specified. A duplicate of an invalid DLL name was specified. ISDN Service: LAPD link layer name was not matched in the client request. LAPD returns this code if the given link layer name provided in an OpenStation or DirectLink request does not match the LAPD Service Name provided in the LAPD configuration file. Check the SD string values provided by the client. Make sure the service name provided there matches the service name provided in the LAPD configuration file.Network Software Link Layer: CM Swapping condition response.Network Software Link Layer: The specified SDF File is either invalid or nonexistent.Network Software Link Layer: The passed SD string is invalid. ISDN Service: The passed SD string is invalid. LAPD returns this code if the format of the Station Description string passed to LAPD in the OpenStationLL or OpenStationSL request is in the wrong format. This usually occurs if the last parameter of the string is not terminated by a new line character or if a parameter value is too long. Check the format of your SD string parameters provided by the client. Be sure to follow the guidelines provided in t! he CTOS ISDN Service Administration Guide.Network Software Link Layer: The SDF string not valid for the DLL. The information in the SDF string is not valid for the DLL. ISDN Service: The information in the SD string is not valid for this Link Layer. LAPD returns this code if any of the parameters of the Station Description string passed to LAPD in the OpenStationLL or OpenStationSL request contains an invalid value. Check the SD string parameter values provided in the client's SDF. Be sure to follow the guidelines provided in the CTOS ISDN Service Administration Guide.Network Software Link Layer: Full duplex is not an available option.Network Software Link Layer: Buffer passed to DLL too small. The buffer passed to the DLL is too small. ISDN Service: The DirectLink or DirectStation return buffer passed to LAPD by the client is too small to use. LAPD returns this code if the user specified a buffer that was too small to hold the data to be returned. This usually happens in the DirectStation or DirectLink response if the pReceive/cReceive pair point to an area that is too small for the requested information. A modification of the client software is required to resolve the problem. Ethernet DLL: Buffer too small. Mnemonic: ErcBufferTooSmall The buffer passed to the Link Layer is too small to use. The client software called one of the following requests: - ReadDLFrame - DirectStation with bCommand set to QueryStation - DirectLink with one of these bCommands: QueryLink Layer Statistics Individual Address SetupNetwork Software Link Layer: Fatal error in data link. Use the PLog command to determine the error. Deinstall the Transport Service and the data link using the appropriate data link deinstall command. Then reinstall all the transport software. ISDN Service: A fatal error occurred in LAPD, and the software deinstalled. LAPD returns this code when a fatal error occurs in LAPD. Use the PLog command to check the error code. This error indicates that LAPD is non-functional and needs to be reinstalled.Network Software Link Layer: The DLL user name passed into the request is invalid.Network Software Link Layer: An invalid parameter value was specified during installation or deinstallation. Ethernet DLL: Invalid parameter. Invalid parameter value specified during installation or deinstallation. Check the command form and try again.Network Software Link Layer: The size of the data passed to the DLL is incorrect. ISDN Service: The WriteDLFrame sFrame and sFrameTotal fields passed to LAPD by the client are inconsistent. The size of the data passed to the Link Layer is incorrect. LAPD returns this code in a WriteDLFrame response if there is an inconsistency between sFrame and sFrameTotal values. A modification of the client software is required to resolve the problem. Ethernet DLL: Bad data size. Mnemonic: ErcBadDataSize The size of the data passed to the link layer is incorrect. The client software called one of the following requests: - WriteDLFrame - DirectLink with one of these bCommands: Add Multicast Address Remove Multicast Address Individual Address Setup Configure CommandNetwork Software Link Layer: A message was received with a broadcast or multicast address.Network Software Link Layer: A call establishment problem was encountered. QLLC and PSH-LLC DLLs report this error when they detect that the VC is out of order. Use the X.25 status monitor for a more detailed description of the error.Network Software Link Layer: The Mac LSAP installation parameter is out of range. The value of the Mac LSAP installation parameter is out of range. Network Software Link Layer: DLL in busy state. The DLL is in a busy state. Internal error. Network Software Link Layer: The read/write requests queued up are returned with this error after the link has received a CloseStation request. ISDN Service: LAPD received a request from the client or the operating system to close the station. LAPD returns this code if LAPD receives a CloseStation, Abort, or Terminate request while it is holding on to other requests for the client. When LAPD receives one of these requests it returns all outstanding requests for the LSAP/User with this code. This code indicates normal LAPD operations. No recovery action is required.Network Software Link Layer: This error is returned by the link if it receives a request when it is in an invalid state. ISDN Service: This status code is returned by LAPD if it receives a request when it is in an invalid state. LAPD returns this code to indicate that the requested WriteDLFrame or DirectStation operation could not be performed because the client was in a state inconsistent with the request. A modification of the client software is required to resolve the problem.Network Software Link Layer: The TMS Adapter was unable to transmit the message because there were too many TMS commands outstanding at the time. ISDN Service: LAPD returns this code in a ReadDLFrame request if the data returned is only part of what was received in the frame. The remaining data will be returned on subsequent ReadDLFrame requests. This code indicates normal LAPD operations. No recovery action is required.SNA Transport: The transmit command has completed but the transmission failed for some reason.SNA Transport: The TMS Adapter was unable to execute the current command. Ethernet DLL: Command failed Mnemonic: ErcTooManyConnections Execution of the request failed.SNA Transport: The total number of connections exceeds the value given at the time of installation. Ethernet DLL: Too many connections. The data connection request exceeded the installation parameter value.SNA Transport: Connected links existed when a CloseStation was attempted. A Close Data Link command must be issued to deactivate existing connections prior to attempting to close a station. Ethernet DLL: Active Link There is an active Logical Link associated with the LSAP.SNA Transport: An invalid Remote LSAP specification. LSAP and frame types are incompatible. ISDN Service: LAPD returns this code if it receives a Write request with an invalid remote LSAP specification. A modification of the client software is required to resolve the problem.SNA Transport: There are not enough buffers in the Token-Ring module.SNA Transport: There are not enough buffers in the TMS Adapter RAM. Increase the values specified in the "Total Number of Buffers" and "Minimum Number of Transmit Buffers" installation parameters.SNA Transport: There is no more UCB to assign to LSAPh or DLCh.SNA Transport: The total number of LSAPs exceeds the value given at the time of installation. Increase the number of LSAPs specified in the "Max Number of Connections" installation parameter.Local Event Management: Event Transmitter: Warning - inconsistent directive received from Event Command and Control Utility (ECCU). The command directive is syntactically correct and so ECCU passed it on. However, it contains information that does not make sense, for example, referring to a nonexistent event session.Local Event Management: Event Command and Control Utility (ECCU): Directive syntax error. The command directive was syntactically incorrect and so ECCU did not pass it on to Event Transmitter.DCA Transport: Bad Request Layout. Invalid request structure. The request probably had a bad field in it.DCA Transport: Bad Read Event Resp Size. The ReadEvent response size in the read request (event area) is too small.DCA Transport: Bad Include File Version. DCA internal inconsistency.DCA Transport: Bad Size Upper Event. Event area in request is too small.DCA Transport: Bad Upper Event. Event block in request contained undefined values.DCA Transport: Bad Access Point. The request referenced an invalid Access Point. For DCA IPC, the access point associated with an IPCWrite, IPCRead, or IPCTerminateAccessPoint request is not recognized. Use the correct access point.DCA Transport: Bad User Id. The User Data field contains an invalid End User ID.DCA Transport: Bad Event State. The event code is invalid for the current state.DCA Transport: Bad Access Point Size. Invalid size of area in which to return the Access Point reference number.DCA Transport: Already Installed. DCA layer already installed on this workstation.DCA Transport: Exception Reply Pending. The command cannot be processed as an exception reply is pending. Issue an IPCRead to read the exception reply.DCA Transport: User Still Reading. An event or data is outstanding. Issue an IPCRead to process the event or data.DCA Transport: Prot State Violation.  The command is invalid for the current state of the conversation.DCA Transport: Greater Than 2K. User data associated with an IPCWrite request is greater than 2K. Send the data in more than one IPCWrite request.DCA Transport: NumConvPerApp exceeded. Too many conversions are open. Reissue the IPCOpen when the number of conversations is less than the number configured in the NumConvPerApp parameter of the IPC statement.DCA Transport: IPC ErrOpen Rejected. The secondary rejected the Open command.D" CA Transport: IPC ErrClose Rejected. The secondary rejected the Close command.DCA Transport: Max Conversations Active. The limit for maximum number of conversations per access point has been reached.DCA Transport: Timeout Expired. The timeout associated with an IPCWrite request has expired. The effected conversation has been aborted. If the network is operational, extend the timeout. If the timeout is with an IPCOpen, it could mean that the target application is not available.DCA Transport: Connection Aborted. The connection has been unexpectedly aborted. This error can be reported in any request, even in OpenSession requests. Possible causes:  The user issued an abort request, which causes all outstanding requests to be returned with this error code.  The remote entity has issued an abort request (the protocol generates a disconnect indication), which causes all outstanding requests to be returned with this error code.  The user has issued a bad request (responded to with a request interface error code), causing all outstanding requests to be returned with this code.  The lower layer has failed in some way (normally causing the protocol to generate a disconnect indication), which causes all outstanding requests to be returned with this error code.  Peer protocol failure (normally causing the protocol to generate a disconnect indication), which causes all outstanding requests to be returned with this error code.  Local critical out-of-resources condition at the time when the normal abort/disconnect was meant to be reported.DCA Transport: Terminating AP. This code is returned in all outstanding ReadEvents when a user issues a Terminate Access Point request (or the user aborts).DCA Transport: Reset Flush. Request flushed due to receipt of reset or restart. Data may be lost.DCA Transport: AU Failure. Returned to a WriteRequest using the Assurance Data Unit feature of the DTPx and INT-1 protocol layers.DCA Transport: Read Timeout. Returned to a ReadEvent when the specified timeout period expires. For DCA IPC, the IPCRead timeout expired. Reissue IPCRead with longer timeout.DCA Transport: Out of resources. There is not enough system resources to open a connection. This is a temporary condition. Try the operation later.DCA Transport: Bad connection configuration. The alias specified in a connection request is invalid or some other configuration information is invalid. Check the configuration file for errors.DCA Transport: Network down. The network is not operational.DCA Transport: Quality of service reject. The remote system rejected the transport layer connection connection because the requested quality of service could not be provided.DCA Transport: Remote reject. The remote system rejected the connection for reasons other than unavailability of quality of service.DCA Transport: Remote timeout. The remote system did not respond in time.DCA Transport: Remote error. The remote system failed in some protocol layer.DCA Transport: Local error. The local system failed in some protocol layer.DCA Transport: ErcLogIO ErcLogLevelError The attempt to open, close, or rename the Logfile has failed. For DCA IPC, an invalid log level has been specified in the configuration file. Specify a valid value (0, 1, or 2).DCA Transport: In Progress. The request cannot be processed because a deinstall is in progress.DCA Transport: No Reads. The Manager has no outstanding Read from the specified protocol layer. Try again later.DCA Transport: Full. The ConfigUtil request buffer is full. For DCA IPC, the User application tried to issue an IPCWrite while the application is still reading data.DCA Transport: Bad Log Level. An invalid log level was specified in the installation file. For DCA IPC, the user application tried to issue an IPCWrite while the application is still reading data from below.DCA Transport: Invalid Request. A request has been made with an invalid request code.DCA Transport: Bad Request Content. A request has been made containing invalid data in the request block.DCA Transport: Invalid Control. A request has been made specifying an invalid Control Type in the request block.DCA Transport: Buffer Too Small. The MgrReadControl buffer is too small.DCA Transport: Truncated. The log entry has been truncated.DCA Transport: Invalid Command. A request has been made containing an invalid command in the request block.DCA Transport: Bad Level Spec. A request has been made incorrectly specifying a Protocol Level.DCA Transport: No Access Point. There are no free Access Points available.DCA Transport: Terminating. The request has been flushed, because the Manager is terminating.DCA Transport: Aborted. The request has been flushed, due to a user abort request.DCA Transport: Bad Control Type. A request has been made containing a bad Control Type in the request block.DCA Transport: Bad Sub-Control Type. A request has been made containing a bad Sub-Control Type in the request block.DCA Transport: Bad Config Type. A request has been made containing a bad Config Type in the request block.DCA Transport: Bad Command Type. A request has been made containing a bad Command Type in the request block.DCA Transport: Bad Protocol Type. A request has been made containing a bad Protocol Type in the request block.DCA Transport: Bad Protocol Type. A request has been made containing a bad Protocol Type in the request block.DCA Transport: Bad Statistics Type. A request has been made containing a bad Statistics Type in the request block.DCA Transport: No Such Protocol Reference Number. A request has been made referring to a non-existent Protocol Reference Number.DCA Transport: Name In Use. The Get Access Point request from the Protocol Layer has used an Access Point name that is already in use.DCA Transport: Name Too Long. The Get Access Point request from the Protocol Layer has used an Access Point name that is too long.DCA Transport: Bad Conversation Id. The ConvId associated with an IPCWrite request does not refer to an open conversation. Correct the bug in the application program.DCA Transport: Alias Unknown. The alias specified in the IPCOpen request cannot be retrieved from the configuration file. Correct alias name in IPCOpen request or add the corresponding IPC alias definition to the configuration file.DCA Transport: Can't Change Config File. A SET request to change the configuration file cannot be executed.DCA Transport: Log Not Open. Writing to the Log File has failed because the Log File has not been opened.DCA Transport: Log Write Error. There is an error in writing to the Log File.Undelete: The specified file cannot be recovered. The sectors occupied by the specified file are now occupied by another file. Undelete: The file header is corrupted or does not exist any more. The specified file cannot be recovered. If you submit multiple files to Undelete and one of the files cannot be be recovered, the recovery stops with the bad file. Repeat the Undelete command for the remaining files.Undelete: The filename entered has an invalid specification. Check that you are using the correct volume and directory address, and that the file name is spelled correctly.Undelete: Too many files requested to be undeleted. Undelete can recover up to 10 files at a time. Try recovering fewer files.X.21 CSS: Configuration file not found. The configuration file displayed along with this message does not exist. It was specified on the [Parameter 2] line of the ImRun command (if you did not enter a value here, the program looked for the default configuration file, [Sys]X21CSS.Config). Most likely, you misspelled the file name. Try installing the X.21 CSS again, using the complete file specification, [VolumeName]FileName. If you get the message a second time, make sure your configuration file still exists.X.21 CSS: Invalid Configuration Parameter. The configuration file parameter, displayed along with this message, is invalid. Then update the configuration file and try installing the X.21 CSS again.X.21 CSS: X.21 CSS Already installed. You tried to install a copy of the X.21 CSS that already exists (using identical Service IDs, if specified). If you want multiple copies of the X.21 CSS, install the X.21 CSS using a different Service ID. If you want to replace your X.21 CSS, deinstall it first by rebooting the IDS.X.21 CSS: MGS Not Installed. You specified a Service ID (either on the [Parameter1] line of the ImRun command, or in the JCL file) when installing the X.21 CSS. Multiple Gateway Server must be installed when you use the Service ID to identify multiple copies of the X.21 CSS on the same Intelligent Datacomm Module (IDS). If you are installing a single copy of the X.21 CSS on the IDS, do not enter a Service ID. If you are installing multiple copies of the X.21 CSS on the same IDS, first install MGS, then try to install the X.21 CSS again.X.21 CSS: Invalid Service ID. You either forgot to supply a Service ID or supplied an invalid one. Most likely you misspelled the Service ID. If you are using the ImRun comman" d to install the X.21 CSS, enter the Service ID on the [Parameter 1] line. The Service ID must be 12 characters or less, and enclosed in angle brackets, < >. If you are using the Status Monitor X.21 CSS command in a BNET environment, enter the Service ID immediately after the node name on the [Routing Info] line. If you are using this command in a non BNET environment, enter only the Service ID on the [Routing Info] line. Again, the Service ID must be 12 characters or less, and enclosed in angle brackets, < >.Batch Manager: The Batch Manager is installed. The Batch Supervisor returns this status code if the Queue Manager is deinstalled while Batch Manager is running.BTOS OSI Transport-LAN: Invalid Hardware Type. The XE LAN Relay cannot be installed on this type of hardware. XE LAN Relay can only be installed on B26, B28, B38, and B39 workstations, and on an shared resource processor.BTOS OSI Transport-LAN: STI Active Internal Error. The XE LAN Relay cannot be deinstalled because the Session-to-Transport Interface is still active.BTOS OSI Transport-LAN: Not Correct User. The XE LAN Relay cannot be deinstalled because the deinstallation request was issued from a workstation other than the one where it was installed.BTOS OSI Transport-LAN: No LAN Module. There is no LAN module available for the XE LAN Relay on this cluster. Add a B25-EN3 module to the workstation where the XE LAN Relay is to be installed.BTOS OSI Transport-LAN: No STI. The Session-to-Interface software is not present on the shared resource processor. Install BTOS OSI Transport-LAN again on the shared resource processor.BTOS OSI Transport-LAN: No BOTL. The BTOS OSI Transport-LAN software was not present on the workstation.BTOS OSI Transport-LAN: No XLRs. The XE LAN Relay software has not been installed on the shared resource processor.BTOS OSI Transport-LAN: No B25XLRS. The XE LAN Relay software has not been installed on the workstation, or has been deinstalled.TCP/IP: Unable to deinstall in single partition operating system.TCP/IP: Send buffer too large.TCP/IP: Receive message truncated.TCP/IP: No resources for request.TCP/IP: No connection available.TCP/IP: No such host name.TCP/IP: No such host address.TCP/IP: Invalid socket for open.TCP/IP: Connection refused by remote host.TCP/IP: No such connection handle.TCP/IP: Connection aborted by remote host.TCP/IP: Bad security range.TCP/IP: Program failed an internal check. Contact your Unisys field representative.TCP/IP: Security request not allowed.TCP/IP: Connection already exists.TELNET: Transport Service is not running.TELNET: SAM TELNET configuration file not available.TELNET: Help file not available.TELNET: Received message of invalid size.TELNET: System configuration file not available.TELNET: Options already in effect.TELNET: Received invalid TELNET command.TELNET: Received invalid option negotiation.TELNET: Subnegotiation too long.TELNET: Subnegotiation too short.TELNET: Invalid Subnegotation.TELNET: No connection.TELNET: Open failure.TELNET: Close failure.TELNET: Abort failure.SNA PDF: Too few parameters.SNA PDF: Too many parameters.SNA PDF: Command not specified.SNA PDF: Command not recognized.SNA PDF: Not allowed in file.SNA PDF: Data not allowed.SNA PDF: Invalid parameter name.SNA PDF: Parameter specified more than once.SNA PDF: Data required for parameters.SNA PDF: High value less than low value.SNA PDF: Too much data.SNA PDF: Null value not allowed.SNA PDF: Invalid remote deinstall command.SNA PDF: Insufficient memory.SNA PDF: Numeric value out of range.SNA PDF: Invalid numeric value.SNA PDF: Invalid event session name.SNA PDF: Invalid time format.SNA PDF: File not found.SNA PDF: Unrecognized keyword.SNA PDF: Parameter list not allowed.SNA PDF: Expected diagnostics not found.SNA PDF: Waiting to be deinstalled.SNA PDF: BET already installed.SNA PDF: SNA Gateway is not installed.SNA PDF: SNA Gateway is installed but cannot establish a session.SNA PDF: Event Management System not installed.SNA PDF: EMS is installed but cannot establish a session.SNA PDF: BNet is not running.SNA PDF: BET malfunction occurred.SNA PDF: Route specified cannot be established.SNA PDF: Maximum number of sessions exceeded.SNA PDF: Session already exists.SNA PDF: Insufficient space for partition handle.SNA PDF: Connection does not exist.SNA PDF: No free memory.SNA PDF: Still processing last command.SNA PDF: Invalid connection name.SNA PDF: Internal error.SNA PDF: Invalid Routing Information.SNA PDF: Insufficient space for partition.SNA PDF: Error detected by BET.SNA PDF: Error detected by BERC.SNA PDF: Error detected by SNA PDF.SWD: The Mail User Name was missing in the SWD.user file. The keyword :MailUserName: or its entry was not found and needs to be added. This was detected at the destination station and needs to be corrected by the network administrator using RAF.SWD: The Mail Center Name was missing in the SWD.user file. The keyword :MailCenterName: or its entry was not found and needs to be added. This was detected at the destination station and needs to be corrected by the network administrator using RAF.SWD: SWD was unable to obtain enough short-term memory from the operating system. You can do one or more of the following:  Add more memory boards to the destination workstation.  Reduce the number of programs loaded into memory on the destination workstation.SWD: SWD was unable to create the Holding Directory. The cause of this error is hard to identify. Administrators should use RAF to attempt to create the Holding Directory, directly on the destination workstation. SWD uses the directory name identified by the keyword :SWDDirectory: and its entry.SWD: SWD was unable to establish a mail connection. The cause of this error is hard to identify. Administrators should use OFIS Mail to determine that the desired SWD mail user file is configured correctly and is valid. SWD uses the keywords :SWDMailCenterName: and :SWDMailUserName: and their entries to identify the mail center and user it uses for OFIS Mail communications.SWD: A reboot at the destination station terminated the installation. The destination station crashed or was turned off/on, reset, unplugged, or disconnected from the cluster during the SWD installation. In this case, the returned log file should reflect how far the installation had progressed before it ceased. Correct the Install.jcl file, if necessary. Verify that the destination station is ready to receive the installation and retry.SWD: The From: string in the mail message was invalid. There was a mail system failure, or the message received at the destination station was from an unauthorized source.SWD: The Subject: string in the mail message was invalid. SWD requires the subject name to be "SWD Install" for incoming installation messages.SWD: No installation date was included in the mail message. If no installation date is present, a message will be sent to the originator saying "Software was received without Date/Time. The files have been stored in the SWD directory but are not queued for SWD installation." Note: These files may take up valuable disk space.SWD: The message was delivered after the desired installation Date/Time. If the Date/Time of arrival of the message is later than the desired installation Date/Time, (and Immediate was not given as the desired Date/Time), a message will be sent to the originator saying "Software was received after the desired installation Date/Time. The files have been copied to the SWD directory and queued for installation."SWD: The desired installation date was greater than 90 days in the future. If the Date/Time is more than 90 days from the time that the SWD package was received, a message will be sent to the originator saying "The desired Date/Time of installation is greater than 90 days in the future. The files have been copied to the SWD directory and have been queued for installation."SWD: The SWD package name was missing in the mail message.SWD: The version number of the software to be installed was missing in the mail message.SWD: The number of attachments stated in the message format did not agree with the actual number of attachments in the message.SWD: There was no SWD network administrator named in the SWD.user file. The keyword :SWDAdministrator: or its entry was not found and needs to be added. This was detected at the destination station and needs to be corrected by the network administrator using RAF.SWD: There was no Interface Task in the SWD.user file. The keyword :SWDTaskName: or its entry was not found and needs to be added. This was detected at the destination station and needs to be corrected by the network administrator using RAF.SWD: The Install.jcl script failed in the middle of the installation process and has been timed-out. In this case, the returned log file should reflect how far the installation had progressed before it ceased. Correct the Install.jcl file.SWD: SWD could not open the Interface Task file. In this case, the SWD interface program run file entry is present but cannot be accessed. Check # the SWD.user file and correct the entry for the :SWDTaskName: keyword. Make sure that the file exists, and that it can be accessed by SWD.SWD: SWD could not load the Interface Task file. In this case, the Interface Task was present and the parameter entry was correct but the .run file was corrupt. Reinstall a correct .run file.SWD: There was no Queue Name provided in the SWD.user file. The keyword :SWDDQName: or its entry was not found and needs to be added. This was detected at the destination station and needs to be corrected by the network administrator using RAF.SWD: The SWDservice received an unload request. A person working at the destination station has unloaded SWD. Review the installation log file, and determine how much of the installation was completed. SWD must be reloaded at the destination station and the installation retransmitted if the installation did not finish.SWD: On a delete queue entry request, a matching queue entry was not found and could not be deleted. This could be a user input error. Retry the request.SWD: On a delete queue entry request, the queue entry was already in progress and could not be deleted.SWD: On a delete queue entry request, the specific queue entry was already deleted.SWD could not open the SWD.user file. Using RAF, check this file and make sure that it exists and can be accessed.SWD: The date given was invalid. This could apply to any date given in the OFIS Mail SWD message. Review the mail message and note the use of any dates. Insure the dates are in standard BTOS format.BNetII: Processing error. This error message has three meanings:  The Naming Service is not yet loaded  The Naming Service has already received a fatal error, and is waiting to be unloaded  The request given to the Naming Service has an unrecognized request code BNetII: Needs more memory. There is not enough memory present for the table size options that were selected.BNetII: Problem setting MC address. Naming Service cannot initialize its own multicast address on the LAN.BNetII: Problem resetting MC address. Naming service cannot remove its own multicast address from the LAN.BNetII: Problem sending datagram. Naming Service encountered an unspecified problem sending a datagram.BNetII: Problem receiving datagram. Naming Service encountered an unspecified problem receiving a datagram.BNetII: Problem withdrawing datagram. Naming Service encountered an unspecified problem withdrawing the receipt of a datagram.BNetII: Abort flag has been set. Naming Service cannot service the request because it has already begun its own abort sequence due to a previous error.BNetII: Problem reading disk. The file(s) [Sys]BNetAddres.cfg and [Sys]CCU.cfg, which have been previously accessed by the Naming Service, can no longer be read from the disk.BNetII: Problem writing disk. The file(s) [Sys]BNetAddres.cfg and [Sys]CCU.cfg, which have been previously accessed by the Naming Service, can no longer be written to the disk.BNetII: Problem with un/lock request. The Naming Service has a problem with the (un)locking request for [Sys]BNetAddres.cfg or [Sys]CCU.cfg or both.BNetII: Problem with delete request. The entry number and the type of deletion do not match the referenced entry in the Naming Service table(s).BNetII: Problem with deinstall request. The Naming Service cannot unload at this time because [Sys]BNetAddres.cfg or [Sys]CCU.cfg or both are locked. BNetII: Problem with list request. The entry numbers and types, specified in the list request, conflict with the actual table entries in the Naming Service.BNetII: Duplicate node name detected. On startup the Naming Service has detected another LAN node with the same node name as specified for this node. The BNetII node name must be unique, and may not be duplicated on your network.BNetII: Run parameter too large. The table size options that were selected are larger than can be supported by the Naming Service.BNetII: Problem with Addmod request. The types specified were too long or too short, or the datatypes did not match the actual table entries in the Naming Service.BNetII: List request too short. Not enough buffer space provided with the List Request to accommodate the requested entry data from the Naming Service.BNetII: BNet addrs.cfg file missing. This file is required by the Naming Service.BNetII: Ccu.cfg file missing or not created. This file is required by the Naming Service. It is presently missing and cannot be created by the Naming Service.IS-BTOS: Purge. Returned by the Service to all requests from a terminating application. All requests from this application are responded to with this error code before the Service reponds to the Term/Abort request.IS-BTOS: ErcDeInstallMe. The IS-BTOS Service has encountered a fatal error and should be deinstalled immediately. The System log file contains information about the error encountered by the IS-BTOS Service.IS-BTOS: Single Partition. The IS-BTOS Service was not deinstalled because it was on a single-parition operating system.IS-BTOS: Multiple Installs. An attempt was made to install the IS-BTOS Service more than once on the same workstation.IS-BTOS: ErcI'mOutaHere. The IS-BTOS Service has received a deinstall request and is in the process of shutting down.IS-BTOS: DeInstall Initiated. Returned in response to a deinstallation request to indicate that the IS-BTOS Service has initiated deinstallation.IS-BTOS: Real Mode DeInstall. Returned in response to a deinstallation request to indicate that the IS-BTOS Service has initiated a real mode style deinstallation. This signifies that the program the issued the deinstallation request is responsible for vacating the partition that IS-BTOS occupies. The return of this code signifies that IS-BTOS is ready to be vacated.IS-BTOS: Bad Data Size. An attempt was made to install the IS-BTOS Service giving a buffer size that is not one of the allowable values.IS-BTOS: No Parameters. No parameters were entered on the IS-BTOS Service installation form.IS-BTOS: Invalid Entry. There was an invalid entry on the IS-BTOS Service installation form.IS-BTOS: Trace File Open. An attempt to start a trace operation failed because the file specified does not match that of the companion operation which is already started.itsBTOS: Trace Already Active. An attempt to start a trace operation failed because the operation has already been started.IS-BTOS: Trace Already Inactive. An attempt to stop a trace operation failed because the operation has already been stopped.IS-BTOS: No Access Points. The IS-BTOS Service could not install because IPC could not supply the necessary access points or has not been installed.IS-BTOS: Resources Unavailable. The resources needed to complete the requested operation were unavailable, such as no available converations. When installing the IS-BTOS Service this is returned when it could not install due to insufficient resources, such as memory.IS-BTOS: Bad User Name. The user name specified in the ISBTOSAsynchCmd request was malformed.IS-BTOS: Invalid Command. The command parameter value is not one of the accepted values.IS-BTOS: Short Return Buffer. The return buffer size is less than the minimum allowed.IS-BTOS: Unable To Cancel Job. The IS-BTOS Service was unable to cancel the specified job.IS-BTOS: Bad Buffer Size. The Buffer size specified is not large enough.IS-BTOS: Invalid Op Type. The operation type is not an accepted value.IS-BTOS: Invalid Query Type. The query type is not an accepted value.IS-BTOS: Data Truncated. The return buffer was too small and the data was truncated.IS-BTOS: No Queue Manager. The IS-BTOS Service was not installed because the Queue Manager is not installed. Also returned to any request, with the exception of the deinstall request, if the Queue Manager is deinstalled after the IS-BTOS Service has been deinstalled.IS-BTOS: Bad Host ID. The host ID is too long or does not exist.IS-BTOS: No Batch Queue. The IS-BTOS Service was not installed because a required batch queue does not exist.IS-BTOS: Bad Job Name. The size of the job name in a job status report was too large.IS-BTOS: Unable To Assign Command Id. The command was not queued because of an inablility to assign a command ID. This could be because of a file system failure or because all available command IDs have been allocated.IS-BTOS: Out Of Range. A value in the request was out of range.Version Control System: Differences encountered in source files. This error occurs when DDiff compares two files and finds that they are not identical.Version Control System: A parameter is either missing or invalid.Version Control System: A fatal error occurred. VCSMAKE was unable to produce a do-file.Version Control System: No errors but none of the files needed to be remade.BNet II BP Link: Internal Invalid BPLWABNet II BP Link: Link down The BP Link Service cannot communicate with its counterpart in the paired master. No external action is taken; the calling process responds to the problem. Internally, the BP Link softwa# re attempts to reestablish communications.Target Name Invalid Length A target name (BP Transport Remote Application Process name) is too long (greater than 12 characters) or too short (less than 2 characters).BNet II BP Link: No Such Target The specified target process does not have a link session open on the remote system. Possibly the BP Transport's Local or Remote Application Process does not match.BNet II BP Link: No data buffers available. Internal error.BNet II BP Link: Data buffer request is too large. Internal error. BNet II BP Link: Too many clients. The BP Link Service cannot accept additional clients. Check the :ClientCount: parameter in the BPLinkConfig.sys file.BNet II BP Link: Session is closing. Internal error. BNet II BP Link: SendCheck timed out. The link service on this system has failed to transmit the message within the configured time limit. Either the link service has terminated or the value of the :SendCheckTimeout: configuration parameter in the BPLinkConfig.sys file is too small.BNet II BP Link: Transmission incomplete. Internal error. BNet II BP Link: Duplicate process name. The process name provided matches the name of another session already open. Check the BP Transport's Local and Remote Application Process names.BNet II BP Link: Message or extended buffer does not begin on a word boundary. Internal error.RAF: RAF Target cannot be loaded after Windows. Deinstall the Window Service and try again, or edit your system initialization file to install RAF before it installs Windows, then reboot the workstation.RAF: Target User Profile not defined for this Workstation ID. Use the RAF Target User Profile to define this Workstation ID.RAF: Service can not be loaded on single partition operating system. RAF is not supported for use on single partition real mode operating systems. You must load a BTOS II or higher operating system.RAF: Service can not be loaded on an XE-520/530 server. RAF is not supported for use on an XE-520 or XE-530 shared resource processor.RAF: RS-232 Target Interface can not be loaded before Modem Service. Deinstall the Modem Service and try again, or edit your system initialization file to install RAF before the Modem Service, then reboot the workstation.RAF: Target has not responded, RS-232 Interface time out. Increase your response time through the RAFConfig.sys file.RAF: RAF Bridge can only be loaded on the server. You have tried to load the RAF Bridge on a client workstation. It must be installed on the server.RAF: RS-232 Target Interface is already loaded for this port. No action is needed. Your RAF Target Interface is already loaded.RAF: RAF Bridge is already loaded No action is needed. Your RAF Bridge Interface is already loaded.RAF: RAF Bridge cannot be loaded after RAF Target. Do RAF Unload Target before RAF Load Bridge.RAF: RAF Target is already loaded. No action is needed. Your RAF Target is already loaded.RAF: Performance Gathering Service (PGS) is already loaded. No action is needed. Your the Performance Gathering Service is already loaded.RAF: RAF Bridge working at full capacity; Signon request denied. The system is temporarily busy. Wait and try to sign on again later.RAF: RAF internal error: Contact your local Unisys support center.RAF: Invalid Profile File. The file specified is not a RAF Profile file. Check the file specification and the format of your RAF Profile file. See your RAF manuals for details.RAF: Log File Full. The RAF log file specified is full. Delete or rename, then redefine by pressing the LogDef function from the RAF Target User Profile Log On Screen.RAF: Log File Error. RAF encountered a problem with the Log file. Make sure that the log file is defined through the RAF Target User Profile. If problem persists, delete or rename the log file then redefine it using the RAF Target User Profile command.RAF: Queue manager must be installed to support Printer Redirection Install the Queue manager at the server workstation.RAF: Invalid Script file. The file specified is not a RAF script file. Check the file specification and the format of your RAF Script file. See your RAF manuals for details.RAF: User not authorized. Check your RAF profiles to be sure your user name is defined.RAF: Node specified in script file is not accessible. The network node specified in your RAF script file was not accessible. The network may be down. Also check the node specification in your script file to be sure it is valid.RAF: No targets available on the selected node. There are no targets installed on any of the workstation in the specified node. (If running Cluster BNet, the server node name needs to be selected.)RAF: Workstation specified doesn't exist. Check the workstation ID specified; also check that RAF is installed with such an ID at the one of the workstations in the target node.RAF: Multiple targets on selected node; Specify one. There is more than one workstation at the selected node with RAF Target loaded. Select one by specifying the Workstation ID.RAF: Password required to install. Use the Path command to enter the correct password before installing.RAF: Log file being used; Cannot deinstall RAF Target. The log file is temporarily busy. Try to deinstall again later.RAF: Attempt to load system service after loading Context Manager. System services must be loaded before the Context Manager is installed. Deinstall Context Manager or log out and sign on again using a sign-on user name that does not install the Context Manager.OSI Session: The OSI Session Send Request queue is full. The Session Send Request queue is full. This is a temporary error. The user should re-send the request when this error occurs.OSI Session: The OSI Session Receive Request queue is full. The Session Receive Request queue is full. This is a temporary error. The user should re-send the Receive Request when this error occurs.OSI Session: The session connection is aborted due to lack of channel control block. The session connection request is rejected due to the lack of a channel control block. This is a temporary error. The user should try to issue the connection request again when this error occurs.OSI Session: The session connection is aborted due to lack of resources. The session connection is aborted due to lack of data buffers, buffer control blocks, interaction control blocks, or request blocks. This is a temporary error. The user should try to re-establish the connection request when this error occurs. However, if the problem persists, the user should install OSI Session with more resources.OSI Session: OSI Session is aborting the session connection. OSI Session aborts the session connection as a result of a Provider Abort Indication. The user should check the reason code for the disconnection and re-establish connection when the cause of the abort is cleared.OSI Session: OSI Session is closing the session connection. OSI Session closes the session connection as a result of a User Abort Request.OSI Session: OSI Session closes connections because the SS-user is terminated.  OSI Session closes all session connections to/from an SS-user that is terminated.OSI Session: The OSI Session Listen Request is cancelled because the lower layer service provider is deinstalled. OSI Session cancels the Listen Requests because the service provider is deinstalled. The user should reinstall the lower layer service provider and try again.OSI Session: OSI Session rejects a request block because it contains invalid parameter. The OSI Session detects an invalid parameter in the user's request block. The user should correct the request block and re-send the request.OSI Shared Buffer Pool: OSI Shared Buffer Pool has already been installed. This error is generated because the user tries to install OSI Shared Buffer Pool more than once.OSI Shared Buffer Pool: cannot find OSI Shared Buffer Pool error messages. The OSI Shared Buffer Pool message file is missing or the user tried to install OSI Shared Buffer Pool by running the OSI Shared Buffer Pool run file directly. The user should check for the presence of the Shared Buffer Pool message file and install OSI Shared Buffer Pool using the Install OSI Shared Buffer Pool command.OSI Shared Buffer Pool: not enough parameters. This error is generated when the user installs the OSI Shared Buffer Pool by running the run file directly and enter too few parameters. The user should install OSI Shared Buffer Pool by issuing the Install OSI Shared Buffer Pool command.OSI Shared Buffer Pool: too many sub-parameters. This error is generated when the user installs OSI Shared Buffer Pool by running the run file directly and enter too many parameters. The user should install OSI Shared Buffer Pool by issuing the Install OSI Shared Buffer Pool command.OSI Shared Buffer Pool: integer expected. The parameter value for OSI Shared Buffer Pool is not an integer. The user should correct the parameter value and re-issue the Install OSI Shared Buffer Pool command.OSI Shared Buffer Pool: parameter value out of range. The parameter value specified for Install OSI Shar$ ed Buffer is out of range. The user should correct the parameter value and re-issue the Install OSI Shared Buffer Pool command.OSI Shared Buffer Pool: OSI Shared Buffer Pool cannot allocate memory. The installation of OSI Shared Buffer Pool failed due to lack of physical memory. The user should either add more physical memory or install the Shared Buffer Pool with fewer data buffers.OSI Shared Buffer Pool: Invalid buffer size. The user has specified a buffer size that is smaller than 64 bytes. The user should enter a valid buffer size (64 to 1024) and re-issue the Install OSI Shared Buffer Pool command.OSI Session: OSI Session cannot find Event Messages. The OSI Session event message file is missing or the user tried to install OSI Session by running the OSI Session run file directly. The user should check for the presence of the event message file and install OSI Session using the Install OSI Session command.OSI Shared Buffer Pool: OSI Shared Buffer Pool deinstall failed because there are data buffers still in use. The OSI Shared Buffer Pool cannot be deinstalled because there are data buffers still in use. The user should deinstall all system services that use the OSI Shared Buffer Pool before issuing the Deinstall OSI Shared Buffer Pool command.OSI Shared Buffer Pool: OSI Shared Buffer Pool cannot be deinstalled remotely. This error is generated when the user issues the Deinstall OSI Shared Buffer Pool command from a different (remote) workstation. The OSI Shared Buffer Pool can only be deinstalled locally.OSI Administrator: Invalid location specification used in OSI Session Administrator command. The Location field specification in the OSI Session Administrator command is invalid. The user should correct the Location parameter and try the command again.Configuration file invalid. CTOS SNADS cannot access either the specified or the default configuration file. Either the file does not exist or it is corrupted. If the file does not exist, create it using the SNADS Monitor, or restore it from the most recent system backup. The default configuration file name is SNADScfg.sys.Deinstallation request denied. CTOS SNADS will not allow deinstallation if a SNADS Send or Receive process is active. To prevent premature termination of transaction programs, specific servers or LU 6.2 sessions, all SNADS Send and Receive processes must be idle. Wait for the SNADS Send or Receive process to finish normally. If deinstallation is immediately necessary, you may force deinstallation by stopping the Send or Receive processes: If a Send process is active, use the SNADS Monitor queue management verb SNADSQueue() (``Drain'' or ``Hold'') to stop distributions. If a Receive process is active, use the APPC Control Operator to bring down the LU 6.2 session(s). This will cause the Receive process to terminate.Forms file invalid. The SNADS Monitor cannot access the forms file containing its display forms. Either the forms file ('SNADSMonform') does not exist or the file is corrupted. Restore the file from the most recent system backup, or from the product release disk.Message file invalid. Either CTOS SNADS or the SNADS Monitor cannot access the Native Language Support (NLS) message file it needs to retrieve required text strings. Either the file does not exist, it is not in the CTOS SNADS work directory, or the file is corrupted. If the files 'SNADSMsg.bin' or 'SNADSMonMsg.bin' do not exist, copy them from the CTOS SNADS product release disk. Alternately, use the Create Message File Executive command to create them. Source text files are available on the product release disk as well. If the files exist, they may be corrupt. Try restoring them from the product release disk.Invalid start index supplied. The wIndex parameter is not in the range of possible values. wIndex is supplied on a call to GetAssociatedDSUNs(), GetConnectionInfo(), GetLoggedError(), GetLoggedIUEntry(), or ListDistributionIDs(). The above verbs may be called repeatedly to retrieve portions of an array of data buffers. The wIndex specified is for an element that does not exist. Call the verb again with a correct value of wIndex, which should be one more than the number of buffers that have been retrieved prior to this point. Alternately, call the verb with wIndex set to 1 to reinitiate the process of retrieving buffers.Incompatible version. The particular release of CTOS SNADS executing does not support the version of the request issued. Either a newer Application Programming Interface (API) verb or a newer specific server interface verb was issued to an older release of CTOS SNADS. Install the newer release of CTOS SNADS, or relink your application (or specific server) with the older version of the API.Buffer Truncated. A complete data buffer could not be returned from a CTOS SNADS verb. The application programmer has not allocated enough memory space to hold all the information that could have been returned. The programmer supplied a buffer area, and the maximum size of that buffer. However CTOS SNADS will only return data to the buffer up to the maximum size specified. Any additional data available was not returned. If the data buffer is actually an array of structures, this error means either the last element returned has been truncated, and/or additional elements are available, but could not be returned. The programmer may ignore this error if only a portion of the buffer was desired, and that portion was returned. Otherwise, additional buffer space should be allocated and the verb issued again. If the verb called was GetAssociatedDSUNs(), GetConnectionInfo(), GetLoggedError(), GetLoggedIUEntry(), or ListDistributionIDs(), the verb may be issued again to retrieve the additional data. In this case the wIndex parameter should be set to indicate the value of the last truncated element returned.Connect active. There is already an active connection to CTOS SNADS. The application programmer has already issued the ConnectSNADS() or ConnectSNADSLL() verb to a particular CTOS SNADS system service. Each program may connect to more than one instance of CTOS SNADS, but the same program can have only one connection to any given instance. You may ignore this error if the desired connection is already active. If you wish to dis-establish the connection, the DisconnectSNADS() verb must be issued for the desired active connection. ConnectSNADS() or ConnectSNADSLL() may then be re-issued.Connect inactive. The application program is currently not connected to CTOS SNADS. The application programmer has not yet issued a ConnectSNADS() or ConnectSNADSLL() verb. This is necessary before any other CTOS SNADS Application Programming Interface (API) verb is issued (e.g., a distribution or Operations verb). Issue ConnectSNADS() or ConnectSNADSLL() to connect to a particular instance of CTOS SNADS. API verbs may then be issued.Cannot Connect to CTOS SNADS. CTOS SNADS cannot accept any additional connections from application programs or SNADS Monitors. The maximum number of connects configured for this instance of CTOS SNADS are currently in use. Wait until other applications are finished using CTOS SNADS. The DisconnectSNADS() verb must be issued before another connect is possible. Alternately, finish any SNADS Monitors which may be connected to CTOS SNADS. Otherwise reconfigure CTOS SNADS and specify a larger value for the maximum number of connects.More data available. The Application Programming Interface is indicating that additional data buffers are available than could be returned in the current call to GetAssociatedDSUNs(), GetConnectionInfo(), GetLoggedError(), GetLoggedIUEntry(), or ListDistributionIDs(). Due to the amount, all the data available could not be returned on the current verb call. There are limitations on the size of a request block if it is routed over BNet or cluster communications. The application's buffer size for receiving data may also be limited. The programmer should call the verb repeatedly, until all data buffers are retrieved. This involves varying the value of the wIndex parameter. See the description of the verb you are using.Unrecoverable error. CTOS SNADS encountered an unrecoverable error, making further processing impossible. All further requests received by CTOS SNADS are rejected with this error code. CTOS SNADS detected an unexpected condition, probably due to corrupted memory. Since the current state of execution is unreliable, CTOS SNADS is requesting deinstallation. This is caused by an internal problem, an inconsistent state, or a problem with the operating system or environmental software. Deinstall CTOS SNADS and then reinstall it. Examine the SNADS Interchange Unit log, SNADS Error log, or the system log ('log.sys', using the PLog command) for possible causes. Attempt to correct the situation if possible, or call your Unisys support representative if the problem persists.Deinstall state entered. A forced deinstallation was requested. All outstanding send/receive requests are ignored.Function not allowed. An inappropriate advanced Distribution verb interface function$  was issued. A programmer using the advanced Distribution verb interface must issue the various functions in a prescribed sequence. Not every function may be issued for all Distribution verbs. For instance, the SetFeedBack() function must only be issued if a DistributeData() verb is being constructed. Review the rules for issuing advanced Distribution verb interface functions and correct the application program.SNADS return code generated. The advanced Distribution verb interface function caused CTOS SNADS to generate an unsuccessful SNADS return code. Due to some SNADS error condition, the advanced Distribution verb interface function just issued caused a SNADS return code to be generated. However, the function may not be capable of returning the return code directly. For instance, if the SetObject() function is called, a specific server may encounter a temporary server error while processing the object. SetObject() would then return ercRCGenerated. The programmer should issue the FinishDIU() function to abort the construction or reception of a DIU and retrieve the SNADS return code value.Server request information invalid. The request code information supplied by a specific server registering with CTOS SNADS is incomplete. The possible reasons are: 1. IncrementObjLockServer() and DecrementObjLockServer() functions were not specified. 2. A read function is specified, but all three read functions were not specified. 3. A write function is specified, but all three write functions were not specified. All eight specific server interface functions must be specified with a corresponding request code. Some requests may have the value 0 if they're not implemented. Review the specific server interface for details.Specific server registered. For RegisterSNADSServer(): A specific server with the supplied name is already registered with this CTOS SNADS. For DeregisterSNADSServer(): The specific server name specified was not previously registered with this CTOS SNADS. Each specific server must be configured in the SNADS configuration file. When a specific server is executed, it must register with CTOS SNADS to indicate its availability, using the RegisterSNADSServer() verb. This error indicates the server has already registered using the same name. A single application may perform the function of several specific servers at once, in which case it can issue several registration requests, one for each different server name. Or, it may be a single specific server, and only one registration request is allowed. Another program may be performing the function of the named specific server. In this case, wait for that program to issue DeregisterSNADSServer() before issuing RegisterSNADSServer() again. There may be an application error if the same specific server attempted to register twice with the same server name without first issuing DeregisterSNADSServer(). Check the server name for misspelling. Specific server not configured. The specific server name specified is not configured in this CTOS SNADS. Each specific server must be configured in the SNADS configuration file. This allows CTOS SNADS to determine the name of each potential specific server. CTOS SNADS will reject a received distribution, or a request that is made to send a distribution, if the supplied server name is not known. Use the SNADS Monitor to add a new specific server to the SNADS configuration file. Alternately, ensure that the supplied server name is spelled correctly.SNA RJE: Attempt to deinstall from another workstation. Deinstall from the workstation on which the MLU Manager is installed. SNA RJE: Attempt to deinstall on a single partition OS. You cannot deinstall from a single partition operating system. SNA RJE: Attempt to deinstall under Context Manager. You cannot deinstall under Context Manager. SNA RJE: Attempt to deinstall with sessions active. End all sessions before attempting to deinstall. Local Event Management: Event Command and Control Utility (ECCU): Warning - Local Logger has detected an error in a command directive. The directive was syntactically correct, so ECCU passed it on to Event Transmitter. However, it contains information that does not make sense.Local Event Management: Event Command and Control Utility (ECCU): Warning - Log Converter has detected an error in a command directive. The directive was syntactically correct, so ECCU passed it on to Event Transmitter. However, it contains information that does not make sense.Local Event Management: Event Command and Control Utility (ECCU): Warning - Event Configurator has detected an error in a command directive. The directive was syntactically correct, so ECCU passed it on to Event Transmitter. However, it contains information that does not make sense.Local Event Management: Event Configurator: Incompatible .Bfc file. This error code implies that the .Bfc file supplied to the Event Configurator program being run was generated by a different release, or has become corrupted.Local Event Management: Event Configurator (EC) System Service: Invalid option. This error should only be returned by the EC System Service to cooperating programs. It implies that the internal function requested was illegal or invalid.Local Event Management: Event Configurator (EC) System Service: Event not generated. The event was not generated because the send level for that event (as specified within the current .Bfc file) was less than that set when the EC System Service was installed.Local Event Management: Event Configurator (EC) System Service: Event PenId Unknown. This error code is returned to a event generator when the requested PenId could not be found within the current .Bfc file.Local Event Management: Event Configurator (EC) System Service: Sentence Overflow. This error is returned when the event received has an entry in the .Bfc file and this reconfigured event is too large for the Event Manager (greater than 4096 bytes). Check the entry in the .Bfc file by running the EC List program for the PenId that generated the error.Local Event Management: Event Configurator (EC) System Service: Termination return. This error code is returned within the request block returned to the user, because an Abort or Termination request was received for that user. If a program receives this error code, then there is a problem either with the EC System Service or the operating system.Integrated Event Monitor: VR Command and Control Utility (VCCU): Recording is already on. You have attempted to turn recording on when it is already on.Integrated Event Monitor: VR Command and Control Utility (VCCU): Recording is already off. You have attempted to turn recording off when it is already off.Integrated Event Monitor: VR Command and Control Utility (VCCU): Recording file is corrupt. The recording file has been corrupted or a file that is not in recording file format has been specified. Specify a file with the correct format.Integrated Event Monitor: Database Insert (DBI): Invalid request. DBI received an unexpected CTOS request, that is other than a DBI request.Integrated Event Monitor: Database Insert (DBI): DBI is terminating. When DBI terminates processing, this error code is returned to all outstanding requests.Integrated Event Monitor: Database Insert (DBI): DBI user is terminating. When DBI receives a termination request from a user, it responds to all the outstanding requests from that user with this value.Integrated Event Monitor: Database Insert (DBI): Invalid domain. When DBI receives an insert request from a unknown domain, it responds back to the requester with this value.Integrated Event Monitor: Database Insert (DBI): Invalid data. If the data received from the node is inconsistent in its expected structure, DBI responds to the requester with this value.Integrated Event Monitor: Database Insert (DBI): Fetch exceeded maximum domains. During DBI initialization, if DBI fetches more rows from the domain table than it expected, it returns this error code to the operator.Integrated Event Monitor: Database Insert (DBI): No rows in domain table. This error could be encountered during DBI initialization, when DBI fetches less rows than it anticipated from the Domain Table.Integrated Event Monitor: Database Insert (DBI): Invalid format identifier. The format identifier within the received event is invalid.Integrated Event Monitor: Database Insert (DBI): Unsuccessful Database insert. Returned to requester, when DBI encounters an ORACLE database insert problem. A management event is generated which contains the actual ORACLE error code.Integrated Event Monitor: Database Insert (DBI): Fetch problem on SMS$ND table. Returned to requester when DBI encounters an error during a fetch operation on the SMS$ND table.Integrated Event Monitor: Database Insert (DBI): Fetch problem on SMS$EQ table. Returned to requester when DBI encounters an error during a fetch operation on the SMS$EQ table.Integrated Event Monitor: Database Insert (DBI): Unsuccessful insert into SMS$EVENTS. Returned to requester when DBI encounters an error during an insert op% eration into the SMS$EVENTS table.Integrated Event Monitor: Database Insert (DBI): Unsuccessful insert into SMS$EH. Returned to requester when DBI encounters an error during an insert operation into the SMS$EH table.Integrated Event Monitor: Database Insert (DBI): Unsuccessful commit. Returned to requester when DBI encounters an error during a database commit operation.Integrated Event Monitor: Unknown Symbolic Key returned by DBI. The Symbolic Key in an Event Transmitter request to DBI has no corresponding row in SMS$EventSets.Integrated Event Monitor: Database Insert (DBI): Insert threshold reached. The DBI queue of events to be inserted into the database is full. Delay and retry sending the request to DBI.Integrated Event Monitor: Compare Table Utility (CTU): User does not have the necessary authority. Database Insert (DBI): ORACLE Username not authorized. The registered IEM ORACLE user has not been given the authority to use the named utility.Integrated Event Monitor: Compare Table Utility (CTU): User does not exist. Display Manager (DM): ORACLE Username not registered as an IEM user. The ORACLE User has not been registered in the SMS$USER table.Integrated Event Monitor: Display Manager (DM): Display System already installed. DM is already installed on this workstation in another partition.Integrated Event Monitor: Display Manager (DM): Bad format request. An application made a display system request in an incorrect format. See also Erc 60045.Integrated Event Monitor: Display Manager (DM): Bad usernumber. An application made an display system request with an unknown CTOS usernumber.Integrated Event Monitor: Display Manager (DM): No windows available. The display system is currently out of windows. Increase the MaxWindows value in the IEMWindows.cfg file.Integrated Event Monitor: Display Manager (DM): Version mismatch. Different versions of the display system components are being used together. Check version strings of all display system runfiles.Integrated Event Monitor: Display Manager (DM): Insufficient memory. There is insufficient memory for the display system. Set flexible partitions for Display Manager when using Context Manager. See the Integrated Event Monitor documentation for details of the required partition size. Check that the partition the program is being loaded into is at least the stated size plus the MaxMemory value in the IEMWindows.cfg file.Integrated Event Monitor: Display Manager (DM): Internal error.Integrated Event Monitor: Display Manager (DM): No display system cache memory. The display system cache is currently out of memory. Increase the MaxMemory value in the IEMWindows.cfg file.Integrated Event Monitor: Display Manager (DM): Internal error.Local Event Management: Local Logger Facility (LLF): Local log file is corrupt. This error code is returned by LLF when the open local log file is corrupt. When this error is received, first check that the File name prefix parameter of the Retrieve Local Events command specifies a valid local log file. If this parameter does specify a valid local log file, then deinstall LLF, delete the corrupt local log file, and reinstall LLF. The log records of that particular day will be lost. Local Event Management: Local Logger Facility (LLF): Internal error.Local Event Management: Local Logger Facility (LLF): No free read sessions. Too many instances of Local Logger Display Utility (LLDU) are attempting access to LLF.Local Event Management: Local Logger Facility (LLF): Invalid read session handle. The read session handle received from a Local Logger Display Utility (LLDU) is invalid. This error can occur for two reasons:  The original LLF system service with which LLDU had a read session has been deinstalled and a new LLF system service installed.  The read session handle is corruptLocal Event Management: Local Logger Facility (LLF): Event corrupt. The data in an individual Event message is corrupt. Consult Technical Support.Local Event Management: Local Logger Facility (LLF): Local Logger Facility (LLF): No log file exists. No log file(s) exist for the default or chosen date range. It may mean that no Events were stored by LLF for the default or chosen date ranges.BNet II BP Link: Internal error. Message area length must be nonzero.BNet II BP Link: Internal error. BNet II BP Link: Receipt waiting.BNet II BP Link: Deinstalled. BP Link Service has been deinstalled.POSIX Service: Process table is full. Too many POSIX tasks are executing concurrently. Execute fewer tasks or increase the value for NumberOfExecutableImages in POSIXConfig.sys.POSIX Service: Wrong POSIX Service. The POSIX Service version being used is too old. The POSIX application requests operations that are not supported by the executing version of the POSIX Service.POSIX Service: No environment. An attempt was made to get or set an environment variable where no environment exists.POSIX Service: The environment is full. An attempt was made to set an environment variable when the environment was full. Increase the size by changing EnvironmentSize in POSIXConfig.sys.POSIX Service: Unknown user. The signon username is not contained in the /etc/passwd file. See the system administrator to have your username included.POSIX Service: File system is corrupt. A file system contained in POSIXFileSystem.sys is corrupt. See system administrator.POSIX Service: No root volume. The file system root volume cannot be found. Verify that the RootVol entry in POSIXConfig.sys contains a valid CTOS Volume name on your system.ISDN Service: LAPD reset and reestablished an MF-Established link connection at Layer 2. LAPD returns this code to indicate that an MF-Established link connection has been reset at Layer 2 and is reestablished. All outstanding WriteDLFrame requests with FrameType=0 (I-frame) are returned with this status code when the reset occurs. This code indicates normal LAPD operations. No recovery action is required.SNA Transport: An invalid Frame specification. The frame type in WriteDLFrame is incompatible with the LSAP type. ISDN Service: LAPD received an invalid frame type specification in a WriteDLFrame request. LAPD returns this code if it receives a Write request with an invalid frame type specification. A modification of the client software is required to resolve the problem.ISDN Service: This code indicates that LAPD has run out of some resource. When received in response to an OpenStation request, it means that the maximum number of connections permitted in the configuration file for a specified Service Access Point Identifier (SAPI) has been exhausted. In this case, reconfigure LAPD for more connections on that SAPI. When received in response to a ReadDLFrame or WriteDLFrame request, it indicates the client has issued too many of those requests simultaneously. The number of ReadDLFrame or WriteDLFrame requests that LAPD can hold onto at one time is limited to eight (8). In this case, a modification of the client software is required to resolve the problem.Ethernet DLL: Link Deinstalling The Ethernet DLL performed an emergency deinstallation and responded to all outstanding requests.ISDN Service: LAPD has released MF-Established operation on the link connection. This status code indicates that the link connection has been released. LAPD returns this code to indicate that Acknowledged operation on the link connection has been released. This code is returned to WriteDLFrame requests that require Acknowledged operation prior to executing the client's request. All outstanding WriteDLFrame requests for Information frames (I-frames) are returned with this status code if LAPD or the network releases the connection. This code indicates normal LAPD operations. No recovery action is required.BMULTI: Application cannot be suspended.BMULTI: Session active. An active session must be suspended before it can be resumed by another application.BMULTI: Suspend/Resume session overflow. All available configured Suspend/Resume sessions have been used up.BMULTI: VADs not supported. Virtual Addresses cannot be used as Suspend/Resume addresses. BMULTI: Invalid command. An application has attempted to issue a suspend request on an active connection that was not initiated through the Suspend/Resume filter.BMULTI: Invalid Service ID. A BmResume call was issued with an invalid Service ID in the parameter fields.BMULTI: Application suspended. The current session is in the suspended state and will refuse all commands until the session is resumed.BMULTI: Cancel command denied. The application state is "Receive Ready," "Receiving," or "Transmitting," and the session cannot be suspended.SNA 3270: Invalid Call. Your application may not call this procedure at this time. Depending on the procedure, this could mean that:  Your application called one or more old VTI procedures before calling a VTI+ procedure (an application cannot call both)  The session is open or closed  Required memory is allocated or deallocated  The session is suspended or resumed In general, to avoid this error, make sure you use the VTI+ proc% edures according to the rules for their use, described in the SNA 3270 documentation. The manual also describes special recovery recommendations unique to specific procedures.SNA 3270: Required Memory Not Allocated. Your application called a procedure for which required memory is not allocated. If your application received this error while trying to open a session, first allocate memory (VTIAllocateMemory) and then open the session (VTIOpenSession). If your application received this error while trying to deallocate memory (VTIDeallocateMemory), no memory requires deallocation. Therefore, remove this call from your application.SNA 3270: Invalid Screen Mode. Your application specified the screen mode (ScreenMode) incorrectly when calling this procedure (VTIAllocateMemory). Change the value and try again.SNA 3270: Session Not Suspended. Your application attempted to resume a session that is not suspended when calling this procedure (VTIResumeSession). Change the LU number (pLUNumber) to specify a different session, and try again.SNA 3270: VTI Terminated. Your EEHLLAPI application receives this error code when the VTI+ application it is connected to ends before your EEHLLAPI application disconnects. Before continuing, your EEHLLAPI application must call Disconnect Presentation Space (function 2) and then try to connect to another session. If no other session is available recovery is not possible (fatal error).SNA 3270: VTI Suspended. Your EEHLLAPI application receives this error code when the VTI+ application it is connected to suspends before your EEHLLAPI application disconnects. Before continuing, your EEHLLAPI application must call Disconnect Presentation Space (function 2) and then try to connect to another session. If no other session is available recovery is not possible (fatal error).SNA 3270: Invalid Update Parameter. Your application specified the update size, update address or cursor address incorrectly when attempting to update the screen (VTIUpdateScreen). Change the values and try again.SNA 3270: Invalid Workstation Type. Your application specified a screen mode (ScreenMode) that is not supported on the workstation your application is running on. This message is displayed if, for example, you selected color mode for a monochrome monitor. Enter a valid value in the Screen Mode parameter in the CRT Subsystem's configuration files and try again. Values are specified for VTIAllocateMemory. SNA 3270: No Keyboard Profile. The file containing the keyboard profile (pKbdPro) could not be opened. Your application specifies the keyboard profile file while trying to load a keyboard profile (VTILoadKbdProfile). This could mean that the file name is specified incorrectly, the file does not exist, or that someone is using the file. To correct for cases where the file name is specified incorrectly, change the name of the file and try again. You may need to check the length of the file specified (cbKbdPro) as well as the name given (pKbdPro). To correct for cases where the file does not exist, copy the file SNAKbd.Pro from the product disk and try again. To correct for cases where the file is not in use, wait until the file is not in use and try again.SNA 3270: Invalid Log Type. Your application specified an invalid log type (LogMode) when attempting to start a log (VTIStartLog). Change the value and try again.SNA 3270: Memory Already Allocated. Your application attempted to allocate memory which has already been allocated (VTIAllocateMemory). Remove this call from your application.SNA 3270: Not Between Brackets. Your application tried to suspend the session (VTISuspendSession) when the session was not between brackets. The host, for example, may have been sending a message. Try to clear this state by calling VTIAcceptScreenBuf a few times, or wait and then try suspending your session later.SNA 3270: Suspend File Not Found. The 3270 API could not find the file containing required information about the session your application tried to resume (VTIResumeSession). This could mean that the session is not suspended, that someone deleted the file, or that someone is using the file. To correct for cases where the session is not suspended, check to see that the LU number is specified correctly and try again. Where the file is deleted or in use, recovery is not possible (fatal error).SNA 3270: Invalid BIND. The host sent invalid BIND parameters when your application tried to resume a session (VTIResumeSession). Check the application's parameters and try again.SNA 3270: Cannot Reset. Your application included "Reset" as a keystroke in the data string (pKbdStream) sent to the host (VTIReturnScreenBuf or VTIWriteScreenBuf with an AID key), and Reset cannot be performed. Wait and try again.SNA 3270: Scroll Limit. Your application included a request to scroll as a keystroke in the data string (pKbdStream) sent to the host (VTIReturnScreenBuf or VTIWriteScreenBuf with an AID key), and the scroll cannot be performed. No recovery is necessary.SNA 3270: No GRA Font. The graphics font file (SNAGraphics.Font) required to run your application is not available. Check to be sure the file is in the right directory on your local or server workstation. If it is not, copy it from the product disk.SNA 3270: Non-GRA Workstation. The workstation your graphics application is running on does not support the display of graphics screens. Your application gets this error when it calls VTISetUpScreen. To recover, run your application on an appropriate workstation, or change your application.SNA 3270: What Symbol. The host did not recognize a keystroke sent to it by your application (VTIReturnScreenBuf or VTIWriteScreenBuf with an AID key). Send RESET to the host to clear the condition.SNA 3270: No 3270 Service. Your application attempted to suspend/resume a session, or is an EEHLLAPI application, in a configuration without the SNA 3270 Service. Install the service and try again.SNA 3270: HLL Unsupported Function Number. Your EEHLLAPI application receives this error code when it specifies an invalid function number. Change the function number and try again.SNA 3270: Invalid Password. Your application specified the password (pPassword) incorrectly when attempting to resume a session (VTIResumeSession). Change the value and try again.SNA 3270: Attempt to install the Screen Capture system service on VGA hardware. You cannot install Screen Capture on VGA hardware.SNA 3270: Error Reading Keyboard Profile. The 3270 API reported errors loading the keyboard profile, which are written to the keyboard log file (if supplied). Check the profile to be sure you reconfigured it properly (see to the SNA 3270 operations documentation).SNA 3270: MGS and EEHLLAPI connection are not compatible. Your application specified routing information (pRouteInfo) for the Multiple Gateway Server (MGS) for a session which supports EEHLLAPI connections (fConnectSupported). Routing information is specified when calling VTIOpenSession; the flag for connecting EEHLLAPI applications is specified when calling VTIAllocateMemory. Change one value or the other, and continue.mmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm& mmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm& mmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm' mmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm' mmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm Crashdump.sysBootRecord.sysMfd.sys CrashDump.sysFileheaders.sysLog.sys SysImage.sys BadBlk.sys+System Utilities Diskette 4 of 8 (B25STP-4)(  @ B25STP-4/8@ zwzwB @ D < /> UH89|P^Sys: CTOS 9|gDFileheaders.sysSys< zwzwzwxD xC BootRecord.sysSys: zwzwzwMfd.sysSys: zwzwzwB Log.sysSys< zwzwzw@ F SysImage.sysSys< zwzwzwF BadBlk.sysSys< zwzwzw CrashDump.sysSys: zwzwzw@ +System Utilities Diskette 4 of 8 (B25STP-4)cinchSys< zwzwzwV SysInit.RuncinchCTOS  zw 7wQw SystemMgr.runcinchCTOS  zw&Ux&Ux)&(M VolumeStatus.runcinchCTOS  zw wQw24 StatusCodesMsg.bincinchCTOS  zw!wQwf  F d,n +m*l( )k(j'i&h%g$f#e"d!c ba`_^]\ [ !Z!") Y"#X#$W$%V%&U&'T'(S()R)*Q*+P+, O,- N-. M./ L/0 K01J12I23H34) G45F56E67D78C89B9:@:;{; SysInit.Run SystemMgr.run VolumeStatus.run StatusCodesMsg.bin mJhT%P\uhѻ 9ADS 5 T m pp!#> |}FD" 6!"(#$%s4&'()*+V[,-6.d!2V3I4$ 5J 6X" 7Pz 9u <? =] >kH?@iA Bk+CDHEF PQS#Ri (Sv(T)U)V|*W*X#+Y%+Zh,[zf-\/]1^P2_)%3`|N3aI3b94czL4dC4el 5f^u6g7h8iE:j;k=lA?m?n9ICpDx^EyT`Fz_F{G|\G}\H~YdHHt}JmJ^RTT@UVW 8X XXvxXnX0\Y7YCYZ?[]^:_:_E`X`bbudEfCf9h:iil[jjlm09nXiop.rXt u{?uw{z{{&(|N|}#},}(}~;bL.:/h7oS+‚)x)}|a Ef6c*@("hH,*GVҐs( 5 aБ 1 o0 <AB,0n|~l26ޘn%% ^A!")+0,sٛ-L.3/١0ou12i3c4Z5N@@QAGBFاCFDIdEPFRGNOHI(MJ_uKԪT<VUCVBիWBXEYYOZN[J;\])+^T_0׮`=a8Db,|c6diޯgnGynz%#{H|}Ҳ~_pPvd{}[AHa&E>a d Fg]E; `/0,_ZzzPtZ;6tn?1aJo=OWJ<c,)x\0y"YZ[=\?O]L^>_$`o<abUBc_d\eRf,g(AhiijkdlmnoXp%x-.Wd*AYH(*pa/J*Dt<`TdS;kjscsj6#?6DuJeD P*c& w  w P3 q  j r Y{  M !!"A #IL$%7&kN'(G9)K*M+@,<X-.R/0)1;4kel7mnWXop2c]!e s"~"w# $$DX%%b&z~&&* D'V'(((()k)pV**+(,z,,-.;/=0.11[2pb33`4L}t7M7O8Pg 9Q[q9RG9S:T:Uc;V;Wt<Xx4=Yo=Zm>[>\>]1?^q?_F@`~@aEA~SAnGBgBmCCDD~CE+E.FJG)dG-G:G6G%*H5OH1H-H'H- I )6I!*_I"9I#=I$7I%)6J&_J'6J(0K)+IK*2tK+"K,9K-$L.+%L/+PL0+{L1XL2VL3ZTM4;M5:M6&#N7IN8:N9JO:<RO;DO<?O=AP>5RP?:P@(PA/PB.QCCFQD$QE+QF*QG(RH#*RI)MRJ3vRK3RL0RM7 SN7CSO(zSPSQOURWSXTmZU\V4]W* ^X.J^Y=x^Z?^[*^\,_]-J_^2w__4_`,_a4 `b)=`c*f`d`eQafbgbhci[djekelfmTgn ho/hp3hqT ir+]is3iu*iv)iw*jy8jz$k{k|l}sm~inoopqqqr{r>1sot&u.vvw7xxyz{B-|C|D~ :>x)- 7Pf~l'مΆ ea ƍ N e: E# $ X% m& p' ( |) * O+ 3, - 10. a/ } K 5H } J ; L* v   j1  !f +( 7) * w+ ^\, t- 5.. c/ {0 1 1 ,>2 &j3 4 -5 kŶ6 07 %8 0շ9 n: zs; ,< /= MH> *Z q[ 0 b, u 5 98 q       } m  %z x  R  o! *" C# %$ % L& p' *B( gl) }* NP+ K, k- T. / 0 1 2 y!3 t4 5 6 d7 s'8 9 ;: ; < 4= P> j? m)@ A zB SC j&D E {F x$G IH I dJ O K [L qM XN 3O :P NQ V0R S `T 0U V W EX Y ~Z }v[ ~\ q] ^ _ r` a b 2c @d `e f wg h i 3j k Xl m }n .o p Xq r s |"t u 5v Hw O x \ y z { (   ]  9 R @ C  R 3> q f Rt P   2 _ c2 &   " w# % % v( * , , K. e. v40 0 n1 }:2 L2 4 4 [5 5 6 7 J8 8 k9 ); 7=; jt; ; w< x= z= x= tr> h>H ]N?I Q?J ?K a@L ^@M N>AN XAO AP tBQ o CR Z{CS UC V*D kD UD @E E YbF `F UG UpG ZG _H S~H ^H /I TIJJagKOKbLyLb.M\MzMtfNuTGOvPwQx`Ry&SzT{T|hyW\Y=ZhZ:[|[a;\\RR]]=^__(|_m_)`j:`0`1`/a/4a(ca,a!aEa%b"Bb:dbGbb%c<")c=Kd>e?ye@_QfAfBdgC=hDhisOjljm.kik{llmOmnnenn|opp{DqqpGrrZQss:tnt0uubv0wuwRxlxFyzzsY{{vS|m|X6}}~pfrw\}Z_ۅ\:my|-\PzNʉi{ +g<uߏT1x+m8p%pr {'rQÚF՛[ߜcw_v w1={Rͣyufp)֥1htsx013u2}3 %415~/67Jh8J9:;<=C>?\@AtBCD7E;F0GHfIeJuKM^N}OW(P]QU81kif]:c`WZdaYvNRHoh67|m`IL|K;'<a $\ +J;O IXFHK/z}#g3Do/$<BW x^.4@CtE s\8tcVa^mHyLY@^/Z'04+0,G2s--5/42c2*(  H Im0(P}I1@zIWSZT> : e 1 $ uy vK$,U%&)*9x./m3j<@cI  )!="X"I$8% %&'G( )/*-G+t-c.Z/n0W01_142J3d3X3g?44b5c5[667#88`l9:];$<= =>?A}ABCcDIEaFbGBH,J_KwLMNO QR3S$T1U^"WX iY zY ~Z ~Z M[q][?[# \E0\Du\H\X]Y].V^ E_!7`"e(qeUf<ffgOhhi>jNkkmn@oppq=Mr0sVuzxyz3{{A|Qt^Qp*>dZ'HVߏZmǕ88BB;d}'`7]k{Ra͠.f"2N+yV+֮ t a EN  pi JSML!]~/{Z0OB v!`"R?#$d%x&x'*(+)=*+4,-./7012(3456U:7ostwx?y zb{J|}6~JkA-tTRXu9p p J7 > yQC  y`S*T>a  - !'" #%`&rq'(6)+ ,5,7-9.:y/A[0B1C?2D<^3E3Fne4G+4H?5I^=6Js6Kc7Lq7M7NC8O89@+{AD=IlXJK}LAMGMAPQR~SxBTTUVWaXPY6Z[v[8\p\ S] ^ `^ ^ ` b 3c Ic Hd \d e e Af f g h i Tj mHk k qNl l S\n o p! Rq" q# tr$ iFs% ps& bt' ht( Ht) 1v* Qv+ =xl x y 3{ } ~4!115!b6!D7!8!9!C:!;!!rً?!K@!ތA!B!xC!sD!E!ǐF!]G!IH!NI!AJ!LK!-L!cM!CN!ۗO!lP!Q!PR!LݚS!L)T!ouU!V!W!PX!nԝY!BZ!/'[!NV\!]!^!_!c`!Ea!+b!c!d!Ve!m,f!ch!k!dl!R m!b[n!p!,!ϫ!v!h!ll!ح![|!׮!e!t!}\!ٰ!_\!1!3!3!1R!!l!i!m!f!"\!a~!dߵ!wC!}!v7![!?!G!!`"&a"|Cb"c"fd"e"lf"~$g"h";i"j"k"l"L5m"n"o"p"i>q"r"t-s"t""u"v"Nw"x"yy"z"{",|"}"O~""lO""c`"""i""|""e"k"o"-s""%"h"}E""@Q"<""y_""r"2""~"""U""ae""kc""l"/""?"0'"W"v","="#""h"&"3-"q`"|">M"[":"i ""U""j"r)"*""$M"q"p""z"G"C">"""q8""\"#x"G""d"S"^L""#"="%"M"\#(#)#h#,# # #S #Y7  #2 #( #+ # #p #G #" #, #q #$#A#(#*D#Nn#/#+#( #>!#"###I$#%#&#Q'#I;)#6*#[+#,#-#53 .#Ch /# 0#1F"1#w"2#a%3#x&4#tL'5#)6#VX*7#*8#+9#m&,;#e-<#N-=#F.>#XA/?#50@#1A#Z2B#=3H#i)5I#6J#{7K#_8L#L4;M#<N#,J?O#v@P#>AQ#*AR#CS#DT#qE[#E\#5G]#@G^#RJ_#bK`#iLa#XMb#uNc#&Qd#Qe#Rn#cSo#yTp#rTq#Tr#kUs#5PWt#Wu#o;Xv#Xw#.Yx#Yy#j]|#]}#^~#_#`#Kmc#{d#3e#e#f#Hg#Xcg#eg# h#2h#h#j#mj#lk#kil#Ol##m#m#'m#m#1n#n#Gn#"p#7p#q#q#r#0s#1t#tt#=u#Lu#Ov#Ihv#v#v#Rtw#Qw#8x#%Ox#"tx#&x#Mx# y#M&y#%sy#y#@z#AXz#z#{#{#|#u|#}#w}#~#~# h##U$p$xU$́$yU$g΂$|5 $E $ $΅ $O$o4$$~e${$p^$Ή$X$$$i#$$#$}΍$K$vԎ$BJ$h$C $7!$oΐ"$=#$Ǒ$$ϓ%$u&$b'$g($)$*$M^+$N,${-$rt.$/$~m0$1$՝2$7$K8$9$:$;$С<$=$x>$1?$@$yA$*B$%ḩ%[4%%#%|%;%|ԫ%P%Ѭ%%%%֮%%%%`%l %dy%ݲ%&rE&&ϴ&T&޵&]h&`Ŷ&)% &N &% & &9''ι'c'''t''u''']'''m$'Y%'iH&'c''Q('re)'f*'g=+'`C'HD'ZLE'FF'VG'KBH'JI'gJ'=>K':{L'fM'aN'K|O'4P'YQ'VTR'IS'QT'aDU'LV'tW'LeX'vY''Z't['Q\'Nk]'I^'7t'9u'T<v'w'Tx'y'rz'{'Z|'V_}'~'R'' ''6'O'[.'' '%'6'H'''J't';W''B'#''t''']Q'e'a'{t'c'6R''R,'H~'u'i;'?'b'`E's'J'Fb''d1'='g'K9'q''N}''S'L'[H''uT'm'\6''|''j'H'&'''D'},''g'Y'`'s;''u3''c'n 't''O'4'N'J!'Fk''J 'X 'd ' 's 'i9 'J 'H '4 'V'iX'{'x<'_'p'.'J'''@'P'LN'c'P'M'z'J''Z'v'b'''S' 6'-V']'/';<(lJ=(O>(^?(Pc@(QA(g(k(a (d (!(!(h"(#(#($(%(,&(&)p')?&()e()))R)6))C*7)ml+8)+9)^-:)b7.;)Y.<)P.@)B/A)/B)o0C)1D)1J)42K)2L)Lh3T)3U)V4V)4W)x5X)$6Y)6Z)f7[)R7\)hI8])G8h)8i)9j) :k):r).;s);t)t<u) =v)=w)7>)>)?)@)hA)A)B)XC)>D)D)$E)F)vG)u-H)wH)tI)I)-J)J)K)L)M).N)N)dP)zQ)%Q)Q)LQ)L$R)tpR)`R)ZDS)LS)S)~T)T)U)V)V)7W*W*RX*eX*UFY*Y*LZ0*aZ1*J?[2*A[3*t[4*+>\5*&i\6*M\7*&\8*Y]9*`[]:*];*O]<*"^=**<^>*cf^?*^@*ZR_A*e_B*2`C*3C`D*Lv`E*`F*$`G*aH*5aI*aQaJ*MaK*CaL*BBbM*bN*bO*>b*b*Kc*w]c*4c*]d*Med*Qd*je*Qme*be*H f*Ahf*gf*h*h*Hi*$k*{k*sl*oBm+m+o+,9p+ep+p+Ap+$p+jq+Glq +@q +q +r +s +jt+Xt+Tu+Du+$v+Ov+Qw+SXw+Vw+Nx+MOx+Ux+8x+6)y+0_y+Vy+Sy+U8z+$z +$z!+Gz"+{#+9{$+Y{%+N|&+k|'+$}(+#B})+Me}*+}++},+Ni~-+~.+5j/+y0+31+5K2+n3+4+K5+6+"7+!8+39+TA:+;+3<+$=+Z >+d?+_@+A+B+DC+?D+N E+@nF+@G+6H+$$I+HK+U\L+JM+N+@O+HUP+9\+3֊]+< ^+#E_+'h`+.a+2b+c+ d+%e+Bf+BIg+h+>i+.Lj+zk+ll+:m+/n+3o+'$p+Kq+r+Ӓs+t+^u+!v+w+x+ry+?z+Q|+,S}+~++X+@$+:d+{+R+ek+.П+O+ZM+2+3٠+& +12++c+0+++++Q+ +Ǥ+*|++++|+V4+(+(+&ک+K+ K+k+$+#++ѫ+++R7+R+J۬+J%+$o+,+$+3++3+CR+#+?+B+G9+G+ǯ+^+p+c+s+He+s+G +Yg+g+i'+++Zõ+n+n+`+Y++j+p +y+6+Ǻ+:P++N+߼++v+yt+X+E,a,gK, ,A ,| ,X ,j ,H,H,_*,,u ,,,q,G,Z,jQ,,d,,,w-,,y#,$,',:(,F.1X.[..Qs..V.m1|.}.~..B#.e.!.K0.{.U_..=.>.D...Q+.|.wx..+u..&.0.E.TZ.p..c/....W..D.,X./p/\w/7/? /lI/Y/%/3/\ /6 /7R / /! /R/'/&%/-K/x/K/Y/k/u/;/2/^/</=/R /08"/4h#/F4/J5/D,6/3p7/$8/D9/O :/aZ;/K/K?/.@/W A/\bC/3D/KE/&<F/9bG/)H/#I/"J/0 K/?9L/(xM/>/I/H'/:o/O/Y/NQ/O/O/U=/7/7/8 /;8 /:s /; /H /c0 /N /> /K /Mj /M /L /<P /= /< /, /-1 /$^ /3 /7 /; /$'/VK/>/+ /w/;7/Dr/B/2/*/2/L/2k//</5/G'/-n/1/I/I/[^/G/7/7/C/AQ/@/:/< /9H/?/7/>/*5/1_/6/E/_ /Cj/V/@/C/J/qg/>/</7R/:0n0N10c010a04tN0O02 P0y Q0/!R0!S0yG"T0"U0A#V0~#W0z?$X0p$Y0~)%Z0%[0+&\0|&]0','^0@S'_0)'`0n'a0j*(b0o(c0i)d0l)e0v)f0p*g0w*h0rv+i0q+j0zY,k0,l0]-m0-n0t.o0m/p0As/q0K/r07/s0<60t04r0u040v060w061x0&F1y0Dl1z0>1{0-1|02}0F92~0(20E20>20O*30@y3030&Z40 40s405050,60|60x*70r70r80l80~80p90s90yk:0m:0fQ;0>;06;02+<0)]<0)<0"<0<<0# =050=0:e=04=0>=0%>1?6>15u>19>1@>1<#?1*_?1/?16?1? 1= @ 1/F@ 1&u@ 1&@ 15@1:@1:0A1jA1A1+A1CA11B15@B1/uB 1<B!1FB"10&C#1)VC$1)C%19C&1-C'15D(1&CD)18iD*19D1vD1PE1@E1:(F19bG10G1G1{H1"I1hI1h3J1hJ1'K1'*K1QK1K1-L1L1M1N1LO1LO1Pf4]l4m4~n4_p4oq444444[44Kړ4%4kЕ4<;48w4c4h4Hz4˜44Qw4Jș44m4;45Z4~4 4c4^4SW4V41414N4=4=4U4q444#44?4744~4M/5|5p5D5=5{5|5((5BP5 5U 5ԯ55HE5p555q5)L6mM6UN6fO67]P6Q6R6zS6kT6>U6*V6W6SX6Y6{Z6v'[6)\6]6]Z^6_6Y`6|a69\~6]6^6P666696x6[6]6W6m666i6r6i66D666b6664F6z666Q6DV66&6I6666i6Y66g6K6:6{Y66{r666y\7l7A7 7F&73l(7 )7.a *7> +7 ,7L <7 =7 ?7F @7 A7{ P7Mw Q78 R79 d75 e7 f7BA x7 y7N9 7s 7 7 7 7y 7l  7y 7^ 7v 7` 7>g 7 7y :! : : :b :/ : :z :c ;! ;# `;8# a;W$ b;]9% c;m% d;& e;& f;O' g;' h;B( i;( j; ) k;<+) l;<g) m;) n;) o;bZ* p;* q;Z+ ;y+ ;5j2 ;8 ;p: ; < ;M? ;HB ;NC ;FC ;FCD ;OD ;E ;zF ;+G ;G ;H ;~I ;kQJ ;K ;L ;sM ;JN ;KO ;RP ;%Q ; R ;R ;_XS ;T ;[HU ;V ;hvW <X <]Y ([ L =><k >>@ @>+ A>0 B>7B C>Cy > > > ># > >ٛ > > > >-ٜ >> >=D > >> >D؝ >3 >O >k >' >5 >6 > >+1 >=\ > > >/Z > >~ >? > >+ >+ >,) >U >Y > U >u >, >2ۯ >7 >6D >Mz >dz >Q ?, ?3 ?3R ?$ ? ?4 ?0 ?<" ?^ ? ?&p ?% ? ?ط ? ?O ?a @ @ @>6 @t @f @< @4 @ @' @b @Gj @G @ @ @ @3` @ @J @ @ @L @4 @ @J @Rh @ @7 @] @F @G hBtP iBf jB* kB lB; mB+X nB. B> BF BW5 B Bs Bp 0Cp 1CC` 2C 3CS3 4CX 5CY 6C\7 7CV 8C] 9CWF :C $E %Ei &Ej E% PF25 QFg RF SF TF UF% VF WF XF5 YFR ZF"n [F! \F4 ]F- KG1 LG!C MG(d NG% EH& FH* ?I @I/ AI"L 8Jn 9J. :J+ ;Ji JC ?J< @J.+ AJ8Y BJ2 CJ< DJB EJ~A FJ. GJ) HJ1 IJNG JJ4 KJ' LJ/ MJ, NJ'K OJ'r PJ' QJ' RJ' SJ TJ VJ WJ XJK YJ& ZJB2 [Jst \Ja ]J2H tJz uJZ vJ` wJ1 xJAF yJ2 J J?_ J* J. J J JY JT JT0 J5 JU JT J=b J< JD J: J2Y J= JR JB JW\ JV J^  J9g J) J* J JH JQ J2b JA J4! JI " J_R" J" JB# JF# J!$ J2>$ JHp$ JA$ J>$ J7% J#& J)#& J7L& KG& K2& KE& dKA' eK:%( fK@_( K$) KA) Kl* Kp+ K+, K)?, Kh, K'K- K$r- K5- K. YL/ ZL40 [L=60 \Ls0 ]L!]1 ^L*~1 _L31 `L71 aL+2 bL-=2 cLj2 dL2 eL$2 fL2 gL)2 hL) 3 iL(63 jL^4 kLz4 lL$4 rL&4 sL4 tL%5 uL6 vL6 wL7 xL8 yL(F: zLzn: L'; L(< L*7< L(a< L(< L!< L< L< L = L`+= L\= L`= LXG> LW> L> L?? L4*@ L^A L6eB L>B LAB L0C LJJC LD L)E M;E M;F M%MF MrF MF #MF $M3G %M4G &M:G 'M62H (M9hH )M8H *M9H +M:I ,M9LI -M>I .MGI /MF J EMBPJ GMBJ IMBJ SM,K TM*BK UM*lK VM+K WM/K dM5K eM5%L M5ZL M3L M$L MlL MRN MN MP MP M.Q M R MPR M+R MBS M'WS M'~S MS MS M:S M4T M+IT MtT M3T MIT MG U NTU !N V "NV #NzW $N3X %NrX &N84Y 'N`lY NY N`Z N[ N[[ N\ N] N>^ Na^ N._ N__ N7` N}` NS=a LOSa MOTa NOT7b OOUb POVb QOZ6c ROYc SO^c TOVGd UOd VOBe WO[e XOf YOf ZOVg [Oh \Oh ]Oa`i ^Oj _Ok `OWFl aOl bOWPm cOm -Pn 3Pn zPio {Po |Pp }P"q Pq PKr Pr PWs P:t Pt PLu Pw Pw P;x Py Pz PPy{ se| ?s3| @s/&} As^U} Fs?} Gs8} Hs6*~ PsL`~ Qsp~ Rs> Ss>Z Zs# ds; esI fs'? gs&f hs* ns os<^ ps@ qsxځ rs<R ss? {s`͂ |sg- }s@ vԃ v v| vy vx v< v v v vs v v$ Px Qx Rx'4 SxI[ Zx5 [x3ُ \xK ]x;W ^xJ _x,ܐ x9 x.A |yo }y# ~y. yL yH y yv yr yE y[Ц yj+ y y yHk yP yN yQ y y^ٰ y7 yܲ y y + ye y# y) yz y y y{ ymg yԻ y yr) y y y y[@ y y71 yh y y y y3 y y y y? y y yR y y y y y y y y yc y y y4 y} y= y y y" y y^ y y yy# y yg yJ yO y] yF_ y> y4 yI yr` y] y/ y0 y y\ yK yW< yl yG y(F yn y y y\ ylj yB yE yK] y; y7 y< z0V zE z. z> z>7 z\u zj DzX; Ez FzsD Gz Hz Iz Jz- KzI Lz Mz Nz4@ Oz9t PzW Qz  Rz" Sz/ Tz Uz z*t z/ z9 z= z5C z-x z zr zB: z4| z) zx z=Q z3 z z/c z/ z z zk  zt z zt zu zq zv zdn zC zN z@c zJ z[ zDH zR zL z:* zd zK zYB z\ zW zuN {? { {S {K {a_ {= { {z  {Q {P {& { p{2 { {Q {" { {7 { {? { { { {` {, { { {o {oK! {o! {r)" {i" {y# {s}# {# {qo$ {|$ {\% {p% {jW& {& {L' {' {c( {( {kr) {r) {O* {w++ {r+ {, {l, {l- {~q- {z- {i. {. {/ {0 {:2 {5 {5 {{6 {_7 {7 {~8 {r9 {,: {: {b< {eb< {< {G= {= {> {? {w/@ {@ {#yA |YA |A |B |C |tD |0E |E |wVF |F |WG |wG |x^H |oH |yEI ~WI ~WJ ~VlJ ~VJ ~\K ~tK eL  L N N prO O P UQ Q R yR 0R R R S ##S 'FS &mS 6S 0U $U V 9V 6SV QV @V W +W W KeX UX Y Z !$ Z "@DZ #Z $ [ %\ &\\ 'J ] (U] )K] *V#^ +-y^ ,^ -2_ .Y_ /o ` 0z` 1a 2a 34b 4cb 5ac 6v}c Fc 9d d e i+f nf g Jg Sg B@h Th h @_i ARi BjHj Cj DMk Ek Fl lm Ym Pn n do Vp q \r s t Yu )v Qw fx }y T`z | -} ~ " #} $x ,x -Z .e 66 7؃ 8 9f : ; <u = J K-Z L |4 i o u h e & '< c ] 5g ^   g s f H  ʙ r` Қ q V QL j {  N ͞  y !6 "̡ #X $ AO B2 C? D;[ E2 FSȥ G6 H:Q I2 JA K? L2= M;o OR P1 QB- R.o SS TY U\I VZ WJ Y6I ZI mȪ nMë o p q"2 sgT t u@ vұ w xy y z {o |b }j ~L TO m i fy 㜇߹ 䜸f e  蜧 霉8 Ꜹ y ll` m. n= o}7 p& q' r s< t3Z uZ v wKz xF y8 zIC {8 |- }( ~- 3F 8y 1 2 9 4M 2  3 4 A2 Cs > @ 4 9 :) <c N 9 >& 9d + ? ? HF 3 # ? e# Q -= (j ) * + ,' -/ . " /B 0Y 1<q 2, 3. Z$ [$+ \#O ]r ^ _ `# a) b+ c1@ d,q e f g h i! j k68 )n * ! # * %/ #T w + * * # ", %N 's ! "  + .& "T $v  ( '    à9 ĠT Šr Ơ) Ǡ) Ƞ( ɠ ʠ' ˠ8 ̠$R ͠$v Π# Ϡ Р" Ѡ Ҡ' Ӡ?4 Ԡ?s ՠ$ ֠ נ ؠ+ ٠; ڠ3V ۠: ܠ%  #( K j  % 3 " # $1 %"M &o ' (' )& *& +' ,&B -h . / 0 1 2 3 4)= 5)f 6( 7% 8% 9$ :$% ;$I <m = >" ?+ @% A% B ? D!_ E2 F" G H I$ J*3 K#] T# U V! W! X Y Z0 [F \b ]%| ^# _" ` a$ b$' c#K d"n e   . ( 3= p +   7 8K   2 8 % @ ] $w      # !> _ "|    "  -/ ̡\ ͡+y ѡ ҡ ӡ ԡ'  #3 V !  « ǫY ʫ ˫ ̫ ͫQ Ϋ ϫ ѫ ҫ[ ӫ ԫY ի ֫ ׫t ث ٫v ګ5 ۫v ܫF ݫ ޫ_ ߫ ]{ . - 83 )k x c  Go } ꫸3 c QN b  [ d ~t p b I h>  O ] AN oe T 8  c j zl   z < ^5 S V < U f     L7  ! P PI Y  s  d [  U]  A !! "M~" #" $$ %% &U' '\( (\j( )Y( *) N[) OO* Pp* QMI+ R+ S//, T_^- U*- V . X/ Y1 Za1 [1 \x2 ]3 ^3 _B4 ``I4 vE4 w>4 x<,5 y=h5 zC5 {$5 |> 6 }5J6 ~16 G6 ,6 B#7 )e7 7 z 8 8 )9 e9 q: : ;; < < = = 9> o? lUA aB #"D EE *F F Z=G `H I J K K |L vM M ON O ¬O ìZ0P Ĭ(Q ŬR Ƭ5S ǬS Ȭ|T ɬ7U ʬ>IV ˬW ̬dX ͬG h8 iÏ jL kÞe lS mbV n om pï q. r=ϲ s tZ u|W vYӴ w=, xèi y& zS7 {ú |D }. ~û(    'ɼ B Ü2 ôν Æ À È z Ú &$ #J !m ) # %   !; h\ f ,* 9V J '   = \ "z  % %  .# /Q ; ; @ V6 K H $ _C ē o5 d h īp f !a "ē $kt %i &ěH |3 }5 ~MK / 9 ` s` s ĕF [ m6 N ^ QO : Ă F\ Ė T8 Ā 5 ħA Q Ġ9 R B+ \m u ģ> č Pn DŴ EŤr G H1 Jŧ' K L M b N  OŠ Y + Zz4 [/ M !* "- #ˎ $ˮ %\ & 0 ':9 (fs )˲ *: +z ,W? -s .F 5˗O 6e ;K <ˢ( =e ?3/ @kb Aˡ Bjn C˶ D˔ E˕" F? G˵ H˜ IUG Jp Kp , LS| M~ N{M O˫ Pːs Q R+ S˟ |˴ }lT ~% ˩ ~ (  ^4 e 8 / 4    ( G ˸L ˒  ^ L \L ( R M C* ˟m L  JX     ; '7 (Q ,#k ] a! e! f/ g& h< iiY pZ qE r:a s? t7 uI vTZ 5 6 _ Dx 1 W bD O 7 [, 2 ] U Rk V q ^  4 1+ 0\  & 5 ) *% φO - 5 U7 : Y U Yt / F B a $ M 3 W$ I{ ] ]! 1~ ] 7 ! &C! i! ϒ~! ?" 3O" 3" !" K" s!# $# I# $ +$ +A$ Kl$ I$ =% V=% \% O% 6>& 4-t& 5*& 6N& 7( 8е* 9* :U, ;в, <- =Бh. >Њ. ?(/ @Ћ0 AO61 Ba2 C3 Dк4 E5 F^f6 Ga7 H%9 I: JЮ ; .; ,; L< *`< ,< *< *< x = .= $= *= $= U"> .w> c> *? +2? )]? (? *? )? (@ ؏)@ 0@ 0@ $A 7D ۈF G G H WI BJ ۀ!K QܟK Rܟ@L SvL TeUM UbM VbN WR~N XRN Y^"O ZeO [FO \E+P ]LpP ^KP _HQ `JOQ aLQ baQ c[FR d]R eFR fSDS gtS iZ T oKeT pST qLU rQOU sRU tWU uVIV vKV wXV x[BW yWW zdW {_XX |KX }aY ~QcY OY ZZ $]Z XZ HZ H![ Hi[ F[ J[ HA\ D\ G\ C] LW] I] F] E2^ |nw^ }^ ~d_ ݷ{` ݼ2a a b |c p'd ~d re ݡf Y(g ig ݉g ݙsh ݪ i ݁i ގ7j ޑj tVk gk L1l K}l Cl _ m jm om ߀Xn Zn I2o <{o fo Wp %gtq 'ߋq (ߋfr )nr *߅_s +{s ,{_t /Zt 0V4u 1pu 2Xu 3>Rv 4v DJrw Evw G2x I/y NR4y Oty Ry Sz T{ ]`| ^߻| _X} `ߔ~ ci~ d~ eD f gD> h@ iB€ jߪ lr nߟ pQ q/ r>? sd} A =" /_ 5 NÄ O @` A C A$ Ve ? 6 B0 Nr $ A V% ;{ 8 @ l. ) BÉ B FG _ F W2 = 6Ƌ { w V@ ߃ ߢ G E ߅G ߻̏ u * \& > ߞ B^ 2 ?ғ K B\ - 7˔ ] 0_ ' 8 \ 7J x . 4' D[ 0 "ϗ 4 2% 1W 3 .  am dΙ c2 c 8 9 :( ;ƞ <o =z > ? @7 A}̦ BdI Cd D E FM Gl H\ I Jp K L϶ Mʸ N O PU Q- dyĽ e= hXξ i& ji kg nCx qt r|/ s vs= z {c0 ~ ~ f o m u> o l" u c j pb \ I. !w & i 2' yY / ; @< A| e ~" +1 k\ o |6 | .  x7 n  ~ x {( 8 & x 7 S o 2 o a p p` & _ _U l  d ( XI Y=b [V \5 ]* ^EH _ ` aS ck dn e[v f g h`U iB j k l_ m n ol p qF r s@ t A l!u"F#J$T%p&R_'R(r)Tu*+vd,h-B./P0R3{Q4!>6 ?#@dA%BR]ST>UVWK+XOvYMbcadsRefngWAhkirjJuk=lmmainLo_pTuqnrv7sltnupvpwtgxy]z{i| }m!~kn!O!("!"#{$$'E'&$)J+../ 001j]2u2<3FB3L4M# 4N"C4O!e4P4Q4R!4S+4T# 5Z+.5]Y5^Uu5_&5`#5*65=6!r6*616#6)7-:7!g7"77777 8$8A8 _8!888!8-8''9)N9w9!9+99%9 :%>:c:::%:):$; +;'K;Br;0;:;<#<<0_<.<!<2<$=4=(M="u==&=+= >!!>$B> f> ^? Z@ ,bA |B DEtFJGOHzI;hKYKK |LMzNlOPMQEDRS h%T!TT"sT#TUl Vmo+WnmWomXpjtXqnXrLYsYtgZu#[v[w\x]y]zV^{?_|_}j`~TaXagahbi{cjxdkwdlemuengo^gp^gq\hr}is~itjujv`kw[ lxXely\lzJm{Hcm|Im}Vm~JnBXoooW p`pA=q~qBrZYrMr)s)s*tt=uFuv8vv= xGx`yby~/zzv{{w|T}}fm~a~]4DIzLƃYwЄ3jyQ ʈӉWs  $  R eLĖ<g[  J S /q:|' g!V"p#,$I%'&t6./8^9:0LM|PNfOj2RTUVWXYZd[_\W]^b}c efvg&hijklmnbo"pqxxyz4c@@F{GEE5z/wm,~D34|579jUd)enfnVg\h ilj0klhHmnq8t"u x7 y z  {|b}A~WL) o' General: OK. Successful completion.General: 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. Many conditions can cause this status code. It is often caused when an interrupt application returns, leaving its interrupt in-service. This can be distinguished by the crash dump analyzer reporting the crash in the backgound process. Make sure that the SetIntHandler(fDevice) parameter is set correctly. Also make sure that interrupt routines complete EndOfInterrupt processing before returning.General: Operator intervention. The user pressed ACTION+FINISH.General: Syntax error. The user entered invalid data to the application program. A variety of conditions can cause syntax errors. Check for the following:  Entries that do not follow 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 nestedGeneral: Server not running. Interstation communication with the server of the cluster has been interrupted. Notify the system administrator.General: Not implemented. The procedures necessary to implement 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, WriteBSRe, cord, 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 in 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.Kernel: Exchange out of range.Kernel: Invalid pointer.Kernel: No link block. Generated by PSend. Possible causes: This error can be caused by an application that sends messages, but is either too slow, or fails to respond to the messages queued when the message is exchanged. This error can be caused when requests pile up at exchanges. This could indicate that the system is too slow, or the system is overloaded. This error can occur when Request Tracker is left on. Request Tracker doubles the usage of Link blocks to perform its task. Corrective action: Use the debugger to find which exchange is backlogged with messages. To specify more blocks at system build, increase nMsgWait. The number added to nMsgWait in the .asm files is 128. This can be safely doubled to resolve this problem if indeed the system does encounter periods where it is busy and has trouble responding to messages quickly. For more information, see the CTOS Procedural Interface Reference Manual. Kernel: Invalid interrupt vector. Generated by SetIntHandler. (For information on Interrupt Handlers, see the CTOS Operating System 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. See the System Administration Guide for more information. Kernel: Inconsistent request block. Information provided in request block does not agree with expected values.Kernel: Mismatched response.Kernel: No process 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. (See "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 words are Code Segment (CS) and Instruction Pointer (IP) when the memory protection fault interrupt is detected. (See the Fatal-Error Message explanation in the "Troubleshooting" section, 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 code. 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. For an example of a bus timeout on a workstation, see the Workstation Example in the "Troubleshooting" section of this manual. 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 contents 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 include:  An I/O port fails to respond (by sending a transfer acknowledge) or a nonexistent I/O port is referenced  A nonexistent 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 incorrectly and thus SN:RA is meaningless (For an explanation of fatal errors, see the "Troubleshooting" section of this manual, 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 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, and a bus subordinate when its memory is written and read by the bus server. 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. For an example of a bus timeout on a shared resource processor, see the shared resource processor example in the "Troubleshooting" section of this manual. 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  Hardware 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 are 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. This typically indicates a hardware malfunction. Use the PLog command to check for additional information in the SystemLog. It is also recommended that the memory diagnostics be run for a few hours to catch intermittent hardware errors. 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. 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 contents 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. 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 resource 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 poi- nter (IP) when the nonmaskable interrupt is detected. The error condition causes termination of the operating system and an automatic reload. (For an explanation of fatal errors, see the "Troubleshooting" section of this manual, 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. 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, and 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 indicates the type of interrupt that the processor has attempted to service when no actual interrupt condition has occurred. The problem was probably caused by an invalid program jump to the processor's low memory interrupt vector table. A hardware failure could cause an interrupt of an unknown type.Kernel: Divide overflow. This error often results from 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. (For an explanation of fatal errors, see the "Troubleshooting" section of this manual, for the interpretation of operating system crash status 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 following 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 zero (port 48h).Kernel: Math coprocessor not present. A floating point instruction was encountered that cannot be executed due to the absence of the numeric coprocessor 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 cases, 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 how 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. Possible causes of this problem include:  A service was not installed locally or at the server 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 client workstation. Check for the relevant run file to be certain that the service was installed into memory, and on which processor it was installed. Also, 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 device position. There is no EISA/ISA bus slot or X-Bus workstation module that corresponds to the specified ID or address. Shared Resource Processor Kernel: Wrong file system overlay. Kernel: No such bus. The specified bus does not exist. 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 a real mode program then attempts to call MapXBusWindow. Therefore, if you are running a real mode program that will call MapXBusWindow, specify Yes for this parameter in [Sys]Config.sys. Pre-CTOSII 3.3 operating systems: The operating system read beyond the logical end-of-file in [Sys]Config.sys, to the end-of-medium. Any valid tokens after the end-of-file overrode the previous tokens in Config.sys. To correct this problem, after editing Config.sys, add 7 blank lines (560 characters) to the end of the file. Save the file, then delete the 7 blank lines.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 cluster buffer memory. Initialization error in server. 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). The local CWS Agent Service Process does not have an RCB available to process this request. Specify 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 Agent cannot handle a user-defined request block of this size. Check the total size of the requests being issued.Cluster Request Management: Invalid response from server. The response from the server does not match the request. 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: Unmatched response at server Workstation Agent Service Process. Probably a message was erroneously sent to exchange 12 at the server. 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, BNet II: Request block too large. The transmission buffer or line buffer cannot handle a request block (with data fields expanded) of this size. 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. BNetII: BNet II.: Increase the X block size on the server or reduce the [Size of Large Requests] parameter value when you load the Net Agent and Net Server.Cluster Request Management: Server going down. Polling of the client workstation is going to stop.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, Mouse 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 attempted to unlock it.General: Bad handle. A process attempted to remove an ISR that it did not own.Kernel: EISA/ISA bus slot empty. The specified EISA/ISA bus slot does not contain an identifiable EISA/ISA card. 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. BMULTI: 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 the specified channel does not support split baud rates (different baud rates for receiving and transmitting), 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. The 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 applies to miscellaneous parameters 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. The system also returns this status code 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 expansion, 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 channel.General: Bad CommLineDmaStatus return block size. The CommLineDmaStatus Return Block, in which the current transmit and receive counts are 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 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) specifies DMA capabilities, 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. General: 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. The descriptor table must contain an entry for the selector that was loaded here. 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 checks. 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 fault results. Faults transfer control automatically to the operating system fault handler. Non-system service programs exit and load the exit run file (normally Exec.run). The system will crash if there is 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 cannot 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 the passing of, for example, pbPassord = 0 and cbPassword = 0 in an OpenFile call. Although you can use 0, do not use the value to calculate an address. Additional exceptions, for example, limit exceptions, can occur later when using a valid segment register in an address calculation. A limit exception occurs when trying to address beyond the end of a segment.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 present 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 systems with 80386 or higher processors. 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 an 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 a processor with 80386 or above. General: Math coprocessor overrun.General: Double fault. While trying to invoke a handler for an exception (fault), the processor cannot handle a second exception. Application programs are not expected to generate double faults. Therefore, a double fault is probably caused by an operating system or a system service error.General: Operating system stack overflow. The stack of an operating system process has been corrupted.General: OS interrupt consistency error. Protected Mode Operating Systems: Fatal error. The operating system detected that an interrupt application ha. d returned, leaving its interrupt in-service. Make sure that the SetIntHandler(fDevice) parameter is set correctly. Also make sure that interrupt routines complete EndOfInterrupt processing before returning. In protected mode, interrupt routines can use RET instead of IRET to let the operating system do EndOfInterrupt processing. Real Mode Operating Systems: 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 mediated 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 mode 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 procedure 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 failure was detected during initialization.Initialization: There is insufficient memory for operating system initialization. This can be caused by too much software on the server. 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). See the PLog command in the CTOS Executive Reference Manual. Shared Resource 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. See the CTOS System Administration Guide or CTOS Operating System Concepts Manual for more information about Y and Z blocks. Shared Resource Processor Initialization: Insufficient 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. This error can also be caused by 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. The System Administration Guide contains 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 the 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. 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 position) 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 as follows: :Processor:Default :ClusterLine1: (Speed = 1.8M) :ClusterLine2: (Speed = 1.8M) See the System Administration Guide for more information.Shared Resource Processor Initialization: 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. See the diagnostics or Visinostics documentation.Initialization: Bad Sequence Error. The requests by one processor from another processor were out of sequence. This error indicates that operating systems running on a multiprocessor platform are not synchronized. Initialization: Software incompatible with hardware. The software installed is not compatible with the hardware. For example, you may have attempted to install a system service on a module or CTOS I/O Processor card that does not support that service. 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.Initialization: Bad sysgen tables. Incorrect information was inserted into sysgen table. Initialization: The XBIF service must be installed before this run file can be executed.Kernel: Interrupt cannot block. Erc 130 indicates a programming error. An interrupt handler called Wait. The system crashed because no message was queued at the exchange passed to Wait. Only the device handler can call Wait. This error 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. 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. See the System Administration Guide or CTOS Operating System 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. Multiprocessor Systems: Remote request is too large for local buffer or the pb/cb in the request may be corrupt. A data transfer between processor boards will not fit into the available buffer. The request could be corrupt, or the size of the buffer is too small. Multiprocessor operating systems allow definition of W-blocks, which buffer extremely large board-to-board requests. The default setting for the number of W-blocks is zero. If you have not allocated one or more W-blocks, you should do so if this error occurs. Edit the W-blocks entry for each processor board in the operating system configuration file to match the example shown below. This should eliminate the error if the size of the request buffer is too small. :WBlocks: (Size=65500,Number=1) If this error still occurs after changing the parameters in the W-blocks entry as shown, the error is being caused by a corrupt request block, which is an application error. BNet II: This status code indicates that either the operating system Y-block size (Size parameter) is too small or that there is no W-block allocated or the W-block is too small. For BNet II, the Y-blocks parameter in the operating system configuration file should have a minimum size of 2900 bytes; the default size for CTOS/XE 3.4 and later is 4192 bytes; for prior CTOS/XE versions, you may need to increase the size. Also, see the above d. iscussion for information on changing the size of W-blocks in the system configuration file. 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 but 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 generally occurs 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 %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, see the 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 free 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.Shared Resource Processor Initialization: Odd control information.Shared Resource Processor Initialization: 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 Resource Processor Initialization: Invalid bus address. RemapBusAddress or UnmapBusAddress return this status code 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 map 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.Shared Resource Processor Initialization: DMA Pending. Shared Resource Processor Initialization: Channel in use.Shared Resource Processor Initialization: Service already installed.Shared Resource Processor Initialization: Service cannot be deinstalled. There was an attempt to deinstall the Pertec Sequential Access Service on a shared resource processor. The Pertec Service could not be deinstalled because there is no interface for a ResetIntHandler to undo the effects of an earlier SetIntHandler. The operating system also returns this status code upon an attempt to deinstall other system services that cannot be deinstalled.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 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, then reinitialize the disk 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 returns 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. Some portion of the file specification is invalid. For 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. Context Manager: The operating system returns this status code when attempting to load system services after the Context Manager has been loaded. All system services must be loaded before loading the Context Manager.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 attempted to initialize a new volume with the same name as a volume that already exists.File Management: File is read only. You 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 failed. Restart the server, then reenter your application and recover. This status code may also mean that you tried to perform an operation such 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 are 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. The file system limit for open files or file handles has been reached. Specify more File Control Blocks (FCBs) at system build by increasing nFCB. Related system build parameters, for example, the number of open file handles (nFUB) and open file extents (nFAB), should be greater than or equal to nFCB.File Management: Unrecognized volume or device. The specified volume or device name is not recognized. Device names can include the names of comm lines, printers, caches, and so on. This error can occur when:  The specified device specification is not in the routing table or the wrong volume name is being used.  The drive control cable is defective.  The workstation attempting to access a remote disk drive or CD-ROM device is disconnected from the cluster cable.File Management: Volume is not mounted. The specified volume is not mounted. If you are using a removable storage volume (such as a floppy disk or a CD-ROM), make sure that the volume is properly inserted. Also make sure that the disk or CD-ROM does not have the same name as another volume. With floppy disks, 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. The password supplied is longer than 12 characters.File Management: Invalid mode.File Management: Access denied. This status code may be returned when a file system request is denied because:  The password is either missing or incorrect. Use the Path command to supply t/ he 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) In a system protected by CTOS Access Control system, this status code may be returned whenever the organization's security policy forbids the attempted access. Here, "access" means any operation, such as create, open, rename, or delete, on a file, queue, or other object.File Management: File in use. This error occurs when the Executive command file for a workstation is in use. This happens if the workstation is running Context Manager, or if several workstations are sharing a command file on the server. 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 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, reinitialize, 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: Device is already mounted.File Management: Device is not mounted.File Management: 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). 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, and 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) 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 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.File Management: Run file invalid checksum. The file is probably not a run file, or it 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 inconsistency, or a dormant run file has become invalid because the server 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 run file a second time.File Management: Unrecognized format run file. The file is probably not a run file, or else the operating system loader does not understand the run file version field. 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. (See "Task Management," status codes 430-499, and the "Development Utilities" documentation.)File Management: 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 cannot open the operating system image file for the swapping client workstation.File Management: You cannot read the operating system overlay for the swapping client workstation.File Management: All the user numbers on the server have been used. Change the system build parameter for nWSUserNum. The system also returns this code 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. The 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.rFile Management: File not locked. The operation attempted 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 the 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, see the Procedural Interface Reference Manual.File Management: No free lock request list. No free lists are 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. See the System Administration Guide, for more information.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 not work on volumes or directories. File Management: Bad protection code file handle.File Management: There is no free FCB (file control block). The file system limit has been reached. Specify more File Control Blocks at system build (increase nFCB).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 Mana/ gement: No volume password.File Management: Request incomplete.File Management: Invalid VerifyCode. An invalid VerifyCode has been supplied as an argument.File Management: Remote Files Open. An attempt is being made to change the VerifyCode for a Volume that has files open for remote users.File Management: Log buffer overflow. Multiple errors occurred rapidly and the operating system was unable to log all of them.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 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 media 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 Possible 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-protected 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. Specify more IOBs 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, 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. Floppy Disk Controller: Floppy disk controller busy in command.Floppy Disk Controller: Floppy disk controller never ready in command.Floppy Disk Controller: Floppy disk controller data input in command.Floppy 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 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.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 data 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 without 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 is 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.SCSI Manager: A SCSI device has not interrupted (reselected or completed an operation on) the host processor.SCSI Manager: SCSI check condition. An application program requested a check for any SCSI error condition. SCSI Manager: SCSI page nonexistent.SCSI Manager: A SCSI command was aborted. ScsiWaitTargetDataAsync returns this status code if the foreign SCSI initiator has terminated a command in progress by sending 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 ScsiOpenPath 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 path to the same SCSI device in exclusive mode  A path handle was opened for target mode in a non-target mode operation, or vice versaSCSI 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 Manager: 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 operation or within the system default timeout limit.SCSI Manager: 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 ScsiOpenPath operation was not0  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 target 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. The File System returns this error. The SCSI Manager returns the BUSY target status to the user.Allocation: There is not enough memory available in a specific 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 memoryAllocation: You cannot allocate long-lived memory. The memory cannot be allocated because the Debugger is locked into memory in multiple-process or interrupt mode. See the 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.Allocation: 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. The system returns this error 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. This error can also be caused by listing too many files 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 operation 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. 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 are 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.Timer Management: Duplicate RTC request. A duplicate Timer Request Block (TRB) exists at the time a request is made. This request is returned by OpenRTClock.Task Management: The partition is not large enough to load the exit run file. The Debugger may be 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 installed and an application program tried to print on channel A, B, or the line printer port.Task Management: Kbd Isr already exists. An interrupt handler is already serving the keyboard.Task Management: Not an operating system call.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. See the System Administration Guide.Task Management: Bad Device Type. An invalid device type was passed to ControlInterrupt.Task Management: Memory map overflow. An attempt was made to free or access memory, causing the map to overflow. This internal error indicates a problem in the software you are using. Task Management: Large memory map inconsistent. This internal error indicates a problem in the software you are using. Task Management: No available Active Runfile Information Block (ARIB). This internal error 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 internal error 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 internal memory management error indicates a problem in the software you are using. Task Management: No available Task Information Block (TIB). This internal memory management error 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 Block (TIB) inconsistency. A TIB was referenced that had no associated Active State Information Block. This internal memory management error 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 internal memory management error 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 internal memory management error 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 internal memory management error 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 internal memory management error indicates a problem in the software you are using. Task Management: Segment not in memory. An attempt was made to deallocate a segment that was not present. This internal memory management error indicates a problem in the software you are using. Task Management: This internal error indicates a problem in the software you are using. Task Management: This is an internal inconsistency. Task Management, Memory Management: Unknown linear address. This is an internal error. Contact Technical Support.Task Management, Memory Management: Bad resize. An attempt was made to resize a segment unowned by the user.Memory Management: Real mode requires the paging service. The paging service must be installed in order to run real mode programs.Memory Management: Operation requires paging service. The paging service must be installed in order to perform the operation.Task Management: Memory Manager heap full. The Memory Manager's heap is full. 0  Increase the value of the :sMemMgrHeap: parameter in the Config.sys file.Video 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 timeout 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 collectively defined by all frames exceeds the number of lines on the screen.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 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 process 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 status 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 ServeIBusInt operation returns this status code when the operating system table that records I-Bus device handlers (mouse or pointing device) is full.Keyboard Management: No such I-Bus handler.Keyboard Management: No such I-Bus ID. Keyboard Management: Invalid keyboard identification. The internal keyboard table(s) posted by an application to the operating system are no longer valid for the attached keyboard. This can be caused by switching keyboards. This error code is returned for the ReadKbdInfo request or if an application attempts to post a table with a keyboard (I-Bus) ID that does not match the currently attached keyboard.Keyboard Management: Invalid keyboard table. The internal keyboard table(s) posted by an application to the operating system have become corrupted. This error is returned for the ReadKbdInfo request or if an application attempts to post an invalid table. It can also be returned if an application tries to read an operating system table into an area with inadequate space, or tries to read the current operating system emulation table when one is not loaded.Keyboard Management: Other keyboard table invalid. An application is trying to post a valid translation or emulation keyboard table but the other table already posted is not valid, possibly because the keyboard has been switched. The operating system will keep a pointer to this table but will continue to use its own default tables until the invalid one is replaced with another PostOStables request.Keyboard Management: No buffer space. The operating system returns this error for a WriteKbdBuffer request if all characters would not fit in the target typeahead buffer.Keyboard Management: No character. This error code is used by the operating system internally for various situations. This error can also occur when an attempt is made to use WriteKbdBuffer to write zero characters into the typeahead buffer. Keyboard Management: Invalid keyboard pointer. An attempt by the keyboard process to use a keyboard table failed because the pointer did not point to a valid keyboard table.Keyboard Management: Posted keyboard ID invalid. An attempt has been made to post a keyboard table that does not match the ID of the keyboard currently attached.Keyboard Management: No space for keyboard table. The run file loaded has specified a keyboard profile ID different from the operating system default keyboard profile, but sufficient space was not available. Increase the number of data blocks specified for the :KbdTables: parameter in the system configuration file, [Sys]Config.sys. This error might also occur if the file [Sys]NLSKbd.sys is overwritten after the operating system is initialized.Keyboard Management: No such table. The run file loaded has specified a keyboard profile ID different from the operating system default keyboard profile, but the required keyboard tables are not specified in the keyboard configuration file, [Sys]NLSKbd.sys.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.Keyboard Management: Magnetic Card Reader (MCR) is not supported by the OS at this release level. Keyboard Management: Failure of 1654 Hardware ID microprocessor.Keyboard Management: The hardware ID number must be less than 128 and greater than zero.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. Pre-GPS Spooler: An attempt was made to supply a password when the Print Service was not waiting for one.Spooler: An attempt was made to install a device with the same name as one already in use. Pre-GPS Spooler: The job entry data is inconsistent.Printer Spooler, Pre-GPS Spooler: Device is unable 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 internal error indicates a problem in the software you are using. Contact your Unisys representative. Pre-GPS Spooler: The request path is inconsistent.GPS Spooler, Pre-GPS Spooler: Delete request failed. The print job for which the delete request was issued may have already been completed or deleted and cannot be found.GPS Spooler: Spool job not found. GPS Pr1 int Service, Pre-GPS Spooler: An attempt was made to process a job with an unrecognized job index.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 initialization 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: The Print Service was unable to handle a new spooling request. If this error occurs frequently, reinstall the Print Service and increase the value in the [Number of simultaneous spool jobs] field.GPS: Print Service already installed.Printer Spooler: The Printer 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. GPS Spooler: The Print Service received an illegal command.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. 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 orientation. 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. 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 Management: Cannot create any more partitions. The number of partitions can be increased at system build. Specify more partitions at system build by modifying nPartitions. See the 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 Management: 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. Lock the partition 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 primary 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 have been issued by the operating system. This error is usually caused by services 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 memory descriptors were used. The number of partition memory descriptors may be configured by setting nUseg in the appropriate sysgen prefix file. See the System Administration Guide.Application Partition Management: Bad partition swap mode.Application Partition Management: Termination heap full. Too many simultaneous terminations were attempted. Increase the heap specified by increasing the value of :MaxConcurrentTerm: in the Config.sys file.SetEBifHandler: TyDev Conflict. The specified TyDev is not available due to a resource conflict. SetEBifHandler: TyDev is not shared. The specified TyDev is not shared. It is not necessary to use the EBif service. Instead, use SetDeviceHandler directly. SetEBifHandler: TyDev has not been allocated properly. The specified TyDev was not allocated during system initialization. SetEBifHandler: No available EBif resources. All EBif service resources are in use. ResetEBifHandler: Invalid EBif Handle. An invalid EBif handle was received. Valid EBif handles are assigned by SetEBifHandler. ResetEBifHandler: Invalid EBif user number. An unrecognized user number was received. All valid users are logged by SetEbifHandler. 881 to 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 specified 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 invoked 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 DeleteMarkedQueueEntry, UnmarkQueueEntry, or RewriteMarkedQueueEntry operation was invoked by a service process other than the service 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 process specified 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 queues.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 internal error indicates a problem in the software you are using. Queue Management: An1  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: This status code can be caused by one of the following:  The loadable request file was either missing or was the wrong version  An attempt was made to install the Queue Manager on a client workstationQueue 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 internal error indicates a problem in the software you are using. (For GPS releases prior to 2.0)Queue Management: Duplicate Service A queue service 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. The operation AddQueueEntry returns this status code. (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)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 deactivate 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. See 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 the contents of PLog.  The operating system is not compatible with the [Sys]DebuggerXXX.sys file. Check the contents of PLog.Loader: RMOS not supported. The V8 run file format does not support RMOS. V8 run files do not support real mode operation.Loader: Run file version incompatible. An attempt was made to load a V8 run file that specifies a version incompatible with the operating system.Loader: Bad dynamic link library version. An attempt was made to load a DLL whose version was incompatible with the client program.Loader: Not a dynamic link library. An attempt was made to load a DLL which does not contain exports.Loader: Bad library handle. An invalid module was argued to LibGetName or LibGetProcInfo.Loader: Bad library name. An invalid name was argued to LibGetHandle.Loader: Dynamic link library not found. A library specified by a run file or by the LibLoad request was not found. Check the system log with the PLog command for details.Loader: Cannot bind. A function imported by a client program does not exist in the dynamic link library. Check the system log with the PLog command for details.Loader: Duplicate export name. A dynamic link library contains duplicate exported function names. Check the system log with the PLog command for details.Loader: Invalid resource. The resource directory in a V8 run file is not valid. See the CTOS Programming Utilities Reference Manual: Building Applications for more information on resources.Loader: No such resource. The resource type and ID argued to GetModuleResourceInfo are not included in the module.Loader: Instruction set incompatible. The run file requires an instruction set that is not present on the host system.Loader: Math hardware incompatible. The run file requires a math chip that is not present on the host system.Loader: Loader Heap is full. The loader heap is too small. Increase the heap size specified in Config.sys.Loader: Reserved.Loader: No Free Instance selectors. There are no free instance selectors. Increase the maximum number of instance selectors specified in Config.sys.Loader: No RelocTable. An attempt was made to load run file or dynamic library that required selector relocation that did not contain a selector relocation table.Loader: Page Service required. An attempt was made to use dynamic libraries without the Page Service installed.Loader: Cannot free library. An attempt was made to free a dynamic library for which Exit Procedures existed. See SetExitList.Loader: No such exit procedure. ExitListQuery returns this error when no ExitList procedures exist for the specified handle.Loader: Exit procedure exists. ExitListSet was called twice with the same pProc arguement, thereby attempting to add an ExitProc that is currently registered for the user. Name Management: Name too big. The name argued to NameRegister exceeds 255 bytes.Name Management: Name already exists. The name argued to NameRegister already exists in the class specified.Name Management: Name not found. The name argued to NameQuery does not exist in the class specified.Name Management: Bad name class. The class argued to NameRegister, NameQuery, or NameRemove does not exist.Name Management: Name space full. The name heap is full. Increase the name heap by changing the sNameHeap token in the Config.sys file.CTOS Library Utilities: Configuration file not open. A configuration file must be opened before using other configuration file operations.CTOS Library Utilities: Configuration file already open. A configuration file is already open. It must be closed before another configuration file can be opened.CTOS Library Utilities: Buffer too small. The buffer used for configuration file operations must be at least 512 bytes long.Executive: Invalid Executive invocation. The Executive may report this code when it is improperly invoked from other applications, such as Batch. Such instances may indicate an improper Executive intrinsic command case value, or the Application System Control Block (ASCB) is not properly set up.OFIS Document Products: Bad keyboard message.OFIS Document Products: No more documents. Save more often in a session.OFIS Document Products: No more windows.OFIS Document Products: Cannot locate place.OFIS Document Products: No more display line descriptors.OFIS Document Products: Formatting operator overflow.OFIS Document Products: Wrong video.OFIS Document Products: Formatting operator too big.OFIS Document Products: Bad formatting operator.OFIS Document Products: Cannot resolve placeOFIS Document Products: Too many bins.OFIS Document Designer: Virtual memory lock.OFIS Document Products: Bad file format.OFIS Document Products: Bad file version.OFIS Document Products: Virtual memory read only buffer.OFIS Document Products: Virtual memory dirty page underflow.OFIS Document Products: Data segment allocation error.OFIS Document Products: Bad file number.OFIS Document Products: Bad style. Try removing some of the formatting attributes (headers, footers, indents, etc.) and then save.OFIS Document Products: Back memory allocation error.OFIS Document Products: No free buffer pointer.OFIS Document Products: Spooler disk full.OFIS Document Products: Too many user parameters.OFIS Document Products: Bad font.OFIS Document Products: Format set initialization error.OFIS Document Products: Sort error.OFIS Document Products: Cannot deallocate.OFIS Document Products: No free attribute.OFIS Document Products: Bad anchor header.OFIS Document Products: Index not available. OFIS Document Products: Merge too large.OFIS Document Products: Internal index full. OFIS Document Products: No more fonts.OFIS Document Products: Word already in index. OFIS Document Products: No font service.OFIS Document Products: Cannot register character pointer.OFIS Document Products:2  Character pointer not registered.OFIS Document Products: Bad document.OFIS Document Products: End of typescript file. Recover the session and cancel recovery before the operation that caused the error.OFIS Document Products: Indexed document has bad pointer.OFIS Document Products: Indexed document has bad delta character pointer.OFIS Document Products: Indexed document has bad hash code.OFIS Document Products: Indexed document has bad character pointer.OFIS Document Products: Indexed document has bad index phrase.OFIS Document Products: Indexed document has bad count of bytes.OFIS Document Products: Character pointer too large.OFIS Document Products: Typescript synchronization error.OFIS Document Products: Stack overflow.OFIS Document Products: No more index headers.OFIS Document Products: Negative white space.OFIS Document Products: Internal error. This is not a user error.OFIS Document Products: Memory low.OFIS Document Products: Macro stack empty.OFIS Document Products: Macro stack full.OFIS Document Products: Bad macro file.OFIS Document Products: Bad macro.OFIS Document Products: Bad macro state.OFIS Document Products: Typescript checksum error.OFIS Document Products: Math: Undefined variable.OFIS Document Products: Math: String expected.OFIS Document Products: Math: Selected text too long.OFIS Document Products: Math: String length exceeded.OFIS Document Products: Bad typescript.OFIS Document Products: 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 Document Products: 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 Document Products: 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 Document Products: Bad heap 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 an internal memory management error. Reopen the application and recover.OFIS Document Products: 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 Document Products: 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. 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 Document Products: Node backpointer not found.OFIS Document Products: Bad node address.OFIS Document Products: Bad node backpointer.OFIS Document Products: Bad node count of register pointers.OFIS Document Products: Bad binary-coded decimal (BCD) number.OFIS Document Products: Bad BCD operator.OFIS Document Products: Divide BCD by zero.OFIS Document Products: BCD must be integer.OFIS Document Products: A BCD number is expected.OFIS Document Products: A BCD operator is expected.OFIS Document Products: BCD is too complex.OFIS Document Products: BCD has unmatched brackets.OFIS Document Products: Document in use.OFIS Document Products: No such document.OFIS Document Products, 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 Document Products, Development Utilities: Bad node link. An internal memory management error occurred. If you observe such an error, report it to your Unisys representative.OFIS Document Products, Development Utilities: Bad node tag. An internal memory management error occurred. If you observe such an error, report it to your Unisys representative.OFIS Document Products, Development Utilities: Count of register pointers node overflow. An internal memory management error occurred. If you observe such an error, report it to your Unisys representative.OFIS Document Products, Development Utilities: Count of register pointers node underflow. An internal memory management error occurred. If you observe such an error, report it to your Unisys representative.OFIS Document Products, Development Utilities: Dangling node backpointer. An internal memory management error occurred. If you observe such an error, report it to your Unisys representative.OFIS Document Products, Development Utilities: Double node registry. An internal memory management error occurred. If you observe such an error, report it to your Unisys representative.OFIS Document Products, Development Utilities: No node backpointers. An internal memory management error occurred. If you observe such an error, report it to your Unisys representative.OFIS Document Products, Development Utilities: No free node backpointer. An internal memory management error occurred. If you observe such an error, report it to your Unisys representative.OFIS Document Products, Development Utilities: Node not busy. An internal memory management error occurred. If you observe such an error, report it to your Unisys representative.OFIS Document Products: Node not free. An internal memory management error occurred. If you observe such an error, report it to your Unisys representative.OFIS Document Products: Node not on free list.OFIS Document Products: Cannot register selection.OFIS Document Products: Cannot Unregister selection; selection was not registered.OFIS Document Products: Print job failed. OFIS Document Products: Bad soft key piece number.OFIS Document Products: Bad help version.OFIS Document Products: Merge too large.OFIS Document Products: Bad help version.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 the 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 Cache 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 not a valid handle obtained through RemoteCacheOpen.Caching: Invalid Remote Cache parameter. The Remote Cache service returns this status code if a cb in a request 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 handle obtained through CacheInit.Caching: No such cache entry. CacheGetStatus reutrns this status code if the specified cac2 he 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 return this error 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 File 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 file handle is cache-disabled. Caching 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: Bad Remote Cache control word. The Remote Cache service returns this status code if the controlMask and/or controlValue parameters in a request 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 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 page unlockable. LockInCache returns this status code if a portion of disk cannot be locked into the File Cache because of a disk media defect. 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 the specified heap does not have sufficient space to satisfy the allocation. 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.Editor: Bad keyboard message.Editor: No more documents. Save more often in a session.Editor: No more windows.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.Editor: Internal error. This is an internal memory management error. It indicates a problem with the software you are using. If you receive this error, report it to Technical Support.Editor: Internal Command Table is not found. The Editor has Internal Command Tables for different keyboards, but could not find the appropriate Table for the current keyboard. If you receive this error, report it to Technical Support.Editor: Heap full. There 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 corrupted. 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 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 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: 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 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 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, indicating 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.Sequential Access Method: Too many put backs. Only one PutBackByte is allowed before reading again.Sequential Access Method: Invalid mode to OpenByteStream. Valid modes are: ModeRead, ModeWrite, ModeAppend, ModeModify, and ModeText.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.Sequential Access Method: Buffer too small. Buffer must be 1024 bytes to allow device independence.Sequential Access Method: Invalid video byte stream escape sequence.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 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.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 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 optimized. 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 error3 . 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.)Sequential 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. An error occurred 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 the following, depending on operating 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 error 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. This holds off the transmitter while the receiver catches up, then restarts the transmitter. (See "Create Configuration File" in the 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 catch 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 processor simultaneouslySequential 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 the system returns this code, the caller must expect a subsequent message notifying him when the blocking 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. Receive and transmit operations are independent and may overlap in time. For example, the caller will not get ercWrongTimeToCall from a FlushBufferC 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 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 cleared.Parameter Management: No such parameter. In a call to RqParams, the parameter specified exceeds the maximum number of possible 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 restricted the number of subparameters that may be entered. See the application's documentation for the maximum number of subparameters.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.Parameter Management: Parameter or subparameter was greater than 255 bytes.Parameter Management: VLPB full. The operation failed because the Variable Length Parameter Block could not be extended by allocating long-lived memory.Parameter Management: Illegal iParam. The value of iParam supplied to RgParamSetListStart or RgParamSetSimple is not less then CParams.Parameter Management: Not in list. An RgParamSetEltNext was invoked after an RgParamSetSimple, or the number of parameters in the list was exhausted. Executive Forms: Buffer is full. The buffer provided is not large enough to hold the resulting string. Executive Forms: Exit character. (This is not an error.) The user selected an exit character. EnlsFieldEditByChar returned control to the application, and passed the status code to the application. Executive Forms: Form too large.Executive Forms: Invalid form description.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.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 characters %'. 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 cannot successfully expand a file specification with a wild card character.Executive Forms: Uninitialized work area buffer.Executive Forms: Unrecognized 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 does not fit into the choice text area on the screen.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.Executive Forms: Invalid quote characters. Quote characters use3 d in an Executive command form are not balanced.Executive Forms: Cannot use confirmation from background batch. A command was executed with a confirmation option set to "Yes" while running from a batch JCL file running in the background. Background execution cannot make use of user interaction. Date/Time Conversion: The date specified must be between January 1, 1952 and November 16, 2041. 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.Date/Time Conversion: Month is not in the range 0-11. An invalid value has been supplied by an application to the operation CompactDateTime. The value for the month must be within the range 0-11. If you are a user, try entering the number for the month again.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.ISAM III: No such index exists. An operation that includes a key was invoked, but the specified index does not exist.ISAM III: Prefix is not valid. SetUpISAMIterationPrefix was invoked for an index that is neither a byte nor character string. ISAM III: Bad key length. The key length is inconsistent with the index type. ISAM III: Bad ISAM or data base handle. (C-ISAM error 101: ENOTOPEN) The ISAM handle does not identify an open ISAM dataset. ISAM III: Bad ISAM header size. The ISAM dataset cannot be opened by the OpenISAM operation due to an inconsistency in the header of one of the files of the dataset. ISAM III: Bad ISAM header. See 3104. ISAM III: Too many indexes. An attempt was made to perform an OpenISAM on a dataset with more than 128 indexes (100 indexes for ISAM II). This is an internal error that indicates a problem with the software you are using. ISAM III: ISAM is already installed. This code is generated by the InstallISAM operation or the ISAM INSTALL command if ISAM 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 Blocks. The maximum number of ISAM Control Blocks has been used. Internal error. ISAM: No free ISAM handles. The ISAM dataset cannot be opened because the maximum ISAM datasets that can be simultaneously opened by all users combined has been reached. Increase the number of user opens in the ISAM Control Center. This status code is equivalent to C-ISAM error 104: ETOOMANY).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 pointers 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. Use the Executive PLog command to examine the log file. Locate the error in the file and record the Shutdown Code, Module Id, and Error Code. Call your designated product support.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. This status code is equivalent to C-ISAM error 126: EBADROWID.ISAM: Duplicate key. An attempt to store or modify a record would duplicate the key stored in another record for the same index, but the index does not allow duplicates. This status code is equivalent to C-ISAM error 100: EDUPL.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 dataset. This status code is equivalent to C-ISAM error 105: EBADFILE.ISAM: Attempted privacy breach. An attempt was made to modify a dataset that is open in batch read or transaction read mode. This status code is equivalent to C-ISAM error 101: ENOTOPEN.ISAM: Bad ISAM request. Either the request block is invalid, or the parameters of an operation are inconsistent or have invalid values.ISAM: 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 dataset. If an application tries to open a dataset that does not exist, ISAM returns this error code and puts 203 (No such file) in ErcDetail. This status code is equivalent to C-ISAM error 105: EBADFILE.ISAM: Index to data error. An inconsistency has arisen between the index and data store files of the ISAM dataset.ISAM: Record size incorrect. The record size specification in a call is incorrect. ISAM does not return this error code for OpenISAM.ISAM: Duplicates allowed. An operation specified a unique key parameter (that is, duplicates are not allowed), but the index allows duplicates. This status code is equivalent to C-ISAM error 100: EDUPL.ISAM: No such record exists. A Unique key was used to identify a record, but no record is stored in the ISAM dataset with that key. This status code is equivalent to C-ISAM error 111: ENOERC.ISAM: No more records. A ReadNextISAMRecord(Hold) or GetISAMRecords(Hold) operation has read all the records within the range specified for the current iteration. ISAM III also returns this error if you call ReadPrevISAMRecord(Hold) when the current record position is on the first record of the dataset. This status code is equivalent to C-ISAM error 110: EENDFILE.ISAM: Invalid key. Either 1) an index specification, including all key parts, is longer than 120 bytes or is defined to occupy bytes past the end of the record, or 2) a supplied key is invalid. For example, a DECIMAL key with a non-numeric character in a digiet position is invalid. See ercDetail for further information about why the key is invalid. This status code is equivalent to C-ISAM error 103: EBADKEY.ISAM: Invalid index. ISAM returns this error if you specify an index number that is greater than or equal to the number of indexes in the ISAM dataset. This status code is equivalent to C-ISAM error 103: EBADKEY.ISAM: Bad ISAM mode. The mode parameter of the OpenISAM operation is invalid. This status code is equivalent to C-ISAM error 101: ENOTOPEN.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: Bad 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 does not check password validity if the dataset exists and is not protected. If it is protected, and the supplied password is too long, ISAM reutrns 3132 and stores 217 (Password greater than 12 characters) in ercDetail. This status code is equivalent to C-ISAM error 152: EPASSWD.ISAM: Wrong record size. The OpenISAM operation detects the wrong size record.ISAM: Incompatible ISAM mode. An attempt was made to open a dataset when the dataset is already open in an incompatible mode. This status code is equivalent to C-ISAM error 113: EFLOCKED.ISAM: ISAM already locked. LockISAM was called on an ISAM dataset that was already locked. Internal error.ISAM: Not open in administrator mode. An operation for which the dataset must be open in administrator m4 ode is attempted with the dataset open in some other mode. This status code is equivalent to C-ISAM error 106: ENOTEXCL.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. If the dataset already exists, ISAM returns 3122 instead of 3137.ISAM, CT-DBMS: Buffer is too small. ISAM: The dataset being opened or created requires buffers larger than those installed. CT-DBMS: The relation being accessed requires buffers larger than those installed.ISAM: Not locked. UnLockISAM was called on an ISAM dataset that was not already locked. Internal error.CT-DBMS, ISAM: invalid ISAM record size. ISAM: An attempt was made to create an ISAM dataset with records shorter than four bytes or longer than 4000 bytes. CT-DBMS: An attempt was made to initialize a database 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 in a transaction. Call RollBackTransaction and redo the transaction. See the ISAM III documentation on transaction guidelines in Writing ISAM Applications. This status code is equivalent to C-ISAM error 122: ENOTRANS.CT-DBMS, ISAM: Dataset or relation is not available. ISAM: An attempt to read or hold a record or to hold a dataset failed because the dataset was held by another user. This status code is equivalent to C-ISAM error 113: EFLOCKED. 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: Dataset or tuple is not available. ISAM: An attempt to read or hold a record or to hold a dataset failed because the record was held by another user. This status code is equivalent to C-ISAM error 107: ELOCKED. CT-DBMS: An attempt to read or lock 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 dataset) must be held was invoked when neither the record nor its dataset was held. This status code is equivalent to C-ISAM error 107: ELOCKED. 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 was already held. The maximum is 65535.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. This status code returns C-ISAM error 150: EINTRAN. Note: C-ISAM error 150 is not part of the C-ISAM standard. It is an addition for the ISAM III implementation only.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: Buffers are not enough. The operation failed because you specified too few indexes and/or data buffers in the configuration file.ISAM: ISAM Service not available. Internal error.CT-DBMS, ISAM: Dataset or relation is not locked. ISAM: An operation for which the dataset must be held was called when the dataset was not held. This status code is equivalent to C-ISAM error 113: EFLOCKED. 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 operation failed because there is not enough room in the ISAM or CT-DBMS service's heap to store data structures required by the operation. If an ISAM III application in transaction state receives this message, it should roll back the transaction and try again. If the error occurs frequently, the database administrator should increase the heap size in the ISAM Control Center. This status code is equivalent to C-ISAM error 116: EBADMEM.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 dataset so that the data store and index files would be on different workstations or to open a dataset (in other than administrator mode) that is on a different workstation from the one where the ISAM service is running. CT-DBMS: An attempt was made to initialize a database 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 after modification. An ISAM transaction barrier operation was called after a modification to the dataset or database 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 locked. 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. This status code is equivalent to C-ISAM error 107: ELOCKED.ISAM: Transaction has been rolled back. The application's 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 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: Interal error. Journal record illegal. An error 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 node 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 dataset. 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 software you are using.CT-DBMS, ISAM: Duplicate key. ISAM: An unexpected duplicate key was found in a dataset. 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 ISAM 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 are 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 objects were still realized when an attempt was made to close a cache file. This indicates an internal error with the s4 oftware you are using.CT-DBMS, ISAM: Bad globals. 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: Bad cache unrealize. An attempt to unrealize a cache object failed. This indicates an internal 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, 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 with 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 an 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: Invalid key type. The type field of a key specification for Sort/Merge or ISAM is invalid. This is equivalent to C-ISAM error 103: EBADKEY.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. This is equivalent to C-ISAM error 103: EBADKEY.ISAM: Bad key specification. 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.) This is equivalent to C-ISAM error 103: EBADKEY.ISAM: Bad dataset. This error occurs in the following situations:  The dataset is corrected  The data file buffer returns an internal error Rebuild the database to correct the error This is equivalent to C-ISAM error 105: EBADFILE.ISAM: Invalid cluster station installation. An attempt was made to install the ISAM service on a client workstation without local file storage. This is an unsupported configuration. Either install a local disk drive or install the service on the server.ISAM: Cannot rename file. ISAM is unable to complete a request to rename a file. Check ercDetail (StatWrd2) to find the CTOS error that prevented the rename operation.ISAM: Control point in progress. An application attempting to start a transaction receives this message when the following conditions occur simultaneously:  The ISAM service is processing a sync point  Transactions are active  The Action At Sync Point flag in the ISAM Control Center is set to Do Nothing Wait a short time and try to start the transaction again. The application will continue to receive this error until the sync point processing finishes. This is equivalent to C-ISAM error 151: EINCP.ISAM: Internal heap memory corrupted. Terminate the ISAM service and restart it.ISAM: Invalid index parameters. An attempt to create an index while creating a dataset or adding a new index encountered either of two errors:  The maximum number of indexes (128) is exceeded  The index specification block is invalid From a program, call GetISAMFileStatus to check how many indexes currently exist. From the Executive, use the ISAM STATUS command to check how many indexes exist. If the number of indexes would not cause the error, correct the index specification block in your application This is equivalent to C-ISAM error 103: EBADKEY.ISAM: Cannot begin transaction. This error usually indicates one of two situations:  There are too many concurrent transactions  The ISAM service is terminating Check ercDetail (StatWrd2). If it is 3231, refer to 3231 for corrective actionISAM: Too many transactions. ISAM returns this error in ercDetail (StatWrd2). ISAM is unable to support a new transaction. ISAM limits the total number of concurrent transactions to the maximum number of users specified in the ISAM Control Center. If error 3231 occurs frequently, terminate the server, and increase the Max Users parameter in the ISAM Control Center. Restart the server. If error 3231 returns very rarely, wait a short time for other transactions to finish. Reissue the request to begin a transaction.ISAM: Internal heap memory corrupted. Terminate the ISAM service and restart it.ISAM: Cannot roll back transaction. Terminate the ISAM service and restart it.ISAM: Invalid audit file. The audit file is invalid in the following circumstances:  The audit file number does not match the current audit file number in the control file  The audit file header and trailer do not match  The audit file version does name match the current database  The audit file compressor could not find a CommitTransaction to go with a BeginTransaction in the audit file Back up the database and rebuild it up to, but not including, the invalid file.ISAM: Audit file internal error. ISAM returns this error when an audit file operation fails or if the audit file is corrupted. Terminate the ISAM service and reinstall it.ISAM: Invalid audit block. Rebuild the database.ISAM: Encountered audit file discontinuity. During a rebuild, ISAM encountered a discontinuity in the audit file. An application cannot receive this error because only ISAM utilities can rebuild the database. If you have another backup copy of the audit file, redo the rebuild using that copy. Otherwise, you must end the rebuild at the discontinuity point. This is usually the case because ISAM records a discontinuity when you perform an operation that ISAM cannot roll forward. Those operations are:  CFMaintenance  ISAM Reassociate  Turning the audit trail on or off in the ISAM Control CenterISAM: Invalid file name. Correct the file name. This is equivalent to C-ISAM error 114: EFNAME.ISAM: Too many users. ISAM is already serving the number of users specified in the Max Users parameter of the ISAM Control Center. Wait a short time and try again. If this situation occurs frequently, you should increase the Max Users value. This is equivalent to C-ISAM error 129: EUSER.ISAM: Previous request pending. ISAM returns this error to an application that calls any ISAM procedure (including ISAMRequest) while ISAMRequest form the same application is still pending. ISAM III is single threaded and can, therefore, process only one request at a time. This error only occurs when an application uses the ISAMRequest mechanism. Modify the application to wait until it receives a response from the first request before issuing another ISAM call.ISAM: Too many unique opens. ISAM has reached the maximum number of open datasets. Wait for some datasets to close. If this error occurs frequently, increase the Max Unique Opens parameter in the ISAM Control Center. This is equivalent to C-ISAM error 104: ETOOMANY.ISAM: Too many user opens. ISAM has reached the maximum number of user opens. A user open is an active ISAM handle issued by the ISAM service in response to an OpenISAM or isopen request. Wait for some handles to close. If this error occurs frequently, increase the Max User Opens parameter in the ISAM Control Center. This is equivalent to C-ISAM error 104: ETOOMANY.ISAM: Database not quiet. Only ISAM utilities return this error. Terminate the ISAM service and restart it to force automatic recovery. If the database is still not quiet, you must rebuild the database.ISAM: File name already e5 xists in control file. This error occurs if you try to create a dataset when a dataset with the same filename was previously deleted using the CTOS Executive Delete command instead of the ISAM Delete command. The database is corrupt because the control file does not match the collection of datasets on disk. However, the datasets remaining on disk are valid. Use the following procedure to recover from this condition: 1. Terminate the ISAM service. 2. Correct the control file by using the CFMaintenance Executive command. This records a discontinuity in the audit file. 3. Perform a complete database backup. 4. Restart the ISAM service.Unable to add a key to B-Tree. This error usually occurs when the B-Tree for an index is severely unbalanced. In a severely unbalanced B-Tree, one leg may extend to its full depth. This condition is the result of adding records to the dataset in key order. This error can also occur if the B-Tree is actually full. That is, all legs at all levels are full. However, this situation is extremely unlikely. Reorganize the dataset. This corrects the problem except in the rare condition of the B-Tree actually being full. If reorganizing the dataset does not solve the problem, you must divide the dataset into two databases.ISAM: All null keys. ISAM returns this error with datasets that have Nulls Not Indexed specified for all keys. It returns the error if you try to add a record in which all the keys have null values. Modify the record so that it contains at least one non-null key value.ISAM: Invalid unique ID. ISAM returns this error if you attempt to set the unique ID to a value less than its current value. This is equivalent to C-ISAM error 132: EROWSIZE.ISAM: Cannot delete primary index. ISAM returns this error if you attempt to delete index 0 with DeleteISAMIndex or if you call isdelindex with a keydesc that matches the keydesc of index 1. Reorganize the dataset to delete the index. List all the old indexes, but omit the primary index. The reorganized dataset will not contain the index. This is equivalent to C-ISAM error 109: EPRIMKEY.ISAM: End of file. A sequential read operation has reached the end of the file. This is equivalent to C-ISAM error 110: EENDFILE.ISAM III: Current Record Position is undefined. (C-ISAM error 112: ENOCURR) ISAM returns this error when the application uses a procedure that operates on the current record but the CRP has not been defined. It might be on a deleted record or on a point just before the first or just after the last record. Use one of the calls that defines the CRP. ISAM III: No primary key. (C-ISAM error 127: ENOPRIM) ISAM returns this error code if a primary key does not exist.ISAM III: Index already exists. (C-ISAM error 108: EKEXISTS) ISAM returns this error code if you attempt to add an index with the same index specifications that an existing index already has.ISAM III: Dataset already locked. (C-ISAM error 113: EFLOCKED) ISAM returns this error code if you attempt to lock a dataset that is already locked. Wait for the other user to release the dataset. ISAM III: Invalid argument. (C-ISAM error 102: EBADARG) An application passed an invalid argument to an ISAM procedure. ISAM III: File not open in exclusive mode. (C-ISAM error 106: ENOTEXCL) ISAM returns this error code if you try to perform certain operations, such as adding and deleting indexes, without first opening the dataset in exclusive access mode. Reopen the dataset in an exclusive access mode such as administrator or batch mode. ISAM III: Record has duplicate key but can be added. ISAM returns this code if you add a record that has a duplicate key and the dataset allows duplicate keys. For information only; no action necessary. ISAM adds the record. ISAM III: Next key is duplicate. ISAM returns this code after reading the current record and the next record has the same key value. For information only; no action necessary. ISAM III: Invalid control file. The control file is corruputed. Rebuild the database. ISAM III: Bad audit file during rebuild. Restore a backup copy of the audit file and rebuild again starting with that file. If your backups of the audit file are all bad, you cannot rebuild the database past the point of failure. ISAM III: ISAM service should not be installed. Some ISAM utilities require that the ISAM III service not be installed. Refer to Table B-4 in Accessing and Using ISAM III Utilities.ISAM III: Cannot call IPTI after open. ISAM returns this code if you call ISAMPreserveTransIntegrity after opening a dataset. Modify the application to call ISAMPreserveTransIntegrity before it makes any other ISAM calls. ISAM III: IPTI already set. For information only; no action necessary. ISAM III: No files open. (C-ISAM error 101: ENOTOPEN) ISAM returns this error code if you try to access a dataset by handle when no datasets are open. In this case, the handle you pass is invalid. First open the dataset, then access it. ISAM III: Cannot rebuild from remote workstation. ISAM returns this error code if you try to rebuild a dataset from a remote workstation. The remote workstation may be a cluster workstation with ISAM running on the server. It might also be a workstation on a remote node. You can rebuild on a cluster workstation if the service is running on that workstation. ISAM III: Reserved.ISAM III: The compressor service is already installed.ISAM III: Not a STAM file. The operation failed because the file did not contain the proper signature. ISAM III: STAM header bad checksum. The operation failed because the checksum computed on the file header did not match the checksum computed when the file was created. ISAM III: Record does not exist. The operation failed because the specified record does not exist. Internal Error. ISAM III: Bad Cache Object. The operation failed because the buffer contains a bad data record or a bad index node. ISAM III: Not fixed-length record. The operation failed because the access method cannot reference variable-length records. ISAM III: Bad file type. The operation failed because the file cannot be accessed with the specified access method. ISAM III: Bad buffer size. The operation failed because the buffer size was too small or not a multiple of 512. ISAM III: Buffer is not word-aligned. The operation failed because the buffer was not word-aligned. Sort/Merge: Cannot open work file. Unable to open one of the work files during 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 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. Not enough memory was allocated for the sort work area.Sort/Merge: No records to sort. DoSort was called before any records were released.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 this 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.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 must be numeric.Sort/Merge: Record too large. A record found in the file to be sorted is too large.Sort/Merge: Malformed 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 occurred in one or more of the files being merged. A sort of that file must be performed first.Sort/Merge: Malformed record. A malformed record was found in a 5 file to be merged.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 internal 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 supplied 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 the data.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 file 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. BNet II: If the Network Control Center (NCC), running on a cluster station, exits and reports this error, the server has probably gone down and come back up.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 the 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.Forms 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:  If 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, reading 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.Forms Designer: Protected field. UserFillField was called on a field defined as protected.Forms Designer: Invalid initialization buffer. EditForm or RestoreForm was supplied with an initialization buffer that was not correctly formatted.Forms Designer: Input cancelled. A Form cancel function key terminated TypeForm. 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 more 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 will cause the Form descriptor to exceed its maximum size (8Kb).Forms Designer: Data Truncated In Returned Buffer. The user-supplied buffer is too small to contain all of the returned data. As a result, the system returns the maximum possible valid information and updates CbValuesRet.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 not 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. 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.ISAM III: 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 datasets). Use DB Recover to recover the data base. Recover ISAM datasets by another mechanism such as restoring archived copies. ISAM III: 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 III: 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 III: Too Many Services. The operation failed because the application program tried to access too many services. ISAM III: Bad Node Specification. The dataset file specification contains a bad node name. ISAM III: Context Manager is Installed. You tried to terminate the ISAM service while Context Manager was installed. (Operating system levels prior to BTOS II or CTOS VM 9.2.) ISAM III: Invalid Installation on No LFS System. You tried to install the ISAM service on a system that does not have a local file system. Either install a local disk drive or install the service on the server. ISAM III: A locked record is read. The dataset was opened by the application in transaction read held mode and a locked record was read using an ISAM read operation. ISAM III: Index key buffer too small. The index key buffer size given by the user application is too small for ISAM service to write up all the key information to that buffer (in GetISAMFileStatus call). ISAM III: BadUnrealizeDirty. This error occurs if the information that should be written to a record to indicate that it is deleted is not written. ISAM III: BadUnrealizeCheckB. This error occurs if the CheckB in the record about to be written is incorrect. ISAM III: BadUnrealizeURI. This error occurs if the URI in the record about to be written is incorrect. ISAM III: BadCheckPointURI. This error occurs if the URI in the record about to be written is incorrect. ISAM III: Cannot deinstall ISAM service. ISAM cannot be deinstalled while running in protected mode. ISAM III: CLog handles corrupt. The internal count of the number of ISAM services currently active has become corrupt. ISAM III: Heap is too small. The heap size specified by the configuration file is too small. The heap must be at least 10 kilobytes. ISAM III: 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/80486 processors. ISAM III: Bad heap selector. An address of a heap6  node has become corrupt. ISAM III: Cannot find service. An internal table of the currently active ISAM service has become corrupt. ISAM III: Malformed unrealize. An unrealizable operation preformed on the cache is inconsistent. ISAM III: Not multipartitioned operating system. An attempt was made to deinstall the ISAM Server on an operating system that is not a multipartioned operating system. ISAM III: Service is not on the same workstation. The ISAM Terminate procedure was attempted from a remote workstation. ISAM III: Service in use. The ISAM Terminate procedure was attempted when the ISAM Service was still in use by application systems. ISAM III: 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 III: Rollforward inconsistency. An error has occurred when replaying the journal file during a recover operation. ISAM III: Rollback inconsistency. An internal error has occurred during a rollback operation. Call your designated product support. ISAM III: Rollback not legal. An attempt was made to roll back a transaction 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 database. 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 database when the database was already open in an incompatible mode.CT-DBMS: Unable to create database. This internal error indicates a problem in the software you are using. CT-DBMS: Database off-line. An attempt was made to open a database with a mode other than administrator mode when the database was off-line.CT-DBMS: Database undamaged. Because of a serious hardware or software malfunction, the database may contain invalid data or file structures. The database administrator must repair the database and place it back on line before 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 database.CT-DBMS: No such database. An attempt was made to open a database that has not been initialized by DB Initialize. Cannot compile view. This is the status code for the 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 reason for the failure.CT-DBMS: Database directory error. This is the status code for the OpenDB operation. The detail status code refers to a problem with the directory of databases.CT-DBMS: Database directory already open. This internal error indicates a problem in the software you are using. CT-DBMS: Database directory was accessed before it was open. This internal error indicates a problem in the software you are using. CT-DBMS: Unable to access database directory. This internal error 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 database.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 access 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 database.CT-DBMS: Key record size incorrect. The size of the key record specified is incorrect for the index.CT-DBMS: 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 index 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 in 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 length 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 database. CT-DBMS: No such relation. The relation named in a view specification does not exist in the database. 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 differs from that specified in the schema of the database.CT-DBMS: Data dictionary for the database is corrupt. This internal error indicates 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 specified 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 database handles. The maximum number of databases and ISAM data sets that can be opened simultaneously by all users combined is 1023. This number has now been reached and the database cannot be opened.CT-DBMS: DB Initialize's internal memory space is full. This internal error indicates a problem in the software you are using. CT-DBMS: DB Initialize symbol table overflow. This internal error indicates6  a problem in the software you are using. CT-DBMS: DB Initialize's internal memory workspace is fragmented. This internal error indicates a problem in the software you are using. CT-DBMS: Cannot initialize the database from its schema. A generic error related to a database environment that prohibits DB Initialize from successfully completing its task. The database 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 during 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 internal error indicates a problem in the software you are using.CT-DBMS: Root file 01 already exists. This internal error indicates a problem in the software you are using. CT-DBMS: An error occurred trying to open root file 01. This internal error indicates a problem in the software you are using. CT-DBMS: Root file 05 already exists. This internal error indicates a problem in the software you are using. CT-DBMS: An error occurred trying to open root file 05. This internal error indicates a problem in the software you are using. CT-DBMS: Root file 03 already exists. This internal error indicates a problem in the software you are using. CT-DBMS: An error occurred trying to open root file 03. This internal error indicates a problem in the software you are using. CT-DBMS: The data file for some relation already exists. This internal error 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 database. This internal error indicates a problem in the software you are using. CT-DBMS: The index file for some relation already exists. This internal error 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 database. This internal error indicates a problem in the software you are using. CT-DBMS: Root file 00 already exists. This internal error indicates a problem in the software you are using. CT-DBMS: An error occurred trying to open root file 00. This internal error indicates a problem in the software you are using. CT-DBMS: The journal file specified to DB Initialize already exists. This internal error indicates a problem in the software you are using. CT-DBMS: An error occurred trying to open the journal file. This internal error indicates a problem in the software you are using. CT-DBMS: The data file for some relation already exists. This internal error indicates a problem in the software you are using. CT-DBMS: The index file for some relation already exists. This internal error indicates a problem in the software you are using. CT-DBMS: DB Initialize's internal memory space is corrupt. This internal error indicates a problem in the software you are using. CT-DBMS: User file, symbol table overflow. This internal error indicates a problem in the software you are using. CT-DBMS: Database in use. The database is currently being used by a CT-DBMS utility. If a utility returns this error, the database 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-DBMS configuration file. DB Install was invoked with a configuration file that is not a valid CT-DBMS configuration file. CT-DBMS: CT-DBMS configuration file wrong version. DB Install was invoked with a configuration file created by a version of DB Configure that is incompatible with the version of DB Install being used. Create the configuration file with the version distributed with DB Install.CT-DBMS: CT-DBMS configuration file error. This internal error indicates a problem with the software you are using. CT-DBMS: User file error. An error has occurred in the verification 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 database. If the name should be a valid one and if the user file has recently been modified, it may contain syntax errors. See your Database Administrator.CT-DBMS: Missing user file privileges. There are no privileges list in the user file for this database for this user. CT-DBMS: Journal file inconsistent. The archive copy and the journal file do not represent the current state of the database. Further database 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: Database already open. An application system is allowed to open a given database only once.CT-DBMS: Invalid view for index. The ISAM operation OpenISAM was used to open a relation of a database as an ISAM data set. The operation failed because the view used for one of the indexes did not correspond properly to the index. See the CT-DBMS reference documentation for more information.CT-DBMS: A CT-DBMS physical scanning index Id was used for key lookup. This internal error indicates a problem in the software you are using. CT-DBMS: The data structures used during the scanning of the journal file are corrupt. This internal error indicates a problem in the software you are using. CT-DBMS: The data structures used during roll-forward are corrupt. This internal error 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 internal error indicates a problem in the software you are using. CT-DBMS: The entry in the database directory for the specified database is bad. This internal error indicates a problem in the software you are using. CT-DBMS: View Control Block is corrupt. This internal error indicates a problem in the software you are using. CT-DBMS: Index Control Block is corrupt. This internal error indicates a problem in the software you are using. CT-DBMS: Journalizing databases open at too many nodes. During a transaction, an application is allowed to have journalizing databases open in transaction modify mode at one mode only. Close all databases at the other node before calling BeginTransaction.CT-DBMS: No more databases. A ReadNextDB operation has read all of the databases at the specified node. No information on any database is returned when this status code is generated.Linker/Librarian: Attempt to access data outside of segment bounds, possibly bad object module. If you did not use a segment 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. Linker/Librarian: Virtual address is out of bound.Linker/Librarian: Fatal error. An internal failure has occured. Report the failure to your Unisys Customer Support Center.Linker/Librarian: Too many segment or class names. 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: 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 run 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. See the Development Utilities Programming Guide.Linker/Librarian: Too many public symbols in one module, or 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 the Linker under the Context Manager, reconfigure the partition size  Link the run file on a system with more memoryLinker/Librarian: Too many public symbols in one module, or 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 the Linker under the Context Manager, reconfigure the partition size  Link the run file on a system with more memoryLink7 er/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 moduleLinker/Librarian: Bad Local Segment. Linker discovered segment in second pass that it had not seen or processed correctly in the first pass. Linker/Librarian: Too many common symbols in one module. 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 memoryLinker/Librarian: Bad Common Symbol. Linker discovered Common symbol in second pass that it had not seen or processed correctly in the first pass.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.Linker/Librarian: Data Record Too Large. Data Offset exceeds the current maximum of 64Kb.Linker/Librarian: Segment Reference in Overlay. Object module has code that refers to a segment that is an overlay which is illegal.Linker/Librarian: Selector For Absolute Segment. Object module has code that tries to use the selector of an absolute segment which is illegal.Linker/Librarian: Too many segments or 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 memoryLinker/Librarian: Too many segments or 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 memoryLinker/Librarian: 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 memoryLinker/Librarian: Sort Procedure not Correct. Internal error generated when sorting procedures. Either the sort procedure starts sorting past the end of the allowable range or the flags set for the procedure comparison step are not correct.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 object module, name 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. Cannot open the file. You may have used an illegal library format. Linker/Librarian: 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.Linker/Librarian: Multiple definition of IMPORT procedure. An IMPORT procedure is PUBLIC in more than one object module. Linker/Librarian: Duplicate segment attribute directives, ignored this code segment. Linker/Librarian: Duplicate segment attribute directives, ignored this default data segment.Linker/Librarian: Duplicate segment attribute directives, ignored this segment flag.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 GPAMBeginUnderscore 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: GPAMWA too small.GPAM: 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 to 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.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 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 error. Print Service 2.4: Installation error. Unable to find the operating system tables.GPS 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 in 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. ResumeContext returns this error 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. HeapAlloc returns this error if the heap does not have enough contiguous memory available to satisfy the allocation request. Allocate more space to the heap. Adding 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 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. 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. 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.Device Drivers: An Align or Restart command was attempted upon a device that is not paused. A GPS device must be paused before it can process an Align or Restart command.Device Drivers: Incorrect graphics data was received in the input stream.Device Drivers: An invalid image-mode value was s7 pecified.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 Asynchronous 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.Device Drivers: Busy printing device. The printing device is busy and the device driver is waiting. Printing will resume automatically when the device is ready. 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 command (such as Cancel) cannot be executed when GPS is not processing a document.Device Drivers: A print job must start again from the beginning. This internal error indicates a problem in the software you are using. Contact your Unisys representative.Device Drivers: The request cannot be serviced because the device driver for the requested device is currently being deinstalled from memory.Device Drivers: Job has been cancelled and data will not be output.Device Drivers: Specified file does not exist.GPS releases prior to 2.0: Internal error that indicates a problem in the software you are using. Consult your Unisys representative. GPS 2.0: The font table is full. GPS 2.4: Heap is full. Increase the size of the Font/Graphics Work Area.Device Drivers: The device dependent call DdPutCharG returns this status code when the character does not fit into the current band. This internal error indicates a problem in the software you are using. Consult your Unisys representative. GPS 2.4: Driver is proceeding to the next band.GPS releases prior to 2.0: GPAM data being processed by the GPS device driver contains an invalid GPAM op code. This internal error 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 internal error indicates a problem in the software you are using. Consult your Unisys representative. GPS 2.3: The TIFF data being processed by the device driver is malformed.GPS: Cannot find OS tables. This occurs if the AsyncServer procedures cannot 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 GPS device driver contains malformed CGM records.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 internal error indicates a problem 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 internal error 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 incompatible 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 internal error 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 internal error 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 internal error indicates a problem in the software you are using. Contact your Unisys representative. GPS 2.4: File to be downloaded (such as a font file) does not exist.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 2.4: No such font.GPS Device Drivers: The device driver failed while processing a job change request. This internal error indicates a problem in the software you are using. Contact your Unisys representative. GPS 2.4: Job command error.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 loadable 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. Print Service 2.4: Print Service run file is not compatible with this operating system.GPS 2.0 Routing Switch: The job table does not contain the required job handle. Print Service, Print Sevice 2.4: Bad case data for Job Delete Request.GPS Print Service: Exceeded maximum number of simultaneously open device streams. GPS 1.0 Routing Switch: Either reduce the number of simultaneously 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 is holding a request for an "Unlinked" printer. GPS 2.0 Routing Switch: The request was held at the server for a cluster uplink.Print Service: The request was routed, but not marked, for the Routing Switch uplink. This internal error indicates a problem in the software you are using. Contact your Unisys representative. Print Service 2.4: The request was routed but an error occured during the Print Service uplink. This internal error indicates a software problem. Consult Technical Support.GPS 2.0 Routing Switch: The internal flag indicates that the Routing Switch uplink will process the request. This internal error 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. Print Service 2.4: The request has been forwarded for remote processing.GPS: An invalid request code has been detected. Print Service: The GPS Service is terminating. Requests to a GPS device that is being deinstalled are being returned.  Print Service 2.4: This request cannot be serviced because the Print Service is terminating.GPS Print Service: You cannot deinstall GPS when running on a single partition operating system.GPS Print Service: The device driver has not yet been installed. Device driver is partially installed or is not yet polling its server.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 attempt 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. This error was 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 (default=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. Print Service 2.4: Network device table is full (server only). Reinstall the Print Service and increase the size of the Total number of devices monitored field.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 internal error indicates a problem in the software you are using. Contact your Unisys representative. Bad type case. Location of device in Device table is incorrect. This internal error indicates a problem in the software you are usin8 g. Contact your Unisys representative.GPS Print Service: Bad update case for Network Device Management. This internal error indicates a problem in the software you are using. Contact your Unisys representative.GPS Print Service: Bad query case. This internal error indicates a problem in the software you are using. Contact your Unisys representative. Device configuration record is malformed.GPS Print Service: The device name is not recognized. Network File System: The VPDD cannot find the NPGW to send the print job to. The NPGW name that was entered in the Port field of the VPDD installation is invalid. Reinstall the VPDD with a valid NPGW name (nfsnps).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 Document Products: Bad dictionary version.OFIS Document Products: Bad dictionary environment.OFIS Document Products: Not enough memory.OFIS Document Products: Cannot open dictionary.OFIS Document Products: Bad dictionary I/O.OFIS Document Products: Dictionary word too long.OFIS Document Products: Bad dictionary path.OFIS Document Products: Bad dictionary file.OFIS Document Products: Dictionary temporarily full.OFIS Document Products: Bad dictionary unload.OFIS Document Products: Dictionary inconsistency.OFIS Document Products: Dictionary not available.OFIS Document Products: Need word traits.OFIS Document Products: Word not found.OFIS Document Products: Dictionary Call Not Implemented. Older version of the dictionary does not implement this dictionary request.OFIS Document Products: Too few arguments specified for macro function.OFIS Document Products: Too many arguments specified for macro function.OFIS Document Products: External macro or string function cannot be performed because ICMS is not installed.OFIS Document Products: Bad predicate. OFIS Document Products: External macro or string function argument is too long.OFIS Document Products: Macro or string expression contains an identifier in a context in which identifiers are not allowed.OFIS Document Products: Macro or string expression contains an external function reference in a context in which external function references are not allowed.OFIS Document Products: First macro or string function argument invalid.OFIS Document Products: Second macro function argument invalid.OFIS Document Products: Third macro or string function argument invalid.OFIS Document Products: Object inconsistency. The object anchor has been corrupted.OFIS Document Products: Voice inconsistency. The voice anchor has been corrupted.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 range. 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 keyboard 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. The operating system generates this status code when you attempt to install the Mouse Service. 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 Service 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 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 operating system is not supported. You must have BTOS II, or CTOS 9.5 or higher. This status code is generated when you attempt to 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.Window Services: There are no free windows.Window Services: Windows in use. This status is returned by the DeInstallWindowServices command when there are windows still in use.Window Services: No such window. This status indicates that the specified window handle is not recognized. This status is returned by Window Services procedures which require a window handle as a parameter.Window Services: Window not present. This status indicates that the window's character map is not addressable. This status applies only to partition windows.Window Services: Invalid window parameter. This status indicates that a parameter is invalid, for example, when a window coordinate is given which falls outside of the window's virtual screen. This status is returned by Window Services procedures which require a window descriptor or window relative parameter.Window Services: Not enough memory available. This status is returned by Window Services procedures, such as CreateWindow, that require additional Window Services memory to be allocated.Window Services: Bad memory segment specification. This status is returned by Window Services procedures, such as DestroyWindow, that must specify a memory segment when deallocating Window Services memory.Window Services: Duplicate UIMS query. Windows Services has already queued up the request for GetUIMSEvent by this user. This status code is returned by the request GetUIMSEvent 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.CT-Net, B-NET, BNet II: Request data too large. 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 parameter when installing BNet on the remote node. BNet Net Server: The request received from the Net Agent is too large to fit in the Net Server's buffer. Specify a larger value for the :Max Request Size: parameter when loading the Net Agent and Net Server on the remote node. CT-Net, B-NET, BNet II: No user number available. The Net Server has run out of user numbers to allocate for this request (too many remote users are trying to access a node at the same time). If this error is received regularly you may need to customize the operating system on the remote node reporting the error to increase the number of Net Users.CT-Net, B-NET, 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, BNet 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 8 to a program error or data in memory being written at random.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 field 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. Internal error. CT-Net: 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 the event request on a read does not point to a buffer. Internal error. CT-Net: This could be due to a 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. CT-Net: This could be due to a program error or data in memory being written at random.B-NET, BNet II, CT-Net: File handle for change longevity not found. The file handle specified by ChangeFhLongevity is not in the Net Server's table of remote file handles. Internal error. CT-Net: This could be due to a program error or data in memory being written at random.B-NET, BNet II, CT-Net: No remote file handle available. BNet II: The Net Server cannot support any more remote resources. Increase the value of the :Server Remote Handles: or the [Server Resources] parameter when loading the Net Agent and Net Server on the remote node. CT-Net: An Open request has been processed by the Net Server, but the Net Server cannot support any more remote resources. Increase the number of Server Remote Resources when loading the Net Server on the remote node. Specify 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. CT-Net: This could be due to a 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 in 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. This could be due to a 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.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 is returned when initialization is complete.CT-Net: The CloseAllFiles buffer list is corrupted.CT-Net: A user is terminating and an error occurred in Server Processing.B-Net II: The Net Server has received a request routed by handle, but the handle is not valid for the Net Server. Internal error.B-NET, BNet II, CT-Net: User not waiting for letter of recommendation. Internal error.CT-Net: The file specification is too long for the Net Agent's buffer. Reissue with a shorter length.BNet II Net Session: Resources unavailable. Deinstall and Reinstall BNetSession specifying a larger value for the :Number of buffers: parameter. Note: BNetSession logs this error in the system's PLog; it does not display it on the screen.BNet II Net Session: Message file missing. Reinstall BNetSession from the installation diskette.BNet II Net Session: BNetSession already installed. The BNetSession service is already installed.BNet II Net Session: Number of connections out of range. Install BNetSession specifying a number between 1 and 64 for the :Max Number of Connections: parameter.BNet II Net Session: Number of buffers out of range. Install BNetSession specifying a number between 10 and 256 for the :Number of Buffers: parameter.BNet II Net Session: Buffer size out of range. Install BNetSession specifying a number between 128 and 8192 for the :Buffer Size: parameter.BNet II Net Session: Posted buffers out of range. Install BNetSession specifying a number between 1 and 6 for the :# of Posted Buffers to Transports: parameter.BNet II Net Session: Cannot open CCU file. Run the NCU BNet Connection Configuration Utility function and select the SSAPs and TSAPs appropriate to your environment.BNet II Net Session: Not enough memory. Do one of the following: Install BNetSession specifying a smaller number for the :Buffer Size: or :Number of Buffers: parameters. Reconfigure your system to make more memory available for BNetSession, either by reducing the amount of memory allocated to other applications, or by adding memory to the system.BNet II Net Session: A transport is not installed. Verify that all the Transport services specified in the CCU.cfg file (viewed using the NCU BNet Connection Configuration Utility function) are installed, and are using the SSAPs and TSAPs specified.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. BNet II: The Net Agent has run out of Request Control Blocks. Increase the Agent Client Requests parameter value when you load the Net Agent and Net Server.CT-Net: 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. CT-Net: Invalid data may have been recieved 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 request 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 terminating. 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. CT-Net: This could be due to a 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. B-NET: Increase the Agent Max # Sessions Open parameter when loading the Net Agent. BNet II: Increase the value of the :Agent Connections: or the [Agent Sessions] parameter when loading the Net Agent and Net Server. CT-Net: Increase the value of nSessions in the CT-Net Agent command line.B-NET, CT-Net: Invalid RCB state. Internal error. BNet II: Invalid Rqcb 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 reques9 t). This could be due to a program error or the system may have randomly written data in memory.B-NET, BNet II, CT-Net: Invalid Net Agent connection handle. The Transport Service returned a ConnectionHandle that is not in the Net Agent's table. Internal error. CT-Net: This could be due to a 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 following a session (connection) failure, which causes any open resources to be closed. Also, the caller may not have set the file handle correctly,or might be trying to access it after closing it. Retry the command.BNet II: File handle out of range. CT-Net: Transport failure. BNet II: The Net Agent received a request with a file or resource handle which is out the range of valid numbers. The caller probably did not set the handle correctly. CT-Net: 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. CT-Net: This could be due to a 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 routed 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, CT-Net: No remote file handles available. The Net Agent has run out of remote resource control blocks. BNET: Increase the Agent Max # Remote Resources Open parameter when installing the Net Agent. BNET II: Increase the value of the Agent Resources parameter when loading the Net Agent and Net Server. 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. CT-Net: This could be due to a 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 processor, 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. 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 aborts with this error, it is an internal error.) BNet II: The file handle passed is greater than the number of remote file handles. CT-Net: The system has closed the session (probably due to a timeout).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. CT-Net: This could be due to a program error or data in memory being written at random.B-NET, BNet II, CT-Net: Invalid timeout. The Net Agent 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. CT-Net: This could be due to a 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. CT-Net: 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 initialized. Reassemble 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 was used to unload the Net Agent and Net Server. 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: Net 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 user 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.BNet II: No cluster entry available. The Net Agent on the server cannot handle any more cluster nodes. Increase the :Max Cluster Access Nodes: or the [Number of Cluster Nodes] parameter value when installing the Net Agent and Net Server on the server.BNet II: No cluster session available. The Net Server on the cluster node cannot handle any more sessions, and has rejected this Cluster Access session. Increase the :Server Connections: parameter value when installing the Net Agent and Net Server on the cluster node that you are trying to access. BNet II: Cluster not configured. The Net Agent on the server is not configured to support any cluster nodes. It might have an :Agent Connections: or an [Agent Sessions] parameter value of 0. The Net Agent on the server is not configured to support any cluster nodes. It might have an [Agent Sessions] parameter value of 0.BNet II: Cluster timeout. The cluster node being accessed has failed to post a receive request within a reasonable period of time, and the server has shut down the BNet II connection to it. There might be a deadlock involving cluster buffers (that is, X blocks), especially if two cluster nodes are accessing each other. Try increasing the number of X blocks (Number parameter) in the server. (For the XE-500 Shared Resource Processor this requires editing the system configuration files; for the workstation server, this requires customizing the server operating system). It may also be necessary to increase the number of X blocks that can be used by a single workstation (increase the MaxXBlocksOut parameter). This status code might also indicate that the X block size (Size parameter) on the server is not large enough to support Cluster Access. In that case, the cluster will probably have written a status code 45 to the system log file. Try reducing the :Cluster Access Large X-Block Size: parameter when installing the Net Agent and server on the client workstation.BNet II: Cluster went down. The cluster node being accessed has gone down; or the cluster connection to it has failed; or the node has been disabled.BNet II: Wrong Session Version. BNet is configured to access OSI Session 2.0 but that version is not installed.B-NET, BNet II, CT-Net: Bad heap. The internal heap check, which is performed when doing a heap manipulation, has determined that the heap is not consistent with itself.Virtual Code Segment Management: Overlay already in memory.Virtual Code Segment Management: Next overlay does not fit. The swap buffer 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 because 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. Link time errors reported in the run file load map may have caused this problem.Configuration Management: The configuration exceeds 32 hardware modules. This status code9  may indicate an X-Bus problem or a defective hardware module.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. 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 internal error indicates a problem with the software you are using.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 picture 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 picture 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 the 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 file.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 number 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.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. Open 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 limited 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 requires 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.BTOS 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.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, SetFirstLabel, or SetNextLabel to set the current label.BTOS Graphics II, Graphics 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 would 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-graphics 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 wrongly 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 tr: ansformed object falls outside the world coordinate area, you must supply new transformation parameters. Default world coordinate area is (0,0) through (100,n). See the graphics programming manual to obtain the value of n for your workstation. Include 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 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 the 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 status 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.OFIS Document Products, 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 Library: 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.Graphics Library: SetAlphaColorDefault returns this status code if the parameter's value (bmode) is any value other than zero.BTOS Graphics II: Insufficient memory for an area fill. OFIS Document Products: Picture status warning. This error is returned by the DisplayPicture operation when the picture area could not be filled or a font was not available. As much of the picture is completed as is possible, however.BTOS Graphics II, Graphics Library, OFIS Document Products: Invalid plane was requested. This code is returned if the plane set in SetRasterSourcePlane or SetRasterDestinationPlane does not exist on your workstation. See the graphics documentation to determine the hardware requirements for your workstation.BTOS Graphics II, Graphics Library, OFIS Document Products: Invalid op code was supplied. BTOS Graphics II: An invalid operation code was supplied in DoRasterOp (for wSourceOperation or wDestinationOperation). See the graphics programming manual to be sure that you have supplied the proper operation code for DoRasterOp. Graphics Library, OFIS Document Products: 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. See 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 with the release level.) Reformat the bar chart using fewer data groups. See 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. See the documentation for the specific release of the application for the maximum number of pie segments allowed. OFIS Graphics, Art Designer: Max number of legends for line chart exceeded 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 message from the Inter-Context Message Service (ICMS). Consult the manual for the application that is sending 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 interface 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. OFIS Document Products: Invalid CGI device. This is an internal Document Designer error and should not occur. Call Technical Support.OFIS Graphics, Art Designer, OFIS Document Products: No picture files in this directory. In OFIS Graphics and Art Designer, this message is displayed when you use the View Files function and it finds no files with a .pic file name extension. In OFIS Document Products, you may also get the message "Object out of range." This indicates an internal 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 character 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 Support 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.BTOS Graphics II, Art Designer: Invalid printer was specified. A printer was specified incorrectly in SetPlotterDevice. Printer names are limited to 50 characters. Shorten the printer name. OFIS Graphics: Bad Printer Specification.BTOS 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 Graphics 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 speci: fication must 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. See 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. BTOS 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 generated 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 count 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, which 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. OFIS Document Products: Incomplete CGM file. This error occurs when the CGM Interpreter reaches the end of file before the End Metafile opcode. The CGM file has either been written incorrectly due to an internal error, or, if foreign, is in an invalid CGM file format.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 count 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 devices 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 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. No spooler was 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 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 path 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 continue, 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 Unisys 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 incorrect 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 specified 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 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.) See 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. See the BTOS Draw Operations Guide. If that does not work, contact your Unisys representative. OFIS Graphics, Art Designer: Too many points drawn. A connected line or sketched line was drawn with 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, grid 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 moved outside of the chart's limits. BTOS Draw: Function key is not assigned. You pressed a function key that does not have a template object assigned to it. Press the correct function key; you may need to search for the tem; plate 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 cannot 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, Art 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. BTOS 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 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 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: 720x34880LocSys.Icon or 1024x76880LocSys.Icon  Art Designer: 720x348ArtChartIcons.lib or 1024x768ArtChartIcons.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 720x348ArtChartIcons.lib or 1024x768ArtChartIcons.lib is bad. Recopy the file from the distribution disk of into [Sys].OFIS Graphics, Art Designer: Bad Locator Cursor File. The file 720x34880LocSys.Icon or 1024x76880LocSys.Icon is 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. See the documentation for the specific release of the application for the maximum number data groups allowed. OFIS Graphics, Art Designer: Bad System Font file. Depending on the resolution of the monitor being used, the file [Sys]720x34880Sys.font or [Sys]1024x76880Sys.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, Art 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 - Only 200 names can be listed. 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 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.OFIS Graphics, Art Designer: No picture information 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.OFIS Graphics, Art Designer: Feature not implemented. Displayed when any selected feature is not coded into the current release of the run file.CCGI+: No graphics available. This workstation does not have the necessary graphics hardware. OFIS Document Products: 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 Document Products: Bad CGI state. This indicates a software error. Call Technical Support.CCGI+: CCGI+ previously initialized. A call to cgiInitialize has already been made and you are attempting to reinitialize the system. You must make a call to cgiTerminate before you can make the cgiInitialize call again. OFIS Document Products: 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 cgiInitialize. The system must be successfully initialized before other library calls can be used. OFIS Document Products: Invalid Link or signature. The verification mechanism of an internal 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 internal error 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 Document Products: Invalid SuperVAM device or object. A device handle or object handle given to a SuperVAM procedure does not describe a valid SuperVAM device or object.CCGI+: Insufficient memory. No more memory is available to perform the requested operation. Allocate more memory on initialization or change your partition size. OFIS Document Products: 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 cgiOpenWk, 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. See 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. See the CCGI+ Programmer's Guide for parameter restrictions.CCGI+: Invalid bitmap handle. The bitmap handle you have passed is not valid. Confirm that it is a handle returned from a s; uccessful cgiOpenWk of a bitmap device, or a successful cgiCreateBitMap.CCGI+: Invalid cursor handle. The cursor handle you have passed is not valid. Confirm that it is a handle returned from a successful cgiOpenCursor.CCGI+: Value out of number range. The value has been calculated to fall outside the CCGI+ maximum integer range of -32767 to 32767. Choose a 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 resolution80sys.font (for example, 1024x76880Sys.font). It should reside in your [Sys] directory.CCGI+: Invalid CCGI+ device. The device type specified as input to cgiOpenWk was not recognized. Confirm that it is one of the valid device types specified in the CCGI+ Programming Guide.CCGI+: Insufficient cursors enabled. An attempt has been made to open more cursors than the maximum allowed (defined as input to cgiInitialize). 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 cgiInitialize 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 cgiInitialize, 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 appropriate flag to cgiInitialize 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 per 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 bytes. 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 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 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 call. 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 cgiViewport 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 allowed 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 cgiViewport 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.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. 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 given 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.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.CCGI+: Memory Handling Error. Check code logic for overwriting, or increase memory available for CCGI+. OFIS Document Products: Too many Virtual Memory files open. Close some files and save before opening more files.CCGI+: Memory Handling Error. Check code logic for overwriting, or increase memory available for CCGI+. OFIS Document Products: Virtual file address specified is invalid. Virtual file address specified in Virtual Memory operation contains an invalid file number.CCGI+: Memory Handling Error. Check code logic for overwriting, or increase memory available for CCGI+. OFIS Document Products: 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+. OFIS Document Products: Read only buffer. Attempt to write to a Virtual Memory buffer which is available for reading only.CCGI+: Memory Handling Error. Check code logic for overwriting, or increase memory available for CCGI+. OFIS Document Products: 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+. OFIS Document Products: No free buffer ID. Operation failed because all Virtual Memory buffers are locked.CCGI+: Memory Handling Error. Check code logic for overwriting, or increase memory available for CCGI+. OFIS Document Products: Bad buffer ID. Invalid VM buffer block ID.CCGI+: Memory Handling Error. Check code logic for overwriting, or increase memory available for CCGI+. OFIS Document Products: Inconsistency in VM data structures.CCGI+: Bad heap selector. OFIS Document Products, OFIS Document Products: Bad address. The selector for the pointer does not exist in the heap selector table. This probably indicates an invalid heap pointer or heap corruption. This is an internal error related to memory and heap management in the software. Call Technical Support.CCGI+: Heap selector table overflow. OFIS Document Products: 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+, OFIS Document Products: Heap inconsistency. Inconsistency in heap data structures. This is an internal error related to memory and heap management in the software. Call Technical Support.CCGI+, OFIS Document Products: 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 to memory and heap management in the software. It probably indicates software modifying memory outside of the allocated heap node. Call Technical Support. OFIS Document Products: Bad node link.CCGI+, OFIS Document Products, 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. It may indicate that the software has overwritten heap memory. Call Technical Support.CCGI+, OFIS Document Products, OFIS Graphics: Bad heap node tag. Invalid tag in heap node. This probably indicates a heap corruption.CCGI+, OFIS Document Products, OFIS Graphics: Bad heap finger. The node handle in a heap node does not match the index into the node handle mapping table. This indicates a heap inconsistency. This is an internal error related to memory and heap management in the software. Call Technical Support.CCGI+, OFIS Document Products, 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.CCGI+, OFIS Document Products, OFIS Graphics: Lock count error. Node lock count overflow or underflow. This indicates a software error, such as mismatched node allocations and releases. This is an internal error related to memory and heap management in the software. Call Technical Support.CCGI+, OFIS Document Products: 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 memory and heap management in the software. Call Technical Support.CCGI+, OFIS Document Products, 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+, OFIS Document Products: Heap node too large. An attempt to allocate or grow a heap node failed because the size requested is larger than the maximum node size. This is an internal error related to memory and heap management in the software. Call Technical Support. If this error occurs in OFIS Document Products, save your edits more often.CCGI+, OFIS Document Products: 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 an OFIS Document Product, save your edits more often. This is an internal error related to memory and heap management 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. 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 Technical Support.OFIS Document Products: 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.OFIS Document Products: 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 picked. Pick a chart and try again.OFIS Document Products: No text found (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.OFIS Document Products: 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.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 indicates 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 hardware 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 ready. The DataSetReady (DSR) signal was not set when expected.Communications: Illogical device status. This internal error indicates a problem in the software you are using. Communications: No data. This internal error indicates a problem in the software you are using. Communications: Terminate read or internal consistency check. This internal error indicates a problem in the software you are using. Communications: Break or selected. A break character may have been received. This internal error 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.Server/Client Workstation Communications: Timeout error. A workstation no longer responds to polling. Communications between the server and client workstation are corrupted or nonexistent. Possible causes include improperly terminated cluster lines, excessive cluster line lengths, a faulty cluster port, and faulty cable. Daisy-chain cluster cable overall length limits are: 1200 feet at 307Kbps or 1.8Mbps cluster line speed, and 600 feet at 3.68Mbps cluster line speed. Note that these maximums can be further reduced depending on your cluster configuration and the cluster support features of your client and server hardware. Make sure that cluster lines are properly terminated. Check that all cluster cables are properly connected and not defective. BSC 2780/3780 RJE: The host computer failed to respond to 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 length 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/Client Workstation communications: Invalid state. Run the crash dump analyzer if available. The error condition causes termination of the operating system and an automatic reload. Server/Client workstation communications: Communications hardware failure. Cluster line is reset. The most common cause of this < failure is daisy-chain cluster cabling which exceeds the overall line length limits. Daisy-chain cluster cable overall length limits are: 1200 feet at 1.8Mbps cluster line speed, and 600 feet at 3.68Mbps cluster line speed. Note that these maximums can be further reduced depending on your cluster configuration and the cluster support features of your client and server hardware. Other possible causes of this error include: Faulty cluster cabling. A software error. Server going off-line and on-line again (protected mode). More than one server connected to the physical cluster. Excessive multibus DMA loading. Run the workstation hardware diagnostics.Server/Client Workstation Communications: Protocol failure detected by the server. A client workstation no longer follows proper protocol procedure. The frame received does not match the expected frame type. This error condition causes termination of the operating system and an automatic reload. Possible causes include: improperly terminated cluster lines, excessive cluster line lengths, a faulty cluster port, faulty cluster cable, or more than one server connected to the physical cluster. Shared resource processor: Protocol failure. Possible causes include improperly terminated cluster lines, a faulty RS-422 port on the processor, and faulty cable. Daisy-chain cluster cable overall length limits are: 1200 feet at 307Kbps or 1.8Mbps cluster line speed, and 600 feet at 3.68Mbps cluster line speed. Note that these maximums can be further reduced depending on your cluster configuration and the cluster support features of your client and server hardware. 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/Client Workstation communications: Invalid Direct Memory Access (DMA) buffer address. An error in system initialization has caused the DMA buffer of the Client workstation Agent Service Process to fall outside the low-order 128K bytes of memory or on an odd-byte boundary. Server/Client 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 internal error indicates a problem in the software you are using. Consult the Unisys Customer Support Center. Server/Client Workstation communications: Invalid Command bit (Busy Bit) I/O. This internal error indicates a problem in the software you are using. Consult the Unisys Customer Support Center.Server/Client Workstation communications: An unexpected interrupt was detected while attempting to transmit or receive data.Server/Client Workstation communications: Transmit DMA underrun.Server/Client workstation communications: Protocol failure detected by a client workstation. The most common cause of this failure is daisy-chain cluster cabling which exceeds the overall line length limits. Daisy-chain cluster cable overall length limits are: 1200 feet at 1.8Mbps cluster line speed, and 600 feet at 3.68Mbps cluster line speed. Note that these maximums can be further reduced depending on your cluster configuration and the cluster support features of your client and server hardware. Other possible causes of this error include: Faulty cluster cabling. A software error. Server going off-line and on-line again (protected mode). More than one server connected to the physical cluster. Excessive multibus DMA loading. Server/Client Workstation communications: An error in the hardware (SIO or cabling) on the cluster line has caused a temporary inability of the client workstation to communicate with the server workstation.Server/Client Workstation communications: Server workstation disconnect. An unrecoverable protocol failure has occurred at the server workstation and further communications with this workstation have ceased. The most likely causes 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 loadingServer/Client Workstation communications: Request block error. An improperly formatted request block was sent by a workstation.Server/Client Workstation communications: Read not complete. The system received an interrupt for Read Complete, but the Read Complete bit is not set. Shared Resource Processor: Timer failure.Server/Client Workstation communications: Bootstrap failure. A protocol failure occurred during the bootstrap process.Server/Client 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 workstation specified too few IDs for the cluster configuration.Server/Client 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/Client 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 on the same cluster.Server/Client Workstation communications: Bad length. The length of the data received did not match the length of the data sent by the client workstation. This could be due to a hardware failure.Server/Client 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/Client 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/Client 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/Client Workstation communications: Reject error. A reject (REJ) was received from the client workstation. The workstation detected a protocol violation and sent a reject to the server.Server/Client Workstation communications: Abort. An RcvAbort was detected while reading from the client workstation.Server/Client 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/Client Workstation communications: SetUpCommDma read back a different DMA address than was just written.BSC 2780/3780 RJE, BSC 3270: Abort. The host received an EOT (End of Transmission) 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 to 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 3270: 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 characters 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 RJE, 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/3780 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 all subsequent requests must match the one returned from Open3270Emulator.BSC 3270: Too ma= ny 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 successfully 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 Close3270Emulator.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. Transmission 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 communications 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. 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 through 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, the 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 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 executed. 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 operating 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.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 the host.Communications Interrupt Handlers: Invalid line number. Workstation: The line number specified in InitCommLine and ResetCommLine must be either 0 or 1. If you have a DCX or XC-002, see the System Administration 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 InitCommLine 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. For BMULTI, this status code may also indicate that BMULTI attempted to use X.21 on a channel that does not support X.21. If you are using a server 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 request was made to start programmable terminal emulation on a client workstation that is already in programmable terminal emulation mode.Communications Interrupt Handlers: A request was made to stop programmable terminal emulation on a client workstation that was not in programmable terminal emulation mode.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 PDN 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 exists at the physical level or the link level. 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 operation 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 request 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 determine 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 virtual 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 digitsX.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 NotifyNextIncomingCall op= eration 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 been 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.25: DCE clear.  The PDN cleared the call that was on this virtual 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 lost.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 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 or an OpenX25PermanentVC operation was received for a nonpermanent virtual circuitX.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, AcceptX25Call, ClearX25CallNet, ClearX25VC, or AcceptX25CallNet 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 system 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 release. See the 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 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: 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 file. Only modulus 8 is supported.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.21 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 Service 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.LAPB, 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.X.25: XE service ID is invalid. The entry in the Location parameter is incorrect (for example, the XE Board name is 12 or more characters, including the brackets [ ]).X.25: The communications channel entered in the link level configuration file is not a valid value.X.25: Invalid subaddress value. The subaddress must be from zero to four digits.X.25: Access Point unavailable. The number of access points opened over the packet layer is already equivalent to the number the packet layer is configured to support. If the number is less than 12, you can deinstall the packet and reconfigure it to support a higher number of access points. Otherwise, wait for an access point to become available.X.25: Invalid bType, bFunction, or wType value. The value assigned to this variable is not in the range of values prescribed. This error can be returned to the ControlX25AccessPoint, X25Function, and X25GroupWrite procedures.X.25: The physical call failed after retry.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: CommIOP channel hold. There is a carrier problem on one of the CommIOP channels. Disconnect the client workstations one at a time to determine which is failing.CommIOP: CommIOP command failure. The CommIOP returned erroneous control information to the server.CommIOP: Invalid master workstation to CommIOP command. The CommIOP did not recognize the command from the server.CommIOP: CommIOP bootstrap checksum failure. The CommIOP checksum test failed while loading its code file from the server. 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.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.CommIOP: CommIOP handler timeout. The CommIOP did not get proper status information. The most probable cause is a software problem in the server 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.CommIOP: 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.CommIOP: CommIOP timer failure.  The timer hardware on the CommIOP failed the initialization tests.CommIOP: CommIOP DMA failure. The Direct 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.CommIOP: The cluster is too heavily loaded when the GetClusterStatus operation is invoked.CommIOP: Invalid baud rate specified in SetBaudRate operation.CommIOP: Client workstation (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.SNA Network Gateway, SNA/X.25 Gateway, SNA Transport: Interconnecting line failure or inactive line. One of the following 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 allowedSNA Network Gateway, 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 has 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 Gateway, 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 Transport: 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: 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 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, 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 Transport: 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 maxout 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, SNA 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 Network 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 either 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 specified for the maximum PIU size. The maximum PIU size varies with the release. See the 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.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 entered 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 entrie> s 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. Number(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 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. See the 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 CRT for SNA 3270 Emulator, CS3270 for ClusterShare SNA 3270) with a valid numeric lock parameter value.SNA 3270 Emulator: Invalid Physical Unit (PU) Number supplied. The PU Number is either not numeric or not in the valid range (1-4).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 command with a valid file name.SNA 3270, ClusterShare SNA 3270: SNA Network Gateway not installed. SNA 3270 Emulator: The SNA Network 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 command 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.SNA 3270 Emulator: Time Out occurred. No data was received from the host computer during the time period specified in procedures with a Time Out parameter. This condition 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, for 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 RESET 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 specified with the Ident function. Press RESET (F1) to clear the condition.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 unexpected 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 Net Agent, Net Server, or (with BNet II) the Naming Service 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: Invalid 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 deactivated.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 (BNET Transport) Net Transport Service has temporarily run short of buffers and has to discard packets.CT-Net: 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, BNet 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.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: Invalid 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.BNet Classic Transport: Invalid entry. A non-numeric value was entered in a numeric field in the transport service configuration file.CT-Net: Invalid channel specified. CT-Net: Not yes or no. BNet II: "Yes" or "no" not entered as connection parameter in netcfg.sys. NAC.run returns an error code 8932 if it encounters a netcfg.sys connection parameter value of anything other than yes or no. This is an internal error.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 Configuration] parameter is either 0 or greater than 16.B-NE? T, BNet II, CT-Net, DCA STI: 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. BNet II: If this status code is encountered when you are trying to access a node reachable by means of OSI services or Extended Routing, it may mean that the Naming Service is not loaded or is not accessible. If this status code is encountered when you are trying to load the classic BNET Transport, it may mean that the node name input is invalid. This code might be returned even if the classic BNET Transport is not loaded. If this status code is encountered when you are trying to access a cluster node, it may mean that that node is not currently operational. DCA STI: DCA STI did not recognize a node name. This error is returned to the Naming Server Query request if the node 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 the media service may have failed to install.CT-Net: 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 media. 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 an Adjacent Node or User Node Table entry when that table is full. Increase 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.B-NET, BNet II, CT-Net: Duplicate media. An attempt is being made to add a media configuration table entry for a media which has already been configured, or two media services have been loaded with the same Install Number.CT-Net: Transport Service stopped.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.B-NET, BNet II, CT-Net: Duplicate entry in the configuration file. The configuration file contains two entries for a keyword that does not allow duplicate entries.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. The remote node's Net Server might not be able to support any more sessions. Try increasing the value of the :Server Connections: parameter when loading the Net Agent and Net Server. BNET: Try increasing the number of sessions when installing the Net Server. BNet II: Try increasing the value of the [Server Sessions] parameter when loading the Net Agent and Net Server.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.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.B-NET, BNet II, CT-Net: Normal disconnect. This can occur if the remote Net Server aborts or is deinstalled. BNet II: This can occur if the remote Net Agent and Net Server aborts or is unloaded.B-NET, BNet 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 connection 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. CT-Net: Decrease the KBPS parameter used during media configuration in NCC.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. CT-Net: 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)  Someone at another client workstation is using the dial-up to communicate with a different node (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 large.CT-Net: Transport Protocol provider initiated.CT-Net: Transport Protocol user initiated.CT-Net: Transport Protocol negotiation.BNET, CT-Net: No Send Route entry. BNet II: Remote node cannot be reached. The requested node, although known, cannot currently be reached because something is down. This code might be returned even if the Net Transport is not loaded. BNet II: This can be caused by congestion. If subsequent retries fail, troubleshoot. To troubleshoot 8936 and 8992 errors, you must determine how the connection is normally made. If both nodes are on the LAN, use the Network Configuration Utility (NCU) to check the NCU Address Configuration Tools node table. If the target node appears, then check that it is up (check the line also) and that the Net Agent and Net Server is loaded. If the target node does not appear, use the LDM to try to echo to it. If the echo fails, something is wrong with the LAN hardware or software. If the echo is successful, something is wrong with BNet II or OSI Session. 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 Transport and media services without using extended routing, and you get an erc 8936, the node probably does not appear in the User Node Configuration Table. If the target node is normally accessed over a series of permanent WAN connections (RS-232 direct cables and leased lines, and X.25 PVCs) then check the Network Control Center (NCC) Remote Status display. If the node does not appear in that table, then either it or an intermediate node or the connection is down. Trace the path through intermediate nodes by examining the Remote Status display at 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 Configuration Table. If the target node is accessed using extended routing, including source nodes with only LAN connections, then determine the intermediate node. Check that the initiati? ng 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. If LAN connections are involved, check OSILocalNSAPCnfg.sys and OSILocalESISCnfg.sys for correct addressing.CT-Net: No request blocks.B-NET, BNet II, CT-Net: Segmentation not implemented. CT-Net: You are trying to use a route entry that does not exist. Internal error.B-NET, BNet II, CT-Net: Bad Internet Protocol Checksum. Internal error.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. Tape: Timed out waiting for expected Data Busy false.Sequential Access: Operation timed out. The last command issued to the sequential access device did not complete within the time allotted. This sometimes indicates a problem that can be corrected by manual intervention but more often indicates a hardware error or a difficulty with the usability of the medium in the sequential access device.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 true. 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.Sequential Access: The medium in the squential access device is blank (it contains no recorded data). Blank medium was encountered where recorded data was expected. Tape: Tape is blank .... it 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 selected the wrong QIC format.Tape: An error occurred in the micro-diagnostic.Sequential Access: Early-warning end-of-medium encountered. The medium is positioned in the early-warning zone that is located before physical end-of-medium. This condition is not reported for read operations unless another error is present as well. 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 remaining 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.Sequential Access: A hardware or software error occurred that could not be eliminated by retry. This error is most frequently caused by bad media. Replace the tape media. If that does not correct the problem, clean the read/write heads in the tape drive. If the error continues to occur, after taking these actions, suspect a faulty tape drive. 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.Sequential Access: Insufficient space available in the buffer pool. The amount of buffer space requested in a SeqAccessOpen request cannot be satisfied because the unallocated space in the service buffer pool is too small. Possible causes are too many sequential access devices opened simultaneously or an insufficient buffer pool size parameter at the time the Sequential Access service was installed. Tape: For a minimaster. There is no free preallocated data buffer. Tape Streamer Utilities 7.1: No buffer allocated to tape server. See the Install QicTape Server command in the 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 on 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.Sequential Access, Tape: Device is not ready. The device is not on-line, does not contain any medium, or is busy (for example, rewinding).Sequential Access, Tape: A write was attempted but the medium is write-protected. A data transfer operation to the medium was attempted, but the medium is protected. For quarter-inch cartridge, the protection control is set to Safe; for DDS, the write-protect tab is in the open position or for half-inch reel-to-reel tape no write enable ring has been inserted.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.Sequential Access, Tape: A file mark was encountered during a read operation. A read or space record(s) operation was terminated by a file mark. The residual count indicates the amount of data successfully read from the medium before the file mark.Sequential Access: Invalid mode parameters. The mode parameters supplied with a SeqAccessOpen or SeqAccessModeSet operation are invalid or inconsistent. Tape: An error in specifying a parameter was detected by the Tapemaster, or for the Tape Streamer Utility, the tape controller. The usual cause is a byte count that is zero or too large.Sequential Access: Variable length records not supported by tape byte streams. There is an error in the configuration file. The Tape Byte Stream supports only fixed-length records. For example, the MinRecordSize and MaxRecordSize should be equal, and the BlockSize should be a multiple of the record size.Sequential Access, Tape: A controller or device hardware error has occurred. The hardware interface has not responded as designed to a command or status request issued by the software. Consult Technical Support; diagnostic software may need to be run to isolate the problem.Tape: A streaming read or write operation was terminated by the operating system or disk.Sequential Access Service: Noncontiguous DMA. The Sequential Access Service was unable to install because it could not allocate a contiguous area in memory large enough for the buffer pool. To correct this problem try to reduce the amount of system memory in use at the time of installation. For example, deinstall one or more other system services, or change the order of installation of system services at system initialization. Adding more memory to the system is also an alternative.Sequential Access: Invalid sequential access handle. Tape: Bad tape handle. A tape or sequential access request was made with an invalid handle. This is typically caused by an error in a user program. It may also occur when using the tape or sequential access backup utilities, if the client workstation was taken off-line during the backup operation.Sequential Access: Invalid sequential access request. Tape: Bad tape parameters. A tape or sequential access request has invalid parameters. These include: zero-length buffers, requests to read or write zero records, and so on.Tape: No free tape control blocks. This internal error indicates a problem with the software you are using. Consult Technical Support. Shared resource processor: The half-inch tape server ran out of device control blocks. Sequential Access: Invalid sequential access device or file specification. Tape: Bad tape file name. The tape or sequential access specification supplied is invalid. Tape and Sequential access specifications have the form [Device], [Device]+, or [Device]N, as in the examples [QIC], [DDS]+ or [TAPE]5. The number N indicates the relative file position on the medium starting with file zero. If N is omitted it is assumed to be zero. The special character "+" in the file number position indicates "append" after the last file already recorded on the medium. Tape Streamer Utilities 7.1: Invalid tape name for the currently installed server. The tape name supplied was invalid for the currently installed server. Sequential Access: The device is already in use. A SeqAccessOpen request was made for a device already opened by another user. 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.Sequential Access: The device is opened for read operations, only. A sequential access operation that would cause data transfer to the medium has been made for a device that has been opened in "modeRead". This is normally a user program error. The device should be opened "modeModify" if both read and write operations are to be performed. 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 cartridge 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. Tape Streamer Utilities: An unrecognized command was issued as a tape operation request. This 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.Sequential Access: Invalid sequential access mode. Tape: Unknown tape mode. Tapes and Sequential access devices may be opened in modeRead ("mr") or modeModify ("mm"), only.Sequential Access, Tape: Device operation(s) are outstanding. The tape or sequential access device cannot be closed until all sequential access 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. Alternatively, install the Tape Service, then run the Tape utility again. Sequential Access: Record is truncated. The buffer provided was not large enough for the record read from the medium. The residual of the record may still be in the buffers of the sequential access service and may be recovered by a subsequent read operation.Tape: The QIC tape service is in use. A user, perhaps a client workstation, is using the installed QIC service.Archive Utilities: Internal archive dataset format is corrupted. The Standard Software 12.0-style archive dataset on the tape is internally inconsistent and no more data may be recovered. 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.Sequential Access, Tape: Invalid medium position. The medium in the tape or sequential access device is neither at load point nor at the start of a file.Archive Utilities, Tape: Invalid archive dataset volume. The sequential access volume (QIC cartridge, DDS cassette or half-inch tape reel) is not a part of the archive dataset currently being restored. Verify that you have mounted the correct volume. 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.Archive Utilities: Invalid archive dataset sequence. The sequential access volume (QIC cartridge, DDS cassette or half-inch tape reel) is not in the expected sequence for the archive dataset currently being restored. For example, volume 3 was expected but volume 5 is actually mounted. Verify that you have mounted the correct volume.Archive Utilities: Invalid device configuration file. The sequential access device configuration file is invalid. Use the Configure Sequential Access Device command or the Tape Streamer Utility's Configure File command to create or edit the configuration file.Tape: Missing Tape Configuration file. The Tape Configuration file cannot be found or is inaccessible. Use the Tape Configure File command to create the tape configuration file.Archive Utilities: Invalid record size. Record sizes for tapes created and read by the archive utilities must be 512. The block sizes for the tapes may be any multiple of 512 smaller than 65,536. Tape: Bad tape record size. Tape records must be between 1024 and 16384 bytes for backup, and between 2 and 16384 bytes for tape byte streams.Sequential Access, Tape: Wrong hardware, or hardware is absent. An attempt to install the Sequential Access or Tape service has been made on a processor or system that either cannot have the hardware requested or the hardware requested is not present. For quarter-inch cartridge on a workstation, there may be more than on HB-001 module present. For quarter-inch cartridge (non-SCSI) on an SRP, the slot number specified for the QIC interface board may be incorrect or the QIC interface board may not be installed. For half-inch tape on a Shared Resource Processor (non-SCSI), the sequential access service must be installed on a DP or SP board within the Shared Resource Processor.Sequential Access, Tape: XBIF not installed. The X-Bus interrupt handler, XBIF.Run, has not been installed. You must install XBIF before using non-SCSI quarter-inch cartridge modules on a workstation.Tape: Tape controller failure. The tape controller is not responding correctly. Run the Magtape or tape Diagnostic to diagnose the failure. Sequential Access service: Device buffer not empty. The requested operation cannot be performed because there is user data in the buffer for the device, the Sequential Access Service, or both. Tape: Tape controller failure.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.Sequential Access, Tape: Bad alignment of user-supplied data buffer. Data buffers must be aligned on word boundaries.Tape: The user request specified a data buffer size larger than that specified at tape service installation time.Sequential Access, Tape: Medium was removed. The medium was removed from a sequential access device after the device was opened by a user. If this message appears when a QIC tape cartridge is in place, the cartridge may be broken.Sequential Access: An illegal command was issued to the sequential access device. Tape: An illegal command was sent to the tape controller. This internal error indicates a problem with the software you are using. Consult Technical Support. This error also occasionally indicates that a half-inch tape drive is offline; try putting the device back on-line.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.Sequential Access, Tape: The physical end-of-medium 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 BootTape Table Of Contents does not contain a valid :FileType: token (keyword) for the target file.Sequential Access: Buffer too small for tape operations. For tape byte streams, the buffer provided exclusively for byte stream operations should be at least 1024 bytes. Providing a bigger buffer improves the efficiency of byte stream operations. The buffer size should be at least as large as the MinRecordSize specified in the configuration 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 accomodate requested record size. Install more RAM or decrease the amount of RAM in use. See 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.Sequential Access: The requested operation cannot be performed because there is user data in the buffer for the device, the Sequential Access Service, or both.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 is 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 after 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  A@ ttempt 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 modeTape 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 resetSequential Access: Device status unavailable. Tape Streamer Utilities 7.1: Unable to read tape status after exception.Tape Streamer Utilities 7.1: This error indicates one of the following:  Ready not asserted during command execution  Ready not asserted at beginning of command executionSequential Access: Sequential access device has experienced an unexpected power-on or reset. Tape Streamer Utilities 7.1: Tape status shows unexpected power-on or 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 Utilities 7.1: Bad user number. The user number received is 0FFFFh, which is invalid.Sequential Access: The device is busy. The sequential access device cannot accept any commands because it is still performing an earlier command (such as rewind).Sequential Access: Command aborted by the device.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 service residesTape: 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: 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: Cannot 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 currently 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 be sent because of an internal software error. Call Technical Support.SNA RJE: LogOn ID is out of range. 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 Logical Unit (MLU) manager service is down.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 cannot be terminated because the indicated name does not match any LU-LU session.SNA RJE: Invalid status request. Invalid status type for Status request.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.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 specified 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 (larger 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.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 DFCSTSNComplete 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.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.SNA LUIS: Invalid DFC Command. SNA LUIS 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.SNA 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 RecoveA ry (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 session 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: Applications 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 WriteDFCRU, 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 configuration. 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 error.SNA LUIS: No Headers. Returned by SNA 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 Transport: 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 internal error indicates a problem with the software you are using. Consult Technical Support. SNA Transport: This error code is returned only for foreground programs like SNA Status Monitor.SNA Multiline Gateway: The PU number specified in the Notify command is invalid. The specified PU number should be less than 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 many 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 notify 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 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 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 be 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 internal error indicates 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 internal error indicates a problem in the software you are using. Consult Technical Support.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 Transport: 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: A ReadREQMS/ReadNmvt request is already 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 associated with the request.SNA Network Gateway, SNA/X.25 Gateway, SNA Transport: A request for CNM service 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 from 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.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.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 MA apped) have to 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.SNA DIA: Sync level not supported. Sense data 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 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 deallocated (ended) after use by a transaction program. A deallocation on an already deallocated program is an error condition. Do not de-allocate.SNA DIA: Invalid parameter in Allocate request. Verify all the parameters in Allocate request.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 the parameters; if the parameters appear correct, consult the host system operator.SNA DIA: Illegal state. This is an internal error. Retry; if repeated attempts fail, contact Technical Support.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 correct 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.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-Mail: 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 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 Institute 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 envelope.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 call to InitVm specifies more than 64 short buffers or 8 long buffers.OFIS Mail, CT-Mail: 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. A read or write call specified an invalid file handle.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 range 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 massages that are no longer needed. Use the Reorganize command (see 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 attempt 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 processes 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 organization update.OFIS Mail, CT-MB ail: 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 entry. 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 different 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. OFIS Mail: Logical File Address is past end of folder.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 client workstation, reset the server, 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 system 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 to 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. The 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 whether 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 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. 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 file.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, CT-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 distribution 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 list 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 for 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 items 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 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 encountered 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 remove the appropriate status window from the Interactive Mail Manager 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. 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 record 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-Mail: 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 eigB ht Communications Managers in your Mail Center. OFIS Mail, CT-Mail: Center not removed. An error was encountered in removing the specified Center.OFIS Mail, CT-Mail: Invalid key. The specified key is zero.OFIS Mail, CT-Mail: Invalid 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 Mail 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 Server 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 number 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.OFIS 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 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. The 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 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 the Mail Center configuration now. Try again later.OFIS Mail, CT-Mail: Cannot reset Mail Server. You cannot deinstall, suspend, or resume the Mail Server from a client 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: Synchronization 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 recipient 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 Server 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 (see the 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 message 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.cnfg 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. 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.OFIS Mail, CT-Mail: Key found. Found the index key to the name registry.OFIS 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 Mail, 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 cancelled. 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 C record cannot be changed. You cannot move the mailbox path of the Administrator or internal Mail Server record. The user 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 organization. The center cannot be removed because it is a member of an organization of which the local center is not the capital. (Internal) OSI Message Handling System, OFIS Access-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 in 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-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-X.400: No Such OSI Path. The OSI Path name you entered is not registered with your Mail Center. Display the Path Directory to check OSI Path names.OFIS Mail, OSI Message Handling System, OFIS Access-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-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.OFIS Mail: Path already exists.OFIS Mail: Invalid X.400 user specification.OFIS Mail: Invalid alias. The user referenced by the alias is no longer in the mail system.OFIS Mail: No recipients for this destination.OFIS Mail: Invalid name in organization distribution list.OFIS Mail, CT-Mail: Stack is full. You cannot save any more memos. Mail 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.OFIS Mail, CT-Mail: Disconnect received. 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 internal error 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 internal error 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 internal error indicates a problem with the software you are using.OFIS Mail, CT-Mail: Sequence out of order. Expecting a different record number. This internal error indicates a problem with the software you are using.OFIS Mail, CT-Mail: Not connected yet. An operation that requires a connection to another Mail Center was attempted before the connection was made. This internal error indicates a problem with the software you are using.OFIS Mail, CT-Mail: Wrong record length. The record is longer than 512 characters. This internal error 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 internal error 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.OFIS Mail, CT-Mail: Not valid record type. Something other than one of the 12 record types was received. This internal error indicates a problem in the software you are using. OFIS Mail, CT-Mail: Not status record. Expecting an ACK or REJ record. This internal error indicates a problem in the software you are using. 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 retries. 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.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 cable is plugged into the modem and into the correct port of the workstationOFIS 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, for 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 supported 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 Unisys Customer Support Center.OFIS Mail, CT-Mail: Error in read status from Modem. Bad status from modem. This internal error indicates a problem with the software you are using.OFIS Mail, CT-Mail: Bad modem command. An illegal modem command was given. This internal error indicates a problem with the software you are using.OFIS Mail, CT-Mail: Modem STXV. This internal error indicates a problem with the software you are using. Contact the Unisys Customer Support Center.OFIS Mail, CT-Mail: Modem STXQ. This internal error indicates a problem with the software you are using. Contact the Unisys Customer Support Center.OFIS Mail, CT-Mail: Modem STXX. This internal error indicates a problem with the software you are using. Contact the Unisys Customer Support Center.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 center. 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.OFIS Mail, CT-Mail: Command does not exist. An invalid command string was specified. This internal error indicates a problem with the software you are using. OFIS Mail, CT-Mail: Wrong header string. An invalid header string was specified. This internal error indicates a problem with the software you are using. OFIS Mail, CT-Mail: Quote missing. A quote is missing. This internal error indicates 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 internal error indicates 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 internal error indicates a problem with the software you are using. OFIS Mail, CT-Mail: Bad number format. An incorrect number was specified. This internal error indicates a problem with the software you are using. OFIS Mail, CT-Mail: Bad error code. The abort command was expected. This internal error indicates 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 found. A modem name was not found.OFIS Mail, CT-Mail: File too big. The MailCenter.config file is too large. This internal error indicates a problem with the software you are using.OFIS Mail, CT-Mail: Delimiter missing. The colon character is missing. This internal error indicates a problem C with the software you are using.OFIS Mail, CT-Mail: Missing entry. The entry is missing. This internal error indicates a problem with the software you are using.OFIS Mail, CT-Mail: Duplicate entry. The entry is a duplicate. This internal error indicates a problem with the software you are using.OFIS Mail, CT-Mail: Cnfg type out of range. The specified configuration does not exist. This internal error 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 internal error indicates a problem with the software you are using.OFIS Mail, CT-Mail: Dir type out of range. Specified type does not exist. This internal error indicates a problem with the software you are using.OFIS Mail, CT-Mail: File type out of range. Specified type does not exist. This internal error indicates a problem with the software you are using.OFIS Mail, CT-Mail: Folder type out of range. Specified type does not exist. This internal error indicates a problem with the software you are using.OFIS Mail, CT-Mail: User type out of range. Specified type does not exist. This internal error indicates a problem with the software you are using.OFIS Mail, CT-Mail, B-NET, BNet II, CT-Net: Invalid line handle. The line handle is not associated with any open modem line. This is an internal error. OFIS Access-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-X.400, B-NET, BNet II, CT-Net, CT-Mail: Only [COMM] and [Phone] line types are valid for current version of Modem Server. This is an internal error. Bad pointer in wait. OFIS Mail: The pointer to the request is zero. OFIS Access-X.400, B-NET, BNet II, CT-Net, CT-Mail: This is an internal error. Consult technical support personnel.OFIS Mail, CT-Mail, B-NET, BNet II, CT-Net: Channel is in use. The channel is already configured for use by the modem server.OFIS Mail, CT-Mail, B-NET, BNet II, CT-Net: ID string is too long. The ID string for the AcceptModemCall request is only one character. OFIS Access-X.400: Internal error. OFIS Mail, CT-Mail, B-NET, BNet II, CT-Net: ID string is in use. The ID string specified in the AcceptModemCall request is used by another process. OFIS Access-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 - X.400, B-NET, BNet II: Internal error. Consult technical support personnel.OFIS Mail, CT-Mail, B-NET, BNet II, CT-Net: Exceeds two Read requests. Only two ReadModemBytes requests can be outstanding at one time. OFIS Access-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 - X.400, B-NET, BNet II: Internal error. Consult technical support personnel.OFIS Mail, CT-Mail, CT-Net: Modem Server Fatal error. Modem Server abnormal termination. This internal error indicates a problem with the software you are using. Call technical support personnel. OFIS Access-X.400, B-NET, BNet II: Internal error. Consult technical support personnel.OFIS Mail, CT-Mail, B-NET, BNet II, CT-Net: No more line handles. Only four line handles can be associated with a single channel.OFIS Mail, CT-Mail, B-NET, BNet II, 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, B-NET, BNet II, CT-Net: The channel is busy. Some other process is using the channel currently.OFIS Mail, CT-Mail, B-NET, BNet II, CT-Net: Exceeds maximum channels. The modem server can handle up to six channels.OFIS Mail, CT-Mail, B-NET, BNet II, CT-Net: Channel is not configured. Contact the Unisys Customer Support Center.OFIS Mail, CT-Mail, B-NET, BNet II, 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, B-NET, BNet II, 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, B-NET, BNet II, CT-Net: Request still outstanding. The call is trying to perform CloseModemLine when a read or write request is still outstanding.OFIS Mail, CT-Mail, B-NET, BNet II, CT-Net: One open line allowed. For a direct connect line, only one process can open the line.OFIS Mail, B-NET: 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 uncommented before installing the Modem Server. Uncommented means that the semicolons have been removed from the beginning of the lines.OFIS Mail, CT-Mail, B-NET, BNet II, 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-X.400, B-NET, BNet II: Internal error.Carrier lost. OFIS Mail: The modem line carrier/receive line signal 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-X.400, B-NET, BNet II, 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, B-NET, CT-Net: The name specified in Open Modem Line is in use already. BNet II, OFIS Access-X.400: Name in use. The name specified in Open Modem Line is already in use. Either your program is already installed or another program has a duplicate name.CT-Mail: Modem name missing.CT-Mail: Line specification missing.CT-Mail: Baud rate missing.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, B-NET, CT-Net: Cannot swap Modem Server. You cannot swap the Modem Server.OFIS Mail, CT-Mail, B-NET, 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 internal error 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 password 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. CT-Mail: String from EasyLink host not found. Internal error. This status code indicates an error with the software you are using. Consult 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.CT-Mail: Too many addresses. A maximum of 32 addresses can be entered for computer letter services.CT-Mail: Your TWX ID is not valid. Verify the ID with the EasyLink Network Service.CT-Mail: 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.OFIS Mail, CT-Mail: Bad keyboard message. There is an unknown message at the keyboard exchange.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 formatting 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 arD e 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 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 ID.OFIS 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 set 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 range.CT-Mail: Attempted command not yet implemented. Internal error. CT-Mail: Bad message file.CT-Mail: Stack overflow. OFIS Mail: Alternate Access denied due to incorrect password.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 problem 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 node 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.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: Invalid Selection. See the help screen or the BTOS FSAFinesse 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 available. 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. See the help screen or the BTOS FSAFinesse Installation Utilities Operations Guide for the valid selections to enter.Multibus Adapter: No board exists in designated Multibus Adapter board slot. Message 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 Date.Multibus 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-F or a-fMultibus Adapter: Attempt to set interrupt handler for Multibus Adapter board. FSA Finesse: Record modified.Multibus Adapter: Attempt to reset interrupt handler that was set by another user. FSA Finesse: Error (nnnnn). See the 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 See the relevant part of this status codes documentation for a description 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 record.FSA Finesse: Record added.FSA Finesse: Record deleted.FSA Finesse: Record does NOT exist. Reenter a valid record key.FSA Finesse: Record already exists.FSA Finesse: File is full. No more records can be added to the file until you delete an existing record.FSA Finesse: SETTLE File does NOT exist. Press GO to create the File.FSA Finesse: Upper Limit must NOT be less than the Lower Limit.FSA 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.FSA Finesse: Error (nnnnn) , Press CANCEL to Continue, Error for Teller (nnn). Reorganization is aborted. See 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 Continue.FSA Finesse: Error Writing the EJ Detail File, Press CANCEL to Continue. Back up all EJ and Tank files and remove them from the hard disk.FSA Finesse: Invalid Entry. See the help screen for valid entries.FSA Finesse: EJ Index File Reorganization ABORTED for that Teller, Press CANCEL to Continue. File reorganization for that teller has been aborted.FSA Finesse: Error OPENing the Market Research File, Press CANCEL to Continue.FSA Finesse: Error Reading the Market Research Record, Press CANCEL to Continue.FSA Finesse: Error modifying the Market Research Record, Press CANCEL to Continue.FSA Finesse: Error FINDING KEY in the Market Research File, Press CANCEL to Continue.FSA Finesse: Error OPENing the Sales Activity File, Press CANCEL to Continue.FSA Finesse: Error deleting Sales Activity Record, Press CANCEL to Continue.FSA Finesse: Error FINDING KEY in the Sales Activity File, Press CANCEL to Continue.FSA Finesse: Reorganizing the Electronic Journal files.FSA Finesse: Reorganizing the Customer Service Files.FSA Finesse: Files' Reorganization is complete.FSA Finesse: Current entries will be cleared. Press GO to confirm, CANCEL to cancel.FSA Finesse: Current changes will be lost. Press GO to confirm, CANCEL to cancel.FSA Finesse: Record will be written to disk. Press GO to confirm, CANCEL to cancel.FSA Finesse: Entry must be numeric.FSA Finesse: Value is out of range.FSA Finesse: Field must not be blank. Enter valid value in the field.FSA Finesse: Record written.FSA 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 recordFSA Finesse: Return to previous menu, no update. Press GO to confirm, CANCEL to cancel.FSA Finesse: Record deleted.Multibus 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 cancel.FSA Finesse: Record does not exist.FSA Finesse: Entry must be 0 or 1.FSA Finesse: Value is previously defined. Enter unique values in the field.FSA Finesse: Record retrieved.FSA 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. See the help screen or the BTOS FSAFinesse Installation Utilities Operations Guide for values to enter.FSA Finesse: Entry must be a valid hexadecimal code.FSA Finesse: Insertion is not possible. No slot is available to insert a new field. Delete an allowed, existing field.FSA Finesse: (This message consists of 80 spaces.)FSA Finesse: Cannot delete/insert on an empty field.FSA Finesse: Sum of all maximum lengths is out of range. Enter a sum that does not exceed the allowed limit.FSA Finesse: At least one maximum length field is required. Enter data in a maximum length field. See the help screen or the BTOS FSAFinesse Installation Utilities Operations Guide for values to enter.FSA Finesse: Entry must be alphanumeric. Enter an alphanumeric charD acter.FSA Finesse: Invalid entry.FSA 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 zero.FSA Finesse: (This message consists of 80 spaces.)FSA Finesse: Go to next section, no update. Press GO to confirm, CANCEL to cancel.FSA Finesse: Entry must be 1.FSA Finesse: (This message consists of 80 spaces.)FSA Finesse: Value is out of range.FSA Finesse: Return to DEV PARAM menu, no update. Press GO to confirm, CANCEL to cancel.FSA 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 recreate 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 Parameters 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 recreate 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 Table Element/Type/ID is required.FSA Finesse: Record does not exist. Press CANCEL to continue.FSA Finesse: Next Posting Date must be greater than the current Posting Date.FSA Finesse: CRT address cannot be the same as machine address.FSA Finesse: Duplicate Password in Teller File : Error (20310).FSA Finesse: Leading and embedded blanks not allowed.FSA Finesse: File has been rebuilt.File is not rebuilt.FSA Finesse: Error (nnnnn) See the Status Codes Manual; Press any key to terminate.FSA Finesse: Unable to Encode / Decode. Call your Unisys representative.FSA Finesse: FILE IN USE.FSA 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.FSA Finesse: (This message consists of 80 spaces.)FSA Finesse: Invalid Entry. Enter the time in HHMM format.FSA Finesse: Press GO to Continue.FSA Finesse: Press CANCEL to Continue.FSA Finesse: Press NEXT PAGE for more totals.FSA Finesse: Press PREV PAGE for previous totals.FSA Finesse: Invalid Date.FSA Finesse: Invalid Time.FSA Finesse: Invalid Application Type. Enter a valid application type. The application type refers to the type of account, such as demand deposit or installment loan. The value is the first character of the transaction ID.FSA Finesse: Invalid Teller Number. Enter a valid teller number.FSA Finesse: Invalid Operator Name. Enter a valid operator name.FSA Finesse: Invalid Window Number. Enter a valid window number. The station ID must be defined in the Local Station Parameters.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 system cannot read the drawer file. Press the CANCEL key. See 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. The Teller number must be defined in the Teller Records. See the BTOS FSAFinesse Installation Utilities Operations Guide for instructions on modifying the Teller Records.FSA Finesse: Processing ...FSA Finesse: No TANKed Transactions Present at this Time.FSA Finesse: Press NEXT PAGE for more records.FSA Finesse: Press PREV PAGE for previous records.FSA Finesse: Report Request Completed.FSA Finesse: Report Request NOT Processed: Error (nnnnn) on ACTIVITY File. See 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 File. See 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. See 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 SystParam File. See 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. See 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 TELLER File. See 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. See 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. See 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 Market Research File. See 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. See 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 CANCEL.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. An error has occures on one of the following:  Branch Control Module  Administrative Program  Message Control System (MCS) Execute the Partition Status command from the Executive command line at the branch processor to make sure that the Branch Control Module and Message Control System are running. If the Branch Control Module is down, contact your system administrator. See the appropriate documentation for instructions to execute the Partition Status command.FSA Finesse: Cannot send message to CONTROL. An attempt was made to terminate processing from the administrative workstation, but the branch processor went down. Contact your supervisor.FSA Finesse: Report Request NOT Processed: Error (nnnnn) on Sorted ACTIVITY File. See the relevant part of this status codes documentation for a description of the status code displayed in parentheses.FSA Finesse: Press any key to complete the present transaction.FSA Finesse: Request for Supervisor Override NOT Pending.FSA Finesse: Password level too LOW. The operator's password level does not allow access to this function or transaction.FSA Finesse: Password NOT valid. Enter a password defined in the Teller Records.FSA Finesse: Text Message MUST be entered. This field requires data entry. Enter the text message.FSA Finesse: Terminate all Branch Processing.FSA Finesse: Press NEXT PAGE for more totals or PREV PAGE for previous totals.FSA Finesse: **Posting Date has changed on the Branch Processor.** Press GO to continue.FSA Finesse: Press GO to Confirm, CANCEL to Deny.FSA Finesse: Terminate Administrative Application.FSA Finesse: Time Interval Too Large.FSA Finesse: Exiting to Customer Service/Teller.FSA Finesse: Exiting to Finesse Executive.FSA Finesse: Invalid currency code for editing.FSA Finesse: Currency type already exists.FSA Finesse: Unable to open Teller File. Try operation again. If failure continues, data in teller file may be corrupt. Contact your supervisor or Unisys representative.FSA Finesse: SYLK File Request Not Processed: Error (nnnnn) on Syst Param File. See 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. See 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 MktResearch File. See 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 SYLK File. See the relevant part of this status codes documentation for a description of the status code displayed.FSA Finesse: SYLK File Request Completed.FSA Finesse: SYLK Program Failed. The data being used by the SYLK file program is bad orE  the SLYK file program is bad. Contact your supervisor or Unisys representative. 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. Contact your system administrator. The system returns to the last menu displayed after this message is encountered.FSA Finesse: Percent Delimiter Not Entered Error. Reenter rate field using a percent delimiter. The percent delimiter separates the decimal portion of a rate from the whole portion.FSA Finesse: Invalid Total Set : First Free Set = (nn), Highest Allocated Set = (nn).FSA Finesse: Invalid Percent Delimiter.FSA Finesse: Invalid Decimal Delimiter.FSA Finesse: Invalid Whole Delimiter.FSA 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 the System Parameters File, Branch Parameters section, to "LPT," and ensure that a printer is connected to the workstation.FSA Finesse: Invalid Selection.FSA Finesse: Invalid Exit Key.FSA Finesse: Entry must be numeric.FSA Finesse: Not an Administrator.FSA Finesse: Invalid Administrator Number.FSA Finesse: Invalid Password.FSA Finesse: Processing ...FSA Finesse: TellNo.Dat file not found. Press FINISH to return to the Executive.FSA Finesse: Teller.Dat file not found. Press FINISH to return to the Executive.FSA Finesse: Please terminate process before executing Install Utilities.FSA Finesse: Cannot execute Utilities on two workstations simultaneously.FSA Finesse: Service Not Available.FSA Finesse: Waiting for MCR; Press CANCEL.FSA Finesse: Pass Card Through MCR.FSA Finesse: MCR Read Error; Press CANCEL or NEXT.FSA Finesse: MCR Open Error.FSA Finesse: MCR Device Error.FSA Finesse: This is an MCR Error. See the Device Service Manual.FSA Finesse: Reenter New Password.FSA Finesse: No Currencies to Print, Press CANCEL to continue.FSA Finesse: Customer Service not available for this workstation.FSA Finesse: Report Request Parameters must be in Operator Name Order.FSA Finesse: Next Posting Date can not be before Current Posting Date.Voice/Data 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/Data Services: Too many connections. The connection resulting from the specified operation cannot be completed because there is no available discrete path through the crosspoint switch.Voice/Data Services: Invalid connection. The connection resulting from the specified operation is not allowed.Voice/Data Services: Invalid parameters. The parameters to the specified operation are not valid.Voice/Data Services: Not off hook. The voice unit or telephone line must be offhook for the specified operation.Voice/Data Services: Bad handle. The handle you specified was invalid.Voice/Data Services: Timeout. The operation was terminated because a specified time limit for completion expired.Voice/Data Services: Invalid module. The module specified is invalid.Voice/Data Services: Not on hook. The line must be onhook for the operation specified.Voice/Data Services: Voice unit on hook. The voice unit must be offhook for the operation specified.Voice/Data Services: Invalid function. The function specified to the TsDoFunction operation is illegal.Voice/Data Services: On hold. The operation was terminated due to the line being placed on hold as the result of command being issued.Voice/Data Services: On hook. The operation was terminated due to the phone or line being placed onhook or to a TsOnHook or TsDoFunction (hang up) command being issued.Voice/Data Services: Service reset. The service was reset with the TsDoFunction service.Voice/Data Services: Voice work area too small. The work area must be at least 13312 bytes and word aligned.Voice/Data Services: Voice in use. The voice hardware is either in use or has been locked with TsDoFunction.Voice/Data Services: Voice sample not found. The specified starting sample could not be found.Voice/Data 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/Data Services: Voice data lost (CPU). The voice operation was terminated because the Telephone Service process could not keep up with the voice data rate.Voice/Data Services: Bad voice parameters. One or more field in the voice control structure are invalid.Voice/Data Services: Invalid voice data file. The signature byte is invalid in a record of the file specified.Voice/Data 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/Data Services: No request file. The Operating System did not load the Telephone Service request file during system initialization (boot).Voice/Data Services: Bad request file. The Telephone Service request file and the Telephone Service are not of the same revision level.Voice/Data Services: Telephone Service already installed.Voice/Data 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/Data Services: Bad request. A request not recognized by the Voice/Data Service was received at the Voice/Data Service's service exchange.Voice/Data 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/Data Services: User swapped. The operation was terminated due to the swapping to disk of the program using the service.Voice/Data Services: Invalid configuration file. The signature word in the configuration files specified is invalid.Voice/Data Services: Duplicate request. The request is a duplicate of one currently being processed and is not allowed.Voice/Data Services: Firmware invalid. The Voice Processor module firmware is invalid.Voice/Data Services: Bad deinstallation order. Multiple invocations of the Telephone Service must be deinstalled in the reverse order in which they were installed.Voice/Data Services: Bad dial character. A character specified in the dial string is not valid.Voice/Data Services: Dialing in progress. A TsDial service is in progress using the dialing hardware.Voice/Data Services: No dial tone: Busy. A busy signal was detected instead of dial tone when a wait for dial tone command (=) was processed.Voice/Data 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/Data Services: No dial tone. No dial tone was detected when a wait for dial tone command (= or !=) was processed. Voice/Data Services: Bad dial pulse character. A character that can not be dialed (such as # or *) was processed with pulse dialing.Voice/Data Services: Too many characters to dial. No more than 64 characters can be processed at a time.Voice/Data Services: Detector in use. The hardware required for detecting Dual Tone Multifrequency (DTMF) or a dial tone is in use by another operation.Voice/Data Services: No answer. The party being called did not answer.Voice/Data Services: Line in use. The line specified in a TsDataOpenLine operation is in use.Voice/Data Services: Invalid line specification. The line specified in a TsDataOpenLine or TsDataUnAcceptCall operation is in use.Voice/Data Services: Invalid line parameters. The line control structure has invalid parameters or an invalid size.Voice/Data Services: Unaccepted issued. The TsDataOpenLine operation is being terminated due to a TsDataUnAcceptCall being issued.Voice/Data Services: No accept call issued. The TsDataUnAcceptCall failed because no TsDataOpenLine operation for the line was waiting to accept the call.Voice/Data Services: Modem driver not installed. The Telephone Service was installed without the modem drivers.Voice/Data Services: Lost carrier. The modem lost the carrier signal.Voice/Data 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/Data Services: Bad parity. The TsDataRead operation was returned due to bad parity being detected.Voice/Data Services: TsDataRead or TsDataWrite timeout. The TsDataRE ead or TsDataWrite operation was returned due to the time limit specified in the operation expiring.Voice/Data Services: End-of-Block character received. The TsDataRead operation was returned due to the specified end of block character being received.Voice/Data 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 by 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/Data Services: Line in use: accept call issued. A TsDataOpenLine to accept a call has already been issued for the specified line.Voice/Data Services: Line in use: modem active. An open modem session is already in progress on the specified line.Voice/Data Services: Line in use: modem error. 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/Data Services: Line in use: voice. An open voice or modem session is already in progress on the specified line.Voice/Data Services: DSP Software Failure. There has been a DSP code failure. Deinstall and reinstall the Voice/Date Service.Voice/Data Services: TsVoice Disk Underrun. The voice operation was terminated due to the disk and/or cluster not being able to keep up with the voice data rate.Voice/Data Services: Voice file not supported. Voice/Data Services running on SG5000 does not support files recorded on an NGen Voice Processor module (B25-TEL). The hardware recording techniques are incompatible.Voice/Data Services: Record/Playback option not supported. A SuperGen Series 5000 workstation cannot record files using the Save Disk Space option, which specifies record/playback at the rate of 6KHz. Record with the High Voice Quality option, which specifies the 8KHz sampling rate supported on the SuperGen Series 5000.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 does 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 requests. See the System Administration Guide.System Requests: Illegal parity option. A mark or space parity was 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. See the System Administration Guide.System Requests: The board type is inconsistent with the amount of memory. (Shared Resource Processor only)AdminAgent: The default path supplied to mfAdminAgent.run from WsAdminAgent.run is not a valid 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 has an improper format. This error can occur if the WsAdminAgent and MfAdminAgent run files are not at the same version level. This status code applies to releases prior to CTOS/XE 3.0.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 Access Error to Invalid LFA. Contact your system administrator.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). See 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. The disk is nearly full. Discontinue processing and make more disk space available. Back up all of your files and use the Reorganize Files Utility.Context Manager: Information block 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). See the relevant part of this status codes documentation for a description of the status code displayed in parentheses. Context Manager: A context cannot call CMTerminateContext to terminate itself. FSA Finesse: BTOS Error (nnnnn), TOTALs Error, CONTACT YOUR SUPERVISOR. See the relevant part of this status codes documentation 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 name too long. FSA Finesse: Teller Already Signed On. Proceed with processing. Context Manager: 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). See the relevant part of this status codes documentation for a description of the status code displayed in parentheses. Context Manager: Cannot change parent to self. FSA Finesse: BTOS Error (nnnnn), CANNOT Read Totals, CONTACT YOUR SUPERVISOR. See the relevant part of this status codes documentation for a description of the status code displayed in parentheses. Context Manager: Cannot switch to locked context. FSA Finesse: Cash Drawer has EXCEEDED the Upper Limit By: (nnnnn)Context Manager: Cannot adopt parent or grandparent context. FSA Finesse: Cash Drawer has Fallen Below the Lower Limit By: (nnnnn)FSA Finesse: Totals Processed and CLEARED.FSA Finesse: Totals Processed.FSA Finesse: Branch Totals Processed.FSA Finesse: Branch Totals Partially Processed.Context Manager: This application is not reading the keyboard. This status code indicates that the application selected to receive the pasted data has been suspended or halted. Applications in this state cannot read the keyboard, and therefore cannot receive pasted data. FSA Finesse: Batch Totals Processed and CLEARED.Context Manager: Cannot paste to a submit program. FSA Finesse: Balance Complete.Context Manager: Paste already in progress. FSA Finesse: Electronic Journal, TANK, and Teller Totals Updated.Context Manager: Invalid data transfer parameters. An error occurred during data transfer, eitherbecause you did not select any data to be transferred, or because you specified an invalid default data transfer mode in your CM config file. FSA Finesse: Cash Drawer OVER.Context Manager: The context cannot terminate the child context. FSA Finesse: Cash Drawer SHORT.Context Manager: No function key for this context. FSA Finesse: Cannot Establish Communication with the Host: Error (nnnnn). See the relevant part of this status codes documentation for a description of the status code displayed in parentheses. Context Manager: No function key for this context.Context Manager: This status code indicates one of the following:  Protected Mode: A user interface for CM has already been registered.  Real Mode: Real Mode Context Manager does not support separate user interfaces. FSA Finesse: Reentry Begun for Teller; Press FINISH to Interrupt. Context Manager: Protected Mode: A user interface for CM has already been registered. Context Manager: Real Mode: Real mode Context Manager does not support separate user interfaces.Context Manager: Not a registered CM user interface. FSA Finesse: Reentry SUSPENDED.FSA Finesse: Reentry COMPLETE.Context Manager: Cannot start shared video child context. FSA Finesse: Reentry CANCELLED: Error (nnnnn) on the EJ Index File. A BTOS error occurred while accessing the EJ Index file (EJ..Dat). See the relevant part of tF his status codes manual for a description of the status code displayed in parentheses. Context Manager: Cannot supend or resume child. FSA Finesse: Reentry CANCELLED: Error (nnnnn) on TANK File. A BTOS error occurred while accessing the EJ Detail/Tank File. See the relevant part of this status codes documentation for a description of the status code displayed in parentheses. Context Manager: Missed event. The caller has missed an event it should have received from CMReadContextEvent. To correct this, the caller should issue a call to CMQueryOtherContexts. 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: Supervisor NOT available. Specify another destination for override request. FSA Finesse: Request for authorization is NOT pending.Context Manager: Data transfer is not supported from this application. The user attempted to use the Data Transfer feature from an application which does not have the necessary keyboard tables to support Data Transfer. FSA Finesse: Detail/Tank Access Error to Invalid Next LFA. Contact your system administrator.FSA Finesse: Detail/Tank Access Error to Invalid maximum record length. Contact your system administrator.FSA Finesse: Detail/Tank Access Error to Table full. Contact your system administrator.FSA Finesse: Cash Drawer in BALANCE.FSA Finesse: Reentry CANCELLED: Host wait time elapsed. Check the host line. If the problem continues, contact your system administrator.FSA Finesse: Detail/Tank Access Error to Invalid Index. Contact your system administrator.FSA Finesse: Supervisor has ignored Override Request.FSA Finesse: Vault Cash Error, Vault is not signed on.FSA 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. No tanked transactions exist for that date. Enter another date.FSA Finesse: No more Tellers available for Auto-Reentry. Please try again later.FSA Finesse: Status Request Processed.FSA Finesse: Tellers Still Signed On.FSA Finesse: Message Sent to Destination(s).FSA Finesse: Teller NOT Available. An 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 system administrator.FSA Finesse: Error writing the New Account Record. 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 system administrator.Context Manager: The swap file is full -- cannot swap any more contexts. 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. Only a predefined number of tellers can access a certain number of days at one time. Try again later.FSA Finesse: BCM error. Invalid index for drawer access. Contact your system administrator.FSA Finesse: BACKUP DISK APPROACHING 100% USED. Disk is becoming full. Back up all of your files and use the Reorganize Files Utility. Discontinue processing and make more disk space available. If this message recurs, contact your system administrator.FSA Finesse: Error Sending Messages to BACKUP. BCM discontinues sending messages to the Backup workstation. If this message recurs, contact your system administrator.FSA Finesse: BACKUP ERROR (nnnnn). See the BTOS FSAFinesse Installation Guide.FSA Finesse: Date only valid for Branch Totals.FSA Finesse: Supervisor transaction limit exceeded.FSA Finesse: Tlr already signed on at Station (nnn). Signon aborted.Context Manager: The run file needed for this application does not exist.Context Manager: You cannot start any more contexts; maximum is 20.Context Manager: There is no context to return to.Context Manager: The swap file is full -- cannot swap any more contexts. Page Service: Swap file full. A page cannot be swapped out because the swap file is full. The page fault handler encounters this error when it tries to find a replacement page. The process that faulted is aborted.Context Manager: The run file is too large to run in any partition.Context Manager: You cannot logout; there are contexts which must be finished.Context Manager: Warning: There are unfinished contexts. Press GO to logout or CANCEL to deny.Context Manager: This context cannot be finished from the Context Manager.Context Manager: The file specified as your swap file does not exist.Context Manager: You can run only one graphics application at a time.Context Manager: Cannot start an additional video-controlling application.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 enough room in the swap file to swap the highlighted context.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 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.Database: Invalid database handle. FSA Finesse: FILE ERROR to (nnnnn).Database: Invalid Query identifier. FSA Finesse: Invalid Date Format.FSA Finesse: Invalid System Date or Current Posting Date.Database: Invalid Relation identifier. FSA Finesse: Invalid Input Parameter.Database: No more free handles. The memory allocated for handles has been exhausted. Database: The specified operation is not implemented for CT-DBMS databases. Database: The specified operation is not implemented for personal databases. Database: An error occurred while the data dictionary was being initialized. Database: An error occurred while part of the data dictionary was being discarded. Database: There is no such database in the dictionary.Database: There is no such relation in the dictionary.Database: There is no such attribute in the dictionary.Database: There are no more relations in the dictionary. Database: There are no more attributes in the dictionary.Database: There are no more databases in the dictionary. Database: An error occurred while the data dictionary was being read. Database: The specified database is not open. Multiplan: The specified PDB relation is not open.Database: A name cannot be returned because the supplied buffer is too small.Database: The specified data type is not currently supported.Database: The user does not have read privileges for the specified object.Database: The user does not have modify privileges for the specified object.Database: The user does not have delete privileges for the specified object.Database: The user does not have store privileges for the specified object.Database: An error occurred in accessing the physical view.Database: An error occurred in accessing the physical index.Database: An error occurred in accessing the physical scan.Database: The physical view is too complex.Database: The physical index is too complex.Database: The symbol table is full.Database: An error occurred during initialization.Database: There is not enough memory to initialize. Database: Initialization must occur before this operation.Database: There is no symbol table.Database: The pointer for initializing the work area points to nonaddressable memory.Database, Multiplan: An error occurred during initialization.Database: The memory area for the Virtual Memory heap is not large enough. Currently, the Virtual Memory heap requires at least 10240 bytes of memory.Database, Multiplan: Cannot open the specified database. An error occurred while the specified database was being opened. A second status code may appear, giving the reason for the failure.Database: The maximum number of databases is already open.Database: The maximum number of personal databases is already open.Database: The mode specified for opening the database is invalid.Database: The specified database is already open.Database, Multiplan: Cannot create the specified database. An error occurred while the specified database was being created. A second status code may appear, giving the reason for the failure.Database: The specF ified database kind is invalid.Database: An error occurred while the specified relation was being created.Database: The specified relation already exists. Database, Multiplan: Cannot add field. The specified field or attribute cannot be added. A second status code may appear, giving the reason for the failure.Database, 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.Database: The Attribute Descriptor Block is invalid.Database: An error occurred during acceptance of the specified query. Database: The specified query is not active.Database: The specified query is already active.Database: An error occurred while the specified query was being started.Database: An error occurred while the specified query was being started.Database: The specified relation cannot be modified because an active query exists for it.Database: An error occurred while the specified view was being opened.Database: The mode specified for this view is invalid.Database, 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.Database: The query contains an illegal or unknown attribute name.Database: The query contains an attribute name that is too long.Database: The query contains a constant value that is too long.Database: The query contains too many selection criteria.Database: The query contains an illegal selection criteria.Database: The query results with no data being returned.Database: The query can return data only for named attributes.Database: The query contains too many attribute names.Database: The query requests a data record that is too large.Database: The query structure is invalid.Database: Illegal data types are being compared.Database: The field value being compared is illegal. Database: An error occurred during execution of the specified query.Database: The memory area specified by the user to contain the data record is not long enough.Database: There are no more records to be returned for the query. Database: An error occurred while the specified query was being set up for execution.Database: The specified tuple identifier is illegal or unknown.Database: 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.Database: The "null allowed" status for this attribute cannot be changed.Database, Multiplan: Illegal type conversion. You tried to change an alpha field into a numeric, or vice versa.Database: The size of the specified type cannot be changed. Database: The Attribute Descriptor Block is the wrong size.Database: The mode specified for the query is invalid.Database: The specified record is locked by another user.Database: The specified value duplicates a value in another record, and this field does not allow duplicates.Database: A null value may not be put into a field that does not allow nulls.Database: The user must store values into all fields in the relation that require non-null values.Database: The specified database already exists.Database: The database has too may attribute names, or the size of the data record is too large.Database: The specified attribute name is too long.Database: A number (not a string) was expected to be converted. This internal error indicates a problem in the software you are using. Database, Multiplan: Number is too small to be converted. This internal error indicates a problem in the software you are using. Database: Illegal data type for conversion. This internal error indicates a problem in the software you are using. Database: A string (not a number) was expected to be converted. This internal error indicates a problem in the software you are using. Database: An internal inconsistency was detected during conversion. This internal error indicates a problem in the software you are using. Database: Premature end of the compiled query. This internal error indicates a problem in the software you are using. Database: Illegal kind of field in the compiled query. This internal error indicates a problem in the software you are using. Database: Illegal kind of node in the compiled query. This internal error indicates a problem in the software you are using. Database: The specified view is already executable. This internal error indicates a problem in the software you are using. Database: The specified view is not executable. This internal error indicates a problem in the software you are using. Database: Illegal kind of structure. This internal error indicates a problem in the software you are using. Database: No space available to allocate structure. This internal error indicates a problem in the software you are using. Database: Attempt to de-allocate a nonexistent structure. This internal error indicates a problem in the software you are using. Database: No such attribute exists in the specified index. This internal error indicates a problem in the software you are using. Database: No such nodes exists in the dictionary. This internal error indicates a problem in the software you are using. Database: The dictionary is malformed.Database: Attempted to open a database when it is already open.Database: The dictionary does not exist.Database: Illegal dictionary level. This internal error indicates a problem in the software you are using. Database: No such index exists. This internal error indicates a problem in the software you are using. Database: There are no more indices. This internal error indicates a problem in the software you are using. Database: Illegal access type. This internal error indicates a problem in the software you are using. Database: The physical view cannot be freed because it is not open. This internal error indicates a problem in the software you are using. Database: Illegal physical view identifier. This internal error indicates a problem in the software you are using. Database: The physical index cannot be freed because it is not open. This internal error indicates a problem in the software you are using. Database: Illegal physical index identifier. This internal error indicates a problem in the software you are using. Database: The symbol table is corrupt. This internal error indicates a problem in the software you are using. Database: Illegal symbol identifier. This internal error indicates a problem in the software you are using. Database: The specified symbol does not exist. This internal error indicates a problem in the software you are using. Database: The specified object could not be mapped to a symbol. This internal error indicates a problem in the software you are using. Database: The specified symbol does not denote a valid symbol identifier. This internal error indicates a problem in the software you are using. Database: The return buffer for the symbol is too small. This internal error indicates a problem in the software you are using. Database: Attempt to de-allocate the handle of a nonexistent structure. This internal error indicates a problem in the software you are using. Database: Illegal kind of handle. This internal error indicates a problem in the software you are using. Database: The memory area specified for the record is too small.Database: The record identifier specifies a nonexistent or deleted record.Database: There are no more records in the scan range.Database: The scan ended with an illegal record identifier.Database: The specified field name already exists. Database: There are no more attributes to query. Database: The field name to be deleted was not found.Database: The field type and length are inconsistent.Database: The field name is too long.Database: The buffer specified for the relation query is too small.Database: Not enough space was given for the work space area.Database: Illegal relative attribute number.Database: Illegal match kind.Database: The attribute value to scan for is more than 64 bytes long.Database: Expected attribute not found.Database: The attribute is longer than specified in the FieldIOSpec.Database: The name was truncated to fit into the user buffer.Database: The specified field is not variable length; the length may be reset.Database: The database may not be written to in read-only mode.Database, 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.Database: Too many field definitions.Database: Too many field names.Database: Too many heap blocks accessed. This internal error indicates a problem in the software you are using. Database: The specified block may not be freed, it is still in use. This internal error indicates a problem in the software you are using. Database: Illegal tag in heap (node is neither free nor in use). This internal error indicateG s a problem in the software you are using. Database: The specified block is not on the free list. This internal error indicates a problem in the software you are using. Database: The next block is not on the free list. This internal error indicates a problem in the software you are using. Database: The next block has an invalid link. This internal error indicates a problem in the software you are using. Database: Illegal tag in previous heap. This internal error indicates a problem in the software you are using. Database: Illegal tag in the next heap. This internal error indicates a problem in the software you are using. Database: Illegal heap signature. This internal error indicates a problem in the software you are using. Database: Too little space for heap initialization. This internal error indicates a problem in the software you are using. Database: All heap blocks are in use, nothing may be swapped. This internal error indicates a problem in the software you are using. Database: Illegal heap block identifier. This internal error indicates a problem in the software you are using. Database: The specified block is not accessed. This internal error indicates a problem in the software you are using. Database: Illegal heap block size. This internal error indicates a problem in the software you are using. Database: The heap is full. This internal error indicates a problem in the software you are using. 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 queues at once.SPA: File name record corruption detected by ReadRamFile.SPA: AllocHighMemory return value is out of range. 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 Name 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.SPA: Lost File Name record.SPA: File Name record corruption detected.SPA: File Name record pointer missing from rgoFnRecordLocal table.SPA: 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.SPA: 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.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:  Received 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 BNetII, 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 switched 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.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 internal error indicates an invalid state for disconnecting a session from the Net Agent. CT-Net: This internal error indicates an invalid state for disconnecting a session from the Net Agent. CT-Net: This internal error indicates an invalid state for disconnecting a session from the Net Agent. 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: HDLC 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, 9600,or 19200.B-NET, BNetII, CT-Net HDLC Media: Invalid modem type. An attempt has been made to configure the HDLC media as HDLCD, but the modem type specified is not R, 1200PA, 2400PA, (in BNetII ) Hnnnn (where nnnn is the baud rate supported by the Hayes-compatible modem) 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 service 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-NET, 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 mode received character. Internal error.B-NET, BNetII, CT-Net HDLC Media: Asynch mode received 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 requirements 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 connection, or currently being reset. This status code might also indicate that a leased line has been configured as a switched line.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 parameter other than i or e.CT-Net HDLC Media: Using a duplicate install number.BNetII: Excessive interrupts. The HDLC media service is receiving an excessive rate of interrupts on an RS-232-C line. This is causing it to fall behind in its processing and to eventually disable the line. There might be an unterminated cable, or some otherG  source of noise on the line.B-NET, BNetII, CT-Net HDLC Media: Received aborted frame. Internal error.B-NET, BNetII, CT-Net X.25 Media: Invalid number VCs. The X.25 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. BNetII: When loading the X.25 media service, an invalid size was entered for the [User Buffer Size] parameter.B-NET, BNetII, CT-Net X.25 Media: Total user buffer size too large. The X.25 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: Total X.25 buffer size too large. The X.25 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 X.25 media service is being installed, and the specified X.25 Buffer Size parameter is invalid. Valid values are 128, 256, 512, and 1024.B-NET, BNetII, CT-Net X.25 Media: Transmit data from Transport Service too large. Internal error.B-NET, BNetII, CT-Net X.25 Media: No VCBs available. An attempt is being made to establish an X.25 VC, but the X.25 media service cannot support any more SVCs. When installing X.25, 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 X.25 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 X.25 media 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 X.25 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 X.25 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 X.25 media service was installed, the Switched VC Call Type parameter 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. CT-Net: This error indicates a wrong state. Internal error.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. B-NET, BNetII: Internal error. CT-Net: Internal error. This 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. Check the X.25 configuration. Internal error.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 X.25 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 X.25 media service to indicate that a buffer is not available and that data may have been discarded. 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 the X.25 finds this has happened, it shuts down one SVC and routes all traffic over the other. It posts this status code to the log file to indicate 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.B-NET, BNetII, CT-Net Asynchronous Media: Invalid number of 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 invalid 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 Dial Connection timeout parameter.B-NET, BNetII, CT-Net HDLC Media: Invalid configuration file. Internal error.B-NET, BNetII, CT-Net: Internal error.BNet at remote site refused connection. The Net Server at the remote node may not be able to support any more connections. Try increasing the :Server Connections: parameter when installing the Net Agent/Server on the remote node.B-NET, BNet II, CT-Net: Internal error.B-NET, BNET II, CT-Net: Invalid destination node name. BP Transport does not recognize the node name passed.B-NET, BNET II, CT-Net: Internal error. Invalid handle.B-NET, BNET II, CT-Net: Internal error. Invalid handle.B-NET, BNET II, CT-Net: Timeout of acknowledgment. Acknowledgment not received from remote node within the configured time frame. If this happens very often, increase the :Time Out Value: parameter in the BP Transport configuration file.B-NET, BNET II, CT-Net: Unknown TSAP. The TSAP number is not defined in the BP Transport configuration file.B-NET, BNET II, CT-Net: TSAP in use. The TSAP number is already in use by another user.B-NET, BNET II, CT-Net: Insufficient memory. Not enough memory to allocate another TSAP. Increase the :Total Number of Transport Connections: parameter in the BP Transport configuration file and reinstall.B-NET, BNET II, CT-Net: Internal error.B-NET, BNET II, CT-Net: Internal error.B-NET, BNET II, CT-Net: Internal error. Operation attempted over BP Transport by user who is not currently attached to it.B-NET, BNET II, CT-Net: Connection terminated. A connection has been terminated due to excessive timeouts, lack of resources, or similar problem.B-NET, BNET II, CT-Net: Media not connected. Either the BP Link service is not installed or the connection to the media service closed to recover from an error condition.B-NET, BNET II, CT-Net: Invalid media definition. Internal error; Contact Technical Support.B-NET, BNET II, CT-Net: Media connection reset. The media connection has been reset to recover from error. This can be caused by heavy traffic in conjunction with a small packet size. Increase the :Packet size: parameter if this error occurs often. This error can occur if the media service is deinstalled.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 coH llisions 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.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-Net 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.SPA RamDisk.run: The RamDisk.run program failed to install. The reason that the installation failed appears on the screen.SPA RamDisk.run: An internal record that describes a cached file has been corrupted. The cache is 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 discovered an internal error. No recovery is possible.SPA RamDisk.run: The system detected an internal error. The RamDisk.run exchange has incorrectly received a request. No recovery is possible.SPA RamDisk.run: The system discovered an internal inconsistent state. The most likely cause 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.SPA Mover.run: Mover.run has failed to install. The reason for the failure appears on the screen.Image Designer, OFIS Imager: Bad data was sent to the scanner. Command error. The last command sent to the scanner was not recognized.Image Designer, OFIS Imager: 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 command 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.Image Designer, OFIS Imager: File is not an image (TIFF) file. The file does not follow the TIFF format.GPS Imaging: Invalid or unsupported formats encountered in TIFF raster image data. Image Designer, OFIS Imager: The file is not understood by Image Designer (OFIS Imager).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.Image Designer, OFIS Imager: Operation can't be done with this scanner. The scanner defined in the user file does not support this feature. 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. The user file does not list a scanner.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 file was given in the user file. Install the BLP Server to communicate with the operating system.GPS Imaging: Invalid or unsupported formats encountered in TIFF raster image 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 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.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.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 Final 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 change this option.NLS: No such Native Language Support (NLS) table signature.NLS: Bad Native Language Support (NLS) table signature.NLS: Not a message file. B-NET: No response from the remote node on link level echo function. NLS: Message not found. The application you were running did not find a specific message in the Msg.bin file for the application or could not find the Msg.bin file. 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 (see 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. B-NET: The LAN software has received an illegal request. B-NET: The remote node has aborted the connection. Change Message File: Invalid delimiter for message number: Create Message File returns this status code if an invalid delimiter (such as `0' through `9', `A' through `Z', or `a' through `z') is specified for a message contained in the ".mtext" file. The following is an invalid definition: :3: "No headpark performed." The valid definition would be: :3: "No headpark performed."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. B-NET: A duplicate request has been made to either open a connection, or to await a close on it. B-NET:  The remote node rejected a connection request, probably due to incompatible options. B-NET: The local node rejected a connection attempt due to incompatible options. B-NET: An illegal address was specified for a connection attempt or for a datagram. B-NET: An error occurred at the network layer. 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 LAN 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. B-NET: Agent no CDB available. The LAN software has exceeded an internal resource. Contact field support to have this resource expanded.B-NET: No remote response. The Net Server in the remote node does not respond, although the LAN software appears to be installed. The Net Server may not be installed, or there may be some other problem with the software runH ning 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. BNetII: No node name. No node name was entered when installing the Net Agent and Net Server.B-NET: LAN data 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 parameters.B-NET: Service 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 it may be too long or zero lengthened.) BNetII: Invalid node name. The node name entered when the Net Agent and Net Server were installed is invalid.B-NET, BNetII: Data segment too large. The parameters specified when installing the Net Agent or Net Server require more memory than can be utilized. Try reducing the number of input parameters.B-NET, BNetII: Too many file handles. When installing the Net Agent, the number of remote resources specified exceeded 255. Reduce that parameter value. When loading the Net Agent and Net Server, the number of :Agent Remote Handles: specified exceeded 4095. Reduce that parameter value. BNetII: When loading the Net Agent and Net Server, the number of [Agent Resources] specified exceeded 255. Reduce that parameter value.B-NET: Duplicate node name. Another node on the LAN has the same node name.BNET, BNetII: Invalid request block. The request block contains too many ReqPbCb pairs for the Net Agent and Net Server to handle. Try increasing the :Max Request Block Size: parameter. BNetII: The request block contains inconsistencies.BNET, BNetII: Invalid parameter. 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 cannot deinstall the Net Agent and Net Server. This might be because the Network Configuration Utility (NCU) is running on a client workstation while the Net Agent and Net Server is running on the server.BNetII: Agent No User Number Available. The Net Agent has run out of user numbers for local clients. Increase the value of the [Agent Users] parameter when loading the Net Agent and Net 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. This occurs during loading of the Net Agent and Net Server when an invalid character is entered for the [Compress] or :Use Compression: parameter value. If a program which is attempting to turn compression on or off gets this error, it indicates that the request indicated something other than on or off, or that the Net Agent and Net Server were loaded with an option other than per user.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 or the value of the value of the :Server Large Requests: parameter when installing the Net Server.BNetII: Internal. The Net Agent received a compressed message of the wrong length.Message too long. The request block and request pbcb's are too large. Try increasing the :Max Request Size: parameter and/or the :Max Message Size: parameter for the protocol stack used.BNetII: No Server Session Available. The Net Server cannot support any more sessions. When installing the Agent/Server on the remote node, increase the number of Server Sessions.BNetII: OSI Session Abort. The OSI Session has closed the connection.BNetII: File Spec too Long. The file specification (including default pathing information) exceeds 100 bytes.BNetII: Partial Buffer Received. The OSI Session sent BNetII an incomplete message. The OSI Transport Service was possibly installed after BNetII and the OSI Session.BNetII: Remote Partial Buffer. On the remote node, the OSI Session sent BNet an incomplete message. Possibly the OSI Transport Service was installed after BNetII and the OSI Session on that node.No OSI session. The Naming Service returned an entry for the target node indicating that it is reachable through the OSI Session, but the OSI Session is not loaded or not accessible. Wrong O/S type. An attempt was made to run BNetSrvr.run on a workstation that is not a server; or an attempt was made to run BNetClstr.run on a workstation that is not a client workstation. Font Services: Font Service Not Running. Deinstall Font Service command was issued when it was not running.Font Services: Incorrect Version Font Database. Installation of Font Service failed because the version of the runtime font database is incompatible 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 process of serving a request. 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 this 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 default 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. The Font Service returns this status code when it fails to install because the Font Service request codes are already being served by some service. Verify whether the Font Service has already been installed.Font Services: Cannot Deinstall. The Deinstall Font Service returns this status code under a single partition operating system.Font Services: Font Data Unavailable. The Font Service returns this status code 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 are 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 request (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 families.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.Font Service: Scaling Font Service required. The Font Service returns this status code if the reduced font key in a request for the font data indicates that the font should be scaled on the fly. This status code is also returned if the application (such as the HP LaserJet Device Driver) requires a font in a format that can only be supported by the Scaling Font Service.Scaling Font Service: Error opening outline file. Be sure that all the outline files are present in the directory specified when installing the Scaling Font Service ([Sys], by default). Also, verify that no access violations or disk errors are encountered when accessing each outline file.Scaling Font Service: Invalid parameters. The parametersI  passed to the Scaling Font Service are incomplete or specify a font that is out of range.Scaling Font Service: Scaling keys too complex. The Font Database names more scaling font keys or outlines than the Font Service can uniquely identify. Deinstalling the Font Service and deleting the metrics cache, before reinstalling the Scaling Font Service, will temporarily fix the problem. To correct the problem reduce the number of font keys in the Font Database that reference distinct combinations of outlines, character sets, and device type. The Scaling Font Service caches highly compressed (binary) representations of the device type, outlines, and character sets indicated by various font keys referenced in calls to the Scaling Font Service. Each of these is assigned a unique 8-bit identification that makes up half of the unique 16-bit handle used to identify each font in the small and medium format cells. (The other bits indicate the point size of the font.) These handles are used to reaccess fonts on successive calls to the Scaling Font Service (by OFIS Designer or Document Designer, for example) and to obtain font metrics cached in prior calls. This error indicates that the space for identifying distinct fonts has been exhausted. It is impossible to assign a unique font handle for reaccessing the font. You cannot reference more than 256 distinct scaling font keys, or more than 256 outline files qualified by distinct character sets.Scaling Font Service: Invalid outline file was accessed. If this occurs, reinstall the outlines from the distribution media and renationalize them if necessary.Scaling Font Service: An unanticipated error was detected in the Speedo portion of the Scaling Font Service supplied by Bitstream Inc.Scaling Font Service: An unanticipated error was detected in the portion of the Scaling Font Service implemented by Unisys.Scaling Font Service: Outline names too long. The Scaling Font Service caches the names of outlines used for scaled fonts in a fixed area of the metrics cache file, which is mirrored in memory. If the 12-character naming conventions in the released product are followed, this area has room for 194 outline names. If you are adding more outlines than this, rename them to use shorter names (for example, omit the .SFO suffix), and modify the Font Database accordingly. There is an architectural limit of 256 outlines that can be accommodated with 8-character names.Semaphore Service: No semaphore service memory. The semaphore service has run out of memory used to allocate semaphores. The most likely cause is that the client program is stuck in a loop allocating semaphores. In [Sys]Config.sys, you can use :cbSemMem: to specify the number of bytes to allocate for semaphore memory. A semaphore record is 38 bytes. Each local open semaphore requires one record. Each system open semaphore requires one record if the semaphore is unnamed, and two records if the semaphore has a name. Each process waiting for a non-critical semaphore requires one record.Semaphore Service: Semaphore name too long. A semaphore name cannot be longer than 36 bytes.Semaphore Service: Semaphore user number is too big. A user number specified in a call to SemEnumerate is greater than the number of users in the system.Semaphore Service: Semaphore handle is invalid. A handle specified for a semaphore operation is not a valid semaphore handle. A semaphore must not be opened for both critical selection and non-critical selection use.Semaphore Service: Semaphore invalid user. A call to SemOpen has specified exclusive use, and the semaphore is already open by another user, or a semaphore operation has specified a handle that was opened for exclusive use by another user.Semaphore Service: Semaphore timeout. The timeout specified in a semaphore operation occurred before the semaphore became clear.Semaphore Service: Semaphore owner terminated. The system returns this status code if the previous owner of the semaphore was terminated. The next owner that tries to obtain the semaphore will do so, but will receive this ercSemOwnerKilled. An application that receives this status code should take some action. For example, if the semaphore is used to lock the line printer, for example, and the owner of the semaphore dies, the next application to obtain the semaphore will know to skip to the top of the page. On the other hand, if the owner of the semaphore died while updating a database, the next owner of the semaphore might terminate saying "this database is corrupt."Semaphore Service: Semaphore overflow. The open count or the use count for a semaphore has been incremented to 0FFFFh.Semaphore Service: Semaphore locked. A semClose operation specified a semaphore that is currently locked. The semaphore must be cleared before it is closed.Paging Service: Paging Service internal. The Paging Service has detected an internal error.Paging Service: No replacement page. The page replacement algorithm could not find a replacement page. This can occur when a page fault is encountered. No pages in the users resident set can be replaced because they are all locked. No new pages can be allocated because the user has reached the maximum number of pages allocated or because there are no other pages available in the system. When the page fault handler encounters this status code the program is aborted. This error can also be returned by the LockPages request.Paging Service: Stack overflow. A stack overflow has been detected in a context running in the Paging Service. Each time a page fault occurs or a request is received by the Paging Service a fixed amount of stack space is allocated for the context. The amount of stack space allocated can be specified in Config.sys by the parameter PagingServiceStackSize. If no parameter is specified, a default of 400 bytes will be used.Paging Service: Heap memory not available. The Paging Service is out of heap space. Memory is allocated out of the heap for stack space each time a page fault occurs or a request is sent to the Paging Service. A fixed amount of heap space is allocated by the Paging Service during initialization. The amount of heap space allocated can be specified in Config.sys by the parameter PagingServiceHeapSize. If no parameter is specified the Paging Service calculates the amount of heap space by the formula (PagingServiceStackSize * numberOfPartitions) where numberOfPartitions corresponds to the number of partitions allocated to the system.Paging Service: Invalid heap block. The Paging Service has detected an invalid heap block. This could be due to an internal Paging Service error or to a program storing data in random memory locations.Paging Service: Not enough pages. A call to MapPages requested more pages be allocated and locked in than there are available in the system.Paging Service: Page not locked. UnlockPage or MapLocalPagesToLockedGla has specified a page that is not locked.Paging Service: Page not present. AliasPages or MapLocalPagesToLockedGla has specified a global linear address that is not present.Paging Service: Global linear address already used. A call to RemapPages or to MapPages with fPresentAndLocked has specified a global linear address that is already mapped. Note that MapUninitializedDataPages will unmap pages that are already mapped and change them to uninitialized data. This has the effect of freeing pages that are being used. MapPages with fPresentAndLocked is different because it is allocating new pages for a user that is about to be loaded.Paging Service: Too many backing store files. The Paging Service does not have room in its tables for another file handle specified by a Map operation. The maximum number of backing store files can be specified in Config.sys by the :BackingStoreFileCount: parameter. If no parameter is specified a default of 50 is used.Paging Service: Page locked. UnmapPages has specified a page that is locked. MapPages or MapUninitializedDataPages has specified a page that is already mapped and locked.Paging Service: Page not mapped. A Paging Service request such as AliasPages or LockPages or MapLocalPagesToLockedGla or RemapPages has specified a page that is not mapped.Paging Service: No local page map. A Paging Service request requires that the user have a local page map but none has been allocated by CreateLocalPageMap.Paging Service: Swap file too small. The size of the swap file is too small to be used. See the CTOS System Administration Guide for more information on swap files.Paging Service: Invalid parameters. A SetPagingParameters request has specified parameters that are invalid, for example, cFramesMin greater than cFramesMax.Paging Service: Write in progress. A ReassignPages request has specified memory that is currently being written to backing store. Or a request such as UnMapPages or MapPages when the page is already being used has caused the page to be unmapped and the page cannot be unmapped when a write is in progress.Paging Service: Paging Service already installed. Paging is already installed and an attempt has been made to install it again.PaginI g Service: User does not own page. A ReassignPages request specifies a page that does not belong to the user specified by oldOwner.Paging Service: Invalid page class. The page class was not valid. If no file handle is specified the page class must be data.PMOS: This internal error indicates a problem with the software you are using. PMOS: This internal error indicates an unsupported version of CTOS.PMOS: The PMOS service received a request block containing an unexpected request code. Some other service or client may be malfunctioning.PMOS: Like any service, PMOS cannot be installed after the Context Manager is installed. Deinstall 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.PMOS: No more real mode stacks are available. This error occurs when the [Maximum number of protected mode processes] parameter 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 64 Kb of message buffers. Try again with a smaller value.PMOS: Mover segment 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. 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.)PMOS: No mover handle available. This error occurs when the [Maximum number of Mover Server segments] parameter is exceeded. Reboot 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 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.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 that all message buffers are full, or that all large message buffers are full and a large message buffer is required. PMOS will use large message buffers for small messages if all small message buffers are full.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 received from a real mode program, or an internal error occurred in PMOS.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 user, 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 the CTOS Crash 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. 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 allocation 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 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 that 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 code segment. Only expand-up data segments may be converted to code segments.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.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 translateable to a real mode address because it refers to a 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 addresses and back en route.PMOS: Not enough memory. This status code occurs when upper memory is full.PMOS: This internal error indicates an invalid heap ID.PMOS: This internal error indicates LSD is already free.PMOS: No such run file. This message should not be returned to user programs. It is an internal error that 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.PMOS: No pending task. An internal error occurred while a protected mode program was loading. Specifically, PMOS received J an unexpected request from an instance of PmSubAgent.run.PMOS: Invalid default user number in effect for process at ConvertToSys time.PMOS: This internal error indicates a bad process descriptor (the structure used as an argument to CreateProcess).PMOS: No free CommLine control structure available. Internal error. This should never occur, since PMOS is built with enough of such control structures for ten (10) serial ports, the maximum possible on a workstation (with two XC-002 Port Expander modules in place). PMOS: Bad structCode operand to GetPStructure. This value of the structCode parameter is not supported. See the 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: Bad SetPStructure field offset. This field is not supported. See the Procedural Interface Reference Manual for a list of supported fields. 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 automatically.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.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 String 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 filled 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.FSA Finesse: Invalid computed term of investment. The calculated term of years, months, and days of the present value of investment is invalid. Check the validity of your input data.FSA Finesse: Invaild computed interest rate. The calculated interest rate for the investment is less than -99.999 or greater than 999.999. Check the validity of your input data.FSA Finesse: Data conversion error. This message is displayed when an error occurs while converting an input data string into a numeric value to be used in a computation. Check the validity of your input data.FSA Finesse: Invalid code in screen definition. The screen for a particular function has been created incorrectly and an invalid screen definition code is encountered. Contact your system administrator.FSA Finesse: Memory unavailable for loan payment array. The workstation does not have enough memory to calculate the amount on a multiple payment loan.FSA Finesse: Invalid computed loan payment amount. An error has occurred while computing the annual interest rate on a loan calculation. Check the validity of your input data.FSA Finesse: APR calculation error. One of the following errors has occurred:  The computed APR is greater than 99.99999  One or more of the amounts being used is less than or equal to zero Check the validity of your input data.Math Service: Numeric exception occurred. A numeric exception 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. This status code may also be caused by a Math Service or math co-processor exception when a floating point operation fails due to an illegal operand. FSA Finesse: Invalid date encountered. Enter the date in the correct format as defined in the System Parameters File. Note: The number of digits entered for a date must be at least five digits. If you enter fewer than five digits, you will receive this error.FSA Finesse: Conflicting term and payment frequency. The term of the loan is less than the payment frequency. Change the term or the payment frequency and recalculate.ENLS: Invalid offset in string. The offset parameter passed was invalid. This status code is returned if:  The oChar parameter points to the second byte of a multi-byte character mode  No characters precede the specified string offset  The specified string offset is greater than the size of the stringENLS: Invalid line type. The value specified in the bLineType parameter is not valid.ENLS: Buffer is full. The buffer provided is not large enough to hold the resulting string.ENLS: Invalid character. The character parameter passed was invalid. It cannot be classified or converted.ENLS: Exit character. This is not an error. The user selected an exit character. ENLSFieldEdit returned control to the application, and passed the status code to the application.ENLS: End of string. The value passed for the size of the input string was invalid. The buffer for the returned character is too small, or the cbString parameter in EnlsGetChar or EnlsGetPrevChar is set to 0.ENLS: Bad field type. The FieldType parameter passed to FieldEdit is invalid.ENLS: Value was not mappable. Either the Standard Value was not mappable to an equivalent value in the current character set, or a value in the current character set was not mappable to the equivalent Standard Value.ENLS: Bad string size. The specified string size is less than 0.ENLS: Invalid string.ENLS: Bad character returned.ENLS: Bad count returned. The count returned is incorrect.ENLS: Bad value returned. The value returned is incorrect.ENLS: Bad state pointer.ENLS: Bad form character pointer. This status code is returned if you provide a null pointer to the form character string to draw a line of form characters.ENLS: Bad form character size. The user supplied a negative number to the cbFormChars parameter.ENLS: Bad form attribute pointer. This status code is returned if you provide a null pointer to the form attribute string to draw a line of form characters.ENLS: Bad form attribute size.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 before or after the colon terminating a parameter identifier. AP Laser, AP Matrix drivers: The type of printer indicated is not a recognized string. CT Matrix driver: The printer name specified in the Device setup field is not recognized. Daisy driver: An unrecognized printer type was entered after the keyword :Printer:. Epson FX-286 driver: Characters were sent to the Epson device driver in the wrong y (vertical) order. (That is, a character with a lesser y coordinate was received by the driver after it had printed a character with a greater y coordinate.) This status code indicates an error in the application sending data to the GPS system. HP LaserJet driver: The name used for the sheet feeder is not recognized in the Device Setup field. 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. Imagen8300 driver: The document specifies more distinct fonts than can be output in one document by this device driver. Reduce the number of fonts in the document. This error indicates an overflow in the device driver's internal table. The printer usually overflows its own Font/Graphics Work Area long before the device driver does. The device driver makes no attempt to predict when the printer will overflow, and no error message is reported by GPS when the printer overflows its memory. PostScript driver: The emulatJ ion mode specified is inconsistent with the normal processing method specified in the Device Setup field. Device Driver: 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. APDMatrix driver: An invalid character set specification was given on the device setup line. AP Matrix, AP Hr Matrix drivers: The character set indicated is not a valid character set. AP Laser driver: The resolution indicated is not a valid resolution. Daisy driver: An unrecognized sheetfeeder type was entered after the keyword :SheetFeeder: or :Feed:. Epson FX-286 driver: A font has been defined in the Font Database that cannot be selected by the Epson device driver. The combination of keywords in the font key alias cannot be processed by the device driver. HP Plotter driver: The type of printer indicated is not a valid printer name. Imagen driver: The Font Database encountered an erroneous second-level translation value. Verify this driver has a valid "Font Device Type" string. Use the Font Tool to correct the translation data in the Font Database. Imagen8300 driver: An erroneous second level translation value has been encountered in the Font Database font translation data for the Imagen printer. Verify that the Imagen device driver was installed with a valid Font Device Type string. (Leaving this field blank causes the correct font data to be used if the Unisys-supplied Font Database is being used). Use the Font Tool to correct the Imagen's translation data in the Font Database. PostScript driver: An inconsistency was found attempting to output an accented character. 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. AP Matrix, AP Hr Matrix drivers: The ribbon indicated is not a recognized string. Or, a color has been selected for a printer that does not have the capability. APDMatrix driver: An invalid ribbon specification was given on the device setup line. HP Plotter driver: The type of media indicated is not a valid string. Device Driver: This is an internal error. Consult Customer Support. (GPS releases prior to 2.0.) APDMatrix drivers: A page width greater than the capabilities of the printer was specified. AP Hr Matrix, CT Matrix drivers: The resolution indicated is not a valid resolution. HP Plotter driver: The number of pens indicated is not correct for the plotter specified. Imagen, Imagen8300 drivers: A document requires more Imagen-printer "Families" than can be used at one time. Reduce the number of fonts in the document. PostScript driver: The emulation mode specified in the Device Setup field is not recognized. 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 the driver. APDMatrix drivers: A page length greater than the capabilities of the printer was specified. AP Hr Matrix: Sheet feeder value must be Yes or No. HP Plotter driver: The pen parameters are not correct. Imagen, Imagen8300 drivers: A document requires more Imagen-printer "Maps" than can be used at one time. Reduce the number of fonts in the document. PostScript driver: The emulation mode required for this print job cannot be set. (For example, if an OFIS Writer job is submitted to a PostScript printer that does not have the keyword :Emul: 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. HP Plotter driver: The polygon sent to the driver is too complex. Reduce the complexity of the picture. Imagen8300 driver: The normal job processing method specified in the Device Setup field cannot be used. PostScript driver: The value specified after the keyword :Delay: is not recognized in the Device Setup field.APDMatrix drivers: The polygon that was being printed has too many points specified. To correct the problem, break the polygon up into several smaller polygons. HP Plotter driver: The driver received too many polypoints. Reduce the complexity of the picture.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.Device Driver: The Font Device 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 internal error 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 internal error indicates a problem with the software. Contact the nearest Customer Support center. Device Driver: Unable to find or store string. This internal error 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 internal error 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 internal error indicates a problem with the software. Contact the nearest Customer Support Center. Device Driver: An invalid font handle was present in a call to DdGetAlias within the GPS Device Driver. This internal error indicates a problem with the software. Contact the nearest Customer Support center. Device 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 device 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 internal error indicates a problem with the software. Contact the nearest Customer Support center. Device Driver: The recipient data structure specified in a call to DdChXlate within the GPS Device Driver was too short. This internal error indicates a problem with the software. Contact the nearest Customer Support center.Device Driver: Out of memory for font tables or raster image work area. To print the document, reinstall the device driver and specify a larger amount under Storage Allocation in the Font/Graphics Work Area field.Device Driver: Insufficient 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. Device Driver: There is not enough memory within the device driver to store the font definitions or raster image work area required by this document. Additional memory may be allocated within the device driver by reinstalling it with a larger number in the Font/Graphics Work Area field of Print Manager Device Installation form.Device Driver: An invalid font handle was present in a call to DdChWidth within the GPS Device Driver. This internal error 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 internal error indicates a problem with the software. Contact the nearest Customer Support center. (GPS release 2.0.)Device Driver: Error allocating memory from the Font/Graphics Work Area. This internal error indicates a problem with the software. Contact the nearest Customer Support center. Device Driver: Unable to retrieve string. This internal error 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/Graphics Work Area field in the Print Manager Device Installation form. Otherwise, an internal error that indicates a problem with the software. Contact the nearest Customer Support center. Device Driver: This internal error indicates the device driver's memory heap has been corrupted. Contact the nearest Customer Support center. Device Driver: There is not enough memory within the device driver to store the font definitions or raster image work area required by this document. In addition, memory may be allocK ated within the device driver by reinstalling it with a larger number specified in the Font/Graphics Work Area field in the Print Manager Device Installation form.Device Driver: An invalid font handle was present in a call to DdChXlate within the GPS Device Driver. This internal error indicates a problem with the software. Contact the nearest Customer Support center. Device Driver: Cannot scale graphic. The device driver does not have sufficient memory to scale an image. Reinstall the printer with a larger value in the Font/Graphics Work Area field. If the maximum value in the Font/Graphics Work Area field (64K) has already been specified, rescan the image at the size to be printed (or some smaller size than before).Device Driver: The timeout period has expired for the Network Printing Gateway to wait for a response from across the network.Device Driver: The timeout period specified has expired for the Network Printing Gateway to wait for a response from a CTOS application or service.Device Driver:  No message blocks are available for communication to a Network Printing Gateway session process.Device Driver: Network Printing Gateway session not available.Device Driver: Network Printing Gateway process not available.Device Driver: Bad parameters passed to a Network Printing Gateway call.Device Driver: Network Printing Gateway request is not known.Device Driver: Network Printing Gateway request is being forwarded.Device Driver: Print Service version should be updated.Device Driver: Print Service is not available.Device Driver: Bad session Id.Device Driver: Network Printing Gateway cannot deinstall.NPGW, CTOS NFS /NPS: The mount daemon on remote host is not responding with a valid handle. Verify that mount is installed on the remote host.NPGW, CTOS NFS /NPS: The nfs daemon on the remote host is not responding with a valid handle. Verify that the nfs daemon is installed on the remote host. NPGW, CTOS NFS /NPS: The pcnfs daemon on the remote host is not responding with a valid handle. Verify that pcnfs is installed on the remote host. NPGW, CTOS NFS /NPS: The print job failed for some reason other than an invalid printer name. The most common reason is that the server was unable to create a spool directory. Log onto the remote host and try to manually create the pcnfsd's spool directory (with a default mode). Note and follow any resulting error message(s).NPGW, CTOS NFS /NPS: The call failed because the remote printer name specified in the Device Setup line in the GPS printer device driver configuration screen (NPGW: printer_name), did not name an available printer. Deinstall the VPDD and enter a valid printer name in the Device Setup line. Then, reinstall the VPDD. NPGW, CTOS NFS /NPS: The remote spool call failed for some other unspecified reason. Deinstall the remote pcnfsd and reinstall it with it's trace option turned on, if tracing is available. Note any resulting error message after attempting to print a file. NPGW, CTOS NFS /NPS: The server determined that the file was already being printed and that no further action was taken. The client will usually interpret this to mean that the request was retransmitted because an original response with status of "OKAY" was lost. NPGW, CTOS NFS /NPS: The server determined that the file was empty, and therefore not printed. The server deletes the file before returning this status. The pcnfsd did not spool the job with the remote print system because it determined that the file had a length of zero. Make sure that the print file, you are attempting to print, does not have a length of zero.NPGW, CTOS NFS /NPS: The print job failed because the print file could not be found. NPGW: The print job failed while creating an authentication handle. CTOS NFS / NPS: The print job failed because not enough memory could be allocated during a UNIX authentication call. UNIX authentication failed because not enough memory could be allocated for the call's return data structure. Make sure enough memory is available to the client.NPGW, CTOS NFS /NPS: The mount of the remote spool directory failed. Generally, the spool directory will fail to be mounted because the spool directory was not exported correctly or the correct clients are not listed. Make sure that the spool directory is exported correctly and that its clients are listed correctly.NPGW: The creation of the remote spool file failed. CTOS NFS / NPS: The print job failed because the file could not be created in the remote spool directory. Generally, a files fails to be created because the spool directory has been exported as "read only" or because the user does not have the correct permissions to access the spool directory. Make sure that the spool directory is exported correctly, and that the clients, the directory is being exported to have the correct permissions.NPGW: The writing of the remote spool file failed. CTOS NFS / NPS: The print job failed because the file could not be written into the remote spool directory. Generally, a files fails to be written because the spool directory has been exported as "read only" or because the user does not have the right permissions to access the spool directory. Make sure that the spool directory is exported correctly, and that the clients, the directory is being exported to have the correct permissions.NPGW: The remote host name entered in the location field of the GPS Printer Device Driver configuration screen was invalid. CTOS NFS / NPS: The print job failed because the named remote host is invalid. The remote host name specified in the Location field of the VPDD installation screen did not name an available remote host. Deinstall the VPDD and enter a valid host name in the Location field. Then, reinstall the VPDD.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.Device Driver: The normal mode setting is incompatible with your other settings.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 must 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: Error encountered determining page orientation during installation. Check Device Setup parameters in Print Manager. This internal error 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.0 Installer (GpsInstall.run) is being used. Consider deleting the existing .state and .config files for the affected device before repeating the installation process. CD-ROM: Maximum number of CD-ROM files are open on the server. If possible, close some files that are in use. If you need to open more files, deinstall the CD-ROM System Service. Then re-install CD-ROM Service, increasing the number in the [Maximum number of CDROM files open] parameter. If you install the CD-ROM Service through the SysInit.jcl file, you may want to increase the value for [Maximum number of CDROM files open] there as well.CD-ROM: Invalid CD-ROM handle. This indicates a software error, usually caused by disturbances in the cluster or network. Most likely, the server was rebooted, and the connection to the CD-ROM module is no longer valid.CD-ROM: Invalid CD-ROM device specification. In the CTOS environment, this status code indicates that an invalid file or device specification has been received during a CdOpen or CdSearchFirst request. See the CTOS CD-ROM User's Guide. In the DOS environment, this status code indicates that an error was made when issuing the CDR Assign command. Try using the CDR Assign command again, making sure that all parameters are filled in correctly. See the CTOS CD-ROM User's Guide.CD-ROM: There is no such CD-ROM device number at the server. In the CTOS environment, this status code indicates that a device name was received during a CdOpen or CdSearchFirst request. See the CTOS CD-ROM User's Guide to determine the proper device name. In the DOS environment, this status code indicates that you have assigned a drive letter to a CD-ROM module that does not exist. Reassign the drive letter to the CD-ROM module. At the MS-DOS prompt (C:>), type Type AutoExec.bat to see if a CDR Assign command for a nonK existent module is included in the AutoExec.bat file. If so, see the discussion on adding or removing CD-ROM Modules in the CTOS CD-ROM User's Guide. CD-ROM: Internal CD-ROM software Error. A software error has occurred. Consult Technical Support. If possible, try to remember the sequence of events that led up to the error; it might help Technical Support pinpoint the problem.CD-ROM: The CD-ROM device is in use. Another user has opened the CD-ROM module in mode private, restricting access of the device. You will have to wait until that user closes the CD-ROM module before you can access this device. To allow multiple user access, the CD-ROM should be opened in mode share.CD-ROM: The drive letter has not been assigned to a CD-ROM. Assign a drive letter to the CD-ROM module (using the CDR Assign command), as explained in the CTOS CD-ROM User's Guide. Note: This error occurs only in the DOS environment.CD-ROM: The CD-ROM device has not been opened. A CD-ROM software error has occurred, or there is a problem with the cluster or network. In most cases, the CD-ROM software will restart automatically, but you may have to reassign a drive letter to the CD-ROM module. Note: This error occurs only in the DOS environment.CD-ROM: The CD-ROM is currently performing an audio operation. Another user has opened the CD-ROM module and is currently performing an audio operation. You must wait until the audio operation is halted by this before you can access this device.CD-ROM: End-Of-File encountered while accessing a CD-ROM file. The end of a CD-ROM file has been reached while performing a CdRead operation. When this error occurs, check the number of bytes successfully read by the service. Note: This error occurs only when making CdRead requests in the CTOS environment.CD-ROM: Invalid CD-ROM buffer. An invalid buffer pointer has been passed to the CD-ROM System Service. Either the buffer is too small for the requested operation, or a null pointer has been received by the service. Note: This error occurs only in the CTOS environment.CD-ROM: The CD-ROM device is not ready. An attempt was made to access the CD-ROM device and it was not ready. Make sure that the CD-ROM disc is inserted properly in the device. Note: This error occurs only in the CTOS environment.CD-ROM: The CD-ROM device has reported a hardware error. A hardware error has occurred. Consult Technical Support. If possible, try to remember the sequence of events that led up to the error; it might help to identify the problem. Note: This error occurs only in the CTOS environment.CD-ROM: Share Mode Violation. A request was received to perform a function that is only allowed in Mode Private (such as Lock/Unlock Door and Eject Disc) on a volume that is open in Mode Share. Note: This error occurs only in the CTOS environment.CD-ROM: An Invalid CD-ROM function has been requested. A bad function value was passed to the CD-ROM System Service when making a CdControl, CdAudioCtl, CdGetVolumeInfo, or CdServiceControl request. Note: This error occurs only in the CTOS environment.CD-ROM: No such CD-ROM file. The requested CD-ROM file was not found during a CdOpen, CdSearchFirst, or CdSearchNext request. Note: This error occurs only in the CTOS environment.CD-ROM: CD-ROM Service Heap Too Small. An internal software error has occurred during service initialization. Consult Technical Support. If possible, try to remember the sequence of events that led up to the error; it might help pinpoint the problem.CD-ROM: CD-ROM Service Heap Full. The CD-ROM System Service heap is full. This error can occur when many active users access the CD-ROM service. Retry the last request be retried, since heap resources are dynamic. Note: This error occurs only in the CTOS environment.CD-ROM: Invalid CD-ROM Service Heap Node. An internal heap management software error has occurred. Consult Technical Support. If possible, try to remember the sequence of events that led up to the error; it might help pinpoint the problem.CD-ROM: No available CD-ROM user numbers. All of the user numbers in the CD-ROM System Service have been used. This error can occur when many active users are accessing the CD-ROM Service. When this error occurs, retry the last request. If the problem recurs, deinstall the service and then re-install it with a larger number entered in the [Maximum number of CDROM users] parameter field.CD-ROM: CD-ROM Buffer size or LFA not a multiple of 512. The return buffer size or LFA passed during a CdRead request is not a multiple 512. Note: This error occurs only in the CTOS environment.CD-ROM: No such CD-ROM path. The specified path does not exist on the CD-ROM disc. Note: This error occurs only in the CTOS environment.PC Emulator, CTOS/Vpc: An inconsistent state has been discovered in the application's software. FSA Finesse: After entering data, press GO to store data.PC Emulator, CTOS/Vpc: 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 or CTOS/Vpc software. FSA Finesse: Press the NEXT PAGE key to display the rate screen.PC Emulator, CTOS/Vpc: The PC service version does not match the PC Emulator or CTOS/Vpc version. FSA Finesse: Press GO to confirm or CANCEL to deny.PC Emulator, CTOS/Vpc: Bad color value specified in the PC Emulator or CTOS/Vpc 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, CTOS/Vpc:  Too many colors specified in the PC Emulator or CTOS/Vpc configuration file. A maximum of eight different colors may appear on a color monitor at one time. PC Emulator, CTOS/Vpc: Hardware and/or system software required to run the PC Emulator or CTOS/Vpc is not present on this workstation. The CTOS/Vpc requires either a PC Emulator module or an 80386-based processor module running the CTOSII operating system. The PC Emulator requires either a PC Emulator module or an 80386-based processor module running BTOSII or CTOS/VM operating system.PC Emulator, CTOS/Vpc: Only one PC Emulator or CTOS/Vpc session is possible when using a PC Emulator module. Only one PC Emulator or CTOS/Vpc session is possible when using a PC Emulator module. You can have more than one session only when the PC Emulator or CTOS/Vpc is used directly on an 80386-based processor module.CTOS/VPC: Physical DOS partition access not supported. Access to a physical DOS partition on the disk drive is not supported on this platform. You must have a CTOS EISA/ISA workstation in order to make use of this feature. CTOS/VPC: Physical DOS partition access error. An error has been encountered while trying to access a physical DOS partition on the disk drive. The operating system is unable to obtain consistent disk geometry information for the disk drive. CTOS/Vpc: DriveC and DriveD have been assigned to the same physical device. Make the necessary changes to your Vpc configuration file ([Sys]UsernamePC.sys) and restart Vpc.  FSA Finesse: Invalid value for category.FSA Finesse: Clear screen first.PC Emulator, CTOS/Vpc: 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. FSA Finesse: Press NEXT PAGE, PREV PAGE, CANCEL, or FINISH.FSA Finesse: Beginning year must not be later than ending year.FSA Finesse: Value cannot exceed 30 years.FSA Finesse: Loading Customer Service files ...FSA Finesse: Teller level too low for access to Admin.FSA Finesse: Partial word processor record written for Interviews.FSA Finesse: Waiting for AMP printer. FSAFinesse 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 the specified port.FSA Finesse: Waiting for V&R printer. FSAFinesse 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: Insert.FSA 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 properlyFSA Finesse: Turn page, insert.FSA Finesse: Printing.FSA Finesse: Remove.FSA 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 key.FSA Finesse: Invalid line number, try again.FSA Finesse: Press COPY for journal, RETURN or NEXT for form.FSA Finesse: Press COPY for ticket, RETURN or NEXT for form.FSA Finesse: Press NEXT.FSA Finesse: STOP key pressed on the AMP, document cancelled.FSA Finesse: Module out of paper; ReplaL ce or press FINISH to abort.FSA Finesse: (This message consists of 80 spaces.)FSA Finesse: Transport jam.FSA Finesse: Load paper.FSA Finesse: End of document detected.FSA Finesse: Remove document after printing is done.FSA Finesse: Cover open; Replace or press CANCEL key.FSA Finesse: Cover closed.FSA Finesse: Station manually deactivated.FSA Finesse: CANCEL key pressed, Current document cancelled.FSA Finesse: AMP time out.FSA Finesse: Invalid device config file. FSAFinesse has received one of the following messages from the BTOS Device Service:  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. This 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 handlerFSA 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 Forms definition indicated  A passbook transaction was performed, but the Forms definition does not specify the AMP printer FSAFinesse 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 failure AMP  50130 to 50143: Internal and confidence test routine errors Contact your system administrator.FSA Finesse: Device server not available. During system sign-on, the Device Service system service was not successfully installed. Use the FSAFinesse 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). FSAFinesse received an error from the Screen and Keyboard Module while attempting to retrieve the optional line number. Note the number and contact your data processing department or system administrator.FSA Finesse: AMP keyboard error, try again.FSA 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 system administrator.FSA Finesse: Spooler queue error - (nnnnn). An error was encountered in an attempt to send information to the Spooler Utility. See the relevant section of this status codes documentation 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. See the relevant section of this status codes documentation for a description of the status code displayed in parentheses.FSA Finesse: Device Sharing Error. FSAFinesse has received one of the following 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 small FSA Finesse: Device Server/Sharer error - (nnnnn). See the relevant section of this status codes documentation for a description of the status code displayed in parentheses.FSA Finesse: AMP Forms Handler not available. The Form 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 system administrator.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 system administrator.FSA Finesse: 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 system administrator.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: Unable to access StoreBuffer.Dat file. Exit to FSAFinesse Executive and reload Customer Service/Teller Module. Contact your system administrator.FSA Finesse: Waiting for MCR; press CANCEL.FSA Finesse: Waiting for PIN keypad; press CANCEL.FSA Finesse: Waiting for OCR reader; press CANCEL.FSA Finesse: Pass card through MCR.Enter PIN and press *FSA Finesse: Pass MICR document through OCR reader.FSA Finesse: Unable to retrieve account number.FSA Finesse: MCR read error; CANCEL to quit; NEXT to retry.FSA Finesse: PIN read/device error: press CANCEL 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 received.FSA Finesse: OCR field format error.FSA Finesse: MCR not active.FSA Finesse: PIN not active.FSA Finesse: OCR not active.FSA Finesse: PIN validation unsuccessful; press CANCEL to quit, NEXT to retry.FSA Finesse: MCR customizing error. The MCR field layout record of the MCR/OCR File was customized incorrectly. Verify the accuracy of that file.Request Set Utilities: Syntax error. This error occurs only in Make Request Set when the user has entered invalid data in the request text file. A variety of conditions can cause syntax errors. Check for the following:  Entries that do not follow 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 restrictionsRequest Set Utilities: Request block offset too large for previous request. Constants in the parameter list must be less than 255 decimal. The following example illustrates a valid request block parameter list: :Params: w(12), w(14), p(16), c(2,20) The following example illustrates a request block parameter list that would generate an erc 16385: :Params: w(12), w(14), p(16), c(2,300)Request Set Utilities: Request codes in level non-contiguous.Request Set Utilities: Text line too long. This error code only occurs in Make Request Set when a request text file contains a text line that exceeds 512 characters.Request Set Utilities: Invalid field descriptor.This error only occurs in Make Request Set when an invalid request block field descriptor has been encountered in a request text file. Valid field descriptors are: :RequestCode:  :RequestName: :Version: :LclSvrCode: :ServiceExch: :sCntInfo: :nReqPbCb: :nRespPbCb: :Params: :NetRouting: :SrpRouting:Request Set Utilities: Missing parenthesis. This error only occurs in Make Request Set when a subparameter entry in the :Params: descriptor field of the request text file is missing a parenthesis. The following example illustrates an entry which would result in an erc 16389: :Params: w(12), w(14), p(16, c(2,20)Request Set Utilities: Invalid parameter type. This error only occurs in Make Request Set when an invalid subparameter type is encountered in the :Params: descriptor field of the request text file. Valid subparameter type are: b, w, p, or c which signify byte, word, pointer, and constant respectively.Request Set Utilities: Invalid constant supplied. An input parameter to one of the Request Set utilities contains a non-numeric constant where a numeric constant was expected, such as in the Exclusion List parameter in List Request Set, or the parameter constants foundL  in the request text file. For example, this status code would be returned if you attempt a Make Request Set with the following line in a Request text file: :Params:w(12),w(20),w(18),(w22),w(16),w(14),p(24), c(bogus, value)Request Set Utilities: Internal error.Request Set Utilities: Invalid subparameter type. This error occurs only in Make Request Set when a constant type subparameter in the :Params: descriptor field of the request text file is missing a comma. An example of an invalid entry is as follows: :Params: w(12), w(14), p(16), c(2 20) The proper entry is: :Params: w(12), w(14), p(16), c(2, 20)Request Set Utilities: No exchange specified for the previous request.Request Set Utilities: No sCntInfo specified for the previous request.Request Set Utilities: Invalid value or literal. This error occurs only in Make Request Set when an invalid entry has been made in the :ServiceExch:, :NetRouting:, or :SrpRouting: descriptor fields of the request text file.Request Set Utilities: Invalid range for constant. This error occurs only in Make Request Set when a :ServiceExchange: value greater than 256 or :sCntInfo: value of greater than 63 has been entered in the request text file.Request Set Utilities: Duplicate field descriptor. This error only occurs in Make Request Set. Examine the request block and delete the duplicate field descriptor.Request Set Utilities: Insufficient table space for procedural interface code. This error only occurs in Make Request Set (should rarely if ever happen) when the application has become overloaded with request information. Please review the request text file(s) to be processed and look for abnormalities.Request Set Utilities: Level 0 requests may not be loaded. This error only occurs in Make Request Set when a request code of less than 1000h is encountered in the request text file. All request codes defined in the request text file MUST be greater than or equal to 1000h. 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.Request Set Utilities: Request codes -1 through -32 may not be loaded. This error only occurs in Make Request Set when a request code greater than or equal to FFE0h is encountered in the request text file. All request codes defined in the request text file MUST be less than FFE0h. FSA Finesse: Unable to print, Press CANCEL to cancel printing, NEXT to retry (For FSA Finesse, this message consists of two lines, 16401 and 16402.)FSA Finesse: Printing on same printer or GO to reroute to backup printer. (For FSA Finesse, this message consists of two lines, 16401 and 16402.) Request Set Utilities: This internal error only occurs in Make Request Set.Request Set Utilities: Malformed request file. This error occurs in List and Update Request Set when an old style request file has been encountered. Contact Technical Support for help.Request Set Utilities: This internal error only occurs in Make Request Set.Request Set Utilities: Procedural interface code is invalid for request. This error occurs in List and Update Request Set when the binary request file contains an invalid procedural interface request block. The only way to recover from this error is to restore a binary request file that you know is good.Request Set Utilities: Invalid offset for pbcb. This error occurs in List and Update Request Set when the binary request file contains an invalid pbcb offset. The only way to recover from this error is to restore a binary request file that you know is good.Request Set Utilities: Procedural interface is not allowed in odd levels. This error occurs in List and Update Request Set. To use the request procedural interface and validity checking procedures, a request must be defined by a request code in an even-numbered level. Odd-level request codes are reserved for system requests.Request Set Utilities: This internal error occurs in List and Update Request Set.Request Set Utilities: Not a valid type. This error occurs in all of the Request Set Utilities. The error occurs in Make Request Set if the user enters an invalid type parameter when invoking the Make Request Set command from the executive. Valid type parameters are: SRP, Ws, or Current. If this error occurs in List or Update Request Set either your binary request file is old or it is corrupt. First try restoring a binary request file you know is good. If this fails, call Technical Support.Request Set Utilities: Invalid request block offset. This error occurs only in Make Request Set when a subparameter has been entered in the :Params: descriptor field with an offset of less than 12. An example of :Params: entry which would result in this error follows: :Params: w(10), w(12), p(14), c(2, 18)Request Set Utilities: The size of the request data in the output request file exceeds 64KB.Request Set Utilities: There are too many requests defined. This error occurs only in Make Request Set when more than 32759 request codes have been processed. Decrease the number of requests. Request Set Utilities: The two request files are not of the same type.FSA 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 Allowed.FSA Finesse: Scrolling and Paging Allowed.FSA Finesse: Error; Press CANCEL to Continue.FSA 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 number is not in the permitted range. Enter a buffer size in the range of 1 to 64.FSA Finesse: Buffer size exceeded. Used for internal flow control within SKM. Contact your system administrator.FSA Finesse: Invalid text area. Used for internal flow control within SKM. Contact your system administrator.FSA Finesse: Invalid screen ID. Used for internal flow control within SKM. Contact your system administrator.FSA Finesse: Screen not found. Contact your system administrator.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 system administrator.FSA Finesse: Help ID not found. Customizing error. Contact your system administrator.FSA Finesse: Invalid screen handle. Internal error. Contact your system administrator.FSA Finesse: Screen handle not active. Internal error. Contact your system administrator.FSA Finesse: Saved screen found. Internal error. Contact your system administrator.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 system administrator.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 not retrieved.FSA 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.FSA Finesse: Invalid data type. Used for internal flow control within SKM. Contact your system administrator.FSA Finesse: Data too large for field. Used for internal flow control within SKM. Contact your system administrator.FSA 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 defined.FSA Finesse: Invalid field number. Internal error. Contact your system administrator.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 Finesse: CheckField in session. Used for internal flow control within SKM. Contact your system administrator.FSA Finesse: Invalid exit key. Used for internal flow control within SKM. Contact your system administrator.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 tM he 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 system administrator.FSA Finesse: Invalid key code. Used for internal flow control within SKM. Contact your system administrator.FSA Finesse: Not enough memory available. Used for internal flow control within SKM. Contact your system administrator.FSA Finesse: Null string. Used for internal flow control within SKM. Contact your system administrator.FSA Finesse: Blank string. Used for internal flow control within SKM. Contact your system administrator.FSA Finesse: Invalid string. Internal error. Contact your system administrator.FSA Finesse: Invalid number of screens. This error occurs in the Test Drive routine. The maximum number of screens that can be entered depends on the Finesse release level (for Finesse 2.0, the maximum is five, for Finesse 3.0 the maxium number is seven). Reenter the number of screens.FSA Finesse: Main menu. Used for internal flow control within SKM. Contact your system administrator.FSA Finesse: Delete. Used for internal flow control within SKM. Contact your system administrator.FSA Finesse: Duplicate. Used for internal flow control within SKM. Contact your system administrator.FSA Finesse: Cancel. Used for internal flow control within SKM. Contact your system administrator.FSA Finesse: Screen design. Used for internal flow control within SKM. Contact your system administrator.FSA Finesse: Finish. Used for internal flow control within SKM. Contact your system administrator.FSA Finesse: Exit. Used for internal flow control within SKM. Contact your system administrator.FSA Finesse: Screen exists. To duplicate an existing screen, enter a unique screen ID for the duplicate screen.FSA Finesse: Field within selection. Used for internal flow control within SKM. Contact your system administrator.FSA Finesse: Unable to secure LRU memory. All the memory in the pool has been allocated. This is a Fatal Error: All programs terminate. 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: SKM Font Service Error.FSA Finesse: Special Routines Module (SRM) Error.FSA Finesse: Invalid month.FSA Finesse: Invalid day.FSA Finesse: Invalid year.FSA Finesse: Invalid edit code.FSA Finesse: Invalid input for edit.FSA Finesse: Invalid hour.FSA Finesse: Invalid minute.FSA Finesse: Invalid second.FSA Finesse: Invalid AM/PM.FSA Finesse: Invalid data length.FSA Finesse: Invalid field size.FSA Finesse: Invalid currency code for SRM Editing.FSA Finesse: Maximum currency size exceeded.FSA Finesse: Invalid check digit position (CDV).FSA Finesse: Invalid input data.FSA Finesse: Invalid check digit (CDV).FSA Finesse: Invalid type specified.FSA Finesse: Input data out of range.FSA Finesse: Length of data out of range.FSA Finesse: Invalid value.FSA Finesse: Invalid multiple of denomination.FSA Finesse: Invalid data length.FSA Finesse: Invalid Tran ID.FSA Finesse: Transaction not allowed offline.FSA Finesse: Supervisor password required.FSA Finesse: User defined memory exceeded. Contact your supervisor. Contact your system administrator.FSA Finesse: Screen for transaction does not exist.FSA Finesse: Please press GO to transmit.FSA Finesse: Transaction selection not possible for this document.FSA Finesse: Teller level not valid for transaction access.FSA Finesse: Input needed for required field.FSA Finesse: Tran not allowed in Multi Cash Check mode.FSA Finesse: Tran not allowed in Tran Audit mode.FSA Finesse: Multi Cash key not allowed in Tran Audit mode.FSA Finesse: Tran Audit key not allowed in Multi Cash Check mode.FSA 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 continue.FSA Finesse: Transaction out of balance.FSA Finesse: Amount greater than maximum length.FSA Finesse: Teller transaction limit exceeded; supervisor override required.FSA Finesse: Supervisor transaction limit exceeded.FSA Finesse: Field value out of range.FSA Finesse: Field value not correct multiple.FSA Finesse: Not a multi-paged transaction.FSA Finesse: Required field on Page 1.FSA Finesse: Required field on Page 2.FSA Finesse: Required 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 Denomination/Settle file is zero or the multiple for rolled/strapped amounts in the System Parameters File is zero.FSA Finesse: Transaction not allowed; a page has no input field. The system will return to the teller idle mode. Do not input transaction again. Contact your system administrator.FSA Finesse: Error during EJ build - EJ not built. FSAFinesse 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. Contact your system administrator.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. See the BTOS FSAFinesse Installation Utilities Operations Guide for the procedure.FSA Finesse: Unknown Erc from MFIFDI.FSA Finesse: Customer Service not available for this workstation.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 current field but the field definition for this field does not exist on disk. Verify the Transaction and Field Definition files are correct.FSA Finesse: Error detected during field handling. An error was detected during output of the current field. Verify all custom files associated with fields are correct. If you cannot solve the problem with the custom files, contact your system administrator.FSA Finesse: Access error on previous field. FSAFinesse is unable to process the previous field on the screen. Verify all custom files associated with screen fields are correct.FSA Finesse: Exchange Rate record not in memory.FSA Finesse: Currency code does not exist in Exchange Rate File.FSA Finesse: Error in reading Exchange Rate file.FSA Finesse: Unable to allocate memory. The system is not able to allocate needed memory. Stop processing immediately and notify your system administrator. A memory allocation problem has occurred within the Heap Management Module while processing the response from the host. The current transaction will not terminate normally, and processing will return to the teller idle state. Contact your system administrator.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 system administrator.FSA Finesse: Customer already in session.FSA Finesse: Initialize new customer session.FSA Finesse: Deallocation error. Contact your supervisor. A memory problem has occurred. Complete the current transaction, but do not continue processing. Contact your system administrator.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 system administrator.FSA Finesse: Header field length greater than maximum length allowed. This error message was received while building a data communication message. While attempting to build a message to send to the host, FSAFinesse 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, FSAFinesse 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 index length. This error message was received while building a data communication message. While attempting to build a message to send to the host, FSAFiM nesse 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. While attempting to build a message to send to the host, FSAFinesse 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, FSAFinesse encountered the displayed error. Verify the data communication information in the Transaction and Data Comm Definition files.FSA Finesse: Invalid common index 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, FSAFinesse 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 message to send to the host, FSAFinesse 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, FSAFinesse encountered the displayed error. Verify the data communication information in the Transaction and Data Comm Definition files.FSA Finesse: Not enough memory to build indices. This error message was received while building a data communication message. While attempting to build a message to send to the host, FSAFinesse 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, FSAFinesse encountered the displayed error. Verify 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, FSAFinesse 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 message to send to the host, FSAFinesse 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, FSAFinesse encountered the displayed error. Verify the data communication information in the Transaction and Data 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, FSAFinesse 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 to build a message to send to the host, FSAFinesse 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, FSAFinesse encountered the displayed error. Verify the data communication information in the Transaction and Data Comm Definition files.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, FSAFinesse 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 length.FSA Finesse: Press CANCEL to end search.FSA Finesse: Press NEXT PAGE to continue.FSA Finesse: Invalid 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 Reversals.FSA 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, FSAFinesse encountered the displayed error. Verify 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, FSAFinesse 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 message. While attempting to build a message to send to the host, FSAFinesse encountered the displayed error. Verify the data communication information in the Transaction and Data Comm Definition files.FSA Finesse: Criteria not met for next transaction.FSA Finesse: Press CANCEL to continue, CODE+CANCEL to cancel linked set.FSA Finesse: Press NEXT to begin next transaction in linked set or CODE+CANCEL to cancel link.FSA Finesse: Unsuccessful link; contact your supervisor. The system is unable to initiate the next conditionally linked transaction. A conditional search table needed to initiate a conditionally linked transaction is not defined.FSA Finesse: Unable to continue processing based on current data.FSA Finesse: Clear current field and press RETURN to skip this field.FSA Finesse: Enter new data.FSA Finesse: Field level validation unsuccessful.FSA Finesse: Press NEXT to initiate host transaction, CANCEL to ignore.FSA Finesse: Unable to process host transaction, Press NEXT key.FSA Finesse: Conditional Linking not active; file not loaded.FSA Finesse: Conditional file error. Contact your supervisor. The Conditional Search File has been accidentally deleted or corrupted. The file must be recreated. Contact your system administrator.FSA Finesse: Message sent to host:FSA Finesse: Message received from host:FSA Finesse: Check writer transaction is not required.FSA Finesse: Press NEXT PAGE or PREV PAGE to continue, CANCEL to exit.FSA Finesse: Press NEXT or PREV PAGE to continue.FSA Finesse: ** Posting Date has changed on the Branch Processor. **FSA Finesse: Unable to retrieve form ID- (nnnnn). A form was specified to be printed in the Transaction Definition process cannot be retrieved because it does not exist or is corrupt. Verify that the custom files are correct.FSA Finesse: Press NEXT to duplicate, FINISH to continue.FSA Finesse: Host data discarded. Data were received from the host but, the matching form definition did not access or retrieve the data, so the data were discarded. Check the message received against the forms listed in the transaction definition record. If the problem continues, contact your system administrator.FSA Finesse: Transaction cancelled.FSA Finesse: Press VALIDATE OFFLINE to continue, CANCEL to quit.FSA Finesse: Host 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.FSA Finesse: Waiting for host response ...FSA Finesse: Host Format Error: (nnnnn).FSA Finesse: Error encountered during Auto Reentry. FSAFinesse 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 interrupted.FSA Finesse: Auto Reentry Complete.FSA Finesse: Teller not signed on to Auto Reentry. An error received from the host by the Branch ControlN  Module has indicated 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, host interface parameters 1 and 2.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.FSA Finesse: ReEnter Password.FSA Finesse: ReEnter New Password For Verification.FSA Finesse: ReEntered Password does not match New Password.FSA 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. Contact your system administrator.FSA Finesse: Security Violation.FSA Finesse: Press GO to change password.FSA Finesse: Another supervisor password required.FSA Finesse: Invalid multiple of roll or strap amount.FSA Finesse: Printer module not available.FSA Finesse: Maximum total amounts exceeded.FSA Finesse: Invalid date.FSA Finesse: Invalid entry.FSA Finesse: Invalid teller number.FSA Finesse: Invalid password.FSA Finesse: Teller A already signed on.FSA Finesse: Teller B already signed on.FSA 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. Contact your system administrator.FSA Finesse: Vault cash in.FSA Finesse: Vault cash out.FSA Finesse: Invalid Currency Code.FSA Finesse: Sign on to Auto Reentry.FSA Finesse: Unable to go online. Verify that your station address is set properly in each of the following:  FSAFinesse Station Parameters File  Host Network Definition Language (NDL) configuration  Host Message Control System (MCS) configuration  Agent ConfiguratorFSA Finesse:  Auto Reentry initiated.FSA Finesse: MCR file not available. The attempt to activate the MCR device is unsuccessful. Records need to be defined to utilize the device. See the BTOS FSAFinesse 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. See the BTOS FSAFinesse 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. See the BTOS FSAFinesse Operations Guide, Volume2: Teller Functions.FSA Finesse: Unable to initiate Auto Reentry. Verify that the date was entered correctly. See the Auto Reentry directions in the BTOS FSAFinesse Operations Guide, Volume2: Teller Functions. Finesse 3.0: The Automatic Reentry routine cannot be initiated. The transaction or transaction screen may not exist or may be corrupt. Make sure that the Transaction Definition File is correct. Contact your system administrator.FSA Finesse: Press FINISH to interrupt.FSA Finesse: BCM wait time elapsed; press CANCEL to return to 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 Branch Control Module is running. If there are many stations configured, the Branch Control Module wait time should be increased.FSA Finesse: Password level incorrect.FSA Finesse: Day and date do not agree.FSA Finesse: Invalid date and time entry.FSA Finesse: Station ID already in use.FSA Finesse: Station ID already in use.FSA Finesse: Invalid station ID.FSA Finesse: Checks-In List.FSA Finesse: Cash-Out List.FSA Finesse: Cashed Check List.FSA Finesse: Customizing error, Laser Form ID - nnn. Enter valid source or location in source.FSA Finesse: Error reading laser forms definition file. Contact your system administrator.FSA Finesse: Error creating Forms Plus Laser WP merge file. Contact your system administrator.FSA Finesse: Forms Plus Server request queue not available. Install Forms Plus Server.FSA Finesse: Forms Plus Server status queue not available. Install Forms Plus Server.FSA Finesse: Unable to communicate with Branch Control Module. The current processing is not verified. Make sure that the Branch Control Module is running. If the BCM has been reinstalled, the Customer Service/Teller Module must be reloaded.FSA Finesse: Press NEXT PAGE to display next teller's records.FSA Finesse: Function not allowed; transactions are conflicting transaction types. An attempt was made to perform:  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 transactionFSA Finesse: Function 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 entered.FSA Finesse: Detail search not allowed on local transactions.FSA Finesse: Sequence number beyond range of EJ summary records.FSA Finesse: No more EJ records match criteria.FSA Finesse: Branch Control Module has 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 ignored and the CTM continues to wait for the correct message.FSA Finesse: Waiting for valid response.FSA Finesse: No Detail record stored for this transaction.FSA Finesse: No Host Response stored for this transaction.FSA Finesse: Perform next EJ Search.FSA Finesse: Host now online.FSA Finesse: Host now offline.FSA Finesse: Unknown message type received from Branch Control Module. A message was received from the Branch Control Module that the Customer Service/Teller Module (CTM) cannot interpret. Contact your system administrator.FSA Finesse: Unexpected Sign On response, ignored.FSA Finesse: Unexpected Sign Off response, ignored.FSA Finesse: Unexpected Cash Balancing response, ignored.FSA Finesse: Unexpected Vault Cash response, ignored.FSA Finesse: Unexpected Branch Totals response, ignored.FSA Finesse: Unexpected Batch Totals response, ignored.FSA Finesse: Unexpected Teller Totals response, ignored.FSA Finesse: Unexpected Checks In List response, ignored.FSA Finesse: Unexpected Cash Out List response, ignored.FSA Finesse: Unexpected Cashed Checks List response, ignored.FSA Finesse: Unexpected Sign On to New Posting Date response, ignored.FSA Finesse: Unexpected Establish New Posting Date response, ignored.FSA Finesse: Unexpected Auto Reentry Initiated response, ignored.FSA Finesse: Unexpected Auto Reentry Suspended response, ignored.FSA Finesse: Unexpected Password Level Inquiry response, ignored.FSA Finesse: Return Customer Cash: (nnnnn).FSA Finesse: Transaction Audit initiated.FSA Finesse: Transaction Audit completed.FSA Finesse: Multi Cashed Check initiated.FSA Finesse: Total of checks cashed: ($nnnnn).FSA Finesse: Unexpected EJ Totals response, ignored.FSA Finesse: Unexpected EJ Update response, ignored.FSA Finesse: Unexpected EJ Search response, ignored.FSA Finesse: Unexpected EJ List response, ignored.FSA Finesse: Invalid menu selected.FSA 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 Module. Finesse 3.0: Status Area Definition Z400 must exist in the Transaction Definition File in order to continue to initialize the Customer Service/Teller Module (CTM).FSA Finesse: Unable to initialize system, press any key to exit. Finesse 3.0: Unable to initialize system, press FINISH key to exit. Reboot 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 See 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 Control 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 already 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 sucN cessfully.FSA Finesse: Unable to load Device Service. During system sign-on, a problem has been encountered while attempting to load the Device Service.FSA Finesse: Request for Supervisor Override received; press RCV MSG or CANCEL.FSA Finesse: Invalid Speed Transaction ID.FSA Finesse: Requested Speed Transaction ID has not been defined.FSA Finesse: Press TLR-A or TLR-B key.FSA Finesse: Invalid Local Routine ID.FSA Finesse: For Teller A.FSA Finesse: For Teller B.FSA Finesse: Unable to find Device Configuration File(s).FSA Finesse: Exiting to Administrative Application.FSA Finesse: Exiting to Finesse Executive.FSA Finesse: Exiting to CTM.FSA 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.FSA Finesse: Deallocation error. Internal error. Contact your system administrator. 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 of memory that was allocated. Internal error. Contact your system administrator.FSA Finesse: Memory stack overFlow. Too many variables have been allocated on the memory management stack. Internal error. Contact your system administrator.FSA Finesse: Unable to allocate memory management stack. Available memory is insufficient to allocate the memory management stack. Internal error. Contact your system administrator.FSA Finesse: Unable to allocate memory. Available memory is insufficient for allocation. Internal error. Contact your system administrator.FSA Finesse: Invalid type. The application has given an invalid pointer or the pointer pointed to was not found.FSA Finesse: Invalid type. There is no type available.FSA Finesse: Invalid Size. The size was specified with 0 length. Specify a size other than 0.FSA Finesse: Invalid bit position. The bit position does not fall within the allowable range. Internal error. Contact your system administrator.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 system administrator.FSA Finesse: Invalid number string. Non-numeric character in numeric string. Internal error. Contact your system administrator.FSA Finesse: Invalid parameter specified. Either the destination string is too small or the source string is empty. If this condition occurs during an attempt to print a form, the form may need to be split into multiple forms. If this condition continues, contact your system administrator. Internal error. Contact your system administrator.FSA Finesse: Invalid string size. The string length must be between 0 and 32763, inclusive. Internal error. Contact your system administrator.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 system administrator.FSA Finesse: Invalid pointer, value is nill. A nill string is being used as a parameter. Internal error. Contact your system administrator.FSA Finesse: Invalid order of deallocation. Internal error. Contact your system administrator.FSA Finesse: Unable to open file. The file you tried to open is not an RFAM file. Enter the name of an existing RFAM file. If that fails, delete the file and restart.FSA Finesse: Close failed. Could not close the raw file. Press the FINISH key and try again.FSA Finesse: File not found. The file does not exist, or the file specification is incorrect. Enter the name of an existing RFAM file.FSA Finesse: Invalid file specification. The file specification is incorrect. Reenter the file name in the correct format.FSA Finesse: File in use. File is in use. Try again when the file is not in use.FSA Finesse: Stack full. Internal VDAM error. Contact your system administrator.FSA Finesse: Stack empty. Internal VDAM error. Contact your system administrator.FSA Finesse: Extend node. Internal VDAM error. Contact your system administrator.FSA Finesse: Keep looking. Internal VDAM error. Contact your system administrator.FSA Finesse: OverWrite key. Internal VDAM error. Contact your system administrator.FSA Finesse: Key found. The specified key was found. Contact your system administrator.FSA Finesse: Insert and shift. Internal VDAM error. Contact your system administrator.FSA Finesse: Invalid key specified. Internal VDAM error. Contact your system administrator.FSA Finesse: Out of memory. Internal VDAM error. Contact your system administrator.FSA Finesse: Key not found. The key pointed to was not found, or this message was caused by a customizing problem. Make sure the key value you entered is correct and reenter the value. Reload the SKM menu files and restart.FSA Finesse: Duplicate key. The key pointed to is a duplicate. FSA Finesse: Need to split node. Internal VDAM error. Contact your system administrator.FSA Finesse: Compress failed. CompressFile error. The file is corrupted. Reload a back-up copy of the file and try again. Contact your system administrator.FSA Finesse: Build of temporary file failed. Insufficient disk space exists to hold temporary files created by the Compress File function or Recover Key File function. Delete any unnecessary files from the disk and try again. Contact your system administrator.FSA Finesse: CleanUp failed. CompressFile error. Contact your system administrator.FSA Finesse: File name build failed. Problem creating temporary files used by CompressFile and RecoverKeyFile. Contact your system administrator.FSA Finesse: Read failed. VDAM File read problem. Contact your Unisys representative. Finesse 3.0: The file is corrupted. Reload a back-up copy of the file and try again.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. Finesse 3.0: The file is corrupted. Reload a back-up copy of the file and try again.FSA Finesse: Record not found. The key exists, but the corresponding record does not. Delete the key file and then recover it using the Recover Key File function. Contact your system administrator.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 system administrator.FSA Finesse: No current key. Internal VDAM error. Contact your system administrator.FSA Finesse: Invalid insertion. Internal VDAM error. Contact your Unisys representative. Finesse 3.0: The file is corrupted. Reload a back-up copy of the file and try again.FSA Finesse: Node not found. Internal VDAM error. Contact your system administrator.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. Shorten the length of the key entered. Contact your system administrator.FSA Finesse: Cannot chain to [!SYS]EDITOR.RUN. Verify Editor.Run has been installed. Contact your system administrator.FSA Finesse: Cannot chain to [!SYS]SMTRANSLATOR.RUN. Verify SmTranslator.Run has been installed. Contact your system administrator.FSA Finesse: I-code file and Interpreter are incompatible. Edit the Smart File with the Authoring Tool.FSA Finesse: Numeric value is too large to convert for FILL statement. The value used in a FILL statement cannot be larger than 2147483647.FSA Finesse: String data cannot be converted to binary. Check the string for errors. String is longer than 255 characters or does not represent a numeric value.FSA Finesse: Binary data cannot be converted to a string. String is too short. The receiving string variable is not long enough to hold the resulting string or the resulting string is longer than 255 characters.FSA Finesse: Use of uninitialized data. The value of a data variable not initialized is used. Check the Smart File for any uninitialized data.FSA Finesse: Division by zero. Check the Smart File for division by zero.FSA Finesse: Text data returned from Export Import is too long. Actual text data is longer than length defined in the Smart File.FSA Finesse: Invalid instruction code, I-Code file may be corrupted. Have the Smart File edited with the Authoring Tool and generate I-Code again with Test Driver. If the problem continues, contact your system administrator.FSA Finesse: Cannot display Smart Sell recommendation screen. You must use the Display Screen command before using the Write To Field command in the Smart File.FSA Finesse: No memory allocated for the Smart Sell WRITE TO BUFFER. Verify the memory allocation of the Smart Sell API buffer in the CTM application program. If the problem continues, contact your system administrator.FSA Finesse: Cannot write beyond Smart Sell buffer maximum size. TotO al length of data written to the Smart Sell API buffer exceeds the size of the buffer. Verify the data length in the Smart File and the memory allocation of the buffer in the CTM application program. If the problem continues, contact your system administrator.FSA Finesse: Cannot display trace. Smart File has been changed or is corrupted. Verify Smart File is correct. If not, recreate Smart File.FSA Finesse: Smart File data declaration error. Check the Smart File data declaration portion and make the necessary correction. Verify the external reference for each data, and all the source numbers, field in source and field type codes are within the range.FSA Finesse: Number of fields exceeds limit or screen does not exist. Check the Display Field command for external references. The screen ID cannot exceed 5 characters and the total number of fields cannot exceed 200. The total number of fields must agree with the actual number of fields defined on the screen.FSA Finesse: WRITE TO FIELD error. Field number is incorrect. Check the Smart File and verify the WRITE TO FIELD statement. Look for the filed number and verify it is valid. Verify the length and type of each filed on the screen.FSA Finesse: Data length is greater than maximum length. Verify the initial value and the expected value of each numeric data of the Smart File. The data cannot exceed 80 characters.FSA Finesse: Decode error. Internal error. Contact your system administrator.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 TWOTASK error.Oracle: Specified 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.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.Oracle: ORACLE failed to initialize because of insufficent memory for SGA. Oracle: ORACLE failed to initialize because the required SGA (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.Oracle: Internal OSD wait failure.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.Oracle: ORACLE could 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 file.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.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 invalid. 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 invalid. 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.SNA 3270 Terminal Emulator, BSC 3270 Terminal 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. 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 Module has reset CPU.BNA: BTOS BNA did not load successfully. See PLog for more information.BNA: Invalid request code received by BNA Log Agent.BNA: Invalid RqOp value received by BNA Log Agent.BNA: BNA Message Compatibility Table already initialized in BNA Log Agent.BNA: BNA Log Agent encountered error in renaming log file.BNA: BNA Log Agent attempted to close a log file that was already closed.BNA: BNA Log Agent truncated a log message.BNA: Invalid BNA/B-NET Support Service (BBSS) parameter.BNA: BBSS encountered a fatal internal error.SNA Transport, BTOS OSI Transport-LAN: Internal error. An attempt was made to use a station that is already in use. LAPB, X.25, HDLC LAPB, NRM: The data-link is already in use.SNA Transport, BTOS OSI Transport-LAN: Internal error. An attempt was made to use a station that is not configured or there are no more free addresses. LAPB, HDLC LAPB, X.25: Invalid station address. There are no more station addresses available in the data-link level. HDLC NRM: The control unit address identification number in the configuration file is invalid. Either you have entered a non-numeric value or a number beyond 254. Valid station CU address numbers are 1 through 254. ISDN Service: The LAPD station address is not configured. LAPD returns this code if the Service Access Point Identifier (SAPI) specified by the client in the OpenStationLL or OpenStationSL request has not been configured with the ISDN>LAPD.config file. Check the Station Descriptor (SD) string values provided by the client and change the SAPI value there to match the value provided in the ISDN>LAPD.config file or change the SAPI value in the ISDN>LAPD.config file to match the value provided in the client's SD string.SNA Transport, BTOS OSI Transport-LAN: Internal error. An attempt was made to access an unopened station. ISDN Service: An attempt is made to access an unopened station. LAPD returns this code when a request is received with an unrecognized station handle or Connection Identifier. This occurs if a ReadDLFrame, WriteDLFrame, CloseStation, or DirectStation request was issued with an invalid connection identifier or without first exchanging a successful OpenStation request. A modification of the client software is required to resolve the problem.SNA Transport, BTOS OSI Transport-LAN: Internal error. An attempt was made to use a service by other than the opening user. ISDN Service: The client user number does not match the user number for this LAPD connection. A service was requested by someone other than the opening user. LAPD returns this code if the user number in the request block does not match the user number given in the OpenStationLL or OpenStationSL request.O  A modification of the software may be required to resolve the problem.SNA Transport, BTOS OSI Transport-LAN: Internal error. An attempt was made to use an undefined command in the DirectDLL request. ISDN Service: LAPD returns this code to indicate one of the following:  A DirectStation request with invalid pSend information  An invalid loop code in DirectLink request  An invalid DirectLink command code A modification of the client software is required to resolve the problem.SNA Transport, BTOS OSI Transport-LAN: Internal error. An attempt was made to use an unsupported command with the DirectDLL request. ISDN Service: A defined command which is not supported by this Link Layer was used in DirectLink. LAPD returns this code to DirectStation or DirectLink requests when the command code is not supported by LAPD or to a WriteDLFrame with the connection ID set for a broadcast connection. A modification of the client software is required to resolve the problem. Ethernet DLL: Command not supported. Mnemonic: ErcNotSupported There is a defined command in either the DirectLink or DirectStation request that is not supported by the CTOS Ethernet Data Link.SNA Transport, BTOS OSI Transport-LAN: Internal error. The buffer size in the WriteDLFrame request is larger than the maximum frame install parameter. ISDN Service: The buffer size given in WriteDLFrame request is larger than the maximum user data size install parameter. Reconfigure either LAPD's or the client's user data size. Ethernet DLL: Data truncated. Mnemonic: ErcXmtDataTrunc The buffer size given in the WriteDLFrame request (I or UI frames), or the DirectStation Transmit Test command request, is larger than the maximum frame install parameter (if any). The truncated data is transmitted across the line.SNA Transport: Internal error. An attempt was made to specify a buffer size of zero in a ReadDLFrame or WriteDLFrame request. BTOS OSI Transport-LAN: The received frame is larger than the maximum frame install parameter buffer provided in a ReadDLFramerequest. LAPB, HDLC LAPB and X.25: Invalid frame size. The frame received was larger than the maximum user data size parameter setting in the link level configuration file. You may need to check the packet level maximum packet size to correct the problem. HDLC NRM: The maximum user data parameter link level configuration file setting is too small to accommodate the frame received. You may need to check the frame size your application is passing to the link level, and then reset your maximum user data large enough to accept the frame. ISDN Service: LAPD returns this code if it receives a UI frame that doesn't fit in the outstanding Read request buffer and no more Read requests are queued. The request buffer is filled and the remaining data is discarded. Reconfigure the client to send larger Read request buffers or to keep more ReadDLFrame requests outstanding.SNA Transport, BTOS OSI Transport-LAN: Internal error. The buffer size specified in the ReadDLFrame or WriteDLFrame request was zero. ISDN Service: LAPD returns this code if the user specified a zero (0) length buffer in the WriteDLFrame request. A modification of the client software is required to resolve the problem.SNA Transport, BTOS OSI Transport-LAN: The line is inoperable. LAPB, HDLC LAPB and X.25 LAPB: The data-link is down. ISDN Service: The line (media) is inoperable. LAPD returns this code to write requests if the physical interface goes down or the DLCI is removed. This code indicates normal LAPD operations. No recovery action is required.SNA Transport: Abort or terminate condition. BTOS OSI Transport-LAN: The operation has been terminated.SNA Transport: Internal error. An outstanding request has been cancelled. BTOS OSI Transport-LAN: An outstanding request has been canceled due to a DirectStationCancel command. ISDN Service: LAPD cancelled all outstanding requests at the client's request. LAPD returns this code if LAPD receives a DirectStation request with the Cancel Requests command. When LAPD receives this command, it returns all outstanding requests for the station with this code. The Cancel Requests command is returned with erc=0. This code indicates normal LAPD operations. No recovery action is required. Ethernet DLL: Request canceled. Mnemonic: ErcReqCanceled An outstanding request was canceled due to one of the following requests: - DirectStation with one of these bCommands: Cancel Reset Logical Link Open Logical Link Close Logical Link - CloseStation - An abort request - A terminate request - ReadDLFrame responding with a reset event - WriteDLFrame, when the maximum number of WriteDLFrame requests are already queuedSNA Transport: Deinstall request for wrong type of operating system. BTOS OSI Transport-LAN: Attempt to deinstall on a single-partition operating system or attempt to deinstall from a remote workstation.SNA Transport: Deinstall request when the Context Manager is installed.SNA Transport: An attempt was made to deinstall the DLL when a user was active.SNA Transport: The parameter must be Y (yes) or N (no) in upper or lower case. HDLC LAPB and X.25 LAPB: The wait for DCE ACK parameter in link level configuration file has an invalid entry. The entry must be Y (Yes) or N (No), in either upper case or lower case. For performance reasons, it is recommended you use the No setting.SNA Transport: Invalid frame modulus. HDLC LAPB and NRM, and X.25 LAPB: Frame modulus value entered in the link level configuration file is not 8. Only modulus 8 is supported.SNA Transport: Invalid number of outstanding frames. HDLC LAPB and NRM, and X.25 LAPB: The number of outstanding frames entered in the link level configuration file is incorrect. Valid entries are 2 through 7.SNA Transport: Invalid communications channel specification. HDLC LAPB and NRM, and X.25 LAPB: Invalid communication channel parameter was entered in the link level configuration file. Check to see if the communication channel is being used by another application or that you have assigned a valid communication channel in the configuration file.SNA Transport: Invalid communications type specification. HDLC LAPB and NRM: Invalid communication port parameter. Valid entries are 1 for RS-232 and 2 for X.21.SNA Transport: Invalid maximum frame size. HDLC LAPB: Maximum user data size invalid. Maximum user data must be large enough to handle your maximum data size. HDLC NRM: Maximum user data size invalid. The size of the maximum user data parameter must be large enough to handle the maximum frame size passed by your network level application. X.25 LAPB: Maximum user data size invalid. Maximum user data must be large enough to handle your maximum packet size.SNA Transport: The installation buffer memory size is too small or too large. HDLC LAPB and NRM, and X.25 LAPB: Buffer memory size is too small or too large. Buffer size is based upon the maximum user data size and the number of outstanding frames.SNA Transport, BTOS OSI Transport-LAN: Invalid switched ID. HDLC NRM: The value used in the switched ID parameter in the link level configuration file is not in the correct format.SNA Transport: Invalid station address. BTOS OSI Transport-LAN: The installation station address is invalid. HDLC NRM: The value used for the station CU address in the link level configuration file is invalid. The number is either out of range or the entry is non-numeric. Valid values for control unit addresses are 1 through 254. Ethernet DLL: Bad CU Address. The LSAP or MAC address specified is invalid.SNA Transport: Invalid line speed.SNA Transport, BTOS OSI Transport-LAN: The request code list or station information buffer is too small. HDLC: Invalid PDN type. Refer to the High-Level Data Link Control documentation for the valid types of Public Data Networks.HDLC: Invalid T1 Timer value. Refer to the High-Level Data Link Control documentation for the valid values of T1 Timers.HDLC: Invalid N2 counter value. Refer to the High-Level Data Link Control documentation for the valid values of the N2 counter.HDLC: Invalid MGS service ID length. The length must be 12 alphanumeric characters, including brackets. X.25 LAPB: Invalid MGS service ID length. The length must be 14 alphanumeric characters, including angle brackets.X.25 LAPB: Invalid MGS service ID length. Maximum allowable size is 14 alphanumeric characters, including angle brackets.X.25: Access point handle is closed. The access point handle specified in the call is not currently open.X.25: A non-APM procedure called. The application called a SAM or PAM procedure not in the APM interface. Applications cannot combine calls to procedures from more than one X.25 Gateway interface.X.25: VC not in access point handle. The virtual circuit specified in the call does not belong to the application's access point handle.X.25: Outstanding requests returned. The application requested that all outstanding read requests be returned.X.25: Invalid bAppend value. The value assigned to this variable is not in the range of values pr