The only difference is that LRECL in production has been increased automatically by 4 bytes.
Hmmm..... by Natural or the OP system?

Of course, I opened support request 572876.
ServLine24 has several issues and solutions regarding NAT1512, but only one for NAT413 (TRUNC subparameter does not work).

Solution and explanation:

NAT228 and NAT232 allowed you to write 100 bytes (1 AREA (A100)) to a file defined as VB and LRECL=100, for example.

In NAT3 and higher, LRECL must be 104 or Natural will complain with NaT1512 (unless you use TRUNC=ON in which case the record will be truncated).

Another solution, I think a better one, is to include the new VMAX=NAT Natural parameter into the NTWORK macro. VMAX controls the LRECL setting for an output file with variable record format (RECFM=V). So you won't have to change your DCB in the JCL.

At this time (7 April 2005), VMAX=NAT doesn't work. I added 4 bytes to LRECL.