Re: QNTC and Windows Server 2012

I'm confused, how is any of this "proprietary" when the specs are open and
widely known. Just because one vendor implements it first, as long as the
specs are open then it is not "proprietary". When the specs are closed,
then yes it is proprietary.

Linux/unix has been able to interoperate with samba just fine since 1992.

You can run a full fledge samba environment on the IBM i now that they
have ported it to the PASE environment, I believe it may even include the
smbclient the individual was looking for in addition to the server pieces.

See here: http://www-01.ibm.com/support/docview.wss?uid=nas8N1020089

This implementation is much better than IBM's proprietary and slow
implementation of NetServer. They finally threw in the towel and realized
they couldn't make a good one, and have now embraced the open source worlds
version of it.

Also, the previous poster was wondering why smbclient wasn't available,
well it is now. Read the above URL.


-----Original Message-----
From: Charles Wilt [mailto:charles.wilt@xxxxxxxxx]
Sent: Thursday, October 1, 2015 2:48 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: QNTC and Windows Server 2012

How would Windows networking be IBM proprietary?

Charles

On Thu, Oct 1, 2015 at 3:35 PM, Richard Schoen <
Richard.Schoen@xxxxxxxxxxxxxxx> wrote:

Well actually it's probably more like IBM proprietary :-)

Happy CPY-ing !!

Regards,

Richard Schoen | Director of Document Management Technologies,
HelpSystems
T: + 1 952-486-6802
RJS Software Systems | A Division of HelpSystems
richard.schoen@xxxxxxxxxxxxxxx www.rjssoftware.com Visit me on:
Twitter | LinkedIn

------------------------------

message: 5
date: Thu, 1 Oct 2015 19:18:11 +0000
from: Winchester Terry <terry.winchester@xxxxxxxxxxxxxxx>
subject: RE: QNTC and Windows Server 2012


We had a meeting earlier this week and I made a few remarks using the
phrase "MS-proprietary" ;-)

So one of the PC Admins set up WS4U and after a bunch of twiddling
with security we were able to succesfully use a MOUNT, CPY and UNMOUNT
command to move some data.

Now I need to do a little research on the viability of doing MOUNT's
within QSTRUP and/or doing them dynamically for each application.

Thanks ALL for the help!

Terry


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Vernon Hamberg
Sent: Friday, September 25, 2015 3:35 PM
To: Midrange Systems Technical Discussion
Subject: Re: QNTC and Windows Server 2012

LOL - just call it WS4U and tell them it's from Microsoft.

On 9/25/2015 2:11 PM, Winchester Terry wrote:

Vern...that is true! I think the aversion is the word "Unix" ;-)

It was my understanding that managing security around NFS services
required a bit more work too...but maybe that's not true.

TGIF

Terry

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf
Of Vernon Hamberg
Sent: Friday, September 25, 2015 12:19 PM
To: Midrange Systems Technical Discussion
Subject: Re: QNTC and Windows Server 2012

Terry

Windows Services for Unix IS from Microsoft, so they should not
averse

to it.

HTH
Vern

On 9/25/2015 9:14 AM, Winchester Terry wrote:

Of the two remaining preferences, it's probably easier to use NFS
but these are "windows" guys and they seem to have an aversion to
non-MS solutions so proposing that they run "services for NFS" is
not going to be my first recommendation.

We have a meeting slated for sometime next week. I am leaning
towards using standard FTP but that means they will have to run FTP
services on each of their file servers.

This will probably be the lessor of two evils in their eyes ;-)

I really wish that IBM support had various versions of SMBCLIENT
available for download based on the level of the O/S. I find it
hard to believe that, with all of their available talent, IBM can't
have an FTP site available with pre-compiled binaries for stuff like

this...

Terry

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf
Of Richard Schoen
Sent: Friday, September 25, 2015 10:01 AM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: QNTC and Windows Server 2012

Have them install Windows services for Unix and open up appropriate
NFS

shares.

Then you simply mount the servers from IBMi.

Regards,

Richard Schoen | Director of Document Management Technologies,
HelpSystems
T: + 1 952-486-6802
RJS Software Systems | A Division of HelpSystems
richard.schoen@xxxxxxxxxxxxxxx www.rjssoftware.com Visit me on:
Twitter | LinkedIn

------------------------------

message: 6
date: Fri, 25 Sep 2015 12:55:07 +0000
from: Winchester Terry <terry.winchester@xxxxxxxxxxxxxxx>
subject: QNTC and Windows Server 2012

Is it possible to use QNTC with the new version of Windows Server
2012

(R2)?

We're currently running SMBCLIENT 2.2.8 and it has served us well
for

years, but the Windows folks are doing some server upgrades to the new
2012 version and our Samba client is no longer working.

Based on a little research, it appears that only Samba versions
later than
3.6 will work with MS Server 2012. Since I am *not* a C-programmer
and

there doesn't appear to be any binaries available for our platform (at
V6R1) it seems that our only options are (1) Use QNTC, (2) Convince
the MS-Admins that they need to run the NFS server utilities on each
of their servers so that we can mount their drives or (3) Convince the
MS-Admins that we must use FTP to push files to each server.

I would prefer to use option (1) but it doesn't seem to work. So I

guess we're stuck with options (2) and (3)...

BTW, upgrading to a V7Rx is not likely to happen since we're slated
to move off the platform in the next 18-24 months (to outsourced
*NIX servers running
SAP)

Any thoughts?

Thanks,

Terry

Confidentiality Notice: The preceding e-mail message (including any

attachments) contains information that may be confidential, protected
by applicable legal privileges, or constitute non-public information.
It is intended to be conveyed only to the designated recipient(s). If
you are not an intended recipient of this message, please notify the
sender by replying to this message and then delete it from your
system. Use, dissemination, distribution or reproduction of this
message by unintended recipients is not authorized and may be unlawful.

--
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.

Confidentiality Notice: The preceding e-mail message (including any

attachments) contains information that may be confidential, protected
by applicable legal privileges, or constitute non-public information.
It is intended to be conveyed only to the designated recipient(s). If
you are not an intended recipient of this message, please notify the
sender by replying to this message and then delete it from your
system. Use, dissemination, distribution or reproduction of this
message by unintended recipients is not authorized and may be unlawful.

--
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.

Confidentiality Notice: The preceding e-mail message (including any

attachments) contains information that may be confidential, protected
by applicable legal privileges, or constitute non-public information.
It is intended to be conveyed only to the designated recipient(s). If
you are not an intended recipient of this message, please notify the
sender by replying to this message and then delete it from your
system. Use, dissemination, distribution or reproduction of this
message by unintended recipients is not authorized and may be unlawful.

--
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.

Confidentiality Notice: The preceding e-mail message (including any
attachments) contains information that may be confidential, protected
by applicable legal privileges, or constitute non-public information.
It is intended to be conveyed only to the designated recipient(s). If
you are not an intended recipient of this message, please notify the
sender by replying to this message and then delete it from your
system. Use, dissemination, distribution or reproduction of this
message by unintended recipients is not authorized and may be unlawful.



------------------------------

Subject: Digest Footer

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) digest
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.



------------------------------

End of MIDRANGE-L Digest, Vol 14, Issue 1402
********************************************
--
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.

--
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.


--
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.