× 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.




Does the issue persist if you use a new workspace? I have seen this happen
with damaged workspaces.

Mike

Mike Hockings, M.Eng., P.Eng.
DevOps for Enterprise
IBM Developer for z Systems and Power Systems Software Technical Support
IBM Canada Ltd. Laboratory
hockings@xxxxxxxxxx
voice 1-905-413-3199 T/L 313-3199 ITN 23133199




From: "Tyler, Matt" <matt.tyler@xxxxxxxxxxxxxx>
To: "Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries" <wdsci-l@xxxxxxxxxxxx>
Date: 2018/08/14 10:19
Subject: Re: [WDSCI-L] RDi Debug problem?
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>



I have had issues since 9.6.x debugging with break points. When I need to
set break points I use STRDBG. I have yet to put in a PMR or document any
reason for my problem. Other in my work place at 9.6.x with the same
plugins are not experiencing the same problem. I have debug break point
problems with all programs without the DUMP op-code.

-Matt

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Brian
Parkins
Sent: Tuesday, August 14, 2018 3:39 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for
System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: [WDSCI-L] RDi Debug problem?

Recently, Barbara Morris submitted RFE 123323,

https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=123323


regarding RDi debug. Out of curiosity I copied and modified the code sample
as follows:

**Free
   dcl-s a_job char(3) inz('a!b');
   dcl-s a_37 char(3) ccsid(37) inz('a!b');
   dcl-s a_500 char(3) ccsid(500) inz('a!b');
   dcl-s a_utf8 char(3) ccsid(*utf8) inz('a!b');
   dump(a);          // Breakpoint set here (1)
   a_job = 'ABC';    // Breakpoint set here (2)
   *InLR = *On;
   return;

I found an odd inconsistency in RDi debug. I set two breakpoints (1) and
(2) above. When the program was run under RDi (SEP) debug, it halted at
(1). When Resume or Step Into were invoked, the program continued to run to
termination.
The same program with the same breakpoints was run under the host debug
facility, (STRDBG).  Execution halted at (1), but when Resumed/Stepped, the
program to halted at (2) - as expected.

It would appear that the RPG IV DUMP opcode causes the RDi debug to
terminate program execution prematurely, ignoring subsequent breakpoints or
statement stepping.

Running RDi 9.6.0.4 - anyone else experience similar?

Brian.
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list To post a message
email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list
options,
visit:
https://lists.midrange.com/mailman/listinfo/wdsci-l

or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/wdsci-l
.
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/wdsci-l

or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
https://archive.midrange.com/wdsci-l
.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.