The enhanced 3270 user interface address space uses the z/OS UNIX API for TCP/IP
communications, so the user ID associated with the address space must be defined to your security
product as a z/OS UNIX user. If this user ID is not already defined, you should define it
now.
About this task
The user ID for the address space must be defined using the security authorization
facility (RACF, for example) to contain what is known as an OMVS Segment. As part of defining the
OMVS Segment for the user ID, you must also supply a z/OS UNIX UID. The UID you supply does not need
to have superuser authority (that is, UID=0 is not required). The following is an example of a RACF
ADDUSER command that defines an OMVS Segment and a UID for a new RACF user ID:
ADDUSER userid ... OMVS(UID(nnn) ...)