CMDTUX MESSAGES 700-799

700 ERROR: Group's current location inconsistent with TUXCONFIG file

DESCRIPTION

The location of a server group was being updated in the master copy of the TUXCONFIG file, to reflect a new location after migration. The new location unexpectedly did not match either the primary or backup specified in the TUXCONFIG file.

ACTION

The master machine's TUXCONFIG is inconsistent with the group's real location. The file can be restored by shutting down the application, and then running tmloadcf using a backup ASCII version of the configuration file. Running tmunloadcf on another machine in the configuration should provide a recent backup version.

SEE ALSO

tmloadcf (1), tmunloadcf (1), ubbconfig (5)

730 ERROR: Memory allocation failure

DESCRIPTION

This error occurred while attempting to shut down a partitioned lmid and its associated servers.

ACTION

Remove processes that may be tying up physical memory, ensure that the application ipckey is correct, or verify that the UNIX sysgen process sizing parameters are correct.

SEE ALSO

tmshutdown (1)

731 ERROR: for debug level

DESCRIPTION

A non-numeric argument was specified with the debugging option of tmboot or tmshutdown , causing the process to abort.

ACTION

Specify a numeric value for the debugging level command line option.

732 ERROR: for srvid

DESCRIPTION

The argument for the -i option of tmboot or tmshutdown is not a numeric value between 1 and 30,000.

ACTION

Specify a numeric value between 1 and 30,000.

SEE ALSO

tmboot (1), tmshutdown (1), ubbconfig (5)

733 ERROR: for sequence number

DESCRIPTION

The argument for the -o option of tmboot or tmshutdown is not a numeric value between 1 and 9,999.

ACTION

Specify a numeric value between 1 and 9,999.

SEE ALSO

tmboot (1), tmshutdown (1), ubbconfig (5)

734 ERROR: for delay

DESCRIPTION

The argument for the -w option of tmshutdown is not a number greater than 0.

ACTION

Specify a numeric value greater than 0.

SEE ALSO

"TUXEDO Administrator's Guide" , tmshutdown (1), ubbconfig (5)

735 ERROR: Memory allocation failure

DESCRIPTION

This error occurred while booting the MASTER machine.

ACTION

Remove processes that may be tying up physical memory, ensure that the application ipckey is correct, or verify that the UNIX sysgen process sizing parameters are correct.

SEE ALSO

tmboot (1)

737 ERROR: tmboot too many arguments

DESCRIPTION

An argument is present that does not match the options selected for tmboot , or no options are specified and an argument is passed.

ACTION

Resubmit after verifying the command line options.

SEE ALSO

"TUXEDO Administrator's Guide" , tmboot (1)

738 ERROR: -R option requires either the -g or -l option

DESCRIPTION

A shutdown request with the -R option shuts down servers on their original processors to prepare them for migration to another processor. This option must be used with either the group name, -g grpname, or logical name, -l lmid, option.

ACTION

Resubmit the command and specify either the -g or -l option that contains the servers to be shut down and eventually migrated.

SEE ALSO

"TUXEDO Administrator's Guide" , tmshutdown (1)

739 ERROR: -A option not allowed with -R

DESCRIPTION

A shutdown request with the migration option, -R , has been issued with the administrative servers option, -A . This request isn't valid, since migration is specific to server groups through options -l or -g , not administrative servers.

ACTION

Resubmit tmshutdown with either option -R to shut down the servers specified for migration, or after all the servers in the SERVERS section of the configuration file have been shut down, the -A option may be used to shut down the administrative servers.

SEE ALSO

"TUXEDO Administrator's Guide" , tmshutdown (1)

740 ERROR: -S option not allowed with -R

DESCRIPTION

A shutdown request with the -R option has been issued with the -S option specifying that all servers in the SERVERS section of the configuration file should be shut down for migration. This request isn't valid since the -R option must be used with either option -l or -g .

ACTION

Resubmit tmshutdown without the -S option and instead specify the servers to be shut down by the -l lmid or -g grpname options that contain these server groups.

SEE ALSO

"TUXEDO Administrator's Guide" , tmshutdown (1)

741 ERROR: -B option not allowed with -R

DESCRIPTION

A shutdown request with the migration, -R , option has been issued with the BBL, -B , option. A BBL may not be shut down for migration.

ACTION

Resubmit tmshutdown without the -B option and instead specify the servers to be shut down by the -l lmid or -g grpname options that contain these server groups.

SEE ALSO

"TUXEDO Administrator's Guide" , tmshutdown (1)

742 ERROR: -T option not allowed with -R

DESCRIPTION

A shutdown request with the migration, -R , option has been issued with the TMS servers, -T , option. A TMS may not be shut down for migration.

ACTION

Resubmit tmshutdown without the -T option and instead specify the servers to be shut down by the -l lmid or -g grpname options that contain these server groups.

SEE ALSO

"TUXEDO Administrator's Guide" , tmshutdown (1)

743 ERROR: -H option not allowed with -R

DESCRIPTION

A shutdown request with the migration, -R , option has been issued with the -H option to shut down all administrative and application servers on a specified processor. This request isn't valid since migration is specific to server groups through options -l or -g , not administrative servers.

ACTION

Resubmit tmshutdown with the -l option to specify the servers to be shut down on the specified processor for migration.

SEE ALSO

"TUXEDO Administrator's Guide" , tmshutdown (1)

744 ERROR: -i option not allowed with -R

DESCRIPTION

A shutdown request with the migration, -R , option has been issued with the -i srvid option which will shut down all servers in the SERVERS section of the configuration file whose SRVID parameter is srvid. This request isn't valid since the -R option must be used with either option -l or -g .

ACTION

Resubmit tmshutdown without the -i option and instead specify the servers to be shut down by the -l lmid or -g grpname options that contain these server groups.

SEE ALSO

"TUXEDO Administrator's Guide" , tmshutdown (1)

745 ERROR: -o option not allowed with -R

DESCRIPTION

A shutdown request with the migration, -R , option has been issued with the -o sequence option which will shut down all servers in the SERVERS section of the configuration file whose SEQUENCE parameter is sequence. This request isn't valid since the -R option must be used with either option -l or -g .

ACTION

Resubmit tmshutdown without the -o option and instead specify the servers to be shut down by the -l lmid or -g grpname options that contain these server groups.

SEE ALSO

"TUXEDO Administrator's Guide" , tmshutdown (1)

746 ERROR: -s option not allowed with -R

DESCRIPTION

A shutdown request with the migration, -R , option has been issued with the -s aout option which will shut down all servers in the SERVERS section of the configuration file whose name is aout. This request isn't valid since the -R option must be used with either option -l or -g .

ACTION

Resubmit tmshutdown without the -s option and instead specify the servers to be shut down by the -l lmid or -g grpname options that contain these server groups.

SEE ALSO

"TUXEDO Administrator's Guide" , tmshutdown (1)

754 ERROR: error processing configuration file

DESCRIPTION

When booting or shutting down an application, tmboot or tmshutdown attempts to load in the TUXCONFIG file. At this point the configuration file defined by the environment variable TUXCONFIG cannot be found or has been corrupted.

ACTION

The value of the TUXCONFIG environment variable should be checked to see if it set to the correct configuration file and exported. After ensuring that this variable is set correctly and the same failure occurs, the TUXCONFIG file has been corrupted. The TUXCONFIG file must be regenerated by the tmloadcf command from the UBBCONFIG file.

SEE ALSO

tmboot (1), tmloadcf (1), tmshutdown (1), ubbconfig (5)

755 ERROR: -R option not allowed if MIGRATE not specified

DESCRIPTION

A shutdown request with the -R option has been issued for a configuration that does not have the MIGRATE option specified in the UBBCONFIG file.

ACTION

To enable migration for an application in this situation, the application must be shut down, and the configuration must be updated to include the MIGRATE option (in the *RESOURCES section). Then the TUXCONFIG file must be recompiled using tmloadcf , and after the application is brought back up, migration may be performed.

SEE ALSO

"TUXEDO Administrator's Guide" , tmboot (1), tmloadcf (1), tmshutdown (1), ubbconfig (5)

756 ERROR: -P option not allowed on non-partitioned node

DESCRIPTION

A shutdown request with the -P option has been issued on a non-partitioned node. The -P option is specifically used for nodes that are partitioned (there is no access with the DBBL).

ACTION

To shut down servers on this lmid, the -l option may be used.

SEE ALSO

"TUXEDO Administrator's Guide" , tmshutdown (1)

757 ERROR: Could not reset model to MP for partitioned shutdown

DESCRIPTION

A TUXEDO System internal value was not set correctly. Check the userlog for additional error messages to clarify this error condition. The circumstances associated with this error are not likely to be caused by something that the invoker of the tmshutdown command will have done. It is more likely to be a TUXEDO System error.

ACTION

Try repeating the same operation. If this fails with the same error, contact your TUXEDO System Technical Support.

SEE ALSO

tmshutdown (1)

758 ERROR: Could not attach to local BB for partitioned shutdown

DESCRIPTION

While trying to connect to the local bulletin board to complete the partitioned shutdown request, an error occurred in the initialization phase. There are several scenarios that may eventually cause this error, including a corrupted TUXCONFIG file, authentication failure, and invalid buffer types. Also, the tpinfo buffer could contain illegal values.

ACTION

Check the userlog for error messages to clarify the problem. If the cause cannot be discerned, contact your TUXEDO System Technical Support.

SEE ALSO

"TUXEDO Administrator's Guide" , tmshutdown (1)

759 ERROR: Could not bring up temp DBBL for partitioned shutdown

DESCRIPTION

While trying to process a partitioned shutdown request, a temporary DBBL process must be booted. An error occurs such as running the command on a machine that is not partitioned. Or while starting the pseudo-DBBL, the original DBBL is still reachable through another bridge from the "partitioned" site.

ACTION

Determine if the machine is partitioned (by using the tmadmin command psr ). Check the userlog for error messages to clarify the problem. If the machine is partitioned and this error occurs again, contact your TUXEDO System Technical Support.

SEE ALSO

"TUXEDO Administrator's Guide" , tmadmin (1), tmshutdown (1)

760 ERROR: Failed to attach to temp DBBL for partitioned shutdown

DESCRIPTION

The tmadmin process was unable to attach itself to the Bulletin Board to perform the requested action. Check the userlog for additional error messages to clarify the problem.

ACTION

Try repeating the command again. If it fails in the same manner, contact your TUXEDO System Technical Support.

SEE ALSO

"TUXEDO Administrator's Guide" , tmshutdown (1)

761 ERROR: Illegal TUXCONFIG value

DESCRIPTION

The value of the TUXCONFIG environment variable and the caller process and the value for the machine set in the UBBCONFIG file are inconsistent.

ACTION

Reset the TUXCONFIG variable and rerun the command.

SEE ALSO

ubbconfig (5)

762 ERROR: LAN mode not specified for multiple node application

DESCRIPTION

The OPTIONS parameter in the *RESOURCES section must specify the LAN option for a multiple node application.

ACTION

Change the application configuration to ensure that the OPTIONS parameter in the *RESOURCES section includes the LAN value.

SEE ALSO

ubbconfig (5)

763 ERROR: cannot create internal BB tables

DESCRIPTION

While booting, an application error in attaching to the shared memory has occurred.

ACTION

Contact your TUXEDO System Technical Support.

SEE ALSO

tmboot (1)

764 ERROR: can't attach to BB

DESCRIPTION

While shutting down an application, an error in attaching to the configuration bulletin board has occurred.

ACTION

Check the userlog for additional diagnostic messages. Normally this error implies that the TUXCONFIG environment variable is not set correctly, or that the application is not booted.

SEE ALSO

tmshutdown (1)

765 ERROR: must run on master node

DESCRIPTION

tmboot must be run on either of the master nodes specified in the MASTER parameter of the *RESOURCES section. tmshutdown must be run on the active master.

ACTION

Reissue the boot or shutdown command on the proper processing element.

SEE ALSO

tmboot (1), tmshutdown (1)

766 ERROR: must run on master node

DESCRIPTION

A boot request is issued from the backup master node specified in the configuration. Or, the system cannot find a DBBL process in the system during a shutdown request.

ACTION

Reissue the boot request from the master specified in the configuration. If this error results from a shutdown request, make sure that there is a DBBL process running before reissuing the request.

SEE ALSO

tmboot (1), tmshutdown (1)

767 ERROR: must run on master node

DESCRIPTION

A shutdown request is issued from the master node specified in the configuration. However, this is no longer the active master, since the original master has been migrated.

ACTION

Reissue the shutdown request from the active master.

SEE ALSO

tmshutdown (1)

768 ERROR: Bad LMID (lmid) in command line option(s)

DESCRIPTION

The argument lmid specified for the command line option is invalid.

ACTION

Check the configuration for the correct lmid value and reissue the command.

SEE ALSO

tmboot (1), tmshutdown (1)

769 ERROR: Server group name (grpname) too long

DESCRIPTION

The group name specified for the command line option is too long. The server group name must be less than or equal to 30 characters.

ACTION

Check the configuration for the correct group name and reissue the command.

SEE ALSO

tmboot (1), tmshutdown (1), ubbconfig (5)

770 ERROR: Invalid server group name (grpname)

DESCRIPTION

The group name specified for this command is not in the configuration.

ACTION

Check the configuration for the correct group name and reissue the command.

SEE ALSO

tmboot (1), tmshutdown (1), ubbconfig (5)

771 ERROR: Bad command line options! Check the LOG file

DESCRIPTION

An invalid command line option was specified that resulted in a fatal error.

ACTION

Check the userlog file to determine the exact cause of the error.

SEE ALSO

tmboot (1), tmshutdown (1), ubbconfig (5)

772 ERROR: can't get (D)BBL's table entry

DESCRIPTION

While shutting down the system, a server table entry is in an inconsistent state.

ACTION

Contact your TUXEDO System Technical Support.

777 INFO: See ULOG for complete process status

DESCRIPTION

This message reminds the user that there is more information available in the userlog.

ACTION

No action required.

786 ERROR: Memory allocation failure

DESCRIPTION

During shutdown, memory could not be allocated for an internal structure that holds process information.

ACTION

Remove processes that may be tying up physical memory, ensure that the application ipckey is correct, or verify that the UNIX sysgen process sizing parameters are correct.

787 ERROR: Memory allocation failure

DESCRIPTION

During shutdown, memory could not be allocated for an internal structure that holds process information.

ACTION

Remove processes that may be tying up physical memory, ensure that the application IPC key is correct, or verify that the UNIX sysgen process sizing parameters are correct.

788 ERROR: Memory allocation failure

DESCRIPTION

During shutdown, memory could not be allocated for an internal structure that holds process information.

ACTION

Remove processes that may be tying up physical memory, ensure that the application IPC key is correct, or verify that the UNIX sysgen process sizing parameters are correct.

790 INFO: *Interrupt* Want to Continue? (y/n):

DESCRIPTION

The system was being shut down when an alarm was turned on.

ACTION

You may proceed with the shutdown request by entering 'y', or you may abort the request by entering 'n'.

794 ERROR: Memory allocation failure

DESCRIPTION

During tmboot , memory could not be allocated for an internal structure that holds process information.

ACTION

Remove processes that may be tying up physical memory, ensure that the application IPC key is correct, or verify that the UNIX sysgen process sizing parameters are correct.

795 ERROR: Memory allocation failure

DESCRIPTION

During tmboot , memory could not be allocated for an internal structure that holds process information.

ACTION

Remove processes that may be tying up physical memory, ensure that the application IPC key is correct, or verify that the UNIX sysgen process sizing parameters are correct.

796 ERROR: Cannot continue booting without DBBL

DESCRIPTION

During the booting sequence for a multiprocessing configuration, the DBBL process is required to be booted before the BBLs may be booted. However, the DBBL has not been booted.

ACTION

Make sure that the DBBL is running on the master node. If the DBBL is in fact running, contact your TUXEDO System Technical Support. Otherwise, the DBBL must be booted (unless all of the admin processes are started at the same time with "tmboot -A" ).

SEE ALSO

tmboot (1)

797 ERROR: No BBL available for boot of BRIDGE on lmid

DESCRIPTION

The BRIDGE process requires that a BBL is present on that lmid. The BBL is not currently available.

ACTION

The BBL may be booted explicitly using "tmboot -B" lmid and the original command retried.

SEE ALSO

tmboot (1)

798 ERROR: Cannot boot remote BBL(lmid1), no BRIDGE available on DBBLs node(lmid2)

DESCRIPTION

The BRIDGE process on the DBBL's node, lmid2, must be present to boot the BBL on lmid1 as requested.

ACTION

Contact your TUXEDO System Technical Support.

799 ERROR: Cannot boot remote BBL(lmid), machine inaccessible

DESCRIPTION

The node lmid is inaccessible and the BBL may not be booted as requested.

ACTION

Verify that the node lmid is running. If so, contact your TUXEDO System Technical Support.