General OMVS segment requirements
The first table in this topic lists the OMVS segment requirements sorted by product or component name.
OMVS segment requirements by address space figure lists the OMVS segment requirements sorted by the type of address space.
OMVS segment requirements by product or component
Product or component | Runs in this type of address space | OMVS segment required? | Notes |
|---|---|---|---|
BMC Discovery for z/OS | PAS | Yes | Superuser authority is required; use either UID 0 or BPX.SUPERUSER. |
CMF MONITOR | z/OS PAS | Maybe | If CMFCPM xx or CMFIPM xx includes the OMVS extractor statement, to run this control statement, the user ID under which the Extractor is running must be designated as a valid OMVS user ID. You can use the security system facilities for your system to define the user ID to OMVS. If using TCP/IP for CAS communications, an OMVS segment is required. |
MainView AutoOPERATOR | BBI-SS PAS | Maybe | You need to define an OMVS segment for your PAS when one of the following conditions is true:
|
MainView Explorer | PAS | Yes | None |
MainView for CICS | BBI-SS PAS | Maybe | If using TCP/IP for CAS communications, an OMVS segment is required. |
MainView for DB2 | BBI-SS PAS | Yes | An OMVS segment is required. |
MainView for DBCTL | BBI-SS PAS | Maybe | If using TCP/IP for CAS communications, an OMVS segment is required. |
MainView for IMS Online | BBI-SS PAS | Maybe | If using TCP/IP for CAS communications, an OMVS segment is required. |
MainView for IP | PAS | Yes | A security product like Resource Access Control Facility (RACF) is required for the OS/390 eNetwork Communications Server version 2.5 (or newer) IP environment. Each unit of work in the system that requires UNIX System Services must be associated with a UNIX System Services identity. A valid identity refers to the presence of a valid UNIX user ID (UID), a valid UNIX group ID (GID), and a valid HOME directory for the user. The UID and the GID are defined through the OMVS segment, in the RACF profile, and in the RACF group profile. If the started task is not defined to a user ID that has a defined OMVS segment, error messages might be issued. If the HOME directory is not specified for the user ID, the socket call might fail. |
MainView for Java Environments | z/OS PAS | Yes | Superuser authority is required. Assign one of the following privileges:
|
MainView for Linux - Servers | PAS | Yes | None |
MainView for Unix System Services | z/OS PAS | Yes | Superuser authority is required. Assign UID=0 or a user ID authorized to read access to RACF class resource BPX.SUPERUSER. |
MainView for VTAM | PAS | Yes | None |
MainView for WebSphere Application Server | PAS | Yes | None |
MainView for MQ | BBI-SS PAS | Yes | None |
MainView for z/OS | z/OS PAS | Maybe | If using TCP/IP for CAS communications, an OMVS segment is required. |
MainView Infrastructure | CAS | Yes | CAS-to-CAS communication using TCP/IP needs an OMVS segment. MainView Alarm Management version 5.0 or newer needs an OMVS segment. |
MainView SRM | PAS | Maybe | The MainView SRM Started Task (SVOS) requires an OMVS segment and UNIX superuser authority for the line command HFU. If your site uses HFS file systems, verify that a UID of 0 (superuser authority) is assigned in the UID parameter in the OMVS segment of the ADDUSER or ALTUSER commands in the RACF profile. If using TCP/IP for CAS communications, an OMVS segment is required. |
MainView SYSPROG Services | z/OS PAS | Maybe | If using TCP/IP for CAS communications, an OMVS segment is required. |
MainView Transaction Analyzer | PAS | Maybe | If using TCP/IP for CAS communications, an OMVS segment is required. |
BMC Runtime Component System (RTCS) | RTCS subsystem STC | No | None |
RTCSRTCS | RTCS initiator STC | No | None |
TSO user | UAS | Maybe | If TCP/IP is being used for CAS-to-CAS communication, the TSO user's address space (UAS) will need an OMVS segment. If default OMVS segments are defined for a system, TCP/IP access does not need OMVS segments to be explicitly defined for the user ID. |
OMVS segment requirements by address space
Product or component | Runs in this type of address space | OMVS segment required? | Notes |
|---|---|---|---|
MainView AutoOPERATOR | BBI-SS PAS | Maybe | You need to define an OMVS segment for your PAS when one of the following conditions is true:
|
MainView for CICS | BBI-SS PAS | Maybe | If using TCP/IP for CAS communications, an OMVS segment is required. |
MainView for DB2 | BBI-SS PAS | Maybe | If using TCP/IP for CAS communications, an OMVS segment is required. |
MainView for DBCTL | BBI-SS PAS | Maybe | If using TCP/IP for CAS communications, an OMVS segment is required. |
MainView for IMS Online | BBI-SS PAS | Maybe | If using TCP/IP for CAS communications, an OMVS segment is required. |
MainView for MQ | BBI-SS PAS | Yes | None |
MainView Infrastructure | CAS | Yes | CAS-to-CAS communication using TCP/IP needs an OMVS segment. MainView Alarm Management version 5.0 or newer needs an OMVS segment. |
CMF MONITOR | z/OS PAS | Maybe | If CMFCPMxx or CMFIPMxx includes the OMVS extractor statement, to run this control statement, the user ID under which the Extractor is running must be designated as a valid OMVS user ID. You can use the security system facilities for your system to define the user ID to OMVS. If using TCP/IP for CAS communications, an OMVS segment is required. |
MainView for Unix System Services | z/OS PAS | Yes | Superuser authority is required. Assign UID=0 or a user ID authorized to read access to RACF class resource BPX.SUPERUSER. |
MainView for z/OS | z/OS PAS | Maybe | If using TCP/IP for CAS communications, an OMVS segment is required. |
MainView SYSPROG Services | z/OS PAS | Maybe | If using TCP/IP for CAS communications, an OMVS segment is required. |
BMC Discovery for z/OS | PAS | Yes | Superuser authority is required; use either UID 0 or BPX.SUPERUSER. |
MainView Explorer | PAS | Yes | None |
MainView for IP | PAS | Yes | A security product like Resource Access Control Facility (RACF) is required for the OS/390 eNetwork Communications Server version 2.5 (or newer) IP environment. Each unit of work in the system that requires UNIX System Services must be associated with a UNIX System Services identity. A valid identity refers to the presence of a valid UNIX user ID (UID), a valid UNIX group ID (GID), and a valid HOME directory for the user. The UID and the GID are defined through the OMVS segment, in the RACF profile, and in the RACF group profile. If the started task is not defined to a user ID that has a defined OMVS segment, error messages might be issued. If the HOME directory is not specified for the user ID, the socket call might fail. |
MainView for Java Environments | z/OS PAS | Yes | Superuser authority is required. Assign one of the following privileges:
|
MainView for Linux - Servers | PAS | Yes | None |
MainView for VTAM | PAS | Yes | None |
MainView for WebSphere Application Server | PAS | Yes | None |
MainView SRM | PAS | Maybe | The MainView SRM Started Task (SVOS) requires an OMVS segment and UNIX superuser authority for the line command HFU. If your site uses HFS file systems, verify that a UID of 0 (superuser authority) is assigned in the UID parameter in the OMVS segment of the ADDUSER or ALTUSER commands in the RACF profile. For additional information, see Customizing-after-installation. If using TCP/IP for CAS communications, an OMVS segment is required. |
MainView Transaction Analyzer | PAS | Maybe | If using TCP/IP for CAS communications, an OMVS segment is required. |
RTCS | RTCS initiator STC | No | None |
RTCS | RTCS subsystem STC | No | None |
TSO user | UAS | Maybe | If TCP/IP is being used for CAS-to-CAS communication, the TSO user address space (UAS) will need an OMVS segment. If default OMVS segments are defined for a system, TCP/IP access does not need OMVS segments to be explicitly defined for the user ID. |
Related topicS