The JTOpen library contains a class which has methods for the EBCDIC-to-ASCII conversion.
Ebcdic file viewer code#
Note: Because EBCDIC-to-ASCII conversions may be complex (since there are multiple EBCDIC code pages, and because the underlying file structure may be complex) it is helpful to know whether a conversion tool or process is already available in your organization. If a conversion protocol is already available, usually it is simplest to utilize the existing conversion. You can familiarize yourself with this feature through this worked example of a custom function. In addition, we'll use the "custom function" feature of the QuerySurge Flat File JDBC driver. After you download the zip, extract only the top-level jt400.jar file and deploy it to your project classpath. Note: You can find general project information about the JTOpen toolbox here. For the conversion, we'll use IBM's JTOpen library, an open source IBM Toolbox for Java access to IBM i resources.
Ebcdic file viewer how to#
In this example, we use a small EBCDIC file with a simple fixed-width layout to show how to set up EBCDIC-to-ASCII conversions via a custom plug-in function. This article shows the basic setup for an automated EBCDIC-to-ASCII conversion followed by a query against the ASCII version of the file. This procedure can usually be fully automated, via the custom "plug-in" feature of QuerySurge's flat file JDBC driver.
In order for QuerySurge to access the data in such files, the files need conversion to an ASCII format. Second, mainframe files are typically encoded using the IBM EBCDIC standard.
If mainframe files are part of your testing scheme, there are several steps that may be needed in order to incorporate them into your QuerySurge execution runs. First, files need to be moved from the mainframe to a network location where a QuerySurge Agent can access them.
0 kommentar(er)
