CMDGW Messages 3100-3199
|
|
|
3100
ERROR: Can't find REMOTE SERVICE entry in table
Description
The GWADM administrative server received a request to dynamically update a REMOTE_SERVICE entry. This message indicates that the update operation failed because it could not find the entry. Check the surrounding messages for specifics.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
3101
ERROR: Can't setup links from REMOTE SERVICE entry to routing/rdomentry
Description
The GWADM administrative server received a request to dynamically update a REMOTE_SERVICE entry. This message indicates that the update operation failed because it could not set up the links from the new (updated) entry to the RDOM and/or ROUTING entry.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
3102
ERROR: Can't add ACL entry into table
Description
The GWADM administrative server received a request to dynamically add an ACL entry. This message indicates that the add operation failed. Check surrounding messages for specifics.
Action
Correct the error and re-issue the request.
See Also
dmconfig(5)
3103
ERROR: Can't find ACL entry in table
Description
The GWADM administrative server received a request to dynamically update an ACL entry. This message indicates that the update operation failed because it could not find the entry in the ACL table.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
3104
ERROR: Can't delete ACL entry from table
Description
The GWADM administrative server received a request to dynamically delete an ACL entry. This message indicates that the delete operation failed because it could not find the entry in the ACL table.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
3105
ERROR: Can't add ROUTING entry into table
Description
The GWADM administrative server received a request to dynamically add a ROUTING entry. This message indicates that the add operation failed. Check surrounding messages for specifics.
Action
Correct the error and re-issue the request.
See Also
dmconfig(5)
3106
ERROR: Can't delete ROUTING entry from table
Description
The GWADM administrative server received a request to dynamically delete a ROUTING entry. This message indicates that the delete operation failed because it could not find the entry.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
3107
ERROR: Can't delete RANGES entry from table
Description
The GWADM administrative server received a request to dynamically delete a ROUTING entry from the shared memory. The server was able to delete the entry from the ROUTING table. However, it was not able to delete the corresponding entries in the RANGES table.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
3108
ERROR: Can't delete ROUTSTRPOOL entry from table
Description
The GWADM administrative server received a request to dynamically delete a ROUTING entry from the shared memory. The server was able to delete the entry from the ROUTING table and also succeeded in deleting entries in RANGES table. However, it was not able to delete the corresponding entry in the ROUTSTRPOOL table.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
3109
ERROR: Can't add ROUTING entry into table
Description
The GWADM administrative server received a request to dynamically update a ROUTING entry. The old entry is first deleted and the new entry added in its place. This message indicates that the add operation failed after successfully deleting the old entry. Check surrounding messages for specifics.
Action
Correct the error and do an ADD operation this time.
See Also
dmconfig(5)
3110
ERROR: Can't add PASSWORD entry into table
Description
The GWADM administrative server received a request to dynamically add a PASSWORD entry. This message indicates that the add operation failed. Check surrounding messages for specifics.
Action
Correct the error and re-issue the request.
See Also
dmconfig(5)
3111
ERROR: Can't delete PASSWORD entry from table
Description
The GWADM administrative server received a request to dynamically delete a PASSWORD entry for a remote domain. This message indicates that the delete operation failed. Check the surrounding messages for specifics.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
3112
ERROR: Can't delete PASSWORD entry from table
Description
The GWADM administrative server received a request to dynamically update a PASSWORD entry. The old entry is deleted and the new entry is added. This message indicates that GWADM could not delete the old entry.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
3113
ERROR: Can't add PASSWORD entry into table
Description
The GWADM administrative server received a request to dynamically update a PASSWORD entry. The old entry is deleted and the new entry is added. This message indicates that GWADM could not add the new entry after deleting the old entry.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
3114
ERROR: Can't add RDOMSEC entry into table
Description
The Gateway Administrative server detected an internal error while trying to process a request. An RDOMSEC entry could not be added.
Action
This is an internal error with no associated user action. If the message persists, contact BEA TUXEDO system Technical Support with the exact error message.
See Also
GWADM(5)
3116
ERROR: Can't setup principal-appkey mappings
Description
The Gateway Administrative server detected an internal error while trying to process a request.
Action
This is an internal error with no associated user action. If the message persists, contact BEA TUXEDO system Technical Support with the exact error message.
See Also
GWADM(5)
3117
ERROR: Can't delete RDOMSEC entry from table
Description
The Gateway Administrative server detected an internal error while trying to process a request.
Action
This is an internal error with no associated user action. If the message persists, contact BEA TUXEDO system Technical Support with the exact error message.
See Also
GWADM(5)
3118
ERROR: Can't delete RDOMSEC entry from table for update
Description
The Gateway Administrative server detected an internal error while trying to process a request.
Action
This is an internal error with no associated user action. If the message persists, contact BEA TUXEDO system Technical Support with the exact error message.
See Also
GWADM(5)
3119
ERROR: Can't add RDOMSEC entry into table
Description
The Gateway Administrative server detected an internal error while trying to process a request.
Action
This is an internal error with no associated user action. If the message persists, contact BEA TUXEDO system Technical Support with the exact error message.
See Also
GWADM(5)
3120
ERROR: Can't add RDOMUSR entry into table
Description
The Gateway Administrative server detected an internal error while trying to process a request.
Action
This is an internal error with no associated user action. If the message persists, contact BEA TUXEDO system Technical Support with the exact error message.
See Also
GWADM(5)
3122
ERROR: Can't delete RDOMUSR entry from table
Description
The Gateway Administrative server detected an internal error while trying to process a request.
Action
This is an internal error with no associated user action. If the message persists, contact BEA TUXEDO system Technical Support with the exact error message.
See Also
GWADM(5)
3123
ERROR: Can't delete RDOMUSR entry from table for update
Description
The Gateway Administrative server detected an internal error while trying to process a request.
Action
This is an internal error with no associated user action. If the message persists, contact BEA TUXEDO system Technical Support with the exact error message.
See Also
GWADM(5)
3124
ERROR: Can't add RDOMUSR entry into table for update
Description
The Gateway Administrative server detected an internal error while trying to process a request.
Action
This is an internal error with no associated user action. If the message persists, contact BEA TUXEDO system Technical Support with the exact error message.
See Also
GWADM(5)
3125
ERROR: Cannot allocate memory to retrieve service table entries
Description
An attempt dynamically to allocate memory from the operating system using malloc failed.
Action
Make sure that 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.
See Also
dmconfig(5)
3126
ERROR: Can't have more than one GWADM in a given group
Description
The Gateway Administrative server detected an error while trying to initialize. A group with more than one GWADM server was found. A maximum of 1 GWADM server is allowed per group in the ubbconfig(1) file.
Action
Correct the configuration such that only one GWADM is defined per group.
See Also
GWADM(5)
3127
ERROR: Restarting GWADM server can't attach the shared memory segment(s) created when first booted
Description
A re-startable GWADM administrative server terminated abnormally. An attempt to attach to the shared memory segments it created earlier failed when it tried to start again.
Action
Make sure that the shared memory segments have not been removed and the permissions are correct.
See Also
dmconfig(5)
3128
ERROR: Not compatible_gwadm: Can't interpret internet type of address(es)
Description
The Domain Administrative server detected an error while trying to register the Gateway Administrative server for the first time. An incompatible network address type was found in the DM_TDOMAIN section of the bdmconfig file.
Action
Correct the DM_TDOMAIN section of the configuration file such that the NWADDR parameter for the domain gateway contains an address which is not an internet type of address.
See Also
dmconfig(5)
3129
ERROR: Can't read OSITPX section of BDMCONFIG file (file)
Description
When the DMADM administrative server is booted, it manages a BDMCONFIG file. When the GWADM administrative servers are started, they request configuration information for a specific local domain from DMADM. This error message indicates that DMADM could not read the DM_OSITP section of the BDMCONFIG file. This indicates that the file is probably corrupted.
Action
Shut down the application and re-generate the BDMCONFIG file.
See Also
dmconfig(5)
3130
ERROR: BDMCONFIG environment variable not set
Description
When the DMADM administrative server is booted, it manages a BDMCONFIG file. The environment variable must be set to an existing BDMCONFIG file.
Action
Set and export the BDMCONFIG environment variable and restart the DMADM server.
See Also
dmconfig(5)
3131
ERROR: BDMCONFIG file (file) doesn't exist
Description
When the DMADM administrative server is booted, it manages a BDMCONFIG file. The BDMCONFIG file, however, does not exist or is not accessible.
Action
Set a valid value for the BDMCONFIG environment variable and restart the DMADM server.
See Also
dmconfig(5)
3132
ERROR: Can't read LOCAL DOMAINS section of BDMCONFIG file (file)
Description
When the DMADM administrative server is booted, it manages a BDMCONFIG file. When the GWADM administrative servers are started, they request configuration information for a specific local domain from DMADM. This error message indicates that DMADM could not read the DM_LOCAL_DOMAINS section of the BDMCONFIG file. This indicates that the file is probably corrupted.
Action
Shut down the application and re-generate the BDMCONFIG file.
See Also
dmconfig(5)
3133
ERROR: Can't read REMOTE DOMAINS section of BDMCONFIG file (file)
Description
When the DMADM administrative server is booted, it manages a BDMCONFIG file. When the GWADM administrative servers are started, they request configuration information for a specific local domain from DMADM. This error message indicates that DMADM could not read the DM_REMOTE_DOMAINS section of the BDMCONFIG file. This indicates that the file is probably corrupted.
Action
Shut down the application and re-generate the BDMCONFIG file.
See Also
dmconfig(5)
3134
ERROR: Can't read TDOMAIN section of BDMCONFIG file (file)
Description
When the DMADM administrative server is booted, it manages a BDMCONFIG file. When the GWADM administrative servers are started, they request configuration information for a specific local domain from DMADM. This error message indicates that DMADM could not read the DM_TDOMAIN section of the BDMCONFIG file. This indicates that the file is probably corrupted.
Action
Shut down the application and re-generate the BDMCONFIG file.
See Also
dmconfig(5)
3135
ERROR: Can't read OSITP section of BDMCONFIG file (file)
Description
When the DMADM administrative server is booted, it manages a BDMCONFIG file. When the GWADM administrative servers are started, they request configuration information for a specific local domain from DMADM. This error message indicates that DMADM could not read the DM_OSITP section of the BDMCONFIG file. This indicates that the file is probably corrupted.
Action
Shut down the application and re-generate the BDMCONFIG file.
See Also
dmconfig(5)
3136
ERROR: Can't read LOCAL SERVICES section of BDMCONFIG file (file)
Description
When the DMADM administrative server is booted, it manages a BDMCONFIG file. When the GWADM administrative servers are started, they request configuration information for a specific local domain from DMADM. This error message indicates that DMADM could not read the DM_LOCAL_SERVICES section of the BDMCONFIG file. This indicates that the file is probably corrupted.
Action
Shut down the application and re-generate the BDMCONFIG file.
See Also
dmconfig(5)
3138
ERROR: Can't read ROUTING section of BDMCONFIG file (file)
Description
When the DMADM administrative server is booted, it manages a BDMCONFIG file. When the GWADM administrative servers are started, they request configuration information for a specific local domain from DMADM. This error message indicates that DMADM could not read the DM_ROUTING section of the BDMCONFIG file. This indicates that the file is probably corrupted.
Action
Shut down the application and re-generate the BDMCONFIG file.
See Also
dmconfig(5)
3139
ERROR: Can't read ACCESS_CONTROL section of BDMCONFIG file (file)
Description
When the DMADM administrative server is booted, it manages a BDMCONFIG file. When the GWADM administrative servers are started, they request configuration information for a specific local domain from DMADM. This error message indicates that DMADM could not read the DM_ACCESS_CONTROL section of the BDMCONFIG file. This indicates that the file is probably corrupted.
Action
Shut down the application and re-generate the BDMCONFIG file.
See Also
dmconfig(5)
3140
ERROR: Cannot find master without BB
Description
An attempt was made to find the acting MASTER machine, that is, the machine where the DBBL is currently running, by a process that has not yet joined the application as a client or server.
Action
Contact BEA TUXEDO system Technical Support.
See Also
dmconfig(5)
3141
ERROR: Cannot allocate memory for registering GWADM's
Description
An attempt dynamically to allocate memory from the operating system using malloc failed.
Action
Make sure that 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.
See Also
dmconfig(5)
3142
ERROR: Cannot send config to GWADM group=grp
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)
3143
ERROR: Cannot register GWADM of group grp
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)
3144
ERROR: Cannot send config section section_num to GWADM group=grp
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)
3145
ERROR: Cannot un-register GWADM group=grp
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)
3146
ERROR: Cannot allocate memory for registering GWADM's
Description
An attempt dynamically to allocate memory from the operating system using malloc failed.
Action
Make sure that 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.
See Also
dmconfig(5)
3147
ERROR: Failed to perform dynamic reconfiguration of the application
Description
While performing dynamic re-configuration for a local domain, the DMADM administrative server encountered an error. Check surrounding messages for specifics.
Action
Correct the error and re-issue the request.
See Also
dmconfig(5)
3148
ERROR: Can't send dynamic re-configuration changes to GWADM server(s)
Description
The DMADM administrative server received a request for dynamic re-configuration of the application. It successfully made the changes to the BDMCONFIG file but failed to propagate the changes to GWADM server(s).
Action
Check if any GWADM server terminated abnormally. Restart any GWADM servers that died. The changes will be picked up by the restarting GWADMs.
See Also
dmconfig(5)
3149
INFO: BDMCONFIG environment variable not set. Using $APPDIR/BDMCONFIG
Description
When the DMADM administrative server is booted, it manages a BDMCONFIG file. The environment variable should be set to an existing BDMCONFIG file. Since it is not set, the program will attempt to use $APPDIR/BDMCONFIG.
Action
No action required.
See Also
dmconfig(5)
3150
ERROR: Can't read PASSWORDS section of BDMCONFIG file (name)
Description
When the DMADM administrative server is booted, it manages a BDMCONFIG file. This error message indicates that DMADM could not read the PASSWORDS section of the BDMCONFIG file. This indicates that the file is probably corrupted.
Action
Shut down the application and re-generate the BDMCONFIG file.
See Also
dmconfig(5)
3151
ERROR: Running multiple DMADM servers in the same application not allowed
Description
An attempt was made to boot more than one DMADM server. This is not supported.
Action
No action required.
See Also
dmconfig(5)
3152
ERROR: Cannot set environment variable BDMCONFIG
Description
The BDMCONFIG environment variable is not set in the environment. The program attempted to use a default value of $APPDIR/BDMCONFIG but could not get $APPDIR from the environment.
Action
Make sure that $APPDIR is set in the environment or set $BDMCONFIG in the environment explicitly.
See Also
dmconfig(5)
3153
INFO: $BDMCONFIG file does not exist. Creating $BDMCONFIG
Description
When the DMADM administrative server is booted, it manages a BDMCONFIG file. This file does not exist so a default configuration file will be created using dmloadcf.
Action
No action required. You can explicitly create a configuration using dmloadcf(1).
See Also
dmloadcf(1), dmconfig(5)
3154
ERROR: Can't read SNADOM section of BDMCONFIG file (file)
Description
When the DMADM administrative server is booted, it manages a BDMCONFIG file. This error message indicates that DMADM could not read the DM_SNADOM section of the BDMCONFIG file. This indicates that the file is probably corrupted or not properly configured.
Action
Shut down the application and re-generate the BDMCONFIG file.
See Also
dmconfig(5)
3155
ERROR: Can't read RDOMSEC section of BDMCONFIG file (file)
Description
When the DMADM administrative server is booted, it manages a BDMCONFIG file. When the GWADM administrative servers are started, they request configuration information for a specific local domain from DMADM. This error message indicates that DMADM could not read the DM_RDOMSEC section of the BDMCONFIG file. This indicates that the file is probably corrupted or not properly configured.
Action
Shut down the application and re-generate the BDMCONFIG file.
See Also
dmconfig(5)
3156
ERROR: Can't read RDOMUSR section of BDMCONFIG file (file)
Description
When the DMADM administrative server is booted, it manages a BDMCONFIG file. When the GWADM administrative servers are started, they request configuration information for a specific local domain from DMADM. This error message indicates that DMADM could not read the DM_RDOMUSR section of the BDMCONFIG file. This indicates that the file is probably corrupted or not properly configured.
Action
Shut down the application and re-generate the BDMCONFIG file.
See Also
dmconfig(5)
3157
ERROR: Can't find LOCAL DOMAIN entry in table
Description
An error occurred while retrieving the local domain entry in table.
Action
Contact BEA TUXEDO system Technical Support.
3158
ERROR: Unable to determine license level
Description
An error occurred while retrieving the current license attributes.
Action
Check the log for prior messages indicating the cause of the problem. Normally, it means that the product has not been licensed properly.
3159
ERROR: No license for /T Domains
Description
You do not have a license to use /T Domains.
Action
Purchase a license for /T Domains. If you believe that you own and have installed the license for /T Domains, contact BEA TUXEDO system Technical Support.
3160
ERROR: Domain compression configured for val, but no license available
Description
You do not have a license to use Domains compression.
Action
Purchase a license for Domains compression.
3163
ERROR: Memory allocation failure
Description
An error was detected while processing the dmconfig file using the dmloadcf command. A memory allocation failure was detected.
Action
Attempt to identify and stop any extraneous processes to free up virtual memory on your system.
See Also
dmconfig(5)
3164
ERROR: Memory allocation failure
Description
An error was detected while processing the dmconfig file using the dmloadcf command. A memory allocation failure was detected.
Action
Attempt to identify and stop any extraneous processes to free up virtual memory on your system.
See Also
dmconfig(5)
3165
ERROR: Aliasing /T internal system service is prohibited
Description
The Domain configuration file in the DM_LOCAL_SERVICES section contains entry which map a /T internal system service to a user accessible service name.
Action
Correct the error in the Domain configuration, and re-run dmloadcf.
3166
ERROR: Aliasing /T internal system service is prohibited
Description
The Domain configuration file in the DM_REMOTE_SERVICES section contains entry which map a BEA TUXEDO system internal system service to a user accessible service name.
Action
Correct the error in the Domain configuration, and re-run dmloadcf.
3167
ERROR: Aliasing /T system service is prohibited
Description
The Domain configuration in the DM_LOCAL_SERVICES section contains entry which map a BEA TUXEDO system service to a user accessible service name.
Action
Correct the error in the Domain configuration, and re-run dmloadcf.
3168
ERROR: Aliasing /T system service is prohibited
Description
The Domain configuration in the DM_REMOTE_SERVICES section contains entry which map a BEA TUXEDO system service to a user accessible service name.
Action
Correct the error in the Domain configuration, and re-run dmloadcf.
3169
ERROR: Aliasing /T internal system service is prohibited
Description
User trying to dynamically add or change a local service which use RNAME to map a BEA TUXEDO system internal system service to a user accessible service.
Action
Correct the error.
3170
ERROR: Aliasing /T system service is prohibited
Description
User trying to dynamically add or change a local service which use RNAME to map a BEA TUXEDO system service to a user accessible service.
Action
Correct the error.
3171
ERROR: Aliasing /T internal system service is prohibited
Description
User trying to dynamically add or change a remote service which use RNAME to map a BEA TUXEDO system internal system service to a user accessible service.
Action
Correct the error.
3172
ERROR: Aliasing /T system service is prohibited
Description
User trying to dynamically add or change a remote service which use RNAME to map a BEA TUXEDO system system service to a user accessible service.
Action
Correct the error.
3173
ERROR: Memory allocation failure
Description
An attempt to dynamically allocate memory from the operating system using malloc failed while parsing the DMCONFIG file.
Action
Ensure 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.
3174
WARN: value val does not fit in character
Description
While parsing the DMCONFIG file, a hex escape sequence was found with a value larger than will fit in a single character (i.e., greater than 0xff).
Action
Correct the value and re-run dmloadcf(1).
3175
WARN: dubious escape val
Description
While parsing the DMCONFIG file, a backslash escape preceding a character that is not a valid escape sequence (t, n, f, b, r, 0, backslash, n, x, or X).
Action
Correct the value and re-run dmloadcf(1).
3176
WARN: value val does not fit in character
Description
While parsing the DMCONFIG file, an octal escape sequence was found with a value larger than will fit in a single character (i.e., greater than 0xff).
Action
Correct the value and re-run dmloadcf(1).
3177
WARN: dubious escape val
Description
While parsing the DMCONFIG file, a backslash escape preceding a character that is not a valid escape sequence (t, n, f, b, r, 0, backslash, n, x, or X).
Action
Correct the value and re-run dmloadcf(1).
3178
ERROR: Memory allocation failure
Description
An attempt to dynamically allocate memory from the operating system using malloc failed while parsing the DMCONFIG file.
Action
Ensure 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.
3179
ERROR: Duplicate entry (entry) occurs in section section. (IC = code)
Description
An error was encountered while processing the dmconfig(5) file. The entry name <entry> is a duplicate of an existing entry name within section <section>. All entry names within a section must be unique. The value of <code> is an internal error code used for diagnosis.
Action
Correct the value in the DMCONFIG file as appropriate and retry the operation.
See Also
dmconfig(5)
3180
ERROR: Can't get sizes for SNA related sections of BDMCONFIG file
Description
The Domain Administrative Server (DMADM) encountered an error while trying to determine the configuration size to be sent to the Gateway Administrative Server (GWADM). The configuration size for the SNA sections could not be determined. The SNA sections of the BDMCONFIG may be unreadable due to corruption of the BDMCONFIG file.
Action
Attempt to unload the BDMCONFIG file using dmunloadcf(1). If the BDMCONFIG file is corrupted, it may be necessary to rebuild the BDMCONFIG file from the ascii version DMCONFIG file using dmloadcf(1).
See Also
dmconfig(5), dmunloadcf(1), dmloadcf(1)
3183
ERROR: Domain (name) is not a (scope) domain. (IC = code)
Description
An error was encountered while processing the dmconfig(5) file. While parsing either a DM_SNALINKS entry or a DM_SNACRM entry, a domain name of the wrong scope was referred to. The value of scope is one of either "LOCAL" or "REMOTE". A DM_SNALINKS section entry can only refer to a domain of scope "REMOTE" and a DM_SNACRM section entry can only refer to a domain of scope "LOCAL". The value of code is an internal error code used for diagnosis.
Action
Correct the value in the DMCONFIG file as appropriate and retry the operation.
See Also
dmconfig(5)
3184
ERROR: SNACRMADDR <addr> already referenced within LDOM <name>
Description
An error was encountered while processing an entry in the DM_SNACRM section of the dmconfig(5) file. The value addr on the SNACRMADDR parameter has already been specified by a prior DM_SNACRM section entry referring to LDOM name. The value of the SNACRMADDR parameter must be unique within DM_SNACRM entries pointing to the same LDOM.
Action
Correct the value in the DMCONFIG file as appropriate and retry the operation.
See Also
dmconfig(5)
3185
ERROR: Parameter (name) contains value (value) not previously defined. (IC = code)
Description
An error was encountered while processing the dmconfig(5) file. The parameter name contains a value value which refers to an entry which was not previously defined. The value of parameter name must refer to an entry which was previously defined. The value of code is an internal error code used for diagnosis.
Action
Correct the value in the DMCONFIG file as appropriate and retry the operation.
See Also
dmconfig(5)
3186
ERROR: Parameter (name) contains an invalid value (value) . (IC = code)
Description
An error was encountered while processing the dmconfig(5) file. The value value specified for parameter name is not a valid value. The value of code is an internal error code used for diagnosis.
Action
Correct the value in the DMCONFIG file as appropriate and retry the operation.
See Also
dmconfig(5)
3187
ERROR: Remote domain <domain name> already referenced by SNALINK <link>
Description
An error was encountered while processing a DM_SNALINKS section entry in the dmconfig(5) file. The remote domain name domain name specified on the DM_SNALINKS entry link name is already referenced by a prior DM_SNALINKS section entry. There must be a one-to-one correspondence between DM_SNALINKS sections and remote domains sections of type SNAX.
Action
Correct the value in the DMCONFIG file as appropriate and retry the operation.
See Also
dmconfig(5)
3189
ERROR: Unknown API type <type>. Only ATMI, CICS, are recognized. (IC = code)
Description
An error was encountered while processing the dmconfig(5) file. The API parameter in the DM_LOCAL_SERVICES (or DM_REMOTE_SERVICES) section contains an invalid value. The value type specified on the API parameter is not one of the recognized values. Only the values ATMI, or CICS are recognized. The value of code is an internal error code used for diagnosis.
Action
Correct the value in the DMCONFIG file as appropriate and retry the operation.
See Also
dmconfig(5)
3191
ERROR: Unknown FUNCTION type <type>. Only APPC, ATI, DPL, DTP, are recognized
Description
An error was encountered while processing the dmconfig(5) file. The FUNCTION parameter in the DM_REMOTE_SERVICES section contains an invalid value. The value type specified on the FUNCTION parameter is not one of the recognized values. Only the values APPC, ATI, DPL or DTP are recognized.
Action
Correct the value in the DMCONFIG file as appropriate and retry the operation.
See Also
dmconfig(5)
3192
ERROR: Can't add SNACRM entry into table
Description
An error was encountered by the Gateway Administrative Server (GWADM) while processing a MIB request. An entry could not be added to the shared memory table associated with the SNACRM configuration.
Action
This is an internal error with no associated user action. If the error persists, contact your BEA TUXEDO system Technical Support with the exact error message.
See Also
GWADM(5)
3193
ERROR: Can't add SNASTACK entry into table
Description
An error was encountered by the Gateway Administrative Server (GWADM) while processing a MIB request. An entry could not be added to the shared memory table associated with the SNASTACK configuration.
Action
This is an internal error with no associated user action. If the error persists, contact your BEA TUXEDO system Technical Support with the exact error message.
See Also
GWADM(5)
3194
ERROR: Can't add SNALINK entry into table
Description
An error was encountered by the Gateway Administrative Server (GWADM) while processing a MIB request. An entry could not be added to the shared memory table associated with the SNALINK configuration.
Action
This is an internal error with no associated user action. If the error persists, contact your TUXEDO System Technical Support
with the exact error message.
See Also
GWADM(5)
3195
ERROR: temp file creation failed
Description
The dmadmin(1) dynamic configuration utility detected an error. A system error prevented the process from creating a temporary file needed for the operation.
Action
Attempt to identify the cause of the system error preventing the creation of the temporary file. Correct the problem and retry the operation. If the error persists, contact your TUXEDO System Technical Support with the exact error message.
See Also
dmadmin(1)
3196
ERROR: cannot open output file file name
Description
The dmunloadcf(1) utility detected an error. A system error prevented the process from opening the specified output file file name.
Action
Attempt to identify the cause of the system error preventing the opening of the output file. Correct the problem and retry the operation. If the error persists, contact your TUXEDO System Technical Support with the exact error message.
See Also
dmunloadcf(1)
3197
ERROR: If SECURITY = DM_PW, then DOMAIN TYPE must be TDOMAIN
Description
An error was encountered while processing the dmconfig(5) file. The DM_LOCAL_DOMAINS section entry specified a security value of DM_PW; however, the domain type is not TDOMAIN. A domain must be of type TDOMAIN in order to specify DM_PW for the SECURITY parameter.
Action
Correct the value in the DMCONFIG file as appropriate and retry the operation.
See Also
dmconfig(5)
3198
ERROR: Bad domain type for MAX_LISTENING_EP
Description
The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The MAX_LISTENING_EP parameter in the DM_OSITP section is specified for the wrong type of domain. The MAX_LISTENING_EP parameter can only be specified for LOCAL domains of type OSITP.
Action
Correct the entry in the DM_OSITP section and retry the operation.
See Also
dmloadcf(1)
3199
ERROR: MAX_LISTENING_EP can only be specified for LOCAL OSITP domain
Description
The dmloadcf(1) utility detected an error while processing the dmconfig(5) file. The MAX_LISTENING_EP parameter in the DM_OSITP section is specified for the wrong type of domain. The MAX_LISTENING_EP parameter can only be specified for LOCAL domains of type OSITP.
Action
Correct the entry in the DM_OSITP section and retry the operation.
See Also
dmloadcf(1)
 |
 |
 |