|
Jim, You have to configure a build style because in the architecture of iSeries Projects it is the build style that has the responsibility of providing the code and actions to push the code back to the server. You could just define a no-op command in the build style like DSPLIBL *PRINT if you do not want to do anything. Or you could also just use the Push options and not the Submit Compile option in which case it would not run the command anyway. The idea behind the command was that you would plugin in a call to this CL build program you say you have and be able to run it as part of the process. If you write your program properly, it can even automatically pull back the results after the build completes. Mark wdsci-l-bounces@xxxxxxxxxxxx wrote on 04/20/2004 11:44:26 AM: > 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.