ibmi-brunch-learn

Announcement

Collapse
No announcement yet.

RDI error

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • RDI error

    Hello everyone! 0-)

    Last night I started receiving the error below while working on a Service Program.

    I thought I might have accidentally changed a copybook so that it refers to another which in turn refers to back to the original, but I can't find any loops of that sort.

    Error: com.ibm.etools.iseries.rpgle.DataScope.isRecursive LikedsSource(DataScope.java:1405)

    Has anyone seen this error before? I could not find anything on it.

    Thanks in advance for any insights.

    Walt

  • #2
    Check for recursive d-spec definitions. E.g.
    Code:
    Dcl-S myVar   like(myVar);
    Dcl-Ds myDs   likeDs(myDs);
    I suspect this error would also occur if you have a multi step recursive reference. E.g.
    Code:
    Dcl-S myVar1   like(myVar2);
    Dcl-S myVar2   like(myVar1);
    Given that your error mentions "likeds" It's probably a DS definition.

    Comment


    • #3
      Originally posted by Vectorspace View Post
      Check for recursive d-spec definitions. E.g.
      Code:
      Dcl-S myVar like(myVar);
      Dcl-Ds myDs likeDs(myDs);
      I suspect this error would also occur if you have a multi step recursive reference. E.g.
      Code:
      Dcl-S myVar1 like(myVar2);
      Dcl-S myVar2 like(myVar1);
      Given that your error mentions "likeds" It's probably a DS definition.

      I agree completely that this is related to likeds.

      But I haven't been able to find where I broke it. 0-(

      Thanks for the reply. 0-)


      Walt

      Comment


      • #4
        Very odd....

        I'm back working in that same service program member again today, and RDI is no longer throwing the error.

        Walt

        Comment


        • #5
          Well, I went to lunch and came back...

          ...and now the error has returned, after working on the program all morning without it occurring.

          truly mystifying. 0-(

          Walt

          Comment


          • #6
            ...and today, back to no error.

            Walt

            Comment

            Working...
            X