Comments on: Batch debug

By: Featured Member: Graybeard52 - ITKE Community Blog

Featured Member: Graybeard52 - ITKE Community Blog — Tue, 10 May 2011 06:24:31 +0000

[...] Batch debug [...]

By: tomliotta

tomliotta — Sun, 03 Apr 2011 10:03:03 +0000

What kind of files are we referring here? Is it a pf files, lf files, etc?

First, this is a mostly separate question; so it should be asked in a separate thread.

Second, the UPDPROD() parameter works against data files that may be physical (PF) or logical (LF). But they will be *PROD files if UPDPROD(*YES) is required. A *PROD file is one that exists in a library that was created as TYPE(*PROD). See the CRTLIB command to review the TYPE() parameter.

The idea is that a debugging session may involve a programmer changing values in memory in order to affect production data. This can be a serious violation of system and application security and should be controlled. The UPDPROD(*YES) action requires significant authority. By copying data into a *TEST library and running in a test environment, UPDPROD(*NO) can be used; and production files are protected — the system will prevent accidental changes to *PROD data.

UPDPROD(*YES) should be used only with care.

Tom

By: neon

neon — Sat, 02 Apr 2011 12:19:58 +0000

During debugging, i have noticed the parameter UPDPROD(*YES) which means you are going to update the production files. What kind of files are we referring here? Is it a pf files, lf files, etc? Please help.

..Neon

By: graybeard52

graybeard52 — Tue, 08 Jul 2008 17:06:00 +0000

Or, from the RSE panel, right-click either the object or the object source you want to debug and select “Set service Entry Point” (also set the userid you want to debug). When the program launches, the debugger interface opens automagically. You can then set monitors, watches, break points,etc. The break points can be saved with the source code.