------------------------------------------------------------
Pro/MECHANICA STRUCTURE Version 23.3(313)
Diagnostic Log
Wed Jan 22, 2003   21:36:18
------------------------------------------------------------

Begin Engine Bookkeeping
Wed Jan 22, 2003   21:36:18

Begin Analysis: "A220103_01"
Wed Jan 22, 2003   21:36:33

Using Sparse Solver

Begin Mass Calculation
Wed Jan 22, 2003   21:36:43

Begin P-Loop Pass 1
Wed Jan 22, 2003   21:36:52

Begin Processing Multi-Point Constraints
Wed Jan 22, 2003   21:36:55

Begin Matrix Profile Minimization
Wed Jan 22, 2003   21:36:55

Begin Element Calculations, Pass 1
Wed Jan 22, 2003   21:36:55

Begin Global Matrix Assembly, Pass 1
Wed Jan 22, 2003   21:37:00

Begin Equation Solve, Pass 1
Wed Jan 22, 2003   21:37:00

Number of equations: 14902
Average bandwidth:   86.8585
Maximum bandwidth:   481
Size of global matrix profile (mb): 10.3549
Number of terms in global matrix profile: 1294365     
Minimum recommended solram for direct solver: 2

Size of element file (mb): 10.7365
Maximum element matrix size (bytes): 624
Average element matrix size (bytes): 624

NOTES:
Solver RAM allocation can be done with a single parameter,
called solram.  If the Pro/MECHANICA STRUCTURE/THERMAL
engine is the only memory-intensive application running on
your computer, performance will usually be best if you set
solram equal to half of your machine RAM.  For example,
solram 60 is a good choice for a machine with 128 MB of RAM.

If you are running other memory-intensive applications on
your computer, decrease the solram allocation accordingly.
For example, set solram to 0.25 times machine RAM if you are
running two large applications at once.  However, you often
can run two large jobs faster one after another than if you
try to run both jobs at once.

The purpose of solram is to reduce the amount of disk I/O.
If you set solram too high, performance will usually suffer,
even on machines with very large RAM, because there will not
be enough machine RAM for other important data.  For
example, Pro/MECHANICA allocates many large, non-solver
memory areas that will cause excessive swapping unless you
leave enough spare machine RAM.  You must also leave enough
RAM for the operating system to do disk caching.  Disk
caching improves filesystem performance by holding file data
in RAM for faster access.  Setting solram to half machine
RAM is usually the best compromise between reducing the
amount of disk I/O, and leaving enough machine RAM for disk
caching and for other data.

If you set solram too low, performance will suffer because
Pro/MECHANICA must transfer data between machine RAM and
disk files many more times than with a larger setting.
For example, performance may degrade significantly if you
set solram to 0.1 times machine RAM or less.  A preferable
minimum is 0.25 times machine RAM.

The available swap space on your machine must be greater
than the maximum memory usage of your job.  The available
disk space on your machine must be greater than the maximum
disk usage of your job.  You can monitor the resource usage
of your job in the log (stt) file.  Your job may fail if
your machine does not have enough available disk space or
swap space, or if the maximum memory usage of your job is
greater than the memory limits set for your operating
system.

Begin Load Calculations
Wed Jan 22, 2003   21:37:02

Begin Post-Processing Calculations, Pass 1
Wed Jan 22, 2003   21:37:02
*** A fatal error has occurred. ***

The engine is unable to open the file  å.
Please check the directory/file permissions.