The Tek-Tips staff will check this out and take appropriate action. Click Here to join Tek-Tips and talk with other members! Already a Member? Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free. Register now while it's still free! Already a member? Close this window and log in. Join Us Close. Join Tek-Tips Forums! Join Us!
By joining you are opting in to receive e-mail. Promoting, selling, recruiting, coursework and thesis posting is forbidden. Students Click Here.
Hello I have a problem. I need to export data from Cobol data files dat, inx to anything else txt, cvs, excel access, whatever. I need to do this using C and. NET platform. But I cannot open or read this files I tried as flat file with fixed row size and separator, I tried different data readers like SiberDataViewer or even simple notepad if open file I can see only strange characters.
I wonder I anyone know some ODBC driver or data reader which will be able to open and read this files free or with demos, trials to check if it works witch my dat,inx files before I buy it.
Hotels use Cobol application called ReHot which store data in dat data , inx indexes files. Software vendor of course won't help and application cannot export data to different files only print them on fiscal printer. The files are in simple binary code, unless some encryption hasn't been applied. Which means it would be useful if you had the source describing the record format of these files. If I read your post right in saying that "the vendor won't help", that probably means all you have is the executable, which means you won't have this.
The vendor would have likely made this closed-source, which probably means there are EULA considerations involved. Speaking of which, I'm not finding anything when I google the terms you used.
Anyhow, unless you have the record format of the file Is this on the vendor website? Vendor name is gip unfortunately web site is in Polish so you wont be able to read it but I checked and there is only description of the software for customers, nothing for programmers : Also I don't have any record format of these files.
You can then open that file as a csv in Excel. Write an excel macro. In one sheet provide the structure i. The macro will read the structure of the file and split the text in multiple columns based on their length. You can look at this link for some idea on how to write the macro. If this is a one-time task I'd just open it in excel and use text to columns and manually set split points to get each field into its own cell.
If this isn't a one-off I'd just modify the program that produces the output to have a comma between each field in the output record. The FileWizard results can be stored in a Xml file for use in other languages or you can use the copy Function to copy from Ebcdic to either Ascii fixed or CSV formats. There is some out of date documentation on the File Wizard.
Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Asked 10 years, 2 months ago. Active 9 years, 8 months ago. Also, if special or unique conversion processing is required it may be added to the generated COBOL source code.
The copy file is required to have one 01 level group definition with a valid field name. If multiple record types are defined with multiple 01 group levels then the copy file will need to be split apart by each 01 group level. A callable COBOL program should then be generated for each of the 01 group levels or multiple record types.
When used in conjunction with the SimoZAPS utility program a complete suite of conversion programs may be generated. CBL parameters. CMD process. To create a complete conversion package requires the use of two SimoTime utility programs. For example, a five digit packed field would be changed to a three byte x'F' value. The following is an example. Note: It is not a good practice to have non-numeric values in a numeric field.
The reason the packed field contains spaces should be corrected. Refer to the Considerations and Limitations, Packed Numeric Fields section of this document for more information.
The following would pass the arguments as parameters to the command file Rec1Mfo1. Once the preceding information is entered the "Record Layout" function may then be selected from the Micro Focus Desktop "Tools" item.
Note: The information about the user tools is stored in the Windows registry. The information is stored in the Windows registry at the following location. With the "Tools" item highlighted select "Registry" from the toolbar at the top of the "Registry Editor" window and from the drop-down list select "Export Registry File".
At this point follow the prompts to select a directory and file name to save the exported registry entry information for the user defined tools to be used with MFE. The following command file Rec1Mfo1. An HTML document will also be created and displayed using the browser. This section describes situations that may occur during the migration of data from an IBM Mainframe to a Windows platform.
This approach offers two advantages. I think we all would agree that numeric fields should never contain non-numeric values.
The situation that causes a non-numeric value in a numeric field should be corrected. The following table shows the rules used by SimoREC1 for conversion of numeric fields. Numeric fields that are signed, zoned-decimal format require additional consideration. The two options for maintaining the numeric format as zoned-decimal are as follows. The sign position trailing or leading will have the high-order four bits or left-most nibble represent the sign and low order four bits or right-most nibble is the binary value for the digit.
The sign position will be 'Cn' or b'nnnn'. The ASCII format for positive numbers in all positions except the sign position will be x'3n' or b'nnnn'. The sign position will be x'7n' or b'nnnn'. Use a modified-zoned-decimal format where the sign position trailing or leading will be translated based on the character display value.
The sign position trailing or leading will have the high-order four bits or left-most nibble represent the sign and low order four bits or right-most nibble represent the digit. The sign position will no longer abide by the strict definition of zoned-decimal. These will convert to the ASCII letters "A" through "I" or x'41' through x'49' and this would maintain the right-most nibble as the binary digit value and this is in accordance with the definition of zoned-decimal.
The departure from the strict definition of zoned-decimal happens with the positive zero and negative zero through nine. The same is true for the negative digits 1 through 9. These are translated to the ASCII values of "J" through "R" which are x'4A' through x''52' and the right-most nibble is no longer the binary value of the digit.
This is a departure from the definition of zoned-decimal. Micro Focus supports both the zoned-decimal and the modified-zoned-decimal. If the FTP mode is ASCII then the sign position will conform to the modified-zone-decimal format when the data is converted during the file transfer process.
This is the default behavior. However, we have seen a few instances where a packed field may contain SPACES and we have addressed this situation with a configurable option. The purpose of this document is to assist as a tutorial for new programmers or as a quick reference for experienced programmers.
In the world of programming there are many ways to solve a problem. This documentation and software were developed and tested on systems that are configured for a SIMOTIME environment based on the hardware, operating systems, user requirements and security requirements.
Therefore, adjustments may be needed to execute the jobs and programs when transferred to a system of a different architecture or configuration. Software Agreement and Disclaimer Permission to use, copy, modify and distribute this software, documentation or training material for any purpose requires a fee to be paid to SimoTime Technologies.
Once the fee is received by SimoTime the latest version of the software, documentation or training material will be delivered and a license will be granted for use within an enterprise, provided the SimoTime copyright notice appear on all copies of the software. The SimoTime name or Logo may not be used in any advertising or publicity pertaining to the use of the software without the written permission of SimoTime Technologies.
SimoTime Technologies makes no warranty or representations about the suitability of the software, documentation or learning material for any purpose.
It is provided "AS IS" without any expressed or implied warranty, including the implied warranties of merchantability, fitness for a particular purpose and non-infringement. SimoTime Technologies shall not be liable for any direct, indirect, special or consequential damages resulting from the loss of use, data or projects, whether in an action of contract or tort, arising out of or in connection with the use or performance of this software, documentation or training material.
This section includes links to documents with additional information that are beyond the scope and purpose of this document. The first group of documents may be available from a local system or via an internet connection, the second group of documents will require an internet connection. Note: A SimoTime License is required for the items to be made available on a local system or server.
Note: The latest versions of the SimoTime Documents and Program Suites are available on the Internet and may be accessed using the icon. If a user has a SimoTime Enterprise License the Documents and Program Suites may be available on a local server and accessed using the icon. This discussion will leverage the non-relational file support provided by Micro Focus for the distributed systems. Explore an Extended List of Software Technologies that are available for review and evaluation.
The software technologies or Z-Packs provide individual programming examples, documentation and test data files in a single package. For example Beaulieu and Bewley share the soundex code B Some software "breaks" when presented with accented characters. This can cause a problem when importing accented name and address data from legacy files into some mailing programs unless you remove the accents to "unaccent" it by removing each accent by substituting the unaccented character.
Calculate arithmetic expressions involving the the input fields e. Perform additional transformations using "plugin" programs which you write in almost any computer language. Eliminate duplicate records and non-identical records containing effectively duplicate data based on individual field analysis.
Insert "header" and "trailer" blocks in output files. This gives the ability, for example, to generate web pages of list-type data directly from a database.
Command Line Interface permits calls from shortcuts, batchfiles or other programs needing sophisticated input parsing. Interleaved Output. You may wish to use your output file as input to a mailmerge program which prints several mailing pieces on a single sheet of paper.
Interleaving records permits you to maintain the same sequence as your input records after cutting up the output stack. Standalone product. TextPipe does not rely on the presence of the database engines of other products its competition often does. The Siber Systems website has been abandoned since , and neither Data2Flat or Data Viewer software has been updated since Cobol Data Files Everywhere A lot of important data collected in the last 40 years by corporations and governments resides in Cobol data files.
Why Reading Cobol Data Is Hard Cobol data files do not contain information about their own organization and record structure. This statement tells the system how the file is organized: it contains file organization, file access mode, etc. FD statement for the file.
0コメント