Page 1 of 1

Exceeding the 132 byte default for DISPLAY

PostPosted: Wed May 10, 2017 10:55 pm
by Joe Horgan
Hello,

I am updating a job which executes a Natural program. The Natural program uses a DISPLAY statement to create a columned report, and I would like to add an extra two columns, but the output to the CMPRINT file will not display past the 132nd byte. I've increased the LRECL in the JCL and am using the FORMAT LS=190 in the Natural (needed to stow). Is there a PARM that can be added to the EXEC statement or is this a nucleus specific parameter that needs to be updated for the Natural program to exceed the default? Any help is appreciated!

Thanks,

Joe

Re: Exceeding the 132 byte default for DISPLAY

PostPosted: Thu May 11, 2017 9:54 pm
by Robert Sample
Have you posted a query to the Software AG support site? From what I can tell, FORMAT (1) LS=190 -- or something like that syntax -- should set the line size to 190 bytes. If it is not working for you, the SAG support people should be able to help you find out why.

Re: Exceeding the 132 byte default for DISPLAY

PostPosted: Mon May 15, 2017 9:57 am
by RGZbrog
Natural can handle a line size of 250 characters. I have written SYSOUT datasets of 160 characters, but I don't recall needing to go beyond that, so I can't say whether your issue is a mainframe limitation or your/user error. ;) (I haven't run a mainframe Natural batch job for years.)

An alternative to such a long line is to produce a multi-line report. See if the VERT keyword of the DISPLAY statement will help.

Re: Exceeding the 132 byte default for DISPLAY

PostPosted: Wed May 17, 2017 12:57 am
by RGZbrog
OK. I tested this on a mainframe.

SYSOUT is restricting the line size. Change your JCL to send the report to a dataset, instead.
//CMPRT01 DD  DSN=MY.REPORT,
//            RECFM=FBA,LRECL=191,BLKSIZE=0,
//            DISP=(NEW,CATLG),etc...