|
midrange.com
There are two views -- the plain Navigator and the iSeries Project
Navigator. The plain Navigator shows exactly those files that are in your
workspace. The iSeries Project Navigator is a "filtered" view that shows
only iSeries projects. The workbench can host many different kinds of
projects, webfacing projects, java projects, ..., but if you're just using
iSeries Projects I can see how the difference can be confusing since the
views would show the same things. In the iSeries Projects Navigator you
can get a combined view of the local and remote resources of the system --
something that's not possible in the plain Navigator. It also hides some
of the special files that are kept around in your project in order for
attributes to synchronize properly with the target system -- stuff like
member text or source file record lengths.
The "command" build style sounds like its something you could use. It
simply runs a command of your choice when you use the "submit build"
operation. If you already have a program you call to build your stuff, you
can use a call command to invoke that program and build your project.
The command or program doesn't run when you do the push -- it runs when you
do a "submit build". So, you can edit and push changes all you want and
when you've got it the way you want, do the "submit build". You can
configure the command build style to do a "push changes" automatically
before it submits the command. So the "build" can automatically do a
"push", but a "push" never does a "build".
The push operations are "contributed" by the build style. IBM provides a
couple of these. Other vendors can hook in and provide their own build
styles as well. They can then tailor their push operations to provide
extra function over what IBM provides.
_______________________
David Dykstal
david_dykstal@xxxxxxxxxx
Jim Essinger
<esinger@xxxxxxxx
> To
Sent by: Websphere Development Studio Client
wdsci-l-bounces@m for iSeries <wdsci-l@xxxxxxxxxxxx>
idrange.com cc
Subject
04/20/2004 10:44 Re: [WDSCI-L] Why can't I push my
AM source file changes?
Please respond to
Websphere
Development
Studio Client for
iSeries
David,
Thanks for your response. I have two projects, one that was created before
I upgraded, and I was able to push then. I have the new one I created
after I upgraded, and I was not able to push on the new project, and was
not able to push on the old project. I have since discovered there are two
views in the project, iSeries Project Navigator, and just the
Navigator. The option for the iSeries Build Style is only available in the
properties thru the iSeries Project Navigator view. They are so similar
that they confused me. I don't really know what the difference is. I
found there that the build style was not defined. I chose command, and
after putting a command in the prompt, I had the ability to push my
changes. It only took me 2.5 hours to get this working.
I question the need to have a command or program HAVE to run. I have not
done a lot of off line programming, because I think there are some things
lacking yet in the tool, such as archiving the database, printer file,
display file information so that I can view properties and fields, as well
as verify to those compiled objects. I would like drag and drop
capabilities with the field names, and the alias field names when looking
at the file information.
The reason I question the _NEED_ to have a command or program run is I have
a build CL on the iSeries that I use after I have the source updated, and
have done several other setup things. Can I tell the build style (now that
I know where it is!!) that I don't want a command to run when I push the
changes? All I want to do is put the changes back on the iSeries in the
original source files I took them from.
Jim
At 06:20 AM 4/20/2004, you wrote:
>If the iSeries build style properties are completely missing it sounds
like
>there might be a configuration problem that is causing the remote build
>plugin not to be recognized. This would also account for the missing menu
>items. Is there anything in the .log file from .metadata directory in
your
>workspace that might indicate that?
>
>Did you upgrade to 5.1.0.2 before or after you created this particular
>project?
>_______________________
>David Dykstal
>david_dykstal@xxxxxxxxxx
>
>
>
> Jim Essinger
> <esinger@xxxxxxxx
> >
To
> Sent by: wdsci-l@xxxxxxxxxxxx
> wdsci-l-bounces@m
cc
> idrange.com
>
Subject
> [WDSCI-L] Why can't I push my
> 04/19/2004 05:50 source file changes?
> PM
>
>
> Please respond to
> Websphere
> Development
> Studio Client for
> iSeries
>
>
>
>
>
>
>I created a project, downloaded some source code to the project and worked
>on the source while off line. Now I want to push the changes to the
>iSeries and compile them. Before I upgraded to 5.1.0.2, the options were
>there to push my source code to the associated library. Now the push
>options are not there. I have done this before. What changed??? How do
I
>
>get my source code back to the iSeries so I can compile? Why does this
>have to be so stinking hard to do??
>
>
>Any help would be appreciated.
>
>
>I have looked at help, and it says to right click on the project, go to
>properties and select the iSeries Build Style. I don't have that option
in
>
>my properties. I have Info, External Tools Builders, Iseries Projects
>(which shows the correct connection and associated library), Links
>Validation/Refactoring, Project References, Server Preference, and
>Validation.
>
>----------------------------------------------------------
>
>Jim Essinger
>Senior Programmer/Analyst
>UnLtd / SLFI / IMA
>PO Box 730
>Fruitland, ID 83619
>
>208-452-4058 Extension 133
>esinger@xxxxxxxx
>
>------------------------------------------------------------
_______________________________________________
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.
