JP2003228484A - File management system and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To store and manage file history status systematically, and to consolidate media information and managing information in a list form, and to facilitate download of desired media information by a user without user's search. <P>SOLUTION: A command, which is requested by a user, is issued from a shell window 1 and input in a file management processing control part 4. In this file management processing control part 4, a setting part 2, in which a history target command is set, is prepared and a history management task 8A executes a target file 6, 7 in response to the input command. After this command is executed, prescribed history information of the executed target file is stored in a file history storing part 5 when the command from the shell window is the history target command which is set in the setting part. <P>COPYRIGHT: (C)2003,JPO

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a file management system and program for systematically storing and managing a history of file operations.

[0002]

2. Description of the Related Art Generally, a source file in which a high-level language source program is described is translated by a compiler to create an executable program load module. This load module is a loader (Lo
READER) to read the above-mentioned executable program and allocate an address to create an executable file that describes the computer-executable program. In some cases, a source file describing a source program is translated using a compiler to create an executable executable file.

By the way, when the source file A, the source file B, the execution file a, and the execution file b exist as shown in FIG. 13, the execution file a is first created by REV0 (revision 0) of the source file A. The execution file b is created by REV0 (revision 0) of the source file B. After that, the execution file a,
Although b is updated, finally, the execution file a is created by REV2 (revision 2) of the source file B, and the execution file b is created by REV1 (revision 1) of the source file A. .

However, in the conventional file management system, when the execution files a and b are updated by another source file in accordance with the purpose of use, change of business condition, system change, etc. during file development, the update date of the file Since it has been recorded, the file update date can be displayed at a later date, but other various circumstances are not recorded. On the other hand, files created during software development are often saved as they are.

[0005]

Therefore, in the above file management system, the following various problems have been pointed out.

(1) When the execution file is updated,
It is possible to display the update date of the executable file, but since there is no history of file operations, for example, the system hardware or software support contract period has expired, or a new system is moved due to a failure. In case of
Although some files are still under development, there is a problem that it takes a lot of time to determine the progress of the execution file created, that is, the target file of the update process.

(2) In addition, although an executable file is developed based on the source file, it is not possible to prepare all the staff at the time of the development, and since it is the development several years ago, I remember the detailed course of the development. In many cases, there is a problem that it takes a long time to determine which source file is used to create the execution files a and b, and wastes labor.

(3) Similarly, when there is an executable file with the same file name, there is a problem that it cannot be determined from which source file the executable file was created.

(4) Further, since the judgment is made while relying on the memory of a person, there is a point that accuracy is insufficient.

The present invention has been made in view of the above circumstances, and provides a file management system and program that systematically stores and manages the file history status such as the file operation process, and can respond to the status change promptly and accurately. The purpose is to do.

[0011]

[Means for Solving the Problems] (1) In order to solve the above problems, a file management system according to the present invention is
For example, a shell window for generating a file operation history command, history target command setting means for setting a history target command in advance, command execution means for executing a target file based on a command generated from the shell window, and the shell When the command input from the window is a history target command set in the history target command setting means, a file history storing means for storing predetermined history information of the target file executed by the command executing means is provided. It is a composition.

According to the present invention having the above-mentioned configuration, when a command of file operation history is generated from the shell window, the command executing means generates a file to be executed from the source file based on the file operation history command. Perform the operation. Subsequently, the command input from the shell window is compared with the history target command set in the history target command setting means, and if the input command exists as the history target command, the operation history information of the file is acquired and the predetermined file Since it is stored in the storage area, it is possible to easily grasp which source file revision has created the execution file in the past, and it is possible to quickly and easily start software development even if there is no development staff at that time.

The command generated from the shell window depends on the user's request, and examples thereof include file move, file copy, file edit, and file delete.

(2) Further, the functions of the system as described above can be similarly realized by storing the program in the program memory and causing the computer to read the program.

[0015]

BEST MODE FOR CARRYING OUT THE INVENTION Embodiments of the present invention will be described below with reference to the drawings.

(Embodiment 1) FIG. 1 is a system configuration diagram showing an embodiment of a file management system according to the present invention.

This file management system includes a dedicated shell window 1 for outputting a command for realizing a user's request, and a history target command setting section 2 for setting a file operation history as a target command in advance based on the user's request. And a history number setting unit 3 for setting the number of history records to be retained as history based on past experiences of software developers and the like.
And a file management processing control unit 5 including a history management software 4 which is a program for realizing a required file management process according to a command generated from the shell window 1 and a CPU, and a file history storage unit 6. Has been. Reference numeral 7 is a source file, and 8 is an execution file.

The shell window 1 is a program for generating a file operation history command for giving an instruction to the OS (operating system) which is the basic software of the system in order to realize the user's request. It has a function to generate commands for creating development software, and is a kind of user interface.

Although the history target command setting unit 2, the history number setting unit 3, and the file history storage unit 6 are described as independent in the drawing, for example, they are divided into areas in an external storage device which is the same recording medium. Alternatively, the required information may be stored.

The file management processing control unit 5 receives a command from the shell window 1 and the history management task 4 executes a series of program processing according to the command. A file operation history command executing means 41 for compiling the source program of the source file 7 with the compiler to create the execution file 8 based on the file operation history command to be executed, and an input command from the shell window 1 and a history target command after execution of this command. Whether or not there is a history target command that stores the file operation history corresponding to the input command by comparing it with the history target command set in the setting unit 2, that is, whether or not to save the file operation history Judgment means 42 and judgment to save the file operation history When the command execution date, creation date of the executable file, and the file history content acquisition unit 43 for acquiring a file operation history revision etc. of the source file 7 is provided.

In the file management processing control unit 5, the number of file histories stored in the file history storage unit 5 (serial number or serial number of each file history) and the number of set items set in the history number setting unit 3 ( When the file operation history information is saved this time, it is determined whether the number of file histories exceeds the set number, and when it is determined that the number of file histories exceeds the set number, the maximum number of file history saving section 6 is determined. A history record number judging means 44 for deleting old history information and a file operation history saving means 45 for saving the file operation history acquired by the file history content acquisition means 43 in the file history saving part 6 are provided.

Reference numeral 46 is a file management software of the OS, which is provided for the file history content acquisition means 43 to acquire the command execution date and the execution file creation date.

FIG. 2 is a diagram showing the directory structure of the system according to the present invention. FIG. 2A is a directory structure of the source file area 11 and the execution file area 12 on the hard disk, and FIG. 2B is a file structure. The directory structures of the source file history storage area 11a and the execution file history storage area 12a in the history storage unit 6 are shown. These two directory structures are exactly the same. The source file name xxx of the source file 7 is also added to the file history saving area saved in the file history saving unit 6 (see FIG. 1).

Next, the operation of the system configured as described above and the processing of the history management task which is a program for executing a series of processing will be described with reference to FIG.

After the operation of the system is started, when the command of the file operation history is acquired from the shell window 1 (S
1) Issue a command execution request to the compiler and start the compiler. This invoked compiler is based on the acquired file operation history command,
An execution file 8 which is a program executable by a computer is created from the source file 7 (S2). These S
Reference numerals 1 and S2 correspond to the file operation history command execution function.

At this time, the OS file management task 46
The command execution date is acquired from and stored in an appropriate storage means (S3).

Further, based on the command of the file operation history from the shell window 1, the history target command set in the history target command setting section 2 is referred to, and the acquired file operation history command becomes the file operation history save target. It is determined whether or not (S4: history saving permission / inhibition determination function). If the file is not to be saved, the file operation history is not saved.

On the other hand, when it is determined that the data is to be saved,
The creation date of the execution file 8 is acquired from the file management task 46 of the OS (S5), and the revision of the execution file (source file history serial number) is acquired (S5).
6). These S3, S5, and S6 correspond to the file operation history content acquisition function.

Subsequently, the number of file histories saved in the file history saving unit 6 (for example, the serial number of the source file history) is compared with the number of settings set in the history number setting unit 3 (S7), and the current file operation is performed. When it is determined that the number of operation histories exceeds the set number when the history information is saved, the oldest file operation history information in the file history saving unit 6 is deleted (S8). These S7 and S8 correspond to the file operation history number determination function.

As described above, when the number of operation history records exceeds the set number, the oldest file operation history information or simple file history information is deleted, and when the number of history records has not reached the set number, the file history In the execution file history storage area of the storage unit 6, file operation history information such as serial numbers, command execution execution dates and times, input commands, source file revisions, execution file creation dates, and other necessary items is stored (S9).

Therefore, according to the above embodiment, when the file operation history command from the shell window 1 corresponds to the history target command, the necessary file operation history information by executing the compiler is saved, It is possible to easily grasp which revision of the source file 7 has created the execution file 8 in the past, and it is possible to start software development easily and quickly even if there is no development staff at that time.

(Second Embodiment) FIG. 4 is a system configuration diagram showing another embodiment of the file management system according to the present invention. In the figure, the same parts as those in FIG. 1 are designated by the same reference numerals, and the details will be referred to the description of FIG.

This system is an example of executing a file move command, and a shell window 1 for outputting a file move command, at least a history subject command setting section 2 in which the file move command is set as a history subject command, a history Number setting part 3, history management task 4
A file management processing control unit 5 and a file history storage unit 6 are provided.

The file management processing control unit 5 has a file move command executing means 51 for executing a file move command input from the shell window 1, an input file move command and a history target command setting unit 2.
History saving propriety determining means 52 for determining whether to save the file movement history state based on the history target command
When it is determined that the file move history is to be saved, the file move history content acquisition unit 53 that acquires the required file move history contents, the history number determination unit 54, and the source source file history of the file history saving unit 6 After moving all the source source file history information in the storage area, the file source history storing means 55 for moving and storing the source source file history information in the source file history storage area and the source source file 7 being deleted after storing the file source history information. And the source file deleting means 56 for moving source.

Next, the operation of the system as described above and a series of processing examples by the program will be described with reference to FIG.

After the operation of the system is started, when the file move command is obtained from the shell window 1 (S11), the source file 7 is based on this command, as shown in FIG. (B) Move to the area (S12). S11 and S12 correspond to the file move command execution function.

At this time, the OS file management task 46
The command execution date is acquired from and stored in an appropriate storage means (S13).

Further, based on the file move command from the shell window 1, the history target command set in the history target command setting section 2 is referred to, and it is judged whether or not the file move command is a file history save target. (S14: File move history save availability determination function) If the file is not the save target, the file move history is not saved.

On the other hand, when it is determined that the file migration history is to be stored, the creation date of the source file 7a after migration is acquired from the OS file management task 46 (S1).
5) Further, the revision of the execution file (serial number of the source file history) is acquired (S16). These S13,
S15 and S16 correspond to the file transfer history content acquisition function.

Subsequently, the number of file histories stored in the file history storage unit 6 (1. serial number or 4. serial number of source file history) is compared with the number of set items set in the history number setting unit 3 (S17). ) If the number of history records exceeds the set number when the current file movement history is stored, the oldest file history information in the file history storage unit 6 is deleted (S18). These S17 and S18 correspond to the file movement history number determination function.

When the file history information is deleted as described above, or when the number of file history items has not reached the set number, the source file history information of the source file in the source file history storage area of the file history storage section 6 is deleted. Are moved and saved in the source file history saving area after moving (see (a ′) → (b ′) in FIG. 6B). Further, the file operation history information of the serial number, the command execution execution date and time, the input command, the revision of the source file of the move source, the creation date of the source file after the move and other necessary items is saved (S19: file move history save function).

After that, the migration source source file in the migration source source file history saving area is deleted (S20: migration source source file deletion function).

Therefore, according to the above-described embodiment, when the file move command from the shell window 1 corresponds to the history target command, for example, the move status of the source file is saved, so that the source file 7a does not depend on which one. It is possible to easily grasp whether the file has been moved from the source source file history storage area.

(Third Embodiment) FIG. 7 is a system configuration diagram showing another embodiment of the file management system according to the present invention. In the figure, the same parts as those in FIGS. 1 and 4 are designated by the same reference numerals and the details thereof will be referred to the description of FIGS.

This system is an example of executing a file copy command, and a shell window 1 for outputting a file copy command, a history target command setting section 2 in which at least the file copy command is set as a history target command, and the number of history records A setting unit 3, a file management processing control unit 5 having a history management task 4, and a file history storage unit 6 are provided.

In the file management processing control unit 5, the file copy command executing means 61 for executing the file copy command input from the shell window 1 and the input file copy command and history target command setting unit 2 are set. History saving possibility determination means 62 for determining whether or not to save the file copy history state based on the history target command to be stored, and a required file copy history content when the file copy history is determined to be saved. A file copy history content acquisition unit 63, a history number determination unit 64, and a file copy history storage unit 65 for storing copy history information in the file history storage area of the file history storage unit 6 are provided.

Next, the operation of the system as described above and a series of processing examples by the program will be described with reference to FIG.

When the file copy command is acquired from the shell window 1 after the system operation starts (S2
1) Based on the acquired command, copy is executed based on the file 6 or 7 that is the copy source, and the file 6b or 7b after copying is created (S22). S2
1, S22 correspond to the file copy command execution function.

..

At this time, the OS file management task 46
The command execution date is acquired from and stored in an appropriate storage means (S23).

Further, based on the file move command from the shell window 1, the history target command of the history target command setting section 2 is referred to, and it is judged whether or not the acquired file copy command is the target of saving the copy history ( S
24: File copy history saving permission / inhibition function), the file copy history is not saved if it is not a save target.

On the other hand, when the file copy history is to be saved, the creation date of the post-copy file 7b or 8b is acquired from the file management task 46 of the OS (S25), and the revision of the copy source file (copy source file history A serial number is acquired (S26). These S23, S
25 and S26 correspond to the file copy history content acquisition function.

Subsequently, the number of file histories saved in the file history saving unit 5 is compared with the number set in the history number setting unit 3 (S27), and if the number of history items exceeds the set number, the file history saving unit 6 The oldest file history information is deleted (S28). These S27 and S28 correspond to a file copy history number determination function.

When the file history information is deleted as described above, or when the number of history records has not reached the set number, the file history storage area of the file history storage unit 6 has a serial number, a command execution date and time, an input command, The revision of the copy source file, the creation date of the file after copying, and other necessary file operation history information are saved (S1).
9: File copy history saving function).

Therefore, according to the above-described embodiment, when the file copy command corresponds to the history target command, the file copy is executed and the history information of the file copy is saved, so that the copied file is It is possible to easily grasp which copy source file has been copied.

(Fourth Embodiment) FIG. 9 is a system configuration diagram showing another embodiment of the file management system according to the present invention. In the figure, the same parts as those in FIGS. 1, 4 and 7 are designated by the same reference numerals, and the details will be omitted to the description of FIGS.

This system is an example of executing a file edit command, and the file management processing control unit 5 is inputted with a file edit command executing means 71 for executing a file edit command inputted from the shell window 1. A history saving permission judgment unit 72 for judging whether or not the file edit state is saved from the file edit command and the history target command of the history target command setting unit 2, and a required file edit history when the file edit state is judged to be saved. A file editing history content acquiring unit 73 for acquiring the contents, a history number determining unit 74, and a file editing history saving unit 75 for saving the file editing history information in the file history saving area of the file history saving unit 5 are provided. .

Next, the operation of the system and a series of processing examples of the program will be described with reference to FIG.

When the file edit command is acquired from the shell window 1 after the system operation starts (S31),
For example, the source file 7 is edited based on the acquired command, and the edited source file 7 is created (S32). S31 and S32 correspond to the file edit command execution function.

At this time, the OS file management task 46
The command execution date is acquired from and stored in an appropriate storage means (S33).

Further, based on the file edit command from the shell window 1, the history target command of the history target command setting section 2 is referred to, and it is judged whether or not the file edit command saves the edit history (S34: (File edit history save availability judgment function), the file edit history is not saved if it is not a save target.

On the other hand, when it is determined that the data is to be saved,
The last edit date of the source file is acquired from the OS file management task 46 (S35), and the revision of the source file (serial number of the source file history) is acquired (S36). These S33, S35, and S36 correspond to the file edit history content acquisition function.

Subsequently, the number of file histories saved in the file history saving section 6 is compared with the number of settings set in the history number setting section 3 (S37), and if the number of histories exceeds the set number, the file history is saved. The oldest file history information of section 6 is deleted (S38). These S37, S38
Corresponds to the file edit history number judgment function.

When the file history information is deleted as described above, or when the number of file editing history items has not reached the set number, the file history saving area of the file history saving unit 6 stores a serial number, command execution date and time, The input command, the revision of the source file, the last edit date of the source file, and other necessary file history information are saved (S39: file edit history saving function).

Therefore, according to the above embodiment, when the file edit command corresponds to the history target command, by saving the file edit history state,
It is possible to grasp which source file was edited and when.

(Fifth Embodiment) FIG. 11 is a system configuration diagram showing another embodiment of the file management system according to the present invention. In the figure, the same parts as those in FIGS. 1 and 4 are designated by the same reference numerals, and the detailed description thereof will be omitted from the description of FIGS.

This system is an example of executing a file deletion command, and the file management processing control unit 5 is input with file deletion command execution means 81 for executing the file deletion command input from the shell window 1. A history savability determination unit 82 that determines whether or not to save the file deletion state based on the file deletion command and the history target command of the history target command setting unit 2, and a required file editing history when it is determined to save the file deletion state. A file edit history content acquisition unit 83 for acquiring the content, a history number determination unit 84, and a file edit history storage unit 85 for storing the file deletion history information in the file history storage area of the file history storage unit 5 are provided. .

Next, the operation of the above system and a series of processing of the program will be described with reference to FIG.

When the file deletion command is acquired from the shell window 1 after the operation of the system is started (S41),
For example, the source file 6 is deleted based on the acquired command (S42). S41 and S42 correspond to the file delete command execution function.

At this time, the OS file management task 46
The command execution date is acquired from and stored in an appropriate storage means (S43).

Further, referring to the history target command of the history target command setting section 2, it is judged whether or not the acquired file deletion command is the target of history storage (S44: file deletion history storage availability determination function). The file deletion history is not saved if the history is not saved.

On the other hand, when it is determined that the file deletion history is to be stored, the revision of the source file (serial number of the source file history) is acquired (S45). These S43 and S45 correspond to the file deletion history content acquisition function.

Subsequently, the number of file histories saved in the file history saving unit 6 is compared with the number of set items set in the number of history items setting unit 3 (S46), and if the number of file history items exceeds the set number of files, the file history is set. The oldest file history information in the storage unit 6 is deleted (S47). These S4
6, S47 corresponds to a file deletion history number determination function.

As described above, if the file history information is deleted or the number of file deletion history items has not reached the set number, the source file is deleted in the file history saving area of the file history saving unit 6. , The creation date of the source file cannot be retrieved. Therefore, after saving only the serial number, the command execution execution date and time, the input command, and the revision of the source file (S38: file deletion history saving function), delete the file name. An identifier is added (S39).

When the delete command is executed, the source file disappears, but the file history information in the file history storage unit 6 remains, which may limit the capacity of the hard disk. Therefore, create a command that deletes the file history information with the identifier that deleted the source file, and make it determine whether or not to delete the target file history information. If there is a history information deletion command, the history information of the target file is deleted. It may be deleted.

Therefore, according to the above-described embodiment, when the file deletion command corresponds to the history target command, it is easy to determine which source file was deleted by saving the history of file deletion. I can figure it out.

In addition, the present invention is not limited to the above-mentioned embodiment, and various modifications can be carried out without departing from the scope of the invention. Further, the respective embodiments can be implemented in combination as much as possible, and in that case, the effect of the combination can be obtained. Furthermore, each of the above-described embodiments includes various inventions of higher and lower stages, and various inventions can be extracted by appropriately combining a plurality of disclosed constituent elements. For example, when the invention is extracted by omitting some of the constituent elements from all the constituent elements described in the means for solving the problem, the omitted part when implementing the extracted invention. Are appropriately supplemented by well-known techniques.

[0078]

As described above, according to the present invention, it is possible to systematically store and manage the file history status such as the file operation process, and to quickly and accurately execute software development in response to changes in the situation. And a program can be provided.

[Brief description of drawings]

FIG. 1 is a configuration diagram showing an embodiment of a file management system according to the present invention.

FIG. 2 is a diagram showing a directory structure of files and a history file storage area.

FIG. 3 is a flowchart illustrating an operation of the system shown in FIG. 1 and a processing example by a program.

FIG. 4 is a configuration diagram showing another embodiment of a file management system according to the present invention.

5 is a flowchart illustrating an operation of the system shown in FIG. 4 and a processing example by a program.

FIG. 6 is a diagram showing a directory structure of files and a history file storage area.

FIG. 7 is a configuration diagram showing still another embodiment of a file management system according to the present invention.

FIG. 8 is a flowchart illustrating an operation of the system shown in FIG. 7 and a processing example by a program.

FIG. 9 is a configuration diagram showing still another embodiment of a file management system according to the present invention.

10 is a flowchart illustrating an operation of the system shown in FIG. 9 and a processing example by a program.

FIG. 11 is a configuration diagram showing still another embodiment of a file management system according to the present invention.

FIG. 12 is a flowchart illustrating an operation of the system shown in FIG. 11 and a processing example by a program.

FIG. 13 is a diagram illustrating a conventional file system.

[Explanation of symbols]

1 ... Shell window 2 ... History target command setting section 3 ... History number setting section 4 ... History management task 5 ... File management processing control unit 6 ... File history storage 7 ... Source file 8 ... Executable file 41, 51, 61, 71, 81 ... Command executing means 42, 52, 62, 72, 82 ... History storage availability determination means 43, 53, 63, 73, 83 ... History content acquisition means 44, 54, 64, 74, 84 ... History storage means

Claims (4)

[Claims] 1. A shell window for generating a predetermined command, history target command setting means for setting history target commands in advance, command execution means for executing a target file based on a command generated from the shell window, When the command input from the shell window is a history target command set in the history target command setting means, a file history saving means for saving predetermined history information of the target file executed by the command executing means, A file management system characterized by having. 2. The file management system according to claim 1, wherein the command generated from the shell window is any one of file operation history, file move, file copy, file edit, and file delete commands. A file management system characterized by. 3. A command executing function for executing a target file based on a command from the shell window, and a command of the shell window, in a computer for executing a command generated from a shell window in which a history target command is set in advance. Is a history target command, a file history saving permission judgment function, and a file history content acquisition function for acquiring a predetermined history content of the target file when it is judged that the file history is saved by this judgment function. And a storage function of storing predetermined history information of a target file acquired by this function in a predetermined file history storage area, the computer-readable program. 4. The program according to claim 3, wherein the number of history records is newly set, and the file is stored in the predetermined file history storage area after the computer realizes the file history content acquisition function. A history that compares the number of history information items with the set number of history items, and if the number of file history information items exceeds the number of history items, deletes the oldest file history information and creates a state that can be saved in the file history saving area. The computer-readable program, which realizes a function for determining the number of cases.