RE: Debugging with missing source

What's the compile default for DBGVIEW? That should be configurable on the
development side of the package.

I'm not sure what you mean about moving the programs with their source. Does
that mean the source code is sent to the production machine when you deploy
the program objects?

Paul Nelson
Cell 708-670-6978
Office 409-267-4027
nelsonp@xxxxxxxxxxxxx


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Matt
Lavinder
Sent: Thursday, October 09, 2014 7:36 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Debugging with missing source

We are using a new change management package that compiles programs once
and then moves them with their source. It's their way of doing things,
but the issue is if we try to debug it in our test environment, the
source is no longer in the development library and STRDBG cannot find
the source.

Their answer is to use the RDi debugger because it lets you specify a
source file, but not all our developers are using RDi. The ones that do
really don't like using its debugger as it takes quite a bit to get it
up and running.

I am aware the STRISDBG allows you to specify a source member. Is there
a way to do something similar in STRDBG?

Also, can STRISDBG debug ILE programs and service programs?