I’m struggling with a software vendor that wants to upload (Server to z/VSE) a 100-byte record (that has no termination character(s), like CRLF). I’m having problems with CSI on finding a way to transfer this file into a SAM (VSAM-managed SAM file). (We’ve never done FTP to an EPIC disk file and I’ve successfully transferred the PTF.FILE to a SAM-ESDS.)
So, I’m reaching out for ideas.
Frank M. Ramaekers Jr. | Systems Programmer | Information Technology | American Income Life Insurance | 254-761-6649
Frank,
No terminate characters, at all? That sounds like a problem on the sending end.
I believe you can set a ‘linux’ mode that will accept LF only. Could that be the case? They’re sending LF only, and not CRLF?
Dave
Dave Stuart
Principal Information Systems Support Analyst
Information Technology Services
County of Ventura, CA
No, this is my understanding that the file they create has no record terminating character(s).
Frank M. Ramaekers Jr.
Maybe try uploading in Binary mode?
Dave
Are the records fixed length? You can then force fixed length on the transfer. Also, it’s much easier to make a VSAM ESDS the target of the transfer since VSAM is inherently variable length records and easily accommodates records of varying sizes. I also recall there being something about 4/8 byte overhead on sequential files when unblocked/blocked, but I always use VSAM ESDS so I really don’t have an illustrative example.
_______________________________________________
VSE-L mailing list
VS...@lists.lehigh.edu
https://lists.lehigh.edu/mailman/listinfo/vse-l
Need the ASCII to EBCDIC translation.
Records are not of varying lengths. 100 bytes fixed length.
Programs work on SAM files, they don’t want to change a large number of programs from SAM to ESDS.
Frank M. Ramaekers Jr.
Send it to a VSAM file, then REPRO it to the working sequential file.
Seriously, send it to a VSAM file and at least look at what you’re really getting. I’ve seen files where “all records are the same” except the first or last record is different. Another good tool for the PC is TextPad which can expose hex information where you can see how records are really terminated; they frequently are but the creator is unaware of it.
From: VSE-L [mailto:vse-l-bounces+kcorkery=live...@lists.lehigh.edu] On Behalf Of Frank M. Ramaekers
Sent: Thursday, July 28, 2016 1:17 PM
To: VSE Discussion List
Subject: RE: FTP of 100-byte record file to VSE
Records are coming from a Windows server, so I’ve tried the following:
QUOTE SITE LRECL 100
QUOTE SITE RECFM F (and FB)
QUOTE SITE CRLF OFF
But I still get something very odd like:
FTP928E Record 1 larger then max(92) for xxxxxxx UNIX=NO
Not sure why FTP server thinks that the maximum is 92 on a 100 fixed length file.
Frank M. Ramaekers Jr.
If you are using FTPBATCH, try adding SET EXTRADAT ACCEPT to the FTPBATCH.L and see if that lets it transfer. If you’re using the internal FTP client, define the FTPD with EXTRADATA=ACCEPT specified.
Hope it helps,
Max E. Singley
Technical Services Project Leader
Alex Lee, Inc.
Email: max.s...@alexlee.com
Tel: 828-725-4894
A responsive and reliable production environment doesn't just happen by accident.
Again, the client is on a Windows Server machine.
Frank M. Ramaekers Jr.
From: VSE-L [mailto:vse-l-bounces+framaekers=ailif...@lists.lehigh.edu] On Behalf Of Max Singley
Sent: Thursday, July 28, 2016 12:45 PM
To: VSE Discussion List
In that case, you will have to add EXTRADATA=ACCEPT to your mainframe FTPD.
have fun,
Max
Leap and the net will appear!
We do transfers to SD files all the time. But I’m having this very same problem. The records look variable but I think FTP is seeing them as one big chunk because of the CRLF missing…
____________________________________
Andy Engels
IS Team Leader – Technology Infrastructure
IMRF
Oak Brook, IL
630-368-5346
From: VSE-L [mailto:vse-l-bounces+aengels=imrf...@lists.lehigh.edu]
On Behalf Of Frank M. Ramaekers
Sent: Thursday, July 28, 2016 11:04 AM
To: vs...@lists.lehigh.edu
Subject: FTP of 100-byte record file to VSE
I’m struggling with a software vendor that wants to upload (Server to z/VSE) a 100-byte record (that has no termination character(s), like CRLF). I’m having problems with CSI on finding a way to transfer this file into a SAM (VSAM-managed SAM file). (We’ve never done FTP to an EPIC disk file and I’ve successfully transferred the PTF.FILE to a SAM-ESDS.)
To eliminate some items, I’m now trying to send a 100-byte/record file and each record is followed by a LF (Unix record delimiter). I’m attempting to upload to a SAM file (complete with DLBL/EXTENT/ASSGN).
I’m still getting the FTP928E Record 1 larger then max(92) for xxxxxxx UNIX=NO message, although I have SITE RECFM F/FB and SITE LRECL 100/108. (Thought I’d throw in the 108 since the difference between 92 and 100 is 8 characters).
No matter what I do, it (FTP Daemon) thinks that 92 is the maximum, for some reason. Since it is now strictly SAM, I can’t imagine where it is getting this information from.
So, I tried w/o any SITE commands and get the same message.
Frank M. Ramaekers Jr.
From: VSE-L [mailto:vse-l-bounces+framaekers=ailif...@lists.lehigh.edu] On Behalf Of Stuart, David
Sent: Thursday, July 28, 2016 11:10 AM
To: VSE Discussion List
Yeah, tried that. DEFINEd a separate FTPD o a different port and added the EXTRADATA=ACCEPT. No luck. L
Just as a side note, tried the same transfer to z/VM and it transferred okay….well, that’s until you examine the file contents, only the first 100 bytes transferred. Ugh!
Frank M. Ramaekers Jr.
From: VSE-L [mailto:vse-l-bounces+framaekers=ailif...@lists.lehigh.edu] On Behalf Of Andy Engels
Sent: Thursday, July 28, 2016 1:03 PM
To: VSE Discussion List
How about treating it as a binary file and using a SITE command to specify attributes like recfm or lrecl? I haven't used FTP directly to VSE, but I've done that sort of thing to MVS.