You lose, fella. The EMTP logic has detected an error condition, and is now going to terminate program execution. The following2 F% i; v9 |- u) k" z
message summarizes the circumstances leading to this situation. Where an otherwise-unidentified data card is referred to, or where9 o* Y# g, o% j# f9 [# e2 Z4 b
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 card 1 Y4 c( O7 Y" W" n5 Pis generally the last one printed out prior to this termination message. But possibly this last-read card has not yet been , \& D1 A- d7 a7 fdisplayed, so a copy follows: / j6 A4 o e% H% S" p/ [( Z "14X0184A 0 2.2E5 50. -1. 1." , f; H& d( x! c+ m- t# m KILL code number Overlay number Nearby statement number . E" c/ ]* f8 X @' M" K3 a 12 5 42461 b5 K. F. |* V8 O
KILL = 12. The bus name that was read from columns 3-8 of the last source card is unrecognizable, not having been previously! j% h6 l0 d2 w" J" \+ J- R5 M
defined by a branch card or a switch card. The name read from the data card is "X0184A". The user is not allowed to connect * ], M# ^$ i9 R' i: C8 ~" R4 o: Asources to network nodes that are not a part of the network that was previously defined by branch and switch cards of this data( {- d' O# E4 [% r7 |9 B
case. Any such new node would be completely disconnected from the network, so could not affect the solution. Most probably, one or9 u( C3 J: y; a, y5 }4 A: ]
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.