4019
|
ERROR: Cannot get fieldid for fld
|
|
|
Description
|
A system error occurred in getting the field identifier when loading the routing entry into the Bulletin Board.
|
|
Action
|
Check the field tables to see if the field specified in the routing table is defined. Also, check your environment variables FLDTBLDIR and FIELDTBLS.
|
|
See Also
|
GWADM(5)
|
4023
|
ERROR: unknown type type to route on
|
|
|
Description
|
The BUFTYPE, type, for routing is unknown to the system. Currently, only VIEW and FML are supported buffer types for routing.
|
|
Action
|
Check your BUFTYPE definitions in the DM_ROUTING section of the DMCONFIG file. Only VIEW and FML can be specified. Then, re-load the BDMCONFIG file and re-boot the application.
|
|
See Also
|
dmconfig(5)
|
4024
|
ERROR: cannot use data, field type not identical for field fieldname
|
|
|
Description
|
The data routing entry cannot be used because the field type is not identical for field, fieldname, in the routing table.
|
|
Action
|
Check the field type, fieldname, in the DM_ROUTING section of the DMCONFIG file for consistency.
|
|
See Also
|
dmconfig(5)
|
4025
|
ERROR: Can't add ROUTSTRPOOL entry into table
|
|
|
Description
|
The GWADM administrative server couldn't successfully add a DM_ROUTING entry into shared memory. Check the surrounding messages for specifics.
|
|
Action
|
Correct the error and re-boot the application.
|
|
See Also
|
dmconfig(5)
|
4026
|
ERROR: Can't find ROUTSTRPOOL entry in table
|
|
|
Description
|
The GWADM administrative server couldn't successfully add a DM_ROUTING entry into shared memory. The server couldn't retrieve the entry it just added.
|
|
Action
|
Contact your BEA TUXEDO system Technical Support.
|
|
See Also
|
dmconfig(5)
|
4027
|
ERROR: Can't add ROUTSTRPOOL entry into table
|
|
|
Description
|
The GWADM administrative server couldn't successfully add a DM_ROUTING entry into shared memory. Check the surrounding messages for specifics.
|
|
Action
|
Correct the error and re-boot the application.
|
|
See Also
|
dmconfig(5)
|
4028
|
ERROR: Can't find ROUTSTRPOOL entry in table
|
|
|
Description
|
The GWADM administrative server couldn't successfully add a DM_ROUTING entry into shared memory. The server couldn't retrieve the entry it just added.
|
|
Action
|
Contact your BEA TUXEDO system Technical Support.
|
|
See Also
|
dmconfig(5)
|
4029
|
ERROR: Can't add RANGES entry into table
|
|
|
Description
|
The GWADM administrative server couldn't successfully add a DM_ROUTING entry into shared memory. Check the surrounding messages for specifics.
|
|
Action
|
Correct the error and re-boot the application.
|
|
See Also
|
dmconfig(5)
|
4030
|
ERROR: Can't find RANGES entry in table
|
|
|
Description
|
The GWADM administrative server couldn't successfully add a DM_ROUTING entry into shared memory. The server couldn't retrieve the entry it just added.
|
|
Action
|
Contact your BEA TUXEDO system Technical Support.
|
|
See Also
|
dmconfig(5)
|
4031
|
ERROR: dmroute failed, could not find routing criteria of routing_name for buffer type FML
|
|
|
Description
|
A routing_name was specified for a DM_REMOTE_SERVICES entry in the DMCONFIG file that does not appear in the DM_ROUTING section, and the standard FML routing function is used (which requires a matching DM_ROUTING entry).
|
|
Action
|
Correct and re-load the DMCONFIG file, or provide an application-specific routing function for FML typed buffers.
|
|
See Also
|
dmconfig(5)
|
4032
|
ERROR: dmroute failed, could not find routing criteria of routing_name for buffer type FML
|
|
|
Description
|
A routing_name was specified for a DM_REMOTE_SERVICES entry in the DMCONFIG file that does not appear in the DM_ROUTING section, and the standard FML routing function is used (which requires a matching DM_ROUTING entry).
|
|
Action
|
Correct and re-load the DMCONFIG file, or provide an application-specific routing function for FML typed buffers.
|
|
See Also
|
dmconfig(5)
|
4033
|
ERROR: dmroute failed, could not find routing criteria of routing_name for buffer type VIEW
|
|
|
Description
|
A routing_name was specified for a DM_REMOTE_SERVICES entry in the DMCONFIG file that does not appear in the DM_ROUTING section, and the standard VIEW routing function is used (which requires a matching DM_ROUTING entry).
|
|
Action
|
Correct and re-load the DMCONFIG file, or provide an application-specific routing function for VIEW typed buffers.
|
|
See Also
|
dmconfig(5)
|
4034
|
ERROR: dmroute failed, could not find routing criteria of routing_name for buffer type VIEW
|
|
|
Description
|
A routing_name was specified for a DM_REMOTE_SERVICES entry in the DMCONFIG file that does not appear in the DM_ROUTING section, and the standard VIEW routing function is used (which requires a matching DM_ROUTING entry).
|
|
Action
|
Correct and re-load the DMCONFIG file, or provide an application-specific routing function for VIEW typed buffers.
|
|
See Also
|
dmconfig(5)
|
4035
|
ERROR: unknown field type used for FML routing
|
|
|
Description
|
During data-dependent routing of an FML typed buffer, an unknown field type was encountered for the routing field. This should not occur during normal system operation.
|
|
Action
|
Contact your BEA TUXEDO system Technical Support.
|
|
See Also
|
dmconfig(5)
|
4036
|
ERROR: unknown field type used for VIEW routing
|
|
|
Description
|
During data-dependent routing of a VIEW typed buffer, an unknown field type was encountered for the routing field. This should not occur during normal system operation.
|
|
Action
|
Contact your BEA TUXEDO system Technical Support.
|
|
See Also
|
dmconfig(5)
|
4037
|
ERROR: Routing field value for 'service' not valid
|
|
|
Description
|
While doing data-dependent routing on an FML typed buffer for the specified service service, the routing field value did not match any of the ranges specified in the routing criteria and the criteria did not contain a wild-card pattern.
|
|
Action
|
Make sure the routing field value is valid. Correct the routing criteria in the RANGES value of the DMCONFIG file.
|
|
See Also
|
dmconfig(5)
|
4038
|
ERROR: Routing field value for 'service' not valid
|
|
|
Description
|
While doing data-dependent routing on a VIEW typed buffer for the specified service service, the routing field value did not match any of the ranges specified in the routing criteria and the criteria did not contain a wild-card pattern.
|
|
Action
|
Make sure the routing field value is valid. Correct the routing criteria in the RANGES value of the DMCONFIG file.
|
|
See Also
|
dmconfig(5)
|
4039
|
ERROR: more than one wild card in entry range
|
|
|
Description
|
More than one wild-card (*) range for the short routing data was specified in the data routing entry.
|
|
Action
|
Check your DMCONFIG file for multiple definitions of wild-card ranges for the short routing data. Only one wild-card range is allowed per routing entry, and it should be the last (ranges following it will be ignored).
|
|
See Also
|
dmconfig(5)
|
4040
|
ERROR: range values out of order upper_range < low_range
|
|
|
Description
|
The range values for the short routing data are out of order, that is, the upper range is less than the lower range value.
|
|
Action
|
Check routing range values for the short routing data in your DMCONFIG file. The lower range value must be less than or equal to the upper range value.
|
|
See Also
|
dmconfig(5)
|
4041
|
ERROR: more than one wild card in entry range
|
|
|
Description
|
More than one wild-card (*) range for the integer routing data was specified in the data routing entry.
|
|
Action
|
Check your DMCONFIG file for multiple definitions of wild-card ranges for the integer routing data. Only one wild-card range is allowed per routing entry, and it should be the last (ranges following it will be ignored).
|
|
See Also
|
dmconfig(5)
|
4042
|
ERROR: range values out of order upper_range < low_range
|
|
|
Description
|
The range values for the integer routing data are out of order, that is, the upper range is less than the lower range value.
|
|
Action
|
Check routing range values for the integer routing data in your DMCONFIG file. The lower range value must be less than or equal to the upper range value.
|
|
See Also
|
dmconfig(5)
|
4043
|
ERROR: more than one wild card in entry range
|
|
|
Description
|
More than one wild-card (*) range for the long routing data was specified in the data routing entry.
|
|
Action
|
Check your DMCONFIG file for multiple definitions of wild-card ranges for the long routing data. Only one wild-card range is allowed per routing entry, and it should be the last (ranges following it will be ignored).
|
|
See Also
|
dmconfig(5)
|
4044
|
ERROR: range values out of order upper_range < low_range
|
|
|
Description
|
The range values for the long routing data are out of order, that is, the upper range is less than the lower range value.
|
|
Action
|
Check routing range values for the long routing data in your DMCONFIG file. The lower range value must be less than or equal to the upper range value.
|
|
See Also
|
dmconfig(5)
|
4045
|
ERROR: more than one wild card in entry range
|
|
|
Description
|
More than one wild-card (*) range for the float routing data was specified in the data routing entry.
|
|
Action
|
Check your DMCONFIG file for multiple definitions of wild-card ranges for the float routing data. Only one wild-card range is allowed per routing entry, and it should be the last (ranges following it will be ignored).
|
|
See Also
|
dmconfig(5)
|
4046
|
ERROR: range values out of order upper_range < low_range
|
|
|
Description
|
The range values for the float routing data are out of order, that is, the upper range is less than the lower range value.
|
|
Action
|
Check routing range values for the float routing data in your DMCONFIG file. The lower range value must be less than or equal to the upper range value.
|
|
See Also
|
dmconfig(5)
|
4047
|
ERROR: more than one wild card in entry range
|
|
|
Description
|
More than one wild-card (*) range for the double routing data was specified in the data routing entry.
|
|
Action
|
Check your DMCONFIG file for multiple definitions of wild-card ranges for the double routing data. Only one wild-card range is allowed per routing entry, and it should be the last (ranges following it will be ignored).
|
|
See Also
|
dmconfig(5)
|
4048
|
ERROR: range values out of order upper_range < low_range
|
|
|
Description
|
The range values for the double routing data are out of order, that is, the upper range is less than the lower range value.
|
|
Action
|
Check routing range values for the double routing data in your DMCONFIG file. The lower range value must be less than or equal to the upper range value.
|
|
See Also
|
dmconfig(5)
|
4049
|
ERROR: more than one wild card in entry range
|
|
|
Description
|
More than one wild-card (*) range for the char routing data was specified in the data routing entry.
|
|
Action
|
Check your DMCONFIG file for multiple definitions of wild-card ranges for the char routing data. Only one wild-card range is allowed per routing entry, and it should be the last (ranges following it will be ignored).
|
|
See Also
|
dmconfig(5)
|
4050
|
ERROR: char range with MAX as lower value has values out of order
|
|
|
Description
|
If MAX is specified for the char lower routing range, then its corresponding upper routing range must also be specified as MAX, that is, MAX-MAX:remote_domain_name.
|
|
Action
|
Check the char routing range in the DM_ROUTING section of the DMCONFIG file. If MAX is specified for the lower range, then its corresponding upper range must be MAX.
|
|
See Also
|
dmconfig(5)
|
4051
|
ERROR: char range with MIN as upper value has values out of order
|
|
|
Description
|
If MIN is specified for the char lower routing range, then its corresponding upper routing range must also be specified as MIN, that is, MIN-MIN:remote_domain_name.
|
|
Action
|
Check the char routing range in the DM_ROUTING section of the DMCONFIG file. If MIN is specified for the lower range, then its corresponding upper range must be MIN.
|
|
See Also
|
dmconfig(5)
|
4052
|
ERROR: range values out of order upper_range < low_range
|
|
|
Description
|
The range values for the char routing data are out of order, that is, the upper range is less than the lower range value.
|
|
Action
|
Check routing range values for the char routing data in your DMCONFIG file. The lower range value must be less than or equal to the upper range value.
|
|
See Also
|
dmconfig(5)
|
4053
|
ERROR: more than one wild card in entry range
|
|
|
Description
|
More than one wild-card (*) range for the string routing data was specified in the data routing entry.
|
|
Action
|
Check your DMCONFIG file for multiple definitions of wild-card ranges for the string routing data. Only one wild-card range is allowed per routing entry, and it should be the last (ranges following it will be ignored).
|
|
See Also
|
dmconfig(5)
|
4054
|
ERROR: range values out of order for the string routing data
|
|
|
Description
|
The range values for the string routing data are out of order, that is, the upper range is less than the lower range value.
|
|
Action
|
Check routing range values for the string routing data in your DMCONFIG file. The lower range value must be less than or equal to the upper range value.
|
|
See Also
|
dmconfig(5)
|
4055
|
ERROR: more than one wild card in entry range
|
|
|
Description
|
More than one wild-card (*) range for the carray routing data was specified in the data routing entry.
|
|
Action
|
Check your DMCONFIG file for multiple definitions of wild-card ranges for the carray routing data. Only one wild-card range is allowed per routing entry, and it should be the last (ranges following it will be ignored).
|
|
See Also
|
dmconfig(5)
|
4056
|
ERROR: range values out of order for the carray routing data
|
|
|
Description
|
The range values for the carray routing data are out of order, that is, the upper range is less than the lower range value.
|
|
Action
|
Check routing range values for the carray routing data in your DMCONFIG file. The lower range value must be less than or equal to the upper range value.
|
|
See Also
|
dmconfig(5)
|
4057
|
ERROR: more than one wild card in entry range
|
|
|
Description
|
More than one wild-card (*) range for the decimal routing data was specified in the data routing entry.
|
|
Action
|
Check your DMCONFIG file for multiple definitions of wild-card ranges for the decimal routing data. Only one wild-card range is allowed per routing entry, and it should be the last (ranges following it will be ignored).
|
|
See Also
|
dmconfig(5)
|
4058
|
ERROR: range values out of order for the decimal routing data
|
|
|
Description
|
The range values for the carray routing data are out of order, that is, the upper range is less than the lower range value.
|
|
Action
|
Check routing range values for the carray routing data in your DMCONFIG file. The lower range value must be less than or equal to the upper range value.
|
|
See Also
|
dmconfig(5)
|
4059
|
ERROR: unknown field type given
|
|
|
Description
|
An unknown field type was specified in the data routing entry.
|
|
Action
|
Check the field types specified in the DM_ROUTING section of the DMCONFIG file.
|
|
See Also
|
dmconfig(5)
|
4060
|
ERROR: expected colon to separate remote domain name range
|
|
|
Description
|
Within a range and a remote domain pair, the range is separated from the remote domain name by a colon (:) in the DM_ROUTING section of the DMCONFIG file.
|
|
Action
|
Check the range and remote domain name specified in the DM_ROUTING section of the DMCONFIG file. A colon (:) is expected to separate the range and the remote domain name.
|
|
See Also
|
dmconfig(5)
|
4061
|
ERROR: expected comma after remote domain name domain_name, string
|
|
|
Description
|
Within a range and a remote domain name pair, a comma (,) is expected after remote domain name in the DM_ROUTING section of the DMCONFIG file.
|
|
Action
|
Check the range and remote domain name specified in the DM_ROUTING section of the DMCONFIG file. A comma (,) is expected after the remote domain name.
|
|
See Also
|
dmconfig(5)
|
4062
|
ERROR: expecting keyword MAX
|
|
|
Description
|
The keyword MAX is expected to indicate the maximum value for the data type of the associated field in the DM_ROUTING section of the DMCONFIG file.
|
|
Action
|
Check the range and the remote domain name specified in the DM_ROUTING section of the DMCONFIG file. The keyword MAX should be specified to indicate the maximum value for the data type of the associated field.
|
|
See Also
|
dmconfig(5)
|
4063
|
ERROR: expecting keyword MIN
|
|
|
Description
|
The keyword MIN is expected to indicate the minimum value for the data type of the associated field in the DM_ROUTING section of the DMCONFIG file.
|
|
Action
|
Check the range and the remote domain name specified in the DM_ROUTING section of the DMCONFIG file. The keyword MIN should be specified to indicate the minimum value for the data type of the associated field.
|
|
See Also
|
dmconfig(5)
|
4064
|
ERROR: expecting keyword MIN or MAX
|
|
|
Description
|
The keyword MAX or MIN is expected to indicate the maximum or minimum value for the data type of the associated field in the DM_ROUTING section of the DMCONFIG file.
|
|
Action
|
Check the range and the remote domain name specified in the DM_ROUTING section of the DMCONFIG file. The keyword MAX or MIN should be specified to indicate the maximum or minimum value for the data type of the associated field.
|
|
See Also
|
dmconfig(5)
|
4065
|
ERROR: cannot have a '-' in front of MAX or MIN
|
|
|
Description
|
The routing range cannot have a '-' sign in front of the MAX or MIN value.
|
|
Action
|
Check the routing data in the DM_ROUTING section of the DMCONFIG file. Remove any '-' sign in front of the MAX or MIN value.
|
|
See Also
|
dmconfig(5)
|
4066
|
ERROR: value out of range for a short value
|
|
|
Description
|
The routing value for a short routing data is out of range.
|
|
Action
|
Check routing range values for the short routing data in the DM_ROUTING section of the DMCONFIG file.
|
|
See Also
|
dmconfig(5)
|
4067
|
ERROR: value out of range for an int value
|
|
|
Description
|
The routing value for an integer routing data is out of range.
|
|
Action
|
Check routing range values for the integer routing data in the DM_ROUTING section of the DMCONFIG file.
|
|
See Also
|
dmconfig(5)
|
4068
|
ERROR: value out of range for a long value
|
|
|
Description
|
The routing value for a long routing data is out of range.
|
|
Action
|
Check routing range values for the long routing data in the DM_ROUTING section of the DMCONFIG file.
|
|
See Also
|
dmconfig(5)
|
4069
|
ERROR: cannot have a '-' and a '+' sign in front of a number
|
|
|
Description
|
The routing range cannot have a '-' and '+' sign in front of a number.
|
|
Action
|
Check the routing range data in the DM_ROUTING section of the DMCONFIG file. If a '-' and a '+' sign are both in front of a number, remove the '+' sign.
|
|
See Also
|
dmconfig(5)
|
4070
|
ERROR: cannot have a '-' in front of MAX or MIN
|
|
|
Description
|
While loading all of the information that is in the BDMCONFIG file into the shared memory, the calling process failed to get a data routing entry. The failure occurred while parsing a range string into data based on the field type information of one of the entries in the DM_ROUTING section of the configuration file. The calling process was unable to create the data routing entry.
|
|
Action
|
Make sure the RANGES parameter in the DM_ROUTING section of the DMCONFIG file is valid. The range strings may not contain a '-' in front of MIN or MAX.
|
|
See Also
|
dmconfig(5)
|
4071
|
ERROR: expecting a ' ', '+', '-' or number after 'e/E' in float/double
|
|
|
Description
|
A '', '+', '-' or number after 'e' or 'E' is expected for float or double routing values.
|
|
Action
|
Check the routing range values of the float and double in the DM_ROUTING section of the DMCONFIG file.
|
|
See Also
|
dmconfig(5)
|
4072
|
ERROR: value out of range for a float value
|
|
|
Description
|
The routing value for a float routing data is out of range.
|
|
|
Action
|
Check routing range values for the float routing data in the DM_ROUTING section of the DMCONFIG file.
|
|
|
See Also
|
dmconfig(5)
|
4073
|
ERROR: value out of range for a double value
|
|
|
Description
|
The routing value for a double routing data is out of range.
|
|
|
Action
|
Check routing range values for the double routing data in the DM_ROUTING section of the DMCONFIG file.
|
|
|
See Also
|
dmconfig(5)
|
4074
|
ERROR: cannot have a '-' in front of MAX or MIN
|
|
|
Description
|
The routing range cannot have a '-' and '+' sign in front of the MAX or MIN value.
|
|
|
Action
|
Check the routing range data in the DM_ROUTING section of the DMCONFIG file. Remove any '-' sign in front of the MAX or MIN value.
|
|
|
See Also
|
dmconfig(5)
|
4075
|
ERROR: expected single quote to begin char routing data value
|
|
Description
|
A single quote (') is expected at the beginning of char routing data.
|
|
Action
|
Check routing range values for the char routing data in the DM_ROUTING section of the DMCONFIG file. A char routing data must begin with a single quote (').
|
|
See Also
|
dmconfig(5)
|
4076
|
ERROR: expected single quote to end char routing data value
|
|
|
Description
|
A single quote (') is expected at the end of char routing data.
|
|
Action
|
Check routing range values for the char routing data in the DM_ROUTING section of the DMCONFIG file. A char routing data must be ended with a single quote (').
|
|
See Also
|
dmconfig(5)
|
4077
|
ERROR: cannot have a '-' in front of MAX or MIN
|
|
|
Description
|
The routing range cannot have a '-' and '+' sign in front of the MAX or MIN value.
|
|
Action
|
Check the routing range data in the DM_ROUTING section of the DMCONFIG file. Remove any '-' sign in front of the MAX or MIN value.
|
|
See Also
|
dmconfig(5)
|
4078
|
ERROR: expected single quote for string/carray routing data value
|
|
|
Description
|
A single quote (') is expected for string and carray routing data.
|
|
Action
|
Check routing range values for the string and carray routing data in the DM_ROUTING section of the DMCONFIG file. The string and carray routing data must be within single quotes (').
|
|
See Also
|
dmconfig(5)
|
4079
|
ERROR: not enough string pool space available for routing info
|
|
|
Description
|
There is not enough routing free string pool space in the shared memory when filling the data section with string and carray data.
|
|
Action
|
This is s system error, contact your BEA TUXEDO system Technical Support.
|
|
See Also
|
dmconfig(5)
|
4080
|
ERROR: cannot have a '-' and a '+' sign in front of a number
|
|
|
Description
|
The routing range cannot have a '-' and '+' sign in front of a number.
|
|
Action
|
Check the routing range data in the DM_ROUTING section of the DMCONFIG file. If a '-' and a '+' sign are both in front of a number, remove the '+' sign.
|
|
See Also
|
dmconfig(5)
|
4081
|
ERROR: cannot have a '-' in front of MAX or MIN
|
|
|
Description
|
The routing range cannot have a '-' and '+' sign in front of the MAX or MIN value.
|
|
Action
|
Check the routing range data in the DM_ROUTING section of the DMCONFIG file. Remove any '-' sign in front of the MAX or MIN value.
|
|
See Also
|
dmconfig(5)
|
4082
|
ERROR: invalid format for decimal
|
|
|
Description
|
The routing range packed decimal data are specified incorrectly.
|
|
Action
|
Check routing range packed decimal data in the DM_ROUTING section of the DMCONFIG file. The decimal data must be in the correct format.
|
|
See Also
|
dmconfig(5)
|
4083
|
ERROR: discovered NULL character in string routing data value
|
|
|
Description
|
A NULL character is found in the string routing data.
|
|
Action
|
Check the string routing data for NULL characters in the DM_ROUTING section of the DMCONFIG file. A string value is terminated with a NULL character.
|
|
See Also
|
dmconfig(5)
|
4084
|
ERROR: Routing field for 'routing_field' null
|
|
|
Description
|
During data-dependent routing for an FML buffer, the specified 'routing_field' value in the FML buffer was null.
|
|
Action
|
Make sure the routing field is correctly set in the FML buffer.
|
|
See Also
|
dmconfig(5)
|
4085
|
ERROR: Field type of buffer does not match routing criteria type
|
|
|
Description
|
During data-dependent routing of an FML typed buffer, the field type for the routing field didn't match the field type for the typed buffers. This should not occur during normal system operation.
|
|
Action
|
Contact your BEA TUXEDO system Technical Support.
|
|
See Also
|
dmconfig(5)
|
4086
|
ERROR: Illegal offset value for routing_field
|
|
|
Description
|
Data-dependent routing failed for a VIEW buffer because the offset for the routing field is invalid. This should not occur during normal system operation.
|
|
Action
|
Contact your BEA TUXEDO system Technical Support.
|
|
See Also
|
dmconfig(5)
|
4087
|
ERROR: Routing field for 'routing_field' null
|
|
|
Description
|
During data-dependent routing for a VIEW buffer, the specified 'routing_field' value in the VIEW buffer was null.
|
|
Action
|
Make sure the routing field is correctly set in the VIEW buffer.
|
|
See Also
|
dmconfig(5)
|
4089
|
ERROR: _dmcf_OLD_open failed: Can't open DM_PASSWORDS section
|
|
|
Description
|
When the GWADM server is booted, it requests the configuration for its domain from the DMADM server. The DMADM server then retrieves all the entries from the BDMCONFIG file that are pertinent to this domain. This message indicates that DMADM couldn't open the BDMCONFIG file for reading the DM_PASSWORDS section.
|
|
Action
|
Make sure that the BDMCONFIG file still exists and is accessible by the DMADM server, and re-start the application.
|
|
See Also
|
dmconfig(5)
|
4090
|
ERROR: _dmcf_OLD_open failed: Can't open DM_PASSWORDS section
|
|
|
Description
|
When the GWADM server is booted, it requests the configuration for its domain from the DMADM server. The DMADM server then retrieves all the entries from the BDMCONFIG file that are pertinent to this domain. This message indicates that DMADM couldn't open the BDMCONFIG file for reading the DM_PASSWORDS section.
|
|
Action
|
Make sure that the BDMCONFIG file still exists and is accessible by the DMADM server, and re-start the application.
|
|
See Also
|
dmconfig(5)
|
4091
|
ERROR: Can't add PASSWORD entry into table
|
|
|
Description
|
When the GWADM administrative server is booted, it fetches the configuration information for its domain from the DMADM administrative server. It then loads the entries into shared memory. This message indicates that it couldn't load a PASSWORD into shared memory. This should only occur if the GWADM administrative server couldn't find free space in the existing shared memory segments and it couldn't create additional shared memory segments to add the new entry.
|
|
Action
|
Change the UNIX IPC parameters, if needed, make the new kernel, reboot the machine, and then restart the application.
|
|
See Also
|
dmconfig(5)
|
4092
|
ERROR: _dmcf_OLD_open failed: Can't open DM_RESOURCES section
|
|
|
Description
|
When the GWADM server is booted, it requests the configuration for its domain from the DMADM server. The DMADM server then retrieves all the entries from the BDMCONFIG file that are pertinent to this domain. This message indicates that DMADM couldn't open the BDMCONFIG file for reading the DM_RESOURCES section.
|
|
Action
|
Make sure that the BDMCONFIG file still exists and is accessible by the DMADM server, and re-start the application.
|
|
See Also
|
dmconfig(5)
|
4093
|
ERROR: Can't add RESOURCES entry into table
|
|
|
Description
|
When the GWADM administrative server is booted, it fetches the configuration information for its domain from the DMADM administrative server. It then loads the entries into shared memory. This message indicates that it couldn't load the DM_RESOURCES info into shared memory. This should only occur if the shared memory is corrupted.
|
|
Action
|
Contact your BEA TUXEDO system Technical Support.
|
|
See Also
|
dmconfig(5)
|