Cross-session Debugging - Micro Focus

Cross-session Debugging
Cross-session debugging allows you to use Animator in a different terminal
window to that in which the program to be debugged is running. With crosssession
debugging, Animator is started first in one session and left in a
waiting state. Both sessions must use the same user ID.
Using the COBANIMSRV Environment Variable
The COBANIMSRV Environment Variable will need to set in both terminal
windows for cross-session debugging. The environment variable will need a
unique identifier. Animator will then only debug a program that has a
matching identifier.
For example, in one session enter:
export COBANIMSRV=myid
myid is now a unique identifier you can use to match Animator to a program.
Enter the command to start Animator:
cobanimsrv
Animator waits for the COBOL program to start that has the same identifier.
In another session enter:
export COBANIMSRV=myid
cobrun program1.int
When program1.int starts, the unique identifier myid matches that of
Animator, so Animator attaches to this process. In the first session, the
Animator main screen is displayed and the cursor placed on the first line
program1.int.
Using the Same Directory
If Animator is started in the same directory as that in which you run the
program that is to be debugged, the program will attach to the waiting
Animator process.
Using CBL_DEBUG_START and CBL_DEBUG_STOP
With these routines you can switch debugging on and off as you wish and
debug more than one program without having to stop and restart the
Animator process. You start up Animator in one session, using the
cobanimsrv command. In a second session you run a program that has a
different COBANIMSRV environment variable value, or if it is not set, is
running in a different directory. This program starts running as normal, not
animated.

When a call to CBL_DEBUG_START is encountered with an identifier
parameter that matches the value of the COBANIMSRV environment variable
for the Animator process, or if the identifier parameter is unset, is running in
the same directory, then Animator attaches to the program.
For example, in one session enter:
export COBANIMSRV=myid
myid is now a unique identifier you can use to match Animator to a program.
Enter the command to start Animator:
cobanimsrv
Animator waits for a COBOL program to start that has a matching identifier.
In another session enter:
cobrun program1.int
The program1.int program starts running without animation. A call to
CBL_DEBUG_START is encountered:
call CBL_DEBUG_START using by value flags, timeout,
by reference "myid",
returning status-code
The unique identifier myid matches that of Animator, so Animator attaches to
this process. In the first session, the Animator main screen is displayed and
the cursor placed on the line of prog1.int containing the CBL_DEBUG_START
call.
You can stop or suspend debugging by issuing a call to CBL_DEBUG_STOP.
CBL_DEBUG_START and CBL_DEBUG_STOP calls can also be used to switch
remote and local animation on and off.
Just-in-time Debugging
Just-in-time debugging enables you to start Animator and debug a running
program if that program terminates with a run-time error. This will allow you
to see what was happening when the program failed.
To start just-in-time debugging you need to create your run-time
configuration and then add the run-time tunable debug_on_error to the
configuration file.
For example, add the following line:
set debug_on_error=1
Ensure that the configuration file can be read by the run-time system:
export COBCONFIG=cobopt.cfg
Additional Options

There might also be a need to specify which debugger to start. Normally, it
is not necessary to specify this as cobanim is set by default, as it enables
Animator to start in a separate window under X. If you want to specify a
different debugger, such as anim add
set debugger_command="anim"
to the configuration file.
You might also want to add directives to the command;
for example, to add directives to the cobanim command:
set debugger_command="cobanim mixedlangdebug"