MODEENT options

When you define your Db2 subsystem to VTAM®, you can specify mode values. As you choose these values, be aware that partner systems can have different values. VTAM negotiates different values to limits that are acceptable to both systems when the session is established for the mode.

The options that are used in the MODEENT macro have the following meanings.

name

The name option (IBMDB2LM and IBMRDB in the examples) is optional and has no function in the specification of a logon mode table.

LOGMODE

Specifies the logon mode name that is to be used as a key for the session options in this table entry. This logon mode name corresponds to mode name columns in the CDB.

TYPE

TYPE=0 indicates that Db2 is using a negotiable BIND, which is required for communicating with dependent LUs.

SRCVPAC

Specifies the secondary receive pacing count. The Db2 suggested value is X'00'.

SSNDPAC

Specifies the secondary send pacing count. The Db2 suggested value is any nonzero number. Do not use 0; this turns off pacing, which can result in problems with IOBUF storage.

RUSIZES

Specifies the maximum length of data in bytes that can be sent and received in one request/response unit (RU). It is read as two numbers, each having two hexadecimal digits. The first number is for the send amount. The second number is for the receive amount. The suggested value of X'8989' means that VTAM sends a maximum of 4096 bytes (8 × 2⁹) across at one time, but there is no limit to how much total information can be sent.

FMPROF

This constant specifies the function management profile that is required for LU 6.2.

TSPROF

This constant specifies the transmission services profile that is required for LU 6.2.

PRIPROT

This constant specifies the primary LU protocols that are used in LU 6.2.

SECPROT

This constant specifies the secondary LU protocols that are used in LU 6.2.

COMPROT

This constant specifies the common LU protocols that are used in LU 6.2.

PSERVIC

This constant specifies this LU as an LU type 6.2.

Some of the above options can have a profound effect on performance because of their impact on pacing.

The ENCR option is not included in the sample above because it is ignored by LU 6.2.