On Mon, 12 Mar 2012 08:21:13 -0700, Sam Siegel <[email protected]> wrote:
>Scott - I think the EOF marker is handled by SMS. If a file is >allocated to a non-sms volume with IEFBR14 it might be that no EOF >marker was created. This can result in a wrong length read when >trying to read from the dataset instead of going straight to EODAD. >Sam > This changed in z/OS 1.11 to include non-SMS also for an . As John M. hinted, it does require a valid DSORG. That can come from a default DATACLAS or from JCL. >From the announcement letter: "In z/OS V1.11, DFSMSdfp processing is changed to indicate end-of-file (EOF) during the allocation of data sets on DASD that are not SMS-managed and have either sequential or an undefined data set organization. This makes this processing for both SMS-managed and non-SMS-managed data sets consistent, to make it unnecessary to open data sets solely to indicate EOF, and to help prevent programs from reading old data when a data set is read immediately after being allocated. " -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:[email protected] Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
