• Subject: RE: Transferring files from NT to System/36
  • From: "Jordan Waterhouse" <jrwaterhouse@xxxxxxx>
  • Date: Tue, 9 Nov 1999 09:28:30 -0600
  • Importance: Normal

On November 9, you wrote:

The system we use is using OS/400.  This is the operating system used by the
machine.  But once this operating system has IPL'd then we start a 36
machine (M36 Object) on this system which we have configured so that it
takes control of about 90% of our devices, so as far as the majority of our
users are concerned they are still using SSP and the older S/36.  They work
into the S/36 and never see the OS/400 which is behind it.  The problem is
that it is the system/36 that I want to transfer the files to so that some
of our older applications can use the data in these files.  Does that make
it any clearer??

We have the exact same setup here at Rogers Water Utilities.  We use Client
Access to move files to and from the AS/400 and use a Network Resource
Directory (HELP DDM, option # 3) on the virtual System/36 to point the
System/36 file name to the directory and name on the AS/400.  Programs on
the AS/400 and System/36 can both use the same file without having to move
it to the System/36.  To use this, you need to make sure you have ILAN up
and operational on the AS/400 and the System/36.

Jordan Waterhouse
Rogers Water Utilities
Jrwaterhouse@usa.net


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 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].