> -----Original Message-----
> From: IBM Mainframe Discussion List
> [mailto:[EMAIL PROTECTED] On Behalf Of Crispin Hugo
> Sent: Wednesday, July 18, 2007 2:25 PM
> To: [email protected]
> Subject: z/OS NFS Client to Linux NFS
>
>
> I have been asked to set up z/OS NFS client to access Linux
> files on Redhat.
> I have searched the archives and found little information.
> Documentation on
> z/OS client is very sparse.
> Any pointers/problems/gotchas etc I should be aware of. The
> requirement is
> to have 100 plus user accessing 50 or so folders on Linux to
> update files on
> Linux system/s.
>
> Crispin Hugo
> Systems Programmer, Macro 4
> <http://www.macro4.com/>
Lucky you! I have this working myself. Use the z/OS 1.6 NFS client to
mount a Linux Fedora Core 6 subdirectory.
I don't always have the mounts active, so I don't have them in the
BPXPRMxx member of parmlib. What I do have in BPXPRMxx is:
FILESYSTYPE TYPE(NFS) /* Filesystem type NFS */
ENTRYPOINT(GFSCINIT) /* Entrypoint for defining NFS */
ASNAME(GFSCPROC) /* STC Procedure Name */
PARM(' ') /* Null PARM for physical file */
/* system */
It goes in the same member as the other FILESYSTYPE entries. This sets
up to allow both the NFS client and NFS server. I then customized the
NFS client JCL, which resides in SYS1.NFSSAMP, member GFSCPROC. Once you
have the GFSCPROC running, and the Linux system is up and has done the
"exportfs" command necessary, then you can run a job:
//STEP010 EXEC PGM=IKJEFT01,
// REGION=4096K,
// DYNAMNBR=40
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
MOUNT FILESYSTEM('SERVER1.ASCII') +
MOUNTPOINT('/nfs-ascii/server1') +
PARM('10.143.26.125:/nfs/LIH1,xlat(Y)') +
TYPE(NFS) +
MODE(RDWR)
MOUNT FILESYSTEM('SERVER1.BINARY') +
MOUNTPOINT('/nfs-binary/server1') +
PARM('10.143.26.125:/nfs/LIH1,xlat(N)') +
TYPE(NFS) +
MODE(RDWR)
/*
The both MOUNT commands mount the same mountpoint on the Linux server.
The difference is the "xlat(.)" parameter. In the first MOUNT command, I
tell the z/OS NFS client to automatically translate to/from
EBCDIC/ASCII. The z/OS mountpoint is "/nfs-ascii/server1". It mounts the
"/nfs/LIH1" subdirectory on the Linux system.
In the second MOUNT command, I tell the z/OS NFS client to just transfer
the bytes with no translation. The z/OS mountpoint is
"/nfs-ascii/server1". It mounts the very same "/nfs/LIH1" subdirectory
as the first.
The 10.143.25.125 is the IP address of my Linux server. If you have DNS
working correctly, you can use the DNS name instead. The names in the
FILESYSTEM('...') just don't matter. They just need to be unique. They
don't reference a dataset name or anything else. They are simply "place
holders".
On my Linux system, my /etc/exports looks like:
/ 10.170.30.0/24 (ro,sync,root_squash,insecure)
/nfs/LIH1 10.170.30.0/24 (rw,sync,root_squash,insecure)
I had to include the root for some reason, so I made it read-only in the
export. And I'm too lazy to figure out why the mount would not work
without it. Likely a mistake on my part, somewhere.
--
John McKown
Senior Systems Programmer
HealthMarkets
Keeping the Promise of Affordable Coverage
Administrative Services Group
Information Technology
The information contained in this e-mail message may be privileged
and/or confidential. It is for intended addressee(s) only. If you are
not the intended recipient, you are hereby notified that any disclosure,
reproduction, distribution or other use of this communication is
strictly prohibited and could, in certain circumstances, be a criminal
offense. If you have received this e-mail in error, please notify the
sender by reply and delete this message without copying or disclosing
it.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
