BillyBoyo wrote:steve-myers is correct, although looking the message up gives little further information.
Why have you got DATA in your EDIT command, and what does it do for you (other than disallow the LRECL of your data set)?
The DATA in the command line specifies the data type of the data set. In terms of the TSO command line, it's a keyword, but it's required by EDIT. The DATA keyword implies the data set contains generic data, not some language specific data like PLI, FORT, or ASM. It also implies a data set name suffix when the data set name is not fully qualified.
E X DATA implies you are using data set userid.X.DATA
There's a lot of junk hanging around from early TSO that has either disappeared or never really got implemented. One of these ideas was language syntax checkers that could be used within EDIT. There was some activity in this area in the 1970s, but it has all disappeared, usually because it was too clumsy or too limited. After SPF appeared there was no real interest in enhancing the command line portion of TSO. About the only language oriented syntax checker that has survived are the JCL check products from at least 2 vendors if my memory is correct, and these operate with ISPF, not the command line.
As billy-boyo says, the DATA keyword limits the record size to 255. There is a table in TSO/E Command Reference
(which I just discovered) that discusses this better than I can here, but you'll notice that all these data set types limit you to 255 bytes or less. This appears to be a generic restriction in EDIT.