|
Kushal, Thank you very much for the tips. I'm beginning to think that handling database changes and creations will be very tricky anyway. For instance, simply making the changes you described, will logical files compile properly and find the physical file they are to be built over properly. Another example, I'm pretty sure that WDSCi won't know if a physical file already exists or not, how would it know whether to do a CRTPF or a CHGPF? Another question I have is how one might handle a test environment and then rolling all changes once tested into production. This is such an awesome product but I hate flying blind here knowing that other shops must be doing exactly what I need to be able to do. HEHE John. -----Original Message----- From: Kushal Munir [mailto:kmunir@xxxxxxxxxx] Sent: Wednesday, May 12, 2004 10:07 PM To: Websphere Development Studio Client for iSeries Subject: RE: [WDSCI-L] iSeries Navigator View in WDSCi and "Push"ing sourc e files back t o iSeries. John, the way to do this is through compile commands. In Remote Systems Explorer, right click iSeries Objects for the connection you're using, and select Work With->Compile Commands. This dialog lets you associate compile commands with source types. If you select PF and/or LF you'll see the associated compile commands. Here, you can also create your own. Click on New Command, enter a label and the actual command to be executed when this label is selected. You can specify the target library in the command (instead of &O which by default resolves to source library). Note that the label is what you see when you right click a member of that type and go to the Compile or Compile (Prompt) submenu. The label is just an identifier. Once you've created a command (or rather a label for a command), right click on a member of that type (in RSE), and from Compile or Compile (Prompt) menu, select your label to execute the command. Now go back to iSeries projects, right click on project and select Generate COMPILE.CLLE. The build CL picks up the last used command for each member type. If you wanted to use &O, you can change the object library of the connection by right clicking iSeries Objects, selecting Properties and going to the Command Execution page. Set the object library there. This will affect other compile commands and user actions however. If you have dependencies in your script, i.e. you need certain member types to be compiled before others, you can set the ordering through preferences. Look in Remote Systems->iSeries->Command Execution and set the ordering of member types. This is global, i.e. applies to all connections. 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 John Wallroff <jwallroff@founda tion.nebraska.edu To > "'Websphere Development Studio Sent by: Client for iSeries'" wdsci-l-bounces@m <wdsci-l@xxxxxxxxxxxx> idrange.com cc Subject 05/12/2004 05:58 RE: [WDSCI-L] iSeries Navigator PM View in WDSCi and "Push"ing sourc e files back t o iSeries. Please respond to Websphere Development Studio Client for iSeries Thanks Kusal, That was it. Now I have another question. I was able to build my project but our data library is different from the library we put other objects into. Is changing the Build CL that is generated my only option to getting my physical and logical files to compile in the correct library? I'm curious to hear how others handle data file creations and changes with WDSCi. Thanks again everyone. John. -----Original Message----- From: Kushal Munir [mailto:kmunir@xxxxxxxxxx] Sent: Wednesday, May 12, 2004 4:02 PM To: Websphere Development Studio Client for iSeries Subject: Re: [WDSCI-L] iSeries Navigator View in WDSCi and "Push"ing source files back t o iSeries. John, The name of the view is iSeries Project Navigator. The docs on the web are referring to this view. You don't see Push actions if the build style for your project in *NONE. To change the build style for an existing project, right click on it and select Properties. Choose iSeries Build, select one of CL Program or Command build style, then click OK. 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 John Wallroff <jwallroff@founda tion.nebraska.edu To > "'wdsci-l@xxxxxxxxxxxx'" Sent by: <wdsci-l@xxxxxxxxxxxx> wdsci-l-bounces@m cc idrange.com Subject [WDSCI-L] iSeries Navigator View in 05/12/2004 04:51 WDSCi and "Push"ing source PM files back t o iSeries. Please respond to Websphere Development Studio Client for iSeries Hello all, I'm having a bit of trouble working with my first iSeries Project in WDSCi. Through trial and error and looking around the web I've been able to create my first iSeries project, bring source files into it, work with them and put them into CVS and share them with other programmers. The part I'm having trouble with is "Push"ing the files back to the iSeries. All the examples I've seen on the web show a view of "iSeries Navigator". I have "Navigator" and "iSeries Project Navigator" but no "iSeries Navigator" view. "iSeries Navigator" is the view that everyone shows that has the "Push" option. Am I missing a view or is "iSeries Project Navigator" the one I need and I don't have something set up right to "Push" my source files back to the iSeries? Thanks for your help. John. John C. Wallroff Senior Programmer/Analyst IBM Certified AS/400 Programmer UNIVERSITY OF NE FOUNDATION 1010 Lincoln Mall, Suite 300 Lincoln, NE 68508-2886 (402) 472-0109 <mailto:jwallroff@xxxxxxxxxxxxxxxxxxxxxxx> jwallroff@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ 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. _______________________________________________ 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.
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.
midrange.com
