Re: Dump reports calling proc

Yes fixing the error with some logic is no problem.

The dump in QEZDEBUG shows as being Statement in Error . . . . . . . . . .
: 00005200

The JOBLOG does indicate the actual failing line number
Application error. MCH1210 unmonitored by R0307JX at statement
0000009525, instruction X'0000'.



On Tue, Sep 4, 2018 at 9:51 AM Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:

Well there are multiple options - the first being to handle the error
within the procedure itself. Monitor block or the relatively new on-exit.

Are you sure though that there is no mention of the failing line in the
log?


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Sep 4, 2018, at 9:02 AM, Steve Jones <sjones@xxxxxxxxxxxxxxx> wrote:

I had a program fail & I "D"umped it. The reported dump shows the

calling

procedure as what failed, but what really failed was a line of called

that

is in another proc, that is called from the proc that the dump reported,
not very helpful.

What do I need to change so that it would have reported the line of code
that actually caused the failure?

In the below example the dump would report DoSomething as the failing

line,

but really it was in the proc NextThing.

Dou %Eof(x);
Read x;
If Not %Eof(x);
DoSomething();
Endif;
Enddo;

Dcl-proc DoSomething;
NextThing();
End-proc;

Dcl-proc NextThing;
Actual failing line of code;
End-proc;
--
Steve Jones
H-P Products, Inc
330-871-2054

--
NOTE: The information in this email is confidential and may be legally
privileged. If you are not the intended recipient, you must not read,

use

or disseminate the information; please advise the sender immediately by
reply email and delete this message and any attachments without

retaining a

copy. Although this email and any attachments are believed to be free

of

any virus or other defect that may affect any computer system into which

it

is received and opened, it is the responsibility of the recipient to

ensure

that it is virus free and no responsibility is accepted by H-P Products,
Inc. for any loss or damage arising in any way from its use.
--
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: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related

questions.

Help support midrange.com by shopping at amazon.com with our affiliate

link: http://amzn.to/2dEadiD

--
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: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD