|
I was missing the WINS configuration, but I just copied what my PC was set up for and it works great. Put this in your tool box for yet another method of 'How do I copy something from my 400 down to a PC?' 1) QNTC - by doing WRKLNK '/QNTC/*' 2) FTP 3) Client access ... The question I have is exactly what options do you use on CPY to copy from/to QNTC files. Let me guess, it varies by file type. Let's use the following examples, (don't assume, test) PC name will be MYPC: A) sample.txt notepad file from the PC to an IFS directory. B) sample.txt notepad file from the PC to a DB2 file. C) A in reverse D) B, in reverse E) /qsys.lib/mylib.lib/myfile.savf to a directory on the PC F) E, in reverse The reason I ask is because CPY OBJ('/QNTC/ROB/QTEMP/SPOOL.TXT') TODIR('/') give me CPFA098 And let me tell you something, if you have lots of PC's and you do a WRKLNK '/QNTC/*' you will definitely have time to go get a cup of coffee before the screen refreshes. A faster test to is make sure you have a share set up on a directory on your PC first (use Windows explorer). Then do WRKLNK '/QNTC/mypc/*' Rob Berendt ================== A smart person learns from their mistakes, but a wise person learns from OTHER peoples mistakes. "Mark Phippard" <MarkP@softlanding. To: MIDRANGE-L@midrange.com com> cc: Sent by: Subject: Re: QNTC owner-midrange-l@mi drange.com 05/31/01 12:12 PM Please respond to MIDRANGE-L Pete, Mark, QNTC is one of the coolest but least known features that have been added to OS/400 in recent years. /QNTC is the AS/400 equivalent of your Windows Network Neighborhood. When you browse into ths file system, all of the systems in your domain will automatically appear. When you browse a system, all of its shares will appear. When you browse a share all of the files will appear. The file system is fully supported, so you can copy files between directories and PC's from the green screen using this file system. Caveats: 1) The OS/400 NetServer function needs to be configured from OpsNav and running. The main things you configure are the name of your NT domain and the IP address of the WINS server for the domain. OS/400 needs this to resolve the IP address of the system. 2) You can see all of your systems, but you can only see the shares and files for NT/2000 systems. 3) The biggie. The user id and password of your green screen job must be a valid NT user name and password, and that NT user must be authorized to the share/file. This means if you are signed on as QSECOFR, you will not be able to access the shares of an NT system unless you have created a user in your NT network named QSECOFR and given it the exact same password. That should be enough to get you started. Mark Phippard Pete Massiello <pmassiello@os-solu To: MIDRANGE-L@midrange.com tions.com> cc: Sent by: Subject: Re: QNTC owner-midrange-l@mi drange.com 05/31/01 12:42 PM Please respond to MIDRANGE-L Mark, That is your NT FSIOP (or whatever the current name of the card is) data that is associated with your *NWSD. It always goes in the IFS, although some piece will also go in QUSRSYS as *SVRSTG. Pete MWalter@hanoverwire.com wrote: > Hello all, > > I was wondering around the IFS and found a QNTC folder. Does anyone else > have one and for what is it used? In the folder it looks like there are > disk images of a number of PC's on our network including two NT Servers. I > don't remember putting it there. > > thanks > > Mark > > Mark Walter > Sr. Programmer/Analyst > Hanover Wire Cloth a div of CCX, Inc. > mwalter@hanoverwire.com > http://www.hanoverwire.com > 717.637.3795 Ext.3040 > > +--- > | 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 > +--- -- Pete Massiello OS Solutions International Phone: (203)-744-7854 Ext 11. http://www.os-solutions.com mailto:pmassiello@os-solutions.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 +--- +--- | 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.