This is an informative message indicating that the BEA TUXEDO administrative server GWADM server is shutting down.
No action required.
The named value is invalid. Check surrounding messages for specifics.
Correct the value in the DMCONFIG file as appropriate, according to surrounding messages.
DMCONFIG (5)
While executing dmloadcf, the TUXCONFIG environment variable has not been set and exported.
Set and export the TUXCONFIG environment variable and re-execute the command.
DMCONFIG (5)
The value of the TUXCONFIG environment variable must be an absolute pathname. Relative paths and environment variables are not allowed.
Correct the value for the TUXCONFIG environment variable to be an absolute pathname.
DMCONFIG (5)
While executing dmloadcf command, the TUXCONFIG file is read to cross-check the information in the DMCONFIG file. This message indicates that the reading of the TUXCONFIG file failed.
Set TUXCONFIG to the appropriate filename. Make sure that the file and the directory structure is accessible by the user running dmloadcf.
DMCONFIG (5)
An attempt to allocate dynamic memory from the operating system using malloc() failed while parsing the configuration file.
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, or increase the amount of virtual memory that a process can allocate for various sections (data, stack, vmemory, etc).
All the sections in the DMCONFIG file can be defined only once.
Remove the second definition of the section or merge it into the first definition and then re-load the configuration.
Value of the parameter should conform to the restrictions stated above.
Edit the DMCONFIG file to change the value of the specified parameter and then re-load the configuration.
The BDMCONFIG file is a binary file in the BEA TUXEDO VTOC format. Each section of the DMCONFIG file (*DM_RESOURCES, *DM_LOCAL_SERVICES, etc.) is stored as a separate table in the BDMCONFIG file. An error occurred while writing to a section of the BDMCONFIG.
If the BDMCONFIG file is a UNIX file, the file system that it is in should be checked to see if it has enough free space. The file should be checked to see if its permissions allow writing. If the BDMCONFIG VTOC is being used to hold only the BDMCONFIG tables (and not the TLOG or a BEA TUXEDO /D database), then the first thing to try is to recreate a new BDMCONFIG. If the BDMCONFIG is a UNIX file, simply remove it. If it is stored on raw disk, erase it by doing: echo "" > $BDMCONFIG If the error persists, check for disk-type error conditions that might cause problems writing to files. Finally, contact BEA TUXEDO System Technical Support, making sure to have the vtoc_errno that was printed in the error message.
DMCONFIG (5)
The BDMCONFIG file is a binary file in the BEA TUXEDO VTOC format. Each section of the BDMCONFIG file (*DM_RESOURCES, *DM_LOCAL_SERVICES, etc.) is stored as a separate table in the BDMCONFIG file. While trying to parse the BDMCONFIG file, dmloadcf got an error trying to open the section section_name.
Check the value of the BDMCONFIG environment variable. If it is the right value, the BDMCONFIG file may be corrupted. Re-generate the BDMCONFIG file and re-execute the command.
The sections must appear in the order specified in the DMCONFIG(5) description.
Rearrange the sections such that they are in the proper order and then re-load the configuration.
DMCONFIG (5)
The BDMCONFIG file is a binary file in the BEA TUXEDO VTOC format. Each section of the DMCONFIG file (*DM_RESOURCES, *DM_LOCAL_SERVICES, etc.) is stored as a separate table in the BDMCONFIG file. An error occurred while writing to a section of the BDMCONFIG.
If the BDMCONFIG file is a UNIX file, the file system that it is in should be checked to see if it has enough free space. The file should be checked to see if its permissions allow writing. If the BDMCONFIG VTOC is being used to hold only the BDMCONFIG tables (and not the TLOG or a BEA TUXEDO /D database), then the first thing to try is to recreate a new BDMCONFIG. If the BDMCONFIG is a UNIX file, simply remove it. If it is stored on raw disk, erase it by doing: echo "" > $BDMCONFIG If the error persists, check for disk-type error conditions that might cause problems writing to files. Finally, contact BEA TUXEDO System Technical Support, making sure to have the vtoc_errno that was printed in the error message.
DMCONFIG (5)
The GWGRP specified, grpname, in the *DM_LOCAL_DOMAIN section of the DMCONFIG file must have a GWADM server listed in the UBBCONFIG file.
Set the GWGRP in *DM_LOCAL_DOMAIN section of the DMCONFIG file to a correct group in the UBBCONFIG file and re-load the configuration.
DMCONFIG (5)
The domain type, domain_type, specified is not found in the system file. This file should not be modified by non-source customers.
If you are a binary-only customer, read the file from the install tape. If you are a source customer, call Technical Support.
DMCONFIG (5)
The stated parameter was specified as a hexadecimal number (starting with 0x or \\\\x), but a non-hexadecimal character was encountered in the string.
Enter hexadecimal characters in the stated parameter and re-load the configuration.
DMCONFIG (5)
The stated parameter was specified as a hexadecimal number (starting with 0x or \\\\x). This requires that there be an even number of characters following the prefix.
Correct the value to have an even number of hexadecimal characters and re-load the configuration.
DMCONFIG (5)
Entries in the specified section have to be unique by the domain name.
Choose another name for one of the unique keys duplicated.
DMCONFIG (5)
domainid must be unique across local and remote domains.
Specify a value for domainid that has not already been specified in the *DM_LOCAL_DOMAIN section and *DM_REMOTE_DOMAIN section of the DMCONFIG file.
DMCONFIG (5)
The AUDITLOG parameter in the *DM_LOCAL_DOMAIN section of the DMCONFIG file must be an absolute pathname. This means it must begin with a '/' character.
Replace the current AUDITLOG parameter with the full pathname of the file, for example, "/domain_app/DOMAIN_AUDIT.LOG".
DMCONFIG (5)
The string parameter specified has a length that is greater than the specified maximum number of characters.
Correct the string in the DMCONFIG file to be less than or equal to len characters.
DMCONFIG (5)
The identifier, ident, has a length that is greater than the maximum number of characters.
Correct the identifier in the DMCONFIG file to be less than or equal to the len characters.
DMCONFIG (5)
If SECURITY is set to APP_PW for a local domain in the DMCONFIG file, then SECURITY must be set to APP_PW in the UBBCONFIG file.
Set SECURITY (in *RESOURCES section) to APP_PW in UBBCONFIG, run tmloadcf on the UBBCONFIG file, and then run dmloadcf on the DMCONFIG file.
DMCONFIG (5)
The value USER_PW was found on the SECURITY= parameter of the DM_LOCAL_DOMAINS section of the DMCONFIG file. The value USER_PW requires that either USER_AUTH, ACL, or ACL_MANDATORY be specified for the SECURITY parameter in the RESOURCES section of the TUXCONFIG file.
Change the value in the DMCONFIG file or modify TUXCONFIG as appropriate.
DMCONFIG (5)
A value is required for parameter, param, in section section.
Specify a value for the parameter, param, in the section and then re-load the configuration.
DMCONFIG (5)
The domain type specified is not found in the system file $TUXDIR/udataobj/DMTYPE. This file should not be modified by non-source customers.
If you are a binary-only customer, read the file from the install tape. If you are a source customer, call Technical Support.
DMCONFIG (5)
The value of ACN parameter in *DM_OSITP section of the DMCONFIG file can only be set to either XATMI or UDT.
Choose a valid value for ACN and re-load the configuration.
DMCONFIG (5)
The value of PROFILE in *DM_OSITP section of the DMCONFIG file can only be set to one of the above values.
Choose a valid value for PROFILE and re-load the configuration.
DMCONFIG (5)
Domain name is referenced in other section(s) without it being defined in *DM_LOCAL_DOMAIN or *DM_REMOTE_DOMAIN of the DMCONFIG file.
Define the domain name first before referencing it and re-load the configuration.
DMCONFIG (5)
You cannot specify more than max_rdom remote domains per ACL.
Reduce the number of remote domains specified for this ACL entry and re-load the configuration.
DMCONFIG (5)
The option specified is not a valid option to the dmloadcf command.
Correct the options to the dmloadcf command as per the usage message.
DMCONFIG (5)
While executing dmloadcf, an attempt to get the current working directory path failed. This can indicate that either the directory pathname is greater than 78 characters in length or that the directory hierarchy is not readable.
Check that the directory has the proper permissions and is not longer than 78 characters, and re-execute the command.
DMCONFIG (5)
While executing dmloadcf, the length of the absolute pathname of the input file (the directory name followed by '/' and the file name) is greater than 78 characters in length.
Choose a shorter pathname for the input file and re-execute the command.
DMCONFIG (5)
While executing dmloadcf, the specified input file cannot be opened.
Check that the input (DMCONFIG) file exists and is readable and re-execute the command.
DMCONFIG (5)
While executing dmloadcf, an error occurred parsing the input DMCONFIG file.
Earlier warning error messages will indicate the nature of the error. Correct these problems and re-execute the command.
DMCONFIG (5)
While executing dmloadcf, an error occurred in the input DMCONFIG file such that the BDMCONFIG file cannot be loaded. These errors include missing sections, multiple occurrence of sections, dynamic space allocation errors, etc., such that the parsing of the input DMCONFIG file was terminated before reading the entire file.
Earlier warning error messages will indicate the nature of the error. Correct these problems and re-execute the command.
DMCONFIG (5)
While executing dmloadcf, one or more errors occurred in the input DMCONFIG file such that the BDMCONFIG file cannot be loaded. Normally, this message indicates that the entire DMCONFIG file was read and checked for errors.
Earlier warning error messages will indicate the nature of the error. Correct these problems and re-execute the command.
DMCONFIG (5)
While executing dmloadcf, the specified file, filename, could not be opened for reading. dmloadcf works by reading the input twice, and this failure occurs in the second pass. If the input is not from a file (for example, from the standard input), then the input is put into a temporary file and this file cannot be opened for reading.
Check that this file still exists and has read permission. Re-execute the command.
DMCONFIG (5)
While executing dmloadcf, an error was found during the second pass of parsing the input.
Re-execute the command. If the problem happens again, contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
While executing dmloadcf, the input DMCONFIG file has been successfully processed and a new BDMCONFIG file, filename, has been created (that is, it did not exist and a new one was created).
No action required.
DMCONFIG (5)
While executing dmloadcf, the input DMCONFIG file has been processed and an existing BDMCONFIG file has been updated with the information.
No action required.
DMCONFIG (5)
While executing dmloadcf, the BDMCONFIG environment variable has not been set and exported.
Set and export the BDMCONFIG environment variable and re-execute the command.
DMCONFIG (5)
While executing dmloadcf, the BDMOFFSET environment variable is not set correctly to a non-negative integer offset.
Set and export the BDMOFFSET environment variable to a non-negative integer offset and re-execute the command.
DMCONFIG (5)
While executing dmloadcf, an error occurred in checking the BDMCONFIG file.
Check that either the BDMCONFIG file does not exist (if it is being created for the first time) or that it exists and is a valid configuration file. Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
While executing dmloadcf, the size specified for the -b option on the command is too small to hold the configuration.
If BDMCONFIG is a UNIX file, it is recommended that the -b option not be specified such that dmloadcf will size the configuration file correctly. If BDMCONFIG is a raw device, then the -b option should be used to specify the total size in blocks of the device; if this was done, then a larger raw device is needed. System message CW1555 indicates the minimum number of blocks needed for the file or device.
DMCONFIG (5)
While executing dmloadcf, the size specified for the -b option on the command is too small to hold the configuration.
If BDMCONFIG is a UNIX file, it is recommended that the -b option not be specified such that dmloadcf will size the configuration file correctly. If BDMCONFIG is a raw device, then the -b option should be used to specify the total size in blocks of the device; if this was done, then a larger raw device is needed. The minimum number of blocks needed is specified in this message, nblocks.
DMCONFIG (5)
While executing dmloadcf, creation of the BDMCONFIG file failed.
A subsequent system message will indicate the nature of the failure. Correct the problem and re-execute the command.
DMCONFIG (5)
While executing dmloadcf, a new BDMCONFIG file or device was created with the specified size, nblocks.
No action required.
DMCONFIG (5)
While executing dmloadcf, a failure occurred while trying to create the specified tablename. One table is created for each of the sections in the DMCONFIG file.
A subsequent system message will indicate the nature of the failure. Correct the problem and re-execute the command.
DMCONFIG (5)
While executing dmloadcf, a failure occurred while trying to write the specified tablename. One table is created, opened, and written for each of the sections in the DMCONFIG file.
A subsequent system message will indicate the nature of the failure. Correct the problem and re-execute the command.
DMCONFIG (5)
While executing dmloadcf, a failure occurred while trying to write the table associated with the section section_name. One table is created, opened, and written for each section in the DMCONFIG file.
This is an internal error with no associated user action. If the error persists, contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
While executing dmloadcf, the configuration file could not be loaded because the application is active.
If the application is active, shut down the application using the tmshutdown command, or make the change using the dynamic reconfiguration program dmadmin. If the application is not active, then another application is using the same IPC key. Choose another IPC key and re-execute the command.
DMCONFIG (5)
While executing dmloadcf, the BDMCONFIG file did not exist. When asked if the BDMCONFIG file should be created, the administrator did not respond positively so the file was not created and loaded.
No action required.
DMCONFIG (5)
While executing dmloadcf, the BDMCONFIG file already exists. When asked if the BDMCONFIG file should be overwritten, the administrator did not respond positively so the file was not updated.
No action required.
DMCONFIG (5)
The local domain specified in the administrative request is either not configured or currently inactive.
Configure and activate the corresponding local domain.
An error was encountered while reading the referenced section from the Domain Configuration file (BDMCONFIG). The BDMCONFIG file is a binary file in the BEA TUXEDO VTOC format. Each section of the DMCONFIG file (*DM_RESOURCES, *DM_LOCAL_SERVICES, etc.) is stored as a separate table in the BDMCONFIG file. An error occurred while reading from a section of the BDMCONFIG.
If the BDMCONFIG file is a UNIX file, the file system that it is in should be checked to see if it has enough free space and if its permissions allow writing. If the BDMCONFIG VTOC is being used to hold only the BDMCONFIG tables (and not the TLOG or a BEA TUXEDO /D database), then the first thing to try is to recreate a new BDMCONFIG. If the BDMCONFIG is a UNIX file, simply remove it. If it is stored on raw disk, erase it by doing: echo "" > $BDMCONFIG If the error persists, check for disk-type error conditions that might cause problems writing to files. Finally, contact BEA TUXEDO System Technical Support, making sure to have the vtoc_errno that was printed in the error message.
DMCONFIG (5)
The Domain type (TDOMAIN/OSITP/...) cannot be validated because the file specified in the error message cannot be accessed.
The problem may be that of a missing file, or incorrect permissions to the file or to a directory in the pathname of the file. Correct the problem through the usual UNIX interfaces.
The Domain type specified in the request does not exist in the $TUXDIR/udataobj/DMTYPE file.
Check whether the correct Domain type is specified in the request, and also check if the type exists in the $TUXDIR/udataobj/DMTYPE file.
A request of an invalid class has been routed to the DMADM server.
Contact BEA TUXEDO System Technical Support with the exact error message.
An invalid operation has been specified in the administrative request. The valid operations are GET, SET, and GETNEXT.
Specify the correct operation in the administrative request.
The option specified is not a valid option to the dmunloadcf command.
Correct the options to the dmunloadcf command as per the usage message.
DMCONFIG (5)
dmunloadcf(1) The offending option is printed with this error message.
Verify options to dmunloadcf and re-execute the command.
DMCONFIG (5)
While executing dmloadcf, the BDMCONFIG environment variable has not been set and exported.
Set and export the BDMCONFIG environment variable and re-execute the command.
DMCONFIG (5)
The value of the BDMCONFIG environment variable must be an absolute pathname. Relative paths and environment variables are not allowed.
Correct the value for the BDMCONFIG environment variable to be an absolute pathname.
DMCONFIG (5)
The BDMCONFIG file is a binary file in the BEA TUXEDO VTOC format. Each section of the BDMCONFIG file (*DM_RESOURCES, *DM_LOCAL_SERVICES, etc.) is stored as a separate table in the BDMCONFIG file. While trying to read the BDMCONFIG file, dmunloadcf got an error trying to open the *DM_RESOURCES section.
Check the value of the BDMCONFIG environment variable. If it is the right value, the BDMCONFIG file may be corrupted. Re-generate the BDMCONFIG and re-execute the command.
DMCONFIG (5)
The BDMCONFIG file is a binary file in the BEA TUXEDO VTOC format. Each section of the BDMCONFIG file (*DM_RESOURCES, *DM_LOCAL_SERVICES, etc.) is stored as a separate table in the BDMCONFIG file. While trying to read the BDMCONFIG file, dmunloadcf got an error trying to open the *DM_LOCAL_DOMAINS section.
Check the value of the BDMCONFIG environment variable. If it is the right value, the BDMCONFIG file may be corrupted. Re-generate the BDMCONFIG and re-execute the command.
DMCONFIG (5)
The BDMCONFIG file is a binary file in the BEA TUXEDO VTOC format. Each section of the BDMCONFIG file (*DM_RESOURCES, *DM_LOCAL_SERVICES, etc.) is stored as a separate table in the BDMCONFIG file. While trying to read the BDMCONFIG file, dmunloadcf got an error trying to open the *DM_REMOTE_DOMAINS section.
Check the value of the BDMCONFIG environment variable. If it is the right value, the BDMCONFIG file may be corrupted. Re-generate the BDMCONFIG and re-execute the command.
DMCONFIG (5)
The BDMCONFIG file is a binary file in the BEA TUXEDO VTOC format. Each section of the BDMCONFIG file (*DM_RESOURCES, *DM_LOCAL_SERVICES, etc.) is stored as a separate table in the BDMCONFIG file. While trying to read the BDMCONFIG file, dmunloadcf got an error trying to open the *DM_TDOMAIN section.
Check the value of the BDMCONFIG environment variable. If it is the right value, the BDMCONFIG file may be corrupted. Re-generate the BDMCONFIG and re-execute the command.
DMCONFIG (5)
The BDMCONFIG file is a binary file in the BEA TUXEDO VTOC format. Each section of the BDMCONFIG file (*DM_RESOURCES, *DM_LOCAL_SERVICES, etc.) is stored as a separate table in the BDMCONFIG file. While trying to read the BDMCONFIG file, dmunloadcf got an error trying to open the *DM_OSITP section.
Check the value of the BDMCONFIG environment variable. If it is the right value, the BDMCONFIG file may be corrupted. Re-generate the BDMCONFIG and re-execute the command.
DMCONFIG (5)
The BDMCONFIG file is a binary file in the BEA TUXEDO VTOC format. Each section of the BDMCONFIG file (*DM_RESOURCES, *DM_LOCAL_SERVICES, etc.) is stored as a separate table in the BDMCONFIG file. While trying to read the BDMCONFIG file, dmunloadcf got an error trying to open the *DM_ACCESS_CONTROL section.
Check the value of the BDMCONFIG environment variable. If it is the right value, the BDMCONFIG file may be corrupted. Re-generate the BDMCONFIG and re-execute the command.
DMCONFIG (5)
The BDMCONFIG file is a binary file in the BEA TUXEDO VTOC format. Each section of the BDMCONFIG file (*DM_RESOURCES, *DM_LOCAL_SERVICES, etc.) is stored as a separate table in the BDMCONFIG file. While trying to read the BDMCONFIG file, dmunloadcf got an error trying to open the *DM_LOCAL_SERVICES section.
Check the value of the BDMCONFIG environment variable. If it is the right value, the BDMCONFIG file may be corrupted. Re-generate the BDMCONFIG and re-execute the command.
DMCONFIG (5)
The BDMCONFIG file is a binary file in the BEA TUXEDO VTOC format. Each section of the BDMCONFIG file (*DM_RESOURCES, *DM_LOCAL_SERVICES, etc.) is stored as a separate table in the BDMCONFIG file. While trying to read the BDMCONFIG file, dmunloadcf got an error trying to open the *DM_REMOTE_SERVICES section.
Check the value of the BDMCONFIG environment variable. If it is the right value, the BDMCONFIG file may be corrupted. Re-generate the BDMCONFIG and re-execute the command.
DMCONFIG (5)
The BDMCONFIG file is a binary file in the BEA TUXEDO VTOC format. Each section of the BDMCONFIG file (*DM_RESOURCES, *DM_LOCAL_SERVICES, etc.) is stored as a separate table in the BDMCONFIG file. While trying to read the BDMCONFIG file, dmunloadcf got an error trying to open the *DM_ROUTING section.
Check the value of the BDMCONFIG environment variable. If it is the right value, the BDMCONFIG file may be corrupted. Re-generate the BDMCONFIG and re-execute the command.
DMCONFIG (5)
The value of PROFILE in *DM_OSITP section of the DMCONFIG file can only be set to one of the above values if ACN is set to XATMI.
Choose a valid value for PROFILE and re-load the configuration.
DMCONFIG (5)
The value of AET in *DM_OSITP section of the DMCONFIG file is in invalid format.
Specify a valid value for AET and re-load the configuration.
DMCONFIG (5)
The value of AUTOTRAN in *DM_REMOTE_SERVICES section of the DMCONFIG file can be either Y or N.
Specify a valid value and re-load the configuration.
DMCONFIG (5)
The value of CONV in *DM_REMOTE_SERVICES section of the DMCONFIG file can be either Y or N.
Specify a valid value and re-load the configuration.
DMCONFIG (5)
The value of RANGES parameter in *DM_ROUTING section of the DMCONFIG file is in invalid format.
Specify a valid value and re-load the configuration.
DMCONFIG (5)
The FML buffer type cannot be specified for INBUFTYPE or OUTBUFTYPE in *DM_LOCAL_SERVICES or *DM_REMOTE_SERVICES section of the DMCONFIG file if LDOM for that entry is of OSITP type.
Correct the error and re-load the configuration.
DMCONFIG (5)
The build_dgw command was unable to execute the C compiler. The name of the program that build_dgw attempted to execute is given as part of the error message.
Verify that the compiler has been installed on the machine, that it is executable, and that the directory containing the compiler is included in the PATH environment variable. If the name of the compiler is other than the standard CC, set and export the CC shell variable to the proper name of the compiler. Otherwise, verify that the CC shell variable is not set to some extraneous value.
DMCONFIG (5)
While executing build_dgw, the TUXDIR environment variable has not been set and exported.
Set the TUXDIR environment variable to the base directory of the BEA TUXEDO System software, and export this variable.
DMCONFIG (5)
The build_dgw cannot open the file, filename, with the pathname specified for the domain type information file: $TUXDIR/udataobj/DMTYPE.
Check your TUXDIR environment variable, and make sure that there is a $TUXDIR/udataobj directory and the DMTYPE file, $TUXDIR/udataobj/DMTYPE, exists and is readable.
DMCONFIG (5)
The file $TUXDIR/udataobj/DMTYPE exists and is readable but it does not have the domain type domain_type.
Add the proper entry in the file and then re-execute build_dgw.
DMCONFIG (5)
A reference was made to routing entry routname in *DM_REMOTE_SERVICES but the definition for that routing criterion does not exist in the *DM_ROUTING section of the DMCONFIG file.
Define a routing entry in *DM_ROUTING that matches routname, or leave the ROUTING field in *DM_REMOTE_SERVICES blank.
DMCONFIG (5)
The BUFTYPE parameter in *DM_ROUTING section of the DMCONFIG file specified duplicate type/subtype pairs. (For types without any subtype specified, the BUFTYPE parameter specified duplicate type pairs.)
Modify the entry so that the same type/subtype pair is not specified more than once. Reload the configuration file.
DMCONFIG (5)
While executing dmloadcf, duplicate entries were found in the *DM_ROUTING section of the DMCONFIG file. ROUTINGNAME and type/subtype together constitute the key.
Modify the entries so that ROUTINGNAME/type/subtype pair is not specified more than once. Reload the configuration file.
DMCONFIG (5)
The value for UID as specified in the *RESOURCES section of the UBBCONFIG file is not the effective user ID of the dmloadcf process. The effective UID of the dmloadcf process must be the same as the UID specified in the *RESOURCES section of the UBBCONFIG file.
Change the UID as specified in the *RESOURCES section of the UBBCONFIG file to the effective UID of the user who will be running the dmloadcf command. If this change is not desired, then the dmloadcf command cannot be run by this user.
DMCONFIG (5)
The SECURITY parameter in the *DM_LOCAL_DOMAINS of the DMCONFIG file is invalid.
Specify a valid value and re-load the configuration file.
DMCONFIG (5)
The RANGES parameter in the *DM_ROUTING section of the DMCONFIG file is invalid.
Correct the error and re-load the configuration.
DMCONFIG (5)
While executing dmloadcf, the BDMCONFIG environment variable has not been set and exported.
Set and export the BDMCONFIG environment variable and re-execute the command.
DMCONFIG (5)
The value of the BDMCONFIG environment variable must be an absolute pathname. Relative paths and environment variables are not allowed.
Correct the value for the BDMCONFIG environment variable to be an absolute pathname.
DMCONFIG (5)
The binary DMCONFIG file represented by environment variable BDMCONFIG file does not exist or is not accessible. Check the pathname of the file and the access permissions of the directory structure.
Specify the correct value for the BDMCONFIG environment variable.
DMCONFIG (5)
Cannot get BDMCONFIG file information using stat() UNIX system call.
Check to make sure that the file is accessible and that the directory structure has proper permissions.
DMCONFIG (5)
The BDMOFFSET environment variable is less than 0.
Specify a value for the BDMOFFSET environment variable that is greater than or equal to 0.
DMCONFIG (5)
The calling process failed to open a configuration table in the BDMCONFIG file. An invalid table type was passed to the system routine responsible for opening configuration tables.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
The section_name of the BDMCONFIG file cannot be opened. The BDMCONFIG file might be corrupted.
You can shut down the application and re-load the BDMCONFIG file using dmloadcf. If the error still occurs, contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
Memory allocation failed for adding new sections in the BDMCONFIG file.
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.
DMCONFIG (5)
The calling process failed to close a configuration table in the BDMCONFIG file. An invalid table type was passed to the system routine responsible for closing configuration tables.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
The BDMCONFIG file in the VTOC table cannot be closed.
Check the permissions and the existence of the BDMCONFIG file, or contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
The calling process failed to seek a configuration table in the BDMCONFIG file. An invalid table type was passed to the system routine responsible for seeking configuration tables.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
Read an entry from the disk table failed. Possible causes: 1) the logical table file descriptor was corrupted, 2) the read page offset was set incorrectly by the system, or 3) the table itself got corrupted which caused read() to fail.
Check your disk tables such as VTOC for possible corruptions and/or damages. If this error still occurs, contact your BEA TUXEDO System Technical Support.
DMCONFIG (5)
While executing a dynamic re-configuration, an invalid table type was detected when attempting to write to the BDMCONFIG file.
This is an internal error with no associated user action. If the error persists, contact BEA TUXEDO System Technical Support.
DMADMIN (5)
While executing a dynamic re-configuration, an error was detected when attempting to write to the BDMCONFIG file. The file associated with the named section section_name of the BDMCONFIG file was not opened prior to attempting the write.
This is an internal error with no associated user action. If the error persists, contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
While executing a dynamic re-configuration, an error was detected when attempting to write to the BDMCONFIG file. The file associated with the named section section_name of the BDMCONFIG file could not be written.
This is an internal error with no associated user action. If the error persists, contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
An error was detected while processing the DMCONFIG file. The buffer type, FML, cannot be specified for INBUFTYPE or OUTBUFTYPE in any *DM_LOCAL_SERVICES or *DM_REMOTE_SERVICES section entry of the DMCONFIG file if the local domain (LDOM) for that entry is of type OSITP.
Correct the error and re-load the configuration.
dmconfig (5)
An error was detected while processing the DMCONFIG file. The entry string appears more than once in the section section_name.
Correct the error and re-load the configuration.
dmconfig (5)
An error was detected while processing the DMCONFIG file. The service name service_name appears more than once in the *DM_LOCAL_SERVICES section.
Correct the error and re-load the configuration.
dmconfig (5)
An error was detected while processing the DMCONFIG file. The name aclname appears more than once in the *DM_ACCESS_CONTROL section.
Correct the error and re-load the configuration.
dmconfig (5)
This is an information message to indicate that the /Domain Administrative server is exiting.
No action required.
dmadmin (1)
The Domain Administrative server was unable to access the Domain type file $TUXDIR/udataobj/DMTYPE.
Check that the TUXDIR environment variable is set correctly and that the DMTYPE file is present in the directory $TUXDIR/udataobj then retry the operation.
dmadmin (1)
The Domain Administrative server was unable to access the Tuxedo configuration file TUXCONFIG.
Check the surrounding messages for information to correct the problem. Correct the source of the problem and retry the operation.
dmadmin (1)
The domain type specified in the *DM_LOCAL_DOMAINS section was not found in the system file $TUXDIR/udataobj/DMTYPE. This file should not be modified by non-source customers.
Correct the TYPE parameter of the *DMLOCAL_DOMAINS section and retry the operation.
dmconfig (5)
The Application Entity Title parameter AET specified in the *DM_OSITP section contains invalid hex digits.
Correct the AET parameter of the *DM_OSITP section and retry the operation.
dmconfig (5)
The domain administrative server detected an error while trying to add or update an entry in the BDMCONFIG file. The DOMAINID parameter specified in the *DM_LOCAL_DOMAINS section was found to contain an odd number of hex digits.
Correct the DOMAINID parameter of the *DM_LOCAL_DOMAINS section and retry the operation.
dmconfig (5)
The domain administrative server detected an error while trying to add or update an entry in the BDMCONFIG file. The AUDITLOG parameter specified in the *DM_LOCAL_DOMAINS section was found to contain an invalid path.
Correct the AUDITLOG parameter of the *DM_LOCAL_DOMAINS section and retry the operation.
dmconfig (5)
The domain administrative server detected an error while trying to add or update an entry in the BDMCONFIG file. The DOMAINID parameter specified was found to be a duplicate of a DOMAINID of an existing entry in either of the *DM_LOCAL_DOMAINS or *DM_REMOTE_DOMAINS sections.
Correct the DOMAINID parameter and retry the operation.
dmconfig (5)
The domain administrative server detected an error while trying to add or update an entry in *DM_LOCAL_DOMAINS section of the BDMCONFIG file. The combination of DMTLOGDEV and DMTLOGNAME parameters must be unique across local domains.
Correct the DMTLOGDEV/DMTLOGNAME parameter combination so that it is unique across local domains.
dmconfig (5)
The domain administrative server detected an error while trying to add or update an entry in the BDMCONFIG file. The DOMAINID parameter specified was found to be a duplicate of a DOMAINID of an existing entry in either of the *DM_LOCAL_DOMAINS or *DM_REMOTE_DOMAINS sections.
Correct the DOMAINID parameter and retry the operation.
dmconfig (5)
The domain administrative server detected an error while trying to retrieve, update, or delete an entry in the BDMCONFIG file. The requested entry in section section_name was not found in the BDMCONFIG file.
You may wish to use the retrieve option to retrieve existing records and retry the operation with a valid entry.
dmconfig (5)
An error was detected while processing the DMCONFIG file. While processing the *DM_REMOTE_SERVICES section a duplicate entry service was found. The mapping of remote services to local domains must be unique within a configuration.
Correct the DMCONFIG file to contain only unique service entries in the *DM_REMOTE_SERVICES section.
dmconfig (5)
An error was detected by the Domain Administrative server while processing a dynamic reconfiguration. In order for the SECURITY parameter of a local domain (*DM_LOCAL_DOMAINS section of the DMCONFIG file) to be set to APP_PW, the application security (*RESOURCES section of the UBBCONFIG file) must be set to APP_PW.
Set the SECURITY (in *RESOURCES section of the UBBCONFIG) to APP_PW, run tmloadcf on the UBBCONFIG file, and then retry the operation.
dmconfig (5) ubbconfig (5)
An error was detected while processing a dynamic reconfiguration. The SECURITY parameter in the *DM_LOCAL_DOMAINS section of the DMCONFIG file contains an invalid value security.
Specify a valid SECURITY value and retry the operation.
dmconfig (5)
The Domain Administrative server was unable to access the Domain type file $TUXDIR/udataobj/DMTYPE.
Check that the TUXDIR environment variable is set correctly and that the DMTYPE file is present in the directory $TUXDIR/udataobj then retry the operation.
dmadmin (1)
An error was detected while processing a dynamic reconfiguration. The domain type specified in the *DM_LOCAL_DOMAINS section was not found in the system file $TUXDIR/udataobj/DMTYPE. This file should not be modified by non-source customers.
Correct the TYPE parameter of the *DMLOCAL_DOMAINS section and retry the operation.
dmconfig (5)
An error was detected while processing a dynamic reconfiguration. The DOMAINID parameter specified in the *DM_REMOTE_DOMAINS section contains invalid hex digits.
Correct the DOMAINID parameter in the *DM_REMOTE_DOMAINS section and retry the operation.
dmconfig (5)
An error was detected while processing a dynamic reconfiguration. The DOMAINID parameter specified in the *DM_LOCAL_DOMAINS section contains invalid hex digits.
Correct the DOMAINID parameter in the *DM_LOCAL_DOMAINS section and retry the operation.
dmconfig (5)
An error was detected while processing a dynamic reconfiguration. The NWADDR parameter specified in the *DM_TDOMAIN section contains invalid hex digits.
Correct the NWADDR parameter in the *DM_TDOMAIN section and retry the operation.
dmconfig (5)
The Domain Administrative server detected an error while trying to change the blocking timeout for a local domain. The new value must be within the range minimum to maximum.
Correct the value of the blocking timeout and retry the operation.
dmconfig (5)
The Gateway Administrative server detected an error while trying to advertise the service service_name.
Check for related messages in the log file.
GWADM (5)
The Domain Administrative server detected an error while trying to change the audit trace setting for a local domain. The value for the audit trace toggle must be either on or off.
Issue the audit command with the correct option (either on or off).
dmadmin (1)
The Domain Administrative server detected an error while trying to create the log file for a local domain. The log file cannot be created while the local domain is running.
Shut down the Gateway Administrative server for the local domain and retry.
dmadmin (1)
The Domain Administrative server detected an error while trying to create the log file for a local domain. The log file cannot be created when one already exists.
If you want to re-initialize the log, use the dsdmlog command to destroy the current log. Retry the crdlg operation.
dmadmin (1)
The Domain Administrative server detected an error while trying to perform a dynamic reconfiguration. The entry identifier of type entry_type was not found in the section or sections described in section_name(s).
Define the missing entry and retry the operation.
dmconfig (5)
The Domain Administrative server detected an error while trying to perform a dynamic reconfiguration. The value of field field_name must be less than or equal to maximum.
Correct the value and retry the operation.
dmconfig (5)
The Domain Administrative server detected an error while trying to perform a dynamic reconfiguration. The value of field field_name must be greater than or equal to minimum.
Correct the value and retry the operation.
dmconfig (5)
The Domain Administrative server detected an error while trying to perform a dynamic reconfiguration. The value of field field_name must be greater than or equal to minimum and less than or equal to maximum.
Correct the value and retry the operation.
dmconfig (5)
An error was detected by the Domain Administrative server while processing a dynamic reconfiguration. The field field_name was found with no associated value. A value must be provided for this field.
Provide a valid value for the field field_name and retry the operation.
DMCONFIG (5)
An error was detected by the Domain Administrative server while processing a dynamic reconfiguration. The field field_name was found to have an invalid value.
Provide a valid value for the field field_name and retry the operation.
DMCONFIG (5)
An error was encountered while reading the referenced section section_name from the Domain Configuration file (BDMCONFIG). The BDMCONFIG file is a binary file in the BEA TUXEDO VTOC format. Each section of the DMCONFIG file (*DM_RESOURCES, *DM_LOCAL_SERVICES, etc.) is stored as a separate table in the BDMCONFIG file. An error occurred while reading from a section of the BDMCONFIG.
If the BDMCONFIG file is a regular file, the file system that it is in should be checked to see if it has enough free space and if its permissions allow writing. If the BDMCONFIG VTOC is being used to hold only the BDMCONFIG tables (and not the TLOG or a BEA TUXEDO database), then the first thing to try is to recreate a new BDMCONFIG. If the BDMCONFIG is a regular file, simply remove it. If it is stored on raw disk, erase it by doing: echo "" > $BDMCONFIG. If the error persists, check for disk-type error conditions that might cause problems writing to files. Finally, contact BEA TUXEDO System Technical Support, making sure to have the vtoc_errno that was printed in the error message.
DMCONFIG (5)
An error was detected by the Domain Administrative server while processing a dynamic reconfiguration. The operation attempted on entry entry_name in section section_name of the BDMCONFIG file can not be performed when the Gateway Administrative Server (GWADM) is active.
Shut down the Gateway Administrative Server (GWADM) and retry the operation.
DMCONFIG (5)
An error was detected by the Domain Administrative server while processing a dynamic reconfiguration. The operation attempted on field field_name of entry entry_name in section section_name of the BDMCONFIG file can not be performed when the Gateway Administrative Server (GWADM) is active.
Shut down the Gateway Administrative Server (GWADM) and retry the operation.
DMADMIN (1)
An error was detected by the Domain Administrative server while processing a dynamic reconfiguration. A delete operation was attempted on either a local domain (*DM_LOCAL_DOMAINS section) or remote domain (*DM_REMOTE_DOMAINS section) while the domain was being referenced by an entry in the section section name. A domain cannot be deleted while a reference to it exists.
Remove all references to the domain which you are attempting to delete and retry the operation.
DMADMIN (1)
An error was detected by the Domain Administrative server while processing a dynamic reconfiguration. An add operation was attempted for an entry which already exists in the section section_name. A duplicate entry cannot be added.
Either rename the entry which you are attempting to add or delete the existing entry and retry the operation.
DMCONFIG (5)
An error was detected by the Domain Administrative server while processing a dynamic reconfiguration. An add operation was attempted for an entry in the section section_name without adequate space available for the expanded section.
If there are any extraneous or unused entries in the named section you may try to remove them to free the necessary space and retry the operation. Another option would be to partition the application among two or more domains; in effect, reducing the space required for the sections in any single domain.
DMCONFIG (5)
This is an informational message indicating that the update of the BDMCONFIG file resulting from a dynamic reconfiguration completed successfully.
No action required.
DMCONFIG (5)
This is an informational message indicating that the requested dynamic reconfiguration operation completed successfully.
No action required.
DMCONFIG (5)
The domain administrative server detected an error while trying to add or upd ate an entry in the BDMCONFIG file. The DOMAINID parameter specified in the *DM_REMOTE_DOMAINS section was found to contain an odd number of hex digits.
Correct the DOMAINID parameter of the *DM_REMOTE_DOMAINS section and retry the operation.
DMCONFIG (5)
The domain administrative server detected an error while trying to add or update an entry in the BDMCONFIG file. The DOMAINID parameter specified was found to be a duplicate of a DOMAINID of an existing entry in either of the *DM_LOCAL_DOMAINS or *DM_REMOTE_DOMAINS sections.
Correct the DOMAINID parameter and retry the operation.
DMCONFIG (5)
The Domain Administrative server was unable to access the Tuxedo configuration file TUXCONFIG.
Check the surrounding messages for information to correct the problem. Correct the source of the problem and retry the operation.
DMADMIN (1)
The Gateway Administrative server detected an error while trying to process an advertise command. The TA_SERVICENAME field was not found in the FML buffer.
This is an internal error with no associated user action. If the error persists, contact BEA TUXEDO System Technical Support.
DMADMIN (1)
The Gateway Administrative server detected an error while trying to process an advertise command. The remote service name specified is not valid.
Correct the remote service name and retry the operation.
DMADMIN (1)
The Domain Administrative Server issues this informational message while processing a destroy domain transaction log command (dsdmlog) when the user enters no to the verification prompt.
No action required.
DMADMIN (1)
The Domain Administrative Server issues this informational message while processing an initialize domain transaction log command (indmlog) when the user enters no to the verification prompt.
No action required.
DMADMIN (1)
The Gateway Administrative server detected an error while trying to process a suspend or resume command. The TA_SERVICENAME field was not found in the FML buffer.
This is an internal error with no associated user action. If the error persists, contact BEA TUXEDO System Technical Support.
DMADMIN (1)
The Gateway Administrative server detected an error while trying to process a suspend or resume command. The remote service name specified is not valid.
Correct the remote service name and retry the operation.
DMADMIN (1)
The Gateway Administrative server detected an error while trying to process an unadvertise command. The TA_SERVICENAME field was not found in the FML buffer.
This is an internal error with no associated user action. If the error persists, contact BEA TUXEDO System Technical Support.
DMADMIN (1)
The Gateway Administrative server detected an error while trying to process an unadvertise command. The remote service name specified is not valid.
Correct the remote service name and retry the operation.
DMADMIN (1)
The Gateway Administrative server detected an error while trying to process the operation specified by the value code. The value code is an internal error code for use in diagnosis.
This is an internal error with no associated user action. If the error persists, contact BEA TUXEDO System Technical Support with the internal error code code.
DMADMIN (1)
The Gateway Administrative server detected an error while trying to process the operation specified by the value code. The process was unable to obtain enough virtual memory. The value code is an internal error code for use in diagnosis.
Attempt to identify and stop any extraneous processes to free up virtual memory on your system.
DMADMIN (1)
The Gateway Administrative server detected an internal error while trying to process a suspend operation for service service_name.
This is an internal error with no associated user action. If the error persists, contact BEA TUXEDO System Technical Support.
DMADMIN (1)
The Gateway Administrative server detected an internal error while trying to process a resume operation for service service_name.
This is an internal error with no associated user action. If the error persists, contact BEA TUXEDO System Technical Support.
DMADMIN (1)
The Gateway Administrative server detected an error while trying to process a resume operation for service service_name. The service service_name needs to be advertised in order for the resume command to complete successfully.
Use the advertise command to advertise the service service_name and retry the operation.
DMADMIN (1)
The Gateway Administrative server detected an error while trying to process an advertise operation. There was no remote service specified and the keyword all was not present.
Retry the advertise command with the proper syntax.
DMADMIN (1)
The Gateway Administrative server detected an error while trying to process an unadvertise operation. There was no remote service specified and the keyword all was not present.
Retry the unadvertise command with the proper syntax.
DMADMIN (1)
The Gateway Administrative server detected an error while trying to process a suspend operation. There was no remote service specified and the keyword all was not present.
Retry the suspend command with the proper syntax.
DMADMIN (1)
The Gateway Administrative server detected an error while trying to process a resume operation. There was no remote service specified and the keyword all was not present.
Retry the resume command with the proper syntax.
DMADMIN (1)
An error was detected while trying to write an audit record to the AUDITLOG file. The audit file file name could not be created. The open system call for the file was not successful. This error may indicate a problem with the file permission settings or a problem with the file system.
Identify any problems with the file permission settings or file system.
DMCONFIG (5)
An error was detected while trying to write an audit record to the AUDITLOG file. The audit file file name could not be written to. The write system call for the file was not successful. This error may indicate a problem with the file permission settings or a problem with the file system.
Identify any problems with the file permission settings or file system.
DMCONFIG (5)
The Domain Administrative server detected an error while trying to process the dmadmin(1) command. An invalid command line option option was detected.
Retry the dmadmin(1) command with the proper options.
DMADMIN (1)
The Domain Administrative server detected an error while trying to process the dmadmin(1) command. An invalid command line argument arg was detected.
Retry the dmadmin(1) command with the proper arguments.
DMADMIN (1)
The Domain Administrative server detected an error while trying to process the dmadmin(1) command. The TUXCONFIG environment variable was not set.
Set the TUXCONFIG environment variable to the complete path and file name for the binary Tuxedo configuration file and retry the dmadmin(1) command.
DMADMIN (1)
The Domain Administrative server detected an error while trying to process the dmadmin(1) command. The TUXCONFIG environment variable was not set to an absolute path. One example of an absolute path is a path starting with a slash (ie. /home/mypath/myfile).
Set the TUXCONFIG environment variable to an absolute path and retry the dmadmin(1) command.
DMADMIN (1)
The Domain Administrative server detected an error while trying to process the dmadmin(1) command. An error was encountered while trying to get the necessary parameters for initialization. A more specific message will also be issued.
Check the surrounding messages for more specific diagnostic information. Correct the source of the error and retry the dmadmin(1) command.
DMADMIN (1)
The Domain Administrative server detected an error while trying to process the dmadmin(1) command. An error was encountered while trying to check the authentication level during initialization.
Check for other related messages in the log.
DMADMIN (1)
The Domain Administrative server detected an error while trying to process the dmadmin(1) command. An error was encountered while trying to obtain virtual memory for the TPINIT buffer.
Attempt to identify and stop any extraneous processes to free up virtual memory on your system, and then retry the operation.
DMADMIN (1)
The Domain Administrative server detected an error while trying to process the dmadmin(1) command. An error was encountered while trying to obtain the password file entry for user user_name.
Have your administrator add the required entry to the password file or use a userid which is already in the password file, and then retry the operation.
DMADMIN (1)
The Domain Administrative server detected an error while trying to process the dmadmin(1) command. An error was encountered while trying to obtain the application password during dmadmin(1) initialization.
Make sure that the application password has been set or that the APP_PW environment variable is set if the process is not attached to a tty, then retry the operation.
DMADMIN (1)
The Domain Administrative server detected an error while trying to process the dmadmin(1) command. The dmadmin(1) command attempted to establish itself as a client to forward administrative requests to DMADM. The description string will provide more detailed information as to the cause of the error.
Use the information in the error description string to correct the cause of the problem and then retry the operation.
DMADMIN (1)
This is a warning message issued as a result of processing the dmadmin(1) command. The issuer of the dmadmin(1) command is not authorized to be the administrator. This message indicates that only a limited number of administrative commands are available to this user.
This is a warning message. If additional capabilities are required see your Tuxedo administrator.
DMADMIN (1)
The Domain Administrative server detected an error while trying to process the shell command shell command. The dmadmin(1) command interpreter allows the execution of shell commands using the ! character prepended to the command. This message indicates that the shell command failed. Additional messages from the shell will be issued to diagnose the cause of the problem.
Use the error messages from the shell to diagnose the cause of the error and retry the operation.
DMADMIN (1)
The Domain Administrative server detected an error while trying to process an administrative command. The opt option contained an argument value which was not numeric.
Repeat the command with a numeric argument value for option opt.
DMADMIN (1)
The Domain Administrative Server detected an error while trying to process the operation specified by the value code. The process was unable to obtain enough virtual memory. The value code is an internal error code for use in diagnosis.
Attempt to identify and stop any extraneous processes to free up virtual memory on your system.
DMADMIN (1)
The Domain Administrative Server detected an error while trying to process the operation specified by the value code. The process was unable to perform the operation. The value code is an internal error code for use in diagnosis. The ULOG will contain more specific information.
Check the ULOG for more specific information on the cause of the error. Correct the cause of the error and retry the operation.
DMADMIN (1)
The Gateway Administrative Server issues this message in response to either a suspend or resume command. The action action was taken for the service remote service name on number queues.
This is an informational message with no associated user action.
DMADMIN (1)
The Gateway Administrative Server issues this message in response to either a suspend or resume command. The action action was taken for the service remote service name on number queue.
This is an informational message with no associated user action.
DMADMIN (1)
The Gateway Administrative Server issues this message in response to the stats command which is used to toggle the statistics gathering functionality. This informational message indicates that statistics gathering has been started.
This is an informational message with no associated user action.
DMADMIN (1)
The Gateway Administrative Server issues this message in response to the stats command which is used to toggle the statistics gathering functionality. This informational message indicates that statistics gathering has been stopped.
This is an informational message with no associated user action.
DMADMIN (1)
The Domain Administrative Server detected an error while processing the stats command which is used to toggle the statistics gathering functionality. An invalid option was entered for the stats command. The only valid options are on, off, or reset.
Enter the stats command with one of the valid options.
DMADMIN (1)
The Domain Administrative Server detected and error while processing the dsdmlog command which is used to destroy the domain transaction log. The transaction log cannot be destroyed while the local domain is running.
Stop the local domain and then try to destroy the transaction log.
DMADMIN (1)
The Domain Administrative Server detected and error while processing the indmlog command which is used to initialize the domain transaction log. The transaction log cannot be initialized while the local domain is running.
Stop the local domain and then try to initialize the transaction log.
DMADMIN (1)
An error was detected while processing the DMCONFIG file. An invalid value was found on the LOOPBACK= parameter in the *DM_REMOTE_DOMAINS section. The only valid values for the LOOPBACK parameter are either Y or N.
Correct the value of the LOOPBACK= parameter in the *DM_REMOTE_DOMAINS section and reload the configuration.
DMADMIN (1)
An error was detected by the Domain Administrative server while processing a dynamic reconfiguration. The value field value found for entry field name is too long. The value must be less than or equal to length characters in length.
Correct the value field value for the entry field name and retry the operation.
DMCONFIG (5)
An error was detected by the Domain Administrative server while processing a dynamic reconfiguration to add or update an entry in the BDMCONFIG file. The DOMAINID parameter specified was found to be a duplicate of a DOMAINID of an existing entry in either of the *DM_LOCAL_DOMAINS or *DM_REMOTE_DOMAINS sections.
Correct the value of the DOMAINID and retry the operation.
DMCONFIG (5)
An error was detected by the Domain Administrative server while processing a dynamic reconfiguration. The NWADDR parameter specified was found to contain an odd number of hex digits. The NWADDR parameter must contain and even number of hex digits.
Correct the value of the NWADDR parameter and retry the operation.
DMCONFIG (5)
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.
Correct the value of the AET parameter and retry the operation.
DMCONFIG (5)
The value of AET in *DM_OSITP section is in invalid format.
Specify a valid value and re-load the configuration.
DMCONFIG (5)
While executing dmadmin, the TUXCONFIG environment variable has not been set and exported.
Set and export the TUXCONFIG environment variable and re-execute the command.
DMCONFIG (5)
The value of the TUXCONFIG environment variable must be an absolute pathname. Relative paths and environment variables are not allowed.
Correct the value for the TUXCONFIG environment variable to be an absolute pathname.
DMCONFIG (5)
While performing dynamic re-configuration, DMADM administrative server cannot read TUXCONFIG file. Since the application must be booted for dynamic reconfiguration to occur and booting requires reading the configuration file, this error should not normally occur. It may indicate that the configuration file has been destroyed or that a disk problem has occurred.
Shut down the application and re-generate the TUXCONFIG file.
DMCONFIG (5)
The BUFTYPE parameter in *DM_ROUTING section in the DMCONFIG file specified duplicate type/subtype pairs. (For types without any subtype specified, the BUFTYPE parameter specified duplicate type pairs.)
Modify the entry so that the same type/subtype pair is not specified more than once. Reload the configuration file.
DMCONFIG (5)
While executing dmadmin, duplicate entries were found in the *DM_ROUTING. ROUTINGNAME and type/subtype together constitute the key.
Modify the entries so that ROUTINGNAME/type/subtype pair is not specified more than once. Re-execute the command.
DMCONFIG (5)
When the /Domain gateway was booted, it was unable to update its own System/T queue table entry with the proper flags. This failure will prevent the gateway from receiving either conversational or RPC type requests.
Look to see whether an earlier userlog message gives further information on the failure. Shut down the application and reboot it to clear any corrupted memory that may be present. Consider running the application temporarily with SYSTEM_ACCESS set to PROTECTED|NO_OVERRIDE in the *RESOURCES section of the TUXCONFIG file. This setting will slow performance, but will prevent the possibility of application corruption of shared memory. If the problem still persists when running with SYSTEM_ACCESS set to PROTECTED|NO_OVERRIDE , contact your TUXEDO System Technical Support.
An attempt was made to dynamically re-configure a local domain that is non-existent, or the GWADM server corresponding to that local domain is not running.
If the specified local domain name is invalid, enter a valid value and re-submit the command. If the GWADM server for the local domain is not running, startup the server and then re-issue the command.
DMCONFIG (5)
The BDMCONFIG file is a binary file in the BEA TUXEDO VTOC format. Each section of the BDMCONFIG file (*DM_RESOURCES, *DM_LOCAL_SERVICES, etc.) is stored as a separate table in the BDMCONFIG file. While trying to read the BDMCONFIG file, dmunloadcf got an error trying to open the *DM_PASSWORDS section.
Check the value of the BDMCONFIG environment variable. If it is the right value, the BDMCONFIG file may be corrupted. Re-generate the BDMCONFIG and re-execute the command.
DMCONFIG (5)
The passwd command must be run from a terminal as opposed to, say, a shell script, since dmadmin prompts for new passwords on the terminal.
Remove the use of the passwd command from any non-terminal invocations of dmadmin.
DMCONFIG (5)
The passwd command failed because dmadmin could not open the terminal device (/dev/tty) for reading.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
The passwd command failed because dmadmin could not open the terminal device (/dev/tty) for reading.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
The passwd command requires a new password to be entered and re-entered identically. If after three attempts this does not occur, the command fails and prints this error message.
Retry the passwd command.
DMCONFIG (5)
The passwd command failed because dmadmin could not open the terminal device (/dev/tty) for reading.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
The passwd command failed because dmadmin could not open the terminal device (/dev/tty) for reading.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
The passwd command requires a new password to be entered and re-entered identically. If after three attempts this does not occur, the command fails and prints this error message.
Retry the passwd command.
DMCONFIG (5)
The /Domain gateway was unable to write a record to the /Domain transaction log.
Check if a hardware failure or administrator action has accidentally damaged the device specified as the DMTLOGDEV in the DM_LOCAL_DOMAINS section of the BDMCONFIG file. If possible, repair any corruption. If the DMTLOGDEV must be recreated, shut down the /Domain gateway group. Then use the dmadmin (1) subcommand crdmlog to create the domain, or just reboot the /Domain gateway group, which will automatically create the log if it does not already exist.
dmadmin (1)
Entries to *DM_PASSWORD section of DMCONFIG file cannot be added when application security is not enabled for the application. That is, the SECURITY keyword in the UBBCONFIG file must be set to APP_PW before domain passwords can be added.
If application security is desired, add the SECURITY keyword to the *RESOURCES section of your UBBCONFIG file and set its value to APP_PW. Then, run tmloadcf() which prompts you for an initial application password. A new password can now be set for the local and remote domain pairs in the configuration mode of the dmadmin command.
DMCONFIG (5)
Entries to *DM_PASSWORDS section of BDMCONFIG file can only be added by running the command from a terminal as opposed to, say, a shell script, since dmadmin prompts for new passwords on the terminal.
Remove the usage of the command from any non-terminal invocations of dmadmin.
DMCONFIG (5)
When updating LPWD parameter for a *DM_PASSWORDS entry in the BDMCONFIG file using dmadmin configuration mode, TA_LPWD must be set to U.
Specify a valid value for TA_LPWD and re-execute the command.
DMCONFIG (5)
When adding a *DM_PASSWORDS entry to the BDMCONFIG file using dmadmin configuration mode, TA_LPWD must be set to Y.
Specify a valid value for TA_LPWD and re-execute the command.
DMCONFIG (5)
When adding a *DM_PASSWORDS entry to the BDMCONFIG file using dmadmin configuration mode, TA_LPWD must be set to Y.
Specify a valid value for TA_LPWD and re-execute the command.
DMCONFIG (5)
When updating RPWD parameter for a *DM_PASSWORDS entry in the DMCONFIG file using dmadmin configuration mode, TA_RPWD must be set to U.
Specify a valid value for TA_RPWD and re-execute the command.
DMCONFIG (5)
When adding a *DM_PASSWORDS entry to the DMCONFIG file using dmadmin configuration mode, TA_RPWD must be set to Y.
Specify a valid value for TA_RPWD and re-execute the command.
DMCONFIG (5)
When adding a *DM_PASSWORDS entry to the DMCONFIG file using dmadmin configuration mode, TA_RPWD must be set to Y.
Specify a valid value for TA_RPWD and re-execute the command.
DMCONFIG (5)
The passwd command failed because dmadmin could not open the terminal device (/dev/tty) for reading.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
The passwd command failed because dmadmin could not open the terminal device (/dev/tty) for reading.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
The passwd command requires a new password to be entered and re-entered identically. If after three attempts this does not occur, the command fails and prints this error message.
Retry the passwd command.
DMCONFIG (5)
The passwd command failed because dmadmin could not open the terminal device (/dev/tty) for reading.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
The passwd command failed because dmadmin could not open the terminal device (/dev/tty) for reading.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
The passwd command requires a new password to be entered and re-entered identically. If after three attempts this does not occur, the command fails and prints this error message.
Retry the passwd command.
DMCONFIG (5)
As part of changing the domain password with the passwd command, the new password is encrypted before writing it to the BDMCONFIG file. This message is issued when the key used for encrypting the new password cannot be generated because memory for the key cannot be dynamically allocated from the operating system using malloc().
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.
DMCONFIG (5)
As part of changing the domain password with the passwd command, the new password is encrypted before writing it to the BDMCONFIG file. This message is issued when the key used for encrypting the new password cannot be generated because memory for the key cannot be dynamically allocated from the operating system using malloc().
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.
DMCONFIG (5)
As part of changing the domain password with the passwd command, the new password is encrypted before writing it to the BDMCONFIG file. The two-way encryption algorithm requires an encryption schedule to be created for use by the encryption routine. This message is issued when the key used for encrypting the new password cannot be generated because memory for the key cannot be dynamically allocated from the operating system using malloc().
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.
DMCONFIG (5)
As part of changing the domain password with the passwd command, the new password is encrypted before writing it to the BDMCONFIG file. This message is issued if the encryption algorithm fails.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
As part of changing the domain password with the passwd command, the new password is encrypted before writing it to the BDMCONFIG file. This message is issued when the key used for encrypting the new password cannot be generated because memory for the key cannot be dynamically allocated from the operating system using malloc().
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.
DMCONFIG (5)
As part of changing the domain password with the passwd command, the new password is encrypted before writing it to the BDMCONFIG file. The two-way encryption algorithm requires an encryption schedule to be created for use by the encryption routine. This message is issued when the key used for encrypting the new password cannot be generated because memory for the key cannot be dynamically allocated from the operating system using malloc().
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.
DMCONFIG (5)
As part of changing the domain password with the passwd command, the new password is encrypted before writing it to the BDMCONFIG file. This message is issued if the encryption algorithm fails.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
While re-encrypting passwords in *DM_PASSWORDS section of BDMCONFIG file, the *DM_RESOURCES section of BDMCONFIG file cannot be opened for reading.
Make sure that the BDMCONFIG file still exists.
DMCONFIG (5)
While re-encrypting passwords in *DM_PASSWORDS section of BDMCONFIG file, the *DM_RESOURCES section of BDMCONFIG file cannot be accesses for reading.
Make sure that the BDMCONFIG file still exists.
DMCONFIG (5)
While re-encrypting passwords in *DM_PASSWORDS section of BDMCONFIG file, the *DM_PASSWORDS section of BDMCONFIG file cannot be opened for reading.
Make sure that the BDMCONFIG file still exists.
DMCONFIG (5)
While re-encrypting passwords in *DM_PASSWORDS section of BDMCONFIG file, the *DM_PASSWORDS section of BDMCONFIG file cannot be accessed for writing the new re-encrypted entries.
Make sure that the BDMCONFIG file still exists.
DMCONFIG (5)
While re-encrypting passwords in *DM_PASSWORDS section of BDMCONFIG file, the *DM_PASSWORDS section of BDMCONFIG file cannot be accessed for writing the new DMKEY.
Make sure that the BDMCONFIG file still exists.
DMCONFIG (5)
As part of changing the domain password with the passwd command, the new password is encrypted before writing it to the BDMCONFIG file. This message is issued when the key used for encrypting the new password cannot be generated because memory for the key cannot be dynamically allocated from the operating system using malloc().
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.
DMCONFIG (5)
While executing dmloadcf, the TUXCONFIG environment variable has not been set and exported.
Set and export the TUXCONFIG environment variable and re-execute the command.
DMCONFIG (5)
The value of the TUXCONFIG environment variable must be an absolute pathname. Relative paths and environment variables are not allowed.
Correct the value for the TUXCONFIG environment variable to be an absolute pathname.
DMCONFIG (5)
While executing dmloadcf, the TUXCONFIG configuration file cannot be read to validate information in the DMCONFIG file.
Check for the existence of the TUXCONFIG file. If the file exists, make sure that the file and the directory can be accessed. If it does not exist, generate the TUXCONFIG file before running dmloadcf.
DMCONFIG (5)
As part of changing the domain password with the passwd command, the new password is encrypted before writing it to the BDMCONFIG file. This message is issued if the encryption algorithm fails.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
As part of changing the domain password with the passwd command, the new password is encrypted before writing it to the BDMCONFIG file. The two-way encryption algorithm requires an encryption schedule to be created for use by the encryption routine. This message is issued when the key used for encrypting the new password cannot be generated because memory for the key cannot be dynamically allocated from the operating system using malloc().
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.
DMCONFIG (5)
As part of changing the domain password with the passwd command, the new password is encrypted before writing it to the BDMCONFIG file. This message is issued if the encryption algorithm fails.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
While executing dmloadcf, the TUXCONFIG file cannot be accessed to validate BLOCKTIME in *DM_LOCAL_DOMAIN section of the DMCONFIG file.
Check to make sure that the file exists and the directory structure is accessible. If the TUXCONFIG file does not exist, create it first before running dmloadcf.
DMCONFIG (5)
The value of NWDEVICE in *DM_TDOMAIN section of the DMCONFIG file must be an absolute pathname. Relative paths and environment variables are not allowed.
Correct the value for the NWDEVICE to be an absolute pathname.
DMCONFIG (5)
The value of NWDEVICE in *DM_OSITP section of the DMCONFIG file must be an absolute pathname. Relative paths and environment variables are not allowed.
Correct the value for the NWDEVICE to be an absolute pathname.
DMCONFIG (5)
If APT in *DM_OSITP section of the DMCONFIG file is an object identifier, then AEQ for that entry must be an integer value.
Specify a valid value for AEQ and re-load the configuration.
DMCONFIG (5)
If APT in *DM_OSITP section of the DMCONFIG file is an object identifier, then AEQ for that entry must be an integer value.
Specify a valid value for AEQ and re-load the configuration.
DMCONFIG (5)
If RDOM and ROUTING are specified for a *DM_REMOTE_SERVICE entry in the DMCONFIG file, then all the requests will be sent to remote domain rdom. For rout to take effect, set RDOM to NULL.
No action required.
DMCONFIG (5)
When doing dmloadcf, if SECURITY is set to APP_PW in *RESOURCES section of UBBCONFIG file, then the administrator should enter the password before the BDMCONFIG file is over-written or created. This message indicates that if the standard input is not a terminal, then APP_PW environment variable should be set to the application password before running dmloadcf.
Correct the error and re-execute the batch command.
DMCONFIG (5)
If an application password is required, dmloadcf either prompts for it (if the invoker is attached to a terminal), or it reads from the environment variable, APP_PW, if standard input is not a terminal. This message is issued when the password cannot be obtained. The most common cause for this is that APP_PW is not set and standard input is not a terminal.
If dmloadcf is not attached to a terminal when invoked, then check that the environment variable, APP_PW, is set correctly.
DMCONFIG (5)
If SECURITY is set to APP_PW in *RESOURCES section of the TUXCONFIG file, and dmloadcf is run on the DMCONFIG file, the user must enter the application password before the BDMCONFIG file is created or over-written. dmloadcf attempted to read the key used for 2-way encryption from the protected file, $APPDIR/.adm/.keydb. This message is issued when an error is encountered reading this key from the key database file.
If APPDIR has been changed or $APPDIR/.adm/.keydb has been removed, re-load the TUXCONFIG file using tmloadcf which will create $APPDIR/.adm/.keydb. Then, run dmloadcf to create the BDMCONFIG file.
DMCONFIG (5)
An unexpected error occurred while trying to encrypt the application security password.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
If SECURITY is set to APP_PW in *RESOURCES section of the TUXCONFIG file, and dmloadcf is run on the DMCONFIG file, the user must enter the application password before the BDMCONFIG file is created or over-written. dmloadcf attempt to decrypt the application password failed.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
A failure occurred while processing the dmconfig file with the dmloadcf command. The application password given does not match the password established when the ubbconfig file was processed using the tmloadcf command.
Retry the operation and enter the correct password. Alternatively, you may use tmloadcf to process the ubbconfig file again and establish a new password.
DMCONFIG (5)
The value of NWADDR in *DM_TDOMAIN section of the DMCONFIG file must be unique.
Specify a valid value for NWADDR and re-load the configuration.
DMCONFIG (5)
There can only be one address specified for an OSITP domain. OSITP domain, ositp, has multiple addresses.
Delete one of the entries for ositp domain and re-load the configuration.
DMCONFIG (5)
If a domain is defined as TDOMAIN, you cannot specify OSITP addresses for it. If a domain is defined as OSITP, you cannot specify TDOMAIN addresses for it.
Correct the error and re-load the configuration.
DMCONFIG (5)
If entries in *DM_REMOTE_SERVICE section of the DMCONFIG file have the same LDOM value, then they should also have the same ROUTING criterion if RDOM is different.
Correct the error and re-load the configuration.
DMCONFIG (5)
The Gateway Administrative Server issues this message in response to the stats command which is used to toggle the statistics gathering functionality. This informational message indicates that statistics gathering has been reset.
This is an informational message with no associated user action.
DMADMIN (1)
While executing dmadmin, the TUXCONFIG file cannot be accessed to validate BLOCKTIME in *DM_LOCAL_DOMAIN section of the DMCONFIG file.
Check to make sure that the file exists and the directory structure is accessible. If the TUXCONFIG file does not exist, create it first before running dmloadcf.
DMCONFIG (5)
All remote domains listed in the ACLIST of *DM_ACCESS_CONTROL section of the DMCONFIG file must be of the same type, that is, TDOMAIN or OSITP.
Correct the error and re-load the configuration.
DMCONFIG (5)
An entry in *DM_LOCAL_SERVICES section of the DMCONFIG file referenced an undefined entry, aclname, in *DM_ACCESS_CONTROL section.
Correct the error and re-load the configuration.
DMCONFIG (5)
An error was detected while processing the dmconfig file using the dmloadcf command. The MTYPE= parameter in the *DM_LOCAL_DOMAINS section contains a value which is too long. The value for MTYPE must be less than or equal to length characters in length.
Correct the MTYPE= parameter and retry the operation.
DMCONFIG (5)
An error was detected while processing the dmconfig file using the dmloadcf command. The MTYPE= parameter in the *DM_REMOTE_DOMAINS section contains a value which is too long. The value for MTYPE must be less than or equal to length characters in length.
Correct the MTYPE= parameter and retry the operation.
DMCONFIG (5)
An error was detected while processing the dmconfig file using the dmloadcf command. A memory allocation failure was detected.
Attempt to identify and stop any extraneous processes to free up virtual memory on your system.
DMCONFIG (5)
The Domain Administrative server detected an error while trying to open the temporary edit file file name. This error may indicate a problem with the file permission settings or a problem with the file system.
Identify any problems with the file permission settings or file system.
DMADMIN (1)
The Domain Administrative server detected an error while trying to create the configuration environment. The environment variable FIELDTBLS could not be added to the environment.
This is an internal error with no associated user action. If the error persists, contact BEA TUXEDO System Technical Support.
DMADMIN (1)
The Domain Administrative server detected an error while trying to create the configuration environment. The environment variable TUXDIR was not defined or the Domain Administrative server could not obtain the environment variable TUXDIR.
Ensure that the environment variable TUXDIR is set in your environment to the absolute path for your BEA TUXEDO System software.
DMADMIN (1)
The Domain Administrative server detected an error while trying to create the configuration environment. The environment variable FLDTBLDIR could not be added to the environment.
This is an internal error with no associated user action. If the error persists, contact BEA TUXEDO System Technical Support.
DMADMIN (1)
The Domain Administrative server detected an error while trying to create the configuration environment. The field identifier could not be retrieved for field name TA_SRVGRP. The value of error code will give more details describing the cause of the error.
Refer to the FML documentation for a description of error code. Correct the source of the error and retry the operation.
DMADMIN (1)
When the /Domain gateway was booted, it found that another server on a different queue within the same group was already offering the same transaction coordination services that are offered by a /Domain gateway. This is an error, and the gateway process will exit.
/Domain gateway groups should not have a TMS server associated with them, since the TMS functionality is performed by the gateway itself. Modify the TUXCONFIG file so that the TMSNAME parameter is not included in the *GROUPS section of the configuration file for /Domain gateway groups.
ubbconfig (5), tmloadcf (1), tmconfig (1)
The current release of the /Domain software does not allow multiple domain gateways within the same group. Additional gateways beyond the first gateway will fail to boot.
No immediate action is required, but the TUXCONFIG file should be updated so that this error does not reoccur when the application is next booted. Only one /Domain gateway should be specified per group in the TUXCONFIG file. If a very high throughput application requires the use of more than one /Domain gateway, the gateways can be placed in separate server groups.
ubbconfig (5), tmloadcf (1)
A request of an invalid class has been routed to the DMADM server.
Contact BEA TUXEDO System Technical Support with the exact error message.
Failed to allocate dynamic memory necessary for processing the administrative request.
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.
While performing dynamic re-configuration for a local domain, the DMADM administrative server encountered an error. Check surrounding messages for specifics.
Correct the error and re-issue the request.
DMCONFIG (5)
An invalid operation was specified in the administrative request. The valid operations are GET, SET, and GETNEXT.
Specify the correct operation in the administrative request.
A request of an invalid class has been routed to the DMADM server.
If using Admin API, check that the Domain Admin is not being called directly. Contact BEA TUXEDO System Technical Support with the exact error message.
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).
Check if any GWADM server terminated abnormally. Restart any GWADM servers that died. The changes will be picked up by the restarting GWADMs.
DMCONFIG (5)
Failed to allocate memory necessary for processing the administrative request.
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 TUXEDO System Technical Support with the exact error message.
A request of an invalid class has been routed to the DMADM server.
If using Admin API, check that the Domain Admin is not being called directly. Contact BEA TUXEDO System Technical Support with the exact error message.
An invalid request buffer was passed to the Domain Admin server (DMADM).
Check the validity of all attributes of the request and also that the request buffer was an FML32 typed buffer. If message persists, contact BEA TUXEDO System Technical Support.
An invalid reply buffer was returned by core MIB modules, in response to the current request.
Contact BEA TUXEDO System Technical Support.
An invalid reply buffer was returned by core MIB modules, in response to the current request.
Contact BEA TUXEDO System Technical Support.
Failed to allocate memory necessary for processing the administrative request.
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 TUXEDO System Technical Support with the exact error message.
A request of an invalid class has been routed to the DMADM server.
If using Admin API, check that the Domain Admin is not being called directly. Contact BEA TUXEDO System Technical Support with the exact error message.
An invalid request buffer was passed to the Domain Admin server (DMADM).
Check the validity of all attributes of the request and also that the request buffer was an FML32 typed buffer. If message persists, contact BEA TUXEDO System Technical Support.
An invalid reply buffer was returned by core MIB modules, in response to the current request.
Contact BEA TUXEDO System Technical Support.
An invalid reply buffer was returned by core MIB modules, in response to the current request.
Contact BEA TUXEDO System Technical Support.
The transaction state corresponding to the (one of the) transaction(s) is invalid.
Contact BEA TUXEDO System Technical Support with exact message and events leading up to the message.
Failed to allocate memory necessary for processing the administrative request.
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 TUXEDO System Technical Support with the exact error message.
A request of an invalid class has been routed to the DMADM server.
If using Admin API, check that the Domain Admin is not being called directly. Contact BEA TUXEDO System Technical Support with the exact error message.
An invalid request buffer was passed to the Domain Admin server (DMADM).
Check the validity of all attributes of the request and also that the request buffer was an FML32 typed buffer. If message persists, contact BEA TUXEDO System Technical Support.
An invalid reply buffer was returned by core MIB modules, in response to the current request.
Contact BEA TUXEDO System Technical Support.
An invalid reply buffer was returned by core MIB modules, in response to the current request.
Contact BEA TUXEDO System Technical Support.
The generic MIB attributes specified in the request buffer are invalid.
Correct the generic MIB attributes in the request buffer and re-issue the request.
Failed to allocate memory necessary for processing the administrative request.
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 TUXEDO System Technical Support with the exact error message.
The TA_STATE attribute specified in the request buffer is invalid. Refer to the MIB(5) manual page for the class in question and check the allowable values for TA_STATE.
Correct the request buffer and re-issue the request.
Failed to encrypt the password specified. This may be due to a number of problems with the configuration files and other system files.
Contact BEA TUXEDO System Technical Support with the exact message, after sanity checks on the BEA TUXEDO Configuration files and Domain Configuration files.
A request of an invalid class has been routed to the DMADM server.
If using Admin API, check that the Domain Admin is not being called directly. Contact BEA TUXEDO System Technical Support with the exact error message.
An invalid request buffer was passed to the Domain Admin server (DMADM).
Check the validity of all attributes of the request and also that the request buffer was an FML32 typed buffer. If message persists, contact BEA TUXEDO System Technical Support.
An invalid reply buffer was returned by core MIB modules, in response to the current request.
Contact BEA TUXEDO System Technical Support.
An invalid reply buffer was returned by core MIB modules, in response to the current request.
Contact BEA TUXEDO System Technical Support.
When DMADM administrative server is booted, it manages a BDMCONFIG file. The BDMCONFIG file, however, does not exist or is not accessible.
Set a valid value for BDMCONFIG environment variable and restart the DMADM server.
DMCONFIG (5)
The BEA TUXEDO Configuration file indicated by the environment variable TUXCONFIG is not accessible.
Check for the presence of the $TUXCONFIG file and also check the permissions of the file along with permissions of directories in its pathname. Correct the problem and reboot the DMADM server.
The Gateway Administrative server (GWADM) for the indicated gateway group is of a different compatibility level than the Domain Admin server (DMADM).
Check that the GWADM server being executed is of the correct release/version number. Also check that for the DMADM server. If the GWADM server belongs to an incorrect version, reboot only the Gateway group with the correct GWADM server. If DMADM server belongs to an incorrect version, reboot the entire set of /Domain servers (DMADM, all GWADM(s), all Gateways) using the correct DMADM server.
The Domain Administrative server detected an error. The domain domain name is not active. The domain must be active for the operation to complete.
Activate the domain domain name and retry the operation.
DMADMIN (1)
The Gateway Administrative server detected an error during server initialization. The service service name is offered by more than one server in this domain. A service can be offered by no more than one server in a given domain.
Correct the domain configuration such that no service is offered by more than one server in the domain.
GWADM (5)
The Gateway Administrative server detected an error during server initialization. The Domain Administrative service service name is not advertised. The DMADM process must be booted before GWADM can be initialized.
Boot the Domain Administrative server DMADM and retry.
GWADM (5)
The Domain Administrative server detected an error while trying to create the configuration environment. An error occurred while trying to allocate virtual memory.
Attempt to identify and stop any extraneous processes to free up virtual memory on your system.
DMADMIN (1)
The Domain Administrative server detected an error while trying to process the modusr command. The modusr command must be processed under control of a terminal.
Retry the modusr command from a terminal.
DMADMIN (1)
The Domain Administrative server detected an error while trying to process the addumap command. The addumap command cannot set both the remote user and the local user to *.
Retry the addumap command with a valid argument.
DMADMIN (1)
The Domain Administrative server detected an error while trying to process the delumap command. The delumap command cannot set both the remote user and the local user to *.
Retry the delumap command with a valid argument.
DMADMIN (1)
The Domain Administrative server detected an internal error while trying to obtain a remote user password. This message is issued when using the dmadmin(1) command interpreter in configuration mode.
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.
DMADMIN (1)
The Domain Administrative server detected an error while trying to check a remote user password. This message is issued when using the dmadmin(1) command interpreter in configuration mode. The SECURITY= parameter in the *RESOURCES section of the ubbconfig(1) file is set to NONE. In order for this operation to complete the application security must be other than NONE.
Set the SECURITY= parameter in the *RESOURCES section of the UBBCONFIG(1) file to a valid value other than NONE and retry the operation.
ubbconfig (5) DMADMIN (1)
The Domain Administrative server detected an error while trying to add a remote user password. This message is issued when using the dmadmin(1) command interpreter in configuration mode. The server detected that it was not being run from a terminal.
Attempt the operation again by running dmadmin(1) from a terminal.
DMADMIN (1)
The Domain Administrative server detected an error while trying to update a remote user entry. This message is issued when using the dmadmin(1) command interpreter in configuration mode. The server found an invalid value for the TA_RPRINPASSWD tag in the edit buffer. In order to update a remote user entry the value should be set to U.
Retry the operation specifying the value U for TA_RPRINPASSWD.
DMADMIN (1)
The Domain Administrative server detected an error while trying to add a remote user entry. This message is issued when using the dmadmin(1) command interpreter in configuration mode. The server found an invalid value for the TA_RPRINPASSWD tag in the edit buffer. In order to add a remote user entry the value should be set to Y.
Retry the operation specifying the value Y for TA_RPRINPASSWD.
DMADMIN (1)
The Domain Administrative server detected an error while trying to add a remote user entry. This message is issued when using the dmadmin(1) command interpreter in configuration mode. The server found an invalid value for the TA_RPRINPASSWD tag in the edit buffer. In order to add a remote user entry the value should be set to Y.
Retry the operation specifying the value Y for TA_RPRINPASSWD.
DMADMIN (1)
The Domain Administrative server detected an internal error while trying to process the request.
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.
DMADMIN (1)
An error was detected while trying to load the dmconfig(5) file as a result of the dmloadcf command. The buffer type buffer type requires a subtype specification.
Correct the parameter specification in error and reload the configuration.
DMCONFIG (5)
An error was detected while trying to load the dmconfig(5) file as a result of the dmloadcf command. The buffer type buffer type requires a subtype specification.
Correct the parameter specification in error and reload the configuration.
DMCONFIG (5)
An error was detected while trying to load the dmconfig(5) file as a result of the dmloadcf command. The buffer type type specified is not a valid buffer type.
Replace the parameter specification in error with one of the valid buffer types listed above and reload the configuration.
DMCONFIG (5)
The BDMCONFIG file is a binary file in the BEA TUXEDO VTOC format. Each section of the BDMCONFIG file (*DM_RESOURCES, *DM_LOCAL_SERVICES, etc.) is stored as a separate table in the BDMCONFIG file. While trying to read the BDMCONFIG file, dmunloadcf got an error trying to open the *DM_SNADOM section.
Check the value of the BDMCONFIG environment variable. If it is the right value, the BDMCONFIG file may be corrupted. Re-generate the BDMCONFIG and re-execute the command.
DMCONFIG (5)
The passwd command must be run from a terminal as opposed to, say, a shell script, since dmadmin prompts for new passwords on the terminal.
Remove the use of the passwd command from any non-terminal invocations of dmadmin.
DMCONFIG (5)
An invalid password value was given (greater than 8 characters in length).
Retry the passwd command.
DMCONFIG (5)
The passwd command requires a new password to be entered and re-entered identically. If after three attempts this does not occur, the command fails and prints this error message.
Retry the passwd command.
DMCONFIG (5)
The passwd command requires a new password to be entered and re-entered identically. If after three attempts this does not occur, the command fails and prints this error message.
Retry the passwd command.
DMCONFIG (5)
As part of changing the domain password with the passwd command, the new password is encrypted before writing it to the BDMCONFIG file. This message is issued when the key used for encrypting the new password cannot be generated because memory for the key cannot be dynamically allocated from the operating system using malloc().
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.
DMCONFIG (5)
As part of changing the domain password with the passwd command, the new password is encrypted before writing it to the BDMCONFIG file. The two-way encryption algorithm requires an encryption schedule to be created for use by the encryption routine. This message is issued when the key used for encrypting the new password cannot be generated because memory for the key cannot be dynamically allocated from the operating system using malloc().
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.
DMCONFIG (5)
As part of changing the domain password with the passwd command, the new password is encrypted before writing it to the BDMCONFIG file. The two-way encryption algorithm requires an encryption schedule to be created for use by the encryption routine. This message is issued when the key used for encrypting the new password cannot be generated because memory for the key cannot be dynamically allocated from the operating system using malloc().
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.
DMCONFIG (5)
As part of changing the domain password with the passwd command, the new password is encrypted before writing it to the BDMCONFIG file. This message is issued if the encryption algorithm fails.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
As part of changing the domain password with the passwd command, the new password is encrypted before writing it to the BDMCONFIG file. This message is issued if the encryption algorithm fails.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
The Domain Administrative server detected an internal error while trying to obtain a remote user's password while processing either an addusr or modusr command.
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.
DMADMIN (1)
The Domain Administrative server detected an internal error while trying to obtain a remote user's password while processing an addusr command.
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.
DMADMIN (1)
The Domain Administrative server detected an internal error while trying to obtain a remote user's password while processing a modusr command.
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.
DMADMIN (1)
The Domain Administrative server detected an internal error while trying to obtain a remote user's password while processing either an addusr or a modusr command.
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.
DMADMIN (1)
The Gateway Administrative server detected an internal error while trying to process a dynamic reconfiguration. The *DM_SNADOM section of the bdmconfig file could not be opened.
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.
DMADMIN (1)
The Gateway Administrative server detected an internal error while trying to process a dynamic reconfiguration. The *DM_RDOMSEC section of the bdmconfig file could not be opened.
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.
DMADMIN (1)
The Domain Administrative server detected an internal error while trying to obtain a remote user password. This message is issued when using the dmadmin(1) command interpreter in configuration mode.
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.
DMADMIN (1)
An error was detected while trying to load the dmconfig(5) file as a result of the dmloadcf command. The VTOC could not be listed. A more specific error message will follow.
Check the surrounding messages for more detailed information. Correct the source of the error and reload the configuration.
DMCONFIG (5)
An error was detected while trying to load the dmconfig(5) file as a result of the dmloadcf command. The VTOC could not be read. A more specific error message will follow.
Check the surrounding messages for more detailed information. Correct the source of the error and reload the configuration.
DMCONFIG (5)
An error was detected while trying to load the dmconfig(5) file as a result of the dmloadcf command. The configuration could not be written. A more specific error message will follow.
Check the surrounding messages for more detailed information. Correct the source of the error and reload the configuration.
DMCONFIG (5)
An error was detected while trying to load the dmconfig(5) file as a result of the dmloadcf command. An invalid internet address was found.
Correct the parameter specification in error and reload the configuration.
DMCONFIG (5)
The Domain Administrative server issues this informational message to indicate that the password for principal principal name has been set to a default value of -1 as a result of an addusr command.
This is an informational message with no associated user action.
DMADMIN (1)
An error was detected while trying to load the dmconfig(5) file as a result of the dmloadcf command. The buffer type buffer type requires a subtype specification.
Correct the parameter specification in error and reload the configuration.
DMCONFIG (5)
An error was detected while trying to load the dmconfig(5) file as a result of the dmloadcf command. The SNA domain domain has more than one address.
Correct the parameter specification in error and reload the configuration.
DMCONFIG (5)
The Gateway Administrative server detected an internal error while trying to process a dynamic reconfiguration. The *DM_RDOMUSR section of the bdmconfig file could not be opened.
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.
DMADMIN (1)
The Gateway Administrative server detected an internal error while trying to process a dynamic reconfiguration. The *DM_OSITP section of the bdmconfig file could not be opened.
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.
DMADMIN (1)
The DMADM administrative server received a request to dynamically re-configure the application. The DMADM performs checks to make sure that the integrity of the data in the BDMCONFIG is kept in-contact before it performs any changes in the file. This message indicates that DMADM could not read the BDMCONFIG file to perform the data integrity checks. Make sure that the BDMCONFIG file still exists and is readable.
If the file does not exist, shut down the application and re-start it. If the file does exist, make it accessible and re-issue the request.
DMCONFIG (5)
The DMADM administrative server received a request to dynamically re-configure the application. The DMADM performs checks to make sure that the integrity of the data in the BDMCONFIG is kept in-contact before it performs any changes in the file. This message indicates that DMADM could not read the BDMCONFIG file to perform the data integrity checks. Make sure that the BDMCONFIG file still exists and is readable.
If the file does not exist, shut down the application and re-start it. If the file does exist, make it accessible and re-issue the request.
DMCONFIG (5)
The DMADM administrative server received a request to dynamically re-configure the application. The DMADM performs checks to make sure that the integrity of the data in the BDMCONFIG is kept in-contact before it performs any changes in the file. This message indicates that DMADM could not read the BDMCONFIG file to perform the data integrity checks. Make sure that the BDMCONFIG file still exists and is readable.
If the file does not exist, shut down the application and re-start it. If the file does exist, make it accessible and re-issue the request.
DMCONFIG (5)
The DMADM administrative server received a request to dynamically re-configure the application. The DMADM performs checks to make sure that the integrity of the data in the BDMCONFIG is kept in-contact before it performs any changes in the file. This message indicates that DMADM could not read the BDMCONFIG file to perform the data integrity checks. Make sure that the BDMCONFIG file still exists and is readable.
If the file does not exist, shut down the application and re-start it. If the file does exist, make it accessible and re-issue the request.
DMCONFIG (5)
The DMADM administrative server received a request to dynamically re-configure the application. The DMADM performs checks to make sure that the integrity of the data in the BDMCONFIG is kept in-contact before it performs any changes in the file. This message indicates that DMADM could not read the BDMCONFIG file to perform the data integrity checks. Make sure that the BDMCONFIG file still exists and is readable.
If the file does not exist, shut down the application and re-start it. If the file does exist, make it accessible and re-issue the request.
DMCONFIG (5)
The DMADM administrative server received a request to dynamically re-configure the application. The DMADM performs checks to make sure that the integrity of the data in the BDMCONFIG is kept in-contact before it performs any changes in the file. This message indicates that DMADM could not read the BDMCONFIG file to perform the data integrity checks. Make sure that the BDMCONFIG file still exists and is readable.
If the file does not exist, shut down the application and re-start it. If the file does exist, make it accessible and re-issue the request.
DMCONFIG (5)
The DMADM administrative server received a request to dynamically re-configure the application. The DMADM performs checks to make sure that the integrity of the data in the BDMCONFIG is kept in-contact before it performs any changes in the file. This message indicates that DMADM could not read the BDMCONFIG file to perform the data integrity checks. Make sure that the BDMCONFIG file still exists and is readable.
If the file does not exist, shut down the application and re-start it. If the file does exist, make it accessible and re-issue the request.
DMCONFIG (5)
When the GWADM administrative server is booted, it reads the TUXCONFIG file to determine the number of gateway processes in its group so that it can figure out the size of PROC table in shared memory. This message indicates that GWADM could not read the TUXCONFIG file. Make sure that the file still exists and is accessible.
If the file still exists, check the permissions. If it does not exist, restart the application.
DMCONFIG (5)
The GWADM administrative server could not create shared memory segment(s) to create hash tables for various sections in the DMCONFIG file. The GWADM creates a large segment and doles out portions of it for hash tables in the very beginning of the initialization procedure. This error should not occur normally.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
The GWADM administrative server first estimates the size of shared memory required for the domain, creates the shared memory, and then doles out pieces of it for various sections. This message indicates that the GWADM could not create one of the tables in shared memory because there was no space left in shared memory, and it could not create additional segments to hold the new table.
Change the UNIX IPC parameters, if needed, make the new kernel, reboot the machine, and then restart the application.
DMCONFIG (5)
The GWADM administrative server first loads the addresses for the local domain and then sets up links from the local domain information to its listening addresses. This message indicates that it could not set up the link. This message should only happen if the shared memory is corrupted for some reason.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
The Gateway Administrative server detected an internal error while trying to initialize.
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.
GWADM (5)
The GWADM administrative server could not allocate an entry in the PROC table. This message indicates that the gateway processes terminated without relinquishing their slot in the PROC table. This message should not occur normally.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
The GWADM administrative server first estimates the size of shared memory required for the domain, creates the shared memory, and then doles out pieces of it for various sections. This message indicates that the GWADM could not create one of the tables in shared memory because there was no space left in shared memory, and it could not create additional segments to hold the new table.
Change the UNIX IPC parameters, if needed, make the new kernel, reboot the machine, and then restart the application.
DMCONFIG (5)
The GWADM administrative server received a request to dynamically update the LOCAL DOMAIN entry. This message indicates that the update operation failed because it could not find the entry.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
The GWADM administrative server received a request to dynamically update the LOCAL DOMAIN entry. This message indicates that the update operation failed because it could not find the entry.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
The GWADM administrative server received a request to dynamically add a remote domain. The server, at first, adds an entry in the DOMAINID table for the given remote domain. This message indicates that the add operation failed. Check surrounding messages for specifics.
Correct the error and re-issue the request.
DMCONFIG (5)
The GWADM administrative server received a request to dynamically add a REMOTE DOMAIN entry. This message indicates that the add operation failed because it could not find an entry in the DOMAINID table it just added.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
The GWADM administrative server received a request to dynamically add a remote domain. The server, at first, adds an entry in the DOMAINID table for the given remote domain. Then, it adds an entry in the REMOTE DOMAIN table. This message indicates that the second add operation failed. Check surrounding messages for specifics.
Correct the error and re-issue the request.
DMCONFIG (5)
The GWADM administrative server received a request to dynamically add an address for a remote domain. This message indicates that the add operation succeeded but it failed to set up links from the added entry to the list of addresses.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
The GWADM administrative server received a request to dynamically add an address for a domain. This message indicates that add operation failed. Check surrounding messages for specifics.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
The GWADM administrative server received a request to dynamically add a listening address for the local domain. After successfully adding the entry in the address table, it links the new address to the list of addresses already existing in the shared memory. This message indicates that the GWADM server could not set up the links.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
The GWADM administrative server received a request to dynamically add a new address for a remote domain. After successfully adding the entry in the ADDRESS table, it links the new address to the list of addresses already existing in the shared memory. This message indicates that the GWADM server could not set up the links.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
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.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
The GWADM administrative server received a request to dynamically add a listening address for the local domain. After successfully adding the entry in the ADDRESS table, it links the new address to the list of addresses already existing in the shared memory. This message indicates that the GWADM server could not set up the links.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
The GWADM administrative server received a request to dynamically add a new address for a remote domain. After successfully adding the entry in the ADDRESS table, it links the new address to the list of addresses already existing in the shared memory. This message indicates that the GWADM server could not set up the links.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
The GWADM administrative server received a request to dynamically add a SNADOM entry. This message indicates that the add operation failed. Check surrounding messages for specifics.
Correct the error and re-issue the request.
DMCONFIG (5)
The GWADM administrative server received a request to dynamically add a new address for a remote domain. After successfully adding the entry in the ADDRESS table, it links the new address to the list of addresses already existing in the shared memory. This message indicates that the GWADM server could not set up the links.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
The GWADM administrative server received a request to dynamically add a new address for a remote domain. After successfully adding the entry in the ADDRESS table, it links the new address to the list of addresses already existing in the shared memory. This message indicates that the GWADM server could not set up the links.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
The GWADM administrative server received a request to dynamically add a LOCAL SERVICE entry. This message indicates that the add operation failed. Check surrounding messages for specifics.
Correct the error and re-issue the request.
DMCONFIG (5)
The GWADM administrative server received a request to dynamically add a LOCAL SERVICE entry. The add operation succeeded but GWADM failed to set up the link from the added entry to the entry in the ACL table.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
The GWADM administrative server received a request to dynamically delete a LOCAL SERVICE entry. This message indicates that the delete operation failed. Check the surrounding messages for specifics.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
The GWADM administrative server received a request to dynamically add a LOCAL SERVICE entry. The add operation succeeded but GWADM could not set up the link from the new entry to the ACL entry.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
The GWADM administrative server received a request to dynamically delete a LOCAL SERVICE entry. This message indicates that the delete operation failed. Check the surrounding messages for specifics.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
The GWADM administrative server received a request to dynamically add a LOCAL SERVICE entry. This message indicates that the add operation failed. Check surrounding messages for specifics.
Correct the error and re-issue the request.
DMCONFIG (5)
The GWADM administrative server received a request to dynamically add a LOCAL SERVICE entry. The add operation succeeded but GWADM failed to set up the link from the added entry to the entry in the ACL table.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
The GWADM administrative server received a request to dynamically add a REMOTE SERVICE entry. This message indicates that the add operation failed. Check surrounding messages for specifics.
Correct the error and re-issue the request.
DMCONFIG (5)
The GWADM administrative server received a request to dynamically add a REMOTE SERVICE entry. The add operation succeeded but GWADM failed to set up the link from the added entry to the entry in the RDOM and/or ROUTING entry.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
The GWADM administrative server received a request to dynamically delete a REMOTE SERVICE entry. This message indicates that the delete operation failed. Check the surrounding messages for specifics.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
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.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
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.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
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.
Correct the error and re-issue the request.
DMCONFIG (5)
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.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
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.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
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.
Correct the error and re-issue the request.
DMCONFIG (5)
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.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
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.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
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.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
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.
Correct the error and do an ADD operation this time.
DMCONFIG (5)
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.
Correct the error and re-issue the request.
DMCONFIG (5)
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.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
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.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
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.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
The Gateway Administrative server detected an internal error while trying to process a request. An RDOMSEC entry could not be added.
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.
GWADM (5)
The Gateway Administrative server detected an internal error while trying to process a request.
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.
GWADM (5)
The Gateway Administrative server detected an internal error while trying to process a request.
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.
GWADM (5)
The Gateway Administrative server detected an internal error while trying to process a request.
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.
GWADM (5)
The Gateway Administrative server detected an internal error while trying to process a request.
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.
GWADM (5)
The Gateway Administrative server detected an internal error while trying to process a request.
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.
GWADM (5)
The Gateway Administrative server detected an internal error while trying to process a request.
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.
GWADM (5)
The Gateway Administrative server detected an internal error while trying to process a request.
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.
GWADM (5)
The Gateway Administrative server detected an internal error while trying to process a request.
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.
GWADM (5)
The Gateway Administrative server detected an internal error while trying to process a request.
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.
GWADM (5)
The Gateway Administrative server detected an internal error while trying to process a request.
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.
GWADM (5)
An attempt dynamically to allocate memory from the operating system using malloc() failed.
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.
DMCONFIG (5)
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.
Correct the configuration such that only one GWADM is defined per group.
GWADM (5)
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.
Make sure that the shared memory segments have not been removed and the permissions are correct.
DMCONFIG (5)
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.
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.
DMCONFIG (5)
The Domain Administrative server detected an error while trying to register the Gateway Administrative server for the first time. The *DM_TDOMAIN section of the bdmconfig file could not be opened.
The configuration file may be corrupted. Reload the configuration from scratch.
DMCONFIG (5)
When the DMADM administrative server is booted, it manages a BDMCONFIG file. The environment variable must be set to an existing BDMCONFIG file.
Set and export the BDMCONFIG environment variable and restart the DMADM server.
DMCONFIG (5)
When the DMADM administrative server is booted, it manages a BDMCONFIG file. The BDMCONFIG file, however, does not exist or is not accessible.
Set a valid value for the BDMCONFIG environment variable and restart the DMADM server.
DMCONFIG (5)
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.
Shut down the application and re-generate the BDMCONFIG file.
DMCONFIG (5)
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.
Shut down the application and re-generate the BDMCONFIG file.
DMCONFIG (5)
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.
Shut down the application and re-generate the BDMCONFIG file.
DMCONFIG (5)
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.
Shut down the application and re-generate the BDMCONFIG file.
DMCONFIG (5)
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.
Shut down the application and re-generate the BDMCONFIG file.
DMCONFIG (5)
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_SERVICES section of the BDMCONFIG file. This indicates that the file is probably corrupted.
Shut down the application and re-generate the BDMCONFIG file.
DMCONFIG (5)
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.
Shut down the application and re-generate the BDMCONFIG file.
DMCONFIG (5)
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.
Shut down the application and re-generate the BDMCONFIG file.
DMCONFIG (5)
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.
Contact BEA TUXEDO System Technical Support.
DMCONFIG (5)
An attempt dynamically to allocate memory from the operating system using malloc() failed.
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.
DMCONFIG (5)
The DMADM administrative server could not send the initial configuration information to a GWADM for the local domain corresponding to the group, grp.
Make sure that the BDMCONFIG file still exists and is accessible.
DMCONFIG (5)
The DMADM administrative server could not process a request to register from a GWADM administrative server. Check surrounding messages for specifics.
Correct the error and re-boot the application.
DMCONFIG (5)
The DMADM administrative server could not send the section numbered section_num to the GWADM administrative server corresponding to group, grp.
Make sure that the BDMCONFIG file still exists and is accessible.
DMCONFIG (5)
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.
No action required.
DMCONFIG (5)
An attempt dynamically to allocate memory from the operating system using malloc() failed.
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.
DMCONFIG (5)
While performing dynamic re-configuration for a local domain, the DMADM administrative server encountered an error. Check surrounding messages for specifics.
Correct the error and re-issue the request.
DMCONFIG (5)
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).
Check if any GWADM server terminated abnormally. Restart any GWADM servers that died. The changes will be picked up by the restarting GWADMs.
DMCONFIG (5)
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.
No action required.
DMCONFIG (5)
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.
Shut down the application and re-generate the BDMCONFIG file.
DMCONFIG (5)
An attempt was made to boot more than one DMADM server. This is not supported.
No action required.
DMCONFIG (5)
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.
Make sure that $APPDIR is set in the environment or set $BDMCONFIG in the environment explicitly.
DMCONFIG (5)
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.
No action required. You can explicitly create a configuration using dmloadcf(1).
dmloadcf (1), DMCONFIG (5)
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.
Shut down the application and re-generate the BDMCONFIG file.
DMCONFIG (5)
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.
Shut down the application and re-generate the BDMCONFIG file.
DMCONFIG (5)
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.
Shut down the application and re-generate the BDMCONFIG file.
DMCONFIG (5)
An error occurred while retrieving the local domain entry in table.
Contact BEA TUXEDO System Technical Support.
An error occurred while retrieving the current license attributes.
Check the log for prior messages indicating the cause of the problem. Normally, it means that the product has not been licensed properly.
You do not have a license to use /T Domains.
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.
You do not have a license to use Domains compression.
Purchase a license for Domains compression.
An error was detected while processing the dmconfig file using the dmloadcf command. A memory allocation failure was detected.
Attempt to identify and stop any extraneous processes to free up virtual memory on your system.
DMCONFIG (5)
An error was detected while processing the dmconfig file using the dmloadcf command. A memory allocation failure was detected.
Attempt to identify and stop any extraneous processes to free up virtual memory on your system.
DMCONFIG (5)
The /Domain configuration file in the DM_LOCAL_SERVICES section contains entry which map a /T internal system service to an user accessible service name.
Correct the error in the /Domain configuration, and re-run dmloadcf.
The /Domain configuration file in the DM_REMOTE_SERVICES section contains entry which map a /T internal system service to an user accessible service name.
Correct the error in the /Domain configuration, and re-run dmloadcf.
The /Domain configuration in the DM_LOCAL_SERVICES section contains entry which map a /T system service to an user accessible service name.
Correct the error in the /Domain configuration, and re-run dmloadcf.
The /Domain configuration in the DM_REMOTE_SERVICES section contains entry which map a /T system service to an user accessible service name.
Correct the error in the /Domain configuration, and re-run dmloadcf.
User trying to dynamically add or change a local service which use RNAME to map a /T internal system service to an user accessible service.
Correct the error.
User trying to dynamically add or change a local service which use RNAME to map a /T system service to an user accessible service.
Correct the error.
User trying to dynamically add or change a remote service which use RNAME to map a /T internal system service to an user accessible service.
Correct the error.
User trying to dynamically add or change a remote service which use RNAME to map a /T system service to an user accessible service.
Correct the error.
An attempt to dynamically allocate memory from the operating system using malloc() failed while parsing the DMCONFIG file.
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.
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).
Correct the value and re-run dmloadcf(1).
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).
Correct the value and re-run dmloadcf(1).
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).
Correct the value and re-run dmloadcf(1).
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).
Correct the value and re-run dmloadcf(1).
An attempt to dynamically allocate memory from the operating system using malloc() failed while parsing the DMCONFIG file.
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.
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.
Correct the value in the DMCONFIG file as appropriate and retry the operation.
DMCONFIG (5)
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.
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).
DMCONFIG (5) dmunloadcf (1) dmloadcf (1)
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 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.
Correct the value in the DMCONFIG file as appropriate and retry the operation.
DMCONFIG (5)
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.
Correct the value in the DMCONFIG file as appropriate and retry the operation.
DMCONFIG (5)
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 proviously 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.
Correct the value in the DMCONFIG file as appropriate and retry the operation.
DMCONFIG (5)
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.
Correct the value in the DMCONFIG file as appropriate and retry the operation.
DMCONFIG (5)
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 refererced by a prior *DM_SNALINKS section entry. There must be a one-to-one corresponse between *DM_SNALINKS sections and remote domains sections of type SNAX.
Correct the value in the DMCONFIG file as appropriate and retry the operation.
DMCONFIG (5)
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.
Correct the value in the DMCONFIG file as appropriate and retry the operation.
DMCONFIG (5)
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.
Correct the value in the DMCONFIG file as appropriate and retry the operation.
DMCONFIG (5)
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.
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.
GWADM (5)
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.
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.
GWADM (5)
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.
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.
GWADM (5)
The dmadmin(1) dynamic configuration utility detected an error. A system error prevented the process from creating a temporary file needed for the operation.
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.
dmadmin(1)
The dmunloadcf(1) utility detected an error. A system error prevented the process from opening the specified output file file name.
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.
dmunloadcf(1)
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.
Correct the value in the DMCONFIG file as appropriate and retry the operation.
DMCONFIG (5)
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.
Correct the entry in the *DM_OSITP section and retry the operation.
dmloadcf(1)
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.
Correct the entry in the *DM_OSITP section and retry the operation.
dmloadcf(1)
The dmloadcf(1) utility detected an error while processing the DMCONFIG(5) file. The MAX_LISTENING_EP parameter in the *DM_OSITP section specified a value which is out of the accepted range. The MAX_LISTENING_EP parameter must be within the range of 0 to 32767.
Correct the value of the MAX_LISTENING_EP parameter in the *DM_OSITP section and retry the operation.
dmloadcf(1)
The dmloadcf(1) utility detected an error while processing the DMCONFIG(5) file. The MAX_LISTENING_EP parameter in the *DM_OSITP section specified a value which is out of the accepted range. The MAX_LISTENING_EP parameter must be within the range of 0 to 32767.
Correct the value of the MAX_LISTENING_EP parameter in the *DM_OSITP section and retry the operation.
dmloadcf(1)
The dmloadcf(1) utility detected an error while processing the DMCONFIG(5) file. The XATMI_ENCODING parameter in the *DM_OSITP section specified an invalid string value. The XATMI_ENCODING parameter must be one of either PRELIMINARY, UNISYS, OLTP_TM2200, or CAE.
Correct the value of the XATMI_ENCODING parameter in the *DM_OSITP section and retry the operation.
dmloadcf(1)
The dmloadcf(1) utility detected an error while processing the DMCONFIG(5) file. The XATMI_ENCODING parameter in the *DM_OSITP section entry for domain name specified an invalid string value value. The XATMI_ENCODING parameter must be one of either PRELIMINARY, UNISYS, OLTP_TM2200, or CAE.
Correct the value of the XATMI_ENCODING parameter in the *DM_OSITP section and retry the operation.
dmloadcf(1)
The Domain Administrative Server (DMADM) detected an error while processing MIB(5) request. The Local Domain / Remote Domain pair ldom / rdom specified is incorrect. The domain types for both ldom and rdom must match.
Correct the values of ldom and/or rdom and retry the operation.
dmadmin(1) MIB(5)