As400 Manual Pdf
Rosamunda Froats
There is a DB2 lite offering and I believe it is offered on the Windows and Linux platforms. The iSeries (AS/400) as well as z-Series (mainframe) use the "full version" of DB2 because it is integrated into the operating system. If I were you, I would ask the mainframe guys if they have the .NET ADO.NET driver from IBM and the connection information for you.
IBM has provided a good redbook on the subject of connecting to the AS/400 (i5). Basically you need to make sure you have the licensed product iSeries Access For Windows (5722-XE1) and you need to setup a data provider on the Systemi. The redbook discusses setting the provider up. The resource for 5722-XE1 is found on the IBM website.
Hope this helps -- feel free to post if there is additional information you need or if your administrators have questions about the setup. If you need additional info, make sure you post the OS version (like V5R4 or something like that)
You mentioned that you are accessing "files" from the AS/400 (aka iSeries, aka IBM i). A "file" is a table. A library is a collection, a record is a row and a field is a column. They are the same thing.
iSeries Access comes with a .NET ADO.NET driver. You can use that and then use SQL as one normally would in an MS SQL database. Some of the functions are different but you can use the manual to figure out those quirks.
It's important to understand that the DB2 engine is embedded in the operating system. Therefore any table in any place is part of the DB2 database. It is ABSOLUTELY NOT important how the file is created (e.g. SQL, RPG, CRTPF, JDBC, COBOL, C). Also, it is ABSOLUTELY NOT important if someone calls the object a file. Everything is really a database table that is in the scope of DB2. You can test that yourself by using the system catalog on the iSeries (e.g. SYSTABLES). Notice that you can find your table in that place. Also, notice that you can use any JDBC or ODBC software to access the data on the iSeries.
That having said, there are some subtle differences. First of all, the DB2 for iSeries is a 100% real DB2 application, but is missing some things from his fellows. For example, MERGE is available on Windows and Unix, but not on the iSeries. Check the IBM Information center for this.
On the iSeries you do have some other objects that can store data. Most used are the DATAAREA and the DTAQ. These objects are NOT part of the DB2 database. Something like the FIFO object on unix is not part of the database
At last but not least, you can work with DB2 the iSeries way, or the DB2 way. The iSeries way is available for guys that grew up with the AS400. For example, you use CATALOG/TABLE instead of CATALOG.TABLE. Normally you would use the DB2 way. Every tool with iSeries support that I know off, does also support the DB2 way. Choose that option and everything works like the books.
How we did it on the mainframe: using CICS web services, we have some transactions that serve up data using SOAP. From a programmer standpoint, it's essentially just writing to a TS queue. Then we use an WSDL generation tool provided by IBM to build the WSDL that describes the service accordingly (with methods, input/output parms, etc). Then on the .NET side, just add a web reference to the WSDL and you are on your way. One caveat: we had create a class that inherits the web service, and overrides GetWebRequest to set KeepAlive to false. You may need to do this as well.
Going the other way (mainframe acting as client), it's basically the same thing (a temp TS que write), except there are a couple different parameters required (such as the URL to the web server to be invoked, name of the method, etc).
There is probably a better way, but we couldn't figure out any other way. I believe we had to take the more difficult route because our OS is not MVS, but rather VSE, which is a cheaper version and does not have very many nice features as MVS. The initial code samples we referenced were written by Richard Smrcina.
Apart from cost-effectiveness, EDI, when integrated with AS400, offers manifold perks such as streamlined data exchange, error reduction by 80%, faster and secure transactions, improved accuracy, and much more.
EDI (Electronic Data Interchange) software unlocks a smooth exchange of data between 2 computer systems in a standard electronic format, replacing paper-based documents such as shipping addresses, invoices, sale orders, etc.
A human error can cost your business up to 80% defects, leading to pricey affairs and declining customer satisfaction, as per a study by the International Journal of Engineering Research and Applications.
Electronic Data Interchange technology facilitates the exchange of data and transactions in a few minutes, with better accuracy, leading to faster completion, better productivity, and improved efficiency to focus on other crucial business challenges.
AS400 (Application System/400) EDI technology takes you toward effective data collection, enhanced visibility, and in-depth analysis. As e-documents can be stored, shared, and processed in various IT systems, they unlock a seamless flow of information.
EDI AS400 solutions involve sensitive business data, requiring more than a one-way approach. With an inefficient security plan in action, the integrity and confidentiality of your EDI transactions are in doubt.
Consider this scenario: A temperature-sensitive shipment of medicinal drugs is being shipped via a refrigerated ship. The shipper and the carrier have an agreement on maintaining the required temperature throughout the transportation process.
An AI agent routinely observes the connected events and quickly identifies a non-compliant event. It also determines the need for a new shipment, figures out the most efficient source of replacement, renews the order, and even accepts an authorized return, with little to zero manual intervention.
Blockchain technology allows you to program a smart contract to control the temperature of the pharmaceuticals. Additionally, the stakeholders can access the blockchain to view the real-time temperature data of the shipment, enabling proactive decision-making.
Our dedicated team of EDI AS400 system professionals has been involved in every level of the Electronic Data Interchange development process for our AS-400 and non-AS/400 clients from diverse industries.
Ans: EDI AS400 system is beloved and adopted by millions of businesses for its tangible benefits such as faster commerce, data enrichment, elevated productivity, and not to forget cost efficiency. Unsurprisingly, it has witnessed a growth of 61% in the past years.
Ans: EDI system is used in a variety of useful ways in the healthcare arena. From insurance claims processing, insurance eligibility verification, patient statements, laboratory and diagnostic orders, supply chain management, etc. It has provenly reduced the administrative burden of the lifesavers and improved patient care coordination.
Ans: The EDI integration enables the e-communication of business information such as tax documents, inventory data, invoices, HR documents, customer orders, and more to your own ERP system, CRM, or back-office operations for easier collaboration.
This blog is brought to you by Integrative Systems. Feel free to share your business challenges, goals, and requirements at [email protected], and our team will get in touch with a detailed AS400 EDI strategy withing next 2 business days!
- IBM i (OS/400) version 6.1 or later.
- Your TCP/IP must be installed and working.
- You need an ILE RPG compiler.
Instructions
- Download the .ZIP file to your PC by right-clicking this link HTTP API distribution and choosing "Save Target As."
- Extract the data from the .ZIP file into a temporary location on your hard drive.
- Tip: If you are using a FreeBSD/Linux/Unix PC, use the following unzip command to make sure that the files are in Unix text format:
- unzip -a httpapi.zip
- Tip: Windows XP has an unzip tool built in. If you double-click the httpapi.zip file after you've downloaded it, it'll open up as a folder. There's a link on the left-hand side that lets you unzip all of the files, I suggest unzipping them to c:\httpapi or a similarly easy to remember location.
- Switch to the directory where you unzipped HTTPAPI.ZIP
C:\ > cd \httpapi - Run the batch file. It will FTP to your iSeries, create the LIBHTTP library, create the appropriate source files, and upload all of the source members. You have to pass parameters to tell it where your iSeries is, as well as your userid and password:
C:\HTTPAPI > upload ibmi.example.com bob mypassword - Skip ahead to the section entitled "Building the Source"Manual Upload to iSeriesNot everyone wants to use my batch file (bummer) so here are the steps that the batch file takes for you. Type them carefully to do this process manually:
Once you have created an export file for your GL transactions or AP invoices and downloaded it to your organization's network, you can import it into your accountingsystems. This topic outlines procedures to bring downloaded transaction and invoice files into Global Software's AS 400 accounting system. Instructions are also included for running several reports and for an optional procedure to generate a chase file for GL transactions.
This procedure outlines the manual process for importing journal vouchers. We recommend this method if you import journal vouchers no more than once a day. More frequent importing of journal vouchers is more efficient if you use an automatic job. Notes on how to run the job automatically are included at the end.
c80f0f1006