You lose, fella. The EMTP logic has detected an error condition, and is now going to terminate program execution. The following) \$ {+ e0 [" l* b0 j3 X
message summarizes the circumstances leading to this situation. Where an otherwise-unidentified data card is referred to, or where . E1 n6 t8 Q$ xthe "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 9 v A: f) \! N& _* n0 I, r) uis generally the last one printed out prior to this termination message. But possibly this last-read card has not yet been2 D) b8 ?9 P# {/ c: q
displayed, so a copy follows: 6 ]; m9 N, i* s1 }# t K+ F: N& h "14source 0 311. 50. -1. 1." 9 ^6 ~* A' ]2 C( O# o7 |' z1 E. s3 K KILL code number Overlay number Nearby statement number/ Z8 t- \" w( o3 a0 s
12 5 4246 4 E/ N$ Q$ I! q( b1 |/ C* {KILL = 12. The bus name that was read from columns 3-8 of the last source card is unrecognizable, not having been previously ! J1 |/ a7 ] I/ e; ^5 c- P/ Wdefined by a branch card or a switch card. The name read from the data card is "source". The user is not allowed to connect - J' ^" X7 a* i( j( bsources to network nodes that are not a part of the network that was previously defined by branch and switch cards of this data/ |7 o/ @9 z" F/ h6 c3 X# T
case. Any such new node would be completely disconnected from the network, so could not affect the solution. Most probably, one or' q% Y4 F& h- I
more spelling errors (including the positioning of imbedded blanks) have been made in the keying of one or more node names on EMTP% U7 K+ U( ?# p9 ^- q
data cards. 9 ~, l% E: @8 {& u6 K$ P% `' Q3 Z0 Y) v/ U& ^, B0 w