> C:\ICOMIS\COMIS\BINARY\COMIS.EXE
> This program has performed an illegal operation and will be shut down.
> The exception occurred in COMBDPL
>
> I think could be a problem with software versions.
> In other cases
> (a previous version of tht same case study - windows schedule only)
> in the .cof file appears
>
> ***CER*** SEVERE ***
> Did not find expected word
> Variable=get schedule name in CheckTMS
> looked from position = 8 to pos=9
> for a word in the 3 long string:
> string=*W1
> ***CER*** FATAL ***
> Variable: get schedule name in CheckTMS.
> Could not proces the input line listed below:
> *W1

This is just a wild guess, but you may have too many links defined.

Subroutine COMBDPL doesn't do much besides sum pressure differences on
a per-link basis. There isn't much opportunity to throw an
illegal-operation error, except by trying to access outside of an array
bounds.

Early versions of COMIS did not always check that the number of inputs
stayed within their pre-defined limit. In particular, the old code for
COMIS v.3.0.2 did not check that the number of links read out of the
CIF file did not exceed the maximum number of links for which storage
was allocated. (This is in subroutine INLINK, in file comv-in5.for, in
case anybody with source code wants to check).

By contrast, COMIS v3.1 does check the maximum link count. It sounds
to me like you need to upgrade to COMIS v3.1.

-Dave

David Lorenzetti
Lawrence Berkeley National Laboratory