Oracle Tuxedo 11g R1 Documentation

CMDDES Messages 0-99

ERROR: program_name: Could not open file_name for recording

説明

The filename specified with the -r option to mio (or wmio) could not be opened appropriately for recording the session.

アクション

Check the path and filename for permissions and reenter the mio (or wmio) command line with an updated recording filename specified.

関連項目

mio(1)

ERROR: Access to the initial mask is not permitted

説明

According to the settings of the environment variables OKXACTS and NGXACTS, you are not allowed to access the initial mask specified on the mio command line.

アクション

Modify the setting of the environment variables OKXACTS and NGXACTS to allow access to this form, or use a different form.

関連項目

mio(1), compilation(5)

ERROR: Could not find initial mask

説明

The initial mask specified with the -i option on the mio (or wmio) command line could not be found.

アクション

Check the settings of the MASKPATH and TUXDIR environment variables. The mask file specified with the -i option could not be found in any of the MASKPATH or TUXDIR /locale directories. Reset MASKPATH or TUXDIR as necessary to find the initial mask.

関連項目

mio(1), compilation(5)

ERROR: Initial mask not found

説明

The initial mask specified with the -m option on the mio command line or the default initial mask if no -m option is specified, msk1.M, could not be found.

アクション

Check the settings of the MASKPATH and TUXDIR environment variables. The mask file specified with the -m option could not be found in any of the MASKPATH or TUXDIR /locale directories. Reset MASKPATH or TUXDIR as necessary to find the initial mask.

関連項目

mio(1), compilation(5)

WARN: login cannot print the initial form

説明

The initial system mask cannot be printed and an attempt was made to print using the mio escape sequence that allows a form to be printed by sending it to the FRMPRT service.

アクション

No action required.

関連項目

mio(1)

ERROR: login you are not allowed to enter mask_name transactions

説明

The mask indicated by mask_name has been selected by the input to the current form. However, mask_name is not allowed to be accessed by this user according to the settings of the OKXACTS and NGXACTS environment variables.

アクション

Modify the setting of the environment variables OKXACTS and NGXACTS to allow access to this form, or use a different form.

関連項目

mio(1), compilation(5)

ERROR: login could not find form mask_name

説明

The next form to be displayed, indicated by mask_name, could not be found.

アクション

Check the settings of the MASKPATH and TUXDIR environment variables. mask_name could not be found in any of the MASKPATH or TUXDIR /locale directories. Reset MASKPATH or TUXDIR as necessary to find the mask.

関連項目

mio(1), compilation(5)

ERROR: Non-existent transaction

説明

The menu option selected maps to a choice with no mask/form associated.

アクション

Check your mask file to be sure the menu choice that resulted in this error is fully specified.

関連項目

mio(1)

ERROR: Form mask_name not found

説明

The next form to be displayed, indicated by mask_name, could not be found.

アクション

関連項目

mio(1), compilation(5)

ERROR: Memory allocation failure

説明

An attempt dynamically to allocate memory from the operating system failed allocating a screen image. Additional information about the problem is printed as part of the message.

アクション

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.

ERROR: Memory allocation failure

説明

An attempt to dynamically allocate memory from the operating system using malloc() failed while processing the fielded buffer associated with a form. The occurrence of this error will cause mio to terminate processing.

アクション

Ensure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.

関連項目

mio(1), malloc(3) in UNIX system reference manuals

WARN: SYSTEM BUSY ... PLEASE WAIT A FEW SECONDS

説明

The application and/or operating system is busy to the point that the requested service cannot be satisfied immediately.

アクション

Wait a few seconds and try the transaction again. If the problem persists, then contact your BEA TUXEDO system Technical Support.

関連項目

mio(1)

ERROR: NO SERVER AVAILABLE FOR THIS FORM

説明

The service associated with the selections made on this form is currently not offered or is suspended.

アクション

Contact your BEA TUXEDO system Technical Support. They will need to administer the application to make the service available. This can be done by booting a new server, unsuspending a suspended service, or by advertising a new service on an existing server.

関連項目

mio(1)

ERROR: MEMORY ALLOCATION FAILURE

説明

An attempt to dynamically allocate memory from the operating system using malloc() failed while creating internal storage required to expand a date string for presentation on the screen. The occurrence of this error will cause mio to terminate processing.

アクション

関連項目

mio(1), malloc(3) in UNIX system reference manuals

ERROR: CANNOT SEND TO SERVER

説明

The service requested by the selections made on the current form could not be satisfied because the queue associated with the server or the local BRIDGE process has been abnormally removed from the system.

アクション

Contact your BEA TUXEDO system Technical Support. This error indicates an abnormal removal of UNIX System IPC resources that should be investigated. In any case, the service can be retried after the system restarts the server (abnormal removal of a queue results in a server exit) or after the administrator boots a new instance of the server.

関連項目

mio(1)

ERROR: unknown send failure

説明

A UNIX System message send or receive error was encountered while attempting to satisfy the service request selected on the current form. The error is something other than EINVAL or EAGAIN, which are reported on separate messages. Possible causes of this error are EACCESS, which would indicate that the queue permissions of the server have been changed to deny access to the user running mio, or EFAULT, which would indicate a memory corruption problem in application routines linked into mio.

アクション

Contact your BEA TUXEDO system Technical Support. The UNIX message queue permissions should be checked for access rights. Additionally, memory access in application routines linked into mio should be reviewed.

関連項目

mio(1), msgsnd(2), msgrcv(2) in UNIX system reference manuals

ERROR: FIELDED BUFFER ERROR

説明

Internal system fielded buffer error indicating use of a non-fielded or misaligned buffer within mio.

アクション

Contact your BEA TUXEDO system Technical Support.

関連項目

mio(1), Fchgs(3), Fojoin(3), Fupdate(3)

ERROR: internal failure-get_page

説明

An error occurred while initializing a new form.

アクション

See earlier messages that indicate the exact nature of the problem.

関連項目

mio(1)

ERROR: VALIDATION FUNCTION valfunc NOT FOUND

説明

The validation function valfunc could not be found in the version of mio being run.

アクション

The are two ways to resolve this problem. The first way is to change the definition of the form being used to use a different validation function or to use built-in validation rules such as regular expression matching. The second way is to build or rebuild a customized version of mio containing the indicated validation function.

関連項目

buildmio(1), mio(1)

ERROR: Unexpected End of File encountered

説明

While reading input, end of file was reached before getting the entire message.

アクション

Contact your BEA TUXEDO system Technical Support.

関連項目

mio(1)

ERROR: Error in file udfkfile describing user defined keys

説明

mio encountered a problem accessing and/or processing the user-defined function keys (UDFK) file specified with the -u option on the mio command line.

アクション

Check that the UDFK file being used exists and conforms to the specifications described in the udfk(5) manual page.

関連項目

mio(1), udfk(5)

ERROR: Screen/window too small: must be at least 24x80

説明

The window in which mio is running is too small.

アクション

Expand your window or move to a larger window before running mio.

関連項目

mio(1), curses(3X) in UNIX system reference manuals

ERROR: operation not allowed in release

説明

mio has attempted to make use of an interface semantic that is not available in the current release of the system.

アクション

Contact your BEA TUXEDO system Technical Support.

関連項目

mio(1), tpacall(3), tpbegin(3), tpcommit(3), tpgetrply(3)

ERROR: Transaction could not be committed

説明

The transaction could not be committed by mio because either the work performed by the initiator or by one or more of its participants could not commit.

アクション

Depending on the situation that caused the transaction not to commit, a retry may be successful. If multiple retries over a period of time are not successful, then contact your database administrator(s) to see if they can identify the reason why your transactions cannot be completed.

関連項目

mio(1), tpcommit(3)

ERROR: Service timed out - status unknown

説明

The service associated with the current screen was requested and a timeout occurred in one of three places. Either the request could not be enqueued within the defined timeout interval (only applies if the -B option is specified to mio), or the reply was not received within the timeout interval, or the transaction commit processing timed out. In most cases, the transaction (if any) will have timed out when this error occurs. The only exception is when the transaction commit processing times out.

アクション

Depending on the situation that caused the request to timeout, a retry may be successful. If multiple retries over a period of time are not successful, then contact your database administrator(s) to see if they can identify the reason why your request cannot be completed.

関連項目

mio(1), tpacall(3), tpcommit(3), tpgetrply(3)

ERROR: Desired service does not take FML buffers

説明

The service associated with the current form does not accept FML buffers as input. The set of buffer types accepted by a particular server is determined at compile time. This set may further be restricted by settings for the BUFTYPE parameter in the SERVICES section.

アクション

Contact your application administrator to determine why the requested service does not accept the FML buffer type. Possible actions are to rebuild the server with the FML buffer type included, or to update the configuration file to allow for FML buffer types sent to this service.

関連項目

buildserver(1), mio(1), tpacall(3), typesw(5), tuxtypes(5), ubbconfig(5)

ERROR: Transaction could not be started

説明

A global transaction could not be started prior to requesting the service associated with the current form. This may be caused by a full global transaction table on the local site or by some other system related problem.

アクション

The request should be retried a number of times and then the application administrator should be contacted to examine the userlog file for the machine on which mio was running. In the case of an unrecoverable system problem, log messages will be generated to aid in diagnosis of the problem.

関連項目

mio(1), tpbegin(3)

WARN: Error allocating FML buffer for unsolicited processing

説明

A memory allocation failure was encountered while attempting to generate a typed buffer to be used in processing unsolicited notification messages to the mio process. This failure may have resulted from a failure on a call to malloc().

アクション

関連項目

mio(1), tpalloc(3), malloc(3) in UNIX system reference manuals

ERROR: Disk Error while accessing mask form

説明

An error was encountered on a disk operation while accessing a mask form that had not been cached. Possible errors include problems reading, problems seeking, and corrupted information in the mask form. The occurrence of this error will cause mio to terminate processing.

アクション

Regenerate the mask forms used by mio in the case where the problem was encountered and try the interaction again. If the problem persists, contact your BEA TUXEDO system Technical Support.

関連項目

mio(1)

ERROR: Cannot open temporary file file

説明

buildmio could not open one of the temporary files it needs to build a customized version of mio.

アクション

Check the permissions on the /tmp file system. This file system must be writable for buildmio to create temporary files. If the directory is writable, then check remaining file space and inode restrictions to see if the file system is nearly or completely full. If it is full, then contact your system administrator to clean up temporary file space.

関連項目

buildmio(1), fopen(3) in UNIX system reference manuals

ERROR: Cannot open temporary file file

説明

buildmio could not open one of the temporary files it needs to build a customized version of mio.

アクション

関連項目

buildmio(1), fopen(3) in UNIX system reference manuals

ERROR: Cannot open temporary file file

説明

buildmio could not open one of the temporary files it needs to build a customized version of mio.

アクション

関連項目

buildmio(1), fopen(3) in UNIX system reference manuals

WARN: Cannot open file file

説明

file could not be opened for writing by buildmio.

アクション

Check the permissions on the directory and the file specified by file to make sure that the file can be created and/or written to.

関連項目

buildmio(1), fopen(3) in UNIX system reference manuals

WARN: Failed to execute nm nmflags files

説明

The indicated invocation of the nm command on the file or files specified failed for some reason. The symbols specified in the libraries in question will not be built in to the version of mio created; and if they are referenced at runtime, the reference will fail and mio will encounter an error.

アクション

Attempt a manual invocation of the indicated nm command to determine the exact cause of the problem. Possibilities include corrupted or invalid library names. In this case, regenerate the desired library and retry the buildmio command.

関連項目

buildmio(1), nm(1) in UNIX system reference manuals

ERROR: ipckey is an illegal IPC key value (non-numeric)

説明

The indicated InterProcess Communication (IPC) key, ipckey, contains non-numeric characters and is therefore invalid.

アクション

Change the InterProcess Communication key to a completely numeric value and reenter the command.

関連項目

loadfiles(1), ipcs(1), shmget(2) in UNIX system reference manuals

ERROR: Memory allocation failure

説明

An attempt to dynamically allocate memory from the operating system using malloc() failed while attempting to create an in-memory version of the file cache. The occurrence of this error will cause loadfiles to terminate processing.

アクション

関連項目

loadfiles(1), malloc(3) in UNIX system reference manuals

ERROR: Failed to open filename for caching

説明

The file filename could not be opened for reading by loadfiles. This error is preceded by a call to the UNIX function perror(), which gives further indication of the cause of the error.

アクション

Check the permissions on the indicated file for read access. Correct the permissions or correct the input filename and reenter the command.

関連項目

loadfiles(1), open(2), perror(2) in UNIX reference manuals

ERROR: Memory allocation failure

説明

An attempt to dynamically allocate memory from the operating system using realloc() failed while attempting to create an in-memory version of the file cache. The occurrence of this error will cause loadfiles to terminate processing.

アクション

This error may indicate that you are trying to include too many files in a single shared memory file cache. Try reducing the number of files being cached if you think this may be the problem. However, the problem may also result from system limitations outside the direct control of the user. Ensure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.

関連項目

loadfiles(1), realloc(3) in UNIX system reference manuals

ERROR: Too many files in cache

説明

The user has attempted to cache more than the system imposed limit on the number of files to be stored in the shared memory cache.

アクション

Reduce the number of files to be entered into this shared memory cache to less than 1000 and reenter the command.

関連項目

loadfiles(1)