Are the AS/400s currently connected? Dave
Unconfigured Ad Widget
Collapse
Announcement
Collapse
No announcement yet.
Communicating between 2 AS400's
Collapse
X
-
Communicating between 2 AS400's
DDM was designed to handle only low-volume data transfer. It won't perform as well as the others when high-volume file transfer is required. All the rest can do the job. But when you are talking about regular, automated, high volume AS/400-to-AS/400 file trasfers, nothing beats SNADS. SNADS might not be the fastest of the lot, but none can provide the same service-level as SNADS: 1. Built-in repository for transmitted data (see WRKNETF command) 2. Built-in capability for encrypted transfer of security data (by user-id and/or by locations) 3. Convenient monitoring of file-sending status (see WRKDSTQ command)
Comment
-
Communicating between 2 AS400's
We have two package applications currently running on an AS400. A background job runs every 10 - 30 seconds to read the transaction file from one package to feed it as input to the other package. We now need to put the two applications on 2 different AS400's in the same computer room. What would be the best method to get the data from one system to the other? What kind of problems might I run up against. Data would need to be available from both systems for the standard inquiry programs in one of the packages. Thoughts...suggestions?
Comment
-
Communicating between 2 AS400's
SNADS is good if your sending a file but if you have 2 400's in the same shop then its best not to have duplicate data. Because duplicate data is bad data (it never stays in synch). If you just need to access certian records in a database you don't need to send the whole file to the other computer when you can just use DDM or SQL to retrieve those records. Sure, if your sending a file to a vendor for invoices or something, then you would want to use SNADS or FTP.
Comment
Comment