|
For actual debugging, using the normal
PERCobol debugger, the Application Server must be started in debug mode.
That involves either using the Application Server's special 'debug'
startup script, or modifying the startup script that already exists
(making a backup first).
The java line that starts the appserver must be similar to the following:
java.exe -Djava.compiler=NONE
-Xdebug -Xnoagent
-Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=y ...
where ... is the rest of the normal line. /(The -Djava.compiler=NONE
parameter is not necessary for JDK 1.4. It was required for JDK 1.3. Note,
it does slow down the Application Server significantly.)
The PERCobol debugger will then be used in 'remote' launch configuration
mode to the Application Server system. (This is true even when the
Application Server system is the same as the one running the IDE since the
program is controlled from a different process.)
However, since that involves a lot of steps, it's usually simpler to just
add spot debugging statements (DISPLAY UPON SYSOUT or SYSERR will usually
go to the appserver console) or use EXEC CICS TRACE statements. A journal
may be setup to point to SYSOUT or SYSERR, and then the trace set to use
this journal.
|
