3200
|
ERROR: Invalid numeric value range
|
|
|
Description
|
The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The MAX_LISTENING_EP parameter in the DM_OSITP section specified a value that is out of the accepted range. The MAX_LISTENING_EP parameter must be within the range of 0 to 32767.
|
|
Action
|
Correct the value of the MAX_LISTENING_EP parameter in the DM_OSITP section and retry the operation.
|
|
See Also
|
dmloadcf(1)
|
3201
|
ERROR: Value of MAX_LISTENING_EP must be in <0, 32767> range
|
|
|
Description
|
The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The MAX_LISTENING_EP parameter in the DM_OSITP section specified a value that is out of the accepted range. The MAX_LISTENING_EP parameter must be within the range of 0 to 32767.
|
|
Action
|
Correct the value of the MAX_LISTENING_EP parameter in the DM_OSITP section and retry the operation.
|
|
See Also
|
dmloadcf(1)
|
3202
|
ERROR: Bad string value for XATMI_ENCODING, ignored
|
|
|
Description
|
The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The XATMI_ENCODING parameter in the DM_OSITP section specified an invalid string value. The XATMI_ENCODING parameter must be one of the following: PRELIMINARY, UNISYS, OLTP_TM2200, or CAE.
|
|
Action
|
Correct the value of the XATMI_ENCODING parameter in the DM_OSITP section and retry the operation.
|
|
See Also
|
dmloadcf(1)
|
3203
|
ERROR: Invalid XATMI_ENCODING(value) for domain(name)
|
|
|
Description
|
The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The XATMI_ENCODING parameter in the DM_OSITP section entry for domain name specified an invalid string value value. The XATMI_ENCODING parameter must be one of the following: PRELIMINARY, UNISYS, OLTP_TM2200, or CAE.
|
|
Action
|
Correct the value of the XATMI_ENCODING parameter in the DM_OSITP section and retry the operation.
|
|
See Also
|
dmloadcf(1)
|
3204
|
ERROR: Invalid LDOM/RDOM pair ldom / rdom for operation.
|
|
|
Description
|
The Domains Administrative Server (DMADM) detected an error while processing MIB(5) request. The specified Local Domain/Remote Domain pair ldom/rdom is incorrect. The domain types for ldom and rdom must match.
|
|
Action
|
Correct the values of ldom and/or rdom and retry the operation.
|
|
See Also
|
dmadmin(1), MIB(5)
|
3212
|
ERROR: Unknown CONNECTION_POLICY <string>. Only ON_DEMAND, ON_STARTUP, INCOMING_ONLY are recognized
|
|
|
Description
|
The dmloadcf(1) utility detected an error while processing the dmconfig file. The CONNECTION_POLICY parameter in the DM_LOCAL_DOMAINS section is set to an invalid setting.
|
|
Action
|
Correct the entry in the DM_LOCAL_DOMAINS section and retry the operation.
|
|
See Also
|
dmloadcf(1), dmconfig(5)
|
3214
|
ERROR: RETRY_INTERVAL only allowed with CONNECTION_POLICY of ON_STARTUP
|
|
|
Description
|
The dmloadcf(1) utility detected an error while processing the dmconfig file. The RETRY_INTERVAL parameter in the DM_LOCAL_DOMAINS section is allowed only for the ON_STARTUP connection policy.
|
|
Action
|
Either change the CONNECTION_POLICY to ON_STARTUP or remove the RETRY_INTERVAL.
|
|
See Also
|
dmloadcf(1), dmconfig(5)
|
3216
|
ERROR: MAXRETRY not allowed with CONNECTION_POLICY of ON_DEMAND
|
|
|
Description
|
The dmloadcf(1) utility detected an error while processing the dmconfig file. The MAXRETRY parameter in the DM_LOCAL_DOMAINS section is allowed only for the ON_STARTUP connection policy.
|
|
Action
|
Either change the CONNECTION_POLICY to ON_STARTUP or remove the MAXRETRY.
|
|
See Also
|
dmloadcf(1), dmconfig(5)
|
3217
|
ERROR: Cannot have more than number entries in RDOM LIST
|
|
|
Description
|
The dmloadcf(1) utility detected an error while processing the dmconfig file. When using Domains-level failover, you may specify a comma-separated list for RDOM in a DM_REMOTE_SERVICES entry. A maximum of three entries are allowed: RDOM=R1, R2, R3.
|
|
Action
|
Change the value of the RDOM parameter specifying a maximum of three values.
|
|
See Also
|
dmloadcf(1), dmconfig(5)
|
3218
|
ERROR: For CONNECTION_POLICY setting, DOMAIN TYPE must be TDOMAIN
|
|
|
Description
|
The dmloadcf(1) utility detected an error while processing the dmconfig file. The CONNECTION_POLICY parameter in the DM_LOCAL_DOMAINS section is specified for the wrong type of domain. The CONNECTION_POLICY parameter can be specified only for local domains of type TDOMAIN.
|
|
Action
|
Correct the entry in the DM_LOCAL_DOMAINS section and retry the operation.
|
|
See Also
|
dmloadcf(1), dmconfig(5)
|
3222
|
ERROR: MAXRETRY only allowed with CONNECTION_POLICY of ON_STARTUP
|
|
|
Description
|
The dmloadcf(1) utility detected an error while processing the dmconfig file. The MAXRETRY parameter in the DM_LOCAL_DOMAINS section is allowed only for the ON_STARTUP connection policy.
|
|
Action
|
Either change the CONNECTION_POLICY to ON_STARTUP or remove the MAXRETRY.
|
|
See Also
|
dmloadcf(1), dmconfig(5)
|
3224
|
ERROR: Unknown CONNECTION_POLICY <string>.
|
|
|
Description
|
During dynamic configuration, an unknown connection policy was entered.
|
|
Action
|
Change the connection policy to either ON_STARTUP, ON_DEMAND or INCOMING_ONLY.
|
|
|
|
3225
|
WARN: multiple RDOMs not allowed on REMOTE_SERVICES in string mode
|
|
|
Description
|
When the CONNECTION_POLICY is not set in the DM_LOCAL_DOMAINS entry, or is set to ON_DEMAND, you may not specify multiple values for RDOM in a DM_REMOTE_SERVICES entry. If multiple values for RDOM are specified, only the first one will be used. Using multiple values allows you to specify Domains-level failover, where a comma-separated list of RDOMs can be specified. The first value listed for RDOM is the primary value; the rest are alternates.
|
|
Action
|
If Domains-level failover/failback is desired, you must set the CONNECTION_POLICY to either ON_STARTUP or INCOMING_ONLY. If Domains-level failover/failback is not desired, you can continue to run the gateway as is (the first value of RDOM will be used), or modify the configuration file so that only one value for RDOM is specified in the DM_REMOTE_SERVICES entry.
|
|
|
|
3226
|
WARN: Only the first RDOM in the list will be used
|
|
|
Description
|
When multiple RDOMs are specified in a DM_REMOTE_SERVICES entry and the connection policy is set to ON_DEMAND, only the first RDOM in the comma-separated list is used.
|
|
Action
|
If this is the desired behavior, no action is required. If failover is desired, another connection policy must be specified.
|
|
|
|
3250
|
ERROR: Cannot send config to GWADM group=val
|
|
|
Description
|
The DMADM administrative server could not send the initial configuration information to a GWADM for the local domain corresponding to the group, grp.
|
|
Action
|
Make sure that the BDMCONFIG file still exists and is accessible.
|
|
See Also
|
dmconfig(5)
|
3251
|
ERROR: Cannot register GWADM of group val
|
|
|
Description
|
The DMADM administrative server could not process a request to register from a GWADM administrative server. Check surrounding messages for specifics.
|
|
Action
|
Correct the error and re-boot the application.
|
|
See Also
|
dmconfig(5)
|
3252
|
ERROR: Cannot send config section val to GWADM group=val
|
|
|
Description
|
The DMADM administrative server could not send the section numbered section_num to the GWADM administrative server corresponding to group, grp.
|
|
Action
|
Make sure that the BDMCONFIG file still exists and is accessible.
|
|
See Also
|
dmconfig(5)
|
3253
|
ERROR: Can't put FIELDTBLS32 into environment
|
|
|
Description
|
The BEA TUXEDO Domain Administrative server detected an error while trying to create the configuration environment. The environment variable FIELDTBLS32 could not be added to the environment.
|
|
Action
|
Make the existing environment smaller by unsetting some unneeded variables (or make environment larger if the operating system allows it) and re-execute the program.
|
|
See Also
|
DMADMIN(1), dmconfig(5)
|
3254
|
ERROR: Can't put FLDTBLDIR32 into environment
|
|
|
Description
|
The BEA TUXEDO Domain Administrative server detected an error while trying to create the configuration environment. The environment variable FLDTBLDIR32 could not be added to the environment.
|
|
Action
|
Make the existing environment smaller by unsetting some unneeded variables (or make environment larger if the operating system allows it) and re-execute the program.
|
|
See Also
|
DMADMIN(1), dmconfig(5)
|
3255
|
ERROR: Cannot un-register GWADM group=val
|
|
|
Description
|
A GWADM administrative server, when first booted, registers with the DMADM server. When the GWADM is about to shut down, it sends a message to DMADM to un-register. This message indicates that this particular GWADM server never registered with the currently running DMADM server.
|
|
Action
|
No action required.
|
|
See Also
|
dmconfig(5)
|
3256
|
ERROR: Incompatible GWADM server -- group = val
|
|
|
Description
|
A DMADM administrative server received a registration
request from a GWADM server that is no compatible.
This may because the GWADM is from a later release
or otherwise needs a capability not available.
|
|
Action
|
Check that your configuration is correct. Call BEA Support.
|
|
See Also
|
DMADMIN(1), dmconfig(5)
|
3257
|
ERROR: Fldid failed(Ferror=val). Can't find TA_SRVGRP in FIELDTBLS32 files
|
|
|
Description
|
The Gateway Administrative process, GWADM, failed to find the definition for one of the system field table in the FIELDTBLS32 and FLDTBLDIR32 environment variable.
|
|
Action
|
Usually this table is in the udataobj subdirectory under TUXDIR, and its name is dmadmin32. If FLDTBLDIR32 not specified, then it assumes the default location is TUXDIR/udataobj. Check if the file exists. If the file does not exist, you may need to re-install the TUXEDO product. If after the re-installation this file still missing, you need to contact BEA support. If the file does exist, then you need to check your environment.
|
|
See Also
|
dmconfig(5)
|
