You lose, fella. The EMTP logic has detected an error condition, and is now going to terminate program execution. The following! k; c: A& N, a3 H; j/ \& _
message summarizes the circumstances leading to this situation. Where an otherwise-unidentified data card is referred to, or where0 }6 F) a- w2 U: V
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 card2 R- s- D) ~# \
is generally the last one printed out prior to this termination message. But possibly this last-read card has not yet been 7 p8 p5 K1 e. W. A m; n4 S1 Ydisplayed, so a copy follows:) g& e4 _) \0 o, K7 }) k1 S+ B6 S3 Z2 Y
"14X0184A 0 2.2E5 50. -1. 1." ! a- y. ^! I+ Z KILL code number Overlay number Nearby statement number: Y3 L0 J( c9 X/ R. I+ _7 N
12 5 42469 S7 N: e. m" F
KILL = 12. The bus name that was read from columns 3-8 of the last source card is unrecognizable, not having been previously 5 d. j! Y9 C# ?* x1 j9 U7 \; @2 f0 Sdefined by a branch card or a switch card. The name read from the data card is "X0184A". The user is not allowed to connect / k9 m+ f( v4 @" {sources to network nodes that are not a part of the network that was previously defined by branch and switch cards of this data $ ^: \# A8 S' Xcase. Any such new node would be completely disconnected from the network, so could not affect the solution. Most probably, one or" [& m9 ]# W3 M- f+ k2 v- T
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.