Re: Source member locks revisited

Hi Ben,

If you want to lock and save members to the iSeries immediately, you should
open the member from the Remote Systems view. You can either create filters
to access members or you can use Ctrl+Shift+I to open a particular member
(or right click iSeries Objects and select Open Member...).

iSeries Projects was meant for local offline editing of source, so it won't
lock members and you have to do an explicit push to send the local changes
to the server. For "live" editing, use the Remote Systems view.

Cheers,

Kushal Munir
Websphere Development Studio Client for iSeries
IBM Toronto Lab, 8200 Warden Ave., Markham, ON
Phone: (905) 413-3118        Tie-Line: 969-3118
Email: kmunir@xxxxxxxxxx



                                                                           
             Ben_Pforsich@bobe                                             
             vans.com                                                      
             Sent by:                                                   To 
             wdsci-l-bounces@m         wdsci-l@xxxxxxxxxxxx                
             idrange.com                                                cc 
                                                                           
                                                                   Subject 
             01/04/2005 10:15          [WDSCI-L] Source member locks       
             AM                        revisited                           
                                                                           
                                                                           
             Please respond to                                             
                 Websphere                                                 
                Development                                                
             Studio Client for                                             
                  iSeries                                                  
                                                                           
                                                                           








I know this topic has been brought up before, but I could find a solution
to my problem in the archive lists or in the online help.  My problem is
that I cannot get WDSC to behave like CODE did when it comes to locking my
source members and saving them instantly on the 400.  I just upgraded to
WDSC 5.1.2.3 on my Windows 2000 (SP4) machine, but I've been using previous
versions of CODE for a couple years now.  We're on V5R2 with all the
appropriate PTF's applied (I think).

This is what I'm trying:
I create an iSeries project and set the associated library to an existing
library.  (I've tried all three different build styles and I've discovered
that it won't let me push changes down if I selected the *NONE build
style.)
I then import existing source members into my project.
I make changes and save them, but they're only being saved locally.  I have
to push the changes down to update the source member, but still no locks
are placed.  Anyone can come along and edit the source on the 400
and--Viola!--we now have conflicts.

My questions are:

How do I get WDSC to lock my source member when I open it just like CODE
did?
How can I get it to automatically push my changes down everytime I save the
source like CODE did?

Is there something I'm missing here?

Thanks for your help,

Ben Pforsich
Programmer Analyst
Bob Evans Farms, Inc.
I/S Department
Columbus, Ohio
Ben_Pforsich@xxxxxxxxxxxx

--
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.