View Full Version : Client Access Express: Access IFS via System Name
05-17-2001, 12:44 PM
Go into Operations Navigator(Part of Client Access Express) Click on File Systems find the structure you want to share right mouse click select Sharing and create a share for this structure You can set permissions etc here too. When you access the share you will probably have to use Dir \Qmyas400users*.* I don't remember the reason for the Q before the systems name.
05-17-2001, 03:00 PM
Chris S, Programmatically, I need to launch an Excel document on the IFS from a green screen (w/STRPCCMD or other tool) so I need the path to be the same, regardless of whether the connection is via Client Access or Client Access Express (or Host on-demand?). Can I set a shared folder for Express that is the same name as the AS400 and is the root? I hope so because then I can just retrieve the system name with RTVNETA and plug that into the path. Example: \MyAs400docsExcel1.xls If this is not possible, then perhaps all users will have to manually map the same drive letter to the IFS. I really want to avoid this. Thanks. Chris R
05-17-2001, 03:11 PM
Why not use an environment variable to control the path name? That way you can set it one way for workstations with Client Access, and another way for workstations with Client Access Express? Joe
05-17-2001, 06:45 PM
Joe, Do you mean an old fashioned DOS environment variable? Hmmmm... that interesting. I could make that environment variable part of the string I pass down and DOS should do the substitution before the document loading occurs. I'm not sure if an environment variable set in autoexec.bat gets copied into a new DOS window or not. I'll have to try that. And in my case, I'd have to set two environment variables since we have both a development and a production AS/400 and incorporate the AS/400 system name into each DOS environment variable name. Thanks Joe. Chris
05-17-2001, 08:13 PM
Sometimes the old tried and true methods are the best.
05-22-2001, 06:13 AM
I had a similar problem but I fount that in our shop the file path \qmfpoer1 works for both client access and client access express to access our shared drives so it must be possible. I don't know if we had to do anything special to make that work. You might try setting up the qmyAS400 path for client access express as described in someone elses and see if the path name also works for a regular client access machine. Bill Hamaker
05-23-2001, 02:52 PM
Bill, Let me preface this message by saying I don't have C/A Express loaded on my PC nor do I have access to Ops Nav. You're solution worked. Our operations person renamed the netserver from MY400 to QMY400, shared a folder, restared the server and now both C/A and C/A Express PC's can access that folder. However, all documents open as "read-only" when accessing folder through the netserver. Is there something else that needs to be checked? I have *ALLOBJ and *RWX *ALL authority to the particular folder and documents. If I access the folder through //My400, I can still update the documents. Thanks! Chris Ringer
05-24-2001, 06:25 AM
Chris - When the share is set up, one must specify "read only" or "read/write". "Read only" is the default. Get your operations folks to revisit the share and change it to "read/write". You might also ask them to check whether "Maximum number of users" is "No maximum" or set to a specific number. HTH, Steve
05-24-2001, 07:18 AM
Some PCs here use Client Access (mine) and some use Client Access Express. From a DOS prompt, I can type Dir \MyAs400users*.* and get a listing of directories and files without the need to map a drive letter. How can do the same thing (use the system name instead of a mapped drive letter) on a PC that connects with Client Access Express? Thanks. Chris
05-24-2001, 07:18 AM
Steve, Thanks. That solved the problem. User authorities are a combination of both the "share" authority and the IFS authorities. We changed the "Share" authority to R/W and now both Client Access and Client Access Express users can access the share through one common path. Chris
Powered by vBulletin® Version 4.1.5 Copyright © 2013 vBulletin Solutions, Inc. All rights reserved.