The following table describes the parameters used by xdbappc.ini.
PU Definition Section
| Parameter | Description |
|---|---|
PU |
Physical Unit name. This parameter must match the entry in the CSCON profile named "Peripheral CP Name." |
Profile |
Profile name. This name must match the name of the profile configured with CSCON and loaded with CSLOAD. |
Network |
Network Identifier. This parameter must match the entry in the CSCON profile named "SNA Network ID." |
LuName |
Logical Unit Name. This is the LU name configured on the host that identifies this computer. |
LuAlias |
Logical Unit Alias Name. This is the name of the LU as it will be known locally. We recommend that you use the XDB Server name as the alias. |
LocAddr |
LU local address. This address must be 0 for independent LUs. |
SessionLimit |
LU Session Limit. This value specifies the number of sessions this LU can have with the host. The value should be less than or equal to the entry in the CSCON profile named "Independent Sessions." |
MaxTPs |
Maximum Transaction Program Limit. This entry indicates the number of transaction programs that can use this LU. It should be less than or equal to the session limit above. Each user connected through XDB Link gets an individual session and TP, so MaxTPs represents the maximum XDB Link connections possible with the host. |
QueueDepth |
Depth of incoming allocate queue. This is the number of allocate requests that can be in the queue, waiting to be serviced by this LU. |
PLU |
Partner Logical Unit Name. This specifies the remote database as it is known to the SNA network. For MVS/VTAM, this is the VTAM DB2 APPLID name. |
Network ID |
Network Identifier. This is the name of the SNA network to which the partner LU belongs. This allows for a fully-qualified partner LU name. |
Alias |
Partner Logical Unit Alias. This is the name of the partner LU as it will be known locally. The value of this parameter is used by the Gateway Profile Utility to identify the remote database. |
Security |
Partner Logical Unit Security Capabilities.
Combinations of security capabilities can be added together. For Example: 3 is Conversation Level security and Already Verified (1 OR 2). |
SessionLimit |
Partner Logical Unit Session Limit. This entry is the maximum number of sessions for which this partner is configured. |
MaxMcSendLL |
Maximum Mapped Conversation Send Logical Length. Maximum size of data to send on a mapped conversation. The value 0 means use the largest possible value (32767). |
DlcName |
Data Link Control Name. This entry identifies the connection type to the host system. Possible values are:
|
AdaptNum |
Adapter Number. Indicates which adapter to use. For Token Ring use 0 to indicate the Primary adapter or 1 to indicate the Secondary adapter. All other DLCs should use 0. |
AdaptAddr |
Adapter address:
|
ModeName |
Mode Name. This entry is used to identify which mode definition to use for this partner LU. |
Mode Definition Section
| Parameter | Description |
|---|---|
Mode |
The Mode Name. The name of the mode to use for setting up sessions between the Local LU and the Partner LU. The recommended value is IBMRDB. |
MaxRu |
Maximum Request/Response Unit. The maximum size (in bytes) of a Request/Response Unit. |
MinRu |
Minimum Request/Response Unit. The minimum size (in bytes) of a Request/Response Unit. |
MaxNegotiable |
The Maximum Negotiable Session Limit. This value is used to override the PLU max session limit. |
Pacing |
Pacing Limit. The maximum number of Request/Response Units allowed before confirmation between LU and PLU. |