Try going without the PARM for now and see what happens. Here is what I use:
FILESYSTYPE TYPE(NFS) /* Network Files System */
ENTRYPOINT(GFSCINIT) /* Entrypoint for NFS Client */
/* PARM('') defaults PARM for NFS Client */
ASNAME(MVSNFSC,'SUB=MSTR')
/* Auto-started PROC *REQ* */
My MVSNFSC proc looks similar to yours. Take a look in your LOG files. I have
messages written in there, maybe these is something useful in there for you to
see.
_________________________________________________________________
Dave Jousma
Assistant Vice President, Mainframe Engineering
[email protected]
1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H
p 616.653.8429
f 616.653.2717
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of RCG
Sent: Thursday, September 17, 2015 11:11 AM
To: [email protected]
Subject: Re: NFS Client implementation query
Thanks Lizette -
Here is the PARMS that I have used in BPXPRMxx -
FILESYSTYPE TYPE(NFS)
ENTRYPOINT(GFSCINIT)
PARM('biod(6),Bufhigh(128),nfsv4domain(xxx.xxxx.com)')
ASNAME(MVSNFSC,'SUB=MSTR')
Here is the JCL for started task MVSNFSC -
==================================================================================================
//MVSNFSC PROC SYSNFS=SYS1
//********************************************************************
//* *
//* OS/390 NETWORK FILE SYSTEM CLIENT START UP PROC(HDZ11TC) *
//* *
//* CHANGE HISTORY *
//* change to log1 and 2 to move off tecwk volumes....cde 1/10/3 *
//* $L41=NFSC,HDZ11SE,960120,SJPLJST: NFS Client support *
//* $KAB0020=NFSC,HDZ11TC,970425,SJPLPKL: Update FMID *
//* *
//********************************************************************
//MVSCLNT EXEC PGM=BPXVCLNY,
// REGION=0M,
// TIME=1440
//*
//* STEPLIB CONSISTS OF NFSLIB AND LANGUAGE ENVIRONMENT LIBRARIES
//* CHANGE THE NAMES AS APPROPRIATE FOR YOUR INSTALLATION
//* NOTE: EACH OF THESE LIBRARIES MUST BE AUTHORIZED
//*
//* &TCPIP..TCPIP.DATA IS TCP/IP DATA FILE
//* &SYSNFS..NFSLIB IS OS/390 NETWORK FILE SYSTEM CLIENT
//* TARGET LIBRARY
//* &SYSLE..SCEERUN IS LANGUAGE ENVIRONMENT RUNTIME LIBRARY
//*
//SYSTCPD DD DISP=SHR,DSN=SYS3.OS.TCPIP.PROFILE.OS390R25(TCPDATA)
//STEPLIB DD DISP=SHR,DSN=&SYSNFS..NFSLIBE
// DD DISP=SHR,DSN=SYS1.LE.SCEERUN
//*
//*SYSPRINT DD SYSOUT=O
//SYSPRINT DD DUMMY,DCB=(LRECL=133,BLKSIZE=133,RECFM=F)
//********************************************************************
//* *
//* THE SYSMDUMP DATASET NEEDS TO BE PRE-ALLOCATED TO THE *
//* DCB SPECIFICATIONS REQUIRED BY SYSMDUMP *
//* *
//********************************************************************
//*SYSMDUMP DD DISP=SHR,DSN=&NFSPRFX..SYSMDUMP
//*OUTPUT DD SYSOUT=O
//OUTPUT DD DUMMY,DCB=(LRECL=133,BLKSIZE=133,RECFM=F)
//*SYSERR DD SYSOUT=O
//SYSERR DD DUMMY,DCB=(LRECL=133,BLKSIZE=133,RECFM=F)
//*
//********************************************************************
//* *
//* NFSCMSG1 AND NFSCMSG2 DD'S ARE *
//* THE TWO CLIENT LOG DATA SETS NEED TO BE PRE-ALLOCATED *
//* AS SEQUENTIAL FILES. *
//* THE DCB WILL BE SET TO (VB,LRECL=137,BLKSIZE=6144) *
//* ONCE MVSCLNT IS STARTED, REGARDLESS OF THE ALLOCATION DCB. *
//* INITIALLY, WE RECOMMEND SPACE=(CYL,(2,5),RLSE) *
//* *
//********************************************************************
//NFSCMSG1 DD DISP=SHR,DSN=SYS1.TCPIP.MVSNFSC.MSC1.LOG1
//NFSCMSG2 DD DISP=SHR,DSN=SYS1.TCPIP.MVSNFSC.MSC1.LOG2
============================================================================================
I do not have any defined checklist that I'm following. :-(
Regards,
On Thu, Sep 17, 2015 at 10:55 AM, Lizette Koehler <[email protected]>
wrote:
> Could you provide the JCL you are using and any commands that JCL is
> using? It might help clarify the issue. Mask any names you need to
>
> Also, if you have any detailed checklists you are using for this
> process, that would also be helpful to see.
>
> Lizette
>
>
> > -----Original Message-----
> > From: IBM Mainframe Discussion List
> > [mailto:[email protected]] On Behalf Of RCG
> > Sent: Thursday, September 17, 2015 7:43 AM
> > To: [email protected]
> > Subject: Re: NFS Client implementation query
> >
> > Thanks for the responses Scott & Allan.
> >
> > NFSv4 Client is to mount non mainframe server path under USS, I
> > believe
> that's the
> > solution available (Not sure if anything else, Please do direct me
> > if
> any)
> >
> > Allan, Not certain if that is spawning a server, Am quite new to
> > this
> and trying to
> > understand better, And so seeking advice from experts like you all..
> Like I said, This is
> > a request from Application team for them to mount external drives to
> z/OS USS
> >
> >
> >
> >
> > On Thu, Sep 17, 2015 at 9:53 AM, Staller, Allan
> > <[email protected]>
> > wrote:
> >
> > > Is it spawning a server (similar to FTP?). You start the task and
> > > it ends pretty quickly, However, there is an OMVS task spawned
> > > that stays
> up.
> > >
> > > e.g. S FTPD
> > > FTPD will end quickly, but on the OMVS side there is a process
> > > FTPDn where N is a single character (in my case 4) that stays up
> indefinitely.
> > >
> > > HTH
> > >
> > > <snip>
> > > Need expert advise here on the NFS Client implementation on zOS
> > > platform
> > >
> > > - I've configured the parms in BPXPRMxx.
> > > - Had set-up the STC proc in the active proclib
> > > - Had made necessary Security definitions (STC ID, definition to
> > > STARTED CLASS, dataset access)
> > >
> > > However, When I start the task, It starts and ends in less than
> > > minute although with CC = 0.
> > >
> > > Any recommendation why here ?
> > >
> > > Highly appreciate the pointers what is missing here please.
> > > </snip>
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send
> email to [email protected] with the message: INFO IBM-MAIN
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
[email protected] with the message: INFO IBM-MAIN
This e-mail transmission contains information that is confidential and may be
privileged. It is intended only for the addressee(s) named above. If you
receive this e-mail in error, please do not read, copy or disseminate it in any
manner. If you are not the intended recipient, any disclosure, copying,
distribution or use of the contents of this information is prohibited. Please
reply to the message immediately by informing the sender that the message was
misdirected. After replying, please erase it from your computer system. Your
assistance in correcting this error is appreciated.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
