×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
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
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
