Skip to Content
author's profile photo Former Member
Former Member

Exception in Substep End Routine how to see which record is causing it?

Hi Folks,

a load fails. I know which code portion and most probably why. However, I struggle to determine the record. My debugging skills are limited to looping thru the end_routine loop but this would been doing 20k clicks :-(

Monitor says something about superordinate nodes of monitor that would show which data record etc.

Can anybody tell me where to find those?


Or any other way to hunt down the issue record?


Thanks and best regards,

Axel

Error_Capture.JPG (79.6 kB)
Add a comment
10|10000 characters needed characters exceeded

Related questions

4 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Jul 19, 2016 at 06:02 AM

    Thanks for all replies so far.

    Issue appears in test system therefore modifications to code are not possible.

    I will try watchpoints / data package reduction.

    Anybody knows the superordinate node of the monitor (which is mentioned in the error message)?

    Thanks and best regards,

    Axel

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jul 18, 2016 at 02:51 PM

    If you had a runtime error I would assume you find a dump in ST22?

    If yes, then the code line is marked any you see the specific variables with their values.

    If not, I recommend you google how to work with "Watchpoints" and try to find it in this way in the Debugger.

    Should your number really be *6158 then you should include a general coding which replaces "strange chars" like ! or # or * by space.

    BR, Martin

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jul 18, 2016 at 06:43 PM

    Hi,

    There are several ways out.

    1, As Martin pointed out check for the errors in ST22.

    2. Also make use of " MONITOR_REC" which is the part of end routine. Here using it you can track the success records and the point of failure.

    3. Another way, i would rather say a painful way is to just create a "Z*" table and keep updating the records, every successful record would store there and make sure you sort before the data load.

    4.One more way(less painful) is to, reduce the package size to 200 and run then you will be able to easily identify the failure.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jul 23, 2016 at 10:53 AM

    Hi, Did you find a way out to solve?

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi,

      yes - with the reduction in data package size I was able to debug a bunch of records.

      And there I saw that a date was empty and causing an issue in an calculation date1 - date2

      Thanks for all replies !

      Axel

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.