I have downloaded VB format dataset from Mainframe to PC. Then I have uploaded the file from PC to Mainframe as a new dataset. While comparing the new dataset with original dataset, the data is not matching. If the dataset is FB format it's matching.
Can anyone help me how to solve this FTP issue with VB format datasets?
Joined: 26 Apr 2004 Posts: 4650 Location: Raleigh, NC, USA
I've been looking at this issue from a bunch of different angles, and I can't see a solution that doesn't compromise the integrity of the data. Why you wish to do this process, I don't know, but here is what I see to be the major issues:
As you know, the VB dataset format uses the RDW (Record Descriptor Word) in the first 4 bytes to indicate the length of the record. You can remove the RDW (which is the default) or keep in with the data (LOCSITE RDW), but I can't see where it would help any on a binary transfer. Since VB records don't contain trailing blanks, then specifying LOCSITE TRAIL to retain any trailing blanks isn't going to help either. When you specify a binary transfer, then you lose the inter-record seperator indicators (which on an ASCII transfer would convert the END-OF-RECORD (hex '15') to a Carriage-Return/Line Feed (hex '0D0A')). So, in essence, you create a continuous stream of bits without any indicators as to how to properly re-assemble them after the upload.
Now, if you were to just transfer the data as ASCII without the RDW or trailing blanks, it would probably work.