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



When I have opened a source member (for editing) in the LPEX editor, and 
close the member again, then the source change date/time (on the server) 
is modified, even if no changes have been made to the source. Therefore, 
we often run into the following situation:

We open a member in the LPEX editor, we make some changes to the source, 
we save the changes, we compile the member, we do some testing, we close 
the member (because no further changes are needed). Now, when we want to 
transfer the modified object to the test environment, our software change 
management product (Tight as a Drum, marketed by Unbeaten Path 
International) checks if the change date/time of the source member matches 
with the source change date/time information that is contained in the 
object. (This is a reasonable check, because it prevents that the object 
is not in line with the source.) Because the source change date/time was 
changed by WDSCi on the last closing of the member, an error is signalled. 


This is a bit annoying. We now have to first close the member, and then do 
the compile (from the Remote Systems view, or from the iSeries Table 
view). Everytime we forget this, an error is signalled upon transfer to 
the test environment, and we have to compile the source again.

Is there a way to prevent the update of the source change date/time when 
no actual changes have been made to the source member? 

Ewout

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.