Problem solve Get help with specific problems with your technologies, process and projects.

KSDS and unexpected sequencing

From a CICS region I write records to a VSAM KSDS file. All the necessary error handling is in place but every now and then I end up with a corrupted dataset because one of the records gets written out of sequence. Why would this happen and how is it happening because at the time of the write there is no indication that the error has occurred? We are currently running ZOS 2.1 and CICS TS 1.3

If you are using a KSDS, I don't understand how you can get out of sequence errors. If it was another type of VSAM file, then there are UnitOfWork implications which can lead to unexpected sequencing.

Robert Harris
CICS Technical Strategist -- CICS expert at Search390.com

Editor's note: Do you agree with this expert's response? If you have more to share, post it in one of our .VO7aaqqaAFk.0@/search390>discussion forums.

Dig Deeper on IBM system z and mainframe systems

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.