V
vkurien
Guest
Hello, Before whoever is reading this, the question,that you need to answer is how to find locking issues on an AppServer PAS/Classic. Not talking lock-wait timeout, but locking that can happen for faction of sec for each iteration loop and each loop running millions of times. On a Progress Client running (_progres) with -b I can turn on 4GLMessages to see in use by on . Wait or choose CANCEL to stop. (2624) But on a Appserver there is no way to display this message since 4GLMessages are not valid for Appserver. I understand why 4GLMessages are not there because progress is displaying some messages and some not to reduce the log file size. But when there is a problem there should be a way by which a developer should be able to turn on logging flag and see all the messages that are displayed by 4GLMessages. This can be done using a new parameter AS4GLMessages when set will display all messages to AS log. I know it is kind of hard to reason why you need this on an appserver, but believe me most customers use appserver for mult-threading of long running jobs and it is difficult to scan through 100's programs when promon shows lots of lock waits but does not give any info about line number or program. Thanks, Verghese
Continue reading...
Continue reading...