If the OPM programs are compiled with OPTION(*LSTDBG) and the GENOPT(*LIST) you can use STRDGB without source. Set the OPMSRC() option to OPMSRC(*YES).
For ILE programs compile with OPTION(*SRCSTMT) and DBGVIEW(*LIST) to not need the source.
*LIST
Generates the listing view for debugging the compiled
program object. The information contained in the
listing view is dependent on whether *SHOWCPY,
*EXPDDS, and *SRCSTMT are specified for the OPTION
parameter.
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Matt Lavinder
Sent: Thursday, October 09, 2014 5: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?
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
