Re: Debugging a UDF on V6.1

SBREAK is a command inside a debug session - stands for SEP breakpoint - you use a statement number, then an optional user - it defautls to you. To do stuff for the user associated with CGI jobs, do this kind of thing -

sbreak 664 user qtmhhtp1

Then, when someone comes in from a browser and there's your CGI program, YOU will get a message, with the STRSRVJOB command that you need - Do a SYSREQ 1 to get to another session, run the STRSRVJOB, then STRDBG and set the break point with a normal F6 or BREAK command, go back to the first session, hit enter a lot until you are back to a command line, then go to the second session and wait for things to stop at the breakpoint.

Badabing!

HTH
Vern

On 2/27/2014 1:04 PM, Walter Bellisio wrote:

Sorry, but still not sure what SBREAK is. We have no such object on the system. I though you just ran a STRSRVJOB & STRDBG on one session and then ran the SQL on the other session (the one the STRSRVJOB points to)?

Walter



-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Campin
Sent: Thursday, February 27, 2014 1:56 PM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: Re: Debugging a UDF on V6.1

I should clarify that more. In one session just do a STRDBG and then issue a SBREAK for the line you want to break and your user id. Then in another session, run your SQL. It will break on your previous statement and tell you the STRSRVJOB command to use on another session. Then issue STRDBG in that session.


On Thu, Feb 27, 2014 at 11:46 AM, Walter Bellisio <wbellisio@xxxxxxxxxxx>wrote:

I'm attempting to debug a User Defined Function that uses a service
program to do the work on a V6.1 release. This is the iDate source
downloaded from A. Campin, with the modules, service program and
functions created properly. STRSRVJOB and STRDBG are done on one
session, and a simple STRSQL with a select statement that uses the UDF
is done on the other session that the STRSRVJOB points to. A break
point was set on the first statement of every procedure in both
modules and I can't get a module to stop at any of the break points.
The RPGLE modules of the service program were also compiled with
DBGVIEW(*ALL) and that did not work as well. Has anyone encountered a similar problem?

Walter
--
This is the RPG programming on the IBM i (AS/400 and iSeries)
(RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/rpg400-l.

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.