RE: Detecting dumps in a CL program?

["Hiebert, Chris" <chris.hiebert@xxxxxxxxxxxxxx>]

I tested with two programs. On V7R3.

I start debug and call TESTH_CL from the command line.


CRTBNDRPG RPGLE program TESTH

**FREE
Ctl-Opt OPENOPT(*NOINZOFL) OPTION(*NODEBUGIO:*SRCSTMT);
Ctl-Opt DFTACTGRP(*NO) ACTGRP(*CALLER);

*INH7 = *ON;
*INLR = *ON;
RETURN;


CRTBNDCL CLLE program "TESTH_CL"

DCL        VAR(&MSGDTALEN) TYPE(*DEC) LEN(5)
DCL        VAR(&MSGDTA) TYPE(*CHAR) LEN(100)
DCL        VAR(&HALTIND) TYPE(*INT) STG(*DEFINED) LEN(2) +
             DEFVAR(&MSGDTA 48)

DCL        VAR(&MSGID) TYPE(*CHAR) LEN(7)

CALL TESTH
MONMSG MSGID(RNX0233) EXEC(DO)

  CHGVAR VAR(&MSGDTALEN) VALUE(%SIZE(&MSGDTA))
  RCVMSG     MSGTYPE(*LAST) RMV(*NO) MSGDTA(&MSGDTA) +
               MSGDTALEN(&MSGDTALEN) MSGID(&MSGID)

ENDDO

ENDPGM



Job log:

CALL TESTH_CL
   109 - CALL PGM(TESTH)
RPG procedure TESTH returned with halt indicator 7 on.
   116 - RCVMSG MSGTYPE(*LAST) RMV(*NO) MSGDTA(&MSGDTA)
  MSGDTALEN(&MSGDTALEN) MSGID(&MSGID)
       - RETURN        /* RETURN due to end of CL program */



Message ID . . . . . . :   RNX0233       Severity . . . . . . . :   50
Message type . . . . . :   Escape
Date sent  . . . . . . :   08/11/22      Time sent  . . . . . . :   16:01:33

Message . . . . :   RPG procedure TESTH returned with halt indicator 7 on.
Cause . . . . . :   The halt indicator 7 in RPG procedure TESTH in program
  PGCH/TESTH was set on and a return was requested.
Recovery  . . . :   Contact the person responsible for program maintenance to
  determine the cause of the problem.


Chris Hiebert
--
Winco Foods, LLC
Applications Development
(208) 672-2047
Chris.Hiebert@xxxxxxxxxxxxxx<mailto:Chris.Hiebert@xxxxxxxxxxxxxx>

From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of James H. H. Lampert via MIDRANGE-L
Sent: Thursday, August 11, 2022 3:31 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: James H. H. Lampert <jamesl@xxxxxxxxxxxxxxxxx>
Subject: Re: Detecting dumps in a CL program?


On 8/11/22 2:14 PM, Peter Dow wrote:

> Which one is the *ESCAPE message?

>

> My guess is the RNX0233 is a *DIAGnositc message.



Actually, it's an escape message sent by the called RPG program *to itself*



To be clear, I am ending the called program (in the test setup, and I'm

pretty sure also in the real world) by setting both LR and H1, and then

doing a RETURN.



Not sure how Chris Hiebert is seeing the RNX0233 from the calling CL

program, and I'm not, given that the calling CL program is essentially

the same code.



--

JHHL