JP2006003978A - Conversion error record recovery program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a conversion error record recovery program that allows easily performing a process for recovering error data without interrupting a data conversion process. <P>SOLUTION: The conversion error record recovery program includes a code conversion step for subjecting an input file 10 to code conversion according to a code conversion table, an error record output step for outputting error record information that does not correspond to the code conversion table to an error logging file 30, and an error data code conversion step for reading and subjecting the error logging file 30 to code conversion according to the corrected code conversion table, so that the program can easily perform a process for recovering error data by use of the error logging file 30 without interrupting the code conversion process. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to the distribution of data having different data code systems between computer systems and the like, and the change of data attributes, and more particularly to a code conversion error record recovery program that performs recovery processing for conversion errors.

  Conventionally, when code conversion processing is performed, for example, to convert shift JIS code data stored in an input file into EUC code data and store it in an output file, conversion from shift JIS code to EUC code Using the table, each record of the input file is code-converted. If there is a record that cannot be code-converted, an error message is output to the user who has performed the code conversion and notified. After that, the user identifies the record in error by the code conversion error message, retrieves the record from the input file of the code conversion process, and removes the cause of the code conversion error in the environment of the code conversion process. The code conversion error was recovered by re-executing the code conversion processing of the record.

  Also, in the case of data attribute change, for example, when character attribute data (□□ 100, □: indicates a blank) is changed to numeric attribute data (00100), the blank (□□) is not a numerical value. An invalid data error occurs. For recovery of invalid data error, the error record is identified from the input file based on the error message in the same way as for the code conversion error, the error part of the record is changed (blank is changed to a numerical value, etc.) The record was being recovered.

  Here, FIG. 13 is a block diagram of a conventional format conversion apparatus (data conversion apparatus) that converts existing data created by another system into a form that can be used by the own system, and FIG. 14 is a process flowchart. Show and explain.

  As shown in FIG. 13, a conventional format conversion apparatus includes a format conversion processing unit 105, conversion source data 101, conversion method parameter file 102, conversion destination data 103, and alarm log file 104 connected to the format conversion processing unit 105. And a plurality of external conversion processing modules 106.

  Here, the conversion source data 101 is data created by another system. The conversion method parameter file 102 is a conversion method parameter file describing a conversion method and the like. The conversion destination data 103 is data used in the own system. The alarm log file 104 is a file for storing the result when invalid data is found in the conversion source data 101. The format conversion processing unit 105 is a format conversion processing unit that performs format conversion of the conversion source data 101. The external conversion processing module 106 is an external conversion processing module group that is called when performing conversion processing that cannot be processed inside the format conversion unit 105.

  As shown in FIG. 14, in the conventional format conversion apparatus, first, in step 201, the format conversion processing unit 105 reads the conversion method parameter file 102 and stores it inside. In step 202, a loop is started for the number of data items of the conversion source data 101. Next, in step 203, one conversion source data 101 is read, and in step 204, a loop is started for the number of conversion methods specified in the conversion method parameter file 102. In step 205, it is checked whether the data specified by the conversion source data input order is the data specified by the data format and the number of digits. In step 206, the check result is determined. If it is determined that the data is invalid, alarm data is written in the alarm log file 104 as error processing in step 207. At this time, if the conversion source data input order, the data format, and the number of digits are not designated, it is determined that the data is normal without checking, and the processing is continued.

  Thereafter, if it is determined in step 206 that the data is normal, the process proceeds to step 208, where it is determined whether the conversion process can be performed by the internal process from the format conversion method or whether the external conversion process module group 106 needs to be called. . When it is determined that conversion processing can be performed by internal processing, format conversion is performed by internal processing, and when it is determined that it is necessary to call the external conversion processing module 106, the external conversion processing module 106 to be called from the format conversion method. And an appropriate external conversion processing module 106 is called to perform format conversion processing.

Thereafter, the format conversion processing from step 204 to step 212 is repeated for the number of conversion methods instructed to create one conversion destination data, and the conversion destination data 103 is output in step 215. Further, when the number of conversion source data 101 is repeated, the processing is terminated (see, for example, Patent Document 1).
JP 2001-184190 A

  However, in such a conventional data conversion processing apparatus, the recovery process cannot be performed only by writing error data in the alarm log file. Therefore, for recovery processing of data that cannot be converted, the code conversion error record is searched from the input file of the code conversion process, identified, the code conversion environment is corrected, and the code of the record is again recorded. Since the conversion must be executed, there is a problem that it takes time as a recovery method. In addition, there is a similar problem with the recovery process of an illegal data error.

  In addition, if a pattern that cannot be converted appears during the data conversion process, if an attempt is made to always input a replacement process on the spot, the data conversion process is temporarily stopped, the processing efficiency deteriorates, and the operator However, there is a problem that processing cannot be performed unless the conversion method is well known.

  Therefore, the present invention has been made to solve such a conventional problem, and it is easy to detect error data without interrupting the data conversion process and without searching for an error record. A code conversion error recovery program capable of performing a recovery process is provided.

  The conversion error record recovery program of the present invention provides a computer with code conversion means for code-converting a data record according to a code conversion table, and when the data record does not correspond to the code conversion table and a code conversion error occurs, the data In accordance with the error record output means for outputting error record information including records to the error logging file, and the corrected code conversion table, the data record causing the code conversion error included in the error record information is extracted from the error logging file. , Functioning as error code conversion means for code conversion, and conversion record output means for outputting the code-converted data record.

  With this configuration, error data is extracted to a separate file from the input file, so data recovery processing can be performed separately from code conversion processing, and data that has become error can be processed without interrupting code conversion processing. The recovery process of the code conversion process can be easily performed without searching again.

  The conversion error record recovery program of the present invention is further characterized in that when the error code conversion means fails in code conversion, it further functions as means for updating the error record information.

  With this configuration, for data that could not be recovered, the recovery process can be performed again using the update record of the error logging file.

  Further, the conversion error record recovery program of the present invention provides a computer, attribute conversion means for converting the attribute of the data record according to the data attribute table, and attribute conversion without the data record corresponding to the data attribute table. When an error occurs, the error record information including the data record is output from the error logging file to the error record information in accordance with an error record output means for outputting to the error logging file, and an error recovery mode including an action when an attribute conversion error occurs. It is characterized by functioning as an error data repairing means for taking out a data record in which an attribute conversion error is included and repairing the data record, and a repair record output means for outputting the repaired data record.

  With this configuration, an error recovery form is set for the data having a data attribute conversion error and recovery processing is performed, so that data with the same data attribute conversion error can also be recovered by this error repair form.

  Further, the conversion error record recovery program of the present invention is characterized in that the error code recovery means further functions as means for updating the error record information when the data record repair fails.

  With this configuration, the recovery process can be performed again with the update record of the error logging file for the data for which the invalid data error could not be resolved by the recovery process.

  Furthermore, the conversion error record recovery program according to the present invention provides the error recovery when the attribute conversion means causes an attribute conversion error when the data record does not correspond to the data attribute table and there is the error recovery form. According to the form, it is further characterized by further functioning as means for converting the attribute of the data record.

  With this configuration, if there is an error repair mode when the data attribute is changed, the error is repaired according to this error repair mode.

  The present invention performs code conversion on a data record according to a code conversion table, and outputs error record information including the data record to an error logging file when the data record does not correspond to the code conversion table and a code conversion error occurs. Then, according to the corrected code conversion table, the data record in which the code conversion error has occurred included in the error record information is extracted from the error logging file and converted, so that the error data is stored in a file separate from the input file. Because the data is extracted, the data recovery process can be performed separately from the code conversion process, and the code conversion process can be easily recovered without interrupting the code conversion process and searching for the data that has become an error again. When processing can be done It is capable of providing transcoding error record recovery program having an effect.

  Further, according to the present invention, when the code conversion fails in the error code conversion, the error record information is updated, and for the data that could not be recovered, the recovery process is performed again by the update record of the error logging file. be able to.

  Further, the present invention converts an attribute of a data record according to a data attribute table, and when the data record does not correspond to the data attribute table and an attribute conversion error occurs, an error record including the data record Information is output to an error logging file, and the data record in which the attribute conversion error is included in the error record information is extracted from the error logging file in accordance with the error repair mode including the action when the attribute conversion error occurs, and the data By repairing a record, an error recovery mode is set for the data that has a data attribute conversion error and recovery processing is performed. Therefore, data with the same data attribute conversion error can also be recovered by this error recovery mode. .

  Further, according to the present invention, in the error code repair, when the data record cannot be repaired, the error record information is updated to update the error record information. Recovery processing can be performed again using the updated record.

  Further, the present invention provides the data record according to the error repair mode when the data record does not correspond to the data attribute table in the attribute conversion and an attribute conversion error occurs and the error repair mode exists. By converting the attribute of the data, if there is an error repair form when the data attribute is changed, the error is repaired according to the error repair form. Therefore, the data attribute change error data that has already been handled is converted to data without making it illegal. And invalid data errors can be resolved with past data.

  Hereinafter, a schematic explanatory diagram of a code conversion error recovery program according to an embodiment of the present invention will be described with reference to FIG.

  As shown in FIG. 1, the code conversion error recovery program of the present invention inputs a data record from an input file 10, performs code conversion processing and data attribute change processing, and creates an output file 20. If an error or an invalid data error occurs, error record information is output to a newly prepared error logging file 30, and the error logging file 30 is used as an input to perform recovery processing.

(First embodiment)
First, FIG. 2 shows the relationship between the code conversion process, the error logging file 30, and the recovery process. Here, numbers 1 to 10 given before the processing shown in FIG. 2 indicate the entire processing order, and error information output and code conversion to the error logging file 30 when a code conversion error occurs in the code conversion processing. The recovery process after repairing the error environment is shown.

  Code conversion error recovery processing is broadly divided into three types: code conversion processing, error environment repair processing, and recovery processing.

  FIG. 3 shows a flowchart of the code conversion process, and FIG. 4 shows a flowchart of the recovery process.

  Hereinafter, the code conversion error recovery process will be described with reference to FIGS. 2, 3, and 4.

  First, in the code conversion process, the code conversion target input file 10 is input (s11), and the code conversion target record of the input file 10 is read (s12). If all the records of the input file 10 are to be converted, the first record is read. Subsequently, code conversion is performed in accordance with the code conversion table from the top data of the read record (s13).

  Here, a specific example is given and demonstrated about code conversion in FIG. The code conversion table shown in FIG. 5 is obtained by adding an EUC corresponding code to a JIS code table. Therefore, mutual conversion between the JIS code and the EUC code can be performed by this code conversion table.

  As shown in FIG. 5, for example, the character “A” in the record of the input file 10 created by the JIS code system is expressed as “2422” (hexadecimal notation) in the JIS code. Therefore, the input file 10 has data with a code of X "2422" (X indicates hexadecimal notation). The code system is converted by the code conversion table so that this can be correctly recognized and displayed in the environment represented by the EUC code system. "A" is X "A4A2" in the EUC code system, so X "2422" is converted to X "A4A2" according to this code conversion table during code conversion.

  Similarly, the character “A” in the input record is converted from X “2341” of the JIS code to X “A3C1” of the EUC code. In this way, data held in the JIS code system is converted into data in the EUC code system.

  Returning to the description of the code conversion error recovery process, it is determined whether or not the code conversion is correctly performed in the code conversion process (s13) (s14). If the code conversion is correctly performed, the record converted into the output file 20 is determined. Is output (s21).

  In the code conversion process (s13), if there is no corresponding code and the code conversion cannot be performed and an error occurs, an error message is output (s15), and information on the record in error is output to the error logging file 30. (S16). The error information includes date and time of error occurrence, error message code / content, error occurrence item, input record, and the like.

  Subsequently, it is determined whether or not there is a next code conversion target record in the input file 10 (s17). If there is a target record, the record is read and the above processing (s12 to s17) is repeated, When there are no more conversion target records, the code conversion process is terminated.

  Regardless of the end of the code conversion process for all records, after the code conversion error occurs, the operator repairs the error environment so that the error data is correctly converted from the error message or the like. In repairing this error environment, the operator corrects the code conversion table so that those that could not be converted are converted correctly.

  For example, when data is distributed from a general-purpose computer GS series computer to a UNIX (registered trademark) computer, the extended Kanji characters of the JEF code used in the GS series are not handled by the UNIX (registered trademark) EUC code. If code conversion is simply performed, an error occurs. Specifically, JEF extended kanji is applicable. FIG. 6 shows a part of JEF extended kanji.

  When a conversion error occurs, as shown in FIG. 7, in order to handle the GS series extended kanji as UNIX (registered trademark) as an error environment repair, each extended kanji is defined as a user-defined character in the JEF code and EUC. Definition is required in the external character area of the code.

  When the error environment can be repaired, recovery processing is performed. In the recovery process, the error logging file 30 containing the input record information for which the code conversion process could not be performed is input (s41), and the recovery target record of the error logging file 30 is read (s42). If all the records of the error logging file 30 are to be recovered, read from the first record.

  Here, by making only the records before the correction date and time of the code conversion table as the recovery target records, the recovery process can be efficiently performed without performing the extra code conversion process. Furthermore, if the error code or the like can correspond to the code conversion table corrected, the target record can be pinpointed and the efficiency of the recovery process can be increased.

  Subsequently, code conversion is performed from the top data of the read record according to the corrected code conversion table (s43).

  In the code conversion process (s43), it is determined whether or not the code conversion is correctly performed (s44). If the code conversion is correctly performed, the converted record is output to the output file 20 (s51). Then, the record that has been correctly transcoded is deleted from the error logging file 30 (s52).

  If there is an error during the code conversion process (s43), an error message is output (s45), and the corresponding data record in the error logging file 30 is updated with this error information (s46).

  Subsequently, it is determined whether or not there is a next recovery target record in the error logging file 30 (s47). If there is a target record, the record is read and the above processing (s42 to s47) is repeated to recover. When processing has been performed on all of the target records, the recovery processing is terminated.

  In the recovery process of the code conversion process, the corresponding record is deleted when the code conversion is completed during the code conversion from the error logging file 30 (s43), and an error occurs when there is a code conversion error. The record information is updated (s46), but when the code conversion is completed, the record is not deleted, and when there is a code conversion error, the error record information is output to a new error logging file. good. In this case, new error recovery processing can be performed during error recovery using a new error logging file, and recovery processing can be performed one after another every time the error environment is repaired, and the code conversion definition has been completed. The data can be converted in order.

  With the above processing, the recovery processing of the code conversion processing can be easily performed without interrupting the code conversion processing and without searching again for the record in error.

(Second Embodiment)
Next, taking the data attribute change process as an example, the relationship between the data attribute change process, the error logging file 30 and the recovery process is shown in FIG. Here, the numbers 1 to 10 given before the processing shown in FIG. 8 indicate the entire processing order as in the explanatory diagram of the code conversion processing, and an error when an illegal data error occurs in the data attribute change processing. The recovery process after the error information output to the logging file 30 and the data attribute change error environment have been repaired is shown.

  Data attribute change recovery processing is roughly divided into three: data attribute change processing, error environment repair processing, and recovery processing.

  FIG. 9 shows a flowchart of the data attribute change process, and FIG. 10 shows a flowchart of the error recovery process of the data attribute change process. Here, since the data attribute of the output destination is determined in the data attribute changing process, the data defining the data attribute of the output destination is defined as an output data attribute definition file.

  Hereinafter, error recovery processing for changing data attributes will be described with reference to FIGS.

  First, in the data attribute change process, the input file 10 that is the data attribute change target is input (s61), and the data attribute change target record of the input file 10 is read (s62). Subsequently, the data attribute of the read record is changed according to the definition of the output data attribute definition file (s63).

  Next, in the data attribute changing process (s63), it is determined whether or not the data attribute has been correctly changed (s64). If the data attribute has been correctly changed, the converted record is output to the output file 20. (S71).

  If there is an invalid data error during the data attribute change process (s63), an error message is output (s65), and information on the record having the illegal data error is output to the error logging file 30 (s66). This error information includes the date and time of error occurrence, error message code / contents, error occurrence item, input record, etc., as in code conversion.

  Subsequently, it is determined whether or not there is a next data attribute change target record in the input file 10 (s67). If there is a target record, the record is read and the above processing (s62 to s67) is repeated. When there are no more data attribute change target records, the data attribute change process is terminated.

  Regardless of the end of the data attribute change processing for all records, after the data attribute change error occurs, the operator repairs the error environment so that the data with the invalid data error is correctly converted from the error message etc. . In this error environment repair, an operator creates an error repair form and sets it in a file so that an error can be repaired even if an invalid data error has occurred.

  Here, FIG. 11 shows an example of data attribute change error and an example of creating an error repair mode, which will be described.

  For example, it is assumed that the m item of the input record M in the input file 10 is “□□ 100” (□ indicates a blank), and this is set as a numerical attribute item in the output file 20. In this case, since □ is not a numerical item, a data attribute error occurs in the data attribute change process.

  Therefore, as an error repair, the handling of □ of the record that caused the error is “Replace □ of numeric digits or more with 0 (that is, change the □ of the upper digit of 100 to 0)”. Thus, even if an error with the same data attribute occurs in the x item of the input record M or an item in the input record N, the error recovery mode can be recovered.

  As another example, numeric conversion from character items to packed format (□ 123 → X "0123C" (pack format): C is a sign indicating that the numeric value is positive), 0 suppression from numeric item to character item (00123 → □□ 123) or the like can be considered.

  Next, data attribute change error recovery processing after error environment repair will be described. In the recovery process for the data attribute change error, the error logging file 30 containing the input record information for which the data attribute change process could not be performed is input (s91), and the data attribute change recovery target record of the error logging file 30 is read (s92). ). If all the records of the error logging file 30 are data attribute change recovery targets, read from the first record. Subsequently, the read record is repaired according to the error repair mode (s93).

  Next, in the error repair process (s93), it is determined whether or not the data attribute has been correctly changed and the error has been repaired (s94). If the data attribute has been correctly changed, the data is stored in the output file 20. The record whose attribute has been changed is output (s101). Then, the record whose data attribute has been correctly changed is deleted from the error logging file 30 (s102).

  If there is an error again during the error recovery process (s93), an error message is output (s95), and the corresponding data record in the error logging file 30 is updated with this error information (s96).

  Subsequently, it is determined whether or not there is a next recovery target record in the error logging file 30 (s97). If there is a target record, the record is read and the above processing (s92 to s97) is repeated to recover. When processing has been performed on all of the target records, the recovery processing is terminated.

  Similarly to the above code conversion process, in the data attribute change recovery process, when the data attribute can be changed, the record is not deleted. When there is a data attribute change error, the error record information is stored in a new error logging file. You may make it output.

  Furthermore, an automatic repair process that automatically performs error repair in the data attribute change process is shown in FIG.

  As shown in FIG. 12, in the automatic repair process, the automatic repair process is performed using an error repair form created in the past. That is, in the data attribute change process, when invalid data is detected (determined in s64), it is determined whether there is an error repair mode (s111), and if a similar data attribute error has occurred in the past (error If the types are the same), the error data is repaired in accordance with the action when an error occurs in the error repair mode (s112), and the conversion record is output to the output file 20 (s71).

  By this automatic repair process, the invalid data error can be automatically resolved by referring to the past repair method for the data that has become the same invalid data in the data attribute change in the past.

  As described above, according to the present invention, since the data information of the code conversion error / data attribute conversion error is extracted to a file different from the input file, the code conversion / data attribute is set after setting the code conversion table / error repair form. Data recovery processing can be performed separately from the change, and the code conversion processing and data attributes can be easily performed without interrupting the code conversion processing and data attribute changing processing, and without re-searching the record in error. The recovery process of the change process can be performed.

  Furthermore, the following is added to the present invention.

(Appendix 1)
Reading means for reading data records from the input file,
Code conversion means for converting the read data record according to the code conversion table;
In the code conversion means, when the data record does not correspond to the code conversion table and a code conversion error occurs, error record information including the data record is output to an error logging file.
In accordance with a code conversion table that has been corrected so as not to cause a code conversion error, an error code conversion unit that takes out the data record in which the code conversion error has occurred included in the error record information from the error logging file and converts the code.
Conversion record output means for outputting the data record that has been code-converted in the error code conversion means,
Conversion error record recovery program to function as.

  (Additional remark 2) The conversion error record recovery program of Claim 1 for functioning further as a means to update the said error record information, when the code conversion in the said error code conversion means fails.

(Appendix 3)
Reading means for reading data records from the input file,
Attribute conversion means for converting the attributes of the read data record according to the data attribute table;
In the attribute conversion means, when the data record does not correspond to the data attribute table and an attribute conversion error occurs, error record information including the data record is output to an error logging file.
In accordance with an error repair mode including an action when an attribute conversion error occurs, an error data repairing unit that takes out a data record in which an attribute conversion error is included in the error record information from the error logging file and repairs the data record;
Repair record output means for outputting the repaired data record,
Conversion error record recovery program to function as.

  (Additional remark 4) The conversion error record recovery program of Additional remark 3 for making it further function as a means to update the said error record information, when the said error code repair means fails in the recovery of the said data record.

  (Additional remark 5) When the said data record does not correspond to the said data attribute table in the said attribute conversion means, but an attribute conversion error occurs, and there exists the said error repair form, according to the said error repair form, The conversion error record recovery program according to appendix 3 or appendix 4 for further functioning as a means for converting an attribute.

  As described above, the code conversion error record recovery program according to the present invention has an effect that error data recovery processing can be easily performed by an error logging file without interrupting code conversion processing. It is particularly useful as a code conversion error record recovery program for performing recovery processing for conversion errors, regarding the distribution of data having different data code systems between systems and the like and the change of data attributes.

It is a schematic explanatory drawing of the code conversion error recovery program of this invention. It is a figure which shows the relationship between the code conversion process of this invention, an error logging file, and a recovery process. It is a flowchart which shows a code conversion process. It is a flowchart which shows a recovery process. It is a figure which shows an example of a JIS and EUC code conversion table. It is a figure which shows the list (part) of a JEF expansion Kanji. It is a figure which shows the example of an error environment repair process in the code conversion error of a JEF expansion kanji. It is a figure which shows the relationship of the data attribute change process of this invention, an error logging file, and a recovery process. It is a flowchart which shows a data attribute change process. It is a flowchart which shows the recovery process of a data attribute change process. It is a figure which shows the creation example of the example of a data attribute change error, and an error repair form. It is a flowchart which shows the data attribute change process which performs automatic error correction. It is a block diagram which shows the conventional format conversion apparatus. It is a flowchart which shows the processing operation of the conventional format conversion apparatus.

Explanation of symbols

10 Input File 20 Output File 30 Error Logging File 101 Conversion Source Data 102 Conversion Method Parameter File 103 Conversion Destination Data 104 Alarm Log File 105 Format Conversion Processing Unit 106 External Conversion Processing Module

Claims (3)

Computer
Reading means for reading data records from the input file,
Code conversion means for converting the read data record according to the code conversion table;
In the code conversion means, when the data record does not correspond to the code conversion table and a code conversion error occurs, error record information including the data record is output to an error logging file.
In accordance with a code conversion table that has been corrected so as not to cause a code conversion error, an error code conversion unit that takes out the data record in which the code conversion error has occurred included in the error record information from the error logging file and converts the code.
Conversion record output means for outputting the data record that has been code-converted in the error code conversion means,
Conversion error record recovery program to function as. Computer
Reading means for reading data records from the input file,
Attribute conversion means for converting the attributes of the read data record according to the data attribute table;
In the attribute conversion means, when the data record does not correspond to the data attribute table and an attribute conversion error occurs, error record information including the data record is output to an error logging file.
In accordance with an error repair mode including an action when an attribute conversion error occurs, an error data repairing unit that takes out a data record in which an attribute conversion error is included in the error record information from the error logging file and repairs the data record;
Repair record output means for outputting the repaired data record,
Conversion error record recovery program to function as. In the attribute conversion means, when the data record does not correspond to the data attribute table and an attribute conversion error occurs, and there is the error repair mode, the attribute of the data record is converted according to the error repair mode The conversion error record recovery program according to claim 2 for further functioning as means.

Images