JP6199774B2 - Program management apparatus and method, and program for controlling program management apparatus - Google Patents

Description

  The present invention relates to a program management apparatus and method, and a program for controlling the program management apparatus.

  ISO / IEC15288, which is a standard relating to software life cycle processes, has a description relating to software disposal processes. However, this standard only conceptually defines the purpose and outcome of the software disposal process, and does not describe at all when and how to discard the software.

  A large number of programs are used in existing computer systems, particularly large-scale computer systems used for mission-critical business such as companies called mainframes. For example, in a computer system that executes business processing related to a credit card, more than 100,000 programs are stored in a storage device, and a large number of programs are executed according to the description of a JCL (Job Control Language) statement.

  In program (software) development, existing programs may be partially modified. In this case, in order to be able to take immediate action in the event of some system failure, in general, not only the modified program is saved, but the program before the modification is still left, and this is repeated to increase the system scale. There is a current situation of enlargement. The enlargement of the system scale leads to an increase in revision cost and maintenance cost.

  Patent Document 1 retains license information for each client, extracts unused software that has not been used for a predetermined period, and deletes registration of unused software from the license information for a long period of time. Describes a software management system that collects licenses for unused software to effectively use assets.

JP 2004-62561 A

  However, simply deleting the license information cannot avoid the above-described enlargement of the computer system caused by repeated program modifications.

  SUMMARY OF THE INVENTION An object of the present invention is to reduce the size of a computer system without human intervention by automatically saving unused programs so that they can be restored.

  A program management device according to the present invention records at least the latest used date data for each of a plurality of programs stored in a production library storing a plurality of programs used for business processing by the business processing device. First determining means for determining whether the program stored in the production library is an unused program that has not been used for a predetermined period according to the latest usage date data of the usage status management table and the program usage status management table; When the first judging means judges that the program is an unused program, the saving means for copying the program and storing it in a saving library different from the production library, and the saving means not using the saving library A copy of the program After it is stored, and a deletion means for deleting the unused program from the production library.

  According to the present invention, since unused programs that have not been used for a predetermined period are automatically deleted from the production library, only the programs that have been used within the predetermined period remain in the production library. The revision work of the production library storing a plurality of programs used for business processing by the business processing device is simplified, and the enlargement of the system scale and the increase in maintenance cost can be reduced. It is also easier to identify the scope of impact when renovating programs.

  The predetermined period for determining whether the program is an unused program can be arbitrarily set.

  Further, according to the present invention, a copy of an unused program that is deleted from the production library is left in the save library. Therefore, an unused program deleted from the production library can be returned to the production library as necessary. Since the backup library is not a library used for business processing by the business processing device, revision work to the backup library is not required, so even if a copy of an unused program is left in the backup library, maintenance costs and the like increase significantly. There is nothing.

  In one embodiment, the update means for periodically updating the latest use date data for each of the plurality of programs recorded in the program usage status management table is provided, and the update of the latest use date data by the update means is finished. Thereafter, it is determined whether or not the program is an unused program by the first determining means. The latest usage record can always be used to determine whether the program is an unused program.

  The latest use date data is preferably updated in a span linked to the processing timing of the program management apparatus according to the present invention. For example, when the program management device is started in daily processing (daily), the update of the latest use date data is also daily processing. When the program management apparatus is started in monthly processing (monthly), the update of the latest usage date data is also monthly processing.

  Preferably, date data when each program stored in the production library is registered (stored) in the production library is recorded in the program usage status management table. The program management device includes second determination means for determining, based on the registration date data, whether a predetermined period has elapsed since the program stored in the production library has been registered in the production library. Further, the saving means is determined by the first determining means to be an unused program, and determined to have passed a predetermined period after being registered in the production library by the second determining means. If this happens, the program is duplicated and stored in a save library different from the production library. In other words, even if it is an unused program, if it is a program that has just been registered in the production library, a copy of the program is stored in the save library and the program is used for production. It is not deleted from the library. It is prevented that a program newly registered in the production library and not used yet is deleted from the production library. The predetermined period used in the second determination means can also be set arbitrarily.

  In one embodiment, the program usage status management table is configured to be able to set a non-save flag for each of the programs stored in the production library, and the save unit sets the non-save flag. Skip processing for the program. Even if a non-use program or a non-use program has been registered for the production library and the specified period has passed, if a non-save flag is set, a copy of that program is saved. It is not stored in the library and the program is not deleted from the production library. For example, if a program that is used only once in a few years but is used once in a few years (such as a program used only in a leap year) is flagged as unsaveable, the program is always left in the production library. I can keep it.

  In another embodiment, the production library stores a refurbishment source program and a refurbishment destination program obtained by refurbishing the refurbishment source program, and the rehabilitation source program is refurbished in the program usage status management table. For the refurbishment source program in which the data (program name, identification number, etc.) identifying the rehabilitation destination program that has modified the original program is further recorded and the rehabilitation destination program identification data is recorded in the program usage status management table, Third determining means for further determining whether or not the renovation destination program is an unused program that has not been used for a predetermined period according to the latest use date data of the renovation destination program identified by the renovation destination program identification data, The evacuation means is the first determination means. Therefore, when it is determined that the repair source program is an unused program, and the third determination means determines that the repair destination program is also an unused program, the repair source program is copied and the production library is copied. Is stored in a different save library, and if the third determination means determines that the repair destination program is not an unused program, the processing for the repair source program is skipped.

  When the refurbishment source program and the refurbishment destination program obtained by refurbishing the refurbishment source program are stored in the production library, the refurbishment source program when the refurbishment source program is a non-use program and the renovation destination program is also a nonuse program The copy of the program is stored in the save library and the modification source program is deleted from the production library. Even if the renovation source program is a non-use program, if the renovation destination program is not a nonuse program, a copy of the renovation source program is not stored in the save library and the renovation source program is not deleted from the production library. . It is possible to delete from the production library a program that is highly likely not to affect business processing by the business processing device and that is not likely to be referenced later.

  Preferably, when the program to be executed in the business processing device is not stored in the production library, a search for searching the save library for the program to be executed according to an error message output from the business processing device And a recovery means for copying the program to be executed found by the search means and storing it in an emergency library that is different from the production library and the save library and accessible by the business processing device. As described above, in the program management apparatus, a copy of the unused program deleted from the production library remains in the save library. By copying the program remaining in the backup library to the emergency library and making this emergency library accessible on the business processing device, even if it is a program once deleted from the production library, the business processing on the business processing device Can be used. Since the emergency library is not a library that always stores the program used by the business processing device for business processing, the program copied to the emergency library is stored (returned) in the production library by the operator.

  Preferably, in the statement defining the program to be executed in the business processing device, the production library and the emergency library are written together with the emergency library in a high priority as a library in which the program is stored. Yes. As a result, the business processing apparatus can execute the program copied to the emergency library.

  The present invention also provides a method and program for controlling the above-described program management apparatus.

FIG. 2 is a block diagram schematically showing a business processing computer system and a program management computer system. It is a block diagram which shows the flow of the movement of the program between a production library, an evacuation library, and an emergency library. The program usage status management table is shown. It is a flowchart which shows the flow of a process of an evacuation processing program. It is a flowchart which shows the flow of a process of an evacuation processing program. It is a flowchart which shows the flow of a process of an evacuation processing program. It is a flowchart which shows the flow of a process of a recovery process program. The program usage condition management table of a modification is shown. Indicates the program generation relationship. It is a flowchart which shows the flow of a process of the save process program of a modification.

  FIG. 1 schematically shows a business processing computer system and a program management computer system.

  The business processing computer system 10 performs predetermined business processing (job) according to the description of the given JCL statement 11, such as authentication processing, usage record recording processing, invoice issuance processing, consumption tax addition in the case of a credit card system. It is a system that executes processing. The JCL statement 11 describes a job execution instruction, a program name to be executed in the job, a library name for storing the program to be executed, an input file name, an output file name, a storage device name for storing the processing result, and the like. , The operation of the business processing computer system 10 is controlled according to the description of the JCL statement 11. That is, the business processing computer system 10 reads the input file stored in the storage device 12 connected to the business processing computer system 10 according to the given JCL statement 11, and stores it in a production library or the like to be described later. A predetermined process (job) is performed using the program, and the processing result is recorded in the output file. One job executes one or a plurality of programs. One program may be commonly used for a plurality of jobs.

  A program used for a job executed in the business processing computer system 10 is stored in a production library 31 that is a storage device connected to the business processing computer system 10. That is, the business processing computer system 10 reads the program specified by the program name described in the JCL statement 11 from the production library 31 and executes it. The production library 31 stores a large number of programs, for example, tens of thousands.

  Further, an emergency library 33 which is a storage device different from the production library 31 is connected to the business processing computer system 10. The emergency library 33 normally does not store anything. As will be described in detail later, when the program to be executed in the business processing computer system 10 is not stored in the production library 31, the program to be executed is temporarily stored in the emergency library 33. Programs temporarily stored in the emergency library 33 are also used for jobs by the business processing computer system 10.

  In the JCL statement 11 described above, the two library names of the production library 31 and the emergency library 33 described above are written together with the emergency library 33 in high priority as storage library names of programs to be executed. By describing the JCL statement 11 in this way, the business processing computer system 10 first searches the emergency library 33 for a program having the program name described in the JCL statement 11, reads it, and finds it in the emergency library 33. If there is not, control is performed so as to search and read out in the production library 31 next time.

  The program management computer system 20 is a computer system used together with the business processing computer system 10, and is a system for managing a large number of programs stored in the above-described production library 31 (also referred to as a library management system). it can). The above-described production library 31 and emergency library 33 are also connected to the program management computer system 20.

  An evacuation library 32 is further connected to the program management computer system 20. As will be described later, the save library 32 stores a copy (copy) of a program stored in the production library 31 that has not been used for a certain period of time (hereinafter referred to as an unused program). After the copy of the unused program is stored in the save library 32, the unused program is deleted from the production library 31. As will be described later, when the program to be executed in the business processing computer system 10 is not stored in either the production library 31 or the emergency library 33, the program management computer system 20 stores the program to be executed. A process of searching from the backup library 32 and moving to the emergency library 33 (a process of copying to the emergency library 33 and deleting from the backup library 32) is also performed.

  A program for controlling the program management computer system 20 is stored in a storage device 21 connected to the program management computer system 20. The storage device 21 stores a program usage status management table, a save processing program, and a recovery processing program, which will be described later. Details of these tables and programs will be described later.

  FIG. 2 schematically shows the flow of program transfer between the above-described production library 31, save library 32, and emergency library 33.

  The production library 31 stores a large number of programs executed by the business processing computer system 10 as described above. Here, among the many programs stored in the production library 31, there are programs that are not used at all later by the business processing computer system 10. This is because program development (construction of the production library 31) is generally performed by modifying a part of an existing program.

  In other words, when refurbishing a business processing computer system 10 that is already in operation, all the programs stored in the production library 31, that is, all the programs stored in the production library 31, must be replaced with newly created programs all at once. Is not generally done. This is because continuous service provision (business processing) may be hindered. When the business processing computer system 10 that is already in operation is repaired, only a few programs required for the repair among the many programs stored in the production library 31 are repaired. Furthermore, with regard to program modifications, the entire program is not generally rewritten, but only a part of it is rewritten. When the program is partially modified, the modified program is newly stored in the production library 31. At this time, the program that has been used before is also left in the production library 31 although it is unlikely that it will be used after that. This is also in order to prevent continuous service provision from being hindered by making the pre-repair program ready to be used if there is any defect in the post-repair program. . This is why the production library 31 has something that will not be used at all later by the business processing computer system 10.

  As will be described in detail later, the program management computer system 20 performs processing for saving unused programs that have not been used for a predetermined period among the many programs stored in the production library 31 to the save library 32 (in the save library 32). The process of storing the copy and deleting it from the production library 31 is executed. As a result, there is no unused program in the production library 31 that has not been used for a long time. Since only the programs used by the business processing computer system 10 within a predetermined period are stored in the production library 31, the repair work can be performed smoothly thereafter, and maintenance costs can be reduced. Can be planned. It is also easy to identify the scope of impact when renovating a program.

  Further, as will be described in detail later, the program management computer system 20 saves the program when the business processing computer system 10 requests execution of a program not stored in the production library 31 and the emergency library 33. To the emergency library 33 (processing for storing a copy in the emergency library 33 and deleting it from the save library 32). The program restored in the emergency library 33 is then re-registered in the production library 31 by the operator.

  FIG. 3 shows a program usage status (usage record) management table 21A stored in the storage device 21 of the program management computer system 20.

  The program usage status management table 21A includes data records for each of a large number of programs stored in the production library 31, and each data record includes the program name, the latest use date, the registration date, and the save date. Each data item of the impossible flag is recorded.

  The “program name” is a name unique to each program stored in the production library 31. The program name is described in the JCL statement 11 described above.

  “Latest use date” is the latest date when the program was used. The latest use date is updated according to the program execution history data described in the system log created by the business processing computer system 10 (its operating system).

  “Registration date” is the date when the program is stored (registered) in the production library 31. When a program is registered in the production library 31 by an operator (librarian), the registration date may be automatically recorded by the business processing computer system 10 (its operating system).

  The “non-saving flag” is a flag indicating that the program is not a target of the saving process described below. A program for which the evacuation impossible flag is set is excluded from the evacuation process described later.

  4 to 6 are flowcharts showing the flow of operations of the program management computer system 20 controlled by the save processing program.

  The save processing program is executed daily at a predetermined time, for example, by daily processing. First, according to the usage record for one day, the latest usage date of the program usage status management table 21A is updated (step 41). As described above, the business processing computer system 10 (its operating system) creates a system log including execution history data of programs executed by the business processing computer system 10. The latest use date is updated based on this log.

  Counter i is initialized (step 42). For each of all programs registered in the program usage status management table 21A (that is, all programs stored in the production library 31), the following processing is performed using the data in the program usage status management table 21A. (NO in step 43) (the number of programs managed in the program usage status management table 21A is “N” here).

  It is determined whether the program has been used in the past year (step 44). The latest use date is used for this determination. It is determined whether the period from the machine time (that is, the current date) of the program management computer system 20 to the latest use date is within one year.

  If it is used within one year, the counter i is incremented and the process proceeds to the next program (NO in step 44, step 48). That is, the saving process is skipped.

  If one year has passed since the most recent use date (YES in step 44), it is then determined whether three days have passed since the registration date (step 45). The registration date is used for this determination. This is to prevent a program that has been newly stored in the production library 31 and has not been used yet from being stored and immediately saved because there is no record of use. In general, development work is performed until just before the program is actually used. Therefore, when a program is newly stored in the production library 31, the program is stored in the production library 31 immediately before use. The

  If a few days have passed since the registration date, in this case three days, that is, if it is determined that the program is newly stored in the production library 31, the counter i is incremented and processing for the next program is performed. Proceed (NO at step 45, step 48). That is, the saving process is skipped.

  If three days have passed since the registration date (YES in step 45), it is next determined whether or not there is an evacuation flag (step 46). When the save disable flag is set in the program usage status management table 21A (NO in step 46), the program is forcibly removed from the save process. For example, an evacuation impossible flag is set in a program related to a leap year that is executed only once every four years. In addition, a program that has been restored from the save library 32 to the emergency library 33 by a restoration process, which will be described later, is also flagged when the program is re-registered in the production library 31. In any case, if the save disable flag is set, the counter i is incremented and the process proceeds to the next program (step 48). That is, the saving process is skipped.

  If the program has not been used for the past year, 3 days have passed since the date of registration, and no evacuation flag is set (YES at step 44, YES at step 45, YES at step 46) Copy parameters and delete parameters for the program (hereinafter referred to as the save target program) are created (step 47).

  According to the created copy parameter, the save processing program reads the save target program from the production library 31 and creates a copy thereof (steps 51 and 52 in FIG. 5). A copy of the created save target program is stored (registered) in the save library 32 (step 53).

  Further, according to the created delete parameter, the save processing program deletes the save target program from the production library 31 (step 61 in FIG. 6). Further, the save processing program deletes the data record for the save target program deleted from the production library 31 and stored in the save library 32 from the program usage status management table 21A (step 62).

  The above-described processing is performed for all programs (all programs stored in the production library 31) managed in the program usage status management table 21A. When processing for all programs is completed, the processing of the save processing program ends (YES in step 43).

  Through such processing, for example, a program such as “do not issue a bill to the affected area at the time of a large-scale disaster” is deleted from the production library 31 and stored in the save library 32.

  For a program deleted from the production library 31 and stored in the save library 32, a table may be created that stores data such as the program name and the date stored in the save library 32.

  The processing order of steps 44, 45, and 46 is arbitrary. For example, whether a program that has not passed 3 days from the date of registration or a program that has a flag that cannot be saved is excluded from processing, and the remaining programs have passed 1 year from the most recent use date You may decide whether.

  FIG. 7 is a flowchart showing an operation flow of the program management computer system 20 controlled by the recovery processing program.

  As described above, the business processing computer system 10 reads a program necessary for a job from the emergency library 33 or the production library 31 and executes it according to the description of the given JCL statement 11. If the program to be executed is not stored in either the emergency library 33 or the production library 31, the business processing computer system 10 (its operating system) temporarily ends the job and selects the program name that could not be executed. Output error message including. The recovery processing program is activated when this error message is output by the business processing computer system 10.

  The recovery processing program searches the backup library 32 for the program that caused the job termination according to the error message output from the business processing computer system 10 (step 71). As described above, when deleting the save target program from the production library 31, the program management computer system 20 stores a copy of the program in the save library 32. For this reason, a program previously stored in the production library 31 but later deleted from the production library 31 is stored in the save library 32. The program specified by the error message is highly likely to be stored in the save library 32.

  When the program specified by the error message is found in the save library 32, the recovery processing program copies the found program and stores (registers) it in the emergency library 33 (step 72). Preferably, the recovery processing program deletes the copied program from the save library 32 (step 73).

  When the program is copied to the emergency library 33, a re-execution command for the JCL statement 11 that caused the job to end is given from the program management computer system 20 to the business processing computer system 10, and the business processing computer system 10 causes the job to end. Execute JCL statement 11 again. As described above, in the JCL statement 11, two libraries, the emergency library 33 and the production library 31, are written together with the emergency library 33 as a higher priority as a storage library of programs to be executed. Therefore, when the JCL statement 11 is re-executed, the program copied from the save library 32 to the emergency library 33 is read, and the job is executed normally.

  The program stored in the emergency library 33 by the recovery processing program is re-registered in the production library 21 by the operator of the business processing computer system 10 and deleted from the emergency library 33 after the re-registration is completed. In addition, for a program re-registered in the production library 21 from the emergency library 33, a program that has been re-registered in the production library 21 is subsequently retrieved from the production library 21 by setting a non-saveable flag in the program usage status management table 21A. It can be prevented from being deleted.

  In the embodiment described above, the program management computer system 20 has been described as a computer system separate from the business processing computer system 10, but the processing of the program management computer system 20 can also be executed by the business processing computer system 10. In this case, an execution instruction for the save process program, an execution instruction for the recovery process program, and the like are written in the JCL statement 11 described above, and the JCL statement 11 is read into the business process computer system 10 so that the business process computer system 10 operates as a program management computer system 20.

  In the above-described embodiment, it is assumed that the program stored in the production library 31 or the like is an execution module, but it may be a source code. In general, an execution module is created by compiling source code with a compiler to create object code, and linking a plurality of object codes with a linker. The programs copied from the production library 31 to the save library 32 and deleted from the production library 31 and the programs copied from the save library 32 to the emergency library 33 are both the above-described execution modules and source codes. Alternatively, only the execution module or the source code may be used.

  FIG. 8 shows a program usage status management table 21B of another embodiment. The program usage status management table 21A shown in FIG. 3 includes data items “repair source program name” and “renovation destination program name” in the data record for each of a large number of programs stored in the production library 31. Differences are added.

  As described above, when modifying a program, the entire program is generally not rewritten, and only a part of the program is rewritten. The “renovation source program name” is the name of the program that is the basis of the refurbishment when the program is refurbished. The modification source program name is recorded in a data record for the modified program (renovation destination program). On the other hand, “renovation destination program name” is the name of the renovated program. The name of the program to be repaired is recorded in a data record for the program that is the source of the repair (the repair source program).

  Referring to FIG. 9, it is assumed that, for example, a part of the program with the program name “P00001” is modified, and two programs with the program names “P00021” and “P00045” are newly created and registered in the production library 31. To do. In this case, the program names “P00021” and “P00045” are recorded in the data item “repair destination program name” of the data record for the program name “P00001” (see FIG. 8). On the other hand, the “renovation source program name” of the data record for the program with the program name “P00021” created by refurbishing a part of the program name “P00001” includes the program name “P00001” that is the source of the renovation. Recorded (see FIG. 8). Similarly, the data name of the program with the program name “P00045” created by refurbishing a part of the program name “P00001” is changed to “renovation source program name” and the program name “P00001”. Is recorded (not shown).

  By refurbishing a part of each of the two programs named “P00021” and “P00045” created by modifying a part of the program named “P00001”, the program from the program named “P00021” Assume that two programs with names “P00123” and “P00234” are created from programs with program names “P00045” and program names “P00345” and “P00456”, respectively. Also in this case, in the “repair source program name” of the data record for the newly created program, for example, the program with the program name “P00123”, the program name of the program that is the source of the repair, here “P00021”. Is recorded (see FIG. 8). Program names “P00123” and “P00234” are recorded in “repair destination program name” of the data record of the program name “P00021” (see FIG. 8). In this way, generation data (association data representing the relationship between the parent, the child, and the grandchild) is recorded in the program usage status management table 21B when the program is modified.

  FIG. 10 shows a flow of processing of the save processing program when the above-described program usage status management table 21B is used, and is a flowchart corresponding to FIG. 4 is different from the flowchart of FIG. 4 in that the process of step 49 is added.

  If the program has not been used for the past year (YES in step 44), 3 days have passed since the registration date (YES in step 45), and the program cannot be saved (a program to be saved) (step to be saved) If YES in 46), it is further determined whether or not the renovation destination program has been unused for the past year (step 49). Referring to FIG. 9, for example, even if the program with the program name “P00001” is a program to be saved, the next-generation (child) renovation destination program or the next-generation (grandchild) renovation-destination program has been in the past year. If it is used, the modification source program with the program name “P00001” is excluded from the save target (NO in step 49). When the next generation or all of the next generation renovation destination programs have not been used for the past year, the process proceeds to the subsequent evacuation process (YES in step 49). Note that the period for determining whether or not the renovation source program is an unused program (step 44) may be the same as or different from the period for determining whether or not the renovation destination program is an unused program (step 49). May be.

  In this modification, when the repair destination program has been used relatively recently, the repair source program remains in the production library 31 even if it has not been used relatively recently. In addition, since the program usage status management table 21B also stores the name of the modification source program, the modification source program remaining in the production library 31 can be traced when the program is modified. In this modified example, a program group (a program group considered to have already completed its mission) in which neither the modification source program nor the modification destination program is used is deleted from the production library 31. It is possible to delete from the production library 31 a program that is highly likely not to affect business processing performed by the business processing computer system 10 and that is not likely to be referenced later.

10 Business processing computer system (business processing device)
11 JCL statement
12, 21 storage device
20 Program management computer system (program management device)
21A, 21B Program usage status management table
31 Production library
32 Backup library
33 Emergency library

Claims (8)

A program usage status management table that records at least the latest used date data for each of a plurality of programs stored in a production library storing a plurality of programs used for business processing by a business processing device;
First determination means for determining whether the program stored in the production library is an unused program that has not been used for a predetermined period according to the latest usage date data of the program usage status management table;
Save means for copying the program and storing it in a save library different from the production library when it is determined by the first determination means that the program is an unused program ;
After copies of the unused program save library is stored by the upper Symbol retreating means, deleting means for deleting the unused program from the production library, and
Updating means for periodically updating the latest usage date data for each of the plurality of programs recorded in the program usage status management table;
After the update of the latest use date data by the updating means, it is determined whether or not the program is an unused program by the first determining means.
Program management device. In the program usage status management table, date data when each program stored in the production library is registered in the production library is recorded.
A second determination means for determining, based on the registration date data, whether or not a predetermined period has elapsed since the program stored in the production library has been registered in the production library;
The evacuation means is
When the first judging means judges that the program is an unused program, and the second judging means judges that a predetermined period has elapsed since registration in the production library, the program is copied. And store it in a backup library different from the above production library,
The program management apparatus according to claim 1 . The program usage status management table is configured so that a non-saveable flag can be set for each of the programs stored in the production library,
The evacuation means is
Skip processing for programs that have the above flag set to prevent evacuation,
Program management apparatus according to claim 1 or 2. The above-mentioned production library stores a renovation source program and a renovation destination program obtained by refurbishing the above renovation source program.
In the program usage status management table, data for identifying the refurbishment destination program that has refurbished the refurbishment source program is further recorded for the refurbishment source program.
For the repair source program whose repair destination program identification data is recorded in the program usage status management table, the repair destination program is determined in accordance with the latest use date data of the repair destination program specified by the repair destination program identification data. A third determination means for further determining whether the program is not used for a period of time;
The evacuation means is
When the first determining means determines that the repair source program is an unused program and the third determining means determines that the repair destination program is also an unused program, the repair source program is copied Is stored in a backup library different from the actual library, and when the third determination means determines that the repair destination program is not an unused program, the processing for the repair source program is skipped.
The program management apparatus as described in any one of Claim 1 to 3 . Search means for searching the save library for the program to be executed in accordance with an error message output from the business processor when the program to be executed in the business processor is not stored in the production library; A recovery means for copying the program to be executed found by the search means and storing it in an emergency library that is different from the production library and the save library and accessible by the business processing device;
The program management apparatus as described in any one of Claim 1 to 4 . In the statement defining the program to be executed in the business processing device, the production library and the emergency library are written together with the emergency library in high priority as a library in which the program to be executed is stored. Is,
The program management apparatus according to claim 5 . Program management including a program usage status management table for recording at least the latest used date data for each of a plurality of programs stored in a production library storing a plurality of programs used for business processing by a business processing device A method of controlling a device,
According to the latest usage date data in the program usage status management table, it is determined whether the program stored in the production library is an unused program that has not been used for a predetermined period of time.
If it is determined that it is an unused program, the program is copied and stored in a backup library different from the production library,
After copies of the unused program is stored in the save library, delete the unused program from the production library,
Update the latest usage date data for each of the multiple programs recorded in the program usage status management table,
After updating the latest use date data, proceed to determine whether it is an unused program.
Method. Program management including a program usage status management table for recording at least the latest used date data for each of a plurality of programs stored in a production library storing a plurality of programs used for business processing by a business processing device A program for controlling a device,
According to the latest usage date data in the program usage status management table, the program stored in the production library is judged whether it is an unused program that has not been used for a predetermined period of time,
If it is determined that it is an unused program, the program is copied and stored in a backup library that is different from the production library.
After the copy of the unused program is stored in the backup library, the unused program is deleted from the production library,
The latest usage date data for each of the plurality of programs recorded in the program usage status management table is periodically updated.
It said after finishing the latest use date data update, to control the program management apparatus so that is performed for determining whether or not use program,
program.

Images