Debugging a trigger program. Posts Latest Activity Photos. Page of 1. Filtered by:. Previous template Next. Debugging a trigger program August 6, , PM. Hi, Is there any way we can debug a trigger program when it is called upon any file operation. Thanks in advance. Tags: None. August 7, , AM. We can debug a trigger program that is associated with the file for certain operation. Then you can see the program is stopped at the placed breakpoint.
But all it needs is to work on the same session. It won't work, if we put the break point in one session and do the file operation on the other session. Comment Post Cancel. Re: Debugging a trigger program You can debug the program just like any other program that you have access to. PHP Code:. Hunting down the future ms. Ex DeadManWalks. August 8, , AM. Re: Debugging a trigger program whts "RSE". Positions the view to the next breakpoint in the source currently displayed.
Positions the view to the previous breakpoint in the source currently displayed. Shows the online help information for the available source debugger commands.
Specifies if case sensitive or case insensitive searching is performed for all subsequent FIND requests in the current debug session. It also allows you to change the update production files value.
Displays a list of the currently active watch conditions. The module object is created by using references to locations of the source statements in the root source member instead of copying the source statements into the view. Therefore, you should not modify, rename, or move root source members between the creation of the module and the debugging of the module created from these members. These functions include:. If the line on which you want to set a breakpoint is not a runnable statement, the breakpoint is set at the next runnable statement.
The name of the sort sequence table is saved during compilation. At debug time, the source debugger uses the name saved from the compilation to access the sort sequence table. Char Character literal is of the form 'abc'. Hexadecimal literal is of the form X'hex digits'. You cannot specify the number of statements to step through when you use F10 Step or F22 Step into. Pressing F10 Step or F22 Step into performs a single step. The called program object must have debug data associated with it in order for it to be shown in the Display Module Source display.
Variable-name is the name of the variable that you want to display in hexadecimal format. If no length is specified after the 'x', the size of the variable is used as the length. A minimum of 16 bytes is always displayed. If the length of the variable is less than 16 bytes, then the remaining space is filled with zeroes until the 16 byte boundary is reached. DBCS variables can be assigned any of the following:. If a program that is in debug mode is deleted, re-created, or saved with storage freed, references made to that program except a RMVPGM command may result in a function check.
If you want to change the program and then debug it, you must remove it from debug mode and after it is re-created, add it to debug mode ADDPGM command. CL programs can be recursive; that is, a CL program can call itself either directly or indirectly through a program it has called.
Some high-level languages do not allow recursive program calls. Other languages allow not only programs to be recursive, but also procedures within a program to be recursive. In this guide, the term recursion level refers to the number of times the program has been called in the call stack. A procedure's recursion level is referred to explicitly as the procedure recursion level.
All CL commands and displays make use of only the program qualified name recursion level. A CL variable must be entered with surrounding apostrophes. If you specify an array variable, you can do one of the following:. Specify the subscript values of the array element you want to display. The subscript values can either be integer values or the names of numeric variables in the program.
Display the entire array by not entering any subscripts. Display a single-dimension cross-section of the array by specifying values for all subscripts except one, and an asterisk for that one subscript value. Variable names can be specified as simple or qualified names, but must be placed between apostrophes.
A qualified name can be specified in either of two ways:. Variable names alternating with the special separator words OF or IN, ordered from lowest to highest qualification level.
A blank must separate the variable name and the special separator word. Variable names separated by periods, ordered from highest to lowest qualification level. In some languages, the definition of a call is made at the procedure level and not just at the program level. For these languages, storage for automatic variables is associated with the call of the procedure.
Every time a procedure is called, a new copy of the variable is gotten. A change to an automatic variable remains in effect only while that procedure is called. Only the automatic variables in the most recent procedure call can be changed. You can show the job name from this display by selecting option 5 for the job. No other debug commands can be entered while the job is waiting on the job queue. A display appears when the job is ready to start, indicating that you may begin debugging the job.
Press F10 to show the Command Entry display. Press F3 to leave the Command Entry display, and then press Enter to start the batch job. When the job stops at a breakpoint, you see the normal breakpoint display.
0コメント