Re: Source in IFS

My own preference is to stay in the library structure for source as well. Since the tooling for dealing with those type of objects is more mature and well understood by the IBM i community, it only makes sense to keep source in the QSYS.LIB file structure, but there are those that prefer to mess around with the directories. Then again for languages like PHP that must live in the IFS, you need to have back up and recovery procedures set up to keep them in synchronization as well. That's one reason I really like BRMS for back ups, it's easy to do stuff like that.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 2/19/2013 1:33 PM, David Gibbs wrote:

On 2/19/2013 1:15 PM, Jim Oberholtzer wrote:

> I'm not recommending it nor against it, just pointing out that it is
> done now and a plan for the directory structure needs to be in place.
> One might consider making sure the backups are altered to ensure this
> change does not catch directories from being backed up. Making sure the
> Asynchronous fetch is in place for back up as well.

OK, I was misinterpreting what you wrote.

FWIW: None of the source analysis tools I am aware of can deal with source in IFS. Unless there a driving need to put source in IFS, I would advise against it.

david


-- IBM i on Power Systems - For when you can't afford to be out of business