CMS Snapshot Analysis - Run Analyzer - Mainframe - Information - Mainframe File descriptor Block must be defined with zero record

Purpose

This page explains why Mainframe File Descriptor block must be defined with zero record.

Applicable in CAST Version

ReleaseYes/No
8.3.x✅

Details

Quality/rules:  File descriptor block must be defined with zero record

Block contains 0 records

It was a clause used on IBM Mainframe COBOL because in the old days of COBOL you had to specified a buffer size. By putting 0 records in the BLOCK CONTAINS, it will leave up to System to get the optimal block size for buffer on the machine being processed (i.e., IBM-360, IBM-370, etc).
This rule is for IBM zOS environments and should be deactivated for other platforms.

Notes / Comments

Related Pages