So going from a "windows" environment to mainframe - there is a difference with record sizes.
The "windows" environment has long records. The file being created in the mainframe side (and you should logon to the mainframe to view it in Option 3.4) will have a fixed or VB record length that may not be long enough. The SMS functions may not allocate your file on the mainframe long enough. For example, your CSV file has a maximum line length of 356 characters. But on the mainframe side the default allocation you are getting is an LRECL of 80. This can create this type of error. Note: When working on moving data from PC to MF or MF to PC would be best done while you are active in BOTH environments. Then where there is an error you can look on the system where the error came from can be viewed. If possible, you might want to see if you have access to tools like FILEZILLA or REFLECTIONS FTP. Both can provide a better interface than native FTP, IMO. You need to know how many characters on a line, then set the LRECL to the maximum length. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Ron Thomas > Sent: Friday, April 21, 2017 10:40 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: FTP Failing with space issues > > Ok . i tried to copy a csv file that is there in the shell and i am getting > the below message . I tried increasing the LRECL of the PDS file and still the > same issue . Any idea on what could be the issue here ? > > $ cp -T SN_ASC00_03212017.csv "//'ng772pt.X.Y.Z'" > cp: FSUM6260 write error on file "//'ng772pt.X.Y.Z'": EDC5003I Truncation of a > record occurred during an I/O operation. > > Thanks > Ron T > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
