You lose, fella. The EMTP logic has detected an error condition, and is now going to terminate program execution. The following * q; [) G: y+ fmessage summarizes the circumstances leading to this situation. Where an otherwise-unidentified data card is referred to, or where4 Y+ o1 U# U6 F! ?% Q( a1 \5 [6 X- C5 O
the "last" card is mentioned, it is the most recently read card of the input data that is meant. The 80-column image of this card5 @ g' t9 K4 U9 F: Y U- d
is generally the last one printed out prior to this termination message. But possibly this last-read card has not yet been 5 n1 E# O, P8 K: L) e6 Odisplayed, so a copy follows:1 \: \5 K. Y& I6 s# [
"14X0184A 0 2.2E5 50. -1. 1." / v9 P0 O; v" j" y0 a- _& D KILL code number Overlay number Nearby statement number, ?1 o9 e; `- ?; ~ e! W6 J
12 5 4246 3 W& n" G/ i9 I K% bKILL = 12. The bus name that was read from columns 3-8 of the last source card is unrecognizable, not having been previously 5 [% P$ z [3 R9 R6 t! Pdefined by a branch card or a switch card. The name read from the data card is "X0184A". The user is not allowed to connect 0 R8 a4 i1 ]5 o S' D, @, V& isources to network nodes that are not a part of the network that was previously defined by branch and switch cards of this data# @# {! w. P4 ]! L5 y! q
case. Any such new node would be completely disconnected from the network, so could not affect the solution. Most probably, one or6 T7 T" `5 l1 b
more spelling errors (including the positioning of imbedded blanks) have been made in the keying of one or more node names on EMTP data cards.