Home |
Search |
Today's Posts |
|
#1
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
I have a 2046 byte record that I download from the mainframe to a ".txt"
file. The low order 1500 bytes of this file is purely text data. The first 746 bytes, however, contain a mixture of text, binary and packed data files (Comp and Comp-3) fields. It appears that irregardless of the contents of these files, the record length is shortened by the compression of this data in the download process. Is there any way that I can download this file, compensating for the loss of the compressed fields (don't need them anyway), so I can parse and load the true text fields into an Excel Spreadsheet? Thanking you all in advance... -- John |
#2
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
If I had to do this, I would convert the data to plain old ASCII on the
mainframe. It would make life a lot simpler on the pc side. And since the work has to be done somewhere, why not do it where it's easier -- on the mainframe. JEB wrote: I have a 2046 byte record that I download from the mainframe to a ".txt" file. The low order 1500 bytes of this file is purely text data. The first 746 bytes, however, contain a mixture of text, binary and packed data files (Comp and Comp-3) fields. It appears that irregardless of the contents of these files, the record length is shortened by the compression of this data in the download process. Is there any way that I can download this file, compensating for the loss of the compressed fields (don't need them anyway), so I can parse and load the true text fields into an Excel Spreadsheet? Thanking you all in advance... -- John -- Dave Peterson |
#3
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
David;
Thank you for your prompt response and insight. If it were possible to do this on the mainframe I would, agreeing with you to take the simplist solution. Unfortunately I'm not able to do that for a variety of reasons; cost, time and crossing boundries only to name a few. I have an immediate need for this information and cannot wait six months of BS to get it done. Thank you again. -- John "Dave Peterson" wrote: If I had to do this, I would convert the data to plain old ASCII on the mainframe. It would make life a lot simpler on the pc side. And since the work has to be done somewhere, why not do it where it's easier -- on the mainframe. JEB wrote: I have a 2046 byte record that I download from the mainframe to a ".txt" file. The low order 1500 bytes of this file is purely text data. The first 746 bytes, however, contain a mixture of text, binary and packed data files (Comp and Comp-3) fields. It appears that irregardless of the contents of these files, the record length is shortened by the compression of this data in the download process. Is there any way that I can download this file, compensating for the loss of the compressed fields (don't need them anyway), so I can parse and load the true text fields into an Excel Spreadsheet? Thanking you all in advance... -- John -- Dave Peterson |
Reply |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
Text Data mixed with Binary (Comp) and Packed (Comp-3) fields. | Excel Programming | |||
IF/AND Statements in Comp Calculator | Excel Worksheet Functions | |||
how do i set up a Cobol Comp-3 data field in Excel? | Excel Programming | |||
Code not working on another comp | Excel Programming | |||
Round error on home comp | Excel Programming |