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



On 5/16/2017 11:35 AM, Dan wrote:

I'm investigating an issue where a line in a source member *must* have been
changed in the past month, but looking at it in SEU shows the line was last
changed in 2014.

I don't know the answer to the direct question as to whether or not RDi
could make an update without changing SRCDAT in the source file.

I know someone could use SQL or DBU, for example, to
change the line without impacting the SRCDAT value, but we're hoping
there's a less "sneaky" reason, perhaps someone monkeyed with their
preferences in RDi and turned it off.

How I've come to loathe SRCDAT:

Day 1:
170102 c eval customer_type = GOOD_CUSTOMER;

Day 2:
170516 c if customer_id = SPECIAL_CUSTOMER;
170516 c eval customer_type = SUPER_CUSTOMER;
170516 c else;
170102 c eval customer_type = GOOD_CUSTOMER;
170516 c endif;

Program runs on Day 2; updates customer type.

Day 3:
170102 c eval customer_type = GOOD_CUSTOMER;

Programmer looks at code on Day 3; determines that it is impossible that
this program has set the customer type to SUPER, but the journal entry
does not lie.

In my own case, it was GOTO...TAG but the general situation remains: It
is absolutely drop dead simple for a non-malicious series of program
changes to result in baffling effects if one /believes/ that SRCDAT
describes *the complete state of the code* at any particular point in
the past.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.