Porting the mvslogin, mvslogout, and showattr commands

The z/OS NFS server supports any client machine that has an NFS client software package implemented according to the Sun NFS protocol. See Tested clients for the z/OS NFS server for a list of supported platforms.

Note: NFS supports the authentication procedures of PCNFSD Version 1 and Version 2 protocols. If a PC client supports PCNFSD and keeps the UID and GID to each mount point base, you do not need to port the mvslogin command. See PCNFSD protocol for details on PCNFSD support.

To port the mvslogin, mvslogout, and showattr commands successfully, you should understand the following:

C language - The source code for these commands is written in C.
System calls for your client machine's operating system - For example, the FAT file system under DOS only allows up to eight characters for file names, and up to three characters for file name extensions. AIX and UNIX do not have this restriction. Therefore, while mvslogout is a valid file name in an AIX or UNIX environment, it is too long to be a valid file name in a FAT file system under DOS.
As another example, the way that you get mount information varies for different platforms. The mount command is in the following (or similar) format:
```
mount <server>:<remote file system> <local mount point>    
```
The minimum information for porting the client enabling commands is:
1. Server name
2. Remote file system (high-level qualifier)
3. Local Mount point
4. UID and GID
The system calls to get the information for porting the client enabling commands are platform-dependent. If you cannot find the information in the following types of documents for the platform, you must call the support telephone number for the platform and ask to speak with their NFS development department:
- Operating system development toolkit
- TCP/IP development toolkit
- NFS development toolkit
The source code for mvslogin, mvslogout, and showattr.
For example, mvslogin tells the server the z/OS user id and its associated client UID number. This client UID number is expected to be passed to the server for all further client requests to the NFS. If the client user does not specify the z/OS user id and password on the mvslogin command, the z/OS login ID is taken from the login ID on the workstation with no password assumed. If authentication for this default login ID from the workstation fails, then mvslogin prompts the user to enter the z/OS login password.

Figure 1 shows the common source files for the mvslogin, mvslogout, and showattr commands on all platforms:

Figure 1. Common source files

Seven .c files

gfsawaxd.c: XDR encode and decode routines for attributes service.
gfsawclt.c: NFS protocol calls for mvslogin and mvslogout.
gfsawlin.c: Main program to generate mvslogin command.
gfsawlou.c: Main program to generate mvslogout command.
gfsawmcl.c: Create the client handle and initialize it.
gfsawmou.c: XDR protocol definitions for mvslogin and mvslogout.
gfsawsha.c: Main program to generate showattr command mvslogout.

Four .h files

gfsawmnt.h: Protocol definitions for mvslogin and mvslogout.
gfsawsho.h: Attribute definition and procedures.
gfsawrp6.h: IPv6 RPC library definitions.
gfsawrs6.h: IPv6 RPC support functions.

One makefile