Invoking Screen Designer / Report Designer programmatically - Member locks left

Hi,

we've got a plug-in for RDPower and we invoke the ScreenDesigner/Report
Designer from our code. We do this by using this sort of code:

//get a handle on the source member
QSYSEditableRemoteSourceFileMember qsysFile = ....

// open the Designer
if (designScreen) {
qsysFile.open("com.ibm.etools.iseries.dds.tui.editor.ScreenDesigner",
false, new NullProgressMonitor());
} else {
qsysFile.open("com.ibm.etools.iseries.dds.tui.editor.ReportDesigner",
false, new NullProgressMonitor());
}


This works great to get the Designer to open up. However, after saving the
source changes and closing the Designer, the Designer leaves
member locks behind. Is there a way to get rid of these locks
programmatically? Or should we invoke the Designer in a different way?



regards

JAMES O'SULLIVAN
Senior Technical Consultant
SMART Team Leader
CSC

Royal Pavilion, Wellesley Road, Aldershot, Hampshire, GU11 1PZ, UK.
Financial Services EMEA | p:+44 1252 536681 | f:+44 1252 534022 | m:+44
7827 843323 | josulli4@xxxxxxx | www.csc.com/uk

CSC â This is a PRIVATE message. If you are not the intended recipient,
please delete without copying and kindly advise us by e-mail of the
mistake in delivery. NOTE: Regardless of content, this e-mail shall not
operate to bind CSC to any order or other contract unless pursuant to
explicit written agreement or government initiative expressly permitting
the use of e-mail for such purpose â CSC Computer Sciences Limited â
Registered Office: Royal Pavilion, Wellesley Road, Aldershot, Hampshire,
GU11 1PZ, UK â Registered in England No: 0963578