Caché Upgrade Checklists - InterSystems Documentation

Caché 5.1 Upgrade ChecklistService%Service_ComPort%Service_Console%Service_LAT%Service_Telnet%Service_TerminalPrivilegeUseUseUseUseUseConditionOn Windows, if service is enabledOn Windows, if service is enabledOn Windows, if service is enabledOn Windows, if service is enabledOn UNIX® and OpenVMSAfter the administrator has configured the system appropriately, the UnknownUser user can either be disabled or theresources assigned to the role%LegacyUnknownUser can be gradually reduced via ^SECURITY or the System ManagementPortal as additional aspects of the application environment are brought under the control of Caché Advanced Security. Thisreduction of the privileges of the %LegacyUnknownUser role or its removal is a manual step in the transition. It is notdone automatically by Caché.11.1.20.5 %LegacyCD and %LegacySQLThese are applied automatically to existing users only during upgrades to ensure that those users continue to have the samelevel of access in 5.1 that they did previously. New users aren't required to have these roles specifically.11.1.20.6 Allow %-Global Access as in Previous VersionsThe value of Security.System.PercentGlobalWrite is set true for upgrades. (For new installations it is set false.) This makesaccess to %-globals consistent with earlier versions. The value can be changed via the ^SECURITY routine.11.1.20.7 All Members of a Cluster Must Run the Same Caché VersionAll members of an ECP cluster must be running the same version of Caché. If you upgrade one, you must upgrade all therest.11.1.20.8 Removal of CSP Gateway On OpenVMS UpgradeThe CSPGateway is no longer supported on OpenVMS. The material referencing it has been removed from the OpenVMSinstallation script and the code is no longer part of the product for OpenVMS.Note:Any existing CSP Gateway files will be removed during a upgrade from a previous version.11.1.20.9 Removal of Global & Package MappingsDuring an upgrade from an earlier version, the following mappings to globals will be removed:• all globals whose names begin with “^odd”• ^rINDEXCLASS, ^rOBJ, ^ROUTINE• ^mddPackages whose names start with “%Z”, “%z”, “Z” and “z” will have their definitions retained (“^oddDEF”), but willhave their compiled class information removed. The “^odd” globals will be recreated when the classes are recompiled via$SYSTEM.OBJ.Upgrade().In addition, ALL class mappings that were defined in the configuration file (.cpf) will be discarded.238 Caché Upgrade Checklists