Vsam file return code 04

Write error on data. Write error on index. Write error in sequence set. Read past end of file. Duplicate key. Key sequence error.

Not found. Control interval in use by other job. Volume cannot be mounted. Unable to extend dataset. RBA not found. Key is not in a defined key range.

Insufficient virtual storage. Find centralized, trusted content and collaborate around the technologies you use most. Connect and share knowledge within a single location that is structured and easy to search.

Below is ithe input output section in my pgm. So FB should have record contains or Varying clause. Assuming your VSAM file is properly initialized and your JCL is coded consistently with your program requirements there should be no issue.

How are we doing? Please help us improve Stack Overflow. Take our short survey. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Fix your code to have the right record length for the file. Both lengths are same,but still i am getting same error. VSAM program fields in my program below, Code:. Posted: Sat May 15, am. If you could post the DUMP command output, that will help. Just in the off-chance, what is your DD statement in the step? Posted: Mon May 17, am.

Posted: Mon May 17, pm. I hope you are not getting any error code when you are opening this file. Problem got solved and it working fine now Check both in the manuals and understand thoroughly. Do some tests to confirm.

VDO and ODO are different ways you could have chosen to solve the problem, as would have been supplying levels of different sizes representing the different record-types on your file. I can't make sense of what you say at the end. If the input file was empty, you'd get end-of-file file-status