JP2005267341A - Check device, program release check method, and program release check program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To easily confirm new registration or the like from the attribute of a program at the time of executing a program release. <P>SOLUTION: This check device for checking a released program comprises a present registration book storage part 15 recording the first attribute of the program at a present point, a previous registration book storage part 16 recording the second attribute of the program in the previous check, a program registration book comparison part 10 outputting the result of the comparison of the first attribute with the second attribute, and a program change list formation part 12 creating a change portion list based on the result outputted by the comparison part 16. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to a check apparatus, method, and program for automatically checking attributes of a released program.

  Conventionally, when a program is released to a core system server, the program is released through a release procedure determined in-house. As specific release procedures, the following procedures (1) to (4) were sequentially performed.

(1) The release operator drafts a release procedure document, and describes the attributes of the newly registered program, the changed program, the deleted program, etc. in the release procedure document in the core system server.

(2) The release executor presents and circulates the release procedure manual to the team leader of the release team to which the release executor belongs and the key system server administrator, and the team leader approves the release procedure manual. get.

(3) The release executor or team leader presents the release procedure document to the boss of the team leader and asks the release procedure document for approval.

(4) The release implementer releases the program to the core system server.

  In addition, related parties such as the release executor, team leader, boss, manager of the core system server, etc., based on the release procedure document, the newly implemented, changed or deleted program, etc. The attributes of can be confirmed.

  However, in some cases, the above-mentioned related parties cannot confirm the attributes of newly registered, changed, or deleted programs, etc., in actuality with the released contents. For this reason, the following secondary problems have also occurred.

[Investigation of cause of failure after emergency release]

  Conventionally, when an urgent failure occurs in a core system server, the release implementer may skip the above release procedure and release a new program corresponding to the urgent failure (hereinafter referred to as an urgent release). That said.) In this case, the release procedure document corresponding to the emergency release was created after the emergency release was performed. For this reason, if another failure caused by an emergency release occurs before the release procedure document is created, the release procedure document does not exist, so check the newly registered, changed, or deleted program by the emergency release. It was impossible to do so, and it took a lot of time and effort to investigate the cause of the failure.

[Unauthorized program release without creating a release procedure]

  Conventionally, when a program is released to a core system server by deliberately or negligently omitting the release procedure, the person concerned cannot recognize the fact.

  In this regard, the applicant is unaware of the described prior art documents.

  It is an object of the present invention to be able to easily confirm that a new registration has been made from a program attribute by executing a program release.

  In order to solve the above problems, the present invention employs the following configuration.

  The invention described in claim 1 is a check device for checking a released program. The check device includes a current register storage unit that records a first attribute of a program at a current time, a previous register storage unit that records a second attribute of a program at the time of a previous check, the first attribute, and the first attribute A program register comparing unit that outputs a result of comparing two attributes, and a program change list creating unit that creates a change list based on the result output from the program register comparing unit It is characterized by. Here, the attribute is information necessary for identifying the program, and for example, in the present embodiment, is information necessary for determining new, update, or deletion. In particular, the attribute recorded in the registration list storage unit this time is referred to as a first attribute, and the attribute recorded in the previous registration list storage unit is referred to as a second attribute.

  The invention according to claim 2 is the check device according to claim 1, wherein the first attribute and the second attribute include at least a program identifier and the latest update date and time.

  The invention according to claim 3 is characterized in that the program register comparison unit compares the first attribute and the second attribute to determine the state of the program. The check device according to item 1.

  The invention described in claim 4 is a method for checking a released program in the check device according to claim 1. The method includes a step in which the check device records a first attribute of a program at a current time in the current registry storage unit, and records a second attribute of the program at the previous check in a previous registry storage unit; A step of outputting a result obtained by comparing the first attribute and the second attribute, and a step of creating a change list based on the output result are executed.

  The invention described in claim 5 is a program used for the check device according to claim 1. The program stores, in the check device, a first attribute of the program at the present time in the current registry storage unit, a second attribute of the program at the previous check in the previous registry storage unit, A step of outputting a result of comparing one attribute with a second attribute and a step of creating a change list based on the output result are executed.

  By executing the release of the program, it is possible to easily confirm that the program has been newly registered from the attribute of the program.

  Hereinafter, an embodiment of the present invention will be described with reference to FIGS.

  FIG. 1 is an overall configuration diagram of a program release check system to which the present invention is applied. This program release check system includes a backbone system server 10 (also referred to as a check device), a mail distribution server 20, a party terminal 30, and a computer network 40.

  Among these, the core system server 10 is a computer that manages the release of the program transmitted from the party terminal 30. The mail delivery server 20 is a computer that receives information related to program release from the core system server 10 and delivers this information to the related party terminal 30 by mail. The related party terminal 30 is a computer used by a release team including a release implementer and a team leader related to a program release, a release approver including a boss and the like, or an administrator of the core system server 10. The party terminal 30 has a function of transmitting a program to be released and an attribute thereof (this attribute may be integrated with the program or a separate entity) to the core system server 10 and mail distribution. And a function of receiving e-mail from the server 20. Here, the program may be either a source program or an object program. In the present embodiment, the case of an object program will be mainly described. Here, the attribute is information necessary for identifying the program, and for example, in the present embodiment, is information necessary for determining new, update, or deletion. Further, the computer network 40 only needs to be able to perform data communication with each other by using the Internet or an intranet so that the core system server 10, the mail distribution server 20, and the party terminal 30 can communicate with each other.

  The core system server 10 and the mail distribution server 20 have a general computer hardware configuration, and as shown in FIG. 2, a processing device (CPU), a main memory (MEM) as a storage device, and an auxiliary memory. (HDD) and a communication interface (NIC) to a computer network 40 as a communication device are connected to a bus.

  The core system server 10 and the mail delivery server 20 are configured to realize a program release management function and a program release information delivery function by the CPU executing a predetermined program.

  FIG. 3 is a functional block diagram of the core system server 10 and the mail delivery server 20. The core system server 10 includes a program registration list comparison unit 11, a program change list creation unit 12, a list transfer unit 13, and other processing units 14. Each of these units is realized by the CPU of the core system server 10 executing a predetermined program. In addition, information necessary for the operation of each of these units is stored in each storage unit. The current registration list storage unit 15, the previous registration list storage unit 16, the change list storage unit 17, It has.

  First, a breakdown of information stored in each storage unit will be described. The current registration list storage unit 15 stores “current registration list”. Whenever the CPU of the core system server 10 receives a program to be released from the related party terminal 30 via the NIC, the CPU records the attributes of the program in the current registration list storage unit 15. The data structure of the registration register storage unit 15 this time is the structure shown in FIG. 4. The record serial number (No.), the following items, for example, a program identifier (program name) and its The program description language (language), the registration date of the program, the latest update date and time of the program, the updater identifier (updater ID) of the program, and the program size of the program are recorded in association with each other. It has become. In FIG. 4, the “status” field is illustrated, but this field is not necessary for the current registry storage unit 15 and is illustrated for convenience of later explanation. The CPU of the core system server 10 records the above items in the current registry storage unit 15 as attribute information each time a program to be released is received from the party terminal 30.

  The recorded data in the current registration list storage unit 15 is used for a program release check process, which will be described later. As shown in FIG. After the “current register” is backed up as the “previous register” and the “current register” continues to be updated, the “current register” and “ This is because only programs that have been updated within a predetermined period can be extracted by comparing with the “previous registration list”. For this reason, the previous registration list storage unit 16 is provided, and the data structure of the previous registration list storage unit 16 is the same as the data structure of the current registration list storage unit 15 described above.

  When the CPU of the core system server 10 detects a program updated by the program release check process (including newly registered programs and deleted programs), the breakdown of the detected programs is displayed in the change list. It comes to write out. For this reason, what is stored in the change list storage unit 17 is provided. The data structure of the change list stored in the change list storage unit 17 is basically the same as the data structure of the current registration list or the previous registration list, but the data in the “status” field shown in FIG. Are also stored in association with each other. In the “status” field, a flag indicating whether the update content is “new” registration of the program, “update” of the registered program, or “deletion” of the registered program is detected in the “status” field. It comes to record. Computer processing of the core system server 10 is advanced while using these storage units.

  On the other hand, the mail distribution server 20 includes a list reception unit 21, a mail creation unit 22, a mail transmission unit 23, and other processing units 24. Each of these units is realized by the CPU of the mail delivery server 20 executing a predetermined program. In addition, information necessary for the operation of each of these units is stored in each storage unit, and a change list storage unit 25, a mail template storage unit 26, a completed mail storage unit 27, And a mail destination storage unit 28.

  The change list storage unit 25 stores the change list received by the list reception unit 21 from the core system server 10. The e-mail template storage unit 26 stores in advance e-mail templates used when the e-mail creating unit 22 creates e-mail data. Further, the completion mail storage unit 27 is configured to store e-mail data created by the mail creation unit 22. The mail destination storage unit 28 records in advance the mail addresses of related parties such as the release implementer, team leader, boss, and core system server administrator. The computer processing of the mail distribution server 20 is advanced using these storage units.

  Next, the operation of the system of the present application will be described.

  The computer processing performed by the core system server 10 is roughly divided into two. One is that each time a program to be released is received from the related party terminal 30, the attribute of the program is recorded in the above-described current registration list, and This is a process for releasing the program to the user. Through this process, the contents of the current registration list are updated as needed. That is, the No, program name, language, registration date, latest update date, updater ID, and program size shown in FIG. 4 are updated as needed.

  Hereinafter, the update of the current registration list storage unit 15 will be described in detail when a program is newly registered, a program is updated, or a program is deleted.

[When registering a new program]

  The CPU of the core system server 10 receives the program from the party terminal 30 by FTP (File Transfer Protocol) or the like and records it in the HDD. Subsequently, the CPU of the core system server 10 acquires the program name of the program recorded in the HDD by using a function provided by an OS (Operating System). In the present embodiment, the attribute is acquired using the function provided by the OS, but it goes without saying that a function for acquiring the attribute may be provided exclusively. Then, the CPU of the core system server 10 performs the following process when the acquired program name is not recorded in the current registry storage unit 15. The CPU of the core system server 10 acquires the language, the registration date, the latest update date, the updater ID, and the program size of the program recorded in the HDD by using a function provided by the OS. Next, the CPU of the core system server 10 issues a new No (serial number), the issued No (serial number), the program name, the language, and the registration date acquired using the function of the OS. The latest update date / time, the updater ID, and the program size are associated with each other and recorded in the current registry storage unit 15 as a new record.

[When updating a program]

  The CPU of the core system server 10 receives the program from the party terminal 30 by FTP or the like and records it in the HDD. Here, if a program having the same program name as the program received from the party terminal 30 is already stored in the HDD, the CPU of the core system server 10 has already stored the program received from the party terminal 30. Overwrite the recorded program and record. Subsequently, the CPU of the core system server 10 acquires the program name of the program recorded in the HDD using a function provided by the OS. Then, the CPU of the core system server 10 performs the following process when the acquired program name is recorded in the current registry storage unit 15. The CPU of the core system server 10 acquires the latest update date / time, the updater ID, and the program size of the program recorded in the HDD using a function provided by the OS. Next, the CPU of the core system server 10 updates the latest update date and time for the same record as the program name obtained by using the function provided by the OS in the program name field in the current registry storage unit 15. Updater ID and program size are updated.

[When deleting a program]

  The CPU of the core system server 10 receives a program deletion command and a program name to be deleted from the party terminal 30 by TELNET or the like. Then, the CPU of the core system server 10 deletes the program corresponding to the program name to be deleted based on the delete command. Subsequently, the CPU of the core system server 10 deletes the record in which the value of the program name field is the same as the program name to be deleted in the current registration list.

  On the other hand, another important process executed by the core system server 10 is a program release check process (although this is executed every time a predetermined time comes). This check process will be described with reference to the functional block of FIG.

  When the program release check process is instructed, the program registration list comparison unit 11 reads the data of the current registration list at that time from the current registration list storage unit 15 and the data of the previous registration list at that time as the previous registration list. Read from the storage unit 16. Then, the two registers are compared, and a change point, that is, a mismatched portion is detected. This change is delivered to the program change list creation unit 12, and the program change list creation unit 12 creates a change list that lists only the change points in the change list storage unit 17. This process will be described with reference to the flowchart of FIG.

  The CPU of the core system server 10 reads the current registration list from the current registration list storage unit 15 and reads the previous registration list from the previous registration list storage unit 16 at a predetermined time (S1). Then, the CPU of the core system server 10 compares the record in the current registration list with the record in the previous registration list, and performs the following process (S2).

(1) When a new program name is registered in the current register

  When a record having the same program name as the record name of the record in the current registration list has not been recorded in the previous registration list, the CPU of the core system server 10 sets the record in the current registration list and the status flag “new”. Is recorded in the MEM.

(2) When the program name is deleted from the current registry

  When a record having the same program name as the program name of the record in the previous register is not recorded in the current register, the CPU of the core system server 10 sets the record in the previous register and the status flag “deleted”. Is recorded in the MEM.

(3) When the same program name is recorded in the current register and the previous register

  A record having the same program name as the program name of the record in the current register is recorded in the previous register, and the latest update date and time of the record in the current register is different from the latest update date and time of the record in the previous register Moreover, the CPU of the core system server 10 records the current registration list record and the status flag “update” in association with each other in the MEM.

  Then, the CPU of the core system server 10 repeats the processes (1) to (3) for all the records in the current registration list and the previous registration list (S3). In this embodiment, the change point is determined by comparing the record in the current registration list with the record in the previous registration list, but other methods may be used. For example, a field for inputting a flag indicating a state in the current registration list and the previous registration list is provided in advance. If there is no program that matches each record in the current registration list in the previous registration record, a flag indicating a new state is entered in the current registration list field. If a program that matches each record in the current registration list exists in the previous registration list and the latest update date / time is different, a flag indicating the update status is input to the fields of the current registration list and the previous registration list. Further, if no flag is input in the field indicating the state of the previous registration list, the program is determined as a deleted program. After such processing has been performed, the CPU of the core system server 10 has a record having flags “new”, “update”, and “delete” from among the flags indicating the status of the current registration list and the previous registration list. Even if the information is recorded in the MEM, the change point can be derived.

  Thereafter, the program registration list comparison unit 11 records the current registration list stored in the current registration list storage unit 15 in the previous registration list storage unit 16 as the previous registration list. Then, the program change list creation unit 12 stores the change list when the record of the current registration list or the previous registration list and the status flag thereof are recorded in the MEM by the processes (1) to (3). A new change list is created in the unit 17, and the record recorded in the MEM and the status flag associated with the record are recorded in the change list in the change list storage unit 17. Subsequently, the list transfer unit 13 extracts the change list from the change list storage unit 17 and transfers it to the mail delivery server 20.

  On the other hand, the mail delivery server 20 performs the following processing. The list receiving unit 21 receives the change list transmitted from the core system server 10 and stores the received change list in the change list storage unit 25. Next, based on the mail template stored in the mail template storage unit 26 and the change list stored in the change list storage unit 25, the mail creation unit 22 uses the change list as its contents. Create email data. FIG. 6 is an example of the contents of the e-mail. Subsequently, the mail creation unit 22 stores the created electronic mail data in the completed mail storage unit 27. The mail transmission unit 23 then releases the e-mail data stored in the completed mail storage unit 27 based on the mail destination stored in the mail destination storage unit 28 in advance, the team leader, the boss, and the core system. Send to related parties such as server administrator.

  According to this, the checking device compares the attribute of the current program recorded in the current registry storage unit with the attribute of the program recorded in the previous registry storage unit at the previous check, and displays the change list. Since it is created, it can be easily confirmed that the program has been newly registered from the attribute of the program by executing the release of the program.

  According to the present embodiment described above, the change can be confirmed only by releasing the program. Furthermore, according to the present embodiment, the mail delivery server transmits an email having the contents of the change list created by the core system server to the related parties. The attributes of the changed or deleted program can be confirmed.

  According to this, even if there is no release procedure document corresponding to the emergency release, a program newly registered, changed, or deleted by the emergency release can be identified by the contents of the above-mentioned mail, so it is very useful for investigating the cause of the failure. Save time and effort. In addition, when the content of the e-mail is different from the content of the latest release procedure document, the related person can recognize that an illegal program release that does not create a release procedure document has been implemented. In this case, the supervisor or the like can also instruct the release implementer to create a release procedure document afterwards, and can prevent unauthorized program release without creating a release procedure document. Furthermore, the parties concerned can share release information according to the contents of the e-mail.

  The scope of the present invention is not limited to the scope of the above embodiment, and various modifications can be made. For example, the core system server may include a mail distribution unit, and the server may distribute the notification mail. In addition, the core system server may include a detection unit that detects that a program has been released, and may deliver an email each time it is detected. Also, compare the source program itself, not the program directory, and include the contents of the changed program list, the ID of the new / changed / deleted person, the changed contents of the program (the source code change location and the changed contents are listed in parallel) May be.

It is a whole block diagram of a program release check system. It is a block diagram of a core system server and a mail delivery server. It is a functional block diagram of a core system server and a mail delivery server. It is a data structure figure of this time register. It is a flowchart of a program release check process. It is an example of the content of an email.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 Core system server 11 Program registration list comparison part 12 Program change list preparation part 13 List transfer part 14 Other processing part 15 This time register storage part 16 Previous registration list storage part 17 Change list storage part 20 Mail distribution server 21 List reception Unit 22 Mail creation unit 23 Mail transmission unit 24 Other processing unit 25 Change list storage unit 26 Mail template storage unit 27 Completed mail storage unit 28 Mail destination storage unit 30 Personnel terminal 40 Computer network

Claims (5)

A check device for checking a released program,
This time register storage unit that records the first attribute of the program at the present time;
A previous registry storage unit that records the second attribute of the program at the time of the previous check;
A program register comparing unit that outputs a result of comparing the first attribute and the second attribute;
A program change list creating unit that creates a change list based on the results output by the program register comparing unit;
A check device comprising:   The check device according to claim 1, wherein the first attribute and the second attribute include at least a program identifier and a latest update date and time.   The said program registration list comparison part compares the said 1st attribute and the said 2nd attribute, and judges the state of a program, Either of Claim 1 and Claim 2 characterized by the above-mentioned. Check device. The check apparatus according to claim 1, wherein the released program is checked.
The check device is
a) recording the first attribute of the program at the present time in the current register storage unit;
b) recording the second attribute of the program at the time of the previous check in the previous registry storage unit;
c) outputting a result of comparing the first attribute with the second attribute;
d) creating a change list based on the output result;
A program release check method characterized by executing A program used for the check device according to claim 1,
In the check device,
a) recording the first attribute of the program at the present time in the current register storage unit;
b) recording the second attribute of the program at the time of the previous check in the previous registry storage unit;
c) outputting a result of comparing the first attribute with the second attribute;
d) creating a change list based on the output result;
A program release check program characterized in that

Images