Communications Server for z/OS V1R7 TCP/IP Implementation, Volume 1: Base Functions, Connectivity, and Routing

66 Communications Server for z/OS V1R7 TCP/IP Implementation, Volume 1 - Base Functions, Connectivity, and Routing

Figure 3-4 Command not found error

In this case you must preface the command with the directory path necessary to locate it:

/usr/lpp/tcpip/bin/oping

If you experience such a problem, check that the symbolic links are correct. Part of the

installation is to run the UNIX MKDIR program to set up the symbolic links for the various

commands and programs from their real path to /bin or /usr/sbin, where they can be found

using the default search path.

3.5 Verification checklist

The following checklist will help ensure that all z/OS and USS related setup tasks have been

completed for the base functions:

1. Have TNF and VMCF initialized successfully?

Check the console log for a successful start of EZAZSSI, TNF, VMCF.

2. Has the TCP/IP feature of z/OS been enabled or registered in IFAPRDxx?

3. Has a

full-function OMVS (DFSMS, RACF, zFS) started successfully?

– Is OMVS active when you issue D OMVS?

– Is SMS active when you issue D SMS?

– Have z/OS UNIX file systems been mounted? Verify with D OMVS,F.

– Is RACF enabled on the system?

4. Have the definitions in BPXPRMxx of SYS1.PARMLIB been made to reflect:

– The correct stack for the stack or stacks you will be running?

– The support for dual-mode is defined to support IPv4 and IPv6 (AF_INET and

AF_INET6)?

– The correct CS for z/OS IP proc names?

– The correct use of INET versus CINET?

– The correct ENTRYPOINT name for z/OS Communications Server IP versus earlier

versions of OE function in TCP/IP (z/OS IP ENTRYPOINT = EZBPFINI)?

– The mounting of file systems for users? (You can verify with D OMVS,F.)

– Appropriate values for MAXPROCSYS, MAXPROCUSER, MAXUIDS,

MAXFILEPROC, MAXPTYS, MAXTHREADTASKS, and MAXTHREADS?

5. Have z/OS UNIX file systems and directories been created and mounted for the users of

the system?

6. Have RACF definitions been put in place? For example:

– OMVS user IDs and group IDs for your CS for z/OS IP procedures

– OMVS user IDs and group IDs for your other users, for superusers, for a default user,

with definitions for appropriate Facility classes, like BPX.SUPERUSER

–TCP/IP VARY commands

BROWSE -- /tmp/cs01

Command ===>

********************************* Top of Data ***

oping: FSUM7351 not found

******************************** Bottom of Data *