I did try that Lizette, Although it had done initializing other filesystype like zFS, UDS, INET etc, It has done nothing with NFS :-(
O/P of SETOMVS RESET=(00) ===> ================================================================================= SETOMVS RESET=(00) IEE252I MEMBER BPXPRM00 FOUND IN SYS1.PARMLIB BPXO036I PARMLIB OPTIONS IGNORED WHILE PROCESSING 851 PARMLIB MEMBER= BPXPRM00 SETOMVS RESET= IGNORES CTRACE MOUNT ROOT RUNOPTS FILESYS SWA ALTROOT. BPXF011I A FILE SYSTEM WITH FILESYSTYPE OR SUBFILESYSTYPE HFS 860 FAILED TO INITIALIZE. A DUPLICATE FILESYSTYPE/SUBFILESYSTYPE STATEMENT WAS FOUND IN PARMLIB MEMBER BPXPRM00. BPXF011I A FILE SYSTEM WITH FILESYSTYPE OR SUBFILESYSTYPE ZFS 861 FAILED TO INITIALIZE. A DUPLICATE FILESYSTYPE/SUBFILESYSTYPE STATEMENT WAS FOUND IN PARMLIB MEMBER BPXPRM00. BPXF011I A FILE SYSTEM WITH FILESYSTYPE OR SUBFILESYSTYPE AUTOMNT 862 FAILED TO INITIALIZE. A DUPLICATE FILESYSTYPE/SUBFILESYSTYPE STATEMENT WAS FOUND IN PARMLIB MEMBER BPXPRM00. BPXF011I A FILE SYSTEM WITH FILESYSTYPE OR SUBFILESYSTYPE UDS 863 FAILED TO INITIALIZE. A DUPLICATE FILESYSTYPE/SUBFILESYSTYPE STATEMENT WAS FOUND IN PARMLIB MEMBER BPXPRM00. BPXF011I A FILE SYSTEM WITH FILESYSTYPE OR SUBFILESYSTYPE INET 864 FAILED TO INITIALIZE. A DUPLICATE FILESYSTYPE/SUBFILESYSTYPE STATEMENT WAS FOUND IN PARMLIB MEMBER BPXPRM00. BPXF202I DOMAIN AF_UNIX WAS NOT ACTIVATED FOR FILE SYSTEM 865 TYPE UDS. RETURN CODE = 00000079, REASON CODE = 12030259 BPXF202I DOMAIN AF_INET WAS NOT ACTIVATED FOR FILE SYSTEM 866 TYPE INET. RETURN CODE = 00000079, REASON CODE = 743A0259 BPXO015I THE SETOMVS COMMAND WAS SUCCESSFUL. ===================================================================================== On Thu, Sep 17, 2015 at 12:02 PM, Lizette Koehler <[email protected]> wrote: > I would think doing what Dave said with BPX Parms and issuing the Set > command should bring in NFS. > > Lizette > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:[email protected]] On > > Behalf Of RCG > > Sent: Thursday, September 17, 2015 8:52 AM > > To: [email protected] > > Subject: Re: NFS Client implementation query > > > > And other catch is Lizette, The STC ID for this task has no OMVS > segment, I had > > requested the Security folks to get one for me > > > > On Thu, Sep 17, 2015 at 11:37 AM, RCG <[email protected]> wrote: > > > > > Hi Lizette, Interesting - > > > > > > Here is O/P of /D OMVS,PFS - > > > > > > -D OMVS,PFS > > > BPXO068I 11.35.21 DISPLAY OMVS 068 > > > OMVS 000F ACTIVE OMVS=(00) > > > PFS CONFIGURATION INFORMATION > > > PFS TYPE ENTRY ASNAME DESC ST START/EXIT TIME > > > INET EZBPFINI SOCKETS A 2015/09/13 06.42.27 > > > UDS BPXTUINT SOCKETS A 2015/09/13 06.37.38 > > > AUTOMNT BPXTAMD LOCAL A 2015/09/13 06.37.38 > > > ZFS IOEFSCM ZFS LOCAL A 2015/09/13 06.36.53 > > > HFS GFUAINIT LOCAL A 2015/09/13 06.36.52 > > > > > > PFS TYPE DOMAIN MAXSOCK OPNSOCK HIGHUSED > > > INET AF_INET 60000 27 35 > > > UDS AF_UNIX 10000 20 30 > > > > > > PFS TYPE FILESYSTYPE PARAMETER INFORMATION > > > HFS > > > CURRENT VALUES: FIXED(0) VIRTUAL(2009) > > > > > > PFS TYPE STATUS INFORMATION > > > AUTOMNT TIME=2015/09/13 06:42:11 SYSTEM=XXXX USER=OMVSKERN > > > POLICY=/etc/auto.master > > > > > > So can't see NFS here.. > > > > > > On Thu, Sep 17, 2015 at 11:34 AM, RCG <[email protected]> wrote: > > > > > >> Hi David, I think my issue quite close to " The z/OS NFS client is > > >> started when the z/OS UNIX file system is initialized and is > > >> persistent until z/OS UNIX is stopped", > > >> > > >> But I'm not certain what zOS UNIX file system it is refers to ? > > >> > > >> On Thu, Sep 17, 2015 at 11:30 AM, Lizette Koehler < > > >> [email protected]> wrote: > > >> > > >>> Does your STC have an OMVS Segment? > > >>> Have you set up your security correctly? > > >>> What is being mounted on the MF? Aix, Unix, Windows files? > > >>> Where does the client run? Where does the server run? > > >>> Please post any messages from the STC. > > >>> > > >>> > > >>> Do the following commands and see if NFS is there. Please post the > > >>> results. > > >>> > > >>> D OMVS,PFS > > >>> > > >>> > > >>> > > >>> And may review this, if you have not done so > > >>> http://www-03.ibm.com/systems/z/os/zos/features/nfs/ > > >>> > > >>> z/OS Network File System Guide and Reference SC23-6883-00 > > >>> > > >>> http://www-304.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm. > > >>> zos.v2r1.nfs/nfs.htm > > >>> > > >>> NFS configuration Section > > >>> > > >>> http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.z > > >>> os.v2r1.idan400/nfsconf.htm > > >>> > > >>> > > >>> Lizette > > >>> > > >>> > > >>> > -----Original Message----- > > >>> > From: IBM Mainframe Discussion List > > >>> > [mailto:[email protected]] > > >>> On > > >>> > Behalf Of RCG > > >>> > Sent: Thursday, September 17, 2015 8: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
