IBM Tivoli NetView for z/OS, Version 6.2

Defining the UNIX Command Server

To enable the running of UNIX for z/OS® commands from the NetView® program, a dedicated PPI receiver (CNMEUNIX) is needed to receive commands and data from the NetView program. A server process running in a UNIX for z/OS address space waits on this PPI receiver for incoming commands and data.

CNMEUNIX runs as a UNIX for z/OS kernel process. The UNIX command server consists of three parts that must be installed in the UNIX hierarchical file system (HFS). The default directory into which the installation installs the parts is <PathPrefix>/usr/lpp/netview/v6r2/bin.

Setting a region size for the UNIX command server of 0MB allows the UNIX command server to access all available memory. System-defined installation exits might limit this amount. If you receive an out-of-memory condition for the UNIX command server address space, adjust the installation exit values.

If the UNIX command server is started as a submitted job, ensure that the CNMSJUNX sample job is contained in a DSIPARM data set. If the UNIX command server is started as a started task, ensure that the CNMSSUNX sample job is copied into a data set defined in the IEFJOBS or IEFPDSI concatenation of master JCL, for example, SYS1.PROCLIB. This is required because CNMSSUNX contains a job statement. Also ensure that the sample z/OS START command CNMSUNXS is contained in a DSIPARM data set. For more information about specifying whether the UNIX command server runs as a submitted job or as a started task, see the online help for the DEFAULTS STRTSERV command.

Before you start a UNIX command server, you can customize the samples that are provided with the NetView program to fit your environment. If the SCNMLNKN data set is not defined as part of the LNKLST concatenation, you must include a STEPLIB DD statement for it in the UNIX command server JCL. When a START UNIXSERV command is issued, the NetView program issues an MVS™ START command (if DEFAULTS STRTSERV is set to STRTPROC) or submits a job (if DEFAULTS STRTSERV is set to SBMTJOB). For a started task, member CNMSUNXS contains the MVS START command that is used to start the procedure or job specified in the START UNIXSERV command. For a submitted job, the member specified on the MEM keyword in the START UNIXSERV command is submitted as an MVS job.

Member CNMSUNXS or the member containing the submitted JCL, for example, CNMSJUNX, can contain specific variables for which the NetView program performs substitutions before the task is started or the job is submitted. These variables have names that begin with an ampersand (&) followed by lowercase letters and end with a period (.). You can specify any of these substitution variables to customize how your UNIX command server is started. The following list describes these variables:

&sprcnm.

The member name containing the JCL that is to be started or submitted. This value is the value of the MEM keyword on the START UNIXSERV command

For a started task, if MEM is not specified, CNMSSUNX is used. This variable is specified in sample CNMSUNXS as the procedure or job to start.
For a submitted job, if MEM is not specified, CNMSJUNX is used. This variable is not specified in sample CNMSJUNX because it is the same as the sample name.

&jobname.

The name to be used on the JOB statement on a submitted job. This value is always set to CNMEUNIX.

For a started task, this variable is not specified in sample CNMSUNXS because it does not apply to the MVS START command.
For a submitted job, this variable is not specified in sample CNMSJUNX because the name is always set to CNMEUNIX.

&userid.

The TSO user ID under whose authority the started task or submitted job runs. To easily identify which user ID the task or job is running for, the JOBNAME (for start) or the step name (for submit) specifies this name. The value is always set to CNMEUNIX.

For a started task, this variable is specified in sample CNMSUNXS as the value for the JOBNAME keyword on the MVS START command.
For a submitted job, this variable is not specified in sample CNMSJUNX.

&ppiname.

The receiver name used for communication between the server and the NetView program across the PPI. The value is always set to CNMEUNIX.

For a started task, this variable is not specified in sample CNMSUNXS because the PPI name is always CNMEUNIX.
For a submitted job, this variable is not specified in sample CNMSJUNX because the PPI name is always CNMEUNIX.

If your installation is a RACF® controlled environment, there are additional RACF requirements. For more information, see the IBM Tivoli NetView for z/OS Security Reference.

Feedback