Using Netserver to share directories in the IFS works without any Client Access installed. But I cannot remember when Netserver was introduced to the AS400. Was is available in 3.2? I think so. Windows clients cannot tell the difference between Unix, NT or AS400 shares, supposedly. Christopher K. Bipes mailto:ChrisB@Cross-Check.com Sr. Programmer/Analyst mailto:Chris_Bipes@Yahoo.com CrossCheck, Inc. http://www.cross-check.com 6119 State Farm Drive Phone: 707 586-0551 x 1102 Rohnert Park CA 94928 Fax: 707 586-1884 If consistency is the hobgoblin of little minds, only geniuses work here. Karen Herbelin - Readers Digest 3/2000 -----Original Message----- From: D.BALE@handleman.com [mailto:D.BALE@handleman.com] Sent: Wednesday, November 22, 2000 12:13 PM To: MIDRANGE-L@midrange.com Subject: RE: QOpenSys name rules OK, copied it to the IFS root, no problems using a long filename from there. One of the issues I'm dealing with here is that I'm developing an application that will make me the next Brad Stone <g> and it requires copying an AS/400 file to a location from where Microsoft Word can insert the file into a document. So I need to keep it as flexible as possible in terms of all the different AS/400 setups out there for potential customers. I need to think in terms of OS/400 release independence (V3R2 on up) and different users' client software and hardware. Which brings up another question. Is my ability to map a drive in Windows Explorer dependent on using Client Access? If it is, how do non-CA Windows users gain access to the IFS? Also, I'm not sure I really want to dump these files into the IFS root, so I did another test creating a BALED directory in the root directory, copying the file there; the long filename appeared to work fine in this case as well. Regarding AS/400 security, is this something I'll be able to "get away with" on most AS/400s out there? John Earl, comments? Dan Bale IT - AS/400 Handleman Company 248-362-4400 Ext. 4952 +--- | 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: firstname.lastname@example.org +---
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.