SYSIBM.LUNAMES columns

The SYSIBM.LUNAMES table is used only for requests that use SNA protocols.

Begin general-use programming interface information.
LUNAME CHAR(8)
The LUNAME of the remote system. A blank value identifies a default row that serves requests from any system that is not specifically listed elsewhere in the column.
SECURITY_IN CHAR(1)
The acceptance option for a remote request from the corresponding LUNAME:
V
The option is verify. An incoming request must include one of the following authentication entities:
  • User ID and password
  • User ID and RACF® PassTicket
  • User ID and RACF encrypted password (not recommended)
  • Kerberos security tickets
  • User ID and DRDA encrypted password
  • User ID, password, and new password
  • User ID and encrypted password, or encrypted user ID and encrypted password
A
The option is already verified. This is the default. With A, a request does not need an authentication token, although the token is checked if it is sent.
With this option, an incoming connection request is accepted if it includes any of the following authentication tokens:
  • User ID only
  • All authentication methods that option V supports

If the USERNAMES column of SYSIBM.LUNAMES contains I or B, RACF is not invoked to validate incoming connection requests that contain only a user ID.

ENCRYPTPSWDS CHAR(1)
This column only applies to Db2 for z/OS® or Db2 for z/OS partners when passwords are used as authentication tokens. It indicates whether passwords received from and sent to the corresponding LUNAME are encrypted:
Y
Yes, passwords are encrypted. For outbound requests, the encrypted password is extracted from RACF and sent to the server. For inbound requests, the password is treated as if it is encrypted.
N
No, passwords are not encrypted. This is the default; any character other than Y is treated as N. Specify N for CONNECT statements that contain a USER parameter.

Recommendation: When you connect to a Db2 for z/OS partner that is at Version 5 or a subsequent release, use RACF PassTickets (SECURITY_OUT='R') instead of using passwords.

USERNAMES CHAR(1)
This column indicates whether an ID accompanying a remote request, sent from or to the corresponding LUNAME, is subject to translation and come from checking. When you specify I, O, or B, use the SYSIBM.USERNAMES table to perform the translation.
I
An inbound ID is subject to translation.
O
An outbound ID, sent to the corresponding LUNAME, is subject to translation.
B
Both inbound and outbound IDs are subject to translation.
blank
No IDs are translated.
End general-use programming interface information.