// $Id: err.txt,v 2.36 2012/05/12 17:06:56 mschenke Exp $ // ARCS: $Header: /home/cvs/cvs/RDA_4/src/scripting/lib/modules/err.txt,v 2.36 2012/05/12 17:06:56 mschenke Exp $ // /////////////////////////////////////////////////////////////////////////// // 00000.00099 General Errors // /////////////////////////////////////////////////////////////////////////// // 00000,0, "Cannot change to the RDA install directory" // *Cause: RDA failed to change the current directory to the RDA install // directory. // *Action: Check the path and the permissions of the install directory. // *Mnemonic: RDA_CD_HOME_FAIL // 00001,0, "Cannot change to the report directory" // *Cause: RDA failed to change the current directory to the report directory. // *Action: Check the path and the permissions of the report directory. The // directory does not always exist before data is collected. // *Mnemonic: RDA_CD_OUTPUT_FAIL // 00002,0, "Cannot zip the reports" // *Cause: RDA detected an error when using zip to package the reports. // *Action: Check for any other errors reported by the zip command. Check the // path that is stored in the setup file, which is used to execute // that command. // *Mnemonic: GU_ZIP_ERROR // 00003,0, "Cannot package the reports using 'pax'" // *Cause: RDA detected an error when using pax to package the reports. // *Action: Check for any other errors reported by the pax command. Check the // path that is stored in the setup file, which is used to execute // that command. // *Mnemonic: GU_PAX_ERROR // 00004,0, "Cannot package the reports using 'tar'" // *Cause: RDA detected an error when using tar to package the reports. // *Action: Check for any other errors reported by the tar command. Check the // path that is stored in the setup file, which is used to execute // that command. // *Mnemonic: GU_TAR_ERROR // 00005,0, "Cannot list the reports" // *Cause: RDA cannot open the report directory. // *Action: Check access to the reports. // *Mnemonic: GU_DIR_ERROR // 00006,0, "Archive command not -yet- identified" // *Cause: No packaging tool paths have been found. // *Action: RDA cannot find any packaging tool paths. Typically this occurs // when the end report has not been produced yet or if these commands // are not found in the current execution path (cf. PATH). // *Mnemonic: GU_PKG_ERROR // 00007,0, "Error not found" // *Cause: RDA failed to find the explanation of the specified error. // *Action: Report this error to Oracle Support. Describe the circumstances // under which the error was encountered. // *Mnemonic: GU_BAD_ERROR // 00008,0, "External package '' not available" // *Cause: RDA cannnot load the specified package. // *Action: The next line provides more information about this error. Take // appropriate actions to fix it. // *Mnemonic: GU_BAD_PACKAGE // 00009,0, "Error in external call" // *Cause: RDA encountered an error when evaluating the external call. // *Action: The next line provides more information about that error. Take // appropriate actions to fix it. // *Mnemonic: GU_BAD_CALL // 00010,0, "Cannot locate required RDA modules" // *Cause: RDA encountered an error when loading RDA Perl packages. // *Action: The next line provides more information about that error. Take // appropriate actions to fix it. // *Mnemonic: GU_NO_AGENT // 00011,0, "Missing file list" // *Cause: RDA encountered an error when loading RDA Perl packages. // *Action: Reinstall RDA. // *Mnemonic: GU_NO_LIST // 00012,0, "Directory structure not preserved" // *Cause: RDA found the file list in the top RDA directory. // *Action: Reinstall RDA, ensuring that the directory structure is preserved. // *Mnemonic: GU_BAD_TOPO // 00013,0, "File list corrupted" // *Cause: The checksum of the file list is incorrect. // *Action: Reinstall RDA. // *Mnemonic: GU_BAD_LIST // 00014,0, "%d issue(s) found in the RDA installation" // *Cause: RDA encountered issues when checking the installation. // *Action: Reinstalling RDA is usually the easiest way to fix file // alteration problems. However, permissions problems can also result // from other factors: // - If RDA has been installed by another user, the default settings // may be too restrictive. Review the local context with that user // and your local system administrator. // - Execution permissions can be missing from startup scripts for // other platforms and when Perl is not available from the command // line. // *Mnemonic: GU_BAD_INST // 00015,0, "Warning - %d database request(s) not executed in %s module(s)" // *Cause: RDA encountered execution timeouts or requests have been skipped. // *Action: More about these errors can be found in 'Report Settings'. // If there are no database problems, increase the SQL_TIMEOUT value // using one of the following methods: // - Edit the setup file. // - At the command line, use an option such as -e SQL_TIMEOUT=120 // The value indicates the number of seconds a database request can // run before being interrupted. A zero value disables any timeout. // *Mnemonic: GU_SQL_WARNINGS // 00016,0, "END module setup required for managing authentication" // *Cause: RDA cannot find the END module in the configuration file. // *Action: Set up the END module by using the following command arguments: // -S END // *Mnemonic: GU_NO_END // 00017,0, "Warning - %d command(s) not executed in %s module(s)" // *Cause: RDA encountered execution timeouts. // *Action: More about these errors can be found in 'Report Settings'. // If there are no system problems, increase the RDA_TIMEOUT value // using one of the following methods: // - Edit the setup file. // - At the command line, use an option such as -e RDA_TIMEOUT=600 // The value indicates the number of seconds an operating system // command can run before being interrupted. A zero value disables any // timeout. // *Mnemonic: GU_OS_WARNINGS // 00018,0, "Warning - %d XML request(s) not executed in %s module(s)" // *Cause: RDA encountered execution timeouts. // *Action: More about these errors can be found in 'Report Settings'. // If there are no system problems, increase the RDA_TIMEOUT value // using one of the following methods: // - Edit the setup file. // - At the command line, use an option such as -e RDA_TIMEOUT=600 // The value indicates the number of seconds an operating system // command can run before being interrupted. A zero value disables any // timeout. // *Mnemonic: GU_XML_WARNINGS // 00019,0, "Cannot package the reports using 'jar'" // *Cause: RDA detected an error when using jar to package the reports. // *Action: Check for any other errors reported by the jar command. Also check // the path that is stored in the setup file, which is used to execute // that command. // *Mnemonic: GU_JAR_ERROR // 00020,0, "Cannot create the transfer directory" // *Cause: RDA failed to create the transfer directory in the report directory. // *Action: Check the permissions and ownership of the report directory. // *Mnemonic: GU_XFR_CREATE // 00021,0, "Cannot delete the module" // *Cause: An attempt was made to delete a module that must be executed at each // run. // *Action: Consider setup as an alternative. // *Mnemonic: GU_DEL_MODULE // 00022,0, "Option '-f' required to delete the module and its collected data" // *Cause: RDA collected data for that module already. // *Action: Use the '-f' option to remove the collected data also. // *Mnemonic: GU_DEL_REPORTS // 00023,0, "Invalid list type" // *Cause: An invalid list type was provided. // *Action: Use 'levels', 'modules', 'profiles', 'tests', or 'tools' as list // types. // *Mnemonic: GU_BAD_TYPE // 00024,0, "Warning - Partially collected modules" // *Cause: RDA did not execute some sections in the specified modules. // *Action: Review the 'Report Settings' for more information about this error. // *Mnemonic: GU_SECTION_WARNINGS // 00025,0, "Bad option" // *Cause: RDA encountered an invalid option when parsing the command. // *Action: Check the command syntax and fix the error. // *Mnemonic: GU_BAD_OPTION // 00026,0, "Cannot package the reports using '7zip'" // *Cause: RDA detected an error when using 7zip to package the reports. // *Action: Check for any other errors reported by the 7zip command. Check the // path that is stored in the setup file, which is used to execute // that command. // *Mnemonic: GU_7ZIP_ERROR 00090,0, "Cannot create the lock file" // *Cause: RDA cannot create a lock file in its top directory. // *Action: The next line provides more information about that error. Take // appropriate actions to fix it. // *Mnemonic: GU_ENG_LOCK // 00091,0, "Cannot copy the compiled engine" // *Cause: RDA cannot make a copy of the compile engine to its top directory. // *Action: The next line provides more information about that error. Take // appropriate actions to fix it. // *Mnemonic: GU_ENG_COPY // 00092,0, "Cannot move the compiled engine" // *Cause: RDA cannot rename the compile engine copy in its top directory. // *Action: The next line provides more information about that error. Take // appropriate actions to fix it. // *Mnemonic: GU_ENG_MOVE // // /////////////////////////////////////////////////////////////////////////// // 00100.00199 Setup Errors (Agent.pm, Module.pm, Setting.pm) // /////////////////////////////////////////////////////////////////////////// // 00100,0, "Cannot create the setup file" // *Cause: RDA cannot create the setup file. // *Action: Check to see if the current user has write permissions to the // existing setup file and to the related directory (by default, the // RDA top directory.) // *Mnemonic: SETUP_CREATE_FAIL // 00101,0, "Invalid setup file" // *Cause: RDA encountered an error when loading the setup file. // *Action: Do not edit the setup file directly. Use the setup mode of RDA. // *Mnemonic: SETUP_BAD_FILE // 00102,0, "Invalid character in setting value" // *Cause: RDA found a carriage return, a line feed, or a &#nnn; character // in a setting value. // *Action: These characters are not allowed in setting values and must be // removed because they can cause setup file corruptions. // *Mnemonic: SETUP_BAD_CHAR // 00103,0, "Cannot open the setup specification file" // *Cause: RDA cannot open the module setup specification file. // *Action: Verify that the current user has permissions to access // and to open the setup specification file. // *Mnemonic: SETUP_OPEN_FAIL // 00104,0, "Invalid setup attribute keyword" // *Cause: RDA found an invalid attribute keyword. // *Action: Ensure that the keyword corresponds to a known attribute. // *Mnemonic: SETUP_BAD_KEY // 00105,0, "Invalid setup attribute value" // *Cause: RDA found an invalid attribute value. // *Action: There are invalid character(s) in the attribute value or extra // characters are found after an attribute value. RDA allows comments // only after an attribute value. Remove the offending characters. // *Mnemonic: SETUP_BAD_VALUE // 00106,0, "Unexpected setup specification" // *Cause: RDA found an invalid setup specification. // *Action: The corresponding line does not correspond to valid syntax. // Correct the invalid syntax. // *Mnemonic: SETUP_BAD_SPEC // 00107,0, "Error(s) in setup" // *Cause: RDA detected errors when loading the setup specifications. // *Action: Check the previous messages related to all errors found. // *Mnemonic: SETUP_LOAD_ERROR // 00108,0, "Invalid name" // *Cause: RDA found an invalid setting name. // *Action: The setting name can contain alphanumeric characters and // underscores only. A special name - also exists. Rename the setting // and omit the illegal characters. // *Mnemonic: SETUP_BAD_NAME // 00109,0, "Invalid type" // *Cause: RDA found an invalid setting type. // *Action: Enter a valid setting type. Valid types are: B (Boolean), // C (Comment), D (Directory), F (File), N (Number), T (Text). // *Mnemonic: SETUP_BAD_TYPE // 00110,0, "Cannot backup the setup file" // *Cause: RDA cannot rename the setup file under a new name. // *Action: Verify that the current user has write permissions to the existing // setup file and to the related directory, by default the RDA top // directory. // *Mnemonic: SETUP_BACKUP_FAIL // 00111,0, "Setup file already in use" // *Cause: The setup file is currently used by a concurrent run. // *Action: Wait until the completion of the other run and try again. // *Mnemonic: SETUP_IN_USE // 00112,0, "Cannot open the profile definition file" // *Cause: RDA cannot open the setup profile definition file. // *Action: Verify that the current user has permissions to access and to open // the setup profile definition file. // *Mnemonic: PROFILE_OPEN_FAIL // 00113,0, "Invalid profile specification value" // *Cause: RDA found an invalid value. // *Action: Invalid characters are found in the specification value or // extra characters are found after the value. RDA allows comments only // after a value. Remove the offending characters. // *Mnemonic: PROFILE_BAD_VALUE // 00114,0, "Invalid profile module list" // *Cause: RDA found an invalid module list. // *Action: Invalid characters were found in the module list or extra // characters were found after the list. RDA allows comments only // after a list. Remove the offending characters. // *Mnemonic: PROFILE_BAD_LIST // 00115,0, "Unexpected profile specification" // *Cause: RDA found an invalid setup profile specification. // *Action: The corresponding line does not correspond to valid syntax. // Correct the invalid syntax. // *Mnemonic: PROFILE_BAD_SPEC // 00116,0, "Error(s) in profile definition file" // *Cause: RDA detected errors when loading the setup profile specifications. // *Action: Check the previous messages related to all errors found. // *Mnemonic: PROFILE_LOAD_ERROR // 00117,0, "Invalid validation type" // *Cause: RDA found an invalid setting validation. // *Action: Enter a valid setting validation type. Valid types are: E (Error), // N (No validation), W (Warning) // *Mnemonic: SETUP_BAD_VALIDATION // 00118,0, "Invalid setting value" // *Cause: RDA detected an invalid setting value. // *Action: See the previous line(s) for more explanations about the error. // *Mnemonic: SETUP_INVALID_SETTING // 00119,0, "Invalid word" // *Cause: A word can contain alphanumeric characters only. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: SETUP_INVALID_WORD // 00120,0, "Cannot open pager" // *Cause: RDA failed to open the pager. // *Action: Check the setting of the PAGER environment variable. // *Mnemonic: SETUP_PAGER_FAIL // 00121,0, "RDA setup interrupted" // *Cause: The RDA program was interrupted during the setup of a data // collection module. // *Action: Run RDA again as appropriate. // *Mnemonic: SETUP_INTERRUPT // 00122,0, "Invalid profile name" // *Cause: RDA cannot find the specified profile name. // *Action: Check the list of defined profiles, particularly if the RDA_PROFILE // environment variable is used. // *Mnemonic: PROFILE_BAD_NAME // 00123,0, "Missing setup file" // *Cause: The INI module was not configured yet in that setup file. // *Action: Configure a module first before executing that request. // *Mnemonic: SETUP_MISSING // 00124,0, "Filter not enabled" // *Cause: The filter is not defined or not active. // *Action: Define the filter and enable it. // *Mnemonic: NO_FILTER // 00125,0, "Cannot create the filter file" // *Cause: RDA encountered an error when creating the filter file. // *Action: Check the existence and the permissions of the work directory and // of a possible previous file. // *Mnemonic: SAVE_FILTER // 00126,0, "Incompatible profiles" // *Cause: RDA cannot combine profiles from different types. // *Action: Collect the different collection types separately. // *Mnemonic: PROFILE_BAD_COMBINATION // 00130,0, "Cannot load the associated logic" // *Cause: RDA encountered errors when loading the associated logic. // *Action: Check the module syntax and fix errors. // *Mnemonic: LOAD_EXE // 00131,0, "Invalid property" // *Cause: The associated logic tried to access a property that does not exist. // *Action: Review and fix the associated logic. // *Mnemonic: BAD_EXE_PROPERTY // // /////////////////////////////////////////////////////////////////////////// // 00200.00299 Collect Errors (Block.pm) // /////////////////////////////////////////////////////////////////////////// // 00200,0, "Cannot create the report directory" // *Cause: RDA failed to create the report directory. // *Action: Check the existence, permissions, and ownership of the report // directory's parent directories. Verify that the name of the report // directory does not contain references to shell variables. // *Mnemonic: COLLECT_DIR_CREATE // 00201,0, "Report file not specified" // *Cause: A report declaration is missing. // *Action: Declare the report. The report must be declared before the first // attempt to write to the report file. // *Mnemonic: COLLECT_NO_REPORT // 00202,0, "Cannot create the report file" // *Cause: RDA cannot create the report file. // *Action: Correct the permissions problem and execute RDA again. // Alternatively, specify another report directory by running the // setup of the initialization module again, using the following // command arguments: // -S INI // *Mnemonic: COLLECT_OUTPUT_CREATE // 00203,0, "Cannot create the TOC file" // *Cause: RDA cannot create the Table of Content file. // *Action: Correct the permissions problem and execute RDA again. // Alternatively, specify another report directory by running the // setup of the initialization module again, using the following // command arguments: // -S INI // *Mnemonic: COLLECT_TOC_CREATE // 00204,0, "Cannot create a test file in the report directory" // *Cause: RDA cannot create the test file in the report directory. // *Action: Correct the permissions problem and execute RDA again. // Alternatively, specify another report directory by running the // setup of the initialization module again, using the following // command arguments: // -S INI // *Mnemonic: COLLECT_TEST_CREATE // 00205,0, "Cannot remove the test file from the report directory" // *Cause: RDA cannot remove the test file from the report directory. // *Action: RDA must be able to remove temporary and report files from the // report directory. It is required for maintaining the report // consistency when running RDA multiple times. Correct the permissions // problem and execute RDA again. Alternatively, specify another // report directory by running the setup of the initialization module // again, using the following command arguments: // -S INI // *Mnemonic: COLLECT_TEST_UNLINK // 00206,0, "RDA data collection interrupted" // *Cause: The RDA program was interrupted during data collection. // *Action: Report the error, providing contextual information when RDA // was interrupted for a possible hang. // *Mnemonic: COLLECT_INTERRUPT // 00207,0, "Not enough free space for running RDA" // *Cause: The available space on the disk partition, where the report // directory resides, is less than the minimum specified by the // RDA_FREE setting. // *Action: Free some space or relocate the report directory on another disk // with more available space. // *Mnemonic: COLLECT_FREE // 00208,0, "Not enough free space to complete the output request" // *Cause: The available space on the disk partition, where the report // directory resides, is not enough to complete the output request. // *Action: Free some space or relocate the report directory on another disk // with more available space. // *Mnemonic: OUTPUT_FREE // 00209,0, "Collect error" // *Cause: The collection was aborted. // *Action: Look at the associated message and determine the appropriate // actions. // *Mnemonic: COLLECT_ERROR // 00210,0, "Invalid or missing macro call" // *Cause: RDA found an invalid argument in a call command. // *Action: Make sure that the argument of a 'call' command is a macro call. // *Mnemonic: COLLECT_CALL_ARG // 00211,0, "Missing scalar variable" // *Cause: No scalar variable was specified in the 'for' or 'loop' command. // *Action: Make sure that all 'for' or 'loop' commands include a scalar // variable to contain the current iteration value. // *Mnemonic: COLLECT_LOOP_VAR // 00212,0, "Invalid command format" // *Cause: RDA found an invalid for format. // *Action: Make sure that all 'for' statements have 2 or 3 values, to define // the value interval and the incrementation value. // *Mnemonic: COLLECT_FOR_INTERVAL // 00213,0, "Missing scalar variable" // *Cause: No variable was specified in the 'decr' or 'incr' command. // *Action: Make sure that a scalar variable (including an array or hash item) // is the first argument of a decr or incr command. // *Mnemonic: COLLECT_INCR_VAR // 00214,0, "Extra value(s) found" // *Cause: RDA found more values than expected. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: COLLECT_EXTRA_VALUE // 00215,0, "Invalid or missing name" // *Cause: RDA detected an invalid or missing name. // *Action: Make sure that all output, macro, named block, and section names // start with a letter that is followed by additional alphanumeric // characters. // *Mnemonic: COLLECT_NAME // 00216,0, "Invalid or missing name" // *Cause: RDA detected an invalid or missing name. // *Action: Make sure that all submodule names in a run command contain // alphanumeric characters only. // *Mnemonic: COLLECT_RUN_NAME // 00217,0, "Invalid left value list" // *Cause: The left value list of a var command does not contain variables only. // *Action: Make sure that the left value list contains variables, // variable references, array or hash items only. // *Mnemonic: COLLECT_VAR_BAD_LIST // 00218,0, "Invalid value" // *Cause: The argument is a value that cannot be used as left value. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: COLLECT_BAD_LVALUE // 00219,0, "Invalid or missing variable" // *Cause: RDA detected an invalid or missing variable in an assignment // operation. // *Action: Make sure that the var command argument begins with a variable // or a variable list followed by an assignment if required. Make sure // that the global command begins with a valid global variable name. // *Mnemonic: COLLECT_VAR_BAD_LIST // 00220,0, "Invalid value(s) found in variable list" // *Cause: RDA found invalid values in the 'delete', 'import', or 'keep' // arguments. // *Action: Make sure that the variables are included as arguments only. // *Mnemonic: COLLECT_BAD_VARIABLE // 00221,0, "Invalid variable" // *Cause: RDA detected an invalid variable in a 'set' or an 'append' command. // *Action: Make sure that a scalar variable is used. // *Mnemonic: COLLECT_NO_VARIABLE // 00222,0, "Missing opening parenthesis" // *Cause: RDA expects an opening parenthesis. // *Action: Make sure that the value or argument list begins with a parenthesis. // *Mnemonic: COLLECT_START_PARENTHESIS // 00223,0, "Missing closing parenthesis" // *Cause: RDA expects a closing parenthesis. // *Action: A closing parenthesis terminates lists. The parser can be // confused by invalid syntax inside a list. Make sure that the list // ends with a parenthesis. // *Mnemonic: COLLECT_END_PARENTHESIS // 00224,0, "Invalid or missing array index" // *Cause: RDA expected a single value as an array index. // *Action: Make sure that the array index contains only one value, and that // the value can be evaluated as a number. // *Mnemonic: COLLECT_BAD_INDEX // 00225,0, "Missing closing bracket" // *Cause: RDA expects a closing bracket in the expression. // *Action: Make sure that the array index or anonymous array reference ends // with a closing (square) bracket. // *Mnemonic: COLLECT_END_BRACKET // 00226,0, "Invalid or missing hash key" // *Cause: RDA expects a single value as a hash key. // *Action: Make sure that the hash key contains only one value, and that the // value can be evaluated as a text string. // *Mnemonic: COLLECT_BAD_KEY // 00227,0, "Missing closing brace" // *Cause: RDA expects a closing brace in the expression. // *Action: Make sure that the hash key, the anonymous hash reference, the // subscripted expression converter, or the property name ends with a // closing brace (curly bracket). // *Mnemonic: COLLECT_END_BRACE // 00228,0, "Invalid argument list end" // *Cause: RDA expects a closing parenthesis at the end of a macro or named // block call. // *Action: Make sure that the macro has an argument list. Even if there are no // arguments, an empty list must be provided. Argument lists are // optional for named block calls. An argument list must be terminated // by a closing parenthesis. // *Mnemonic: COLLECT_END_MACRO // 00229,0, "Invalid value" // *Cause: RDA found an unrecognized value. // *Action: The parser is not able to identify the value. // *Mnemonic: COLLECT_BAD_VALUE // 00230,0, "Invalid report file type" // *Cause: An invalid report file type was specified. // *Action: Specify a valid report file type: OF, ON, RF, RN, SF, or SN. // *Mnemonic: COLLECT_OUTPUT_TYPE // 00231,0, "Cannot open the report file" // *Cause: RDA cannot open the report file. // *Action: Verify the permissions of the report file and take appropriate // actions. // *Mnemonic: COLLECT_OUTPUT_OPEN // 00232,0, "Cannot create the reference file" // *Cause: RDA cannot create the reference file. // *Action: Correct the permissions problem and execute RDA again. // *Mnemonic: COLLECT_REF_CREATE // 00233,0, "Cannot open the reference file" // *Cause: RDA cannot open the reference file. // *Action: Verify the permissions of the reference file and take appropriate // actions. // *Mnemonic: COLLECT_REF_OPEN // 00234,0, "Cannot create the sample file" // *Cause: RDA cannot create the sample file. // *Action: Correct the permissions problem and execute RDA again. // *Mnemonic: COLLECT_SAMPLE_CREATE // 00235,0, "Cannot open the sample file" // *Cause: RDA cannot open the sample file. // *Action: Verify the permissions of the sample file and take appropriate // actions. // *Mnemonic: COLLECT_SAMPLE_OPEN // 00236,0, "Cannot create the alias file" // *Cause: RDA cannot create the alias file in the report directory. // *Action: Correct the permissions problem and execute RDA again. // *Mnemonic: COLLECT_ALIAS_CREATE // 00237,0, "The report file prefix is too long" // *Cause: Key parts of the report file names could be truncated. // *Action: Specify a shorter prefix. Rerun the initialization module setup by // specifying '-S INI' as command arguments. // *Mnemonic: COLLECT_ALIAS_OPEN // 00238,0, "Cannot create the communication pipe" // *Cause: RDA cannot create the communication pipe. // *Action: Verify the associated command. // *Mnemonic: COLLECT_OUTPUT_PIPE // 00239,0, "Cannot open pager" // *Cause: RDA failed to open the pager. // *Action: Check the setting of the PAGER environment variable. // *Mnemonic: COLLECT_PAGER_FAIL // 00240,0, "Break or next used outside a loop" // *Cause: RDA found a break or next command outside a for, a loop, a once, or // a while command. // *Action: Report the error, providing contextual information to reproduce // the problem. // *Mnemonic: COLLECT_BAD_BREAK // 00241,0, "Error encountered in the block called" // *Cause: RDA detected an error when executing a submodule. // *Action: Report the error and the previous errors. // *Mnemonic: COLLECT_RUN_ERROR // 00242,0, "Missing if command" // *Cause: RDA found an else or elsif command without a previous if command // in the current block. // *Action: Report the error, providing contextual information to reproduce // the problem. // *Mnemonic: COLLECT_IF // 00243,0, "Invalid operator" // *Cause: RDA did not find the operator definition. // *Action: Report the error, providing contextual information to reproduce // the problem. // *Mnemonic: COLLECT_BAD_OPERATOR // 00244,0, "Invalid test module name" // *Cause: The module name provided to the test command does not correspond to // a tool or a test module. // *Action: Report the error, providing contextual information to reproduce // the problem. // *Mnemonic: COLLECT_TEST_NAME // 00245,0, "Undefined global variable" // *Cause: RDA does not accept undefined global variables. // *Action: Define the global variable through the global or use mechanism. // *Mnemonic: COLLECT_BAD_GLOBAL // 00246,0, "Invalid or missing alias name" // *Cause: The alias name is missing or contains nonalphanumeric characters. // *Action: Fix the definition. // *Mnemonic: COLLECT_ALIAS_NAME // 00247,0, "Invalid or missing alias definition" // *Cause: The alias definition is not a method invocation. // *Action: Fix the alias definition. // *Mnemonic: COLLECT_ALIAS_DEF // 00248,0, "Reporting disabled" // *Cause: There is no reporting control object associated with the top block. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: COLLECT_NO_OUTPUT // 00249,0, "Thread nesting" // *Cause: A thread or a job cannot contain another thread or job. // *Action: Review the logic and eliminate the nested thread or the nested job. // *Mnemonic: THREAD_NESTING // 00250,0, "Invalid value type" // *Cause: An invalid type is specified in value creation. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: VAL_BAD_TYPE // 00251,0, "Invalid reference assignment" // *Cause: RDA expects a reference to be assigned to that variable. // *Action: Report the error. // *Mnemonic: VAL_BAD_REF // 00253,0, "Error encountered in the macro called" // *Cause: RDA encountered an error in a macro and propagated it to the // calling context. // *Action: Report the error, along with any previous errors. // *Mnemonic: VAL_MACRO_ERROR // 00254,0, "Undefined macro" // *Cause: The macro is not defined. // *Action: Report the error. // *Mnemonic: VAL_UNKNOWN_MACRO // 00255,0, "Not a numeric value" // *Cause: RDA cannot convert the value to a number. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: VAL_BAD_NUMBER // 00256,0, "Not a text string" // *Cause: RDA cannot convert the value to a text string. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: VAL_BAD_TEXT // 00260,0, "Cannot open the specification file" // *Cause: RDA cannot find a specification file for the specified module. // *Action: An invalid module name has been specified. Look in the // module list or in the modules directory for the exact name. // *Mnemonic: LOAD_FILE // 00266,0, "Unknown object" // *Cause: RDA did not find any package associated with the class. // *Action: Check the class name and when a corresponding package is available // in the RDA/Object directory. // *Mnemonic: COLLECT_UNKNOWN_OBJECT // 00267,0, "Bad object" // *Cause: The package associated with the specified class does not contain any // object definition interface. // *Action: Check that the class name is correct and that the associated // package contains a public and valid %SDCL variable. // *Mnemonic: COLLECT_BAD_OBJECT // 00268,0, "Bad class" // *Cause: RDA cannot determine which Perl package is associated with the class // name. // *Action: Fix the class name. // *Mnemonic: COLLECT_BAD_CLASS // 00269,0, "Unknown named block" // *Cause: RDA did not find the name block in the specified context. // *Action: Check that the named block reference is in the same context than // its definition. // *Mnemonic: COLLECT_CODE_UNKNOWN // 00270,0, "Error encountered in the named block called" // *Cause: RDA detected an error when executing a named block. // *Action: Report the error and the previous errors. // *Mnemonic: COLLECT_CODE_ERROR // 00271,0, "Duplicate section" // *Cause: Two sections have the same name. // *Action: Make sure that every section has a unique name. // *Mnemonic: COLLECT_DUP_SECTION // 00272,0, "Invalid block start" // *Cause: RDA found a block start that is not associated with any command. // *Action: Review and fix the code syntax. // *Mnemonic: COLLECT_BAD_START // 00273,0, "Invalid block end" // *Cause: RDA found a block end without a corresponding block start. // *Action: Review and fix the code syntax. // *Mnemonic: COLLECT_NO_END // 00274,0, "Missing block end" // *Cause: A block is not ended in the same section. // *Action: Review and fix the code syntax. // *Mnemonic: COLLECT_BAD_END // 00275,0, "Invalid characters at end of line" // *Cause: RDA found characters when expecting an end of line (or a comment). // *Action: Review and fix the code syntax. // *Mnemonic: COLLECT_BAD_CHARACTERS // 00276,0, "No corresponding loop" // *Cause: The name does not correspond to a for, a loop, a once, or a while // command in the same context. // *Action: Review and fix the logic. // *Mnemonic: COLLECT_BAD_LOOP_NAME // 00290,0, "No filter rules" // *Cause: No filter rules found // *Action: Review the filter definition and take appropriate actions. // *Mnemonic: NO_RULES // 00291,0, "Filter code error" // *Cause: RDA cannot create the filter code created from the specified rules. // *Action: Review the filter definition and take appropriate actions. // *Mnemonic: BAD_FILTER // // /////////////////////////////////////////////////////////////////////////// // 00300.00399 Render Errors (Render.pm) // /////////////////////////////////////////////////////////////////////////// // 00300,0, "Cannot create the report directory" // *Cause: RDA failed to create the report directory. // *Action: Check the existence, permissions, and ownership of the report // directory's parent directories. Verify that the name of the report // directory does not contain references to shell variables. // *Mnemonic: RPT_DIR_CREATE // 00301,0, "Cannot open the report directory" // *Cause: RDA failed to read the report directory content. // *Action: Check the permissions to access the report directory. // *Mnemonic: RPT_DIR_OPEN // 00302,0, "Cannot open the format specification file" // *Cause: RDA failed to open the format specification file. // *Action: Check the permissions to access files in the report directory. // *Mnemonic: RPT_TEXT_OPEN // 00303,0, "Cannot create the report file" // *Cause: RDA failed to create the report file in the report directory. // *Action: Check the permissions of the report directory. // *Mnemonic: RPT_HTML_CREATE // 00304,0, "Cannot create the index format specifications" // *Cause: RDA failed to create the index format specification file in the // report directory. // *Action: Check the permissions of the report directory. // *Mnemonic: RPT_INDEX_CREATE // 00305,0, "Cannot create the subindex format specifications" // *Cause: RDA failed to create the subindex format specification file in the // report directory. // *Action: Check the permissions of the report directory. // *Mnemonic: RPT_SUB_INDEX_CREATE // 00306,0, "Cannot create the start file" // *Cause: RDA failed to create the start file in the report directory. // *Action: Check the permissions of the report directory. // *Mnemonic: RPT_START_CREATE // 00307,0, "Cannot create the blank file" // *Cause: RDA failed to create the blank file in the report directory. // *Action: Check the permissions of the report directory. // *Mnemonic: RPT_BLANK_CREATE // 00308,0, "Cannot launch rendering subprocess" // *Cause: RDA is not able to execute itself. // *Action: Adapt the configuration to allow RDA to be launched by itself. // *Mnemonic: COLLECT_RENDER_PIPE // // /////////////////////////////////////////////////////////////////////////// // 00400.00499 Manual Page Errors (Pod.pm) // /////////////////////////////////////////////////////////////////////////// // 00400,0, "Cannot display manual pages" // *Cause: RDA failed to display the manual pages due to missing Perl packages. // *Action: If available, use a more recent or complete Perl environment. // *Mnemonic: MAN_DISPLAY_FAIL // 00401,0, "Missing or invalid manual file" // *Cause: RDA failed to find the corresponding file. // *Action: Check to see if the name corresponds to an existing module or to // a '.def' or 'pod' file in the modules directory. // *Mnemonic: MAN_MISSING // 00402,0, "Cannot open the manual file" // *Cause: RDA failed to open the manual file. // *Action: Check the permissions of the modules directory and contained files. // *Mnemonic: MAN_OPEN_FAIL // 00403,0, "Cannot open pager" // *Cause: RDA failed to open the pager. // *Action: Check the setting of the PAGER environment variable. // *Mnemonic: MAN_PAGER_FAIL // // /////////////////////////////////////////////////////////////////////////// // 00500.00599 Macro Errors // /////////////////////////////////////////////////////////////////////////// // 00500,0, "Expecting a hash variable as argument" // *Cause: The argument is not a hash. // *Action: Verify that 'keys' has a hash as an argument. // *Mnemonic: INVALID_HASH // 00501,0, "Database accesses disabled due to a connection problem" // *Cause: RDA cannot connect to execute a simple SQL statement. // *Action: Look at the associated error message for more information about the // problem. // - Ensure there are no prompts being made by // $ORACLE_HOME/sqlplus/admin/glogin.sql or $HOME/login.sql. // - If the userid is incorrect, rerun the database module setup by // specifying '-S DB' as command arguments. // - If the userid is correct, then maybe an incorrect password was // specified // - If the password is incorrect, provide a valid password when // prompted. // Remember that for SYSDBA users, the password used should be the // database password for the user and not the password stored in the // password file. // *Mnemonic: NO_CONNECTION // 00502,0, "Database connection timeout" // *Cause: The database cannot execute the SQL statement(s) in the specified // time. // *Action: If there are no database problems, increase the SQL_TIMEOUT value // using one of the following methods: // - Edit the setup file. // - At the command line, use an option such as -e SQL_TIMEOUT=120 // The value indicates the number of seconds a database request can // run before being interrupted. A zero value disables any timeout. // *Mnemonic: SQL_TIMEOUT // 00503,0, "Cannot create the pipe" // *Cause: RDA cannot create a communication pipe. // *Action: Report the problem to Oracle Support. Include information about the // Perl version used (cf. Perl -V) // *Mnemonic: PIPE_ERROR // 00504,0, "Cannot fork" // *Cause: A new process cannot be forked. // *Action: Report the problem to Oracle Support. Include information about the // Perl version used (cf. Perl -V) // *Mnemonic: FORK_ERROR // 00505,0, "Cannot launch SQL*Plus" // *Cause: RDA cannot launch SQL*Plus. // *Action: Verify that SQL*Plus is available from the command line. // *Mnemonic: NO_SQLPLUS // 00506,0, "Cannot create the temporary SQL script" // *Cause: RDA failed to create a temporary file with the SQL script. // *Action: Check the permissions of the report directory. // *Mnemonic: SQL_TEMP_ERROR // 00507,0, "SQL Error" // *Cause: RDA received an error when executing the SQL statements. // *Action: Check the associated error message and take appropriate actions. // *Mnemonic: SQL_ERROR // 00508,0, "Null password given; logon denied" // *Cause: An empty password was provided // *Action: A password must be specified. // *Mnemonic: NO_PASSWORD // 00509,0, "Missing SQL code" // *Cause: No SQL code was provided. // *Action: Provide some SQL code. // *Mnemonic: NO_SQL // 00510,0, "SQL execution disabled" // *Cause: The maximum number of tries has been reached. // *Action: The execution of SQL statements is disabled due to a // connection test error or too many timeouts. If there are // no database problems, increase the SQL_TIMEOUT value using one // of the following methods: // - Edit the setup file. // - At the command line, use an option such as -e SQL_TIMEOUT=120 // The value indicates the number of seconds a database request can // run before being interrupted. A zero value disables any timeout. // *Mnemonic: SQL_DISABLED // 00511,0, "Cannot create the remote directory" // *Cause: RDA failed to create the remote directory in the report directory. // *Action: Check the permissions and ownership of the report directory. // *Mnemonic: REM_DIR_CREATE_FAIL // 00512,0, "Cannot create the remote log file" // *Cause: RDA cannot create the remote log file in the remote directory. // *Action: Check the permissions and ownership of the remote directory in the // report directory. // *Mnemonic: REM_LOG_CREATE_FAIL // 00513,0, "Missing remote shell command" // *Cause: RDA cannot find a remote shell command (ssh, rsh, or remsh). // *Action: Check the PATH environment variable or define a reference to // an alternative tool with the REMOTE_SSH_COMMAND and // REMOTE_SSH_OPTIONS settings. // *Mnemonic: REM_NO_SSH // 00514,0, "Missing remote file copy command" // *Cause: RDA cannot find a remote file copy command (scp or rcp). // *Action: Check the PATH environment variable or define a reference to // an alternative tool with the REMOTE_SSH_COMMAND and // REMOTE_SSH_OPTIONS settings. // *Mnemonic: REM_NO_SCP // 00515,0, "Cannot access environment variables" // *Cause: PERL_ENV_TABLES is not set correctly. When perl "-V" is executed, it // produces an error also: %RMS-F-SYN, file specification syntax error. // *Action: Check that PERL_ENV_TABLES has CRTL_ENV as the first element // in its value list and that all elements are valid. // *Mnemonic: ENV_COPY_ERROR // 00516,0, "Expecting an array or a hash variable as first argument" // *Cause: The first argument is not an array or a hash. // *Action: Verify that the first argument is an array or a hash. // *Mnemonic: INVALID_ARRAY_HASH // 00517,0, "'new' macro not supported for that class" // *Cause: The class does not support object creation in the SDCL code. // *Action: Review the logic. // *Mnemonic: NO_NEW // 00518,0, "Object creation error" // *Cause: RDA encountered an error during object creation. // *Action: Look at the other error messages and take appropriate actions. // *Mnemonic: NEW_ERROR // 00519,0, "Missing DSN" // *Cause: No data source name (DSN) has been provided at login time. // *Action: Specify the data source name. // *Mnemonic: NO_DSN // 00520,0, "PL/SQL not supported through ODBC" // *Cause: ODBC does not allow to get PL/SQL results directly. // *Action: Consider alternatives. // *Mnemonic: NO_PLSQL // 00521,0, "Missing or invalid JDBC connection information" // *Cause: No valid connection information has been provided at login time. // *Action: Specify the driver class and the connection URL separated by a pipe // character. // *Mnemonic: JDBC_NO_DRV_URL // 00522,0, "Launch error" // *Cause: RDA detected an error when launching its JDBC server. // *Action: Check the associated error message and take appropriate actions. // *Mnemonic: JDBC_LAUNCH // 00523,0, "Request error" // *Cause: RDA received an error when executing a JDBC request. // *Action: Check the associated error message and take appropriate actions. // *Mnemonic: JDBC_REQUEST // // /////////////////////////////////////////////////////////////////////////// // 00600.00699 Background Collection Errors (Daemon.pm) // /////////////////////////////////////////////////////////////////////////// // 00600,0, "Cannot create the daemon file" // *Cause: RDA failed to create the background collection control file. // *Action: Check if the current user can create a file in the directory where // the setup file is located or in the directory specified by the // RDA_PID environment variable when defined. // *Mnemonic: DMN_CREATE_CTL // 00601,0, "Cannot redirect input" // *Cause: RDA failed to redirect the standard input of the background process. // *Action: Check that the current user can read from /dev/null. // *Mnemonic: DMN_INPUT // 00602,0, "Cannot redirect output" // *Cause: RDA failed to redirect the standard output of the background process. // *Action: If an output file has been specified, check that it can be // created. Otherwise, check that the current user can write to // /dev/null. // *Mnemonic: DMN_OUTPUT // 00603,0, "Cannot halt the background collection" // *Cause: RDA failed to rename the background collection control file. // *Action: If the file is still present, check the file permissions and owner. // *Mnemonic: DMN_HALT // 00604,0, "Cannot create the archive directory" // *Cause: RDA failed to create the archive directory inside the report // directory. // *Action: Check the permissions and ownership of the report directory. // *Mnemonic: DMN_CREATE_ARC // 00605,0, "Cannot create the ref directory" // *Cause: RDA failed to create the ref directory inside the report directory. // *Action: Check the permissions and ownership of the report directory. // *Mnemonic: DMN_CREATE_REF // 00606,0, "Cannot create the sample directory" // *Cause: RDA failed to create the sample directory inside the report // directory. // *Action: Check the permissions and ownership of the report directory. // *Mnemonic: DMN_CREATE_SMP // 00607,0, "Cannot change to the sample directory" // *Cause: RDA failed to change the current directory to the sample directory. // *Action: Check the path and the permissions of the sample directory. The // directory does not always exist before samples are collected. // *Mnemonic: DMN_CD_SMP // 00608,0, "Cannot list the samples" // *Cause: RDA cannot open the sample directory. // *Action: Check access to the samples. // *Mnemonic: DMN_LS_SMP // 00609,0, "Cannot change to the RDA install directory" // *Cause: RDA failed to change the current directory to its install directory. // *Action: Check the path and the permissions of the install directory. // *Mnemonic: DMN_CD_HOME // 00610,0, "Cannot zip the reports" // *Cause: RDA detected an error when using zip to package the reports. // *Action: Check for any other error reported by the zip command. Also check // the path that is stored in the setup file, which is used to execute // that command. // *Mnemonic: DMN_ZIP_ERROR // 00611,0, "Cannot package the reports using pax" // *Cause: RDA detected an error when using pax to package the reports. // *Action: Check for any other error reported by the pax command. Also check // the path that is stored in the setup file, which is used to execute // that command. // *Mnemonic: DMN_PAX_ERROR // 00612,0, "Cannot package the reports using tar" // *Cause: RDA detected an error when using tar to package the reports. // *Action: Check for any other error reported by the tar command. Also check // the path that is stored in the setup file, which is used to // execute that command. // *Mnemonic: DMN_TAR_ERROR // 00613,0, "Archive command not -yet- identified" // *Cause: RDA cannot find any packaging tool paths. // *Action: The path to zip or tar commands has not been collected. This // typically occurs when the end report has not been produced yet // or if these commands have not been found in the current execution // path (cf. PATH). // *Mnemonic: DMN_PKG_ERROR // 00614,0, "Cannot package the reports using jar" // *Cause: RDA detected an error when using jar to package the reports. // *Action: Check for any other error reported by the jar command. Also check // the path that is stored in the setup file, which is used to execute // that command. // *Mnemonic: DMN_JAR_ERROR // 00615,0, "Cannot create the sample alias file" // *Cause: RDA cannot create the alias file in the sample directory. // *Action: Correct the permissions problem and execute RDA again. // *Mnemonic: DMN_ALIAS_CREATE // 00616,0, "Cannot open the sample alias file" // *Cause: RDA cannot open the sample alias file. // *Action: Correct the permissions problem and execute RDA again. // *Mnemonic: DMN_ALIAS_OPEN // // /////////////////////////////////////////////////////////////////////////// // 00800.00899 Context and Value Errors // /////////////////////////////////////////////////////////////////////////// // 00800,0, "Cannot modify the internal variable" // *Cause: You cannot assign a new value to the specified internal variable. // *Action: Modify the code appropriately. // *Mnemonic: CTX_BAD_INTERNAL // 00801,0, "Pointer loop detected" // *Cause: RDA detected that a reference chain contains a reference to an // upper reference. // *Action: Modify the code to prevent such a reference loop. // *Mnemonic: CTX_POINTER_LOOP // 00802,0, "Pointer referencing a missing variable" // *Cause: The variable referenced by the point does not exist anymore. // *Action: Modify the code to prevent that situation. // *Mnemonic: CTX_BAD_POINTER // 00803,0, "Invalid value type" // *Cause: The current execution context cannot determine the variable type. // *Action: Provide a valid variable name. The name must start with a '$', '@', // or '%' character only. // *Mnemonic: CTX_BAD_TYPE // 00804,0, "Bad variable for increment or decrement operation" // *Cause: Increment or decrement operation is possible on scalar variables // only. // *Action: Modify the code to prevent that situation. // *Mnemonic: CTX_BAD_VARIABLE // 00805,0, "Bad internal variable abbreviation" // *Cause: The internal variable abbreviation is missing or invalid. // *Action: Internal variable abbreviations must start with a letter, possibly // followed by alphanumeric characters. // *Mnemonic: CTX_BAD_ABBREVIATION // 00810,0, "Cannot determine if the value is usable as a left value" // *Cause: The value is not usable as a left value. // *Action: Modify the code to prevent that situation. // *Mnemonic: VALUE_BAD_LEFT // 00811,0, "Cannot use the value in complex data structures" // *Cause: The value is not usable in such a data structure. // *Action: Modify the code to prevent that situation. // *Mnemonic: VALUE_BAD_COMPLEX // 00812,0, "Cannot delete the value" // *Cause: No deletion mechanism is available for such a value. // *Action: Modify the code to prevent that situation. // *Mnemonic: VALUE_BAD_DELETE // 00813,0, "Cannot convert the value in a Perl list" // *Cause: No conversion approach defined for such a value. // *Action: Modify the code to prevent that situation. // *Mnemonic: VALUE_BAD_CONVERT // 00814,0, "Not a numeric value" // *Cause: RDA cannot convert the value to a number. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: VALUE_BAD_NUMBER // 00815,0, "Not a text string" // *Cause: RDA cannot convert the value to a text string. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: VALUE_BAD_TEXT // 00820,0, "Incompatible types" // *Cause: The value is incompatible with the expected value type. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: VALUE_INCOMPATIBLE_TYPE // 00821,0, "Array expected" // *Cause: RDA expected an array to perform the operation. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: VALUE_ARRAY_EXPECTED // 00822,0, "Hash expected" // *Cause: RDA expected a hash to perform the operation. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: VALUE_HASH_EXPECTED // 00823,0, "Invalid value type" // *Cause: RDA cannot use such a value type to perform the operation. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: VALUE_BAD_TYPE // 00824,0, "Object required to invoke a method" // *Cause: The associated value is not an object reference or an undefined // value. // *Action: Take care that the associate value is an object reference. // *Mnemonic: VALUE_NO_OBJECT // 00825,0, "Unknown object type" // *Cause: The object type does not corresponded to any loaded class. // *Action: Load the class with the use command. // *Mnemonic: VALUE_UNKNOWN_CLASS // 00826,0, "Undefined method" // *Cause: The method is not included in the list of valid methods. // *Action: Use defined methods only. // *Mnemonic: VALUE_BAD_METHOD // 00827,0, "Error encountered in method" // *Cause: RDA encountered an error when executing the method. // *Action: Check the other errors and take appropriate actions. // *Mnemonic: VALUE_METHOD_ERROR // 00828,0, "Invalid value type to assign" // *Cause: The value type is not supported in value assignments. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: VALUE_INVALID_ASSIGN // 00829,0, "Invalid value type to delete" // *Cause: The value type is not supported in value deletions. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: VALUE_INVALID_DELETE // 00830,0, "Assign not implemented" // *Cause: No assign mechanism defined for the value type. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: VALUE_NO_ASSIGN // 00831,0, "Find not implemented" // *Cause: No find mechanism defined for the value type // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: VALUE_NO_FIND // 00832,0, "Delete not implemented" // *Cause: No delete mechanism defined for the value type // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: VALUE_NO_DELETE // 00833,0, "Invalid internal variable name" // *Cause: RDA did not retrieve the internal variable definition. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: VALUE_BAD_INTERNAL // 00834,0, "Cannot assign a new value to the property" // *Cause: No assignment mechanism associated with the property. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: VALUE_PROP_ASSIGN // 00835,0, "Invalid property name" // *Cause: RDA encountered an invalid name in a dynamic property. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: VALUE_PROP_NAME // 00836,0, "Cannot open a pipe to the named block" // *Cause: The block language does not allow to pipe data to the named block. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: VALUE_BAD_PIPE // // /////////////////////////////////////////////////////////////////////////// // 00900.00999 Operator Errors // /////////////////////////////////////////////////////////////////////////// // 00900,0, "Array expected" // *Cause: RDA expected an array reference as the operator argument. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: ARRAY_EXPECTED // 00901,0, "Extra value(s) found" // *Cause: RDA found more values than expected. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: ARRAY_EXTRA_VALUE // 00902,0, "Missing array argument" // *Cause: The operator requires more arguments. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: ARRAY_ARG_MISSING // 00903,0, "Incompatible types" // *Cause: Variable and value types are incompatible. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: ARRAY_INCOMPATIBLE // 00910,0, "Hash expected" // *Cause: RDA expected a hash reference as the operator argument. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: HASH_EXPECTED // 00911,0, "Extra value(s) found" // *Cause: RDA found more values than expected. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: HASH_EXTRA_VALUE // 00912,0, "Missing argument" // *Cause: The operator requires more arguments. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: HASH_ARG_MISSING // 00920,0, "Missing scalar variable" // *Cause: No variable was specified in the 'decr' or 'incr' command. // *Action: Make sure that a scalar variable (including an array or hash item) // is the first argument of a decr or incr command. // *Mnemonic: SCALAR_INCR_VAR // 00921,0, "Extra value(s) found" // *Cause: RDA found more values than expected. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: SCALAR_EXTRA_VALUE // 00930,0, "Expecting an array or a hash variable as first argument" // *Cause: The first argument is not an array or a hash. // *Action: Verify that the first argument is an array or a hash. // *Mnemonic: OPER_INVALID_ARRAY_HASH // 00931,0, "Extra value(s) found" // *Cause: RDA found more values than expected. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: OPER_EXTRA_VALUE // 00932,0, "Missing argument" // *Cause: The operator requires more arguments. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: OPER_ARG_MISSING // 00933,0, "Invalid first argument" // *Cause: The argument is not a value that can be used as a left value. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: OPER_BAD_FIRST // 00934,0, "Invalid left value to assign" // *Cause: The value does not support value assignment. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: OPER_BAD_ASSIGN // 00935,0, "Invalid left value to delete" // *Cause: The value does not support value deletion. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: OPER_BAD_DELETE // 00936,0, "Object required to invoke a method" // *Cause: The associated value is not an object reference or an undefined // value. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: OPER_NO_OBJECT // 00937,0, "Undefined macro" // *Cause: The macro is not defined. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: OPER_UNKNOWN_MACRO // 00938,0, "Error encountered in the macro called" // *Cause: RDA encountered an error in a macro and propagated it to the // calling context. // *Action: Report the error along with any previous errors. // *Mnemonic: OPER_MACRO_ERROR // 00939,0, "Missing right value" // *Cause: The assignment does not contain any right value. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: OPER_NO_RVALUE // // /////////////////////////////////////////////////////////////////////////// // 01000.01999 Object Errors // /////////////////////////////////////////////////////////////////////////// // 01000,0, "Unknown directory type" // *Cause: An invalid directory type was specified. // *Action: Specify a valid directory type: A, C, E, I, J, L, M, P, R, S, T, // or X. // *Mnemonic: OUT_BAD_DIRECTORY // 01001,0, "Cannot create the report directory" // *Cause: RDA failed to create the report directory. // *Action: Check the permissions and ownership of the parent directories. // *Mnemonic: OUT_ERR_RPT_CREATE // 01002,0, "Cannot create the archive directory" // *Cause: RDA failed to create the archive directory inside the report // directory. // *Action: Check the permissions and ownership of the report or parent // directories. // *Mnemonic: OUT_ERR_ARC_CREATE // 01003,0, "Cannot create the extern directory" // *Cause: RDA failed to create the extern directory inside the report // directory. // *Action: Check the permissions and ownership of the report or parent // directories. // *Mnemonic: OUT_ERR_EXT_CREATE // 01004,0, "Cannot create the remote directory" // *Cause: RDA failed to create the remote directory inside the report // directory. // *Action: Check the permissions and ownership of the report or parent // directories. // *Mnemonic: OUT_ERR_REM_CREATE // 01005,0, "Cannot create the ref directory" // *Cause: RDA failed to create the ref directory inside the report directory. // *Action: Check the permissions and ownership of the report or parent // directories. // *Mnemonic: OUT_ERR_REF_CREATE // 01006,0, "Cannot create the sample directory" // *Cause: RDA failed to create the sample directory inside the report // directory. // *Action: Check the permissions and ownership of the report or parent // directories. // *Mnemonic: OUT_ERR_SMP_CREATE // 01007,0, "Cannot create the temporary directory" // *Cause: RDA failed to create the temporary directory inside the report // directory. // *Action: Check the permissions and ownership of the report or parent // directories. // *Mnemonic: OUT_ERR_TMP_CREATE // 01008,0, "Cannot create the transfer directory" // *Cause: RDA failed to create the transfer directory inside the report // directory. // *Action: Check the permissions and ownership of the report or parent // directories. // *Mnemonic: OUT_ERR_XFR_CREATE // 01009,0, "Cannot create the multi-run collection directory" // *Cause: RDA failed to create the multi directory inside the report // directory. // *Action: Check the permissions and ownership of the report or parent // directories. // *Mnemonic: OUT_ERR_MRC_CREATE // 01010,0, "Cannot create the inline code directory" // *Cause: RDA failed to create the inline code directory inside the // report directory. // *Action: Check the permissions and ownership of the report or parent // directories. // *Mnemonic: OUT_ERR_INC_CREATE // 01011,0, "Cannot create the job directory" // *Cause: RDA failed to create the job directory inside the report directory. // *Action: Check the permissions and ownership of the report or parent // directories. // *Mnemonic: OUT_ERR_JOB_CREATE // 01012,0, "Cannot create the lock directory" // *Cause: RDA failed to create the lock directory inside the report directory. // *Action: Check the permissions and ownership of the report or parent // directories. // *Mnemonic: OUT_ERR_LCK_CREATE // 01013,0, "Cannot create the sandbox directory" // *Cause: RDA failed to create the sandbox directory inside the report // directory. // *Action: Check the permissions and ownership of the report or parent // directories. // *Mnemonic: OUT_ERR_BOX_CREATE // 01020,0, "Filter error" // *Cause: RDA received some errors when compiling the filter. // *Action: Examine other reported errors and take appropriate actions. // *Mnemonic: OUT_ERR_FILTER // 01021,0, "The report file prefix is too long" // *Cause: The length of the report file prefix is incompatible with the // file name length. // *Action: Use a shorter report file prefix. // *Mnemonic: OUT_PREFIX_LENGTH // 01022,0, "Cannot create a test file in the report directory" // *Cause: RDA cannot create the test file in the report directory. // *Action: Correct the permissions problem and execute RDA again. Alternatively, // specify another report directory by running the setup of the // initialization module again, using the following command arguments: // -S INI // *Mnemonic: OUT_TEST_CREATE // 01023,0, "Cannot remove the test file from the report directory" // *Cause: RDA cannot remove the test file from the report directory. // *Action: RDA must be able to remove temporary and report files from the // report directory. It is required for maintaining the report // consistency when running RDA multiple times. Correct the permissions // problem and execute RDA again. Alternatively, specify another // report directory by running the setup of the initialization module // again, using the following command arguments: // -S INI // *Mnemonic: OUT_TEST_UNLINK // 01024,0, "Invalid request in a multi-run collection section" // *Cause: RDA detected a request that make impossible to reject the section. // *Action: Review the logic to perform the operation elsewhere. // *Mnemonic: OUT_MRC // 01029,0, "Not enough free space for running RDA" // *Cause: The available space on the report disk is less than the minimum // specified by the RDA_FREE setting. // *Action: Free some space or relocate the report directory on another disk // with more available space. // *Mnemonic: OUT_FREE // 01030,0, "Cannot suspend the reporting control" // *Cause: RDA encountered problems when suspending the reporting control. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: OUT_BAD_SUSPEND // 01031,0, "Cannot resume the reporting control" // *Cause: RDA encountered problems when resuming the reporting control. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: OUT_BAD_RESUME // 01032,0, "Cannot load information from threads" // *Cause: RDA encountered errors when loading information from threads. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: OUT_ERR_LOAD // 01033,0, "Reports are not available in this context" // *Cause: Only local report control objects can manage reports. // *Action: Use a local report control structure to manage reports. // *Mnemonic: OUT_NO_REPORT // 01034,0, "Invalid report type" // *Cause: An invalid report file type was specified. // *Action: Specify a valid report file type: B, C, D, E, F, R, or S. // *Mnemonic: OUT_BAD_TYPE // 01035,0, "Invalid or missing name" // *Cause: The report name does not start with a letter. // *Action: Start the report name with a letter. // *Mnemonic: OUT_BAD_NAME // 01036,0, "Temporary files are not available in this context" // *Cause: Only local report control objects can manage temporary files. // *Action: Use a local report control structure to manage temporary files. // *Mnemonic: OUT_NO_TEMP // 01037,0, "Pipes are not available in this context" // *Cause: Only local report control objects can manage communication pipes. // *Action: Use a local report control structure to manage communication pipes. // *Mnemonic: OUT_NO_PIPE // 01038,0, "Missing command" // *Cause: The pipe has no associated command. // *Action: Provide a command for each pipe. // *Mnemonic: OUT_NO_COMMAND // 01039,0, "Work files are not available in this context" // *Cause: Only local report control objects can manage work files. // *Action: Use a local report control structure to manage work files. // *Mnemonic: OUT_NO_WORK // 01050,0, "Invalid report file type" // *Cause: An invalid report file type was specified. // *Action: Specify a valid report file type: B, C, D, E, F, R, or S. // *Mnemonic: RPT_BAD_TYPE // 01051,0, "Cannot open or create the report file" // *Cause: RDA cannot open or create the report file. // *Action: Correct the permissions problem and execute RDA again. // *Mnemonic: RPT_RPT_ERROR // 01052,0, "Cannot open or create the data file" // *Cause: RDA cannot open or create the data file. // *Action: Correct the permissions problem and execute RDA again. // *Mnemonic: RPT_DAT_ERROR // 01053,0, "Cannot open or create the extern file" // *Cause: RDA cannot open or create the extern file. // *Action: Correct the permissions problem and execute RDA again. // *Mnemonic: RPT_EXT_ERROR // 01054,0, "Cannot open or create the reference file" // *Cause: RDA cannot open or create the reference file. // *Action: Correct the permissions problem and execute RDA again. // *Mnemonic: RPT_REF_ERROR // 01055,0, "Cannot open or create the sample file" // *Cause: RDA cannot open or create the sample file. // *Action: Correct the permissions problem and execute RDA again. // *Mnemonic: RPT_SMP_ERROR // 01056,0, "Cannot open or create the temporary file" // *Cause: RDA cannot open or create the temporary file. // *Action: Correct the permissions problem and execute RDA again. // *Mnemonic: RPT_TMP_ERROR // 01060,0, "Prefix error" // *Cause: RDA encountered an error when executing the prefix block. // *Action: Check for any other errors reported and take appropriate actions. // *Mnemonic: RPT_PREFIX // 01061,0, "Cannot clone an active report" // *Cause: A thread cannot have multiple control objects allowing writes on a // same report. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: RPT_CLONE_ACTIVE // 01062,0, "Cannot clone a report before its creation" // *Cause: The report must exist before any report cloning. // *Action: Create the report explicitly before launching the thread. // *Mnemonic: RPT_CLONE_NEW // 01063,0, "Locked report" // *Cause: It is not possible to write to a locked report. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: RPT_LOCKED // 01064,0, "Report already ended" // *Cause: It is not possible to write to an ended report. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: RPT_ENDED // 01065,0, "Missing catalog" // *Cause: The corresponding argument is missing. // *Action: Verify the catalog type. Supported type is: E (for Explorer). // *Mnemonic: NO_CATALOG // 01066,0, "Invalid catalog" // *Cause: The corresponding argument is invalid. // *Action: Verify the catalog type. Supported type is: E (for Explorer). // *Mnemonic: BAD_CATALOG // 01067,0, "Missing or invalid Explorer type" // *Cause: The corresponding argument is missing or invalid. // *Action: Verify the Explorer type. Valid types are: B, D, E, O, or T. // *Mnemonic: XPLR_TYPE // 01068,0, "Missing or invalid Explorer name" // *Cause: The argument is missing or contains invalid characters. // *Action: Verify the Explorer name. It can contain a directory part. The name // should contain alplanumeric characters, +, -, =, @, dots, or // underscores only. // *Mnemonic: XPLR_NAME // 01070,0, "Cannot create the table of content file" // *Cause: RDA cannot open or create the table of content file. // *Action: Correct the permissions problem and execute RDA again. // *Mnemonic: TOC_ERR_CREATE // 01071,0, "Invalid table of content name" // *Cause: The name contains invalid characters. // *Action: Verify the name. It should contain alphanumeric characters only. // *Mnemonic: TOC_BAD_OID // 01080,0, "Cannot create the communication pipe" // *Cause: RDA cannot create the communication pipe. // *Action: Verify the output command. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: PIPE_ERR_CREATE // 01081,0, "Pipe already closed" // *Cause: It is no longer possible to write to a communication pipe after its // closure. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: PIPE_CLOSED // 01082,0, "Prefix error" // *Cause: RDA encountered an error when executing the prefix block. // *Action: Check for any other reported errors and take appropriate actions. // *Mnemonic: PIPE_PREFIX // 01083,0, "Locked pipe" // *Cause: Only a single thread can write to a communication pipe. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: PIPE_LOCKED // 01100,0, "Missing or invalid buffer type" // *Cause: The buffer type is not 'B', 'F', 'H', 'L', 'R', 'S', or 'T'. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: BUFFER_BAD_TYPE // 01101,0, "Offset outside string" // *Cause: The new offset points outside the string. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: BUF_BAD_OFFSET // 01102,0, "getlines() called in a scalar context" // *Cause: getlines() requires a list context. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: BUF_GETLINES // 01103,0, "Bad whence" // *Cause: The seek request contains an invalid offset type. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: BUF_BAD_WHENCE // 01110,0, "Invalid source table" // *Cause: The source object is not a table. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: TABLE_BAD_SOURCE // 01111,0, "Missing offset" // *Cause: Identifying a column requires an offset. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: TABLE_NO_OFFSET // 01112,0, "Invalid offset" // *Cause: The offset is incompatible with the number of columns. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: TABLE_BAD_OFFSET // 01113,0, "Unknown column" // *Cause: The specified name does not correspond to any column. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: TABLE_BAD_COLUMN // 01120,0, "ERR_CREATE" // *Cause: RDA cannot create the lock file. // *Action: Check the permissions of the lock directory specified by the // RDA_LOCK environment variable. When the environment variable is // not defined, check the permissions of the directory that contains // the setup file. // *Mnemonic: LOCK_CREATE_ERROR // 01130,0, "Cannot resolve" // *Cause: RDA cannot resolve the HTTP server name. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: HTTP_RESOLVE // 01131,0, "Socket error" // *Cause: RDA encountered a socket error. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: HTTP_SOCKET_ERROR // 01132,0, "Connect error" // *Cause: RDA encountered a connect error. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: HTTP_CONNECT_ERROR // 01133,0, "Connect timeout" // *Cause: RDA encountered a connect timeout. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: HTTP_CONNECT_TIMEOUT // 01134,0, "Request error" // *Cause: RDA encountered a request error. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: HTTP_REQ_ERROR // 01135,0, "Request timeout" // *Cause: RDA encountered a request timeout. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: HTTP_REQ_TIMEOUT // 01136,0, "Request content error" // *Cause: RDA encountered a content error. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: HTTP_CONTENT_ERROR // 01137,0, "Request content timeout" // *Cause: RDA encountered a content timeout. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: HTTP_CONTENT_TIMEOUT // 01138,0, "Response select error" // *Cause: RDA encountered a select error. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: HTTP_SEL_ERROR // 01139,0, "Response read error" // *Cause: RDA encountered a read error. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: HTTP_RSP_ERROR // 01140,0, "Response timeout" // *Cause: RDA encountered a response timeout. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: HTTP_RSP_TIMEOUT // 01141,0, "Close error" // *Cause: RDA encountered a close error. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: HTTP_CLOSE // 01142,0, "Missing location" // *Cause: RDA did not find a location in a redirection request. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: HTTP_NO_LOCATION // 01143,0, "Invalid type" // *Cause: RDA supports GET and POST requests only. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: HTTP_BAD_TYPE // 01144,0, "Unsupported url" // *Cause: The URL format is invalid or not supported. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: HTTP_BAD_URL // 01150,0, "Cannot resolve" // *Cause: RDA cannot resolve the FTP server name. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: FTP_RESOLVE // 01151,0, "Socket error" // *Cause: RDA encountered a socket error. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: FTP_SOCKET_ERROR // 01152,0, "Bind error" // *Cause: RDA encountered a bind error. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: FTP_BIND // 01153,0, "Connect error" // *Cause: RDA encountered a connect error. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: FTP_CONNECT_ERROR // 01154,0, "Connect timeout" // *Cause: RDA encountered a connect timeout. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: FTP_CONNECT_TIMEOUT // 01155,0, "Start error" // *Cause: RDA encountered a start error. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: FTP_START_ERROR // 01156,0, "Request error" // *Cause: RDA encountered a request error. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: FTP_REQUEST_ERROR // 01157,0, "Request timeout" // *Cause: RDA encountered a request timeout. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: FTP_REQUEST_ERROR // 01158,0, "Send error" // *Cause: RDA encountered a send error. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: FTP_SEND_ERROR // 01159,0, "Send timeout" // *Cause: RDA encountered a send timeout. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: FTP_SEND_TIMEOUT // 01160,0, "Response timeout" // *Cause: RDA encountered a response timeout. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: FTP_RESPONSE_TIMEOUT // 01161,0, "Listen error" // *Cause: RDA encountered a listen error. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: FTP_LISTEN_ERROR // 01162,0, "Listen timeout" // *Cause: RDA encountered a listen timeout. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: FTP_LISTEN_TIMEOUT // 01163,0, "Receive error" // *Cause: RDA encountered a receive timeout. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: FTP_RECEIVE_ERROR // 01164,0, "Receive timeout" // *Cause: RDA encountered a recieve timeout. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: FTP_RECEIVE_TIMEOUT // 01169,0, "Missing command" // *Cause: The FTP request requires a command. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: FTP_NO_COMMAND // 01170,0, "Missing directory" // *Cause: The command requires a directory. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: FTP_NO_DIRECTORY // 01171,0, "Missing file" // *Cause: The command requires a file. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: FTP_NO_FILE // 01172,0, "Missing or invalid local file" // *Cause: The command requires a valid local file. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: FTP_NO_LOCAL // 01173,0, "Missing remote file" // *Cause: The command requires a remote file. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: FTP_NO_REMOTE // 01174,0, "Missing rename source" // *Cause: The rename command requires a source name. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: FTP_RENAME_SOURCE // 01175,0, "Missing rename destination" // *Cause: The rename command requires a destination name. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: FTP_RENAME_DEST // 01176,0, "Cannot open local file" // *Cause: Encountered an error when opening the local file. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: FTP_OPEN // 01177,0, "Cannot binmode local file" // *Cause: RDA encountered an error when forcing the binary mode. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: FTP_BINMODE // 01178,0, "Cannot write to local file" // *Cause: RDA encountered an error when writing to the local file. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: FTP_WRITE // 01179,0, "Cannot close local file" // *Cause: RDA encountered an error when closing the local file. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: FTP_CLOSE // 01180,0, "Error in reader compilation" // *Cause: RDA encountered an error when compiling the code to read input // lines. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: PARSE_READ // 01181,0, "Error in parser compilation" // *Cause: RDA encountered an error when compiling the parsing code. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: PARSE_PREPARE // 01182,0, "Parsing error" // *Cause: RDA encountered an error when parsing input lines. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: PARSE_ANALYZE // 01190,0, "Cannot access environment variables" // *Cause: PERL_ENV_TABLES is not set correctly. When perl "-V" is executed, it // also produces an error: %RMS-F-SYN, file specification syntax error. // *Action: Check that PERL_ENV_TABLES has CRTL_ENV as the first element // in its value list and that all elements are valid. // *Mnemonic: ENV_ERR_COPY // 01191,0, "Read-only copy of the environment variables" // *Cause: This copy of the environment variables is protected against changes. // *Action: Clone the object and use the resulting object. // *Mnemonic: ENV_NO_CHANGE // 01200,0, "Cannot change to the work directory" // *Cause: RDA encountered an error when changing to the work directory. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: RDA_ERR_CD // 01201,0, "Cannot create the directory" // *Cause: RDA failed to create the directory. // *Action: Check the permissions and ownership of the parent directories. // *Mnemonic: RDA_ERR_CREATE // 01202,0, "Invalid directory group" // *Cause: An invalid directory group has been used. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: RDA_BAD_GROUP // 01203,0, "Cannot determine the RDA engine code build" // *Cause: RDA failed to determine the RDA engine code build. // *Action: Install the latest version for RDA and all compiled engines present. // *Mnemonic: RDA_NO_BUILD // 01204,0, "Expecting the RDA build or later" // *Cause: The RDA engine code is older than the module code. // *Action: Install the latest version for RDA and all compiled engines present. // *Mnemonic: RDA_BAD_BUILD // 01210,0, "Cannot open pager" // *Cause: RDA failed to open the pager. // *Action: Check the setting of the PAGER environment variable. // *Mnemonic: DSP_PAGER_FAIL // 01211,0, "Package '' not available" // *Cause: RDA cannnot load the specified package. // *Action: The next line provides more information about this error. Take // appropriate actions to fix it. // *Mnemonic: DSP_BAD_PACKAGE // 01220,0, "Unknown group" // *Cause: RDA did not find the definition of the group. // *Action: The next line provides more information about this error. Take // appropriate actions to fix it. // *Mnemonic: CNV_BAD_GROUP // 01221,0, "Cannot open the report" // *Cause: RDA cannot open the file to convert. // *Action: The next line provides more information about this error. Take // appropriate actions to fix it. // *Mnemonic: CNV_OPEN_RPT // 01222,0, "Cannot open the group definition file" // *Cause: RDA cannot open the group definition file. // *Action: The next line provides more information about this error. Take // appropriate actions to fix it. // *Mnemonic: CNV_OPEN_DEF // 01223,0, "Cannot create the result file" // *Cause: RDA cannot create the result file. // *Action: The next line provides more information about this error. Take // appropriate actions to fix it. // *Mnemonic: CNV_CREATE // 01224,0, "Bad abbreviation" // *Cause: The abbreviation contains invalid characters. // *Action: Verify the abbreviation. It should contain alphanumeric characters // only. // *Mnemonic: CNV_BAD_ABBR // 01225,0, "Bad line" // *Cause: RDA encountered a line with an unknown syntax. // *Action: Review the specification syntax and fix it. // *Mnemonic: CNV_BAD_LINE // 01226,0, "Bad pattern" // *Cause: RDA encountered an invalid pattern. // *Action: A pattern must start with a plus (+) or minus (-) sign. // *Mnemonic: CNV_BAD_PATTERN // 01227,0, "Bad value" // *Cause: RDA found extra characters at the end of the specification. // *Action: Review the specification syntax and fix it. // *Mnemonic: CNV_BAD_VALUE // 01228,0, "Missing group specification" // *Cause: RDA found group details before the first group definition. // *Action: Review the line sequence and fix it. // *Mnemonic: CNV_DEF_GROUP // 01229,0, "Error(s) in group definition file" // *Cause: RDA encountered errors when parsing the conversion group definitions. // *Action: Fix previous errors. // *Mnemonic: CNV_DEF_ERROR // 01230,0, "Conversion error" // *Cause: RDA encountered an error in the plugin execution. // *Action: The next line provides more information about this error. Take // appropriate actions to fix it. // *Mnemonic: CNV_CONV_ERROR // 01231,0, "Error encountered when loading the plugin" // *Cause: RDA encountered an error when loading the plugin. // *Action: The next line provides more information about this error. Take // appropriate actions to fix it. // *Mnemonic: CNV_LOAD_ERROR // 01232,0, "Plugin definition error" // *Cause: The package does not contain a plugin definition hash. // *Action: The next line provides more information about this error. Take // appropriate actions to fix it. // *Mnemonic: CNV_NO_DEF // 01233,0, "Search error" // *Cause: RDA encountered an error when executing a selection function. // *Action: The next line provides more information about this error. Take // appropriate actions to fix it. // *Mnemonic: CNV_BAD_SEARCH // 01234,0, "Cannot extract the report" // *Cause: RDA cannot extract the report from the archive. // *Action: Check the archive integrity and the compression method. RDA // supports deflated and stored methods only. // *Mnemonic: CNV_EXT_ERROR // 01250,0, "No RDA catalog found" // *Cause: RDA did not find any catalog file. // *Action: Verify that RDA knows the location and the report group of the // collected files and that RDA has collected files for the specified // modules. // *Mnemonic: TOOL_NO_CATALOG // 01251,0, "Partial file" // *Cause: RDA collected a file fragment only. // *Action: Determine the impact of fragmental information and take appropriate // actions. // *Mnemonic: TOOL_FIL_PARTIAL // 01252,0, "Missing file" // *Cause: RDA cannot find the requested file in its catalog. // *Action: Review which files are available using the 'find' option. // *Mnemonic: TOOL_FIL_MISSING // 01260,0, "Cannot open the file, containing the report block" // *Cause: RDA cannot open the report file. // *Action: Verify the permissions of the reference file and take appropriate // actions. // *Mnemonic: BLOCK_FILE_OPEN // 01261,0, "Cannot find the report block in the file" // *Cause: RDA cannot find the report block on in the file. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: BLOCK_FILE_SEEK // 01262,0, "getlines() called in a scalar context." // *Cause: RDA called the getlines procedure in scalar context. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: BLOCK_FILE_LINES // 01270,0, "Missing file or directory" // *Cause: RDA did not find the specified file or directory in the file catalog. // *Action: Verify its path and that the right collections have been performed. // *Mnemonic: IDX_ITM_MISSING // 01271,0, "Cannot create extract file" // *Cause: RDA cannot write the extracted file in the target directory. // *Action: Verify the permissions in the target directory and retry the // extraction operation. // *Mnemonic: IDX_EXTRACT_ERR // 01272,0, "Missing or invalid directory" // *Cause: RDA cannot find the specified directory in the file catalog. // *Action: Verify the directory path and that the right collections have been // performed. // *Mnemonic: IDX_DIR_MISSING // 01273,0, "Missing file" // *Cause: RDA cannot find a file in the file catalog. // *Action: Verify the file path and that the right collections have been // performed. // *Mnemonic: IDX_FIL_MISSING // 01274,0, "Invalid path" // *Cause: RDA found an another object than a directory. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: IDX_BAD_DIR // 01280,0, "Cannot open the group definition file // *Cause: RDA cannot open the group definition file. // *Action: Verify that the current user has permissions to access and to open // the group definition file. // *Mnemonic: MRC_OPEN_FAIL // 01281,0, "Invalid group specification value" // *Cause: RDA found an invalid value. // *Action: Invalid characters are found in the specification value or // extra characters are found after the value. RDA allows comments only // after a value. Remove the offending characters. // *Mnemonic: MRC_BAD_VALUE // 01282,0, "Invalid group module list" // *Cause: RDA found an invalid module list. // *Action: Invalid characters were found in the module list or extra // characters were found after the list. RDA allows comments only // after a list. Remove the offending characters. // *Mnemonic: MRC_BAD_LIST // 01283,0, "Unexpected group specification" // *Cause: RDA found an invalid group specification. // *Action: The corresponding line does not correspond to valid syntax. // Correct the invalid syntax. // *Mnemonic: MRC_BAD_SPEC // 01284,0, "Error(s) in group definition file" // *Cause: RDA detected errors when loading the group specifications. // *Action: Check the previous messages related to all errors found. // *Mnemonic: MRC_LOAD_ERROR // 01285,0, "Invalid group name" // *Cause: RDA cannot find the specified group. // *Action: Check the list of defined groups. // *Mnemonic: MRC_BAD_GROUP // 01286,0, "Invalid set name" // *Cause: RDA cannot find the specified set. // *Action: Check the list of defined sets. // *Mnemonic: MRC_BAD_SET // 01290,0, "Context change inside a collection" // *Cause: RDA detected the declaration of the multi-run collection context // inside a multi-run collection. // *Action: Review the collection logic and take corrective actions. // *Mnemonic: MRC_BEGIN_CONTEXT // 01291,0, "Missing module declaration" // *Cause: RDA cannot determine the module involved in the multi-run // collection. // *Action: Declare the multi-run collection context before executing the // collect command. // *Mnemonic: MRC_BEGIN_MODULE // 01292,0, "Invalid or missing name" // *Cause: RDA detected an invalid or missing name. // *Action: Make sure that all submodule names in a collect command contain // alphanumeric and pipe characters only. // *Mnemonic: MRC_COLLECT_NAME // 01293,0, "Invalid collect nesting" // *Cause: RDA encountered a collect command inside a multi-run collection // section. // *Action: For nesting multi-run collection, use a control section for // executing a collect command. // *Mnemonic: MRC_COLLECT_NESTING // 01294,0, "Error encountered in the block called" // *Cause: RDA detected an error when executing a multi-run collection module. // *Action: Report the error and the previous errors. // *Mnemonic: MRC_COLLECT_ERROR // 01295,0, "Not in a multi-run collection section" // *Cause: RDA encountered a validate command outside a multi-run collection // section. // *Action: Review the collection logic and take corrective actions. // *Mnemonic: MRC_VALIDATE_ERROR // 01300,0, "getlines() called in a scalar context" // *Cause: getlines() requires a list context. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: AREA_GETLINES // 01301,0, "Bad whence" // *Cause: The seek request contains an invalid offset type. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: AREA_BAD_WHENCE // 01310,0, "getlines() called in a scalar context" // *Cause: getlines() requires a list context. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: DEFLATE_GETLINES // 01311,0, "Bad whence" // *Cause: The seek request contains an invalid offset type. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: DEFLATE_BAD_WHENCE // 01350,0, "Missing target name" // *Cause: No object identifier specified at target creation // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: NO_TGT_NAME // 01351,0, "Invalid object name" // *Cause: The target identifier can contain alphanumeric characters and // underscores only. It must start with the target type. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: BAD_TGT_NAME // 01352,0, "Missing target definition" // *Cause: No definition specified at target creation // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: NO_TGT_DEFINITION // 01353,0, "Invalid target class" // *Cause: RDA encountered errors when loading the corresponding target class. // *Action: The next line provides more information about this error. Take // appropriate actions to fix it. // *Mnemonic: BAD_TGT_CLASS // 01354,0, "Missing or invalid identifier" // *Cause: The target identifier can contain alphanumeric characters and // underscores only. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: BAD_BAD_FOCUS // 01355,0, "Focus not support for the target" // *Cause: Focus definition attempted on a target that does not support focus // management // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: BAD_NO_FOCUS // 01360,0, "Missing Oracle home directory" // *Cause: No Oracle home directory specified when creating an Oracle home // target // *Action: Specify the Oracle home directory in the target definition or as // attribute. // *Mnemonic: NO_OH_DIR // 01361,0, "Invalid object identifier" // *Cause: The home target identifier can contain alphanumeric characters and // underscores only. It must start with CH or OH as type. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: BAD_HOME_NAME // 01370,0, "Missing WebLogic Server home directory" // *Cause: No Oracle home directory specified when creating an Oracle home // target // *Action: Specify the Oracle home directory in the target definition or as // attribute. // *Mnemonic: NO_WH_DIR // 01380,0, "Missing domain home directory" // *Cause: No domain home directory specified when creating an Oracle WebLogic // Server domain target // *Action: Specify the Oracle WebLogic Server domain home directory in the // target definition or as attribute. // *Mnemonic: NO_DOM_DIR // 01381,0, "Missing or invalid identifier" // *Cause: The target identifier can contain alphanumeric characters and // underscores only. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: BAD_BAD_SERVER // 01400,0, "Cannot set cache version" // *Cause: RDA cannot save the cache version. // *Action: The next line provides more information about this error. Take // appropriate actions to fix it. // *Mnemonic: LNG_CACHE_ERR // 01401,0, "Cannot load language" // *Cause: RDA cannot load the language-specific package. // *Action: The next line provides more information about this error. Take // appropriate actions to fix it. // *Mnemonic: LNG_LOAD_ERR // 01402,0, "Unsupported language" // *Cause: The language package does not provide an initialisation method. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: LNG_LANG_ERR // 01403,0, "Missing or invalid language" // *Cause: No valid language provided when calling the method. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: LNG_BAD_LANG // 01410,0, "Invalid named block" // *Cause: RDA detects a new attempt to execute a named block that previously // encountered an error. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: LNG_BAD_BLOCK // 01411,0, "Unregistred named block" // *Cause: RDA detects an attempt to execute a name block before its // registration. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: LNG_BAD_NAME // 01412,0, "Duplicate named block name" // *Cause: The specified name is already used. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: LNG_DUP_NAME // 01420,0, "Missing public class definition" // *Cause: The Java code does not contain the public class definition. // *Action: Review the code and take appropriate actions to fix it. // *Mnemonic: JAVA_NO_CLASS // 01421,0, "Missing main method definition" // *Cause: Java code does not contain a static main method. // *Action: Review the code and take appropriate actions to fix it. // *Mnemonic: JAVA_NO_MAIN // 01422,0, "Copy error" // *Cause: RDA encountered an error when copying the class file. // *Action: The next line provides more information about this error. Take // appropriate actions to fix it. // *Mnemonic: JAVA_COPY_ERR // 01423,0, "Missing Java compiler" // *Cause: RDA did not find any Java compiler. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: JAVA_NO_JAVAC // 01424,0, "Error encountered when compiling Java block" // *Cause: RDA encountered an error when compiling a Java block. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: JAVA_COMP_ERR // 01425,0, "Missing Java configuration" // *Cause: RDA did not find any Java execution environment. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: JAVA_NO_JAVA // 01426,0, "Error encountered when executing Java block" // *Cause: RDA encountered an error when executing a Java block. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: JAVA_EXEC_ERR // 01427,0, "Missing public interface definition" // *Cause: The Java code does not contain the public interface definition. // *Action: Review the code and take appropriate actions to fix it. // *Mnemonic: JAVA_NO_INTERFACE // 01428,0, "Main block required" // *Cause: A sub block has been used instead of the main block. // *Action: Review the code and take appropriate actions to fix it. // *Mnemonic: JAVA_NOT_MAIN // 01430,0, "Not connected" // *Cause: The operation requires an open connection. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: TELNET_NO_OPEN // 01431,0, "Cannot create log file" // *Cause: RDA cannot create the log file. // *Action: The next line provides more information about this error. Take // appropriate actions to fix it. // *Mnemonic: TELNET_LOG_ERR // 01432,0, "Unknown remote host" // *Cause: RDA cannot resolve the host name. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: TELNET_BAD_HOST // 01433,0, "Cannot create socket" // *Cause: RDA cannot create the socket. // *Action: The next line provides more information about this error. Take // appropriate actions to fix it. // *Mnemonic: TELNET_SOCKET_ERR // 01434,0, "Cannot connect to host" // *Cause: RDA encountered an error when connecting to the host. // *Action: The next line provides more information about this error. Take // appropriate actions to fix it. // *Mnemonic: TELNET_NO_CONNECT // 01435,0, "Timeout in host name lookup" // *Cause: RDA encountered a timeout when resolving the host name. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: TELNET_LOOKUP_TIMEOUT // 01436,0, "Timeout in connection to host" // *Cause: RDA encountered a timeout when connecting to the host. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: TELNET_CONNECT_TIMEOUT // 01440,0, "Invalid error mode" // *Cause: RDA detected an invalid mode as error mode. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: TELNET_BAD_ERR // 01441,0, "Invalid reference specified as error mode" // *Cause: RDA detected an invalid reference as error mode. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: TELNET_BAD_REF // 01442,0, "Invalid skip mode" // *Cause: RDA detected an invalid reference as skip mode. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: TELNET_BAD_SKIP // 01443,0, "Invalid TCP service" // *Cause: RDA detected an unknown TCP service. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: TELNET_BAD_TCP // 01444,0, "Invalid telnet option" // *Cause: RDA detected an invalid value as telnet option. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: TELNET_BAD_OPTION // 01445,0, "Invalid timeout value" // *Cause: RDA detected an invalid value as timeout value. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: TELNET_BAD_TIMEOUT // 01446,0, "Null input record separator" // *Cause: RDA detected a null string as input record separator. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: TELNET_BAD_IRS // 01450,0, "Missing command" // *Cause: RDA did not find any command to execute. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: TELNET_NO_COMMAND // 01451,0, "Command timeout" // *Cause: RDA encountered a timeout when reading the command results. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: TELNET_COMMAND_TIMEOUT // 01452,0, "Missing option callback function" // *Cause: RDA did not find any callback function to handle the telnet options. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: TELNET_NO_CALLBACK // 01453,0, "Invalid option action" // *Cause: RDA received an invalid action for the telnet options. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: TELNET_BAD_ACTION // 01454,0, "Invalid option request" // *Cause: RDA received an invalid request during telnet option negotiation. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: TELNET_BAD_ACTION // 01455,0, "Missing user name" // *Cause: RDA did not find any user name in the request. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: TELNET_NO_USER // 01456,0, "Missing user password" // *Cause: RDA did not find any user password in the request. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: TELNET_NO_PASSWORD // 01457,0, "Invalid user and password combination" // *Cause: The remote host does not accept the user name and password // combination. // *Action: Provide a valid user and paswword combination. // *Mnemonic: TELNET_BAD_LOGIN // 01458,0, "Invalid device" // *Cause: The banner text does not match the check pattern. // *Action: Check the host connection and take appropriate actions. // *Mnemonic: TELNET_BAD_DEVICE // 01460,0, "Expecting a match as prompt" // *Cause: RDA expects a match operation as prompt pattern. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: TELNET_BAD_PROMPT // 01461,0, "Error when compiling pattern" // *Cause: RDA encountered an error when compiling the prompt pattern. // *Action: The next line provides more information about this error. Take // appropriate actions to fix it. // *Mnemonic: TELNET_CODE_ERR // 01462,0, "Warnings when compiling pattern" // *Cause: RDA got warnings when compiling the prompt pattern. // *Action: The next line provides more information about this error. Take // appropriate actions to fix it. // *Mnemonic: TELNET_CODE_WARN // 01463,0, "Expecting a match operation" // *Cause: RDA expects a match operation to identify an expected event. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: TELNET_NO_MATCH // 01464,0, "Timeout in pattern match" // *Cause: RDA encountered a timeout while waiting for events. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: TELNET_PATTERN_TIMEOUT // 01465,0, "EOF in pattern match" // *Cause: RDA encountered an end of file while waiting for events. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: TELNET_PATTERN_ERR // 01470,0, "Maximum reception buffer length exceeded" // *Cause: The reception buffer is full. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: TELNET_BUFFER_FULL // 01471,0, "Fill timeout" // *Cause: RDA encountered a timeout while filling its reception buffer. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: TELNET_FILL_TIMEOUT // 01472,0, "Select error" // *Cause: RDA encountered an error while waiting for input. // *Action: The next line provides more information about this error. Take // appropriate actions to fix it. // *Mnemonic: TELNET_SELECT_TIMEOUT // 01473,0, "Select timeout" // *Cause: RDA encountered a timeout while waiting for input. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: TELNET_SELECT_ERR // 01474,0, "Read error" // *Cause: RDA encountered an error while reading some input. // *Action: The next line provides more information about this error. Take // appropriate actions to fix it. // *Mnemonic: TELNET_READ_ERR // 01475,0, "Request timed-out" // *Cause: RDA encountered a timeout while sending some data. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: TELNET_TIMEOUT // 01476,0, "Write error" // *Cause: RDA encountered an error while sending some data. // *Action: The next line provides more information about this error. Take // appropriate actions to fix it. // *Mnemonic: TELNET_WRITE_ERR // 01477,0, "Zero length write" // *Cause: A write operation completed without any data effectively sent. // *Action: The next line provides more information about this error. Take // appropriate actions to fix it. // *Mnemonic: TELNET_NULL_WRITE // 01500,0, "Requires a session manager object" // *Cause: The method is supported on session manager object only. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: REMOTE_NOT_MANAGER // 01501,0, "Requires a session object" // *Cause: The method is supported on session object only. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: REMOTE_NOT_REMOTE // 01502,0, "Requires a remote session object" // *Cause: The method is supported on remote session object only. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: REMOTE_NOT_SESSION // 01503,0, "Missing session identifier" // *Cause: RDA cannot create a session without an identifier. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: REMOTE_NO_ID // 01504,0, "Invalid session identifier" // *Cause: RDA encountered invalid characters in the session identifier. // *Action: A session identifier must start with a letter, possibly followed by // alphanumeric characters. // *Mnemonic: REMOTE_BAD_ID // 01505,0, "Missing session type" // *Cause: The method requires a session type. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: REMOTE_NO_TYPE // 01506,0, "Invalid session type" // *Cause: RDA does not know the specified sesssion type. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: REMOTE_BAD_TYPE // 01507,0, "Missing user name" // *Cause: A login request requires an user name. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: REMOTE_NO_USER // 01510,0, "Package '' not available" // *Cause: RDA cannnot load the specified package. // *Action: The next line provides more information about this error. Take // appropriate actions to fix it. // *Mnemonic: REMOTE_BAD_PACKAGE // 01511,0, "Cannot manage local sessions" // *Cause: RDA did find any possible remote access mechanism. // *Action: Run the ssh test module and take appropriate actions. // *Mnemonic: REMOTE_CANNOT_ANY // 01512,0, "Cannot manage sessions" // *Cause: RDA cannot used the specified mechanism in the current context. // *Action: Run the ssh test module and take appropriate actions. // *Mnemonic: REMOTE_CANNOT_TYPE // 01513,0, "Expecting a match as prompt" // *Cause: Prompt keys require a match operator as value. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: REMOTE_NO_PATTERN // 01514,0, "Error when compiling pattern" // *Cause: The pattern generates compilation errors. // *Action: The next line provides more information about this error. Take // appropriate actions to fix it. // *Mnemonic: REMOTE_ERR_PATTERN // 01515,0, "Warnings when compiling pattern" // *Cause: The pattern generates compilation warnings. // *Action: The next line provides more information about this error. Take // appropriate actions to fix it. // *Mnemonic: REMOTE_WARN_PATTERN // 01516,0, "Invalid skip mode" // *Cause: RDA encountered an unknown skip mode in the collect request // *Action: Provide a positive integer number as value. // *Mnemonic: REMOTE_BAD_SKIP // 01517,0, "Invalid timeout" // *Cause: RDA encountered an unknown timeout value in the collect request. // *Action: Provide an integer number as value. // *Mnemonic: REMOTE_BAD_TIMEOUT // 01520,0, "Cannot perform remote sessions" // *Cause: RDA did not find any acceptable mechanism for performing remote // requests. // *Action: Run the ssh test module and take appropriate actions. // *Mnemonic: REMOTE_ERR_EXEC // 01521,0, "Cannot open result file" // *Cause: RDA cannot open the result file. // *Action: The next line provides more information about this error. Take // appropriate actions to fix it. // *Mnemonic: REMOTE_ERR_OPEN // // /////////////////////////////////////////////////////////////////////////// // 08000.08099 Archive Errors // /////////////////////////////////////////////////////////////////////////// // 08000,0, "Cannot create archive" // *Cause: RDA cannot create the archive file. // *Action: The next line provides more information about this error. Take // appropriate actions to fix it. // *Mnemonic: ARC_CREATE_ERROR // 08001,0, "Not open for output" // *Cause: No open archive file // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: ARC_OPEN_ERROR // 08002,0, "Cannot write archive" // *Cause: RDA encoutered an error while write in the archive file. // *Action: The next line provides more information about this error. Take // appropriate actions to fix it. // *Mnemonic: ARC_WRITE_ERROR // 08003,0, "Cannot initialize the data deflation" // *Cause: Compress::Zlib reported an error at deflation initialization. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: ARC_INIT_ERROR // 08004,0, "Cannot deflate data" // *Cause: Compress::Zlib reported an error when deflating data. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: ARC_DEFLATE_ERROR // 08005,0, "Cannot flush deflated data" // *Cause: Compress::Zlib reported an error when flushing data. // *Action: Report the error and provide contextual information to reproduce // the problem. // *Mnemonic: ARC_FLUSH_ERROR // // /////////////////////////////////////////////////////////////////////////// // 08100.08199 Diaglet Errors // /////////////////////////////////////////////////////////////////////////// // 08100,0, "No such rulesets" // *Cause: RDA did not found any ruleset matching the selection criteria. // *Action: Verify that rulesets are present in the specified or default // directory. When present, review your selection criteria. // *Mnemonic: DIAG_NO_SETS // 08101,0, "Missing or invalid diaglet" // *Cause: The specified ruleset does not exists or is invalid. // *Action: Make sure that a ruleset file exists at the specified location and // that it starts with an sdp_diaglet element. // *Mnemonic: DIAG_NO_DIAGLET // 08102,0, "Diaglet XML parsing error(s)" // *Cause: The XML format of the ruleset is not correct. // *Action: Correct the XML format of the ruleset. // *Mnemonic: DIAG_ERR_XML // 08103,0, "Missing set attribute" // *Cause: The sdp_diaglet element has no set attribute. // *Action: Add a set attribute to the sdp_diaglet element. // *Mnemonic: DIAG_NO_SET // 08104,0, "Missing title attribute" // *Cause: The sdp_diaglet element has no title attribute. // *Action: Add a title attribute to the sdp_diaglet element. // *Mnemonic: DIAG_NO_TITLE // 08105,0, "Missing type attribute" // *Cause: The sdp_diaglet element has no type attribute. // *Action: Add a type attribute to the sdp_diaglet element. // *Mnemonic: DIAG_NO_TYPE // 08106,0, "Missing content block" // *Cause: RDA did not find any sdp_content element as child of the sdp_diaglet // element. // *Action: Make sure that the sdp_diaglet element has at least one sdp_content // child element. // *Mnemonic: DIAG_NO_CONTENT // 08107,0, "Missing or invalid type in content block" // *Cause: The type of the content block is not check or eval. // *Action: Make sure that the sdp_content element has check or eval as type // attribute value. // *Mnemonic: DIAG_BAD_CONTENT // 08108,0, "Invalid opt-out identifier" // *Cause: The opt-out identifier contains invalid characters. // *Action: Make sure that the opt identifier is composed of one or more // alphanumeric characters or underscores. // *Mnemonic: DIAG_OPTOUT_ID // 08110,0, "Missing group" // *Cause: RDA did not find any sdp_group element as child in an sdp_content // element of type check. // *Action: Make sure that all sdp_content elements of type check have at least // one sdp_group child element. // *Mnemonic: DIAG_NO_GROUP // 08111,0, "Missing rule in group" // *Cause: RDA did not find any sdp_rule element as child in an sdp_group // element. // *Action: Make sure that all sdp_group elements have at least one sdp_rule // child element. // *Mnemonic: DIAG_BAD_GROUP // 08120,0, "Missing identifier in fact" // *Cause: The corresponding sdp_fact element has no id attribute. // *Action: Add an id attribute to the sdp_fact element. // *Mnemonic: DIAG_BAD_FACT // 08121,0, "Duplicate fact identifier" // *Cause: The specified identifier is present in multiple sdp_fact elements. // *Action: Make the fact identifiers unique. // *Mnemonic: DIAG_DUP_FACT // 08122,0, "Fact : Command errors" // *Cause: RDA detected errors in the code contained in the sdp_command // elements. // *Action: Fix the code errors. // *Mnemonic: DIAG_FACT_ERRORS // 08123,0, "Fact : Invalid command type" // *Cause: The corresponding sdp_command element has no valid type attribute. // *Action: Make sure that the sdp_command element contains a mode attribute // with ATTACH, OS, PERL, PROMPT, RDA, SDCL, or SQL as value. // *Mnemonic: DIAG_FACT_BAD_TYPE // 08124,0, "Fact : Invalid parameter name" // *Cause: The name attribute value does not contain a valid parameter // name. // *Action: Fix the paramater name attribute value. Valid names are be composed // of two or more words, separated by dots. // *Mnemonic: DIAG_FACT_BAD_PARAM // 08125,0, "Fact : Missing command" // *Cause: The corresponding sdp_fact element has no sdp_command child elements. // *Action: Add one or more sdp_command child element to the sdp_fact element. // *Mnemonic: DIAG_FACT_NO_COMMAND // 08126,0, "Fact : Missing description" // *Cause: RDA did not find a sdp_description element as child of the sdp_fact // element. // *Action: Make sure that the corresponding sdp_fact element has a single // sdp_description child element. // *Mnemonic: DIAG_FACT_NO_DESC // 08127,0, "Fact : Missing parameter" // *Cause: The sdp_fact element has no parameter attribute. // *Action: Add a parameter attribute in the sdp_fact element. // *Mnemonic: DIAG_FACT_NO_PARAM // 08128,0, "Fact : Multiple descriptions" // *Cause: The sdp_fact element contains multiple sdp_description elements. // *Action: Make sure that the sdp_fact elements has a single sdp_description // child element. // *Mnemonic: DIAG_FACT_MORE_DESC // 08130,0, "Missing or invalid rule identifier" // *Cause: The sdp_rule element has no id attribute. // *Action: Add an id attribute in the sdp_rule element. // *Mnemonic: DIAG_BAD_RULE // 08131,0, "Duplicate rule" // *Cause: Two or more rules have the same identifier. // *Action: Make the rule identifier unique. // *Mnemonic: DIAG_DUP_RULE // 08132,0, "Rule : Action(s) never used" // *Cause: The rule contains more actions after an unconditional action. // *Action: Review the action flow. // *Mnemonic: DIAG_ACT_NOT_USED // 08133,0, "Rule : Bad parameter name" // *Cause: The parameter attribute value does not contain a valid parameter // name. // *Action: Fix the paramater name. Valid names are be composed of two or // more words, separated by dots. // *Mnemonic: DIAG_RULE_BAD_PARAM // 08134,0, "Rule : Bad variable name in action" // *Cause: The variable attribute value does not contain a valid variable name. // *Action: Fix the variable name. Valid names start with a dollar ($) and a // letter followed by alphanumerical characters. // *Mnemonic: DIAG_ACT_BAD_VAR // 08135,0, "Rule : Bad variable name" // *Cause: The variable attribute value does not contain a valid variable name. // *Action: Fix the variable name. Valid names start with a dollar ($) and a // letter followed by alphanumerical characters. // *Mnemonic: DIAG_RULE_BAD_VAR // 08136,0, "Rule : Circular dependencies" // *Cause: An sdp_dependency element of the corresponding sdp_rule element has // a direct or indirect reference to this rule. // *Action: Eliminate the circular dependency. // *Mnemonic: DIAG_RULE_CIRC // 08137,0, "Rule : Command errors" // *Cause: RDA detected errors in the code contained in the sdp_command // elements. // *Action: Fix the code errors. // *Mnemonic: DIAG_RULE_ERRORS // 08138,0, "Rule : Identifier too long" // *Cause: The id attribute value of the corresponding sdp_rule element is too // long. // *Action: Make sure that the id attribute value in the sdp_rule elements is // not longer than 6 characters. // *Mnemonic: DIAG_RULE_BAD_ID // 08139,0, "Rule : Invalid condition in action" // *Cause: RDA did not recognize the condition. // *Action: Review the action condition and take corrective actions. // *Mnemonic: DIAG_ACT_BAD_COND // 08140,0, "Rule : Invalid message reference in action" // *Cause: The message attribute contains one or more references to unknown // sdp_message elements. // *Action: Make sure that the message attribute value is a comma-separated // list of existing message identifiers. // *Mnemonic: DIAG_ACT_BAD_MESG // 08141,0, "Rule : Invalid result code in action" // *Cause: RDA found an invalid result code in the action. // *Action: Make sure that the value of the result attribute is FAILED, // PASSED, SKIPPED, or WARNING. // *Mnemonic: DIAG_ACT_BAD_RESULT // 08142,0, "Rule : Invalid syntax type in action" // *Cause: RDA found an invalid syntax type in the action. // *Action: Make sure that the value of the syntax attribute is either text or // wiki. // *Mnemonic: DIAG_ACT_BAD_SYNTAX // 08143,0, "Rule : Maximum attribute required for condition in action" // *Cause: The specified condition requires a maximum value. // *Action: Review the action condition and take corrective actions. // *Mnemonic: DIAG_ACT_NO_MAX // 08144,0, "Rule : Minimum attribute required for condition in action" // *Cause: The specified condition requires a minimum value. // *Action: Review the action condition and take corrective actions. // *Mnemonic: DIAG_ACT_NO_MIN // 08145,0, "Rule : Missing command" // *Cause: The corresponding sdp_rule element has no sdp_command child elements. // *Action: Add one or more sdp_command child element to the sdp_rule element. // *Mnemonic: DIAG_RULE_NO_COMMAND // 08146,0, "Rule : Missing definition for dependency" // *Cause: The sdp_dependency element refers to an undefined rule. // *Action: Review the dependencies and take corrective actions. // *Mnemonic: DIAG_RULE_NO_DEP // 08147,0, "Rule : Missing dependency identifier" // *Cause: Some sdp_dependency elements do not have an id attribute. // *Action: Make sure that all sdp_dependency elements have an id attribute. // *Mnemonic: DIAG_RULE_NO_ID // 08148,0, "Rule : Missing description" // *Cause: RDA did not find a sdp_description element as child of the sdp_rule // element. // *Action: Make sure that the corresponding sdp_rule element has a single // sdp_description child element. // *Mnemonic: DIAG_RULE_NO_DESC // 08149,0, "Rule : Missing or invalid command type" // *Cause: The corresponding sdp_command element has no valid type attribute. // *Action: Make sure that the sdp_command element contains a mode attribute // with ATTACH, OS, PERL, PROMPT, RDA, SDCL, or SQL as value. // *Mnemonic: DIAG_RULE_NO_TYPE // 08150,0, "Rule : Missing or invalid rule mode" // *Cause: The corresponding sdp_rule element has no valid mode attribute. // *Action: Make sure that the sdp_rule element contains a mode attribute with // ATTACH, LOG, RECORD, VERIFY, or VERIFY_ABORT as value. // *Mnemonic: DIAG_RULE_NO_MODE // 08151,0, "Rule : Missing rule name" // *Cause: The corresponding sdp_rule element has no name attribute. // *Action: Add a name attribute to the sdp_rule element. // *Mnemonic: DIAG_RULE_NO_NAME // 08152,0, "Rule : Multiple descriptions" // *Cause: The sdp_rule element contains multiple sdp_description elements. // *Action: Make sure that the sdp_rule elements has a single sdp_description // child element. // *Mnemonic: DIAG_RULE_MORE_DESC // 08153,0, "Rule : Rule name too long" // *Cause: The rule name can be truncated on display. // *Action: Too avoid display truncation, the rule name should not be longer // than 20 characters. // *Mnemonic: DIAG_RULE_BAD_NAME // 08154,0, "Rule : Opt-out/ dependency conflict" // *Cause: The rule can be opted out but appears in dependencies. // *Action: Take corrective actions to eliminate that situation. // *Mnemonic: DIAG_BAD_OPTOUT // 08160,0, "Rule /Dependency : Invalid condition" // *Cause: RDA did not recognize the condition. // *Action: Review the dependency condition and take corrective actions. // *Mnemonic: DIAG_DEP_BAD_COND // 08161,0, "Rule /Dependency : Invalid message reference" // *Cause: The message attribute contains one or more references to unknown // sdp_message elements. // *Action: Make sure that the message attribute value is a comma-separated // list of existing message identifiers. // *Mnemonic: DIAG_DEP_BAD_MESG // 08162,0, "Rule /Dependency : Invalid result code" // *Cause: RDA found an invalid result code in the dependency. // *Action: Make sure that the value of the result attribute is FAILED, // PASSED, SKIPPED, or WARNING. // *Mnemonic: DIAG_DEP_BAD_RESULT // 08163,0, "Rule /Dependency : Invalid syntax type" // *Cause: RDA found an invalid syntax type in the dependency. // *Action: Make sure that the value of the syntax attribute is either text or // wiki. // *Mnemonic: DIAG_DEP_BAD_SYNTAX // 08164,0, "Rule /Dependency : Maximum attribute required for condition" // *Cause: The specified condition requires a maximum value. // *Action: Review the dependency condition and take corrective actions. // *Mnemonic: DIAG_DEP_NO_MAX // 08165,0, "Rule /Dependency : Minimum attribute required for condition" // *Cause: The specified condition requires a minimum value. // *Action: Review the dependency condition and take corrective actions. // *Mnemonic: DIAG_DEP_NO_MIN // 08170,0, "Missing identifier in message" // *Cause: The id attribute is missing in the corresponding sdp_message element. // *Action: Add an id attribute to the sdp_message element. // *Mnemonic: DIAG_BAD_MESG // 08171,0, "Duplicate message identifier" // *Cause: The specified identifier is present in multiple sdp_message elements. // *Action: Make the message identifiers unique. // *Mnemonic: DIAG_DUP_MESG // 08180,0, "Missing attribute name in request" // *Cause: The name attribute is missing in the corresponding sdp_ask element. // *Action: Add a name attribute to the sdp_ask element. // *Mnemonic: DIAG_EVAL_NO_NAME // 08181,0, "Missing command in request" // *Cause: The command attribute is missing in the corresponding sdp_exec // element. // *Action: Add a command attribute to the sdp_exec element. // *Mnemonic: DIAG_EVAL_NO_COMMAND // 08182,0, "Invalid tag" // *Cause: An sdp_content element of type eval contains an unexpected tag. // *Action: Make sure that sdp_content elements of type eval contain only // sdp_ask and sdp_exec child elements. // *Mnemonic: DIAG_EVAL_BAD_TAG // 08183,0, "Only tags expected in request" // *Cause: RDA expected only tag elements in an sdp_content element of type // eval. // *Action: Make sure that sdp_content elements of type eval contain only // sdp_ask and sdp_exec child elements. // *Mnemonic: DIAG_EVAL_NOT_TAG // // /////////////////////////////////////////////////////////////////////////// // 09000.09999 Other Errors // /////////////////////////////////////////////////////////////////////////// // 09000,0, "Cannot open the Web service directory" // *Cause: RDA cannnot open the Web service directory. // *Action: The next line provides more information about this error. Take // appropriate actions to fix it. // *Mnemonic: WEB_ERR_OPEN // 09001,0, "Cannot load the Web service" // *Cause: RDA cannnot load the specified package. // *Action: The next line provides more information about this error. Take // appropriate actions to fix it. // *Mnemonic: WEB_ERR_LOAD // 09002,0, "No services" // *Cause: RDA did not load any Web service. // *Action: The next line provides more information about this error. Take // appropriate actions to fix it. // *Mnemonic: WEB_NO_SERVICE // 09003,0, "socket error" // *Cause: RDA encountered a socket error. // *Action: The next line provides more information about this error. Take // appropriate actions to fix it. // *Mnemonic: WEB_SOCKET_ERR // 09004,0, "setsockopt error" // *Cause: RDA encountered a setsockopt error. // *Action: The next line provides more information about this error. Take // appropriate actions to fix it. // *Mnemonic: WEB_SETSOCKOPT_ERR // 09005,0, "bind error" // *Cause: RDA encountered a bind error. // *Action: The next line provides more information about this error. Take // appropriate actions to fix it. // *Mnemonic: WEB_BIND_ERR // 09006,0, "listen error" // *Cause: RDA encountered a listen error. // *Action: The next line provides more information about this error. Take // appropriate actions to fix it. // *Mnemonic: WEB_LISTEN_ERR // 09010,0, "Invalid directory" // *Cause: The target path does not correspond to a directory. // *Action: The next line provides more information about this error. Take // appropriate actions to fix it. // *Mnemonic: XPLR_DIR_ERR // 09011,0, "Cannot create result file" // *Cause: RDA cannot create the Explorer report // *Action: The next line provides more information about this error. Take // appropriate actions to fix it. // *Mnemonic: XPLR_CREATE_ERR // 09012,0, "Cannot open report file" // *Cause: RDA cannot open the report containing some Explorer results. // *Action: The next line provides more information about this error. Take // appropriate actions to fix it. // *Mnemonic: XPLR_OPEN_ERR // // //////////////////////////////////////////////////////////////////////////// // Copyright Notice // Copyright (c) 2002, 2012, Oracle and/or its affiliates. All rights reserved. // // Trademark Notice // Oracle and Java are registered trademarks of Oracle and/or its // affiliates. Other names may be trademarks of their respective owners. // ////////////////////////////////////////////////////////////////////////////