Re: RPGLE source date & time in *PGM object -- MIDRANGE-L

Thanks Charles! Where did you learn that little nugget of info? And why would IBM leave the old source dates in there? Why have them if you aren't going to maintain them? Or is this something to do with the "marooned modules"?

What about the module creation date? Does that also not get updated? Although that doesn't seem like the case, since the Implementer promotion occurred on 05/04/2021 but the module creation date is the next day, 05/05/2021.

On 6/28/2021 3:27 PM, Charles Wilt wrote:

The source dates don't change if UPDPGM / UPDSRVPGM are used to update a
module in a *PGM or *SRVPGM.

Charles

On Mon, Jun 28, 2021 at 3:11 PM Peter Dow <petercdow@xxxxxxxxx> wrote:

I've depended on a *PGM object's source changed date & time for decades,
especially on systems where customers have not done too well with
keeping track of their source vs object.

Today I came across this:

WRKOBJ PSIWBAPL/PCK222S option 8
================================

Display Object Description - Full
Library 1 of 1
Object . . . . . . . : PCK222S Attribute . . . . . : RPGLE
Library . . . . . : PSIWBAPL Owner . . . . . . . : QDFTOWN
Library ASP device . : *SYSBAS Library ASP group . : *SYSBAS
Type . . . . . . . . : *PGM Primary group . . . : *NONE

User-defined information:
Attribute . . . . . . . . . . . . . :
Text . . . . . . . . . . . . . . . . : RPG : PackList Document
Type select
on
Creation information:
Creation date/time . . . . . . . . . : 05/07/21 07:24:06
Created by user . . . . . . . . . . : MWIPROD
System created on . . . . . . . . . : VISTAPRD
Object domain . . . . . . . . . . . : *USER

DSPPGM PSIWBAPL/PCK222S *MODULE shows
=====================================

Display Program Information

Program . . . . . . . : PCK222S Library . . . . . . . :
PSIWBAPL

Module attributes:
Module . . . . . . . . . . . . . . . . . . . . : PCK222S
Library . . . . . . . . . . . . . . . . . . : QTEMP
Source file . . . . . . . . . . . . . . . . . : QRPGSRC
Library . . . . . . . . . . . . . . . . . . : MODWBSRC
Source member . . . . . . . . . . . . . . . . : PCK222S
Module attribute . . . . . . . . . . . . . . . : RPGLE
Module creation date/time . . . . . . . . . . : 05/05/21 10:21:59
Source file change date/time . . . . . . . . . : 05/28/20 14:35:31
Coded character set identifier . . . . . . . . : 37
Creation data . . . . . . . . . . . . . . . . : *YES
Allow RTVCLSRC (CL module) . . . . . . . . . . : *NO
Sort sequence table . . . . . . . . . . . . . : *HEX
Language identifier . . . . . . . . . . . . . : *JOBRUN
Optimization level . . . . . . . . . . . . . . : *NONE

Note the module creation and source changed dates & times.

STRDBG PSIWBAPL/PCK222S F15 - ILE RPG Listing View
==================================================

Display Module
Source

Program: PCK222S Library: PSIWBAPL Module: PCK222S
19 001800 -* 04/21/2021 P.Dow IT-63684 23732 210421
20 001900 * Added Acom form parameter. 210421
21 002000 * 210421
22 002100
***************************************************************************

000000
23 002200 fOBCOL100 if e k disk 160125

Note the change date on the 3 source lines: 210421 (2021-04-21).

Here's the timeline I've been able to piece together:

1. 04/21/2021: The program was compiled in an Implementer development
environment.

2. 05/04/2021: Using Implementer, it was promoted to a QA environment.

3. 05/07/2021: Using Implementer, it was promoted from QA to production
and distributed to a remote system.

However, the dates still don't make sense. Implementer says the QA
promotion happened on 05/04/2021, but the module creation date is
05/05/2021. And the program creation date is 05/07/2021. And the source
change date is 05/28/2020, yet debug's listing view shows comments from
04/21/2021.

How could this happen?

--
*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
petercdow@xxxxxxxxx <mailto:petercdow@xxxxxxxxx>
pdow@xxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxx> /
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com