|
Thanks Evan I always listen to Nathan ;) and I think you are probably right about the sna/ip decision. I am just dabbling at this point and I hate the extra complexity inherent in this idea anyway. Thanks for your thoughts they are much appreciated. Regards, Rick DuVall Systems Manager Dealer's Auto Auction of Okc 1028 S. Portland Oklahoma City, OK 73108 (405) 947-2886 rick@xxxxxxxxxx http://www.nothingisreal.com/dfki/no-word On Behalf Of Evan Harris Nathan's point about an additional point of failure is a good one. If possible applications using the DDM files should be coded on the basis that the file might not be there, probably via a user open or something similar. You want to avoid a scenario where using DDM creates an additional dependency such that each time a machine needs to off-line e.g. for backups or maintenance it affects other machines that might be requesting data and applications start failing with "File not Found" or similar messages. I would also avoid the Anynet connectivity option if possible - this can require a bit of work of an administrative nature when converting so you may as well set them up as IP in the first place, at it is likely to be more long-lived than SNA. regards Evan Harris
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.