|
We have a process where an AS/400 program creates a file off of Lawson, and this is downloaded via Client Access to the network, where I then manually run an Hyperion Essbase program to update Essbase with this Lawson data. I would like to automate, first by having the AS/400 program FTP the file and second, by having the AS/400 trigger the job on the network. I am having trouble with the second part, and was wondering if this is a simple matter or not. Thanks, Phil -----Original Message----- From: Carl Galgano [mailto:cgalgano2@ediconsulting.com] Sent: Wednesday, August 07, 2002 11:49 AM To: midrange-l@midrange.com Subject: RE: Achieving Shipping Compliance at Remote Locations Hi Rick: As with most issues, it depends.... Is DSL required, no, would any internet connection work.... Yes. If all you are doing is AS400 functions with some printing, a dial up connection would work well. Just off the top of my head here is how I would do it: 1. Set up some sort of VPN server on your internal network. If the PC server you are currently using is W2000 or NT, you have what you need. 2. Use a PC in each plant, each to have 2 parallel cards, one for a laser printer, one for the bar code printer. 3. Equip the PC with a bar code scanner 4. Have the PC connect via a dial up to the internet, then start the VPN connection to your internal network 5. Once you are connected, the PC looks like it is connected locally to the AS400. Of course it is not quite this simple, as you will need to be sure the AS/400 apps are up to snuff to perform the business tasks required. You may have some issues with the config of the printers, especially the bar code printer, but should not be much of a problem, it may require some trial and error. You will have to select a PC emulator that support the remote printing..... It can either be TN5250e or LPD/LPR. Most of the software out there is very inexpensive. Once you had a "hardware package" you were comfortable with, you could roll it out to each plant. If you go with a dial up connection, it should be pretty straight forward to the personal, if the connection drops, then have it dial again (persistent dial up). In my opinion, you can spend a lot of money on this, or not a lot of money, your choice. The solutions I am suggesting are pretty much the least expensive for initial costs, and recurring costs. Of course you could install frame relay, but to support one or 2 devices..... Why? Even DSL is relatively cheap. With DSL you could use a VPN router and ethernet connected printers. Just a few ideas for you to think over. cjg Carl J. Galgano EDI Consulting Services, Inc. 550 Kennesaw Avenue, Suite 800 Marietta, GA 30060 (770) 422-2995 - voice (419) 730-8212 - fax mailto:cgalgano@ediconsulting.com http://www.ediconsulting.com AS400 EDI, Networking, E-Commerce and Communications Consulting and Implementation http://www.icecreamovernight.com Premium Ice Cream Brands shipped Overnight "You ain't gonna learn what you don't want to know" - rw -----Original Message----- From: midrange-l-admin@midrange.com [mailto:midrange-l-admin@midrange.com] On Behalf Of Rick Rauterkus Sent: Wednesday, August 07, 2002 11:22 AM To: midrange-l@midrange.com Subject: RE: Achieving Shipping Compliance at Remote Locations Hi Carl, > Reading between the lines in your post, it seems to me that you are > leaning towards some sort of stand alone solution for your remote > plants? Yes, that's what I had in mind. > Why not have your remote plants connect to your AS/400? I don't think bandwidth would be a problem. Would only need a tube with a scanner, a label printer, and a laser printer on their end. Is DSL required? Or any Internet connection? Would our AS/400 have to be connected directly to the Internet somehow? Currently all access to the Internet here is handled through a PC server. This gateway and the AS/400 are on the same network. I am assuming the reliability and security of this solution are adaquate, or you probably wouldn't have suggestted it. Thanks for your input! Rick _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.