1000
ERROR: USAGE: Set name value
Description
You can set environment variables with TuxShell using the Set command. The syntax for the Set command is "Set name value", which will set the environment variable name to the value value.
Action
Ensure that the Set command in the script run by the TuxShell has the proper format.
1001
ERROR: Could not allocate memory for environment
While creating an environment context, the system ran out of memory.
Check the memory on the system where the TuxShell was running. Increase the amount of memory which is allotted to TuxShell using the finder.
1002
ERROR: tuxputenv returns an error. String not added to environment
tuxputenv(3c) returned an error while TuxShell was setting an environment variable.
tuxputenv
1003
ERROR: Environment is full
The TuxShell process can only keep track of 255 environment variables.
Use fewer environment variables in your TuxShell script.
1004
1005
ERROR: USAGE: Unset name
You can unset environment variables with TuxShell using the Unset command. The syntax for the Unset command is "Unset name", which will unset the environment variable name.
Ensure that the Unset command in the script run by the TuxShell has the proper format.
1007
ERROR: Memory Full Error returned by AEProcessAppleEvent
A high level event has been received by the process. The Macintosh High Level Event API AEProcessAppleEvent has been called, in order to properly parse the event. A memFullErr event code was returned by AEProcessAppleEvent.
Check the memory on the system where the process was running. Increase the amount of memory which is allotted to the process using the finder.
1008
ERROR: Buffer is too small returned by AEProcessAppleEvent
A high level event has been received by the process. The Macintosh High Level Event API AEProcessAppleEvent has been called, in order to properly parse the event. A bufferIsSmall event code was returned by AEProcessAppleEvent.
The high level event returned by the system is improper. Contact your BEA TUXEDO system Technical Support.
1009
ERROR: Corrupt Data returned by AEProcessAppleEvent
A high level event has been received by the process. The Macintosh High Level Event API AEProcessAppleEvent has been called, in order to properly parse the event. A errAECorruptData event code was returned by AEProcessAppleEvent.
1010
ERROR: Newer Version returned by AEProcessAppleEvent
A high level event has been received by the process. The Macintosh High Level Event API AEProcessAppleEvent has been called, in order to properly parse the event. A errAENewerVersion event code was returned by AEProcessAppleEvent.
1011
ERROR: The directory {TUXDIR}lib is not present
viewc(1) and viewc32 need to be able to find the {TUXDIR}lib directory on Macintosh, in order to find the Symantec Project VIEWC_DNR.prj.
viewc
viewc32
Make sure that TUXDIR is set using the Set command. Make sure that the {TUXDIR}lib directory exists as has the proper permissions. Make sure that the project VIEWC_DNR.prj can be located in the {TUXDIR}lib directory.
1012
ERROR: Error creating FSSpec record
An error occurred while creating an internal structure to represent the {TUXDIR}lib directory.
Contact your BEA TUXEDO system Technical Support.
1013
ERROR: Error creating alias record
1014
ERROR: Error creating descriptor list
1015
ERROR: The file VIEWC_DNR was removed
1016
An error occurred while creating an internal structure to represent the {TUXDIR}lib:VIEWC_DNR.prj file.
1017
1018
ERROR: Error adding Alias record to list
An error occurred while updating an internal structure to represent the {TUXDIR}lib:VIEWC_DNR.prj file, inside the {TUXDIR}lib directory.
1019
ERROR: Error Creating Finder Address
An error occurred while creating an internal structure to represent the finder.
1020
ERROR: Error Creating High Level Event for Compiler
An error occurred while creating a high level event for the Symantec compiler.
1021
ERROR: Error adding option to Apple Event
An error occurred while updating a high level event for the Symantec compiler.
1022
ERROR: Error adding Alias List to Apple Event
1023
ERROR: TimeoutError Waiting for reply AppleEvent
An error occurred while sending a high level event to the Symantec compiler.
1024
ERROR: Error Creating Target Compiler Address
An error occurred while creating a high level event for the MPW compiler.
1025
ERROR: Error getting the current working directory
While attempting to find the current working directory of the process, an error occurred.
Make sure that the directory in which the process is working still exists.
1026
1027
ERROR: Error adding buildclient command to Apple Event
viewc and viewc32 work by sending a buildclient command to ToolServer. An error occurred while updating a high level event with the buildclient command.
ToolServer
1028
viewc and viewc32 work by sending a buildclient command to ToolServer. The MPW compiler may have taken too long to complete the compilation process.
1029
ERROR: An error occurred getting the MPW Error Code
viewc and viewc32 work by sending a buildclient command to ToolServer. An error occurred while attempting to retrieve the status of the compilation.
1030
WARN: An error has occurred compiling the file. Usually a struct > 32K
viewc and viewc32 work by sending a buildclient command to ToolServer. The view compilation has failed.
The usual cause of this error is a view structure which is greater than 32K. The MPW compiler cannot handle a structure this large, and hence this compilation will fail. Decrease the number of elements in the view, or the number of occurrences of elements in the view.
1031
ERROR: Error creating Launch record for internal application
In the second phase of viewc and viewc32, an application which was generated in the first phase must be run. An error occurred while generating a launch record for this application.
1032
ERROR: Error launching internal application
In the second phase of viewc and viewc32, an application which was generated in the first phase must be run. An error occurred while launching this application.
1033
ERROR: Error waiting for launched application
In the second phase of viewc and viewc32, an application which was generated in the first phase must be run. An error occurred while waiting for this application to finish execution.
1034
ERROR: TUXDIR is not set
While attempting to initialize the Symantec THINK C compiler, it was found that TUXDIR was not set.
Use the Set command in your TuxShell script to set the appropriate value for TUXDIR.
TuxShell
1035
ERROR: Utility not handled
An unknown utility was requested in TuxShell.
1036
ERROR: Error Creating THINK Address
While attempting to create the address of the Symantec THINK C compiler, an error occurred.
1037
ERROR: Error Creating High Level Event for THINK Compiler
While attempting to create a high level event for the Symantec THINK C compiler, an error occurred.
1038
While waiting for a high level event from the Symantec THINK C compiler, an error occurred.
1039
ERROR: An error occurred making compiler noninteractive
An error occurred while attempting to make the Symantec THINK C compiler noninteractive.
1040
ERROR: viewc created file not found
viewc or viewc32 creates a file to be compiled in its first phase. While the Symantec THINK C Compiler was being used, TuxShell could not find the file generated by viewc or viewc32.
1041
viewc or viewc32 creates a file to be compiled in its first phase. While the Symantec THINK C Compiler was being used, TuxShell could create an FSSpec record for this file.
1042
An error occurred while creating a high level event for the THINK compiler.
1043
ERROR: Error adding file name to Apple Event
viewc or viewc32 creates a file to be compiled in its first phase. While the Symantec THINK C Compiler was being used, TuxShell could not add the file name to a high level apple event for the compiler.
1044
ERROR: Error adding signature to Apple Event
viewc or viewc32 creates a file to be compiled in its first phase. While the Symantec THINK C Compiler was being used, TuxShell could not add the application signature to a high level apple event for the compiler.
1045
viewc or viewc32 creates a file to be compiled in its first phase. While the Symantec THINK C Compiler was being used, a timeout error occurred while waiting for the compiler to compile the file.
1046
ERROR: An error occurred adding generated file to project
viewc or viewc32 creates a file to be compiled in its first phase. An error occurred while attempting to add the file to the VIEWC_DNR.prj project.
1047
ERROR: An error occurred getting obj specifier of file
viewc or viewc32 creates a file to be compiled in its first phase. An error occurred while attempting to retrieve information about the file which has been added to the VIEWC_DNR.prj project.
1048
viewc or viewc32 creates a file to be run in its second phase. An error occurred while attempting to create an apple event to tell the Symantec THINK C compiler to run the project.
1049
ERROR: Error adding update options to Apple Event
viewc or viewc32 creates a file to be run in its second phase. An error occurred while attempting to create an update an apple event to tell the Symantec THINK C compiler to run the project.
1050
ERROR: Error adding save options to Apple Event
1051
viewc or viewc32 creates a file to be run in its second phase. An error occurred while waiting for the VIEWC_DNR.prj project to run to completion.
1052
ERROR: Error running internal application
viewc or viewc32 creates a file to be run in its second phase. The application did not run successfully.
1053
viewc or viewc32 creates a file to be run in its second phase. We are attempting to clean the VIEWC_DNR.prj project by removing the file generated in the first phase. However, an error occurred while generating a high level apple event for this purpose.
1054
viewc or viewc32 creates a file to be run in its second phase. We are attempting to clean the VIEWC_DNR.prj project by removing the file generated in the first phase. An error occurred while adding the file name to a high level apple event.
1055
viewc or viewc32 creates a file to be run in its second phase. We are attempting to clean the VIEWC_DNR.prj project by removing the file generated in the first phase. A timeout error occurred while waiting for the Symantec THINK C Compiler to remove the file.
1056
ERROR: An error occurred removing generated file from project
viewc or viewc32 creates a file to be run in its second phase. We are attempting to clean the VIEWC_DNR.prj project by removing the file generated in the first phase. An error occurred while removing the file.
1057
WARN: The utility returned an error
All the utilities which TuxShell runs return an error code. One of the utilities run by TuxShell returned an error. This occurs when wud or wud32 is being used.
Consult the documentation on the utility which returned an error.
1058
ERROR: Could not get utility menu Handle
An error occurred reading the resource fork of the TuxShell.
1059
ERROR: An error occurred quitting project
The Symantec THINK C Compiler returned an error to TuxShell while quitting the VIEWC_DNR.prj project.
1060
While attempting to generate an address for the Symantec THINK C Compiler, an error occurred.
1061
ERROR: CC is not set
When using viewc or viewc32 through TuxShell, the environment variable CC must be set.
Set CC depending on the compiler which is being used. If you are using the MPW compiler, set CC to applec. If you are using the Symantec THINK C compiler, set CC to THINK_C. If you are using the MetroWerks CodeWarrior compiler, set CC to mwerks.
1062
ERROR: Compiler compiler is not supported
The compiler compiler given via the CC environment variable is not supported.
1063
viewc or viewc32 must run the Symantec THINK C compiler. An error occurred while creating a High Level Event.
1064
viewc or viewc32 must run the Symantec THINK C compiler. A timeout error occurred while configuring the Symantec THINK C Compiler.
1065
1066
ERROR: THINK C compile call returns an error
The Symantec THINK C compiler failed.
1067
ERROR: MPW compile call returns an error
The MPW compiler failed.
1068
ERROR: Compiler not supported: compiler
compiler is not supported.
1069
WARN: Utility not found: utility
TuxShell does not run utility.
Make sure your TuxShell script invokes only those utilities which are available to it. Utilities which are supported by TuxShell are gencat, mklanginfo, mkfldhdr, viewc, viewdis, viewc32, viewdis32, mkfldhdr32, set, and unset.
gencat
mklanginfo
mkfldhdr
viewdis
viewdis32
mkfldhdr32
set
unset
1070
WARN: Quoting Error. Skipping line
All double quoted elements must have a terminating double quote in TuxShell scripts.
If you are using double quotes, make sure they are properly matched in your TuxShell script.
1071
WARN: Too many parameters. Skipping line
TuxShell can handle a maximum of 31 arguments per command.
Use fewer arguments.
1072
WARN: Could not start compiler. Skipping line
TuxShell attempted to start a compiler for viewc or viewc32 but was not successful. TuxShell will skip the line.
Analyze the cause of the compiler failure. If you are using Symantec THINK C, be sure that the VIEWC_DNR.prj is located in TUXDIR:lib:. Be sure that if you double click on VIEWC_DNR.prj, that the compiler launches properly. Be sure that the Symantec THINK C Compiler is not already active.
1073
WARN: An Error occurred in utility: utility
All the utilities which TuxShell runs return an error code. One of the utilities run by TuxShell returned an error.
1074
ERROR: A fatal error has occurred. Aborting TuxShell
Some fatal error has occurred during the TuxShell processing.
Restart TuxShell and try again.
1075
ERROR: Could not get apple menu Handle
1076
ERROR: Could not get file menu Handle
1077
While the TuxShell was processing a high level apple event, a memFullErr occurred.
1078
While the TuxShell was processing a high level apple event, a bufferIsSmall error occurred.
1079
While the TuxShell was processing a high level apple event, a errAECorruptData error occurred.
1080
While the TuxShell was processing a high level apple event, a errAENewerVersion error occurred.
1081
ERROR: Unable to open TuxShell.stdout
TuxShell attempt to write all output destined for stdout into a file called TuxShell.stdout. However, TuxShell could not open the file in the working directory.
Make sure that the working directory of the TuxShell exists and that it is writable.
1082
ERROR: Unable to open TuxShell.stderr
TuxShell attempt to write all output destined for stderr into a file called TuxShell.stderr. However, TuxShell could not open the file in the working directory.
1083
ERROR: Error opening script file
TuxShell attempted to open a script for execution. However, TuxShell could not open the file.
Make sure that the directory in which the script resides is writable by the user of TuxShell.
1084
ERROR: Error retrieving directory name
TuxShell attempted to open a script for execution. However, TuxShell could not retrieve the name of the directory in which the file exists.
1085
ERROR: Error initializing status dialog
1086
ERROR: Error updating status dialog
1087
INFO: User killed script
The user of TuxShell cancelled the script while in progress.
Do not hit the CANCEL button.
1088
ERROR: Unknown Error: number returned by RunScript
An internal routine of TuxShell returned unknown error code number.
1089
ERROR: Memory is low. Aborting TuxShell
The memory low routine of TuxShell was invoked.
1090
ERROR: Unable to allocate Handle for emergency memory. Aborting TuxShell
Check the memory on the system where the TuxShell was running. Increase the amount of memory which is allotted to TuxShell using the finder. If it seems that there should be enough memory for this operation, contact your BEA TUXEDO system Technical Support.
1091
INFO: Could not add variable to environment
The Set command of TuxShell could not add variable to the environment.
1092
WARN: wud32 returns an error
The wud32 command of TuxShell returned an error.
Check the files TuxShell.stdout and TuxShell.stderr for further information about the cause of failure.
1093
WARN: wud returns an error
The wud command of TuxShell returned an error.
1094
WARN: TuxShell file overflow
An internal error occurred while reading the TuxShell script file.
1095
ERROR: MWERKS_MPW must be set to the MPW component of Code Warrior
If the MetroWerks compiler is used, then the environment variable MWERKS_MPW must be set to point to the directory where the MPW component of the MetroWerks compiler is installed.
If you are using the MetroWerks compiler, be sure to install the MPW portion of the compiler. Set MWERKS_MPW to point to the directory where the MPW utilities are installed. The ToolServer must also know where to find the MPW utilities.
1096
An error occurred creating the address for the MetroWerks Compiler.
1097
While attempting to initialize the MetroWerks compiler, it was found that TUXDIR was not set.
1098
1099
An error occurred while creating a high level event for the MetroWerks compiler.