
Changes at run time with Enterprise COBOL Version 6
In some cases, the STORAGE runtime option cannot be used to initialize WORKING-STORAGE to a chosen value at startup. These cases are:
- COBOL V6 programs with spanned (RECORDING MODE S) files
- Non-CICS COBOL V5 programs compiled with DATA(31)
- File status changes in V6:
- WRITE statement on line-sequential file with a record size mismatch.
In prior releases of Enterprise COBOL, when an attempt is made to write a record to a line-sequential file with mismatched record size, file status 48 is incorrectly returned. This is corrected in Enterprise COBOL V6 to return file status 44.
OPEN INPUT on a line-sequential file when the UNIX file attribute is write-only.
In prior releases of Enterprise COBOL, an OPEN statement with the INPUT phrase on a line-sequential file that has the write-only attribute, such as a z/OS® UNIX file with DD PATHOPTS=(OWRONLY,...) or a COBOL program that has the write access permission only, incorrectly returned file status 0 (successful). An OPEN statement attempted on a file that does not support the open access mode should return file status 37.Note: "write-only" here does not mean the APPLY WRITE-ONLY clause that is not applicable to line-sequential files. Line-sequential files are files created in the z/OS UNIX file system.In Enterprise COBOL V6, this OPEN statement is detected with file status 37.
- OPEN INPUT, I-O, EXTEND on VSAM file with file attributes mismatch. In prior releases of Enterprise COBOL, when an OPEN INPUT, I-O or EXTEND statement is attempted on a VSAM file that is not defined as OPTIONAL, and a file attributes mismatch is detected, file status 35 is incorrectly returned. This is corrected inEnterprise COBOL V6 to return file status 39.Note: Similar file attributes mismatch condition for OPEN OUTPUT, and for OPEN INPUT, I-O, and EXTEND when the VSAM file is defined as OPTIONAL, are already correctly reported as file status 39.
- WRITE statement on line-sequential file with a record size mismatch.
