Using Caché ObjectScript - InterSystems Documentation

More documents

Recommendations

Info

Command-line Routine Debugging Argument "L" "L+" "S" "S+" "T" "N" Description Same as "B", except GOTO initiates single-step execution, stopping at the beginning of each line. When a DO command, user-defined function, or XECUTE command is encountered, single-step mode is suspended until that command or function completes. Same as "B", except GOTO initiates single-step execution, stopping at the beginning of each line. DO commands, user-defined functions, and XECUTE commands do not suspend single-step mode. Same as "B", except GOTO initiates single-step execution, stopping at the beginning of each command. When a DO command, user-defined function, FOR command, or XECUTE command is encountered, single-step mode is suspended until that command or function completes. Same as "B", except GOTO initiates single-step execution, stopping at the beginning of each command. DO commands, user-defined functions, FOR commands, and XECUTE commands do not suspend single-step mode. Can be used together with any other argument. Outputs a trace message to the trace device. This argument works only after you have set tracing to be ON with the ZBREAK /TRACE:ON command, described later. The trace device is the principal device unless you define it differently in the ZBREAK /TRACE command. If you use this argument with a breakpoint, you see the following message: TRACE: ZBREAK at tag2^rou2. If you use this argument with a watchpoint, you see a trace message that names the variable being watched and the command being acted upon. In the example below, the variable a was being watched. It changed at the line test+1 in the routine test. TRACE: ZBREAK SET a=2 at test+1^test. If you include the "T" action, you must also explicitly include the "B" action as in ZBREAK *a:"TB", to have an actual break occur. Take no action at this breakpoint/watchpoint.The condition expression is always evaluated and determines if the execute_code is executed. 14.1.2.6 ZBREAK Examples The following example establishes a watchpoint that suspends execution whenever the local variable a is killed. No action is specified, so "B" is assumed. ZBREAK *a::"'$DATA(a)" The following example illustrates the above watchpoint acting on a direct mode Caché command (rather than on a command issued from within a routine). The caret (^) points to the command that caused execution to be suspended: %SYS>KILL a KILL a ^ %SYS 1s0> The following example establishes a breakpoint that suspends execution and sets single-step mode at the beginning of the line tag^rou. ZBREAK tag^rou:"L" The following example shows how the break would appear when the routine is run. The caret (^) indicates where execution was suspended. 150 Using Caché ObjectScript
Debugging with the Caché Debugger %SYS>DO ^rou tag SET x=1 ^ tag^rou %SYS 2d0> In the following example, a breakpoint at line tag^rou does not suspend execution, because of the "N" action. However, if xDO ^test FOR i=1:1:6 SET a=a+1 ^ test+3^test %SYS 3f0>WRITE a 5 14.1.3 Disabling Breakpoints and Watchpoints You can disable either: • Specific breakpoints and watchpoints • All breakpoints or watchpoints 14.1.3.1 Disabling Specific Breakpoints and Watchpoints You can disable a breakpoint or watchpoint by preceding the location with a minus sign. The following command disables a breakpoint previously specified for location tag^rou: ZBREAK -tag^rou A disabled breakpoint is “turned off”, but Caché remembers its definition. You can enable the disabled breakpoint by preceding the location with a plus sign. The following command enables the previously disabled breakpoint: ZBREAK +tag^rou 14.1.3.2 Disabling All Breakpoints and Watchpoints You can disable all breakpoints or watchpoints by using the plus or minus signs without a location: ZBREAK - ZBREAK + Disable all defined breakpoints and watchpoints. Enable all defined breakpoints and watchpoint. Using Caché ObjectScript 151
Page 1 and 2:
Using Caché ObjectScript Version 2
Page 3 and 4:
Table of Contents About This Book .
Page 5 and 6:
5.7.3 Specifying a Combination Patt
Page 7 and 8:
10.2 Manipulating Multidimensional
Page 9 and 10:
15.6.2 Database Conversion ........
Page 11:
List of Tables Table 3-1: Date Form
Page 15 and 16:
1 Introducing Caché ObjectScript C
Page 17 and 18:
Invoking Commands and Functions 1.3
Page 19 and 20:
2 Syntax Rules This chapter describ
Page 21 and 22:
Comments • White space must appea
Page 23 and 24:
Literals 2.5 Literals A literal is
Page 25 and 26:
Labels These prefix characters iden
Page 27 and 28:
3 Data Types and Values Caché Obje
Page 29 and 30:
Numbers 3.2.1 Fundamentals of Numbe
Page 31 and 32:
Objects You can use the $DOUBLE fun
Page 33:
Dates 3.7 Dates Caché ObjectScript
Page 36 and 37:
Variables reserved for system use a
Page 38 and 39:
Variables 4.1.2.2 Listing Process-p
Page 40 and 41:
Variables Other examples of special
Page 42 and 43:
Variables 4.3 Variable Declaration
Page 44 and 45:
Operators and Expressions ObjectScr
Page 46 and 47:
Operators and Expressions For those
Page 48 and 49:
Operators and Expressions Set pies
Page 50 and 51:
Operators and Expressions Set x = 4
Page 52 and 53:
Operators and Expressions The follo
Page 54 and 55:
Operators and Expressions • The &
Page 56 and 57:
Operators and Expressions The || Bi
Page 58 and 59:
Operators and Expressions • Combi
Page 60 and 61:
Operators and Expressions 5.6.2.1 D
Page 62 and 63:
Operators and Expressions operandpa
Page 64 and 65:
Operators and Expressions The Patte
Page 66 and 67:
Operators and Expressions Set match
Page 68 and 69:
Operators and Expressions indir ; g
Page 70 and 71:
Operators and Expressions Start Set
Page 73 and 74:
6 Commands The command is the basic
Page 75 and 76:
Command Postconditional Expressions
Page 77 and 78:
Invoking Code 6.3 Invoking Code Thi
Page 79 and 80:
Flow Control Commands Set (per1.Gen
Page 81 and 82:
Flow Control Commands All values ca
Page 83 and 84:
I/O Commands With one or more varia
Page 85 and 86:
7 Functions Functions are pieces of
Page 87 and 88:
8 User-defined Code Caché comes wi
Page 89 and 90:
Procedures, Routines, Subroutines,
Page 91 and 92:
Procedures in Detail 8.2.1.2 Using
Page 93 and 94:
Procedures in Detail SAMPLES>Write
Page 95 and 96:
Procedures in Detail If there are m
Page 97 and 98:
Procedures in Detail • Any tags i
Page 99 and 100:
Legacy User-Defined Code label para
Page 101 and 102:
Legacy User-Defined Code User-defin
Page 103:
Legacy User-Defined Code The Do com
Page 106 and 107:
ObjectScript Macros and the Macro P
Page 108 and 109:
Page 110 and 111:
Page 112 and 113: ObjectScript Macros and the Macro P
Page 127 and 128: 10 Multidimensional Arrays Caché i
Page 129 and 130: 11 String Operations ObjectScript p
Page 131 and 132: Delimited Strings This code sets x
Page 133: Lists Versus $Piece and Strings •
Page 136 and 137: Transaction Processing 12.1.1 Trans
Page 138 and 139: Transaction Processing 12.1.3.1 Iss
Page 140 and 141: Transaction Processing 12.3 System-
Page 143 and 144: 13 Error Processing Managing the be
Page 145 and 146: The TRY-CATCH Mechanism • A THROW
Page 147 and 148: Traditional Error Processing • An
Page 149 and 150: Traditional Error Processing If a s
Page 151 and 152: Traditional Error Processing • Ha
Page 153 and 154: Traditional Error Processing to an
Page 155 and 156: Traditional Error Processing Passin
Page 157 and 158: Traditional Error Processing 1. Cac
Page 159 and 160: 14 Command-line Routine Debugging T
Page 161: Debugging with the Caché Debugger
Page 165 and 166: Debugging with the Caché Debugger
Page 171 and 172: Debugging With BREAK If you had not
Page 173 and 174: Debugging With BREAK use the line e
Page 175 and 176: Debugging With BREAK %SYS>BREAK "L"
Page 177 and 178: Using %STACK to Display the Stack L
Page 179 and 180: Using %STACK to Display the Stack F
Page 181 and 182: Other Debugging Tools 14.4 Other De
Page 183: Other Debugging Tools Note: %ER is
Page 186 and 187: Open M Language Compatibility WRITE
Page 188 and 189: Open M Language Compatibility • Y
Page 190 and 191: Open M Language Compatibility Param
Page 192 and 193: Open M Language Compatibility Bit 2
Page 194 and 195: Open M Language Compatibility • $
Page 196 and 197: Open M Language Compatibility • I
Page 198 and 199: Open M Language Compatibility The C
Page 200 and 201: Open M Language Compatibility • Z
Page 202 and 203: Open M Language Compatibility Cach
Page 204 and 205: Open M Language Compatibility missi
Page 206 and 207: Open M Language Compatibility • $
Page 208: Open M Language Compatibility • O
show all

Using Caché ObjectScript - InterSystems Documentation

Create successful ePaper yourself

Delete template?

Save as template?