Hello, when copying a FB 80 member to a VB 4096 dataset, trailing blanks in the FB 80 member seem to be removed, is this true? I did the copy using TSO ISPF 3.3.
The FB 80 member contains a XML document which originally comes from a UNIX machine, and it is split in fixed parts, so the new record starts anywhere in between (maybe in the middle of a XML tag). The XML parser which reads the document is a C program. In the past it used fgets and read the document as a textfile, but that's not ok in this case, because the splitted lines will cause XML syntax errors (due to the line feed which appear in the middle of the tags etc.). So I added an option to read the file as a binary file (fopen with "rb,type=record" and fread instead of fgets). In this case there are no line feeds at the end of the lines (which were not there originally in Unix). This works perfect, if the file is an FB file, and the blanks at the end of the lines are preserved. But if I copy the file to a VB file, the trailing blanks are removed, and the XML document is in error (in some places). So my question: can I copy a FB file to a VB file and keep the trailing blanks? Can this be done using the TSO ISPF dialog, or is a batch job needed? And: what about the ISPF editor? If I edit the VB file and save it, will the trailing blanks always be removed, or are there options to preserve the trailing blanks? What will FTP do, if the file is transferred from Unix as a text file into a VB 4096 file? For example, if the text file on Unix has no line feeds originally, but there are blanks at the positions 4094, 4095, 4096.: will they be stored or removed ?? Is it better to use FB in such cases? The XML file of possibly unlimited length has to be transferred to z/OS and processed there ... Kind regards Bernd ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
