, December 26, 2013 11:55 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: NFS mount problem between zOS and Linux
Hi all,
The mount command I tried last, after several variartions was the example
from the IBM manual:
mount -t nfs4 -o sec=sys proto=tcp Catweazle-zOS/hfs/jedsp/web /jedsp/web
There are no error
On 12/26/2013 at 12:55 PM, jan de decker jan.je...@gmail.com wrote:
The mount command I tried last, after several variartions was the example
from the IBM manual:
mount -t nfs4 -o sec=sys proto=tcp Catweazle-zOS/hfs/jedsp/web /jedsp/web
The typical mount syntax involves
hostname:/path/name
Is it possible to configure the NFS daemon so it uses SSL
credentials (~/.ssh/authorized_keys) rather than the
ever-so-funky mvslogin for:
o Classic data sets
o UNIX files (less important because we can serve from a UNIX
server any UNIX files we need to share).
Thanks,
gil
reference the path /u/cics/wsbinds and be redirected
to /u/wsbinds automatically.
From: Alan Field alan_c_fi...@bluecrossmn.com
To: IBM-MAIN@LISTSERV.UA.EDU,
Date: 07/19/2013 14:10
Subject:NFS automount help requested
Sent by:IBM Mainframe Discussion List IBM-MAIN
criticism.
Systems Programming: Guilty, until proven innocent John Norgauer 2004
-Original Message-
From: Alan Field [mailto:alan_c_fi...@bluecrossmn.com]
Sent: July 19, 2013 15:11
Subject: NFS automount help requested
[snip]
But I really want this to be automounted on LPAR B.
On LPAR B I
I have an NFS Server task running on LPAR A.
I export a directory /u/cics/wsbinds.
On LPAR B I can issue a mount for this directory using
MOUNT FILESYSTEM(wsbinds) +
TYPE(NFS)+
MOUNTPOINT('/u/cics/wsbinds')+
MODE(RDWR
http://publib.boulder.ibm.com/infocenter/zos/v1r11/index.jsp?topic=/com.ibm.zos.r11.idan400/cpn1co71.htm
Instead of automounting the file, I think you need to login to mount
the NFS, then logout to unmount it before accessing it from another
userid or system.
On Fri, Jul 19, 2013 at 2:10 PM, Alan
/06/2012 07:47 AM
Subject:Re: NFS Client Start Delay
Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU
On Fri, 6 Jul 2012 07:35:27 +0530, saurabh khandelwal
sourabhkhandelwal...@gmail.com wrote:
I started NFS client at 23.35.45 but it actually started
Saurabh,
just a couple of questions:
I started NFS client at 23.35.45 but it actually started at 00.10.15e. So,
it took more then 30 min to start. Not sure, why this is happening.
When did you receive the BPXI004I OMVS INITIALIZATION COMPLETE message ?
Do you have a shared USS file system
Hello Walter,
Yes, we have shared USS file system. We get
BPXI004I message before the NFS client start completely. Please look at the
below job log.
*BPXI004I OMVS INITIALIZATION COMPLETE*
IEF404I BPXAS - ENDED - TIME=23.09.35
IEF404I BPXAS - ENDED - TIME=23.09.35
would presume that the
NFS Client
cannot start if OMVS is not completely initialized.
Walter Marguccio
z/OS Systems Programmer
BELENUS LOB Informatic GmbH
Munich - Germany
--
For IBM-MAIN
On Fri, 6 Jul 2012 07:35:27 +0530, saurabh khandelwal
sourabhkhandelwal...@gmail.com wrote:
I started NFS client at 23.35.45 but it actually started at 00.10.15e. So,
it took more then 30 min to start. Not sure, why this is happening.
Is there any thing to do with parallel sysplex or something
On Fri, 6 Jul 2012 08:44:31 -0700, Skip Robinson jo.skip.robin...@sce.com
wrote:
Delay cause seems to be crucial here. I haven't seen anyone comment on
what I consider to be OP's unusual configuration. If I understand the
original post, two out of three 'sysplex' members are parallel while the
Hello Lizette,
We have NFS ( Server and Client) setup on our z/OS
systems. In our environment
1) We have three system are in sysplex. out of them two are in parallel
sysplex. All three z/OS system version are 1.11.
2) We also using netview script to bring down and Ipling
IN SYS1.PARMLIB
01.38.46 STC00122 GFSC284I NETWORK FILE SYSTEM CLIENT COULD NOT GET GSS
CREDENT
291 FOR THE NFS CLIENT : GSS API krb5_get_default_realm()
FAILED
291 WITH GSS MAJOR STATUS 96C73ADF GSS MINOR STATUS
01.38.46 STC00122 GFSC700I z/OS NETWORK FILE SYSTEM
01.38.36 STC00122 $HASP373 MVSNFSC STARTED
01.38.36 STC00122 IEF403I MVSNFSC - STARTED - TIME=01.38.36
01.38.36 STC00122 IEE252I MEMBER CTINFC00 FOUND IN SYS1.PARMLIB
01.38.46 STC00122 GFSC284I NETWORK FILE SYSTEM CLIENT COULD NOT GET GSS
CREDENT
291 FOR THE NFS CLIENT : GSS API
101 - 116 of 116 matches
Mail list logo