|
Jim, No, we can not use any of the OS/400 commands because we are not using 36 environment on the AS/400. The S/36 is set up as a virtual machine on the AS/400. Once a user is working in the S/36 the operating system is still SSP and any files on the AS/400 can not be accessed. Only files on the S/36 can be accessed. The two machines act as if they were totally independent even though the S/36 is really only an object on the AS/400. Does that make more sense?? Regards, Keith. -----Original Message----- From: owner-midrange-l@midrange.com [SMTP:owner-midrange-l@midrange.com] Sent: 09 November 1999 16:38 To: MIDRANGE-L@midrange.com Subject: Re: Transferring files from NT to System/36 Okay, so you are running the S/36 emulation on an AS/400. Any file on the AS/400 you can use in your S/36 environment using OVRDBF. If you want to place the file in QS36F then you don't' have to do an OVRDBF. You can transfer the file via OS/400 FTP. Just because you are running S/36 emulation you can still run any and all OS/400 commands. In fact, you can place OS/400 CL commands in PRCs and they run fine. Now, as I understand it you have one machine, right? You can transfer the files using FTP, client access, or whatever. I don't think I am understanding the problem fully. Regards, Jim Langston keith.nolan@dubport.ccs.ie wrote: > Patrick, > > 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?? +--- | 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 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 +---
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.