Hello All,We are this EOV related message in the log when a VSAM RLS file gets an EOV condition.
VAM is not getting involved and adding volumes..
IEC070I - 104-204, an error occurred during EOV processing for a VSAM data set
Application team backed out file from RLS control to a non-RLS dataset and now VAM is working as expected.
They defined the dataset with the exact same definitions.
V370040 END OF VOLUME RECOVERY OPERATION STARTING FOR
V370040 CURRENTLY ON EXTENT # 1 ON VOLUME PPICJ9
V370040 END OF VOLUME RECOVERY OPERATION SUCCESSFUL FOR
V370040 NEW VOLUME SMS ADDED, NEW VOLUME COUNT 9
The define is exactly the same except the RLS Dataclass and Storclass are removed.
VAM works when file is not an RLS dataset and does not when it is a RLS dataset.
That is the only difference. We have seen this in more than 1 file.
VOLUMES (* *)
FREESPACE (25 25))
As you know, RLS is a very different design then non-RLS. It has its own servers(SMSVSAM) and all the control blocks are inaccessible to other programs. Is it possible that the hooks that VAM has been using to intercept VSAM functions will not work with RLS?Thank you,Luke Kutner