× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.




"WARNING, WARNING, DANGER WILL ROBINSON!"  (arms flailing wildly)

Please note that when you put source code in the IFS, you lose one of the most important features of OS/400, IMHO, that *PGMs and *MODULEs carry with them the name of the source file, library and member name and date/time stamp for the primary source member from which they were created. That feature has "saved" many companies in identifying the "correct" source for objects in "production" use. No other platforms have this feature built-in -- it is unique to i5/OS and OS/400, to my knowledge.

IBM mainframe customers license expensive ISV products to add this functionality to the operating system.

Sincerely,

Mark S. Waterbury

> Violaine Batthish wrote:
Hi Arco,

You are correct that iSeries project do not currently support IFS.
IFS support is on the list of requirements for iSeries projects.

thanks,

Violaine Batthish
WebSphere Development Studio Client, IBM Toronto Lab



wdsci-l-bounces@xxxxxxxxxxxx wrote on 09/20/2006 10:37:18 AM:

   Hi Michael,

   >Thanks for straightening me out on the SRCSTMF parameter.  I'm sure
it
   >wasn't added after I sent my post <grin>.  I just never looked that
   >closely.  Out of curiosity, what benefit do you see in using the IFS
for
   >source?

   A very simple reason/benefit. I'd like to use an open source Version
   Control system (Subversion) with it.
   Subversion only operates on the "normal" filesystems.

   I'm aware that putting my source on the IF causes the loss of member
text
   and source type, and not to forget the source lines change date and
   sequence.

   But when an iSeries Project imports sources from the original source
   members under the QSYS system, the project keeps track of this member
text
   and source type in separate metadata files. That way, when the project
   sourcemember is pushed back to the original sourcefile, the stored
text
   and sourcetype are reset. So there are possibilities to keep track of
the
   same thing for IFS sources.

   But for me, keeping these properties would not be very important. For
   example, in other programming languages we don't have text
descriptions on
   the sources at all, so personally I don't care if I lose them.

   The most important thing would be the possibility to import an IFS
source
   in a WDSC project, and have the possibility to do the same thing with
it
   as I can do with source members. But as far as I can see this is not
   possible now.

   Best regards,
   Arco Simonse



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.