CCTK RELEASE NOTES, May 15, 2008 Command and Control Toolkit 2.3.3 --------------------------------- Please see the CCTK Installation Manual for software installation instructions. The CCTK Administrator's Manual provides instructions for configuring the software after installation. Release Summary --------------- Version 2.3.3 is a minor release of the CCTK software The following is a summary list of significant changes that have been introduced in the 2.3 releases of the CCTK software: + Moved log file generation location + Significant Map & Graph Performance Optimization for large real-time track population + Support for the Tarsus telemetry device under RHES4 + Major revision to web plug-in + DataProc command-line control of channel timeout parameters + Map display supports user defined logical groups and group visibility control + MonCon graphical client is now an independent package managed separate form CCTK The following list is a summary of the significant bugs fixes and enhancements that are included in the 2.3.3 release. 995: App-libmoncon - Add capability to define and manage logical groups 951: CCTK-CctkClient - Progress bar does not update during project shutdown 992: CCTK-CGIMonCon - Decouple dynamic dependencies to libmoncon.a 994: CCTK-MonCon - Separate MonCon from CCTK package 996: App-Other - Add "cleanup" target to Application's Makefile.am's 998: CCTK-Other - Pull SocketIf from project cctk, relocating to cctutils/libcctsocket 999: CCTK-libars - Relocate function my_timegm from libars & RetParamConvert to cctutils, rename to cct_timegm 1007: App-MonCon - Track icon visibility is not controlled properly from external applications. The following list is a summary of the significant bugs fixes and enhancements that are included in the 2.3.2 release. 256: Move log file generate code from KInit() to ProjectManager. 955: Create IssueCmd API that accepts a timeout value 961: libCctkQtWidgets StopProject Dialog box blocks signals, but never unblocks them 962: Rebaseline RangeClear under CCTK Applications 963: Relocate PeerReceiver to applications/PeerToPeer package 964: Relocate PeerSender to applications/PeerToPeer package 970: Added test tools for CCT-Utils 973: Added the kazlib library to cctutils 974: Add CCT 'demo' user to CVS The following list is a summary of the significant bugs fixes and enhancements that are included in the 2.3.1 release. 945: Map & Graph Performance Optimizations 952: CCTK-PeerSender debug statement gets dumped out prior to check on socket 958: CCTK 2.3 Documentation Update 959: New data packet type to handle binary data generically 966: AGSP Makefile.am in atlas and IRIG161 packages sill reference the old hack libAGSP.o The following list is a summary of the significant bugs fixes and enhancements that are included in the 2.3 release. 850: Port Tarsus Driver to RHEL Server v4 859: Port Tarsus production build and RPM packaging to RHES4 940: Update CGI MonCon for CCTK-2.2, RHES4, GLG 2.9 946: Add DataProc command-line options to control channel timeout parameters Incompatibilities with Previous Releases ---------------------------------------- No known incompatibilities exist. Known Bugs and Limitations -------------------------- Note: Please contact CCT for the latest patch availability status. 35: TAM File XX% Full Reports Continuously. - Description: When the temporary archive media becomes 80% or greater full a message is logged repeatedly once very minute. A more desirable approach would allow the message to be filtered at a user selectable rate - Workaround: No workaround is available. 158: CCTK exception notification. - Description: CCTK provides the ability to asynchronously notify an application program when a limit violation occurs. This capability is not functioning - Workaround: No workaround is available. 227: String Exceptions not handled correctly by configuration database. - Description: There is no string exception element defined within the CCTK XML configuration database. - Workaround: Instead, a byte array exception element must be used for string exception definition in the configuration database. 257: CCTK core dumps when expected resources not present. - Description: If an attempt is made to start CCTK with incorrect tables and/or incorrect channels, Project Manager will core dump, or display non-obvious error messages. - Workaround: Use the default configuration settings provided with CCTK. 259: CCTK fails to process measurements when initial value is set and raw value is zero. - Description: If a measurement is configured in the database to have an initial value, the processed value is set to the specified value, but the raw value is left unchanged at zero. If the first value received for that measurement is raw value zero, then it is possible that the measurement will not be processed correctly. - Workaround: No workaround is available. The likely hood of occurrence is small. 261: Project's system_state.xml file is not validated. - Description: The system_state.xml is not validated before being parsed. The system_state.xml file may become corrupt if an application or the system improperly terminates. The most common situation is when the operating system is shutdown without first terminating a running CCTK project. If there is a format error within the file, it will not be detected and it will "most likely" prevent the project from being started. - Workaround: Remove the system_state.xml file, it will be regenerated the next time the project is started. 280: CctkClient resets selected mode when project_config.pcml changes. - Description: CctkClient monitors the project_config.pcml and, whenever it changes, reloads the file. Whenever the file is loaded, the selected mode is reset back to the default mode. - Workaround: Re-select the correct mode in the start project dialog in CctkClient before restarting the project. 315: File not found messages not relayed to user - error # 127 instead. - Description: When starting a project in CctkClient, if a executable is missing or could not otherwise be found, then error # 127 is reported. - Workaround: No workaround is available. Run ProjectManager from the command line to identify the problem executable. Errata/Additions to the Manuals ------------------------------- none CCT Help Desk ------------- Help Desk Phone Number: (321) 264-1193 (available 8:00 am to 5:00 pm, U.S. Eastern Time, Monday through Friday, excluding holidays). CCT provides free unlimited telephone and e-mail support for 90 days after purchase as part of our standard warranty. Customers who purchase the technical support upgrade option have unlimited telephone or email support for one year after purchase or renewal. For questions or comments about CCTK or other CCT products or services please call (321) 264-1193 and ask to speak to a customer representative. For e-mail information, contact support@cctcorp.com or visit our website at: http://www.cctcorp.com. It is important when calling for help with a problem to preserve the project environment as much as possible to allow CCT engineers to efficiently diagnose the problem. If at all possible, leave the project and operation in its current state at the time of the problem and call the Help Desk. If it is not possible to stop and troubleshoot during an operation, please perform the following steps: 1. Completely document all of the symptoms of the problem and as much of the state and configuration of the project as possible. 2. Copy the KPATH directory to a location outside of the project environment (e.g., /tmp/projectname/date/). 3. Note the time and date of the problem. Additional help may be found at the CCT Technical Support web site http://www.cctcorp.com/support. This CCTK_RELEASE_NOTES text file is found in the root directory of the CCTK CD. All CCTK manuals are also provided in the root directory of the CCTK CD in Acrobat(c) PDF format. ------------------------------------------------------------------------------ Command and Control Toolkit, T-Zero, and RangeNet are trademarks of Command and Control Technologies Corporation. Copyright (c) 2008 Command and Control Technologies Corp. All rights reserved.