--- title: "Connecting to IBM Db2 for z/OS" slug: "connection-to-ibm-db2-for-zos" updated: 2026-02-05T05:42:18Z published: 2026-02-05T05:42:18Z canonical: "skthelp.syniti.com/connection-to-ibm-db2-for-zos" --- > ## Documentation Index > Fetch the complete documentation index at: https://skthelp.syniti.com/llms.txt > Use this file to discover all available pages before exploring further. # Connecting to IBM Db2 for z/OS When connecting to a IBM Db2 OS/390 database from the Syniti Knowledge Platform (SKP), provide the following connection properties to establish a secure and reliable connection. This article explains each property to understand what information is required and how it is used. | **Property** | Description | Notes | | --- | --- | --- | | **Name** *(required)* | Name of the IBM Db2 zSystem, OS/390 connection unique to the SKP. | NA | | **Description** | Enter a description that briefly states the purpose of this connection. | NA | | **Hostname** *(required)* | Hostname is the network name or IP address of the IBM Db2 machine you want to connect to. | NA | | **Port** *(required)* | The TCP/IP port number on which the Db2 database listens for incoming connections. | Default for Db2 LUW is typically 50000 unless explicitly configured otherwise. | | **Username** *(required)* | The database account identifier used for authentication when establishing the connection. | The account must have the necessary privileges for the operations being performed. | | **Password** *(required)* | The password for the username above. | This value is used to authenticate the connection to the database. | | **Security Mechanism** | Defines the authentication or encryption scheme used for the connection (for example, SSL or alternate token/key mechanisms). | This setting dictates how credentials are validated and may affect encryption layers. Default values User/Password. | | **Database** | The name of the specific Db2 database instance to connect to on the server. | Db2 servers can host multiple logical databases. | | **Host Code Page** *(required)* | The code page setting that influences character encoding conversion between the client and database. | Ensures correct interpretation of text data across differing regional or system defaults. | | **Socket Timeout** | The maximum wait time for socket-level operations before the connection attempt or data transfer is aborted. | Helps avoid indefinite hangs during connectivity or network delays. Default value 90 seconds. | | **Package Collection** | The job or library collection where Db2 packages (compiled SQL execution plans) are bound. | This affects how SQL statements are prepared and optimized. Default value is NULLID. | | **Isolation Level** | The transactional isolation mode (e.g., *Uncommitted Read*, *Cursor Stability*, *Repeatable Read*) that governs visibility of data changes during concurrent access. | No Commit (NC) | | **Alternative Qualifier** | An optional schema or namespace qualifier used to resolve objects when the default schema isn’t appropriate. | Enables connection scope customization for multi-schema environments. | | **Fetch Block Size** | The number of rows the driver retrieves per network call during query result set retrieval. | Larger values can improve throughput for large result sets. | | **Hold Cursors** | Controls whether cursors remain open across commits. | A setting of *on* retains active cursors after transaction commits; *off* closes them. Useful for applications that rely on cursor continuity. | | **Bind Rules** | Determines whether driver bind rules are applied for package creation, potentially affecting compatibility and performance of prepared statements. | Available only with DB2 MVS v4.1 or higher. | | **Convert Date Time** | Enables automatic conversion of date/time formats between client and server representations. | Turning this off may require the client to handle formatting explicitly. | | **Remove Blanks** | Indicates whether trailing blanks are trimmed from fixed-length character fields before returning data to the client. | Used at the end of a character field, for example, CHAR, VARCHAR, LONGVARCHAR. | | **Connection Pooling** | When enabled, connections are reused from a pool instead of opening a new connection for every request. | Pooling greatly improves performance in high-throughput environments. | | **Minimum Pool Size** *(required)* | The smallest number of connections that the pool maintains open when pooling is active. | Ensures a baseline of ready connections. | | **Maximum Pool Size** *(required)* | The upper limit on the number of simultaneous pooled connections. | Prevents excessive resource consumption and enforces predictable connection capacity. | | **Connection Lifetime** *(required)* | The amount of time a pooled connection is kept alive before being retired. | Helps avoid issues with stale connections and enforces periodic reconnection cycles. | ## Related Articles [Create a Connection](/v1/docs/create-a-connection)