The following release notes are available in the \Docs subdirectory of your installation:

• Late-breaking information about this kit: \relnotes\readme.1st
• Release notes for this kit: \relnotes\cache\relnotes.htm (this document)
• Release notes from prior kits: \relnotes\cache\prenotes.htm

This document provides a list of the changes between Caché 2007.1.1 and Caché 2007.1.2.

Topics include:

• General Announcements
• InterSystems News, Alerts, and Advisories
• Online Documentation
• Description of a Change Report
• Change Reports for This Maintenance Kit

Since this maintenance kit is based on Caché 2007.1.1, anyone upgrading from a Caché release at or before 5.0 will need a new license key.

From time to time, InterSystems publishes items of immediate importance to users of our software. These include alerts, mission critical issues, important updates, fixes, and release announcements.

The most current list can be obtained from the InterSystems Website.

Users should check this list periodically to obtain the latest information on issues that may have an effect on the operation of their site.

As a convenience to our users, InterSystems provides online access to documentation for recent product versions at the InterSystems Website. From the home page choose Support and Education, then Caché Support and on then Caché Documentation. Then select the specific version and type of documentation you are interested in.

To help you assess the impact of this maintenance kit on your applications, the remaining topics in this document describe each modification in detail. The format for this description is a Change Report.

Each Change Report provides a table with the following information:

• Likelihood: The probability that a user on the affected platform will encounter this issue.
• Risk: An assessment of how likely this change is to introduce additional issues into the application environment.
• Ad Hoc: Whether this change has previously been deployed in an ad hoc release and successfully used by customers in production.
• Enhancement: Whether this change provides new features or capabilities for the product.

When you login CSP will normally automatically redirect you have to the original page so you do not see the login username/password in the URL and you can refresh this page without getting a 'To refresh the browser will resubmit your data to this page' dialog.

Due to how this redirect was done if you created an encoded page and then brought it up in the browser you were presented with the login page. If on this login page you enter a parameter value %quot;MONEY=9999999", for example, and then login, this parameter value was being automatically encoded so it appeared this value came from the server when it was really entered by the user.

This could be a fairly serious security issue for any CSP application that relies on encoded parameter values. This problem was first introduced in 2007.1.

Now we make sure we do not encode these user values on the server which avoids this problem.

The application server checks and converts the requests to the server's endian. Previously, requests with Unicode strings were NOT converted to the server's endian. This caused serious problems when the application server and the database server were of differing endianness.

This change fixes a problem in the Light C++ Binding. When storing C++ double values in %Float or %Currency properties, Caché performed bad conversions for certain numeric values. This resulted in wrong values (usually zero or near-zero values) being stored in the database.

The problem occurred for approximately 0.3% of possible numeric values. Any given value would either always be converted correctly, or always incorrectly.

A problem on Unix and OpenVMS which prevented the job command from succeeding when a process slot had been used too many times has been resolved. This was introduced in 2007.1 and is now fixed.

On AIX platforms, if a Cache instance is owned by someone other than root but startup is done by root, inter-process signals may not be received. This affects commands like JOBEXAM or RESJOB.

The "ccontrol force instance_name" did not work on Windows Vista unless the user was running as administrator. This change corrects this by using the service to force down the Caché instance before forcing the instance manually.

Note: It is best to be logged in and running administrator when running "ccontrol force" on Windows Vista. You can do this by right clicking on "Command Prompt" in the Windows start menu and selecting "run as administrator".