I am not positive of this, but I think you DO need the JCL override. If the "hard coded" maximum LRECL in the FD does NOT match the maximum for the physical file and you don't have the JCL override, I believe you will get a file status of 39 when you OPEN the file indicating a "physical file attribute conflict".
As indicated elsewhere in the thread, I recommend using the RECORD VARYING IN SIZE rather than RECORD CONTAINS form for the FD of a variable length file. (Among other things, this allows you to determine the actual record length after every read - without negative subscripting to get the LLZZ information from the RDW) FYI, There is an existing SHARE requirement for getting COBOL to (better) handle SMS information without worrying about coding FD stuff. "Ted MacNEIL" <eamacn...@yahoo.ca> wrote in message news:<756912698-1229553371-cardhu_decombobulator_blackberry.rim.net-61158795 8...@bxe348.bisx.prod.on.blackberry>... > >Do you mean just define the COBOL FD as RECORD CONTAINS 0 TO 32756 CHARACTERS and then use LRECL=32760 as a JCL override for a file no matter what it's variable max length is? > > I don't believe you need the JCL override. > - > Too busy driving to stop for gas! ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
