Caché Upgrade Checklists - InterSystems Documentation

DevelopersWrite "Error line: ", $PIECE($ZERROR, ">", 2)and should be changed to be something likeWrite "Error line: ", $PIECE($PIECE($ZERROR, ">", 2), " ", 1)The following table gives a list of errors that include additional info and the format of that information. The new info isseparated from the previous text by a space.Error CodeDescriptionthe name of the variable (including any subscripts used)the subscript reference in errorthe referenced class namethe name of the referenced property and the class name it is supposed to bein, separated by a commathe name of the method invoked and the class name assumed to contain it,separated by a commathe name of the global referenced and the name of the directory containing it,separated by a commathe name of the routine being invokedThe names of variables local to routines (or methods) as well as the names of class properties and methods are indicatedwith an asterisk preceding the name. Global variable names are prefixed with a caret as expected.Examples: *x *abc(2) ^xyz(2,"abc") *SomeProp,Package.Classname *AMethod,SamePackage.DifferentClass ^%GlobalVar,c:\cx\mgr\notyours\11.2.10.6 $ZUTILPermission ChangesThe authority needed to execute certain $ZUTIL functions is more specific in version 5.1 than prior releases. Unless otherwisenoted in the following table, published $ZUTIL options require no special permission.FunctionNumber5Requirement%DB_:RExplanationSubject: change to another namespaceIn version 5.1, changing to a different namespace requires thatthe user have %DB_XXX:Read where XXX is the name of thedatabase that contains the globals for the namespace.Caché Upgrade Checklists 267