		------------------------------------
		SIMSCRIPT II.5 Release 2.0 :  README
		------------------------------------


This file contains notes on SIMSCRIPT II.5 Release 2.0
for Sun/Solaris 2.x

1. C O M P A T I B I L I T Y :

   This SIMSCRIPT II.5 release is fully compatible with 
   the previous release 1.9, but to take advantage of the 
   enhancements in run-time libraries you have to relink 
   your models.

   SIMSCRIPT II.5 contains redesigned SIMGRAPHICS II, 
   new Graphical Editor SIMDRAW and new library features.

   New enhancements maintain backward compatibility.
   All graphical elements (icons, graphs and forms)
   created with the previous Graphical Editor are readable 
   with the new editor and can be used with the new 
   SIMGRAPHICS II libraries.

   Graphical elements created with the new SIMDRAW can not be 
   used with the older version of SIMDRAW and the SIMGRAPHICS II
   libraries.
   
   Please see: sim_examples/_new_sg2 models for ilustration of new 
        SIMGRAPHICS II features.


2. On-line documentation is available on the CD in .PDF format
   readable with ACROBAT reader provided on the same CD.
     - SIMSCRIPT II.5 Programming Manual
     - SIMSCRIPT II.5 Reference Manual
     - SIMGRAPHICS II for SIMSCRIPT II.5 User's Guide
     - SIMGRAPHICS I Case Book
     - UNIX SIMSCRIPT II.5 User's Guide

3. SIMSCRIPT II.5 Release 2.0 requires  License Key from CACI to run.
   Please install your License Key before you start to use 
   the software.
    

4. This SIMSCRIPT II.5 Release 2.0 requires Sun/Solaris 2.4 or higher
   and Sun Workshop compiler C/C++ 4.2.





=====================================================================

NOTE: Atached are notes from Release 1.9 because they contain 
      important information
 
                     	------------------------------------
                     	SIMSCRIPT II.5 Release 1.9 :  README
		     	------------------------------------


This file contains notes on your SIMSCRIPT II.5 release 1.9.
Please read this information carefully.


1. Notes on the SimDebug debugger:
----------------------------------

A few problems turned up for unusual source code.


1.1 Problems with routine names that 'look like' library routines.
------------------------------------------------------------------

Although their use is discouraged, you may use routine names that look like
library routines, i.e. that have a name of the form "name.<letter>" or 
"<letter>.name". This causes problems for the debugger, since SimDebug then
assumes that these are runtime library routines, hence are not debuggable.


Workaround: 

Redefine your routine names in the preamble. E.g. for a routine
"GETHEADER.F" add a line into the preamble

   define GETHEADER.F to mean GETHEADER.FF

Then recompile all of your program. This will consistently rename your
routine/ function names without you having to change the source code of
every routine and call. 



1.2 SIMSCRIPT routines directly implemented in C
------------------------------------------------

In SIMSCRIPT II.5 you can call C routines by defining them in the preamble
as "nonsimscript". When YOU CALL A C ROUTINE that is NOT DEFINED AS NON-
SIMSCRIPT, you will get into trouble with the debugger, since the SimDebug
calls each routine with a certain flag set to get its debugging information.

Fix: Define all C routines you call as "nonsimscript" (you might have to
change the routine name and remove the leading "R" from the name).



1.3 Running SIMSCRIPT II.5 model as in a background mode 
---------------------------------------------------------

If you run your model as a background job you should use a script  as follows:
	
		exec a.out -batchtrace &

In case of a  run-time error, trace back will be written to a file "simerr.trc".
    
If you do not use -batchtrace switch, in case of some run-time errors like 
wrong pointer, debugger may enter endless loop. 







2. Notes on SIMSCRIPT II.5 Run-Time library
-------------------------------------------


2.1 Checkpoint/Restart was reimplemented; 
-----------------------------------------

To record memory you should use:

     Record memory  on unit xx, Restore to label_name

     'label_name'

Run your program as 
	a.out -cr
	
This will create checkpoint file SIMUxx.chk.

To restart from a checkpoint, model has to be restarted from the command line:

	a.out -cr -restore xx

where xx - is a unit number, where checkpoint file SIMUxx.chk was created.


In this relaese Checkpoint/Restart works with non_graphical models only. 


