sponsored links

Collapse

Announcement

Collapse
No announcement yet.

JAVA and commitment control lockin record

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

  • JAVA and commitment control lockin record

    I have a JAVA connection adding a record to a file on the iSeries under commitment control, but the server side program (COBOL) cannot access the record as it is locked. This is all within the same server job. The JAVA developer doesn't want to commit until his work and the server work is completed.

  • #2
    I'd guess the problem is that the Java code actually runs in PASE rather than ILE (or OPM) where the COBOL runs.

    Comment


    • #3
      It seems like a GOOD thing that you can't access a record that hasn't been committed...

      Comment


      • #4
        Originally posted by Scott Klement View Post
        It seems like a GOOD thing that you can't access a record that hasn't been committed...
        Not really, as this is all within the same job. The JAVA process connects to the iSeries in QUSRWRK/QZDASOINIT , clears an iSeries file, then adds a record to it - then calls an RPGLE stored procedure, it tries to read the record to update it, but it hangs because the record is locked.

        Comment

        sponsored links

        Collapse

        Working...
        X