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



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> /

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.