SYSIBM.LUNAMES
                        www.cadcobol.com - linguagem de programação COBOL

Volta a página anterior

Volta ao Menu das SYSIBM

Volta ao Menu Principal


Desenvolvido por DORNELLES, Carlos Alberto - Analista de Sistemas - Brasília DF.

The table must contain a row for each remote SNA client or server that communicates with DB2. Rows in this table can be inserted, updated, and deleted.

Nome da coluna Tipo do dado Descrição Uso
 LUNAME  CHAR(8) NOT NULL  Name of the LU for one or more accessible systems. A blank string indicates the  row applies to clients whose LU name is not specifically defined in this table.

 All other column values for a given row in this table are for clients and servers  associated with the row's LU name.		  G
 SYSMODENAME  CHAR(8) NOT NULL
 WITH DEFAULT		  Mode used to establish inter-system conversations. A blank indicates the default  mode IBMDB2LM (used for DB2 private protocol access and for collecting syplex  balancing information from remote data sharing groups).

 If private protocols are used to access a remote DB2 LU or if the remote LU is a  member of a DB2 data sharing group, use a separate mode other than the default  mode.		  G
 SECURITY_IN  CHAR(1) NOT NULL
 WITH DEFAULT 'A'		  This column defines the security options that are accepted by this DB2 when an  SNA client connects to DB2:

 V       The option is "verify." An incoming connection request must include one of the            following: a userid and password, a userid and RACF PassTicket, or a
           Kerberos security ticket.

 A       The option is "already verified." A request does not need a password,
           although a password is checked if it is sent.

           With this option, an incoming connection request is accepted if it includes any            of the following:
           a userid, a userid and password, a userid and RACF PassTicket, or a Kerberos            security ticket.

           If the USERNAMES column contains 'I' or 'B', RACF is not invoked to validate            incoming connection requests that contain only a userid.		  G
 SECURITY_OUT  CHAR(1) NOT NULL
 WITH DEFAULT 'A'		  This column defines the security option that is used when local DB2 SQL  applications connect to any remote server associated with this LUNAME:

 A       The option is "already verified." Outbound connection requests contain an            authorization ID and no password.

           The authorization ID used for an outbound request is either the DB2 user's            authorization ID or a translated ID, depending upon the value of the
           USERNAMES column.

 R       The option is "RACF PassTicket." Outbound connection requests contain a            userid and a RACF PassTicket. The server's LU name is used as the RACF            PassTicket application name.

           The authorization ID used for an outbound request is either the DB2 user's            authorization ID or a translated ID, depending upon the value of the
           USERNAMES column.

 P       The option is "password." Outbound connection requests contain an
           authorization ID and a password. The password is obtained from the
           SYSIBM.USERNAMES table or RACF, depending upon the value specified in            the ENCRYPTPWDS column.

           The USERNAMES column must specify 'B' or 'O'.		  G
 ENCRYPTPSWDS  CHAR(1) NOT NULL
 WITH DEFAULT 'N'		  This column only applies to DB2 for OS/390 and z/OS partners. It is provided to  support connectivity to prior releases of DB2 that are unable to support RACF  PassTickets.

 For connections between DB2 Version 5 and later, we recommend using the  SECURITY_OUT='R' option instead of the ENCRYPTPSWDS='Y' option.

 N       No, passwords are not in internal RACF encrypted format. This is the default.

 Y       Yes for outbound requests, the encrypted password is extracted from RACF            and sent to the server. For inbound requests, the password is treated as            encrypted.		  G
 MODESELECT  CHAR(1) NOT NULL
 WITH DEFAULT 'N'		  Whether to use the SYBIBM.MODESELECT table:

 N       Use default modes: IBMDB2LM (for DB2 private protocol) and IBMRDB (for            DRDA).

 Y       Searches SYSIBM.MODESELECT for appropriate mode name.		  G
 USERNAMES  CHAR(1) NOT NULL
 WITH DEFAULT		  This column controls inbound and outbound authorization ID translation, and
 "come from" checking.

 Inbound translation and "come from" checking are performed when an
 authorization ID is received from a remote client.

 Outbound translation is performed when an authorization ID is sent by DB2 to a  remote server.

 When I, O, or B is specified in this column, rows in the SYSIBM.USERNAMES table  are used to perform ID translation.

 I       An inbound ID is subject to translation and "come from" checking.

           No translation is performed on outbound IDs.

 O       No translation or "come from" checking is performed on inbound IDs.

           An outbound ID is subject to translation.

 B       An inbound ID is subject to translation and "come from" checking.

          An outbound ID is subject to translation.

 blank   No translation occurs.		  G
 GENERIC  CHAR(1) NOT NULL
 WITH DEFAULT 'N'		  Indicates whether DB2 should use its real LU name or generic LU name to identify  itself to the partner LU, which is identified by this row.

 N       The real VTAM LU name of this DB2 subsystem

 Y       The VTAM generic LU name of this DB2 subsystem		  G
 IBMREQD  CHAR(1) NOT NULL
 WITH DEFAULT 'N'		  A value of Y indicates that the row came from the basic machine-readable material  (MRM) tape. For all other values, see Release dependency indicators in topic D.0.  G