Caché Upgrade Checklists - InterSystems Documentation

More documents

Recommendations

Info

Caché 2009.1 Upgrade ChecklistUTF-8 is fully compatible with ASCII. This means that locales with languages that use ASCII exclusively (such as English)will not notice any change. Customers with other Latin1-based locales which use characters between 128 and 255 mightneed to change the encoding used by their telnet client programs to UTF-8 so that they can correctly handle accented letters.6.2.18.2 Terminal Log Files From Unicode Systems Now In UnicodeBeginning with version 2009.1, the log files produced by the Caché TERMINAL will be encoded as ANSI for 8–bitinstallations, and as Unicode for Unicode installations.6.2.18.3 $LISTSAME On Big-Endian SystemsOn prior versions, the $LISTSAME() function could report that two lists were not equal when one list contained an integerand the corresponding position in the other list was a different representation of that same integer (such as string or floatingpoint). The failure occurred only on big-endian platforms.6.2.18.4 MQ Context ChangedPrior versions of Caché unconditionally set the Context to 2 (SET_ALL_CONTEXT). This behavior caused authorizationerrors when using MQ.Now, a flag is defined for an MQ Put connection (Net.MQSend) called Context. The context flag is:• 0: Default.• 1: Identity. The application should use the Identity context to set and pass the ApplIdentityData field.• 2: All context. The Context allows the ApplIdentifyData and the PutApplType fields to be set and passed.Setting the context to Identity (1) or All (2) may have authorization implications. Applications that succeeded before maynow fail with an MQ Authorization error (2035). Please see your IBM Websphere MQ documentation for additional details.6.2.18.5 OpenVMS Stream Record Size IncreasedCaché now allows applications running on OpenVMS to create records on OpenVMS in Stream mode up to 32767 bytesin length (the maximum allowed by OpenVMS RMS sequential files). This length includes the CR/LF that ends the record.Prior versions of Caché would handle requests to write records longer 163853 by silently splitting them into 2 (or more)records in the sequential file. This change will also report a error if the 32767 limit is exceeded; applicationswill get a clear indicator that they have exceeded the maximum record size, rather than unknowingly creating multiplerecords.6.2.18.6 Comparisons On 64–Bit Systems CorrectedCaché version 2008.2 introduced a discrepancy in floating-point comparisons between nearly equal values that is correctedin this version. The problem occurred in comparisons between a $DOUBLE value and a Cache decimal value where the20 digit expansion of the $DOUBLE value (rounded to be a decimal value) was equal to the Cache decimal value. In thiscase, comparing the $DOUBLE value with the Cache decimal value resulted in all three of the relations less than, equalto, and greater than being false. Now, these comparisons always have at least one of the relationships as true.6.2.18.7 Windows Interfaces Now Built With Visual Studio 2008Version 2009.1 now builds its Windows components using Microsoft Visual Studio 2008. Applications using C, C++,CallIn, or CallOut should also be built using that version of Visual Studio. The Windows samples in the SAMPLESnamespace were also built with that version.164 Caché Upgrade Checklists
Operators6.2.18.8 Windows Installation Now Uses Lowercase Directory NamesCaché now uses lowercase for installation directory names. In previous versions, for example, it installed into the \Bindirectory. In version 2009.1, it is \bin.6.3 Operators6.3.1 System Management PortalThere have been a number of changes and improvements to the system management portal since 2007.1 was released.These are detailed in the administrator section.Caché Upgrade Checklists 165
Page 1 and 2:
Caché Upgrade ChecklistsVersion 20
Page 3 and 4:
Table of ContentsAbout This Book ..
Page 5 and 6:
5.2.15 MultiValue Changes .........
Page 7 and 8:
10 Caché 5.2 Upgrade Checklist ...
Page 9:
List of TablesTable 5-1: Non-Proces
Page 13 and 14:
1General Upgrade InformationBackgro
Page 15:
Upgrading CachéThe application ser
Page 18 and 19:
Caché 2012.1 Upgrade ChecklistUpon
Page 20 and 21:
Caché 2012.1 Upgrade Checklist2.1.
Page 22 and 23:
Caché 2012.1 Upgrade ChecklistNote
Page 24 and 25:
Page 26 and 27:
Caché 2012.1 Upgrade Checklist•
Page 28 and 29:
Caché 2012.1 Upgrade ChecklistClas
Page 30 and 31:
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Caché 2012.1 Upgrade Checklist= 1,
Page 40 and 41:
Caché 2012.1 Upgrade Checklistself
Page 42 and 43:
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Caché 2011.1 Upgrade Checklist2. R
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Page 62:
Page 65 and 66:
Developerscan be compiled at the sa
Page 67 and 68:
Developers3.2.6 Studio Changes3.2.6
Page 69 and 70:
Developers3.2.7.6 Changes to Java M
Page 71 and 72:
Developers3.2.8.8 SQL Statement Pro
Page 73 and 74:
DevelopersClassMethod SquareIt(valu
Page 75 and 76:
Developers3.2.9.5 Session Events An
Page 77 and 78:
Developers3.2.13.2 Changes To Catal
Page 79 and 80:
Developers3.2.14.7 jBase CHAIN Hand
Page 81 and 82:
Developers2. zenLaunchPopupWindow s
Page 83:
Developers3.2.17 %Installer Changes
Page 86 and 87:
Caché 2010.2 Upgrade ChecklistNote
Page 88 and 89:
Caché 2010.2 Upgrade ChecklistThe
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Caché 2010.2 Upgrade Checklist2. I
Page 100 and 101:
Page 102 and 103:
Page 105 and 106:
5Caché 2010.1 Upgrade ChecklistPur
Page 107 and 108:
AdministratorsGMHEAP Defaults Incre
Page 109 and 110:
Developers5.2.1 General Operational
Page 111 and 112:
Developers5.2.2.3 Remove $ZUTIL Fun
Page 113 and 114:
DevelopersCodeDescriptionClassPrope
Page 115 and 116:
DevelopersTable 5-2: Process- & Sys
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Developers5.2.5.2 Class DeletionsTh
Page 123 and 124: DevelopersClass%Installer.Namespace
Page 125 and 126: DevelopersClass%MV.SelectList%Resul
Page 127 and 128: DevelopersClass Name%CPT.CalloutDum
Page 129 and 130: DevelopersClass NameConfig.ECPConfi
Page 131 and 132: Developers5.2.6.2 Superclass Availa
Page 133 and 134: Developers5.2.6.11 Change In Suppor
Page 135 and 136: Developers5.2.8.4 Reserved Word Che
Page 137 and 138: Developers• ModulesPrior to this
Page 139 and 140: 6Caché 2009.1 Upgrade ChecklistPur
Page 141 and 142: AdministratorsPrior Version Mapping
Page 143 and 144: Administrators^CacheAuditD(, ) = $l
Page 145 and 146: Developers6.1.6.5 Weblink No Longer
Page 147 and 148: DevelopersPotential confusion arise
Page 149 and 150: Developers6.2.5.4 XML DOM Internal
Page 151 and 152: Developers• %Monitor.System.Dashb
Page 153 and 154: Developers• %Exception.AbstractEx
Page 155 and 156: DevelopersArgument list: AddGlobalM
Page 157 and 158: Developers6.2.6.11 EXTENT Queries P
Page 159 and 160: Developers6.2.8.3 Support INSERT ..
Page 161 and 162: Developers• ()in ODBC mode and/o
Page 163 and 164: Developers6.2.10 CSP Changes6.2.10.
Page 165 and 166: DevelopersThis means that applicati
Page 167 and 168: Developersmax(scale1, scale2)Multip
Page 169 and 170: DevelopersMetaData Table NameSQLGet
Page 171 and 172: Developers6.2.15.10 Match Select Li
Page 173: Developers3. As a collection of giv
Page 178 and 179: Caché 2008.2 Upgrade ChecklistIn t
Page 180 and 181: Caché 2008.2 Upgrade Checklist7.1.
Page 182 and 183: Caché 2008.2 Upgrade ChecklistWhen
Page 184 and 185: Caché 2008.2 Upgrade ChecklistWhen
Page 188 and 189: Caché 2008.2 Upgrade ChecklistAll
Page 194 and 195: Caché 2008.2 Upgrade ChecklistSee
Page 196 and 197: Caché 2008.2 Upgrade Checklistmean
Page 200 and 201: Caché 2008.2 Upgrade Checklistrepo
Page 211 and 212: AdministratorsBeginning with this v
Page 213 and 214: Developersis now interpreted as:Col
Page 215 and 216: Developers8.3.7 Class Changes8.3.7.
Page 217 and 218: DevelopersIn addition, the internal
Page 221 and 222: Administrators9.1.7 System API Chan
Page 223 and 224: AdministratorsC:\users\someuser\App
Page 225 and 226:
Developers9.2.1 System Management P
Page 227 and 228:
Developers9.2.3.8 Statement Changes
Page 229 and 230:
10Caché 5.2 Upgrade ChecklistPurpo
Page 231 and 232:
Developers• Windows - 32-bit only
Page 233:
Operators10.3.2.3 SQL LEFT JOIN Cha
Page 236 and 237:
Caché 5.1 Upgrade Checklist11.1.1
Page 238 and 239:
Caché 5.1 Upgrade ChecklistService
Page 240 and 241:
Caché 5.1 Upgrade ChecklistWebServ
Page 242 and 243:
Caché 5.1 Upgrade Checklist• The
Page 244 and 245:
Caché 5.1 Upgrade Checklist• Fas
Page 246 and 247:
Caché 5.1 Upgrade ChecklistLocaler
Page 248 and 249:
Caché 5.1 Upgrade ChecklistService
Page 250 and 251:
Page 252 and 253:
Page 254 and 255:
Caché 5.1 Upgrade Checklist\caches
Page 256 and 257:
Page 258 and 259:
Caché 5.1 Upgrade Checklist2. They
Page 260 and 261:
Caché 5.1 Upgrade Checklist• UPD
Page 262 and 263:
Page 264 and 265:
Caché 5.1 Upgrade ChecklistIn Cach
Page 266 and 267:
Caché 5.1 Upgrade Checklist• In
Page 268 and 269:
Caché 5.1 Upgrade Checklist/// - s
Page 270 and 271:
Caché 5.1 Upgrade ChecklistCached
Page 272 and 273:
Caché 5.1 Upgrade Checklist11.2.8.
Page 274 and 275:
Caché 5.1 Upgrade Checklistwill ha
Page 276 and 277:
Caché 5.1 Upgrade Checklist2. the
Page 278 and 279:
Caché 5.1 Upgrade ChecklistFunctio
Page 280 and 281:
Caché 5.1 Upgrade Checklistthan th
Page 282 and 283:
Page 285:
IndexSymbols error, 99 errors, 99SS
show all

Caché Upgrade Checklists - InterSystems Documentation

Create successful ePaper yourself

Delete template?

Save as template?