Caché Upgrade Checklists - InterSystems Documentation

DevelopersTROL); the translation would be performed on both textual data which did require the translation and binary data that didnot. This change also fixes an anomoly earlier versions that might result in fewer form feeds being output at the start of ajob.4.2.12.7 Use Default Precision Of 4 For SQL FormattingUsers of the MV formatting operations in SQL introduced in 2010.1 ($MVFMT, $MVOCONV, and others) will find thatthe MultiValue precision now defaults to 4, the same as it does from the MV Shell, rather than zero. In prior versions, thevalue was not initialized until an MV command was issued.4.2.12.8 Logical Operators Now Emulation DependentThe MVBasic logical operators “AND” and “OR” will now behave properly according to the emulation under whichthey are compiled. Emulations such as Universe and jBase will stop evaluating arguments as soon as a result for theexpression is known.A new $OPTIONS is provided to control this behavior if the emulation default is not desired:• $OPTIONS FULL.LOGICAL.EVALUATION means that all the operands will always be evaluated.• $OPTIONS -FULL.LOGICAL.EVALUATION means that if the result is known after evaluating the first operand,other operands will not be evaluated.4.2.12.9 VAR.SELECT Now Default For Ultimate$OPTIONS VAR.SELECT is now the default for the Ultimate emulation.4.2.12.10 Comparison Of Non-Numeric Strings FixedNon-numeric strings in the arguments for the comparison functions EQS, NES, GTS, GES, LTS, and LES will now beconverted properly according to the emulation under which the program is compiled. This was not the case in prior versions.4.2.12.11 Positioning Of READPREV CorrectedIn prior versions, the first READPREV after a SELECT ATKEY to a key that does not exist would skip one record. Now,the record position is properly managed and the record is not skipped.4.2.12.12 Suppress Newline At End Of Print JobNormally, when printing in MultiValue, at the end of printing a line of data a newline sequence will be printed. This isnormally CR + LF (but can be amended with SP-CONTROL). There are now 3 scenarios when we do NOT print thisnewline sequence at the end of a line of data:1. When outputting binary data on a line, as specified with the CHAR(255):"BINARY": sequence.2. When a line of data is immediately followed by a form-feed on the next line. In this case the new line sequence is notonly superfluous,but might also create an unintended blank page.3. At the end of a print job. Again, this might create a blank page if the page was full when the newline is printed. It isup to the form feed specification using the SP-SKIP setting to decide trailing form feeds.There is a small chance that print job might have been relying on the previous behavior to throw a page at the end of a printjob. If this is the case, then the form queue setting needs to be amended with SP-SKIP to carefully define the end-of-jobform feeds.Caché Upgrade Checklists 91