Re: Scanning to IFS Directory

[Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>]

It's not possible for a copier to access the IFS directly, unless the 
copier is running IBM i, in which case it can access it's own internal 
IFS, but not one on another computer.

Or, at least, that would be my answer if I thought she was using the 
right term.

The copier could potentially use NFS, Windows Networking (SMB) / 
NetServer, HTTP or FTP.  Absolutely.  I totally agree with that.  But 
that's not "direct to the IFS", is it?  It's "via NFS to the IFS" or 
"via SMB to the IFS".

Note that in my reply to Candy, I did not take her to task for the wrong 
terminology.  I only explained it later, because SJL appeared to 
misunderstand her, because he thought she really meant IFS.

I'm very tired of people trying to make me look bad, like I'm being a 
jerk.  I'm trying to help.

I should quit these assinine mailing lists... they're good for nothing 
but aggravation, lately.


On 3/30/2011 7:21 AM, Charles Wilt wrote:
> Scott,
>
> I think IFS is the right term...
>
> Candy said, "We need to be able to scan directly into a directory on
> the IFS from either a scanner or a copier..."
>
> That is 100% correct.  She's telling us exactly what she wants to end up with.
>
> The i supports at least 4 servers that could allow external access to the IFS
> 1) Windows File sharing (aka SMB or Netserver)
> 2) Network File System (aka NFS)
> 3) FTP
> 4) HTTP
>
> Given Candy's next statement, "We have set up a shared directory on
> the IFS..." it is likely that she's talking about using Netserver, but
> she could be talking NFS.
>
> It's also probable that the copier supports FTP and/or HTTP which may
> be an option she hasn't considered.
>
> Candy, which clients does the copier support?
>
> If windows file sharing, can you see the shared directory from a PC?
>
> Charles