Re: Consuming (mounting) over a Windows NFS share from IBM i

[Evan Harris <auctionitis@xxxxxxxxx>]

Hi Rob

when we did this one other thing bit us: line endings were different on
document shared via NFS to those that had previously been picked up by a
different route (Windows file system shares).

There was some software (InfoSphere CDC) expecting the CRLF as per a
Windows share but instead it was now just a CR (or whatever) as per Unix.

Probably not an issue as most software seems to translate without issue but
also useful to be aware of.

On Thu, May 26, 2016 at 3:22 AM, Rob Berendt <rob@xxxxxxxxx> wrote:

> Thank you.
> The little things (like the CCSID) help.
>
>
> 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:   Gad Miron <gadmiron@xxxxxxxxx>
> To:     midrange-l@xxxxxxxxxxxx
> Date:   05/25/2016 11:08 AM
> Subject:        Re: Consuming (mounting) over a Windows NFS share from IBM
> i
> Sent by:        "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
>
>
>
> Hi Rob
>
> My 2 cents...
>
> We use NFS Mounts to Write documents (PDF, Excel) to  shared Windows
> directories and have them popped open on the user's PC (using STRPCCMD)
> without having users connecting (mapped) to IFS directories.
> You certainly can access these NFS mounts from the i.
>
> 1. create a Windows directory and share it using Windows shares and
> permissions
>     as well as NFS shares/permissions.
>    you have to set up the built in Windwos NFS server feature.
>    (we use Windows 2012 Server.)
>
> 2. create a IFS directory .
>
> 3. mount the Windows NFS dir . like the following
> ADDMFS     TYPE(*NFS) +
>              MFS('192.168.168.210:/NFS4AS400XLS') +
>              MNTOVRDIR('/NFS4AS400XLS') CCSID(1255 1255)
> (in this example the IFS dir name and the Windows one are both
>  NFS4AS400XLS  but it is not mandatory).
>  when looking at IFS directories using Navigator you get a visual
> indication
>  for NFS mounted directories - see following print screen..
>
> 4. On the i side you access the documents/files in the mounted Windows
> dir.
>     simply by accessing the local IFS directory as if it was a regular IFS
> dir.
>     (When saving IFS directories we get errors for these mounted NFS
> directories
>       but I'm pretty sure you can exclude them )
>
> 5. If you do not use SSO to log in to the i then you must synchronize user
> names & passwords between the i and the Windows domain.
> We instead authorize user "Anonymouse"  on the NFS Windows side so we
> can access the Windows dir from the i without authority issues.
>
> HTH
> Gad
>
> [image: Inline image 2]
>
> message: 6
> date: Fri, 20 May 2016 15:03:03 -0400
> from: Rob Berendt <rob@xxxxxxxxx>
> subject: Consuming (mounting) over a Windows NFS share from IBM i
>
> I would like to avoid using /QNTC to access Windows shares.  I've had too
> many strange issues based on things like length of share names, etc.
>
> I want to serve up a share on Windows using NFS.
> I then want IBM i to MOUNT over that share.
>
> I've done this between lpars of IBM i.
> I've used EXPORTFS on one lpar and MOUNTed from another.
>
> I'm sure that someone on this list has done so.  I am hoping that someone
> has some step-by-step instructions for both the Windows side, and the IBM
> i side.
>
> A system running under user QPGMR will be accessing this share.
> Vendor software (GoAnywhere MFT by Linoma).
> Internet  - - >   DMZ IBM i - - - - >  Windows (Intranet)
> https:  - - - >   GoAnywhere  - - - >  NFS Export
>
>
> 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
> --
> 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.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
>
> --
> 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.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.