JP3913742B2 - Object version check system and method, and program - Google Patents

Description

  The present invention relates to a source program and an object version check system and method for checking the version of an object module generated by compiling using include information incorporated as a component of the program, and a program, for example, a COBOL language. This can be used to check the version of the source program described in (1) and the program generated by compiling using macros and copy phrases.

  In general, development of various programs constituting a system is performed by a plurality of developers in charge of work. In addition, the program (object module) created by each developer is released to other developers and used for testing in several environments, and finally the system is operated. Provided to users.

  At this time, the program created by each developer uses a source program and include information stored in a so-called include file (a part of the source program is taken out) depending on the type of language to be described. There are some which compile and generate an object module. For example, when the COBOL language is used, an object module is generated by compiling using a source program described in the COBOL language and a macro or copy phrase described in the COBOL language. In developing such a program, the person in charge of creating the source program (the person in charge of managing the object module) and the person in charge of managing the include file are often different.

  Therefore, when the contents of the include file (include information) are updated, it is important to communicate the updated contents among the persons in charge and to reflect the updated contents. In other words, even though the include information has been updated, the object module compiled using the pre-update include information has been released, or it has already been released after being compiled using the pre-update include information. When there is an object module, if this object module remains as it is without being recompiled, an inconsistency with other object modules occurs. For this reason, the person in charge of the include file must notify the person in charge of creating each source program (the person in charge of managing each object module) that the include information has been updated. When releasing an object module, the module manager must check whether the object module has been compiled using the latest include information. The person in charge of managing each object module needs to monitor whether or not the object module is kept compiled using the latest include information. Conventionally, such confirmation work and monitoring work are performed by each person in charge confirming and monitoring the update date of the include information.

  Further, the following system has been proposed as a system for managing the release of a program (see Patent Document 1). A plurality of update operations (for example, a single update operation to which correction No. 0001 is attached) for a program product composed of a plurality of modules (here, a module is a dynamic link library including some load modules). And another piece of update work to which correction No. 0031 is attached) is performed in parallel. Some modules targeted for the update work of 0001 are modules scheduled to be released (current release target). It is assumed that some modules subject to the update work of 0031 are modules that are not scheduled to be released (not the current release target but the target to be released later). At this time, the revision No. released earlier. The module group to be updated in 0001 and the correction number released later. When there is a module with the same name (for example, A.dll, B.dll) in the module group to be updated, the update point of those modules is compared and the release is scheduled Correction No. 0001 module A. If the update time of dll is the release number corresponding to the module, 0031 Module A. A fault is detected when it is newer than the update time of dll. In other words, in such a situation, the revision No. that has been compiled and updated earlier but the test has not been completed and is not yet released. Module A. after modification of 0031 (modification of load module) Although there is a dll, there is a modification No. that has been compiled and updated later, but the test was completed first and was released first. Module A. after modification of 0001 Since there is a dll, the modification No. Upon release of 0001, module A. dll may include untested modifications (modified load modules that have not been tested). Conversely, the revision No. scheduled to be released. Module 0001 of 0001 If the update time of dll is the release number corresponding to the module, 0031 Module B. When it is older than the update time of dll, the module that has been compiled and updated first completes the test first and is released first, so that no defect is detected. In addition, in this system, a module management table to be released (table that stores the module name and the update time in correspondence with the module group to be released) and a module management table that is not to be released (about the module group that is not to be released) A failure is detected by comparing a module name and a table that stores the module name in association with the update time.

  Furthermore, the following system has also been proposed as another system for managing program release (see Patent Document 2). This system manages load module development and release, that is, compiles a source unit (SL) to generate a compilation unit (CU), and further links the compilation unit (CU) to generate a load module (LM). Information management system, and SL / CU information (information created by associating source unit information and compile unit information) related to the released load module and the configuration of the load module, and release information for each load module When storing in the management file and the storage area is insufficient at the time of storage, the oldest stored release information is deleted, and the compile unit (CU) and load module (LM) constituting the deleted release information are deleted. Compile each For managing the release information that you want to remove from the file and load module file (the file to store the compiled unit (CU)) (the file that stores the load module (LM)).

  Further, the following system has been proposed as a system for detecting program version mismatch (see Patent Document 3). In this system, when compiling and generating an executable program, the version information (version number, date, etc.) is imported into the compiler, and the version information is automatically reflected (included) in the executable program. After the version check program reflecting the above is generated, the execution program and the version check program are transferred to the system operating environment. When the execution program is started in the system operating environment, the version check program is called and started from the execution program, and the version check program that has been started causes the version information of the start source execution program and the version check program to be started. Comparison processing with the version information held by itself is performed. Here, if the compared version information matches, the version check program processing ends and the execution program processing continues. On the other hand, if they do not match, the processing is performed to the system operator. A message prompting the user to select whether or not to continue is output to the system terminal.

JP 2003-296108 A (paragraphs [0027] to [0031], [0037] to [0049], FIG. 2, summary) JP-A-5-233233 (paragraphs [0005], [0007], [0008], [0012], FIG. 1, abstract) Japanese Patent Laid-Open No. 9-265385 (paragraphs [0004] to [0006], FIG. 2, summary)

  When an object module is generated by compiling using the above-described source program and include information (for example, macro or copy phrase in the case of COBOL language), there is a problem between object modules as in the past. In order to prevent consistency, if the person in charge of creating each source program (the person in charge of managing each object module) visually confirms and monitors the update date of include information, it takes time and labor. The work burden on the person in charge is heavy. For this reason, inconsistencies between the object modules caused by the update of the include information (inconsistencies due to the fact that the update of the include information is not reflected for each object module to be reflected) are prevented, In order to reduce the work burden on the person in charge, a system that can automatically check the version of an object module is desired.

  In the system described in Patent Document 1 described above, the update time of the load module included in the module (dynamic link library) is not compared, but the entire module (dynamic link library) including the updated load module is compared. A process different from the present invention is performed in that the update time points are compared. Further, unlike the present invention, the process of embedding the information indicating the generation time in the include information itself is not performed, but any information to be compared is different from the present invention in that information management is performed using a table. Processing is in progress.

  Further, in the system described in Patent Document 2 described above, information on the source unit (SL) and compile unit (CU) used for generating the load module to be released is only managed as release information for each load module. However, various inconsistencies in the load module alone may be eliminated, but this does not solve the problem of further generating and releasing a module (dynamic link library) using the load module.

  Furthermore, in the system described in Patent Document 3 described above, a version check program dedicated to version check must be generated for each execution program, and if the execution program is not started, version check is performed. This is different from the present invention in that it cannot be performed.

  An object of the present invention is to provide an object version check system and method, and program capable of automatically performing version check of object modules, preventing inconsistencies between object modules and reducing the burden on a worker. There is to offer. In the present invention, when the version check is automatically performed, it means that the check process itself is automated, and the timing for performing the check process includes the case where the person in charge of the work gives and the timing addition. And automating.

  The present invention is an object version check system for checking the version of an object module generated by compiling using a source program and include information incorporated as a component of the program. Generation time embedding processing means for embedding information indicating the generation time of the include information in the include information itself, module identification information for identifying the object module as the version management information of the object module, and generation of the object module The version control database that stores information indicating the generation time of the include information used for the correspondence and the source program and include information are compiled and The information indicating the generation time of the include information is extracted from the include information used for generating the object module, and the information indicating the generation time of the extracted include information and the include information are used. Module identification that includes the compilation processing means that performs processing to write the module identification information of the generated object module in correspondence with the version management database, and the information that indicates the generation time of the include information used to generate the object module that is the version check target The information is obtained from the version control database based on the information, and the information indicating the generation time of this include information is extracted from the latest corresponding include information, and the information indicating the generation time is compared with each other. It is characterized in that a version check processing means for performing processing of checking whether they match.

  Here, if the “object module” to be subjected to “version check” is an object module generated by compiling using the source program and include information, for example, COBOL language, C language, assembly language, etc. It may be generated using a source program and include information written in any language. The “compile” in the present invention includes assembly.

  “Include information” refers to information that goes out of a source program, is stored in a so-called include file, and is incorporated as a component of the program at the time of compilation. For example, in the case of the COBOL language, a macro or copy phrase is used. Yes, in the case of the C language, it is a code that is commonly used in a plurality of programs, such as constant names and function prototype definitions. The same applies to the following inventions. In the specification of the present application, a file (include file) in which a macro or a copy phrase is stored is not particularly distinguished from a macro or copy phrase (include information) stored in the file, and is simply a macro or a copy phrase. May be described.

  Furthermore, the “generation time” may be only the date (generation date), and may include not only the date but also the time. The same applies to the following inventions.

  And, the meaning of “embedding information indicating the generation time of this include information in the include information itself” does not mean that information indicating the generation time of the file is attached to the file storing the include information. This means that the include information itself, that is, the information indicating the generation time is embedded in the contents. Similarly, the meaning of “extracting the information indicating the generation time of this include information from the include information” does not mean reading the information indicating the generation time of the file in which the include information is stored, but the inclusion stored in the file. This means that information indicating the generation time is extracted from the information itself (contents). The same applies to the following inventions. Note that embedding in a source program and extraction from a source program described later have the same meaning.

  The “module identification information” is, for example, a module ID, a module name, or the like. The same applies to the following inventions.

  Furthermore, “corresponding” include information in “corresponding latest include information” includes include information that is managed and handled with the same identification information (for example, the same name, the same ID, etc.) even if the content is updated. 2 includes the same identification information as the identification information (name, ID, etc.) of the include information used for generating the object module for the version check. The “latest” include information means include information having the latest generation time among the include information managed and handled with the same identification information (for example, the same name and the same ID). The same applies to the following inventions.

  In such an object version check system of the present invention, the generation time embedding processing means embeds information indicating the generation time in the include information itself, and the compile processing means uses the include information used for compilation at the time of compilation. Is stored in the version management database as version management information. Then, when the version check processing means performs a version check of the object module generated by compiling, the include information (include information incorporated as a component of the program at the time of compilation) used to generate the object module is included. Acquires the information indicating the generation time from the version control database, and the latest corresponding include information (include information that exists in a single file in the state of being included in the include file when it is out of the source program) The information indicating the generation time is extracted from the information, and the information indicating the generation time is compared with each other to check whether or not they match. Here, if they match, the object module is a version compiled using the latest include information and is judged to be normal. On the other hand, if they do not match, release permission or warning is issued. It is possible to perform processing in the case of abnormal output or the like.

  For this reason, it is possible to prevent inconsistencies between the object modules that are caused by updating the contents of the include information. For example, an object that has been compiled by the source program creator (object module manager) using the include information before the update even though the include file manager has updated the include information A situation in which a module is released without being recompiled, that is, without reflecting the updated contents of the include information, and inconsistency with other object modules is avoided. In addition, if the include information is updated when the object module has already been released, the person in charge of the object module will not be aware that the include information has been updated and will compile using the pre-update include information. As a result of not recompiling the object module that is being used, a situation in which inconsistency with other object modules occurs is avoided.

  Furthermore, since the version check of the object module is performed by the version check processing means, the work time is shortened and the object time is shortened as compared with the case of performing the confirmation and monitoring work of the update date of the include information by the blind eye as in the past. The workload of the person in charge of managing the module is reduced, and the object is achieved by these.

  Further, in the object version check system described above, the version check processing means sets the object module to be released as the version check target when the object module is released from the lower environment to the upper environment, Information indicating the generation time of include information used to generate this object module is acquired from the version control database based on the module identification information, and this information is also obtained from the latest corresponding include information released in the upper environment in advance. It is desirable that the information indicating the generation time of the include information is extracted, and the information indicating the generation time is compared with each other to check whether or not they match.

  Here, the "latest latest include information that has been released to the higher environment first" includes information that is "released to the upper environment first" means that the object module subject to version check is released. Include information that has been released prior to the object module whose version is to be checked. In addition, the "latest" include information here refers to the object module that is the version check target, when the updated include information is released and the include information before update is overwritten and deleted. Means the only include information that is released in a higher-level environment where the release is released. On the other hand, even if updated include information is released, the pre-update include information remains unerased. In this case, it means include information having the latest generation time out of include information released in a higher environment where an object module subject to version check is released. The same applies to the following inventions.

  Further, “at the time of release” includes, for example, a time point when the object module is moved to a release standby place in addition to a time point when the object module is actually moved to the release destination of the higher environment. The same applies to the following inventions.

  In this way, when the version check is performed when the object module is released, it is possible to prevent a situation in which an object module compiled using include information before update is released.

  Further, in the case where the version check is performed at the time of release of the object module described above, the version check processing means periodically sets the object module after the release as a version check target in addition to the version check process at the time of release. Information indicating the generation time of include information used to generate the object module is acquired from the version management database based on the module identification information, and the latest corresponding version released in the same environment as the object module subjected to version check The information that indicates the generation time of the include information is extracted from the include information, and the information that indicates the generation time is compared with each other to check whether or not they match. And it is desirable that.

  Here, “regular” means that the execution timing of the version check process is, for example, a fixed time every day at night, a fixed time after working hours every day, or a fixed time at night on Wednesday and Saturday. This means that it is determined in advance without depending on the action (operation) of the person in charge of the work.

  In this way, when it is configured to periodically check the version of the object module in addition to the release of the object module, it is possible to check the version of the object module after the release periodically, and to include the pre-update include information. The situation is avoided in which the object module compiled using the module is left without being recompiled, and the warning list etc. is output to urge the person in charge of the object module to recompile. It is possible to notify the person in charge of managing the object module and the tester of the development system that there is an inconsistency.

  In addition to the above-described object module release, when the version check is periodically performed, the version check processing by the version check processing means compares the information indicating the generation time of the include information with each other. This object module is stored in the version control database provided in the lower environment, as well as moving the object module to the release destination of the higher environment for the object module to be released for which the check result indicates that they match Release execution processing means for performing processing for writing the version management information in the version management database provided in the higher environment, and the version check processing means is the version check processing at the time of release. In the version check process that obtains information indicating the generation time of include information used to generate the object module to be released from the version management database provided in the lower environment and periodically after the release, the released object Information indicating the generation time of include information used to generate modules is obtained from the version management database provided in the higher environment after the write processing by the release execution processing means is performed. Is desirable.

  In the case of a configuration including release execution processing means for performing release processing of an object module whose check result is normal and writing processing of the version management information of the object module to the version management database of the higher environment. The version check processing at the time of release by the version check processing means and the periodic version check processing after the release are linked so that a series of processing associated with system development can be performed smoothly, and The burden is reduced.

  Furthermore, in the object version check system described above, the generation time embedding processing means adds the generation time of the source program to the source program itself in addition to the process of embedding information indicating the generation time of the include information in the include information itself. The version management database is configured to store information indicating the generation time of the include information as well as information indicating the generation time of the source program in association with the module identification information. In addition to the process of extracting the information indicating the generation time of the include information from the include information used for generating the object module, the compile processing means, the source program from the source program used for generating the object module It is also configured to perform processing for extracting information indicating the generation time, and the information indicating the generation time of the extracted include information and the information indicating the generation time of the source program and the information including the include information and the source program are generated. It is configured to perform a process of writing to the version management database in association with the module identification information of the object module, and the version check processing means includes information indicating the generation time of the include information used for generating the object module subject to version check. In addition, the information indicating the generation time of the source program used to generate this object module is also obtained from the version control database and this include information is obtained from the latest included information. In addition to the process of extracting the information indicating the generation time, the process of extracting the information indicating the generation time of the source program from the corresponding latest source program is also performed, and the information indicating the generation time of the include information is compared with each other. In addition to the process of checking whether or not they match, it is preferable that the process of comparing information indicating the generation time of the source program and checking whether or not they match is also performed.

  Here, the “corresponding” source program in the “corresponding latest source program” is a source program that is managed and handled with the same identification information (for example, the same name, the same ID, etc.) even if the contents are updated. In this case, it means a source program with the same identification information as the identification information (name, ID, etc.) of the source program used to generate the object module to be subjected to version check. Further, the “latest” source program means a source program having the latest generation time among source programs managed and handled with the same identification information (for example, the same name, the same ID, etc.). The same applies to the following inventions.

  In this way, in a configuration that performs version check processing that compares information indicating the generation time of the source program in addition to the include information, it is reflected in the object module even though the contents of the source program are updated. The situation of not being performed is avoided, and inconsistencies between modules resulting from such a situation are prevented.

  The present invention described above is configured to store the version management information of the object module (information indicating the generation time of the include information used for generating the object module) in the version management database. This is a version management database-based invention. On the other hand, the present invention described below is called an object module embedded invention because the version management information of the object module is not stored in the version management database but is embedded in the object module itself.

  That is, the present invention is an object version check system for performing version check of an object module generated by compiling using a source program and include information incorporated as a component of the program. , Generation time embedding processing means for performing processing for embedding information indicating the generation time of the include information in the include information itself, and generating an object module by compiling using the source program and include information, and this object module The information indicating the generation time of the include information is extracted from the include information used for generating the information, and the information indicating the generation time of the extracted include information is generated. Compile processing means that embeds as version control information in the module itself, and information indicating the generation time of include information embedded in the object module from the version check target object module, and the latest corresponding include information And a version check processing means for extracting information indicating the generation time of this include information, comparing the information indicating the generation time with each other, and checking whether or not they match. It is a feature.

  In such an object version check system of the present invention, the generation time embedding processing means embeds information indicating the generation time in the include information itself, and the compile processing means uses the include information used for compilation at the time of compilation. Is embedded in the object module itself. Then, when the version check processing means performs a version check of the object module generated by compiling, the include information (include information incorporated as a component of the program at the time of compilation) used to generate the object module is included. Extracts information indicating the generation time from the object module, and also from the latest corresponding include information (include information that exists in a single state when it is out of the source program, that is, it is stored in the include file) Information indicating the generation time is extracted, and the information indicating the generation time is compared with each other to check whether or not they match. Here, if they match, the object module is a version compiled using the latest include information and is judged to be normal. On the other hand, if they do not match, release permission or warning is issued. It is possible to perform processing in the case of abnormal output or the like.

  For this reason, as in the case of the above-described invention using the version management database, it is possible to prevent inconsistencies among the object modules that are caused by updating the contents of the include information.

  Furthermore, since the version check of the object module is performed by the version check processing means, the work time is shortened and the object time is shortened as compared with the case of performing the confirmation and monitoring work of the update date of the include information by the blind eye as in the past. The workload of the person in charge of managing the module is reduced, and the object is achieved by these.

  Further, in the object version check system described above, the version check processing means sets the object module to be released as the version check target when the object module is released from the lower environment to the upper environment, Information indicating the generation time of include information embedded as version control information is extracted from this object module, and the generation time of this include information is extracted from the latest corresponding include information released in the higher environment in advance. It is desirable that the information to be extracted is extracted, and the information indicating the generation time is compared to check whether or not they match.

  In this way, when the version check is performed when the object module is released, the object module compiled using the include information before the update is released as in the case of the above-described invention using the version management database. It is possible to prevent such a situation.

  Furthermore, in the case of a configuration in which version check is performed at the time of release of the object module described above, the version check processing means periodically sets the object module after release as a version check target in addition to the version check process at the time of release. Extracts information indicating the generation time of include information embedded as version management information from the object module, and also includes this information from the latest corresponding include information released in the same environment as the object module subject to version check. It is desirable that the information indicating the generation point of time is extracted, and the information indicating the generation point of time is compared with each other to check whether or not they match.

  In this way, when the version check is periodically performed in addition to the release of the object module, the released object module is also periodically updated as in the case of the above-described version management database utilization type invention. Version checking can be performed, and it is possible to avoid a situation in which an object module compiled using include information before update is left without being recompiled. It is possible to process a notification of inconsistency to a person.

  In addition, when the version is periodically checked in addition to the above-mentioned release of the object module, the generation time embedding processing means adds to the process of embedding information indicating the generation time of the include information in the include information itself. The source program itself is also configured to embed information indicating the generation time of the source program, and the compile processing means extracts information indicating the generation time of the include information from the include information used for generating the object module. In addition to the processing, the processing for extracting the information indicating the generation time of the source program from the source program used for generating the object module is also performed, and the information indicating the generation time of the extracted include information and the source program It is configured to embed information indicating the creation time as version management information in the object module itself to be generated, and the version check processing means generates include information embedded in this object module from the object module subject to version check. In addition to the process of extracting information indicating the generation time of the source program in addition to the information indicating the generation time of the source program, in addition to the process of extracting the information indicating the generation time of this include information from the latest corresponding include information, In addition to the process of extracting the information indicating the generation time of this source program from the source program, comparing the information indicating the generation time of the include information and checking whether or not they match, the source program of That it is configured to performs processing to check whether they match by comparing the pieces of information indicating the formation time is desirable.

  In this way, in a configuration in which version check processing for comparing information indicating the generation point of the source program in addition to the include information is performed, as in the case of the above-described version management database utilization type invention, Although the content has been updated, a situation where it is not reflected in the object module is avoided, and inconsistencies between modules resulting from such a situation are prevented.

  Further, as an object version check method realized by the object version check system of the present invention described above (the invention using the version management database and the object module embedded invention), the following object version of the present invention is provided. Check method is mentioned.

  That is, the present invention is an object version check method for checking the version of an object module generated by compiling using a source program and include information incorporated as a component of the program. The generation time embedding processing means performs processing for embedding information indicating the generation time of the include information in the include information itself, and the compile processing means performs compilation using the source program and the include information to generate an object module. In addition, information indicating the generation time of the include information is extracted from the include information used for generating the object module, and information indicating the generation time of the extracted include information and the Corresponding module identification information for identifying the object module generated using the lude information is written as version management information in the version management database, and the version check processing means generates the object module for the version check. The information indicating the generation time of include information used in the process is acquired from the version management database based on the module identification information, and the information indicating the generation time of this include information is extracted from the latest corresponding include information It is characterized by performing processing for comparing information indicating time points and checking whether or not they match.

  Further, the present invention is an object version check method for checking the version of an object module generated by compiling using a source program and include information incorporated as a component of the program. When generating include information The generation time embedding processing means performs processing for embedding information indicating the generation time of the include information in the include information itself, and the compile processing means compiles using the source program and the include information to generate an object module. At the same time, information indicating the generation time of the include information is extracted from the include information used for generating the object module, and information indicating the generation time of the extracted include information is generated. The version check processing means extracts the information indicating the generation time of the include information embedded in the object module from the version check target object module, and embeds it as version management information in the object module itself. The information indicating the generation time of the include information is extracted from the include information, and the information indicating the generation time is compared with each other to check whether or not they match. is there.

  In such an object version check method of the present invention (a version management database utilization type invention and an object module embedded type invention), the operations and effects obtained by the object version check system of the present invention described above can be obtained as they are. This achieves the object.

  The following program of the present invention can be cited as a program for implementing the above-described version management database utilization type invention and object module embedded type invention.

  That is, the present invention is a program for causing a computer to function as an object version check system for checking the version of an object module generated by compiling using a source program and include information incorporated as a component of the program. When generating the include information, the generation point embedding processing means for embedding information indicating the generation time of the include information in the include information itself, and the object module as the version management information of the object module are identified. A version management database for storing the module identification information for generating and the information indicating the generation time of the include information used for generating the object module in association with each other; Compile using the gram and include information to generate an object module, extract information indicating the generation time of this include information from the include information used to generate this object module, and generate the extracted include information The compile processing means that performs processing to write the information indicating the time point and the module identification information of the object module generated using this include information in correspondence with the version management database, and was used to generate the object module for the version check Information indicating the generation time of include information is acquired from the version control database based on the module identification information, and the generation time of this include information is determined from the latest corresponding include information. As an object version check system comprising: version check processing means for extracting information indicating, comparing the information indicating the generation point of time and checking whether or not they match each other To make the computer function.

  Further, the present invention is a program for causing a computer to function as an object version check system that performs version check of an object module generated by compiling using a source program and include information incorporated as a component of the program. When generating include information, the generation point embedding processing means for embedding information indicating the generation time of the include information in the include information itself, and compiling using the source program and the include information, the object is compiled. Generates a module, extracts information indicating the generation time of this include information from the include information used to generate this object module, and Compile processing means for performing processing to embed information indicating the generation time as version management information in the object module itself to be generated, and information indicating the generation time of include information embedded in this object module from the version check target object module In addition to extracting, information indicating the generation time of the include information is extracted from the latest corresponding include information, and the information indicating the generation time is compared to check whether they match. An object version check system including a version check processing unit is provided for causing a computer to function.

  Note that the above-described program or a part thereof is, for example, a magneto-optical disk (MO), a read-only memory (CD-ROM) using a compact disk (CD), a CD recordable (CD-R), a CD rewritable. (CD-RW), read-only memory (DVD-ROM) using digital versatile disk (DVD), random access memory (DVD-RAM) using DVD, flexible disk (FD), magnetic tape, Recording, storage, distribution, etc. on a recording medium such as a hard disk, read only memory (ROM), electrically erasable and rewritable read only memory (EEPROM), flash memory, random access memory (RAM), etc. Possible, for example, a local area network LAN, Metropolitan Area Network (MAN), Wide Area Network (WAN), Internet, Intranet, Extranet, and other wired networks, wireless communication networks, and combinations of these transmission media It is also possible to carry it on a carrier wave. Furthermore, the program described above may be a part of another program, or may be recorded on a recording medium together with a separate program.

  As described above, according to the present invention, information indicating the generation time of the include information used for generating the object module subject to version check is acquired from the version management database, or this information is obtained from the object module subject to version check. Extracts the information indicating the generation time of include information embedded in the object module, extracts the information indicating the generation time of this include information from the latest corresponding include information, and compares the information indicating these generation times Version check processing is performed to check whether they match, so that the version check of object modules can be performed automatically, and inconsistencies between object modules can be prevented and work can be done. There is an effect that can be shortened and the work the person in charge of the burden between.

  An embodiment of the present invention will be described below with reference to the drawings. FIG. 1 shows an outline of various processes including a work flow at the time of program development performed using the object version check system 10 of the present embodiment and a version check process at the time of release of an object module. Shows an overview of version check processing that is periodically performed by the system 10 at night or the like. 3 shows the overall configuration of the system 10, and FIG. 4 shows detailed contents of various processes including a version check process performed by the system 10.

  The object version check system 10 is a system for developing a system composed of a plurality of programs with the involvement of a plurality of developers, and is a system for realizing the invention using a version management database. Before describing the detailed configuration of the system 10, first, an outline of processing performed by the system 10 will be described with reference to FIGS. 1 and 2.

  In FIG. 1, a macro 4, a copy phrase 5, and a COBOL written in the COBOL language from the Japanese macro 1, the record information (copy phrase) 2, and the Japanese IPO (program) 3 created or prepared by the program development tool. When the source (source program) 6 is generated, information indicating the generation time (macro generation date, copy phrase generation date, and source generation date) is displayed in the macro 4 itself, the copy phrase 5 itself, and the COBOL source 6 itself. ) Is embedded (steps S1, S2, S3).

  When compiling using the macro 4, the copy phrase 5 and the COBOL source 6 (step S4), the macro generation date and the copy phrase embedded in the macro 4, the copy phrase 5 and the COBOL source 6 are stored. The generation date and the source generation date (information) are extracted, respectively, the extracted macro generation date, copy phrase generation date, and source generation date, and the object module generated by compilation (hereinafter simply referred to as a module) The information (module generation date) indicating the generation time of 7 is written and stored in the version management database 40 in association with the module ID assigned to the generated module 7 (step S5). As will be described later, version management databases 40A to 40E are provided in each environment, but the version management database 40 is used as a generic name for them.

  Prior to the release of the module 7, the macro 4, the copy phrase 5, and the COBOL source 6 are released and stored in the object storage library 50 (steps S6, S7, S8). As will be described later, object storage libraries 50A to 50D are provided in each environment, and the object storage library 50 is used as a generic name for them.

  Subsequently, when the module 7 is released, the version check processing unit 33 uses the version check processing unit 33 to indicate information (macro generation date, copy) when the macro 4, the copy phrase 5, and the COBOL source 6 used to generate the module 7 The phrase generation date and the source generation date) are acquired from the version management database 40 using the module ID as a key. Also, from the corresponding latest macro 4, copy phrase 5, and COBOL source 6 previously released and stored in the object storage library 50, the macro generation date, copy phrase generation date embedded in them, and Extract the source generation date (information). Then, version check processing is performed by comparing these macro generation dates, copy phrase generation dates, and source generation dates, respectively, and checking whether or not they match (step S9). If the generation dates match and the check result is normal, the module 7 is released and stored in the object storage library 50 (step S10).

  On the other hand, if the generation dates do not match and the check result is an error, the module 7 is not released. A mismatch between the generation dates occurs in the following cases. For example, the manager in charge of the macro 4 or copy phrase 5 has updated the macro 4 or copy phrase 5, but the manager in charge of the module 7 has compiled the macro 4 or copy phrase 5 before the update. Therefore, when trying to release the generated module 7 or after generating the module 7 after compiling, the macro 4 and the copy phrase 5 are updated and the module 7 is in charge of management. An error occurs when the user tries to release the module 7 that has been compiled using the macro 4 or the copy phrase 5 before being updated without recompiling. If the module 7 in which such an error has occurred is released, an inconsistency will occur with another module 7 that is compiled and generated using the latest macro 4 or copy phrase 5. Become.

  In FIG. 2, after the release of the module 7, the version check processing means 33, 62 allows the version check target module 7 already released and stored in the object storage library 50 to be stored in the object storage library 50, for example, every day at a certain time at night. Acquires information (macro generation date, copy phrase generation date, and source generation date) indicating the generation time of the macro 4, the copy phrase 5 and the COBOL source 6 used for generation from the version management database 40 using the module ID as a key. To do. Also, from the latest corresponding macro 4, copy phrase 5 and COBOL source 6 stored in the object storage library 50 in the same environment as the version check target module 7, the macro generation date and copy phrase embedded in them Extraction date and source generation date are extracted. Then, version check processing is performed by comparing these macro generation dates, copy phrase generation dates, and source generation dates, and checking whether or not they match (step S21).

  If the generation dates do not match and the check result is an error, the result is output to the warning list 33A (step S22). A mismatch between the generation dates occurs in the following cases. For example, in a situation where the module 7 has already been released and stored in the object storage library 50, when the macro 4 or copy phrase 5 is updated, the person in charge of the module 7 updates the macro 4 or copy phrase 5. An error occurs when the module 7 compiled using the macro 4 and the copy phrase 5 before being updated is not re-compiled and left as it is without being noticed. If the module 7 in which such an error has occurred is left in the object storage library 50, the module 7 that is compiled and generated using the latest macro 4 or copy phrase 5 is used. Will cause inconsistencies.

  Next, a detailed configuration of the object version check system 10 will be described. In this embodiment, as an example, the system development environment by the system 10 is assumed to include a UT environment, an ITa environment, an ITb environment, and an ST environment in order from the lower environment. UT is a unit test performed in an individual environment, ITa and ITb are integration tests (integration tests) performed as a whole in a state in which a team composed of a plurality of developers is disclosed, and ST is an actual test This is a system test to check the interface etc. including the user who operates the system. When the tests in these environments are completed, the production environment is entered.

  In FIG. 3, an object version check system 10 includes a plurality of personal terminal devices 20 that are operated when each person in charge of development performs the work that each developer is in charge of, and a network such as a LAN or an intranet. 11 and a production management system 30 connected to the development management system 30 via the network 11.

  Each personal terminal device 20 is constituted by a personal computer, for example, and is equipped with a program development tool 21 that supports development of programs (in the present embodiment, macro 4, copy phrase 5, and COBOL source 6). . As the program development tool 21, for example, a commercially available HLL / WB (H.L. workbench) as a development tool for improving the productivity and quality of COBOL language program development can be employed. This HLL / WB performs a process for supporting the operation of coding the Japanese macro 1 in the HLL / WB language (mainly Japanese) by the administrator of the macro 4, and after completing the coding of the Japanese macro 1, Based on the execution operation of the “generate macro” function by the administrator of the macro 4, the conversion process from the Japanese macro 1 file described in the HLL / WB language to the macro 4 file described in the COBOL language ( Step S1 in FIG. 1) is performed. The file of the macro 4 generated by this conversion process corresponds to a so-called include file, and the macro 4 is a part of the coding and corresponds to the inked information in the present invention.

  In addition, HLL / WB is in the format for HLL / WB based on the execution operation of the “copy phrase generation” function by the administrator of copy phrase 5 after the completion of importing the file of record information 2 onto HLL / WB. A process of generating a file of copy phrase 5 described in the COBOL language from the file of the record information 2 described (the process of step S2 in FIG. 1) is performed. The file of the copy phrase 5 obtained by this generation processing corresponds to a so-called include file, and the copy phrase 5 is a definition of a file format used in the COBOL program, an I / O area, and the like. This corresponds to the inked information. Note that the record information 2 file is a file in the HLL / WB format that has been captured on the HLL / WB, is not coded on the HLL / WB, and is separate from the copy phrase layout file created at the time of design. It is taken in using the tool.

  Furthermore, the HLL / WB performs a process for supporting the work of coding the Japanese IPO3 in the language for the HLL / WB (mainly Japanese) by the administrator of the COBOL source 6, and after the coding of the Japanese IPO3 is completed, Based on the execution operation of the “source generation” function by the administrator of the COBOL source 6, from the Japanese IPO3 file described in the language for HLL / WB, the file of the COBOL source 6 that is a source program described in the COBOL language. Conversion processing (processing in step S3 in FIG. 1).

  Further, the program development tool 21 is provided with generation time embedding processing means 22 for performing processing for embedding information indicating the generation time in the source program itself and the include information itself. In the present embodiment, the generation time embedding processing means 22 performs the process of generating the macro 4, the copy phrase 5, and the COBOL source 6 from the Japanese macro 1, the record information 2, and the Japanese IPO 3, respectively. The macro 4 itself, the copy phrase 5 itself, and the COBOL source 6 itself are each embedded with information indicating the generation time (macro generation date, copy phrase generation date, and source generation date). The function of the generation time embedding processing means 22 is, for example, that the administrator of the system 10 generates each of the “macro generation” function, “copy phrase generation” function, and “source generation” function of the HLL / WB itself. It can be obtained by customizing each process to embed the day.

  The development management system 30 is composed of, for example, a host computer and one or a plurality of servers linked with the host computer, and a processing means 31 for performing various processes relating to the development of a program constituting the development target system, and the processing means A plurality of version management databases 40 (40A, 40B, 40C, 40D) connected to the server 31, a common work area 41, a personal work area 42, and a plurality of object storage libraries 50 (50A, 50B, 50C). Yes.

  The processing unit 31 includes a compile processing unit 32, a version check processing unit 33, and a release execution processing unit 34.

  The compile processing means 32 performs processing for generating an object module 7 by compiling using the macro 4, the copy phrase 5, and the COBOL source 6. Also, the compile processing means 32 receives information indicating the generation time (macro generation date, copy phrase generation date, and The source generation date), the extracted macro generation date and the macro ID for identifying the macro 4, the extracted copy phrase generation date and the copy phrase ID for identifying the copy phrase 5, and the extracted A process of writing the source generation date and the source ID for identifying the COBOL source 6 and the module generation date and the module ID of the generated module 7 to the version management database 40 (40A) is performed.

  When the module 7 is generated using a plurality of macros 4 or a plurality of copy phrases 5 at the time of compilation, the macro generation date and macro ID for all of the plurality of macros 4 or a plurality of copies are generated. The copy phrase generation date and the copy phrase ID for all of the phrases 5 are written in the version management database 40 (40A) in association with the module ID of the generated module 7.

  Such a function of the compile processing means 32 can be obtained by customizing a commercially available compiler by adding a function for performing generation date extraction processing and writing processing to the version management database 40 (40A). .

  The version check processing means 33 includes information indicating the generation time of the macro 4, the copy phrase 5, and the COBOL source 6 used to generate the object module 7 subject to version check, and their IDs (macro generation date / macro ID, copy The phrase generation date / copy phrase ID and the source generation date / source ID) are acquired from the version management database 40 (40A, 40B, 40C, 40D) using the module ID as a key, and the object storage library 50 (50A, 50B, 50C) and the corresponding latest macro 4, copy phrase 5, and COBOL source 6 (macro 4 with the same macro ID, copy phrase 5 with the same copy phrase ID, and COBOL source 6 with the same source ID) The latest life in each environment The macro generation date, the copy phrase generation date, and the source generation date embedded in these are extracted from those having the date, and information indicating the generation time (macro generation dates, copy phrase generation dates) , And source generation dates) are compared to check whether they match.

  When the module 7 subject to version check is generated using a plurality of macros 4 or a plurality of copy phrases 5, the macro generation dates for all of the plurality of macros 4 or a plurality of copy phrases 5 The copy phrase generation dates for all of the above are compared.

  In addition, the version check processing performed by the version check processing means 33 includes processing performed at the time of releasing the object module 7 from the lower environment to the higher environment, and periodically performing the object module 7 after the release at night or the like. There is processing to be called. The check result at the time of release of the former is output as an error message on the display screen at the time of release operation by the person in charge of the module 7 and / or when applying for release, and the result of the check periodically performed at night or the like is a warning. The file is output as a list 33A (see FIG. 2) and stored in the development management system 30, and each person in charge goes to refer to it.

  In the version check process at the time of release, the release target module 7 placed in the lower environment is the version check target, and the macro 4, the copy phrase 5 and the COBOL source 6 used to generate the module 7 Each generation date and each ID thereof are acquired from the version management database 40 using the module ID as a key, and the latest corresponding corresponding release date stored in the object storage library 50 provided in the upper environment is stored. The macro generation date, copy phrase generation date, and source generation date embedded in these are extracted from the macro 4, the copy phrase 5 and the COBOL source 6, respectively, and these generation dates are compared with each other. A process of checking whether or not it is done is performed.

  On the other hand, in the latter version check process after the release, the module 7 already released and stored in the object storage library 50 is subjected to the version check, and the macro 4, the copy phrase 5, and the Each generation date of the COBOL source 6 and each ID thereof are acquired from the version management database 40 using the module ID as a key, and released and stored in the object storage library 50 in the same environment as the module 7 subjected to the version check. The macro generation date, copy phrase generation date, and source generation date embedded in these are extracted from the corresponding latest macro 4, copy phrase 5 and COBOL source 6, respectively. Compare them to match Performs processing to check whether or not Luke.

  The release execution processing unit 34 selects the release target object module 7 for which no error has occurred in the version check processing at the time of release by the version check processing unit 33, based on the release request of the person in charge of the module 7. The version management information (each generation date and each ID) of this module 7 stored in the version management database 50 of the lower environment is transferred (released) to the object storage library 50 of the upper environment, and the version of the upper environment A process of writing to the management database 50 is performed. The release execution processing means 34 also performs a process of releasing the macro 4, the copy phrase 5, and the COBOL source 6 in advance of the module 7 based on the release application of each developer.

  The version management database 40 includes, as version management information of the generated object module 7, the macro generation date and macro ID of the macro 4 used to generate the module 7, and the copy phrase 5 used to generate the module 7. The copy phrase generation date and copy phrase ID, the source generation date and source ID of the COBOL source 6 used to generate the module 7, and the module generation date of the generated module 7 are associated with the module ID of the module 7. To remember.

  The version management database 40 includes version management databases 40A, 40B provided in development environments such as a work environment for performing a release preparation work from a UT environment to a higher environment such as compilation, an ITa environment, an ITb environment, and an ST environment. There are 40C and 40D.

  The common work area 41 is an area for storing a macro 4, a copy phrase 5, and a COBOL source 6 to be bound at the time of compilation.

  The personal work area 42 is an area for each development person to perform his / her own work, and is an area for storing the release target macro 4, copy phrase 5, COBOL source 6, and module 7. The compiled module 7 is output to the personal work area 42.

  The object storage library 50 stores the released macro 4, copy phrase 5, COBOL source 6, and module 7. The object storage library 50 includes object storage libraries 50A, 50B, and 50C provided in the development environments of the ITa environment, the ITb environment, and the ST environment.

  The production system 60 is a system that is operated by a user (for example, a department in charge of operation different from each department in charge of development) by actually operating the developed program, and is configured by one or a plurality of computers, for example. And a processing means 61 for performing various processes relating to system operation, and a version management database 40 (40E) and an object storage library 50 (50D) connected to the processing means 61.

  The processing unit 61 includes a version check processing unit 62 that performs the same processing as the version check processing unit 33 provided in the processing unit 31 of the development management system 30. However, the version check processing means 62 performs a version check process periodically performed at night or the like, but does not perform a version check process at the time of release.

  The version management database 40E is the version management database 40 provided in the production environment, and has the same configuration as the version management databases 40A to 40D provided in each development environment of the development management system 30.

  The object storage library 50D is an object storage library 50 provided in the production environment, and has the same configuration as the object storage libraries 50A to 50C provided in each development environment of the development management system 30. In the present embodiment, for the object storage libraries 50A, 50B, and 50C of the development environments (ITa environment, ITb environment, and ST environment) described above, the macro 4, the copy phrase 5, the COBOL source 6, and the module 7 are present. When it is released (released), the corresponding macro 4, copy phrase 5, COBOL source 6, and module 7 that were originally stored there (having the same ID) are overwritten and erased. However, since the object storage library 50D in the production environment may be urgently restored in the event of a problem, the version older by one generation is managed and released. However, in each development environment, although it is not disclosed, since it is managed to be backed up every day, the old version is actually stored for a certain period of time. Such a management method is an example, and the present invention is not limited to this.

  In the above, the generation point embedding processing means 22 included in the program development tool 21 of the personal terminal device 20, the compile processing means 32 included in the processing means 31 of the development management system 30, the version check processing means 33, and the release The version check processing means 62 included in the execution processing means 34 and the processing means 61 of the production system 60 includes the personal terminal device 20, the development management system 30, and the computer main bodies (personal computer, host computer) constituting the production system 60. , Server, etc.) and a central processing unit (CPU) provided in the interior of the CPU, and one or a plurality of programs that define the operation procedure of the CPU.

  The version management databases 40A, 40B, 40C, and 40D provided in the development management system 30, the common work area 41, the personal work area 42, the object storage libraries 50A, 50B, and 50C, and the versions provided in the production system 60 The management database 40E and the object storage library 50D are preferably realized by, for example, a hard disk, but ROM, EEPROM, flash memory, RAM, MO, CD, as long as there are no problems with storage capacity, access speed, etc. -ROM, CD-R, CD-RW, DVD-ROM, DVD-RAM, FD, magnetic tape, or a combination thereof may be employed.

  In this embodiment, the program is developed while performing the version check process of the object module 7 using the object version check system 10 as follows. Here, the detailed contents of the processing will be described mainly with reference to FIG.

  First, as outlined in FIG. 1, each person in charge of development operates each personal terminal device 20 and uses the program development tool 21 to use the Japanese macro 1, record information 2, and Japanese IPO3. Create or prepare. Then, the program development tool 21 is used to execute the execution functions of “macro generation”, “copy phrase generation”, and “source generation”, and from the Japanese macro 1, record information 2, and Japanese IPO3, A macro 4, a copy phrase 5, and a COBOL source 6 described in the COBOL language are generated (steps S1, S2, and S3 in FIG. 1). During the processing of steps S1, S2, and S3, the generation time embedding processing means 22 causes the macro 4 itself, the copy phrase 5 itself, and the COBOL source 6 itself to receive information (macro generation date, The copy phrase generation date and the source generation date) are embedded. The above operations are performed in the UT environment.

  Subsequently, each developer in charge moves (copies) the generated macro 4, the copy phrase 5, and the COBOL source 6 to the common work area 41 as an object to be compiled, as shown in FIG. It is also moved (copied) to its own personal work area 42 in preparation for release.

  Then, the person in charge of creating the COBOL source 6 (the person in charge of managing the module 7) compiles the COBOL source 6 created by himself. Then, the compile processing unit 32 incorporates the necessary macro 4 and copy phrase 5 to generate the object module 7 and outputs the generated module 7 to the person's personal work area 42 (FIG. 1). And step S4 in FIG. At this time, the compile processing unit 32 extracts the macro generation date, the copy phrase generation date, and the source generation date embedded in the macro 4, the copy phrase 5 and the COBOL source 6 used for the compilation, and The extracted macro generation date and the macro ID of the macro 4, the extracted copy phrase generation date and the copy phrase ID of the copy phrase 5, the extracted source generation date and the source ID of the COBOL source 6, and the module generation date, It is written in the version management database 40A of the work environment in correspondence with the generated module ID of the module 7 (step S5 in FIGS. 1 and 4).

  Also, as shown in FIG. 4, each developer in charge performs a release operation on the macro 4, the copy phrase 5, and the COBOL source 6 that he / she is in charge of, and moves to a release standby place (not shown) to apply for release. Do. Then, for example, at the night of the day, the release execution processing unit 34 moves the macro 4, the copy phrase 5, and the COBOL source 6 for which release has been applied to the object storage library 50 </ b> A in the ITa environment as a higher environment. (Steps S601, S701, S801 in FIG. 4 are equivalent to Steps S6, S7, S8 in FIG. 1). When the macro 4, the copy phrase 5, and the COBOL source 6 are released, the version check process is not performed as when the module 7 is released.

  The release of the macro 4, the copy phrase 5, and the COBOL source 6 is performed prior to the release of the module 7. In addition, since the macro 4, the copy phrase 5, and the COBOL source 6 need only be released prior to the module 7, they may be released before compilation (step S4). Furthermore, each developer can select according to the purpose to which environment the macro 4, the copy phrase 5, and the COBOL source 6 that he / she is responsible for are released. Accordingly, not only the release to the object storage library 50A in the ITa environment (steps S601, S701, S801 in FIG. 4) but also the release to the object storage library 50B in the ITb environment (steps S602, S702, S802 in FIG. 4), ST Release to the environment object storage library 50C (steps S603, S703, and S803 in FIG. 4) and release to the actual environment object storage library 50D (steps S604, S704, and S804 in FIG. 4) may be performed. For example, when the contents of the macro 4 are updated, in the ST environment, since the entire test has already been performed using the module 7 compiled using the macro 4 before the update, the old module 7 is temporarily replaced. In order to proceed with the test, the manager in charge of the macro 4 may keep the updated release of the macro 4 until the ITb environment below the ST environment. In such a case, since the updated macro 4 is not released in the ST environment, the macro 4 before the update becomes the latest macro 4 in the ST environment, and the version check processing unit 33 performs nighttime in the ST environment. In the version check process performed periodically, the macro generation date is compared between the old module 7 compiled using the macro 4 before the update and the macro 4 before the update. There is no error.

  Thereafter, the manager in charge of the module 7 performs a release operation on the module 7 output to his / her personal work area 42. When the release operation is performed, the module 7 is moved to a release standby place (not shown). At this time, the version check processing by the version check processing means 33 is automatically performed. That is, the version check processing means 33 has information indicating the generation time of the macro 4, the copy phrase 5 and the COBOL source 6 used to generate the module 7, and their IDs (macro generation date / macro ID, copy phrase generation). The date / copy phrase ID and the source generation date / source ID) are acquired from the version management database 40A of the work environment using the module ID assigned to the module 7 as a key. Also, from the corresponding latest macro 4, copy phrase 5 and COBOL source 6 that were released in advance and stored in the object storage library 50A of the ITa environment, the macro generation date and copy phrase generation embedded in them Extract the date and source generation date respectively. Then, the version check processing means 33 compares the macro generation dates, the copy phrase generation dates, and the source generation dates, respectively, and checks whether they match, thereby performing the version check processing. This is performed (step S901 in FIG. 4: equivalent to step S9 in FIG. 1).

  Here, when the generation dates coincide with each other and there is no error in the check result, the manager in charge of the module 7 makes a release application to the ITa environment. If an error occurs, the module 7 may not be moved to a release standby location (not shown), or may be moved to a release standby location, but the manager in charge of the module 7 does not make a release application. Thus, a warning display may be issued or release application may not be performed. Then, when the person in charge of managing the module 7 makes a release application, for example, the release execution processing unit 34 releases the modules 7 for which the release application has been made to the ITa environment from the release standby location at the same time. It is stored in the environmental object storage library 50A (step S101 in FIG. 4: equivalent to step S10 in FIG. 1).

  Further, the release execution processing means 34, together with the release processing for the module 7 to the ITa environment, version management information (module generation date / module ID, macro) stored in the version management database 40A of the work environment for the module 7 The generation date / macro ID, the copy phrase generation date / copy phrase ID, and the source generation date / source ID) are written in the version management database 40B of the ITa environment, which is the higher environment where the module 7 was released (step of FIG. 4). S11).

  Next, when the test in the ITa environment is completed and the module 7 is released to the ITb environment, which is a higher environment, the manager in charge of the module 7 performs a release operation on the module 7 and releases the module 7 Move to a waiting place (not shown). At this time, the version check processing by the version check processing means 33 is automatically performed. That is, the version check processing means 33 uses the generation date of each of the macro 4, the copy phrase 5, and the COBOL source 6 used for generating the module 7 and their IDs, and the version management database of the ITa environment using the module ID as a key. Obtain from 40B. Also, from the corresponding latest macro 4, copy phrase 5 and COBOL source 6 that have been released in advance and stored in the object storage library 50B of the ITb environment, the macro generation date and copy phrase generation embedded in them Extract the date and source generation date respectively. Then, the version check processing means 33 compares the macro generation dates, the copy phrase generation dates, and the source generation dates, respectively, and checks whether or not they match, thereby performing the version check processing. This is performed (step S902 in FIG. 4; corresponding to step S9 in FIG. 1).

  Here, when the generation dates coincide with each other and there is no error in the check result, the manager in charge of the module 7 makes a release application to the ITb environment. Then, for example, at the night of the day, the release execution processing means 34 collectively releases the modules 7 for which release has been applied from the release standby location to the ITb environment and stores them in the object storage library 50B of the ITb environment (FIG. 4). Step S102: equivalent to Step S10 in FIG. 1).

  Further, the release execution processing means 34 uses the version management information stored in the version management database 40B of the ITa environment for the module 7 together with the release process for the module 7 to the ITb environment, Is written in the version management database 40C of the ITb environment (step S12 in FIG. 4).

  Similarly, when the test in the ITb environment is completed and the module 7 is released to the ST environment, which is a higher environment, the person in charge of the module 7 performs a release operation on the module 7, and Move to the release waiting place (not shown). At this time, the version check processing by the version check processing means 33 is automatically performed. That is, the version check processing unit 33 uses the generation date of each of the macro 4, the copy phrase 5, and the COBOL source 6 used to generate the module 7 and their IDs, and the version management database of the ITb environment using the module ID as a key. Acquired from 40C. Further, from the corresponding latest macro 4, copy phrase 5 and COBOL source 6 released in advance and stored in the object storage library 50C of the ST environment, the macro generation date and copy phrase generation embedded in these Extract the date and source generation date respectively. Then, the version check processing means 33 compares the macro generation dates, the copy phrase generation dates, and the source generation dates, respectively, and checks whether they match, thereby performing the version check processing. This is performed (step S903 in FIG. 4: equivalent to step S9 in FIG. 1).

  Here, when the generation dates coincide with each other and there is no error in the check result, the manager in charge of the module 7 makes a release application to the ST environment. Then, for example, at the night of the day, the release execution processing unit 34 collectively releases the modules 7 that have been requested for release from the release standby location to the ST environment and stores them in the object storage library 50C of the ST environment (FIG. 4). Step S103: equivalent to Step S10 in FIG. 1).

  Further, the release execution processing means 34 uses the version management information stored in the version management database 40C of the ITb environment for the module 7 together with the release process to the ST environment for the module 7, and the higher level where the module 7 is released. Is written in the version management database 40D of the ST environment (step S13 in FIG. 4).

  Further, when the test in the ST environment is completed and the module 7 is released to the production environment, the person in charge of the module 7 performs a release operation on the module 7 and places the module 7 in a release standby place (not shown). Move to. At this time, unlike the case of the release under the development environment, the version check processing by the version check processing means 33 is not performed.

  Then, when the person in charge of the module 7 makes a release application to the production environment, for example, at the night of the day, the release execution processing unit 34 collects the modules 7 for which the release application has been made from the release standby location. And stored in the object storage library 50D in the production environment (step S104 in FIG. 4).

  Further, the release execution processing means 34 uses the version management information stored in the version management database 40D of the ST environment for the module 7 together with the release processing for the module 7 to the production environment, and the production that the module 7 has been released to. Write to the environment version management database 40E (step S14 in FIG. 4).

  In addition to the processes including the version check process at the time of release described above, the object version check system 10 uses the version check processing means 33 and 62 to develop the development environment of the ITa environment, the ITb environment, and the ST environment, and the production environment. For example, the version check process is performed on the module 7 after release in the same environment described in FIG. The contents of this process will be described with reference to FIG.

  In the ITa environment, the version check processing means 33 uses the macro 4, the copy phrase 5, and the COBOL source that have been released and used to generate the version check target module 7 stored in the object storage library 50A of the ITa environment. 6 are generated from the version management database 40B of the ITa environment using the module ID as a key. Also, from the corresponding latest macro 4, copy phrase 5, and COBOL source 6 stored in the object storage library 50 A of the ITa environment that is the same environment as the environment in which the module 7 subject to version check is released, The embedded macro generation date, copy phrase generation date, and source generation date are extracted. Then, the version check processing means 33 compares the macro generation dates, the copy phrase generation dates, and the source generation dates, respectively, and checks whether they match, thereby performing the version check processing. This is performed (step S21 in FIG. 2). If the generation dates do not match and the check result is an error, the result is output to the warning list 33A (step S22 in FIG. 2).

  Similarly, in the ITb environment, the version check processing unit 33 stores the version management information (such as the macro generation date) stored in the version management database 40C of the ITb environment and the object storage library 50B of the ITb environment. The macro generation date is compared with each other using the macro 4 or the like. In the ST environment, the version check processing unit 33 performs version management information (macro generation date) stored in the version management database 40D of the ST environment. Etc.) and the macro 4 etc. stored in the object storage library 50C of the ST environment are used to compare the macro generation dates. In the production environment, the version check processing means 62 performs the production environment. Stored in version control database 40E And version management information (the macro generation date, etc.), by using the macro 4 or the like stored in the object storage library 50D of production, comparison, etc. between the macro-date is performed.

  In the following, an example of a processing procedure when the contents of the macro 4 are updated in a situation where the object module 7 has already been released in a certain environment (for example, an ITa environment) will be described. The same applies when the copy phrase 5 is updated.

  In FIG. 4, the manager in charge of the macro 4 updates the contents of the macro 4 and notifies the manager in charge of each module 7 of the fact and the scheduled release date of the macro 4 (for example, February 1). The macro 4 notified and updated is stored in the common work area 41 for compiling, and also stored in the personal work area 42 for release preparation. When the manager in charge of each module 7 receives the macro update notification, the compile processing unit 32 compiles using the updated macro 4 to generate a new module 7, which is stored in the personal work area 42. Store and prepare for release. At this time, as the version management information of the generated new module 7, the macro generation date of the macro 4 used for the compilation is written in the version management database 40A.

  Subsequently, when the person in charge of the macro 4 performs a release operation on the updated macro 4, the macro 4 is moved from the personal work area 42 to a release standby place (not shown). When the person in charge of the macro 4 makes a release application, the release execution processing means 34 releases the macro 4 from the release standby place to the object storage library 50A in the ITa environment at night of the day (February 1). The

  Thereafter, when the version check processing unit 33 performs a nighttime (February 1) version check process in the ITa environment, at this point, the module 7 released in the object storage library 50A in the ITa environment is still Since it is an old one compiled using the macro 4 before update, an error (a check processing result indicating an error) is temporarily output as a check result.

  Then, for example, on the next day (February 2), when the person in charge of the module 7 performs a release operation on the module 7 recompiled by using the updated macro 4, this module 7 is stored in the personal work area. The version is moved from 42 to a release waiting place (not shown). At this time, the version check processing means 33 performs a version check process at the time of release. In this version check process, the macro generation date stored in the version management database 40A as the version management information for the module 7 recompiled using the updated macro 4 and the ITa released earlier on February 1 Since the macro generation date of the macro 4 stored in the environment object storage library 50A is compared, an error (check processing result indicating an error) does not appear in the check result.

  Then, when the person in charge of the module 7 makes a release application, the release execution processing means 34 releases the module 7 from the release standby place to the object storage library 50A in the ITa environment at night of the day (February 2). At the same time, the version management information (such as macro generation date) stored in the version management database 40A is written into the version management database 40B of the ITa environment.

  After that, when the version check processing unit 33 performs nighttime (February 2) version check processing in the ITa environment, at this time, the module 7 released in the object storage library 50A in the ITa environment is updated. The module 7 is a new one compiled using the macro 4, and no error is generated in the check result for the module 7.

  In this way, when all the modules 7 necessary for the test in each environment (here, the ITa environment) are recompiled and no error occurs in the check result, the modules 7 in the environment The inconsistency disappears, and testing within that environment can be performed normally.

  According to this embodiment, there are the following effects. That is, since the object version check system 10 includes the generation time embedding processing means 22, each generation date can be embedded in the macro 4 and the copy phrase 5 when they are generated, and the compile processing means 32 and the version management database 40, the generation dates of the macro 4 and the copy phrase 5 used for generating the module 7 at the time of compilation can be written in the version management database 40. Furthermore, since the system 10 includes version check processing means 33 and 62, the generation date of the macro 4 and the copy phrase 5 used for generating the version check target module 7 is acquired from the version management database 40. Each generation date embedded in them is extracted from the latest corresponding macro 4 or copy phrase 5, and these generation dates are compared with each other to check whether or not they match. For this reason, it is possible to prevent inconsistencies among the modules 7 that are caused by updating the contents of the macro 4 and the copy phrase 5.

  Further, since the system 10 includes the version check processing means 33 and 62, the version check of the module 7 can be automatically performed. For this reason, the work time can be shortened and the workload of the manager in charge of the module 7 can be reduced as compared with the case of performing confirmation work and monitoring work of the update date of the macro 4 and the copy phrase 5 by the blindness as in the past. Can do.

  Since the version check processing unit 33 performs version check when the module 7 is released, it is possible to prevent a situation in which the module 7 compiled using the macro 4 and the copy phrase 5 before being updated is released. it can.

  Also, since the version check processing means 33 and 62 periodically check the version of the module 7 after the release at a fixed time at night, for example, the version check processing means 33 and 62 are compiled using the macro 4 and the copy phrase 5 before update. It is possible to avoid the situation where the released module 7 is left without being recompiled, and the warning list 33A and the like are output to prompt the manager of the module 7 to recompile. It is possible to perform processing such as notifying the manager in charge of other modules 7 and the tester of the development system that there is a mismatch.

  Further, since the system 10 includes the release execution processing unit 34, the release process of the module 7 for which the result of the check process is normal and the environment of the environment above the version management information (such as the macro generation date) of the module 7 Write processing to the version management database 40 can be performed. For this reason, the version check processing at the time of release by the version check processing means 33 and the periodic version check processing after release can be linked, and a series of processing accompanying system development can be smoothly performed. The burden on the worker can be reduced.

  The version check processing means 33 and 62 perform version check processing for comparing the generation dates of the COBOL source 6 in addition to the macro 4 and the copy phrase 5, so that the contents of the COBOL source 6 are updated. The situation where it is not reflected in the module 7 can be avoided, and inconsistencies between the modules 7 resulting from such a situation can be prevented.

  Note that the present invention is not limited to the above-described embodiment, and modifications and the like within a scope where the object of the present invention can be achieved are included in the present invention.

  That is, in the above embodiment, the system 10 is configured to generate the object module 7 using the macro 4, the copy phrase 5, and the COBOL source 6. However, the application target language of the present invention is the COBOL language. For example, C language or the like may be used, and in short, the present invention can be applied to the development of a program that is compiled using include information to generate an object module.

  In the embodiment, the version management database 40 writes version management information such as the macro generation date and the copy phrase generation date (invention using the version management database). As in the object version check system 200, a configuration in which version management information is embedded in the object module 8 itself (an object module embedded type invention) may be employed.

  FIG. 5 shows an outline of various processes including a work flow at the time of program development performed using the object version check system 200 and a version check process at the time of release of the object module 8. FIG. 200 shows an outline of the version check process periodically performed at night or the like.

  The difference between the system 200 and the system 10 of the embodiment is that the system 10 of the embodiment includes the version management database 40, whereas the system 200 does not include the version management database. In the object module 7 generated by compiling by the system 10, the version management information of the module 7 is not embedded, whereas in the object module 8 generated by compiling by the system 200, the version management is performed. In contrast to the fact that the information is embedded and the version check processing means 33 and 62 of the system 10 of the above-described embodiment acquire the version management information of the module 7 to be version checked from the version management database 40, the system 200 Over John check processing unit 233,262 is that obtained from the module 8 itself. Below, the outline | summary of the process performed by the system 200 is demonstrated with reference to FIG. 5 and FIG.

  In FIG. 5, when the macro 4, the copy phrase 5, and the COBOL source 6 described in the COBOL language are generated from the Japanese macro 1, the record information 2, and the Japanese IPO 3 created or prepared by the program development tool. The macro 4 itself, the copy phrase 5 itself, and the COBOL source 6 itself are embedded with information (macro generation date, copy phrase generation date, and source generation date) indicating the respective generation times (steps S201, S202, S203). ). This processing is the same as the processing in steps S1, S2, and S3 of the embodiment.

  When compiling using the macro 4, the copy phrase 5 and the COBOL source 6 (step S204), the macro generation date and the copy phrase embedded in the macro 4, the copy phrase 5 and the COBOL source 6 are stored. The generation date and the source generation date are extracted, respectively, and the extracted macro generation date, copy phrase generation date, source generation date, and information (module generation date) indicating the generation time of the object module 8 generated by compiling Then, it is embedded in the generated module 8 itself as version management information of the module 8. Therefore, the compile processing means 32 of the system 10 of the above embodiment has performed the process of writing the version management information into the version management database 40 (step S5 in FIG. 1), but the compile processing means of the system 200 is the module 8 itself. Therefore, the writing process to the version management database 40 is not performed.

  Prior to the release of the module 8, the macro 4, the copy phrase 5, and the COBOL source 6 are released and stored in the object storage library 250 (steps S205, S206, S207). This processing is the same as the processing in steps S6, S7, and S8 of the above embodiment.

  Subsequently, when the module 8 is released, the version check processing means 233 provided in the development management system indicates the generation time of the macro 4, the copy phrase 5, and the COBOL source 6 used to generate the module 8. Information (macro generation date, copy phrase generation date, and source generation date) is extracted from the module 8. Also, from the corresponding latest macro 4, copy phrase 5, and COBOL source 6 previously released and stored in the object storage library 250, the macro generation date, copy phrase generation date embedded in these, and Extract the source generation date. Then, the version check process is performed by comparing the macro generation dates, the copy phrase generation dates, and the source generation dates, respectively, and checking whether or not they match (step S208). If the generation dates match and the check result is normal, the module 8 is released and stored in the object storage library 250 (step S209). On the other hand, if the generation dates do not match and the check result is an error, the module 8 is not released.

  In FIG. 6, after the release of the module 8, the version check processing means 233 provided in the development management system and the version check processing means 262 provided in the production system have already been released, for example, every day at a fixed time at night. Information indicating the generation time of the macro 4, the copy phrase 5 and the COBOL source 6 used to generate the version check target module 8 stored in the object storage library 250 (macro generation date, copy phrase generation date, And the source generation date) are extracted from the module 8. Also, from the corresponding latest macro 4, copy phrase 5 and COBOL source 6 stored in the object storage library 250 in the same environment as the version check target module 8, the macro generation date and copy phrase embedded in them Extraction date and source generation date are extracted. Then, these macro generation dates, copy phrase generation dates, and source generation dates are compared with each other to check whether or not they match to perform version check processing (step S221). If the generation dates do not match and the check result is an error, the result is output to the warning list 233A (step S222).

  As described above, the object version check system and the method and the program according to the present invention can check the version of a program generated by compiling using, for example, a source program described in the COBOL language and a macro or copy phrase. It is suitable for use when performing.

BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is an explanatory view of an outline of various processes including a flow of a program development performed using an object version check system according to an embodiment of the present invention and a version check process at the time of release of an object module. Explanatory drawing of the outline | summary of the version check process performed regularly at night etc. by the system of the said embodiment. 1 is an overall configuration diagram of a system of the embodiment. FIG. Explanatory drawing of the detailed content of various processes including the version check process performed by the system of the said embodiment. The explanatory view of the outline of various processing including the work flow at the time of program development performed using the object version check system of another form of the present invention, and the version check processing at the time of release of an object module. Explanatory drawing of the outline | summary of the version check process performed regularly at night etc. by the system of the said another form.

Explanation of symbols

4 Macro that is include information 5 Copy phrase that is include information 6 COBOL source that is a source program 7, 8 Object module 10,200 Object version check system 22 Generation point embedding processing means 32 Compile processing means 33, 62, 233, 262 Version check processing means 34 Release execution processing means 40 (40A, 40B, 40C, 40D, 40E) Version management database

Claims (10)

An object version check system for checking the version of an object module generated by compiling using a source program and include information incorporated as a component of the program,
Generation time embedding processing means for performing a process of embedding information indicating the generation time of the include information in the include information itself when generating the include information;
A version management database that stores module identification information for identifying the object module in association with information indicating the generation time of the include information used for generating the object module, as the version management information of the object module; ,
Performing the compilation using the source program and the include information to generate the object module, extracting information indicating the generation time of the include information from the include information used for generating the object module; and Compile processing means for performing processing of writing the information indicating the generation time of the extracted include information and the module identification information of the object module generated using the include information in association with each other, and writing to the version management database;
Transfer and store the object module from a lower-level environment object storage library or personal work area provided for performing step-by-step program development to a higher-level environment object storage library used in a more advanced development stage. The release target object module stored in the lower-level environment object storage library or personal work area is subject to version check, and the include information used to generate the object module together with the information indicating the generation time of obtaining from the version management database based on the module identification information, date of the corresponding preceding to be transferred to the object storage library of the host environment stored Include Version check processing means for extracting information indicating the generation time of this include information from the information and comparing the information indicating the generation time to check whether or not they match. An object version check system characterized by The version check processing means, in addition to the version check process when the release regularly above, the object module after the release has taken place and the version check target, used to generate this object module The information indicating the generation time of the include information is acquired from the version management database based on the module identification information, and transferred to the object storage library in the same environment as the object module subjected to the version check and stored The information indicating the generation time of the include information is extracted from the latest include information to be compared, and the information indicating the generation time is compared to check whether or not they match. Being Object version check system of claim 1, wherein. For the version check process the included information the release of the target the object module that they compare the pieces of information indicating the generation time point out the check result that is consistent with version check process during the release by means , along with transferring the object module in the object storage library of the host environment, the versioning database the versioning information for this object module stored in the version management database of the subordinate environment, the higher the environment Release execution processing means for performing processing to write to
The version check processing means includes:
The version check process during the release, the information indicating the generation time of the included information used to generate the subject the object module of the release, obtained from the version management database of the subordinate environment,
Version check process regularly carried out after the release has been performed, information indicating the generation time of the included information used to generate the object module after the release has taken place, by the release execution processing unit The object version check system according to claim 2 , wherein the object version check system is configured to acquire from the version management database of the upper environment after the writing process is performed. The generation time embedding processing means performs processing for embedding information indicating the generation time of the source program in the source program itself, in addition to processing for embedding information indicating the generation time of the include information in the include information itself. And
The version management database is configured to store, in addition to information indicating the generation time of the include information, information indicating the generation time of the source program in association with the module identification information,
The compile processing means, in addition to the process of extracting information indicating the generation time of the include information from the include information used for generating the object module, in addition to the process of extracting the source program from the source program used for generating the object module. A process for extracting information indicating the generation time is also performed, and the information indicating the generation time of the extracted include information and the information indicating the generation time of the source program are generated using the include information and the source program. And a process for writing to the version management database in association with the module identification information of the object module,
The version check processing means indicates the generation time of the source program used to generate the object module in addition to information indicating the generation time of the include information used to generate the object module to be the version check target. In addition to processing for obtaining information from the version management database and extracting information indicating the generation time of the include information from the latest corresponding include information, the information is also obtained from the latest corresponding source program. In addition to the process of extracting information indicating the generation time of the program, comparing the information indicating the generation time of the include information and checking whether or not they match, the generation time of the source program is Compare the information shown Object version checking system according to any one of claims 1 to 3, characterized in that they are configured to performs a process of checking whether they match with. An object version check system for checking the version of an object module generated by compiling using a source program and include information incorporated as a component of the program,
Generation time embedding processing means for performing a process of embedding information indicating the generation time of the include information in the include information itself when generating the include information;
Performing the compilation using the source program and the include information to generate the object module, extracting information indicating the generation time of the include information from the include information used for generating the object module; and Compile processing means for performing processing for embedding information indicating the generation time of the extracted include information as version management information in the object module itself to be generated;
Transfer and store the object module from a lower-level environment object storage library or personal work area provided for performing step-by-step program development to a higher-level environment object storage library used in a more advanced development stage. At the time of release, the object module of the release target stored in the object storage library of the lower environment or the personal work area is subjected to version check, and the object module is embedded in the object module. extracts the information indicating the generation time of the included information, raw preceding to this include information from the latest of the included information corresponding stored is transferred to the object storage library of the host environment Object version check characterized by comprising version check processing means for extracting information indicating time points and comparing the information indicating the generation time points to check whether they match. system. The version check processing means, in addition to the version check process during the release, periodically, the object module after the release has taken place and the version checked, embedded as the version control information from the object module extracts the information indicating the generation time of the included information that is, from the version check target has been a corresponding date of the inclusion information the is the object module and is transferred to the object storage library of the same environment storage It is configured to extract information indicating the generation time of the include information, and to compare the information indicating the generation time and check whether or not they match. Obuji as claimed in claim 5, ECTS version check system. The generation time embedding processing means performs processing for embedding information indicating the generation time of the source program in the source program itself, in addition to processing for embedding information indicating the generation time of the include information in the include information itself. And
The compile processing means, in addition to the process of extracting information indicating the generation time of the include information from the include information used for generating the object module, in addition to the process of extracting the source program from the source program used for generating the object module. The process is also performed to extract the information indicating the generation time, and the version management includes the information indicating the generation time of the extracted include information and the information indicating the generation time of the source program in the object module itself to be generated. It is configured to embed as information,
The version check processing means is a process for extracting information indicating the generation time of the source program in addition to the information indicating the generation time of the include information embedded in the object module from the object module of the version check target In addition to the process of extracting the information indicating the generation time of the include information from the latest corresponding include information, the process of extracting the information indicating the generation time of the source program from the corresponding latest source program In addition to the process of comparing the information indicating the generation time of the include information to check whether they match, and comparing the information indicating the generation time of the source program Process to check whether or not Object version checking system according to claim 5 or 6, characterized in that it is configured to perform. An object version check method for checking a version of an object module generated by compiling using a source program and include information incorporated as a component of a program,
When generating the include information, the generation time embedding processing means performs a process of embedding information indicating the generation time of the include information in the include information itself,
Compile processing means performs the compilation using the source program and the include information to generate the object module, and information indicating the generation time of the include information from the include information used for generating the object module. Information indicating the generation time of the extracted include information is associated with module identification information for identifying the object module generated using the include information as version management information in the version management database. Write process,
The version check processing means converts the object storage library of the lower environment provided for performing stepwise program development or the object storage library of the higher environment used in the development stage further advanced from the personal work area. When releasing an object module to be transferred and stored, the object module of the release target stored in the object storage library of the lower environment or the personal work area is subjected to version check, and this object module is generated. the information indicating the generation time of the included information used, the obtains from the version management database based on the module identification information, is preceded and stored are transferred to the environment object store libraries of the upper Corresponding extracts information indicating the generation time of this include information from the latest of the included information that, to carry out processing them by comparing the pieces of information indicating these products when it is checked whether the match Feature object version check method. An object version check method for checking a version of an object module generated by compiling using a source program and include information incorporated as a component of a program,
When generating the include information, the generation time embedding processing means performs a process of embedding information indicating the generation time of the include information in the include information itself,
Compile processing means performs the compilation using the source program and the include information to generate the object module, and information indicating the generation time of the include information from the include information used for generating the object module. Performing extraction and embedding information indicating the generation time of the extracted include information as version management information in the object module itself to be generated;
The version check processing means converts the object storage library of the lower environment provided for performing stepwise program development or the object storage library of the higher environment used in the development stage further advanced from the personal work area. When releasing an object module to be transferred and stored, the object module of the release target stored in the object storage library of the lower environment or the personal work area is set as a version check target, and the object module is deleted from the object module. extracts the information indicating the generation time of the included information embedded in the module, the latest of the included information corresponding prior to being transferred to the object storage library of the host environment is stored From extracts information indicating the generation time of this include information, object version checking method, which comprises carrying out the process to which they compare information together exhibiting these production time to check whether they match. A program for causing a computer to function as the object version check system according to claim 1 .

Images