|
Yes, a source configuration management system :-) In alphabetical order (as not to imply an preference): - Aldon - Concurrent Versions System (CVS) - MKS - Rational ClearCase - SoftLanding There are others but these are the ones I can think of. This also gives you the advantage of tracking changes, etc... The other option is to just export the projects you want backed up to the IFS every night (although you have to remember to do this, but you have to remember to synchronize when using an SCM system too.) Don Yantzi Technical Release Lead WebSphere Development Studio & WebSphere Development Studio Client for iSeries IBM Toronto Lab Phone: (905) 413-4476 IBM internal: IBMCA(yantzi) - Internet: yantzi@xxxxxxxxxx <Rick.Chevalier@xxxxxxxxxxxxxxx> Sent by: wdsci-l-bounces@xxxxxxxxxxxx 12/21/2004 12:57 PM Please respond to Websphere Development Studio Client for iSeries To <wdsci-l@xxxxxxxxxxxx> cc Subject RE: [WDSCI-L] Additional statement numbers iniSeries sourcewith 5.1.2.3 Don, I didn't realize it was creating so much network traffic by using a network drive. This may be beyond the scope of this conversation, but another reason I moved the workspace is that I have started doing some web service projects and it looks like we will be heading in that direction in the near future. It occurred to me during my proof of concept work that the only place the source exists is on my PC. If this was truly a production application I would want it somewhere else for recovery purposes and maybe version control. Because my PC isn't backed up but the IFS is I moved the workspace there to see how it would work. Is there a better solution to what I'm trying to accomplish? Rick -----Original Message----- From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]On Behalf Of Don Yantzi Sent: Tuesday, December 21, 2004 9:34 AM To: Websphere Development Studio Client for iSeries Subject: RE: [WDSCI-L] Additional statement numbers iniSeries sourcewith 5.1.2.3 Rick, Glad to hear that. As a general rule, I would try to avoid using a network drive for your workspace if it can be avoided (I realize in this case you are having some hard disk space issues!) This is main for performance reasons: when you edit a member the RSE downloads it and stores it in this temporary project while it is being edited (the remote member is locked just like SEU.) So in effect you are downloading the member from the QSYS file system to the local PC, then saving it back to the IFS before it is opened in the editor. Every time you save the editor the exact reverse happens. So you are sending the member over the network twice. Don Yantzi Technical Release Lead WebSphere Development Studio & WebSphere Development Studio Client for iSeries IBM Toronto Lab Phone: (905) 413-4476 IBM internal: IBMCA(yantzi) - Internet: yantzi@xxxxxxxxxx Privileged and Confidential. This e-mail, and any attachments there to, is intended only for use by the addressee(s) named herein and may contain legally privileged or confidential information. If you have received this e-mail in error, please notify me immediately by a return e-mail and delete this e-mail. You are hereby notified that any dissemination, distribution or copying of this e-mail and/or any attachments thereto, is strictly prohibited. -- 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.