I am not interested in it being in the load module (or program object), though 
that may be useful for things other than what I am specifically concerned 
about.  I am interested in it being in the directory (be it PDS or PDSE).

Here is my specific concern.  If a new module is to be implemented today 
(though perhaps bind/linked prior to today and then copied in to the load 
library today) I want to be able to verify for sure that it was done.  
Sometimes our production migration process has failed in that the actual of the 
load module to production was forgotten, or somehow failed, or something.  In 
VSE I can do this:

// EXEC LIBR
LISTD SUBLIB=USER.PROD                      
/*                                          

And I get a nice report of the members in the USER.PROD VSE library, like this:

--------------------------------------------------------------------
DIRECTORY DISPLAY    SUBLIBRARY=USER.PROD           DATE: 2010-05-21
                                                    TIME: 18:41     
--------------------------------------------------------------------
 M E M B E R      CREATION   LAST     BYTES    LIBR CONT SVA  A- R- 
NAME     TYPE     DATE      UPDATE   RECORDS   BLKS STOR ELIG MODE  
--------------------------------------------------------------------
ACCTCHEK PHASE    02-02-20 08-06-04  35984 B      37 YES  NO  31 ANY
ACCTNO   PHASE    08-07-31 09-02-26  21080 B      22 YES  NO  31 ANY
ACDSTAT1 PHASE    03-06-13   -  -    12344 B      13 YES  NO  31 ANY
ACDSTAT2 PHASE    03-06-13   -  -    54064 B      55 YES  NO  31 ANY
ACHCVT   PHASE    07-07-25 07-08-28  24688 B      25 YES  NO  31 ANY

Is that not very useful?

Frank
-- 

Frank Swarbrick
Applications Architect - Mainframe Applications Development
FirstBank Data Corporation - Lakewood, CO  USA
P: 303-235-1403


On 5/21/2010 at 4:03 AM, in message
<20100521111948.538d8f58...@smtp.patriot.net>, "Shmuel Metz (Seymour J.)"
<shmuel+ibm-m...@patriot.net> wrote:
> In <4bf49653.6f0f.008...@efirstbank.com>, on 05/20/2010
>    at 01:53 AM, Frank Swarbrick <frank.swarbr...@efirstbank.com> said:
> 
>>I find it perplexing, though, that there is apparently no field in a
>>load module PDS that indicates when a member was created and/or last
>>updated. 
> 
> What are IDRDATA, chopped liver?
> 
>>Why is it there for non-load module PDSs
> 
> It isn't. Not all members are created by ISPF.
> 
>>but not for load module PDSs?
> 
> It's been in load modules for around 4 decades. In fact, I believe
> that IDRDATA is older than SPF. Anyone have the exact dates?

>>> 

The information contained in this electronic communication and any document 
attached hereto or transmitted herewith is confidential and intended for the 
exclusive use of the individual or entity named above.  If the reader of this 
message is not the intended recipient or the employee or agent responsible for 
delivering it to the intended recipient, you are hereby notified that any 
examination, use, dissemination, distribution or copying of this communication 
or any part thereof is strictly prohibited.  If you have received this 
communication in error, please immediately notify the sender by reply e-mail 
and destroy this communication.  Thank you.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to