Debugging from Code: Interactive vs. Non-Interactive applications

[berestet@xxxxxxxxxx]

Hi folks,

Lately, there seem to be a few questions floating around regarding
interactive and
non-interactive CODE servers and what they mean for CODE debugger. I think
that
the following posting might clear things up for everyone who uses CODE
debugger:

Historically, CODE/400 users had to issue an STRCODE command on 5250
screen to get a CODE/400 server connection. Obviously, this required
an interactive session and user issuing a command after each PC reboot.
Hence, we added a way to configure CODE servers via the 'Communications
Daemon'
dialog. These server configurations are more 'permanent' (stay there
between
reboots), but they do not have an associated interactive session.
They are good for most CODE interactions with client, but not good at
all for debugging or running interactive applications. For interactive
scenarios you do require to have an interactive CODE server started via
STRCODE command.
Both server types will show up in the server list, but they look
differently.
NOTE: Server names MUST be unique across all kinds of CODE servers.

Having said all that, 'Actions' -> 'Debug' has 'Interactive' and
'Non-Interactive' options. They will list appropriately interactive and
non-interactive servers available for debugging purposes. Same goes for
the 'Set Default Server' option.

n most cases you can use a non-interactive CODE server for debugging
as long as your application has no I/O screens).

Hope this is useful.
Regards,
Vadim Berestetsky,
Distributed Debugger development.