search cancel

ACF2 ACFFDR timestamp difference on two LAPRS

book

Article ID: 201620

calendar_today

Updated On:

Products

ACF2 ACF2 - DB2 Option ACF2 for zVM ACF2 - z/OS ACF2 - MISC LDAP SERVER FOR Z/OS PAM CLIENT FOR LINUX ON MAINFRAME WEB ADMINISTRATOR FOR TOP SECRET

Issue/Introduction

SMPE CSI is used on two LPAR runtime, but somehow the Assembly date differs in Stage when compared with Dev. Since ACFFDR RMID in Dev and Stage matches we infer that both Dev and Stage are at same maintenance level.

NDC7(Dev):

RUNNING CA ACF2  REL 16 /MVS SP7.2.2; WITH MODE = ABORT                            

USING FDR ASSEMBLY:  08.54  03/26/18

 NDC8(Stage):

RUNNING CA ACF2  REL 16 /MVS SP7.2.2; WITH MODE = ABORT                        

USING FDR ASSEMBLY:  10.36  06/06/18

Environment

Release : 16.0

Component : CA ACF2 for z/OS

Resolution

The assemblies of the ACFFDR on 2 LPARS using the same CSI can be different for a multitude of reasons.

The best path going forward is to look at the installation libraries and compare them to the runtime libraries of SYSTEMA and SYSTEMB. The ACFFDR of each runtime library should match the install library. This is the hlq.CAX1LINK(ACFFDR). Inside the ACFFDR module, you can find the date of the last assembly. Use the command:

f 'CA ACF2 REL 16.0'

After the 'CA ACF2 REL 16.0' there will be a time and date stamp. Compare this to each runtime library. My assumption is that it will match the SYSTEMB library and not the SYSTEMA. If it matches both, then you will need to issue the commands on the SYSTEMA system:

F LLA,REFRESH
F ACF2,NEWMOD(ACFFDR)

If it doesn't match on one or both systems then update the runtime libraries and issue the previous commands.