Re: Service break reasoning

I don't use SBREAKS, but instead use Service Entry Points from within RDi. You can debug anything from there, as long as the language is an ILE language. That includes CLLE.

Mark Murphy
STAR BASE Consulting, Inc.
mmurphy@xxxxxxxxxxxxxxx


-----Thomas Garvey <tgarvey@xxxxxxxxxx> wrote: -----
To: "RPG programming on the IBM i (AS/400 and iSeries)" <rpg400-l@xxxxxxxxxxxx>
From: Thomas Garvey <tgarvey@xxxxxxxxxx>
Date: 03/17/2016 12:53PM
Subject: Service break reasoning


Hi, everyone,

I suspect most of us here are familiar with setting service job breaks
for batch jobs that need to be debugged.
One thing that has always annoyed me is the inability to set this type
of break in a CL program that happens to be the controlling program of a
procedural process that needs this debugging technique.
When trying to set up the service job break, using SBREAK in the CL
program initially results in a syntax error.
But when an RPGLE program that gets called by the CL program is instead
set up with the initial SBREAK,
I am allowed to add the CL OPM program to the debugged program list and
set further SBREAKs in the calling CL program.

Seems like the debugging process is capable of setting SBREAKS in CL OPM
programs, so why is it disallowed when the CL OPM is the original program?
Is it that further SBREAKs aren't really service breaks, just normal
breaks since the job is already being serviced?

Just a curiosity that I wonder if anyone can explain well.

Thanks,

Tom Garvey