I am getting a file via JCL/FTP which goes out to a server to pick up a Variable Length file that is being sent to a server in EBCIDIC. The reason it is being sent in EBCIDIC is to maintain the integrity of a Binary Bit Map that is included with every record. The problem I am having is that the file is currently coming to us as one continuous string of data. The CR and RDW are being stripped off the file during the FTP process.
Below are the commands listed after the IP address that are currently being used:
LOCSITE RECFM=VB LRECL=154 BLKSIZE=0
get KELLYSERV0.B00094 'TEST.IDA65.FROMAMEX.RESPONSE(+1)'
Joined: 17 Aug 2007 Posts: 562 Location: Iowa, USA
To keep the EBCDIC values, the file was probably sent to the intermediate server as BINARY. The binary file on the server has no RDW or CRLF and is just a string of data with no concept of "records".
When you bring this back to your mainframe that's what you get is a string of data.
You need a utility such as TRSMAIN (free from IBM) to PACK the records into a fixed length file before sending from the original mainframe. When you receive it on your mainframe, do the UNPACK to get the original VB file.