B055 after Easytrieve upgrade - field past end of record

Program that compiled for years started failing with B055 INVALID LENGTH, TYPE OR DECIMAL PLACES after we jumped releases.

Field starts at 10 length 72 on a FILE declared FB(80 ...). Math says that sticks out past 80. Did they tighten the check?

Yes. Newer maintenance actually verifies field defs against the declared record length. Old levels let that slide and you risked S0C4 at runtime.

Fix the layout. Either the LRECL is wrong or the field is.

Copybook was for a 100-byte version of the file. JCL still said 80. Aligned both. Clean compile.