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



Thanks David.  I had noticed that in some situations the source changed date & time matched the restored date & time of a program.  In those situations, it was the restored date & time that was correct, so something had changed the source changed date & time to match.  Not sure why or under what circumstances.

I remember Leif Svalgaard had a CHGMBR command to change the source date & time of a file member that was written in MI.  APIs would seem a lot safer, but if they're putting incorrect data in there, it doesn't help much.


On 6/29/2021 7:05 AM, David Gibbs via MIDRANGE-L wrote:
On 6/28/21 7:27 PM, Peter Dow wrote:
I did use Implementer's job log inquiry, and it shows it using CRTBNDRPG.

I did find a source member with matching date & time on a different system.  But even if it were restored from that system, the WRKOBJ doesn't show a restored date, and it doesn't explain why the debug list view shows source from almost a year later.

My understanding is that the ILE Listing View in debug is part of the *PGM object, added when it was compiled.

IIRC, there are some API's used to manipulate source references, when Implementer promotes program objects, to keep things in sync.

I would suggest you contact Implementer support to help track down what's going on.

david



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.