Authorization requirements

This topic describes the requirements for security products, for dispatching priorities, and for VTAM Applids.

RACF requirements

A security product like Resource Access Control Facility (RACF) is required for the OS/390 eNetwork Communications Server version 2.5 (or later) Internet Protocol (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 such user. The UID and the GID are defined through the OMVS segment, in the RACF profile, and in the RACF group profile.

For more information about RACF, see the IBM IP Planning and Migration Guide.

Dispatching priority

When initialization is complete, ULTRAOPT executes most of its code under each optimized application’s address space, using that address space’s dispatching priority. However, the Monitor component is run partially under the TSO user’s address space and partially under the ULTRAOPT address space. BMC recommends setting the ULTRAOPT dispatching priority to be the same as the VTAM dispatching authority. In addition, BMC also recommends setting the dispatching priority of the VTAM applications lower than that of VTAM.

VTAM Applids

To optimize an application’s data streams, you must specify the application ID (Applid) on the appropriate Monitor panel. The Applid for each application is in a member of SYS1.VTAMLST. The member is referred to as the application’s major node. SYS1.VTAMLST is the default name for this data set. You might need to ask your VTAM system programmer for the name of this data set and each application’s major node name at your data center. In each member, search for a statement of the following form:

label is the Applid. This statement, known as the application’s Applid, defines a minor node. There might be more than one per major node, depending on how your system is configured.