| Message ID | Message Text | Description | Resolution | Phase of Reference |
|---|---|---|---|---|
| WRC0201 | The field must be set to space. | During the mask editing of "Creation Delete Define Sources" Job from toolkit, there are one or more full fields. | Verify the full field and add spaces to it. | Toolkit's programs |
| WRC0202 | There is not enough information in the process identifier to retrieve the segment record lengths. | The process identifier found that the DL/I file does not contain all the information required to load the DL/I file correctly. | Use the Work with Process IDs window to make sure the process identifier you want to use contains all the information required to process the DL/I file typology. | File loading |
| WRC0203 | An error occurred during the analysis of SYSPUNCH SYSPUNCH-Name. | An error during the analysis of the specified SYSPUNCH has occurred. | Check the SYSPUNCH source to ensure the correct SYSPUNCH is entered for the DB2 table you want to load. If the error persists, contact Micro Focus Product Support for technical assistance. | File loading |
| WRC0205 | The INTO clause was not found in SYSPUNCH SYSPUNCH-Name. | The INTO clause for the specified SYSPUNCH cannot be found during the end of the loading phase for a DB2 table through an access to the sequential unload. | Check the SYSPUNCH source to verify the lack of the INTO clause. If necessary, contact Micro Focus Product Support for technical assistance. | File loading |
| WRC0206 | A variable length field was found as the last column for SYSPUNCH SYSPUNCH-Name. Check the table record length. | A VARCHAR in the last column for the specified SYSPUNCH has been identified at the end of the loading phase of a DB2 file through an access to the sequential unload. This field will be loaded with a length of 256. | File Loading | |
| WRC0207 | More than 1500 columns were found for SYSPUNCH SYSPUNCH-Name. | More than 1500 columns are identified for the specified SYSPUNCH at the end of the DB2 table loading phase through an access to the sequential unload. A SYSPUNCH exceeding 1500 columns cannot be processed. | File loading | |
| WRC0213 | An error occurred during the analysis of copybook CopybookName. | A problem with the search for keywords during the analysis of copybook/include statements has occurred. | If they do not, contact Micro Focus Product Support for technical assistance. | |
| WRC0214 | A nested copybook was found in CopybookName. Data Manager is not able to process nested copybooks. | Nested copybooks (or copybooks that cannot be processed) have been identified. | Nested copybooks are not generally used to describe the layout of a file, so the message can likely be ignored. Should the copybook describe a file layout, it would be necessary to turn the nested copybook into a simple copybook. | Copybook, include analysis |
| WRC0215 | More than 32767 rows were found in copybook CopybookName. The analysis will be terminated. | The presence of more than 32767 rows for the specified copybook have been identified. The product cannot process copybooks containing such a large number of rows. | This type of copybook is not generally used to describe the layout of a file, so the message can likely be ignored. Should the copybook describe a file layout, it would be necessary to split up the copybook. | Copybook, include analysis |
| WRC0216 | The copybook name CopybookName is not valid as a file description. | The message is a warning explaining that the analyzed copybook is not compatible with the description of a file layout. To show the description of a file, the copybook must be a working copybook; that is, one that contains definitions of fields. | Copybook analysis | |
| WRC0217 | No word could be found in string StringName . | Unexpected syntax in the copybook has been identified. This does not normally occur with copybooks describing file layouts. | If the copybook describes a file layout, make sure the generated fields correspond to the actual conditions of the file. If the generated fields do not correspond to the true conditions of the file, the recommended workaround is the creation of a simplified copy of the copybook with field statements only. | Copybook, include analysis |
| WRC0218 | The first word of string StringName is longer than expected. | Unexpected syntax in the copybook has been identified. This does not normally occur with copybooks describing file layouts. | If the copybook describes a file layout, make sure the generated fields correspond to the actual conditions of the file. If the generated fields do not correspond to the true conditions of the file, the recommended workaround is the creation of a simplified copy of the copybook with field statements only. | Copybook, include analysis |
| WRC0219 | Internal error processing string StringName . | A general problem has been found with the search for keywords within the copybook/include analysis. |
Make sure the generated fields correspond to the actual conditions of the file. Otherwise, contact Micro Focus Product Support for technical assistance. |
Copybook, include analysis |
| WRC0220 | A length greater than 32767 was found for an elementary field in copybook StringName . The length 32767 will be assumed. | An elementary field longer than 32767 bytes for the specified copybook has been identified. As a result, the product will store a 32767-byte long field ignoring the rest. | This message can be ignored. | Copybook, include analysis |
| WRC0221 | Level 66 has been found in copybook CopybookName and will be ignored. | A 66 level field in the specified copybook has been identified. These fields will be ignored. |
This message can be ignored. |
Copybook, include analysis |
| WRC0222 | More than 99999 fields have been found in copybook CopybookName. Fields beyond 99999 will be ignored. | More than 99999 fields in have been identified. As a result, the product will store the first 99999 fields and ignore all the others. | Make sure the generated fields correspond to the effective conditions of the file. | Copybook, include analysis |
| WRC0223 | An undefined field FieldName was found in copybook CopybookName. | The definition of the field referenced in the specified copybook has not been found. This generally occurs when the REDEFINES clause references an invalid field. |
Make sure the generated fields correspond to the actual conditions of the file. |
Copybook, include analysis |
| WRC0224 | Multiple occurrences of field FieldName have been found in copybook CopybookName. | A field has been defined several times in the specified copybook. This generally happens as a result of an unexpected COBOL syntax. |
Make sure the generated fields correspond to the actual conditions of the file. |
Copybook, include analysis |
| WRC0225 | Field FieldName of I/O area I/O-Area-Name could not be divided because the I/O area contains the OCCURS clause. | The product cannot divide a field of the specified I/O area because the I/O area contains the OCCURS clause. |
Make sure the generated fields correspond to the actual conditions of the file. |
Copybook, include analysis |
| WRC0226 | The maximum number of incongruent formats for I/O area I/O-Area-Name has been reached. Field definition splitting is skipped. | While analyzing the specified I/O area, a number of incongruent formats exceeding the specified value Maximum Progressive of I/O Area have been identified. As a result, separate I/O areas for each incongruent format are not created. This happens when an I/O Area with several REDEFINES clauses is found. | Copybook, include analysis | |
| WRC0227 | No copybook was found to analyze specified parameters. | No copybook has been found for the specified launch parameters. | Make sure the copybooks you want to analyze have been loaded into the environment with the Work with Copybook function and that the launch parameters specified for the copybook analysis are correct. | Copybook analysis phase |
| WRC0228 | Error found in I/O operation on data set Data-Set-Name - File status: FileStatus. | An error in an I/O operation has occurred during batch processing. | Verify the availability of the specified data set. If the error persists, contact Micro Focus Product Support for technical assistance. | |
| WRC0230 | Direct access to the DL/I file is not allowed for file analysis. | Direct access for file analysis was attempted, but is not allowed for the loading and analysis phases. | Modify the launch parameter and relaunch the file analysis. | File loading |
| WRC0231 | More than 99 DL/I segments were found. Additional segments will not be handled. | More than 99 segments for the DL/I file have been found. The product does not handle DL/I files with such a large number of segments. | DL/I analysis | |
| WRC0240 | The file type FileType is unknown. | An error message occurred as a result of a data check on the data entered. The specified file type is unknown to the system. | Make sure you have entered the correct file typology. Correct values for file type are described in the Data Model Guide. | |
| WRC0242 | The file name Filename is not correct for file type FileType. | The file name has not been correctly specified. | Make sure the file used for the import contains the values required for each file type. In particular, make sure the FILENAME field contains the file name for DB2 files, the segment name for DL/I files, and the data set name for GDG or VSAM sequential files. Then, relaunch the import phase. Correct syntax for file name is described in the Data Model Guide. | File loading |
| WRC0247 | No tables found with matching input criteria. | The data store name included in the Input file for the execution of "Load Sequential File" Job is invalid. | Verify the correct name of the data store. | Load Sequential File from toolkit |
| WRC0248 | The table TableName cannot be accessed. SQLCODE SQL-Code. | Direct access to a table was attempted but refused due to the table being locked. | Check whether there are jobs locking the table. | |
| WRC0249 | Burldb4 - unrecognized, SQL type: SQL-Type. | A problem has been found with the direct access to the table due to the presence of an unrecognized type of column. | If necessary, contact Micro Focus Product Support for technical assistance. | |
| WRC0259 | Found and discarded preprocessor statement PreprocessorStatement. | Statements have been found that are related to preprocessors inside the copybook. These instructions are ignored. | Copybook analysis | |
| WRC0260 | Error found processing source SourceName. | A general message has been generated due to a problem with the search for keywords within the copybook analysis. This does not generally occur with copybooks. |
Make sure the generated fields correspond to the actual conditions of the file. Otherwise, contact Micro Focus Product Support for technical assistance. |
Include analysis |
| WRC0261 | Error found in analysis of the include IncludeName. | A general message has been generated due to a problem with the search for keywords within the copybook analysis. This does not generally occur with copybooks. |
Make sure the generated fields correspond to the actual conditions of the file. Otherwise, contact Micro Focus Product Support for technical assistance. |
Include analysis |
| WRC0262 | A nested include in IncludeName was found and discarded. | A nested include (which is a type of include that cannot be processed) has been found. | Nested includes are not generally used to describe a file layout so the message can be ignored. Should the include describe a file layout, it would be necessary to turn a nested include into a simple include. | Include analysis |
| WRC0263 | More than 32767 rows were found in include IncludeName. The analysis will be terminated. | More than 32767 rows for the specified include have been found, and cannot process the sources. | This message can be ignored. Should the include describe a file layout, it would be necessary to split the include up. | Include analysis |
| WRC0264 | The include IncludeName is not valid for a file description. | The message is a warning explaining that the analyzed include is not compatible with the description of a file layout. To show the description of a file, the include must contain field definitions. | Include analysis | |
| WRC0265 | Data items with external attributes have been found in include IncludeName. | External attributes (PL/I concept) that are not handled have been found. This does not generally occur with file includes. |
Make sure the generated fields correspond to the actual conditions of the file. Otherwise, contact Micro Focus Product Support for technical assistance. |
Include analysis |
| WRC0266 | Nested factoring in include IncludeName was found and discarded. | Nested factoring (PL/I concept) that is not handled has been found. This does not generally occur with copybooks. |
Make sure the generated fields correspond to the actual conditions of the file. Otherwise, contact Micro Focus Product Support for technical assistance. |
Include analysis |
| WRC0270 | The DBD direct-access request was discarded. Processing for DatabaseName must be through sequential unload. | An error has occurred as a result of the launch of phases for DL/I files. The direct access is set for these files, but these phases only support the processing of DL/I files through sequential unload. The product will not process these DL/I files. | Change the process identifier as direct access is not supported for DL/I files. | |
| WRC0277 | Unexpected syntax was found in statement StatementName of include IncludeName. | Unexpected syntax in the specified include has been found. | Should the copybook/include describe a file layout, make sure the generated fields correspond to the actual conditions of the file. If the generated fields do not correspond to the actual conditions of the file, the recommended workaround is creating a simplified copy of the copybook/include with field statements only. | |
| WRC0278 | A defined data item was found inside a structure in include IncludeName. | Unexpected syntax in the specified include has been found. |
Make sure the generated fields correspond to the actual conditions of the file. After an incorrect generation of fields, the recommended workaround is creating a simplified copy of the include with field statements only. |
Include analysis |
| WRC0279 | An unhandled data item or token was found in include IncludeName at line LineNumber. | Unexpected syntax in the specified include has been found. |
Make sure the generated fields correspond to the actual conditions of the file. After an incorrect generation of fields, the recommended workaround is creating a simplified copy of the include with field statements only. |
Include analysis |
| WRC0280 | x OCCURS clauses were found for field FileName in copybook CopybookName. x OCCURS clauses assumed. | During analysis of the specified copybook, the number of OCCURS clauses in fields exceeded the limit Data Manager can handle. Therefore, a set number of OCCURS clauses are assumed and the remaining ones have been ignored. The maximum number of handled OCCURS clauses is 256. | Copybook, include analysis | |
| WRC0281 | Too many end statements were found in include IncludeName. | An unexpected END instruction has been found. | This message can be ignored. | Include analysis |
| WRC0282 | An error occurred during the parsing of include IncludeName. | A nested include (an include inside another include) with some unrecognized syntax has been found. |
Make sure the generated fields correspond to the actual conditions of the file. Otherwise, contact Micro Focus Product Support for technical assistance. |
Include analysis |
| WRC0283 | x OCCURS clauses were found for field FieldName in include IncludeName. x OCCURS clauses assumed. | During the analysis of the specified include, the product has found a number of OCCURS clauses that exceeds the limit handled by the product. Therefore, a number of OCCURS clauses have been assumed and the remaining ones have been ignored The maximum number of handled OCCURS clauses is 256. | Copybook, include analysis | |
| WRC0286 | The I/O area I/O-AreaName has already been defined in a procedure in include IncludeName.The request was discarded. | Unexpected syntax in the specified include has been found. |
Make sure the generated fields correspond to the actual conditions of the file. After an incorrect generation of fields, the recommended workaround is creating a simplified copy of the include with field statements only. |
Include analysis |
| WRC0287 | The open I/O area I/O-Area-Name was found in include IncludeName. | Unexpected syntax in the specified include has been found. |
Make sure the generated fields correspond to the actual conditions of the file. . In case incorrect fields are generated, the recommended workaround is creating a simplified copy of the include with field statements only. |
Include analysis |
| WRC0288 | The Copybook-Library-Name, CopybookName was discarded. | An error message occurred at the end of the copybook loading phase (JCL statement containing the VSAM file definitions) because the specified copybook/source of the indicated type has not been loaded in the product repository as it was not recognized. This message is generated only if the Load only Handled Languages option is selected when the phase is launched. In general, unrecognized copybooks or sources are discarded because they are not useful to the processing operations. | Force recognition, copybook loading | |
| WRC0289 | The copybook CopybookName was already loaded in the data repository. The request was discarded. | The specified copybook has already been loaded in the product repository. | If you want to load a different version of the copybook, remove first the previous version of the file by selecting the Delete function in the Work with Copybooks window. | Copybook loading |
| WRC0294 | Decimal columns were found for table TableName. Check the number of integer and decimal digits. | A message has occurred during the DB2 table loading phase through sequential unload with specification of the SYSPUNCH, which explains that columns have been defined as DECIMAL. Information on the number of integers and decimals in these columns from the SYSYPUNCH cannot be retrieved, so all digits specified in the columns are loaded as integers. | If the DECIMAL columns do not contain decimals, the message can be ignored. Otherwise, to display fields with the correct separation between integer and decimal digits, you must load the table again replacing the SYSPUNCH with the table DCLGEN. | Table loading |