Re: MVSNFS shows a different file under the Unix side compared to the MVS side
-- Have you tried using FBS vs. FB ? This is for fixed block standard and recognizes the last block can be shorter and not a full block. FB likewise permits the last block to be shorter. Keep in mind one significant drawback: if the RECFM is FBS, an imbedded short block, for example in a MOD'ed file, will signal EOF to QSAM. Rick -- 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
Re: MVSNFS shows a different file under the Unix side compared to the MVS side
>>>Have you tried using FBS vs. FB ? This is for fixed block standard and >>>recognizes the last block can be shorter and not a full block. >> FB likewise permits the last block to be shorter. >Surely FB permits *any* block to be short. It's FBS that requires that all but the last be full size. We are actually using Variable blocks. I think the argument of the cache is valid but not after 24 hours. Also, I noticed that the files in the NFS mount point when I am looking at them under TSO/ISPF are quite often locked (file in use). I end up having to put a "B" for browse under 3.4 and keep on hitting enter until I can get into the file. The file is not supposed to be in use on the Unix side so I don't know why I get the locks. -- 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 -- 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
Re: MVSNFS shows a different file under the Unix side compared to the MVS side
On 31 August 2011 13:31, Paul Gilmartin wrote: > On Wed, 31 Aug 2011 16:31:44 +, Mingee, David wrote: > >>Have you tried using FBS vs. FB ? This is for fixed block standard and >>recognizes the last block can be shorter and not a full block. >> > FB likewise permits the last block to be shorter. Surely FB permits *any* block to be short. It's FBS that requires that all but the last be full size. Tony H. -- 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
Re: MVSNFS shows a different file under the Unix side compared to the MVS side
On Wed, 31 Aug 2011 16:31:44 +, Mingee, David wrote: >Have you tried using FBS vs. FB ? This is for fixed block standard and >recognizes the last block can be shorter and not a full block. > FB likewise permits the last block to be shorter. -- gil -- 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
Re: MVSNFS shows a different file under the Unix side compared to the MVS side
Have you tried using FBS vs. FB ? This is for fixed block standard and recognizes the last block can be shorter and not a full block. David L. Mingee Principal Systems Administrator Indianapolis Production Control Data Center Operations / Operations Technical Support Work Ext 782-6460 Work Direct Dial 317 581-6460 Home 317 598-0919 / Cell 317 341-0885 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Paul Gilmartin Sent: Wednesday, August 31, 2011 12:22 PM To: IBM-MAIN@bama.ua.edu Subject: Re: MVSNFS shows a different file under the Unix side compared to the MVS side On Tue, 30 Aug 2011 22:24:35 +, Uriel Carrasquilla wrote: >we have a an NFS mount point on a Sun Solaris that is being serviced by MVS >(zOS 1.11) NFS server. when my customer dropped a file on the Sun's side NFS >mount point, it caused an I/O error. When I compared what I see on the Sun >side under the mount point to what I see under TSO/ISPF, I can see that 1,131 >records failed to get across out of about 77k records. Yet, the original file >that was dropped into the NFS mount point are identical. In other words, when >I do a diff between the original file and the one in the MVS Mount Point on >the Unix side, they are identical. When I download the MVS file and do a diff >with what is supposed to be an identical copy in the Unix Mount point, they >are different. >May be someone can enlight me with an explanation as to why the the Unix side >shows an identical copy of the original that was dropped in the mount point >but in the MVS side I see records in errors. > MVSNFS does some aggressive caching. It's possible that on the UNIX side you're seeing data that MVSNFS returns from cache; on the MVS side the actual file content. My most frequent source of I/O errors is attempting to copy to a RECFM=FB data set a UNIX file containing trailing blanks. -- gil Regards, >Uriel > >-- >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 -- 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 -- 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
Re: MVSNFS shows a different file under the Unix side compared to the MVS side
On Tue, 30 Aug 2011 22:24:35 +, Uriel Carrasquilla wrote: >we have a an NFS mount point on a Sun Solaris that is being serviced by MVS >(zOS 1.11) NFS server. when my customer dropped a file on the Sun's side NFS >mount point, it caused an I/O error. When I compared what I see on the Sun >side under the mount point to what I see under TSO/ISPF, I can see that 1,131 >records failed to get across out of about 77k records. Yet, the original file >that was dropped into the NFS mount point are identical. In other words, when >I do a diff between the original file and the one in the MVS Mount Point on >the Unix side, they are identical. When I download the MVS file and do a diff >with what is supposed to be an identical copy in the Unix Mount point, they >are different. >May be someone can enlight me with an explanation as to why the the Unix side >shows an identical copy of the original that was dropped in the mount point >but in the MVS side I see records in errors. > MVSNFS does some aggressive caching. It's possible that on the UNIX side you're seeing data that MVSNFS returns from cache; on the MVS side the actual file content. My most frequent source of I/O errors is attempting to copy to a RECFM=FB data set a UNIX file containing trailing blanks. -- gil Regards, >Uriel > >-- >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 -- 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
MVSNFS shows a different file under the Unix side compared to the MVS side
we have a an NFS mount point on a Sun Solaris that is being serviced by MVS (zOS 1.11) NFS server. when my customer dropped a file on the Sun's side NFS mount point, it caused an I/O error. When I compared what I see on the Sun side under the mount point to what I see under TSO/ISPF, I can see that 1,131 records failed to get across out of about 77k records. Yet, the original file that was dropped into the NFS mount point are identical. In other words, when I do a diff between the original file and the one in the MVS Mount Point on the Unix side, they are identical. When I download the MVS file and do a diff with what is supposed to be an identical copy in the Unix Mount point, they are different. May be someone can enlight me with an explanation as to why the the Unix side shows an identical copy of the original that was dropped in the mount point but in the MVS side I see records in errors. Regards, Uriel -- 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
