• This utility lets you toggle J.D. Edwards® OneWorld/EnterpriseOne® Debug Logging On and Off on the fly.
• It works for both GUI interfaces (aktivConsole.exe and oexplore.exe) as well as any Server / Background processes (if run on an Intel Logic Server).
• It works under Windows® NT / 2000 / XP / 2003 / Vista (Note: there is no W95/98/ME support).
• The OWDLC.EXE is a GUI-based WIN32 executable.
• It requires standard Windows® system "psapi.dll" library (normally installed by OneWorld/EnterpriseOne® into the Windows System32 folder anyway).
• Naturally, the user running OWDLC must be a member of the local "Administrators" group on their machine in order to use this tool.

Version 9.0.0 Highlights:

XP64 fixes, better error reporting, E900 support, new skin, digitally signed executable and setup.

Version 8.2.2 Highlights:

New improved interface.

Version 8 Highlights:

• Julian Date To/From conversion routines - an easy to use convenience feature;

Version 7 Highlights:

• Control over OneWorld/EnterpriseOne® Server Processes (when executed on Intel-based Enterprise Servers) - including processing batches;
• Re-sizeable window - important when there are many running OneWorld/EnterpriseOne® processes;
• Sorted Grid - important when there are many running OneWorld/EnterpriseOne® processes (double-click a column header to sort);
• Report the effective OneWorld/EnterpriseOne® User Name and the Environment for each Process displayed (this will not work under NT / 2000 / 2003 Terminal Server Edition for other user's sessions), including most of the Server Processes (some of them do not actually log in);
• Reset ALL OneWorld/EnterpriseOne® Memory Caches (per process) - including Data / Security / OCM / DSN, etc. - this functionality is present in OneWorld/EnterpriseOne®, but is not available under Terminal Server (because LOCAL server is hidden);
• ERP9 (Unicode) Support;
• Since v. 7.0.0.5, OWDLC minimises into an icon in the System Tray;
• Version 7.2 introduces a new feature - one-click deletion of the 6 DD files (DDDICT, DDTEXT & GLBLTBL) in all installed PathCodes on the Client;
• V. 7.3 improves the interface slightly: "F5" for "Refresh", a new pop-up menu item for "Delete the 6 DD Files", etc.;
• V. 7.4 introduces E810 support.

Known Issues:
=== None ===

From about SP21, toggling debuglog ON using OWDLC makes OneWorld/EnterpriseOne® to log everything, except the SQL statements. This is caused by the new threading implementation in OW Middleware - it now stores a thread-safe copy of the logging flag for each thread (or open datasource?), ignoring the current global value.

The work-around is to start OW with "Output" setting in the "[DEBUG]" section of the JDE.INI file set to "FILE" (no quotes), then toggle DebugLog OFF using OWDLC after starting JDE Client up and truncate the JDEDEBUG.LOG. Now, turning the logging ON and OFF will work just as it used to, before SP21.

    * Starting with XE SP20 the JDEDEBUG.LOG file is always kept open AND locked and cannot be deleted (or truncated/overwritten) except by OWDLC (since v. 6).

      Truncating the JDEDEBUG.LOG file for OneWorld/EnterpriseOne® SP20 and above doesn't work under the original WinXP (without any Service Packs) - caused by a WinXP bug that has been fixed in WinXP SP1.

   * Although it is not a bug, but a fundamental Terminal Server property, it is in some respects an issue that under WTS the Debug Logging can only be toggled for the current user session's OneWorld/EnterpriseOne® process and not for other users' sessions, which will show as "INACCESSIBLE" in the grid.

      OWDLC will list all OneWorld/EnterpriseOne® processes and report Windows User Name for each process, but those processes running in other users' sessions will read "INACCESSIBLE" in the DebugLog status field and have the OneWorld/EnterpriseOne® User Name field blank.

   * And of course, if the OneWorld/EnterpriseOne® process you are attempting to toggle the debuglog mode for is being debugged and is paused in the Debugger, the status won't change because the process is not actually running.

   * Windows/Intel "Data Execution Prevention" feature may have a direct impact on OWDLC functionality and should be disabled for this application.