We are in the process of upgrading to CICS/TS 1.3 from 4.1. While testing we will need to go back and forth with our 4.1 region. While testing in TS 1.3, our VSAM files will be updated. Are there any issues regarding this? Are 4.1 and TS/1.3 compatible this way? Is there documentation you can point me too that describes this?
This should be OK - as long as you are only doing it in an environment where the VSAM data is not vital : I would hope that you don't do this in a production environment.
As long as you ensure that the CICS region successfully shuts down, your VSAM file integrity should work. The problem will occur on a failure and you restart on a different release - in flight activity will not have been backed out/recovered, and this will lead to the integrity problems.
I guess you are interested in finding out how the Logger reacts to your environment, so as long as you do the logger-based recovery processing before switching back to CTS 4.1, all should be well.
Dig Deeper on IBM system z and mainframe systems
Related Q&A from Robert Crawford
For better mainframe capacity planning, how do I convert CPU hours to MIPS? And is there a way to calculate the relationship between MIPS and MSUs? Continue Reading
I have two years of experience in mainframe technology, currently working as a mainframe developer. I want to change to Java technology. Continue Reading
I want to replicate DB2 from the mainframe to an AIX box since it's cheaper and the copy can be used for testing. Is this possible? Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.