Re: as400 as a samba/nt client

["Keith Carpenter" <CarpCon@xxxxxxx>]

Good idea about using a profile handle to work around the matching network
user/password issue.


I recently asked a QNTC related question in the C400 list but got no
response.  Maybe some on this list knows.

Using QNTC, I've tried compiling some code where the path the source (
CRTCMOD SRCSTMF(/QNTC/server/share/project/file.c) ) is on the W2K server.
I get a garbage compiler listing (untranslated ascii source).  When these
same source files are copied to a local IFS directory, the stuff compiles
OK.

The code pages as reported by WRKLNK are 437 for the IFS files and 1252 for
the network.  These are both ascii, so you'd think they'd both get
translated by the compiler.

It would seem this is a bug, but I've seen this problem on 3 separate
systems.  Has anyone tried compiling source with the SRCSTMF() parm ?   Did
it work from an QNTC or NFS share ?


Keith




----- Original Message -----
From: "Pete Hall" <pbhall@xxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Wednesday, May 07, 2003 10:04 PM
Subject: Re: as400 as a samba/nt client


> At 16:58 05/07/2003, Chad Whitten wrote:
> >is it possible to mount a samba/windows nt file share to a local folder
on
> >the as400?
> >we have on our as400 a web app that generates reports and such.
>
> Assuming that netserver is running, the NT share must be in the same
domain
> as the AS400. Supposedly, the shares will get mounted automatically at IPL
> time, but maybe only if they are in the same segment as the AS400. I've
> never had that luxury. All of our NT share names end in "$", so I always
> have to run MKDIR /QNTC/sharename, after which they are visible. MKDIR
runs
> verrrrry slowly, but once mounted, data access seems quite reasonable. In
> order to access the data from the AS400, the user name and password must
be
> identical on the AS400 and the NT domain. If that's not possible, you can
> get around the requirement by obtaining a profile handle to a user ID that
> does have an identical password on both systems. It's not necessary to
know
> the password, as long as the real user has *USE authority for the profile
> being adopted. With a little up front effort it has worked pretty well for
us.
>
>
> Pete Hall
> pbhall@xxxxxxxxxxxxx
> http://www.pbhall.us/
>
> _______________________________________________
> 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.cgi/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.
>
>