From: B.Gilli
                                                           Date: 25 Sep 1998


             VLT-SW-OCT98 - RELEASE NOTES FOR CCS lite
             =========================================

Environments:
------------
Conventions identical to standard ccs:
	- CCS_Lite environment names starting with "w" since WS envs.
	- CCS_Lite environments declared in /etc/services
	- CCS_Lite environments to be known by Rtap should be declared
	  in RtapEnvList.
	- All environments to be known by CCS_Lite environments should
	  be listed in a CcsEnvList file located in $VLTDATA/config.
	  Format identical to RtapEnvList.
	- rtap user must exist on the WS.(needed by msg &scan)
	
CCS_Lite environments use CcsEnvTable, identical to RtapEnvTable:
	- same location: $VLTDATA/ENVIRONMENTS/<envname>/CcsEnvTable.
	- Supported features:
		. Autostart
		. Start order including splitting in phase.
		. Predefined or automatically assigned Id.
		. Obituary & clean up handling.
		. Command line arguments.
	 - Unsupported features:
		. real time priorities.
		. Process auto restart/env shutdown on termination.
		. Shutdown sequence. Only fixed sequence, reversed from startup.
		. No rtap user

Startup:
ccsScheduler [-e <envname>]
If no -e option, the environment defined by the variable RTAPENV is started.

Shutdown:
ccsShutdown -e <envname> [-s]   ******Note: <envname> is mandatory*****
Optional -s to force a snapshot BEFORE stopping any process.

This command is the only one providing full cleanup capabilities. 
in particular the kill -9 <ccsScheduler_pid> shall never be used since it
will leave orphan resources.

In case an environment has been accidentally stopped, leaving orphan resources,
a clean up is necessary to allow proper restart of any environment.
1) remaining processes should be killed, including qsemu.
2) If necessary, use the option -9 to kill processes.
3) Check with command "ipcs" if there is any resource still allocated.
4) if so, use the "ipcrm" to release them. 





Limitations:
Although CCS_Lite can coexist with other CCS & CCS_Lite environments,
for one user on a given WS, only one environment type:
full CCS or(exclusive) CCS_Lite. 



Rtap equivalent processes:
**************************

RtapScheduler		<->	ccsScheduler
RtapShutdown		<->	ccsShutdown
RtapQServer		<->	qsemu (pid 3 mandatory)
RtapDbStartup		<->	dbStartup
RtapPerfMon		<->	ccsPerfMon
RtapForceSnap		<->	dbForceSnap, option -w supported.
...

Application Programmatic Interface:
***********************************

NO DIFFERENCE with standard CCS for supported functionality. See below.


Capabilities:
*************

log		Full support.
err		Full support, Rtap error stack emulated with single level.
msg/cmd		All capabilities supported, communications with CCS,
		CCS_Lite, LCU.
db		Full support for access to local database,
		remote access to LCU databases.
		Access to remote CCS_Lite databases at a later stage.
		No access to remote Rtap databases.
		NO CALCULATION ENGINE.
		Quality always OK.
		NO SECURITY (R/W, categories, groups protection.)
evt		Full support for local & remote envs, with the exception of
		configuring (and thus getting) events generated into a
		CCS_Lite database to be sent to an Rtap env.
tims		Full support for local env.
scan		Only one way: CCS_Lite env can be scanned by full CCS env.
alrm		NO SUPPORT.

Data historian, sampling, plotting: NOT SUPPORTED.

eccs		full support.
evh		full support.

Obituary handling: supported, registration only for ALL or NONE.


CAUTIONS:
*********
Code running under CCS_Lite will be more sensitive towards invalid memory
accesses, due e.g. to uninitialized or NULL pointers. Rtap was providing some
protection against this type of errors. 
What frequently happens is a core dump in an strcmp call or similar functions.
In that case, check validity of arguments. 
The same might happen in error handling if there is any missing arguments with 
respect to the error format. Use the errch tool to verify your code.   

                                ___oOo___