The RBP option lets you halt a program prior to all CICS commands, DL/I, DB2, or calls to software recognized by CA InterTest for CICS. This option also lets you halt a program prior to specific CICS commands, such as File Control or Program Control commands. Most users will find it easier to use the CNTL Command Builder menus rather than the RBP option to specify request breakpoints.
Note: If the F=term1 or T=term2 parameter is omitted, it defaults to the terminal that issued the RBP option.
To specify request breakpoints, use the following commands:
RBP=request RBP=(request1,request2,...,request9)
RBP=((request),F=term1,T=term2) RBP=((request1,...,request9),F=term1,T=term2)
RBP=((request),F=term1,T=term2,L=loopnumber) RBP=((request1,...,request9),F=term1,T=term2,L=loopnumber)
Specifies where the request breakpoint should occur:
For a list of valid codes, see the Help facility.
Specifies the terminal at which the program must be executing for the breakpoint to take effect. F=.ANY specifies that the breakpoint take effect at all terminals—even when the program executes without a terminal. F=.NO specifies that the breakpoint take effect only when the program executes without a terminal.
Specifies the terminal to which the breakpoint display is sent. T=.ANY specifies that the breakpoint display be sent to the terminal at which the program is executing.
Specifies how often the program should be halted at the breakpoint.
Example
L=2 halts the program every other time it reaches the specified command; L=13 halts it every thirteenth time. If this parameter is omitted, the breakpoint occurs every time the program reaches the specified command. This parameter is especially useful when a CICS command occurs within a loop; for example, during a browse.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|