IFCID 106 - Distributed Data Facility Parameters

This topic shows detailed information about "Record Trace - IFCID 106 - Distributed Data Facility Parameters".

This block shows how Distributed Data Facility (DDF) was started and the protocols used.

To use DDF, you must have VTAM installed, even if you use TCP/IP connections only.

Record trace - IFCID 106 - Distributed Data Facility Parameters

The field labels shown in the following sample layout of "Record Trace - IFCID 106 - Distributed Data Facility Parameters" are described in the following section.

                                       DISTRIBUTED DATA FACILITY PARAMETERS                                              
FACILITY NAME ...: DDF                   FACILITY START ..:                 AUTO  TCP/IP VERIFIED .:                   NO
DBAT STATUS .....: INACTIVE              RLF DYNAMIC ERROR:              NOLIMIT  TCP/IP KEEPALIVE :                  120
IDLE THR TIMEOUT :                  120  RLF STATIC ERROR :              NOLIMIT  MAX T1 INACT THR :                    0
POOL THR TIMEOUT :                  120  PRIVATE PROTOCOL :                   NO  RESYNCH INTERVAL :                    2
CONN Q MAX DEPTH :                    0  ID & PASSWORD REQ:                   NO  SQL INTRPT DISABL:                   NO
CONN Q MAX WAIT .:                    0  DDF COMP PRIOR V :  
                                      DDF COMPATIBILITY                                                                                                   
SP_PARMS_JV      :                   NO  SP_PARMS_NJV     :                   NO  IGNORE_TZ        :                   NO
DSBL_IMPCAST_JV  :                   NO  DSBL_IMPCAST_NJV :                   NO                                         
FACILITY NAME

The name of the DDF facility.

Field Name: QWP9NAME

FACILITY START

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

TCP/IP VERIFIED

Indicates whether DB2 accepts TCP/IP connection requests containing only a user ID.

When YES, a connection request is accepted with a user ID only. This value must be the same for all members of a data sharing group.

When NO (default), TCP/IP clients must provide authentication information (password, RACF PassTicket, or Kerberos ticket) to gain access to DB2.

Install parameter TCP/IP ALREADY VERIFIED on panel DSNTIP5, or ZPARM TCPALVER in DSN6FAC.

Field Name: QWP9TCPA

DBAT STATUS

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

RLF DYNAMIC ERROR

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.

A number from 1 to 5000000 is the default limit; if the limit is exceeded, the SQL statement is terminated.

Install parameter RLST ACCESS ERROR on panel DSNTIPR, or ZPARM RLFERRD in DSN6FAC (DB2 field QWP9RLER).

Field Name: QWP9RLER

TCP/IP KEEPALIVE

Indicates whether the TCP/IP configuration KeepAlive value has been overwritten.

When ENABLE (default), KeepAlive is enabled, the TCP/IP configuration stack value is used.

When DISABLE, TCP/IP KeepAlive has been disabled.

A value in the range 1 through 65534 means KeepAlive is active, and the TCP/IP stack value has been overridden. The number reported shows the time, in seconds, between TCP/IP probes.

When considering overwriting the keep-alive time, it is recommended to set a value close to the IDLE THREAD TIMEOUT value on installation panel DSNTIPR or the IRLM RESOURCE TIMEOUT value on installation panel DSNTIPI. It is good practice to set all these to about five minutes, or less.

Because KeepAlive detection is accomplished by probing the network at this interval, avoid small values, which can cause excessive network traffic and system resource consumption.

The trick is to find a proper balance that allows network failures to be detected on a timely basis without impacting system and network performance.

Install parameter TCP/IP KEEPALIVE on panel DSNTIP5, ZPARM TCPKPALV in DSN6FAC.

Field Name: QWP9TCKA

IDLE THR TIMEOUT

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

RLF STATIC ERROR
Start of changeShows what DB2 does when the governor cannot access the resource limit specification table or when no row in the table matches the currently running statement:
NOLIMIT
This is the default. It allows all static SQL statements to run without limit.
NORUN
Terminates all static SQL statements immediately with an SQL error code. A number from 1 to 5000000 is the default limit; if the limit is exceeded, the SQL statement is terminated.
End of change

Start of changeInstall parameter REMOTE STATIC SQL on panel DSNTIPO4, or ZPARM RLFERRDSTC in DSN6FAC (DB2 field QWP9RLER).End of change

Field Name: RLFERRDSTC

MAX T1 INACT THR

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

POOL THR TIMEOUT

The approximate time, in seconds, that a DBAT can remain idle in the pool before it is terminated.

A DBAT thread in the pool counts as an active thread against MAX REMOTE ACTIVE and can hold locks, but does not have any cursors.

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. The default is 120.

Install parameter POOL THREAD TIMEOUT on panel DSNTIP5, ZPARM POOLINAC in DSN6FAC.

Field Name: QWP9INAC

PRIVATE PROTOCOL
Start of changeShows 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.
End of change

ZPARM name PRIVATE_PROTOCOL in DSN6FAC.

Field Name: QWP9PRVPA

RESYNCH INTERVAL

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

CONN Q MAX DEPTH

The maximum depth of the connection-request queue of connections that are waiting for a DBAT to process a request. If this value is non-zero, and QWP9CMST is active, or the subsystem is not a member of a data sharing group, DB2 operates as if this value were 0.

Start of changeA value of 0 is displayed for OFF; a value of 32767 is displayed for ON. End of change

This field corresponds to field CONN QUEUE MAX DEPTH on installation panel DSNTIP5. The ZPARM name is MACONQN in DSN6FAC.

Field Name: QWP9MCONQN

ID & PASSWORD REQ
Start of changeShows 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.
End of change

Field Name: QWP9TCPVE

SQL INTRPT DISABL
Start of changeShows 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.
End of change

Start of changeZPARM name SQLINTRP in DSN6FAC.End of change

Field Name: QWP9SINTD

CONN Q MAX WAIT

The maximum time that a connection waits for a DBAT request. If this value is non-zero, and QWP9CMST is active, or the subsystem is not a member of a data sharing group, DB2 operates as if this value is 0.

Start of changeA value of 0 is displayed for OFF; a value of 1 is displayed for ON. End of change

This field corresponds to field CONN QUEUE MAX WAIT on installation panel DSNTIP5. The ZPARM name is MAXCONQW in DSN6FAC.

Field Name: QWP9MCONQW

DDF COMP PRIOR V

Start of changeThe DDF compatibility parameter. The DB2 server with new-function mode has not yet been activated. The DDF compatibility parameter causes this server to identify itself to all remote clients as being in new-function mode for the previous version. The format of this field in the trace record is nnr, where nn is the version of the DB2 server and r is the release.End of change

Field Name: QWP9DDFCIP

SP_PARMS_JV

Start of changeSpecifies that when a Java client application calls a DB2 for z/OS stored procedure, DB2 returns output argument values with data types that match the data types that were specified in the CallableStatement.registerOutParameter method calls.End of change

Start of changeIf SP_PARMS_JV is not specified, DB2 returns output parameter values with data types that match the data types of the parameters in the stored procedure definition.End of change

Start of changeZPARM name DDF_COMPATIBILITY and ZPARM value SP_PARMS_JV in DSN6FAC.End of change

Field Name: QWP9SPPMJ

SP_PARMS_NJV
Start of changeSpecifies that when a non-Java client application calls a DB2 for z/OS stored procedure, DB2 returns output argument values with data types that match the data types of the corresponding CALL statement arguments, unless one of the following conditions are true:
  • The non-Java client is Version 10 or later.
  • The stored procedure uses a parameter data type that was introduced in DB2 for z/OS Version 10 (XML, TIMESTAMP WITH TIMEZONE, or TIMESTAMP with precision greater than 6).
End of change

Start of changeIf one condition is true, DB2 returns output parameter values with data types that match the data types of the parameters in the stored procedure definition. If SP_PARMS_NJV is not specified, DB2 returns output parameter values with data types that match the data types of the parameters in the stored procedure definition.End of change

Start of changeZPARM name DDF_COMPATIBILITY and ZPARM value SP_PARMS_NJV in DSN6FAC.End of change

Field Name: QWP9SPPM

IGNORE_TZ

Start of changeShows whether to ignore the time zone (TMZ) in TMZ input for Java.End of change

Field Name: QWP9ITZJ

DSBL_IMPCAST_JV
Start of changeSpecifies whether the DB2 for z/OS server disables implicit casting of input host variables from numeric data types to string data types, or from string data types to numeric data types, when the application is a Java client application that uses the IBM Data Server Driver for JDBC and SQLJ. If application compatibility is set to:
  • V10R1: DB2 uses DISABLE_IMPCAST_JV.
  • V11R1 or later: DB2 always does implicit casting.
End of change

Start of changeZPARM name DDF_COMPATIBILITY ZPARM value DISABLE_IMPCAST_JV in DSN6FAC.End of change

Field Name: QWP9ICIJ

DSBL_IMPCAST_NJV

Start of changeSpecifies that DB2 for z/OS disables implicit casting of input host variables from numeric data types to string data types, or from string data types to numeric data types, when the application is a non-Java client application that uses an IBM Data Server client or driver that is at Version 10.5 or earlier.End of change

Start of changeZPARM name DDF_COMPATIBILITY and ZPARM value DISABLE_IMPCAST_NJV in DSN6FAC.End of change

Field Name: QWP9ICIN



Feedback