I received a message after publishing the No More Number Indicators story about an alternate method of conditioning fields in a Display file without using indicators. As the person who sent me this did so as Anonymous I cannot thank them by name, but you know who you are. I did use this method once. QPRTJOB is a job that is automatically created by the system when your job tries to create a spool file and the job's current user ID is different to the user ID that the job is running under. For example, in your GUI application, the HTTP server job starts running under. Q: Is there a way I can get the attributes (date/time created/modified, file size) for an IFS object in a CL or RPG/IV program? I have a batch file running on an NT server that extracts some data from another server (Novell) to a directory on the AS/400. Debugging a Program Debugging allows you to detect, diagnose, and eliminate errors in a program. You can debug your OPM and ILE COBOL programs using the ILE source debugger. This chapter describes how to use the ILE source debugger to: Prepare your ILE. I've 4 databases A,B,C an D which are connected through one another through database links. A single schema can have multiple links which connect to different schemas on the remote database. All the links were created by using the option 'connect to. Complete AS400 System Administrator - Free ebook download as PDF File (.pdf), Text File (.txt) or read book online for free. AS/400 SYSTEM OPERATIONS System Administrator Tasks . Debugging a Program. ILE COBOL Programmer's Guide. Debugging allows you to detect, diagnose, and eliminate errors in a. You can debug your OPM and ILE COBOL programs using the ILE. The. syntax for preventing file modification would be. See the chapter on debugging in the ILE Concepts. ILE source debugger (including authority. Using debug commands with. ILE program that contains debug data you can. Debug any ILE COBOL or mixed ILE language application. Monitor the flow of a program by using the debug commands while the. If you use the ILE COBOL COLLATING SEQUENCE clause in your. ILE COBOL program to specify your own collating sequence, this collating. ILE source debugger. At this point you can enter more debug. After you have. started the debugger, you can set breakpoints or other ILE source debugger. The debug commands and their parameters are entered on the. Debug command line displayed on the bottom of the Display Module Source and. Evaluate Expression displays. These commands can be entered in upper. Refer to ILE Concepts. The online help for. ILE source debugger describes the debug commands and explains their. The. attributes are the size and type of the variable as recorded in the debug. Refer to Table 5 for a list of attributes and their ILE COBOL. These attributes are not the same as the attributes. ILE COBOL. Use BREAK. WHEN expression to enter a conditional job. It also allows you to display a different source module. Display Module Source display. The. module object must exist in the current program object. Table 5 shows the equivalence between the attributes of variables as. ILE source debugger and ILE COBOL data categories. They are. Statement view. For more information. Starting the ILE Source Debugger. The listing view provides all. COPY and REPLACE statements) made by the ILE COBOL. The. listing view exist independent of the source member. The source member. However, any debug commands issued from. Display Module Source display will be applied only to the compilation unit. Therefore, you should not modify, rename, or move root. The size of the generated module. The source view does. ILE COBOL compiler when it creates the. The source view depends on the. Any changes made to the. However, any debug commands issued from the. Display Module Source display will be applied only to the compilation unit. It contains. line numbers and statement numbers. To debug an ILE COBOL module object. The size of the. created module object is smaller than that generated with the listing view or. The statement view minimizes the size of the created. The. statement view only provides the symbol table and a mapping between statement. You can change the attributes of the debug mode later. Change Debug (CHGDBG) command. The ENDDBG command does not have any. For a full description of the STRDBG. CHGDBG, and ENDDBG commands and their parameters, refer to the CL and. APIs section of the Programming category in the i. Series. 4. 00 Information Center at this Web site - http: //publib. Up to 2. 0 service programs can initially be added to the debug. Service Program (SRVPGM) parameter of the STRDBG. Additional service programs can be added to the debug session. In addition, you can initially add as many. Service Programs. SRVPGM) parameter on the STRDBG command. The rules for debugging a. The program or service program must have debug data. You must have *CHANGE authority to a program or service program object to. If ILE, the entry. ILE program with debug data is shown. RPG and COBOL programs can be compiled with *LSTDBG or *SRCDBG. CL programs must be compiled with *SRCDBG.). The ILE debug environment is set to accept OPM programs. You can do. this by specifying OPMSRC(*YES) on the STRDBG command. If there is no debug data, then the DSPMODSRC screen will be. If an ILE program and a service program are specified, then the. ILE program will be shown. When a mixture of ILE programs and ILE debugger- enabled OPM. STRDBG command, the first program with debug. If the first program is an ILE program, the first module. Figure 3. 3. You can also use the Change Debug (CHGDBG) command to set. However, the OPMSRC option cannot be changed by the. CHGDBG command. OPMSRC can only be changed by the SET debug. To enable the ILE source debugger to accept OPM programs. After entering STRDBG, if the current display is not the. Display Module Source display, type. The Set Debug Options display appears. Then, call the program. CALL CL command. If the exception is not handled by any. Display Module Source display is. The module object within which the exception occurred is. Refer to ILE COBOL Error and Exception Handling for more information on error and exception handling. Refer to Setting and Removing Breakpoints for more information on setting breakpoints. The Work with Module List display can be accessed. Display Module Source display by pressing F1. Work with Module. List). To add a service program, change the default program type from. PGM to *SRVPGM. There is no limit to the number of ILE program objects. If you specified. OPMSRC(*YES), by using either STRDBG, the SET debug command, or CHGDBG, then. OPM program using the Work with Module List display. If you specified. OPMSRC(*NO), then you must use the Add Program (ADDPGM) command. Only. 2. 0 OPM programs can be in a debug session when OPMSRC(*NO) is. If an OPM program is already in an OPM debug session. ILE debug. session or stepping into it from a call statement. Similarly, if you. OPM debug session, you must first remove it from an. ILE debug session. ILE service programs can be added to a debug session only by. Work with Module List display. ILE service. programs cannot be specified on the STRDBG command. The Work with Module List display can be accessed. Display Module Source display by pressing F1. Work with Module. List). If you specified. OPMSRC(*YES), by using either STRDBG, the SET debug command, or CHGDBG, then. OPM program using the Work with Module display. If you specified. OPMSRC(*NO), then you must use the Remove Program (RMVPGM) command. A module object's. DBGVIEW(*SOURCE). The source of an OPM program can be shown if the following conditions are. The OPM program was compiled with OPTION(*LSTDBG) or. OPTION(*SRCDBG). Lines numbers that have breakpoints set are. When a breakpoint, step, or message causes the program to. The Work with Module List display can be accessed from the. Display Module Source display by pressing F1. Work with Module List). If you use this option with an ILE. Otherwise, the first module object bound to the program object. If you use this option with an OPM program. On the debug command line, type. DISPLAY MODULE module- name. The module object module- name will now be shown. The. module object must exist in a program object that has been added to the debug. These views are. ILE COBOL Listing view. ILE COBOL Source view. You can change the view of the module object that is shown on the Display. Module Source display through the Select View display. The Select View. display can be accessed from the Display Module Source display by pressing F1. Select View). The Select View display is shown in Figure 3. The current view is listed at the top of the window. Each module. object in a program object or service program can have a different set of. An unconditional. A conditional breakpoint stops the program object. Both a job breakpoint. In. general, there is one set of debug commands and Function keys for job. For the rest of this. The appropriate module object is shown with the. This line. is highlighted. At this point, you can evaluate variables, set more. An unconditional job breakpoint is set. The job breakpoint is removed from. A list of options appear which allow you to set or. If you select 4 (Clear), a job breakpoint is. You can also use F2. Command Line) from the. Display Module Source display to call the program from a command line. When a breakpoint is reached, the program. Display Module Source display is shown. At this point, you can evaluate variables, set more breakpoints. When a job breakpoint is cleared, it is cleared. For more information, see Example of Using ILE COBOL in a Multithreaded Environment. Where the BREAK debug command sets a job breakpoint at the. TBREAK debug command sets a thread. When a debug stop occurs. The debug THREAD command and the Work with Debugged. Threads display can be used to change the current thread. When a thread breakpoint is cleared, it is cleared for the. The Work with Module Breakpoints. Display Module Source display by pressing F1. Work with module breakpoints). The Work with Module Breakpoints. Figure 3. 8. You can also use F2. Command Line) from the Display Module. Source display to call the program object from a command line. When a statement with a. If the. result is false, the program object continues to run. If the result is. Display Module Source display is. At this point, you can evaluate variables, set more breakpoints. The conditional. expression can only be a simple expression. The term on the right hand. For example, I=2. I=A+2 or I=3*2 are not accepted. You can also remove. Figure 3. 8 shows a typical display where 4 (Clear) could be entered in. Opt field. The difference between these commands is that the. BREAK debug command sets a conditional job breakpoint at the same position in. TBREAK debug command sets a conditional thread. When a conditional thread breakpoint is removed, it is removed. To. use the debug command, type. The breakpoints are removed from all of. Setting watch. conditions is similar to setting conditional job breakpoints, with these. Watch conditions stop the program as soon as the value of a watched. When the content at the storage address is changed from the value. The next watch condition will be registered if. This number includes watches set by the. If you try to set a watch. Therefore, the maximum. If this is. not the case, an error message is issued when a watch is requested, indicating. Therefore, if a watch is set on a temporary location. You must not assume that a variable is in scope just. If these restrictions are.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2016
Categories |