Table of Contents Previous Next PDF


Oracle Tuxedo Application Rehosting Workbench Messages
Oracle Tuxedo Application Rehosting Workbench Messages
The messages in this section are organized by tool. The following tools are documented:
•
RDBMS – DB2-to-Oracle Converter Messages
•
FILE - File Convertor Messages
•
JCL - JCL Translator Messages
DB2-to-Oracle Converter Messages
Overview
The error and warning messages generated by the DB2-to-Oracle Convertor fall into one of the following categories:
•
DB2-to-Oracle Converter Messages.
•
File Internally Called Script Messages.
•
Reloading Error Messages.
DB2-to-Oracle Convertor Error Messages and Translation Issues
Overview
There are two types of reason why error messages may be produced:
•
Environment problem: Your working environment is either not correctly installed or incorrectly configured. The environment has perhaps been modified during the data migration.
•
Internal error: To resolve any internal errors, check the error messages produced during preceding phases, including the Cataloger phase.
DB2-to-Oracle Convertor Set-up Error Messages
RDBMS-0005:
Message: The configuration file <arg> should be an absolute path.
Environment problem.
RDBMS-0006:
Message: The configuration file <arg> has an unexpected name. Expected param/trans.conf.
Environment problem.
RDBMS-0008:
Message: Filenames in <arg> must be relative to the param directory.
Environment problem.
RDBMS-0009:
Message: Filenames passed to the SQL DB2-to-Oracle Converter on the command line must be absolute.
Environment problem.
RDBMS-0010:
Message: No -s command line argument.
Environment problem.
RDBMS-0011:
Message: No -target-os command line argument.
Environment problem
RDBMS-0012:
Message: No -target-rdbms command line argument.
Environment problem: The target database management system must be specified with the -target-rdbms command line argument. Check your configuration files.
RDBMS-0013:
Message: No -target-rdbms-version command line argument.
Environment problem.
RDBMS-0014:
Message: One of either -ddl or -ddls-file must be on the command line.
Environment problem.
RDBMS-0020:
Message: Ambiguous source information from the system (OS: <arg>, DB: <arg>, Version: <arg>). No suitable default could be determined.
Environment problem.
RDBMS-0021:
Message: Invalid source OS or database specified: (OS: <arg>, DB: <arg>, Version: <arg>).
Environment problem.
RDBMS-0022:
Message: Ambiguous target information from the system (OS: <arg>, DB: <arg>, Version: <arg>). No suitable default could be determined.
Explanation: The target operating system and database information specified in the configuration files was ambiguous. The system could not find any default configuration that matches the information that was provided.
RDBMS-0023:
Message: Invalid target OS or database specified: (OS: <arg>, DB: <arg>, Version: <arg>).
Environment problem.
RDBMS-0030:
Message: Translation from <arg> to <arg> is not supported.
Environment problem.
RDBMS-0040:
Message: Cannot find the DB properties file <arg>.
Environment problem.
RDBMS-0041:
Message: Unrecognized db properties line <arg>.
Explanation: The DB properties line has an incorrect format.
RDBMS-0042:
Message: Both :indexsort <arg> and :indexlang <arg> were specified.
Explanation: The :indexsort and :indexlang properties are mutually exclusive. The configuration file specified both. Remove one of these properties.
RDBMS-0043:
Message: Invalid lobs_fname_length.
Explanation: The lobs_fname_length parameter must be a valid integer, giving the maximum length of external file names containing LOB data.
RDBMS-0060:
Message: Cannot find the reserved words file <arg>.
Environment problem.
RDBMS-0061:
Message: Cannot determine the reserved words for <arg>.
Explanation: The system could not determine the set of reserved words for a SQL dialect.
RDBMS-0080:
Message: Cannot find rename file <arg>.
Environment problem.
RDBMS-0081:
Message: Invalid rename pattern: <arg>.
Explanation: The rename file line could not be parsed as a rename pattern.
RDBMS-0082:
Message: Unrecognized renaming pattern line <arg>
Explanation: The rename file line has an incorrect format.
RDBMS-0100:
Message: Could not find system description file <arg>.
Environment problem.
RDBMS-0101:
Message: The SQL source contains parse errors. The mis-parsed files are: <arg>.
Explanation: Some of the SQL files in the system mis-parsed. Check the files for correct syntax.
RDBMS-0102:
Message: The SQL source does not contain any statements.
Explanation: There are no statements in the SQL system. Check your source files.
RDBMS-0103:
Message: Loading system description file <arg> failed.
Environment problem.
RDBMS-0104:
Message: Failed to update system catalog for <arg>.
Environment problem.
RDBMS-0105:
Message: Catalog for <arg> is out of date and needs to be updated externally.
Explanation: The catalog for the system is out of date. Either update it directly or specify the -will-ddl-changes command line argument.
RDBMS-0106:
Message: Bad source directory <arg>.
Environment problem.
RDBMS-0107:
Message: Bad target directory <arg>.
Environment problem.
RDBMS-0120:
Message: Cannot find schema name file <arg>.
Environment problem.
RDBMS-0121:
Message: Bad SQL system <arg>.
Environment problem.
RDBMS-0122:
Message: Bad virtual file <arg>.
Environment problem.
RDBMS-0123:
Message: Could not extract schema <arg>.
Explanation: The schema could not be extracted from the SQL system.
RDBMS-0124:
Message: Bad schemas were extracted <arg>.
Explanation: Some of the schemas that were extracted are corrupted.
RDBMS-0125:
Message: Elements <arg> were claimed by several schemas.
Explanation: Some SQL elements were claimed by multiple schemas.
RDBMS-0126:
Message: <arg> is not a known schema name.
Explanation: A schema name was specified that does not exist in the SQL system.
RDBMS-0127:
Message: The current schema is corrupted.
Explanation: The current schema for translation is corrupted.
RDBMS-0128:
Message: SQL schema <arg> is empty.
Explanation: There are no SQL elements in the given schema.
RDBMS-0129:
Message: Adding duplicate schema element: <arg>
Explanation: An attempt was made to add a duplicate element to a schema.
Setup Translation-Issue Messages
RDBMS-0024:
Message: Incomplete source information for the system (OS: <arg>, DB: <arg>, Version: <arg>). Defaulting to (OS: <arg>, DB: <arg>, Version: <arg>).
Environment problem.
RDBMS-0025:
Message: Incomplete target information for the system (OS: <arg>, DB: <arg>, Version: <arg>). Defaulting to (OS: <arg>, DB: <arg>, Version: <arg>).
Environment problem.
RDBMS-0045:
Message: Unknown RDBMS parameter <arg> <arg>.
Environment problem.
RDBMS-0083:
Message: Rename pattern <arg> is pre-empted by an earlier pattern and will never be applied.
Explanation: The renaming pattern is not effective because there is a pattern earlier in the pattern sequence that will be applied in the same situations. Review the sequence of renaming patterns.
RDBMS-0130:
Message: Schema <arg> is not in the system. It will be skipped.
Explanation: The indicated schema could not be found in the system. It will not be translated.
RDBMS-0131:
Message: Schemas <arg> are not in the system. They will be skipped.
Explanation: The indicated schemas could not be found in the system. They will not be translated.
RDBMS-0132:
Message: <num> schema elements <arg> not claimed by any schema. The <arg>: <arg>.
Explanation: There are SQL elements in the system that cannot be mapped to any schema. The types of the elements are listed in the message.
Translation Error Messages
There are currently no error messages associated with the translation phase.
Translation Issue Messages
RDBMS-1000:
Message: No source file information for a <arg> node.
Internal error.
RDBMS-1001:
Message: <num> <arg> violations detected.
Internal error.
RDBMS-1002:
Message: <arg> violation: <arg>
Internal error.
RDBMS-1003:
Message: Unlinked identifier <arg>.
Internal error.
RDBMS-1004:
Message: Multi linked identifier <arg>.
Internal error.
RDBMS-1005:
Message: Instantiated interior class <arg>.
Internal error.
RDBMS-1040:
Message: There are DATE data types but the :date_format was not specified.
Explanation: The translator needs knowledge of the :date_format in order to translate DATE data types.
RDBMS-1041:
Message: There are TIME data types but the :time_format was not specified.
Explanation: The translator needs knowledge of the :time_format in order to translate TIME data types.
RDBMS-1042:
Message: There are TIMESTAMP data types but the :timestamp_format was not specified.
Explanation: The translator needs knowledge of the :timestamp_format in order to translate TIMESTAMP data types.
RDBMS-1043:
Message: There are CLOB or BLOB data types but the :lobs_fname_length was not specified.
Explanation: The translator needs knowledge of the :lobs_fname_length in order to translate CLOB or BLOB data types.
RDBMS-1060:
Message: Unexpected top-level DDL element of class <arg>.
Internal error.
RDBMS-1080:
Message: Unknown table constraint type <arg>.
Explanation: The translator found a table constraint that it could not identify.
RDBMS-1081:
Message: Unrecognized table constraint type <arg> for <arg>.
Explanation: The translator found a type of table constraint that it was not expecting.
RDBMS-1082:
Message: Unknown column constraint type for <arg>.
Explanation: The translator found a column constraint that it could not identify.
RDBMS-1083:
Message: Unrecognized column constraint type <arg> for <arg>.
Explanation: The translator found a type of column constraint that it was not expecting.
RDBMS-1085:
Message: Could not determine default NULL value for data type <arg>.
Explanation: The translator could not determine a translation for a DEFAULT value of NULL for a data type.
RDBMS-1086:
Message: Could not determine default empty string value for data type <arg>.
Explanation: The translator could not determine a translation for a DEFAULT value of "" for a data type.
RDBMS-1100:
Message: Untranslated data type <arg>.
Explanation: A source data type was not translated to a target data type.
RDBMS-1101:
Message: CHAR to VARCHAR2 size is too long: <num>.
Explanation: The length of the CHAR type is greater than the maximum allowed VARCHAR2 length.
RDBMS-1200:
Message: Identifier name <arg> conflicts with a reserved word.
Explanation: An identifier name conflicts with a reserved word. Add a rename rule to remove the conflict.
RDBMS-1201:
Message: There are duplicate <arg> schema elements: <arg>.
Explanation: Duplicate schema elements were detected in the final translation.
RDBMS-1202:
Message: Table <arg> has duplicate column names <arg>.
Explanation: There are duplicate column names in a table definition.
RDBMS-1203:
Message: <arg> was not fully applied to the schema elements.
Internal error.
Output Error Messages
There are currently no error messages associated with the output phase.
Output Translation-Issue Messages
There are currently no translation issues associated with the output phase.
Miscellaneous Error Messages
RDBMS-3001:
Message: There is no base directory, but this file is relative: <arg>.
Environment problem.
RDBMS-3002:
Message: Invalid value of Configuration-From(<arg>).
Environment problem.
RDBMS-3003:
Message: Catalog system <arg> did not load correctly.
Environment problem.
RDBMS-3004:
Message: SQL System <arg> did not load correctly.
Environment problem.
RDBMS-3005:
Message: Poorly formed parse tree <arg>.
Internal error.
RDBMS-3011:
Message: Bad value for *rename-pattern-match-mode*: <arg>.
Explanation: The renaming sub-system has detected an internal inconsistency.
RDBMS-3012:
Message: DIALECT-LOOKUP: no value in <arg> for <arg>.
Internal error.
RDBMS-3013:
Message: DIALECT-LOOKUP-2: no value in <arg> for <<arg>, <arg>>.
Internal error.
RDBMS-3015:
Message: DDL-TRANS-ELEMENTS-SUCH-THAT: bad predicate <arg>.
Internal error.
RDBMS-3016:
Message: Adding duplicate root element: <arg>.
Internal error.
RDBMS-3017:
Message: Problem linking original <arg> (<arg>) and copy <arg> (<arg>).
Internal error.
RDBMS-3018:
Message: Unexpected unlinked id action <arg>.
Internal error.
RDBMS-3019:
Message: Do not make multiple name generators of class <arg>.
Internal error.
RDBMS-3020:
Message: Unknown DB2-to-Oracle Converter mode <arg>.
Internal error.
RDBMS-3021:
Message: IN-ORIGINAL-SCHEMA?: no current schema to check <arg>.
Internal error.
RDBMS-3022:
Message: IN-TRANSLATION-TREE?: no translation root to check <arg>.
Internal error.
RDBMS-3023:
Message: RECORD-OUTPUT-FILE: unknown output file type <arg>.
Internal error.
RDBMS-3024:
Message: GET-OUTPUT-FILES-OF-TYPE: unknown output file type <arg>.
Internal error.
RDBMS-3025:
Message: OUTPUT-DATA-LOADER-FILES: <arg> is not callable.
Internal error.
RDBMS-3026:
Message: Bad dialect comparison mode <arg>.
Internal error.
RDBMS-3027:
Message: Bad dialect canonicalization function <arg>.
Internal error.
Miscellaneous Translation-Issue Messages:
RDBMS-3007:
Message: Failed to output DDL for <arg>.
Explanation: A DDL element was not output to the SQL files.
RDBMS-3008:
Message: Could not determine data type class for column <arg>.
Explanation: The data type class could not be determined for a column type.
RDBMS-3009:
Message: No COBOL DDEs for <arg>.
Explanation: The translator did not produce any data description entries for a column.
RDBMS-3010:
Message: Could not determine SQL*Loader data type for <arg>.
Explanation: The SQL*Loader data type for a column data type could not be determined.
RDBMS Script Error Messages
The messages in this section are organized by tool. The following tools are documented:
•
RDBMS –DB2-to-Oracle Converter messages
•
DB2-to-Oracle Converter Setup Error Messages:
RDBMSWB-0001:
Example: $usage
Explanation: Error in the arguments entered for the rdbms.sh command.
RDBMSWB-0002:
Example: Do not mix -C and -C parameters. $usage
Explanation: The -c and -C parameters cannot be used simultaneously to concurrently to launch rdbms.sh, correct and relaunch the execution.
RDBMSWB-0003:
Example: Unix variable TMPPROJECT is not set or contains a bad directory name.
Explanation: Check the value of the TMPPROJECT variable and relaunch the execution.
RDBMSWB-0004:
Example: Temporary output directory $tempoutputdir is missing.
Explanation: Check the value of the TMPPROJECT variable and relaunch the execution.
RDBMSWB-0005:
Example: Invalid argument: do not use -s argument with -c|-C or -g or -m or -r or -i. $usage
Explanation: Check the arguments passed with the rdbms.sh command and relaunch the execution.
RDBMSWB-0006:
Example: Target output directory $targetoutputdir is missing. Check parameters: -i <output_directory> <schema>
Explanation: Check the arguments passed with the rdbms.sh command and relaunch the execution.
RDBMSWB-0007:
Example: Target output directory $targetoutputdir is missing. Check parameters: -s <output_directory> (<schema>,...)
Explanation: Check the arguments passed with the rdbms.sh command and relaunch the execution.
RDBMSWB-0008:
Example: Mandatory argument is list of schema (<schema>,...). $usage
Explanation: The -s option expects an installation directory and a list of schemas as arguments.
RDBMSWB-0009:
Example: Mandatory argument is <schema_name>. $usage
Explanation: The -i option expects an installation directory and a list of schemas as arguments.
RDBMSWB-0010:
Example: Too many arguments: $2. $usage
Explanation: Check the arguments passed with the rdbms.sh command and relaunch the execution.
RDBMSWB-0011:
Example: External Variable PARAM is not set!
Explanation: Initialize the PARAM variable and relaunch the execution.
RDBMSWB-0021:
Example: Can not access to directory $tempoutputdir/Template/$schema.
Explanation: Check the sequence of options used to execute the rdbms.sh script.
RDBMSWB-0022:
Example: can not access to directory $tempoutputdir.
Explanation: Check the value of the TMPPROJECT variable and relaunch the Rehosting Workbench.
RDBMSWB-0102:
Example: in reading configuration file db-param.cfg. Check previous error messages (1)
Explanation: __
RDBMSWB-0103:
Example: Error in adding line into ${optionsfile} file. Check previous error messages.
Explanation: __
RDBMSWB-0111:
Example: The file <file> containing list of unsupported objects is missing.
Explanation: Check previous error messages.
RDBMSWB-0112:
Example: Error during reading the file containing list of unsupported objects. Check previous error messages.
Explanation: __
RDBMSWB-0199:
Example: conversion aborted $addMess. Check previous error messages.
Explanation: __
RDBMSWB-0201:
Example: Mapper file $tempoutputdir/$schema/mapper-$schema.re does not exist! $addMess
Explanation: This file is automatically generated; check the system messages displayed before this error.
RDBMSWB-0202:
Example: Mapper file $tempoutputdir/$schema/mapper-$schema.re is empty! $addMess
Explanation: This file is automatically generated; check your work environment.
RDBMSWB-0203:
Example: Datamap file $tempoutputdir/$schema/Datamap-$schema.re does not exist! $addMess
Explanation: This file is automatically generated; check the system messages displayed before this error.
RDBMSWB-0204:
Example: Default Templates list file $defaulttemplatesfile is missing !
Explanation: Check the system messages displayed before this error.
RDBMSWB-0205:
Example: Can not modify #VAR: strings (in templates list file)
Explanation: Check the system messages displayed before this error.
RDBMSWB-0206:
Example: Check $templatesfile and $tmptemplatesfile files
Explanation: Check the system messages displayed before this error.
RDBMSWB-0207:
Example: Mapper file $orimapperfile is missing!
Explanation: This file is automatically generated; check the system messages displayed before this error.
RDBMSWB-0208:
Example: Can not modify #VAR: strings (in mapper file)
Explanation: Check the system messages displayed before this error.
RDBMSWB-0211:
Example: The file <file> containing list of generated components to be discarded is missing.
Explanation: Check previous error messages.
RDBMSWB-0212:
Example: Error during reading the file containing list of generated components to be discarded. Check previous error messages.
Explanation: __
RDBMSWB-0242:
Example: unknown datatype for field %FLD-1:-C%INDICES:: %FLD-1:-IBM-DESC / %FLD-1:-MF-DESC
Explanation: The DB2 DDL is incorrect or the data type is not supported.
RDBMSWB-0243:
Example: datatype not supported in DB2/MVS. field %FLD-1:-C%INDICES:: %FLD-1:-IBM-DESC / %FLD-1:-MF-DESC
Explanation: The DB2 DDL is incorrect or the data type is not supported.
RDBMSWB-0244:
Example: OCCURS engineering not supported in SPLIT %SPLIT-1:-L
Explanation: COBOL OCCURS not supported in the data description copy files.
RDBMSWB-0250:
Example: Unknown JCL_UNLOAD_UTILITY_NAME option. Check '<VAL>'
Explanation: Bad value for parameter rdbms:jcl_unload_utility_name: in db-param.cfg configuration file.
RDBMSWB-0251:
Example: Unknown JCL_UNLOAD_FORMAT_FILE option. Check '<VAL>’
Explanation: Bad value for parameter rdbms:jcl_unload_format_file: in db-param.cfg configuration file.
RDBMSWB-0252:
Example: JCL_UNLOAD_FORMAT_FILE='csv' is only compatible with JCL_UNLOAD_UTILITY_NAME='dsnuproc'. Check '<VAL>'
Explanation: __
RDBMSWB-0299:
Example: generation aborted. Check previous error messages
Explanation: __
RDBMSWB-0303:
Example: There was a problem during dynamic modification of programs
Explanation: The script used to modify the generated components has not ended normally; check the script and relaunch the execution.
RDBMSWB-0304:
Example: There was a problem during modification. Check previous message.
Explanation: __
RDBMSWB-0305:
Example: problem in modifying $ext files
Explanation: Check the system messages displayed before this error.
RDBMSWB-0306:
Example: problem during chmod of shell $file
Explanation: Check the system messages displayed before this error.
RDBMSWB-0307:
Example: problem in accessing *sh files
Explanation: Check the system messages displayed before this error.
RDBMSWB-0402:
Example: can not access to directory $tempoutputdir/outputs/$schema.
Explanation: Check the system messages displayed before this error.
RDBMSWB-0403:
Example: can not access to directory $tempoutputdir/SQL/$schema.
Explanation: Check the system messages displayed before this error.
RDBMSWB-0404:
Example: can not access to generates script $scriptfile. # Check -g parameter
Explanation: Check the use of the -g parameter of the rdbms.sh.
RDBMSWB-0405:
Example: script $scriptfile is not executable. # Use -r after -m parameter.
Explanation: When executing the rdbms.sh script the -r parameter should be used after the -m parameter.
RDBMSWB-0407:
Example: Remove schema name step aborted. Check script file name $scriptfile.
Explanation: Check the previous messages.
RDBMSWB-0501:
Example: installation aborted. Check previous message.
Explanation: __
RDBMSWB-0502:
Example: Configuration file generation aborted. Check previous error messages
Explanation: __
RDBMS and File Internally Called Script Messages
The messages in this section are organized by tool. The following tools are documented:
•
RDBMS –DB2-to-Oracle Converter messages
•
DB2-to-Oracle Converter Setup Error Messages:
DATAWB-1001:
Example: File $template is missing!
Explanation: The Oracle Tuxedo Application Rehosting Workbench working environment is not correctly installed.
DATAWB-1002:
Example: Missing Template file: $file or his pob version
Explanation: The *templates.txt file is incorrectly installed or has been incorrectly modified.
DATAWB-1003:
Example: Remove the pob extension to file name $file
Explanation: The *templates.txt file is incorrectly installed or has been incorrectly modified.
DATAWB-1011:
Example: missing file name arg1
Explanation: Internal error, The Oracle Tuxedo Application Rehosting Workbench working environment is not correctly installed or configured.
DATAWB-1012:
Example: bad return code for awk
Explanation: Check the previous system messages.
DATAWB-1013:
Example: There was a problem during updating component $fixedfile
Explanation: Check the previous system messages.
DATAWB-1014:
Example: There was a problem during comparing component $file
Explanation: Check the previous system messages.
DATAWB-1021:
Example: Bad 1st parameter. <InputFile> <OutputFile>
Explanation: Check the previous system messages.
DATAWB-1022:
Example: Bad 2nd parameter. <InputFile> <OutputFile>
Explanation: Internal error, The Oracle Tuxedo Application Rehosting Workbench working environment is not correctly installed or configured.
DATAWB-1023:
Example: sed script return a bad return code
Explanation: Check the previous messages.
DATAWB-1031:
Example: can not access to directory Template/$schema.
Explanation: Internal error, The Oracle Tuxedo Application Rehosting Workbench working environment is not correctly installed or configured.
DATAWB-1032:
Example: can not found $movefile file
Explanation: Internal error, The Oracle Tuxedo Application Rehosting Workbench working environment is not correctly installed or configured.
DATAWB-1033:
Example: can not read $movefile file
Explanation: Internal error, The Oracle Tuxedo Application Rehosting Workbench working environment is not correctly installed or configured.
DATAWB-1034:
Example: Version $relformat in $movefile is not supported by this tool.
Explanation: Internal error, The Oracle Tuxedo Application Rehosting Workbench working environment is not correctly installed or configured.
DATAWB-1035:
Example: can not evaluate string [$line] from $movefile
Explanation: Internal error, The Oracle Tuxedo Application Rehosting Workbench working environment is not correctly installed or configured.
DATAWB-1036:
Example: bad 1st argument typ in line $line
Explanation: Internal error, The Oracle Tuxedo Application Rehosting Workbench working environment is not correctly installed or configured.
DATAWB-1037:
Example: bad 2nd argument source_directory in line $line
Explanation: Internal error, The Oracle Tuxedo Application Rehosting Workbench working environment is not correctly installed or configured.
DATAWB-1038:
Example: $info_filename is missing or empty (in <td>/$inputfile)
Explanation: Internal error, The Oracle Tuxedo Application Rehosting Workbench working environment is not correctly installed or configured.
DATAWB-1039:
Example: $info_filename: problem when creating directory $targetdirectory for $outputfile
Explanation: Check the previous system messages.
DATAWB-1040:
Example: $info_filename: problem during a copy $inputfile to $outputfile in line $line
Explanation: Check the previous system messages.
DATAWB-1041:
Example: $info_filename: can not chmod executable $outputfile
Explanation: Check the previous system messages.
DATAWB-1042:
Example: $info_filename: can not chmod non executable script $inputfile
Explanation: Check the previous system messages.
DATAWB-1043:
Example: bad return code when executing $inputfile
Explanation: Check the previous system messages.
DATAWB-1051:
Example: can not access to directory Template/$schema. Separator character between each schema name has to be a coma ','.
Explanation: Internal error, The Oracle Tuxedo Application Rehosting Workbench working environment is not correctly installed or configured.
DATAWB-1052:
Example: can not grep $movefile file
Explanation: Internal error, The Oracle Tuxedo Application Rehosting Workbench working environment is not correctly installed or configured.
DATAWB-1053:
Example: content of file $movefileori are not equal for tag 'M:s:'
Explanation: Internal error, The Oracle Tuxedo Application Rehosting Workbench working environment is not correctly installed or configured.
DATAWB-1054:
Example: can not find generated file $filetoinclude
Explanation: Internal error, The Oracle Tuxedo Application Rehosting Workbench working environment is not correctly installed or configured.
DATAWB-1055:
Example: can not modify a file
Explanation: Check the previous system messages.
DATAWB-1056:
Example: can not generate $outputfile using perl program
Explanation: Check the previous system messages.
DATAWB-1057:
Example: $info_filename: can not chmod a temporary file $tmpfilemc in line $line
Explanation: Check the previous system messages.
DATAWB-1061:
Example: Bad parameters: file|rdbms <configfile> <OutputFile>
Explanation: Check the previous system messages.
DATAWB-1062:
Example: Configuration file $configfile is missing !
Explanation: Check the previous system messages.
DATAWB-1063:
Example: Can not create temporary parameter file $outputfile
Explanation: Check the previous system messages.
DATAWB-1064:
Example: Can not insert a line into the temporary parameter file $outputfile
Explanation: Check the previous system messages.
DATAWB-1065:
Example: Bad 1st parameter. file|rdbms <configfile> <OutputFile>
Explanation: Check the previous system messages.
DATAWB-1101:
Example: usage is $scriptname <format_log> <mvslog_filename> <output_report_filename>
Explanation: Impossible to process the LOG file containing the z/OS unloading information.
DATAWB-1102:
Example: in $scriptname. Input mvs log file is missing $mvslogfile.
Explanation: Impossible to process the LOG file containing the z/OS unloading information.
DATAWB-1103:
Example: in $scriptname.$0. bad return code for awk reading $mvslogfile
Explanation: Impossible to process the LOG file containing the z/OS DSNTIAUL unloading information.
DATAWB-1104:
Example: in $scriptname.$0. can not found SUCCESSFUL UNLOAD x ROWS information in SYSPRINT LOG report file $mvslogfile
Explanation: Impossible to process the LOG file containing the z/OS DSNTIAUL unloading information.
DATAWB-1105:
Example: in $scriptname.$0. empty 4th arg. $usage4args
Explanation: Impossible to process the LOG file containing the z/OS FTP unloading information.
DATAWB-1106:
Example: in $scriptname.$0. illegal format for 4th arg '$optionalargs'. $usage4args
Explanation: Impossible to process the LOG file containing the z/OS FTP unloading information.
DATAWB-1107:
Example: in $scriptname.$0. empty physical file name '$physfilename' in 4th arg '$optionalargs'. $usage4args
Explanation: Impossible to process the LOG file containing the z/OS FTP unloading information.
DATAWB-1108:
Example: in $scriptname.$0. can not found binary transferred file '$binaryTransferredFile' in 4th arg '$optionalargs'. $usage4args
Explanation: Impossible to process the LOG file containing the z/OS FTP unloading information.
DATAWB-1109:
Example: in $0. bad return code for awk reading $mvslogfile. $recfmandreclen
Explanation: Impossible to process the LOG file containing the z/OS FTP unloading information.
DATAWB-1110:
Example: in $0. can not found $physfilename information in ftp report file $mvslogfile
Explanation: Impossible to process the LOG file containing the z/OS FTP unloading information.
DATAWB-1111:
Example: in $scriptname. bad return code for ls or awk reading $mvslogfile. $rows
Explanation: Impossible to process the LOG file containing the z/OS FTP unloading information.
DATAWB-1112:
Example: in $scriptname. can not create output report file $outputreportfile
Explanation: Impossible to process the LOG file containing the z/OS unloading information.
DATAWB-1113:
Example: in $scriptname. Bad mvs log format: $mvsformat.
Explanation: Impossible to process the LOG file containing the z/OS unloading information.
DATAWB-1114:
Example: in $scriptname. internal variable tableAndRows is empty.
Explanation: Impossible to process the LOG file containing the z/OS unloading information.
DATAWB-1115:
Example: in $scriptname. can not create report file $outputreportfile
Explanation: Impossible to process the LOG file containing the z/OS unloading information.
DATAWB-1120:
Example: in ${scriptname}.$0. bad return code for awk reading ${mvslogfile}
Explanation: Impossible to process the LOG file containing the z/OS DSNUPROC unloading information.
DATAWB-1121:
Example: in ${scriptname}.$0. can not found NUMBER OF RECORDS UNLOADED information in SYSPRINT LOG report file ${mvslogfile}
Explanation: Impossible to process the LOG file containing the z/OS DSNUPROC unloading information.
DATAWB-1122:
Example: in $0. bad return code for awk reading $mvslogfile. $recfmandreclen
Explanation: Impossible to process the LOG file containing the z/OS DSNUTILB unloading information.
DATAWB-1122:
Example: in $0. bad return code for awk reading $mvslogfile. $recfmandreclen
Explanation: Impossible to process the LOG file containing the z/OS DSNUTILB unloading information.
DATAWB-1201:
Example: unix variable NLS_LANG not set
Explanation: Check the value of the NLS_LANG variable before relaunching the.execution.
DATAWB-1203:
Example: unix variable MT_DB_USER not set
Explanation: Check the value of the MT_DB_USER variable before relaunching the.execution.
DATAWB-1204:
Example: unix variable MT_DB_PWD not set
Explanation: Check the value of the MT_DB_PWD variable before relaunching the.execution.
DATAWB-1204:
Example: can not found directory $MT_LOG : $MT_LOG
Explanation: Check the value of the MT_LOG variable before relaunching the execution.
DATAWB-1205:
Example: can not found directory $TMPPROJECT : $TMPPROJECT
Explanation: Check the value of the TMPPROJECT variable before relaunching the execution.
DATAWB-1206:
Example: can not find Control File : $ctl. Use -h for help
Explanation: Check the generation step reached by the Rehosting Workbench.
DATAWB-1207:
Example: Bad Parameter: $1
Explanation: Internal error.
DATAWB-1208:
Example: bad Control File. Can not found table name.
Explanation: The *.ctl is not adapted, check its generation.
DATAWB-1209:
Example: Bad argument for parameter: $1
Explanation: this parameter accepts an argument as value after the “:” character.
DATAWB-1210:
Example: can not create log file
Explanation: Check the system messages displayed before this error.
DATAWB-1212:
Example: unix variable MT_DB_LOGIN not set
Explanation: Check the value of the MT_DB_LOGIN variable before relaunching the.execution.
DATAWB-1221:
Example: can not clean this table! Check file $TMPPROJECT/truncate_$table.log
Explanation: The table does not exist or contains integrity constraints.
DATAWB-1222:
Example: Syntax or Oracle Error: Oracle errors are listed bellow
Explanation: __
DATAWB-1223:
Example: can not give how many rows have been inserted into table $table
Explanation: Internal error.
DATAWB-1224:
Example: can not modify current CTL file.
Explanation: Check the system messages displayed before this error.
DATAWB-1241:
Example: can not found report file
Explanation: Check the system messages displayed before this error.
DATAWB-1242:
Example: the report file containing the number of rows to be inserted is missing: $fichierReport
Explanation: The number of records is absent from the LOG of the transcodage program.
DATAWB-1243:
Example: the number of rows inserted into table $table is not equal to the number written in the report file $fichierReport !Oracle $qteOraReport $qteFile
Explanation: __
DATAWB-1299:
Example: an error occurred! Checks also file: $log
Explanation: Check the LOG and the messages displayed before this error.
Reloading Error Messages
The messages in this section are organized by tool. The following tools are documented:
•
RDBMS –DB2-to-Oracle Converter messages
•
DB2-to-Oracle Converter Setup Error Messages:
RDBMSLD-0001:
Example: invalid parameter: $usage
Explanation: Error when entering the arguments for the loadrdbms.sh script
RDBMSLD-0002:
Example: can not create log file $logtab
Explanation: System error.
RDBMSLD-0003:
Example: input file $DD_ENTREE not found Content of log file $logtab is
Explanation: Check the configuration used and the presence of the file unloaded by the DB2 unloading utility.
RDBMSLD-0004:
Example: bad conversion for file $DD_ENTREE
Explanation: Check previous messages.
RDBMSLD-0005:
Example: bad loading for table $table_name
Explanation: Check previous messages.
RDBMSLD-0006:
Example: input file $DD_SORTIE not foundContent of log file $logtab is
Explanation: The file to reload using SQL*LOADER is absent, check preceding messages
RDBMSLD-0007:
Example: variable $var is badly or is not initialized.
Explanation: Check the value of the $var variable before relaunching the.execution.
RDBMSLD-0020:
Example: csv format file does not need transcoding step.
Explanation: Check “rdbms:” parameters in db-param.cfg parameter file or remove -t option.
RDBMSLD-0021:
Example: csv format file does not accept filesystem type.
Explanation: Do not use -f option.
RDBMSLD-0031:
Example: bad filesystem for LOB datatypes. Allowed filesystem types are 'hfs', 'pds' (default).
Explanation: Check if the argument of the -f option is badly set or parameter in db-param.cfg configuration file.
RDBMSLD-0032:
Example: input ${DD_ENTREE_DIR}/${LOBDIR} directory for LOB files does not exist.
Explanation: Check the value of these internal variables and the presence of the directory.
RDBMSLD-0033:
Example: -O argument for LOB datatypes is not allowed for this table.
Explanation: __
RDBMSLD-0034:
Example: -T argument for table with LOB datatypes is not allowed for this table.
Explanation: __
RDBMSLD-0035:
Example: -f argument for LOB datatypes is not allowed for this table.
Explanation: __
RDBMSLD-0036:
Example: can not create LOB directory ${DD_SORTIE_DIR}/${LOBDIR}
Explanation: Check the previous system messages.
RDBMSLD-0037:
Example: can not create sysin file $sysinfile
Explanation: Check the previous system messages.
RDBMSLD-0038:
Example: output ${DD_SORTIE_DIR}/${LOBDIR} directory for LOB files does not exist
Explanation: Check the previous error messages or -O argument of the loadrdbms.sh script has been used without a previously launch with -T or -t argument.
RDBMSLD-0039:
Example: list of clob files name ${DD_%{FLD-1:-T}} does not exist
Explanation: Check the previous error messages or -O argument of the loadrdbms.sh script has been used without a previously launch with -T or -t argument.
RDBMSLD-0040:
Example: list of blob files name ${DD_%{FLD-1:-T}} does not exist
Explanation: Check the previous error messages or -O argument of the loadrdbms.sh script has been used without a previously launch with -T or -t argument.
RDBMSLD-0045:
Example: bad conversion for the clob column %{FLD-1:-T}
Explanation: Check the previous system messages or COBOL program messages.
RDBMSLD-0046:
Example: input file for the blob column %{FLD-1:-T} does not exist
Explanation: Check the configuration used and the presence of the directory.
RDBMSLD-0047:
Example: bad link for the blob column %{FLD-1:-T}
Explanation: Check the previous system messages.
RDBMSLD-0102:
Example: bad method of check. Allowed method is 'rows'$usage
Explanation: Error when entering the -c argument of the loadrdbms.sh script.
RDBMSLD-0104:
Example: can not create a report file for table $table_name
Explanation: System error.
RDBMSLD-0107:
Example: the number of rows written by the transcode process is not equal to the number calculated using the log file (see created report $reportfile) !Transcode $qteTranscodeReport $qteFile
Explanation: __
RDBMSLD-0113:
Example: input file $DD_MVSLOG not found.Content of log file $logtab is
Explanation: The DB2 unloading utility Log created on z/OS is not available.
RDBMSLD-0201:
Example: INPUT ENTREE FAILEDIO-STATUS = IO-STATUS
Explanation: Control the COBOL I/O status.
RDBMSLD-0202:
Example: OUTPUT SORTIE FAILEDIO-STATUS = IO-STATUS
Explanation: Control the COBOL I/O status.
RDBMSLD-0203:
Example: WRITE SORTIE FAILEDIO-STATUS = IO-STATUS
Explanation: Control the COBOL I/O status.
RDBMSLD-0204:
Example: UNABLE TO APPLY DISCRIM RULEINVALID DATA in REC Num D-NB-RECSREDEFINE %SPLIT-1-L
Explanation: The discrimination rule is incorrect; some data cannot be processed by it.
RDBMSLD-0205:
Example: DD_ENTREE_DIR variable not set
Explanation: System error.
RDBMSLD-0206:
Example: DD_SORTIE_DIR variable not set
Explanation: System error.
RDBMSLD-0207:
Example: BAD PARAMETER. MUST BE P OR H
Explanation: System error.
RDBMSLD-0210:
Example: BAD VALUE IN INDICATOR FIELDINDICATOR FIELD %FLD-1-C-IND%INDICESCONTAINS A BAD VALUE (NOT '?', SPACEOR LOW-VALUE)CURRENT BAD VALUE IS [ E-%FLD-1-C-IND%INDICES ]
Explanation: Check the content of the DSNTIAUL file from z/OS.
RDBMSLD-0211:
Example: FIELD %FLD-1:-C%INDICES:NOT NUMERICGroup Zone value is [ X-E-%FLD-1-C%INDICES ]
Explanation: Check the content of the DB2 unloading file from z/OS.
RDBMSLD-0212:
Example: BAD VALUE FOR LOB FIELD <field> LOB ROW FILE NAME IS [ xx ]
Explanation: Format of the LOBS file name written in the unloading DB2 file is not correct. Check HFS or PFS dataset type.
RDBMSLD-0213:
Example: MAX FILE NAME LENGTH IS REACH FOR LOB FIELD <field>LOB ROW FILE NAME IS [ xx ]MAX LENGTH HAS TO BE <max>
Explanation: System error.
RDBMSLD-0214:
Example: TOO MANY DIRECTORIES FOR LOB FIELD <field> LOB ROW FILE NAME IS [ xx ]
Explanation: System error
File Convertor Messages
File Script Error Messages
FILEWB-0001:
Example: $usage
Explanation: Error when entering the arguments of the file.sh command.
FILEWB-0003:
Example: Unix variable TMPPROJECT is not set or contains a bad directory name.
Explanation: Check the value of the TMPPROJECT variable and relaunch the execution.
FILEWB-0004:
Example: Temporary output directory $tempoutputdir is missing.
Explanation: Check the value of the TMPPROJECT variable and relaunch the execution.
FILEWB-0005:
Example: invalid argument: do not use -s argument with -g or -m or -i. $usage
Explanation: Check the arguments passed to the file.sh command and relaunch the execution.
FILEWB-0006:
Example: Target output directory $targetoutputdir is missing. Check parameters: -i <output_directory> <configuration_name>. $usage
Explanation: Check the arguments passed to the file.sh command and relaunch the execution.
FILEWB-0007:
Example: Target output directory $targetoutputdir is missing. Check parameters: -s <output_directory> (<configuration>,...). $usage
Explanation: Check the arguments passed to the file.sh command and relaunch the execution.
FILEWB-0008:
Example: Mandatory argument is list of configuration name (<configuration>,...). $usage
Explanation: The -s option expects an installation directory name and a list of configurations as arguments.
FILEWB-0009:
Example: Mandatory argument is <configuration_name>. $usage
Explanation: The -s option expects an installation directory name and a configuration name as arguments.
FILEWB-0010:
Example: Too many arguments: $2. $usage
Explanation: Check the arguments passed to the file.sh command and relaunch the execution.
FILEWB-0011:
Example: External Variable PARAM is not set!
Explanation: Initialize the PARAM variable.
FILEWB-0021:
Example: can not access to directory $tempoutputdir/Template/$schema.
Explanation: Check the sequence of options used to execute the file.sh command.
FILEWB-0022:
Example: can not access to directory $tempoutputdir.
Explanation: Check the value of the TMPPROJECT variable and relaunch the execution.
FILEWB-0201:
Example: Mapper file $PARAM/file/mapper-$schema.re does not exist !
Explanation: A mapper-<schema name>.re configuration file should be created to execute file.sh.
FILEWB-0202:
Example: Mapper file $PARAM/file/mapper-$schema.re is empty !
Explanation: A mapper-<schema name>.re configuration file should be set to execute file.sh.
FILEWB-0203:
Example: Datamap file $PARAM/file/Datamap-$schema.re does not exist !
Explanation: A mapper-<schema name>.re configuration file should be created to execute file.sh.
FILEWB-0204:
Example: Default Templates list file $defaulttemplatesfile is missing !
Explanation: Check the system errors proceeding this error.
FILEWB-0205:
Example: Can not modify #VAR: strings (in templates list file)
Explanation: Check the system errors proceeding this error.
FILEWB-0206:
Example: Check $templatesfile and $tmptemplatesfile files
Explanation: Check the system errors proceeding this error.
FILEWB-0207:
Example: Mapper file $orimapperfile is missing !
Explanation: Check the system errors proceeding this error.
FILEWB-0208:
Example: Can not modify #VAR: strings (in mapper file)
Explanation: Check the system errors proceeding this error.
FILEWB-0209:
Example: in reading configuration file db-param.cfg. Check previous error messages
Explanation: __
FILEWB-0210:
Example: in treating configuration file db-param.cfg. Bad targetdatabase version in db-param.cfg file (${targetdatabase})
Explanation: __
FILEWB-0241:
Example: unknown sign format for field %FLD-1:-C%INDICES:: %FLD-1:-IBM-DESC / %FLD-1:-MF-DESC
Explanation: Sign format not supported; check the syntax.
FILEWB-0242:
Example: unknown datatype for field %FLD-1:-C%INDICES:: %FLD-1:-IBM-DESC / %FLD-1:-MF-DESC
Explanation: Datatype format not supported, check the COBOL syntax.
FILEWB-0299:
Example: generation aborted. Check previous error messages
Explanation: __
FILEWB-0303:
Example: There was a problem during dynamic modification of components. Check $PARAM/$type_shell/modif-source-$shell_name.sh script
Explanation: the script created to modify the generated components did not end normally: check the script and relaunch the execution.
FILEWB-0304:
Example: There was a problem during modification. Check previous message
Explanation: Check the errors preceding this error.
FILEWB-0305:
Example: problem in modifying $ext files
Explanation: Check the system errors preceding this error.
FILEWB-0306:
Example: problem during chmod of shell $file
Explanation: Check the system errors preceding this error.
FILEWB-0307:
Example: problem in accessing *sh files
Explanation: Check the system errors preceding this error.
FILEWB-0501:
Example: installation aborted. Check previous message.
Explanation: __
FILEWB-0601:
Example: configuration file generation aborted. Check previous error messages
Explanation: __
File Internally Called Script Messages
DATAWB-1001:
Example: File $template is missing!
Explanation: Oracle Tuxedo Application Rehosting Workbench working environment is not correctly installed.
DATAWB-1002:
Example: Missing Template file: $file or his pob version
Explanation: Installation problem or modification error for the *templates.txt file.
DATAWB-1003:
Example: Remove the pob extension to file name $file
Explanation: Installation problem or modification error for the *templates.txt file.
DATAWB-1011:
Example: missing file name arg1
Explanation: Internal error, the Rehosting Workbench working environment is incorrectly installed or wrongly configured.
DATAWB-1012:
Example: bad return code for awk
Explanation: Check the preceding system messages.
DATAWB-1013:
Example: There was a problem during updating component $fixedfile
Explanation: Check the preceding system messages.
DATAWB-1014:
Example: There was a problem during comparing component $file
Explanation: Check the preceding system messages.
DATAWB-1021:
Example: Bad 1st parameter. <InputFile> <OutputFile>
Explanation: Check the preceding system messages.
DATAWB-1022:
Example: Bad 2nd parameter. <InputFile> <OutputFile>
Explanation: Internal error, the Rehosting Workbench working environment is incorrectly installed or wrongly configured.
DATAWB-1023:
Example: sed script return a bad return code
Explanation: Check the preceding system messages.
DATAWB-1031:
Example: can not access to directory Template/$schema.
Explanation: Internal error, the Rehosting Workbench working environment is incorrectly installed or wrongly configured.
DATAWB-1032:
Example: can not found $movefile file
Explanation: Internal error, the Rehosting Workbench working environment is incorrectly installed or wrongly configured.
DATAWB-1033:
Example: can not read $movefile file
Explanation: Internal error, the Rehosting Workbench working environment is incorrectly installed or wrongly configured.
DATAWB-1034:
Example: Version $relformat in $movefile is not supported by this tool.
Explanation: Internal error, the Rehosting Workbench working environment is incorrectly installed or wrongly configured.
DATAWB-1035:
Example: can not evaluate string [$line] from $movefile
Explanation: Internal error, the Rehosting Workbench working environment is incorrectly installed or wrongly configured.
DATAWB-1036:
Example: bad 1st argument typ in line $line
Explanation: Internal error, the Rehosting Workbench working environment is incorrectly installed or wrongly configured.
DATAWB-1037:
Example: bad 2nd argument source_directory in line $line
Explanation: Internal error, the Rehosting Workbench working environment is incorrectly installed or wrongly configured.
DATAWB-1038:
Example: $info_filename is missing or empty (in <td>/$inputfile)
Explanation: Internal error, the Rehosting Workbench working environment is incorrectly installed or wrongly configured.
DATAWB-1039:
Example: $info_filename: problem when creating directory $targetdirectory for $outputfile
Explanation: Check the preceding system messages.
DATAWB-1040:
Example: $info_filename: problem during a copy $inputfile to $outputfile in line $line
Explanation: Check the preceding system messages.
DATAWB-1041:
Example: $info_filename: can not chmod executable $outputfile
Explanation: Check the preceding system messages.
DATAWB-1042:
Example: $info_filename: can not chmod non executable script $inputfile
Explanation: Check the preceding system messages.
DATAWB-1043:
Example: bad return code when executing $inputfile
Explanation: Check the preceding system messages.
DATAWB-1051:
Example: can not access to directory Template/$schema. Separator character between each schema name has to be a coma ','.
Explanation: Internal error, the Rehosting Workbench working environment is incorrectly installed or wrongly configured.
DATAWB-1052:
Example: can not grep $movefile file
Explanation: Internal error, the Rehosting Workbench working environment is incorrectly installed or wrongly configured.
DATAWB-1053:
Example: content of file $movefileori are not equal for tag 'M:s:'
Explanation: Internal error, the Rehosting Workbench working environment is incorrectly installed or wrongly configured.
DATAWB-1054:
Example: can not find generated file $filetoinclude
Explanation: Internal error, the Rehosting Workbench working environment is incorrectly installed or wrongly configured.
DATAWB-1055:
Example: can not modify a file
Explanation: Check the preceding system messages.
DATAWB-1056:
Example: can not generate $outputfile using perl program
Explanation: Check the preceding system messages.
DATAWB-1057:
Example: $info_filename: can not chmod a temporary file $tmpfilemc in line $line
Explanation: Check the preceding system messages.
DATAWB-1061:
Example: Bad parameters: file|rdbms <configfile> <OutputFile>
Explanation: Check the preceding system messages.
DATAWB-1062:
Example: Configuration file $configfile is missing!
Explanation: Check the preceding system messages.
DATAWB-1063:
Example: Can not create temporary parameter file $outputfile
Explanation: Check the preceding system messages.
DATAWB-1064:
Example: Can not insert a line into the temporary parameter file $outputfile
Explanation: Check the preceding system messages.
DATAWB-1065:
Example: Bad 1st parameter. file|rdbms <configfile> <OutputFile>
Explanation: Check the preceding system messages.
DATAWB-1101:
Example: usage is $scriptname <format_log> <mvslog_filename> <output_report_filename>
Explanation: Impossible to process the LOG file containing the information unloaded from z/OS.
DATAWB-1102:
Example: in $scriptname. Input mvs log file is missing $mvslogfile.
Explanation: Impossible to process the LOG file containing the information unloaded from z/OS.
DATAWB-1103:
Example: in $scriptname.$0. bad return code for awk reading $mvslogfile
Explanation: Impossible to process the LOG file containing the information unloaded from z/OS.
DATAWB-1104:
Example: in $scriptname.$0. can not found SUCCESSFUL UNLOAD x ROWS information in SYSPRINT LOG report file $mvslogfile
Explanation: Impossible to process the LOG file containing the information unloaded from z/OS.
DATAWB-1105:
Example: in $scriptname.$0. empty 4th arg. $usage4args
Explanation: Impossible to process the LOG file containing the information unloaded from z/OS.
DATAWB-1106:
Example: in $scriptname.$0. illegal format for 4th arg '$optionalargs'. $usage4args
Explanation: Impossible to process the LOG file containing the information unloaded from z/OS.
DATAWB-1107:
Example: in $scriptname.$0. empty physical file name '$physfilename' in 4th arg '$optionalargs'. $usage4args
Explanation: Impossible to process the LOG file containing the information unloaded from z/OS.
DATAWB-1108:
Example: in $scriptname.$0. can not found binary transferred file $binaryTransferredFile' in 4th arg '$optionalargs'. $usage4args
Explanation: Impossible to process the LOG file containing the information unloaded from z/OS.
DATAWB-1109:
Example: in $0. bad return code for awk reading $mvslogfile. $recfmandreclen
Explanation: Impossible to process the LOG file containing the information unloaded from z/OS.
DATAWB-1110:
Example: in $0. can not found $physfilename information in ftp report file $mvslogfile
Explanation: Impossible to process the LOG file containing the information unloaded from z/OS.
DATAWB-1111:
Example: in $scriptname. bad return code for ls or awk reading $mvslogfile. $rows
Explanation: Impossible to process the LOG file containing the information unloaded from z/OS.
DATAWB-1112:
Example: in $scriptname. can not create output report file $outputreportfile
Explanation: Impossible to process the LOG file containing the information unloaded from z/OS.
DATAWB-1113:
Example: in $scriptname. Bad mvs log format: $mvsformat.
Explanation: Impossible to process the LOG file containing the information unloaded from z/OS.
DATAWB-1114:
Example: in $scriptname. internal variable tableAndRows is empty.
Explanation: Impossible to process the LOG file containing the information unloaded from z/OS.
DATAWB-1115:
Example: in $scriptname. can not create report file $outputreportfile
Explanation: Impossible to process the LOG file containing the information unloaded from z/OS.
DATAWB-1201:
Example: unix variable NLS_LANG not set
Explanation: Check the value of the NLS_LANG variable before relaunching the execution.
DATAWB-1202:
Example: unix variable MT_DB_USER not set
Explanation: Check the value of the MT_DB_USER variable before relaunching the execution.
DATAWB-1203:
Example: unix variable MT_DB_PWD not set
Explanation: Check the value of the MT_DB_PWD variable before relaunching the execution.
DATAWB-1204:
Example: can not found directory $MT_LOG: $MT_LOG
Explanation: Check the value of the MT_LOG variable before relaunching the execution.
DATAWB-1205:
Example: can not found directory $TMPPROJECT : $TMPPROJECT
Explanation: Check the value of the TMPPROJECT variable before relaunching the execution.
DATAWB-1206:
Example: can not found Control File : $ctl. Use -h for help
Explanation: Check the generation step reached by the Rehosting Workbench.
DATAWB-1207:
Example: Bad Parameter: $1
Explanation: Internal error.
DATAWB-1208:
Example: bad Control File. Can not found table name.
Explanation: The *.ctl file is not adapted, check the generation.
DATAWB-1210:
Example: can not create log file
Explanation: Check the system errors preceding this error.
DATAWB-1212:
Example: unix variable MT_DB_LOGIN not set
Explanation: Check the value of the MT_DB_LOGIN variable before relaunching the execution.
DATAWB-1221:
Example: can not clean this table! Check file $TMPPROJECT/truncate_$table.log
Explanation: The table does not exit or there are integrity constraints.
DATAWB-1222:
Example: Syntax or Oracle Error:Oracle errors are listed bellow
Explanation: __
DATAWB-1223:
Example: can not give how many rows have been inserted into table $table
Explanation: Internal error.
DATAWB-1241:
Example: can not found report file
Explanation: Check the system errors preceding this error.
DATAWB-1242:
Example: the report file containing the number of rows to be inserted is missing: $fichierReport
Explanation: The number of records is absent from the LOG of the transcoding program.
DATAWB-1243:
Example: the number of rows inserted into table $table is not equal to the number written in the report file $fichierReport !Oracle $qteOraReport $qteFile
Explanation: __
DATAWB-1299:
Example: an error occurred! Checks also file: $log
Explanation: Check the LOG and the messages displayed before this error.
Reloading Error Messages
FILELD-0001:
Example: invalid parameter: $usage
Explanation: Error when inputting the arguments for the loadfile or loadtable scripts.
FILELD-0002:
Example: can not create log file $logfile
Explanation: System error. - Check the preceding messages.
FILELD-0003:
Example: input file $DD_ENTREE not found Content of log file $logfile is
Explanation: Transferred file is missing or the DD_ENTREE variable is wrongly initialized.
FILELD-0004:
Example: file $DD_ENTREE is not reloadedContent of log file $logfile is
Explanation: __
FILELD-0005:
Example: input variable DD_ENTREE must be set
Explanation: Installation problem. - Check the use of the loadgdg script.
FILELD-0006:
Example: input variable DD_SORTIE must be set
Explanation: Installation problem. - Check the use of the loadgdg script.
FILELD-0007:
Example: input variable DD_GENEID must be set
Explanation: Installation problem. - Check the use of the loadgdg script.
FILELD-0008:
Example: can not create temporary file $tmpfile.list
Explanation: System error. - Check the proceeding messages.
FILELD-0009:
Example: GDS file ($geneid) is missing and it already exists a previous GDS file.
Explanation: Files, members of a GDG, are missing.
FILELD-0010:
Example: Content of log file $tmpfile.loadgds is :See message above.
Explanation: Error when executing loadgds.
FILELD-0011:
Example: problem with sort of $tmpfile.list
Explanation: System error. - Check the preceding messages.
FILELD-0012:
Example: none GDS file are converted. (LIMIT is %LIMIT-GDG:)
Explanation: __
FILELD-0013:
Example: can not create temporary script $tmpfile.ksh
Explanation: System error. - Check the preceding messages.
FILELD-0014:
Example: transcoded GDS file ($geneid) is missing and it already exists a previous GDS file.
Explanation: Transcoded files, members of a GDG, are missing.
FILELD-0015:
Example: can not modify temporary script $tmpfile.ksh
Explanation: System error. - Check the preceding messages.
FILELD-0016:
Example: none GDS file are prepared. (LIMIT is %LIMIT-GDG:)
Explanation: The loadgdg script was launched with the -l option and the -t option has not executed correctly.
FILELD-0017:
Example: can not add final line in temporary file $tmpfile.ksh
Explanation: System error. - Check the preceding messages.
FILELD-0018:
Example: can not chmod temporary script $tmpfile.ksh
Explanation: System error. - Check the preceding messages.
FILELD-0019:
Example: can not create GDG file using RT BATCH EJR utility.
Explanation: Check preceding messages (See the Oracle Tuxedo Application Runtime for Batch Reference Guide).
FILELD-0101:
Example: bad sub parameters '$OPTARG%%:*' for method ftpParameter has to be 'ftp<physical_name_in_ftplogfile><ftplog_file>'$usage
Explanation: Check the arguments of the -c option.
FILELD-0102:
Example: bad method '$methodofcheck' of check. Allowed method is 'ftp'$usage
Explanation: Check the configuration of the loadfile script. Then relaunch the execution.
FILELD-0103:
Example: input file $DD_MVSLOG not found. Check parameter -c.Content of log file $logfile is
Explanation: Impossible to process the LOG file containing the information unloaded from z/OS.
FILELD-0104:
Example: can not create a report file for $DD_ENTREE
Explanation: System error. - Check the preceding messages.
FILELD-0105:
Example: awk return a bad return code when analyzing logfileContent of log file $logfile is
Explanation: System error. - Check the preceding messages.
FILELD-0106:
Example: the number of rows written in file $DD_SORTIE is not equal to the number calculated using the log file (see created report $reportfile) !Report $recstransferred
Explanation: __
FILELD-0111:
Example: bad sub parameters '$OPTARG%%:*' for method ftpParameter has to be 'ftp<begin_physical_name_in_ftplogfile><ftplog_file>'$usage
Explanation: Check the arguments of the -c option specific to the case of GDGs.
FILELD-0151:
Example: missing or empty DDL file $ddlfileContent of log file $logfile is
Explanation: Check the content of the $DDL variable.
FILELD-0152:
Example: can not create <RDBMS> DDL using $ddlfile file
Explanation: Check the RDBMS error messages and the values of the associated variables.
FILELD-0153:
Example: %FILE-1:-L. File $DD_ENTREE not reloaded into RDBMS. Content of log file $logfile is
Explanation: __
FILELD-0154:
Example: can not connect to db2 using MT_DB_DBNAME unix variable
Explanation: Check the RDBMS error messages and the values of the associated variables.
FILELD-0155:
Example: can not execute a 'connect reset' db2 statement
Explanation: Check the RDBMS error messages.
FILELD-0156:
Example: can not execute a 'terminate' db2 statement
Explanation: Check the RDBMS error messages.
FILELD-0201:
Example: OPEN INPUT %FILE-1:-CONVERTER-NAME FAILEDASSIGN ENTREEIO-STATUS = IO-STATUS
Explanation: Check the COBOL I/O status.
FILELD-0202:
Example: OUTPUT %FILE-1:-CONVERTER-NAME FAILEDASSIGN SORTIEIO-STATUS = IO-STATUS
Explanation: Check the COBOL I/O status.
FILELD-0203:
Example: WRITE %FILE-1:-CONVERTER-NAME FAILEDASSIGN SORTIEIO-STATUS = IO-STATUS
Explanation: Check the COBOL I/O status.
FILELD-0204:
Example: UNABLE TO APPLY DISCRIM RULEINVALID DATA in REC Num D-NB-RECSREDEFINE %SPLIT-1-L
Explanation: The discrimination rule is not correct, some data cannot be processed by this rule.
FILELD-0205:
Example: INSERT %FILE-1:-L FAILEDIO-STATUS = IO-STATUS
Explanation: Check the preceding error message and the RDBMS SQL code.
FILELD-0206:
Example: UNABLE TO GET A NEXTVAL FROM :%TABLE-1-SEQ-NUM-SEQUENCE-TSQLCODE= SQLCODE
Explanation: Check the RDBMS SQL code.
FILELD-0207:
Example: INSERT INTO %TABLE-1:SQLCODE= SQLCODESQLERRMC= SQLERRMC(1SQLERRML)MW-SORTIE-REC
Explanation: Check the RDBMS SQL code.
FILELD-0209:
Example: BAD CREATING SEQUENCE:%TABLE-1-SEQ-NUM-SEQUENCE-TSQLCODE= SQLCODESQLERRMC= SQLERRMC(1SQLERRML)
Explanation: Check the RDBMS SQL code.
JCL Translator Messages
JCL Translator Error Messages
When the translator encounters uses of utility programs which are only partially supported, it may produce error messages of the form: #{keyword} utility [optional sub parameter].
Message: Not yet translated.
Example: No yet translated ICETOOL with SELECT
Explanation: Operation or command SELECT of utility program ICETOOL will not be translated, because the translation is not yet implemented.
Message: Untranslated
Example: Untranslated IEBGENER, GENERATE with MEMBER
Explanation: Operation or command GENERATE with MEMBER of utility program IEBGENER will not be translated, because the translator does not know how to reproduce the original behavior with the information available to it. Use post-translation facilities to implement the required behavior.
Message: Ignored
Example: Ignored ICETOOL with OCCUR
Explanation: Operation or command OCCUR of utility program ICETOOL will not be translated, because there is no need for it on the target platform.
JCL Translator Log Errors
Message: Configuration file is absent or inaccessible
Error: The file #P"../param/system.desc" does not exist.
ERROR*: Parse-Whole-File: file /param/file-in-tabler.txt not found!
Message: Syntax error in the system description file
Parsing system file : ../param/system.desc
Parse error at character position nnn in file:
…
While parsing in grammar CATALOG::SYSTEM-GRAMMAR,
Message: Syntax error in the translator configuration file
Parsing config file : ../param/config-trad-JCL.desc
Parse error at character position nnn in file:
…
While parsing in grammar JCLZ::CONFIG
Message: Impossible to find the POB file for the component to translate
*FATAL INTERNAL ERROR*:
Can't find POB file
/JCL/pob/BPRAJ001.jcl.pob; please re-catalog the system.
Message: The JCL source file is more recent than the POB file
*FATAL INTERNAL ERROR*:
POB /JCL/pob/BPRAJ001.jcl.pob is less recent
than source file /JCL/BPRAJ001.jcl; please re-catalog the system.
 

Copyright © 1994, 2017, Oracle and/or its affiliates. All rights reserved.