You lose, fella. The EMTP logic has detected an error condition, and is now going to terminate program execution. The following2 O; X0 u1 }7 K0 L
message summarizes the circumstances leading to this situation. Where an otherwise-unidentified data card is referred to, or where $ ]3 A- Q1 }" F* d) n8 S. r) @# Nthe "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 * ?! l$ [$ a- E# H; i8 y# M( cis generally the last one printed out prior to this termination message. But possibly this last-read card has not yet been8 H0 } @2 P4 D% w6 n
displayed, so a copy follows: 7 S3 [3 r3 B B "14X0184A 0 2.2E5 50. -1. 1." / G0 N& X# p2 H1 R KILL code number Overlay number Nearby statement number+ \' A6 G6 D) a9 b# K! j
12 5 4246& j- M6 O4 U6 ~) Y9 Z9 W
KILL = 12. The bus name that was read from columns 3-8 of the last source card is unrecognizable, not having been previously + |$ n* C% Z3 @, E: @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 + X3 ^# v7 N/ X4 {sources to network nodes that are not a part of the network that was previously defined by branch and switch cards of this data- H! m: Q/ ~) z7 d/ s' N4 E
case. Any such new node would be completely disconnected from the network, so could not affect the solution. Most probably, one or' X2 {' N9 \3 Q" x' T% }/ i; m
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.