So in the UNIX world I can still use batchdebug or batchanim.
On NT it seems those are not available to me.

Well batchdebug is but all it does is return the prompt. I am trying to debug a report which is doing some really wierd things. Any help would be appreciated.

Thanks

There is some fairly detailed instruction in the knowledbase about doing a debug on NT/W2K. One of the requirements is that you need to be at the server console. I did try it once but could'nt make it work. GSC kept asking me to make sure I was at the console (which I was). One of the Lawson folks I met at CUE 2004 swore it works perfectly. In any case, since the server room access was restricted, I gave up and ended up putting in a whole bunch of displays.

For batch programs I'm almost positive that you do not have to be on the console. I've worked with the GSC more than once (although not too recently) in debugging batch programs and I have used terminal services without any issues. I asked that specific question in my case as well so I'll see if I can find those case details to confirm. I believe the only requirements for batch programs is that the user performing the batch debug is an admin in both Lawson and on the server itself.

I do recommend you reference the KB articles for animating batch jobs if you haven't read them though because they do provide some good details on the process.

Well that pretty much sucks.
I don't have access to the server or terminal server. I'm logged in through a vpn connection and really only use LID.
I know on UNIX both batch and cob debug are extremely easy to do. You can't expect developers to be at the server to debug their programs. Debugging is a huge part of good programming even if your code is working fine.

Suggestion: Create a Rant and Rave section so I don't have to complain about these things here :angry:

Hey, I feel your pain! I can't do a debug session yet in W2K either.

Some things that I've stumbled across during documentation searches:
o Program has to be recompiled with "-D" flag
o In W2K you can only debug if you are on the System console. (I don't know if using Windows' Remote Desktop Connection is okay.)
o ladebug has to be running (ladebug is the "Debug Server")
o You have to specify debugging is "TRUE" in ladebug.cfg.

The actual debugger is called the Micro Focus Net Express Animator. You have to run that. The explanation of how to run it goes on for many pages in the Application Development Workbench manual.

That's why I haven't bothered to get it running. I usually recompile an offending program with the -T option, and examine the job log to see the trace.