We've had that too. Is the original report defined in CMOD as VB? does it need to be? When ODF outputs VB reports, it seems to use the Maximum record length - for VB, that's about what it is. If that is the case and it isn't avoidable, I've used one of our INPUT EXITS. When using OS/390 and an INPUT EXIT, I could force the second Application to 133, FB. (the hoops we jump thru).
Another way of accomplishing the same thing would be to define 2 output cards in the JCL and send one copy to one application group and another copy to the other. That way it won't matter. May have to coordinate with JCL prod control people though.
//HSC125MH OUTPUT NAME='XXXXXXXXX',
// FORMDEF=S0S00,PAGEDEF=SP1B < WRITER=P11B >
//HSC125DM OUTPUT NAME='XXXXXXXXXX',
// FORMDEF=S0S00,PAGEDEF=SP1B < WRITER=P11B >
//HSC125A EXEC EXEZTP,MEMBER=HSC125
//STEPLIB DD DSN=CORPL.HLTHSVCS.BTCHLOAD,DISP=SHR
//BSPWNERR DD SYSOUT=*
//CNTLCARD DD *
ALLB240 YDN0099N
//PRTFILE DD SYSOUT=(J,P11B),
// OUTPUT=(*.HSC125MH,*.HSC125DM)