KILL = 122. An overflow of TACS storage space has occurred, for TACS table number 7. For a definition of such storage, see* W7 }' v3 {" X1 }7 \ r6 R6 V
"ABSOLUTE TACS DIMENSIONS" in Section II-A of the EMTP Rule Book. The problem is with a sub-table, really, a partition of size 3 i2 p7 c# W+ ]4 [' u7 {8 [1 [4 ?24955 within EMTP List 19 (which allocates total TACS storage). Since the List 19 space can be allocated among TACS tables at / \/ ?, a! M5 E* S+ `* `! xexecution time (using "ABSOLUTE TACS DIMENSIONS"), it may not actually be necessary to increase List 19. For Salford EMTP,, n% S( [3 E8 m
dynamic dimensioning allows an expansion of List 19 at the start of execution (by changing LISTSIZE.DAT). But other systems 0 Q; p! B( }5 z3 ~require a compiler, linker, and variable-dimensioning program VARDIM. If "ABSOLUTE TACS DIMENSIONS" has been used, the $ G* Z4 p* B/ s8 H$ Y) z"Present figure" for List 19 will show the total working space that is required for the user-requested dimensions, and this should% b3 k, G6 Z- z% k$ ~8 o
be compared with the available total space of List 19. On the other hand, if it is "RELATIVE TACS DIMENSIONS" that is used, the0 F3 T. s4 A" W) t) c: U( B
"Present figure" will simply equal the limit, always. In any case, the user can allocate the available space among the different $ y6 F2 M/ |' ^5 dTACS tables only if he knows the multiplicity of each. These are as follows: 4 H' g( \. R7 S, V5 m' Y TACS Table Number 1 2 3 4 5 6 7 8' S6 F' z' W! U/ B
REAL multiplicity 4 2 0 5 0 0 1 69 d: Y. v. {8 B4 n5 |
INTEGER multiplicity 8 0 2 1 3 1 0 2 1 _4 n, m# n% I" Y& ^ z/ b0 o4 F Total multiplicity 12 2 2 6 3 1 1 8 - x/ E; h; o/ z7 y: HThe TACS table sizes that just proved to be inadequate were: 0 \% ]. ?4 b6 U( r, E5 h) J TACS Table Sizes 1426 6417 7130 652 2139 17825 24955 4278% Z% p, K' z) F; f$ h) S8 h; D. {