File Status 35 during OPEN statement in mainframe environments
29K reputation · 23 Jul 2021, 09:20 UTC
In IBM Enterprise COBOL, the OPEN statement relies on the external Job Control Language (JCL) to map the SELECT clause's assignment name to a physical dataset via a Data Definition (DD) statement.
When the runtime environment cannot locate the required DD name or the associated dataset is missing, the system returns a File Status 35. While this is a documented failure condition, the specific interaction between the FILE-CONTROL configuration and the JCL environment can lead to ambiguity during deployment validation.
Given a scenario where the JCL is syntactically correct but the runtime returns File Status 35, what are the primary environmental factors that cause this mismatch? How does the compiler version affect the reporting of this status compared to a system abort?
cobol