When your casefile data resides in separate directories below a parent, such as:
/home/bjn /home/bjn/data1 /home/bjn/data2 /home/bjn/data3
It is valid to use the global path to specify the parent directory, and the individual files to give the path on down. Such as:
cfiles global path: /home/bjn cfiles: data1/file1.case data2/file_b.case data3/bruce.case
This will result internally as the same thing as if you had done:
cfiles: /home/bjn/data1/file1.case /home/bjn/data2/file_b.case /home/bjn/data3/bruce.case
If you desire to use all casefiles on one server, you can obviously do so with the above option by using the SOS with one server. However, there is a variation on this option that can be used without using the SOS. It can be used with a client and server alone.
It is very similar to the MULTIPLE_CASEFILES option in an SOS casefile, except that it is placed in the first regular casefile of the series - the one that you will read. It uses APPENDED_CASEFILES as the section header, and lists just the additional casefiles (not the one that this is placed in).
So instead of using the SOS with an SOS casefile like
FORMAT type: master_server gold MULTIPLE_CASEFILES total number of cfiles: 4 cfiles global path: /home/bjn cfiles: bjn1.case bjn2.case bjn3.case bjn4.case SERVERS number of servers: 1 machine id: gun executable: ensight_server
You could place the following in bjn1.case
FORMAT type: ensight gold GEOMETRY model: bjn1.geo VARIABLE scalar per node: scalar bjn1.scl APPENDED_CASEFILES total number of cfiles: 3 cfiles global path: /home/bjn cfiles: bjn2.case bjn3.case bjn4.case
Note: All current limitations for the MULTIPLE_CASEFILES option (which were enumerated above) also apply to the APPENDED_CASEFILES option. The two options cannot be used in combination. It is an either or situation.