| Author |
Message |
vinh nguyen
New User
Joined: 20 Mar 2008
Posts: 3
Location: California
|
|
|
|
Hi,
I would like to send a variable length binary file to the mainframe from a unix and/or linux system. The case is as follows. I send a file from the mainframe to the unix using BINARY and SITE RDW. The file is on the unix. Now, I want to send it back to the mainframe.
I used options such as BINARY, SITE RDW RECFM=VB LRECL=121.
Because we are sending as binary, the RDW is recognized as data and gets stored. Also, every line is being filled up to 121 and there is no variable length except maybe the last line.
How do i let the mainframe or ftp know when is the end of a line so it can save properly?
I've googled for weeks and haven't found a solution yet. The only thing i found was maybe to pad the file down with spaces to make it fixed length, and then post-process it on the mainframe. however, i don't know how to do this either.
Help?
I can append a (fake) BDW to the file if necessary. Also, I would prefer any manipulations on the unix side as i don't know mainframe as well. |
|
| Back to top |
|
 |
References
|
 Posted: Tue Mar 25, 2008 9:32 pm Post subject: Re: ftp: send variable length binary (VB) file to mainframe |
|
|
|
|
| Moved: Wed Mar 26, 2008 12:36 am by superk From TSO/ISPF to Other Mainframe Topics |
Gautam512
Senior Member
Joined: 05 Oct 2005
Posts: 346
Location: Vizag / US
|
|
|
|
hi,
try saving the file as a wordpad and try doing the transfer. |
|
| Back to top |
|
|
vinh nguyen
New User
Joined: 20 Mar 2008
Posts: 3
Location: California
|
|
|
|
What exactly do u mean? Save the file as wordpad?
I'm trying to send TO the mainframe variable length file containing binary data. So problem is telling the mainframe how long each record length is... |
|
| Back to top |
|
|
dick scherrer
Global Moderator
Joined: 23 Nov 2006
Posts: 6033
Location: 221 B Baker St
|
|
|
|
Hello,
| Quote: |
try saving the file as a wordpad and try doing the transfer.
|
How do you beileve that will help?
As far as i know, wordpad files are in a proprietary format that is completely incompatible with the mainframe. If you go to "Save As", there is no selection for IBM Mainframe, Variable Length . . .
Did you try this on your system? If yes, please post what happened. . . If no, please do so and then tell us what happens.
vinh nguyen -
How was this file used on the unix system? What processing needs it sent back to the mainframe - it is already there. . .? |
|
| Back to top |
|
|
vinh nguyen
New User
Joined: 20 Mar 2008
Posts: 3
Location: California
|
|
|
|
hey dick,
as of now, we are using the VB file from the mainframe to process using SAS in the UNIX (just our group at the company, the mainframe will never go away). We transfer the VB file over to the unix with the RDW intact, and we have a python script that appends a fake BDW to the data so SAS could read it via RECFM=VB.
Now, sometime, we might do changes to the raw data file (VB), and we have to send it out, and in order to do this, we have to get the file back on the mainframe. I don't have to do it yet (no cases yet), but i think we may have to do it in the future.
If we can do this, then our group could do all of our analysis on the unix and we'll just get and send files to the mainframe.
thanks for all your help! |
|
| Back to top |
|
|
dick scherrer
Global Moderator
Joined: 23 Nov 2006
Posts: 6033
Location: 221 B Baker St
|
|
|
|
You're welcome 
So far, i don't believe i've been much help. . .
If you have sas on both platforms, you might open an issue with sas support and see if they have a way to move sas files back and forth between the mianframe and unix.
Hopefully, there will be a solution before you meet the requirement.
d |
|
| Back to top |
|
|
|
|
