Installing the client enabling commands

This section describes the tasks you must perform to install and port the client enabling commands. These tasks include retrieving commands for AIX and Sun Solaris. This section also includes information about porting the mvslogin, mvslogout, and showattr commands and dealing with different compilers and operating systems.

To enable client users to access the z/OS system and to display system attributes, you must install the mvslogin, mvslogout, and showattr commands on the client workstations. For some client machines, you might need to modify the code to port these commands so they run on your client machine. See Porting the mvslogin, mvslogout, and showattr commands. Before you install the commands, make sure that TCP/IP and File Transfer Protocol (FTP) are running both on z/OS and on the client.

Note: The z/OS NFS client utilities, including mvslogin, mvslogout, and showattr, are installed when the z/OS NFS client and TCP/IP are installed. The target library NFSCUTIL is a DDDEF to an existing z/OS UNIX directory (/usr/lpp/NFS/IBM) and will contain the client commands for the z/OS NFS client after installation. There is no need to port the z/OS NFS client utilities as you would for the remote NFS clients which use the z/OS NFS server.

Follow these installation procedures:

Delete any previous versions of the mvslogin, showattr, and mvslogout commands and their source code from your client workstation.
Retrieve the mvslogin, mvslogout, and showattr commands (in tarbin file format for AIX® or UNIX, or in source code format for any other platform) from the prefix.NFSTARB data set, where prefix is an installation-specified variable. Use FTP with a binary transfer to send the tarbin or executable files to a client workstation for UNIX or AIX (no character conversion should be made). Use FTP with text transfer to send the source code of the three commands to a client workstation for any platform.
Use the tar utility to extract the files only if the client uses AIX or UNIX.
Compile the source code only if it is not in executable code format. (You might need to modify the code for your specific client machine.)
Make executable code versions of the commands available to all clients.

Recommendation: We recommend placing these commands on a LAN server (possibly in /usr/local/bin) that is available to many workstations, rather than installing them on each client workstation.

Table 1 is a list of all files stored in prefix.NFSTARB data set related to the server's client commands (mvslogin, mvslogout, and showattr):

Table 1. Files in the prefix.NFSTARB data set to download to clients
File Name	Download as:	Description	Client Environment
prefix.NFSTARB(GFSAWAIX)	client.tarbin (or any name)	Binary file	AIX, UNIX
Source Code for Commands
prefix.NFSTARB(GFSAWMNT)	gfsawmnt.h	C header files	All ¹
prefix.NFSTARB(GFSAWSHO)	gfsawsho.h
prefix.NFSTARB(GFSAWRP6)	gfsawrp6.h
prefix.NFSTARB(GFSAWRS6)	gfsawrs6.h
prefix.NFSTARB(GFSAWAXD)	gfsawaxd.c	C modules	All ¹
prefix.NFSTARB(GFSAWLIN)	gfsawlin.c
prefix.NFSTARB(GFSAWLOU)	gfsawlou.c
prefix.NFSTARB(GFSAWMOU)	gfsawmou.c
prefix.NFSTARB(GFSAWSHA)	gfsawsha.c
prefix.NFSTARB(GFSAWJCL)	makefile	All ¹
Note: For AIX or UNIX, you do not need to download every individual file if you download the GFSAWAIX file.

The following sample client screens show how to retrieve and create the mvslogin, mvslogout, and showattr client commands for the following platforms.

AIX, Sun Solaris, and Linux; see page Retrieving commands for AIX, Sun Solaris, and Linux.

Retrieval of source code for client enabling commands shows how to retrieve the necessary source code to install the client commands on any platform except for an AIX or UNIX workstation.