Tips on Reading jdedebuglog FilesWord文档下载推荐.docx

1、 Turning on debug logsStep 2: Get into EnterpriseOneStep 3: Locate jdedebug.logStep 4: Generate the jdedebug.logStep 5: Delete unwanted informationStep 6: Create the Purchase OrderStep 7: Look at the jdedebug.logStep 8: Copying information into ExcelStep 9: Fill in the sequence numberStep 10: Sort d

2、ata and delete unwanted informationStep 11: Turn off Debug LogsA bit of information on the format of SQL statements Turning on debug logs To begin the process, turn debugging on in the jde.ini. This is accomplished by going to the start menu and clicking on “Run”.In the run dialog window type in C:/

3、winnt/jde.ini. The Notepad program will open up and display the contents of the jde.ini file.Change the line located under the DEBUG stanza from Output=NONE to Output=FILE. Further down a line that reads DebugFile=c:jdedebug.log indicates that the debug file will be located in the C: and its name wi

4、ll be jdedebug.log. This could be named anything, but the default value is fine.Save the changes and close Notepad. The LEVEL line in the INI file sets up how much detail to record in the jdedebug.log. The default value is fine for this operation.A note on the jdedebug.log file: The debug log file w

5、ill grow in size quickly while EnterpriseOne is used. This is because every call to a table, business function, menu, object and everything else is recorded. Setting to a different LEVEL of detail can reduce this, but still there is a lot of data. This file can also be deleted using the Windows Expl

6、orer and it will simply be created again by EnterpriseOne. This functionality is important for this exercise.Back to Top Get into EnterpriseOne Start up EnterpriseOne. This process will automatically create the jdedebug.log in the C: directory as specified in the JDE.INI file we edited in step 1.Ope

7、n up Windows Explorer the jdedebug.log is seen Remember it is located it in the root directory of C Drive. It may be at the bottom of the list as it will have just been created by EnterpriseOne. Generate the jdedebug.log One way to use debug logs is to follow what tables are populated and what recor

8、ds are changed when a Purchase Order is created. However, while navigating through EnterpriseOne data is being captured in the jdedebug.log. It is in this stage, that the function of the jdedebug.log being continually recreated after it is deleted is important. To get only the information required,

9、get to the point where the information in the debuglog is valuable. In this case, click Add, fill out the information in the header and detail, but do not press the OK button to save the PO yet. Delete unwanted information Remember the debug file is full of unwanted information. For this example, we

10、 are looking for the data changed or entered when I save the PO, not all the data relating to opening the PO menu, verifying item and supplier numbers etc. To do this, go back to the Windows Explorer and delete the jdedebug.log.Yup delete it! Dont worry; it will be recreated when the Purchase Order

11、is saved with only the pertinent information. Create the Purchase Order Go back to EnterpriseOne and click OK. The Purchase Order is saved. Do nothing else in EnterpriseOne. Look at the jdedebug.log Go back to Windows Explorer and locate the newly created jdedebug.log file. Double click the file; it

12、 will open up using the Notepad program. It is full of datawading through this looking for all the data entries takes a long time. Even using the search tool can be difficult trying to follow the chronological order of the data. The following method of using Excel helps filter out only the data we w

13、ant and keep it in order.Highlight the entire list of entries in the jdedebug.log （Edit menu, Select All） and Copy （Ctrl+C）. Open Excel and Paste （Ctrl+V） the copied information into field B1. Fill in the sequence number Fill in a sequence of numbers in Column A. This can be done by entering 1 in A1

14、 and 2 in A2 and then highlighting and dragging to the end of the pasted data. Widened column B so that the pasted data is shown more clearly.Now sort the data by column C so that it is easy to locate the SQL commands entries SELECT, UPDATE and INSERT these names are self explanatory, but more detai

15、ls of how they are used and the format they are used in will follow.Once the data has been sorted by column C it easy to delete all the rows of information where SELECT, UPDATE and INSERT are not in column C. After deleting all the rows where SELECT, UPDATE and INSERT are not in column C, a fewer nu

16、mber of rows are left, showing just the data we want to see. By once again sorting all the data, but this time using Column A as the sort key to put the information back into chronological order which shows the data in and out of table as it happened.The SELECT statements may not be necessary, as th

17、ey are only calling data, not changing data. They could also be deleted. The graphic above shows all the data changes （UPDATE） and record entries （INSERT） in the order they occurred when a Purchase Order is saved. This is very useful to better understand the processes in EnterpriseOne and follow exa

18、ctly where and what data is Selected, Updated and Inserted into tables.When you have finished using the JDEDEBUG.LOG turn it off so that you do not clutter up your hard drive. See step 1 to change the OUTPUT=FILE back to OUTPUT=NONE.SelectThe select statement is used to select data from a table.SELE

19、CT * FROM F0101 WHERE （ ABAN8 = 1001.000000 ） This means select All the data （*） from table F0101 where field ABAN8 （the Address Number） = 1001 .The * may also be replaced by 1 or many field names. UpdateThe update statement is used to change existing data in a record.UPDATE F4102 SET IBITM=60003.00

20、0000,IBMCU= 30,IBMRPC=1,IBUSER=DEMO,IBPID=EP4310,IBJOBN=MEL-CG6840,IBUPMJ=2/12/2001,IBTDAY=85439.000000 WHERE （ IBITM = 60003.000000 AND IBMCU = ）This means update the record in F4102 and make the following fields have the value specified: IBITM=60003, IBMCU= 30etc. in this table for the record wher

21、e IBITM = 60003 and IBMCU = 30InsertThe insert is used to insert a new record in a table.INSERT INTO F4074 VALUES （4923.000000,OP,00001,1.000000,0.000000, ,60003.000000,4343.000000,0.000000,USDEA,0.000000,10.000000,0.000000,2/12/2001,85437.000000）This means that a new record will be inserted into F4311. The data will be entered into the fields in the order shown and separated by commas. In some cases you will see that Zeros have been used to “pad” the cellsBottom of Form