Re: Debugging with missing source

[Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>]

To expand - Matt, your CMS should let you change defaults for the create 
commands - or you should be able to override them. As Paul says, set the 
DBGVIEW parameter there.

STRISDB will not do ILE programs at all. STRDBG can do OPM programs if 
you have used the right option on the create and if you say yes to the 
OPMSRC parameter.

Our CMS does copy the source to the production LPAR, so that we have the 
same process happening on development and production - a SOX thing, as 
it's been explained to me.

Now there may be reasons not to make debugging easy on a production 
system - I can't on ours. In order to debug something, I need to make my 
own copy on the production machine in my test library, with the debug 
options set. But we are not supposed to even run test stuff on 
production, if we can avoid it - too much possibility of corrupting things.

One more thing - your CMS should let you change command defaults at 
different promotion levels - so that when promoted to test, you get the 
debug stuff - when promoted to production, you don't.

HTH
Vern

On 10/9/2014 7:41 AM, Paul Nelson wrote:
> 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?