|
midrange.com
Thank you all... that makes a little more sense now. I've since discovered
that I can create ONE filter that spans multiple source members in multiple
files (e.g. one from QDDSSRC, two from QRPGLESRC, one from QCLSRC, etc.)
which is basically what I was looking for in using projects. I like being
able to organize and easily access all the members I need to modify for a
specific project even though they can be found in more than one library and
source file on our system. It's also useful to create a filter to select
all members for each source file (like PDM) but I don't use that as much as
the project-level view.
"Bruce Guetzkow"
<bruceg@unitedcre
ditservice.com> To
Sent by: <wdsci-l@xxxxxxxxxxxx>
wdsci-l-bounces@m cc
idrange.com
Subject
[WDSCI-L] RE: Source member locks
01/04/2005 11:59 revisited
AM
Please respond to
Websphere
Development
Studio Client for
iSeries<wdsci-l@m
idrange.com>
Ben:
<quote>
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?
</quote>
Yes, as previously mentioned, the iSeries Projects Perspective is
designed specifically for working on source "offline". When you add
source to a project, you are copying the source to your local drive (or
wherever you have specified). That is the copy you are updating. You
must "manually" push the source back to the iSeries. During the push
action, the source member is probably locked, but it is not locked
otherwise.
I have been using iSeries Projects for about 18 months now. I always
"check-out" the production source to my test library, then download it
to a project. This way, the production source never changes, and I am
also the only one who can update the copy in my library. Of course, as
the only developer, there aren't many chances that anyone would update
it anyway, but, you get the idea.
If you are updating production source directly, I'd suggest that you
re-think this process, whether you use WDSc, CODE or any other tool. If
you have a "shared" test library where all source is checked-out into,
you may also want to re-think this process as anyone could update your
source before or after you make your changes.
If it is imperative that you lock the code on the iSeries while actually
making your changes, I'd suggest you access the source member directly
from the Remote Systems view in either RSE or iSeries Projects (by way
of filters as previously suggested). You lose the iSeries Projects
functionality, but you gain the lock.
While this does not solve the locking issue, there is one setting that
may be of some value to you. Go to
Window -> Preferences -> iSeries Projects -> Build and Compile
and click on the "Configure Templates..." button. A window will appear
which allows you to specify a Build Source File and there are check
boxes for
Automatically generate COMPILE.CLLE prior to each build
Automatically push all changed members prior to build
If you are using any build options with your projects, these may help to
push your source.
Hope this helps,
--Bruce Guetzkow
--
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
