× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: QOpenSys name rules
  • From: Joel Fritz <JFritz@xxxxxxxxxxxxxxxx>
  • Date: Wed, 22 Nov 2000 13:13:49 -0800

You should do fine with directories created off the root.  

As far as universal access, it depends.  You may need to have file shares
created through NetServer, which I believe is a part of Client Access that
comes with the base operating system.  

You really owe it to yourself to check out the IFS intro manual.  It's
currently available on line in (Dis)InfoCenter.  That could change at any
moment. <g>  It's one of the readable and informative IBM manuals.
<evangelism>If you're in a networked environment and aren't using the IFS
for much of anything, it could change your life.  IMHO, the IFS is one of
the best arguments for continued use of the 400.  It allows the 400 to
coeexist with almost any other platform transparently.  Read the section on
QNTC for some interesting things you can do with/to your NT
network.</evangelism>  

> -----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: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

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.