We just installed z/OS 2.3
Since then, CA-Allocate EOV logic is disabled.
This is also reported by Health Check : ALLOC_VRFY_EOV_X37_SVCS_STATUS
I can't find why or any error message.
Here is part of the joblog :
VAM000I VDSUT002 CCTVC50 ~RMID(RO53726)~ 20130109 18.41
VAM5020 VAMAB490 HOOKED AT IEFAB490
VAM000I V37ST451 CCTVC50 ~RMID(RESERVE)~ 20100222 17.02
VAM000I V37LODER CCTVC50 ~RMID(RO97974)~ 20170915 17.21
VAM5012 V37IAM01 IS LOADED AT A197E000 WITH LENGTH 00005348
VAM5012 V37TCTUP IS LOADED AT A1977000 WITH LENGTH 00006050
VAM5012 V37UCB01 IS LOADED AT A196B000 WITH LENGTH 0000BFA8
VAM5301 EOV LOGIC DISABLED
VAM5012 VAM2F$F1 IS LOADED AT A1958000 WITH LENGTH 00010A38
VAM5012 VAM2F$B1 IS LOADED AT A1952000 WITH LENGTH 00005BC0
DIM000I DYNAMIC INTERFACE MANAGER VAM.
VAM000I VAMHKR00 CCTVC50 ~RMID(RESERVE)~ 20100308 14.37
VAM000I VAMHKR01 CCTVC50 ~RMID(RO23185)~ 20101012 17.13
DIM010I DYNAMIC INSTALLATION OF SVC(026) HOOK.
I thought we installed all required maintenance for z/OS 2.3
Is there any missing maintenance of parameter for this ?
Release : 12.5
Component : CA Allocate DASD Space and Placement
Regarding your EOV problem please verify if you have PTF SO11680 installed:
After applying IBM PTF's UJ00897 (z/os 2.4), UJ00896 (z/os 2.3), and UJ00898 (z/os 2.2), the CA Allocate 'end-of-volume' (EOV) environment willnot be enabled after CA Allocate initialization.
VAM5301 EOV LOGIC DISABLED
VAM000I VAMHC006 HEALTH POOR
Your CA Allocate system failed to initialize End-of-volume Support.
You can download the PTF using the following link:
The VAMH0101E is issued since you are running with PLOPT94 set to Y.
Following is from the health check:
CA Allocate is not configured to utilize available STUB Methodology.
Explanation: You are running with PLSOPT94 set to (Y) which will cause CA Allocate to attempt to remove the hooks it has at IGGPRE00, IGGDAC02, IGGPOST0 and SVC26 during a REMOVE operation in the order in which they were set. This process is referred to as LIFO (last-in, first-out).
The default value of PLSOPT94 is (N), which will cause CA Allocate to leave those hooks in. This process is referred to as the STUB process. The STUBs provide anchor points for CA Allocate and are effectively dormant when the system is not active.
System Action: In the event of a shutdown outside of an IPL, CA Allocate will attempt removal of the hooks it has at IGGPRE00, IGGDAC02, IGGPOST0 and SVC26 using the LIFO Methodology. LIFO removal of one or more of these hooks is likely to fail because of other OEM products you are running with also hook at these places and very likely hooked after CA Allocate hooked.
Operator Response: Notify the systems programmer.
System Programmer Response: Change the value of PLSOPT94 to (N) in the sysparm override member of your CA Allocate parmlib. The new value(s) will become effective the next time you recycle CA Allocate, or you can use a PARMREF operation to dynamically activate the new values.