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

CMDGW Messages 1500-1599

1501	ERROR: Invalid value
	Description	The named value is invalid. Check surrounding messages for specifics.
	Action	Correct the value in the DMCONFIG file as appropriate, according to surrounding messages.
	See Also	dmconfig(5)
1503	ERROR: TUXCONFIG environment variable not set
	Description	While executing dmloadcf, the TUXCONFIG environment variable has not been set and exported.
	Action	Set and export the TUXCONFIG environment variable and re-execute the command.
	See Also	dmconfig(5)
1504	ERROR: TUXCONFIG environment variable must be an absolute pathname
	Description	The value of the TUXCONFIG environment variable must be an absolute pathname. Relative paths and environment variables are not allowed.
	Action	Correct the value for the TUXCONFIG environment variable to be an absolute pathname.
	See Also	dmconfig(5)
1505	ERROR: Error in reading TUXCONFIG file
	Description	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.
	Action	Set TUXCONFIG to the appropriate filename. Make sure that the file and the directory structure is accessible by the user running dmloadcf.
	See Also	dmconfig(5)
1506	ERROR: Configuration too big. Ran out of memory. (IC = number)
	Description	An attempt to allocate dynamic memory from the operating system using malloc failed while parsing the configuration file.
	Action	Make sure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine, or increase the amount of physical memory on the machine, or increase the amount of virtual memory that a process can allocate for various sections (data, stack, vmemory, etc).
1507	ERROR: Can't have duplicate name section. (IC = number)
	Description	All the sections in the DMCONFIG file can be defined only once.
	Action	Remove the second definition of the section or merge it into the first definition and then re-load the configuration.
1511	ERROR: Value of name must be string number. (IC = number)
	Description	Value of the parameter should conform to the restrictions stated above.
	Action	Edit the DMCONFIG file to change the value of the specified parameter and then re-load the configuration.
1512	ERROR: write failed (vtoc_errno = vtoc_errno)
	Description	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.
	Action	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.
	See Also	dmconfig(5)
1513	ERROR: Can't open section_name section.(vtoc_errno = number)
	Description	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.
	Action	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.
1514	ERROR: Section string must appear before the name section. (IC = number)
	Description	The sections must appear in the order specified in the dmconfig(5) description.
	Action	Rearrange the sections such that they are in the proper order and then re-load the configuration.
	See Also	dmconfig(5)
1515	ERROR: write failed (vtoc_errno=vtoc_errno)
	Description	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.
	Action	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.
	See Also	dmconfig(5)
1516	ERROR: Group name grpname not associated with GWADM server in TUXCONFIG file
	Description	The GWGRP specified, grpname, in the DM_LOCAL_DOMAIN section of the DMCONFIG file must have a GWADM server listed in the UBBCONFIG file.
	Action	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.
	See Also	dmconfig(5)
1517	ERROR: Domain Type domain_type not found in $TUXDIR/udataobj/DMTYPE file
	Description	The domain type, domain_type, specified is not found in the system file. This file should not be modified by non-source customers.
	Action	If you are a binary-only customer, read the file from the install tape. If you are a source customer, call Technical Support.
	See Also	dmconfig(5)
1519	ERROR: Value of parameter must contain hexadecimal digits
	Description	The stated parameter was specified as a hexadecimal number (starting with 0x or \\\\x), but a non-hexadecimal character was encountered in the string.
	Action	Enter hexadecimal characters in the stated parameter and re-load the configuration.
	See Also	dmconfig(5)
1520	ERROR: Value of parameter must contain an even number of hex digits
	Description	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.
	Action	Correct the value to have an even number of hexadecimal characters and re-load the configuration.
	See Also	dmconfig(5)
1521	ERROR: Invalid parameter: Entry in section (domain_name) appears more than once
	Description	Entries in the specified section have to be unique by the domain name.
	Action	Choose another name for one of the unique keys duplicated.
	See Also	dmconfig(5)
1522	ERROR: Invalid parameter: Entry in section (domainid) appears more than once
	Description	domainid must be unique across local and remote domains.
	Action	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.
	See Also	dmconfig(5)
1523	ERROR: AUDITLOG file filename must be an absolute pathname
	Description	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.
	Action	Replace the current AUDITLOG parameter with the full pathname of the file, for example, "Domain_appDomain_AUDIT.LOG".
	See Also	dmconfig(5)
1525	ERROR: Value of string "parameter" must be expr len characters in length (IC = number)
	Description	The string parameter specified has a length that is greater than the specified maximum number of characters.
	Action	Correct the string in the DMCONFIG file to be less than or equal to len characters.
	See Also	dmconfig(5)
1527	ERROR: Identifier ident must be expr len characters in length. (IC = number)
	Description	The identifier, ident, has a length that is greater than the maximum number of characters.
	Action	Correct the identifier in the DMCONFIG file to be less than or equal to the len characters.
	See Also	dmconfig(5)
1528	ERROR: APP_PW requires password to be specified in TUXCONFIG file
	Description	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.
	Action	Set SECURITY (in *RESOURCES section) to APP_PW in UBBCONFIG, run tmloadcf on the UBBCONFIG file, and then run dmloadcf on the DMCONFIG file.
	See Also	dmconfig(5)
1529	ERROR: USER_PW requires USER_AUTH, ACL, or ACL_MANDATORY to be specified in TUXCONFIG file
	Description	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.
	Action	Change the value in the DMCONFIG file or modify TUXCONFIG as appropriate.
	See Also	dmconfig(5)
1531	ERROR: Must specify param parameter in section section. (IC = number)
	Description	A value is required for parameter, param, in section section.
	Action	Specify a value for the parameter, param, in the section and then re-load the configuration.
	See Also	dmconfig(5)
1532	ERROR: Domain Type string not found in $TUXDIR/udataobj/DMTYPE file
	Description	The domain type specified is not found in the system file $TUXDIR/udataobj/DMTYPE. This file should not be modified by non-source customers.
	Action	If you are a binary-only customer, read the file from the install tape. If you are a source customer, call Technical Support.
	See Also	dmconfig(5)
1535	ERROR: ACN(string) can only be either XATMI or UDT
	Description	The value of ACN parameter in DM_OSITP section of the DMCONFIG file can only be set to either XATMI or UDT.
	Action	Choose a valid value for ACN and re-load the configuration.
	See Also	dmconfig(5)
1536	ERROR: PROFILE can only be one of the following: (ATP11, ATP21, ATP31, ATP12, ATP22, ATP32)
	Description	The value of PROFILE in DM_OSITP section of the DMCONFIG file can only be set to one of the above values.
	Action	Choose a valid value for PROFILE and re-load the configuration.
	See Also	dmconfig(5)
1537	ERROR: Invalid parameter: Entry in string (string) was not defined previously
	Description	Domain name is referenced in other section(s) without it being defined in DM_LOCAL_DOMAIN or DM_REMOTE_DOMAIN of the DMCONFIG file.
	Action	Define the domain name first before referencing it and re-load the configuration.
	See Also	dmconfig(5)
1538	ERROR: Cannot have more than max_rdom entries in ACLIST
	Description	You cannot specify more than max_rdom remote domains per ACL.
	Action	Reduce the number of remote domains specified for this ACL entry and re-load the configuration.
	See Also	dmconfig(5)
1539	ERROR: Invalid option string
	Description	The option specified is not a valid option to the dmloadcf command.
	Action	Correct the options to the dmloadcf command as per the usage message.
	See Also	dmconfig(5)
1541	ERROR: Current work directory path name is too long
	Description	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.
	Action	Check that the directory has the proper permissions and is not longer than 78 characters, and re-execute the command.
	See Also	dmconfig(5)
1542	ERROR: Absolute path name of the input file is too long
	Description	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.
	Action	Choose a shorter pathname for the input file and re-execute the command.
	See Also	dmconfig(5)
1543	ERROR: Can't open file string
	Description	While executing dmloadcf, the specified input file cannot be opened.
	Action	Check that the input (DMCONFIG) file exists and is readable and re-execute the command.
	See Also	dmconfig(5)
1544	ERROR: string: Parse failed
	Description	While executing dmloadcf, an error occurred parsing the input DMCONFIG file.
	Action	Earlier warning error messages will indicate the nature of the error. Correct these problems and re-execute the command.
	See Also	dmconfig(5)
1545	ERROR: string: Severe error found. Stop syntax checking.
	Description	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.
	Action	Earlier warning error messages will indicate the nature of the error. Correct these problems and re-execute the command.
	See Also	dmconfig(5)
1546	ERROR: string: Above errors found during syntax checking
	Description	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.
	Action	Earlier warning error messages will indicate the nature of the error. Correct these problems and re-execute the command.
	See Also	dmconfig(5)
1547	ERROR: Can't open file filename
	Description	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.
	Action	Check that this file still exists and has read permission. Re-execute the command.
	See Also	dmconfig(5)
1548	ERROR: string: Error found in yyparse
	Description	While executing dmloadcf, an error was found during the second pass of parsing the input.
	Action	Re-execute the command. If the problem happens again, contact BEA TUXEDO system Technical Support.
	See Also	dmconfig(5)
1549	INFO: BDMCONFIG file filename has been created
	Description	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).
	Action	No action required.
	See Also	dmconfig(5)
1550	INFO: BDMCONFIG file filename has been updated
	Description	While executing dmloadcf, the input DMCONFIG file has been processed and an existing BDMCONFIG file has been updated with the information.
	Action	No action required.
	See Also	dmconfig(5)
1551	ERROR: BDMCONFIG environment variable not set
	Description	While executing dmloadcf, the BDMCONFIG environment variable has not been set and exported.
	Action	Set and export the BDMCONFIG environment variable and re-execute the command.
	See Also	dmconfig(5)
1552	ERROR: BDMOFFSET environment variable must >= 0
	Description	While executing dmloadcf, the BDMOFFSET environment variable is not set correctly to a non-negative integer offset.
	Action	Set and export the BDMOFFSET environment variable to a non-negative integer offset and re-execute the command.
	See Also	dmconfig(5)
1553	ERROR: BDMCONFIG not set or incorrectly set
	Description	While executing dmloadcf, an error occurred in checking the BDMCONFIG file.
	Action	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.
	See Also	dmconfig(5)
1554	ERROR: The value of -b option (number) is too small.
	Description	While executing dmloadcf, the size specified for the -b option on the command is too small to hold the configuration.
	Action	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.
	See Also	dmconfig(5)
1555	ERROR: BDMCONFIG file needs at least nblocks size-byte blocks
	Description	While executing dmloadcf, the size specified for the -b option on the command is too small to hold the configuration.
	Action	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.
	See Also	dmconfig(5)
1556	ERROR: Can't create BDMCONFIG file
	Description	While executing dmloadcf, creation of the BDMCONFIG file failed.
	Action	A subsequent system message will indicate the nature of the failure. Correct the problem and re-execute the command.
	See Also	dmconfig(5)
1557	INFO: A new file system has been created. (size = nblocks size-byte blocks)
	Description	While executing dmloadcf, a new BDMCONFIG file or device was created with the specified size, nblocks.
	Action	No action required.
	See Also	dmconfig(5)
1558	ERROR: Can't create tablename
	Description	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.
	Action	A subsequent system message will indicate the nature of the failure. Correct the problem and re-execute the command.
	See Also	dmconfig(5)
1559	ERROR: Can't open tablename
	Description	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.
	Action	A subsequent system message will indicate the nature of the failure. Correct the problem and re-execute the command.
	See Also	dmconfig(5)
1560	ERROR: Can't write section_name
	Description	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.
	Action	This is an internal error with no associated user action. If the error persists, contact BEA TUXEDO system Technical Support.
	See Also	dmconfig(5)
1561	ERROR: dmloadcf cannot run on an active node
	Description	While executing dmloadcf, the configuration file could not be loaded because the application is active.
	Action	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.
	See Also	dmconfig(5)
1563	ERROR: BDMCONFIG file not created: exiting
	Description	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.
	Action	No action required.
	See Also	dmconfig(5)
1565	ERROR: BDMCONFIG file not updated: exiting
	Description	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.
	Action	No action required.
	See Also	dmconfig(5)
1567	ERROR: Error reading string section from BDMCONFIG
	Description	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.
	Action	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.
	See Also	dmconfig(5)
1576	ERROR: Invalid option string
	Description	The option specified is not a valid option to the dmunloadcf command.
	Action	Correct the options to the dmunloadcf command as per the usage message.
	See Also	dmconfig(5)
1578	ERROR: Invalid argument: string
	Description	dmunloadcf(1) The offending option is printed with this error message.
	Action	Verify options to dmunloadcf and re-execute the command.
	See Also	dmconfig(5)
1583	ERROR: BDMCONFIG environment variable not set
	Description	While executing dmloadcf, the BDMCONFIG environment variable has not been set and exported.
	Action	Set and export the BDMCONFIG environment variable and re-execute the command.
	See Also	dmconfig(5)
1584	ERROR: BDMCONFIG environment variable must be an absolute pathname.
	Description	The value of the BDMCONFIG environment variable must be an absolute pathname. Relative paths and environment variables are not allowed.
	Action	Correct the value for the BDMCONFIG environment variable to be an absolute pathname.
	See Also	dmconfig(5)
1585	ERROR: _dmcf_open failed: Can't open DM_RESOURCES section
	Description	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.
	Action	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.
	See Also	dmconfig(5)
1586	ERROR: _dmcf_open failed: Can't open DM_LOCAL_DOMAINS section
	Description	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.
	Action	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.
	See Also	dmconfig(5)
1587	ERROR: _dmcf_open failed: Can't open DM_REMOTE_DOMAINS section
	Description	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.
	Action	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.
	See Also	dmconfig(5)
1588	ERROR: _dmcf_open failed: Can't open DM_TDOMAIN section
	Description	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.
	Action	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.
	See Also	dmconfig(5)
1589	ERROR: _dmcf_open failed: Can't open DM_OSITP section
	Description	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.
	Action	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.
	See Also	dmconfig(5)
1590	ERROR: _dmcf_open failed: Can't open DM_ACCESS_CONTROL section
	Description	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.
	Action	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.
	See Also	dmconfig(5)
1591	ERROR: _dmcf_open failed: Can't open DM_LOCAL_SERVICES section
	Description	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.
	Action	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.
	See Also	dmconfig(5)
1592	ERROR: _dmcf_open failed: Can't open DM_REMOTE_SERVICES section
	Description	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.
	Action	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.
	See Also	dmconfig(5)
1593	ERROR: _dmcf_open failed: Can't open DM_ROUTING section
	Description	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.
	Action	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.
	See Also	dmconfig(5)
1594	ERROR: _dmcf_open failed: Can't open DM_OSITPX section
	Description	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.
	Action	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.
	See Also	dmconfig(5)
1595	ERROR: If ACN = XATMI, then PROFILE has to be one of the following: ATP11, ATP21, ATP31
	Description	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.
	Action	Choose a valid value for PROFILE and re-load the configuration.
	See Also	dmconfig(5)
1597	ERROR: AET=<string> is in an invalid format (IC = number)
	Description	The value of AET in DM_OSITP section of the DMCONFIG file is in invalid format.
	Action	Specify a valid value for AET and re-load the configuration.
	See Also	dmconfig(5)
1598	ERROR: AUTOTRAN(string) can only be either Y or N
	Description	The value of AUTOTRAN in DM_REMOTE_SERVICES section of the DMCONFIG file can be either Y or N.
	Action	Specify a valid value and re-load the configuration.
	See Also	dmconfig(5)
1599	ERROR: CONV(string) can only be either Y or N
	Description	The value of CONV in DM_REMOTE_SERVICES section of the DMCONFIG file can be either Y or N.
	Action	Specify a valid value and re-load the configuration.
	See Also	dmconfig(5)