Caché Upgrade Checklists - InterSystems Documentation

Caché 2012.1 Upgrade Checklist2.1.4.3 OpenVMSUpdate Xerces And Xalan For OpenVMSIn this release, the XERCES and XALAN utilities have been upgraded to versions 3.1.1 and 1.11 respectively.2.1.4.4 Non-OpenVMS SystemsLarge Journal WritesIn this version, the maximum size of a journal write has been increased to 4MB. Measurements indicate this speeds upjournaling by a factor of 2 for a streams load on non-SAN disks producing 1.5GB of journal.2.2 DevelopersThis section contains information of interest to those who have designed, developed and maintained applications runningon prior versions of Caché.The items listed here are brief descriptions. In most cases, more complete descriptions are available elsewhere in the documentation.2.2.1 Naming Conventions For GlobalsBegining with version 2012.1, InterSystems reserves for itself global names that meet the following criteria:• In user databases, all names starting with “^ISC.”.• In CACHETEMP, all names beginning with “^CACHETEMP.ISC.”.• For process-private globals, all name starting with “^||ISC.”.2.2.2 Routine Compiler Changes2.2.2.1 Check For Too Many Arguments In A Multiple SETA SET command that sets multiple variables to the same value could overflow the argument stack and cause unpredictableerrors. The compiler will now correctly count the number of argument stack entries that the command will use and give acompile error if there are more than 255.2.2.3 Routine Changes2.2.3.1 Error Stack Now Initialized For Each ErrorPrior to this release, the error stack information persisted until $ECODE was set to the null string. This means that it couldcontain levels for an older error that happened at a deeper stack level, mixed with levels of a newer error that happened ata less deep level. This made it difficult to interpret the stack display for the newer error.Beginning with 2012.1, any existing error stack information will be cleared when a new error happens, and the new errorstack will contain only entries that show the state at the time of the current error.This change should make error analysis code simpler and avoid confusion that could happen with the previous arrangement.Existing code should not have to change unless it has special provisions to try to compensate for the previous behavior.14 Caché Upgrade Checklists