Re: Opening a member for edit in both WDSC and CODE at the same time.

Don,

I am reasonably sure that is not what Clauss and I were seeing at COMMON. 
He has the lab sheet as to how to duplicate the problem.
I'd have to look further at the details as to whether or not Craig's issue 
was similar.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





Don Yantzi <yantzi@xxxxxxxxxx> 
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
05/25/2004 08:12 PM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
cc

Subject
Re: [WDSCI-L] Opening a member for edit in both WDSC and CODE at the same 
time.










Rob,

CODE and WDSc use different server jobs and each have unique locks.  When
you open a member in WDSc the member is locked on the iSeries just as it 
is
locked with SEU or CODE.  However if you disconnect the RSE connection or
shutdown the workbench then the lock is released.  When you restart WDSC
the workbench automatically reopens all editors that were open on 
shutdown,
however the RSE does not try to reconnect to the remote system and re-lock
the member until the first time you save any changes.  I believe this is
the scenario outlined in the link below.

You can prevent the workbench from re-opening editors on startup using the
Workbench > Editors preference page (select the "Close all editors on 
exit"
preference.)

Please let us know if you are seeing different behaviour than this.

Thanks.

Don Yantzi
WebSphere Development Studio Client for iSeries
IBM Toronto Lab
Phone: (905) 413-4476
IBM internal:  IBMCA(yantzi)  -  Internet: yantzi@xxxxxxxxxx



 
             rob@xxxxxxxxx 
             Sent by: 
             wdsci-l-bounces@m                                          To 

             idrange.com               Websphere Development Studio Client 

                                       for iSeries <wdsci-l@xxxxxxxxxxxx> 
                                                                        cc 

             05/25/2004 02:27 
             PM                                                    Subject 

                                       [WDSCI-L] Opening a member for edit 

                                       in both WDSC and CODE at the  same 
             Please respond to         time. 
                 Websphere 
                Development 
             Studio Client for 
                  iSeries 
 
 




Clauss,

Based on that little incident at COMMON in which I was able to open a
member, for edit, in both WDSC and Code/400,
and, based on this old posting:
http://archive.midrange.com/wdsci-l/200401/msg00267.html
this doesn't sound like anything new.

Let me guess, they both get piped through the same server job?  Thus it
thinks the only lock is itself?

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

_______________________________________________
This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.


_______________________________________________
This is the Websphere Development Studio Client for iSeries  (WDSCI-L) 
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.