#146 Locking a source despite selecting the browse mode

[Melina Theiler]

Hello there,
I am using the iSphere plugin in RDi to compare sources. This works very well!
But apparently the source is locked if I already have a source open for editing. This would be fine if I opened the compare in edit mode, but I compare in browse mode.
I have uploaded two images, one is the window with my selections for comparison (iSphere_Selection_Window.png) and the other is the error message from the lock (iSphere_Lock_Window.png).

I am using RDi version 9.8.0.0 and iSphere version 5.2.9.r.

Please feel free to contact me if you have any questions!

Thanks for your support

Melina

[Thomas Raddatz]

Hi Melina,
May you please retest that one more time? I cannot reproduce the problem. Here is how I tested the case you reported:

1. Ensured that the source members that I want to compare are unlocked. (command: WRKOBJLCK, members DEMO1 and DEMO2 of file QRPGLESRC in library ISPHERE)
2. Selected both members and selected "iSphere Compare Editor" from the context menu.
3. Selected "Open for edit".
4. Member DEMO1 (left member) is locked, member DEMO2 (right member) is unlocked.
5. Closed the compare editor.
6. Ckecked that both members are unlocked.
7. Started over and selected "Open for browse".
8. Both members are unlocked.
9. Closed the compare editor.

I debugged the whole stuff and the code that locks the member is executed only in case the member is opened for edit.

Is it possible that the member was locked before you started the compare editor? If there is no crash, the lock is removed from the member at the time the editor is closed.

The lock is also removed, when I kill RDi with the windows task manager.

[Thomas Raddatz]

I get the "Member ... is locked by job ..." message only when I have the member open in an RDi or SEU editor and if I select "Open for edit" on the "Compare Source Members" dialog.

See screenshot: Thomas_Member_locked_message.png

[Melina Theiler]

Hi Thomoas,

Here is how I get the message:

1. Open SOURCE_A in edit mode with RDi
2. Open the iSphere compare for browse (via RDi, attachment "iSphere_open_comparison.png")
3. On the left side SOURCE_A
4. On the right side SOURCE_B
5. Have a look at the changes and edit SOURCE_A which I have opend before (and not the source in the iSphere comparison)
6. When saving the edited source, the lock appears
   The lock is also created when I close the comparison before saving

hopefully, that description will help a little bit more :)

Melina

[Thomas Raddatz]

Hi Melina,

Thanks to your great explanation I was able to reproduce the error. It is definitely not iSphere that locks the member, because I can open DEMO1 for edit in one RDi and at the same time start the compare editor for DEMO1 and DEMO2 in a second RDi and save changes to DEMO1 in the first RDi.

So there is definitely no lock on the IBM i.

Next I get the error, when I open DEMO1, then start the compare editor and then attempt to save my changes to DEMO1. (one RDi)

But I do not get any error, when I start with the compare editor and then open DEMO1 for edit and then save my changes. (one RDi)

Honestly I do not yet have an idea what goes wrong. At the moment my best bet is that job QRWTSRVR is the problem. I will post to the WDSCI-L mailing list and I consider opening a case at IBM. I'll keep you posted.

Thomas.

[Melina Theiler]

Hi Thomas,

I am curious and thank you for your help!

Melina :)

[Thomas Raddatz]

Figured out, that the QRWTSRVR server job is the problem. When I use one RDi with different connection, two QRWTSRVR are started and I can successfully save DEMO1 while the compare editor is open. So the assumption is, that the QRWTSRVR holds something like a "soft lock" that is not shown at the output of the WRKOBJLCK command.

Melina, may you please confirm that?

You need to create two remote connection with different host names. That is important!
Example, I created two remote connections with the following remote names:

• dev.de.obi.net (open for edit)
• DEVSYSTEM (compare editor in browse mode)

Both DNS names resolve to the same IP address. RDi appears to start one QRWTSRVR server job per host name.

[Thomas Raddatz]

Also figured out that it works, when I open DEMO1 for edit in the LPEX editor and then start the IBM compare editor for DEMO1 and DEMO2. The IBM compare editor is in edit mode by default. Although I used one remote connection I can transparently save changes in the LPEX editor or the compare editor. The contents of the editors are updated at the time the content is saved.

[Thomas Raddatz]

Conclusion: It does not make sense to open a case at IBM. We need to figure out what IBM does under the cover and change our source code accordingly.

[Melina Theiler]

Hello Thomas,

I can confirm the scenario (with the two connections) you described.

Melina

[Thomas Raddatz]

Hi Melina,

I seems as I could fix the problem. At least it does no longer happen with my changes. Once that my changes have been reviewed, I can create a new beta version. A new release will take some more time, because the latest enhancements have not yet been thoroughly tested.

Thomas.

[Melina Theiler]

Hello Thomas,

that sounds very good! Thank you for your help and support and I am looking forward to the new release :D

Melina

[Thomas Raddatz]

Hi Melina,

It took some time, but the problem has been fixed with iSphere 6.0.2, that has been released a few days before. It took that long due to the new iSphere Synchronize Members editor, which was a more work than expected.

Regards,

Thomas.