The Enterprise Server jde.log File
You can use the enterprise server jde.log to track fatal error messages generated by batch applications and business functions that are executing on the enterprise server. The jde.log tracks any fault that might occur within JD Edwards EnterpriseOne. When you are looking for startup errors, you should read the jde.log from the top down. For other errors, you should read from the bottom up.
If jde.log is enabled, a uniquely identified log file is created each time you start a JD Edwards EnterpriseOne job (including JD Edwards EnterpriseOne startup) on the enterprise server. These logs are associated with an enterprise server process ID (Job Number for IBM i).
The process ID (Job Number for IBM i) is appended to the file name, before the .log extension, with an underscore character (for example, jde_442.log).
jde.log File Creation
The enterprise server jde.log file is created (if it does not exist) or overwritten (if it exists) at the start of every JD Edwards EnterpriseOne session. For a Microsoft Windows enterprise server jde.log file, JD Edwards EnterpriseOne appends new information to the end of the jde.log.
Troubleshooting: Enabling and Disabling jde.log
Normally, the enterprise server should be set to enable the jde.log and disable the jdedebug.log. This example has combinations for the jde.ini parameter setting for enabling or disabling server logs.
Enable jde.log
This is an example of the jde.log file with debug logging enabled:
[DEBUG] Output=NONE LogErrors=1 JobFile=valid location/name (1) DebugFile=valid location/name (2)
Enable jde.log and jdedebug.log
This is an example of the jde.log file with debug logging enabled and output to a file:
[DEBUG] Output=FILE LogErrors=1 JobFile=valid location/name (1) DebugFile=valid location/name (2)
Disable jde.log
This is an example of the jde.log file with debug logging disabled:
[DEBUG] Output=NONE JobFile=blank/invalid location/name (1) DebugFile= blank/invalid location/name (2)
Files and members generated by the jde.log will be located in JobFile. JD Edwards EnterpriseOne uses these naming conventions:
jde_process_ID.log
Where jde is the file or member name prefix, process_ID
is a uniquely named process ID, and log is the file or member suffix or
extension.
For non-IBM i enterprise servers, files generated by the jdedebug.log will be located in DebugFile. JD Edwards EnterpriseOne uses these naming conventions:
jdedebug_process_ID.log
Where jdedebug is the file name prefix, process_ID is a uniquely named process ID, and log is the file suffix or extension.
For IBM i enterprise servers, the members generated by jdedebug will be located in DebugFile. JD Edwards EnterpriseOne uses these naming conventions:
jdedebug_process_ID
Where jdedebug is the file name prefix and process_ID
is a uniquely named process ID.
Troubleshooting: Recommendations for the Enterprise Server jde.log
You can create a normal (successful) jde.log by signing on to JD Edwards EnterpriseOne and then immediately signing off. Use this log of successful startup statements to compare against logs that have a problem.
You can also rename the log to indicate the nature of the problem. For example, you might delete the jde.log and then run a report that causes an error condition. Then you could rename the jde.log to report.log.
If you are the only user running an instance of JD Edwards EnterpriseOne, you can add comment lines to the jde.log indicating the sequence of events you are performing. For example, you might be running an application that you know causes an error. Before you run the application, you could edit the jde.log to add a comment line stating you are about to start the suspect application.
Troubleshooting: Recommendations for Setting Up Server Locations
JD Edwards EnterpriseOne recommends that you create a separate directory on the enterprise server for logs. You should set up the jde.ini file to explicitly direct log files to that directory. For jde.log, the location and name of the log file are controlled by this default setting:
[DEBUG] JobFile=jde.log
Files generated by the jde.log are located in JobFile. JD Edwards EnterpriseOne uses this syntax for naming files:
jde_process_ID.log (jde_jobnumber.log for IBM i)
If you do not specify a location, JD Edwards EnterpriseOne places the log files in the directory where you ran the JD Edwards EnterpriseOne startup executable (the default). On a UNIX machine, if you start JD Edwards EnterpriseOne with these commands and if logging is enabled, the system places the log files in the /u13/JDEdwards/E920/system/bin32 directory:
cd /u13/JDEdwards/E920/system/bin32 RunOneWorld.sh
If you start JD Edwards EnterpriseOne with these commands and if logging is enabled, the system places the log files in the /usr/JDEdwards directory because that is the working directory:
cd /usr/JDEdwards
/u13/JDEdwards/E920/system/bin32/RunOneWorld.sh
If you set up the UNIX machine to automatically start JD Edwards EnterpriseOne when the machine is started, it is especially important that you specify the full path of the log file in the jde.ini file.
Naming Conventions for jde.log
JD Edwards EnterpriseOne processes create logs as jde_processID.log (jde_JobNumber.log for IBM i), where processID is the process ID of the process that creates the log.
Non-IBM i JD Edwards EnterpriseOne processes move logs for batch jobs to the PrintQueue directory and rename them as report_version_date_time.log, where report is the report name and version is the version name; for example, R014021_XJDE0001_D990312_T161854215.log.
Example: Enterprise Server jde.log
This example of the jde.log from the enterprise server displays errors caused by signon tables that were not properly closed after fetching data. Normally, the only way this can happen is if a business function program did not close the table. Therefore, generated code applications cannot have this problem.
Most entries in the jde.log file are significant, and you should examine them closely. This information is also used by developers to indicate problems with the application that need to be addressed.
Troubleshooting: Recommendations for the Enterprise Server jde.log when a fatal crash occurs
If a fatal crash occurs on a JD Edwards EnterpriseOne Windows Server the Call Stack will be automatically be dumped into the jde.log file. This information in the jde.log file will contain a fully qualified path to the system install location. Therefore, you should take the necessary steps to ensure that the install path information is secured.