TMADMIN MESSAGES 400 & Above

TMADMIN MESSAGES 400-499

473 ERROR: Error reading file filename

DESCRIPTION

An attempt to read a saved Bulletin Board failed.

ACTION

The BB may be the wrong size or corrupted, or the specified file may not be a saved BB.

474 ERROR: Error setting auth type to CLIENT

DESCRIPTION

An attempt to open a saved Bulletin Board file failed.

ACTION

Check to see that the specified file exist and that you have read permission.

475 ERROR: Error setting bb type to PRIVATE

DESCRIPTION

An attempt to attach to a saved bulletin board failed.

ACTION

Contact your TUXEDO System Technical Support.

476 ERROR: Error attaching to private bulletin board

DESCRIPTION

An attempt to attach to a saved bulletin board failed.

ACTION

Contact your TUXEDO System Technical Support.

477 ERROR: Error opening file filename

DESCRIPTION

An attempt to open a saved bulletin board failed.

ACTION

Contact your TUXEDO System Technical Support.

494 ERROR: Cannot stop processes from non-master node

DESCRIPTION

The shutdown command invokes tmshutdown (1) to shut down processes. Because tmshutdown (1) needs access to the DBBL for successful processing, it must run on the master node (that is, where the DBBL resides).

ACTION

Consult the MASTER keyword of the *RESOURCES section of the ubbconfig (5) file to determine your application's master node. This is the node on which tmadmin (1)'s shutdown command must be executed. Note that if the master command was previously executed, the DBBL may be running on the backup node instead. In this case, the shutdown command must be executed from tmadmin (1) running on the backup node.

498 ERROR: The new value is not within the range of min-max

DESCRIPTION

This message is printed when an illegal value has been given to one of the changeload, changepriority, or changetrantime commands of tmadmin(1). Service loads must be between 1 and 32767, inclusive; service priorities must be between 1 and 100, inclusive; and transaction times must be between 0 and 2,147,483,647, inclusive.

ACTION

Re-enter the command using a value within the appropriate range. The SERVICES section of the ubbconfig (5) manual page describes the correct ranges and defaults for these service attributes.

499 ERROR: Error changing value

DESCRIPTION

An error was encountered trying to update a service's priority with the changepriority command, or its transaction timeout value with the changetrantime command. This error may have occurred because of a communication failure between tmadmin (1) and the DBBL or one of the BBLs.

ACTION

Check the userlog (3) file to see if a communication error occurred that caused the requested command to fail.

TMADMIN MESSAGES 500-599

512 ERROR: Cannot create device devname, start val, size val on val

DESCRIPTION

Creation of a new device using crdl failed. The parameters to the creation are printed.

ACTION

Check to ensure that you have write permission on the device, that tlid values are specified, and that the slice does not overlap with an existing device (use the lidl command to check existing devices).

515 WARN: Not destroyed

DESCRIPTION

While executing dsdl to destroy a device list entry, a "yes" answer was not provided to the prompt to ensure that the operation should be done.

ACTION

No action required.

516 ERROR: Cannot list device devindex on config-file

DESCRIPTION

While destroying a device using dsdl, the specified index on the configuration file could not be listed.

ACTION

Use the lidl command to see what devices are available and specified a valid device index.

517 ERROR: Cannot destroy device index on device

DESCRIPTION

While destroying a device using dsdl, the specified index on the configuration file could not be destroyed. This could occur for many reasons including the file is being updated by another process, entry 0 is being destroyed and other files or device entries exist, or an I/O error occurred.

ACTION

For device entry 0, use litc and livtoc to ensure that other entries don't exist. Re-try the operation.

520 WARN: Not re-initialized

DESCRIPTION

While executing indir to re-initialize a configuration, a "yes" answer was not provided to the prompt to ensure that the operation should be done. This operation wipes out all files and device entries for the file - use with care!

ACTION

No action required.

521 ERROR: Can't open file

DESCRIPTION

While executing indir to re-initialize a configuration file, the specified file could not be opened. This operation wipes out all files and device entries for the file - use with care!

ACTION

Make sure that the proper value was specified for the -z option and that the file has read and write permission.

523 ERROR: Can't write file

DESCRIPTION

While executing indir to re-initialize a configuration file, the specified file could not be updated. This operation wipes out all files and device entries for the file - use with care!

ACTION

Make sure that the proper value was specified for the -z option and that the file has read and write permission.

526 WARN: Not initialized

DESCRIPTION

While executing indl to re-initialize a decide list entry, a "yes" answer was not provided to the prompt to ensure that the operation should be done.

ACTION

Contact your TUXEDO System Technical Support.

527 ERROR: Cannot list device index on file

DESCRIPTION

While executing indl to initialize a device list entry, an error occurred while reading information about the entry.

ACTION

Check to see that the file is a valid TUXEDO configuration file, that you have read permission, and that the index is valid (use lidl).

528 ERROR: Cannot re-initialize device index on file

DESCRIPTION

While executing indl to initialize a device list entry, an error occurred while reading information about the entry. This operation frees up all space on that entry - don't do this operation if TUXEDO tables are using space on the entry. Freeing up entry 0 clears all other device entries - use with care!

ACTION

Check to see that the file is a valid TUXEDO configuration file, that you have write permission, and that the index is valid (use lidl). Another program may have the file locked for update.

530 ERROR: Device list not initialized

DESCRIPTION

The lidl was executed for a configuration device that was not initialized.

ACTION

Make sure the device specified with the -z option is correct. If it has not already been initialized, use the crdl command to initialize it and create a device entry.

539 ERROR: Can't get vtoc on device

DESCRIPTION

The livtoc was executed for a configuration device that was not initialized or for which the user does not have access permissions.

ACTION

Make sure the device specified with the -z option is correct, and that you have read permissions. If it has not already been initialized, you must also have update permissions, and you should use the crdl command to initialize the device and create a device entry.

544 WARN: No entries found

DESCRIPTION

A "printgroup" or "pg" was executed but no groups were found to match the specified group (-g) or machine (-m) options, or no groups exist.

ACTION

No action required.

552 ERROR: Migration not allowed

DESCRIPTION

The "migg" or "migrategroup" command was executed but the application is not configured with the MIGRATE option set.

ACTION

Change the configuration to have the MIGRATE option, and configure backup machines.

553 ERROR: Invalid group name

DESCRIPTION

The "migg" or "migrategroup" command was executed but an invalid group name was specified.

ACTION

Use the pg command to print a list of valid group names.

554 ERROR: Error occurred (errval): Check ULOG file

DESCRIPTION

A "migg" or "migrategroup" command was executed but the operation failed.

ACTION

Check the event log for messages indicating the nature of the failure.

555 ERROR: Migration time out: Check ULOG file

DESCRIPTION

A "migg" or "migrategroup" command was executed but the operation did not complete within the configured timeout value.

ACTION

Check the event log for messages indicating the state of the migration. It may still complete after the time-out occurs.

557 ERROR: Migration not allowed

DESCRIPTION

The "migm" or "migratemach" command was executed but the application is not configured with the MIGRATE option set.

ACTION

Change the configuration to have the MIGRATE option, and configure backup machines.

558 ERROR: Invalid machine name

DESCRIPTION

The "migm" or "migratemach" command was executed but an invalid machine name was specified.

ACTION

Use the pg command to print a list of valid group names and their associated machine names.

559 ERROR: Error occurred (errval): Check ULOG file

DESCRIPTION

A "migm" or "migratemach" command was executed but the operation failed.

ACTION

Check the event log for messages indicating the nature of the failure.

560 ERROR: Migration time out: Check ULOG file

DESCRIPTION

A "migm" or "migratemach" command was executed but the operation did not complete within the configured timeout value.

ACTION

Check the event log for messages indicating the state of the migration. It may still complete after the time-out occurs.

562 ERROR: Not running on Master

DESCRIPTION

The crlog or crlg command was run but not from the configured master machine.

ACTION

Execute the command from the configured master machine.

563 ERROR: Can't get log information

DESCRIPTION

The crlog or crlg command was executed but the log information for the specified or default machine could not be found.

ACTION

Make sure that the TUXCONFIG file is loaded and that the machine name specified is valid.

564 ERROR: TLOGDEVICE must be specified

DESCRIPTION

The crlog or crlg command was executed but the configuration for the specified machine does not have a TLOGDEVICE specified.

ACTION

Change the configuration for the machine to define a TLOGDEVICE file.

565 ERROR: remote log creation failed

DESCRIPTION

The crlog or crlg command was executed for a remote machine but the operation failed. This is most often because tlisten(1) is not running on the remote machine.

ACTION

Make sure tlisten is running on the remote machine. Check the event log on the local and remote machine for related messages.

566 ERROR: local log creation failed

DESCRIPTION

The crlog or crlg command was executed for the local machine but the operation failed.

ACTION

Check the event log on the local for related messages.

568 ERROR: can't open dump file - errno = errval

DESCRIPTION

The dumptlog or dl command was executed but the output file could not be created and opened. The errno value is printed.

ACTION

Check the errno value to determine the reason for the fopen() failure. It may be that you don't have permissions on the directory or the file, or a lack of resources (files or space).

569 ERROR: command failed, check ULOG file for message

DESCRIPTION

The dumptlog or dl command was executed but getting information about the associated log file failed.

ACTION

Check the event log for the prior failure message (_gp_litbl).

570 ERROR: command failed, check ULOG file for message

DESCRIPTION

The dumptlog or dl command was executed but opening the transaction log file failed.

ACTION

Check the event log for the prior failure message.

571 ERROR: command failed, check ULOG file for message

DESCRIPTION

The dumptlog or dl command was executed but reading the transaction log file failed.

ACTION

Check the event log for the prior failure message (_gp_tblread).

572 ERROR: command failed, check ULOG file for message

DESCRIPTION

The dumptlog or dl command was executed but updating the transaction log file failed.

ACTION

Check the event log for the prior failure message (_gp_tblwrite).

573 ERROR: Tmdumptlog: Page num skipped, chksum unmatch

DESCRIPTION

While processing a dl or dumptlog command, a page was found in the transaction log that was invalid. The page is skipped and processing continues.

ACTION

Contact your TUXEDO System Technical Support.

575 ERROR: command failed, check ULOG file for message

DESCRIPTION

The dumptlog or dl command was executed but reading a page from the transaction log file failed.

ACTION

Check the event log for the prior failure message (_gp_tblread).

576 ERROR: command failed, check ULOG file for message

DESCRIPTION

The dumptlog or dl command was executed but reading a page from the transaction log file failed.

ACTION

Check the event log for the prior failure message (_gp_tblread).

579 ERROR: Not running on Master

DESCRIPTION

The dslog or dslg command was run but not from the configured master machine.

ACTION

Execute the command from the configured master machine.

580 ERROR: Not enough log information

DESCRIPTION

The dslog or dslg command was executed but the log information for the specified or default machine could not be found, or a TLOGDEVICE was not configured.

ACTION

Make sure that the TUXCONFIG file is loaded and that the machine name specified is valid. Change the configuration for the machine to define a TLOGDEVICE file.

581 ERROR: Application is still active

DESCRIPTION

The dslog or dslg command was executed but the one or more servers are still active.

ACTION

Shutdown the application and re-run the command.

583 ERROR: Not destroyed

DESCRIPTION

While executing dslog or dslg to destroy a transaction log, a "yes" answer was not provided to the prompt to ensure that the operation should be done.

ACTION

No action required.

584 ERROR: remote log destroy failed

DESCRIPTION

The dslog or dslg command was executed for a remote machine but the operation failed. This is most often because tlisten(1) is not running on the remote machine.

ACTION

Make sure tlisten is running on the remote machine. Check the event log on the local and remote machine for related messages.

585 ERROR: tlog_destroy failed

DESCRIPTION

The dslog or dslg command was executed for the local machine but the operation failed.

ACTION

Check the event log on the local for related messages.

587 ERROR: Not running on Master

DESCRIPTION

The inlog or inlg command was run but not from the configured master machine.

ACTION

Execute the command from the configured master machine.

588 ERROR: Not enough log information

DESCRIPTION

The inlog or inlg command was executed but the log information for the specified or default machine could not be found, or a TLOGDEVICE was not configured.

ACTION

Make sure that the TUXCONFIG file is loaded and that the machine name specified is valid. Change the configuration for the machine to define a TLOGDEVICE file.

589 ERROR: Application is still active

DESCRIPTION

The inlog or inlg command was executed but the one or more servers are still active.

ACTION

Shutdown the application and re-run the command.

591 ERROR: remote log init failed

DESCRIPTION

The inlog or inlg command was executed for a remote machine but the operation failed. This is most often because tlisten(1) is not running on the remote machine.

ACTION

Make sure tlisten is running on the remote machine. Check the event log on the local and remote machine for related messages.

592 ERROR: tlog_reinit failed

DESCRIPTION

The inlog or inlg command was executed for the local machine but the operation failed.

ACTION

Check the event log on the local for related messages.

594 ERROR: The system is not active

DESCRIPTION

The loadtlog command was executed but the application is not currently active or there is an error in finding the master machine.

ACTION

Check the event log for messages related to the failure.

595 ERROR: loadtlog failed, can't open tlog file

DESCRIPTION

The loadtlog command was executed but the transaction log file could not be opened for reading/writing.

ACTION

Check that the file specified is valid (e.g., that the directory and file specified exists and has read and write permission). Check for limited resources (out of files or disk space).

596 ERROR: can't write tlog dump file - errno = val

DESCRIPTION

The loadtlog command was executed but the status of the transaction log file could not be determined.

ACTION

Contact your TUXEDO System Technical Support.

597 ERROR: loadtlog failed, can't get msgbuf. tperrno = sub

DESCRIPTION

An attempt dynamically to allocate memory from the operating system failed while trying to load a transaction log.

ACTION

Make sure 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.

598 ERROR: loadtlog failed, can't read logfile. errno = val

DESCRIPTION

The loadtlog command was executed but a read of the transaction log file failed.

ACTION

Make sure that the file specified is a valid transaction log. The file is character-based and can be read using any text editor.

599 ERROR: can't close tlog dump file - errno = errno.

DESCRIPTION

The loadtlog command was executed. After reading the transaction log, the close of the file failed.

ACTION

This error is ignored and processing continues. No action required.

TMADMIN MESSAGES 600-699

600 ERROR: error during send/receive of remote procedure call

DESCRIPTION

While processing a loadtlog command, processing the administrative message failed.

ACTION

Check the event log for related problems. Re-try the command.

601 ERROR: loadtlog failed, tperrno = val

DESCRIPTION

While processing a loadtlog command, processing the administrative message failed.

ACTION

Check the event log for related problems. Re-try the command.

602 ERROR: loadtlog failed, tperrno = val

DESCRIPTION

While processing a loadtlog command, processing the administrative message failed.

ACTION

Check the event log for related problems. Re-try the command.

604 ERROR: The system is not active

DESCRIPTION

The warmstart command was executed but the application is not currently active or there is an error in finding the master machine.

ACTION

Check the event log for messages related to the failure.

605 ERROR: tlog warmstart failed, tperrno = val

DESCRIPTION

An attempt dynamically to allocate memory from the operating system failed while trying to warmstart a transaction log.

ACTION

606 ERROR: error during send/receive of remote procedure call

DESCRIPTION

While processing a warmstart command, processing the administrative message failed.

ACTION

Check the event log for related problems. Re-try the command.

607 ERROR: tlog warmstart failed, tperrno = val

DESCRIPTION

While processing a warmstart command, processing the administrative message failed.

ACTION

Check the event log for related problems. Re-try the command.

608 ERROR: tlog warmstart failed, tperrno = val

DESCRIPTION

While processing a warmstart command, processing the administrative message failed.

ACTION

Check the event log for related problems. Re-try the command.

610 ERROR: Invalid tranindex value

DESCRIPTION

The transaction index passed to the aborttrans command is invalid.

ACTION

Use the printtrans command to find the correct index for the transaction that you wish to abort. Note that the transaction will not be reported by printtrans if it has already been either committed or aborted.

611 INFO: No RM users in transaction

DESCRIPTION

The transaction passed to the aborttrans command has not been aborted. The transaction is not associated with any group that accesses an XA-compliant resource manager. Thus, the transaction has not yet been assigned a coordinating group.

ACTION

See the description of the aborttrans command for details on how to remove a transaction for the system.

612 ERROR: Use printtrans to check results

DESCRIPTION

The transaction passed to the aborttrans command may not have been aborted due to a timeout communicating with a TMS.

ACTION

The printtrans command should be used to check the results of the aborttrans operation.

613 ERROR: aborttrans: error errorcode; use printtrans to check results

DESCRIPTION

The transaction passed to the aborttrans command may not have been aborted due to an error communicating with a TMS. This error may occur, for example, when using the -g option to the aborttrans command for a group that has no TMSs booted.

ACTION

The printtrans command should be used to check the results of the aborttrans operation.

614 ERROR: Invalid tranindex value

DESCRIPTION

The transaction index passed to the committrans command is invalid.

ACTION

Use the printtrans command to find the correct index for the transaction that you wish to commit. Note that the transaction will not be reported by printtrans if it has already been either committed or aborted.

615 ERROR: Use printtrans to check results

DESCRIPTION

The transaction passed to the committrans command may not have been committed due to a timeout communicating with a TMS .

ACTION

The printtrans command should be used to check the results of the committrans operation.

616 ERROR: committrans: error error; use printtrans to check results

DESCRIPTION

The transaction passed to the committrans command may not have been committed due to an error communicating with a TMS. This error may occur, for example, when trying to commit a transaction at a group that has no TMSs booted. Also, this error can occur if the transaction has been marked abort-only.

ACTION

The printtrans command should be used to check the results of the committrans operation.

618 INFO: No transaction entries to print

DESCRIPTION

This message is printed when the maximum number of global transaction table entries (MAXGTT) defined in the ubbconfig (5) file is 0.

ACTION

No action required.

619 ERROR: make msg failed, tperrno = errno

DESCRIPTION

An attempt dynamically to allocate memory from the operating system using malloc() failed in the printconn command. The printconn command failed.

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.

620 ERROR: Error during send/receive of remote procedure call

DESCRIPTION

An error occurred during the printconn command trying to contact a BBL. tmadmin retrieves connection information from each node in the system by contacting the BBL on every node.

ACTION

Issue the bbclean command to ensure that all connections with remote sites are in working order. Also, issue the printnet command which reports on any links with remote sites that are partitioned.

629 INFO: No outstanding transactions

DESCRIPTION

No transaction entries were found after scanning the transaction tables for the specified machines and groups.

ACTION

No action required.

644 INFO: Not destroyed

DESCRIPTION

The transaction log specified to the inlog command was not initialized because the appropriate affirmative response was not given at the prompt to initialize the log.

ACTION

No action required.

646 ERROR: can't read TLOG, different release

DESCRIPTION

The dl or dumptlog was executed but the release of the current program does not match the release of the program that wrote the log.

ACTION

Use tmadmin from the release that created the log to dump the transaction log.

TMADMIN MESSAGES 1000-1099

1073 ERROR: Gateway server failed, tperrno=val

DESCRIPTION

While executing a command to access information about foreign services, an error occurred in the /Domain gateway. The associated tperrno value is printed.

ACTION

Check the event log for related information.

1074 ERROR: Foreign host failed, hosterrno=val

DESCRIPTION

While executing a command to access information about foreign services, an error occurred at the foreign host. The associated host error value is printed.

ACTION

Check the event log for related information.

1075 ERROR: Remote procedure call failed, tperrno=val

DESCRIPTION

While executing a command to access information about foreign services, an error occurred. The associated tperrno value is printed.

ACTION

Currently, this error cannot occur.

1076 ERROR: Illegal return code, rtn=val

DESCRIPTION

While executing the a command to access information about foreign services, an invalid error occurred.

ACTION

This error should not occur, call TUXEDO Support.

1077 ERROR: printservice (psc) request failed, service=val

DESCRIPTION

While executing printservice or psc for a foreign service, the request failed.

ACTION

Look for earlier messages regarding the nature of the failure.

1078 ERROR: stats service request failed

DESCRIPTION

While executing the stats command to print statistical information about foreign services, an error occurred.

ACTION

See earlier messages about the nature of the failure.

1091 ERROR: Partial success: Check ULOG

DESCRIPTION

An error prevented the migrategroup command from succeeding. The exact nature of the error was written to the userlog (3). This message is usually the result of a network partition occurring during the migration.

ACTION

See the userlog (3) for the exact reason that the migrategroup command failed. Also, use the printnet command to see the status of all machine connections in the network. This command reports any network partitions.

1092 ERROR: Partial success: Check ULOG

DESCRIPTION

An error prevented the migratemach command from succeeding. The exact nature of the error was written to the userlog (3). This message is usually the result of a network partition occurring during the migration.

ACTION

See the userlog (3) for the exact reason that the migratemach command failed. Also, use the printnet command to see the status of all machine connections in the network. This command will report any network partitions.

1099 ERROR: Foreign administrative service not allowed

DESCRIPTION

It is an error to specify the foreign administrative service name to tmadmin 's stats command. This command will show statistical information pertaining only to application service names.

ACTION

Try the stats command again with another service name, or leave off the -s option to see statistical information for all the application service names.

TMADMIN MESSAGES 1100-1199

1106 ERROR: Could not determine level of authentication required.

DESCRIPTION

When tmadmin starts up, it calls tpchkauth (3) to see what level of authentication is required by the application. This message is issued when tpchkauth (3) fails. tpchkauth (3) can fail if tmadmin cannot find the TUXCONFIG file.

ACTION

Make sure the TUXCONFIG environment variable is set correctly.

1107 ERROR: Memory allocation failure.

DESCRIPTION

An attempt dynamically to allocate memory from the operating system using malloc() failed. When tmadmin initializes, it calls tpalloc () to get an initial buffer for tpinit (). When this message is issued, tpalloc ()'s call to malloc() failed.

ACTION

1108 ERROR: Could not find entry for user number.

DESCRIPTION

When tmadmin is invoked, the invoker's login id is used as the "User Name" when tmadmin joins the application. If there is an error retrieving the invoker's login id from the system password file, this message is printed.

ACTION

Contact your system administrator to ensure that your password entry contains your user id (uid) and your login.

1110 ERROR: Unable to obtain application password.

DESCRIPTION

If an application password is required, tmadmin either prompts for it (if the invoker is attached to a terminal), or it reads it 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.

ACTION

If tmadmin is not attached to a terminal when invoked, then check that the environment variable, APP_PW , is set correctly.

1130 ERROR: Broadcast failed, tperrno = tperrno

DESCRIPTION

The broadcast command failed. This tmadmin command called the ATMI verb tpbroadcast (3) which encountered an error.

ACTION

The error number, tperrno, that is printed with this message can be used to look up the exact error on the ATMI tpbroadcast (3) manual page. The mapping of the numeric value of tperrno to the symbolic constant shown on the tpbroadcast (3) manual page can be found in the intro (3) manual page or in $TUXDIR/include/atmi.h. SEE ALSO tmadmin (1), intro (3)

1131 ERROR: Memory allocation failure, tperrno = number

DESCRIPTION

An attempt dynamically to allocate memory from the operating system using malloc () failed. The broadcast command calls tpalloc() to allocate a typed buffer for text to be broadcast. When this message is issued, tpalloc ()'s call to malloc() failed.

ACTION

1134 ERROR: make msg failed, tperrno = number

DESCRIPTION

An attempt dynamically to allocate memory from the operating system using malloc () failed. When this message is issued, the attempt by the printclient command to allocate memory for retrieving client information failed. The printclient command calls tpalloc() which in turn calls malloc ().

ACTION

1135 ERROR: error during send/receive of remote procedure call

DESCRIPTION

An error occurred during the printclient command trying to retrieve client information from a BBL. tmadmin retrieves client information by contacting BBLs.

ACTION

Issue the bbclean command to ensure that all connections with remote sites are in working order. Also, issue the printnet command which reports on any links with remote sites that are partitioned.

1143 WARN: Application security not enabled

DESCRIPTION

The passwd command cannot be used 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 an application password can be assigned.

ACTION

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 assigned to your application using the passwd command.

1144 ERROR: The passwd command must be run from the terminal

DESCRIPTION

The passwd command must be run from a terminal as opposed to, say, a shell script, since tmadmin prompts for a new password on the terminal.

ACTION

Remove the use of the passwd command from any non-terminal invocations of tmadmin .

1146 ERROR: Error obtaining Application Password

DESCRIPTION

The passwd command failed because tmadmin could not open the terminal device (/dev/tty) for reading.

ACTION

Contact your TUXEDO System Technical Support.

1148 ERROR: Error obtaining Application Password

DESCRIPTION

The passwd command failed because tmadmin could not open the terminal device (/dev/tty) for reading.

ACTION

Contact your TUXEDO System Technical Support.

1150 ERROR: Too many failed attempts

DESCRIPTION

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 message.

ACTION

Retry the passwd command.

1151 ERROR: Memory allocation failure, tperrno = number

DESCRIPTION

An attempt dynamically to allocate memory from the operating system using malloc() failed. When this message is issued, the attempt by the passwd command to allocate memory for sending the new passwd to the DBBL failed. The passwd command calls tpalloc () which in turn calls malloc (). The application password is not changed.

ACTION

1152 ERROR: Passwd update failed

DESCRIPTION

The passwd command requests the DBBL to change the application password to the new password. The request could not be processed by the DBBL . The most likely reason for the failure is that the request could not be sent to the DBBL . The application password is not changed.

ACTION

Check the userlog (3) file to see if a communication error occurred that caused the requested command to fail.

1173 ERROR: -b option: argument must be numeric.

DESCRIPTION

When the -b option is used as an argument to a tmadmin command, its argument must be a numeric value.

ACTION

Try the command again with a numeric value for the -b option.

1174 ERROR: Memory allocation failure

DESCRIPTION

An attempt dynamically to allocate memory from the operating system using malloc() failed. When this message is issued, the attempt by the printdomain command to allocate memory for requesting host domain-specific information failed. The printdomain command calls tpalloc (), which in turn calls malloc ().

ACTION

1175 ERROR: printdomain (pd) service request failed, group=groupname queue=queuename

DESCRIPTION

The printdomain command failed to send a request for information to a gateway group due to a communication error. The printdomain command continues to send requests to other gateway groups.

ACTION

Check the userlog (3) to see if a communication error occurred that caused the requested command to fail.

1178 ERROR: could not retrieve server group entry

DESCRIPTION

The printdomain command failed to retrieve a gateway group's addressing information while preparing to send the group a request for information.

ACTION

Check the userlog (3) to see if a communication error occurred that caused the requested command to fail.

1179 ERROR: make msg failed, tperrno = number

DESCRIPTION

An attempt dynamically to allocate memory from the operating system using malloc () failed while preparing to send a message to a host gateway group.

ACTION

1180 ERROR: could not send message to gateway server, tperrno = number

DESCRIPTION

An error was encountered while trying to send a message to a host gateway group. The issued command fails.

ACTION

See the userlog (3) file for the exact reason that the command failed. Also, use the printnet command to see the status of all machine connections in the network. This command reports any network partitions.

1181 ERROR: error receiving reply from gateway server, tperrno = number

DESCRIPTION

A host administration command was issued and successfully sent to one or more gateway servers. However, an error occurred retrieving the response. A timeout waiting for the reply or a network failure may have occurred.

ACTION

Check the userlog (3) to see if a communication error occurred that prevented the reply from reaching tmadmin .

1182 ERROR: did not receive successful reply from gateway, tperrno = tperrno

DESCRIPTION

A host administration command was issued and successfully sent to one or more gateway servers. However, the reply contains an error that is reflected in the variable, tperrno.

ACTION

The error number, tperrno, that is printed with this message can be used to look up the exact error. The mapping of the numeric value of tperrno to a symbolic constant can be found in the intro (3) manual page or in $TUXDIR/include/atmi.h .

1184 ERROR: Service GATE_ADMIN not offered

DESCRIPTION

A tmadmin command was issued for one or more host gateway servers. However, there are no gateways currently offering the GATE_ADMIN service which is required for host related administrative requests. Either no gateway servers have been booted, or the CLOPT specified in the ubbconfig file for the gateway servers do not have the -A option specified.

ACTION

If there are gateways servers currently running, use the printservice command to see whether the GATE_ADMIN service is offered. If it is not, then make sure that the gateway servers offer this service either by dynamically advertising it (via the advertise command) or by adding the -A option to the CLOPT in the ubbconfig file.

1185 ERROR: Queue specified by -q option not part of group specified by -g option

DESCRIPTION

For those host-related tmadmin commands where both a queue and a group can be specified, this message is issued when the queue specified does not belong to the specified group.

ACTION

Use the printserver command to determine the correct queue and group combinations, and re-issue your command.

1186 ERROR: Server with ID serverid not offered on queue queuename

DESCRIPTION

For those host-related tmadmin commands where both a queue and a server id can be specified, this message is issued when the server specified does not read from the queue specified.

ACTION

Use the printserver command to determine the correct queue and server id combinations, and re-issue your command.

1187 ERROR: Service GATE_ADMIN not offered

DESCRIPTION

ACTION

1198 ERROR: -i option: argument must be numeric.

DESCRIPTION

When the -i option is used as an argument to a tmadmin command, its argument must be a numeric value.

ACTION

Try the command again with a numeric value for the -i option.

1199 ERROR: -o option: argument must be numeric.

DESCRIPTION

When the -o option is used as an argument to a tmadmin command, its argument must be a numeric value.

ACTION

Try the command again with a numeric value for the -o option.

TMADMIN MESSAGES 1200-1299

1200 ERROR: -O option: argument must be numeric.

DESCRIPTION

When the -O (upper case Oh) option is used as an option to a tmadmin command, its argument must be a numeric value.

ACTION

Try the command again with a numeric value for the -O option.

1230 ERROR: error during send/receive of remote procedure call

DESCRIPTION

An error occurred when the printclient command tried to retrieve client information from a BBL. tmadmin retrieves client information by contacting BBLs.

ACTION

Issue the bbclean command to ensure that all connections with remote sites are in working order. Also, issue the printnet command, which reports on any links with remote sites that are partitioned.

1231 ERROR: failure on remote procedure call

DESCRIPTION

An error occurred when the printclient command tried to retrieve client information from a BBL. tmadmin retrieves client information by contacting BBLs.

ACTION

See the userlog (3) for the exact reason that the printclient command failed.

1232 ERROR: error during send/receive of remote procedure call

DESCRIPTION

An error occurred when the printconn command tried to retrieve connection information from a BBL. tmadmin retrieves connection information by contacting BBLs.

ACTION

Issue the bbclean command to ensure that all connections with remote sites are in working order. Also, issue the printnet command, which reports on any links with remote sites that are partitioned.

1233 ERROR: failure on remote procedure call

DESCRIPTION

An error occurred when the printconn command tried to retrieve connection information from a BBL. tmadmin retrieves connection information by contacting BBLs.

ACTION

Issue the bbclean command to ensure that all connections with remote sites are in working order. Also, issue the printnet command, which reports on any links with remote sites that are partitioned.

1234 ERROR: Memory allocation failure

DESCRIPTION

An attempt dynamically to allocate memory from the operating system failed while executing the shmstats command.

ACTION

1235 ERROR: Memory allocation failure

DESCRIPTION

An attempt dynamically to allocate memory from the operating system failed while executing the shmstats command.

ACTION

1236 ERROR: Memory allocation failure

DESCRIPTION

An attempt dynamically to allocate memory from the operating system failed while executing the shmstats command.

ACTION

1246 ERROR: Client information could not be retrieved from site lmid

DESCRIPTION

While executing the printclient or pclt command, the specified target machine is suspended.

ACTION

Re-try the command when the machine is available again.

1274 ERROR: Connection information could not be retrieved from site machine

DESCRIPTION

While executing the printconn command in tmadmin , the specified machine, machine, was found to be partitioned and no connection information could be retrieved.

ACTION

If information for all machines is being retrieved, then information from other available machines will be printed. The specified machine must be reconnected via the tmadmin reconnect command, possibly after restarting the application on that machine.

1291 ERROR: TUXCONFIG must be an absolute pathname.

DESCRIPTION

When executing tmadmin, the TUXCONFIG environment variable is not a rooted (full) pathname.

ACTION

Re-set the TUXCONFIG value to a rooted path for the configuration file.

1292 ERROR: FSCONFIG must be an absolute pathname.

DESCRIPTION

When executing tmadmin, the FSCONFIG environment variable is set but not a rooted (full) pathname.

ACTION

Re-set the FSCONFIG value to a rooted path or unset the value. file.

1293 ERROR: -z option must be an absolute pathname.

DESCRIPTION

A command was executed with the -z option but the specified configuration pathname was not an absolute pathname.

ACTION

Re-run the command specifying a full pathname for the device (for example, on a POSIX operating system, it must start with a forward slash (/)).

1294 ERROR: New device must be an absolute pathname.

DESCRIPTION

While executing the crdl command, new device name is not a rooted pathname.

ACTION

Re-try the command with a full pathname for the new device.

1295 ERROR: Failure return from command - 0xretval, errno val.

DESCRIPTION

The execution of command (tmboot, tmshutdown, or tmconfig) failed. The return value of the command and the errno value are printed. Additional information may be printed on the standard error output.

ACTION

Check for additional information messages. Make sure that the PATH includes TUXDIR/bin.

1300 ERROR: can't become a client - tpinit() failed - string

DESCRIPTION

Execution of tmadmin failed because the user could not join the application. The printed string indicates the reason for the failure. This message can be printed either because no more clients can join the application or because the user failed security permissions.

ACTION

If the reason is that no more clients can join the application, re-try the operation a later time. The system should be configured to allow for more clients.

If a security problem occurs, the command must be run by the TUXEDO administrator.

1301 ERROR: Foreign host already booted, hosterrno=sub

DESCRIPTION

A command to boot a foreign host with foreign services was executed when the host was already booted.

ACTION

This operation cannot be done from tmadmin, thus it cannot occur.

1302 ERROR: Foreign host already shutdown, hosterrno=sub

DESCRIPTION

A command to shutdown a foreign host with foreign services was executed when the host was already shut down.

ACTION

This operation cannot be done from tmadmin, thus it cannot occur.

1303 ERROR: Unlicensed TUXEDO System Binary

DESCRIPTION

An attempt was made to execute tmadmin in an unlicensed TUXEDO binary.

ACTION

Contact your TUXEDO System Technical Support.

1304 ERROR: Expired TUXEDO System Binary

DESCRIPTION

An attempt was made to execute tmadmin in an expired TUXEDO binary.

ACTION

Contact your TUXEDO System Technical Support.

1315 ERROR: Memory allocation failure, tperrno = error_info

DESCRIPTION

An attempt dynamically to allocate memory from the operating system failed while executing changetrance or chtr. Additional information about the problem is printed as part of the message.

ACTION

1316 ERROR: Can't change trace configuration on machine lmid

DESCRIPTION

A failure occurred while trying to change the tracing configuration on the specified machine.

ACTION

Check the event log for related messages.

1318 ERROR: Can't change trace configuration of server name in group groupname

DESCRIPTION

A failure occurred while trying to change the tracing configuration on the specified server and group.

ACTION

Check the event log for related messages.

1320 ERROR: Update of trace configuration to R4.2 machine not supported

DESCRIPTION

The chtr or changetrace command was executed for a machine that is running a release earlier than 5.0. This feature was not supported on those releases.

ACTION

No action required.

1321 ERROR: Invalid trace specification

DESCRIPTION

The trace specified for the chtr or changetrace command was not valid syntax.

ACTION

Correct the syntax and re-run the command

1322 ERROR: Trace specification too long

DESCRIPTION

The trace specified for the chtr or changetrace command was greater than 78 characters in length.

ACTION

Change the trace specification and re-run the command.

1323 ERROR: Update of trace configuration for server name in group groupname on R4.2 machine not supported

DESCRIPTION

The chtr or changetrace command was executed for a server on a machine that is running a release earlier than 5.0. This feature was not supported on those releases.

ACTION

No action required.

1324 ERROR: Can't change trace configuration of server name in group groupname

DESCRIPTION

A failure occurred while trying to change the tracing configuration on the specified server and group.

ACTION

Check the event log for related messages.

1326 ERROR: You must print the transaction table (printtrans) before aborting it

DESCRIPTION

The aborttrans or at command was executed before executing printtrans. The information from printtrans is needed to specify an index of the entry to be aborted.

ACTION

Execute the printtrans command and then the aborttrans command.

1327 ERROR: You must print the transaction table (printtrans) before committing it

DESCRIPTION

The committrans or ct command was executed before executing printtrans. The information from printtrans is needed to specify an index of the entry to be committed.

ACTION

Execute the printtrans command and then the committrans command.

1330 INFO: Command: string

DESCRIPTION

All commands that are not read-only or boot (or quit) are written to the event log as a trace of administrative actions that are done.

ACTION

No action required.

1331 ERROR: Could not send message to tlisten

DESCRIPTION

While trying to execute crlog to create a transaction log on a remote machine, tmadmin was unable to contact the tlisten on the remote machine.

ACTION

Check that tlisten is running on the remote machine. Check the event log for related messages.

1332 ERROR: Could not send message to tlisten

DESCRIPTION

While trying to execute dslg to destroy the transaction log on a remote machine, tmadmin was unable to contact the tlisten on the remote machine.

ACTION

Check that tlisten is running on the remote machine. Check the event log for related messages.

1333 ERROR: Could not send message to tlisten

DESCRIPTION

While trying to execute inlog to re-initialize the transaction log on a remote machine, tmadmin was unable to contact the tlisten on the remote machine.

ACTION

Check that tlisten is running on the remote machine. Check the event log for related messages.

1341 ERROR: Size of Shared Memory file is too large for the existing SHMID

DESCRIPTION

An attempt to load a file into shared memory via "loadmem" failed because the size of the file was too large for the existing shared memory id.

ACTION

Re-create (if possible) the file that is being loaded with the correct size.

1344 ERROR: Invalid IPCKEY. IPCKEY must be between 32768 and 262143.

DESCRIPTION

The IPCKEY that was used was not in the valid range of keys. Valid keys are between 32768 and 262143.

ACTION

Enter a new IPCKEY within the valid range.

1345 ERROR: Invalid filename for load memory function.

DESCRIPTION

The filename that was used was not valid.

ACTION

Check that the file specified is valid (e.g., that the directory and file specified exists and has read permission). Check for limited resources (out of files or disk space).

1348 ERROR: Could not send message to tlisten

DESCRIPTION

While trying to execute stoptlisten to stop tlisten on a remote machine, tmadmin was unable to contact the tlisten on the remote machine.

ACTION

Check that tlisten is running on the remote machine. Check the event log for related messages.

1349 ERROR: Failed to stop tlisten

DESCRIPTION

While trying to execute stoptlisten to stop tlisten on a remote machine, a failure occurred.

ACTION

Check the event log for related messages.