00D3103C

Explanation

An attempt was made to allocate an SNA (LU 6.2) conversation, but the authentication request failed because the specified remote partner LUNAME will not allow authentication based on a user ID alone. The remote partner LUNAME is configured to require authentication using a user ID and corresponding password.

A password must be provided through Db2 application logic or through Db2 Communications Database (CDB) definitions. Alternately, the partner LUNAME can be configured to allow authentication based on user ID alone. For example, specify LU 6.2 SECURITY=SAME or Already-Verified.

System action

The attempt to allocate an LU6.2 conversation fails, and the error is reported to the Db2 application that requested access to the distributed resource.

System programmer response

If the remote LUNAME configuration can be changed, change it to allow Already Verified (Security=Same) authentication, which does not require a password. If the target LUNAME is a Db2 for z/OS® system, support is declared by specifying SECACPT=ALREADYV on the Db2 VTAM® APPL statement.

If remote LUNAME configuration changes are not appropriate, or if a higher level of security is required, then the local Db2 for z/OS system must honor the requirements of the remote LUNAME and provide a password. It might be possible to make application changes to provide a password. If application changes are not possible, CDB changes will be required.

If the local application is DRDA related, and if it is executing an explicit SQL CONNECT statement to connect to the remote system, consider changing the application to provide a password on the SQL CONNECT statement as follows: 

CONNECT TO server USING userid USING password

In the following circumstances, Db2 Communications Database tables must be changed to provide a password:

  • The local application cannot be modified to provide a password on its SQL CONNECT statement.
  • The application is performing an implicit SQL connection. (The application refers to a three-part name, or alias, that resolves to the remote system.)
In these cases, change the SYSIBM.LUNAMES rows, which are associated to the partner LUNAME, to specify 'P' (password) or 'R' (RACF® PassTicket) for SECURITY_OUT. If you specify 'P', you must also:
  • Add a SYSIBM.USERNAMES outbound row that specifies the user ID and its associated password.
  • Specify a SYSIBM.LUNAMES USERNAMES column value of 'O' or 'B' to satisfy referential constraints on the SYSIBM.USERNAMES table.

User response

Notify the system programmer.

Problem determination

Collect the following diagnostic items:
  • The VTAM APPL definition for the remote Db2 system.
  • The contents of the SYSIBM.LUNAMES table.