Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy
	http://www.oracle.com/technology/documentation/index.html   |   Site Map   |   Search   |   PDF Files   |   Contact   |   Glossary
Tuxedo Doc Home   |   Messages   |   Catalog List   |   Previous   |   Next

CMDGW Messages 3600-3699

3601	ERROR: tpalloc failed
	Description	Failed to allocate memory necessary for processing the administrative request.
	Action	Make sure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. If message persists, contact BEA Customer Support with the exact error message.
3602	ERROR: Invalid class specified
	Description	A request for an invalid class has been routed to the DMADM server.
	Action	If using Admin API, check that the Domain Admin is not being called directly. Contact BEA Customer Support with the exact error message.
3603	ERROR: x_SEL=<badhex> contains an invalid hex value
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The S/P/T_SEL parameter in the DM_OSITPX section contains an invalid hex value.
	Action	Correct this entry in the DM_OSITPX section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3609	ERROR: Failover remote domains domain1 and domain2 are not the same domain type for the DM_REMOTE_SERVICES entry service
	Description	A DM_REMOTE_SERVICES entry service specified failover remote domain values in the DMCONFIG file. The failover domains listed, domain1 and domain2, were not of the same domain type (such as TDOMAIN, TOPEND, OSITP, etc.).
	Action	Edit the DMCONFIG file and modify the service entry to only specify alternate RDOM values that are of the same type.
	See Also	dmconfig(5)
3610	ERROR: Domain types differ for local domain ldom and remote domain rdom for the DM_REMOTE_SERVICES entry service
	Description	A DM_REMOTE_SERVICES entry service specified an LDOM parameter and an RDOM parameter that are of different types. A domain gateway may only communicate with a remote domain of the same type (such as TDOMAIN, TOPEND, OSITP, etc.).
	Action	Edit the DMCONFIG file and modify the service entry such that both LDOM and RDOM parameters have matching system types.
	See Also	dmconfig(5)
3611	ERROR: TP_SYSTEM values differ for local domain ldom and remote domain rdom for the DM_REMOTE_SERVICES entry service
	Description	The BEA TOP END DM_REMOTE_SERVICES entry service has local domain ldom specified with a TP_SYSTEM value that does not match the TP_SYSTEM value for the remote domain rdom.
	Action	Edit the DMCONFIG file and modify the service entry such that both LDOM and RDOM have matching TP_SYSTEM parameters.
	See Also	dmconfig for GWTOPEND(5)
3612	ERROR: Failover remote domains domain1 and domain2 do not have matching TP_SYSTEM values for the DM_REMOTE_SERVICES entry service
	Description	The BEA TOP END DM_REMOTE_SERVICES entry service has multiple remote domains specified for the RDOM parameter. In such a failover configuration, all remote domains must have the same TP_SYSTEM value.
	Action	Edit the DMCONFIG file and modify the service entry such that the RDOM values domain1 and domain2 have matching TP_SYSTEM parameters.
	See Also	dmconfig for GWTOPEND(5)
3613	ERROR: memory allocation failure
	Description	Failed to allocate memory necessary for processing the administrative request.
	Action	Make sure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. If message persists, contact BEA Customer Support with the exact error message.
3614	ERROR: FML buffer inconsistency
	Description	While processing a Domains MIB request an inconsistency was discovered in the FML buffer received from a GWADM adminstrative server.
	Action	If the message persists, contact BEA TUXEDO system technical Support with the exact error message.
3615	ERROR: internal table bad
	Description	An internal inconsistency was detected in an internal table used for processing Domains MIB requests.
	Action	Contact BEA TUXEDO system technical Support with the exact error message.
3616	ERROR: unable to read request buffer
	Description	An error has occurred reading an attribute from a GWADM message buffer while processing a Domains MIB request.
	Action	If the message persists, contact BEA TUXEDO system technical Support with the exact error message.
3617	ERROR: FML error (error message) mapping request to gwadm protocol
	Description	An FML error identified in message error message has occurred while mapping a Domains MIB request to internal GWADM protocol.
	Action	If the message persists, contact BEA Customer Support with the exact error message.
3618	ERROR: FML error (error number) mapping request to gwadm protocol
	Description	An FML error identified by error number has occurred while mapping a Domains MIB request to internal GWADM protocol.
	Action	If the message persists, contact BEA Customer Support with the exact error message.
3619	ERROR: Failed decoding GWADM reply (error message)
	Description	The error identified in error message occurred while decoding the reply from GWADM for a Domains MIB request.
	Action	Perform the recommended action for the error message. If the message persists, contact BEA Customer Support.
3620	ERROR: unexpected error response from GWADM (error message)
	Description	The unexpected error identified in error message was received from GWADM while processing a Domains MIB request.
	Action	Perform the recommended action for the error message. If the message persists, contact BEA Customer Support.
3621	ERROR: unrecognised error response (error number) from GWADM (error message)
	Description	An unrecognised error response error number was received from GWADM. The error message error message gives additional information.
	Action	Perform the recommended action for the error message. If the message persists, contact BEA Customer Support.
3622	ERROR: unexpected error response from GWADM (error message)
	Description	The unexpected error identified in error message was received from GWADM while processing a Domains MIB request.
	Action	Perform the recommended action for the error message. If the message persists, contact BEA Customer Support.
3623	ERROR: unexpected error response from GWADM (error message)
	Description	The unexpected error identified in error message was received from GWADM while processing a Domains MIB request.
	Action	Perform the recommended action for the error message. If the message persists, contact BEA Customer Support.
3624	ERROR: call to GWADM failed tperrno(error number)
	Description	While processing a Domains MIB request, and unexpected error response was received from an internal call to the GWADM adminstration server. The tperrno error number given in error number details the error that occurred.
	Action	If the GWADM administration server is no longer running, restart it and repeat the request. Otherwise, if the message persists, contact BEA Customer Support.
3625	ERROR: unexpected error response from GWADM (error message)
	Description	The unexpected error identified in error message was received from GWADM while processing a Domains MIB request.
	Action	Perform the recommended action for the error message. If the message persists, contact BEA Customer Support.
3626	ERROR: unrecognised error response (error number) from GWADM (error message)
	Description	An unrecognised error response error number was received from GWADM. The error message error message gives additional information.
	Action	Perform the recommended action for the error message. If the message persists, contact BEA Customer Support.
3627	ERROR: unexpected error response from GWADM (error message)
	Description	The unexpected error identified in error message was received from GWADM while processing a Domains MIB request.
	Action	Perform the recommended action for the error message. If the message persists, contact BEA Customer Support.
3628	ERROR: unexpected error response from GWADM (error message)
	Description	The unexpected error identified in error message was received from GWADM while processing a Domains MIB request.
	Action	Perform the recommended action for the error message. If the message persists, contact BEA Customer Support.
3629	ERROR: call to GWADM failed tperrno(error number)
	Description	While processing a Domains MIB request, and unexpected error response was received from an internal call to the GWADM adminstration server. The tperrno error number given in error number details the error that occurred.
	Action	If the GWADM administration server is no longer running, restart it and repeat the request. Otherwise, if the message persists, contact BEA Customer Support.
3630	ERROR: attribute_name - must contain hex digits
	Description	The attribute_name attribute was specified as a hexadecimal string (starting with 0x or \\\\x), but a non-hexadecimal character was encountered in the string.
	Action	Enter hexadecimal characters in the attribute_name attribute and resubmit the request.
	See Also	DMIB(5)
3631	ERROR: attribute_name - must contain an even number of hex digits
	Description	The attribute attribute_name was specified as a hexadecimal strring (starting with 0x or \\\\x). This requires that there be an even number of characters following the prefix.
	Action	Correct the value to have an even number of hexadecimal characters and resubmit the MIB request.
	See Also	DMIB(5)
3632	ERROR: Cannot access $TUXCONFIG to validate T_DM_LOCAL class
	Description	While processing a T_DM_LOCAL class MIB request, the TUXCONFIG file cannot be accessed to validate attributes of the MIB request.
	Action	Check to make sure that the file exists and the directory structure is accessible. If the TUXCONFIG file does not exist, recreate it first before resubmitting the MIB request.
	See Also	DMIB(5)
3633	ERROR: ACL_POLICY(val) can only be either LOCAL or GLOBAL
	Description	While executing dmloadcf, the value for ACL_POLICY was not set to either LOCAL or GLOBAL.
	Action	Correct the value for ACL_POLICY and re-execute the command.
	See Also	dmconfig(5)
3635	ERROR: LOCAL_PRINCIPAL_NAME cannot be specified when ACL_POLICY is GLOBAL
	Description	While executing dmloadcf, the value for ACL_POLICY was set to GLOBAL and a LOCAL_PRINCIPAL_NAME was specified. This is not allowed.
	Action	Change the value for ACL_POLICY to LOCAL, or remove the LOCAL_PRINCIPAL_NAME and re-execute the command.
	See Also	dmconfig(5)
3637	ERROR: memory allocation failure
	Description	Failed to allocate memory necessary for processing the administrative request.
	Action	Make sure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. If message persists, contact BEA Customer Support with the exact error message.
	See Also	dmloadcf(1) and dmconfig(5)
3638	ERROR: XATMI_ENCODING can only be specified for REMOTE domain
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The XATMI_ENCODING parameter in the DM_OSITPX section is specified for the wrong type of domain. The XATMI_ENCODING parameter can only be specified for REMODE domains of type OSITPX.
	Action	Correct this entry in the DM_OSITPX section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3639	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_OSITPX section is an invalid value. The parameter values for the XATMI_ENCODING in the OSITPX section must be CAE, PRELIMINARY, OLTP_TM2200, or NATIVE_A_SERIES. The default parameter is CAE.
	Action	Correct this entry in the DM_OSITPX section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3640	ERROR: Invalid XATMI_ENCODING(encoding_name) for domain(domain_name)
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The XATMI_ENCODING parameter in the DM_OSITPX section is an invalid value. The parameter values for the XATMI_ENCODING in the OSITPX section must be CAE, PRELIMINARY, OLTP_TM2200, or NATIVE_A_SERIES. The default parameter is CAE.
	Action	Correct this entry in the DM_OSITPX section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3641	ERROR: Bad string value for NWADDR, failed parse
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The NWADDR parameter in the DM_OSITPX section has an invalid value.
	Action	Correct the NWADDR entry in the DM_OSITPX section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3642	ERROR: Invalid NWADDR(nwaddr_string) for domain(ositpx_domain_name)
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The NWADDR parameter in the DM_OSITPX section is an invalid value.
	Action	Correct the NWADDR entry in the DM_OSITPX section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3643	ERROR: Bad string value for P_SEL, failed parse
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The P_SEL parameter in the DM_OSITPX section has an invalid value.
	Action	Correct the P_SEL entry in the DM_OSITPX section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3644	ERROR: Invalid P_SEL(psel) for domain(ositpx_domain_name)
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The P_SEL parameter in the DM_OSITPX section is an invalid value.
	Action	Correct the P_SEL entry in the DM_OSITPX section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3645	ERROR: Bad string value for S_SEL, failed parse
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The S_SEL parameter in the DM_OSITPX section has an invalid value.
	Action	Correct the S_SEL entry in the DM_OSITPX section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3646	ERROR: Invalid S_SEL(ssel) for domain(ositpx_domain_name)
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The S_SEL parameter in the DM_OSITPX section is an invalid value.
	Action	Correct the S_SEL entry in the DM_OSITPX section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3647	ERROR: Bad string value for T_SEL, failed parse
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The T_SEL parameter in the DM_OSITPX section has an invalid value.
	Action	Correct the T_SEL entry in the DM_OSITPX section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3648	ERROR: Invalid T_SEL(tsel) for domain(ositpx_domain_name)
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The T_SEL parameter in the DM_OSITPX section is an invalid value.
	Action	Correct the T_SEL entry in the DM_OSITPX section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3649	ERROR: Bad string value for DNS_RESOLUTION, ignored
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The DNS_RESOLUTION parameter in the DM_OSITPX section has an invalid value.
	Action	Correct the DNS_RESOLUTION entry in the DM_OSITPX section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3650	ERROR: Invalid DNS_RESOLUTION(dns_code) for domain(ositpx_domain_name)
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The DNS_RESOLUTION parameter in the DM_OSITPX section is an invalid value.
	Action	Correct the DNS_RESOLUTION entry in the DM_OSITPX section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3651	ERROR: Bad domain type for MULTIPLEXING
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The MULTIPLEXING parameter in the DM_OSITPX section is specified for the wrong type of domain. The MULTIPLEXING parameter can only be specified for REMOTE domains of type OSITPX.
	Action	Correct this entry in the DM_OSITPX section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3652	ERROR: MULTIPLEXING can only be specified for REMOTE domain
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The MULTIPLEXING parameter in the DM_OSITPX section is specified for the wrong type of domain. The MULTIPLEXING parameter can only be specified for REMOTE domains of type OSITPX.
	Action	Correct this entry in the DM_OSITPX section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3653	ERROR: Invalid numeric value range
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The MULTIPLEXING parameter in the DM_OSITPX section is specified with an invalid value.
	Action	Correct this entry in the DM_OSITPX section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3654	ERROR: Value of MULTIPLEXING must be = 0
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The MULTIPLEXING parameter in the DM_OSITPX section must have zero as its only valid value.
	Action	Correct this entry in the DM_OSITPX section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3655	ERROR: Bad domain type for MINENCRYPTBITS
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The MINENCRYPTBITS parameter in the DM_OSITPX section is specified for the wrong type of domain. The MINENCRYPTBITS parameter can only be specified for REMOTE domains of type OSITPX.
	Action	Correct this entry in the DM_OSITPX section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3656	ERROR: MINENCRYPTBITS can only be specified for REMOTE domain
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The MINENCRYPTBITS parameter in the DM_OSITPX section is specified for the wrong type of domain. The MINENCRYPTBITS parameter can only be specified for REMOTE domains of type OSITPX.
	Action	Correct this entry in the DM_OSITPX section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3657	ERROR: Bad domain type for MAXENCRYPTBITS
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The MAXENCRYPTBITS parameter in the DM_OSITPX section is specified for the wrong type of domain. The MAXENCRYPTBITS parameter can only be specified for REMOTE domains of type OSITPX.
	Action	Correct this entry in the DM_OSITPX section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3658	ERROR: MAXENCRYPTBITS can only be specified for REMOTE domain
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The MAXENCRYPTBITS parameter in the DM_OSITPX section is specified for the wrong type of domain. The MAXENCRYPTBITS parameter can only be specified for REMOTE domains of type OSITPX.
	Action	Correct this entry in the DM_OSITPX section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3659	ERROR: Bad domain type for OPTIONS
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The OPTIONS parameter in the DM_OSITPX section is specified for the wrong type of domain. The OPTIONS parameter can only be specified for REMOTE domains of type OSITPX.
	Action	Correct this entry in the DM_OSITPX section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3660	ERROR: OPTIONS can only be specified for REMOTE domain
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The OPTIONS parameter in the DM_OSITPX section is specified for the wrong type of domain. The OPTIONS parameter can only be specified for REMOTE domains of type OSITPX.
	Action	Correct this entry in the DM_OSITPX section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3661	ERROR: Bad string value for OPTIONS, ignored
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The OPTIONS parameter in the DM_OSITPX section contains an invalid value.
	Action	Correct this entry in the DM_OSITPX section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3662	ERROR: Invalid OPTIONS(opt_value) for domain(ositpx_domain_name)
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The OPTIONS parameter in the DM_OSITPX section contains an invalid parameter string.
	Action	Correct this entry in the DM_OSITPX section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3663	ERROR: Invalid value
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The COUPLING parameter in the DM_EXPORT section is an invalid value. The parameter values for the COUPLING are either TIGHT or LOOSE.
	Action	Correct this entry in the DM_EXPORT section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3664	ERROR: Unknown COUPLING type <val>. Only TIGHT or LOOSE are recognized
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The COUPLING parameter in the DM_EXPORT section contains an invalid value.
	Action	Correct this entry in the DM_IMPORT section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3665	ERROR: Invalid value
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The AUTOPREPARE parameter in the DM_IMPORT section is an invalid value. The parameter values for the AUTOPREPARE are either Y or N.
	Action	Correct this entry in the DM_IMPORT section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3666	ERROR: AUTOPREPARE(value) can only be either Y or N
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The AUTOPREPARE parameter in the DM_IMPORT section contains an invalid value.
	Action	Correct this entry in the DM_IMPORT section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3667	ERROR: Invalid string value
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The NWADDR parameter in the DM_OSITPX section contains an invalid value.
	Action	Correct this entry in the DM_OSITPX section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3668	ERROR: NWADDR=<nsap> contains an invalid format (IC = indicator_code)
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The NWADDR parameter in the DM_OSITPX section contains an invalid value. Refer to the returned indicator_code to correct the format of the NWADDR. 1 = a comma was seen and the expected network type was invalid. 2 = the dotted IP address could not be parsed. It must be in the format a.a.a.a 3 = IP port number is out of range. 1 <= port number <= 65535 4 = The IP address value is out of range, format a.a.a.a where 1 <= a <= 255 5 = The IP port number could not be parsed. 6 = CONS, CLNS address size is too large. 7 = CONS, CLNS invalid hex value 8 = Invalid network type. Must be IP, CONS, or CLNS 9 = Maximum number of NSAP values reached.
	Action	Correct this entry in the DM_OSITPX section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3669	ERROR: Invalid string value
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The S/P/T_SEL parameter in the DM_OSITPX section is specified with an invalid value.
	Action	Correct this entry in the DM_OSITPX section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3670	ERROR: x_SEL=<badhex> contains an invalid hex value
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The S/P/T_SEL parameter in the DM_OSITPX section contains an invalid hex value.
	Action	Correct this entry in the DM_OSITPX section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3671	ERROR: Invalid value
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The TPSUT_TYPE parameter in the DM_IMPORT section is an invalid value. The parameter values for the TPSUT_TYPE are either NotSupplied or INTEGER or PrintableString.
	Action	Correct this entry in the DM_IMPORT section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3672	ERROR: Unknown TPSUT_TYPE type <Type>. Must be: NotSupplied, INTEGER or PRINTABLESTRING
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The TPSUT_TYPE parameter in the DM_IMPORT section is an invalid value. The parameter values for the TPSUT_TYPE are either NotSupplied or INTEGER or PrintableString.
	Action	Correct this entry in the DM_IMPORT section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3673	ERROR: Invalid value
	Description	The parameter values for the TPSUT_TYPE are either NotSupplied or INTEGER or PrintableString.
	Action	Correct this entry in the DM_IMPORT section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3674	ERROR: TPSUT_TYPE must be specified as: INTEGER or PRINTABLESTRING
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The TPSUT parameter in the DM_IMPORT section must be preceeded by a TPSUT_TYPE parameter of either INTEGER or PrintableString.
	Action	Correct this entry in the DM_IMPORT section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3675	ERROR: Invalid integer value
	Description	The parameter values for the TPSUT is specified as INTEGER however there are alphanumeric ASCII characters instead of numeric values.
	Action	Correct this entry in the DM_IMPORT section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3676	ERROR: REM_TPSUT <tpsut> is specified as INTEGER but contains a non-numeric ASCII value.
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The parameter values for the TPSUT is specified as INTEGER however there are alphanumeric ASCII characters instead of numeric values. Valid values for INTEGER are "0123456789-"
	Action	Correct this entry in the DM_IMPORT section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3677	ERROR: Invalid character value
	Description	The parameter values for the TPSUT is specified as PrintableString however there are non valid alphanumeric ASCII characters.
	Action	Correct this entry in the DM_IMPORT section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3678	ERROR: REM_TPSUT <tpsut> is specified as PRINTABLESTRING but contains a invalid ASCII value.
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The parameter values for the TPSUT is specified as PrintableString however there are invalid alphanumeric ASCII characters instead of numeric values. Valid values for PrintableString are 0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz '(),+-./=?
	Action	Correct this entry in the DM_IMPORT section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3680	ERROR: PRIORITY_TYPE(priority type) can only be either LOCAL_RELATIVE, LOCAL_ABSOLUTE, or GLOBAL
	Description	An error was detected while trying to load the dmconfig(5) file as a result of the dmloadcf command. The priority type type must be set to one of: LOCAL_RELATIVE, LOCAL_ABSOLUTE, or GLOBAL.
	Action	Correct the parameter specification in error and reload the configuration.
	See Also	dmconfig(5)
3681	ERROR: Can't find REMOTE DOMAIN entry in table
	Description	The GWADM administrative server received a request to dynamically update the REMOTE_DOMAIN entry. This message indicates that the update operation failed because it could not find the entry.
	Action	Contact BEA TUXEDO system Technical Support.
	See Also	dmconfig(5)
3682	ERROR: Can't find REMOTE DOMAIN entry by link
	Description	The GWADM administrative server received a request to dynamically update the REMOTE_DOMAIN entry. This message indicates that the update operation failed because it could not find the entry.
	Action	Contact BEA TUXEDO system Technical Support.
	See Also	dmconfig(5)
3684	ERROR: INPRIORITY must be within the range 1 and 100 inclusive when LOCAL_ABSOLUTE specified
	Description	An error was detected while trying to load the dmconfig(5) file as a result of the dmloadcf command. The priority INPRIORITY must be within the range 1 and 100 inclusive when the PRIORITY_TYPE has been set to LOCAL_ABSOLUTE.
	Action	Correct the parameter specification in error and reload the configuration.
	See Also	dmconfig(5)
3686	ERROR: INPRIORITY must be within the range -99 and 99 inclusive when LOCAL_RELATIVE or GLOBAL specified
	Description	An error was detected while trying to load the dmconfig(5) file as a result of the dmloadcf command. The priority INPRIORITY must be within the range 1 and 100 inclusive when the PRIORITY_TYPE has been set to LOCAL_RELATIVE or GLOBAL.
	Action	Correct the parameter specification in error and reload the configuration.
	See Also	dmconfig(5)
3688	ERROR: GLOBAL can only be specified when TYPE is TDOMAIN
	Description	While executing dmloadcf, the value for TYPE was not set to TDOMAIN. This is not allowed when PRIORITY_TYPE is set to GLOBAL.
	Action	Correct the parameter specification in error and reload the configuration.
	See Also	dmconfig(5)
3689	ERROR: Subtype specification not allowed in BUFTYPE="buffer type"
	Description	An error was detected while trying to load the dmconfig(5) file as a result of the dmloadcf command. The buffer type buffer type must not include a ":subtype" subtype specification.
	Action	Correct the parameter specification in error and reload the configuration.
	See Also	dmconfig(5)
3690	ERROR: Subtype specification not allowed in BUFTYPE="buffer type"
	Description	An error was detected while trying to load the dmconfig(5) file as a result of the dmloadcf command. The buffer type buffer type must not include a ":subtype" subtype specification.
	Action	Correct the parameter specification in error and reload the configuration.
	See Also	dmconfig(5)
3692	ERROR: CREDENTIAL_POLICY(CREDENTIAL_POLICY) can only be LOCAL or GLOBAL
	Description	An error was detected while trying to load the dmconfig(5) file as a result of the dmloadcf command. The credential policyCREDENTIAL_POLICY must be LOCAL or GLOBAL.
	Action	Correct the parameter specification in error and reload the configuration.
	See Also	dmconfig(5)
3693	ERROR: Bad domain type for XATMI_ENCODING
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The XATMI_ENCODING parameter in the DM_OSITPX section is specified for the wrong type of domain. The XATMI_ENCODING parameter can only be specified for REMOTE domains of type OSITPX.
	Action	Correct this entry in the DM_OSITPX section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3694	ERROR: NWADDR=<nsap> contains an invalid format (IC = indicator_code)
	Description	The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The NWADDR parameter in the DM_OSITPX section contains an invalid value. Refer to the returned indicator_code to correct the format of the NWADDR. 1 = a comma was seen and the expected network type was invalid. 2 = the dotted IP address could not be parsed. It must be in the format a.a.a.a 3 = IP port number is out of range. 1 <= port number <= 65535 4 = The IP address value is out of range, format a.a.a.a where 1 <= a <= 255 5 = The IP port number could not be parsed. 6 = CONS, CLNS address size is too large. 7 = CONS, CLNS invalid hex value 8 = Invalid network type. Must be IP, CONS, or CLNS 9 = Maximum number of NSAP values reached.
	Action	Correct this entry in the DM_OSITPX section and retry the operation.
	See Also	dmloadcf(1) and dmconfig(5)
3695	ERROR: Can't add OSITPX entry into table
	Description	The GWADM administrative server received a request to dynamically add an address for a domain. This message indicates that the add operation failed. Check surrounding messages for specifics.
	Action	Contact BEA TUXEDO system Technical Support.
	See Also	dmconfig(5)
3696	ERROR: Can't setup links from LOCAL DOMAIN entry to ositpx
	Description	The GWADM administrative server received a request to dynamically add a listening address for the local dom ain. After successfully adding the entry in the ADDRESS table, it links the new address to the list of addr esses already existing in the shared memory. This message indicates that the GWADM server could not set up the links.
	Action	Contact BEA TUXEDO system Technical Support.
	See Also	dmconfig(5)
3697	ERROR: Can't setup links from REMOTE DOMAIN entry to ositpx
	Description	The GWADM administrative server received a request to dynamically add a new address for a remote domain. Af ter successfully adding the entry in the ADDRESS table, it links the new address to the list of addresses a lready existing in the shared memory. This message indicates that the GWADM server could not set up the lin ks.
	Action	Contact BEA TUXEDO system Technical Support.
	See Also	dmconfig(5)
3698	ERROR: AET - must contain hex digits
	Description	The Application Entity Title parameter AET specified in the DM_OSITP section contains invalid hex digits.
	Action	Correct the AET parameter of the DM_OSITP section and retry the operation.
	See Also	dmconfig(5)
3699	ERROR: AET - must contain an even number of hex digits
	Description	An error was detected by the Domain Administrative server while processing a dynamic reconfiguration. The AET parameter specified was found to contain an odd number of hex digits. The AET parameter must contain and even number of hex digits.
	Action	Correct the value of the AET parameter and retry the operation.
	See Also	dmconfig(5)