D
dbeavon
Guest
I really like the log entry type of FileID for seeing exactly when things are being compiled, within the control flow of the ABL programs. Additionally I wanted to point out that I found another way to see what was compiled between "check-points". IE. you can run a program, and after it comes back you can check to see if anything important was compiled along the way. This is possible by enabling the "-y" startup parameter for "procedure usage statistics": OpenEdge 11.7 Documentation Then you can use the SHOW-STATS or SHOW-STATS CLEAR commands whenever you wish to know about the possible compilation of programs on the fly. The output looks like the following. If you see zero compilations and zero saves, then you know that there were no delays that were compiler-related. Saves of compilation .r's: 0 0 Compilations of .p's: 0 0 Checks of files with stat: 64 0 Unfortunately this information isn't going to appear in the client logging file, but in another file (named in the format "client.XXX.AS-YYY.mon") which will be located in your working directory. We then have to correlate the information from one log file with the information from the other log file. This correlation is easier if the SHOW-STATS statement is used on a frequent basis.
Continue reading...
Continue reading...