I have a CICS defined ESDS file which serves as a log file. Everytime I need to run batch to print the full content of the ESDS log file, I have to close the file in CICS, run the batch program and then re-open the ESDS file in CICS for use. If I did not close the file, the batch program will not be able to print the full content of the log file. What parameters can I set to the FCT of the CICS ESDS file or any expert advise you can give to me so that I can bypass the step to close the file before running my batch program?
The short answer to this one is that - as you have observed - VSAM buffering is stopping you from getting at all the records at the end of your ESDS. You could try reducing the buffers used for the file within CICS - but that would cause you performance problems (perhaps) and only reduce the number of missing records - not guarenteeing that you will get all of them from Batch. Have a look through all the earlier responses to this forum and you will see an equivalent Q&A about Closing & Opening the file from Batch Processing using my EXCI SupportPac.
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.