Source line change dates - IFS vs source physical files -- WDSCI-L

× 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.

Subject: [WDSCI-L] Source line change dates - IFS vs source physical files
From: rob@xxxxxxxxx
Date: Tue, 3 Jun 2003 09:46:17 -0500
Cc: Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
List-archive: <http://archive.midrange.com/wdsci-l>
List-help: <mailto:wdsci-l-request@midrange.com?subject=help>
List-id: Websphere Development Studio Client for iSeries <wdsci-l.midrange.com>
List-post: <mailto:wdsci-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/wdsci-l>,<mailto:wdsci-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/wdsci-l>,<mailto:wdsci-l-request@midrange.com?subject=unsubscribe>

I wondered if the line change dates were a property of source physical 
files, or the property of the editors involved.  Your remark seems to 
indicate that it is a property of the editor itself.

That being so, then there is no reason that IBM couldn't fix the fact that 
storing source in the IFS doesn't currently support line change dates.

<snip>
The things I like about ... CODE ... it does maintain the SEU line change 
dates ...

Bob Cozzi
Cozzi Consulting
www.rpgiv.com
<endsnip>


Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin

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.