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



Green screen debugging works.

With positioning the cursor and pressing F11:

If I put the cursor anywhere on OutA I get the everything for entry 1 of the array, including OutA.Units(1,1), OutA.Units(1,2), thru OutA.Units(1,12). Very complete.

If I put the cursor on In.QTYSH or In.Mth the variable is shown. (I'd expect that.)

If I put the cursor anywhere in (1).Units it does EVAL Units(In.Mth) and says Identifier does not exist. (Seems reasonable since positioning the cursor isn't exactly precise.)

It also works if I key in the EVAL statement:

If I enter EVAL OutA(1).Units(In.Mth)it shows me the correct single entry in Units.

If I enter EVAL OutA(1).Units it shows me the 12 array elements of Units.

So it looks like the OS/400 debugger is pretty good about evaluating complex expressions and there is a problem in RDP 8.5.

If it is fixed in RDP 9 I'll go beat on our BP to get it (if I can find time...)

Sam

On 9/1/2013 7:35 PM, Mike Hockings wrote:
I believe that the expression evaluation is done by the debugger on the
IBM i. You could confirm that by debugging in the green-screen and trying
the same expression...

Mike


Mike Hockings, M.Eng., P.Eng.
IBM Rational Developer for System z and Power Systems Software Technical
Support


From: Sam_L <lennon_s_j@xxxxxxxxxxx>
Subject: [WDSCI-L] DBGE0001E Expression xxx is too complex
I'm running RDP 8.5 against OS V7R1.

I have a line of code that says:
OutA(1).Units(In.Mth) += In.QTYSH;

In a service entry point debug session, when I hover anywhere over the
left hand side it get a Debug Engine Message:

DBGE0001E Expression OutA(1).Units is too complex.

I see a report of something similar back in WDSc and it looks like also
in 8.5.

(Trying to monitor OutA doesn't work either.)

Anyone know if this fixed in 9.0? Or is it a restriction on the
underlying debug engine in OS/400?

Thanks, Sam


The definitions are like this:
*=== Template for PSA100 records ==============================
ddsPSA100OUt E DS EXTNAME(PSA100:*OUTPUT)
d qualified
d Itnbr 13 overlay(dsPSA100Out:9)
d Units overlay(dsPSA100Out:22)
d like(SUNT01)
d dim(12)

*=== Arrary of PSA100 Record are built here ===================
d OutA ds likeds(dsPSA100Out)
d dim(99)


As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.