Why are the ++PROGRAM binder dates different from ++MOD binder dates when installing RO73025?

book

Article ID: 40675

calendar_today

Updated On:

Products

CA Gen CA Gen - Build Tool CA Gen - Workstation Toolset CA Gen - Host Encyclopedia CA Gen - Run Time Distributed 3RD PARTY TSO

Issue/Introduction

Question: 

Why are the ++PROGRAM and the ++MOD element binder dates not the same when installing RO73025? 

The two ELEMENT TYPEs that I am questions are on ++PROGRAM and are in SYSMOD RO73025. These are the two modules in question: 

1. TIRTROFF 

2. TIRUNST 

I'm used to seeing members in a load library being identified as a MOD 'ELEMENT TYPE' with the member name 'LOAD MODULE' and the library name 'LMOD SYSLIB'. The binder link date for these two elements are different than the other elements in the CEHBPLD0 library. The binder link date for these two elements is 2014.233 and the link date for other elements in the same library that were included in the same install is 2014.328. 

I excepted the binder link date for the two ELEMENT TYPEs in question to be 2014.328. Please let me know why the element binder dates for the same SMP/e install are different. 

PROGRAM TIRTROFF APPLIED CETA850 RO73025 AEHBPGM0 CEHBPLD0 

Load Library SYSIOSIP.YZ776.CGN85C.CEHBPLD0 

Load Module TIRTROFF 

Linked on 2014.233 at 17:40:24 

Size 0000238 TTR 0000C2 

 

PROGRAM TIRUNST APPLIED CETA850 RO73025 AEHBPGM0 CEHBPLD0 

Load Library SYSIOSIP.YZ776.CGN85C.CEHBPLD0 

Load Module TIRUNST 

Linked on 2014.233 at 17:40:51 

Size 0000FA0 

 

TICBCMPX CEHBPLD0 

Load Library SYSIOSIP.YZ776.CGN85C.CEHBPLD0 

Load Module TICBCMPX 

Linked on 2014.328 at 06:15:20 

Size 0149EC8 

 

TICBLBCX CEHBPLD0 

Load Library SYSIOSIP.YZ776.CGN85C.CEHBPLD0 

Load Module TICBLBCX 

Linked on 2014.328 at 06:15:20 

Size 017F5D8 

 

Environment:  

CA GEN release 8.5

 

Answer: 

When we deliver ++PROGRAM elements, then these are already an LMOD, which we deliver and which does not need to be rebuilt.  These are just copied.  These two ++PROGRAM elements are linked by CA Technologies, delivered as load modules, and that is the earlier date which you see.

PDF0103C COPYMOD OUTDD=CEHBPLD0,INDD=SYSUT1 SEQ # 000001 

PDF0103C S M=((TIRTROFF,,R)) RO73025 

PDF0111I COPYMOD: SYSUT1 DSN=SYS14328.T061500.RA000.N570EDAP.R0263898 VOL=WRS802(DISK) DCB=(0 27,998 U PO) 

PDF0113I UNLOAD DATASET'S PHYSICAL DCB=(28,018 28,018 VS PS) 

PDF0112I CEHBPLD0 DSN=SYSIOSIP.YZ776.CAGN85.CEHBPLD0 VOL=SMIN8E(PDSE) DCB=(0 32,760 U PO) 

 

PDF0150M TIRTROFF WILL REPLACE SAME-NAMED MEMBER IN OUTPUT DATASET 

PDF0156M TIRTROFF LOADED ADR 000000 ---------- 

PDF0131M SYSUT1: MEMBERS: 1 COPIED 0 NOT COPIED 1 TOTAL 

PDF0132D DIR BLKS: 1 USED 0 FREE 1 TOTAL 

PDF0133M CEHBPLD0: MEMBERS: 0 ADDED 1 REPLACED 191 TOTAL 

PDF0189I END OF COPY STEP 1 - RC(0) 

 

Binder link dates for the two ++PROGRAM (TIRTROFF and TIRUNST)  were 2014.233 as linked by CA Technologies on this date and then delivered via the PTFs. 

For the other ++MOD elements (TICBCMPX and TICBLBCX), which have the date of 2014.328 and are linked during the SMP/e APPLY job: 

z/OS V2 R1 BINDER 06:15:17 MONDAY NOVEMBER 24, 2014 

Please note that binder, or the link, date of November 24, 2014 is date as 2014.328. 

Environment

Release: KGNDDL99000-8.5-Gen-DBP Developer License
Component: