RE: NFS Mount

[Peter Connell <Peter.Connell@xxxxxxxxxx>]

Rob,
Is there a dummies guide to getting NFS working on i5 (including any necessary Windows config)
Peter

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Monday, 3 June 2013 2:22 p.m.
To: Midrange Systems Technical Discussion
Subject: Re: NFS Mount

NetServer:  Serving file shares from your IBM i.  Works ok.  This OS isn't the fastest for stream file serving but it works.
QNTC:  A method for IBM i to consume shares served from other platforms. 
Lots of people using it.  Has some of the strangest quirks that make it a "your results may be unreliable".  For example, if someone creates a share on a windows PC with a name longer than ?14? characters and even if the share you're trying to access is only 8 characters just the fact that a larger share exists your results may not be reliable.  Amazingly enough the same problem also plagues the Z os.  A DCR to get IBM to fix this was flat out rejected.
NFS:  IBM i can either serve NFS (see EXPORTFS) or consume NFS served by other platforms (see MOUNT).  See also STRNFSSVR.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to:  2505 Dekko Drive
          Garrett, IN 46738
Ship to:  Dock 108
          6928N 400E
          Kendallville, IN 46755
http://www.dekko.com





From:   Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
To:     Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>, 
Date:   06/02/2013 02:10 AM
Subject:        Re: NFS Mount
Sent by:        midrange-l-bounces@xxxxxxxxxxxx



I don't know about Peter's scenario completely, but one big reason to go 
with NFS is to get files off of local disk. To, for example, to put them 
on a SAN. There can be various reasons to do this, of course.

What you suggest is exactly right, IF you are ok with leaving these 
files on local DASD, which might not be an option - 92% disk usage, 
anyone?

Vern

On 6/2/2013 1:00 AM, Alan Campin wrote:
> Maybe I am missing something but we not just go into Netserver and 
create a
> share? As far as Windows is concerned it is just another network share.
>
>
> On Sat, Jun 1, 2013 at 9:39 PM, Richard Schoen 
<richard@xxxxxxxxxxxxxxx>wrote:
> > If you want i to mount a Windows drive share, enabled Windows Services 
for
> > Unix NFS server support.
> >
> > Otherwise you could enabled the NFS server on i and mount the IFS 
shares
> > from Windows.
> >
> > I would recommend the first option.
> >
> > Regards,
> > Richard Schoen
> > RJS Software Systems Inc.
> > Where Information Meets Innovation
> > Document Management, Workflow, Report Delivery, Forms and Business
> > Intelligence
> > Email: richard@xxxxxxxxxxxxxxx
> > Web Site: http://www.rjssoftware.com
> > Tel: (952) 736-5800
> > Fax: (952) 736-5801
> > Toll Free: (888) RJSSOFT
> > ------------------------------
> >
> > message: 2
> > date: Sun, 2 Jun 2013 10:56:01 +1000
> > from: Peter Connell <Peter.Connell@xxxxxxxxxx>
> > subject: NFS mount
> >
> > I want to load a file in a database on SQL Server 2008 R2 using SQL 
bulk
> > insert from a csv file.
> > So that I can use the IFS on the i5 I would like to mount the SQL 
server
> > using the MOUNT command but need some advice as this is new to me.
> > The MOUNT cmd  has the format MOUNT TYPE(*NFS) MFS(?????)
> > MNTOVRDIR(??????) and I need to know what to specify for MFS and 
MNTOVRDIR
> > The host name of the SQL Server box is nzaklgl-db601.corp.bayadv which 
can
> > be pinged from the i5 and returns an IP address of 10.9.64.65
> > If I log on to the SQL Server machine and look at the drives via 
Windows
> > Explorer I see the following
> >
> > Computer
> >                  OS(C:)
> >                  Data(F:)
> >                  Logs(H:)
> >                  Work(I:)
> >                  Backup(K:)
> >                  ...
> >                  ...
> >
> > I figure that I need a folder in one of these drives to be the target 
of
> > the MOUNT.
> > So what do I specify for MFS and MNTOVRDIR?
> >
> > Peter
#####################################################################################
> > This correspondence is for the named person's use only. It may contain
> > confidential
> > or legally privileged information, or both. No confidentiality or
> > privilege is waived
> > or lost by any mistransmission. If you receive this correspondence in
> > error, please
> > immediately delete it from your system and notify the sender. You must 
not
> > disclose,
> > copy or rely on any part of this correspondence if you are not the
> > intended recipient.
> > Any views expressed in this message are those of the individual sender,
> > except where
> > the sender expressly, and with authority, states them to be the views 
of
> > Veda.
> > If you need assistance, please contact Veda on either :-
> > Australia 1300-762-207 or New Zealand +64 9 367 6200
> >
> >
> >
> > --
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.