Authorizing the IBM Z OMEGAMON AI for Network Monitor started tasks for TCP/IP privileges

Use this information to define a TCP/IP OMVS segment for the user ID associated with units of work requesting these UNIX™ System Services.

About this task

The IBM® Z OMEGAMON Network Monitor TCP/IP data collector uses TCP/IP service components in z/OS® Communications Server that exploit z/OS UNIX System Services. Using these components requires a UNIX System Services security construct, called an OMVS segment, for the user ID associated with units of work requesting these services.

The OMVS segment must be defined with SuperUser authority. [Note that a userid defined with SuperUser authority is not the same as UID(0).] Authorize the IBM Z OMEGAMON Network Monitor started task for TCP/IP privileges by creating an OMVS segment for RACF® or another SAF product. Identify the IBM Z OMEGAMON Network Monitor started task IBMN3 as a superuser, as in this example:

ALU IBMN3 OMVS(UID(0) HOME(/) PROGRAM(/bin/sh))

See the z/OS Communications Server IP Planning and Migration Guide for an explanation of how to provide an OMVS segment for the IBM Z OMEGAMON Network Monitor started task.

Note: This command makes setting of SuperUser authority more explicit. This action has actually already taken place when you ran the JCL job described in Defining monitoring agent access to the network management interfaces and commands.

If you recently migrated to z/OS v2.1, you might find OMVS errors in the system log when you launch the IBM Z OMEGAMON Network Monitor monitoring agent. Be aware that as of z/OS V2R1, the ability to use default OMVS segments has been removed. All z/OS UNIX users or groups must now have OMVS segments defined for user and group profiles with unique user IDs (UIDs) and group IDs (GIDs). For more information about this error and workarounds, see OMVS and SNAMGMT errors found in system log on z/OS v2.1 systems in the IBM Z OMEGAMON Network Monitor: Troubleshooting Guide.