CA Filesave RCS Automated Recovery currently supports the recovery of non-Transactional VSAM files. At this time when one attempts to use a Transactional VSAM file, CA Filesave RCS Automated Recovery will fail and you will receive an abend when the Transactional VSAM file is opened.
At this time CA Filesave RCS Automated Recovery does not support Transactional VSAM.
You will find that CA Filesave RCS Automated Recovery works fine with non-Transactional VSAM files, but if you run with a Transactional VSAM file, you will get an abend similar to the one below while trying to open the Transactional VSAM File:
"FILE-MSG028 TRANSPARENT BATCH JOURNAL OPEN SUCCESSFUL FOR FILE DCF
IEA995I SYMPTOM DUMP OUTPUT
USER COMPLETION CODE=4039 REASON CODE=00000000
TIME=10.41.07 SEQ=03829 CPU=0000 ASID=019F
PSW AT TIME OF ERROR 078D1000 87C98B02 ILC 2 INTC 0D
NO ACTIVE MODULE FOUND
DATA AT PSW 07C98AFC - 00181610 0A0D58D0 D00498EC
AR/GR 0: A7CE15D6/84000000 1: 00000000/84000FC7
2: 00000000/28FCFD98 3: 00000000/0002000D
An enhancement request has been created for have this support added to the product. Please contact CA Technologies Support if you would like an update on the current status of CA Filesave's RCS Automated Recovery support of Transactional VSAM files.