Re: NFS Export of Data Set File System
On Wed, 10 Jan 2024 10:02:54 -0600, Lionel B. Dyck wrote: >Not to argue - they should have a User's Guide but they don't. The key with >dsfs is that once you understand the /dsfs/type (txt/bin/rec/sysout) that is >it no different than using any other file in a filesystem. > Case sensitivity? Directory links to files in other directories? Symbolic links? Concurrent updates to the same file by multiple jobs with O_APPEND? Unless such things are handled transparently by the "Colony address space" and the "Utility file system" there's need for a User's Guide. The product shouldn't have gone to GA without one. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS Export of Data Set File System
Not to argue - they should have a User's Guide but they don't. The key with dsfs is that once you understand the /dsfs/type (txt/bin/rec/sysout) that is it no different than using any other file in a filesystem. Lionel B. Dyck <>< Github: https://github.com/lbdyck “Worry more about your character than your reputation. Character is what you are, reputation merely what others think you are.” - - - John Wooden -Original Message- From: IBM Mainframe Discussion List On Behalf Of Paul Gilmartin Sent: Wednesday, January 10, 2024 10:00 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: NFS Export of Data Set File System On Wed, 10 Jan 2024 09:12:29 -0600, Lionel B. Dyck wrote: >There is no users guide ... > Has IBM not noticed the lack? >... but there is an admin guide at > https://www.ibm.com/docs/en/zos/3.1.0?topic=administration-dsfs-guide > That's for admins. But if there are differences between DSFS and a POSIX filesystem they should be described in a User's Guide. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS Export of Data Set File System
On Wed, 10 Jan 2024 09:12:29 -0600, Lionel B. Dyck wrote: >There is no users guide ... > Has IBM not noticed the lack? >... but there is an admin guide at > https://www.ibm.com/docs/en/zos/3.1.0?topic=administration-dsfs-guide > That's for admins. But if there are differences between DSFS and a POSIX filesystem they should be described in a User's Guide. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS Export of Data Set File System
But, if you're willing to pay, this can do it - https://virtualzcomputing.com/ On Wednesday, January 10th, 2024 at 20:36, Paul Gilmartin <042bfe9c879d-dmarc-requ...@listserv.ua.edu> wrote: > On Wed, 10 Jan 2024 14:37:22 +, Mark Jacobs wrote: > > > Can /dsfs and the directories under it be NFS exported such that > > Windows/Linux clients can connect to it and then directly read/write z/OS > > datasets? > > What are you looking for beyond: > https://www.ibm.com/docs/en/zos/3.1.0?topic=introduction-zos-conventional-mvs-data-sets > > > Where's the DSFS User's Guide, which ought to treat such topics? > > -- > gil > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAINBu -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS Export of Data Set File System
There is no users guide but there is an admin guide at https://www.ibm.com/docs/en/zos/3.1.0?topic=administration-dsfs-guide Lionel B. Dyck <>< Github: https://github.com/lbdyck “Worry more about your character than your reputation. Character is what you are, reputation merely what others think you are.” - - - John Wooden -Original Message- From: IBM Mainframe Discussion List On Behalf Of Paul Gilmartin Sent: Wednesday, January 10, 2024 9:07 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: NFS Export of Data Set File System On Wed, 10 Jan 2024 14:37:22 +, Mark Jacobs wrote: >Can /dsfs and the directories under it be NFS exported such that Windows/Linux >clients can connect to it and then directly read/write z/OS datasets? > What are you looking for beyond: <https://www.ibm.com/docs/en/zos/3.1.0?topic=introduction-zos-conventional-mvs-data-sets> Where's the DSFS User's Guide, which ought to treat such topics? -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS Export of Data Set File System
On Wed, 10 Jan 2024 14:37:22 +, Mark Jacobs wrote: >Can /dsfs and the directories under it be NFS exported such that Windows/Linux >clients can connect to it and then directly read/write z/OS datasets? > What are you looking for beyond: <https://www.ibm.com/docs/en/zos/3.1.0?topic=introduction-zos-conventional-mvs-data-sets> Where's the DSFS User's Guide, which ought to treat such topics? -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS Export of Data Set File System
Ah yes sorry. Although what I said sounds "interesting", thinking about it a bit more, I don't think what I said below is possible. User has to interact with the unionfs and the "root" of it has to be NFS (for reachability over network). But, I don't think NFS allows its sub-tree or whatever to be anything other than further NFS sub-mounts. On Wednesday, January 10th, 2024 at 20:20, Mark Jacobs <0224d287a4b1-dmarc-requ...@listserv.ua.edu> wrote: > Do you mean the Union File System? > > Mark Jacobs > > Sent from ProtonMail, Swiss-based encrypted email. > > GPG Public Key - > https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com > > > On Wednesday, January 10th, 2024 at 9:42 AM, kekronbekron > 02dee3fcae33-dmarc-requ...@listserv.ua.edu wrote: > > > > > Something called OverlayFS was recently added to zOS. > > So in theory, > > > > top-level overlayfs --> NFS mount in zOS --> DSFS underneath (serving some > > paths/directories for the overlayFS) > > > > ... this sounds possible? > > > > On Wednesday, January 10th, 2024 at 20:07, Mark Jacobs > > 0224d287a4b1-dmarc-requ...@listserv.ua.edu wrote: > > > > > Can /dsfs and the directories under it be NFS exported such that > > > Windows/Linux clients can connect to it and then directly read/write z/OS > > > datasets? > > > > > > Mark Jacobs > > > > > > Sent from ProtonMail, Swiss-based encrypted email. > > > > > > GPG Public Key - > > > https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com > > > > > > -- > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS Export of Data Set File System
Do you mean the Union File System? Mark Jacobs Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com On Wednesday, January 10th, 2024 at 9:42 AM, kekronbekron <02dee3fcae33-dmarc-requ...@listserv.ua.edu> wrote: > Something called OverlayFS was recently added to zOS. > So in theory, > > top-level overlayfs --> NFS mount in zOS --> DSFS underneath (serving some > paths/directories for the overlayFS) > > > ... this sounds possible? > > > > On Wednesday, January 10th, 2024 at 20:07, Mark Jacobs > 0224d287a4b1-dmarc-requ...@listserv.ua.edu wrote: > > > > > Can /dsfs and the directories under it be NFS exported such that > > Windows/Linux clients can connect to it and then directly read/write z/OS > > datasets? > > > > Mark Jacobs > > > > Sent from ProtonMail, Swiss-based encrypted email. > > > > GPG Public Key - > > https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS Export of Data Set File System
Something called OverlayFS was recently added to zOS. So in theory, top-level overlayfs --> NFS mount in zOS --> DSFS underneath (serving some paths/directories for the overlayFS) ... this sounds possible? On Wednesday, January 10th, 2024 at 20:07, Mark Jacobs <0224d287a4b1-dmarc-requ...@listserv.ua.edu> wrote: > Can /dsfs and the directories under it be NFS exported such that > Windows/Linux clients can connect to it and then directly read/write z/OS > datasets? > > Mark Jacobs > > Sent from ProtonMail, Swiss-based encrypted email. > > GPG Public Key - > https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
NFS Export of Data Set File System
Can /dsfs and the directories under it be NFS exported such that Windows/Linux clients can connect to it and then directly read/write z/OS datasets? Mark Jacobs Sent from [ProtonMail](https://protonmail.com), Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DSFS vs. NFS vs. BPAM ...
Instead of complaining, I'm just going to say thanks to whoever thought this up and did the work. I haven't had a chance to look at the doc much yet, but the txt/rec/bin directories to handle the issue of different access methods seems inspired. On 5/6/2022 8:39 AM, Paul Gilmartin wrote: On Fri, 6 May 2022 12:43:30 +, Clifford McNeill wrote: IBM's Native American name shall be Broken-Link. Cliff Which leads me to wonder, how will DSFS represent a broken symbolic link in a PDSE member? On Fri, 6 May 2022 08:46:24 -0500, Bill Schoen wrote: "Good Job IBM!" "'Bout Damn Time".. but also "Where's the rest (VSAM, VBS, z/OS to OMVS) ? RECFM=VBS,LRECL=X would seem to be the natural representation of a file which might contain more than 32760 bytes between LFs. At the moment there still is a development team. It seems that for the interim (of possibly arbitrary duration) there's need for a "DSFS limitations and Restrictions" manual. Should I expect differences in the outcome of: cp source //\'my.pdse(member)\' # and cp source /dsfs/my.pdse/member # ? (Also, does DSFS obey TSO DSN prefixing?) What does "some-command >>/dsfs/my.pdse/member" do? Does it copy to do the append? Will "some-command >>/dsfs/my.ps.log.file" perform the append without the ENQ EXC of DISP=MOD? Suppose a PDSE contains members created by ISPF, with stats, and others created by (e.g.) IEBGENER with no stats. Will DSFS fall back to FAMS metadata as NFS does: <https://www.ibm.com/docs/en/zos/2.2.0?topic=sets-time-stamps-pdss-pdses>? How consistent will the behavior be among: o Accessing a PDS(E) as DSFS via ISPF 3.17 o Accessing directly as a DSN via other ISPF services o Accessing from a (Linux) desktop via NFS. Case insensitivity is a bane! In some of the instances above, the user will see member names in UPPER case; in others, lower. Consistency should prevail, allowing orderly copy/paste from one member display to a command line. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
DSFS vs. NFS vs. BPAM ...
On Fri, 6 May 2022 12:43:30 +, Clifford McNeill wrote: >IBM's Native American name shall be Broken-Link. >Cliff > Which leads me to wonder, how will DSFS represent a broken symbolic link in a PDSE member? On Fri, 6 May 2022 08:46:24 -0500, Bill Schoen wrote: >>> "Good Job IBM!" "'Bout Damn Time".. but also >>> "Where's the rest (VSAM, VBS, z/OS to OMVS) ? > RECFM=VBS,LRECL=X would seem to be the natural representation of a file which might contain more than 32760 bytes between LFs. >At the moment there still is a development team. > It seems that for the interim (of possibly arbitrary duration) there's need for a "DSFS limitations and Restrictions" manual. Should I expect differences in the outcome of: cp source //\'my.pdse(member)\' # and cp source /dsfs/my.pdse/member # ? (Also, does DSFS obey TSO DSN prefixing?) What does "some-command >>/dsfs/my.pdse/member" do? Does it copy to do the append? Will "some-command >>/dsfs/my.ps.log.file" perform the append without the ENQ EXC of DISP=MOD? Suppose a PDSE contains members created by ISPF, with stats, and others created by (e.g.) IEBGENER with no stats. Will DSFS fall back to FAMS metadata as NFS does: <https://www.ibm.com/docs/en/zos/2.2.0?topic=sets-time-stamps-pdss-pdses>? How consistent will the behavior be among: o Accessing a PDS(E) as DSFS via ISPF 3.17 o Accessing directly as a DSN via other ISPF services o Accessing from a (Linux) desktop via NFS. Case insensitivity is a bane! In some of the instances above, the user will see member names in UPPER case; in others, lower. Consistency should prevail, allowing orderly copy/paste from one member display to a command line. -- Thanks, gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS client RC=13 SDB/IRWD VALIDATION ERROR
Trying to write to a system message log which isn't allocated. MSTR has allocated a temp file and the attributes are incomplete. Check your JCL, SMS rules. Could just be SYSOUT. On Sun, Dec 26, 2021 at 8:20 PM Peter wrote: > Hello > > I am receiving the below error message while starting the NFS client. I > understand that one of the DD output file is bad. So SYS00012 refers to > which DD ? How to see the DD name refering to SYS value ? > > IEF196I IEF285I VOL SER NOS= OSREST. > > IEF196I IEF285I SYS1.IBM.PARMLIB KEPT > > IEF196I IEF285I VOL SER NOS= OSREST. > > BPXO015I THE SETOMVS COMMAND WAS SUCCESSFUL. > > IEF196I IEF237I 5301 ALLOCATED TO SYS5 > > IEF196I IEF285I TCPIP.TCPIP.DATA KEPT > > IEF196I IEF285I VOL SER NOS= OSSYB1. > > IEF196I IEF237I 5301 ALLOCATED TO SYS9 > > IEF196I IEF285I TCPIP.TCPIP.DATA KEPT > > IEF196I IEF285I VOL SER NOS= OSSYB1. > > IEF196I IEF237I 5301 ALLOCATED TO SYS00011 > > IEF196I IEF285I TCPIP.STANDARD.TCPXLBIN KEPT > > IEF196I IEF285I VOL SER NOS= OSSYB1. > > IEF196I IEF237I MSTR ALLOCATED TO SYS00012 > > $HASP708 MVSNFSC OPEN FAILED 746 > > RC=13 SDB/IRWD VALIDATION ERROR > > IEF196I IEC141I 013-C0,IGG0199G,MVSNFSC,MVSNFSC,SYS00012 > > IEC141I 013-C0,IGG0199G,MVSNFSC,MVSNFSC,SYS00012 747 > > IEF196I IEF285I JES2.MVSNFSC .MS.SYS00012 SYSOUT > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Wayne V. Bickerdike -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
NFS client RC=13 SDB/IRWD VALIDATION ERROR
Hello I am receiving the below error message while starting the NFS client. I understand that one of the DD output file is bad. So SYS00012 refers to which DD ? How to see the DD name refering to SYS value ? IEF196I IEF285I VOL SER NOS= OSREST. IEF196I IEF285I SYS1.IBM.PARMLIB KEPT IEF196I IEF285I VOL SER NOS= OSREST. BPXO015I THE SETOMVS COMMAND WAS SUCCESSFUL. IEF196I IEF237I 5301 ALLOCATED TO SYS5 IEF196I IEF285I TCPIP.TCPIP.DATA KEPT IEF196I IEF285I VOL SER NOS= OSSYB1. IEF196I IEF237I 5301 ALLOCATED TO SYS9 IEF196I IEF285I TCPIP.TCPIP.DATA KEPT IEF196I IEF285I VOL SER NOS= OSSYB1. IEF196I IEF237I 5301 ALLOCATED TO SYS00011 IEF196I IEF285I TCPIP.STANDARD.TCPXLBIN KEPT IEF196I IEF285I VOL SER NOS= OSSYB1. IEF196I IEF237I MSTR ALLOCATED TO SYS00012 $HASP708 MVSNFSC OPEN FAILED 746 RC=13 SDB/IRWD VALIDATION ERROR IEF196I IEC141I 013-C0,IGG0199G,MVSNFSC,MVSNFSC,SYS00012 IEC141I 013-C0,IGG0199G,MVSNFSC,MVSNFSC,SYS00012 747 IEF196I IEF285I JES2.MVSNFSC .MS.SYS00012 SYSOUT -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS Problem
Its happens that way once in a blue moon - Not once a day like windows
support people have users do
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Jousma, David
Sent: Wednesday, March 25, 2020 1:42 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: NFS Problem
That sounds like someone who support windows machines hehehe
_
Dave Jousma
AVP | Manager, Systems Engineering
Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids,
MI 49546
616.653.8429 | fax: 616.653.2717
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Steve Beaver
Sent: Wednesday, March 25, 2020 1:58 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: NFS Problem
**CAUTION EXTERNAL EMAIL**
**DO NOT open attachments or click on links from unknown senders or
unexpected emails**
The easiest and old school way is to IPL out of the problem and that is what
I'm going to do
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Jousma, David
Sent: Wednesday, March 25, 2020 11:08 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: NFS Problem
This may be a hint:
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3
.bpxb200/tranreq.htm
Use the PARM= parameter of the z/OS UNIX colony address space. To set
transport affinity for the NFS Client or DFS Client, use the PARM= keyword
of the EXEC statement that starts BPXVCLNY in the colony address space
procedure as follows:
//MVSCLNT EXEC PGM=BPXVCLNY,TIME=1440,PARM=TP(TPNAME)Copy
where the PARM=value is the following:
All in uppercase
Starts with "TP("
TPNAME is the left-aligned, 1-to-8-character name of the desired transport
If PARM= is specified and does not conform to these rules, the colony is
terminated by an EC6 abend with a reason code of 11BE8039. When CINET is
configured on the system and the specified transport is not configured under
CINET, the colony is terminated by an EC6 abend with a reason code of
11BE803A. In either case, the colony can be restarted after the procedure is
corrected by replying to the operator prompt that is issued.
_
Dave Jousma
AVP | Manager, Systems Engineering
Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids,
MI 49546
616.653.8429 | fax: 616.653.2717
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Steve Beaver
Sent: Wednesday, March 25, 2020 11:55 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: NFS Problem
**CAUTION EXTERNAL EMAIL**
**DO NOT open attachments or click on links from unknown senders or
unexpected emails**
Dave - now I have the following
IEF450I MVSNFSC MVSNFSC - ABEND=SEC6 U REASON=11BE8039
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Jousma, David
Sent: Wednesday, March 25, 2020 10:35 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: NFS Problem
Steve,
I could be mistaken, but its only necessary to issue that command if you are
running NFS Client. It sounds to me like you configured/started the z/OS
NFS server, in which case I believe you just recycle the task.
We only run the NFS client, and that is how we shutdown MVSNFSC task.
Restarting that task is the SET OMVS command you mention, and that restarts
just the Client.
RTFM says
https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.id
an400/sts.htm
P NFS or F NFS,STOP, or F NFS,SHUTDOWN
S NFS to start
_
Dave Jousma
AVP | Manager, Systems Engineering
Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids,
MI 49546
616.653.8429 | fax: 616.653.2717
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Steve Beaver
Sent: Wednesday, March 25, 2020 11:22 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: NFS Problem
**CAUTION EXTERNAL EMAIL**
**DO NOT open attachments or click on links from unknown senders or
unexpected emails**
I was forced to STOP NFS (See Below) because of a RACF definition problem
F OMVS,STOPPFS=NFS
Now when I SET OMVS=MC I get this message
BPXF011I A FILE SYSTEM WITH FILESYSTYPE OR SUBFILESYSTYPE NFS 114
FAILED TO INITIALIZE.
A DUPLICATE FILESYSTYPE/SUBFILESYSTYPE STATEMENT WAS FOUND IN PARMLIB
MEMBER
BPXPRMMC.
Anyone have any idea how to remediate this problem
--
For IBM-MAIN subscribe / signoff / archive access instructions, send email
to lists...@lists
Re: NFS Problem
That sounds like someone who support windows machines hehehe
_
Dave Jousma
AVP | Manager, Systems Engineering
Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI
49546
616.653.8429 | fax: 616.653.2717
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Steve Beaver
Sent: Wednesday, March 25, 2020 1:58 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: NFS Problem
**CAUTION EXTERNAL EMAIL**
**DO NOT open attachments or click on links from unknown senders or unexpected
emails**
The easiest and old school way is to IPL out of the problem and that is what
I'm going to do
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Jousma, David
Sent: Wednesday, March 25, 2020 11:08 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: NFS Problem
This may be a hint:
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3
.bpxb200/tranreq.htm
Use the PARM= parameter of the z/OS UNIX colony address space. To set transport
affinity for the NFS Client or DFS Client, use the PARM= keyword of the EXEC
statement that starts BPXVCLNY in the colony address space procedure as follows:
//MVSCLNT EXEC PGM=BPXVCLNY,TIME=1440,PARM=TP(TPNAME)Copy
where the PARM=value is the following:
All in uppercase
Starts with "TP("
TPNAME is the left-aligned, 1-to-8-character name of the desired transport If
PARM= is specified and does not conform to these rules, the colony is
terminated by an EC6 abend with a reason code of 11BE8039. When CINET is
configured on the system and the specified transport is not configured under
CINET, the colony is terminated by an EC6 abend with a reason code of 11BE803A.
In either case, the colony can be restarted after the procedure is corrected by
replying to the operator prompt that is issued.
_
Dave Jousma
AVP | Manager, Systems Engineering
Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI
49546
616.653.8429 | fax: 616.653.2717
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Steve Beaver
Sent: Wednesday, March 25, 2020 11:55 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: NFS Problem
**CAUTION EXTERNAL EMAIL**
**DO NOT open attachments or click on links from unknown senders or unexpected
emails**
Dave - now I have the following
IEF450I MVSNFSC MVSNFSC - ABEND=SEC6 U REASON=11BE8039
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Jousma, David
Sent: Wednesday, March 25, 2020 10:35 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: NFS Problem
Steve,
I could be mistaken, but its only necessary to issue that command if you are
running NFS Client. It sounds to me like you configured/started the z/OS NFS
server, in which case I believe you just recycle the task.
We only run the NFS client, and that is how we shutdown MVSNFSC task.
Restarting that task is the SET OMVS command you mention, and that restarts
just the Client.
RTFM says
https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.id
an400/sts.htm
P NFS or F NFS,STOP, or F NFS,SHUTDOWN
S NFS to start
_
Dave Jousma
AVP | Manager, Systems Engineering
Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI
49546
616.653.8429 | fax: 616.653.2717
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Steve Beaver
Sent: Wednesday, March 25, 2020 11:22 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: NFS Problem
**CAUTION EXTERNAL EMAIL**
**DO NOT open attachments or click on links from unknown senders or unexpected
emails**
I was forced to STOP NFS (See Below) because of a RACF definition problem
F OMVS,STOPPFS=NFS
Now when I SET OMVS=MC I get this message
BPXF011I A FILE SYSTEM WITH FILESYSTYPE OR SUBFILESYSTYPE NFS 114
FAILED TO INITIALIZE.
A DUPLICATE FILESYSTYPE/SUBFILESYSTYPE STATEMENT WAS FOUND IN PARMLIB
MEMBER
BPXPRMMC.
Anyone have any idea how to remediate this problem
--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
lists...@listserv.ua.edu with the message: INFO IBM-MAIN **CAUTION EXTERNAL
EMAIL**
**DO NOT open attachments or click on links from unknown senders or unexpected
emails**
This e-mail transmission contains information that is confidential and may
be privileged. It is intended only for the addressee(s) named abo
Re: NFS Problem
The easiest and old school way is to IPL out of the problem and that is what
I'm going to do
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Jousma, David
Sent: Wednesday, March 25, 2020 11:08 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: NFS Problem
This may be a hint:
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3
.bpxb200/tranreq.htm
Use the PARM= parameter of the z/OS UNIX colony address space. To set
transport affinity for the NFS Client or DFS Client, use the PARM= keyword
of the EXEC statement that starts BPXVCLNY in the colony address space
procedure as follows:
//MVSCLNT EXEC PGM=BPXVCLNY,TIME=1440,PARM=TP(TPNAME)Copy
where the PARM=value is the following:
All in uppercase
Starts with "TP("
TPNAME is the left-aligned, 1-to-8-character name of the desired transport
If PARM= is specified and does not conform to these rules, the colony is
terminated by an EC6 abend with a reason code of 11BE8039. When CINET is
configured on the system and the specified transport is not configured under
CINET, the colony is terminated by an EC6 abend with a reason code of
11BE803A. In either case, the colony can be restarted after the procedure is
corrected by replying to the operator prompt that is issued.
_
Dave Jousma
AVP | Manager, Systems Engineering
Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids,
MI 49546
616.653.8429 | fax: 616.653.2717
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Steve Beaver
Sent: Wednesday, March 25, 2020 11:55 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: NFS Problem
**CAUTION EXTERNAL EMAIL**
**DO NOT open attachments or click on links from unknown senders or
unexpected emails**
Dave - now I have the following
IEF450I MVSNFSC MVSNFSC - ABEND=SEC6 U REASON=11BE8039
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Jousma, David
Sent: Wednesday, March 25, 2020 10:35 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: NFS Problem
Steve,
I could be mistaken, but its only necessary to issue that command if you are
running NFS Client. It sounds to me like you configured/started the z/OS
NFS server, in which case I believe you just recycle the task.
We only run the NFS client, and that is how we shutdown MVSNFSC task.
Restarting that task is the SET OMVS command you mention, and that restarts
just the Client.
RTFM says
https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.id
an400/sts.htm
P NFS or F NFS,STOP, or F NFS,SHUTDOWN
S NFS to start
_
Dave Jousma
AVP | Manager, Systems Engineering
Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids,
MI 49546
616.653.8429 | fax: 616.653.2717
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Steve Beaver
Sent: Wednesday, March 25, 2020 11:22 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: NFS Problem
**CAUTION EXTERNAL EMAIL**
**DO NOT open attachments or click on links from unknown senders or
unexpected emails**
I was forced to STOP NFS (See Below) because of a RACF definition problem
F OMVS,STOPPFS=NFS
Now when I SET OMVS=MC I get this message
BPXF011I A FILE SYSTEM WITH FILESYSTYPE OR SUBFILESYSTYPE NFS 114
FAILED TO INITIALIZE.
A DUPLICATE FILESYSTYPE/SUBFILESYSTYPE STATEMENT WAS FOUND IN PARMLIB
MEMBER
BPXPRMMC.
Anyone have any idea how to remediate this problem
--
For IBM-MAIN subscribe / signoff / archive access instructions, send email
to lists...@listserv.ua.edu with the message: INFO IBM-MAIN **CAUTION
EXTERNAL EMAIL**
**DO NOT open attachments or click on links from unknown senders or
unexpected emails**
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 lists...@listserv.ua.edu with the message: INF
Re: NFS Problem
This may be a hint:
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.bpxb200/tranreq.htm
Use the PARM= parameter of the z/OS UNIX colony address space. To set transport
affinity for the NFS Client or DFS Client, use the PARM= keyword of the EXEC
statement that starts BPXVCLNY in the colony address space procedure as follows:
//MVSCLNT EXEC PGM=BPXVCLNY,TIME=1440,PARM=TP(TPNAME)Copy
where the PARM=value is the following:
All in uppercase
Starts with "TP("
TPNAME is the left-aligned, 1-to-8-character name of the desired transport
If PARM= is specified and does not conform to these rules, the colony is
terminated by an EC6 abend with a reason code of 11BE8039. When CINET is
configured on the system and the specified transport is not configured under
CINET, the colony is terminated by an EC6 abend with a reason code of 11BE803A.
In either case, the colony can be restarted after the procedure is corrected by
replying to the operator prompt that is issued.
_
Dave Jousma
AVP | Manager, Systems Engineering
Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI
49546
616.653.8429 | fax: 616.653.2717
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Steve Beaver
Sent: Wednesday, March 25, 2020 11:55 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: NFS Problem
**CAUTION EXTERNAL EMAIL**
**DO NOT open attachments or click on links from unknown senders or unexpected
emails**
Dave - now I have the following
IEF450I MVSNFSC MVSNFSC - ABEND=SEC6 U REASON=11BE8039
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Jousma, David
Sent: Wednesday, March 25, 2020 10:35 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: NFS Problem
Steve,
I could be mistaken, but its only necessary to issue that command if you are
running NFS Client. It sounds to me like you configured/started the z/OS NFS
server, in which case I believe you just recycle the task.
We only run the NFS client, and that is how we shutdown MVSNFSC task.
Restarting that task is the SET OMVS command you mention, and that restarts
just the Client.
RTFM says
https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.id
an400/sts.htm
P NFS or F NFS,STOP, or F NFS,SHUTDOWN
S NFS to start
_
Dave Jousma
AVP | Manager, Systems Engineering
Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI
49546
616.653.8429 | fax: 616.653.2717
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Steve Beaver
Sent: Wednesday, March 25, 2020 11:22 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: NFS Problem
**CAUTION EXTERNAL EMAIL**
**DO NOT open attachments or click on links from unknown senders or unexpected
emails**
I was forced to STOP NFS (See Below) because of a RACF definition problem
F OMVS,STOPPFS=NFS
Now when I SET OMVS=MC I get this message
BPXF011I A FILE SYSTEM WITH FILESYSTYPE OR SUBFILESYSTYPE NFS 114
FAILED TO INITIALIZE.
A DUPLICATE FILESYSTYPE/SUBFILESYSTYPE STATEMENT WAS FOUND IN PARMLIB
MEMBER
BPXPRMMC.
Anyone have any idea how to remediate this problem
--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
lists...@listserv.ua.edu with the message: INFO IBM-MAIN **CAUTION EXTERNAL
EMAIL**
**DO NOT open attachments or click on links from unknown senders or unexpected
emails**
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
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
lists...@listserv.ua.edu with the message: INFO IBM-MAIN **CAUTION EXTERNAL
EMAIL**
**DO NOT open attachments or click on links from unkno
Re: NFS Problem
That's usually security error in unix, but that reason code is unknown on my system when I issue TSO BPXMTEXT 11BE8039 _ Dave Jousma AVP | Manager, Systems Engineering Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI 49546 616.653.8429 | fax: 616.653.2717 -Original Message- From: IBM Mainframe Discussion List On Behalf Of Steve Beaver Sent: Wednesday, March 25, 2020 11:55 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: NFS Problem **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** Dave - now I have the following IEF450I MVSNFSC MVSNFSC - ABEND=SEC6 U REASON=11BE8039 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jousma, David Sent: Wednesday, March 25, 2020 10:35 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: NFS Problem Steve, I could be mistaken, but its only necessary to issue that command if you are running NFS Client. It sounds to me like you configured/started the z/OS NFS server, in which case I believe you just recycle the task. We only run the NFS client, and that is how we shutdown MVSNFSC task. Restarting that task is the SET OMVS command you mention, and that restarts just the Client. RTFM says https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.id an400/sts.htm P NFS or F NFS,STOP, or F NFS,SHUTDOWN S NFS to start _ Dave Jousma AVP | Manager, Systems Engineering Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI 49546 616.653.8429 | fax: 616.653.2717 -Original Message- From: IBM Mainframe Discussion List On Behalf Of Steve Beaver Sent: Wednesday, March 25, 2020 11:22 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: NFS Problem **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** I was forced to STOP NFS (See Below) because of a RACF definition problem F OMVS,STOPPFS=NFS Now when I SET OMVS=MC I get this message BPXF011I A FILE SYSTEM WITH FILESYSTYPE OR SUBFILESYSTYPE NFS 114 FAILED TO INITIALIZE. A DUPLICATE FILESYSTYPE/SUBFILESYSTYPE STATEMENT WAS FOUND IN PARMLIB MEMBER BPXPRMMC. Anyone have any idea how to remediate this problem -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS Problem
Dave - now I have the following IEF450I MVSNFSC MVSNFSC - ABEND=SEC6 U REASON=11BE8039 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jousma, David Sent: Wednesday, March 25, 2020 10:35 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: NFS Problem Steve, I could be mistaken, but its only necessary to issue that command if you are running NFS Client. It sounds to me like you configured/started the z/OS NFS server, in which case I believe you just recycle the task. We only run the NFS client, and that is how we shutdown MVSNFSC task. Restarting that task is the SET OMVS command you mention, and that restarts just the Client. RTFM says https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.id an400/sts.htm P NFS or F NFS,STOP, or F NFS,SHUTDOWN S NFS to start _ Dave Jousma AVP | Manager, Systems Engineering Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI 49546 616.653.8429 | fax: 616.653.2717 -Original Message- From: IBM Mainframe Discussion List On Behalf Of Steve Beaver Sent: Wednesday, March 25, 2020 11:22 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: NFS Problem **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** I was forced to STOP NFS (See Below) because of a RACF definition problem F OMVS,STOPPFS=NFS Now when I SET OMVS=MC I get this message BPXF011I A FILE SYSTEM WITH FILESYSTYPE OR SUBFILESYSTYPE NFS 114 FAILED TO INITIALIZE. A DUPLICATE FILESYSTYPE/SUBFILESYSTYPE STATEMENT WAS FOUND IN PARMLIB MEMBER BPXPRMMC. Anyone have any idea how to remediate this problem -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS Problem
Steve, I could be mistaken, but its only necessary to issue that command if you are running NFS Client. It sounds to me like you configured/started the z/OS NFS server, in which case I believe you just recycle the task. We only run the NFS client, and that is how we shutdown MVSNFSC task. Restarting that task is the SET OMVS command you mention, and that restarts just the Client. RTFM says https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.idan400/sts.htm P NFS or F NFS,STOP, or F NFS,SHUTDOWN S NFS to start _ Dave Jousma AVP | Manager, Systems Engineering Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI 49546 616.653.8429 | fax: 616.653.2717 -Original Message- From: IBM Mainframe Discussion List On Behalf Of Steve Beaver Sent: Wednesday, March 25, 2020 11:22 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: NFS Problem **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** I was forced to STOP NFS (See Below) because of a RACF definition problem F OMVS,STOPPFS=NFS Now when I SET OMVS=MC I get this message BPXF011I A FILE SYSTEM WITH FILESYSTYPE OR SUBFILESYSTYPE NFS 114 FAILED TO INITIALIZE. A DUPLICATE FILESYSTYPE/SUBFILESYSTYPE STATEMENT WAS FOUND IN PARMLIB MEMBER BPXPRMMC. Anyone have any idea how to remediate this problem -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
NFS Problem
I was forced to STOP NFS (See Below) because of a RACF definition problem F OMVS,STOPPFS=NFS Now when I SET OMVS=MC I get this message BPXF011I A FILE SYSTEM WITH FILESYSTYPE OR SUBFILESYSTYPE NFS 114 FAILED TO INITIALIZE. A DUPLICATE FILESYSTYPE/SUBFILESYSTYPE STATEMENT WAS FOUND IN PARMLIB MEMBER BPXPRMMC. Anyone have any idea how to remediate this problem -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS
On 3/24/2020 11:49 AM, Steve Beaver wrote: How many shops are running MVSNFS currently? We are now. It used to be SMB, but IBM discontinued that... :-( -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 https://www.phoenixsoftware.com/ This e-mail message, including any attachments, appended messages and the information contained therein, is for the sole use of the intended recipient(s). If you are not an intended recipient or have otherwise received this email message in error, any use, dissemination, distribution, review, storage or copying of this e-mail message and the information contained therein is strictly prohibited. If you are not an intended recipient, please contact the sender by reply e-mail and destroy all copies of this email message and do not otherwise utilize or retain this email message or any or all of the information contained therein. Although this email message and any attachments or appended messages are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by the sender for any loss or damage arising in any way from its opening or use. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS
I got it figure out. The biggest problem I have is the sheer number of LPAR's that I have to install NFS on -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jousma, David Sent: Tuesday, March 24, 2020 2:50 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: NFS We run just the NFS client, mounting open system disk on MF for application use. _ Dave Jousma AVP | Manager, Systems Engineering Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI 49546 616.653.8429 | fax: 616.653.2717 -Original Message- From: IBM Mainframe Discussion List On Behalf Of Steve Beaver Sent: Tuesday, March 24, 2020 2:49 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: NFS **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** How many shops are running MVSNFS currently? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS
z/OSMF has workflows that may be helpful: Workflow for Installing and Configuring the z/OS NFS Server guides the system administrator through the process of setting up the z/OS NFS Server, information on the initial installation see the Workflow for Migration from z/OS DFS/SMB to z/OS NFS Dana >-Original Message- >From: IBM Mainframe Discussion List On Behalf Of >Steve Beaver >Sent: Tuesday, March 24, 2020 2:49 PM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: NFS > >How many shops are running MVSNFS currently? > > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS
We run just the NFS client, mounting open system disk on MF for application use. _ Dave Jousma AVP | Manager, Systems Engineering Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI 49546 616.653.8429 | fax: 616.653.2717 -Original Message- From: IBM Mainframe Discussion List On Behalf Of Steve Beaver Sent: Tuesday, March 24, 2020 2:49 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: NFS **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** How many shops are running MVSNFS currently? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS
I did because I assumed it would be required... or maybe I attempted to start it and it failed. I have it running on three LPARs. One system programmer test LPAR, one application test LPAR and one production LPAR. On Tue, Mar 24, 2020 at 3:31 PM Steve Beaver wrote: > My biggest concern is do I need to allocate the file uniquely by LPAR > since I have a log of LPARS? > > TIA > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Keith Smith > Sent: Tuesday, March 24, 2020 2:00 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: NFS > > We run it. > > On Tue, Mar 24, 2020 at 2:49 PM Steve Beaver > wrote: > > > How many shops are running MVSNFS currently? > > > > > > > > > > > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > > -- > Keith Smith > Engineer-Enterprise Sys Sr.-IT Capacity & Performance > Shaw Industries Inc. > Subsidiary of Berkshire Hathaway > 616 E Walnut Ave > Mail Drop 072-08 > Dalton, GA 30721 > Email: keith.sm...@shawinc.com Office: 706.532.3244 > > Please consider the environment before printing. > > -- > ** > Privileged > and/or confidential information may be contained in this message. If you > are not the addressee indicated in this message (or are not responsible > for > delivery of this message to that person), you may not copy or deliver this > message to anyone. In such case, you should destroy this message and > notify > the sender by reply e-mail. > If you or your employer do not consent to > Internet e-mail for messages of this kind, please advise the sender. > Shaw > Industries does not provide or endorse any opinions, conclusions or other > information in this message that do not relate to the official business of > the company or its subsidiaries. > > ** > > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Keith Smith Engineer-Enterprise Sys Sr.-IT Capacity & Performance Shaw Industries Inc. Subsidiary of Berkshire Hathaway 616 E Walnut Ave Mail Drop 072-08 Dalton, GA 30721 Email: keith.sm...@shawinc.com Office: 706.532.3244 Please consider the environment before printing. -- ** Privileged and/or confidential information may be contained in this message. If you are not the addressee indicated in this message (or are not responsible for delivery of this message to that person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and notify the sender by reply e-mail. If you or your employer do not consent to Internet e-mail for messages of this kind, please advise the sender. Shaw Industries does not provide or endorse any opinions, conclusions or other information in this message that do not relate to the official business of the company or its subsidiaries. ** -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS
It has been a while back but I don't recall anything being difficult. We are only using it to present an MVS dataset prefix to the distributed world. There are several VSAM files that need to be created and some parm selection. We use RACF and we attached the started task to the same owner as TCPIP so it would have USS authority. As I recall it was pretty much a step by step install. On Tue, Mar 24, 2020 at 3:08 PM Steve Beaver wrote: > How long did it take to get it up and functional? > > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Keith Smith > Sent: Tuesday, March 24, 2020 2:00 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: NFS > > We run it. > > On Tue, Mar 24, 2020 at 2:49 PM Steve Beaver > wrote: > > > How many shops are running MVSNFS currently? > > > > > > > > > > > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > > -- > Keith Smith > Engineer-Enterprise Sys Sr.-IT Capacity & Performance > Shaw Industries Inc. > Subsidiary of Berkshire Hathaway > 616 E Walnut Ave > Mail Drop 072-08 > Dalton, GA 30721 > Email: keith.sm...@shawinc.com Office: 706.532.3244 > > Please consider the environment before printing. > > -- > ** > Privileged > and/or confidential information may be contained in this message. If you > are not the addressee indicated in this message (or are not responsible > for > delivery of this message to that person), you may not copy or deliver this > message to anyone. In such case, you should destroy this message and > notify > the sender by reply e-mail. > If you or your employer do not consent to > Internet e-mail for messages of this kind, please advise the sender. > Shaw > Industries does not provide or endorse any opinions, conclusions or other > information in this message that do not relate to the official business of > the company or its subsidiaries. > > ** > > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Keith Smith Engineer-Enterprise Sys Sr.-IT Capacity & Performance Shaw Industries Inc. Subsidiary of Berkshire Hathaway 616 E Walnut Ave Mail Drop 072-08 Dalton, GA 30721 Email: keith.sm...@shawinc.com Office: 706.532.3244 Please consider the environment before printing. -- ** Privileged and/or confidential information may be contained in this message. If you are not the addressee indicated in this message (or are not responsible for delivery of this message to that person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and notify the sender by reply e-mail. If you or your employer do not consent to Internet e-mail for messages of this kind, please advise the sender. Shaw Industries does not provide or endorse any opinions, conclusions or other information in this message that do not relate to the official business of the company or its subsidiaries. ** -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS
My biggest concern is do I need to allocate the file uniquely by LPAR since I have a log of LPARS? TIA -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Keith Smith Sent: Tuesday, March 24, 2020 2:00 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: NFS We run it. On Tue, Mar 24, 2020 at 2:49 PM Steve Beaver wrote: > How many shops are running MVSNFS currently? > > > > > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Keith Smith Engineer-Enterprise Sys Sr.-IT Capacity & Performance Shaw Industries Inc. Subsidiary of Berkshire Hathaway 616 E Walnut Ave Mail Drop 072-08 Dalton, GA 30721 Email: keith.sm...@shawinc.com Office: 706.532.3244 Please consider the environment before printing. -- ** Privileged and/or confidential information may be contained in this message. If you are not the addressee indicated in this message (or are not responsible for delivery of this message to that person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and notify the sender by reply e-mail. If you or your employer do not consent to Internet e-mail for messages of this kind, please advise the sender. Shaw Industries does not provide or endorse any opinions, conclusions or other information in this message that do not relate to the official business of the company or its subsidiaries. ** -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS
How long did it take to get it up and functional? -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Keith Smith Sent: Tuesday, March 24, 2020 2:00 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: NFS We run it. On Tue, Mar 24, 2020 at 2:49 PM Steve Beaver wrote: > How many shops are running MVSNFS currently? > > > > > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Keith Smith Engineer-Enterprise Sys Sr.-IT Capacity & Performance Shaw Industries Inc. Subsidiary of Berkshire Hathaway 616 E Walnut Ave Mail Drop 072-08 Dalton, GA 30721 Email: keith.sm...@shawinc.com Office: 706.532.3244 Please consider the environment before printing. -- ** Privileged and/or confidential information may be contained in this message. If you are not the addressee indicated in this message (or are not responsible for delivery of this message to that person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and notify the sender by reply e-mail. If you or your employer do not consent to Internet e-mail for messages of this kind, please advise the sender. Shaw Industries does not provide or endorse any opinions, conclusions or other information in this message that do not relate to the official business of the company or its subsidiaries. ** -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS
We run it. On Tue, Mar 24, 2020 at 2:49 PM Steve Beaver wrote: > How many shops are running MVSNFS currently? > > > > > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Keith Smith Engineer-Enterprise Sys Sr.-IT Capacity & Performance Shaw Industries Inc. Subsidiary of Berkshire Hathaway 616 E Walnut Ave Mail Drop 072-08 Dalton, GA 30721 Email: keith.sm...@shawinc.com Office: 706.532.3244 Please consider the environment before printing. -- ** Privileged and/or confidential information may be contained in this message. If you are not the addressee indicated in this message (or are not responsible for delivery of this message to that person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and notify the sender by reply e-mail. If you or your employer do not consent to Internet e-mail for messages of this kind, please advise the sender. Shaw Industries does not provide or endorse any opinions, conclusions or other information in this message that do not relate to the official business of the company or its subsidiaries. ** -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
NFS
How many shops are running MVSNFS currently? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS Mount Failure
I'm sorry, I think I misunderstood something somewhere. From what I
understood, the problem was that when a remote NFS server is rebooted, you
have to remount the NFS file system on z/OS, and then there needs to be a
file access attempt before you can actually access the files in the file
system.
So what I was suggesting was to put the touch command in a batch job after
the remount command, so that the file access attempt happens right after
the file system is remounted. If it's a different problem you're trying to
solve, the touch command won't help.
---
Kevin McKenzie
External Phone: 845-435-8282, Tie-line: 8-295-8282
z/OS Test Services - Test Architect, Provisioning
IBM Mainframe Discussion List wrote on
01/24/2019 03:57:22 PM:
> From: "Watkins, Philip S."
> To: IBM-MAIN@LISTSERV.UA.EDU
> Date: 01/24/2019 03:58 PM
> Subject: Re: NFS Mount Failure
> Sent by: IBM Mainframe Discussion List
>
> I am performing an unmount, touch and then mount. The mount is
> successful, but my job still fails unless I browse /u/usr/xerox/
> manually first.
>
> //XEROXUMT EXEC PGM=IKJEFT01 DYNAMNBR=NN,PARM='COMMAND'
> //SYSTSPRT DD SYSOUT=*
> //SYSEXEC DD DUMMY
> //SYSTSIN DD *
> UNMOUNT FILESYSTEM('XEROXRAW')
> /*
> //STEP0001 EXEC PGM=AOPBATCH,PARM='sleep 15'
> //STDOUT DD SYSOUT=*
> //STDERR DD SYSOUT=*
> //STDINDD DUMMY
> //TOUCHEXEC PGM=BPXBATCH,PARM='SH touch -c /u/usr/xerox/tmpfile'
> //STDOUT DD SYSOUT=*
> //STDERR DD SYSOUT=*
> //*STDPARM DD dummy
> //*
> //XEROXMNT EXEC PGM=IKJEFT01 DYNAMNBR=NN,PARM='COMMAND'
> //SYSTSPRT DD SYSOUT=*
> //SYSEXEC DD DUMMY
> //SYSTSIN DD *
> MOUNT FILESYSTEM('XEROXRAW') MOUNTPOINT('/u/usr/xerox') TYPE(NFS) -
> MODE(RDWR) PARM('PGCSYS:/XEROXRAW,SOFT,SOFT,VERS(3),XLAT(Y), +
> CLN_CCSID(1047),SRV_CCSID(819)')
> /*
>
> -Original Message-
> From: IBM Mainframe Discussion List On
> Behalf Of Carmen Vitullo
> Sent: Thursday, January 24, 2019 2:57 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: NFS Mount Failure
>
> CAUTION: This email originated from an external email domain which
> carries the additional risk that it may be a phishing email and/or
> contain malware.
>
>
> that's a really easy and great option !
> I use touch to create files interactively I never thought about
> using touch like that !
>
>
>
> Carmen Vitullo
>
> - Original Message -
>
> From: "Kevin Mckenzie"
> To: IBM-MAIN@LISTSERV.UA.EDU
> Sent: Thursday, January 24, 2019 1:44:25 PM
> Subject: Re: NFS Mount Failure
>
> Right. touch is a standard unix command; it officially is used for
> updating the access or last modified time of a file, but it's often
> used sort of as a utility command in the way IEFBR14 can be used to
> create a file.
>
> So I would think a job step like:
>
> //TOUCH EXEC PGM=BPXBATCH,PARM='SH touch -c /u/usr/xerox/tmpfile'
>
> would force USS to go see if /u/usr/xerox/tmpfile exists, and
> therefore require NFS to reestablish a full connection to the
> server, after you've run the automount command. The -c option tells
> touch not to create a file that isn't already there, so that should
> prevent any file from actually being created. I haven't tested this,
> though I'm trying to get in touch with one of the NFS folks to see
> if this is known/expected behavior.
>
> Note that case matters in the PARM statement.
> ---
> Kevin McKenzie
>
> External Phone: 845-435-8282, Tie-line: 8-295-8282 z/OS Test
> Services - Test Architect, Provisioning
>
> IBM Mainframe Discussion List wrote on
> 01/24/2019 12:31:15 PM:
>
> > From: "Watkins, Philip S."
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Date: 01/24/2019 12:33 PM
> > Subject: Re: NFS Mount Failure
> > Sent by: IBM Mainframe Discussion List
> >
> > Thanks Kevin, I am trying to understand how to convert what I have to
> > use BPXBATCH.
> > I was not aware of the use of a "TOUCH" command.
> > Any help converting would be greatly appreciated.
> >
> > I currently use the following on the Mainframe;
> >
> > MOUNT FILESYSTEM('XEROXRAW') MOUNTPOINT('/u/usr/xerox') TYPE(NFS) -
> > MODE(RDWR) PARM('PGCSYS:/XEROXRAW,SOFT,SOFT,VERS(3),XLAT(Y), +
> > CLN_CCSID(1047),SRV_CCSID(819)')
> >
> >
> >
> > -Original Message-
> > From: IBM Mainframe Discussion List On
> > Behalf Of Kevin Mckenzie
> > Sent: Thursday, January 24, 2019 11:54 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Re: NFS Mount Failure
> >
> > CAUTION: This email originated from an external email domain which
> > carries the additional risk that it may be a phish
Re: NFS Mount Failure
I am performing an unmount, touch and then mount. The mount is successful, but
my job still fails unless I browse /u/usr/xerox/ manually first.
//XEROXUMT EXEC PGM=IKJEFT01 DYNAMNBR=NN,PARM='COMMAND'
//SYSTSPRT DD SYSOUT=*
//SYSEXEC DD DUMMY
//SYSTSIN DD *
UNMOUNT FILESYSTEM('XEROXRAW')
/*
//STEP0001 EXEC PGM=AOPBATCH,PARM='sleep 15'
//STDOUT DD SYSOUT=*
//STDERR DD SYSOUT=*
//STDINDD DUMMY
//TOUCHEXEC PGM=BPXBATCH,PARM='SH touch -c /u/usr/xerox/tmpfile'
//STDOUT DD SYSOUT=*
//STDERR DD SYSOUT=*
//*STDPARM DD dummy
//*
//XEROXMNT EXEC PGM=IKJEFT01 DYNAMNBR=NN,PARM='COMMAND'
//SYSTSPRT DD SYSOUT=*
//SYSEXEC DD DUMMY
//SYSTSIN DD *
MOUNT FILESYSTEM('XEROXRAW') MOUNTPOINT('/u/usr/xerox') TYPE(NFS) -
MODE(RDWR) PARM('PGCSYS:/XEROXRAW,SOFT,SOFT,VERS(3),XLAT(Y), +
CLN_CCSID(1047),SRV_CCSID(819)')
/*
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Carmen Vitullo
Sent: Thursday, January 24, 2019 2:57 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: NFS Mount Failure
CAUTION: This email originated from an external email domain which carries the
additional risk that it may be a phishing email and/or contain malware.
that's a really easy and great option !
I use touch to create files interactively I never thought about using touch
like that !
Carmen Vitullo
- Original Message -
From: "Kevin Mckenzie"
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Thursday, January 24, 2019 1:44:25 PM
Subject: Re: NFS Mount Failure
Right. touch is a standard unix command; it officially is used for updating the
access or last modified time of a file, but it's often used sort of as a
utility command in the way IEFBR14 can be used to create a file.
So I would think a job step like:
//TOUCH EXEC PGM=BPXBATCH,PARM='SH touch -c /u/usr/xerox/tmpfile'
would force USS to go see if /u/usr/xerox/tmpfile exists, and therefore require
NFS to reestablish a full connection to the server, after you've run the
automount command. The -c option tells touch not to create a file that isn't
already there, so that should prevent any file from actually being created. I
haven't tested this, though I'm trying to get in touch with one of the NFS
folks to see if this is known/expected behavior.
Note that case matters in the PARM statement.
---
Kevin McKenzie
External Phone: 845-435-8282, Tie-line: 8-295-8282 z/OS Test Services - Test
Architect, Provisioning
IBM Mainframe Discussion List wrote on
01/24/2019 12:31:15 PM:
> From: "Watkins, Philip S."
> To: IBM-MAIN@LISTSERV.UA.EDU
> Date: 01/24/2019 12:33 PM
> Subject: Re: NFS Mount Failure
> Sent by: IBM Mainframe Discussion List
>
> Thanks Kevin, I am trying to understand how to convert what I have to
> use BPXBATCH.
> I was not aware of the use of a "TOUCH" command.
> Any help converting would be greatly appreciated.
>
> I currently use the following on the Mainframe;
>
> MOUNT FILESYSTEM('XEROXRAW') MOUNTPOINT('/u/usr/xerox') TYPE(NFS) -
> MODE(RDWR) PARM('PGCSYS:/XEROXRAW,SOFT,SOFT,VERS(3),XLAT(Y), +
> CLN_CCSID(1047),SRV_CCSID(819)')
>
>
>
> -Original Message-
> From: IBM Mainframe Discussion List On
> Behalf Of Kevin Mckenzie
> Sent: Thursday, January 24, 2019 11:54 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: NFS Mount Failure
>
> CAUTION: This email originated from an external email domain which
> carries the additional risk that it may be a phishing email and/or
> contain malware.
>
>
> Have you thought about using BPXBATCH and something like the touch
> command to force an access of the remote file system?
>
> ---
> Kevin McKenzie
>
> External Phone: 845-435-8282, Tie-line: 8-295-8282 z/OS Test Services
> - Test Architect, Provisioning
>
> IBM Mainframe Discussion List wrote on
> 01/23/2019 01:11:26 PM:
>
> > From: Carmen Vitullo
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Date: 01/23/2019 01:12 PM
> > Subject: Re: NFS Mount Failure
> > Sent by: IBM Mainframe Discussion List
> >
> > for mounts or remounts - same here, I just run a BPXBATCH to run
> theautomount
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> This E-mail and any of its
> attachments may contain Prince George’s County Government or Prince
> George's County 7th Judicial Circuit Court proprietary information or
> Protected Health Information, which is privileged and confidential.
> This E-mail is intended solely for the use of the individual or entity
> to which it is addressed. If you are not the intended recipient of
> this E-mail, you are hereby notified that any dissemination,
> distri
Re: NFS Mount Failure
On Thu, 24 Jan 2019 14:44:25 -0500, Kevin Mckenzie wrote: >Right. touch is a standard unix command; it officially is used for >updating the access or last modified time of a file, but it's often used >sort of as a utility command in the way IEFBR14 can be used to create a >file. > >So I would think a job step like: > >//TOUCH EXEC PGM=BPXBATCH,PARM='SH touch -c /u/usr/xerox/tmpfile' > My experience has been that "touch" from an NFS client does *not* update the timestamp of an existing PDS(E) member. ISPF timestamp? FAMS timestamp? Whatever. >... The -c option tells touch not to create a file that isn't already there, >... > Conversely, I use: : >>/some/path/name ... which creates a new file but does not modify the timestamp of an existing file. >Note that case matters in the PARM statement. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS Mount Failure
that's a really easy and great option !
I use touch to create files interactively I never thought about using touch
like that !
Carmen Vitullo
- Original Message -
From: "Kevin Mckenzie"
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Thursday, January 24, 2019 1:44:25 PM
Subject: Re: NFS Mount Failure
Right. touch is a standard unix command; it officially is used for
updating the access or last modified time of a file, but it's often used
sort of as a utility command in the way IEFBR14 can be used to create a
file.
So I would think a job step like:
//TOUCH EXEC PGM=BPXBATCH,PARM='SH touch -c /u/usr/xerox/tmpfile'
would force USS to go see if /u/usr/xerox/tmpfile exists, and therefore
require NFS to reestablish a full connection to the server, after you've
run the automount command. The -c option tells touch not to create a file
that isn't already there, so that should prevent any file from actually
being created. I haven't tested this, though I'm trying to get in touch
with one of the NFS folks to see if this is known/expected behavior.
Note that case matters in the PARM statement.
---
Kevin McKenzie
External Phone: 845-435-8282, Tie-line: 8-295-8282
z/OS Test Services - Test Architect, Provisioning
IBM Mainframe Discussion List wrote on
01/24/2019 12:31:15 PM:
> From: "Watkins, Philip S."
> To: IBM-MAIN@LISTSERV.UA.EDU
> Date: 01/24/2019 12:33 PM
> Subject: Re: NFS Mount Failure
> Sent by: IBM Mainframe Discussion List
>
> Thanks Kevin, I am trying to understand how to convert what I have
> to use BPXBATCH.
> I was not aware of the use of a "TOUCH" command.
> Any help converting would be greatly appreciated.
>
> I currently use the following on the Mainframe;
>
> MOUNT FILESYSTEM('XEROXRAW') MOUNTPOINT('/u/usr/xerox') TYPE(NFS) -
> MODE(RDWR) PARM('PGCSYS:/XEROXRAW,SOFT,SOFT,VERS(3),XLAT(Y), +
> CLN_CCSID(1047),SRV_CCSID(819)')
>
>
>
> -Original Message-
> From: IBM Mainframe Discussion List On
> Behalf Of Kevin Mckenzie
> Sent: Thursday, January 24, 2019 11:54 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: NFS Mount Failure
>
> CAUTION: This email originated from an external email domain which
> carries the additional risk that it may be a phishing email and/or
> contain malware.
>
>
> Have you thought about using BPXBATCH and something like the touch
> command to force an access of the remote file system?
>
> ---
> Kevin McKenzie
>
> External Phone: 845-435-8282, Tie-line: 8-295-8282 z/OS Test
> Services - Test Architect, Provisioning
>
> IBM Mainframe Discussion List wrote on
> 01/23/2019 01:11:26 PM:
>
> > From: Carmen Vitullo
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Date: 01/23/2019 01:12 PM
> > Subject: Re: NFS Mount Failure
> > Sent by: IBM Mainframe Discussion List
> >
> > for mounts or remounts - same here, I just run a BPXBATCH to run
> theautomount
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
> This E-mail and any of its attachments may contain Prince George’s
> County Government or Prince George's County 7th Judicial Circuit
> Court proprietary information or Protected Health Information, which
> is privileged and confidential. This E-mail is intended solely for
> the use of the individual or entity to which it is addressed. If you
> are not the intended recipient of this E-mail, you are hereby
> notified that any dissemination, distribution, copying, or action
> taken in relation to the contents of and attachments to this E-mail
> is strictly prohibited by federal law and may expose you to civil
> and/or criminal penalties. If you have received this E-mail in
> error, please notify the sender immediately and permanently delete
> the original and any copy of this E-mail and any printout.
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS Mount Failure
Right. touch is a standard unix command; it officially is used for
updating the access or last modified time of a file, but it's often used
sort of as a utility command in the way IEFBR14 can be used to create a
file.
So I would think a job step like:
//TOUCH EXEC PGM=BPXBATCH,PARM='SH touch -c /u/usr/xerox/tmpfile'
would force USS to go see if /u/usr/xerox/tmpfile exists, and therefore
require NFS to reestablish a full connection to the server, after you've
run the automount command. The -c option tells touch not to create a file
that isn't already there, so that should prevent any file from actually
being created. I haven't tested this, though I'm trying to get in touch
with one of the NFS folks to see if this is known/expected behavior.
Note that case matters in the PARM statement.
---
Kevin McKenzie
External Phone: 845-435-8282, Tie-line: 8-295-8282
z/OS Test Services - Test Architect, Provisioning
IBM Mainframe Discussion List wrote on
01/24/2019 12:31:15 PM:
> From: "Watkins, Philip S."
> To: IBM-MAIN@LISTSERV.UA.EDU
> Date: 01/24/2019 12:33 PM
> Subject: Re: NFS Mount Failure
> Sent by: IBM Mainframe Discussion List
>
> Thanks Kevin, I am trying to understand how to convert what I have
> to use BPXBATCH.
> I was not aware of the use of a "TOUCH" command.
> Any help converting would be greatly appreciated.
>
> I currently use the following on the Mainframe;
>
> MOUNT FILESYSTEM('XEROXRAW') MOUNTPOINT('/u/usr/xerox') TYPE(NFS) -
> MODE(RDWR) PARM('PGCSYS:/XEROXRAW,SOFT,SOFT,VERS(3),XLAT(Y), +
> CLN_CCSID(1047),SRV_CCSID(819)')
>
>
>
> -Original Message-
> From: IBM Mainframe Discussion List On
> Behalf Of Kevin Mckenzie
> Sent: Thursday, January 24, 2019 11:54 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: NFS Mount Failure
>
> CAUTION: This email originated from an external email domain which
> carries the additional risk that it may be a phishing email and/or
> contain malware.
>
>
> Have you thought about using BPXBATCH and something like the touch
> command to force an access of the remote file system?
>
> ---
> Kevin McKenzie
>
> External Phone: 845-435-8282, Tie-line: 8-295-8282 z/OS Test
> Services - Test Architect, Provisioning
>
> IBM Mainframe Discussion List wrote on
> 01/23/2019 01:11:26 PM:
>
> > From: Carmen Vitullo
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Date: 01/23/2019 01:12 PM
> > Subject: Re: NFS Mount Failure
> > Sent by: IBM Mainframe Discussion List
> >
> > for mounts or remounts - same here, I just run a BPXBATCH to run
> theautomount
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
> This E-mail and any of its attachments may contain Prince George’s
> County Government or Prince George's County 7th Judicial Circuit
> Court proprietary information or Protected Health Information, which
> is privileged and confidential. This E-mail is intended solely for
> the use of the individual or entity to which it is addressed. If you
> are not the intended recipient of this E-mail, you are hereby
> notified that any dissemination, distribution, copying, or action
> taken in relation to the contents of and attachments to this E-mail
> is strictly prohibited by federal law and may expose you to civil
> and/or criminal penalties. If you have received this E-mail in
> error, please notify the sender immediately and permanently delete
> the original and any copy of this E-mail and any printout.
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS Mount Failure
Thanks Kevin, I am trying to understand how to convert what I have to use
BPXBATCH.
I was not aware of the use of a "TOUCH" command.
Any help converting would be greatly appreciated.
I currently use the following on the Mainframe;
MOUNT FILESYSTEM('XEROXRAW') MOUNTPOINT('/u/usr/xerox') TYPE(NFS) -
MODE(RDWR) PARM('PGCSYS:/XEROXRAW,SOFT,SOFT,VERS(3),XLAT(Y), +
CLN_CCSID(1047),SRV_CCSID(819)')
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Kevin Mckenzie
Sent: Thursday, January 24, 2019 11:54 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: NFS Mount Failure
CAUTION: This email originated from an external email domain which carries the
additional risk that it may be a phishing email and/or contain malware.
Have you thought about using BPXBATCH and something like the touch command to
force an access of the remote file system?
---
Kevin McKenzie
External Phone: 845-435-8282, Tie-line: 8-295-8282 z/OS Test Services - Test
Architect, Provisioning
IBM Mainframe Discussion List wrote on
01/23/2019 01:11:26 PM:
> From: Carmen Vitullo
> To: IBM-MAIN@LISTSERV.UA.EDU
> Date: 01/23/2019 01:12 PM
> Subject: Re: NFS Mount Failure
> Sent by: IBM Mainframe Discussion List
>
> for mounts or remounts - same here, I just run a BPXBATCH to run
theautomount
--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
This E-mail and any of its attachments may contain Prince George’s County
Government or Prince George's County 7th Judicial Circuit Court proprietary
information or Protected Health Information, which is privileged and
confidential. This E-mail is intended solely for the use of the individual or
entity to which it is addressed. If you are not the intended recipient of this
E-mail, you are hereby notified that any dissemination, distribution, copying,
or action taken in relation to the contents of and attachments to this E-mail
is strictly prohibited by federal law and may expose you to civil and/or
criminal penalties. If you have received this E-mail in error, please notify
the sender immediately and permanently delete the original and any copy of this
E-mail and any printout.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS Mount Failure
Have you thought about using BPXBATCH and something like the touch command to force an access of the remote file system? --- Kevin McKenzie External Phone: 845-435-8282, Tie-line: 8-295-8282 z/OS Test Services - Test Architect, Provisioning IBM Mainframe Discussion List wrote on 01/23/2019 01:11:26 PM: > From: Carmen Vitullo > To: IBM-MAIN@LISTSERV.UA.EDU > Date: 01/23/2019 01:12 PM > Subject: Re: NFS Mount Failure > Sent by: IBM Mainframe Discussion List > > for mounts or remounts - same here, I just run a BPXBATCH to run theautomount -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS Mount Failure
for mounts or remounts - same here, I just run a BPXBATCH to run the automount
Carmen Vitullo
- Original Message -
From: "Philip S. Watkins"
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Wednesday, January 23, 2019 11:27:31 AM
Subject: Re: NFS Mount Failure
My unmount and mounts are issued via batch from the mainframe. What about
yours?
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Carmen Vitullo
Sent: Wednesday, January 23, 2019 11:59 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: NFS Mount Failure
CAUTION: This email originated from an external email domain which carries the
additional risk that it may be a phishing email and/or contain malware.
that's the process we follow also unfortunately
Carmen Vitullo
- Original Message -
From: "Philip S. Watkins"
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Wednesday, January 23, 2019 10:54:29 AM
Subject: Re: NFS Mount Failure
I set up a process to unmount the file server and mount it again before the
transfer job runs and it still requires at times to browse the USS file to
recover.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Carmen Vitullo
Sent: Wednesday, January 23, 2019 11:42 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: NFS Mount Failure
CAUTION: This email originated from an external email domain which carries the
additional risk that it may be a phishing email and/or contain malware.
I'm not an NFS expert but we do have NFS to Windows and HP/UX, for us once the
server is backup and a connection is requested on the 'Z' side the mount is re
established, or we run the automount for nfs, but that's really not necessary
for one server connection.
Carmen Vitullo
- Original Message -
From: "Philip S. Watkins"
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Wednesday, January 23, 2019 10:05:03 AM
Subject: NFS Mount Failure
We have an NFS mount from the z/OS 1.13 mainframe to a windows 2012 server.
Whenever the server is rebooted communication is lost between the two. I can
run an unmount and mount from the mainframe but it does not cause files on the
directory to be accessible. The mainframe shows the NFS mount as being there,
but only if I browse one of the files via USS on the directory does
communications open again. This problem started this year, not sure what has
changed on the router, but the mainframe has not changed at all.
Is there any way to automatically drive recovery from the windows server or
mainframe?
Server
Protocol Versions: Version 2, 3, 4.1
NLM grace period: 15 seconds
Lease period: 120 seconds
NFSv4.1 grace period: 240 seconds
Renew authentification
Frequency 600 seconds
Server: pgcsys
Share name: XeroxRaw
Folder path: D:\FTPData\XeroxRaw
Remote path: PGCSYS:/XeroxRaw
Protocol: NFS
Availability type: Not Clustered
XeroxRaw
D:\FTPData\XeroxRaw
NFS
Not Clustered
Mainframe
MOUNT FILESYSTEM('XEROXRAW') MOUNTPOINT('/u/usr/xerox') TYPE(NFS) -
MODE(RDWR) PARM('PGCSYS:/XEROXRAW,SOFT,SOFT,VERS(3),XLAT(Y), +
CLN_CCSID(1047),SRV_CCSID(819)')
This E-mail and any of its attachments may contain Prince George's County
Government or Prince George's County 7th Judicial Circuit Court proprietary
information or Protected Health Information, which is privileged and
confidential. This E-mail is intended solely for the use of the individual or
entity to which it is addressed. If you are not the intended recipient of this
E-mail, you are hereby notified that any dissemination, distribution, copying,
or action taken in relation to the contents of and attachments to this E-mail
is strictly prohibited by federal law and may expose you to civil and/or
criminal penalties. If you have received this E-mail in error, please notify
the sender immediately and permanently delete the original and any copy of this
E-mail and any printout.
--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
This E-mail and any of its attachments may
contain Prince George’s County Government or Prince George's County 7th
Judicial Circuit Court proprietary information or Protected Health Information,
which is privileged and confidential. This E-mail is intended solely for the
use of the individual or entity to which it is addressed. If you are not the
intended recipient of this E-mail, you are hereby notified that any
dissemination, distribution, copying, or action taken in relation to the
contents of and attachments to this E-mail is strictly proh
Re: NFS Mount Failure
My unmount and mounts are issued via batch from the mainframe. What about yours?
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Carmen Vitullo
Sent: Wednesday, January 23, 2019 11:59 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: NFS Mount Failure
CAUTION: This email originated from an external email domain which carries the
additional risk that it may be a phishing email and/or contain malware.
that's the process we follow also unfortunately
Carmen Vitullo
- Original Message -
From: "Philip S. Watkins"
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Wednesday, January 23, 2019 10:54:29 AM
Subject: Re: NFS Mount Failure
I set up a process to unmount the file server and mount it again before the
transfer job runs and it still requires at times to browse the USS file to
recover.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Carmen Vitullo
Sent: Wednesday, January 23, 2019 11:42 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: NFS Mount Failure
CAUTION: This email originated from an external email domain which carries the
additional risk that it may be a phishing email and/or contain malware.
I'm not an NFS expert but we do have NFS to Windows and HP/UX, for us once the
server is backup and a connection is requested on the 'Z' side the mount is re
established, or we run the automount for nfs, but that's really not necessary
for one server connection.
Carmen Vitullo
- Original Message -
From: "Philip S. Watkins"
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Wednesday, January 23, 2019 10:05:03 AM
Subject: NFS Mount Failure
We have an NFS mount from the z/OS 1.13 mainframe to a windows 2012 server.
Whenever the server is rebooted communication is lost between the two. I can
run an unmount and mount from the mainframe but it does not cause files on the
directory to be accessible. The mainframe shows the NFS mount as being there,
but only if I browse one of the files via USS on the directory does
communications open again. This problem started this year, not sure what has
changed on the router, but the mainframe has not changed at all.
Is there any way to automatically drive recovery from the windows server or
mainframe?
Server
Protocol Versions: Version 2, 3, 4.1
NLM grace period: 15 seconds
Lease period: 120 seconds
NFSv4.1 grace period: 240 seconds
Renew authentification
Frequency 600 seconds
Server: pgcsys
Share name: XeroxRaw
Folder path: D:\FTPData\XeroxRaw
Remote path: PGCSYS:/XeroxRaw
Protocol: NFS
Availability type: Not Clustered
XeroxRaw
D:\FTPData\XeroxRaw
NFS
Not Clustered
Mainframe
MOUNT FILESYSTEM('XEROXRAW') MOUNTPOINT('/u/usr/xerox') TYPE(NFS) -
MODE(RDWR) PARM('PGCSYS:/XEROXRAW,SOFT,SOFT,VERS(3),XLAT(Y), +
CLN_CCSID(1047),SRV_CCSID(819)')
This E-mail and any of its attachments may contain Prince George's County
Government or Prince George's County 7th Judicial Circuit Court proprietary
information or Protected Health Information, which is privileged and
confidential. This E-mail is intended solely for the use of the individual or
entity to which it is addressed. If you are not the intended recipient of this
E-mail, you are hereby notified that any dissemination, distribution, copying,
or action taken in relation to the contents of and attachments to this E-mail
is strictly prohibited by federal law and may expose you to civil and/or
criminal penalties. If you have received this E-mail in error, please notify
the sender immediately and permanently delete the original and any copy of this
E-mail and any printout.
--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
This E-mail and any of its attachments may
contain Prince George’s County Government or Prince George's County 7th
Judicial Circuit Court proprietary information or Protected Health Information,
which is privileged and confidential. This E-mail is intended solely for the
use of the individual or entity to which it is addressed. If you are not the
intended recipient of this E-mail, you are hereby notified that any
dissemination, distribution, copying, or action taken in relation to the
contents of and attachments to this E-mail is strictly prohibited by federal
law and may expose you to civil and/or criminal penalties. If you have received
this E-mail in error, please notify the sender immediately and permanently
delete the original and any copy of this E-mail and any printout.
--
For IBM-MAIN
Re: NFS Mount Failure
that's the process we follow also unfortunately
Carmen Vitullo
- Original Message -
From: "Philip S. Watkins"
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Wednesday, January 23, 2019 10:54:29 AM
Subject: Re: NFS Mount Failure
I set up a process to unmount the file server and mount it again before the
transfer job runs and it still requires at times to browse the USS file to
recover.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Carmen Vitullo
Sent: Wednesday, January 23, 2019 11:42 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: NFS Mount Failure
CAUTION: This email originated from an external email domain which carries the
additional risk that it may be a phishing email and/or contain malware.
I'm not an NFS expert but we do have NFS to Windows and HP/UX, for us once the
server is backup and a connection is requested on the 'Z' side the mount is re
established, or we run the automount for nfs, but that's really not necessary
for one server connection.
Carmen Vitullo
- Original Message -
From: "Philip S. Watkins"
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Wednesday, January 23, 2019 10:05:03 AM
Subject: NFS Mount Failure
We have an NFS mount from the z/OS 1.13 mainframe to a windows 2012 server.
Whenever the server is rebooted communication is lost between the two. I can
run an unmount and mount from the mainframe but it does not cause files on the
directory to be accessible. The mainframe shows the NFS mount as being there,
but only if I browse one of the files via USS on the directory does
communications open again. This problem started this year, not sure what has
changed on the router, but the mainframe has not changed at all.
Is there any way to automatically drive recovery from the windows server or
mainframe?
Server
Protocol Versions: Version 2, 3, 4.1
NLM grace period: 15 seconds
Lease period: 120 seconds
NFSv4.1 grace period: 240 seconds
Renew authentification
Frequency 600 seconds
Server: pgcsys
Share name: XeroxRaw
Folder path: D:\FTPData\XeroxRaw
Remote path: PGCSYS:/XeroxRaw
Protocol: NFS
Availability type: Not Clustered
XeroxRaw
D:\FTPData\XeroxRaw
NFS
Not Clustered
Mainframe
MOUNT FILESYSTEM('XEROXRAW') MOUNTPOINT('/u/usr/xerox') TYPE(NFS) -
MODE(RDWR) PARM('PGCSYS:/XEROXRAW,SOFT,SOFT,VERS(3),XLAT(Y), +
CLN_CCSID(1047),SRV_CCSID(819)')
This E-mail and any of its attachments may contain Prince George's County
Government or Prince George's County 7th Judicial Circuit Court proprietary
information or Protected Health Information, which is privileged and
confidential. This E-mail is intended solely for the use of the individual or
entity to which it is addressed. If you are not the intended recipient of this
E-mail, you are hereby notified that any dissemination, distribution, copying,
or action taken in relation to the contents of and attachments to this E-mail
is strictly prohibited by federal law and may expose you to civil and/or
criminal penalties. If you have received this E-mail in error, please notify
the sender immediately and permanently delete the original and any copy of this
E-mail and any printout.
--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
This E-mail and any of its attachments may contain Prince George’s County
Government or Prince George's County 7th Judicial Circuit Court proprietary
information or Protected Health Information, which is privileged and
confidential. This E-mail is intended solely for the use of the individual or
entity to which it is addressed. If you are not the intended recipient of this
E-mail, you are hereby notified that any dissemination, distribution, copying,
or action taken in relation to the contents of and attachments to this E-mail
is strictly prohibited by federal law and may expose you to civil and/or
criminal penalties. If you have received this E-mail in error, please notify
the sender immediately and permanently delete the original and any copy of this
E-mail and any printout.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS Mount Failure
I set up a process to unmount the file server and mount it again before the
transfer job runs and it still requires at times to browse the USS file to
recover.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Carmen Vitullo
Sent: Wednesday, January 23, 2019 11:42 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: NFS Mount Failure
CAUTION: This email originated from an external email domain which carries the
additional risk that it may be a phishing email and/or contain malware.
I'm not an NFS expert but we do have NFS to Windows and HP/UX, for us once the
server is backup and a connection is requested on the 'Z' side the mount is re
established, or we run the automount for nfs, but that's really not necessary
for one server connection.
Carmen Vitullo
- Original Message -
From: "Philip S. Watkins"
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Wednesday, January 23, 2019 10:05:03 AM
Subject: NFS Mount Failure
We have an NFS mount from the z/OS 1.13 mainframe to a windows 2012 server.
Whenever the server is rebooted communication is lost between the two. I can
run an unmount and mount from the mainframe but it does not cause files on the
directory to be accessible. The mainframe shows the NFS mount as being there,
but only if I browse one of the files via USS on the directory does
communications open again. This problem started this year, not sure what has
changed on the router, but the mainframe has not changed at all.
Is there any way to automatically drive recovery from the windows server or
mainframe?
Server
Protocol Versions: Version 2, 3, 4.1
NLM grace period: 15 seconds
Lease period: 120 seconds
NFSv4.1 grace period: 240 seconds
Renew authentification
Frequency 600 seconds
Server: pgcsys
Share name: XeroxRaw
Folder path: D:\FTPData\XeroxRaw
Remote path: PGCSYS:/XeroxRaw
Protocol: NFS
Availability type: Not Clustered
XeroxRaw
D:\FTPData\XeroxRaw
NFS
Not Clustered
Mainframe
MOUNT FILESYSTEM('XEROXRAW') MOUNTPOINT('/u/usr/xerox') TYPE(NFS) -
MODE(RDWR) PARM('PGCSYS:/XEROXRAW,SOFT,SOFT,VERS(3),XLAT(Y), +
CLN_CCSID(1047),SRV_CCSID(819)')
This E-mail and any of its attachments may contain Prince George's County
Government or Prince George's County 7th Judicial Circuit Court proprietary
information or Protected Health Information, which is privileged and
confidential. This E-mail is intended solely for the use of the individual or
entity to which it is addressed. If you are not the intended recipient of this
E-mail, you are hereby notified that any dissemination, distribution, copying,
or action taken in relation to the contents of and attachments to this E-mail
is strictly prohibited by federal law and may expose you to civil and/or
criminal penalties. If you have received this E-mail in error, please notify
the sender immediately and permanently delete the original and any copy of this
E-mail and any printout.
--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
This E-mail and any of its attachments may contain Prince George’s County
Government or Prince George's County 7th Judicial Circuit Court proprietary
information or Protected Health Information, which is privileged and
confidential. This E-mail is intended solely for the use of the individual or
entity to which it is addressed. If you are not the intended recipient of this
E-mail, you are hereby notified that any dissemination, distribution, copying,
or action taken in relation to the contents of and attachments to this E-mail
is strictly prohibited by federal law and may expose you to civil and/or
criminal penalties. If you have received this E-mail in error, please notify
the sender immediately and permanently delete the original and any copy of this
E-mail and any printout.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS Mount Failure
I'm not an NFS expert but we do have NFS to Windows and HP/UX, for us once the
server is backup and a connection is requested on the 'Z' side the mount is re
established, or we run the automount for nfs, but that's really not necessary
for one server connection.
Carmen Vitullo
- Original Message -
From: "Philip S. Watkins"
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Wednesday, January 23, 2019 10:05:03 AM
Subject: NFS Mount Failure
We have an NFS mount from the z/OS 1.13 mainframe to a windows 2012 server.
Whenever the server is rebooted communication is lost between the two. I can
run an unmount and mount from the mainframe but it does not cause files on the
directory to be accessible. The mainframe shows the NFS mount as being there,
but only if I browse one of the files via USS on the directory does
communications open again. This problem started this year, not sure what has
changed on the router, but the mainframe has not changed at all.
Is there any way to automatically drive recovery from the windows server or
mainframe?
Server
Protocol Versions: Version 2, 3, 4.1
NLM grace period: 15 seconds
Lease period: 120 seconds
NFSv4.1 grace period: 240 seconds
Renew authentification
Frequency 600 seconds
Server: pgcsys
Share name: XeroxRaw
Folder path: D:\FTPData\XeroxRaw
Remote path: PGCSYS:/XeroxRaw
Protocol: NFS
Availability type: Not Clustered
XeroxRaw
D:\FTPData\XeroxRaw
NFS
Not Clustered
Mainframe
MOUNT FILESYSTEM('XEROXRAW') MOUNTPOINT('/u/usr/xerox') TYPE(NFS) -
MODE(RDWR) PARM('PGCSYS:/XEROXRAW,SOFT,SOFT,VERS(3),XLAT(Y), +
CLN_CCSID(1047),SRV_CCSID(819)')
This E-mail and any of its attachments may contain Prince George's County
Government or Prince George's County 7th Judicial Circuit Court proprietary
information or Protected Health Information, which is privileged and
confidential. This E-mail is intended solely for the use of the individual or
entity to which it is addressed. If you are not the intended recipient of this
E-mail, you are hereby notified that any dissemination, distribution, copying,
or action taken in relation to the contents of and attachments to this E-mail
is strictly prohibited by federal law and may expose you to civil and/or
criminal penalties. If you have received this E-mail in error, please notify
the sender immediately and permanently delete the original and any copy of this
E-mail and any printout.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
NFS Mount Failure
We have an NFS mount from the z/OS 1.13 mainframe to a windows 2012 server.
Whenever the server is rebooted communication is lost between the two. I can
run an unmount and mount from the mainframe but it does not cause files on the
directory to be accessible. The mainframe shows the NFS mount as being there,
but only if I browse one of the files via USS on the directory does
communications open again. This problem started this year, not sure what has
changed on the router, but the mainframe has not changed at all.
Is there any way to automatically drive recovery from the windows server or
mainframe?
Server
Protocol Versions: Version 2, 3, 4.1
NLM grace period: 15 seconds
Lease period: 120 seconds
NFSv4.1 grace period: 240 seconds
Renew authentification
Frequency 600 seconds
Server: pgcsys
Share name: XeroxRaw
Folder path: D:\FTPData\XeroxRaw
Remote path: PGCSYS:/XeroxRaw
Protocol: NFS
Availability type: Not Clustered
XeroxRaw
D:\FTPData\XeroxRaw
NFS
Not Clustered
Mainframe
MOUNT FILESYSTEM('XEROXRAW') MOUNTPOINT('/u/usr/xerox') TYPE(NFS) -
MODE(RDWR) PARM('PGCSYS:/XEROXRAW,SOFT,SOFT,VERS(3),XLAT(Y), +
CLN_CCSID(1047),SRV_CCSID(819)')
This E-mail and any of its attachments may contain Prince George's County
Government or Prince George's County 7th Judicial Circuit Court proprietary
information or Protected Health Information, which is privileged and
confidential. This E-mail is intended solely for the use of the individual or
entity to which it is addressed. If you are not the intended recipient of this
E-mail, you are hereby notified that any dissemination, distribution, copying,
or action taken in relation to the contents of and attachments to this E-mail
is strictly prohibited by federal law and may expose you to civil and/or
criminal penalties. If you have received this E-mail in error, please notify
the sender immediately and permanently delete the original and any copy of this
E-mail and any printout.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS on Mainframe
Hi Allan BPXMTEXT does not support reason code qualifier 6E05 From Network File System Guide and Reference Version 2 Release 3 SC23-6883-30 6E Indicates NFS Client modules (that is, GFSC). 05 NFS reason codes See Table 74 on page 457. 0002 NFSERR_NOENT No such file or directory A component of a specified path name does not exist, or the path name is an empty string. Action: Ensure that the file or directory exists. Got my NFS client working and now off to NFS server before venturing in to NFS security and encryption. Component trace for mvsnfsc also worked like a charm, just need doco to interpret trace entries although errors are error code stands out. Thanks a lot. Kind Regards Munif -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS on Mainframe
TSO BPXMTEXT where is the reason code from the message. In the case below: "TSO BPXMTEXT 6E050002" -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Munif Sadek Sent: Thursday, December 7, 2017 11:26 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: NFS on Mainframe Apologies Listers Falls alarm..Message is documented in SC23-6883-30 as Parm invalid. Now I am in much better place with IP packets trace and following error messages BPXF162E ASYNCHRONOUS MOUNT FAILED FOR FILE SYSTEM NFS. BPXF135E RETURN CODE 0081, REASON CODE 6E050002. THE MOUNT FAILED FOR FILE SYSTEM NFS. Kind regards Munif. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. ::DISCLAIMER:: The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS on Mainframe
Apologies Listers Falls alarm..Message is documented in SC23-6883-30 as Parm invalid. Now I am in much better place with IP packets trace and following error messages BPXF162E ASYNCHRONOUS MOUNT FAILED FOR FILE SYSTEM NFS. BPXF135E RETURN CODE 0081, REASON CODE 6E050002. THE MOUNT FAILED FOR FILE SYSTEM NFS. Kind regards Munif. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS on Mainframe
Thank you Mr Sipples
Got my NFS client started successfully (ignored following warning as no
security initially and target Unix server is PINGable)
GFSC284I NETWORK FILE SYSTEM CLIENT COULD NOT GET GSS CREDENTIALS
FOR THE NFS CLIENT : GSS API krb5_get_default_realm() FAILED
WITH GSS MAJOR STATUS 96C73ADF GSS MINOR STATUS
Now when I am trying to mount a UNIX file via zOS command
MOUNT FILESYSTEM(NFS) +
TYPE(NFS) +
MOUNTPOINT('/NFS')+
MODE(RDWR)+
PARM('nnn.nnn.nnn.nnn:"/nfs,",') +
NOSETUID +
TAG(TEXT,1047)+
WAIT
I am getting
BPXF135E RETURN CODE 0079, REASON CODE 6E017015. THE MOUNT FAILED FOR FILE
SYSTEM NFS
or
BPXF135E RETURN CODE 0079, REASON CODE 6E017017. THE MOUNT FAILED FOR FILE
SYSTEM NFS
Cant find anywhere Reason Code "6E017017" including in IBM SR, Google.
Cant find any incoming / outgoing packets between zOS and Unix server
Did try to run a CT on mvsnfsc with OPTIONS All, but component trace is not
recording any data.
Thanks once again for your advise, and helping me out
kind regards
Munif
Can someone please give me simple syntax for zOS NFS client MOUNT please or
point me in the right direction.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS on Mainframe
Yes, there is a z/OS NFS "Quick Setup Guide," available here: https://www.ibm.com/developerworks/community/blogs/e0c474f8-3aad-4f01-8bca-f2c12b576ac9/entry/Shortcut_bringing_up_z_OS_NFS?lang=en This guide covers both the NFS Server and NFS Client. If you're setting up only the NFS Client (and expect to stay that way), you can skip the NFS Server-only steps. Timothy Sipples IT Architect Executive, Industry Solutions, IBM Z and LinuxONE, AP/GCG/MEA E-Mail: sipp...@sg.ibm.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS on Mainframe
On Tue, 5 Dec 2017 19:52:17 -0600, John McKown wrote: >> > >> We tried that once. Failed because of a certain application that used >> commas in filenames. > >Why would a comma cause a problem? I'm not NFS literate. But wouldn't >PATH='/some/directory,me/file.txt' work on NFS as well as zFS? > Network File System Guide and Reference Version 2 Release 3 Naming MVS files The z/OS NFS server uses the comma (,) as a delimiter to a list of file attributes. Do not use a comma as a special character in file name. For example, you can enter this command: $ vi "/u/smith/new,text" This indicates to NFS that a file called new is being edited in the attribute text mode, not file new,text. And while the delimiter can be changed, (perhaps entirely disabled, unlike ISPF's delimiter), this is in global options and may adversely affect other users who depent on using ',' as a delimiter. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS on Mainframe
On Tue, Dec 5, 2017 at 5:11 PM, Paul Gilmartin < 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > On Mon, 4 Dec 2017 23:23:18 -0600, Munif Sadek wrote: > > >To start with. I am planning to l configure NFS client on my Sandbox zOS > 2.3 LPAR and NFS server on sandbox AIX 7.1 LPAR (using classic IBM > Hypervisor). > > > >Depending on the outcome, I may switch zOS to be the NFS server. Our main > objective is stop FTPing tens of reports but write them to NFS so that > end-users (non mainframers) can pick them up. > > > We tried that once. Failed because of a certain application that used > commas in filenames. > Why would a comma cause a problem? I'm not NFS literate. But wouldn't PATH='/some/directory,me/file.txt' work on NFS as well as zFS? > > -- gil > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- I have a theory that it's impossible to prove anything, but I can't prove it. Maranatha! <>< John McKown -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS on Mainframe
Hi Andrew Thanks for the hint. Last time I read about HTTPS, when I was attempting to implement SSL on our ezasocket CICS Listener. I just hope that I do not need another licensed product. I do not think HTTPS is the solution in our case but may be a replacement for FTP. NFS is such a *out of box things* in non-Mainframe world and surprise to see its not popular/standard in Mainframe which is taken for granted to be large Data server. I have got NFS Guide and reference 640 Pages manual to review and was expecting if any kind lister can give some pointer to implement NFS with and without security. (neither I have LDAP or Kerberos customized in our mainframe, so there will be heavy lifting) Thanks a lot, Kind regards Munif -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS on Mainframe
On Wed, 6 Dec 2017 10:57:21 +1100, Andrew Rowley wrote: >On 5/12/2017 4:23 PM, Munif Sadek wrote: >> Depending on the outcome, I may switch zOS to be the NFS server. Our main >> objective is stop FTPing tens of reports but write them to NFS so that >> end-users (non mainframers) can pick them up. >> >Have you considered serving them via HTTPS instead? > Are the "reports" all text; no binary; no packed decimal? Might be practical with a script to add headers and footers and entify "dangerous" characters, "&", "<", and ">". And some browsers will treat a document lacking HTML headers as preformatted text. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS on Mainframe
On 5/12/2017 4:23 PM, Munif Sadek wrote: Depending on the outcome, I may switch zOS to be the NFS server. Our main objective is stop FTPing tens of reports but write them to NFS so that end-users (non mainframers) can pick them up. Have you considered serving them via HTTPS instead? -- Andrew Rowley Black Hill Software -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS on Mainframe
I'm jumping in on thisis there any quickstarts out there to get NFS (Client or server?) installed on z/os? Dennis -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Paul Gilmartin Sent: Tuesday, December 5, 2017 3:12 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: NFS on Mainframe On Mon, 4 Dec 2017 23:23:18 -0600, Munif Sadek wrote: >To start with. I am planning to l configure NFS client on my Sandbox zOS 2.3 >LPAR and NFS server on sandbox AIX 7.1 LPAR (using classic IBM Hypervisor). > >Depending on the outcome, I may switch zOS to be the NFS server. Our main >objective is stop FTPing tens of reports but write them to NFS so that >end-users (non mainframers) can pick them up. > We tried that once. Failed because of a certain application that used commas in filenames. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS on Mainframe
On Mon, 4 Dec 2017 23:23:18 -0600, Munif Sadek wrote: >To start with. I am planning to l configure NFS client on my Sandbox zOS 2.3 >LPAR and NFS server on sandbox AIX 7.1 LPAR (using classic IBM Hypervisor). > >Depending on the outcome, I may switch zOS to be the NFS server. Our main >objective is stop FTPing tens of reports but write them to NFS so that >end-users (non mainframers) can pick them up. > We tried that once. Failed because of a certain application that used commas in filenames. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS on Mainframe
To start with. I am planning to l configure NFS client on my Sandbox zOS 2.3 LPAR and NFS server on sandbox AIX 7.1 LPAR (using classic IBM Hypervisor). Depending on the outcome, I may switch zOS to be the NFS server. Our main objective is stop FTPing tens of reports but write them to NFS so that end-users (non mainframers) can pick them up. Do not want to mention NetApp as of yet and waiting for *corporate* security guidelines, especially with the NFS <-->CIFS. regards Munif -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: EXTERNAL: Re: NFS on Mainframe [USAA Confidential]
I've had experience with both a NFS client and server running on z/OS. I'd recommend the NFS server since it performs and functions better. USAA Confidential -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Timothy Sipples Sent: Monday, December 04, 2017 3:01 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: EXTERNAL: Re: NFS on Mainframe To clarify, z/OS is the NFS client, and something else is the NFS server, correct? It'd be helpful to know exactly what is the NFS server. If it's AIX, what release? If it's NetApp's NFS server, same question. Timothy Sipples IT Architect Executive, Industry Solutions, IBM Z and LinuxONE, AP/GCG/MEA E-Mail: sipp...@sg.ibm.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS on Mainframe
If AIX is the NFS server, you have specific steps to do to export the filesystem, and add the correct IP to the export list to allow it to be mounted. You will need to find a friend in either Network storage or Open system to do some of the admin setup for you. _ Dave Jousma Manager Mainframe Engineering, Assistant Vice President david.jou...@53.com 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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Munif Sadek Sent: Sunday, December 03, 2017 10:50 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: NFS on Mainframe **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** Dear Listers I need your help in mounting pSeries (and may be NetApp) NFS folder on my zOS 2.3. I have tried it before NFS(and also SMB) but had give up on one pretext or other. Yes I am corporate slave and have no authority over Network Storage, Open system Certificate Management etc and had to get my requirements right. Is anyone doing it and if yes, May I please get any pointers. kind regards, Munif -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS on Mainframe
Last time I looked (about 15 years ago), zOS has both an NFS client and server available. > Timothy Sipples <mailto:sipp...@sg.ibm.com> > December 4, 2017 at 4:01 AM > To clarify, z/OS is the NFS client, and something else is the NFS server, > correct? > > It'd be helpful to know exactly what is the NFS server. If it's AIX, what > release? If it's NetApp's NFS server, same question. > > > Timothy Sipples > IT Architect Executive, Industry Solutions, IBM Z and LinuxONE, AP/GCG/MEA > E-Mail: sipp...@sg.ibm.com > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > Please be alert for any emails that may ask you for login information > or directs you to login via a link. If you believe this message is a > phish or aren't sure whether this message is trustworthy, please send > the original message as an attachment to 'phish...@timeinc.com'. > -- Mark Jacobs Time Customer Service Global Technology Services The standard you walk past is the standard you accept. Lt. Gen. David Morrison -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS on Mainframe
To clarify, z/OS is the NFS client, and something else is the NFS server, correct? It'd be helpful to know exactly what is the NFS server. If it's AIX, what release? If it's NetApp's NFS server, same question. Timothy Sipples IT Architect Executive, Industry Solutions, IBM Z and LinuxONE, AP/GCG/MEA E-Mail: sipp...@sg.ibm.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
NFS on Mainframe
Dear Listers I need your help in mounting pSeries (and may be NetApp) NFS folder on my zOS 2.3. I have tried it before NFS(and also SMB) but had give up on one pretext or other. Yes I am corporate slave and have no authority over Network Storage, Open system Certificate Management etc and had to get my requirements right. Is anyone doing it and if yes, May I please get any pointers. kind regards, Munif -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Windows NFS (was: z14 and z/OS 2.3 Blog Post)
On Sat, 29 Jul 2017 10:03:43 +0800, Timothy Sipples wrote:
>
>Microsoft includes NFS ("Services for NFS") in Windows 7 Enterprise and
>Ultimate. (I don't think Windows 8.x had an Ultimate flavor, so in the
>Windows 8.x stream Microsoft's NFS is only in Windows 8 Enterprise.) All
>that really changed in Windows 10 is that Microsoft included NFS in their
>lower Windows 10 license tiers.
>
What security mechanism(s) do(es) it provide:
o UID/GID?
(What do UID and GID mean to Windows?)
o MVSLOGIN?
o Kerberos?
o Other (specify)?
Does it support:
o Classic data sets?
(ISPF-style member serialization (this seems to be a z/OS server function)?
o HFS/zFS files?
-- gil
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
How to use the Win7 NFS client with z/OS NFS server
Anyone using the Win7 NFS client with the z/OS NFS server, and if so, what is the mount command to use to get to a file, say a PDS member? Thanks, Mark Regan -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
ISPF Extended Stats and NFS
(I posted this to ISPF-L a few days ago and got no replies. But I remain curious, so I'll try here. Perhaps IBMTCP-L or even MVS-OE would be better?) I was mildly surprised that when I create PDSE members via the z/OS 2.2 NFS server, then display them with "ls" on a Solaris workstation, the Time Changed appears with a granularity of microseconds. More surprised because: z/OS z/OS 2.2.0 ISPF z/OS V2R2 ISPF Messages and Codes Diagnostic Tools and Information Diagnostic information ISPF statistics entry in a PDS directory ... gives no hint of where this information resides. Does PDSE rather than ISPF maintain it? The granularity is seconds for a PDS. And, when I try to edit such a member I am warned, apparently: ISRE548 -WARNING- Extended statistics exist for this member but will be Explanation The site does permit extended statistics to be recorded in the PDS directory but they already exist. System programmer response Use the ISPF configuration dialog (ISPCCONF) to enable Extended Statistics to be stored. User response Contact the Systems Programmer (copied and pasted with apparent typos) However, the CHANGED time is updated, still with microsecond granularity and bit 1 of byte 3 remains set. Doesn't look exactly like OA30217 or OA31634. It looks as if ISPCCONF sets global options, not controlled by any RACF profile. Is NFS server breaking a rule? Is Edit breaking a rule by not obliterating the extended stats as it threatened? -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Mounting NFS Directory on zOS as Binary
Caveat: getting the daily digest implies response delays...
Jasi: the Knowledge Centre page for BPXF135E showed up at the top of the
Google search for me. If you research the message further, you find it
indicates 'can't reach host'.
Perhaps the list shouldn't be your first stop. [1] Common courtesy, really.
[1] if it wasn't, you should indicate what research you did so we don't have
to repeat it.
> signature = 8 lines follows <
Neil Duffee, Joe Sysprog, uOttawa, Ottawa, Ont, Canada
telephone:1 613 562 5800 x4585 fax:1 613 562 5161
mailto:NDuffee of uOttawa.ca http:/ /aix1.uOttawa.ca/ ~nduffee
“How *do* you plan for something like that?” Guardian Bob, Reboot
“For every action, there is an equal and opposite criticism.”
“Systems Programming: Guilty, until proven innocent” John Norgauer 2004
"Schrodinger's backup: The condition of any backup is unknown until a restore
is attempted." John McKown 2015
-Original Message-
From: Jasi Grewal [mailto:ja...@hot...com]
Sent: June 21, 2016 16:48
Subject: Mounting NFS Directory on zOS as Binary
Greetings, I am trying to mount this zLinux Filesystem on zOS using NFS with
the following command and it seems that either is not supported as Binary or I
am missing something.
mount filesystem('lozlnx00:/sandbox') type(nfs)
mountpoint('/nfsmnts/lozlnx00/sandbox')
parm('lozlnx00:"/sandbox,binary",xlat(y),vers(3)')
I get the following error:
BPXF162E ASYNCHRONOUS MOUNT FAILED FOR FILE SYSTEM LOZLNX00:/SANDBOX.
BPXF135E RETURN CODE 046A, REASON CODE 6E2A1003. THE MOUNT FAILED FOR FILE
SYSTEM LOZLNX00:/SANDBOX.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Mounting NFS Directory on zOS as Binary
Hi Donald, Thanks for the response and it is working now as binary and all we needed to do was change to xlat(n) and that is all. Regards, Jasi. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Mounting NFS Directory on zOS as Binary
The difficult part can be establishing security. What do you
have in your export file for security? For initial testing,
easiest to just allow access to the z/OS NFS from the
IP address of your zLinux with a command like:
/sandbox1 -rw=192.168.231.10
Then add better security after you get it working.
Also do you have the host names defined in a
host table or DNS server?
--
Donald J.
dona...@4email.net
On Tue, Jun 21, 2016, at 01:47 PM, Jasi Grewal wrote:
> Greetings, I am trying to mount this zLinux Filesystem on zOS using NFS with
> the following command and it seems that either is not supported as Binary or
> I am missing something.
>
> mount filesystem('lozlnx00:/sandbox') type(nfs)
> mountpoint('/nfsmnts/lozlnx00/sandbox')
> parm('lozlnx00:"/sandbox,binary",xlat(y),vers(3)')
>
> I get the following error:
> BPXF162E ASYNCHRONOUS MOUNT FAILED FOR FILE SYSTEM LOZLNX00:/SANDBOX.
>
> BPXF135E RETURN CODE 046A, REASON CODE 6E2A1003. THE MOUNT FAILED FOR
> FILE SYSTEM LOZLNX00:/SANDBOX.
>
> Any information would be grateful.
> Thank You in advance,
> Regards,
>
> Jasi Grewal.
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
--
http://www.fastmail.com - Access all of your messages and folders
wherever you are
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Mounting NFS Directory on zOS as Binary
On Tue, Jun 21, 2016 at 3:47 PM, Jasi Grewal <ja...@hotmail.com> wrote:
> Greetings, I am trying to mount this zLinux Filesystem on zOS using NFS
> with the following command and it seems that either is not supported as
> Binary or I am missing something.
>
> mount filesystem('lozlnx00:/sandbox') type(nfs)
> mountpoint('/nfsmnts/lozlnx00/sandbox')
> parm('lozlnx00:"/sandbox,binary",xlat(y),vers(3)')
>
Why do you have ",binary" _and_ xlat(y) ? they are saying the exact
opposite. You might try xlat(n). I'm not guaranteeing anything. And I'm
leaving for the day.
>
> I get the following error:
> BPXF162E ASYNCHRONOUS MOUNT FAILED FOR FILE SYSTEM LOZLNX00:/SANDBOX.
> BPXF135E RETURN CODE 046A, REASON CODE 6E2A1003. THE MOUNT FAILED FOR
> FILE SYSTEM LOZLNX00:/SANDBOX.
>
> Any information would be grateful.
> Thank You in advance,
> Regards,
>
> Jasi Grewal.
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
--
"Pessimism is a admirable quality in an engineer. Pessimistic people check
their work three times, because they're sure that something won't be right.
Optimistic people check once, trust in Solis-de to keep the ship safe, then
blow everyone up."
"I think you're mistaking the word optimistic for inept."
"They've got a similar ring to my ear."
>From "Star Nomad" by Lindsay Buroker:
Maranatha! <><
John McKown
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Mounting NFS Directory on zOS as Binary
Greetings, I am trying to mount this zLinux Filesystem on zOS using NFS with
the following command and it seems that either is not supported as Binary or I
am missing something.
mount filesystem('lozlnx00:/sandbox') type(nfs)
mountpoint('/nfsmnts/lozlnx00/sandbox')
parm('lozlnx00:"/sandbox,binary",xlat(y),vers(3)')
I get the following error:
BPXF162E ASYNCHRONOUS MOUNT FAILED FOR FILE SYSTEM LOZLNX00:/SANDBOX.
BPXF135E RETURN CODE 046A, REASON CODE 6E2A1003. THE MOUNT FAILED FOR FILE
SYSTEM LOZLNX00:/SANDBOX.
Any information would be grateful.
Thank You in advance,
Regards,
Jasi Grewal.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
NFS and ISPF member timestamps
It appears that NFS attempts to create and display NFS timestamps. But, on Solaris, with a PDS mounted from z/OS, I see: user@SunOS.5.11: ls -alErt -rw-rw-rw- 1 root root7608 2016-05-12 18:49:25.498515000 -0600 allasm ... -rw-rw-rw- 1 root root 177 2016-05-12 18:49:26.115548000 -0600 proxy -rw-rw-rw- 1 root root 15318 2016-05-12 18:49:26.156919000 -0600 putcopy -rw-rw-rw- 1 root root5268 2016-05-12 18:49:26.190468000 -0600 putpipe -rw-rw-rw- 1 root root 36 2016-05-12 18:49:26.220976000 -0600 rexx -rw-rw-rw- 1 root root1437 2016-05-12 18:49:26.255249000 -0600 showfmt -rw-rw-rw- 1 root root 558 2016-05-12 18:49:26.296425000 -0600 smpp -rw-rw-rw- 1 root root 64 2016-05-12 18:49:26.315789000 -0600 syscall -rw-rw-rw- 1 root root 751 2016-05-12 18:49:26.335391000 -0600 termvars -rw-rw-rw- 1 root root 731 2016-05-12 18:49:26.355828000 -0600 testspbw -rw-rw-rw- 1 root root 39757 2016-05-12 18:49:26.457639000 -0600 trkrelfi -rw-rw-rw- 1 root root 12691 2016-05-12 18:49:26.511337000 -0600 trksmpfx -rw-rw-rw- 1 root root 18723 2016-05-12 18:49:26.541057000 -0600 xfplink -rw-rw-rw- 1 root root 13423 2016-06-01 17:45:56.382017000 -0600 isfunld drwxrwxrwx 2 root root8192 2016-06-08 19:22:45.0 -0600 .. drwxrwxrwx 2 root root1024 2016-06-08 19:22:45.0 -0600 . ISPF, sorted by Changed ascending, shows me: DSLISTuser.CLISTRow 001 of 035 Command ===> ,Scroll ===> CSR Name Prompt Size Created Changed ID _ MAKEASM 93 1989/11/17 1989/11/17 13:16:00 user ... _ SYSCALL 1 2015/04/23 2015/04/23 10:42:50 user _ LMABORT 7 2015/10/20 2015/10/20 14:04:00 user _ SMPP 20 2015/11/05 2015/11/05 15:06:00 user _ PROXY 5 2016/01/13 2016/01/13 19:40:00 user _ CHDIR37 2016/02/29 2016/02/29 11:11:00 user _ ISPFHFS 9 2016/03/08 2016/03/08 16:11:00 user _ ISPFWHAT 33 2016/03/08 2016/03/08 16:11:00 user _ ISREDIT 8 2016/03/08 2016/03/08 16:11:00 user _ ISPSHOW 35 2016/02/22 2016/03/08 16:12:00 user _ SHOWFMT 53 2016/03/08 2016/03/08 16:13:00 user _ TERMVARS 20 2016/03/08 2016/03/08 19:11:00 user _ PUTPIPE 195 2016/05/12 2016/05/12 18:42:00 user _ ISFUNLD 422 2015/05/06 2016/06/01 17:45:00 user **End** ISPF shows resolution no finer than one minute. NFS shows nanoseconds. The only entry for which NFS agrees with ISPF is the newest one. (I suspect that might be cached. But where?) For all other entries, NFS shows timestamps distributed over about one second about a month ago. I suspect the newer ones were changed by NFS; the others by other means (FTP, OMVS "cp", ISPF Edit, ...). The Changed dates ISPF shows are plausible; I haven't logs to confirm. What's happening here? (Would this be better asked on ISPF-L or MVS-OE?) - gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS Client implementation query
Additionally, you cannot manually start stop the actual address space yourself.
Here are the notes I have for starting and stopping NFS client:
Stop NFS client#
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. To stop the z/OS NFS client
gracefully the system operator can use the modify operator command omvs,stoppfs
specifying the NFS client, as follows:
F OMVS,STOPPFS=NFS
You will respond to the "xx BPXI078D STOP OF NFS REQUESTED. REPLY 'Y' TO
PROCEED. ANY OTHER REPLY WILL CANCEL THIS STOP." which shuts down the NFS
client.
Restart #
We use a SYS1.PARMLIB(BPXPRMNF) that can be used to restart the NFS client if
it is stopped.
SETOMVS RESET=(NF)
Which contains
EDIT SYS1.PARMLIB(BPXPRMNF) - 01.00 Columns 0
Command ===> Scroll
** * Top of Data ***
01 /***/
02 /* */
000003 /* NFS Client*/
04 /*use SETOMVS RESET=(NF) to restart totally dead client */
05 /***/
06 FILESYSTYPE TYPE(NFS)/* Network Files System */
07 ENTRYPOINT(GFSCINIT) /* Entrypoint for NFS Client */
08 /* PARM('')defaults PARM for NFS Client */
09 ASNAME(MVSNFSC,'SUB=MSTR')
10 /* Auto-started PROC *REQ* */
11 /**/
_
Dave Jousma
Assistant Vice President, Mainframe Engineering
david.jou...@53.com
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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of RCG
Sent: Thursday, September 17, 2015 11:11 AM
To: IBM-MAIN@LISTSERV.UA.EDU
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..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 volumescde 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
//*
//* IS TCP/IP DATA FILE
//* IS OS/390 NETWORK FILE SYSTEM CLIENT
//*TARGET LIBRARY
//* IS LANGUAGE ENVIRONMENT RUNTIME LIBRARY
//*
//SYSTCPD DD DISP=SHR,DSN=SYS3.OS.TCPIP.PROFILE.OS390R25(TCPDATA)
//STEPLIB DD DISP=SHR,DSN=
// 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=
//*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 SEQ
Re: NFS Client implementation query
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 ASNAMEDESC STSTART/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 IOEFSCMZFS LOCAL A 2015/09/13 06.36.53
HFS GFUAINIT LOCAL A 2015/09/13 06.36.52
PFS TYPE DOMAINMAXSOCK OPNSOCK HIGHUSED
INET AF_INET 6 2735
UDS AF_UNIX 1 2030
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= USER=OMVSKERN
POLICY=/etc/auto.master
So can't see NFS here..
On Thu, Sep 17, 2015 at 11:34 AM, RCG <rkcgowda1...@gmail.com> 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 <stars...@mindspring.com
> > 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.zos.v2r1.idan400/nfsconf.htm
>>
>>
>> Lizette
>>
>>
>> > -Original Message-
>> > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
>> On
>> > Behalf Of RCG
>> > Sent: Thursday, September 17, 2015 8:11 AM
>> > To: IBM-MAIN@LISTSERV.UA.EDU
>> > 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..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 volumescde 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
>> > //*
>> > //* IS TCP/IP DATA FILE
>> > //* IS OS/390 NETWORK FILE SYSTEM CLIENT
>> > //*TARGET LIBRARY
>> > //* IS LANGUAGE ENVIRONMENT RUNTIME LIBRARY
>> > //*
>> > //SYSTCPD DD DISP=SHR,DSN=SYS3.OS.TCPIP.PROFILE.OS390R25(TCPDATA)
>> > //STEPLIB DD DISP=SHR,DSN=
>> > //
Re: NFS Client implementation query
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 = 0079, REASON CODE = 12030259 BPXF202I DOMAIN AF_INET WAS NOT ACTIVATED FOR FILE SYSTEM 866 TYPE INET. RETURN CODE = 0079, REASON CODE = 743A0259 BPXO015I THE SETOMVS COMMAND WAS SUCCESSFUL. = On Thu, Sep 17, 2015 at 12:02 PM, Lizette Koehler <stars...@mindspring.com> 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:IBM-MAIN@LISTSERV.UA.EDU] On > > Behalf Of RCG > > Sent: Thursday, September 17, 2015 8:52 AM > > To: IBM-MAIN@LISTSERV.UA.EDU > > 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 <rkcgowda1...@gmail.com> 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 ASNAMEDESC STSTART/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 IOEFSCMZFS LOCAL A 2015/09/13 06.36.53 > > >HFS GFUAINIT LOCAL A 2015/09/13 06.36.52 > > > > > > PFS TYPE DOMAINMAXSOCK OPNSOCK HIGHUSED > > >INET AF_INET 6 2735 > > >UDS AF_UNIX 1 2030 > > > > > > 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= USER=OMVSKERN > > >POLICY=/etc/auto.master > > > > > > So can't see NFS here.. > > > > > > On Thu, Sep 17, 2015 at 11:34 AM, RCG <rkcgowda1...@gmail.com> 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 < > > >> stars...@mindspring.com> 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. > > >>> > > >>> > > >>
Re: NFS Client implementation query
Create a member with just the NFS stuff in it, and activate that with the set command. On my system, right or wrong, the STC ID has UID 0. _ Dave Jousma Assistant Vice President, Mainframe Engineering david.jou...@53.com 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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of RCG Sent: Thursday, September 17, 2015 12:20 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: NFS Client implementation query 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 = 0079, REASON CODE = 12030259 BPXF202I DOMAIN AF_INET WAS NOT ACTIVATED FOR FILE SYSTEM 866 TYPE INET. RETURN CODE = 0079, REASON CODE = 743A0259 BPXO015I THE SETOMVS COMMAND WAS SUCCESSFUL. = On Thu, Sep 17, 2015 at 12:02 PM, Lizette Koehler <stars...@mindspring.com> 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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of RCG > > Sent: Thursday, September 17, 2015 8:52 AM > > To: IBM-MAIN@LISTSERV.UA.EDU > > 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 <rkcgowda1...@gmail.com> 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 ASNAMEDESC STSTART/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 IOEFSCMZFS LOCAL A 2015/09/13 06.36.53 > > >HFS GFUAINIT LOCAL A 2015/09/13 06.36.52 > > > > > > PFS TYPE DOMAINMAXSOCK OPNSOCK HIGHUSED > > >INET AF_INET 6 2735 > > >UDS AF_UNIX 1 2030 > > > > > > 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= USER=OMVSKERN > > >POLICY=/etc/auto.master > > > > > > So can't see NFS here.. > > > > > > On Thu, Sep 17, 2015 at 11:34 AM, RCG <rkcgowda1...@gmail.com> 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
Re: NFS Client implementation query
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
david.jou...@53.com
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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of RCG
Sent: Thursday, September 17, 2015 11:11 AM
To: IBM-MAIN@LISTSERV.UA.EDU
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..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 volumescde 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
//*
//* IS TCP/IP DATA FILE
//* IS OS/390 NETWORK FILE SYSTEM CLIENT
//*TARGET LIBRARY
//* IS LANGUAGE ENVIRONMENT RUNTIME LIBRARY
//*
//SYSTCPD DD DISP=SHR,DSN=SYS3.OS.TCPIP.PROFILE.OS390R25(TCPDATA)
//STEPLIB DD DISP=SHR,DSN=
// 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=
//*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 <stars...@mindspring.com>
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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of RCG
> > Se
Re: NFS Client implementation query
Hi David, I think I need a restart of OMVS to refresh the PARMS ?
And unfortunately nothing written at LOG files perhaps because nothing
processed at all and just a start / end of the MVSNFSC task.
Regards,
On Thu, Sep 17, 2015 at 11:18 AM, Jousma, David <david.jou...@53.com> wrote:
> 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
> david.jou...@53.com
> 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:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of RCG
> Sent: Thursday, September 17, 2015 11:11 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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..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 volumescde 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
> //*
> //* IS TCP/IP DATA FILE
> //* IS OS/390 NETWORK FILE SYSTEM CLIENT
> //*TARGET LIBRARY
> //* IS LANGUAGE ENVIRONMENT RUNTIME LIBRARY
> //*
> //SYSTCPD DD DISP=SHR,DSN=SYS3.OS.TCPIP.PROFILE.OS390R25(TCPDATA)
> //STEPLIB DD DISP=SHR,DSN=
> // 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=
> //*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.M
Re: NFS Client implementation query
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:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of RCG
> Sent: Thursday, September 17, 2015 8:52 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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 <rkcgowda1...@gmail.com> 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 ASNAMEDESC STSTART/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 IOEFSCMZFS LOCAL A 2015/09/13 06.36.53
> >HFS GFUAINIT LOCAL A 2015/09/13 06.36.52
> >
> > PFS TYPE DOMAINMAXSOCK OPNSOCK HIGHUSED
> >INET AF_INET 6 2735
> >UDS AF_UNIX 1 2030
> >
> > 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= USER=OMVSKERN
> > POLICY=/etc/auto.master
> >
> > So can't see NFS here..
> >
> > On Thu, Sep 17, 2015 at 11:34 AM, RCG <rkcgowda1...@gmail.com> 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 <
> >> stars...@mindspring.com> 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:IBM-MAIN@LISTSERV.UA.EDU]
> >>> On
> >>> > Behalf Of RCG
> >>> > Sent: Thursday, September 17, 2015 8:11 AM
> >>> > To: IBM-MAIN@LISTSERV.UA.EDU
> >>> > 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..com)')
> >>> > ASNAME(MVSNFSC,'SUB=MSTR')
> >>> >
> >>> > Here is the JCL for started task MVSNFSC -
> >>> >
> >>> >
> ==
> >>> > ==
> >>> > ==
> >>> >
> >>> > //MVSNFSC PROC SYSNFS=SYS1
> >>> >
> //
Re: NFS Client implementation query
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.zos.v2r1.idan400/nfsconf.htm
Lizette
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of RCG
> Sent: Thursday, September 17, 2015 8:11 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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..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 volumescde 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
> //*
> //* IS TCP/IP DATA FILE
> //* IS OS/390 NETWORK FILE SYSTEM CLIENT
> //*TARGET LIBRARY
> //* IS LANGUAGE ENVIRONMENT RUNTIME LIBRARY
> //*
> //SYSTCPD DD DISP=SHR,DSN=SYS3.OS.TCPIP.PROFILE.OS390R25(TCPDATA)
> //STEPLIB DD DISP=SHR,DSN=
> // 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=
> //*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 <stars...@mindspring.com>
> wrote:
>
> > Could you provide the JCL you are using and any commands that JCL is
> > using? It might help clarify the issue. Ma
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 <rkcgowda1...@gmail.com> 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 ASNAMEDESC STSTART/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 IOEFSCMZFS LOCAL A 2015/09/13 06.36.53
>HFS GFUAINIT LOCAL A 2015/09/13 06.36.52
>
> PFS TYPE DOMAINMAXSOCK OPNSOCK HIGHUSED
>INET AF_INET 6 2735
>UDS AF_UNIX 1 2030
>
> 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= USER=OMVSKERN
>POLICY=/etc/auto.master
>
> So can't see NFS here..
>
> On Thu, Sep 17, 2015 at 11:34 AM, RCG <rkcgowda1...@gmail.com> 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 <
>> stars...@mindspring.com> 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.zos.v2r1.idan400/nfsconf.htm
>>>
>>>
>>> Lizette
>>>
>>>
>>> > -Original Message-
>>> > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
>>> On
>>> > Behalf Of RCG
>>> > Sent: Thursday, September 17, 2015 8:11 AM
>>> > To: IBM-MAIN@LISTSERV.UA.EDU
>>> > 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..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 volumescde 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=14
Re: NFS Client implementation query
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 <stars...@mindspring.com>
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.zos.v2r1.idan400/nfsconf.htm
>
>
> Lizette
>
>
> > -Original Message-
> > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> > Behalf Of RCG
> > Sent: Thursday, September 17, 2015 8:11 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > 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..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 volumescde 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
> > //*
> > //* IS TCP/IP DATA FILE
> > //* IS OS/390 NETWORK FILE SYSTEM CLIENT
> > //*TARGET LIBRARY
> > //* IS LANGUAGE ENVIRONMENT RUNTIME LIBRARY
> > //*
> > //SYSTCPD DD DISP=SHR,DSN=SYS3.OS.TCPIP.PROFILE.OS390R25(TCPDATA)
> > //STEPLIB DD DISP=SHR,DSN=
> > // 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=
> > //*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
Re: NFS Client implementation query
RCG wrote:
Thanks Lizette -
Here is the PARMS that I have used in BPXPRMxx -
FILESYSTYPE TYPE(NFS)
ENTRYPOINT(GFSCINIT)
PARM('biod(6),Bufhigh(128),nfsv4domain(xxx..com)')
ASNAME(MVSNFSC,'SUB=MSTR')
Are you just trying to mount a Unix dir from a Unix server onto OMVS or are you
trying to set up an Kerbero ssecure client?
If you do not intend the latter, apparently you don't have to do any of what
you are doing.
You just use the OMVS mount command instead.
--
Jack J. Woehr # Science is more than a body of knowledge. It's a way of
www.well.com/~jax # thinking, a way of skeptically interrogating the universe
www.softwoehr.com # with a fine understanding of human fallibility. - Carl Sagan
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS Client implementation query
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 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. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS Client implementation query
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:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of RCG > Sent: Thursday, September 17, 2015 7:43 AM > To: IBM-MAIN@LISTSERV.UA.EDU > 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 <allan.stal...@kbmg.com> > 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 > > > > > > 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. > > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
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..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 volumescde 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
//*
//* IS TCP/IP DATA FILE
//* IS OS/390 NETWORK FILE SYSTEM CLIENT
//*TARGET LIBRARY
//* IS LANGUAGE ENVIRONMENT RUNTIME LIBRARY
//*
//SYSTCPD DD DISP=SHR,DSN=SYS3.OS.TCPIP.PROFILE.OS390R25(TCPDATA)
//STEPLIB DD DISP=SHR,DSN=
// 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=
//*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 <stars...@mindspring.com>
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:IBM-MAIN@LISTSERV.UA.EDU] On
> > Behalf Of RCG
> > Sent: Thursday, September 17, 2015 7:43 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > 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 <allan.stal...@kbmg.com>
> > 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 F
Re: NFS Client implementation query
>>> On 9/16/2015 at 03:01 PM, RCG <rkcgowda1...@gmail.com> wrote: > Dear Listers, > > 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 ? It's been quite a long time since I worked with UNIX System Services, but I would think that you would only be starting an NFS _server_ process, not for a client. An NFS "client" would be the mount command to mount the exported file system into your HFS/ZFS. Mark Post -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
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 <allan.stal...@kbmg.com> 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 > > > 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. > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS Client implementation query
In article
NFS Client implementation query
Dear Listers, 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. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS Client implementation query
You mentioned client? Where's the server located ? On Wednesday, September 16, 2015, RCG <rkcgowda1...@gmail.com> wrote: > Dear Listers, > > 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. > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu <javascript:;> with the message: > INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
NFS mount of z/OS filesystem from Linux
Ø I searched the web and tried the command examples from the IBM manual but every variation failed. Two things: 1) You need to download and compile mountpw for your Linux system. The source code is supplied with z/OS. Mountpw associates a numeric uid with your z/OS userid, so that the NFS security works. Before you try the mount, run mountpw to establish a userid- uid mapping. 2) z/OS is NFS version 3. NFS4 is supposed to downgrade gracefully, but it's iffy with non-Unix implementations. Specify nfs3. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS mount problem between zOS and Linux
I was having some strange issues with my z/OS to linux system and had to
specify vers(3).
MOUNT FILESYSTEM(MYNFS) +
MOUNTPOINT('/mnt') +
parm('10.6.0.10:/srv/ftp/pub,vers(3)') +
TYPE(NFS) MODE(RDWR)
On Thu, Dec 26, 2013 at 3:40 PM, Mark Post mp...@suse.com wrote:
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
whereas you don't have the colon in it.
I don't know what the -o sec=sys does, so I can't comment on that.
In the past, you used to have to compile the mvslogin program to run on
the Linux system that would be doing the mount. That was so the External
Security Manager on z/OS (whether ACF2, RACF, or other) could authenticate
the subsequent request for the mount. I would think that _some_ sort of
authentication would still be needed today.
Mark Post
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
--
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions
Mark D Pace
Senior Systems Engineer
Mainline Information Systems
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
NFS mount problem between zOS and Linux
Hi all First of all a happy good year. I can not mount a zOS NFS directory from my Linux machine. I searched the web and tried the command examples from the IBM manual but every variation failed. From the Linux machine I can do a showattr of the zOS server if I only supply the zOS host name. The last attempt was the Linux command: mount -t nfs4 -o sec=sys proto=tcp Catweazle-zOS/jedsp /jedsp where Catweazle-zOS is the zOS host name and jedsp are directories on both systems. The EXPORTS file contains: /hfs/jedsp JEdSP Any help would be greatly appreciated. Thanks, j@n -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS mount problem between zOS and Linux
On Thu, 26 Dec 2013 15:26:26 +0100, jan de decker jan.je...@gmail.com wrote: Hi all First of all a happy good year. I can not mount a zOS NFS directory from my Linux machine. I searched the web and tried the command examples from the IBM manual but every variation failed. From the Linux machine I can do a showattr of the zOS server if I only supply the zOS host name. The last attempt was the Linux command: mount -t nfs4 -o sec=sys proto=tcp Catweazle-zOS/jedsp /jedsp where Catweazle-zOS is the zOS host name and jedsp are directories on both systems. The EXPORTS file contains: /hfs/jedsp JEdSP What error messages are you getting? Is /jedsp really in the root? What other parms if any are in your export for /hfs/jedsp? Is JEdSP the HLQ of a classic MVS data set? Why the d in lower case (although I doubt that would matter, but I've never checking into nor used lower case in exporting MVS data sets). -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS ITIL v3 Foundation Certified mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://search390.techtarget.com/ateExperts/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
NFS mount problem between zOS and Linux
Hi all, Thanks Mark for your quick reply. The message after the mount command is the mount help information. JEDSP is a MVS FLQ I changed the EXPORTS dsn to include /hfs/jedsp/web WEB and removed the old jedsp entries. but to avail. I am running Ubuntu 12.04 kernel 3.2.0.57 Can somebody help? I think there is an error in the mount command. Thanks, j@n -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS mount problem between zOS and Linux
On Thu, 26 Dec 2013 18:17:29 +0100, jan de decker jan.je...@gmail.com wrote: Hi all, Thanks Mark for your quick reply. The message after the mount command is the mount help information. JEDSP is a MVS FLQ I changed the EXPORTS dsn to include /hfs/jedsp/web WEB and removed the old jedsp entries. but to avail. I am running Ubuntu 12.04 kernel 3.2.0.57 Can somebody help? I think there is an error in the mount command. Thanks, You didn't answer the question about the dir you are trying to export. Is it in the root file system on z/OS? Is the path actually /jedsp or /jedsp/web or something else (like /u/jedsp)? I'm asking because it would be bad practice to create a path / dir in your z/OS root or even sysplex root as opposed to having some other standard / path where you install z/OS unix software. But I see it often anyway. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS ITIL v3 Foundation Certified mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://search390.techtarget.com/ateExperts/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: NFS mount problem between zOS and Linux
Please check your MVS syslog... you should have error messages (especially if your mount command is wrong) that should give you an idea of what the problem is. I missed your initial post ... please also repost your mount command ... Kind Regards. Jim Thomas -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of jan de decker Sent: Thursday, December 26, 2013 11:17 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: NFS mount problem between zOS and Linux Hi all, Thanks Mark for your quick reply. The message after the mount command is the mount help information. JEDSP is a MVS FLQ I changed the EXPORTS dsn to include /hfs/jedsp/web WEB and removed the old jedsp entries. but to avail. I am running Ubuntu 12.04 kernel 3.2.0.57 Can somebody help? I think there is an error in the mount command. Thanks, j@n -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
NFS mount problem between zOS and Linux
Hi all, Mark, I agree that maybe it is a bad practice to touch the root system but in my case the zOS has a /jedsp/web directory because I did not want the pollute the default install directories Underneath /jedsp/web there are directories for pub, cgi, css images. The zOS HTTP server has no problem to find /jedsp/web/pub/index.html Can you or somebody else from the list help? Thanks, j@n -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
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 messages in the zOS log nor in the NFSS STC Hope somebody can help. Thanks j@n -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
