Distributed Data Facility Panel 1 (DSNTIPR)
This topic shows detailed information about System Parameters - Distributed Data Facility Panel 1 (DSNTIPR)
.
This block shows how Distributed Data Facility (DDF) was started and the names used to connect another Db2 subsystem.
To use DDF, you must have VTAM installed, even if you use TCP/IP connections only.
System Parameters - Distributed Data Facility Panel 1 (DSNTIPR)
The field labels shown in the following sample layout of System Parameters - Distributed Data Facility Panel 1 (DSNTIPR)
are described in the following section.
DISTRIBUTED DATA FACILITY PANEL 1 (DSNTIPR)
-------------------------------------------
FACILITY NAME...............................................DDF
DDF STARTUP OPTION (DDF)...................................AUTO
RLST ACCESS ERROR (RLFERRD).............................NOLIMIT
RESYNCHRONIZATION INTERVAL IN MINUTES (RESYNC)................2
DBAT STATUS (CMTSTAT)..................................INACTIVE
MAX TYPE 1 INACTIVE THREADS (MAXTYPE1)........................0
IDLE THREAD TIMEOUT INTERVAL (IDTHTOIN)...................1,800
EXTENDED SECURITY (EXTSEC)..................................YES
USER ID AND PASSWORD REQUIRED................................NO
SQL INTERRUPT PROCESSING DISABLED (SQLINTRP).................NO
PRIVATE PROTOCOL (PRIVATE_PROTOCOL)........................AUTH
- FACILITY NAME
-
The name of the DDF facility.
Field Name: QWP9NAME
- DDF STARTUP OPTION (DDF)
-
Indicates whether DDF is loaded, and if so, how it was started.
When NO, DDF was not loaded at Db2 startup and cannot be started.
AUTO means DDF was loaded and started automatically when Db2 was started. The DDF address space was started as part of DDF initialization.
COMMAND means DDF was initialized and the DDF address space was started at Db2 startup. IF DDF is running, it was started from the console with the -DSN1 START DDF command. If it is not running, it can be started with this command.
Install parameter DDF STARTUP OPTION on panel DSNTIPR, or ZPARM DDF in DSN6FAC.
Field Name: QWP9STRT
- RLST ACCESS ERROR (RLFERRD)
-
Shows what Db2 does when the governor cannot access the resource limit specification table or when no row in the table matches the currently executing statement.
NOLIMIT (default) allows all dynamic SQL statements to run without limit.
NORUN terminates all dynamic SQL statements immediately with an SQL error code.
The number of CPU service units allowed for a query can be anywhere from 1 to 5000000.
Install parameter RLST ACCESS ERROR on panel DSNTIPR, or ZPARM RLFERRD in DSN6FAC (Db2 field QWP9RLER).
Field Name: QWP9RLER
- RESYNCHRONIZATION INTERVAL IN MINUTES (RESYNC)
-
The number of minutes between resynchronization periods.
A resynchronization period is the time during which indoubt logical units of work involving this Db2 subsystem and partner logical units are processed.
Install parameter RESYNC INTERVAL on panel DSNTIPR, or ZPARM RESYNC in DSN6FAC.
Field Name: QWP9RYC
- DBAT STATUS (CMTSTAT)
-
Shows whether Db2 inactivates threads that have successfully committed or rolled back, and hold no cursors.
ACTIVE provides the best performance but consumes system resources.
INACTIVE is recommended when the installation must support a large number of connections.
When a thread becomes eligible for inactivation, Db2 tries to make it a type 2 inactive thread, which uses less storage than a type 1 inactive thread. If this fails, Db2 tries to make it a type 1 inactive thread. If neither attempt is successful, the thread remains active.
Install parameter DDF THREADS on panel DSNTIPR, or ZPARM CMTSTAT in DSN6FAC.
Field Name: QWP9CMST
- MAX TYPE 1 INACTIVE THREADS (MAXTYPE1)
-
Indicates the number of type 1 inactive threads that Db2 allows.
A large number of type 1 inactive threads can adversely affect system performance. Type 1 inactive threads are used for Db2 private protocol.
DRDA uses type 2 inactive threads.
Zero indicates that type 1 inactive connections are not allowed. Threads remain active when they become eligible to be made a type 1 inactive thread.
A value greater than zero indicates that type 1 inactive connections are allowed, but are limited to this number. When a thread becomes eligible to be made a type 1 inactive thread, and this threshold is reached, the remote connection is terminated.
When this is equal to MAX REMOTE CONNECTED on panel DSNTIPE, Db2 allows all remote threads to become type 1 inactive threads.
Install parameter MAX INACTIVE DBATS on panel DSNTIPR, or ZPARM MAXTYPE1 in DSN6FAC.
Field Name: QWP9MAX1
- IDLE THREAD TIMEOUT INTERVAL (IDTHTOIN)
-
The approximate time, in seconds, that an active server thread can remain idle before it is canceled.
Inactive and indoubt threads are not subject to timeout.
Threads are checked for timeouts every 3 minutes. This means that timeouts might not be honored for up to 3 minutes when the timeout value is less than this.
0 (default) means timeout processing is disabled, idle server threads remain in the system and continue to hold their resources, if any.
Install parameter IDLE THREAD TIMEOUT on panel DSNTIPR, or ZPARM IDTHTOIN in DSN6FAC.
Field Name: QWP9TTO
- EXTENDED SECURITY (EXTSEC)
-
Extended security options.
When YES (strongly recommended), detailed reason codes are returned to a DRDA level 3 client when a DDF connection request fails because of security errors. When using SNA protocols, the requester must have included a product that supports the extended security sense codes, such as Db2 Connect version 5 and subsequent releases.
RACF users can change their passwords using the DRDA change password function. This support is only for DRDA level 3 requesters that have implemented support for changing passwords.
YES allows properly enabled DRDA clients to determine the cause of security failures without requiring Db2 operator support.
When NO, generic error codes are returned to the clients and RACF users are prevented from changing their passwords.
Install parameter EXTENDED SECURITY on panel DSNTIPR, or ZPARM EXTSEC in DSN6SYSP.
Field Name: QWP1SCER
- USER ID AND PASSWORD REQUIRED
-
Shows whether user ID and password are required. In addition, one of the following is required:
- The user ID and password and any RACF® PassTickets (A PassTicket is a one-time-only password that is generated by a requesting product or function) are Advanced Encryption Standard (AES) encrypted.
- A Kerberos ticket is required.
- The connection is protected by a z/OS® Communications Server IP Application Transparent Transport Layer Security (AT-TLS) policy, which is ensured through a Db2® SECPORT.
- The connection is protected by an IPSec tunnel.
Field Name: QWP9TCPVE
- SQL INTERRUPT PROCESSING DISABLED (SQLINTRP)
-
Shows how SQL interrupts are processed. It can have the following values:
- NO
- SQL interrupt processing is enabled.
- YES
- Db2 SQL interrupt support is disabled. Note: YES should only be used if remote client systems experience failures because of SQL interrupts. In this case, SQL interrupt support should be disabled only until the remote client systems can be modified to tolerate SQL interrupts.
ZPARM name SQLINTRP in DSN6FAC.
Field Name: QWP9SINTD
- PRIVATE PROTOCOL (PRIVATE_PROTOCOL)
-
Shows if it is allowed to use the private protocol. It can have the following values:
- YES
- Allows private-protocol-related plan-owner-based package authorization behavior. Plan-owner-based package execution authorization semantics are honored for Db2 for z/OS DRDA requester systems that might rely on it. Secondary IDs are not used to determine package execution privileges for remote Db2 for z/OS applications.
- NO
- Does not allow any private-protocol-related behavior. Plan-owner-based package execution authorization semantics are not honored. This might affect Db2 for z/OS DRDA requester systems that rely on it. Secondary IDs are used to determine package execution privileges for remote Db2 for z/OS applications.
ZPARM name PRIVATE_PROTOCOL in DSN6FAC.
Field Name: QWP9PRVPA