Re: RPGLE source date & time in *PGM object

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