The following paragraphs describe and illustrate how the system determines the validity of an access request from a remote host.

Requests from a User at a Remote Host

When a user at a remote host requests access to the local host through a distributed systems service, the system searches the USERDATAFILE for entries enabling the requesting <usercode>/<host name> combination to access the local host.

When a “matching” entry is found, the search terminates and the user is granted access to the local host. If the entry contains a local-alias usercode, that usercode is used to identify the user; otherwise, the requesting remote usercode is used.

See Managing Usercodes for Remote Users for a discussion of how the system evaluates an incoming transfer request for access to the local system and how it then searches the USERDATAFILE for applicable REMOTEUSER entries.

Example

As an example, consider a host in a network where the following <remoteuser add> statements are used to create REMOTEUSER entries in the USERDATAFILE:

+RU SALES OF BRONX, WALLSTREET;

+RU SALES OF *ANYHOST LOCALALIAS = OTHERSALES;

+RU *ANYUSER OF BRONX, WALLSTREET;

+RU *ANYUSER OF *ANYHOST LOCALALIAS = OTHERUSER;

+RU *NOUSERCODE OF NEWYORK LOCALALIAS = BIGAPPLE;

The following table shows which usercodes are used for local identification when requests are received from remote users at various hosts in the network.