Y Secure connection using SSL required for outbound DRDA Use Secure Socket Layer (SSL) protocol for outbound DRDA connections when local DB2 applications connects to remote database server using TCP/IP Access to remote location requires trusted context defined at remote location Name is used to access a remote database serverĬonnection to remote server can be trusted. Used only when local DB2 begins an SNA conversation with another serverĭatabase alias. TCP/IP is used for outbound DRDA connections when following statements is true: Row exists in IPNAMES, where LINKNAME column matches value specified in LOCATIONS LINKNAME column Y indicates row came from basic (MRM) tape Identifies VTAM or TCP/IP attributes associated with this location Name by which the remote server is known to local DB2 SQL applications IP address or domain name of a remote TCP/IP hostĬontains a row for every accessible remote server Column nameĪ unique location name for accessible server. S USERNAMES table is used to obtain systemĪUTHID used to establish a trusted connection Blank No translation occurs No translation or ‘come from’ checking is performed an inbound IDs. USERNAMES table are used to perform ID translation. O An outbound ID is subject to translation. Performed when an auth ID is sent by DB2 to a remote server: #Transtype in java passwordValue specified must value specified in LINKNAME column of associated role in LOCATIONSĭRDA security option used when local DB2 SQL applications connect to remote server associated with this TCP/IP host:ĭ “userid and security sensitive data encryption”Į “userid, password and security sensitive data encryption”Ĭontrols outbound auth ID translation. Defines the remote DRDA servers DB2 can access using TCP/IP Column name
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |